[Openstack] Help about Quantum Conf
Hi, I have finished installing OpenStack Folsom but i am encountring a small issue about configuring Quantum. I would like to start the simplest scenario Flat Network http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_flat.html but i dont know how to configure my bridges (br-int, br-ex and br-tun) i have two NICs on each node ( primary eth0 and secondary eth1) If someone can show me the way, i will be very grateful since i will be writing a guide about it for future users. Thanks. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Help about Quantum Conf
Thanks sheng ! you are a life saver ;) Le 09/10/2012 10:29, gong yong sheng a écrit : 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. Regards, Yong Sheng Gong On 10/09/2012 03:29 PM, Bilel Msekni wrote: Hi, I have finished installing OpenStack Folsom but i am encountring a small issue about configuring Quantum. I would like to start the simplest scenario Flat Network http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_flat.html but i dont know how to configure my bridges (br-int, br-ex and br-tun) i have two NICs on each node ( primary eth0 and secondary eth1) If someone can show me the way, i will be very grateful since i will be writing a guide about it for future users. Thanks. ___ Mailing list:https://launchpad.net/~openstack Post to :openstack@lists.launchpad.net Unsubscribe :https://launchpad.net/~openstack More help :https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] No proper displau with Horizon
Good day everyone,
I have installed OpenStack Folsom successfully but i am experiencing a
wierd bug in the dashboard: It's not giving me any proper display.
This is the error log i got from apache, http://pastebin.com/P44Edku5
it seems like it is looking for an endpoint which are all there and
working fine.
P.S: I used this script to populate my database
===
create_endpoint () {
case $1 in
compute)
keystone endpoint-create --region $KEYSTONE_REGION --service-id $2
--publicurl 'http://'$MASTER':8774/v2/$(tenant_id)s' --adminurl
'http://'$MASTER':8774/v2/$(tenant_id)s' --internalurl
'http://'$MASTER':8774/v2/$(tenant_id)s'
;;
volume)
keystone endpoint-create --region $KEYSTONE_REGION --service-id $2
--publicurl 'http://'$MASTER':8776/v1/$(tenant_id)s' --adminurl
'http://'$MASTER':8776/v1/$(tenant_id)s' --internalurl
'http://'$MASTER':8776/v1/$(tenant_id)s'
;;
image)
keystone endpoint-create --region $KEYSTONE_REGION --service-id $2
--publicurl 'http://'$MASTER':9292/v2' --adminurl
'http://'$MASTER':9292/v2' --internalurl 'http://'$MASTER':9292/v2'
;;
object-store)
if [ $SWIFT_MASTER ]; then
keystone endpoint-create --region $KEYSTONE_REGION --service-id $2
--publicurl 'http://'$SWIFT_MASTER':8080/v1/AUTH_$(tenant_id)s'
--adminurl 'http://'$SWIFT_MASTER':8080/v1' --internalurl
'http://'$SWIFT_MASTER':8080/v1/AUTH_$(tenant_id)s'
else
keystone endpoint-create --region $KEYSTONE_REGION --service-id $2
--publicurl 'http://'$MASTER':8080/v1/AUTH_$(tenant_id)s' --adminurl
'http://'$MASTER':8080/v1' --internalurl
'http://'$MASTER':8080/v1/AUTH_$(tenant_id)s'
fi
;;
identity)
keystone endpoint-create --region $KEYSTONE_REGION --service-id $2
--publicurl 'http://'$MASTER':5000/v2.0' --adminurl
'http://'$MASTER':35357/v2.0' --internalurl 'http://'$MASTER':5000/v2.0'
;;
ec2)
keystone endpoint-create --region $KEYSTONE_REGION --service-id $2
--publicurl 'http://'$MASTER':8773/services/Cloud' --adminurl
'http://'$MASTER':8773/services/Admin' --internalurl
'http://'$MASTER':8773/services/Cloud'
;;
network)
keystone endpoint-create --region $KEYSTONE_REGION --service-id $2
--publicurl 'http://'$MASTER':9696/' --adminurl
'http://'$MASTER':9696/' --internalurl 'http://'$MASTER':9696/'
;;
esac
}
Please, i need some help
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] No proper displau with Horizon
Thanks for replying Dolph:
keystone service-list
+--+--+--+--+
|id| name | type |
description |
+--+--+--+--+
| 020a5c2b03074e89972202f3822fa95f | quantum | network | OpenStack
Networking service |
| 2b3d91dd9110493a92ea5eb7909d41cf | ec2| ec2| OpenStack EC2
service |
| 4ef30c360f4e4e0aaac9d1247dcaafe8 | cinder | volume | OpenStack
Volume Service |
| 776d3b71749f4711bf1c956ccfeb2728 | glance | image | OpenStack
Image Service|
| 9733c366161f4f7f8e8484fe702ee840 | keystone | identity | OpenStack
Identity |
| c6011214a82645fe97b4bbd64608ad9b | nova | compute | OpenStack
Compute Service |
+--+--+--+--+
keystone endpoint-list
+--+---+--+--+--+
|id| region |
publicurl | internalurl |
adminurl |
+--+---+--+--+--+
| 2febceec3f324755b0c9c7fe3ba2d29d | RegionOne |
http://x.x.x.x:9696/ | http://x.x.x.x:9696/ |
http://x.x.x.x:9696/ |
| 649d5e5b5cd8467c89b218b2adc29009 | RegionOne |
http://x.x.x.x:8774/v2/$(tenant_id)s |
http://x.x.x.x:8774/v2/$(tenant_id)s |
http://x.x.x.x:8774/v2/$(tenant_id)s |
| 7b25b6283dd4408d8c8f7541b9b9d2f0 | RegionOne |
http://x.x.x.x:5000/v2.0 | http://x.x.x.x:5000/v2.0 |
http://x.x.x.x:35357/v2.0 |
| 9ebfa2784d78425fa08a146aa27e786b | RegionOne |
http://x.x.x.x:9292/v2| http://x.x.x.x:9292/v2|
http://x.x.x.x:9292/v2|
| f321ae42d39d4d9a9d5e771be459f6ba | RegionOne |
http://x.x.x.x:8776/v1/$(tenant_id)s |
http://x.x.x.x:8776/v1/$(tenant_id)s |
http://x.x.x.x:8776/v1/$(tenant_id)s |
| f7ef924364614d91b49a589ca7719ce6 | RegionOne |
http://x.x.x.x:8773/services/Cloud |
http://x.x.x.x:8773/services/Cloud | http://x.x.x.x:8773/services/Admin |
+--+---+--+--+--+
x.x.x.x refers to my Host address :)
Le 08/10/2012 10:18, Dolph Mathews a écrit :
it seems like it is looking for an endpoint which are all there are
you sure? -- it looks like your service catalog is missing the
'identity' service entirely... can you paste the output of the
following two commands?:
$ keystone service-list
$ keystone endpoint-list
-Dolph
On Mon, Oct 8, 2012 at 2:59 AM, Bilel Msekni ski...@hotmail.fr
mailto:ski...@hotmail.fr wrote:
Good day everyone,
I have installed OpenStack Folsom successfully but i am
experiencing a wierd bug in the dashboard: It's not giving me any
proper display.
This is the error log i got from apache, http://pastebin.com/P44Edku5
it seems like it is looking for an endpoint which are all there
and working fine.
P.S: I used this script to populate my database
===
create_endpoint () {
case $1 in
compute)
keystone endpoint-create --region $KEYSTONE_REGION
--service-id $2 --publicurl
'http://'$MASTER':8774/v2/$(tenant_id)s' --adminurl
'http://'$MASTER':8774/v2/$(tenant_id)s' --internalurl
'http://'$MASTER':8774/v2/$(tenant_id)s'
;;
volume)
keystone endpoint-create --region $KEYSTONE_REGION
--service-id $2 --publicurl
'http://'$MASTER':8776/v1/$(tenant_id)s' --adminurl
'http://'$MASTER':8776/v1/$(tenant_id)s' --internalurl
'http://'$MASTER':8776/v1/$(tenant_id)s'
;;
image)
keystone endpoint-create --region $KEYSTONE_REGION
--service-id $2 --publicurl 'http://'$MASTER':9292/v2'
--adminurl 'http://'$MASTER':9292/v2' --internalurl
'http://'$MASTER':9292/v2'
;;
object-store)
if [ $SWIFT_MASTER ]; then
keystone endpoint-create --region $KEYSTONE_REGION --service-id $2
--publicurl 'http://'$SWIFT_MASTER':8080/v1/AUTH_$(tenant_id)s'
--adminurl 'http://'$SWIFT_MASTER':8080/v1' --internalurl
'http://'$SWIFT_MASTER':8080/v1/AUTH_$(tenant_id)s'
else
keystone endpoint-create --region $KEYSTONE_REGION --service-id $2
--publicurl 'http://'$MASTER':8080/v1/AUTH_$(tenant_id)s'
--adminurl 'http://'$MASTER':8080/v1' --internalurl
'http://'$MASTER':8080/v1/AUTH_$(tenant_id)s'
fi
;;
identity
Re: [Openstack] No proper displau with Horizon
Response to :
{
endpoints: [
{
adminurl: http://x.x.x.x:9696/;,
region: RegionOne,
internalurl: http://x.x.x.x:9696/;,
service_id: 020a5c2b03074e89972202f3822fa95f,
id: 2febceec3f324755b0c9c7fe3ba2d29d,
publicurl: http://x.x.x.x:9696/;
},
{
adminurl: http://x.x.x.x:8774/v2/$(tenant_id)s,
region: RegionOne,
internalurl: http://x.x.x.x:8774/v2/$(tenant_id)s,
service_id: c6011214a82645fe97b4bbd64608ad9b,
id: 649d5e5b5cd8467c89b218b2adc29009,
publicurl: http://x.x.x.x:8774/v2/$(tenant_id)s
},
{
adminurl: http://x.x.x.x:35357/v2.0;,
region: RegionOne,
internalurl: http://x.x.x.x:5000/v2.0;,
service_id: 9733c366161f4f7f8e8484fe702ee840,
id: 7b25b6283dd4408d8c8f7541b9b9d2f0,
publicurl: http://x.x.x.x:5000/v2.0;
},
{
adminurl: http://x.x.x.x:9292/v2;,
region: RegionOne,
internalurl: http://x.x.x.x:9292/v2;,
service_id: 776d3b71749f4711bf1c956ccfeb2728,
id: 9ebfa2784d78425fa08a146aa27e786b,
publicurl: http://x.x.x.x:9292/v2;
},
{
adminurl: http://x.x.x.x:8776/v1/$(tenant_id)s,
region: RegionOne,
internalurl: http://x.x.x.x:8776/v1/$(tenant_id)s,
service_id: 4ef30c360f4e4e0aaac9d1247dcaafe8,
id: f321ae42d39d4d9a9d5e771be459f6ba,
publicurl: http://x.x.x.x:8776/v1/$(tenant_id)s
},
{
adminurl: http://x.x.x.x:8773/services/Admin;,
region: RegionOne,
internalurl: http://x.x.x.x:8773/services/Cloud;,
service_id: 2b3d91dd9110493a92ea5eb7909d41cf,
id: f7ef924364614d91b49a589ca7719ce6,
publicurl: http://x.x.x.x:8773/services/Cloud;
}
]
}
i didn't edit my local_settings.py, i just disabled the quantum then i
restarted apache and memcached services.
Le 08/10/2012 10:59, Dolph Mathews a écrit :
Hmm... I don't see anything wrong there. Any chance you've
overridden AVAILABLE_REGIONS in your horizon configuration? If so,
what's the new value?
Also, to make sure service_id references are configured correctly, can
you paste the raw output of:
curl http://x.x.x.x:35357/v2.0/endpoints -H 'x-auth-token: ADMIN'
Substitute your own IP for keystone and a valid token.
-Dolph
On Mon, Oct 8, 2012 at 3:47 AM, Bilel Msekni ski...@hotmail.fr
mailto:ski...@hotmail.fr wrote:
Thanks for replying Dolph:
keystone service-list
+--+--+--+--+
|id| name | type |
description |
+--+--+--+--+
| 020a5c2b03074e89972202f3822fa95f | quantum | network |
OpenStack Networking service |
| 2b3d91dd9110493a92ea5eb7909d41cf | ec2| ec2|
OpenStack EC2 service |
| 4ef30c360f4e4e0aaac9d1247dcaafe8 | cinder | volume |
OpenStack Volume Service |
| 776d3b71749f4711bf1c956ccfeb2728 | glance | image |
OpenStack Image Service|
| 9733c366161f4f7f8e8484fe702ee840 | keystone | identity |
OpenStack Identity |
| c6011214a82645fe97b4bbd64608ad9b | nova | compute |
OpenStack Compute Service |
+--+--+--+--+
keystone endpoint-list
+--+---+--+--+--+
|id| region |
publicurl | internalurl |
adminurl |
+--+---+--+--+--+
| 2febceec3f324755b0c9c7fe3ba2d29d | RegionOne |
http://x.x.x.x:9696/ | http://x.x.x.x:9696/ | http://x.x.x.x:9696/ |
| 649d5e5b5cd8467c89b218b2adc29009 | RegionOne |
http://x.x.x.x:8774/v2/$(tenant_id)s
http://x.x.x.x:8774/v2/$%28tenant_id%29s |
http://x.x.x.x:8774/v2/$(tenant_id)s
http://x.x.x.x:8774/v2/$%28tenant_id%29s |
http://x.x.x.x:8774/v2/$(tenant_id)s
http://x.x.x.x:8774/v2/$%28tenant_id%29s |
| 7b25b6283dd4408d8c8f7541b9b9d2f0 | RegionOne |
http://x.x.x.x:5000/v2.0 | http://x.x.x.x:5000/v2.0 |
http://x.x.x.x:35357/v2.0 |
| 9ebfa2784d78425fa08a146aa27e786b | RegionOne |
http://x.x.x.x:9292/v2 | http://x.x.x.x:9292/v2 |
http://x.x.x.x:9292/v2
Re: [Openstack] No proper displau with Horizon
Hi Dolph,
I figured it out. This is not a keystone problem but actually a problem
in the Ubuntu OpenStack theme.
I just commented these lines
=
# Enable the Ubuntu theme if it is present.
#try:
#from ubuntu_theme import *
#except ImportError:
#pass
so that i can go back at using the default OpenStack theme , restarted
apache and memcached
I am still getting the no endpoint problem but at least i get a proper
display to work with :)
Le 08/10/2012 11:14, Bilel Msekni a écrit :
Response to :
{
endpoints: [
{
adminurl: http://x.x.x.x:9696/;,
region: RegionOne,
internalurl: http://x.x.x.x:9696/;,
service_id: 020a5c2b03074e89972202f3822fa95f,
id: 2febceec3f324755b0c9c7fe3ba2d29d,
publicurl: http://x.x.x.x:9696/;
},
{
adminurl: http://x.x.x.x:8774/v2/$(tenant_id)s,
region: RegionOne,
internalurl: http://x.x.x.x:8774/v2/$(tenant_id)s,
service_id: c6011214a82645fe97b4bbd64608ad9b,
id: 649d5e5b5cd8467c89b218b2adc29009,
publicurl: http://x.x.x.x:8774/v2/$(tenant_id)s
},
{
adminurl: http://x.x.x.x:35357/v2.0;,
region: RegionOne,
internalurl: http://x.x.x.x:5000/v2.0;,
service_id: 9733c366161f4f7f8e8484fe702ee840,
id: 7b25b6283dd4408d8c8f7541b9b9d2f0,
publicurl: http://x.x.x.x:5000/v2.0;
},
{
adminurl: http://x.x.x.x:9292/v2;,
region: RegionOne,
internalurl: http://x.x.x.x:9292/v2;,
service_id: 776d3b71749f4711bf1c956ccfeb2728,
id: 9ebfa2784d78425fa08a146aa27e786b,
publicurl: http://x.x.x.x:9292/v2;
},
{
adminurl: http://x.x.x.x:8776/v1/$(tenant_id)s,
region: RegionOne,
internalurl: http://x.x.x.x:8776/v1/$(tenant_id)s,
service_id: 4ef30c360f4e4e0aaac9d1247dcaafe8,
id: f321ae42d39d4d9a9d5e771be459f6ba,
publicurl: http://x.x.x.x:8776/v1/$(tenant_id)s
},
{
adminurl: http://x.x.x.x:8773/services/Admin;,
region: RegionOne,
internalurl: http://x.x.x.x:8773/services/Cloud;,
service_id: 2b3d91dd9110493a92ea5eb7909d41cf,
id: f7ef924364614d91b49a589ca7719ce6,
publicurl: http://x.x.x.x:8773/services/Cloud;
}
]
}
i didn't edit my local_settings.py, i just disabled the quantum then i
restarted apache and memcached services.
Le 08/10/2012 10:59, Dolph Mathews a écrit :
Hmm... I don't see anything wrong there. Any chance you've
overridden AVAILABLE_REGIONS in your horizon configuration? If so,
what's the new value?
Also, to make sure service_id references are configured correctly,
can you paste the raw output of:
curl http://x.x.x.x:35357/v2.0/endpoints -H 'x-auth-token: ADMIN'
Substitute your own IP for keystone and a valid token.
-Dolph
On Mon, Oct 8, 2012 at 3:47 AM, Bilel Msekni ski...@hotmail.fr
mailto:ski...@hotmail.fr wrote:
Thanks for replying Dolph:
keystone service-list
+--+--+--+--+
|id| name | type |
description |
+--+--+--+--+
| 020a5c2b03074e89972202f3822fa95f | quantum | network |
OpenStack Networking service |
| 2b3d91dd9110493a92ea5eb7909d41cf | ec2| ec2|
OpenStack EC2 service |
| 4ef30c360f4e4e0aaac9d1247dcaafe8 | cinder | volume |
OpenStack Volume Service |
| 776d3b71749f4711bf1c956ccfeb2728 | glance | image |
OpenStack Image Service|
| 9733c366161f4f7f8e8484fe702ee840 | keystone | identity |
OpenStack Identity |
| c6011214a82645fe97b4bbd64608ad9b | nova | compute |
OpenStack Compute Service |
+--+--+--+--+
keystone endpoint-list
+--+---+--+--+--+
|id| region |
publicurl | internalurl |
adminurl |
+--+---+--+--+--+
| 2febceec3f324755b0c9c7fe3ba2d29d | RegionOne |
http://x.x.x.x:9696/ | http://x.x.x.x:9696/ | http://x.x.x.x:9696/ |
| 649d5e5b5cd8467c89b218b2adc29009 | RegionOne |
http://x.x.x.x:8774/v2
[Openstack] Disable Quantum in Horizon Folsom
Hi, Back with a new bug :) So, i have installed OpenStack Folsom and edited the horizon localsetting.py file to disable Quantum service: (Quantum_Enabled=False) Still now Horizon is giving errors and inhibiting me from starting VMs: I get this when i click on the networks tab in the dashboard page: http://pastebin.com/7766hVwb does anyone have an idea how to disable quantum in Horizon ? ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Disable Quantum in Horizon Folsom
Thank you Kiall for replying, Of course i did :) Yet, after consulting with OpenStack IRC people, it seems that quantum can not be excluded from horizon :) I am going for installing it :) Le 08/10/2012 12:10, Kiall Mac Innes a écrit : Did you restart apache after editing local_settings.py? Thanks, Kiall On Mon, Oct 8, 2012 at 10:57 AM, Bilel Msekni ski...@hotmail.fr mailto:ski...@hotmail.fr wrote: Hi, Back with a new bug :) So, i have installed OpenStack Folsom and edited the horizon localsetting.py file to disable Quantum service: (Quantum_Enabled=False) Still now Horizon is giving errors and inhibiting me from starting VMs: I get this when i click on the networks tab in the dashboard page: http://pastebin.com/7766hVwb does anyone have an idea how to disable quantum in Horizon ? ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Problem installing Nova 2012.2
Hi Stackers, I am encountering a problem when i do this: _apt-get -y install nova-common nova-compute nova-volume nova-vncproxy nova-api nova-ajax-console-proxy nova-cert nova-consoleauth nova-doc nova-scheduler nova-network_ It replies back with : _The following packages have unmet dependencies:__ __ nova-vncproxy : Depends: nova-common (= 2012.2+git201209200431~precise-0ubuntu1) but 2012.2+git201209250431~precise-0ubuntu1 is to be installed__ __E: Unable to correct problems, you have held broken packages._ Does anyone have an idea how to fix this ? ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Problem installing Nova 2012.2
Le 04/10/2012 13:56, Daviey Walker a écrit : On 4 October 2012 12:51, Bilel Msekni ski...@hotmail.fr wrote: Hi Stackers, I am encountering a problem when i do this: apt-get -y install nova-common nova-compute nova-volume nova-vncproxy nova-api nova-ajax-console-proxy nova-cert nova-consoleauth nova-doc nova-scheduler nova-network It replies back with : The following packages have unmet dependencies: nova-vncproxy : Depends: nova-common (= 2012.2+git201209200431~precise-0ubuntu1) but 2012.2+git201209250431~precise-0ubuntu1 is to be installed E: Unable to correct problems, you have held broken packages. Does anyone have an idea how to fix this ? SNIP Where are you trying to install this from? The following output would be helpful, please: $ apt-cache policy nova-common This is what apt-cache policy nova-common is giving me : == nova-common: Installed: 2012.2-0ubuntu3~cloud0 Candidate: 2012.2-0ubuntu3~cloud0 Version table: *** 2012.2-0ubuntu3~cloud0 0 500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ precise-updates/folsom/main amd64 Packages 100 /var/lib/dpkg/status 2012.1.3+stable-20120827-4d2a4afe-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 2012.1+stable~20120612-3ee026e-0ubuntu1.3 0 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 2012.1-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages i am following the http://docs.openstack.org/trunk/openstack-compute/install/apt/content/ install guide so i am installing using the _*deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/folsom main*__ _I am not the only one experiencing this problem, check this : https://answers.launchpad.net/nova/+question/210171 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Error in the OpenStack Folsom install guide
Le 04/10/2012 14:55, Consonni, Marco a écrit : Hello, I would recommed to file the bug here: https://bugs.launchpad.net/openstack-manuals You need to subscribe to launchpad. Cheers, MCo *From:*openstack-bounces+marco.consonni=hp@lists.launchpad.net [mailto:openstack-bounces+marco.consonni=hp@lists.launchpad.net] *On Behalf Of *Bilel Msekni *Sent:* Thursday, October 04, 2012 12:40 PM *To:* openstack@lists.launchpad.net *Subject:* [Openstack] Error in the OpenStack Folsom install guide Hi all, There is a mistake in the OpenStack Folsom install guide in this page : http://docs.openstack.org/trunk/openstack-compute/install/apt/content/images-verifying-install.html First there is no glance --version command and moreover it shouldn't display back the Essex version :) Okay, thanks :) ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Problem installing Nova 2012.2
Le 04/10/2012 14:51, Daviey Walker a écrit : On 4 October 2012 13:02, Bilel Msekni ski...@hotmail.fr wrote: Le 04/10/2012 13:56, Daviey Walker a écrit : On 4 October 2012 12:51, Bilel Msekni ski...@hotmail.fr wrote: Hi Stackers, I am encountering a problem when i do this: apt-get -y install nova-common nova-compute nova-volume nova-vncproxy nova-api nova-ajax-console-proxy nova-cert nova-consoleauth nova-doc nova-scheduler nova-network It replies back with : The following packages have unmet dependencies: nova-vncproxy : Depends: nova-common (= 2012.2+git201209200431~precise-0ubuntu1) but 2012.2+git201209250431~precise-0ubuntu1 is to be installed E: Unable to correct problems, you have held broken packages. Does anyone have an idea how to fix this ? SNIP Where are you trying to install this from? The following output would be helpful, please: $ apt-cache policy nova-common This is what apt-cache policy nova-common is giving me : == nova-common: Installed: 2012.2-0ubuntu3~cloud0 Candidate: 2012.2-0ubuntu3~cloud0 Version table: *** 2012.2-0ubuntu3~cloud0 0 500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ precise-updates/folsom/main amd64 Packages 100 /var/lib/dpkg/status 2012.1.3+stable-20120827-4d2a4afe-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 2012.1+stable~20120612-3ee026e-0ubuntu1.3 0 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 2012.1-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages i am following the http://docs.openstack.org/trunk/openstack-compute/install/apt/content/ install guide so i am installing using the deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/folsom main I am not the only one experiencing this problem, check this : https://answers.launchpad.net/nova/+question/210171 Hi, This seems to be a change introduced after Folsom milestone 3, which the documentation reflects. In your apt-get install line, can you replace nova-vncproxy with nova-novncproxy. Therefore: $ sudo apt-get -y install nova-common nova-compute nova-volume nova-novncproxy nova-api nova-ajax-console-proxy nova-cert nova-consoleauth nova-doc nova-scheduler nova-network Please let me know if this doesn't resolve the issue for you. Thanks. Your solution works like a charm. I guess the documentation is really outdated, i will signal that. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Quantum features in the folsom release
Hi Stackers, Can someone here help me out by detailing the new Quantum features that will be available in the Folsom release. Even a link or anything could help ! i can't seem to find any proper documentation and i have to persuade my boss about the potentials of Quantum :) Thanks ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Quantum features in the folsom release
Le 10/09/2012 20:39, Dan Wendlandt a écrit : On Mon, Sep 10, 2012 at 11:07 AM, Bilel Msekni ski...@hotmail.fr wrote: Hi Stackers, Can someone here help me out by detailing the new Quantum features that will be available in the Folsom release. Even a link or anything could help ! i can't seem to find any proper documentation and i have to persuade my boss about the potentials of Quantum :) Hi Bilel, Don't worry, the Quantum team is working hard on docs for Folsom as we speak. At an extremely high-level, the two main things that Quantum provides are: 1) A rich tenant-facing API for defining networks. This let's tenants create rich network topologies, including multiple private networks, multi-tier web applications, etc. and choose which IP subnets are used on these networks (this even works if two tenants decide to use the same subnet). 2) Quantum has pluggable backends that allow cloud operators to use more advanced network technologies on the back-end. For example, you can use Open vSwitch tunneling to avoid limitations around VLANs or take advantage of a plugin that is aware of advanced hardware capabilities. The Quantum Admin Guide is still in draft form and we're hoping to have a publicly consumable draft near the end of this week. That should provide the additional details about specific capabilities. Dan Thanks ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp Thanks Dan, Sydney and Logan for your help, Actually i am already familiar with Quantum features but what i am really interested in is the monitoring and QoS apects. I was reading what happened in folsom summit in this link : http://etherpad.openstack.org/quantum-folsom and my guess is that Quantum will not support the monitoring and QoS features in the folsom release. Am i correct ? ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Dear Friends D
Hi,dear How are you ? A good web busines for you. www.aggoq.com I have bought an iphone there with excellent quality. Now they are on sale, and the delivery speed is very fast, you need not to wait for long. I hope you will love it. Just share it with you. May you hapiness !skible K___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Nova Volume and provisionning on iSCSI SAN
Hi all, I have a question relating to nova-volume, and provisioning block devices as storage for VMs. As I understand it from the documentation, nova-volume will take a block device with LVM on it, and then become an iSCSI target to share the logical volumes to compute nodes. I also understand that there is another process for using an HP lefthand SAN or solaris iSCSI setup, whereby nova-volume can interact with APIs for volume creation on the SAN itself. I have a dell iSCSI SAN, and I can see that I'd be able to mount a LUN from the SAN on my nova-volume node, then go through the documented process of creating an LVM on this LUN and having nova-volume re-share it over iSCSI to the compute nodes, but what I'm wondering is whether I can have the compute nodes simple connect to the iSCSI SAN to access these volumes (which would be created and managed by nova-volume still), rather than connect each compute node to the iSCSI target which nova-volume presents? I imagine with this setup, I could take advantage of the SAN's HA and performance benefits. Hope that makes sense.. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] AMQP server on localhost:5672 is unreachable: IOError Socket closed.
Le 15/05/2012 11:14, Shashi Kanth Boddula a écrit :
Essex on Ubuntu 12.04.
I am seeing these messages in noa-api.log file, and the nova is not
functional in dashboard. I believe the problem is with rabbitmq, but i
don't know how to solve this situation.
2012-05-15 14:20:11 ERROR nova.rpc.common
[req-1d70ea22-fb6e-4be8-84f5-54cfd78698ac
0c1bd987f8b84088983e17645067c225 488ef90f59fd4bf68fc78f7086556af2]
AMQP server on localhost:5672 is unreachable: Socket closed. Trying
again in 30 seconds.
2012-05-15 14:20:11 TRACE nova.rpc.common Traceback (most recent call
last):
2012-05-15 14:20:11 TRACE nova.rpc.common File
/usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py, line 446,
in reconnect
2012-05-15 14:20:11 TRACE nova.rpc.common self._connect()
2012-05-15 14:20:11 TRACE nova.rpc.common File
/usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py, line 423,
in _connect
2012-05-15 14:20:11 TRACE nova.rpc.common self.connection.connect()
2012-05-15 14:20:11 TRACE nova.rpc.common File
/usr/lib/python2.7/dist-packages/kombu/connection.py, line 154, in
connect
2012-05-15 14:20:11 TRACE nova.rpc.common return self.connection
2012-05-15 14:20:11 TRACE nova.rpc.common File
/usr/lib/python2.7/dist-packages/kombu/connection.py, line 560, in
connection
2012-05-15 14:20:11 TRACE nova.rpc.common self._connection =
self._establish_connection()
2012-05-15 14:20:11 TRACE nova.rpc.common File
/usr/lib/python2.7/dist-packages/kombu/connection.py, line 521, in
_establish_connection
2012-05-15 14:20:11 TRACE nova.rpc.common conn =
self.transport.establish_connection()
2012-05-15 14:20:11 TRACE nova.rpc.common File
/usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line
255, in establish_connection
2012-05-15 14:20:11 TRACE nova.rpc.common
connect_timeout=conninfo.connect_timeout)
2012-05-15 14:20:11 TRACE nova.rpc.common File
/usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line
52, in __init__
2012-05-15 14:20:11 TRACE nova.rpc.common super(Connection,
self).__init__(*args, **kwargs)
2012-05-15 14:20:11 TRACE nova.rpc.common File
/usr/lib/python2.7/dist-packages/amqplib/client_0_8/connection.py,
line 144, in __init__
2012-05-15 14:20:11 TRACE nova.rpc.common (10, 30), # tune
2012-05-15 14:20:11 TRACE nova.rpc.common File
/usr/lib/python2.7/dist-packages/amqplib/client_0_8/abstract_channel.py,
line 95, in wait
2012-05-15 14:20:11 TRACE nova.rpc.common self.channel_id,
allowed_methods)
2012-05-15 14:20:11 TRACE nova.rpc.common File
/usr/lib/python2.7/dist-packages/amqplib/client_0_8/connection.py,
line 202, in _wait_method
2012-05-15 14:20:11 TRACE nova.rpc.common
self.method_reader.read_method()
2012-05-15 14:20:11 TRACE nova.rpc.common File
/usr/lib/python2.7/dist-packages/amqplib/client_0_8/method_framing.py,
line 221, in read_method
2012-05-15 14:20:11 TRACE nova.rpc.common raise m
2012-05-15 14:20:11 TRACE nova.rpc.common IOError: Socket closed
2012-05-15 14:20:11 TRACE nova.rpc.common
# service rabbitmq-server status
Status of node rabbit@openstack ...
[{pid,2137},
{running_applications,[{rabbit,RabbitMQ,2.7.1},
{os_mon,CPO CXC 138 46,2.2.7},
{sasl,SASL CXC 138 11,2.1.10},
{mnesia,MNESIA CXC 138 12,4.5},
{stdlib,ERTS CXC 138 10,1.17.5},
{kernel,ERTS CXC 138 10,2.14.5}]},
{os,{unix,linux}},
{erlang_version,Erlang R14B04 (erts-5.8.5) [source] [64-bit]
[smp:24:24] [rq:24] [async-threads:30] [kernel-poll:true]\n},
{memory,[{total,26413240},
{processes,10154960},
{processes_used,10134760},
{system,16258280},
{atom,1124441},
{atom_used,1120341},
{binary,69304},
{code,11134417},
{ets,742384}]},
{vm_memory_high_watermark,0.397628105},
{vm_memory_limit,13491309772}]
...done.
--
Thanks Regards,
Shashi Kanth
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Nova connects to RabbitMQ through the defaults values ( localhost:5672)
and credentials (guest)
Check for the address of your rabbitMQ in the config file
(/etc/rabbitmq/rabbitMQ.config)
and do this
nano /etc/rabbitmq/rabbitmq.config
[{rabbit, [{tcp_listeners, [{127.0.0.1,5672}] }] } ]. #Paste this line
#Exit and SAVE
service start rabbitmq-server
This certainly will make your rabbitMQ talk to Nova. otherwise there is
something wrong with your nova
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
[Openstack] OpenStack Install Understand Guide by Me :)
Hi everyone , i proudly present 30 days of work.30 days ago , i was an OpenStack Noobie, Today i have much more knowledge about this awesome project.I wanted to share this work with those who are still taking the fist steps into the world of cloud computing.It's a one host install guide, pretty simple and covers almost everything. take a look, help me out with comments to enhance my work and if you want to participate join me at : https://github.com/mseknibilel/OpenStack-Install-and-Understand-Guide#openstack-install-and-understand-guide ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Floating IPs don't get dissociated after delete
Hi , I am having this problem just like many others. Each time I delete a VM, the floating IP doesn't get automatically dissociated, has anyone encountred this problem and solved it ? ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] BadCleaning after deleting a VM instance
Hi i have installed OS Essex and everything is working well so far, yet i have noticed a bad clean up after deleting VMs 1- My Tap interface ( vNIC comming from OpenVSwitch) is still on my bridge and it doesn't go away2- Floating IP doesn't get dissociated resulting in 500 error when i try to fetch all floating IPs I have seen a bug reported about that and fixed but the problem still persist for me and for other peoples tooCan anyone help me out here ? I am using quantum and OpenVSwitch as a pluging on ubuntu 11.04 ( It's an All in one install mode) P.S : Still trying to get a my VNC to work, i have a bad configuration ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Instance IP assignment problem
Fixed IP or Floating IP ? From: emilien.openst...@gmail.com To: salma...@live.com Date: Thu, 3 May 2012 09:55:31 +0200 CC: openstack@lists.launchpad.net Subject: Re: [Openstack] Instance IP assignment problem Hi, As I told you, I have also a problem for instance IP assignement. My architecture : I use Quantum with OVS plugin on 2 servers Essex-1 Essex-2. Essex-1 runs all services and Essex-2 runs OVS, Quantum-agent nova-compute only. You can see more details here. My configurations files are here and in my documentation. Problem Description : When an instance is created in ESSEX-1, all is working (network). But when the VM is started on ESSEX-2, it does not get an IP address. (log file) I'm sure the problem comes from OVS connection with ESSEX-1. Do I need to configure something like a trunk or a tunnel between Essex-1 Essex-2 ? I miss something in my configuration, if you have any idea... Regards Emilien Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a écrit : It may help if you can share the log of your launched instance as well. There is a possibility that we both are having the same issue. Netstack developers can give a definitive answer to this, but it would be interesting to learn what goes wrong with a launched instance. Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: salma...@live.com CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:26:26 +0200 Le mardi 01 mai 2012 à 14:22 -0500, Salman Malik a écrit : Regarding L3 gateway, I believe its not necessary to have one (as the VM hasn't obtained an IP right now, so it can't talk to anything outside its net), but I am not sure. Regarding your problem, do you see any DHCP responses from the DHCP server ? I am asking this because I was having a similar problem earlier where I was getting assigned an IP address no in my desired fixed_network and I believe that was cause by another interfering DHCP server that was replying to discover messages before the nova-network could. Here my nova.conf and I don't have any interfering DHCP server : https://github.com/EmilienM/doc-openstack/blob/master/Configuration%20Files/Essex-1/nova.conf Thanks Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: salma...@live.com CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:06:01 +0200 Hi Salman, I'm thinking about a networking issue. Where is your L3 gateway in this architecture ? Maybe do you need an ip helper tool to redirect DHCP broadcast ? What do you think about my problem (follow up to my last e-mail) ? Thanks Emilien Le mardi 01 mai 2012 à 14:00 -0500, Salman Malik a écrit : Hi, Here is the error log: http://pastebin.com/KrNZDrvD and nova.conf: http://pastebin.com/Fvd6dSZs Emilien, I am trying to get an understanding of how different Quantum plugins work with OpenStack. Ryu plugin is particularly interesting as it uses an OpenFlow controller to configure Vswitches. The problem I am faced with is (I think ) that I already have a private network and Quantum should assign IP addresses to instances using DHCP. But instances send out discover message on laucnh but never find a DHCP server (although there are 2 dnsmasqs running). Any ideas? Thanks, Salman Date: Tue, 1 May 2012 20:43:44 +0200 Subject: Re: [Openstack] Instance IP assignment problem From: jorge.delac...@stackops.com To: emilien.openst...@gmail.com CC: openstack@lists.launchpad.net; salma...@live.com Hi Emilien and Salman, Please, could you upload all the files, errors and conf in pastebin or something like that? I have troubles to open in phone :) Thank you El 01/05/2012 20:39, Emilien Macchi emilien.openst...@gmail.com escribió: Hi, I have a similar problem when I create a network per project_id with Quantum. My VMs don't get IP and I can't understand why today.
Re: [Openstack] Instance IP assignment problem
Then the problem isn't in the instance but in the nova-network service , please check if it is working well as well as give us the output log when you attempt to create a new instance. Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: ski...@hotmail.fr CC: salma...@live.com; openstack@lists.launchpad.net Date: Thu, 3 May 2012 10:21:37 +0200 Fixed IP Le jeudi 03 mai 2012 à 09:15 +0100, Bilel Msekni a écrit : Fixed IP or Floating IP ? From: emilien.openst...@gmail.com To: salma...@live.com Date: Thu, 3 May 2012 09:55:31 +0200 CC: openstack@lists.launchpad.net Subject: Re: [Openstack] Instance IP assignment problem Hi, As I told you, I have also a problem for instance IP assignement. My architecture : I use Quantum with OVS plugin on 2 servers Essex-1 Essex-2. Essex-1 runs all services and Essex-2 runs OVS, Quantum-agent nova-compute only. You can see more details here. My configurations files are here and in my documentation. Problem Description : When an instance is created in ESSEX-1, all is working (network). But when the VM is started on ESSEX-2, it does not get an IP address. (log file) I'm sure the problem comes from OVS connection with ESSEX-1. Do I need to configure something like a trunk or a tunnel between Essex-1 Essex-2 ? I miss something in my configuration, if you have any idea... Regards Emilien Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a écrit : It may help if you can share the log of your launched instance as well. There is a possibility that we both are having the same issue. Netstack developers can give a definitive answer to this, but it would be interesting to learn what goes wrong with a launched instance. Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: salma...@live.com CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:26:26 +0200 Le mardi 01 mai 2012 à 14:22 -0500, Salman Malik a écrit : Regarding L3 gateway, I believe its not necessary to have one (as the VM hasn't obtained an IP right now, so it can't talk to anything outside its net), but I am not sure. Regarding your problem, do you see any DHCP responses from the DHCP server ? I am asking this because I was having a similar problem earlier where I was getting assigned an IP address no in my desired fixed_network and I believe that was cause by another interfering DHCP server that was replying to discover messages before the nova-network could. Here my nova.conf and I don't have any interfering DHCP server : https://github.com/EmilienM/doc-openstack/blob/master/Configuration%20Files/Essex-1/nova.conf Thanks Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: salma...@live.com CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:06:01 +0200 Hi Salman, I'm thinking about a networking issue. Where is your L3 gateway in this architecture ? Maybe do you need an ip helper tool to redirect DHCP broadcast ? What do you think about my problem (follow up to my last e-mail) ? Thanks Emilien Le mardi 01 mai 2012 à 14:00 -0500, Salman Malik a écrit : Hi, Here is the error log: http://pastebin.com/KrNZDrvD and nova.conf: http://pastebin.com/Fvd6dSZs Emilien, I am trying to get an understanding of how different Quantum plugins work with OpenStack. Ryu plugin is particularly interesting as it uses an OpenFlow controller to configure Vswitches. The problem I am faced with is (I think ) that I already have a private network and Quantum should assign IP addresses to instances using DHCP. But instances send out discover message on laucnh but never find a DHCP server (although there are 2 dnsmasqs running). Any ideas? Thanks
Re: [Openstack] Instance IP assignment problem
èmm , can you do this on your instance : nova show %instance_Id so that i may see the problem in the resume of spawning ?and are you sure you have enough fixed ip addresses left for use ? The configuration of nova and quantum is almost the same as me and the instances are getting Fixed Ips without any problem ! Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: ski...@hotmail.fr CC: salma...@live.com; openstack@lists.launchpad.net Date: Thu, 3 May 2012 10:48:43 +0200 All seems alright but not working yet. http://paste.openstack.org/show/14791/ I have executed on both servers : ovs-vsctl add-port br-int eth1 Need I do something else ? How the DHCP is working in this case ? Le jeudi 03 mai 2012 à 09:29 +0100, Bilel Msekni a écrit : Then the problem isn't in the instance but in the nova-network service , please check if it is working well as well as give us the output log when you attempt to create a new instance. Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: ski...@hotmail.fr CC: salma...@live.com; openstack@lists.launchpad.net Date: Thu, 3 May 2012 10:21:37 +0200 Fixed IP Le jeudi 03 mai 2012 à 09:15 +0100, Bilel Msekni a écrit : Fixed IP or Floating IP ? From: emilien.openst...@gmail.com To: salma...@live.com Date: Thu, 3 May 2012 09:55:31 +0200 CC: openstack@lists.launchpad.net Subject: Re: [Openstack] Instance IP assignment problem Hi, As I told you, I have also a problem for instance IP assignement. My architecture : I use Quantum with OVS plugin on 2 servers Essex-1 Essex-2. Essex-1 runs all services and Essex-2 runs OVS, Quantum-agent nova-compute only. You can see more details here. My configurations files are here and in my documentation. Problem Description : When an instance is created in ESSEX-1, all is working (network). But when the VM is started on ESSEX-2, it does not get an IP address. (log file) I'm sure the problem comes from OVS connection with ESSEX-1. Do I need to configure something like a trunk or a tunnel between Essex-1 Essex-2 ? I miss something in my configuration, if you have any idea... Regards Emilien Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a écrit : It may help if you can share the log of your launched instance as well. There is a possibility that we both are having the same issue. Netstack developers can give a definitive answer to this, but it would be interesting to learn what goes wrong with a launched instance. Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: salma...@live.com CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:26:26 +0200 Le mardi 01 mai 2012 à 14:22 -0500, Salman Malik a écrit : Regarding L3 gateway, I believe its not necessary to have one (as the VM hasn't obtained an IP right now, so it can't talk to anything outside its net), but I am not sure. Regarding your problem, do you see any DHCP responses from the DHCP server ? I am asking this because I was having a similar problem earlier where I was getting assigned an IP address no in my desired fixed_network and I believe that was cause by another interfering DHCP server that was replying to discover messages before the nova-network could. Here my nova.conf and I don't have any interfering DHCP server : https://github.com/EmilienM/doc-openstack/blob/master/Configuration%20Files/Essex-1/nova.conf Thanks Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: salma...@live.com CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:06:01 +0200
Re: [Openstack] Instance IP assignment problem
Basing on your architecture picture , I think you mean ping VM that resides on Essex 2 from server containing Essex 1I had a similar networking problem and i honestly don't know i fixed it ( didn't enable tunneling) , this is what i did1- ifconfig eth0 0.0.0.02- dhclient br-int ( normally the bridge will take the address of eth0) and pinging went back to working fine but i am still testing if there are any side effectsTry it out and txt me ! btw , i used your ubuntu 12.04 LTS cloud img and i can't seem to ping it but when i choose another image ( the default tty for example) it ping as a charm , probably you should pick another image ! Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: ski...@hotmail.fr CC: openstack@lists.launchpad.net Date: Thu, 3 May 2012 11:11:04 +0200 Ok : http://paste.openstack.org/show/14797/ I know where is the problem but I dont know yet how to fix it : - Quantum creates TAP interface on ESSEX-2 - From ESSEX-2, I can't ping VMs on ESSEX-1 Here my ovs_quantum_plugin.ini : [DATABASE] sql_connection = mysql://ovs_quantum:password@10.68.1.40:3306/ovs_quantum [OVS] integration-bridge = br-int [AGENT] root_helper = sudo Do we need enable bridge ? Le jeudi 03 mai 2012 à 10:00 +0100, Bilel Msekni a écrit : èmm , can you do this on your instance : nova show %instance_Id so that i may see the problem in the resume of spawning ? and are you sure you have enough fixed ip addresses left for use ? The configuration of nova and quantum is almost the same as me and the instances are getting Fixed Ips without any problem ! Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: ski...@hotmail.fr CC: salma...@live.com; openstack@lists.launchpad.net Date: Thu, 3 May 2012 10:48:43 +0200 All seems alright but not working yet. http://paste.openstack.org/show/14791/ I have executed on both servers : ovs-vsctl add-port br-int eth1 Need I do something else ? How the DHCP is working in this case ? Le jeudi 03 mai 2012 à 09:29 +0100, Bilel Msekni a écrit : Then the problem isn't in the instance but in the nova-network service , please check if it is working well as well as give us the output log when you attempt to create a new instance. Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: ski...@hotmail.fr CC: salma...@live.com; openstack@lists.launchpad.net Date: Thu, 3 May 2012 10:21:37 +0200 Fixed IP Le jeudi 03 mai 2012 à 09:15 +0100, Bilel Msekni a écrit : Fixed IP or Floating IP ? From: emilien.openst...@gmail.com To: salma...@live.com Date: Thu, 3 May 2012 09:55:31 +0200 CC: openstack@lists.launchpad.net Subject: Re: [Openstack] Instance IP assignment problem Hi, As I told you, I have also a problem for instance IP assignement. My architecture : I use Quantum with OVS plugin on 2 servers Essex-1 Essex-2. Essex-1 runs all services and Essex-2 runs OVS, Quantum-agent nova-compute only. You can see more details here. My configurations files are here and in my documentation. Problem Description : When an instance is created in ESSEX-1, all is working (network). But when the VM is started on ESSEX-2, it does not get an IP address. (log file) I'm sure the problem comes from OVS connection with ESSEX-1. Do I need to configure something like a trunk or a tunnel between Essex-1 Essex-2 ? I miss something in my configuration, if you have any idea... Regards Emilien Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a écrit : It may help if you can share the log of your launched instance as well. There is a possibility that we both are having the same issue. Netstack developers can give a definitive answer to this, but it would be interesting to learn what goes wrong with a launched instance. Salman
Re: [Openstack] Can't get fix ip via dhcp and can't accociate Floating ip using quantum
Network 2 could not be found.
That's your key
Date: Thu, 3 May 2012 17:58:43 +0800
From: mwjpi...@gmail.com
To: openstack@lists.launchpad.net
Subject: [Openstack] Can't get fix ip via dhcp and can't accociate Floating
ip using quantum
I use quantum as my nova-network in ubuntu 12.04LTS, there are two problem:
1: it can show fix ip, but in vm, the network interfaces have no ips. Using
dhclient eth0 does not make sense. Using ifconfig eth0 inet xxx netmask xxx
can work.
2: when I accociate floating ip to a vm , it show error, the nova-network log
is below:
2012-05-03 17:51:18 DEBUG nova.rpc.amqp
[req-f0a4fffa-d6fa-4ab6-9985-1bc4e248edf7 538eac0210274847a183a988f57fbd59
57eb0d7989c7457aa3818998fbf9a4dc] unpacked context: {'user_id':
u'538eac0210274847a183a988f57fbd59', 'roles': [u'Member'], 'timestamp':
'2012-05-03T09:51:18.403089', 'auth_token': 'SANITIZED', 'remote_address':
u'127.0.0.1', 'is_admin': False, 'request_id':
u'req-f0a4fffa-d6fa-4ab6-9985-1bc4e248edf7', 'project_id':
u'57eb0d7989c7457aa3818998fbf9a4dc', 'read_deleted': u'no'} from (pid=3791)
_safe_log /usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
2012-05-03 17:51:18 DEBUG nova.rpc.amqp [-] received {u'_context_roles':
[u'Member'], u'_msg_id': u'c4056c388c26498b83a3909d33e6d4ce',
u'_context_read_deleted': u'no', u'_context_request_id':
u'req-ec319cc9-245d-4808-991b-a00b417b923e', u'args': {u'id': u'1'},
u'_context_auth_token': 'SANITIZED', u'_context_is_admin': False,
u'_context_project_id': u'57eb0d7989c7457aa3818998fbf9a4dc',
u'_context_timestamp': u'2012-05-03T09:51:18.787337', u'_context_user_id':
u'538eac0210274847a183a988f57fbd59', u'method': u'get_floating_ip',
u'_context_remote_address': u'127.0.0.1'} from (pid=3791) _safe_log
/usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
2012-05-03 17:51:18 DEBUG nova.rpc.amqp
[req-ec319cc9-245d-4808-991b-a00b417b923e 538eac0210274847a183a988f57fbd59
57eb0d7989c7457aa3818998fbf9a4dc] unpacked context: {'user_id':
u'538eac0210274847a183a988f57fbd59', 'roles': [u'Member'], 'timestamp':
'2012-05-03T09:51:18.787337', 'auth_token': 'SANITIZED', 'remote_address':
u'127.0.0.1', 'is_admin': False, 'request_id':
u'req-ec319cc9-245d-4808-991b-a00b417b923e', 'project_id':
u'57eb0d7989c7457aa3818998fbf9a4dc', 'read_deleted': u'no'} from (pid=3791)
_safe_log /usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
2012-05-03 17:51:18 DEBUG nova.rpc.amqp [-] received {u'_context_roles':
[u'Member', u'admin'], u'_msg_id': u'248d0e0cbff14809978e1b0333621772',
u'_context_read_deleted': u'no', u'_context_request_id':
u'req-ac208065-fc2e-4c3b-8fd5-d3661ca33ce1', u'args': {u'instance_id': 5,
u'instance_uuid': u'57f9432f-2177-4635-9692-645ed5a5f2f7', u'host': u'cloud',
u'project_id': u'57eb0d7989c7457aa3818998fbf9a4dc', u'rxtx_factor': 1.0},
u'_context_auth_token': 'SANITIZED', u'_context_is_admin': True,
u'_context_project_id': u'57eb0d7989c7457aa3818998fbf9a4dc',
u'_context_timestamp': u'2012-05-03T09:51:18.825231', u'_context_user_id':
u'538eac0210274847a183a988f57fbd59', u'method': u'get_instance_nw_info',
u'_context_remote_address': u'127.0.0.1'} from (pid=3791) _safe_log
/usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
2012-05-03 17:51:18 DEBUG nova.rpc.amqp
[req-ac208065-fc2e-4c3b-8fd5-d3661ca33ce1 538eac0210274847a183a988f57fbd59
57eb0d7989c7457aa3818998fbf9a4dc] unpacked context: {'user_id':
u'538eac0210274847a183a988f57fbd59', 'roles': [u'Member', u'admin'],
'timestamp': '2012-05-03T09:51:18.825231', 'auth_token': 'SANITIZED',
'remote_address': u'127.0.0.1', 'is_admin': True, 'request_id':
u'req-ac208065-fc2e-4c3b-8fd5-d3661ca33ce1', 'project_id':
u'57eb0d7989c7457aa3818998fbf9a4dc', 'read_deleted': u'no'} from (pid=3791)
_safe_log /usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
2012-05-03 17:51:18 DEBUG nova.utils [req-ac208065-fc2e-4c3b-8fd5-d3661ca33ce1
538eac0210274847a183a988f57fbd59 57eb0d7989c7457aa3818998fbf9a4dc] Attempting
to grab semaphore get_dhcp for method _get_dhcp_ip... from (pid=3791) inner
/usr/lib/python2.7/dist-packages/nova/utils.py:927
2012-05-03 17:51:18 DEBUG nova.utils [req-ac208065-fc2e-4c3b-8fd5-d3661ca33ce1
538eac0210274847a183a988f57fbd59 57eb0d7989c7457aa3818998fbf9a4dc] Got
semaphore get_dhcp for method _get_dhcp_ip... from (pid=3791) inner
/usr/lib/python2.7/dist-packages/nova/utils.py:931
2012-05-03 17:51:18 DEBUG nova.utils [req-ac208065-fc2e-4c3b-8fd5-d3661ca33ce1
538eac0210274847a183a988f57fbd59 57eb0d7989c7457aa3818998fbf9a4dc] Attempting
to grab semaphore get_dhcp for method _get_dhcp_ip... from (pid=3791) inner
/usr/lib/python2.7/dist-packages/nova/utils.py:927
2012-05-03 17:51:18 DEBUG nova.utils [req-ac208065-fc2e-4c3b-8fd5-d3661ca33ce1
538eac0210274847a183a988f57fbd59 57eb0d7989c7457aa3818998fbf9a4dc] Got
semaphore get_dhcp for method _get_dhcp_ip... from (pid=3791) inner
/usr/lib/python2.7/dist-packages/nova/utils.py:931
2012-05-03 17:51:18 DEBUG nova.utils
