1. Introduce the apic:svi network extension attribute to indicate its a SVI network. 2. For SVI network, user can do either pre-existing l3out or auto-l3out (which means we will create the whole l3out for the user). For pre-existing l3out, user has to provide the external network DN while creating the SVI network. 3. When auto-l3out is being used, the l3out vrf/tenant can be changed accordingly when this SVI network is connected to a router. For this release we will prevent user from connecting the pre-existing l3out SVI network to a router. 4. When VM is being spun on a host, the corresponding host link(s) will be used to create the SVI interface under the l3out while for the non-SVI network, the host link(s) will be added to the static paths of the corresponding EPG. There will be no EPG/BD being created on the APIC side though for the SVI network as its using the l3out instead. Change-Id: I44e2d3ef57ba562c5f157c440f7f15d671536cf4 (cherry picked from commit8c0d978296) (cherry picked from commit72b45dbe21) (cherry picked from commit6602e9a233)
Group Based Policy (GBP) provides declarative abstractions for achieving scalable intent-based infrastructure automation.
GBP complements the OpenStack networking model with the notion of policies that can be applied between groups of network endpoints. As users look beyond basic connectivity, richer network services with diverse implementations and network properties are naturally expressed as policies. Examples include service chaining, QoS, path properties, access control, etc.
GBP allows application administrators to express their networking requirements using a Group and a Policy Rules-Set abstraction. The specifics of policy rendering are left to the underlying pluggable policy driver.
GBP model also supports a redirect operation that makes it easy to abstract and consume complex network service chains and graphs.
Checkout the GBP wiki page for more detailed information: <http://wiki.openstack.org/GroupBasedPolicy>
The latest code is available at: <http://git.openstack.org/cgit/openstack/group-based-policy>.
GBP project management (blueprints, bugs) is done via Launchpad: <http://launchpad.net/group-based-policy>
For help using or hacking on GBP, you can send mail to <mailto:openstack-dev@lists.openstack.org>.
Acronyms used in code for brevity:
- PT: Policy Target
- PTG: Policy Target Group
- PR: Policy Rule
- PRS: Policy Rule Set
- L2P: L2 Policy
- L3P: L3 Policy
- NSP: Network Service Policy
- EP: External Policy
- ES: External Segment