Servers: Difference between revisions
From HacDC Wiki
No edit summary |
|||
Line 4: | Line 4: | ||
=Hardware= | =Hardware= | ||
==[[Shimmer]]== | ==[[Shimmer]]== | ||
Shell and VPS server, emphasis on uptime. Dual-Core, 4GB RAM, 500GB HDD | Shell and VPS server, emphasis on uptime. Dual-Core, 4GB RAM, 500GB HDD. | ||
'''ONLINE''' | '''ONLINE''' | ||
==[[ | ==[[Starlight]]== | ||
Shell and VPS server, emphasis on uptime, durability, and performance. Octo-Core dual Xeon X5355, 48GB ECC RAM, 20TB RAID6, 5TB RAID0, 900MB/s 1000 IOPS peak estimated throughput. | |||
''ONLINE'' | |||
=Available Resources= | =Available Resources= | ||
Line 15: | Line 16: | ||
==Shell Servers == | ==Shell Servers == | ||
* [[Shimmer]] | * [[Shimmer]] | ||
* [[ | * [[Starlight]] | ||
==Network Attached Storage== | ==Network Attached Storage== | ||
==VM Server== | ==VM Server== | ||
* [[Shimmer]] | * [[Shimmer]] | ||
* | * [[Starlight]] | ||
=Collocation= | =Collocation= | ||
Line 40: | Line 31: | ||
==Commercialization== | ==Commercialization== | ||
* Resale of HacDC services is subject to approval at a | * Resale of HacDC services is subject to approval at a duly held member meeting | ||
* | * Incidental use of HacDC services for commercial purposes is acceptable when it complies with all relevant HacDC policies. | ||
* It is requested than any commercial users 'give back' fairly (upwards 5% of returns). | * It is requested than any commercial users 'give back' fairly (upwards 5% of returns). | ||
Line 51: | Line 42: | ||
* Actions prohibited by HacDC policy. | * Actions prohibited by HacDC policy. | ||
* Any form of spam, or activity which causes spam filters to reject mail from *.hacdc.org or any other HacDC related domain. | * Any form of spam, or activity which causes spam filters to reject mail from *.hacdc.org or any other HacDC related domain. | ||
* Heavy network use, reducing QoS for | * Heavy network use, reducing QoS for neighbouring tenants. | ||
* Uncoordinated excess resource usage adversely affecting other users. | * Uncoordinated excess resource usage adversely affecting other users. | ||
* Failure to comply with password policies. | * Failure to comply with password policies. | ||
The following are grounds for immediate, complete, and permanent loss of all access: | The following are grounds for immediate, complete, and permanent loss of all access: | ||
* Actions which | * Actions which jeopardize the resources or safety of the staff, members, guests, tenants of HacDC or St. Stephen's Church. | ||
* Failure to comply with previous sanctions. | * Failure to comply with previous sanctions. | ||
* Compromised accounts. | * Compromised accounts. |
Revision as of 16:52, 15 May 2016
Hardware
Shimmer
Shell and VPS server, emphasis on uptime. Dual-Core, 4GB RAM, 500GB HDD. ONLINE
Starlight
Shell and VPS server, emphasis on uptime, durability, and performance. Octo-Core dual Xeon X5355, 48GB ECC RAM, 20TB RAID6, 5TB RAID0, 900MB/s 1000 IOPS peak estimated throughput. ONLINE
Available Resources
WIP = Work In Progress
Shell Servers
Network Attached Storage
VM Server
Collocation
Besides HacDC servers maintained semi-officially, members can host their own servers, within reason and assistance from the HacDC admin team. Mostly, we ask that collocated servers be efficient, on an as-needed basis, and out of the way.
Acceptable Use Policies
Applicable to all use of HacDC communal computing resources.
Commercialization
- Resale of HacDC services is subject to approval at a duly held member meeting
- Incidental use of HacDC services for commercial purposes is acceptable when it complies with all relevant HacDC policies.
- It is requested than any commercial users 'give back' fairly (upwards 5% of returns).
Prohibited Activities
Server/network/web administrators may take corrective action to address violations of policy. The following actions are never acceptable.
- Actions contrary to HacDC's 501(c)3 mission.
- Violations of applicable laws (international, federal, state, or local).
- Actions prohibited by HacDC policy.
- Any form of spam, or activity which causes spam filters to reject mail from *.hacdc.org or any other HacDC related domain.
- Heavy network use, reducing QoS for neighbouring tenants.
- Uncoordinated excess resource usage adversely affecting other users.
- Failure to comply with password policies.
The following are grounds for immediate, complete, and permanent loss of all access:
- Actions which jeopardize the resources or safety of the staff, members, guests, tenants of HacDC or St. Stephen's Church.
- Failure to comply with previous sanctions.
- Compromised accounts.