Andrew says ...
following the hours of turgid discussion at LISA, i have been
dwelling
on the issues of deployment/rollout of service changes. in particular,
how we should think of this as a separate and orthogonal issue
to that of what needs to be done. so i decided to test the
separateness
by working on a local (real) problem, which i present in simplified
form.
....
any comments? has anyone else tried this approach?
any traps ahead for me?
I'm sure that I seen several comparatively simple examples in a
similar vein (Ed?). I worry about how you get from there to something
practical.
How do you specify what you want in a simple and concise way - having
someone (sysadmin?) write arbitrary code in a logic programming
language and let it lose to reconfigure my network would make me a
little twitchy :-) - you still want to allow the flexibility though -
perhaps you need to provide some layer which restricts what is
possible, and makes the application context clearer - for example
"remove server A while maintaining these properties ....."
It is also hard to specify all the correct constraints in practice -
my previous example being migrating some service on to somebody's
laptop because there wasn't any constraint to say that this was a bad
idea ....
But I really would like to see this approach followed up a little
further.
I have zero time right now, but I might be able to initiate a student
project to play with it and keep me involved .... (?)
Paul
_______________________________________________
lssconf-discuss mailing list
lssconf-discuss@inf.ed.ac.uk
http://lists.inf.ed.ac.uk/mailman/listinfo/lssconf-discuss
