Servers: Difference between revisions
From HacDC Wiki
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
=Hardware= | =Hardware= | ||
==[[ | ==[[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''' | ||
| Line 14: | Line 14: | ||
==Shell Servers == | ==Shell Servers == | ||
* [[ | * [[Shimmer]] | ||
* [[Tortoise]] | * [[Tortoise]] | ||
| Line 21: | Line 21: | ||
==Package Build Server== | ==Package Build Server== | ||
* [[ | * [[Shimmer]] - Gentoo/Funtoo | ||
==Package Management Caching Proxy== | ==Package Management Caching Proxy== | ||
| Line 30: | Line 30: | ||
==VM Server== | ==VM Server== | ||
* [[ | * [[Shimmer]] | ||
* Xen - WIP | * Xen - WIP | ||
Revision as of 22:51, 21 November 2014
Hardware
Shimmer
Shell and VPS server, emphasis on uptime. Dual-Core, 4GB RAM, 500GB HDD ONLINE
Albert
Network Attached Storage and Shell server. Dual-Socket Dual-Core, 4GB ECC RAM, >1TB HDD Capacity, RAID
Available Resources
WIP = Work In Progress
Shell Servers
Network Attached Storage
Package Build Server
- Shimmer - Gentoo/Funtoo
Package Management Caching Proxy
Mirror Server
VM Server
- Shimmer
- Xen - WIP
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. Running OwnCloud on a Raspberry Pi would probably be fine, an ancient mainframe might be less welcome.
Acceptable Use Policies
Applicable to all use of HacDC communal computing resources.
Commercialization
- Resale of HacDC services is subject to approval at a duely held member meeting
- Insidental use of HacDC services for commercial purposes is accceptable when it complies with all relavent 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 neighboring tenants.
- Uncoordinated excess resource usage adversely effecting other users.
- Failure to comply with password policies.
The following are grounds for immediate, complete, and permanent loss of all access:
- Actions which jepordize the resources or safety of the staff, members, guests, tennants of HacDC or St. Stephen's Church.
- Failure to comply with previous sanctions.