Lab Setup¶
Here is the setup we will leverage to either create a new environment or to connect to an existing environment (F5 UDF)
In the existing environment, here is the setup you’ll get:
| System | Network | Gateway |
|---|---|---|
| Master 1 | 10.2.10.10/24 | 10.2.10.254 |
| Master 2 | 10.2.10.20/24 | 10.2.10.254 |
| Master 3 | 10.2.10.30/24 | 10.2.10.254 |
| Agent 1 | 10.2.10.40/24 | 10.2.10.254 |
| Agent 2 | 10.2.10.50/24 | 10.2.10.254 |
| Windows Jumpbox | 10.10.200.199/24 | 10.10.200.1 |
| BIG-IP | 10.2.10.60/24 | 10.2.10.254 |
Here are a few things to know that could be useful (if you want to reproduce this in another environment)
- We used Ubuntu xenial (16.04) in this lab
- We updated on all the nodes the /etc/hosts file so that each node is reachable via its name
Example of our hosts file
user@master1:~$ cat /etc/hosts
127.0.0.1 localhost
10.2.10.10 f5-mesos-master1 f5-mesos-master1.agility-labs.io
10.2.10.20 f5-mesos-master2 f5-mesos-master2.agility-labs.io
10.2.10.30 f5-mesos-master3 f5-mesos-master3.agility-labs.io
10.2.10.40 f5-mesos-agent1 f5-mesos-agent1.agility-labs.io
10.2.10.50 f5-mesos-agent2 f5-mesos-agent2.agility-labs.io
- On f5-mesos-master1, we created some ssh keys for user that we copied on all the nodes. This way you can use f5-mesos-master1 to connect to all nodes without authentication
- we enabled user to do sudo commands without authentication. This was done via the visudo command to specify that we allow passwordless sudo command for this user (here is a thread talking about how to do it: visudo)