Re: [openstack-dev] [oslo] kilo graduation plans
On 11/18/2014 05:11 PM, Sachi King wrote: > On Wednesday, November 12, 2014 02:06:02 PM Doug Hellmann wrote: >> During our “Graduation Schedule” summit session we worked through the list >> of modules remaining the in the incubator. Our notes are in the etherpad >> [1], but as part of the "Write it Down” theme for Oslo this cycle I am also >> posting a summary of the outcome here on the mailing list for wider >> distribution. Let me know if you remembered the outcome for any of these >> modules differently than what I have written below. >> >> Doug >> >> >> >> Deleted or deprecated modules: >> >> funcutils.py - This was present only for python 2.6 support, but it is no >> longer used in the applications. We are keeping it in the stable/juno branch >> of the incubator, and removing it from master >> (https://review.openstack.org/130092) >> >> hooks.py - This is not being used anywhere, so we are removing it. >> (https://review.openstack.org/#/c/125781/) >> >> quota.py - A new quota management system is being created >> (https://etherpad.openstack.org/p/kilo-oslo-common-quota-library) and should >> replace this, so we will keep it in the incubator for now but deprecate it. >> >> crypto/utils.py - We agreed to mark this as deprecated and encourage the use >> of Barbican or cryptography.py (https://review.openstack.org/134020) >> >> cache/ - Morgan is going to be working on a new oslo.cache library as a >> front-end for dogpile, so this is also deprecated >> (https://review.openstack.org/134021) >> >> apiclient/ - With the SDK project picking up steam, we felt it was safe to >> deprecate this code as well (https://review.openstack.org/134024). >> >> xmlutils.py - This module was used to provide a security fix for some XML >> modules that have since been updated directly. It was removed. >> (https://review.openstack.org/#/c/125021/) >> >> >> >> Graduating: >> >> oslo.context: >> - Dims is driving this >> - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-context >> - includes: >> context.py >> >> oslo.service: > > During the "Oslo graduation schedule" meet up someone was mentioning they'd > be willing to help out as a contact for questions during this process. > Can anyone put me in contact with that person or remember who he was? I think that was me, but I've been kind of out of touch since the summit. Feel free to contact me with any questions though. bnemec on #openstack-oslo. > >> - Sachi is driving this >> - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-service >> - includes: >> eventlet_backdoor.py >> loopingcall.py >> periodic_task.py >> request_utils.py >> service.py >> sslutils.py >> systemd.py >> threadgroup.py >> >> oslo.utils: >> - We need to look into how to preserve the git history as we import these >> modules. >> - includes: >> fileutils.py >> versionutils.py >> >> >> >> Remaining untouched: >> >> scheduler/ - Gantt probably makes this code obsolete, but it isn’t clear >> whether Gantt has enough traction yet so we will hold onto these in the >> incubator for at least another cycle. >> >> report/ - There’s interest in creating an oslo.reports library containing >> this code, but we haven’t had time to coordinate with Solly about doing that. >> >> >> >> Other work: >> >> We will continue the work on oslo.concurrency and oslo.log that we started >> during Juno. >> >> [1] https://etherpad.openstack.org/p/kilo-oslo-library-proposals >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo] kilo graduation plans
On Nov 18, 2014, at 6:11 PM, Sachi King wrote: > On Wednesday, November 12, 2014 02:06:02 PM Doug Hellmann wrote: >> During our “Graduation Schedule” summit session we worked through the list >> of modules remaining the in the incubator. Our notes are in the etherpad >> [1], but as part of the "Write it Down” theme for Oslo this cycle I am also >> posting a summary of the outcome here on the mailing list for wider >> distribution. Let me know if you remembered the outcome for any of these >> modules differently than what I have written below. >> >> Doug >> >> >> >> Deleted or deprecated modules: >> >> funcutils.py - This was present only for python 2.6 support, but it is no >> longer used in the applications. We are keeping it in the stable/juno branch >> of the incubator, and removing it from master >> (https://review.openstack.org/130092) >> >> hooks.py - This is not being used anywhere, so we are removing it. >> (https://review.openstack.org/#/c/125781/) >> >> quota.py - A new quota management system is being created >> (https://etherpad.openstack.org/p/kilo-oslo-common-quota-library) and should >> replace this, so we will keep it in the incubator for now but deprecate it. >> >> crypto/utils.py - We agreed to mark this as deprecated and encourage the use >> of Barbican or cryptography.py (https://review.openstack.org/134020) >> >> cache/ - Morgan is going to be working on a new oslo.cache library as a >> front-end for dogpile, so this is also deprecated >> (https://review.openstack.org/134021) >> >> apiclient/ - With the SDK project picking up steam, we felt it was safe to >> deprecate this code as well (https://review.openstack.org/134024). >> >> xmlutils.py - This module was used to provide a security fix for some XML >> modules that have since been updated directly. It was removed. >> (https://review.openstack.org/#/c/125021/) >> >> >> >> Graduating: >> >> oslo.context: >> - Dims is driving this >> - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-context >> - includes: >> context.py >> >> oslo.service: > > During the "Oslo graduation schedule" meet up someone was mentioning they'd > be willing to help out as a contact for questions during this process. > Can anyone put me in contact with that person or remember who he was? I don’t know if it was me, but I’ll volunteer now. :-) dhellmann on freenode, or this email address, are the best way to reach me. I’m in the US Eastern time zone. Doug > >> - Sachi is driving this >> - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-service >> - includes: >> eventlet_backdoor.py >> loopingcall.py >> periodic_task.py >> request_utils.py >> service.py >> sslutils.py >> systemd.py >> threadgroup.py >> >> oslo.utils: >> - We need to look into how to preserve the git history as we import these >> modules. >> - includes: >> fileutils.py >> versionutils.py >> >> >> >> Remaining untouched: >> >> scheduler/ - Gantt probably makes this code obsolete, but it isn’t clear >> whether Gantt has enough traction yet so we will hold onto these in the >> incubator for at least another cycle. >> >> report/ - There’s interest in creating an oslo.reports library containing >> this code, but we haven’t had time to coordinate with Solly about doing that. >> >> >> >> Other work: >> >> We will continue the work on oslo.concurrency and oslo.log that we started >> during Juno. >> >> [1] https://etherpad.openstack.org/p/kilo-oslo-library-proposals >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo] kilo graduation plans
On Wednesday, November 12, 2014 02:06:02 PM Doug Hellmann wrote: > During our “Graduation Schedule” summit session we worked through the list of > modules remaining the in the incubator. Our notes are in the etherpad [1], > but as part of the "Write it Down” theme for Oslo this cycle I am also > posting a summary of the outcome here on the mailing list for wider > distribution. Let me know if you remembered the outcome for any of these > modules differently than what I have written below. > > Doug > > > > Deleted or deprecated modules: > > funcutils.py - This was present only for python 2.6 support, but it is no > longer used in the applications. We are keeping it in the stable/juno branch > of the incubator, and removing it from master > (https://review.openstack.org/130092) > > hooks.py - This is not being used anywhere, so we are removing it. > (https://review.openstack.org/#/c/125781/) > > quota.py - A new quota management system is being created > (https://etherpad.openstack.org/p/kilo-oslo-common-quota-library) and should > replace this, so we will keep it in the incubator for now but deprecate it. > > crypto/utils.py - We agreed to mark this as deprecated and encourage the use > of Barbican or cryptography.py (https://review.openstack.org/134020) > > cache/ - Morgan is going to be working on a new oslo.cache library as a > front-end for dogpile, so this is also deprecated > (https://review.openstack.org/134021) > > apiclient/ - With the SDK project picking up steam, we felt it was safe to > deprecate this code as well (https://review.openstack.org/134024). > > xmlutils.py - This module was used to provide a security fix for some XML > modules that have since been updated directly. It was removed. > (https://review.openstack.org/#/c/125021/) > > > > Graduating: > > oslo.context: > - Dims is driving this > - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-context > - includes: > context.py > > oslo.service: During the "Oslo graduation schedule" meet up someone was mentioning they'd be willing to help out as a contact for questions during this process. Can anyone put me in contact with that person or remember who he was? > - Sachi is driving this > - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-service > - includes: > eventlet_backdoor.py > loopingcall.py > periodic_task.py > request_utils.py > service.py > sslutils.py > systemd.py > threadgroup.py > > oslo.utils: > - We need to look into how to preserve the git history as we import these > modules. > - includes: > fileutils.py > versionutils.py > > > > Remaining untouched: > > scheduler/ - Gantt probably makes this code obsolete, but it isn’t clear > whether Gantt has enough traction yet so we will hold onto these in the > incubator for at least another cycle. > > report/ - There’s interest in creating an oslo.reports library containing > this code, but we haven’t had time to coordinate with Solly about doing that. > > > > Other work: > > We will continue the work on oslo.concurrency and oslo.log that we started > during Juno. > > [1] https://etherpad.openstack.org/p/kilo-oslo-library-proposals > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo] kilo graduation plans
Thanks Steve. On Thu, Nov 13, 2014 at 12:50 PM, Steve Martinelli wrote: > looking at http://specs.openstack.org/openstack/oslo-specs/ and > http://specs.openstack.org/openstack/keystone-specs/ should have all the > info you need. The specs are hosted at: > https://github.com/openstack/keystone-specs there's a template spec too. > > Thanks, > > _ > Steve Martinelli > OpenStack Development - Keystone Core Member > Phone: (905) 413-2851 > E-Mail: steve...@ca.ibm.com > > > > From:Rodrigo Duarte > To:"OpenStack Development Mailing List (not for usage questions)" > > Date: 11/13/2014 10:13 AM > Subject:Re: [openstack-dev] [oslo] kilo graduation plans > -- > > > > Hi Doug, > > I'm going to write the spec regarding the policy graduation, it will be > placed in the keystone-specs repository. I was wondering if someone have > examples of such specs so we can cover all necessary points. > > On Thu, Nov 13, 2014 at 10:34 AM, Doug Hellmann <*d...@doughellmann.com* > > wrote: > > On Nov 13, 2014, at 8:31 AM, Dmitry Tantsur <*dtant...@redhat.com* > > wrote: > > > On 11/13/2014 01:54 PM, Doug Hellmann wrote: > >> > >> On Nov 13, 2014, at 3:52 AM, Dmitry Tantsur <*dtant...@redhat.com* > > wrote: > >> > >>> On 11/12/2014 08:06 PM, Doug Hellmann wrote: > >>>> During our “Graduation Schedule” summit session we worked through the > list of modules remaining the in the incubator. Our notes are in the > etherpad [1], but as part of the "Write it Down” theme for Oslo this cycle > I am also posting a summary of the outcome here on the mailing list for > wider distribution. Let me know if you remembered the outcome for any of > these modules differently than what I have written below. > >>>> > >>>> Doug > >>>> > >>>> > >>>> > >>>> Deleted or deprecated modules: > >>>> > >>>> funcutils.py - This was present only for python 2.6 support, but it > is no longer used in the applications. We are keeping it in the stable/juno > branch of the incubator, and removing it from master ( > *https://review.openstack.org/130092* > <https://review.openstack.org/130092>) > >>>> > >>>> hooks.py - This is not being used anywhere, so we are removing it. ( > *https://review.openstack.org/#/c/125781/* > <https://review.openstack.org/#/c/125781/>) > >>>> > >>>> quota.py - A new quota management system is being created ( > *https://etherpad.openstack.org/p/kilo-oslo-common-quota-library* > <https://etherpad.openstack.org/p/kilo-oslo-common-quota-library>) and > should replace this, so we will keep it in the incubator for now but > deprecate it. > >>>> > >>>> crypto/utils.py - We agreed to mark this as deprecated and encourage > the use of Barbican or cryptography.py ( > *https://review.openstack.org/134020* > <https://review.openstack.org/134020>) > >>>> > >>>> cache/ - Morgan is going to be working on a new oslo.cache library as > a front-end for dogpile, so this is also deprecated ( > *https://review.openstack.org/134021* > <https://review.openstack.org/134021>) > >>>> > >>>> apiclient/ - With the SDK project picking up steam, we felt it was > safe to deprecate this code as well (*https://review.openstack.org/134024* > <https://review.openstack.org/134024>). > >>>> > >>>> xmlutils.py - This module was used to provide a security fix for some > XML modules that have since been updated directly. It was removed. ( > *https://review.openstack.org/#/c/125021/* > <https://review.openstack.org/#/c/125021/>) > >>>> > >>>> > >>>> > >>>> Graduating: > >>>> > >>>> oslo.context: > >>>> - Dims is driving this > >>>> - > *https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-context* > <https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-context> > >>>> - includes: > >>>>context.py > >>>> > >>>> oslo.service: > >>>> - Sachi is driving this > >>>> - > *https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-service* > <https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-service> > >>>> - includes: > >>>>eventlet_
Re: [openstack-dev] [oslo] kilo graduation plans
looking at http://specs.openstack.org/openstack/oslo-specs/ and http://specs.openstack.org/openstack/keystone-specs/ should have all the info you need. The specs are hosted at: https://github.com/openstack/keystone-specs there's a template spec too. Thanks, _ Steve Martinelli OpenStack Development - Keystone Core Member Phone: (905) 413-2851 E-Mail: steve...@ca.ibm.com From: Rodrigo Duarte To: "OpenStack Development Mailing List (not for usage questions)" Date: 11/13/2014 10:13 AM Subject: Re: [openstack-dev] [oslo] kilo graduation plans Hi Doug, I'm going to write the spec regarding the policy graduation, it will be placed in the keystone-specs repository. I was wondering if someone have examples of such specs so we can cover all necessary points. On Thu, Nov 13, 2014 at 10:34 AM, Doug Hellmann wrote: On Nov 13, 2014, at 8:31 AM, Dmitry Tantsur wrote: > On 11/13/2014 01:54 PM, Doug Hellmann wrote: >> >> On Nov 13, 2014, at 3:52 AM, Dmitry Tantsur wrote: >> >>> On 11/12/2014 08:06 PM, Doug Hellmann wrote: >>>> During our ?Graduation Schedule? summit session we worked through the list of modules remaining the in the incubator. Our notes are in the etherpad [1], but as part of the "Write it Down? theme for Oslo this cycle I am also posting a summary of the outcome here on the mailing list for wider distribution. Let me know if you remembered the outcome for any of these modules differently than what I have written below. >>>> >>>> Doug >>>> >>>> >>>> >>>> Deleted or deprecated modules: >>>> >>>> funcutils.py - This was present only for python 2.6 support, but it is no longer used in the applications. We are keeping it in the stable/juno branch of the incubator, and removing it from master ( https://review.openstack.org/130092) >>>> >>>> hooks.py - This is not being used anywhere, so we are removing it. ( https://review.openstack.org/#/c/125781/) >>>> >>>> quota.py - A new quota management system is being created ( https://etherpad.openstack.org/p/kilo-oslo-common-quota-library) and should replace this, so we will keep it in the incubator for now but deprecate it. >>>> >>>> crypto/utils.py - We agreed to mark this as deprecated and encourage the use of Barbican or cryptography.py ( https://review.openstack.org/134020) >>>> >>>> cache/ - Morgan is going to be working on a new oslo.cache library as a front-end for dogpile, so this is also deprecated ( https://review.openstack.org/134021) >>>> >>>> apiclient/ - With the SDK project picking up steam, we felt it was safe to deprecate this code as well (https://review.openstack.org/134024). >>>> >>>> xmlutils.py - This module was used to provide a security fix for some XML modules that have since been updated directly. It was removed. ( https://review.openstack.org/#/c/125021/) >>>> >>>> >>>> >>>> Graduating: >>>> >>>> oslo.context: >>>> - Dims is driving this >>>> - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-context >>>> - includes: >>>>context.py >>>> >>>> oslo.service: >>>> - Sachi is driving this >>>> - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-service >>>> - includes: >>>>eventlet_backdoor.py >>>>loopingcall.py >>>>periodic_task.py >>> By te way, right now I'm looking into updating this code to be able to run tasks on a thread pool, not only in one thread (quite a problem for Ironic). Does it somehow interfere with the graduation? Any deadlines or something? >> >> Feature development on code declared ready for graduation is basically frozen until the new library is created. You should plan on doing that work in the new oslo.service repository, which should be showing up soon. And the you describe feature sounds like something for which we would want a spec written, so please consider filing one when you have some of the details worked out. > Sure, right now I'm experimenting in Ironic tree to figure out how it really works. There's a single oslo-specs repo for the whole oslo, right? Yes, that?s right openstack/oslo-specs. Having a branch somewhere as a reference would be great for the spec reviewers, so that seems like a good way to start. Doug > >> >>> >>>>request_utils.py >>>>service.py >>>>sslutils.py >>>>systemd.py >>>>threadgrou
Re: [openstack-dev] [oslo] kilo graduation plans
> On Nov 12, 2014, at 14:22, Doug Hellmann wrote: > > >> On Nov 12, 2014, at 4:40 PM, Adam Young wrote: >> >>> On 11/12/2014 02:06 PM, Doug Hellmann wrote: >>> During our “Graduation Schedule” summit session we worked through the list >>> of modules remaining the in the incubator. Our notes are in the etherpad >>> [1], but as part of the "Write it Down” theme for Oslo this cycle I am also >>> posting a summary of the outcome here on the mailing list for wider >>> distribution. Let me know if you remembered the outcome for any of these >>> modules differently than what I have written below. >>> >>> Doug >>> >>> >>> >>> Deleted or deprecated modules: >>> >>> funcutils.py - This was present only for python 2.6 support, but it is no >>> longer used in the applications. We are keeping it in the stable/juno >>> branch of the incubator, and removing it from master >>> (https://review.openstack.org/130092) >>> >>> hooks.py - This is not being used anywhere, so we are removing it. >>> (https://review.openstack.org/#/c/125781/) >>> >>> quota.py - A new quota management system is being created >>> (https://etherpad.openstack.org/p/kilo-oslo-common-quota-library) and >>> should replace this, so we will keep it in the incubator for now but >>> deprecate it. >>> >>> crypto/utils.py - We agreed to mark this as deprecated and encourage the >>> use of Barbican or cryptography.py (https://review.openstack.org/134020) >>> >>> cache/ - Morgan is going to be working on a new oslo.cache library as a >>> front-end for dogpile, so this is also deprecated >>> (https://review.openstack.org/134021) >>> >>> apiclient/ - With the SDK project picking up steam, we felt it was safe to >>> deprecate this code as well (https://review.openstack.org/134024). >>> >>> xmlutils.py - This module was used to provide a security fix for some XML >>> modules that have since been updated directly. It was removed. >>> (https://review.openstack.org/#/c/125021/) >>> >>> >>> >>> Graduating: >>> >>> oslo.context: >>> - Dims is driving this >>> - >>> https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-context >>> - includes: >>>context.py >>> >>> oslo.service: >>> - Sachi is driving this >>> - >>> https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-service >>> - includes: >>>eventlet_backdoor.py >>>loopingcall.py >>>periodic_task.py >>>request_utils.py >>>service.py >>>sslutils.py >>>systemd.py >>>threadgroup.py >>> >>> oslo.utils: >>> - We need to look into how to preserve the git history as we import these >>> modules. >>> - includes: >>>fileutils.py >>>versionutils.py >> You missed oslo.policy. Graduating, and moving under the AAA program. > > I sure did. I thought we’d held a separate session on policy and I was going > to write it up separately, but now I’m not finding a link to a separate > etherpad. I must have been mixing that discussion up with one of the other > sessions. > > The Keystone team did agree to adopt the policy module and create a library > from it. I have Morgan and Adam down as volunteering to drive that process. > Since we’re changing owners, I’m not sure where we want to put the > spec/blueprint to track the work. Maybe under the keystone program, since > you’re doing the work? > Yeah putting it in keystone specs makes the most sense I think of the locations we have today. --Morgan >> >> >>> >>> >>> Remaining untouched: >>> >>> scheduler/ - Gantt probably makes this code obsolete, but it isn’t clear >>> whether Gantt has enough traction yet so we will hold onto these in the >>> incubator for at least another cycle. >>> >>> report/ - There’s interest in creating an oslo.reports library containing >>> this code, but we haven’t had time to coordinate with Solly about doing >>> that. >>> >>> >>> >>> Other work: >>> >>> We will continue the work on oslo.concurrency and oslo.log that we started >>> during Juno. >>> >>> [1] https://etherpad.openstack.org/p/kilo-oslo-library-proposals >>> ___ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo] kilo graduation plans
Hi Doug, I'm going to write the spec regarding the policy graduation, it will be placed in the keystone-specs repository. I was wondering if someone have examples of such specs so we can cover all necessary points. On Thu, Nov 13, 2014 at 10:34 AM, Doug Hellmann wrote: > > On Nov 13, 2014, at 8:31 AM, Dmitry Tantsur wrote: > > > On 11/13/2014 01:54 PM, Doug Hellmann wrote: > >> > >> On Nov 13, 2014, at 3:52 AM, Dmitry Tantsur > wrote: > >> > >>> On 11/12/2014 08:06 PM, Doug Hellmann wrote: > During our “Graduation Schedule” summit session we worked through the > list of modules remaining the in the incubator. Our notes are in the > etherpad [1], but as part of the "Write it Down” theme for Oslo this cycle > I am also posting a summary of the outcome here on the mailing list for > wider distribution. Let me know if you remembered the outcome for any of > these modules differently than what I have written below. > > Doug > > > > Deleted or deprecated modules: > > funcutils.py - This was present only for python 2.6 support, but it > is no longer used in the applications. We are keeping it in the stable/juno > branch of the incubator, and removing it from master ( > https://review.openstack.org/130092) > > hooks.py - This is not being used anywhere, so we are removing it. ( > https://review.openstack.org/#/c/125781/) > > quota.py - A new quota management system is being created ( > https://etherpad.openstack.org/p/kilo-oslo-common-quota-library) and > should replace this, so we will keep it in the incubator for now but > deprecate it. > > crypto/utils.py - We agreed to mark this as deprecated and encourage > the use of Barbican or cryptography.py ( > https://review.openstack.org/134020) > > cache/ - Morgan is going to be working on a new oslo.cache library as > a front-end for dogpile, so this is also deprecated ( > https://review.openstack.org/134021) > > apiclient/ - With the SDK project picking up steam, we felt it was > safe to deprecate this code as well (https://review.openstack.org/134024). > > xmlutils.py - This module was used to provide a security fix for some > XML modules that have since been updated directly. It was removed. ( > https://review.openstack.org/#/c/125021/) > > > > Graduating: > > oslo.context: > - Dims is driving this > - > https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-context > - includes: > context.py > > oslo.service: > - Sachi is driving this > - > https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-service > - includes: > eventlet_backdoor.py > loopingcall.py > periodic_task.py > >>> By te way, right now I'm looking into updating this code to be able to > run tasks on a thread pool, not only in one thread (quite a problem for > Ironic). Does it somehow interfere with the graduation? Any deadlines or > something? > >> > >> Feature development on code declared ready for graduation is basically > frozen until the new library is created. You should plan on doing that work > in the new oslo.service repository, which should be showing up soon. And > the you describe feature sounds like something for which we would want a > spec written, so please consider filing one when you have some of the > details worked out. > > Sure, right now I'm experimenting in Ironic tree to figure out how it > really works. There's a single oslo-specs repo for the whole oslo, right? > > Yes, that’s right openstack/oslo-specs. Having a branch somewhere as a > reference would be great for the spec reviewers, so that seems like a good > way to start. > > Doug > > > > >> > >>> > request_utils.py > service.py > sslutils.py > systemd.py > threadgroup.py > > oslo.utils: > - We need to look into how to preserve the git history as we import > these modules. > - includes: > fileutils.py > versionutils.py > > > > Remaining untouched: > > scheduler/ - Gantt probably makes this code obsolete, but it isn’t > clear whether Gantt has enough traction yet so we will hold onto these in > the incubator for at least another cycle. > > report/ - There’s interest in creating an oslo.reports library > containing this code, but we haven’t had time to coordinate with Solly > about doing that. > > > > Other work: > > We will continue the work on oslo.concurrency and oslo.log that we > started during Juno. > > [1] https://etherpad.openstack.org/p/kilo-oslo-library-proposals > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > >>> > >>> > >>> __
Re: [openstack-dev] [oslo] kilo graduation plans
On Nov 13, 2014, at 8:31 AM, Dmitry Tantsur wrote: > On 11/13/2014 01:54 PM, Doug Hellmann wrote: >> >> On Nov 13, 2014, at 3:52 AM, Dmitry Tantsur wrote: >> >>> On 11/12/2014 08:06 PM, Doug Hellmann wrote: During our “Graduation Schedule” summit session we worked through the list of modules remaining the in the incubator. Our notes are in the etherpad [1], but as part of the "Write it Down” theme for Oslo this cycle I am also posting a summary of the outcome here on the mailing list for wider distribution. Let me know if you remembered the outcome for any of these modules differently than what I have written below. Doug Deleted or deprecated modules: funcutils.py - This was present only for python 2.6 support, but it is no longer used in the applications. We are keeping it in the stable/juno branch of the incubator, and removing it from master (https://review.openstack.org/130092) hooks.py - This is not being used anywhere, so we are removing it. (https://review.openstack.org/#/c/125781/) quota.py - A new quota management system is being created (https://etherpad.openstack.org/p/kilo-oslo-common-quota-library) and should replace this, so we will keep it in the incubator for now but deprecate it. crypto/utils.py - We agreed to mark this as deprecated and encourage the use of Barbican or cryptography.py (https://review.openstack.org/134020) cache/ - Morgan is going to be working on a new oslo.cache library as a front-end for dogpile, so this is also deprecated (https://review.openstack.org/134021) apiclient/ - With the SDK project picking up steam, we felt it was safe to deprecate this code as well (https://review.openstack.org/134024). xmlutils.py - This module was used to provide a security fix for some XML modules that have since been updated directly. It was removed. (https://review.openstack.org/#/c/125021/) Graduating: oslo.context: - Dims is driving this - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-context - includes: context.py oslo.service: - Sachi is driving this - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-service - includes: eventlet_backdoor.py loopingcall.py periodic_task.py >>> By te way, right now I'm looking into updating this code to be able to run >>> tasks on a thread pool, not only in one thread (quite a problem for >>> Ironic). Does it somehow interfere with the graduation? Any deadlines or >>> something? >> >> Feature development on code declared ready for graduation is basically >> frozen until the new library is created. You should plan on doing that work >> in the new oslo.service repository, which should be showing up soon. And the >> you describe feature sounds like something for which we would want a spec >> written, so please consider filing one when you have some of the details >> worked out. > Sure, right now I'm experimenting in Ironic tree to figure out how it really > works. There's a single oslo-specs repo for the whole oslo, right? Yes, that’s right openstack/oslo-specs. Having a branch somewhere as a reference would be great for the spec reviewers, so that seems like a good way to start. Doug > >> >>> request_utils.py service.py sslutils.py systemd.py threadgroup.py oslo.utils: - We need to look into how to preserve the git history as we import these modules. - includes: fileutils.py versionutils.py Remaining untouched: scheduler/ - Gantt probably makes this code obsolete, but it isn’t clear whether Gantt has enough traction yet so we will hold onto these in the incubator for at least another cycle. report/ - There’s interest in creating an oslo.reports library containing this code, but we haven’t had time to coordinate with Solly about doing that. Other work: We will continue the work on oslo.concurrency and oslo.log that we started during Juno. [1] https://etherpad.openstack.org/p/kilo-oslo-library-proposals ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >>> ___ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-
Re: [openstack-dev] [oslo] kilo graduation plans
On 11/13/2014 01:54 PM, Doug Hellmann wrote: On Nov 13, 2014, at 3:52 AM, Dmitry Tantsur wrote: On 11/12/2014 08:06 PM, Doug Hellmann wrote: During our “Graduation Schedule” summit session we worked through the list of modules remaining the in the incubator. Our notes are in the etherpad [1], but as part of the "Write it Down” theme for Oslo this cycle I am also posting a summary of the outcome here on the mailing list for wider distribution. Let me know if you remembered the outcome for any of these modules differently than what I have written below. Doug Deleted or deprecated modules: funcutils.py - This was present only for python 2.6 support, but it is no longer used in the applications. We are keeping it in the stable/juno branch of the incubator, and removing it from master (https://review.openstack.org/130092) hooks.py - This is not being used anywhere, so we are removing it. (https://review.openstack.org/#/c/125781/) quota.py - A new quota management system is being created (https://etherpad.openstack.org/p/kilo-oslo-common-quota-library) and should replace this, so we will keep it in the incubator for now but deprecate it. crypto/utils.py - We agreed to mark this as deprecated and encourage the use of Barbican or cryptography.py (https://review.openstack.org/134020) cache/ - Morgan is going to be working on a new oslo.cache library as a front-end for dogpile, so this is also deprecated (https://review.openstack.org/134021) apiclient/ - With the SDK project picking up steam, we felt it was safe to deprecate this code as well (https://review.openstack.org/134024). xmlutils.py - This module was used to provide a security fix for some XML modules that have since been updated directly. It was removed. (https://review.openstack.org/#/c/125021/) Graduating: oslo.context: - Dims is driving this - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-context - includes: context.py oslo.service: - Sachi is driving this - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-service - includes: eventlet_backdoor.py loopingcall.py periodic_task.py By te way, right now I'm looking into updating this code to be able to run tasks on a thread pool, not only in one thread (quite a problem for Ironic). Does it somehow interfere with the graduation? Any deadlines or something? Feature development on code declared ready for graduation is basically frozen until the new library is created. You should plan on doing that work in the new oslo.service repository, which should be showing up soon. And the you describe feature sounds like something for which we would want a spec written, so please consider filing one when you have some of the details worked out. Sure, right now I'm experimenting in Ironic tree to figure out how it really works. There's a single oslo-specs repo for the whole oslo, right? request_utils.py service.py sslutils.py systemd.py threadgroup.py oslo.utils: - We need to look into how to preserve the git history as we import these modules. - includes: fileutils.py versionutils.py Remaining untouched: scheduler/ - Gantt probably makes this code obsolete, but it isn’t clear whether Gantt has enough traction yet so we will hold onto these in the incubator for at least another cycle. report/ - There’s interest in creating an oslo.reports library containing this code, but we haven’t had time to coordinate with Solly about doing that. Other work: We will continue the work on oslo.concurrency and oslo.log that we started during Juno. [1] https://etherpad.openstack.org/p/kilo-oslo-library-proposals ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo] kilo graduation plans
On Nov 13, 2014, at 3:52 AM, Dmitry Tantsur wrote: > On 11/12/2014 08:06 PM, Doug Hellmann wrote: >> During our “Graduation Schedule” summit session we worked through the list >> of modules remaining the in the incubator. Our notes are in the etherpad >> [1], but as part of the "Write it Down” theme for Oslo this cycle I am also >> posting a summary of the outcome here on the mailing list for wider >> distribution. Let me know if you remembered the outcome for any of these >> modules differently than what I have written below. >> >> Doug >> >> >> >> Deleted or deprecated modules: >> >> funcutils.py - This was present only for python 2.6 support, but it is no >> longer used in the applications. We are keeping it in the stable/juno branch >> of the incubator, and removing it from master >> (https://review.openstack.org/130092) >> >> hooks.py - This is not being used anywhere, so we are removing it. >> (https://review.openstack.org/#/c/125781/) >> >> quota.py - A new quota management system is being created >> (https://etherpad.openstack.org/p/kilo-oslo-common-quota-library) and should >> replace this, so we will keep it in the incubator for now but deprecate it. >> >> crypto/utils.py - We agreed to mark this as deprecated and encourage the use >> of Barbican or cryptography.py (https://review.openstack.org/134020) >> >> cache/ - Morgan is going to be working on a new oslo.cache library as a >> front-end for dogpile, so this is also deprecated >> (https://review.openstack.org/134021) >> >> apiclient/ - With the SDK project picking up steam, we felt it was safe to >> deprecate this code as well (https://review.openstack.org/134024). >> >> xmlutils.py - This module was used to provide a security fix for some XML >> modules that have since been updated directly. It was removed. >> (https://review.openstack.org/#/c/125021/) >> >> >> >> Graduating: >> >> oslo.context: >> - Dims is driving this >> - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-context >> - includes: >> context.py >> >> oslo.service: >> - Sachi is driving this >> - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-service >> - includes: >> eventlet_backdoor.py >> loopingcall.py >> periodic_task.py > By te way, right now I'm looking into updating this code to be able to run > tasks on a thread pool, not only in one thread (quite a problem for Ironic). > Does it somehow interfere with the graduation? Any deadlines or something? Feature development on code declared ready for graduation is basically frozen until the new library is created. You should plan on doing that work in the new oslo.service repository, which should be showing up soon. And the you describe feature sounds like something for which we would want a spec written, so please consider filing one when you have some of the details worked out. > >> request_utils.py >> service.py >> sslutils.py >> systemd.py >> threadgroup.py >> >> oslo.utils: >> - We need to look into how to preserve the git history as we import these >> modules. >> - includes: >> fileutils.py >> versionutils.py >> >> >> >> Remaining untouched: >> >> scheduler/ - Gantt probably makes this code obsolete, but it isn’t clear >> whether Gantt has enough traction yet so we will hold onto these in the >> incubator for at least another cycle. >> >> report/ - There’s interest in creating an oslo.reports library containing >> this code, but we haven’t had time to coordinate with Solly about doing that. >> >> >> >> Other work: >> >> We will continue the work on oslo.concurrency and oslo.log that we started >> during Juno. >> >> [1] https://etherpad.openstack.org/p/kilo-oslo-library-proposals >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo] kilo graduation plans
On 11/12/2014 08:06 PM, Doug Hellmann wrote: During our “Graduation Schedule” summit session we worked through the list of modules remaining the in the incubator. Our notes are in the etherpad [1], but as part of the "Write it Down” theme for Oslo this cycle I am also posting a summary of the outcome here on the mailing list for wider distribution. Let me know if you remembered the outcome for any of these modules differently than what I have written below. Doug Deleted or deprecated modules: funcutils.py - This was present only for python 2.6 support, but it is no longer used in the applications. We are keeping it in the stable/juno branch of the incubator, and removing it from master (https://review.openstack.org/130092) hooks.py - This is not being used anywhere, so we are removing it. (https://review.openstack.org/#/c/125781/) quota.py - A new quota management system is being created (https://etherpad.openstack.org/p/kilo-oslo-common-quota-library) and should replace this, so we will keep it in the incubator for now but deprecate it. crypto/utils.py - We agreed to mark this as deprecated and encourage the use of Barbican or cryptography.py (https://review.openstack.org/134020) cache/ - Morgan is going to be working on a new oslo.cache library as a front-end for dogpile, so this is also deprecated (https://review.openstack.org/134021) apiclient/ - With the SDK project picking up steam, we felt it was safe to deprecate this code as well (https://review.openstack.org/134024). xmlutils.py - This module was used to provide a security fix for some XML modules that have since been updated directly. It was removed. (https://review.openstack.org/#/c/125021/) Graduating: oslo.context: - Dims is driving this - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-context - includes: context.py oslo.service: - Sachi is driving this - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-service - includes: eventlet_backdoor.py loopingcall.py periodic_task.py By te way, right now I'm looking into updating this code to be able to run tasks on a thread pool, not only in one thread (quite a problem for Ironic). Does it somehow interfere with the graduation? Any deadlines or something? request_utils.py service.py sslutils.py systemd.py threadgroup.py oslo.utils: - We need to look into how to preserve the git history as we import these modules. - includes: fileutils.py versionutils.py Remaining untouched: scheduler/ - Gantt probably makes this code obsolete, but it isn’t clear whether Gantt has enough traction yet so we will hold onto these in the incubator for at least another cycle. report/ - There’s interest in creating an oslo.reports library containing this code, but we haven’t had time to coordinate with Solly about doing that. Other work: We will continue the work on oslo.concurrency and oslo.log that we started during Juno. [1] https://etherpad.openstack.org/p/kilo-oslo-library-proposals ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo] kilo graduation plans
On Nov 12, 2014, at 4:40 PM, Adam Young wrote: > On 11/12/2014 02:06 PM, Doug Hellmann wrote: >> During our “Graduation Schedule” summit session we worked through the list >> of modules remaining the in the incubator. Our notes are in the etherpad >> [1], but as part of the "Write it Down” theme for Oslo this cycle I am also >> posting a summary of the outcome here on the mailing list for wider >> distribution. Let me know if you remembered the outcome for any of these >> modules differently than what I have written below. >> >> Doug >> >> >> >> Deleted or deprecated modules: >> >> funcutils.py - This was present only for python 2.6 support, but it is no >> longer used in the applications. We are keeping it in the stable/juno branch >> of the incubator, and removing it from master >> (https://review.openstack.org/130092) >> >> hooks.py - This is not being used anywhere, so we are removing it. >> (https://review.openstack.org/#/c/125781/) >> >> quota.py - A new quota management system is being created >> (https://etherpad.openstack.org/p/kilo-oslo-common-quota-library) and should >> replace this, so we will keep it in the incubator for now but deprecate it. >> >> crypto/utils.py - We agreed to mark this as deprecated and encourage the use >> of Barbican or cryptography.py (https://review.openstack.org/134020) >> >> cache/ - Morgan is going to be working on a new oslo.cache library as a >> front-end for dogpile, so this is also deprecated >> (https://review.openstack.org/134021) >> >> apiclient/ - With the SDK project picking up steam, we felt it was safe to >> deprecate this code as well (https://review.openstack.org/134024). >> >> xmlutils.py - This module was used to provide a security fix for some XML >> modules that have since been updated directly. It was removed. >> (https://review.openstack.org/#/c/125021/) >> >> >> >> Graduating: >> >> oslo.context: >> - Dims is driving this >> - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-context >> - includes: >> context.py >> >> oslo.service: >> - Sachi is driving this >> - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-service >> - includes: >> eventlet_backdoor.py >> loopingcall.py >> periodic_task.py >> request_utils.py >> service.py >> sslutils.py >> systemd.py >> threadgroup.py >> >> oslo.utils: >> - We need to look into how to preserve the git history as we import these >> modules. >> - includes: >> fileutils.py >> versionutils.py > You missed oslo.policy. Graduating, and moving under the AAA program. I sure did. I thought we’d held a separate session on policy and I was going to write it up separately, but now I’m not finding a link to a separate etherpad. I must have been mixing that discussion up with one of the other sessions. The Keystone team did agree to adopt the policy module and create a library from it. I have Morgan and Adam down as volunteering to drive that process. Since we’re changing owners, I’m not sure where we want to put the spec/blueprint to track the work. Maybe under the keystone program, since you’re doing the work? > > >> >> >> Remaining untouched: >> >> scheduler/ - Gantt probably makes this code obsolete, but it isn’t clear >> whether Gantt has enough traction yet so we will hold onto these in the >> incubator for at least another cycle. >> >> report/ - There’s interest in creating an oslo.reports library containing >> this code, but we haven’t had time to coordinate with Solly about doing that. >> >> >> >> Other work: >> >> We will continue the work on oslo.concurrency and oslo.log that we started >> during Juno. >> >> [1] https://etherpad.openstack.org/p/kilo-oslo-library-proposals >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo] kilo graduation plans
On 11/12/2014 02:06 PM, Doug Hellmann wrote: During our “Graduation Schedule” summit session we worked through the list of modules remaining the in the incubator. Our notes are in the etherpad [1], but as part of the "Write it Down” theme for Oslo this cycle I am also posting a summary of the outcome here on the mailing list for wider distribution. Let me know if you remembered the outcome for any of these modules differently than what I have written below. Doug Deleted or deprecated modules: funcutils.py - This was present only for python 2.6 support, but it is no longer used in the applications. We are keeping it in the stable/juno branch of the incubator, and removing it from master (https://review.openstack.org/130092) hooks.py - This is not being used anywhere, so we are removing it. (https://review.openstack.org/#/c/125781/) quota.py - A new quota management system is being created (https://etherpad.openstack.org/p/kilo-oslo-common-quota-library) and should replace this, so we will keep it in the incubator for now but deprecate it. crypto/utils.py - We agreed to mark this as deprecated and encourage the use of Barbican or cryptography.py (https://review.openstack.org/134020) cache/ - Morgan is going to be working on a new oslo.cache library as a front-end for dogpile, so this is also deprecated (https://review.openstack.org/134021) apiclient/ - With the SDK project picking up steam, we felt it was safe to deprecate this code as well (https://review.openstack.org/134024). xmlutils.py - This module was used to provide a security fix for some XML modules that have since been updated directly. It was removed. (https://review.openstack.org/#/c/125021/) Graduating: oslo.context: - Dims is driving this - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-context - includes: context.py oslo.service: - Sachi is driving this - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-service - includes: eventlet_backdoor.py loopingcall.py periodic_task.py request_utils.py service.py sslutils.py systemd.py threadgroup.py oslo.utils: - We need to look into how to preserve the git history as we import these modules. - includes: fileutils.py versionutils.py You missed oslo.policy. Graduating, and moving under the AAA program. Remaining untouched: scheduler/ - Gantt probably makes this code obsolete, but it isn’t clear whether Gantt has enough traction yet so we will hold onto these in the incubator for at least another cycle. report/ - There’s interest in creating an oslo.reports library containing this code, but we haven’t had time to coordinate with Solly about doing that. Other work: We will continue the work on oslo.concurrency and oslo.log that we started during Juno. [1] https://etherpad.openstack.org/p/kilo-oslo-library-proposals ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo] kilo graduation plans
On Nov 12, 2014, at 4:16 PM, Doug Hellmann wrote: > > On Nov 12, 2014, at 2:06 PM, Doug Hellmann wrote: > >> During our “Graduation Schedule” summit session we worked through the list >> of modules remaining the in the incubator. Our notes are in the etherpad >> [1], but as part of the "Write it Down” theme for Oslo this cycle I am also >> posting a summary of the outcome here on the mailing list for wider >> distribution. Let me know if you remembered the outcome for any of these >> modules differently than what I have written below. >> >> Doug >> >> >> >> Deleted or deprecated modules: >> >> funcutils.py - This was present only for python 2.6 support, but it is no >> longer used in the applications. We are keeping it in the stable/juno branch >> of the incubator, and removing it from master >> (https://review.openstack.org/130092) >> >> hooks.py - This is not being used anywhere, so we are removing it. >> (https://review.openstack.org/#/c/125781/) >> >> quota.py - A new quota management system is being created >> (https://etherpad.openstack.org/p/kilo-oslo-common-quota-library) and should >> replace this, so we will keep it in the incubator for now but deprecate it. >> >> crypto/utils.py - We agreed to mark this as deprecated and encourage the use >> of Barbican or cryptography.py (https://review.openstack.org/134020) >> >> cache/ - Morgan is going to be working on a new oslo.cache library as a >> front-end for dogpile, so this is also deprecated >> (https://review.openstack.org/134021) >> >> apiclient/ - With the SDK project picking up steam, we felt it was safe to >> deprecate this code as well (https://review.openstack.org/134024). > > I left out the cliutils module, which we are treating the same as apiclient. > The python-openstackclient project replaces cliutils, so we are deprecating > that as well. Hmm, that came out garbled. Let me try again: cliutils is deprecated in favor of python-openstackclient, and everyone is encouraged to contribute to python-openstackclient instead. > >> >> xmlutils.py - This module was used to provide a security fix for some XML >> modules that have since been updated directly. It was removed. >> (https://review.openstack.org/#/c/125021/) >> >> >> >> Graduating: >> >> oslo.context: >> - Dims is driving this >> - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-context >> - includes: >> context.py >> >> oslo.service: >> - Sachi is driving this >> - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-service >> - includes: >> eventlet_backdoor.py >> loopingcall.py >> periodic_task.py >> request_utils.py >> service.py >> sslutils.py >> systemd.py >> threadgroup.py >> >> oslo.utils: >> - We need to look into how to preserve the git history as we import these >> modules. >> - includes: >> fileutils.py >> versionutils.py >> >> >> >> Remaining untouched: >> >> scheduler/ - Gantt probably makes this code obsolete, but it isn’t clear >> whether Gantt has enough traction yet so we will hold onto these in the >> incubator for at least another cycle. >> >> report/ - There’s interest in creating an oslo.reports library containing >> this code, but we haven’t had time to coordinate with Solly about doing that. >> >> >> >> Other work: >> >> We will continue the work on oslo.concurrency and oslo.log that we started >> during Juno. >> >> [1] https://etherpad.openstack.org/p/kilo-oslo-library-proposals >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo] kilo graduation plans
On Nov 12, 2014, at 2:06 PM, Doug Hellmann wrote: > During our “Graduation Schedule” summit session we worked through the list of > modules remaining the in the incubator. Our notes are in the etherpad [1], > but as part of the "Write it Down” theme for Oslo this cycle I am also > posting a summary of the outcome here on the mailing list for wider > distribution. Let me know if you remembered the outcome for any of these > modules differently than what I have written below. > > Doug > > > > Deleted or deprecated modules: > > funcutils.py - This was present only for python 2.6 support, but it is no > longer used in the applications. We are keeping it in the stable/juno branch > of the incubator, and removing it from master > (https://review.openstack.org/130092) > > hooks.py - This is not being used anywhere, so we are removing it. > (https://review.openstack.org/#/c/125781/) > > quota.py - A new quota management system is being created > (https://etherpad.openstack.org/p/kilo-oslo-common-quota-library) and should > replace this, so we will keep it in the incubator for now but deprecate it. > > crypto/utils.py - We agreed to mark this as deprecated and encourage the use > of Barbican or cryptography.py (https://review.openstack.org/134020) > > cache/ - Morgan is going to be working on a new oslo.cache library as a > front-end for dogpile, so this is also deprecated > (https://review.openstack.org/134021) > > apiclient/ - With the SDK project picking up steam, we felt it was safe to > deprecate this code as well (https://review.openstack.org/134024). I left out the cliutils module, which we are treating the same as apiclient. The python-openstackclient project replaces cliutils, so we are deprecating that as well. > > xmlutils.py - This module was used to provide a security fix for some XML > modules that have since been updated directly. It was removed. > (https://review.openstack.org/#/c/125021/) > > > > Graduating: > > oslo.context: > - Dims is driving this > - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-context > - includes: > context.py > > oslo.service: > - Sachi is driving this > - https://blueprints.launchpad.net/oslo-incubator/+spec/graduate-oslo-service > - includes: > eventlet_backdoor.py > loopingcall.py > periodic_task.py > request_utils.py > service.py > sslutils.py > systemd.py > threadgroup.py > > oslo.utils: > - We need to look into how to preserve the git history as we import these > modules. > - includes: > fileutils.py > versionutils.py > > > > Remaining untouched: > > scheduler/ - Gantt probably makes this code obsolete, but it isn’t clear > whether Gantt has enough traction yet so we will hold onto these in the > incubator for at least another cycle. > > report/ - There’s interest in creating an oslo.reports library containing > this code, but we haven’t had time to coordinate with Solly about doing that. > > > > Other work: > > We will continue the work on oslo.concurrency and oslo.log that we started > during Juno. > > [1] https://etherpad.openstack.org/p/kilo-oslo-library-proposals > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo] kilo graduation plans
On Nov 12, 2014, at 3:29 PM, Andreas Jaeger wrote: > On 11/12/2014 08:06 PM, Doug Hellmann wrote: >> During our “Graduation Schedule” summit session we worked through the list >> of modules remaining the in the incubator. Our notes are in the etherpad >> [1], but as part of the "Write it Down” theme for Oslo this cycle I am also >> posting a summary of the outcome here on the mailing list for wider >> distribution. Let me know if you remembered the outcome for any of these >> modules differently than what I have written below. >> >> Doug >> >> >> >> Deleted or deprecated modules: >> >> [...] > >> apiclient/ - With the SDK project picking up steam, we felt it was safe to >> deprecate this code as well (https://review.openstack.org/134024). > > I see all the python clients using this: > python-cinderclient/openstack-common.conf:module=apiclient > python-glanceclient/openstack-common.conf:module=apiclient > python-heatclient/openstack-common.conf:modules=importutils,gettextutils,strutils,apiclient.base,apiclient.exceptions > python-ironicclient/openstack-common.conf:module=apiclient > python-keystoneclient/openstack-common.conf:module=apiclient > python-manilaclient/openstack-common.conf:module=apiclient > python-novaclient/openstack-common.conf:module=apiclient > python-saharaclient/openstack-common.conf:module=apiclient.exceptions > python-troveclient/openstack-common.conf:module=apiclient > python-tuskarclient/openstack-common.conf:module=apiclient > > So, this needs a good transition plan, Right, the idea is to deprecate it so we won’t work on new features, and encourage any energy that would have been spent on new features to go into the SDK project instead. We’ll carry the code for bug fixes until we can safely delete it completely. Doug ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo] kilo graduation plans
On 11/12/2014 08:06 PM, Doug Hellmann wrote:
> During our “Graduation Schedule” summit session we worked through the list of
> modules remaining the in the incubator. Our notes are in the etherpad [1],
> but as part of the "Write it Down” theme for Oslo this cycle I am also
> posting a summary of the outcome here on the mailing list for wider
> distribution. Let me know if you remembered the outcome for any of these
> modules differently than what I have written below.
>
> Doug
>
>
>
> Deleted or deprecated modules:
>
> [...]
> apiclient/ - With the SDK project picking up steam, we felt it was safe to
> deprecate this code as well (https://review.openstack.org/134024).
I see all the python clients using this:
python-cinderclient/openstack-common.conf:module=apiclient
python-glanceclient/openstack-common.conf:module=apiclient
python-heatclient/openstack-common.conf:modules=importutils,gettextutils,strutils,apiclient.base,apiclient.exceptions
python-ironicclient/openstack-common.conf:module=apiclient
python-keystoneclient/openstack-common.conf:module=apiclient
python-manilaclient/openstack-common.conf:module=apiclient
python-novaclient/openstack-common.conf:module=apiclient
python-saharaclient/openstack-common.conf:module=apiclient.exceptions
python-troveclient/openstack-common.conf:module=apiclient
python-tuskarclient/openstack-common.conf:module=apiclient
So, this needs a good transition plan,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF:Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
