Thank you All for your comments.
I've updated the page with those and other thoughts.
Please have a look at the updated and more mature version of the page.
Again, you're more than welcome to send your comments.
Regards,
Yevgeny
On 18/08/14 20:00, Einav Cohen wrote:
* The mockups/UI is missing the "Cluster --> Manage networks" screen which
should present the selection of a network as a management network. That
ability should probably be behave as migration and display role (i.e. radio
button).
+1 on that; pointing out that currently, it looks like the columns that
behave like radio-button (i.e. selection of a cell in one row deselects
the cell of the same column in another row) actually contain check check-
boxes. would be nice to change that to actual radio-buttons, if possible.
another comment on the New/Edit Cluster dialog:
I am not sure if the location of the Management Network field (at the top
gray area of the dialog) is proper; I am not sure how popular the "use
something other than 'ovirtmgmt' as the management network" use-case will
be. If it is not expected to be that popular, maybe even worth putting
that in a section other than 'General'; maybe even something similar to
the "Manage Network" dialog can be put within the "New Cluster" dialog
in a (new) "Network" side-section?
----
Thanks,
Einav
----- Original Message -----
From: "Moti Asayag" <masa...@redhat.com>
To: "Yevgeny Zaspitsky" <yzasp...@redhat.com>
Cc: devel@ovirt.org
Sent: Sunday, August 17, 2014 2:12:25 PM
Subject: Re: [ovirt-devel] Management network as a role - design proposal
Hi,
* The mockups/UI is missing the "Cluster --> Manage networks" screen which
should present the selection of a network as a management network. That
ability should probably be behave as migration and display role (i.e. radio
button).
A network has a status field in the context a cluster: A new required network
is added as 'non-operational', and will change its status to 'operational'
when it is configured on all of the cluster's hosts.
If the network is added as 'not required', it will automatically be set as
'operational'.
Setting the network status on cluster level as 'operational' is determined
and not reversal.
* The introduction is aimed to the first user-flow:
"* Appointing a network as the management network will make the network
required in the given cluster. " - should block 'non-operational' networks
or 'non required' networks from being selected as a management network, and
also block any attempt to mark a management network as non-required.
* network labels aspect:
** if a labelled network is marked as a management network, removing the
label should not remove that network from the hosts (if labelled).
** "Moving a host from a cluster to another one." - if a management network
on cluster A is configured on host, but not attached to cluster B, and that
network is management on the host by label, changing the cluster will remove
it from the host, which will targeted in a host without a management
cluster. This should be blocked to avoid loosing connectivity.
Regards,
Moti
----- Original Message -----
From: "Yevgeny Zaspitsky" <yzasp...@redhat.com>
To: devel@ovirt.org
Cc: rhevm-network-st...@redhat.com
Sent: Thursday, August 14, 2014 6:52:41 PM
Subject: Management network as a role - design proposal
Hi All,
The proposed feature will allow defining an arbitrary network in the DC as
the management network for the cluster, which in its turn will allow
assigning different VLANs for the management networks in the same DC.
Feature page can be found here -
http://www.ovirt.org/Features/Management_Network_As_A_Role .
Please take a look into the page especially into "Open issues" section. I'd
like to have your opinions on that.
Best regards,
Yevgeny Zaspitsky
_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
