Globus Connect Server Collection Create
Synopsis
globus-connect-server collection create STORAGE_GATEWAY_ID
BASE_PATH
DISPLAY_NAME
[OPTIONS]…
Description
The globus-connect-server collection create command creates a new mapped collection. When you create a mapped collection, you are allow your users access to their own data on a Storage Gateway via the GridFTP and HTTPS protocols.
There are three required arguments to this command:
- STORAGE_GATEWAY_ID
-
The ID of the storage gateway which contains the data you want to provide access to. This will need to be created before creating the collection by using the storage-gateway create command.
- BASE_PATH
-
This is the path which is the root of the mapped collection. You can use / to provide access to the entire namespace of the storage gateway (depending on the path restrictions policy of the gateway), or you can restrict it to some subtree of the data available by using a different value here.
- DISPLAY_NAME
-
The name of the collection. This is not guaranteed to be unique, but can be used as a first piece of information for for your users to find the collection.
Other command line options allow additional metadata to help users search for the collection, control visibility of the collection, provide policies for sharing data on a collection, or requiring data encryption when accessing the collection.
Note that any of the options used when creating the collection may be updated using the globus-connect-server collection update command.
Visibility
A collection can be public or private. A public collection may show up in search results for any globus users. A private collection is only visible by those with role assignments.
The --public and --private command-line options determine whether a collection is public or not.
Metadata
Many of the options to this command allow you to set metadata on your collection to help your users find the collections that are relevant to their needs. The more metadata you supply, the easier it will be for them to find relevant collections.
The --keywords, --department, --organization, and --description options all provide data to improve results when searching for collections.
The --contact-email, --contact-info, and --info-link options will provide data that will help your users find out more about what data you provide in the collection.
Guest Collections
With Globus Connect Server v5.4, it is possible to create guest collections that allow users to share access to their data on a mapped collection with other Globus users. This must be explicitly enabled on a mapped collection by using the --allow-guest-collections command-line option. If this is not set, then users are not allowed to share data.
Additionally, you can set path restrictions for guest collections. For example, you could allow read-only access to the data on the storage gateway, or completely deny access to some subdirectories. Use the --sharing-restrict-paths command line option to configure this. By default, if guest collections are allowed, and the sharing path restrictions are not set, then users may share any paths visible on the collection via a guest collection.
In GCSv5.4.18 and higher, it is possible to set user specific sharing policy. These are managed by the globus-connect-server sharing-policy command. These policies allow additional path restrictions to be applied to allow or deny sharing of paths to individual users.
Also, you can restrict which accounts on the storage gateway can create guest collections. You can either provide a list of local user accounts which can create guest collections, or provide a list of local user accounts which can not create guest collections. For the POSIX connector, you can also perform restrictions on which POSIX groups the account is a member of. You can use the --sharing-user-allow, --sharing-user-deny, --posix-sharing-group-allow, --posix-sharing-group-deny (New in GCSv5.4.8), --posix-staging-sharing-group-allow, and -posix-staging-sharing-group-deny to configure these policies (New in GCSv5.4.10).
Currently, guest collections can only be created via the globus.org web application or the GCS Manager API. For most users, it’s easiest to visit the mapped collection on the web, click on the Shares tab and then the Create New Shared Collection button.
Options
- -h, --help
-
Show help message and exit.
- --version
-
Show the version and exit.
- -F, --format "text"|"json"
-
Output format for this command. If the format is json, then the resulting role document is displayed.
- --use-explicit-host IP_ADDRESS (new in 5.4.23)
-
IP address of the GCS node to use for this request. If not specified, any available GCS node in the endpoint will be used.
- --display-name
-
Name for the Collection
- --public
- --private
-
Set the Collection to be public or private (defaults to public)
- --domain-name TEXT (new in 5.4.13)
-
DNS host name for the collection (mapped collections only). This may be either a host name or a fully-qualified domain name, but if it is the latter it must be a subdomain of the endpoint’s domain.
- --allow-guest-collections
- --no-allow-guest-collections
-
Allow guest collections to be created on this collection. This option is only usable on mapped collections. If this option is disabled on a mapped collection which already has associated Guest Collections, those collections will no longer be accessible.
- --guest-auth-policy-id [UUID|null] (new in 5.4.57)
-
Set the auth policy on a mapped collection which is inherited by all guest collections attached to the mapped collection. Pass '--guest-auth-policy-id null' to remove the auth policy from the collection. This option is only usable on mapped collections.
- --disable-anonymous-writes (new in 5.4.27)
- --enable-anonymous-writes
-
Allow anonymous write ACLs on Guest Collections attached to this Mapped Collection. This option is only usable on non high assurance Mapped Collections and the setting is inherited by the hosted Guest Collections. Anonymous write ACLs are enabled by default.
- --sharing-restrict-paths
JSON
|file:JSON_FILE
-
Path restrictions for sharing data on guest collections based on this collection. This option is only usable on mapped collections. In the first syntax, you pass a PathRestrictions as a string; in the second syntax you pass the path to a file containing the PathRestrictions object.
-
--sharing-user-allow
USERNAME
(new in GCSv5.4.8) -
Allow a user on this collection’s storage gateway to create guest collections. This option can be included multiple times on a single command-line invocation to allow multiple users. When updating a collection, setting the value to an empty string will clear this restriction. This policy is only evaluated if the account passes the storage gateway user and (if applicable) group allowed checks.
-
--sharing-user-deny
USERNAME
(new in GCSv5.4.8) -
Deny a user on this collection’s storage gateway permission to create guest collections. This option can be included multiple times on a single command-line invocation to deny multiple users. When updating a collection, setting the value to an empty string will clear this restriction. This policy is only evaluated if the account passes the storage gateway user and (if applicable) group allowed checks.
-
--posix-sharing-group-allow
GROUPNAME
(new in GCSv5.4.8) -
Allow a user on this collection’s storage gateway to create guest collections if they are a member of the POSIX group
GROUPNAME
. This option can be included multiple times on a single command-line invocation to allow multiple groups. This is can only be used with collection on POSIX storage gateways. This policy is only evaluated if the account passes the storage gateway user and group allowed checks, and is not explicitly allowed or denied by the --sharing-user-allow and --sharing-user-deny values configured on this collection. -
--posix-sharing-group-deny
USERNAME
(new in GCSv5.4.8) -
Deny a user on this collection’s storage gateway permission to create guest collections if they are a member of the POSIX group
GROUPNAME
. This option can be included multiple times on a single command-line invocation to deny multiple groups. When updating a collection, setting the value to an empty string will clear this restriction. This is can only be used with collection on POSIX storage gateways. This policy is only evaluated if the account passes the storage gateway user and group allowed checks, and is not explicitly allowed or denied by the --sharing-user-allow and --sharing-user-deny values configured on this collection. -
--posix-staging-sharing-group-allow
GROUPNAME
(new in GCSv5.4.10) -
Allow a user on this collection’s storage gateway to create guest collections if they are a member of the POSIX group
GROUPNAME
. This option can be included multiple times on a single command-line invocation to allow multiple groups. This is can only be used with collection on POSIX Staging storage gateways. This policy is only evaluated if the account passes the storage gateway user and group allowed checks, and is not explicitly allowed or denied by the --sharing-user-allow and --sharing-user-deny values configured on this collection. -
--posix-staging-sharing-group-deny
USERNAME
(new in GCSv5.4.10) -
Deny a user on this collection’s storage gateway permission to create guest collections if they are a member of the POSIX group
GROUPNAME
. This option can be included multiple times on a single command-line invocation to deny multiple groups. When updating a collection, setting the value to an empty string will clear this restriction. This is can only be used with collection on POSIX Staging storage gateways. This policy is only evaluated if the account passes the storage gateway user and group allowed checks, and is not explicitly allowed or denied by the --sharing-user-allow and --sharing-user-deny values configured on this collection. - --force-encryption
- --no-force-encryption
-
When set, all transfers to and from this collection are always encrypted. If not set, this can be configured on a per-transfer basis. If a mapped collection forces encryption, all of its guest collections must as well. If this option is used on a mapped collection, the value is propagated to its guest collections.
- --keywords string,string,…
-
Comma separated list of keywords to help searches for the collection
- --department
DEPARTMENT
-
Department which operates the collection
- --organization
ORGANIZATION
-
Organization for the Collection
- --contact-email
EMAIL
-
Email address of the support contact for this collection. This is visible to end users so that they may contact your organization for support.
- --contact-info
INFO
-
Other non-email contact information for the collection, e.g. phone and mailing address. This is visible to end users for support.
- --info-link
URL
-
Link to a web page containing info about the collection.
- --description
STRING
-
Description of the collection.
- --identity-id
IDENTITY
-
Globus Auth identity to act as the owner of this collection. This only needs to be used if you have multiple linked identities that match the storage gateway policies and allows you to select which of those will act as the owner of this collection. The identity must have an endpoint administrator or endpoint owner role on the endpoint and must be in your current identity set.
- --google-project-id
PROJECT
-
For Google Cloud Storage backed Collections only. The Google Cloud Platform project ID to use when accessing this collection.
-
--user-message
MESSAGE
(new in 5.4.5) -
A message for clients to display to users when interacting with this collection. This can only be set on mapped collections, but its value is inherited by related guest collections.
-
--user-message-link
URL
(new in 5.4.5) -
Link to additional messaging for clients to display to users when interacting with this endpoint, linked to an http or https URL with this collection. This can only be set on mapped collections, but its value is inherited by related guest collections.
- --enable-https, --disable-https (new in 5.4.5)
-
Enable or disable the HTTPS interface to this collection. If HTTPS access is enabled for a mapped collection, it may be selectively disabled for individual guest collections. If HTTPS is is disabled for a mapped collection, it can not be enabled for a guest collection.
- --verify [force|disable|default] (new in 5.4.21)
-
Set the policy for this collection for file integrity verification after transfer. 'force' requires all transfers to perform verification. 'disable' disables all verification checks. 'default' allows the user to decide on verification at Transfer task submit time. When set on mapped collections, this policy is inherited by any guest collections.
- --default-directory TEXT
-
Default directory when browsing the collection.
- --delete-protected (new in 5.4.57)
-
Create the collection with delete protection enabled. When enabled, the mapped collection can not be deleted. An administrator can use the globus-connect-server collection update command to disable delete protection.