Petri/WeeklyMeeting/2011-12-21

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

First draft of Q1 goals

• narrowing scope for 2012
  • proposal: IaaS & PaaS (node,python,mongo,couch,redis)
  • minimal (but non-zero) netops configuration
  • XXX
• defining evaluation criteria
• evaluating in first N weeks of Q, then
• deciding, modeling needs, & ordering hardware by EOQ.

Action Items:

• finding an "infrastructure thing to doodle with"
• schedule calls with "vendors" to ask about roadmaps
• come up with list of "tasks" for developers and operators [da + mmayo + gozer]
• gozer to find out about our amazon accounts
• gozer to setup 3-node cloudfoundry-from-github
• david to share his notes about cloudfoundry

Must haves:

• once account provisioned, service/vm is self-served (automated)

Not needed:

• account provisioning can be manual