cloud January 2017

cloud@lists.fedoraproject.org

27 participants
73 discussions

May miss today's meeting
by Trishna Guha 18 Jan '17

18 Jan '17

Hello, I have got a bad fever from today evening. I may not be available in today's Atomic-wg meeting if I am not well. If I miss the meeting I'll make sure to go through the meeting logs tomorrow and will work on if I find a task for myself :). I was thinking to host today's meeting. But I'm not sure that I can do it now. If I feel better I'll be there to attend. Thanks, Trishna

1 0

Re: [atomic-devel] Fedora 2wk Atomic Blocker Bugs
by Dusty Mabe 17 Jan '17

17 Jan '17

On 01/17/2017 02:26 PM, Eric Paris wrote: > On Tue, 2017-01-17 at 13:42 -0500, Dusty Mabe wrote: >> There are a few bugs that are blocking 2wk release. >> >> - one with the kernel that causes kube dns to not work >> * https://bugzilla.redhat.com/show_bug.cgi?id=1414068 >> - one with kube that causes selinux breakage >> * https://bugzilla.redhat.com/show_bug.cgi?id=1414096 > > The selinux issue is fixed in 1.5. 1.4 will not be updated. Yep, that was understood. We just needed a reference to point to when talking to people about the issue so I created a BZ. > The kernel regression I'm still poking at... > jbrooks tested the rawhide kernel kernel-4.10.0-0.rc4.git0.1.fc26 and it all works for him. we are investigating further. There is a 4.9.4 kernel he is testing next to see if it is fixed there. Also, Laura Abbott pointed us to this as a possible culprit: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=… Dusty

1 0

Fedora Atomic WG Workflow Proposal
by Adam Miller 17 Jan '17

17 Jan '17

Hello all, Recently I attempted to start a mailing list thread that was the product of a discussion on IRC about putting together an Atomic WG workshop session[0] at DevConf[1]. This was then discussed during today's Atomic WG Meeting[2] where it was decided that we should make this Workshop into a re-occurring Virtual Fedora Activity Day(FAD[3]) instead taking place every 2 months. I would like to propose the following: Each Virtual FAD occurs on a Thursday, the day after a Fedora Atomic WG meeting such that we can use the meeting the day before to plan out the work to be done at the Virtual FAD. All work will be tracked in a kanban[4] board, I've created one for this purpose in Fedora's Taiga instance[5] (Note: I don't know why my FAS name is in the URL, Taiga just does that). In the kanban board, we would create cards in the NEW column through out the two month cycle between Virtual FADs (these should correlate to tickets in pagure[6]), then on the meeting before the FAD we would "groom" the NEW cards that we want to accomplish on the following day of the Virtual FAD, these "groomed" cards would be placed into the READY column to signify they are ready to be worked on. On the day of the VFAD, participants/contributors would then assign a card to themselves that they want to work on, and move the card into "IN PROGRESS" so that everyone knows what is being worked on and nobody attempts to work on the same thing (unless that's intentional, in that case both people's names should be listed in the card description for reference). Once a task is done, then it should be moved to the DONE column. This will give a good reflection of what work was accomplished during the VFAD and we can (optionally) have a retrospective meeting after the VFAD about what went well, what didn't go well, and what we could do better next time. Also the day before the next VFAD at the start of the "grooming" session (the weekly Atomic WG meeting), all the previous VFAD's cards in the DONE column from the previous VFAD should be moved to ARCHIVED for posterity. Cards created should be units of work that can feasibly be accomplished in a day or less worth of work. I would like to ultimately propose we move to a more iterative cycle where we use this workflow weekly instead of dedicating a single day every 2 months (these periods of time are often known as a "sprint" in Agile[7]) but my hope is that this is a good place to start and we can improve over time. If this is acceptable as a change we would like to adopt as a group, I am happy to pre-populate the kanban board with work items we had previously discussed that we wanted to accomplish as the original agenda to the (now defunct) DevConf Workshop. From there I would propose that the first meeting after DevConf (2017-02-01) be used as the first grooming session and the following Thursday be the first VFAD (2017-02-02). From there we would set a schedule for every 2 months to have a VFAD. If everyone is in agreement, I'll also get a section of the Wiki page (which we need to move out of the Cloud namespace) added to document this workflow for newcomers who would like to join the Atomic WG. Thank you, -AdamM [0] - https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org… [1] - https://devconf.cz/index.html [2] - https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org… [3] - https://fedoraproject.org/wiki/Fedora_Activity_Day_-_FAD [4] - https://en.wikipedia.org/wiki/Kanban [5] - https://taiga.fedorainfracloud.org/project/maxamillion-fedora-atomic-wg/kan… [6] - https://pagure.io/atomic-wg/issues [7] - https://en.wikipedia.org/wiki/Agile_software_development

4 8

Fedora Cloud Images Home page - oVirt
by Sandro Bonazzola 17 Jan '17

17 Jan '17

Hi, I'm looking at https://alt.fedoraproject.org/cloud/ and I'd like to ask to mention oVirt[1] project as well since oVirt can use Fedora 25 Cloud Base Images as well. If this mailing list is not the right place to ask, can you please point me to the correct place? [1] https://www.ovirt.org/ Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 2

Re: docker-latest in Fedora
by Antonio Murdaca 16 Jan '17

16 Jan '17

On Jan 15, 2017 10:07 PM, "Dusty Mabe" <dusty(a)dustymabe.com> wrote: On 01/13/2017 11:18 AM, Antonio Murdaca wrote: > > > > That sounds good. However, I didn't fully understand how to achieve that. Do you mean that docker-latest shouldn't build docker-latest anymore but just require "docker" and make a symlink out of it? Exactly. in other words, it's just a placeholder for now. With the power of git it won't be too hard to revive the spec file to start building it again if we decide we need to. Not sure that's gonna work well. The thing that's not really the point maybe. The issue is there's really a lack of users for docker-latest and I'm questioning its existence :). Take F24 for instance, docker is at 1.10.3 while docker-latest is at 1.12.6. However, nobody really test/use it resulting in me spending time updating it where it sounds like nobody cares about it. Your approach works for F25, both docker and docker-latest are at 1.12.x. Maybe we should just wait for system containers and keep building it (on me). If you need any help with this let me know. Dusty

2 1

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 16 Jan '17

16 Jan '17

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2017-01-18 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

[atomic-wg] Issue #195 `atomic host: add sanity checks for rpm content changes `
by Pagure 15 Jan '17

15 Jan '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` We should be sanity checking the content that goes into each new ostree update of F25 atomic host. Here are some ideas: - raise flag if any rpm go down in version/release - raise flag if any rpm gets pulled from fedora (release day) repo vs updates repo iff one exists in the updates repo - raise flag when packages get added/removed This will help us have better oversight over changes and not miss important changes that weren't intended. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/195

1 0

docker-latest in Fedora
by Antonio Murdaca 15 Jan '17

15 Jan '17

Hi, Seems like no people are really using docker-latest in Fedora. I realized that because the version in F25 is old and nobody adds karma to the updates in bodhi there. Is there any real user of docker-latest in Fedora? Just asking because it's a maintenance cost to always rebuild that as well (even if I automated it a bit). To my knowledge, openshift guys aren't really using it either. Should we spread the voice about it? What do you think?

3 4

old docker in the ostree that was built last night
by Dusty Mabe 13 Jan '17

13 Jan '17

Refrain from running `rpm-ostree upgrade` for now on Fedora Atomic Hosts. The version of docker that made it into Fedora updates repo yesterday has a dependency that is still in updates-testing and thus that version won't install due to dependency errors. The ostree composer fell back to an older version of docker that it could find all the deps for. This means the docker that got installed was old. The needed dep will make it into the next ostree update. Dusty

1 0

[atomic-wg] Issue #194 `Develop process to make sure we add new AWS regions when they become available`
by Pagure 12 Jan '17

12 Jan '17

mattdm reported a new issue against the project: `atomic-wg` that you are following: `` The current process is "wait until someone complains". I think we can do better. :) They're announced at https://aws.amazon.com/new/#global-infra — maybe we come up with automation, or maybe it's just a matter of adding "review this list" as a six-month checklist item as we prepare for the overall Fedora GA, plus responding like we currently do if someone asks in the meantime. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/194

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud January 2017