ptoohill1 025ec0024b Allow user-data on amphora creation
Currently, Amphora configuration data is being sent as personality
files as considered by Nova and some providers have limitations
and must use cloud-init user-data.

This patch introduces a new config option to enable user-data.
If enabled the files that were built, such as the amphora config
and certificates for the agent, will be templated into a cloud-init
user-data script that loads the files as expected. After this we
need to restart the agent as cloud-init happens at a higher level
than service scripts. This does increase the boot time.

This is configurable so there is no impact if it's not needed.

Change-Id: I60fa87722302eee9d3d1fd6ff1b5b5b697a2406e
Closes-Bug: #1541231
2016-02-09 16:34:16 -06:00
2014-09-04 15:28:10 -06:00
2016-02-04 23:15:59 -08:00
2016-02-09 16:34:16 -06:00
2014-09-04 15:28:10 -06:00
2015-09-29 17:37:35 +00:00
2014-09-04 15:28:10 -06:00
2015-10-01 23:58:03 +00:00
2015-09-17 12:15:32 +00:00
2016-01-13 14:04:13 +08:00

Octavia

Latest Version

Downloads

Operator-grade open source scalable load balancer.

The Octavia project seeks to become the standard operator-grade load balancer in use in large OpenStack deployments. Note that it is not competing with the Neutron LBaaS extension and may never actually replace it. Rather, Octavia should be seen as "yet another vendor" which is accessed via a driver for Neutron LBaaS.

For more information on project direction and guiding principles for contributors, please see the CONSTITUTION.rst file in this directory, or specifications in the specs/ subdirectory. Other documentation can be found in the docs/ directory.

Please also see https://wiki.openstack.org/wiki/Octavia/Roadmap for the latest version of our project roadmap.

Description
Load Balancing as a Service (LBaaS) for OpenStack
Readme 97 MiB
Languages
Python 97.5%
Shell 1.9%
Jinja 0.6%