[Openstack] Per host floating ip

Alessandro Tagliapietra tagliapietra.alessandro at gmail.com
Sat Jul 7 11:26:23 UTC 2012


I'm on other tasks actually but as soon as i get everything working i'll send a msg to the list with blog post with my tutorial for sure.

Regards

Il giorno 07/lug/2012, alle ore 12:19, Marnus van Niekerk ha scritto:

> I have tried gluster for live migration but could net get it working.  Please post back here if get that working.
> Instances ran fine with /var/lib/nova/instances on gluster, but live migration would change vm state to migrating and then back to running but still have it running where it was without any errors in the logs.
> 
> M
> 
> On Saturday, 7 July 2012, Alessandro Tagliapietra <tagliapietra.alessandro at gmail.com> wrote:
> > I'm currently building up, i did a test setup with 3 machines and it worked.
> > Now i'm doing it again with secure passwords, firewall etc.
> > Btw, i just bought 3 EX 4 servers with a private lan between them using the switch + additional nic option they provide.
> >
> > I was thinking that another solution would be to use failover ip and when i assign an ip to an instance a custom hook calls the hetzner api to change the routing to point the ip to the server which is running the vm.
> >
> > Next step would be to use a shared fs like gluster for vm HA.
> >
> > I was thinking to make a blog post as soon as i get everything working to share how i did the setup.
> >
> > Regards
> >
> > Il giorno 06/lug/2012, alle ore 23:45, Michael Grosser ha scritto:
> >
> >> Sounds like a solution, but a manual one. A more automatic way would
> >> be great I reckon.
> >>
> >> On Fri, Jul 6, 2012 at 7:00 PM, Marnus van Niekerk <m at mjvn.net> wrote:
> >>> I have limited knowledge of OpenStack, but I host many servers with Hetzner
> >>> and know their infrastructure well.
> >>>
> >>> Since nova allows you to assign specific floating IPs to specific instances
> >>> you could do the following.
> >>> Create a floating range include all of the IPs Hetzner has given you.
> >>> Then just associate the IP from the underlying host with a VM running on it
> >>> that host using euca-associate-address.
> >>>
> >>> On 06/07/2012 18:17, Michael Grosser wrote:
> >>>
> >>> Hey,
> >>>
> >>> I would love to hear more on your setup at hetzner, I was looking to
> >>> setup openstack there myself, but I didn't see a solution for the per
> >>> server ip issue.
> >>> How many machines do you use?
> >>> How did you set it up?
> >>> Do you use only nova or swift too?
> >>>
> >>> I would love to get more insight.
> >>>
> >>> Thanks for taking the time
> >>> Cheers Michael
> >>>
> >>> On Fri, Jul 6, 2012 at 12:24 PM, Alessandro Tagliapietra
> >>> <tagliapietra.alessandro at gmail.com> wrote:
> >>>
> >>> Hello guys, i've some servers at hetzner,
> >>> i've actually installed essex on those and they're working fine, the step
> >>> i'm missing is that hetzner gives you additional ip fixed to one host or
> >>> failover ip that i can move to one server to another with the api.
> >>> What i want is to assign floating ip to vm, depending on which host the vm
> >>> is running or use a create hook to move the failover ip to the host which is
> >>> running the vm. Is it possible in some way?
> >>>
> >>> Best Regards
> >>> _______________________________________________
> >>> Mailing list: https://launchpad.net/~openstack
> >>> Post to     : openstack at lists.launchpad.net
> >>> Unsubscribe : https://launchpad.net/~openstack
> >>> More help   : https://help.launchpad.net/ListHelp
> >>>
> >>> _______________________________________________
> >>> Mailing list: https://launchpad.net/~openstack
> >>> Post to     : openstack at lists.launchpad.net
> >>> Unsubscribe : https://launchpad.net/~openstack
> >>> More help   : https://help.launchpad.net/ListHelp
> >>>
> >>>
> >>>
> >
> >





More information about the Openstack mailing list