Servers: Difference between revisions
From HacDC Wiki
(Created page with "Category:Equipment =Basic= Simple project server, emphasis on availability and uptime. ==Policies== ===Permissions=== ====Root==== HacDC members with a demonstrable need...") |
No edit summary |
||
| Line 3: | Line 3: | ||
=Basic= | =Basic= | ||
Simple project server, emphasis on availability and uptime. | Simple project server, emphasis on availability and uptime. | ||
=Status= | |||
In progress. | |||
==Capabilities== | |||
* CPU - E2200 Dual-Core 2.2GHz | |||
* RAM - 1GB | |||
* HDD - 500GB | |||
==Redundancy (RAID)== | |||
None yet. Internal backups or RAID1 planned for OS/user storage. Access to a RAID0 (striped) array planned for high-speed semi-permanent storage. | |||
==Policies== | ==Policies== | ||
| Line 10: | Line 21: | ||
====Xen==== | ====Xen==== | ||
All HacDC members are welcome to xenshell access. Resources, including CPU, disk space, and external network ports, will be allocated on an as-needed first-come-first-serve basis. | All HacDC members are welcome to xenshell access. Resources, including CPU, disk space, and external network ports, will be allocated on an as-needed first-come-first-serve basis. | ||
==Notifications== | ===Notifications=== | ||
Internal server email will notify users, if feasible, on the following schedules, subject to change. | Internal server email will notify users, if feasible, on the following schedules, subject to change. | ||
* Three days before planned downtime. | * Three days before planned downtime. | ||
| Line 24: | Line 35: | ||
Machine is physically accessible to all keyholding HacDC members. Although HacDC members are generally responsible, privacy should not be expected. | Machine is physically accessible to all keyholding HacDC members. Although HacDC members are generally responsible, privacy should not be expected. | ||
===AcceptableUse=== | ===AcceptableUse=== | ||
====Sharing=== | ====Sharing=== | ||
Sharing of account resources is permitted, however, additional resources will be allocated according to individual member needs for specific purposes. As a reminder, compromised accounts | Sharing of account resources is permitted, however, additional resources will be allocated according to individual member needs for specific purposes. As a reminder, compromised accounts will be immediately removed as discovered. | ||
== | ==ChiefAdmin== | ||
mirage335 | |||
== | ==Credits== | ||
= | |||
Hunterkll - Donated core hardware. | Hunterkll - Donated core hardware. | ||
=General Policies= | =General Policies= | ||
Applicable to all use of HacDC server resources. | Applicable to all use of HacDC server resources. | ||
==Commercialization== | |||
* Resale of HacDC hosting services is subject to 501(c)3 provisions, and member acceptance. Within those restrictions, it is politely requested than any commercial users 'give back' fairly, upwards 5% of returns. | |||
==Prohibited== | ==Prohibited== | ||
| Line 53: | Line 55: | ||
* Contrary to US public policy. | * Contrary to US public policy. | ||
* Prohibited by HacDC internal policy. | * Prohibited by HacDC internal policy. | ||
* Jeopardizes HacDC or other HacDC members. Specifically, compromised accounts will be immediately disabled, and may be immediately deleted | * Jeopardizes HacDC or other HacDC members. Specifically, compromised accounts will be immediately disabled upon discovery, and may be immediately deleted. | ||
Revision as of 00:28, 21 October 2014
Basic
Simple project server, emphasis on availability and uptime.
Status
In progress.
Capabilities
- CPU - E2200 Dual-Core 2.2GHz
- RAM - 1GB
- HDD - 500GB
Redundancy (RAID)
None yet. Internal backups or RAID1 planned for OS/user storage. Access to a RAID0 (striped) array planned for high-speed semi-permanent storage.
Policies
Permissions
Root
HacDC members with a demonstrable need or willingness to manage non-root users may be given root access. Imperative that root users do not jeopardize uptime.
Xen
All HacDC members are welcome to xenshell access. Resources, including CPU, disk space, and external network ports, will be allocated on an as-needed first-come-first-serve basis.
Notifications
Internal server email will notify users, if feasible, on the following schedules, subject to change.
- Three days before planned downtime.
- One week before permanent downtime (obsolescence).
Removal
- Three months before removal of ex-member accounts. Exceptions on a case-by-case basis.
DataLoss
- Users should regularly backup critical data offiste.
- Onsite data storage is not guaranteed to be reliable.
- All server data may be deleted after obsolescence.
- Removed accounts may be deleted immediately and permanently upon deactivation.
Privacy
Machine is physically accessible to all keyholding HacDC members. Although HacDC members are generally responsible, privacy should not be expected.
AcceptableUse
=Sharing
Sharing of account resources is permitted, however, additional resources will be allocated according to individual member needs for specific purposes. As a reminder, compromised accounts will be immediately removed as discovered.
ChiefAdmin
mirage335
Credits
Hunterkll - Donated core hardware.
General Policies
Applicable to all use of HacDC server resources.
Commercialization
- Resale of HacDC hosting services is subject to 501(c)3 provisions, and member acceptance. Within those restrictions, it is politely requested than any commercial users 'give back' fairly, upwards 5% of returns.
Prohibited
At minimum, credentials and assets may be immediately deleted.
- Contrary to HacDC's 501(c)3 mission.
- Contrary to US public policy.
- Prohibited by HacDC internal policy.
- Jeopardizes HacDC or other HacDC members. Specifically, compromised accounts will be immediately disabled upon discovery, and may be immediately deleted.