Open Stack

On 10 October 2015 at 12:14, Clint Byrum <clint at fewbar.com> wrote:

>> I think the important thing is to focus on what we have in 6 months
>> doesn't break current users / applications, and is incrementally closer
>> to our end game. That's the lens I'm going to keep putting on this one.
>>
>
> Right, so adopting a new catalog type that we see as the future, and
> making it the backend for the current solution, is the route I'd like
> to work toward. If we get the groundwork laid for that, but we don't
> make any user-visible improvement in 6 months, is that a failure or a win?

I don't think its either from this distance. IF we guess right about
what we need, the groundwork helps, and \o/.

If we guess wrong, then we now have new groundwork that still needs
hammering on, and it might be better or worse :/.

If we can be assessing the new thing against our known needs at each
step, that might reduce the risk.

But the biggest risk I see is the one Sean already articulated: we
have only a vague idea about how folk are /actually/ using what we
built, and thus its very hard to predict 'changing X will break
someone'.

-Rob

-- 
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Converged Cloud