jberkus

Bug Wrassler Release Team Role

Your job for the release is to make sure that bugs (issues) and their related PRs which affect the release are dealt with in a timely fashion. In general, you will be polling bugs, checking status, sending reminders and questions to contributors and SIG leads, and publishing summary reports.

Secondarily, you will be helping improve automation around issue management and release tagging.

How this works depends on where you are in the release cycle. There are five relevant periods where your workload changes:

1. Early Release: between Feature Freeze and a week before Code Slush.

jberkus

Steering Committee Update

Showed list of Steering Committee backlog.

We had a meeting, and the two big items we'd been pushing on hard were:

• votining in the proposals in the bootstrap committee
• how we're going to handle incubator and contrib etc.

jberkus

Demos in the booth
Virtualization Salon
OpenShift Commons
Talks?

Dinner/other team outing?

jberkus

Potential ordering for F27 Blog Posts

Tuesday: Release announcement/summary

Tuesday: 26->27 Migration post

Wednesday: Migrating Kubernetes post

Thursday: Multi-arch (both on blog and on Magazine)

jberkus

FROM fedora:25

MAINTAINER Josh Berkus "josh@agliodbs.com"

LABEL Usage="docker run -d -P --tmpfs /run --tmpfs /tmp -v /sys/fs/cgroup:/sys/fs/cgroup pgadmin4"

ENV container=oci

# install packages
RUN dnf install -y https://download.postgresql.org/pub/repos/yum/9.6/fedora/fedora-25-x86_64/pgdg-fedora96-9.6-3.noarch.rpm && \

jberkus

As an example, let's say that we have a Fedora Atomic host which is on the default ref.  That ostree will now be updated every two weeks, and only every two weeks:

```
-bash-4.3# date
Fri Feb 10 21:05:27 UTC 2017

-bash-4.3# rpm-ostree status
State: idle
Deployments:
● fedora-atomic:fedora-atomic/25/x86_64/docker-host

jberkus

#!/usr/bin/env python

# Usage: download_issues.py owner repo postgres_dsn github_token

# simple script for downloading all issues from the given repository
# requires you to set up an API token with no special permissions
# also requires a PostgreSQL database with the following tables:

"""
create table issues (

jberkus

Nov 22 22:06:57 ip-172-31-36-35.us-west-2.compute.internal oci-systemd-hook[9680]: systemdhook <debug>: Skipping as container command is /usr/local/bin/kube-controller-manager, not init or systemd
Nov 22 22:06:57 ip-172-31-36-35.us-west-2.compute.internal kubelet[8942]: I1122 22:06:57.998626    8942 factory.go:111] Using factory "docker" for container "/system.slice/docker-ba0c74e340d3795cd0d490cbad0b4135
Nov 22 22:06:58 ip-172-31-36-35.us-west-2.compute.internal systemd[1]: libcontainer-9684-systemd-test-default-dependencies.scope: Scope has no PIDs. Refusing.
Nov 22 22:06:58 ip-172-31-36-35.us-west-2.compute.internal systemd[1]: libcontainer-9684-systemd-test-default-dependencies.scope: Scope has no PIDs. Refusing.
Nov 22 22:06:58 ip-172-31-36-35.us-west-2.compute.internal kubelet[8942]: I1122 22:06:58.046995    8942 server.go:608] Event(api.ObjectReference{Kind:"Pod", Namespace:"kube-system", Name:"kube-controller-manager
Nov 22 22:06:58 ip-172-31-36-35.us-west-2.compute.internal kernel: XFS (dm-8): Mounti

jberkus

containers & databases
======================

databases
---------

* postgres
* mysql & mariadb
* oracle
* redis

jberkus

install
reboot
lang en_US.UTF-8
keyboard us
timezone --utc America/Los_Angeles
selinux --enforcing
zerombr
clearpart --all --initlabel
bootloader --location=mbr --boot-drive=sda
reqpart --add-boot