Public bug reported:
I'm hoping this is something that will go away with the neutron-lbaas
and Octavia merge.
Create a self-signed certificate like so:
openssl genrsa -des3 -out self-signed_encrypted.key 2048
openssl rsa -in self-signed_encrypted.key -out self-signed.key
openssl req -new -x509
Public bug reported:
Right now, the Octavia API allows the specification of the project_id on
the create commands for the following objects:
listener
health_monitor
member
pool
However, all of these objects should be inheriting their project_id from
the ancestor load_balancer object. Allowing
parameter
as appropriate.
** Affects: neutron
Importance: Undecided
Assignee: Stephen Balukoff (sbalukoff)
Status: In Progress
** Changed in: neutron
Assignee: (unassigned) => Stephen Balukoff (sbalukoff)
--
You received this bug notification because you are a mem
Public bug reported:
Both the reference Octavia driver and the namespace driver use haproxy
to deliver load balancing services with LBaaSv2. When closely looking at
the operation of the haproxy daemons with a utility like hatop (
https://github.com/feurix/hatop ), one can see that the connection
Public bug reported:
When q-lbaasv2 is enabled in your devstack local.conf, this implies that
LBaaS v2 is going to be used, and neutron-lbaas's corresponding devstack
plugin.sh script creates a new /etc/neutron/neutron_lbaas.conf file with
come configuration parameters. However, under several
indeed change at any time), or updated to more
dynamically detect the VIP address that gets assigned when the value
isn't specified directly.
** Affects: neutron
Importance: Undecided
Assignee: Stephen Balukoff (sbalukoff)
Status: New
** Changed in: neutron
Assignee
to
dynamically determine the Ubuntu codename in use on the current devstack
(i.e. so we don't break compatibility with trusty, but also allow for
testing on other Ubuntu releases).
** Affects: neutron
Importance: Undecided
Assignee: Stephen Balukoff (sbalukoff)
Status: In Progress
tences;
Empty set (0.00 sec)
** Affects: neutron
Importance: Undecided
Assignee: Stephen Balukoff (sbalukoff)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Stephen Balukoff (sbalukoff)
--
You received this bug notification because you are a member
Public bug reported:
In neutron/db/migration/__init__.py, on line 168, the
create_foreign_keys method there forces any foreign keys that created to
have ondelete='CASCADE', no matter whether the foreign_keys parameter
passed to the method had that option set. This is particularly bad,
because if
Public bug reported:
Given the problems caused recently by a migration on neutron-lbaas that
broke things for people using PostgreSQL, we should implement a test
which ensures that alembic migrations produce results exactly consistent
with the database models in the project, and which are
(which is one of the purposes of the patch, along with preparation for
deploying the L7 code).
** Affects: neutron
Importance: Undecided
Assignee: Stephen Balukoff (sbalukoff)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo
11 matches
Mail list logo