May 2018 - Atomic Working Group - Fedora mailing-lists

[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 #469: AWS ImportVolume gets stuck mid way
by Sayan Chowdhury 28 Jun '18

28 Jun '18

sayanchowdhury reported a new issue against the project: `atomic-wg` that you are following: `` Here are a few import volumes which got stuck in last few days - * import-vol-fh6keksr * import-vol-ffuza9fb * import-vol-fgxmcpdg * import-vol-ffhkmpsx * import-vol-ffzdnft6 * import-vol-fgwb2cbw `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/469

4 4

[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

Fedora Atomic WG Meeting Minutes 2018-05-30
by Dusty Mabe 30 May '18

30 May '18

Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-05-30/fedora_atomic… Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2018-05-30/fedora_atomic… Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-05-30/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-05-30/fedora_atomic… . Meeting summary --------------- * roll call (dustymabe, 16:30:20) * previous meeting action items (dustymabe, 16:32:31) * ACTION: dusty/ashcrow/jberkus try to get community FAQ released around Atomic/CoreOS future (dustymabe, 16:33:07) * dustymabe opened https://pagure.io/atomic-wg/issue/502 to track flock submissions (dustymabe, 16:34:34) * ACTION: lorbus to write blog post about progress with Greeboot (dustymabe, 16:36:23) * ACTION: jdoss to write a blogpost about his ongoing work on Kernel Module support for Atomic on projectatomic blog (dustymabe, 16:37:44) * atomic working group talks/sessions for flock 2018 (dustymabe, 16:38:56) * LINK: https://pagure.io/atomic-wg/issue/502 (dustymabe, 16:39:12) * LINK: https://flocktofedora.org/ (dustymabe, 16:40:36) * please add talk ideas to #502 so we can coordinate talks for flock (dustymabe, 16:43:07) * open floor (dustymabe, 16:43:12) * sayan pushed a blog with ENA support: http://words.yudocaa.in/ena-support-now-in-fedora-amis (dustymabe, 16:44:36) * longer resource IDs for AMIs in EC2 soon - see https://github.com/fedora-infra/fedimg/issues/122 (dustymabe, 16:48:03) Meeting ended at 16:52:02 UTC. Action Items ------------ * dusty/ashcrow/jberkus try to get community FAQ released around Atomic/CoreOS future * lorbus to write blog post about progress with Greeboot * jdoss to write a blogpost about his ongoing work on Kernel Module support for Atomic on projectatomic blog Action Items, by person ----------------------- * jdoss * jdoss to write a blogpost about his ongoing work on Kernel Module support for Atomic on projectatomic blog * **UNASSIGNED** * dusty/ashcrow/jberkus try to get community FAQ released around Atomic/CoreOS future * lorbus to write blog post about progress with Greeboot People Present (lines said) --------------------------- * dustymabe (55) * zodbot (15) * jdoss (12) * sayan (6) * kushal (5) * ksinny (3) * miabbott (2) * strigazi (1) * rubao (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[atomic-wg] PR #504: remove _ari_ from list of people to ping
by Dusty Mabe 30 May '18

30 May '18

dustymabe opened a new pull-request against the project: `atomic-wg` that you are following: `` remove _ari_ from list of people to ping `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/pull-request/504

1 1

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group May 2018