[one-users] OpenNebula and The Foreman integration
Dear OpenNebula users, In case you missed it, we want to highlight the integration between OpenNebula and The Foreman carried by our partners, Netways. With this integration is possible to deploy virtual machines within OpenNebula using the Foreman interface which configures DNS,DHCP,PXE,Puppet and so on as well. The functionality is covered by using and extending the ruby fog library. The pull requests for both The Foreman and fog project can be found on GitHub: - https://github.com/theforeman/foreman/pull/1443 - https://github.com/fog/fog/pull/2919 You can find a quick demo can be found here: https://blog.netways.de/2014/05/13/videoblog-unser-foreman-opennebula-setup/ Let us know want you think about the integration, would it be useful in your infrastructure? - The OpenNebula Team Link to the original post: http://opennebula.org/foreman-integration/ -- OpenNebula - Flexible Enterprise Cloud Made Simple -- Constantino Vázquez Blanco, PhD, MSc Senior Infrastructure Architect at C12G Labs www.c12g.com | @C12G | es.linkedin.com/in/tinova -- Confidentiality Warning: The information contained in this e-mail and any accompanying documents, unless otherwise expressly indicated, is confidential and privileged, and is intended solely for the person and/or entity to whom it is addressed (i.e. those identified in the To and cc box). They are the property of C12G Labs S.L.. Unauthorized distribution, review, use, disclosure, or copying of this communication, or any part thereof, is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify us immediately by e-mail at ab...@c12g.com and delete the e-mail and attachments and any copy from your system. C12G thanks you for your cooperation. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Gratuitous ARP replies: VM live-migration without loss of IP connectivity
Thanks Stefan! Do you think it could be do this in the network scripts? Those script are executed in the node to prepare the node for a new machine or a migrated one. Does it make sense for newly created VMs? They take more to get the IP but it may also be good to tell the switch beforehand. Even if this does not make sense it is a nice candidate for an addon. Cheers On Wed, May 28, 2014 at 6:50 PM, Stefan Kooman ste...@bit.nl wrote: Hi List, In some larger cloud / network environments IPv4 connectivity issues may arise when VM's get (live-)migrated from one HOST to the other. The MAC address(es) of the Virtual Machine (VM) might still be mapped to the wrong port on switches/routers upstream from the switch the HOST is patched on. This might lead to IPv4 connectivity issues for the VM being migrated. This issue becomes escpecially noticable when the VM doesn't generate a lot of network traffic and/or the MAC address table timeout on the switch(es) is large. To overcome this issue I made a VM_HOOK and script(s) that run on the HOST when the hook is triggered [1]. It will execute a script that sends Gratuitous ARP replies (unsollicited ARP reply) on the virtual network interface(s) on behalf of the VM. These VM_HOOK and script(s) will work on a KVM/QEMU environment with OpenvSwitch. It should be fairly easy to adjust the scripts to support other enviroments (i.e. Xen with legacy bridging). Environments based on VMware with VM's that have vmware-tools installed are covered by VMware ESX. VMware will have the VM send gratuitous ARP replies as soon as the live-migration finishes. It does _not_ work for VM's without vmware-tools installed though. I hope one-grarp will be useful for some of you out there suffering from this issue. Gr. Stefan [1]: https://github.com/hydro-b/one-grarp P.s. In so called switched fabric networks the issue above might not occur because the fabric operates as one (logical) switch (like Brocade's Ethernet Fabric). -- | BIT BV http://www.bit.nl/Kamer van Koophandel 09090351 | GPG: 0xD14839C6 +31 318 648 688 / i...@bit.nl ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Javier Fontán Muiños Developer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | @OpenNebula | github.com/jfontan ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] [ BUG ] opennebula-sunstone-4.6.1-1.x86_64 : Unresponsive Updating Templates
Hello Mailing List, Preface, physical server information: Processor: Single E5-1650 v2 [ 6/12 @ 3.50 GHz / Ivy Bridge ] Storage: 2x 6TB HDD [ Local Storage via default data-stores ] Software types and versions installed: Operating System: Linux Distribution: Cent OS Version: 6.5 Architecture: x86_64 (64 bit) Kernel: 2.6.32-431.17.1.el6 opennebula-ruby-4.6.1-1.x86_64 opennebula-sunstone-4.6.1-1.x86_64 opennebula-node-kvm-4.6.1-1.x86_64 opennebula-common-4.6.1-1.x86_64 opennebula-4.6.1-1.x86_64 opennebula-server-4.6.1-1.x86_64 --- The actual issue: --- After creating a new SunStone + KVM Node configuration, as specified in your QuickStart documentation [ without NFS configuration, as both the frontend and backend are on the same server for testing. ] I have created the host machine and network in the CLI, then did the following: I attempted to update one of my existing templates, [ created via the following raw template data as imported into the SunStone via the second option. ] When I attempt to Update the template, the web interface stalls for some 10-60 seconds, other times it doesn't ever come up [ the template in wizard mode to edit. ] This issue is not seen with the CLI, so I know the issue is not a slow database. The default .sqlite database is being used. This issue was not seen in the previous version [4.6] , it appears new to [4.6.1] ; but I have not had this hardware before then, so I cannot confirm this. --- Steps to Reproduce: --- 1. Click on any template in SunStone 2. Click Update and wait... --- RAW Template Data [attached] --- NAME=CentOS-6.5 CONTEXT=[ NETWORK=YES, SSH_PUBLIC_KEY=$USER[SSH_PUBLIC_KEY] ] CPU=1.0 DISK=[ IMAGE=CentOS-6.5, DRIVER=qcow2, DEV_PREFIX=vd ] GRAPHICS=[ LISTEN=0.0.0.0, TYPE=vnc ] MEMORY=512 NIC=[ NETWORK=network ] OS=[ ARCH=x86_64 ] ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
