Bug 1090733
| Summary: | [RFE][neutron]: LBaaS API v2 and object model improvement | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | RHOS Integration <rhos-integ> |
| Component: | openstack-neutron | Assignee: | Nir Magnezi <nmagnezi> |
| Status: | CLOSED ERRATA | QA Contact: | Alexander Stafeyev <astafeye> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | chrisw, lpeer, markmc, nyechiel, oblaut, tfreger, yeylon |
| Target Milestone: | Upstream M2 | Keywords: | FutureFeature, Triaged |
| Target Release: | 7.0 (Kilo) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://blueprints.launchpad.net/neutron/+spec/lbaas-api-and-objmodel-improvement | ||
| Whiteboard: | upstream_milestone_kilo-2 upstream_definition_approved upstream_status_implemented | ||
| Fixed In Version: | openstack-neutron-2015.1.0-11.el7ost | Doc Type: | Enhancement |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-08-05 13:12:01 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1215470, 1294785 | ||
| Bug Blocks: | |||
|
Description
RHOS Integration
2014-04-24 04:06:45 UTC
This bug reflects API v2 for LBaaS, we recommend adding automation for the new API. *** Bug 1110995 has been marked as a duplicate of this bug. *** Finished testing. Additional BUGs and general info can be found in the following MOJO page https://mojo.redhat.com/docs/DOC-1036220 Several bugs were opened during the test. Not many fixed Gnerally- Lbaasv2 works well ( exceptions: session persistence and health monitoring) LB methods (round robin, least connections, source ip) - good HTTP+HTTPS on same loadbalncer- good Multiple loadbalncers- good. https- good Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2015:1548 |