Difference between revisions of "Meetings/Orchestration"
< Meetings
| Line 8: | Line 8: | ||
* Questions on Essex Orchestration presentation | * Questions on Essex Orchestration presentation | ||
** http://dl.dropbox.com/u/166877/OrchestrationEssex.pdf | ** http://dl.dropbox.com/u/166877/OrchestrationEssex.pdf | ||
| − | * | + | * A paper on transactional orchestration - http://dl.dropbox.com/u/166877/CloudTransaction.pdf |
| + | * Slides on a draft proposal for transactional orchestration in Nova - http://dl.dropbox.com/u/3314334/novaorch.pptx | ||
* First dev steps: | * First dev steps: | ||
** Getting success/failure notifications from rabbit back to scheduler | ** Getting success/failure notifications from rabbit back to scheduler | ||
Revision as of 04:13, 8 November 2011
Weekly Orchestration team meeting
If you're interested in Orchestration for OpenStack, we hold public meetings weekly in #openstack-meeting, on Tuesdays at 12:00 CST. Please feel free to add items to the agenda below and we'll cover them.
Agenda for next meeting
Scheduled for November 1st, 2011, 1700 UTC (noon CST)
- Questions on Essex Orchestration presentation
- A paper on transactional orchestration - http://dl.dropbox.com/u/166877/CloudTransaction.pdf
- Slides on a draft proposal for transactional orchestration in Nova - http://dl.dropbox.com/u/3314334/novaorch.pptx
- First dev steps:
- Getting success/failure notifications from rabbit back to scheduler
- use nova.notify.list_notifier.py to relay events to scheduler queue (new channel)
- pick up these notifications in scheduler.
- Getting success/failure notifications from rabbit back to scheduler
- Create a simple state machine for instance lifecycle
- Store the parameters passed in with the original request
Previous meetings
Previous meetings, with their notes and logs, can be found under Orchestration/MeetingLogs
