summaryrefslogtreecommitdiff
path: root/openstack/usr/share/openstack/openstack-neutron-network-configuration-for-one-node
Commit message (Collapse)AuthorAgeFilesLines
* openstack-net-config: Check whether we need to run before gethering network ↵Richard Maw2015-03-231-4/+4
| | | | config
* Move patch link creation into openvswitchRichard Maw2015-03-231-19/+15
| | | | | | | | | | 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.
* Rejigger networking so the bridge has the MAC of the external interfaceRichard Maw2015-03-231-9/+20
| | | | | | | | | | 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.
* Ensure newly brought up devices are correctly configuredRichard Maw2015-03-231-16/+21
| | | | | | | | | 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.
* Deallocate IP address from bound interface after bindingRichard Maw2015-03-231-0/+3
| | | | | | 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 initial switching setup, switch DHCP to external ifaceRichard Maw2015-03-231-0/+15
| | | | | | | | | | 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.
* WIP: Add OpenStack initial configurationRichard Maw2015-03-231-0/+56
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