Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

Presentation

  • Scope
    • ACS Services Daemon
    • ACS Container Daemon
    • ACS Daemons Architecture
  • Duration: 10 minutes

...

 In one machine configure the daemons:

Code Block
languagebash
linenumberstrue
collapsetrue
acsservicesdaemon &
acscontainerdaemon &

Later, to stop the daemons:

Code Block
languagebash
linenumberstrue
collapsetrue
fg
Ctrl+C
fg
Ctrl+C

or:

Code Block
languagebash
linenumberstrue
collapsetrue
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
languagebash
linenumberstrue
collapsetrue
acscontainerdaemon &

Later, to stop the daemon:

Code Block
languagebash
linenumberstrue
collapsetrue
fg
Ctrl+C

or:

Code Block
languagebash
linenumberstrue
collapsetrue
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
languagebash
linenumberstrue
collapsetrue
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
languagebash
linenumberstrue
collapsetrue
acsdaemonStopContainer -c bilboContainer -i 0 -H <host1>
acsdaemonStopContainer -c frodoContainer -i 0 -H <host2>
acsdaemonStopAcs -i 0 -H <host1>

...