Re: [openstack-dev] [tripleo] Migration to Storyboard
On Fri, Jun 15, 2018 at 2:13 AM Michele Baldessari wrote: > On Mon, May 21, 2018 at 01:58:26PM -0700, Emilien Macchi wrote: > > During the Storyboard session today: > > https://etherpad.openstack.org/p/continuing-the-migration-lp-sb > > > > We mentioned that TripleO would continue to migrate during Rocky cycle. > > Like Alex mentioned in this thread, we need to migrate the scripts used > by > > the CI squad so they work with SB. > > Once this is done, we'll proceed to the full migration of all blueprints > > and bugs into tripleo-common project in SB. > > Projects like tripleo-validations, tripleo-ui (more?) who have 1:1 > mapping > > between their "name" and project repository could use a dedicated project > > in SB, although we need to keep things simple for our users so they know > > where to file a bug without confusion. > > We hope to proceed during Rocky but it'll probably take some time to > update > > our scripts and documentation, also educate our community to use the > tool, > > so we expect the Stein cycle the first cycle where we actually consume > SB. > > > > I really wanted to thank the SB team for their patience and help, TripleO > > is big and this migration hasn't been easy but we'll make it :-) > > Having used storyboard for the first time today to file a bug^Wstory in > heat, > I'd like to raise a couple of concerns on this migration. And by all > means, if I just missed to RTFM, feel free to point me in the right > direction. > > 1. Searching for bugs in a specific project is *extremely* cumbersome >and I am not even sure I got it right (first you need to put >openstack/project in the search bar, wait and click it. Then you add >the term you are looking for. I have genuinely no idea if I get all >the issues I was looking for or not as it is not obvious on what >fields this search is performed > The wait and click-it part is being resolved- that was a bug where you had to select it to actually get the correct project- it couldn't just be typed. Yes, if you are looking for stories from a certain project- you want to restrict the search by adding the project- same way you do in gerrit. If you feel like the search results aren't showing as many as you think there should be- you can adjust the setting to show more results. I suppose we could add some sort of natural language process thing where with the results it says searching for 'y' in project 'x' (where you put x and y into the search- x as the project and y as the term as you did in the description above). Not sure if that would help? I think the search is a lot more intelligent than people assume and so it seems difficult to deal with until you figure out how it works. Checking out the api docs on search might be helpful[1]? [1] https://docs.openstack.org/infra/storyboard/webapi/v1.html > 2. Advanced search is either very well hidden or not existant yet? >E.g. how do you search for bugs filed by someone or over a certain >release, or just generally more complex searches which are super >useful in order to avoid filing duplicate bugs. > > Advanced search is the magnifying glass icon on the left navigation bar (assuming you are using the webclient interface at storyboard.o.o) which I think is what you were describing using above. The search in the top right of the webclient is just a jump to quick search. > I think Zane's additional list also matches my experience very well: > http://lists.openstack.org/pipermail/openstack-dev/2018-June/131365.html > > I think a lot of Zane's comment's have already been addressed, but I can go reply on that thread too and hopefully clear up some of the concerns/fears. > So my take is that a migration atm is a bit premature and I would > postpone it at least to Stein. > > Hopefully- it will be a stein release goal so it wouldn't be that big a deal if you waited, but ideally, if there aren't any real blockers for your team, the sooner the better. > Thanks, > Michele > > > Thanks, > > > > On Tue, May 15, 2018 at 7:53 AM, Alex Schultz > wrote: > > > > > Bumping this up so folks can review this. It was mentioned in this > > > week's meeting that it would be a good idea for folks to take a look > > > at Storyboard to get familiar with it. The upstream docs have been > > > updated[0] to point to the differences when dealing with proposed > > > patches. Please take some time to review this and raise any > > > concerns/issues now. > > > > > > Thanks, > > > -Alex > > > > > > [0] https://docs.openstack.org/infra/manual/developers.html# > > > development-workflow > > > > > > On Wed, May 9, 2018 at 1:24 PM, Alex Schultz > wrote: > > > > Hello tripleo folks, > > > > > > > > So we've been experimenting with migrating some squads over to > > > > storyboard[0] but this seems to be causing more issues than perhaps > > > > it's worth. Since the upstream community would like to standardize > on > > > > Storyboard at some point, I would propose that we do a cut over of > a
Re: [openstack-dev] [tripleo] Migration to Storyboard
On Fri, Jun 15, 2018 at 3:12 AM, Michele Baldessari wrote: > On Mon, May 21, 2018 at 01:58:26PM -0700, Emilien Macchi wrote: >> During the Storyboard session today: >> https://etherpad.openstack.org/p/continuing-the-migration-lp-sb >> >> We mentioned that TripleO would continue to migrate during Rocky cycle. >> Like Alex mentioned in this thread, we need to migrate the scripts used by >> the CI squad so they work with SB. >> Once this is done, we'll proceed to the full migration of all blueprints >> and bugs into tripleo-common project in SB. >> Projects like tripleo-validations, tripleo-ui (more?) who have 1:1 mapping >> between their "name" and project repository could use a dedicated project >> in SB, although we need to keep things simple for our users so they know >> where to file a bug without confusion. >> We hope to proceed during Rocky but it'll probably take some time to update >> our scripts and documentation, also educate our community to use the tool, >> so we expect the Stein cycle the first cycle where we actually consume SB. >> >> I really wanted to thank the SB team for their patience and help, TripleO >> is big and this migration hasn't been easy but we'll make it :-) > > Having used storyboard for the first time today to file a bug^Wstory in heat, > I'd like to raise a couple of concerns on this migration. And by all > means, if I just missed to RTFM, feel free to point me in the right > direction. > > 1. Searching for bugs in a specific project is *extremely* cumbersome >and I am not even sure I got it right (first you need to put >openstack/project in the search bar, wait and click it. Then you add >the term you are looking for. I have genuinely no idea if I get all >the issues I was looking for or not as it is not obvious on what >fields this search is performed > 2. Advanced search is either very well hidden or not existant yet? >E.g. how do you search for bugs filed by someone or over a certain >release, or just generally more complex searches which are super >useful in order to avoid filing duplicate bugs. > > I think Zane's additional list also matches my experience very well: > http://lists.openstack.org/pipermail/openstack-dev/2018-June/131365.html > > So my take is that a migration atm is a bit premature and I would > postpone it at least to Stein. > Given that my original request was to try and do it prior to M2 and that's past, I think I'd also side with waiting until early Stein to continue. Let's focus on the Rocky work and push this to early Stein instead. I'll talk about this in the next IRC meeting if anyone wishes to discuss further. Thanks, -Alex > Thanks, > Michele > >> Thanks, >> >> On Tue, May 15, 2018 at 7:53 AM, Alex Schultz wrote: >> >> > Bumping this up so folks can review this. It was mentioned in this >> > week's meeting that it would be a good idea for folks to take a look >> > at Storyboard to get familiar with it. The upstream docs have been >> > updated[0] to point to the differences when dealing with proposed >> > patches. Please take some time to review this and raise any >> > concerns/issues now. >> > >> > Thanks, >> > -Alex >> > >> > [0] https://docs.openstack.org/infra/manual/developers.html# >> > development-workflow >> > >> > On Wed, May 9, 2018 at 1:24 PM, Alex Schultz wrote: >> > > Hello tripleo folks, >> > > >> > > So we've been experimenting with migrating some squads over to >> > > storyboard[0] but this seems to be causing more issues than perhaps >> > > it's worth. Since the upstream community would like to standardize on >> > > Storyboard at some point, I would propose that we do a cut over of all >> > > the tripleo bugs/blueprints from Launchpad to Storyboard. >> > > >> > > In the irc meeting this week[1], I asked that the tripleo-ci team make >> > > sure the existing scripts that we use to monitor bugs for CI support >> > > Storyboard. I would consider this a prerequisite for the migration. >> > > I am thinking it would be beneficial to get this done before or as >> > > close to M2. >> > > >> > > Thoughts, concerns, etc? >> > > >> > > Thanks, >> > > -Alex >> > > >> > > [0] https://storyboard.openstack.org/#!/project_group/76 >> > > [1] http://eavesdrop.openstack.org/meetings/tripleo/2018/ >> > tripleo.2018-05-08-14.00.log.html#l-42 >> > >> > __ >> > 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 >> > >> >> >> >> -- >> Emilien Macchi > >> __ >> 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 > > > -- > Michele Baldessari > C2
Re: [openstack-dev] [tripleo] Migration to Storyboard
On Mon, May 21, 2018 at 01:58:26PM -0700, Emilien Macchi wrote: > During the Storyboard session today: > https://etherpad.openstack.org/p/continuing-the-migration-lp-sb > > We mentioned that TripleO would continue to migrate during Rocky cycle. > Like Alex mentioned in this thread, we need to migrate the scripts used by > the CI squad so they work with SB. > Once this is done, we'll proceed to the full migration of all blueprints > and bugs into tripleo-common project in SB. > Projects like tripleo-validations, tripleo-ui (more?) who have 1:1 mapping > between their "name" and project repository could use a dedicated project > in SB, although we need to keep things simple for our users so they know > where to file a bug without confusion. > We hope to proceed during Rocky but it'll probably take some time to update > our scripts and documentation, also educate our community to use the tool, > so we expect the Stein cycle the first cycle where we actually consume SB. > > I really wanted to thank the SB team for their patience and help, TripleO > is big and this migration hasn't been easy but we'll make it :-) Having used storyboard for the first time today to file a bug^Wstory in heat, I'd like to raise a couple of concerns on this migration. And by all means, if I just missed to RTFM, feel free to point me in the right direction. 1. Searching for bugs in a specific project is *extremely* cumbersome and I am not even sure I got it right (first you need to put openstack/project in the search bar, wait and click it. Then you add the term you are looking for. I have genuinely no idea if I get all the issues I was looking for or not as it is not obvious on what fields this search is performed 2. Advanced search is either very well hidden or not existant yet? E.g. how do you search for bugs filed by someone or over a certain release, or just generally more complex searches which are super useful in order to avoid filing duplicate bugs. I think Zane's additional list also matches my experience very well: http://lists.openstack.org/pipermail/openstack-dev/2018-June/131365.html So my take is that a migration atm is a bit premature and I would postpone it at least to Stein. Thanks, Michele > Thanks, > > On Tue, May 15, 2018 at 7:53 AM, Alex Schultz wrote: > > > Bumping this up so folks can review this. It was mentioned in this > > week's meeting that it would be a good idea for folks to take a look > > at Storyboard to get familiar with it. The upstream docs have been > > updated[0] to point to the differences when dealing with proposed > > patches. Please take some time to review this and raise any > > concerns/issues now. > > > > Thanks, > > -Alex > > > > [0] https://docs.openstack.org/infra/manual/developers.html# > > development-workflow > > > > On Wed, May 9, 2018 at 1:24 PM, Alex Schultz wrote: > > > Hello tripleo folks, > > > > > > So we've been experimenting with migrating some squads over to > > > storyboard[0] but this seems to be causing more issues than perhaps > > > it's worth. Since the upstream community would like to standardize on > > > Storyboard at some point, I would propose that we do a cut over of all > > > the tripleo bugs/blueprints from Launchpad to Storyboard. > > > > > > In the irc meeting this week[1], I asked that the tripleo-ci team make > > > sure the existing scripts that we use to monitor bugs for CI support > > > Storyboard. I would consider this a prerequisite for the migration. > > > I am thinking it would be beneficial to get this done before or as > > > close to M2. > > > > > > Thoughts, concerns, etc? > > > > > > Thanks, > > > -Alex > > > > > > [0] https://storyboard.openstack.org/#!/project_group/76 > > > [1] http://eavesdrop.openstack.org/meetings/tripleo/2018/ > > tripleo.2018-05-08-14.00.log.html#l-42 > > > > __ > > 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 > > > > > > -- > Emilien Macchi > __ > 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 -- Michele Baldessari C2A5 9DA3 9961 4FFB E01B D0BC DDD4 DCCB 7515 5C6D __ 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] [tripleo] Migration to Storyboard
During the Storyboard session today: https://etherpad.openstack.org/p/continuing-the-migration-lp-sb We mentioned that TripleO would continue to migrate during Rocky cycle. Like Alex mentioned in this thread, we need to migrate the scripts used by the CI squad so they work with SB. Once this is done, we'll proceed to the full migration of all blueprints and bugs into tripleo-common project in SB. Projects like tripleo-validations, tripleo-ui (more?) who have 1:1 mapping between their "name" and project repository could use a dedicated project in SB, although we need to keep things simple for our users so they know where to file a bug without confusion. We hope to proceed during Rocky but it'll probably take some time to update our scripts and documentation, also educate our community to use the tool, so we expect the Stein cycle the first cycle where we actually consume SB. I really wanted to thank the SB team for their patience and help, TripleO is big and this migration hasn't been easy but we'll make it :-) Thanks, On Tue, May 15, 2018 at 7:53 AM, Alex Schultz wrote: > Bumping this up so folks can review this. It was mentioned in this > week's meeting that it would be a good idea for folks to take a look > at Storyboard to get familiar with it. The upstream docs have been > updated[0] to point to the differences when dealing with proposed > patches. Please take some time to review this and raise any > concerns/issues now. > > Thanks, > -Alex > > [0] https://docs.openstack.org/infra/manual/developers.html# > development-workflow > > On Wed, May 9, 2018 at 1:24 PM, Alex Schultz wrote: > > Hello tripleo folks, > > > > So we've been experimenting with migrating some squads over to > > storyboard[0] but this seems to be causing more issues than perhaps > > it's worth. Since the upstream community would like to standardize on > > Storyboard at some point, I would propose that we do a cut over of all > > the tripleo bugs/blueprints from Launchpad to Storyboard. > > > > In the irc meeting this week[1], I asked that the tripleo-ci team make > > sure the existing scripts that we use to monitor bugs for CI support > > Storyboard. I would consider this a prerequisite for the migration. > > I am thinking it would be beneficial to get this done before or as > > close to M2. > > > > Thoughts, concerns, etc? > > > > Thanks, > > -Alex > > > > [0] https://storyboard.openstack.org/#!/project_group/76 > > [1] http://eavesdrop.openstack.org/meetings/tripleo/2018/ > tripleo.2018-05-08-14.00.log.html#l-42 > > __ > 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 > -- Emilien Macchi __ 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] [tripleo] Migration to Storyboard
Bumping this up so folks can review this. It was mentioned in this week's meeting that it would be a good idea for folks to take a look at Storyboard to get familiar with it. The upstream docs have been updated[0] to point to the differences when dealing with proposed patches. Please take some time to review this and raise any concerns/issues now. Thanks, -Alex [0] https://docs.openstack.org/infra/manual/developers.html#development-workflow On Wed, May 9, 2018 at 1:24 PM, Alex Schultz wrote: > Hello tripleo folks, > > So we've been experimenting with migrating some squads over to > storyboard[0] but this seems to be causing more issues than perhaps > it's worth. Since the upstream community would like to standardize on > Storyboard at some point, I would propose that we do a cut over of all > the tripleo bugs/blueprints from Launchpad to Storyboard. > > In the irc meeting this week[1], I asked that the tripleo-ci team make > sure the existing scripts that we use to monitor bugs for CI support > Storyboard. I would consider this a prerequisite for the migration. > I am thinking it would be beneficial to get this done before or as > close to M2. > > Thoughts, concerns, etc? > > Thanks, > -Alex > > [0] https://storyboard.openstack.org/#!/project_group/76 > [1] > http://eavesdrop.openstack.org/meetings/tripleo/2018/tripleo.2018-05-08-14.00.log.html#l-42 __ 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] [tripleo] Migration to Storyboard
On Wed, May 9, 2018 at 2:20 PM, Wesley Hayutin wrote: > > > On Wed, May 9, 2018 at 3:25 PM Alex Schultz wrote: >> >> Hello tripleo folks, >> >> So we've been experimenting with migrating some squads over to >> storyboard[0] but this seems to be causing more issues than perhaps >> it's worth. Since the upstream community would like to standardize on >> Storyboard at some point, I would propose that we do a cut over of all >> the tripleo bugs/blueprints from Launchpad to Storyboard. >> >> In the irc meeting this week[1], I asked that the tripleo-ci team make >> sure the existing scripts that we use to monitor bugs for CI support >> Storyboard. I would consider this a prerequisite for the migration. >> I am thinking it would be beneficial to get this done before or as >> close to M2. >> >> Thoughts, concerns, etc? > > > Just clarifying. You would like to have the tooling updated by M2, which is > fine I think. However squads are not expected to change all their existing > procedures by M2 correct? I'm concerned about migrating our current kanban > boards to storyboard by M2. > I'm talking about tooling (irc bot/monitoring) and launchpad migration complete by m2. Any other boards can wait until squads want to move over. Thanks, -Alex > Thanks > >> >> >> Thanks, >> -Alex >> >> [0] https://storyboard.openstack.org/#!/project_group/76 >> [1] >> http://eavesdrop.openstack.org/meetings/tripleo/2018/tripleo.2018-05-08-14.00.log.html#l-42 >> >> __ >> 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 > __ 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] [tripleo] Migration to Storyboard
On Wed, May 9, 2018 at 3:25 PM Alex Schultz wrote: > Hello tripleo folks, > > So we've been experimenting with migrating some squads over to > storyboard[0] but this seems to be causing more issues than perhaps > it's worth. Since the upstream community would like to standardize on > Storyboard at some point, I would propose that we do a cut over of all > the tripleo bugs/blueprints from Launchpad to Storyboard. > > In the irc meeting this week[1], I asked that the tripleo-ci team make > sure the existing scripts that we use to monitor bugs for CI support > Storyboard. I would consider this a prerequisite for the migration. > I am thinking it would be beneficial to get this done before or as > close to M2. > > Thoughts, concerns, etc? > Just clarifying. You would like to have the tooling updated by M2, which is fine I think. However squads are not expected to change all their existing procedures by M2 correct? I'm concerned about migrating our current kanban boards to storyboard by M2. Thanks > > Thanks, > -Alex > > [0] https://storyboard.openstack.org/#!/project_group/76 > [1] > http://eavesdrop.openstack.org/meetings/tripleo/2018/tripleo.2018-05-08-14.00.log.html#l-42 > > __ > 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
[openstack-dev] [tripleo] Migration to Storyboard
Hello tripleo folks, So we've been experimenting with migrating some squads over to storyboard[0] but this seems to be causing more issues than perhaps it's worth. Since the upstream community would like to standardize on Storyboard at some point, I would propose that we do a cut over of all the tripleo bugs/blueprints from Launchpad to Storyboard. In the irc meeting this week[1], I asked that the tripleo-ci team make sure the existing scripts that we use to monitor bugs for CI support Storyboard. I would consider this a prerequisite for the migration. I am thinking it would be beneficial to get this done before or as close to M2. Thoughts, concerns, etc? Thanks, -Alex [0] https://storyboard.openstack.org/#!/project_group/76 [1] http://eavesdrop.openstack.org/meetings/tripleo/2018/tripleo.2018-05-08-14.00.log.html#l-42 __ 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