diff options
| author | Haiwei Xu <xu-haiwei@mxw.nes.nec.co.jp> | 2014-10-07 17:39:38 +0900 |
|---|---|---|
| committer | Haiwei Xu <xu-haiwei@mxw.nes.nec.co.jp> | 2014-10-07 17:45:08 +0900 |
| commit | fd0275b659b2f1874eeec574af128abcad6502ea (patch) | |
| tree | 599c985abbb0214998faffd51cf87f9b32382c1e | |
| parent | 0d544c7130d62e829413a7fa3d495ffecb090972 (diff) | |
| download | kolla-fd0275b659b2f1874eeec574af128abcad6502ea.tar.gz kolla-fd0275b659b2f1874eeec574af128abcad6502ea.zip | |
Remove the trailing space in README.md
Change-Id: Iafdae5d5e38f6910dbf89af5a5f47a9c29df4e5c
| -rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -18,7 +18,7 @@ deployment tool that can be found [here](https://github.com/larsks/heat-kubernetes). -Build Docker Images +Build Docker Images ------------------- Within the docker directory is a tool called build. This tool will build @@ -121,7 +121,7 @@ $ curl https://raw.githubusercontent.com/stackforge/kolla/master/docker/keystone $ kubecfg -c keystone-service-5000.json create services $ kubecfg -c keystone-service-35357.json create services $ kubecfg -c keystone.json create pods -``` +``` The keystone pod should become status running, if it doesn't you can troubleshoot it the same way that the database was. Once keystone is running you should be able to use the keystone client to do a token-get against one of the proxy's ip addresses. |