Dedicated support for Metal OTW – Join the Beta!
The new support experience for Metal users (Beta) is Live! Metal customers have access for the very first time to an Enterprise-compliant support experience. Key Support Center Beta Features: All-New Support Case System – Easily create Metal support cases with our redesigned case submission system. Unified Case Management – View and manage all your support cases for Equinix products in one place. Seamless Collaboration – Seamlessly invite team members to monitor the status for any Metal support case. Realtime Notifications – Receive email notifications whenever your Metal case has been updated. How do I join the beta? It’s easy, fill out this request form! Who and how to access the beta? For qualifying organizations and users, the new support portal can be accessed in two ways: via a link displayed on the support page of Metal console directly via the URL https://customer-support.equinix.com/ and SSO (same credentials as for Metal) Be sure to check out the Support section of our documentation for more details and let us know how you like it!191Views3likes0CommentsRunning Terraform from a restricted environment
When running Terraform to provision and manage Equinix Fabric, Metal, and Network Edge, you may want to run Terraform from a restricted environment. Network filtering ACLs will need a predictable set of IP ranges to permit. This discussion will help you discover the IP services, ports, and address ranges your Terraform runner environment will need access to. We'll also discuss alternative ways to run Terraform configuration. If your ACLs permit the Terraform runner environment outbound HTTPS (TCP 443) and responses, that would cover everything Terraform needs to start provisioning infrastructure on Equinix. We'll assume we don't have unrestricted access and dig in a little further. Upon running, `terraform init`, Terraform will attempt to use DNS (UDP/TCP 53) services and HTTPS services to download provider plugins, such as the Equinix Terraform provider. The default host for fetching these plugins is registry.terraform.io, managed by Hashicorp. This is the defacto hub for public providers and published Terraform modules, although you may run your own local registry service. DNS for the Terraform registry points to CloudFront, a CDN whose addresses may change. If this presents a problem, there are options to download (or mirror) the necessary plugins in advance and use locally distributed copies. https://developer.hashicorp.com/terraform/cli/plugins Similarly, the DNS service for api.equinix.com, the one base domain that the Terraform Equinix provider will need for API access, resolves to Akamai, another CDN whose addresses may change or depend on where the request originates. As a Terraform configuration grows, you'll likely want to enable SSH access to the Metal and NE nodes being provisioned to automate OS provisioning. The SSH addresses will vary depending on the Metro where services are deployed. One way to ensure that the addresses are predictable in Metal is to provision the servers usingElastic IP addresses. A good follow-up question to this discussion is which ranges are assigned to NE devices and whether these IP addresses can be drawn from a predefined pool like Metal's Elastic IP Addresses. Terraform configurations typically include resources from multiple cloud providers. The node where the configuration is run would need to permit access to the APIs of these other providers. We'll leave the network filters needed by provisioned nodes to another discussion. Depending on your needs, cloud service providers offer managed services for Terraform or OpenTofu (a fork of Terraform persisting the original open-source license). These services can run your Terraform configuration predictably and reliably from a central location. Hashicorp provides the HCP service. https://developer.hashicorp.com/terraform/cloud-docs/run/run-environment Alternatives include: https://spacelift.io/ https://upbound.io https://www.env0.com/ https://www.scalr.com/ You can run similar CI/CD Terraform configuration control planes in your own backend with opensource tools such as: https://argoproj.github.io/cd/ https://www.crossplane.io/ https://docs.tofutf.io/ These SaaS providers or local solutions will also need access to the cloud provider APIs and nodes. With these providers you have full control of the configuration that is run and you can work these into a GitOps workflow. There are even more alternatives outside of the Terraform ecosystem. However, the Terraform ecosystem is your best option for the richest IaC integration experience with Equinix digital services. Equinix provides several Terraform modules to make it easy to get started. That extended ecosystem includes IaC tools that take advantage of the robust Equinix Terraform provider. These tools includePulumi and Crossplane. TLDR; You'll want to expose select DNS, HTTPS, and SSH access from your Terraform runners. What alternative deployment strategies did I miss? What other network restrictions should be considered?570Views3likes0CommentsCalling All Open Source Enthusiasts! Join the Equinix Demo Day!
Hey everyone, are you passionate about the power of open source technology? We’re hosting our first Demo Day of 2024 on Tuesday, May 28th from 1-3:30pm (EDT), and it's a virtual event you won't want to miss! Why Attend? Deep Dive into Open Source: Hear from leading experts in the open-source space who will share their knowledge and insights. Expert Insights: Gain invaluable insights from our esteemed lineup of speakers, including Hannah Aubry, Robert Chacón, Herbert Wolverson, and AmyTobey. They'll share their firsthand experiences, best practices, and visionary ideas to inspire and empower you. Network with Your Community: Connect with fellow open-source enthusiasts and developers. Explore the Latest Trends: Stay ahead of the curve on what's happening in the open-source world. Subscribe to the channel and click the “Notify Me” to get notified when the livestream starts!786Views1like0CommentsVirtual Routing and Forwarding (VRF) is now LIVE!
🚀 Exciting News! You’ve got a simpler way to connect your services deployed across Equinix products. Give Virtual Routing and Forwarding (VRF) a shot and help shape the future of VRF! 🛠️ Configure VRF through the API or UI directly, making connectivity easier than ever! 📚 For more information on what VRF is and how to use it, check out our deploy documentation page: https://deploy.equinix.com/developers/docs/metal/layer2-networking/vrf/ 🗣️ Your feedback matters! Whether it's good or bad, share your thoughts with us. We're eager to hear from you and will use your input to shape the future of VRF. Help us make it even better!1.1KViews2likes0CommentsWork Visit API - issue EQX-161-403
Hey there, I need help! I tried to use API and create a POST REST API request to raise a Work Visit request to Equinix. but unfortunately returned the EQX-161-403 errors. Please kindly help, no idea what this error message means and how to fix this error. Here's the error message frommy PowerShell script: $workvisit = invoke-restmethod -uri "https://api.equinix.com/v1/orders/workvisit" -method POST -Headers $postParams -body $postParamsWVJson -ContentType "application/json" invoke-restmethod : {"errors":[{"code":"EQX-161-403","message":"Contacts (with userName) should be Active and Approved"}],"ticketId":"201030030XXXXXX"} Here's my PowerShell script: $postParams = @{} $postParams.Authorization="Bearer " + $token.access_token $location = invoke-restmethod -uri "https://api.equinix.com/v1/orders/workvisit/locations" -method GET -Headers $postParams -ContentType "application/json" $location2= invoke-restmethod -uri "https://api.equinix.com/v1/retrieve-orders/locations" -method GET -Headers $postParams -ContentType "application/json" $postParamsWV = ` @{"contacts" = @( @{"contactType"="ORDERING"; "userName" = "XXXX@YYY.com"}; @{"contactType"="NOTIFICATION"; "userName" = "XXXX@YYY.com"}; ); "ibxLocation"= @{"ibx" = "SAMPLE"; "cages"= @( @{"cage"="SAMPLE:00:000000"; "accountNumber" = "SAMPLE NUMBER"} )}; "serviceDetails" = @{schedule = @{startDateTime = "2020-05-10T01:00:00Z"; endDateTime = "2020-05-11T02:00:00Z" }; "visitors" =@(@{"firstName" = "John"; "lastName" = "Doe"; "company" = "NN Test"; "email" = "John.Doe@Test.com"; "mobilePhoneCountryCode" = "+81"; "mobilePhone" = "80-1111-2222";}; @{ "userName" = "DDDD@yahoo.com"} ); escortRequired = $false; openCabinet = $false; } } $postParamsWVJson = $postParamsWV|convertto-json -depth 100 $workvisit = invoke-restmethod -uri "https://api.equinix.com/v1/orders/workvisit" -method POST -Headers $postParams -body $postParamsWVJson -ContentType "application/json" Regards, AlanSolved1.8KViews0likes1Commentdelta sandbox<>prod apis
Hi, We noticed that some APIs aren't available in the sandbox but only in production of the Equinix API. Do we have a way to test this? These APIs seem to be available in the playground-zone These works on Prod but not sandbox: list userports list metros list buyer/connections For example: curl -X GET "$url/ecx/v3/l2/common/metros" -H "accept: application/json" -H "Authorization: Bearer $token" {"fault":{"faultstring":"Invalid API call as no apiproduct match found","detail":{"errorcode":"keymanagement.service.InvalidAPICallAsNoApiProductMatchFound"}}}% curl -X GET "$url/ecx/v3/port/userport" -H "accept: application/json" -H "Authorization: Bearer $token" {"fault":{"faultstring":"Invalid API call as no apiproduct match found","detail":{"errorcode":"keymanagement.service.InvalidAPICallAsNoApiProductMatchFound"}}}% curl -X GET "$url/ecx/v3/l2/buyer/connections" -H "accept: application/json" -H "Authorization: Bearer $token" {"fault":{"faultstring":"Invalid API call as no apiproduct match found","detail":{"errorcode":"keymanagement.service.InvalidAPICallAsNoApiProductMatchFound"}}}%1.3KViews0likes0CommentsPower API interval queries
Hello, A few questions for API access and usage. Please can you give me the interval of query for your different levels (power/temperature/etc...). I want to configure a prob who will call your API every x minutes according to your granularity. What is the maximum query per second on the API? Did you have a limitation with token creation (quantity / over time / other)? Are there plans to have the possibility to stream data to an endpoint, I see specific endpoint like GCP/AWS/Azure but what if I want to have my own endpoint? Thanks for your answers,Solved2.8KViews0likes2CommentsNew WorkVisit validation error
We have been using the API /catalog/workvisitv1for a while now and we now have a new validation error that is causing a failure to use the API endpoint: { "error": "Unable to create access request with Equinix. Status code = 400, error = {\"errors\":[{\"code\":\"EQX-161-6119\",\"fields\":[\"\\/attachments\"],\"message\":\"Justification form is mandatory for visiting the IBX : %s. Justification is available to download as part of work visit page in Equinix Customer Portal.\",\"messageParams\":[\"CH3\"]}],\"ticketId\":\"redacted\"}" } This appears to be a new validation error. I haven't seen anything regarding changes to the published API. Do you guys know if this is a bug or a new requirement?1.8KViews0likes1CommentFilter "portName" on connection list not working
Hello, for theendpoint GET https://api.equinix.com/ecx/v3/l2/seller/connections I use it with the profileId filter and I get back many results.I go from page to page to list the connection I have on one specific port. I would like to reduce those calls using the filter portName.However the result is always empty : { "isFirstPage": true, "isLastPage": true, "totalCount": 0, "pageSize": 20, "content": [], "pageNumber": 0 } Have anyone succeeded in getting this to work ? Best regards,5KViews0likes7Comments