Open Stack

Dear all,

I have prepared a draft template for discussion on Monday: https://etherpad.openstack.org/p/template_gap_and_overlap_analysis

Best regards,
Gerald

From: Shamail [mailto:itzshamail at gmail.com]
Sent: Donnerstag, 12. Januar 2017 23:20
To: Sun, Yih Leong <yih.leong.sun at intel.com>
Cc: Kunzmann, Gerald <kunzmann at docomolab-euro.com>; Arkady.Kanevsky at dell.com; user-committee at lists.openstack.org; Tokunaga, Keiichirou <tokunaga.keiich at jp.fujitsu.com>
Subject: Re: [User-committee] [Product] User Story Trackers for OpenStack Feature Tracker Announcement



On Jan 12, 2017, at 2:16 PM, Sun, Yih Leong <yih.leong.sun at intel.com<mailto:yih.leong.sun at intel.com>> wrote:
I think that is fine.
We also had the bare-metal gap analysis without the common template.

Carol,Shamail,
Do we have slot to add into next week PWG agenda:

-          gap-analysis template and where to keep gap-analysis document (e.g. user-stories/gap-analysis)

-          review capacity-management’s gap-analysis (https://etherpad.opnfv.org/p/promise_gap_analysis)
+1, I think it would be a good addition... it's better to discuss now rather than have to refactor gap analysis/implementation plans later.



From: Kunzmann, Gerald [mailto:kunzmann at docomolab-euro.com]
Sent: Thursday, January 12, 2017 7:33 AM
To: Sun, Yih Leong <yih.leong.sun at intel.com<mailto:yih.leong.sun at intel.com>>; Shamail Tahir <itzshamail at gmail.com<mailto:itzshamail at gmail.com>>
Cc: Arkady.Kanevsky at dell.com<mailto:Arkady.Kanevsky at dell.com>; user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>; Tokunaga, Keiichirou <tokunaga.keiich at jp.fujitsu.com<mailto:tokunaga.keiich at jp.fujitsu.com>>
Subject: RE: [User-committee] [Product] User Story Trackers for OpenStack Feature Tracker Announcement

Hi,

Thanks for the clarification.

Can we perform in parallel the 1) creation of the template and 2) the discussion on the gap analysis in order not to delay 2) ?

We have in today’s OPNFV Promise meeting agreed on the gap analysis document and would like to submit this to the PWG for discussion. Can we put the gap analysis to next week’s agenda?

Best regards,
Gerald

From: Sun, Yih Leong [mailto:yih.leong.sun at intel.com]
Sent: Mittwoch, 11. Januar 2017 18:50
To: Kunzmann, Gerald <kunzmann at docomolab-euro.com<mailto:kunzmann at docomolab-euro.com>>; Shamail Tahir <itzshamail at gmail.com<mailto:itzshamail at gmail.com>>
Cc: Arkady.Kanevsky at dell.com<mailto:Arkady.Kanevsky at dell.com>; user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>; Tokunaga, Keiichirou <tokunaga.keiich at jp.fujitsu.com<mailto:tokunaga.keiich at jp.fujitsu.com>>
Subject: RE: [User-committee] [Product] User Story Trackers for OpenStack Feature Tracker Announcement

That’s a good question. There isn’t a template for gap analysis yet.

We also documented the gap analysis of bare metal on an etherpad so far.
Given that we have two gap analysis documented now (bare metal [1] and capacity management [2]), I would suggest we base on these two documents and create a common template that make future work easier.

We should keep the gap document in the git repo.
We have “tracker” and “user-stories/proposed” in the root now. Maybe we can put all the gap documents under “user-stories/gap-analysis”, using the same filename as in “user-stories/proposed”?
e.g.
- user-stories/proposed/baremetal-service.rst
- user-stories/proposed/capacity_management.rst

- user-stories/gap-analysis/baremetal-service.rst
- user-stories/gap-analysis/capacity_management.rst

This allows us to maintain and work on separate documents.
Any thoughts?

On a side note, I realized that not all filename using the same convention. E.g. some uses hyphen but some uses underscore.
We should follow the Docs convention and uses hyphen for filename [3]. (e.g. abc-xyz.rst)

[1] https://etherpad.openstack.org/p/bare_metal_service_gap_and_overlap_analysis
[2] https://etherpad.opnfv.org/p/promise_gap_analysis
[3] http://docs.openstack.org/contributor-guide/rst-conv/file-naming.html


From: Kunzmann, Gerald [mailto:kunzmann at docomolab-euro.com]
Sent: Wednesday, January 11, 2017 1:14 AM
To: Kunzmann, Gerald <kunzmann at docomolab-euro.com<mailto:kunzmann at docomolab-euro.com>>; Shamail Tahir <itzshamail at gmail.com<mailto:itzshamail at gmail.com>>
Cc: Arkady.Kanevsky at dell.com<mailto:Arkady.Kanevsky at dell.com>; user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>
Subject: Re: [User-committee] [Product] User Story Trackers for OpenStack Feature Tracker Announcement

Hi Shamail,

According to the user story workflow, the next step is to conduct a gap analysis.
We have started drafting such analysis with a focus on the resource reservation aspects: https://etherpad.opnfv.org/p/promise_gap_analysis

Is there a template on how such gap analysis should look like?
Is there a specific space in the repo where we should upload the analysis?

Best regards,
Gerald


From: Kunzmann, Gerald [mailto:kunzmann at docomolab-euro.com]
Sent: Donnerstag, 5. Januar 2017 21:58
To: Shamail Tahir <itzshamail at gmail.com<mailto:itzshamail at gmail.com>>
Cc: Arkady.Kanevsky at dell.com<mailto:Arkady.Kanevsky at dell.com>; product-wg at lists.openstack.org<mailto:product-wg at lists.openstack.org>; user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>
Subject: Re: [User-committee] [Product] User Story Trackers for OpenStack Feature Tracker Announcement

Hi Shamail,

Thanks for the clarification.
We are currently working in OPNFV Promise and OpenStack Blazar projects on such an implementation plan. I will come back to you and the PWG once we have a draft ready from our side.

Best regards,
Gerald

From: Shamail Tahir [mailto:itzshamail at gmail.com]
Sent: Donnerstag, 5. Januar 2017 17:45
To: Kunzmann, Gerald <kunzmann at docomolab-euro.com<mailto:kunzmann at docomolab-euro.com>>
Cc: Arkady.Kanevsky at dell.com<mailto:Arkady.Kanevsky at dell.com>; user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>; product-wg at lists.openstack.org<mailto:product-wg at lists.openstack.org>
Subject: Re: [User-committee] [Product] User Story Trackers for OpenStack Feature Tracker Announcement

Hi Gerald,

The capacity management tracker is just a sample and not populated with actual data (relevant specs, blueprints, etc.)  We do need that one updated if we think we have the implementation plan defined for it.  Happy to discuss further at our next meeting.

Thanks,
Shamail


On Thu, Jan 5, 2017 at 4:15 AM, Kunzmann, Gerald <kunzmann at docomolab-euro.com<mailto:kunzmann at docomolab-euro.com>> wrote:
Dear Shamail,

Thanks for having added the capacity mgmt. user story to the tracker.

It seems the tracker has a bug:
It reports 0% completed for the capacity mgmt. user story on the overview page: http://featuretracker.openstack.org/projectList
And 80% completed on the project page: http://featuretracker.openstack.org/projectDetail/0002

Best regards,
Gerald

From: Shamail [mailto:itzshamail at gmail.com<mailto:itzshamail at gmail.com>]
Sent: Dienstag, 3. Januar 2017 19:25
To: Arkady.Kanevsky at dell.com<mailto:Arkady.Kanevsky at dell.com>
Cc: user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>; product-wg at lists.openstack.org<mailto:product-wg at lists.openstack.org>
Subject: Re: [User-committee] [Product] User Story Trackers for OpenStack Feature Tracker Announcement

Hi Arkady,

I would suggest coordinating with Pete Chadwick since he is the user story owner for HA VM.  If we believe we know the blueprints/specs needed (e.g. gaps analysis is completed and we have an implementation plan) then we should go ahead and create the tracker for it.

Trackers are only needed for stories that are moving towards implementation with gaps analysis completed already.  Most of our stories are not at that stage yet.

Thanks,
Shamail

On Jan 3, 2017, at 12:49 PM, <Arkady.Kanevsky at dell.com<mailto:Arkady.Kanevsky at dell.com>> <Arkady.Kanevsky at dell.com<mailto:Arkady.Kanevsky at dell.com>> wrote:
Thanks Shamail,
We need to put all stories we voted to push last cycle under the project list.
What about other stories?
HA VM is not supported with rolling upgrade.  How do we want to track that.
RedHat and DellEMC are working on it.

Thanks,
Arkady


-----Original Message-----
From: Sun, Yih Leong [mailto:yih.leong.sun at intel.com]
Sent: Tuesday, January 03, 2017 11:43 AM
To: Shamail Tahir <itzshamail at gmail.com<mailto:itzshamail at gmail.com>>; product-wg at lists.openstack.org<mailto:product-wg at lists.openstack.org>; user-committee <user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>>
Subject: Re: [Product] User Story Trackers for OpenStack Feature Tracker Announcement

Hi Shamail,

I will collaborate with Kei (Fujitsu) to create the tracker for baremetal user story [2].

Where is this "Feature Tracker" pulling data from?
Are we adding the user-story-tracker.json [3] to the tracker folder [4]?

[2] https://specs.openstack.org/openstack/openstack-user-stories/user-stories/proposed/baremetal-service.html
[3] https://github.com/openstack/openstack-user-stories/blob/master/user-story-tracker.json
[4] https://github.com/openstack/openstack-user-stories/tree/master/tracker

Thanks!
Leong.


-----Original Message-----
From: Shamail Tahir [mailto:itzshamail at gmail.com]
Sent: Tuesday, January 3, 2017 9:32 AM
To: product-wg at lists.openstack.org<mailto:product-wg at lists.openstack.org>; user-committee <user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>>
Subject: [Product] User Story Trackers for OpenStack Feature Tracker Announcement

Hi everyone,

The first version of the OpenStack Feature Tracker (formerly known as the User Story Tracker) is essentially complete now thanks to the amazing work done by Teresita, Viridiana and Marcela from Intel (along with help from Jimmy and Jeremy from the OpenStack Foundation)...  We would like to announce the availability of this tool more broadly (e.g. dev ML) but don't want to proceed with that step until we have actual user story trackers in place.  If you visit the Feature Tracker[1], you will notice that the trackers currently being used just contain dummy/test data.

We believe the 'first impression' for the tool will be more powerful if done with actual tracker data.  I know we have a few user stories, namely the bare-metal service and rolling upgrades, that are probably ready for tracking.  I would like to ask if the user stories owners could create actual trackers and submit them to our repository?

[1] http://featuretracker.openstack.org

--
Thanks,
Shamail Tahir
t: @ShamailXD
tz: Eastern Time
_______________________________________________
Product-wg mailing list
Product-wg at lists.openstack.org<mailto: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<mailto:Product-wg at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg



--
Thanks,
Shamail Tahir
t: @ShamailXD
tz: Eastern Time
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20170113/4cca2e97/attachment-0001.html>