Chris, I understand your confusion about the redesign, as we all know, in a traditional development cycle this would certainly be late for these kinds of discussions. That being said, I agree with Judd and personally welcome any changes in favour of reducing complexity. The more we simply things, the sooner we'll be able to release and actually start utlizing all the goodness we currently have sitting in trunk.
Simon -----Original Message----- From: crowbar-bounces On Behalf Of Judd Maltin Sent: Friday, May 31, 2013 11:24 AM To: Dearborn, Chris Cc: crowbar Subject: Re: [Crowbar] CB2 Core Design update The original Crowbar 2.0 design was unworkably complex. I know the stuff I designed was too complex. We slipped and had to pivot. So, now we're looking at simplifying. Nobody in our space is doing networking right. Most aren't even trying it. Some are collaborating with network gear manufacturers to start ferreting out the primitives. Rob's proposing changes to try to make things simpler, and to get to those primitives. When he mentioned using "roles" for networking to me, I too was unsure, and I still am. But with Deployments defined at a broader scope, everything feels thrown up in the area. More diagrams and effort are required. This is far from over. I'm hoping the result will be something simple yet flexible and powerful. -judd On Fri, May 31, 2013 at 10:55 AM, <[email protected]> wrote: > I agree. I'm struggling to understand why things are being redesigned at > this stage. > > Regarding the design changes to the network barclamp, it sounds like conduits > will still exist and that they will just be represented as roles in the model > instead of being explicitly represented as Conduits/ConduitRules/etc. It's > unclear to me that this change will make things simpler, and it appears that > it will only serve to obfuscate conduits (which are not a simple concept to > begin with) further. > > > Thanks, > > Chris > > > -----Original Message----- > From: crowbar-bounces On Behalf Of Adam Spiers > Sent: Friday, May 31, 2013 6:38 AM > To: crowbar > Subject: Re: [Crowbar] CB2 Core Design update > > Adam Spiers ([email protected]) wrote: >> Rob Hirschfeld ([email protected]) 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 > [email protected] > https://lists.us.dell.com/mailman/listinfo/crowbar > For more information: http://crowbar.github.com/ > > _______________________________________________ > Crowbar mailing list > [email protected] > https://lists.us.dell.com/mailman/listinfo/crowbar > For more information: http://crowbar.github.com/ -- Judd Maltin T: 917-882-1270 F: 501-694-7809 what could possibly go wrong? _______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/ _______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
