[00:00] <SpamapS> bcsaller: sweeeeet
[00:00] <SpamapS> bcsaller: curious, why are the config options not part of the main metadata.yaml ?
[00:02] <bcsaller> SpamapS: I don't think there is a strong reason, but for example when you look at a packages metadata its different that looking at what it might put in /etc/ to tune it 
[00:02] <SpamapS> Yeah I think I like it better this way actually
[00:02] <SpamapS> metadata could get out of hand fast if everything about the formula went into it
[00:12] <SpamapS> bcsaller: so... this is going to force a move toward a general direction that I think will become common to most formulas..
[00:12] <SpamapS> bcsaller: it appears that most hooks pretty much just need to update a local store of relation settings and config settings..
[00:13] <SpamapS> bcsaller: and then run a regeneration script.
[00:13] <bcsaller> SpamapS: vs data scoped at the service, you're talking about scoped to the unit?
[00:14] <SpamapS> I'm just thinking out loud mostly.
[00:14] <SpamapS> I like the way I did it with memcached.. with an include.. basically when memcached relations in mediawiki change, you just regenerate the memcached settings..
[00:14] <SpamapS> but some services don't have includes..
[00:15] <SpamapS> So for those, each hook just has to store some data locally ... "facts" if you will, and then regenerate from a template that queries said facts.
[00:16] <bcsaller> SpamapS: what example are you thinking of that shouldn't apply to all units of a service?
[00:17] <SpamapS> Err, we are totally on different pages
[00:17] <SpamapS> I'm talking about how hooks work together to configure the service.
[00:38] <SpamapS> bcsaller: FYI, adding config options is actually pretty fun.. the formula feels far more useful with them.
[00:38]  * SpamapS signs off for the weekend.
[00:39] <bcsaller> SpamapS: thanks, have a good one 
[03:17] <RoAkSoAx> fwreade ok so.bootstrap and deploy work and needs 2 fixes will email u later im not home
[03:17] <RoAkSoAx> fwereade  ^^
[03:36] <hazmat> fwereade, tests that need external factors are functional tests
[03:37] <hazmat> SpamapS, we're around 98% last i checked, which is a while ago granted
[06:03] <SpamapS> hrm.. very confusing
[06:04] <SpamapS> so if I have a default value for an option, it should be considered optional
[06:04] <SpamapS> but I get
[06:04] <SpamapS> Invalid options specification: options.wiki-title.validator: required value not found in /home/clint/src/principia/principia-tools/formulas/mediawiki/config.yaml
[06:04] <SpamapS> That seems rather broken
[07:09] <_mup_> Bug #814974 was filed: config options need a "file" type <Ensemble:New> < https://launchpad.net/bugs/814974 >
[07:11] <_mup_> Bug #814977 was filed: ImportError when running ensemble-make-image <Ensemble:New> < https://launchpad.net/bugs/814977 >
[07:44] <_mup_> Bug #814987 was filed: config-changed hook is retried on 'resolved' even when --retry is not passed <Ensemble:New> < https://launchpad.net/bugs/814987 >
[07:52] <SpamapS> bcsaller: reminder, the next upload to Ubuntu is Tuesday.. would be great to have the deploy bits in there too. :)
[12:33] <hazmat> SpamapS, is there a bug filed for the default value should be used for required values?
[12:46]  * hazmat goes back to setting up his new laptop