I have successfully setup Open Stack cloud from the documentation:UbuntuCloudInfrastructure
But when i run Juju status i see relation error between at cloud-compute against nova-cloud-controller.
When i Run juju debug-log I see following result.
2013-04-02 15:17:52,842 unit:nova-compute/0: statemachine DEBUG: relationworkflowstate: execute action do_error
2013-04-02 15:17:52,843 unit:nova-comput
We're using Puppet to manage an OpenStack installation. OpenStack
consists of a number of loosely connected parts, all communicating via
AMQP.
I'm trying to install openstack on RHEL 6.2.
So playing with nova launcher I said ill try nova prime then decided I wouldnt really use it so returned it but wait my nova launcher is still running on nova prime 2.0 and still have all of tge add ons for prime so has this happend to anyone I did get a return code emailed to me so just woundering???
Under what circumstances would ls -lh show a total that is less than the sum of the individual files?
I have one controller node with CentOS and one compute node with kvm hyperviser. I am using OpenStack.
When I try to launch an instance with OpenStack, I get the following error in nova-compute.log:
(nova.rpc): TRACE: libvirtError: operation failed: domain 'instance-0000000a' already exists with uuid 5f81a7d2-1b0f-8c72-4e1e-377c275e9289
However, virsh doesn't show any domains:
$ sudo virsh list
Id Name State
----------------------------------
Why isn't that domain showing up
On March 20, Canonical published in a security notice details about an OpenStack Nova vulnerability for its Ubuntu 12.10, Ubuntu 12.04 LTS, and Ubuntu 11.10 operating systems.
According to Canonical, a couple of security problems were fixed in Nova.
For example, it was discovered that Nova did not properly validate VNC tokens, after an instance was deleted.
On January 29, Canonical published in a security notice details about an OpenStack Nova vulnerability for its Ubuntu 12.10, Ubuntu 12.04 LTS, and Ubuntu 11.10 operating systems.
According to Canonical, Nova volume could be made to expose volumes from other users.
It was discovered that nova-volume did not validate access to volumes.