Bug 1228419
| Summary: | OSP director does not support split network overcloud configurations | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Ben Nemec <bnemec> |
| Component: | rhosp-director | Assignee: | Dan Sneddon <dsneddon> |
| Status: | CLOSED ERRATA | QA Contact: | Alexander Chuzhoy <sasha> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | Director | CC: | dmacpher, jslagle, mburns, rhel-osp-director-maint, sclewis |
| Target Milestone: | ga | Keywords: | Triaged |
| Target Release: | Director | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
The director provides a method to isolate different network services on individual subnets and VLANs. These instructions are contains within the Basic and Advanced Overcloud Scenarios in the Red Hat Enterprise Linux OpenStack Platform 7.0 Director Installation and Usage guide.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-08-05 13:52:45 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: | |||
|
Description
Ben Nemec
2015-06-04 21:51:10 UTC
The functionality to isolate networks should land in midstream this week. Dan Sneddon will add documenation on how to use it. The network isolation code was just merged into midstream yesterday. A couple of us are testing now, and if we can get the overcloud to deploy with the new code we will put it on CI. Documentation for the network isolation code will be added to the rdo-manager docs. Verified: Environment: instack-undercloud-2.1.2-21.el7ost.noarch The network isolation has been added and it's possible now to separate networks: Provisioning Internal API Tenant Storage Storage Management External 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:1549 |