Thanks Rob / Judd / Simon for the clarification. Which of you will be
in Austin when I'm there (June 24-26)? Seems like a good opportunity
to continue this discussion.
Rob Hirschfeld (rob_hirschf...@dell.com) wrote:
> Adam / Chris / CB Community,
>
> I tried to frame this during the design call and it's worth repeating -> the
> original scope for CB2 was overly ambitious and I believe we need a more
> practical target ("CB2 core") for our next iteration.
>
> We've accomplished a lot in CB2 trunk from database schema, jig framework,
> Chef 11, Rails 3, Ruby 1.9, automated testing, integrated docs, improved
> packaging and much other real progress.
>
> Most importantly, we have LEARNED a lot. With the pause for Pebbles, we've
> had a chance to reflect. The #1 lesson for me is that our orchestration
> plans were incomplete and too large. It is now clear to me that the
> orchestration complexity was a major factor in our delivery slips.
>
> My objective is to start bringing these lessons learned to the community for
> discussion. I think a dialog about them is important; however, we need to
> accept that the code base will be "down-factored" to achieve a core
> functionality set. These functions will include work from above that we've
> accomplished and should also deliver important CB2 objectives like late-bound
> networking, heterogeneous O/S, online cache mode, scale, multiple CMDBs, and
> the ability share/upstream cookbooks.
>
> I've seen some great discussion on this topic so far. I hope my $0.02 helps
> add clarity.
>
> I'm going offline for a week - I'm looking forward to seeing where you've
> taken this when I return.
>
> Rob
>
> -----Original Message-----
> From: crowbar-bounces On Behalf Of Adam Spiers
> Sent: Friday, May 31, 2013 5:38 AM
> To: crowbar
> Subject: Re: [Crowbar] CB2 Core Design update
>
> Adam Spiers (aspi...@suse.com) wrote:
> > Rob Hirschfeld (rob_hirschf...@dell.com) wrote:
> > > Victor and I were kicking around the DB models a little more. The result
> > > was a further refinement/simplification for discussion.
> > >
> > >
> > > 1) Deployment is the top level thing. Basically, all the roles hang
> > > off the deployment (through the snapshot pointer). When a role has a
> > > prerequisite, that prerequisite is always resolved from within the
> > > deployment. The discussion image shows the role prereq chain in blue.
> >
> > Just checking you saw my feedback yesterday? I'm not yet convinced
> > how well this will work, but I'm very willing to be persuaded via
> > answers to my questions :)
>
> Just as an aside, I'm sort of puzzled that we're going through another
> fundamental iteration of redesign of 2.0 at this point. Have the timescales
> for release shifted sufficiently far into the future to make this feasible?
> I haven't been too involved in those discussions so maybe I missed something,
> but I thought the goal was to aim for a
> 2.0 release relatively soon after Pebbles?
>
> _______________________________________________
> Crowbar mailing list
> Crowbar@dell.com
> https://lists.us.dell.com/mailman/listinfo/crowbar
> For more information: http://crowbar.github.com/
_______________________________________________
Crowbar mailing list
Crowbar@dell.com
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/
