Effective December 3, NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources.For accounts that did not pre-register (prior to Dec 3), access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity.To learn more, read the FAQ and watch the video.Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.
Are you also like me, and would like to see Hitachi NAS (HNAS) inventory support in OCI?
If you have spare time, and want to get together to run a "standalone" OCI datasource to automatically run a bunch of CLI commands via SSH against your HNAS, we would appreciate this as this will help us work towards a OCI HNAS beta datasource for OCI 7.1.x early next year.
Email me at ostiguy at netapp dot com if you'd like to get together via a webex - all we need is:
the ability to download and unzip this standalone datasource onto your OCI server
Administrator level username and password that can SSH to the HNAS - we aren't certain yet if we can live with only read-only credentials.
A standalone datasource is a fancy name for a zip file that unpacks a batch script with some java code. We invoke the batch script, passing some parameters that get passed to a standalone Java runtime environment that runs out code, using the credentials and IP to SSH, and running a variety of read only CLI commands. We log all the data. This will not impact OCI in any way - OCI has no idea we'd be doing this.
#1. It is shipping with OCI 7.2.0, and will ship with the next OCI 7.1.x data source service pack, as well as with OCI 7.1.3, what will likely be the last maintenance release for OCI 7.1.x
#2. Currently, we have implemented reporting OCI storage pools (spans in HDS-speak), OCI internal volumes ("file systems" in HDS-speak). We will know which internal volumes maps to which SVM/vFiler (EVS in HDS-speak). What we haven't implemented yet is qtree support (virtual voliume aka vivol in HDS-speak) or iSCSI support.
OCI is treating HNAS as a storage virtualizer, and so long as you discover the backend storage, OCI will understand which HNAS storage pool sits on virtual disks mapping to volumes from the appropriate backend arrays.