dc36a98fc1
Revert ensureProperty warning message, too many false positives in places where Info is correctly propigated. Better approach needed.
2014-12-21 21:33:03 -04:00
d194765e10
propellor spin
2014-12-21 21:14:11 -04:00
23399416f1
broke up big function to describe PrivDataField
2014-12-14 16:14:05 -04:00
2e2438ae66
improve haddock formating of filenames
2014-12-09 14:22:37 -04:00
4e9b01a8a7
propellor spin
...
(cherry picked from commit 1d02d589c7
2014-12-08 01:07:25 -04:00
4c2eac2d3c
remove -i, seems not needed and may be causing problem
2014-11-27 19:10:39 -04:00
96ecbaad25
pute full path to bin/propellor inside shim
2014-11-22 22:10:53 -04:00
6c92f1034f
split out info types
2014-11-21 18:55:33 -04:00
a4f04fcb02
propellor spin
2014-11-20 15:15:28 -04:00
b8b746a7f1
starting work on a Chroot module
...
factored out info up-propigation code rom Docker
2014-11-20 14:15:26 -04:00
5e4c57652c
fix docker container provisioning
...
Since the containers are no longer on the host list, they were not found
while provisioning, oops.
To fix, had to add to a host's info a map of the containers docked to it.
Unfortunately, that required Propellor.Types.Info be glommed into
Propellor.Types, since it needed to refer to Host.
2014-11-20 00:21:40 -04:00
d49d251897
separate docker container type
...
Docker containers are now a separate data type, cannot be included in the
main host list, and are instead passed to Docker.docked. (API change)
2014-11-19 23:11:34 -04:00
803e1407a0
improve display
2014-11-19 01:40:56 -04:00
1872ee1ffc
propellor spin
2014-11-19 01:32:09 -04:00
4dddbb725d
prevent multiple concurrent provisioning inside docker container
...
Lock a lock file while provisioning inside, otherwise propellor could be
running to init the container when the system has just booted, or the
container was just started from being stopped, and at the same time,
propellor run outside the container chains into it to provision.
Previously, simplesh prevented this in a different way.
2014-11-19 01:28:38 -04:00
05086b3abe
propellor spin
2014-11-19 01:02:13 -04:00
f8b71c0ab4
propellor spin
2014-11-19 00:38:11 -04:00
325fe4037b
propellor spin
2014-11-19 00:30:06 -04:00
2bbb2aa6e2
remove --docker; use Continue
...
And --chain was already not used.
2014-11-18 18:52:00 -04:00
4a0cac113c
fix color display when running propellor inside docker
2014-11-18 17:53:42 -04:00
9755b761bb
Docker: Stop using docker.io; that was a compat symlink in the Debian package which has been removed in docker.io 1.3.1~dfsg1-2.
2014-11-08 15:55:58 -04:00
f5b5159f76
don't need RestartPolicy data type; simplify
2014-10-23 12:28:33 -04:00
73a75cbefc
Fix loop when a docker host that does not exist was docked.
...
The problem is it fell back to looking for an alias for the bad hostname,
but to get the aliases, it needs to know which hosts are docked where,
so looped.
2014-10-23 12:11:43 -04:00
e6924a894d
Revert "Revert "Revert "propellor spin"""
...
This reverts commit 26bef2486d
2014-10-23 11:46:15 -04:00
26bef2486d
Revert "Revert "propellor spin""
...
This reverts commit 8d353813bf
2014-10-23 11:42:34 -04:00
8d353813bf
Revert "propellor spin"
...
This reverts commit ac7b182b5a
2014-10-23 11:39:29 -04:00
ac7b182b5a
propellor spin
2014-10-23 11:36:06 -04:00
bdf3e37066
Revert "propellor spin"
...
This reverts commit 80f5b53f1b
2014-10-23 11:33:00 -04:00
bbec7021f8
Revert "propellor spin"
...
This reverts commit 45ce3a5e8c
2014-10-23 11:31:00 -04:00
45ce3a5e8c
propellor spin
2014-10-23 11:28:10 -04:00
80f5b53f1b
propellor spin
2014-10-23 11:26:05 -04:00
5bfeb3f9aa
Revert "propellor spin"
...
This reverts commit 7637ea0af9
2014-10-23 11:25:07 -04:00
7637ea0af9
propellor spin
2014-10-23 11:23:25 -04:00
856a4c673c
propellor spin
2014-10-23 03:27:40 -04:00
93099b8627
bugfix
2014-10-23 03:18:52 -04:00
a0e4c872b6
propellor spin
2014-10-23 02:50:50 -04:00
9e3485a13b
propellor spin
2014-10-23 02:41:47 -04:00
9d7a442182
propellor spin
2014-10-23 02:36:08 -04:00
fbba9639d6
propellor spin
2014-10-23 02:34:42 -04:00
2be1255b89
propellor spin
2014-10-10 13:51:52 -04:00
df0c0e56cb
Docker: Avoid committing container every time it's started up.
...
This was using a lot of disk space. Instead, start the container, and then
use the running container to check if docker is running it with the right
params. In the unlikely case that the params have changed, we still need to
commit the container and restart it. The common case of eg a reboot no
longer commits though.
2014-10-10 13:47:41 -04:00
c120355272
propellor spin
2014-10-10 13:25:30 -04:00
ff9647cf9d
propellor spin
2014-10-10 13:21:42 -04:00
6a674c79d7
fix some accidental uses of spaces, rather than tabs, for indentation
2014-10-08 13:14:21 -04:00
fc95968145
propellor spin
2014-09-18 23:50:13 -04:00
53bb64040a
wording
2014-07-06 17:58:27 -04:00
cd37316dd5
propigate required privdata fields out from docker containers to the hosts they're docked in
2014-07-06 17:54:06 -04:00
58f79c12aa
propellor spin
2014-07-06 15:56:56 -04:00
fc49d75e4f
Attr is renamed to Info.
2014-06-09 01:47:11 -04:00
3df3fd1746
propellor spin
2014-06-01 13:40:06 -04:00
Joey Hess
Joey Hess
Joey Hess