Re: [Openstack] [QUANTUM] (Bug ?) L3 routing not correctly fragmenting packets ?

2013-03-11 Thread Sylvain Bauza
Hi Rick, reply inline. Le 08/03/2013 20:27, Rick Jones a écrit : On 03/08/2013 09:55 AM, Aaron Rosen wrote: Hi Sylvain, This seems very odd to me. The reason this should happen is if your client is sending packets with the DF (don't fragment) bit set in the TCP header of the packets you are

Re: [Openstack] [QUANTUM] (Bug ?) L3 routing not correctly fragmenting packets ?

2013-03-11 Thread Sylvain Bauza
I also forgot to mention: I'm using a typical Openvswitch setup with GRE encapsulation. I can't proof, but would GRE not able to work with PathMTU ? -Sylvain Le 11/03/2013 09:40, Sylvain Bauza a écrit : Hi Rick, reply inline. Le 08/03/2013 20:27, Rick Jones a écrit : On 03/08/2013 09:55 AM,

Re: [Openstack] [Heat] Problem with visit 169.254.169.254 from VM

2013-03-11 Thread Steven Hardy
On Thu, Mar 07, 2013 at 09:09:57AM +0800, 蒋闻天 wrote: Hi everyone, I have a problem when i use devstack to test heat and quantum. This is my localrc DATABASE_PASSWORD=nova RABBIT_PASSWORD=nova SERVICE_TOKEN=nova SERVICE_PASSWORD=nova ADMIN_PASSWORD=nova SCREEN_LOGDIR=/var/log/devstack

Re: [Openstack] Network node needed?

2013-03-11 Thread Logan McNaughton
No it's not needed, you just run quantum-server, the L3 agent, the DHCP agent, and the plugin agent (probably open vSwitch) all on the controller. You'll just need to plan out which NICs you'll use for what purpose and setup accordingly. As a side note, you'll also need to run the plugin agent on

Re: [Openstack] [QUANTUM] (Bug ?) L3 routing not correctly fragmenting packets ?

2013-03-11 Thread Sylvain Bauza
Okay. I think I got the reason why it's not working with OVS/GRE contrary to FlatDHCP nova-network. So, as per http://www.cisco.com/en/US/tech/tk827/tk369/technologies_white_paper09186a00800d6979.shtml , GRE encapsulation protocol can add up to 34 bytes to the IP datagram (meaning the TCP

Re: [Openstack] Incredibly odd mysql permission error

2013-03-11 Thread Samuel Winchenbach
Does anyone think this could be an openstack bug? I just want to check before submitting a bug report. Sam On Fri, Mar 8, 2013 at 4:02 PM, Jay Pipes jaypi...@gmail.com wrote: Sorry, I really can't think of anything :( On 03/08/2013 03:52 PM, Samuel Winchenbach wrote: I dropped those

[Openstack] Cinder volume as root in Grizzly?

2013-03-11 Thread Logan McNaughton
Will Grizzly support specifying an empty Cinder volume as an instance's root device? Right now you need to setup the volume before hand and you can boot from volume. But will there be support similar to AWS EBS-backed instances in Grizzly? ___ Mailing

Re: [Openstack] Incredibly odd mysql permission error

2013-03-11 Thread Sylvain Bauza
So as to reproduce the nova-manage SQL command, I would recommand to tcpdump -A port 3306 on the host and get the SQL trace on what's failing. Could you please explain further what is your HA config ? Are you using pacemaker/heartbeat or any VIP ? -Sylvain Le 11/03/2013 14:23, Samuel

Re: [Openstack] Incredibly odd mysql permission error

2013-03-11 Thread Samuel Winchenbach
I enabled general_log in /etc/mysql/my.cnf Here are the results of connecting from test1, test2 and using the client: http://paste2.org/p/3115525 I purposefully used the real password in case there is a problem with it. I changed before submitting post. here is a raw packet TCP dump (tcpdump

Re: [Openstack] Network node needed?

2013-03-11 Thread Martinx - ジェームズ
Is it possible to deploy Quantum (Flat) with two servers (controller + compute) that have only 1 ethernet on each? Plus, the Instances gateway will not be the controller, but my office firewall, external to the cloud, can be? Tks! On 11 March 2013 09:55, Logan McNaughton lo...@bacoosta.com

Re: [Openstack] Network node needed?

2013-03-11 Thread JuanFra Rodriguez Cardoso
Hi: You could find it in this link: http://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html Regards, JuanFra 2013/3/11 Martinx - ジェームズ thiagocmarti...@gmail.com Is it possible to deploy Quantum (Flat) with two servers (controller + compute) that

[Openstack] Tempest for Integration testing of Openstack (FOLSOM)

2013-03-11 Thread Girija Sharan
Hi All, I am trying to do Integration testing of Openstack environmment (Folsom) using Tempest. On controller node I am having my Tempest root directory and I have also installed Coverage, Tissue and Openstack-nose as it was mentioned in the setup.cfg file. 1. Do I have to use this release

Re: [Openstack] quantum-agent-setup: command not found

2013-03-11 Thread Aru s
I belive the below command will work instead. quantum-node-setup --plugin openvswitch Regards, Arumon On Fri, Mar 8, 2013 at 9:54 PM, Aru s arumo...@gmail.com wrote: Hi, I have installed openstack-quantum-openvswitch on my compute host. When try to enable the agent i am getting the below

Re: [Openstack] Incredibly odd mysql permission error

2013-03-11 Thread Samuel Winchenbach
#1 - No change #2 - All of grants are in the ip/mask form such as: 'nova'@' 10.21.0.0/255.255.0.0' I have also tried adding 'nova'@'test1' and 'nova'@'10.21.0.1'. No change. #3 - I changed the SQL connection string over to IP instead of hostname. No change. I didn't restart nova-api because it

Re: [Openstack] [QUANTUM] (Bug ?) L3 routing not correctly fragmenting packets ?

2013-03-11 Thread Rick Jones
On 03/11/2013 06:09 AM, Sylvain Bauza wrote: Okay. I think I got the reason why it's not working with OVS/GRE contrary to FlatDHCP nova-network. So, as per http://www.cisco.com/en/US/tech/tk827/tk369/technologies_white_paper09186a00800d6979.shtml , GRE encapsulation protocol can add up to 34

Re: [Openstack] Incredibly odd mysql permission error

2013-03-11 Thread Samuel Winchenbach
For completeness here the routing table, and ip listing for both test1 and test2. Doubt this will help much: http://paste2.org/p/3117125 On Mon, Mar 11, 2013 at 1:52 PM, Samuel Winchenbach swinc...@gmail.comwrote: #1 - No change #2 - All of grants are in the ip/mask form such as: 'nova'@'

Re: [Openstack] Incredibly odd mysql permission error

2013-03-11 Thread Samuel Winchenbach
OK Someone on the IRC channel got me closer, but we have no idea why this would happen: this works: root@test1:~# nova-manage --config-file=/etc/nova/nova.conf service list Why would I have to specify the config file though? It is in the standard place. Thanks, Sam On Mon, Mar 11,

Re: [Openstack] Network node needed?

2013-03-11 Thread Martinx - ジェームズ
Well, I've read that but, I'm still unable to run Quantum on its simplest scenario... FlatDHCP single (multi=false, no-GRE, no L3 agents?)...? I mean, I'm trying Quantum without the network-node too (i.e. controller does that job)... So, not off-topic... =) Today, I have Folsom with

Re: [Openstack] Keypair name - unsupported chars?

2013-03-11 Thread Scott Devoid
I can confirm this in Essex as well. I've posted a bug at: https://bugs.launchpad.net/nova/+bug/1144839 ~ Scott On Wed, Mar 6, 2013 at 5:21 AM, Antonio Messina antonio.s.mess...@gmail.com wrote: Hi all, I've just found that nova only accepts alphanumeric chars for keypair name, but it's

Re: [Openstack] Incredibly odd mysql permission error

2013-03-11 Thread Miller, Mark M (EB SW Cloud - RD - Corvallis)
I ran into a similar problem with the Grizzly-3 Keystone release. I had to specify keystone.conf as the config-file with keystone-manage/ db_sync command otherwise it would not use the mysql statement in the keystone.conf file. Mark From:

Re: [Openstack] Incredibly odd mysql permission error

2013-03-11 Thread Samuel Winchenbach
ugh... I had an example file called nova.conf in /root Apparently nova-manage looks for that file first. Case closed. I wish I could get the last week back. Sam On Mon, Mar 11, 2013 at 2:37 PM, Miller, Mark M (EB SW Cloud - RD - Corvallis) mark.m.mil...@hp.com wrote: I ran into a similar

Re: [Openstack] Network node needed?

2013-03-11 Thread JR
Great, thanks Logan. Also, for anyone on the list that aren't aware of it; last night I discovered the Openstack Operations Guide at: http://docs.openstack.org/ops/ It contains lots of answers to questions that I'd not found anywhere else. The only downside is that it doesn't cover quantum.

[Openstack] Agent out of sync with plugin!

2013-03-11 Thread Greg Chavez
So I'm setting up Folsom on Ubuntu 12.10, using the Github Folsom Install Guide: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst After following the steps to instantiate the network node, I'm left with 3 new but downed OVS

[Openstack] Configuring More-than-One Cinder Node

2013-03-11 Thread Craig E. Ward
I have an installation that wants to deploy two or more cinder nodes within an OpenStack (Folsom) cluster. All of the hits I find on Google for configuring cinder only describe how to configure the software for a single node. Is it even possible to have more than one node running the cinder

Re: [Openstack] Configuring More-than-One Cinder Node

2013-03-11 Thread Debashis Kundu (dkundu)
O - Original Message - From: Craig E. Ward [mailto:cw...@isi.edu] Sent: Monday, March 11, 2013 05:23 PM To: openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: [Openstack] Configuring More-than-One Cinder Node I have an installation that wants to deploy two or more

Re: [Openstack] Cinder volume as root in Grizzly?

2013-03-11 Thread Vishvananda Ishaya
Not exactly, although you can do something similar in both folsom and grizzly. If you have a volume snapshot you can pass it in the block_device_mapping when you boot an instance and nova will automatically create a volume from the snapshot and boot from it. If you also set delete_on_terminate

Re: [Openstack] Cinder volume as root in Grizzly?

2013-03-11 Thread Logan McNaughton
Oh great! I didn't realize you can create a cinder volume from an image. So can I pass cinder a QCOW2 image, then boot from that volume? On Mar 11, 2013 7:16 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: Not exactly, although you can do something similar in both folsom and grizzly. If you

Re: [Openstack] Configuring More-than-One Cinder Node

2013-03-11 Thread Logan McNaughton
You'll want to look here: http://docs.openstack.org/trunk/openstack-ha/content/s-cinder-api.html You'll need to basically create a virtual IP and load balance between the nodes running cinder-api and cinder-scheduler. If you want multiple nodes running cinder-volume, you can add them regularly,

Re: [Openstack] Tempest for Integration testing of Openstack (FOLSOM)

2013-03-11 Thread Masayuki Igawa
Hi, On Tue, Mar 12, 2013 at 1:14 AM, Girija Sharan girijasharansi...@gmail.comwrote: Hi All, I am trying to do Integration testing of Openstack environmment (Folsom) using Tempest. On controller node I am having my Tempest root directory and I have also installed Coverage, Tissue and

Re: [Openstack] Agent out of sync with plugin!

2013-03-11 Thread Logan McNaughton
It looks like it's a time sync error. Are you using NTP on all your nodes? On Mar 11, 2013 6:14 PM, Greg Chavez greg.cha...@gmail.com wrote: So I'm setting up Folsom on Ubuntu 12.10, using the Github Folsom Install Guide:

[Openstack] the ip_forward is enable when using vlan + multi_host on computer node

2013-03-11 Thread Lei Zhang
Hi all, I am testing the nova-network + vlan + multi_host. But I found that the ip_forward is enable automatically when launch new instances. You can check the code https://github.com/openstack/nova/blob/master/nova/network/linux_net.py#L770 I found there is some issue seriously when the

Re: [Openstack] Tempest for Integration testing of Openstack (FOLSOM)

2013-03-11 Thread Girija Sharan
Hi Masayuki, Thanks a lot for your early response. I am using Openstack Folsom and not Devstack. I am not getting how to integrate Tempest for Folsom. As you mentioned there is tempest.conf.sample file but in that there is a field which requires path to nova source directory (source_dir =

[Openstack-ubuntu-testing-notifications] Build Failure: raring_grizzly_nova_trunk #867

2013-03-11 Thread openstack-testing-bot
Title: raring_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/867/Project:raring_grizzly_nova_trunkDate of build:Mon, 11 Mar 2013 02:09:34 -0400Build duration:35 secBuild cause:Started by user Adam GandelmanBuilt

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #868

2013-03-11 Thread openstack-testing-bot
Title: raring_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/868/Project:raring_grizzly_nova_trunkDate of build:Mon, 11 Mar 2013 02:10:36 -0400Build duration:34 secBuild cause:Started by user Adam GandelmanBuilt

[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #869

2013-03-11 Thread openstack-testing-bot
Title: raring_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/869/Project:raring_grizzly_nova_trunkDate of build:Mon, 11 Mar 2013 02:11:45 -0400Build duration:33 secBuild cause:Started by user Adam GandelmanBuilt

[Openstack-ubuntu-testing-notifications] Build Fixed: raring_grizzly_nova_trunk #870

2013-03-11 Thread openstack-testing-bot
Title: raring_grizzly_nova_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/870/Project:raring_grizzly_nova_trunkDate of build:Mon, 11 Mar 2013 02:18:34 -0400Build duration:36 secBuild cause:Started by user Adam GandelmanBuilt

[Openstack-ubuntu-testing-notifications] Build Failure: raring_grizzly_python-quantumclient_trunk #52

2013-03-11 Thread openstack-testing-bot
Title: raring_grizzly_python-quantumclient_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_python-quantumclient_trunk/52/Project:raring_grizzly_python-quantumclient_trunkDate of build:Mon, 11 Mar 2013 03:37:16 -0400Build duration:66 msBuild

[Openstack-ubuntu-testing-notifications] Build Failure: precise_grizzly_python-cinderclient_trunk #41

2013-03-11 Thread openstack-testing-bot
Title: precise_grizzly_python-cinderclient_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-cinderclient_trunk/41/Project:precise_grizzly_python-cinderclient_trunkDate of build:Mon, 11 Mar 2013 03:37:16 -0400Build duration:69 msBuild

[Openstack-ubuntu-testing-notifications] Build Failure: precise_essex_horizon_stable #34

2013-03-11 Thread openstack-testing-bot
Title: precise_essex_horizon_stable General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_horizon_stable/34/Project:precise_essex_horizon_stableDate of build:Mon, 11 Mar 2013 03:37:16 -0400Build duration:66 msBuild cause:Started by an SCM changeBuilt

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_grizzly_python-cinderclient_trunk #42

2013-03-11 Thread openstack-testing-bot
cause:Started by user James PageBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 2 builds failed.50ChangesNo ChangesConsole Output[...truncated 2122 lines...]Finished at 20130311-0341Build needed 00:00:45, 2224k disc spaceINFO:root:Uploading package

[Openstack-ubuntu-testing-notifications] Build Fixed: raring_grizzly_python-quantumclient_trunk #53

2013-03-11 Thread openstack-testing-bot
cause:Started by user James PageBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 2 builds failed.50ChangesNo ChangesConsole Output[...truncated 2319 lines...]Finished at 20130311-0342Build needed 00:00:42, 2908k disc spaceINFO:root:Uploading package to ppa:openstack

[Openstack-ubuntu-testing-notifications] Jenkins build is back to normal : cloud-archive_folsom_version-drift #10370

2013-03-11 Thread openstack-testing-bot
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10370/ -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe :

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_essex_horizon_stable #35

2013-03-11 Thread openstack-testing-bot
on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 2 builds failed.50ChangesNo ChangesConsole Output[...truncated 5272 lines...]Finished at 20130311-0405Build needed 00:01:32, 21328k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing/essex-stable-testinggpg

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_folsom_cinder_stable #147

2013-03-11 Thread openstack-testing-bot
Title: precise_folsom_cinder_stable General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_cinder_stable/147/Project:precise_folsom_cinder_stableDate of build:Mon, 11 Mar 2013 04:01:24 -0400Build duration:4 min 12 secBuild cause:Started by an SCM changeBuilt

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_grizzly_keystone_trunk #191

2013-03-11 Thread openstack-testing-bot
Title: precise_grizzly_keystone_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_keystone_trunk/191/Project:precise_grizzly_keystone_trunkDate of build:Mon, 11 Mar 2013 10:11:58 -0400Build duration:8 min 57 secBuild cause:Started by user James

[Openstack-ubuntu-testing-notifications] Build Fixed: raring_grizzly_keystone_trunk #204

2013-03-11 Thread openstack-testing-bot
Title: raring_grizzly_keystone_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_keystone_trunk/204/Project:raring_grizzly_keystone_trunkDate of build:Mon, 11 Mar 2013 10:12:03 -0400Build duration:9 min 51 secBuild cause:Started by user James

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_grizzly_ceilometer_trunk #131

2013-03-11 Thread openstack-testing-bot
Title: precise_grizzly_ceilometer_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_ceilometer_trunk/131/Project:precise_grizzly_ceilometer_trunkDate of build:Mon, 11 Mar 2013 11:50:53 -0400Build duration:4 min 0 secBuild cause:Started by user James

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_grizzly_nova_trunk #789

2013-03-11 Thread openstack-testing-bot
Title: precise_grizzly_nova_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/789/Project:precise_grizzly_nova_trunkDate of build:Mon, 11 Mar 2013 14:08:56 -0400Build duration:14 minBuild cause:Started by user James PageBuilt

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_glance_stable #208

2013-03-11 Thread openstack-testing-bot
Title: precise_folsom_glance_stable General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_glance_stable/208/Project:precise_folsom_glance_stableDate of build:Mon, 11 Mar 2013 20:31:25 -0400Build duration:2 min 18 secBuild cause:Started by an SCM changeBuilt

[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_glance_stable #206

2013-03-11 Thread openstack-testing-bot
Title: quantal_folsom_glance_stable General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_glance_stable/206/Project:quantal_folsom_glance_stableDate of build:Mon, 11 Mar 2013 20:33:44 -0400Build duration:2 min 28 secBuild cause:Started by an SCM changeBuilt

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_essex_nova_stable #66

2013-03-11 Thread openstack-testing-bot
Title: precise_essex_nova_stable General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_nova_stable/66/Project:precise_essex_nova_stableDate of build:Mon, 11 Mar 2013 22:02:45 -0400Build duration:14 minBuild cause:Started by an SCM changeBuilt

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_essex_deploy #18363

2013-03-11 Thread openstack-testing-bot
Title: precise_essex_deploy General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_deploy/18363/Project:precise_essex_deployDate of build:Mon, 11 Mar 2013 22:17:40 -0400Build duration:14 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_essex_test #600

2013-03-11 Thread openstack-testing-bot
Title: precise_essex_test General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_test/600/Project:precise_essex_testDate of build:Mon, 11 Mar 2013 22:32:25 -0400Build duration:5 min 59 secBuild cause:Started by command line by jenkinsBuilt on:masterHealth