The ask.openstack.org website will be read-only from now on. Please ask questions on the openstack-discuss mailing-list, stackoverflow.com for coding or serverfault.com for operations.
 | 1 | initial version |
Hi Max:
I've launched one instance in the following scenario:
- cloud controller (all services except nova-compute)
- nova-compute 1 (only nova-compute service)
- nova-compute 2 (only nova-compute service)
- nova-compute 3 (only nova-compute service)
I asked if nova-compute was necessary on cloud controller because of my instance is not deployed correctly when nova-compute service is not installer on cloud controller. The instance log is:
cloud-init start running: Thu, 24 May 2012 18:16:21 +0000. up 9.85 seconds
2012-05-24 18:17:47,705 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [6/120s]: url error [[Errno 113] No route to host]
2012-05-24 18:17:50,704 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [9/120s]: url error [[Errno 113] No route to host]
2012-05-24 18:17:53,704 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [12/120s]: url error [[Errno 113] No route to host]
2012-05-24 18:19:44,782 - DataSourceEc2.py[CRITICAL]: giving up on md after 123 seconds
no instance data found in start
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
landscape-client is not configured, please run landscape-config.
acpid: starting up with proc fs
acpid: 1 rule loaded
acpid: waiting for events: event logging is off
Starting System V runlevel compatibility[74G[ OK ]
Starting ACPI daemon[74G[ OK ]
Starting save kernel messages[74G[ OK ]
Starting automatic crash report generation[74G[ OK ]
Starting regular background program processing daemon[74G[ OK ]
Starting deferred execution scheduler[74G[ OK ]
Starting CPU interrupts balancing daemon[74G[ OK ]
Stopping save kernel messages[74G[ OK ]
Starting crash report submission daemon[74G[ OK ]
Stopping System V runlevel compatibility[74G[ OK ]