<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-cloud-services.git/meta-openstack/recipes-devtools/python/python-nova/nova-console.init, branch rocko</title>
<subtitle>Mirror of git.yoctoproject.org/meta-cloud-services.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-cloud-services.git/atom?h=rocko</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/atom?h=rocko'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/'/>
<updated>2014-03-25T13:56:15+00:00</updated>
<entry>
<title>OpenStack: modify controller to be able to talk to both console</title>
<updated>2014-03-25T13:56:15+00:00</updated>
<author>
<name>Amy Fong</name>
<email>amy.fong@windriver.com</email>
</author>
<published>2014-03-24T17:18:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/commit/?id=dfc85232382af8fee180a83bd33f9d436557b774'/>
<id>urn:sha1:dfc85232382af8fee180a83bd33f9d436557b774</id>
<content type='text'>
We modify the controller so that both vnc and spice html5 proxies are running.
Since in the current recipe, both controller and compute share the same nova.conf
file, in the compute, both vnc and spice html5 are set to enabled and in this
configuration, vnc is chosen (in source: vnc is chosen because it's better
tested).

To change to spice, only change required is on the compute side.

The controller (since the default console_type is auto) will try to talk
to both and run whichever is available.

Signed-off-by: Amy Fong &lt;amy.fong@windriver.com&gt;
</content>
</entry>
<entry>
<title>OpenStack: nova-novncproxy:can't stop this service</title>
<updated>2014-03-24T20:53:27+00:00</updated>
<author>
<name>Amy Fong</name>
<email>amy.fong@windriver.com</email>
</author>
<published>2014-03-21T21:07:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/commit/?id=ec4dd1f12eff5aab513845cafa87fbec8166adff'/>
<id>urn:sha1:ec4dd1f12eff5aab513845cafa87fbec8166adff</id>
<content type='text'>
nova-novncproxy and nova-spicehtml5proxy both do not check to see if the process
specified in PIDFILE exists before firing off a new one. Both initrd files can
actually use nova.init (used for the many other nova-* daemons)

nova-consoleauth also has this issue, we add a check in start to see if the process
in PIDFILE exists and exits if it does.

Signed-off-by: Amy Fong &lt;amy.fong@windriver.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
</content>
</entry>
</feed>
