Earlier  
Later
New Search
Posted Nick Remark
#openstack-sdks - 2018-06-19
16:09:37 openstackgerrit Merged openstack/openstacksdk master: Change 'Member' role reference to 'member' https://review.openstack.org/576283
16:28:02 openstackgerrit Merged openstack/os-client-config master: Update links in README https://review.openstack.org/574645
17:24:39 openstackgerrit Merged openstack/openstacksdk master: Switch VEXXHOST to 'v3password' auth_type https://review.openstack.org/574745
18:11:17 openstackgerrit Merged openstack/openstacksdk master: Fix path for Limestone Networks vendor file https://review.openstack.org/574746
18:30:13 openstackgerrit Monty Taylor proposed openstack-infra/shade master: Adds Senlin support to shade https://review.openstack.org/542537
19:39:27 openstackgerrit Merged openstack/keystoneauth master: Add minimum version for requirements https://review.openstack.org/575685
19:47:44 rm_work so ... it looks like python-openstackclient gates are broken? Anyone know what's up with that?
19:48:41 dtroyer rm_work: I wish I knew. I've de-raced the volume type tests that had never been a periodic issue before and still don't know what changed under us to break this
19:49:09 rm_work :(
19:49:28 rm_work it seems pretty consistent
19:49:40 rm_work let me take a quick look (have 10m before a meeting)
19:56:47 openstackgerrit Adam Harwell proposed openstack/python-openstackclient master: Add ability to filter image list by tag https://review.openstack.org/575256
19:57:14 rm_work it just... seems like it's not creating properly maybe?
19:57:29 rm_work like, every test that creates and then tries to use a volume type, fails because it just isn't there
19:57:33 rm_work set / delete / list
19:57:42 rm_work but i don't see any Create failures >_>
19:59:37 dtroyer good point on create failure… I have not yet dug in to the cinder logs to see if the failures are visible there
20:00:32 rm_work i did, and didn't see any T_T
20:01:37 rm_work you sure it isn't a race?
20:01:40 rm_work interestingly, we see like:
20:01:56 rm_work Failed to delete volume type with name or ID '011166e91f4345dca72eb23264ed9696': No volumetype with a name or ID of '011166e91f4345dca72eb23264ed9696' exists.
20:01:56 rm_work Failed to delete volume type with name or ID 'e541a03a5e6c4c3aa52bb2b8e89e60ef': No volumetype with a name or ID of 'e541a03a5e6c4c3aa52bb2b8e89e60ef' exists.
20:02:01 rm_work then the next test we see:
20:02:23 rm_work testtools.matchers._impl.MismatchError: 'e4b2ce1108f34228a0812d78f3524c13' not in [u'e541a03a5e6c4c3aa52bb2b8e89e60ef', u'011166e91f4345dca72eb23264ed9696', u'b08252d6419c4c6c81698907e45bbb74', u'32840b2ace7e4d4897bf7c9f6eae7ac1', u'70e870861a6b4157a8b6213bc9db6fac', u'lvmdriver-1']
20:02:24 rm_work which includes the last two that weren't found, but NOT the newest one
20:02:30 rm_work do they not return right away after a create?
20:04:46 dtroyer I thought it was a race, we've had them in many of the network functional tests and I re-wrote most of them
20:05:01 dtroyer https://review.openstack.org/#/c/575448/ is my attempt at volume type
20:05:53 dtroyer I've had to wedge that in between other totally different work so I may totally be missing something
20:39:01 rm_work i wonder how cinder works, like, if i create a volume type, I assume that is async -- but if i do a GET while it's still working (but after the create call returns), will it return it in PENDING or something, or will it just hide it?
20:39:16 rm_work we may need to bring in someone from cinder? (volumes == cinder right?)
20:51:21 dtroyer rm_work: yes, this is cinder, and it wouldn't be the first time something like this surfaced here first
21:26:51 openstackgerrit Monty Taylor proposed openstack-infra/shade master: Adds Senlin support to shade https://review.openstack.org/542537
21:33:47 openstackgerrit Monty Taylor proposed openstack/openstacksdk master: Adds Senlin support to openstacksdk https://review.openstack.org/576650
22:52:35 openstackgerrit Merged openstack/openstacksdk master: Add tests to verify behavior on '' in self link https://review.openstack.org/575158
#openstack-sdks - 2018-06-20
02:27:24 openstackgerrit Mark Kirkwood proposed openstack/python-openstackclient master: Add an option to container create for storage policy https://review.openstack.org/564665
06:46:47 openstackgerrit tianhui proposed openstack/python-openstackclient master: Compute: Add description support for flavor https://review.openstack.org/575390
06:50:41 openstackgerrit Slawek Kaplonski proposed openstack/openstacksdk master: Support port binding extended attributes for querying port https://review.openstack.org/573645
06:56:37 openstackgerrit baiwenteng proposed openstack-infra/shade master: add release notes to README.rst https://review.openstack.org/576756
07:12:31 openstackgerrit tianhui proposed openstack/python-openstackclient master: Compute: Add description support for flavor https://review.openstack.org/575390
09:11:37 openstackgerrit tianhui proposed openstack/python-openstackclient master: Compute: Add description support for flavor https://review.openstack.org/575390
09:19:06 openstackgerrit Fan Zhang proposed openstack/python-openstackclient master: Add --key-name option for server rebuild API. https://review.openstack.org/576422
09:28:04 openstackgerrit Fan Zhang proposed openstack/python-openstackclient master: Add --key-name option for server rebuild API. https://review.openstack.org/576422
09:34:07 openstackgerrit John Haan proposed openstack/python-openstackclient master: Implement image tag into OSC https://review.openstack.org/576804
09:35:10 openstackgerrit John Haan proposed openstack/python-openstackclient master: Implement image tag into OSC https://review.openstack.org/576804
09:43:24 openstackgerrit Merged openstack/api-wg master: spelling error https://review.openstack.org/575967
10:31:38 openstackgerrit Merged openstack/openstacksdk master: Allow configuring status_code_retries and connect_retries via cloud config https://review.openstack.org/573780
11:10:14 openstackgerrit yanpuqing proposed openstack/python-openstackclient master: Delete the LB object quotas set command in openstackclient https://review.openstack.org/576465
11:41:20 openstackgerrit Fan Zhang proposed openstack/python-openstackclient master: Add --key-name option for server rebuild API. https://review.openstack.org/576422
12:08:50 openstackgerrit Telles Mota Vidal Nóbrega proposed openstack/python-openstackclient master: Adding api_version to FakeApp https://review.openstack.org/576833
12:34:05 openstackgerrit Merged openstack-infra/shade master: add release notes to README.rst https://review.openstack.org/576756
13:05:08 mnaser mordred: do you wanna re-workflow this to avoid the trip through check/gate? https://review.openstack.org/#/c/574747/
13:14:48 mordred mnaser: yup
13:14:50 mordred mnaser: done
13:17:43 mnaser mordred: cool thanks
13:27:44 openstackgerrit Telles Mota Vidal Nóbrega proposed openstack/python-openstackclient master: Adding api_version to FakeApp https://review.openstack.org/576833
13:47:05 openstackgerrit Merged openstack/openstacksdk master: Support port binding extended attributes for querying port https://review.openstack.org/573645
14:55:42 cdent edleafe, elmiko, dtantsur : question about error codes (of the "code": "placement.undefined_code" sort defined in the errors guideline)
14:56:20 cdent this one : http://specs.openstack.org/openstack/api-wg/guidelines/errors.html
14:57:27 cdent there are three different kinds of 404 one could get: /foobar is a url that never existed and never will, /reshaper is a url that exists but is a 404 at the current microversion, /resource_provider/some_uuid is that there is no resource provider with that uuid
14:57:45 cdent 404 is intentionally ambiguous about these differences
14:57:59 cdent should the error code clarify or mantain the ambiguity?
15:08:39 mordred cdent: clarify
15:09:12 cdent i'm leaning that way too
15:09:20 mordred cdent: one of my biggest complaits about early openstack deployments was that people would shut api calls off with policy and then have them return 404 as if the API wasn't a publically documented thing anyway
15:09:28 mordred but while this isn't related to that
15:09:55 mordred the failure case was similar - which is that as a user I wasn't sure if I'd made a mistake in constructing my url or if a resource didn't exist
15:10:11 mordred ( did I do /server/foo when I should have done /servers/foo ? )
15:11:04 mordred SO - if there was a clarifying code in the response body "route /server is unknown" vs "server foo doesn't exist" you know
15:11:23 dtantsur ++ for clarifying as much as possible
15:11:50 mordred I think it might also make sense to indicate that it's in-game to update error responses for older microversions
15:12:00 mordred and that that's not an API break ...
15:12:28 mordred (so that you can potentially do the thing you mentioned - this route isn't valid in this microversion)
15:13:39 cdent i now have a todo item
15:13:45 cdent small but important progress or something
15:36:08 dhellmann dtroyer : I sat down a couple of weeks ago to look at ripping cmd2 out of cliff, but got bogged down in the amount we seem to rely on its differences in interactive mode.
15:36:10 dhellmann :-/
15:38:48 dtroyer interactive mode is one of those things that if you use it you'll miss it but I don't think the majority of OSC users use it
15:39:12 dtroyer I did start converting DevStack to use it more a while back to try and sidestep the startup time issue
15:39:25 dtroyer piping in a list of commands
15:39:45 gtema I am a total fan of interactive mode
15:39:50 dtroyer if we decide to rip it out, OSC4 would be the time
15:40:05 dtroyer ya, I really like it, which is why it exists
15:40:38 dtroyer really, the issue comes down to the 2 or 3 times a year cmd2 causes us to have to jump and if the effort of changing is worth it
15:41:29 openstackgerrit Merged openstack/cliff master: support cmd2 0.9.1 in interactive mode https://review.openstack.org/571524
15:48:59 edleafe cdent: sorry, today is meeting hell for me.
15:49:29 cdent edleafe: I forgive you
15:49:40 edleafe cdent: I'm all for clarity in error codes, so if it is possible to help the user with more information, +1 from me
16:04:07 openstackgerrit Ken Giusti proposed openstack/cliff master: Add test case for interactive help https://review.openstack.org/576900
16:31:33 openstackgerrit Monty Taylor proposed openstack/openstacksdk master: Adds Senlin support to openstacksdk https://review.openstack.org/576650
16:32:31 mordred dtantsur: ^^ I just went in an cleaned up the things you pointed out (except for docstrings)
16:33:15 dtantsur cool!
16:34:12 mordred dtantsur: thanks for that review, btw - my eyeballs had glazed over and missed those :)
16:34:20 dtantsur np :)
16:57:47 elmiko cdent: little late to the party, but i agree with the clarify position
21:21:54 flwang mordred: hello, I have some questions about Magnum support in Shade
21:23:16 flwang mordred: i can see shade is still using old "baymodels", so is there any plan to support the new cluster templates? I would like to contribute but just wanna figure out the deprecation process, thanks
22:55:39 mordred flwang: it shuld also have calls that look like get_cluster_template api calls - but yes, they call the older baymodel endpoint
22:56:31 mordred flwang: I'd love help making the magnum support better though
22:57:04 mordred flwang: is there a way to detect of baymodel or cluster_template should be used?

Earlier   Later