Open Stack

Should we create a review on [1] and push this discussion to gerrit so that this can be tracked? 
Or is there a need to create a new user story?

[1] https://github.com/openstack/openstack-user-stories/blob/master/user-stories/proposed/capacity_management.rst

Thanks!
Leong.

-----Original Message-----
From: Shamail [mailto:itzshamail at gmail.com] 
Sent: Wednesday, May 25, 2016 10:02 AM
To: Tim Bell <Tim.Bell at cern.ch>
Cc: product-wg at lists.openstack.org
Subject: Re: [Product] Quota and accounting user stories from the scientific working group



> On May 25, 2016, at 9:59 AM, Tim Bell <Tim.Bell at cern.ch> wrote:
> 
> 
>> On 25/05/16 18:53, "Shamail" <itzshamail at gmail.com> wrote:
>> 
>> Hi,
>> 
>>> On May 25, 2016, at 9:42 AM, Tim Bell <Tim.Bell at cern.ch> wrote:
>>> 
>>> I’d be happy to either add a new one or to expand the current one in quota/capacity planning ?
>>> 
>>> My worry to expand the existing one is that since there is a significant set of additional use cases to add, these new items would dilute the existing user story.
>> I think the concern is valid... The initial capacity management story was submitted with reservations in mind.  Our goal with this story, during the current cycle, was to re-evaluate whether it fits how quotas are being leveraged and desired attributes that we might need to enhance.  From the Scientific WG perspective, is resource reservation not a focus or do you see the user story/requirements being a super-set (reservation related topics AND the ones mentioned below)?  
> 
> There is a subset of the community for HPC who are interested in reservations and I think the existing user story covers this need. My (very biased) opinion is that this is not the highest priority of the HTC/HPC quota/scheduling.
> 
>>> On the other hand, we could make a consistent set of requests if we integrate them and it would avoid asking for potentially incompatible requirements.
>> We could leverage a single user story but clearly delineate the user stories through usage examples.  
>>> 
>>> I’ve listed the needs at the end of the CERN blog which seems to sum up most of the scientific working group requirements so I’m happy to work on whatever would be the best way to present these needs (both the existing user story and the HTC/HPC ones) to the community.
>> One approach might be to revisit the current content in the capacity management user story and trim any items that are not being surfaced currently through the market needs for enterprise, HTC/HPC, and telco and then add the user stories from HTC/HPC and solicit feedback from enterprise and telco to build a holistic user story for capacity management.  Thoughts?  If you agree then I can work with the team to start the refactor.
> 
> I think the needs identified in the existing user story are very valid (e.g. in a classroom environment envisaged by the Blazar project or an enterprise “run the end of month processing” capacity request).
> 
> I’d be fine to work with the product-wg to include the needs we identified in Austin into the user story.
Perfect, thanks Tim.  I'll follow up with you so we can draft a change.
> 
>>> Tim
>>> 
>>> From: "Arkady_Kanevsky at DELL.com" <Arkady_Kanevsky at DELL.com>
>>> Date: Wednesday 25 May 2016 at 18:34
>>> To: Tim Bell <Tim.Bell at cern.ch>, "product-wg at lists.openstack.org" <product-wg at lists.openstack.org>
>>> Subject: RE: [Product] Quota and accounting user stories from the scientific working group
>>> 
>>> Tim,
>>> Can we add HTC/HPC quota and accounting requirements as use cases under the current user stories?
>>> Arkady
>>> 
>>> -----Original Message-----
>>> From: Tim Bell [mailto:Tim.Bell at cern.ch]
>>> Sent: Wednesday, May 25, 2016 11:23 AM
>>> To: OpenStack Product Work Group
>>> Subject: [Product] Quota and accounting user stories from the scientific working group
>>> 
>>> The scientific working group (https://wiki.openstack.org/wiki/Scientific_working_group) has reviewed the quota and capacity planning user story (http://specs.openstack.org/openstack/openstack-user-stories/user-stories/draft/capacity_management.html). Much of the content is around the area of resource reservation.
>>> 
>>> During the summit, we had reviewed the areas of interest for high performance and high throughput computing. A number of the scenarios were described in the CERN blog at http://openstack-in-production.blogspot.fr/2016/04/resource-management-at-cern.html but there are several others.
>>> 
>>> We would be interested to find the right ways to contribute to the product working group user stories but I would be concerned that if we add the HTC/HPC user stories to the existing quota and capacity planning user story, it will overload the description since there are many additional items not covered in the draft (performance related accounting and scheduling, nested quotas, pre-emptible instances, missing quota for projects and setting quota below utilization).
>>> 
>>> What would be the best way to proceed ?
>>> 
>>> Tim
>>> 
>>> _______________________________________________
>>> Product-wg mailing list
>>> Product-wg at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg
>>> _______________________________________________
>>> Product-wg mailing list
>>> Product-wg at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg
> 

_______________________________________________
Product-wg mailing list
Product-wg at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg