Bug 2004236: Document how to enable Octavia Day 2

[iamemilio]

Documentation to describe the steps to enable octavia as a day 2
operation in a cluster.

/hold
/cc @dulek

[openshift-ci]

@iamemilio: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

Document how to enable Octavia Day 2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[iamemilio]

cc @mandre

[iamemilio]

/assign @mandre
/assign @dulek

[iamemilio]

/assign @MaysaMacedo

[iamemilio]

cc @maxwelldb how does this look?

[maxwelldb]

Lookin' pretty good. Made a few comments and suggestions.

[iamemilio]

Updated, thanks all for the reviews :)

[EmilienM]

could we add a link to a BZ tracking this feature, so 1) users can follow the feature and 2) we have a BZ in our backlog and solve it one day :)

[iamemilio]

Talked this over with Martin, I am not going to track this with a BZ because we can never backport support for this. It would be considered a feature backport. We will just document it here and downstream.

[mandre]

Looks good. How do you plan to merge this? We'll need to reference a BZ, where the parent is validated, if we want to merge in release-4.8.

[openshift-ci]

@iamemilio: This pull request references Bugzilla bug 2004236, which is invalid:

• expected the bug to target the "4.8.z" release, but it targets "---" instead
• expected dependent Bugzilla bug 2004235 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
• expected dependent Bugzilla bug 2004235 to target a release in 4.9.0, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 2004236: Document how to enable Octavia Day 2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mandre]

/bugzilla refresh
/retest

[openshift-ci]

@mandre: This pull request references Bugzilla bug 2004236, which is invalid:

• expected dependent Bugzilla bug 2004235 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh
/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mandre]

/bugzilla refresh

[openshift-ci]

@mandre: This pull request references Bugzilla bug 2004236, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.8.z) matches configured target release for branch (4.8.z)
• bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 2004235 is in the state CLOSED (CURRENTRELEASE), which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
• dependent Bugzilla bug 2004235 targets the "4.9.0" release, which is one of the valid target releases: 4.9.0
• bug has dependents

Requesting review from QA contact:
/cc @eurijon

In response to this:

/bugzilla refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mandre]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mandre

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• docs/user/openstack/OWNERS [mandre]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[iamemilio]

/hold cancel

[hardys]

[patch-manager] Can someone help me understand the dependency chain here please? https://bugzilla.redhat.com/show_bug.cgi?id=2004236 depends on https://bugzilla.redhat.com/show_bug.cgi?id=2004235 which links to #5090 but AFAICS this isn't a backport of that patch.

[iamemilio]

sorry, I removed that dependency. We closed the 4.9 bz, and this is not a backport.

[hardys]

sorry, I removed that dependency. We closed the 4.9 bz, and this is not a backport.

[patch-manager] Thanks @iamemilio - so from what I can understand the situation is:

• Code changes landed in 4.9 to make this configuration easier so the process/docs are different
• This documents a 4.8 only interim method, thus it's not a backport of the 4.9 patch

I just wanted to understand the impact if users start doing this, e.g can they cleanly upgrade from this 4.8 only method to the new-for-4.9 method, and is that tested anywhere?

Not trying to be too pedantic here, I do realize it's just a docs change (and that $customers will likely follow downstream docs), but I wanted to ensure we fully understand the potential upgrade impact before merging, thanks for any further info you can provide! :)

[iamemilio]

yeah, so actually, what we are having users manually do in 4.8 is exactly what we automated in 4.9. In order to use these fetaures in a 4.9 cluster, we would actually require users to follow this documentation if they were upgrading from 4.8.

[iamemilio]

cc @mandre for a fact check, just in case we did some fancy upgrade automation I dont know about

[mandre]

yeah, so actually, what we are having users manually do in 4.8 is exactly what we automated in 4.9. In order to use these fetaures in a 4.9 cluster, we would actually require users to follow this documentation if they were upgrading from 4.8.
cc @mandre for a fact check, just in case we did some fancy upgrade automation I dont know about

This is correct, nothing fancy here, just instruction on how to edit the cloud provider configuration. It should have no impact on upgrades.

[dhellmann]

[patch-manager] 🚀 Approved for z-stream by score: 0.50

picked

[openshift-ci]

@iamemilio: All pull requests linked via external trackers have merged:

• openshift/installer#5161

Bugzilla bug 2004236 has been moved to the MODIFIED state.

In response to this:

Bug 2004236: Document how to enable Octavia Day 2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.