Bug 1235663
| Summary: | [RFE] Configure LBaaS service under pacemaker on an OSP director Deployment | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Anderson Kaiser <akaiser> |
| Component: | rhosp-director | Assignee: | Hugh Brock <hbrock> |
| Status: | CLOSED WONTFIX | QA Contact: | Shai Revivo <srevivo> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0 (Juno) | CC: | akaiser, akaris, apevec, astafeye, fdinitto, felipe.alfaro, hbrock, ihrachys, jcoufal, jjoyce, jraju, judd.maltin, kurt_hey, lhh, mburns, mzheng, nyechiel, rajini.karthik, randy_perryman, rhel-osp-director-maint, wlehman |
| Target Milestone: | --- | Keywords: | FutureFeature, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-12-14 10:27:09 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
As an additional information: Sadique's comment in Support Case attached to this RFE: [...] Details on on how to enable LBaaS can be found from below article. https://access.redhat.com/articles/1241813 Our recommendation is to stop puppet on each node and do those changes as installer need to be considered as one time deployment tool instead of life cycle management tool. If you must do this via the installer, you can follow the below unsupported step. Note that this change may be overwritten when you update puppet-modules packages on installer and if you report a new puppet related problem, we may request to undo this change and reproduce that problem to continue support. What we need to do is enable the LBaaS plugin by setting the service_plugin value in the /etc/neutron/neutron.conf file: (this need to be appended to the existing one) service_plugins =neutron.services.l3_router.l3_router_plugin.L3RouterPlugin This is not exposed by "Advanced Configuration" of UI. So the only way is to follow the unsupported method of editing /etc/puppet/environments/production/modules/quickstack/manifests/neutron/all.pp and changing line 52 to value => join(['neutron.services.l3_router.l3_router_plugin.L3RouterPlugin',',lbaas',]), to include lbaas as shown above. Other changes required for lbaas are not managed by puppet which are mostly in /etc/neutron/lbaas_agent.ini and will not be overwritten. It has nothing to do with neutron, moving to OSP Director. *** Bug 1240987 has been marked as a duplicate of this bug. *** (In reply to Anderson Kaiser from comment #3) > What we need to do is enable the LBaaS plugin by setting the service_plugin > value in the /etc/neutron/neutron.conf file: (this need to be appended to > the existing one) > > service_plugins =neutron.services.l3_router.l3_router_plugin.L3RouterPlugin > Just to clarify , will this add the lbaas agent under pacemaker on controller too ? Hello , Can anyone give suggestions on how lbaas service needs to be configured under pacemaker ? I couldn't find any upstream doc too . Regards, Jaison R Removing me from "need-info" since the case and bz moved forward. -- Kaiser This is out of scope for RHOSP 10 [I made this BZ public] We have no intention to integrate LBaaS and its HAProxy service plugin with OSP director. This solution is already deprecated upstream, and the focus now in on LBaaS v2 with Octavia: https://bugzilla.redhat.com/show_bug.cgi?id=1378993 |
1. Proposed title of this feature request Enable LBaaS on an OSP Installer Deployment 2. Who is the customer behind the request? Lucas Vanzin (# 1324851) TAM customer: no SRM customer: no Strategic: no 3. What is the nature and description of the request? Enable LBaaS on an OSP Installer Deployment 4. Why does the customer need this? (List the business requirements here) I need to offer LBaaS for my customers, and as I used OSP Installer, the only way of doing that is disabling puppet updates on all controller nodes, and that's bad as is a nice replication feature. Also, for every new controller deployment, I'll need to manyally enable LBaaS since this change won't be automated. 5. How would the customer like to achieve this? (List the functional requirements here) That can be done by default, or there can be an optional item (even on advanced table would help us). 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. You can create this option, enable, and see if all deployed machines gets this option working after a puppet update. 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? N/A 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? No 9. Is the sales team involved in this request and do they have any additional input? No 10. List any affected packages or components. /etc/neutron/neutron.conf /etc/puppet/environments/production/modules/quickstack/manifests/neutron/all.pp puppet-3.6.2-2.el7.noarch 11. Would the customer be able to assist in testing this functionality if implemented? Yes