Add a machine-config-daemon.spec

[cgwalters]

As we move towards having more things in MachineConfig, we also
in many cases need the functionality during "early pivot" before
the cluster is up.

Let's just ship the MCD as part of the host as well so we can use
the same code then.

Now of course we have the same code in two places. I think
what we'd want to do after this is have the "pod-MCD" call out
to the "host-MCD" as a subprocess. That would actually simplify
other things as well.

[cgwalters]

xref #798

[ashcrow]

spec looks proper to me. One question is how this would be built and provided where RHCOS could consume the result.

[cgwalters]

One question is how this would be built and provided where RHCOS could consume the result.

The easy answer today is that we build it the same way we build pivot right? (And then a logical step after that is to fold pivot into this repo)

[cgwalters]

I started the paperwork to do the RPM builds.

[cgwalters]

OK I rebased and did some further tweaks to the spec, which required the VERSION_OVERRIDE and SOURCE_GIT_COMMIT sourcery¹ too.

What I'd like to do is try to do some of this work incrementally; if we land the spec file I can get the machine-config-daemon binary into rhcos, but it won't do anything until we start more work. If the binary is there though it'll just make it easier to hack on without having to custom deploy both RHCOS and the MCD.

¹ See what I did there?

[runcom]

/retest
/approve

[runcom]

let's get this in to allow more testing then

/lgtm

[openshift-ci-robot]

[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:

• OWNERS [cgwalters,runcom]

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

[runcom]

oh this did go in just fine :/

[openshift-ci-robot]

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

Test name	Commit	Details	Rerun command
ci/prow/e2e-etcd-quorum-loss	fc66aa9	link	/test e2e-etcd-quorum-loss

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.

[kikisdeliveryservice]

@runcom @cgwalters wait why is ci running on something that merged??

[cgwalters]

I think the parts of Prow here are asynchronous, and for non-required contexts it doesn't kill them after the PR has merged. (For required contexts, the PR needs them to merge)

[kikisdeliveryservice]

I think the parts of Prow here are asynchronous, and for non-required contexts it doesn't kill them after the PR has merged. (For required contexts, the PR needs them to merge)

but...4 hours async? zoinks