Intersight Module - Easy Intersight Managed Mode

Use Cases

• Build Workspaces in TFCB to support Infrastructure as Code Provisioning.
• Use Terraform/TFCB to provision Intersight Pools.
• Use Terraform/TFCB to provision Intersight UCS Policies.
• Use Terraform/TFCB to provision UCS Chassis Profiles in IMM Mode.
• Use Terraform/TFCB to provision UCS Domains in IMM Mode.
• Use Terraform/TFCB to provision UCS Server Profiles in IMM Mode.
• Use Terraform/TFCB to provision Operation Systems on Baremetal UCS Servers.

Pools - module/pools

• Fibre-Channel Pools (WWNN/WWPN)
• IP Pools
• IQN Pools
• MAC Pools
• UUID Pools

Intersight Policies - Folder modules/policies

• Adapter Configuration (Standalone Servers)
• BIOS
• Boot Order
• Certificate Management
• Device Connector
• Ethernet Adapter (vnIC Adapter Policy)
• Ethernet Network (Standalone Servers)
• Ethernet Network Control (CDP/LLDP)
• Ethernet Network Group (VLAN Groups)
• Ethernet QoS (vNIC QoS)
• FC Zone (Fibre-Channel Zoning Policy)
• Fibre Channel Adapter (vHBA Adapter Policy)
• Fibre Channel Network
• Fibre Channel QoS (vHBA QoS)
• Ethernet Network Control (CDP/LLDP)
• Ethernet Network Group (VLAN Groups)
• Flow Control
• IMC Access
• IPMI Over LAN
• iSCSI Adapter
• iSCSI Boot
• iSCSI Static Target
• LAN Connectivity
• LDAP (Standalone Servers)
• Link Aggregation
• Link Control
• Local User
• Multicast
• Network Connectivity (DNS)
• NTP
• Persistent Memory
• Port
• Power
• SAN Connectivity
• SD Card - Depricated
• Serial Over LAN
• SMTP
• SNMP
• SSH
• Storage
• Switch Control
• Syslog
• System QoS
• Thermal
• Virtual KVM
• Virtual Media
• VLAN
• VSAN

UCS Chassis Profiles - module/profiles

• ucs_chassis_profiles

UCS Domain Profiles - module/ucs_domain_profiles

• ucs_domain_profiles

UCS Server Profiles - module/profiles

• ucs_server_profiles

Pre-requisites and Guidelines

1. Sign up for a user account on Intersight.com. You will need at least one Advantage Tier license as well as a Intersight Workload Optimizer license to complete this use case. Log in to intersight.com and generate API/Secret Keys. Both licensing requirements can utilize the available demo licensing if you don't have the subscription levels.

2. Sign up for a TFCB (Terraform for Cloud Business) at https://app.terraform.io/. Log in and generate the User API Key. You will need this when you create the TF Cloud Target in Intersight. If not a paid version, you will need to enable the trial account.

3. Clone this repository to your own VCS Repository for the VCS Integration with Terraform Cloud.

4. Integrate your VCS Repository into the TFCB Orgnization following these instructions: https://www.terraform.io/docs/cloud/vcs/index.html. Be sure to copy the OAth Token which you will use later on for Workspace provisioning.

VERY IMPORTANT NOTE: The Terraform Cloud provider stores terraform state in plain text. Do not remove the .gitignore that is protecting you from uploading the state files to a public repository in this base directory. The rest of the modules don't have this same risk

Obtain tokens and keys

Terraform Cloud Variables

• terraform_cloud_token

  instructions: https://www.terraform.io/docs/cloud/users-teams-organizations/api-tokens.html

• tfc_oath_token

  instructions: https://www.terraform.io/docs/cloud/vcs/index.html

• tfc_organization (TFCB Organization Name)

• tfc_email (Must be an Email Assigned to the TFCB Account)

• agent_pool (The Name of the Agent Pool in the TFCB Account)

• vcs_repo (The Name of your Version Control Repository. i.e. CiscoDevNet/intersight-tfb-iks)

Intersight Variables

• apikey

• secretkey

  instructions: https://community.cisco.com/t5/data-center-documents/intersight-api-overview/ta-p/3651994

Import the Variables into your Environment before Running the Terraform Cloud Provider module(s) in this directory

Modify the terraform.tfvars file to the unique attributes of your environment for your domain and server profiles and policies.

Once finished with the modification commit the changes to your reposotiry.

The Following examples are for a Linux based Operating System. Note that the TF_VAR_ prefix is used as a notification to the terraform engine that the environment variable will be consumed by terraform.

• Terraform Cloud Variables - Linux

export TF_VAR_terraform_cloud_token="your_cloud_token"
export TF_VAR_tfc_oauth_token="your_oath_token"

• Terraform Cloud Variables - Windows

$env:TF_VAR_terraform_cloud_token="your_cloud_token"
$env:TF_VAR_tfc_oauth_token="your_oath_token"

• Intersight apikey and secretkey - Linux

export TF_VAR_apikey="your_api_key"
export TF_VAR_secretkey=`cat ~/Downloads/SecretKey.txt`

• Intersight apikey and secretkey - Windows

$env:TF_VAR_apikey="your_api_key"
$env:TF_VAR_secretkey="$HOME\Downloads\SecretKey.txt"

IPMI over LAN Secure Variables

Use the following environment variable, based on your deployment, for IPMI over LAN Settings if you want to configure encryption for the IPMI communication.

• IPMI over LAN Encryption Key

export TF_VAR_ipmi_key_1="your_password"

$env:TF_VAR_ipmi_key_1="your_password"

LDAP Secure Variables

Use the following environment variable, based on your deployment, for LDAP Policy Binding Settings.

• LDAP Binding user Password

export TF_VAR_ldap_password="your_password"

$env:TF_VAR_ldap_password="your_password"

Local User Secure Variables

Use the following environment variable, based on your deployment, for Local User Policy Users. This would allow you to configure up to 5 unique users in an organization for CIMC Access.

• Local user Password

export TF_VAR_local_user_password_1="your_password"
export TF_VAR_local_user_password_2="your_password"
export TF_VAR_local_user_password_3="your_password"
export TF_VAR_local_user_password_4="your_password"
export TF_VAR_local_user_password_5="your_password"

$env:TF_VAR_local_user_password_1="your_password"
$env:TF_VAR_local_user_password_2="your_password"
$env:TF_VAR_local_user_password_3="your_password"
$env:TF_VAR_local_user_password_4="your_password"
$env:TF_VAR_local_user_password_5="your_password"

Persistent Memory Secure Variables

Use the following environment variable, based on your deployment, for Persistent Memory Encryption.

• Persistent Memory Encryption Password

export TF_VAR_persistent_passphrase="your_password"

$env:TF_VAR_persistent_passphrase="your_password"

SNMP Secure Variables

Use the following environment variables, based on your deployment, for SNMP Settings. There are 5 values for each variable type. This allows for creating up to 5 snmp users or 5 community strings. You only need to configure these variables if you want to use them. For instance you want to add an SNMP user with AuthPriv. You would configure snmp_auth_password_1 and snmp_privacy_password_1. The rest can be unused unless you were going to configure 5 different SNMP users with different passwords. The same holds true with community strings.

• SNMP User Passwords

export TF_VAR_snmp_auth_password_1="your_password"
export TF_VAR_snmp_auth_password_2="your_password"
export TF_VAR_snmp_auth_password_3="your_password"
export TF_VAR_snmp_auth_password_4="your_password"
export TF_VAR_snmp_auth_password_5="your_password"
export TF_VAR_snmp_privacy_password_1="your_password"
export TF_VAR_snmp_privacy_password_2="your_password"
export TF_VAR_snmp_privacy_password_3="your_password"
export TF_VAR_snmp_privacy_password_4="your_password"
export TF_VAR_snmp_privacy_password_5="your_password"

$env:TF_VAR_snmp_auth_password_1="your_password"
$env:TF_VAR_snmp_auth_password_2="your_password"
$env:TF_VAR_snmp_auth_password_3="your_password"
$env:TF_VAR_snmp_auth_password_4="your_password"
$env:TF_VAR_snmp_auth_password_5="your_password"
$env:TF_VAR_snmp_privacy_password_1="your_password"
$env:TF_VAR_snmp_privacy_password_2="your_password"
$env:TF_VAR_snmp_privacy_password_3="your_password"
$env:TF_VAR_snmp_privacy_password_4="your_password"
$env:TF_VAR_snmp_privacy_password_5="your_password"

• SNMP Communities

export TF_VAR_access_community_string_1="your_community"
export TF_VAR_access_community_string_2="your_community"
export TF_VAR_access_community_string_3="your_community"
export TF_VAR_access_community_string_4="your_community"
export TF_VAR_access_community_string_5="your_community"
export TF_VAR_snmp_trap_community_1="your_community"
export TF_VAR_snmp_trap_community_2="your_community"
export TF_VAR_snmp_trap_community_3="your_community"
export TF_VAR_snmp_trap_community_4="your_community"
export TF_VAR_snmp_trap_community_5="your_community"

$env:TF_VAR_access_community_string_1="your_community"
$env:TF_VAR_access_community_string_2="your_community"
$env:TF_VAR_access_community_string_3="your_community"
$env:TF_VAR_access_community_string_4="your_community"
$env:TF_VAR_access_community_string_5="your_community"
$env:TF_VAR_snmp_trap_community_1="your_community"
$env:TF_VAR_snmp_trap_community_2="your_community"
$env:TF_VAR_snmp_trap_community_3="your_community"
$env:TF_VAR_snmp_trap_community_4="your_community"
$env:TF_VAR_snmp_trap_community_5="your_community"

Execute the Terraform Plan

Once all Variables have been imported into your environment, run the plan in the tfe folder:

Terraform Cloud

When running in Terraform Cloud with VCS Integration the first Plan will need to be run from the UI but subsiqent runs should trigger automatically

Terraform CLI

• Execute the Plan

terraform plan -out=main.plan
terraform apply main.plan

When run, this module will Create the Terraform Cloud Workspace(s) and Assign the Variables to the workspace(s).

Requirements

Providers

No providers.

Modules

Resources

No resources.

Inputs

map(object(
    {
      allow_destroy_plan        = optional(bool)
      auto_apply                = optional(bool)
      branch                    = optional(string)
      description               = optional(string)
      global_remote_state       = optional(bool)
      queue_all_runs            = optional(bool)
      remote_state_consumer_ids = optional(list(string))
      speculative_enabled       = optional(bool)
      working_directory         = string
      workspace_type            = string
    }
  ))

{
  "default": {
    "allow_destroy_plan": true,
    "auto_apply": false,
    "branch": "master",
    "description": "",
    "global_remote_state": false,
    "queue_all_runs": false,
    "remote_state_consumer_ids": [],
    "speculative_enabled": true,
    "working_directory": "",
    "workspace_type": ""
  }
}

Outputs