October 2017 - 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 #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 #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 #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 #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 #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 #345: 20171003 ISO does not boot on minnowboard
by Josh Berkus 01 Feb '18

01 Feb '18

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

4 16

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

18 Jan '18

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

3 5

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) October 2017