Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base

2013-12-20 Thread Victor Lowther
On Dec 20, 2013 8:45 AM, "Dirk Müller" wrote: > > Hi Victor, > > > * The database files are append-only and grow in size over time despite > > garbage collection, leading to fairly significant slowdown on admin nodes > > that run for long periods of time. Run an admin node in production for 6 > >

Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base

2013-12-20 Thread Dirk Müller
Hi Victor, > * The database files are append-only and grow in size over time despite > garbage collection, leading to fairly significant slowdown on admin nodes > that run for long periods of time. Run an admin node in production for 6 > months and you will see what I mean. Didn't you fix that y

Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base

2013-12-20 Thread Adam Spiers
Rob Hirschfeld (rob_hirschf...@dell.com) wrote: > Adam, > As you know, we use a very different build process than your team. We have > tried several times to duplicate your process using Kiwi and your tool chain > without success. We are not going to put additional effort into that. Sure - th

Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base

2013-12-19 Thread Rob_Hirschfeld
unces On Behalf Of Adam Spiers Sent: Wednesday, December 18, 2013 9:16 AM To: crowbar Subject: Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base Victor Lowther (victor.lowt...@gmail.com) wrote: > I do not want to go back to having branches in the top-level r

Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base

2013-12-19 Thread Rob_Hirschfeld
-Original Message- From: crowbar-bounces On Behalf Of Vincent Untz Sent: Wednesday, December 18, 2013 4:32 AM Ø What's really worrying to me, though, is that your suggestion might lead to a split in the community. Our community is not that big, and I don't think we can afford it. I've

Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base

2013-12-18 Thread Adam Spiers
gt; > From: crowbar-bounces On Behalf Of Terpstra, John > Sent: Wednesday, December 18, 2013 9:29 AM > To: aspi...@suse.com; crowbar > Subject: Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our > new code base > > Unfortunately, our internal infrastructure

Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base

2013-12-18 Thread Adam Spiers
John Terpstra (john_terps...@dell.com) wrote: > Unfortunately, our internal infrastructure makes use of DevTool to > build and test CB1.x - if we make the changes Adam suggests will > take only 60 sec, it will take several engineers from our team to > update/change/fix the DevTool No it won't. Th

Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base

2013-12-18 Thread Arkady_Kanevsky
Spiers Sent: Wednesday, December 18, 2013 9:16 AM To: crowbar Subject: Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base Victor Lowther (victor.lowt...@gmail.com<mailto:victor.lowt...@gmail.com>) wrote: > I do not want to go back to having branches in the

Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base

2013-12-18 Thread John_Terpstra
: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base Victor Lowther (victor.lowt...@gmail.com) wrote: > I do not want to go back to having branches in the top-level repo -- I > strongly prefer that it only hold release-independent (and therefore > non-branch-needin

Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base

2013-12-18 Thread Adam Spiers
Judd Maltin (j...@newgoliath.com) wrote: > Dear Vincent, > > I for one do not believe that CB1 is end of life. I think there is still > good value in the product, strong commit-stream or not. Just the way it is > it is still far ahead of our nearest competition. It was two years ahead of > the p

Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base

2013-12-18 Thread Adam Spiers
Victor Lowther (victor.lowt...@gmail.com) wrote: > I do not want to go back to having branches in the top-level repo -- I > strongly prefer that it only hold release-independent (and therefore > non-branch-needing) things, and pull in other repos that are branched based > on release. We agree (as

Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base

2013-12-18 Thread Judd Maltin
Dear Vincent, I for one do not believe that CB1 is end of life. I think there is still good value in the product, strong commit-stream or not. Just the way it is it is still far ahead of our nearest competition. It was two years ahead of the pack two years ago, and it still remains still far ahe

Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base

2013-12-18 Thread Victor Lowther
On Wed, Dec 18, 2013 at 4:31 AM, Vincent Untz wrote: > Hi Rob, > > Your mail seems to indicate that Crowbar 1.x has reached the end of its > life. This makes me really sad: I think we're proving this view is wrong > on a daily basis, as you can see with the amount of changes going in > Crowbar 1.

Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base

2013-12-18 Thread Vincent Untz
Hi Rob, Your mail seems to indicate that Crowbar 1.x has reached the end of its life. This makes me really sad: I think we're proving this view is wrong on a daily basis, as you can see with the amount of changes going in Crowbar 1.x. I dare to say that its development has never been so fast, and

Re: [Crowbar] Rationalizing Crowbar Project Infrastructure for our new code base

2013-12-18 Thread Ralf Haferkamp
Hi, On Tue, Dec 17, 2013 at 11:22:17PM -0600, rob_hirschf...@dell.com wrote: > All, > > So far, we've accomplished more with Crowbar 1 than I imagined possible. We > have led an new generation of bare metal automated installation and set a > standard that has been noticed. More importantly, we'