Previous Topic: Application Migration WizardNext Topic: Importing an Application from a Remote Grid


Setting Up Trust Between the Grids

Before the Application Import Wizard can be run, "trust between the two grids" must be set up.

To setup trust between the two grids to execute the 'Migrate From' operation (migrate application from a remote grid to the local grid):

  1. From the grid shell on the local grid, execute grid info -v and copy the value of the Grid Public SSH Key ensuring that the key is contained on a single line without any whitespace or newlines.
  2. Log into the remote grid and create a new user specifying the public SSH key retrieved in the previous step as the sshkey parameter. For Example:
    user create remotegrid@ca.net pwd=somepwd sshkey=sshkey
    
  3. From within the grid shell on the remote grid, provide the just-created user with 'app_developer' access on the grid ACL which will allow this user to migrate the application. For example:
    grid modify_acl local:user:remotegrid@ca.net=app_developer
    
  4. From within the grid shell on the remote grid, provide the just-created user with 'configure' access on the application ACL of the application(s) that is/are to be migrated. For example:
    app modify_acl myapp local:user:remotegrid@ca.net=configure
    
  5. From within the Application list tab, select the 'Migrate from' button from the toolbar or the right-click menu.
  6. Optional: Remove the user that was created on the remote grid if no more applications need to be migrated.

To setup trust between the two grids to execute the 'Migrate To' operation (migrate an application from the local grid to a remote grid)

  1. From the grid shell on the local grid, execute grid info -v and copy the value of the Grid Public SSH Key ensuring that the key is contained on a single line without any whitespace or newlines.
  2. Log into the remote grid and create a new user specifying the public SSH key retrieved in the previous step as the sshkey parameter. For Example:
    user create remotegrid@ca.net pwd=somepwd sshkey="sshkey"
    
  3. From within the grid shell on the remote grid, provide the just-created user with 'app_developer' access on the grid ACL which will allow this user to migrate the application. For example:
    grid modify_acl local:user:remotegrid@ca.net=app_developer
    
  4. From the grid shell on the remote grid, execute grid info -v and copy the value of the Grid Public SSH Key ensuring that the key is contained on a single line without any whitespace or newlines.
  5. Log into the local grid and create a new user specifying the public SSH key retrieved in the previous step as the sshkey parameter. For Example:
    user create localgrid@ca.net pwd=somepwd sshkey="sshkey"
    
  6. From the grid shell on the local grid, provide the just-created user with 'app_developer' access on the grid ACL which will allow this user to migrate the application. For example:
    grid modify_acl local:user:localgrid@ca.net=app_developer
    
  7. From the grid shell on the local grid, provide the just-created user with 'configure' access on the ACL of the application(s) that is/are to be migrated to the remote grid. For example:
    app modify_acl myapp local:user:localgrid@ca.net=configure
    
  8. From within the Application list tab on the local grid, select the 'Migrate to' button from the toolbar or the right-click menu.
  9. Optional: Remove the users that were created on the local and remote grids if no more applications need to be migrated.