Bug 1221021 - [RFE][packstack]: support installation of LBaaS v2
Summary: [RFE][packstack]: support installation of LBaaS v2
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-puppet-modules
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z5
: 7.0 (Kilo)
Assignee: Martin Magr
QA Contact: Alexander Stafeyev
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-13 07:06 UTC by Roey Dekel
Modified: 2020-06-11 12:41 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
lbaas v2 activiation 1. The following command will update neutron mariaDB with lbaas tables. neutron-db-manage --service lbaas --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head 3. go to vim /etc/neutron/neutron_lbaas.conf in "service providers" section, commentout (#) all except service_provider=LOADBALANCERV2:Haproxy:neutron_lbaas.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default 4. go to vim /etc/neutron/neutron.conf make sure that in the "service_plugins" section you see "neutron_lbaas.services.loadbalancer.plugin.LoadBalancerPluginv2" (not only this, it is possible that you will see other plugins you enabled in answerfile) 5. go to lbaas_agent file (can be in /etc/neutron or /etc/neutron/services/loadbalancer/haproxy/) add in [DEFAULT] block ovs_use_veth = False add in [haproxy] block user_group = haproxy commentout any "device friver" that is not commented out. If the l3-agent is in failed mode pls see l3_agent logs- you wil probably need to go to /etc/neutron/neutron.conf and comment-out several values in [DEFAULT] block and uncomment-out same values in "oslo_messaging_rabbit" block and other block - you will see it in the log. create "/usr/lib/systemd/system/neutron-lbaasv2-agent.service" file (copy "/usr/lib/systemd/system/neutron-lbaas-agent.service" file to "/usr/lib/systemd/system/neutron-lbaasv2-agent.service" file ) edit: Description=OpenStack Neutron Load Balancing V2 as a Service Agent ExecStart=/usr/bin/neutron-lbaasv2-agent --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/neutron_lbaas.conf --config-file=/etc/neutron/lbaas_agent.ini --log-file /var/log/neutron/lbaasv2-agent.log but with the same flags systemctl stop neutron-lbaas-agent.service systemctl start neutron-lbaasv2-agent.service
Last Closed: 2017-01-30 13:02:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 234727 0 None None None Never
OpenStack gerrit 234728 0 None None None Never

Description Roey Dekel 2015-05-13 07:06:18 UTC
Description of problem:
packstack only supports LBaaS v1 installation

Additional info:
LBaaS v2 is merged to Kilo, manual update of drivers and db is possible.

Comment 4 Alexander Stafeyev 2015-06-03 14:30:17 UTC
ADDITIONALLY 
I think the lbaas tables (which refer to lbaasv2) should be named "lbaasv2"

Comment 5 Alexander Stafeyev 2015-06-04 13:12:31 UTC
lbaas v2 activiation

1. The following command will update neutron mariaDB with lbaas tables. 
neutron-db-manage --service lbaas --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head

3. go to 
vim /etc/neutron/neutron_lbaas.conf
in "service providers" section, commentout (#) all except service_provider=LOADBALANCERV2:Haproxy:neutron_lbaas.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default

4. go to 
vim /etc/neutron/neutron.conf
make sure that in the "service_plugins" section you see "neutron_lbaas.services.loadbalancer.plugin.LoadBalancerPluginv2" (not only this, it is possible that you will see other plugins you enabled in answerfile)

5. go to lbaas_agent file (can be in /etc/neutron or /etc/neutron/services/loadbalancer/haproxy/)


add in [DEFAULT] block
ovs_use_veth = False
add in [haproxy] block
user_group = haproxy
commentout any "device friver" that is not commented out. 

If the l3-agent is in failed mode pls see l3_agent logs- you wil probably need to go to /etc/neutron/neutron.conf and comment-out several values  in [DEFAULT] block and uncomment-out same values in "oslo_messaging_rabbit" block and other block - you will see it in the log.

create "/usr/lib/systemd/system/neutron-lbaasv2-agent.service" file (copy "/usr/lib/systemd/system/neutron-lbaas-agent.service" file to "/usr/lib/systemd/system/neutron-lbaasv2-agent.service" file ) 

edit:

Description=OpenStack Neutron Load Balancing V2 as a Service Agent
ExecStart=/usr/bin/neutron-lbaasv2-agent --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/neutron_lbaas.conf --config-file=/etc/neutron/lbaas_agent.ini --log-file /var/log/neutron/lbaasv2-agent.log
but with the same flags  


systemctl stop neutron-lbaas-agent.service
systemctl start neutron-lbaasv2-agent.service

Comment 23 Jason Guiditta 2016-05-03 13:24:51 UTC
Can just say this will not be backported to kilo?  Seems kind of late to be adding more features.  My vote would be to say closed current release after retargetting this BZ to liberty, and then add needed configuration in installers if desired.


Note You need to log in before you can comment on or make changes to this bug.