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
Fix the example by suggesting the creation of the directory
and customizing nova properly.
Change-Id: Ie5cd9b7f309416745dce60211b5a800e8c5273f7
Co-Authored-By: ampopp04@gmail.com
* Remove references to all-in-one, kolla Swift now works correctly in both
all-in-one and multinode contexts
* Fixup commands used for generating rings
* General readability improvements
Change-Id: I3ec87068a98ba5397bb6f2feb707bc685181e747
* Instruct the user that the VG needs to be on the storage nodes
* enable_cinder_backend_lvm needs to be enabled when following this
guide.
Change-Id: I252ec98c98493705417aaf197f703957cce8528f
Get follwing error when running tox -edocs
doc/bifrost.rst:91: D001 Line too long
doc/manila-hnas-guide.rst:28: D000 Title underline too short.
doc/manila-hnas-guide.rst:28: D000 Title underline too short.
doc/networking-guide.rst:93: D000 Title underline too short.
doc/networking-guide.rst:93: D000 Title underline too short.
doc/multinode.rst:14: D001 Line too long
doc/quickstart.rst:474: D001 Line too long
doc/vagrant-dev-env.rst:129: D001 Line too long
Change-Id: I88090487a4710547224361d29aaf8371f8340c28
Docker version 1.13.0 is broken with the kolla-ansible deliverlable.
Mark it as such in the documentation.
Change-Id: I91da906cfa2a4552739749b27b41006fbc06215d
Integrate designate service with neutron to allow instances
and floatingip resolve designate dns.
MDNS service need to be reachable from nova instances
in order to resolve DNS queries.
Added new dns_interface to make this configurable.
Add designate guide.
Closes-Bug: #1661330
Change-Id: I5a2ac5cf2a9aa0977ae42d53dd64699623ddf3ed
Update documents reference image-building documents correctly after
image-building.rst was deleted from kolla-ansible directory.
Change-Id: Ib66475e1f0f3055f2e38fc33ae649cae300c9c36
Kolla-ansible related documents existed on both Kolla and Kolla-Ansible
repositories. A lot of Kolla-ansible related documents were updated in
the Kolla repository. Porting the changes made to these documents in
Kolla repo to Kolla-Ansible repo so that the Kolla-ansible documents can
be removed (Refer to patch https://review.openstack.org/#/c/425749/)
Change-Id: I7c53626ce551189acdb0dcbabe9369b81eed3347
