Difference between revisions of "Meetings/NovaLiveMigration"
< Meetings
Tobias-urdin (talk | contribs) m (→Agenda for next meeting) |
(→Agenda for next meeting) |
||
Line 42: | Line 42: | ||
** auto-converge status | ** auto-converge status | ||
*** https://review.openstack.org/#/c/266001/ | *** https://review.openstack.org/#/c/266001/ | ||
+ | ** make live-migration api friendly | ||
+ | *** johnthetubaguy has concern while upgrade compute node, so he prefers to split this implement to two part, compute api layer merged in this release and REST API layer merged in next release to avoid bad request while live-migration request send to old compute node. Also he doe's like return information from compute api which make live-migration api synchronous | ||
* Bugs | * Bugs | ||
* Open Discussion | * Open Discussion |
Revision as of 14:02, 16 February 2016
Contents
Weekly Nova Live Migration Subteam Meeting
Meeting time: Tuesdays at 1400 UTC (#openstack-meeting-3)
Chair: Paul Murray (IRC: PaulMurray)
Agenda for next meeting
Add your IRC nick to this list to be pinged at the start of the meeting:
PaulMurray
paul-carlton2
eliqiao
shaohe_feng
pkoniszewski
jlanoux
yuntongjin
mdbooth
kashyap
kmartin
claudiub
tobasco
Can't make it but still wants to be part of the fun:
mikal
Here is the agenda for the next meeting (subject to change):
- Need someone to chair this meeting on 16th Feb
- Paul is on holiday week of 15th Feb
- Priority reviews
- Feature freeze is end of this month (29th Feb) - less than 3 weeks
- split-network-plane-for-live-migration merged
- pause-vm-during-live-migration only needs +W
- https://review.openstack.org/#/c/245921 - needs +W
- abort-live-migration - started to appear
- block-live-migrate-with-attached-volumes
- https://review.openstack.org/#/c/227278 - has +2 from danpb
- https://review.openstack.org/#/c/234659 - needs minor revision
- live-migration-progress-report
- auto-converge status
- make live-migration api friendly
- johnthetubaguy has concern while upgrade compute node, so he prefers to split this implement to two part, compute api layer merged in this release and REST API layer merged in next release to avoid bad request while live-migration request send to old compute node. Also he doe's like return information from compute api which make live-migration api synchronous
- Bugs
- Open Discussion
Tracking Pages
- Live migration etherpad
- Priority spec review tracking etherpad
- Priority code review tracking etherpad
- Untriaged live migration bugs
- All live migration bugs