Assuming the later, check among Supermicro & Dell servers. Last time I needed to setup a cluster, the Dell R610s were a good pick, giving great manageability over the LAN, low volume and decent features (balanced storage space along with cpu capacity, around 8 cores + 8 TBs per 1u blade). Don't rule out also options like Shuttle XPCs, they are damned robust in thermal aspects (hey, you'll be running these continuously, won't you?). Finally, don't underestimate the need for local sysadmining; you will likely need to setup a queueing system (Torque, *PBS*, SLURM, SGE, LSF, NQS, Condor) and manage the whole thing. This won't happen automatically, take a note on that. If you run something of the pbs or sge family I can happily help with setting up a tool called qtop
I'm pretty certain that the science is sound), Morgado's pump is in limbo because he hasn't yet found anyone who'd lend him $4-million or $10-million to build a factory. He has plenty of offers to buy the technology outright, but he has the audacity to presume that he should be the one to profit from his invention.
Imagine if the demand for energy suddenly plunged by more than 25%. Oil is only going for $100/barell because demand roughly matches supply. If supply exceeds demand by a significant percentage, we'd be back to $1/gallon gas in a heartbeat.
If Morgado's invention is at present tested and reliable enough to do all that, it worths more than 10^7 $ and everyone who has that money not investing it is stupid. If not, don't make us cry for his uninvested intellectual property, he is just a hacking good inventor who can build something lesser to raise 10^7 $s until the next stage. In short, if he has faith about this invention, then he should make a business compromise. btw. oil supply is controlled by OPEC, prices are not really an accident.
The problem is your "ownership" is derived from management's ownership of that hardware and software. So if they demand access, you do not have the authority to deny it.
Yes and no.
If the the authority clause can imply full automatic access, then the boss should ask for a copy of all passwords, disks or files, too.
I am not sure that this is even automatically permitted under many jurisdictions. Think of forensics and liability here.
We can understand the problem as similar one to an airplane owner and a pilot (or a shipping magnate and a captain, etc):
Being the owner of the plane does not imply that you should fly it every now and then, maybe "on-the-fly", just because you own it. You surely have reserved the right to do so. BUT. The pilot should also have the right, to exit the plane safely on ground upon your demand, inform his crew on the spot of his actions and properly handing over the control. This is how business should be done.
Talking about systems, a solution could be to put all administrative passwords in an envelope, seal it, hand it to your boss on the condition that you take responsibility of the systems as long as the envelope remains sealed. If the envelope is broken, it's his job.
If you are asked to hand-over the systems, you unseal together the envelope; the "agreed protocol" takes care of the rest. At any such step, it is appropriate for the sysadmin to disclaim further responsibility to his users, in some brief, formal, communication.
I refuse to co-sysadmin my systems together with my managers, unless they can also share the responsibility, solve problems etc.
After all, *I* have choice in the job market and I am authoritative enough to make use of that.
In the end of the day, it's just a question of professionalism from all parties involved.
OSS advocacy and Apple don't mix. Stop selling your soul for shiny baubles.
OSS advocacy and Mobile Phones don't mix. Stop writing software for it and making your phonecalls with it.
If all else fails, lower your standards.
