#81: Create cloud training materials for ambassadors
-------------------------------------------+-----------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 22
Component: Collaboration & Communication | Keywords:
-------------------------------------------+-----------------------
Many Fedora Ambassadors come from a desktop or old-school sysadmin
background. Cloudy concepts are new and foreign. In talking with some of
them, it was suggested that it'd be really, really helpful to have some
basic training materials for our own ambassadors -- what is cloud, why
does it matter, what is Fedora Cloud, what is our strategy, why do _we_
matter, and so on.
http://mattdm.org/fedora/cloud2013/#1 might be a starting point. Maybe
some more interactive training would even be useful.
Of course, it'd also be awesome to get some people from the new modern
world interested in being ambassadors as well -- another direction to
approach the same issue. (But even then, training on what _we_ are doing
would be useful.)
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/81>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#38: Automatic Smoketests on Image Build
--------------------------+-------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Alpha)
Component: Testing & QA | Keywords:
--------------------------+-------------------------------
'''Summary:''' When a new image is built in Koji, automatically boot it
and run a basic matrix of tests.
'''Importance:''' moderate (worst case, we can keep doing this by hand)
'''Timeframe:''' F21 alpha / Want to reduce manual test workload
'''Fedora Sub-Project/SIG:''' QA and the Taskotran project
'''Cloud SIG owner:''' Sandro Mathys
https://fedoraproject.org/wiki/Taskotron
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/38>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#25: File F21 change: OpenShift Out-of-the-Box Image
--------------------------------+------------------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Feature Deadline)
Component: OpenShift Origin | Keywords:
Image |
--------------------------------+------------------------------------------
'''Summary:''' Fedora Cloud agreed to make a base image plus several
tailored to specific purposes. This is one of the tailored ones —
OpenShift ready to run.
'''Importance:''' nice to have (if we fail to do it, we are not any worse-
off than we are now, and OpenShift can still be installed on the base
iamge.)
'''Timeframe:''' F21 alpha / If it's not ready for alpha, we have missed
this release
'''Scope:''' self-contained (in collaboration with OpenShift developers)
'''Cloud SIG owner:''' TBD
https://fedoraproject.org/wiki/Changes/OpenShift_Out-of-the-
Box_Cloud_Image
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/25>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#28: discuss modularized SELinux policy packaging
------------------------------+-----------------------
Reporter: mattdm | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Fedora 22
Component: Cloud Base Image | Keywords:
------------------------------+-----------------------
Possible F22 feature?
Summary: Monolith SELinux policy has rules for everything that could
exist, not just that which is installed. Possible room for reduction here.
'''Importance:''' nice-to-have
'''Timeframe:''' F21 or F22 / This is not low-hanging fruit.
'''Scope:''' self-contained (SELinux)
'''
Cloud SIG owner:''' TBD
(No Feature filed at this time -- discuss with SELinux policy maintainers)
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/28>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#73: test cases for cloud-init
--------------------------+-------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Final)
Component: Testing & QA | Keywords:
--------------------------+-------------------------------
We have a number of bugs for #cloud-config syntax not working properly --
probably because it's mostly been tested with debian/ubuntu-universe
tools.
For example:
* https://bugzilla.redhat.com/show_bug.cgi?id=1126857
* https://bugzilla.redhat.com/show_bug.cgi?id=1126365
We should fix these, obviously, but also, each time we fix one, we should
make a test case -- ideally an automatic test case! -- to make sure it
stays fixed.
It would also be nice to have some other test cases for cloud-config
syntax we expect to work.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/73>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#57: get official images uploaded into Rackspace
-------------------------------------------------+-------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21
Component: Infrastructure & Release | (Final)
Engineering | Keywords:
-------------------------------------------------+-------------------------
Work with Rackspace engineers... they don't yet have public image sharing,
but getting our official images uploaded to a fedora account as part of
the release process would be a good start.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/57>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#42: policies for batched updates
------------------------------+-------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Final)
Component: Software Updates | Keywords:
------------------------------+-------------------------------
See ticket #18
We want to putting out updated images periodically (or aperiodically as
needed). What are the rules? What are the procedures? Where are they
documented?
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/42>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#12: send list of packages on cloud images to spot for change from %doc to
%license
------------------------------+-----------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21
Component: Cloud Base Image | Keywords: easyfix
------------------------------+-----------------------
See https://fedorahosted.org/fpc/ticket/411
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/12>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#37: External Need: software collections
-------------------------------------+-------------------------------------
Reporter: mattdm | Owner: mattdm
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Feature
Component: Collaboration & | Deadline)
Communication | Keywords:
-------------------------------------+-------------------------------------
External Need: Software Collections for Cloud Users
Summary: Provides selection of language stacks of particular versions to
users.
'''Importance:''' vital (provides a meaningful reason to use Fedora cloud
image, and helps insulate against rapid change)
'''Timeframe:''' F21 release / This is a requirement of users in
production.
'''Fedora Sub-Project/SIG:''' Environments and Stacks
'''Cloud SIG owner:''' mattdm -- more help wanted :)
Draft feature proposal:
https://fedoraproject.org/wiki/Cloud_Changelist#External_Need:_Software_Col…
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/37>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
#63: list fedora accounts needed for releng to make official cloud images
content
--------------------+--------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Branch)
Component: --- | Keywords:
--------------------+--------------------------------
What official accounts and agreements do we need to upload cloud images to
our intended targets, including Amazon AWS, Google GCE, and etc?
What do we need to a) upload docker base images and b) do docker trusted
builds?
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/63>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System