cloud May 2017

cloud@lists.fedoraproject.org

13 participants
83 discussions

firewalld in atomic host
by Dusty Mabe 01 Nov '17

01 Nov '17

NOTE: if you respond to this message please 'reply-all'. I'd like to discuss firewalld on atomic host. Recently I was trying to figure out the best way to explain to other users how to set firewall rules on atomic host. Usually I would say add your rules and then iptables-save, but on Atomic Host docker has added it's firewall rules in there dynamically so if you iptables-save you'll get a bunch of stuff that you don't want in your static configuration. There are ways around this; manually create your config file, or use iptables-save and then rip the docker stuff out. Either way it's a bit of a pain. I think firewalld would make this easier on the user. Not sure of the pro/con ratio though. Thoughts? Dusty

4 8

Fedora Atomic Host Two Week Release Announcement
by noreply＠fedoraproject.org 26 Jul '17

26 Jul '17

A new Fedora Atomic Host update is available via an OSTree commit: Commit: 3fd888c674c6d69907eabc665103341e01ebe3a04c3876af6cac673b0bf43662 Version: 25.122 Existing systems can be upgraded in place via e.g. `atomic host upgrade` or `atomic host deploy`. Corresponding image media for new installations can be downloaded from: https://getfedora.org/en/atomic/download/ Respective signed CHECKSUM files can be found here: https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-201705… https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-201705… For direct download, the "latest" targets are always available here: https://getfedora.org/atomic_iso_latest https://getfedora.org/atomic_qcow2_latest https://getfedora.org/atomic_raw_latest https://getfedora.org/atomic_vagrant_libvirt_latest https://getfedora.org/atomic_vagrant_virtualbox_latest Filename fetching URLs are available here: https://getfedora.org/atomic_iso_latest_filename https://getfedora.org/atomic_qcow2_latest_filename https://getfedora.org/atomic_raw_latest_filename https://getfedora.org/atomic_vagrant_libvirt_latest_filename https://getfedora.org/atomic_vagrant_virtualbox_latest_filename For more information about the latest targets, please reference the Fedora Cloud Wiki space. https://fedoraproject.org/wiki/Cloud#Quick_Links Do note that it can take some of the mirrors up to 12 hours to "check-in" at their own discretion. Thank you, Fedora Release Engineering

2 2

[atomic-wg] Issue #271: support ENA for fedimg upload
by Dusty Mabe 16 Jul '17

16 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` https://aws.amazon.com/blogs/aws/elastic-network-adapter-high-performance-n… we support this in our kernel so we should probably enable it. We need to: 1 - enable it in fedimg and underlying tools if needed 2 - see if having it enabled on all AMIs affects being able to launch on certain instance types (we would like to be able to enable it on all AMIs and just have it be a no-op on instances that don't support it. cc @sayanchowdhury `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/271

1 4

[atomic-wg] Issue #215 `Move redis httpd container image from Fedora-Dockerfiles GitHub into DistGit`
by Adam Miller 14 Jul '17

14 Jul '17

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/redis `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/215

3 5

[atomic-wg] Issue #210 `Move systemd-systemd container image from Fedora-Dockerfiles GitHub into DistGit`
by Adam Miller 14 Jul '17

14 Jul '17

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/systemd/syst… `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/210

2 1

[atomic-wg] Issue #218 `Move postgresql container image from Fedora-Dockerfiles GitHub into DistGit`
by Adam Miller 14 Jul '17

14 Jul '17

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/postgresql `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/218

3 2

[atomic-wg] Issue #222 `Move systemd-apache httpd container image from Fedora-Dockerfiles GitHub into DistGit`
by Adam Miller 14 Jul '17

14 Jul '17

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/systemd/apac… `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/222

3 2

[atomic-wg] Issue #203 `Move apache httpd container image from Fedora-Dockerfiles GitHub into DistGit`
by Adam Miller 14 Jul '17

14 Jul '17

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/apache `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/203

2 2

[atomic-wg] Issue #208 `Move mariadb container image from Fedora-Dockerfiles GitHub into DistGit`
by Adam Miller 14 Jul '17

14 Jul '17

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/mariadb `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/208

4 4

[atomic-wg] Issue #229 `decide on version scheme and image naming scheme for f26`
by Dusty Mabe 14 Jul '17

14 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` We are now *releasing* OSTree content every two weeks rather than every night ([link](http://www.projectatomic.io/blog/2017/02/matching-fedora-ostree-released-content-with-each-2week-atomic-release/)). Next we would like to make the image names that get produced reflect in some way the OSTree content that is baked into the image. During recent development @jlebon actually suggested that we use date based versions for Fedora Atomic Host: something like `version: 20170130.0`, `version: 20170130.1`, `version: 20170215.0`, etc... Let's decide on what we want the versioning scheme to look like and also what the image names "could look like" as a result of this. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/229

6 16

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud May 2017