search

crosscloudci / crosscloudci

Integrating, testing, and deploying projects within the CNCF ecosystem. Results published daily to the CNCF CI Dashboard.
https://cncf.ci/#/
Apache License 2.0
84 stars 11 forks source link

[IMPROVEMENT] Update use of Packet to Equinix Metal #228

Open lixuna opened 3 years ago

lixuna commented 3 years ago

Wording borrowed from https://github.com/cncf/cnf-testbed/issues/368

This affects cncf.ci as well

As the title states, Packet has been renamed Equinix Metal

At this time I am not sure if this will have implications for the use of existing APIs, but I know that "Packet" is mentioned a lot throughout documentation.

Another issue on cncf.ci will be to replace the "Packet" logo/button in the Test Environment section to use the Equinix Metal logo and replace the packet.com url to be https://metal.equinix.com/.

TODO:

lixuna commented 3 years ago

See related issue for additional details https://github.com/crosscloudci/ci-dashboard/issues/184

lixuna commented 3 years ago

Note: if the horizontal Equinix Metal logo is not compatible with the dashboard's UI, then a hyperlink for "Equinix Metal™" should also work.

lixuna commented 3 years ago

Here is a stacked Equinix Metal logo

displague commented 3 years ago

Hi!

Here is a similar issue I've responded to regarding branding: https://github.com/crossplane/crossplane.github.io/issues/67

As for the API, https://github.com/packethost/packngo/pull/197 covers the changes. Namely, the API and Metadata endpoints are different.

One other important change is that users new to Equinix Metal (who did not already have a Packet account) may not have immediate access to legacy Packet facilities and plans. The user's API token will show all of the plans and facilities that are available to them.

agentpoyo commented 3 years ago

api.packet.net is found 3 times in crosscloudci/ repositories, where one is a comment of the link, the other is a capacity.sh script which I believe is broken anyways and then in a README file.

https://github.com/search?q=org%3Acrosscloudci+api.packet.net&type=code

It does seem we have a lot of references to the term packet in the code base though for terraform scripts, mostly what seems to be variables. Not sure if we need to change all these references but Terraform hasn't updated it's references to packet yet for the packet resource configs.

https://registry.terraform.io/providers/packethost/packet/latest/docs

I don't see us changing such references until terraform updates their own resource called packet.

agentpoyo commented 3 years ago

metadata.packet.net is found zero times in our crosscloudci repository.

displague commented 3 years ago

I'll let you know when https://github.com/packethost/terraform-provider-packet/pull/288 lands.

On Mon, Nov 16, 2020, 2:32 PM agentpoyo notifications@github.com wrote:

api.packet.net is found 3 times in crosscloudci/ repositories, where one is a comment of the link, the other is a capacity.sh script which I believe is broken anyways and then in a README file.

https://github.com/search?q=org%3Acrosscloudci+api.packet.net&type=code

It does seem we have a lot of references to the term packet in the code base though for terraform scripts, mostly what seems to be variables. Not sure if we need to change all these references but Terraform hasn't updated it's references to packet yet for the packet resource configs.

https://registry.terraform.io/providers/packethost/packet/latest/docs

I don't see us changing such references until terraform updates their own resource called packet.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/crosscloudci/crosscloudci/issues/228#issuecomment-728277277, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACNRVNMFIGZ3UVHZBKJKTLSQF46NANCNFSM4SGF3AGQ .