|
|
# Getting started on the perfSONAR/MaDDash sampler project
|
|
|
|
|
|
This project doesn't do any network monitoring! It does show how you can set up the files from the perfSONAR RPMS to set up testpoint nodes and then a central management Maddash web site, incorporating the monitoring details from the testpoint hosts.
|
|
|
This project doesn't do any network monitoring! It does show how you can set up the perfSONAR RPMS to set up testpoint nodes and then a central management Maddash web site, incorporating the monitoring results from the testpoint nodes.
|
|
|
|
|
|
|
|
|
|
|
|
This is essentially a virtual machine implementation of Andy Lake's one page "MaDDash and perfSONAR Install" document (see https://docs.google.com/document/d/1k7FT66MKPy3JjpD5k0OFAFlTpSdFmZ6huhTUDQ2rGGY/edit?usp=sharing)
|
|
|
|
|
|
|
|
|
I've intentionally tested this on a small system, an Intel Nuc (NUC8i3BEK). It has a dual core Intel Core i3-8109U, 8G of RAM, and a 230g M.2 SATA drive. The project works on this level of hardware, barely. If you have a larger box for this demo system, it will save you waiting time during the installs.
|
|
|
I've intentionally tested this on a small system, an Intel Nuc (NUC8i3BEK). It has a dual core Intel Core i3-8109U, 8G of RAM, and a 230g M.2 SATA drive. The project works on this level of hardware, barely. If you have a larger box for this demo system, it will save you some time during the installs.
|
|
|
|
|
|
|
|
|
The project uses libvirt KVM virtual machines, generally these are based on Centos or Fedora base systems. 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 an 'USB3 to Enet' dongle and it worked out just fine.
|
|
|
The project uses libvirt KVM virtual machines, generally these are based on Centos or Fedora base systems. 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 an 'USB3 to Ethernet' dongle and it worked out just fine.
|
|
|
|
|
|
|
|
|
A few more setup details. You'll need to have management access to a DHCP and DNS server. For networking, 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.
|
... | ... | @@ -32,7 +32,7 @@ Next let's plan the name, IP, MAC addr, and domain names needed for the project. |
|
|
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 we will seed them to the vm's. From the MAC address, the DCHP server should provide the fixed IP number indicated, lastly, depending on how fancy your setup is, you may be able to assign a private or public FQDN to each planned VM.
|
|
|
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 vm's. From the MAC address, the DCHP server should provide the fixed IP number indicated. Lastly, depending on how fancy your setup is, 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 to keep the footprint small.
|
... | ... | @@ -50,7 +50,7 @@ ip a |
|
|
```
|
|
|
|
|
|
|
|
|
Once that is done you'll need to load up Git, Ansible and Vagrant. Git and Ansible are straight forward yum installs. Vagrant has a yum component but the libvirt provisioner needs to be added and is often tricky.
|
|
|
Once that is done you'll need to load Git, Ansible and Vagrant. Git and Ansible are straight forward yum installs. Vagrant has a yum component but the libvirt provisioner needs to be added and is often tricky.
|
|
|
|
|
|
Tool install on Centos 7:
|
|
|
```
|
... | ... | |