Community

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?

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:

As a customer if I bring my own IP address will Equinix force me to a Dual-Stack or just IPv4-only config?

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

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

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!

I'm interested in submitting an idea to the Equinix Community Ideas page. How do I submit a new idea for consideration?

I saw that the Equinix Community now features Ideas, what is an idea? 

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.

We're making improvements to the Equinix Community login experience! Starting April 6, 2023, you'll see a change to our login experience as we update to the new unified login experience for Equinix portals. Here's what to expect:Consistent look and feel across all Equinix portal login experiences If you use a password manager, you'll need to resubmit your username/password If you encounter an issue with logging into Community, please email community@equinix.com so we can look into it further.   

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.

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.