Re: [Netstack] latest stack.sh - failed to run with quantum

2012-03-23 Thread Rohit Agarwalla (roagarwa)
Thanks Dave and Shweta. Works ! >-Original Message- >From: David Lapsley [mailto:dlaps...@nicira.com] >Sent: Friday, March 23, 2012 10:40 AM >To: Rohit Agarwalla (roagarwa) >Cc: Dan Wendlandt; netstack@lists.launchpad.net >Subject: Re: [Netstack] latest stack.sh -

Re: [Netstack] latest stack.sh - failed to run with quantum

2012-03-23 Thread Rohit Agarwalla (roagarwa)
: Rohit Agarwalla (roagarwa) Cc: netstack@lists.launchpad.net Subject: Re: [Netstack] latest stack.sh - failed to run with quantum Its working for me. Did you "git pull" within the devstack directory to make sure you have the latest devstack? Devstack is updated pretty frequently

[Netstack] latest stack.sh - failed to run with quantum

2012-03-23 Thread Rohit Agarwalla (roagarwa)
Hi guys, Tried setting up a fresh devstack and seeing a similar issue as is suggested here - https://answers.launchpad.net/devstack/+question/191325 devstack experts, please comment. Thanks Rohit -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.ne

Re: [Netstack] Quantum and Keystone

2012-03-23 Thread Rohit Agarwalla (roagarwa)
Message- >From: Deepak Garg [mailto:deepakgarg.i...@gmail.com] >Sent: Friday, March 23, 2012 3:36 AM >To: Dan Wendlandt >Cc: Rohit Agarwalla (roagarwa); gkot...@redhat.com; >netstack@lists.launchpad.net >Subject: Re: [Netstack] Quantum and Keystone > >Thanx Dan. I had a

Re: [Netstack] Quantum and Keystone

2012-03-23 Thread Rohit Agarwalla (roagarwa)
Message- >From: Deepak Garg [mailto:deepakgarg.i...@gmail.com] >Sent: Friday, March 23, 2012 3:36 AM >To: Dan Wendlandt >Cc: Rohit Agarwalla (roagarwa); gkot...@redhat.com; >netstack@lists.launchpad.net >Subject: Re: [Netstack] Quantum and Keystone > >Thanx Dan. I had a

Re: [Netstack] Quantum and Keystone

2012-03-21 Thread Rohit Agarwalla (roagarwa)
I had tried to resolve this issue at my end just prior to RC1 period as well (had pointed it out to a limited group then). Couple of config changes in quantum.conf that worked for me are as follows - [filter:authN] #this is using the default auth_token.py in keystone middleware paste.filter_