Re: [Engine-devel] Network labeling requirements follow up questions

On 01/08/2014 06:18 PM, Malini Rao wrote: > [top posting] > > Based on your responses then, we need to tweak Eldan's sketch - see attached. > > Here, you will see I have two tabs on the right - Unassigned networks and Labels. Unassigned networks will list individual networks that have not been assigned either manually or as part of a label. If a network has been assigned to a NIC as apart of a label, it will still show up on the unassigned networks list but if the user tries to assign that network to that same NIC, then the UI will not allow that and a message will pop-up stating '<Network Name> is already assigned to this NIC". Does this make sense? Or do we allow network sharing only via Bonding? I.e, if NIC 1 is assigned Label1 ( Blue, yellow, Green) and I want to assign NIC2 to Blue only, would I drag Blue from unassigned networks ( even t hoguh blue is assigned via label 1 to another NIC) or do I drag NIC 2 to NIC 1 and create a bond which presents me an option to use all 3 or select from the list of networks attached to NIC1? > > Going back to my mockup, you will also see an attachment for the unassigned Labels tab where you see the labels, the networks associated with them so that you don't have to drag it to the left in order to see what networks live in that label. I have retained Eldan's Manage labels action link too. > > Let me know if this makes sense. > Hi Malini, We are currently using the idea of labels as an aggregation object and tried to capture that in the UI approach we are taking. Lior would add screen shots of the approach later today or early next week and we can start a discussion based on his current work. Livnat > Thanks > Malini > > > > ----- Original Message ----- > From: "Livnat Peer" <lpeer(a)redhat.com&gt; > To: "Malini Rao" <mrao(a)redhat.com&gt; > Cc: "Eldan Hildesheim" <ehildesh(a)redhat.com&gt;, "Dan Kenigsberg" <danken(a)redhat.com&gt;, "Moti Asayag" <masayag(a)redhat.com&gt;, "Lior Vernia" <lvernia(a)redhat.com&gt;, "engine-devel" <engine-devel(a)ovirt.org&gt; > Sent: Wednesday, January 8, 2014 3:41:29 AM > Subject: Re: Network labeling requirements follow up questions > > On 01/07/2014 11:46 PM, Malini Rao wrote: >> Livnat, >> >> I had asked a couple of questions about network labeling reqs offline but wanted to continue the discussion on the list. Thank you for the answers and I have copied my questions and your answers for context - >> >> 1. Can a network be part of several labels? >> Currently not, we are not sure if there is a use case for that ATM, but >> I hope users would surprise us with an interesting use case. >> >> 2. Can a network exist as a available network in the Setup Host networks dialog on its own even if it is part of a label? i.e, can a network be assigned to a NIC on its own and to another NIC as part of a label? >> >> Network can not be provisioned twice on the same host (regardless of labels). >> >> With regard to your answer to my question 2, I understand that the network cannot be provisioned twice on the same host but it can be provisioned to multiple hosts... right? >> >> So, Let's say the Green network is part of a label called label 1 which also includes yellow and red networks, and let's say Host 1 is provisioned using label 1 and so it can use green, yellow and red networks. > >> For Host 2, can I provision with just Green rather than with Label 1? > > yes > >> Or can a network be used only once in a label and across hosts? > > label is just a tool to ease network provisioning on the host, you can > always use 'manual' actions to provision the networks. > > Hope that clarifies, I'll be happy to answer more questions if you have any. > > Livnat > > >> >> >> Thanks >> Malini >> >