Sebastian,
thanks for updating us all.
Simon
-Original Message-
From: crowbar-bounces On Behalf Of Sebastian Zimmermann
Sent: Tuesday, October 15, 2013 3:07 PM
To: crowbar
Subject: Re: [Crowbar] Build fails
Re-synced and installed libxml-ruby gem. After adding 8.07.07_MegaCLI.zip and
S
JB,
currently the Roxy branch is still mostly Grizzly based, we're expecting to
make a major push towards Havana in the next 2 weeks. So stay tuned for now,
and watch the work over the next 2 weeks.
Simon
-Original Message-
From: crowbar-bounces On Behalf Of Jonathan Brownell
Sent: Tue
It's been about 6 weeks since the Roxy branch was cut, to enable
Havana support in our barclamps. How is that development going, and
what's the status of Havana support?
In my informal testing it looks like some barclamps are working OK,
but I notice that the Quantum barclamp still doesn't make mu
Re-synced and installed libxml-ruby gem. After adding
8.07.07_MegaCLI.zip and SAS2IRCU_P16.zip to my home folder the build
process finished without any more errors.
Thanks! :-)
-Sebastian
2013/10/15 Sebastian Zimmermann :
> Re-synced and installed libxml-ruby gem. After adding
> 8.07.07_MegaCLI
On Tue, Oct 15, 2013 at 1:22 PM, wrote:
> Thanks Victor.
> For HW enumeration bullet, does CB2.0 handles marking disks used for boot
> so they are not available for swift and cinder?
>
Nope, hence my bullet point about needing a framework for enumerating,
reserving, and releasing resources.
>
Thanks Victor.
For HW enumeration bullet, does CB2.0 handles marking disks used for boot so
they are not available for swift and cinder?
Even thou CB-2.0 does not enumerate HW does it provide a utility for workload
to verify that available node resource are sufficient for workload role on a
node
Shane Gibson (shane_gib...@symantec.com) wrote:
> > -Original Message-
> > Subject: Re: [Crowbar] New Server for Crowbar Lists
> >
> > > > In my experience, users often prefer a forum style interface over a
> > > > mailing list. If we investigate alternatives, I think we should
> > > > con
At this point, Crowbar 2.0 is ready to start porting some of our
non-core barclamps over from the 1.x codebase, and doing an initial cut
of our first workload (Ceph).
We are also ready to start bringing other folks up to speed on the
Crowbar 2.0 codebase. To help with that process (and not at all
Yes, we were virtualizing while we set up our try & buy so that we could
get acclimated to the product. I am aware it is meant for bare-metal
hardware. We were able to source some old Dell PowerEdge's, so I'm in
the process of setting up those in place of our (broken) virtual setup.
On the upsi
