A PLUMgrid Edge is an OpenStack compute node running IO Visor. IO Visor
provides the data plane and network connectivity for OpenStack tenant
instances. Communication between instances on compute nodes is enabled
by creation of VXLAN based overlay tunnels and networks.
The PLUMgrid Platform is a software-only solution that provides a rich set of distributed network functions such as routers, switches, NAT, IPAM, DHCP, and it also supports security policies, end-to-end encryption, and third party Layer 4-7 service insertion.
This charm is responsible for configuring a Compute node as a PLUMgrid Edge.
Once deployed, the charm configures the IO Visor kernel module as a PLUMgrid Edge. The charm also triggers the services essential for a PLUMgrid Edge.
It is a subordinate charm to nova-compute.
Instructions on using the charm:
juju deploy neutron-api
juju deploy neutron-api-plumgrid
juju deploy plumgrid-director
juju deploy nova-compute
juju deploy plumgrid-edge
juju add-relation neutron-api neutron-api-plumgrid
juju add-relation plumgrid-director plumgrid-edge
juju add-relation nova-compute plumgrid-edge
juju add-relation neutron-api-plumgrid plumgrid-edge
For plumgrid-edge to work make the configuration in the neutron-api, neutron-api-plumgrid and plumgrid-director charms as specified in the configuration section below.
Provide the source repo path for PLUMgrid Debs in 'install_sources' and the corresponding keys in 'install_keys'.
The virtual IP passed on in the neutron-api charm has to be same as the one passed in the plumgrid-director charm.
This charm supports the use of Juju Network Spaces, allowing the charm to be bound to network space configurations managed directly by Juju. This is only supported with Juju 2.0 and above.
To use this feature, use the --bind option when deploying the charm:
juju deploy plumgrid-edge --bind "internal=internal-space fabric=fabric-space"
alternatively these can also be provided as part of a juju native bundle configuration:
NOTE: Spaces must be configured in the underlying provider prior to attempting to use them. 'internal' binding is mapped onto OpenStack internal-api endpoint while 'fabric' is mapped to OpenStack tenant-data-api endpoint.
Bilal Baqar firstname.lastname@example.org
Javeria Khan email@example.com
Junaid Ali firstname.lastname@example.org