- Added an entry_point for oslo config generator
- Added a script to enumerate config options
- Added a tox target to invoke config generator
Change-Id: Ibc66efd103e790a73ef6389817e099ede65d4f32
WSME released version 0.8.0 which included a few API breaking changes.
These changes resulted in additional validation of our API definition and
is a good thing as things that should have been caught in testing are being caught now.
Email thread:
http://osdir.com/ml/openstack-dev/2015-08/msg01687.html
Culprit:
https://review.openstack.org/#/c/182761/7
Change-Id: I782545d135d622ce8238ec71695ebc342e68bcf7
Config section [oslo_messaging] used to set rabbit config is wrong and not used anymore.
New section [oslo_messaging_rabbit] must be used.
Change-Id: Id06bcdfbfecda202bff13915c4f020bc00e19c3c
Some tests start mocks[1] but never stop them! This change updates
Octavia testcase base class[2] in order to ensure all mocks are stopped
during test cleanups.
[1] self.worker_patcher in
octavia.tests.unit.controller.queue.test_endpoint
[2] octavia.tests.unit.base.TestCase
Change-Id: I30805c729da6a43c028d7df118d26dfe85f000ed
Closes-Bug: #1488586
Not sure if this is actually the fix, but by passing a pure NotFound as
a side-effect, the building of that exception actually fails, which
causes the test to fail (as expected) but not for the reason expected...
NotFound expects at LEAST code=<response_code> and optionally a message.
Change-Id: I0a8539da164074249aa93b70d2cf5af72d1036b4
The code was checking the tenant to determine if octavia had created the
vip port or not. If it did create the vip port then it would delete it, if not
it would not delete the port. Since neutron-lbaas merged a change that set
the device_owner appropriately on the port, we can now check device_owner for
ownership. This also adds octavia as the device_owner of the vip port if
it does create it and sets the device_id to the load balancer's id.
Change-Id: I12adf2824c77f633be7499f120e6f5b3a9c326ef
There are common methods that all neutron based network drivers will most
likely implement the same way. To prevent duplicate code, a common base driver
for all neutron drivers has been created. In the process of splitting this out,
cleaning up of some existing code was done as well.
The network driver's plug_network and unplug_network methods took an
amphora_id as a parameter, but it was always assumed to be the compute_id.
This parameter has been changed to compute_id.
The octavia interface network model originally had just a single ip_address,
but to more accurately reflect what neutron and probably other networking
as a services will return, this has been changed to fixed_ips because
interfaces and ports can have multiple ip addresses.
Other cleanup includes calling the network drivers own get_network, get_subnet,
and get_port methods instead of calling the neutron client's show_network,
show_subnet, and show_port methods. Also, all of these changes required some
test changes as well.
Change-Id: Ie6ebc5bc8babe8562c280ba12a1feab21b4ff3f9
Updating config file to include attributes for spare check and db cleanup
Validate the spare amphora count and create new ones when needed
Perform DB cleanup of the expired amphora
Implements: blueprint housekeeping-manager
Change-Id: I98990fbd3a3cb281a70e0eab97f256c960ca5dcb
Will now load certificates with the provided cert manager.
This allows multilple driver implementations to reuse code
in regards to loading the certificate data from the certificate
manager, e.g. Barbican cert manager.
Change-Id: Id20acf49753c3f75b4152d351412e93394e72b17
The REST driver had an issue with json encoding.
This patchset fixes that issue and adds an assertion
that will cause the tests to catch future encoding issues
with the json encoding.
Change-Id: I723a978dd42282289e25de7077897cccd017df42
Adds the functionality to reload the REST agent when
the certificat to communicate with the controller
changes.
Change-Id: Ifda7ddce5979237b8c00a22a24f73d3c6f993f07
1. Creates a new element for pyroute2
2. Adds this element to the amphora image
3. Updates the amphora REST interface to pass additional network information
4. Creates the policy based routes and rules on the amp during plug vip
5. Updates the REST API spec
Change-Id: Ibd622ec302cf78c12ae2bd5d76d012ab619939a6
When a member is created there must be some calculation to determine what
networks the amphorae need to be plugged into. This calculation needs to
retrieve network information. How it retrieves information was based on an
old version of the network driver and was missed during the network driver
decoupling refactor. The calculate delta method now calls the get_subnet
method of the member's subnet_id attribute.
Change-Id: I65da3ae5f02b991fb6aad5a267dc02b0572b35fd
The /details api provides details about the amphora VM.
It reads the interface's statistics file
/sys/class/net/{interface}/statistics/{type}_bytes
to collect all the stats. While doing so it tries to read the
stat files of the virtual interfaces like eth0:1 also,
which are not available and throws an exception. This
fix excludes virtual interfaces while collecting the
stats by checking whether the interface name has : in it
Closes-Bug:1466688
Change-Id: Ie2786f18b96881ba600a338bcad916677709a5b3
Since I'm updating documentation anyway, and as these fixes don't
fit well into v1 or v2 design documents, I figured a small commit
here to correct the 'VM' terminology to be 'amphora' where
appropriate is called for.
Change-Id: I5f62f9fb62534f48de3d761c64419c08c66fed64