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

2013-03-14 Thread Jiang Jim
Yes, you are right, the problem is caused by both exist of n-net and
quantum.
I just add one line, disable_service n-net. It works.

Thank all of you. I will do more test and develop on heat.


2013/3/11 Steven Hardy sha...@redhat.com

 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
  ENABLED_SERVICES+=,heat,h-api,h-api-cfn,h-api-cw,h-eng
  ENABLED_SERVICES+=,quantum,q-svc,q-agt,q-dhcp,q-l3,q-meta
  ENABLED_SERVICES-=n-net

 This last line looks like invalid bash syntax?

 Try:

 ENABLED_SERVICES=$(echo $ENABLED_SERVICES | sed 's/n-net//')

 I suspect the problem is you have quantum and nova networking enabled due
 to
 this bash error in the localrc

 Steve

___
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] [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
 ENABLED_SERVICES+=,heat,h-api,h-api-cfn,h-api-cw,h-eng
 ENABLED_SERVICES+=,quantum,q-svc,q-agt,q-dhcp,q-l3,q-meta
 ENABLED_SERVICES-=n-net

This last line looks like invalid bash syntax?

Try:

ENABLED_SERVICES=$(echo $ENABLED_SERVICES | sed 's/n-net//')

I suspect the problem is you have quantum and nova networking enabled due to
this bash error in the localrc

Steve

___
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] [Heat] Problem with visit 169.254.169.254 from VM

2013-03-08 Thread Clint Byrum
Excerpts from 蒋闻天's message of 2013-03-06 17:09:57 -0800:
 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
 ENABLED_SERVICES+=,heat,h-api,h-api-cfn,h-api-cw,h-eng
 ENABLED_SERVICES+=,quantum,q-svc,q-agt,q-dhcp,q-l3,q-meta
 ENABLED_SERVICES-=n-net
 SWIFT_HASH=nova
 
 When I start a heat stack, I step into my instance console and found
 timeout problem with 169.254.169.254
 
 I ping 169.254.169.254 from my host and is ok, but the vm can't.
 
 I found the Network Topology with a router on it which have connected
 private network and external network. I can ssh on the VM but I do not have
 password.(Key must get from metadata on  169.254.169.254)
 
 Is there some config i have made is wrong?

I've been using devstack with heat for quite some time without these problems.

Have you tried with Quantum instead of nova-network?

Good instructions here:

https://wiki.openstack.org/wiki/QuantumDevstack

___
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] [Heat] Problem with visit 169.254.169.254 from VM

2013-03-06 Thread 蒋闻天
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
ENABLED_SERVICES+=,heat,h-api,h-api-cfn,h-api-cw,h-eng
ENABLED_SERVICES+=,quantum,q-svc,q-agt,q-dhcp,q-l3,q-meta
ENABLED_SERVICES-=n-net
SWIFT_HASH=nova

When I start a heat stack, I step into my instance console and found
timeout problem with 169.254.169.254

I ping 169.254.169.254 from my host and is ok, but the vm can't.

I found the Network Topology with a router on it which have connected
private network and external network. I can ssh on the VM but I do not have
password.(Key must get from metadata on  169.254.169.254)

Is there some config i have made is wrong?
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp