cloud April 2016

cloud@lists.fedoraproject.org

26 participants
100 discussions

[cloud] #148: Container "Packager" Guildelines and Naming Conventions
by Fedora Cloud Trac Tickets 15 Jun '16

15 Jun '16

#148: Container "Packager" Guildelines and Naming Conventions -------------------------+--------------------- Reporter: maxamillion | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting -------------------------+--------------------- Container Layered Image Builds[0] (CLIBs) are going to be the first deliverable provided by the Fedora Project as an official delivery/release build artifact other than RPM. The first container implementation we're targeting is Docker. With RPMs, there are many guildelines in place on how to create them[1][2] for official inclusion for Fedora. We should really look into doing something similar for CLIBs. Below are a couple of links to draft docs to address some of these. I would like peer review on these docs as well as brainstorming on areas that might also need attention around this. https://fedoraproject.org/wiki/PackagingDrafts/Containers https://fedoraproject.org/wiki/PackagingDrafts/Package_Review_Process_with_… I look forward to feedback and continued discussion. -AdamM [0] - https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service [1] - https://fedoraproject.org/wiki/Package_Review_Process [2] - https://fedoraproject.org/wiki/Packaging:Guidelines -- Ticket URL: <https://fedorahosted.org/cloud/ticket/148> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 13

[cloud] #115: Fedora Cloud FAD (late 2015/early 2016)
by Fedora Cloud Trac Tickets 15 Jun '16

15 Jun '16

#115: Fedora Cloud FAD (late 2015/early 2016) -----------------------+----------------------- Reporter: dustymabe | Owner: dustymabe Type: task | Status: new Priority: normal | Milestone: Future Component: Planning | Keywords: meeting -----------------------+----------------------- At Flock we talked about having a Fedora Activity Day for the cloud working group to get some work done. This ticket will serve as a stub for planning and coordination of this event. The first step is to write up a proposal and submit it for review. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/115> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 9

[cloud] #93: Getting sha256sum published for the cloud images
by Fedora Cloud Trac Tickets 02 Jun '16

02 Jun '16

#93: Getting sha256sum published for the cloud images --------------------------------------------------+----------------------- Reporter: kushal | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 22 Component: Infrastructure & Release Engineering | Keywords: meeting --------------------------------------------------+----------------------- This will help things systemd to search the images provided by Fedora in a standard way using nspawn tool. Example of such file from ubuntu: https://cloud-images.ubuntu.com/trusty/current/SHA1SUMS https://cloud-images.ubuntu.com/trusty/current/SHA256SUMS.gpg -- Ticket URL: <https://fedorahosted.org/cloud/ticket/93> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 15

[cloud] #126: python3 only means ansible won't work
by Fedora Cloud Trac Tickets 17 May '16

17 May '16

#126: python3 only means ansible won't work ------------------------------+--------------------- Reporter: dustymabe | Owner: Type: task | Status: new Priority: major | Milestone: Future Component: Cloud Base Image | Keywords: meeting ------------------------------+--------------------- If we have only python3 in our cloud images then ansible won't work as it assumes /usr/bin/python is there. You end up with: ``` GATHERING FACTS *************************************************************** failed: [f23] => {"failed": true, "parsed": false} /bin/sh: /usr/bin/python: No such file or directory ``` We need to figure out a solution to this. For f23 cloud base image maybe we decide that adding it via cloud-init is enough.. For vagrant I think we should definitely include it in the image. There also could be some workaround that I don't know about for this. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/126> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 9

dnf in Dockerfiles
by Joe Brockmeier 15 May '16

15 May '16

Hey all, So dgilmore pointed out that f22 docker images will not have yum installed - which means we need to update the Dockerfiles for f22 to use dnf and not yum. We probably ought to go through and sanity-check them all to ensure they work with the f22 image as well before, say, beta. I'm CC'ing Scott b/c, if I'm not mistaken, he's done quite a lot of the work so far on the Dockerfiles - but also, I think he's looking for assistance there in keeping the effort going. Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

10 12

Re: [Marketing] Re: [MAGAZINE PROPOSAL] Fwd: [DRAFT] Why we're retiring 32-bit Images
by Paul W. Frields 05 May '16

05 May '16

On Thu, Apr 21, 2016 at 06:14:05PM -0400, Justin W. Flory wrote: > On 04/21/2016 05:10 PM, Joe Brockmeier wrote: > >On 04/21/2016 05:04 PM, Paul W. Frields wrote: > >>I can't make tonight's Magazine meeting, but I'm +1 to get this out > >>ASAP. I've moved this article to Pending Review, but I already > >>reviewed it and it looks fine. I added a couple additional links for > >>SEO power. > >> > >>Anything Justin OK's for schedule for this is fine by me, assume > >>+1. :-) And I'll be happy to help with social media, just please leave > >>me an email or IRC message to do so and I'll catch it in the morning. > > > >I'd like to put this up too, but I don't think we've settled the > >question on 32-bit that Dennis raised. Will check again. > > > > Do we still want to aim for publishing this tomorrow? In the meeting, we > agreed to publish it Friday, but if it's not ready or the questionable part > can't be edited out, let's definitely hold on this. The article apparently was left in Scheduled status -- I moved it back to Pending Review status, and Patrick Uiterwijk kindly stripped it from the Fedora Planet so it wouldn't confuse anyone. It was out there for a few hours, though, FYI. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com

4 5

[PATCH] cloud-base-vagrant: Add sshfs to support vagrant-sshfs plugin
by Dusty Mabe 30 Apr '16

30 Apr '16

Adding sshfs into the image will make it so that users won't have to wait for the package to be installed on bringup. --- fedora-cloud-base-vagrant.ks | 3 +++ 1 file changed, 3 insertions(+) diff --git a/fedora-cloud-base-vagrant.ks b/fedora-cloud-base-vagrant.ks index df338d7..f7f1518 100644 --- a/fedora-cloud-base-vagrant.ks +++ b/fedora-cloud-base-vagrant.ks @@ -32,6 +32,9 @@ dnf-yum # users setup. This can actually take a bit of time. Just fold it # in to the base box disk image rsync +# Add fuse-sshfs so that the vagrant-sshfs plugin won't have to +# install it on boot. https://github.com/dustymabe/vagrant-sshfs +fuse-sshfs %end %post --erroronfail -- 2.7.4

1 0

ATTN: Beta Blocker - docker is broken running F-24 on F-24
by Peter Robinson 28 Apr '16

28 Apr '16

So heads up because I'm not sure we want docker broken again at GA for F-24. https://bugzilla.redhat.com/show_bug.cgi?id=1322909 The bug has been open since end of March and is on x86 and it appears F-24 docker binaries are broken so F-24 (and likely other) images don't work on F-24. I'm not sure how the cloud SIG tests docker deliverables but now might be a good time to move to F-24 on the host. Peter

5 9

Re: [Marketing] Re: [MAGAZINE PROPOSAL] Fwd: [DRAFT] Why we're retiring 32-bit Images (was Re: Retiring 32-bit images)
by Joe Brockmeier 27 Apr '16

27 Apr '16

On 04/07/2016 06:59 PM, Joe Brockmeier wrote: > On 04/07/2016 06:47 PM, Ryan Lerch wrote: >> Will it just be a featured image? Or are there other graphics required? >> > Just the featured image. Thanks! OK, looks like we have the featured image here: https://pagure.io/fedoramagazine-images/issue/12 Is this ready to go? Is there a specific date to target or run it now, or...? Best, jzb -- Joe Brockmeier | Community Team, OSAS jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

8 35

Expanding objectives for FAD
by Josh Berkus 27 Apr '16

27 Apr '16

Folks, We have an outline of objectives for the FAD which is nowhere near detailed enough for the council to approve it. Questions follow: Automated testing Atomic Host Tests Plan for CI builds/testing for Host/OStree -- What specific deliverables do we expect from the FAD? A specification? Writing some tests? More? -- What are all of the things we are testing? Atomic Edition F25 Change Updated PRD Proposal to Council with the above -- What F25 change? What will we be doing about it at the FAD? -- Links to issues? Docker How to handle multiple versions of Docker Docker vs. runc -- I'll expand this one. Registry Public Atomic Registry for Fedora? -- Again, I'll expand this one Documentation At least one F24-focused runbook. -- For what? Will the runbook be produced at the FAD? Adam, can you maybe add an item about the new releng pipeline? -- -- Josh Berkus Project Atomic Red Hat OSAS

2 1

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud April 2016