Re: [Crowbar] Resolving inter-repository dependencies for CB 2.0

2014-01-03 Thread Adam Spiers
Victor Lowther (victor.lowt...@gmail.com) wrote: > This is intended to work as a starting point for a discussion of what tool > we should use to use to track inter-repository dependencies for CB2.0 in > the opencrowbar org. Before evaluating the tools I think it would be worth trying to clarify th

Re: [Crowbar] Resolving inter-repository dependencies for CB 2.0

2014-01-03 Thread Victor Lowther
On Fri, Jan 3, 2014 at 5:33 AM, Adam Spiers wrote: > Victor Lowther (victor.lowt...@gmail.com) wrote: > > This is intended to work as a starting point for a discussion of what > tool > > we should use to use to track inter-repository dependencies for CB2.0 in > > the opencrowbar org. > > Before e

Re: [Crowbar] Resolving inter-repository dependencies for CB 2.0

2014-01-03 Thread Adam Spiers
Victor Lowther (victor.lowt...@gmail.com) wrote: > On Fri, Jan 3, 2014 at 5:33 AM, Adam Spiers wrote: > > Victor Lowther (victor.lowt...@gmail.com) wrote: > > > This is intended to work as a starting point for a discussion of what tool > > > we should use to use to track inter-repository dependenc

Re: [Crowbar] Resolving inter-repository dependencies for CB 2.0

2014-01-03 Thread Victor Lowther
On Fri, Jan 3, 2014 at 8:52 AM, Adam Spiers wrote: > Victor Lowther (victor.lowt...@gmail.com) wrote: > > On Fri, Jan 3, 2014 at 5:33 AM, Adam Spiers wrote: > > > Victor Lowther (victor.lowt...@gmail.com) wrote: > > > > This is intended to work as a starting point for a discussion of > what tool

Re: [Crowbar] Resolving inter-repository dependencies for CB 2.0

2014-01-03 Thread Adam Spiers
Victor Lowther (victor.lowt...@gmail.com) wrote: > On Fri, Jan 3, 2014 at 8:52 AM, Adam Spiers wrote: > > Victor Lowther (victor.lowt...@gmail.com) wrote: > > > On Fri, Jan 3, 2014 at 5:33 AM, Adam Spiers wrote: > > > > Victor Lowther (victor.lowt...@gmail.com) wrote: > > > > > This is intended t

[Crowbar] packaging barclamps in gems

2014-01-03 Thread Adam Spiers
As requested by Victor, I'd like to start a conversation about the idea of packaging barclamps as gems (which are then optionally automatically wrapped in .rpms / .debs). This was first proposed a *long* time ago by James Tan, and has occasionally surfaced in conversations since then, but other th

Re: [Crowbar] packaging barclamps in gems

2014-01-03 Thread John_Terpstra
Adam, The things you have brought up here are most timely. As we begin to address the way that Crowbar2 will be packaged to facilitate the creation and deployment of admin nodes and workloads we need to adopt a different strategy from the Crowbar1 ISO build approach. The Crowbar project should

Re: [Crowbar] Resolving inter-repository dependencies for CB 2.0

2014-01-03 Thread David_Paterson
Is it worthwhile to look at octokit and writing a dev tool replacement in Ruby? Octokit is the github supported Ruby toolkit for the github API. https://github.com/octokit/octokit.rb Thanks, dp From: crowbar-bounces On Behalf Of Victor Lowther Sent: Friday, January 03, 2014 10:49 AM To: Adam

Re: [Crowbar] Resolving inter-repository dependencies for CB 2.0

2014-01-03 Thread Victor Lowther
On Fri, Jan 3, 2014 at 1:42 PM, wrote: > Is it worthwhile to look at octokit and writing a dev tool replacement in > Ruby? Octokit is the github supported Ruby toolkit for the github API. > > > > https://github.com/octokit/octokit.rb > I did that once. The startup overhead that using bundler a

Re: [Crowbar] packaging barclamps in gems

2014-01-03 Thread Adam Spiers
John Terpstra (john_terps...@dell.com) wrote: > [Uncle] How can we move this forwards? What is the next step and who should > drive it? How can I help? I think the next step is addressing any objections that anyone can come up with ;-) [snipped] > Ensuring that all files get copied / moved / sy

Re: [Crowbar] packaging barclamps in gems

2014-01-03 Thread Rob_Hirschfeld
John, My sense on this is that gems are more for Rails extensions (parts of apps) than a full application. While OpenCrowbar is mostly Rails, it is NOT only Rails. There's quite a bit of extra stuff (chef, erlang, scripts, docs, etc) that we package at the same level as the Rails app. I fou