Difference between revisions of "Meetings/StateManagement"
< Meetings
(→Agenda for next meeting) |
(→When) |
||
| Line 11: | Line 11: | ||
== When == | == When == | ||
| − | If you're interested in State management in OpenStack, we hold public meetings weekly in <code><nowiki>#openstack-meeting</nowiki></code>, on Thursday at 20:00 UTC in freenode | + | If you're interested in State management in OpenStack, we hold public meetings weekly in <code><nowiki>#openstack-meeting</nowiki></code>, on Thursday at 20:00 UTC in freenode. |
== Agenda for next meeting == | == Agenda for next meeting == | ||
Revision as of 17:31, 6 June 2013
Contents
Weekly State Management Team Meeting
Mission
To provide nova, heat, reddwarf and other openstack projects (in incubation or core) a more structured state management library, routines, and code patterns to incrementally move toward a programming model which hopefully can be easier to ['audit', 'automate', 'extend', 'resume', 'revert', 'review', 'schedule', 'understand', '...'].
Coordinator
When
If you're interested in State management in OpenStack, we hold public meetings weekly in #openstack-meeting, on Thursday at 20:00 UTC in freenode.
Agenda for next meeting
- Discuss ongoing status of the overall effort and any needed coordination. - Go over new launchpad site (at https://launchpad.net/taskflow) - Discuss about how we can coordinate using blueprints/bugs on said site - Go over new stackforge site (at https://github.com/stackforge/taskflow) - Discuss how we can select core members and determine who may be interested to be in taskflow-core - Talk about progress with regards to cinder/nova integration - Talk about progress with regards to celery, ZK integration (locking API?) - Discuss about any other potential new use-cases for said library. - Discuss about any other ideas, problems, issues, solutions.
Previous meetings
Previous meetings, with their notes and logs, can be found under StateManagement/MeetingLogs
