Community

Charles Meyers, Equinix CEO and president, joins CNBC ‘Squawk on the Street’ to discuss the appetite for use cases with A.I., where Equinix fits into the digital infrastructure landscape, and more.  

The v0.15.0 release of metal-cli begins our migration from the packngo SDK to metal-go. The following subcommands have been updated to use metal-go in this release: init metros operating-systems plan project In addition, all subcommands have gained the --http-header flag, which can be used to add custom HTTP headers to any request that is sent to the Equinix Metal API as part of a metal-cli command execution.

This release of metal-go includes a number of features and improvements to ease the transition from packngo to metal-go. This includes support for include and exclude parameters when creating various Equinix Metal resources, fixed request paths for Metal Gateway API endpoints, and support for the default project ID and default organization ID for individual users.  A number of duplicated models have been consolidated to reduce the need for type conversions when interacting with different API endpoints. In addition, we have added support for the new SOS hostname attribute on devices to reduce reliance on the deprecated facility attribute.This release also includes features that are not available in packngo, such as support for the Invoices API. To learn more, check out the full release notes on GitHub and visit the metal-go page on Equinix Labs.

Equinix Internet Access now offers Fabric users a virtual connection to the internet. The first 3 months of this service are available as a trial period for no charge. During the trial period, you can use the Fabric portal or public API commands to set up and test your internet service with Equinix Fabric for free. This preview of the Equinix Internet Access service with Fabric currently supports a limited configuration that includes only these items: Single port or single connection Fixed billing account (although the preview is available at no charge for the first 3 months of service) 500 Mbps bandwidth commitment Static routing protocol In addition, Equinix will provide: WAN-facing IPv4 /30 addresses Additional IPv4 /27 addresses for customer devices For details on locations and how to onboard, please visit our page at, Internet Connection with Fabric – Free Trial (equinix.com).

 Optimize your multicloud connectivity and gain performance-cost benefits using Equinix Fabric® and Google Cloud.Led by Nick De Cristofaro, Networking Specialist Customer Engineer, Google Cloud and Jun Wei, Senior Principal Solutions Architect, Equinix you’ll learn how to:Leverage the best solutions from multiple cloud providers while avoiding lock-in with one provider Use multiple cloud providers for backup and disaster recovery Meet data sovereignty requirements for on-premises workloads to Google, using Equinix Fabric®  

This is the first official release of our experimental generated Java SDK for the Equinix Metal API. This SDK is generated from the Equinix Metal OpenAPI specification. To learn more about our generated Java SDK, visit the equinix-labs/metal-java repo on GitHub.

Equinix has made the Fortune 500 list by Fortune Magazine for the 3rd consecutive year, solidifying our position as the world's Digital Infrastructure company.

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.

Equinix is being featured in a short film highlighting our goals and perspective on sustainability. The documentary also looks at our alignment with United Nations’ (UN) Sustainable Development Goals (SDGs) and our vision for sustainability and its drivers in the data center industry.  The documentary is part of the Vision 2045 campaign, which is an effort to highlight what multinational companies are doing to help save our planet.   Produced by TBD Media Group and sponsored by The Economist. Check it out!    

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

Version 0.2.0 of the metal-python SDK has been extended to cover all available Metal API resources! The items from v0.1.0 are still included (Metal Gateway, VRF, Interconnection, etc.). This continues to flesh out possibilities for the growing Ansible Collection for Equinix (ansible-collection-equinix).  Tags: DevRel, Engineering, Release, Metal-Python, Metal, Python, SDK 

We're continuing to improve the security process when you visit an IBX. You can now check in and check out with your Equinix Customer Portal (ECP) mobile application: Read the full announcement below:

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 of previous 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 the Community Slack and Community 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 latest cloud-provider-equinix-metal v3.6.1 by default and is built on golang version 1.19 and cluster-api 1.3.

We've released v0.7.2 to comply with the new kubernetes package repositories new key signing process. This new process prevented cluster-api installs from working at all. Please update to v0.7.2 so you can deploy new nodes again.https://github.com/kubernetes-sigs/cluster-api-provider-packet/releases/tag/v0.7.2

Incase you missed it: We have extended the timeline for migration of your Equinix-configured Network Edge Devices to Self-configured Network Edge Devices. This notification is only for Equinix-configured Network Edge Devices; it does not impact Self-configured Network Edge Devices. Read the full announcement below:

In this short Tech Talk, we review how to manage hybrid workloads in a multicloud environment using Azure Arc and Platform Equinix®. Our experts explain how to enable your business to use the power of the cloud regardless of workload location.Led by Jaime Schmidtke, Microsoft Unified Edge Specialist, Global Black Belt and Brian Petit, Equinix Global Solutions Architect, Microsoft AllianceHighlightsLearn how to leverage Azure Arc to enable the central operation and governance of diverse environments. Discover how to simplify the complexity you face when building applications and services in hybrid cloud. Understand how to maintain a secure and robust dedicated connection between on-premise and public cloud. Experience seamless, on-demand, direct access to cloud services such as Microsoft Azure. 

Did you miss the exiting announcement from our identity team? Identity and Access Management (IAM) will be implemented for Fabric, Network Edge, and Equinix Precision Time (EPT) users in your account in the next few weeks. Read the full announcement below:

Equinix Internet Access 2023.3 release is mostly about ordering internet access service instance using a Fabric port, but it also introduces new endpoints for searching and viewing your EIA service instances. For more information, see Equinix Internet Access - 2023.3 Release Notes.

As of v0.2.1, the official Pulumi provider for Equinix is now listed in the Pulumi registry. This version includes a fix for a documentation bug as well as updated documentation that more accurately covers supported languages.

You can now enable your portal users to self-serve notification preferences for IBX Policy Violation Notifications in the Equinix Customer Portal (ECP). See the announcement below:

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 A

The 0.2.0 release of pulumi-equinix includes Pulumi SDKs generated with v1.14.1 of terraform-provider-equinix. This release includes a bug fix that improve usability of single-element set- and list-type fields; deprecation notices for facility-related fields to prepare for the deprecation of facilities in the Equinix Metal platform; and support for key types in Network Edge SSH key resources, which makes it possible to provision Arista routers in Network Edge with Pulumi.

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.

Do you have Network Edge service in the Amsterdam (AM) Metro? If so, make sure you review the service impact document below:

This is our first Java SDK release for the Equinix Fabric v4.6 API Specification built on the OpenAPI Generator.To get started with the Equinix Fabric Java SDK, please refer to the documentation in the project repository. We welcome feedback and suggestions from the developer community on how we can improve this SDK. Please share your feedback and suggestions by opening an issue on GitHub.