|
Size: 1513
Comment: first commit, moving page
|
Size: 1316
Comment: Member freeze scripts?
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Sunday, June 22, 2008 == | = IRC Meeting to be held Sunday, June 22, 2008 = |
| Line 3: | Line 3: |
| 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. | == Agenda == |
| Line 5: | Line 5: |
| === Adding a new Mail Server === | We have recently had quite a bit of downtime, and it indicates that we need to improve and expand our infrastructure. Technical proposals for expansion have been requested on hcoop-sysadmin, and they should be complete by the time that the board meets. The primary purpose of the meeting is to figure out how financial and human resources can be allocated to improving our infrastructure. |
| Line 7: | Line 7: |
| 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: | === Primary Agenda Item: Improving our infrastructure === |
| Line 9: | Line 9: |
| * 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 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 * 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 |
We'll summarize proposals for expansion of our infrastructure, and figure out how much we can allocate for doing so. We should also be able to figure out a timeline for making those resources available. |
| Line 19: | Line 11: |
| === Secondary issues === | Things to cover in "proposals for expansion of our infrastructure": * Available systems awaiting setup * Virtualization * Offsite backups (S3) * Paid staff === Secondary Agenda Items === Ancillary items that we should be able to take care of, and things that we just need to vote on while we have a quorum. |
| Line 23: | Line 23: |
| * Formulate a policy for service plans on servers * Member freeze scripts? |
1. IRC Meeting to be held Sunday, June 22, 2008
1.1. Agenda
We have recently had quite a bit of downtime, and it indicates that we need to improve and expand our infrastructure. Technical proposals for expansion have been requested on hcoop-sysadmin, and they should be complete by the time that the board meets. The primary purpose of the meeting is to figure out how financial and human resources can be allocated to improving our infrastructure.
1.1.1. Primary Agenda Item: Improving our infrastructure
We'll summarize proposals for expansion of our infrastructure, and figure out how much we can allocate for doing so. We should also be able to figure out a timeline for making those resources available.
Things to cover in "proposals for expansion of our infrastructure":
- Available systems awaiting setup
- Virtualization
- Offsite backups (S3)
- Paid staff
1.1.2. Secondary Agenda Items
Ancillary items that we should be able to take care of, and things that we just need to vote on while we have a quorum.
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
- Formulate a policy for service plans on servers
- Member freeze scripts?