From 34145b1d05e811bbea3d4caf8f0422280b7c502d Mon Sep 17 00:00:00 2001 From: Surojit Pathak Date: Tue, 25 Aug 2015 21:41:05 +0000 Subject: [PATCH] Doc update for 'magnum coe-service-*' As per bug#1487580, we are renaming all 'magnum service-*' CLIs to 'magnum coe-service-*'. Change-Id: I4cb60a0b91d69b97413b00e7c9f2febf650f80bb Partially-Implements: blueprint magnum-service-list Closes-bug: #1488663 Depends-On: Ia4ee95e324087309b7f771b3a9d4930b8d8589cf --- doc/source/dev/dev-quickstart.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/dev/dev-quickstart.rst b/doc/source/dev/dev-quickstart.rst index 3e5bb4a3ed..1af963d7a6 100644 --- a/doc/source/dev/dev-quickstart.rst +++ b/doc/source/dev/dev-quickstart.rst @@ -272,7 +272,7 @@ a pod for the redis-master:: Now create a service to provide a discoverable endpoint for the redis sentinels in the cluster:: - magnum service-create --manifest ./redis-sentinel-service.yaml --bay k8sbay + magnum coe-service-create --manifest ./redis-sentinel-service.yaml --bay k8sbay To make it a replicated redis cluster create replication controllers for the redis slaves and sentinels:: @@ -285,7 +285,7 @@ redis slaves and sentinels:: Full lifecycle and introspection operations for each object are supported. For example, magnum bay-create, magnum baymodel-delete, magnum rc-show, -magnum service-list. +magnum coe-service-list. Now run bay-show command to get the IP of the bay host on which the redis-master is running::