-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Designate CI framework and Zuul Jobs
-
12
-
False
-
-
False
-
Not Selected
-
?
-
No Docs Impact
-
To Do
-
RHOSSTRAT-109 - Designate support for RHOSO Greenfield Deployment (Target 18.0 FR3)
-
?
-
?
-
40% To Do, 40% In Progress, 20% Done
-
-
-
VANS-001, VANS-002
-
2
-
2024Q3
Set the basics for Designate CI, covering the architecture repo (i.e. addition to a unified job) , ci-framework-jobs and any necessary changes to the ci-framework, and Zuul job that can be used to monitor designate's state.
Note: does not include successful tempest tests at this time. This is mainly to establish a stable base to "release" patches into.
Definition of done is a usable base for deploying designate using the ci-framework as well as a zuul job that can be run* Does not include being enabled in a unified job as designate is not yet ready. That is:
- can designate be deployed using standard ci-framework. ansible execution with a workaround patch that enables designate in the openstack operator
- can designate be deployed using a zuul job
- how to do both is documented somewhere accessible
'*' it is likely the zuul job may have require a depends on as well as an additional patch of some kind to enable designate at this time.
- is blocked by
-
OSPRH-8123 make bind9 and unbound accessible as necessary.
- In Progress
-
OSPRH-417 The designate operator should create and manage an unbound pod
- In Progress
-
OSPRH-8133 Implement predicable IPs for designate miniDNS and bind9 pods
- In Progress
-
OSPRH-10105 Reintroduce redis in designate-operator
- In Progress
-
OSPRH-8109 Generate basic backend related configurations for relevant designate services
- Dev Complete
-
OSPRH-8128 Implement bind pool management for podified control plane
- Dev Complete
- relates to
-
OSPRH-480 BZ#2109004 [RFE] Podified Control Plane: Designate (QE Tasks)
- In Progress