mkdir to create /etc/kolla/config/nova fails if config
folder is not created.
This change adds `-p` to create both config and nova folders
Change-Id: Ibceaa437834cbba681b30c418da3c15d75d49945
In quick start added the correct link which can be used
to setup the development environment with vagrant
Change-Id: Id3eabe3da05264058fed3136acc4cd270b5134ae
Closes-Bug: #1681978
Kibana index name prefix to create was wrong.
As describe in
'kolla-ansible/ansible/roles/common/templates/conf/output/01-es.conf.j2'
index prefix is "flog".
Change-Id: I6c2a38808258a8968024bcf8992353ff9672e0f9
Last Openstack version supported on Ubuntu 14.04 is Mitaka. Hence Ubuntu
14.04 related documentation can be remove since Kolla Newton release.
Change-Id: Ibedd9dea659fc787660e44909573a59339b870c3
doc/running-tests.rst:64: D001 Line too long
doc/bifrost.rst:164: D000 Unknown target name: "edit-inventory".
doc/nova-fake-driver.rst:: WARNING: document isn't included in any
toctree
Change-Id: I83bb44ed10cb464f87e5235a423a475151ace208
Add links to refer to the main Kolla documentation. Also fix minor
formatting errors that were preventing the docs from building.
Change-Id: I8759b9e995097d221900441bd001a1234ae007fd
Depends-On: Ia7959c71a241b9d7139ec50b34e36b24fbcf76e6
Co-Authored-By: Mauricio Lima <mauriciolimab@gmail.com>
In order to slove the problem of running `vagrant up` hangs on
NFS mounting, we can allow these services on server firewall.
Change-Id: I70fb072b6103fa662fcfaaafd0f8f57e45193798
Closes-Bug: #1675378
Currently the project-deploy-guide links to the entire dev
doc repo for Kolla-Ansible. This is incorrect. It should link
only to installation information that can be found in the quick
start guide. This patch remedies that change, and ensures that
there is a link to the kolla deploy guide published at
docs.o.o.
Change-Id: I43738e341e996cb5a589a09c4c59c0dc8b058458
correspondence with 'logstash_prefix flog' in 'kolla-ansible/ansible/
/roles/common/templates/conf/output/01-es.conf.j2'
and 'kolla-ansible/ansible/roles/common/templates/conf/output/
/00-local.conf.j2'.
Change-Id: I90a7b1b6a5267d79f192345e531b503d3a99ca79
Added a note about Elasticsearch using volume space.
Renamed Kibana guide to central-logging guide.
Change-Id: I0a451b5316a53815a53c62faa2bf993ca34f27e0
Closes-Bug: #1614572
This change fills out the Bifrost developer documentation and makes a
few corrections.
Change-Id: I14a6eca58c440677d5de638cbc677e9ec05738af
Closes-Bug: #1661013
Co-Authored-By: Sayantani Goswami <sayantani.goswami@intel.com>
Correct syntax error for Deployment Philosophy doc.
Update node types descriptions for more unified in doc Production
architecture.
Change-Id: I9266a72eb88d9c4c52673bbdecc952b684a56d12
It is not currently possible to deploy Bifrost on a host other than the
Ansible control host. A deployer may want to manage an Ansible control
environment remotely from the Bifrost deployment host but is currently
unable to.
This change adds a new top level 'deployment' Ansible group and a
'bifrost' Ansible group containing the 'deployment' group. The Ansible
play in ansible/bifrost.yml is now targeted at the hosts in the
'bifrost' group. For backwards compatibility, the all-in-one and
multinode inventories add localhost to the deployment group. This allows
a deployer to deploy Bifrost on a remote host by modifying the hosts in
the deployment or bifrost groups.
Change-Id: I76808feab5dd67dff63379ed9c7d08a105636acf
Closes-bug: #1665373
With libvirt 2.0, when using qemu cpu mode is not properly
evaluated and need to be set to cpu_mode = none.
Add this option when kvm is not supported, otherwise user
will still facing errors when launching instances over qemu.
Change-Id: Ic970e3de74817ce4e17bb4e15d130e1e82d595cc
Add support for basic multiple regions, that is to say, many OpenStack
with a shared Keystone (same users) and Horizon. The shared Keystone
and Horizon are deployed into one region, for instance RegionOne.
Services of other regions have an access to this Keystone. This
support assumes that the operator knows the name of all OpenStack
regions in advance, and considers as many Kolla runs as there are
regions.
The new variable, multiple_regions_names, contains the name of
regions. It is needed by the region that includes Keystone and
Horizon. In register.yml, it specifies to create as many Keystone
endpoints as there are regiones, so that services of other regions can
connect to Keystone. In local_settings.j2, it changes the render to
support multiple regions in Horizon. The multi-regions.rst explains
how to perform a multiple regions deployment.
Implements: blueprint multi-kolla-config
Change-Id: Icab2aebfc4de0e3bc609950956e0af397705f403
Adding -e REGISTRY_PROXY_REMOTEURL=https://registry-1.docker.io to the
docker run command in the start-registry script configures the local
registry as a pull through cache. However, pushing of images to the
local registry fails.
Pushing to a registry configured as a pull-through cache is unsupported.
For more information, reference the proxy section in Docker
Documentation (https://docs.docker.com/registry/configuration/)
The start_registry script has been updated in the patch set
https://review.openstack.org/#/c/426338/
Change-Id: If62b40d8316af7c3593523493cad8a904d35dceb
This builds the deployment guide that will be published to
https://docs.openstack.org/project-deploy-guide/newton/.
In this approach, all existing documents in kolla-ansible/doc directory
will remain. The kolla-ansible/deploy-guide directory will simply
include all documents that exist in the kolla-ansible/doc directory.
All new changes will be made to the documents in the docs directory
which will be imported to the deployment-guide. However, I believe we
will also have to build the deployment-guide every time a change is
merged to the docs in the doc directory.
Change-Id: I98db4ec45403cf48086381b45bf5a12bbf998911
