| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
This enables serial console access to local nodes from the host machine
by running `novaconsole $VM_NAME` after it has been installed by running
pip install git+http://github.com/larsks/novaconsole.git
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This should be handled by neutron, and except for the mis-configuration,
it should have been.
However, since both neutron and nova were configured to handle
firewalling, they would both install their firewall rules into iptables,
and it would be random which one would be used as either service is
likely to start before the other and install their hook first.
The result being that we'd randomly not be able to reach VMs after a
reboot, unless we'd installed the same firewall rules in both nova and
neutron.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The ip of the compute node is gotten from the bridge device and
this value is set in the novncproxy configuration in nova.conf.
This is required for horizon to access to the compute node so
have access to the VMs created on it.
Also:
- remove /usr/share/vnc which is now created in the vnc chunk.
- add explicity where to find novnc client to nova-novncproxy systemd
unit.
|
|
TODO: Split this out into:
1. initial config (openstack/etc) default values
2+. as many individual changes to initial config as possible to extract,
including support scripts and configuration extensions
|