Re: [one-users] DISK 0: User 0 does not own an image with name
What I'd the output of : oneimage show 1 Sent from my Verizon Wireless 4G LTE smartphone Original message From: Juan José Fuentes juanjose.fuen...@sigmaaie.org Date: 05/29/2015 6:54 AM (GMT-06:00) To: users@lists.opennebula.org Subject: [one-users] DISK 0: User 0 does not own an image with name Hi, We’re getting an error when instantiating a template: $ onetemplate instantiate tplCentOS7 [TemplateInstantiate] Error allocating a new virtual machine. DISK 0: User 0 does not own an image with name: diskCentOS7 . Set IMAGE_UNAME or IMAGE_UID of owner in DISK. $ onetemplate show 1 TEMPLATE 1 INFORMATION ID : 1 NAME : tplCentOS7 USER : oneadmin GROUP : oneadmin REGISTER TIME : 05/29 12:17:28 PERMISSIONS OWNER : um- GROUP : --- OTHER : --- TEMPLATE CONTENTS CONTEXT=[ NETWORK=YES, SSH_PUBLIC_KEY=$USER[SSH_PUBLIC_KEY] ] CPU=1.0 DISK=[ IMAGE=diskCentOS7, IMAGE_ID=1, IMAGE_UID=0, IMAGE_UNAME=oneadmin ] GRAPHICS=[ LISTEN=0.0.0.0, TYPE=vnc ] MEMORY=512 NIC=[ NETWORK=private ] OS=[ ARCH=x86_64 ] SUNSTONE_CAPACITY_SELECT=YES SUNSTONE_NETWORK_SELECT=YES VCPU=1 Tail -f oned.log Fri May 29 13:50:49 2015 [Z0][ReM][D]: Req:7920 UID:0 TemplatePoolInfo invoked , -2, -1, -1 Fri May 29 13:50:49 2015 [Z0][ReM][D]: Req:7920 UID:0 TemplatePoolInfo result SUCCESS, VMTEMPLATE_POOLVM... Fri May 29 13:50:49 2015 [Z0][ReM][D]: Req:7376 UID:0 TemplateInfo invoked , 1 Fri May 29 13:50:49 2015 [Z0][ReM][D]: Req:7376 UID:0 TemplateInfo result SUCCESS, VMTEMPLATEID1/I... Fri May 29 13:50:49 2015 [Z0][ReM][D]: Req:2784 UID:0 TemplateInstantiate invoked , 1, , false, ... Fri May 29 13:50:50 2015 [Z0][ONE][E]: DISK 0: User 0 does not own an image with name: diskCentOS7 . Set IMAGE_UNAME or IMAGE_UID of owner in DISK. Fri May 29 13:50:50 2015 [Z0][ReM][E]: Req:2784 UID:0 TemplateInstantiate result FAILURE [TemplateInstantiate] Error allocating a new virtual machine. DISK 0: User 0 does not own an image with name: diskCentOS7 . Set IMAGE_UNAME or IMAGE_UID of owner in DISK. Kind regards, Jjf. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Opennebula + OpenVSwitch + FLoodlight with multiple hosts
The physical switch that the hosts are connected to, need to be configured as trunk ports, and allow trunking for all VLANS. Robert Foote Chief Technical Officer Phone | 1-800-611-8763 Ext. 201 www.bpsnode.com From: Users [mailto:users-boun...@lists.opennebula.org] On Behalf Of Jhon Masschelein Sent: Monday, October 20, 2014 11:27 AM To: users@lists.opennebula.org Subject: [one-users] Opennebula + OpenVSwitch + FLoodlight with multiple hosts Hi, I am trying to get OpenNebula to work using OVS + VLAN networking, but I cannot get VMs on different hosts to talk to each other. If I just configure the OVS bridge on the host, set up the OpenNebula virtual network as an OVS network and add the hosts using the OVS driver, everything works within a host. Any VMs running on that host can talk to each other. Also, the two hosts themselves can talk to each other using the ip address assigned to the OVS bridge device. But a vm on one host cannot ping a VM on the other host. A number of internet resources like http://openvswitch.org/support/config-cookbooks/vlan-configuration-cookbook/ would seem to indicate that this should work, but it does not, at least not for me. As a next step, I set up a Floodlight openflow controller. With the above setup, I assign the controller to the OVSwitches and almost immediately, all running VMs are able to talk to each other. However, any VM's I start after the Floodlight controller has started, are again confined to their respective hosts. A restart of the Floodlght controller fixes it again: all VM's (old and new) are able to talk to each other. Of course, restarting floodlight every time does not seem to be the right way of doing this. I also reconfigured floodlight to learning switch mode but that did not change anything. I do see the ports added to the switches when the new VMs come up, but nothing more. Has anybody been able to get this setup to work? Is an openflow controller like floodlight required to get this to work reliably? FYI; the floodlight controller is not controlling the switch that is sitting between the hosts. I am not sure if this is even relevant since the web page I mentioned above indicates it should all work without a controller. If it can be made to work without the need for an external controller like floodlight, that would be totally acceptable. If anyone has been able to make a OVS setup work, I would be very grateful for any information you can pass my way. Best regards, Jhon Masschelein ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Isolated VMs on different Hosts can't communicate - ONE 4.8, OVS 2.0.1
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 [mailto:users-boun...@lists.opennebula.org] On Behalf Of Hüning, Christian Sent: Thursday, September 04, 2014 9:27 AM To: Users@lists.opennebula.org Subject: [one-users] Isolated VMs on different Hosts can't communicate - ONE 4.8, OVS 2.0.1 Hi there, I have a cluster of 5 hosts running with openNebula 4.8 and just recently configured OpenvSwitch on all these nodes. Networking is working just fine. This holds also true for VLAN isolation, but just as long as the VMs belonging to the isolated Virtual Network reside on the same physical host. When I move these VMs to different hosts, they cant communicate with each other anymore. Non-isolated nodes can communicate to everywhere without problems. Is that intentional? I chose OpenVswitch because the ONE docs say it requires no support from the switch hardware (or more specifically it says 802.1Q would require support). A colleague suggested it might have to do with the switch not forwarding the tagged packets from Open vSwitch. Can that be the cause? Does OVS even tag the packets? Heres my environment: OpenNebula 4.8 Open vSwitch 2.0.1 Cisco Switch Host OS: Ubuntu Server 14.04 LTS (latest patches) Output from ovs-vsctl show: Bridge br0 Port vnet3 Interface vnet3 Port bond0 Interface bond0 Port vnet1 Interface vnet1 Port vnet2 Interface vnet2 Port vnet5 Interface vnet5 Port br0 Interface br0 type: internal Port vnet0 Interface vnet0 Port vnet4 Interface vnet4 ovs_version: 2.0.1 Where br0 is my ovs bridge interface which has the external real IP address configured and bond0 is a link aggregated dual Gbit interface which is the port for br0 I would greatly appreciate some suggestions or ideas on this, since I am a bit lost. Cheers, Christian --- Christian Hüning, BSc. Fakultät Technik und Informatik, Department Informatik Berliner Tor 7 20099 Hamburg Web: http://www.mars-group.org --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Isolated VMs on different Hosts can't communicate - ONE 4.8, OVS 2.0.1
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 all you need to do at this point. Robert Foote bpsNode www.bpsnode.com From: Hüning, Christian [mailto:christian.huen...@haw-hamburg.de] Sent: Thursday, September 04, 2014 9:43 AM To: Robert Foote; Users@lists.opennebula.org Subject: AW: [one-users] Isolated VMs on different Hosts can't communicate - ONE 4.8, OVS 2.0.1 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 [mailto:rfo...@bpsnode.com] Gesendet: Donnerstag, 4. September 2014 16:40 An: Hüning, Christian; Users@lists.opennebula.org mailto:Users@lists.opennebula.org Betreff: RE: [one-users] Isolated VMs on different Hosts can't communicate - ONE 4.8, OVS 2.0.1 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 http://www.bpsnode.com From: Users [mailto:users-boun...@lists.opennebula.org] On Behalf Of Hüning, Christian Sent: Thursday, September 04, 2014 9:27 AM To: Users@lists.opennebula.org mailto:Users@lists.opennebula.org Subject: [one-users] Isolated VMs on different Hosts can't communicate - ONE 4.8, OVS 2.0.1 Hi there, I have a cluster of 5 hosts running with openNebula 4.8 and just recently configured OpenvSwitch on all these nodes. Networking is working just fine. This holds also true for VLAN isolation, but just as long as the VMs belonging to the isolated Virtual Network reside on the same physical host. When I move these VMs to different hosts, they cant communicate with each other anymore. Non-isolated nodes can communicate to everywhere without problems. Is that intentional? I chose OpenVswitch because the ONE docs say it requires no support from the switch hardware (or more specifically it says 802.1Q would require support). A colleague suggested it might have to do with the switch not forwarding the tagged packets from Open vSwitch. Can that be the cause? Does OVS even tag the packets? Heres my environment: OpenNebula 4.8 Open vSwitch 2.0.1 Cisco Switch Host OS: Ubuntu Server 14.04 LTS (latest patches) Output from ovs-vsctl show: Bridge br0 Port vnet3 Interface vnet3 Port bond0 Interface bond0 Port vnet1 Interface vnet1 Port vnet2 Interface vnet2 Port vnet5 Interface vnet5 Port br0 Interface br0 type: internal Port vnet0 Interface vnet0 Port vnet4 Interface vnet4 ovs_version: 2.0.1 Where br0 is my ovs bridge interface which has the external real IP address configured and bond0 is a link aggregated dual Gbit interface which is the port for br0 I would greatly appreciate some suggestions or ideas on this, since I am a bit lost. Cheers, Christian --- Christian Hüning, BSc. Fakultät Technik und Informatik, Department Informatik Berliner Tor 7 20099 Hamburg Web: http://www.mars-group.org _ http://www.avast.com/ This email is free from viruses and malware because avast! Antivirus http://www.avast.com/ protection is active. --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Automatic recover from hardware failure
I hope this particular feature is coming soon, as this is a standard ‘cloud’ feature for High Availability, and automatic failover. Robert Foote bpsNode www.bpsnode.com From: Users [mailto:users-boun...@lists.opennebula.org] On Behalf Of Carlos Martín Sánchez Sent: Monday, September 01, 2014 10:46 AM To: Sander Klein Cc: users Subject: Re: [one-users] Automatic recover from hardware failure Hi, On Thu, Aug 14, 2014 at 8:36 PM, Sander Klein roe...@roedie.nl mailto:roe...@roedie.nl wrote: The delete-recreate action will create a new VM from the original template. This means that the VM will have a new ID, IP, and clean disks. We are working on a new mechanism for hosts with shared storage, to migrate the failed VM to a new host keeping the current IPs, disk state, etc. Is there an ETA on this new mechanism? I just ran into the same problem today in my test setup. I can't say when it will be ready. It's not a patch that you can apply, the changes are made in the core and the scheduler, so you will need to wait for the next OpenNebula release. Regards. -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org http://www.opennebula.org/ | cmar...@opennebula.org mailto:cmar...@opennebula.org | @OpenNebula http://twitter.com/opennebula --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] IP Addressing
Hi All: I have some VMs in my opennebula cloud that need to use about 5 static IP addresses, that will not be leased to them through OpenNebula, they will be in use manually due to the need for VRRP on them. However, those IP addresses, are part of a VNET that I've already established and have leases coming out of, but those specific IPs have not yet been leased out by opennebula. Is there a way I can tell opennebula not to use those specific IP addresses when future VMs are created on that specific VNET? Thanks, Robert Foote bpsNode www.bpsnode.com --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] IP Addressing
Perfect, Thanks! Robert Foote bpsNode www.bpsnode.com -Original Message- From: Stefan Kooman [mailto:ste...@bit.nl] Sent: Friday, August 29, 2014 8:49 AM To: Robert Foote Cc: users@lists.opennebula.org Subject: Re: [one-users] IP Addressing Quoting Robert Foote (rfo...@bpsnode.com): Hi All: I have some VMs in my opennebula cloud that need to use about 5 static IP addresses, that will not be leased to them through OpenNebula, they will be in use manually due to the need for VRRP on them. However, those IP addresses, are part of a VNET that I've already established and have leases coming out of, but those specific IPs have not yet been leased out by opennebula. Is there a way I can tell opennebula not to use those specific IP addresses when future VMs are created on that specific VNET? Jep. In ONE you cane put leases on HOLD. Just go to leases of the specific VNET, add an IP and click Hold IP. On the cli you would do something like this: onevnet hold vnetid/vnetname ip. In ONE 4.8 onwards you can also make a reservation: onevnet reserve vnetid/vnetname. Gr. Stefan -- | BIT BV http://www.bit.nl/Kamer van Koophandel 09090351 | GPG: 0xD14839C6 +31 318 648 688 / i...@bit.nl --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] How to create a non-volatile disk to attach to VM
Hello: I am trying to figure out how to create a Non-volatile disk to attach to a VM. From what I can see, I can only attach volatile disks to VM's. I need to be able to create a 2TB blank disk, that can then be attached to a customers VM image. Is this possible? Thanks, Robert Foote bpsNode www.bpsnode.com --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
