Hi Darrel,
I've created some shell scripts for crowbar multi-node setups back in the
day https://github.com/iteh/crowbar-virtualbox
Maybe this is starting point for what you want to accomplish.
- Edmund
2013/11/21 Darrel O'Pry
>
> On Thu, Nov 21, 2013 at 6:45 AM, Adam Spiers wrote:
>
>> Darr
Sascha Peilicke (speili...@suse.com) wrote:
> On Thursday 21 November 2013 08:41:51 Victor Lowther wrote:
> > On Thu, Nov 21, 2013 at 6:33 AM, Adam Spiers wrote:
> > > Sascha Peilicke (speili...@suse.com) wrote:
> > > > I would also wonder why we append
> > > > /master to every branch :-) Why not
That is pretty awesome and should be a developer experience that is
maintained, but opened to a wider audience. I know a lot of good admins
and dev ops engineers who work primarily on mac or windows in the
enterprise space.
On Thu, Nov 21, 2013 at 12:53 PM, Victor Lowther
wrote:
> On Thu, Nov
On Thursday 21 November 2013 08:41:51 Victor Lowther wrote:
> On Thu, Nov 21, 2013 at 6:33 AM, Adam Spiers wrote:
> > Sascha Peilicke (speili...@suse.com) wrote:
> > > I would also wonder why we append
> > > /master to every branch :-) Why not just "release/roxy" ? Or better
> > > "stable/roxy" wh
Sascha Peilicke (speili...@suse.com) wrote:
> On the other hand, we could probably kill some branches across
> repos.
Great idea - very low-hanging fruit ... if we are scared about losing
important stuff for ever, we can always take a backup first.
> This is what I currently have just for the "cr
On Thu, Nov 21, 2013 at 6:33 AM, Adam Spiers wrote:
> Sascha Peilicke (speili...@suse.com) wrote:
> > I would also wonder why we append
> > /master to every branch :-) Why not just "release/roxy" ? Or better
> > "stable/roxy" which seems like a more common pattern in the git world.
>
> Because th
On Thursday 21 November 2013 09:23:11 Judd Maltin wrote:
> Semver would be just great! 02.00.01 ?
Depends on how you put it. If Crowbar-2.0 is already out there and we're still
fixing it, then it would be something like 2.0.1. If we are very close to
releasing CB2, it's more like 2.0a1. However,
On Thu, Nov 21, 2013 at 11:38 AM, Darrel O'Pry wrote:
>
> vagrant up dev
> vagrant up ubuntu12.10-admin
> vagrant up bare-node1
> vagrant up bare-node2
> vagrant up bare-node3
> vagrant up bare-node4
>
> Which could all be wrapped up in a grunt, make, rake, shell script task...
> There could even
Semver would be just great! 02.00.01 ?
Judd Maltin
1-917-882-1270
I have suffering to learn compassion once and once again.
On Nov 21, 2013 7:34 AM, "Adam Spiers" wrote:
> Sascha Peilicke (speili...@suse.com) wrote:
> > On the other hand, we could probably kill some branches across
> > repos.
>
On Thu, Nov 21, 2013 at 6:45 AM, Adam Spiers wrote:
> Darrel O'Pry (darrel.o...@gmail.com) wrote:
>
> > I hear a lot of knee jerk throw everything out and start over
> undertones. I
> > don't that that is a wise idea as it loses history. One of the things I
> > love about git is history. Also be
On Thursday 21 November 2013 11:29:45 Adam Spiers wrote:
> [lots of very good remarks,as usual...]
I agree with Adam that the main repo has to have proper branches for releases.
Once we have that, we can cleanup the confusing directory layout (hey, iit's
only 20 install-chef.sh scripts, nice).
Darrel O'Pry (darrel.o...@gmail.com) wrote:
> The project has come along way since I first started following it a few
> years ago. What is there now is a vast improvement over what I first found
> which were the links to Rob's blog. It has been steady forward
> progress.
Agreed.
> I hear a lot of
Simon Jakesch (simon_jake...@dell.com) wrote:
> I've gone through the entire thread and I am going to make an
> attempt at summarizing this conversation to flush out the most
> burning and critical issues around this discussion. I've summarized
> what I believe the high-level argument to be. Please
Rob Hirschfeld (rob_hirschf...@dell.com) wrote:
> We want to solve those exact problems in CB2 but that creates a huge
> cleanup lift for CB1 that risks CB1 stability.
Sorry - we must have a major disconnect here because I can't
understand this at all. Please can you explain what you mean in more
Message -
From: Adam Spiers [mailto:aspi...@suse.com]
Sent: Wednesday, November 20, 2013 11:14 AM Central Standard Time
To: crowbar
Subject: Re: [Crowbar] Crowbar 2 Hack Report
Sorry, I don't understand your logic.
Newbie *users* are confused because the website does not contain a
quickl
ment
> as well as testing, it’s a definite need.
>
>
>
> Sak
>
> -Original Message-
> From: crowbar-bounces On Behalf Of Adam Spiers
> Sent: 20 November 2013 17:31
> To: crowbar
> Subject: Re: [Crowbar] Crowbar 2 Hack Report
>
> John Terpstra (john_terp
actually resolving any of the "newbie" confusion or even aggregating the
confusion on documentation
- search engine indexes not directing people properly
From: crowbar-bounces On Behalf Of Rai, Sakvinder
Sent: Wednesday, November 20, 2013 3:40 PM
To: crowbar
Subject: Re: [Crowbar] Crow
owbar] Crowbar 2 Hack Report
John Terpstra (john_terps...@dell.com) wrote:
> The fact that Crowbar has a high barrier to new participants is
> undeniable. It is of utmost importance to the future of the project
> that the obstacles to entry of new developers must be removed.
Agreed!
> T
-bounces On Behalf Of Judd Maltin
Sent: 20 November 2013 10:01
To: Adam Spiers
Cc: crowbar
Subject: Re: [Crowbar] Crowbar 2 Hack Report
All the branching doesn't address the confusing situation for newbies who we
are trying to attract to the project. Since we'll be leaving a huge portion o
John Terpstra (john_terps...@dell.com) wrote:
> The fact that Crowbar has a high barrier to new participants is
> undeniable. It is of utmost importance to the future of the project
> that the obstacles to entry of new developers must be removed.
Agreed!
> The positive steps to remove barriers s
Judd Maltin (j...@newgoliath.com) wrote:
> Furthermore, since every administrator I talk to asks me "Isn't Crowbar a
> Dell-only project," I think it's a good idea to embrace the OpenCrowbar
> project name.. much as SUSE is recognized by OpenSUSE, even in the press
> http://linux.slashdot.org/story
Sorry, I don't understand your logic.
Newbie *users* are confused because the website does not contain a
quickly and easily digestible introduction explaining the architecture
and how to get started.
If you need convincing that the website is inadequate, compare it to
https://juju.ubuntu.com/
: [Crowbar] Crowbar 2 Hack Report
Furthermore, since every administrator I talk to asks me "Isn't Crowbar a
Dell-only project," I think it's a good idea to embrace the OpenCrowbar project
name.. much as SUSE is recognized by OpenSUSE, even in the press
http://linux.slashdo
Furthermore, since every administrator I talk to asks me "Isn't Crowbar a
Dell-only project," I think it's a good idea to embrace the OpenCrowbar
project name.. much as SUSE is recognized by OpenSUSE, even in the press
http://linux.slashdot.org/story/13/11/19/2353236/opensuse-131-released-and-revie
me
To: Adam Spiers
Cc: Dearborn, Chris; crowbar; Hirschfeld, Rob
Subject: Re: [Crowbar] Crowbar 2 Hack Report
All the branching doesn't address the confusing situation for newbies who we
are trying to attract to the project. Since we'll be leaving a huge portion of
the 1.x codebase behi
All the branching doesn't address the confusing situation for newbies who
we are trying to attract to the project. Since we'll be leaving a huge
portion of the 1.x codebase behind for good and forever, I think the gains
of making it easy for newbies to join FAR outweighs branching and cleaning
up.
christopher_dearb...@dell.com (christopher_dearb...@dell.com) wrote:
> Rob,
>
> I think you misunderstood my recommendation below. What I'm
> proposing is that we branch everything, including the main Crowbar
> repo.
I think I'm on the same page as you here Chris, although the above
statement mak
t;mailto:aspi...@suse.com>; crowbar
Subject: RE: [Crowbar] Crowbar 2 Hack Report
On your -1. I'm certain that we can create new CB2 repos that address issues
in Crowbar 1; however...
· We shouldn't/cannot touch the CB1 repos without a major investment in
validation that I t
m: crowbar-bounces On Behalf Of Dearborn, Chris
Sent: Monday, November 18, 2013 6:58 AM
To: aspi...@suse.com; crowbar
Subject: Re: [Crowbar] Crowbar 2 Hack Report
I agree that we need to get rid of the releases dir in the root crowbar repo
and begin branching all repos (including the root crowbar repo
I agree, Chris, I don't think we need a new org.
From: crowbar-bounces On Behalf Of Dearborn, Chris
Sent: Monday, November 18, 2013 8:58 AM
To: aspi...@suse.com; crowbar
Subject: Re: [Crowbar] Crowbar 2 Hack Report
I agree that we need to get rid of the releases dir in the root crowbar repo
Behalf Of Adam Spiers
Sent: Sunday, November 17, 2013 10:06 AM
To: crowbar
Subject: Re: [Crowbar] Crowbar 2 Hack Report
Rob Hirschfeld (rob_hirschf...@dell.com) wrote:
> That's a clear +1 towards new Github Org to me.
Hmm, that's not clear to me - possibly the way to go, but I thi
ot;
> Anyone have objections or issues?
I wouldn't be keen on seeing a new org until I'm clear about the
answers to the above questions.
> -Original Message-
> From: crowbar-bounces On Behalf Of Adam Spiers
> Sent: Saturday, November 16, 2013 11:16 PM
> To: crowba
crowbar
Subject: Re: [Crowbar] Crowbar 2 Hack Report
Restructuring the repositories is long overdue, so thank you for getting
behind this. Victor and I discussed it at some length during my Austin visit,
and we documented some of our ideas here:
http://crowbar.sync.in/crowbar-repos
You w
Restructuring the repositories is long overdue, so thank you for
getting behind this. Victor and I discussed it at some length during
my Austin visit, and we documented some of our ideas here:
http://crowbar.sync.in/crowbar-repos
You will see that in addition to restructuring, we mention a
Rob,
These are excellent suggestions
1) Workload and barclamp repos. I like the organizing principle here. The
natural breakdown of workloads into barclamps, and then barclamps into
their script/puppet/chef code can be managed with tools more familiar to
those communities: berkshelf/librarian, e
35 matches
Mail list logo
