cloud October 2015

cloud@lists.fedoraproject.org

24 participants
89 discussions

Why I'm excited about Atomic for Fedora
by Matthew Miller 09 Nov '15

09 Nov '15

I've spent the last 3+ years asking people what they would like from a guest operating system in the cloud. Sometimes framed as "Why did you choose Fedora?", sometimes as "Why didn't you choose Fedora?", and sometimes basically the generic question. I'd say that overall, the reason people say that they chose what they did was either familiarity, or that they found documentation — or another person — doing a similar thing, and they just followed whatever OS that had. When I ask what they *want*, though, there's a somewhat different story. It's pretty universal, though: a small, simple base without much risk, and a library of components to go on top of that. Fedora Cloud Base is a decent job of being a small base, although we still have a lot of dependency bloat and updates churn. But the library of stuff — languages, services — is difficult. We've got a great set of packages, but they're largely irrelevant, because the versions are usually changing too quickly. Mostly, you've got to bring your own stacks. I'd hoped that we could answer this by slimming down the base and then offering a wide selection of SCLs on top. But, I don't think that's really panning out. The base is way less minimal than I'd like, and I don't know a good way to manage the updates situation. And SCLs are both still somewhat stuck *and* unlikely to explode (in the good sense) if they get unstuck. For people who chose Fedora Cloud already — familiarity, or they found someone else familiar — we're probably okay. No one has anything negative to say about the work we've done — in fact, people who have chosen it generally say good things. I think it's very useful to keep producing Fedora Cloud Base for that group. But... it's a small club. So, enter Atomic Host plus containers. This is, basically, exactly what people have been asking for. The ostree tech brings some order to the base, making updates more reliable and testable. And containers bring us the library of components — at the very least making it easier to bring your own, and ideally providing a new, better way for us to offer different versions, possibly with a different lifecycle. That's why I'd like to move the Cloud Base image to a dedicated cloud.fedoraproject.org page along the lines of http://arm.fedoraproject.org, and replace Cloud with Atomic Host as a top level on <https://arm.fedoraproject.org/>, and to rename Cloud WG to Atomic WG (but still keeping the Cloud SIG to work on the Base image). This is all just my 2¢, but I hope you'll consider them 2¢ with a lot of prior listening. If you have a counter story which will help us significantly grow adoption of Cloud Base *instead*, I'd love to hear it. -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

7 10

[cloud] #128: Extra ifcfg file in the cloud base image
by Fedora Cloud Trac Tickets 03 Nov '15

03 Nov '15

#128: Extra ifcfg file in the cloud base image --------------------+-------------------- Reporter: kushal | Owner: kushal Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: --------------------+-------------------- We now have an extra ifcfg-ens3 file in cloud base image, that is resulting the failure of the network service in the image. For more details please read https://lists.fedoraproject.org/pipermail/cloud/2015-October/005939.html -- Ticket URL: <https://fedorahosted.org/cloud/ticket/128> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

RC* Atomic images are broken
by Dusty Mabe 02 Nov '15

02 Nov '15

We found out today that all RC images for Atomic are broken. They are building against a much older yum repo (the beta repos) and thus have a very old systemd, which has some breakages with ostree. dgilmore and maxamillion have done some investigation and believe they have somewhat pinpointed the issue, although I don't know if they know of an exact fix yet. This would have been caught by tunir/autocloud but tunir skips this test for atomic images. I have submitted a PR for it to not do that [1]. Right now the last booting atomic image is TC11. If we don't do another compose then we won't have an atomic image for release. Dusty [1] - https://github.com/kushaldas/tunirtests/pull/6

5 6

[cloud] #119: [VOTE] New members approval
by Fedora Cloud Trac Tickets 02 Nov '15

02 Nov '15

#119: [VOTE] New members approval ----------------------+-------------------- Reporter: hguemar | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: Planning | Keywords: ----------------------+-------------------- Discussed in the mailing list: https://lists.fedoraproject.org/pipermail/cloud/2015-August/005653.html We've got two empty seats and two candidates: * Ratnadeep Debnath https://lists.fedoraproject.org/pipermail/cloud/2015-August/005655.html * Aditya Patawari https://lists.fedoraproject.org/pipermail/cloud/2015-August/005656.html Active members are requested to approve or not the candidates before formally making them Cloud WG members. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/119> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 6

RC6 vagrant images are indexed in atlas - please test
by Dusty Mabe 31 Oct '15

31 Oct '15

Hi all, We will be indexing our vagrant images in Atlas for the F23 release. We'd like to invite people to try it out with the RC6 vagrant images that I just recently indexed in atlas. Right now these images are in my own repository, but on release they will be under the fedora name so just imagine s/dustymabe/fedora/ in the instructions below: For cloud base: vagrant init dustymabe/23-cloud-base; vagrant up --provider libvirt or vagrant init dustymabe/23-cloud-base; vagrant up --provider virtualbox For atomic host: vagrant init dustymabe/23-atomic-host; vagrant up --provider libvirt or vagrant init dustymabe/23-atomic-host; vagrant up --provider virtualbox Let me know what you think, Dusty

1 1

Can't run a container with root bind mounted in F23 docker 1.7
by Dusty Mabe 30 Oct '15

30 Oct '15

docker 1.7 is what is in the stable f23 repo. with that we can't run a container with root bind mounted into it: ``` -bash-4.3# docker run -it --rm -v /:/host busybox Error response from daemon: Relabeling of / is not allowed -bash-4.3# rpm -q docker docker-1.7.0-22.gitdcff4e1.fc23.x86_64 ``` I guess we'll just have to go with it.. Dusty

4 6

atomic/cloud package maintaners and experts: please help create test plans!
by Matthew Miller 30 Oct '15

30 Oct '15

I was talking to Colin recently, and one thing he mentioned was difficulty in getting karma for getting updates through bodhi. This is something where our community can really help, but it's sometimes hard to know exactly how to test. See for example the anonymous comment on the docker update for F23: https://bodhi.fedoraproject.org/updates/docker-io-1.7.1-4.el6#comment-345195 Fedora QA actually has a standard procedure for creating test cases and test plans for manual validation (in addition of course to whatever automated tests we can run). The procedure for doing this is at: https://fedoraproject.org/wiki/QA:SOP_package_test_plan_creation and once test cases are created and properly categorized, they actually will show up right in Bodhi. Thanks! -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

1 0

Cloud Meeting Minutes 2015-10-28
by Dusty Mabe 29 Oct '15

29 Oct '15

html version: http://meetbot.fedoraproject.org/fedora-meeting-1/2015-10-28/cloud_wg.2015-… full log: http://meetbot.fedoraproject.org/fedora-meeting-1/2015-10-28/cloud_wg.2015-… =========================== #fedora-meeting-1: Cloud WG =========================== Meeting started by roshi at 17:02:39 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2015-10-28/cloud_wg.2015-… . Meeting summary --------------- * Roll Call (roshi, 17:02:53) * Previous Meeting Followup (roshi, 17:05:10) * ACTION: dustymabe to integrate cloud WG and 2 week atomic efforts (roshi, 17:11:02) * python3 only breaks ansible (roshi, 17:11:38) * LINK: https://fedorahosted.org/cloud/ticket/126 (roshi, 17:11:46) * ACTION: jzb to write up a magazine article on bootstrapping if the pitch is accepted for the magazine (roshi, 17:26:39) * ACTION: roshi to put in for the magazine pitch (roshi, 17:26:50) * Updated Cloud/Atomic images (roshi, 17:27:12) * LINK: https://fedorahosted.org/cloud/ticket/94 (roshi, 17:27:18) * ACTION: dustymabe to close ticket 94 and open a couple more specific tickets (roshi, 17:33:00) * Working with the Server WG (roshi, 17:34:39) * LINK: https://fedorahosted.org/cloud/ticket/127 (roshi, 17:34:48) * ACTION: after F23 GA, jzb to schedule a meeting between the groups for a strategy discussion (roshi, 17:54:58) * ACTION: jzb to start discuss thread on cloud/atomic/server wg stuff (jzb, 17:54:59) * Open Floor (roshi, 17:55:30) * LINK: https://atlas.hashicorp.com/dustymabe/boxes/fedora/versions/23.RC3 (dustymabe, 18:00:03) Meeting ended at 18:02:48 UTC. Action Items ------------ * dustymabe to integrate cloud WG and 2 week atomic efforts * jzb to write up a magazine article on bootstrapping if the pitch is accepted for the magazine * roshi to put in for the magazine pitch * dustymabe to close ticket 94 and open a couple more specific tickets * after F23 GA, jzb to schedule a meeting between the groups for a strategy discussion * jzb to start discuss thread on cloud/atomic/server wg stuff Action Items, by person ----------------------- * dustymabe * dustymabe to integrate cloud WG and 2 week atomic efforts * dustymabe to close ticket 94 and open a couple more specific tickets * jzb * jzb to write up a magazine article on bootstrapping if the pitch is accepted for the magazine * after F23 GA, jzb to schedule a meeting between the groups for a strategy discussion * jzb to start discuss thread on cloud/atomic/server wg stuff * roshi * roshi to put in for the magazine pitch * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dustymabe (103) * roshi (85) * jzb (75) * kushal (52) * jbrooks (30) * maxamillion (28) * zodbot (15) * adimania (11) * linuxmodder (8) * nzwulfin_ (7) * lalatenduM (5) * sayan (2) * smdeep (1) * rtnpro (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Fedora 23 Final RC6 call for testing
by Adam Williamson 29 Oct '15

29 Oct '15

Hi folks! We have what should hopefully be the final RC for Fedora 23 available for testing now. It would be really great if folks could help us run as many of the validation tests as possible ahead of the Go/No- Go meeting tomorrow. Here are the result pages: https://fedoraproject.org/wiki/Test_Results:Fedora_23_Final_RC6_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_23_Final_RC6_Base https://fedoraproject.org/wiki/Test_Results:Fedora_23_Final_RC6_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_23_Final_RC6_Server https://fedoraproject.org/wiki/Test_Results:Fedora_23_Final_RC6_Cloud we need to run all the tests marked as Alpha, Beta and Final, ideally for all the 'environments' (columns). Image download links are at the top of the page, and you can file results by editing the pages manually or using the 'relval' tool - you need to get that from a side repo, see https://www.happyassassin.net/wikitcms/ for info on installing it, then just run 'relval report-results'. If you find something that looks like a release blocker bug, please submit a bug report, file a 'fail' result referencing the bug report, and mark the bug as blocking 'FinalBlocker' (or use https://qa.fedoraproject.org/blockerbugs/propose_bug ) to propose it as a blocker. Thanks a lot folks! If you have any questions, please ask in #fedora-qa on Freenode. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Functional Requirements for Layered Image Build Service
by Matthew Miller 29 Oct '15

29 Oct '15

Hey everyone. Adam is updating the Layered Image Build service Change page for F24. If you're interested in _using_ this service, we'd appreciate feedback on functional requirements — what do you need in order to get the output you want? See https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service#F… thanks! -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

3 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 October 2015