@@ -11,10 +11,10 @@ apisections:
1111
1212<!--
1313 Copyright 2020 Joyent, Inc.
14- Copyright 2022 MNX Cloud, Inc.
14+ Copyright 2025 MNX Cloud, Inc.
1515-->
1616
17- # Joyent Hybrid Images
17+ # Triton Hybrid Images
1818
1919This document describes the best practices for HVM image creation such that they
2020are compatible with the QEMU/KVM and bhyve hypervisors on SmartOS.
@@ -27,10 +27,10 @@ The key characteristics of a hybrid image are:
2727 locations in the device tree, perhaps with different model identifiers, serial
2828 numbers. etc.
2929- Must configure networking using the [ mdata
30- protocol] ( https://eng.joyent .com/mdata/protocol.html ) on the second serial
30+ protocol] ( https://eng.tritondatacenter .com/mdata/protocol.html ) on the second serial
3131 port (` ttyS1 ` , ` ttyb ` , ` COM2 ` , etc.).
3232- Should take other actions as described in the [ data
33- dictionary] ( https://eng.joyent .com/mdata/datadict.html ) .
33+ dictionary] ( https://eng.tritondatacenter .com/mdata/datadict.html ) .
3434- Should have an administrative port on the first serial port (` ttyS0 ` , ` ttya ` ,
3535 ` COM1 ` , etc.).
3636- Should use virtio block and network devices.
@@ -57,7 +57,7 @@ The typical hybrid image creation process involves the following steps.
5757 installation. This sanity check likely involves looking for well-known
5858 markers in the log output described above.
59596 . Generate an image, which is comprised of a zfs stream and a
60- [ manifest] ( https://github.com/joyent /sdc-imgapi/blob/master/docs/index.md#image-manifests ) .
60+ [ manifest] ( https://github.com/TritonDataCenter /sdc-imgapi/blob/master/docs/index.md#image-manifests ) .
61617 . Optionally upload to Manta and/or https://updates.tritondatacenter.com .
6262
6363The steps described above are generally handled with automation. Steps 1, 2,
@@ -125,16 +125,16 @@ vmadm start $uuid
125125
126126The following repositories follow the patterns described above.
127127
128- * [mi-centos-hvm](https://github.com/joyent /mi-centos-hvm) for CentOS 6 - 8
129- * [mi-debian-hvm](https://github.com/joyent /mi-debian-hvm) for Debian 8 - 10
128+ * [mi-centos-hvm](https://github.com/TritonDataCenter /mi-centos-hvm) for CentOS 6 - 8
129+ * [mi-debian-hvm](https://github.com/TritonDataCenter /mi-debian-hvm) for Debian 8 - 10
130130
131131Each repo is intended to handle a family of distributions. The mi-centos-hvm
132132repo probably implements the hard parts required for RHEL, Fedora, and other
133133RHEL-derived distributions. Likewise, it should be straight-forward to add
134134support for Ubuntu to mi-debian-hvm.
135135
136- Each of those repositories has this ([eng](https://github.com/joyent /eng)) and
137- [sdc-vmtools](https://github.com/joyent /sdc-vmtools) as subrepos. The eng repo
136+ Each of those repositories has this ([eng](https://github.com/TritonDataCenter /eng)) and
137+ [sdc-vmtools](https://github.com/TritonDataCenter /sdc-vmtools) as subrepos. The eng repo
138138is home to common tools used for building the images and the sdc-vmtools repo
139139is used for things that are added to the image.
140140
@@ -235,7 +235,7 @@ have specialized control over the boot loader, etc., additional arguments can be
235235specified on the command line.
236236
237237A key example of how this is used is in the [CentOS
238- images](https://github.com/joyent /mi-centos-hvm/blob/master/create-image).Rather
238+ images](https://github.com/TritonDataCenter /mi-centos-hvm/blob/master/create-image).Rather
239239than remastering the image to add the appropriate boot options, the installation
240240media is mounted in the host and QEMU is started with options that specify the
241241kernel, initrd, kernel command line, and a secondary CD which contains the
0 commit comments