Page MenuHomePhabricator
Create Task
Maniphest T297588

connect 2nd cloudcontrol200x-dev NIC to vlan 2105
Closed, DeclinedPublic
Actions

Description

The cloudcontrol200x-dev servers have 2 NIC.

By the time of this writing, they are networked this way (initial config):

* untagged connection to public1-x-codfw (v200x). With static IP assigned from netbox.

As part of T297587: PoC: have cloud hardware servers to the cloud realm using neutron VLAN we would like to explore with adding a connection to vlan 2105.

Intermediary setup should be:

* tagged connection to public1-x-codfw (v200x). With static IP assigned from netbox.
* tagged connection to cloud-instances2-b-codfw (v2105). No IP address since will get it from neutron DHCP.

Once we confirm traffic flows and the setup works as expected, the final state should be:

* tagged connection to cloud-hosts1-codfw (v2118). With static IP assigned from netbox.
* tagged connection to cloud-instances2-b-codfw (v2105). No IP address since will get it from neutron DHCP.

In case the PoC goes wrong, we should rollback to the initial config state.

We will try first with the cloudcontrol2004-dev server.

  • cloudcontrol2004-dev
  • cloudcontrol2001-dev ge-1/0/34
  • cloudcontrol2003-dev

Related Objects
Search...

Event Timeline

aborrero created this task.Dec 13 2021, 10:01 AM
Restricted Application added a project: Infrastructure-Foundations. · View Herald TranscriptDec 13 2021, 10:01 AM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
aborrero added a parent task: T297587: PoC: have cloud hardware servers to the cloud realm using neutron VLAN.Dec 13 2021, 10:01 AM
aborrero assigned this task to Papaul.Dec 13 2021, 10:18 AM
aborrero triaged this task as Medium priority.
aborrero updated the task description. (Show Details)
Maintenance_bot added a project: SRE.Dec 13 2021, 10:45 AM
Papaul added a comment.Dec 13 2021, 3:00 PM

@aborrero can we test this for now on only one server to see if it works before moving it to the other servers?

Papaul updated the task description. (Show Details)Dec 13 2021, 3:07 PM
Papaul updated the task description. (Show Details)
ayounsi subscribed.Dec 13 2021, 4:08 PM

Could we trunk the new vlan instead of using a 2nd physical port?

aborrero added a comment.Dec 13 2021, 4:18 PM
In T297588#7566526, @Papaul wrote:

@aborrero can we test this for now on only one server to see if it works before moving it to the other servers?

Yes, definitely!

In T297588#7566749, @ayounsi wrote:

Could we trunk the new vlan instead of using a 2nd physical port?

Yes! Not sure if that will work for swift (bc bandwidth) but for the first testing in codfw should be enough.

Will rework the task description in a bit.

aborrero updated the task description. (Show Details)Dec 13 2021, 5:37 PM
Dzahn renamed this task from conncet 2nd cloudcontrol200x-dev NIC to vlan 2105 to connect 2nd cloudcontrol200x-dev NIC to vlan 2105.Dec 13 2021, 7:30 PM
Papaul added a comment.Dec 13 2021, 10:21 PM

The 2nd NIC is connected to port ge-1/0/34 only thing left is to do the config in Netbox.

Papaul added a comment.Dec 14 2021, 1:56 PM

@aborrero are we doing trunk so i can assign this task to netops?

aborrero changed the task status from Open to Stalled.Dec 14 2021, 5:54 PM
aborrero moved this task from Inbox to Soon! on the cloud-services-team (Kanban) board.

Yes, we will be doing trunk. Thanks @Papaul I think we're fine here from DCops side for now.

Also, we just had a team meeting today, and I'm no longer sure that I will work on this project anytime soon, so marking as stalled.

Papaul removed Papaul as the assignee of this task.Dec 14 2021, 9:04 PM
Papaul subscribed.
Papaul removed a project: ops-codfw.Jan 3 2022, 3:30 PM
• Marostegui removed a project: SRE.May 19 2022, 7:25 AM
ayounsi moved this task from Backlog to Watching on the netops board.Jul 5 2022, 6:30 AM
aborrero closed this task as Declined.Nov 10 2022, 12:25 PM

It seems we'll be working on T297596: have cloud hardware servers in the cloud realm using a dedicated LB layer instead.

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL