January 2018 - Atomic Working Group (ARCHIVED)

[atomic-wg] Issue #339: Adding Fedora to AWS Marketplace
by David Duncan 21 Nov '18

21 Nov '18

davdunc reported a new issue against the project: `atomic-wg` that you are following: `` I have made arrangements with Mattdm to host Marketplace AMIs of F27 in the AWS Marketplace. These will be hosted by me as a member of the Fedora community. This allows us to get around certain legal issues that have heretofore prevented the images hosting. * Need Fedora Marketing to assist with writeup for the listing. * TODO F27 submission prior to release date (there is a security audit) Account number for Marketplace deployment is 662243699625. This is legally separate from the FAS managed account. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/339

3 8

[atomic-wg] Issue #396: Write up on using other docker versions on Atomic Host
by Steve Milner 29 Jun '18

29 Jun '18

smilner reported a new issue against the project: `atomic-wg` that you are following: `` A write up (blog, documentation, or something similar) is needed to show folks how to use different versions of the docker runtime on atomic host. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/396

3 5

[atomic-wg] Issue #389: Need links to alternate architectures on getfedora
by Josh Berkus 28 Jun '18

28 Jun '18

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` Currently, https://getfedora.org/en/atomic/download/ has no links to ARM or PPC images of any kind. We need to add these in some form. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/389

4 7

[atomic-wg] Issue #392: update fedmsgs for multi-arch
by Dusty Mabe 27 Jun '18

27 Jun '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` The [two week atomic fedmsgs](https://apps.fedoraproject.org/datagrepper/raw?topic=org.fedorapro… don't include multi-arch information in them. We need to update them so that we more appropriately can release and announce multi-arch content. example from: https://apps.fedoraproject.org/datagrepper/id?id=2017-139f15b3-1d9a-4237-ac… ``` { "username": "mohanboddu", "source_name": "datanommer", "certificate": "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUVZRENDQThtZ0F3SUJBZ0lDQWlnd0RRWUpL\nb1pJaHZjTkFRRUZCUUF3Z2FBeEN6QUpCZ05WQkFZVEFsVlQKTVFzd0NRWURWUVFJRXdKT1F6RVFN\nQTRHQTFVRUJ4TUhVbUZzWldsbmFERVhNQlVHQTFVRUNoTU9SbVZrYjNKaApJRkJ5YjJwbFkzUXhE\nekFOQmdOVkJBc1RCbVpsWkcxelp6RVBNQTBHQTFVRUF4TUdabVZrYlhObk1ROHdEUVlEClZRUXBF\nd1ptWldSdGMyY3hKakFrQmdrcWhraUc5dzBCQ1FFV0YyRmtiV2x1UUdabFpHOXlZWEJ5YjJwbFkz\nUXUKYjNKbk1CNFhEVEUxTVRBd05qSXdORGt3T0ZvWERUSTFNVEF3TXpJd05Ea3dPRm93Z2U0eEN6\nQUpCZ05WQkFZVApBbFZUTVFzd0NRWURWUVFJRXdKT1F6RVFNQTRHQTFVRUJ4TUhVbUZzWldsbmFE\nRVhNQlVHQTFVRUNoTU9SbVZrCmIzSmhJRkJ5YjJwbFkzUXhEekFOQmdOVkJBc1RCbVpsWkcxelp6\nRTJNRFFHQTFVRUF4TXRjbVZzWlc1bkxXSnYKWkdocExXSmhZMnRsYm1Rd01TNXdhSGd5TG1abFpH\nOXlZWEJ5YjJwbFkzUXViM0puTVRZd05BWURWUVFwRXkxeQpaV3hsYm1jdFltOWthR2t0WW1GamEy\nVnVaREF4TG5Cb2VESXVabVZrYjNKaGNISnZhbVZqZEM1dmNtY3hKakFrCkJna3Foa2lHOXcwQkNR\nRVdGMkZrYldsdVFHWmxaRzl5WVhCeWIycGxZM1F1YjNKbk1JR2ZNQTBHQ1NxR1NJYjMKRFFFQkFR\nVUFBNEdOQURDQmlRS0JnUURSekVEdjF5Y3pXRG1jbzBRTyt5ekJ2MlR5Nm1LSkZVMHRsVllITis5\nSgpKWnYyclJzdGs1ampLRTlDNVkyczIyT2RXdWlaMVBCUE5WbXNmQ25aT0dTWFRGRkhiUlhXazFh\nQVRFVVJINTZFCkN1dzIwVkkyTnF3dDJ5MHhBQjB3cU1kNFdNcjlkNDUyL3FpY3ZySzVISDdvQjdP\nbnVHL0lSQS94ZUNoQkZYOTIKWndJREFRQUJvNElCVnpDQ0FWTXdDUVlEVlIwVEJBSXdBREF0Qmds\nZ2hrZ0JodmhDQVEwRUlCWWVSV0Z6ZVMxUwpVMEVnUjJWdVpYSmhkR1ZrSUVObGNuUnBabWxqWVhS\nbE1CMEdBMVVkRGdRV0JCUWVUQWxIWmpTRHpVU1lyQlNTCnAzL2cxd3VVNERDQjFRWURWUjBqQklI\nTk1JSEtnQlJyUUZyNUVnaUpXZWRaNVFYMUFoMEtUbjhVQUtHQnBxU0IKb3pDQm9ERUxNQWtHQTFV\nRUJoTUNWVk14Q3pBSkJnTlZCQWdUQWs1RE1SQXdEZ1lEVlFRSEV3ZFNZV3hsYVdkbwpNUmN3RlFZ\nRFZRUUtFdzVHWldSdmNtRWdVSEp2YW1WamRERVBNQTBHQTFVRUN4TUdabVZrYlhObk1ROHdEUVlE\nClZRUURFd1ptWldSdGMyY3hEekFOQmdOVkJDa1RCbVpsWkcxelp6RW1NQ1FHQ1NxR1NJYjNEUUVK\nQVJZWFlXUnQKYVc1QVptVmtiM0poY0hKdmFtVmpkQzV2Y21lQ0NRRGpVQjVIVHhjZVJUQVRCZ05W\nSFNVRUREQUtCZ2dyQmdFRgpCUWNEQWpBTEJnTlZIUThFQkFNQ0I0QXdEUVlKS29aSWh2Y05BUUVG\nQlFBRGdZRUFTUXdKUzd2YlNCcm0rVGszCkNEMVI1V3l4SWRLTTI2K1dXVHNoRC9wRlh2aUg4TVY0\naVlQMC9PTzcxaDZhbVRvQlZEdS95TTZJK3JLVmxTc0IKSmNwWS81Q0hFZ0U0V0YydUNUSmtJajVh\nSkwyZndRN1UvNVorWmNGVHFEcWhWYmNwbmkxN3BhTnRrLzlYU09McApScGhSYzB6a3hXeXBEdkVH\ncEFBZVd6ZWZGRlE9Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K\n", "i": 2, "timestamp": 1512060519.0, "msg_id": "2017-139f15b3-1d9a-4237-ac70-b3154a214807", "crypto": "x509", "topic": "org.fedoraproject.prod.releng.atomic.twoweek.complete", "headers": {}, "signature": "XQPKdCcNf2wn9uHiu9RGPt/Vm67bYTkHr5Cq9vhgqLeJO0pGWcXc1dUWcZrhmdG45jvOfLGD8zHR\nRmgXaurMC7T9XiEm1Y/O95K3YcWAxD9x2wysvV0rEnd4OyZPchfclAkOj0Mfd4pg1rn//iFmQcSH\nzcu8c+x8fPyZySYuzdk=\n", "source_version": "0.8.1", "msg": { "atomic_qcow2": { "release": "27", "image_url": "/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/CloudImages/x86_64/images/Fedora-Atomic-27-20171129.0.x86_64.qcow2", "image_name": "Fedora-Atomic-27-20171129.0.x86_64.qcow2", "compose_id": "Fedora-Atomic-27-20171129.0", "name": "Fedora-Atomic-27-20171129.0." }, "atomic_vagrant_libvirt": { "release": "27", "image_url": "/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20171129.0.x86_64.vagrant-libvirt.box", "image_name": "Fedora-Atomic-Vagrant-27-20171129.0.x86_64.vagrant-libvirt.box", "compose_id": "Fedora-Atomic-27-20171129.0", "name": "Fedora-Atomic-Vagrant-27-20171129.0." }, "atomic_raw": { "release": "27", "image_url": "/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/CloudImages/x86_64/images/Fedora-Atomic-27-20171129.0.x86_64.raw.xz", "image_name": "Fedora-Atomic-27-20171129.0.x86_64.raw.xz", "compose_id": "Fedora-Atomic-27-20171129.0", "name": "Fedora-Atomic-27-20171129.0." }, "atomic_vagrant_virtualbox": { "release": "27", "image_url": "/pub/alt/atomic/stable/Fedora-Atomic-27-20171129.0/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-20171129.0.x86_64.vagrant-virtualbox.box", "image_name": "Fedora-Atomic-Vagrant-27-20171129.0.x86_64.vagrant-virtualbox.box", "compose_id": "Fedora-Atomic-27-20171129.0", "name": "Fedora-Atomic-Vagrant-27-20171129.0." } } } ``` `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/392

4 20

[atomic-wg] Issue #354: help.md file for each container
by Petr Hracek 08 Jun '18

08 Jun '18

phracek reported a new issue against the project: `atomic-wg` that you are following: `` I thinks each container should provide to user some help page. Fedora has requirement for providing such file https://fedoraproject.org/wiki/Container:Guidelines#Help_File The help.md file should contain some required fields like: - image name - maintainer - name - description - usage - if container uses environment variables then section ENVIRONMENT VARIABLES - if container exposes ports then also section SECURITY IMPLICATION e.g. memcached help.md ~~~ % MEMCACHED(1) Container Image Pages % Petr Hracek % February 6, 2017 # NAME memcached - Memcached is a high-performance, distributed memory object caching system # DESCRIPTION Memcached is a high-performance, distributed memory object caching system, generic in nature, but intended for use in speeding up dynamic web applications by alleviating database load. The container itself consists of: - fedora/f26 base image - memcached RPM package Files added to the container during docker build include: /files/memcached.sh # USAGE To get the memcached container image on your local system, run the following: docker pull docker.io/modularitycontainers/memcached # ENVIRONMENT VARIABLES The image recognizes the following environment variables that you can set during initialization be passing `-e VAR=VALUE` to the Docker run command. | Variable name | Description | | :----------------------- | ----------------------------------------------------------- | | `MEMCACHED_DEBUG_MODE` | Increases verbosity for server and client. Parameter is -vv | | `MEMCACHED_CACHE_SIZE` | Sets the size of RAM to use for item storage (in megabytes) | | `MEMCACHED_CONNECTIONS` | The max simultaneous connections; default is 1024 | | `MEMCACHED_THREADS` | Sets number of threads to use to process incoming requests | # SECURITY IMPLICATIONS Lists of security-related attributes that are opened to the host. -p 11211:11211 Opens container port 11211 and maps it to the same port on the host. # SEE ALSO Memcached page <https://memcached.org/> ~~~ `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/354

8 36

[atomic-wg] Issue #399: Document how to make a system container from start to finish
by Steve Milner 08 Jun '18

08 Jun '18

smilner reported a new issue against the project: `atomic-wg` that you are following: `` It was brought up in a meeting that our current blog posts are a bit scattered and may not be enough for someone looking to make a system container for the very first time. A start to finish how to is needed to help guide people in creating system containers. - https://github.com/projectatomic/atomic-system-containers/blob/master/READM… - https://github.com/projectatomic/atomic-system-containers/blob/master/FILES… - https://www.projectatomic.io/blog/2017/06/creating-system-containers/ - www.projectatomic.io/blog/2016/09/intro-to-system-containers/ /cc @markllama `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/399

3 9

[atomic-wg] Issue #364: Article for F27: Running Fedora images on Microsoft Azure
by Dusty Mabe 29 May '18

29 May '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` We have done some work to get our images booting properly on MSFT azure. Brent has volunteered to write a blog post (draft [here](https://gist.github.com/baude/cc8fccc51eacfc0964cd14afc202df5c)) We'll try to publish this on fed mag. I'll work with fedmag team to get this published. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/364

4 7

[atomic-wg] Issue #405: blog post/email about ostree HTTP2 issues and work arounds for F27 AH/AW
by Micah Abbott 28 May '18

28 May '18

miabbott reported a new issue against the project: `atomic-wg` that you are following: `` I was the latest victim of issues pulling updates via HTTP2 when using `rpm-ostree upgrade` on my F27AW system. The problem is covered here: https://github.com/ostreedev/ostree/issues/1362 Thankfully, the latest release of `ostree` (2017.15) contains the fix (workaround?) for the issue, but users are going to need to install that fixed version before they'll be able to successfully update their Atomic Host/Workstations. The ol' chicken vs egg problem. We should publicize this issue via a blog post or email to `atomic-devel` (or both) because it has the potential to impact a lot of users. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/405

5 18

[atomic-wg] Issue #375: Article for F27: The new Atomic Workstation
by Josh Berkus 28 May '18

28 May '18

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` Since we're now offering regular updates for Atomic Workstation, it's time for a detailed blog post about installing it and running it. Maybe even a series. Ideal would be a summary article in Fedora Magazine, and a detailed series over time on the Atomic blog. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/375

6 9

[atomic-wg] Issue #366: Blog post covering AWS MP availability for F27
by David Duncan 28 May '18

28 May '18

davdunc reported a new issue against the project: `atomic-wg` that you are following: `` blog post announcing the availability of F27 Atomic in the AWS Marketplace. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/366

4 4

[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

[atomic-wg] Issue #388: Add Fedora AMIs to govcloud region.
by David Duncan 08 Feb '18

08 Feb '18

davdunc reported a new issue against the project: `atomic-wg` that you are following: `` There are currently no Fedora images in the AWS govcloud region. To publish images in the govcloud, we must follow the ITAR guidelines. The AWS GovCloud (United States) region supports United States International Traffic in Arms Regulations (ITAR) compliance. International Traffic in Arms Regulations (ITAR) controls the export of defense-related articles and states that no non-US person can have physical or logical access to the articles stored in the ITAR environment. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/388

2 2

[atomic-wg] Issue #394: Write up on using other docker versions on Atomic Host
by Steve Milner 07 Feb '18

07 Feb '18

smilner reported a new issue against the project: `atomic-wg` that you are following: `` We need to have documentation showing how to use other docker versions on Atomic Host in the event the admin wishes to use an alternate docker runtime. References: - https://jebpages.com/2017/11/08/install-docker-ce-on-fedora-atomic-host-if-… `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/394

4 12

[atomic-wg] Issue #407: cri-o in Atomic Host
by Steve Milner 07 Feb '18

07 Feb '18

smilner reported a new issue against the project: `atomic-wg` that you are following: `` In [this ticket](https://pagure.io/atomic-wg/issue/360) is was decided to continue to keep ``docker`` in the base. However, we want to make sure that people have the option to use ``cri-o`` as their container runtime if they would like to do so (and possibly other runtimes in the future). For consistency it would seem ``cri-o`` should be added to base as well but this would increase the size. However, we already have system containers for both ``cri-o`` and ``docker``. How can we provide a good ``cri-o`` experience for our Atomic Host user base keeping in mind that ``docker`` will be part of the base already? /cc @dwalsh @mpatel `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/407

3 7

[atomic-wg] Issue #406: Create buildah container for Atomic Host usage
by Steve Milner 07 Feb '18

07 Feb '18

smilner reported a new issue against the project: `atomic-wg` that you are following: `` We need a ``buildah`` image which can be used on Atomic Host. **Related**: - https://pagure.io/atomic-wg/issue/402 - https://github.com/projectatomic/buildah/issues/158 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/406

3 6

[atomic-wg] Issue #351: atomic working group talks/sessions for devconf.cz
by Dusty Mabe 01 Feb '18

01 Feb '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` Let's strategize on what sessions we want to submit for devconf this year. Please update the description with a bulleted list of sessions we'd like to submit as well as the status for each session. For example: - Atomic Host 101 Hands On Lab - Not Yet Submitted - Dusty Mabe Please add a comment anytime you update the description with a changelog of what you changed in the description. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/351

6 11

[atomic-wg] Issue #382: growpart seems to fail on aarch64 atomic host cloud image
by Dusty Mabe 01 Feb '18

01 Feb '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` I'm not sure why but would like others to confirm/deny that it happens for them with [the image from the first f27 release](https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-…. ``` [root@cloudhost ~]# rpm-ostree status State: idle Deployments: ● fedora-atomic:fedora/27/aarch64/atomic-host Version: 27.1 (2017-11-10 12:02:44) Commit: da1bd08012699a0aacaa11481d3ed617477858aab0f2ea7300168ce106202255 GPGSignature: Valid signature by 860E19B0AFA800A1751881A6F55E7430F5282EE4 [root@cloudhost ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 40G 0 disk ├─sda1 8:1 0 200M 0 part /boot/efi ├─sda2 8:2 0 1G 0 part /boot └─sda3 8:3 0 4.8G 0 part └─atomicos-root 253:0 0 4.8G 0 lvm /sysroot sdb 8:16 0 368K 0 disk sdc 8:32 0 10G 0 disk [root@cloudhost ~]# growpart /dev/sda 3 GPT PMBR size mismatch (12582911 != 83886079) will be corrected by w(rite). attempt to resize /dev/sda failed. sfdisk output below: | GPT PMBR size mismatch (12582911 != 83886079) will be corrected by w(rite). | Backup files: | PMBR (offset 0, size 512): /tmp/growpart.gpxB0y/backup-sda-0x00000000.bak | GPT Header (offset 512, size 512): /tmp/growpart.gpxB0y/backup-sda-0x00000200.bak | GPT Entries (offset 1024, size 16384): /tmp/growpart.gpxB0y/backup-sda-0x00000400.bak | | Disk /dev/sda: 40 GiB, 42949672960 bytes, 83886080 sectors | Units: sectors of 1 * 512 = 512 bytes | Sector size (logical/physical): 512 bytes / 512 bytes | I/O size (minimum/optimal): 512 bytes / 512 bytes | Disklabel type: gpt | Disk identifier: 5B1DEB7C-8134-464C-8767-0883E53D8B64 | | Old situation: | | Device Start End Sectors Size Type | /dev/sda1 2048 411647 409600 200M EFI System | /dev/sda2 411648 2508799 2097152 1G Linux filesystem | /dev/sda3 2508800 12580863 10072064 4.8G Linux LVM | | >>> Script header accepted. | >>> Script header accepted. | >>> Script header accepted. | >>> Script header accepted. | >>> Script header accepted. | >>> Script header accepted. | >>> Created a new GPT disklabel (GUID: 5B1DEB7C-8134-464C-8767-0883E53D8B64). | /dev/sda1: Created a new partition 1 of type 'EFI System' and of size 200 MiB. | Partition #1 contains a vfat signature. | /dev/sda2: Created a new partition 2 of type 'Linux filesystem' and of size 1 GiB. | Partition #2 contains a ext4 signature. | /dev/sda3: The last usable GPT sector is 12582878, but 83886079 is requested. | Failed to add #3 partition: Invalid argument | Leaving. | FAILED: failed to resize ***** WARNING: Resize failed, attempting to revert ****** 512+0 records in 512+0 records out 512 bytes copied, 0.0930597 s, 5.5 kB/s ***** Appears to have gone OK **** ``` `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/382

2 8

[atomic-wg] Issue #412: aarch64 qcow won't boot when installed from testing tree
by Dusty Mabe 01 Feb '18

01 Feb '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` The updates tree works fine. The testing tree yields a non-bootable machine with the following message after passing the grub menu: ``` error: failed to create kernel parameters. Failed to boot both default and fallback entries. Press any key to continue... ``` After trying again I see: ``` error: failed to install/update FDT. Press any key to continue... ``` The current difference between the updates and testing aarch64 trees is: ``` ostree diff commit old: 2f78eaf5c843a3a8c03b21ba9db41073864e8a6b941679a126ac27b910fe66dc ostree diff commit new: 40a4fdfb17242b97bffb1da84c127f60131ca49c1705a407e327ffe32357c39d Upgraded: NetworkManager 1:1.8.4-7.fc27 -> 1:1.8.6-1.fc27 NetworkManager-libnm 1:1.8.4-7.fc27 -> 1:1.8.6-1.fc27 NetworkManager-team 1:1.8.4-7.fc27 -> 1:1.8.6-1.fc27 cloud-utils-growpart 0.27-18.fc27 -> 0.30-1.fc27 criu 3.6-1.fc27 -> 3.7-3.fc27 glib2 2.54.2-1.fc27 -> 2.54.3-2.fc27 glibc 2.26-21.fc27 -> 2.26-24.fc27 glibc-all-langpacks 2.26-21.fc27 -> 2.26-24.fc27 glibc-common 2.26-21.fc27 -> 2.26-24.fc27 gnutls 3.5.16-4.fc27 -> 3.5.17-1.fc27 grub2-common 1:2.02-19.fc27 -> 1:2.02-21.fc27 grub2-efi-aa64 1:2.02-19.fc27 -> 1:2.02-21.fc27 grub2-tools 1:2.02-19.fc27 -> 1:2.02-21.fc27 grub2-tools-extra 1:2.02-19.fc27 -> 1:2.02-21.fc27 grub2-tools-minimal 1:2.02-19.fc27 -> 1:2.02-21.fc27 libassuan 2.4.3-6.fc27 -> 2.5.1-1.fc27 libcrypt-nss 2.26-21.fc27 -> 2.26-24.fc27 libgcrypt 1.8.1-3.fc27 -> 1.8.2-1.fc27 libtasn1 4.12-3.fc27 -> 4.13-1.fc27 oci-register-machine 0-5.12.git3c01f0b.fc27 -> 0-5.13.git66691c3.fc27 ostree 2017.15-1.fc27 -> 2018.1-1.fc27 ostree-grub2 2017.15-1.fc27 -> 2018.1-1.fc27 ostree-libs 2017.15-1.fc27 -> 2018.1-1.fc27 python3 3.6.3-2.fc27 -> 3.6.4-3.fc27 python3-libs 3.6.3-2.fc27 -> 3.6.4-3.fc27 rpm-ostree 2017.11-1.fc27 -> 2018.1-1.fc27 rpm-ostree-libs 2017.11-1.fc27 -> 2018.1-1.fc27 sed 4.4-3.fc27 -> 4.4-4.fc27 timedatex 0.4-5.fc27 -> 0.5-2.fc27 vim-minimal 2:8.0.1427-1.fc27 -> 2:8.0.1428-3.fc27 Removed: python-rhsm-certificates-1.20.1-3.fc27.aarch64 Added: gdbm-devel-1:1.13-6.fc27.aarch64 subscription-manager-rhsm-certificates-1.21.1-1.fc27.aarch64 ``` I suspect grub is the problem but it will need more testing. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/412

2 6

[atomic-wg] Issue #349: evaluate atomic-ci repo
by Dennis Gilmore 01 Feb '18

01 Feb '18

ausil reported a new issue against the project: `atomic-wg` that you are following: `` @releng had setup a atomic-ci tree based on the rawhide buildroot to enable a place for quick availability to test rawhide builds. per https://pagure.io/releng/pull-request/7094 it had been broken for the last 3 months. I would like for it to be evaluated and either be something cared about and used, setting up automated testing, or something we nuke from orbit due to no longer needing to be used. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/349

4 6

[atomic-wg] Issue #372: proposal to include firewalld in atomic host
by Dusty Mabe 01 Feb '18

01 Feb '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` I started [a thread](https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-April/msg00022.html) some time ago on including firewalld in atomic host. I don't believe we received any major objections there so I'm going to propose we move forward with including it in the host. Some highlights from the mail thread: - good for new users since docker adds iptables rules dynamically it's really hard to properly get an iptables config that accurately reflects the rules you want to add without including the dynamic rules docker adds. Also if you do get a config that works and apply it while the system is running then you lost the dynamic rules docker added. - good for openshift origin / kubernetes From @jdetiber : *The iptables-based management that is done in openshift-ansible has always been a hack that was only meant to be a stopgap until firewalld was fully supported up and down the entire stack. There are way too many edge cases that could cause issues with the create/save/restore process. We tried to limit those by using a dedicated chain for openshift-ansible rules, but having another process modify rules without using '-w' or other modifications to the firewall could inadvertently be persisted with the iptables-save.* - make sure we avoid the default zones/policies from firewalld from ben breard on list: if we include it we would want to *clean up the absurd default zones & policies and have something relevant for AH out of the box* `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/372

12 29

[atomic-wg] Issue #345: 20171003 ISO does not boot on minnowboard
by Josh Berkus 01 Feb '18

01 Feb '18

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` 1. wrote Fedora-Atomic-ostree-x86_64-26-20171003.0.iso to usb key (used in prior tests) 2. ran kickstart install of Atomic using my standard f26 kickstart 3. install ran 4. On rebook, system goes through bootup messages and dmesg for around 20 seconds, then without warning reboots. This cycle continues as long as I let it (I counted 5 cycles, then turned it off). 5. Tested with a new USB key and a different minnowboard. Same result. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/345

4 16

[atomic-wg] Issue #415: history incorrect for FAH 27
by Colin Walters 31 Jan '18

31 Jan '18

walters reported a new issue against the project: `atomic-wg` that you are following: `` ``` $ ostree pull --depth 50 --commit-metadata-only fedora-atomic:fedora/27/x86_64/atomic-host $ ostree log fedora-atomic:fedora/27/x86_64/atomic-host | tail -20 Date: 2018-01-16 16:35:15 +0000 Version: 27.60 (no subject) commit d9ec96a8ed7ac4a7c97e5e464953c1b0a3da6bb15b99121fc104a53f82ba5c52 Date: 2018-01-15 16:28:32 +0000 Version: 27.59 (no subject) commit 460b88235ea65d6f511edd9ff56e135a0960f7c5a6f1afb1b00a870468702f8c Date: 2018-01-13 22:45:43 +0000 Version: 27.58 (no subject) commit 5bb743ca42f936f7c5ae5aa475153a6d2ce3f44ce363f5fc63233e9b58dfa55c Date: 2018-01-12 14:09:32 +0000 Version: 27.57 (no subject) << History beyond this commit not fetched >> ``` This looks broken - we're only supposed to have promoted release commits on the branch right? Did somehow the prod ref get pointed to updates? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/415

2 4

[atomic-wg] PR #416: meeting-people.txt: adding myself
by Giuseppe Scrivano 31 Jan '18

31 Jan '18

gscrivano opened a new pull-request against the project: `atomic-wg` that you are following: `` meeting-people.txt: adding myself `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/pull-request/416

2 3

Fedora Atomic WG Meeting Minutes 2018-01-31
by Dusty Mabe 31 Jan '18

31 Jan '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-01-31/fedora_atomic… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-01-31/fedora_atomic… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by dustymabe at 16:30:56 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-01-31/fedora_atomic… . Meeting summary - --------------- * roll call (dustymabe, 16:31:02) * previous meeting action items (dustymabe, 16:34:40) * devconfcz (dustymabe, 16:36:36) * devconfcz this past weekend in brno; we had a lot of interest and talk about atomic host/workstation and the other projects in the atomic ecosystem. colin started a document to link to related talks: https://public.etherpad-mozilla.org/p/devconf-atomic-talks (dustymabe, 16:37:48) * this weeks container release (dustymabe, 16:44:04) * open floor (dustymabe, 16:49:53) * prepared a self-contained change proposal which includes having FAH on s390x in Fedora 28. This should help to get requried changes done in F28 timeframe (ksinny, 16:52:27) * LINK: https://fedoraproject.org/wiki/Changes/Atomic_Cloud_and_Docker_images_for_s… (ksinny, 16:52:29) Meeting ended at 17:01:09 UTC. Action Items - ------------ Action Items, by person - ----------------------- * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * dustymabe (57) * ashcrow (15) * zodbot (13) * jlebon (9) * maxamillion (9) * lorbus (7) * jbrooks (7) * walters (6) * ksinny (5) * rubao (3) * kushal (1) * sanja (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlpyAwsACgkQMwLb1zlS 5nGTng//ZX0JKpXsvRizvwVQdUaBcumu2XhsgB6wFKyuOu71hGFANFuXBCF7HJDj HxCaVSKLP5hqtNTZO0/gYFwAk1WOlxu0ga3uiIVHQHd2GNJ8qGmHRzCT5ngBA0Eo umr77SiWd5PezdmyU+/KC9tCD4srOQTbwDmDrf8bedJgAHp+S1NKKvsQT5NjRX86 F1p/D1S7VyRd1m1Aa96GkSPqvmh/sdi4jZV+IcmfqOLFKc3I8Rd2BRfXvI0Udm1T 51B1pJc1Dnn4JM6wntlT38p4YxiZHBekpFcGadhTGnSdJpP3JUTW5rMH2dkEmnz2 C3leo9Vw9cq1wKj7Mhs28szU8ABXXVKXz4+s558X/8OqLD4kv3NdLhvfLRE28KI/ I2TZmMyRm8RIFjjPKNG8mI1JlQ5psggCgBAD9nJaoiTFX9j7/wh2ZCwpTuUDVX+s 2kkk1ZJncouQ1/xZq+Ft9p6MGTbW3B15Ix9AnwQu8bLuqn7IDMajPHgRWnqUw8eI wnv6c0w/ipbpLznk1hynTMiwHDi1JKFNBA/hHFrzECjUghX8XsGvwcHrviqOpKEA zZpwLpANgnD8iY+fZhZ7HTmtTrHQkGUzCO2SQneT3E6i95o4+u0jvshnyAfsvSqo N3ePN2zUSapiUndFtaylJYVq/OdNUqQgCfW2RFe3qgIeWfJi9iU= =Sqfi -----END PGP SIGNATURE-----

1 0

[Fedocal] Reminder meeting : Atomic Working Group Weekly Meeting
by dusty＠dustymabe.com 30 Jan '18

30 Jan '18

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2018-01-31 from 16:30:00 to 17:30:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: This is the meeting for the Fedora Atomic Working Group. We typically go over previous meeting action items and then cover all tickets with the meeting keyword: https://pagure.io/atomic-wg/issues?status=Open&tags=meeting More information available at: [https://fedoraproject.org/wiki/Atomic_WG#Meetings](https://fedoraproject.or… Source: https://apps.fedoraproject.org/calendar/meeting/6952/

1 0

No Atomic Working Group meeting today
by Dusty Mabe 24 Jan '18

24 Jan '18

1 0

[atomic-wg] Issue #414: enable installing with gpg commit verification enabled
by Dusty Mabe 23 Jan '18

23 Jan '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` If we want to install an atomic host via anaconda we currently don't have any good way of telling it where the keyfile is using the `ostreesetup` line that is supported by anaconda. We need to enhance anaconda so that we can provide this information to ostree and enable commit verification. See related issue in anaconda that is an RFE for a feature that would help us enable this. - https://github.com/rhinstaller/pykickstart/issues/133 We would also need to verify the keyfiles are installed in the media and can be used during install. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/414

1 0

[Fedocal] Reminder meeting : Atomic Working Group Weekly Meeting
by dusty＠dustymabe.com 23 Jan '18

23 Jan '18

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2018-01-24 from 16:30:00 to 17:30:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: This is the meeting for the Fedora Atomic Working Group. We typically go over previous meeting action items and then cover all tickets with the meeting keyword: https://pagure.io/atomic-wg/issues?status=Open&tags=meeting More information available at: [https://fedoraproject.org/wiki/Atomic_WG#Meetings](https://fedoraproject.or… Source: https://apps.fedoraproject.org/calendar/meeting/6952/

1 0

[atomic-wg] Issue #385: Installer doesn't match Fedora Website
by Andreas Nilsson 22 Jan '18

22 Jan '18

andreasn reported a new issue against the project: `atomic-wg` that you are following: `` The website says "Fedora Atomic", but the uses branding that says "Fedora Cloud" <!!image> `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/385

3 10

[atomic-wg] Issue #410: Move AutoCloud to Fedora CI infrastructure
by Dusty Mabe 19 Jan '18

19 Jan '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` Some time ago [we determined](https://pagure.io/atomic-wg/issue/361#comment-473329) the future of testing for Atomic would not be rooted in AutoCloud. We need to migrate the features of autocloud to the new FedoraCI infra. This will probably take some time, but we'll use this ticket to track work related to it. The first item up is creating some documentation on how we can do compose based testing in FedoraCI. - https://pagure.io/fedora-ci/AtomicCi/issue/77 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/410

1 0

[atomic-wg] Issue #358: Article For F27: Cockpit on F27
by Josh Berkus 18 Jan '18

18 Jan '18

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` Article Title: Managing Fedora 27 Atomic with Cockpit Deadline: December 1 Publication: Project Atomic Blog OR Fedora Community Blog Priority: Nice To Have Would be great to have a blog post, with pictures/videos, showing how to manage some of Atomic's particular capabilities (containers, ostree layers, etc.) with the latest Cockpit. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/358

3 5

2wk atomic release candidate: 20180117
by Dusty Mabe 18 Jan '18

18 Jan '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Tomorrow we will attempt to release the 20180117 images. These images contain the following ostree version/commits from the Fedora-27-updates-20180117.0 updates run: Version: 27.61 Commit(x86_64): 772ab185b0752b0d6bc8b2096d08955660d80ed95579e13e136e6a54e3559ca9 Commit(aarch64): 598626fd61dc6ed4b702159e50b6029ee70a527e855fce7d8e61a870b141f893 Commit(ppc64le): 16ce78ee689066f582dbfc0672dab1706051fefab496fcebd8109d58738eb8fe The atomic host VM images are in the sub-directories under: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-27-2018011… The ISO images are in the sub-directories under: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-27-2018011… The AMIs are here: Fedora-Atomic-27-20180117.1.x86_64 EC2 (ap-northeast-1) ami-047b1d62 hvm standard Fedora-Atomic-27-20180117.1.x86_64 EC2 (ap-southeast-1) ami-df6a15a3 hvm standard Fedora-Atomic-27-20180117.1.x86_64 EC2 (ap-southeast-2) ami-a6b34cc4 hvm standard Fedora-Atomic-27-20180117.1.x86_64 EC2 (eu-central-1) ami-88b926e7 hvm standard Fedora-Atomic-27-20180117.1.x86_64 EC2 (eu-west-1) ami-9b0a93e2 hvm standard Fedora-Atomic-27-20180117.1.x86_64 EC2 (sa-east-1) ami-0e6b2662 hvm standard Fedora-Atomic-27-20180117.1.x86_64 EC2 (us-east-1) ami-6a98b410 hvm standard Fedora-Atomic-27-20180117.1.x86_64 EC2 (us-west-1) ami-27313347 hvm standard Fedora-Atomic-27-20180117.1.x86_64 EC2 (us-west-2) ami-ee952696 hvm standard Fedora-Atomic-27-20180117.1.x86_64 EC2 (ap-northeast-1) ami-1846207e hvm gp2 Fedora-Atomic-27-20180117.1.x86_64 EC2 (ap-southeast-1) ami-6666191a hvm gp2 Fedora-Atomic-27-20180117.1.x86_64 EC2 (ap-southeast-2) ami-bab14ed8 hvm gp2 Fedora-Atomic-27-20180117.1.x86_64 EC2 (eu-central-1) ami-76b62919 hvm gp2 Fedora-Atomic-27-20180117.1.x86_64 EC2 (eu-west-1) ami-a8069fd1 hvm gp2 Fedora-Atomic-27-20180117.1.x86_64 EC2 (sa-east-1) ami-006a276c hvm gp2 Fedora-Atomic-27-20180117.1.x86_64 EC2 (us-east-1) ami-6593bf1f hvm gp2 Fedora-Atomic-27-20180117.1.x86_64 EC2 (us-west-1) ami-29323049 hvm gp2 Fedora-Atomic-27-20180117.1.x86_64 EC2 (us-west-2) ami-7c9f2c04 hvm gp2 An example of the diff between this and the previous released version (for x86_64) is: ostree diff commit old: b5845ebd002b2ec829c937d68645400aa163e7265936b3e91734c6f33a510473 ostree diff commit new: 772ab185b0752b0d6bc8b2096d08955660d80ed95579e13e136e6a54e3559ca9 Upgraded: GeoIP-GeoLite-data 2017.10-1.fc27.noarch -> 2018.01-1.fc27.noarch bash 4.4.12-12.fc27.x86_64 -> 4.4.12-13.fc27.x86_64 cockpit-bridge 158-1.fc27.x86_64 -> 159-1.fc27.x86_64 cockpit-docker 158-1.fc27.x86_64 -> 159-1.fc27.x86_64 cockpit-networkmanager 158-1.fc27.noarch -> 159-1.fc27.noarch cockpit-ostree 158-1.fc27.x86_64 -> 159-1.fc27.x86_64 cockpit-system 158-1.fc27.noarch -> 159-1.fc27.noarch container-selinux 2:2.36-1.fc27.noarch -> 2:2.38-1.fc27.noarch dhcp-client 12:4.3.6-7.fc27.x86_64 -> 12:4.3.6-8.fc27.x86_64 dhcp-common 12:4.3.6-7.fc27.noarch -> 12:4.3.6-8.fc27.noarch dhcp-libs 12:4.3.6-7.fc27.x86_64 -> 12:4.3.6-8.fc27.x86_64 docker 2:1.13.1-42.git4402c09.fc27.x86_64 -> 2:1.13.1-44.git584d391.fc27.x86_64 docker-common 2:1.13.1-42.git4402c09.fc27.x86_64 -> 2:1.13.1-44.git584d391.fc27.x86_64 docker-rhel-push-plugin 2:1.13.1-42.git4402c09.fc27.x86_64 -> 2:1.13.1-44.git584d391.fc27.x86_64 dracut 046-5.fc27.x86_64 -> 046-8.git20180105.fc27.x86_64 dracut-config-generic 046-5.fc27.x86_64 -> 046-8.git20180105.fc27.x86_64 dracut-network 046-5.fc27.x86_64 -> 046-8.git20180105.fc27.x86_64 gdbm 1.13-3.fc27.x86_64 -> 1.14-1.fc27.x86_64 gettext 0.19.8.1-11.fc27.x86_64 -> 0.19.8.1-12.fc27.x86_64 gettext-libs 0.19.8.1-11.fc27.x86_64 -> 0.19.8.1-12.fc27.x86_64 glibc 2.26-20.fc27.x86_64 -> 2.26-21.fc27.x86_64 glibc-all-langpacks 2.26-20.fc27.x86_64 -> 2.26-21.fc27.x86_64 glibc-common 2.26-20.fc27.x86_64 -> 2.26-21.fc27.x86_64 glusterfs 3.12.4-1.fc27.x86_64 -> 3.12.5-1.fc27.x86_64 glusterfs-client-xlators 3.12.4-1.fc27.x86_64 -> 3.12.5-1.fc27.x86_64 glusterfs-fuse 3.12.4-1.fc27.x86_64 -> 3.12.5-1.fc27.x86_64 glusterfs-libs 3.12.4-1.fc27.x86_64 -> 3.12.5-1.fc27.x86_64 initscripts 9.78-1.fc27.x86_64 -> 9.79-1.fc27.x86_64 iproute 4.13.0-1.fc27.x86_64 -> 4.14.1-4.fc27.x86_64 iproute-tc 4.13.0-1.fc27.x86_64 -> 4.14.1-4.fc27.x86_64 kernel 4.14.8-300.fc27.x86_64 -> 4.14.13-300.fc27.x86_64 kernel-core 4.14.8-300.fc27.x86_64 -> 4.14.13-300.fc27.x86_64 kernel-modules 4.14.8-300.fc27.x86_64 -> 4.14.13-300.fc27.x86_64 kmod 24-3.fc27.x86_64 -> 25-1.fc27.x86_64 kmod-libs 24-3.fc27.x86_64 -> 25-1.fc27.x86_64 libcrypt-nss 2.26-20.fc27.x86_64 -> 2.26-21.fc27.x86_64 libpkgconf 1.3.12-1.fc27.x86_64 -> 1.3.12-2.fc27.x86_64 libseccomp 2.3.2-5.fc27.x86_64 -> 2.3.3-1.fc27.x86_64 linux-firmware 20171215-81.git2451bb22.fc27.noarch -> 20171215-82.git2451bb22.fc27.noarch microcode_ctl 2:2.1-19.fc27.x86_64 -> 2:2.1-20.fc27.x86_64 oci-register-machine 0-5.11.gitcd1e331.fc27.x86_64 -> 0-5.12.git3c01f0b.fc27.x86_64 oci-systemd-hook 1:0.1.13-1.gitafe4b4a.fc27.x86_64 -> 1:0.1.15-1.git2d0b8a3.fc27.x86_64 oci-umount 2:2.3.0-1.git51e7c50.fc27.x86_64 -> 2:2.3.2-1.git3025b19.fc27.x86_64 os-prober 1.74-3.fc27.x86_64 -> 1.74-4.fc27.x86_64 pcre 8.41-3.fc27.x86_64 -> 8.41-4.fc27.x86_64 pcre2 10.30-3.fc27.x86_64 -> 10.30-5.fc27.x86_64 pigz 2.3.4-3.fc27.x86_64 -> 2.4-1.fc27.x86_64 pkgconf 1.3.12-1.fc27.x86_64 -> 1.3.12-2.fc27.x86_64 pkgconf-m4 1.3.12-1.fc27.noarch -> 1.3.12-2.fc27.noarch pkgconf-pkg-config 1.3.12-1.fc27.x86_64 -> 1.3.12-2.fc27.x86_64 publicsuffix-list-dafsa 20171028-1.fc27.noarch -> 20171228-1.fc27.noarch python2 2.7.14-4.fc27.x86_64 -> 2.7.14-5.fc27.x86_64 python2-libs 2.7.14-4.fc27.x86_64 -> 2.7.14-5.fc27.x86_64 runc 2:1.0.0-12.rc4.gitaea4f21.fc27.x86_64 -> 2:1.0.0-15.rc4.gite6516b3.fc27.x86_64 selinux-policy 3.13.1-283.17.fc27.noarch -> 3.13.1-283.21.fc27.noarch selinux-policy-targeted 3.13.1-283.17.fc27.noarch -> 3.13.1-283.21.fc27.noarch vim-minimal 2:8.0.1386-1.fc27.x86_64 -> 2:8.0.1427-1.fc27.x86_64 Added: ebtables-2.0.10-24.fc27.x86_64 firewalld-0.4.4.5-3.fc27.noarch firewalld-filesystem-0.4.4.5-3.fc27.noarch ipset-6.32-1.fc27.x86_64 ipset-libs-6.32-1.fc27.x86_64 python3-firewall-0.4.4.5-3.fc27.noarch We have an updated kernel (the spectre patches are slowly working their way out [1]), and an updated docker with a security fix [2]. We also are *including* firewalld in the ostree now [3] but we are *not* enabling it by default. I'll post a follow up blog post on this topic in the next day or two. [1] https://fedoramagazine.org/update-ongoing-meltdown-spectre-work/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=1510351 [3] https://pagure.io/atomic-wg/issue/372 Dusty -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlpf8TcACgkQMwLb1zlS 5nFsQBAAj/5vpKnbkcuiMVYW+Ajn8Bs9pQMY4Zd+0or+MMzd0YSTky4e49W0TaFd jFRYxkSM8uPjdsIZuU/2rNfmQ19Zu2sO8eR9x134DSH2gqYtDmqSPGw9zbNMcW2B +tiMbFmFnPU8HtIP0QGcFXh/75ipmXiKbYZyEeul9W1BzAaC+Ww99UiB/TxiL0da oEFBNH+4E5r4jbYjRfk3PY9CaApZ5/Mu1paMGu7JpZSb5JXD65BFsoXXQKZ+BiD6 5qh2Y3jEvaaFPyDt4cuihC1wAdFKFVZp+Jm+UVXP601w5X6qtaJB4AiK6BwrMBbo pyzGszHOk5Ok9kIHXXOKBKWLFejh54Bn2jvTzLY/pFIonKnX82EpJKMoM8Fs+sBi 8PLwKW+CZ2hLzhPWAwpTO5phIPhJLszXVpiooSrFvMmXw+zjAUbvhlp+hXvhmBPp QK1esc95BgjujYF5xpzPfAyaP90suttdMwEqzVaaI5rx+ZQbr9ecO8NrcwXQnZE7 9GaMD9zUbjjrAxxAaQ0HDKtSgR4jRS7n6avs/YgKYx9FqMbbtEacUDWafHDzIp7Z yOWYGy1LpkvG4l1u6wXUh+WwCqYoY8ptpF1cDWbitUNk3qqMiKatR08IPASJPhqt hfSGstZ8VEgF298pStDrDqMklen1BEPAoVgsXMNjckLkLkAc0YY= =y436 -----END PGP SIGNATURE-----

2 1

[fedora-atomic] PR #106: Add packages needed to support aarch64 single board computers
by Peter Robinson 17 Jan '18

17 Jan '18

pbrobinson opened a new pull-request against the project: `fedora-atomic` that you are following: `` Add packages needed to support aarch64 single board computers `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/106

3 11

[fedora-atomic] PR #105: Add packages needed to support aarch64 single board computers
by Peter Robinson 17 Jan '18

17 Jan '18

pbrobinson opened a new pull-request against the project: `fedora-atomic` that you are following: `` Add packages needed to support aarch64 single board computers `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/105

3 5

Fedora Atomic WG Meeting Minutes 2018-01-17
by Dusty Mabe 17 Jan '18

17 Jan '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-01-17/fedora_atomic… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-01-17/fedora_atomic… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by dustymabe at 16:31:52 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-01-17/fedora_atomic… . Meeting summary - --------------- * roll call (dustymabe, 16:31:57) * previous meeting action items (dustymabe, 16:34:57) * sanja closed membership proposal AND voting proposal. updated the wiki and closed ticket (dustymabe, 16:39:37) * LINK: https://pagure.io/atomic-wg/issue/406 (ashcrow, 16:41:01) * LINK: https://pagure.io/atomic-wg/issue/407 (ashcrow, 16:41:36) * topics? (dustymabe, 16:42:32) * LINK: https://public.etherpad-mozilla.org/p/topics (dustymabe, 16:43:21) * this week's FAH release (dustymabe, 16:44:40) * meeting schedule due to devconf? (dustymabe, 16:48:00) * we will not have our regularly scheduled atomic wg meeting next week due to devconf (dustymabe, 16:51:18) * ACTION: ashcrow to send email to atomic-devel/announce to let people know (dustymabe, 16:51:42) * meeting schedule at devconf (dustymabe, 16:52:23) * open floor (dustymabe, 16:59:19) * LINK: https://github.com/ostreedev/ostree/releases/tag/v2018.1 (dustymabe, 17:04:40) * LINK: https://github.com/projectatomic/rpm-ostree/releases/tag/v2018.1 (dustymabe, 17:04:58) Meeting ended at 17:08:42 UTC. Action Items - ------------ * ashcrow to send email to atomic-devel/announce to let people know Action Items, by person - ----------------------- * ashcrow * ashcrow to send email to atomic-devel/announce to let people know * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * dustymabe (84) * ashcrow (25) * sanja (16) * zodbot (16) * jberkus (10) * sayan (9) * ksinny (3) * maxamillion (3) * kushal (2) * puiterwijk (2) * walters (2) * strigazi (1) * jbrooks (1) * coremodule (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlpfqX4ACgkQMwLb1zlS 5nGi3RAAkLH76QFo1b0sgGyeBdZqPkeQmapF1FCcNPvV0wqvN8h0mj62qBNU92y0 zrLc/b1Zk9yQR88RHzjKIU0vkNueepQbt33BDZbc4qp8U7QFmPFeG4SPiPTW9kAZ ecV3+NG7aCDmz2hLT4n3NQ7haqPqmTWaKCFYLwqs28UJtQHfVpbuwD19qRLt9iVc trx69BUSCG6Mbh1/s8sHXdwk3VtKXFB/9tyotrRy32xdBFGVTjtQVaSgWIRy1P5c DMDSOEG7tfDAbnQ2H5dFgAzXpvDT6E+tpGGiTnsjlk7JKqfxGWyV8tP36gVqJuLl o96YSJ5oBNB1tSdRmXvBAmCrYJvh2dUgme8SRH6pN1F/3RUST7z9ve/6R8p+jBpN m2yX5QbSUfusehWBaW7LuLsrjpRiV5ig8wOT1f7jINPO/ROhyEaNofYEYV9Nsby3 j3t3Bc93Gag9x0Ukz2gDI7C8mUv2gRmDOmErAjubVtBW5G0hApsyuj7UKy+HNeux ZwWQqAIrffPm+2UgFRYMJSgXQIXDqHtsgGZzr/IQ+IpVVmZCu7Dqc50rpfqTJ4gY j1Dcjjv54UHGKLg2m2owypVlWus91ElBKwZabtTwE5v1cpQxlYITFXNtzxaDDuDZ nCBQV/Ne7e5dL/eS4iiC9XpS+lwgY0YJTzF62KxkTLo8NErgTqk= =Ye7C -----END PGP SIGNATURE-----

1 0

[atomic-wg] Issue #401: add --use-system-defaults option to firewall anaconda kickstart argument
by Dusty Mabe 17 Jan '18

17 Jan '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` This is needed for (including firewalld in atomic host)[https://pagure.io/atomic-wg/issue/372]. Basically right now anaconda will always enable firewalld on the host if firewalld is installed. Since we want to include firewalld in atomic host, but we want to leave it disabled by default, then we need anaconda to leave the system alone and not enable or disable it. We need a `firewall --use-system-defaults` flag inside anaconda for this. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/401

1 5

[atomic-wg] Issue #363: Overhaul list of members, Quorum Rules
by Josh Berkus 16 Jan '18

16 Jan '18

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` The current list of members, carried over from the Cloud SIG, is here: https://fedoraproject.org/wiki/Atomic_WG#Working_Group_Members_and_Points_o… Things we need to change: 1. Who should we remove? Are jsmith and nzwulfin active anymore? 2. Who needs to be added? Jlebon? ashcrow? QUORUM ISSUE: We currently list meeting quorum as 51% of all members. With our open membership, though, that means that we need at least 11 people at a Fedora Atomic meeting to make decisions. We need to either lower that threshold (I suggest six) or we need to restrict membership in the WG. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/363

10 29

[Fedocal] Reminder meeting : Atomic Working Group Weekly Meeting
by dusty＠dustymabe.com 16 Jan '18

16 Jan '18

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2018-01-17 from 16:30:00 to 17:30:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: This is the meeting for the Fedora Atomic Working Group. We typically go over previous meeting action items and then cover all tickets with the meeting keyword: https://pagure.io/atomic-wg/issues?status=Open&tags=meeting More information available at: [https://fedoraproject.org/wiki/Atomic_WG#Meetings](https://fedoraproject.or… Source: https://apps.fedoraproject.org/calendar/meeting/6952/

1 0

[fedora-atomic] PR #27: post: Work around LVM archival conflicting with ostree
by Dusty Mabe 15 Jan '18

15 Jan '18

dustymabe canceled a pull-request against the project: `fedora-atomic` that you are following. Cancelled pull-request: `` post: Work around LVM archival conflicting with ostree `` https://pagure.io/fedora-atomic/pull-request/27

1 0

[fedora-atomic] PR #27: post: Work around LVM archival conflicting with ostree
by Dusty Mabe 15 Jan '18

15 Jan '18

dustymabe commented on the pull-request: `post: Work around LVM archival conflicting with ostree` that you are following: `` I'm going to close this PR. Originally it was created to handle https://bugzilla.redhat.com/show_bug.cgi?id=1365297 but the [fix](https://github.com/ostreedev/ostree/issues/545) that we're going to invest time in is a more generic fix for solving **lost /etc/ changes that were done post upgrade but pre-reboot** problems. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/27

1 0

[atomic-wg] Issue #282: Atomic Host images omit many common locales that all other flavors include
by Jonathan Lebon 15 Jan '18

15 Jan '18

jlebon added a new comment to an issue you are following: `` https://pagure.io/atomic-wg/issue/408 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/282

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) January 2018