cgwalters

20160304

Mostly more fighting with OpenStack instances. Played around with the new QEOS7, hit random issues. Tried a bit more to bootstrap OpenShift containerized on OS1 Public, but the lack of DNS was problematic. Realized I had bootstrapping issues trying to build/update a dnsmasq container.

Ended up backing off a multi-node cluster and just set everything to point at one VM for playing around. I/O appears to be really, really slow.

However, I did successfully use the Let's Encrypt Docker image, which worked out quite nicely.

Update: Apparently d-s-s failed because my rootfs was too small, left me with a corrupted pool, had to blow away all of my images after adding a cinder volume.

cgwalters

I'm trying to set up my own OpenShift cluster under aos.verbum.org, running on CentOS Atomic Host, inside an OpenStack cluster.

The containerized install is giving me all of the pain of docker-vs-systemd that we've known about forever.

Spent about an hour trying to track down why my attempts to add Cinder PVs were being rejected. It turns out that there's currently a hard requirement that the hostname match the instance ID in the cloud provider...which is rather annoying, as I have my hostname set to the public version.

cgwalters

The goal here is to create a local mirror of the upstream OSTree repository.

Log into a shell on the host, and run the tools container. This isn't strictly necessary right now as we could use the host's ostree binary too, but in the future the tools container might contain more scripts for things like this. Once we're inside the tools container, we make an unprivileged user, as general best practice. It also shows that OSTree is perfectly happy to mirror/manipulate content as non-root.

cgwalters

From 252613fff3142dc2be7e9a3c47fc9c4488ff75da Mon Sep 17 00:00:00 2001
From: Colin Walters <walters@verbum.org>
Date: Thu, 31 Mar 2016 21:27:24 -0400
Subject: [PATCH 1/2] Demote pytest/coverage to Fedora only

We aren't running the tests on CentOS due to dependency issues (whole
vast swath of Python modules to backport), so add these deps into %if
fedora as well.
---
 python-docker-py.spec | 2 +-

cgwalters

We want to replace Colin's Homu with one more collaboratively maintained in a public OpenShift v3 instance, but for now:

• Edit cfg.toml, add the 3 sections (main, github, travis)
  • openssl rand -hex 20 for secret
• Add cgwalters-bot as collaborator
• Verify that cgwalters can also commit (could possibly instead sign in as cgwalters-bot in firefox)
• Open up webhook page on new repo
• Rsync config file, restart homu
• docker exec -ti homu ssh git@github.com # Work around ssh known_hosts in container

cgwalters

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512

This is an assertion that I am a maintainer of the https://github.com/ostreedev/ostree project. Its most recent release: https://github.com/ostreedev/ostree/releases/tag/v2016.5 is signed by cgwalters, aka https://keybase.io/walters

I assert that I am also the user "walters" on freenode.

cgwalters

On Friday I did: https://ci.centos.org/job/atomic-fedora-ws/

See: https://pagure.io/fork/walters/workstation-ostree-config/commits/f23

Notes on my personal conversion:

Hit grub2.cfg not being updated when doing install-inside-existing Need to detect this case and update both grub.cfg?

Need atomic run centos/tools for strace on flatpak

cgwalters

/* -*- Mode: C; tab-width: 8; indent-tabs-mode: t; c-basic-offset: 8 -*- */
/*
 * Copyright (C) 2001-2003, Ximian, Inc.
 * Copyright (C) 2013 Igalia, S.L.
 */

#ifdef HAVE_CONFIG_H
#include <config.h>
#endif

cgwalters

In Project Atomic we implemented two models to install what one might call "system containers".

There's now "atomic install" and "atomic install --system". I will call the former "atomic install" and the latter "system containers".

projectatomic/atomic#298

These both use:

cgwalters

Release 2017.4

Things are starting to ramp up notably for rpm-ostree.  This
release fixes a number of bugs; for example, installing `mock` on
the host now works.
Issue: https://github.com/projectatomic/rpm-ostree/issues/671

We also fixed a regression related to GPG from 2017.3 that affects
COPR notably.
Issue: https://github.com/projectatomic/rpm-ostree/issues/715