... | ... | @@ -13,28 +13,6 @@ I've intentionally tested this on a small system, an Intel Nuc (NUC8i3BEK). It h |
|
|
The project uses libvirt KVM virtual machines. I'll be using Centos 7, (the perfSONAR/MaDDash VMs also use Centos 7). Related to using libvirt VMs, the project uses Macvtap networking. This has a number of advantages that I won't go into. It does require one extra bit of hardware however. The base system needs a second ethernet port! Many systems come native with that, use that if your system has it. The Nuc doesn't have the second port so I used a 'USB3 to Ethernet' dongle and it worked fine.
|
|
|
|
|
|
|
|
|
You'll need to have management access to a DHCP and DNS server. For networking IPs, you could be bold and use a public network or more likely use a non-routable private segment. These git files use the 192.168.1.0/24 net, but that can be adjusted if needed (see maddash.yml).
|
|
|
|
|
|
|
|
|
Next let's plan the name, IP, MAC addr, and domain names needed for the project.
|
|
|
|
|
|
|Name |IP# |Mac Addr |FQDN |
|
|
|
| ---| ---| ---| ---|
|
|
|
|vm1|192.168.1.210|52:54:00:73:6f:41|vm1.ufixu.com|
|
|
|
|vm2|192.168.1.211|52:54:00:73:6f:42|vm2.ufixu.com|
|
|
|
|vm3|192.168.1.212|52:54:00:73:6f:43|vm3.ufixu.com|
|
|
|
|md|192.168.1.213|52:54:00:73:6f:44|md.ufixu.com|
|
|
|
| | | | |
|
|
|
|dj1|192.168.1.214|52:54:00:73:6f:45|dj1.ufixu.com|
|
|
|
|dj2|192.168.1.215|52:54:00:73:6f:46|dj2.ufixu.com|
|
|
|
|dj3|192.168.1.216|52:54:00:73:6f:47|dj3.ufixu.com|
|
|
|
|
|
|
If you make changes to the above table, plan to make similar edits to: Vagrantfile, review all the .yml files and possibly mesh.json & disjoint.json.
|
|
|
|
|
|
|
|
|
To set the context, VMs create their own MAC addresses, thus the set suggested will be fine, as the suggested MAC addrs will be seeded to the VMs. From the MAC address, the DCHP server should provide a fixed IP number indicated. Lastly, depending on your setup, you may be able to assign a private or public FQDN for each planned VM.
|
|
|
|
|
|
|
|
|
Build the base system with its own hard coded MAC and IP, **with the user 'vagrant' (sudo enabled) and any pword you'll remember**. Use Centos7, do a minimal install and add the EPEL repository, do a final 'update'.
|
|
|
|
|
|
The base host needs two ethernet interfaces, but only one needs to be active. The easiest way to get this setup is to only plug in one ethernet cable to the base system during the initial install. Once Centos is installed, plug in the second ethernet cable into the second port or plug in the USB-enet adapter with the ethernet cable connected. Then use the following commands:
|
... | ... | @@ -73,4 +51,26 @@ ssh-keygen -o -a 256 -t ed25519 |
|
|
```
|
|
|
|
|
|
|
|
|
Now that the base system is setup, return to the project README.md page for more steps, |
|
|
\ No newline at end of file |
|
|
With all of this accomplished, there are just a few more things to establish. To start you'll need to have management access to a DHCP and DNS server. For networking IPs, you could be bold and use a public network or more likely use a non-routable private segment. The project git files use the 192.168.1.0/24 net, but that can be adjusted if needed (see maddash.yml).
|
|
|
|
|
|
|
|
|
Next let's plan the name, IP, MAC addr, and domain names needed for the project.
|
|
|
|
|
|
|Name |IP# |Mac Addr |FQDN |
|
|
|
| ---| ---| ---| ---|
|
|
|
|vm1|192.168.1.210|52:54:00:73:6f:41|vm1.ufixu.com|
|
|
|
|vm2|192.168.1.211|52:54:00:73:6f:42|vm2.ufixu.com|
|
|
|
|vm3|192.168.1.212|52:54:00:73:6f:43|vm3.ufixu.com|
|
|
|
|md|192.168.1.213|52:54:00:73:6f:44|md.ufixu.com|
|
|
|
| | | | |
|
|
|
|dj1|192.168.1.214|52:54:00:73:6f:45|dj1.ufixu.com|
|
|
|
|dj2|192.168.1.215|52:54:00:73:6f:46|dj2.ufixu.com|
|
|
|
|dj3|192.168.1.216|52:54:00:73:6f:47|dj3.ufixu.com|
|
|
|
|
|
|
If you make changes to the above table, plan to make similar edits to: Vagrantfile, review all the .yml files and possibly mesh.json & disjoint.json.
|
|
|
|
|
|
|
|
|
To set the context, VMs create their own MAC addresses, thus the set suggested will be fine, as the suggested MAC addrs will be seeded to the VMs. From the MAC address, the DCHP server should provide a fixed IP number indicated. Lastly, depending on your setup, you may be able to assign a private or public FQDN for each planned VM.
|
|
|
|
|
|
|
|
|
Now that the base system is done and a plan the VM names, IP, MAC addr has been created, return to the project README.md page for more steps. |
|
|
\ No newline at end of file |