Re: [ovirt-users] separate ovirtmgmt from glusterfs traffic
Hi, In my experience, having ovirt traffic on the same nic that gluster can make your platafrom unstable. I was using it for large file storage and gluster has so big traffic that ovirt got confused and started marking hosts as unavailable because of hi latency. I've opened an RFE over a year ago, but had no luck with the team to get it done. In the RFE I was asking to have a way in the UI to decide which nic to use for gluster other than the MGMT net that is the one ovirt lets you use. There's another way to do this and it's from outside ovirt. There you have to unregister and re register the bricks using gluster console commands. This way, when you register the bricks, you can specify the IP address of the spare NIC and then the traffic will not interfere with the mgmt. There's a step that I don't recall much, but ovirt is going to need to know that the bricks are no longer is the mgmt IP, maybe someone else in the list can help with this. I can tell you that if you search the list you'll see my posts about this and the replys of those who helped my back then. Regards,
On 18-11-2014 10:25, Juan Pablo Lorier wrote:
Hi,
In my experience, having ovirt traffic on the same nic that gluster can make your platafrom unstable. I was using it for large file storage and gluster has so big traffic that ovirt got confused and started marking hosts as unavailable because of hi latency. I've opened an RFE over a year ago, but had no luck with the team to get it done. In the RFE I was asking to have a way in the UI to decide which nic to use for gluster other than the MGMT net that is the one ovirt lets you use. There's another way to do this and it's from outside ovirt. There you have to unregister and re register the bricks using gluster console commands. This way, when you register the bricks, you can specify the IP address of the spare NIC and then the traffic will not interfere with the mgmt. There's a step that I don't recall much, but ovirt is going to need to know that the bricks are no longer is the mgmt IP, maybe someone else in the list can help with this. I can tell you that if you search the list you'll see my posts about this and the replys of those who helped my back then. Regards,
The way I split this is using a split-dns solutions, either with bind or hosts files. This way engine sees the mgmt address and the gluster servers see their storage address. Regards, Joop
On 18/11/14 06:25, Juan Pablo Lorier wrote:
Hi,
In my experience, having ovirt traffic on the same nic that gluster can make your platafrom unstable. I was using it for large file storage and gluster has so big traffic that ovirt got confused and started marking hosts as unavailable because of hi latency. I've opened an RFE over a year ago, but had no luck with the team to get it done. In the RFE I was asking to have a way in the UI to decide which nic to use for gluster other than the MGMT net that is the one ovirt lets you use. There's another way to do this and it's from outside ovirt. There you have to unregister and re register the bricks using gluster console commands. This way, when you register the bricks, you can specify the IP address of the spare NIC and then the traffic will not interfere with the mgmt. There's a step that I don't recall much, but ovirt is going to need to know that the bricks are no longer is the mgmt IP, maybe someone else in the list can help with this. I can tell you that if you search the list you'll see my posts about this and the replys of those who helped my back then. Regards,
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I think that the possibility to add a separate storage network is a must. It doesn't make sense Gluster support if you can't separate management network traffic of storage network traffic. In 3.5 you can define management/vm/display/migration interfaces but not storage interfaces. Why? I don't know. But I think that Gluster support is incomplete without exclusive storage networking. Regards Federico
Hi, I think is a really good question, why does not possible sepereate storage network traffic like display, etc? This is not an easy task to set up, and it's more difficult on a live system. Tibor ----- Eredeti üzenet -----
On 18/11/14 06:25, Juan Pablo Lorier wrote:
Hi,
In my experience, having ovirt traffic on the same nic that gluster can make your platafrom unstable. I was using it for large file storage and gluster has so big traffic that ovirt got confused and started marking hosts as unavailable because of hi latency. I've opened an RFE over a year ago, but had no luck with the team to get it done. In the RFE I was asking to have a way in the UI to decide which nic to use for gluster other than the MGMT net that is the one ovirt lets you use. There's another way to do this and it's from outside ovirt. There you have to unregister and re register the bricks using gluster console commands. This way, when you register the bricks, you can specify the IP address of the spare NIC and then the traffic will not interfere with the mgmt. There's a step that I don't recall much, but ovirt is going to need to know that the bricks are no longer is the mgmt IP, maybe someone else in the list can help with this. I can tell you that if you search the list you'll see my posts about this and the replys of those who helped my back then. Regards,
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I think that the possibility to add a separate storage network is a must. It doesn't make sense Gluster support if you can't separate management network traffic of storage network traffic. In 3.5 you can define management/vm/display/migration interfaces but not storage interfaces. Why? I don't know. But I think that Gluster support is incomplete without exclusive storage networking.
Regards
Federico _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi Demeter, Yes...I already asked the same question before 2 months....they suggest me the workaround ( http://www.ovirt.org/oVirt_Wiki:How_to_change_Gluster%27s_network_interface) but after workaround still it's same...even no improvement in the Ovirt 3.5... It's very hard to go in the production without separate storage network....may be someone from redhat can help... Thanks, Punit On Wed, Nov 19, 2014 at 4:00 AM, Demeter Tibor <tdemeter@itsmart.hu> wrote:
Hi,
I think is a really good question, why does not possible sepereate storage network traffic like display, etc? This is not an easy task to set up, and it's more difficult on a live system.
Tibor
----- Eredeti üzenet -----
On 18/11/14 06:25, Juan Pablo Lorier wrote:
Hi,
In my experience, having ovirt traffic on the same nic that gluster can make your platafrom unstable. I was using it for large file storage and gluster has so big traffic that ovirt got confused and started marking hosts as unavailable because of hi latency. I've opened an RFE over a year ago, but had no luck with the team to get it done. In the RFE I was asking to have a way in the UI to decide which nic to use for gluster other than the MGMT net that is the one ovirt lets you use. There's another way to do this and it's from outside ovirt. There you have to unregister and re register the bricks using gluster console commands. This way, when you register the bricks, you can specify the IP address of the spare NIC and then the traffic will not interfere with the mgmt. There's a step that I don't recall much, but ovirt is going to need to know that the bricks are no longer is the mgmt IP, maybe someone else in the list can help with this. I can tell you that if you search the list you'll see my posts about this and the replys of those who helped my back then. Regards,
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I think that the possibility to add a separate storage network is a must. It doesn't make sense Gluster support if you can't separate management network traffic of storage network traffic. In 3.5 you can define management/vm/display/migration interfaces but not storage interfaces. Why? I don't know. But I think that Gluster support is incomplete without exclusive storage networking.
Regards
Federico _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
We will try and address this in the next release of oVirt - there were some issues earlier with identifying the bricks correctly, but with the gluster host uuid support in gluster xml commands, we can fix this. https://bugzilla.redhat.com/show_bug.cgi?id=1049994 - marked for 3.6.0 On 11/19/2014 01:30 AM, Demeter Tibor wrote:
Hi,
I think is a really good question, why does not possible sepereate storage network traffic like display, etc? This is not an easy task to set up, and it's more difficult on a live system.
Tibor
----- Eredeti üzenet -----
On 18/11/14 06:25, Juan Pablo Lorier wrote:
Hi,
In my experience, having ovirt traffic on the same nic that gluster can make your platafrom unstable. I was using it for large file storage and gluster has so big traffic that ovirt got confused and started marking hosts as unavailable because of hi latency. I've opened an RFE over a year ago, but had no luck with the team to get it done. In the RFE I was asking to have a way in the UI to decide which nic to use for gluster other than the MGMT net that is the one ovirt lets you use. There's another way to do this and it's from outside ovirt. There you have to unregister and re register the bricks using gluster console commands. This way, when you register the bricks, you can specify the IP address of the spare NIC and then the traffic will not interfere with the mgmt. There's a step that I don't recall much, but ovirt is going to need to know that the bricks are no longer is the mgmt IP, maybe someone else in the list can help with this. I can tell you that if you search the list you'll see my posts about this and the replys of those who helped my back then. Regards,
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I think that the possibility to add a separate storage network is a must. It doesn't make sense Gluster support if you can't separate management network traffic of storage network traffic. In 3.5 you can define management/vm/display/migration interfaces but not storage interfaces. Why? I don't know. But I think that Gluster support is incomplete without exclusive storage networking.
Regards
Federico _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi, Is this feature will be available on an existing domain or on a live system ? (after upgrade) I would be very grateful if it will available on 3.5.x versions:) In this case your team will be guest for a lot of chocklet/beer from me:) Have a nice day, Tibor ----- Eredeti üzenet -----
We will try and address this in the next release of oVirt - there were some issues earlier with identifying the bricks correctly, but with the gluster host uuid support in gluster xml commands, we can fix this.
https://bugzilla.redhat.com/show_bug.cgi?id=1049994 - marked for 3.6.0
On 11/19/2014 01:30 AM, Demeter Tibor wrote:
Hi,
I think is a really good question, why does not possible sepereate storage network traffic like display, etc? This is not an easy task to set up, and it's more difficult on a live system.
Tibor
----- Eredeti üzenet -----
On 18/11/14 06:25, Juan Pablo Lorier wrote:
Hi,
In my experience, having ovirt traffic on the same nic that gluster can make your platafrom unstable. I was using it for large file storage and gluster has so big traffic that ovirt got confused and started marking hosts as unavailable because of hi latency. I've opened an RFE over a year ago, but had no luck with the team to get it done. In the RFE I was asking to have a way in the UI to decide which nic to use for gluster other than the MGMT net that is the one ovirt lets you use. There's another way to do this and it's from outside ovirt. There you have to unregister and re register the bricks using gluster console commands. This way, when you register the bricks, you can specify the IP address of the spare NIC and then the traffic will not interfere with the mgmt. There's a step that I don't recall much, but ovirt is going to need to know that the bricks are no longer is the mgmt IP, maybe someone else in the list can help with this. I can tell you that if you search the list you'll see my posts about this and the replys of those who helped my back then. Regards,
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I think that the possibility to add a separate storage network is a must. It doesn't make sense Gluster support if you can't separate management network traffic of storage network traffic. In 3.5 you can define management/vm/display/migration interfaces but not storage interfaces. Why? I don't know. But I think that Gluster support is incomplete without exclusive storage networking.
Regards
Federico _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (6)
-
Demeter Tibor -
Federico Alberto Sayd -
Joop -
Juan Pablo Lorier -
Punit Dambiwal -
Sahina Bose