VirtualNetworks

• Launchpad Entry: OpenstackSpec:foo
• Created:
• Contributors:
• Packages affected:

Summary

Rather than treating private and public IP addresses as separate entities (with distinct APIs and divergent featuresets), we should manage all cloud IP resources in a consistent fashion. This should support different physical and logical network topologies.

Release Note

The new virtual networking apis provide users with control of both private and public addressing, multiple NICs on each virtual server, and explicit firewall controls on each NIC.

Rationale

The existing network code in Nova is restrictive, and assumptions about NASA-centric requirements (such as the cloudpipe VPNs) are baked into the code at a low level. At the same time, it does not provide enough flexibility to support alternative network models.

Virtual Networks

Each virtual server runs within a designated virtual network. There are two primary network models currently supported: vlan-based (used by NASA Nebula), and 'flat' (used by Rackspace Cloud). Every network model must provide for the concept of a virtual network.

VNets may be shared: globally (in the case of public addressing, or the use of flat networks), or within a project (in the case of vlan-based networks)

VNets may use RFC 1918 or real-world IP addressing.

VNets must (for the sake of future virtual network portability) use a subnettable block of IP addresses, with a dedicated gateway and broadcast address within the subnet.

Vnets should support both IPv4 and IPv6 natively - it is strongly encouraged that OpenStack deployments (and the reference packages) use IPv6 internally at least.

Design

You can have subsections that better describe specific parts of the issue.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

Include:

• data migration, if any
• redirects from old URLs to new ones, if any
• how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

---