[OpenAFS-devel] Retiring the debian-i386 buildbot slave. Do we
need a replacement?
Nathaniel Hatley
nathaniel.hatley@gmail.com
Tue, 3 Feb 2015 16:00:11 -0500
--001a1135ebe457345e050e355be6
Content-Type: text/plain; charset=UTF-8
Good Afternoon
I can host Debian Jessie i386 and amd64 slaves. I'll get them setup
tonight.
-Nathan
On Wed, Jan 21, 2015 at 3:57 PM, Garrett Wollman <wollman@csail.mit.edu>
wrote:
> <<On Tue, 20 Jan 2015 20:43:18 -0500, Jason Edgecombe <
> jason@rampaginggeek.com> said:
>
> > What types of management do you need others to provide?
> > * initial installation of OS
>
> Since VMs would be set up from images this is not required.
>
> > * general maintenance and patching of OS
>
> For our (CSAIL's) managed Ubuntu VMs this happens semi-automatically.
> For a generic Debian I would want someone else to be keeping an eye on
> it. (I already do this for the FreeBSD buildslaves.)
>
> > * installation and management of the buildslave software (without root
> > access)
>
> Installation and configuration of the actual buildslave is something
> that I can do, but since I'm not familiar with doing it on Debianoid
> systems it would be nicer to have a recipe to follow. (On our managed
> Ubuntu platform we would get Puppet to do this, if there was any
> chance of having more than one VM.)
>
> -GAWollman
>
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>
--001a1135ebe457345e050e355be6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Good Afternoon<br></div><div><br>I can host Debian Je=
ssie i386 and amd64 slaves.=C2=A0 I'll get them setup tonight.<br><br><=
/div>-Nathan<br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">On Wed, Jan 21, 2015 at 3:57 PM, Garrett Wollman <span dir=3D"ltr"><=
;<a href=3D"mailto:wollman@csail.mit.edu" target=3D"_blank">wollman@csail.m=
it.edu</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=
=3D""><<On Tue, 20 Jan 2015 20:43:18 -0500, Jason Edgecombe <<a hr=
ef=3D"mailto:jason@rampaginggeek.com">jason@rampaginggeek.com</a>> said:=
<br>
<br>
> What types of management do you need others to provide?<br>
> * initial installation of OS<br>
<br>
</span>Since VMs would be set up from images this is not required.<br>
<span class=3D""><br>
> * general maintenance and patching of OS<br>
<br>
</span>For our (CSAIL's) managed Ubuntu VMs this happens semi-automatic=
ally.<br>
For a generic Debian I would want someone else to be keeping an eye on<br>
it.=C2=A0 (I already do this for the FreeBSD buildslaves.)<br>
<span class=3D""><br>
> * installation and management of the buildslave software (without root=
<br>
> access)<br>
<br>
</span>Installation and configuration of the actual buildslave is something=
<br>
that I can do, but since I'm not familiar with doing it on Debianoid<br=
>
systems it would be nicer to have a recipe to follow.=C2=A0 (On our managed=
<br>
Ubuntu platform we would get Puppet to do this, if there was any<br>
chance of having more than one VM.)<br>
<br>
-GAWollman<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
_______________________________________________<br>
OpenAFS-devel mailing list<br>
<a href=3D"mailto:OpenAFS-devel@openafs.org">OpenAFS-devel@openafs.org</a><=
br>
<a href=3D"https://lists.openafs.org/mailman/listinfo/openafs-devel" target=
=3D"_blank">https://lists.openafs.org/mailman/listinfo/openafs-devel</a><br=
>
</div></div></blockquote></div><br></div>
--001a1135ebe457345e050e355be6--