Global Namespace (GNS)

Describes the data plane that connects all of your HPE Data Fabric deployments.

Because enterprise data is scattered across multiple sources between edge, core, and multi-cloud, a mechanism is needed to enable access to the data seamlessly, irrespective of the data location. The global namespace is a solution that aggregates disparate and remote data sources and provides a namespace that encompasses all of your infrastructure and deployments. The global namespace maintains the native security model of the HPE Data Fabric, so that location details are abstracted from the application.

Global namespace technology lets you manage globally deployed data as a single resource. Because of the global namespace, you can view and run multiple fabrics as a single, logical, and local fabric. The global namespace is designed to span multiple edge nodes, on-prem data centers, and clouds:

A global namespace stitches multiple data sources into a single accessible entity and provides multiple data access points, where each access point shows the same hierarchical namespace. The entire group of data sources could be accessed and operated by using any one of the access points, without any need to know the source's physical data location.

In the global namespace, all fabrics can view all other fabrics. The Data Fabric UI shows the global namespace on the All resources page in the Graph view.

Following is a sample screenshot for the graph view.

The global namespace is available in the Table view. If you have an elaborate list of fabrics and fabric resources in your global namespace, it might be a good idea to view the resources in the table view. To view resources in the table view, you must click the table view icon that is placed to the right of the Actions menu.

Following is a sample screenshot for the table view.

The Data Fabric also supports adding external NFSv4 and external S3 object stores to a global namespace.

In support of S3 object stores, S3 clients can access multiple fabrics by using a single endpoint after specifying a single pair of access key and secret key.