Skip to content

templates: Remove empty platform directories#653

Merged
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
cgwalters:templates-drop-platformdirs
May 14, 2019
Merged

templates: Remove empty platform directories#653
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
cgwalters:templates-drop-platformdirs

Conversation

@cgwalters
Copy link
Copy Markdown
Member

@cgwalters cgwalters commented Apr 23, 2019

So far we have not made any use of per-platform templated MCs. Going
forward I don't really expect us to do that much, rather the conditional
code ends up in other components. For the operating system, we
expect components to look at the ignition.platform.id kernel
command line argument. For example, coreos/afterburn
has Azure specific code and it keys off this.

OpenShift components should be looking at the install-config, as
e.g. the machine-api-operator does.

The goal here is simply the templates; specifically this
cuts down on the combinatorial explosion of (master,worker) x platform.

@openshift-ci-robot openshift-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Apr 23, 2019
@runcom
Copy link
Copy Markdown
Member

runcom commented Apr 23, 2019

sounds reasonable to me

/approve

@kikisdeliveryservice
Copy link
Copy Markdown
Contributor

we are totally sure we dont need these? just double checking bc i keep seeing people add them and but have also never seen them used.

@kikisdeliveryservice
Copy link
Copy Markdown
Contributor

(I've always wondered what these were for)

@kikisdeliveryservice
Copy link
Copy Markdown
Contributor

to be held for 4.2 (cc: @runcom)
/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 23, 2019
@abhinavdahiya
Copy link
Copy Markdown
Contributor

to be fair didn't see the change in the PR

it would be shortsightedness to say MCO will never add things that are for a specific platform.
So we should not completely close the path of platform specific MC fragments.

for example

  • Azure internal load balancers black hole flows that have the same source and destination... (components on control plane host talking to api through load balancer black hole requests when the same control plane host is chosen as destination)
    so we might at some point need to deploy some special configuration (scripts,units) to can prevent that.
  • RHHI bare metal platform will require special static pods for infra setup.

@cgwalters
Copy link
Copy Markdown
Member Author

it would be shortsightedness to say MCO will never add things that are for a specific platform.
So we should not completely close the path of platform specific MC fragments.

Right, and to be clear this doesn't remove that functionality, just makes the platform directories not required.

So far we have not made any use of per-platform templated MCs.  Going
forward I don't really expect us to do that much, rather the conditional
code ends up in other components.  For the operating system, we
expect components to look at the `ignition.platform.id` kernel
command line argument.  For example, coreos/afterburn
has Azure specific code and it keys off this.

OpenShift components should be looking at the `install-config`, as
e.g. the machine-api-operator does.

The goal here is simply the templates; specifically this
cuts down on the combinatorial explosion of (master,worker) x platform.
@cgwalters cgwalters force-pushed the templates-drop-platformdirs branch from 66ba1fa to 00dc0b2 Compare May 14, 2019 14:55
@cgwalters
Copy link
Copy Markdown
Member Author

Rebased 🏄‍♂️
/hold cancel
/joke

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@cgwalters: Why did the half blind man fall in the well? Because he couldn't see that well!

Details

In response to this:

Rebased 🏄‍♂️
/hold cancel
/joke

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 removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 14, 2019
@cgwalters
Copy link
Copy Markdown
Member Author

Following up to #653 (comment)

I reworded the commit message and PR text to explicitly note that we're not removing functionality. But let's clean things up for the common case and only create platform dirs where we really need it.

@runcom
Copy link
Copy Markdown
Member

runcom commented May 14, 2019

/approve
/lgtm

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cgwalters, runcom

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-bot
Copy link
Copy Markdown
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 0b76a36 into openshift:master May 14, 2019
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. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants