Monsoon is to be used for research purposes only. This includes either funded or unfunded research projects occurring in academic departments or research centers at NAU. Research purposes can include data analysis or exploration, computational method development and testing, and other tasks specifically related to research projects. Monsoon cannot be used to host analytic tools (e.g., web-based scientific computing software) for users outside of NAU. Monsoon is not for educational use. If you’re interested in academic computing resources, please contact ITS academic computing at 928-523-9294.
If Monsoon contributes to published work, the following acknowledgement should be included, if the publisher’s policy allows for it:
“[Some of the] Computational analyses were run on Northern Arizona University’s Monsoon computing cluster, funded by Arizona’s Technology and Research Initiative Fund.”
Connections to Monsoon are allowed only via SSH with your NAU credentials. This ensures that your authentication and sessions are encrypted.
File transfers can be done either via scp or samba. Both of these methods require use of your NAU username and password.
Do not share your login credentials. You are responsible for account actions; if it is determined that your account is being shared, it will be disabled.
If you witness suspicious activity, general security incident or abuse, please report it to: firstname.lastname@example.org.
Outages and maintenance will be communicated via the NAUHPC listserv, login node “message of the day”, and posted on the HPC website.
Minor scheduled maintenance does not require the whole cluster to be down and will be communicated with two days notice. This type of maintenance shouldn’t effect running/scheduled jobs.
- login node reboot
- minor network maintenance
- brief scheduler outage
- security patches
Major scheduled maintenance requires the whole cluster to be down and will be communicated with two weeks of notice.
- storage changes
- major network maintenance
Critical Maintenance is required to resolve critical issues and will be communicated with as much notice as possible.
- scheduler outage
- network degradation
- storage degradation
- serious security issues
Unexpected outages will be communicated within one hour of occurrence.