From Fedora Project Wiki
(→‎Quick Links: Add a link to the Cloud Sig)
 
(30 intermediate revisions by 9 users not shown)
Line 9: Line 9:


* Get running with Fedora in the cloud here: [https://getfedora.org/en/cloud/download/ https://getfedora.org/en/cloud/download/]
* Get running with Fedora in the cloud here: [https://getfedora.org/en/cloud/download/ https://getfedora.org/en/cloud/download/]
* Pre-release software (alphas, betas) can be found at [https://getfedora.org/en/cloud/prerelease/ https://getfedora.org/en/cloud/prerelease/]
* Pre-release software (Rawhide) can be found in [https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Cloud/ Cloud Rawhide nightlies].
 
* '''Get involved''' as a member of the [/Cloud_SIG Fedora Cloud SIG] today.
== Fedora Cloud Atomic Image Download Links ==
 
The links below are meant to allow for users to have a "single point of download" so that the location may be stored or used in a scripted way to always download the latest image.
 
A couple of things to note:
* The <code>_latest</code> URLs are simply 302 redirects to the actual image name and URL for the mirror network
* The image that is actually downloaded will be unique for every release, it's name will be the same as is located at <code>_latest_filename</code>, which has been provided for easy scripting.
 
Example script:
<pre>
#!/bin/bash
 
image_name=$(curl -s https://getfedora.org/atomic_qcow2_latest_filename)
curl -L https://getfedora.org/atomic_qcow2_latest -o $image_name
 
ls -l $image_name
</pre>
 
{|
! Image !! Latest URL !! Latest Filename URL
|-
| Fedora Atomic qcow2 || https://getfedora.org/atomic_qcow2_latest || https://getfedora.org/atomic_qcow2_latest_filename
|-
| Fedora Atomic raw || https://getfedora.org/atomic_raw_latest || https://getfedora.org/atomic_raw_latest_filename
|-
| Fedora Atomic Vagrant libvirt || https://getfedora.org/atomic_vagrant_libvirt_latest || https://getfedora.org/atomic_vagrant_libvirt_latest_filename
|-
| Fedora Atomic Vagrant VirtualBox || https://getfedora.org/atomic_vagrant_virtualbox_latest || https://getfedora.org/atomic_vagrant_virtualbox_latest_filename
|-
| Fedora Atomic ISO Installer || https://getfedora.org/atomic_iso_latest || https://getfedora.org/atomic_iso_latest_filename
|}


= Our Goals =
= Our Goals =


The Fedora Cloud Working group leads the design and production of Fedora's Cloud edition.
The ''Fedora Cloud Edition'' allows users to work across multiple virtual environments at
scale by focusing engineering efforts on supplying a base disk images, rpms, and
container-based tooling of various architectures for working in and around public and
private cloud environments. The ''Cloud Edition Working Group'' targets efforts towards the
facilitation and improvement of continuous delivery by ensuring that Fedora project
solutions support cloud native workflow without forcing users to understand all of the
environments in which they require enablement.


== Role in Fedora ==
== Role in Fedora ==
Line 61: Line 36:
= Product Requirements Document =
= Product Requirements Document =


[[Cloud/Cloud_PRD | Cloud PRD]]
[[Cloud/Cloud_PRD | Cloud PRD ]]


== Runbooks / Standard Operating Procedures ==
== Runbooks / Standard Operating Procedures ==
Line 67: Line 42:
Let's keep track of how things work here so that we can help integrate new folks more easily.
Let's keep track of how things work here so that we can help integrate new folks more easily.


[[Cloud/Atomic_Runbooks | Atomic SOPs and Runbooks]]
[[Cloud/Release_Checklist | Production Release Checklist ]]


== RFCs ==
== RFCs ==


This section will list the RFCs in progress or RFCs that have been accepted by the Cloud Working Group.
This section lists the RFCs in progress or RFCs that have been accepted by the Cloud Working Group.
=== RFCs for Review ===


[[Cloud/Cloud_RFC_Docker_Trusted_Images_Rebuild_Policy | RFC: Rebuild Policy for Fedora Docker Trusted Images]]
=== RFCs Recently Accepted ===
[https://pagure.io/cloud-sig/blob/main/f/guidelines/changing-fedora-cloud-images.md Guidelines for Changing Fedora Cloud Images]


= Communications =
= Communications =
Line 79: Line 56:
It is our policy to default to open; wherever possible, all communications will be held in the open and archived for future public reference. In some rare cases, it may necessary for some members of the group to enter into non-disclosure agreements (for example, when working with public cloud vendors) but such circumstances should be minimal and not impact core decisions of the group.
It is our policy to default to open; wherever possible, all communications will be held in the open and archived for future public reference. In some rare cases, it may necessary for some members of the group to enter into non-disclosure agreements (for example, when working with public cloud vendors) but such circumstances should be minimal and not impact core decisions of the group.


Our primary forum for discussion is the Cloud SIG mailing list, https://lists.fedoraproject.org/mailman/listinfo/cloud. Members also regularly are available in the <tt>#fedora-cloud</tt> IRC channel on FreeNode.
Our primary forum for discussion is the Cloud SIG mailing list, https://lists.fedoraproject.org/mailman/listinfo/cloud. Members also regularly are available in the <tt>#fedora-cloud</tt> IRC channel on libera.chat.


The Cloud SIG will work with other groups (Base WG, QA, Rel-eng, etc.) as needed to help deliver the final cloud products.
The Cloud SIG will work with other groups (Base WG, QA, Rel-eng, etc.) as needed to help deliver the final cloud products.
Line 87: Line 64:
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/


== IRC ==
== Real-time Communications ==
=== Matrix ===
<nowiki>#cloud:fedoraproject.org</nowiki> on [https://matrix.org/ Matrix.org]
=== IRC ===
<nowiki>#fedora-cloud</nowiki> on [https://libera.chat/ Libera.Chat].


<nowiki>#fedora-cloud</nowiki> on [https://freenode.net/ Freenode].
== Working Group Members and Points of Contact ==


== Points of Contact ==
At a later date we will likely establish a formal on-boarding process for new community members but at this time if you're interested in joining, simply add your name below either in the "General" section or under a specific sub topic and then reach out via the irc channel and mailing list to introduce yourself.
 
General:
* [[User:davdunc | David Duncan ]]
* [[User:mhayden | Major Hayden ]]
* [[User:dustymabe | Dusty Mabe ]]
* [[User:Ngompa | Neal Gompa ]]
* [[User:spotz | Amy Marrich ]]
* [[User:davide | Davide Cavalca ]]
* [[User:salimma | Michel Salim ]]
* [[User:cmurf | Christopher Murphy ]]


Testing:
Testing:
* [[User:Kushal | Kushal Das ]]
* [[User:Kushal | Kushal Das ]]
* [[User:Rtnpro | rtnpro ]]
* [[User:davdunc | David Duncan ]]
* [[User:Adimania | adimania ]]
* [[User:miabbott | miabbott ]]
* [[User:Sayan | sayan ]]
* [[User:Roshi | roshi ]]


Release Engineering:
Release Engineering:
* [[User:Kushal | Kushal Das ]]
* [[User:davdunc | David Duncan]]
* [[User:Dustymabe | dustymabe ]]
* [[User:ngompa | Neal Gompa ]]
* [[User:Maxamillion | maxamillion ]]
* [[User:mhayden | Major Hayden ]]
* [[User:dustymabe | Dusty Mabe ]]


Documentation/Marketing:
Documentation/Marketing:
* [[User:Kushal | Kushal Das ]]
* [[User:davdunc | David Duncan ]]
* [[User:Nzwulfin | nzwulfin ]]
* [[User:mhayden | Major Hayden ]]
* [[User:Jsmith | jsmith ]]
* [[User:jasonbrooks | jbrooks ]]


== Meetings ==
== Meetings ==


The Fedora Cloud Working Group has a weekly meeting. The meeting usually happens in #fedora-meeting-1 on irc.freenode.net and the schedule for the meeting can be found here: https://apps.fedoraproject.org/calendar/cloud/
The Fedora Cloud Working Group has a weekly meeting. The meeting usually happens in fedora-meeting-1@irc.libera.chat and the schedule for the meeting can be found here: https://calendar.fedoraproject.org/cloud/


You can find Meeting Minutes on the [https://meetbot.fedoraproject.org/ Fedora møte: meeting wrangler]. Meetings are currently held every Wednesday at 17:00 UTC.
You can find Meeting Minutes on the [https://meetbot.fedoraproject.org/ Fedora møte: meeting wrangler]. Meetings are currently held every other Thursday at 14:00 UTC.
 
=== Upcoming Meetings ===
 
Meetings are announced on the Cloud SIG mailing list. The Fedora Cloud SIG and Working Group meeting schedule is also found on the [https://calendar.fedoraproject.org/cloud/ Cloud Fedocal]. To subscribe to the calendar and receive changes automatically, you can import "From URL" in Google Calendar (and others) with this link: <code>https://calendar.fedoraproject.org//ical/cloud/</code>
 
=== Quorum Voting Policy ===
 
At minimum 51% of the voting members of the Atomic WG must be in attendance in order to make decisions on meeting items. The definition of voting members is that of those who have self identified themselves as participants of the Working Group by adding their name [[Cloud#Working_Group_Members_and_Points_of_Contact | here]]. A quorum vote is required to approve a decision on behalf of the working group, not simply the majority vote of those in attendance of any particular meeting.


=== Steps to run the meeting ===
=== Steps to run the meeting ===
Line 140: Line 136:


* #endmeeting
* #endmeeting
=== Upcoming Meetings, Agendas, and Chairs ===
Ideally we should have an agenda prior to each meeting that consists of any urgent business, action items from the last meeting (carry over if not completed!), and Trac tickets marked with the "meeting" tag. ([https://fedorahosted.org/cloud/report/9 See the Meeting report in Trac].)
We need someone to chair the meeting each week, and it's a good idea to come prepared to run the meeting rather than playing "who's the chair this week?" To that end, here's a list of upcoming meetings. Please call a spot if you're interested in chairing:
* 03 Aug 2016: NO MEETING - FLOCK CONFERENCE
* 10 Aug 2016: Chair - Scott Collier (scollier)
* 17 Aug 2016: Chair - Sayan Chowdhury (sayanchowdhury)
* 24 Aug 2016: Chair - Dusty Mabe (dustymabe)
* 31 Aug 2016: Chair - Trishna Guha (trishnag)
* 07 Sep 2016: Chair - Trishna Guha (trishnag)
* 14 Sep 2016: Chair - Sayan Chowdhury (sayanchowdhury)
* 21 Sep 2016: Chair - Sayan Chowdhury (sayanchowdhury)
* 28 Sep 2016: Chair - Trishna Guha (trishnag)
* 05 Oct 2016: Chair - Sayan Chowdhury (sayanchowdhury)
* 12 Oct 2016: Chair -
* 19 Oct 2016: Chair - Trishna Guha (trishnag)
* 26 Oct 2016: Chair - Randy Bizarlow (bowlofeggs)
* 02 Nov 2016: Chair -
* 09 Nov 2016: Chair -
* 16 Nov 2016: Chair - Trishna Guha (trishnag)
* 23 Nov 2016: Chair -
* 30 Nov 2016: Chair -
* 07 Dec 2016: Chair -
* 14 Dec 2016: Chair -
* 21 Dec 2016: Chair -
* 28 Dec 2016: Chair -
* 04 Jan 2017: Chair -
* 11 Jan 2017: Chair -
* 18 Jan 2017: Chair -
* 25 Jan 2017: Chair -
== Physical Meetings ==
[[Cloud SIG Meeting - Flock 2015 - 14 August 2015 - Rochester]]
[[Category:Cloud]]
[[Category:Cloud SIG]]

Latest revision as of 21:03, 1 November 2022

This is the home for the Fedora Cloud Working Group, where we are developing Fedora's next-generation cloud product. You may also be interested in the Cloud SIG, which has a broader, more loosely defined mission covering all things related to Fedora and cloud computing.


Fedora Cloud Working Group

Quick Links

Our Goals

The Fedora Cloud Edition allows users to work across multiple virtual environments at scale by focusing engineering efforts on supplying a base disk images, rpms, and container-based tooling of various architectures for working in and around public and private cloud environments. The Cloud Edition Working Group targets efforts towards the facilitation and improvement of continuous delivery by ensuring that Fedora project solutions support cloud native workflow without forcing users to understand all of the environments in which they require enablement.

Role in Fedora

The Fedora Cloud Working Group is a subset of the Fedora Cloud SIG, one of the many teams working on Fedora.

The Working Group is responsible for initial and ongoing development of the Product Requirements Document, and for coordinating production of the Fedora Cloud operating system.

We work with existing groups across the greater Fedora Project, and may delegate particular members to take responsibility for working with certain other teams. For example, a working group member may act as a coordinator for quality assurance or for release engineering.

Charter / Governance

Cloud/Governance

Product Requirements Document

Cloud PRD

Runbooks / Standard Operating Procedures

Let's keep track of how things work here so that we can help integrate new folks more easily.

Production Release Checklist

RFCs

This section lists the RFCs in progress or RFCs that have been accepted by the Cloud Working Group.

RFCs for Review

RFCs Recently Accepted

Guidelines for Changing Fedora Cloud Images

Communications

It is our policy to default to open; wherever possible, all communications will be held in the open and archived for future public reference. In some rare cases, it may necessary for some members of the group to enter into non-disclosure agreements (for example, when working with public cloud vendors) but such circumstances should be minimal and not impact core decisions of the group.

Our primary forum for discussion is the Cloud SIG mailing list, https://lists.fedoraproject.org/mailman/listinfo/cloud. Members also regularly are available in the #fedora-cloud IRC channel on libera.chat.

The Cloud SIG will work with other groups (Base WG, QA, Rel-eng, etc.) as needed to help deliver the final cloud products.

Mailing List

https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/

Real-time Communications

Matrix

#cloud:fedoraproject.org on Matrix.org

IRC

#fedora-cloud on Libera.Chat.

Working Group Members and Points of Contact

At a later date we will likely establish a formal on-boarding process for new community members but at this time if you're interested in joining, simply add your name below either in the "General" section or under a specific sub topic and then reach out via the irc channel and mailing list to introduce yourself.

General:

Testing:

Release Engineering:

Documentation/Marketing:

Meetings

The Fedora Cloud Working Group has a weekly meeting. The meeting usually happens in fedora-meeting-1@irc.libera.chat and the schedule for the meeting can be found here: https://calendar.fedoraproject.org/cloud/

You can find Meeting Minutes on the Fedora møte: meeting wrangler. Meetings are currently held every other Thursday at 14:00 UTC.

Upcoming Meetings

Meetings are announced on the Cloud SIG mailing list. The Fedora Cloud SIG and Working Group meeting schedule is also found on the Cloud Fedocal. To subscribe to the calendar and receive changes automatically, you can import "From URL" in Google Calendar (and others) with this link: https://calendar.fedoraproject.org//ical/cloud/

Quorum Voting Policy

At minimum 51% of the voting members of the Atomic WG must be in attendance in order to make decisions on meeting items. The definition of voting members is that of those who have self identified themselves as participants of the Working Group by adding their name here. A quorum vote is required to approve a decision on behalf of the working group, not simply the majority vote of those in attendance of any particular meeting.

Steps to run the meeting

  • #startmeeting fedora_atomic_wg
  • #topic Roll Call

Wait for 2 minutes for the roll call.

  • #chair all the people present for the meeting
  • #topic Action items from last meeting

^^ Find the last meeting log from https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg (cloud_wg_logs: https://meetbot-raw.fedoraproject.org/teams/fedora_cloud_wg)

Do the following for each ticket

  • #topic Ticket subject link_to_the_ticket

When all the tickets are over, go for Open floor

  • #topic Open Floor
  • #endmeeting
Retrieved from "https://fedoraproject.org/w/index.php?title=Cloud&oldid=659963"