Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: OpenStack: Operators

Multi nic configuration documentation

 

 

OpenStack operators RSS feed   Index | Next | Previous | View Threaded


janis.gengeris at gmail

Aug 10, 2012, 12:38 AM

Post #1 of 3 (379 views)
Permalink
Multi nic configuration documentation

Hi all,

I would like to test the multi nic setup for VMs. The only official
documentation that I can find is here
http://docs.openstack.org/essex/openstack-compute/admin/content/using-multi-nics.html.
Although it has lots of nice graphics, but lacks description of how to
configure it.

I've seen on the list that people are using or trying to use this setup,
maybe someone could share knowledge on how to configure the most basic
setup. Also I would like to configure VMs so that the public IP is assigned
to separate VM interface and visible with ifconfig from inside of the VM.
Is this possible to do with FlatDHCP and without Quantum?

Regards,
--janis


joe.topjian at cybera

Aug 11, 2012, 10:26 PM

Post #2 of 3 (369 views)
Permalink
Re: Multi nic configuration documentation [In reply to]

Hi Janis,

The command to enable multi nic is in the link you gave:

nova-manage network create --fixed_range_v4=20.20.0.0/24 --num_networks=1
--network_size=256 --label=test --project=$your-project

You most likely already used the "nova-manage network create" command to
create a network when initially installing OpenStack. This command just
creates a second network with a different subnet and ties it to one
particular project (--project).

That's all that is needed. When you launch a new instance in that project,
the instance will automatically have two NICs. You will most likely have to
manually enable the interface inside the instance as most cloud images are
only configured for one interface.

Regarding your question about public ips: to my knowledge there is not a
way to assign a public IP directly on the instance. It is always hosted on
the server running nova-network.

Thanks,
Joe

On Fri, Aug 10, 2012 at 1:38 AM, Jānis Ģeņģeris <janis.gengeris [at] gmail>wrote:

> Hi all,
>
> I would like to test the multi nic setup for VMs. The only official
> documentation that I can find is here
> http://docs.openstack.org/essex/openstack-compute/admin/content/using-multi-nics.html.
> Although it has lots of nice graphics, but lacks description of how to
> configure it.
>
> I've seen on the list that people are using or trying to use this setup,
> maybe someone could share knowledge on how to configure the most basic
> setup. Also I would like to configure VMs so that the public IP is assigned
> to separate VM interface and visible with ifconfig from inside of the VM.
> Is this possible to do with FlatDHCP and without Quantum?
>
> Regards,
> --janis
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators [at] lists
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>


--
Joe Topjian
Systems Administrator
Cybera Inc.

www.cybera.ca

Cybera is a not-for-profit organization that works to spur and support
innovation, for the economic benefit of Alberta, through the use
of cyberinfrastructure.


jon at jonproulx

Aug 12, 2012, 3:11 PM

Post #3 of 3 (351 views)
Permalink
Re: Multi nic configuration documentation [In reply to]

On Fri, Aug 10, 2012 at 3:38 AM, Jānis Ģeņģeris
<janis.gengeris [at] gmail> wrote:
> Also I would like to configure VMs so that the public IP is assigned
> to separate VM interface and visible with ifconfig from inside of the VM. Is
> this possible to do with FlatDHCP and without Quantum?

As Joe said, no...but while the public IP isn't available via ifconfig
but you can get it from the metadata service (provided that's
configured correctly)[1], for example from within the vm:

curl http://169.254.169.254/latest/meta-data/public-ipv4

I'm not 100% sure what this shows with multiple nics as I only use a
single nic on my vms.

You could possibly code something up if you had openstack credentials
within the vm that it would check its instance ID from the metadata
service (curl http://169.254.169.254/latest/meta-data/instance-id)
then use euca2ools (metadata give an ec2 compatible interface so id
will be wrong for use with nova client) to assign the ip it wants to
itself, but this is definitely not a common usage. Typically you use
the same tool to assing the public IP as you did to launch the
instance (python-novaclient, euca2ools, Horizon Dashboard web
interface, Hybridfox, or the API)

-Jon

[1] http://docs.openstack.org/essex/openstack-compute/admin/content/metadata-service.html

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

OpenStack operators RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.