Skip to content

Conversation

@stbenjam
Copy link
Member

@stbenjam stbenjam commented Jun 19, 2019

Hi all 👋

This adds experimental support for the baremetal IPI platform. Details about how to use it are in the docs/ directory. We have a prerequisite that there is an existing Ironic infrastructure, and that can be deployed with openshift-metal3/dev-scripts. We are working on moving that to the bootstrap VM, to avoid the dependency on another repository, but we are blocked until RHCOS has an updated version of libpod.

Other known issues that we are working on are tracked here.


This PR since it's initial opening has been broken up into some smaller PR's in addition to this one.

@openshift-ci-robot openshift-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jun 19, 2019
@stbenjam
Copy link
Member Author

Builds for other platforms will fail until openshift-metal3/kni-installer#115 is in, go-lint is addressed in openshift-metal3/kni-installer#113.

@abhinavdahiya
Copy link
Contributor

Please reduce the bash and python magic, and make sure there is a lot of documentation. It's not acceptable to point to docs in a different repo, I would expect that commits have the detailed documentation.

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 20, 2019
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 20, 2019
@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 21, 2019
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 2, 2019
@stbenjam stbenjam force-pushed the baremetal-ipi branch 2 times, most recently from ec082ae to e4d82ab Compare July 2, 2019 14:59
@openshift-ci-robot openshift-ci-robot removed lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Jul 17, 2019
@stbenjam
Copy link
Member Author

@eparis Needs another /lgtm due to rebasing. Small conflict in Gopkg.toml and pkg/asset/machines/worker.go

@stbenjam
Copy link
Member Author

/retest

@eparis
Copy link
Member

eparis commented Jul 17, 2019

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 17, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, eparis, stbenjam

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

@russellb
Copy link
Contributor

/retest

@openshift-ci-robot
Copy link
Contributor

@stbenjam: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/prow/e2e-aws-scaleup-rhel7 0055065 link /test e2e-aws-scaleup-rhel7

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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-merge-robot openshift-merge-robot merged commit 45807e8 into openshift:master Jul 17, 2019
trown pushed a commit to trown/installer that referenced this pull request Jul 18, 2019
For platforms without a DNS as a Service available, there is a
chicken/egg scenario. This is because we cannot setup our own DNS
solution on the nodes before they are booted via ignition.

Instead, we get the ignition config via a virtual IP that is
conifgured and maintained by keepalived. The setup of keepalived
will be done via machine-config-operator, so it is not part of
this patch.

This patch only sets up the plumbing so that we can merge the
keepalived work while keeping CI green. Then we can put up a patch
that will switch to actually using this functionality.

This patch also adds an interface for other platforms that need this
functionality to work from. Specifically, these PRs can be rebased
on this work:
openshift#1873
openshift#1948
mandre pushed a commit to mandre/installer that referenced this pull request Jul 26, 2019
For platforms without a DNS as a Service available, there is a
chicken/egg scenario. This is because we cannot setup our own DNS
solution on the nodes before they are booted via ignition.

Instead, we get the ignition config via a virtual IP that is
conifgured and maintained by keepalived. The setup of keepalived
will be done via machine-config-operator, so it is not part of
this patch.

This patch only sets up the plumbing so that we can merge the
keepalived work while keeping CI green. Then we can put up a patch
that will switch to actually using this functionality.

This patch also adds an interface for other platforms that need this
functionality to work from. Specifically, these PRs can be rebased
on this work:
openshift#1873
openshift#1948
iamemilio pushed a commit to iamemilio/installer that referenced this pull request Jul 26, 2019
For platforms without a DNS as a Service available, there is a
chicken/egg scenario. This is because we cannot setup our own DNS
solution on the nodes before they are booted via ignition.

Instead, we get the ignition config via a virtual IP that is
conifgured and maintained by keepalived. The setup of keepalived
will be done via machine-config-operator, so it is not part of
this patch.

This patch only sets up the plumbing so that we can merge the
keepalived work while keeping CI green. Then we can put up a patch
that will switch to actually using this functionality.

This patch also adds an interface for other platforms that need this
functionality to work from. Specifically, these PRs can be rebased
on this work:
openshift#1873
openshift#1948
mandre pushed a commit to mandre/installer that referenced this pull request Aug 5, 2019
For platforms without a DNS as a Service available, there is a
chicken/egg scenario. This is because we cannot setup our own DNS
solution on the nodes before they are booted via ignition.

Instead, we get the ignition config via a virtual IP that is
conifgured and maintained by keepalived. The setup of keepalived
will be done via machine-config-operator, so it is not part of
this patch.

This patch only sets up the plumbing so that we can merge the
keepalived work while keeping CI green. Then we can put up a patch
that will switch to actually using this functionality.

This patch also adds an interface for other platforms that need this
functionality to work from. Specifically, these PRs can be rebased
on this work:
openshift#1873
openshift#1948
wking added a commit to wking/openshift-installer that referenced this pull request Sep 5, 2019
Most of our docs were bumped in befde3c (pkg/types/installconfig:
Bump v1beta4 to v1, 2019-04-10, openshift#1589), but these v1beta4 references
snuck in with 0ec07d0 (docs: vSphere installation docs, 2019-04-07, openshift#1545)
and 0055065 (baremetal: add baremetal IPI platform, 2019-07-16, openshift#1873).
wking added a commit to wking/openshift-installer that referenced this pull request Oct 30, 2019
…m provider()

We've had the argument since the package landed in 0055065
(baremetal: add baremetal IPI platformo, 2019-07-16, openshift#1873), but it
has never been used.  Drop it to simplify the function calls, and to
make it easier to use grep to answer questions like "does metal
actually care about machineCIDR?" (apparently not).
vrutkovs pushed a commit to vrutkovs/installer that referenced this pull request Dec 2, 2019
…m provider()

We've had the argument since the package landed in 0055065
(baremetal: add baremetal IPI platformo, 2019-07-16, openshift#1873), but it
has never been used.  Drop it to simplify the function calls, and to
make it easier to use grep to answer questions like "does metal
actually care about machineCIDR?" (apparently not).
jhixson74 pushed a commit to jhixson74/installer that referenced this pull request Dec 6, 2019
Most of our docs were bumped in befde3c (pkg/types/installconfig:
Bump v1beta4 to v1, 2019-04-10, openshift#1589), but these v1beta4 references
snuck in with 0ec07d0 (docs: vSphere installation docs, 2019-04-07, openshift#1545)
and 0055065 (baremetal: add baremetal IPI platform, 2019-07-16, openshift#1873).
jhixson74 pushed a commit to jhixson74/installer that referenced this pull request Dec 6, 2019
…m provider()

We've had the argument since the package landed in 0055065
(baremetal: add baremetal IPI platformo, 2019-07-16, openshift#1873), but it
has never been used.  Drop it to simplify the function calls, and to
make it easier to use grep to answer questions like "does metal
actually care about machineCIDR?" (apparently not).
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. lgtm Indicates that a PR is ready to be merged. platform/baremetal IPI bare metal hosts platform size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.