Page History
...
We suggest using the latest analysis release. You can find a list of most recent releases in the Release Notes. Note that not all of them would be packaged into the virtual images. Also note that not all platforms which we generally support at LCLS may be represented in the above mentioned collection of virtual images. And for well known reasons For instance, we can't redistribute images based on RHEL because this is a proprietary Linux distribution. Instead of that we replace RHEL systems with the corresponding versions of the CentOS distribution.
...
Both accounts have the same default password: LCLS2014 Please, change the one as soon as you start the image and log into the system! Protecting your system is solely your own responsibility. The passwords can be changed by logging as pcds and then switching to the superuser mode using one of the following commands:
| Code Block |
|---|
% sudio -i % su |
You should use the superuser account to manage your system (add/remove accounts, change passwords, configure the network, mount dists, etc.). The second account is used to install the LCLS releases. We do NOT recommend using that pcds account for your software development. The account has a special configuration for importing/updating releases. This document may later be extended to explain how one could upgrade to the latest analysis release using this account w/o re-installing the VM from scratch. We highly recommend
Testing and using the installed machine
Starting/stopping
By default, after you start the machine, the network connection will not be enable on the VM. You shall locate the following sign on the title bar on the top right corner of the machine's GUI:
that you created your own user accounts for your analysis activities. Just make sure you set up the analysis environment for that accounts as explained in the Analysis Setup document.
Which software is installed
Basically, we've tried to replicate the usual analysis environment, including the names of releases, a location of the release, the environment initialization commands (sit_setup), etc. And each VM image comes with at least one version of the full analysis release:
| Code Block |
|---|
% ls -al /reg/g/psdm/sw/releases/
total 12
drwxr-xr-x. 3 pcds pcds 4096 Aug 5 13:44 .
drwxrwxr-x. 5 pcds pcds 4096 Apr 4 18:04 ..
drwxr-xr-x. 101 pcds pcds 4096 Aug 5 13:38 ana-0.13.0
lrwxrwxrwx. 1 pcds pcds 10 Aug 5 13:40 ana-current -> ana-0.13.0 |
We also put a few tutorials for using the interactive psana (explained at psana - Python Script Tutorial) into the image:
| Code Block |
|---|
% ls -al /reg/g/psdm/tutorials/ total 28 drwxrwsr-x. 6 pcds pcds 4096 Apr 4 17:55 . drwxr-xr-x. 7 pcds pcds 4096 Apr 4 18:04 .. drwxrwsr-x. 3 pcds pcds 4096 Apr 4 17:55 common drwxrwsr-x. 3 pcds pcds 4096 Apr 4 17:55 cxi -rw-rw-r--. 1 pcds pcds 1554 Apr 4 17:55 README.1st drwxrwsr-x. 3 pcds pcds 4096 Apr 4 17:55 sxr drwxrwsr-x. 3 pcds pcds 4096 Apr 4 17:55 xcs |
There are some important
...
notes regarding what's not available on the VM:
- you won't be able to see your NFS home directory even if you will add your own account to the system using your sudo privilege
- all accounts found on the machine have nothing to do with LCLS accounts
...
- you won't be able to see any data directories (you can mount the ones using sshfs as explained later in this document)
Testing and using the installed machine
Starting/stopping
The virtual machine can be in either of the following states:
- powered off (same as hibernated or temporarily suspended and saved to disk)
- shut down (similarly to shutting down your host system; all sessions will be closed)
- running (in memory and using CPU)
- paused (still in memory but not using CPU)
The VirtualBox GUI has the corresponding controls to move the machine between the states. It's important to know that the machine state will be properly preserved between running and powered off states only if the machine is brought down using the GUI operations. This will allow VirtualBox to save the machine's state to disk. If you just kill the application then all modifications made to the VM system may be lost.
Mounting host machine's directories
VirtualBox allows to make select file systems (of your choice) of your host system available within the VM. This can be configured by selecting a desired machine from the list and clicking on the Setting button on the VirtualBox top-level menu. Then proceed to the "Shared Folders" sections where you can specify which file systems of your host machine you would like to mount on the VM. You may also control what kind of access level you would allow for the directories. Note that you will need to do so when the machine is shut down (not just powered off). The directories will be mounted when the machine will start up.
Mounting data directories of
Enabling/disabling network connection
By default, after you start the machine, the network connection will not be enable on the VM. You shall locate the following sign on the title bar on the top right corner of the machine's GUI:
If you see what you see above then the network is disabled. You will still be able to log on that machine through the GUI, but you won't be able to ssh out of the machine. Click on that sign and then click on the name of the network interface eth0 in order to enable the network.
ddd
Final notes
- The default configuration of the virtual machine won't allow external login into the machine (one can'e do 'ssh' into the system). However, it's possible to give you machine a unique IP address to allow the logins. Instructions can be found in the VirtualBox documentation. And make sure you change the default passwords of both root and pcds accounts in your virtual image.
- Please, read the documentation on VirtualBox
...
Overview
Content Tools