Leaving the procurement ticket where it is and linking it.
This is the setup ticket for the freenode server. They require Debian, and this
system will also be placed in its own sandbox vlan.
--
Rob Halsell
Operations Engineer
Refers To:
{T81444}
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | coren | T82958 Deploy a freenode server | |||
| Restricted Task | |||||
| Restricted Task |
i just wanted to look at installing the Debian, and saw it's done already
dickson login:
Debian GNU/Linux 7 dickson ttyS1
HEAD is now at 367294d Add dickson to DNS (new freenode server)
but it didn't appear to be in autoinstall stuff, did you use debtakeover?
(http://freecode.com/projects/debtakeover)
could you add my key to dickson? i'd like to help with the setup/maintenance of
this one and talk about where we treat it different from other servers and
where we don't. are we adding it to puppet?
On Mon Sep 23 11:32:38 2013, dzahn wrote:
are we adding it to puppet?
No us; freenode manages their servers with puppet, but from their own
puppetmaster.
I'm still working out the technical details of deploying our keys with them, I
should know how to go about it today.
The server is now up and running, and while not advertised as such is part of
freenode.
For opsen who want to have access to the box, please email me a public ssh key;
I can have it included in their puppet config.
On Tue Sep 24 20:44:27 2013, Coren wrote:
For opsen who want to have access to the box, please email me a public
ssh key;
I can have it included in their puppet config.
mailed a new key (separate from regular prod key)