Q1:codfw:frack network upgrade tracking task
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	RobH
	Jul 30 2024, 8:27 PM

Project Tags

Referenced Files

	F57520229: codfw_frack.jpg
	Sep 18 2024, 2:11 AM

	Restricted File
	Sep 12 2024, 3:40 AM

	F57461650: codfw_frack.jpg
	Sep 4 2024, 10:34 PM

Subscribers

Aklapper

ayounsi

cmooney

Description

This task will track the upgrade of the codfw frack network via items purchased on parent task T367613.

This includes (2) firewalls and (2) switches.

Rack Placement Notes: The firewall devices are only available front to back cooling, so the front of these devices need to face the front of the cold aisle rack intake. The switches are back to front cooling as we prefer and should be set with their network ports facing the rear of the rack.

Coordination on how to best roll this out is best handled with the on-sites for ops-codfw with fundraising-tech-ops and netops.

Overall Checklist (feel free to edit/remove/add):

ops-codfw and netops review and devise racking plan for rolling out this change with fundraising-tech-ops.
install new firewalls facing front of rack (only available in front to rear cooling)
install new switches facing rear of rack (back to front cooling)

Related Objects
Search...

Status	Assigned	Task
		Restricted Task
		Unknown Object (Task)
Resolved	Papaul	T371434 Q1:codfw:frack network upgrade tracking task
Resolved	Papaul	T374176 codfw:frack:rack/install/configuration new firewalls
Resolved	Papaul	T375151 codfw:frack:servers migration task
Resolved	Papaul	T377254 codfw:frack pfw3 and old fasw decommission

Event Timeline

RobH created this task.Jul 30 2024, 8:27 PM

Restricted Application added a project: Infrastructure-Foundations. · View Herald TranscriptJul 30 2024, 8:27 PM

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

RobH added a parent task: Unknown Object (Task).Jul 30 2024, 8:27 PM

RobH moved this task from Backlog to Racking Tasks on the ops-codfw board.

RobH unsubscribed.

Maintenance_bot added a project: SRE.Jul 30 2024, 8:29 PM

ayounsi assigned this task to Papaul.Jul 31 2024, 7:33 AM

Dwisehaupt moved this task from Triage to Watching on the fundraising-tech-ops board.Aug 1 2024, 9:44 PM

The diagram below will outline the cabling of the new Fundraising network devices

{F57501590}

In T371434#10119784, @Papaul wrote:

The diagram below will outline the cabling of the new Fundraising network devices

$codfw_frack.jpg (1,055×544 px, 45 KB)$

Nice work! LGTM overall.

One thing me and @ayounsi discussed before was whether we need the virtual-chassis? As there is no MC-LAG requirement (afaik), we could possibly simplify the setup with two independent switches, with a 2x100G AE trunk to stretch the vlans between them?

Just an idea if we wanted to investigate that. The VC will work fine if we stick with it too.

Papaul updated the task description. (Show Details)Sep 5 2024, 10:37 PM

@cmooney thanks for the feedback. The discussion about not using virtual-chassis was it a final decision or just something that is still on going?

In T371434#10120335, @cmooney wrote:

In T371434#10119784, @Papaul wrote:

The diagram below will outline the cabling of the new Fundraising network devices

$codfw_frack.jpg (1,055×544 px, 45 KB)$

Nice work! LGTM overall.

One thing me and @ayounsi discussed before was whether we need the virtual-chassis? As there is no MC-LAG requirement (afaik), we could possibly simplify the setup with two independent switches, with a 2x100G AE trunk to stretch the vlans between them?

Just an idea if we wanted to investigate that. The VC will work fine if we stick with it too.

I update the diagram with the new interfaces information

@cmooney thanks for the feedback. The discussion about not using virtual-chassis was it a final decision or just something that is still on going?

Final unless strong reasons to revisit it. We didn't purchase the costly VC license.

Cabling wise it should be very similar, the main difference is that we have 2 control planes for the config instead of 1 virtual.

Diagram lgtm !

I think next is to draft up the step by step actions to have everything migrated. Deciding if we want to have a more complex migration but with a short downtime, or we're ok with a longer downtime and direct equipment swap.
Also if we want to replace the pfw first, then the switches, or the other way around.

I think replacing the pfw first will be a good idea since we are not changing any configuration on them but just the name and less cables to deal with.

I update the diagram again since we will not be using VC.

$codfw_frack.jpg (1,055×652 px, 52 KB)$