Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

PowerScaleOneFS CLI Command Reference

PDF

isi cloud access add

Adds cloud write access to the cluster for all accounts that are associated with the cluster GUID that was supplied.

Syntax

isi cloud access add <guid> 
 [--expiration-date]<timestamp>
 [--force
 [--verbose]

Options

<guid>
The GUID of the cluster that will be granted access to buckets for all cloud accounts.
--expiration-date <timestamp>
The date and time when unreferenced (stale) data will be removed from the cloud. The timestamp format is MMDDYY:hh:mm. For example, 022016:12:00 specifies an expiration date and time of February 20, 2016 at 12:00 PM.
Use this command to set the date when all currently unreferenced objects or files in the cloud will be deleted from the cloud.
{-- force | -f}
Do not ask for confirmation.
{--verbose | -v}
Displays more detailed information.

Examples

The following example adds cloud write access to a cluster by specifying the cluster GUID and an expiration date: 
isi cloud access add 000556bf1e82059801563f1ad44a8c155acf
--expiration-date 022016:12:00
OneFS displays a message indicating which cloud accounts and file pool policies the secondary cluster gain access to, and requires confirmation. Type yes, and press ENTER to complete the process.
NOTE:Only a single cluster should have access to the cloud accounts and pools for a specific GUID at a given time.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\