October 2015 - cloud - Fedora mailing-lists

[cloud] #131: make docker archived image get imported with lowercase tag
by Fedora Cloud Trac Tickets 20 Apr '16

20 Apr '16

#131: make docker archived image get imported with lowercase tag -----------------------+--------------------- Reporter: dustymabe | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting -----------------------+--------------------- Our docker image has a repositories file with this in it: ``` {"Fedora-Docker-Base-23_TC1-20150929.x86_64": {"latest": "27653b989fba2fada76e804f4112b87d7b013758e99bbb88a26c070dbcae5962"}} ``` This means that the docker image gets tagged with Fedora-Docker-Base- 23_TC1-20150929.x86_64 when it gets loaded in. Unfortunately if you try to build on top of this image by having a Dockerfile with `FROM Fedora- Docker-Base-23_TC1-20150929.x86_64` then you will get an error because only lowercase letters are allowed in tags of images in a registery: "[a-z0-9]+(?:[._-][a-z0-9]+)*" We should update this so that users can have a better experience. [1] - //dl.fedoraproject.org/pub/alt/stage/23_TC1/Docker/x86_64/Fedora- Docker-Base-23_TC1-20150929.x86_64.tar.xz -- Ticket URL: <https://fedorahosted.org/cloud/ticket/131> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 8

[cloud] #123: Document process for using Fedora-Dockerfile branches
by Fedora Cloud Trac Tickets 24 Mar '16

24 Mar '16

#123: Document process for using Fedora-Dockerfile branches ----------------------+-------------------- Reporter: scollier | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: ----------------------+-------------------- This should probably go on the github repo home page. Need to provide instructions for users to submit to a specific branch, and not just to master. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/123> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 10

[cloud] #88: Social Media for Dockerfiles
by Fedora Cloud Trac Tickets 24 Feb '16

24 Feb '16

#88: Social Media for Dockerfiles -----------------------------------+--------------------- Reporter: jzb | Owner: jzb Type: task | Status: new Priority: normal | Milestone: Future Component: Docker Base Container | Keywords: meeting -----------------------------------+--------------------- We need to work with marketing to tweet about things regularly. I'd like to put out regular tweets to promote individual Dockerfiles. Thoughts? -- Ticket URL: <https://fedorahosted.org/cloud/ticket/88> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 7

[cloud] #99: AMI lifetimes (Cloud WG members vote needed)
by Fedora Cloud Trac Tickets 24 Feb '16

24 Feb '16

#99: AMI lifetimes (Cloud WG members vote needed) -------------------------------------+------------------------------------- Reporter: oddshocks | Owner: oddshocks Type: task | Status: new Priority: normal | Milestone: Fedora 22 Component: Infrastructure & | Keywords: aws, images, vote, Release Engineering | policy -------------------------------------+------------------------------------- This ticket is to discuss and vote on appropriate lifetimes for Fedora Cloud AMIs on our official and community cloud accounts, as discussed on the Cloud SIG list this month[1] and in this week's meeting. Everyone seems to agree that after a final release, all TC, RC, Alpha, Beta, and scratch builds should be deleted. This makes sense because there'd be no reason to use any of these AMIs after the final release. Still, we need to definitively decide on: 1. When should TC, RC, Alpha, Beta, and scratch builds be deleted? (1) After a final release? (2) Progressively, when a newer build of the same type comes out? (3) After a set amount of time, depending on the build type? Note that with (2) or (3), we'd need some way to mark each build with it's type. I don't think that necessarily happens now. 2. When should final release AMIs be deleted? (1) After a certain number of newer final releases? (2) After a certain amount of time? (3) Never? Also note that if we choose any age-based deletion policies, we'd need to set up some sort of regular polling of *all* our AMIs on both accounts. We want to hold as few AMIs at one time as is reasonable. There are many AMIs created for each image build that happens, so our AWS storage charges will become quite high if we don't keep our accounts clean. Discuss, and then perhaps a vote? [1]: https://lists.fedoraproject.org/pipermail/cloud/2015-March/005087.html -- Ticket URL: <https://fedorahosted.org/cloud/ticket/99> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 18

[cloud] #121: Migrate all Dockerfiles / Images to systemd where possible
by Fedora Cloud Trac Tickets 11 Jan '16

11 Jan '16

#121: Migrate all Dockerfiles / Images to systemd where possible ----------------------+-------------------- Reporter: scollier | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: ----------------------+-------------------- There are some images that still use supervisord. We need to migrate those to systemd. One example: https://github.com/fedora-cloud/Fedora- Dockerfiles/tree/master/lighttpd -- Ticket URL: <https://fedorahosted.org/cloud/ticket/121> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 16

[cloud] #122: Clean up READMEs.
by Fedora Cloud Trac Tickets 06 Jan '16

06 Jan '16

#122: Clean up READMEs. ----------------------+-------------------- Reporter: scollier | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: ----------------------+-------------------- The readmes need to be cleaned up a bit and standardized. Some have "Tested on Docker 1.4.0" We need to update those. Needs standard sections: Build Run Test -- Ticket URL: <https://fedorahosted.org/cloud/ticket/122> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 5

[DISCUSS] Cloud and Server Workgroup relationship
by Joe Brockmeier 20 Nov '15

20 Nov '15

Hi all, During today's Cloud Working Group meeting we had a short but spirited discussion on the roles of the Cloud and Server Working Group and the editions we're producing. I wanted to open a discussion on that topic (see also [1]) ahead of planning for F24 to see if the current setup makes sense, how we can collaborate, and so forth. I have opinions but I want to kick off a discussion without starting from a specific viewpoint. And... go! [1] https://fedorahosted.org/cloud/ticket/127 -- Joe Brockmeier | Community Team, OSAS jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

15 34

[cloud] #116: Fedora Vagrant Boxes in Atlas
by Fedora Cloud Trac Tickets 16 Nov '15

16 Nov '15

#116: Fedora Vagrant Boxes in Atlas -----------------------+----------------------- Reporter: dustymabe | Owner: dustymabe Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting -----------------------+----------------------- We need to get our boxes into atlas to make it easier for people to pull down our vagrant boxes. lala/KB have got a few centos boxes in there. Let's get Fedora in there too. I will work with lala to add boxes and co-maintain. We'll use this ticket as an update on the progress. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/116> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 13

[cloud] #127: Working with the Server WG
by Fedora Cloud Trac Tickets 11 Nov '15

11 Nov '15

#127: Working with the Server WG -------------------------------------------+--------------------- Reporter: roshi | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: Collaboration & Communication | Keywords: meeting -------------------------------------------+--------------------- It was brought up in today's Server WG meeting [0] that they wanted to do some coordination with Workstation and Cloud. Ideas for WS are already there, but some thought should be put into how Server and Cloud can make things easier for both to work together when they're deployed. This ticket is a call to arms for some brain storming on this topic. [0] https://meetbot.fedoraproject.org/fedora- meeting-1/2015-10-13/serversig.2015-10-13-15.00.log.html -- Ticket URL: <https://fedorahosted.org/cloud/ticket/127> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 6

[cloud] #94: Producing Updated Cloud/Atomic Images
by Fedora Cloud Trac Tickets 11 Nov '15

11 Nov '15

#94: Producing Updated Cloud/Atomic Images ------------------------------+--------------------- Reporter: dustymabe | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: Cloud Base Image | Keywords: meeting ------------------------------+--------------------- We need to finalize our policy around producing updated images and then start doing it. Right now we have loosely decided to release new images once a month or whenever security updates require it. Additionally, as part of this we should also decide on a policy that determines when we stop updating images for a particular release. I imagine that we don't want to be producing updated images for Fedora X, Y, and Z all at the same time. Ideally we would only be producing updated images for the current/latest major version. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/94> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 24

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 01 Nov '15

01 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 30 Oct '15

30 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 28 Oct '15

28 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 28 Oct '15

28 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 28 Oct '15

28 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

Fwd: Call for Proposals: Virtualization & IaaS Devroom at FOSDEM 2016
by Joe Brockmeier 28 Oct '15

28 Oct '15

Please spread the word far and wide! -------- Forwarded Message -------- Subject: Call for Proposals: Virtualization & IaaS Devroom at FOSDEM 2016 Date: Wed, 28 Oct 2015 19:38:35 +0100 From: Mikey Ariel <mariel(a)redhat.com> Organization: Red Hat, Inc. To: rhev-tech(a)redhat.com, fosdem-planning(a)redhat.com, osas(a)redhat.com, rhev-devel(a)redhat.com I'm happy to announce that the call for proposals is now open for the virtualization and Infrastructure-as-a-Service devroom at FOSDEM 2016. See the full text in this blog post: http://community.redhat.com/blog/2015/10/call-for-proposals-fosdem16-virtua… Please don't hesitate to ping me with any questions, as well as share this post with people or projects that you think might be interested. Cheers, Mikey -- Mikey Ariel Community Lead, oVirt www.ovirt.org "To be is to do" (Socrates) "To do is to be" (Jean-Paul Sartre) "Do be do be do" (Frank Sinatra) Mobile: +420-702-131-141 IRC: mariel / thatdocslady Twitter: @ThatDocsLady -- Joe Brockmeier | Community Team, OSAS jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

[cloud] #124: CI for Fedora-Dockerfiles
by Fedora Cloud Trac Tickets 28 Oct '15

28 Oct '15

#124: CI for Fedora-Dockerfiles ----------------------+-------------------- Reporter: scollier | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: ----------------------+-------------------- Need a strategy to make sure all the images are built when new versions of Docker are released, or the images are updated with scripts, w/e. Need to figure out what the proper triggers are, and what the infrastructure it would be run on is. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/124> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 7

Re: [atomic-devel] Introducing sen: terminal user interface for docker engine
by Joe Brockmeier 27 Oct '15

27 Oct '15

On Tuesday, October 27, 2015 10:13:17 AM Stef Walter wrote: > On 27.10.2015 09:59, Tomas Tomecek wrote: > > Quoting Joe Brockmeier (2015-10-27 01:55:17) > > > >> Any chance this is going to be a Cloud feature for Fedora 24? > >> (Probably juuuust a bit late to slip into F23 now.) > >> > >> Best, > >> > >> jzb > > > > Way too late for f23 since I just made it work recently and I'm sure > > it's full of bugs (and missing features). > > > > I'm planning to package this to Fedora, no question. Can submit it > > as a f24 feature. Nice. I'm CC'ing the cloud working group here as well. > > One could think that sen is directly competing with cockpit. That's > > true. The difference is target audience -- sen is meant for folks > > who are not fans of webuis and prefer terminal instead. Not sure if > > this should be mentioned in the feature proposal. Nope, totally different audience. > Yup. Doesn't compete with Cockpit at all. In fact you could use it > within Cockpit's terminal, if you were feeling really funky ... I like this. Container-ception? Best, jzb -- Joe Brockmeier | Community Team, OSAS jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

2 1

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 26 Oct '15

26 Oct '15

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2015-10-28 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

2 week Atomic Host release ready for testing
by Mike McGrath 23 Oct '15

23 Oct '15

Latest Atomic Host build is ready for testing: http://dl.fedoraproject.org/pub/alt/fedora-atomic/images/testing/ kernel: 4.2.3-200 docker: 1.8.2-1 etcd: 2.0.13-2 kubernetes: 1.1.0-0.5 cloud-init: 0.7.6-3 ostree: 2015.6-2 atomic: 1.1-1 cockpit: 0.81

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud October 2015