Yamdown format and group/type info

ColonelPanics commented 6 years ago

This PR is based off of #2 and actually adds the markdown and yamdown formatting properly.

Currently there is no data collected regarding machine type and groups, this will require a solution which allows for commands to only be ran on the controller without using SSH.

ColonelPanics commented 6 years ago

@mjtko The yamdown format now creates a file that looks like the following:

localhost:
  name: localhost
  type: NOT IMPLEMENTED
  primary_group: pri_group
  secondary_group: secondary,another
  info: |
# System

## BIOS Version

```0.5.1```

## Service Tag

```Not```

## CPU(s)

- Model: Intel Xeon E312xx (Sandy Bridge)
- Cores: 2
- Count: NOT IMPLEMENTED
- Hyperthreading: disabled

## RAM

- Total: 3790 MB

# Network Devices

| Interface | Type | State | Speed | Slaves | MAC | Location |
|-----------|------|-------|-------|--------|-----|----------|
| __eth0__ | Ethernet | UP group default | N/A |  | 52:54:00:9d:74:af | 0000:00:03.0 |
| __eth1__ | Ethernet | UP group default | N/A |  | 52:54:00:d1:a5:f8 | 0000:00:04.0 |
| __eth2__ | Ethernet | UP group default | N/A |  | 52:54:00:3e:e6:c0 | 0000:00:05.0 |

mjtko commented 6 years ago

Excellent, let's go with that for now, I reckon merge this in now. We can tweak when we get a bit further down the line with the Flight Center side of things.

Refs: alces-software/alces-flight-center#481

alces-software / benchware

Yamdown format and group/type info #4