From 39356329d0d31c9054f1b288b3c5a7f3187083dc Mon Sep 17 00:00:00 2001
From: Alexander Lutay <alutay@sipwise.com>
Date: Mon, 16 Feb 2015 12:42:52 +0100
Subject: [PATCH] MT#11263 Start/stop glusterfs-server manually for
 manipulations with network.yml

We have migrated to ngcp.inc with modern list of services to be stopped
at the end of ngcp-installer.
See commit e75b01441cadd09096b9057b55ef9c966951b6a8 for more details.

Unfortunately deployment.sh is performing 'magic' with network.yml and depends on glusterfs
for pulling/pushing configs from/to shared storage. I am planning to move this 'magic' to
ngcp-installer, but while it is here, we have to start stop glusterfs-server manually.

Change-Id: Ia0aac183df52a1e2bd51ff6f2326f8438cad5b79
---
 deployment.sh | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/deployment.sh b/deployment.sh
index 4222a24..a880892 100755
--- a/deployment.sh
+++ b/deployment.sh
@@ -1625,6 +1625,9 @@ elif "$PRO_EDITION" ; then
     exit 0
   fi
 
+  # we have to start glusterfs-server back to work with shared storage
+  invoke-rc.d glusterfs-server start
+
   if [ "$ROLE" = "sp1" ] ; then
     cp /etc/ngcp-config/network.yml /etc/ngcp-config/network.yml.factory_default
 
@@ -1723,6 +1726,9 @@ elif "$PRO_EDITION" ; then
       echo "Skipping ngcpcfg init-mgmt as it is not available"
     fi
   fi
+
+  # we have to stop glusterfs-server back
+  invoke-rc.d glusterfs-server stop
 EOT
 fi