From Fedora Project Wiki
Maxamillion (talk | contribs) |
|||
| Line 38: | Line 38: | ||
#* Proposal to Council with the above | #* Proposal to Council with the above | ||
# Docker | # Docker | ||
#* | #* As of version 1.10, it has become necessary for us to support multiple versions of Docker in our repo, as new versions are not backwards-compatible. This requires deciding: | ||
#* Docker | #** Which versions will we offer? | ||
#** What will the packaging look like? Will we follow RHEL's lead with Docker-1.9 and Docker-Next? | |||
#** Does this affect packaging/versions for runc? | |||
#* Deliverables: plan for packaging and supporting different versions of Docker in Fedora. | |||
# Registry | # Registry | ||
#* Public Atomic Registry for Fedora? | #* Public Atomic Registry for Fedora: It is now possible for us to have a dedicated Fedora container registry. We need to figure out: | ||
#** Feasibily of doing so | |||
#** Build pipeline for images | |||
#** Hosting: OK to have CentOS host this? | |||
#** Requirements for accounts, official images only or open to all project members? | |||
#* Deliverables: either decision not to run a registry, or a workable plan for maintaining and governing one. | |||
# Documentation | # Documentation | ||
#* At least one F24-focused runbook. | #* At least one F24-focused runbook. | ||
Revision as of 17:57, 25 April 2016
This is the main page for FAD Fedora Cloud Working Group 2016.
Purpose
Our purpose is to complete the following primary goals:
- Retrospective of Fedora 23 release for the Cloud/Atomic products.
- Future of Automated Testing for Fedora Cloud/Atomic
- Concrete Plan for Fedora Atomic Edition for F25.
- Increase the Public Cloud Provider reach.
- OpenShift Origin, and how to integrate in our cloud story (may be for contributors)
- CentOS and Fedora Atomic hosts
Diversity Statement
We are aware that the State of North Carolina has passed recent laws which are not consistent with the Fedora Project's views on equality and diversity, and may make some attendees of the FAD uncomfortable. Both Red Hat and the Fedora Project are committed to providing a discrimination-free experience for attendees. Red Hat, the host of this FAD, will provide facilities appropriately regardless of gender, sexuality, religion or race.
Regardless, if North Carolina's laws make you feel uncomfortable or unable to attend the FAD for any reason, or require changes to your travel arrangements, please contact either Josh Berkus or the Fedora Project diversity advisor, Maria Leandro with your concerns. All such contacts will be confidential.
Detailed Work Items & Final Attendees
Priorities
Deliverables
- Automated testing
- Atomic Host Tests
- Plan for CI builds/testing for Host/OStree
- Atomic Edition
- F25 Change
- Updated PRD
- Proposal to Council with the above
- Docker
- As of version 1.10, it has become necessary for us to support multiple versions of Docker in our repo, as new versions are not backwards-compatible. This requires deciding:
- Which versions will we offer?
- What will the packaging look like? Will we follow RHEL's lead with Docker-1.9 and Docker-Next?
- Does this affect packaging/versions for runc?
- Deliverables: plan for packaging and supporting different versions of Docker in Fedora.
- As of version 1.10, it has become necessary for us to support multiple versions of Docker in our repo, as new versions are not backwards-compatible. This requires deciding:
- Registry
- Public Atomic Registry for Fedora: It is now possible for us to have a dedicated Fedora container registry. We need to figure out:
- Feasibily of doing so
- Build pipeline for images
- Hosting: OK to have CentOS host this?
- Requirements for accounts, official images only or open to all project members?
- Deliverables: either decision not to run a registry, or a workable plan for maintaining and governing one.
- Public Atomic Registry for Fedora: It is now possible for us to have a dedicated Fedora container registry. We need to figure out:
- Documentation
- At least one F24-focused runbook.
- Event report for Community Blog
- Need to produce one or more reports for the larger group / project to follow along with results of the FAD
Attendees and Travel Details
| Contributor | Arrival | Departure | Roommate | Need Travel Funding? | Budget amount for travel |
|---|---|---|---|---|---|
| Josh Berkus | Jun 6 | Jun 9 | - | No | |
| Matthew Miller | Not sure yet | Also not sure yet | - | No | |
| Scott Collier | Not sure yet | Also not sure yet | - | No | |
| Dusty Mabe | Jun 6 | Jun 8 (late) | - | No | |
| Joe Brockmeier | Lives Here | Lives Here | Heck No | No | |
| Adam Miller | Jun 6 | Jun 9 | Kushal Das | Yes | $1000 ($450 Hotel, $400 Flight, $50 To/From Airport, $100 Food) |
| Kushal Das | June 5th | June 10th | - | Yes | $1050 ($450 Hotel, $450 Flight, $50 To/From Airport) (I hope food will be taken care by in total). |
| Tim Flink ? | not sure yet, may end up remote | not sure yet | - | Yes | |
| Jason Brooks | Jun 6 | Jun 9 | - | No |
| Remote attendees |
|---|
Plan
- Location: Red Hat, Raleigh, NC USA
- Room Red Hat Annex, "Red Rover" room
- Date: Jun-07 to Jun-08
Logistics
Snacks/Beverages:
Breakfast:
- Covered at hotel
Lunch:
- Days other than Tue/Wed/ to be covered by attendees.
- Tue: Order in, cost covered (est. $125)
- Wed: Order in, cost covered (est. $125)
Dinner:
- Days other than Tue/Wed to be covered by attendees
- Tue: Team @ local venue (est. $300)
- Wed: Team @ local venue (est. $300)
Total food: est. $850
Travel estimates
| Contributor | Taxi/transport (to/from home) | Airfare | Hotel | Taxi/transport (to/from site) | Parking | Add Meals | Other |
|---|---|---|---|---|---|---|---|
| tflink | USD 50 | USD 320 | USD 450 | USD 40 | USD 50 | USD 40 | |
| Adam | $50 | $400 | $450 | $40 | $100 |
- Space:
- $0 if Supplied by Red Hat
- Supplies:
- N/A
- Food: $850 (from above)
Total budget: $