python-pip package from canocnical for trusty is old.
It causes resolving dependencies problem when "pip install".
This fixes it.
Change-Id: I9134d9d46eba3e9c37167552bf90758690b62ecf
Closes-Bug: #1595792
By adding `kolla-ansible pull` before the deployment, it may help to
guarantee a successful deployment, and avoid polluting the host
environment due to the failure of the deployment.
Change-Id: I951a3093ca02601ed6c0469e626fcd92bd1297c1
There was an unwanted line break in the systemd file preventing the proxy from
being configured correctly.
TrivialFix
Change-Id: I3e6413d4f2d373951cb558e0af1b8bc92d4cbb91
Instead of using the same logger for all the things
which makes it incredibly hard to figure out what the images
and there builds are doing; instead have it so that each
image gets its own logger which is then used by tasks that
process that image.
Each images logs now will (optionally) go to a logs directory
that can be more easily read and looked over and leaves
the main logger for informational/task kind of
output only.
Closes-Bug: #1586478
Change-Id: I939e073a2bc5ed8b5a1e969888fc743d80f468c9
Cinder has closed a flaw in the design of either glance, cinder, or
OpenStack in general. Whatever the case is, LVM + multi-controller
doesn't work correctly.
TrivialFix
Change-Id: Ibe3445699cfdb1622279a85b6c4e612663d08def
To customize apt packages, you need to do something like that in
override file:
{% set base_apt_packages = base_apt_packages + ['vim', 'emacs'] %}
Change-Id: I7913ed405c2cb7e33f1cfe310d651030e0700e6b
Partially-implements: blueprint third-party-plugin-support
VM instance state (e.g., instance.xml) should be persistent
regardless of nova-libvirt container.
Change-Id: I4463d0634db2aaefde7dc2c45a144e920d9cb1ac
Closes-Bug: #1569828
This introduces a new configuration parameter neutron_enable_qos to
be able to enable the Neutron QoS service plugin.
More details about the Neutron QoS service plugin are available at:
http://docs.openstack.org/liberty/networking-guide/adv-config-qos.html
Change-Id: I8525bf4dce5f1e225f72a4e1c3760b64a36b17f6
Closes-bug: #1593183
Implements: bp netowrking-qos
Since this is the user for which we setup the SSH key.
This commit allows to run kolla-ansible as vagrant user without using
sudo.
This only applies to multinode.
TrivialFix
Change-Id: Ie5231085a66511a520d4dbe5e9f35414acf1900b
The regex used previously would keep the short hostname (hostname -s)
on the 127.0.0.1 line.
Reset the 127.0.0.1 line to keep only localhost.
TrivialFix
Change-Id: I90bdec6793ac5b2d304e178e5114369b7b3b9626
The SUPPORT_NODE variable was missed during a refactoring of
bootstrap.sh and is now unused. Remove it.
TrivialFix
Change-Id: I10ab4368b383dbb620916f70c368153403944001
In vagrant environments, the kolla_internal_vip_address didn't belong
to the private network provisioned on the machine and was failing the
prechecks.
TrivialFix
Change-Id: I0e7e4d134e350c49ef7510c7262677754a83bcbf
This allows us to execute vagrant commands by default on the 'operator'
VM and eliminate one of the difference between AIO and multinode.
TrivialFix
Change-Id: Ia14aa026d1146ec4b1e006c72a2460edfc0cf6eb
This patch check two senario
first if we choose to start a new container
with name say XXX, however in the env a container
already exist with XXX name and second to start a stopped container.
Change-Id: Ibd6c5fbcc6f37ea2481634ac2e6b3edb91ae7aab
Partially-Implements: blueprint ansible-unit-tests
When kolla_internal_vip_address didn't belong to the same network as
network_interface, the prechecks would spit out an ugly error:
Unexpected templating type error occurred on [snip]:
argument of type 'NoneType' is not iterable"
This commit fixes the check to execute properly.
Change-Id: I24a066c212c78e105a923525b131724736ac74b6
The Nova EC2 API is disabled by default, the default value
of the enabled_apis parameter in nova.conf is "osapi_compute, metadata"
The EC2 API is marked as deprecated and will be removed from Nova in
the future.
Change-Id: I6b9d66017e066cde5749be45b367194d2192ead3
Closes-bug: #1586605