Earlier  
Later
New Search
Posted Nick Remark
#openstack-sdks - 2017-08-18
08:36:41 openstackgerrit TingtingYu proposed openstack/python-openstacksdk master: fix the bug that cannot create a pool by openstacksdk https://review.openstack.org/495118
08:37:26 openstackgerrit TingtingYu proposed openstack/python-openstacksdk master: fix the bug that cannot create a pool by openstacksdk https://review.openstack.org/495118
09:26:27 openstackgerrit TingtingYu proposed openstack/python-openstacksdk master: fix the bug that cannot create a healthmonitor by openstacksdk https://review.openstack.org/495135
09:32:23 openstackgerrit TingtingYu proposed openstack/python-openstacksdk master: fix the bug that cannot create a healthmonitor by openstacksdk https://review.openstack.org/495135
10:21:47 openstackgerrit Praveen N proposed openstack/python-openstackclient master: remove the wrong argument https://review.openstack.org/495155
12:33:26 openstackgerrit Merged openstack/python-openstacksdk master: fix the bug that cannot create a pool by openstacksdk https://review.openstack.org/495118
12:38:44 cdent elmiko, edleafe: I guess we should have an etherpad, so I started one: https://etherpad.openstack.org/p/api-ptg-queens
12:38:59 cdent this is because of https://wiki.openstack.org/wiki/PTG/Queens/Etherpads
12:42:45 openstackgerrit Brian Curtin proposed openstack/python-openstacksdk master: Add required pool_id property to HealthMonitor https://review.openstack.org/495135
12:46:28 openstackgerrit Brian Curtin proposed openstack/python-openstacksdk master: Introduce Health Monitor for Octavia https://review.openstack.org/453243
12:56:54 openstackgerrit Merged openstack/python-openstacksdk master: Updated from global requirements https://review.openstack.org/494909
13:57:29 figleaf cdent: all the cool kids have etherpads
13:58:34 cdent we must be cool then
14:50:59 elmiko cdent figleaf, i'm gonna axe that gist, thanks for the input! =)
15:01:36 openstackgerrit Merged openstack/os-service-types master: Updated from global requirements https://review.openstack.org/494868
15:38:42 openstackgerrit Praveen N proposed openstack/python-openstackclient master: remove the wrong argument https://review.openstack.org/495155
15:43:12 openstackgerrit Chris Dent proposed openstack/microversion-parse master: Provide a helper method to get headers from environ https://review.openstack.org/495356
15:43:53 cdent elmiko: if you’re around a look that rather old bug fix would be appreciated (you and sdague are the only other cores at the moment) ^
17:09:33 openstackgerrit Rajath Agasthya proposed openstack/cliff master: Alias exit to cmd2's quit command to exit interactive shell https://review.openstack.org/491217
17:32:26 openstackgerrit Merged openstack/python-openstacksdk master: Add required pool_id property to HealthMonitor https://review.openstack.org/495135
17:38:28 openstackgerrit Merged openstack/python-openstacksdk master: Introduce Health Monitor for Octavia https://review.openstack.org/453243
18:03:50 openstackgerrit Merged openstack/python-openstackclient master: Updated from global requirements https://review.openstack.org/494908
19:48:08 openstackgerrit Merged openstack/python-openstackclient master: auto-generate object docs https://review.openstack.org/494701
20:37:31 openstackgerrit Michael Johnson proposed openstack/python-openstacksdk master: Introduce L7Policy for Octavia (load balancing) https://review.openstack.org/451980
21:17:22 juliandemille python-openstackclient v3.12.0 is giving me this error: "__init__() got an unexpected keyword argument 'user_domain_name'"
22:38:36 openstackgerrit Michael Johnson proposed openstack/python-openstacksdk master: Introduce L7Rule for Octavia (load balancing) https://review.openstack.org/452832
23:02:34 juliandemille Does anyone know how to deal with "__init__() got an unexpected keyword argument 'user_domain_name'" in the Python client?
#openstack-sdks - 2017-08-19
00:20:11 openstackgerrit Rajath Agasthya proposed openstack/cliff master: Move comments up in [extras] section of setup.cfg https://review.openstack.org/495460
00:20:23 openstackgerrit Rajath Agasthya proposed openstack/cliff master: Updated from global requirements https://review.openstack.org/494775
02:03:49 openstackgerrit TingtingYu proposed openstack/python-openstacksdk master: fix the bug that cannot create a listener by openstacksdk https://review.openstack.org/493449
02:59:12 openstackgerrit ShangXiao proposed openstack/cliff master: Fix typos and replace http with https for doc links in cliff https://review.openstack.org/495477
05:42:33 openstackgerrit Reedip proposed openstack/python-openstackclient master: [WIP]Allow for Bulk Floating IP creation https://review.openstack.org/405145
20:38:16 openstackgerrit Michael Johnson proposed openstack/python-openstacksdk master: Introduce L7Rule for Octavia (load balancing) https://review.openstack.org/452832
#openstack-sdks - 2017-08-20
06:02:20 openstackgerrit Merged openstack/python-openstacksdk master: Introduce L7Policy for Octavia (load balancing) https://review.openstack.org/451980
06:03:39 openstackgerrit Merged openstack/python-openstacksdk master: Introduce L7Rule for Octavia (load balancing) https://review.openstack.org/452832
#openstack-sdks - 2017-08-21
02:11:13 openstackgerrit TingtingYu proposed openstack/python-openstacksdk master: fix the bug that cannot create a listener by openstacksdk https://review.openstack.org/493449
02:12:07 openstackgerrit TingtingYu proposed openstack/python-openstacksdk master: fix the bug that cannot create a listener by openstacksdk https://review.openstack.org/493449
03:12:44 openstackgerrit Merged openstack/python-openstacksdk master: fix the bug that cannot create a listener by openstacksdk https://review.openstack.org/493449
14:25:36 openstackgerrit Eric Fried proposed openstack/service-types-authority master: Generate standard api_reference https://review.openstack.org/495887
14:31:34 efried mordred ^
14:31:55 cdent efried: is there a “why” for that, or just cuz it’s tidy?
14:32:17 efried cdent See argument... ahem, "discussion" here: https://review.openstack.org/#/c/495326/1
14:33:58 cdent so, there are plenty of projects that don’t publish their api-ref to … /api-ref
14:34:11 cdent they put it somewhere in docs
14:34:16 cdent (docs.o.o)
14:36:51 efried cdent Right, left the ability to customize.
14:37:21 cdent efried: in your change, yeah, but in monty’s change, it appears to be making an assumption
14:37:44 cdent and using only the service type, not the doc info
14:38:13 efried cdent Right.
14:38:44 efried Though to be fair, it's only redirecting from certain URLs involving service type aliases.
14:39:37 efried So my opinion was that we should always redirect from /api-ref/{alias or service type} to {the api_reference from sta, whatever that may be}
14:39:43 cdent efried: sure, but after redirecting to the actual service type it’s still possible to get a 404
14:39:51 efried cdent Totally.
14:39:55 cdent yeah, that’s what I think too
14:40:11 efried Because theoretically not possible to get a 404 from whatever's in the api_reference fierd in sta
14:40:13 efried field
14:41:02 efried thanks for the backup :) Helps me to know that I'm not crazy (or, if I am, I've got company)
14:41:41 cdent i’m totally crazy
16:25:19 mordred efried, cdent: I believe the effort dhellmann has been undertaking is to enforce that projects publish their api docs to /api-ref/{service-type}
16:25:53 mordred there's gate jobs in project-config to ensure api doc publication goes to the correct place
16:26:16 mordred so while I agree that up until now there has not been consistency, my understand (which might be wrong) is that the intent is to fix that
16:26:54 efried mordred Seems like a good interim solution to allow overrides from sta, so we can immediately start using api_reference from https://review.openstack.org/#/c/495326/ et al; then as projects become conformant, we just have to remove their overrides from sta.
16:27:15 efried And when they're all done, we could (but don't have to) even remove the override ability from sta.
16:28:28 mordred efried: yah - for sure
16:29:03 mordred efried: I think that's a great plan - mostly just wanted to get on the same page WRT end-goal
16:29:06 cdent it would be useful if we could have exactly one source of authority for this stuff; which is why I was nervous about including anything other than services in sta
16:29:33 cdent so if we’ve got a path to migrating away from including the doc info, I’m into that, but agree with efried that we need the overrides for now
16:29:44 mordred agree
16:30:25 efried mordred cdent My main goal here was to avoid having multiple disparate sources of the official API reference URL.
16:30:26 mordred themost important thing for sta to be the authority on is "this is the service-type name for this project and it used to be called these things"
16:31:33 mordred efried: yup
16:31:42 efried That is, I didn't want sta to be saying "the API reference is <result of some calculation, or this override>" and then api-site to be saying "the API reference is <result of some calculation whose logic might sort of duplicate what's in sta, but might diverge at some point if we forget or aren't careful>"
16:31:53 mordred efried: +1000
16:32:00 mordred efried: we share the same goal :)
16:32:05 efried Sweet.
16:32:06 cdent I’ll see that 1000 and raise 10000
16:32:54 mordred so - I thnk honestly step 1 is to verify whether there are actually any non-compliant api-ref docs
16:33:00 efried mordred Did that.
16:33:09 cdent sta has plenty of examples, yes?
16:33:09 mordred cool! are there?
16:33:18 mordred sta is, I think, out of date
16:33:24 efried mordred The ones that are still in https://review.openstack.org/#/c/495887/ are non-compliant
16:33:46 efried Because I checked the "official" constructed URL for all of those and it's 404.
16:33:48 cdent “out of date” :) some authority ;)
16:34:07 mordred ah. awesome
16:34:39 efried Well, I didn't check the URLs that are in there to make sure they're *not* 404 :)
16:34:48 efried 13 of 'em, I think.
16:37:13 efried They're all good except for https://developer.openstack.org/api-ref/monitoring-events-api/ - which I think we knew was still in the works. (Also, https://git.openstack.org/cgit/openstack/zun/tree/api-ref/source is a source tree.)
16:40:11 efried I can't tell from https://review.openstack.org/#/c/482443/ where those docs are going to land.
16:49:47 mordred efried: - api-ref-jobs:
16:49:49 mordred service: monitoring-events
16:50:06 mordred efried: that's what's in jenkins/jobs/projects.yaml
16:50:26 efried mordred Then we should whack that guy's override from https://review.openstack.org/#/c/495887/
16:51:00 mordred it doens't look like thaturl exists though - so maybe no docs have published since that job definition landed?
16:51:14 efried mordred The above change set hasn't merged yet.
16:51:40 efried Point is, both URLs are 404, but once https://review.openstack.org/#/c/482443/ lands, it'll be the right one, so we should remove the override.
16:52:35 mordred agree
16:52:40 openstackgerrit Eric Fried proposed openstack/service-types-authority master: Generate standard api_reference https://review.openstack.org/495887
16:52:44 efried Cool. ^^
#openstack-sdks - 2017-08-22
00:35:08 openstackgerrit OpenStack Proposal Bot proposed openstack/cliff master: Updated from global requirements https://review.openstack.org/494775

Earlier   Later