From fcb3145df7132747e6d442ad91fdf82dd03c9db8 Mon Sep 17 00:00:00 2001
From: Steven Dake <sdake@redhat.com>
Date: Tue, 7 Oct 2014 08:16:05 -0700
Subject: [PATCH] Remove -master from README.md

The removal of the foo-master labels left the README.md in an
incorrect state.  Fix that problem.

Change-Id: I61802a18c0f424cd9e5c16b988d5fbd5d462afac
---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index c44f4e759a..d7ef135fa2 100644
--- a/README.md
+++ b/README.md
@@ -64,12 +64,12 @@ their addresses. You'll see the same thing in keystone when it's launched.
 $ kubecfg -c mariadb-service.json create services
 ID                  Labels              Selector              Port
 ----------          ----------          ----------            ----------
-mariadbmaster                           name=mariadb-master   3306
+mariadb                           name=mariadb   3306
 
 $ kubecfg -c mariadb.json create pods
 ID                  Image(s)                       Host                Labels                Status
 ----------          ----------                     ----------          ----------            ----------
-mariadb             kollaglue/fedora-rdo-mariadb   /                   name=mariadb-master   Waiting
+mariadb             kollaglue/fedora-rdo-mariadb   /                   name=mariadb   Waiting
 ```
 To verify their creation and see their status use the list command. You are ready to move on when the
 pod's status reaches **Running**.
@@ -77,7 +77,7 @@ pod's status reaches **Running**.
 $ kubecfg list pods
 ID                  Image(s)                       Host                Labels                Status
 ----------          ----------                     ----------          ----------            ----------
-mariadb             kollaglue/fedora-rdo-mariadb   10.0.0.3/           name=mariadb-master   Running
+mariadb             kollaglue/fedora-rdo-mariadb   10.0.0.3/           name=mariadb   Running
 ```
 If MariaDB doesn't move to running within a few minutes use journalctl on the master and the nodes to
 troubleshoot. The first command is for the master and the second is for the nodes.