On 07/14/2011 11:12 AM, Carl Trieloff wrote:
On 07/14/2011 10:46 AM, Chris Lalancette wrote:
> On 07/14/11 - 10:04:43AM, Hugh Brock wrote:
>> On Thu, Jul 14, 2011 at 09:55:41AM -0400, Carl Trieloff wrote:
>>> On 07/14/2011 09:58 AM, Hugh Brock wrote:
>>>> On Fri, Jun 17, 2011 at 11:16:00AM +0100, Mark McLoughlin wrote:
>>>>> Hey,
>>>>>
>>>>> Chatting to Justin yesterday, I suggested we come up with a list of
the
>>>>> top 5 features for the next release
>>>>>
>>>>> The idea is that these would be the features we'd concentrate on
>>>>> polishing off for the release and then promote heavily in the
release
>>>>> announcement with demos etc.
>>>>>
>>>>> My attempt is below. What am I missing? Any thoughts on the idea?
>>>>>
>>>>> Cheers,
>>>>> Mark.
>>>>>
>>>>> 1) New UI design!
>>>>> - Complete new theme
>>>>> - Design & Deploy, Monitor and Administer tabs
>>>>> - Pretty View and Filter View
>>>>> - Breadcrumbs
>>>>> - Monitor UI
>>>>> - "Launch Deployable" and deployments UI
>>>>>
>>>>> 2) RHEV-M, VMWare vSphere and CondorCloud support:
>>>>> - Available as provider types in conductor
>>>>> - Image build/upload support
>>>>> - Audrey config server IP used to get addresses of RHEV-M VMs
>>>>>
>>>>> 3) Deployable concept:
>>>>> - Launch multiple instances using a deployable definition
which
>>>>> lists the images to use
>>>>> - Stop all the instances in a deployment in one click
>>>>>
>>>>> 4) aeolus-image CLI:
>>>>> - Build an image from a template
>>>>> - Push it to multiple providers
>>>>> - Import an image
>>>>> - List images available for use in deployables
>>>>>
>>>>> 5) Reduced complexity:
>>>>> - Template creation and image building UI removed
>>>>> - condor_refreshd, the condor classad plugin, warehouse sync,
>>>>> image factory connector and delayed job daemons all removed
>>>> Hey guys, pay attention: You get to decide what goes in this release,
>>>> not me, and you certainly know more about what's actually in it than
I
>>>> do. What else should we be showing off for this release? Is there
>>>> anything we shouldn't be showing off, isn't ready yet, whatever?
>>>>
>>>> Responses encouraged...
>>>>
>>>> --Hugh
>>>>
>>> DC API ontop of Conductor, is the big missing item. Don't care about
>>> admin API for v1, but DC API needs to be there.
>>>
>>> Carl.
>> Ahh... well, we were talking about what features we would promote for
>> the release we're about to do *right now*, not one that is some time
>> in the future, and since the DC API isn't started yet we can't very
>> well promote it for this release.
>>
>> Having said that, would you mind describing for everyone what exposing
>> a DC API in front of Conductor would buy us?
> I've been wondering about this as well. The DC API doesn't seem to map very
> well onto the conductor; the concepts are not even the same. It feels like
> jamming a square peg into a round hole. What benefit would we gain from doing
> this, and do customers actually care about it?
>
All clouds that are worth anything have a public API, ours is
deltacloud. If I stand up aeolus for my private cloud, I want to be able
to use it via the API in the same way I can do with EC2, rackspace,
openstack etc.
API is used for all automation of deployment, and any deployment of size
is automated. The API of openstack, euca, enomaly etc are all highly
used, so I see no reason why the same usage pattern would not exist on
aeolus.
Carl.