Changes

Jump to: navigation, search

Historical Hera Config

435 bytes added, 21:46, 6 December 2006
Roadmap: reorganization
== Roadmap ==
=== Documentation === Documentation is extremely important in this project. Because many people have administrative access to the cluster machines soft copy documentation is necessary. Anyone who needs to know something about the cluster '''should''' be able to find it within the documentation. So far, there are three pages (so far) that must be kept up-to-date: [[Mozilla@Seneca Cluster Administration<u>Short Term</Forwarded Ports|Forwarded Ports]], [[Mozilla@Seneca Cluster Administration/List of Cluster Users|List of Cluster Users]], and [[Mozilla@Seneca Cluster Administration/Cluster Machine Tasks|Cluster Machine Tasks]]. * Any time that a new port is forwarded the [[Mozilla@Seneca Cluster Administration/Forwarded Ports|Forwarded Ports]] must be updated. This page is mainly used as a reference for users in case they forget what port to connect on for ssh, http, etc.* Any time a new user is given access to a cluster machine or a VM running on a cluster machine the [[Mozilla@Seneca Cluster Administration/List of Cluster Users|List of Cluster Users]] must be updated. This is just a quick reference page.* [[Mozilla@Seneca Cluster Administration/Cluster Machine Tasks|Cluster Machine Tasks]] is the most important of all three. It tracks exactly who has access to what machine or VM, what servers are running on them, and in the case of VMs their IP address. This is something that '''everyone''' needs to keep in mind when working on the cluster, not just the administrators. === Real World IPs u> ===
==== Real World IPs ====
This is a high priority item that we do not have direct control over. The people in charge are working to make this happen and hopefully it will happen soon.
* We need to find out if ACS needs to be informed when new port forwards are done.
==== Windows and Linux Generic VMs ====
As the cluster usage becomes higher and higher it is important to have easy and quick ways to bring up new machines. Generic Ubuntu images have been made already but the quality of them is currently unknown. Some testing should be done to make sure they are stable and complete. I would like to have this done before the start of the next Winter 2007 semester as there will probably be an influx of requests for VMs by new DPS909 students.
When the images are created the steps for creating a VM and the steps for bringing up a new VM should be documented. This is listed in the table in the [[#Details|project details]] section.
=== High Latency = VNC access to Linux machines ====VNC normally runs on a single port running a single X session. This makes it very tough to have multiple users connected at the Cluster same time -- or even multiple users using different accounts. This is an issue that we want solved. When someone connects on VNC it should be the same as sitting down at the desktop. GDM should allow a login to that users' desktop. When a second user connects they should see the same thing. This may have to be done through some XDMCP but it '''must''' but compatible with Windows and Linux VNC clients. ==== Look into Networking Management Systems ====As the cluster is used more and more it will become more difficult to manage by hand. I'd like a network management system such as Nagios to be used to help speed up maintenance. === <u>Medium Term</u> ===
The high latency problem on ==== Implement Network Management System ====Implement one of the systems described above.  === <u>Long Term</u> ===  === <u>Ongoing</u> === ==== Documentation ====Documentation is extremely important in this project. Because many people have administrative access to the cluster seems machines soft copy documentation is necessary. Anyone who needs to know something about the cluster '''should''' be solved but we need able to keep an eye on find itwithin the documentation. If this issues crop  So far, there are three pages (so far) that must be kept up again -to-date: [[Mozilla@Seneca Cluster Administration/Forwarded Ports|Forwarded Ports]], [[Mozilla@Seneca Cluster Administration/List of Cluster Users|List of Cluster Users]], and [[Mozilla@Seneca Cluster Administration/Cluster Machine Tasks|Cluster Machine Tasks]]. * Any time that a new port is forwarded the [[Mozilla@Seneca Cluster Administration/Forwarded Ports|Forwarded Ports]] must be updated. This page is mainly used as a reference for users in case they should forget what port to connect on for ssh, http, etc.* Any time a new user is given access to a cluster machine or a VM running on a cluster machine the [[Mozilla@Seneca Cluster Administration/List of Cluster Users|List of Cluster Users]] must be recognized updated. This is just a quick reference page.* [[Mozilla@Seneca Cluster Administration/Cluster Machine Tasks|Cluster Machine Tasks]] is the most important of all three. It tracks exactly who has access to what machine or VM, what servers are running on them, and reported to ACS very quicklyin the case of VMs their IP address.
=== VNC access This is something that '''everyone''' needs to Linux machines ===keep in mind when working on the cluster, not just the administrators.
VNC normally runs ==== High Latency on a single port running a single X session. This makes it very tough the Cluster ====The high latency problem on the cluster seems to be solved but we need to have multiple users connected at the same time -- or even multiple users using different accounts. This is keep an issue that we want solved. When someone connects eye on VNC it should be the same as sitting down at the desktop. GDM should allow a login to that users' desktop. When a second user connects If this issues crop up again they should see the same thing. This may have to be done through some XDMCP but it '''must''' but compatible with Windows recognized and Linux VNC clientsreported to ACS very quickly.
== Details ==
1
edit

Navigation menu