Open Stack

I guess I would need to see real examples that support this approach.
All of the current entries at
http://wiki.openstack.org/OperationsUseCases look like robust
problems, and blue prints support iterative progress on a scenario.
Also, wikis and pads are not the collaboration environment that
mailing lists are.

Beware the silos,
Lloyd


On Thu, Nov 8, 2012 at 11:39 AM, Tim Bell <Tim.Bell at cern.ch> wrote:
>
> Lloyd,
>
> Not all of the openstack users are not as confident as you are :-) :-)
>
> Personally, I appreciate having other users validate that what I feel is a
> requirement is not my incorrect approach.  I'm sure there are ways of doing
> this sort of flow within Launchpad but getting a starter list together on a
> wiki as James has started is a good way to bootstrap the process.
>
> Tim
>
>> -----Original Message-----
>> From: Lloyd Dewolf [mailto:lloydostack at gmail.com]
>> Sent: 08 November 2012 20:22
>> To: Tim Bell
>> Cc: Michael Still; James R Penick; openstack-operators at lists.openstack.org
>> Subject: Re: [Openstack-operators] Operations use cases/pain points
>>
>> I've never hesitated to open issues containing only experienced issues or
>> symptoms. All successful software projects handle these with grace.
>>
>> On Thu, Nov 8, 2012 at 11:16 AM, Tim Bell <Tim.Bell at cern.ch> wrote:
>> >
>> > Our user community should not be obliged to understand the internals
>> > of OpenStack. Many high level pain points can have multiple project hits
>> (e.g.
>> > horizon/keystone/nova)
>>
>>
>> --
>> @lloyddewolf
>> http://www.pistoncloud.com/



-- 
--
@lloyddewolf
http://www.pistoncloud.com/