Thursday, 2014-02-06

*** nanjj has joined #openstack-meeting00:00
*** randallburt has joined #openstack-meeting00:00
zaneb#startmeeting heat00:00
openstackMeeting started Thu Feb  6 00:00:35 2014 UTC and is due to finish in 60 minutes.  The chair is zaneb. Information about MeetBot at http://wiki.debian.org/MeetBot.00:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.00:00
*** openstack changes topic to " (Meeting topic: heat)"00:00
openstackThe meeting name has been set to 'heat'00:00
zaneb#topic Roll call00:01
*** arbylee1 has joined #openstack-meeting00:01
*** openstack changes topic to "Roll call (Meeting topic: heat)"00:01
*** andrew_plunk has quit IRC00:01
randallburto/00:01
kanabuchihello00:01
*** oubiwann_ has quit IRC00:01
zanebslow day today00:02
randallburtyup00:02
*** oubiwann_ has joined #openstack-meeting00:02
nanjjhello00:02
tango|2hello00:02
*** sarob has quit IRC00:03
*** sarob has joined #openstack-meeting00:03
zanebok, I think it's going to be a quick one today00:05
zanebstevebaker is away, so I volunteered last week to chair00:05
*** arbylee1 has quit IRC00:05
zanebsdake and jpeeler also said they couldn't make it today00:05
*** armax has joined #openstack-meeting00:05
*** mrodden has joined #openstack-meeting00:05
zaneb#topic Review last meeting's actions00:05
*** openstack changes topic to "Review last meeting's actions (Meeting topic: heat)"00:05
radixhello00:05
zaneb#link http://eavesdrop.openstack.org/meetings/heat/2014/heat.2014-01-29-20.00.html00:05
*** lsell has left #openstack-meeting00:05
zanebradix: o/ :)00:05
radix:-)00:06
zanebthere weren't any!00:06
zanebnest :)00:06
zaneb#topic Adding items to the agenda00:06
*** openstack changes topic to "Adding items to the agenda (Meeting topic: heat)"00:06
zanebanybody?00:06
randallburtzaneb:  curent agenda link?00:06
zaneb#link https://wiki.openstack.org/wiki/Meetings/HeatAgenda00:07
*** mestery has joined #openstack-meeting00:07
*** lisaclark1 has joined #openstack-meeting00:07
zanebok, next :)00:07
zaneb#topic Default Resource Names00:07
*** openstack changes topic to "Default Resource Names (Meeting topic: heat)"00:07
zanebradix: is this you?00:07
*** sarob has quit IRC00:07
randallburtok so, kebray asked me to represent him here00:07
radixummm not me00:08
radixok :)00:08
randallburtzaneb:  it was kebray00:08
zanebok, cool00:08
zanebrandallburt: you have the floor :)00:08
*** SumitNaiksatam has joined #openstack-meeting00:08
randallburtbasically he is asking that we use stuff like OS::Compute::Server rather than the "internal" project names00:08
*** mestery has quit IRC00:08
randallburtuse basically use the  type of service from the catalog and openstack documentation in place00:08
zanebI like that idea00:08
radixhould we support both? (I guess we need to for backwards compatibility at least)00:09
radixs00:09
zanebradix: yes00:09
randallburtcool. based on my understanding, he'd add something in the default environment to alias like we did with Quantum00:09
radixshould those aliases be in the default environment, or should it be in the resource mappings in the code?00:09
zanebtbh it's also trivial to do it in code00:09
radix:)00:09
randallburtyeah, I'm not personally fussed either way00:10
zanebI actually would have suggested s/Nova/Compute/ a lot earlier...00:10
nanjjGive one example, how to say 'OS::Docker::Container'00:10
radixnanjj: docker isn't really related here, it's not an OpenStack program00:10
zanebexcept that I was saving those names for when we found out that are resource models were crap, and we wanted to redo them ;)00:10
radixer, not in one00:10
*** krotscheck has joined #openstack-meeting00:11
randallburtso I'll let him know to raise bp's if needed. perhaps a ML thread?00:11
randallburtzaneb:  so cagy ;)00:11
radixheh heh00:11
zaneb+1, only because turnout is so low at this meeting00:11
*** otherwiseguy has quit IRC00:11
zaneb(for ML post, that is)00:11
randallburtzaneb:  agreed00:12
zanebok, anything else on this topic?00:12
randallburtnope00:12
zanebcool00:12
zaneb#topic Discuss status of x-auth-trust bp00:12
*** openstack changes topic to "Discuss status of x-auth-trust bp (Meeting topic: heat)"00:12
zanebI added this one00:12
zanebbut I have actually already checked with shardy00:13
*** ruhe has joined #openstack-meeting00:13
zanebso there's not actually anything to discuss :)00:13
zaneb#topic Scrub the blueprints list for Icehouse00:13
*** openstack changes topic to "Scrub the blueprints list for Icehouse (Meeting topic: heat)"00:13
randallburtdoes it support v2 keystone? ;)00:13
* randallburt ducks00:13
zanebrandallburt: don't go there :D00:13
zaneb#link https://launchpad.net/heat/+milestone/icehouse-300:13
zanebso I already bumped a few bps to next00:14
*** andrew_plunk has joined #openstack-meeting00:14
zanebradix: I bumped a couple of the autoscaling API ones, I know00:14
randallburtare we having a "cut off date". for example, IIRC, glance is saying in by the 17th or its not going to make it.00:14
radixok, looking00:14
zanebrandallburt: I believe we setting on the same feature proposal date as other projects00:15
randallburtk00:15
radixwait, did you bump any? it looks the same to me00:15
*** sarob has joined #openstack-meeting00:15
*** RajeshMohan has quit IRC00:15
zanebradix: I definitely did, because you only have 3 targeted for i-3 in that list linked above now00:16
zaneb#link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule00:16
*** __nikhil__ has joined #openstack-meeting00:16
*** radsy has quit IRC00:16
zanebso patches for features should be submitted for review by 18 Feb00:16
*** __nikhil__ has quit IRC00:16
zaneb#link https://wiki.openstack.org/wiki/FeatureProposalFreeze00:17
zaneband they need to be merged by Feature Freeze on the 6th of March00:17
asalkeldo/00:17
zaneb#link https://wiki.openstack.org/wiki/FeatureFreeze00:17
zanebasalkeld: o/00:17
randallburtzaneb:  did you bump my stack-update/resource status bug?00:18
asalkeldsorry was on the phone00:18
andrew_plunko/00:18
zanebrandallburt: I haven't bumped any bugs as far as I recall00:18
radixok00:18
randallburthrm. k, I'll check in a bit.00:18
radixzaneb: oh, I was confused00:18
radixzaneb: yeah, ok00:18
zanebbut it was yesterday already that I was messing with these, so it's hard to say ;)00:18
randallburtzaneb:  nevermind. found it.00:19
radixyeah, some of that stuff needs to be moved into future00:19
randallburtall is well00:19
zanebthe bottom line is that there is less than 2 weeks left to propose patches for new features00:19
radixas-engine-db, at least00:19
zanebso it's time to start aggressively bumping blueprints to next if you don't think they're going to make it00:20
radixI really doubt intermediate resources are going to be done by I at this point, but I do plan on starting on them00:20
randallburtseems there's too many there without names attached IMO00:20
*** matsuhashi has joined #openstack-meeting00:20
zaneb#action everybody to scrub their assigned blueprints for icehouse-300:20
radixalright, doing that now00:20
zanebrandallburt: I only see two unassigned bps00:21
zanebthey both look to be on stevebaker's patch, but I assume he left them unassigned in case someone else wanted to pick them up00:21
randallburtoh, I was counting bugs too00:21
zanebI think it's likely we'll want to bump both of those00:21
randallburtprobably00:21
*** __nikhil__ has joined #openstack-meeting00:21
zanebbut I'll leave it to stevebaker when he gets back00:21
*** __nikhil__ has quit IRC00:21
*** egallen has quit IRC00:22
zaneb#topic Open Discussion00:22
*** openstack changes topic to "Open Discussion (Meeting topic: heat)"00:22
kanabuchizeneb: I'd like to discuss about this bp: https://blueprints.launchpad.net/heat/+spec/router-properties-object.00:22
zanebkanabuchi: ok, go ahead00:22
*** jmontemayor has quit IRC00:22
kanabuchiI wrote down my opinion to bp00:23
*** __nikhil__ has joined #openstack-meeting00:23
kanabuchiI think, ExtraRoutes is really important function, for supporting physical hardware00:23
zanebjust reading it now00:23
kanabuchiok00:23
*** __nikhil__ has quit IRC00:23
*** david-lyle has quit IRC00:24
zanebso the issue for me is that it's really hard for Heat to model things that are completely outside of OpenStack and Heat's data model00:25
*** sarob has quit IRC00:25
*** sarob has joined #openstack-meeting00:26
randallburtkanabuchi:  does Neutron have an actual API endpoint for CRUD on extra routes? can I get a list of them from neutron and edit each one?00:26
kanabuchiYes, real hardware resource can't model in heat now00:26
randallburtor is this strictly operational in nature?00:26
*** esker has joined #openstack-meeting00:26
*** kin_ has joined #openstack-meeting00:26
zanebkanabuchi: you seem to be saying that extra routes are needed for operators (i.e. admins)... it's not clear what that implies for Heat, which is user-facing00:27
*** nikhil__ has quit IRC00:27
kanabuchiI'm not sure about Neutron's API design, extra route should be update via route now.00:28
kanabuchizeneb: Yes, extraroute need to provide option for operators00:28
*** markwash has quit IRC00:29
* radix is still scrubbing BPs00:29
*** ryanpetrello has joined #openstack-meeting00:29
kanabuchizeneb: My image of usecase is00:29
*** nikhil has joined #openstack-meeting00:30
*** nikhil has quit IRC00:30
*** sarob has quit IRC00:30
kanabuchizeneb: when the operator want to hardware network devices, example for VPN route, L3 router, another devices...00:30
*** reed has quit IRC00:31
kanabuchizeneb: that physical hardware can't model on heat at present, right?00:31
*** nikhil has joined #openstack-meeting00:31
zanebHeat is primarily a service for users, I don't think we should have resources in the tree that are (1) only for operators, and (2) don't actually work for orchestration00:31
zaneboperators, unlike users, have the flexibility to install their own plugins00:32
*** krotscheck has quit IRC00:32
zanebso if you wanted to put the proposed patch in /contrib, I would be OK with that00:32
zanebif it's going to be user-facing, we need to figure out a different model IMO00:33
asalkeld+100:33
*** sarob has joined #openstack-meeting00:33
*** krotscheck has joined #openstack-meeting00:35
*** oubiwann_ has quit IRC00:35
zanebok, anything else on this or any other topic?00:35
*** nikhil has quit IRC00:35
radixnothing from me00:36
*** anniec has quit IRC00:36
*** nikhil has joined #openstack-meeting00:36
kanabuchizeneb: please continue this discussion, thanks00:36
kanabuchioh, not today00:36
asalkeldhttps://review.openstack.org/#/c/71199/00:36
asalkeld(easier contib setup in devstack)00:36
randallburtnope00:36
zaneb#action zaneb add summary of this discussion to the router-properties-object blueprint00:36
asalkeldif anyone is interested00:36
*** markpeek has joined #openstack-meeting00:37
*** ryanpetrello has quit IRC00:37
*** yamahata has joined #openstack-meeting00:37
*** tango|2 has quit IRC00:38
randallburtcool asalkeld. minor −1 but lgtm00:38
zanebasalkeld: how does that fit in with https://review.openstack.org/#/c/68751/ ?00:39
*** tango|2 has joined #openstack-meeting00:39
*** jcoufal has joined #openstack-meeting00:39
*** nikhil has quit IRC00:39
*** anniec has joined #openstack-meeting00:39
zanebactually, that's the wrong patch00:39
*** nikhil has joined #openstack-meeting00:39
asalkeldzaneb, I know there is a rename00:39
randallburtzaneb:  yeah, stuff got moved around a lot in those patches, but should be fixable in the devstack patch.00:39
zanebhttps://review.openstack.org/#/c/68746/800:40
zanebthat one ^00:40
asalkeldthat's why I put Richard on the review00:40
*** banix has quit IRC00:40
zanebok, cool00:40
*** markwash has joined #openstack-meeting00:40
* zaneb goes back to ignoring it ;)00:41
asalkeldzaneb,  that's for loading even when it won't work00:41
asalkeldI want the plugin to work00:41
zanebyep, you're right, different thing00:41
asalkeld:-O00:41
asalkeldI'll start using the docker plugin in anger soon00:41
zanebasalkeld: so you're working on Solum stuff now then?00:42
asalkeldyeah mostly00:42
asalkeldgota make it do something00:42
zanebcool, sounds like a good project for you00:43
tango|2Can I ask about the Update Failure Recovery bp?00:43
zanebtango|2: you may00:43
*** vkmc has joined #openstack-meeting00:43
*** sarob has quit IRC00:44
tango|2I am working on the bp for troubleshooting, got a dependency on the Update Failure Recovery.00:44
*** RajeshMohan has joined #openstack-meeting00:44
*** ken1ohmichi has joined #openstack-meeting00:44
tango|2what's the outlook for this bp?00:44
*** sarob has joined #openstack-meeting00:44
zanebchances are nil for icehouse :(00:44
zanebI already bumped it to next00:44
tango|2Is this hard to do? say for someone new like me, maybe with some guidance?00:45
zanebtango|2: it's just about the hardest possible task I can imagine taking on00:46
tango|2ok, that's good to know, so I won't make a fool of myself :)00:47
zanebtango|2: I'm not seeing a dependency in the troubleshooting-low-level-control blueprint00:47
zaneb#link https://blueprints.launchpad.net/heat/+spec/troubleshooting-low-level-control00:48
*** markwash has quit IRC00:48
tango|2It's for continuing a failed stack after an update00:48
*** sarob has quit IRC00:49
zanebif you think it requires another blueprint, please add it as a dependency down at the bottom there00:49
tango|2ok, I will add the dependency.00:49
zanebbut reading through the description, it's not clear to me that it does00:49
*** atiwari has quit IRC00:49
radixfwiw pretty much everything depends on it IMO :)00:50
*** thuc has quit IRC00:50
*** sarob has joined #openstack-meeting00:50
zanebmy plan is to use the 2+ months between feature freeze and summit to work on stuff for Juno00:51
tango|2if a create stack fails, and the user wants to debug, fix, then continue the stack, I think we can handle in the bp00:51
*** dcramer_ has joined #openstack-meeting00:51
zanebthat way I might have a chance of getting something done in the next cycle00:51
*** thuc has joined #openstack-meeting00:51
zanebin Icehouse I have got nothing done except emails :(00:51
tango|2ok I will just handle debugging failed stack-create for now, deferring the failed stack-update till Juno00:52
*** andrew_plunk has quit IRC00:52
zanebtango|2: it definitely seems less useful without being able to continue, but it doesn't seem like you couldn't write a significant portion of the code without that00:52
zanebok, cool00:53
zanebremember, you have <2 weeks left to submit patches if you want them to land for Icehouse00:53
zanebok, shall we wrap this one up?00:54
tango|2sounds good00:54
*** Sukhdev has quit IRC00:54
zanebthis meeting didn't go as quick as it was looking like after all :D00:54
nanjj:-)00:55
*** ddutta has joined #openstack-meeting00:55
radixhehe00:55
zanebthanks everyone, see you next time and/or in #heat00:55
kanabuchi:)00:55
kanabuchibye00:55
zaneb#endmeeting00:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"00:55
openstackMeeting ended Thu Feb  6 00:55:35 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)00:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2014/heat.2014-02-06-00.00.html00:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2014/heat.2014-02-06-00.00.txt00:55
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2014/heat.2014-02-06-00.00.log.html00:55
*** thuc has quit IRC00:55
*** TravT has quit IRC00:56
*** nosnos has joined #openstack-meeting00:56
*** kanabuchi has quit IRC00:57
*** randallburt has left #openstack-meeting00:57
*** Duane_ has joined #openstack-meeting00:57
*** markmcclain has joined #openstack-meeting01:00
*** nanjj has quit IRC01:00
*** sarob has quit IRC01:01
*** sarob has joined #openstack-meeting01:01
*** thuc has joined #openstack-meeting01:01
*** hemna is now known as hemnafk01:04
*** comay has quit IRC01:04
*** thuc has quit IRC01:04
*** anniec has quit IRC01:05
*** ryanpetrello has joined #openstack-meeting01:05
*** sarob has quit IRC01:06
*** thuc has joined #openstack-meeting01:06
*** ryanpetrello has quit IRC01:07
*** sarob has joined #openstack-meeting01:07
*** mrodden has quit IRC01:10
*** vkmc has quit IRC01:10
*** kanabuchi has joined #openstack-meeting01:13
*** Duane_ has quit IRC01:14
*** Duane_ has joined #openstack-meeting01:14
*** marcoemorais has joined #openstack-meeting01:15
*** jdurgin has quit IRC01:15
*** igor has joined #openstack-meeting01:15
*** igor____ has quit IRC01:16
*** marcoemorais1 has quit IRC01:17
*** jdurgin has joined #openstack-meeting01:17
*** ruhe has quit IRC01:18
*** Duane_ has quit IRC01:18
*** markmcclain has quit IRC01:21
*** prad has joined #openstack-meeting01:21
*** ddutta has quit IRC01:22
*** esmute has quit IRC01:22
*** markmcclain has joined #openstack-meeting01:23
*** pvaneck has quit IRC01:23
*** anniec has joined #openstack-meeting01:23
*** tanisdl has quit IRC01:23
*** cody-somerville has quit IRC01:25
*** thuc_ has joined #openstack-meeting01:25
*** mrda is now known as mrda_away01:27
*** rossk has quit IRC01:28
*** thuc has quit IRC01:29
*** thuc_ has quit IRC01:30
*** thuc has joined #openstack-meeting01:32
*** krotscheck has quit IRC01:34
*** bill_az_ has quit IRC01:35
*** armax has left #openstack-meeting01:36
*** markmcclain has left #openstack-meeting01:36
*** sc68cal has quit IRC01:37
*** Invent has joined #openstack-meeting01:37
*** marcoemorais has quit IRC01:38
*** marcoemorais has joined #openstack-meeting01:38
*** jcoufal has quit IRC01:39
*** jcoufal has joined #openstack-meeting01:40
*** Invent has quit IRC01:42
*** beyounn has quit IRC01:42
*** amcrn has quit IRC01:43
*** TravT has joined #openstack-meeting01:43
*** bdpayne has quit IRC01:44
*** arbylee has joined #openstack-meeting01:49
*** marcoemorais has quit IRC01:50
*** sacharya has joined #openstack-meeting01:51
*** lisaclark2 has joined #openstack-meeting01:53
*** weshay has joined #openstack-meeting01:54
*** lisaclark1 has quit IRC01:56
*** sc68cal has joined #openstack-meeting01:56
*** mestery has joined #openstack-meeting01:57
*** tango|2 has quit IRC02:00
*** fnaval has joined #openstack-meeting02:02
*** gokrokve has quit IRC02:02
*** rakhmerov has quit IRC02:05
*** ryanpetrello has joined #openstack-meeting02:07
*** beyounn has joined #openstack-meeting02:08
*** epim has quit IRC02:09
*** IlyaE has quit IRC02:11
*** anniec has quit IRC02:11
*** prad has quit IRC02:13
*** banix has joined #openstack-meeting02:13
*** sarob_ has joined #openstack-meeting02:14
*** amrith has quit IRC02:14
*** mestery has quit IRC02:15
*** amrith has joined #openstack-meeting02:15
*** sarob has quit IRC02:16
*** dcramer_ has quit IRC02:16
*** ityaptin has quit IRC02:16
*** ityaptin has joined #openstack-meeting02:16
*** stevemar has quit IRC02:17
*** jcoufal has quit IRC02:18
*** sarob_ has quit IRC02:18
*** ryanpetrello has quit IRC02:20
*** SumitNaiksatam has quit IRC02:24
*** sarob has joined #openstack-meeting02:25
*** Duane_ has joined #openstack-meeting02:26
*** morganfainberg is now known as morganfainberg_Z02:28
*** thuc has quit IRC02:28
*** mrda_away is now known as mrda02:29
*** thuc has joined #openstack-meeting02:29
*** rakhmerov has joined #openstack-meeting02:32
*** thuc has quit IRC02:33
*** baoli has joined #openstack-meeting02:37
*** Duane_ has quit IRC02:37
*** sc68cal has quit IRC02:38
*** lisaclark2 has quit IRC02:42
*** dims has joined #openstack-meeting02:44
*** arnaud__ has quit IRC02:44
*** harlowja has quit IRC02:44
*** arnaud has quit IRC02:45
*** jasondotstar has joined #openstack-meeting02:50
*** gokrokve has joined #openstack-meeting02:50
*** balajiiyer has joined #openstack-meeting02:50
*** asalkeld has quit IRC02:52
*** dkranz has quit IRC02:52
*** balajiiyer has quit IRC02:54
*** balajiiyer has joined #openstack-meeting02:54
*** harlowja has joined #openstack-meeting02:55
*** gokrokve has quit IRC02:55
*** gokrokve has joined #openstack-meeting02:56
*** spzala has quit IRC02:58
*** RajeshMohan has quit IRC02:59
*** gokrokve has quit IRC03:00
*** RajeshMohan has joined #openstack-meeting03:00
*** gokrokve has joined #openstack-meeting03:00
*** doug_shelley66 has quit IRC03:00
*** baoli has quit IRC03:00
*** rakhmerov has quit IRC03:04
*** sarob has quit IRC03:06
*** gokrokve has quit IRC03:06
*** sarob has joined #openstack-meeting03:06
*** rakhmerov has joined #openstack-meeting03:07
*** otherwiseguy has joined #openstack-meeting03:08
*** zehicle_at_dell has quit IRC03:09
*** zehicle_at_dell has joined #openstack-meeting03:09
*** briancline has quit IRC03:10
*** aignatov_ is now known as aignatov03:11
*** baoli has joined #openstack-meeting03:12
*** coolsvap_away has quit IRC03:13
*** asalkeld has joined #openstack-meeting03:13
*** sc68cal_ has joined #openstack-meeting03:14
*** stevemar has joined #openstack-meeting03:14
*** paragan has joined #openstack-meeting03:14
*** sc68cal_ has quit IRC03:15
*** sc68cal_ has joined #openstack-meeting03:18
*** sc68cal_ has quit IRC03:18
*** Mandell has quit IRC03:19
*** lcheng_ has joined #openstack-meeting03:26
*** prad has joined #openstack-meeting03:26
*** prad has quit IRC03:28
*** sc68cal_ has joined #openstack-meeting03:28
*** weshay has quit IRC03:29
*** novas0x2a|laptop has quit IRC03:29
*** thuc has joined #openstack-meeting03:31
*** thuc_ has joined #openstack-meeting03:32
*** amotoki has joined #openstack-meeting03:34
*** thuc has quit IRC03:36
*** zehicle_at_dell has quit IRC03:37
*** zehicle_at_dell has joined #openstack-meeting03:38
*** Invent has joined #openstack-meeting03:38
*** sc68cal_ has quit IRC03:39
*** baoli has quit IRC03:40
*** ken1ohmichi has quit IRC03:42
*** Invent has quit IRC03:42
*** zehicle_at_dell has quit IRC03:42
*** zehicle_at_dell has joined #openstack-meeting03:43
*** sc68cal has joined #openstack-meeting03:45
*** comay has joined #openstack-meeting03:47
*** rakhmerov has quit IRC03:47
*** david-lyle has joined #openstack-meeting03:51
*** rakhmerov has joined #openstack-meeting03:52
*** rakhmerov has quit IRC03:54
*** rakhmerov has joined #openstack-meeting03:54
*** rakhmerov has quit IRC03:54
*** rakhmerov has joined #openstack-meeting03:54
*** rakhmerov has quit IRC03:54
*** rakhmerov has joined #openstack-meeting03:55
*** rakhmerov has quit IRC03:55
*** emagana has quit IRC03:57
*** thuc_ has quit IRC03:58
*** thuc has joined #openstack-meeting03:58
*** thuc has quit IRC04:03
*** amrith has quit IRC04:03
*** arbylee has quit IRC04:04
*** lcheng_ has quit IRC04:06
*** dcramer_ has joined #openstack-meeting04:08
*** HenryG has joined #openstack-meeting04:09
*** Duane_ has joined #openstack-meeting04:16
*** bdpayne has joined #openstack-meeting04:18
*** Duane_ has quit IRC04:20
*** gokrokve has joined #openstack-meeting04:24
*** arbylee1 has joined #openstack-meeting04:36
*** TravT has quit IRC04:37
*** sgordon has quit IRC04:37
*** dguitarbite has joined #openstack-meeting04:37
*** lcheng_ has joined #openstack-meeting04:38
*** jcooley_ has quit IRC04:43
*** ArthurBerezin has joined #openstack-meeting04:43
*** coolsvap has joined #openstack-meeting04:44
*** akuznetsov has joined #openstack-meeting04:45
*** ryanpetrello has joined #openstack-meeting04:46
*** ayoung is now known as ayoung-ZzZzzZZzz04:48
*** arbylee1 has quit IRC04:48
*** sc68cal has quit IRC04:50
*** mspreitz has joined #openstack-meeting04:50
*** sc68cal has joined #openstack-meeting04:50
*** gokrokve has quit IRC04:50
*** gokrokve has joined #openstack-meeting04:52
*** arbylee has joined #openstack-meeting04:52
*** otherwiseguy has quit IRC04:53
*** gokrokve has quit IRC04:53
*** SumitNaiksatam has joined #openstack-meeting04:56
*** jasondotstar has quit IRC04:57
*** doug_shelley66 has joined #openstack-meeting04:57
*** doug_shelley66 has quit IRC05:01
*** nosnos_ has joined #openstack-meeting05:02
*** mspreitz has left #openstack-meeting05:02
*** dims has quit IRC05:03
*** Guest10180 has joined #openstack-meeting05:03
*** dims has joined #openstack-meeting05:04
*** jrist has quit IRC05:04
*** sarob has quit IRC05:05
*** balajiiyer has quit IRC05:05
*** harlowja has quit IRC05:05
*** nosnos has quit IRC05:06
*** arbylee has quit IRC05:07
*** emagana has joined #openstack-meeting05:08
*** pablosan has quit IRC05:09
*** sarob has joined #openstack-meeting05:10
*** pablosan has joined #openstack-meeting05:11
*** emagana has quit IRC05:13
*** ryanpetrello has quit IRC05:13
*** harlowja has joined #openstack-meeting05:14
*** sarob has quit IRC05:15
*** arbylee has joined #openstack-meeting05:16
*** arbylee has quit IRC05:18
*** nshaikh has joined #openstack-meeting05:19
*** blamar has quit IRC05:21
*** aignatov is now known as aignatov_05:27
*** markpeek has quit IRC05:30
*** akuznetsov has quit IRC05:34
*** Mandell has joined #openstack-meeting05:36
*** tchaypo has joined #openstack-meeting05:36
*** akuznetsov has joined #openstack-meeting05:36
*** tchaypo has left #openstack-meeting05:37
*** jrist has joined #openstack-meeting05:39
*** Invent has joined #openstack-meeting05:39
*** DinaBelova_ is now known as DinaBelova05:41
*** jrist has quit IRC05:43
*** jrist has joined #openstack-meeting05:43
*** Invent has quit IRC05:43
*** bdpayne has quit IRC05:44
*** sandywalsh has quit IRC05:46
*** banix has quit IRC05:47
*** jcooley_ has joined #openstack-meeting05:49
*** jrist has quit IRC05:52
*** emagana has joined #openstack-meeting05:57
*** jamespage_ has joined #openstack-meeting05:58
*** dteselkin_ has quit IRC05:59
*** dteselkin_ has joined #openstack-meeting05:59
*** julim has joined #openstack-meeting06:00
*** denis_makogon has joined #openstack-meeting06:00
*** Duane_ has joined #openstack-meeting06:04
*** jamespage_ has quit IRC06:05
*** jamespage__ has joined #openstack-meeting06:05
*** DinaBelova is now known as DinaBelova_06:06
*** matsuhashi has quit IRC06:07
*** matsuhashi has joined #openstack-meeting06:07
*** bdpayne has joined #openstack-meeting06:08
*** Duane_ has quit IRC06:09
*** matsuhas_ has joined #openstack-meeting06:09
*** matsuhashi has quit IRC06:09
*** Guest10180 is now known as jimidar06:10
*** jimidar is now known as jimidar|afk06:11
*** jcooley_ has quit IRC06:11
*** ujuc has joined #openstack-meeting06:13
*** sarob has joined #openstack-meeting06:17
*** igor has quit IRC06:18
*** igor has joined #openstack-meeting06:18
*** egallen has joined #openstack-meeting06:20
*** sarob has quit IRC06:21
*** smemon92 has joined #openstack-meeting06:23
*** topol has quit IRC06:24
*** jcooley_ has joined #openstack-meeting06:24
*** denis_makogon_ has joined #openstack-meeting06:24
*** _nadya_ has joined #openstack-meeting06:25
*** denis_makogon has quit IRC06:26
*** mrda is now known as mrda_away06:27
*** IlyaE has joined #openstack-meeting06:34
*** Daisy has joined #openstack-meeting06:38
*** jamespage__ has quit IRC06:39
*** jamespage__ has joined #openstack-meeting06:39
*** nosnos has joined #openstack-meeting06:40
*** jimidar has joined #openstack-meeting06:40
*** bdpayne has quit IRC06:42
*** nosnos_ has quit IRC06:42
*** julim has quit IRC06:42
*** _nadya_ has quit IRC06:43
*** IlyaE has quit IRC06:45
*** NikitaKonovalov_ is now known as NikitaKonovalov06:48
*** coolsvap_away has joined #openstack-meeting06:51
*** dguitarbite_ has joined #openstack-meeting06:52
*** coolsvap has quit IRC06:52
*** dguitarbite has quit IRC06:52
*** markwash has joined #openstack-meeting06:53
*** NikitaKonovalov is now known as NikitaKonovalov_06:54
*** jpich has joined #openstack-meeting06:55
*** HenryG_ has joined #openstack-meeting06:55
*** yamahata__ has quit IRC06:57
*** yamahata__ has joined #openstack-meeting06:57
*** HenryG has quit IRC06:58
*** egallen has quit IRC06:58
*** IlyaE has joined #openstack-meeting06:58
*** jamespage__ has quit IRC06:58
*** egallen has joined #openstack-meeting06:58
*** masayukig has quit IRC06:58
*** ddutta has joined #openstack-meeting06:58
*** luis_fdez1 has quit IRC06:59
*** DeeJay1 has joined #openstack-meeting06:59
*** luis_fdez has joined #openstack-meeting06:59
DeeJay1right on time ;)06:59
DaisyWelcome, DeeJay1 !07:00
DeeJay1hi Daisy!07:00
DaisyI will start the meeting then.07:00
Daisy#startmeeting OpenStack I18n Meeting07:00
openstackMeeting started Thu Feb  6 07:00:33 2014 UTC and is due to finish in 60 minutes.  The chair is Daisy. Information about MeetBot at http://wiki.debian.org/MeetBot.07:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:00
*** openstack changes topic to " (Meeting topic: OpenStack I18n Meeting)"07:00
openstackThe meeting name has been set to 'openstack_i18n_meeting'07:00
DaisyHello! Who are around there to attend I18n meeting?07:00
* jimidar here07:01
jpichHi Daisy o/07:01
DaisyGood moring/afternoon/evening.07:01
jimidarGood Afternoon from India Daisy07:01
DaisyLet's start.07:02
Daisy#topic Update on log messages translation plan07:02
*** openstack changes topic to "Update on log messages translation plan (Meeting topic: OpenStack I18n Meeting)"07:02
*** coolsvap_away has quit IRC07:02
DaisyI raised the request to Oslo in Icehouse design summit: seperate log messages from other messages.07:02
DaisyWith the help of Doug Hellmann ( PTL of Oslo ), the log translation plan is discussed in openstack release meeting, where most project PTLs joined.07:03
*** Steff00 has joined #openstack-meeting07:03
DaisyOslo team is working on the technical support. The goal is to add separate translation marker functions similar to _() with names like _LE and _LW to allow us to extract the messages into different catalogs.07:03
Steff00hello everybody sorry to be late07:03
DaisyWe are going to skip debug messages, for this phase of the project, and focus only on messages at INFO or higher levels.07:03
DaisyGood evening, Steff00 .07:04
DaisyThe _() marker should only be used for end-user messages from exceptions and API calls.07:04
DaisySteff00: we are on the first topic: log messages translation plan07:04
Steff00ok thank you07:04
DaisyWhen Oslo team make sure their technical support well and there is no issues, they will broadcast it in the dev ML.07:05
DaisyI will work together with Oslo team to pick up a project as a prototype and have a try.07:05
*** funzo has quit IRC07:05
DaisyThen the syncronization scripts and resources in Transifex will be updated based on this change. We will find a resource only containing exceptions and API calls.07:05
DaisyThen it depends on each translation team to decide whether to translate these end-user messages in their languages in Icehouse releasy cycle.07:05
*** nati_ueno has quit IRC07:06
*** akuznetsov has quit IRC07:06
DaisyIn Icehouse release cycle, maybe not all projects have this update ready. But I hope to find at least one project.07:06
Daisyquestions? comments?07:06
*** coolsvap has joined #openstack-meeting07:07
jpichGreat to see progress on this :)07:07
Steff00no questions for me07:07
DaisyIn Havana code, there are 7000+ messages in total.07:08
DeeJay1I spent some time yesterday with ajeager who's handling the doc builds and we've run into some problems with building the translated documentation through tox in a seperate build environment, right now we stuck to using the generatedocbook script from the manuals package instead of the doc-tools one due to xml2po not being available in a tox virtualenv07:08
DaisyAfter separation, I think, the real end-user messages would be less than a half.07:08
DaisyDeeJay1: thank you for working on it. Could we discuss it in a following topic?07:09
*** akuznetsov has joined #openstack-meeting07:09
DeeJay1(ok, now my screen refreshed and I feel silly ;)07:09
Daisy:)07:09
*** IlyaE has quit IRC07:09
*** _nadya_ has joined #openstack-meeting07:09
DaisyNext topic07:10
Daisy#topic Push on the translation of "installation guide"07:10
*** openstack changes topic to "Push on the translation of "installation guide" (Meeting topic: OpenStack I18n Meeting)"07:10
Daisy:)07:10
DaisyI think there is just a reminder.07:10
DaisyI see DeeJay1 is working on a website to display the installation guide in many languages.07:10
DaisyIt's a wonderful job, DeeJay1 .07:11
DeeJay1yup, but I'd like for the teams to look at the build status, there are a few issues with some of the translations07:11
*** coolsvap_away has joined #openstack-meeting07:11
DaisyAs we discussed before, in HK summit, infra team agreed to use a staging server for the draft translation review.07:11
Daisyso I think they will agree to move your work to openstack infra.07:12
*** coolsvap has quit IRC07:12
DaisyWe just need to make sure it run well and most issues can be resolved.07:12
DeeJay1I don't know if it's feasible, right now I have more room to pull the translations from transifex without commiting the po files to the repo07:12
DaisyWhat issues do you have now?07:13
*** funzo has joined #openstack-meeting07:13
DeeJay1https://bugs.launchpad.net/openstack-manuals/+bug/1275499 - some guides will have missing chars in the PDF documents without that07:14
uvirtbotLaunchpad bug 1275499 in openstack-manuals "clouddocks-maven-plugin and Polish language support" [Undecided,New]07:14
Daisy"pull the translations from transifex without commiting the po files to the repo", do you mean the translations are from Transfiex , not git repo? I think it's just what we want. We want to get the latest translation, whether it is committed or not?07:14
DeeJay1Daisy: yes, but AFAIR getting the translations isn't possible on all jenkins nodes right now07:14
*** lcheng_ has quit IRC07:14
DaisyI think that's a known issue. We could work with Doc team to resolve it.07:15
Daisywhy "AFAIR getting the translations isn't possible on all jenkins nodes right now"?07:15
*** lcheng_ has joined #openstack-meeting07:15
DeeJay1Daisy: transifexrc is only on a subset of them, but I'd have to double check that07:16
DaisyDo we need transifexrc to be installed on all nodes? I think we only need to install it on the relevant nodes.07:17
DaisyAnd I remember there is a way to config to install transifexrc.07:17
DeeJay1yes, but I don't know how the infra team feels about putting the credentials to transifex on all the nodes07:17
DaisyI think they are open minded if we really need it.07:18
DeeJay1anyway I'll take a second look at it07:19
*** sacharya has quit IRC07:20
DeeJay1so feel free to assign that task to me07:20
DaisyDeeJay1: how about you send a summary and the issues you need help to Infra team, when you feel comfortable. Then we can start the discussion with them.07:20
DaisySure, I will.07:20
*** nkhare_ has joined #openstack-meeting07:20
*** IlyaE has joined #openstack-meeting07:21
Daisyas to the previous issue you raised, "we stuck to using the generatedocbook script from the manuals package instead of the doc-tools", I know this situation.07:21
DeeJay1I'd like to take a look at using itstool for that07:21
DaisyBut what's the meaning of "xml2po not being available in a tox virtualenv"? Why we need tox virtualenv?07:22
DeeJay1Daisy: well, it's something the docs team seems to want07:22
*** _nadya_ has quit IRC07:22
DaisyI don't understand the background.07:22
DaisySo if we could use doc-tools, this issue can be fixed?07:23
*** harlowja is now known as harlowja_away07:23
*** markwash has quit IRC07:24
DeeJay1well, it seems that the background is to use a similar process like for other software, eg all the required build tools are installed in a virtualenv not to require changes to the build infrastructure if any new dependencies are added07:24
Daisyok.07:24
DeeJay1so if you need tool X to build the manual you only change tox.ini in the openstack-manuals repo without any intervention from the infra team07:24
Daisygot your point.07:25
Daisydoes our I18n use a separate config file with doc team, or we use a same tox.ini?07:25
DeeJay1well, as for recently we didn't have a build infrastructure at all07:26
DaisyI think, they may want us to use a same tox virtualbox. That is a same tox.ini07:26
Daisyok. Got your point.07:26
DaisyIf you need any of help, send email to I18n ML.07:26
*** _nadya_ has joined #openstack-meeting07:27
DeeJay1of course, the only thing I'd need right now is some feedback on mail recent email, about building all the docs in openstack-manuals at once vs building the docs separate07:27
DeeJay1so I could forward that to the docs team07:28
DaisyIn my last talk with ajeager , he wanted me to summary our requirements, and then we together initiate the discussion with Infra team, in order to use doc-tools.07:28
*** stevemar has quit IRC07:28
ujucoh... sorry.. ;(07:28
*** _nadya_ has quit IRC07:28
Daisywelcome, ujuc.07:28
ujuchi :)07:28
DaisySo I will continue the discussion with ajeager about how to use doc-tools directly, when I'm back to office.07:29
*** MaxV has joined #openstack-meeting07:29
DaisySorry for my late response, DeeJay1. I'm on vacation now and don't check email frequently.07:30
DaisyI think it's a wonderful work you did.07:30
DeeJay1Daisy: n/p - I for one can only do stuff outside of work, so durin EU buisness hours I'm out of the loop anyway07:30
*** sushil_ has joined #openstack-meeting07:31
DaisySo let's continue the discussion in ML, and improve your work together.07:31
Daisycan we move to next topic ?07:31
*** dfarrell07 has joined #openstack-meeting07:31
DeeJay1yes07:31
Steff00ok07:31
Daisy#topic Work items in Feb07:31
*** openstack changes topic to "Work items in Feb (Meeting topic: OpenStack I18n Meeting)"07:32
DaisyIn this topic, we list the work items together, and find the assignees. :)07:32
DaisyFinish installation guide translations.07:32
*** markwash has joined #openstack-meeting07:33
*** IlyaE has quit IRC07:33
DaisyI think, coordinators should be the assignee. The end of Feb would be a good time to stop this work. In March, we would be very busy in the messages translation.07:33
*** brucer has quit IRC07:34
DaisySet up Horizon messages translation environment in Transifex07:34
DaisyI will take this work.07:34
Daisy#action Daisy Set up Horizon messages translation environment in Transifex07:34
Steff00ok for France wa try to go with the installation guide, it will be hard because I think I've lost a great part of the team, even me sometimes07:34
DaisyIt's under processing.07:35
DaisyHow many people are working on the translation together with you, Steff00 ?07:35
*** jimidar has quit IRC07:36
Steff00almost nobody anymore . I lost control one month because of work and it seems nobody does translation anymore07:36
Daisy:) understand.07:36
Steff00I'll get new ones I hope07:36
DaisyActually, the document translation has no deadline, no hard stop.07:37
* DeeJay1 is still alone on the PL team also07:37
*** coolsvap_away is now known as coolsvap07:37
*** ddutta has quit IRC07:37
DaisyYou can continue this work even you miss the time.07:37
DaisyBut anyway, in march, we have to focus on the message translation because of the release cycle won't wait for us.07:38
Steff00no problem, I do my best on the focuses topics07:38
DaisyThank you. Steff00 .07:38
DaisyWrite scripts and create jobs to publish these installation guides in different languages.07:39
*** flaper87|afk is now known as flaper8707:39
DaisyI think, DeeJay1 has do a good job, and it's very similar to what he has finished now.07:39
*** nkhare_ has left #openstack-meeting07:39
*** Invent has joined #openstack-meeting07:40
DaisyDeeJay1 may want to focus on his current work. So are there anybody else who would like to work on it?07:40
DaisyOr how can we leverage DeeJay1's work ?07:40
DaisyWhat we need to do is to publish our translations in docs.openstack.org.07:41
*** dfarrell07 has left #openstack-meeting07:41
*** IlyaE has joined #openstack-meeting07:41
DaisyIf nobody, I can take it too.07:41
Steff00I try  to do it for french07:42
Daisy#action Daisy and Steff00 to publish the translations to docs.openstack.org.07:42
DaisyYes, I definitely need your help, Steff00 . At least, each of you need to write a page in your own language as an index page of your language.07:43
Steff00It will be apleasue DAisy :)07:43
*** emagana has quit IRC07:43
DaisyJust like what Japanese team has done: http://docs.openstack.org/ja/07:43
*** Invent has quit IRC07:44
Steff00I'll take a look today at the japanese page07:44
DaisyYes, Steff00 . After we do it, it will be a great success, which we can broadcast in next summit.07:44
Steff00I think I won't be at the Atlanta Summit, hard to get the money for the fly07:45
DeeJay1hmm, I'd like to take a look if we can leverage the main docs page and just make it translatable07:45
*** asalkeld has quit IRC07:46
DeeJay1IMHO the language pages should provide links to the English docs in case the docs in <language> aren't provided07:46
DaisySteff00: if you want, many be you can apply for a travel sponsor program.07:46
DeeJay1so in the end we could just point browsers to specific versions07:46
*** mdurnosvistov_ has joined #openstack-meeting07:46
Steff00Daisy : Why not07:46
DaisyDeeJay1: I don't know if we really want to "links to the English docs in case the docs in <language> aren't provided"07:47
*** MaxV has quit IRC07:47
DaisyIf we only translate the main page, and provide English doc links, the help we provide to the readers is only the translation of main page. If readers cannot understand English main page, how can they understand English doc?07:48
Steff00they won't07:49
DaisyCurrently, we only provide links to locale language documents in locale page.07:49
DeeJay1Daisy: ok, let me put it this way - right now you have to be on the English page first just to be able to select the Japanese page07:49
DaisyYes.07:49
*** sc68cal is now known as sc68cal_07:50
DaisyDeeJay1: do you want me to assign you a task: move your website to OpenStack Infra? You don't need to finish it in Feb, but it can be a clear goal for you. Is that OK with you?07:51
amotokihi, i just backed from the meeting.07:51
DeeJay1Daisy: yeah, I'll work with Andreas to put it up on docs-draft somehow07:51
DaisyThank you, DeeJay1.07:52
*** sarob has joined #openstack-meeting07:52
Daisy#action DeeJay1 to move the document publish website to docs-draft07:52
*** sc68cal_ is now known as sc68cal07:52
*** Duane_ has joined #openstack-meeting07:52
Daisyamotoki: we are going to move to open discussion now.07:53
Daisy#topic Open discussion07:53
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack I18n Meeting)"07:53
*** evgenyf has joined #openstack-meeting07:53
Daisyanything to discuss here?07:53
amotokiDaisy: what does "Set up Horizon messages translation environment in Transifex" mean?07:53
DaisyDeeJay1: besides to publish the draft translation documents, do you have further plan to improve it, as a way for translators to easily do the review?07:53
*** julim has joined #openstack-meeting07:54
Daisyamotoki: it's to set up the resources, make sure the synchronization scripts running well before March, then we can start the translation after string freeze.07:54
ujucinstall guide end in Feb 28???07:54
*** IlyaE has quit IRC07:54
DeeJay1Daisy: frankly, I'd like to get rid of the code fragments in the po files07:55
Daisyno deadline ujuc. But it's a good date to close the document translation, because we have to focus on the message translation in order to catch the release date.07:55
DeeJay1Daisy: it's just needles copy&paste IMO07:55
amotokiDaisy: i see. I start to think it may be okay to import from transifex to master automatically too.07:55
*** denis_makogon_ has quit IRC07:55
ujucDaisy: ok :)07:55
amotokiDaisy: what do you think?07:56
DaisyDeeJay1: then you may need to improve two scripts in doc-tools.07:56
DaisyAgree, amotoki .07:56
*** kevinbenton has joined #openstack-meeting07:56
*** rohit404 has joined #openstack-meeting07:56
DaisyI like automation too.07:56
*** Duane_ has quit IRC07:56
DeeJay1Daisy: yeah, but I wonder if someone has a need for them to exist...07:57
amotokiAfter milestone-proposed is cut, we need to do it manually, so we can control the quality of the release I believe.07:57
DaisyDeeJay1: in my mind, if we want to use your website as a review tool, I think we need to a way to facilitate reviewers to report the errors to translators they find.07:58
Daisyamotoki: even we automatically import from Transifex to master, there is a review job created in gerrit.07:59
DaisyIt's not 100% automation. Is this what you want?07:59
DaisyNow nova, glance and etc are using this way to import translations.08:00
amotokiDaisy: yes, but the patch of translation import is not checked from the content point of view...08:00
Daisysomebody must approve before it finally gets merge.08:00
DeeJay1Daisy: there's a report bug on every page I think, maybe I could switch it to do the reporting against openstack-i18n instead of manuals08:00
Daisynice thinking, DeeJay108:01
Daisyamotoki: after milestone-proposed, who do you plan to do the merge manually?08:01
amotoki+1 for bug link to i18n site.08:01
Daisysomebody who can take reponsible for the content review?08:02
amotokii think so now. milestone-proposed is very tricky, so it is not easy to automate.08:02
*** markwash has quit IRC08:02
amotokiDaisy: it is expected to be done on Transifex.08:02
Daisyso we only import reviewed contents?08:03
amotokiIMO it is okay to import all contents.08:03
jpichEven if the language is not at 100%?08:04
amotokibecause we upload final translation for milestonr-proposed.08:04
amotokiand we can drop non-100% lang at this stage.08:04
*** comay has quit IRC08:04
Daisyamotoki: if we follow Nova and glace and etc, the importing is being done daily, which will generate a review job in gerrit.08:04
DaisyAs our first plan, some coordinators should be included as the reviewer to vote +1.08:05
amotokiyeah.08:05
DaisyBut now, I don't think the coordinators are involved.08:05
Daisyso the approval is being done by technical developers.08:05
Steff00Sorry I have to leave .08:05
amotokiThe meeting time is over. Can we continue the discussion in #openstack-translation?08:06
DaisySure. sorry I don't notice the time.08:06
DaisyThank you all for your attending!08:06
Daisy#endmeeting08:06
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:06
openstackMeeting ended Thu Feb  6 08:06:35 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2014/openstack_i18n_meeting.2014-02-06-07.00.html08:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2014/openstack_i18n_meeting.2014-02-06-07.00.txt08:06
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2014/openstack_i18n_meeting.2014-02-06-07.00.log.html08:06
jpichI must go as well unfortunately, please let the list know what is decided with regard to automating the translation reviews :) Thanks!08:06
*** jpich has quit IRC08:06
DaisyI will, jpich!08:07
ujuc:)08:07
*** Fdot has joined #openstack-meeting08:08
*** rakhmerov has joined #openstack-meeting08:08
*** lcheng_ has quit IRC08:12
*** jcoufal has joined #openstack-meeting08:17
*** evgenyf has quit IRC08:17
*** markwash has joined #openstack-meeting08:18
*** NikitaKonovalov_ is now known as NikitaKonovalov08:20
*** sbalukoff has quit IRC08:20
*** MaxV has joined #openstack-meeting08:22
*** AlexF has joined #openstack-meeting08:22
*** egallen has joined #openstack-meeting08:24
*** xianghui has joined #openstack-meeting08:26
*** sbalukoff has joined #openstack-meeting08:26
*** jimidar has joined #openstack-meeting08:29
*** jimidar has quit IRC08:30
*** bogdando has joined #openstack-meeting08:30
*** jimidar has joined #openstack-meeting08:31
*** ndipanov_gone is now known as ndipanov08:32
*** pnavarro has joined #openstack-meeting08:32
*** smemon92 has quit IRC08:33
*** mdurnosvistov_ has quit IRC08:40
*** nati_ueno has joined #openstack-meeting08:40
*** Daisy has quit IRC08:41
*** afazekas has joined #openstack-meeting08:42
*** markwash has quit IRC08:43
*** marekd|away is now known as marekd08:47
*** jcoufal has quit IRC08:50
*** nacim has joined #openstack-meeting08:51
*** ygbo has joined #openstack-meeting08:51
*** jlibosva has joined #openstack-meeting08:52
*** jtomasek has joined #openstack-meeting08:55
*** salv-orlando has quit IRC08:59
*** sarob has quit IRC09:00
*** sarob has joined #openstack-meeting09:01
*** fbo is now known as fbo_away09:01
*** I159 has joined #openstack-meeting09:02
*** beyounn has quit IRC09:03
*** sarob has quit IRC09:06
*** jcoufal has joined #openstack-meeting09:06
*** fbo_away is now known as fbo09:06
*** jimidar has quit IRC09:07
*** jimidar has joined #openstack-meeting09:09
*** aignatov_ is now known as aignatov09:10
*** rossella_s has joined #openstack-meeting09:12
*** mdbooth has joined #openstack-meeting09:15
*** jamespage_ has joined #openstack-meeting09:15
*** yassine has joined #openstack-meeting09:16
*** AlexF has quit IRC09:16
*** jamespage_ has quit IRC09:17
*** jimidar has quit IRC09:19
*** nati_ueno has quit IRC09:23
*** safchain has joined #openstack-meeting09:24
*** cody-somerville has joined #openstack-meeting09:28
*** cody-somerville has quit IRC09:28
*** cody-somerville has joined #openstack-meeting09:28
*** nati_ueno has joined #openstack-meeting09:29
*** ArthurBerezin1 has joined #openstack-meeting09:29
*** ArthurBerezin1 has left #openstack-meeting09:30
*** igor_ has joined #openstack-meeting09:30
*** igor has quit IRC09:32
*** jcooley_ has quit IRC09:32
*** ArthurBerezin has quit IRC09:32
*** nati_ueno has quit IRC09:36
*** DinaBelova_ is now known as DinaBelova09:37
*** reed has joined #openstack-meeting09:38
*** derekh has joined #openstack-meeting09:38
*** johnthetubaguy has joined #openstack-meeting09:39
*** johnthetubaguy1 has joined #openstack-meeting09:40
*** johnthetubaguy has quit IRC09:40
*** miarmak has joined #openstack-meeting09:40
*** Invent has joined #openstack-meeting09:41
*** Duane_ has joined #openstack-meeting09:41
*** johnthetubaguy has joined #openstack-meeting09:42
*** johnthetubaguy1 has quit IRC09:44
*** Invent has quit IRC09:45
*** Duane_ has quit IRC09:45
*** Steff00 has quit IRC09:49
*** rushiagr has left #openstack-meeting09:52
*** jimidar has joined #openstack-meeting09:54
*** jimidar has quit IRC09:58
*** jasondotstar has joined #openstack-meeting10:00
*** johnthetubaguy has quit IRC10:03
*** ArthurBerezin has joined #openstack-meeting10:03
*** ArthurBerezin has left #openstack-meeting10:04
*** johnthetubaguy has joined #openstack-meeting10:05
*** sarob has joined #openstack-meeting10:11
*** salv-orlando has joined #openstack-meeting10:14
*** sarob has quit IRC10:16
*** pnavarro has quit IRC10:18
*** evgenyf has joined #openstack-meeting10:19
*** ruhe has joined #openstack-meeting10:21
*** aignatov is now known as aignatov_10:22
*** mrda_away is now known as mrda10:31
*** salv-orlando has quit IRC10:31
*** ken1ohmichi has joined #openstack-meeting10:32
*** ken1ohmichi has quit IRC10:32
*** pnavarro has joined #openstack-meeting10:36
*** paragan has quit IRC10:36
*** xianghui has quit IRC10:38
*** thouveng has joined #openstack-meeting10:41
*** jhenner has joined #openstack-meeting10:42
*** evgenyf has quit IRC10:44
*** bgorski has joined #openstack-meeting10:53
*** evgenyf has joined #openstack-meeting10:54
*** NikitaKonovalov is now known as NikitaKonovalov_10:54
*** dguitarbite_ has quit IRC10:54
*** NikitaKonovalov_ is now known as NikitaKonovalov10:57
*** aignatov_ is now known as aignatov10:58
*** jamespage_ has joined #openstack-meeting10:58
*** jamespage_ has quit IRC10:58
*** jasondotstar has quit IRC11:00
*** yassine has quit IRC11:01
*** mrda is now known as mrda_away11:02
*** ujuc has quit IRC11:03
*** RajeshMohan has quit IRC11:10
*** jimidar|afk has quit IRC11:11
*** RajeshMohan has joined #openstack-meeting11:11
*** jprovazn has joined #openstack-meeting11:11
*** egallen has quit IRC11:14
*** salv-orlando has joined #openstack-meeting11:14
*** david-lyle has quit IRC11:17
*** boris-42_ has quit IRC11:18
*** vkmc has joined #openstack-meeting11:19
*** andreaf has joined #openstack-meeting11:22
*** jimidar|afk has joined #openstack-meeting11:28
*** Duane_ has joined #openstack-meeting11:29
*** jimidar|afk has quit IRC11:29
*** coolsvap_away has joined #openstack-meeting11:29
*** miarmak has quit IRC11:29
*** coolsvap has quit IRC11:30
*** salv-orlando has quit IRC11:30
*** miarmak has joined #openstack-meeting11:33
*** miarmak has quit IRC11:33
*** Duane_ has quit IRC11:33
*** miarmak has joined #openstack-meeting11:33
*** miarmak has quit IRC11:34
*** ken1ohmichi has joined #openstack-meeting11:34
*** miarmak has joined #openstack-meeting11:34
*** fbo is now known as fbo_away11:35
*** Invent has joined #openstack-meeting11:41
*** salv-orlando has joined #openstack-meeting11:43
*** vkmc has quit IRC11:43
*** coolsvap_away is now known as coolsvap11:46
*** Invent has quit IRC11:46
*** pnavarro has quit IRC11:48
*** jamespage_ has joined #openstack-meeting11:49
*** salv-orlando has quit IRC11:49
*** jasondotstar has joined #openstack-meeting11:50
*** jamespage_ has quit IRC11:51
*** DinaBelova is now known as DinaBelova_11:52
*** safchain has quit IRC11:56
*** Duane_ has joined #openstack-meeting11:57
*** paragan has joined #openstack-meeting12:00
*** baoli has joined #openstack-meeting12:00
*** Duane__ has joined #openstack-meeting12:01
*** matrohon has quit IRC12:02
*** rakhmerov has quit IRC12:02
*** doug_shelley66 has joined #openstack-meeting12:04
*** Duane_ has quit IRC12:04
*** DinaBelova_ is now known as DinaBelova12:05
*** jamespage_ has joined #openstack-meeting12:07
*** amrith has joined #openstack-meeting12:08
*** jamespage_ has quit IRC12:09
*** Invent has joined #openstack-meeting12:10
*** pradipta` has joined #openstack-meeting12:10
*** pradipta has quit IRC12:12
*** yassine has joined #openstack-meeting12:13
*** yassine_ has joined #openstack-meeting12:13
*** yamahata has quit IRC12:14
*** asalkeld has joined #openstack-meeting12:17
*** asalkeld has left #openstack-meeting12:17
*** Duane__ has quit IRC12:17
*** miqui has joined #openstack-meeting12:18
*** alexpilotti has joined #openstack-meeting12:18
*** Duane_ has joined #openstack-meeting12:18
*** egallen has joined #openstack-meeting12:18
*** Duane_ has quit IRC12:22
*** Invent has quit IRC12:23
*** IanGovett has joined #openstack-meeting12:25
*** jcooley_ has joined #openstack-meeting12:26
*** boris-42_ has joined #openstack-meeting12:30
*** jcooley_ has quit IRC12:31
*** rakhmerov has joined #openstack-meeting12:32
*** Daisy has joined #openstack-meeting12:32
*** rfolco has joined #openstack-meeting12:33
*** pnavarro has joined #openstack-meeting12:34
*** coolsvap has quit IRC12:34
*** coolsvap has joined #openstack-meeting12:34
*** rakhmerov1 has joined #openstack-meeting12:34
*** rakhmerov has quit IRC12:34
*** ryanpetrello has joined #openstack-meeting12:35
*** jamespage_ has joined #openstack-meeting12:37
*** rakhmerov1 has quit IRC12:39
*** jamespage_ has quit IRC12:40
*** baoli has quit IRC12:42
*** baoli has joined #openstack-meeting12:42
*** igor has joined #openstack-meeting12:45
*** Duane_ has joined #openstack-meeting12:45
*** igor_ has quit IRC12:46
*** f_rossigneux has quit IRC12:47
*** isviridov has left #openstack-meeting12:49
*** ken1ohmichi has quit IRC12:49
*** egallen_ has joined #openstack-meeting12:52
*** egallen has quit IRC12:52
*** egallen_ is now known as egallen12:52
*** weshay has joined #openstack-meeting12:53
*** ken1ohmichi has joined #openstack-meeting12:53
*** sgordon has joined #openstack-meeting12:54
*** coolsvap has quit IRC12:55
*** fbo_away is now known as fbo12:55
*** yassine has quit IRC12:55
*** Duane_ has quit IRC12:56
*** Duane_ has joined #openstack-meeting12:56
*** jasondotstar has quit IRC13:00
*** Duane_ has quit IRC13:00
*** rakhmerov has joined #openstack-meeting13:01
*** sushil_ has quit IRC13:01
*** evgenyf has quit IRC13:02
*** pdmars has joined #openstack-meeting13:04
*** Daisy has quit IRC13:06
*** evgenyf has joined #openstack-meeting13:07
*** prad_ has joined #openstack-meeting13:08
*** safchain has joined #openstack-meeting13:09
*** safchain has quit IRC13:09
*** safchain has joined #openstack-meeting13:10
*** amrith has quit IRC13:15
*** alex_xu has joined #openstack-meeting13:18
*** jasondotstar has joined #openstack-meeting13:19
*** julim has quit IRC13:23
*** topol has joined #openstack-meeting13:27
*** topol has quit IRC13:31
*** rdxc has joined #openstack-meeting13:32
*** vgnbkr_1 has quit IRC13:36
*** prad_ has quit IRC13:38
*** vkmc has joined #openstack-meeting13:38
*** Tross has quit IRC13:42
*** jjmb has joined #openstack-meeting13:44
*** ken1ohmichi has quit IRC13:45
*** jdob has joined #openstack-meeting13:49
*** thomasem has joined #openstack-meeting13:49
*** rbrady has joined #openstack-meeting13:50
*** doug_shelley66 has quit IRC13:50
*** otherwiseguy has joined #openstack-meeting13:51
*** ktbenton has quit IRC13:52
*** garyduan has joined #openstack-meeting13:52
*** arbylee has joined #openstack-meeting13:53
*** gduan has quit IRC13:53
*** dprince has joined #openstack-meeting13:56
*** vjay has joined #openstack-meeting13:57
enikanorov__neutron lbaas meeting in 3 minutes13:57
*** avishayb has joined #openstack-meeting13:57
*** jcooley_ has joined #openstack-meeting13:57
*** hartsocks has joined #openstack-meeting13:58
*** zhiyan has joined #openstack-meeting13:59
*** dvarga has joined #openstack-meeting14:00
*** BobBall has joined #openstack-meeting14:00
*** belmoreira has joined #openstack-meeting14:00
*** dkranz has joined #openstack-meeting14:00
enikanorov__hi, who's for lbaas meeting?14:00
*** sushil_ has joined #openstack-meeting14:01
obondarevhi14:01
evgenyfHi14:01
*** pcm_ has joined #openstack-meeting14:01
enikanorov__#startmeeting neutron lbaas14:01
openstackMeeting started Thu Feb  6 14:01:02 2014 UTC and is due to finish in 60 minutes.  The chair is enikanorov__. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
sbalukoffHowdy! I am!14:01
*** openstack changes topic to " (Meeting topic: neutron lbaas)"14:01
openstackThe meeting name has been set to 'neutron_lbaas'14:01
edhallhi14:01
* pcm_ lurking14:01
enikanorov__ok, lets start with the announcements14:02
vjayhi14:02
avishaybhello14:02
enikanorov__and the most important is that gates are working more or less14:02
obondarev\o/14:02
*** s3wong has joined #openstack-meeting14:02
enikanorov__so core team may spend more time on reviews14:02
*** arbylee has left #openstack-meeting14:02
enikanorov__and also you actually can get +1 on your patches14:03
vjay:-)14:03
evgenyfGood!14:03
enikanorov__and if it's -1 from Jenkins - you need to really dig into the logs14:03
enikanorov__and not just recheck no bug :)14:03
*** jcooley_ has quit IRC14:03
*** bknudson has quit IRC14:03
baoliHi, rkukura14:03
enikanorov__the second announcement is that feature proposal deadline is 18th of feb14:03
*** rkukura has joined #openstack-meeting14:04
enikanorov__if i'm not mistaken, so any new featuers implementation should be published before that14:04
vjaywhat is published? merged to trunk or submitted to Gerrit?14:04
*** mspreitz has joined #openstack-meeting14:04
enikanorov__pushed to gerrit. if it's on review alredy - that's fine14:05
*** BobBall has left #openstack-meeting14:05
*** sushil_ has quit IRC14:05
enikanorov__we have whole line of patches under development on all three major features14:06
enikanorov__l7, lb instance, ssl14:06
enikanorov__the features are important and make a big part of lbaas API and functionality14:06
*** rbrady is now known as rbrady-brb14:07
*** sushil_ has joined #openstack-meeting14:07
*** browne has joined #openstack-meeting14:07
*** jamespage_ has joined #openstack-meeting14:07
*** ftcjeff has joined #openstack-meeting14:07
*** lblanchard has joined #openstack-meeting14:07
enikanorov__in my opinion there are very little chances that what we are working on right now will be merged in Icehouce14:07
*** browne has left #openstack-meeting14:08
*** sankarshan_away is now known as sankarshan14:08
enikanorov__but at the same time we'd like to give users some advancement in lbaas service over what whas in Havana14:08
*** dcramer_ has quit IRC14:08
enikanorov__so there is an idea to make a 'downstream' version of neutron (focused on lbaas plugin and drivers)14:09
vjaywhat does that mean? can you elaborate?14:09
enikanorov__yep14:09
enikanorov__that supposed to be the merge of current master + exsiting features on review, which are stable and tested14:10
enikanorov__so the branch could be packed and given to users for early adoption14:10
enikanorov__so I'd like to ask if that makes sense to you guys?14:11
vjaywho will track and make this release happen?14:11
obondarevwho will be using that downstream version? Are therte such requests from someone?14:11
evgenyfWhen should that happen?14:11
*** dvarga is now known as dvarga|away14:11
*** dvarga|away is now known as dvarga14:12
avishaybI think some of Radware  customers are candidates14:12
enikanorov__vjay: i guess i'm going to do that if there is such demand14:12
enikanorov__now i'm exploring the need for that14:12
enikanorov__of course this is some additional work that needs to be done14:12
avishaybwe can not come with nothing in lbaas for H version14:12
enikanorov__however it may be beneficial for some vendors/customers14:13
enikanorov__but having downstream version doesn't means every unmerget lbaas patch gets in14:14
*** crank has quit IRC14:14
enikanorov__so we need some kind of policy for that (of course focused on quality)14:14
obondarevare there any examples of such downstream versions in any other OS projects?14:14
*** yamahata has joined #openstack-meeting14:15
*** RajeshMohan has quit IRC14:15
enikanorov__obondarev: in fact many adopters use whiole OS in such manner14:15
evgenyfenikanorov__: are we planning to do this version before or after a freeze of Icehouse14:16
enikanorov__I'm trying to understand will it be beneficial for development speed14:16
obondarevyeah, I know, my question was about kind of official downstream version14:16
*** RajeshMohan has joined #openstack-meeting14:16
enikanorov__as we'll need to work with two repos14:16
enikanorov__evgenyf: we don't have deadlines, although what I'm talking about is not something decided14:16
enikanorov__it's just an idea14:16
enikanorov__i'm going to discuss it with Mark14:16
vjayHow will fixes get into this branch?14:17
enikanorov__as we don't wan't to position it as 'here, have that, because neutron could not make anything in Icehouse'14:17
*** rbrady-brb is now known as rbrady14:17
vjaytill when we will support this?14:18
enikanorov__vjay: i think if a patch passes Jenkins and the author has tests to verify the patch, it will be a candidate for inclusion14:18
enikanorov__by saying tests i mean integration tests14:18
enikanorov__(scenarios)14:18
enikanorov__vjay: good question. It needs to be decided14:19
enikanorov__meanwhile it would be good if you could ask potential customers if they will be willing to try such kind of stuff.14:20
vjaywell, i know of two types of customers. one that dont want to move from havana to icehouse. Others who wants to jump from grizzly directly to icehouse.14:21
vjayusing this version will be very tricky14:21
obondareva question: what about horizon? do we need a downstream horizon version for new features merged to downstream neutron?14:21
enikanorov__ok, basically that's the argument against the idea :)14:22
vjaywill this branch be kept in sync with neutron changes in icehouse?14:22
vjaychanges == fixes14:22
enikanorov__obondarev: i don't think so, CLI would be enough14:22
enikanorov__vjay: yes14:22
*** yamahata has quit IRC14:22
*** bknudson has joined #openstack-meeting14:22
vjayand it will be cut on top of havana?14:22
*** belmoreira has quit IRC14:22
obondarevenikanorov__: is CLI really ok for customers?14:23
vjaysorry14:23
vjayicehouse14:23
*** belmoreira has joined #openstack-meeting14:23
enikanorov__vjay:  i think it will be following current master, because we are not targeting particular release14:23
*** yamahata has joined #openstack-meeting14:23
*** neelashah has joined #openstack-meeting14:24
enikanorov__it matters how we distribute the code14:24
*** egallen_ has joined #openstack-meeting14:24
vjaythen it will be tricky.14:24
obondarevenikanorov__: ok, so for CLI we need a downstream neutron client version - right?14:24
enikanorov__it could be a mere diff applied to a certain revision of neutron's master14:24
*** eharney has joined #openstack-meeting14:24
enikanorov__obondarev: yes14:24
enikanorov__vjay: it's not very simple, but we can try to make it simple14:24
*** belmoreira1 has joined #openstack-meeting14:25
*** yamahata has quit IRC14:25
*** bill_az has joined #openstack-meeting14:25
obondarevenikanorov__: things are getting complicated :)14:25
*** yamahata has joined #openstack-meeting14:25
enikanorov__well, not really14:25
vjayhmm...it is a long shot... as you said we need to first verify the need.14:25
enikanorov__to test a new feature in the devstack you only need to provide a link to a repo14:25
enikanorov__in your localrc14:25
enikanorov__so using downstream version should not be more complex14:26
edhallso what specific functionality will be added to this branch?14:26
*** egallen has quit IRC14:26
*** egallen_ is now known as egallen14:26
enikanorov__edhall: based on review results. it could be a common case when feature is not getting approved because of some minor concerns or feature freeze or ...14:27
*** JoshuaG_AIM has joined #openstack-meeting14:27
enikanorov__in this case if we are sure it's working - we add it to our branch14:27
*** belmoreira has quit IRC14:27
enikanorov__any more questions on the downstream idea?14:29
evgenyfLet's here Mark's opinion14:30
sbalukoffExpansion on edhall's question: Are there specific features being considered to add to this branch right now?14:30
evgenyfhear*14:30
*** bauzas has joined #openstack-meeting14:30
enikanorov__sbalukoff: i think we don't have major feature that is ready for that14:31
sbalukoffOk.14:31
enikanorov__loadbalancer instance may be, but it's not a big addition to functionality14:31
*** prad_ has joined #openstack-meeting14:31
*** prad_ has quit IRC14:32
*** jrist has joined #openstack-meeting14:32
enikanorov__also, we'll have 3 months between feature freeze and the time new features will be reviewed for merging14:32
vjayenikanorov__: just to double confirm. there is no chance that ssl, l7 will make it to icehouse. is that right?14:33
enikanorov__i didn't say no chance, but i don't think we will manage to polish those features14:33
edhallso this is essentially a way to progress in the face of the Feb 18th feature freeze?14:34
*** Invent has joined #openstack-meeting14:34
sbalukoffThat's what it sounds like to me, too.14:34
obondarevfeature freeze is Feb 28 I think14:34
*** toanster_ is now known as toanster14:35
*** thomasem_ has joined #openstack-meeting14:35
enikanorov__yes, but our deadline is closer14:35
obondarevso we have a bit more time to polish14:35
*** IanGovett has quit IRC14:35
obondarevwhat is our deadline?14:35
enikanorov__right, our objective is to publish the code before 18th :)14:35
enikanorov__not have it merged14:36
*** bgorski has quit IRC14:36
enikanorov__we'll have ~2 additional weeks to address review comments14:36
enikanorov__but it's still lot's of work14:36
obondarevright14:36
obondarevit's all depends on the review speed14:37
obondarevfrom core reviewers14:37
enikanorov__i think it also depends on development speed right now14:37
*** joesavak has joined #openstack-meeting14:37
enikanorov__as we don't have working implementations of l7 and ssl yet14:37
obondarevright now yes14:38
*** thomasem has quit IRC14:38
*** dims has quit IRC14:38
*** lisaclark1 has joined #openstack-meeting14:39
obondarevso let's move to the statuses on features?14:39
enikanorov__let's briefly discuss the features under development14:39
enikanorov__i'll start with lb instance14:39
enikanorov__the patch is ready, obondarev is working on applying instance approach to haproxy14:40
obondarevI've uploaded a patch wich adopts lb instance for agent scheduling14:40
enikanorov__so users will be able to create multiple pools in haproxy14:40
enikanorov__these are prerequisities for L7 rules14:40
obondarevsecond patch will adopt lb instance for lbaas agent itself, I'm working on it14:40
*** jecarey has joined #openstack-meeting14:40
*** julim has joined #openstack-meeting14:41
evgenyfmy next steps for SSL are: writing db layer unitests and fixing all review comments14:42
enikanorov__avishayb: obondarev: what's the status of l7? do we have CLI for l7 resources?14:42
avishaybI have updated the wiki - https://wiki.openstack.org/wiki/Neutron/LBaaS/l714:42
*** julim has quit IRC14:42
evgenyfBTW, I have undated the WIKI page too, https://wiki.openstack.org/wiki/Neutron/LBaaS/SSL14:42
enikanorov__evgenyf: good14:42
avishaybits in sync with the code now. Begining next week I will start to react on reviews14:43
avishaybNo CLI yet14:43
enikanorov__avishayb: i see14:43
enikanorov__evgenyf: i have another concern on ssl API14:43
obondarevavishayb: I put some new comments on the patch. Also will be great if you can address/answer comments on the previous patch sets14:43
*** burt1 has joined #openstack-meeting14:43
*** julim has joined #openstack-meeting14:43
enikanorov__it seems complex to me, so I'd like to see some ability to use simplified workflow14:43
*** sandywalsh has joined #openstack-meeting14:43
avishaybobodarev: I will14:44
obondarevit's really hard to review if you don't know what you agrre and what not and why14:44
enikanorov__i'll explain what i mean14:44
evgenyfThere is beagaviour description for vip/pool/ssl policy protocole mismatches. Guys, please have a look..14:44
evgenyf*behaviour14:44
*** dims has joined #openstack-meeting14:44
*** dhellmann_ is now known as dhellmann14:44
enikanorov__by saying 'complex API' i don't mean it needs to be changed, but instead it should provide ability to do things on less steps14:45
obondarevavishayb: thanks14:45
enikanorov__say, create a vip with 1 command, providing all ssl attributes14:45
enikanorov__evgenyf: do you think it's possible?14:45
*** changbl has quit IRC14:45
enikanorov__1 command = 1 rest call14:45
*** tongli has joined #openstack-meeting14:46
evgenyfenikanorov__: Do you mean using CLI?14:47
enikanorov__no, i'd prefer to see it in the API14:47
enikanorov__it's like loadbalancer instance, you can create one, and then add pool to it, or you can create a pool and lb instance will be created for the pool automatically14:48
enikanorov__can we apply the same approach to policies/certs?14:48
*** balajiiyer has joined #openstack-meeting14:48
evgenyfyou mean applying default SSL poliy and certs. to vip on creation stage?14:49
vjaydefault cert?14:50
enikanorov__no14:50
enikanorov__i mean i could provide cert on vip create14:50
*** zehicle_at_dell has quit IRC14:50
evgenyfI do not see a reason for doing that.. can you elaborate ?14:51
enikanorov__i'm just thinking of the terrible amount of parameters i need right now to setup a ssl vip14:51
enikanorov__ok, i'll review the API again and will explain more precisely14:51
evgenyfenikanorov__: Ok, let's discuss it14:52
enikanorov__ok, that's all i wanted to discuss today14:52
*** doug_shelley66 has joined #openstack-meeting14:52
enikanorov__doesn anyone have questions/items to discuss?14:52
*** bgorski has joined #openstack-meeting14:52
evgenyfPlease review SSL wiki page for new details14:53
obondarevlbaas scenario test is in good shape, should be merged soon14:53
vjayis anyone working on sslconnect+haproxy?14:53
*** balajiiyer has left #openstack-meeting14:53
enikanorov__vjay: stunnel?14:54
vjaysorry, yes stunnel14:54
*** jamespage_ has quit IRC14:54
*** blamar has joined #openstack-meeting14:55
enikanorov__it's me, but i have not made much progress on that particular item as I'm working with evgenyf on ssl API patch14:55
vjayok.14:56
*** cody-somerville has quit IRC14:57
*** ndn9797 has joined #openstack-meeting14:57
enikanorov__ok, if theres' no other questions then let's wrap up14:57
*** eglynn has joined #openstack-meeting14:58
enikanorov__thanks for joining everyone14:58
*** pcm_ has left #openstack-meeting14:58
*** amrith has joined #openstack-meeting14:58
*** dcramer_ has joined #openstack-meeting14:58
vjaybye.14:58
sbalukoffSeeya!14:58
obondarevbye all14:58
s3wongbye14:58
evgenyfbye14:58
enikanorov__see you all14:58
*** gordc has joined #openstack-meeting14:58
enikanorov__#endmeeting14:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:58
openstackMeeting ended Thu Feb  6 14:58:57 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_lbaas/2014/neutron_lbaas.2014-02-06-14.01.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_lbaas/2014/neutron_lbaas.2014-02-06-14.01.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_lbaas/2014/neutron_lbaas.2014-02-06-14.01.log.html14:59
*** hartsocks has left #openstack-meeting14:59
*** ildikov_ has joined #openstack-meeting14:59
*** bgorski has quit IRC15:00
*** belmoreira1 has quit IRC15:00
*** markpeek has joined #openstack-meeting15:00
jd__#startmeeting ceilometer15:00
openstackMeeting started Thu Feb  6 15:00:18 2014 UTC and is due to finish in 60 minutes.  The chair is jd__. 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: ceilometer)"15:00
openstackThe meeting name has been set to 'ceilometer'15:00
eglynno/15:00
jd__#link https://wiki.openstack.org/wiki/Meetings/Ceilometer15:00
tonglihi, @jd__15:00
tonglio/15:00
jd__hi everyone15:00
gordco/15:00
*** crank has joined #openstack-meeting15:00
ildikov_o/15:00
nprivalovao/15:02
*** belmoreira has joined #openstack-meeting15:02
jd__#topic Milestone status icehouse-315:02
*** ndn9797 has left #openstack-meeting15:02
*** openstack changes topic to "Milestone status icehouse-3 (Meeting topic: ceilometer)"15:02
*** boris-42_ has quit IRC15:02
jd__#link https://launchpad.net/ceilometer/+milestone/icehouse-315:02
*** amotoki has quit IRC15:02
*** amrith has quit IRC15:02
jd__so a lot of things are started, but it'd be great to finish ASAP15:02
ildikov_we still need approval for this patch: https://review.openstack.org/#/c/62157/15:02
jd__otherwise we'll be caught in the gate storm15:03
*** bgorski has joined #openstack-meeting15:03
*** vjay has quit IRC15:03
jd__ildikov_: yeah I'll try to take a look at it15:03
gordcildikov_: i may have time to review tomorrow as well.15:03
*** amrith has joined #openstack-meeting15:03
ildikov_jd__: thanks15:03
jd__otherwise not much to add on my part yet15:04
*** stevemar has joined #openstack-meeting15:04
ildikov_thanks guys, it would be really good, if we could go on wih the statistics bp and also have the patch sets of the complex query landed in i-315:04
jd__anything else about one of your blueprint?15:04
nprivalovaI'm still confused about aggregation15:04
nprivalovanot sure should I continue or not15:05
*** s3wong has quit IRC15:05
jd__nprivalova: do you have a requirement on that?15:05
eglynnnprivalova: did we come to any conclusion on the overlapping periods issue I raised?15:05
silehto/15:05
ityaptino/15:05
eglynnnprivalova: ... i.e. the question of whether aggregation can be helpful in the common case of periods that overlap15:06
* jd__ dodges the issue15:06
nprivalovaeglynn: we agreed that it is not for alarming15:06
nprivalova#link https://blueprints.launchpad.net/ceilometer/+spec/base-aggregation15:07
*** esker has quit IRC15:07
*** jswarren has joined #openstack-meeting15:07
eglynnnprivalova: k, then the question really is the potential benefit for the other common cases of recurring statistics queries15:07
*** esker has joined #openstack-meeting15:08
eglynnnprivalova: ... if we can detect when the same query constraints recurr15:08
nprivalovayep, I agree. I saw a comment about billing use case15:08
eglynnnprivalova: ... and match the actual query constraints to the pre-aggregated values15:08
*** prad_ has joined #openstack-meeting15:08
nprivalovaanyway, I think we may continue with meeting :)15:08
jd__ok15:08
jd__#topic Tempest integration15:09
*** openstack changes topic to "Tempest integration (Meeting topic: ceilometer)"15:09
jd__wassup on that?15:09
*** esker has quit IRC15:09
*** mestery has joined #openstack-meeting15:09
nprivalovawe have the following15:09
nprivalovahttps://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:bp/add-basic-ceilometer-tests,n,z15:09
nprivalovaso notifications part is done15:09
nprivalovabut we have a bug :)15:09
*** Gordonz has joined #openstack-meeting15:10
nprivalova#link https://bugs.launchpad.net/ceilometer/+bug/127460715:10
uvirtbotLaunchpad bug 1274607 in ceilometer "ceilometer-agent-notification is broken without eventlet monkey patching" [Critical,In progress]15:10
nprivalovayep, so that's why we have only -1 from Jenkins15:11
*** bgorski has quit IRC15:11
jd__fair enough, that one should be resolved soon fortunately15:11
nprivalovaI'm testing the fix15:11
*** avishayb has quit IRC15:11
jd__#topic Release python-ceilometerclient?15:11
*** openstack changes topic to "Release python-ceilometerclient? (Meeting topic: ceilometer)"15:11
eglynnno need this AFAIK15:11
eglynn*for this15:12
jd__ok :)15:12
jd__#topic Polling-on-demand discussion (ityaptin)15:12
*** openstack changes topic to "Polling-on-demand discussion (ityaptin) (Meeting topic: ceilometer)"15:12
jd__ityaptin: enlighten us15:12
ityaptinabout pollsters on demand. Use cases of this feature are tests and debug.15:12
nprivalova#link https://review.openstack.org/#/c/66551/15:13
jd__(nprivalova: the fix works if you have https://review.openstack.org/#/c/71124/)15:13
*** Gordonz has quit IRC15:13
eglynnso the purpose of this is to trigger polling for tests ... could the same be acheived by simply configuring the test with a v. short pipeline interval?15:13
*** nwidell has joined #openstack-meeting15:13
* dhellmann apologizes for being late15:13
*** Gordonz has joined #openstack-meeting15:14
gordchttps://blueprints.launchpad.net/ceilometer/+spec/run-all-pollsters-on-demand15:14
ityaptinAnd exists proposal to turn on this feature only with flag 'debug', because somebody can DoS ceilometer with starting pollstering.15:14
jd__dhellmann: you're… not fired!15:14
*** IanGovett has joined #openstack-meeting15:14
* dhellmann whew!15:14
eglynni.e. the test needs to precipitate events that happen relatively infrequently (i.e. polling cycles with the boilerplate pipeline.yaml)15:14
eglynn... so one approach would be simply to make these events more frequent in the test scenario15:15
gordcityaptin: how does the flag get set? the DoS issue was a concern when i read bp15:15
silehtfyi: I have added this to devstack: CEILOMETER_PIPELINE_INTERVAL=1015:15
jd__the problem is that polling != having sample anyway, there's no guarantee that samples are going to be available N seconds after being polled15:15
dhellmannis this for tempest tests or unit tests?15:15
jd__nothing's synchronous15:15
jd__dhellmann: tempest15:15
tongli@eglynn, that still won't be the same, I would think.15:15
silehtperhaps we can just set a different value for devstack-gate15:15
jd__DoS concern? I doubt that, it's a feature available on RPC15:15
*** IanGovett1 has joined #openstack-meeting15:16
jd__sure the admin can DoS himself, but well.. he's admin15:16
eglynntongli: not exactly equivalent, but perhaps a close enough analogue?15:16
*** krotscheck has joined #openstack-meeting15:16
nprivalovaI think it's not only for tempest. When I install devstack it is useful just to check that pollsters work ok, without waiting interval15:16
*** belmoreira has quit IRC15:16
jd__nprivalova: agreed15:16
ityaptingordc: For example -  debug option15:16
eglynnnprivalova: ... but the test has to wait anyway for some "ingestion" lag15:16
tongli@eglynn, I think it will be nice to hit an enter key, then expect the code hit the break point.15:17
*** matsuhas_ has quit IRC15:17
*** vijendar has joined #openstack-meeting15:17
silehteglynn, agree, for example the swift accounts size is done by a async swift task15:17
tongli@eglynn, @ityaptin, or you use the new notification alarm.15:17
silehteglynn, so you have to wait swift have updated the value because ceilometer poll it15:18
silehtbecause/before15:18
tongliwhich will simply trigger it as soon as a notification is present on the bus.15:18
* jd__ has no problem with that feature15:18
*** whenry has joined #openstack-meeting15:18
dhellmannif we're going to have a special test mode, it seems like it makes the most sense to make that a separate executable that runs the polling one time and exits15:18
nprivalovaactually the question was about default value for debug flag :)15:18
dhellmannrather than adding a test mode to the main service15:18
gordcdhellmann: agreed15:19
eglynndhellmann: ... that sounds reasonable to me15:19
jd__dhellmann: if that would be synchronous, that'd be better15:19
ityaptintongli: If we want to test pollsters it does not suitable15:19
*** belmoreira has joined #openstack-meeting15:19
*** IanGovett has quit IRC15:19
jd__dhellmann FTW15:19
tongli@ityaptin, true.15:19
dhellmannjd__: yeah, just refactor the code that runs the polling pipelines so it can be called from a console script15:19
*** vgnbkr_1 has joined #openstack-meeting15:19
jd__dhellmann: I vote for that definitely, because that would be much better for Tempest15:19
dhellmannthat wouldn't do anything for testing the collector15:19
*** ArthurBerezin has joined #openstack-meeting15:19
dhellmanndo we need some way to have the collector notify tests when data is available?15:20
jd__what I don't know is if it's reasonable to use that trick in tempest?15:20
*** matrohon has joined #openstack-meeting15:20
jd__dhellmann: that'd be great15:20
dhellmannjd__: good point, we wouldn't really be testing the polling service15:20
dhellmannbut we could have separate tests for that15:20
*** mestery has quit IRC15:20
dhellmannif the point is to show that the service works and the pollsters work, do they have to run in the same test to know they work?15:21
*** nosnos has quit IRC15:21
jd__or we can also use the API method as in the current patch if it's synchronous, i.e. the GET /pollsters returns only when all pollsters are run15:21
nprivalovawe may set configs only in devstack15:21
*** mestery has joined #openstack-meeting15:21
nprivalovathere is o way to hack smth in tempest15:21
jd__having a callback on the collector is another issue, I don't have a solution yet but we can think about something else later I gues15:21
eglynnin general I wonder how does tempest handle asserting other asynchronous tasks have completed?15:21
dhellmannnprivalova: ah, so we have to set devstack to configure ceilometer for tempest?15:21
eglynnsuch as spinning up an instance15:21
eglynnor a volume becoming available?15:22
nprivalovadhellmann: AFAIK, yes15:22
dhellmanneglynn: I see a lot of polling for status and timing out in the errors in the recheck list15:22
dhellmannnprivalova: ok15:22
jd__eglynn: by waiting and timing out, which has the potential to make Ceilometer the new Neutron :/15:22
*** ildikov_ has quit IRC15:22
*** mspreitz has quit IRC15:22
*** kevinconway has joined #openstack-meeting15:22
eglynnyeah I guess15:23
nprivalovamaybe we should move it to mailing list?15:23
*** mrodden has joined #openstack-meeting15:23
dhellmannare we emitting any sort of notification of having received data?15:23
eglynn... /me is made a bit nervous by making big changes to the ceilo execution path for testing15:23
dhellmanncould we write the test to watch the log for a specific message, or to listen for a notification?15:23
dhellmanneglynn: yeah15:23
eglynn... in the sense that we end up testing something other than what actually runs in prod15:24
jd__sending notification when we receive notifications?15:24
*** bgorski has joined #openstack-meeting15:24
*** ildikov_ has joined #openstack-meeting15:24
dhellmannjd__: otherwise I guess the test would call the api over and over until it got the data it wanted?15:24
jd__Ceilometer inception15:24
nprivalovaoh no :)15:24
jd__dhellmann: yeah… polling and timing out :(15:24
eglynnyeah so in prod its not the extra notification being emitted that has value, it's these data being visible in the API15:24
dhellmanneglynn: sure, I'm just trying to figure out how to write the test with the least polling15:25
dhellmannmaybe polling is the best thing we can do15:25
eglynn... I dunno, suppose we did something funky with mongo replication15:25
jd__I think so for now15:25
dhellmannpolling would certainly be simplest15:25
eglynn... and the data stopped being visible from a secondary replica15:25
eglynn... but the tests still pass15:26
jd__now the question is, is it acceptable to have a different path for polling (a request to the API) rather than the regular timer in term of testing15:26
dhellmanneglynn: but our tests aren't for mongo, they're for our code15:26
nprivalovanotifications is another question. Now we are speaking only about polling15:26
*** nshaikh has left #openstack-meeting15:26
eglynndhellmann: I thinking of our mongo storage driver doing some replication aware logic that has the potential to be broken15:26
dhellmannnprivalova: what I was hinting at was having ceilometer send a notification that the test could listen for to know when data had arrived, instead of polling the API15:26
*** fnaval has quit IRC15:27
dhellmanneglynn: if we have to put replication logic in our driver, then we'd have to test for it -- we don't have anything like that now, right?15:27
eglynndhellmann: nope, we don't ... that was just off the cuff example of something that could break15:27
dhellmanneglynn: ok15:27
jd__I think this is going too far?15:28
tongli@dhellmann, I am working the notification alarm, if that is what you asked.15:28
jd__I think my previous question is a good one, can I haz a cheese^W^Wyour opinion?15:28
eglynndhellmann: and might not be caught by a test that just asserted for a special notification that the collector had seen the incoming metering message15:28
tongli@dhellmann, when a notification appears, you can make something happen,15:28
dhellmannjd__: ok, I think we're talking about 2 different things15:28
dhellmanntongli: good point, just a sec15:28
eglynns/collector/notification agent/15:28
dhellmannjd__: I was talking about how the test would know when ceilometer's collector had received data15:29
nprivalovalet us write to mailing list again because honestly I don't see any solution now15:29
dhellmannnprivalova: good idea15:29
jd__dhellmann: I know, but that's a different topic that the one we're discussing15:29
dhellmannsorry, I thought we had moved on15:29
jd__dhellmann: so I'd like to have an answer on the first point, first :)15:30
* dhellmann wonders when jd__ became such a stickler ;-)15:30
jd__which is having different path used to poll the data15:30
nprivalovaand please take a look into notification tests in tempest, because we need to be sure that tests are correct15:30
jd__lol15:30
dhellmannI think it's a mistake to build something in for testing that is too different from something that would be useful in production15:30
dhellmannwe have a periodic polling loop, so we need a test that shows that we poll periodically15:30
eglynndhellmann: +115:30
jd__agreed15:30
dhellmannif we have an API to trigger polling, then we need a *separate* test to show that the api triggers polling15:31
*** bgorski has quit IRC15:31
* jd__ hits the channel with his maillet15:31
dhellmannso we might as well just test for the code we have now, since we can't avoid it15:31
dhellmannif, as nprivalova says, we have to use the devstack configuration, then we will need to adjust the polling interval there to something relatively small and use that for the test15:31
* jd__ nods15:32
eglynnyep ... my suggestion exactly15:32
jd__as far as the notification of notification received is concern, I think it's something we should think about15:32
dhellmannalternately, if we could have the test adjust that interval -- maybe by starting a second copy of the service? -- then we could do all of this in tempest15:32
jd__but probably not here and now :)15:32
*** spzala has joined #openstack-meeting15:33
dhellmannjd__: for notification of notifications, we might be able to use the alarm trigger feature, but that is using some production code to test other production code15:33
jd__indeed15:33
dhellmannso it might be better conceptually to just have the test poll the API looking for the data15:33
eglynnas long as the polling is "smart" enough, it that approach really that bad?15:33
jd__that would be good enough for now anyway15:33
dhellmannwhich is less elegant, in some sense, but more "correct" from a testing standpoint15:33
jd__eglynn: we'll see?15:33
dhellmanneglynn: nah, it just feels a little heavy-handed15:34
*** bgorski has joined #openstack-meeting15:34
eglynnby "smart" I mean say using a reasonably adaptive/backed-off intra-poll delay15:34
jd__it's tempest, you can hammer the API15:34
dhellmanneglynn: right15:34
*** banix has joined #openstack-meeting15:34
dhellmannhaha15:34
jd__"adaptive", tsss :)15:34
eglynnLOL :)15:35
jd__GIVE ME THE DAMN DATA YOU API15:35
jd__that's how we should do it15:35
jd__shall we move on gentlemen?15:35
* dhellmann opens a blueprint to change the API to allow queries in all caps15:35
nprivalovaunfortunately we should commit it to devstack first :)15:35
* jd__ puts his maillet away15:35
*** ddutta has joined #openstack-meeting15:35
silehtdevstack already have CEILOMETER_PIPELINE_INTERVAL configuration variable, so we just have to set it in gate-devstack15:35
*** david-lyle has joined #openstack-meeting15:36
jd__(and gentlewomen)15:36
*** Invent has quit IRC15:36
*** jgrimm has joined #openstack-meeting15:36
jd__nprivalova: would that be a problem?15:36
*** Gordonz has quit IRC15:36
nprivalovasileht: I will work on this15:36
jd__good point sileht15:36
*** thomasbiege has joined #openstack-meeting15:36
dhellmannsileht saves us from over-engineering15:36
*** atiwari has joined #openstack-meeting15:36
*** Invent has joined #openstack-meeting15:36
jd__#topic Work with metadata discussion15:37
nprivalovajd__, I don't know :) maybe you have a power to commit everything to everywhere15:37
*** openstack changes topic to "Work with metadata discussion (Meeting topic: ceilometer)"15:37
nprivalovait's me again15:37
jd__nprivalova: I may or may not have some super power :D15:37
nprivalovaThe long story short:15:38
nprivalovaWhen user requests meters or resources their's metadata is being flattened.15:38
nprivalovaOn other hand, when meter or resource is stored to db their metadata is flattened too.15:38
nprivalovaThese two processes are independent and now two different flatten-functions exist.15:38
nprivalovaWe decided to keep only one of them (related bug #link https://bugs.launchpad.net/ceilometer/+bug/1268618).15:38
uvirtbotLaunchpad bug 1268618 in ceilometer "similar flatten dict methods exists" [Medium,In progress]15:38
nprivalovaAfter some discussions with team I decided to use dict_to_keyval everywhere. The reason is that this func allow user to create queues on lists and doesn't contain bugs.15:38
nprivalovaSo the question: API layer is the only place where recursive_keypairs is used and this function contais a bug.15:38
*** david_lyle_ has joined #openstack-meeting15:39
nprivalovaThe perfect solution is to change recursive_keypairs=>dict_to_keyval in API, but output of these funcs are different15:39
nprivalovaYou may take a look here #link https://review.openstack.org/#/c/67704/4/ceilometer/api/controllers/v2.py15:39
nprivalovaIs it absolutely forbidden to make any changes in API output? We may postpone to change recursive_keypairs=>dict_to_keyval in API but maybe we may fix a bug in recursive_keypairs and fix all our wrong tests?15:39
dhellmannnprivalova: what's the bug in recursive_keypairs?15:40
eglynnwell it would be forbidden I'd say to make changes that could break existing API callers15:40
*** tanisdl has joined #openstack-meeting15:40
dhellmannyes, changing the return format would require an API version bump15:40
nprivalovashould I fix the bug but simulate it again in API to keep the behaviour?15:40
eglynn#link https://wiki.openstack.org/wiki/APIChangeGuidelines15:40
dhellmannwhich isn't out of the question, but is probably not something we want to do at this point in the cycle15:40
*** jgrimm has quit IRC15:41
* jd__ shakes in fear of APIv315:41
nprivalova#link https://bugs.launchpad.net/ceilometer/+bug/126862815:41
uvirtbotLaunchpad bug 1268628 in ceilometer "recursive_keypairs doesn't throw 'separator' param to next iteration" [Undecided,In progress]15:41
gordcnprivalova: i guess your fix is good then. i actually don't like how we're outputing some odd formatting... but it will change output to fix it.15:41
dhellmannnprivalova: ah15:41
gordcsince the consensus is to not change output i think we need to keep your patch in to keep output consistent as before.15:42
nprivalovayep, just wanted to clear that15:42
*** david-lyle has quit IRC15:43
jd__cool15:43
jd__I like when we all agree15:43
jd__#topic Open discussion15:43
*** openstack changes topic to "Open discussion (Meeting topic: ceilometer)"15:43
nprivalovaand one more cr https://review.openstack.org/#/c/68583/15:43
gordcnprivalova: you've no idea how much it bothers me seeing 'a.b:c:d' keys.lol i'll review patch again15:43
nprivalovagordc: cool :)15:44
tonglianyone know if the ctrl+c problem was fixed or not?15:44
nprivalovatongli: where? in devstack?15:44
tongliyes.15:45
tongliI do not think that is specific to devstack though.15:45
silehttongli, https://review.openstack.org/#/c/70338/ this one is missing I think for CRTL+C issue15:45
nprivalovatongli: oh, I'm not alone :) Today I faced it several times with devstack-master15:45
gordctongli:  it's patched. the oslo sync code just got merged.15:46
*** lpabon has joined #openstack-meeting15:46
tongliok. good.15:46
*** jcooley_ has joined #openstack-meeting15:46
*** dcramer_ has quit IRC15:46
*** vjay has joined #openstack-meeting15:46
nprivalovado you have some bug-scrub procedure?15:47
*** Leonr has joined #openstack-meeting15:47
*** mestery has quit IRC15:47
*** mrodden has quit IRC15:47
eglynnnprivalova: ... do you mean triaging the bug queue?15:48
eglynn... or squashing the actual bugs with a concerted effort at fixing?15:48
*** aignatov is now known as aignatov_15:48
*** bgorski has quit IRC15:48
eglynn... such as a "bug-squashing day"15:48
nprivalovaI meant clean-up15:49
nprivalovaand triaging, yes15:49
tonglinova had few of these days in the past,15:49
eglynna clean-up that ends with a neater, prioritized queue ... but not necessarily with fixed bugs, right?15:49
dduttaHi I am a noob in ceilometer .... was reading code ..... any place i can help to start learning about the code?15:50
dhellmannhi, ddutta!15:50
jd__ddutta: try fixing a bug?15:50
nprivalovaand the same with bps. I just found a bug with 'Confirmed' state that was fixed half of the year ago :)15:50
dduttabtw I found a trivial typo too :) https://review.openstack.org/#/c/71431/15:50
dduttadhellmann: hi ... would love to do something here as my interests are in streaming data mining and machine learning :) ...15:51
dhellmannddutta: you've seen http://docs.openstack.org/developer/ceilometer/ right?15:52
eglynnnprivalova: ... the newer bugs seem to be traiged fairly rapidly in general, but seems like we may need to do a periodic trawl of the older ones for dupes/stales etc.15:52
dduttawill take on some simple bugs for starters to get more code and design insight ,......15:52
gordcnprivalova: which bug was that? i occasionally run through bugs to clean them up a bit... i tend to let jenkins switch bug status so i guess it missed it in this case.15:52
*** ayoung-ZzZzzZZzz is now known as ayoung15:52
dduttadhellmann: yes I started to read those15:52
*** jcooley_ has quit IRC15:53
*** fnaval has joined #openstack-meeting15:53
gordcddutta: i tend to throw breakpoints in code i'm interested in and step through... probably doesn't work for everyone but works for me.15:53
dhellmannddutta: +2 on that patch, good eye15:54
nprivalovagordc: ah, ok. it was https://bugs.launchpad.net/ceilometer/+bug/1217412 . We've changed the status15:54
uvirtbotLaunchpad bug 1217412 in ceilometer "HBase DB driver losing historical resource metadata" [Medium,Fix released]15:54
*** shakayumi has joined #openstack-meeting15:54
*** gothicmindfood has joined #openstack-meeting15:54
*** sacharya has joined #openstack-meeting15:55
*** bgorski has joined #openstack-meeting15:55
dduttadhellmann: thx .... on to the bugs now15:55
dduttagordc: good idea ....15:55
gordcnprivalova: ah, yeah. that status wasn't updated by build... i guess anyone can change the status so if you notice anything feel free to make updates.15:55
jd__time to wrap up guys15:57
jd__feel free to continue in #openstack-ceilometer :)15:57
jd__happy hacking!15:57
jd__#endmeeting15:57
*** AlexF has joined #openstack-meeting15:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:57
openstackMeeting ended Thu Feb  6 15:57:50 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ceilometer/2014/ceilometer.2014-02-06-15.00.html15:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ceilometer/2014/ceilometer.2014-02-06-15.00.txt15:57
openstackLog:            http://eavesdrop.openstack.org/meetings/ceilometer/2014/ceilometer.2014-02-06-15.00.log.html15:57
*** esker has joined #openstack-meeting15:58
*** bauzas has quit IRC15:58
*** nwidell has quit IRC15:59
*** gordc has left #openstack-meeting16:00
*** mrodden has joined #openstack-meeting16:01
*** vjay has quit IRC16:03
*** sacharya has quit IRC16:03
gothicmindfoodnot sure who is here for storyboard, but let's get to it...16:04
krotschecko/16:04
gothicmindfood#startmeeting storyboard16:04
openstackMeeting started Thu Feb  6 16:04:26 2014 UTC and is due to finish in 60 minutes.  The chair is gothicmindfood. Information about MeetBot at http://wiki.debian.org/MeetBot.16:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:04
*** openstack changes topic to " (Meeting topic: storyboard)"16:04
openstackThe meeting name has been set to 'storyboard'16:04
gothicmindfoodyay! I can do meetingbot commands.16:04
*** doug_shelley66 has quit IRC16:04
gothicmindfood#topic Current State of MVP16:05
*** openstack changes topic to "Current State of MVP (Meeting topic: storyboard)"16:05
gothicmindfoodkrotscheck: your floor16:05
krotscheckALrightey16:05
*** paragan has quit IRC16:05
krotscheckSo to I finished the first run of the UI on monday, and that's working in a no-backend state.16:05
krotscheckYesterday I got it wired up to the API.16:05
*** doug_shelley66 has joined #openstack-meeting16:06
krotscheckBoth of those WIP MVP commits work together, except both buidls are currently failing.16:06
krotscheckThe Webclient is failing because... I don't know, apparently the database credentials stopped working on the integration tests?16:06
krotscheckThe API changes are failing because I hacked that shit together as quickly as possible and it's code that should be thrown out and burned in effigy.16:07
gothicmindfooddoes anyone want to volunteer to burn krotscheck 's API code and replace it with something else?16:08
NikitaKonovalovI'll have a look at your change16:08
krotscheckOther than that, there is no auth layer, but the UI and the API can now create projects, stories, adn tasks.16:08
NikitaKonovalovAuth contorller is in progress16:09
krotscheckNice!16:09
gothicmindfoodyay!16:09
SergeyLukjanovawesome ;)16:09
NikitaKonovalovI'm just trying to launch in the most simple config with in-mem sotrage16:09
SergeyLukjanovNikitaKonovalov, I think it'll be enough for MVP016:09
NikitaKonovalovit should be16:09
SergeyLukjanovthe diff is that non in-memory storage will just not logout all users after restart16:10
krotscheckALso, the tasks API doesn't actually seem to save titles.16:10
krotscheckAnd the data model doesn't have a description either.16:10
*** bgorski_ has joined #openstack-meeting16:10
NikitaKonovalovthe migration with an additional field should cure the problem16:10
krotscheckIn case anyone is curious, the non-api client is here: http://docs-draft.openstack.org/97/70897/1/check/gate-storyboard-webclient-js-unittests/32bcc1d/dist/#!/16:11
* krotscheck cedes the floor to NikitaKonovalov 16:11
*** andreaf2 has joined #openstack-meeting16:12
*** jaypipes has quit IRC16:12
*** bgorski has quit IRC16:12
*** elo1 has joined #openstack-meeting16:12
NikitaKonovalovhmm, the link above is a blank page for me16:12
*** andreaf has quit IRC16:12
* gothicmindfood loves the non-api client and thinks it's nice looking16:12
gothicmindfoodit's not blank for me.16:13
krotscheckNikitaKonovalov: Ehh? Whaa? anything interesting showing up in the console?16:13
*** jmontemayor has joined #openstack-meeting16:13
NikitaKonovalovnow it's ok16:13
NikitaKonovalovthere was a tim-out, but 10 page refreshes and it's working16:14
gothicmindfoodNikitaKonovalov: anything you want to cover re: auth or the api?16:14
*** jmontemayor has quit IRC16:14
*** shakayumi has quit IRC16:14
*** jmontemayor has joined #openstack-meeting16:15
NikitaKonovalovEverything is clear for me right now16:15
*** boris-42_ has joined #openstack-meeting16:15
NikitaKonovalovso implementation should not take very long16:15
*** thuc has joined #openstack-meeting16:15
*** shanks has quit IRC16:16
gothicmindfoodNikitaKonovalov and SergeyLukjanov - also, did you guys see the auth specs krotscheck and I wrote out at http://etherpad.openstack.org/p/StoryboardAuth ?16:16
*** akuznetsov has quit IRC16:16
*** thuc_ has joined #openstack-meeting16:16
SergeyLukjanovgothicmindfood, not yes16:16
SergeyLukjanovgothicmindfood, not yet*16:16
SergeyLukjanovgothicmindfood, I'll take a look on it tomorrow16:17
gothicmindfoodOk - not a problem. Feel free to get in there and edit it, too, SergeyLukjanov - we just wanted to do a krotscheck brain dump before he went to Thailand and abandoned us all :)16:17
*** salv-orlando has joined #openstack-meeting16:18
*** mestery has joined #openstack-meeting16:18
*** ildikov_ has quit IRC16:18
krotscheckI'm not abandoning you!16:18
*** vkmc has quit IRC16:18
* gothicmindfood kids krotscheck 16:19
gothicmindfoodok16:19
jeblairol16:19
*** dklyle has joined #openstack-meeting16:19
gothicmindfooddo we have anything else we need to cover re: current state of MVP?16:19
gothicmindfoodjeblair: hi!16:19
jeblairsorry i'm late, anything i can help out with?16:19
SergeyLukjanovjeblair, o/16:19
*** thuc has quit IRC16:20
ilyashakhatda5xTYr16:20
* jeblair reviews auth stories16:20
NikitaKonovalovI've started a few patches to introduce some functional tests16:21
*** jjmb has quit IRC16:21
*** shanks has joined #openstack-meeting16:21
ilyashakhatoops :) my test env pwd16:21
jeblairkrotscheck: can you link to the review for the change that's failing database tests?16:21
SergeyLukjanovilyashakhat, just c-p your private key here ;)16:22
NikitaKonovalovthe were stuck with a virtualenv release or smt. like that16:22
ilyashakhatno way!16:22
krotscheckjeblair: http://logs.openstack.org/97/70897/2/check/gate-storyboard-webclient-js-unittests/7e35c1d/console.html16:22
*** david_lyle_ has quit IRC16:22
krotscheckhttps://review.openstack.org/#/c/70897/16:23
NikitaKonovalovruhe now tries to make them work with new depencies' versions16:23
*** jprovazn is now known as jprovazn_afk16:23
jeblairkrotscheck: we changed some slave configuration recently.  i don't know if that's the cause but i'll look into it16:23
krotscheckjeblair: That would make sense.16:24
jeblairkrotscheck: when are you back from vacation?16:24
gothicmindfood#action jeblair to look into db test failure16:25
* gothicmindfood fails at meeting commands apparently16:25
jeblairgothicmindfood: i believe that was correct16:26
*** salv-orlando has quit IRC16:26
krotscheckjeblair, The 24th16:26
gothicmindfoodjeblair: oh yay. I thought it'd echo back to us all.16:26
* ttx joins late16:26
jeblairgothicmindfood: link and action are quiet16:26
* krotscheck will have reception, but no laptop.16:26
* ttx reads backlog16:26
jeblair#link http://logs.openstack.org/97/70897/2/check/gate-storyboard-webclient-js-unittests/7e35c1d/console.html16:26
gothicmindfoodttx: hi there!16:26
jeblair#link https://review.openstack.org/#/c/70897/16:26
gothicmindfoodAny other comments on MVP current state before we go to open discussion?16:27
gothicmindfoodoooh, also...  #link https://etherpad.openstack.org/p/StoryboardAuth16:28
jeblair#link https://etherpad.openstack.org/p/StoryboardAuth16:28
gothicmindfoodjeblair: you owe me a coke.16:28
*** akuznetsov has joined #openstack-meeting16:29
*** zhiyan has quit IRC16:29
krotscheckOh, one.16:29
jeblair(commands have to start lines, and i have a crate of mexi-cokes here; one has your name on it)16:29
krotscheckI threw some post-MVP api design thougths here: https://etherpad.openstack.org/p/StoryboardAPIPaging16:29
*** jcooley_ has joined #openstack-meeting16:30
gothicmindfood#link https://etherpad.openstack.org/p/StoryboardAPIPaging16:31
ttxkrotscheck: would be good to look at how other openstack project do pagination / limit / offset querying16:31
ttxunless your preference for option 2 is string16:31
ttxor strong16:31
NikitaKonovalovwhatever we choose, pecan will handle both, but headers look better to me16:32
*** bauzas has joined #openstack-meeting16:33
gothicmindfoodttx: any particular projects that might stand out over others as being better at the pagination thing?16:33
gothicmindfood(in case of a lack of standards)16:33
SergeyLukjanovI'm agreed with headers, it'll not clutter up API body16:33
krotscheckttx: Yeah, I took a look at what Ironic was doing. There's some philosophically strong adherence to REST semantics there that I feel is overly pedantic, but they just return a plain array16:33
ttxgothicmindfood: I wouldn't dare saying one is better16:33
gothicmindfoodttx: smart man. :)16:33
ttxbut I remember a lot of endless discussions about it in Glance16:34
NikitaKonovalovand aifik, horizon does pagination via setting some kind of a separator id16:34
*** salv-orlando has joined #openstack-meeting16:34
krotscheck#link http://git.openstack.org/cgit/openstack/ironic/tree/ironic/api/controllers/v1/node.py#n48016:34
NikitaKonovalovand the maximum page size is kept in some settings field16:34
krotscheckFor example, they use "marker" instead of "offset"16:34
*** ArthurBerezin has quit IRC16:34
krotscheckFeels like "what everyone else is doing" doesn't agree with each other16:34
jeblairkrotscheck: i've seen that with a few api servers, it may be the most common method with openstack16:35
jeblair(the 'marker' idea)16:35
*** sacharya has joined #openstack-meeting16:36
krotscheckjeblair: Yeah, naming is just semantics. I find it more interesting that there doesn't seem to be a way for the API  to respond with "oh by the way I have this much"16:37
*** dklyle is now known as david-lyle16:37
*** sparkycollier has joined #openstack-meeting16:37
david-lyleHorizon uses marker because that's what the underlying APIs support16:37
david-lyleit provides that most limited form of pagination imaginable16:38
david-lyleif you own the API aim higher16:38
*** dvarga is now known as dvarga|away16:40
*** dvarga|away is now known as dvarga16:40
gothicmindfoodthanks, david-lyle - anyone else have thoughts on that?16:40
*** pablosan has quit IRC16:41
jeblaircool.  i don't think we have to limit ourselves to what openstack is doing elsewhere, just that we should consider it, use it if it makes no difference; if it does make a difference, do whatever we think best but be informed about it.16:41
krotscheckPagination really only requires three things. A marker, an record limit, and some understanding of how large the paged data set is.16:41
*** pablosan has joined #openstack-meeting16:41
david-lyleThe argument for the marker scheme from the services has been performance related16:41
*** sdake has quit IRC16:41
*** amrith has quit IRC16:42
krotscheckdavid-lyle: Marker is also a very useful metaphor because it doesn't care about RDB vs NoSQL16:42
*** thomasbiege1 has joined #openstack-meeting16:42
david-lyleyes, and the page-limit is supported, it's the set size that doesn't come back16:42
krotscheckdavid-lyle: So your API returns just a plain array of results?16:43
david-lyleso you can keep clicking next, but have no idea that there are 10,000 more clicks to get to the end16:43
*** ArthurBerezin has joined #openstack-meeting16:43
*** thomasbiege has quit IRC16:43
david-lylejust the number of results we request, or the API defined limit16:43
krotscheckRight.16:43
*** sudorandom has joined #openstack-meeting16:44
david-lylewe grab the last ID as the marker and go from there16:44
*** mestery has quit IRC16:44
krotscheckdavid-lyle: Makes sense.16:44
david-lylebut there is no call to get total number of records available, nor is it returned16:45
ttxgothicmindfood: at some point we need to have some brainstorming around priorities. Talking to jeblair about it last weekend helped me structure my thoughts16:45
*** ArthurBerezin has left #openstack-meeting16:45
gothicmindfoodttx: agreed. shall we space some time out for that in the next meeting, or try to schedule something separately?16:46
krotscheckdavid-lyle: I was thinking of having a custom header added to the HTTP response to include the response size (once we have a large enough data set where that matters)16:47
ttxgothicmindfood: we could try a phone call as a first step. I rant better using phones16:47
gothicmindfoodalso, I think if we're close to finishing API and pagination, we can move topics.16:47
gothicmindfood#topic open discussion16:47
*** openstack changes topic to "open discussion (Meeting topic: storyboard)"16:47
krotscheckseems like a better idea than modifying the returned data structure.16:47
ttxgothicmindfood: I expect you'll have to colect a variety of opinions around that topic and see if there is a convergent solution16:47
krotscheckkk16:47
krotscheckOk, I'm out.16:47
jeblairi'm wondering about site customization.  i imagine deployers would like to use custom logos, headers, footers, and css.  how should that be handled?  i'm particularly unsure about how that sort of thing should work with a fully-client-side js app.16:47
jeblairit is build time or run time customization?  does the app fetch some config json from the server with that info?  or...?16:47
gothicmindfoodkrotscheck: HAVE SO MUCH FUN.16:47
jeblairoh, and that was a question for krotscheck.  oh well.16:47
krotscheckjeblair: Replace Bootstrap.js. Done.16:48
krotschecksorry16:48
krotscheckbootstrap.css16:48
david-lylekrotscheck: just?16:48
jeblairkrotscheck: cool, that's enough to help me understand the mechanism.  thanks and have fun.16:48
*** bdpayne has joined #openstack-meeting16:49
krotscheckjeblair: I have some ideas on a customization path for the UI.16:49
krotscheckjeblair: Maybe we can put that on the agenda post-mvp?16:49
ruhejeblair: mordred: could you please help me to find why docs aren't uploaded to http://ci.openstack.org/storyboard ?16:50
krotscheckToodles. Thanks, gothicmindfood !16:50
*** krotscheck has quit IRC16:50
*** gyee has joined #openstack-meeting16:50
gothicmindfood#action gothicmindfood to meet with ttx to start talking about post-MVP priorities16:51
*** vijendar has quit IRC16:51
jeblairruhe: definitely16:51
gothicmindfoodanything else for open discussion time?16:52
*** jcoufal has quit IRC16:52
ruhejeblair: i think we have everything needed in zuul (and mordred confirmed that during the sprint). but somehow post jenkins jobs were never executed16:52
jeblairruhe: ok16:53
*** lsmola has quit IRC16:53
*** jtomasek has quit IRC16:54
*** dcramer_ has joined #openstack-meeting16:54
*** DeeJay1 has quit IRC16:55
ruheand just a status update from side: i help Nikita to build testing infrastructure for Pecan+SQLA+Alembic; once that is done we will be in 0.5 step away from MVP16:55
ttxgothicmindfood: nope16:55
*** jjmb has joined #openstack-meeting16:55
*** sudorandom has quit IRC16:55
*** jjmb has quit IRC16:55
gothicmindfoodawesome, ruhe16:55
gothicmindfoodok16:55
*** hemna has joined #openstack-meeting16:55
gothicmindfood#endmeeting16:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:56
openstackMeeting ended Thu Feb  6 16:56:18 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2014/storyboard.2014-02-06-16.04.html16:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2014/storyboard.2014-02-06-16.04.txt16:56
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2014/storyboard.2014-02-06-16.04.log.html16:56
*** julienvey has quit IRC16:56
gothicmindfoodthanks everyone16:56
*** sudorandom has joined #openstack-meeting16:56
gothicmindfoodsee you next week!16:56
*** mestery has joined #openstack-meeting16:56
*** jcooley_ has quit IRC16:56
*** jcooley_ has joined #openstack-meeting16:57
*** NikitaKonovalov is now known as NikitaKonovalov_16:58
*** sparkycollier has quit IRC16:59
*** sbalukoff has quit IRC17:00
*** jmontemayor has quit IRC17:00
*** jmontemayor has joined #openstack-meeting17:00
*** emagana has joined #openstack-meeting17:01
*** MaxV has quit IRC17:02
*** rajdeep has joined #openstack-meeting17:02
*** sarob has joined #openstack-meeting17:02
*** akuznetsov has quit IRC17:02
*** MaxV has joined #openstack-meeting17:02
*** jlibosva has quit IRC17:03
*** TravT has joined #openstack-meeting17:04
*** egallen has quit IRC17:04
*** DinaBelova is now known as DinaBelova_17:04
*** lcheng_ has joined #openstack-meeting17:06
*** yassine_ has quit IRC17:06
*** egallen has joined #openstack-meeting17:06
*** MaxV has quit IRC17:07
*** jlibosva has joined #openstack-meeting17:07
*** sarob has quit IRC17:07
*** kiall has quit IRC17:08
*** GheRivero has quit IRC17:09
*** sdake has joined #openstack-meeting17:09
*** sdake has quit IRC17:09
*** sdake has joined #openstack-meeting17:09
*** rajdeep has quit IRC17:11
*** jecarey has quit IRC17:13
*** markmcclain has joined #openstack-meeting17:15
*** evgenyf has quit IRC17:18
*** mst89 has joined #openstack-meeting17:19
*** dripton is now known as dripton_lunch17:20
*** markwash has joined #openstack-meeting17:21
*** I159 has quit IRC17:21
*** Fdot has quit IRC17:21
*** giulivo has joined #openstack-meeting17:23
*** mst89 has quit IRC17:23
*** SridarK has quit IRC17:23
*** patelna has joined #openstack-meeting17:25
*** markwash has quit IRC17:26
*** comay has joined #openstack-meeting17:26
*** ashepelev1 has joined #openstack-meeting17:26
*** marcoemorais has joined #openstack-meeting17:27
*** doug_shelley66 has quit IRC17:27
*** ashepelev1 has quit IRC17:29
*** _nadya_ has joined #openstack-meeting17:29
*** cdub has joined #openstack-meeting17:33
*** marekd is now known as marekd|away17:36
*** DinaBelova_ is now known as DinaBelova17:37
*** ash|2 has joined #openstack-meeting17:37
*** doug_shelley66 has joined #openstack-meeting17:37
*** salv-orlando has quit IRC17:38
*** julim has quit IRC17:38
*** bpb has joined #openstack-meeting17:39
*** shanks has quit IRC17:40
*** jcooley_ has quit IRC17:41
*** jcooley_ has joined #openstack-meeting17:42
*** vijendar has joined #openstack-meeting17:42
*** mdbooth has quit IRC17:42
*** AlexF has quit IRC17:42
*** akuznetsov has joined #openstack-meeting17:42
*** shanks has joined #openstack-meeting17:44
*** tristanC has joined #openstack-meeting17:46
*** ygbo has quit IRC17:46
*** jjmb has joined #openstack-meeting17:46
*** dvarga is now known as dvarga|away17:46
*** dvarga|away is now known as dvarga17:46
*** egallen has quit IRC17:47
*** Invent has quit IRC17:47
*** Invent has joined #openstack-meeting17:47
*** MaxV has joined #openstack-meeting17:47
*** jecarey has joined #openstack-meeting17:48
*** esmute has joined #openstack-meeting17:50
*** SumitNaiksatam has quit IRC17:51
*** mrodden has quit IRC17:52
*** _nadya_ has quit IRC17:52
*** aignatov_ is now known as aignatov17:53
*** lisaclark1 has quit IRC17:53
*** nati_ueno has joined #openstack-meeting17:54
*** mrodden has joined #openstack-meeting17:55
*** rossk has joined #openstack-meeting17:55
*** markwash has joined #openstack-meeting17:56
*** AlexF has joined #openstack-meeting17:56
*** belmoreira has quit IRC17:56
*** jmontemayor has quit IRC17:57
*** shohel has joined #openstack-meeting17:57
*** shanks has quit IRC17:58
*** Gordonz has joined #openstack-meeting17:58
*** rossella_s has quit IRC17:58
*** harlowja_away is now known as harlowja17:59
bdpayne#startmeeting OpenStack Security Group18:00
openstackMeeting started Thu Feb  6 18:00:02 2014 UTC and is due to finish in 60 minutes.  The chair is bdpayne. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: OpenStack Security Group)"18:00
openstackThe meeting name has been set to 'openstack_security_group'18:00
bdpaynehi everyone18:00
*** david_lyle_ has joined #openstack-meeting18:00
bdpayne#topic Role Call18:00
*** openstack changes topic to "Role Call (Meeting topic: OpenStack Security Group)"18:00
bdpayneo/18:00
mkoderero/18:00
shohelo/18:00
*** Gordonz has quit IRC18:01
*** sc68cal_ has joined #openstack-meeting18:01
*** davidhadas_ has joined #openstack-meeting18:01
bdpayneok, I'm sure that others will join in shortly18:01
bdpayne#topic Agenda18:01
*** openstack changes topic to "Agenda (Meeting topic: OpenStack Security Group)"18:01
bdpayneI've been chatting with some people who are interested in discussing security testing this week18:01
bdpayneI have a brief update from the book editors18:02
*** safchain has quit IRC18:02
*** derekh has quit IRC18:02
*** jmontemayor has joined #openstack-meeting18:02
bdpayneAnything else to discuss?18:02
*** julienvey has joined #openstack-meeting18:02
*** david-lyle has quit IRC18:02
ash|2Hello everyone. Execuse me please...18:02
mkodererfuzzy testing framework18:02
*** davidhadas has quit IRC18:02
bdpaynegreat, yes we'll discus the fuzzing testing ideas18:03
*** fbo is now known as fbo_away18:03
*** malini1 has joined #openstack-meeting18:03
*** sarob has joined #openstack-meeting18:03
*** cdub has quit IRC18:03
*** Gordonz has joined #openstack-meeting18:04
bdpayneok, let's get started18:04
bdpayne#topic Security Testing and Fuzzing Testing18:04
*** openstack changes topic to "Security Testing and Fuzzing Testing (Meeting topic: OpenStack Security Group)"18:04
*** lmcmpou has joined #openstack-meeting18:04
bdpaynemkoderer would you like to introduce what it is that you are working on?18:04
mkodereryep18:04
mkodererI am currently working on a framework to generate negative tests in Tempest18:05
mkodererthis framework generates these test out of json schemas18:05
ash|2I'm not a developer of Openstack, but I find it very usefull to write here. I'm a student and looking forward for participating in GSoC2014 with OpenStack. I have already found a mentor (Debojyoti Dutta) and we are looking forward for find anyone who could organize this (the administrator). Excuse me - I found it usefull to write here.18:05
*** eglynn has quit IRC18:06
mkodererthe idea is that I want to discuss is that it would be quite easy to use this for fuzzy testing18:06
*** amcrn has joined #openstack-meeting18:06
mkodererin Tempest we have already stress tests that can run any Tempest test with a certain number of workers18:06
bdpaynecan you expand what you're doing with the negative tests more specifically?18:07
mkodererbdpayne: sure18:07
*** bauzas has quit IRC18:07
*** gothicmindfood has left #openstack-meeting18:07
*** paulmo has joined #openstack-meeting18:07
*** sarob has quit IRC18:07
mkodererI think when it comes to security testing we need to change somehow the design18:08
*** shanks has joined #openstack-meeting18:08
hyakuheiSorry, here late.18:08
*** NikitaKonovalov_ is now known as NikitaKonovalov18:08
mkoderermy question.. is already somebody working on this topic?18:08
*** dripton_lunch is now known as dripton18:08
*** sankarshan has quit IRC18:08
*** sankarshan has joined #openstack-meeting18:08
hyakuheimkoderer: what sort of tests? are there example json schema's out there for review?18:09
bdpayneso there were some people talking about this last fall18:09
*** DinaBelova is now known as DinaBelova_18:09
mkodererhyakuhei: https://review.openstack.org/#/c/64733/18:09
bdpayneI asked thomas from suse to join us today... not sure if he is here yet18:09
mkodererthere are 3 json files in it as example18:09
*** marcoemorais has quit IRC18:10
mkodererbdpayne: ok I saw his blog post about fuzzy testing18:10
bdpaynemkoderer so you may be the one working on this at this point :-)18:11
bdpaynebut we can help18:11
*** armax has joined #openstack-meeting18:11
bdpayneyou said that things need to change for security testing18:11
bdpaynewhat specific work do you believe needs to happen here?18:11
bdpayneand what kind of security testing did you have in mind?18:11
*** DinaBelova_ is now known as DinaBelova18:11
*** johnthetubaguy has quit IRC18:11
mkodererbdpayne: I mean the focus is slightly different as for negative testing18:12
*** shanks has quit IRC18:12
mkoderercurrently all negative test simply execute and prove if the result value is corect18:12
mkodererI don't think that we need this.. we could simply fire a lot of records and after that have a look if everything is running18:13
malini1mkoderer: do you mean like DOS18:14
*** beyounn has joined #openstack-meeting18:14
mkoderermalini1: yep possibly18:14
mkodererok let me finish my negative testing blueprint and I will propose a patch and we could discuss it here18:15
tristanCmkoderer: I am curious, are input generated purely randomly or is there some kind of intrumentation ? and also do you think it can also be used to find issues other than service dos ?18:15
*** sarob has joined #openstack-meeting18:15
malini1mkoderer: I like that .. it would also be a stress/performance test then, if we say n records, 2n 4n records etc to see when things break down18:15
mkoderertristanC: currently the negative testing is not really random.. if a integer value is needed it sends a predefined string18:16
mkoderertristanC: but it my plan that I add a lot of generator with different random generators18:16
mkoderermalini1: a stress job is already running every night in tempest18:17
mkoderermalini1: but only with usual test cases18:17
*** mst89 has joined #openstack-meeting18:17
tristanCmkoderer: oh ok. well it's a good idea (fuzzing OS) imo18:17
*** NikitaKonovalov is now known as NikitaKonovalov_18:17
mkodererok cool18:17
*** shanks has joined #openstack-meeting18:18
*** arnaud___ has joined #openstack-meeting18:18
*** arnaud__ has joined #openstack-meeting18:18
*** lcheng_ has quit IRC18:19
malini1mkoderer: IMHO -- if you detect a negative test that brings down the system, after analysis -- it should be added into regular test suite .. reason: random tests sometimes do not reoccur as easily18:19
*** sarob has quit IRC18:20
*** IlyaE has joined #openstack-meeting18:20
*** Duane_ has joined #openstack-meeting18:20
mkoderermalini1: yes I think the tricky part will be the analysis18:20
*** amrith has joined #openstack-meeting18:20
*** mestery has quit IRC18:20
bdpaynesounds like the next step here is for mkoderer to finish putting together a blueprint18:20
bdpaynethen we can discuss that as a more concerete set of ideas?18:21
mkodererbdpayne: yes sure18:21
bdpaynegreat, thanks18:21
*** jcooley_ has quit IRC18:21
bdpayneplease use the mailing list to let us know when that is available18:21
bdpayneand feel free to come back here to discuss more at future meetings, too18:21
bdpayneany other thoughts on the testing stuff for today?18:21
*** NikitaKonovalov_ is now known as NikitaKonovalov18:21
*** ddutta has quit IRC18:22
*** morganfainberg_Z is now known as morganfainberg18:22
bdpayne#topic General Updates18:22
*** openstack changes topic to "General Updates (Meeting topic: OpenStack Security Group)"18:22
bdpayneSo I have a few quite updates to pass along18:22
bdpayneI spoke with the book editor team briefly18:22
*** DinaBelova is now known as DinaBelova_18:23
bdpaynesounds like they are all planning to move forward, but simply have not yet18:23
*** david_lyle_ is now known as david_lyle18:23
bdpayneso we'll stay tuned there18:23
bdpaynewe also do have some open tickets related to the book18:23
*** Yathi has joined #openstack-meeting18:23
bknudsondo the edits go through gerrit review?18:23
bdpaynetickets to fix some wordings18:23
*** AlexF has quit IRC18:23
bdpayneyeah, they go through gerrit18:23
bdpayneand get reviewed by the doc team18:23
*** GheRivero has joined #openstack-meeting18:23
bknudsonjust wonder if they'll need help reviewing18:23
bdpayneso if anyone is interested in working on some book edits, let me know18:23
bdpaynewhen we get to that point, they will18:24
bdpayneI can send out some emails at that time18:24
malini1bdpayne: where are the tickets, i would like to work on it18:24
*** SumitNaiksatam has joined #openstack-meeting18:24
bknudsonbdpayne: thanks18:24
malini1i have been meaning to put in the glossary references and this will be a good entry point18:24
bdpayneI'm also tracking several private security related bugs atm, which all appear to be tracking towards creating OSSNs18:24
bdpaynemalini1 I will find the tickets, one sec18:25
bdpayneso just a heads up that the OSSN authors should have their pens ready ;-)18:25
bdpayneTickets: https://bugs.launchpad.net/horizon/+bug/1118194 and https://bugs.launchpad.net/openstack-manuals/+bug/124353418:26
uvirtbotLaunchpad bug 1118194 in openstack-manuals "Security Documentation for Horizon" [Wishlist,Confirmed]18:26
malini1:-)18:26
bdpayneThe Horizon stuff might be best addressed by someone here at Nebula that wrote the initial section there18:26
bdpaynebut the other one is good to dive into if you want18:26
annegentlebdpayne: nice :)18:26
malini1sounds good, i shall take the other one18:27
bdpayneannegentle I may be slow, but I do get there eventually :-)18:27
bdpayneok, and one final note for this week...18:27
annegentlebdpayne: who's your book editor?18:27
*** jlibosva1 has joined #openstack-meeting18:27
* annegentle can be slow too18:27
*** sushil_ has quit IRC18:27
*** changbl has joined #openstack-meeting18:27
bdpayneSeveral OSSG members will be at RSA in San Francisco at the end of the month18:27
bdpayneif anyone else is planning to come and would like to meet up, just drop me a line18:28
bdpayneannegentle The book editors are Sriram Subramanian, David Mortman, and Ben de Bont18:28
bdpayneok, that's all that I have for today18:28
annegentlebdpayne: oh are they doing review passes?18:28
*** rakhmerov has quit IRC18:29
bdpayneyeah they are trying to improve the clarity and make it a common voice, etc18:29
bdpaynealso identify areas that need more technical work18:29
annegentlebdpayne: nice, that is super helpful18:29
*** jlibosva has quit IRC18:29
bdpaynethanks everyone... have a great week!18:29
bdpayne#endmeeting18:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:30
openstackMeeting ended Thu Feb  6 18:30:00 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_security_group/2014/openstack_security_group.2014-02-06-18.00.html18:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_security_group/2014/openstack_security_group.2014-02-06-18.00.txt18:30
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_security_group/2014/openstack_security_group.2014-02-06-18.00.log.html18:30
*** miarmak has quit IRC18:30
*** lmcmpou has quit IRC18:31
*** dvarga is now known as dvarga|away18:33
*** dvarga|away is now known as dvarga18:33
*** paulmo has left #openstack-meeting18:33
*** mdurnosvistov_ has joined #openstack-meeting18:33
*** tristanC has left #openstack-meeting18:34
*** shohel has quit IRC18:34
*** sushils has joined #openstack-meeting18:34
*** julienvey has quit IRC18:35
*** julienvey has joined #openstack-meeting18:35
*** sankarshan has quit IRC18:36
*** sankarshan has joined #openstack-meeting18:36
*** akuznetsov has quit IRC18:37
*** ndipanov is now known as ndipanov_gone18:37
*** Yathi has quit IRC18:37
*** igor has quit IRC18:40
*** mestery has joined #openstack-meeting18:41
*** troytoman-away is now known as troytoman18:41
*** jjmb1 has joined #openstack-meeting18:42
*** jjmb has quit IRC18:43
*** igor has joined #openstack-meeting18:44
*** spzala has quit IRC18:44
*** beyounn has quit IRC18:45
*** NikitaKonovalov is now known as NikitaKonovalov_18:45
*** gokrokve has joined #openstack-meeting18:46
*** ArxCruz has quit IRC18:47
*** ArxCruz has joined #openstack-meeting18:47
*** eglynn has joined #openstack-meeting18:47
*** marcoemorais has joined #openstack-meeting18:48
*** jprovazn_afk has quit IRC18:50
*** Gordonz has quit IRC18:50
*** NikitaKonovalov_ is now known as NikitaKonovalov18:51
*** eglynn has quit IRC18:51
*** nacim has quit IRC18:53
*** lisaclark1 has joined #openstack-meeting18:54
*** lcheng_ has joined #openstack-meeting18:55
*** tanisdl has quit IRC18:55
*** sbalukoff has joined #openstack-meeting18:55
*** bgorski_ has quit IRC18:58
*** jcooley_ has joined #openstack-meeting18:58
*** emagana has quit IRC18:58
*** ruhe_ has joined #openstack-meeting18:59
*** troytoman is now known as troytoman-away19:00
*** krtaylor has quit IRC19:01
thomasbiege1hi19:01
*** Gordonz_ has joined #openstack-meeting19:01
*** lisaclark1 has quit IRC19:01
*** malini1 has quit IRC19:01
*** rakhmerov has joined #openstack-meeting19:02
*** balajiiyer has joined #openstack-meeting19:02
*** rakhmerov has joined #openstack-meeting19:02
*** IanGovett has joined #openstack-meeting19:03
*** giulivo has left #openstack-meeting19:03
*** IanGovett1 has quit IRC19:03
*** ddutta has joined #openstack-meeting19:04
*** balajiiyer1 has joined #openstack-meeting19:05
*** balajiiyer has quit IRC19:07
*** Gordonz_ has quit IRC19:07
*** Gordonz has joined #openstack-meeting19:07
*** epim has joined #openstack-meeting19:08
*** NikitaKonovalov is now known as NikitaKonovalov_19:09
*** Gordonz has quit IRC19:12
*** spzala has joined #openstack-meeting19:14
*** DinaBelova_ is now known as DinaBelova19:14
*** NikitaKonovalov_ is now known as NikitaKonovalov19:15
*** lisaclark1 has joined #openstack-meeting19:17
*** mestery has quit IRC19:19
*** ftcjeff has quit IRC19:19
*** ftcjeff has joined #openstack-meeting19:19
*** jwalls has joined #openstack-meeting19:20
*** ftcjeff has quit IRC19:20
*** NikitaKonovalov is now known as NikitaKonovalov_19:23
*** kiall has joined #openstack-meeting19:24
*** dvarga is now known as dvarga|away19:27
*** dvarga|away is now known as dvarga19:27
*** ruhe_ has quit IRC19:27
*** spzala has quit IRC19:28
*** NikitaKonovalov_ is now known as NikitaKonovalov19:28
*** spzala has joined #openstack-meeting19:29
*** pnavarro has quit IRC19:30
*** sarob has joined #openstack-meeting19:30
*** malini1 has joined #openstack-meeting19:31
*** tanisdl has joined #openstack-meeting19:31
*** Yathi has joined #openstack-meeting19:32
*** mrodden has quit IRC19:32
*** NikitaKonovalov is now known as NikitaKonovalov_19:32
*** ddutta has quit IRC19:32
*** jjmb1 has quit IRC19:34
*** jcooley_ has quit IRC19:35
*** bdpayne has quit IRC19:36
*** jcooley_ has joined #openstack-meeting19:36
*** gokrokve has quit IRC19:36
*** Gordonz has joined #openstack-meeting19:37
*** NikitaKonovalov_ is now known as NikitaKonovalov19:38
*** NikitaKonovalov is now known as NikitaKonovalov_19:39
*** jcooley_ has quit IRC19:40
*** jcooley_ has joined #openstack-meeting19:41
*** novas0x2a|laptop has joined #openstack-meeting19:42
*** bdpayne has joined #openstack-meeting19:42
*** mrodden has joined #openstack-meeting19:44
*** sarob has quit IRC19:44
*** jcooley_ has quit IRC19:45
*** markmcclain has quit IRC19:45
*** sarob has joined #openstack-meeting19:45
*** markmcclain has joined #openstack-meeting19:45
*** thomasbiege1 has quit IRC19:45
*** thomasbiege has joined #openstack-meeting19:46
*** jlibosva1 has quit IRC19:47
*** Invent has quit IRC19:47
*** beyounn has joined #openstack-meeting19:48
*** d0ugal has quit IRC19:49
*** zhiyan has joined #openstack-meeting19:49
*** jcooley_ has joined #openstack-meeting19:50
*** lblanchard has quit IRC19:52
*** torgomatic has left #openstack-meeting19:52
*** sarob has quit IRC19:54
*** sarob has joined #openstack-meeting19:54
*** emagana has joined #openstack-meeting19:54
*** ccrouch has joined #openstack-meeting19:55
*** aignatov is now known as aignatov_19:56
*** jcooley_ has quit IRC19:56
*** jwalls has quit IRC19:57
*** ftcjeff has joined #openstack-meeting19:57
*** ladquin has joined #openstack-meeting19:57
*** jcooley_ has joined #openstack-meeting19:57
*** sarob has quit IRC19:59
*** lpabon has quit IRC19:59
*** ativelkov has joined #openstack-meeting20:00
harlowja#startmeeting openstack-state-management20:01
openstackMeeting started Thu Feb  6 20:01:16 2014 UTC and is due to finish in 60 minutes.  The chair is harlowja. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
*** brianr is now known as rosmaita20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: openstack-state-management)"20:01
openstackThe meeting name has been set to 'openstack_state_management'20:01
harlowja#link https://wiki.openstack.org/wiki/Meetings/StateManagement#Agenda_for_next_meeting20:01
harlowjaanyone around today (if not, short meeting, ha)20:01
*** iv_m has joined #openstack-meeting20:02
iv_mhi there20:02
harlowjaiv_m howdy20:02
* harlowja waits a few minutes for others20:03
*** lcheng_ has quit IRC20:03
*** jmontemayor has quit IRC20:04
harlowjaok, guess might be short meeting20:04
harlowjahaha20:04
harlowja#topic last-action-items20:04
*** openstack changes topic to "last-action-items (Meeting topic: openstack-state-management)"20:04
harlowja#link http://eavesdrop.openstack.org/meetings/state_management/2014/state_management.2014-01-30-20.00.html20:04
*** HenryG_ has quit IRC20:04
*** glange has left #openstack-meeting20:04
harlowjaso oslo transition will happen this weekend, or early next week20:05
*** HenryG_ has joined #openstack-meeting20:05
harlowjait will mean reviews will have to be reposted20:05
dhellmannscheduled for 20:00 UTC tomorrow20:05
*** HenryG_ has quit IRC20:05
harlowjathx dhellmann20:05
*** rfolco has quit IRC20:05
*** ashwini has joined #openstack-meeting20:05
*** ashwini has left #openstack-meeting20:05
harlowjahopefully thats not to much of a pain, but just something to be aware of (likely involving adding a new git remote...)20:06
*** HenryG has joined #openstack-meeting20:06
*** lcheng_ has joined #openstack-meeting20:06
harlowjaiv_m any progress on the writeup for reversion/retry strategies?20:07
*** ativelkov has left #openstack-meeting20:07
iv_mnot yet, sorry20:07
harlowjanp20:07
harlowjak, not many other action items20:08
harlowja#topic taskflow 0.1.320:08
*** openstack changes topic to "taskflow 0.1.3 (Meeting topic: openstack-state-management)"20:08
*** Invent has joined #openstack-meeting20:08
harlowjaso the reason for this is a unicode problem in 0.1.220:08
changblhey guys20:08
harlowjahi changbl20:08
harlowja#link https://etherpad.openstack.org/p/TaskFlow-0.1.320:09
*** _nadya_ has joined #openstack-meeting20:09
harlowjai think we are ok to release that20:09
iv_mya20:09
iv_mlooks like we are ready20:09
changblgreat20:09
harlowjak, i'll do that shortly20:09
harlowjaafter meeting /lunch20:09
harlowjathen i think 2.0 we can merge in after move to oslo20:09
harlowja0.220:09
harlowjanot 2.0, lol20:09
changbl2.0 :)20:10
*** bauzas has joined #openstack-meeting20:10
harlowjaoops20:10
harlowjaif we adopt the firefox/chrome versioning scheme we should be at 10.0 already ,lol20:10
harlowjai was also thinking about a 0.1.3 tag and a stable/0.1 branch?20:11
*** Yathi has quit IRC20:11
harlowjajust incase this happens again :-P20:11
harlowjasince after 0.2 code starts coming in, not gonna be easy to do small releases of 0.120:11
harlowja*if we need to20:11
iv_mi think we should choose lazy approach and branch it when that happens again, if ever20:11
harlowjaok20:11
harlowjai'm fine with that to20:12
*** jmontemayor has joined #openstack-meeting20:12
*** jcooley_ has quit IRC20:12
*** akarpinska1 has joined #openstack-meeting20:12
akarpinska1hi20:12
*** jcooley_ has joined #openstack-meeting20:12
iv_malso, we might want to enforce some policy for bugfixes -- to know for sure what needs to be backported for stable branch when/if we make one20:12
harlowjak, after https://review.openstack.org/#/c/71362/ goes into the incubator, we can use that instead of our mini-version20:12
harlowjaiv_m sure, what where u thinking?20:13
harlowjahi akarpinska120:13
iv_mi was thinking of smth like '-1 all real bugfixes unless there is launchpad bug and it is reffered from commit message'20:13
harlowjai was hoping stable would just be for tiny stuff (like some unicode stuff we missed somehow)20:13
harlowjaiv_m thats fair20:14
harlowjasounds good to me20:14
harlowjak, so next release20:15
harlowja#topic 0.2 release20:15
*** openstack changes topic to "0.2 release (Meeting topic: openstack-state-management)"20:15
harlowjaso this one i think we all know whats going into it, nothing unexpected afaik20:15
harlowjajust lets merge things after move to oslo20:16
harlowjai'm also thinking we should put a release notes on ML20:16
harlowja*some type of release notes20:16
iv_msure20:17
*** mestery has joined #openstack-meeting20:17
harlowjaiv_m maybe for each release we should follow the pattern @ https://etherpad.openstack.org/p/TaskFlow-0.1.320:17
harlowjathat one seems nice20:17
*** TravT has quit IRC20:17
harlowjamake a https://etherpad.openstack.org/p/TaskFlow-0.2.0 for example20:17
harlowjawith whats new, what changed ...20:18
changblwhen to have 0.2?20:18
iv_msounds good20:18
harlowjachangbl ah that question :)20:18
*** sarob has joined #openstack-meeting20:18
harlowja#action harlowja start https://etherpad.openstack.org/p/TaskFlow-0.2.020:18
harlowjachangbl i think the goal is next week or the week after20:19
changblok, that is quick20:19
changblvery soon20:19
harlowjawell we can change that :-P20:19
harlowja0.1.3 wasn't supposed to exist, lol (more of a patch release)20:19
*** thomasbiege has quit IRC20:20
harlowjachangbl do u think we should wait more?20:20
harlowjai can see a nice to have being more examples for 0.2.020:20
harlowjathat would help show to people the new features20:20
* harlowja always likes more examples :-P20:20
changblharlowja, depends on what to achieve in 0.2:)20:22
harlowjawell i think its composed of the following20:22
harlowja* jobboard reference impl (ready for people to start trying it out)20:22
*** RajeshMohan has quit IRC20:22
harlowja* remote workers20:22
harlowja* retry controlling that akarpinska1  is working on20:22
*** mrda_away is now known as mrda20:22
harlowja+ any other bug fixes20:23
harlowjayour zookeeper backend will be in 0.1.3 (since it merged)20:23
*** mst89 has quit IRC20:23
*** RajeshMohan has joined #openstack-meeting20:23
*** mestery has quit IRC20:23
*** _nadya_ has quit IRC20:24
changbli think probably more time is needed to nail down all above TODOs.20:24
harlowjaagreed, i think changbl  its mostly review time though and documentation and examples20:25
harlowjahopefully those don't take to long20:25
changblreview take time...20:25
harlowjaya, np, no rush there :)20:25
harlowjaif it takes more time to review, thats fine20:26
*** markmcclain has quit IRC20:26
harlowjawe can revisit release date to, just seems like ~2weeks should be able to review, document, make examples (and all that)20:27
harlowjaif not, we can change to >2weeks20:27
*** malini1 has quit IRC20:27
harlowjasound fine?20:28
changblharlowja, yes20:28
harlowjak20:28
harlowja#topic cinder-integration-process20:28
*** openstack changes topic to "cinder-integration-process (Meeting topic: openstack-state-management)"20:28
harlowjaso this one is connected to http://lists.openstack.org/pipermail/openstack-dev/2014-February/026184.html20:28
harlowjai just wanted to see how we can improve there (along with others and the cinder work)20:28
*** jcoufal has joined #openstack-meeting20:28
*** IanGovett has quit IRC20:29
changblJohn G mentioned persistence is wanted right?20:29
harlowjachangbl ya20:29
changblwe'd get persistence ready for cinder20:29
changblseems they really like persistence from taskflow20:29
harlowjachangbl i am thinking so, i need to see if i can get the nttdata folks to jump in20:29
*** sarob has quit IRC20:29
harlowjaakarpinska1 do u see any major issues doing this, it will likely change a little bit how they run there workflows (its split across 3 components still)20:30
*** sarob has joined #openstack-meeting20:30
harlowjai imagine the simplest approach is to add persistence in the 3 places (is it the same logbook, not sure)20:30
changblwhich 3 places?20:30
akarpinska1I started to move common parts to separate tasks20:30
harlowjachangbl also i think part of the improvement that was desired, is to make sure that all the refactoring that was happening was well understood20:30
changblharlowja, yes20:31
harlowjachangbl api node, scheduler node, volume node20:31
akarpinska1when I finish with retries I'll finish it20:31
*** oubiwann_ has joined #openstack-meeting20:31
harlowjaakarpinska1 lets also see if we can get the ntt folks to jump in, they seem willing and able20:31
akarpinska1now we can give some recommendations about the coding style for flows, but the most important part is a persistence, I think20:32
harlowjasome of these ideas i wrote up and have updated @ https://etherpad.openstack.org/p/cinder-taskflow-persistence20:32
harlowjaakarpinska1 agreed, even the basic persistence model they would benefit from20:32
harlowjaand that i think would then unblock these other reviews (once they see what it means)20:32
harlowjai'll try to catch the nttdata folks, see if they want to take ownership of this (or i can work with them to make it happen), just want to make sure they are visible and communicating the changes they are doing20:33
harlowjaand the overall plan (which i think was confusing some of the cinder folks, thus the above ML email)20:34
changblharlowja, rohit and another folk from nttdata?20:34
*** sarob has quit IRC20:34
harlowjachangbl i think abhishek (and a couple other folks)20:34
changblharlowja, ok20:35
harlowjarohit (who used to be doing some orchestration work) i think went to another company (unless its a different rohit u are thinking)20:35
*** IanGovett1 has joined #openstack-meeting20:35
changbloh, we mean the same rohit:)20:35
*** nikhil is now known as nikhil-brb20:35
harlowjak20:35
harlowja#action harlowja engage cinder folks, nttdata folks to get some movement on persistence writeups,ideas...20:36
harlowjathe other thing that cinder wants to gain from taskflow is there state consistency issues20:36
harlowja*is to resolve there state-consistency issues20:37
harlowjai think there will be a feb cinder mid-cycle meetup where everyone will try to figure out what to do here, i'll try to be there if its in the bay area20:37
harlowjanot so easy to nail down what it means, is it resource consistency problems, race conditions on manipulating resources, other....20:38
harlowjajgriffith has the location for this been finalized yet (so that i can try to go :))20:38
harlowja*this == cinder mid-cycle meetup20:38
*** krtaylor has joined #openstack-meeting20:39
harlowjaanyways i'll followup on that, anyone that wants to attend to help please join ;)20:39
*** nikhil-brb is now known as nikhil20:39
harlowjaakarpinska1 ^^ ;)20:39
akarpinska1k20:40
harlowja#action harlowja determine when is the cinder meetup so that taskflow people can jump on phone, in person...20:40
harlowja#topic new use-cases20:41
*** openstack changes topic to "new use-cases (Meeting topic: openstack-state-management)"20:41
harlowjaany new things that people are thinking about that we should have (that we don't)20:41
harlowjaif not i guess we can just jump into open-discuss20:41
harlowja520:42
harlowja420:42
changblsold:)20:42
harlowja320:42
ccrouchhttp://lists.openstack.org/pipermail/openstack-dev/2014-February/026403.html20:42
harlowjawe have  winner20:42
changbljust kidding:)20:42
changblgo on20:42
ccrouchanything relevant in sdakes message there?20:42
harlowjaccrouch interesting20:42
ccrouchi.e. integration with Heat20:43
* harlowja reading20:43
ccrouchits a *big* thread, but thats the part that seemed most relevant to taskflow20:44
harlowjahmmm, so partially that seems to be suggesting a workflow service right, which to me brings into the picture what mistral is20:45
harlowjaalthough there has been much discussion about heat using taskflow20:45
harlowja*which changes alot of how heat runs (for better or worse)20:45
harlowjaalthough the mistral dsl seems to be turning into a 'full-fledged programming language'20:46
*** colinmcnamara has joined #openstack-meeting20:46
ccrouch(2:45:23 PM) harlowja: although there has been much discussion about heat using taskflow20:46
ccrouchi will go and try and find that20:46
harlowjaccrouch i've been working with the mistral folks on using taskflow, there initial prototype still isn't using taskflow but i think they want to20:47
harlowjaccrouch http://icehousedesignsummit.sched.org/event/ced7d22ac4c037f102b3cf3ade553104#.UvP00fY71ro20:47
harlowjai think there was a etherpad somewhere20:47
harlowjaccrouch https://etherpad.openstack.org/p/icehouse-summit-heat-workflow20:47
harlowjathe problem with changing heat was the coroutine style in heat makes it really hard to alter/change it to something else (something say that uses remote workers)20:48
harlowjai'm all for bringing the question up again20:48
harlowjafrom the HK summit i think the conclusion was that heat needed to do some refactoring before changing how it ran was even possible20:49
harlowja*which was also desired to fix there scaling bottleneck20:50
harlowjaand they wanted taskflow to have a remote-worker model (now @ https://review.openstack.org/#/c/63155/)20:50
ccrouchharlowja: ok, i can trying poking sdake about where this is at, if you would be receptive on your side to pushing the "workflow" ball down the field with heat20:50
* harlowja unsure what that exactly means :)20:50
harlowjathe pushing the workflow ball down the field to heat :)20:51
ccrouchthat folks won;t say "too busy doing cinder integration, sorry cant talk" :-)20:51
harlowjaoh, sure, i'm always up for talking :)20:51
harlowja*unless i'm in mad crazy programming mode, lol20:52
*** julim has joined #openstack-meeting20:52
harlowjaccrouch sounds good, lets start this conversation up with sdake (and any others)20:52
harlowjaand see what happens20:52
ccrouchok i'll see where sdake is at20:52
ccrouch+120:52
*** banix has quit IRC20:52
harlowjacool, thx much20:52
*** julim has quit IRC20:53
harlowjaalright final topic20:53
harlowja#topic open-discuss20:53
*** openstack changes topic to "open-discuss (Meeting topic: openstack-state-management)"20:53
harlowjasooo the only thing that i have is to get more input on https://etherpad.openstack.org/p/taskflow-atlanta-speaker-ideas :)20:54
harlowjaso that we can start filing little speaker abstracts20:54
harlowja'Hurry, the deadline to submit is February 14, 2014.  '20:54
*** mattgriffin has quit IRC20:54
harlowjaso start adding in anything that might be cool to show20:54
harlowjaor talk about20:54
harlowjaor...20:54
*** asalkeld has joined #openstack-meeting20:55
harlowjaanyways, that all i got20:56
*** jcoufal has quit IRC20:56
harlowjaanybody else, if not we can end :-P20:57
harlowja520:57
harlowja420:57
harlowja3.120:57
harlowja220:57
harlowja0.520:57
harlowja0.020:57
harlowjaboom20:57
harlowjathanks for coming again folks20:57
harlowjamore excitement always found in #openstack-state-management20:57
*** julim has joined #openstack-meeting20:58
harlowja#endmeeting20:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:58
openstackMeeting ended Thu Feb  6 20:58:02 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_state_management/2014/openstack_state_management.2014-02-06-20.01.html20:58
*** akarpinska1 has left #openstack-meeting20:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_state_management/2014/openstack_state_management.2014-02-06-20.01.txt20:58
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_state_management/2014/openstack_state_management.2014-02-06-20.01.log.html20:58
*** iv_m has left #openstack-meeting20:59
*** vkmc has joined #openstack-meeting20:59
*** TravT has joined #openstack-meeting20:59
*** rkukura has quit IRC20:59
*** vladikr has joined #openstack-meeting21:00
*** denis_makogon_ has joined #openstack-meeting21:00
*** dvarga is now known as dvarga|away21:00
*** dvarga|away is now known as dvarga21:00
*** asalkeld has quit IRC21:00
*** andreaf2 has quit IRC21:00
*** denis_makogon_ is now known as denis_makogon21:01
*** IanGovett1 has quit IRC21:02
*** colinmcnamara has quit IRC21:02
*** Yathi has joined #openstack-meeting21:02
*** NikitaKonovalov_ is now known as NikitaKonovalov21:02
*** amrith has quit IRC21:02
*** ccrouch has left #openstack-meeting21:03
*** amrith has joined #openstack-meeting21:03
*** malini has joined #openstack-meeting21:04
*** sgordon has quit IRC21:04
*** colinmcnamara has joined #openstack-meeting21:05
*** vladikr has left #openstack-meeting21:05
*** thomasbiege has joined #openstack-meeting21:06
*** nikhil has quit IRC21:06
*** lblanchard has joined #openstack-meeting21:06
*** mattgriffin has joined #openstack-meeting21:09
*** thuc_ has quit IRC21:10
*** sudorandom has left #openstack-meeting21:11
*** thuc has joined #openstack-meeting21:11
*** mattgriffin has quit IRC21:11
*** ken1ohmichi has joined #openstack-meeting21:11
*** markwash has quit IRC21:12
*** nikhil__ has joined #openstack-meeting21:13
*** asalkeld has joined #openstack-meeting21:14
*** colinmcnamara has quit IRC21:14
*** gokrokve has joined #openstack-meeting21:14
*** thuc has quit IRC21:15
*** nikhil__ has quit IRC21:16
*** nikhil__ has joined #openstack-meeting21:16
*** sarob has joined #openstack-meeting21:17
*** dvarga is now known as dvarga|away21:17
*** dvarga|away is now known as dvarga21:17
*** malini has left #openstack-meeting21:18
*** markmcclain has joined #openstack-meeting21:18
*** ryanpetrello has quit IRC21:20
*** ryanpetrello has joined #openstack-meeting21:22
*** zhiyan has left #openstack-meeting21:22
*** sudorandom has joined #openstack-meeting21:23
*** krtaylor has quit IRC21:24
*** DinaBelova is now known as DinaBelova_21:25
*** beyounn has quit IRC21:25
*** cdub has joined #openstack-meeting21:27
*** ddutta has joined #openstack-meeting21:28
*** jcooley_ has quit IRC21:28
*** jcooley_ has joined #openstack-meeting21:29
*** jjmb has joined #openstack-meeting21:29
*** Gordonz has quit IRC21:29
*** jcoufal-mobile has joined #openstack-meeting21:31
*** ddutta has quit IRC21:32
*** sarob has quit IRC21:33
*** sarob has joined #openstack-meeting21:33
*** d0ugal has joined #openstack-meeting21:34
*** d0ugal has quit IRC21:34
*** d0ugal has joined #openstack-meeting21:34
*** cdub has quit IRC21:34
*** dprince has quit IRC21:35
*** d0ugal has quit IRC21:35
*** amrith has quit IRC21:36
*** sarob has quit IRC21:36
*** jjmb has quit IRC21:36
*** sarob has joined #openstack-meeting21:37
*** amrith has joined #openstack-meeting21:38
*** masayukig has joined #openstack-meeting21:38
*** jjmb has joined #openstack-meeting21:40
*** sarob has quit IRC21:41
*** d0ugal has joined #openstack-meeting21:41
*** d0ugal has quit IRC21:41
*** d0ugal has joined #openstack-meeting21:41
*** zehicle_at_dell has joined #openstack-meeting21:42
*** otherwiseguy has quit IRC21:45
*** beyounn has joined #openstack-meeting21:45
*** Duane_ has quit IRC21:48
*** Duane_ has joined #openstack-meeting21:49
*** mst89 has joined #openstack-meeting21:49
*** thouveng has quit IRC21:51
*** thouveng has joined #openstack-meeting21:51
*** Duane_ has quit IRC21:53
*** rocky2 has joined #openstack-meeting21:55
*** zehicle_at_dell has quit IRC21:55
*** zehicle_at_dell has joined #openstack-meeting21:55
*** bdpayne has quit IRC21:56
*** ayoung is now known as ayoung-afk21:57
*** doug_shelley66 has quit IRC21:57
*** bdpayne has joined #openstack-meeting21:58
*** mlavalle has joined #openstack-meeting21:58
mtreinish#startmeeting qa22:00
openstackMeeting started Thu Feb  6 22:00:14 2014 UTC and is due to finish in 60 minutes.  The chair is mtreinish. Information about MeetBot at http://wiki.debian.org/MeetBot.22:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:00
*** openstack changes topic to " (Meeting topic: qa)"22:00
openstackThe meeting name has been set to 'qa'22:00
*** jjmb has quit IRC22:00
mtreinishhi who do we have today?22:00
*** swifterdarrell has left #openstack-meeting22:00
dkranzHere22:00
masayukigo/22:00
rahmuhello22:00
mlavallehello22:00
mtreinish#link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting22:00
mtreinish^^^ today's agenda22:01
ken1ohmichihi22:01
boris-42_hi all22:01
boris-42_=)22:01
afazekashi22:01
*** balajiiyer1 has left #openstack-meeting22:01
boris-42_how are you guys?)22:01
mtreinishlet's dive into it22:01
*** epim has quit IRC22:01
mtreinish#topic Blueprints22:01
*** openstack changes topic to "Blueprints (Meeting topic: qa)"22:01
mtreinishdoes anyone have a blueprint that needs attention?22:02
mtreinishor a status update on an open blueprint?22:02
dkranzmtreinish: no :)22:03
mtreinishheh yeah I guess let's move on to the next topic22:03
*** epim has joined #openstack-meeting22:03
mtreinish#topic Neutron testing22:03
*** openstack changes topic to "Neutron testing (Meeting topic: qa)"22:03
mtreinishmlavalle: any updates on the status of things with neutron?22:03
* boris-42_ enikanorov__ ping22:04
mlavalleapi tests development has continued22:04
enikanorov__boris-42_: queque22:04
mlavallelot's of good contributions. We have almost a 100% coverage of the gap identified in the etherpad22:04
enikanorov__boris-42_: greate that you've just woke me up22:04
mtreinishoh wow are they all up for review?22:04
mlavallethey are all in some part of the revuew cycle22:05
*** shakayumi has joined #openstack-meeting22:05
enikanorov__i wanted to ask tempest cores to look at the patch we want for quite a long time:22:05
mlavalleI am doing about 4 reviews a day22:05
enikanorov__oh22:05
enikanorov__i see it got approved22:05
enikanorov__https://review.openstack.org/#/c/58697/22:05
enikanorov__thanks!22:05
mtreinishmlavalle: ok and is the neutron gate stablized so we can start pushing things through?22:06
*** jcoufal-mobile has quit IRC22:06
masayukigyeah22:06
dkranzenikanorov__: I was a little concerned about the runtime22:06
dkranzmtreinish: It adds 45 seconds to neutron run. What should we do about this?22:06
mlavallesalv-orlando reported good progress this past Monday22:06
mtreinishdkranz: the neutron run isn't that much of a concern on the time budget22:06
dkranzmtreinish: We said we would focus on scenarios but by nature they can take some time22:06
mtreinishbecause they only run smoke22:06
mlavalleI understand they are still stabilizing this week22:06
enikanorov__dkranz: it spanws a vm. i guess we could setup a backend on the host itself22:07
dkranzmtreinish: Yes, but they are only running a few minutes faster...22:07
enikanorov__and just add route to the host from the tenant network22:07
mtreinishdkranz: it'll be an issue long term but for right now it's ok22:07
dkranzmtreinish: sdague wanted us to watch out for this22:07
mlavalleI will ping him again today or tomorrow and pass the status in the qa channel22:07
mtreinishmlavalle: ok cool22:07
mtreinishI know we merged the neutron api tenant isolation patch22:07
dkranzmtreinish: ok, I will stop worrying and love the bomb22:07
mtreinishwhich previously broke things22:08
mlavallewe've made good progress getting people contributing and I don't want to loose their enthusiasm22:08
mtreinishdkranz: yeah sdague just said we need to be careful with what we merge to try and control the overall runtime22:08
*** IlyaE has quit IRC22:08
mlavallethat's all I have22:08
mtreinishdkranz: if it becomes an issue we can just start tagging things as slow22:09
mtreinishand add a new nonheat slow job22:09
dkranzmtreinish: True22:09
*** david_lyle has quit IRC22:09
*** pdmars has quit IRC22:09
*** sc68cal_ has quit IRC22:10
mtreinishok does anyone have anything else to bring up about neutron testing?22:10
*** jjmb has joined #openstack-meeting22:10
mtreinishok then let's move on22:10
mtreinish#topic When can we enable failing jobs with bogus log ERRORs (dkranz)22:10
*** openstack changes topic to "When can we enable failing jobs with bogus log ERRORs (dkranz) (Meeting topic: qa)"22:10
mtreinishdkranz: you're up22:11
dkranzmtreinish: I put in a lot of work to get this feature in.22:11
*** NikitaKonovalov is now known as NikitaKonovalov_22:11
dkranzmtreinish: It got turned off due to unstable gate22:11
dkranzNow bugs are creeping back in22:11
dkranzThat are ignored because they just show up in a log that no one looks at.22:11
*** shakayumi has quit IRC22:11
*** andreaf has joined #openstack-meeting22:12
mtreinishdkranz: yeah it was causing a lot of nondeterministic failures at a time when things were already really unstable22:12
dkranzsdague made a comment that we could turn this back on after icehouse-222:12
dkranzmtreinish: which is now22:12
mtreinishdkranz: we can't do that now because of the oslo.messaging errors22:12
dkranzmtreinish: but now we have all these errors again22:12
mtreinishevery run will fail22:12
dkranzmtreinish: right, so how do we get that fixed?22:12
rahmudkranz: mtreinish: can you please briefly explain what this feature is about?22:12
dkranzrahmu: ok22:13
mtreinishrahmu: sure, dkranz wrote a script that goes through all the service logs and prints out the error messages after a gate run22:13
mtreinishit used to fail the job if there was an error in any of the logs22:13
dkranzrahmu: There are a lot of bugs that let tests seem to pass even thought something is screwed up22:13
dkranzmtreinish: is fixing the oslo thing a priority for any one?22:14
*** IlyaE has joined #openstack-meeting22:14
mtreinishI know sdague brought it up on the ML, but I haven't been paying too much attention to it22:14
rahmumtreinish: dkranz: I understand. Thanks :)22:14
dkranzThe "lot of work" was not to write the script but to make sure all errors existing converged in a whitelist22:15
*** A-G has joined #openstack-meeting22:15
*** thomasem_ has quit IRC22:15
dkranzA task we are stuck with again22:15
mtreinishdkranz: yeah I understand, another idea that sdague and I were throwing around was to split the log checking into a separate bot22:15
dkranzmtreinish: You mean make it not part of the gate?22:16
mtreinishso instead of failing a run, it would look at the logs after jenkins reported the results and would leave another voting score (only +1 or -1)22:16
mtreinishthat way we wouldn't be hit by nondeterministic issues in the gate22:16
mtreinishbut we'd still get a -1 if there were errors in the logs22:17
dkranzmtreinish: Will that cause any one to fix them?22:17
dkranzmtreinish: A lot, if not most, of these errors are bugs.22:17
rahmumtreinish: will that be a blocking -1?22:18
mtreinishdkranz: I don't know, we've never done something like that before22:18
dkranzmtreinish: And they are easy to track down because you can see where they came from22:18
mtreinishrahmu: no, it'd be a -1 like the third party testing22:18
clarkbthere is no such thing as a blocking -122:19
clarkbonly -2 can block22:19
mtreinishdkranz: yeah, it was just another approach to consider about doing this22:19
clarkb(in the verified column)22:19
*** andreaf has quit IRC22:19
dkranzmtreinish: Why can't we treat it like any other test failure, as we were doing?22:19
*** andreaf has joined #openstack-meeting22:20
mtreinishclarkb: isn't it any column?22:20
*** rakhmerov has quit IRC22:20
clarkbmtreinish: well approved is only 0 or 1 so 0 is blocking22:20
mtreinishclarkb: oh yeah that's true22:20
mtreinishdkranz: it was more about splitting out the complexity from the one job I think22:21
dkranzmtreinish: What complexity? I think we either care about this or we don't.22:21
dkranzmtreinish: If I am the only one who really cares about it we should just drop the whole thing, no?22:21
*** andreaf has quit IRC22:22
*** andreaf has joined #openstack-meeting22:22
mtreinishdkranz: it's polluting the console log right now and everyone ignores it. So we have to climb the hurdle to get it failing jobs again22:22
dkranzmtreinish: Having some bot is way more complex than what it was doing.22:22
mtreinishthis was just an idea for a middle ground22:22
dkranzmtreinish: Only the oslo thing is polluting it. If we just fixed that there would not be a problem.22:23
dkranzmtreinish: There wasn't a problem before.22:23
*** banix has joined #openstack-meeting22:23
dkranzmtreinish: ANd if we had left this on the oslo thing never would have gotten in!22:23
*** beyounn has quit IRC22:23
*** jdob has quit IRC22:23
*** kfarr has joined #openstack-meeting22:23
mtreinishdkranz: I don't think that oslo.messaging is the only issue right now. It's the biggest one definitely22:24
mtreinishand things slipped in because the script was broken for a while22:24
mtreinish(on the d-g side)22:24
dkranzmtreinish: Anyway, I am ok with moving on now22:24
mtreinishdkranz: ok22:24
dkranzmtreinish: If we are going to get anywhere, sdague will have to send an email about it.22:24
mtreinish#topic Criteria for accepting tests that cannot run normally in the gate (dkranz)22:25
*** openstack changes topic to "Criteria for accepting tests that cannot run normally in the gate (dkranz) (Meeting topic: qa)"22:25
mtreinishdkranz: this one is yours too22:25
*** jjmb has quit IRC22:25
*** mestery has joined #openstack-meeting22:25
dkranzmtreinish: There could be a lot of valuable tests that we share but we can't due to our policy of only accepting code that runs upstream22:25
*** RajeshMohan has quit IRC22:25
dkranzmtreinish: I just thought we should clarify exactly what that means22:26
dkranzmtreinish: So folks can decide whether to try to submit tests upstream or do them downstream, which would be a shame.22:26
*** epim has quit IRC22:26
mtreinishdkranz: it's not code that runs upstream, we need results for every review with the test running22:26
*** RajeshMohan has joined #openstack-meeting22:26
mtreinishit can be from an outside test system22:26
*** andreaf_ has joined #openstack-meeting22:26
mtreinishlike the 3rd party testing requirements in the other projects22:26
*** epim has joined #openstack-meeting22:27
mtreinishthe issue is that if we don't exercise tests for everything they tend to bitrot very quickly22:27
dkranzmtreinish: So vote on every commit22:27
dkranzmtreinish: That is a very high bar22:27
mtreinishit's the same reason we stopped accepting commits with skips22:27
mtreinishdkranz: otherwise we don't know if things work or not22:27
mtreinishand that's not a good position to be22:27
dkranzmtreinish: That may be ok for folks trying to get drivers into the code base22:27
mtreinishright now we've got legacy tests in the tree like live migration that I've never run22:28
mtreinishI have no idea if they work22:28
dkranzmtreinish: I could not justify such a third-party system just to be able to submit my tests upstream22:28
dkranzmtreinish: How about a compromise22:28
mtreinishdkranz: it came up earlier this week with the multi-backend cinder22:28
*** rohit404 has quit IRC22:28
dkranzmtreinish: The tests can run be reported on by third party nightly22:28
dkranzmtreinish: But if they stay broken for more than X time, they are removed22:29
*** blackchip has joined #openstack-meeting22:29
*** lisaclark1 has quit IRC22:29
*** andreaf has quit IRC22:29
mtreinishdkranz: we tried that before with the nightly periodic all job22:29
*** lisaclark1 has joined #openstack-meeting22:29
mtreinishno one ever looked at it22:29
dkranzmtreinish: Not the remove part :)22:29
*** dvarga has quit IRC22:29
dkranzmtreinish: That is the teeth22:30
*** andreaf has joined #openstack-meeting22:30
mtreinishdkranz: yeah after a few months I just ripped out all the tests that got run in all that didn't run in the gate22:30
mtreinishI think it was mostly whitebox22:30
dkranzmtreinish: RIght22:30
dkranzmtreinish: And any one who cared enough to put the tests upstream would probably care enough to keep them working22:30
mtreinishdkranz: it's a good idea but we'll have to be explicit about the policy22:30
dkranzmtreinish: Just an idea22:30
*** beyounn has joined #openstack-meeting22:31
mtreinishand it'll require someone to watch it22:31
dkranzmtreinish: ok, I'll send out some kind of proposal to the ml if it seems worthwhile22:31
mtreinishdkranz: that hasn't been my experience. Things normally just get thrown over the fence22:31
*** mestery has quit IRC22:31
mtreinishdkranz: yeah bring this out to the ml22:31
dkranzmtreinish: The test would be external so it is likely some one would be watching22:31
*** blackchip has quit IRC22:32
mtreinishand maybe we'll follow up at summit22:32
*** blackchip has joined #openstack-meeting22:32
dkranzmtreinish: And one motivation for this is that our  plan is to increase function of upstream22:32
dkranzmtreinish: So in the future multnode tests maybe could run and if we do this they will be there22:32
*** andreaf_ has quit IRC22:32
dkranzmtreinish: That's all for now22:33
*** vijendar has quit IRC22:33
mtreinishdkranz: the issue with this though is the integrated gating, it's not just tempest that could break things22:33
*** dwalleck has joined #openstack-meeting22:33
mtreinishdkranz: ok we can move on22:33
*** andreaf_ has joined #openstack-meeting22:33
mtreinish#topic Bugs22:34
*** openstack changes topic to "Bugs (Meeting topic: qa)"22:34
*** lisaclark1 has quit IRC22:34
*** doug_shelley66 has joined #openstack-meeting22:34
mtreinishDoes anyone have any bugs that they think needs some attention?22:34
mtreinishor any high priority or critical bugs that need extra eyes on them?22:34
*** andreaf has quit IRC22:34
mtreinishok I guess there aren't any bugs today :)22:35
afazekashttps://review.openstack.org/#/c/71575/22:35
*** joesavak has quit IRC22:35
mtreinish#topic Critical Reviews22:35
*** openstack changes topic to "Critical Reviews (Meeting topic: qa)"22:35
mtreinishafazekas: good timing22:36
mtreinish#link https://review.openstack.org/#/c/71575/22:36
mtreinishdoes anyone else have any reviews that they'd like to get some eyes on?22:36
dkranzhttps://review.openstack.org/#/c/65930/22:36
*** blackchip has quit IRC22:37
boris-42_mtreinish #link https://review.openstack.org/#/c/70131/22:37
dkranzhttps://review.openstack.org/#/c/71579/22:37
mtreinish#link https://review.openstack.org/#/c/65930/22:37
boris-42_mtreinish it is not tempest but it is related ..22:37
mtreinish#link https://review.openstack.org/#/c/71579/22:37
mtreinishboris-42_: that's fine22:37
mtreinishI'll take a look at it probably tomorrow22:37
boris-42_mtreinish could I share 2 blueprints around integration of rally & tempest?22:38
mtreinishlike share them between projects in lp? or right now in the meeting?22:38
*** dwalleck has quit IRC22:38
boris-42_mtreinish in meeting, could we have some topic about integration.. I would like to be a closer to openstack QA team..22:39
boris-42_mtreinish sorry didn't add it to agenda =(22:39
mtreinishboris-42_: sure22:39
boris-42_mtreinish thank you22:39
mtreinishfirst does anyone else have reviews to bring up?22:39
*** beyounn has quit IRC22:40
mtreinishok I guess not22:40
mtreinish#topic Rally tempest integration22:40
*** openstack changes topic to "Rally tempest integration (Meeting topic: qa)"22:40
mtreinishboris-42_: go ahead22:40
*** beyounn has joined #openstack-meeting22:41
*** asalkeld has quit IRC22:41
boris-42_so there are 2 parts of integration22:41
*** Mandell has quit IRC22:41
boris-42_first of all what is rally… small diagram https://wiki.openstack.org/w/images/e/ee/Rally-Actions.png22:41
boris-42_so it is the tool that allows you to work with different clouds, verify them, deploy on (virtual) servers and benchmark22:42
boris-42_(in future as well profile & analyze logs)22:42
*** thuc has joined #openstack-meeting22:42
*** otherwiseguy has joined #openstack-meeting22:42
boris-42_it is done to simplify work for human22:42
boris-42_=)22:42
boris-42_We are trying to reuse as much as possible from OpenStack and related project22:42
boris-42_e.g. one of deploy engine is based on DevStack22:43
*** krtaylor has joined #openstack-meeting22:43
boris-42_so there are 2 first points that are related to tempest22:43
boris-42_1. add some kind of pretty interface to tempest22:43
boris-42_ https://blueprints.launchpad.net/rally/+spec/tempest-verification22:43
*** thuc_ has joined #openstack-meeting22:44
boris-42_So when you are working around nova e.g.22:44
boris-42_you have cloud22:44
boris-42_you would like to have some command like22:44
boris-42_rally verify nova (that will run only tempest tests that are related to nova)22:44
boris-42_and after something fails22:44
boris-42_you are fixing it22:44
boris-42_and would like first of all to run failed tests22:45
boris-42_so run rally verify latest_failed22:45
boris-42_as well you would like to keep results for some cloud somewhere (it will be Rally DB)22:45
mtreinishboris-42_: that sounds like a wrapper around a lot of things in tempest already22:45
mtreinishboris-42_: We try to service tag tests so you can run with a regex filter compue for example and that should run every test that touches nova22:46
boris-42_mtreinish yep buy I would like to simplify this step a bit22:46
boris-42_mtreinish if it is already implemented in tempest great22:46
mtreinishand testr already keeps a db (obviously a bit more simplistic than rally's) of runs with failed jobs22:46
boris-42_mtreinish if it could be implement ok22:46
mtreinishand information about them22:46
boris-42_mtreinish I know but it is not enough simple for end users imho..22:47
*** thuc has quit IRC22:47
boris-42_mtreinish there is a lot of tasty things that could be added22:47
boris-42_mtreinish one more time the goal is not to reimplement stuff (just unify & simplify interface)22:48
boris-42_mtreinish and somewhere store all results related to specifc cloud22:48
mtreinishboris-42_: ok, I just don't know if those 2 examples have to be rally specific22:48
mtreinishthey seem generally applicable to tempest and testr and improvements22:48
*** mdurnosvistov_ has quit IRC22:49
boris-42_mtreinish we will try to implement all that is possible inside tempest22:49
mtreinishI don't know if we should wrap things to add extra functionality22:49
mtreinishboris-42_: ok22:49
boris-42_mtreinish the idea is next22:49
boris-42_mtreinish it is nice when you have one interface for all operation that is all unified22:49
*** beyounn has quit IRC22:50
boris-42_mtreinish I mean one commad to add/deploy cloud22:50
boris-42_mtreinish then another command to play with tempest22:50
boris-42_mtreinish then third command to benchmark22:50
boris-42_mtreinish and even after year you will have all results22:50
boris-42_mtreinish in one place22:50
boris-42_So goal is to unify, make some pretty hooks for most often commands, somewhere store results and so on=)22:51
*** beyounn has joined #openstack-meeting22:51
boris-42_mtreinish as well as automation of generation of config for tempest by passing endpoints of cloud22:52
boris-42_I know when you are working with tempest for a while it is just a put here and there some info and it works22:53
boris-42_but when somebody is newbie to tempest it takes a while..22:53
boris-42_So next thing is https://blueprints.launchpad.net/rally/+spec/tempest-benchmark-scenario22:54
mtreinishboris-42_: we've actually been working on tooling to simplify that part of the problem22:54
*** Gordonz has joined #openstack-meeting22:54
boris-42_mtreinish oh it will be nice if you share your results/blueprints/discussion22:54
boris-42_mtreinish we will be glad to help you guys22:54
mtreinishboris-42_: this is most recent one I'm working on: https://blueprints.launchpad.net/tempest/+spec/config-verification22:55
mtreinishboris-42_: you definitely have a lot of info to share here, but we're running out of time22:55
* boris-42_ mtreinish added to bookmarks22:55
mtreinishand it feels like we need a larger discussion about rally and tempest22:55
boris-42_so okay just a bit about benchmarking scenario22:55
rahmumtreinish: speaking of which. Can you give us a quick status about it and tell us what's left to do?22:55
rahmumtreinish: I'm talking about the config-verification bp22:56
mtreinishboris-42_: can you take this to the ML22:56
boris-42_mtreinish okay we can continue in mailing list probably?)22:56
boris-42_mtreinish sure I will take22:56
mtreinishwith all the details22:56
mtreinishboris-42_: great thanks22:56
boris-42_mtreinish let us then prepare demo22:56
boris-42_mtreinish we are always able just to put some code from rally to tempst/devstack22:56
boris-42_actually we will be only glad to reduce code base of rally=)22:56
*** mattgriffin has joined #openstack-meeting22:57
mtreinishrahmu: sure I'm still working on adding all the extension detection. I've got a patch up for swift now22:57
mtreinishthen I still need to finish api version discovery for keystone, and cinder22:57
mtreinishand add endpoint/service checking to it as well22:57
mtreinishand I'm sure there are other optional features or things I'm missing22:58
mtreinishbut that's what I have on my mind right now for it22:58
mtreinishboris-42_: ok cool22:58
boris-42_mtreinish thank you for giving timeframe=)22:58
mtreinish#topic open discussion22:58
*** markwash has joined #openstack-meeting22:58
*** openstack changes topic to "open discussion (Meeting topic: qa)"22:58
mtreinishactually there is only ~1 min left22:59
mtreinishso let's end here today22:59
boris-42_^_^22:59
dkranzbye22:59
*** rocky2 has quit IRC22:59
mtreinishif there was something we couldn't get to we can just pick it up on -qa22:59
rahmubye everyone22:59
mtreinishthanks everyone22:59
mtreinish#endmeeting22:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:59
openstackMeeting ended Thu Feb  6 22:59:29 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/qa/2014/qa.2014-02-06-22.00.html22:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/qa/2014/qa.2014-02-06-22.00.txt22:59
openstackLog:            http://eavesdrop.openstack.org/meetings/qa/2014/qa.2014-02-06-22.00.log.html22:59
masayukigyeah, bye22:59
ken1ohmichibye22:59
*** amrith has quit IRC22:59
*** ken1ohmichi has left #openstack-meeting22:59
*** david-lyle has joined #openstack-meeting22:59
*** markmcclain has quit IRC23:02
*** amrith has joined #openstack-meeting23:02
*** Gordonz has quit IRC23:02
*** amcrn has quit IRC23:03
*** kfarr has quit IRC23:03
*** balajiiyer has joined #openstack-meeting23:04
*** epim has quit IRC23:04
*** rocky2 has joined #openstack-meeting23:05
*** amcrn has joined #openstack-meeting23:06
*** sacharya has quit IRC23:07
*** dkranz has quit IRC23:08
*** venkatesh has joined #openstack-meeting23:09
*** Yathi has quit IRC23:09
*** epim has joined #openstack-meeting23:09
*** enikanorov has joined #openstack-meeting23:11
*** eharney has quit IRC23:11
*** enikanorov__ has quit IRC23:12
*** Invent has quit IRC23:15
*** dcramer_ has quit IRC23:15
*** burt1 has quit IRC23:16
*** alex_xu has quit IRC23:17
*** brucer has joined #openstack-meeting23:17
*** asalkeld has joined #openstack-meeting23:19
*** asalkeld has quit IRC23:19
*** markpeek has quit IRC23:20
*** asalkeld has joined #openstack-meeting23:20
*** rocky2 has quit IRC23:21
*** eglynn has joined #openstack-meeting23:22
*** beyounn has quit IRC23:29
*** julim has quit IRC23:29
*** lblanchard has quit IRC23:29
*** dims has quit IRC23:30
*** bpb has quit IRC23:30
*** julienvey has quit IRC23:32
*** lisaclark1 has joined #openstack-meeting23:32
*** otherwiseguy has quit IRC23:32
*** banix has quit IRC23:33
*** kevinconway has quit IRC23:34
*** jmontemayor has quit IRC23:35
*** prad_ has quit IRC23:35
*** jmontemayor has joined #openstack-meeting23:35
*** SumitNaiksatam has quit IRC23:36
*** A-G has quit IRC23:37
*** A-G has joined #openstack-meeting23:37
*** A-G has quit IRC23:38
*** asalkeld has quit IRC23:39
*** jmontemayor has quit IRC23:39
*** esker has quit IRC23:40
*** sarob has joined #openstack-meeting23:40
*** denis_makogon has quit IRC23:41
*** lcheng_ has quit IRC23:42
*** lisaclark1 has quit IRC23:42
*** eglynn has quit IRC23:42
*** sarob has quit IRC23:45
*** dims has joined #openstack-meeting23:46
*** tanisdl has quit IRC23:47
*** changbl has quit IRC23:47
*** ftcjeff has quit IRC23:48
*** amrith has quit IRC23:48
*** yamahata has quit IRC23:49
*** reed has quit IRC23:50
*** changbl has joined #openstack-meeting23:51
*** radsy has joined #openstack-meeting23:51
*** asalkeld has joined #openstack-meeting23:52
*** IanGovett has joined #openstack-meeting23:52
*** bauzas has quit IRC23:53
*** Mandell has joined #openstack-meeting23:55
*** thuc_ has quit IRC23:55
*** thuc has joined #openstack-meeting23:56
*** SumitNaiksatam has joined #openstack-meeting23:56
*** thuc has quit IRC23:56
*** thuc has joined #openstack-meeting23:57
*** bknudson has quit IRC23:59

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