Cluster-API-Provider-Packet v0.7.0 Release
Version 0.7.0 of cluster-api-provider-packet, introduces metro level support vs facility level in accordance with the soon-to-be updated Metal API. Users ofprevious versions will want to take advantage of this immediately. The basic requirements to upgrade your existing clusters can be found here. Please work with your Equinix support team to determine the best migration path for your architecture. Assistance can also be found in theCommunity Slack andCommunity site. Read more at our Metros Quick Reference and see the facility deprecation announcement. *Please note that if devices are already in the correct metros you’ve specified, no disruption will happen to clusters or their devices. As with any production change, test your changes before applying them to clusters in production. In addition to metro-level support, this release installs the latestcloud-provider-equinix-metal v3.6.1 by default and is built on golang version 1.19 and cluster-api 1.3. The default OS used is Ubuntu 20.04 and kube-vip is updated to v0.5.12 in the kube-vip flavor templates. Lastly, the CI workflow has been refactored with caching removed and updated tests considering cluster-api 1.3 dependencies. See more at the github release here! https://github.com/kubernetes-sigs/cluster-api-provider-packet/releases/tag/v0.7.0OpenShift on Baremetal v0.5.0
A Terraform module that quickly installs OpenShift for use on Equinix Metal. First off, v0.4.0 aligned with thesupport of metros and deprecated the use of facilities; see the announcement here. The default location was changed fromSJC1 to DA, the default size is c3.small vs the previous c2.medium, and Terraform version 1 or higher isrequired. 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 theMigrating 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 firstrelease 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 thethe 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 Pythonis 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.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.Equinix Deploy
Test drive our growing digital services portfolio and deploy the cloud you need in minutes, not months. Try our enhanced self-service capabilities and e-commerce experience to accelerate your journey toward automated infrastructure. The new deploy.equinix.com website makes it easier than ever to try, adopt and scale Equinix digital services with a few simple clicks. Interact with Equinix Fabric, Network Edge, and Metal firsthand to see how our fast growing ‘as a service’ offers dramatically improve your speed to market and application performance with automated, infrastructure at Equinix. Highlights also include live chat 24 x 7 technical support, comprehensive technical guides and documentation and expanded global availability. Visit deploy.equinix.com to try Equinix digital services for yourself.How to Customize an ESXi Configuration with Equinix Metal
In this video, we'll show you how to use the Custom Data feature of Equinix Metal to customize an ESXi instances configuration at deployment time. After some background on how helpful this GitHub repo is with formatting the JSON content, we dive into how to apply it to a new metal deployment. In our example, we deploy an On-Demand System in the Dallas Metro using a VMware VCF ESXi 7.0 operating system. Here is a link to the GitHub repo with documentation and an example of properly formatted custom data JSON content that you can use as a guide for your own deployments.Flatcar: A Cloud Native Take on Linux
A few years ago, the folks behind Flatcar Container Linux made it their business to change that, to give the world a version of Linux that would behave and be managed like a cloud native developer would expect. Today, engineers can configure and deploy Flatcar instances using the same declarative approach they use to create a Kubernetes cluster: by listing their desired configuration details in a YAML doc and then having the OS image automatically installed and configured on as many servers as they would like. Here’s how the Flatcar team does this, with a little bit of help from its friends at Equinix! Read more on Deploy.Equinix.com
