| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
This allows the subsequent DHCP request to get the same IP address back,
which means it only needs one address for first boot, and the address
can be pre-allocated by the DHCP server before deployment.
This is needed for the floating address range to be allocated in some
set-ups, such as our local one at the office, where a subnet in a
different class is routed to the server.
|
| |
|
|
|
|
|
|
|
| |
This adds masking config for the virtual devices to prevent them from
attempting to DHCP, and stops us from giving the ip of eno1 to the
bridge device, since eno1's address was obtained by DHCP, so it's
against the rules to statically allocate that address to an interface.
Now, we DHCP for a new address for the bridge.
|
| |
|
|
|
|
| |
If we leave that interface with its address, then the routing table is
incorrect, as it will try to send connections out from an interface that
cannot handle them.
|
| |
|
|
|
|
|
|
|
|
| |
After the external interface has been bound to Open vSwitch, we should
not attempt to DHCP on it, as it won't receive the DHCP responses.
Attempting to DHCP results in startup stalling on network-online.target,
because systemd-networkd-wait-online.service looks at every network
interface it should configure based on the [Match] sections, and waits
for all of them to be configured by systemd-networkd, which will never
finish if DHCP is broken.
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Installing rootwrap filters from their repositories will
make easy to deal with updates. Also move neutron rootwrap
filters to the right location without duplication.
|
|
|
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
|
