Skip to content

Latest commit

 

History

History
102 lines (78 loc) · 3.35 KB

SetupTestServer.md

File metadata and controls

102 lines (78 loc) · 3.35 KB

Setup Test Server

For best results you should use a test server that is in the same subnet but is not running the services/apps you are testing.

Install Support Tools

** Linux **

# yum -y install epel-release
# yum -y install git
# yum -y install java-1.8.0-openjdk
# yum -y install maven

** Windows **

  • Install Java -- Java SE Development Kit Windows x64.
    -- Accept Defaults for installs. -- Open Windows Advanced System Settings; Environemnt Variables -- Create a new System Variable; Variable name: JAVA_HOME, Variable value: C:\Program Files\Java\jdk1.8.0_121.
    -- NOTE: The last number should match the version of Java you installed. You can use Explorer and navigate to the folder. then cut and paste the value.
  • Install Git Download 64-bit Git for Windows Setup. Defaults for all installation dialogs. -- You can use defaults during install
  • Install Maven -- Download the Binary zip archive and unzip (I usually put it in C:) -- Open Windows Advanced System Settings; Environemnt Variables -- Edit the Path variable and append Maven to the path. Append a semicolon followed by path to Maven bin folder (e.g. ;C:\apache-maven-3.5.0\bin). Cut and paste is helpful.

Clone Simulator

$ git clone https://github.com/david618/Simulator

Build Simulator

$ cd Simulator
$ mvn install

Should end with "BUILD SUCCESS"

Install JMeter (optional)

To support Map/Feature Service Testing

$ cd ~
$ curl -O http://apache.org/dist/jmeter/binaries/apache-jmeter-3.1.tgz

** Windows ** Download JMeter zip

Verify signature (Linux)

$ md5sum apache-jmeter-3.1.tgz
f439864f8f14e38228fee5fab8d912b0  apache-jmeter-3.1.tgz

Untar or Unzip

$ tar xvzf apache-jmeter-3.1.tgz

$ git clone https://github.com/david618/agsservicetesting

Trinity

When configuring DCOS cluster you can an additional public agent(s) to support testing. You can request the additional nodes using the ARM template (Azure) or using a Cloudconfiguration File with additional nodes.

After the cluster is built take the test agents out of the cluster.

For Example:

$ ssh -i azureuser p2
$ sudo su -
# systemctl stop dcos-mesos-slave-public.service
# systemctl disable dcos-mesos-slave-public.service

You can verify that the node disappears from DCOS Dashboard. DCOS will show the node as Unhealthy for a while; then it will disappear. Usually takes a few minutes.

I used public agents, because they are a little smaller that the private agents and do not have the extra disk space (which is not required on the test server). You can do the same thing extra private agents or masters.

You must leave at least 1 public agent (Marathon-LB / Trinity) needs one.

From the test server (e.g. p2) you can now use Mesos-DNS entries.

[p2]$ ping hub01.mesos
[p2]$ ping broker-0.hub01.mesos
[p2]$ ping broker-1.hub01.mesos

[p2]$ ping sat01.mesos
[p2]$ ping sat01-node.sat01.mesos
[p2]$ host sat01-node.sat01.mesos
sat01-node.sat01.mesos has address 172.17.2.4
sat01-node.sat01.mesos has address 172.17.2.6

These addresses can be used in the test tools like Simulator; instead of using IP's.