Juju Charm - Neutron API
Go to file
James Page ea727e8286 [trivial] Tidy summary and description in metadata.yaml 2014-06-24 11:59:40 +01:00
hooks Added start/stop hooks 2014-06-23 12:48:50 +01:00
templates Remove unused etc_nova_api-paste.ini template and config 2014-06-17 10:25:17 +01:00
unit_tests Updated with fixes suggested from bug comments 2014-06-23 12:18:17 +01:00
.bzrignore more tests, more coverage 2014-06-18 17:48:38 +01:00
.coveragerc Added openstack upgrade, unit tests and lint fixes 2014-06-20 11:02:09 +01:00
Makefile Added Makefile and charm-helpers-sync.yaml. Fixed lint 2014-06-17 16:52:42 +01:00
README.md Added readme 2014-06-23 14:44:08 +01:00
charm-helpers-sync.yaml Added Makefile and charm-helpers-sync.yaml. Fixed lint 2014-06-17 16:52:42 +01:00
config.yaml Add syslog,verbose and debug logging options 2014-06-17 10:06:48 +01:00
copyright Updated with fixes suggested from bug comments 2014-06-23 12:18:17 +01:00
icon.svg Updated with fixes suggested from bug comments 2014-06-23 12:18:17 +01:00
metadata.yaml [trivial] Tidy summary and description in metadata.yaml 2014-06-24 11:59:40 +01:00
setup.cfg Added openstack upgrade, unit tests and lint fixes 2014-06-20 11:02:09 +01:00

README.md

Overview

This principle charm provides the Neutron API service which was previously provided by the nova-cloud-controller charm. When this charm is joined with the nova-cc charm the nova-cc charm will shutdown its api service, deregister it from neutron and inform the compute nodes of the new neutron url. This charm expects the following relations:

  1. neutron-plugin-api relation with subordinate neutron plugin charms (such as neutron-openvswitch)
  2. neutron-api relation with nova-cloud-controller
  3. Database backend
  4. amqp relation with message broker. If a single message broker is being used for the openstack deployemnt then it can relat to that. If a seperate neutron message broker is being used it should relate to that.
  5. identity-service relation
  6. ha relation with ha subordinate