Page MenuHomePhabricator

CloudVPS: network architecture
Open, MediumPublic

Description

This is the epic tracking task for the current efforts to re-evaluate and re-think the CloudVPS network architecture and the relationship between production and cloud realms.

We have several working documents that are related to this:

Related Objects

StatusSubtypeAssignedTask
OpenNone
Resolvedaborrero
Resolvedayounsi
Resolvedayounsi
OpenNone
Declinedaborrero
Declined JHedden
OpenNone
Openfaidon
StalledNone
Resolvedaborrero
Resolvedaborrero
StalledNone
Resolvedayounsi
Resolvedaborrero
Resolvedayounsi
Openaborrero
ResolvedPapaul
ResolvedRobH
Resolvedaborrero
Resolvedaborrero
OpenNone
Resolvedayounsi
Resolvedaborrero
Resolvedaborrero

Event Timeline

The document is: https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS/Admin/Neutron_ideal_model (edits welcome).

I put in some basic ones: https://wikitech.wikimedia.org/w/index.php?title=Portal:Cloud_VPS/Admin/Neutron_ideal_model&diff=1808555&oldid=1808492

From the page:

full IPv6 support in Cloud VPS, meaning that every single VM has his own IPv6 allocated (TODO: or even a range per project?)

I'd suggest that each project should get it's own IPv6 range and ideally it's own IPv4 range. Recently I've seen a couple of interesting cross-project traffic flows that flew under the radar due to generic 10/8 rules. The eqiad1-r migration showed some of them but it's not the solution to the problem as there's still a flat network which any project will have instances scattered across. I haven't edited this in but I think we should? I don't know how much space we're willing to give each project.

Edit: After some semi-related discussion with Arturo I've split this out into it's own entry on the page

Can someone point me to the current network layout? Vlans, ip space in use, what's used to route/filter traffic, etc.? Knowing the current situation is usually a good first step when designing a to be situation. Does Wikimedia have an overall architecture or architecture principles? That would be good input too.

Can someone point me to the current network layout? Vlans, ip space in use, what's used to route/filter traffic, etc.? Knowing the current situation is usually a good first step when designing a to be situation. Does Wikimedia have an overall architecture or architecture principles? That would be good input too.

Regarding the Neutron side, you can check this https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS/Admin/Neutron

aborrero renamed this task from CloudVPS: our ideal future model to CloudVPS: network architecture.Dec 21 2020, 12:53 PM
aborrero updated the task description. (Show Details)
aborrero added a subtask: Restricted Task.
ayounsi closed subtask Restricted Task as Resolved.Apr 8 2021, 12:32 PM