Marques Johansson
Marques Johansson
closes #75 closes #72 closes #71
https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gkeonprem_bare_metal_admin_cluster These resources should reduce the amount of script customization is needed. (If that is not the case, there may be benefit in having the Google provider resources included in...
The nodes in this cluster use their public IP addresses for intra-cluster communication. ``` root@k3s-demo-cluster-k3s-cp-aio:~# kubectl get nodes -o wide NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME...
Packet Python is a hand maintained SDK managed by Equinix employees and the community of users. This SDK has been used by Packet and Equinix Metal users and developers for...
We would like to replace the use of the `packet` pypi module with a module that reflects Equinix Metal branding. In doing so, we can not break existing projects that...
Implement Metal Gateway and VRF support. See: https://registry.terraform.io/providers/equinix/equinix/latest/docs/resources/equinix_metal_gateway for example. More info at https://metal.equinix.com/developers/docs/networking/metal-gateway/ API at https://metal.equinix.com/developers/api/#tag/MetalGateways https://registry.terraform.io/providers/equinix/equinix/latest/docs/resources/equinix_metal_vrf
As expressed in https://github.com/packethost/packngo/issues/189#issuecomment-802234842, users would benefit from a common configuration file location and format shared between tools. What does this look like for packet-python? (Following a rename #106) ```...
Equinix Metal offers the ability to provision IP Address ranges, access these reservations by a unique id, list these reservations, and remove these reservations. https://metal.equinix.com/developers/api/ipaddresses/ packet-python should implement these resources....
Implement Connection and Virtual Circuit support. See: * https://metal.equinix.com/developers/docs/networking/fabric/ * https://metal.equinix.com/developers/api/connections/ * https://github.com/packethost/packngo/pull/234
It should now be safe to remove the workaround to https://github.com/packethost/packet-python/issues/78: https://github.com/packethost/packet-python/blob/927684bda1b5092ab14327ac517f5dcad2e7cafd/packet/Manager.py#L222-L232 The function should be returned to its original composition from https://github.com/packethost/packet-python/pull/80. Other changes from #80 can be retained.