Petri/WeeklyMeeting/2011-12-21: Difference between revisions
< Petri | WeeklyMeeting
| (4 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
* weekly meetings hopefully very short, primary goal to produce project update artefacts for broader consumption | * weekly meetings hopefully very short, primary goal to produce project update artefacts for broader consumption | ||
= | === Discussion Notes === | ||
* | * Agreement that we need to look at VM provisioning as well as PaaS. | ||
* | * Agreement to do short-term iterations, and avoid boiling the ocean (such as starting by designing dashboards) | ||
* Agreement that because we're dealing with a smallish number of users, we can defer things like account provisioning automation and start with manual processes. | |||
* | * Agreement that once one has an account, self-serve is critical -- no manual step needed to get up and going. | ||
* | * Agreement that current labs cluster setup is suboptimal (in particular, no dns automation, lack of network isolation between VMs) but fixable post-datacenter move. | ||
* | * Agreement on current evaluation criteria (see [/Petri main page] | ||
* | |||
=== Action Items === | |||
* schedule calls with "vendors" to ask about roadmaps | |||
* come up with list of "tasks" for developers and operators [ | * mark: schedule calls with "vendors" to ask about roadmaps | ||
* all: come up with list of "tasks" for developers and operators, in PaaS and IaaS: | |||
** [https://petri.etherpad.mozilla.org/1 PaaS tasks] | |||
** [https://petri.etherpad.mozilla.org/2 IaaS tasks] | |||
* gozer to find out about our amazon accounts | * gozer to find out about our amazon accounts | ||
* gozer to setup 3-node cloudfoundry-from-github | * gozer to setup 3-node cloudfoundry-from-github | ||
* david to share his notes about cloudfoundry | * david to share his notes about cloudfoundry | ||
Next meeting: [[Petri/WeeklyMeeting/2012-1-4 | Jan 4th]] | |||
Latest revision as of 18:36, 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
- Agreement that we need to look at VM provisioning as well as PaaS.
- Agreement to do short-term iterations, and avoid boiling the ocean (such as starting by designing dashboards)
- Agreement that because we're dealing with a smallish number of users, we can defer things like account provisioning automation and start with manual processes.
- Agreement that once one has an account, self-serve is critical -- no manual step needed to get up and going.
- Agreement that current labs cluster setup is suboptimal (in particular, no dns automation, lack of network isolation between VMs) but fixable post-datacenter move.
- Agreement on current evaluation criteria (see [/Petri main page]
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
- david to share his notes about cloudfoundry
Next meeting: Jan 4th