Petri/WeeklyMeeting/2012-1-4: Difference between revisions
< Petri | WeeklyMeeting
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
Attendees: davida, gozer, strangecharm; mmayo sent minutes | Attendees: davida, gozer, strangecharm; mmayo sent minutes | ||
Add to evaluation criteria: make PaaS easy to run on IaaS system. | |||
=== Action Items === | === Action Items === | ||
Revision as of 18:50, 4 January 2012
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.
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:
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.
- gozer to email CF setup info
- gozer to publish notes and diff.
david to share his notes about cloudfoundry
Next meeting: Jan 11th