[Engine-devel] RFE: Netwrok Main Tab

[Avi Tal]

----- Original Message -----
> From: "Yaniv Kaul" <ykaul at redhat.com>
> To: "Moti Asayag" <masayag at redhat.com>
> Cc: engine-devel at ovirt.org
> Sent: Sunday, September 23, 2012 6:16:47 PM
> Subject: Re: [Engine-devel] RFE: Netwrok Main Tab
> 
> On 09/23/2012 06:12 PM, Moti Asayag wrote:
> > On 09/23/2012 05:01 PM, Yaniv Kaul wrote:
> >> On 09/23/2012 04:55 PM, Alona Kaplan wrote:
> >>> ----- Original Message -----
> >>>> From: "Avi Tal" <atal at redhat.com>
> >>>> To: "Alona Kaplan" <alkaplan at redhat.com>
> >>>> Cc: engine-devel at ovirt.org
> >>>> Sent: Sunday, September 23, 2012 4:17:26 PM
> >>>> Subject: Re: [Engine-devel] RFE: Netwrok Main Tab
> >>>>
> >>>>
> >>>>
> >>>> ----- Original Message -----
> >>>>> From: "Alona Kaplan" <alkaplan at redhat.com>
> >>>>> To: "Avi Tal" <atal at redhat.com>
> >>>>> Cc: engine-devel at ovirt.org
> >>>>> Sent: Sunday, September 23, 2012 1:31:32 PM
> >>>>> Subject: Re: [Engine-devel] RFE: Netwrok Main Tab
> >>>>>
> >>>>> 1. What actions do you suggest to add?
> >>>> Add, Edit and remove actions of each component.
> >>>>
> >>> Host:
> >>> Add- What will add action on Networks->Hosts sub tab do? Choose
> >>> an
> >>> existing host and attach the network to one of its nics?
> >>> How will it work? after choosing the host you will open
> >>> setupNetworks
> >>> window and just enable dragging of the selected network (in the
> >>> main
> >>> tab) to a nic? I think it is too much.
> >>>
> >>> Edit- same as add.
> >>>
> >>> Remove- What is the meaning of Remove host in network's context?
> >>> The
> >>> network will be detached from the host? I think it is confusing.
> >>>
> >>> Vm/Template:
> >>> Add: What will it do? You will choose a vm and then add a vnic to
> >>> the
> >>> vm? Where will you see the vnic details?
> >>> Edit: Same as add.
> >>> Remove: You will remove all the vnics that use the selected
> >>> network
> >>> from the vm? Or do you mean to add a remove per vnic?
> >> For all the above: yes.
> >> We can certainly work on the small details, but having a main tab
> >> with
> >> little to no action whatsoever is kinda disappointing.
> > IMO adding 'assign' action in the main tab might be handy in order
> > to
> > assign a single network in a single dialog to several clusters.
> >
> > However It is not clear to me how Add/Edit for a VM in a sub-tab
> > should
> > look like. The VM should have a list of interfaces (represented as
> > sub
> > collection/tree).
> 
> I was thinking more of right-click on the network, selecting 'Add to
> VM'
> and then selecting single/mutliple VMs from a dialog with all the VMs
> (yes, filtered via search).
> Y.
> 

+1

> > What will be the meaning of 'Add' in that context? Since the VM
> > already
> > have a vNIC attached to that network. If adding another once, it
> > should
> > be enabled on the record representing the VM itself which will
> > confuse
> > the user.
> > Same goes for 'Edit' of a VM interface under a context of a
> > specific
> > network: in the current 'Edit VM Interface' you can change the
> > network.
> > Should the same dialog be used here as well?
> >
> > The 'Remove' option is the clearer action on this context.
> >
> >
> >> (example of 'small details' - yes, when clicking remove for a
> >> VM/template - it will remove all vNICs that use that network from
> >> the
> >> VM. A VM with more than one vNIC on the same network is not the
> >> common
> >> case anyway, and if you want to remove just a single vNIC, go to
> >> the
> >> VM). I think we can also live with Add/Remove only, and 'defer'
> >> the edit
> >> actions to the respectable objects (host/vm/template) edit dialog
> >> boxes
> >> that originates from their own main tab.
> >>
> >> Y.
> >>
> >>>>> 2. I don't understand your suggestion. You mean add
> >>>>> SetupNetworks
> >>>>> to
> >>>>> the Networks main tab?
> >>>> No.
> >>>> Just Thinking of a nice display which will present logical
> >>>> network
> >>>> and his connected host/vm configuration instead of passing
> >>>> through
> >>>> dub-tabs
> >>>> I should give it a deeper thought.
> >>>>
> >>>>
> >>>>> ----- Original Message -----
> >>>>>> From: "Avi Tal" <atal at redhat.com>
> >>>>>> To: "Alona Kaplan" <alkaplan at redhat.com>
> >>>>>> Cc: engine-devel at ovirt.org
> >>>>>> Sent: Thursday, September 20, 2012 6:58:05 PM
> >>>>>> Subject: Re: [Engine-devel] RFE: Netwrok Main Tab
> >>>>>>
> >>>>>> 1. Why not having Actions for Hosts, Vms and Templates ?
> >>>>>> I believe we should have those actions instead of making the
> >>>>>> user
> >>>>>> browse between 'network -> vms -> network (sub tab)' just in
> >>>>>> order
> >>>>>> to update VM's network.
> >>>>>>
> >>>>>> 2. Why having such a big window which most of the time will be
> >>>>>> empty?
> >>>>>>      How many logical network would be existed in the system?
> >>>>>>      My suggestion is to go for more graphical window which
> >>>>>>      will
> >>>>>>      present:
> >>>>>>      A. logical networks
> >>>>>>      B. Multiple networks with the host configurations at the
> >>>>>>      same
> >>>>>>      window: very important because most of the System admins
> >>>>>>      would
> >>>>>>      like to have a bigger picture of the entire network
> >>>>>>      configuration
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> ----- Original Message -----
> >>>>>> From: "Alona Kaplan" <alkaplan at redhat.com>
> >>>>>> To: engine-devel at ovirt.org
> >>>>>> Sent: Thursday, September 20, 2012 1:50:15 PM
> >>>>>> Subject: [Engine-devel] RFE: Netwrok Main Tab
> >>>>>>
> >>>>>> Hi all,
> >>>>>>
> >>>>>> Please review the wiki and add your comments.
> >>>>>>
> >>>>>> http://wiki.ovirt.org/wiki/Feature/NetworkMainTab
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> RFE:
> >>>>>> https://bugzilla.redhat.com/858742
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Alona.
> >>>>>> _______________________________________________
> >>>>>> Engine-devel mailing list
> >>>>>> Engine-devel at ovirt.org
> >>>>>> http://lists.ovirt.org/mailman/listinfo/engine-devel
> >>>>>>
> >>> _______________________________________________
> >>> Engine-devel mailing list
> >>> Engine-devel at ovirt.org
> >>> http://lists.ovirt.org/mailman/listinfo/engine-devel
> >> _______________________________________________
> >> Engine-devel mailing list
> >> Engine-devel at ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/engine-devel
> 
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>