---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Cloudian Storage

# Cloudian Storage Discovery {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Cloudian Storage Discovery

ServiceNow Discovery enables identification and mapping of Cloudian Storage components, including Cloudian servers and related disks, by using specialized discovery patterns.
These patterns require installation of specific applications from the ServiceNow Store, such as the Patterns application, Discovery and Service Mapping Patterns, and the CMDB CI Class Models.
The discovery process supports Cloudian Storage components running on the ServiceNow AI Platform from the Paris release onward.
Show full answer Show less  
Cloudian provides software-defined, S3-compatible object storage solutions known as Cloudian Hyperstore, which can be deployed on CentOS or RHEL servers, physical hardware, VMs, or Cloudian appliances.

## Prerequisites and Setup

* The device must respond to `/bin/systemctl status cloudian-s3` with valid output containing "Cloudian HyperStore Storage System" to be identified as a Cloudian server; otherwise, it is discovered as a Linux server.
* Ensure SSH credentials are configured properly for the Cloudian Storage Server.
* The MID server must have network access to the target Cloudian device.
* The Discovery user must have sufficient privileges to execute discovery commands.
* Install required plugins: **CMDB CI Class Models (v1.31.0 or later)** and **Discovery and Service Mapping Patterns (v1.0.84 or later)**.

## Credentials and Compatibility

Cloudian Hyperstore software must be deployed on CentOS or RHEL servers. Credential configuration is consistent with Linux server credentials. SSH credentials must be configured to allow Discovery to access the Cloudian Storage Server.

## Running Discovery

To discover Cloudian Storage Systems, create a Discovery schedule targeting the IP address of the Cloudian Storage Server with appropriate SSH credentials. Discovery will collect information during horizontal discovery about storage servers, disks, file systems, network adapters, and IP addresses.

## Data Collected by Discovery

* **Storage Server \[cmdbcistorageserver\]**: Captures details such as name, serial number, IP address, manufacturer, model, OS version, CPU details, RAM, and short description.
* **Disk \[cmdbcidisk\]**: Includes name, device ID, storage type, size, manufacturer, and relationship to the storage server.
* **File System \[cmdbcifilesystem\]**: Records name, size, free space, mount point, and references to disks and storage servers.
* **Network Adapter \[cmdbcinetworkadapter\]** and **IP Address \[cmdbciipaddress\]**: Collects network interface and IP details linked to the storage server.

## Classification and CMDB Integration

The Cloudian probe runs a system command to verify the presence of Cloudian HyperStore software. It classifies devices as Cloudian Storage Servers ahead of generic Linux classification, creating configuration item (CI) records in the `cmdbcistorageserver` table. This classification triggers the Cloudian Storage System Pattern for detailed discovery.

## CI Relationships

The Cloudian Storage pattern establishes key relationships within the CMDB to accurately represent infrastructure dependencies:

* **Storage Server** owns **Network Adapters** and **IP Addresses**
* **Storage Server** contains **Disks** and **File Systems**
* **Storage Server** virtualizes **VM Instances**
* **Disks** provide **File Systems**

## Practical Benefits for ServiceNow Customers

By leveraging Cloudian Storage Discovery, customers can automate the identification and mapping of Cloudian Storage infrastructure within their CMDB. This enables accurate asset tracking, dependency mapping, and improved service management for Cloudian environments integrated with ServiceNow Discovery and Service Mapping capabilities.  
ServiceNow
Discovery uses the Cloudian Storage discovery pattern to find Cloudian servers and
related disks. Discovering these resources requires installing the Patterns application from the
ServiceNow Store.

Discovery uses Cloudian Storage System patterns to find Cloudian Storage system data.
Discovering these resources requires installing the Discovery and Service Mapping Patterns and
the CMDB CI Class Models applications from the ServiceNow

Store, as each application is dependent on the other.

You can use the patterns
for discovering the Cloudian Storage components on the ServiceNow AI Platform using the Paris
release or later.

Cloudian is a software-defined data storage company. Cloudian provides turnkey distributed
software-defined
S3-compatible object storage
solutions.

Cloudian Hyperstore Software
:
Deploy the CentOS operating system, related packages, and Hyperstore software binary files on the
Hyperstore Node.

Cloudian Hyperstore Node:
This is an independent hardware server in which Cloudian Hyperstore software is
deployed on an industry standard server or on a VM. It can also be pre-installed on a Cloudian Hyperstore appliance.

## Request apps on the Store {#cloudian-storage-discovery__section_sv2_vw5_5mb}

Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#cloudian-storage-discovery__inline-send-to-store}

## Prerequisites {#cloudian-storage-discovery__section_ssc_c1h_gqb}

To discover a device as a Cloudian server, the /bin/systemctl status cloudian-s3 command must return valid responses and contain the Cloudian HyperStore Storage System. If this is not the case, then the device is discovered
as a Linux server.  
* Make sure the client is using Discovery patterns.
* Set SSH credentials for the Cloudian Storage Server.
* Make sure the MID server has access to the target device.
* Ensure that the Discovery user has the correct privileges to run commands.
* Install the following plugins:
*
  * CMDB CI Class Models plugin (Version 1.31.0 or later)
  * Discovery and Service Mapping Patterns plugin (Version 1.0.84 or later)
  * Discovery and Service Mapping Patterns: (sn_itom_pattern) version 1.0.84 and dependent plugin CMDB CI Class Models (sn_cmdb_ci_class) version 1.31.0 (October content release)
  {#cloudian-storage-discovery__ul_khp_kw3_2rb}
{#cloudian-storage-discovery__ul_jhp_kw3_2rb}

## Credentials {#cloudian-storage-discovery__section_dyv_zxc_2rb}

Make sure the Cloudian Hyperstore Software is deployed on either CentOS or RHEL Servers. The
credentials configurations are the same as for a Linux server.

Configure the SSH credentials for the Cloudian Storage Server.

## Running Discovery {#cloudian-storage-discovery__section_lbt_j1j_2rb}

To discover the Cloudian Storage System, create a Discovery schedule that targets the IP
address of the Cloudian Storage Server. Make sure that the SSH
credentials that you configured can access the Cloudian Server.

## Data collected by Discovery during horizontal discovery {#cloudian-storage-discovery__section_flq_pnq_cqb}

{#cloudian-storage-discovery__table_ths_ldd_2qb__entry__2}

| Field | Description |
|-|-|
| name |   |
| serial_number |   |
| ip_address |   |
| manufacturer |   |
| model_id |   |
| short_description |   |
| os_version |   |
| os |   |
| ram |   |
| cpu_manufacturer |   |
| cpu_name |   |
| cpu_core_count |   |
| cpu_type |   |
[Table 1. Storage Server \[cmdb_ci_storage_server\]]

{#cloudian-storage-discovery__table_ths_ldd_2qb} {#cloudian-storage-discovery__table_svv_nfd_2qb__entry__2}

| Field | Description |
|-|-|
| name |   |
| device_id |   |
| storage_type |   |
| size_bytes |   |
| manufacturer |   |
| model_id |   |
| computer \[Reference cmdb_ci_storage_server\] |   |
[Table 2. Disk \[cmdb_ci_disk\]]

{#cloudian-storage-discovery__table_svv_nfd_2qb}

## File System \[cmdb_ci_file_system\] {#cloudian-storage-discovery__section_gpd_tbj_2rb}

{#cloudian-storage-discovery__table_ohd_tbj_2rb__entry__2}

| Field | Description |
|-|-|
| name |   |
| size_bytes |   |
| free_space_bytes |   |
| file_system |   |
| mount_point |   |
| computer \[Reference cmdb_ci_storage_server\] |   |
| provided_by \[Reference cmdb_ci_disk\] |   |
[ ]

{#cloudian-storage-discovery__table_ohd_tbj_2rb}

## Network Adapter \[cmdb_ci_network_adapter\] {#cloudian-storage-discovery__section_ngx_tbj_2rb}

{#cloudian-storage-discovery__table_phd_tbj_2rb__entry__2}

| Field | Description |
|-|-|
| name |   |
| ip_address |   |
| netmask |   |
| mac_address |   |
| cmdb_ci \[Reference cmdb_ci_storage_server\] |   |
[ ]

{#cloudian-storage-discovery__table_phd_tbj_2rb}

## IP Address \[cmdb_ci_ip_address\] {#cloudian-storage-discovery__section_syx_bcj_2rb}

{#cloudian-storage-discovery__table_qhd_tbj_2rb__entry__2}

| Field | Description |
|-|-|
| ip_address |   |
| netmask |   |
| nic \[Reference cmdb_ci_network_adapter\] |   |
[ ]

{#cloudian-storage-discovery__table_qhd_tbj_2rb}

The Cloudianprobe is created in the
Unix-Classify Multiprobe. The Cloudian probe runs
the /bin/systemctl status cloudian-s3 command and checks that the output
contains Cloudian HyperStore Storage System.
Figure 1. Cloudian Probe

In Unix classification, the Cloudian Server classifier runs before the
Linux Classifier. The Cloudian classifier creates records in the
\[cmdb_ci_storage_server\] table. This classifier invokes the Cloudian Storage System Pattern.
Classification CriteriaFigure 2. Classification Criteria

## CMDB Data Model {#cloudian-storage-discovery__section_chb_vlj_2rb}

Figure 3. CMDB Data Model  
Storage Server to Network AdapterFigure 4. Storage Server to Network Adapter Storage Server to DisksFigure 5. Storage Server to Disks  
Storage Server to Disks and File SystemsFigure 6. Storage Server to Disks and File Systems

## CI Relationships {#cloudian-storage-discovery__section_ezp_j3b_gqb}

## Relationships created by the Cloudian Storage pattern {#cloudian-storage-discovery__section_trc_qd5_3qb}

{#cloudian-storage-discovery__id_wxw_5d5_3qb__entry__3}

| Parent | Relationship | Child |
|-|-|-|
| cmdb_ci_storage_server | Owns::Owned by | cmdb_ci_network_adapter |
| cmdb_ci_storage_server | Owns::Owned by | cmdb_ci_ip_address |
| cmdb_ci_storage_server | Contains::Contained by | cmdb_ci_disk |
| cmdb_ci_storage_server | Contains::Contained by | cmdb_ci_file_system |
| cmdb_ci_storage_server | Virtualized by::Virtualizes | cmdb_ci_vm_instance |
| cmdb_ci_disk | Provides::Provided by | cmdb_ci_file_system |
[ ]

{#cloudian-storage-discovery__id_wxw_5d5_3qb}