...
The AAT/PPI has 3 parallel 'environments'. Each of these environments consists of a set of software which is deployed to dedicated servers in both NM and CV, and a set of configuration parameters (also called CAPO Profiles) for each deployment location for that environment. The 3 environments (and their associated profiles) are:
- Production (nmprod, vaproddsoc-prod, naasc-prod)
- The current release of the AAT/PPI
- No redeployments without an announcement to the archive_issues list
- Web interface: archive-new.nrao.edu
- Test (dsoc-test, naasc-test)
- Used for integration testing & validation of changes (features or bug fixes)
- Also the home for pre-release candidates for release to production
- Typically stable on day+ timescales
- Major redeployments are announced on the archive_test list
- Web interface: archive-test.nrao.edu
- Development (nmtest, vatestdsoc-dev, naasc-dev)
- Developers' basic verification testing ground
- Often subject to sudden redeployments of subsystems
- Can have components from multiple branches of development deployed at one time
- Web interface: webtest.aoc.nrao.edu/portal/#/
- (Yes, I know, that name is unfortunate)
...
As a convenience feature, these two accounts have had the activate_profile & deactivate_profile commands added to their Bash configuration. When given the name of a CAPO profile (nmproddsoc-prod, dsoc-test, etc) activate_profile sets up a few environment variables and sets up your shell so that the corresponding set of utilities (and the correct supporting libraries) in your $PATH, so that they're easy to use.
...
When running just a few commands, it might be easier to simply directly call the appropriate utility without resorting to the relevant 'pipe' account. In that case, pay particular attention to the directory from which you run the command (either by changing directory there or typing out the path). The differences between /users/vlapipe/workflows/nmproddsoc-prod/bin/myCommand and /users/vlapipe/workflows/nmtestdsoc-test/bin/myCommand can (potentially) be not just the details of the software itself, but also any differences in the profile's parameters.
...
These properties define information like server names, where to process data, and what version of CASA to use as a default. They are editable by the vlapipe account, so those values which are of interest can be readily modified by the Data Analysts. It is possible (even likely) that some of those variable names may change as the system evolves. It is important to remember that the copy of the files in NM take precedence and will periodically overwrite their counterparts in CV. If you don't have access to the vlapipe account, contact one of your fellow DAs or the SSA team.
The Renaming Of The Profiles
With the addition of the Test environment, it was decided that the names of the CAPO profiles required revision. In addition to needing to distinguish among 3 environments instead of 2, the location portion of the names was changed to the site's label (dsoc/naasc), rather than the state's abbreviation. Thus we have the following mapping:
nmtest → dsoc-dev
vatest → naasc-dev
dsoc-test: No Change
naasc-test: No Change
nmprod → dsoc-prod
vaprod → naasc-prod
There are already symlinks in place, so you can begin using the new names to ease this transition. There is not currently a timeline for the official retirement of the old names, but it will likely coincide with an official release of the AAT/PPI.
What is that source ~pipeaccount/workflows/myprofile/bin/activate command doing?
...