| Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I4217433a2c7d199a3768ae02e2f6798fe6703fd8
|
|
This mini-spec documents an approach for how Kolla-triggered and managed
MariaDB backups might be handled.
Change-Id: I65f1ab92b9dce48cdd752fffd2123bd58d65b98f
bp: https://blueprints.launchpad.net/kolla/+spec/database-backup-recovery
|
|
The current bluestore disk label naming is inconsistent with the
filestore. The filestore naming format is that the disk prefixes
belonging to the same osd are the same and the suffixes are
different.
This patch keeps the bluestore's disk naming as well.
Change-Id: I090cf055ebedc555b5ada35e140b7a7bb2a4cf8f
|
|
Describes the proposed approach to introduce Ceph blustore[1] OSDs
in Kolla.
[1] http://docs.ceph.com/docs/master/
Partially-Implements: blueprint kolla-ceph-bluestore
Change-Id: I388e720270f9971900fe56c38d52a8cdf563e7a2
Signed-off-by: Tone Zhang <tone.zhang@arm.com>
|
|
Change-Id: Idabd40606b385430ce35925fa6d1558c835065f1
|
|
Fixed typos in readme "Specifications".
Change-Id: I1e4c26b3d72f216d7d6b14ad90297e8cc656878f
|
|
Use https instead of http to ensure the safety.
Change-Id: Iaf09b5b878e117d2333c30b8a769304a4a20f7ee
|
|
Change-Id: I9426b176a0d7af452c569590b771e4661b4652a2
|
|
|
|
Change-Id: I1dfbd2f9dbe2e320bc8b8f5e905d0bc600ba3d24
|
|
This patch changes the use of back end in kolla according to the
word choice convention [1].
[1] http://docs.openstack.org/contributor-guide/writing-style/word-choice.html
Change-Id: I20f2e158ba487622208d89b48eea0250257f5e76
|
|
TrivialFix
Change-Id: Ifca64d8c4d6e7654d25001022e806f082acfa0b8
|
|
Github is just a mirror of the OpenStack git-repo.
Changed from Github to OpenStack git url wherever possible.
Change-Id: I7941ef86967de4efe7f23ff9fb11ec86c793901e
|
|
TrivialFix
Change-Id: I92cc2d826f2d418b9575e35dd048c98775c0be5c
Signed-off-by: Mohammed Salih Puthenpurayil <linusali@gmail.com>
|
|
related blueprint kolla-kubernetes
Change-Id: Ib1023787fca096d22a21c583c1ef647ccf925f00
|
|
We got rid of the kolla-mesos repo:
http://git.openstack.org/cgit/openstack/kolla-mesos/tree/README.rst
So we don't need things in the main kolla tree
related to Mesos/Marathon
Closes-Bug: #1577951
Change-Id: Iafae63914c8a6601dc1b5b04231af8a1d2cc8642
|
|
This reverts commit 99761c5cdce0d4e59adc19d1c33d32fa30872ceb.
Change-Id: Ib40224841f3399c6794b8aa71ca5cd7f0308a722
|
|
related blueprint kolla-kubernetes
Co-Authored-By: mrostecki@mirantis.com
Change-Id: I5ef968a0f9b4a1b47b32bb041fbc5d5a3c2e2be7
|
|
Change-Id: I454d3ff2226a51b6b98515c1b29f7d3d45351e4f
|
|
|
|
Change-Id: I27ca0ea75f3d6a4371c91b3cb2c7a999ec90fbc4
|
|
Trivial Fix
Change-Id: Ic14778bb4e894490a3b6af9471ba01ab4da94601
|
|
This adds a spec for using Heka as Kolla's log processing tool.
Change-Id: Ia786601f3f0b298c120950e2abdd6d1b71e32ba5
|
|
Co-Authored-By: Georgy Okrokvertskhov <gokrokvertskhov@mirantis.com>
related blueprint mesos
Change-Id: I0bc2d9e69819079b8cdaf9a47c5363a3017dced9
|
|
Change-Id: I50d4d66a507b06e75c9968cf0e0ee1ad9fd55c0a
|
|
Change-Id: Ie2f5a3b8e239cae13909cf70f8be44b05b19d431
|
|
|
|
Previously, a spec did not exist to define how Kolla will support
highly available OpenStack services.
Change-Id: I8fcc60f26d2cb98179be6b520c13abb22a372ecf
|
|
This specification outlines some of the design goals and practices to
be used to implement an Ansible multi-node deployment tool. The goals
of this work are simplicity, optimizing deployment time, and Operator
flexibility.
The long term objective is for Kolla to become the de-facto solution
for deploying OpenStack in containers.
Partially Implements: blueprint ansible-multi
Co-Authored-By: Sam Yaple <sam@yaple.net>
Change-Id: I8c5d8b7e69c4ed54624061428e2fbde6af6a1815
|
|
The EXPOSE options will create a local docker-proxy. This is
unnecessary with --net=host mode. The docker-proxy adds about
20 microseconds of latency. Add documentation to the specification
to indicate where to find the ports that are exposed by the
services in case someone were to desire to add EXPOSE back to
the Dockerfiles.
Change-Id: I398e922fe096d6022a2d5985bb92498f89a5ea31
|
|
Change-Id: Ia21736dd43a4fe63fbf4567c96dd53b452594677
|
|
|
|
Permit different levels of horizontal scalability for API vs engine or
conductor processes. Typically API may need different levels of scale
compared to the engine processes.
.
Change-Id: I2916fed7745bd9b0f67fda0abbb6d148315e5e00
|
|
Added cinder and metadata
Change-Id: I42feae68a387dd5a9de97837f785d2672c320419
|
|
Added keepalived to HA control container set
Change-Id: Ic209bc6ca55125a52d1974003104238bb9c4caa2
|
|
Added a container set for network operations
Change-Id: I625f0f03366b1d68f210a0bf92e58d5ceb6c568d
|
|
The container spec file had a couple places were nested
lists were used which didn't have the necessary blank
lines before and after. As such, they didn not render
to HTML correctly.
Change-Id: I5d17644facdc25ec30db563c217367672529b8e1
|
|
This specification proposes using fig (being renamed to compose
soon) to provide single-node multi-container orchestration. By
using this mechanism, a very simple Ansible Playbook could easily
deploy a single node in to a specific role type - such as a controller
node, a compute node, or a storage node.
This specification further proposes using super-privileged containers
to provide solutions for the upgrade and rollback use cases of an
OpenStack deployment.
Change-Id: I56ff1fdf8b19b47be97778b55ea947ebb43995c1
|