Additional note: If the new management network is already configured on the hosts,
it should be verified it is configured either with DHCP or static boot protocol.
What about the case in which a host was added and installed via a static IP and not
by FQDN ? Currently, we block changing the IP address. Either we block changing the
management network in such clusters, or we suggest a method to update the host address
and its certificate.
----- Original Message -----
From: "Moti Asayag" <masayag(a)redhat.com>
To: "Yevgeny Zaspitsky" <yzaspits(a)redhat.com>
Cc: devel(a)ovirt.org
Sent: Sunday, August 17, 2014 9:12:25 PM
Subject: Re: 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" <yzaspits(a)redhat.com>
> To: devel(a)ovirt.org
> Cc: rhevm-network-staff(a)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
>
>