Skip to content

Instantly share code, notes, and snippets.

View miabbott's full-sized avatar

Micah Abbott miabbott

View GitHub Profile
@miabbott
miabbott / multiple-ostree-commits.md
Created September 15, 2023 18:27
Working with multiple ostree commits/refs in a single repo

Using a centralized ostree repo

  1. Assume you are using a RHEL 9.2 system with osbuild + nginx installed
  2. Create an empty blueprint selecting "rhel-92" as the distro:
name = "minimal-rhel92"
description = "minimal blueprint for ostree commit"
version = "1.0.0"
## Initial ostree commit
$ composer-cli blueprints show minimal92
name = "minimal92"
description = "minimal rhel for edge blueprint"
version = "1.0.1"
packages = []
modules = []
groups = []
distro = "rhel-92"
@miabbott
miabbott / bonding-testing.txt
Created September 11, 2020 17:19
bonding testing
# virt-install command
virt-install --name rhcos4 --os-variant rhel8.1 --ram 2048 --vcpus 2 --disk size=20 --network network=default,mac=52:54:00:f6:f3:41 --network network=default,mac=52:54:00:de:44:7c --accelerate --cdrom rhcos-43.81.202001072253.0-installer.x86_64.iso
# install options
coreos.inst.install_dev=vda coreos.inst.image_url=http://192.168.124.1:9001/rhcos-43.81.202001101655.0-metal.x86_64.raw.gz coreos.inst.ignition_url=http://192.168.124.1:9001/ignition.json coreos.inst.platform_id=qemu ip=192.168.124.100::192.168.124.1:255.255.255.0:rhcos:bond0:none bond=bond0:enp1s0,enp2s0:mode=active-backup,miimon=100rd.peerdns=0 nameserver=10.5.30.160 nameserver=10.0.128.69
# vadim's build
coreos.inst.install_dev=vda coreos.inst.image_url=http://192.168.124.1:9001/rhcos-43vrutkovs.80.20191015.2-metal.x86_64.raw.gz coreos.inst.ignition_url=http://192.168.124.1:9001/ignition.json coreos.inst.platform_id=qemu ip=192.168.124.100::192.168.124.1:255.255.255.0:rhcos:bond0:none bond=bond0:enp1s0,enp2s0:mode=activ
```
$ sudo curl -LO https://download.fedoraproject.org/pub/fedora/linux/releases/31/Cloud/x86_64/images/Fedora-Cloud-Base-31-1.9.x86_64.raw.xz
$ sudo unxz Fedora-Cloud-Base-31-1.9.x86_64.raw.xz
$ sudo qemu-img convert -O qcow2 Fedora-Cloud-Base-31-1.9.x86_64.raw Fedora-Cloud-Base-31-1.9.x86_64.qcow2
$ sudo qemu-img create -f qcow2 -o backing_file=Fedora-Cloud-Base-31-1.9.x86_64.qcow2 Fedora-Cloud-Base-31-1.9.x86_64.vm0423a.qcow2
$ sudo virt-install --import --name f31 --ram 2048 --vcpus 2 --disk path=/var/lib/libvirt/images/Fedora-Cloud-Base-31-1.9.x86_64.vm0423a.qcow2,format=qcow2,bus=virtio --disk path=/var/lib/libvirt/images/cloud-init.iso,device=cdrom,readonly=on --network bridge=virbr0 --os-type linux --os-variant fedora31 --noautoconsole
@miabbott
miabbott / custom-release-payload.md
Last active April 22, 2020 19:00
Building custom release payload

Building a Custom Release Payload

This shows how to replace the machine-os-content and machine-config-operator

I built the machine-os-content in a devel pipeline and uploaded it to my personal Quay repo.

Likewise, I built machine-config-operator with hack/build-image on my host (uses podman, so can't easily run from a container)

The personal Quay repos need to be publicly available so CI can get to them.

@miabbott
miabbott / gist:1e790139031706c4b47eec10f2870e40
Created January 16, 2020 14:01
42.80.20191002.0 -> 42.81.20191223.0
{
"sources": {
"42.80.20191002.0": "https://releases-rhcos-art.cloud.privileged.psi.redhat.com/storage/releases/rhcos-4.2/42.80.20191002.0/commitmeta.json",
"42.81.20191223.0": "https://releases-rhcos-art.cloud.privileged.psi.redhat.com/storage/releases/rhcos-4.2/42.81.20191223.0/commitmeta.json"
},
"diff": {
"NetworkManager": {
"42.80.20191002.0": "NetworkManager-1.14.0-14.el8.x86_64",
"42.81.20191223.0": "NetworkManager-1.20.0-5.el8_1.x86_64"
},
@miabbott
miabbott / keybase.md
Created October 3, 2018 16:34
Keybase Proof

Keybase proof

I hereby claim:

  • I am miabbott on github.
  • I am rageear (https://keybase.io/rageear) on keybase.
  • I have a public key ASD9D0ci0yXzcwn6NHTsDcqFILk8K1gMHnG4y6HcP4Z-MQo

To claim this, I am signing this object:

@miabbott
miabbott / pm.txt
Created March 3, 2018 19:20
pirate mirror instructions
# cd $(mktemp -d)
# ostree --repo=repo init --mode=archive
# ostree --repo=repo remote add --set gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-27-primary pirate https://f27-atomic-content.ams3.digitaloceanspaces.com/backup/repo/
# ostree --repo=repo pull pirate:fedora/27/x86_64/workstation
@miabbott
miabbott / pirate-mirror.md
Created March 3, 2018 15:44
Creating a 'Pirate' Mirror of Fedora Atomic Workstation Content

In the #atomic channel, I've seen a few complaints about slow speeds when trying to fetch the Fedora Atomic Workstation (FAW) content from the official sources. Especially when connecting from a location in Europe. This is a two-fold problem. First, the official FAW content is located in a datacenter in Phoenix, Arizona in the United States. Second, the FAW content is not mirrored as part of the official Fedora mirror network.

It is discouraging to see users who want to participate in the Project Atomic community being frustrated with slow speeds, so I decided I would investigate how to mirror the content in the European region.