[Starlingx-discuss] LaunchPad vs Storyboard for bug tracking
Hi All, Launchpad seems to be more mature compare to Storyboard for bug tracking, here is list of advantages I found in few minutes looking at it: 1: Advance search 2: More meta data : Status, Importance, Milestone 3: Attachments 4: subscriber management 4: Ildiko mentioned there would migration path to new platform So my question is for people who know the history and have more experience using it, Why Openstack is trying to replace this and move to Storyboard? What are the shortcomings for day to day use? Basically why we should not be using it to manage our bugs for StarlingX? Thanks, Dariush
On Thu, Aug 9, 2018 at 9:31 AM, Eslimi, Dariush <Dariush.Eslimi@windriver.com> wrote:
So my question is for people who know the history and have more experience using it, Why Openstack is trying to replace this and move to Storyboard? What are the shortcomings for day to day use?
OpenStack's reasons for leaving LP include: * needing to get to a single authentication authority (LP requires Ubuntu One accounts) to allow using a DCO rather than ICLA * limitations on task tracking across projects * persistent issues with API response and performance Thierry Carrez's post with more details is at https://storyboard-blog.io/why-storyboard-for-openstack.html dt -- Dean Troyer dtroyer@gmail.com
Thanks for response, but as is today not all that is mentioned in the blog is addressed by Storyboard: * We will depend on UbuntuOne regardless of Launchpad, as we need it for gerrit. * The limit of after 10 task per bug and performance, have this been discussed and raised with Launchpad team? Storyboard is not very speedy today, and this would not be an issue for StarlingX, limit of 10 is workable. * API-first : Storybard suffers from same issue, rich API, UI not representation of API and backend. So for short term, I suggest we use for Launchpad until Storyboard catches up and becomes a viable option for bug tracking. Thanks, Dariush -----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: August-09-18 1:06 PM To: Eslimi, Dariush Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] LaunchPad vs Storyboard for bug tracking On Thu, Aug 9, 2018 at 9:31 AM, Eslimi, Dariush <Dariush.Eslimi@windriver.com> wrote:
So my question is for people who know the history and have more experience using it, Why Openstack is trying to replace this and move to Storyboard? What are the shortcomings for day to day use?
OpenStack's reasons for leaving LP include: * needing to get to a single authentication authority (LP requires Ubuntu One accounts) to allow using a DCO rather than ICLA * limitations on task tracking across projects * persistent issues with API response and performance Thierry Carrez's post with more details is at https://storyboard-blog.io/why-storyboard-for-openstack.html dt -- Dean Troyer dtroyer@gmail.com
On Thu, Aug 9, 2018 at 1:10 PM, Eslimi, Dariush <Dariush.Eslimi@windriver.com> wrote:
* We will depend on UbuntuOne regardless of Launchpad, as we need it for gerrit.
OpenStack will move Gerrit and other tooling to the OpenStack Foundation auth authority when we are free of LaunchPad, this tie is why it is an issue. That change will also affect StarlingX and any other project using OpenStack Foundation resources.
* API-first : Storybard suffers from same issue, rich API, UI not representation of API and backend.
You have this backward. LaunchPad does not expose everything in its API that it can do in the web UI. This has hampered some automation efforts and in fact was one of the motivators for the SB teams position of API first. The situation with Storyboard allows users with API capabilities to solve their own problems regarding UI limitations. This is not possible with LaunchPad. I am not arguing a position one way or the other, just clarifying the stated reasons and why a specific organization has wanted to leave LaunchPad for over 6 years now. dt -- Dean Troyer dtroyer@gmail.com
Thanks for clarification, I understand the motivations, all I am trying to say Storyboard is not ready yet for bugs. So we can join others in Openstack and move when all move to new platform. Dariush -----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: August-09-18 4:07 PM To: Eslimi, Dariush Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] LaunchPad vs Storyboard for bug tracking On Thu, Aug 9, 2018 at 1:10 PM, Eslimi, Dariush <Dariush.Eslimi@windriver.com> wrote:
* We will depend on UbuntuOne regardless of Launchpad, as we need it for gerrit.
OpenStack will move Gerrit and other tooling to the OpenStack Foundation auth authority when we are free of LaunchPad, this tie is why it is an issue. That change will also affect StarlingX and any other project using OpenStack Foundation resources.
* API-first : Storybard suffers from same issue, rich API, UI not representation of API and backend.
You have this backward. LaunchPad does not expose everything in its API that it can do in the web UI. This has hampered some automation efforts and in fact was one of the motivators for the SB teams position of API first. The situation with Storyboard allows users with API capabilities to solve their own problems regarding UI limitations. This is not possible with LaunchPad. I am not arguing a position one way or the other, just clarifying the stated reasons and why a specific organization has wanted to leave LaunchPad for over 6 years now. dt -- Dean Troyer dtroyer@gmail.com
Hi, Thanks Dariush for doing the evaluation work. While Launchpad is not perfect, I would like to confirm on this thread too what Dariush mentioned as well, there is a migration script and process to move from Launchpad to StoryBoard which I think is a big advantage. Thanks and Best Regards, Ildikó
On 2018. Aug 9., at 22:19, Eslimi, Dariush <Dariush.Eslimi@windriver.com> wrote:
Thanks for clarification, I understand the motivations, all I am trying to say Storyboard is not ready yet for bugs. So we can join others in Openstack and move when all move to new platform.
Dariush
-----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: August-09-18 4:07 PM To: Eslimi, Dariush Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] LaunchPad vs Storyboard for bug tracking
On Thu, Aug 9, 2018 at 1:10 PM, Eslimi, Dariush <Dariush.Eslimi@windriver.com> wrote:
* We will depend on UbuntuOne regardless of Launchpad, as we need it for gerrit.
OpenStack will move Gerrit and other tooling to the OpenStack Foundation auth authority when we are free of LaunchPad, this tie is why it is an issue. That change will also affect StarlingX and any other project using OpenStack Foundation resources.
* API-first : Storybard suffers from same issue, rich API, UI not representation of API and backend.
You have this backward. LaunchPad does not expose everything in its API that it can do in the web UI. This has hampered some automation efforts and in fact was one of the motivators for the SB teams position of API first. The situation with Storyboard allows users with API capabilities to solve their own problems regarding UI limitations. This is not possible with LaunchPad.
I am not arguing a position one way or the other, just clarifying the stated reasons and why a specific organization has wanted to leave LaunchPad for over 6 years now.
dt
--
Dean Troyer dtroyer@gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
I spent some time looking at LaunchPad today. It seems like it should meet our needs for bug handling. We might want to use it as a place to work on specs/blueprints. I suggest we spin up an instance and start using it. We'll know pretty quickly if the issues identified in this thread are serious enough that we'd want to go to Plan B. bruecj -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa@gmail.com] Sent: Thursday, August 9, 2018 1:57 PM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] LaunchPad vs Storyboard for bug tracking Hi, Thanks Dariush for doing the evaluation work. While Launchpad is not perfect, I would like to confirm on this thread too what Dariush mentioned as well, there is a migration script and process to move from Launchpad to StoryBoard which I think is a big advantage. Thanks and Best Regards, Ildikó
On 2018. Aug 9., at 22:19, Eslimi, Dariush <Dariush.Eslimi@windriver.com> wrote:
Thanks for clarification, I understand the motivations, all I am trying to say Storyboard is not ready yet for bugs. So we can join others in Openstack and move when all move to new platform.
Dariush
-----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: August-09-18 4:07 PM To: Eslimi, Dariush Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] LaunchPad vs Storyboard for bug tracking
On Thu, Aug 9, 2018 at 1:10 PM, Eslimi, Dariush <Dariush.Eslimi@windriver.com> wrote:
* We will depend on UbuntuOne regardless of Launchpad, as we need it for gerrit.
OpenStack will move Gerrit and other tooling to the OpenStack Foundation auth authority when we are free of LaunchPad, this tie is why it is an issue. That change will also affect StarlingX and any other project using OpenStack Foundation resources.
* API-first : Storybard suffers from same issue, rich API, UI not representation of API and backend.
You have this backward. LaunchPad does not expose everything in its API that it can do in the web UI. This has hampered some automation efforts and in fact was one of the motivators for the SB teams position of API first. The situation with Storyboard allows users with API capabilities to solve their own problems regarding UI limitations. This is not possible with LaunchPad.
I am not arguing a position one way or the other, just clarifying the stated reasons and why a specific organization has wanted to leave LaunchPad for over 6 years now.
dt
--
Dean Troyer dtroyer@gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
participants (4)
-
Dean Troyer
-
Eslimi, Dariush
-
Ildiko Vancsa
-
Jones, Bruce E