March 2018 - Atomic Working Group (ARCHIVED)

[fedora-atomic] PR #114: add a few modules to initramfs to enable vmw/hyperv
by Dusty Mabe 21 Dec '18

21 Dec '18

dustymabe opened a new pull-request against the project: `fedora-atomic` that you are following: `` add a few modules to initramfs to enable vmw/hyperv `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/114

3 11

[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 #421: coordinate Project Atomic-related talks for devconf.us
by Sanja Bonic 29 Jun '18

29 Jun '18

sanja reported a new issue against the project: `atomic-wg` that you are following: `` Please everyone comment on this if you either: 1. are submitting to DevConf.us but don't know what to talk about 2. already submitted to DevConf.us but don't want others to see what you submitted yet 3. already submitted and want others to see the abstract 4. know someone who fits into 1.-3. but doesn't know about this ticket here I'll approach you individually afterwards and have a link with gathered information ready for those who are participating - if you wanna give a talk but need help submitting, message me. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/421

11 29

[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 #432: AH with Podman for CI tests only
by Brent Baude 08 Jun '18

08 Jun '18

baude reported a new issue against the project: `atomic-wg` that you are following: `` The upstream libpod project (https://github.com/projectatomic/libpod/) would love to have an AH F27 variant without docker and with podman and its friends. This would be only used in our PAPR CI tests and perhaps for debug. We understand a more official project is in the works for this and is being tracked by issue #422. Today we currently use an F27 cloud image and install the packages we need. We would prefer that this be done predeployment and use AH instead of cloud. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/432

6 11

[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 #418: Design Meetings over Video
by Steve Milner 28 May '18

28 May '18

smilner reported a new issue against the project: `atomic-wg` that you are following: `` An idea that @dustymabe had was to start having design meetings via video (like Hangouts/BJN/etc..) to help speed up design discussions. We traditionally either had these discussions over long issue threads or IRC conversations. Would it be worth having a time/location that we could get community members together to discuss deeper design items together in public? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/418

5 8

[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 #442: CentOS Atomic AMI's missing
by Chris Collins 28 May '18

28 May '18

clcollins reported a new issue against the project: `atomic-wg` that you are following: `` Not sure if this belongs here or on the bugs.centos.org, but I'm guessing the right person will see it, heh. The CentOS wiki provides documentation on the current CentOS Atomic Host AMIs available in AWS: https://wiki.centos.org/SpecialInterestGroup/Atomic/Download However, it appears that several of the AMIs from the latest release are missing. From the spot check I did looking for: ami-a06447da : us-east-1a ami-fe12389b : us-east-2 ami-31262451 : us-west-1 ami-39cc7f41 : us-west-2 Only ami-a06447da appears to exist, at least within the publicly available images for me. Even searching by name (CentOS Atomic host 7 x86_64 HVM EBS 1801_01), I have not been able to find anything in us-east-2 or us-west-1 or -2. Apologies if I'm missing something obvious here... `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/442

3 3

[atomic-wg] Issue #438: use botbot.me to log #atomic channel
by Micah Abbott 28 May '18

28 May '18

miabbott reported a new issue against the project: `atomic-wg` that you are following: `` I think it would be useful to have an archive of conversations in #atomic that we could reference when searching for solutions to previously seen problems or the like. This would also allow folks who might not have a persistent connection to IRC to go back and catch up on the day (or days) worth of chatter. However, I understand that some folks might not want to have the channel or their participation logged, so we should discuss the pros/cons. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/438

5 10

[atomic-wg] Issue #446: FAW 28 ISO requires network
by Colin Walters 12 May '18

12 May '18

walters reported a new issue against the project: `atomic-wg` that you are following: `` Presumably this is an anaconda regression; we have the ostree data cached in the ISO so there's no reason for us to require networking to install. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/446

3 5

[atomic-wg] Issue #445: Fedora 28 Talking Points
by Dusty Mabe 02 May '18

02 May '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` From @mattdm : ``` Do we have anything I should emphasize for beta, coming up next week? What about in May? https://fedoraproject.org/wiki/Fedora_28_talking_points#Fedora_Atomic ``` `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/445

8 26

[atomic-wg] Issue #422: Evaluate podman for inclusion in atomic host
by Dusty Mabe 18 Apr '18

18 Apr '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` We've had a few discussions about including `cri-o` in atomic host and one [recently](https://pagure.io/atomic-wg/issue/407) discussing both `cri-o` and `podman`. The consensus on `cri-o` was that if someone needs to get openshift/kubernetes then it's not that much harder to also get `cri-o` as part of the same process (for example, using the `openshift-ansible` installer). `podman`, however, is something we could consider adding because it gives us a nice familiar CLI with possibly less bloat. `podman` is brand new and there is still some work to be done on it. It was decided that we should evaluate adding `podman` into atomic host in a few months time. This was proposed at the [feb 7th WG meeting](https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-February/msg00024.html). `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/422

8 26

[atomic-wg] Issue #440: Packaging Project Atomic container tools for Debian
by Victor Hugo Aguiar Pacce 13 Apr '18

13 Apr '18

drakonis reported a new issue against the project: `atomic-wg` that you are following: `` Currently there's just an Ubuntu ppa with the tools, we should work towards getting it into Debian. * https://launchpad.net/~projectatomic/+archive/ubuntu/ppa `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/440

2 5

[atomic-wg] Issue #441: get autocloud testing F28 media
by Dusty Mabe 13 Apr '18

13 Apr '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` right now I don't see [autocloud](https://apps.fedoraproject.org/autocloud/) testing F28 media. let's figure out why this is so we can get some test results for f28 if possible. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/441

4 11

[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 #439: Container Release
by Clement Verna 04 Apr '18

04 Apr '18

cverna reported a new issue against the project: `atomic-wg` that you are following: `` The Fedora container release are quite difficult to get out, while the tooling might still need some work, I also feel that it is not really clear what we are expecting from the release. Following a discussion on atomic-devel, I propose the following : * Release containers that are based on the current stable fedora ( would be f27 currently) * Release containers that are based on the next stable fedora release (beta) ( would be f28 currently) with the idea to have these available for testing. This process would exclude rebuilding the f26 and rawhide based containers. Any feedback on this proposition ? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/439

5 11

Fedora Atomic WG Meeting Minutes 2018-03-28
by Micah Abbott 28 Mar '18

28 Mar '18

minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-28/fedora_atomic… minutes (text): https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2018-03-28/fedora_at… log: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-28/fedora_atomic… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by miabbott at 16:30:37 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-28/fedora_atomic… . Meeting summary --------------- * roll call (miabbott, 16:30:45) * previous meeting action items (miabbott, 16:34:57) * LINK: https://pagure.io/atomic-wg/issue/438 (miabbott, 16:35:52) * LINK: https://pagure.io/atomic-wg/issue/439 (cverna, 16:37:52) * ACTION: cverna to add some more details to the ticket (439) and email adam miller for feedback (miabbott, 16:39:38) * ACTION: drakonis to open an atomic-wg issue to track container tools in debian discussion (miabbott, 16:40:07) * coordinate Project Atomic-related talks for devconf.us (miabbott, 16:40:48) * LINK: https://pagure.io/atomic-wg/issue/421 (miabbott, 16:40:57) * devconf.us CfP closes on April 3 (miabbott, 16:42:28) * engage sanja for talk ideas or travel costs related to devconf.us/devconf.in (miabbott, 16:43:34) * ACTION: sanja to start email thread with talk volunteers to make sure abstracts are submitted on time (miabbott, 16:45:24) * jberkus has volunteered to review defconf.us submissions before CfP closes (miabbott, 16:49:37) * Evaluate podman for inclusion in atomic host (miabbott, 16:50:31) * LINK: https://pagure.io/atomic-wg/issue/422 (miabbott, 16:50:41) * ACTION: ashcrow to make a PR to include podman in Fedora Rawhide Atomic Host (miabbott, 16:54:43) * use botbot.me to log #atomic channel (miabbott, 16:55:14) * LINK: https://pagure.io/atomic-wg/issue/438 (miabbott, 16:55:21) * ACTION: dustymabe to configure botbot.me to log #atomic channel (miabbott, 17:01:50) * Container Release (miabbott, 17:02:20) * LINK: https://pagure.io/atomic-wg/issue/439 (miabbott, 17:02:23) * Fedora 28 Talking Points (miabbott, 17:04:05) * LINK: https://pagure.io/atomic-wg/issue/445 (miabbott, 17:04:08) * open floor (miabbott, 17:12:51) * cverna planning on container release mar 29 for f27 (miabbott, 17:13:58) * ACTION: sayan to open ticket with cloud-sig about deprecating pv AMIs (miabbott, 17:18:42) * first project atomic community meeting in asia/australia to be held April 03, 2018 - 05:00 UTC (miabbott, 17:20:38) * everyone should publicize the asia/australia meeting via social media, etc (miabbott, 17:26:02) Meeting ended at 17:28:23 UTC. Action Items ------------ * cverna to add some more details to the ticket (439) and email adam miller for feedback * drakonis to open an atomic-wg issue to track container tools in debian discussion * sanja to start email thread with talk volunteers to make sure abstracts are submitted on time * ashcrow to make a PR to include podman in Fedora Rawhide Atomic Host * dustymabe to configure botbot.me to log #atomic channel * sayan to open ticket with cloud-sig about deprecating pv AMIs Action Items, by person ----------------------- * ashcrow * ashcrow to make a PR to include podman in Fedora Rawhide Atomic Host * cverna * cverna to add some more details to the ticket (439) and email adam miller for feedback * dustymabe * dustymabe to configure botbot.me to log #atomic channel * sayan * sayan to open ticket with cloud-sig about deprecating pv AMIs * **UNASSIGNED** * drakonis to open an atomic-wg issue to track container tools in debian discussion * sanja to start email thread with talk volunteers to make sure abstracts are submitted on time People Present (lines said) --------------------------- * miabbott (84) * sanja1 (64) * dustymabe (59) * ashcrow (32) * zodbot (27) * rubao (15) * lorbus (12) * jberkus (10) * cverna (8) * sayan (7) * ksinny (5) * giuseppe (4) * puiterwijk (3) * jlebon (3) * strigazi (1) * walters (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[fedora-atomic] PR #117: podman: Add podman to packages
by Steve Milner 28 Mar '18

28 Mar '18

smilner opened a new pull-request against the project: `fedora-atomic` that you are following: `` podman: Add podman to packages `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/117

2 2

What talking points do we have for Atomic in the F28 release timeframe?
by Matthew Miller 28 Mar '18

28 Mar '18

Do we have anything I should emphasize for beta, coming up next week? What about in May? https://fedoraproject.org/wiki/Fedora_28_talking_points#Fedora_Atomic -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

2 1

[atomic-wg] Issue #443: Boot from ISO stuck at Reached target Basic System
by Rares Vernica 28 Mar '18

28 Mar '18

rares reported a new issue against the project: `atomic-wg` that you are following: `` I got `Fedora-Atomic-ostree-x86_64-27-20180314.0.iso` on a USB stick. When booting from USB, I get as far as: ~~~~ ... [ OK ] Reached target paths. [ OK ] Reached target Basic System. _ ~~~~ Than it get stack there forever. On the same hardware, I was able to boot and install previous versions of the ISO. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/443

2 4

[atomic-wg] Issue #444: Fedora Atomic CI pipeline package whitelist
by Miroslav Vadkerti 28 Mar '18

28 Mar '18

mvadkert reported a new issue against the project: `atomic-wg` that you are following: `` The Fedora Atomic CI pipeline currently runs tests only for packages on this list [1]. The "rpm -qa" from a fresh install shows more packages in interest [2]. Is that fine? Shouldn't the pipeline run package level tests for packages in list [2]? The diff of these two can be found here [3]. [1] https://pagure.io/fedora-atomic/raw/f26/f/fedora-atomic-host-base.json [2] https://github.com/Andrei-Stepanov/wikistat/blob/master/repos-fedora-atomic [3] https://paste.fedoraproject.org/paste/jVxhRQPPtsBbOovvU4CViA `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/444

3 3

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

27 Mar '18

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2018-03-28 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

2wk atomic release candidate: 20180326.1
by Sinny Kumari 27 Mar '18

27 Mar '18

By the end of the day, we will attempt to release the 20180326.1 images. These images contain the following ostree version/commits from the Fedora-27-updates-20180325.0 updates run: Version: 27.105 Commit(x86_64): c4015063c00515ddbbaa4c484573d38376db270b09adb22a4859faa0a39d5d93 Commit(aarch64): 69bd8187bb519483f275dc1456434cc18eec961ab53d965fd50516865ded3c25 Commit(ppc64le): ae9104933a70342d2b2b08c8ff9f07f2e883b6e18abf2b06c6a3e7be3685af66 The atomic host VM images are in the sub-directories under: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-27-2018032… The ISO images are in the sub-directories under: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-27-2018032… The AMIs are here: Fedora-Atomic-27-20180326.1.x86_64 EC2 (us-west-2) ami-8260f9fa hvm standard Fedora-Atomic-27-20180326.1.x86_64 EC2 (us-west-1) ami-69c9df09 hvm standard Fedora-Atomic-27-20180326.1.x86_64 EC2 (us-east-1) ami-3abd6247 hvm standard Fedora-Atomic-27-20180326.1.x86_64 EC2 (sa-east-1) ami-431c4b2f hvm standard Fedora-Atomic-27-20180326.1.x86_64 EC2 (eu-west-1) ami-cf5303b6 hvm standard Fedora-Atomic-27-20180326.1.x86_64 EC2 (eu-central-1) ami-8660326d hvm standard Fedora-Atomic-27-20180326.1.x86_64 EC2 (ap-southeast-2) ami-96e824f4 hvm standard Fedora-Atomic-27-20180326.1.x86_64 EC2 (ap-southeast-1) ami-806836fc hvm standard Fedora-Atomic-27-20180326.1.x86_64 EC2 (ap-northeast-1) ami-834e47ff hvm standard Fedora-Atomic-27-20180326.1.x86_64 EC2 (us-west-2) ami-dd60f9a5 hvm gp2 Fedora-Atomic-27-20180326.1.x86_64 EC2 (us-west-1) ami-bef6e0de hvm gp2 Fedora-Atomic-27-20180326.1.x86_64 EC2 (us-east-1) ami-1bb16e66 hvm gp2 Fedora-Atomic-27-20180326.1.x86_64 EC2 (sa-east-1) ami-391e4955 hvm gp2 Fedora-Atomic-27-20180326.1.x86_64 EC2 (eu-west-1) ami-152f7f6c hvm gp2 Fedora-Atomic-27-20180326.1.x86_64 EC2 (eu-central-1) ami-3b6634d0 hvm gp2 Fedora-Atomic-27-20180326.1.x86_64 EC2 (ap-southeast-2) ami-b5ef23d7 hvm gp2 Fedora-Atomic-27-20180326.1.x86_64 EC2 (ap-southeast-1) ami-826836fe hvm gp2 Fedora-Atomic-27-20180326.1.x86_64 EC2 (ap-northeast-1) ami-a04c45dc hvm gp2 An example of the diff between this and the previous released version (for x86_64) is: ostree diff commit old: 326f62b93a5cc836c97d31e73a71b6b6b6955c0f225f7651b52a693718e6aa91 ostree diff commit new: c4015063c00515ddbbaa4c484573d38376db270b09adb22a4859faa0a39d5d93 Upgraded: ceph-common 1:12.2.3-1.fc27 -> 1:12.2.4-1.fc27 cockpit-bridge 163-1.fc27 -> 164-1.fc27 cockpit-docker 163-1.fc27 -> 164-1.fc27 cockpit-networkmanager 163-1.fc27 -> 164-1.fc27 cockpit-ostree 163-1.fc27 -> 164-1.fc27 cockpit-system 163-1.fc27 -> 164-1.fc27 container-selinux 2:2.48-1.fc27 -> 2:2.52-1.fc27 curl 7.55.1-9.fc27 -> 7.55.1-10.fc27 elfutils-default-yama-scope 0.170-1.fc27 -> 0.170-10.fc27 elfutils-libelf 0.170-1.fc27 -> 0.170-10.fc27 elfutils-libs 0.170-1.fc27 -> 0.170-10.fc27 jansson 2.10-4.fc27 -> 2.11-1.fc27 kernel 4.15.8-300.fc27 -> 4.15.10-300.fc27 kernel-core 4.15.8-300.fc27 -> 4.15.10-300.fc27 kernel-modules 4.15.8-300.fc27 -> 4.15.10-300.fc27 libcephfs2 1:12.2.3-1.fc27 -> 1:12.2.4-1.fc27 libcurl 7.55.1-9.fc27 -> 7.55.1-10.fc27 librados2 1:12.2.3-1.fc27 -> 1:12.2.4-1.fc27 libradosstriper1 1:12.2.3-1.fc27 -> 1:12.2.4-1.fc27 librbd1 1:12.2.3-1.fc27 -> 1:12.2.4-1.fc27 librgw2 1:12.2.3-1.fc27 -> 1:12.2.4-1.fc27 libsss_idmap 1.16.0-8.fc27 -> 1.16.1-1.fc27 libsss_nss_idmap 1.16.0-8.fc27 -> 1.16.1-1.fc27 libsss_sudo 1.16.0-8.fc27 -> 1.16.1-1.fc27 libtirpc 1.0.2-4.fc27 -> 1.0.3-0.fc27 microcode_ctl 2:2.1-20.fc27 -> 2:2.1-22.fc27 nspr 4.18.0-1.fc27 -> 4.19.0-1.fc27 nss 3.35.0-1.1.fc27 -> 3.36.0-1.0.fc27 nss-softokn 3.35.0-1.0.fc27 -> 3.36.0-1.0.fc27 nss-softokn-freebl 3.35.0-1.0.fc27 -> 3.36.0-1.0.fc27 nss-sysinit 3.35.0-1.1.fc27 -> 3.36.0-1.0.fc27 nss-tools 3.35.0-1.1.fc27 -> 3.36.0-1.0.fc27 nss-util 3.35.0-1.0.fc27 -> 3.36.0-1.0.fc27 pcre2 10.31-1.fc27 -> 10.31-3.fc27 python-cephfs 1:12.2.3-1.fc27 -> 1:12.2.4-1.fc27 python-rados 1:12.2.3-1.fc27 -> 1:12.2.4-1.fc27 python-rbd 1:12.2.3-1.fc27 -> 1:12.2.4-1.fc27 python-rgw 1:12.2.3-1.fc27 -> 1:12.2.4-1.fc27 python2 2.7.14-8.fc27 -> 2.7.14-10.fc27 python2-libs 2.7.14-8.fc27 -> 2.7.14-10.fc27 python3 3.6.4-8.fc27 -> 3.6.4-9.fc27 python3-libs 3.6.4-8.fc27 -> 3.6.4-9.fc27 python3-sssdconfig 1.16.0-8.fc27 -> 1.16.1-1.fc27 selinux-policy 3.13.1-283.26.fc27 -> 3.13.1-283.28.fc27 selinux-policy-targeted 3.13.1-283.26.fc27 -> 3.13.1-283.28.fc27 shared-mime-info 1.9-1.fc27 -> 1.9-2.fc27 sssd-client 1.16.0-8.fc27 -> 1.16.1-1.fc27 This release contains updated cockpit [1]. Please test it to ensure that latest Atomic Host is working for you as expected! [1] https://github.com/cockpit-project/cockpit/releases/tag/164 Thanks, Sinny Kumari

1 0

[atomic-wg] Issue #428: Archive unused GitHub repositories
by Sanja Bonic 22 Mar '18

22 Mar '18

sanja reported a new issue against the project: `atomic-wg` that you are following: `` **Goal: cleanup** by archiving the repositories in this list. Thanks @smilner for the initial list. Please add repositories you think should be archived or comment which ones should not be archived from this list. * ansible-role-atomic-reactor * ansible-role-osbs-secret * openshift2nulecule (archived) * fedora-productimg-atomic * ansible-role-pulp-secret * ansible-role-osbs-proxy * ansible-role-install-openshift * atomic-enterprise-ansible * forward-journald * vagrant-adbinfo * docker-py * image-inspector * ruby-hello-world * atomic-enterprise * heat-kubernetes * docker-fedora-images * heat-atomic * oversight * adb-vagrant-redhat-certification * anaconda * rhci-docker * atomic-enterprise-training * ansible-osbs * nulecule (archived) * commissaire-mvp [should be archived] * commctl [should be archived] * commissaire-http [should be archived] * commissaire (archived) * commissaire-service [should be archived] `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/428

6 14

Fedora Atomic WG Meeting Minutes 2018-03-21
by Dusty Mabe 21 Mar '18

21 Mar '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-21/fedora_atomic… Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-21/fedora_atomic… Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-21/fedora_atomic… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by dustymabe at 16:30:43 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-21/fedora_atomic… . Meeting summary - --------------- * roll call (dustymabe, 16:30:48) * previous meeting action items (dustymabe, 16:35:55) * jlebon wrote blog post on new features of ostree/rpm-ostree http://www.projectatomic.io/blog/2018/03/new-rpm-ostree-features/ (dustymabe, 16:36:51) * coordinate Project Atomic-related talks for devconf.us (dustymabe, 16:38:19) * LINK: https://pagure.io/atomic-wg/issue/421 (dustymabe, 16:38:24) * please add devconf.us talk ideas to https://pagure.io/atomic-wg/issue/421 (dustymabe, 16:47:26) * Evaluate podman for inclusion in atomic host (dustymabe, 16:52:09) * LINK: https://pagure.io/atomic-wg/issue/422 (dustymabe, 16:52:15) * use botbot.me to log #atomic channel (dustymabe, 17:04:26) * LINK: https://pagure.io/atomic-wg/issue/438 (dustymabe, 17:04:32) * ACTION: dustymabe to update the botbot ticket with information from meeting (dustymabe, 17:08:46) * Container Release (dustymabe, 17:09:32) * LINK: https://pagure.io/atomic-wg/issue/439 (dustymabe, 17:09:38) * ACTION: cverna to add some more details to the ticket and email adam miller for feedback (dustymabe, 17:18:06) * open floor (dustymabe, 17:18:27) * LINK: https://launchpad.net/~projectatomic/+archive/ubuntu/ppa (jbrooks, 17:22:10) * ACTION: drakonis to open an atomic-wg issue to track container tools in debian discussion (dustymabe, 17:27:26) * LINK: https://pagure.io/atomic-wg/issue/440 (drakonis, 17:29:50) Meeting ended at 17:31:24 UTC. Action Items - ------------ * dustymabe to update the botbot ticket with information from meeting * cverna to add some more details to the ticket and email adam miller for feedback * drakonis to open an atomic-wg issue to track container tools in debian discussion Action Items, by person - ----------------------- * cverna * cverna to add some more details to the ticket and email adam miller for feedback * drakonis * drakonis to open an atomic-wg issue to track container tools in debian discussion * dustymabe * dustymabe to update the botbot ticket with information from meeting * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * dustymabe (116) * ashcrow (28) * jbrooks (26) * lorbus (20) * zodbot (17) * cverna (15) * drakonis (13) * mheon (11) * patux (9) * langdon (6) * jlebon (6) * walters (5) * rubao (3) * ksinny (3) * kushal (2) * coremodule (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlqypbcACgkQMwLb1zlS 5nG2Sg//QvpcZ5vGvLMnRF5JRpkoPLiqSNRONxaHr/XStrmBjYz/FO2UqDeBNhoO jwgJJXgm4dU4TBwgSSr9GZP7lnYXOjOKbwC2oKQPH+6E/HKfOWZE6kTJ1mgYwsIp tGXL3xfur/dBrtvolPVQ1/4lHSCjzLpy1oelvmYvuu4C/lwhXBsjehEPGZf/Zr78 hXxMB4tj69Il3pwWth9ng2YXt1sbu6EWRApcDYg2pCVPnVchjBUUTLNyx6pAIrQD vbLmpIovZsllOolePI/PT2PsmYfM5H2y9cpfpsS9tHM96ZzmMP/NDP7r7Cpa20ni mfVmvVR+jPHdUCllTDs00+rp68xgyAbeh3hbzy+tT6VOi62li77aWD+SbVKIMbc/ CkOLY1JV2O9lOcTvCCLpZezLPtm1klRjZ4cKw9CtcpiCdSkygJEQ1NrPaWkECGJp McoYYjDeh3wDMVUYDU5xi/65p2Yy2HNDXnBvH4fhVpem7Dyx5iPRPVVALyuuoV+I LIFiSd9hXkSY6IbreXJjFUzUgdBMNkso/SNRY1kzgGw0u34G87Ch5ZOzpRSi5Yp4 Hf8Snn4xwoD4n4O+MPmrT+ysMZFZw5E7c8/YQYRcHZQZRr9EmMwQjtR56suN2JUy FPTZqGXF0p8Di8lUNn0+1fFinIuV9/e7JhLDZemUK0NS+k4FHdw= =laLy -----END PGP SIGNATURE-----

1 0

[atomic-wg] PR #437: Remove puiterwijk from meeting-people
by Patrick "マルタインアンドレアス" Uiterwijk 21 Mar '18

21 Mar '18

puiterwijk opened a new pull-request against the project: `atomic-wg` that you are following: `` Remove puiterwijk from meeting-people `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/pull-request/437

2 3

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

20 Mar '18

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2018-03-21 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 #128: Extra ifcfg file in the cloud base image
by Adam Williamson 19 Mar '18

19 Mar '18

adamwill added a new comment to an issue you are following: `` This got zombied, by the 'persistent' device name changing: https://bugzilla.redhat.com/show_bug.cgi?id=1558027 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/128

1 0

[atomic-wg] Issue #206: Move nginx container image from Fedora-Dockerfiles GitHub into DistGit
by Clement Verna 15 Mar '18

15 Mar '18

The status of the issue: `Move nginx container image from Fedora-Dockerfiles GitHub into DistGit` of project: `atomic-wg` has been updated to: Closed as Fixed by cverna. https://pagure.io/atomic-wg/issue/206

1 0

[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 #206: Move nginx container image from Fedora-Dockerfiles GitHub into DistGit
by Dusty Mabe 14 Mar '18

14 Mar '18

dustymabe added a new comment to an issue you are following: `` > This is now in the registry, so we can close this ticket you have ticket access now so you should be able to close tickets! `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/206

1 0

[atomic-wg] Issue #276: Set architecture label in the base container image
by Clement Verna 14 Mar '18

14 Mar '18

cverna added a new comment to an issue you are following: `` I believe this is done now. ``` { "Name": "candidate-registry.fedoraproject.org/f27/greenwave", "Digest": "sha256:abda79af6349e8ff09fb35500477d71c01f4607e90721d60b8d010fe51097aab", "RepoTags": [ "rawhide-container-candidate-49347-20180212083824", "f27-91008-20180218082622", "f27-container-candidate-75796-20180314172356" ], "Created": "2018-03-14T17:27:32.444383Z", "DockerVersion": "1.13.1", "Labels": { "architecture": "x86_64", ``` `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/276

1 0

[atomic-wg] Issue #206: Move nginx container image from Fedora-Dockerfiles GitHub into DistGit
by Clement Verna 14 Mar '18

14 Mar '18

cverna added a new comment to an issue you are following: `` This is now in the registry, so we can close this ticket `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/206

1 0

[atomic-wg] Issue #272: FLIBS: bogus 'authorative-source-url' in layered images
by Dusty Mabe 14 Mar '18

14 Mar '18

The status of the issue: `FLIBS: bogus 'authorative-source-url' in layered images` of project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe. https://pagure.io/atomic-wg/issue/272

1 0

[atomic-wg] Issue #272: FLIBS: bogus 'authorative-source-url' in layered images
by Dusty Mabe 14 Mar '18

14 Mar '18

The issue: `FLIBS: bogus 'authorative-source-url' in layered images` of project: `atomic-wg` has been assigned to `cverna` by dustymabe. https://pagure.io/atomic-wg/issue/272

1 0

[atomic-wg] Issue #272: FLIBS: bogus 'authorative-source-url' in layered images
by Dusty Mabe 14 Mar '18

14 Mar '18

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

1 0

[atomic-wg] Issue #272: FLIBS: bogus 'authorative-source-url' in layered images
by Clement Verna 14 Mar '18

14 Mar '18

cverna added a new comment to an issue you are following: `` This is now fixed. ``` { "Name": "candidate-registry.fedoraproject.org/f27/greenwave", "Digest": "sha256:abda79af6349e8ff09fb35500477d71c01f4607e90721d60b8d010fe51097aab", "RepoTags": [ "rawhide-container-candidate-49347-20180212083824", "f27-91008-20180218082622", "f27-container-candidate-75796-20180314172356" ], "Created": "2018-03-14T17:27:32.444383Z", "DockerVersion": "1.13.1", "Labels": { "architecture": "x86_64", "authoritative-source-url": "registry.fedoraproject.org", "build-date": "2018-03-14T17:24:02.218777", ``` we can close this issue `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/272

1 0

Fedora Atomic WG Meeting Minutes 2018-03-14
by Sinny Kumari 14 Mar '18

14 Mar '18

summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-14/fedora_atomic… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-14/fedora_atomic… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by ksinny at 16:30:10 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-14/fedora_atomic… . Meeting summary --------------- * Roll Call (ksinny, 16:30:25) * Action items from last meeting (ksinny, 16:34:26) * davdunc is working with the Marketplace team at AWS to walk them through it (ksinny, 16:40:22) * davdunc will do further update about AWS scan results of Fedora Atomic Host on atomic-wg ticket (ksinny, 16:43:52) * LINK: https://pagure.io/atomic-wg/issue/339 (ksinny, 16:44:03) * ACTION: jlebon to write blog post for recent rpm-ostree/ostree releases features (ksinny, 16:44:38) * Asian/Australian timezone IRC meeting for community and parts of WG (ksinny, 16:45:13) * LINK: https://pagure.io/atomic-wg/issue/433 (ksinny, 16:45:21) * atomic-wg meeting for Asian/Australian timezone has been scheduled biweekly on Tuesday at 5:00 UTC on #fedora-meeting1 (ksinny, 16:56:01) * LINK: https://pagure.io/atomic-wg/issue/429 (sanja_, 16:59:13) * Atomic VFAD outcome from last week (ksinny, 17:00:44) * LINK: https://pagure.io/atomic-wg/issue/429 (ksinny, 17:00:55) * LINK: VFAD vluejeans recording - https://dustymabe.fedorapeople.org/2018-03-09_Fedora-Atomic-WG-vFAD.mp4 (ksinny, 17:07:44) * LINK: VFAD summary - https://public.etherpad-mozilla.org/p/2018-03-09_Fedora-Atomic-WG-vFAD (ksinny, 17:08:00) * Open Floor (ksinny, 17:08:06) * cverna will be introducing some CI to fedora container which will incldude checks like Dockerfile linter (ksinny, 17:12:30) Meeting ended at 17:23:14 UTC. Action Items ------------ * jlebon to write blog post for recent rpm-ostree/ostree releases features Action Items, by person ----------------------- * jlebon * jlebon to write blog post for recent rpm-ostree/ostree releases features * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * ksinny (74) * sanja_ (69) * zodbot (34) * miabbott (22) * dustymabe (21) * cverna (17) * jlebon (11) * davdunc (7) * roshi (6) * ttomecek (6) * misc (5) * maxamillion (5) * jsmith (4) * jbrooks (3) * kushal (2) * lorbus (2) * strigazi (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[atomic-wg] Issue #433: Asian/Australian timezone IRC meeting for community and parts of WG
by Sanja Bonic 14 Mar '18

14 Mar '18

sanja reported a new issue against the project: `atomic-wg` that you are following: `` Several times we've had to say "sorry, no can do" to community members for the Asian/Australian time zone and it would be good to be able to accommodate that timezone with a meeting as well. ## GOAL * including people in the Asian and Australian timezone into the discussions they often cannot be part of live due to time set * gain new voices ## ACTIONS These actions are needed in order to implement such a meeting. * show the meeting char the zodbot commands and explain how to chair an IRC meeting (contact me by replying to the mailing list or via private mail if you're interested but need more information) * go through the atomic-wg meeting items and see if there are some actions your meeting participants can/want to take over * introduce new discussions that are relevant to members which will then be discussed in atomic-wg's Wednesday meeting if relevant, otherwise pagure issues will be created --- This was posted to the mailing list - @sinnykumari has stated she can chair the meetings for that timezone. This ticket is about finding a suitable time. Suggestions in the ticket please - updates to the description can be made then. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/433

3 4

[atomic-wg] PR #436: Update meeting-people.txt
by Jared Smith 14 Mar '18

14 Mar '18

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

2 1

2wk atomic release candidate:20180314
by Sinny Kumari 14 Mar '18

14 Mar '18

Hi all, We couldn't send Release Candidate for testing earlier due to some issue with AMIs upload. Good news is that issue has been resolved and latest AMIs are available now! Tomorrow we will attempt to release the 20180314 images. These images contain the following ostree version/commits from the Fedora-27-updates-20180313.0 updates run: Version: 27.100 Commit(x86_64): 326f62b93a5cc836c97d31e73a71b6b6b6955c0f225f7651b52a693718e6aa91 Commit(aarch64): ba2aa19d99466c53e614651f014c8b97ae1940f87885b7c7dfed1fb62ae91567 Commit(ppc64le): ca0ea3a6e15b6270aefe3c7b55ffbee3c8bd27707fd6d979cc66b39fc18fa5f4 The atomic host VM images are in the sub-directories under: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-27-2018031… The ISO images are in the sub-directories under: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-27-2018031… The AMIs are here: Fedora-Atomic-27-20180314.0.x86_64 EC2 (us-west-2) ami-a468f8dc hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (us-west-1) ami-c20612a2 hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (us-east-1) ami-a112d1dc hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (sa-east-1) ami-8d5401e1 hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (eu-west-1) ami-e3a8e19a hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (eu-central-1) ami-452e452a hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (ap-southeast-2) ami-c022e1a2 hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (ap-southeast-1) ami-432d7d3f hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (ap-northeast-1) ami-0a5e146c hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (us-west-2) ami-916afae9 hvm gp2 Fedora-Atomic-27-20180314.0.x86_64 EC2 (us-west-1) ami-30071350 hvm gp2 Fedora-Atomic-27-20180314.0.x86_64 EC2 (us-east-1) ami-3e16d543 hvm gp2 Fedora-Atomic-27-20180314.0.x86_64 EC2 (sa-east-1) ami-d75702bb hvm gp2 Fedora-Atomic-27-20180314.0.x86_64 EC2 (eu-west-1) ami-31a8e148 hvm gp2 Fedora-Atomic-27-20180314.0.x86_64 EC2 (eu-central-1) ami-bd2f44d2 hvm gp2 Fedora-Atomic-27-20180314.0.x86_64 EC2 (ap-southeast-2) ami-c623e0a4 hvm gp2 Fedora-Atomic-27-20180314.0.x86_64 EC2 (ap-southeast-1) ami-f32f7f8f hvm gp2 Fedora-Atomic-27-20180314.0.x86_64 EC2 (ap-northeast-1) ami-c85d17ae hvm gp2 An example of the diff between this and the previous released version (for x86_64) is: ostree diff commit old: da0bd968610aa1e29c5bb37065649407fbbfffa53e63831afdadbd34a3b05327 ostree diff commit new: 326f62b93a5cc836c97d31e73a71b6b6b6955c0f225f7651b52a693718e6aa91 Upgraded: atomic 1.21.1-1.fc27 -> 1.22.1-1.fc27 atomic-registries 1.21.1-1.fc27 -> 1.22.1-1.fc27 audit 2.8.2-1.fc27 -> 2.8.3-1.fc27 audit-libs 2.8.2-1.fc27 -> 2.8.3-1.fc27 audit-libs-python 2.8.2-1.fc27 -> 2.8.3-1.fc27 audit-libs-python3 2.8.2-1.fc27 -> 2.8.3-1.fc27 bridge-utils 1.5-16.fc27 -> 1.6-1.fc27 ceph-common 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 cockpit-bridge 161-1.fc27 -> 163-1.fc27 cockpit-docker 161-1.fc27 -> 163-1.fc27 cockpit-networkmanager 161-1.fc27 -> 163-1.fc27 dhcp-client 12:4.3.6-8.fc27 -> 12:4.3.6-9.fc27 dhcp-common 12:4.3.6-8.fc27 -> 12:4.3.6-9.fc27 dhcp-libs 12:4.3.6-8.fc27 -> 12:4.3.6-9.fc27 dnsmasq 2.78-2.fc27 -> 2.78-6.fc27 fedora-gpg-keys 27-1 -> 27-2 fedora-repos 27-1 -> 27-2 glibc 2.26-24.fc27 -> 2.26-27.fc27 glibc-all-langpacks 2.26-24.fc27 -> 2.26-27.fc27 glibc-common 2.26-24.fc27 -> 2.26-27.fc27 gnupg2 2.2.4-1.fc27 -> 2.2.5-1.fc27 gnupg2-smime 2.2.4-1.fc27 -> 2.2.5-1.fc27 ima-evm-utils 1.0-3.fc27 -> 1.1-2.fc27 kernel 4.15.4-300.fc27 -> 4.15.8-300.fc27 kernel-core 4.15.4-300.fc27 -> 4.15.8-300.fc27 kernel-modules 4.15.4-300.fc27 -> 4.15.8-300.fc27 libblkid 2.30.2-1.fc27 -> 2.30.2-2.fc27 libcephfs2 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 libcrypt-nss 2.26-24.fc27 -> 2.26-27.fc27 libfdisk 2.30.2-1.fc27 -> 2.30.2-2.fc27 libgcc 7.3.1-2.fc27 -> 7.3.1-5.fc27 libgomp 7.3.1-2.fc27 -> 7.3.1-5.fc27 libidn2 2.0.4-1.fc27 -> 2.0.4-3.fc27 libmount 2.30.2-1.fc27 -> 2.30.2-2.fc27 librados2 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 libradosstriper1 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 librbd1 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 libreport-filesystem 2.9.3-1.fc27 -> 2.9.3-2.fc27 librgw2 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 libsmartcols 2.30.2-1.fc27 -> 2.30.2-2.fc27 libsolv 0.6.31-1.fc27 -> 0.6.33-1.fc27 libsss_idmap 1.16.0-6.fc27 -> 1.16.0-8.fc27 libsss_nss_idmap 1.16.0-6.fc27 -> 1.16.0-8.fc27 libsss_sudo 1.16.0-6.fc27 -> 1.16.0-8.fc27 libstdc++ 7.3.1-2.fc27 -> 7.3.1-5.fc27 libunistring 0.9.7-3.fc27 -> 0.9.9-1.fc27 libuuid 2.30.2-1.fc27 -> 2.30.2-2.fc27 mpfr 3.1.5-5.fc27 -> 3.1.6-1.fc27 nspr 4.17.0-1.fc27 -> 4.18.0-1.fc27 nss 3.34.0-1.0.fc27 -> 3.35.0-1.1.fc27 nss-softokn 3.34.0-1.0.fc27 -> 3.35.0-1.0.fc27 nss-softokn-freebl 3.34.0-1.0.fc27 -> 3.35.0-1.0.fc27 nss-sysinit 3.34.0-1.0.fc27 -> 3.35.0-1.1.fc27 nss-tools 3.34.0-1.0.fc27 -> 3.35.0-1.1.fc27 nss-util 3.34.0-1.0.fc27 -> 3.35.0-1.0.fc27 p11-kit 0.23.9-2.fc27 -> 0.23.10-1.fc27 p11-kit-trust 0.23.9-2.fc27 -> 0.23.10-1.fc27 pcre 8.41-5.fc27 -> 8.41-6.fc27 pcre2 10.30-6.fc27 -> 10.31-1.fc27 policycoreutils 2.7-4.fc27 -> 2.7-5.fc27 policycoreutils-python 2.7-4.fc27 -> 2.7-5.fc27 policycoreutils-python-utils 2.7-4.fc27 -> 2.7-5.fc27 policycoreutils-python3 2.7-4.fc27 -> 2.7-5.fc27 publicsuffix-list-dafsa 20171228-1.fc27 -> 20180223-1.fc27 python-cephfs 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 python-rados 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 python-rbd 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 python-rgw 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 python2 2.7.14-7.fc27 -> 2.7.14-8.fc27 python2-libs 2.7.14-7.fc27 -> 2.7.14-8.fc27 python3-sssdconfig 1.16.0-6.fc27 -> 1.16.0-8.fc27 runc 2:1.0.0-17.rc4.git9f9c962.fc27 -> 2:1.0.0-19.rc5.git4bb1fe4.fc27 selinux-policy 3.13.1-283.24.fc27 -> 3.13.1-283.26.fc27 selinux-policy-targeted 3.13.1-283.24.fc27 -> 3.13.1-283.26.fc27 sssd-client 1.16.0-6.fc27 -> 1.16.0-8.fc27 subscription-manager-rhsm-certificates 1.21.1-1.fc27 -> 1.21.2-3.fc27 systemd 234-9.fc27 -> 234-10.git5f8984e.fc27 systemd-container 234-9.fc27 -> 234-10.git5f8984e.fc27 systemd-libs 234-9.fc27 -> 234-10.git5f8984e.fc27 systemd-pam 234-9.fc27 -> 234-10.git5f8984e.fc27 systemd-udev 234-9.fc27 -> 234-10.git5f8984e.fc27 util-linux 2.30.2-1.fc27 -> 2.30.2-2.fc27 vim-minimal 2:8.0.1527-1.fc27 -> 2:8.0.1573-1.fc27 xfsprogs 4.12.0-4.fc27 -> 4.15.1-1.fc27 Removed: cockpit-system-161-1.fc27.noarch Added: cockpit-ostree-163-1.fc27.noarch Please test it to ensure that latest Atomic Host is working for you as expected! Thanks, Sinny Kumari

1 0

[atomic-wg] Issue #427: Delete/Archive/Rename redundant resources: mailing lists, IRC channels
by Sanja Bonic 14 Mar '18

14 Mar '18

sanja reported a new issue against the project: `atomic-wg` that you are following: `` **Problem** We are confusing newcomers through redundant/unused resources that are mentioned in various places - we need to clean up and make the start more welcoming. **Actions** * delete/archive/rename redundant resources **Goals** * community growth - both users and contributors * new healthy and active baseline to operate from --- **Proposed Changes** Please express your opinions in the comments. If you have no comments, just vote with a "+1". ***Mailing Lists*** * delete the two unused mailing lists (delete atomic-announce and atomic, keep just atomic-devel(a)projectatomic.io and rename atomic-devel to just atomic) ***IRC Channels*** * rename (or delete it not used) #fedora-atomic as people stumble upon it and ask questions there - it's more intuitive to send them to #atomic directly if there is no #fedora-atomic (if #fedora-atomic is being used but it's more for release engineering/build problems, whoever is responsible for it, please rename it so that people who want to contribute/get support for Atomic don't stumble on it) `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/427

6 15

[atomic-wg] Issue #435: Tag etcd images registry.fedoraproject.org/latest/etcd to match etcd version
by Michael Gugino 13 Mar '18

13 Mar '18

michaelgugino reported a new issue against the project: `atomic-wg` that you are following: `` Tags should match etcd version, if possible. This will help openshift origin users get the correct version of etcd. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/435

1 0

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

13 Mar '18

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2018-03-14 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 #434: Keyboard selection from anaconda installer is not preserved
by Jonathan Lebon 12 Mar '18

12 Mar '18

jlebon reported a new issue against the project: `atomic-wg` that you are following: `` During installation, an alternate key board is chosen (IE dvorak). This setting is not used post-install. Steps to Reproduce: 1. Install atomic host with an alternate keyboard 2. reboot 3. keyboard layout is not used post installation. Migrated from https://bugzilla.redhat.com/show_bug.cgi?id=1430180 for upstream discussions. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/434

2 1

[atomic-wg] Issue #429: 20180309: Topics for march VFAD
by Dusty Mabe 09 Mar '18

09 Mar '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` We would like to have a VFAD (virtual Fedora Activity Day) on March 9th at approximately [Fri Mar 9 15:00:00 UTC 2018](https://www.worldtimebuddy.com/?qm=1&lid=100,5,4839366&h=100&date=201… Proposed topics for the VFAD include: - [rpm-ostree rojig](https://github.com/projectatomic/rpm-ostree/issues/1081) (special way of delivering ostree updates) - others? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/429

6 13

Atomic Working Group VFAD 03/09
by Dusty Mabe 08 Mar '18

08 Mar '18

Hi everyone, This is a reminder that tomorrow we have a VFAD (Virtual Fedora Activity Day) for everyone who can and wants to join in on the discussions: https://pagure.io/atomic-wg/issue/429 ------ Location: https://bluejeans.com/dmabe ------ Topics: [upstream technology] * rpm-ostree rojig - short presentation/demo [5 minutes] * rpm-ostree rojig - Q&A [ max 10 minutes ] * podman - pros/cons to including it in the host vs using as a container [ 10 minutes ] [community] * discussion on whether Project Atomic needs to step away from the "umbrella" and make it clear what it's about, spin off projects [ 40 minutes ] [Atomic Workstation] * suggestion for rebranding atomic workstation [ 20 minutes ] * dev/pet container tools - gather links to examples/docs [ 10 minutes ] * Minimizing content set in FAW [ 10 minutes ] o https://pagure.io/workstation-ostree-config/pull-request/74 [Q&A for users] * Q&A session for atomic host/workstation users [ 20 minutes ] ------ See you there, Atomic WG

2 1

[fedora-atomic] PR #116: Remove repos from the base ostree file
by Patrick "マルタインアンドレアス" Uiterwijk 08 Mar '18

08 Mar '18

puiterwijk opened a new pull-request against the project: `fedora-atomic` that you are following: `` Remove repos from the base ostree file `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/116

2 3

[fedora-atomic] PR #115: Split out updates-testing and -stable and -base
by Patrick "マルタインアンドレアス" Uiterwijk 08 Mar '18

08 Mar '18

puiterwijk opened a new pull-request against the project: `fedora-atomic` that you are following: `` Split out updates-testing and -stable and -base `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/115

3 4

Fedora Atomic WG Meeting Minutes 2018-03-07
by Dusty Mabe 07 Mar '18

07 Mar '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-07/fedora_atomic… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-07/fedora_atomic… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by dustymabe at 16:30:15 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-07/fedora_atomic… . Meeting summary - --------------- * roll call (dustymabe, 16:30:22) * previous meeting action items (dustymabe, 16:33:16) * a new f27 tools container was built (https://koji.fedoraproject.org/koji/buildinfo?buildID=1052335) and is in the registry at registry.fedoraproject.org/f27/tools (dustymabe, 16:35:27) * ACTION: davdunc to inform WG about AWS scan results of Fedora Atomic Host (dustymabe, 16:36:45) * 20180309: Topics for march VFAD (dustymabe, 16:40:44) * LINK: https://pagure.io/atomic-wg/issue/429 (dustymabe, 16:40:50) * LINK: https://public.etherpad-mozilla.org/p/topics (dustymabe, 16:54:04) * open floor (dustymabe, 17:15:27) * LINK: https://www.google.com/search?q=reply+hazy+try+again&tbm=isch (walters1, 17:17:53) * in fedora we moved to a unifed ostree repo structure: see https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-Mar… (dustymabe, 17:20:23) * misc has a working openshift config for host projectatomic docs (dustymabe, 17:22:00) * LINK: https://dustymabe.com/ says yes (dustymabe, 17:24:01) * ACTION: jlebon to write blog post for recent rpm-ostree/ostree releases features (dustymabe, 17:27:27) Meeting ended at 17:28:30 UTC. Action Items - ------------ * davdunc to inform WG about AWS scan results of Fedora Atomic Host * jlebon to write blog post for recent rpm-ostree/ostree releases features Action Items, by person - ----------------------- * jlebon * jlebon to write blog post for recent rpm-ostree/ostree releases features * **UNASSIGNED** * davdunc to inform WG about AWS scan results of Fedora Atomic Host People Present (lines said) - --------------------------- * dustymabe (126) * sanja_ (48) * zodbot (18) * lorbus (18) * walters1 (17) * miabbott (15) * misc (13) * jlebon (12) * rubao (8) * jbrooks (3) * kushal (1) * jligon (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlqgNOAACgkQMwLb1zlS 5nHtkQ/9GTr9r7tT2knwO6enHt1JUkvd3EqBovsQbqM2orvLADXpFhvquhLwQki0 AvHhxiwBxz9fatkUzdxn0MaK/nnb5X3COTp+VpOOXyObFkiWDz98zqKCUN+eElKt ZSQrPKeh15F0rqzE+hWdxYWAnePSOBSNDVapGhb/l/C7nSU7BltuHn7L1JTKjchc TP5Zb6rTgqyCnoF/r1ZQ5QhGMEtOsLqyEagjPhsTQdKWKlieJ4wDAYKnQr3MkULR tbUkzgOcvD46ncalm8kVWCQdzupq0KVrqMEyUvf73/TtSC+yUZX1GNRSnI6aqjdH b3Wly8oKeSqjMqU7xg3q24UaMVm20axKGGew0S2X/QPDTIjY835DuWSQiNWq3nX9 Aegnms680RmGqPscHPmVC0XgEuJMXFgu/BG+QVsujWTEHI/VSznZPRoiWmcUSb3P Evg8N7vKS2dWjJ4P8Zn9+W7KDhS6X7CCgdRSNn8t9NXjEbVaCOe1JDGEKbcbTx/b SRF8pLasRyDWiDuAiCE/IomqBn3YVuFQ30ayusebM3Al/A9RRHi1GXS+Tc6q2klL F3X/nUTuFwnNBL0/43U2b+cUIl2BG8zY7i57wK1MZDZ781pG5VNBxWQf0Ny0gU+U HkvOynA54bw6BGxtjFrUgANiA79cqcLOyiKS2p9Utj4BlXiBBnA= =SFGM -----END PGP SIGNATURE-----

1 0

[atomic-wg] Issue #426: Run dracut on atomic upgrades
by William Brown 07 Mar '18

07 Mar '18

firstyear reported a new issue against the project: `atomic-wg` that you are following: `` When you install a new rpm-ostree (ie upgrade) dracut should be run. This is to capture settings relevant to the hardware from files such as /etc/crypttab (discard via luks) or modprobe.d. Today, it would appear manually running dracut has no effect (?). This would be a great addition as it would then automate and allow hardware corrections for kernel modules - for me I have a macbook pro that requires quirks set to the sdhci card, but on atomic I need to modprobe -r/modprobe after restart to make them apply. Thanks, `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/426

3 8

[fedora-atomic] PR #113: python-docker-py is deprecated
by Dusty Mabe 07 Mar '18

07 Mar '18

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

2 3

Unified ostree repositories in Fedora
by Dusty Mabe 06 Mar '18

06 Mar '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 TL;DR: If you use f27 atomic workstation or rawhide atomic host/workstation then you need to add a new remote and rebase. [f27 atomic workstation] # ostree remote add --set=gpg-verify=true --set=gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-27-primary onerepo https://kojipkgs.fedoraproject.org/atomic/repo/ # rpm-ostree rebase onerepo: [rawhide atomic host/workstation] # ostree remote add --set=gpg-verify=true --set=gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-primary onerepo https://kojipkgs.fedoraproject.org/atomic/repo/ # rpm-ostree rebase onerepo: Hey Atomic Land, In Fedora we have migrated to using a single unified repository setup for our ostree repositories. This means that f28+ all releases will be served out of the same ostree repo. The repo will be located at https://kojipkgs.fedoraproject.org/atomic/repo/. If you are a current user of rawhide atomic host/workstation or a current user of f27 atomic workstation please run the above commands on your machine to move to the new repository setup. Current users of F27 Atomic Host don't need to do anything at this time. Please let us know if you have any questions! Dusty -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlqfF5sACgkQMwLb1zlS 5nFPcg/+OHkKWyQcNlulzpNdJyi8tGx3BtmYE5czibhYSJ2iVua6IK3JImI/SWt1 XPm1rtuz5Ldy+vdqLOv6VkGYLDLY6JPz/D6ovyRwAPs3ZXhAZiuws47ZNzQkPeDg lTTEswCRKb4CVJ0MhCUy12wqMBYecfv9eibvGD01v7vuxEK7e1Ck0/ogIOXGgWsC gLRj8SEd0f7dc9JTnipFe5NIQDa7I7vTwo3btFUUms4vxuGpctyrbYreKPC71XKG iyYHTISsOEk5PmghYg3CxoPzCjJsuFo3L6SBPrt734e3G9+dOMbNgaRFv3xFU6mN LVm9tr6FvFPYT64kidjAllIaxCciSvtDL3Qm6iaptwXeAFFw4q8I1O/jEMwPVfxY 5B2bqLUO+deWudAlcyquvS9ujttNtT/q201FselGLVGoEUZCzL+bt7hMPi5UAm46 wG2dZzrAMMKTu7vTUVNYIxjv96aMdXxpGbJRqn/+z9EPDFxdk904Nwrg5E/utx2R ta8WKGBnSkLqGxx06T7BcwlWZ5S6ismuIwyiHNfgjPJ2O+RtUQwVshdPDmgVE3rz AL4/0FqBHIHSBtvaKgR5V5R6Y021ARleQpyYb7F1hq5kipSkaneCXgPW0wMkE3Zs plLqrSVRB4RGElFT9NLrf6ykS5pkNRZTNnzXxviuPfuzsgt92cg= =x7VK -----END PGP SIGNATURE-----

1 0

[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

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

06 Mar '18

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2018-03-07 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 #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 #430: consider using quay.io container registry
by Dusty Mabe 01 Mar '18

01 Mar '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` In a few previous issues ([1](https://pagure.io/atomic-wg/issue/379) [2](https://pagure.io/atomic-wg/issue/381) [3](https://pagure.io/atomic-wg/issue/383) we had discussed our strategy regarding automated container builds in dockerhub. Now that we have friends with a hosted container registry we should consider pivoting and using quay.io instead. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/430

5 4

[atomic-wg] Issue #431: Set "disk.EnableUUID = True" in vSphere OVA for Atomic Host
by Chris Collins 01 Mar '18

01 Mar '18

clcollins reported a new issue against the project: `atomic-wg` that you are following: `` The vSphere Cloud Provider for Kubernetes/OpenShift requires that "disk.EnableUUID = True" be set for the node VMs to be able to identify the dynamically provisioned VMDKs that are mounted into the containers for dynamically created persistent storage volumes. (See: https://kubernetes.io/docs/getting-started-guides/vsphere/#enable-vsphere-c… ; and: https://docs.openshift.org/latest/install_config/configuring_vsphere.html#v…) Setting "disk.EnableUUID = True" allows disks to show up in /dev/disk/by-uuid when they're added to the VM. We can set it manually each time we create a new node, but the potential to forget is high, and the consequences would be unfortunate (pods would no longer be able to mount storage when scheduled on nodes without the setting). Considering a lot of the focus on Atomic Host is for Kubernetes & OpenShift, and folks using the vSphere OVA for Atomic would probably like to use the vSphere provisioning with it, this might make sense to be a default setting. Ideally this would apply to the Red Hat and CentOS Atomic OVAs as well. Included for more info: I asked about this in the #Atomic channel, and the replies mentioned - (03:10:36 PM) walters: it's going to involve changes to https://github.com/redhat-imaging/imagefactory/ most likely (03:11:35 PM) walters: specifically https://github.com/redhat-imaging/imagefactory/blob/master/imagefactory_plu… I believe `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/431

1 0

[atomic-wg] Issue #424: memcached and mariadb container not built for f27
by Clement Verna 01 Mar '18

01 Mar '18

cverna reported a new issue against the project: `atomic-wg` that you are following: `` The memcached and mariadb container were never built for f27. The last build for mariadb is mariadb-10.1-13.f26container and for memcached memcached-0-2.f26container_modular. Also memcached Dockerfile on the f27 is using the rawhide base image. https://src.fedoraproject.org/container/memcached/blob/f27/f/Dockerfile#_1 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/424

1 5

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) March 2018