Skip to content
Snippets Groups Projects
Commit ac767551 authored by Michael Boniface's avatar Michael Boniface
Browse files

Update README.md

parent 864d8d74
No related branches found
No related tags found
No related merge requests found
......@@ -124,17 +124,14 @@ pytest -s --pyargs clmctest.monitoring
A lxd container is setup on givry called `clmc-ci`. The container is priviledged and allows for nested containers. The container was created using the following commands
```
lxc launch ubuntu:18.04 clmc-ci -c security.privileged=true -c security.nesting=true
lxc network attach br_ci clmc-ci eth0
lxc config device set clmc-ci eth0 ipv4.address 10.0.3.15
lxc launch ubuntu:18.04 flame-clmc-ci -c security.privileged=true -c security.nesting=true
```
the container is then started and LXD initialised
```
lxc start clmc-ci
lxc exec clmc-ci -- bash
lxc init
lxd init
```
Follow the interactive prompts, use the defaults apart from the storage pool type, use `dir` type
......@@ -142,16 +139,18 @@ Follow the interactive prompts, use the defaults apart from the storage pool typ
Now configure ip table persistence, this is needed for the fixtures script to work but not for CI
```
apt update
echo iptables-persistent iptables-persistent/autosave_v4 boolean true | sudo debconf-set-selections
echo iptables-persistent iptables-persistent/autosave_v6 boolean true | sudo debconf-set-selections
apt-get -y install iptables-persistent
apt -y install iptables-persistent
```
The install git runner file was just copied to the container from a tmp director
```
cp /tmp/install-git-runner.sh /var/lib/lxd/containers/clmc-ci/rootfs/tmp
chmod 755 /var/lib/lxd/containers/clmc-ci/rootfs/tmp
lxc file push /home/mjb/dev/flame-clmc/scripts/test/install-git-runner.sh flame-clmc-ci/root/
lxc exec flame-clmc-ci -- chmod 755 ./install-git-runner.sh
lxc exec flame-clmc-ci -- ./install-git-runner.sh
```
Note that the branch must be "protected" for the secret repo rc variables to be passed to the CI script
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment