I apologize for the wordy nature of this notice, and the dry tone. I try to dress these things up and make them a more entertaining read, but there’s a lot of information to convey and I don’t want any of it to get lost. Hang out until the end for a fun joke to make it worthwhile.
This information is applicable to anyone with an MCS account (aka a CELS account), largely based around the MCS/CELS linux environment (which we’ve started lovingly referring to as the legacy environment), as well as LCRC users, since we’re unifying these environments to enable easier integration across the entire CELS computing infrastructure. This is the first merger of this type we’re doing, and it’s pretty exciting, because it opens a lot of possibilities.
So, let’s dive in. We’re in the last stages of rolling out the new CELS General Compute Environment (GCE), which will eventually replace the legacy environment. We’re waiting on the account management software (more on that later), but we can still get a head start on things. One of the requirements for the new environment is that it uses Argonne accounts instead of MCS or CELS accounts. As such, if you don’t have an Argonne account, you’re going to need one.
The process and policy for getting an account for non-employees is fundamentally the same as it always was, but the interface looks a bit different. But at the high level it remains:
- Visit the account application link and agree to the Computer User Policy
- Specify who your Argonne sponsor is (must be an Argonne employee), and specify why you need the account
- Fill out the account identity info
- Sponsor will get notified and approve
- Account created
- Account comes up for renewal every year
There are extra steps in there for foreign nationals, but that’s also the same process we’re currently following.
In order to use GCE, you must have an Argonne account. In order to use LCRC resources, an Argonne account will be required by January 1, 2020.
In December of 2019 we will be introducing our new account management system (Userbase 3), which will manage both GCE and LCRC access. This system is how you’ll request access to the various projects, resources, systems, groups, and other entities in both GCE and LCRC. In order to login, you will use your Argonne account. We’ll send more details on this when the rollout is ready, but it would be a good idea to get an Argonne account now if you don’t already have one.
I’m going to split out the details on the new process for Argonne employees and non-employees (collaborators) below. Feel free to skip to the relevant section, but it won’t hurt to see both sides, so you’ll understand the process. This process is documented at [link goes here].
You’re getting this mail, so you already have an account with us. This means you’ve already gone through this process once already, though the aesthetics are a little different.
I want to point out we can’t simply import the data and carry everyone over. There’s a lot of stale data, and the backend systems are entirely different, even though they follow a similar process.
The link to apply for an Argonne Collaborator account is at and is accessible from anywhere. You will need to use the official Argonne e-mail address of your Argonne sponsor. If you don’t know it, you can contact your sponsor directly and ask. If there’s some reason that doesn’t work, let us know at firstname.lastname@example.org and we’ll figure it out with you.
These Argonne Collaborator accounts are annual and can be renewed by the sponsor each year. More details on the account life cycle will be in the documentation linked above.
For Argonne employees:
Argonne employees and affiliates should already have an account. If you’ve got an active badge, you likely have an account, and are entitled to one if you don’t already have one. If you’re unsure as to whether or not you have an Argonne account, you can check at . It’s the same account you use to login to your e-mail account and other Argonne apps.
When you join GCE, you will login using your Argonne credentials. When you login to LCRC after the new year, the same applies. Remote access rules regarding SSH keys and One Time Password remain unaffected. Account management will be handled through Userbase 3 (link to be announced when it’s live), and will use Argonne logins.
You can invite collaborators via the Cyber Gate Pass app. You will also approve, reject, and renew accounts in this app. The rules for sponsorship remain largely unchanged. You can find details on the Cyber Gate Pass application, rules, and processes here: (internal access only).
The last bit:
We will send updates on the process of this rollout as it progresses. We will very soon be seeking out early friendly users to dive into the environment and tell us what’s missing. If you’re in EVS, you’re already in there, so good for you! We’re still writing up the documentation on the default policies and such for this environment, but it’ll be all announced and available on as soon as it’s completed.
Okay, the pithy joke. What do you call a pig with three eyes?
Thanks, I’ll be here all week, tip your waitstaff.