| *** alex_xu has quit IRC | 00:40 | |
| *** alex_xu has joined #openstack-tc | 00:41 | |
| *** edmondsw has joined #openstack-tc | 01:04 | |
| *** edmondsw has quit IRC | 01:08 | |
| *** edmondsw has joined #openstack-tc | 02:52 | |
| *** edmondsw has quit IRC | 02:57 | |
| *** diablo_rojo has joined #openstack-tc | 04:06 | |
| *** edmondsw has joined #openstack-tc | 04:40 | |
| *** edmondsw has quit IRC | 04:44 | |
| *** flwang1 has quit IRC | 04:54 | |
| *** ricolin has joined #openstack-tc | 04:59 | |
| *** diablo_rojo has quit IRC | 06:25 | |
| *** edmondsw has joined #openstack-tc | 06:28 | |
| *** edmondsw has quit IRC | 06:33 | |
| *** jpich has joined #openstack-tc | 06:58 | |
| *** tosky has joined #openstack-tc | 07:35 | |
| *** ricolin has quit IRC | 07:35 | |
| *** ricolin has joined #openstack-tc | 07:54 | |
| *** edmondsw has joined #openstack-tc | 08:16 | |
| *** edmondsw has quit IRC | 08:21 | |
| *** flwang1 has joined #openstack-tc | 08:30 | |
| *** rosmaita has joined #openstack-tc | 09:56 | |
| *** cdent has joined #openstack-tc | 10:17 | |
| *** cdent has quit IRC | 10:41 | |
| *** jaypipes has joined #openstack-tc | 12:06 | |
| *** cdent has joined #openstack-tc | 12:14 | |
| *** ricolin has quit IRC | 12:17 | |
| *** mriedem has joined #openstack-tc | 12:23 | |
| *** edmondsw has joined #openstack-tc | 12:24 | |
| *** edmondsw has quit IRC | 12:29 | |
| *** edmondsw has joined #openstack-tc | 12:31 | |
| *** edmondsw has quit IRC | 12:35 | |
| *** edmondsw has joined #openstack-tc | 12:37 | |
| *** edmondsw has quit IRC | 12:42 | |
| *** edmondsw has joined #openstack-tc | 12:45 | |
| *** edmondsw has quit IRC | 12:49 | |
| *** edmondsw has joined #openstack-tc | 12:51 | |
| *** edmondsw has quit IRC | 12:53 | |
| *** edmondsw has joined #openstack-tc | 12:53 | |
| *** lbragstad has joined #openstack-tc | 13:37 | |
| *** ricolin has joined #openstack-tc | 13:45 | |
| *** hongbin has joined #openstack-tc | 13:51 | |
| dims | o/ | 14:17 |
|---|---|---|
| cdent | o/ | 14:17 |
| dims | fyi, ASF annual report - https://s3.amazonaws.com/files-dist/AnnualReports/FY2018%20Annual%20Report.pdf | 14:23 |
| *** pabelanger has quit IRC | 14:33 | |
| *** pabelanger has joined #openstack-tc | 14:33 | |
| scas | taking some more time to look at how releases are being done in openstack-the-ecosystem, i don't see any real issue as to why chef can't use the releases repository with its own publishing mechanism. "i don't know what i don't know" applies especially true when working in this context. my trepidation has been largely out of lack of clarity. until a few minutes ago, i wasn't able to even say whether or | 14:41 |
| scas | not moving chef's release process would work. i would be contributing to the amount that needs to be reviewed. if that's not a problem, then i don't have a problem with it | 14:41 |
| dhellmann | scas : there's no reason chef repos couldn't have their own release job | 14:59 |
| dhellmann | the requirement is to have the tag application reviewed, not to use one of the existing release jobs to publish tarballs | 15:00 |
| dhellmann | we just need to wire all the pieces together -- puppet and ansible already do something like that | 15:01 |
| scas | yep. that's what i've been sifting through gerrit to better understand. i don't see any major impediments after seeing what i've seen | 15:02 |
| scas | kolla publishes to dockerhub, which is analogous to my supermarket. i've come across the incantation to not publish tarballs, which works for me | 15:04 |
| dhellmann | having the supermarket publishing automated would be good, but it doesn't have to happen all in one step | 15:05 |
| scas | no, it doesn't. it's still a manual task right now, but i'll want it on a periodic | 15:06 |
| scas | but i think that's all a me-thing | 15:06 |
| scas | ENOTIME excepting, i should be able to find what i need there | 15:07 |
| dhellmann | why periodic? | 15:07 |
| scas | supermarket is a mirror like github. i could have it done after every version bump, but that feels like more work | 15:08 |
| dhellmann | ah. ok. we usually treat tagging releases as the thing that triggers artifact uploads. if you're going to do it periodically, that's still a very different model than any of the other projects | 15:09 |
| scas | 'simpsons^Wkolla did it' is my excuse. it can be done one-shot, which is more or less how it's done now | 15:10 |
| dhellmann | I think we're treating the kolla images as distinct from the kolla software | 15:11 |
| *** cdent has quit IRC | 15:13 | |
| dhellmann | but you'd have to talk to smcginnis about that | 15:13 |
| fungi | the reason kolla is publishing snapshots is to prevent them from looking like officially supported versions, due to https://governance.openstack.org/tc/resolutions/20170530-binary-artifacts.html | 15:20 |
| fungi | chef would presumably be making source-based releases | 15:21 |
| dhellmann | ah, right | 15:21 |
| cmurphy | diablo_rojo_phon: persia: fungi: I see there are no dates given for ptl elections on https://releases.openstack.org/rocky/schedule.html , should there be? aren't those coming up? | 15:22 |
| cmurphy | one of my health-check projects is wondering | 15:22 |
| dhellmann | https://governance.openstack.org/tc/reference/charter.html#election-for-ptl-seats | 15:23 |
| dhellmann | it will be closer to the PTL and end of cycle | 15:23 |
| jroll | it's R-7 already :) | 15:26 |
| cmurphy | ah somehow my brain thought it was R-5 already | 15:26 |
| scas | fungi: the artifacts on supermarket would be references back to the git projects as well as exports from supermarket as tarballs, but those tarballs would be outside the release process | 15:26 |
| jroll | feels like we should at least be setting dates by now | 15:26 |
| fungi | i agree, we're probably coming up on when we should be preparing for the next round of elections but i'm standing for a seat on the tc again so i won't be an election official at least for the tc election (which is going to be fairly adjacent to the ptl elections) | 15:27 |
| scas | i mean, the tool itself, stove, creates those tarballs and publishes them | 15:30 |
| scas | i had to do a code dive for clarity | 15:31 |
| fungi | but they're not compiled binaries integrating components other than what the chef team is producing, right? | 15:34 |
| scas | no | 15:34 |
| fungi | so effectively a source-based release | 15:34 |
| scas | in that definition, yes | 15:40 |
| fungi | more to the point, the concerns in the binary artifacts resolution aren't applicable for chef releases | 15:42 |
| pabelanger | dhellmann: left a comment on https://review.openstack.org/580495/ using tox for docs builds | 16:01 |
| pabelanger | given the history of tox -edocs, interesting we are considering reverting to it | 16:02 |
| dhellmann | pabelanger : http://lists.openstack.org/pipermail/openstack-dev/2018-July/132025.html | 16:03 |
| dhellmann | in particular my response to zaneb's similar question: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132074.html | 16:04 |
| pabelanger | thanks! I missed that | 16:05 |
| dhellmann | np. At least since there are questions I know people are reading my email. ;-) | 16:09 |
| *** dklyle has joined #openstack-tc | 16:23 | |
| mnaser | it sure would be nice if tox had some sort of inheritence model or something | 16:24 |
| mnaser | that way the pti is defined in one repo | 16:24 |
| dhellmann | that's an interesting idea | 16:27 |
| dhellmann | it sort of puts us back in a state where it would be difficult to change the jobs without breaking things, though, because of the centralization | 16:28 |
| mnaser | well changing behaviour for doc jobs shouldn't really break if you're doing things the right way | 16:38 |
| mnaser | anyways | 16:38 |
| mnaser | i'm torn on the adjutant stuff, i kinda was starting to be with it until I read " E.g. for Catalyst I'm right now building a custom Adjutant API for managing credit cards in our system/stripe, while yes the API is user accessible and requires Keystone auth" | 16:39 |
| mnaser | and again that totally sounds like that should be it's own service built by/for/only catalyst, dunno why it has to be part of adjutant | 16:40 |
| mnaser | if everyone is going to add their own logic to it, whats the actual point of it because no one will have any shared logic | 16:40 |
| *** jpich has quit IRC | 16:52 | |
| scas | 'stove' has an option to not tag git repos, which is how i've been invoking it all along. it looks like i can have it exist as a playbook or a rake task with the same behavior | 17:06 |
| *** ricolin has quit IRC | 17:09 | |
| *** cdent has joined #openstack-tc | 17:16 | |
| dhellmann | scas : that sounds like it would be useful for building the job you want | 17:17 |
| dhellmann | mnaser : yeah, I took that to mean they were going to use adjutant as a framework for building those APIs rather than adding them to adjutant itself | 17:17 |
| scas | dhellmann: yeah, it's pretty much my only tool for publishing artifacts. i haven't done the wiring yet, but it *seems* doable | 17:23 |
| openstackgerrit | Doug Hellmann proposed openstack/governance master: update the pti to use tox for building docs https://review.openstack.org/580495 | 17:23 |
| openstackgerrit | Doug Hellmann proposed openstack/governance master: add check_review_status.py https://review.openstack.org/579953 | 17:30 |
| *** annabelleB has joined #openstack-tc | 18:01 | |
| *** mriedem1 has joined #openstack-tc | 18:19 | |
| *** annabelleB has quit IRC | 18:19 | |
| *** mriedem has quit IRC | 18:21 | |
| *** annabelleB has joined #openstack-tc | 18:22 | |
| *** mriedem1 is now known as mriedem | 18:22 | |
| *** annabelleB has quit IRC | 18:41 | |
| fungi | mnaser: yes, that basically echoes the concerns i reraised in my comment on the adjutant review. if nobody has the same actual api methods exposed, there will basically be no user-facing community forming around it (no real ecosystem client integration, no single sdk for it, et cetera) | 18:45 |
| *** annabelleB has joined #openstack-tc | 18:56 | |
| fungi | basically if you want to use the catalyst cloud payment api, you need to install catalyst-adjutantclient or catalyst-adjutantsdk | 18:58 |
| fungi | which presumably catalyst cloud's customer knowledge base or help desk will direct you to and document how it's used | 18:59 |
| * fungi recalls rackspace directing customers to install their authentication client/library back when they didn't run keystone | 19:01 | |
| fungi | not a user-friendly experience | 19:02 |
| *** tosky has quit IRC | 19:23 | |
| *** flwang1 has quit IRC | 19:35 | |
| *** annabelleB has quit IRC | 19:42 | |
| *** annabelleB has joined #openstack-tc | 19:48 | |
| *** annabelleB has quit IRC | 19:49 | |
| *** annabelleB has joined #openstack-tc | 19:50 | |
| *** dklyle has quit IRC | 19:52 | |
| *** dklyle has joined #openstack-tc | 20:35 | |
| *** e0ne has joined #openstack-tc | 20:36 | |
| *** annabelleB has quit IRC | 20:45 | |
| *** e0ne has quit IRC | 21:31 | |
| *** hongbin has quit IRC | 22:19 | |
| *** cdent has quit IRC | 22:47 | |
| *** ianychoi_ has joined #openstack-tc | 23:21 | |
| *** diablo_rojo_phon has quit IRC | 23:22 | |
| *** diablo_rojo_phon has joined #openstack-tc | 23:24 | |
| *** ianychoi has quit IRC | 23:25 | |
| *** edmondsw has quit IRC | 23:26 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!