cloud August 2016

cloud@lists.fedoraproject.org

24 participants
91 discussions

[cloud] #165: Reimbursement for the Cloud FAD
by Fedora Cloud Trac Tickets 12 Oct '16

12 Oct '16

#165: Reimbursement for the Cloud FAD --------------------+-------------------- Reporter: kushal | Owner: jzb@… Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: --------------------+-------------------- Attaching the flight ticket + cab receipts. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/165> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 6

[cloud] #160: Ship fedora-motd in F24 atomic image
by Fedora Cloud Trac Tickets 05 Oct '16

05 Oct '16

#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

1 2

[cloud] #155: Decide on post-GA update cadence for various deliverables
by Fedora Cloud Trac Tickets 05 Oct '16

05 Oct '16

#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

1 5

[cloud] #144: f23 atomic iso configures docker loopback storage
by Fedora Cloud Trac Tickets 05 Oct '16

05 Oct '16

#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

3 10

[cloud] #167: Decide a process about failed tests for Autocloud
by Fedora Cloud Trac Tickets 05 Oct '16

05 Oct '16

#167: Decide a process about failed tests for Autocloud --------------------+--------------------- Reporter: kushal | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting --------------------+--------------------- If we have a test failing the compose (right test, catching a real bug), should we stop the release till the time the bug gets resolved? My personal opinion is yes, first fix, and then only go ahead. For example [https://apps.fedoraproject.org/autocloud/jobs/353/output#283 this test] fails time to time on the vagrant virtualbox image. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/167> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 5

[cloud] #136: vagrant boxes fixups
by Fedora Cloud Trac Tickets 28 Sep '16

28 Sep '16

#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

1 5

[cloud] #168: Put OpenShift Origin in Container with Fedora Base
by Fedora Cloud Trac Tickets 21 Sep '16

21 Sep '16

#168: Put OpenShift Origin in Container with Fedora Base ------------------------------------+--------------------- Reporter: scollier | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: OpenShift Origin Image | Keywords: meeting ------------------------------------+--------------------- AIUI right now if you deploy OpenShift Origin on a Fedora Atomic host, it pulls down Origin running in CentOS based images. Perhaps we should port those images to Fedora. The images that the CentOS team are created are located here: https://wiki.centos.org/ContainerPipeline We would want to coordinate the effort with the images on Docker hub: https://hub.docker.com/u/openshift/ And figure how this fits into Fedoras build system. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/168> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 5

[cloud] #169: Spec for IRC bot to notify about blockers
by Fedora Cloud Trac Tickets 14 Sep '16

14 Sep '16

#169: Spec for IRC bot to notify about blockers ---------------------+--------------------- Reporter: jberkus | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting ---------------------+--------------------- One of the issues we have with release blockers is slow response by the fedora-cloud WG. As that group is very IRC-centric, we'd like to have some form of notification via IRC when a release blocker is encountered. Here's a draft spec, please revise: 1. whenever a release blocker issue is filed or updated, a message will be sent via bot to the #fedora-cloud channel; 2. the /topic of #fedora-cloud will be updated with a list of release- blocker issues once a day. Questions: how do we identify release-blocker issues? This relates to issue https://fedorahosted.org/cloud/ticket/167 -- Ticket URL: <https://fedorahosted.org/cloud/ticket/169> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 5

[cloud] #147: Don't overwrite download location for 2 week atomic images
by Fedora Cloud Trac Tickets 14 Sep '16

14 Sep '16

#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

1 16

[cloud] #154: make Fedora Atomic download page clearer
by Fedora Cloud Trac Tickets 14 Sep '16

14 Sep '16

#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

1 5

← 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 August 2016