----- Original Message ----- > From: "Livnat Peer" <lp...@redhat.com> > To: "engine-devel" <engine-devel@ovirt.org>, "Ofri Masad" <oma...@redhat.com> > Sent: Sunday, June 30, 2013 3:59:37 PM > Subject: [Engine-devel] VNIC profiles > > Hi, > > We are working on adding VNIC profiles as part of the work to add VNIC QoS. > > http://www.ovirt.org/Features/Network_QoS#VNIC_Profiles > > We need to define some of the system behavior followed by this change, > here is my take - > > Editing a profile - > -------------------- > A user should be able to edit the profile properties (including profile > name) while VMs are attached and are using this Profile (reference > should be done by id). > > Changing the network though is a bit more tricky as long as we don't > have a way to distinguish between running and current configurations I > think it could be very confusing to the user. Especially since we > support dynamic wiring so the behavior IMO is unpredictable. > I think it should be blocked at this point. > > > Edit a VNIC / change a VNIC profile - > ------------------------------------ > Changing the profile a VM is using while the VM is running should behave > like dynamic wiring (changing the VM network while it is running). > > > Remove a Profile - > ------------------- > Is only valid if all VMs that are using this profile are in status down.
What about HA VMs , are they forced to be down as well for this operation? > It should update all VMs to point to no profile which should behave like > none network today. > > I see no reason to support a profile on a none network at this point. > > The above is also relevant for upgrade flow (upgrading none network to > point to no profile) > > > Removing a Network - > ---------------------- > should remove all profiles on that network > > > VM snapshot/import/export - > -------------------------- > We should handle VMs that are pointing to a network directly for b/w > compatibility. > we need to select first profile that is on that network that the user > has permissions on. > > > I assume there are more, comments are welcome > > Thanks, Livnat > > _______________________________________________ > Engine-devel mailing list > Engine-devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel