From Fedora Project Wiki

Line 3: Line 3:
== Purpose ==
== Purpose ==
Our purpose is to complete the following '''primary''' goals:
Our purpose is to complete the following '''primary''' goals:
# Continue and/or complete key CI pipeline implementation
# Expand skills/knowledge of authorization/authentication systems in Fedora -- ''(max 1 day)''
#* ''This goal will be further outlined based on discussions between now and the event.''
# Expand skills/knowledge of authorization/authentication systems in Fedora
#* All core sysadmin team members will understand FreeIPA/Ipsilon backend administration tasks and ensure they are documented in [http://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/index.html the Fedora Infra Sysadmin Guide]
#* All core sysadmin team members will understand FreeIPA/Ipsilon backend administration tasks and ensure they are documented in [http://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/index.html the Fedora Infra Sysadmin Guide]
#* Key developers will understand changes needed in current apps and best practices for new ones, if applicable, and capture them in [http://fedora-infra-docs.readthedocs.io/en/latest/dev-guide/index.html the Fedora Infra Developer Guide]
#* Key developers will understand changes needed in current apps and best practices for new ones, if applicable, and capture them in [http://fedora-infra-docs.readthedocs.io/en/latest/dev-guide/index.html the Fedora Infra Developer Guide]
# Establish an OpenShift instance in Fedora infrastructure
# Continue and/or complete key CI pipeline implementation -- ''(est. 2 days)''
#* ''This goal will be further outlined based on discussions between now and the event.''
# Establish an OpenShift instance in Fedora infrastructure -- ''(est. 2 days)''
#* Determine the extent to which OpenShift can be expanded beyond [https://copr.fedorainfracloud.org/coprs/maxamillion/atomic-reactor/ OSBS]
#* Determine the extent to which OpenShift can be expanded beyond [https://copr.fedorainfracloud.org/coprs/maxamillion/atomic-reactor/ OSBS]
#* Determine policy and workflows and what might fit in and what will stay out  
#* Determine policy and workflows and what might fit in and what will stay out  

Revision as of 15:27, 3 April 2017

This is the main page for a CI and Infrastructure hackathon 2017. This hackathon is intended to help the team leap ahead for several critical Fedora initiatives.

Purpose

Our purpose is to complete the following primary goals:

  1. Expand skills/knowledge of authorization/authentication systems in Fedora -- (max 1 day)
    • All core sysadmin team members will understand FreeIPA/Ipsilon backend administration tasks and ensure they are documented in the Fedora Infra Sysadmin Guide
    • Key developers will understand changes needed in current apps and best practices for new ones, if applicable, and capture them in the Fedora Infra Developer Guide
  2. Continue and/or complete key CI pipeline implementation -- (est. 2 days)
    • This goal will be further outlined based on discussions between now and the event.
  3. Establish an OpenShift instance in Fedora infrastructure -- (est. 2 days)
    • Determine the extent to which OpenShift can be expanded beyond OSBS
    • Determine policy and workflows and what might fit in and what will stay out
      • Application development
      • Application deployment
      • Upstream collaboration with Factory 2.0
    • Develop necessary playbooks, etc. to deploy

Detailed Work Items & Final Attendees

Priorities

Priorities: ((AuthN/AuthZ)) Task Owner Done
Priorities: ((CI Pipeline)) Task Owner Done
Priorities: ((OpenShift)) Task Owner Done

Deliverables

AuthN/AuthZ Task Owner Done
More to come...

Attendees and Travel Details

Contributor Arrival Departure Roommate Notes
Patrick Uiterwijk
Kevin Fenzi
Pierre-Yves Chibon
Adam Miller
Randy Barlow -∞
Jeremy Cline -∞
Stephen Smoogen -∞
Kushal Das
Brian Stinson
Tim Flink?
Ricky Elrod
Paul Frields (unsure of stay length)
Remote attendees
Aurélien Bompard

Planning Prerequisites

See the How to organize a FAD list; you can keep your to-do list here.

  • Work out budget
  • Decide on Dates and Location
  • Arrange Facilities
  • List Resources
  • Be Somewhat Structured
  • Arrange Lodging
  • Arrange Refreshments
  • Arrange a Social Event -- N/A

Plan

  1. Location: Red Hat, Raleigh NC, USA
    • Red Hat Tower, 9th Floor South, "Fedora" room
  2. Date: 2017-May-08 to 2017-May-12
    • Visitors should arrive on Sunday May 7th if possible
  3. Remote Attendees: (include dial-in)
  4. Schedule
    • Event starts 9:30am daily
    • Event ends by noon Friday May 12th, to allow for travel outbound
    • ...

Logistics

Snacks/Beverages: Can be snarfed from Raleigh office

Breakfast:

  • Covered at hotel

Lunch:

  • ...

Dinner:

  • ...

Total food: est. $

Travel estimates

Contributor Taxi/transport (to/from home) Airfare Taxi/transport (to/from site) Parking Other
pingou ~USD200 (home <-> Paris) KLM: ~USD1300
Adam Miller N/A American: ~$450 ~$50 $105
Jeremy Cline $0 $0 $0 $0
Kevin Fenzi $40 Southwest: ~420
Patrick Uiterwijk $0 KLM: ~1400USD
Tim Flink $30 United: ~$400 $50 50
Ricky Elrod $20 American ~$300 ~$60
  1. Travel: $$
  2. Housing: - $3200 (est)
    • Courtyard Raleigh Midtown -- 1041 Wake Town Dr, Raleigh, NC 27609 -- Red Hat rate $139 + taxes
    • Possibility of 1-2 people being housed locally?
  3. Space:
    • $0 -- Supplied by Red Hat
  4. Supplies:
    • N/A
  5. Food: $$

Total budget: $$