Tuesday, 2015-06-23

*** markvoelker has joined #openstack-meeting-300:00
*** carl_baldwin has joined #openstack-meeting-300:09
*** SumitNaiksatam has quit IRC00:09
*** yamamoto has joined #openstack-meeting-300:10
*** Longgeek has joined #openstack-meeting-300:13
*** fallenpe_ has quit IRC00:13
*** pballand has joined #openstack-meeting-300:14
*** puranamr has joined #openstack-meeting-300:15
*** fallenpegasus has joined #openstack-meeting-300:17
*** Swami has quit IRC00:25
*** annp has joined #openstack-meeting-300:27
*** pballand has quit IRC00:34
*** puranamr has quit IRC00:38
*** nelsnelson has quit IRC00:44
*** Yi_ has joined #openstack-meeting-300:44
*** Longgeek has quit IRC00:46
*** fallenpegasus has quit IRC00:47
*** fallenpegasus has joined #openstack-meeting-300:49
*** Yi__ has joined #openstack-meeting-300:50
*** Yi_ has quit IRC00:52
*** yamamoto has quit IRC00:52
*** DericHorn-HP has joined #openstack-meeting-300:53
*** Yi_ has joined #openstack-meeting-300:54
*** bradjones has quit IRC00:54
*** dims has quit IRC00:55
*** Yi__ has quit IRC00:55
*** dims has joined #openstack-meeting-300:57
*** bradjones has joined #openstack-meeting-300:59
*** bradjones has quit IRC00:59
*** bradjones has joined #openstack-meeting-300:59
*** puranamr has joined #openstack-meeting-300:59
*** safchain has quit IRC00:59
*** yamamoto has joined #openstack-meeting-301:02
*** puranamr has quit IRC01:04
*** Piet has quit IRC01:06
*** bradjones has quit IRC01:07
*** bpokorny has quit IRC01:07
*** bradjones has joined #openstack-meeting-301:09
*** bradjones has quit IRC01:09
*** bradjones has joined #openstack-meeting-301:09
*** yamamoto has quit IRC01:10
*** haleyb has quit IRC01:13
*** Longgeek has joined #openstack-meeting-301:15
*** stevemar has joined #openstack-meeting-301:19
*** Networkn3rd has joined #openstack-meeting-301:20
*** sdake has joined #openstack-meeting-301:24
*** annp has quit IRC01:25
*** sdake_ has joined #openstack-meeting-301:27
*** sdake has quit IRC01:31
*** yamahata has quit IRC01:33
*** stanzgy has joined #openstack-meeting-301:35
*** alexpilotti has quit IRC01:40
*** SumitNaiksatam has joined #openstack-meeting-301:42
*** yamamoto has joined #openstack-meeting-301:46
*** s3wong has quit IRC01:52
*** carl_baldwin has quit IRC01:53
*** julim has quit IRC01:53
*** carl_baldwin has joined #openstack-meeting-301:54
*** carl_baldwin has quit IRC01:57
*** sdake_ has quit IRC01:58
*** bpokorny has joined #openstack-meeting-301:58
*** sdake has joined #openstack-meeting-301:58
*** sbalukoff has quit IRC02:05
*** sdake has quit IRC02:07
*** Yi_ has quit IRC02:16
*** carl_baldwin has joined #openstack-meeting-302:19
*** muralia has joined #openstack-meeting-302:28
*** DericHorn-HP has quit IRC02:30
*** kebray has joined #openstack-meeting-302:31
*** kebray has quit IRC02:32
*** kebray has joined #openstack-meeting-302:33
*** carl_baldwin has quit IRC02:35
*** dims has quit IRC02:36
*** kebray has quit IRC02:39
*** DericHorn-HP has joined #openstack-meeting-302:39
*** zhenguo has joined #openstack-meeting-302:40
*** carl_baldwin has joined #openstack-meeting-302:41
*** sankarshan_away is now known as sankarshan02:42
*** fallenpegasus has quit IRC02:42
*** fallenpegasus has joined #openstack-meeting-302:44
*** kebray has joined #openstack-meeting-302:45
*** fallenpegasus has quit IRC02:47
*** rushiagr_away is now known as rushiagr02:53
*** Longgeek has quit IRC02:55
*** DericHorn-HP has quit IRC02:57
*** puranamr has joined #openstack-meeting-302:58
*** puranamr has quit IRC03:05
*** puranamr has joined #openstack-meeting-303:05
*** ivar-laz_ has joined #openstack-meeting-303:19
*** Longgeek has joined #openstack-meeting-303:23
*** ivar-lazzaro has quit IRC03:23
*** ctlaugh has quit IRC03:23
*** ivar-laz_ has quit IRC03:24
*** sdake has joined #openstack-meeting-303:25
*** bpokorny has quit IRC03:26
*** tobe has joined #openstack-meeting-303:26
*** sdake_ has joined #openstack-meeting-303:27
*** sdake has quit IRC03:31
*** sdake__ has joined #openstack-meeting-303:32
*** shwetaap has joined #openstack-meeting-303:32
*** carl_baldwin has quit IRC03:32
*** rushiagr is now known as rushiagr_away03:32
*** sdake_ has quit IRC03:35
*** DericHorn-HP has joined #openstack-meeting-303:38
*** DericHorn-HP has quit IRC03:38
*** mickeys has quit IRC03:39
*** coolsvap|away is now known as coolsvap03:47
*** haleyb has joined #openstack-meeting-303:53
*** shwetaap has quit IRC03:55
*** Longgeek has quit IRC04:00
*** Longgeek has joined #openstack-meeting-304:00
*** sballe has quit IRC04:02
*** pballand has joined #openstack-meeting-304:02
*** david-lyle_ has quit IRC04:03
*** Networkn3rd has quit IRC04:10
*** rushiagr_away is now known as rushiagr04:11
*** rushiagr is now known as rushiagr_away04:14
*** rushiagr_away is now known as rushiagr04:15
*** pballand has quit IRC04:17
*** mestery has joined #openstack-meeting-304:19
*** sdake__ has quit IRC04:24
*** Longgeek has quit IRC04:29
*** Longgeek has joined #openstack-meeting-304:32
*** puranamr has quit IRC04:38
*** haleyb has quit IRC04:48
*** mestery has quit IRC04:49
*** naohirot has joined #openstack-meeting-304:54
*** puranamr has joined #openstack-meeting-304:58
jroll.04:58
*** rameshg87 has joined #openstack-meeting-305:00
devanandahi folks!05:00
devananda#startmeeting ironic05:00
openstackMeeting started Tue Jun 23 05:00:47 2015 UTC and is due to finish in 60 minutes.  The chair is devananda. Information about MeetBot at http://wiki.debian.org/MeetBot.05:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:00
*** openstack changes topic to " (Meeting topic: ironic)"05:00
openstackThe meeting name has been set to 'ironic'05:00
devanandawho's around?05:00
mrdao/05:00
jrollohai \o05:00
naohiroto/05:01
*** ramineni has joined #openstack-meeting-305:01
devanandathe agenda, as usual, is here:05:01
devananda#link https://wiki.openstack.org/wiki/Meetings/Ironic05:01
devanandait is oddly empty05:01
*** rameshg87 has joined #openstack-meeting-305:01
jrollI won't complain :)05:02
*** wanyen has joined #openstack-meeting-305:02
devanandaI'll wait a few more minutes and see who shows up05:02
* mrda hopes everything going swimmingly then05:02
rameshg87o/05:02
devanandamrda: I've been on the road for, um, several weeks >_<05:02
wanyeno/05:02
jrollI have a couple things of note at some point05:02
mrdadevananda: you must be glad to be home then05:02
devanandamrda: very much so05:02
*** martini has joined #openstack-meeting-305:03
*** puranamr has quit IRC05:03
*** nkrinner has joined #openstack-meeting-305:04
* devananda continues waiting to see if we get any more cores in the room05:04
*** Nisha has joined #openstack-meeting-305:04
jrolldevananda: 2 is enough to decide anything, right? :)05:04
devanandajroll: lol05:04
*** carlp has quit IRC05:05
*** krtaylor has quit IRC05:05
* jroll merges everything05:05
mrda"jroll merges all the things"05:05
devanandaall right ... 5 minutes in and we've got 3 cores ...05:05
mrdathat could be a meme05:05
jrollheh05:06
devananda#info only 3 cores present, and no agenda on the wiki.05:06
devananda#topic open discussion05:06
*** openstack changes topic to "open discussion (Meeting topic: ironic)"05:06
jrolloh, I missed rameshg87, hi rameshg87! be louder :)05:06
jrollso I have some things for open discussion05:06
rameshg87hi jroooooollllllll05:06
* rameshg87 gets louder :)05:06
jrollfirst off, this neutron integration spec has rough consensus from the subteam. I hate asking for reviews, but we need reviews :)05:07
jroll#link https://review.openstack.org/#/c/187829/05:07
mrdaCool!05:07
rameshg87great .. :)05:07
jrollmaybe that's it, I thought I had something else but it's late and it isn't coming to mind :P05:08
*** armax has joined #openstack-meeting-305:08
devanandajroll: nova stuff?05:08
jrollaha yes05:08
jrollI put up a spec today for fixing our nova-compute model of the world05:09
jroll#link https://review.openstack.org/#/c/194453/05:09
jrollpls to check it out :)05:09
mrdaThanks jroll - I will take a look05:09
jrollawesome.05:09
rameshg87oh i was about to ask if someone was working on it :)05:09
jrollit's roughly what we decided in vancouver05:09
jrolland jay pipes, devananda and myself chatted about it today05:09
mrdaThat'll be a nice piece of work, if we get agreement05:10
jrollindeed. I for one am excited.05:10
mrdaOk, I have something to raise, if we're done with that05:10
*** tobe has quit IRC05:11
mrdaI feel I should mention "Bare metal" or "Bare Metal" and https://review.openstack.org/#/c/19423005:11
devanandamrda: we should go to vegas. jaypipes and I agree on something :)05:11
* naohirot jroll, I need to discuss with you regarding the #link https://review.openstack.org/#/c/187829/05:11
mrdadevananda: Is the midcycle fixed for SEA? :P05:11
devanandamrda: I'm *STILL* waiting on facilities :(05:11
devanandaand getting quite grumpy about it05:11
jrolldevananda: boooooo05:11
mrdadevananda: well, maybe then05:11
devanandaI am actually going into the office tomorrow and will sort this out05:12
*** Haomeng|2 has joined #openstack-meeting-305:12
mrdaAnyhow, "Bare metal" vs "Bare metal" in docs05:12
mrdaSorry Bare Metal05:12
rameshg87mrda: does it actually matter somewhere ? Bare Metal or Bare metal ?05:12
rameshg87for docs, is it ?05:12
mrdaExcept it's work to be done with little value05:12
jrollnaohirot: go ahead? I don't have anything to say I haven't said in that discussion05:12
mrdaI don't want us to be seen as bike shedders05:12
mrdaDo we really need to change it?05:12
naohirotjroll: Okay, the point I need to discuss is the problem description,05:13
mrdaOpinions?05:13
jrollnaohirot: so the discussion here. https://review.openstack.org/#/c/187829/3/specs/liberty/network-provider.rst05:13
jrollright?05:13
rameshg87mrda: i am +0 on it unless it matters somewhere :)05:13
naohirotjroll: yeah, right05:13
mrdaI just want to keep docs on-side.  My preference is pretty much +0 too05:14
jrollnaohirot: what isn't clear about "ironic provisions servers on the same network that tenants use"?05:14
jrollanyone else, is there something unclear about that, that I am not seeing05:14
naohirotnaohirot: As I commented in the gerrit, sufficient or not only can be judged by reader.05:14
mrdaI guess I'm hoping the other two cores here will chime in05:15
naohirotjroll: for instance, if developer thought it's good product, but customer didn't think so05:15
devanandamrda: see the last comment and link to the ML re: capitalization of Proper Names05:15
jrollnaohirot: what?05:15
naohirotjroll: developer cannot deny the customer05:15
devanandamrda: I think things will go in that direction05:16
mrdadevananda: so ML discussion will decide then?05:16
jrollnaohirot: I have no idea what a customer has to do with this05:16
naohirotjroll: That customer felt so, that is fact, it's not denyable.05:16
devanandanaohirot: a great many of the developers in this case are also users05:17
*** tobe has joined #openstack-meeting-305:17
naohirotjroll: customer is a reader in this case.05:17
devanandanaohirot: i dont understand why you're arguing about this05:17
naohirotjroll: reader felt it is not sufficient to understand the problem05:17
devanandanaohirot: you didn't understand something. you do now. let's move on.05:17
devanandanaohirot: dialogue occurred. knowledge was shared. what's the problem?05:18
naohirotdevananda: but it's not only me, other new conributer likely to have same question05:18
devanandanaohirot: also, a design spec IS NOT DOCUMENTATION. the intended audice of https://review.openstack.org/#/c/187829/3/specs/liberty/network-provider.rst are existing contributors familiar with the code05:19
devanandanaohirot: who are themselves then able to judge the merits and drawbacks of the proposed changes05:19
*** tobe has quit IRC05:19
jrollthe goal is to make the problem disappear, so nobody needs to understand that problem description.05:19
devanandanaohirot: a new contributor is not able to make that judgement in the same way because they lack the context and knowledge05:19
naohirotdevananda: if review comment is ignored by unreasonable reason, the whole review process is wast of time05:19
devanandanaohirot: the review process is not a waste of time05:20
devanandanaohirot: i'm sorry you feel that way05:20
jrollnaohirot: so is this your review comment or your customer's review comment?05:20
*** smoriya_ has joined #openstack-meeting-305:20
jrollnaohirot: also, define "customer". developer, deployer, ironic user, nova user?05:20
naohirotdevananda: I made a comment it's not sufficient, why is it ignored?05:20
devanandanaohirot: if your feedback was on documentation -- that some section of documentation was not understandable, or lacked context, and was hard to understand or ambiguous -- then we should clearly update that documentation05:21
*** woodster_ has quit IRC05:21
naohirotdevananda: then I proposed sentence to Jim.05:21
devanandanaohirot: the current wording is perfectly clear to me05:22
naohirotdevananda: I proposed concrete sentence how to update for reader who is not knowlegable05:22
devananda"Ironic currently provisions servers on the same (flat) network that tenants use."05:22
naohirotdevananda: sure, you are core and know details.05:22
devanandaI know exactly what that means05:22
*** alexsyip has joined #openstack-meeting-305:23
naohirotdevananda: but are we writing the spec for only such people like you?05:23
jrollhonestly, I'm tempted to say that anyone who does not already understand the problem does not need to review that spec. why does someone care about fixing it if they don't know it's a problem?05:23
jrollif a flat network is fine, then don't review it05:23
jrollif you don't even know that ironic uses a single flat network, I don't believe you are a developer/deployer/operator/user of ironic?05:24
devanandanaohirot: the author of a patch has every right to change their spec as they see fit05:24
devanandanaohirot: you don't get to insist that jroll changes his document in the way that you want05:24
naohirotjroll: i think neutron integration is important for cloud provider05:24
rameshg87naohirot: i guess point jroll was having was the problem is same regardless of it's single/multiple conductors or nova/standalone deployment05:24
rameshg87naohirot: so honestly i don't feel that change is required too05:25
naohirotjroll: that's the reason I'm reviewing and trying to understand the problem05:25
*** krtaylor has joined #openstack-meeting-305:25
*** irenab has joined #openstack-meeting-305:25
devanandanaohirot: reviewing a design proposal for new work is not the place to stop someone else's work and ask them to help you understand the current problem05:26
naohirotrameshg87: again I know that core know about it, I don't deny it.05:26
rameshg87in a team/community project, voice of community > voice of individuals. so i guess if more people agree on one side, we should just stick with it.05:26
rameshg87right ?05:26
devanandanaohirot: that is valuable feedback for documentation, NOT for design work05:26
naohirotrameshg87: I'm talking about people, ordianry people05:26
devanandanaohirot: and again, a design spec is intended for those people already involved in a project to evaluate the proposed changes.05:26
jrollordinary people don't know what a network is05:26
devanandanaohirot: if the documentation is not clear, please provide feedback on ways we can improve it (or -- better yet, a patch to improve it)05:27
jrollso going back to square one.05:27
* rameshg87 has one item to discuss05:27
jrollnaohirot: now that you (presumably) understand the problem, is it still unclear to you?05:27
naohirotdevananda: again I commented a concrete sentence how we should explain the problem in the gerrit.05:27
jrollrameshg87: I hear you, don't let us forget :)05:28
*** alexsyip has quit IRC05:28
* Nisha has capabilities to be discussed05:28
rameshg87:)05:28
devanandanaohirot: even now, you are not understanding me. let's move on.05:28
devanandaNisha: go ahead :)05:28
naohirotjroll: Yes I understood the problem, but why don't we record the essense in the spec.05:28
* rameshg87 takes the mic05:28
jrollrameshg87 was first05:28
devanandajroll: thanks. rameshg87 -- the floor is yours :)05:28
Nisharameshg87, :)05:28
Nishayes jroll :)05:29
jrollnaohirot: because the spec is not documentation about how ironic works.05:29
rameshg87i have a patch here to refactor pxe as boot interface - https://review.openstack.org/#/c/166513/05:29
jroll\o/05:29
mrda:)05:29
rameshg87there is no time left for liberty-1 anyway, but it will be good if we can get much of the work done in liberty-205:29
devanandarameshg87: whoa! nice05:30
rameshg87i am planning to put up patches one after another05:30
devanandarameshg87: hm. isn't there a bp/spec for that? it's not tagged on the commit header05:30
rameshg87people are welcome to review and more importantly to try it05:30
*** carlp has joined #openstack-meeting-305:30
rameshg87to make sure we don't break anything05:30
* rameshg87 forgot 05:30
*** koteswar has joined #openstack-meeting-305:30
devananda:)05:30
rameshg87devananda: will add bp to next patch05:30
* jroll personally would like to stop talking about liberty-1 etc :)05:31
rameshg87it is still W-1 as i need to add some documentation05:31
*** haleyb has joined #openstack-meeting-305:31
jrollI'd love to do a release when the boot/deploy split is done05:31
rameshg87i mean docstrings05:31
rameshg87\o/05:31
jrollrameshg87: I suggest you remove the WIP, otherwise some people won't review it05:31
rameshg87jroll: so that may be the first release :)05:31
jrollrameshg87: if someone merges it by accident we can follow up with docstring patches :)05:32
mrda:)05:32
* rameshg87 removed now05:32
jrollwoot.05:32
devanandajroll: if we can sort the release details out w/ dhellmann before this lands ... it would make an interesting first go at it05:32
jrollthanks for taking this work on :)05:32
devanandarameshg87: my biggest concern with this is ofc how does it affect out of tree drivers05:32
jrolldevananda: I don't think there's much contention there, if I wasn't going on vacation I'd hope to do it this week :)05:32
rameshg87devananda: it doesn't, there is no change to how conductor sees drivers now05:33
rameshg87devananda: it's just an understand between boot and deploy interfaces of drivers that is driving this change05:33
devanandarameshg87: what if this file  https://review.openstack.org/#/c/166513/7/ironic/drivers/pxe.py,cm were split into multiple changes?05:33
jrollrameshg87: so the deploy driver calls to the boot driver, right?05:33
rameshg87*understanding05:33
rameshg87jroll: yes05:33
devanandarameshg87: not asking that it necessarily be done that way, but it would be a good way to prove that it works05:34
jrollcool, so I agree probably doesn't affect out-of-tree drivers unless they're relying on deploy_utils etc05:34
rameshg87devananda: how does it prove it ? i didn't get05:34
jrollyeah, not seeing it either05:34
*** kebray has quit IRC05:35
devanandaeh, it's late. maybe i'm wrong05:35
rameshg87okay, i tested with pxe_vbox and jenkins tested with pxe_ssh, so reasonably it should work with other drivers :)05:35
*** haleyb has quit IRC05:35
jrollso as this is, a completely out of tree driver should be fine. one that relies on some of our helper functions may break05:35
rameshg87other drivers of form pxe_* :)05:35
devanandaoh - nope, i'm not wrong05:36
jrolland I think I'm okay with that, we don't guarantee anything explicitly about those methods05:36
jrolldevananda: famous last words :)05:36
devanandadrivers/modules/pxe.py: PXEDeploy class is removed in this patch05:36
rameshg87jroll: do we really promise them stuffs like deploy_utils are not changed ?05:36
devanandaso if I had another driver that inherited from that -- boom05:36
jrollrameshg87: we don't promise it explicitly, no05:36
devananda(that's not part of our driver API -- but it's still a thing someone may have done downstream)05:37
jrolldevananda: while I'm all about not breaking out of tree things... is that part of our contract?05:37
jrollyeah05:37
rameshg87devananda: but upstream drivers have mostly unit tests, so going by that it will fail05:37
jrollI mean, we should at a minimum mail a list about this05:37
jrollI'm not sure if we should do more :)05:37
devanandajroll: we totally have to do a mailing about this before it lands05:38
devanandathis one line change sums up my concern: https://review.openstack.org/#/c/166513/7/ironic/drivers/modules/amt/vendor.py,cm05:38
jroll+105:38
rameshg87devananda: may be it's time to have something written down in wiki about contract05:38
devanandaanyone who may have an out of tree driver that is extending or inheriting from one of our current driver CLASSES is going to get broken05:38
devanandaeven though the API contract itself is not broken05:38
jrollyep05:38
devanandaso we're technically fine -- a completely original out of tree driver will not be affected05:39
rameshg87devananda: afaik we only have contracts about interfaces that publish explicity05:39
devanandarameshg87: you're correct05:39
rameshg87devananda: may be mailing list is a good place to communicate ?05:39
rameshg87because we need that to be broken down in any case :)05:40
devanandabut this will break my out-of-tree driver :P05:40
devanandahttps://review.openstack.org/#/c/193767/1/ironic/drivers/pxe.py,cm05:40
devanandaso I know it will affect anyone else who's doing something similar05:40
rameshg87petitboot05:40
rameshg87i already commented on that review05:40
jrollyeah, agree we should mail a list05:40
devanandayup -- that too05:40
jrollis there anythign more we should do though?05:41
jrollsounds like we're in agreement05:41
devanandarameshg87: please send an email to both openstack-dev and openstack-operators lists05:41
devanandaand let's wait a minimum of 7 days after that before we land it05:41
rameshg87devananda: sure05:41
jrolldo we want to -2 or anything to enforce that?05:42
devanandarealistically, we'll all probably be fighting to land it as soon as 7 days have passed, because this is fantastic05:42
jrollheh05:42
devanandabut waiting is the right thing to do05:42
rameshg87okay ..05:42
* rameshg87 hands microphone over to Nisha 05:42
devanandajroll: just W-1 ?05:42
jrollyeah, seems fine05:42
naohirotdevananda: can we discuss another topic regarding liberty-1?05:43
rameshg87devananda: do you want me to W-1 again ?05:43
jrollok, Nisha and naohirot both have items to discuss, should we risk taking them in parallel? :)05:43
jrollnaohirot: what's the general subject, out of curiousity?05:44
Nishadevananda, we agreed earlier for boolean capabilities. My ques is where do we define them? in each driver? or a centre place in ironic?05:44
NishaDo we require a spec to just define all the possible capabilities05:44
naohirotjroll: I'm fine if we can discuss my topic in the ironic channel, go ahead to Nisha's topic05:44
devanandaNisha: eeeeh. yea, I think this needs to be defined across all drivers (iow, in the conductor) so we need to define the set of supported capabilities05:44
jrollat a glance I think I agree05:45
devanandaNisha: has Nova team agreed to the way you want to expose them?05:45
mrdaNisha: My personal opinion is that we have a spec for this05:45
jrolland then maybe drivers can indicate which they support05:45
devanandajroll: exactly05:45
jrollcool05:45
Nishadevananda, they have agreed for boolean capabilities but i didnt get any further reviews on the spec from them05:45
jrollsee, 2 cores can get stuff done :)05:45
* jroll +A05:45
Nishamrda, but the spec will just contain all the capabilities so far05:46
mrdaI think that's a good start05:46
devanandarameshg87: W-1 needs to be applied at every revision. you could also -2 your own patch :)05:46
Nishamrda, ok :)05:46
* naohirot jroll , devananda , my topic is irmc vmedia, and maybe related to new feature release model05:46
Nisha#link https://review.openstack.org/182934, with this spec i have proposed capabilities to be a new field in node table which can accept key:value pair.05:46
jrollNisha: I think that's fine, additional capabilities can be covered in the spec that adds the feature05:47
devanandaNisha: if we were to allow each driver to expose arbitrary capabilities, we'll have no consistency between drivers -- and thus defeat much of the purpose of capabilities. so yea, I think we need a spec to define the set of ironic-supported capabilities05:47
mrdaI think that's good.  Question is for a driver writer to know what capabilities there are, and which ones they should support05:47
* rameshg87 does that05:47
devanandaNisha: and if we need to add to that list over time, we'll need some aceptance from >1 driver/vendor that they can support it05:47
* jroll makes a motion to #agreed05:47
Nishajroll ques was where do we have the set of supported capabilities05:48
Nishadevananda, +105:48
jrollNisha: ironic/common/capabilities.py? :)05:48
devanandaNisha: list of ... yes, in python ^05:48
Nishadevananda, jroll ok05:48
devanandathis could be discovered by ironic-inspector and the node record updated05:48
devanandaor $soemthing05:48
Nishaso do we agree that capabilities shall be a new field in node table05:48
mrdaDo we see the need to have a required minimum set for each class of driver?05:49
Nishayes05:49
Nishadevananda, i was coming to above point05:49
devanandamrda: supports_power_management :)05:49
mrda:)05:49
jrollNisha: I think I'd rather a separate table, didn't we agree on that part already?05:49
Nishajroll, i actually didnt understand the need for a new table05:50
devanandamuch like node.properties, we will need to search based on capabilities at some point in the near future05:50
jrollNisha: to be able to index it. can't index lists in mysql.05:50
devanandaNisha: so that we can efficiently create INDEX(key, value) on that table05:50
devanandaand do queries such as ...05:50
Nishalet me summarize the flow i think would be feasible (from nova to ironic)05:50
devanandaSELECT node.uuid FROM nodes JOIN node_caps ... WHERE node_caps.key='boot_mode' AND node_caps.value='secure';05:51
jrolldevananda: your dark past is about to show, I think :)05:51
jrollyep.05:51
devanandajroll: yup05:51
rameshg87:)05:51
Nishadevananda, so do we need end point for capabilities if nova doesnt require it05:51
devanandabecause trying to mimic that query outside of the database is just insanity -- and there, in a nutshell, is one of my biggest problems with the nova scheduler today05:51
devanandaNisha: yes05:51
rameshg87i would still vote for a capabilities endpoint05:52
devanandaNisha: but don't worry about that in this spec05:52
NishaOk...05:52
devanandajust add the capabilities table, a decent initial set to the conductor, and REST API to change them05:52
* rameshg87 notes 8 minutes left 05:52
devanandawe'll worry about the query API after that05:52
Nishadevananda, sorry a trivial ques but what shall be the fields of this table05:53
* mrda thinks we'll still need one though05:53
* jroll nods at rameshg8705:53
devanandabecause I also want to refactor the node.properties JSON field into its own table, that has the same structure and same index05:53
Nishai was unable to think on that05:53
Nishak05:53
devanandaand then create a REST endpoint like: GET /v1/search?field=value&another=value&....05:53
jrollNisha: node_uuid, key, value? or node_uuid, capability, supported.05:53
jrollNisha: not super important right now, I think, we can review in the spec05:54
*** salv-orlando has joined #openstack-meeting-305:54
*** mrmartin has joined #openstack-meeting-305:54
Nishajroll thanks for the pointer05:54
Nishathat helps05:54
*** stevemar has quit IRC05:54
jrollNisha: welcome :)05:54
devanandanode_id INT UNSIGNED, capability VARCHAR(nn) NOT NULL, PRIMARY KEY (node_id, capability)05:54
devanandathat's it05:54
Nishaok will change the spec and post it05:54
*** stevemar has joined #openstack-meeting-305:54
Nishadevananda, thanks05:55
devanandathat's it, I think, because the presence of a row means "supported" and lack of a row means "unsupported" ?05:55
devanandaI think that's good enough05:55
devanandabut at least it's a starting point05:55
devanandaNisha: thanks much for working through all this! I know it's taken a long time05:55
Nishadevananda, :) thanks for the guidance05:55
rameshg87okay, 5 minutes left, any other topic ?05:56
jrollshall we give the last 5 minutes to naohirot ?05:56
wanyendeva and nisah, should conductor just get a list of supported capabilities from drivers?05:56
*** stendulker has joined #openstack-meeting-305:56
devanandanaohirot: the floor is yours05:56
naohirotjroll: I need more than 5 mins :)05:56
*** salv-orlando has quit IRC05:56
jrollhm05:56
naohirotdevananda: can we disucss in the ironic channel?05:57
devanandawanyen: no. see my previous comments. tldr; that will be a leaky API and essentially unsupportable05:57
jrolljust take it to the channel then?05:57
devanandanaohirot: sure05:57
wanyenThat's way when driver added supported capabilities then we don't need to change conductor05:57
jrollcool05:57
devanandawanyen: every vendor will be different, there will be no way to do common scheduling, and users will suffer05:57
naohirotdevananda: thanks!05:58
*** salv-orlando has joined #openstack-meeting-305:58
wanyendevananda, forcommon capabilities we should standaridize capbility name but for vendor specific capability we should allow them too05:58
devanandawanyen: I disagree. we shouldn't support vendor-specific capabilities05:58
wanyendeva, why not?05:58
devanandawanyen: if a functionality can not be expressed in a common way, it belongs in /vendor_passthru/05:59
mrda+105:59
devanandaas long as it can be expressed in a common way, the implementations can be wildly different05:59
devanandabut the API can be the same05:59
wanyendeva, yea,vendor pass through but it needs capability05:59
Haomeng|2+105:59
devanandaand there is a tremendous value in that consistency05:59
jrollwhoa whoa whoa, consistency between drivers?!?!06:00
devanandajroll: inoright? :P06:00
devanandaanyway, we're out of time ... thanks all!06:00
wanyenit relies on Nova to pass capabilities info to ironic driver06:00
jrollthanks everybody.06:00
devananda#endmeeting06:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:00
openstackMeeting ended Tue Jun 23 06:00:39 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-06-23-05.00.html06:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-06-23-05.00.txt06:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-06-23-05.00.log.html06:00
*** smoriya_ has quit IRC06:01
*** ramineni has left #openstack-meeting-306:01
*** wanyen has quit IRC06:02
*** martini has quit IRC06:08
*** Haomeng|2 has left #openstack-meeting-306:08
*** koteswar has quit IRC06:08
*** stevemar2 has joined #openstack-meeting-306:10
*** stevemar has quit IRC06:12
*** mohankumar has joined #openstack-meeting-306:15
*** hichihara has quit IRC06:15
*** stevemar2 is now known as stevemar06:17
*** zz_ttrifonov is now known as ttrifonov06:17
*** tobe has joined #openstack-meeting-306:22
*** mrmartin has quit IRC06:24
*** mrmartin has joined #openstack-meeting-306:26
*** belmoreira has joined #openstack-meeting-306:26
*** mrunge has joined #openstack-meeting-306:31
*** haleyb has joined #openstack-meeting-306:32
*** haleyb has quit IRC06:36
*** mrmartin has quit IRC06:39
*** markvoelker has quit IRC06:40
*** rushiagr is now known as rushiagr_away06:42
*** armax has quit IRC06:49
*** jtomasek has joined #openstack-meeting-306:49
*** sahid has joined #openstack-meeting-306:51
*** fallenpegasus has joined #openstack-meeting-306:51
*** etoews has quit IRC06:53
*** Longgeek_ has joined #openstack-meeting-306:56
*** lazy_prince has joined #openstack-meeting-306:57
*** Nisha_away has joined #openstack-meeting-306:58
*** sahid has quit IRC06:59
*** sahid has joined #openstack-meeting-306:59
*** Longgeek has quit IRC06:59
*** Nisha has quit IRC07:02
*** rameshg87 has quit IRC07:06
*** matrohon has joined #openstack-meeting-307:11
*** matrohon has quit IRC07:20
*** haleyb has joined #openstack-meeting-307:33
*** safchain has joined #openstack-meeting-307:35
*** haleyb has quit IRC07:37
*** salv-orl_ has joined #openstack-meeting-307:37
*** salv-orlando has quit IRC07:40
*** markvoelker has joined #openstack-meeting-307:41
*** stevemar has quit IRC07:43
*** devvesa has joined #openstack-meeting-307:45
*** markvoelker has quit IRC07:46
*** qwebirc17062 has joined #openstack-meeting-307:47
*** sahid has quit IRC07:49
*** sahid_ has joined #openstack-meeting-307:49
*** mickeys has joined #openstack-meeting-307:52
*** persia has quit IRC07:53
*** persia has joined #openstack-meeting-307:53
*** persia has quit IRC07:53
*** persia has joined #openstack-meeting-307:53
*** salv-orl_ has quit IRC07:58
*** sahid_ has quit IRC07:59
*** sahid has joined #openstack-meeting-307:59
*** salv-orlando has joined #openstack-meeting-308:00
*** stanzgy has quit IRC08:04
*** mickeys has quit IRC08:08
*** ttrifonov is now known as zz_ttrifonov08:11
*** stanzgy has joined #openstack-meeting-308:19
*** egallen has joined #openstack-meeting-308:22
*** e0ne has joined #openstack-meeting-308:32
*** haleyb has joined #openstack-meeting-308:34
*** haleyb has quit IRC08:38
*** e0ne is now known as e0ne_08:38
*** e0ne_ has quit IRC08:44
*** e0ne has joined #openstack-meeting-308:48
*** JeanBriceCombebi has joined #openstack-meeting-308:48
*** fallenpegasus has quit IRC08:50
*** zz_ttrifonov is now known as ttrifonov08:51
*** egallen has quit IRC08:51
*** egallen has joined #openstack-meeting-308:52
*** pkonisze has joined #openstack-meeting-309:01
*** pkonisze has quit IRC09:01
*** pkonisze has joined #openstack-meeting-309:01
*** john-davidge has joined #openstack-meeting-309:03
*** pkonisze has quit IRC09:05
*** pkoniszewski has joined #openstack-meeting-309:05
*** john-davidge_ has joined #openstack-meeting-309:05
*** e0ne is now known as e0ne_09:06
*** john-davidge has quit IRC09:07
*** john-davidge_ is now known as john-davidge09:07
*** pbrooko has joined #openstack-meeting-309:08
*** JeanBriceCombebi has quit IRC09:09
*** JeanBriceCombebi has joined #openstack-meeting-309:10
*** e0ne_ has quit IRC09:11
*** e0ne has joined #openstack-meeting-309:15
*** markvoelker has joined #openstack-meeting-309:17
*** egallen has quit IRC09:18
*** yamahata has joined #openstack-meeting-309:18
*** egallen has joined #openstack-meeting-309:19
*** Nisha_away has left #openstack-meeting-309:20
*** markvoelker has quit IRC09:22
*** jcoufal has joined #openstack-meeting-309:23
*** pbrooko has quit IRC09:23
*** pbrooko has joined #openstack-meeting-309:24
*** pbrooko has quit IRC09:24
*** marios_ is now known as marios09:26
*** pbrooko has joined #openstack-meeting-309:28
*** alexpilotti has joined #openstack-meeting-309:34
*** haleyb has joined #openstack-meeting-309:35
*** JeanBriceCombebi has quit IRC09:35
*** egallen has quit IRC09:36
*** egallen has joined #openstack-meeting-309:37
*** JeanBriceCombebi has joined #openstack-meeting-309:37
*** haleyb has quit IRC09:39
*** mpavlase has joined #openstack-meeting-309:41
*** naohirot has quit IRC09:56
*** dims has joined #openstack-meeting-310:06
*** e0ne is now known as e0ne_10:10
*** yamamoto has quit IRC10:11
*** e0ne_ has quit IRC10:20
*** salv-orlando has quit IRC10:29
*** haleyb has joined #openstack-meeting-310:36
*** egallen has quit IRC10:37
*** john-davidge has left #openstack-meeting-310:37
*** mrmartin has joined #openstack-meeting-310:39
*** tobe has quit IRC10:39
*** haleyb has quit IRC10:41
*** pbrooko has quit IRC10:49
*** yamamoto has joined #openstack-meeting-310:50
*** mrunge has quit IRC10:53
*** mrunge has joined #openstack-meeting-310:53
*** stanzgy has quit IRC10:54
*** yamamoto has quit IRC10:55
*** coolsvap is now known as coolsvap|away10:55
*** yamahata has quit IRC10:55
*** mohankumar has quit IRC11:01
*** yamamoto has joined #openstack-meeting-311:03
*** markvoelker has joined #openstack-meeting-311:06
*** e0ne has joined #openstack-meeting-311:09
*** markvoelker has quit IRC11:11
*** irenab has quit IRC11:12
*** irenab has joined #openstack-meeting-311:13
*** egallen has joined #openstack-meeting-311:16
*** baoli has joined #openstack-meeting-311:23
*** yamamoto has quit IRC11:24
*** yuikotakada has quit IRC11:24
*** yamamoto has joined #openstack-meeting-311:27
*** yamamoto_ has joined #openstack-meeting-311:28
*** jcoufal has quit IRC11:29
*** salv-orlando has joined #openstack-meeting-311:30
*** yamamoto has quit IRC11:32
*** salv-orlando has quit IRC11:36
*** egallen has quit IRC11:36
*** yamamoto_ has quit IRC11:36
*** e0ne is now known as e0ne_11:36
*** haleyb has joined #openstack-meeting-311:37
*** stendulker has quit IRC11:37
*** egallen has joined #openstack-meeting-311:37
*** haleyb has quit IRC11:41
*** pbrooko has joined #openstack-meeting-311:42
*** yamamoto has joined #openstack-meeting-311:43
*** zhenguo has quit IRC11:43
*** mrmartin has quit IRC11:44
*** e0ne_ has quit IRC11:46
*** sdake has joined #openstack-meeting-311:46
*** sdake_ has joined #openstack-meeting-311:47
*** sdake has quit IRC11:50
*** salv-orlando has joined #openstack-meeting-311:54
*** sdake_ has quit IRC11:54
*** sankarshan is now known as sankarshan_away11:56
*** shwetaap has joined #openstack-meeting-311:56
*** JeanBriceCombebi has quit IRC12:01
*** JeanBriceCombebi has joined #openstack-meeting-312:01
*** markvoelker has joined #openstack-meeting-312:05
*** muralia has quit IRC12:10
*** JeanBriceCombebi has quit IRC12:10
*** obondarev has quit IRC12:10
*** JeanBriceCombebi has joined #openstack-meeting-312:11
*** sankarshan_away is now known as sankarshan12:11
*** VW_ has joined #openstack-meeting-312:18
*** killer_prince has joined #openstack-meeting-312:20
*** killer_prince has quit IRC12:21
*** killer_prince has joined #openstack-meeting-312:22
*** lazy_prince has quit IRC12:23
*** woodster_ has joined #openstack-meeting-312:25
*** killer_prince has quit IRC12:27
*** bknudson has quit IRC12:35
*** mrmartin has joined #openstack-meeting-312:36
*** e0ne has joined #openstack-meeting-312:37
*** haleyb has joined #openstack-meeting-312:37
*** haleyb has quit IRC12:42
*** mwagner_afk has joined #openstack-meeting-312:43
*** muralia has joined #openstack-meeting-312:43
*** yamamoto has quit IRC12:45
*** amotoki has joined #openstack-meeting-312:51
*** coolsvap|away is now known as coolsvap12:51
*** salv-orlando has quit IRC12:52
*** egallen has quit IRC12:58
*** coolsvap is now known as coolsvap|away13:01
*** egallen has joined #openstack-meeting-313:02
*** coolsvap|away is now known as coolsvap13:08
*** peristeri has joined #openstack-meeting-313:08
*** openstack has quit IRC13:17
*** openstack has joined #openstack-meeting-313:17
*** ChanServ sets mode: +o openstack13:17
*** lazy_prince has joined #openstack-meeting-313:20
*** shwetaap1 has joined #openstack-meeting-313:27
*** shwetaap has quit IRC13:31
*** sdake_ has joined #openstack-meeting-313:32
*** singlethink has joined #openstack-meeting-313:33
*** egallen has quit IRC13:36
*** egallen has joined #openstack-meeting-313:38
*** singleth_ has joined #openstack-meeting-313:45
*** egallen has quit IRC13:45
*** yamamoto has joined #openstack-meeting-313:46
*** coolsvap is now known as coolsvap|away13:46
*** bknudson has joined #openstack-meeting-313:48
*** fallenpegasus has joined #openstack-meeting-313:48
*** singlethink has quit IRC13:49
*** yamamoto has quit IRC13:51
*** egallen has joined #openstack-meeting-313:51
*** salv-orlando has joined #openstack-meeting-313:52
*** bknudson has quit IRC13:54
*** salv-orlando has quit IRC13:57
*** egallen has quit IRC13:58
*** ativelkov has left #openstack-meeting-313:58
*** fallenpegasus has quit IRC13:58
*** baoli has quit IRC13:59
*** yamamoto has joined #openstack-meeting-314:02
*** baoli has joined #openstack-meeting-314:02
*** bryan_att has joined #openstack-meeting-314:04
*** jckasper has quit IRC14:06
*** sigmavirus24_awa is now known as sigmavirus2414:07
*** bknudson has joined #openstack-meeting-314:08
*** zz_jgrimm is now known as jgrimm14:09
*** haleyb has joined #openstack-meeting-314:09
*** sdake_ has quit IRC14:12
*** marun has joined #openstack-meeting-314:16
*** haleyb has quit IRC14:21
*** marun has quit IRC14:22
*** hichihara has joined #openstack-meeting-314:23
*** VW_ has quit IRC14:26
*** nkrinner has quit IRC14:29
*** Piet has joined #openstack-meeting-314:42
*** lazy_prince has quit IRC14:43
*** e0ne is now known as e0ne_14:44
*** sballe has joined #openstack-meeting-314:44
*** Vikram has joined #openstack-meeting-314:46
*** stevemar has joined #openstack-meeting-314:46
*** e0ne_ is now known as e0ne14:49
*** sdake has joined #openstack-meeting-314:51
*** jpomero has quit IRC14:53
*** JeanBriceCombebi has quit IRC14:54
*** JeanBriceCombebi has joined #openstack-meeting-314:55
*** VW_ has joined #openstack-meeting-314:55
*** yamamoto has quit IRC14:56
*** ttrifonov is now known as zz_ttrifonov14:57
*** yamahata has joined #openstack-meeting-314:59
*** haleyb has joined #openstack-meeting-314:59
*** yamamoto has joined #openstack-meeting-315:01
*** galstrom has joined #openstack-meeting-315:01
*** matrohon has joined #openstack-meeting-315:02
*** sarob has joined #openstack-meeting-315:03
*** bauzas is now known as JustinBieber15:04
*** absubram has joined #openstack-meeting-315:05
*** JustinBieber is now known as NotJustinBieber15:05
*** absubram has left #openstack-meeting-315:06
*** NotJustinBieber is now known as bauzas15:06
*** jckasper has joined #openstack-meeting-315:07
*** mrunge has quit IRC15:08
*** sarob has quit IRC15:10
*** belmoreira has quit IRC15:21
*** Networkn3rd has joined #openstack-meeting-315:21
*** jpomero has joined #openstack-meeting-315:22
*** JeanBriceCombebi has quit IRC15:24
*** jxstanford has joined #openstack-meeting-315:24
*** amotoki has quit IRC15:26
*** etoews has joined #openstack-meeting-315:26
*** sarob has joined #openstack-meeting-315:29
*** matrohon has quit IRC15:32
*** pballand has joined #openstack-meeting-315:32
*** armax has joined #openstack-meeting-315:33
*** mestery has joined #openstack-meeting-315:34
*** amotoki has joined #openstack-meeting-315:35
*** mestery_ has joined #openstack-meeting-315:35
*** singleth_ has quit IRC15:35
*** matrohon has joined #openstack-meeting-315:38
*** mestery has quit IRC15:39
*** mickeys has joined #openstack-meeting-315:39
*** mestery_ is now known as mestery15:40
*** sdake has quit IRC15:42
*** marun has joined #openstack-meeting-315:43
*** pballand has quit IRC15:43
*** e0ne is now known as e0ne_15:46
*** pbrooko has quit IRC15:47
*** e0ne_ is now known as e0ne15:47
*** ajmiller has joined #openstack-meeting-315:48
*** angela-s has joined #openstack-meeting-315:50
*** armax has quit IRC15:50
*** hichihara has quit IRC15:51
*** marun has quit IRC15:51
*** pballand has joined #openstack-meeting-315:52
*** puranamr has joined #openstack-meeting-315:53
*** shwetaap1 has quit IRC15:54
*** marun has joined #openstack-meeting-315:55
*** devvesa has quit IRC15:56
*** beagles is now known as beagles_brb15:56
*** sahid has quit IRC15:59
*** pballand has quit IRC16:01
*** yamamoto has quit IRC16:01
*** sayaji15 has joined #openstack-meeting-316:03
*** jgrimm is now known as zz_jgrimm16:03
*** pballand has joined #openstack-meeting-316:04
*** armax has joined #openstack-meeting-316:05
*** sdake has joined #openstack-meeting-316:05
*** kebray has joined #openstack-meeting-316:06
*** lexholden has joined #openstack-meeting-316:07
*** SumitNaiksatam has quit IRC16:08
*** armax has quit IRC16:08
*** yamamoto has joined #openstack-meeting-316:08
*** SumitNaiksatam has joined #openstack-meeting-316:08
*** bpokorny has joined #openstack-meeting-316:08
*** singlethink has joined #openstack-meeting-316:11
*** yamamoto has quit IRC16:21
*** marun has quit IRC16:23
*** salv-orlando has joined #openstack-meeting-316:23
*** yamahata has quit IRC16:24
*** yamamoto has joined #openstack-meeting-316:26
*** mestery has quit IRC16:28
*** e0ne has quit IRC16:29
*** Swami has joined #openstack-meeting-316:29
*** krtaylor has quit IRC16:29
*** puranamr has quit IRC16:30
*** dims has quit IRC16:30
*** puranamr has joined #openstack-meeting-316:31
*** safchain has quit IRC16:31
*** sayaji15 has quit IRC16:32
*** dims has joined #openstack-meeting-316:33
*** angela-s has quit IRC16:33
*** shwetaap has joined #openstack-meeting-316:36
*** beagles_brb is now known as beagles16:38
*** yamamoto has quit IRC16:38
*** Vikram has quit IRC16:39
*** kebray has quit IRC16:39
*** mrmartin has quit IRC16:41
*** kebray has joined #openstack-meeting-316:44
*** baoli has quit IRC16:46
*** SumitNaiksatam has quit IRC16:49
*** baoli has joined #openstack-meeting-316:51
*** krtaylor has joined #openstack-meeting-316:51
*** yamamoto has joined #openstack-meeting-316:55
*** masahito has joined #openstack-meeting-316:56
*** thinrichs has joined #openstack-meeting-316:58
*** mpavlase has quit IRC17:00
*** haleyb has quit IRC17:00
*** haleyb has joined #openstack-meeting-317:01
*** zz_jgrimm is now known as jgrimm17:01
thinrichsHi all.  Time for the Congress meeting17:01
*** dontalton has joined #openstack-meeting-317:01
thinrichs#startmeeting CongressTeamMeeting17:01
openstackMeeting started Tue Jun 23 17:01:43 2015 UTC and is due to finish in 60 minutes.  The chair is thinrichs. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: CongressTeamMeeting)"17:01
openstackThe meeting name has been set to 'congressteammeeting'17:01
thinrichsWho's here this week?  I know alexsyip is out of town.17:02
masahitoHi17:02
thinrichsmasahito: hi!17:03
thinrichspballand: ping17:03
*** baoli has quit IRC17:03
bryan_attHi17:04
*** matrohon has quit IRC17:05
pballandhi17:05
thinrichsbryan_att, pballand: hi17:06
thinrichsWe have a few items to discuss today.17:06
thinrichsSo instead of everyone doing status updates, does anyone have anything they need help from the group for?17:06
bryan_attthinrichs: for the agenda, I'm looking to replicate or re-use the Vancouver Contgress hands-on-lab environment, for internal and OPNFV education/experimentation17:07
thinrichs#topic quick-status17:07
*** openstack changes topic to "quick-status (Meeting topic: CongressTeamMeeting)"17:07
thinrichsbryan_att: got it.17:08
*** DericHorn-HP has joined #openstack-meeting-317:08
thinrichsAnyone else?17:08
thinrichsHere's the agenda then.17:08
thinrichsmid-cycle sprint17:08
thinrichstalk submission17:08
thinrichsoslo liaison17:08
thinrichsmilestones17:08
thinrichsHOL17:08
thinrichs#topic mid-cycle sprint17:08
*** openstack changes topic to "mid-cycle sprint (Meeting topic: CongressTeamMeeting)"17:08
thinrichsWe have 6 people interested in the mid-cycle sprint: masahito, peter, alex, zhenzan, sayaji, and me17:09
thinrichsSo we need to find date, time, and place.17:10
thinrichsSince at least half are in the bay area, it makes sense to host it there.17:10
pballandI won’t be able to make during july17:10
thinrichsJune is almost gone, so how about August?17:11
pballand+1 for bay area17:11
masahito+1 for August17:12
pballandI can look into hosting it at VMware again if that works for people17:12
thinrichspballand: that'd be great!  Thanks!17:12
thinrichsmasahito: does the Bay Area work for you?17:12
pballandlast year we had quite a large turnout - if we can lock down dates I can see about reserving some space17:12
masahitoeverywhere in U.S is Ok17:13
masahitobecause I will fly from Tokyo17:13
*** fitoduarte has joined #openstack-meeting-317:13
bryan_attWould you have ability to dial-in or use webex etc? If possible I will try to be there but remote attendance would be a good option.17:13
pballandbryan_att: last year we tried and had mixed results for those online17:14
bryan_attyes, mixed at best I know17:14
thinrichsmasahito: understood.  (On a side note, I'll be hitting you up for tourist stuff at the next summit.  :))17:14
pballandwe can certainly do it again, but no promises on quality17:14
thinrichsbryan_att: the plan was for more of a code sprint than a general policy summit.17:15
pballandhow about Aug 3-4 or 6-7?17:15
thinrichswe were talking about working on a specific feature: making our message bus work across processes and across machines17:15
thinrichsand then writing the code to implement.17:15
thinrichsAlso some design discussions for scale out assuming that feature is in place.17:15
thinrichsBut yes a remote option is a good idea.17:16
pballandhow long? I think 2 days makes sense if people are traveling out17:16
thinrichspballand: I'm avail Aug 3-4 and 6-7.  And 2 days seems good.17:16
thinrichsI think we should defer to those who are traveling longer distances, of course.17:16
masahito6-7 is better for me.17:16
thinrichsLet's find a couple of dates, since there are some people who would like to attend but aren't at this meeting.17:17
pballandI could also do July 30-31 if we want it closer to the middle of the cycle :)17:17
*** mrmartin has joined #openstack-meeting-317:17
thinrichsThe week of July 30-31 is the OpenDaylight conf.17:18
thinrichsI have a panel, but I don't know the exact day yet.  I'm looking.17:18
thinrichsFound it.  It's July 28, so July 30-31 works for me.17:19
masahito3-4 is also ok if others isn't available Aug 6-7.17:19
pballandfyi: here are the other sprints: https://wiki.openstack.org/wiki/Sprints17:20
thinrichsmasahito: would 3-4 be preferable to July 30-31 for you?17:20
masahito3-4 is better than July 30-31.17:21
masahitoI have a private plan in Aug 1.17:21
*** tsandall_ has joined #openstack-meeting-317:21
thinrichsmasahito: sounds good.17:21
thinrichsLet's find one more option the next week, in case someone is on vacation the whole first week of August.17:22
thinrichsMy next week is free.  Masahito: what days that week work for you?17:23
masahitoIn August?17:23
thinrichsAug 10-1417:23
pballand10-14 is clear for me as well17:23
masahito10-13 is available.17:24
thinrichsThanks.  We've got some options now.17:24
*** yamamoto has quit IRC17:24
thinrichs#info Possible dates, in order of preference Aug 6-7, Aug 3-4, Aug 10-1317:24
thinrichs#action pballand will look into hosting at VMware17:25
*** mestery has joined #openstack-meeting-317:25
pballandthinrichs: are you going to post to the ML?17:25
thinrichs#action thinrichs will touch base with other 3 who were interested to settle on date and I will post the decision to ML17:25
thinrichsNext topic: milestones17:26
thinrichs#topic milestones17:26
*** openstack changes topic to "milestones (Meeting topic: CongressTeamMeeting)"17:26
thinrichsWe have a bunch of blueprints that are up, but few people have signed up for them or chosen a milestone (liberty-1, liberty-2, liberty-3)17:26
thinrichs#link https://blueprints.launchpad.net/congress17:26
thinrichsThis week is the end of liberty-117:27
thinrichsTime flies.  :)17:27
thinrichsSo let's have everyone create blueprints, sign up for them, and assign a milestone.17:27
masahitook. btw, If anyone doesn't assign in blueprint, is it ok I get assignee?17:28
thinrichsAnd if you don't have the right to assign a milestone, tell me when you think it'll get done.17:28
*** baoli has joined #openstack-meeting-317:29
pballand#link https://wiki.openstack.org/wiki/Liberty_Release_Schedule17:29
thinrichsmasahito: yep—feel free to sign up for anything that doesn't have an assignee17:29
thinrichspballand: thanks for the link.17:29
*** VW_ has quit IRC17:30
thinrichsIt's worth mentioning that unlike the last cycle where we let the feature freeze period slip, this cycle we're going to do feature freeze at the same time as everyone else.17:30
thinrichsIt'll help us get on track for the next cycle.17:30
thinrichsAny questions about the blueprints?17:32
thinrichsIn particular, I'd like to see us sign up for the highest priority BPs.17:32
thinrichs#action everyone will sign up for blueprints and assign milestones or email thinrichs with milestone requests17:33
thinrichsNext topic is whether we want to submit a talk for the next OpenStack summit17:34
thinrichs#topic talk submission at summit17:34
*** openstack changes topic to "talk submission at summit (Meeting topic: CongressTeamMeeting)"17:34
pballandit seems the HOL was popular in Vancouver, so it seems we should propose that again17:34
thinrichsI think we should submit at least one talk.  Ideas?17:34
thinrichspballand: sounds good.  Anything qualitatively different from last time?17:34
masahitosorry, what does HOL mean?17:35
thinrichshands-on-lab17:35
masahitothinrichs: thank you.17:35
thinrichsHOL from vancouver:17:35
thinrichs#link https://docs.google.com/document/d/1lXmMkUhiSZYK45POd5ungPjVR--Fs_wJHeQ6bXWwP44/pub17:35
pballandthinrichs: no changes come to mind, unless there was feedback from the last one17:36
thinrichsIt would be nice to highlight some new feature we added this cycle.17:36
*** Yi_ has joined #openstack-meeting-317:36
thinrichsSeems we're focusing on scale/performance/architecture this cycle.17:36
thinrichsThat's hard to put into a HOL.17:36
thinrichsMaybe we could do something around delegation?17:37
pballandfrom a proposal perspective, do  we need to decide this now?17:37
thinrichsOk.  We should think about the details.  But we can put that off until it's been accepted.17:37
thinrichsAny other talk ideas?17:37
bryan_attIt would be good to have an update on the feature roadmap, e.g. state of proactive enforcement work17:38
masahitoI plan to submit a general session about congress with my use-case.17:38
thinrichsbryan_att: The update at Vancouver wasn't well attended.  So I'm hesitant to just propose a 'Congress Update' talk.17:39
thinrichsmasahito: I like the idea of a use-case driven talk.17:39
thinrichsI was thinking of something like… Policy Federation between Congress, Keystone, and CloudFoundry17:39
masahitobut I think this idea is too specific to get congress official time slots.17:40
thinrichsmasahito: I'd imagine targeting a use-case talk to a specific track, like telcos.17:40
pballandI like operator-driven use-case talks, but don’t have a specific topic17:41
thinrichsIf there's an audience that is deeply interested in the use case, and there's a track for that audience, you may have better luck.17:41
*** jxstanford has quit IRC17:41
thinrichsFor the policy federation talk, I was thinking about doing some sort of inter-service policy exchange with Keystone and CloudFoundry.17:42
thinrichsMaybe start by pulling policy.json out of OpenStack and comparing that to a Congress policy.17:42
thinrichsThen maybe gate CloudFoundry operations on a Congress policy.17:42
thinrichsThoughts?17:42
bryan_attMaybe some federation discussion around OpenDaylight GBP and Congress?17:43
thinrichsbryan_att: that's been on the stack for a while.  Good thought.17:43
*** jwy has joined #openstack-meeting-317:43
thinrichsjwy: here for the Congress meeting?17:44
*** marun has joined #openstack-meeting-317:44
bryan_atte.g. how do we know when an SDNC action has violated a policy expressed in Congress - I guess it needs a driver...17:44
jwythinrichs: hi, yep, albeit a bit late..17:44
thinrichsbryan_att: what's an SDNC?17:44
bryan_attSDN Controller17:45
thinrichsjwy: we're brainstorming talk ideas for the summit.  Any thoughts?17:45
*** Yi_ has quit IRC17:45
thinrichsbryan_att: I think we typically expect the SDNC to do the correct thing, i.e. we have a datasource driver for the SDNC, but we don't have datasource drivers for the underlying components that the SDNC is manipulating.17:46
thinrichsbryan_att: at least, that's how we typically think about it.  I don't know if anyone has thought about applying Congress to check the correctness of the SDNC.17:46
jwylooking at the meeting log for today so far. agreed about doing the hol again17:46
*** irenab has joined #openstack-meeting-317:47
*** Yi_ has joined #openstack-meeting-317:47
thinrichsok.  low on time.  Let's everyone keep thinking since the deadline is coming up soon.17:48
jwyanother intro talk? probably a different mix of attendees, being in asia vs. north america17:48
thinrichsjwy: It's worth submitting for sure, but I'm dubious it'll be accepted.17:49
thinrichsLet's jump to bryan's topic.17:49
bryan_attthinrichs: the idea is that a valid action at the SDNC may nonetheless cause some side-effect that is discoverable through a datasource driver17:49
thinrichs#topic redeployment of the HOL17:49
*** openstack changes topic to "redeployment of the HOL (Meeting topic: CongressTeamMeeting)"17:49
*** armax has joined #openstack-meeting-317:50
thinrichsbryan_att: I see the attraction of applying Congress to monitor the SDNC's behavior.  I just don't know what the ramifications are.17:50
thinrichsbryan_att: want to tell us what you want to do with the HOL?17:50
bryan_attSorry, browser issue17:52
bryan_attWe want to replicate the HOL to educate internal teams and OPNFV on what you can do with Congress17:52
bryan_attWe are looking to the role of Congress in our NFVI and need to demo use cases that people care about17:53
thinrichsbryan_att: Cool!17:53
bryan_attAlso inform them about the roadmap, e.g. how proactive enforcement can be done today but what it implies re Congress-external functions17:53
bryan_attSo it would be a great thing to be able to replicate the HOL environment in our lab, and then expose that to people who want to learn more about it.17:54
bryan_attSimilar to TryStack, but with Congress and scripted activities17:54
thinrichsbryan_att: Got it.  You basically want the setup instructions for getting the VMs to the state they were in at the start of the HOL.17:55
thinrichsRight?17:55
bryan_attYes17:55
thinrichsThe people who did that aren't on IRC right now.  I'll take an action item to chase them down and see what they can give us.17:55
thinrichs#action thinrichs will look into setup instructions for the Vancouver HOL.17:55
bryan_attThanks, I don't want to create a lot of work for folks but appreciate any help17:56
thinrichsbryan_att: anything else we can do to help?17:56
bryan_attFor now, any details you can send will be helpful17:56
thinrichsIt'd be good to have basic setup instructions available.  Hopefully next time we'll tack them on at the end of the doc, at least.17:56
thinrichsbryan_att: will do.17:56
thinrichsJust a couple of minutes left.17:57
thinrichs#topic open discussion17:57
*** openstack changes topic to "open discussion (Meeting topic: CongressTeamMeeting)"17:57
thinrichsOne thing we're supposed to do is migrate congress/openstack/common/log  to oslo.logging17:58
thinrichsAny takers?  I can add a Blueprint for it.17:58
thinrichsOr maybe just a bug report.17:59
thinrichsWe're out of time.  We hammered through a bunch of stuff this week.  Nice work all!18:00
masahitoIf there is a bug report or bp to track it, I will patch it.18:00
*** mestery has quit IRC18:00
thinrichsmasahito: deal.  I'll put up the bug report and email it to you.18:00
thinrichsThanks all!18:00
thinrichs#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Tue Jun 23 18:00:56 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/congressteammeeting/2015/congressteammeeting.2015-06-23-17.01.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2015/congressteammeeting.2015-06-23-17.01.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/congressteammeeting/2015/congressteammeeting.2015-06-23-17.01.log.html18:01
*** mestery has joined #openstack-meeting-318:01
*** masahito has quit IRC18:01
*** mwagner_afk has quit IRC18:02
*** ivar-lazzaro has joined #openstack-meeting-318:04
*** s3wong has joined #openstack-meeting-318:05
*** armax has quit IRC18:05
*** VW_ has joined #openstack-meeting-318:06
*** e0ne has joined #openstack-meeting-318:08
*** mestery has quit IRC18:10
*** armax has joined #openstack-meeting-318:13
*** jwy has left #openstack-meeting-318:14
*** amotoki has quit IRC18:17
*** armax has quit IRC18:18
*** mickeys has quit IRC18:23
*** yamamoto has joined #openstack-meeting-318:25
*** sbalukoff has joined #openstack-meeting-318:26
*** e0ne is now known as e0ne_18:27
*** yamamoto has quit IRC18:30
*** e0ne_ has quit IRC18:32
*** reed has quit IRC18:36
*** markmcclain has quit IRC18:36
*** puranamr has quit IRC18:37
*** puranamr has joined #openstack-meeting-318:37
*** jxstanford has joined #openstack-meeting-318:39
*** haleyb has quit IRC18:41
*** e0ne has joined #openstack-meeting-318:41
*** puranamr has quit IRC18:41
*** puranamr has joined #openstack-meeting-318:44
*** puranamr has quit IRC18:46
*** puranamr has joined #openstack-meeting-318:48
*** natorious is now known as zz_natorious18:49
*** puranamr has quit IRC18:50
*** belmoreira has joined #openstack-meeting-318:51
*** thinrichs has quit IRC18:51
*** irenab has quit IRC18:52
*** baoli has quit IRC18:54
*** baoli has joined #openstack-meeting-318:56
*** puranamr has joined #openstack-meeting-318:56
*** terrylhowe has joined #openstack-meeting-318:58
*** stevelle has joined #openstack-meeting-318:59
*** singleth_ has joined #openstack-meeting-318:59
*** thinrichs has joined #openstack-meeting-319:00
briancurtin#startmeeting python-openstacksdk19:00
openstackMeeting started Tue Jun 23 19:00:24 2015 UTC and is due to finish in 60 minutes.  The chair is briancurtin. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: python-openstacksdk)"19:00
*** DericHorn-HP has quit IRC19:00
openstackThe meeting name has been set to 'python_openstacksdk'19:00
terrylhoweo/19:00
briancurtinif you're here for the SDK meeting, say hi19:00
etoewso/19:01
*** Yi_ has quit IRC19:01
briancurtin#topic Add Heat resource support19:02
*** openstack changes topic to "Add Heat resource support (Meeting topic: python-openstacksdk)"19:02
briancurtin#link https://review.openstack.org/#/c/181063/19:02
*** DericHorn-HP has joined #openstack-meeting-319:02
stevelleo/19:02
*** dtroyer has joined #openstack-meeting-319:02
briancurtini think the last patchset addressed etoews concern, and i think overall it looks alright. it'll end up changing a bit later depending on what happens with find, but should go on as-is if it works19:02
*** singlethink has quit IRC19:02
etoews+119:03
dhellmanno/19:03
terrylhoweon my todo list to look at that one, but it was real close before19:04
etoewscool.19:04
briancurtin#topic marking APIs as Beta in the SDK19:04
*** openstack changes topic to "marking APIs as Beta in the SDK (Meeting topic: python-openstacksdk)"19:04
briancurtinnot sure who put this in - anyone?19:04
etoewsthat was me19:04
etoewsreasoning...19:05
etoewswe put a bunch of code into the sdk and release it. even though we're pre 1.0 and instability *should* be assumed. it's hard to tell what's stable and what isn't.19:05
etoewsthis topic is actually more important post 1.019:06
etoewswe'll be putting code in post 1.0 and users will have no way to know what's stable and what isn't19:06
etoewssince it all winds up getting released19:06
*** DericHorn-HP_ has joined #openstack-meeting-319:07
terrylhowewe could start a plugin repo for new dev19:07
*** Longgeek_ has quit IRC19:07
briancurtinthen it all falls apart like the current mess19:07
etoewsperhaps we can mark entire services as beta?19:07
*** DericHorn-HP has quit IRC19:07
*** DericHorn-HP_ is now known as DericHorn-HP19:07
briancurtincurrent mess meaning *clients19:07
etoewswe went down the "alternate" repo path with jclouds. it was horrible.19:07
stevellethis seems related to the next agenda topic19:08
briancurtinetoews: within CPython we have the idea that new APIs can be added for one or more releases in a provisional state. i believe the ipaddr module went in like this19:08
etoewsthat's the kind of thing i had in mind19:08
briancurtinas for versioning, i think we probably just have to be super strict on version numbers and grow like browsers do, where we'll be on version 35 at this time next year19:09
briancurtinor does that not solve what you're looking for etoews?19:09
etoewsi'm not as concerned with semver (although i do like it) but more of a way of signaling to users that something isn't fully baked yet.19:10
etoewsfor instance, i'd be fine with not incrementing major version if it was a beta api that we were breaking backwards compat with.19:10
briancurtinon that, then i'd probably stick with the provisional thing. in CPython that's really just signaled within teh PEP that added something, as well as in documentation. i wouldnt mind some kind of decorator that logged a message saying it's a provisional API, or the warning module to emit something19:10
*** jxstanford has quit IRC19:11
etoews++19:11
briancurtini know someone is going to say "but people don't read the docs" and the answer is "too bad"19:11
*** markmcclain has joined #openstack-meeting-319:11
etoewsisn't that what emitting something would be for?19:12
*** markmcclain has quit IRC19:12
briancurtinetoews: assuming people pay attention to them, and i forget what the situation is with warnings showing up in the default case of just running "python"19:12
*** markmcclain has joined #openstack-meeting-319:13
briancurtini know DeprecationWarning is silenced by default and you have to explictly turn warnings to be louder to get it. not sure about other types, or custom types19:13
*** reed has joined #openstack-meeting-319:13
etoewswell anything, it becomes more import post 1.0. i'll log a bug to keep track of it.19:13
briancurtincool19:13
etoewss/anything/anyway/19:13
briancurtin#topic functional testing of "non-core" service19:14
*** openstack changes topic to "functional testing of "non-core" service (Meeting topic: python-openstacksdk)"19:14
briancurtin"can openstack.tests.functional.base.requires_service be changed to wrap an entire test class?"19:14
etoewsme again19:14
briancurtinthat answer is yes, it can be a class decorator19:14
stevelleI'd like to decide what might be provisional from the previous discussion. Is this topic a good place to do that?19:15
briancurtinetoews: are we going to bother defining core/non-core, or does this just mean stuff that doesn't show up in a usual devstack?19:15
briancurtinyeah actually let's pause this for a second19:15
etoewsusual devstack is the answer i think19:15
briancurtinstevelle: may as well, we've got the time19:15
briancurtinetoews: any specific example of something you'd want to put through a provisional state?19:16
etoewsbasically anything new19:16
etoewsfor example...19:16
etoewsi was doing the message service and i got the interface wrong the first time around.19:17
etoewsa release could have happened before i had a chance to fix it19:17
etoewsnow i've got someone thinking they can depend on this crappy interface19:17
etoewsand i come along and change it in the next release19:17
stevelleok, I just wanted to clarify.  Are there OpenStack services in the sdk that we believe are currently in a provisional state?19:18
etoewsi just want to be able to signal to users that certain services are under development and to expect a bumpy ride19:18
stevellethis is a great topic, as it also helps identify where the project team can apply resources as well19:19
etoewsheat19:19
etoewsmessage19:19
briancurtinstevelle: im not really sure if any entire services are like that19:19
briancurtinetoews: i think we're on the same page with how you're thinking of this19:19
etoewsit's still so early on in the development of those i'm not confident the interfaces are stable19:19
etoewsbut again we're pre 1.0 so it's kinda all fair game.19:20
briancurtingood to think about though. we have somewhat of a free pass right now but real life starts fairly soon19:21
etoewsnot that i think we're due for any huge interface changes19:21
* etoews looks forward to real life19:21
briancurtinas we get around to more functional tests im sure we'll run into stuff that just does not work at all as-is, and will need to be changed around19:21
terrylhoweyeh, that’s why it is taking so long to write teh functional tests19:22
etoewsmore functional tests for the functional test god19:22
terrylhoweonce we get a lazy load for the modules, that would be a good point to put up some warning on deprecated/beta services19:22
briancurtinwe're at the point now where no resource/proxy changes should go in without functional test changes as well19:22
stevelleand we are not thinking about provisional tag for things that don't work or are not insufficiently tested, just for things that may have api changes at proxy or above, right?19:23
etoewsterrylhowe: when you say that is it because things are changing out from underneath you?19:23
briancurtin(i guess we've been there a while and i think a few people have said that...but anyway)19:23
stevellenot/insufficiently*19:23
terrylhoweno, the proxies were never really functionall tested in a lot of cases and they just don’t work19:23
*** yamahata has joined #openstack-meeting-319:23
*** yamahata has quit IRC19:24
briancurtinstevelle: things that don't work should just be pulled out, i woudnt want to cover up bugs with this. once we get to a better level of functional testing this tag might make sense19:24
etoewsah. yes. i work under the assumption that if there's no functional test it's most likely broken.19:24
briancurtinit should really only be used as an excuse for the API changing, not the behavior19:24
*** yamahata has joined #openstack-meeting-319:24
*** Networkn3rd has quit IRC19:25
*** geoffarnold has joined #openstack-meeting-319:25
*** zz_natorious is now known as natorious19:25
*** jtomasek has quit IRC19:26
briancurtinwe especially  have the broken proxy issue when it comes to most anything that needs path_args19:26
briancurtinbut we'll get around to those, or are getting around to those19:26
stevelleI forget if we have a coverage report for functional tests19:27
stevelleI don't believe I recall seeing one19:27
briancurtinnot currently, but should add it. only unit test now19:27
briancurtinwill have to figure out how to configure it since we'll want it to only report based on proxy classes and not the entire openstack namespace19:28
stevellegot it.19:28
briancurtinshould get back to "functional testing of "non-core" service"19:29
stevelleI think we can return to the functional testing topic yes19:29
briancurtinetoews: so what else did you have in mind here?19:29
etoewsmostly just being able to requires_service at a class level.19:30
etoewsi've got a bunch of message functional tests but haven't committed them because a call per method is so slow.19:30
briancurtinthat shouldn't be too bad, and we should actually put that on every single class just to be safe and not assume anything is actually there19:30
*** fifieldt_ has joined #openstack-meeting-319:30
briancurtinetoews: i can look into that right after this then19:31
etoewscool. thx.19:31
terrylhowemay be related to this topic.  I was wondering if we could get rid of setupClass teardownClass because of the change in tox.ini19:32
etoewsin the base functional class?19:32
terrylhoweI’d like to try again.  I made that change originally before all tests from one class were forced to one thread19:32
briancurtini'm not familiar with a change to tox.ini that would affect those methods19:33
etoewsi noticed that ostestr has a --serial param19:33
etoewsthat could be handy for functional tests19:33
terrylhoweyes19:33
terrylhoweanyway, I’d like to explore the standard format again, but there is a lot out there at the moment19:34
*** fifieldt has quit IRC19:34
*** SumitNaiksatam has joined #openstack-meeting-319:34
*** belmoreira has quit IRC19:35
briancurtin#topic Resource.find19:36
*** openstack changes topic to "Resource.find (Meeting topic: python-openstacksdk)"19:36
terrylhowesomewhat related ostestr has a bug I don’t think the fix has been released, probably only on ubuntu https://review.openstack.org/#/c/187300/19:36
briancurtin#link https://review.openstack.org/#/c/193728/19:36
briancurtini haven't seen that one, running on osx19:36
terrylhoweI kind of figured most people were on osx19:37
briancurtinwith this Resource.find, terrylhowe i'm not sure if you saw my response to your comment about it working like the previous one, but i wonder if we shouldn't push the "find one item by name or id" off to each of the get_* methods in a proxy?19:37
*** Longgeek has joined #openstack-meeting-319:38
stevelleI test under ubuntu fwiw19:38
*** puranamr has quit IRC19:38
*** puranamr has joined #openstack-meeting-319:39
briancurtinwe could just change the from_id method to be a little smarter, or something else has that behavior that knows per-resource if it's name or id that matters, and you'd only get one resource back or nothing. i think we briefly talked about that a while back but didn't go that route19:39
briancurtini'm thinking about that because find running a query based on list makes me think find_* methods should actually be plural, since they are running regex queries that would return multiple items19:40
terrylhowethe whole find thing I’m not really ready to deal with.  I haven’t added functional tests for most of them19:40
briancurtini wouldnt even do that because they will all break19:40
briancurtinmost of them are broken as-is and we'd just break them more19:40
terrylhowehaving find return multiple items makes me think it should be just part of list19:40
briancurtinAs in, we should add this behavior to list and then make the current find better?19:42
*** puranamr has quit IRC19:43
briancurtinmaybe this does make sense, as list+query params (when available) does this19:43
terrylhoweanytime you are searching for some resource, unless by id (or maybe name) you could get multiple responses19:43
briancurtini'll see how i can shift this over to list to make up for the ones that don't support query params, or even supplement the ones that do19:44
*** jtomasek has joined #openstack-meeting-319:44
terrylhoweI’d just like to see something like if (queryparam): slow client side search else: high perf generator19:44
stevelle+119:45
terrylhowesince support is so terrible for query params, it seems like we could just pertend they don’t exist at all for now19:45
terrylhoweand just do the filtering client side19:46
stevelleI'd also be happy with just delegating the filtering to the consumer of the list as well tbh19:46
briancurtininserting our own search in between the proxy call and the resource.list when query params aren't supported shouldn't be too hard. anything we can let the server do to reduce the data returned and work faster i think we should try to enable19:47
terrylhoweif it isn’t too much work, great19:47
stevellejust as a note, it seems appropriate to bring up the filtering guideline from the API-WG here.19:48
*** singlethink has joined #openstack-meeting-319:48
stevellehttps://review.openstack.org/#/c/177468/19:49
briancurtinfiltering as in reducing the fields returned, or filtering as in reducing the amount of resources returned?19:49
stevelleresources returned19:49
stevellewould like to be sure we are providing the best guidance for services to make this support better in the future.19:50
briancurtini'll take a look, but isn't that a server-side thing? i'm not entirely sure what the takeaway of that would be here19:50
briancurtinoh19:50
stevelleparticularly, as terrylhowe points out, support is currently spotty at best19:51
*** Rockyg has joined #openstack-meeting-319:51
*** singleth_ has quit IRC19:52
*** haleyb has joined #openstack-meeting-319:53
terrylhowemay be we should have some way the customer asks for server or client side filtering manually19:53
briancurtini was just thinking about solving some of this with a local=bool flag, but probably not even exposing that at the proxy level. at the proxy level we'd know if a resource can do server-side querying and send those args through, or we pass it through the local query. similar to how we have to set paginated=bool for them at that levlel19:54
*** sdake has quit IRC19:54
etoewslocal=bool seems like a cognitive burden on the user19:55
briancurtinit wouldnt be on the user, it would be handled the same way paginated=bool is right now19:55
etoewsah19:55
etoewsmissed the "not even exposing that..."19:56
* briancurtin blows whistle for 2 minute warning19:58
terrylhowenothing else here19:59
* briancurtin sounds a loud horn20:00
briancurtin#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Jun 23 20:00:14 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python_openstacksdk/2015/python_openstacksdk.2015-06-23-19.00.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2015/python_openstacksdk.2015-06-23-19.00.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/python_openstacksdk/2015/python_openstacksdk.2015-06-23-19.00.log.html20:00
*** mrmartin has quit IRC20:01
*** terrylhowe has left #openstack-meeting-320:01
*** dtroyer has left #openstack-meeting-320:01
*** e0ne is now known as e0ne_20:05
*** e0ne_ is now known as e0ne20:05
*** reed has quit IRC20:07
*** jtomasek has quit IRC20:07
*** reed has joined #openstack-meeting-320:08
*** puranamr has joined #openstack-meeting-320:12
*** Networkn3rd has joined #openstack-meeting-320:16
*** SumitNaiksatam has quit IRC20:18
*** Sukhdev has joined #openstack-meeting-320:20
*** SumitNaiksatam has joined #openstack-meeting-320:22
*** kebray has quit IRC20:22
*** baoli has quit IRC20:31
*** dontalton has quit IRC20:32
*** dontalton has joined #openstack-meeting-320:33
*** Rockyg has quit IRC20:40
*** Rockyg has joined #openstack-meeting-320:41
*** DericHorn-HP has quit IRC20:41
*** DericHorn-HP has joined #openstack-meeting-320:42
*** singleth_ has joined #openstack-meeting-320:46
*** kebray has joined #openstack-meeting-320:46
*** puranamr has quit IRC20:46
*** Rockyg has quit IRC20:47
*** Rockyg has joined #openstack-meeting-320:48
*** puranamr has joined #openstack-meeting-320:48
*** singlethink has quit IRC20:49
*** stevelle has left #openstack-meeting-320:50
*** singlethink has joined #openstack-meeting-320:53
*** singleth_ has quit IRC20:56
*** alexpilotti has quit IRC20:57
*** DericHorn-HP has quit IRC20:59
*** peristeri has quit IRC21:00
*** mickeyspiegel has joined #openstack-meeting-321:04
*** puranamr has quit IRC21:08
*** puranamr has joined #openstack-meeting-321:09
*** kebray has quit IRC21:11
*** kztsv_ws is now known as kzaitsev_ws21:13
*** lexholden has quit IRC21:17
*** matrohon has joined #openstack-meeting-321:19
*** kebray has joined #openstack-meeting-321:26
*** matrohon has quit IRC21:28
*** e0ne is now known as e0ne_21:28
*** krtaylor has quit IRC21:29
*** Piet has quit IRC21:29
*** e0ne_ has quit IRC21:29
*** e0ne has joined #openstack-meeting-321:34
*** e0ne is now known as e0ne_21:42
*** e0ne_ is now known as e0ne21:45
*** Piet has joined #openstack-meeting-321:47
*** mpavlase has joined #openstack-meeting-321:49
*** reed has quit IRC21:54
*** e0ne has quit IRC21:55
*** DericHorn-HP has joined #openstack-meeting-321:56
*** reed has joined #openstack-meeting-321:57
*** jpomero has quit IRC21:57
*** marun has quit IRC21:59
*** thinrichs has quit IRC22:00
*** Networkn3rd has quit IRC22:02
*** yamamoto has joined #openstack-meeting-322:03
*** kebray has quit IRC22:05
*** yamamoto has quit IRC22:07
*** Rockyg has quit IRC22:08
*** bknudson has quit IRC22:09
*** s3wong has quit IRC22:13
*** Sukhdev has quit IRC22:19
*** dontalton2 has joined #openstack-meeting-322:19
*** jgrimm is now known as zz_jgrimm22:21
*** yamahata has quit IRC22:23
*** puranamr has quit IRC22:24
*** sigmavirus24 is now known as sigmavirus24_awa22:26
*** puranamr has joined #openstack-meeting-322:28
*** pballand has quit IRC22:28
*** pballand has joined #openstack-meeting-322:31
*** puranamr has quit IRC22:32
*** puranamr has joined #openstack-meeting-322:32
*** puranamr has quit IRC22:36
*** puranamr has joined #openstack-meeting-322:36
*** thinrichs has joined #openstack-meeting-322:39
*** puranamr has quit IRC22:40
*** puranamr has joined #openstack-meeting-322:41
*** galstrom is now known as galstrom_zzz22:41
*** singlethink has quit IRC22:47
*** puranamr has quit IRC22:49
*** puranamr has joined #openstack-meeting-322:49
*** natorious is now known as zz_natorious22:51
*** puranamr has quit IRC22:57
*** baoli has joined #openstack-meeting-322:58
*** baoli has quit IRC22:59
*** baoli has joined #openstack-meeting-323:00
*** bknudson has joined #openstack-meeting-323:02
*** kebray has joined #openstack-meeting-323:03
*** kebray has quit IRC23:04
*** puranamr has joined #openstack-meeting-323:05
*** thinrichs has quit IRC23:05
*** baoli has quit IRC23:06
*** sdake has joined #openstack-meeting-323:07
*** thinrichs has joined #openstack-meeting-323:08
*** kebray has joined #openstack-meeting-323:10
*** kebray has quit IRC23:10
*** kebray has joined #openstack-meeting-323:11
*** pkarikh has quit IRC23:12
*** pballand has quit IRC23:12
*** dontalton2 has quit IRC23:16
*** dontalton has quit IRC23:16
*** shwetaap has quit IRC23:22
*** sdake_ has joined #openstack-meeting-323:23
*** yamamoto has joined #openstack-meeting-323:24
*** VW_ has quit IRC23:26
*** sdake has quit IRC23:26
*** stevemar has quit IRC23:29
*** pballand has joined #openstack-meeting-323:32
*** pballand has quit IRC23:34
*** carl_baldwin has joined #openstack-meeting-323:39
*** sdake_ has quit IRC23:40
*** yamamoto has quit IRC23:41
*** thinrichs has left #openstack-meeting-323:41
*** mpavlase has quit IRC23:43
*** DericHorn-HP has quit IRC23:45
*** yamamoto has joined #openstack-meeting-323:47
*** mickeyspiegel has quit IRC23:49
*** Swami has quit IRC23:51
*** isq has quit IRC23:54
*** shwetaap has joined #openstack-meeting-323:55
*** dims has quit IRC23:56
*** ajmiller has quit IRC23:58

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