This patch removes an unused configuration option
"haproxy_cert_dir" that was flagged as a potential security
risk.
Change-Id: I31af43e8265431767544802451d9b5c297d83d28
Closes-Bug: #1548556
The L7Policy API type checker presently lists the redirect_pool_id
parameter as StringType(). While this is not incorrect, it is more
correct to call it a UuitType().
In addition to the above change, I removed unnecessary string length
checking on string response parameters.
No tests needed updating, as we already have good test coverage of the
validations we do on the redirect_pool_id in the L7Policy API.
Change-Id: I2bf70b51c6bc0949165f8af31c7d47c3407df08b
Closes-Bug: 1549013
Testing of the API shows that it didn't react well to having
non-essential parameters set to 'None' in update requests. This
patch moves L7Policy validations much sooner in the update process
(ie. we catch them at the API), and otherwise reorganizes most of
the L7Policy validation code into the common validations file both so
that it can be called from various locations in the code base, and
so that we can have an easier time unit testing the validation code.
Closes-Bug: 1550913
Change-Id: I7c14a8cef3d74b2b8d6f4d1ec4f6f9f32f96b9ad
Swift is not default enabled by devsatck, and it is not used
by Octavia by default too. The content in the sample local.conf
is useless.
Change-Id: Ie3accb5c1be455f0212fbc07d4f5c26a55529b3c
Deprecated amp_image_id option with the new amp_image_tag option.
Also switched devstack plugin to rely on the tag to update the image
used for new load balancers.
Implements: blueprint use-glance-tags-to-manage-image
Change-Id: Ibc28b2220565667e15ca2b2674e55074d6126ec3
The previously-merged patches for L7 and shared pools did not include
release notes. This commit adds the missing release notes.
Change-Id: I0c216addf9e85d512fd2fe689db1e819d183b36c
Partially-Implements: blueprint lbaas-l7-rules
Sets up the flows and some new tasks required to create all the
resources needed for an entire load balancer graph. This includes
updating all listeners on all amphorae (depending on topology), and
plugging networks and setting up the routes and rules on every
amphora for a load balancer. Luckily this mostly reuses tasks and
flows that were already created, though some new tasks and flows
were created specifically for handling many listeners.
Co-Authored-By: Trevor Vardeman <trevor.vardeman@rackspace.com>
Change-Id: I43a838e80281a37537e179cd8d4768f45e1ca7f1
We need the ability to send a request to the API with a fully configured
load balancer and have it create all the appropriate resources all at once. It
will support all load balancing topologies, and all different configurations of
a load balancer.
Co-Author: Trevor Vardeman <trevor.vardeman@rackspace.com>
Change-Id: Id3a5ddb8efded8c6ad72a7118424ec01c777318d
Adds a new cascading delete method to the REST API.
When a load balancer is deleted it will alo delete
all associated listeners, pools, memebers, healthmonitors,
and L7 Policies
Change-Id: I0fd88923dc76e573b92d83f68d292ded913b13a6
After a discussion, we decided that the best user experience to have if
they attempt to delete a pool in use by an l7policy (even an inactive
one) is to block the deletion. This patch implements this behavior.
Change-Id: I8b954ac6e12ec994cb63e5b56eecac7fc67c4e83
Closes-Bug: 1549097
Removes unecessary and error causing steps from the
Delete LoadBalancer flow.
Change-Id: Ic96c7e44f223f0603dc899c9acf2cb11c57e18de
Closes-Bug: #1547256
The to_data_model method previously labeled an SNI container without a
unique identifier, using the "listener_id". Now it will use the
"tls_container_id" to ensure it is truly unique.
Change-Id: I174f8f650fc51668fd7b70e845d4706916f06295
Recent scenario tests are showing create operations on
pool-subordinate objects (like Member and Health Monitor) appear
to be returning too quickly with statuses that indictate the
operation is done. This has lead to intermittent problems of tests
failing because the load balancer was not in an expected state.
Our hypothesis is that the aforementioned operations are not
setting the load balancer status to PENDING_UPDATE as they should.
This patch fixes this problem, ensuring that PENDING_UPDATE status
is set on the load balancer and listener status correctly prior to
the execution of the creation taskflow, as well as whenever pool or
pool-subordinate objects are updated and deleted. This should resolve
the related intermittent scenario test failures.
In addition to the above, I have re-organized some of the API methods
to remove some code duplication between various API controller, and
re-organized several of the API functional tests for health monitors
and members to catch the above problem.
Change-Id: I5e3a1eabb76af3b913e3edbe95a3b14c3c40244b
Closes-Bug: 1548588
https://blueprints.launchpad.net/octavia/+spec/anti-affinity
Added a new column in lb table for server group id;
Added a new task in compute tasks for creating server group;
Added a new task in dtabase tasks to update server
group id info for lb;
Add server group id in create method in nova driver to support
anti-affinity when creating compute instance
Change-Id: If0d3a9ba1012651937a2bda9bc95ab4f4c8852d5
