b02b719705
Issue #45 : VM startup won't report READY=YES to OneGate
8 years ago
7449f0caa3
be less verbose
8 years ago
57daf9798c
gh-41: update state constants in onegate
8 years ago
b10446a695
gh-42: change shutdown action to terminate
8 years ago
ea0ce70fb9
Change onegate version number
8 years ago
ed6b9b273e
Change copyright headers
8 years ago
52580e751f
gh-39: use constants instead of file paths
8 years ago
d1b3f4e9bb
gh-39: add locking to context startup script
8 years ago
e530847e39
gh-39: execute reconf when context changes
8 years ago
7a95e9d044
gh-37: send first parameter to scripts
...
Will be used by reconfiguration
8 years ago
f0fd5c1ad4
feature #4255 : The VMID is mandatory in onegate actions
9 years ago
b5e1d71590
Change the order of context.sh retrieval methods
9 years ago
d18062bdb2
Fix bug in one-contextd
9 years ago
84a969763b
Always write context.sh to /tmp
9 years ago
bd529d974e
gh-24: get context.sh in EC2 instances
9 years ago
6dad6796df
Fix one-contextd and deb/rpm init.d
...
One-contextd was missing a call to the start function.
The init.d scripts were calling one-context not
one-contextd
9 years ago
50f8d3c91a
Change one-context to one-contextd
9 years ago
2190ff94a7
Move one-context to sbin and refactor one-context.service
...
One-context should really have been in sbin all along. Updated
one-context.service to run before systemd-networkd but after udev
or kdbus have run. This should eliminate the requirement for a
systemd-networkd restart.
9 years ago
8d98d5a8cc
Change onegate version
9 years ago
a44d12c0be
Add start wrapper to onegate tool
...
It first sources /tmp/one_env file to get context data
9 years ago
42e56c9246
Add onegate script to context
9 years ago
Jaime Melis
Javi Fontan
Daniel Molina
Dan Kelleher