Difference between revisions of "VM Lab"
| Line 9: | Line 9: | ||
Most Spark systems are administered by the sparkadmin user, but sometimes the root user is still used. If you need access, ping the [[Electronics Leads]] | Most Spark systems are administered by the sparkadmin user, but sometimes the root user is still used. If you need access, ping the [[Electronics Leads]] | ||
| + | === Available Space === | ||
| + | Depending on project lifecycles, we may have rack space or virtual compute space available for member use. Contact the [[Electronics Leads]] for more information. | ||
== See Also == | == See Also == | ||
| Line 14: | Line 16: | ||
* [[Minecraft]] | * [[Minecraft]] | ||
* [[Autodrop3D Printing Guidelines]] | * [[Autodrop3D Printing Guidelines]] | ||
| + | * [[Mastodon]] | ||
| + | * [[pfsense]] | ||
Revision as of 16:12, 31 October 2020
VM Lab
The Spark Nerds maintain a hardware lab for virtual machines, with limited capacity for member projects/hosting. If you have questions, reach out to the Electronics Leads.
The Spark Proxmox server can be accessed here from within the Spark network by those with credentials.
We have a Rancher instance running here accessible from within the Spark network. ping the Electronics Leads if you want access. Note that our cluster is SMALL and only suitable for testing and exploration of Kubernetes.
Most Spark systems are administered by the sparkadmin user, but sometimes the root user is still used. If you need access, ping the Electronics Leads
Available Space
Depending on project lifecycles, we may have rack space or virtual compute space available for member use. Contact the Electronics Leads for more information.