Using CA AppLogic › Grid User Guide › Accessing Grids

Accessing Grids

CA AppLogic supports the multiple types of access to the grid.

This section contains the following topics:

GUI Access

GUI Access

The GUI gives you access to the applications and appliances installed on the grid.

When you initially log in, a license agreement page displays, followed by the dashboard page.

The dashboard contains the following information and state about your grid:

Status: includes the account, system, and application status as well as additional information on the number of running applications and application resources.
Messages: displays service issues on the core grid.
Network Resources: display the name, VLAN id, application IP range, netmask, gateway, and name servers.

Follow these steps:

Point your browser to the grid dashboard
http://[gridname].3tera.net.

The gridname is typically the company name.

The Login page displays
Enter your user name and password, then click OK.
The dashboard displays.

Operator Access

Grid administrators are provided access through ssh/bash.

Follow these steps:

Log in to the grid shell.
```
ssh root@controllerhost 
```
The Linux Bash Shell displays.
To access to the Grid Shell, enter 3t at the command line.

Regular User Access

Grid users access the application grid through the GUI.

To access the grid:

Log into the GUI.
The Dashboard page displays.
Select the Applications tab.
Select or create an application.
The grid displays.

Volume Access

Volumes of running applications are accessible using scp and sftp or accessing Manage Volumes in the Infrastructure Editor.

Using SCP and SFTP

An authorized ssh key must be set up for the user to use the scp or sftp access to volumes. When using scp or sftp access, configure the client program to use the private key that corresponds to the key set up with the user create or user set command and specify root as the username to scp or sftp. For example, use root@controllerhost as the target name.

The following commands are supported:

scp

-d localdir controllerhost:/_impex/

copy localdir to the controller's import/export area. Same with swapped 1st and 2nd args to copy from the controller to a local file or directory. This is normally used to copy data for the 'app import', 'class import', 'app export' and 'class export' commands

localfile controllerhost:/app/appname/compname/filepath

copy localfile to the filespace of a running appliance. Same with swapped 1st and 2nd args to copy from an appliance to a local file or directory.

sftp

[options] controllerhost

open an interactive or batch sftp session. The session has access to all volumes to which access is requested beforehand, via the 'vol mount' command sent to the 3t shell. The client sees a filesystem that contains only the 'mounted' volumes as '/appname/volname/ - the same as for the 'scp' command (except no vol root). All SFTP commands are allowed, including chown, chmod, etc., for manipulating file permissions and ownership on the volumes.

nautilus

sftp://controllerhost/

use this or any similar GUI-based SFTP client to access volumes (pre-mounted with a shell command or using the Web GUI). The semantics and the level of access are exactly the same as for the command-line SFTP (barring any functionality restrictions imposed by the GUI app).

Configure User Access

For a user to access the scp and sftp commands, you must:

Configure user to access public ssh key
To configure user access, you must create or update the using AppLogic commands:
```
 user create <name> pwd=- -sshkey="public key>" or user set -sshkey="<public key>"
```
The public key must be added to the infrastructure using AppLogic commands.
Verify access level to the grid
To access the grid, the user logs in to the grid as user 'root' (root@controllerhost) with their private key. The 3t shell prompt automatically displays, instead of the grid controller prompt. Users must access the grid with the username root combined with their private key. For additional information on authorizing a ssh key, refer to the User Management Commands.
Verify access level to the application
To access the application, the user must have either app_operator, app_developer or grid_administrator access level rights on the grid and full access level rights to the target application.

Using the Infrastructure Editor

You can access volumes for specific applications in the Manage Volumes dialog in the Infrastructure Editor.

Follow these steps:

Access the application.
In the Infrastructure Editor, right click the grid and select Manage Volumes.
The Manage Volumes dialog displays.

Appliance Access

You can access running application appliances using ssh and scp.

Follow these steps:

Access the Grid Shell and execute one of the following commands:
```
ssh appname:componentname 
```
or
```
login appname:componentname 
```
Root access to the appliance is provided
Once in the appliance, execute scp to transfer the required files to the appliance.

Scripting Access

You can access the grid using the command line.

For addition information on scripting shell commands, refer to the Command Line Shell Reference Guide.

Note: If you are using GNU bash, Client-side Macros are an alternative method for accessing the shell commands directly from your local command prompt.