Hi,
In
http://docs.opennebula.org/4.8/advanced_administration/application_insight/onegate_usage.html#onegate-usage
the example is incorrect:
curl -X PUT $ONEGATE_ENDPOINT
should be
curl -X PUT $ONEGATE_ENDPOINT/vm
Regards,
Rolandas
___
Users
I also interested on this. The current practice that we are doing is
shutdown/delete the VM, go to template and add the CDROM device and instantiate
VM. By doing this we will have new VM ID and lose the accountability of old VM
ID info
--
Regards,
Anandharaj
From: Users
Your colleague is probably correct.
Have you verified that each of the ports on your physical switch, which the
hypervisors are plugged into, have those port settings, set to trunk and
allow/forward all VLANs?
Robert Foote
bpsNode
www.bpsnode.com
From: Users
Thanks for the quick reply!
I have verified that all of these ports are set to untagged. So this is
essentially wrong as I see ;-)
Do I need to configure anything else on my hypervisor interfaces or is it
just the switch I need to touch?
Thanks!
Christain
Von: Robert Foote
If everything else is working as you mentioned before, I would think that
you would only need to set those ports to trunk and allow all vlans to pass
through. After that, I would imagine youd be able to separate VMs on the
same VLAN over multiple hosts, and ping between them.
That should be
Thanks! That was the solution. Everything works fine now!
Von: Robert Foote [mailto:rfo...@bpsnode.com]
Gesendet: Donnerstag, 4. September 2014 16:52
An: Hüning, Christian; Users@lists.opennebula.org
Betreff: RE: [one-users] Isolated VMs on different Hosts can't communicate -
ONE 4.8, OVS
