Community

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. 

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)

I wanted to share an exciting update for Identity and Access Management

A reliable, fast and easy way to get internet access from the IBX.   Here are some videos that give an overview of the service.  Equinix Internet Videos

What Port Options are Available on Equinix Internet Access (EIA)?

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.

Hi Community!  We posted in January that Equinix is building a new visual online cage tool to make tracking your deployment easier, and the Customer Insights Panel has spoken!Equinix will be including these top 3 important areas of information in the first release of this tool. Main Equinix Contact Action items that require customer attention IBX Cage/Cabinet location Don't miss out on future opportunities to hear first and get exclusive access to new ideas, processes, product releases and more.We're currently seeking feedback on features to include in a new Equinix Fabric capability launching this year – internet access. Sign up today to join the Customer Insights Panel and have your say!  Once your account is activated, you can explore and participate in research activities.

In case you missed it, here is the latest Equinix API Newsletter Release 2023.1

Hey folks,As conference seasons is quickly approaching are there any must-attend conferences that you'll be going to? I plan on going to KubeCon EU, KubeHuddle Toronto, and hopefully some of the DevOps Days conferences (Austin and Chicago, maybe?).If you're going to be at one of those feel free to reach out and we can connect in person.Any other conference or event suggestions? 

We recently published a blog (here) called "How Did My Cloud Bill Get So High?" which focused on choosing the best workload placement based on business value, cost and risks. How have your cloud migrations gone historically? Did you migrate from colocation or something else? What were the best (or worst) parts of your migration? Let us know your stories in the comments! 

Did you hear? Identity and Access Management (IAM) has been implemented for Fabric, Network Edge, and Equinix Precision Time (EPT) users in your account.