On Tue, Jul 19, 2011 at 04:17:12PM -0400, Chris Lalancette wrote:
On 07/19/11 - 02:11:26PM, Hugh Brock wrote:
Other UX work
- I think we should be able to launch single images from Conductor without requiring a deployable XML. To make that easier for users, it would be nice if there was some UI for displaying images that are available to launch.
Incidentally, I was going to reply to this very block to suggest that this might also be of use in the sort of use case I've been thinking about lately -- someone who wants to run Conductor to manage a handful of instances, maybe across a couple providers, but who really doesn't want all the overhead that comes with a full-blown setup.
So there's that, too.
I know this is going to make me unpopular, but I think we need to re-instate the UI for building images. As a short-term solution, removing it and going CLI-only removed a roadblock for us, but the immediate reaction of (potential) users when presented with it is revulsion.
Having witnessed this same reaction, I have to agree with Chris here.
Personally, I'd be fine if we started by providing a limited UI, and explained that the command line tools offered more flexibility. But "hand-edit this XML file, run a command-line tool on it to build the image, tail -f the log file and wait for it to finish, and then copy-and-paste that UUID into another command" really didn't go over well at all with the people I showed this to. It works for us, but not the people we're building this for.
-- Matt