Re: [openstack-dev] Unified Limits work stalled - next steps, need for new leadership

2017-10-18 Thread Sean Dague
That sounds great, thank you! Let's synchronize on IRC to do a quick
bootstrapping about where I think the next steps are, then you all can
run with it.

-Sean

On 10/17/2017 11:31 PM, 王玺源 wrote:
> HI Sean,
>   I think that we(Lance and I) from Huawei are willing to take over and
> continue this feature. I hope that we can get some information and
> suggestion from you. Such as: what’s the progress now? What should I do
> now? IMHO, the main work now is to update and polish these two specs[1],
> right? I'll continue to update them if no objection.
>  
> Thanks.
> 
> 
> [1]: https://review.openstack.org/#/c/441203
>  https://review.openstack.org/#/c/455709
> 
> 2017-09-08 3:18 GMT+08:00 Sean Dague  >:
> 
> This is an email that's probably overdue, but time gets away from
> all of us. Coming out of Atlanta and even Boston we were pushing
> pretty hard on a new approach to unify limits, as well as building
> the infrastructure to have hierarchical limits possible in OpenStack
> (keystone merged spec -
> 
> https://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/unified-limits.html
> 
> )
> 
> However, this effort pretty much as run out of gas, and really needs
> a new driver (or set of drivers) to make forward progress. My
> current set of responsibilities doesn't really make it possible for
> me to own driving this (though I will be happy to help others). That
> seems to also be true of many of the others that were engaged.
> 
> This is going out in advance of the PTG in case any developer(s), or
> organizations feel that hierarchical limits are a priority for them,
> and would be willing to step up there. If so please feel free to
> reach out, and we can carve out some PTG time in helping a new push
> organize here.
> 
> However, without new leadership here, the current plan is to just
> put the effort to rest.
> 
>         -Sean
> 
> -- 
> Sean Dague
> http://dague.net
> 
> __
> 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
> 


-- 
Sean Dague
http://dague.net

__
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] Unified Limits work stalled - next steps, need for new leadership

2017-10-17 Thread 王玺源
HI Sean,
  I think that we(Lance and I) from Huawei are willing to take over and
continue this feature. I hope that we can get some information and
suggestion from you. Such as: what’s the progress now? What should I do
now? IMHO, the main work now is to update and polish these two specs[1],
right? I'll continue to update them if no objection.

Thanks.


[1]: https://review.openstack.org/#/c/441203
 https://review.openstack.org/#/c/455709

2017-09-08 3:18 GMT+08:00 Sean Dague :

> This is an email that's probably overdue, but time gets away from all of
> us. Coming out of Atlanta and even Boston we were pushing pretty hard on a
> new approach to unify limits, as well as building the infrastructure to
> have hierarchical limits possible in OpenStack (keystone merged spec -
> https://specs.openstack.org/openstack/keystone-specs/specs/
> keystone/ongoing/unified-limits.html)
>
> However, this effort pretty much as run out of gas, and really needs a new
> driver (or set of drivers) to make forward progress. My current set of
> responsibilities doesn't really make it possible for me to own driving this
> (though I will be happy to help others). That seems to also be true of many
> of the others that were engaged.
>
> This is going out in advance of the PTG in case any developer(s), or
> organizations feel that hierarchical limits are a priority for them, and
> would be willing to step up there. If so please feel free to reach out, and
> we can carve out some PTG time in helping a new push organize here.
>
> However, without new leadership here, the current plan is to just put the
> effort to rest.
>
> -Sean
>
> --
> Sean Dague
> http://dague.net
>
> __
> 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