Earlier  
Later
New Search
Posted Nick Remark
#openstack-sdks - 2017-04-20
16:30:24 mordred cdent: why would you get the idea that I'm not on a bull
16:30:26 mordred ?
16:31:14 cdent because, though you are a talented person, version discovery is so complex that anyone who is attempting to comprehend it, while on a bull, is no longer on the bull
16:32:06 edleafe mordred: ok, will review and add some acerbic comments
16:32:13 mordred cdent: maybe it would be proof of my acumen if I could perform version discovery correctly whilst upon a bull?
16:32:19 mordred edleafe: sweet!
16:32:24 mordred or, sour perhaps
16:32:50 cdent (and yes, I reckon not for api-wg repo because we want to describe how things should be (although some state of the are description used to be the norm))
16:32:58 edleafe mordred: definitely bitter
16:32:58 mordred cdent, edleafe: also have a followup patch which has thoughts on how we're going to consume microversions in shade
16:33:00 cdent mordred: I think you've figured out your next keynote presentation
16:33:08 mordred cdent: zomgyes
16:33:22 cdent [...] on a bull!
16:33:34 mordred they did not accept my talk for this summit about making BBQ
16:33:51 mordred I'm starting to think I can't get talks on absurd topics accepted purely on name recognition!
16:33:52 cdent making BBQ while on a bull smacks of ethics violation
16:35:07 edleafe yes, too recursive
16:35:19 edleafe unless you are barbecuing a pig, of course
16:35:30 openstackgerrit Dean Troyer proposed openstack/osc-lib master: Revert "Avoid to authenticate twice" https://review.openstack.org/458586
16:37:18 mordred edleafe: I should figure out how to make fake beef out of pork, and fake pork out of beef - and maybe fake coleslaw out of chicken
16:40:05 dtroyer_zz mordred: I'm tackling version/microversion stuffs in OSC too, if I can ever unwind the release madness+client code removal we're in, will try to get that all back into my head this afternoon to compare notes
16:40:23 dtroyer_zz I don't mind duplicating the REST bits, we're doing different things there, but let's make only one of these
16:40:29 edleafe cdent: elmiko: so do you think that adding an email address field to the liaisons.json file is worthwhile?
16:40:51 mordred dtroyer_zz: yah - so I started working on some patches for keystoneauth yesterday
16:40:59 mordred dtroyer_zz: because ksa actually does some of this already
16:41:00 cdent edleafe: it can be useful, but i think it is also possible to extract it from gerrit using the name?
16:41:07 cdent so I dunno
16:41:32 dtroyer_zz mordred: right, I have some bits too that are not yet proposed… distilled from the <sorry> nova & cinder clients
16:41:33 mordred dtroyer_zz: however, I'm not 100% sure I can sell the whole thing at the ksa layer, becaues it starts to get a smidge invasive
16:41:55 mordred dtroyer_zz: maybe if we can at least come to a general agreement on what the overall algorithm should be
16:41:57 dtroyer_zz it does. I think jamielennox is on-board for some of the lower-layer stuff, but not all of it
16:42:13 mordred we can then figure out how much can live in ksa and now much is impl specifics for shade/osc
16:42:15 edleafe cdent: maybe - haven't played much with the gerrit API
16:42:36 mordred dtroyer_zz: please tell me whence you find one!
16:53:20 mordred dtroyer_zz: but any way - if you could find time to look at that shade doc patch and see if you disagree on any fundamental points, that would be cool
16:53:51 mordred dtroyer_zz: I could potentially do a pass through it to talk about it in terms of general discovery and then how shade specifically wants to interact with such a thing
16:53:59 mordred if it winds up being too shade-centric
16:54:56 dtroyer_zz I'm curious to see how similar we want to handle versions, the discovery should be close, it's the philosophy on using microversions that may be different
16:55:22 dtroyer_zz I want to let each command make that decision as much as possible
17:04:47 mordred dtroyer_zz: yes. that's exactly how I want to handle microversions
17:05:20 mordred but I left microversions as a followup document, since the thing I actually need to solve in shade soon is a more generic major version discovery
17:06:12 mordred dtroyer_zz: oh - also, one of the goals of the process/approach in that document is to allow us to get rid of the default values for api versions in occ
17:06:36 dtroyer_zz \o/
17:06:52 mordred doing that curently would screw some things, but if I can get generic discovery working consistently and overridably when needed, then we can get rid of them
17:07:31 mordred (which is one of the things that I think will wind up being invasive ksa-side - currently it'll handle doing discovery, but you have no idea what version it actually discovered)
17:09:04 openstackgerrit Merged openstack/cliff master: Add smart help formatter for command parser https://review.openstack.org/454613
17:17:51 stevemar dtroyer_zz: shouldn't be a big deal about missing that one, Rui's patch only refactored things right?
17:18:24 rukh ping openstack-sdks: Looking at this https://developer.openstack.org/sdks/python/openstacksdk/users/resources/orchestration/v1/resource.html#openstack.orchestration.v1.resource.Resource I was able to get the physical_resource_id for the "Controller" resource and I think must be additional resources associated with this physical id .. I see the class this inherits from has a list() function. but I don't think I can access it like this:
17:18:26 rukh resources = self.conn.orchestration.resources(stack)\
17:18:30 rukh resources = self.conn.orchestration.resources(stack)
17:19:30 rukh resource_id = resource.physical_resource_id
17:20:02 rukh Controller)
17:20:02 rukh node = resources.get(resource_id,
17:20:53 rukh is it possible to access the base class resource members ?
17:21:29 edleafe rukh: since this is Python, yes
17:21:59 edleafe rukh: Also, when posting more than a line or two of code, using a paste service helps make the code more readable
17:22:08 edleafe and doesn't clutter the channel
17:22:16 rukh edleafe, apologies..
17:22:18 openstackgerrit Dean Troyer proposed openstack/osc-lib master: Add token auth test https://review.openstack.org/458597
17:22:24 edleafe rukh: no worries
17:22:46 dtroyer_zz stevemar: can you look at ^^^ and the associated revert if you have a minute?
18:15:59 openstackgerrit Carlos Goncalves proposed openstack/python-openstacksdk master: Add data plane status support to Network Port obj https://review.openstack.org/458608
18:47:22 openstackgerrit Dean Troyer proposed openstack/python-openstackclient master: Correct auth issue in master os-client-config" https://review.openstack.org/458615
18:57:37 openstackgerrit Merged openstack/python-openstacksdk master: Add data plane status support to Network Port obj https://review.openstack.org/458608
19:20:38 openstackgerrit Carlos Goncalves proposed openstack/python-openstackclient master: Add 'data_plane_status' option to Port classes https://review.openstack.org/458626
20:11:37 openstackgerrit Merged openstack/keystoneauth master: Updated from global requirements https://review.openstack.org/455926
20:18:09 openstackgerrit Merged openstack/osc-lib master: Revert "Avoid to authenticate twice" https://review.openstack.org/458586
20:18:16 openstackgerrit Merged openstack/osc-lib master: Add token auth test https://review.openstack.org/458597
20:26:44 rukh ping openstack-sdk: Am a little stuck: https://pastebin.com/n21Ymxnf was able to get the resource_id for the Controller resource but having trouble getting further to get the nodes associated with that resource
20:27:22 briancurtin if you’re using heatclient you may be better off asking in #openstack-heat
20:29:28 rukh briancurtin, I am actually moving that code since the clients I read are deprecated to use the openstack sdk calls
20:29:58 briancurtin i don’t know that they’re actually deprecated. is that documented somewhere?
20:34:51 rukh I might have understood "access to legacy clients" as deprecated just like the individual cli clients are deprecated but
20:46:36 openstackgerrit Carlos Goncalves proposed openstack/python-openstackclient master: Add 'data_plane_status' option to Port classes https://review.openstack.org/458626
#openstack-sdks - 2017-04-21
00:53:11 chatter29 hey guys
00:53:14 chatter29 allah is doing
00:53:18 chatter29 sun is not doing allah is doing
00:53:22 chatter29 to accept Islam say that i bear witness that there is no deity worthy of worship except Allah and Muhammad peace be upon him is his slave and messenger
09:23:44 openstackgerrit David Rabel proposed openstack/python-openstackclient master: Make test_server.py more elegant and simple https://review.openstack.org/458785
09:38:02 openstackgerrit David Rabel proposed openstack/python-openstackclient master: Make test_server.py more elegant and simple https://review.openstack.org/458785
11:06:48 openstackgerrit David Rabel proposed openstack/python-openstackclient master: Make test_server.py more elegant and simple https://review.openstack.org/458785
11:43:26 mordred edleafe: what? you can't just casually read that giant thing? but discovery is so simple ...
12:05:22 cdent mordred: I haven't read that thing yet, and I'm not sure I can promise to get it today because it is sunny and warm for once and I feel like I may deserve a break today. I may seek out livestock to sit on.
12:06:32 dtroyer_zz cdent: take that break before officially assuming your new task list… congrats
12:07:02 cdent thanks dtroyer_zz
12:12:03 mordred cdent: you should always sit on livestock!
12:12:12 mordred cdent: and yes, also, congrats!
12:12:34 cdent "A chicken in every pot, a bull under every butt."
12:12:49 mordred cdent: if you can't get to it today, no worries. edleafe has suggested that he thinks it actually is appropriate to submit to the api-wg repo (with a little bit of genericizing)
12:13:09 mordred so I may just work on that a little bit before you get to it anyway
12:13:46 cdent ah, well, cool
12:14:05 cdent the api-wg shall grow to consume all guidelines on how be midly sane
12:14:12 mordred (I replied ot him that I think there are maybe three documents a) how discoverability _should_ work at a perfect point in the future b) how clients can properly consume discoverability today c) any additional things shade does on top of b
12:15:11 mordred and if we have b, we can highlight with a the value of services implementing the guidelines "look at the fewer calls / less work in the client algorithm if you do discoverability corectly"
12:15:56 mordred anywho - I'll work on an edit nad send it to your repo - also, de-shadifying it a little might help dtroyer_zz to tell me what's broken in it from his pov too
12:16:21 dtroyer_zz mordred: I'm about 3/4 through it, fwiw, and only two comments so far
12:16:59 cdent mordred: a and b sound very api-wg useful
12:22:45 cgoncalves can we get a new release of osc-lib (>1.4.0) so that we can get https://review.openstack.org/#/c/458586/ ? all patch sets are failing to verify with osc-lib==1.4.0
12:24:33 dtroyer_zz cgoncalves: I submitted it last night: https://review.openstack.org/458652 will ping release team again
12:25:10 mordred dtroyer_zz: woot!

Earlier   Later