[Engine-devel] Questions on NIC hotplug (http://www.ovirt.org/wiki/Features/Design/DetailedHotlugNic)
1. I wasn't sure from the description, but can one change the Network to which a NIC is connected to when it's up? (looks like a much lighter and reasonable action than unplugging-changing-plugging. Also very easy to do in the physical world). I'm quite sure there's a request for such a feature. 2. The REST API usage of 'activate' and 'deactivate' is certainly not inline with the UI's terminology, which is not only a shame, but is also (to me) confusing with setting the NIC's link up/down (which is possible in QEMU, not sure if we do it in oVirt). the UI concept of arrows also seem to support 'up'/'down' ... 3. Donno if it's just the mock ups, but lets try to use 'Network Card' over 'NIC' where possible. 4. I'm not sure why do we need the 'plug' and 'unplug' buttons, and can't do it in the 'Edit' dialog box. I think it's confusing. 5. How do I create a non-plugged NIC via the API? How do I see if a VM's NIC is plugged or not via the API? 6. SDK example would be great too.
On 13/05/12 15:12, Yaniv Kaul wrote:
1. I wasn't sure from the description, but can one change the Network to which a NIC is connected to when it's up? (looks like a much lighter and reasonable action than unplugging-changing-plugging. Also very easy to do in the physical world). I'm quite sure there's a request for such a feature.
It is not supported in libvirt yet: https://bugzilla.redhat.com/show_bug.cgi?id=805071
2. The REST API usage of 'activate' and 'deactivate' is certainly not inline with the UI's terminology, which is not only a shame, but is also (to me) confusing with setting the NIC's link up/down (which is possible in QEMU, not sure if we do it in oVirt). the UI concept of arrows also seem to support 'up'/'down' ...
Actually the UI part is not up to date, we changed the terminology and updated the API but the UI screens were left with the old terminology, Igor is fixing that as we speak.
3. Donno if it's just the mock ups, but lets try to use 'Network Card' over 'NIC' where possible.
Will do, Alona can you please suggest where this can be fixed.
4. I'm not sure why do we need the 'plug' and 'unplug' buttons, and can't do it in the 'Edit' dialog box. I think it's confusing.
Plug/unplugged is replaced with activate/deactivate and I don't see it as a nic property thus I think they don't belong in the edit dialog box, IMO separate buttons are more clear.
5. How do I create a non-plugged NIC via the API? How do I see if a VM's NIC is plugged or not via the API?
When you create a nic you can pass a parameter active/inactive, Roy - can you please confirm and add how can I see if a nic is plugged or not in the API?
6. SDK example would be great too.
We'll add it soon. Thanks for your feedback, Livnat _______________________________________________
Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Regarding 3- It is just the mock up. Actually it is - Network Interfaces.
----- Original Message -----
From: "Livnat Peer" <lpeer@redhat.com> To: "Yaniv Kaul" <ykaul@redhat.com> Cc: engine-devel@ovirt.org, "Alona Kaplan" <alkaplan@redhat.com>, "Roy Golan" <rgolan@redhat.com> Sent: Sunday, May 13, 2012 3:30:33 PM Subject: Re: [Engine-devel] Questions on NIC hotplug (http://www.ovirt.org/wiki/Features/Design/DetailedHotlugNic)
On 13/05/12 15:12, Yaniv Kaul wrote:
1. I wasn't sure from the description, but can one change the Network to which a NIC is connected to when it's up? (looks like a much lighter and reasonable action than unplugging-changing-plugging. Also very easy to do in the physical world). I'm quite sure there's a request for such a feature.
It is not supported in libvirt yet: https://bugzilla.redhat.com/show_bug.cgi?id=805071
2. The REST API usage of 'activate' and 'deactivate' is certainly not inline with the UI's terminology, which is not only a shame, but is also (to me) confusing with setting the NIC's link up/down (which is possible in QEMU, not sure if we do it in oVirt). the UI concept of arrows also seem to support 'up'/'down' ...
Actually the UI part is not up to date, we changed the terminology and updated the API but the UI screens were left with the old terminology, Igor is fixing that as we speak.
3. Donno if it's just the mock ups, but lets try to use 'Network Card' over 'NIC' where possible.
Will do, Alona can you please suggest where this can be fixed.
4. I'm not sure why do we need the 'plug' and 'unplug' buttons, and can't do it in the 'Edit' dialog box. I think it's confusing.
Plug/unplugged is replaced with activate/deactivate and I don't see it as a nic property thus I think they don't belong in the edit dialog box, IMO separate buttons are more clear.
5. How do I create a non-plugged NIC via the API? How do I see if a VM's NIC is plugged or not via the API?
When you create a nic you can pass a parameter active/inactive, Roy - can you please confirm and add how can I see if a nic is plugged or not in the API?
6. SDK example would be great too.
We'll add it soon.
Thanks for your feedback,
Livnat
_______________________________________________
Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
participants (3)
-
Alona Kaplan -
Livnat Peer -
Yaniv Kaul