New MOOSE and MASS system

This article contains information about the new Azure MOOSE and MASS system (AZ-MOOSE and AZ-MASS). These are not currently the operational versions of MOOSE and MASS, so please continue to refer to the other MASS pages for current workflows.

MASS refers to the tape archive and MOOSE is the interface used to interact with MASS, allowing you to do GETs, SELECTs and other commands. The current MASS system is aging and a new version of MASS, and a new version of MOOSE, is being developed.

We expect the new AZ-MOOSE commands to work in the same way as current MOOSE commands. However, there will be some differences with the new system, such as new commands to log into AZ-MOOSE.

What do I need to do?  

1. Make your existing MOOSE commands (GETs, SELECTs etc.) as ’nice’ to current MASS as you can. For example, split single large GETs into several smaller GETs.
2. Review your workflows and jobs for those that use moo commands so that you know which ones to target for testing when the AZ-MOOSE client becomes available.
3. Make note of the timeline below to assist with planning of work.
4. Request an account if you wish to explore the new system before it goes live.

This page will be updated with additional information and advice as we receive it.

Timeline and Switchover  

If you would like to be involved in the User Acceptance Testing (UAT) and have not already been contacted about it, please email: monsoon@metoffice.gov.uk

To safely switchover to the new MASS system we need to pause all MASS access and invoke a MASS outage to complete the metadata migration. The minimum outage for all users is expected to be 48 hours, but most users should plan for impacts spanning a longer timeframe of up to 5 working days. The switchover date will be announced as soon possible after User Acceptance Testing to give all users as much notice as possible.

To de-risk the switchover, users may be asked to reduce MASS usage for a short period ahead of the outage. As we get closer to the switchover date, further details about this will be communicated.

Changes to your MASS Account  

AZ-MASS User Account Changes

Note that although what you can access in AZ-MASS will remain the same regardless of what platform you are signing in from (Monsoon/JASMIN/other) the AZ-MOOSE commands you can perform will differ. JASMIN remains a read-only platform (GET/SELECT etc.).

Changes to data access  

There will be some changes to what data access you have for a period of time after service commencement.

If you access datasets that are not associated with any of your projects but are covered by a project access rule, you may lose access to it. We are taking action to prevent this from happening, but we do expect edge cases to arise. Where this happens, please contact: monsoon@metoffice.gov.uk

Removed and Altered MOOSE Commands  

When the Met Office switches over to Azure MASS, some uncommon commands and options still in infrequent use today will no longer be available and for a few their behaviour has changed. The following aims to provide a definitive list of those commands and options as a reference for users.

Removed and Altered MOOSE Commands

Limitations to AZ-MOOSE and AZ-MASS  

Requesting an account  

If you have a MONSooN3 AZ-MASS account, you do not need to request an AZ-MASS account for JASMIN.

1. You must be an existing user of MASS to request an AZ-MASS account (see How to apply for MASS access)
2. Email monsoon@metoffice.gov.uk from the email address you registered your existing MASS account with.

Resources and Further Reading  

• Getting ready for go live 
• Training and resource hub 

If you have any questions, please email: monsoon@metoffice.gov.uk