Configuring a Pure1 Adapter for VMware Cloud Foundation (VCF) Operations 8.x

User Guides for VMware Solutions

Audience
Public
Content Type
User Guides
Source Type
Documentation
  1. Log in to the VCF Operations user interface.
  2. Click the Administration tab.
  3. For VCF 9, the interface has changed.
    1. For VCF 9, click Integrations then select the Accounts tab.
    2. For vSphere 8, click Other Accounts that is found under the Solutions tab at the left-hand side of the page.
  4. Click Add Account.
  5. Click Pure1 Adapter.
  6. Complete the following fields:
    • Cloud Account Information
      • Name: Enter a display name for the cloud adapter instance.
      • Description: Optionally enter a description of the adapter instance.
    • Connection Information

      • Name: Enter a display name for the connection instance.
      • Pure1 API URI: This should be pre-populated. If it is not or it needs to be repopulated, the correct URI is: https://api.pure1.purestorage.com
      • HTTP Proxy Host: If the environment uses an HTTP proxy, the proxy server's FQDN or IP address.
      • HTTP Proxy Port: If the environment uses an HTTP proxy, the proxy server's port.
      • Lookback Minute Start: Start of the lookback period in minutes before the actual collection time.
      • Lookback Minute End: End of the lookback period in minutes before the actual collection time (should be lower than Looback Minute Start value).
      • Credential: Specify the credential name used to log into Pure1.
        • Credential name: Display name of the credential.
        • API key ID: Pure1 API key ID gathered from Pure1.
        • Private Key: This key needs to be of type RSA and have the format PKCS8 with a bit length of 2048. This key also needs to not have a password.
          • An example of how to generate this that should work in Putty or any modern terminal is:
            ssh-keygen -t rsa -f /Path/To/Private/Key/PrivateKeyName -m PKCS8 -b 2048
            
          • When examining the private key, the first and last line need to be:
            -----BEGIN PRIVATE KEY-----
            -----END PRIVATE KEY-----
          • For the public key used for the Pure1 API key, the public key generated by default with ssh-keygen will not work. Please generate a new public key that is type RSA in format PEM using openssl:
            openssl rsa -in /Path/To/Private/Key/PrivateKeyName -pubout -out /Path/To/Public/Key/PublicKeyName.pem
          • When examining the public key that will be pasted into Pure1 for the API key ID, the first and last line need to be:
            -----BEGIN PRIVATE KEY-----
            -----END PRIVATE KEY-----
        • HTTP Proxy Username: If the environment uses an HTTP proxy, the username of the proxy server if credentials are required for access to the proxy server.

        • HTTP Proxy Password: If the environment uses an HTTP proxy, the password of the proxy server if credentials are required for access to the proxy server.
      • Collector / Group: The VCF Operations collector that is used to manage the Pure1 Adapter processes.

  7. Click Test Connection to test the connection between the new adapter instance and Pure1.
  8. Optionally configure the fields in the Advanced Settings section. The Advanced Settings options include:
    • Auto Discovery: Determines how the Pure1 adapter discovers the Pure1 objects after the initial adapter configuration. If set to true (default), the Pure1 adapter automatically discovers any new objects that have been added to the Pure1 instance after the initial adapter configuration and collects data for the new objects. If set to false, the Pure1 adapter does not discover Pure1 objects. Instead, you must manually select which objects you want VCF Operations to monitor.