July 2017 - cloud - Fedora mailing-lists

[atomic-wg] Issue #171: [VOTE] To mark recent failure on Atomic images as non blocking
by Dusty Mabe 14 Jul '17

14 Jul '17

The status of the issue: `[VOTE] To mark recent failure on Atomic images as non blocking` of project: `atomic-wg` has been updated to: Closed by dustymabe. https://pagure.io/atomic-wg/issue/171

1 0

[atomic-wg] Issue #184 `ISO file is missing`
by Pagure 14 Jul '17

14 Jul '17

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` Try to download the ISO at this location, as supplied by GetFedora.org: https://download.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-2… You'll find that there is no file there, and your download does not start. There is currently no way to download the Atomic ISO. In fact, it appears that none of the alternate downloads are available for 12/7: http://mirror.math.princeton.edu/pub/alt//atomic/stable/ `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/184

3 14

[atomic-wg] Issue #192 `atomic working group - periodic virtual FADs`
by Pagure 14 Jul '17

14 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` It would be great if we can have some planned virtual meetings every few months to discuss the atomic working group and current issues that extend into discussions. Should we meet every so often (not necessarily for an entire day) to sync up on issues and work through the backlog of items to clear out cruft and/or promote forgotten priorities? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/192

2 2

[atomic-wg] Issue #166: RFE : vagrant user with id=1000
by Dusty Mabe 14 Jul '17

14 Jul '17

The status of the issue: `RFE : vagrant user with id=1000` of project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe. https://pagure.io/atomic-wg/issue/166

1 0

[atomic-wg] Issue #166: RFE : vagrant user with id=1000
by Dusty Mabe 14 Jul '17

14 Jul '17

dustymabe added a new comment to an issue you are following: `` This is done now and in the fedora 26 artifacts that were just delivered. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/166

1 0

[atomic-wg] Issue #262: F26 Talking Points
by Dusty Mabe 14 Jul '17

14 Jul '17

The status of the issue: `F26 Talking Points` of project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe. https://pagure.io/atomic-wg/issue/262

1 0

[atomic-wg] Issue #262: F26 Talking Points
by Dusty Mabe 14 Jul '17

14 Jul '17

dustymabe added a new comment to an issue you are following: `` f26 is out - and I think this can be closed `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/262

1 0

[atomic-wg] Issue #282: Atomic Host images omit many common locales that all other flavors include
by Adam Williamson 14 Jul '17

14 Jul '17

adamwill reported a new issue against the project: `atomic-wg` that you are following: `` Apparently, it was decided that Fedora Atomic Host images should include only the locales 'officially supported' by RHEL 7 - see https://bugzilla.redhat.com/show_bug.cgi?id=1430182 , jlebon says it was decided to apply the same choice to Fedora as to RHEL. This is entirely out of step with all other Fedora flavors, though, I believe. These include far, far more locales. The 'RHEL supported' list doesn't include such obvious and widely-used locales as en_CA and en_AU. I'm not sure it makes sense to just decide the RHEL 'supported locales' list is an appropriate basis for the list of locales to include in Fedora images. [Transferred from https://bugzilla.redhat.com/show_bug.cgi?id=1459341 as requested there]. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/282

7 13

[atomic-wg] Issue #291: create static delta for f25 to f26 upgrade
by Dusty Mabe 14 Jul '17

14 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` We want to have our users have the ability to use static deltas when moving from f25 to f26. We haven't yet moved to a unified repo but can give the users static deltas by simply pulling in the last f25 commit and then generating a static delta as described [here](https://pagure.io/releng/issue/6871#comment-446988). `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/291

1 3

[atomic-wg] Issue #301: kickstarts broken in rawhide - improperly looking for local repo
by Dusty Mabe 14 Jul '17

14 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` Example failed koji task: https://koji.fedoraproject.org/koji/taskinfo?taskID=20474689 We recently started having ostree re-use the local mirror of content from the ISO image if it existed. We have it look in `/ostree/repo` and `/run/install/repo` in [this line of code](https://github.com/rhinstaller/anaconda/pull/1119/files#diff-3e2b7e1a…. At least for fedora 25 (according to the [lorax template](https://pagure.io/fedora-lorax-templates/blob/f25/f/atomic-installer/lorax-configure-repo.tmpl#_8) the real location was `/run/install/repo/content/repo`. However `/run/install/repo/` is an actual directory on our media and has several things in there that anaconda uses. So `/run/install/repo` exists and is not an ostree repo. This means that any ostree anaconda install that is initiated from a non-ostree install tree (like our atomic host qcows are in our pungi composes) will fail with this error: ``` The following error occurred while installing. This is a fatal error and installation will be aborted. Failed to pull from repository: g-io-error-quark: Opening objects/ directory: openat: No such file or directory (1) ``` I'm thinking we should 1. fix the installer to look for the right location (PR [here](https://github.com/rhinstaller/anaconda/pull/1126)) 2. possibly make ostree not fail if a provided reference repo is bogus. Thoughts? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/301

2 3

[atomic-wg] Issue #287: Identify group of people interested in maintaining kubernetes
by Dusty Mabe 14 Jul '17

14 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` We're trying to balance the pros/cons of trying to have both kubernetes and origin in Fedora. We're trying to find a group of people interested in helping us maintain kubernetes within Fedora. This includes maintaining the rpm, fielding bug reports, making sure docs stay up to date, and trying to make sure upgrades work. From our preliminary discussion i know a few people: - @strigazi - @dimtheo - @jasonbrooks - @jberkus Can we get other people who are interested in helping out add their name to this issue? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/287

8 18

[fedora-atomic] PR #63: Rename treefile to match ref
by Colin Walters 13 Jul '17

13 Jul '17

walters opened a new pull-request against the project: `fedora-atomic` that you are following: `` Rename treefile to match ref `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/63

4 5

Fedora Atomic WG Meeting Minutes 2017-07-12
by Dusty Mabe 13 Jul '17

13 Jul '17

summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-07-12/fedora_atomic… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-07-12/fedora_atomic… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by dustymabe at 17:00:07 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2017-07-12/fedora_atomic… . Meeting summary --------------- * roll call (dustymabe, 17:00:13) * previous meeting action items (dustymabe, 17:04:08) * dustymabe proposed a VFAD https://pagure.io/atomic-wg/issue/294 (dustymabe, 17:05:48) * dustymabe added update to kubernetes thread: https://pagure.io/atomic-wg/issue/287#comment-447645 (dustymabe, 17:06:22) * dusty opened a ticket regarding mailing list/irc channel for atomic/cloud working group: https://pagure.io/atomic-wg/issue/295 (dustymabe, 17:07:00) * fedora-minimal container image is in the fedora registry now https://pagure.io/atomic-wg/issue/290 (dustymabe, 17:09:14) * ACTION: maxamillion roshi to come up with guidelines for meeting quorum for the atomic working group (dustymabe, 17:11:18) * Start using new mailing list/IRC channel around f26 release time (dustymabe, 17:11:44) * LINK: https://pagure.io/atomic-wg/issue/295 (dustymabe, 17:11:52) * LINK: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-Jun… (jbrooks, 17:29:35) * lots of good discussion here - no real concensus (spelling?) - continue discussion in ticket https://pagure.io/atomic-wg/issue/295 (dustymabe, 17:37:19) * Atomic Host images omit many common locales that all other flavors include (dustymabe, 17:37:28) * LINK: https://pagure.io/atomic-wg/issue/282 (dustymabe, 17:37:34) * jlebon worked on some items around this ticket which should address adam's most pressing concerns (dustymabe, 17:38:41) * Delivering Atomic Host via CI/CD pipeline (dustymabe, 17:39:07) * LINK: https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org… (dustymabe, 17:39:12) * LINK: https://fedoraproject.org/wiki/Objectives/Continuous_Integration_and_Delive… (dustymabe, 17:39:18) * LINK: https://upstreamfirst.fedorainfracloud.org/ (stefw, 17:44:56) * LINK: https://fedoraproject.org/wiki/CI (stefw, 17:46:43) * some people have been looking at fedora build process/tooling for fedora atomic and have some initial work links from https://fedoraproject.org/wiki/CI (dustymabe, 17:47:45) * there is a mailing list for the ci efforts in Fedora, that will initially focus on the set of packages in atomic host: ci(a)lists.fedoraproject.org (dustymabe, 17:50:55) * open floor (dustymabe, 18:01:52) * Fedora 26 Atomic host first release was yesterday please read the announcement from projectatomic blog: http://www.projectatomic.io/blog/2017/07/fedora-atomic-26-release/ (dustymabe, 18:02:48) Meeting ended at 18:03:36 UTC. Action Items ------------ * maxamillion roshi to come up with guidelines for meeting quorum for the atomic working group Action Items, by person ----------------------- * maxamillion * maxamillion roshi to come up with guidelines for meeting quorum for the atomic working group * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dustymabe (168) * stefw (92) * maxamillion (24) * jberkus (23) * zodbot (23) * jbrooks (23) * gholms (21) * jdoss (9) * jzb (9) * sayan (9) * walters (9) * ksinny (6) * miabbott (5) * strigazi (2) * tibbs (2) * scollier (2) * yzhang (2) * rubao (1) * bowlofeggs (1) * pingou (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[atomic-wg] Issue #300: bodhi creating ostrees using pungi
by Dusty Mabe 13 Jul '17

13 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` mostly a tracker ticket for getting bodhi to create ostrees by using pungi. This helps us by: - only one way that Fedora Infra creates ostrees (through pungi) - allows us to get ostree versions of the form `26.20170701.0` - delete fedmsg-atomic-composer code - handle multiarch for Atomic Host related bodhi ticket: https://github.com/fedora-infra/bodhi/issues/1182 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/300

1 1

[atomic-wg] Issue #197 `Change size of Root, Docker partitions in F26 Atomic Host storage setup`
by Pagure 13 Jul '17

13 Jul '17

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` The way it is now: Currently, the rootFS is sized at 3GB, fixed, and the Docker partition is 40% of the remaining space. This causes new users to run out of disk space if they do layering, ostree unlock, install a bunch of system containers, or even just run up the logs, even if they have plenty of physical disk space. My suggestion for a new default is: * RootFS: 25% of disk space, with a minimum of 3GB and a maximum of 16GB * Docker Partition: 50% of total disk space (or 65% of remaining space), min 2GB * Unallocated: 25% of disk space. This would mean, for a new install: Disk Root Docker Unallocated 8GB 3GB 4GB 1GB 32GB 8GB 16GB 8GB 200GB 16GB 100GB 84GB `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/197

4 17

Please comment on upcoming Atomic Docs VFAD
by Dusty Mabe 13 Jul '17

13 Jul '17

The Fedora Atomic Working group has a proposed "Virtual" Fedora Activity Day planned for the last week of July. Please consider joining us and or brainstorming on details of the session in the ticket: https://pagure.io/atomic-wg/issue/294 Dusty

1 0

[atomic-wg] Issue #294: VFAD: Docs Treasure Hunt
by Dusty Mabe 13 Jul '17

13 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` Target Date: Last week of July Let's have a VFAD to help us find all of our docs that exist in the wiki and create an index of all of them. I suggest we actually have the index as our README for atomic-wg in pagure as well as our landing page on the wiki, but this may prove problematic. Really it would be great if we could have wiki support markdown formatting so we can just replicate the content between both places. I suggest that we have a short 30minute video session and then a period of IRC collaboration as people go off to find docs (food break can be in here somewhere for breakfast/lunch/dinner depending on where you are). Then we can close with another 30 minutes video session to recap and possibly identify missing documentation and create tickets to get those docs created. This will help us lead up to the Docs workshop at FLOCK. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/294

1 1

[atomic-wg] Issue #286: tracker: AMIs in non us-east-1 regions aren't accessible
by Dusty Mabe 13 Jul '17

13 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` Tracker for https://pagure.io/fedora-infrastructure/issue/6123 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/286

2 5

[fedora-atomic] PR #66: manifest: Drop updates-testing by default
by Colin Walters 12 Jul '17

12 Jul '17

walters opened a new pull-request against the project: `fedora-atomic` that you are following: `` manifest: Drop updates-testing by default `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/66

2 2

[fedora-atomic] PR #65: Rename treefile to match ref
by Dusty Mabe 12 Jul '17

12 Jul '17

dustymabe opened a new pull-request against the project: `fedora-atomic` that you are following: `` Rename treefile to match ref `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/65

2 4

[atomic-wg] Issue #290: Make fedora-minimal base image generally available
by Josh Berkus 12 Jul '17

12 Jul '17

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` A "minimal" build of the base container image exists, but isn't official or generally available from the repository. We need this minimal image for a few reasons: * users care about container size from some use-cases (think super-micro-services and serverless) * arguably a more minimal container is easier to secure * other linux distros offer some kind of small base image * buildah, now in alpha, *really* benefits from a minimal base image For this to succeed, we'd want the following base images as part of registry.fedoraproject.org: * fedora-minimal:25 * fedora-minimal:26 * fedora-minima:latest Given that the minimal image will differ less per release version (since it has less plubming), it would be perfectly acceptable to have a very short expiration window on older release versions, or only supporting the current Fedora release. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/290

7 22

[atomic-wg] Issue #296: Cannot install to bare metal using kickstart due to ref name problems in f26 release
by Josh Berkus 12 Jul '17

12 Jul '17

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` I pave my bare metal cluster using a kickstart similar to the one here: http://www.projectatomic.io/blog/2016/10/install-with-kickstart/ However, as of f26 release, this no longer works. Which is surprising given that f26 alpha did work. The problem is this line in my updated kickstart: ostreesetup --osname="fedora-atomic" --remote="fedora-atomic" --url="file:////run/install/repo/content/repo" --ref="fedora/26/x86_64/atomic-host" --nogpg This should pull the ref from the local media (USB key). However, what I get now is "openat: no such file or directory" So somehow the ref is broken in the ISO. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/296

3 7

[atomic-wg] Issue #279: talk/workshop proposals for Flock
by Dusty Mabe 11 Jul '17

11 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` Let's collect ideas for talk/workshop proposals at [Flock](https://flocktofedora.org/) Due date for CFP submissions is June 15th `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/279

5 14

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

11 Jul '17

A new Fedora Atomic Host update is available via an OSTree commit: Commit: 2e4fcaff52c18cf705a2ecfa47d2ca60958f7443177974f24cc9ce07494b3317 Version: 26.85 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-26-201707… https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-26-201707… 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

3 2

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by dusty＠dustymabe.com 10 Jul '17

10 Jul '17

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2017-07-12 from 17:00:00 to 18:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Standing meeting for the Fedora Cloud Workgroup Source: https://apps.fedoraproject.org/calendar/meeting/1999/

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud July 2017