Meet the Product Managers!
Hello Equinix Community, I'm Jantzen Belliston, Sr Manager at Equinix. Today, we're opening a new chapter in our commitment to fostering transparency and community by introducing you to the incredible individuals behind our innovative products. The essence of Equinix has always been a blend of technology and community. We understand that the pulse of any tech-driven organization is its products, and behind those products, there's a team of dedicated, passionate individuals: our Product Managers. This thread offers a unique opportunity for our customers to get to know these dedicated professionals on a personal level. Our product team is thrilled to be a part of this platform, as it offers us a direct channel to engage, share, and grow with all of you. We see the Equinix Community not just as a space for interactions, but as a bridge to understand your needs, address your questions, and co-create the future. Here’s what to anticipate: Personal Introductions: Our Product Managers from various domains will be stepping forward to share about themselves, their roles, and the inspirations behind the products they steer. Behind-the-Scenes Stories: Insights into the ideation, challenges, and milestones of our product journeys – straight from those who live and breathe them. Open Dialogue: We're building a two-way street. Engage directly with our product teams, share your feedback, or ask anything you've ever wondered about our offerings. Sharing Expertise: Expect enlightening discussions, from technological deep dives to evolving market trends, all from the experts behind our product lineup. I invite our vibrant community to dive into these conversations, ask questions, and truly get to know the people who shape the products and services you trust. Warm regards, JantzenCluster-API-Provider-Packet v0.7.0 Release
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 ofprevious 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 theCommunity Slack andCommunity 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 latestcloud-provider-equinix-metal v3.6.1 by default and is built on golang version 1.19 and cluster-api 1.3. The default OS used is Ubuntu 20.04 and kube-vip is updated to v0.5.12 in the kube-vip flavor templates. Lastly, the CI workflow has been refactored with caching removed and updated tests considering cluster-api 1.3 dependencies. See more at the github release here! https://github.com/kubernetes-sigs/cluster-api-provider-packet/releases/tag/v0.7.0"What Is" Series
stevemarturned me onto Equinix's "What is?" series where each article explores a new technology or topic. For example, you may know what iPXE is but did you know that Equinix actually boots up iPXE for every supported operating system of ours? There's a lot to learn, so give these a read. I'll add some of them below: What is an API https://deploy.equinix.com/developers/guides/what-is-api What is Colocation https://deploy.equinix.com/developers/guides/what-is-colocation What is iPXE https://deploy.equinix.com/developers/guides/what-is-ipxe/ What is Kubernetes https://deploy.equinix.com/developers/guides/what-is-kubernetes What is NVMe https://deploy.equinix.com/developers/guides/what-is-nvmeWhat's the difference between Playground, Sandbox, and Production?
You might be deploying on Network Edgetoday to run through Charles_Randall's tutorial. While reading up on Network Edge atDeveloper Platform, then perhaps you're thinking "what's the difference between Playground, Sandbox, and Production?". In short: Playground is a test environment to test Equinix APIs, using static data without integrating within the actual API. Sandbox is a mock test environmentto test Equinix APIs, using synthetic data (not production data)to integrate with Equinix APIs before moving to Production. Production is the live environment.Why do you use Equinix Metal? Why should someone consider using Equinix Metal?
Hello Community! We know that many of you use Equinix Metal for a variety of reasons, from high-performance computing to hybrid cloud connectivity. We would love to hear more about how you are using Equinix Metal and what benefits you have experienced. Whether you are using Equinix Metal for machine learning, data analytics, or to create a hybrid cloud architecture, we want to hear from you. Share your stories and experiences with the community, and help us all learn more about the benefits of Equinix Metal. Here are some questions to consider: What are the main reasons you chose to use Equinix Metal? How has Equinix Metal helped your business or organization? What benefits have you experienced from using Equinix Metal? How has Equinix Metal helped you to achieve your goals? We look forward to hearing from you and learning more about how you are using Equinix Metal. Don't hesitate to share your thoughts and experiences in the comments below. Let's start a conversation!Create Virtual Devices Using Equinix APIs
You can create Virtual Devices using Equinix APIs. Many vendors, including Cisco, Fortinet, Palo Alto Networks, and others, offer firewalls and routers on our platform. Check out our use cases to understand the required steps and the set of APIs you need to create Clusters, SD-WANs, and other Self-Configured devices: https://developer.equinix.com/dev-docs/ne/getting-started/launch-cluster-device https://developer.equinix.com/dev-docs/ne/getting-started/launch-sdwan-device https://developer.equinix.com/dev-docs/ne/getting-started/launch-self-configured-device You could take advantage of the Postman collection listed on the above pages to get the payload to create any device type.
