Collecting Audrey parameters in conductor
From: Greg Blomquist <gblomqui(a)redhat.com>
Date: Mon, 12 Sep 2011 10:44:57 -0400
I've written up a document explaining how we're planning on implementing
collecting Audrey parameters from within Conductor. Please take a look
and let me know if you have any questions.
My plan is to begin implementing this design today and course correct if
anyone brings up something earth-shattering.
A couple of notes up front:
1) This is dependent on a patch that was submitted quite some time ago,
but never acked. I'm basically pulling that patch, and will have to
rebase and resubmit later...most likely concurrently with this patch.
2) I'd appreciate suggestions on the model changes. Right now it's a
fairly rudimentary key value store for capturing the Audrey parameters
and values. It will serve our purpose for now, since we're only gonna
support scalar values for the time being. But, as this evolves, the
model design will have to change too. I'm not looking to completely
future proof this, but any suggestions on this model are very welcome.
link:
https://www.aeolusproject.org/redmine/projects/audrey/wiki/Collect_Audrey...
Thanks for pulling this together Greg!
I'm not conversant enough with the underpinning code to express an
opinion about the integration points, but it sounds plausible.
Question re scope: If we were trying to pare down to the absolute
rock-bottom functionality, would it save implementation time to skip
the show-instance page enhancements? If the answer is yes, I advocate
staging the work that way, ie do the prompting on the launch page
first, and time permitting, do the show-instance stuff.
My two kopeks....