| Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
|
|
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
|
|
Change-Id: I40d2eb9c5b778e633d54489d31cd32de0e82bf2f
|
|
Change-Id: I9a166ef3035482adc863b79ad70c3ebd56e4ce59
|
|
Add deploy all in one node document.
Use ubuntu host and ubuntu docker image as example.
Change-Id: I8bc0862827e192b63ff3cbf7be9f7227e4f7b1bd
|