Monday, 2014-04-07

*** oomichi has joined #openstack-meeting-alt00:02
*** amytron has joined #openstack-meeting-alt00:05
*** ramashri has joined #openstack-meeting-alt00:21
*** eguz has quit IRC00:28
*** yamahata has joined #openstack-meeting-alt00:36
*** eghobo has joined #openstack-meeting-alt00:39
*** eghobo has quit IRC00:39
*** hockeynut has joined #openstack-meeting-alt00:42
*** hockeynut has quit IRC00:52
*** demorris has joined #openstack-meeting-alt00:57
*** ijw has joined #openstack-meeting-alt01:07
*** ijw has quit IRC01:07
*** ijw has joined #openstack-meeting-alt01:08
*** demorris has quit IRC01:17
*** matjazp has joined #openstack-meeting-alt01:21
*** matjazp has quit IRC01:23
*** mozawa has joined #openstack-meeting-alt01:30
*** nosnos has joined #openstack-meeting-alt01:30
*** zns has joined #openstack-meeting-alt01:33
*** michael-yu has joined #openstack-meeting-alt01:35
*** zns has quit IRC01:45
*** yamahata has quit IRC01:45
*** feryu5644 has joined #openstack-meeting-alt01:49
*** feryu5644 has left #openstack-meeting-alt01:51
*** ijw has quit IRC01:52
*** michael-yu has quit IRC02:00
*** michael-yu has joined #openstack-meeting-alt02:00
*** xuhanp has joined #openstack-meeting-alt02:06
*** michael-yu has quit IRC02:20
*** matjazp has joined #openstack-meeting-alt02:21
*** zz_gondoi is now known as gondoi02:22
*** matjazp has quit IRC02:26
*** michael-yu has joined #openstack-meeting-alt02:26
*** chandan_kumar has joined #openstack-meeting-alt02:29
*** chandan_kumar has quit IRC02:30
*** doug_shelley66 has quit IRC02:32
*** michael-yu has quit IRC02:41
*** esker has quit IRC02:42
*** gondoi is now known as zz_gondoi02:55
*** coolsvap has joined #openstack-meeting-alt02:56
*** michael-yu has joined #openstack-meeting-alt02:57
*** nosnos has quit IRC03:02
*** michael-yu has quit IRC03:08
*** eghobo has joined #openstack-meeting-alt03:15
*** nosnos has joined #openstack-meeting-alt03:20
*** matjazp has joined #openstack-meeting-alt03:21
*** xuhanp has quit IRC03:22
*** matjazp has quit IRC03:24
*** banix has joined #openstack-meeting-alt03:27
*** chandan_kumar has joined #openstack-meeting-alt03:30
*** yamahata has joined #openstack-meeting-alt03:30
*** chandan_kumar has quit IRC03:31
*** chandan_kumar has joined #openstack-meeting-alt03:31
*** chandan_kumar has quit IRC03:48
*** eghobo has quit IRC03:49
*** eghobo has joined #openstack-meeting-alt03:49
*** zhiyan_ is now known as zhiyan03:50
*** nosnos has quit IRC03:51
*** sfineberg has quit IRC04:02
*** sfineberg has joined #openstack-meeting-alt04:04
*** banix has quit IRC04:08
*** chandan_kumar has joined #openstack-meeting-alt04:08
*** akuznetsov has joined #openstack-meeting-alt04:10
*** matjazp has joined #openstack-meeting-alt04:21
*** matjazp has quit IRC04:25
*** michael-yu has joined #openstack-meeting-alt04:27
*** michael-yu has quit IRC04:28
*** michael-yu has joined #openstack-meeting-alt04:31
*** michael-yu has quit IRC04:32
*** eghobo has quit IRC04:38
*** eghobo has joined #openstack-meeting-alt04:39
*** zhiyan is now known as zhiyan_04:39
*** michael-yu has joined #openstack-meeting-alt04:48
*** eguz has joined #openstack-meeting-alt04:50
*** eghobo has quit IRC04:50
*** michael-yu has quit IRC04:51
*** michael-yu has joined #openstack-meeting-alt04:53
*** michael-yu has joined #openstack-meeting-alt05:02
*** chandan_kumar has quit IRC05:02
*** michael-yu has quit IRC05:06
*** _nadya_ has joined #openstack-meeting-alt05:11
*** saju_m has joined #openstack-meeting-alt05:13
*** yamamoto_ has joined #openstack-meeting-alt05:17
*** xuhanp has joined #openstack-meeting-alt05:21
*** matjazp has joined #openstack-meeting-alt05:21
*** Slower has quit IRC05:22
*** _nadya_ has quit IRC05:24
*** matjazp has quit IRC05:25
*** matjazp has joined #openstack-meeting-alt05:27
*** chandan_kumar has joined #openstack-meeting-alt05:27
*** jvrbanac has quit IRC05:28
*** vishy has quit IRC05:28
*** matjazp has quit IRC05:28
*** radix_ has joined #openstack-meeting-alt05:29
*** stevebaker has quit IRC05:29
*** codekobe has quit IRC05:29
*** wendar_ has joined #openstack-meeting-alt05:29
*** radix has quit IRC05:29
*** ryanpetrello has quit IRC05:29
*** lifeless has quit IRC05:30
*** wendar has quit IRC05:30
*** lifeless has joined #openstack-meeting-alt05:31
*** arunkant has quit IRC05:31
*** ryanpetrello has joined #openstack-meeting-alt05:32
*** codekobe has joined #openstack-meeting-alt05:32
*** jvrbanac has joined #openstack-meeting-alt05:32
*** arunkant has joined #openstack-meeting-alt05:33
*** stevebaker has joined #openstack-meeting-alt05:33
*** vishy has joined #openstack-meeting-alt05:34
*** michael-yu has joined #openstack-meeting-alt05:39
*** michael-yu has quit IRC05:40
*** doug_shelley66 has joined #openstack-meeting-alt05:54
*** marios has quit IRC05:56
*** marios has joined #openstack-meeting-alt05:56
*** VINOD has joined #openstack-meeting-alt06:01
*** VINOD has quit IRC06:03
*** jaypipes has joined #openstack-meeting-alt06:03
*** VINOD has joined #openstack-meeting-alt06:04
*** amytron has quit IRC06:04
*** michael-yu has joined #openstack-meeting-alt06:04
*** jtomasek has joined #openstack-meeting-alt06:05
*** marun_afk has quit IRC06:08
*** jprovazn has joined #openstack-meeting-alt06:09
*** michael-yu has quit IRC06:10
*** VINOD has quit IRC06:12
*** michael-yu has joined #openstack-meeting-alt06:23
*** michael-yu has quit IRC06:24
*** xuhanp has quit IRC06:30
*** michael-yu has joined #openstack-meeting-alt06:30
*** rwsu has joined #openstack-meeting-alt06:35
*** saju_m has quit IRC06:41
*** matjazp has joined #openstack-meeting-alt06:42
*** xuhanp has joined #openstack-meeting-alt06:43
*** oomichi has quit IRC06:52
*** saju_m has joined #openstack-meeting-alt06:55
*** michael-yu has quit IRC06:56
*** michael-yu has joined #openstack-meeting-alt07:01
*** luqas has joined #openstack-meeting-alt07:02
*** chandan_kumar has quit IRC07:02
*** xuhanp has quit IRC07:02
*** flaper87|afk is now known as flaper8707:04
*** chandan_kumar has joined #openstack-meeting-alt07:07
*** nwidell has joined #openstack-meeting-alt07:13
*** michael-yu has quit IRC07:14
*** michael-yu has joined #openstack-meeting-alt07:15
*** lsmola_ has joined #openstack-meeting-alt07:16
*** matrohon has joined #openstack-meeting-alt07:18
*** michael-yu has quit IRC07:19
*** eguz has quit IRC07:22
*** jgallard has joined #openstack-meeting-alt07:22
*** jcoufal has joined #openstack-meeting-alt07:25
*** derekh has joined #openstack-meeting-alt07:40
*** derekh has quit IRC07:46
*** julienvey has joined #openstack-meeting-alt07:59
*** nacim has joined #openstack-meeting-alt08:00
*** eloib_ has joined #openstack-meeting-alt08:10
*** safchain has joined #openstack-meeting-alt08:11
*** julienve_ has joined #openstack-meeting-alt08:12
*** matjazp has quit IRC08:16
*** dshulyak has joined #openstack-meeting-alt08:16
*** nosnos has joined #openstack-meeting-alt08:40
*** vk has joined #openstack-meeting-alt08:46
*** julienve_ has quit IRC08:54
*** dmakogon_ is now known as denis_makogon08:57
*** julienve_ has joined #openstack-meeting-alt09:05
*** julienve_ has quit IRC09:05
*** ogelbukh has quit IRC09:17
*** ogelbukh has joined #openstack-meeting-alt09:26
*** saju_m has quit IRC09:27
*** ogelbukh has quit IRC09:28
*** ogelbukh has joined #openstack-meeting-alt09:28
*** stannie has joined #openstack-meeting-alt09:32
*** julienve_ has joined #openstack-meeting-alt09:46
*** julienve_ has quit IRC09:46
*** julienve_ has joined #openstack-meeting-alt09:47
*** yamamoto_ has left #openstack-meeting-alt09:56
*** mozawa has quit IRC10:01
*** kislotnay has quit IRC10:03
*** julienve_ has quit IRC10:05
*** jgallard has quit IRC10:24
*** sreshetnyak has joined #openstack-meeting-alt10:27
*** coolsvap has quit IRC10:27
*** saju_m has joined #openstack-meeting-alt10:32
*** eanxgeek|log is now known as eanxgeek10:47
*** saju_m has quit IRC10:49
*** nwidell has quit IRC10:56
*** jjmb has joined #openstack-meeting-alt11:06
*** julienve_ has joined #openstack-meeting-alt11:22
*** julienve_ is now known as julienvey_11:23
*** mwagner_lap has quit IRC11:23
*** saju_m has joined #openstack-meeting-alt11:24
* IgorYozhikov is now away: went away...11:27
*** jjmb has quit IRC11:33
*** jjmb has joined #openstack-meeting-alt11:33
*** ycombinator has quit IRC11:42
*** annegentle has quit IRC11:43
*** zz_gondoi is now known as gondoi11:46
*** sreshetnyak has quit IRC11:50
*** jgallard has joined #openstack-meeting-alt11:52
*** sreshetnyak has joined #openstack-meeting-alt11:52
*** VINOD_ has joined #openstack-meeting-alt11:53
*** gondoi is now known as zz_gondoi11:56
*** markvoelker has joined #openstack-meeting-alt11:59
*** nosnos has quit IRC11:59
*** demorris has joined #openstack-meeting-alt12:06
*** ErikB1 has quit IRC12:06
*** ErikB1 has joined #openstack-meeting-alt12:07
*** mwagner_lap has joined #openstack-meeting-alt12:10
*** pdmars has joined #openstack-meeting-alt12:10
*** pdmars has quit IRC12:10
*** pdmars has joined #openstack-meeting-alt12:11
*** yamahata has quit IRC12:20
*** bogdando has quit IRC12:22
*** bogdando has joined #openstack-meeting-alt12:22
*** bcrochet has quit IRC12:24
*** bcrochet has joined #openstack-meeting-alt12:26
*** julienvey_ has quit IRC12:28
*** jecarey has quit IRC12:29
*** julienvey_ has joined #openstack-meeting-alt12:31
*** demorris has quit IRC12:35
*** sergmelikyan has joined #openstack-meeting-alt12:36
*** jdob has joined #openstack-meeting-alt12:37
*** andreaf has quit IRC12:45
*** noslzzp has joined #openstack-meeting-alt12:47
*** doug_shelley66 has quit IRC12:48
*** ityaptin has quit IRC13:01
*** ameade has joined #openstack-meeting-alt13:02
*** lblanchard has joined #openstack-meeting-alt13:02
*** dprince has joined #openstack-meeting-alt13:04
*** jecarey has joined #openstack-meeting-alt13:05
*** rustlebee is now known as russellb13:08
*** balajiiyer has joined #openstack-meeting-alt13:08
*** eankutse has joined #openstack-meeting-alt13:10
*** julienvey_ has quit IRC13:14
*** eankutse has quit IRC13:14
*** derekh has joined #openstack-meeting-alt13:15
*** julienvey_ has joined #openstack-meeting-alt13:21
*** lblanchard has quit IRC13:26
*** andreaf has joined #openstack-meeting-alt13:28
*** hockeynut has joined #openstack-meeting-alt13:29
*** kevinconway has joined #openstack-meeting-alt13:32
*** eankutse has joined #openstack-meeting-alt13:33
*** eankutse has joined #openstack-meeting-alt13:33
*** eankutse has quit IRC13:33
*** eankutse has joined #openstack-meeting-alt13:34
*** lblanchard has joined #openstack-meeting-alt13:35
*** thang_ has joined #openstack-meeting-alt13:38
*** zz_gondoi is now known as gondoi13:38
*** damnsmith is now known as dansmith13:39
*** Barker has joined #openstack-meeting-alt13:41
*** overlayer has joined #openstack-meeting-alt13:42
*** banix has joined #openstack-meeting-alt13:44
*** yamahata has joined #openstack-meeting-alt13:45
*** IlyaE has joined #openstack-meeting-alt13:47
*** eankutse1 has joined #openstack-meeting-alt13:47
*** eankutse has quit IRC13:49
*** demorris has joined #openstack-meeting-alt13:50
*** hockeynut has quit IRC13:51
*** hockeynut has joined #openstack-meeting-alt13:51
*** sballe has quit IRC13:55
*** chandan_kumar has quit IRC13:56
*** julienvey_ has quit IRC13:58
*** lascii has joined #openstack-meeting-alt13:58
*** rmoe_ has quit IRC13:59
*** AlanClark has joined #openstack-meeting-alt13:59
*** samstav has joined #openstack-meeting-alt14:00
*** VINOD_ has quit IRC14:01
*** mozawa has joined #openstack-meeting-alt14:03
*** alaski_ has quit IRC14:08
*** lascii is now known as alaski14:08
*** glucas has left #openstack-meeting-alt14:11
*** pdmars has quit IRC14:16
*** pdmars has joined #openstack-meeting-alt14:17
*** pdmars has quit IRC14:17
*** pdmars has joined #openstack-meeting-alt14:18
*** pdmars has quit IRC14:20
*** pdmars has joined #openstack-meeting-alt14:21
*** pdmars has quit IRC14:22
*** pdmars has joined #openstack-meeting-alt14:22
*** matjazp has joined #openstack-meeting-alt14:23
*** balajiiyer has quit IRC14:25
*** doug_shelley66 has joined #openstack-meeting-alt14:26
*** julienvey_ has joined #openstack-meeting-alt14:26
*** amytron has joined #openstack-meeting-alt14:32
*** mattgriffin has joined #openstack-meeting-alt14:32
*** bill_az has joined #openstack-meeting-alt14:32
*** julim has joined #openstack-meeting-alt14:34
*** zns has joined #openstack-meeting-alt14:34
*** akuznetsov has quit IRC14:43
*** IlyaE has quit IRC14:44
*** jmontemayor has joined #openstack-meeting-alt14:45
*** saju_m has quit IRC14:50
*** balajiiyer has joined #openstack-meeting-alt14:56
*** akuznetsov has joined #openstack-meeting-alt14:57
*** balajiiyer has quit IRC14:57
*** balajiiyer has joined #openstack-meeting-alt14:57
*** jasonpgignac has joined #openstack-meeting-alt14:57
*** hockeynut has quit IRC14:57
*** balajiiyer has left #openstack-meeting-alt14:58
*** gusmaskowitz has joined #openstack-meeting-alt14:59
zns#startmeeting satori15:00
openstackMeeting started Mon Apr  7 15:00:31 2014 UTC and is due to finish in 60 minutes.  The chair is zns. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: satori)"15:00
openstackThe meeting name has been set to 'satori'15:00
*** demorris has quit IRC15:00
*** mordred has joined #openstack-meeting-alt15:01
znsGood morning/afternoon! Who's here?15:01
samstavo/15:01
gondoio/15:01
gusmaskowitzo/15:01
gusmaskowitzhowdy folks15:01
jasonpgignaco/15:01
*** hockeynut has joined #openstack-meeting-alt15:01
znsCool. I think others are out today, so we have quorum.15:02
zns#topic action items15:02
*** openstack changes topic to "action items (Meeting topic: satori)"15:02
znsReviewing action items: #1 address possible duplication between 1295391 and 1293670 - DONE15:03
zns#action zns start ML discussion & blueprint for built-in python data plane discovery15:03
znsNot done.15:03
*** IgorYozhikov has quit IRC15:03
*** hhoover has joined #openstack-meeting-alt15:03
znsgondoi - we didn't "discuss netloc_info and ip_info" ... but did you "create blueprint"?15:03
*** ogelbukh has quit IRC15:03
gondoiyes15:04
znsCool. DONE. Thank you!15:04
*** yamahata has quit IRC15:04
zns#action caleb_ Developer docs for doing discovery using Python rather than the command line15:04
gondoihttps://blueprints.launchpad.net/satori/+spec/ip-and-netloc-info15:04
znsassuming not done.15:04
zns#link https://blueprints.launchpad.net/satori/+spec/ip-and-netloc-info15:04
hhoovero/ (sorry for lateness)15:04
*** yamahata has joined #openstack-meeting-alt15:04
znsHi hhoover15:04
znsmanage the agenda and the Thursday cut-off for topics - partially done.15:05
znsI updated the meeting docs, but I did not send out a note last week on the ready agenda items.Sorry about that. I'll put it in my book for this week.15:05
*** sbalukoff has quit IRC15:05
znsgusmaskowitz: create a spec and blueprint for Triple-O - status?15:05
gusmaskowitzDONE.15:05
znsNice.15:06
znsDo you have a link?15:06
gusmaskowitzI wont say it's a GREAT blueprint…. but it's there15:06
znsThat counts.15:06
gusmaskowitznow for the discussion.15:06
znsgusmaskowitz: link?15:06
gusmaskowitzhttps://wiki.openstack.org/wiki/Satori/Specialize-in-Tripple-O-Discovery15:06
zns#link https://wiki.openstack.org/wiki/Satori/Specialize-in-Tripple-O-Discovery15:07
znsThanks15:07
znsgondoi: adding blueprint/spec URLs next to these topic items and adding them to next weeks agenda?15:07
*** IlyaE has joined #openstack-meeting-alt15:07
gondoi?15:07
gusmaskowitzzns that was the wiki link sorry. This is the blueprint. https://blueprints.launchpad.net/satori/+spec/satori-specialize-in-tripple-o15:08
*** david-lyle has joined #openstack-meeting-alt15:08
zns#link  https://blueprints.launchpad.net/satori/+spec/satori-specialize-in-tripple-o15:08
znsgondoi: that was an action item (including me to help!) from last week.15:08
gondoioh yes15:08
gondoidone15:08
znsGreat.15:08
gondoithere is a blueprint, but i did not create the spec urls to the wiki15:09
gondoilinks in the meeting notes15:09
*** cjellick has joined #openstack-meeting-alt15:09
znsCool.15:09
gondoisorry i mean agenda15:09
znsDoes anyone want to discuss a specific blueprint or spec from https://wiki.openstack.org/wiki/Meetings/Satori ?15:10
znsGiven I didn't send an email out, I'm not going to assume the topics have been read by all...15:10
samstavhttps://blueprints.launchpad.net/satori/+spec/satori-minimal15:10
znsI did write this spec https://wiki.openstack.org/wiki/Satori/DiscoverySchema on Thursday, but did not send it out.15:11
znssamstav: I know you spent a lot of time on that one.15:11
samstavUnfortunately so. I have a couple things to mention15:12
zns# topic Discuss https://blueprints.launchpad.net/satori/+spec/satori-minimal15:12
znssamstav: go ahead...15:12
gondoi140 characters or less :P15:13
*** insequent has joined #openstack-meeting-alt15:13
samstavThis is a description of where I left off15:13
samstavhttps://gist.github.com/smlstvnh/986316915:13
znsmultimedia. Love it. samstav raising the bar.15:13
samstavI would bore you to tears going into the details, but most of them are there. Currently looking for alternatives to the initial implementation idea.15:14
samstavThe attempt also resulted in an bug + patch to pbr :15:14
samstavpatch: https://review.openstack.org/#/c/84218/15:14
samstavbug: https://bugs.launchpad.net/pbr/+bug/130038115:15
*** nacim has quit IRC15:15
samstavMr. Hellman seems skeptical, but I'm still waiting for a reply on the bug discussion15:15
znssamstav: what alternative are you leaning towards? Or what direction do you want to take this to?15:16
*** cjellick has quit IRC15:16
*** cjellick has joined #openstack-meeting-alt15:17
samstavThe idea is, you can create a package's environment so that it can be extended, but it's hard to do it the other way around, I found.15:17
*** betsy has joined #openstack-meeting-alt15:17
*** ogelbukh has joined #openstack-meeting-alt15:17
znsAnd that conflicts with that we want the default package to be the full one with all dependencies... right?15:17
samstavWe were trying to create a "base" package with full dependencies, and a "minimal", alternative package with *fewer dependencies.15:18
samstavzns exactly15:18
znsThe conflict arises when we use the same package for those two use cases. So are we going to need to have two packages?15:18
*** ramashri has quit IRC15:19
samstavWe either need two packages, or for the "base" package to be the minimal one15:19
*** eankutse1 has quit IRC15:19
*** mattgriffin has quit IRC15:19
*** eankutse has joined #openstack-meeting-alt15:19
*** mattgriffin has joined #openstack-meeting-alt15:19
znsI prefer the first option, since the minimal package is for a very precise use case that is not the most common one.15:19
znsi.e. two packages15:20
samstavOK, that is definitely the quickest solution as well15:20
*** gyee has joined #openstack-meeting-alt15:20
znsThe use case being, just for the record, for those who want to run satori for data plane discovery on a local machine. So they don't want to have to install nova client and paramiko with their complex dependencies...15:21
samstavHow will we handle the namespacing? e.g. if I have satori-minimal installed AND satori installed in the same environment?15:21
znsgood point. Not only the package names should be different, but potentially the app as well.15:22
znsUnless we have a special entry point and packge name: mini-satori15:22
samstavMy assumption is that you will get the same code installed, but import statements will be try;except [ed], and that they have the same namespace15:22
*** venkatesh has joined #openstack-meeting-alt15:23
samstavor is that ^^ chaos15:23
znsWhat happens if I have satori installed and then I run pip install satori-minimal?15:23
znsIt should be a noop if we're going to have both be supported...15:23
samstavright. Is that possible?15:23
znsAnd that feels jacky.15:23
*** jprovazn is now known as jprovazn_bbl15:23
znshacky!15:24
samstavhmmmmmm.15:24
znsConsider then running pip uninstall satori-minimal. Wouldn't that break satori?15:24
samstavWell, that depends on how pip handles these packages.15:24
znsUnless satori depends on satori-minimal and that's how the packages are builtt?15:25
samstavCan packages have a different name on pypi but the same application-package name?15:25
znsI believe it is possible. I don't know how clean that will be for folks installing/uninstalling packages.15:25
samstavsatori depends on satori-minimal… sure.15:25
samstavthat sounds right, right?15:26
gondoii like that15:26
gondoisatori-mini being a dep of satori15:26
znsIt sounds like it would work. I don't know about if it is the "right" solution. Too subjective of a term :-)15:26
znsMe too. Sounds like the better path.15:26
gondoiwhat about calling it satori-local15:27
samstavIt's not always obvious, unless you're dutch.15:27
znssamstav: do you want to explore that?15:27
samstavsatori-local is probably better if that is its primary use case15:27
zns+1 satori-local15:27
samstav+115:27
zns# agreed we'll handle the local use case by creating a satori-local package and having satori depend on it to minimize duplication of code and keeping packages clean.15:28
zns#agreed we'll handle the local use case by creating a satori-local package and having satori depend on it to minimize duplication of code and keeping packages clean.15:28
samstavSounds good. I'll explore it15:28
znsThanks.15:29
*** pdmars has quit IRC15:29
znsCan we discuss https://wiki.openstack.org/wiki/Satori/DiscoverySchema? Any objections?15:29
*** pdmars has joined #openstack-meeting-alt15:29
gondoisounds good to me15:29
zns#topic Schema https://wiki.openstack.org/wiki/Satori/DiscoverySchema15:29
*** openstack changes topic to "Schema https://wiki.openstack.org/wiki/Satori/DiscoverySchema (Meeting topic: satori)"15:29
*** ijw has joined #openstack-meeting-alt15:30
znsI have some specific questions to bring up, but fire away if you have some too...  first question:15:30
znsHow do you feel about the "errors" array? Is it intuitive? Any objections?15:30
gondoii like it.. do we care what order they happened in?15:31
*** demorris has joined #openstack-meeting-alt15:31
znsThe idea is that not all errors mean discovery should fail. We can have partially successful discoveries.15:31
jasonpgignacI imagine the user will, optionally, want some sort of Stack Trace.15:31
gondoior possibly additional contextual data around the error, like what was being executed15:32
*** pdmars has quit IRC15:32
*** ijw has quit IRC15:32
znsgondoi: I can't think of a use case. Especially since some operations might happen in parallel. Can you think of a use case?15:32
hhooverjasonpgignac: I would want to know the WHY around an error15:32
znsjasonpgignac: how about that gets added if --debug is turned on?15:32
*** pdmars has joined #openstack-meeting-alt15:32
*** ijw has joined #openstack-meeting-alt15:33
*** pdmars has quit IRC15:33
jasonpgignachhoover: I agree in concept. However, my experience of error handling is that many errors occur that we as the devs do not expect. These errors, we don't KNOW the why. So we cannot communicate it to the user.15:33
znsI don't think stack traces should be provided in output by default.15:33
samstavNow --debug is affecting not only how satori runs but the discovery results ?15:33
gondoizns: no i don't think so unless it's a timing issue... but I can't think of any off the top of my head15:33
*** pdmars has joined #openstack-meeting-alt15:33
samstavnot "Now", I mean "Then".   That might be odd. But a separate option might be overkill. Hmm.15:34
jasonpgignaczns: I imagine you will have a lot of people irritated at running a five minute discovery, having it error, not knowing what to do with the error because it provides limited information, and having to wait 5 minutes to run it again, with debug on.15:34
*** pdmars has quit IRC15:34
jasonpgignaczns: This is a technical tool, with a target market of people who not only can read a stacktrace, but would prefer to have the data vailable in the case of an error, I would think?15:35
*** pdmars has joined #openstack-meeting-alt15:35
hhoovermaybe the error messages just need to be very descriptive. "could not log in" != "server unreachable"15:35
znsEven technical tools don't output stack traces unless you have debugging turned on. Give me an example of one that does?15:35
*** pdmars has quit IRC15:35
jasonpgignachhoover: DEFINITELY more descriptive, and perhaps we can just make the carefully defined errors show iwth no stacktrace, but an unexpected one be more descriptive?15:36
znshhoover: +115:36
znsGood error messages/handling.15:36
*** pdmars has joined #openstack-meeting-alt15:36
jasonpgignacThis would require a lot of work from the devs to make sure they catch ONLY the VERY narrow situation they'e planned for. And write a lot of error handlers.15:36
*** mspreitz has joined #openstack-meeting-alt15:36
samstavCan we think for a second about *not* including error information directly inside the discovery results?15:37
samstavBut rather, *always* write a log somewhere, much like pip does?15:37
*** pdmars has quit IRC15:37
samstavUnless the error information is a valid piece of discovery results15:37
*** pdmars has joined #openstack-meeting-alt15:37
znssamstav: how would that work when satori is used as a library?15:37
gondoithat would be good, then you can dump whatever you want in the logs and not bother the user15:37
jasonpgignacsamstav: That's a great idea. Then write a little "There was errors in this discovery. For more info see foo/satori-broke-sorry.log15:37
hhooverIt could say something like, errors occurred, check satori.log for info15:37
hhooveror some such15:38
hhoover+1 jasonpgignac15:38
*** pdmars has quit IRC15:38
samstavhhoover yes that is exactly what I was thinking, esp. when I referenced pip15:38
gondoizns: thinking about the library use case15:38
samstavins good question15:38
samstavzns* ^15:38
jasonpgignacIf you use it as a library, then we shoudl raise errors.15:39
gondoimaybe we can only put the log file work in the shell.py related code?15:39
znsWe could return a tuple, with errors and other non-results in the other variable.15:39
jasonpgignacAnd let the developer wrapping it catch them if they wish.15:39
znsjasonpgignac: that defeats the use case of supporting partially successful discoveries.15:39
*** pdmars has joined #openstack-meeting-alt15:39
jasonpgignaczns: No, it just gives the user control over whether they would LIKE a partially successful discovery.15:39
jasonpgignacLibraries should fail loudly and give freedom of handling to the implementer.15:40
jasonpgignacIMHO15:40
znsSo what is returned if a discovery succeeds partially?15:40
*** pdmars has quit IRC15:40
znsgondoi: I like that. Then one response comes from the discovery code and shell.py strips out the errors?15:41
jasonpgignacThen, let the user receive the error, log it, handle it, or deal with as they wish, and decide what to do with the parts that worked.15:41
*** pdmars has joined #openstack-meeting-alt15:41
*** pdmars has quit IRC15:41
gondoiyes and logs to file the excess info for reference later15:41
znsjasonpgignac: How would you raise an error and return valid results at the same time?15:42
gondoi~/.satori/logs/satori.log (possibly)15:42
*** pdmars has joined #openstack-meeting-alt15:42
jasonpgignacHave an error that returns the partially completed results as a property of itself?15:42
*** pdmars has quit IRC15:42
znsjasonpgignac: -1. Does not feel pythonic to me...15:43
*** esker has joined #openstack-meeting-alt15:43
*** pdmars has joined #openstack-meeting-alt15:43
znsI don't think we should be returning valid results inside errors. Furthermore, how would that work when there are multiple errors? Feels like the wrong direction...15:44
jasonpgignaczns: A function that returns data to me on a partial failure feels highly idiosyncratic to me.15:44
znsI prefer gondoi's approach. Strip errors out in shell.py15:44
jasonpgignac'sfine. Just the way I see it. Failures shoudl look like failures. I should not have to check if something partially failed. That feels like tricking the end user.15:45
jasonpgignacThe user of the library, I mean.15:45
jasonpgignacI mean, that sounds like, maybe, an OPTION I could feed in?15:46
samstavSo, in shell.py,  we strip out errors from the discovery results, but if satori is being used as a library, we leave tracebacks/error messages inside the discovery return body?15:46
jasonpgignacLike, "satoriobjectthing.discover(ignore_errors=true)15:47
samstavNot sure if I followed all of that correctly.15:47
jasonpgignacBut the default, to me, would be false.15:47
jasonpgignacBut I can submit to the opinion of the majority, that's fine.15:47
znssamstav: yes.15:47
samstavThe code/fns used to strip out those errors should be exposed to the user of the library so that they can do the same.15:48
jasonpgignacI have another question, too, but can wait until we are done with this part15:48
znsjasonpgignac: I'm just concerned that if we raise an error on every failure, we're not going to have a useable library. Think about how we've been using this at Rackspace. We provide a lot of useful information even if we can't access one server in a topology.15:49
*** michael-yu has joined #openstack-meeting-alt15:49
jasonpgignaczns: I can  have a more thorough conversation on what I think woudl be the solution to that, but it might be bigger than this meeting.15:49
samstavI.e. it should be part of satori's python API. I am re-considering my opinion that errors/tbs shouldn't be part of the discovery results, because there really isn't a better place for them. Esp. from a python API perspective, I would like to have access to those tracebacks and error context right where the data would have otherwise been.15:50
*** matjazp_ has joined #openstack-meeting-alt15:51
znsjasonpgignac: I don't believe "Libraries should fail loudly and give freedom of handling to the implementer" translates to "Always raise an exception" and never return partial results. We're returning errors clearly. And in some cases, when we're doing a sequence of steps, we can return a grape of what succeeded and what did not.15:51
jasonpgignaczns: I see your point, I think that essentially the problem is that you are not running and returning the results of one mehtod - you are running a number of interrelated methdos with essentially independent result sets that are then integrated into a related set of data.15:52
jasonpgignacWhat you have are essentialyl a set of nested promises, some of which you may break.15:53
znssamstav: I agree. And if --debug is true, maybe the errors list returned would also have tracebacks. Then a library caller can parse those results.15:53
*** ramashri has joined #openstack-meeting-alt15:53
jasonpgignacAs a library user, I would like to be able to decide which of those promises I can live without being fulfilled, and which are entirely essential, in a simple, default way.15:53
*** hockeynut has quit IRC15:53
jasonpgignacSo, a set of nested promise handlers, more or less.15:53
*** hockeynut has joined #openstack-meeting-alt15:54
*** matjazp has quit IRC15:54
jasonpgignacIf I DON'T provie a handler, though, I don't think the right thing to is assume I dont' care if a given piece of data works.15:54
*** eghobo has joined #openstack-meeting-alt15:54
*** eankutse has quit IRC15:54
*** eankutse has joined #openstack-meeting-alt15:54
znsjasonpgignac: we've not built in the ability to specify what you want yet. Right now, satori decides that. At some point, that could be a feature.15:55
gondoiis this something we may want to finalize in #openstack-satori if we have anything else to quickly discuss?15:55
zns5 minutes left...15:55
*** rmoe has joined #openstack-meeting-alt15:56
znsHow about I take this feedback and come back with an updated proposal next week?15:56
jasonpgignaczns: Yes, as stated, I think this conversation is probably bigger than this meeting. I am willing to defer to the majority opinion, or to table until we have mroe time.15:56
gondoii would like to see a more final proposal... maybe we can mull over it and find a time to discuss before the next meeting?15:57
jasonpgignacagreed15:57
znsOK. I'll rev the proposal and send that out. We can then set up a time to discuss.15:58
gondoisounds good15:58
znsOK. Thank you for the good discussion. We're out of time for today.15:58
samstavcool15:59
gondoithanks zns15:59
zns#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Mon Apr  7 15:59:08 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/satori/2014/satori.2014-04-07-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/satori/2014/satori.2014-04-07-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/satori/2014/satori.2014-04-07-15.00.log.html15:59
*** hhoover has left #openstack-meeting-alt15:59
jasonpgignacthanks!15:59
*** jasonpgignac has quit IRC15:59
*** gusmaskowitz has quit IRC15:59
*** banix has quit IRC16:00
*** demorris has quit IRC16:04
*** jgallard has quit IRC16:05
*** ramashri_ has joined #openstack-meeting-alt16:06
*** ramashri has quit IRC16:06
*** matjazp has joined #openstack-meeting-alt16:06
*** jcoufal has quit IRC16:07
*** demorris has joined #openstack-meeting-alt16:07
*** bdpayne has joined #openstack-meeting-alt16:08
*** matjazp_ has quit IRC16:09
*** matjazp has quit IRC16:10
*** matjazp has joined #openstack-meeting-alt16:10
*** stanlagun has joined #openstack-meeting-alt16:11
*** jmontemayor_ has joined #openstack-meeting-alt16:11
*** jmontemayor has quit IRC16:11
*** jmontemayor_ has quit IRC16:12
*** saju_m has joined #openstack-meeting-alt16:12
*** jmontemayor has joined #openstack-meeting-alt16:12
*** chandan_kumar has joined #openstack-meeting-alt16:16
*** arunkant has quit IRC16:17
*** arunkant has joined #openstack-meeting-alt16:18
*** ijw has quit IRC16:19
*** Slower has joined #openstack-meeting-alt16:21
*** michael-yu has quit IRC16:22
*** ijw_ has joined #openstack-meeting-alt16:24
*** ijw_ has quit IRC16:24
*** ijw_ has joined #openstack-meeting-alt16:25
*** esheffield has quit IRC16:26
*** esheffield has joined #openstack-meeting-alt16:26
*** nikhil|afk is now known as nikhil16:28
*** mozawa_ has joined #openstack-meeting-alt16:29
*** mozawa has quit IRC16:30
*** mozawa_ is now known as mozawa16:30
*** markmcclain has joined #openstack-meeting-alt16:33
*** beekneemech is now known as bnemec16:34
*** eankutse has quit IRC16:34
*** esheffield has quit IRC16:34
*** eankutse has joined #openstack-meeting-alt16:34
*** saju_m has quit IRC16:35
*** venkatesh has quit IRC16:36
*** Leonr has joined #openstack-meeting-alt16:38
*** SlickNik has left #openstack-meeting-alt16:38
*** eankutse has quit IRC16:40
*** eankutse has joined #openstack-meeting-alt16:41
*** nikhil is now known as nikhil_16:41
*** nikhil_ is now known as Guest8106316:42
*** richm has joined #openstack-meeting-alt16:42
*** demorris has quit IRC16:43
*** luqas has quit IRC16:44
*** demorris has joined #openstack-meeting-alt16:44
*** Guest81063 is now known as nikhil__16:44
*** denis_makogon_ has joined #openstack-meeting-alt16:45
*** denis_makogon has quit IRC16:47
*** denis_makogon_ is now known as denis_makogon16:47
*** dmakogon_ has joined #openstack-meeting-alt16:47
*** julienvey_ has quit IRC16:53
*** michael-yu has joined #openstack-meeting-alt16:53
*** hockeynut has quit IRC16:54
*** hockeynut has joined #openstack-meeting-alt16:54
*** SumitNaiksatam has quit IRC16:55
*** hockeynut has quit IRC16:55
*** hockeynut has joined #openstack-meeting-alt16:56
*** harlowja has joined #openstack-meeting-alt16:56
*** hockeynut has quit IRC16:57
*** marun has joined #openstack-meeting-alt16:57
*** jmontemayor has quit IRC16:58
*** markmcclain has quit IRC16:59
*** markmcclain has joined #openstack-meeting-alt17:00
*** markmcclain has quit IRC17:00
*** zns has quit IRC17:02
*** colinmcnamara has joined #openstack-meeting-alt17:03
*** hockeynut has joined #openstack-meeting-alt17:03
colinmcnamarahey guys17:03
colinmcnamaraOpenStack Docs meeting - anyone here?17:04
matjazphi colinmcnamara17:04
colinmcnamarahey, give me a minute to get the meetbot commands17:04
colinmcnamara #startmeeting training-manuals17:05
colinmcnamara#startmeeting training-manuals17:05
openstackMeeting started Mon Apr  7 17:05:52 2014 UTC and is due to finish in 60 minutes.  The chair is colinmcnamara. Information about MeetBot at http://wiki.debian.org/MeetBot.17:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:05
*** openstack changes topic to " (Meeting topic: training-manuals)"17:05
openstackThe meeting name has been set to 'training_manuals'17:05
colinmcnamaraok people. OpenStack training-manuals roll call17:06
colinmcnamaracolinmcnamara present17:06
chandan_kumarhello17:06
colinmcnamarahello chandan_kumar:17:07
matjazpmatjazp here17:07
colinmcnamarahello matjazp:17:07
colinmcnamaraproposed Topics17:07
colinmcnamara1. Trello board task status17:07
colinmcnamara2. OpenStack Design Summit Prep17:07
colinmcnamara3. Developer guide status17:08
colinmcnamaraany other proposed topics?17:08
*** SumitNaiksatam has joined #openstack-meeting-alt17:08
colinmcnamaraok, moving forward with proposed topics17:09
matjazpnothing new for Moodle integration with Oauth2... can't get in touch with mordred17:09
colinmcnamaraok, I'm going to add that as a task in the trello board17:09
colinmcnamara(time to be a scrum nazi)17:09
matjazpcolinmcnamara: can you add me to participants in trello board?17:09
colinmcnamaraMatjazp: what is your id on trello?17:09
matjazpmatjazp17:10
colinmcnamaradone17:10
*** derekh has quit IRC17:10
colinmcnamaraso, you are having trouble getting into touch with mordred17:10
colinmcnamarahave you tried popping into the infra channel and asking for support?17:11
matjazpyup.. tried email and IRC..17:11
colinmcnamaraor are you running into release time crunch17:11
matjazpI could just ask anyonethere... I was specifically targeting mordred, because sarob told me he's aldready spoken with him about moodle and possibility of hosting it in opestack-infra17:12
colinmcnamaraok, and Sean is just getting back from holiday17:13
*** amcrn has joined #openstack-meeting-alt17:13
colinmcnamaraI'll follow up with him this week17:13
matjazpcool17:13
colinmcnamaraI think we are just hitting a wall on that one17:13
colinmcnamaraso I've moved that to impeded since forward process is waiting on mordred17:13
colinmcnamarais dguitarbyte: on?17:14
colinmcnamaraI see that there is a patch in day2 lab still in doing17:14
colinmcnamara#info need more info from Pranav17:16
colinmcnamaraSean is back in the saddle this week, and will be working on the how to contribute17:17
colinmcnamaraI am still working on the Dev Course merge, I may have to merge the outline later this week17:17
matjazpcolinmcnamara: Django based course is progressing?17:18
*** ijw_ has quit IRC17:18
colinmcnamarayes it is17:18
colinmcnamaraso I've been taking on a couple tasks17:18
colinmcnamarathe biggest one is for a canned CI workflow17:18
*** mspreitz has quit IRC17:19
colinmcnamaraI have my teams at Nexus refactoring the www.denicacloud.com code17:19
colinmcnamarato contribute the core CI stack as part17:19
colinmcnamarathe individual puppet modules are upstreamed17:19
colinmcnamarabut still refactoring for the "wrapper of wrappers"17:19
*** balajiiyer has joined #openstack-meeting-alt17:19
colinmcnamarathe gerrit and jenkins modules are already done - https://github.com/nexusis17:20
*** jdob_ has joined #openstack-meeting-alt17:20
colinmcnamarateams are still actively pulling our commercial code out of stuff17:20
colinmcnamaraso we can release the git configuration, and then the openstack deployer tool17:20
*** insequent has quit IRC17:21
*** demorris has quit IRC17:23
colinmcnamarastill going on the Django stuff17:24
colinmcnamaraalso, waiting for ashleymcnamara: to get done with school17:25
colinmcnamarashe's at Rackspace17:25
colinmcnamaraand I think I can talk her into some of this, she's good at Django17:25
matjazpDjango is mor or less a vehicle to learning OpenStack API, so probably just basic Django stuff is prefered17:26
colinmcnamaraexactly17:26
colinmcnamarait also gets people confortable with using django, with horizon is written in17:26
*** safchain has quit IRC17:27
colinmcnamarawhich has a bunch of code for interacting with OpenStack API's17:27
colinmcnamarathere is a method to the madness17:27
matjazpcool, can't wait to see the results...17:27
matjazptoo bad that we don't teach Django in our Web Programming course (Rails and other frameworks, but not Django)17:28
colinmcnamarayeah, can be extended17:28
colinmcnamarabut have to start somewhere17:28
colinmcnamarathat is all I have17:28
colinmcnamaraAny other business?17:28
matjazpwell..17:29
matjazpI was invited to speak at a OpenStack CEE day17:29
matjazpCEE=Central and Eastern Europe17:29
matjazpI was thinking of presenting OpenStack Training Manuals17:29
colinmcnamaraAwesome!17:29
colinmcnamaraNICE17:30
matjazpto get some traction around here17:30
colinmcnamaraso, reach out to stef17:30
colinmcnamaraso that it gets on the OpenStack blog17:30
matjazpSure, but I'll wait for conformation17:30
colinmcnamaracool17:30
matjazplast year it was a first event- I talked about SDN in general adn Neutron17:31
matjazpso this year I can pitch Training manuals to general public17:32
colinmcnamaraabsolutely17:32
*** balajiiyer has left #openstack-meeting-alt17:33
matjazpfirst two guides are finished (to the point of beeing usable)17:33
matjazpthe more feedback we receive, the better17:33
*** atiwari has joined #openstack-meeting-alt17:33
*** yogesh has joined #openstack-meeting-alt17:33
colinmcnamaraI agree17:34
matjazpYou and Sean are presenting Training manuals at Dev Summit?17:34
colinmcnamaraYeah17:35
colinmcnamaraeveryone is welcome17:35
matjazpok, could reuse some of your material17:35
colinmcnamaraabsolutely, let's sync up and I'll share17:36
matjazpok, cool17:37
matjazpthat's it from me17:37
colinmcnamaraAny other biz?17:37
matjazpnope17:37
colinmcnamaraok then, thanks for all the effort everyone17:38
colinmcnamara#endmeeting17:38
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:38
openstackMeeting ended Mon Apr  7 17:38:23 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/training_manuals/2014/training_manuals.2014-04-07-17.05.html17:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/training_manuals/2014/training_manuals.2014-04-07-17.05.txt17:38
openstackLog:            http://eavesdrop.openstack.org/meetings/training_manuals/2014/training_manuals.2014-04-07-17.05.log.html17:38
*** matjazp has quit IRC17:39
*** jdob_ has quit IRC17:40
*** julienvey_ has joined #openstack-meeting-alt17:41
*** colinmcnamara has quit IRC17:43
*** colinmcnamara has joined #openstack-meeting-alt17:44
*** arnaud has joined #openstack-meeting-alt17:48
*** colinmcnamara has quit IRC17:50
*** Barker has quit IRC17:54
*** Barker has joined #openstack-meeting-alt17:56
*** sbalukoff has joined #openstack-meeting-alt17:57
*** annegentle_ has joined #openstack-meeting-alt17:57
*** Barker has quit IRC17:59
*** Sukhdev has joined #openstack-meeting-alt18:00
*** saurabhs has joined #openstack-meeting-alt18:01
*** eankutse has quit IRC18:05
*** eankutse has joined #openstack-meeting-alt18:06
*** matjazp has joined #openstack-meeting-alt18:09
*** overlayer has quit IRC18:09
*** mwagner_lap has quit IRC18:10
*** eankutse has quit IRC18:11
*** eankutse has joined #openstack-meeting-alt18:11
*** _nadya_ has joined #openstack-meeting-alt18:11
*** demorris has joined #openstack-meeting-alt18:12
*** ijw has joined #openstack-meeting-alt18:14
*** colinmcnamara has joined #openstack-meeting-alt18:14
*** kgriffs|afk is now known as kgriffs18:15
*** kgriffs is now known as kgriffs|afk18:15
*** jcru has joined #openstack-meeting-alt18:15
*** jcru has left #openstack-meeting-alt18:16
*** zns has joined #openstack-meeting-alt18:16
*** _nadya_ has quit IRC18:19
*** colinmcnamara has quit IRC18:20
*** khyati_ has joined #openstack-meeting-alt18:20
*** kgriffs|afk is now known as kgriffs18:21
*** jdob has quit IRC18:22
*** chadlung has joined #openstack-meeting-alt18:23
*** chadlung has left #openstack-meeting-alt18:23
*** mspreitz has joined #openstack-meeting-alt18:32
*** _nadya_ has joined #openstack-meeting-alt18:33
*** colinmcnamara has joined #openstack-meeting-alt18:35
*** jmontemayor has joined #openstack-meeting-alt18:35
*** markmcclain has joined #openstack-meeting-alt18:39
*** andreaf has quit IRC18:40
*** gondoi is now known as zz_gondoi18:50
*** saju_m has joined #openstack-meeting-alt18:51
*** mspreitz has quit IRC18:52
*** zz_gondoi is now known as gondoi18:54
*** eanxgeek is now known as eanxgeek|log18:58
*** mwagner_lap has joined #openstack-meeting-alt19:00
*** stanlagun has left #openstack-meeting-alt19:01
*** mattgriffin has quit IRC19:02
*** balajiiyer has joined #openstack-meeting-alt19:07
*** dprince has quit IRC19:08
*** matjazp has quit IRC19:08
*** kevinconway has quit IRC19:08
*** eguz has joined #openstack-meeting-alt19:09
*** matjazp_ has joined #openstack-meeting-alt19:10
*** eghobo has quit IRC19:12
*** eghobo has joined #openstack-meeting-alt19:13
*** julienvey_ has quit IRC19:13
*** nati_ueno has joined #openstack-meeting-alt19:14
*** Leonr has quit IRC19:14
*** eguz has quit IRC19:15
*** mattgriffin has joined #openstack-meeting-alt19:19
*** matjazp_ has quit IRC19:23
*** balajiiyer has left #openstack-meeting-alt19:23
*** matjazp has joined #openstack-meeting-alt19:23
*** _nadya_ has quit IRC19:23
*** zns has quit IRC19:25
*** julienvey_ has joined #openstack-meeting-alt19:26
*** markmcclain has quit IRC19:26
*** colinmcnamara has quit IRC19:26
*** kevinconway has joined #openstack-meeting-alt19:27
*** colinmcnamara has joined #openstack-meeting-alt19:29
*** matjazp has quit IRC19:36
*** banix has joined #openstack-meeting-alt19:39
*** irenab has joined #openstack-meeting-alt19:41
*** irenab has quit IRC19:41
*** irenab has joined #openstack-meeting-alt19:41
*** ramashri_ has quit IRC19:43
*** akuznetsov has quit IRC19:44
*** _nadya_ has joined #openstack-meeting-alt19:48
*** matjazp has joined #openstack-meeting-alt19:50
*** eanxgeek|log is now known as eanxgeek19:50
*** gondoi is now known as zz_gondoi19:51
*** zz_gondoi is now known as gondoi19:53
*** michael-yu has quit IRC19:54
*** akuznetsov has joined #openstack-meeting-alt19:54
*** tedchang has joined #openstack-meeting-alt19:57
*** _nadya_ has quit IRC19:57
*** SumitNaiksatam has quit IRC19:59
*** alee_ has joined #openstack-meeting-alt19:59
*** redrobot has joined #openstack-meeting-alt20:00
*** reaperhulk has joined #openstack-meeting-alt20:00
*** Sukhdev has quit IRC20:00
redrobotIt's 20:00 UTC, which means, it's Barbican time! :D20:00
reaperhulk\o/20:01
redrobotwho all is here for the Barbican weekly meeting?20:01
alee_yo20:01
atiwari\0/20:01
arunkant0/20:01
codekobeo/20:01
redrobotok, lots of peeps here.  let's get this started20:02
redrobot#startmeeting barbican20:02
openstackMeeting started Mon Apr  7 20:02:15 2014 UTC and is due to finish in 60 minutes.  The chair is redrobot. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: barbican)"20:02
openstackThe meeting name has been set to 'barbican'20:02
*** woodster1 has joined #openstack-meeting-alt20:02
*** lisaclark has joined #openstack-meeting-alt20:02
redrobotas usual the agenda can be found here:20:03
redrobot#link https://wiki.openstack.org/wiki/Meetings/Barbican20:03
redrobotis malini here?20:03
*** harlowja has quit IRC20:03
*** funzo has quit IRC20:03
redrobotlooks like malini is out this week.  We'll follow up on the OpenStack Security guide next week.20:04
*** funzo has joined #openstack-meeting-alt20:04
hockeynuto/20:04
lisaclarko/20:04
woodster1o/20:04
jraimo/20:05
redrobotok, so first up, let's talk about plugin changes20:05
redrobot#topic Crypto Plugin changes20:05
*** openstack changes topic to "Crypto Plugin changes (Meeting topic: barbican)"20:05
atiwarisure20:05
alee_yup20:05
*** ZangMing1ie has joined #openstack-meeting-alt20:06
*** hemanth__ has joined #openstack-meeting-alt20:06
*** rosmaita_ has joined #openstack-meeting-alt20:06
* redrobot is hunting for urls20:06
*** tedchang has quit IRC20:06
atiwariwe had some discussion last week regarding interface contracts and method signature20:06
atiwari#link https://review.openstack.org/#/c/82189/6/barbican/crypto/plugin.py20:06
redrobot#link alee_ 's changes https://review.openstack.org/#/c/84329/20:06
*** rellerreller has joined #openstack-meeting-alt20:06
alee_it looks like there are two changes out there right now for the plugin -- one to support drm and one to support asymmetric keys20:07
atiwariyes, mine is at #link https://review.openstack.org/#/c/82189/620:08
redrobotright, I think so far we're wanting to land the DRM change, and then discuss the asymmetric approach20:08
*** funzo has quit IRC20:08
alee_so has anyone had a chance to review the DRM changes?20:08
*** megan_wl has joined #openstack-meeting-alt20:09
*** parstac_pete_ has joined #openstack-meeting-alt20:09
redrobotI apologize, but I've had this one on the backburner myself.20:09
*** fouxm has joined #openstack-meeting-alt20:09
*** russellb_ has joined #openstack-meeting-alt20:09
*** megan_wl is now known as megan_w20:09
atiwariI did it last week and mentioned that we are making changes in same land20:09
redrobotone question that was outstanding for you, alee_  is why the DRM plugin needs the UUID for the secret?20:09
alee_I know reaperhulk has looked at it -- any comments/ changes needed?20:10
*** vishy has quit IRC20:10
*** boris-42 has quit IRC20:10
*** russellb has quit IRC20:10
*** fouxm_ has quit IRC20:10
*** megan_w|afk has quit IRC20:10
*** haleyb has quit IRC20:10
*** peterstac has quit IRC20:10
*** rosmaita has quit IRC20:10
*** ZangMingJie has quit IRC20:10
*** hemanth_ has quit IRC20:10
*** edhall has quit IRC20:10
*** russellb_ is now known as russellb20:10
*** parstac_pete_ is now known as peterstac20:10
alee_redrobot, the drm needs an id to label the secret20:10
*** Barker has joined #openstack-meeting-alt20:10
*** Barker has quit IRC20:10
alee_redrobot, we decided that that id would be the  uuid20:10
redrobotalee_ there were some concerns here about the extra load this will add to the DB20:11
redrobotreaperhulk, woodster1 do you guys want to weigh in on it?20:11
woodster1alee: could the DRM plugin generate a unique identifier for the secret on its own?20:11
alee_the drm does in fact generate its own id - which would be unique for the drm - and so we could just pass in some random string20:12
*** vishy has joined #openstack-meeting-alt20:12
alee_basically then you would not really be using the client key id20:12
woodster1alee: I was a little concerned about having barbican details leaking into the plugin contract20:12
*** SumitNaiksatam has joined #openstack-meeting-alt20:12
alee_woodster1, the idea is that the client (which in this case is barbican) provides some label for the secret stored20:13
*** SumitNaiksatam has quit IRC20:13
alee_it doesn't have to be the uuid for the secret - but that seems to make sense.20:13
reaperhulkwell, uuids aren't particularly specific details, but we don't get a uuid until we save the object so we don't actually have that available to pass to the plugin without significant changes (and those changes would increase the DB load quite a bit)20:13
*** SumitNaiksatam has joined #openstack-meeting-alt20:13
woodster1alee: I was hoping that the DRM could create a unique id/handle that would be stored in barbican, and then passed back to barbican when a decrypt is needed.20:14
alee_woodster1, it does in fact do that -- and that is in fact stored for the decruypt20:14
redrobotiirc, this would be a use case for the kek_meta binding with the plugin?20:14
alee_woodster1,  I can create a random string in the plugin to use for the client key id - in which case the secret need not be created until afterwards20:15
woodster1I believe kek_metadata is scoped at the tenant level now rather than per-secret20:15
woodster1alee: I think that might be cleaner overall…then the plugin is more self sufficient and isolated from barbican proper20:16
redrobotwoodster1, i see...20:16
alee_I'm not sure I understand why this is significantly more load on the db .. the change is just to add the secret earlier in the function20:16
*** Barker has joined #openstack-meeting-alt20:16
jraimalee_: I think one concern is what happens when the plugin's generation fails?20:16
jraimnow we have to remove the secret20:17
jraimit would be nice to ensure the plugin behaves before barbican stores the data20:17
woodster1the first call would create the record and cut the ID/UUID, a second call would then be needed to update the record after generation…so two transactions instead of one20:17
*** haleyb has joined #openstack-meeting-alt20:17
*** edhall has joined #openstack-meeting-alt20:17
alee_woodster1, ok - I can generate a random string in the plugin for the client key id then.20:18
*** markmcclain has joined #openstack-meeting-alt20:18
alee_and then we need not create the secret until later20:19
redrobot#agreed alee_ will update DRM plugin changes to generate a UUID instead of saving the secret before calling the plugin20:19
*** harlowja has joined #openstack-meeting-alt20:19
redrobotcool, any other points on alee_ 's CR that we want to talk about?20:20
alee_so then do we still want to pass the required generation parameters in some dto object?20:20
*** jmontemayor has quit IRC20:20
alee_or leave them as they are as separate parameters?20:21
woodster1do you think more parameters are needed?20:21
*** funzo has joined #openstack-meeting-alt20:21
alee_for generation currently no.20:22
atiwariI think dto wd be better20:22
woodster1if we need several passed in, then a dto could make sense20:22
atiwarifor future extension20:22
alee_I agree with atiwari for future extension20:22
alee_of course atiwari - I created the dto from the secret that was created.20:22
alee_which is no longer being created ..20:23
alee_(yet)20:23
*** sarob has joined #openstack-meeting-alt20:23
atiwariok20:23
woodster1we should know all the generation params prior to the generate call, so a new generate_dto might be ok, similar to that secret_dto?20:24
alee_woodster1, I'm thinking also of the decrypt() case.  At some point we are going to want to pass in parameters like a wrapping key tyhat is generated on the client20:24
alee_exactly20:24
alee_I think we probably need a generate_dto and decrypt_dto20:25
woodster1dto's cleanly separate concerns and clean up params, so that sounds fine to me20:25
*** michael-yu has joined #openstack-meeting-alt20:25
atiwarihow about use of kwargs ?20:25
redrobotatiwari kwargs instead of a DTO?20:27
*** irenab has quit IRC20:27
atiwariyes, just throwing another option20:27
atiwaribut I am also ok with DTO20:27
redrobotatiwari I think it would give the plugin a bit more work20:27
alee_atiwari, I think a dto makes things more defined.20:27
atiwaricorrect20:28
*** amcrn has quit IRC20:28
alee_just offhand - I'd vote for dto.20:28
atiwarime too with DTO20:28
woodster1sounds good…I'd say give that a try then20:28
*** boris-42 has joined #openstack-meeting-alt20:28
redrobot#agreed we should use DTOs for create, generate, and decrypt20:29
*** malini has joined #openstack-meeting-alt20:29
redrobot#info DTO = Data Transfer Object20:29
alee_ok - any other concerns about my cr?20:29
atiwarican we move to next topic?20:30
alee_I'll make the changes and resubmit tomorrow.20:30
redrobotsounds good20:30
redrobotlet's move on to atiwari's plugin changes20:30
atiwariok20:31
*** ramashri has joined #openstack-meeting-alt20:31
atiwariwondering have you guys take a look?20:31
redrobotI think the first thing we should talk about is whether we want separate methods for symmetric/asymmetric calls?20:31
atiwari#link https://review.openstack.org/#/c/82189/620:31
redrobotI think reaperhulk has a feedback on this one20:32
atiwariin my opinion yes, because return type is different20:32
*** markmcclain has quit IRC20:32
*** markmcclain has joined #openstack-meeting-alt20:32
*** michael-yu has quit IRC20:32
*** ramashri_ has joined #openstack-meeting-alt20:32
atiwarior ve can device a new generic DTO for return20:32
malini+1 different methods20:33
atiwariredrobot, reaperhulk's comment I tried to fix20:33
atiwariand waiting for more review on this20:33
alee_I'd argue for separate methods because they are very different functionalities20:33
rellerreller+1 different methods20:33
*** michael-yu has joined #openstack-meeting-alt20:33
*** amcrn has joined #openstack-meeting-alt20:33
alee_for instance, right now drm doesn't expose generating an asymmetric key20:33
atiwarialee_ are with different methods?20:34
alee_(it will later .. but it doesn't now)20:34
redrobotI think that we could also argue that the plugin manager would orchestrate generating the different asymmetric parts, before packing it into a Container20:34
*** hyakuhei has joined #openstack-meeting-alt20:34
*** andreaf has joined #openstack-meeting-alt20:34
reaperhulkredrobot, that's an interesting idea20:34
reaperhulkThat part of the logic is probably identical across all plugins, so it might make sense to hoist it up20:35
*** rand738 has quit IRC20:35
alee_redrobot, not sure I understand what you're suggesting?20:35
*** ramashri has quit IRC20:35
atiwariredrobot, I think for separation of concern we should use separate method with different return s20:35
atiwariand bind in container in upper layer20:35
woodster1I'd definitely agree that the plugin should not be creating Containers, but rather the components of it to be put into a Container by the plugin manager later20:36
*** rand738 has joined #openstack-meeting-alt20:36
redrobotalee_ currently, the plugin manager just calls generate with whatever params for symmetric.  the idea would be that the plugin manager would call generate a few times with different params to generate the public key, private key, and possibly a passphrase.20:36
atiwariwoodster1 +120:36
atiwarithat is my plan20:36
woodster1I think some of the concern here is that orders, SSL cert generation/management, containers, and asymmetric key gen have overlapping design concerns20:37
atiwariI think containers are just a envelop20:38
woodster1the crypto plugin level is someone low level in nature right now. The order/container/ssl-cert flows seem higher level orchestration concepts. That's why a design session to discuss this would be very good to do.20:38
*** demorris has quit IRC20:39
redrobotagreed, I think this is going to require a design session during the Summit20:39
atiwariwoodster1, as per our discussion at #link https://blueprints.launchpad.net/barbican/+spec/api-orders-add-more-types20:39
reaperhulksorry guys, gotta run for a bit. redrobot & woodster1 know more about the general design here than I do though so you're in good hands20:40
atiwariwe thought that will be begin with symmetric and asymmetric20:40
*** radix_ is now known as radix20:40
alee_redrobot, I'm a little confused - can you generate a public key separate from the private key?20:40
atiwarialee_ no I think20:41
redrobotalee_ you could generate the private key from the secret key20:41
atiwarithat is why it has to be atomic20:41
*** saju_m has quit IRC20:41
malinino, private&public born at the same time20:41
atiwarimalini +120:41
alee_then I'm a little confused about the idea of calling generate to create the private key, then calling generate to generate the public key, then putting it all together ..20:42
atiwarime too, it has to be atomic calls20:42
rellerrellerI'm confused by that as well20:42
*** rand738 has quit IRC20:42
*** jprovazn_bbl has quit IRC20:43
redrobotthe public key can be derived from the private key.  doing it all at once is probably more efficient, but I do like the idea of generate() only returning single encrypted datums20:43
*** dprince has joined #openstack-meeting-alt20:43
malinialee_, perhaps redrobot mis-wrote there, after private-public born, then certify the public aspect, perhaps attach a passphrase to the private to further protect it20:43
*** rand738 has joined #openstack-meeting-alt20:44
redrobotit's a bummer reaperhulk left already, since he's our in-house crypto expert20:44
malini:-D20:44
atiwariredrobot I think he is ok with separate atomic methods20:44
atiwarias per lat week chat20:44
rellerrellerAre there any other specs or libraries that generate public/private key pairs in two operations?20:44
redrobotrellerreller none that I'm aware of... I'm just brainstorming over here :)20:45
rellerrellerIt might be better for developers to have one method for assymetric bc that's what they're used to20:45
redrobotthis would be just for the plugin_manager to plugin interaction20:45
redrobotrellerreller yeah, that's definitely a good argument.20:46
atiwarirellerreller +120:46
alee_redrobot, I think you're trying to shoe horn what is essentially a single operation generating a public/private key PAIR -- into a single datum20:46
*** matjazp has quit IRC20:46
alee_it makes more sense to me for the plugin to simply return a tuple of the public, private keys20:46
alee_and that probably means separate methods20:46
atiwari+1 that will be simple too20:46
rellerreller+120:47
malinimalini +120:47
alee_generateSymmetiric(), generateAsymmetric()20:47
atiwariI am ok with names20:47
woodster1it seems a separate asymmetric method does make sense, returning a tuple perhaps that is then stored as a Container by the extention manager20:47
alee_and the top layer can combine as needed20:47
atiwariyep20:48
redrobotI'm ok with that.20:48
atiwariagreed :)20:48
atiwari?20:48
malinialee_ +120:48
*** matjazp has joined #openstack-meeting-alt20:48
malinianother advantage is with generateSymmetric() there is no aysnchronous stuff, the call response would be key, and key-id, and can be used promptly20:49
redrobot#agreed Asymmetric Keys should be generated in a new method generate_symmetric()20:49
atiwariOK, then I will redo these method20:50
maliniredrobot -- typo there20:50
atiwariquestion, should I redo with DTO too?20:50
atiwariI think yes?20:50
alee_I think yes20:50
redrobotatiwari keep an eye on alee_ 's changes.  I think we'll want to reuse the DTOs from his CR20:50
atiwariok20:51
alee_atiwari, I should have my revised changes in by tommorow.20:51
atiwarisure20:51
redrobotok, guys we're running out of time here, I don't think we have time to cover any more agenda points20:51
redrobotany last thoughts on Crypto Plugin changes before we call the meeting?20:51
atiwariI am OK20:52
alee_has anyone had a chance to look at my follow on cr?20:52
alee_https://review.openstack.org/#/c/85137/20:52
redrobotmalini do'h >_<20:52
atiwarinot me, I will do20:52
alee_I'm guessing not because it depends on the previous one.20:52
alee_but I'd like to discuss that one once the first one goes in20:53
redrobotI haven't had a chance20:53
* redrobot is way behind on reviews20:53
woodster1quick read of it looks good to me (after the dto changes in the dep CR of course)20:53
alee_woodster1, cool20:54
woodster1not sure about the jenkins fails20:54
alee_lets put it on the agenda for next week then20:54
alee_woodster1, yeah I'll fix those20:54
woodster1I'm curious if tox locally fails too20:54
woodster1oh yeah, unused imports, easy to fix20:55
alee_woodster1, testing though will involve actually creating a drm20:55
woodster1the dev stack fail is probably more tricky to diagnose, so we might need to assist with that one20:55
redrobotdevstack gate was broken for everyone last week, so we may just need to re-kick that CR20:56
alee_yup I'll rekick when I fix the unused imports20:56
alee_(and change the dtos etc)20:56
*** amotoki has joined #openstack-meeting-alt20:57
redrobotok guys, we're out of time for this week.  We'll revisit the other agenda items next week.  In the meantime, try to get some reviews in when you can.20:57
redrobotthanks everyone!20:57
atiwariredrobot, there are more items in agenda can we talk in barbican room20:57
atiwari?20:58
woodster1wow that went by fast20:58
redrobotatiwari yeah, jump over to #openstack-barbican20:58
atiwariok20:58
redrobot#endmeeting20:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:58
openstackMeeting ended Mon Apr  7 20:58:28 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican/2014/barbican.2014-04-07-20.02.html20:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2014/barbican.2014-04-07-20.02.txt20:58
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2014/barbican.2014-04-07-20.02.log.html20:58
*** Sukhdev has joined #openstack-meeting-alt20:59
*** arnaud has quit IRC20:59
*** matjazp has quit IRC21:02
*** irenab has joined #openstack-meeting-alt21:02
*** doug_shelley66 has quit IRC21:03
*** denis_makogon has quit IRC21:05
*** lblanchard has quit IRC21:06
*** dprince has quit IRC21:09
*** GheRivero_ has joined #openstack-meeting-alt21:10
*** scottda has quit IRC21:10
*** matjazp has joined #openstack-meeting-alt21:10
*** colinmcnamara has quit IRC21:16
*** jcoufal has joined #openstack-meeting-alt21:17
*** akuznetsov has quit IRC21:18
*** scottda has joined #openstack-meeting-alt21:18
*** thang_ has quit IRC21:23
*** julienvey_ has quit IRC21:23
*** caleb_ has joined #openstack-meeting-alt21:26
*** atiwari has quit IRC21:26
*** colinmcnamara has joined #openstack-meeting-alt21:27
*** ameade has quit IRC21:30
*** doug_shelley66 has joined #openstack-meeting-alt21:30
*** harlowja is now known as harlowja_away21:31
*** eanxgeek is now known as eanxgeek|log21:34
*** harlowja_away is now known as harlowja21:35
*** yogesh has quit IRC21:37
*** mozawa has quit IRC21:38
*** atiwari has joined #openstack-meeting-alt21:43
*** betsy has quit IRC21:45
*** Barker has quit IRC21:48
*** esker has quit IRC21:48
*** rellerreller has quit IRC21:48
*** GheRivero has quit IRC21:55
*** GheRivero_ is now known as GheRivero21:55
*** matjazp has quit IRC21:57
*** pdmars has quit IRC22:01
*** eankutse has quit IRC22:01
*** markmcclain has quit IRC22:02
*** irenab has quit IRC22:03
*** michael-yu has quit IRC22:04
*** lenrow has joined #openstack-meeting-alt22:05
*** markmcclain has joined #openstack-meeting-alt22:06
*** ramashri_ has quit IRC22:06
*** rmoe has quit IRC22:06
*** ramashri has joined #openstack-meeting-alt22:06
*** gondoi is now known as zz_gondoi22:07
*** amcrn has quit IRC22:08
*** colinmcnamara has quit IRC22:08
*** amcrn has joined #openstack-meeting-alt22:12
*** colinmcnamara has joined #openstack-meeting-alt22:12
*** ramashri has quit IRC22:14
*** ramashri_ has joined #openstack-meeting-alt22:14
*** jecarey_ has joined #openstack-meeting-alt22:19
*** jecarey has quit IRC22:19
*** jecarey_ has quit IRC22:25
*** jaypipes has quit IRC22:27
*** amytron has quit IRC22:31
*** banix has quit IRC22:33
*** arnaud has joined #openstack-meeting-alt22:34
*** zhiyan_ has quit IRC22:34
*** demorris has joined #openstack-meeting-alt22:35
*** zhiyan_ has joined #openstack-meeting-alt22:35
*** woodster1 has quit IRC22:36
*** andreaf has quit IRC22:40
*** amotoki has quit IRC22:41
*** demorris has quit IRC22:41
*** early has quit IRC22:42
*** zns has joined #openstack-meeting-alt22:44
*** AlanClark has quit IRC22:45
*** early has joined #openstack-meeting-alt22:46
*** Barker has joined #openstack-meeting-alt22:50
*** venkatesh has joined #openstack-meeting-alt22:54
*** Barker has quit IRC22:54
*** colinmcnamara has quit IRC22:54
*** julienvey_ has joined #openstack-meeting-alt22:55
*** _nadya_ has joined #openstack-meeting-alt22:58
*** colinmcnamara has joined #openstack-meeting-alt22:58
*** samstav has quit IRC22:59
*** mattgriffin has quit IRC22:59
*** julienvey_ has quit IRC22:59
*** Sukhdev has quit IRC22:59
*** _nadya_ has quit IRC23:02
*** reaperhulk has left #openstack-meeting-alt23:02
*** eguz has joined #openstack-meeting-alt23:03
*** eghobo has quit IRC23:08
*** Sukhdev has joined #openstack-meeting-alt23:13
*** IlyaE has quit IRC23:20
*** david-lyle has quit IRC23:20
*** gyee has quit IRC23:21
*** jcoufal has quit IRC23:22
*** saurabhs has quit IRC23:22
*** yamahata has quit IRC23:24
*** kevinconway has quit IRC23:28
*** flaper87 is now known as flaper87|afk23:33
*** amcrn has quit IRC23:33
*** rmoe has joined #openstack-meeting-alt23:34
*** markmcclain has quit IRC23:35
*** markmcclain has joined #openstack-meeting-alt23:35
*** ErikB1 has quit IRC23:36
*** IlyaE has joined #openstack-meeting-alt23:41
*** baoli has joined #openstack-meeting-alt23:42
*** baoli has quit IRC23:42
*** Barker has joined #openstack-meeting-alt23:43
*** malini has quit IRC23:49
*** zns has quit IRC23:49
*** malini has joined #openstack-meeting-alt23:50
*** markmcclain has quit IRC23:52
*** gyee has joined #openstack-meeting-alt23:58
*** julienvey_ has joined #openstack-meeting-alt23:59

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