Merge ironic and ironic-inspector repositories, single Dockerfile

[elfosardo]

This change moves Dockerfile, configuration and scripts from the
ironic-inspector container image repository to the ironic one.

This approach provides one Dockerfile that builds an image that contains
all the services necessary to run both ironic and ironic-inspector.
The scripts and configurations are kept separated for the time being as
some of them conflict with each other (e.g. runhttpd) and are being
renamed to avoid overwriting during the image building process.

Those changes will need to be reflected in CI as well.

This change is mutually exclusive with #252

[elfosardo]

/assign @maelk @dtantsur @hardys

[elfosardo]

/test-integration

[dtantsur]

I like this path, just a couple of comments inline.

[elfosardo]

/assign @fmuyassarov

[elfosardo]

/test-integration

[elfosardo]

/test-integration

[fmuyassarov]

I assume we will have a single image (named Ironic..)? If yes, then we need to

1. clean up ironic-inspector image references from Metal3-dev-env, some examples: ref1, ref2, etc.
2. remove image building process from quay (this can be done after this PR goes in I think)

[elfosardo]

I assume we will have a single image (named Ironic..)? If yes, then we need to

1. clean up ironic-inspector image references from Metal3-dev-env, some examples: [ref1](https://github.com/metal3-io/metal3-dev-env/blob/40e3f79b78d4f317e117b98731230a7c929f5307/vm-setup/roles/v1aX_integration_test/tasks/move.yml#L13), [ref2](https://github.com/metal3-io/metal3-dev-env/blob/9886555e8abb71fc58d676ba77553567e5aa8163/lib/common.sh#L159), etc.

2. remove image building process from [quay](https://quay.io/repository/metal3-io/ironic-inspector) (this can be done after this PR goes in I think)

Thanks @fmuyassarov !
that's correct, we'll have a single image that contains all needed for ironic and ironic-inspector
I was also looking at metal3-dev-env, but I think that also needs to be done after this PR merges?
I would also like to wait for metal3-io/baremetal-operator#851 and metal3-io/ironic-inspector-image#81 to merge first

[fmuyassarov]

I assume we will have a single image (named Ironic..)? If yes, then we need to

1. clean up ironic-inspector image references from Metal3-dev-env, some examples: [ref1](https://github.com/metal3-io/metal3-dev-env/blob/40e3f79b78d4f317e117b98731230a7c929f5307/vm-setup/roles/v1aX_integration_test/tasks/move.yml#L13), [ref2](https://github.com/metal3-io/metal3-dev-env/blob/9886555e8abb71fc58d676ba77553567e5aa8163/lib/common.sh#L159), etc.

2. remove image building process from [quay](https://quay.io/repository/metal3-io/ironic-inspector) (this can be done after this PR goes in I think)

Thanks @fmuyassarov !
that's correct, we'll have a single image that contains all needed for ironic and ironic-inspector
I was also looking at metal3-dev-env, but I think that also needs to be done after this PR merges?
I would also like to wait for metal3-io/baremetal-operator#851 and metal3-io/ironic-inspector-image#81 to merge first

Yeah, I think metal3-dev-env changes can be done later too, because we will still have image for ironic-inspector in quay, so that won't really break the CI.

[fmuyassarov]

I forgot about BMO, ref1, ref2, etc.

[dtantsur]

\o/

[metal3-io-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dtantsur, elfosardo

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:

• OWNERS [dtantsur]

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

[elfosardo]

@maelk @fmuyassarov @hardys can you please have another look at this? Thanks!

[fmuyassarov]

Thanks, this LGTM. We will probably need to force merge this one too, considering tide isn't in place at this moment.

[elfosardo]

@fmuyassarov thanks! As clarified on our chat, I'm totally ok waiting for tide to be back before we merge this.
We can re-evaluate the status during the week or early next week

[dtantsur]

/lgtm

Tide is back?

[fmuyassarov]

/lgtm

Tide is back?

It was for a while when I was testing. Still there are some minor things to setup :) but hopefully by Monday will be up.

[fmuyassarov]

@elfosardo @dtantsur Prow is back on track. Probably /lgtm will be enough to get this PR in.

[dtantsur]

/lgtm

pretty please