summaryrefslogtreecommitdiff
path: root/openstack
Commit message (Collapse)AuthorAgeFilesLines
* nova: novncproxy_base_url to IP, not hostnamebaserock/pedroalvarez/openstack-ansible-v6Pedro Alvarez2015-03-251-1/+1
|
* nova: disable serial consolePedro Alvarez2015-03-251-1/+1
|
* neutron: onenode hardcoded in ml2_confPedro Alvarez2015-03-251-1/+1
|
* neutron: onenode harcoded in neutron.confPedro Alvarez2015-03-251-1/+1
|
* neutron yml don't create the bridge when br-eth0Pedro Alvarez2015-03-251-0/+1
|
* neutron yml conditionals around getting eth infoPedro Alvarez2015-03-251-2/+8
|
* neutron typo in disable device templatePedro Alvarez2015-03-251-1/+0
|
* neutron.yml, wrong and duplicated codePedro Alvarez2015-03-251-8/+0
|
* neutron.yml, use variables from AnsiblePedro Alvarez2015-03-251-22/+26
|
* neutron yml typoPedro Alvarez2015-03-251-1/+1
|
* neutron yml typoPedro Alvarez2015-03-251-1/+1
|
* neutron fix typo in networkd templatesPedro Alvarez2015-03-251-1/+0
|
* neutron yml fixesPedro Alvarez2015-03-251-3/+4
|
* neutron yml typoPedro Alvarez2015-03-251-1/+1
|
* neutron tml typoPedro Alvarez2015-03-251-1/+1
|
* only one execstart in the neutron-setup servicePedro Alvarez2015-03-251-1/+0
|
* neutron: neutron yml in manifestPedro Alvarez2015-03-251-0/+1
|
* neutron ansible errorPedro Alvarez2015-03-251-11/+10
|
* openvswitch ansible errorPedro Alvarez2015-03-251-2/+2
|
* install serialproxy servicePedro Alvarez2015-03-251-0/+1
|
* neutron: minimize varialbes in conf filesPedro Alvarez2015-03-252-6/+6
|
* neutron: Not install previous file removed and it servicePedro Alvarez2015-03-251-2/+0
|
* neutron: Remove script not needed (ovs configuration one node)Pedro Alvarez2015-03-251-86/+0
|
* neutron: neutron.yml enable neutron servicesPedro Alvarez2015-03-251-4/+9
|
* neutron: openstack-neutron-setup removalPedro Alvarez2015-03-251-1/+0
|
* neutron: Run Ansible scripts in neutron setup unitPedro Alvarez2015-03-252-19/+3
|
* neutron: configure network with ovs in AnsiblePedro Alvarez2015-03-253-0/+108
|
* neutron: add template to disable devicesPedro Alvarez2015-03-251-0/+3
|
* neutron: start ansiblePedro Alvarez2015-03-253-96/+82
|
* Move openvswitch setup to AnsiblePedro Alvarez2015-03-255-60/+40
|
* neutron: Change templates to jinja2 typePedro Alvarez2015-03-252-19/+19
|
* neutron: move templatesPedro Alvarez2015-03-2556-354/+65
|
* Nova configuration to AnsiblePedro Alvarez2015-03-2518-531/+105
|
* Move systemd units to /usr/lib/systemd/system as defined in systemd ↵Francisco Redondo Marchena2015-03-2536-41/+40
| | | | | | | documentation See http://www.freedesktop.org/software/systemd/man/systemd.unit.html for more information
* Horizon to AnsiblePedro Alvarez2015-03-257-107/+29
|
* Cinder setup to ansiblePedro Alvarez2015-03-259-393/+93
|
* Glance configuration in ansiblePedro Alvarez2015-03-2513-118/+89
|
* Keystone configuration to ansiblePedro Alvarez2015-03-2519-251/+179
|
* /etc/hosts: don't resolve hostname as loopbackPedro Alvarez2015-03-211-1/+1
|
* Enable nova serial consoleRichard Maw2015-03-204-2/+22
| | | | | | 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
* Tidy up some nova service enablementRichard Maw2015-03-201-23/+6
|
* Fix openstack-nova-compute.service duplicate descriptionRichard Maw2015-03-201-1/+1
|
* openstack-net-config: Check whether we need to run before gethering network ↵Richard Maw2015-03-201-4/+4
| | | | config
* openstack: Disable nova firewall managementRichard Maw2015-03-201-1/+1
| | | | | | | | | | | | | | 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.
* Move patch link creation into openvswitchRichard Maw2015-03-206-71/+19
| | | | | | | | | | 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.
* Only start neutron-openvswitch-plugin after cleanup has finishedRichard Maw2015-03-201-2/+4
| | | | | | | | | 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.
* Rejigger networking so the bridge has the MAC of the external interfaceRichard Maw2015-03-201-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-201-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-201-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-201-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.
View Lorry Controller Status