Friday, 2014-10-24

*** xgerman has quit IRC00:03
*** vivek-ebay has quit IRC00:13
*** vivek-ebay has joined #openstack-lbaas00:13
*** ajmiller has quit IRC00:17
*** vivek-ebay has quit IRC00:17
*** HenryG has quit IRC00:18
*** dlundquist has left #openstack-lbaas00:22
openstackgerritAdam Harwell proposed a change to stackforge/octavia: TLS Data Security Overview  https://review.openstack.org/13065900:23
*** IZebra has quit IRC00:30
*** mlavalle has quit IRC00:44
*** sbalukoff has quit IRC00:45
*** VijayB_ has quit IRC01:38
*** VijayB has joined #openstack-lbaas01:41
*** IZebra has joined #openstack-lbaas01:52
*** woodster_ has quit IRC02:20
*** fnaval has quit IRC02:40
*** sbalukoff has joined #openstack-lbaas02:51
*** dboik has quit IRC03:02
*** VijayB has quit IRC03:14
*** ksamoray has joined #openstack-lbaas03:26
*** ksamoray has quit IRC04:03
*** dougwig has quit IRC04:03
*** HenryG has joined #openstack-lbaas04:10
*** sbfox has joined #openstack-lbaas04:26
*** sbfox has quit IRC04:30
*** ksamoray has joined #openstack-lbaas04:31
*** ksamoray has quit IRC04:35
*** sbfox has joined #openstack-lbaas04:44
*** sbalukoff has quit IRC04:45
*** vivek-ebay has joined #openstack-lbaas04:52
*** sbalukoff has joined #openstack-lbaas05:09
*** ptoohill has quit IRC05:30
*** TrevorV has quit IRC05:31
*** ptoohill has joined #openstack-lbaas05:32
*** TrevorV has joined #openstack-lbaas05:33
*** ptoohill_ has joined #openstack-lbaas05:37
*** ksamoray has joined #openstack-lbaas05:40
*** ksamoray has quit IRC05:43
*** ptoohill_ has quit IRC05:58
*** ksamoray has joined #openstack-lbaas06:01
*** vivek-ebay has quit IRC06:04
*** sbfox has quit IRC06:13
*** sbalukoff has quit IRC06:15
*** sbalukoff has joined #openstack-lbaas06:28
*** clev has quit IRC06:47
*** mestery has quit IRC06:47
*** mestery has joined #openstack-lbaas06:59
*** clev has joined #openstack-lbaas06:59
*** ksamoray has quit IRC07:14
*** clev has quit IRC07:29
*** mestery has quit IRC07:29
*** mestery has joined #openstack-lbaas07:32
*** mestery has quit IRC07:36
*** clev has joined #openstack-lbaas07:37
*** mestery has joined #openstack-lbaas07:40
*** ksamoray has joined #openstack-lbaas07:52
*** ksamoray has quit IRC07:56
*** ksamoray has joined #openstack-lbaas09:25
*** ksamoray has quit IRC09:30
*** davidlenwell has quit IRC09:53
*** davidlenwell has joined #openstack-lbaas09:53
*** mestery has quit IRC09:55
*** mestery has joined #openstack-lbaas09:56
*** rohara has quit IRC09:58
*** rohara has joined #openstack-lbaas09:59
*** IZebra has quit IRC10:47
*** ksamoray has joined #openstack-lbaas10:51
*** ksamoray has quit IRC10:53
*** ksamoray has joined #openstack-lbaas12:52
*** ksamoray has quit IRC12:53
*** dboik has joined #openstack-lbaas13:15
*** dboik has quit IRC13:32
*** ksamoray has joined #openstack-lbaas13:39
*** ksamoray has quit IRC13:39
*** fnaval has joined #openstack-lbaas13:52
*** dboik has joined #openstack-lbaas13:52
*** IZebra has joined #openstack-lbaas14:04
*** fnaval has quit IRC14:10
*** markmcclain has joined #openstack-lbaas14:50
*** fnaval has joined #openstack-lbaas14:52
*** TrevorV_ has joined #openstack-lbaas14:52
*** ksamoray has joined #openstack-lbaas14:53
*** ksamoray has quit IRC14:56
*** ptoohill_ has joined #openstack-lbaas14:58
*** ptoohill_ has quit IRC15:10
*** ptoohill_ has joined #openstack-lbaas15:11
*** ptoohill_ has quit IRC15:22
*** vivek-ebay has joined #openstack-lbaas15:23
*** xgerman has joined #openstack-lbaas15:24
*** ptoohill_ has joined #openstack-lbaas15:25
*** markmcclain has quit IRC15:41
*** IZebra has quit IRC15:49
*** TrevorV_ has quit IRC15:51
*** enikanorov has joined #openstack-lbaas15:55
*** mlavalle has joined #openstack-lbaas15:55
*** vivek-ebay has quit IRC15:59
*** vivek-ebay has joined #openstack-lbaas16:00
*** jorgem has joined #openstack-lbaas16:00
*** sbalukoff has quit IRC16:01
*** sbalukoff has joined #openstack-lbaas16:02
*** dlundquist has joined #openstack-lbaas16:31
*** barclaac|2 has joined #openstack-lbaas16:35
*** barclaac has quit IRC16:38
*** vivek-ebay has quit IRC16:41
*** ptoohill_ has quit IRC16:47
*** vivek-ebay has joined #openstack-lbaas16:47
*** vivek-ebay has quit IRC16:54
*** ptoohill_ has joined #openstack-lbaas17:05
*** ksamoray has joined #openstack-lbaas17:15
*** barclaac has joined #openstack-lbaas17:16
*** barclaac|2 has quit IRC17:19
*** ksamoray has quit IRC17:36
*** ksamoray has joined #openstack-lbaas17:38
*** vivek-ebay has joined #openstack-lbaas17:42
*** ksamoray has quit IRC17:57
*** dlundquist has quit IRC18:02
mesterylbaas folks: https://review.openstack.org/#/c/130864/18:16
mesteryThat's the merge commit to bring master into feature/lbaasv218:16
mesteryOnce it passes Jenkins, I'll put it in the queue.18:16
mesteryAnd then we can land the second patch which failed jenkins yesterday.18:16
mesteryblogan: ^^^^18:16
*** markmcclain has joined #openstack-lbaas18:22
*** VijayB has joined #openstack-lbaas18:41
*** sbfox has joined #openstack-lbaas18:44
*** dlundquist has joined #openstack-lbaas18:45
*** woodster_ has joined #openstack-lbaas18:50
bloganmestery: thanks!18:57
mesteryblogan: Hopefully it passes the check queue soon and then I'll get it in the merge queue. Apologies it took longer than I thought, but I wanted to be careful I was doing it correct. :)18:58
bloganmestery: understandable, i appreciate you doing it and keeping us up to date19:00
bloganmestery: what are the chances this happens again though?19:00
mesteryblogan: I think I'm going to plan to pull master into feature/lbaasv2 at least every 2 weeks, it's not that hard and almost always will be without conflict I think.,19:01
mesteryThis will keep it fresh.19:01
mesteryI'll make sure to sync with you folks on this though.19:01
*** dlundquist has quit IRC19:01
*** VijayB has quit IRC19:04
*** vivek-ebay has quit IRC19:07
*** vivek-ebay has joined #openstack-lbaas19:07
*** ksamoray has joined #openstack-lbaas19:09
*** ksamoray has quit IRC19:12
*** vivek-ebay has quit IRC19:12
*** vivek-ebay has joined #openstack-lbaas19:12
*** dlundquist has joined #openstack-lbaas19:13
*** ksamoray has joined #openstack-lbaas19:15
*** dlundquist has quit IRC19:20
*** VijayB has joined #openstack-lbaas19:37
*** VijayB has quit IRC19:41
*** VijayB has joined #openstack-lbaas19:44
*** vivek-ebay has quit IRC19:54
*** ksamoray has quit IRC19:54
*** barclaac has quit IRC19:57
*** dlundquist has joined #openstack-lbaas20:06
*** vivek-ebay has joined #openstack-lbaas20:15
rm_workHey guys -- I was looking at what TrevorV is working on right now, and it's a specification for an *implementation* of an interface (for which there is already a spec)... I am a little bit concerned if this is going to become the norm20:22
rm_workCan we agree that we don't need to write a spec document for each *implementation* since it will by definition contain only implementation details?20:23
rm_worksbalukoff / sballe / xgerman20:24
rm_workOr at least that you can make a spec if you want to, but if it's literally just detailing "this is the function in some library i'm going to call to achieve what the interface specification already detailed" then it isn't really useful20:25
bloganmestery: i think there would be a conflict almost always with the migrations, but those are easy to fix20:26
mesteryack20:26
TrevorVmestery syn20:26
mesterylol20:26
rm_workI'm recommending he abandon the WIP spec: https://review.openstack.org/#/c/130640/20:26
rm_workmestery / TrevorV: you guys are doing it backwards. it hurts T_T20:26
*** sbfox has quit IRC20:27
TrevorVI like it20:28
rm_workis TrevorV a time-traveler? >_>20:28
rm_workor rather I guess mestery would be20:29
*** sbfox has joined #openstack-lbaas20:29
mesteryrofl20:29
xgermanI like specs20:31
rm_workxgerman: yeah but we're entering spec overload territory20:32
*** sbfox has quit IRC20:33
xgermanwell, I think the specs are pretty light -- at least you have figured out the functions before writing code. If you use a piece of paper you can as well write a quick spec20:33
xgermanbut I understand that some specs add little value beyoned focusing a person thoughts20:34
*** VijayB has quit IRC20:34
*** sbfox has joined #openstack-lbaas20:34
sballerm_work: I think we need specs. Othewise we are back to where we where in Atlanta where the documentation is "read the code"20:35
sballeand then we cannot discuss design20:35
blogansballe: i think he is arguing that some specs arent necessary for implementing interfaces that already ahve specs, so is it worth doing them?20:37
rm_worksballe: yeah we need specs, we just don't need to write specs for implementations for interfaces that have specs20:37
rm_workbecause at that point it is, literally by definition, purely implementation details20:37
TrevorVAnother thing to consider, sballe, we all agree that specs provide good documentation, but in this case the documentation is necessary for the interface, not so much for the implementation of it, since the documentation can be literally the same.20:39
bloganwell i can see how an implementation of an interface could require some extra details that would be spelld out in a spec20:41
blogansimilar to how neturon lbaas drivers require a spec even though they are implementing the driver interface20:41
rm_workwhich is why i said "feel free if you want to, but please don't say it's required"20:41
bloganmeh if it's not a lot of work then it won't be hard to do and won't take much time, if it is a lot of work then it is worth doing20:44
TrevorVI follow rm_work here.  In cases where an implementation may be ambiguous, it would make sense to have a spec for it for sorting out that ambiguity.  In the case of the aforementioned spec, I feel like its just a copy-paste of the interface spec is all.20:44
ptoohillhttp://i.imgur.com/LhYwbW6.jpg20:45
*** vivek-ebay has quit IRC20:45
*** vivek-ebay has joined #openstack-lbaas20:46
*** VijayB_ has joined #openstack-lbaas20:50
openstackgerritAdam Harwell proposed a change to stackforge/octavia: TLS Data Security Overview  https://review.openstack.org/13065920:52
rm_workAnyway, the only reason I bring that up is so that when TrevorV abandons his review (and when I don't do specs for implementations on my CertManager interface) people won't freak out20:56
bloganim going to freak out20:56
rm_workyou do that :P20:57
*** sbfox1 has joined #openstack-lbaas21:02
*** sbfox has quit IRC21:02
sbalukoffI'll take a closer look at that and register an opinion. In my experience though-- two people looking at the same trivial problem will often come up with different ways to solve it, one of which is usually better. Sometimes that could emerge if things are specced out beforehand and save people some trouble.21:05
*** sbfox has joined #openstack-lbaas21:05
*** sbfox1 has quit IRC21:05
sbalukoffI definitely agree that all interfaces need to be specced, otherwise people can't work in parallel on different components and expect them to actually work together.21:06
rm_worksbalukoff: yeah but at the level of detail that you'd realize that, you practically have the implementation coded21:06
sbalukoffrm_work: Depends on the case.21:06
rm_workwhich is why i keep saying "feel free if you think it's worth it"21:06
rm_workjust don't want to get people complaining if I don't make one :P21:07
sbalukoffI don't want a hard and fast rule here because I don't think it's appropriate. But just know that if you write an implementation that isn't specced, you may end up in a situation where you end up having to rewrite much of your code because "obvious assumptions" to you weren't necessarily obvious to other people.21:07
sbalukoffrm_work: Right. Flip side of that is: Don't complain if we come back and say "You did this totally wrong, please rewrite all of it." ;)21:08
sbalukoffAgain, I haven't had time to look closely at the spec you've linked. Will do so later and register an opinion on whether I think it should be abandoned.21:08
TrevorVsbalukoff its my first spec, and its REALLY rough, so please provide ANY suggestions you come up with21:10
TrevorVI'll work on it over the next week tinkering around21:10
*** ptoohill_ has quit IRC21:11
sbalukoffTrevorV: Actually, I think that both ptoohill and blogan have raised good questions here, on it. And looking at this spec, even though it's pretty simple-- I'd say it's worth it to have it.21:12
sbalukoff(ex. answering the question "How will these actually make calls to nova?" is a good thing to clarify here, eh.)21:13
rm_workuhh21:14
rm_work"using python-novaclient"21:14
sbalukoffrm_work: Good. Glad you aren't curling an API interface yourself. XD21:14
rm_workanything more detailed than that and you may as well just be writing the implementation21:14
sbalukoffI think blogan's point above is still valid: If it's a simple spec, it'll be quick to do, and is a good sanity check (for things you may not have thought about). If it's a more complicated spec, it's needed even more.21:15
rm_worksbalukoff: I'll make sure to write a nice one-liner spec for my CertManager implementation, just for you :P21:16
sbalukoffrm_work: Seriously, I'm not really understanding what the big deal is.21:16
rm_workit's a waste of time21:16
rm_workand it's not just a waste of writers time, it's a waste of the time of all of the people that have to go review and +2 it21:17
rm_workbut *again*, I just want to make sure people won't freak out when I *don't* write a spec for every single tiny implementation CR I do21:18
sbalukoffrm_work: I probably won't freak out. Just note again-- if it's not specced, we may ask you to rewrite significant portions of your code (and even go back and write a spec so we understand your intention is with the code).21:20
sbalukoffI'm all for following formalized process where it makes sense and abandoning it where it doesn't.21:21
sbalukoffAgain, I'm not interested in a hard-fast rule here... just understand what the trade-offs might be.21:21
*** vivek-ebay has quit IRC21:21
*** markmcclain has quit IRC21:22
*** dboik has quit IRC21:23
sbalukoffrm_work: Have I succeeded in frustrating the hell out of you with my ambiguous response? ;)21:24
*** sbfox has quit IRC21:24
rm_workmore like amused21:25
rm_workclassic sbalukoff21:25
sbalukoffSaid another way, my response is: "Don't waste your time doing stupid things, but understand that what I think is21:25
sbalukoff'stupid' and what you think is 'stupid' may not be the same thing."21:26
rm_workmeanwhile, review this more worthwhile spec instead: https://review.openstack.org/#/c/130659 :P21:31
rm_workoh whoops, i forgot to change the BP link *in* the spec21:32
*** sbfox has joined #openstack-lbaas21:32
*** sbfox has quit IRC21:36
*** VijayB_ has quit IRC21:41
*** sbfox has joined #openstack-lbaas21:42
*** VijayB has joined #openstack-lbaas21:45
bloganeveryone, i just sent an email to the neutron lbaas and octavia list, please look at it and respond21:48
*** jorgem has quit IRC21:59
rm_workoh, what: http://sphinx-doc.org/ext/graphviz.html22:03
rm_workare we actually using that extension?22:03
sbalukoffrm_work: Yes.22:11
rm_worki had assumed we were just randomly including dotfiles :P22:12
rm_workcool22:12
*** VijayB has quit IRC22:15
sbalukoffblogan: Responded! Let's hope others in this community are amenable to that idea, too.22:18
*** VijayB_ has joined #openstack-lbaas22:21
bloganthanks sbalukoff, and I hope so too22:23
*** VijayB_ has quit IRC22:31
*** VijayB_ has joined #openstack-lbaas22:33
*** davidlenwell has quit IRC22:43
*** VijayB_ has quit IRC22:44
*** davidlenwell has joined #openstack-lbaas22:44
*** VijayB_ has joined #openstack-lbaas22:52
*** sbfox has quit IRC22:58
*** davidlenwell is now known as david_lenwell23:03
*** david_lenwell is now known as davidlenwell23:03
*** mlavalle has quit IRC23:04
mesteryblogan: https://review.openstack.org/#/c/130864/ merged, rebase https://review.openstack.org/#/c/123468/ now if you have time yet tonight!23:07
mesteryblogan: Thanks!23:08
*** sbfox has joined #openstack-lbaas23:10
*** VijayB_ has quit IRC23:13
*** vivek-ebay has joined #openstack-lbaas23:19
*** sbfox has quit IRC23:19
*** VijayB has joined #openstack-lbaas23:21
openstackgerritAdam Harwell proposed a change to stackforge/octavia: TLS Data Security Overview  https://review.openstack.org/13065923:37
*** VijayB has quit IRC23:48

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