Monday, 2017-04-03

*** jkilpatr has quit IRC00:04
*** reedip has joined #openstack-sdks00:25
*** bobh has joined #openstack-sdks00:38
*** bobh has quit IRC00:44
*** erlon has quit IRC00:45
*** jamielennox|away is now known as jamielennox01:06
*** hoangcx has joined #openstack-sdks01:13
*** reedip has quit IRC01:40
*** reedip has joined #openstack-sdks01:59
reedipo/02:04
ankur-gupta-f4reedip: dont file bug. Only if there was existing. But its just a refactor so its fine02:06
reedipankur-gupta-f4 : were u just waiting for me with that response already typed ???? :D02:07
reedipI am not filing a bug :) , dont worry :P02:07
ankur-gupta-f4No just rmred u commented on patch02:08
ankur-gupta-f4N saw u wave02:08
reedip:D02:09
openstackgerritSean McCully proposed openstack/keystoneauth master: KeystoneAuth should default to system CAFile.  https://review.openstack.org/45258502:21
*** amotoki has joined #openstack-sdks02:39
*** gouthamr has quit IRC02:41
*** dave-mccowan has joined #openstack-sdks02:55
*** dave-mcc_ has quit IRC02:57
*** john-davidge has joined #openstack-sdks02:58
*** amotoki has quit IRC03:00
*** john-davidge has quit IRC03:03
*** dave-mccowan has quit IRC03:05
openstackgerritSean McCully proposed openstack/keystoneauth master: KeystoneAuth should default to system CAFile.  https://review.openstack.org/45258503:10
*** amotoki has joined #openstack-sdks03:20
*** amotoki has quit IRC03:29
*** amotoki has joined #openstack-sdks03:38
*** reedip has quit IRC03:52
*** reedip has joined #openstack-sdks04:00
*** Dinesh_Bhor has joined #openstack-sdks04:01
*** amotoki has quit IRC04:01
*** amotoki has joined #openstack-sdks04:08
*** annp has joined #openstack-sdks04:28
openstackgerritSean McCully proposed openstack/keystoneauth master: KeystoneAuth should default to system CAFile.  https://review.openstack.org/45258505:06
*** hoangcx has quit IRC05:28
*** e0ne has joined #openstack-sdks05:45
*** e0ne has quit IRC05:52
*** adriant has quit IRC05:55
*** IRCFrEAK has joined #openstack-sdks05:57
*** IRCFrEAK has left #openstack-sdks06:00
*** yuanying has quit IRC06:07
*** yuanying_ has joined #openstack-sdks06:13
*** e0ne has joined #openstack-sdks06:23
*** e0ne has quit IRC06:24
openstackgerritSean McCully proposed openstack/keystoneauth master: KeystoneAuth should default to system CAFile.  https://review.openstack.org/45258506:26
openstackgerritReedip proposed openstack/python-openstackclient master: Add extra dhcp option to 'port create/set/unset'  https://review.openstack.org/35626306:31
*** bobh has joined #openstack-sdks06:37
*** bobh has quit IRC06:42
*** ralonsoh has joined #openstack-sdks06:43
reedipRuiChen : I updated the Floating IP Patch, awaiting your  review :)06:48
*** Cagelin has joined #openstack-sdks06:57
*** Cagelin has quit IRC07:04
*** Serlex has joined #openstack-sdks07:29
*** amotoki_ has joined #openstack-sdks07:41
*** prg3 has quit IRC07:42
*** prg3 has joined #openstack-sdks07:43
*** amotoki has quit IRC07:44
*** fzdarsky has joined #openstack-sdks07:50
*** jpich has joined #openstack-sdks08:00
*** openstackgerrit has quit IRC08:03
*** e0ne has joined #openstack-sdks08:08
*** reedip has quit IRC08:28
*** bobh has joined #openstack-sdks08:38
*** bobh has quit IRC08:43
*** john-davidge has joined #openstack-sdks08:51
*** ssbarnea has joined #openstack-sdks08:51
*** reedip has joined #openstack-sdks09:08
*** openstackgerrit has joined #openstack-sdks09:12
openstackgerritSamriddhi proposed openstack/keystoneauth master: Updated inconsistent value of scope parameter  https://review.openstack.org/45265209:13
*** cdent has joined #openstack-sdks09:14
*** amotoki_ has quit IRC09:25
ZZelle_ok10:03
*** annp has quit IRC10:22
*** sdague has joined #openstack-sdks10:23
reedipRuiChen : there?10:31
*** john-davidge has quit IRC10:46
openstackgerritReedip proposed openstack/python-openstackclient master: Add extra dhcp option to 'port create/set/unset'  https://review.openstack.org/35626310:57
*** jkilpatr has joined #openstack-sdks11:01
openstackgerritCedric Brandily proposed openstack/osc-lib master: Avoid to authenticate twice  https://review.openstack.org/45271111:06
*** john-davidge has joined #openstack-sdks11:22
openstackgerritJens Rosenboom proposed openstack/python-openstackclient master: Fix block-device-mapping when volume_size is empty  https://review.openstack.org/45143211:26
*** john-davidge has quit IRC11:27
*** thingee has quit IRC11:36
*** bobh has joined #openstack-sdks11:37
*** dhellmann has quit IRC11:42
*** dhellmann has joined #openstack-sdks11:42
*** thingee has joined #openstack-sdks11:49
*** elmiko_ is now known as elmiko12:19
*** gouthamr has joined #openstack-sdks12:21
*** ssbarnea has quit IRC12:23
*** thingee has quit IRC12:27
*** bobh has quit IRC12:27
reedipankur-gupta-f4 : woke up ?12:29
*** ssbarnea has joined #openstack-sdks12:29
reedipsindhu : there ?12:29
*** thingee has joined #openstack-sdks12:44
*** edleafe- is now known as edleafe12:51
openstackgerritDirk Mueller proposed openstack/cliff master: .gitignore: Ignore eggs  https://review.openstack.org/44974012:53
openstackgerritReedip proposed openstack/python-openstackclient master: Add extra dhcp option to 'port create/set/unset'  https://review.openstack.org/35626313:02
*** john-davidge has joined #openstack-sdks13:06
*** john-davidge has quit IRC13:11
*** cleong has joined #openstack-sdks13:11
*** thingee has quit IRC13:23
*** dhellmann has quit IRC13:24
*** thingee has joined #openstack-sdks13:25
*** dhellmann has joined #openstack-sdks13:25
*** fzdarsky has quit IRC13:43
*** fzdarsky has joined #openstack-sdks13:51
*** hongbin has joined #openstack-sdks13:53
*** jkilpatr has quit IRC14:02
*** bobh has joined #openstack-sdks14:03
*** amotoki has joined #openstack-sdks14:05
*** reedip has quit IRC14:13
*** amotoki has quit IRC14:25
*** reedip has joined #openstack-sdks14:26
*** bobh has quit IRC14:30
sindhureedip: hey wass up14:37
reediphey hi , small issue with unicode in the functional test of https://review.openstack.org/35626314:38
reedipsindhu : the unset command fails to find the dict in the list of dicts in https://review.openstack.org/#/c/356263/23/openstackclient/network/v2/port.py  L#98714:40
reedipcant think straight as of now, if you have some time to day, would be great if you can tell me how to ignore the unicodes14:41
reedipunicode mismatch is the only issue, the items are in the correct value14:41
sindhureedip: cool, will look into it today :)14:42
reedipgr8 thanks :)14:42
*** chlong has joined #openstack-sdks14:45
*** ZZelle_ has quit IRC14:46
*** bobh has joined #openstack-sdks14:56
ankur-gupta-f4reedip: good evening14:58
*** amotoki has joined #openstack-sdks14:59
*** corey__ has joined #openstack-sdks15:05
reedipankur-gupta-f4 : hello15:05
*** cleong has quit IRC15:05
*** john-davidge has joined #openstack-sdks15:07
*** john-davidge has quit IRC15:12
*** dave-mccowan has joined #openstack-sdks15:21
openstackgerritReedip proposed openstack/python-openstackclient master: Add extra dhcp option to 'port create/set/unset'  https://review.openstack.org/35626315:23
reedipsindhu : also need to get this merged so that the floating IP merges https://review.openstack.org/44793815:23
*** Serlex has quit IRC15:24
sindhureedip: yes, the change in SDK won't help us now like u mentioned15:25
reedipyeah , so thats why want this to be merged so that the floating ip change merges soon15:25
sindhuyeah, I agree :)15:27
*** annegentle has joined #openstack-sdks15:28
*** amotoki has quit IRC15:39
openstackgerritStephen Finucane proposed openstack/cliff master: WIP: Add 'cliff' Sphinx directive  https://review.openstack.org/45032215:44
*** stevelle has left #openstack-sdks15:52
*** e0ne has quit IRC15:57
openstackgerritEd Leafe proposed openstack/api-wg master: Recommend the correct HTTP method for tags  https://review.openstack.org/45153616:02
*** cdent has quit IRC16:11
openstackgerritMerged openstack/cliff master: .gitignore: Ignore eggs  https://review.openstack.org/44974016:17
*** jkilpatr has joined #openstack-sdks16:18
*** d0ugal has quit IRC16:19
openstackgerritStephen Finucane proposed openstack/cliff master: Add 'cliff-command' Sphinx directive  https://review.openstack.org/45032216:23
*** jpich has quit IRC16:24
openstackgerritDean Troyer proposed openstack/python-openstackclient master: Add help commands withouth auth in functional  https://review.openstack.org/45240716:31
openstackgerritMerged openstack/os-client-config master: Docs: add a note about rackspace API keys  https://review.openstack.org/45156316:46
openstackgerritNakul Dahiwade proposed openstack/python-openstacksdk master: Introduce L7Rule for Octavia (load balancing)  https://review.openstack.org/45283216:47
openstackgerritNakul Dahiwade proposed openstack/python-openstacksdk master: Introduce L7Rule for Octavia (load balancing)  https://review.openstack.org/45283216:53
*** annegentle has quit IRC16:53
*** e0ne has joined #openstack-sdks16:55
*** aarefiev_afk is now known as aarefiev16:56
openstackgerritShashank Kumar Shankar proposed openstack/python-openstackclient master: Introduce neutron flavor associate, disassociate to OSC  https://review.openstack.org/40390717:02
*** jkilpatr has quit IRC17:05
*** chlong has quit IRC17:05
openstackgerritAnkur proposed openstack/python-openstacksdk master: Introduce Base for Octavia (load balancing)  https://review.openstack.org/42841417:06
openstackgerritStephen Finucane proposed openstack/cliff master: Add 'cliff-command' Sphinx directive  https://review.openstack.org/45032217:06
*** john-davidge has joined #openstack-sdks17:08
openstackgerritStephen Finucane proposed openstack/python-openstackclient master: WIP! Start using 'cliff.sphinxext'  https://review.openstack.org/45286117:12
*** john-davidge has quit IRC17:13
*** d0ugal has joined #openstack-sdks17:15
*** chlong has joined #openstack-sdks17:20
*** cdent has joined #openstack-sdks17:23
cdentedleafe, elmiko : I'm cogitating on how to provide a final revision on https://review.openstack.org/#/c/421846/ (compatibility guidelines). I think I may do what I say in my last comment about "one tactic". Any thoughts?17:25
openstackgerritAnkur proposed openstack/python-openstackclient master: Network L3 Router Commands for OSC  https://review.openstack.org/38572917:25
edleafecdent: I thought the motivation for this *was* the TC tag17:29
cdentthe motivation was that they wanted to use the guidelines and they seemed bad17:29
cdentbut now that they are revised we should revise them so they are not about tags, but about the bigger thing, the mission17:30
cdentthus my statement: interoperability right there in the mission17:30
cdentif we guide to the mission, the relevancy for tags (or new tags) falls out of that, but the tags will be mission oriented, not "make some tags to deal with whatever situation is lying around"17:31
edleafeI get that, but it seems like looking at it as a single concern will make it essentially useless for the vast majority of OpenStack developers17:34
edleafeReally, I joke and call it the "Monty case", but I don't know anyone else who has such stringent requirements17:34
cdentthat's kind of the point: are we trying to describe interop or not? I felt that the outcome from a) the ptg, b) the discussion on the document and c) look at TheMission is that we are. If we are, then the implications are _severe_17:35
cdentand thus the document needs to be pretty explicit about just how difficult things are, and the things to look out for17:35
elmikoi'm having a difficult time following the action item here, are we still trying to figure how to mention alternatives without blessing them?>17:37
cdentelmiko: no, more general than that: get something published that is actionable17:37
elmikocdent: ok, cool. i thought we were in the weeds about that.17:38
cdented pointed out a few more contradictions and issues in his comments shortly before my last one17:38
edleafeI felt that the PTG was really a non-outcome, because we didn't have the two factions talking with each other17:38
elmikoi agree with the sentiment that using these guidelines as the bar for a tag is problematic at best17:38
edleafeelmiko: so how would the TC determine if a project has earned that tag?17:39
elmikoedleafe: i guess it depends a little on the conversation here17:39
elmikolike for example17:39
cdentedleafe: I don't quite agree (about PTG). I think we established that there were some people who did not want to prioritize service wide interoperability and stability and that's okay, but that if you do, there are consequences17:40
elmikoif the guidelines are about the mission and interop, then maybe we need a document that clearly defines what you need for the tag (ugh, more docs)17:40
elmikobut, if the guidelines *are* about the tag, then we need to be more explicit i suppose17:40
elmikoi have to admit, i feel we have gotten so far zoomed in as a result of one issue that i'm having trouble placing all this into the "bigger picture" as stated above17:41
edleafecdent: hence my blog post. The morning group was concerned with moving an API forward without breaking clients. They really showed no concern for interop at the level that Monty et al did in the afternoon17:41
cdentedleafe: hence my suggestion of renaming this document to interoperability guidelines and being able to publish that as a step in a potentially multi-step process17:42
cdent(elmiko, yes, it's hard to tell where to focus)17:42
elmikocdent: that seems like a sensible option to me17:43
edleafecdent: So this would be an "api-interoperability" guiddeline, and there would be another, similar "api-compatibility" guideline? Or just the former and forget about the latter?17:43
cdentdo the former, and if there is demand and/or time do the latter17:44
cdenti'm not sure if there is demand for the latter, but there was clearly demand for the former because people we're wielding the older (incomplete) guideline as a weapon17:45
elmikoouch17:45
cdentwere17:46
edleafeI think that the latter would be more widely useful OpenStack-wide in improving APIs17:46
cdentbecause I know edleafe is watching out for such things17:46
elmikoit's starting to sound like the tag should really be "api-interop" focused then?17:46
elmikoedleafe: ++17:46
edleafecdent: I let that one slide17:46
edleafeNot many projects will implement microversions and be as strict about them as interop requires17:47
cdentedleafe: how do you react to the assertion that forward stability/compatibility is impossible in the kind of environment that openstack projects exist in?17:47
cdentor the other assertion, held by some, that if you're not concerning yourself with interop you shouldn't be openstack?17:47
edleafeBut I can see many projects improving their versioning (*cough* glance *cough*) to at least not break clients17:47
elmikolol17:48
cdenthow did microversions leak in here?17:48
edleafeImpossible? No17:48
edleafeDifficult? Sure17:48
edleafecdent: because we determined that no one knew of any versioning system that could meet the demands of interop besides microversions17:49
cdent(is proxying assertions to cover bases, I've completely lost touch with my own position on this stuff)17:49
edleafeAnd thus demanding interop means demanding microversions17:49
elmikocdent: i can totally empathize17:49
cdentif glance improved their versioning, even if they didn't use microversions™ they would still be microversions if they were selectable in some fashion17:50
*** jamielennox is now known as jamielennox|away17:50
cdentif you are doing some kind of versioning17:51
edleafeThey could adopt semver17:51
edleafe(and stick to it!)17:51
sdagueedleafe: that's actually a pretty accurate replay of what happened, we invented this thing because all the existing strategies broke down when you were talking about multiple deployments that were upgrading at independent schedules17:51
cdentand you can choose what version you want at request time (by uri, or header, content type) then you have the equivalent functionality of microversioning, and thus you have interop17:51
sdagueedleafe: I really don't think semver is meaningful for network based services17:52
sdaguebecause semver is what you use in libraries to know what you can safely upgrade to, and what you just vendor. But you can't vendor a network api. :)17:52
cdentbrb17:52
edleafesdague: the point was that there are other ways to sanely version your API other than microversions17:53
dtroyerbesides, semver is hard enough to get right that consumers can't always trust it anyway…  which is why I've come to the conclusion that I don't care _what_ you use to signal a change, just make it have an order (because ranges) and discoverable17:54
edleafeSome projects have a visceral reaction to even thinking of microversions17:54
edleafeI don't understand that, but it's there17:54
dtroyerbecause anti-Nova sentiment?17:54
edleafedtroyer: that's part of it17:55
edleafebut also because it's perceived as this huge amount of overhead17:55
cdentit's perceived as a way to keep tech debt in both client libraries and servers17:55
dtroyerheh, the overhead is thinking about the consumers of your API rathern than just treating it as write-only17:55
cdentfor some that's a valid cost, for the sake of the user, for others not so much17:56
cdentround-about-jinx17:56
edleafesdague summarized the users well in https://review.openstack.org/#/c/444892/2/guidelines/microversions-architecture.rst17:57
edleafeIt's hard to satisfy all those use cases17:58
sdagueyeh, I need to get back to that document17:58
sdagueedleafe: right, well, it is why we ended up with the microversion solution17:58
sdaguethat was our set of constraints17:58
sdaguesolve for X17:58
elmikoedleafe: i think there is another angle to avoiding microversions. for teams that are stretched or have hard downstream asks, it can be a tough load of tech debt to take on.17:59
*** d0ugal has quit IRC17:59
cdentif the current document didn't have a) any mention of microversions, b) the alternatives section what would it mean or imply for people? Would it serve a useful purpose?17:59
edleafeelmiko: can you explain what the tech debt is that is taken on?17:59
cdentit's not even debt, it's work18:00
*** aarefiev is now known as aarefiev_afk18:00
elmikoedleafe: so, imo, initially someone has to implement the handling of the microversion into the wsgi framework. additionally that knowledge needs to be communicated in a manner that will live on if the implementor disappears.18:00
sdaguecdent: what I heard in the room, it was the debt that people were concerned about. They didn't want to maintain old behaviors.18:00
*** ZZelle has joined #openstack-sdks18:01
elmikoafter it's implemented, then there is the function of keeping the older pathways working while new bits are added18:01
cdentsdague: yeah, but that's not what elmiko is talking about here18:01
sdagueright18:01
ZZelledtroyer, hi18:01
cdents/here/at first/18:01
sdaguecdent: ok18:01
edleafeelmiko: yeah, I get the initial workload to make the change, but really, any change requires work18:01
elmikoas the old paths start to rot, i've experienced a brain-drain in the area of keeping them alive when bugs do creep in *or* if there needs to changes to the overall model of the application in question.18:01
elmikoedleafe: agreed, i'm just airing my perceived drawbacks to a smaller team18:02
elmikomy largest experience is with sahara18:02
edleafeSo for a project that wants to maintain compatibility, they have to maintain the old behaviors in any event18:02
sdagueelmiko: yeh, that's definitely a concern. But the real world implications of that are that a service is just going to stop working for existing clients.18:02
sdaguewhich, makes it a hard choice for people to choose to deploy and count on18:03
elmikosdague: agreed18:03
elmikobare in mind that i'm mainly talking about projects that may not be hot-beds of openstack activity. (for example sahara)18:03
edleafeelmiko: re: bitrot - yeah, agreed. That's why I don't subscribe to the "once an API is released, you have to maintain it forever" school of thought18:03
edleafeelmiko: see: https://blog.leafe.com/api-longevity/18:04
*** ssbarnea has quit IRC18:04
sdagueedleafe: it mostly depends on who has control over the deployment18:04
sdagueso... if sahara wasn't a thing the cloud operator deployed, but a thing that I deployed in my tenant18:04
elmikoif my, downstream, employer has hot demands on what goals they would like to see for a particular cycle, it can extremely difficult to get traction for spending signifcant time doing a microversion re-write18:04
sdaguethen I've got control on the upgrade cycle18:04
sdaguewhich makes it like vendored libraries18:04
sdagueand, then I think some of these concerns go away18:05
elmikosdague: totally agree18:05
*** ssbarnea has joined #openstack-sdks18:05
elmikoin-tenant services is a fantastic idea18:05
sdaguebut when the user has no control of the upgrade schedule18:05
sdague... I have a hard time understanding a different path then the one we've taken18:06
elmikoi feel like this is an area where, due to no ones fault, there are "services" that are embedded into the control plane which would be better served as application riding on top of openshift18:06
elmikoer, openstack18:06
elmikosorry.. too many open*18:06
cdentelmiko bleeds red18:06
sdagueheh18:06
elmikoFOR THE HAT!!!!18:07
edleafesdague: I'm totally agreed on the microversion approach that nova has followed18:07
sdagueelmiko: yeh, that would have been an interesting different road to have taken18:07
* cdent gives elmiko the jokeexplainer award of the day, along with a bandaid18:07
elmikohonestly though, i've doing way more with kubernetes recently and the model of deploying "heroic" services on top the orchestration substrate is a powerful idea18:07
edleafesdague: but I'm trying to find a middle ground to help improve all OpenStack APIs, even for those projects that reject microversions18:07
elmikosdague: ack, c'est la vie ;)18:08
sdagueelmiko: I do kind of wonder if zaneb's ideas around application tokens might get us back headed towards that path18:08
elmikosdague: i have not seen that written up, but it sounds interesting18:08
cdentelmiko: https://review.openstack.org/#/c/447031/18:09
elmikocdent++18:09
sdagueedleafe: sure, I applaud that effort. However, I also feel like we've got a set of services where this matches well, and it would be nice to get that flag in the ground.18:09
cdent(in the links in the bottom)18:09
*** dhellmann has quit IRC18:10
dtroyerZZelle: hey18:10
elmikoi totally agree with the thought that for certain "core" services, mandating microversions is a much stronger idea. but that takes us away from the big tent idea18:11
*** dhellmann has joined #openstack-sdks18:11
* edleafe runs to the kitchen to grab some lunch18:11
cdent(I'm going to need to go at any moment now, I think, if there's a concrete outcome to this conversation that is germane to the doc, can somebody leave a new comment there so I can act on it?)18:12
elmikocdent: ack18:12
cdentthanks18:12
ZZelledtroyer, about your comment in https://review.openstack.org/#/c/452328/1/doc/source/command-objects/server.rst18:12
ZZelledtroyer, i am not sure to understand what you mean18:12
*** ssbarnea has quit IRC18:12
cdentI think being more specific about the scope of the doc and the rigor of the standard being set is probably a good way to go, especially if we leave open the option (we always do) for more docs later18:13
cdentThat moves the doc forward18:13
cdentbut I don't know that that helps us with what might be called the social problem.18:13
cdentbut it may be we don't need to do anything about that18:13
dtroyerits just the form of the help line, we put the '(name or ID)' test at the end pretty much everywhere, except some differences have snuck in.  Fix yours, I'll get the other ones18:14
dtroyerthere's an RST error in there too that stevemar noted but +2'd anyway18:14
ZZelledtroyer, so something like 'Server ... (name or ID).' instead of 'Server (name or ID) ...'?18:14
stevemarZZelle: yep18:15
ZZellestevemar, dtroyer good for me18:15
dtroyeryes.  look at nearly every other command in that file than the add commands near yours18:15
elmikocdent: imo, for a guideline that will define a tag, it should be as explicit as possible in terms of the hoops needed to jump through18:15
elmikoso, that may speak to having 2 separate docs18:15
*** prg3 has quit IRC18:15
cdentI remain a bit unclear on what the second doc is18:17
*** prg3 has joined #openstack-sdks18:17
elmikoi guess that would be needed if we couldn't make the first one specific enough?18:18
elmikoor just having 2 tags or something, one for interop and one for ?18:19
cdentyes, that blank is what I'm blank on18:19
openstackgerritCedric Brandily proposed openstack/python-openstackclient master: Enable to add/remove port to/from a server  https://review.openstack.org/45232818:19
ZZellestevemar, dtroyer ^^18:19
*** d0ugal has joined #openstack-sdks18:20
elmikocdent: yeah, sadly, i have no better answers here =(18:21
dtroyerZZelle: thanks18:22
cdentelmiko: no worries. if/when edleafe comes back he may have something, I gotta run to dinner, thanks for the input, we'll figure something out.18:22
elmikocdent: cool, enjoy o/18:22
*** cdent has quit IRC18:22
*** ralonsoh has quit IRC18:23
stevemarZZelle: ohhh are you cedric?18:23
*** annegentle has joined #openstack-sdks18:24
sshankdtroyer, I think https://review.openstack.org/#/c/403907/ (flavor associate, dissociate) is ready for reviews.18:27
openstackgerritAnkur proposed openstack/python-openstacksdk master: Introduce Base for Octavia (load balancing)  https://review.openstack.org/42841418:28
*** ssbarnea has joined #openstack-sdks18:28
*** e0ne has quit IRC18:28
openstackgerritAnkur proposed openstack/python-openstackclient master: Network L3 Router Commands for OSC  https://review.openstack.org/38572918:32
*** ssbarnea has quit IRC18:33
dtroyerankur-gupta-f1: re https://review.openstack.org/#/c/449757/, why are you filtering the show output?  we've removed specific fields before, I don't understand why you are treating this one like a list command18:39
*** john-davidge has joined #openstack-sdks18:50
*** prg3 has quit IRC18:53
*** prg3 has joined #openstack-sdks18:55
*** john-davidge has quit IRC18:55
openstackgerritMerged openstack/python-openstackclient master: Add help commands withouth auth in functional  https://review.openstack.org/45240718:55
ankur-gupta-f4dtroyer: based on the api response. Since the advanced commands hit different endpoints that the normal list commands19:01
ankur-gupta-f4I can go back thru them do verify if you want19:02
dtroyerwhat happened to advanced commands going into plugins?19:03
ankur-gupta-f4Because its not advanced in the sense that certain features have to be enabled to use the commands. Its just a complex endpoint19:04
dtroyerright, that's what I thought made it different.  'advanced services' has a specific meaning in neutron19:05
ankur-gupta-f4Yea. Will reword it. Sorry for confusion19:05
ZZellestevemar, yes i am19:06
dtroyerbut that doesn't change a) different endpoint and b) the same resource isn't represented by the same fields?19:06
dtroyerwhat endpoint is it?19:06
ankur-gupta-f4i.e. for routers for the list command it hits /v2.0/routers for the list routers --agent <agent-id> it hits /v2.0/routers/<router-id>/l3-agents i believe19:07
dtroyerok, again, endpoint has a specific meaning: service catalog thing19:07
dtroyerthat's a route in wsgi terms19:07
ankur-gupta-f4okay. route.19:07
dtroyerso much overloading of words!19:07
dtroyerso the server returns a different object in that case?19:08
ankur-gupta-f4correct19:08
dtroyerand the SDK doesn't fill it out?  this is one place I'd expect the SDK's high-level-ness to step in and make things look right19:08
ankur-gupta-f4https://github.com/openstack/python-openstacksdk/blob/master/openstack/network/v2/router.py#L134 is how the route is determined in the SDK19:08
dtroyerwe should just start issuing random 3 letter names for all of these different things19:09
ankur-gupta-f4route, complex command, idiotic API.. should suffice19:10
dtroyerso, back to the issue at hand, is —router a filter or a type specifier?19:11
ankur-gupta-f4not a filter in the sense that it filters the resulting data from hitting the common list route. rather a flag to indicate that instead of hitting the usual list route, to hit the specific route that would return a different routers list object from the API.19:13
dtroyerok, the problem is that the columns are different19:15
dtroyerin your examples the router ID is the same so it is that the server returns a different object, except it is still the same router at each endpoint?19:16
ankur-gupta-f4yes19:17
ankur-gupta-f4well..19:17
ankur-gupta-f4the example I posted, the paste.openstack.org link, was just to show that the commands are still listing the correct items19:19
dtroyerso I clearly still don't understand wtf neutron is doing here.  If I were to say: make a router list command always show the same columns, eept for -c and —long, what would you suggest?19:20
ankur-gupta-f4I just ran the commands in --debug to look at the dicts.19:21
openstackgerritNakul Dahiwade proposed openstack/python-openstacksdk master: Introduce Listener for Octavia (load balancing)  https://review.openstack.org/45157419:21
ankur-gupta-f4It should be possible to have all the list commands return the same values.19:22
ankur-gupta-f4what we can do is have all the list commands have the same columns.19:23
ankur-gupta-f4then if the certain agent flag is given19:23
ankur-gupta-f4append the additional columns19:23
*** d0ugal has quit IRC19:23
dtroyerthat would be good.  if we need additional options to select specic column similar to —long, we can talk about that… say for a common use case19:24
*** d0ugal has joined #openstack-sdks19:25
ankur-gupta-f4dtroyer: thanks. Headed to airport now. Will deal with all that shit Wednesday19:26
dtroyerok, thanks19:26
ankur-gupta-f4sshank: here? you will need to update your DHCP-network commands to reflect ^^^^^^19:27
sshankankur-gupta-f4, Yes. I'll need to read through the logs.19:27
*** bobh has quit IRC19:29
ankur-gupta-f4basically have the list commands use the common columns from the base list case. and do like a columns = columns + (whatever additional your specific list command adds on (like ha)) column_headers = column_headers + (whatever)19:30
openstackgerritAnkur proposed openstack/python-openstacksdk master: Introduce Base for Octavia (load balancing)  https://review.openstack.org/42841419:33
*** d0ugal has quit IRC19:36
*** chlong has quit IRC19:37
openstackgerritShashank Kumar Shankar proposed openstack/python-openstacksdk master: Introduce Pool for Octavia (load balancing)  https://review.openstack.org/44926419:47
openstackgerritMerged openstack/python-openstackclient master: Fix block-device-mapping when volume_size is empty  https://review.openstack.org/45143219:49
*** chlong has joined #openstack-sdks19:51
*** john-davidge has joined #openstack-sdks19:51
*** john-davidge has quit IRC19:55
*** jamielennox|away is now known as jamielennox20:05
dtroyerstevemar: if you can spare a minute have a look at https://review.openstack.org/#/c/450453/, it's finally passing everything and fixes our -tips jobs20:05
stevemar++20:06
*** e0ne has joined #openstack-sdks20:08
*** e0ne has quit IRC20:09
*** e0ne has joined #openstack-sdks20:10
dtroyerthanks20:10
*** jkilpatr has joined #openstack-sdks20:25
*** e0ne has quit IRC20:28
stevemardtroyer: want me to push it through or wait til osc-lib is released?20:28
dtroyerthis is all for master, go ahead20:30
dtroyerI'm working on releases, hopefully this week as I'm limited availability next week20:30
openstackgerritNakul Dahiwade proposed openstack/python-openstacksdk master: Introduce Base for Octavia (load balancing)  https://review.openstack.org/42841420:48
openstackgerritMerged openstack/python-openstackclient master: Enable to add/remove port to/from a server  https://review.openstack.org/45232820:51
*** prg3 has quit IRC20:52
*** annegentle has quit IRC20:52
*** hoangcx has joined #openstack-sdks20:55
*** corey__ has quit IRC20:56
*** prg3 has joined #openstack-sdks20:58
*** d0ugal has joined #openstack-sdks21:01
openstackgerritNakul Dahiwade proposed openstack/python-openstacksdk master: Introduce Listener for Octavia (load balancing)  https://review.openstack.org/45157421:09
openstackgerritNakul Dahiwade proposed openstack/python-openstacksdk master: Introduce Listener for Octavia (load balancing)  https://review.openstack.org/45157421:10
openstackgerritNakul Dahiwade proposed openstack/python-openstacksdk master: Introduce Listener for Octavia (load balancing)  https://review.openstack.org/45157421:11
*** annegentle has joined #openstack-sdks21:15
openstackgerritDean Troyer proposed openstack/python-openstackclient master: Help/docs cleanups: marker, limit, ip-address metavars  https://review.openstack.org/45296121:23
*** gouthamr has quit IRC21:24
openstackgerritDean Troyer proposed openstack/python-openstackclient master: Release notes cleanup for 3.10.0 release  https://review.openstack.org/45296521:32
*** reedip has quit IRC21:35
dtroyerjamielennox: when you get a sec have a look at https://review.openstack.org/#/c/452711/ and tell me "I told you that long ago" if this is what I think it is :)21:38
*** prg3 has quit IRC21:49
openstackgerritMerged openstack/python-openstackclient master: Change noauth strategy for plugin loading  https://review.openstack.org/45045321:50
*** prg3 has joined #openstack-sdks21:54
*** ssbarnea has joined #openstack-sdks22:05
*** ZZelle has quit IRC22:15
openstackgerritNakul Dahiwade proposed openstack/python-openstacksdk master: Introduce Base for Octavia (load balancing)  https://review.openstack.org/42841422:16
*** chlong has quit IRC22:38
*** sdague has quit IRC22:57
*** adriant has joined #openstack-sdks23:01
*** annegentle has quit IRC23:03
jamielennoxdtroyer: i was going to push this up but realized you weren't the author23:04
jamielennoxall you really need is:23:05
jamielennox-        if not self._auth_ref:23:05
jamielennox-            self.setup_auth()23:05
jamielennox-            LOG.debug("Get auth_ref")23:05
jamielennox-            self._auth_ref = self.auth.get_auth_ref(self.session)23:05
jamielennox-        return self._auth_ref23:05
jamielennox+        self.setup_auth()23:05
jamielennox+        return self.auth.get_access(session)23:05
jamielennoxget_access will mean it's reused if possible and there is already a guard that means setup_auth won't execute twice23:05
dtroyerjamielennox: ok, thanks23:13
*** ssbarnea has quit IRC23:16
*** prg3 has quit IRC23:21
*** prg3 has joined #openstack-sdks23:24
*** hoangcx has quit IRC23:35
*** bobh has joined #openstack-sdks23:35

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!