Earlier  
Later
New Search
Posted Nick Remark
#openstack-sdks - 2017-11-29
01:14:29 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Start using Connection in openstack.cloud https://review.openstack.org/523259
01:14:29 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Remove get_legacy_client https://review.openstack.org/523483
01:14:50 rods wow
01:16:15 SamYaple one patch a day mordred. thats my review rate for your patches. youre being throttled
01:40:58 openstackgerrit Hengqing Hu proposed openstack/python-openstacksdk master: Add pools attribute to load balancer heath monitor https://review.openstack.org/522962
02:03:36 TheJulia SamYaple: What about for patches written by others? :)
02:04:35 SamYaple TheJulia: dont subvert the spirit of my decleration with your hacker-think!
02:04:45 TheJulia Muahahahahaha!
03:40:38 openstackgerrit Jamie Lennox proposed openstack/keystoneauth master: Mark SAML loader properties as required https://review.openstack.org/523675
03:58:23 openstackgerrit Jamie Lennox proposed openstack/keystoneauth master: Mark SAML loader properties as required https://review.openstack.org/523675
08:58:23 openstackgerrit OpenStack Proposal Bot proposed openstack/keystoneauth master: Updated from global requirements https://review.openstack.org/523736
10:11:53 openstackgerrit Édouard Thuleau proposed openstack/python-openstacksdk master: Set empty Tag list if Network Tag API extension not supported https://review.openstack.org/523834
12:41:37 frickler mordred: how about doing a shade release fixing https://storyboard.openstack.org/#!/story/2001265 ?
13:38:58 openstackgerrit David Shrewsbury proposed openstack-infra/shade master: WIP: os_router idempotency check https://review.openstack.org/523873
13:41:10 Shrews mordred: wow, your changes are not happy moving through to gate
13:41:36 Shrews frickler: i'm looking at that now
13:41:54 Shrews 523873 trying to confirm what's being seen
13:50:34 frickler Shrews: the bug is triggered only when Neutron is configured with HA (or maybe DVR) and the router also uses that, so I'm not sure you will see it in gate easily
13:51:15 Shrews frickler: yeah, just noticed that comment. trying to find the api for that
13:54:23 Shrews frickler: not being familiar with that extension, was https://review.openstack.org/482153 totally the wrong thing to do then?
13:54:52 Shrews mordred: i'm wondering what problem 482153 was solving and if it should just be reverted
13:56:57 Shrews the commit message says "L3 HA ports do not correspond to a router interface" but obviously that's not correct
13:58:56 Shrews frickler: do you know if that is something that can be enabled in devstack?
14:01:24 frickler Shrews: iiuc 482153 solved the issue not to list the L3 HA ports that are more or less internal to the Neutron HA implementation
14:02:26 frickler Shrews: and you can sure enable things in devstack, neutron is running various scenarios with DVR, not sure about HA
14:03:08 Shrews oh! seems a fix is already committed
14:03:44 Shrews ok, i thought we needed a fix AND release. but just a release is needed then
14:03:54 frickler Shrews: ah, yes, I did a fix for that, sorry, I assumed that you had seen it. I thought you were trying to verify the fix
14:04:20 Shrews frickler: my fault, i misunderstood. yeah, only mordred can do the release
14:05:36 frickler Shrews: adding your check above and maybe a devstack scenario that runs Neutron in HA mode still seem useful to me
14:05:46 Shrews would be nice if we could find out if devstack supported this though
14:06:26 Shrews frickler: yeah. i don't know the devstack magic for that :(
14:07:14 frickler Shrews: I'll put it on my list, hopefully sometime this week
14:15:24 cdent sdague: how did your microversions talk go? was it at apistrat?
14:16:51 sdague it went pretty well, it was at apistrat. It was the end of the last day, so I got a couple of questions on it, but not a lot of space for broader discussion
14:18:53 cdent did anyone have an epiphany?
14:38:48 mordred Shrews, frickler: releases are actually run by the release team now, so you can actually submit a patch requesting one without needing me ... but, I can do that this morning - I think we're overdue for a release anyway
14:42:20 Shrews mordred: oh right. is that process described anywhere?
14:46:54 mordred Shrews: it's pretty much making a patch to openstack/releases ... you'll find a file, deliverables/queens/shade.yaml - that has entries you can copy-pasta
14:46:54 mordred Shrews: you need a git sha - so doing a pull on master is usuallya good first step
14:52:07 celebdor1 Does anybody know if shade support heat tags? I couldn't find it with simple grepping
14:52:24 Shrews mordred: ah, the README there has the process... but the PTL or release liaison has to submit the request
14:53:15 mordred celebdor1: I don't think it does, no - but adding it would be a great idea
14:54:31 celebdor1 mordred: It is indeed
14:54:42 celebdor1 I need it for queens though :P
14:55:16 mordred celebdor1: :) it's pretty quick to add things to shade and get them released - I don't think getting it in for queens should be a problem
14:57:28 mordred Shrews: remote: https://review.openstack.org/523890 Release shade 1.25.0
14:58:55 celebdor1 mordred: thanks for the info
14:58:59 celebdor1 :-)
14:59:30 mordred Shrews: also, I have learned this morning that there are a few openstack projects, octavia-dashboard, senlin-dashboard, tricircle, bilean, senlin, heat and a couple others - that an sdk release is going to break
15:00:22 mordred Shrews: so I think I need to put 'get patches landed to each of those projects' to the list of things we do before we cut an sdk release with the new changes in it
15:00:23 Shrews mordred: that's fun
15:02:17 mordred Shrews: oh - actually, no - we kept compat for the thing that would break them
15:02:30 mordred so we can release, then change the interface they all use
15:11:49 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Sort image update results before comparing https://review.openstack.org/523893
15:12:02 mordred Shrews: that ^^ should fix the unittest failures that are happening
15:13:37 mordred Shrews: I'm guessing the jsonpatch release on november 25 is to blame, fwiw
15:48:20 openstackgerrit Monty Taylor proposed openstack-infra/shade master: Avoid tox_install.sh for constraints support https://review.openstack.org/508061
15:48:22 openstackgerrit Monty Taylor proposed openstack-infra/shade master: Fix basepython setting in tox.ini https://review.openstack.org/523915
16:16:24 mordred incoming patch bomb ... sorry for the rebase ... it was needed to get in the jsonpatch sorting fix
16:16:33 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Add ability to work in other auth contexts https://review.openstack.org/522970
16:16:33 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Add helper property to get the current user id https://review.openstack.org/522971
16:16:34 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Remove reference to context-managers from release note https://review.openstack.org/522972
16:16:34 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Document current_user_id in a release note https://review.openstack.org/522973
16:16:35 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Fix py35 and pypy tox env https://review.openstack.org/523383
16:16:35 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Cleanup objects that we create on behalf of images https://review.openstack.org/522974
16:16:36 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Add method to cleanup autocreated image objects https://review.openstack.org/522975
16:16:36 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Complete move of baremetal machine tests https://review.openstack.org/522976
16:16:37 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Treat clouds.yaml with one cloud like envvars https://review.openstack.org/522977
16:16:37 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Protect against p_opt not having prompt attribute https://review.openstack.org/522978
16:16:38 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Update make_rest_client to work with version discovery https://review.openstack.org/522979
16:16:38 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Added nat_source flag for networks. https://review.openstack.org/522980
16:16:39 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Shift image tests from test_operator https://review.openstack.org/523258
16:16:39 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Switch baremetal nics/ports tests over https://review.openstack.org/523355
16:16:40 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Start using Connection in openstack.cloud https://review.openstack.org/523259
16:16:40 openstackgerrit Monty Taylor proposed openstack/python-openstacksdk master: Remove get_legacy_client https://review.openstack.org/523483
16:16:55 mordred Shrews: those should, you know, pass this time
16:17:41 sdague cdent: I don't know that there were any real epiphanies from folks. I think a new interesting spin on it was with graphql, someone asked if that solved the problem all by itself
16:18:53 sdague which, it solves a related problem in theory, though in practice, if your applications don't consume the API directly, but through a 3rd party SDK, as we've seen, graphql probably just always asks for everything, then you are back to REST resources.
16:19:08 cdent I’ve read elsewhere of graphql being a way out of a versioning problem, if you start there
16:19:25 cdent but if you’re not already there…
16:20:54 sdague yeh
16:23:07 sdague also, I think graphql seems to work best when the front end has intimate knowledge of the costs of asking for things on the backend. So as a layer between the github ui and services, it's awesome
16:27:39 mordred sdague: yah - or, as soon as they finish adding all of the things to the graphql layer, it'll help zuul's github driver make fewer API calls and thus avoid rate-limit issues
16:28:15 sdague mordred: sure
16:28:46 mordred sdague: but I agree, in general, with the assessment about intimate knowledge - in this example, the zuul thing is a cost optimization - it's certainly not an easier/better way to write the first version of the thing
16:29:07 sdague mordred: and, you are hitting the API raw, because you need that level of granularity
16:29:17 mordred yup
16:29:26 sdague but, if you went through someone's random SDK
16:29:35 sdague you are unlikely to get those optimizations
16:29:40 mordred yup. exactly
16:30:11 mordred that said - I'd kind of LOVE a graphql api option for openstack service ... for similar reasons
16:30:49 mordred finding the port that's ona subnet on a network is basically doing three full list calls and doing a client-side in-memory join
16:31:02 sdague mordred: honestly, building a graphql porcelin for all of openstack would be a totally legit thing to do
16:31:38 sdague it would be different enough that I don't think it would be confusing between the rest resources at the point sevices and what it returned
16:32:56 mordred sdague: yah. although having a per-service graphql as well that the porcelin could use for push-downs for efficiency would also be nice ... but yes, a graphql openstack porcelain that could do "I want to create a floating IP on a port from the server that is on this subnet of this network"...
16:33:29 mordred would be awesome to do as one call
16:41:58 openstackgerrit Monty Taylor proposed openstack-infra/shade master: Fix basepython setting in tox.ini https://review.openstack.org/523915
16:56:42 openstackgerrit Merged openstack/python-openstackclient master: Set correct designate endpoint in docs https://review.openstack.org/523567
17:17:33 openstackgerrit Dean Troyer proposed openstack/python-openstackclient master: DNM: Test -tips variations https://review.openstack.org/523938

Earlier   Later