I have a 4-node SDS setup running for testing purposes; in each node, only a single NIC port is being used (1Gbps).
I want to change the networking config (I want to explore different bonding options), but I do not want to start ScaleIO services unless everything is ok at the network layer.
I have looked at the services (chkconfig --list) but it seems there are no ScaleIO-specific services. How do I (1) prevent ScaleIO from running while I try the bonding alteratives and (2) allow ScaleIO to run again?
1) What version are you currently running? 2) Are you trying to preserve the data on the node while you make your changes?
3) Is the device you plan on testing with only functioning as an SDS?
Each component does indeed have a service that corresponds to it. If you are rolling centOS, check out each one by going to /opt/emc/scaleio/"type"/bin
So if i wanted to stop the sds - /opt/emc/scaleio/sds/bin/delete_service.sh
Start it up - /opt/emc/scaleio/sds/bin/create_service.sh
If you look inside of the script you can find out what the service name for each component is called for easy management later:
BIN_DIR=`dirname $0`
cd $BIN_DIR
BIN_DIR=`\pwd`
DAEMON_BIN=$(cat $DAEMON_NAME_FILE)
DAEMON_NAME=$(basename $(dirname $BIN_DIR))
systemctl daemon-reload
systemctl start $DAEMON_NAME.service
So we know it's "component name".service
[root@sio61 bin]# service sds start/stop/restart
If you are on version 2.0 you might look into putting your sds in maintenance mode while you make your changes.
IvanSull1
6 Posts
797
0
Posted March 31st, 2016 08:00
1) What version are you currently running?
2) Are you trying to preserve the data on the node while you make your changes?
3) Is the device you plan on testing with only functioning as an SDS?
Each component does indeed have a service that corresponds to it. If you are rolling centOS, check out each one by going to /opt/emc/scaleio/"type"/bin
So if i wanted to stop the sds - /opt/emc/scaleio/sds/bin/delete_service.sh
Start it up - /opt/emc/scaleio/sds/bin/create_service.sh
If you look inside of the script you can find out what the service name for each component is called for easy management later:
BIN_DIR=`dirname $0`
cd $BIN_DIR
BIN_DIR=`\pwd`
DAEMON_BIN=$(cat $DAEMON_NAME_FILE)
DAEMON_NAME=$(basename $(dirname $BIN_DIR))
systemctl daemon-reload
systemctl start $DAEMON_NAME.service
So we know it's "component name".service
[root@sio61 bin]# service sds start/stop/restart
If you are on version 2.0 you might look into putting your sds in maintenance mode while you make your changes.
Hope that's helpful!