oVirt 4.4 and management network requirements
Hello, does oVirt 4.4. support management network distributed between routed networks and not bound to a single one? In some environments I see situations where there are 2 different server farms with networks not necessarily mapped to the same ranges and so it could be useful to let oVirt hosts of the same cluster to be able to communicate but not on the same physical network. Eg vSphere can do it. Thanks in advance, Gianluca
On Tue, May 26, 2020 at 4:37 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
Hello, does oVirt 4.4. support management network distributed between routed networks and not bound to a single one? In some environments I see situations where there are 2 different server farms with networks not necessarily mapped to the same ranges and so it could be useful to let oVirt hosts of the same cluster to be able to communicate but not on the same physical network. Eg vSphere can do it.
Looks like more details are needed, like how such a network looks like. Dominic should know better about this.
On Tue, May 26, 2020 at 4:14 PM Nir Soffer <nsoffer@redhat.com> wrote:
On Tue, May 26, 2020 at 4:37 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
Hello, does oVirt 4.4. support management network distributed between routed networks and not bound to a single one? In some environments I see situations where there are 2 different server farms with networks not necessarily mapped to the same ranges and so it could be useful to let oVirt hosts of the same cluster to be able to communicate but not on the same physical network. Eg vSphere can do it.
Looks like more details are needed, like how such a network looks like.
Dominic should know better about this.
Like server farm1 has its historically pre-defined/configured/ecc mgmnt network on 10.4.167.x, while server farm2 on 10.4.169.x for example. So hosts in server farm1 would have ip on the first one, while servers in the server farm2 on the second one. The two networks are routed. Gianluca
On Tue, May 26, 2020 at 4:18 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Tue, May 26, 2020 at 4:14 PM Nir Soffer <nsoffer@redhat.com> wrote:
On Tue, May 26, 2020 at 4:37 PM Gianluca Cecchi < gianluca.cecchi@gmail.com> wrote:
Hello, does oVirt 4.4. support management network distributed between routed networks and not bound to a single one? In some environments I see situations where there are 2 different server farms with networks not necessarily mapped to the same ranges and so it could be useful to let oVirt hosts of the same cluster to be able to communicate but not on the same physical network. Eg vSphere can do it.
Looks like more details are needed, like how such a network looks like.
Dominic should know better about this.
Like server farm1 has its historically pre-defined/configured/ecc mgmnt network on 10.4.167.x, while server farm2 on 10.4.169.x for example. So hosts in server farm1 would have ip on the first one, while servers in the server farm2 on the second one. The two networks are routed.
Thanks for sharing the scenario. Why might this scenario not work out of the box?
Gianluca
On Tue, May 26, 2020 at 4:22 PM Dominik Holler <dholler@redhat.com> wrote:
On Tue, May 26, 2020 at 4:18 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Tue, May 26, 2020 at 4:14 PM Nir Soffer <nsoffer@redhat.com> wrote:
On Tue, May 26, 2020 at 4:37 PM Gianluca Cecchi < gianluca.cecchi@gmail.com> wrote:
Hello, does oVirt 4.4. support management network distributed between routed networks and not bound to a single one? In some environments I see situations where there are 2 different server farms with networks not necessarily mapped to the same ranges and so it could be useful to let oVirt hosts of the same cluster to be able to communicate but not on the same physical network. Eg vSphere can do it.
Looks like more details are needed, like how such a network looks like.
Dominic should know better about this.
Like server farm1 has its historically pre-defined/configured/ecc mgmnt network on 10.4.167.x, while server farm2 on 10.4.169.x for example. So hosts in server farm1 would have ip on the first one, while servers in the server farm2 on the second one. The two networks are routed.
Thanks for sharing the scenario. Why might this scenario not work out of the box?
Gianluca
Based on this thread in late 2017 https://lists.ovirt.org/archives/list/users@ovirt.org/message/T7RGXRNY24OV2F... where I received an answer that for same cluster is not possible and no other answers regarding instead its feasibility.... Gianluca
On Tue, May 26, 2020 at 5:03 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Tue, May 26, 2020 at 4:22 PM Dominik Holler <dholler@redhat.com> wrote:
On Tue, May 26, 2020 at 4:18 PM Gianluca Cecchi < gianluca.cecchi@gmail.com> wrote:
On Tue, May 26, 2020 at 4:14 PM Nir Soffer <nsoffer@redhat.com> wrote:
On Tue, May 26, 2020 at 4:37 PM Gianluca Cecchi < gianluca.cecchi@gmail.com> wrote:
Hello, does oVirt 4.4. support management network distributed between routed networks and not bound to a single one? In some environments I see situations where there are 2 different server farms with networks not necessarily mapped to the same ranges and so it could be useful to let oVirt hosts of the same cluster to be able to communicate but not on the same physical network. Eg vSphere can do it.
Looks like more details are needed, like how such a network looks like.
Dominic should know better about this.
Like server farm1 has its historically pre-defined/configured/ecc mgmnt network on 10.4.167.x, while server farm2 on 10.4.169.x for example. So hosts in server farm1 would have ip on the first one, while servers in the server farm2 on the second one. The two networks are routed.
Thanks for sharing the scenario. Why might this scenario not work out of the box?
Gianluca
Based on this thread in late 2017
https://lists.ovirt.org/archives/list/users@ovirt.org/message/T7RGXRNY24OV2F...
where I received an answer that for same cluster is not possible and no other answers regarding instead its feasibility....
Even it is technically possible to have the same management network in two IP subnetworks, this would create a knot in my head because a logical network represents usually a layer 2 network in oVirt. What is the drawback of having a cluster with its own management network per server farm?
Gianluca
On Tue, May 26, 2020 at 6:02 PM Dominik Holler <dholler@redhat.com> wrote:
Based on this thread in late 2017
https://lists.ovirt.org/archives/list/users@ovirt.org/message/T7RGXRNY24OV2F...
where I received an answer that for same cluster is not possible and no other answers regarding instead its feasibility....
Even it is technically possible to have the same management network in two IP subnetworks, this would create a knot in my head because a logical network represents usually a layer 2 network in oVirt.
What is the drawback of having a cluster with its own management network per server farm?
Gianluca
Often it happens that you have to work in pre-existing environments where network (and not only) rules are already established and restricted and not under your control. In my case it happened that there were already in place dedicated networks for putting mgmt in site 1 and site 2 and that they were different ranges and also there wasn't a unique layer2 network transported across both sites.... Gianluca
On Tue, May 26, 2020 at 6:20 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Tue, May 26, 2020 at 6:02 PM Dominik Holler <dholler@redhat.com> wrote:
Based on this thread in late 2017
https://lists.ovirt.org/archives/list/users@ovirt.org/message/T7RGXRNY24OV2F...
where I received an answer that for same cluster is not possible and no other answers regarding instead its feasibility....
Even it is technically possible to have the same management network in two IP subnetworks, this would create a knot in my head because a logical network represents usually a layer 2 network in oVirt.
What is the drawback of having a cluster with its own management network per server farm?
Gianluca
Often it happens that you have to work in pre-existing environments where network (and not only) rules are already established and restricted and not under your control. In my case it happened that there were already in place dedicated networks for putting mgmt in site 1 and site 2 and that they were different ranges and also there wasn't a unique layer2 network transported across both sites....
I see. Are multiple management networks for multiple clusters creating any pain?
Gianluca
participants (3)
-
Dominik Holler -
Gianluca Cecchi -
Nir Soffer