Join the Conversation

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.

Hello everyone! At Equinix, we are proud to offer a wide range of products and services to help our customers achieve their business goals. From data centers to network solutions, cloud exchange to security services, we have a variety of offerings that can meet your needs. That's why we would love to hear from you! We would like to get an understanding of which of our products you're using and how they're helping you achieve your goals. Whether it's our: Data centers: providing secure and reliable colocation solutions Network solutions: connecting you to a global network of partners and customers Cloud exchange: giving you the ability to easily and securely connect to multiple clouds Security services: protecting your critical business assets and data Interconnection solutions: allowing you to directly connect to the people, places, and things that matter most to your business Equinix Metal: providing on-demand and scalable bare metal infrastructure solutions Network Edge: delivering

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

Can I connect to multiple cloud providers within an Equinix data center?

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. 

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.

Has anyone been able to successfully integrate EMG notifications with google's pub/sub? I have been at this for months and am not successful.Basic path is:EMG event such as port down is triggeredThis event, which is picked up by the python outgoing notifications script located at https://github.com/equinix/messaging-gateway-templates/tree/master/template-python-outgoing-notifications-v1, which I have deployed as a cloud function and scheduled to run every 2 minutes, is then sent to pub/subthe pub/sub notification is sent out as an email notification to my team.Is anyone able to assist?

I use shipment v2 API in playground.URL of my request: https://playgroundapi.equinix.com/colocations/v2/orders/shipmentsJSON data of my request: { "type": "INBOUND", "requestedDateTime": "2023-03-02T10:45:41Z", "cageId": "1234", "details": { "carrier": "OTHER", "carrierName": "New Carrier", "numberOfBoxes": 2, "carrierTrackingNumbers": [ "t1Z294AK92654678989", "t1Z086DK96424456780" ] } } I get two possible responses for this same request:504 gateway time-out error { "fault": { "faultstring": "Gateway Timeout", "detail": { "errorcode": "messaging.adaptors.http.flow.GatewayTimeout" } } } 204 No ContentHowever according to API docs, I should get 201 and the order id.

I am passing JSON for ordering outbound shipments. The JSON is below but its pretty much that same as my inbound JSON which is fine. The issue I am getting with the outbound order is that I am getting this error:   b'[{"errorCode":"EQ-2016010","errorMessage":"One or more properties are invalid","correlationId":"105073684364570","additionalInfo":[{"property":"details.carrierTrackingNumbers","reason":"details.carrierTrackingNumbers should NOT have more than 1 items","value":["123456789", "987654321"]}]}]' My JSON: { "type": "OUTBOUND", "customerReferenceId": "x", "requestedDateTime": "2023-04-12T07:00:00.000Z", "cageId": "x", "details": { "carrier": "FEDEX", "numberOfBoxes": 2, "declaredValue": 1, "declaredValueCurrency": "USD", "carrierTrackingNumbers": [ "123456789", "987654321" ], "shipmentLabelRequired": false } } Just for reference this is my inbound which is working as expe

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.

Hello, I have a question. ## Question.Is there a best practice to get all CIRCUIT,SENSOR data? ## BackgroundWe are developing and operating a monitoring system for current and temperature sensors in a Datacenter. We would like to import data from Smartview into our monitoring system and are considering using the API. We need data for each CIRCUIT and SENSOR, but if we use the following API, we can only get summary data for the specified unit. === e.g. Current (Power_v1) request ❯ curl --request GET \ --url 'https://api.equinix.com/power/v1/current?accountNo={accountNo}&ibx={ibx}&levelType=ibx&levelValue={ibx}' \ --header 'accept: application/json' \ --header 'authorization: Bearer {bearer}' \ --header 'content-type: application/json' Next, we considered how to obtain a list of CIRCUIT,SENSOR from the HierarchyAPI and request one of each. However, we found that the API limits the number of requests to 1,000 per day. We have more than 1,000 CIRCUITs and SENSORs that we want t

I am trying to generate token using this method but in Postman: Access Token using grant_type = client_credentials (Recommended). POST 'https://api.equinix.com/oauth2/v1/token' -H "content-type: application/json" -d '{ "grant_type": "client_credentials", "client_id": "******", "client_secret": "****" }' I have the body set as specified in the link: https://developer.equinix.com/docs?page=/dev-docs/fabric/overview but when I execute the query I get this error: { "errorDomain": "apps-fqa", "errorTitle": "Unable to Process the Request", "errorCode": "S1002", "developerMessage": "Failed to execute the ExtractVariables: extractjsonparams", "errorMessage": "Unable to Process the Request, Please try again later." } I have a client_id and client_sercret generated and have tested it with Terraform. What am I missing?Thanks!

The Billing function in Equinix Customer Portal allows customers to view and manage their billing information related to their Equinix IBX data center deployments. By accessing the Billing History section, customers can view or download detailed information on all the charges and payments associated with their billing account for the past 12 months, including invoices, credit memos, and payments. The Billing History feature provides a high-level summary of all billing transactions, giving customers an overview of their account's financial status. With this information readily available, customers can better manage their billing account and make informed decisions about their Equinix services.Find out more at https://docs.equinix.com/en-us/Content/Billing/billing.htm.

This is the first release of the pulumi-equinix collection, a successor to the pulumi-metal collection. The new release includes Pulumi generated SDKs for various languages (.NET, Python, TypeScript, Java, and Go) that cover not only Metal, but also Network Edge, and Fabric resources. 

This is the first release of metal-python, a generated Python SDK for the Equinix Metal API and successor to our original packet-python. By taking advantage of the OpenAPI spec for the Metal API, this SDK offers far greater API coverage. Advantages over packet-python include support for Metal Gateway, VRF, Interconnection, and more. The Metal Python SDK has already been put to use, backing the new Metal modules in the Ansible Collection for Equinix (ansible-collection-equinix).

Equinix Internet Access is now on the Equinix Developer platform.  Catalog | Developer Platform (equinix.com)

This release is v3.6.0 of the cloud-provider-equinix-metal project, which provides a Kubernetes cloud controller manager for Equinix Metal. It includes 25 changes, the most exciting change being an upgrade path for users to get the latest version of MetalLB. This means better BGP-based network load balancing across their enabled worker nodes via custom resources. A lesser but still important change is that CPEM no longer does a health check on an incorrect service if said service was created in the default namespace. Various other updates were also bundled into this version such as updating Go language dependencies and improving linting for developer code. Check out the CPEM documentation for MetalLB for more details and review a sample migration path provided by MetalLB.

This release of our experimental generated Go SDK for the Equinix Metal API adds support for additionalProperties as required in the OpenAPI v3 specification.  The new support for additionalProperties allows Go SDK clients to access properties that are included in API responses but are not documented in the API spec and improves the compatibility of the generated Go SDK with future API releases.  This release also introduces a default User-Agent header for improved usage metrics.  Finally, this helps transition us from the old Packet packngo SDK! To learn more about our generated Go SDK, visit the equinix-labs/metal-go repo on GitHub.