|
Size: 1513
Comment: first commit, moving page
|
← Revision 15 as of 2008-07-07 04:28:21 ⇥
Size: 2269
Comment: converted to 1.6 markup
|
| 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 (with conclusions) == |
| 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": |
| Line 21: | Line 13: |
| * 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 |
* Available systems awaiting setup - We will set up IBM xSeries as the all-email processing machine, purchasing RAM http://www.newegg.com/Product/Product.aspx?Item=N82E16820134244. For disks, we need to follow up on the mailing list, but http://www.newegg.com/Product/Product.aspx?Item=N82E16822148041 is being considered (only drawback: price). After the setup, we will re-evaluate our systems performance and see what's the next biggest bottleneck and eventually use the other spare server for it. * Virtualization - Do nothing about it for the moment. * Offsite backups (S3) - Mike will test backups himself and on his own budget, and report back to us within 10 days. * Paid staff - Postponed discussion until we're in a realistic position to do something about it. === 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 - Mike will do it. * Give JustinLeitgeb sudo access, and shell on all machines, since he already has on-site access - Mike will do it. * Formulate a policy for service plans on servers - Postpone for now. * Member freeze scripts? - Davor will do it by July 1st. * Accept David C. as admin? - Davor will verify David is still interested and add him to the admins@ alias. No actual privileges will be given at this point. |
1. IRC Meeting to be held Sunday, June 22, 2008
1.1. Agenda (with conclusions)
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 - We will set up IBM xSeries as the all-email processing machine, purchasing RAM http://www.newegg.com/Product/Product.aspx?Item=N82E16820134244. For disks, we need to follow up on the mailing list, but http://www.newegg.com/Product/Product.aspx?Item=N82E16822148041 is being considered (only drawback: price). After the setup, we will re-evaluate our systems performance and see what's the next biggest bottleneck and eventually use the other spare server for it.
- Virtualization - Do nothing about it for the moment.
- Offsite backups (S3) - Mike will test backups himself and on his own budget, and report back to us within 10 days.
- Paid staff - Postponed discussion until we're in a realistic position to do something about it.
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 - Mike will do it.
Give JustinLeitgeb sudo access, and shell on all machines, since he already has on-site access - Mike will do it.
- Formulate a policy for service plans on servers - Postpone for now.
- Member freeze scripts? - Davor will do it by July 1st.
- Accept David C. as admin? - Davor will verify David is still interested and add him to the admins@ alias. No actual privileges will be given at this point.