| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Labs instance subnet allocation for codfw | operations/dns | master | +21 -0 |
Details
Details
Related Changes in Gerrit:
Revisions and Commits
Revisions and Commits
| rODNS operations-dns | |||
| rODNS1b87bc57fa51 Labs instance subnet allocation | |||
| rODNS131b2b5faacf Labs instance subnet allocation for Codfw | |||
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Andrew | T42525 Cant add a security group to an existing instance | |||
| Resolved | Andrew | T87279 Make OpenStack Horizon useful for production labs | |||
| Resolved | Andrew | T124181 Support instance manipulation, proxies, dns with Horizon | |||
| Resolved | Andrew | T105690 Support 2fa in keystone/horizon | |||
| Resolved | • chasemp | T120293 Create labtest cluster | |||
| Resolved | Papaul | T117097 deployment tracking of codfw labs test cluster | |||
| Resolved | RobH | T114435 Labs test cluster in codfw | |||
| Resolved | • chasemp | T115492 Allocate subnet for labs test cluster instances |
Event Timeline
Comment Actions
Given that we are looking to do vlan config with Neutron, I think it'd be wise to allocate a very large subnet for this which we can then let Neutron carve it out.
I'm thinking a /16 per DC? (It's a single route to the network controller).
Comment Actions
Let's allocate a similar amount of IPs (/20 iirc or thereabouts) as we did in eqiad, but experiment with how to use them with Neutron. I don't think we quite need a /16 at this point. Also, any flexible network model should be able to use multiple smaller ranges as appropriate upon growth, rather than needing one big block. :)
Comment Actions
Change 249919 had a related patch set uploaded (by Faidon Liambotis):
Labs instance subnet allocation for codfw
Comment Actions
Change 249919 had a related patch set uploaded (by Faidon Liambotis):
Labs instance subnet allocation for codfw