[cloud] #138: Produce updated cloud base images monthly
by Fedora Cloud Trac Tickets
#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
7 years, 11 months
F24 Beta Release Notes (coming next week)
by Justin W. Flory
Hello all,
Before going further, please note this is a cross-posted thread! There
is a low-traffic mailing list, logistics(a)lists.fedoraproject.org, which
was created for multi-list collaboration on things like this topic. To
centralize discussion, please consider using that list for replies (even
if you unsubscribe after the discussion finishes).
Anyways, assuming all goes according to plan, the F24 Beta is due to
land on May 3rd, or in seven days from today. Therefore, it's time to
review and look over the release notes for the F24 Beta. The current
draft can be found on the wiki.
https://fedoraproject.org/wiki/F24_Beta_release_announcement
As of now, it is a forked version of the Alpha release announcement with
a few changes based on information I gathered from #fedora-qa. If you
could take some time to review the release notes and ensure everything
is *current* and correct since the Alpha release for areas you are
familiar and knowledgeable with, that would be appreciated so we can aim
to ship this next week.
Thanks all!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 11 months
Fedora-Cloud-Base 24 docker isn't included?
by Chris Murphy
Fedora-Cloud-Base-24-20160424.n.0.x86_64.qcow2
- Docker isn't installed. I can install it, but docker-storage-setup
won't setup a volume group with a thin pool if it's on a non-boot
drive apparently? Are both of these expected? (I normally use cloud
atomic which pretty much works out of the box, so this could be a user
misunderstanding of cloud base behavior).
--
Chris Murphy
7 years, 11 months
2-week build broken again?
by Josh Berkus
According to the downloads page:
"The latest two week build did not meet our testing criteria. The images
available are from over 14 days ago. Check the Project Atomic blog for
updates and information about Atomic blocker bugs."
Can someone let me know what's going on?
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
7 years, 11 months
Minutes from today's meeting
by Josh Berkus
Follows:
Meeting summary
ACTION: jzb to create Wiki page for OpenShift work (jberkus,
17:09:58)
action items from last week (jberkus, 17:11:16)
ACTION: jberkus to create Kubernetes examples for Fedora.
(jberkus, 17:12:15)
ACTION: kushal to update ticket that we are waiting for cloud
base image monthly updates til f24 (dustymabe, 17:15:34)
ACTION: imcleod take ticket 136 on vagrant file fixups
(dustymabe, 17:17:53)
ACTION: goern][ to create ticket for Fedora OpenShift Playground
(FOSP) work (dustymabe, 17:19:16)
open tickets (jberkus, 17:21:25)
https://fedorahosted.org/cloud/report/9 (jberkus, 17:21:38)
https://fedoraproject.org/wiki/FAD_Cloud_WG_2016 (jberkus, 17:23:11)
ACTION: jberkus and dustymabe to submit FAD application
(jberkus, 17:27:19)
ACTION: jberkus to update hotel information for FAD (jberkus,
17:30:47)
ACTION: maxamillion to update ticket 148, container best
practices (jberkus, 17:40:38)
open floor (dustymabe, 17:59:50)
https://fedorahosted.org/cloud/ticket/152 (dustymabe, 18:01:02)
ACTION: kushal to schedule Fedora Test Day for cloud (jberkus,
18:04:55)
Meeting ended at 18:07:15 UTC (full logs).
Action items
jzb to create Wiki page for OpenShift work
jberkus to create Kubernetes examples for Fedora.
kushal to update ticket that we are waiting for cloud base image
monthly updates til f24
imcleod take ticket 136 on vagrant file fixups
goern][ to create ticket for Fedora OpenShift Playground (FOSP) work
jberkus and dustymabe to submit FAD application
jberkus to update hotel information for FAD
maxamillion to update ticket 148, container best practices
kushal to schedule Fedora Test Day for cloud
Action items, by person
dustymabe
jberkus and dustymabe to submit FAD application
goern][
goern][ to create ticket for Fedora OpenShift Playground (FOSP) work
imcleod
imcleod take ticket 136 on vagrant file fixups
jberkus
jberkus to create Kubernetes examples for Fedora.
jberkus and dustymabe to submit FAD application
jberkus to update hotel information for FAD
kushal
kushal to update ticket that we are waiting for cloud base image
monthly updates til f24
kushal to schedule Fedora Test Day for cloud
maxamillion
maxamillion to update ticket 148, container best practices
People present (lines said)
jberkus (91)
dustymabe (82)
kushal (54)
maxamillion (38)
zodbot (23)
misc (22)
goern][ (9)
tflink (6)
scollier (6)
imcleod (4)
jbrooks (3)
jflory7 (1)
sayan (1)
roshi (1)
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
7 years, 11 months
[cloud] #150: Docker container refresh cadence
by Fedora Cloud Trac Tickets
#150: Docker container refresh cadence
----------------------------+---------------------
Reporter: acarter | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: Docker (Other) | Keywords: meeting
----------------------------+---------------------
I need to get a decision from this group about what refresh cadence we
should target for docker containers. We've gotten proposals to refresh
images based on updates passing testing and moving to stable in bodhi,
based on a regularly scheduled & predictable 2 week release cycle
(alternating weeks with Atomic) and (of course) both. We need clear
guidance on what the requirement will be at F25 so that we can design
tooling to support it. If someone has an idea of what the likely
requirements after F25 will be that might help us make somewhat informed
design decisions also. We plan to create an automated build -> test ->
release workflow for these refreshes so that we can scale to a large set
of images quickly.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/150>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
7 years, 11 months
[cloud] #131: make docker archived image get imported with lowercase tag
by Fedora Cloud Trac Tickets
#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
7 years, 11 months