Add documentation for the commit I084e5d1cc8f9993d65167878f9983ad58a68e86e.
Explain how 'build.py' picks up automatically env proxy variables.
Change-Id: Ia8513babd4ff72ed52e167b361d6b54393598a78
Closes-Bug: #1538108
Every now and then people ask about plugins for Kolla. This conversation
may need to be revisted in more detail soon, but till then it's worth
highlighting what we do currently support in Kolla.
Right now adding the block as shown in this patch will make the plugin
archive available in the image, but currently only Neutron has
Dockerfile directives to automatically install them if present. The same
can be added very easily for other commonly pluggable services such as
Horizon.
Change-Id: Ia52d5ccf753667c5452b19fcaf4bf5b893a59fd0
Vagrant and Heat, while really cool tech, are not very well maintained
in Kolla. They are not always up to date, and as a result, are not
recommended for evaluation purposes by this change.
TrivialFix
Change-Id: Ic8b8519431ed5c50a9a46b2e8b8f822d0982b1cf
Due to poor planning on our variable names we have a situation where
we have "internal_address" which must be a VIP, but "external_address"
which should be a DNS name. Now with two vips "external_vip_address"
is a new variable.
This corrects that issue by deprecating kolla_internal_address and
replacing it with 4 nicely named variables.
kolla_internal_vip_address
kolla_internal_fqdn
kolla_external_vip_address
kolla_external_fqdn
The default behaviour will remain the same, and the way the variable
inheritance is setup the kolla_internal_address variable can still be
set in globals.yml and propogate out to these 4 new variables like it
normally would, but all reference to kolla_internal_address has been
completely removed.
Change-Id: I4556dcdbf4d91a8d2751981ef9c64bad44a719e5
Partially-Implements: blueprint ssl-kolla
Made changes in section Managing Ceph to correct the grammatical mistake.
Signed-off-by: Richa Yadav <ricyadav@cisco.com>
Change-Id: I2ed13f766dd39a7ac816af86664986b8d2700d80
- Provided info on installing ansible via yum from EPEL and pointed
readers to the EPEL docs to learn how to install/enable the repo
Change-Id: I4bf87fbf90779be85293eb65fe7cd2ffe548d6ae
In Deploying Kolla section of the quickstart.rst IP addr needed to
be changed IP address.
Change-Id: I4f3895d6f05340a0608b2b66170a769bd1454fb7
Signed-off-by: Asha Saravanamohan <assarava@cisco.com>
Since docker 1.10.1 is required, and docker 1.8.2 does not work with Kolla,
Remove the downgrade instructions
TrivialFix
Change-Id: I461572a40b6fc96f73593cf989967449e4bc8e0a
Signed-off-by: Jason Myers <jason@jasonamyers.com>
The operators aren't mindreaders. Lets throw them a bone about
how to properly evaluate Kolla. This can probably be expanded
on.
TrivialFix
Change-Id: I70d0f6a63417dc9f361d8c14bbb512e1dcc44ed0
The documentation had old information about running
docker registry version 1. Documentation improvement
uses exclusively Docker register version 2.
TrivialFix
Change-Id: I320341c1a646eeeec35fb928a970f4d7e8a13bb9
For CentOS, install from distro packaging by default. Explain
how to install on DEB based systems from packaging when they
update to a newer version of Ansible. Finally, clean up the
ordering of the dependencies for a pip based install.
TrivialFix
Change-Id: I9564a03c2e75fd30b5ec9c7d64f5defb709d7fde
This change let Swift detect and use physical disk for storage. The
old named volume for storage isn't really useful for any serious setup.
Also updated swift-guide.rst accordingly.
Change-Id: I4f577b7b69d8bcd8b3961500946241c65a16db22
Partially-Implements: blueprint swift-physical-disk
The version changes in docker are needed to support named volumes
which are replacing data containers in our implementation. Docker
is no unblocked upstream for us thanks to our new kolla_docker
module so I removed the cap on that as well.
Change-Id: I847979b9f7c9e42a55273b5ee926a4aff19a7bec
- See instructions in doc/nova-fake-driver.rst
Implements: blueprint nova-fake-driver
Change-Id: I553a40c2df39bdcc391eb1b8b2b8fd5f4ed48c33
Signed-off-by: Hui Kang <kangh@us.ibm.com>
Signed-off-by: Marcio D. Silva <marcios@us.ibm.com>
As I walked through quickstart guide doing a CentOS
multinode deployment, I found a few items that needed
updating.
Change-Id: I3fa6d59ea856ff05be415faffd7f45197be67178
In order for the firewalld changes to apply, we must either restart
firewalld (as in this commit), or issue the four add-port commands
listed in the doc again w/o the "--permanent".
Change-Id: I09a12024085c315117bc27d095bae91af9c00d5e