The dot files were missing from the retirement.
Update the documentation to point to the correct SHA hash.
Change-Id: I9da7e1d5016da0cdc5160a417324f766a75119ee
The core reviewer team voted with majority to retire this project.
The full thread of the retirement can be found here:
http://lists.openstack.org/pipermail/openstack-dev/2016-April/093180.html
Change-Id: I1599167bb948a186547cf9d270d37cb2d2cec4fd
Depends-On: Ief32a399d0ff57332864c65d5380269051e24b6b
The bootstrap script for Vagrant did not add the vagrant user to the
docker group. That caused all docker commands, not executed with sudo,
to fail. This commit adds the vagrant user to the docker group, which
permits execution of docker commands without sudo.
Change-Id: I56e6372c8b3a4559051f7be1a8fd7528dcbacc53
Closes-Bug: #1563405
Signed-off-by: Andrei-Lucian Șerb <lucian.serb@icloud.com>
The provisioning script for Vagrant was using an old docker private
registry. This commit changes the private registry to version 2, since
it is now the recommended version.
Change-Id: If48edb33393b692a8892843639ab3e88e5fd44f9
Closes-Bug: #1563386
Signed-off-by: Andrei-Lucian Șerb <lucian.serb@icloud.com>
In the Vagrantfile, when using VirtualBox, the IP used for the
hostmanager plugin is retrieved from the wrong network adapter. This
causes the hostmanager to insert the wrong IP address in /etc/hosts. The
NIC numbering starts from 0, and the one used in the code is 2. That
corresponds to the 3rd NIC, which is actually used as the interface to
the Neutron external network. This commit sets the NIC number to 1,
which represents the internal network used by OpenStack.
Change-Id: I87f2b081c57c8eb3109e8d98b75ee438dd0d4b82
Closes-Bug: #1563367
Signed-off-by: Andrei-Lucian Șerb <lucian.serb@icloud.com>
This commit introduces a clear order of loading jvars:
- passwords.yml
- globals.yml
- custom variables based on globals.yml
- config/<service>/all.yml
- config/<service/[...]
It also introduces a mechanism of jinja2 templating yaml
files by themselves, which means that one variable in yaml
file can be reused in the next variables inside the same file.
TrivialFix
Change-Id: I1a7a61e90963d396702f5e0c14eb476d3ccd21bf
To ensure that the requests_mock will work everywhere, we have
to override the host setting.
TrivialFix
Change-Id: Ia4c51c913b03f6926f83c8cb5616bb1e757fcd37
On computers with wi-fi adapters, promiscuous mode on the VirtualBox (or
maybe other hypervisors as well) NICs does not work, which means the
default way of connecting the Neutron external interface to a bridged
adapter, will not allow communication to and from the Nova VMs over
floating IPs with any computer on the external network (except the host
computer) or with the wi-fi router. This means no ability to connect to
the Nova VMs and no internet access inside the Nova VMs.
According to VirtualBox documentation (excerpt): "Bridging to a wireless
interface is done differently from bridging to a wired interface,
because most wireless adapters do not support promiscuous mode. All
traffic has to use the MAC address of the host’s wireless adapter, and
therefore VirtualBox needs to replace the source MAC address in the
Ethernet header of an outgoing packet to make sure the reply will be
sent to the host interface. When VirtualBox sees an incoming packet with
a destination IP address that belongs to one of the virtual machine
adapters it replaces the destination MAC address in the Ethernet header
with the VM adapter’s MAC address and passes it on. VirtualBox examines
ARP and DHCP packets in order to learn the IP addresses of virtual
machines."
To fix this issue, a new flag has been introduced: WIFI. If true, the
default Vagrant public network is not created anymore. Instead, the 3rd
NIC will be connected to a NAT-Network named OSNetwork. The NAT-Network
has a virtual gateway, which will be used to communicate with the
external physical wi-fi router. Since Vagrant does not have a high-level
mechanism to attach an adapter to a NAT-Network, the code uses the
low-level Vagrant construct vm.customize which makes it provider
specific.
Promiscuous mode is now activated by default on the 3rd NIC.
The WIFI flag is false by default.
This commit only addresses VirtualBox, and it is currently unknown if
the problem described and fixed in this commit is present in other
hypervisors.
DocImpact
Closes-Bug: #1560274
Change-Id: I22517d055cfdcbe70e4c34a0dba611d0ed50dcc3
Signed-off-by: Andrei-Lucian Șerb <lucian.serb@icloud.com>
Checking for "_enabled" attriture in Runner class and its subclasses
didn't happen everywhere it's needed. This commit simplified this
check and does it in every needed place.
TrivialFix
Change-Id: Ib901e8f26cb870d6fbf08b557467bca6427de217
The new kolla-mesos CLI fails when some service in the profile
is not implemented. That required the following changes in all
profiles:
- remove the kolla-toolbox and openvswitch services, because
they're included in the other ones
- remove the haproxy and keepalived profiles, because we will
load balance services by the other more Mesos-compatible way
- remove all not yet implemented services (ceph, ceilometer,
heat etc.)
TrivialFix
Change-Id: I6afe70c9b992e82debe9446661eb1da304952453
- all zookeeper node writes must have string encoded and reads decoded
- list(zip())
- file mocking
Change-Id: I0e858c179cac587ee965aa57c0245050c41dc51a
kolla-mesos commands list <service>
show_tasks.py will be replaced with
this command
partial blueprint per-service-cli
Change-Id: I0fe2f4d3d70e698e2cb3af762572f5f2317292bb
These are to replace the current
kolla-mesos-deploy
kolla-mesos-cleanup
Make scripts that redirect to the new commands.
partial blueprint per-service-cli
Change-Id: Id730a1480b97e1059a7d04dd066b62156a028d20