Tuesday, 2017-03-21

*** Syed__ has quit IRC00:25
*** VW has joined #craton02:21
*** VW has quit IRC04:17
*** VW has joined #craton04:17
*** VW has quit IRC05:32
*** VW has joined #craton05:33
openstackgerritTao Li proposed openstack/craton master: Remove log translations  https://review.openstack.org/44783305:50
*** VW has quit IRC06:37
openstackgerritTao Li proposed openstack/craton master: Remove log translations  https://review.openstack.org/44783308:02
openstackgerritTao Li proposed openstack/craton master: Remove log translations  https://review.openstack.org/44783308:04
-openstackstatus- NOTICE: Wiki is broken with database problems, we are working to resolve it08:28
*** ChanServ changes topic to "Wiki is broken with database problems, we are working to resolve it"08:28
*** ChanServ changes topic to "Summit talk: https://www.youtube.com/watch?v=Q-sf12SDR3M || Logs: http://eavesdrop.openstack.org/irclogs/%23craton/latest.log.html || Mon 1500 UTC in #openstack-meeting-4 || Client/ecosystem Tues 1700 UTC || Core Thur 1700 UTC || Resources: https://etherpad.openstack.org/p/Fleet_Management"08:37
-openstackstatus- NOTICE: Wiki problems have been fixed, it's up and running08:37
*** openstackgerrit has quit IRC09:03
suloo/10:09
*** openstackgerrit has joined #craton10:24
openstackgerritSulochan Acharya proposed openstack/craton master: Create user under project_id passed in request  https://review.openstack.org/44697210:24
*** VW has joined #craton12:08
*** VW has quit IRC12:16
*** VW has joined #craton12:47
sigmavirusbelated mornings12:53
openstackgerritMerged openstack/craton master: Include project_id only where needed  https://review.openstack.org/44693813:03
thomasemo/13:17
thomasemSo, where did we want to enumerate retro topics into the future, so folks know where to go when something occurs to them that they wish to discuss in retro? The main meeting etherpad?13:18
openstackgerritAntony Messerli proposed openstack/craton master: Updates documentation for setting up a dev env  https://review.openstack.org/44769713:23
sigmavirusthomasem: so is that retro going to be open to all folks in this channel?13:41
thomasemsigmavirus: I sure hope so13:41
sigmavirusOr is this going to be a Rackspace specific retro? That's one thing I don't have clarity on13:41
thomasemIf it's not, I'm concerned.13:41
thomasemfsaad: ^^13:42
openstackgerritThomas Maddox proposed openstack/craton master: JSON Path-like querying for variables  https://review.openstack.org/44394113:47
openstackgerritThomas Maddox proposed openstack/craton master: Move to MySQL 5.7 and SQLAlchemy>=1.1.0  https://review.openstack.org/44318613:47
openstackgerritThomas Maddox proposed openstack/craton master: Variable search for resources now uses resolved variables.  https://review.openstack.org/44092913:47
thomasemantonym: thanks a 'mil for the doc updates. I made that the parent to the variables work.13:50
antonymthomasem: sweet, no prob13:50
sigmavirusthomasem: did you mention problems with docker networking yesterday?13:56
thomasemsigmavirus: Only for trying to run functional tests on OS X.13:56
* sigmavirus can't even talk to craton via an exposed port on ubuntu13:56
thomasemOh?13:56
thomasemsigmavirus: are you mapping to the new default port, or 8080?13:56
sigmavirusohhhh13:56
sigmaviruswhat's the new port?13:56
thomasemhttps://github.com/openstack/craton/blob/master/etc/craton-api-conf.sample#L1113:57
sigmavirusnevermind13:57
thomasemsigmavirus: ^^13:57
* sigmavirus angsts13:57
sigmavirusthanks13:58
thomasemsigmavirus: you bet!13:58
sulothomasem: so we stil not sync with global req ?13:58
* sigmavirus missed that merging13:58
sigmavirussulo: correct13:58
sulosigmavirus: why so ?13:58
sigmavirusthomasem: now I'm getting 401's that the bootstrap user isn't permitted to access the server13:58
thomasemsulo: yeah, until the entry in global-requirements.txt matches our lower-bound. We want to communicate the limitations of our project.13:59
sigmavirussulo: the reason is loosely that we're likely to update our own requirements faster than g-r13:59
thomasemsulo: https://github.com/openstack/requirements/blob/master/global-requirements.txt#L278 that's too low for our lower-bound. It must be >=1.1.0.14:00
sigmavirusthomasem: so will these tests need to create their own user with the bootstrap user and then do things?14:00
thomasemsigmavirus: Not if we can inject different values at record time... I thought that was the change you were going to make? Is that not possible, or a good idea?14:01
sigmavirusthomasem: it is possible, but I can't even re-record those cassettes now14:01
thomasemOh... huh14:01
sulothomasem: sigmavirus: so the worry is if someone is already usign that version its not getting updated ...14:01
sigmavirusI'm trying to use the bootstrap user to record these, but it seems that won't work14:02
sigmavirussulo: the worry is that if we only use what's in g-r, someone might use something older than 1.1.0 and they won't have a functioning craton14:02
thomasemI don't see how, if the env vars are set for the bootstrap user's creds?14:02
sulosigmavirus: tests create its own user with given project_id straight into the db14:02
thomasemsulo: sigmavirus is talking about cratonclient integration tests14:02
sulooh gotcha re:client14:03
thomasemRegarding recording API responses so we don't need to call an actual API all of the time.14:03
sigmavirusor impose the cost of setting up a container per-test on the test runner(s)14:03
thomasemYeah... that'd hurt14:03
thomasemsigmavirus: Can you, out of band, talk to the API using that bootstrap user?14:04
thomasemNot through the tests14:04
sulosigmavirus: thomasem: so whats the strategy to sync with global for other pkgs .. it might take ages before g-r gets to 1.1.0 ?14:06
sigmaviruswith curl it seems to work14:07
sigmavirussulo: what other packages?14:08
thomasemHmmm... and you're sure the tests have the same creds? Are the cassettes deleted? I'm not 100% sure how that works, but when I inserted some extra calls I was getting errors because it was trying to run that call against a cassette that didn't contain that call.14:08
sigmavirusintegrated projects don't rely on features of libraries/databases taht they can't guarantee will be there14:08
thomasemSo, that's one way to kind of tracer-bullet debug that14:08
thomasemIs deleting the cassettes the way to re-record? Or do you flip something else?14:09
sulosigmavirus: olso.xxx for example14:09
sigmavirusI delete cassettes and re-record14:09
sigmavirussulo: that's an integrated project14:10
sigmavirusit won't promise support for things that it can't actually support14:10
sulosigmavirus: what does that mean ?14:10
sulonot sure i follow14:10
sulodoes olso not release new version of things etc ?14:10
sigmavirusoslo does release new versions, usually several times over a development cycle14:11
sigmavirusThey won't release a feature that depends on a version of a library that is newer than a lower bound though14:11
sulosigmavirus: and do we not care about those new releases ?14:11
sigmavirusoslo.db, for example, wouldn't support something that's only sqla 1.1.0 when the minimum version is lower than that14:11
sigmavirussulo: we do14:11
sigmavirusand we consume them because we're not pinning to specific versions14:11
sulosigmavirus: so do we care to get upto date with that or not ? you sayiing it not important as long as we freeze ?14:12
sigmavirusI'm saying, we don't freeze versions, so we will inherently, by the default behaviour of pip, remain up-to-date with oslo releases14:13
sigmavirusWe do not cap our dependencies in craton14:13
sigmavirusSo we will always get the newest version, for better or for worse14:13
sigmavirusmy kingdom for craton to log things that are actually useful14:14
suloah right, so we dont care taht g-r caps right ?14:14
sulonevermind, i think it makes sense14:15
sigmavirusg-r has aggressively removed caps on dependencies14:15
sigmavirusg-r is using upper-constraints to test a specific version without capping though14:15
sulosigmavirus: gotcha14:15
sigmavirusthat is what prevents surprise breakage14:15
suloyeah makes sense14:15
sulocool cool i understand now .. thanks14:15
thomasemsigmavirus: I'm going to pull your patch and see if I can better understand the problem.14:17
sigmavirusthomasem: it's not all in that patch at the moment14:17
thomasemAh14:17
thomasemI need to step away for like 15 minutes or so. Want to Vidyo after that, sigmavirus?14:21
sigmavirusSounds good thomasem14:21
fsaadretro is open, thought we discussed sending invite to openstack dev list with subject [CRATON] in right ?14:23
fsaadgood morning btw ;)14:23
sigmavirussitting in craton-recordable14:29
fsaadit's 90 mins away for me sigmavirus14:30
fsaadfor me it shows 11am-12pm central14:30
fsaadthat's how exchange added it anyways14:30
sigmavirusfsaad: ah, I'm talking about an impromptu pairing session with thomasem14:31
fsaadgot it thanks ;)14:31
fsaadwas still reading scroll heh14:31
*** Syed__ has joined #craton14:40
thomasemfsaad: Yeah, that was my impression, too. I don't think a .ics went out yet, though. Thanks for clearing that up!14:49
thomasemInteresting that the push to the betamax review didn't dispatch an IRC message?14:55
sigmavirusthomasem: very interesting15:13
openstackgerritMerged openstack/python-cratonclient master: Enable coverage report in console output  https://review.openstack.org/43350515:14
fsaadwhat's this betamax review y'all talk about ?15:22
openstackgerritIan Cordasco proposed openstack/python-cratonclient master: Add tests for our cells integration  https://review.openstack.org/44551515:23
sigmaviruswell that one worked15:24
anonymikeI'd like to submit some updates on the docs. Nothing major, I'd just like to get some of those sweet launchpad gerrit points ;)  I'm about to report a  bug on the dev environment docs but noticed antonyms parent bug is very similar. Should I piggy back off of that or follow through and create a new bug.15:24
sigmavirusfsaad: https://review.openstack.org/#/c/442165/10 which appears to be failing15:24
sigmavirusanonymike: that's up to your judgment15:24
fsaadah! thanks sigmavirus15:24
anonymikehmm I'm not sure how to create a child bug. Perhaps that's a better exercise15:25
jimbakerthomasem, the retrospective is open to everyone. tojuvone plans to attend, along with intel folks15:26
anonymikeI'll try that15:26
openstackgerritIan Cordasco proposed openstack/python-cratonclient master: Add Betamax for testing  https://review.openstack.org/44216515:26
sigmavirusanonymike: there's no such thing as a child bug15:26
sigmavirussorry, I misunderstood your original question15:26
anonymikeoh?15:26
thomasemjimbaker: +1, good deal15:26
anonymikewhat is the parent in reference to here https://review.openstack.org/#/c/447697/15:27
openstackgerritIan Cordasco proposed openstack/python-cratonclient master: Add tests for our cells integration  https://review.openstack.org/44551515:27
anonymikea child patch?15:27
sigmavirusanonymike: do you mean 584f0551facf065564d8cb2bdcb7fbb138332504? on the gerrit page?15:28
jimbakersigmavirus, thomasem, so with the env vars for https://review.openstack.org/#/c/442165/, no changes required to dbsync bootstrap, right?15:28
sigmavirusThat's the parent commit sha15:28
anonymikesigmavirus: yes15:28
sigmavirusanonymike: want a quick introduction to how git works under the hood?15:28
thomasemjimbaker: that's the idea. We're using placeholders in the recordings so it won't require any specific credentials for replaying the recorded API responses.15:29
thomasemiiuc15:29
anonymikesigmavirus: I'm pretty familiar but I'm sure it wouldn't hurt15:29
jimbakergot it, that sounds the right approach to me. also better than having this type of data explicitly everywhere in the recordings15:30
sigmavirusanonymike: are you familiar with the way that repository history is stored as a Directed Acyclic Graph?15:30
thomasemjimbaker: definitely15:30
anonymikesigmavirus: yes15:30
sigmavirusso each commit has at least one commit that is it's 'parent'15:30
sigmavirusmerge commits tend to have at least 215:31
thomasemhttps://betamax.readthedocs.io/en/latest/configuring.html#filtering-sensitive-data15:31
sigmavirusoctopus commits have been known to have over 50 (in the kernel)15:31
sigmavirusSo the parent in the gerrit view is just the parent commit's SHA115:31
sigmavirusThat has no impact on LaunchPad15:31
anonymike!!! i didn't read the subject matter of the commit correctly. I thought it was a direct reference to a typo in the docs15:32
openstackanonymike: Error: "!!" is not a valid command.15:32
sigmaviruslol anonymike don't upset openstack bot15:33
thomasemLOL15:33
anonymikeSo I thought it was somehow related to what antonym did15:33
thomasem openstack bot smash !!!15:33
anonymikehaha welp, im sorry openstack bot15:33
* anonymike will stop overcomplicating things15:34
sigmavirusanonymike: gerrit is confusing15:35
*** palendae_ is now known as palendae15:35
anonymikelol I was trying to make it a lot more confusing :/ Anyway, I'm just gonna keep going along with this task and try not to upset anyone or any bots15:39
jimbakersulo, https://review.openstack.org/#/c/446972/ - just wanted to find out your plan for the duplicate user creation bug (which could be done as part of overall users functional testing)15:44
jimbakerdidn't want this problem i observed get lost...15:44
sulojimbaker: ah thats tracked separately15:45
sigmavirusanonymike: you only upset the bots15:45
jimbakeralso worthwhile in general. try for example this: craton-post v1/projects name=baz15:45
sulojimbaker: see commit msg on test coverage too .. i've tracked that separately too15:45
sulohttps://bugs.launchpad.net/craton/+bug/167434715:45
openstackLaunchpad bug 1674347 in craton "User create throws 500 error on bad uuid string" [Medium,New] - Assigned to Sulochan Acharya (sulochan-acharya)15:45
sigmavirusanonymike: don't think you upset any of us =)15:45
jimbakerrepeatedly15:45
sulowill tackle the dup with that ^15:46
jimbakersulo, ok, not quite the same, but sounds reasonable15:46
jimbakeri will add my bug report to that, and will +2 the user in project fix15:46
sulojimbaker: yeah, i need to tackle excpetion on that15:46
suloso dup exception will get wrapped15:47
sulojimbaker: sounds good15:47
sulojimbaker: i didnt want to start fixing separate things on that patch is all15:48
thomasemPlease add topics to the etherpad for retro! https://etherpad.openstack.org/p/craton-meetings (starting at line 85)15:48
jimbakersulo, understood15:48
jimbakeri suggest we go through a program of systematic testing15:49
jimbakersuch as attempt to duplicate a resource, for every type of resource; etc15:49
sulojimbaker: +1, yeah i caught that uuid error trying to test bad project_id ... but i am sure the same might be true for others15:50
suloalso there are some other problem re tests15:50
sulofor example .. we were testing output to be json in functional tests .. and some were not returning that back .. so that was erroring out too ..15:51
sulogit-harry has fixed that though in his latest patch15:51
jimbakera bit of refactoring is probably necessary to do this systematically as well - want to parse project uuid the same way, every usage...15:51
jimbakercool15:51
suloyeah true15:52
openstackgerritIan Cordasco proposed openstack/python-cratonclient master: Add integration tests for clouds client  https://review.openstack.org/44590915:52
openstackgerritIan Cordasco proposed openstack/python-cratonclient master: Add integration tests for regions  https://review.openstack.org/44613415:52
sigmavirusbetamax test series updated15:53
thomasemawesome sigmavirus, will take a look15:56
jimbakerso meeting in craton vidyo room...16:00
sulojimbaker: cool, thanks for updating that16:05
jimbakertojuvone, are you joining us today for the retrospective? (including report from milan?)16:10
sigmavirusthomasem: in case you've not read it: https://www.amazon.com/Agile-Retrospectives-Making-Teams-Great/dp/097761664916:11
sigmavirushttps://plans-for-retrospectives.com/en/ is a good companion for the book too16:11
openstackgerritMerged openstack/craton master: Updates documentation for setting up a dev env  https://review.openstack.org/44769716:16
tojuvonejimbaker, yes, just need to bring kid to soccer soon, but back 17 UTC16:26
openstackgerritMerged openstack/craton master: Variable search for resources now uses resolved variables.  https://review.openstack.org/44092916:41
git-harryhttps://review.openstack.org/#/dashboard/?foreach=%2528project%253A%255Eopenstack%252Fopenstack%252Dansible.%252A%2529%250Astatus%253Aopen%250ANOT+owner%253Aself%250ANOT+label%253AWorkflow%253C%253D%252D1%250Alabel%253AVerified%253E%253D1%252Cjenkins%250ANOT+label%253ACode%252DReview%253E%253D0%252Cself&title=OpenStack%252DAnsible+Review+Inbox&Reviews+Requested+by+PTL=starredby%253Ajesse%252Dpretorius&Need16:47
git-harrys+Feedback+%2528Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%2529=NOT+label%253ACode%252DReview%253C%253D2+age%253A5d&You+are+a+reviewer+but+haven%2527t+voted+in+the+current+revision=NOT+label%253ACode%252DReview%253C%253D2%252Cself+reviewer%253Aself&Needs+final+%252B2=label%253ACode%252DReview%253E%253D2+limit%253A50+NOT+label%253ACode%252DReview%253C%253D%252D1%252Cself&Passed+Jenkins%16:47
git-harry252C+No+Negative+Feedback=NOT+label%253ACode%252DReview%253E%253D2+NOT+label%253ACode%252DReview%253C%253D%252D1+limit%253A50&Wayward+Changes+%2528Changes+with+no+code+review+in+the+last+2days%2529=NOT+label%253ACode%252DReview%253C%253D2+age%253A2d16:47
thomasemBy the way, we're past our scheduled time, if anyone needs to run.17:08
fsaad+117:09
fsaadthe tuesday invite I have is for every two weeks, are we not having a weekly sprint and retro flip flop?17:21
jimbakerfsaad, double checking....17:22
fsaadthanks just making sure I didn't misunderstand what we ended up agreeing on17:22
jimbakerso it is flip flopping. but you haven't accepted the sprint planning meeting17:23
jimbakerso probably just a problem in the cal setup. let me resend17:23
fsaadoh! lemme check that17:23
fsaadpebkac17:23
fsaadah that's the empty-looking one I had gotten before17:24
jimbakerok, so strange17:24
fsaadok now I got it fine17:24
fsaadnot sure what was the deal last time but this one worked, thanks jimbaker !17:25
jimbakerfsaad, cool, glad it worked this time!17:26
fsaado/17:27
jimbakerlooks i can readily share my entire calendar. but that's not so good... still looking how to do a single ICS export17:29
jimbaker(may require do separately in a better tool than owa outlook)17:29
*** VW_ has joined #craton17:33
*** VW has quit IRC17:33
sigmavirusjimbaker: what do you use? OWA? Outlook? Mail.app?17:33
thomasemThanks for the suggestions, sigmavirus!!17:35
sigmavirusthomasem: I worked at a consultancy. Used to run our own retros17:35
thomasemAhh, I see. I'll check these out. I've mainly organically learned the various agile flavors, never done any sort of focused learning on the subject, besides some silly training at my last job which got completely ignored by the rest of the team when in practice.17:36
thomasemSo, you did specifically agile consulting, or software, or...?17:38
sigmavirusyes17:41
sigmavirusWe were small and each tasked with doing all the things17:42
sigmavirusAgile Consulting - Helping customers with agile (writing stories, planning work, running retros, etc.); Agile Staff Augmentation - Writing code; and other stuff17:42
sigmavirusWe were billed off as pairs too, so I ended up spending ~32 hours a week pairing17:43
sigmavirusSometimes I spent 36-40 hours pairing to help others make up time off17:43
* sigmavirus is a chronic over-worker17:43
thomasemLol, I see.17:44
sigmavirusI took 1 day of vacation at that job... to interview at Rackspace17:47
sigmavirusFlew in to SATX on a Sunday, flew out the Monday night after the interview. Went to work Tuesday17:47
thomasemWow17:48
thomasemI was about to ask... did you often run into teams pretty resistant to changing as a result of your consulting?17:48
sigmavirusSo I only worked there for a year, and for 90% of that time was on the same client. That client existed before I got there, but was already pretty receptive to agile and constructive feedback on improving their process17:51
sigmavirusOther people worked on other clients, and one was really bad about it17:52
thomasemThat's good. I guess when they bring someone in they recognize their need to change.17:52
thomasemAt least one would hope17:52
sigmavirusThat said, we were doing completely new application development for them, they had no engineers and just wanted an app at the end. Didn't care about properly prioritizing features and getting an MVP out or anything reasonable17:52
thomasemOhhhhhhhh17:52
sigmavirusYeah. The problem, though, is that we hired some people who only ever wanted to write some code and not do the hard work17:53
sigmavirusSo after I left for Rackspace, some of those people took over that client relationship and it fell apart17:53
sigmavirusBut also, after I left for Rackspace, the consultancy lost 11 people in the course of 6 months17:53
thomasemLol, damn. Sounds like it imploded.17:55
sigmavirusYeah, it was in need of hiring some consultants of its own ironically17:56
thomasemHahaha17:56
jimbakersigmavirus, i use OWA17:59
jimbakerit seems to work just fine, other than occasional sync issues with fsaad; or not being able to publish ICS for specific events (or maybe my inadequate knowledge...)18:01
sigmavirusyeah Idk how to do it with owa18:01
*** klindgren has quit IRC18:10
anonymikehow and when are updates to the read the docs  site triggered?18:48
sigmavirusanonymike: I don't think they're triggered any longer as that was configured back when we were using github18:58
sigmavirusWe need to publish our docs via openstack-infra but I've forgotten how that works18:58
anonymikeMost of the changes I proposed were already addressed in the code but not on the doc site :( :(19:00
anonymikeShould have read through that first19:00
fsaadboo19:03
* sigmavirus runs errand19:09
openstackgerritMichael Porras proposed openstack/craton master: Documentation update for pymysql  https://review.openstack.org/44824819:26
anonymikepretty insignificant :/ but just making sure everything is setup correctly ^19:27
thomasemgood catch, anonymike19:48
anonymikeheh thanks, I thought I found a lot more but it was already updated :)19:49
anonymikeworking on getting stuff setup to try and reveiew19:49
jimbakerso docs should rebuild when published in master against github.com/openstack/craton19:52
openstackgerritThomas Maddox proposed openstack/craton master: JSON Path-like querying for variables  https://review.openstack.org/44394119:53
jimbakereven better if we use openstack's doc build of course...19:54
anonymikejimbaker: docs definitely differ between openstack/craton master and read the docs19:56
thomasemGood thing I'm doing the functional tests this way, already found a bug when doing var search on networks.19:57
anonymikewould you like me to look at openstack doc build jimbaker?19:57
jimbakeranonymike, yeah, i noticed the triggering stopped working. manually rebuilt19:57
jimbakeranonymike, +119:57
anonymikecool, I'll dive into that19:58
jimbakeranonymike, ok, should be rebuilt to latest now on http://craton.readthedocs.io/en/latest/index.html19:58
jimbakerand hopefully new support soon against openstack infra19:58
anonymikejimbaker: changes look good19:59
thomasemSo, something introduced in the resolved vars search patch broke network var search.20:03
thomasemWonder if it's something to do with 'descendants'.20:04
jimbakerthomasem, maybe with respect to how descendants are specifically specified by class of resource?20:05
jimbakeri would check that lookup function20:06
thomasemRight20:06
thomasemI shall, thanks!20:06
jimbakernp20:06
thomasemIt was missing from the _resource_mapping for the get_desc lookup20:13
thomasemmodels.Network didn't have an entry there.20:14
thomasemNow it does. :)20:14
jimbakerahh. maybe it should throw a good exception if not registered...20:14
thomasemAnnnnd it works.20:14
jimbakernice. well at least the abstraction holds!20:15
jimbakerjust modestly leaky, due to lack of reg enforcement20:15
thomasemLol, yep20:16
thomasemWould be interested in thoughts on my approach for consistently testing nested var search across all resources: https://review.openstack.org/#/c/443941/12/craton/tests/functional/test_jsonpath_search.py20:16
thomasemAnd Gerrit's like molasses again. :(20:17
openstackgerritThomas Maddox proposed openstack/craton master: JSON Path-like querying for variables  https://review.openstack.org/44394120:17
jimbakerthomasem, will take a look20:19
jimbaker+120:19
jimbakerseems like a decent abstraction to what would be otherwise annoying repetition20:20
jimbakerthomasem, i think the only thing i sometimes do here in this case20:20
jimbakeris to add something to generate specific level keys20:21
jimbakerso in this case it might be "bumbleywump-C1" for cloud, or something like that20:21
jimbakerjust so we get descendant testing as well in20:22
thomasemjimbaker: aha, yeah. So, I was thinking this would help us test the data type handling (json approximation) and unresolved searching for all resources in a uniform fashion, then I was going to set up some separate tests to build a whole cloud and assert things at different layers of it, making sure resolved search works with this.20:23
thomasemTo keep the abstraction simple here.20:23
jimbakeryep. works for me20:24
thomasemexcellent!20:24
jimbakerone slice at a time sounds good20:24
thomasemThat is good feedback and I totally agree we need to address it both ways.20:24
jimbakeragreed. i think the approach you suggest is the best one. the data types being checked are a separable code path from the descendant aspect (as is the conjunction aspect)20:26
jimbakerso three slices, three types of tests20:27
jimbakerMorpheus: ... When I see three objectives, three captains, three ships. I do not see coincidence, I see providence. I see purpose. ...20:28
thomasemjimbaker: yep. Although, I can do a bit of the conjunctive testing in this abstraction. :P20:28
thomasemHahaha20:28
thomasemhttps://bugs.launchpad.net/craton/+bug/167481520:36
openstackLaunchpad bug 1674815 in craton "Network create does not return variables in response" [Undecided,New]20:36
jimbakergit-harry, sigmavirus, sulo - http://lists.openstack.org/pipermail/openstack-dev/2017-March/114425.html - nomination of thomasem for craton core20:43
jimbakerwhich is very much well earned!20:43
thomasemjimbaker: Thanks!! :)20:46
fsaad~.20:46
fsaadjust experienced how annoying the internal network can get if you're trying to contribute upstream20:47
*** klindgren has joined #craton20:48
thomasemlol what happened fsaad?20:48
fsaadwas just playing around with gerrit the firewall bounced me back on my seat as I was taking a stab at a review20:50
fsaadsince port closed.20:50
thomasemWow20:52
thomasemHmmmm, I haven't had that problem? Wonder if it's an LDAP group you need to be in or something?20:52
jimbakerthis is why i do all substantive comments in another editor20:52
jimbakerthen paste into gerrit20:52
jimbakerbut even outside vpn, it can be problematic and lose stuff20:52
jimbakerbecause...20:52
fsaadthomasem: are you on vpn?20:53
fsaadmaybe I'm doing things wrong, but I was following https://docs.openstack.org/infra/manual/developers.html#working-on-bugs20:53
fsaadand git review -s tried to connect to the site on a port that wasn't 80 or 44320:55
thomasemfsaad: I'm not, but I've done that before on VPN. Lemme give it a go here in a bit.20:55
fsaaddon't worry I'll poke around, it's good exercise thanks thomasem20:56
thomasemSounds good, fsaad!20:56
fsaadah it was pretty basic, my ssh key had too open permissions... I'm playing with this in a container so was manually setting stuff up. Thanks thomasem !21:04
fsaadalso I'm now surprised port 29418 is open, but i imagine it's only towards certain ip's.21:05
jimbakerthomasem, also check for user variables as well21:05
jimbakerin search21:05
jimbakerif you haven't done so21:05
jimbakerjust going through an ancestor patch however21:05
jimbakeralthough it looks like user variables are still undersupported in general. hmmm. i guess we can address in a separate pass21:07
jimbaker(probably an outstanding bug..)21:07
thomasemYeah, we need to shore that up.21:12
openstackgerritThomas Maddox proposed openstack/craton master: Return variables in response on Network create  https://review.openstack.org/44828521:22
openstackgerritThomas Maddox proposed openstack/craton master: JSON Path-like querying for variables  https://review.openstack.org/44394121:23
openstackgerritThomas Maddox proposed openstack/craton master: Move to MySQL 5.7 and SQLAlchemy>=1.1.0  https://review.openstack.org/44318621:23
openstackgerritMerged openstack/craton master: Remove log translations  https://review.openstack.org/44783321:24
thomasemjimbaker: I based my patches on https://review.openstack.org/44828521:29
thomasemFYI21:29
jimbakerthomasem, ack21:30
thomasemSince it was a small fix that makes network creates consistent and allows my functional tests to work. :)21:30
jimbakerok, will look at that parent so we can get everything else in21:30
thomasemAwesome21:30
jimbakerthomasem, also this is the sort of trivial that i would love to describe as not needing independent core reviews21:30
thomasemI'm inclined to agree. On my last project we basically gave some rope for trivial changes like this. At least while we weren't stable and in production. :)21:31
jimbakerso i'm going to my core discretion here...21:31
jimbakercool21:31
thomasemIt's the same pattern as everywhere else and the test proves it.21:32
jimbakerindeed21:32
jimbakerok, +2'ed and workflowed21:32
thomasemThanks!21:33
jimbakernp! brb21:33
openstackgerritThomas Maddox proposed openstack/craton master: JSON Path-like querying for variables  https://review.openstack.org/44394121:36
openstackgerritMerged openstack/craton master: Return variables in response on Network create  https://review.openstack.org/44828521:41
openstackgerritMerged openstack/craton master: Move to MySQL 5.7 and SQLAlchemy>=1.1.0  https://review.openstack.org/44318621:41
thomasemAwww yiss21:45
thomasemAlright. I've partied pretty hard today; time to run. Have a lovely evening/day!21:50
anonymikelater thomasem!21:51
jimbakersigmavirus, can you give me more context on your -1 on git-harry's patch - https://review.openstack.org/#/c/447580/3 ?21:58
jimbakereg, is this with respect to https://review.openstack.org/#/c/447580/3/craton/api/v1/schemas.py ? (which seems to be removing lots of duped code, so LGTM, at the cost of some possible reflection possibilities for docs)22:02
*** klindgren has quit IRC22:22
*** pwnall138 is now known as zz_pwnall13822:26
*** VW has joined #craton22:59
*** VW_ has quit IRC23:01
*** VW has quit IRC23:03
*** harlowja has quit IRC23:06
*** cloudkiller has joined #craton23:49
*** cloudnull has quit IRC23:50
*** d34dh0r53 has quit IRC23:50
*** cloudkiller is now known as cloudnull23:50
*** _d34dh0r53_ has joined #craton23:54

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!