Search Results

Every StorONE system runs against a license that determines what capacity and features are available. This chapter covers viewing your current license details and uploading a new license file — for example, after a capacity or feature entitlement change from S...

This chapter covers the customer-configurable system and session settings: how capacity numbers are displayed, how CLI output is formatted, and where to find the anomaly detection settings. Capacity display units Every capacity value StorONE displays — drive s...

StorONE supports non-disruptive updates (NDU) — installing a new software version on a node without taking your storage offline. The customer-facing update flow has two steps: upload the update package to the node you want to update, then install it. Each node...

A system is a StorONE-managed cluster — a single controller or an HA controller pair, along with everything it manages (applications, volumes, pools, and so on). A single CLI or web session can be connected to more than one system at once: one system is always...

When you replicate NAS or object volumes to a remote StorONE system, clients need a stable address to reach whichever side is currently primary. Pairing a local floating IP with a remote one is how you set that up: the two floating IPs are linked, and only one...

A floating IP is a virtual IP address that isn't permanently tied to one node — StorONE moves it between nodes as needed, so clients keep using the same address regardless of which physical node is actually serving it. This is what lets a client connection sur...

On a high-availability (HA) pair, both nodes are normally active, each owning a share of the system's volumes. These commands change that ownership — moving every volume onto one node (takeover), restoring the normal split afterward (giveback) — and let you re...

A StorONE cluster is made up of one or more physical (or virtual) nodes — the servers that run the StorONE software and serve I/O to your hosts. This chapter covers the node-level administration and network settings that are available to you as a customer; mos...

This page covers two unrelated but customer-facing groups of node commands: giving StorONE support secure remote access when you need help, and the iSCSI-related network settings (CHAP authentication and iSNS discovery) that apply to your nodes' iSCSI targets....

The three basic permission roles ( Read, ReadWrite, Admin) are all-or-nothing across the whole system. A permission policy lets you build something more targeted — for example, a user who can create and edit volumes but never delete them, or a user who can o...

StorONE user accounts control who can log in to the system — through the web interface, the CLI, or the REST API — and what they're allowed to do once they're in. Every account is either a local user (username and password stored in S1 itself) or an LDAP user ...

The StorONE REST API lets you do over HTTPS what you do in the web interface and the CLI: provision storage, manage snapshots and replication, read monitoring data, configure notifications, and so on. It's the right tool when another system needs to drive Stor...

You authenticate to the REST API with the same StorONE user accounts you use for the web interface and the CLI. You log in once to get a session token, then send that token with every request. Logging in POST /login Content-Type: application/json { "Username...

Every endpoint follows the same conventions, so once you've made one call you know how to make them all. This page covers how to send parameters, the two generic parameters ( async and outputType), and how to read results and errors. Making a request Send the...

By default, a create, edit, or delete request waits for the operation to finish and returns the outcome. That's the simplest way to script a sequence of steps. For operations that can take a while, or when you want to start several at once, you can run an oper...

Each example below does the same thing, so you can pick the language you work in: Log in and get a session token. List the hosts on the system. Create a test host and check that it worked. Delete it again in the background ( async=true), and wait for the job t...

These endpoints mirror the CLI commands described in Action Policies, Pending Actions. Each endpoint runs the CLI command named under its heading, so the behavior, defaults, and restrictions are the same; this page lists how to call it over REST. Conventions t...

These endpoints mirror the CLI commands described in Applications, Volumes. Each endpoint runs the CLI command named under its heading, so the behavior, defaults, and restrictions are the same; this page lists how to call it over REST. Conventions that apply t...