Versions Compared

Key

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

...

  •  make sure all pre-requisites are met
  •  extract demoStack-Version.zip (e.g. demoStack-0.3.6.zip), it will expand into a demo folder
  •  

    change to this folder, open a command prompt / terminal there and run 

    Code Block
    vagrant up
  •  

    it might take some time and will prompt for your DockerHub credentials (username, passwort) and hit Enter

    Code Block
    Username for DockerHub: customerusername
    Password for DockerHub: allyoursecretsarebelongtous
  •  

    for the first time a lot of files need to be downloaded (2.5 GB) so be patient

  •  

    after a while you should see something like 

    Code Block
    Demo has been successfully deployed!
  •  

    then you can open your browser at http://192.168.33.10:8080/SSCAdminApp

Installation on existing Docker Hosts

Ensure that you got docker-compose installed. See the docs on how to install it.

Code Block
root@ubuntu:~# which docker-compose
/usr/local/bin/docker-compose
root@ubuntu:~# docker-compose -v
docker-compose version 1.7.1, build 0a9ab35
root@ubuntu:~#

Installation on Docker-enabled environments is the fastest way; just open a Bash shell in the demo folder and run.

Code Block
./init_stack.sh

Vagrant Usage

...

Vagrant Usage

Starting and Stopping

Simply stop the Vargrant VM, either via VirtualBox or (being in the demo folder) for stopping:

...

Warning

 This will destroy and purge all your data!

Installation on an existing Docker Hosts

Ensure that you got docker-compose installed. See the docs on how to install it.

Code Block
root@ubuntu:~# which docker-compose
/usr/local/bin/docker-compose
root@ubuntu:~# docker-compose -v
docker-compose version 1.7.1, build 0a9ab35
root@ubuntu:~#

Installation on Docker-enabled environments is the fastest way; just open a Bash shell in the demo folder and run.

Code Block
./init_stack.sh

Demo Stack Usage

The demo stack comes with a collection of admin scripts which basically wrap around docker-compose. Change into the demo directory to access the scripts.

Code Block
azeti@ubuntu:~/demo$ ll
total 48
...
-rwxr-xr-x 1 azeti azeti  101 May 31 17:40 start_stack.sh*
-rwxr-xr-x 1 azeti azeti   99 May 31 17:40 stop_stack.sh*
-rwxr-xr-x 1 azeti azeti  915 May 31 17:40 update_stack.sh*

Starting and Stopping

Use the start and stop script.

Code Block
azeti@ubuntu:~/demo$ sudo ./stop_stack.sh
Stopping the full stack...
Stopping sscdemo_influxdb_1 ... done
Stopping sscdemo_db_1 ... done

Same for starting it up again.

Code Block
azeti@ubuntu:~/demo$ sudo ./start_stack.sh
Starting the full stack...
Starting influxdb_data ... done
Starting db_data ... done
Starting db ... done
Starting influxdb ... done
...

Update

You can eaisly update the full stack with the script, it does a {{docker-compose

Code Block
azeti@ubuntu:~/demo$ sudo ./update_stack.sh
Enter DockerHub username and press [ENTER]: 
Enter DockerHub password and press [ENTER]: 
Login Succeeded
Stopping the full stack...
Stopping sscdemo_tomcat_1 ... done
Stopping sscdemo_activemq_1 ... done
Stopping sscdemo_influxdb_1 ... done
Stopping sscdemo_db_1 ... done
Pulling tomcat (azeti/tomcat-data:latest)...
latest: Pulling from azeti/tomcat-data
8b87079b7a06: Already exists
..
Starting sscdemo_db_data_1
...Starting activemq ... done
Starting tomcat ... done

Troubleshooting

So far there have not been any problems yet. (smile)