Hi all,
During Flock PRD discussion, a proposal was put up about changing the
name of the WG to Atomic. We have few open questions from last week's meeting. I
will try to put those down here, if anyone wants to add to that list, or
explain things better, please go ahead and reply to the thread :)
* If we rename how to make sure that the users know that we are not
abandoning the cloud?
* If we create a new group, then who else are still interested about
helping out the Cloud WG?
* We will require new user stories related to Atomic. This also brings
in the question about old user stories in current PRD. They are still
mostly valid. PRD updation is surely one major point towards Atomic WG.
* Who will maintain Atomic workstation? If it is workstation wg, then
how to reduce duplication of efforts?
* What will happen to the Cloud Base image?
* Who will maintain the Vagrant images?
* What will happen to our effort to push Fedora to different public
cloud services? We have AMI(s) right now, we also push to Digital
Ocean.
Kushal
--
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.inhttps://dgplug.org
We've talked about this for a while, but let's make it formal. The plan
is to transition from Cloud as a Fedora Edition to Something Container
Clustery (see https://fedoraproject.org/wiki/Objectives/ProjectFAO)
But, we still need cloud as a _deploy target_. The FAO-container-thing
will continue to have cloud image deploy targets (as well as bare
metal). I think it makes sense to _also_ have Fedora Server as a cloud
deploy target.
This could possibly be both a Fedora Server Minimal Cloud Image and
Fedora Server Batteries Included Image — but that'd be up to Server WG,
I think.
Overall, I'm proposing:
1. Dissolve Cloud WG (See below; don't panic)
2. Form new Atomic WG or FAO WG (name to be bikeshedded)
(a lot of overlap in membership with current Cloud WG, of course!)
3. _Keep_ Cloud SIG as a gathering point around cloud technology and
covering shared underlying technology (fedimg, koji cloud image
production, autocloud). Think of this as analogous in some ways
to something like the ARM SIG.
4. Change https://getfedora.org/cloud/ to
https://getfedora.org/atomic/ or https://getfedora.org/fao/
5. Create new http://cloud.fedoraproject.org/ in the same style as
https://arm.fedoraproject.org/
6. New Atomic/FAO WG produces Whatever New Deliverable (starting
with Two Week Atomic)
7. Cloud Base Image becomes base (uh, see what I did there?) for new
Fedora Server cloud image (or images).
8. Vagrant image _probably_ the same — or maybe becomes its own
thing?
9. ???
10. Profit!
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
*Issue:*
VARIANT_ID isn't updated within /etc/os-release from this commit:
https://pagure.io/fork/sgallagh/fedora-release/c/56267336c738f80e3e7a344c74…
to Fedora 24 Atomic host.
This is needed in order to differentiate Fedora 24 Atomic hosts from their
other versions (Server + Cloud).
With the help from Stephen Gallagher, it was found that the updated package
set for fedora-release-atomic is missing when generating Fedora 24 Atomic.
*To replicate: *
See: https://paste.fedoraproject.org/390347/
+ cat /etc/os-release after upgrade (the commit above should of added
VARIANT_ID="atomic.host" to /etc/os-release
*Resolution:*
In order to get this resolved, the missing package set
(fedora-release-atomic) should be added :)
Many thanks!
Charlie Drage
PGP - 4096R/C037D617
http://pgp.mit.edu/pks/lookup?op=get&search=0xDA227403C037D617
Hi folks! Just wanted to keep everyone informed.
We had a bit of a panic drill with the Alpha today; it turns out the
Cloud images are completely broken, and in fact have been for months,
only apparently no-one bothers to look at the output of our shiny
automated test systems (autocloud has been reporting this all along,
but apparently no-one's been doing anything about it).
We've worked around the multiple issues and there is now a new compose
running, which will be Alpha-1.2 (some of the image names will be a bit
messed up though). The changes should really only affect the Cloud
images, so most Alpha-1.1 testing should remain valid. But once Alpha-
1.2 lands, we should switch over to testing that, and make sure the
cloud images actually work. It should arrive in ~5-6 hours.
Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1369794https://bugzilla.redhat.com/show_bug.cgi?id=1369934
summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2016-08-24/fedora_cloud_…
full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2016-08-24/fedora_cloud_…
==================================
#fedora-meeting-1: fedora cloud WG
==================================
Meeting started by dustymabe at 17:07:34 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-08-24/fedora_cloud_…
.
Meeting summary
---------------
* previous meeting action items (dustymabe, 17:10:49)
* kushal started wg renaming discussion on the mail list -
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org…
(dustymabe, 17:14:38)
* ACTION: rtnpro will add test workflow (and test cases) for testing
fedora-motd on F24 atomic image (dustymabe, 17:14:54)
* ACTION: gholms to test updated cloud-init on f24 for f25
(dustymabe, 17:15:18)
* kushal needs one more +1 for FBR to update autocloud tests while in
freeze (dustymabe, 17:15:41)
* #125 Fedora-Dockerfiles examples for Kubernetes (dustymabe, 17:17:17)
* LINK: https://fedorahosted.org/cloud/ticket/125 (dustymabe,
17:17:25)
* #147 Don't overwrite download location for 2 week atomic images
(dustymabe, 17:18:33)
* LINK: https://fedorahosted.org/cloud/ticket/147 (dustymabe,
17:18:42)
* #153 design, deploy and document Fedora OpenShift Playground (FOSP)
(dustymabe, 17:21:06)
* LINK: https://fedorahosted.org/cloud/ticket/153 (dustymabe,
17:21:13)
* ACTION: vvaldez to talk with misc, scollier, jberkus about how he
can help with FOSP (#153) (dustymabe, 17:26:47)
* #155 Decide on post-GA update cadence for various deliverables
(dustymabe, 17:27:01)
* LINK: https://fedorahosted.org/cloud/ticket/155 (dustymabe,
17:27:06)
* LINK:
https://lists.fedoraproject.org/archives/list/rel-eng@lists.fedoraproject.o…
(maxamillion, 17:29:19)
* #167 Decide a process about failed tests for Autocloud (dustymabe,
17:33:45)
* LINK: https://fedorahosted.org/cloud/ticket/167 (dustymabe,
17:33:54)
* #168 Put OpenShift Origin in Container with Fedora Base (dustymabe,
17:37:24)
* LINK: https://fedorahosted.org/cloud/ticket/168 (dustymabe,
17:37:30)
* open floor (dustymabe, 17:45:28)
Meeting ended at 17:58:26 UTC.
Action Items
------------
* rtnpro will add test workflow (and test cases) for testing fedora-motd
on F24 atomic image
* gholms to test updated cloud-init on f24 for f25
* vvaldez to talk with misc, scollier, jberkus about how he can help
with FOSP (#153)
Action Items, by person
-----------------------
* gholms
* gholms to test updated cloud-init on f24 for f25
* misc
* vvaldez to talk with misc, scollier, jberkus about how he can help
with FOSP (#153)
* vvaldez
* vvaldez to talk with misc, scollier, jberkus about how he can help
with FOSP (#153)
* **UNASSIGNED**
* rtnpro will add test workflow (and test cases) for testing
fedora-motd on F24 atomic image
People Present (lines said)
---------------------------
* dustymabe (115)
* maxamillion (16)
* jbrooks (15)
* zodbot (14)
* nzwulfin (9)
* kushal (8)
* walters (8)
* trishnag (6)
* misc (5)
* vvaldez (3)
* sayan (2)
* gholms (2)
* bowlofeggs (1)
* coremodule (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Hi all,
I will not be available for today's Fedora Cloud meeting.
See you, next week!
Thanks,
rtnpro
--
Ratnadeep Debnath,
https://www.waartaa.com
GPG Fingerprint: 033C 8041 A0E9 CDBA 2E02 B785 2119 5486 F245 DFD6
Hi,
I will be missing tonight's meeting. Sorry for informing late.
Kushal
--
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.inhttps://dgplug.org
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2016-08-24 from 17:00:00 to 18:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://apps.fedoraproject.org/calendar/meeting/1999/