cloud December 2015

cloud@lists.fedoraproject.org

29 participants
97 discussions

[cloud] #125: Fedora-Dockerfiles examples for Kubernetes
by Fedora Cloud Trac Tickets 01 Sep '16

01 Sep '16

#125: Fedora-Dockerfiles examples for Kubernetes ----------------------+-------------------- Reporter: scollier | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: ----------------------+-------------------- Would be nice to have a couple of services put together to create an application that is managed by Kubernetes on Atomic. This would need to be clearly documented. We would need the proper json kubernetes files to launch the apps with. A few examples would be nice: 1. simple web server with a database 2. simple web server 3. others? -- Ticket URL: <https://fedorahosted.org/cloud/ticket/125> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 13

[cloud] #143: Proposals for F24 features
by Fedora Cloud Trac Tickets 14 Jul '16

14 Jul '16

#143: Proposals for F24 features --------------------+--------------------- Reporter: kushal | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting --------------------+--------------------- We need the proposals in for Fedora 24 release -- Ticket URL: <https://fedorahosted.org/cloud/ticket/143> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 9

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

16 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 03 Jun '16

03 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 16 May '16

16 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

[cloud] #138: Produce updated cloud base images monthly
by Fedora Cloud Trac Tickets 28 Apr '16

28 Apr '16

#138: Produce updated cloud base images monthly -----------------------+--------------------- Reporter: dustymabe | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting -----------------------+--------------------- An extension of https://fedorahosted.org/cloud/ticket/94 We have elected to release cloud base images monthly for the "current" release of Fedora. The releng infra is in place to do this already, we just need appropriate testing and process around it to release new images and verify they aren't broken. This ticket will track progress/status of this. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/138> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 13

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

21 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 25 Feb '16

25 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

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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud December 2015