Bug 1036013

Description of problem:
Hi,

currently, you can not set
a static network via Cloud-Init.


To clarify: The IP-Address, Netmask and Gateway get passed, but instead
of "static" the option "none" gets passed to the vm.

Version-Release number of selected component (if applicable):

ovirt-engine 3.3.1-2 beta

How reproducible:


Steps to Reproduce:
Select a shutdown vm, click run once.
Click Initial Run, select Cloud-Init

Now select "Network" and "add new"
Name your interface, e.g. eth0
Do not configure DHCP, instead,
fill in IP Address, Netmask, Gateway, etc.

Start the vm.


Actual results:
if you mount the meta-data cd-rom into any vm and read
the meta-data.json it says:

iface eth0 inet none

the rest of the information seems to be correct, though.

Expected results:
I would suppose that this would pass the following options
into the meta-data:

iface eth0 inet static


Additional info:


You can see this from 2 point of views:

1. If I do not select DHCP and I configure IP Address etc. I want
a static configuration, therefore "static" should be in the meta-data.
If I would have wanted "none", I wouldn't bother configuring the
interface, would I? -> Bug

2. There is no button for "static" in the GUI, therefore the option
get's not passed, "none" may be the default option.
In this case, it would be cool to have a checkbox for "static".
--> RFE

I didn't test this from the API yet, but I hope there is an option
to set the networking to static from there?

What do you think? Bug or RFE? Can this be fixed in 3.3.1.1 maybe (fix
should be small, without looking into the code)?

I can't always do full upgrades (3.3.2 would be next).

On the Maillinglist this was suggested as a bug.