Browse Source

Apply fix in last commit to other markdown files

So a markdown list should be no indentation followed by two spaces. '  '

*  one
*  two
tags/6.8.0^2
Patrick Marchand 4 months ago
parent
commit
b711154722
5 changed files with 15 additions and 15 deletions
  1. +1
    -1
      CONTRIBUTING.md
  2. +9
    -9
      README.md
  3. +2
    -2
      roles/bgp/README.md
  4. +1
    -1
      roles/nagios-nrpe/README.md
  5. +2
    -2
      roles/ospf/README.md

+ 1
- 1
CONTRIBUTING.md View File

@@ -9,7 +9,7 @@ Contributions are welcome, as long as they respect our current workflow:
2. The dev branch should never be commited to directly, unless
you're updating the CHANGELOG file.

3. Use feature branches for anything else, once they've passed all
3. Use feature branches for anything else, once they've passed all
CI test, lints and have been reviewed by other contributors through a
pull request, they may be merged into the dev branch.



+ 9
- 9
README.md View File

@@ -9,13 +9,13 @@ used by Evolix.
Put your public key in the remote root's autorized_keys
(/root/.ssh/authorized_keys)

1 - Install ansible's prerequisites
1. Install ansible's prerequisites

```
ansible-playbook prerequisite.yml -CDi hosts -l HOSTNAME
```

2 - Run it
2. Run it

```
ansible-playbook evolixisation.yml --ask-vault-pass -CDKi hosts -l HOSTNAME
@@ -26,19 +26,19 @@ ansible-playbook evolixisation.yml --ask-vault-pass -CDKi hosts -l HOSTNAME
Changes can be tested by using [Packer](https://www.packer.io/) and
[vmm(4)](https://man.openbsd.org/vmm.4) :

* This process depends on the [Go](https://golang.org/) programming language.
* This process depends on the [Go](https://golang.org/) programming language.

```
# pkg_add go packer
```

* We use the [packer-builder-vmm](https://github.com/prep/packer-builder-vmm) project to bridge Packer and vmm(4)
* We use the [packer-builder-vmm](https://github.com/prep/packer-builder-vmm) project to bridge Packer and vmm(4)

```
$ go get -u github.com/prep/packer-builder-vmm/cmd/packer-builder-vmm
```

* Here is an example build file
* Here is an example build file

```
$ vim openbsd.json
@@ -101,25 +101,25 @@ $ vim openbsd.json
}


* You need your unprivileged user to be able to run vmctl(8) through doas(1)
* You need your unprivileged user to be able to run vmctl(8) through doas(1)

```
# echo "permit nopass myunprivilegeduser as root cmd /usr/sbin/vmctl" >> /etc/doas.conf
```

* Build the virtual machine
* Build the virtual machine

```
$ packer build openbsd.json
```

* Start it
* Start it

```
doas vmctl start evobsd -cL -d output-vmm/evobsd.qcow2
```

* Enable NAT on your host machine
* Enable NAT on your host machine

```
pass out on em0 inet from tap0:network to any nat-to (em0)


+ 2
- 2
roles/bgp/README.md View File

@@ -10,5 +10,5 @@ Everything is in the `tasks/main.yml` file.

The full list of variables (with default values) can be found in `defaults/main.yml`.

* `bgp_mailto` : email address the output of the script will be sent to when a change is detected
* `bgp_exclude_grep_command` : facultative grep -v command for some peers not to be checked
* `bgp_mailto` : email address the output of the script will be sent to when a change is detected
* `bgp_exclude_grep_command` : facultative grep -v command for some peers not to be checked

+ 1
- 1
roles/nagios-nrpe/README.md View File

@@ -8,6 +8,6 @@ Everything is in the `tasks/main.yml` file.

## Available variables

* `nagios_nrpe_allowed_hosts` : list of IP/hosts authorized (default: none).
* `nagios_nrpe_allowed_hosts` : list of IP/hosts authorized (default: none).

The full list of variables (with default values) can be found in `defaults/main.yml`.

+ 2
- 2
roles/ospf/README.md View File

@@ -10,5 +10,5 @@ Everything is in the `tasks/main.yml` file.

The full list of variables (with default values) can be found in `defaults/main.yml`.

* `ospf_mailto` : email address the output of the scripts will be sent to when a change is detected
* `ospf_sed_command` : facultative sed command to modify the ospfctl output and add a name to IPs
* `ospf_mailto` : email address the output of the scripts will be sent to when a change is detected
* `ospf_sed_command` : facultative sed command to modify the ospfctl output and add a name to IPs

Loading…
Cancel
Save