The current example for including mtu is not suitable for all docker
version and distros. Fox example, the latest docker-ce 17.06 does not
support docker "docker daemon" command. And also docker doesn't
support socket parameter "fd://" on rpm based systems. We need to add
a note to remind user not copy that configuration straightly.
Change-Id: I8f2e0697eefe89abbe7da29612a625c4094c954e
The docker-py python module is now called docker and has an
incompatible api. Running latest kolla-ansible with docker-py
will throw an error like this:
AttributeError: 'module' object has no attribute 'APIClient'
Change-Id: Idd10735c764717cf711f62b3243d39d8c8ed263f
Tacker has become a complex service to deploy in pike
release, adding a bunch of other services dependencies.
This guide aims to ease users to deploy tacker.
Change-Id: Ibe15bee9438fed0cd09b3cabcb270b551fb13b87
Mistral requires redis as of pike release,
notify users about this new feature and make sure
updrades enables redis.
Change-Id: I41e82869d036673181b4dba05ad07089691d0357
* Remove redundant info, e.g. 'kolla can deploy the cinder services'
* List the available backends Kolla supports
* The bug wrt to lvm with multiple control nodes is open rather than
'WontFix', update the note to reflect this.
* Document how to configure the NFS backend
Change-Id: I1621efa35a329676ecaf309d60f578d33d8aa0d4
modify /etc/kolla/config/cinder/ceph.conf,
run kolla-ansible reconfigure but
in the container /etc/ceph.conf has not changed
Change-Id: I3bd55f76295b9ad1b799db9e910dbd0cd03d417c
Rollout redis container in master/slave configuration
Deploy redis-sentinel and connect to redis cluster
Redis is needed for mistral coordination backend.
Partial-Bug: #1700591
Change-Id: Ic0269d0db10624925e7bcdbf0e33ae87b84a9cf2
Upgrade fails as outward_rabbitmq does not exist
and cannot therefore be upgraded. Omit it from the
upgrade check and bootstrap it after rabbitmq upgrade.
Remove jinja2 from 'Find gospel node' task; removes warnings.
Change-Id: I3766271c62779c8dbd31e7cf2300473815bbbe68
Tacker has included a new conductor service
to manage mistral workflows for VIM monitoring.
Without conductor, Tacker cannot create VIMs.
This change reworks tacker to include tacker-conductor
service.
Depends-On: I52778e86e4f2c297ead8d4b09983e5e38ca88c70
Closes-Bug: #1710874
Change-Id: I6901e919887551bedc9dba8983ac904e8c48c9ce
Fluentd repo/packages are changed in depends changes below.
Rpm distros need changes in their config for properly
start and deploy fluentd containers.
Change-Id: I474c4d20c407717c6da973383bbbd5539be480f1
Depends-On: I4802618373cfa53d67d1dfe65be7abe1950b3d04
This reverts commit 91321ac8ff342ad8276c6874f85b7ad3a823a444.
The reasoning given in this commit is incorrect. Keystone/oslo.cache
uses memcached hosts based on a hashing of the key to determine which
memcached host to check. If you have different configured memcached
servers per keystone deployment you have a mis-configured deployment.
Any RESTapi should be capable of roundrobin load-balancing. I am not
familiar with the Murano case with uploading a package, but this change
also does not address Murano at all.
As far as Horizon goes, that hasn't had a problem with shared backends
since the beginning because we use memcached servers with a shared
secret key [1].
All this change has done is lowered the efficiency of loadbalancing
keystone.
[1] https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/horizon/templates/local_settings.j2#L149
Change-Id: Ic0b550e7c96d67c39153933b527ab3edf7d90f27
This access is now mandatory for skydive.
It allows to add netns info to the topology, and to
attach interfaces to their netns if needed.
Closes-Bug: #1710627
Change-Id: I41cc1fd0fdeae0757a2c4e3e310ec6375da0b8cf
