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
We get an awful lot of questions about how to operate with a registry
on the IRC channel and the obvious way to fix that is to document it.
I don't know what to document about Ubuntu but if someone leaves the
appropriate commands in the review I'll be happy to update it to include
the correct operations to make the registry run on Ubuntu. Another option
is perhaps we can get Sam to write those docs once this hits the repo since
the structure will be mostly in place.
TrivialFix
Change-Id: Ib88abbaf9bd6bcabddae994157d9288aab8be2bf
Fixed commands for disabling\stoping libvirt and ntpd in different OS
I encourage to install kolla tools via pip, so user could get rid
of relative paths to config and scripts and run it from everythere.
Change-Id: I77271ce2f72fbaa7d6586a84f7998a9888d9b3a2
The commands around installing docker on Centos7
in the quickstart guide needed a little tweaking
and a little spell checking.
Change-Id: Ia0367900ab9792a096f753d5fd943ffab0a005a4
Mention `chrony` since thats what docs.openstack.org recommends for
WAN connections. It does do better than ntpd
Change-Id: I28caade26492294bf12b092ff949003c7bf0bb8e
I merged "quickstart" doc with "ansible-deployment" and
"deploy-all-in-one-node". All three of them was covering same topic and
added a lot of confusion for new users.
I added some clarification lines from myself, with main goal to recive one
straightforward document for new users.
Change-Id: I793244c47ffbe0ba304e79bacf708494e59d99c4
Include our full mission statement and tidy up the documentation
landing page so it looks more professional and has shorter
titles that communicate the same information.
Change-Id: If54acbfa817e9a9a71e9f16f923094248b2f62f0
Change "kolla's Philosophy on Deployment" to "Kolla's Deplooyment
Philosophy" so it takes up less bytes.
Change-Id: I35d7b91f6b5260878e3a5a45d89b97c74d88cddc
We decided during the ODS documentation session that several
documents need retitling. This patch retitles the documents
but doesn't actually adjust the content. There is a separate
patch under work which refactors the content from three documents
into one document.
Change-Id: If5a4718b0ab50c405d42a2e20b7b054b93f3227a
From this etherpad:
https://etherpad.openstack.org/p/kolla-mitaka-documentation
Lay groundwork for structure of new documentation layout.
Further work will finish the job on this doc work.
Note in a later change I793244c47ffbe0ba304e79bacf708494e59d99c4
ansible-deployment, deploy-all-in-one-node, and quickstart.rst
will be merged into one document.
Change-Id: I42b576ffab796da6e27adc9dbf55b2ceed641c16
The documentation was correct. This table change helps
highlight that default packages are not recent enough
or too recent for the Kolla playbooks.
Change-Id: I9ea3cfc87aebcc10cb344cd8f32e9b91782ecf55
With registry flag,
build image using `tools/build.py --registry 172.22.2.81:4000`
the image name looks like `172.22.2.81:4000/kollaglue/data`
When user use kolla-ansible,
user set `docker_registry` to `172.22.2.81:4000` in `/etc/kolla/globals.yml`.
Build image using `tools/build.py -n abcd`
the image name looks like `abcd/data`
When user use kolla-ansible,
user set `docker_namespace:` to `abcd` in `/etc/kolla/globals.yml`.
build image using `tools/build.py -n abcd --registry 172.22.2.81:4000`
the image name looks like `abcd/data`
When user use kolla-ansible,
user set `docker_namespace:` to `abcd` in `/etc/kolla/globals.yml`.
user set `docker_registry` to `172.22.2.81:4000` in `/etc/kolla/globals.yml`.
With the feature, it will reduce user confusing and mistaking.
Change-Id: I18ac7a3ccec032888e35f5e9a79fc190760cc8a0
Closes-Bug: #1505056
Kolla implements a workaround for the referenced docker issue. There is
no need to document it, however still recommend installing a recent
kernel for better compatibility.
Change-Id: I06eaa0bb0980f0698202724f523ab08cb344418e
Update ansible-deployment to note that root privilege is needed
when deploying.
Change-Id: I80d3792de69c16c05c5285e8113d5924d6192735
Closes-Bug: #1471824
