Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
F
flame-clmc
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
flame
flame-clmc
Commits
ac767551
Commit
ac767551
authored
6 years ago
by
Michael Boniface
Browse files
Options
Downloads
Patches
Plain Diff
Update README.md
parent
864d8d74
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+7
-8
7 additions, 8 deletions
README.md
with
7 additions
and
8 deletions
README.md
+
7
−
8
View file @
ac767551
...
...
@@ -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
lx
c
init
lx
d
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
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment