search

bilelmsekni / OpenStack-Folsom-Install-guide

A full installation guide for OpenStack Folsom with Quantum
161 stars 136 forks source link

Single-Interface Server #3

Closed ChristianKniep closed 12 years ago

ChristianKniep commented 12 years ago

Hey there,

I tried to install the howto on a server with just one interface (and an alias eth0:0). You used three interfaces in the same subnet, why is that?

Wouldn't it be better to have an private interface eth0:192.168.0/24, an host-only interface eth0:0:172.16/16 and an optional external interface eth1:10.10/16.

If I understand this 'cloud'-thingy right, that would be my aim. :)

Cheers Christian

bilelmsekni commented 12 years ago

Hi,

Sorry for replying back a bit late, i was adding your reboot note to the guide :)

Well, you see each NIC has a specific role

eth0 is for management network a.k.a communication between OpenStack components such as keystone, nova,...etc eth1 is for internal network a.k.a VM communication eth2 is for externel network a.k.a enabling VM to access the internet

You can see a more details here .

Your idea is completely correct when it comes to interfaces types (private, host only and external) but i would rather have three NICs instead of aliases because i simply don't trust them :)

AnyWay, there are a lot of networks usecases today thanks to the quantum project ( look here ) where you can use two NICs instead of three but i still don't have the configurations for that yet .

If you manage to get another quantum configuration using aliases , will you be kind and share it as a contributor to this guide ?

----- Mail original -----

De: "Christian Kniep" notifications@github.com À: "mseknibilel/OpenStack-Folsom-Install-guide" OpenStack-Folsom-Install-guide@noreply.github.com Envoyé: Mardi 16 Octobre 2012 22:05:15 Objet: {Disarmed} [OpenStack-Folsom-Install-guide] Single-Interface Server (#3)

Hey there, I tried to install the howto on a server with just one interface (and an alias eth0:0). You used three interfaces in the same subnet, why is that? Wouldn't it be better to have an private interface eth0:192.168.0/24, an host-only interface eth0:0:172.16/16 and an optional external interface eth1:10.10/16. If I understand this 'cloud'-thingy right, that would be my aim. :) Cheers Christian — Reply to this email directly or view it on GitHub . Web Bug from https://github.com/notifications/beacon/J6T91GIPIyhU-8ti4GCGPxht3OBfifWKdsC3eOhaLrWEc_N91h4reIdTm_gl62Wa.gif

mariusandra commented 12 years ago

Hey,

I have a similar problem. I'm renting a server from hetzner.de and they only give me one eth0 to play with. No matter how many different configurations I've tried, I can't manage to connect to my hosts.

Also I have a /28 subnet that's also coming in through eth0.

How should I set up my configuration for such a scenario?

Marius

bilelmsekni commented 12 years ago

Hi Marius,

Well the good thing about your scenario is that you have /28 subnet but the bad thing is that you have only one NIC eth0. This is depracated even in the last OpenStack Essex version since the separation between VM Network and management Network was always recommended.

I suggest that you try to realise this usecase :

These are a couple of hints to do so (i asked the question and someone was kind enough to reply) but i haven't tested it yet.

Hi, quantum.conf: core_plugin = quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 ovs_quantum_plugin.ini: network_vlan_ranges = physnet1 enable_tunneling = False bridge_mappings = physnet1:br-eth0

To create a shared provider network: quantum net-create sharednet1 --shared --provider:network_type flat --provider:physical_network physnet1

Before we can run, create br-eth0: sudo ovs-vsctl add-br br-eth0 sudo ovs-vsctl add-port br-eth0 eth0

we don't need br-ex since we don't use router and floatingip

and br-tun since we don't use GRE.

If you manage to pull this out, don't forget to share it with us :)

Cheers.

----- Mail original -----

De: "Marius Andra" notifications@github.com À: "mseknibilel/OpenStack-Folsom-Install-guide" OpenStack-Folsom-Install-guide@noreply.github.com Cc: "SkiBLE" bilel.msekni@telecom-sudparis.eu Envoyé: Mercredi 17 Octobre 2012 15:07:27 Objet: {Disarmed} Re: [OpenStack-Folsom-Install-guide] Single-Interface Server (#3)

Hey, I have a similar problem. I'm renting a server from hetzner.de and they only give me one eth0 to play with. No matter how many different configurations I've tried, I can't manage to connect to my hosts. Also I have a /28 subnet that's also coming in through eth0. How should I set up my configuration for such a scenario? Marius — Reply to this email directly or view it on GitHub . Web Bug from https://github.com/notifications/beacon/J6T91GIPIyhU-8ti4GCGPxht3OBfifWKdsC3eOhaLrWEc_N91h4reIdTm_gl62Wa.gif

mariusandra commented 12 years ago

Hey,

Unfortunately running "sudo ovs-vsctl add-port br-eth0 eth0" kills the connection and I must use the rescue system delete the conf.db file from /etc/openvswitch to get ssh access again.

I tried creating a virtual interface eth0:2 for the subnet and using eth0:2 instead of eth0 in the bridge, but that didn't help.

From the logs on creating instances I read that br-int was missing, so I created it. Still no luck. No the instances won't even start.

What I'd like to achieve in the end is a simple system where:

1) OpenStack is running in all its glory 2) I have some virtual IPs that get assigned to the instances and that I can access from inside the server (and from the instances) 3) I have a list of public floating IPs that I can assign to the servers as needed.

I tried using the libvirt virtual bridge for #2, but no luck.

I realize there's something simple that I'm missing, but I can't figure out what :-).

Marius

bilelmsekni commented 12 years ago

Hey,

I am sorry to hear that. I will try to test the scenario on my testing machine and try to find out a solution. My best advice for you is to abandon quantum and try to use nova-network. With nova network, you can run OpenStack with one single NIC ;).

----- Mail original -----

De: "Marius Andra" notifications@github.com À: "mseknibilel/OpenStack-Folsom-Install-guide" OpenStack-Folsom-Install-guide@noreply.github.com Cc: "SkiBLE" bilel.msekni@telecom-sudparis.eu Envoyé: Mercredi 17 Octobre 2012 17:04:52 Objet: {Disarmed} Re: [OpenStack-Folsom-Install-guide] Single-Interface Server (#3)

Hey, Unfortunately running "sudo ovs-vsctl add-port br-eth0 eth0" kills the connection and I must use the rescue system delete the conf.db file from /etc/openvswitch to get ssh access again. I tried creating a virtual interface eth0:2 for the subnet and using eth0:2 instead of eth0 in the bridge, but that didn't help. From the logs on creating instances I read that br-int was missing, so I created it. Still no luck. No the instances won't even start. What I'd like to achieve in the end is a simple system where: 1) OpenStack is running in all its glory 2) I have some virtual IPs that get assigned to the instances and that I can access from inside the server (and from the instances) 3) I have a list of public floating IPs that I can assign to the servers as needed. I tried using the libvirt virtual bridge for #2 , but no luck. I realize there's something simple that I'm missing, but I can't figure out what :-). Marius — Reply to this email directly or view it on GitHub . Web Bug from https://github.com/notifications/beacon/J6T91GIPIyhU-8ti4GCGPxht3OBfifWKdsC3eOhaLrWEc_N91h4reIdTm_gl62Wa.gif

ChristianKniep commented 12 years ago

Hi there,

I will try the installation within an VirtualBox to play around. By the way, in your howto I only see the NIC .232, where come the others in play?

bilelmsekni commented 12 years ago

Hi,

All is indicated when i created the bridges in the OpenVSwitch:

br-int will be used for integration

ovs-vsctl add-br br-int

br-eth1 will be used for VM communication

ovs-vsctl add-br br-eth1 ovs-vsctl add-port br-eth1 eth1

br-ex will be used to ensure access to VM from the outside world (a.k.a internet)

ovs-vsctl add-br br-ex ovs-vsctl add-port br-ex eth2 ================================================= ----- Mail original -----

De: "Christian Kniep" notifications@github.com À: "mseknibilel/OpenStack-Folsom-Install-guide" OpenStack-Folsom-Install-guide@noreply.github.com Cc: "SkiBLE" bilel.msekni@telecom-sudparis.eu Envoyé: Mercredi 17 Octobre 2012 18:14:32 Objet: {Disarmed} Re: [OpenStack-Folsom-Install-guide] Single-Interface Server (#3)

Hi there, I will try the installation within an VirtualBox to play around. By the way, in your howto I only see the NIC .232, where come the others in play? — Reply to this email directly or view it on GitHub . Web Bug from https://github.com/notifications/beacon/I1T5EjfDb5OWgQ2B_759LW6u0j2E9e1Nc99YbVJhevi779z0WFcmNy0wlnqgig7J.gif

bilelmsekni commented 12 years ago

Hi to all,

I have just updated the guide to multi node install and i believe you can do it now with just one NIC

kylebrandt commented 12 years ago

Would still like to know how to do this on a single nic/node install. I end up in the same position where when trying to add the port "sudo ovs-vsctl add-port br-eth0 eth0" I lose the connection to the box.

mariusandra commented 12 years ago

Hey, in the end after a few tries I managed to working with only one node.

However I skipped quantum altogether and used nova-network instead. There were some install scripts around that I modified with my own IP settings to get it to work.

I can try to dig it up tomorrow and give you some information about what I did.

bilelmsekni commented 12 years ago

Hi kyle !

Sorry couldn't answer back to you, i was not at the office :) i will investigate more in the volume problem but please make sure that cinder-volume volume group already exists because it disappears after a simple reboot !

for the simple NIC/Node i have to say it's a bit hard to do so ! may be you can be inspired by my milestone branch otherwise try to install Folsom inside VMs in your single node, that seems most appropriate solution. Once you do so, you can try to narrow down the need of NICs to one !

Best regards

----- Mail original -----

De: "kylebrandt" notifications@github.com À: "mseknibilel/OpenStack-Folsom-Install-guide" OpenStack-Folsom-Install-guide@noreply.github.com Cc: "SkiBLE" bilel.msekni@telecom-sudparis.eu Envoyé: Vendredi 9 Novembre 2012 19:23:23 Objet: {Disarmed} Re: [OpenStack-Folsom-Install-guide] Single-Interface Server (#3)

Would still like to know how to do this on a single nic/node install. I end up in the same position where when trying to add the port "sudo ovs-vsctl add-port br-eth0 eth0" I lose the connection to the box. — Reply to this email directly or view it on GitHub . Web Bug from https://github.com/notifications/beacon/J6T91GIPIyhU-8ti4GCGPxht3OBfifWKdsC3eOhaLrWEc_N91h4reIdTm_gl62Wa.gif

bilelmsekni commented 12 years ago

Hi Marius,

I am pretty sure that nova-network can be done on a single node but today's topic is how to get quantum ! It's a great project but the deployment is just a nightmare !

Cheers

----- Mail original -----

De: "Marius Andra" notifications@github.com À: "mseknibilel/OpenStack-Folsom-Install-guide" OpenStack-Folsom-Install-guide@noreply.github.com Cc: "SkiBLE" bilel.msekni@telecom-sudparis.eu Envoyé: Vendredi 9 Novembre 2012 19:38:21 Objet: {Disarmed} Re: [OpenStack-Folsom-Install-guide] Single-Interface Server (#3)

Hey, in the end after a few tries I managed to working with only one node. However I skipped quantum altogether and used nova-network instead. There were some install scripts around that I modified with my own IP settings to get it to work. I can try to dig it up tomorrow and give you some information about what I did. — Reply to this email directly or view it on GitHub . Web Bug from https://github.com/notifications/beacon/I1T5EjfDb5OWgQ2B_759LUqTZ2BaXpmjQBErwbFKRAS0XQzgRm9gS7fNi4pQ0reu.gif