Nuage Vrs
- By Nuage Charmers
- Cloud
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/stable | 1 | 11 Nov 2020 | |
latest/edge | 1 | 11 Nov 2020 |
juju deploy nuage-vrs
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
-
enable-metadata | boolean
Default: True
Enable Metadata Agents. This is useful for deployments which do not include a neutron-gateway (do not require l3, lbaas or vpnaas services) and should only be used in-conjunction with flat or VLAN provider networks configurations.
-
vrs-metadata-name | string
Default: nuage
This parameter is used to set the username when relation is established between nuage-vrs and keystone.
-
vrs-packages | string
Default: nuage-metadata-agent nuage-openvswitch-common nuage-openvswitch-datapath-dkms nuage-python-openvswitch nuage-openvswitch-switch
List of packages to install for VRS. This is Optional as we already have all of them as default value.
-
vrs-ppa-key | string
Optional KEY to Nuage VRS PPA containing Debian packages.
-
vrs-repository-url | string
Nuage VRS repository containing Debian packages.This is must for installing vrs-packages
-
vsc-controller-active | string
Default: 1.1.1.1
Active VRS controller to use. This is mainly used when your Nuage-VSC is not deployed via JUJU, then you can mention your Active VSC IP. When Nuage-VSC is being deployed via juju charm and then configuration is optional as vsc-controller-active ip is being retrieved form relation-get and it will override this vsc-controller-active config value.
-
vsc-controller-standby | string
Default: 1.1.1.2
Optional Standby VRS controller to use ( this is for redundant VSCs). This is mainly used when your Nuage-VSC is not deployed via JUJU, then you can mention your Standby VSC IP. When Nuage-VSC is being deployed via juju charm and then configuration is optional as vsc-controller-standby ip is being retrieved form relation-get and it will override this vsc-controller-active config value