We just have to change the IP addresses for each box to one of the public IPs of the newly created instances:
{code}
# name/IP or hostname/OS user/contol JMX PORT
box1 54.72.215.230 - - 9999
box2 54.72.236.150 - - 9999
box3 54.76.125.3 - - 9999
box4 54.76.154.205 - - 9999
box5 54.76.156.52 - - 9999
box6 54.76.156.53 - - 9999
box7 54.76.156.72 - - 9999
box8 54.76.156.78 - - 9999
{code}
Be sure that Amazon "Security groups" and instances firewalls have proper open ports.
The following assumes that you have installed (unzipped) the new-cluster-test project, provided by Ontotext as a separate ZIP file:
{code}
$ cd ~/new-cluster-test
$ ant amazon-configure
{code}
This process takes awhile, so we can now start deploying the nagios instance.
h2. Launch nagios instance
We'll need one more EC2 instance. This time choose 64-bit Amazon Linux AMI (tested again with t3.medium, though t1.micro may be enough). You'll need just SSH (22) and HTTP (80) ports open for this one.
After the instance is up, you'll need to SSH to it and run the following commands there:
{code}
$ sudo yum install docker
$ sudo service docker start
$ sudo docker login -u ontotext -p ontodocker -e zdravko.tashev@ontotext.com
$ sudo docker pull ontotext/owlim-nagios
{code}
We're now ready to configure and run nagios. For this we need to make sure that the cluster is configured and running (that is, the previous step has finished). We'll need also one of the masters' URLs. E.g. the master in box1 above: [http://54.72.215.230:8080/openrdf-workbench/repositories/master]
{code}
$ sudo docker run -d -p 80:80 ontotext/owlim-nagios conf-and-run http://54.72.215.230:8080/openrdf-workbench/repositories/master
{code}That's it\! The start script will read the cluster's configuration, generate one for nagios and run it. To view the results point your browser to [http://54.76.155.44/nagios3/] or [http://54.76.155.44/pnp4nagios] for graphs (you'll have to put the external IP of the nagios machine here). The credentials are nagiosadmin/nagio
h2. Run sample LDBC-based load test
This is run from the same project new-cluster-test:
- check settings in your test.config, the following parameters at the end are related to the load test
{code}
ldbc_aggregation_agents 16
ldbc_editorial_agents 2
ldbc_run_time 3600
{code}
- then start the tests
{code}
ant ldbc-run
{code}
* Note: ldbc_run_time
** LDBC benchmark required java 7
** The ldbc-run ant target depends on *Unix
...