Nutanix Examples: Protection Policy with VM Migration & Active Directory Authentication
Those looking to explore Nutanix on Equinix Metal are likely to have two concerns in mind: ease of migration and security. Thankfully, two examples have recently been added to the Equinix Terraform directory that demonstrate exactly how a user can accomplish these two things. Nutanix Clusters Setup and Protection Policy - walks a user through creating two Nutanix Clusters on Equinix Metal rapidly, create a protection policy between them, and then practice creating a VM in one cluster and migrating it to the other cluster. Nutanix on Equinix Metal with Active Directory Authentication - helps a user create a cluster on Equinix, add an AD server VM, configure AD authentication, and map a few sample roles to the AD. Both examples use a combination of Terraform and manual Prism console steps, promoting understanding while deploying with speed and convenience. Consider walking through these examples if you're interested in exploring Nutanix on Equinix Metal or learning more about making your infrastructure more reliable and secure.Cloud Infrastructure Made Easy: IaC Demo Day!
Hey everyone! We’re thrilled to be hosting our second Demo Day of 2024, this time all about Infracode! If you’re already an infrastructure expert slinging Terraform or just starting out, we’ve got experts from across the industry to share their experiences with you! We’ll have folks like Marino Wijay of Kong talking about Platform best practices for AI, Jared Watts talking about Crossplane, and Engin Diri to talk to us about Pulumi. We’ve even got two of our Equinix DevRel Engineers, Chris Privitere and Oscar Cobles to talk about Kubernetes Cluster API and using Terraform to interconnect Equinix Metal and your AWS cloud. See our Event Page for more information and/or join us live at the link below so you can post your questions for our speakers directly in the chat! Can’t wait to see you in the chat! P.S. -- if you can’t make it, or you’re getting this late, don’t panic! Our full session will be embedded below
Terraform Provider Demo | Inside Equinix Developer Tech
In this video, we explore Terraform as the industry standard for provisioning on Equinix Metal. We’ll discuss the advantages of a declarative approach using HashiCorp Configuration Language (HCL), which enables reproducible and repeatable server environments. Join us for a demonstration of setting up Equinix Metal, including authentication and creating projects and devices with user data for automated configurations. Thank you for watching, and don’t miss the other videos in this series!
What is Infrastructure as Code?
Discover how Infrastructure as Code (IaC) can transform your workflow by enabling automation for provisioning and managing infrastructure. Explore popular IaC tools like Terraform and Pulumi, and learn how Equinix's IaC providers can enhance your services. Understand the benefits of IaC in reducing human error, speeding up deployments, and maintaining consistency across different environments. Subscribe for more insights and visit deploy.equinix.com/labs for detailed information.
Terraform CDK | Inside Equinix Developer Tech
In this video, David Flanagan a.k.a. Rawkode, does a deepdive on the Equinix Terraform CDK. David will discuss the advantages of using Terraform CDK for your Equinix provisioning, emphasizing the benefits of a declarative approach to code. This method allows for reusable snippets across teams, reducing redundant work. We'll demonstrate how to create a function to find the cheapest server configuration and show how this refactored code can be published and shared via various platforms like NPM and PyPy. Thank you for joining this walkthrough on provisioning Equinix Metal devices with Terraform CDK. Be sure to check out the other demo videos in this series. See you next time!
Nutanix Terraform Cluster Provisioning
Come join Equinix's Chris Privitere! Nutanix Terraform Cluster Provisioning simplifies the process of setting up cloud environments. By using a few lines of code, you can efficiently configure and deploy clusters. This method ensures a streamlined and consistent setup, reducing manual errors. It's a reliable solution for managing complex IT infrastructures. LINKS Nutanix Workshop Create an Account Deploy Labs
Nutanix Terraform Cluster Provisioning
Come join Equinix's Chris Privitere! Nutanix Terraform Cluster Provisioning simplifies the process of setting up cloud environments. By using a few lines of code, you can efficiently configure and deploy clusters. This method ensures a streamlined and consistent setup, reducing manual errors. It's a reliable solution for managing complex IT infrastructures.Running Terraform from a restricted environment
When running Terraform to provision and manage Equinix Fabric, Metal, and Network Edge, you may want to run Terraform from a restricted environment. Network filtering ACLs will need a predictable set of IP ranges to permit. This discussion will help you discover the IP services, ports, and address ranges your Terraform runner environment will need access to. We'll also discuss alternative ways to run Terraform configuration. If your ACLs permit the Terraform runner environment outbound HTTPS (TCP 443) and responses, that would cover everything Terraform needs to start provisioning infrastructure on Equinix. We'll assume we don't have unrestricted access and dig in a little further. Upon running, `terraform init`, Terraform will attempt to use DNS (UDP/TCP 53) services and HTTPS services to download provider plugins, such as the Equinix Terraform provider. The default host for fetching these plugins is registry.terraform.io, managed by Hashicorp. This is the defacto hub for public providers and published Terraform modules, although you may run your own local registry service. DNS for the Terraform registry points to CloudFront, a CDN whose addresses may change. If this presents a problem, there are options to download (or mirror) the necessary plugins in advance and use locally distributed copies. https://developer.hashicorp.com/terraform/cli/plugins Similarly, the DNS service for api.equinix.com, the one base domain that the Terraform Equinix provider will need for API access, resolves to Akamai, another CDN whose addresses may change or depend on where the request originates. As a Terraform configuration grows, you'll likely want to enable SSH access to the Metal and NE nodes being provisioned to automate OS provisioning. The SSH addresses will vary depending on the Metro where services are deployed. One way to ensure that the addresses are predictable in Metal is to provision the servers using Elastic IP addresses. A good follow-up question to this discussion is which ranges are assigned to NE devices and whether these IP addresses can be drawn from a predefined pool like Metal's Elastic IP Addresses. Terraform configurations typically include resources from multiple cloud providers. The node where the configuration is run would need to permit access to the APIs of these other providers. We'll leave the network filters needed by provisioned nodes to another discussion. Depending on your needs, cloud service providers offer managed services for Terraform or OpenTofu (a fork of Terraform persisting the original open-source license). These services can run your Terraform configuration predictably and reliably from a central location. Hashicorp provides the HCP service. https://developer.hashicorp.com/terraform/cloud-docs/run/run-environment Alternatives include: https://spacelift.io/ https://upbound.io https://www.env0.com/ https://www.scalr.com/ You can run similar CI/CD Terraform configuration control planes in your own backend with opensource tools such as: https://argoproj.github.io/cd/ https://www.crossplane.io/ https://docs.tofutf.io/ These SaaS providers or local solutions will also need access to the cloud provider APIs and nodes. With these providers you have full control of the configuration that is run and you can work these into a GitOps workflow. There are even more alternatives outside of the Terraform ecosystem. However, the Terraform ecosystem is your best option for the richest IaC integration experience with Equinix digital services. Equinix provides several Terraform modules to make it easy to get started. That extended ecosystem includes IaC tools that take advantage of the robust Equinix Terraform provider. These tools include Pulumi and Crossplane. TLDR; You'll want to expose select DNS, HTTPS, and SSH access from your Terraform runners. What alternative deployment strategies did I miss? What other network restrictions should be considered?
