Resistence is futile - London Hackspace

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Resistence is futile
Received-SPF: pass (google.com: domain of sam.lindenrat...@gmail.com designates 209.85.220.54 as permitted sender) client-ip=209.85.220.54;
MIME-Version: 1.0
In-Reply-To: <6539445e-5465-48d5-bfd4-dcf58f0b19f4@googlegroups.com>
References: <CADHhd=wury3oqVPuqwkdyOMcdOOXqB-zTpnVXBwx-i6V4do...@mail.gmail.com>
 <6539445e-5465-48d5-bfd4-dcf58f0b19f4@googlegroups.com>
From: SamLR <sam.lindenrat...@gmail.com>
Date: Fri, 5 Oct 2012 17:37:16 +0100
Message-ID: <CAGqn4cZ_gB0NgcNBzHHBiB4tSEpt=ZchDH-t8rS+fCRSOS=...@mail.gmail.com>
Subject: Re: [london-hack-space] Re: Resistence is futile
To: london-hack-space@googlegroups.com
Content-Type: multipart/alternative; boundary=e89a8fb207b850d1e104cb527df5

--e89a8fb207b850d1e104cb527df5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<2cents>
If we can reduce the number of individual machines (babbage, lazor etc) and
replace with thin clients running from a single, low power server this is
good.

If we have some huge mega machine consisting of multiple machines taking up
~1m^3 which gets spun up once in a blue moon when someone wants to play
around with a massively parallelised machine: sod that.

Assuming we can virtualise babbage and layzor for under 300W we save money
(and don't lose too much space). Keeping a behemoth will be ultimately
useless. Make it, spin it up for the fun value then sell the bloody thing.

*tl;dr: keep one, low power server; use it to replace babbage, layzor and
give people a place to spin up VMs as required*
</2cents>

S

On 5 October 2012 17:09, Dean Forbes <m...@deanforbes.com> wrote:

> As we have the hardware it would in my mind be criminal not to use it and
> build a beast that can be turned on and used when we require big horse
> power
>
> I don't have a need for it personally but is the hackspace not about
> exploring skills and boundaries, pulling that creativity out that we all
> have etc and applying it to hacking
>
> 6 months ago I did not need a solder station .... today I spent a few
> hours at it
>
> :-)
>
>
>
> On Thursday, 4 October 2012 20:42:16 UTC+1, Matthew Copperwaite wrote:
>
>> TL;DR: Borg is useful, it will be moved in to the backroom and we will
>> monitor power consumption.
>>
>> So first off the 'eatallthepower' machine that is/was in the main room
>> will not be Borg, we're going for a lower power version. There's been
>> a lot of debate about Borg. Most of the concern has been about:
>> 1. That it is taking up space,
>> 2. Will it be useful,
>> 3. The electricity costs.
>>
>> I am pro Borg but these are valid concerns. Usefulness is a pretty
>> easy one to deal with. It can be used for many things including
>> recording the cams to give poor Babbage a bit of breathing room,
>> putting individual shell accounts on there so Babbage doesn't get
>> overloaded and eventually putting Babbage out to pasture. Other
>> suggestions have included giving people an environment for
>> crosscompiling (moving it from Lovelace) and moving a lot of the
>> random computers around the space that do just one thing.
>>
>> This will have the benefit of saving us some power by sharing it in
>> one machine. This goes some way to help offset the extra power Borg
>> will take.
>>
>> Obviously Borg may still consume more power and some people are
>> concerned about the extra cost. We (tgreer and me) will be monitoring
>> the usage as closely as we can, our goal is to be under 275W.
>> Admittedly a number I plucked out of my arse but seems like a
>> reasonable goal based upon similar hardware that is heavily used. We
>> costed this to be about =A327 per month but obviously this is the
>> maximum and we aim to be well under that. If it goes over 275W
>> regularly we can then have a discussion about how best to either
>> reduce it, or using a different solution entirely.
>>
>> We will of course be keeping a careful eye on the power consumption to
>> get a baseline. We'll also try to get a gauge from Babbage, Lovelace
>> and Tesla to have a comparison.
>>
>> As for location, we have devised a cunning plan. It has been
>> previously discussed that the Laser Cutter be placed in the back room
>> in the workshop, potentially we could move that in there and stack the
>> Borg underneath it. It's not ideal, it may not fit, and we need magic
>> solexious approval, but it's worth a try, and it gets it out of the
>> main or quiet areas. I'll be in the space on Monday so I'll attempt to
>> measure stuff up and move whatever needs moving (help would be
>> appreciated). Tgreer is north of the border until Tuesday so it will
>> be worked on then.
>>
>> I'm open to better suggestions there does seem a general consensus
>> that it Borg is a good idea, and a very vocal minority totally against
>> it for one reason or another. Hopefully greater transparency and a
>> proper plan will improve that.
>>
>> Matt
>>
>

--e89a8fb207b850d1e104cb527df5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

&lt;2cents&gt;<div>If we can reduce the number of individual machines (babb=
age, lazor etc) and replace with thin clients running from a single, low po=
wer server this is good.=A0</div><div><br></div><div>If we have some huge m=
ega machine consisting of multiple machines taking up ~1m^3 which gets spun=
 up once in a blue moon when someone wants to play around with a massively =
parallelised machine: sod that.=A0</div>


<div><br></div><div>Assuming we can virtualise babbage and layzor for under=
 300W we save money (and don&#39;t lose too much space). Keeping a behemoth=
 will be ultimately useless. Make it, spin it up for the fun value then sel=
l the bloody thing.=A0</div>


<div><br></div><div><b>tl;dr: keep one, low power server; use it to replace=
 babbage, layzor and give people a place to spin up VMs as required</b></di=
v><div>&lt;/2cents&gt;</div><div><br></div><div>S</div><div><br><div class=
=3D"gmail_quote">


On 5 October 2012 17:09, Dean Forbes <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:m...@deanforbes.com" target=3D"_blank">m...@deanforbes.com</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex">


<div>As we have the hardware it would in my mind be criminal not to use it =
and build a beast that can be turned on and used when we require big horse =
power=A0</div><div><br></div><div>I=A0don&#39;t=A0have a need for it person=
ally but is the hackspace not about exploring skills and boundaries, pullin=
g that creativity out that we all have etc and applying it to hacking=A0</d=
iv>


<div><br></div><div>6 months ago I did not need a solder station .... today=
 I spent a few hours at it=A0</div><div><br></div><div>:-)</div><div><div><=
br></div><div><br></div><div><br></div>On Thursday, 4 October 2012 20:42:16=
 UTC+1, Matthew Copperwaite  wrote:</div>


<div><div><blockquote class=3D"gmail_quote" style=3D"margin:0;margin-left:0=
.8ex;border-left:1px #ccc solid;padding-left:1ex">TL;DR: Borg is useful, it=
 will be moved in to the backroom and we will
<br>monitor power consumption.
<br>
<br>So first off the &#39;eatallthepower&#39; machine that is/was in the ma=
in room
<br>will not be Borg, we&#39;re going for a lower power version. There&#39;=
s been
<br>a lot of debate about Borg. Most of the concern has been about:
<br>1. That it is taking up space,
<br>2. Will it be useful,
<br>3. The electricity costs.
<br>
<br>I am pro Borg but these are valid concerns. Usefulness is a pretty
<br>easy one to deal with. It can be used for many things including
<br>recording the cams to give poor Babbage a bit of breathing room,
<br>putting individual shell accounts on there so Babbage doesn&#39;t get
<br>overloaded and eventually putting Babbage out to pasture. Other
<br>suggestions have included giving people an environment for
<br>crosscompiling (moving it from Lovelace) and moving a lot of the
<br>random computers around the space that do just one thing.
<br>
<br>This will have the benefit of saving us some power by sharing it in
<br>one machine. This goes some way to help offset the extra power Borg
<br>will take.
<br>
<br>Obviously Borg may still consume more power and some people are
<br>concerned about the extra cost. We (tgreer and me) will be monitoring
<br>the usage as closely as we can, our goal is to be under 275W.
<br>Admittedly a number I plucked out of my arse but seems like a
<br>reasonable goal based upon similar hardware that is heavily used. We
<br>costed this to be about =A327 per month but obviously this is the
<br>maximum and we aim to be well under that. If it goes over 275W
<br>regularly we can then have a discussion about how best to either
<br>reduce it, or using a different solution entirely.
<br>
<br>We will of course be keeping a careful eye on the power consumption to
<br>get a baseline. We&#39;ll also try to get a gauge from Babbage, Lovelac=
e
<br>and Tesla to have a comparison.
<br>
<br>As for location, we have devised a cunning plan. It has been
<br>previously discussed that the Laser Cutter be placed in the back room
<br>in the workshop, potentially we could move that in there and stack the
<br>Borg underneath it. It&#39;s not ideal, it may not fit, and we need mag=
ic
<br>solexious approval, but it&#39;s worth a try, and it gets it out of the
<br>main or quiet areas. I&#39;ll be in the space on Monday so I&#39;ll att=
empt to
<br>measure stuff up and move whatever needs moving (help would be
<br>appreciated). Tgreer is north of the border until Tuesday so it will
<br>be worked on then.
<br>
<br>I&#39;m open to better suggestions there does seem a general consensus
<br>that it Borg is a good idea, and a very vocal minority totally against
<br>it for one reason or another. Hopefully greater transparency and a
<br>proper plan will improve that.
<br>
<br>Matt
<br></blockquote></div></div></blockquote></div><br></div>

--e89a8fb207b850d1e104cb527df5--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
