#ONTAP Day 0 Automation

1 messages · Page 1 of 1 (latest)

azure sage
#

Does anyone use Ansible to do Day 0 configuration of a cluster?

  • Configure SP (expect?)
  • Reboot (expect?)
  • zero disks... (expect?)
  • etc... (expect?)
  • Cluster manage LIF is ready --> start using REST...
stark pumice
#

Because ansible using the REST API. Thing like Reboot (while can be done with ansible) are not going to be Idempotent as the REST API won't respond when rebooting.

azure sage
#

Eh, I learned today that there’s an expect module for Ansible…

#

That must have some way to handle or bypass idempodence.

#

The existing tooling my group uses from NetApp engineering to bootstrap a hardware cluster from a power reset at the PDU/CDU using an SNMP call then takes over through a terminal server via expect, unfortunately, has many assumptions that are inaccurate to our environment. So, we’re looking for an alternative…

Between Ansible having support for SNMP and expect, I believe my group will be able to create something using Ansible.

swift lotus
azure sage
#

I did and @mental forge DM'd me about it. (By the way, much appreciated @mental forge).
There are a few phases to my scenario:

  1. The cluster is in a fully isolated VLAN. No NAT allowed. Access between Ansible server 01 (Ansible-External) and the nodes is and is only terminal.
  2. Reboot is done 'hard' via SNMP because we don't know the state the controllers are being 'returned' to us by the user.
  3. Once the controllers are configured to a the point that Ansible can take over, an Ansible server on the same VLAN (Ansible-Internal) will take over and configure the nodes/cluster as the necessary.

I've researched the APIs that System Manager uses (anyone can do it with increased logging) and there are APIs that Ansible is not setup to use that can be used "manually" to dynamically find the other nodes (based on standardized naming) and configure the cluster.