Re: [openstack-dev] [cinder] Let's do presentations/sessions on Mitaka's new complex features in Design Summit
I can do a presentation on microversions. Scott D'Angelo (scottda) -- Original Message -- >From : Gorka Eguileor Subject : [openstack-dev] [cinder] Let's do presentations/sessions on Mitaka's new complex features in Design Summit Hi, As you all probably know, during this cycle we have introduced quite a big number of changes in cinder that will have a great impact in the development of the new functionality as well as changes to existing ones moving forward from an implementation perspective. These changes to the cinder code include, but are not limited to, microversions, rolling upgrades, and conditional DB update functionality to remove API races, and while the latter has a good number of examples already merged and more patches under review, the other 2 have just been introduced and there are no patches in cinder that can serve as easy reference on how to use them. As cinder developers we will all have to take these changes into account in our new patches, but it is hard to do so when one doesn't have an in-depth knowledge of them, and while we all probably know quite a bit about them, it will take some time to get familiar enough to be aware of *all* the implications of the changes made by newer patches. And it's for this reason that I would like to suggest that during this summit's cinder design sessions we take the time to go through the changes giving not only an example of how they should be used in a patch, but also the do's, dont's and gotchas. A possible format for these explanations could be a presentation -around 30 minutes- by the people that were involved in the development, followed by Q&A. I would have expected to see some of these in the "Upstream Dev" track, but unfortunately I don't (maybe I'm just missing them with all the cool title names). And maybe these talks are not relevant for that track, being so specific and only relevant to cinder developers and all. I believe these presentations would help the cinder team increase the adoption speed of these features while reducing the learning curve and the number of bugs introduced in the code caused by gaps in our knowledge and misinterpretations of the new functionality. I would take lead on the conditional DB updates functionality, and I would have no problem doing the Rolling upgrades presentation as well. But I believe there are people more qualified and more deserving of doing that one; though I offer my help if they want it. I have added those 3 topics to the Etherpad with Newton Cinder Design Summit Ideas [1] so people can volunteer and express their ideas in there. Cheers, Gorka. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder] Let's do presentations/sessions on Mitaka's new complex features in Design Summit
On 16/03, D'Angelo, Scott wrote: > I can do a presentation on microversions. > "I love it when a plan comes together". This one had your name written all over it. ;-) > > > Scott D'Angelo (scottda) > > -- Original Message ------ > From : Gorka Eguileor > Subject : [openstack-dev] [cinder] Let's do presentations/sessions on > Mitaka's new complex features in Design Summit > > > Hi, > > As you all probably know, during this cycle we have introduced quite a > big number of changes in cinder that will have a great impact in the > development of the new functionality as well as changes to existing ones > moving forward from an implementation perspective. > > These changes to the cinder code include, but are not limited to, > microversions, rolling upgrades, and conditional DB update functionality > to remove API races, and while the latter has a good number of examples > already merged and more patches under review, the other 2 have just been > introduced and there are no patches in cinder that can serve as easy > reference on how to use them. > > As cinder developers we will all have to take these changes into account > in our new patches, but it is hard to do so when one doesn't have an > in-depth knowledge of them, and while we all probably know quite a bit > about them, it will take some time to get familiar enough to be aware of > *all* the implications of the changes made by newer patches. > > And it's for this reason that I would like to suggest that during this > summit's cinder design sessions we take the time to go through the > changes giving not only an example of how they should be used in a > patch, but also the do's, dont's and gotchas. > > A possible format for these explanations could be a presentation -around > 30 minutes- by the people that were involved in the development, > followed by Q&A. > > I would have expected to see some of these in the "Upstream Dev" track, > but unfortunately I don't (maybe I'm just missing them with all the cool > title names). And maybe these talks are not relevant for that track, > being so specific and only relevant to cinder developers and all. > > I believe these presentations would help the cinder team increase the > adoption speed of these features while reducing the learning curve and > the number of bugs introduced in the code caused by gaps in our > knowledge and misinterpretations of the new functionality. > > I would take lead on the conditional DB updates functionality, and I > would have no problem doing the Rolling upgrades presentation as well. > But I believe there are people more qualified and more deserving of > doing that one; though I offer my help if they want it. > > I have added those 3 topics to the Etherpad with Newton Cinder Design > Summit Ideas [1] so people can volunteer and express their ideas in > there. > > Cheers, > Gorka. > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder] Let's do presentations/sessions on Mitaka's new complex features in Design Summit
If people are interested I could do some small presentation on genconfig. All the Best, Kendall J. Nelson Software Engineer & OpenStack Contributor E-mail: kjnel...@us.ibm.com IBM Cell Phone: (952) 215- 4025 IRC Nickname: diablo_rojo 3605 Hwy 52 N Rochester, MN 55901-1407 United States From: Gorka Eguileor To: OpenStack Development Mailing List Date: 03/14/2016 03:57 PM Subject: [openstack-dev] [cinder] Let's do presentations/sessions on Mitaka's new complex features in Design Summit Hi, As you all probably know, during this cycle we have introduced quite a big number of changes in cinder that will have a great impact in the development of the new functionality as well as changes to existing ones moving forward from an implementation perspective. These changes to the cinder code include, but are not limited to, microversions, rolling upgrades, and conditional DB update functionality to remove API races, and while the latter has a good number of examples already merged and more patches under review, the other 2 have just been introduced and there are no patches in cinder that can serve as easy reference on how to use them. As cinder developers we will all have to take these changes into account in our new patches, but it is hard to do so when one doesn't have an in-depth knowledge of them, and while we all probably know quite a bit about them, it will take some time to get familiar enough to be aware of *all* the implications of the changes made by newer patches. And it's for this reason that I would like to suggest that during this summit's cinder design sessions we take the time to go through the changes giving not only an example of how they should be used in a patch, but also the do's, dont's and gotchas. A possible format for these explanations could be a presentation -around 30 minutes- by the people that were involved in the development, followed by Q&A. I would have expected to see some of these in the "Upstream Dev" track, but unfortunately I don't (maybe I'm just missing them with all the cool title names). And maybe these talks are not relevant for that track, being so specific and only relevant to cinder developers and all. I believe these presentations would help the cinder team increase the adoption speed of these features while reducing the learning curve and the number of bugs introduced in the code caused by gaps in our knowledge and misinterpretations of the new functionality. I would take lead on the conditional DB updates functionality, and I would have no problem doing the Rolling upgrades presentation as well. But I believe there are people more qualified and more deserving of doing that one; though I offer my help if they want it. I have added those 3 topics to the Etherpad with Newton Cinder Design Summit Ideas [1] so people can volunteer and express their ideas in there. Cheers, Gorka. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder] Let's do presentations/sessions on Mitaka's new complex features in Design Summit
On 15/03, Michał Dulko wrote: > On 03/14/2016 09:52 PM, Gorka Eguileor wrote: > > Hi, > > > > As you all probably know, during this cycle we have introduced quite a > > big number of changes in cinder that will have a great impact in the > > development of the new functionality as well as changes to existing ones > > moving forward from an implementation perspective. > > > > These changes to the cinder code include, but are not limited to, > > microversions, rolling upgrades, and conditional DB update functionality > > to remove API races, and while the latter has a good number of examples > > already merged and more patches under review, the other 2 have just been > > introduced and there are no patches in cinder that can serve as easy > > reference on how to use them. > > > > As cinder developers we will all have to take these changes into account > > in our new patches, but it is hard to do so when one doesn't have an > > in-depth knowledge of them, and while we all probably know quite a bit > > about them, it will take some time to get familiar enough to be aware of > > *all* the implications of the changes made by newer patches. > > > > And it's for this reason that I would like to suggest that during this > > summit's cinder design sessions we take the time to go through the > > changes giving not only an example of how they should be used in a > > patch, but also the do's, dont's and gotchas. > > > > A possible format for these explanations could be a presentation -around > > 30 minutes- by the people that were involved in the development, > > followed by Q&A. > > > > I would have expected to see some of these in the "Upstream Dev" track, > > but unfortunately I don't (maybe I'm just missing them with all the cool > > title names). And maybe these talks are not relevant for that track, > > being so specific and only relevant to cinder developers and all. > > > > I believe these presentations would help the cinder team increase the > > adoption speed of these features while reducing the learning curve and > > the number of bugs introduced in the code caused by gaps in our > > knowledge and misinterpretations of the new functionality. > > > > I would take lead on the conditional DB updates functionality, and I > > would have no problem doing the Rolling upgrades presentation as well. > > But I believe there are people more qualified and more deserving of > > doing that one; though I offer my help if they want it. > > > > I have added those 3 topics to the Etherpad with Newton Cinder Design > > Summit Ideas [1] so people can volunteer and express their ideas in > > there. > > > > Cheers, > > Gorka. > > I can certainly do one on rolling upgrades from developer's perspective. > I think I've got this knowledge summed up in patch to enhance the devref > [1], but of course presentation and Q&A would be beneficial. Jeje, I was actually thinking of you for that one, but didn't want to be pushy about it. ;-) > > And by the way - I think that for all the stuff that's worthy of such > presentation, we should have a detailed devref page. > > [1] https://review.openstack.org/#/c/279186/ You are totally right! I'll review that one and work on adding a new one for the conditional update stuff. Cheers, Gorka. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder] Let's do presentations/sessions on Mitaka's new complex features in Design Summit
On 03/14/2016 09:52 PM, Gorka Eguileor wrote: > Hi, > > As you all probably know, during this cycle we have introduced quite a > big number of changes in cinder that will have a great impact in the > development of the new functionality as well as changes to existing ones > moving forward from an implementation perspective. > > These changes to the cinder code include, but are not limited to, > microversions, rolling upgrades, and conditional DB update functionality > to remove API races, and while the latter has a good number of examples > already merged and more patches under review, the other 2 have just been > introduced and there are no patches in cinder that can serve as easy > reference on how to use them. > > As cinder developers we will all have to take these changes into account > in our new patches, but it is hard to do so when one doesn't have an > in-depth knowledge of them, and while we all probably know quite a bit > about them, it will take some time to get familiar enough to be aware of > *all* the implications of the changes made by newer patches. > > And it's for this reason that I would like to suggest that during this > summit's cinder design sessions we take the time to go through the > changes giving not only an example of how they should be used in a > patch, but also the do's, dont's and gotchas. > > A possible format for these explanations could be a presentation -around > 30 minutes- by the people that were involved in the development, > followed by Q&A. > > I would have expected to see some of these in the "Upstream Dev" track, > but unfortunately I don't (maybe I'm just missing them with all the cool > title names). And maybe these talks are not relevant for that track, > being so specific and only relevant to cinder developers and all. > > I believe these presentations would help the cinder team increase the > adoption speed of these features while reducing the learning curve and > the number of bugs introduced in the code caused by gaps in our > knowledge and misinterpretations of the new functionality. > > I would take lead on the conditional DB updates functionality, and I > would have no problem doing the Rolling upgrades presentation as well. > But I believe there are people more qualified and more deserving of > doing that one; though I offer my help if they want it. > > I have added those 3 topics to the Etherpad with Newton Cinder Design > Summit Ideas [1] so people can volunteer and express their ideas in > there. > > Cheers, > Gorka. I can certainly do one on rolling upgrades from developer's perspective. I think I've got this knowledge summed up in patch to enhance the devref [1], but of course presentation and Q&A would be beneficial. And by the way - I think that for all the stuff that's worthy of such presentation, we should have a detailed devref page. [1] https://review.openstack.org/#/c/279186/ __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder] Let's do presentations/sessions on Mitaka's new complex features in Design Summit
Great idea Gorka! I know I could benefit from this as a reviewer. Thanks for proposing it. Jay On Mon, Mar 14, 2016 at 3:52 PM Gorka Eguileor wrote: > Hi, > > As you all probably know, during this cycle we have introduced quite a > big number of changes in cinder that will have a great impact in the > development of the new functionality as well as changes to existing ones > moving forward from an implementation perspective. > > These changes to the cinder code include, but are not limited to, > microversions, rolling upgrades, and conditional DB update functionality > to remove API races, and while the latter has a good number of examples > already merged and more patches under review, the other 2 have just been > introduced and there are no patches in cinder that can serve as easy > reference on how to use them. > > As cinder developers we will all have to take these changes into account > in our new patches, but it is hard to do so when one doesn't have an > in-depth knowledge of them, and while we all probably know quite a bit > about them, it will take some time to get familiar enough to be aware of > *all* the implications of the changes made by newer patches. > > And it's for this reason that I would like to suggest that during this > summit's cinder design sessions we take the time to go through the > changes giving not only an example of how they should be used in a > patch, but also the do's, dont's and gotchas. > > A possible format for these explanations could be a presentation -around > 30 minutes- by the people that were involved in the development, > followed by Q&A. > > I would have expected to see some of these in the "Upstream Dev" track, > but unfortunately I don't (maybe I'm just missing them with all the cool > title names). And maybe these talks are not relevant for that track, > being so specific and only relevant to cinder developers and all. > > I believe these presentations would help the cinder team increase the > adoption speed of these features while reducing the learning curve and > the number of bugs introduced in the code caused by gaps in our > knowledge and misinterpretations of the new functionality. > > I would take lead on the conditional DB updates functionality, and I > would have no problem doing the Rolling upgrades presentation as well. > But I believe there are people more qualified and more deserving of > doing that one; though I offer my help if they want it. > > I have added those 3 topics to the Etherpad with Newton Cinder Design > Summit Ideas [1] so people can volunteer and express their ideas in > there. > > Cheers, > Gorka. > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [cinder] Let's do presentations/sessions on Mitaka's new complex features in Design Summit
Hi, As you all probably know, during this cycle we have introduced quite a big number of changes in cinder that will have a great impact in the development of the new functionality as well as changes to existing ones moving forward from an implementation perspective. These changes to the cinder code include, but are not limited to, microversions, rolling upgrades, and conditional DB update functionality to remove API races, and while the latter has a good number of examples already merged and more patches under review, the other 2 have just been introduced and there are no patches in cinder that can serve as easy reference on how to use them. As cinder developers we will all have to take these changes into account in our new patches, but it is hard to do so when one doesn't have an in-depth knowledge of them, and while we all probably know quite a bit about them, it will take some time to get familiar enough to be aware of *all* the implications of the changes made by newer patches. And it's for this reason that I would like to suggest that during this summit's cinder design sessions we take the time to go through the changes giving not only an example of how they should be used in a patch, but also the do's, dont's and gotchas. A possible format for these explanations could be a presentation -around 30 minutes- by the people that were involved in the development, followed by Q&A. I would have expected to see some of these in the "Upstream Dev" track, but unfortunately I don't (maybe I'm just missing them with all the cool title names). And maybe these talks are not relevant for that track, being so specific and only relevant to cinder developers and all. I believe these presentations would help the cinder team increase the adoption speed of these features while reducing the learning curve and the number of bugs introduced in the code caused by gaps in our knowledge and misinterpretations of the new functionality. I would take lead on the conditional DB updates functionality, and I would have no problem doing the Rolling upgrades presentation as well. But I believe there are people more qualified and more deserving of doing that one; though I offer my help if they want it. I have added those 3 topics to the Etherpad with Newton Cinder Design Summit Ideas [1] so people can volunteer and express their ideas in there. Cheers, Gorka. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev