Extra HPC provision on Monsoon (NEXCS)

Hi All,
the details are here:
http://collab.metoffice.gov.uk/twiki/bin/view/Support/NEXCS

Project resource

Requests for NERC project resource should be made through the regular NERC process – in the early-usage stage (April 2017 – July 2017), access will be open.

http://www.nerc.ac.uk/research/sites/facilities/hpc/applying/

Machine access

NEXCS has the same 2-factor security model as does Monsoon2; a fob is required to access a bastion machine (the lander) with subsequent ssh to the xcs. NEXCS maintains accounting groups (projects) to which users are assigned after receipt of a security fob.

Current Monsoon2 users need only be added to an appropriate NEXCS group to use the resource.

Contact NCAS-CMS to request access to NEXCS and/or access to specific projects.
http://cms.ncas.ac.uk/wiki/CmsHelpdesk
====

UM Users Monsoon Switch-over has happened

We had plenty of warning.
The umsystems team have consolidated the “lander” user id of those of us with Met Office internal unix IDs. On the new Monsoon (xcs-c) those userids will have no data available unless it was transferred from the previous userid. That includes all data in the /projects/project/useridB working directories (DATADIR). The earlier userid is referred to as UseridB and the consolidated userid is UseridC.
I had to set up a blank id_rsa.pub key on XCM to add to the authorized_keys on XCSC to allow password-less transfer of data.

For the last week I have transferred data from XCM _to_ XCSC by pushing with:
scp -p A useridC@xcslc0:A

Now I find I should have also made a reverse key (oops) as I can only log into my earlier user id (Monsoon terminology useridB) with a password. Which I do not know.

This link is to instructions on the collaboration Twiki which requires a separate login (which hopefully you already know).
Monsoon Twiki