On Wed, Jul 20, 2011 at 02:00:55PM -0400, Chris Lalancette wrote:
On 07/19/11 - 05:19:25PM, Hugh Brock wrote:
I firmly believe that the reason not having a template building UI is a problem, is because we keep telling people they have to build templates in order to do things. I further think if we want Conductor to be successful, we should fix it so people don't have to build templates unless they really, really want to.
As may be evident by some of my other replies, I am of the opinion that people will want to build their own images to install their own software.
However, even if we step back and take the tactic that people will always use pre-canned images, at the very least you need an "import image" GUI screen. If we start there, then we can see whether it is worthwhile to go further and have a full-up "choose your packages and install your OS" screen. Does that make sense?
I think an "Import image" GUI screen or a "Show me the images that are available" GUI screen is a must-have. I'd like to get it scoped for this release. My thought is we should add it to the pool screen -- a pool should have some images that it can see by virtue of being connected to a cloud provider.
I was talking to a couple of the Katello guys today (www.katello.org) and they are going to look at adding a feature to generate a Factory template definition to an upcoming sprint. They don't think it should be that difficult if it's limited to specifying packages. I know their UI isn't explicitly connected to ours, but it seems to me like we should be using their template definition UI if we're going to use one.
Anyone up for having a look at Katello and helping those guys out in generating a Factory template? Or better yet calling Factory directly to build a image and put it in Warehouse?
--H