| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | OpenStack: modify controller to be able to talk to both console | Amy Fong | 2014-03-25 | 1 | -119/+0 |
| | | | | | | | | | | | | | | | | 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 <amy.fong@windriver.com> | ||||
| * | OpenStack: nova-novncproxy:can't stop this service | Amy Fong | 2014-03-24 | 1 | -0/+119 |
| 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 <amy.fong@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> | |||||
