*** lbragstad has joined #openstack-tc | 00:06 | |
*** mriedem has quit IRC | 00:06 | |
*** hongbin has quit IRC | 00:13 | |
*** kumarmn has joined #openstack-tc | 00:42 | |
*** mguiney has quit IRC | 00:43 | |
*** sdague has quit IRC | 00:44 | |
*** mguiney has joined #openstack-tc | 00:45 | |
fungi | tc-members: commence to officing | 01:01 |
---|---|---|
harlowja | tps reports due on entry | 01:12 |
SamYaple | yeaaaaa if we could not harlowja, that would be greeeeaaattt | 01:18 |
harlowja | mk | 01:18 |
fungi | harlowja: cover page optional? | 01:18 |
harlowja | nope, didn't u get the memo | 01:19 |
* fungi has half a mind to give harlowja a taste of his red swingline | 01:19 | |
* fungi thinks better of it | 01:20 | |
SamYaple | such a great movie | 01:20 |
SamYaple | always forget jennifer anniston is in that | 01:20 |
*** liujiong has joined #openstack-tc | 01:21 | |
*** kumarmn has quit IRC | 01:27 | |
*** purplerbot has quit IRC | 01:56 | |
*** purplerbot has joined #openstack-tc | 01:56 | |
*** mguiney has quit IRC | 02:14 | |
*** mguiney has joined #openstack-tc | 02:14 | |
*** kumarmn has joined #openstack-tc | 02:17 | |
*** kumarmn has quit IRC | 02:23 | |
*** liujiong has quit IRC | 03:26 | |
*** kumarmn has joined #openstack-tc | 03:51 | |
*** kumarmn has quit IRC | 04:09 | |
*** kumarmn has joined #openstack-tc | 04:11 | |
*** kumarmn has quit IRC | 04:16 | |
*** kumarmn has joined #openstack-tc | 04:37 | |
*** kumarmn has quit IRC | 04:41 | |
*** rosmaita has quit IRC | 04:56 | |
*** dklyle has quit IRC | 05:15 | |
*** alex_xu has quit IRC | 06:10 | |
*** alex_xu has joined #openstack-tc | 06:11 | |
*** mguiney has quit IRC | 07:45 | |
*** mguiney has joined #openstack-tc | 07:47 | |
*** jpich has joined #openstack-tc | 08:17 | |
*** chkumar|404 is now known as chandankumar | 08:22 | |
*** kumarmn has joined #openstack-tc | 09:10 | |
*** kumarmn has quit IRC | 09:14 | |
*** dtantsur|afk is now known as dtantsur | 09:26 | |
*** gcb has joined #openstack-tc | 09:39 | |
*** gcb has quit IRC | 11:05 | |
*** sdague has joined #openstack-tc | 11:27 | |
openstackgerrit | Ifat Afek proposed openstack/governance master: Update the status of Vitrage goals completion https://review.openstack.org/521445 | 11:31 |
*** dtantsur is now known as dtantsur|brb | 12:47 | |
*** rosmaita has joined #openstack-tc | 12:52 | |
ttx | Wouldn't mind a quick review of https://review.openstack.org/#/c/523860/ before merging it. | 12:53 |
ttx | (context: we need a job run to start publishing the ICS calendars in the right places) | 12:54 |
*** kumarmn has joined #openstack-tc | 13:11 | |
*** kumarmn has quit IRC | 13:15 | |
*** kumarmn has joined #openstack-tc | 13:20 | |
*** kumarmn has quit IRC | 13:25 | |
openstackgerrit | Doug Hellmann proposed openstack/governance master: stop linking to documentation from governance https://review.openstack.org/523195 | 13:26 |
dims | +1 ttx | 13:39 |
ttx | thanks all | 13:40 |
*** openstackstatus has quit IRC | 13:43 | |
*** openstack has joined #openstack-tc | 13:44 | |
*** ChanServ sets mode: +o openstack | 13:44 | |
*** openstackstatus has joined #openstack-tc | 13:45 | |
*** ChanServ sets mode: +v openstackstatus | 13:45 | |
*** mriedem has joined #openstack-tc | 13:51 | |
*** cdent has joined #openstack-tc | 14:10 | |
*** kumarmn has joined #openstack-tc | 14:20 | |
*** dtantsur|brb is now known as dtantsur | 14:24 | |
openstackgerrit | Thierry Carrez proposed openstack/governance master: Tags are applied to deliverables, or teams https://review.openstack.org/523886 | 14:37 |
*** hongbin has joined #openstack-tc | 14:40 | |
*** openstack has quit IRC | 14:46 | |
*** openstack has joined #openstack-tc | 14:50 | |
*** ChanServ sets mode: +o openstack | 14:50 | |
ttx | efried: +2 on the other one. Thanks for uncovering those | 14:50 |
efried | Thanks! | 14:51 |
ttx | It's the downside of documenting stuff... you need to keep it up to date | 14:51 |
efried | totally. | 14:51 |
efried | dhellmann Given ttx's desire to keep the project-team-guide non-project-specific, is there any other bug-related wiki content you feel it would be appropriate to move over? | 14:52 |
efried | I'll grant you I haven't read the *whole* wiki... | 14:52 |
ttx | efried: it's a good time travel experience! | 14:53 |
efried | Like I was going to hit https://wiki.openstack.org/wiki/BugTriage -- but that has a ton of project-specific links. | 14:53 |
efried | maybe I should quit while I'm ahead... | 14:54 |
*** cdent has quit IRC | 14:59 | |
*** marst has joined #openstack-tc | 15:06 | |
openstackgerrit | Lance Bragstad proposed openstack/governance master: Update policy goal for manila https://review.openstack.org/523906 | 15:32 |
*** cdent has joined #openstack-tc | 15:32 | |
cdent | zaneb: just reading your email about tempests tests | 16:26 |
zaneb | cdent: there's a lively discussion going on in #heat as well :) | 16:26 |
cdent | I sympathize/empathize/*ize with your confusion and concern | 16:26 |
cdent | just in case you want more confusion there’s also this: https://review.openstack.org/#/c/521602/ | 16:27 |
cdent | which is about where interop tests are supposed to go | 16:27 |
cdent | the fact that we’ve got this same name for thing that does interop testing, cloud verification, and integration tests is chaos | 16:27 |
zaneb | ah yes. we really should have figured that out *before* making a project-wide goal of where to put tests :/ | 16:27 |
smcginnis | cdent: ++ | 16:28 |
cdent | the assertion in the project wide goal was that anyone who was using a plugin was supposed to put that plugin in a different repo | 16:28 |
cdent | it didn’t get much further than that | 16:29 |
cdent | I tried to assert that if some peopel have to use plugins then everyone should | 16:29 |
cdent | but that didn’t float | 16:29 |
cdent | but now it sounds like, zaneb, that you’re getting a mixed message and only some tests need to move? | 16:29 |
mugsie | zaneb: do you have tests in tempest? | 16:30 |
zaneb | cdent: I'm getting that message, and that was apparently what was agreed at the PTG (I wasn't there) | 16:30 |
zaneb | mugsie: we used to, but I think they were all deleted. we now have them in a tempest plugin in the heat repo | 16:30 |
* cdent blinks | 16:30 | |
mugsie | cdent: look at interop meeting logs from yesterday | 16:31 |
mugsie | sorry, refstack | 16:31 |
zaneb | cdent: more importantly, I'm sending the message that some (most in our case) tests need to *not* move, even if that means they're not in a tempest plugin any more | 16:31 |
cdent | zaneb: that seems like a reasonable outcome | 16:33 |
cdent | actually strike that, I misread and don’t actually know what I think | 16:33 |
* cdent thinks | 16:33 | |
zaneb | cdent: btw a propos of mugsie's level-playing-field-for-plugins crusade, I present https://bugs.launchpad.net/python-openstackclient/+bug/1735016 | 16:33 |
openstack | Launchpad bug 1735016 in python-openstackclient "Plugin documentation is worthless" [Undecided,New] | 16:33 |
mugsie | I am confused by this line: | 16:34 |
mugsie | So from discussion on IRC today I learned that the plan agreed at the PTG was *not* to move all of heat_integrationtests to a separate repo, but just those tests that test the API and are likely to be used in the trademark program for verifying clouds. | 16:34 |
mugsie | that is the exact opposite of what I remember | 16:34 |
mugsie | my recolection is all API tests should be in a separate repo | 16:34 |
zaneb | mugsie: I wasn't there, so I'm only going on what I'm being told | 16:34 |
zaneb | http://eavesdrop.openstack.org/irclogs/%23heat/%23heat.2017-11-29.log.html#t2017-11-29T15:31:08 | 16:35 |
mugsie | zaneb: Yeah, I am just confuised aboiut what has changed | 16:35 |
smcginnis | I didn't think we were moving anything from openstack/tempest, just that openstack/$PROJECT tempest tests needed to move because of entry points or such. | 16:35 |
zaneb | smcginnis: right, this thread is only about Heat's in-tree tempest plugin | 16:36 |
mugsie | smcginnis: tempest already did a purge of things not in the "core" | 16:37 |
smcginnis | mugsie: Oh? I wasn't aware of that. | 16:37 |
zaneb | mugsie: so the issue for us is that all of our tests use the API, but only a tiny subset are designed to be 'API tests'. we're fine with that subset going in a separate, branchless plugin repo | 16:38 |
mugsie | smcginnis: http://eavesdrop.openstack.org/meetings/refstack/2017/refstack.2017-11-28-17.02.log.html#l-155 | 16:38 |
cdent | mugsie: I’ve struggled to extract meaning from the refstack log | 16:38 |
cdent | zaneb: is heat using gabbi without tempest these days or with or both? | 16:39 |
zaneb | cdent: with | 16:39 |
mugsie | zaneb: OK, that makes more sense | 16:39 |
zaneb | cdent: and that's the part that makes perfect sense to go into a separate branchless tempest plugin imho | 16:39 |
cdent | because they are effectively api verfication "scripts"? | 16:40 |
zaneb | yes | 16:40 |
zaneb | they check that the API doesn't change. it makes sense to run those across multiple branches | 16:41 |
* cdent nods | 16:41 | |
mugsie | ++ | 16:41 |
zaneb | I mean, we can and probably should have more and better tests of that stuff. but those are the ones we have at present | 16:41 |
zaneb | the other tests are designed to test internals for regressions. they just happen to do so by making API calls | 16:42 |
mugsie | well, for us, we moved a few out into the repo, and then started increasing coverage | 16:42 |
* cdent maintains a little personal fantasy of the trademark tests being written in gabbi | 16:42 | |
dtroyer | cdent: ++ is it time to reverse the sense here and have the trademark tests be the primary purpose of whatever code implements it, and _then_ use that in CI alongside tempest? | 16:43 |
cdent | that’s kinda what my thinking was with regard to putting them in their own plugin/repo | 16:45 |
mugsie | dtroyer: not a bad idea. | 16:45 |
cdent | once self-contained they can be and mean whatever they want | 16:45 |
cdent | when they are multiply-hosted and multply-meaning that’s harder to do | 16:45 |
dtroyer | but totally divorce it from Tempest. The co=opting of that is playing out in a way that cries for "stop the madness!" | 16:45 |
cdent | but the old canard of “who is going to do it” (in the log that mugsie pointed to earlier) is a concern | 16:46 |
dtroyer | of course, it's easier said than done without people to do the lifting | 16:46 |
dtroyer | jinx | 16:46 |
mugsie | I think #3 in the proposal is a good step to divorcing it, without a huge amount of technical work | 16:47 |
mugsie | a bit of political work though | 16:47 |
zaneb | +1 imho tempest should just be a test-running framework. there should be an out-of-tree 'openstack-trademark-tests' plugin that implements the trademark tests | 16:47 |
dtroyer | I'll shut up now, I'm having a hard enough time keeping up with things I want to do, much less everything that self-appointed critics want me to do too | 16:47 |
cdent | aw, I prefer it when dtroyer is not shut up | 16:47 |
mugsie | zaneb: could you comment on https://review.openstack.org/#/c/521602/ please ? just so we get a more divirse set of view points | 16:48 |
zaneb | sure | 16:48 |
openstackgerrit | Merged openstack/project-team-guide master: Port wiki bugs pages (1 of ?) https://review.openstack.org/523551 | 16:50 |
mugsie | and it looks less like mugsie is a drunk, walking down the road shouting at lamp posts | 16:50 |
cdent | I think I saw you on the street recently, but not sure, I was probably drunk | 16:50 |
mugsie | :) | 16:51 |
*** efried is now known as efried_rollin | 17:22 | |
*** jpich has quit IRC | 17:29 | |
zaneb | mugsie, cdent: added a comment on the review | 17:29 |
cdent | thanks | 17:30 |
mugsie | zaneb: thanks | 17:31 |
*** dtantsur is now known as dtantsur|afk | 18:10 | |
dhellmann | efried_rollin : the triage instructions seem like they'd be project-specific, so I agree it's probably best to quit while you're ahead. if we find more content, we can move it later | 18:22 |
*** david-lyle has joined #openstack-tc | 18:45 | |
*** david-lyle has quit IRC | 18:54 | |
*** diablo_rojo has quit IRC | 18:55 | |
*** diablo_rojo has joined #openstack-tc | 18:55 | |
*** david-lyle has joined #openstack-tc | 19:01 | |
*** david-lyle has quit IRC | 19:02 | |
*** david-lyle has joined #openstack-tc | 19:21 | |
*** david-lyle has quit IRC | 19:34 | |
*** david-lyle has joined #openstack-tc | 19:35 | |
*** rosmaita has quit IRC | 19:37 | |
*** rosmaita has joined #openstack-tc | 19:43 | |
*** david-lyle has quit IRC | 19:53 | |
*** david-lyle has joined #openstack-tc | 20:04 | |
*** efried_rollin is now known as efried | 20:07 | |
efried | dhellmann Ack. | 20:07 |
efried | dhellmann That change set merged; at what point do the changes show up on https://docs.openstack.org/project-team-guide/ ? (So I can update the wiki with the redirect) | 20:09 |
efried | ttx ^ | 20:12 |
openstackgerrit | Lance Bragstad proposed openstack/governance master: Update policy goal for aodh https://review.openstack.org/523979 | 20:33 |
*** david-lyle has quit IRC | 20:45 | |
*** david-lyle has joined #openstack-tc | 21:04 | |
*** bbrad has joined #openstack-tc | 21:14 | |
dhellmann | efried : they should have showed up shortly after the merge | 21:14 |
efried | dhellmann Here? https://docs.openstack.org/project-team-guide/bugs.html | 21:15 |
dhellmann | yeah | 21:15 |
dhellmann | unless publishing is broken | 21:15 |
dhellmann | :-( | 21:15 |
dhellmann | efried : the logs for the publish job are in http://logs.openstack.org/d3/d3a367920bc67cc0254927494f6f4ab682aac72e/post/publish-openstack-sphinx-docs-direct/5e71e35/job-output.txt.gz | 21:16 |
dhellmann | I don't see a failure, but it doesn't seem to have updated that page | 21:16 |
dhellmann | that's something to bring up with the infra team, to figure out what's going on there | 21:16 |
dhellmann | your new file does show up in the collected files list: http://logs.openstack.org/d3/d3a367920bc67cc0254927494f6f4ab682aac72e/post/publish-openstack-sphinx-docs-direct/5e71e35/job-output.txt.gz#_2017-11-29_16_58_54_982305 | 21:17 |
efried | Is "unreachable" something to worry about? | 21:18 |
dhellmann | likely | 21:22 |
dhellmann | the infra team is going to be more help with that :-/ | 21:22 |
efried | Will ask there. Thanks dhellmann | 21:23 |
dhellmann | I'm familiar with some of the obvious errors, but I don't see one here | 21:23 |
dhellmann | sorry I can't be more immediate help | 21:23 |
dhellmann | lbragstad : if you're OK with this keystoneauth release I can approve it - https://review.openstack.org/#/c/523515/ | 21:27 |
dhellmann | oops, wrong channel | 21:27 |
* dhellmann needs cursor-follows-eyes mode | 21:27 | |
openstackgerrit | Sean McGinnis proposed openstack/governance master: Mark Cinder policy in code as done https://review.openstack.org/523998 | 21:51 |
*** bbrad has quit IRC | 21:58 | |
dtroyer | +1 on cursor-follows-eyes, although I worry about what else "they" will do with that ability | 22:00 |
*** cdent has quit IRC | 22:03 | |
EmilienM | lbragstad: thanks for all the work on the goals | 22:53 |
EmilienM | lbragstad: I'm wondering if you tried to get projects updating themselves the governance | 22:53 |
EmilienM | lbragstad: or if you agreed to do it yourself | 22:53 |
lbragstad | EmilienM: i've certainly encouraged them to propose the updates but i've defaulted to stepping in when needed | 22:58 |
EmilienM | ok | 22:58 |
EmilienM | lbragstad: for the next champions, we might investigate a workflow where the champion doesn't have to do it and the projects know how to do it themselves in a simple manner | 22:59 |
EmilienM | it can be an etherpad or a gerrit topic | 22:59 |
lbragstad | yeah - that'd be easier to tc to instead of having to review all of them | 22:59 |
EmilienM | and then, once per milestone, we update governance | 22:59 |
EmilienM | it's not for TC imho | 23:00 |
EmilienM | it takes me 1 min to review | 23:00 |
EmilienM | it's more for champions | 23:00 |
lbragstad | i thought the storyboard integration sounded nice | 23:00 |
EmilienM | yeah | 23:00 |
lbragstad | since we could track everything in a single place | 23:00 |
EmilienM | imho, a champion should be here for socializing the goal and talk with projects | 23:00 |
lbragstad | when the last commit merges, things are updated in storyboard, and the completion docs are done automatically | 23:01 |
EmilienM | and projects understand the goal, implement it and update governance or storyboard themselves | 23:01 |
EmilienM | cool | 23:01 |
lbragstad | yeah - that'd be nice | 23:01 |
EmilienM | diablo_rojo: hello :-) | 23:05 |
EmilienM | diablo_rojo: I was talking with tripleo folks and we were wondering if any project already migrated from Launchpad to StoryBoard, and if yes, who are they, we want to ask them feedback and try ourselves | 23:05 |
lbragstad | EmilienM: persia was saying the bulk migration is happening earlying 2018 | 23:06 |
lbragstad | early* | 23:06 |
EmilienM | lbragstad: do we know how that works? which feature are we loosing etc | 23:06 |
EmilienM | because we have tools relying on launchpad now | 23:06 |
EmilienM | I wasn't aware about a bulk migration | 23:07 |
EmilienM | which projects? all? | 23:07 |
lbragstad | that's how i interpreted it when i spoke with persia at the PTG, but i'm sure he'll be able to correct me | 23:07 |
diablo_rojo | EmilienM, Refstack, Octavia, Craton, Monasca. | 23:21 |
EmilienM | diablo_rojo: ok, thanks | 23:22 |
diablo_rojo | EmilienM, getting ready to migrate Kolla too. Just waiting for them to ask final questions and then pick a date. | 23:22 |
diablo_rojo | EmilienM, no problem :) | 23:22 |
EmilienM | diablo_rojo: is the process documented? | 23:22 |
EmilienM | diablo_rojo: like, do we close bugs on launchpad during migration? | 23:22 |
diablo_rojo | https://docs.openstack.org/infra/storyboard/migration.html | 23:22 |
EmilienM | diablo_rojo: what do we need to change on our side? (is Closes-Bug: still work?) | 23:22 |
EmilienM | etc | 23:22 |
EmilienM | ok i need to read that | 23:22 |
EmilienM | thanks | 23:22 |
diablo_rojo | We have a script that copies over all the bugs | 23:23 |
diablo_rojo | No problem :) | 23:23 |
EmilienM | diablo_rojo: what happens to the bugs migrated? are they closes in Launchpad? | 23:24 |
diablo_rojo | I am trying to figure out with Launchpad's painful apis to modify our migration script to post links to the new storyboard stories on the old launchpad bugs. | 23:25 |
diablo_rojo | EmilienM, ^^ | 23:25 |
EmilienM | that would be awesome | 23:26 |
EmilienM | after a migration, what happens to the bugs in Launchpad? | 23:26 |
EmilienM | they aren't touched at all? | 23:26 |
EmilienM | diablo_rojo: ^ | 23:27 |
diablo_rojo | The history stays there. The project needs to disable the ability to report new bugs and should also update their docs to point to storyboard for new bugs. Should let users know too. | 23:28 |
EmilienM | diablo_rojo: ok | 23:40 |
EmilienM | diablo_rojo: and is the status of the bugs updated after a migration? | 23:40 |
EmilienM | diablo_rojo: for example, if a bug is "In progress", when migrated, the bug is also "In progress"? | 23:40 |
*** kumarmn has quit IRC | 23:41 | |
diablo_rojo | I think originally they weren't but I vaguely remember someone fixing that.. fungi do you remember? | 23:41 |
fungi | no, the import script doesn't authenticate to lp and makes no changes to any bugs | 23:42 |
diablo_rojo | But do the statuses persist after migration? | 23:42 |
fungi | we've discussed modifying it to leave comments in all imported bugs with links to the equivalent stories in sb, but the lp api is very unreliable so i don't think that would scale terribly well | 23:43 |
fungi | the import script leaves in progress bugs in lp as in progress, yes | 23:43 |
diablo_rojo | fungi, even figuring out how to use the apis to authenticate to comment on the lp bugs hasn't been fun. | 23:44 |
diablo_rojo | writing the comment isn't hard, its the step before that isn't great.. | 23:44 |
fungi | well, yeah, you have to script openid auth | 23:44 |
fungi | it's a terrible method of authenticating tools | 23:45 |
diablo_rojo | EmilienM, tldr is yes, the statuses persist after migration in sb | 23:45 |
fungi | fine for authenticating web browsers, but not really anything else | 23:45 |
EmilienM | diablo_rojo: ok cool. | 23:45 |
EmilienM | diablo_rojo: we have a TON of bugs | 23:45 |
EmilienM | diablo_rojo: I don't want to spend a weekend manually updating them ;-) | 23:46 |
EmilienM | (well we have scripts etc) | 23:46 |
diablo_rojo | EmilienM, WHAT!? You mean you would rather be out flying a plane than glued to a screen spending quality time with launchpad? | 23:46 |
* diablo_rojo is suprised | 23:46 | |
EmilienM | lol | 23:46 |
EmilienM | diablo_rojo: I would actually do the triage from the plane | 23:47 |
EmilienM | and before mention it's because diablo_rojo told me to do so | 23:47 |
EmilienM | :P | 23:47 |
diablo_rojo | It wouldn't be a problem if there werent so many bugs EmilienM ;) | 23:47 |
fungi | diablo_rojo: anyway, if you write something to leave comments or update statuses on lp bugs en masse, expect it to be an order of magnitude slower (at least) than querying it in a read-only fashion, and also expect many, many, many of those api calls to just time out with an incomprehensible error from the api | 23:48 |
diablo_rojo | fungi, that sounds like something I don't really want to touch with a ten foot pole.. | 23:48 |
*** marst has quit IRC | 23:49 | |
fungi | because lp seems to block synchronously while attempting to send e-mail notifications to all subscribers of a bug, which for lots of those bugs on more active projects can easily be in the hundreds and hundreds of recipients | 23:49 |
diablo_rojo | These all sound likek very compelling reasons to get the hell away from lauunchpad.. | 23:50 |
fungi | instead we mostly rely on closing out the bug tracker in lp to hide the bug reporting interface and no longer provide an index of bugs for that project. couple that with a url to the new bug tracker in the project description in lp and it's seemed to work fine for the most part | 23:50 |
fungi | people can still update bugs for those projects in lp _if_ they can find them (e.g. through web search engines), but that seems to mostly not happen | 23:51 |
fungi | and they at least can't open new bugs | 23:51 |
diablo_rojo | The index disappearing is a really easy way to keep people from finding things. | 23:52 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!