On Fri, Mar 07, 2008 at 04:57:50PM -0800, Liane Praza wrote: > As far as the temporary creation goes, the other piece of design to > consider is whether it's a requirement that somoene can to go from > temporary to permanent without re-specifying the command-line > configuration. That is, "I tried this change, it worked out, and now I > want to make it permanent". It seems the difference is in context: is > someone doing this to try the config out before committing to deploying > it, just playing around with the system, or doing emergency > reconfiguration things.
You could model temporary instances as persistent ones that are deleted on reboot. That'd be one proprty in the general framework pg. svcs should probably show temporary instances that are in maintenance, degraded states, yes, and probably in all other states too, though it should probably label them as temporary (and/or grow a new -a-like option). Dependencies by persistent instances on temporary instances should either not be allowed or should be deleted on reboot when the temporary instances are deleted. svc.configd could do the work of deleting temporary instances on reboot, else a new transient service just for that purpose. Making sure it only happens once per-boot is important. Nico --
