cloud June 2017

cloud@lists.fedoraproject.org

19 participants
83 discussions

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

[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

[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

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

[atomic-wg] Issue #284: Fedora OSBS RFE: install go-md2man to buildroot image
by Tomas Tomecek 10 Jul '17

10 Jul '17

ttomecek reported a new issue against the project: `atomic-wg` that you are following: `` ...so OSBS can automatically convert markdown-written help files [1] [2] to roff and add them inside built container image. Help files are part of Fedora Container Guidelines [3]. [1] add_help plugin at https://github.com/projectatomic/atomic-reactor/blob/master/docs/plugins.md [2] a bit more documentation is present in plugin docstring: https://github.com/projectatomic/atomic-reactor/blob/master/atomic_reactor/… [3] https://fedoraproject.org/wiki/Container:Guidelines#Help_File `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/284

2 2

[atomic-wg] Issue #261 `Issue Tracker for F26 release blockers`
by Dusty Mabe 10 Jul '17

10 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` This ticket will be used throughout the f26 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** - **Important Bugs** - none Over time only the description of this bug will be edited for updates. Please do not add comments to this issue. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/261

3 7

[atomic-wg] Issue #269: fedimg: don't use 'builder' instance for uploading AMIs
by Dusty Mabe 05 Jul '17

05 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` we hit [an issue](https://pagure.io/releng/issue/6761) yesterday because fedimg failed upload all of our AMIs for that day's build of FAH. This is most likely due to the fact that we use a builder instance to pull the cloud disk image and then create the EBS. Bringing up the builder instance can fail (commodity hardware in EC2) and thus can lead to situations like this. It would be much better if we don't use a builder instance. This is being worked on in https://github.com/fedora-infra/fedimg/issues/42. This ticket will track that work that is 'two weeks away' from completion. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/269

2 3

← Newer
1
2
3
4
5
6
7
8
9
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud June 2017