Earlier  
Posted Nick Remark
#openstack-sdks - 2017-03-06
17:17:44 openstackgerrit Nakul Dahiwade proposed openstack/python-openstackclient master: OSC Network Flavor Profile https://review.openstack.org/396783
17:18:54 openstackgerrit Nakul Dahiwade proposed openstack/python-openstackclient master: OSC Network Flavor Profile https://review.openstack.org/396783
18:05:38 cdent sdague: I made a new version of the stability guideline and there's an open question on how to deal with experimental stuff on the penultimate patchset in which I invoke you, but I didn't have enough of the memory: https://review.openstack.org/#/c/421846/
18:06:02 sdague cdent: ok, open and starred, I'll look later
18:06:12 cdent cool, thanks
18:18:35 openstackgerrit Merged openstack/osc-lib master: Avoid 'NoneType' error when format conversion https://review.openstack.org/434768
18:20:28 thingee dtroyer_zz: glancing at the current review queue, don't see anything
18:31:46 openstackgerrit Merged openstack/python-openstacksdk master: Reorganize block store docs https://review.openstack.org/438993
18:32:05 openstackgerrit Merged openstack/python-openstacksdk master: Reorganize network docs https://review.openstack.org/439074
18:32:11 openstackgerrit Merged openstack/python-openstacksdk master: Reorganize object_store docs https://review.openstack.org/439093
18:33:45 openstackgerrit Merged openstack/python-openstacksdk master: Reorganize telemetry docs https://review.openstack.org/439020
18:49:01 openstackgerrit Steve Martinelli proposed openstack/python-openstackclient master: add neutron CLI to decoder https://review.openstack.org/439148
20:09:33 openstackgerrit Ankur proposed openstack/python-openstackclient master: Trivial Fix https://review.openstack.org/442146
20:21:12 openstackgerrit Shashank Kumar Shankar proposed openstack/python-openstackclient master: Introduce Neutron DHCP agent commands to OSC https://review.openstack.org/387611
20:22:14 openstackgerrit Dean Troyer proposed openstack/python-openstackclient master: Cleanup release notes for 3.9.0 release https://review.openstack.org/442150
20:26:12 openstackgerrit Dean Troyer proposed openstack/python-openstackclient master: OSC Quota List https://review.openstack.org/379813
20:27:05 stevemar dtroyer_zz: lets get server action into next OSC release :P
20:27:49 dtroyer_zz stevemar: by next you mean not today/tomorrow?
20:28:59 stevemar dtroyer_zz: womp womp
20:29:17 stevemar dtroyer_zz: i didn't know you were targeting one for today/tomorrow
20:29:22 stevemar won't make it then
20:30:00 dtroyer_zz We need to get the SDK session change fixes out since SDK 0.9.14 released last week
20:30:17 dtroyer_zz I just pushed up the release notes cleanup
20:30:40 dtroyer_zz trying to sort out why our -tips job is failing now
20:31:04 stevemar dtroyer_zz: can you +A the network decoder code too? i didn't realize our docs page only refreshes after we release
20:31:22 dtroyer_zz yes, that's where I saw the -tips job fail...
20:44:17 openstackgerrit Shashank Kumar Shankar proposed openstack/python-openstackclient master: Introduce neutron flavor associate, disassociate to OSC https://review.openstack.org/403907
21:31:37 openstackgerrit Merged openstack/python-openstackclient master: Normalize the gnocchiclient docs entry https://review.openstack.org/441889
21:38:28 openstackgerrit Merged openstack/python-openstackclient master: Trivial Fix https://review.openstack.org/441542
21:49:49 openstackgerrit Steve Martinelli proposed openstack/python-openstackclient master: Cleanup release notes for 3.9.0 release https://review.openstack.org/442150
21:50:34 openstackgerrit Merged openstack/python-openstackclient master: add neutron CLI to decoder https://review.openstack.org/439148
21:55:47 openstackgerrit Shashank Kumar Shankar proposed openstack/python-openstackclient master: Introduce neutron flavor associate, disassociate to OSC https://review.openstack.org/403907
23:23:46 thingee ankur-gupta-f1: are you able to restore this https://review.openstack.org/#/c/330027/3 ? Spoke to dhellmann and sdague about this and I think we can continue with the current ini approach
23:24:52 thingee ankur-gupta-f1: related http://lists.openstack.org/pipermail/openstack-dev/2017-March/113173.html
23:30:59 ankur-gupta-f4 thingee: yes will spin up again. Give me till tmw?
23:36:45 thingee ankur-gupta-f4: yes thank you
23:37:21 thingee ankur-gupta-f4: I've replied to thread in hopes smcginnis and mugsie will join in with cinder and desginates part in this
23:55:40 openstackgerrit Merged openstack/python-openstackclient master: Trivial Fix https://review.openstack.org/442146
#openstack-sdks - 2017-03-07
00:41:24 openstackgerrit Merged openstack/python-openstackclient master: Cleanup release notes for 3.9.0 release https://review.openstack.org/442150
02:04:22 openstackgerrit OpenStack Proposal Bot proposed openstack/osc-lib master: Updated from global requirements https://review.openstack.org/440084
02:06:00 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstackclient master: Updated from global requirements https://review.openstack.org/442229
02:26:59 adriant dtroyer_zz, when you're about, can you take a gander at: https://review.openstack.org/#/c/376056/ please :)
04:55:14 openstackgerrit Merged openstack/python-openstackclient master: Updated from global requirements https://review.openstack.org/442229
05:09:37 openstackgerrit Adrian Turjak proposed openstack/python-openstackclient master: Non-Admin can't list own projects https://review.openstack.org/376056
05:16:06 openstackgerrit Adrian Turjak proposed openstack/python-openstackclient master: Non-Admin can't list own projects https://review.openstack.org/376056
06:43:32 dasanind reedip_: reviewed ur patch https://review.openstack.org/383025
07:27:21 openstackgerrit Rui Chen proposed openstack/python-openstackclient master: Add server event list and show commands https://review.openstack.org/441775
07:51:19 reedip_ thanks dasanind :)
11:42:02 reedip_1 o/
12:28:11 openstackgerrit kavitha h r proposed openstack/cliff master: Python 3.4 support is removed https://review.openstack.org/442419
12:35:04 sdague cdent: I went through - https://review.openstack.org/#/c/421846
12:35:40 sdague I'd be good with it landing as is, but there is a comment towards the end
12:36:00 sdague that I'm not sure i want to encourage people to do a thing which is going to be fragile
12:37:26 cdent That was something that was, weirdly, a revelation to people in the room when we were discussing things
12:37:44 cdent there was fear that you couldn't go backwards in time once you go forwards in time on the the client side
12:38:02 cdent so we decided _something_ should be put in the doc that made it more clear
12:38:08 cdent but what's there may not be the right something
12:38:47 cdent sdague: did you see the stuff on the earlier patchset about experimental? any concerns/thoughts there?
12:39:34 sdague cdent: I didn't look at earlier revisions, I think what is in the current revision of the doc is what we recommended in the room
12:39:58 cdent and no more details required?
12:40:12 sdague cdent: I'm fine with that.
12:41:28 cdent cool, thanks for passing your eyes over it
12:42:36 sdague so, I honestly think we probably just need a different document on best practices on writing clients.
12:43:31 sdague because the audience for this document isn't really going to overlap with that audience much
12:43:37 sdague besides like a mordred
12:56:03 cdent sdague: yeah, that's probably a reasonable point. I just wanted to make sure it got down somewhere for people to look at so we could make that decision
12:56:22 cdent having a different doc is a good idea
12:58:40 sdague I have to admit, playing with this blockdiag markup for the quota models doc has also given me some thoughts about effective diagramming for the microversion consumers guide
13:23:11 cdent sdague: that would be cool
13:52:03 dtroyer_zz stevemar: are you travelling today?
14:04:03 dave-mccowan Hello API WG. I have some questions about micro-versions and how to use them. Is now a good time?
14:08:31 cdent dave-mccowan: I can try to help, now, but if we can't figure it out a post to the os-dev list or coming to the meeting on thursday might help. What's up?
14:09:25 dave-mccowan this is for Barbican. During the Pike cycle, we'd like to make a few changes to our API, and I want to make sure to do it right. I think micro versions is the way to go.
14:10:32 dave-mccowan 1) we want to add a field to several of our responses, 2) we'd like to create an alias for one of our resources, 3) we'd like to start deprecating a resource that we announced we would deprecate last cycle.
14:11:25 dave-mccowan first... can all of those things be done as part of a microversion. next... is there a doc somewhere describing how to do a microversion?
14:12:44 cdent dave-mccowan: there's a couple of things that might be useful:
14:13:06 cdent this is the microversion spec http://specs.openstack.org/openstack/api-wg/guidelines/microversion_specification.html which describes how they are supposed to work
14:13:38 cdent there is a review of the guidelines for when a microversion is needed here: https://review.openstack.org/421846
14:14:47 cdent and looking at the commit log for how placement implemented microversions might be useful (as it was a recent implementation) https://github.com/openstack/nova/commits/master/nova/api/openstack/placement/microversion.py
14:16:24 cdent dave-mccowan: to answer your questions more directly: yes, adding a field is a common microversion thing; not quite sure what you mean by alias so not sure about that; deprecating a resource is okay, but generally the concept with stability is that you keep something in the api as long as possible, even in its deprecated state
14:16:41 cdent with microversions you raise the minimum version if you want to fully get rid of something
14:17:11 dave-mccowan cdent thanks.
14:17:29 dave-mccowan cdent for my "alias" question, here's what i have in mind. i'd be happy to hear any advice.
14:17:32 cdent is that sufficient to get you started?
14:18:26 dave-mccowan cdent in barbican we have a resource called "container". sadly, this term has taken on a very popular non-related definition, so we'd like to rename it to something else. (bundle/group/??)
14:18:43 cdent :)
14:19:08 openstackgerrit Ian Cordasco proposed openstack/keystoneauth master: Allow new cassettes to be recorded via fixture https://review.openstack.org/442516
14:19:09 dave-mccowan would making an alias for "container", and responding to both GET /container/ and GET /group/ be an OK thing to do?
14:19:34 cdent yes, but you could also consider a redirect
14:20:30 sigmavirus mordred: could you take a gander at ^
14:20:44 dave-mccowan cdent ah... redirect. i like it.
14:21:09 cdent dave-mccowan: especially if it is just a GET the impact should be low
14:21:30 cdent I know that in ceilometer when they moved alarms out of ceilo to aodh they did a special kind of redirect that also works for POST
14:21:40 cdent 307 if I remember right
14:21:58 cdent or mayb 308
14:22:32 dave-mccowan cdent for the deprectated question... is there a recommended response for a deprecated resource? is there something better than 404?
14:23:25 cdent If it is deprecated, that means it still works but will stop working at some point, so 404 is no good. There's not been a plan for how it would work other than docs.
14:23:45 cdent But if you have a microversion that removes the functionality then in the older microversion it works, and in the newer microversion it is 404
14:24:19 cdent if you want to say in the body of the 404 response "this doesn't work in this microversion" that would be up to you
14:26:22 dave-mccowan cdent this will get me started. i'll put our plans in a spec and advertise it to the api-wg for review. thanks!

Earlier   Later