GLOBUS ENDPOINT CREATE

NAME

globus endpoint create - Create a new endpoint

SYNOPSIS

globus endpoint create [OPTIONS] DISPLAY_NAME

DESCRIPTION

Create a new endpoint.

Requires a display name and exactly one of --personal, --server, or --shared to make a Globus Connect Personal, Globus Connect Server, or Shared endpoint respectively.

Note that --personal does not perform local setup steps. When this command is run with the --personal flag, it returns a setup key which can be passed to Globus Connect Personal during setup.

OPTIONS

--preferred-parallelism INTEGER

Set the endpoint’s preferred parallelism; requires --network-use=custom (Managed endpoints only) (Globus Connect Server only)

--max-parallelism INTEGER

Set the endpoint’s max parallelism; requires --network-use=custom (Managed endpoints only) (Globus Connect Server only)

--preferred-concurrency INTEGER

Set the endpoint’s preferred concurrency; requires --network-use=custom (Managed endpoints only) (Globus Connect Server only)

--max-concurrency INTEGER

Set the endpoint’s max concurrency; requires --network-use=custom (Managed endpoints only) (Globus Connect Server only)

--network-use [normal|minimal|aggressive|custom]

Set the endpoint’s network use level. If using custom, the endpoint’s max and preferred concurrency and parallelism must be set (Managed endpoints only) (Globus Connect Server only)

--subscription-id UUID

Set the endpoint as a managed endpoint with the given subscription ID. Mutually exclusive with --no-managed

--no-managed

Unset the endpoint as a managed endpoint. Does not require the user to be a subscription manager. Mutually exclusive with --subscription-id

--managed

Set the endpoint as a managed endpoint. Requires the user to be a subscription manager. If the user has multiple subscription IDs, --subscription-id must be used instead

--location LATITUDE,LONGITUDE

Manually set the endpoint’s latitude and longitude (Globus Connect Server only)

--oauth-server TEXT

Set the OAuth Server URI (Globus Connect Server only)

--myproxy-server TEXT

Set the MyProxy Server URI (Globus Connect Server only)

--myproxy-dn TEXT

Set the MyProxy Server DN (Globus Connect Server only)

--public / --private

Set the endpoint to be public or private (Globus Connect Server only)

--disable-verify / --no-disable-verify

(Un)Set the endpoint to ignore checksum verification

--force-encryption / --no-force-encryption

(Un)Force the endpoint to encrypt transfers

--no-default-directory

Unset any default directory on the endpoint

--default-directory TEXT

Set the default directory

--keywords TEXT

Comma separated list of keywords to help searches for the endpoint

--department TEXT

Department which operates the endpoint

--organization TEXT

Organization for the endpoint

--contact-email TEXT

Contact Email for the endpoint

--contact-info TEXT

Contact Info for the endpoint

--info-link TEXT

Link for Info about the endpoint

--description TEXT

Description for the endpoint

--personal

Create a Globus Connect Personal endpoint. Mutually exclusive with --server and --shared.

--server

Create a Globus Connect Server endpoint. Mutually exclusive with --personal and --shared.

--shared ENDPOINT_ID:PATH

Create a shared endpoint hosted on the given endpoint and path. Mutually exclusive with --personal and --server.

-v, --verbose

Control level of output

-h, --help

Show this message and exit.

-F, --format [unix|json|text]

Output format for stdout. Defaults to text

--jmespath, --jq TEXT

A JMESPath expression to apply to json output. Forces the format to be json processed by this expression

--map-http-status TEXT

Map HTTP statuses to any of these exit codes: 0,1,50-99. e.g. "404=50,403=51"

EXAMPLES

Create a Globus Connect Personal endpoint:

$ globus endpoint create --personal my_gcp_endpoint

Create a Globus Connect Server endpoint:

$ globus endpoint create --server my_gcs_endpoint

Create a shared endpoint hosted on another endpoint:

$ host_ep=ddb59aef-6d04-11e5-ba46-22000b92c6ec
$ globus endpoint create --shared host_ep:~/ my_shared_endpoint

EXIT STATUS

0 on success.

1 if a network or server error occurred, unless --map-http-status has been used to change exit behavior on http error codes.

2 if the command was used improperly.

3 if the command was used on the wrong type of object, e.g. a collection command used on an endpoint.

4 if the command has authentication or authorization requirements which were not met, as in ConsentRequired errors or missing logins.