[Question]: Does the installer support non-dhcp network for openstack platform?

[bjhuangr]

This issue is opened for asking the question: Does the installer support non-dhcp network for openstack platform?

The background is, if we want to use macvtap mechanism driver, which lacks of DHCP support,

• Is it available to pass the static IP to the RHCOS as kernel parameter and get network interface configured accordingly?
• Does the RHCOS openstack qcow2 image support boot with static IP?

Thanks.

Version

$ openshift-install version
N/A

Platform:

openstack UPI

What happened?

N/A

What you expected to happen?

N/A

How to reproduce it (as minimally and precisely as possible)?

N/A

Anything else we need to know?

N/A

References

N/A

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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-sigs/prow repository.