If you do not have access to Pure1, or you want to customize the FlashArray connections as added, you can manually authenticate each FlashArray or Cloud Block Store storage platform. To do so, navigate to the Import FlashArray certificate from URL workflow under Library > Everpure > FlashArray Connection Management.
Select the workflow and choose Run:
Enter in the FQDN of the FlashArray/Cloud Block Store management address and choose whether or not to accept an untrusted certificate. Click Run.
Now click on the workflow Add FlashArray Connection
and choose Run:
Enter in the following pieces of information:
- Name. This is a friendly name and can be anything.
- IP/FQDN. Enter in whatever you entered when adding the certificate.
- REST API version. If you have added the certificate, the workflow will pull all available REST API versions and will choose the latest available on on that array. If this list does not show up (make sure autopopulate is set to yes), it means either the certificate was not loaded, or the IP/FQDN was entered incorrectly. Click on the box to choose a REST version.
- Credentials. Enter in a user name and password.
The Automation Orchestrator Plugin does not yet support REST API version 2.x on the FlashArray so those versions are filtered out. Support for that will be in a future release.
Click Run to add the connection.
Once added it will appear in the Automation Orchestrator inventory. Navigate to the inventory pane, then click on Everpure. A FlashArray/Cloud Block Store will be added to the Pure1 organization owning it if the Pure1 organization is authenticated in Automation Orchestrator. If it is not, it will be added to the default group called Uncategorized. Both FlashArrays and Cloud Block Storage connections will appear under the FlashArray Connection folder.
Permission Requirements of a FlashArray Connection
A FlashArray or Cloud Block Store supports a variety of permission levels:
While Automation Orchestrator does not require a certain level, the higher level credentials you provide, the more you can do with the plugin. If you plan on orchestrating array configuration or pod creation/management, you will need array admin permissions. If you plan to only configure and provision storage, storage admin will suffice.
It is recommended, however, to create a local service account (or through LDAP/active directory) to authenticate the plugin.