Clean up references to the Packet platform

Packet is now dead and so we can drop any mentions of it.

Author: dustymabe

Design.md

@@ -230,15 +230,6 @@ Originally discussed in [#68](https://github.com/coreos/fedora-coreos-tracker/is
 - OpenStack environments do not require a cloud agent
 - We will provide any base level of functionality with ignition and coreos-metadata
 
-### Packet:
-
-Originally discussed in [#69](https://github.com/coreos/fedora-coreos-tracker/issues/69).
-
-- On the first boot, Packet requires the machine to phone home to report a successful boot.  This will be [handled by coreos-metadata](https://github.com/coreos/coreos-metadata/issues/120).
-- Packet provides the IPv4 public address via DHCP, allowing a machine to acquire network via standard mechanisms.  However, to obtain a private IPv4 address or a public IPv6 address (on the same interface), networking must be configured using metadata from an HTTP metadata service.  This can be handled by coreos-metadata in the initramfs, but it [may need to learn to configure NetworkManager or nm-state](https://github.com/coreos/fedora-coreos-tracker/issues/111) depending on the outcome of [#24](https://github.com/coreos/fedora-coreos-tracker/issues/24).
-- Packet needs the serial console on x86 to be directed to `ttyS1`, not `ttyS0`, requiring [cloud-specific bootloader configuration](https://github.com/coreos/fedora-coreos-tracker/issues/110).  A different serial console configuration is required on ARM64.
-- On many Linux OSes, Packet sets a randomized root password which is then available from the Packet console for 24 hours.  This allows the serial (SOS) console to be used for interactive debugging.  Container Linux, instead, enables autologin on the console by default.  To avoid surprising users, Fedora CoreOS will do neither.  For interactive console access, users can use Ignition to enable autologin or to set a password on the `core` account, and we'll document how to do that.
-
 ### Open questions:
 
  - What do we do about VMware, which has a very involved and intrusive "agent"?
@@ -275,7 +266,7 @@ This means:
 
 Originally discussed in [#114](https://github.com/coreos/fedora-coreos-tracker/issues/114).
 
-We will not enable autologin on serial or VGA consoles by default, even on platforms (e.g. Azure, DigitalOcean, GCP, Packet) which provide authenticated console access.  Doing so would provide an access vector that could surprise users unfamiliar with their platform's console access mechanism and access control policy.  For users who wish to use the console for debugging, we will provide documentation for using Ignition to enable autologin or to set a user password.
+We will not enable autologin on serial or VGA consoles by default, even on platforms (e.g. Azure, DigitalOcean, GCP) which provide authenticated console access.  Doing so would provide an access vector that could surprise users unfamiliar with their platform's console access mechanism and access control policy.  For users who wish to use the console for debugging, we will provide documentation for using Ignition to enable autologin or to set a user password.
 
 ### Automatically disable SMT when needed to address vulnerabilities
 

PRD.txt

@@ -117,7 +117,7 @@ All artifacts will be downloadable from the getfedora.org website. Similarly, fo
 
 === Delivery Format ===
 
-Artifacts will be delivered as cloud images on Amazon EC2, Azure, DigitalOcean, Google Compute Engine, and Packet; as downloadable images for OpenStack, QEMU, VirtualBox, and VMware; and as ISO images, netboot images, and installable raw images for bare metal systems. We may add other public cloud images and downloadable formats to meet demand or anticipated need.
+Artifacts will be delivered as cloud images on Amazon EC2, Azure, DigitalOcean, and Google Compute Engine; as downloadable images for OpenStack, QEMU, VirtualBox, and VMware; and as ISO images, netboot images, and installable raw images for bare metal systems. We may add other public cloud images and downloadable formats to meet demand or anticipated need.
 
 === Architectures ===
 

metadata/stream/rationale.yaml

@@ -10,8 +10,8 @@ architectures:
     artifacts:
       # Some of these will be useful for many users, such as qemu or
       # openstack. Some will likely only be useful for cloud operators,
-      # such as digitalocean or packet.  Some, such as aws, are useful
-      # for users in special situations.
+      # such as digitalocean.  Some, such as aws, are useful for users
+      # in special situations.
       aliyun:
         release: 30.1.2.3
         formats:
@@ -163,15 +163,6 @@ architectures:
               signature: https://artifacts.example.com/oKooheogobofai8l.qcow2.xz.sig
               sha256: ae41e4649b934ca495991b785e3b0c44298fc1c149afbf4c8996fb924272b855
               uncompressed-sha256: 38acb15d02d5ac0f2a2789602e9df950c380d2799b4bdb59394e4eeabdd3a662
-      packet:
-        release: 30.1.2.3
-        formats:
-          "raw.xz":
-            disk:
-              location: https://artifacts.example.com/Oofohng0xo2phai5.raw.xz
-              signature: https://artifacts.example.com/Oofohng0xo2phai5.raw.xz.sig
-              sha256: e41e4649b934ca495991b7852b85e3b0c44298fc1c149afbf4c8996fb92427a5
-              uncompressed-sha256: 38acb15d02d5ac0f2a2789602e9df950c380d2799b4bdb59394e4eeabdd3a662
       qemu:
         release: 30.1.2.3
         formats:
@@ -266,7 +257,3 @@ architectures:
         # currently recommended image, and its release.
         release: 30.1.2.3
         digest-ref: exampleregistry.io/fcos/fcos@sha256:67a81539946ec0397196c145394553b8e0241acf27b14ae9de43bc56e167f773
-      packet:
-        # Images don't have addressable versions, so an operating system
-        # slug is the best we can do.
-        image: fedora_coreos_stable