settingsLogin | Registersettings

[Openstack] Additional Compute won't enable console service

0 votes

Now that almost everything in my cloud is looking like
it's working almost perfectly (except a few minor issues
here and there), I decided to provision the other hosts
as Computes.

Everything on the new node(s) come up as it should (from
what it seems now anyway), but NOT the console service(s)!

When I had only one Control and one Compute, it worked just
fine. But as soon as I added a second (and third etc) Compute,
it just stopped working..

Please correct me if I'm wrong, but the following services
(packages) should be installed on the Control(s):

nova-api
nova-conductor
nova-consoleauth
nova-consoleproxy
nova-scheduler
nova-volume
spice-html5

And on the Compute(s):

nova-compute
nova-compute-kvm
nova-console

The configuration on the Control:

[spice]
html5proxy_host = 0.0.0.0
html5proxy_port = 6082
html5proxy_base_url = http://control:6082/spice_auto.html
server_listen = 0.0.0.0
server_proxyclient_address = control
enabled = true
agent_enabled = false

And the Compute console should connect to the Control:

[spice]
html5proxy_host = 0.0.0.0
html5proxy_port = 6082
html5proxy_base_url = http://control:6082/spice_auto.html
server_listen = 0.0.0.0
server_proxyclient_address = control
enabled = true
agent_enabled = true

The service list (bladeA0[12] is Control nodes, all other are
Compute nodes):

bladeA01:/etc/nova# nova-manage service list 2> /dev/null
Binary           Host                                 Zone             Status     State Updated_At
nova-osapi_compute 0.0.0.0                              internal         enabled    XXX   None
nova-metadata    0.0.0.0                              internal         enabled    XXX   None
nova-conductor   bladeA01                             internal         enabled    :-)   2016-07-24 18:05:10
nova-scheduler   bladeA01                             internal         enabled    :-)   2016-07-24 18:05:15
nova-compute     bladeA03                             nova             enabled    :-)   2016-07-24 18:05:14
nova-compute     bladeA05                             nova             enabled    :-)   2016-07-24 18:05:11
nova-consoleauth bladeA01                             internal         enabled    :-)   2016-07-24 18:05:15
nova-compute     bladeA04                             nova             enabled    :-)   2016-07-24 18:05:07
nova-console     bladeA03                             internal         enabled    :-)   2016-07-24 18:05:42
nova-console     bladeA05                             internal         enabled    XXX   2016-07-24 19:04:26
nova-console     bladeA04                             internal         enabled    XXX   2016-07-24 19:04:34

The 'bladeA03' was the first Compute being installed. That
still seems to be enabled, so maybe I've missed to document
a step to get this to work..
--
God gave man both a penis and a brain,
but unfortunately not enough blood supply
to run both at the same time.
- R. Williams


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
asked Jul 24, 2016 in openstack by Turbo_Fredriksson (8,980 points)   7 13 19

1 Response

0 votes

Never mind. Time issues. Forgot to make sure to "download" the
right time. I forgot that ntpd don't do that initially.

responded Jul 24, 2016 by Turbo_Fredriksson (8,980 points)   7 13 19
...