Difference between revisions of "Virtual Machine Guidelines"

From CSLabsWiki
m (Usage Guidelines: Fixed my stupid formatting error)
(Add suggestion for VM backup process)
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
Before requesting a Virtual Machine for personal or open use, please review this page to ensure that your service is something that belongs on our servers. This is not a strict set of rules, and nor is this meant to deter the creation of new VMs.
 
Before requesting a Virtual Machine for personal or open use, please review this page to ensure that your service is something that belongs on our servers. This is not a strict set of rules, and nor is this meant to deter the creation of new VMs.
 
==Virtual Machine Hosts==
 
====Europa====
 
Europa is a server that is reserved for the more critical systems in the labs. This includes, but not limited to, [[dns1]], [[web1]], etc. Most services do not need to be on this machine permanently.
 
====Titan (Xen2)====
 
Titan's purpose is currently unknown, as it is slated for a rebuild in the near future (as of Nov. 2013). It currently hosts some of the older systems in the labs. It is likely to stay a Xen system, rather than KVM.
 
====Juno====
 
Juno, although also slated for a rebuild, is for smaller systems, or student projects. This is mostly the server new VMs will be created on.
 
   
 
==Usage Guidelines==
 
==Usage Guidelines==
* Services must be for non-commercial use. (Note: This includes services like bitcoin mining)
+
* Services must not be for profit. (Note: This includes services like bitcoin mining)
 
* Services must be legal (by US, NY laws) in operation and storage.
 
* Services must be legal (by US, NY laws) in operation and storage.
 
* Services must considerate of the VM Host's resources, as well as other services in the lab. (Subject to VM Host's Maintainer's discretion)
 
* Services must considerate of the VM Host's resources, as well as other services in the lab. (Subject to VM Host's Maintainer's discretion)
 
* Services must be created with good intent. (i.e. non-malicious)
 
* Services must be created with good intent. (i.e. non-malicious)
  +
* Services must be well documented. Undocumented services will be stopped until adequate documentation is provided on the wiki.
  +
  +
==Student Projects==
  +
Virtual Machines created for student projects are subject to different restrictions
  +
* The student requesting the VM must attend at least one COSI forum meeting to discuss the project
  +
* The student is responsible for installing any software need
  +
* A DNS entry will not be created
  +
* The VM will be removed a week after the start of the following semester, unless a valid reason for continued operation is presented
  +
  +
==External Services==
  +
Services may be hosted in the labs by external entities provided that the machine adheres to the above guidelines, as well as the following:
  +
* The service owner/maintainer must check in at least annually to ensure the service is not inactive.
  +
* The service must have exemplary documentation regarding what the service is doing, and includes current and accurate contact information
  +
* Service maintainers must respond to queries about the service within seven days
  +
* Service up time is not guaranteed
   
 
==Other Notes==
 
==Other Notes==
Line 19: Line 26:
 
* COSI is not responsible for any loss of data.
 
* COSI is not responsible for any loss of data.
 
* Uptime is not guaranteed. If the downtime is excessive, contact the VM Host Maintainer.
 
* Uptime is not guaranteed. If the downtime is excessive, contact the VM Host Maintainer.
  +
  +
==Suggestions==
  +
* For future VM Hosts, consider creating a separate backup staging partition to ensure that the host will not run out of storage for backups when new VMs are created.

Latest revision as of 21:01, 21 January 2016

Before requesting a Virtual Machine for personal or open use, please review this page to ensure that your service is something that belongs on our servers. This is not a strict set of rules, and nor is this meant to deter the creation of new VMs.

Usage Guidelines

  • Services must not be for profit. (Note: This includes services like bitcoin mining)
  • Services must be legal (by US, NY laws) in operation and storage.
  • Services must considerate of the VM Host's resources, as well as other services in the lab. (Subject to VM Host's Maintainer's discretion)
  • Services must be created with good intent. (i.e. non-malicious)
  • Services must be well documented. Undocumented services will be stopped until adequate documentation is provided on the wiki.

Student Projects

Virtual Machines created for student projects are subject to different restrictions

  • The student requesting the VM must attend at least one COSI forum meeting to discuss the project
  • The student is responsible for installing any software need
  • A DNS entry will not be created
  • The VM will be removed a week after the start of the following semester, unless a valid reason for continued operation is presented

External Services

Services may be hosted in the labs by external entities provided that the machine adheres to the above guidelines, as well as the following:

  • The service owner/maintainer must check in at least annually to ensure the service is not inactive.
  • The service must have exemplary documentation regarding what the service is doing, and includes current and accurate contact information
  • Service maintainers must respond to queries about the service within seven days
  • Service up time is not guaranteed

Other Notes

  • Services are to be backed up by the Service Maintainer (i.e. YOU).
  • COSI is not responsible for any loss of data.
  • Uptime is not guaranteed. If the downtime is excessive, contact the VM Host Maintainer.

Suggestions

  • For future VM Hosts, consider creating a separate backup staging partition to ensure that the host will not run out of storage for backups when new VMs are created.