Size: 1649
Comment:
|
Size: 1663
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 14: | Line 14: |
* Purchase a robust server and run Xen. Allocate one slice to mail, another for shell, and other slices to members * Pro: Better long-term solution that allows us to make better resource of our rented space |
* Purchase or lease a robust server and run Xen. Allocate one slice to mail, another for shell, and other slices to members * Pro: Better long-term solution that allows us to make better use of our rented space at Peer 1 |
1. IRC Meeting to be held Sunday, June 22, 2008
1.1. Agenda
Our most critical issue is setting up a better email infrastructure. Along with this question, we should put together some longer-term plan about allocating our cabinet resources at Peer 1. There are some secondary agenda items that we should address when we convene.
1.1.1. Primary Agenda Item: Adding a new Mail Server
There seems to a be a consensus among board and admins that we need to allocate a new machine to be a mail server. There are different options available to us:
- Use Xanadu - machine is currently not utilized and in our cabinet
- Pro: Inexpensive
- Con: weak hardware that will consume a scarce resource (rack space). a hard drive or drives still have to be bought and configured, and the RAID card, which might or might not work, has to be installed.
- Purchase or lease a robust server and run Xen. Allocate one slice to mail, another for shell, and other slices to members
- Pro: Better long-term solution that allows us to make better use of our rented space at Peer 1
- Cons: May take longer to set up, and would be expensive
- Additional resources:
Justin's email about expanding and virtualization: http://justin.phq.org/hcoop/expansion_virtualization.txt
Possible configuration for the kind of server that we would need to purchase for this plan: http://justin.phq.org/hcoop/virtual_server.pdf
1.1.2. Secondary Items
Add a secondary MX at hcoop.net: https://bugzilla.hcoop.net/show_bug.cgi?id=369
Give JustinLeitgeb sudo access, and shell on all machines, since he already has on-site access