Skip to content

Bug 1878758: openstack UPI: Allow for no FIP or router#4219

Merged
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
shiftstack:os_upi_fipless_router
Oct 2, 2020
Merged

Bug 1878758: openstack UPI: Allow for no FIP or router#4219
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
shiftstack:os_upi_fipless_router

Conversation

@pierreprinetti
Copy link
Member

@pierreprinetti pierreprinetti commented Sep 25, 2020

If the external network is not provided, the router will not be created
and external connectivity will be a respopnsibility of the operator.

Floating IPs will be set if available, on an individual basis. The
external network is a requirement for FIPs; if not provided, the
playbooks will error.

The bootstrap FIP is now required to be created manually like the other
FIPs.

This is a follow-up to #3755.

/cc luis5tb adduarte iamemilio mandre

@pierreprinetti
Copy link
Member Author

The e2e-openstack-upi job is expected to fail until I adapt the job to create a bootstrap FIP manually.

May I get a review (/approve) before I start doing that?

@luis5tb
Copy link
Contributor

luis5tb commented Sep 28, 2020

Looks good to me, just a couple of questions:

  • Is bootstrap FIP also a requirement now for IPI?
  • Should we also document the option when you don't want to connect to an external network (like FIPless + disconnected)

@pierreprinetti
Copy link
Member Author

Is bootstrap FIP also a requirement now for IPI?

It is not. In this patch, IPI and UPI diverge a bit in that respect.

Should we also document the option when you don't want to connect to an external network (like FIPless + disconnected)

This new PR aims at narrowing the scope of the change as much as possible, and at avoiding any magic. I believe that working towards supporting the absence of an external network is the natural next step. However, I'd treat it as a separate change. WDYT?

Copy link
Member

@mandre mandre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not clear exactly what problem we're trying to solve here.

Letting the user specify the bootstrap FIP makes some sense to me in a UPI scenario, but why forcing an external network? It's a regression from the previous implementation

@pierreprinetti pierreprinetti changed the title openstack UPI: Create a router when FIPless openstack UPI: Allow for no FIP or router Sep 29, 2020
@pierreprinetti pierreprinetti changed the title openstack UPI: Allow for no FIP or router Bug 1878758: openstack UPI: Allow for no FIP or router Sep 29, 2020
@openshift-ci-robot openshift-ci-robot added the bugzilla/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. label Sep 29, 2020
@openshift-ci-robot
Copy link
Contributor

@pierreprinetti: This pull request references Bugzilla bug 1878758, 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.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.6.0) matches configured target release for branch (4.6.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
Details

In response to this:

Bug 1878758: openstack UPI: Allow for no FIP or router

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.

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Sep 29, 2020
@pierreprinetti
Copy link
Member Author

/label platform/openstack

@pierreprinetti
Copy link
Member Author

Made the external network optional again. Required for FIPs. FIPs can be passed on an individual basis.

@mandre
Copy link
Member

mandre commented Sep 30, 2020

/retest

@pierreprinetti
Copy link
Member Author

/cc @MaysaMacedo

Copy link
Contributor

@MaysaMacedo MaysaMacedo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just a question and suggestion:

@pierreprinetti
Copy link
Member Author

e2e-openstack-upi requires openshift/release#12322

@mandre
Copy link
Member

mandre commented Oct 1, 2020

/retest

Copy link
Contributor

@Fedosin Fedosin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one small typo :)

@pierreprinetti pierreprinetti force-pushed the os_upi_fipless_router branch 2 times, most recently from 99ccd7c to ee3f486 Compare October 1, 2020 18:58
@pierreprinetti
Copy link
Member Author

openshift/release#12385

@mandre
Copy link
Member

mandre commented Oct 2, 2020

/test e2e-openstack-upi

If the external network is not provided, the router will not be created
and external connectivity will be a respopnsibility of the operator.

Floating IPs will be set if available, on an individual basis. The
external network is a requirement for FIPs; if not provided, the
playbooks will error.

The bootstrap FIP is now required to be created manually like the other
FIPs.
@mandre
Copy link
Member

mandre commented Oct 2, 2020

/lgtm
/approve

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 2, 2020
@openshift-ci-robot
Copy link
Contributor

[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

Details Needs approval from an approver in each of these files:

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 2, 2020
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 2, 2020

@pierreprinetti: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-aws-workers-rhel7 7df6205 link /test e2e-aws-workers-rhel7

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit e1fe5b5 into openshift:master Oct 2, 2020
@openshift-ci-robot
Copy link
Contributor

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

Bugzilla bug 1878758 has been moved to the MODIFIED state.

Details

In response to this:

Bug 1878758: openstack UPI: Allow for no FIP or router

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. platform/openstack

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants