# Is there a feature to change the way hypervisor nodes refer to the frontend? **URL:** \ **Category:** Product Support\ **Created:** [May 11, 2017, 8:19am UTC](https://forum.opennebula.io/t/is-there-a-feature-to-change-the-way-hypervisor-nodes-refer-to-the-frontend/4265 "2017-05-11T08:19:25Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![wind0204](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/wind0204/32/5182_2.png) [@wind0204](https://forum.opennebula.io/u/wind0204)\ **Post date:** [May 11, 2017, 8:19am UTC](https://forum.opennebula.io/t/is-there-a-feature-to-change-the-way-hypervisor-nodes-refer-to-the-frontend/4265/1 "2017-05-11T08:19:25Z")
Hi, I’m building a HA cluster of OpenNebula frontends and I’d like to keep the hostnames on the frontend nodes. as ‘one-2’, ‘one-3’, ‘one-1’ Is there a feature to change the way hypervisor nodes refer to the frontend node? so that I can keep the hostname of the frontend nodes in the HA cluster unchanged while there is a V-hostname-thingy and a V-IP address (192.168.255.237 one [one.petacnc.com](http://one.petacnc.com)) that are used on hypervisor nodes. So that in the event of shutting down a failed frontend node and running OpenNebula on another frontend node, hypervisors don’t need any update. it seems it was all set up automatically in the first place and I just needed to put ‘192.168.255.240 one-2 [one-2.petacnc.com](http://one-2.petacnc.com)’ in /etc/hosts on every node. There is an opennebula document about frontend HA setup.( [http://docs.opennebula.org/5.2/advanced\_components/ha/frontend\_ha\_setup.html#frontend-ha-setup](http://docs.opennebula.org/5.2/advanced_components/ha/frontend_ha_setup.html#frontend-ha-setup) ); its example does have a line about setting up a VIP address though it seems just for sunstone, no further example is provided. Thanks in advance. Best Regards, Gunwoo Gim ---
**Author:** ![wind0204](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/wind0204/32/5182_2.png) [@wind0204](https://forum.opennebula.io/u/wind0204)\ **Post date:** [May 12, 2017, 5:36am UTC](https://forum.opennebula.io/t/is-there-a-feature-to-change-the-way-hypervisor-nodes-refer-to-the-frontend/4265/2 "2017-05-12T05:36:24Z")
I think hypervisors have to initiate communication with the frontend, they have to submit the monitoring log, don’t they? ---
**Author:** ![wind0204](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/wind0204/32/5182_2.png) [@wind0204](https://forum.opennebula.io/u/wind0204)\ **Post date:** [May 12, 2017, 5:47am UTC](https://forum.opennebula.io/t/is-there-a-feature-to-change-the-way-hypervisor-nodes-refer-to-the-frontend/4265/3 "2017-05-12T05:47:53Z")
Could anybody tell me when and how the method is declared with which hypervisor nodes initiates data communication with the frontend node? I could just set a DNS record of “one-2” for example. I thought it would be the second best plan. Best Regards, Gunwoo Gim ---
**Author:** ![atodorov\_storpool](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/atodorov_storpool/32/5327_2.png) [@atodorov\_storpool](https://forum.opennebula.io/u/atodorov_storpool)\ **Post date:** [May 12, 2017, 1:47pm UTC](https://forum.opennebula.io/t/is-there-a-feature-to-change-the-way-hypervisor-nodes-refer-to-the-frontend/4265/4 "2017-05-12T13:47:43Z")
Hi, AFAIK the monitoring in the hypervisors is managed by the active front-end. So in your case the second front-end should restart the monitoring pointing the opennebula’s collectd service on the hypervisors to it’s own IP daddres. If I am not wrong there was a bug related to this case and the temp solution is to kill the collectd process on the HVs and reload/restart the monitoring. You should digh here in the forum for the description of the problem and the proposed solution. Best Regards, Anton Todorov ---
**Author:** ![wind0204](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/wind0204/32/5182_2.png) [@wind0204](https://forum.opennebula.io/u/wind0204)\ **Post date:** [May 13, 2017, 6:24am UTC](https://forum.opennebula.io/t/is-there-a-feature-to-change-the-way-hypervisor-nodes-refer-to-the-frontend/4265/5 "2017-05-13T06:24:51Z")
Thank you so much, Anton. Though I just found out that OpenNebula developers are working on native high availability feature in oned itself which is easy to set up and smooth in recovery phase. ( I read the April OpenNebula newsletter just now on May 13 haha ) I wonder how long it would take finishing the tests and releasing it publicly. does anyone have an idea? Best Regards, Gunwoo Gim ---
**Author:** ![atodorov\_storpool](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/atodorov_storpool/32/5327_2.png) [@atodorov\_storpool](https://forum.opennebula.io/u/atodorov_storpool)\ **Post date:** [May 13, 2017, 1:28pm UTC](https://forum.opennebula.io/t/is-there-a-feature-to-change-the-way-hypervisor-nodes-refer-to-the-frontend/4265/6 "2017-05-13T13:28:01Z")
AFAIK first beta should be released any moment - the developers are pushing the feature branches to the master branch and resolving the merging conflicts though. Best Regards, Anton Todorov