MeetingMinutes: 2015 08 05

Home ▸ MeetingMinutes:

Discussion w/ Video: https://plus.google.com/events/cqfpicicbnra9mv6kvpj0mb24u4

Topics:

• State
• Security
• Runtime Config
  • https://github.com/opencontainers/specs/pull/88
• entering existing cgroup (julz)
• Testing (oct / ocp-testing)

Attendees:

• Mrunal Patel
• Michael Crosby
• Vincent Batts
• Julz Friedman
• Meaglith Ma
• Benjamin Mahler
• Alexander Morozov
• Jie Yu
• Jojy Varghese
• David Walter
• Vinod Kone
• 梁辰晔

Minutes:

• State (crosbymichael)
  • https://github.com/opencontainers/specs/pull/87
  • mostly looks good
  • Michael to cleanup of and re-push for review
• Security (mrunalp)
  • https://github.com/opencontainers/specs/pull/89
  • perhaps these sections ought not be in spec.go, but a subdirectory of examples
• entering existing cgroup (julz)
  • like https://github.com/opencontainers/specs/issues/68 ?
  • and the pid’s namespaces as well
• testing and validation
  • nothing yet, as we’re still thrashing through implementation
• topics like bundling
  • this is important, but contingent on features like splitting out mutable configs
  • having bundling of runtime, and a way to address the bundle
  • even testing will rely on this
• new namespaces
  • new namespaces are portable
  • but passing existing paths is not portable
  • Same for rootfs. it is host specific
  • It is a need to split out these non-portable configs
  • everyone need to go through brandon’s PR to flesh that out (https://github.com/opencontainers/specs/pull/88 )
• feedback loop
  • we should likely lean on the golang-dev cycle
  • issues and PRs are basically actionable
  • conversations and discussions should be on dev@opencontainers.org mailing-list (https://groups.google.com/a/opencontainers.org/forum/#!forum/dev ) first, then possibly topics in the discussions.
  • From there create an issue/PR
  • vbatts to take point on adding verbiage for this

Next Discussion:

We’ll likely circulate the link of the youtube broadcast and have an IRC channel (maybe #OCI-discussion) on freenode. This way we do not run the risk of hitting the join limit, can still field new topics, and folks can view as desired.