Equinix Provider for Terraform v1.14.0 Release
The 1.14.0 release of terraform-provider-equinix includes code and documentation to help users identify and update Terraform configurations that are impacted by the deprecation of facilities in the Equinix Metal platform. In addition, this release adds support for the DSA key type in the equinix_network_ssh_key resource, which makes it possible to provision routers in Network Edge with Terraform.OpenShift on Baremetal v0.5.0
A Terraform module that quickly installs OpenShift for use on Equinix Metal. First off, v0.4.0 aligned with the support of metros and deprecated the use of facilities; see the announcement here. The default location was changed from SJC1 to DA, the default size is c3.small vs the previous c2.medium, and Terraform version 1 or higher is required. Underlying this is also a switch from our Metal specific Terraform provider to the full Equinix Terraform provider (v.1.14.1). This allows more configurability for node plans and better default node plans. Newer versions of OpenShift are used. This also includes several outstanding bug and CI fixes that were preventing the project from successfully functioning. It is recommended to rebuild any existing deployments. Migration should be possible by converting the state files as described in the Migrating from equinix/metal to equinix/equinix. v0.5.0 does all the above but includes minor update to the install instructions and provides us with module_name visibility that we use to gauge usage as an indicator of audience value.Ansible-Collection-Equinix v0.1.0 Release
This is the first release of the Equinix Ansible Collection. This collection will mature to succeed the Ansible Equinix Metal collection. The big difference with this collection is that the goal of the project is to cover all Equinix APIs over time, starting with Metal, Fabric, and Network Edge. If you are just getting started with Ansible on Equinix, this is the project to use. Let us know which features you’ll need for your playbooks. We’ve stubbed out issues for all of the resources that will be needed to put this provider on parity with the Equinix Terraform provider which has the the most complete IaC coverage today. Broader API coverage is being facilitated by the move away from legacy, hand-crafted, Python SDKs (packet-python). We will favor (and produce) SDKs generated from the OpenAPI spec for each Equinix API that will be supported. Metal Python is the first of these, an SDK built for wide adoption. Its readiness to simplify the API developer experience in Python is demonstrated throughout the Equinix Ansible collection. Additionally, this collection is applying some of the best practices seen in other Cloud Provider Ansible modules. This is most visible in the name of the module and how it is imported. See the project's E2E tests for working examples of how this collection can be used.Equinix Provider for Terraform v1.14.3 Release
The 1.14.3 release of the Equinix Terraform provider includes bug fixes and documentation improvements to provide a more consistent experience. The spot market request resource and data source have been updated to avoid unnecessary changes when the order of `facilities` changes for a spot market request, the virtual circuit resource has been updated to reduce the occurrence of API errors due to invalid requests, and the documentation for the `equinix_metal_device` resource has been updated to more accurately describe the `user_ssh_key_ids` and `project_ssh_key_ids` fields.Building microservices using Github Actions
Wamaitha Nyamu shows us microservices in this livestream. We'll discuss how to use IaC to build microservices, why they're more efficient, and the software that makes it all possible. If you want to learn about Terraform, Ansible, Docker, and Github Actions then come join us.Terraform-Provider-Equinix v1.16.0 Release
Equinix Terraform Provider v1.16.0 not only has the ability to create Fabric Cloud Router resources directly, but also layer 2 connections to AWS, GCP, and specific fabric ports in Equinix. Connections to Azure and Oracle via Terraform are coming soon! FCR is a great option for those who want to quickly route between clouds using BGP or static networks without worrying about specific OS, vendor requirements, or advanced configuration. For those who use Network Edge, this Terraform release allows you to disable the default internet connectivity before provisioning specific firewalls (Palo Alto Networks NGFW, Cisco FTDv, and Aviatrix FireNet) just like you can in the console.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
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!
