From Fedora Project Wiki
(Flock 2018 workshop notes)
(Formatting)
 
Line 1: Line 1:
How do you get the new build to bodhi?
+
= Notes from Flock 2018 container workshop =
code done
+
* How do you get the new build to bodhi?
can push images to registry
+
** Code is done.
final release test
+
** Can push images to registry
 
+
** Needs to pass final testing.
Multiarch images coming soon
+
* Multiarch images are coming soon
intel, arm, power, s390
+
** intel, arm, power, s390
Betka
+
* Betka (sync upstream content to downstream)
fedmsg -- parse messages
+
** fedmsg -- parse messages
pagure webhooks
+
** pagure webhooks
Flatpak builds container images from module dist-git
+
* Flatpak builds container images from module dist-git.
Build container images automatically out of modules
+
* Build container images automatically out of modules.
pingou wrote koji-simple-ci tool to build RPMs as scratch builds in koji
+
* Pingou wrote koji-simple-ci tool to build RPMs as scratch builds in koji.
get inspired for container images
+
** Get inspired for the same thing for container images.
2 weeks rebuild: we should have an automation in-place to create bodhi updates
+
* 2 weeks rebuild: we should have an automation in-place to create bodhi updates.
a service which would create bodhi update once a container image build is done (via fedmsg)
+
** A service which would create bodhi update once a container image build is done (via fedmsg).
TODO: open source the bots finally!
+
* TODO: open source the bots finally!
create tasks in container SIG and get help from community
+
** Create tasks in container SIG and get help from community.
enable using candidate registry as a base image for builds
+
* Enable using candidate registry as a base image for builds.
SIG
+
* SIG
We need a leader who would organize the whole SIG -- connect people, coordinate, decide things
+
** We need a leader who would organize the whole SIG -- connect people, coordinate, decide things.
Focus
+
** Focus
Guidelines
+
*** Guidelines
Review existing guidelines (an easy way to submit and maintain container images)
+
**** Review existing guidelines (an easy way to submit and maintain container images)
https://github.com/projectatomic/ContainerApplicationGenericLabels figure out status
+
*** https://github.com/projectatomic/ContainerApplicationGenericLabels figure out status
https://github.com/container-images update template repo and status of the images
+
*** https://github.com/container-images update template repo and status of the images
Inftrastructure
+
*** Inftrastructure
Run on top of Fedora based one(using packages and images build on our infrstructure)
+
**** Run on top of Fedora based one (using packages and images build on our infrstructure).
Support the container packagers
+
**** tools, etc
tools, etc
+
*** Support the container users
Support the container users
+
**** image streams,...
image streams,...
+
*** Define the tasks well so anyone can pick them up.
Define the tasks well so anyone can pick them up
+
** issues
issues
+
*** not @packager, but @container-maintainer
not @packager, but @container-maintainer
+
*** time and place of the IRC meeting
time and place of the IRC meeting
+
**** #fedora-containers
#fedora-containers
+
*** write down best practices for container SIG: where do we discuss what?
write down best practices: where do we discuss what?
+
**** Fedora CoreOS: discourse - users, pagure - design discussions
CoreOS: discourse - users, pagure - design discussions
+
*** Fedora taiga?
Fedora taiga?
+
*** Issue tracking for container images
Issue tracking for container images
+
**** Dusty suggests pagure dist-git issue tracker
Dusty suggests pagure dist-git issue tracker
+
**** Clement uses WG issue tracker
Clement uses WG issue tracker
+
* F30 is the time when atomic thing will start going away
F30 is the time when atomic thing will start going away
+
* CentOS has a container something SIG (CCCP) -- do we join forces?
CentOS has a container something SIG (CCCP) -- do we join forces?
+
** Invite them for our SIG meeting
Invite them for our SIG meeting
+
* Validation.
Validation.
+
** How can I use taskotron to validate my image?
How can I use taskotron to validate my image?
+
** Dockerfile linting
Dockerfile linting
+
** Does it run in OpenShift? (Do we care about this?)
Does it run in OpenShift? (Do we care about this?)
+
* Automation (least amount of steps for container maintainers).
Automation (least amount of steps for container maintainers).
+
* We could get people to submit PRs to update the Dockerfiles in distgit since I think there are a few that are a bit out of date.
Delivery (can I have the container on my system ASAP?).
+
* Automatic versioning based on a "main rpm" version (maybe we work on that during hacking time)
Do we wanna start hacking on things we just discussed?
 
We could get people to submit PRs to update the Dockerfiles in distgit since I think there are a few that are a bit out of date.
 
open issues here --> https://pagure.io/ContainerSIG/container-sig/issues 
 
Automatic versioning based on a "main rpm" version (maybe we work on that during hacking time)
 
Moving issues from atomic-wg to container SIG.
 
https://pagure.io/atomic-wg/issues?status=Open&tags=containers
 
 
 
Adding people to the containerSIG group on pagure.io
 
 
 
Parking lot (potential topics for discussion):
 

Latest revision as of 14:24, 10 August 2018

Notes from Flock 2018 container workshop

  • How do you get the new build to bodhi?
    • Code is done.
    • Can push images to registry
    • Needs to pass final testing.
  • Multiarch images are coming soon
    • intel, arm, power, s390
  • Betka (sync upstream content to downstream)
    • fedmsg -- parse messages
    • pagure webhooks
  • Flatpak builds container images from module dist-git.
  • Build container images automatically out of modules.
  • Pingou wrote koji-simple-ci tool to build RPMs as scratch builds in koji.
    • Get inspired for the same thing for container images.
  • 2 weeks rebuild: we should have an automation in-place to create bodhi updates.
    • A service which would create bodhi update once a container image build is done (via fedmsg).
  • TODO: open source the bots finally!
    • Create tasks in container SIG and get help from community.
  • Enable using candidate registry as a base image for builds.
  • SIG
    • We need a leader who would organize the whole SIG -- connect people, coordinate, decide things.
    • Focus
    • issues
      • not @packager, but @container-maintainer
      • time and place of the IRC meeting
        • #fedora-containers
      • write down best practices for container SIG: where do we discuss what?
        • Fedora CoreOS: discourse - users, pagure - design discussions
      • Fedora taiga?
      • Issue tracking for container images
        • Dusty suggests pagure dist-git issue tracker
        • Clement uses WG issue tracker
  • F30 is the time when atomic thing will start going away
  • CentOS has a container something SIG (CCCP) -- do we join forces?
    • Invite them for our SIG meeting
  • Validation.
    • How can I use taskotron to validate my image?
    • Dockerfile linting
    • Does it run in OpenShift? (Do we care about this?)
  • Automation (least amount of steps for container maintainers).
  • We could get people to submit PRs to update the Dockerfiles in distgit since I think there are a few that are a bit out of date.
  • Automatic versioning based on a "main rpm" version (maybe we work on that during hacking time)