...
ACS doesn't provide scripts to simplify the configuration of the ACS Daemons on the operating system, this is a task that at this point has to be performed by the developers and/or sysadmin specialists.
- Scope
- ACS Services Daemon
- ACS Container Daemon
- ACS Daemons Architecture
- Duration: 10 minutes
...
In one machine configure the daemons:
Code Block |
---|
language | bash |
---|
linenumbers | true |
---|
collapse | true |
---|
|
acsservicesdaemon &
acscontainerdaemon & |
Later, to stop the daemons:
Code Block |
---|
language | bash |
---|
linenumbers | true |
---|
collapse | true |
---|
|
fg
Ctrl+C
fg
Ctrl+C |
or:
Code Block |
---|
language | bash |
---|
linenumbers | true |
---|
collapse | true |
---|
|
ps u |grep acscontainerdaemon |grep -v grep |awk '{print $2}' |xargs kill
ps u |grep acsservicesdaemon |grep -v grep |awk '{print $2}' |xargs kill |
Host 2 (Containers)
In the other machine configure only the container daemon:
Code Block |
---|
language | bash |
---|
linenumbers | true |
---|
collapse | true |
---|
|
acscontainerdaemon & |
Later, to stop the daemon:
Code Block |
---|
language | bash |
---|
linenumbers | true |
---|
collapse | true |
---|
|
fg
Ctrl+C |
or:
Code Block |
---|
language | bash |
---|
linenumbers | true |
---|
collapse | true |
---|
|
ps u |grep acscontainerdaemon |grep -v grep |awk '{print $2}' |xargs kill |
Host 3 (Or any of the previous hosts)
Interact with the daemons on the other hosts
Code Block |
---|
language | bash |
---|
linenumbers | true |
---|
collapse | true |
---|
|
acsdaemonStartAcs -i 0 -H <host1>
acsdaemonStartContainer -t cpp -c bilboContainer -i 0 -H <host1>
acsdaemonStartContainer -t java -c frodoContainer -i 0 -H <host2> |
Later, to bring down the system:
Code Block |
---|
language | bash |
---|
linenumbers | true |
---|
collapse | true |
---|
|
acsdaemonStopContainer -c bilboContainer -i 0 -H <host1>
acsdaemonStopContainer -c frodoContainer -i 0 -H <host2>
acsdaemonStopAcs -i 0 -H <host1> |
...