[OpenAFS-devel] Announcing "ParkBench"
Booker Bense
bbense@gmail.com
Sun, 25 Nov 2012 17:54:40 -0800
--bcaec54ee7286ba5b504cf5c374a
Content-Type: text/plain; charset=ISO-8859-1
It's more a try stuff and see where it goes. The ideal end point would be a
mini-cell run in VM's in which you
could do actual functional tests. I'm not sure I'll get there, but I think
just supporting developers building on
more than platform easily seems like progress.
I'm still figuring out the install after build step.
On Sun, Nov 25, 2012 at 1:54 PM, Jason Edgecombe <jason@rampaginggeek.com>wrote:
> On 11/25/2012 01:08 PM, Booker Bense wrote:
>
>> I've been working on a project to use Vagrant to automate some of the
>> process of working on OpenAFS source code.
>>
>> https://github.com/bbense/**ParkBench<https://github.com/bbense/ParkBench>
>>
>> My goal is to eventually use Vagrant to create a mini-cell for testing.
>> That's a long way off. Right now, I'm working on creating a multi-os build
>> environment.
>>
>> It's in very early stages right now, but I'd welcome any feedback.
>>
>> - Booker C. Bense
>>
>> Hi Booker,
>
> Thanks for doing this. It looks like you're trying to have separate build
> and installation modules...is that correct? What is the end-goal?
>
> Do you plan to have openafs checkout from git, build a package, and
> publish the packages to a repo? If so, I suggest having an option for
> specifying the branch or git commit to use.
>
> Do you plan to publish the cookbooks on the chef community website when
> it's fully baked?
>
> I know practically nothing about chef...I'm learning puppet instead.
>
> Sincerely,
> Jason
> ______________________________**_________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/**mailman/listinfo/openafs-devel<https://lists.openafs.org/mailman/listinfo/openafs-devel>
>
--bcaec54ee7286ba5b504cf5c374a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
It's more a try stuff and see where it goes. The ideal end point would =
be a mini-cell run in VM's in which you<div>could do actual functional =
tests. I'm not sure I'll get there, but I think just supporting dev=
elopers building on=A0</div>
<div>more than platform easily seems like progress.=A0</div><div><br></div>=
<div>I'm still figuring out the install after build step.=A0</div><div =
class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sun, Nov 25, 20=
12 at 1:54 PM, Jason Edgecombe <span dir=3D"ltr"><<a href=3D"mailto:jaso=
n@rampaginggeek.com" target=3D"_blank">jason@rampaginggeek.com</a>></spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5">On 1=
1/25/2012 01:08 PM, Booker Bense wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I've been working on a project to use Vagrant to automate some of the<b=
r>
process of working on OpenAFS source code.<br>
<br>
<a href=3D"https://github.com/bbense/ParkBench" target=3D"_blank">https://g=
ithub.com/bbense/<u></u>ParkBench</a><br>
<br>
My goal is to eventually use Vagrant to create a mini-cell for testing.<br>
That's a long way off. Right now, I'm working on creating a multi-o=
s build<br>
environment.<br>
<br>
It's in very early stages right now, but I'd welcome any feedback.<=
br>
<br>
- Booker C. Bense<br>
<br>
</blockquote></div></div>
Hi Booker,<br>
<br>
Thanks for doing this. It looks like you're trying to have separate bui=
ld and installation modules...is that correct? What is the end-goal?<br>
<br>
Do you plan to have openafs checkout from git, build a package, and publish=
the packages to a repo? If so, I suggest having an option for specifying t=
he branch or git commit to use.<br>
<br>
Do you plan to publish the cookbooks on the chef community website when it&=
#39;s fully baked?<br>
<br>
I know practically nothing about chef...I'm learning puppet instead.<br=
>
<br>
Sincerely,<br>
Jason<br>
______________________________<u></u>_________________<br>
OpenAFS-devel mailing list<br>
<a href=3D"mailto:OpenAFS-devel@openafs.org" target=3D"_blank">OpenAFS-deve=
l@openafs.org</a><br>
<a href=3D"https://lists.openafs.org/mailman/listinfo/openafs-devel" target=
=3D"_blank">https://lists.openafs.org/<u></u>mailman/listinfo/openafs-devel=
</a><br>
</blockquote></div><br></div>
--bcaec54ee7286ba5b504cf5c374a--