Open Stack

Hi Sebastian,

The commands are nearly identical - just replace quantum with nova!

Although, it sounds like you already have floating IPs being allocated
randomly.

That could be one of two things - either you have
auto_assign_floatingip=True in your configuration, or you misunderstand the
difference between fixed and floating ips.

When you boot an instance, does it get a private or public IP? And - when
you ran the network-create command, what IP range did you use?

Kiall
On Oct 30, 2012 9:26 AM, "Sébastien Han" <han.sebastien at gmail.com> wrote:

> @Kiall, if it does, tell us more about it please.
>
>
> On Tue, Oct 30, 2012 at 10:19 AM, Kiall Mac Innes <kiall at managedit.ie>
> wrote:
> > I'm fairly confident that quantum is not a requirement for this.
> >
> > Nova's in-built networking supports exactly this since as long ago as I
> can
> > remember.
> >
> > Thanks,
> > Kiall
> >
> > On Oct 30, 2012 9:04 AM, "Emilien Macchi" <emilien at enovance.com> wrote:
> >>
> >> Hello Sebastien,
> >>
> >>
> >> What you can do today is to choose manually which floating IP you need
> to
> >> associate with a specific instance.
> >> You need to run OpenStack Folsom + Quantum.
> >>
> >> First, you need to create Floating IP pool(s) from Quantum CLI, and
> after
> >> that, the tenant is able to associate this IP to a private instance :
> >>
> >> quantum floatingip-create ext_net
> >>
> >> quantum floatingip-associate $FLOATING_ID $PORT_ID
> >>
> >> More informations about Networking configuration with Quantum CLI here :
> >>
> >>
> http://docs.openstack.org/trunk/openstack-network/admin/content/demo_logical_network_config.html
> >>
> >>
> >> Cheers ;-)
> >>
> >>
> >> Emilien Macchi
> >> ----------------------------------------------------
> >> // eNovance Inc.              http://enovance.com
> >> // ✉ emilien at enovance.com     ☎ +33 (0)1 49 70 99 80
> >> // 10 rue de la Victoire 75009 Paris
> >>
> >> ________________________________
> >> De: "Sébastien Han" <han.sebastien at gmail.com>
> >> À: "Openstack" <openstack at lists.launchpad.net>
> >> Envoyé: Lundi 29 Octobre 2012 17:25:47
> >> Objet: [Openstack] Allocate specific floating IP to an instance
> >>
> >> Hi Stacker,
> >>
> >> I know OpenStack is not designed that way and I don't think it's
> >> possible (or maybe I misses something :)) but I was wondering if there
> >> is any simple workaround to choose a specific floating IP to allocate.
> >> In other words, don't give me a random or N+1 next floating IP
> >> available but let me decide which floating IP I want to assign to my
> >> instance. It doesn't make sense in a public cloud but it does for a
> >> corporate/private cloud. It would be nice to have :)
> >>
> >> Thanks in advance.
> >>
> >> Cheers!
> >>
> >> _______________________________________________
> >> 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
> >>
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121030/c430797f/attachment.html>