Add new update data plane service CRs into openstack-operator#1478
Conversation
jistr
left a comment
There was a problem hiding this comment.
We should also make sure the OpenStackVersion resource considers the update finished when the update-services service has deployed. I think we need to edit this spot to make it work both with update and with update-services but not sure if there are more places to edit:
5be737a to
8e307ad
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/0d4d4bf2916a4ab59d4d1efb7b535c09 ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 27m 35s |
8e307ad to
13ae2b6
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/849eb6c0a04f45bfa00e23d6cae29806 ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 26m 51s |
13ae2b6 to
5a0868a
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/5d3cfa78ca8f40988b613e806a50e38b ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 32m 14s |
5a0868a to
0508784
Compare
|
/lgtm |
jistr
left a comment
There was a problem hiding this comment.
My review was still showing as "changes requested" but i already gave a LGTM.
slagle
left a comment
There was a problem hiding this comment.
add logic to indicate that minor update
is complete post service deployment, mirroring the behavior of
'update' EDPMServiceType.
This isn't entirely accurate in that it doesn't mirror the behavior, it's actually a change in behavior and what is being saved on the Status. Previously, we knew when both a service and system update was completed as represented by the deployed OpenStackVersion on the Status. Now we don't, so I think we need to add something in a followup.
Approving with this understanding.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ciecierski, dprince, jistr, slagle The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
The new procedure won't track the state of system update, as using our system update procedure will be optional. Admins will be free to use a different way to keep their operating system up to date, if they'd like. They operating system version will have to fit within what we consider supported. |
|
/retest-required |
Add services for edpm_update_services and edpm_update_system playbooks.[1] For update-services EDPMServiceType add logic to indicate that minor update is complete post service deployment, mirroring the behavior of 'update' EDPMServiceType. Functional test for new update-service is the same as for previous update EDPMServiceType. [1]openstack-k8s-operators/edpm-ansible#962
0508784 to
5dfbabd
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/47630ebb3f8d41be99aab925a0014539 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 48m 37s |
|
recheck |
|
/lgtm |
fdf9869
into
openstack-k8s-operators:main
Add services for edpm_update_services and edpm_update_system playbooks.[1]
For update-services EDPMServiceType add logic to indicate that minor update
is complete post service deployment, mirroring the behavior of
'update' EDPMServiceType.
Functional test for new update-service is the same as for previous
update EDPMServiceType.
OSPRH-16789
[1]openstack-k8s-operators/edpm-ansible#962