January 2018 - Atomic Working Group (ARCHIVED)

[atomic-wg] Issue #331: Issue Tracker for F27 release blockers
by Dusty Mabe 28 May '18

28 May '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` This ticket will be used throughout the f27 release to track potential blocker bugs and/or important bugs for the next release. A blocker bug is a bug that we will choose not to release on if it is not fixed. An important bug is a bug that we want fixed but may choose not to block on. **Blocker Bugs** - [BZ#1490505](https://bugzilla.redhat.com/show_bug.cgi?id=1490505) cloud-init fails when calling `xfs_growfs /dev/mapper/atomicos-root` on Fedora Atomic Host **Important Bugs** Over time only the description of this bug will be edited for updates. The comments of this bug will be used like a *changelog* for the description. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/331

3 13

[atomic-wg] Issue #355: Article For F27: Migrating Kubernetes
by Josh Berkus 28 May '18

28 May '18

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` We need an article on how to migrate from built-in kubernetes to system container kubernetes when migrating from F26 to F27. This is our most critical article for the release. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/355

5 12

[atomic-wg] Issue #386: Provide updated examples for composing custom ostrees
by Micah Abbott 13 Apr '18

13 Apr '18

miabbott reported a new issue against the project: `atomic-wg` that you are following: `` We've received requests/complaints from #atomic on Freenode about the lack of up to date documentation for composing custom ostrees. ``` I've been trying to build my own atomic repo using rpm-ostree for the past couple days. I'm using a Fedora 27 workstation to build a repo for Atomic Fedora 27. I've tried adapting multiple instructions found online (most of them very old). Do working instructions exist anywhere for Fedora 27 Atomic? ``` It seems like we could benefit from an updated version of @jasonbrooks blog post for Fedora 27: https://www.projectatomic.io/blog/2014/11/build-your-own-atomic-updates/ And perhaps another edition that covers composing your own F27 Workstation ostree? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/386

3 8

[atomic-wg] Issue #374: go-md2man deployed in osbs can't render tables
by Tomas Tomecek 15 Mar '18

15 Mar '18

ttomecek reported a new issue against the project: `atomic-wg` that you are following: `` Hi, I just tried to build my container image and let osbs generate the `help.1` file. It worked! The only problem I have is that the present version deployed inside infrastructure does not support rendering tables. Which means that this help.md page ``` % tools (1) Container Image Pages % Tomas Tomecek % September 11th, 2017 # NAME tools - container with all the management tools you miss in Atomic Host # DESCRIPTION You find plenty of well-known tools within this container. Here comes the full list: | Package | Summary | Executables | | --------------- | ------------------------------------------------------------------------------------------- | ---------------------------------- | | bash-completion | Programmable completion for Bash | | | bc | GNU's bc (a numeric processing language) and dc (a calculator) | /usr/bin/bc | | | | /usr/bin/dc | | bind-utils | Utilities for querying DNS name servers | /usr/bin/arpaname | ``` is translated to ``` tools (1) September 11th, 2017 tools (1) NAME tools - container with all the management tools you miss in Atomic Host DESCRIPTION You find plenty of well-known tools within this container. Here comes the full list: USAGE You should invoke this container using atomic command: $ atomic run f26/tools ``` (yes, the table is missing) when it should be translated to ``` tools (1) September 11th, 2017 tools (1) NAME tools - container with all the management tools you miss in Atomic Host DESCRIPTION You find plenty of well-known tools within this container. Here comes the full list: ┌────────────────┬────────────────────────────────────────────┬────────────────────────────────────┐ │Package │ Summary │ Executables │ ├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤ │bash-completion │ Programmable completion for Bash │ │ ├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤ │bc │ GNU's bc (a numeric processing language) │ /usr/bin/bc │ │ │ and dc (a calculator) │ │ ├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤ │ │ │ /usr/bin/dc │ ├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤ │bind-utils │ Utilities for querying DNS name servers │ /usr/bin/arpaname │ ``` I used `golang-github-cpuguy83-go-md2man-1.0.7-1.fc28.x86_64` to do that. Would be awesome to have that version deployed. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/374

5 24

[atomic-wg] Issue #413: use python-docker instead of python-docker-py
by Tomas Tomecek 06 Mar '18

06 Mar '18

ttomecek reported a new issue against the project: `atomic-wg` that you are following: `` I opened this page: https://fedoraproject.org/wiki/CI/Tests/stat I was quite shocked, that python-docker-py is on the list. We have renamed the package to python-docker after the big API changes happened in version 2. Right now I'm trying to get rid of python-docker-py. Would it be possible to include python-docker in Atomic Host compose instead of python-docker-py? The package is probably pulled by atomic CLI, but the fact is that on rawhide atomic RPM requires python3-docker: ``` $ rpm -q --requires atomic | grep docker python3-docker >= 1.7.2 ``` RHEL and CentOS still include python-docker-py because no one requested the newest upstream release yet. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/413

4 15

[atomic-wg] Issue #403: Minimal OSTree/ISO image initiative
by Josh Berkus 06 Mar '18

06 Mar '18

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` Currently, the main user story for Fedora Atomic Host is as a container infrastructure web host. The OStree ref and ISOs we maintain work well for this user story, and it leads to certain decisions like keeping docker and atomic CLI in the base image (see https://pagure.io/atomic-wg/issue/360) However, there is a user story we are not satisfying, which is the user who wants a truly minimal install, and is more interested in being able to compose her own ostrees and atomic updates than she is in container orchestration. This is an important user story because we already have demand for it, especially from the IoT sector. The steps to pursue this would be: 1. work with users to refine and specify the requirements for a "minimal" edition 2. identify and recruit contributors to assist with building it 3. create and publicize new minimal ref and associated tools Based on my conversations at conferences, the main requests are these: * reduce the size of the base ostree by stripping things out, preferably to less than 300MB installed. * auto-rollback on rpm-ostree upgrade reboot fail * a complete, well-documented toolchain for building and redistributing custom ostrees, based on either the minimal ref or "from scratch". * support for ARM32 (unlikely at best, but people have asked) `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/403

6 9

[fedora-atomic] PR #107: Remove old python-docker-py library.
by Dusty Mabe 01 Mar '18

01 Mar '18

dustymabe opened a new pull-request against the project: `fedora-atomic` that you are following: `` Remove old python-docker-py library. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/107

2 4

[atomic-wg] Issue #379: Identify users for docker hub auto builds for system containers
by Steve Milner 21 Feb '18

21 Feb '18

smilner reported a new issue against the project: `atomic-wg` that you are following: `` As part of the work to start github->docker hub autobuilds for system containers we will need a GitHub which will give link to a docker hub account. Are there specific accounts already available which would make sense to reuse? Do we need to create accounts specific to auto building for both GitHub and docker hub? I tend to believe we should avoid a specific human account tied to this but instead use a service account. Reference: https://docs.docker.com/docker-hub/builds/ `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/379

3 8

[atomic-wg] Issue #409: no rawhide atomic workstation ostree composes for a month
by Pete Walter 18 Feb '18

18 Feb '18

pwalter reported a new issue against the project: `atomic-wg` that you are following: `` There's an up to date F27 atomic workstation repo at https://dl.fedoraproject.org/pub/ostree/27 , but it seems to be only for F27 and doesn't have any rawhide content. dustymabe pointed me to the older https://kojipkgs.fedoraproject.org/compose/ostree/rawhide/ repo, which however hasn't been updated for a month now. According to https://kojipkgs.fedoraproject.org/compose/ostree/rawhide/refs/heads/fedora… the last timestamp is 2017-12-18 09:27 dustymabe said on irc that rawhide composes must have been failing and asked me to file this ticket. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/409

5 11

[atomic-wg] Issue #411: release: find way to inspect created artifacts to make sure they have correct ostree version
by Dusty Mabe 16 Feb '18

16 Feb '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` As part of a FAH release we go through each architecture to make sure that the qcow that was created has the same ostree version # across them all. This is to prevent us from doing a release with artifacts that have mismatched ostree versions. It would be nice for us to automate this discovery so we don't have to do it by hand. Some options are: - leverage out test systems to report ostree version/commit in the results - somehow get pungi/koji/imagefactory to report the ostree version/commit that was used when creating the image (might be able to do this with icicle) - pull down the images with some script and use guestfish/libguestfs to verify. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/411

3 3

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) January 2018