Petri/WeeklyMeeting/2012-1-4

Coordination Mechanics

• most discussion on mailing list and in irc #petri
• weekly meetings hopefully very short, primary goal to produce project update artefacts for broader consumption

Discussion Notes

Attendees: davida, gozer, strangecharm; mmayo sent minutes

Add to evaluation criteria: make PaaS easy to run on IaaS system.

Past Action Items

• mark: schedule calls with "vendors" to ask about roadmaps
• all: come up with list of "tasks" for developers and operators, in PaaS and IaaS:
  • PaaS tasks
  • IaaS tasks
• gozer to find out about our amazon accounts
• gozer to setup 3-node cloudfoundry-from-github
  • code availability good, even if docs not great. From an ops POV, not a bad experience so far.
  • security model lacking -- no ACLs; not sure what isolation/information leakage prevention in place.
  • no auto-scaling: capacity adjustment is operator-driven and somewhat involved, not very important for petri's.
• david to share his notes about cloudfoundry

Action Items

• gozer to email CF setup info
• gozer to publish notes and diff.
  • git diff
• gozer to push chef patch upstream and see what happens
  • pull request
• gozer to find out about motivation for current netops environment
• david to refactor etherpads
• david/gozer/others to explore CF/ldap integration
• carryover: mmayo to schedule meetings

Next meeting: Jan 11th