Globus Connect Server Endpoint Migrate53
Synopsis
globus-connect-server endpoint setup -c CLIENT-ID --owner OWNER DISPLAY_NAME --ip-adress IP_ADDRESS [OPTIONS]…
Description
The globus-connect-server endpoint migrate53 command provides a command-line interface to migrate an existing Globus Connect Server v5.3 endpoint for use with Globus Connect Server v5.4. This updates the existing endpoint, storage gateway, user credentials, and collection objects for use with v5.4.
This command performs many of the same operations as globus-connect-server endpoint setup and globus-connect-server node setup to set up the state of the endpoint and deploy it on the current node.
Upon completion, it will create a file called deployment-key.json (by default). This file is important. It must be kept in order to be able to deploy the Globus services for this endpoint on a Data Transfer Node. It must also be kept confidential, as it can be used to unlock the data key used to encrypt your endpoint’s configuration.
Options
- -h, --help
-
Show a help message and exit.
- --version
-
Show the version and exit.
- -c, --client-id CLIENT_ID (required)
-
Auth Client ID for this Globus Connect Server Endpoint. See https://auth.globus.org/v2/web/developers to create this ID.
- -o, --owner USERNAME (required)
-
Identity username of the owner of this endpoint (e.g. janedoe@example.edu). This must be a valid identity username in Globus Auth. The user who owns identity will be granted the
owner
role on this endpoint, which will allow them to create and view storage gateway configuration for this endpoint. - --ip-address IP_ADDRESS
-
Publicly accessible IP address of this endpoint.
- -d, --deployment-key PATH
-
Path for deployment key configuration. If this file exists, it will be loaded and used as the source for the deployment key (for example, if you had previously run this command but interrupted it). If it doesn’t exist, then a new deployment key is created and stored in this file. By default the value
deployment-key.json
is used.
Example
This invocation migrates the v5.3 endpoint on the current node using the
client_id stored in the $CLIENT_ID
environment variable, setting
admin@example.org
as the endpoint owner. If you are planning on setting up
your own endpoint, use your own Globus username as the owner.
% sudo globus-connect-server endpoint migrate53 \ -c $CLIENT_ID \ -o admin@example.org