openstack/charm-nova-compute
Code Issues Proposed changes

Add README update for extra-bindings

Browse Source 
Add more details about the extra-bindings for the nova-compute
charm as the nova-cloud-controller charm must have access to the
same network spaces to support console access and SSH configuration
for live migration.

Change-Id: I6e7392c34513587544f5d099ef4e8914fbc83c17
Related-Bug: 1874235
This commit is contained in:
James Page 2020-05-27 09:37:52 +01:00
parent 8aa29cc755
commit c696d61bbb
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -159,3 +159,21 @@ pci-passthrough-whitelist: [{"product_id":"0001", "vendor_id":"8086"}, {"product
The [OpenStack advanced networking documentation](http://docs.openstack.org/mitaka/networking-guide/adv-config-sriov.html)
provides further details on whitelist configuration and how to create instances
with Neutron ports wired to SR-IOV devices.
Network Spaces
==============
This charm supports use of network spaces by binding relation endpoints.
In addition this charm declares two extra-bindings:
- **internal**: this binding is used to determine the network space
to use for console access to instances.
- **migration**: this binding is used to determine which network space
should be used for live and cold migrations between hypervisors.
Note that the nova-cloud-controller application must have bindings to the
same network spaces used for both 'internal' and 'migration' extra bindings.
See the [Juju documentation](https://juju.is/docs/spaces) for more information on using network spaces.