| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Also change placehoders to jinja2 type
|
| |
|
|
| |
They are now being installed with neutron
|
| |
|
|
| |
Also change placeholders to jinja2 type
|
| |
|
|
| |
These files are being installed with nova
|
| |
|
|
|
|
|
| |
documentation
See http://www.freedesktop.org/software/systemd/man/systemd.unit.html for more
information
|
| | |
|
| |
|
|
| |
This will make the experience more pleasant
|
| | |
|
| |
|
|
|
| |
Now horizon-setup also configures Apache, given that they will be in
the same host. This can be split in different setup scripts.
|
| | |
|
| |
|
|
| |
Also change systemd units and configure extension to match this change
|
| |
|
|
| |
These files are being installed with cinder.
|
| |
|
|
| |
Also change placeholders to jinja2 type
|
| |
|
|
| |
Also change systemd units and configure extension to match this change
|
| |
|
|
| |
Also change placeholders to jinja2 type
|
| | |
|
| |
|
|
|
|
| |
Now keystone-setup also configures postgres and rabbitmq. This can be
split in different setup scripts, but I think that rabbitmq, postgres,
are likely to be in the controller node.
|
| |
|
|
| |
Also change placeholders to jinja2 type
|
| |
|
|
| |
Also remove quotes from the Environment variable.
|
| | |
|
| |
|
|
| |
created in chunk)
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
This is required for Open vSwitch to be able to signal that every
network interface required has been configured.
It also means we no longer need to set the links to promiscuous mode
ourselves, since interfaces need to be set in promiscuous mode to allow
bridging to work and Open vSwitch handles this responsibility if it is
configured to be the one to do the link setup.
|
| |
|
|
|
|
|
|
|
| |
ovs-cleanup is responsible for reconciling the state in openvswitch's
database and neutron's configuration.
This can fail if other services are also changing ovs configuration
though, and the missing dependency resulted in neutron removing the
interface while ovs-cleanup was about to do so.
|
| |
|
|
|
|
|
| |
We want the network links to be configured before we start
systemd-networkd, because we have to use ovs instead of networkd's
config for the interfaces in OpenStack, but we still want to use
networkd to manage DHCP on the interfaces.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Collecting the static files (css, js, png, ...) for horizon, compressing
them and storing them in a folder accessible by horizon, fixes the problem
when some css are not found and improves loading and navigating the pages.
|
| | |
|
| | |
|
|
|
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
|
