February 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 #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 #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 #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 #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 #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

[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 #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 #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-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

[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 #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 #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

Fedora Atomic WG Meeting Minutes 2018-02-28
by Micah Abbott 28 Feb '18

28 Feb '18

summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-28/fedora_atomic… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-28/fedora_atomic… ================================================ #fedora-meeting-1: fedora_atomic_wg ================================================ Meeting started by miabbott_ at 16:32:04 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-28/fedora_atomic… . Meeting summary --------------- * roll call (miabbott_, 16:32:19) * previous meeting action items (miabbott_, 16:36:28) * opened ticket for VFAD: https://pagure.io/atomic-wg/issue/429 (dustymabe, 16:37:05) * quay.io discussion ticket: https://pagure.io/atomic-wg/issue/430 (dustymabe, 16:37:30) * ACTION: davdunc to inform WG about AWS scan results of Fedora Atomic Host (miabbott_, 16:39:23) * archive unused github repos - https://pagure.io/atomic-wg/issue/428 (miabbott_, 16:41:46) * LINK: https://meetbot.fedoraproject.org/sresults/?group_id=fedora_atomic_wg&type=… (misc, 16:42:59) * reduce redundant mailing lists + irc channels - https://pagure.io/atomic-wg/issue/427 (miabbott_, 16:43:20) * ACTION: ashcrow to ping tomas about building f27/tools container (miabbott_, 16:46:17) * march 9th vFAD (dustymabe, 16:49:27) * LINK: https://pagure.io/atomic-wg/issue/429 (dustymabe, 16:49:38) * ACTION: sanja_ to help make/stick to an agenda for next week's VFAD (dustymabe, 16:58:20) * open floor (miabbott_, 16:59:10) * FAW content changes - https://pagure.io/workstation-ostree-config/pull-requests?status=0 (miabbott_, 17:00:43) * sayan got fedimg on stg (miabbott_, 17:02:13) * sayan started work on having fedimg to use qcow2 directly - https://github.com/fedora-infra/fedimg/issues/64 (miabbott_, 17:10:54) * LINK: https://pagure.io/atomic-wg/issues?status=all&search_pattern=fedimg (dustymabe, 17:11:15) * Moved the ownership of the pagure repo to dustymabe (kushal, 17:12:23) Meeting ended at 17:14:56 UTC. Action Items ------------ * davdunc to inform WG about AWS scan results of Fedora Atomic Host * ashcrow to ping tomas about building f27/tools container * sanja_ to help make/stick to an agenda for next week's VFAD Action Items, by person ----------------------- * davdunc * davdunc to inform WG about AWS scan results of Fedora Atomic Host * sanja * sanja_ to help make/stick to an agenda for next week's VFAD * sanja_ * sanja_ to help make/stick to an agenda for next week's VFAD * **UNASSIGNED** * ashcrow to ping tomas about building f27/tools container People Present (lines said) --------------------------- * miabbott_ (54) * dustymabe (51) * zodbot (27) * walters1 (16) * sayan (13) * sanja_ (7) * misc (7) * kushal (6) * sanja (6) * bowlofeggs (4) * lorbus (4) * davdunc (4) * jberkus_ (3) * jbrooks (3) * ksinny (1) * jligon (1) * dustymab1 (1) * jlebon (1) * giuseppe (1) * jberkus (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[fedora-atomic] PR #112: Add support for s390x
by Sinny Kumari 28 Feb '18

28 Feb '18

sinnykumari opened a new pull-request against the project: `fedora-atomic` that you are following: `` Add support for s390x `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/112

2 1

[fedora-atomic] PR #111: Add support for s390x
by Sinny Kumari 28 Feb '18

28 Feb '18

sinnykumari opened a new pull-request against the project: `fedora-atomic` that you are following: `` Add support for s390x `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/111

4 4

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

27 Feb '18

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

[atomic-wg] Issue #420: driver blacklisting issue
by Olivier De Jonckere 26 Feb '18

26 Feb '18

olivierdj reported a new issue against the project: `atomic-wg` that you are following: `` Hello, I deploy in an Openstack cloud a kubernetes solution with Magnum (container orchestration service for Openstack) and gpu aware nodes/containers machine learning. As long as cuda 9.0 is available for fedora 25 only, and magnum doesn't support fedora 27, I naturally chose a fedora 25 atomic image for my cluster nodes. But I had a kernel panic with the nouveau driver on the fedora 25 guests, tried to disabling it, and never succeed. I tried again with a Fedora 27 atomic image and was able to disable nouveau without any problem. What is wrong with blacklisting on fedora 25 atomic? As long Openstack magnum and Nvidia cuda doesn't provide fedora 27 support I can't just switch to fedora 27. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/420

2 3

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

26 Feb '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Tomorrow we will attempt to release the 20180226 images. These images contain the following ostree version/commits from the Fedora-27-updates-20180225.0 updates run: Version: 27.93 Commit(x86_64): da0bd968610aa1e29c5bb37065649407fbbfffa53e63831afdadbd34a3b05327 Commit(aarch64): 6607b02ff08bd0f0fc488772b398c25de28345a0bda0508ef45b433b91839ccd Commit(ppc64le): 848b618bd36e8b03bbcedf2d9ff881450440d8434f62cdb80006d3e899ebaa28 The atomic host VM images are in the sub-directories under: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-27-2018022… The ISO images are in the sub-directories under: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-27-2018022… The AMIs are here: Fedora-Atomic-27-20180226.0.x86_64 EC2 (us-west-2) ami-5840c920 hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (us-west-1) ami-202d2640 hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (us-east-1) ami-068b627b hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (sa-east-1) ami-dbd79fb7 hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (eu-west-1) ami-273f455e hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (eu-central-1) ami-3d1e7352 hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (ap-southeast-2) ami-4b844229 hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (ap-southeast-1) ami-ab541cd7 hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (ap-northeast-1) ami-2b1e594d hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (us-west-2) ami-dd4fc6a5 hvm gp2 Fedora-Atomic-27-20180226.0.x86_64 EC2 (us-west-1) ami-242d2644 hvm gp2 Fedora-Atomic-27-20180226.0.x86_64 EC2 (us-east-1) ami-2b8d6456 hvm gp2 Fedora-Atomic-27-20180226.0.x86_64 EC2 (sa-east-1) ami-86d59dea hvm gp2 Fedora-Atomic-27-20180226.0.x86_64 EC2 (eu-west-1) ami-983a40e1 hvm gp2 Fedora-Atomic-27-20180226.0.x86_64 EC2 (eu-central-1) ami-911c71fe hvm gp2 Fedora-Atomic-27-20180226.0.x86_64 EC2 (ap-southeast-2) ami-4884422a hvm gp2 Fedora-Atomic-27-20180226.0.x86_64 EC2 (ap-southeast-1) ami-cd551db1 hvm gp2 Fedora-Atomic-27-20180226.0.x86_64 EC2 (ap-northeast-1) ami-ed1d5a8b hvm gp2 An example of the diff between this and the previous released version (for x86_64) is: ostree diff commit old: b25bde0109441817f912ece57ca1fc39efc60e6cef4a7a23ad9de51b1f36b742 ostree diff commit new: da0bd968610aa1e29c5bb37065649407fbbfffa53e63831afdadbd34a3b05327 Upgraded: bash 4.4.12-13.fc27 -> 4.4.19-1.fc27 ca-certificates 2017.2.20-1.0.fc27 -> 2018.2.22-1.0.fc27 container-selinux 2:2.44-1.fc27 -> 2:2.48-1.fc27 coreutils 8.27-19.fc27 -> 8.27-20.fc27 coreutils-common 8.27-19.fc27 -> 8.27-20.fc27 findutils 1:4.6.0-14.fc27 -> 1:4.6.0-16.fc27 freetype 2.8-7.fc27 -> 2.8-8.fc27 glusterfs 3.12.5-1.fc27 -> 3.12.6-2.fc27 glusterfs-client-xlators 3.12.5-1.fc27 -> 3.12.6-2.fc27 glusterfs-fuse 3.12.5-1.fc27 -> 3.12.6-2.fc27 glusterfs-libs 3.12.5-1.fc27 -> 3.12.6-2.fc27 gnutls 3.5.17-1.fc27 -> 3.5.18-2.fc27 grub2-common 1:2.02-19.fc27 -> 1:2.02-22.fc27 grub2-efi-x64 1:2.02-19.fc27 -> 1:2.02-22.fc27 grub2-pc 1:2.02-19.fc27 -> 1:2.02-22.fc27 grub2-pc-modules 1:2.02-19.fc27 -> 1:2.02-22.fc27 grub2-tools 1:2.02-19.fc27 -> 1:2.02-22.fc27 grub2-tools-extra 1:2.02-19.fc27 -> 1:2.02-22.fc27 grub2-tools-minimal 1:2.02-19.fc27 -> 1:2.02-22.fc27 ima-evm-utils 1.0-2.fc27 -> 1.0-3.fc27 iproute 4.14.1-4.fc27 -> 4.15.0-1.fc27 iproute-tc 4.14.1-4.fc27 -> 4.15.0-1.fc27 kernel 4.14.18-300.fc27 -> 4.15.4-300.fc27 kernel-core 4.14.18-300.fc27 -> 4.15.4-300.fc27 kernel-modules 4.14.18-300.fc27 -> 4.15.4-300.fc27 krb5-libs 1.15.2-4.fc27 -> 1.15.2-7.fc27 ostree 2018.1-1.fc27 -> 2018.2-1.fc27 ostree-grub2 2018.1-1.fc27 -> 2018.2-1.fc27 ostree-libs 2018.1-1.fc27 -> 2018.2-1.fc27 python2 2.7.14-6.fc27 -> 2.7.14-7.fc27 python2-libs 2.7.14-6.fc27 -> 2.7.14-7.fc27 python3 3.6.4-7.fc27 -> 3.6.4-8.fc27 python3-libs 3.6.4-7.fc27 -> 3.6.4-8.fc27 rpm-ostree 2018.1-2.fc27 -> 2018.3-1.fc27 rpm-ostree-libs 2018.1-2.fc27 -> 2018.3-1.fc27 skopeo 0.1.27-1.git93876ac.fc27 -> 0.1.28-1.git0270e56.fc27 skopeo-containers 0.1.27-1.git93876ac.fc27 -> 0.1.28-1.git0270e56.fc27 strace 4.20-1.fc27 -> 4.21-1.fc27 vim-minimal 2:8.0.1478-1.fc27 -> 2:8.0.1527-1.fc27 Removed: compat-openssl10-1:1.0.2m-1.fc27.x86_64 We have a new kernel (4.15), ostree [1] , and rpm-ostree [2]. Happy testing! Dusty [1] https://github.com/ostreedev/ostree/releases/tag/v2018.2 [2] https://github.com/projectatomic/rpm-ostree/releases/tag/v2018.3 -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlqURtMACgkQMwLb1zlS 5nHizw/9HLx/gXpFlkikQzo5+wmJ0ONUUZmu7SBSePlR6UUYUdLlCLsxwUOzWGg5 it4cW7oOwOldMipLH0eaYoTgWgKJfCM0PVRS2blsZ/gNaDvD7Qq/4LJ2RlAQaixY ZwBFivuKGlUggMYEtW0N7kC2K1BDnkxinmtH+/uRQYJ5ftbMRGxK5kjAzbFHt45d GYPvpL+bd5pQZ8+Kq3O7T9axpkdCJx1UK0ljZ+anoRYYYpK9OZvWE7UgOFudgC6I r6Trh6PyEVNVZj/nozpzgwZCWrli+yQ2lHnS9wpcrc6/2qz6X4sn/PMs6FWPnwIA j0mDsoHE7h6NFeFFlLy7E3P4aun3KC3rg+8CIsauqQ5eDHsp5EQ4FDOXtY/u8plA TxDDVbgtVDTtSD2iUCiS5jpk53tfBKaZ3e7GD/XmLN2FFnn1ifG1O1FNJwarcWR7 MGSajIxn06/krcdRdiHLH8lS0gvQmPrUQMqQSvyDjVxqRoITJcEdwDGIQd4MtUj8 UpM1EFfk9fcQp47d1xgk89qGDdLfTX2AC9/k9O2KrI8sBaZ0oi6eWJtYdN9S+rtp qfmQLiLB/0HYaWuJjYLbQFAnEk0kuRVxsrcpnoC70zI7hJRknVXDtlf+SeVg7VpL icnKp/kHsXV8KNN/gNL6Uq1RgjJX92DS/KkDnWB95XNvaMGu1jw= =Xia2 -----END PGP SIGNATURE-----

1 0

[fedora-atomic] Issue #110: Request to review release blocking deliverables of F28
by Jan Kurik 26 Feb '18

26 Feb '18

jkurik reported a new issue against the project: `fedora-atomic` that you are following: `` I would like to ask for a review of Release blocking deliverables [1] for F28 release delivered by Atomic (Cloud) WG. Please let me know in case of missing images, or in case the "blocking" status has changed since the last release. [1] https://fedoraproject.org/wiki/Releases/28/ReleaseBlocking#Cloud `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/issue/110

2 1

Fedora Atomic WG Meeting Minutes 2018-02-21
by Micah Abbott 21 Feb '18

21 Feb '18

suimmary: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-21/fedora_atomic… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-21/fedora_atomic… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by miabbott at 16:30:25 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-21/fedora_atomic… . Meeting summary --------------- * roll call (miabbott, 16:31:44) * previous meeting action items (miabbott, 16:35:17) * ACTION: dustymabe to schedule february VFAD a CFP for proposed topics (dustymabe, 16:36:25) * working with dockerhub members and new members and will give/revoke access (dustymabe, 16:36:53) * AWS scans of Fedora Atomic Host still pending completion (miabbott, 16:39:48) * ACTION: davdunc to inform WG about AWS scan results of Fedora Atomic Host (miabbott, 16:40:19) * riot/irc tutorial is written, will be published when new web site is announced (miabbott, 16:43:17) * ACTION: sanja to create ticket about elminating redundancy in mailing lists + irc channels (miabbott, 16:45:49) * ACTION: sanja to create ticket about archiving unused projectatomic github repos (miabbott, 16:46:09) * ACTION: misc to open ticket on the irc bot (miabbott, 16:49:00) * Design Meetings over Video (miabbott, 16:49:03) * LINK: https://pagure.io/atomic-wg/issue/418 (miabbott, 16:49:05) * Identify users for docker hub auto builds for system containers (miabbott, 16:52:54) * LINK: https://pagure.io/atomic-wg/issue/379 (miabbott, 16:52:56) * open floor (miabbott, 16:54:46) * ACTION: ashcrow to ping tomas about building f27/tools container (miabbott, 17:04:41) * ACTION: dusty to open ticket to start discussion about quay.io (dustymabe, 17:08:14) * LINK: https://pagure.io/fedora-comps/pull-request/220 (walters1, 17:09:55) * LINK: https://pagure.io/workstation-ostree-config/pull-request/70 (walters1, 17:10:03) * LINK: https://pagure.io/workstation-ostree-config/pull-request/64 (walters1, 17:10:39) * vote on new project atomic logo on mailing list or twitter (miabbott, 17:11:37) * LINK: https://twitter.com/projectatomic/status/965689983490195456 (miabbott, 17:11:41) * LINK: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-Feb… (miabbott, 17:11:46) * recent changes affecting fedora atomic workstation (miabbott, 17:13:19) * LINK: https://pagure.io/fedora-comps/pull-request/220 (miabbott, 17:13:22) * LINK: https://pagure.io/workstation-ostree-config/pull-request/70 (miabbott, 17:13:25) * LINK: https://pagure.io/workstation-ostree-config/pull-request/64 (miabbott, 17:13:32) * first Fedora Atomic Workstation SIG meeting was held on Monday Feb 19 (miabbott, 17:15:02) * LINK: https://fedoraproject.org/wiki/Workstation/AtomicWorkstation/SIG/Notes (miabbott, 17:15:03) * jessfraz working on something that could overlap with buildah (miabbott, 17:17:04) * LINK: https://twitter.com/jessfraz/status/966057711552094209 (miabbott, 17:17:09) * LINK: https://github.com/cyphar/orca-build (miabbott, 17:18:07) * LINK: https://getfedora.org/en/atomic/ this looks like a logo to me. (sanja, 17:19:20) * please contribute content to the new web site (miabbott, 17:26:08) * LINK: https://github.com/projectatomic/atomic-site-new (miabbott, 17:26:10) * tools container PR from action item (ashcrow, 17:29:11) * LINK: https://src.fedoraproject.org/container/tools/pull-request/2 (ashcrow, 17:29:23) * LINK: http://new.projectatomic.io/ (sanja, 17:32:25) Meeting ended at 17:32:36 UTC. Action Items ------------ * dustymabe to schedule february VFAD a CFP for proposed topics * davdunc to inform WG about AWS scan results of Fedora Atomic Host * sanja to create ticket about elminating redundancy in mailing lists + irc channels * sanja to create ticket about archiving unused projectatomic github repos * misc to open ticket on the irc bot * ashcrow to ping tomas about building f27/tools container * dusty to open ticket to start discussion about quay.io Action Items, by person ----------------------- * ashcrow * ashcrow to ping tomas about building f27/tools container * davdunc * davdunc to inform WG about AWS scan results of Fedora Atomic Host * dustymabe * dustymabe to schedule february VFAD a CFP for proposed topics * sanja * sanja to create ticket about elminating redundancy in mailing lists + irc channels * sanja to create ticket about archiving unused projectatomic github repos * **UNASSIGNED** * misc to open ticket on the irc bot * dusty to open ticket to start discussion about quay.io People Present (lines said) --------------------------- * miabbott (87) * sanja (75) * dustymabe (54) * ashcrow (32) * lorbus (26) * zodbot (20) * jbrooks (19) * walters1 (11) * giuseppe (7) * walters (6) * davdunc (4) * rubao|laptop (2) * jlebon (1) * sayan (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[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

[fedora-atomic] PR #108: Branching F28 from rawhide
by Mohan Boddu 20 Feb '18

20 Feb '18

mohanboddu opened a new pull-request against the project: `fedora-atomic` that you are following: `` Branching F28 from rawhide `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/108

2 1

[fedora-atomic] PR #109: Setup for Rawhide being Fedora 29
by Mohan Boddu 20 Feb '18

20 Feb '18

mohanboddu opened a new pull-request against the project: `fedora-atomic` that you are following: `` Setup for Rawhide being Fedora 29 `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/109

2 1

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

20 Feb '18

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2018-02-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 #425: Enable serial consoles in images
by William Brown 18 Feb '18

18 Feb '18

firstyear reported a new issue against the project: `atomic-wg` that you are following: `` It would be useful to have serial consoles as an option for centos/fedora atomic images in parallel to the current video consoles. This would open up options for installation of atomic on embedded and other systems that tend to use serial consoles. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/425

1 0

[atomic-wg] Issue #419: lua in glibc rpm breaks package layering in rawhide
by Dusty Mabe 18 Feb '18

18 Feb '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` @pwhalen reported an issue when trying to upgrade a rawhide system that has package layering: ``` [root@rpiii ~]# rpm-ostree upgrade 1 metadata, 0 content objects fetched; 569 B transferred in 1 seconds Checking out tree 25b4bbe... done Enabled rpm-md repositories: rawhide rpm-md repo 'rawhide' (cached); generated: 2018-02-04 09:02:29 Importing metadata [=============] 100% Resolving dependencies... done Applying 9 overlays Building filesystem (9/9) [=============] 100% Running pre scripts... [ 2074.161675] fuse init (API version 7.26) 1 done Running post scripts... error: Executing %transfiletriggerin for glibc: Package 'glibc' has (currently) unsupported <lua> script in '%transfiletriggerin' ``` This is because glibc [added a lua scriptlet](https://src.fedoraproject.org/rpms/glibc/c/6ff958f2aae58ce8d9199… which we currently [don't support](https://github.com/projectatomic/rpm-ostree/issues/749) We'll need to try to get that switched out so people can package layer in rawhide (and in f28). `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/419

2 5

[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 #423: Failed to start Create Volatile Files and Directories on ppc64le
by J McVicker 15 Feb '18

15 Feb '18

tux808 reported a new issue against the project: `atomic-wg` that you are following: `` Performed default install Fedora-Atomic-ostree 27-20180212.2 for ppc64le & x86_64 platforms. Both installed successfully, but first-boot on ppc64le edition fails with systemd error: Failed to start Create Volatile Files and Directories.. then dropped into emergency dracut:/# prompt. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/423

2 4

Fedora Atomic WG Meeting Minutes 2018-02-14
by Micah Abbott 14 Feb '18

14 Feb '18

=================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by miabbott at 16:31:01 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-14/fedora_atomic… . Meeting summary --------------- * roll call (miabbott, 16:31:18) * previous meeting action items (miabbott, 16:35:34) * dusty created ticket for evaluating podman in a few months (dustymabe, 16:36:08) * LINK: https://pagure.io/atomic-wg/issue/422 (dustymabe, 16:36:11) * LINK: https://pagure.io/atomic-wg/issue/421 (dustymabe, 16:37:24) * LINK: https://pagure.io/atomic-wg/issue/421 (miabbott, 16:37:27) * Design Meetings over Video (miabbott, 16:38:55) * LINK: https://pagure.io/atomic-wg/issue/418 (miabbott, 16:39:16) * ACTION: dustymabe to schedule february VFAD a CFP for proposed topics (dustymabe, 16:40:31) * Identify users for docker hub auto builds for system containers (miabbott, 16:41:33) * LINK: https://pagure.io/atomic-wg/issue/379 (miabbott, 16:41:40) * ACTION: dusty to send email to existing members of PA docker hub org and proposed new members to solidify membership (dustymabe, 16:51:48) * open floor (miabbott, 16:55:28) * update on AWS Marketplace: FAH 27.72 is making the way through preliminary scans. (miabbott, 16:57:53) * LINK: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/using-cloud-i… (jdoss, 16:58:38) * ACTION: davdunc to inform WG about AWS scan results of Fedora Atomic Host 27.72 (miabbott, 17:04:48) * waiting on input from mattdm about publishing Fedora images to Azure (miabbott, 17:07:03) * LINK: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-Feb… (dustymabe, 17:09:08) * a list of common problems affecting users: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-Feb… (dustymabe, 17:10:00) * common problems users are hitting with Atomic Host/Workstation (miabbott, 17:10:10) * LINK: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-Feb… (miabbott, 17:10:11) * submit ideas for docs/guides/faqs on projectatomic site (miabbott, 17:12:44) * LINK: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-Feb… (miabbott, 17:12:46) * LINK: https://github.com/projectatomic/atomic-site-new/tree/master/ideas (miabbott, 17:12:54) * the first Atomic Workstation SIG meeting will be on Monday 02/19 (dustymabe, 17:14:05) * LINK: https://fedoraproject.org/wiki/Workstation/AtomicWorkstation/SIG/Agenda (dustymabe, 17:14:12) * ACTION: sanja to create ticket on eliminating redundant mailing lists + irc channels (miabbott, 17:20:21) * ACTION: sanja to create irc tutorial to onboard newcomers from slack, etc (miabbott, 17:23:00) * ACTION: misc to open ticket on the irc bot (miabbott, 17:27:22) * LINK: https://fedoramagazine.org/3-fedora-videos-devconf-cz-2018/ (dustymabe, 17:29:09) * new Project Atomic site (miabbott, 17:29:22) * LINK: http://new.projectatomic.io/ (miabbott, 17:29:27) Meeting ended at 17:33:47 UTC. Action Items ------------ * dustymabe to schedule february VFAD a CFP for proposed topics * dusty to send email to existing members of PA docker hub org and proposed new members to solidify membership * davdunc to inform WG about AWS scan results of Fedora Atomic Host 27.72 * sanja to create ticket on eliminating redundant mailing lists + irc channels * sanja to create irc tutorial to onboard newcomers from slack, etc * misc to open ticket on the irc bot Action Items, by person ----------------------- * davdunc * davdunc to inform WG about AWS scan results of Fedora Atomic Host 27.72 * dustymabe * dustymabe to schedule february VFAD a CFP for proposed topics * misc * misc to open ticket on the irc bot * sanja * sanja to create ticket on eliminating redundant mailing lists + irc channels * sanja to create irc tutorial to onboard newcomers from slack, etc * **UNASSIGNED** * dusty to send email to existing members of PA docker hub org and proposed new members to solidify membership People Present (lines said) --------------------------- * dustymabe (93) * miabbott (78) * sanja (66) * ashcrow (37) * zodbot (28) * misc (18) * walters (17) * jbrooks (15) * davdunc (10) * jdoss (7) * giuseppe (7) * lorbus (6) * mclasen (5) * jlebon (4) * rubao (3) * imcleod (1) * strigazi (1) * ksinny (1) * gscrivano (0) * smilner (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

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

13 Feb '18

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

Fedora Atomic WG Meeting Minutes 2018-02-07
by Dusty Mabe 07 Feb '18

07 Feb '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-07/fedora_atomic… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-07/fedora_atomic… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by dustymabe at 16:31:42 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-07/fedora_atomic… . Meeting summary - --------------- * roll call (dustymabe, 16:31:48) * previous meeting action items (dustymabe, 16:35:47) * cri-o/podman in Atomic Host (dustymabe, 16:36:54) * LINK: https://pagure.io/atomic-wg/issue/407 (dustymabe, 16:37:10) * LINK: https://medium.com/cri-o/introducing-kpod-f06109b96374 (ashcrow, 16:42:31) * LINK: https://bodhi.fedoraproject.org/updates/FEDORA-2018-665045691d (miabbott, 16:46:27) * dwalsh | podman is just showing up in Fedora now, https://bodhi.fedoraproject.org/updates/FEDORA-2018-665045691d (dustymabe, 16:47:36) * ACTION: dustymabe to create new ticket for evaluating podman in a few months (dustymabe, 16:56:20) * Design Meetings over Video (dustymabe, 17:02:00) * LINK: https://pagure.io/atomic-wg/issue/418 (dustymabe, 17:02:08) * LINK: https://pagure.io/atomic-wg/blob/master/f/README.md (dustymabe, 17:06:47) * we'll try to have a few VFADs over the coming months to work through some design discussions surround system containers and also atomic host (dustymabe, 17:08:59) * open floor (dustymabe, 17:13:04) * submit ideas for new docs - https://github.com/projectatomic/atomic-site-new/tree/master/ideas (miabbott, 17:15:51) * we did an interview with linux unplugged to talk about fedora atomic host/workstation http://www.jupiterbroadcasting.com/122172/atomic-neon-kool-aid-lup-235/ (dustymabe, 17:15:56) * LINK: http://www.jupiterbroadcasting.com/122172/atomic-neon-kool-aid-lup-235/ (dustymabe, 17:16:02) * you can try out jigdo with Fedora Atomic Host Continuous - https://pagure.io/fedora-atomic-host-continuous (miabbott, 17:16:24) * devconf.us CFP is open (dustymabe, 17:16:56) * ACTION: sanja to create ticket in atomic-wg pagure for coordinating devconf.us talks (dustymabe, 17:18:16) * LINK: http://www.projectatomic.io/blog/2018/02/fedora-atomic-workstation/ (dustymabe, 17:24:53) * LINK: http://www.projectatomic.io/blog/2018/02/fedora-atomic-workstation/ (dustymabe, 17:24:58) Meeting ended at 17:28:28 UTC. Action Items - ------------ * dustymabe to create new ticket for evaluating podman in a few months * sanja to create ticket in atomic-wg pagure for coordinating devconf.us talks Action Items, by person - ----------------------- * dustymabe * dustymabe to create new ticket for evaluating podman in a few months * sanja * sanja to create ticket in atomic-wg pagure for coordinating devconf.us talks * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * dustymabe (156) * sanja (38) * ashcrow (36) * zodbot (34) * dwalsh (22) * miabbott (13) * jbrooks (12) * walters (10) * mrguitar (9) * lorbus (8) * misc (6) * davdunc (6) * giuseppe (5) * sayan (4) * clcollins (3) * jligon (2) * jlebon (2) * rubao|laptop (2) * puiterwijk (1) * strigazi (1) * gs (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlp7USUACgkQMwLb1zlS 5nHmrBAAzpjoRd0BueqplwcbKJSoUhYYGDoVwZLIHbo/bzoM5PpyYrx5BOfKOKGM CnSGeOUtgl/bK5dwerFnlKh3FebWSVMlIVwP82oSlZj9GLeAChnH3krgZF6t+bSf biXu5t/0EdZgEBvNUSxIdZqN/MRwk2Ut9NOuIsucfjTkQxRDpiyI1RfRgnl29OCO ZlT2U8DdOepG0CY+KgFtRE8xUpazaoq4pROCmjbFl4ZTfVEUr84NbMOn609Mq2FW pU0fMFer01sT6VMBYwDswFA/vSCrSyCn/Z09dpazgmYMjoJcF1mNNK3FZs5gAfBZ k/DNxkxqdmHiJRO70DmghbPVv9NNS0bidcR+1LhlnGvp7yLeYGF7RkA7Xo+gTDmb rSmber12JZ0Uh20vBUdK1RH0pvyifRhODuJuqmdGjlKh+mvW2tkXPTN6cgeaih0U TxL0/vPfxvWDheK9Nm65+PNrbY1bgKz4AKBdlOExfC8YOSWbRVosCvLfMX5wZe6g J1gFfyYNxbdtpW4x+toJwsEijoskpg2Zx/WVzXF/VppMEU5FPp80MiJManS9o//p mRoOhBCylPx6TK7FreXaysqoNbIIHUO82m99qzR1svP3F9CuvWbeLn1wEbHPRk7W X88542kxo59zu1WTBr4iidvFQSK1K4jA9uw7kaJnPHP/RolcB/0= =OftR -----END PGP SIGNATURE-----

1 0

[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

Fedora Atomic Workstation questions
by Elad Alfassa 07 Feb '18

07 Feb '18

Hi all, I have some questions regarding Fedora Atomic Workstation: 1) How do 3rd party repositories (such as ones providing nonfree drivers, which obviously can't be containerized) work with rpm-ostree? If our end goal is for users to be able to use Fedora Atomic Workstation for every usecase they use Fedora Workstation for today, we need a plan for this. One possible solution (which isn't exactly the most clean one, but it might work) is to allow /usr/local to be writable, and allow it to be managed with package management tools such as dnf. This will also be useful for legacy software which people still need to use, but can't be containerized easily. 3) I understand the benefit of containerizing my workstation. However, I'm not sure everything I do can be done in a container. For example, if I want to hack on a system-level DBus service. What's the proposed workflow for this? keep in mind I don't want to just make temporary changes that'll disappear after a reboot, because I want to be able to use my service even if it never finds its way into Fedora proper (since it probably won't). Am I supposed to create a container and expose DBus (and other system stuff my service might need) to the container? And what if I want to hack on the container runtime itself? :) 4) If I have a container for development, this means that I have to have two copies of coreutils, openssh, and most system libraries/utilities. One copy, the "host", is updated by rpm-ostree. But what about the copy on the container? I'll have to remember to manually rebuild it on every update, or manually run "dnf update" in the container, which is not ideal (i'll probably forget, and end up running insecure/buggy software). Would it be possible to build a container based on the host filesystem in such a way that all basic system libraries and utilities are accessible directly (not as a copy) for the container? Alternatively, would some mechanism for automatic re-building of the container images after every ostree update is done can be created? 5) Do we expect every developer using Fedora to write their own Dockerfile / Buildah script for their development environment? I think that's a bit too much overhead and we need to at least have a utility to automatically generate these based on some common configurations, and the usage might look something like create_dev_container --langauges=rust,python,c --additional-packages=ffmpeg I like the idea of Atomic Workstation, and I want it to become our default offering one day, but I think that before we get there we have to figure out this kind of stuff. (Maybe you already did and I just missed the documentation?) Thanks, -- -Elad.

2 1

[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

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

06 Feb '18

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

[atomic-wg] Issue #417: Add HyperV and VMWare pv storage modules to the default initrd for Atomic host
by Ian McLeod 01 Feb '18

01 Feb '18

imcleod reported a new issue against the project: `atomic-wg` that you are following: `` In order for Atomic Host to work (or work well) on VMWare and HyperV, we need the PV storage drivers for these platforms in the initrd. These two modules are: vmw_pvscsi hv_storvsc Together they are less than 20 kb of additional file content. Can we add these to the default ostree configuration and, once this is done, enable the creation of HyperV and VMWare fusion vagrant boxes for Atomic Host? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/417

3 4

[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

2025

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) February 2018