-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
Moderate
-
Not Selected
-
False
-
False
-
-
-
-
-
-
-
0
-
0
-
rhos-conplat-osasinfra
-
Red Hat OpenStack Services on OpenShift (formerly Red Hat OpenStack Platform)
-
Enhancement
Feature Overview
Provide OpenShift dual-stack deployments on OpenStack IPv6 single-stack environments as a generally available feature.
Background and Strategic Fit
Implementation of the described architecture currently requires a support exception and it is desired that the architecture becomes a standard available configuration.
Goals
- Perform testing to validate the scenario of a dual-stack OpenShift deployment on single-stack IPv6 OpenStack environment.
- Implement automated testing to validate continued availability of this architecture deployment and identify any regressions early.
- Update documentation that indicates this architecture deployment is now available for use generally.
Requirements
A list of specific needs, capabilities, or objectives that a Feature must deliver to satisfy the Feature. Some requirements will be flagged as MVP. If an MVP gets shifted, the Feature shifts. If a non MVP requirement slips, it does not shift the feature.
| Requirement | Notes | isMVP? |
|---|---|---|
| Initial validation that the desired architecture is functionally complete | It is expected the feature is a test-only validation and that net-new development is not necessary. | YES |
| Implement automated testing that covers the now generally available architecture | Automated testing is expected for any generally available feature to identify regressions early and continued validation it continues to operate nominally. | YES |
| Documentation updates describing the supported architecture and identifying it as generally available | Update the appropriate documentation indicating that the described architecture is valid for deployment without support exception. | YES |
Done - Acceptance Criteria
- all testing has been performed and in the positive
- automated testing has been implemented and configured to execute periodically (particularly prior to release of new major releases)
- documentation has been updated indicating support for desired architecture
Use Cases - i.e. User Experience & Workflow
TODO
Out of Scope
- backporting of the functionality to prior releases; all work should be available in the latest release of both OSP and OCP
- ability to convert a dual-stack OpenStack environment to single-stack
Documentation Considerations
- update to existing documentation indicating the architecture in question is available for deployment
- if there are specific implementation details required for this architecture deployment the documentation should guide the administrator towards a successful deployment
- removal of any notes indicating the architecture is not supported or is technical preview
Questions to Answer
- what is the currently supported version matrix between OpenShift and OpenStack where this architecture is first available?
- how often should automated testing be performed and in which system will perform the validation going forward?
Customer Considerations
TODO: Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.
- is related to
-
OCPBUGS-29085 LoadBalancer ingressController not working with IPv6 and OVN-Octavia provider
-
- New
-
-
OCPBUGS-29608 Add security groups creation playbook for dual stack IPv6 primary UPI support
-
- New
-
-
OCPBUGS-29404 "openshift-install destroy" on dualstack cluster does not remove some ports from load balancer
-
- New
-
-
OSASINFRA-3013 CCM: Implement dual stack services support
-
- To Do
-
-
OCPBUGS-48173 [CI] e2e-openstack-singlestackv6 job can't mount an ipv4 manila share
-
- MODIFIED
-
-
OSASINFRA-3561 SRIOV: update to reach metadata over IPv6
-
- Code Review
-
- is triggered by
-
RFE-5315 OCP IPv4/v6 dual-stack on OSP IPv6 single-stack
-
- Approved
-