| Age | Commit message (Collapse) | Author |
|
|
|
|
|
This is more general; it doesn't need to contain a Host.
It would, for example, be possible to make Property itself be an instance
of PropAccum.
|
|
Properties now form a tree, instead of the flat list used before.
This simplifies propigation of Info from the Properties used inside a
container to the outer host; the Property that docks the container on the
host can just have as child properties all the inner Properties, and their
Info can then be gathered recursively. (Although in practice it still needs
to be filtered, since not all Info should propigate out of a container.)
Note that there is no change to how Properties are actually satisfied.
Just because a Property lists some child properties, this does not mean
they always have their propertySatisfy actions run. It's still up to the
parent property to run those actions.
That's necessary so that a container's properties can be satisfied inside
it, not outside. It also allows property combinators to
add the combined Properties to their childProperties list, even if,
like onChange, they don't always run the child properties at all.
Testing: I tested that the exact same Info is calculated before and after
this change, for every Host in my config file.
|
|
where Info is correctly propigated. Better approach needed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also, lost the systemd-nspawn parameters; I'll do that some other way.
|
|
Need to propigate the full container info, not the subset used in chroot
deployment.
|
|
|
|
wow, that was suprisingly trivial!
|
|
|
|
|
|
|
|
|
|
|
|
factored out info up-propigation code rom Docker
|