#147: Don't overwrite download location for 2 week atomic images
-----------------------+---------------------
Reporter: dustymabe | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords: meeting
-----------------------+---------------------
Would be nice if the images don't get overwritten on each release. See
discussion in this email thread:
https://lists.fedoraproject.org/archives/list/cloud%40lists.fedoraproject.o…
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/147>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#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
#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
#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
#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/SHA1SUMShttps://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
#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
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/
#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
#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