Difference between revisions of "Meetings/Nova"
(→Agenda for next meeting) |
(→Agenda for next meeting) |
||
| Line 68: | Line 68: | ||
*** Maybe create-encrypted-volume only in cinder (create from image, retype-to-encrypted volume) will work for enough use-cases. This is a key management thing (that barbican was supposed to provide semantics for, no idea if it currently does) not a where-the-code lives thing. Cinder does not want to copy and paste the code into cinder since that always causes issues with the code getting out of sync. Need a decision though, otherwise we'll have to copy-paste (or keep it in brick without nova moving over, which is effectively the same thing) | *** Maybe create-encrypted-volume only in cinder (create from image, retype-to-encrypted volume) will work for enough use-cases. This is a key management thing (that barbican was supposed to provide semantics for, no idea if it currently does) not a where-the-code lives thing. Cinder does not want to copy and paste the code into cinder since that always causes issues with the code getting out of sync. Need a decision though, otherwise we'll have to copy-paste (or keep it in brick without nova moving over, which is effectively the same thing) | ||
** In the 11/24 #openstack-performance team meeting it was noted that n-api-meta might be causing high CPU load in large ops testing (GoDaddy/Mirantis), mriedem to investigate a large ops job that runs the n-api-meta service; are there any issues with that? | ** In the 11/24 #openstack-performance team meeting it was noted that n-api-meta might be causing high CPU load in large ops testing (GoDaddy/Mirantis), mriedem to investigate a large ops job that runs the n-api-meta service; are there any issues with that? | ||
| + | ** https://bugs.launchpad.net/nova/+bug/1515768 - Instance creation fails with libvirtError: Unable to create tap device: Device or resource busy | ||
== Sub-teams == | == Sub-teams == | ||
Revision as of 08:45, 26 November 2015
Weekly Nova team meeting
MEETING TIME: Thursdays alternating 14:00 UTC (#openstack-meeting) and 21:00 UTC (#openstack-meeting)
This meeting is a weekly gathering of developers working on OpenStack Compute (Nova). We cover topics such as release planning and status, bugs, reviews, and other current topics worthy of real-time discussion.
NOTE: this wiki page should be 'emptied' at the end of each meeting.
Agenda for next meeting
Next meetings scheduled for:
- November 26th 2015 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151126T140000)
- December 3rd 2015 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151203T210000)
Add your IRC nick to this list to be pinged at the start of the meeting:
mikal tjones cburgess jgrimm adrian_otto funzo mjturek jcookekhugen
irina_pov krtaylor danpb alexpilotti flip214 jaypipes garyk edleafe dims
moshele anteaya Nisha sileht claudiub lxsli neiljerram markus_z swamireddy alevine
tonyb andreykurilin ndipanov sc68cal akuriata artom jlvillal mnestratov kashyap
aloga rgeragnov bauzas xyang tpatil med_ nic scottda nagyz belliott
dguitarbite sdague jroll diana_clarke _diana_ raildo jichen gjayavelu mdorman klindgren
sorrison belmoreira mrda mmmpork PaulMurray gcb thorst duncant
Please note "stuck review" means a review where there is some disagreement that needs resolving. Its not for reviews that just haven't had attention, except for exceptional cases. Where you see "?" feel free to just edit the wiki and add your item.
Here is the agenda for the next meeting:
- Release Status
- Virtual doc sprint December 8th and 9th
- Mitaka-1 is December 1st-3rd
- December 3rd is also non-priority spec and blueprints freeze
- https://wiki.openstack.org/wiki/Nova/Mitaka_Release_Schedule
- Specs:
- Review of specless blueprints:
- NOTE: we will not go through the full list in real time, its just to advertise the list and discuss any disagreement/appeal
- please review the list on here: https://etherpad.openstack.org/p/mitaka-nova-spec-review-tracking
- Call for backward incompatible changes for python-novaclient 3.0 (mitaka-2): http://lists.openstack.org/pipermail/openstack-dev/2015-November/079915.html
- Regular Reminders
- New review focus list: https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking
- Bugs (stuck/critical)
- Gate status
- 3rd party CI status
- Critical bugs
- ?
- Reminders:
- ?
- Stable branch status: https://etherpad.openstack.org/p/stable-tracker
- stable/kilo: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/kilo,n,z
- stable/juno: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/juno,n,z
- Juno is frozen for the 2014.2.4 release and then EOL after that.
- Stuck Reviews
- Please note "stuck review" means a review where there is some disagreement that needs resolving. Its not for reviews that just haven't had attention, except for exceptional cases. Where you see "?" feel free to just edit the wiki and add your item.
- Any stuck code reviews to discuss:
- Encryption support for rbd-backed volumes: https://review.openstack.org/#/c/239798/
- How reasonable is it to wait for distros to ship and support a version of QEMU that handles RBD encryption natively?
- ?
- Encryption support for rbd-backed volumes: https://review.openstack.org/#/c/239798/
- Open discussion
- Moving encryption/decryption code into brick
- https://review.openstack.org/#/c/247372/ and at least two mailing list discussions
- Some preference being expressed for keeping decryption only in nova, but this doesn't actually match the use cases
- Encrypted images need to be figured out and documented I think (DuncanT)
- Maybe create-encrypted-volume only in cinder (create from image, retype-to-encrypted volume) will work for enough use-cases. This is a key management thing (that barbican was supposed to provide semantics for, no idea if it currently does) not a where-the-code lives thing. Cinder does not want to copy and paste the code into cinder since that always causes issues with the code getting out of sync. Need a decision though, otherwise we'll have to copy-paste (or keep it in brick without nova moving over, which is effectively the same thing)
- In the 11/24 #openstack-performance team meeting it was noted that n-api-meta might be causing high CPU load in large ops testing (GoDaddy/Mirantis), mriedem to investigate a large ops job that runs the n-api-meta service; are there any issues with that?
- https://bugs.launchpad.net/nova/+bug/1515768 - Instance creation fails with libvirtError: Unable to create tap device: Device or resource busy
- Moving encryption/decryption code into brick
Sub-teams
There are also some Nova subteam meetings. See Nova#Active_Sub-teams: for details.
