#160: Ship fedora-motd in F24 atomic image
--------------------+---------------------
Reporter: rtnpro | Owner: rtnpro
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords: meeting
--------------------+---------------------
fedora-motd-0.1.3-1 has been tested and moved to stable F24 repo. We need
to come up with a plan to ship it an upcoming Fedora 24 atomic cloud
images.
https://bodhi.fedoraproject.org/updates/FEDORA-2016-c8948356b9
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/160>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#155: Decide on post-GA update cadence for various deliverables
-------------------------+---------------------
Reporter: maxamillion | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords: meeting
-------------------------+---------------------
Currently there are plans to update release deliverables more formally
post Fedora 24 GA. These aren't all going to happen immediately following
the release but work will be done to enable them ASAP.
Some of these we've already decided on in the past but a couple still need
decisions. The goal here is to simply determine what we would like to see
as an ideal release cadence of updated deliverables. Technical
implementation and details will be outside this scope.
https://fedoraproject.org/wiki/Fedora_Program_Management/Updating_deliverab…
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/155>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#144: f23 atomic iso configures docker loopback storage
-------------------------+--------------------
Reporter: jasonbrooks | Owner:
Type: defect | Status: new
Priority: major | Milestone: Future
Component: --- | Keywords:
-------------------------+--------------------
ISO installs of f23 atomic get configured w/ loopback storage, which is a
bad thing: http://www.projectatomic.io/blog/2015/06/notes-on-fedora-
centos-and-docker-storage-drivers/.
F22 Atomic had the correct config.
Running "docker info" on a VM installed from Fedora-Cloud_Atomic-
x86_64-22.iso yields:
{{{
...
Storage Driver: devicemapper
Pool Name: fedora-docker--pool
Pool Blocksize: 65.54 kB
Backing Filesystem: extfs
Data file:
Metadata file:
...
}}}
Running "docker info" on a VM installed from Fedora-Cloud_Atomic-
x86_64-23.iso yields:
{{{
...
Storage Driver: devicemapper
Pool Name: docker-253:0-153054-pool
Pool Blocksize: 65.54 kB
Backing Filesystem: extfs
Data file: /dev/loop0
Metadata file: /dev/loop1
...
}}}
I looked over the kickstarts, but I'm not clear on what might be causing
this.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/144>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#136: vagrant boxes fixups
-----------------------+---------------------
Reporter: dustymabe | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords: meeting
-----------------------+---------------------
There are few suggestions we are getting for our vagrant boxes here are
some of them:
Add a cdrom device to the boxes (makes installing vbox guest additions
from ISO easier)
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/136>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#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
#154: make Fedora Atomic download page clearer
-------------------------------+---------------------
Reporter: jberkus | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: Docker Host Image | Keywords: Meeting
-------------------------------+---------------------
The Fedora Atomic Host Download page is confusing to users. I'd like to
make some changes making it clearer what to download and why, including:
* The ISO images should be a main option, not a link in the sidebar
* The qcow2 images, not the raw images, should say "if you're not sure
what to use, use this".
* Each download option should have a link to the specific docs for
installing that kind of download (will wait on new Atomic Host docs,
though)
Also, it would be great if we could list on the download page somewhere
what date the images are from for each 2-week build.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/154>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#164: Fedora Atomic Host 24 Not Available
---------------------+-----------------------
Reporter: jberkus | Owner:
Type: task | Status: new
Priority: blocker | Milestone: Future
Component: --- | Keywords: downloads
---------------------+-----------------------
Fedora Atomic Host 24 wasn't available from the mirrors last week, and is
apparently still unavailable.
Checking getfedora.org today, Atomic Host has been removed from the
Downloads page: https://getfedora.org/en/cloud/download/index.html
What's going on?
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/164>
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
#156: Need complete Kickstart docs for Atomic Host
-------------------------------+---------------------
Reporter: jberkus | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: Docker Host Image | Keywords: Meeting
-------------------------------+---------------------
The documentation here:
http://www.projectatomic.io/docs/fedora_atomic_bare_metal_installation/
punts a lot of practical steps off to the main Fedora docs on how to do a
kickstart install. Since often atomic bare metal installs will involve a
system without full GUI support, we need to make it easy for people to do
this.
Part of the issue is that kickstart isn't exactly developer-friendly; it's
a bit complicated to use. But we can at least doc a step-by-step.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/156>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System