Overview
Scality builds software-defined storage that runs on standard servers instead of purpose-built arrays. RING spreads objects across a pool of commodity nodes and presents them through file and S3-compatible object interfaces, and ARTESCA is the smaller, container-native object platform aimed at edge and backup targets. Because the storage is software on servers you already own, the estate question splits in two: what capacity and tenancy the platform reports, and which physical machines are carrying it.
The ReadyWorks connector is a JSON REST client for the Scality management interface, running on the json_rest_api.php driver. It takes an API domain, a username and password, and a server-side working path used while a response is parsed, and it authenticates with a Base64-encoded HTTP Basic header. This is the most minimal connection form in the storage set: four fields, with no Single Authentication control and no connection-wide Additional Job Fields list.
For ReadyWorks that second half of the question is the interesting one. Capacity and bucket records describe the service; the underlying nodes are servers with serial numbers, warranties and refresh dates that belong in the same estate view as the rest of the hardware. Pulling both sides in lets you see that a storage service depends on a specific set of machines, plan node replacement without losing the data protection the RING provides, and hold tenants and consumed capacity against the business owners who are being charged for them.
The connector is registered as bidirectional. Inbound jobs pull into staging, and the outbound side posts a record from ReadyWorks to an endpoint you nominate, mapping status, message and record key from the reply. Neither direction ships with an endpoint configured.
NOTE: Because there is no Single Authentication control on this connection form, the authentication phase runs again on every pagination and enumeration loop. That is fixed behaviour for this connector and cannot be turned off from the connection.
Connector Properties
Authentication Methods
Scality offers a single authentication method, using a username and password sent as an HTTP Basic credential.
Method 1: Basic Authorization: Username / Password (SCALITY_7cdfe7753a)
Connect to a GET method API with a username / password
Joins the connection’s username and password, Base64-encodes them and sends them as an Authorization: Basic header. Use an account with read access to the management interface you are collecting from, and confirm which of the Scality management surfaces your deployment exposes, since RING and ARTESCA present different administrative interfaces on different addresses.
Connection Configuration Fields (4)
Authentication Configuration
Headers sent on the authentication call:
cURL options:
NOTE: Username and Password are both marked optional even though the Basic credential is assembled from them. A connection saved with either field blank will send a malformed credential rather than failing at save time.
Inbound Job Fields Enabled (44)
Inbound jobs expose the full REST field set, including three levels of enumeration and all five pagination modes.
NOTE: Several labels and tooltips in this form carry defects inherited from the shared ETL5 field templates: the Enumeration 1 Node label reads “Enumaration”, the Append New Data label reads “Exisiting”, and the help text on Enumeration 1 Keys End Point and Enumeration 3 Fields both refer to enumeration 2. The underlying fields behave as their labels say.
Outbound Job Fields Enabled (13)
Outbound jobs expose the REST posting field set, including the outbound field list, the return data mapping and an optional raw JSON body template.
Inbound Job Templates (1)
Scality ships one inbound template, and it is the generic REST skeleton rather than a RING or ARTESCA data pull.
Job Template Configuration
Settings
Outbound Job Templates (1)
One outbound template ships, and it is the matching generic REST skeleton.
Job Template Configuration
Settings
Job Parameters and Enumeration
Rest POST API
Outbound fields list:
Return data fields: