Thursday, 2014-02-06

*** grapex has quit IRC00:01
*** sarob has quit IRC00:03
*** sarob has joined #openstack-meeting-alt00:03
*** mestery has joined #openstack-meeting-alt00:07
*** lisaclark1 has joined #openstack-meeting-alt00:07
*** sarob has quit IRC00:07
*** jcru has quit IRC00:08
*** mestery has quit IRC00:08
*** yogesh has joined #openstack-meeting-alt00:11
*** ruhe has joined #openstack-meeting-alt00:13
*** sarob has joined #openstack-meeting-alt00:15
*** RajeshMohan has quit IRC00:15
*** demorris has joined #openstack-meeting-alt00:19
*** devlaps has joined #openstack-meeting-alt00:20
*** __nikhil__ has joined #openstack-meeting-alt00:21
*** __nikhil__ has quit IRC00:21
*** jergerber has quit IRC00:22
*** jmontemayor has quit IRC00:22
*** __nikhil__ has joined #openstack-meeting-alt00:23
*** __nikhil__ has quit IRC00:23
*** david-lyle has quit IRC00:24
*** sarob has quit IRC00:25
*** sarob has joined #openstack-meeting-alt00:26
*** esker has joined #openstack-meeting-alt00:26
*** kin_ has joined #openstack-meeting-alt00:26
*** nikhil__ has quit IRC00:27
*** markwash has quit IRC00:29
*** nikhil has joined #openstack-meeting-alt00:30
*** nikhil has quit IRC00:30
*** sarob has quit IRC00:30
*** nikhil has joined #openstack-meeting-alt00:31
*** sarob has joined #openstack-meeting-alt00:33
*** yogesh has quit IRC00:34
*** nikhil has quit IRC00:35
*** nikhil has joined #openstack-meeting-alt00:36
*** yamahata has joined #openstack-meeting-alt00:37
*** jcoufal has joined #openstack-meeting-alt00:39
*** nikhil has quit IRC00:39
*** nikhil has joined #openstack-meeting-alt00:39
*** banix has quit IRC00:40
*** markwash has joined #openstack-meeting-alt00:40
*** vkmc has joined #openstack-meeting-alt00:43
*** sarob has quit IRC00:44
*** RajeshMohan has joined #openstack-meeting-alt00:44
*** sarob has joined #openstack-meeting-alt00:44
*** eankutse has quit IRC00:46
*** demorris has quit IRC00:47
*** markwash has quit IRC00:48
*** sarob has quit IRC00:49
*** atiwari has quit IRC00:49
*** sarob has joined #openstack-meeting-alt00:50
*** Sukhdev has quit IRC00:54
*** nosnos has joined #openstack-meeting-alt00:56
*** Duane_ has joined #openstack-meeting-alt00:57
*** sarob has quit IRC01:01
*** sarob has joined #openstack-meeting-alt01:01
*** sarob has quit IRC01:06
*** sarob has joined #openstack-meeting-alt01:07
*** vkmc has quit IRC01:10
*** Duane_ has quit IRC01:14
*** Duane_ has joined #openstack-meeting-alt01:14
*** igor has joined #openstack-meeting-alt01:15
*** igor____ has quit IRC01:16
*** devlaps has quit IRC01:17
*** ruhe has quit IRC01:18
*** Duane_ has quit IRC01:18
*** esmute has quit IRC01:22
*** tanisdl has quit IRC01:23
*** cody-somerville has quit IRC01:25
*** saurabhs has quit IRC01:33
*** mozawa has joined #openstack-meeting-alt01:33
*** bill_az_ has quit IRC01:35
*** sc68cal has quit IRC01:37
*** jcoufal has quit IRC01:39
*** jcoufal has joined #openstack-meeting-alt01:40
*** beyounn has quit IRC01:42
*** amcrn has quit IRC01:43
*** saurabhs has joined #openstack-meeting-alt01:43
*** bdpayne has quit IRC01:44
*** chadlung has quit IRC01:47
*** michael-yu has quit IRC01:49
*** sacharya has joined #openstack-meeting-alt01:51
*** lisaclark2 has joined #openstack-meeting-alt01:53
*** lisaclark1 has quit IRC01:56
*** sc68cal has joined #openstack-meeting-alt01:56
*** mestery has joined #openstack-meeting-alt01:57
*** gokrokve has quit IRC02:02
*** amytron has joined #openstack-meeting-alt02:03
*** beyounn has joined #openstack-meeting-alt02:08
*** IlyaE has quit IRC02:11
*** saurabhs has quit IRC02:12
*** michael-yu has joined #openstack-meeting-alt02:12
*** banix has joined #openstack-meeting-alt02:13
*** sarob_ has joined #openstack-meeting-alt02:14
*** amrith has quit IRC02:14
*** mestery has quit IRC02:15
*** amrith has joined #openstack-meeting-alt02:15
*** sarob has quit IRC02:16
*** ityaptin has quit IRC02:16
*** ityaptin has joined #openstack-meeting-alt02:16
*** jcoufal has quit IRC02:18
*** sarob_ has quit IRC02:18
*** ijw has quit IRC02:23
*** sarob has joined #openstack-meeting-alt02:25
*** Duane_ has joined #openstack-meeting-alt02:26
*** michael-yu has quit IRC02:30
*** richm has quit IRC02:32
*** baoli has joined #openstack-meeting-alt02:37
*** Duane_ has quit IRC02:37
*** sc68cal has quit IRC02:38
*** lisaclark2 has quit IRC02:42
*** arnaud__ has quit IRC02:44
*** harlowja has quit IRC02:44
*** arnaud has quit IRC02:45
*** gokrokve has joined #openstack-meeting-alt02:50
*** balajiiyer has joined #openstack-meeting-alt02:50
*** SushilKM has quit IRC02:52
*** balajiiyer has quit IRC02:54
*** balajiiyer has joined #openstack-meeting-alt02:54
*** harlowja has joined #openstack-meeting-alt02:55
*** gokrokve has quit IRC02:55
*** gokrokve has joined #openstack-meeting-alt02:56
*** RajeshMohan has quit IRC02:59
*** gokrokve has quit IRC03:00
*** RajeshMohan has joined #openstack-meeting-alt03:00
*** gokrokve has joined #openstack-meeting-alt03:00
*** doug_shelley66 has quit IRC03:00
*** baoli has quit IRC03:00
*** sarob has quit IRC03:06
*** gokrokve has quit IRC03:06
*** sarob has joined #openstack-meeting-alt03:06
*** briancline has quit IRC03:10
*** aignatov_ is now known as aignatov03:11
*** baoli has joined #openstack-meeting-alt03:12
*** coolsvap_away has quit IRC03:13
*** sc68cal_ has joined #openstack-meeting-alt03:14
*** sc68cal_ has quit IRC03:15
*** sc68cal_ has joined #openstack-meeting-alt03:18
*** sc68cal_ has quit IRC03:18
*** yogesh has joined #openstack-meeting-alt03:20
*** yogesh has quit IRC03:25
*** sc68cal_ has joined #openstack-meeting-alt03:28
*** amotoki has joined #openstack-meeting-alt03:34
*** sc68cal_ has quit IRC03:39
*** baoli has quit IRC03:40
*** sc68cal has joined #openstack-meeting-alt03:45
*** david-lyle has joined #openstack-meeting-alt03:51
*** amrith has quit IRC04:03
*** HenryG has joined #openstack-meeting-alt04:09
*** Duane_ has joined #openstack-meeting-alt04:16
*** bdpayne has joined #openstack-meeting-alt04:18
*** Duane_ has quit IRC04:20
*** gokrokve has joined #openstack-meeting-alt04:24
*** mattgriffin1 has joined #openstack-meeting-alt04:31
*** mattgriffin1 has quit IRC04:31
*** sgordon has quit IRC04:37
*** dguitarbite has joined #openstack-meeting-alt04:37
*** jcooley_ has quit IRC04:43
*** coolsvap has joined #openstack-meeting-alt04:44
*** akuznetsov has joined #openstack-meeting-alt04:45
*** michael-yu has joined #openstack-meeting-alt04:49
*** sc68cal has quit IRC04:50
*** mspreitz has joined #openstack-meeting-alt04:50
*** sc68cal has joined #openstack-meeting-alt04:50
*** gokrokve has quit IRC04:50
*** gokrokve has joined #openstack-meeting-alt04:52
*** gokrokve has quit IRC04:53
*** doug_shelley66 has joined #openstack-meeting-alt04:57
*** betsy has joined #openstack-meeting-alt04:57
*** doug_shelley66 has quit IRC05:01
*** nosnos_ has joined #openstack-meeting-alt05:02
*** mspreitz has left #openstack-meeting-alt05:02
*** 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
*** sarob has joined #openstack-meeting-alt05:10
*** harlowja has joined #openstack-meeting-alt05:14
*** sarob has quit IRC05:15
*** NearlyFunctional has quit IRC05:27
*** aignatov is now known as aignatov_05:27
*** akuznetsov has quit IRC05:34
*** akuznetsov has joined #openstack-meeting-alt05:36
*** jrist has joined #openstack-meeting-alt05:39
*** DinaBelova_ is now known as DinaBelova05:41
*** jrist has quit IRC05:43
*** jrist has joined #openstack-meeting-alt05:43
*** bdpayne has quit IRC05:44
*** NearlyFunctional has joined #openstack-meeting-alt05:45
*** banix has quit IRC05:47
*** jcooley_ has joined #openstack-meeting-alt05:49
*** jrist has quit IRC05:52
*** sergmelikyan has quit IRC05:58
*** dteselkin_ has quit IRC05:59
*** dteselkin_ has joined #openstack-meeting-alt05:59
*** julim has joined #openstack-meeting-alt06:00
*** denis_makogon has joined #openstack-meeting-alt06:00
*** amytron has quit IRC06:03
*** Duane_ has joined #openstack-meeting-alt06:04
*** DinaBelova is now known as DinaBelova_06:06
*** bdpayne has joined #openstack-meeting-alt06:08
*** Duane_ has quit IRC06:09
*** jcooley_ has quit IRC06:11
*** sarob has joined #openstack-meeting-alt06:17
*** igor has quit IRC06:18
*** igor has joined #openstack-meeting-alt06:18
*** sarob has quit IRC06:21
*** jcooley_ has joined #openstack-meeting-alt06:24
*** denis_makogon_ has joined #openstack-meeting-alt06:24
*** _nadya_ has joined #openstack-meeting-alt06:25
*** denis_makogon has quit IRC06:26
*** IlyaE has joined #openstack-meeting-alt06:34
*** nosnos has joined #openstack-meeting-alt06:40
*** yogesh has joined #openstack-meeting-alt06:42
*** 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-meeting-alt06:51
*** dguitarbite_ has joined #openstack-meeting-alt06:52
*** coolsvap has quit IRC06:52
*** dguitarbite has quit IRC06:52
*** markwash has joined #openstack-meeting-alt06:53
*** NikitaKonovalov is now known as NikitaKonovalov_06:54
*** HenryG_ has joined #openstack-meeting-alt06:55
*** michael-yu_ has joined #openstack-meeting-alt06:56
*** michael-yu has quit IRC06:57
*** yamahata__ has quit IRC06:57
*** michael-yu_ is now known as michael-yu06:57
*** yamahata__ has joined #openstack-meeting-alt06:57
*** HenryG has quit IRC06:58
*** IlyaE has joined #openstack-meeting-alt06:58
*** coolsvap_away has quit IRC07:02
*** yogesh has quit IRC07:03
*** esmute has joined #openstack-meeting-alt07:04
*** funzo has quit IRC07:05
*** nati_ueno has quit IRC07:06
*** akuznetsov has quit IRC07:06
*** coolsvap has joined #openstack-meeting-alt07:07
*** akuznetsov has joined #openstack-meeting-alt07:09
*** IlyaE has quit IRC07:09
*** _nadya_ has joined #openstack-meeting-alt07:09
*** coolsvap_away has joined #openstack-meeting-alt07:11
*** coolsvap has quit IRC07:12
*** funzo has joined #openstack-meeting-alt07:13
*** sacharya has quit IRC07:20
*** IlyaE has joined #openstack-meeting-alt07:21
*** _nadya_ has quit IRC07:22
*** harlowja is now known as harlowja_away07:23
*** markwash has quit IRC07:24
*** _nadya_ has joined #openstack-meeting-alt07:27
*** _nadya_ has quit IRC07:28
*** markwash has joined #openstack-meeting-alt07:33
*** IlyaE has quit IRC07:33
*** coolsvap_away is now known as coolsvap07:37
*** flaper87|afk is now known as flaper8707:39
*** IlyaE has joined #openstack-meeting-alt07:41
*** sc68cal is now known as sc68cal_07:50
*** sarob has joined #openstack-meeting-alt07:52
*** sc68cal_ is now known as sc68cal07:52
*** Duane_ has joined #openstack-meeting-alt07:52
*** julim has joined #openstack-meeting-alt07:54
*** IlyaE has quit IRC07:54
*** denis_makogon_ has quit IRC07:55
*** rohit404 has joined #openstack-meeting-alt07:56
*** Duane_ has quit IRC07:56
*** kevinbenton has joined #openstack-meeting-alt08:01
*** markwash has quit IRC08:02
*** jcoufal has joined #openstack-meeting-alt08:17
*** markwash has joined #openstack-meeting-alt08:18
*** NikitaKonovalov_ is now known as NikitaKonovalov08:20
*** sbalukoff has quit IRC08:20
*** sbalukoff has joined #openstack-meeting-alt08:26
*** nati_ueno has joined #openstack-meeting-alt08:40
*** markwash has quit IRC08:43
*** jcoufal has quit IRC08:50
*** nacim has joined #openstack-meeting-alt08:51
*** jtomasek has joined #openstack-meeting-alt08:55
*** sarob has quit IRC09:00
*** sarob has joined #openstack-meeting-alt09:01
*** beyounn has quit IRC09:03
*** sarob has quit IRC09:06
*** jcoufal has joined #openstack-meeting-alt09:06
*** aignatov_ is now known as aignatov09:10
*** rsblendido has joined #openstack-meeting-alt09:12
*** rossella_s has joined #openstack-meeting-alt09:12
*** nati_ueno has quit IRC09:23
*** safchain has joined #openstack-meeting-alt09:24
*** cody-somerville has joined #openstack-meeting-alt09:28
*** cody-somerville has quit IRC09:28
*** cody-somerville has joined #openstack-meeting-alt09:28
*** nati_ueno has joined #openstack-meeting-alt09:29
*** igor_ has joined #openstack-meeting-alt09:30
*** igor has quit IRC09:32
*** jcooley_ has quit IRC09:32
*** nati_ueno has quit IRC09:36
*** DinaBelova_ is now known as DinaBelova09:37
*** derekh has joined #openstack-meeting-alt09:38
*** johnthetubaguy has joined #openstack-meeting-alt09:39
*** johnthetubaguy1 has joined #openstack-meeting-alt09:40
*** johnthetubaguy has quit IRC09:40
*** Duane_ has joined #openstack-meeting-alt09:41
*** michael-yu has quit IRC09:42
*** johnthetubaguy has joined #openstack-meeting-alt09:42
*** johnthetubaguy1 has quit IRC09:44
*** Duane_ has quit IRC09:45
*** michael-yu has joined #openstack-meeting-alt09:47
*** michael-yu has quit IRC09:48
*** johnthetubaguy has quit IRC10:03
*** johnthetubaguy has joined #openstack-meeting-alt10:05
*** sarob has joined #openstack-meeting-alt10:11
*** sarob has quit IRC10:16
*** ruhe has joined #openstack-meeting-alt10:21
*** aignatov is now known as aignatov_10:22
*** aostapenko has joined #openstack-meeting-alt10:34
*** denis_makogon has joined #openstack-meeting-alt10:46
*** NikitaKonovalov is now known as NikitaKonovalov_10:54
*** dguitarbite_ has quit IRC10:54
*** mozawa has quit IRC10:56
*** NikitaKonovalov_ is now known as NikitaKonovalov10:57
*** aignatov_ is now known as aignatov10:58
*** RajeshMohan has quit IRC11:10
*** irenab has joined #openstack-meeting-alt11:11
*** RajeshMohan has joined #openstack-meeting-alt11:11
*** jprovazn has joined #openstack-meeting-alt11:11
*** david-lyle has quit IRC11:17
*** boris-42_ has quit IRC11:18
*** vkmc has joined #openstack-meeting-alt11:19
*** Duane_ has joined #openstack-meeting-alt11:29
*** coolsvap_away has joined #openstack-meeting-alt11:29
*** coolsvap has quit IRC11:30
*** Duane_ has quit IRC11:33
*** vkmc has quit IRC11:43
*** coolsvap_away is now known as coolsvap11:46
*** DinaBelova is now known as DinaBelova_11:52
*** safchain has quit IRC11:56
*** jpich has joined #openstack-meeting-alt11:57
*** Duane_ has joined #openstack-meeting-alt11:57
*** baoli has joined #openstack-meeting-alt12:00
*** rkukura has quit IRC12:01
*** Duane__ has joined #openstack-meeting-alt12:01
*** matrohon has quit IRC12:02
*** doug_shelley66 has joined #openstack-meeting-alt12:04
*** Duane_ has quit IRC12:04
*** DinaBelova_ is now known as DinaBelova12:05
*** amrith has joined #openstack-meeting-alt12:08
*** yamahata has quit IRC12:14
*** Duane__ has quit IRC12:17
*** Duane_ has joined #openstack-meeting-alt12:18
*** Duane_ has quit IRC12:22
*** jcooley_ has joined #openstack-meeting-alt12:26
*** PhilD has joined #openstack-meeting-alt12:28
*** boris-42_ has joined #openstack-meeting-alt12:30
*** jcooley_ has quit IRC12:31
*** coolsvap has quit IRC12:34
*** coolsvap has joined #openstack-meeting-alt12:34
*** baoli has quit IRC12:42
*** baoli has joined #openstack-meeting-alt12:42
*** igor has joined #openstack-meeting-alt12:45
*** Duane_ has joined #openstack-meeting-alt12:45
*** igor_ has quit IRC12:46
*** sgordon has joined #openstack-meeting-alt12:54
*** coolsvap has quit IRC12:55
*** Duane_ has quit IRC12:56
*** Duane_ has joined #openstack-meeting-alt12:56
baoli#startmeeting PCI Passthrough13:00
openstackMeeting started Thu Feb  6 13:00:22 2014 UTC and is due to finish in 60 minutes.  The chair is baoli. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: PCI Passthrough)"13:00
openstackThe meeting name has been set to 'pci_passthrough'13:00
*** mozawa has joined #openstack-meeting-alt13:00
baolihi13:00
*** Duane_ has quit IRC13:00
irenabhi13:03
irenabsorry for being late13:03
*** pdmars has joined #openstack-meeting-alt13:04
*** sadasu has joined #openstack-meeting-alt13:06
sadasuhello13:06
irenabhi, I got notice from rkukura for being late in 10 mins13:07
sadasuok...until he joins...can we talk about the SriovMechanismDriverBase/Mixin13:08
irenabI have some delay with vnic_type due to other urgent task, I think I will resume the work on it in Sunday.13:09
sadasuwhat do you have in mind?13:09
*** safchain has joined #openstack-meeting-alt13:09
*** safchain has quit IRC13:09
irenabsadasu: We have the nova to support nova that passes in the port profile with all SRIOV related detail13:10
*** safchain has joined #openstack-meeting-alt13:10
*** rkukura has joined #openstack-meeting-alt13:10
sadasuyes, how about the validate_port_binding() in the AgentMechanismDriverBase13:11
irenabsadasu: sorry,  we have to support nova call into port create/update with SRIOV details, seems at least this should be parsed generically13:11
sadasuagreed...but didn't think that was going to be a lot..13:12
sadasunova calls into validate_port_binding(). It is currently implemented only be ovs and linuxbridge agents13:13
sadasuin our SR-IOV context, does each mechanism driver take care of it?13:14
*** NehaV has joined #openstack-meeting-alt13:14
rkukurahi - sorry I'm late (as usual)13:14
irenabsadasu: agree. Seems that it will be code duplication to parse, store and retrive this information by each MD.13:14
irenabrkukura: hi13:15
rkukuraI'm proposing to eliminate validate_port_binding(). Do you see an need for it?13:15
sadasurkukura: hello!13:15
irenabI can attend only for more 15 mins more, sorry13:15
*** amrith has quit IRC13:15
sadasuneed some guidance on the validate_port_binding() method13:16
baoliI was wondering how rkukura's binding:profile binding:vif_details support would look like. Then we can decide based on that13:16
irenabsadasu: I think that validate_port_binding can be generic for SRIOV and if needed call into derived Mech Driver, but actually need write reference code to see how it goes13:16
rkukuraI think I'm on track to push WIP patches for both those BPs tomorrow.13:16
sadasuirenab: as I said earlier, we can add the mixin class if there is enough common functionality...we can discuss on the list13:16
irenabsadasu: fine, I think we can try to figure out on internal mail exchange and then publish on the list if its OK with you13:17
rkukuraSee http://lists.openstack.org/pipermail/openstack-dev/2014-February/026344.html for the proposed changes regarding ML2's port binding and mechanism drivers.13:17
irenabrkukura: great!13:17
sadasurkukura: thanks! And also, nice detailed write up on what you are proposing with original and current portContext13:18
irenabI have some delay with vnic_type, hope to be back on this on Sunday13:19
baoliCool, seems that we are on track from neutron side13:19
sadasuirenab: thanks13:19
baoliCan we continue with what we have left off from yesterday?13:19
rkukurairenab: I'm guessing your policy rule investigation has already been discussed - I'll read the log after the meeting and followup on the email thread if needed13:20
irenabrkukura: not discussed yet13:20
*** NehaV has quit IRC13:20
sadasurkukura: not discussed in the meeting yet, only on the list13:20
irenabbaoli: do you want to discuss the question you sent?13:21
sadasuanythink other than ^^ lesft over from yesterday?13:21
baoli#topic policy rule13:21
*** openstack changes topic to "policy rule (Meeting topic: PCI Passthrough)"13:21
baoliirenab, sure go ahead13:21
*** jpich has left #openstack-meeting-alt13:22
irenabI did net-list on behalf of tenant and saw shared network there13:23
*** julim has quit IRC13:23
irenabbut the net-show shows admin as owner of the shared network13:23
baoli "admin_or_owner": "rule:context_is_admin or tenant_id:%(tenant_id)s",13:24
baoli    "admin_or_network_owner": "rule:context_is_admin or tenant_id:%(network:tenant_id)s",13:24
baoliI can see what admin_or_network_owner is about13:24
baolithe user should either have an admin role, or its tenant id matches the network's tenant id13:25
irenabso what I think that for vnic_type we need "admin_or_owner"13:25
irenabto cover the shared network case13:25
irenabbut actually not sure why it is forbiden for tenant user  to set mac-address and IP on shared network13:26
baoliSo what exactly tenant_id:%(tenant_id)s means in the admin_or_owner definition?13:27
rkukurairenab: "admin_or_owner" allows access for the owner of the poirt itself. That sounds like what we want. If the network is shared and someone else owns it, the user's own port is still owned by that user, not the owner of the network.13:27
sadasuto indavertantly disallow duplicate mac address or IP address config?13:27
irenabbaoli: like rkukura said, owner of the port13:27
baoliirenab, got it, thanks.13:28
sadasurkukura: thanks for clarifying.13:28
irenabso agree on admin_or_owner?13:29
sadasuirenab: so, admin_or_owner should be fine for us13:29
irenabsadasu: great13:29
irenabbaoli: can you please give brief update if there is anything new on nova side?13:30
*** mriedem has joined #openstack-meeting-alt13:30
irenabany progress with your patch?13:30
baoliirenab, I havent heard anything yet?13:30
sadasuthen can i quickly get my question answered by rkukura?13:30
irenabsadsu: may I have few moremins for next  step?13:31
baoliI sent request to the mailing list and John13:31
irenabI just need to go in few mins13:31
sadasuirenab: go ahead13:31
irenabI wanted to suggest that although the chances to get nova part in time are very low, to try to progress with all relevant parts and at least have reference end to end code working13:33
baoliirenab, I agree with you thats the plan.13:33
rkukurairenab: I have a call with markmcclain today and will ask about the blocked status on your BP, and see if I can get that cleared up13:33
irenabthen we will be able to come to Juno release with POC in all components and make every discussion or bp very concrete13:33
sadasucan we post draft code changes even without BP being approved?13:33
sadasuthis is for baoli's nova code13:34
irenabI guess so, it will be just delayed with reviews13:34
rkukuraI believe sgordon is working to recruit nova cores to review patches13:34
sgordonrkukura, correct13:34
baoliOnly in the nova part, I'm not sure if we can get what we want on time13:34
irenabbaoli: I think at least we will have some code to apply and run, and make it fully functional in Juno13:35
sgordonsadasu, i think you can post it as draft13:35
baoliI need to work with Yunhong/yongli for that. Or I can work out something for the time being myself13:35
sgordonsadasu, it makes it easier for me to recruit 2 core for you if i can say "look patches!"13:35
sadasusgordon: ok13:35
*** vgnbkr_1 has quit IRC13:36
baolisgordon, that's great13:36
sgordonrussellb, does that seem like the right approach to you ^13:36
sgordoni think we can assume that for now and move on13:37
baolirkukura, irenab, going back to the multiprovidernet extension for a minute13:37
rkukurabaoli: ok13:37
baoliI think that it shouldn't affect sriov for the time being.13:37
baoliI asked Kyle about it13:38
baoliAnd he said the use case for now is the vxlan support13:38
baoliAnd I don't think that we will have vxlan support with sriov in near future13:38
irenabsorry, I have to go, will look into logs. sadasu, lets exchange emails to see regarding neutron generic SRIOV if needed13:38
*** vkmc has joined #openstack-meeting-alt13:38
sadasuirenab: thanks. will do.13:39
rkukurabaoli: Is the plan for the nova scheduling filter to use the neutron API to get the provider details to find the physical_network for which SR-IOV connectivity is needed?13:39
*** eankutse has joined #openstack-meeting-alt13:39
baolirkukura, no. The plan for the time being is for the MD to fill up the field in binding:profile. The field was named as pci-flaovr, which is not appropriate.13:40
baoliBut let's say we have a field called net-group13:41
baoliand MD can put the physical net name for now.13:41
baolinova api gets this infor after performing a query to neutron, and construct a pci request in the form "net-group: physical net name"13:42
*** eankutse has quit IRC13:42
*** eankutse has joined #openstack-meeting-alt13:43
*** BrianB_ has joined #openstack-meeting-alt13:43
rkukurabaoli: We don't have a bound MD until after the nova scheduler has made its decision and binding:host_id has been set on the port by nova.13:43
baoliThe pci request later is used by the scheduler to schedule the instance13:43
rkukuraOnce we have a bound MD, it can put the physical_network name and/or net-group, or whatever, into binding:profile for the nova VIF driver to use13:43
*** jjmb has joined #openstack-meeting-alt13:44
baolirkukura, how is the decision made on which MD should be bound?13:44
rkukurabut it can't do that until port binding has occurred, which cannot occur until binding:host_id has been set by nova, which cannot occur until nova has scheduled the VM13:44
rkukura"port binding" refers to selecting the bound MD13:45
rkukuraport binding is triggered by the setting of the binding:host_id attribute by nova13:45
baolirkukura, are you saying that a mechanism driver won't be invoked until binding:host_id is set?13:46
*** irenab has quit IRC13:46
rkukuraSo don't we need some way to ensure that nova schedules the VM on a compute node with an available VF for an SR-IOV device connected to the proper physical_network?13:47
rkukurabaoli: yes13:47
rkukurabaoli: sort of - there won't be a bound MD until binding:host_id is set, and its the bound MD that supplies binding:vif_type and soon binding:vif_details13:47
rkukuraseveral lines above I said binding:profile when I meant binding:vif_details13:48
*** jdob has joined #openstack-meeting-alt13:49
baolirkukura, all we need is the physical net name. Let's say that by the time nova api queries neutron with a port-id, neutron should be able to return the network details which includes the physical net name, right?13:49
baoliwhich means, even if we can't get it from vif_details, we can get it from the nuetron network details.13:50
sadasuphysical net name should be part of binding:vif_details13:50
*** doug_shelley66 has quit IRC13:50
rkukurabaoli: nova could use the providernet and/or multiprovidernet extension to find out what physical_network(s) can be used for the port13:50
baolirkukura, yes if we made the assumption.13:51
*** garyduan has joined #openstack-meeting-alt13:52
baolirkukura, another possibility is that we can use an extra argument something like --pci-flavor (--net-group). But I'm hesitating to go there because it will provoke another set of debates on pci-flavor, naming, etc.13:52
rkukurabaoli: This extra argument idea is a --nic option with nova, right?13:53
*** gduan has quit IRC13:53
baolirkukura, neutron port-create --binding:net-group <> --binding:vnic_type <>  and/or nova boot --nic vnic_type=<>,net-group=<>13:54
rkukuraI think I've been hearing two other ways to solve the scheduling issue other than an extra nova boot argument: 1) have user specify a VM flavor or host_aggregate that is known to have the needed SR-IOV connnectivity, or 2) implement a nova scheduler filter that uses the providernet and/or multiprovidernet extension to see what SR-IOV connectivity is needed and filter based on that.13:56
*** dprince has joined #openstack-meeting-alt13:56
baolirkukura, we had lengthy discussion with 1)13:57
baolifor 2), is that what we are trying to do for the time being?13:57
sadasurkukura: exactly...looked at 1 for a while...did not look too much into 213:57
*** jcooley_ has joined #openstack-meeting-alt13:57
*** hartsocks has joined #openstack-meeting-alt13:58
*** zhiyan has joined #openstack-meeting-alt13:59
*** ndipanov has joined #openstack-meeting-alt13:59
rkukuraLets call baoli's 3) implement a nova scheduler filter that uses the net-group value passed with --nic13:59
sadasusimplified version of 214:00
rkukuraI apologize that I've never managed to systematically sort through the history of these discussions and figure out which options are still on the table.14:00
*** sahid has joined #openstack-meeting-alt14:00
*** gilliard has joined #openstack-meeting-alt14:00
*** BobBall has joined #openstack-meeting-alt14:01
russellbneed the channel for the next meeting :)14:01
baolirkukura, for the time being, the assmuption is that the pci whitelist will be tagged with the correct physical net name.14:01
rkukuraAre these three options the ones that have been discussed, and are any off the table?14:01
baoliok14:01
*** a-gorodnev has joined #openstack-meeting-alt14:01
baolirkukura, let's continue in a different channel since people are waiting for this one14:02
baoli#endmeeting14:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:02
openstackMeeting ended Thu Feb  6 14:02:06 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-02-06-13.00.html14:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-02-06-13.00.txt14:02
rkukurabaoli: OK, should I send an email to the list with those 3 options and we can identify pros/cons and narrow it down?14:02
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-02-06-13.00.log.html14:02
russellbthanks!14:02
russellb#startmeeting nova14:02
openstackMeeting started Thu Feb  6 14:02:22 2014 UTC and is due to finish in 60 minutes.  The chair is russellb. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: nova)"14:02
openstackThe meeting name has been set to 'nova'14:02
mriedemhi14:02
hartsocks\o14:02
russellbhi everyone!14:02
PhilDHi14:02
n0anoo/14:02
russellb#topic general14:02
*** openstack changes topic to "general (Meeting topic: nova)"14:02
russellbfirst, the schedule14:03
russellb#link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule14:03
baolirkukura, #openstack-meeting is open now14:03
russellbblueprint approval deadline was this week14:03
*** jcooley_ has quit IRC14:03
russellbcode for blueprints must be posted in 2 weeks from today14:03
russellbi3 quickly closing in on us, so be aware :)14:03
russellbother big thing ... nova meetup next week14:04
russellb#link https://wiki.openstack.org/wiki/Nova/IcehouseCycleMeetup14:04
*** vponomaryov has joined #openstack-meeting-alt14:04
johnthetubaguysounds good14:04
russellbif you have any questions, let me know14:04
russellbwe've been collecting topics on https://etherpad.openstack.org/p/nova-icehouse-mid-cycle-meetup-items14:04
*** mspreitz has joined #openstack-meeting-alt14:04
russellbi'm going to start organizing that into a very rough cut at schedule for some of the big things14:05
n0anoanyone know what time we start on Mon?14:05
russellbn0ano: 9am14:05
n0anotoo civilized :-)14:05
russellbi'm not a great morning person14:05
*** rbrady has joined #openstack-meeting-alt14:05
russellbi want to tag specific big topics to cover in the mornings, at least14:05
russellblike, tasks ... want to see if we can bang through review/approval of design, at least14:06
russellband finalizing plans for taking v3 to final14:06
russellbneutron interaction is another big one14:06
johnthetubaguy+1 for task discussion14:06
russellbprocess discussion would be another14:06
russellbso if you have any topic requests, please record them14:06
*** garyk has joined #openstack-meeting-alt14:06
*** rbrady is now known as rbrady-brb14:07
garykhi14:07
ndipanovrussellb, in the etherpad?14:07
russellbndipanov: yeah etherpad14:07
*** browne has joined #openstack-meeting-alt14:07
russellbwe can discuss more in open discussion if we have time14:07
russellb#topic sub-teams14:07
*** openstack changes topic to "sub-teams (Meeting topic: nova)"14:07
hartsocks\014:07
*** ftcjeff has joined #openstack-meeting-alt14:07
*** lblanchard has joined #openstack-meeting-alt14:07
* n0ano gantt14:07
russellbhartsocks: you're up14:07
* johnthetubaguy raises xenapi hand14:07
hartsocks#link https://wiki.openstack.org/wiki/NovaVMware/Minesweeper14:08
hartsocksJust a quick note there. The CI guys are putting notes on that Wiki. Some status update info is linked on that page as well.14:08
*** sankarshan_away is now known as sankarshan14:08
russellbcool14:08
russellbdo you have your tempest config published?14:08
russellbwhat tests you exclude, if any?14:09
hartsocksWe had some infra trouble earlier in the week. And, we'll link that info and info about configs, excludes etc. on that wiki.14:09
garykfeatures that are not supported are not tested - for example security groups14:09
* russellb nods14:09
mriedemhartsocks: gary: i'd like to see more vmware people scoring on this before the rest of us are approving it: https://review.openstack.org/#/c/70137/14:09
russellbjust would be good to have that reference, i think all the driver CI systems should14:09
garykmriedem: sure14:10
mriedemit kind of blew up14:10
mriedemand it's blocking your other fixees14:10
garykmriedem: what do you mean it blew up?14:10
hartsockswe are going to go through a set of reviews as a team.14:10
mriedemjust got bigger than the oriinal couple of patch sets14:10
mriedemlots of back and forth between vmware people it seemed14:10
mriedemso i'm waiting for that to settle before getting  back on it14:11
garykmriedem: correct - it was a result of comments on the patch sets14:11
mriedemyeah, i know14:11
garykmriedem: understood14:11
garykif possible i'd lile to talk about the deferral of the image - caching14:11
garyki sent a mail to the list. not sure if you guys have seen it. not sure whu it was pushed out of I? the code has been reasy since december14:12
johnthetubaguygaryk: blueprint wasn't approved I guess?14:12
garykjohnthetubaguy: bp was apporved14:12
russellbif it was approved, then i shouldn't have deferred it14:12
russellblink?14:12
russellbi didn't think it was14:12
garykit was then pending a BP that was partially implemented and the proposer of the BP went missing14:13
garyksec14:13
garykhttps://blueprints.launchpad.net/openstack/?searchtext=vmware-image-cache-management14:13
russellbnot approved14:13
russellb"Review"14:13
garykit was approved then move due to https://blueprints.launchpad.net/nova/+spec/multiple-image-cache-handlers which is completely unrelated14:14
garykso what do we need to move from review to approved? this is a parity feature. as part i implemned the generic aging code14:14
*** yamahata has joined #openstack-meeting-alt14:15
*** RajeshMohan has quit IRC14:15
johnthetubaguyI think I stated it need more info for the docs team, or something like that?14:15
*** demorris has joined #openstack-meeting-alt14:15
russellbthe reason i put it in "Review" originally was i wanted the plan to be around making existing code generic where possible14:15
russellband i never got back to review it again14:15
russellblooks like johnthetubaguy also wanted docs added14:15
russellbbut perhaps more as a note before code merges14:15
garykrussellb: thanks for the clarification. basically it is exactly the same as libvirts aging. no new config var.14:15
russellbsharing some code now?14:16
*** RajeshMohan has joined #openstack-meeting-alt14:16
russellbwhere it makes sense?14:16
garykcan you please clarify what i need to add?14:16
russellbor did it just end up being sharing config?14:16
garykthe code that is possible to share is shared. can you please look at the mail on the list. i guess we can take it from there14:16
russellbheh ok if you wish, i mean you have my attention now14:17
russellbanyway it's probably fine14:17
garykthe config is the same as libvirts. the aging is just implemented in the driver - based on the generic code14:17
russellbok.14:17
russellbanything else on vmware?14:17
hartsocksWe could go on about our BP? :-)14:17
garyki do not want to take too much of the meeting time and i think i interupted theminesweepd update14:17
*** rbrady-brb is now known as rbrady14:17
russellbhartsocks: open discussion if you'd like14:18
russellbjohnthetubaguy: let's talk xenapi14:18
russellbjohnthetubaguy: i'm very interested to check in on CI status ...14:18
BobBallI'll talk to that.  CI is annoyingly close.14:18
johnthetubaguyBobBall: go for it14:18
BobBallOur initial efforts were on getting something integrated with the -infra stuff14:18
johnthetubaguythe key thing for me, is that we are putting for an external system now, since -infra stuff has stalled I guess?14:19
BobBalland we've got a bunch of patches up to enable that - but getting review time on that has been tricky14:19
BobBallFor the last two? weeks we've been focused on setting up our own 3rd party system rather than using -infra14:19
russellbyeah they've been pretty slammed14:19
BobBallwhich is annoying close14:19
BobBallGot nodepool running and deploying xenserver nodes and another script that runs the tests on them14:20
russellbany timeframe for turning it on?14:20
BobBalljoining the dots ATM14:20
*** lcostantino has joined #openstack-meeting-alt14:20
BobBallI'f you'd asked me at the beginning of this week I would have said "Friday" ;)14:20
BobBallSo it really could be any day now.14:20
russellbhow about confidence level that you'll have it running by icehouse-3?14:20
BobBallHigh14:20
russellbok, great14:20
johnthetubaguywe have tempest running outside of the automation right?14:21
johnthetubaguyand seen it run in VMs that nodepool should be creating14:21
johnthetubaguyso it really is just joining the dots now, we hope14:21
BobBallWe have full tempest running + passing in VMs in RAX using the -infra scripts14:21
BobBallyes, indeed.14:21
johnthetubaguyyeah, so almost, but no cigar14:21
johnthetubaguythats all from xenapi14:22
russellbok, well cutting it close14:22
russellbbut sounds like good progress14:22
BobBallToo close, yes :/14:22
russellbwhile we're still on driver CI ... hyper-v CI caught a bug yesterday, so that was cool to see14:22
johnthetubaguyyeah, aimed for gate integrated, and that gamble didn't quite work this time, but at least thats much closer for Juno14:22
russellbjohnthetubaguy: great goal though14:22
*** yamahata has quit IRC14:22
russellbjohnthetubaguy: bet you can get more attention early cycle14:23
johnthetubaguyyeah, should be awesome soon :)14:23
BobBallSo, yes, we distracted ourselves from integration to get the 3rd party stuff working so we don't miss the Icehouse deadline.14:23
russellbsounds like a good plan14:23
russellbn0ano: alright, gantt / scheduler stuff14:23
*** yamahata has joined #openstack-meeting-alt14:23
n0anotnx, couple of things...14:23
russellbn0ano: i saw your mail about devstack support, i assumed that means devstack support merged?14:23
n0anorussellb, yep, it's there and I sent an email out on how to configure it (with a typo that just got corrected)14:24
russellbgreat14:24
n0anocouple of things from the meeting...14:24
*** yamahata has quit IRC14:25
n0anono_db scheduler - still working on it, turn out removing the compute_node table from the DB is harder than originally thought but they'll get it eventually14:25
*** bill_az has joined #openstack-meeting-alt14:25
*** yamahata has joined #openstack-meeting-alt14:25
russellbit's starting to feel a bit risky for icehouse anyway14:25
russellbnot sure how others feel about it ...14:25
russellbbut massive architectural change to critical component better early in the cycle than toward the end14:25
n0anofor icehouse - as an option maybe, not as a default I hope14:25
russellbok, perhaps14:26
russellbguess i was assuming we'd do it as *the* way it works14:26
johnthetubaguywhat about a little caching, that gets no db during a user call to the scheduler?14:26
russellbjohnthetubaguy: your bp?14:26
* johnthetubaguy feels dirty for plugging his patch14:26
johnthetubaguyyeah...14:26
russellbjohnthetubaguy: i was going to say, i think that got deferred, but based on your description, i'd be happy to sponsor it14:26
johnthetubaguyhttps://review.openstack.org/#/c/67855/14:26
russellbjohnthetubaguy: because your approach sounds simple / low risk14:27
n0anoI think the current plan is a a complete cut to the no_db way, but if you think there's a  way to stepwise develop that would be good14:27
johnthetubaguyyeah, that one is approved, for a single host solution14:27
johnthetubaguyit just races with multiple hosts14:27
garyki have a few issues with that one when the scheduling deals with data that is not homgenous, but we can take it offline14:27
russellbn0ano: i'm not sure there's a sane way to make it optional14:27
johnthetubaguywe need to find one, I had a rough idea, but now is not the time14:27
n0anorussellb, note I said `if', I not sure there's a way either.14:27
russellbjohnthetubaguy: ah, you approved it yourself :-p14:27
johnthetubaguybasically status update from compute, and stats fetch driver14:28
johnthetubaguyrussellb: yeah, probably...14:28
russellbthat's fine, in this case anyway, heh14:28
*** betsy has quit IRC14:28
*** michael-yu has joined #openstack-meeting-alt14:29
*** Barker has joined #openstack-meeting-alt14:29
russellbi guess we can leave the full no_db thing targeted for now14:29
russellbbut the closer we get, the less comfortable i will be with it merging14:29
russellbwe'll see14:29
n0anoanyway, we also had a bit of a debate about scheduler request rate vs. compute node update rate, I don't expect that to be resolved until we have a working no_db scheduler with performance numbers.14:29
russellbyes, performance numbers are key14:30
n0anocode forklift - devstack changes merged in, still working on getting the pass the unit test changes merged14:30
mspreitzthe debate was about how those things scale14:30
johnthetubaguyyeah, performance testing show the complex cache didn't work, so I stripped it down to what is up for review now14:30
* n0ano fighting gerrit gets interesting14:30
*** bauzas has joined #openstack-meeting-alt14:30
russellbso on the forklift, couple of things14:30
russellb1) i responded to your devstack message with some next steps on getting gate testing running14:31
russellbi'd love to see an experimental job against nova that runs tempest with gantt instead of nova-scheduler14:31
russellbit's not actually that much work, just the right tweaks in the right places14:31
n0anosaw that, after the unit test patches are in I intend to work on that14:31
russellbOK great14:31
russellbok, the unit test patches ....14:31
russellbmy only issue was whether or not we should be including scheduler/rpcapi.py14:31
russellblonger term, that needs to be in its own repo14:32
*** jrist has joined #openstack-meeting-alt14:32
garykwe also need to have the scheduler to use objects14:32
russellbwe could merge it now, and do that later, but that makes the change history against the current gantt more complicated to replay on regenerating the repo later14:32
n0anorussellb, yeah, I think I dealt with that this morning but, due to gate testing, I had to add that file in the first patch and then delete it in the second14:32
garykif the scheduler uses objects then the foklift will be a lot easier in the long run and it will be backward compatiable with nova14:32
garykit will help with the database parts14:33
*** BrianB_ has quit IRC14:33
russellbanyone working on that?14:33
n0anogaryk we're just doing what the current scheduler does14:33
garykobjects?14:33
garyki started. initial patches git blocked14:33
garyki need to go back and speak with dan smith about those14:33
russellbn0ano: ok i'll review again today to see what you updatec14:34
johnthetubaguyas an aside, I guess the scheduler rpcapi and cells rpcapi both need to become public APIs, similar issues14:34
russellbwhy cells?14:35
n0anobtw, I'm not too worried about regenerating, now that I've done it once the second time should be easier, even if the history is a little convoluted14:35
russellbin the scheduler case, it's just the public API to gantt14:35
johnthetubaguycells, we wanted to make that public, so people can plug in there too14:36
russellbah, i see ...14:36
russellbi think the public part would be the manager side, right?14:36
johnthetubaguybut lets ignore that comment for now… its irrelevant really14:36
russellbok :)14:37
russellbrelated: i want to talk about the future of cells next week14:37
johnthetubaguyyes, possibly14:37
russellb#topic bugs14:37
*** openstack changes topic to "bugs (Meeting topic: nova)"14:37
russellbbug day tomorrow!14:37
russellb#link http://lists.openstack.org/pipermail/openstack-dev/2014-February/026320.html14:37
russellbthanks johnthetubaguy for putting message together14:37
johnthetubaguynp14:37
russellbshall we just collaborate in #openstack-nova?14:37
johnthetubaguyI think that works best14:38
johnthetubaguypeople spot its happening that way14:38
russellbagreed14:38
russellb196 new bugs14:38
johnthetubaguywell, thats under the 200 we had before14:38
*** lisaclark1 has joined #openstack-meeting-alt14:39
russellbyeah, someone(s) have been working on it apparently :)14:39
johnthetubaguyemail works, who knew14:39
russellbjohnthetubaguy: :-)14:39
russellbi'll be very pleased if we can hit 150 tomorrow14:39
russellband i'll buy cake if we hit 10014:39
russellbor something14:39
a-gorodnevbeer14:39
garykrussellb: are you talking about triage or fixes?14:39
n0anoa-gorodnev, +114:40
russellbtriage14:40
russellbfixes are great too of course14:40
russellbbut we have to stay on top of triage to make sure we're catching the most critical reports and getting attention on them14:40
garykack14:40
*** jecarey has joined #openstack-meeting-alt14:40
russellbso we'll talk bugs tomorrow ... so on for now14:40
russellb#topic blueprints14:40
*** openstack changes topic to "blueprints (Meeting topic: nova)"14:40
mriedemo/14:41
russellb#link https://blueprints.launchpad.net/nova/+milestone/icehouse-314:41
russellbmy biggest ask right now is to please make sure the status is accurate on your blueprints14:41
russellbbecause it's honestly too many for me to keep on top of and keep updated14:41
mriedemjog0 has a tool scanning those now14:41
*** julim has joined #openstack-meeting-alt14:41
russellbmriedem: nice14:41
russellbscript all the things14:41
mriedempatches with unapproved/wrong blueprint links14:41
johnthetubaguycool, I should try get hold of that14:42
russellbtime to bring out the -2 hammer14:42
russellbjohnthetubaguy: :-)14:42
mriedemstatus?14:42
johnthetubaguyI was going to take on keeping the blueprints honest, I will try do a loop through those soon14:42
*** dgenin has joined #openstack-meeting-alt14:42
*** julim has quit IRC14:42
russellbjohnthetubaguy: hugely appreciated14:42
russellband this is another big topic for next week ... revisiting our process around blueprints14:42
mriedemi wanted to point out that i've got my patches up for db2 support after working out the kinks locally, but of course it's going to be blocked on CI: https://review.openstack.org/#/c/69047/14:43
mriedemwhich is on hold until after the chinese new year...14:43
garykwould it be possible for you guys to review BP's next week - implementations that is14:43
russellbgaryk: some i'm sure14:43
russellbmriedem: CI?14:43
garykif there are a lot of people in the same room then it can be done in groups14:43
mriedem3rd party CI with a db2 backend14:43
*** julim has joined #openstack-meeting-alt14:43
mriedemthat was contingent on the blueprint14:44
russellbmriedem: yeah, that's going to be a blocker ... but if it's running in time, ping14:44
mriedemi don't have high hopes...14:44
*** dhellmann_ is now known as dhellmann14:44
russellbk, well saves me from having to break bad news to you then, you're fully aware :)14:44
mriedemi've already been setting low expectations internally :)14:44
russellbthe next cut on the icehouse-3 list is stuff still "not started"14:45
russellbPhilD: you have one "Not Started"14:45
russellbhttps://blueprints.launchpad.net/nova/+spec/tenant-id-based-auth-for-neutron14:45
russellbnot sure assignees of the others are here14:45
PhilDCode is up for review: https://review.openstack.org/#/c/69972/14:46
russellbheh, k14:46
* russellb sets needs review14:46
*** sadasu has quit IRC14:46
johnthetubaguyOK, so I will try make sure we have all the stats straight on those, I see joe's tool now14:46
PhilDthanks14:46
russellbthere's probably some that are dead14:46
russellbabandoned patches that haven't been touched in weeks14:47
johnthetubaguyalso, abandoned patches, etc, should get detected14:47
russellbshould just defer those too14:47
johnthetubaguyyeah14:47
russellbneed to aggressively prune this list toward reality14:47
johnthetubaguytime to deploy some scripting!14:47
russellbwheeee14:48
russellbthe blueprint API is not great.14:48
a-gorodnevI'm interested in one BP that hasn't be approved14:48
russellbbetter than screen scraping14:48
*** xyang2 has joined #openstack-meeting-alt14:48
russellba-gorodnev: which one is that14:48
a-gorodnevhttps://blueprints.launchpad.net/nova/+spec/glance-snapshot-tasks14:48
*** balajiiyer has joined #openstack-meeting-alt14:48
a-gorodnevthere tons of text there14:48
a-gorodnevbut nothing special14:48
russellbyeah that's not going to happen14:49
a-gorodnevI understand that it's already too late14:49
johnthetubaguywe already delete snapshots that error out, so we are doing better now14:49
a-gorodnevof course, the target is ouf of i314:50
russellb#topic open discussion14:50
*** openstack changes topic to "open discussion (Meeting topic: nova)"14:50
russellb10 minutes to go, can talk blueprints or anything else14:50
mriedemany major gate blockers?14:51
mriedemthis week seems quiet except for the one alexpilottie pointed out yesterday14:51
ndipanovrussellb, https://review.openstack.org/#/c/49395/ it's been sitting there for months, and is a nice fix14:52
mriedemwhich reminds me to check if that quieted another one down14:52
ndipanovprobably needs a rebase tho14:52
*** doug_shelley66 has joined #openstack-meeting-alt14:52
russellbmriedem: yeah, we reverted it ...14:52
russellbi saw one gate bug related to shelving?  though the timeframe sounded like it was probably caused by the same thing alex reverted yesterday14:52
mriedemrussellb: that's what i needed to correlate today14:53
mriedembecause yeah https://review.openstack.org/#/c/71105/14:53
mriedemthe shelving fail and the nwfilter in use fail show up around the same time14:53
*** balajiiyer has left #openstack-meeting-alt14:53
russellbk let me know what you find14:53
mriedemyar!14:53
mriedemah cool, looks like that revert fixed the nwfilter in use fail14:54
russellbcool, makes sense14:54
mriedemthe patch that won't go away :)14:55
*** eharney has joined #openstack-meeting-alt14:55
sahid:)14:55
mriedemtrends look the same with the shelving error, so must have been the root cause14:56
mriedemjog0 was right!14:56
garykndipanov: i had some comments on https://review.openstack.org/#/c/49395/14:57
*** PhilD has quit IRC14:57
*** cody-somerville has quit IRC14:57
russellbalright, well thanks for your time everyone14:57
russellbbye!14:57
russellb#endmeeting14:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:57
openstackMeeting ended Thu Feb  6 14:57:35 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova/2014/nova.2014-02-06-14.02.html14:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova/2014/nova.2014-02-06-14.02.txt14:57
*** ndn9797 has joined #openstack-meeting-alt14:57
openstackLog:            http://eavesdrop.openstack.org/meetings/nova/2014/nova.2014-02-06-14.02.log.html14:57
*** a-gorodnev has left #openstack-meeting-alt14:57
*** sahid has left #openstack-meeting-alt14:57
*** amrith has joined #openstack-meeting-alt14:58
*** scottda has joined #openstack-meeting-alt14:58
*** mriedem has left #openstack-meeting-alt14:58
ndipanovgaryk, ooops... -1 the patch in that case... don't be nice :)14:58
*** bswartz has joined #openstack-meeting-alt14:58
*** hartsocks has left #openstack-meeting-alt14:59
ndipanovgaryk, I don't get the , vs % comment?14:59
garykndipanov: i think that when they are nits i'd rather give a 015:00
garykmy understanding is that fo rthe log messages we should use the , and not pass the translations by % into the logging modules15:00
garykhope that makes sense15:00
bswartz#startmeeting manila15:01
openstackMeeting started Thu Feb  6 15:01:09 2014 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: manila)"15:01
openstackThe meeting name has been set to 'manila'15:01
ndipanovgaryk, ah yes15:01
bswartzhello guys15:01
scottdaHi15:01
ndipanovwell those are all easy to fix so no big deal15:01
aostapenkoHello15:01
vponomaryovHello15:01
xyang2hi15:01
csaba|afkhello15:01
ndn9797Hi..15:01
bill_azHi15:01
*** browne has left #openstack-meeting-alt15:01
*** achirko has joined #openstack-meeting-alt15:01
yportnovahi15:01
*** csaba|afk is now known as csaba15:02
achirkohello15:02
bswartzwow lots of people here today15:02
bswartzthat's good15:02
*** boris-42_ has quit IRC15:02
*** vbellur has joined #openstack-meeting-alt15:02
bswartzand I'm glad freenode got over the DDoS attack from last weekend -- that was annoying15:02
*** amotoki has quit IRC15:02
*** amrith has quit IRC15:02
*** akerr has joined #openstack-meeting-alt15:03
*** Barker has quit IRC15:03
bswartzI don't suppose we have rraja here today15:03
*** amrith has joined #openstack-meeting-alt15:03
bswartzdid all of you see his email?15:03
scottdayes15:03
bswartzI'd like to spend some time talking about taht15:04
csaba#link http://thread.gmane.org/gmane.comp.cloud.openstack.devel/1598315:04
bswartzcsaba: ty!15:04
bswartzI'd also like to revisit the neutron/nova/service VM networking stuff15:05
*** eankutse has quit IRC15:05
bswartzit will matter even more for the gateway-mediated stuff than for the generic driver I think15:05
bswartzbut first15:05
bswartz#topic dev status15:05
*** openstack changes topic to "dev status (Meeting topic: manila)"15:05
bswartzvponomaryov: do you have updates like usual?15:06
vponomaryovyes15:06
vponomaryovDev status:15:06
vponomaryov1) Bugfixing.15:06
vponomaryovMain forces were directed to bugfixing this week. Bugs for share networks available on launchpad.15:06
vponomaryov2) BP https://blueprints.launchpad.net/manila/+spec/share-network-activation-api15:06
vponomaryovgerrit: https://review.openstack.org/#/c/71497/ (client)15:06
vponomaryovTODO: server side implementation15:06
vponomaryovGeneric driver - https://review.openstack.org/#/c/67182/15:07
vponomaryovSome improvements. Now, it works much faster using python paramiko module for ssh instead using venv with ssh client...15:07
bswartzlet's talk about (2) briefly15:07
*** esker has quit IRC15:07
*** jswarren has joined #openstack-meeting-alt15:07
*** esker has joined #openstack-meeting-alt15:08
bswartzthe idea behind the share network activation API is that under the original design, we didnt' actually create a vserver until the first share was created15:08
vponomaryovok, anyone have questions about bp https://blueprints.launchpad.net/manila/+spec/share-network-activation-api ?15:08
bswartzthis API allows us to create it early -- which is good for stuff like validating the parameters that were passed in when the share network was created15:08
*** BobBall has left #openstack-meeting-alt15:09
*** esker has quit IRC15:09
*** mestery has joined #openstack-meeting-alt15:09
bswartzCan I assume everything thinks that's a good thing?15:09
vponomaryoveveryone?15:09
bswartzokay silence is consent15:09
bswartzanyone who wants to provide review input to the generic driver, now is the time15:10
bswartzI want to merge this in the next week15:10
vponomaryovbswartz: we too15:11
bswartznote that we may still modify it in the future -- in particular we may do some of the things rraja suggests15:11
aostapenkounittests are in progress, and there will be some minor changes15:11
bswartzbut with I-3 coming I want to have feature completeness for at least a few drivers15:11
vponomaryovalso, want to remind, that generic driver still requires lightweight image with nfs and samba services for generic driver15:12
bswartzvponomaryov: where is that list of requirements documented?15:12
csabavponomaryov: I'm doing some work in that direction15:12
aostapenkobswartz: I think that we should merge what we have now, and then make some changes15:13
vponomaryovbswartz: we haven't documented such stuff15:13
csabahopefully I can present next week15:13
vponomaryovcsaba: thanks15:13
*** Dinny has joined #openstack-meeting-alt15:13
bswartzlet's write down a list of all of the things the generic driver will depend on from the glance image15:13
*** nwidell has joined #openstack-meeting-alt15:13
bswartzobviously an SSH server is required, as well nfs-kernel-server and samba15:13
*** Dinny has quit IRC15:13
bswartzdoes it matter if it's samba3 or samba4?15:14
*** Dinny has joined #openstack-meeting-alt15:14
bswartzare there any other subtle requirements? does the image need cloud-init?15:14
vponomaryovimage should have server and client sides for NFS and Samba15:15
bswartzwhy would the image need NFS/samba clients?15:15
vponomaryovbecause this image can be used as client VM image for mounting shares15:15
bswartzwhat shares would it mount?15:15
vponomaryovunified for both purposes15:15
vponomaryovmanila's shares15:15
bswartzoh you mean rraja's ideas?15:15
aostapenkoit requires cloud init for key injection, but we have alter auth thru password15:15
bswartzlet's hold off on the gateway stuff -- I just want to document what's required for the generic driver15:16
aostapenkowe do not need samba/nfs clients15:16
vponomaryovbswartz: I mean use case, not only creation of share, but using it too. On client's VM15:16
bswartzthere will be additional requirements if we also use these images as gateways15:16
bswartzyes but the client VMs will be some other glance image15:17
bswartzand those images will be tenant-owned15:17
bswartzthis image will be admin-owned15:17
vponomaryovbswartz: yes, it is in wishlist15:17
bswartzokay15:18
bswartz#topic networking15:18
*** openstack changes topic to "networking (Meeting topic: manila)"15:18
bswartzso we were able to make the generic driver work with separate networks last week15:19
*** vgnbkr_1 has joined #openstack-meeting-alt15:19
bswartzeach service VM gets its own service network, and the network is joined to the tenant network with a virtual router15:20
*** matrohon has joined #openstack-meeting-alt15:20
bswartzI'm pretty satisfied that this approach works, but the downside is that we use up 8 IPs (a /29 CIDR) for every service VM15:20
*** mestery has quit IRC15:20
aostapenkobswartz: we can even use clusters in service subnet in future15:21
bswartzalso there's a small chance that the IP we choose for any given service VM conflicts with something in the tenant's universe15:21
*** nosnos has quit IRC15:21
*** mestery has joined #openstack-meeting-alt15:21
bswartzI'm still interested in putting the service VMs directly on the tenant networks if/when we can solve the issues currently preventing that15:22
bswartzscottda: did you discover anything new since last week?15:22
scottdaNothing earth-shattering...15:22
*** mspreitz has quit IRC15:22
*** kevinconway has joined #openstack-meeting-alt15:22
bswartzscotta: do you just want to share with the team what we discussed last week15:22
scottdaThe Neutron people have the idea of a Distributed Virtual Router (DVR)15:22
scottdahttps://blueprints.launchpad.net/neutron/+spec/neutron-ovs-dvr15:23
aostapenkobswartz: not only tenant universe, cloud universe, because tenants networks can be connected15:23
scottdaThey are actively working on this, but don't expect it to be in in Icehouse. Probably will be this summer.15:23
*** betsy has joined #openstack-meeting-alt15:23
bswartzaostapenko: yes but openstack already manages IPs for the whole cloud -- what it doesn't control is what the tenant connects in from the outside world15:24
scottdaIt will do VM-to-VM intra-tenant routing, but for inter-tenant it will still go out to a Network node. It will have slightly better performance, but not quite what manila wants.15:24
bswartzperformance is on motivation15:24
bswartzs/ on/ one/15:25
scottdaWith the proper champion to write the code and push the blueprint, the DVR can, and probably some day will, be enhanced to have a VM-to-VM intra-tenant connectivity option. But that is in the future.15:25
*** sergmelikyan has joined #openstack-meeting-alt15:25
*** ndn9797 has quit IRC15:26
bswartzbut for me the main thing is that hardware-based drivers will actually be able to directly join tenant networks, and it seems better for the generic driver to have the same behavior -- if only for consistency and common testing15:26
scottdaThat is the synopsis15:26
*** yportnova__ has joined #openstack-meeting-alt15:26
bswartzthanks scottda15:27
bswartzso the plan here is -- we're going to continue with aostapenko's approach of creating a /29 for each instance of the generic driver15:27
bswartzhowever we're going to monitor neutron to see if they give us a better alternative in the future15:28
achirkopeople in Neutron are also working on Service VM infrastructure - https://blueprints.launchpad.net/neutron/+spec/adv-services-in-vms15:28
bswartz#topic gateway-mediated15:29
*** openstack changes topic to "gateway-mediated (Meeting topic: manila)"15:29
aostapenkobswartz: we can even extend to /28 if we want to launch clusters of service vms15:29
bswartzachirko: that's also very interesting to me15:29
bswartzI should probalby join some neutron meetings and +1000 that BP15:29
achirkowe can get some feedback from them on our approach, but it probably will slow down Generic Driver delivery15:30
bswartzachirko: we don't need to slow down anything -- we can go forward with the current approach15:30
vbellurbswartz: all of us could probably +1000 that :)15:30
bswartzachirko: if this BP happens we can go back and update15:30
bswartzokay we're on a new topic though15:30
bswartzand since we still don't have rraja, I'll drive15:31
*** NehaV has joined #openstack-meeting-alt15:31
bswartzso I'll repost the link15:31
bswartz#link http://thread.gmane.org/gmane.comp.cloud.openstack.devel/1598315:31
csabaI can talk on behalf of rraja15:31
bswartzoh okay15:31
bswartzcsaba: take it away!15:32
*** NehaV has quit IRC15:32
*** NehaV has joined #openstack-meeting-alt15:32
csabawell the basic idea is that if we think of various storage backends15:32
csabaie. there is Cinder as with generic driver, there could be lvm, ganesha, gluster-nfs whatnot...15:33
csabawhich are implemented or wip as single tenant drives15:34
csaba*drivers15:34
csabarunning on hypervisor15:34
csabanow what they would do in a generic driver like architecture15:34
csabais not much different15:34
*** banix has joined #openstack-meeting-alt15:34
csabajust their activity wouild have to lifted to the service VM15:35
*** david-lyle has joined #openstack-meeting-alt15:36
csabaso what we thought, if the archictecture could be split to a backend exporter and a network plumbing component...15:36
bswartzokay so let me summarize and see if I'm off base15:36
csabathen it would be easy to leverage those other efforts tand use in a multi-tenant way15:36
bswartzwe could implement gateway-mediated access with the following:15:36
*** atiwari has joined #openstack-meeting-alt15:36
bswartz1) add a network connection from the generic driver's service VM to the backend storage network15:37
bswartz2) add filesystem clients to the service VM15:37
*** Barker has joined #openstack-meeting-alt15:38
bswartz3) implement the backend to just serve filesystems to a single storage network15:38
bswartz4) bridge the backend filesystem onto the tenant network using an NFS server in the server VM, either ganesha-nfs or nfs-kernel-server15:38
*** david_lyle_ has joined #openstack-meeting-alt15:39
bswartzis that it?15:39
*** dgenin has quit IRC15:39
*** tanisdl has joined #openstack-meeting-alt15:40
csabawhat you mean by 3)15:40
csaba"single storage network"?15:40
vbellurthat sounds right to me15:40
bswartzI think the same thing you meant by (10:33:59 AM) csaba: which are implemented or wip as single tenant drives15:41
csabaah OK15:41
csabafine15:41
bswartzthe backends for the gateway-mediated mode wouldn't need to understand tenants really15:41
bswartzbecause the VMs would do that translation15:41
*** ijw has joined #openstack-meeting-alt15:42
bswartzokay so I'd like to have some discussion on the difference between ganesha-nfs and nfs-kernel-server in this context15:42
*** yportn___ has joined #openstack-meeting-alt15:42
bswartzdoes redhat have a preference?15:42
*** david-lyle has quit IRC15:43
scottda+1 to flexibility in choice of NFS server15:43
csabawell point in ganesha is having pluggable storage backends15:43
*** yportnova__ has quit IRC15:43
csababut then kernel nfs is more mature / known ... so it's really good to allow a choiec15:44
bswartzhmm15:44
bswartzI kind of don't like giving users an option here15:45
bswartzit seems like supporting both will double the testing effort and chances for bugs15:45
bswartzit would be better to agree on one and implement that i think15:45
bswartzofc that wouldn't stop someone from also adding a patch to support the other -- but I feel like we should have a recommended approach15:45
csabawell we don't need support both15:46
csabaone can be chosen as supported... down the road15:46
*** jcooley_ has joined #openstack-meeting-alt15:46
*** PhilD has joined #openstack-meeting-alt15:46
bswartzso what I'm asking is, do you have a preference at this time?15:46
vbellurbswartz:  how do we have nfs-kernel-server reach out to various storage backends?15:46
csabapoint is to ease development efforts... for various multi-tenant pocs15:47
*** Leonr has joined #openstack-meeting-alt15:47
*** mestery has quit IRC15:47
bswartzvbellur I think nfs-kernel-server layers ontop of VFS inside the Linux kernel, so any filesystem that has a kernel-mode driver will work underneath it15:47
bswartzif you cound FUSE as a kernel-mode driver than I think literally anything will work15:48
*** aignatov is now known as aignatov_15:48
bswartzs/cound/count/15:48
vbellurbswartz: gluster does not have a kernel mode driver and the performance implications of a fuse mount being an export would be pretty bad15:48
*** ijw has quit IRC15:48
bswartzah15:48
bswartzwell that's a fairly good argument for preferring ganesha-nfs then15:49
bswartzesp if redhat wants to be the first working implementation of this mode15:49
*** ijw has joined #openstack-meeting-alt15:49
bswartzanyone see a serious downside to ganesha-nfs?15:49
vbellurbswartz: the very reason we implemented our own NFS server was due to severe performance implications that we experienced with exporting a fuse mount point.15:49
vponomaryovaddition +1 for ganesha can be its possibility to use over linux containers15:49
bswartzvponomaryov: yes I was going to mention that too15:50
vbellurso can we have nfs-ganesha as the default for v1?15:51
*** skostiuchenko has joined #openstack-meeting-alt15:52
vponomaryovvbellur: does ganesha have stable releases for most of distros?15:52
aostapenkoif we use lxc provided by nova, we could not launch other hypervisors vms in the case of single node instalation15:52
bswartzvbellur: yeah that works for me -- although that approach diverges a little more from teh generic driver than nfs-kernel-server would15:52
*** jcooley_ has quit IRC15:53
vbellurvponomaryov: we have packages for CentOS & Fedora. We also can work with Ganesha community for other distros.15:53
bswartzaostapenko: I don't understand your comment15:53
*** michael-yu has quit IRC15:54
*** shakayumi has joined #openstack-meeting-alt15:54
vponomaryovbswartz: he mant, that if we use LXC VMs, we can not use VMs with other hypervisors15:55
bswartzregarding package and distros, I see it as an administrator's job to provide the glance image that will become the service VM -- if RH-based distros are better suited to running gluster and ganesha then administrators will probably choose those15:55
vponomaryovs/mant/meant/15:55
*** sacharya has joined #openstack-meeting-alt15:55
bswartzyeah LXC has various downsides which we discussed a few months ago15:55
aostapenkobswartz: but we should be able to launch other vms in cloud. not service15:55
bswartzbut LXC has some very interesting advantages too -- I want to come back and look at LXC sometime15:56
bswartz#topic open discussion15:57
*** openstack changes topic to "open discussion (Meeting topic: manila)"15:57
bswartzokay anything else before our time is up?15:57
aostapenkobswartz: i had many exciting nights with lxc, it would be great for performance if we use it15:57
*** yportn___ has quit IRC15:57
bswartzaostapenko: lol15:58
*** esker has joined #openstack-meeting-alt15:58
bswartzaostapenko: I know it has much lower overhead which is good for scalability in low-load situations15:58
*** bauzas has quit IRC15:58
*** alagalah has joined #openstack-meeting-alt15:58
*** nwidell has quit IRC15:59
bswartzokay thanks everyone15:59
vbellurbswartz: thanks!15:59
aostapenkothanks, bye15:59
vponomaryovthanks15:59
bswartzsee you next week15:59
scottdabye15:59
*** michael-yu has joined #openstack-meeting-alt15:59
vbellurbye all15:59
bswartz#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
csababye15:59
openstackMeeting ended Thu Feb  6 15:59:57 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
*** vbellur has left #openstack-meeting-alt16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-02-06-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-02-06-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-02-06-15.01.log.html16:00
*** akerr has left #openstack-meeting-alt16:00
*** edhall has joined #openstack-meeting-alt16:01
*** achirko has quit IRC16:02
*** sacharya has quit IRC16:03
*** bswartz has left #openstack-meeting-alt16:04
*** thinrichs has joined #openstack-meeting-alt16:04
*** doug_shelley66 has quit IRC16:04
thinrichsHi all16:05
*** thinrichs has quit IRC16:05
*** doug_shelley66 has joined #openstack-meeting-alt16:06
*** carl_baldwin has joined #openstack-meeting-alt16:06
*** yportnov_ has joined #openstack-meeting-alt16:07
banixthinrichs: hi16:07
alagalahHi all16:08
banixthe meeting got cancelled for today; I sent out an email.16:08
alagalahWasn't sure if we were meeting today16:08
alagalahbanix:  where did you send the email ?16:08
*** kalebpomeroy has left #openstack-meeting-alt16:08
*** eankutse has joined #openstack-meeting-alt16:08
banixYeah people are at OD Summit ....16:08
banixSent it to the dev mailing list16:09
banixtagged for group policy and neutron16:09
alagalahAh ok...16:09
alagalahI only get digests of that, so will have to change that16:09
alagalahHave a good day16:09
*** alagalah has left #openstack-meeting-alt16:09
banixAre there things you guys want to discuss? I know we haven't got to discuss the conflict resolution stuff but hopefully by next week we will be back in regular schedule.16:10
*** jaypipes has quit IRC16:12
*** jmontemayor has joined #openstack-meeting-alt16:13
*** jmontemayor has quit IRC16:14
*** shakayumi has quit IRC16:14
*** jmontemayor has joined #openstack-meeting-alt16:15
*** boris-42_ has joined #openstack-meeting-alt16:15
*** shanks has quit IRC16:16
*** akuznetsov has quit IRC16:16
*** mestery has joined #openstack-meeting-alt16:18
*** vkmc has quit IRC16:18
*** yportnov_ has quit IRC16:19
*** dklyle has joined #openstack-meeting-alt16:19
*** csaba is now known as csaba|afk16:19
*** jjmb has quit IRC16:21
*** shanks has joined #openstack-meeting-alt16:21
*** david_lyle_ has quit IRC16:22
*** jprovazn is now known as jprovazn_afk16:23
*** akuznetsov has joined #openstack-meeting-alt16:29
*** zhiyan has quit IRC16:29
*** jcooley_ has joined #openstack-meeting-alt16:30
*** jasonb365 has joined #openstack-meeting-alt16:30
*** bauzas has joined #openstack-meeting-alt16:33
*** xyang2 has quit IRC16:35
*** sacharya has joined #openstack-meeting-alt16:36
*** dklyle is now known as david-lyle16:37
*** chadlung has joined #openstack-meeting-alt16:37
*** sparkycollier has joined #openstack-meeting-alt16:37
*** vponomaryov has left #openstack-meeting-alt16:37
*** eankutse has quit IRC16:39
*** eankutse has joined #openstack-meeting-alt16:39
*** amrith has quit IRC16:42
*** mestery has quit IRC16:44
*** michael-yu has quit IRC16:48
*** bdpayne has joined #openstack-meeting-alt16:49
*** PhilD has quit IRC16:49
*** gyee has joined #openstack-meeting-alt16:50
*** jcoufal has quit IRC16:52
*** lsmola has quit IRC16:53
*** jtomasek has quit IRC16:54
*** jjmb has joined #openstack-meeting-alt16:55
*** jjmb has quit IRC16:55
*** julienvey has quit IRC16:56
*** mestery has joined #openstack-meeting-alt16:56
*** jcooley_ has quit IRC16:56
*** jcooley_ has joined #openstack-meeting-alt16:57
*** NikitaKonovalov is now known as NikitaKonovalov_16:58
*** mozawa has quit IRC16:58
*** sparkycollier has quit IRC16:59
*** sbalukoff has quit IRC17:00
*** jmontemayor has quit IRC17:00
*** jmontemayor has joined #openstack-meeting-alt17:00
*** mozawa has joined #openstack-meeting-alt17:00
*** michael-yu has joined #openstack-meeting-alt17:01
*** garyk has quit IRC17:02
*** sarob has joined #openstack-meeting-alt17:02
*** akuznetsov has quit IRC17:02
*** DinaBelova is now known as DinaBelova_17:04
*** gilliard has quit IRC17:07
*** sarob has quit IRC17:07
*** kiall has quit IRC17:08
*** GheRivero has quit IRC17:09
*** jecarey has quit IRC17:13
*** michael-yu has quit IRC17:17
*** dripton is now known as dripton_lunch17:20
*** markwash has joined #openstack-meeting-alt17:21
*** markwash has quit IRC17:26
*** Barker has quit IRC17:26
*** doug_shelley66 has quit IRC17:27
*** _nadya_ has joined #openstack-meeting-alt17:29
*** ylobankov1 has joined #openstack-meeting-alt17:36
*** DinaBelova_ is now known as DinaBelova17:37
*** ash|2 has joined #openstack-meeting-alt17:37
*** doug_shelley66 has joined #openstack-meeting-alt17:37
*** julim has quit IRC17:38
*** bcrochet has quit IRC17:38
*** bcrochet has joined #openstack-meeting-alt17:40
*** shanks has quit IRC17:40
*** jcooley_ has quit IRC17:41
*** jcooley_ has joined #openstack-meeting-alt17:42
*** bcrochet has quit IRC17:42
*** akuznetsov has joined #openstack-meeting-alt17:42
*** bcrochet has joined #openstack-meeting-alt17:43
*** shanks has joined #openstack-meeting-alt17:44
*** jjmb has joined #openstack-meeting-alt17:46
*** jecarey has joined #openstack-meeting-alt17:48
*** _nadya_ has quit IRC17:52
*** aignatov_ is now known as aignatov17:53
*** lisaclark1 has quit IRC17:53
*** nati_ueno has joined #openstack-meeting-alt17:54
*** markwash has joined #openstack-meeting-alt17:56
*** rsblendido has quit IRC17:57
*** jmontemayor has quit IRC17:57
*** shanks has quit IRC17:58
*** garyk has joined #openstack-meeting-alt17:58
*** rossella_s has quit IRC17:58
*** harlowja_away is now known as harlowja17:59
*** jasonb365 has quit IRC17:59
*** bob_nettleton has joined #openstack-meeting-alt17:59
*** david_lyle_ has joined #openstack-meeting-alt18:00
*** crobertsrh has joined #openstack-meeting-alt18:01
*** sc68cal_ has joined #openstack-meeting-alt18:01
*** safchain has quit IRC18:02
*** derekh has quit IRC18:02
*** jmontemayor has joined #openstack-meeting-alt18:02
*** julienvey has joined #openstack-meeting-alt18:02
*** david-lyle has quit IRC18:02
*** tmckay has joined #openstack-meeting-alt18:03
*** sarob has joined #openstack-meeting-alt18:03
*** sreshetnyak has joined #openstack-meeting-alt18:03
*** jasonb365 has joined #openstack-meeting-alt18:03
*** mattf has joined #openstack-meeting-alt18:04
*** alazarev has joined #openstack-meeting-alt18:05
*** amcrn has joined #openstack-meeting-alt18:06
SergeyLukjanovsavanna folks, ping18:07
tmckayhere18:07
crobertsrhhello18:07
bob_nettletonhere18:07
*** bauzas has quit IRC18:07
*** paulmo has joined #openstack-meeting-alt18:07
SergeyLukjanovlet's wait for a few mins18:07
*** sarob has quit IRC18:07
SergeyLukjanovjmaron, jspeidel, aignatov18:08
*** shanks has joined #openstack-meeting-alt18:08
*** Barker has joined #openstack-meeting-alt18:08
alazarevo/18:08
aignatov\o/18:08
*** NikitaKonovalov_ is now known as NikitaKonovalov18:08
NikitaKonovalovhi18:08
*** dripton_lunch is now known as dripton18:08
*** sankarshan has quit IRC18:08
SergeyLukjanovlack of HWX folks18:08
*** sankarshan has joined #openstack-meeting-alt18:08
SergeyLukjanov#startmeeting savanna18:09
openstackMeeting started Thu Feb  6 18:09:02 2014 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.18:09
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:09
*** openstack changes topic to " (Meeting topic: savanna)"18:09
openstackThe meeting name has been set to 'savanna'18:09
SergeyLukjanov#topic Agenda18:09
*** paulmo has left #openstack-meeting-alt18:09
*** openstack changes topic to "Agenda (Meeting topic: savanna)"18:09
SergeyLukjanov#link https://wiki.openstack.org/wiki/Meetings/SavannaAgenda18:09
SergeyLukjanov#topic News / updates18:09
*** DinaBelova is now known as DinaBelova_18:09
*** openstack changes topic to "News / updates (Meeting topic: savanna)"18:09
SergeyLukjanovfolks, please18:09
SergeyLukjanovshort update section18:09
SergeyLukjanovylobankov1, ping,18:09
mattfi caused some headaches by filing a bunch of blueprints <- count as an update?18:09
SergeyLukjanovcould you please make a QA update?18:09
ylobankov1I am here18:09
SergeyLukjanovmattf, it's an update for both of us :)18:10
ylobankov1HDP plugin works with Heat18:10
mattfit looks like the cli is in place and supports --name, so we have a solid base for 0.5. i still need to fully vet an edp use case tho18:10
SergeyLukjanovanyway, I have a good news - now we have fully functional async GATE!!18:10
aignatovylobankov1: cool, I saw SUCCEED18:10
SergeyLukjanovmattf, that's awsome!18:10
crobertsrhI've been working on streaming MapReduce in the dashboard.  Along with a few bug fixes to a few bugs that have been around awhile.  I have a question about one of them.18:11
SergeyLukjanovmattf, I think that it could be released in 1-2 weeks18:11
mattfSergeyLukjanov, awesome!18:11
SergeyLukjanovI mean client 0.5.018:11
mattfre gate18:11
aignatovI'm worked all the week on the adding savanna resource to heat18:11
bob_nettletonI'm working on a separate task this week, so not much progress on the diskimage-builder images for HDP.  I hope to submit a patch review within a week.18:11
tmckaymodified java actions are finally rebased on something stable and pass jenkins/ci.  Streaming mapreduce works through the api, but we are including dotted job types to better support the UI.18:11
aignatovprepared the first patch there18:11
NikitaKonovalovI've sent the change introducing pecan/wsme stuff to start v2 api18:11
*** DinaBelova_ is now known as DinaBelova18:11
SergeyLukjanovme and ylobankov1 are working now on extending basic API tests to tempest18:11
*** johnthetubaguy has quit IRC18:11
sreshetnyaki worked on the integration tests for IDH plugin18:12
*** eanxgeek has joined #openstack-meeting-alt18:12
mattfupdate for venza - we have the beginnings of the spark contribution in the dib elements repo18:12
SergeyLukjanovbob_nettleton, great, looking forward for it18:12
*** shanks has quit IRC18:12
aignatovI hope to make series of 3 patches: cluster create on template, full cluster create with all fields and cluster update18:12
mattfNikitaKonovalov, i hope to try that out today/tomorrow18:12
tmckayI started reviewing the v2 API (CR and email thread) and want to discuss 'cancel' of a job during general topics18:12
mattfNikitaKonovalov, if you have any pointers that'll make it easier for me, i'm all ears18:12
alazarevI started investigation on what is needed to support hadoop 2.x18:13
SergeyLukjanovfolks, please, note that the v2 api CR is just an addition of framework with samples, not the new api :)18:13
NikitaKonovalovmattf, here is the link https://review.openstack.org/#/c/63908/18:13
SergeyLukjanovmattf, what's your estimate for cli stuff to be able to release 0.5.0 client and consume it everywhere?18:13
tmckayit's a target to shoot at :)18:13
*** beyounn has joined #openstack-meeting-alt18:14
mattfSergeyLukjanov, i'll check the bps again, but i think we have a good v0 of the cli now18:14
mattfor v11 is maybe a better way to put it18:14
aignatovSergeyLukjanov: I'd like to see full unit tests set for 0.5 release of savannaclient18:14
aignatov#link https://blueprints.launchpad.net/python-savannaclient/+spec/python-savannaclient-unit-tests18:14
tmckaymattf, with the java action changes currently staged, we can drop "job_exec_data" from the client create() as long as we sync the merges between savanna api/UI and the client18:15
mattfcrobertsrh, ^^18:15
*** sarob has joined #openstack-meeting-alt18:15
mattftmckay, i need to catch up on that, help me after this meeting?18:15
crobertsrhYeah, I'm on it.18:15
tmckaymattf, sure.18:15
crobertsrhI think I have that change ready to go.18:15
tmckayMy plan was to start looking at cli tests this week, but I was mired in rebases18:16
tmckayMaybe now I have a chance18:16
alazarevI like how novaclient is tested by UT, probably we need to do the same thing18:16
SergeyLukjanovaignatov, it sounds reasonable, but we have a good integration tests coverage for latest released version, probably, we should adopt the jobs to test client too18:16
aignatovNews/updaes section of this meeting turned to General discussions :-)18:17
SergeyLukjanovaignatov, I'm not sure that we have enough bandwidth to resolve it before the mid of i318:17
SergeyLukjanovand to the i3 dev status18:17
SergeyLukjanov#topic i3 dev status18:17
*** openstack changes topic to "i3 dev status (Meeting topic: savanna)"18:17
aignatovSergeyLukjanov: I can make it possibly18:17
SergeyLukjanov#link https://launchpad.net/savanna/+milestone/icehouse-318:17
SergeyLukjanovaignatov, It'll be great to have a first release of client with tests :)18:17
*** NikitaKonovalov is now known as NikitaKonovalov_18:17
SergeyLukjanovand probably enable support of py3k, I can help with it18:18
*** shanks has joined #openstack-meeting-alt18:18
mattfi'm still looking for +1s and +2s on the api endpoints - https://review.openstack.org/#/c/70627/18:18
SergeyLukjanovfolkd, please, take a look at https://launchpad.net/savanna/+milestone/icehouse-3 and say what's missed18:18
*** arnaud___ has joined #openstack-meeting-alt18:18
*** arnaud__ has joined #openstack-meeting-alt18:18
SergeyLukjanovor what should be postponed so far18:18
SergeyLukjanovjmaron, jspeidel, ping18:19
SergeyLukjanovheh18:19
mattfSergeyLukjanov, i'll review and make suggestions on #savanna later18:19
SergeyLukjanovthx18:19
SergeyLukjanovI'd like to ask all of us to check their blueprints statuses18:19
SergeyLukjanovand if you're working on blueprint that isn't targeted to i3, please, ping me18:20
*** sarob has quit IRC18:20
*** IlyaE has joined #openstack-meeting-alt18:20
*** Duane_ has joined #openstack-meeting-alt18:20
aignatovhm, it seems already implemented https://blueprints.launchpad.net/savanna/+spec/epd-data-source-existing-hadoop-cluster18:20
SergeyLukjanovwe'll enable soft feature freeze after i318:20
*** amrith has joined #openstack-meeting-alt18:20
*** mestery has quit IRC18:20
*** dmitryme has joined #openstack-meeting-alt18:21
SergeyLukjanovaignatov, agreed, both server side and dashboard side merged18:21
*** jcooley_ has quit IRC18:21
aignatovsreshetnyak: here?18:21
SergeyLukjanovneed to confirm it with Trevor and Chad18:21
sreshetnyakhere18:21
*** NikitaKonovalov_ is now known as NikitaKonovalov18:21
aignatovYou was assigned on external hdfs. is it fully completed?18:22
crobertsrhI believe it is completed18:22
*** DinaBelova is now known as DinaBelova_18:23
*** david_lyle_ is now known as david_lyle18:23
sreshetnyakneed to add integration tests18:23
tmckayI haven't used it for an external cluster, but I have run it with hdfs data sources on the same running cluster18:23
mattf+1.518:24
aignatovI ran it on external hdfs with earliest patches of this commit ;)18:24
SergeyLukjanovok, I've mark it implemented18:24
aignatovit worked18:24
SergeyLukjanovany questions?18:24
aignatovon my laptop ;-)18:24
mattfheh18:24
mattf+.518:24
aignatovmatff, don't you trust my laptop?18:25
tmckayI think all my currently approved blueprints will be implemented very soon, with maybe the exception of https://blueprints.launchpad.net/savanna/+spec/edp-oozie-files-and-archives18:25
tmckayfiles and archives are not strictly necessary -- streaming mapreduce can use 'libs' to bundle files if a script needs to be uploaded18:26
tmckaybut they would be nice on a long-running cluster18:26
mattfaignatov, just getting it to +218:27
crobertsrhI have a question regarding https://bugs.launchpad.net/savanna/+bug/1212354  It's a bug against the UI that happens when you empty out a parameter from the HDFS config tab for a cluster template (or probably most tabs).  The client treats it as ok because the plugin returns a config set that sets those values as optional.  Who would be the right person to talk to about this?18:27
crobertsrhI should say that the dashboard treats it as ok ^^^18:29
*** jmaron has joined #openstack-meeting-alt18:29
mattfjmaron, welcome18:29
jmaronsorry I'm late18:30
SergeyLukjanovjmaron, hey, any updates?18:30
jmaronlost track of time...18:30
mattfall that time in the break room18:30
jmaronputting finishing touched on HDP 2 integration18:30
jmarontouches18:30
jmaronshould have something for review today or tomorrow18:31
jmaronI'd like to commit an initial patch that addresses functionality18:31
aignatovcrobertsrh: I'll try to take a  look on this bug tomorrow18:31
jmaronwith the understanding that there'll be a follow up commit with some needed refactorings18:31
mattfjmaron, you know i'm a fan of phasing changes18:32
crobertsrhaignatov:  Thanks.  Let me know what you think about it.  I may be able to tweak the dashboard if necessary, but I think it would be rather ugly.18:32
jmaronI think doing the refactorings at this time will make the patch unwieldy…18:32
*** yogesh has joined #openstack-meeting-alt18:32
jmaronso no comments about duplicate code ;)18:32
mattffair enough18:33
aignatovcrobertsrh: agreed, when I'll figure out whats happening I'll comment to the bug or to you in channel :)18:33
crobertsrhSounds good18:33
mattfbob_nettleton, btw, i'm eagerly awaiting your dib patches. are you planning to separate out the java & ssh elements at the same time?18:34
*** GheRivero has joined #openstack-meeting-alt18:34
*** julienvey has quit IRC18:35
*** julienvey has joined #openstack-meeting-alt18:35
SergeyLukjanovok, let's move on18:35
bob_nettletonmattf, not in the initial patch submission, but I do think it makes sense to break these out into common elements.  My hope was to get the initial submission in, and then I could refactor the scripts once the common elements were available.18:35
mattfbob_nettleton, should the refactoring bps be assigned to you?18:36
*** sankarshan has quit IRC18:36
*** sankarshan has joined #openstack-meeting-alt18:36
bob_nettletonmattf, sure, that would be ok for now.  if my task assignments change, we might need to re-assign, but I could certainly take a look at this.18:37
mattfbob_nettleton, ok18:37
bob_nettletonmattf, should the common elements go in DIB itself, or in savanna-image-elements?18:37
*** akuznetsov has quit IRC18:37
*** ndipanov is now known as ndipanov_gone18:37
mattfimho, we should try to get all our elements into dib itself. only truly general ones will make the cut.18:37
SergeyLukjanovbob_nettleton, I think the first step is complete them in s-i-e18:37
mattfso you can file a review against both. in the past i'ev filed against dib and when rejected filed against savanna18:38
bob_nettletonSergeyLukjanov, mattf, ok, sounds fine.  thanks!18:38
SergeyLukjanov#topic Project naming collision18:38
*** ijw has quit IRC18:38
*** openstack changes topic to "Project naming collision (Meeting topic: savanna)"18:38
SergeyLukjanov#link https://etherpad.openstack.org/p/savanna-renaming18:38
SergeyLukjanovthere are some proposed options alreadt18:39
SergeyLukjanovlet's continue discussion of new name in this etherpad18:39
mattfdo we have a deadline?18:39
SergeyLukjanovI'm thinking about setting up a voting to cut top XX options18:39
SergeyLukjanovin 1-1.5 weeks18:39
aignatovwe need much more proposed names18:40
*** igor has quit IRC18:40
mattfwe do18:40
mattfis openstack legal giving us a deadline?18:40
aignatovtop XX means 20?18:40
SergeyLukjanovI'd like to select the new name around the i318:40
SergeyLukjanovaignatov, I hope 518:40
alazarevSergeyLukjanov: did you ask about Savannah?18:40
SergeyLukjanovmattf, there is now hard deadline18:40
mattfare there milestones set, such as needing to be fully transitioned by i ga?18:40
SergeyLukjanovmattf, but if we'd like to graduate from the incubation :)18:41
dmitrymeHey, by the way, are you going to present all the options on the voting, or we will filter out some of them before?18:41
mattfSergeyLukjanov, you speak the magic words...18:41
*** mestery has joined #openstack-meeting-alt18:41
*** troytoman-away is now known as troytoman18:41
mattfso we need to fully rename by I. we need to get through legal w/ the new name before we rename, and we need to prune the list before giving it to legal?18:41
SergeyLukjanovdmitryme, I'd like to have several iterations18:41
SergeyLukjanovmattf, yup18:42
mattfare there any estimates on how long renaming takes and how long legal needs?18:42
dmitrymeSergeyLukjanov: yes, seems like a good idea. So at the first iteration we will review all the options and select, say 20 of them, right?18:42
SergeyLukjanovmattf, and it'll be the best option to have a new name around i3 == before the graduation review18:42
aignatovdmitryme: I guess so18:42
*** jjmb1 has joined #openstack-meeting-alt18:42
SergeyLukjanovmattf, <=1w for legals I hope, ~1-2w for renaming18:43
mattfSergeyLukjanov, so i3 - legal time == our deadline18:43
*** jjmb has quit IRC18:43
SergeyLukjanovmattf, yup, that's the best case18:43
mattfi just started soliciting names at rht, so i'd like to go on the 1.5-2wk for vote end18:44
*** igor has joined #openstack-meeting-alt18:44
SergeyLukjanovi3 == Mar 618:44
SergeyLukjanovso, we have 4 w18:44
*** beyounn has quit IRC18:45
mattfis legal going to output a single name or a further pruned list?18:45
*** NikitaKonovalov is now known as NikitaKonovalov_18:45
*** gokrokve has joined #openstack-meeting-alt18:46
mattf...do we need a second round of name voting...18:46
aignatov"noooo, please, please let's us leave our beautiful name Savanna..." - we will write to legals :)18:46
mattfaignatov, i'll +1 that name18:46
SergeyLukjanovmattf, legal could check a short list of names for us18:46
mattfso 4w - 1w voting round 2 - 1.5w legal - 1w voting round 1 == we need to start voting in a week. ok.18:47
mattfi retract my request for 2weeks, thx18:48
SergeyLukjanovI'd like to start voting right after the next meeting18:48
SergeyLukjanovprobably, we'll need to discuss something18:49
aignatovSergeyLukjanov: you mean first round of voting, right?18:49
SergeyLukjanovand I'll setup up for a week, but if it'll collect enough votes, it could be ended earlier18:49
SergeyLukjanovaignatov, yup18:49
aignatovok18:49
SergeyLukjanovhonestly, I don't see any good options now :( Savanna is too own...18:50
*** jprovazn_afk has quit IRC18:50
SergeyLukjanovheh18:50
SergeyLukjanov#topic General discussion18:50
*** openstack changes topic to "General discussion (Meeting topic: savanna)"18:50
*** NikitaKonovalov_ is now known as NikitaKonovalov18:51
SergeyLukjanovany questions/ideas?18:52
mattfaignatov, alazarev, tmckay, crobertsrh, any comments on the base v2 api?18:52
tmckayI would like to reconsider job "cancel" in v2 api18:52
tmckayThe reason:18:52
alazarevmattf: looks good for me18:52
tmckaycrobertsrh notes that job relaunch is implemented on the job executions tab18:52
SergeyLukjanovmattf, probably I missed it, but do you have any general api changes section?18:52
mattftmckay, reconsider? nothing is decided on it atm, just not listed in base.18:52
crobertsrhI tend to agree with tmckay.18:53
SergeyLukjanovmattf, like don't include tenant-id to url?18:53
tmckayso, the use case is cancel a job, tweak the data or configs, and relaunch18:53
*** Ranjitha has joined #openstack-meeting-alt18:53
tmckaymattf, my mistake.  I thought missing meant gone :)18:53
mattfSergeyLukjanov, i focused on the endpoints18:53
SergeyLukjanovmattf, ok18:53
*** nacim has quit IRC18:53
mattftmckay, so it's a stop + modify + restart use case?18:54
aignatovfor long running jobs the 'cancel' operation is extremely needed18:54
*** lisaclark1 has joined #openstack-meeting-alt18:54
*** chadlung has quit IRC18:54
tmckaymattf, yes18:54
mattfaignatov, do you see cancel == stop ?18:54
aignatovyep, stop it running on cluster18:54
mattfaignatov, stop cluster or stop job?18:55
aignatovstop job18:55
*** tanisdl has quit IRC18:55
mattfas in, for a transient cluster. does the clsuter survive the stop + restart?18:55
*** sbalukoff has joined #openstack-meeting-alt18:55
tmckaygood question18:55
aignatovtransient custer is another case :)18:56
crobertsrhI would say that transient cluster goes away18:56
SergeyLukjanovit'll be killed in current code18:56
aignatovcluster should be killed, yes18:56
mattfif it's killed, the stop + edit + restart ~= delete + edit + launch new18:56
tmckayexcept that delete wipes it from the database, so you have to start from scratch.  Maybe a little more typing18:57
mattfanother way is "clone" a running job. so "clone w/ edit" then delete old.18:57
aignatovI said about 'cancel' jobs mostly targeted to persistent clusters (not transient)18:58
*** jcooley_ has joined #openstack-meeting-alt18:58
mattfi'm just tossing out ideas that don't require us to add another verb, but give us the same use case.18:58
mattffyi, clone can be done entirely client side18:58
*** ruhe_ has joined #openstack-meeting-alt18:59
mattfmay be out of time, -> #savana19:00
mattfmay be out of time, -> #savanna19:00
SergeyLukjanovexactly19:00
*** troytoman is now known as troytoman-away19:00
SergeyLukjanov#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Thu Feb  6 19:00:12 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-02-06-18.09.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-02-06-18.09.txt19:00
SergeyLukjanovthanks everyone19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-02-06-18.09.log.html19:00
mattfciao19:00
*** mattf has left #openstack-meeting-alt19:00
*** krtaylor has quit IRC19:01
*** ylobankov1 has left #openstack-meeting-alt19:01
*** lisaclark1 has quit IRC19:01
*** bob_nettleton has left #openstack-meeting-alt19:02
*** balajiiyer has joined #openstack-meeting-alt19:02
*** balajiiyer1 has joined #openstack-meeting-alt19:05
*** balajiiyer has quit IRC19:07
*** NikitaKonovalov is now known as NikitaKonovalov_19:09
*** DinaBelova_ is now known as DinaBelova19:14
*** chadlung has joined #openstack-meeting-alt19:14
*** NikitaKonovalov_ is now known as NikitaKonovalov19:15
*** lisaclark1 has joined #openstack-meeting-alt19:17
*** mestery has quit IRC19:19
*** ftcjeff has quit IRC19:19
*** ftcjeff has joined #openstack-meeting-alt19:19
*** jwalls has joined #openstack-meeting-alt19:20
*** ftcjeff has quit IRC19:20
*** NikitaKonovalov is now known as NikitaKonovalov_19:23
*** kiall has joined #openstack-meeting-alt19:24
*** ruhe_ has quit IRC19:27
*** NikitaKonovalov_ is now known as NikitaKonovalov19:28
*** garyk has quit IRC19:30
*** sarob has joined #openstack-meeting-alt19:30
*** betsy has quit IRC19:31
*** tanisdl has joined #openstack-meeting-alt19:31
*** NikitaKonovalov is now known as NikitaKonovalov_19:32
*** jjmb1 has quit IRC19:34
*** jcooley_ has quit IRC19:35
*** bdpayne has quit IRC19:36
*** jcooley_ has joined #openstack-meeting-alt19:36
*** gokrokve has quit IRC19:36
*** NikitaKonovalov_ is now known as NikitaKonovalov19:38
*** NikitaKonovalov is now known as NikitaKonovalov_19:39
*** jcooley_ has quit IRC19:40
*** jcooley_ has joined #openstack-meeting-alt19:41
*** SushilKM has joined #openstack-meeting-alt19:42
*** SushilKM has left #openstack-meeting-alt19:42
*** bdpayne has joined #openstack-meeting-alt19:42
*** sarob has quit IRC19:44
*** jcooley_ has quit IRC19:45
*** sarob has joined #openstack-meeting-alt19:45
*** beyounn has joined #openstack-meeting-alt19:48
*** d0ugal has quit IRC19:49
*** NehaV1 has joined #openstack-meeting-alt19:49
*** zhiyan has joined #openstack-meeting-alt19:49
*** jcooley_ has joined #openstack-meeting-alt19:50
*** lblanchard has quit IRC19:52
*** NehaV has quit IRC19:52
*** jbernard has joined #openstack-meeting-alt19:53
*** NehaV has joined #openstack-meeting-alt19:53
*** NehaV1 has quit IRC19:53
*** sarob has quit IRC19:54
*** sarob has joined #openstack-meeting-alt19:54
*** jokke_ has joined #openstack-meeting-alt19:55
*** aignatov is now known as aignatov_19:56
*** jcooley_ has quit IRC19:56
*** jwalls has quit IRC19:57
*** ftcjeff has joined #openstack-meeting-alt19:57
*** jcooley_ has joined #openstack-meeting-alt19:57
*** sarob has quit IRC19:59
*** dmitryme has quit IRC19:59
*** Dinny has quit IRC19:59
markwash#startmeeting glance20:00
openstackMeeting started Thu Feb  6 20:00:16 2014 UTC and is due to finish in 60 minutes.  The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: glance)"20:00
openstackThe meeting name has been set to 'glance'20:00
markwashroll call!20:00
arnaud__hi20:00
markwasho/20:00
flwango/20:00
*** crobertsrh has left #openstack-meeting-alt20:01
brianro/20:01
*** brianr is now known as rosmaita20:01
markwashpehw20:01
ativelkovo/20:01
markwashs/eh/he/20:01
jokke_\o20:01
markwashlooks like we have some artifact folks today?20:01
markwashhuzzah20:01
markwashagenda is here20:02
*** jasonb365 has quit IRC20:02
ativelkovWe are here, yeah. At least I am20:02
markwash#link https://etherpad.openstack.org/p/glance-team-meeting-agenda20:02
markwashI made a pass through all the i3 stuff we care most about and added notes20:02
markwashso we'll see how far we can get through that20:02
markwashbut first I think we had some carryover discussion about glance.store20:03
markwash#topic glance.store20:03
*** openstack changes topic to "glance.store (Meeting topic: glance)"20:03
*** jmontemayor has quit IRC20:04
markwashTBH I'm not sure what discussion exactly is needed at this point20:04
markwashand flaper87 is . . not(?) here20:04
arnaud__I saw a change20:04
*** HenryG_ has quit IRC20:04
arnaud__where is is moving the scrubber20:04
markwashindeed, i think that has merged at this point20:05
arnaud__not sure if it has been merged yet20:05
*** HenryG_ has joined #openstack-meeting-alt20:05
arnaud__ok20:05
*** jasonb365 has joined #openstack-meeting-alt20:05
*** HenryG_ has quit IRC20:05
arnaud__the point that I would like to discuss is the timeline20:05
arnaud__for the change20:05
*** Barker has quit IRC20:05
markwashmy questions about glance.stores are mostly process-oriented. . how do we set up the repo, and what coordination is needed with other folks / infra etc20:05
markwasharnaud__: are you seeing it as more of an early juno thing?20:06
*** ashwini has joined #openstack-meeting-alt20:06
arnaud__yes20:06
markwashI could see that20:06
arnaud__but flaper87 had another point of view20:06
arnaud__:)20:06
markwashah20:06
*** HenryG has joined #openstack-meeting-alt20:06
arnaud__we can discuss later since he is not here20:06
flwangmarkwash: I don't think it can complete in Icehouse20:07
*** demorris has quit IRC20:07
markwashyes, I think perhaps we should do that, arnaud__ can you try to pin flaper87 down to a time to discuss in #openstack-glance ?20:07
markwashsometime soon I hope20:07
arnaud__ok sure20:07
markwashall right, let's hear his point of view a bit later then, and move on for now20:08
markwash#topic artifacts api20:08
*** openstack changes topic to "artifacts api (Meeting topic: glance)"20:08
markwashThis week I had a f2f meeting with some mirantis folks about how we will move forward with team integration / coordination with the artifacts api20:08
markwashI've also been speaking with jbernard about the instance template, which is related20:09
*** _nadya_ has joined #openstack-meeting-alt20:09
markwashWe had a few takeaway items from the f2f meeting that I wanted to share here20:09
*** jasonb365 has quit IRC20:09
markwash1) we're going to try to just integrate the artifacts work into the normal glance team rather than having separate teams20:09
*** bauzas has joined #openstack-meeting-alt20:10
flwangmarkwash: cool20:10
markwashwhich will probably mean bringing on more devs to the meeting and core members etc20:10
markwashand for a good while there will probably be a bit of an expertise gap as the two silos are joined20:10
flwangmarkwash: nice20:10
*** soniarvind has joined #openstack-meeting-alt20:10
markwashbut I think we can evolve past that, especially as we figure out how to integrate images into the artifacts work20:11
jbernardfrom what ive read so far, the artifact design should accomodate instance-templates nicely20:11
markwash2) we'll discuss the progress of the artifacts stuff from folks who are working on it in the weekly meeting20:11
ativelkovYes, we just don't need to hurry with this: better have slow progress then to break something20:11
*** jmontemayor has joined #openstack-meeting-alt20:12
markwashas a status checkin and as an opportunity to ask questions20:12
markwashI put some links to the design work and initial blueprint in the agenda20:12
markwash#link https://blueprints.launchpad.net/glance/+spec/metadata-artifact-repository20:12
*** jcooley_ has quit IRC20:12
*** michael-yu has joined #openstack-meeting-alt20:12
markwash#link https://etherpad.openstack.org/p/MetadataRepository-ArtifactRepositoryAPI20:12
markwash#link https://etherpad.openstack.org/p/MetadataRepository-API20:12
*** jcooley_ has joined #openstack-meeting-alt20:12
markwashI think the theory was that tims, a heat guy, would be proposing some code around the api soonish that we could at least look at / keep WIP for a while20:13
markwashbut I've not seen anything yet, is anyone in a position to contact tims to check on his status?20:13
* flaper87 is back20:14
flaper87sorry I'm late guys20:14
markwashbetter late than never20:14
markwashokay maybe I'll try to follow up with tims to see what's going on20:14
markwash#action markwash track down tims and get status20:14
ativelkovI may ask gokrokve to contant tims20:14
*** Barker has joined #openstack-meeting-alt20:15
markwashativelkov: good idea20:15
markwashjbernard: any status for us on the instance templates stuff? what's your initial angle of attack?20:15
ativelkovok, as soon as he appears around, I'll tell him20:15
jbernardmarkwash: the artifact design should be perfect20:16
markwashokay cool20:16
jbernardmarkwash: the type would be 'instance' or something like this20:16
jbernardmarkwash: and the associated metadata would contain the block device mapping20:16
arnaud__markwash: some parts are still not very clear to me. Espcially, the upload/download and the metadata part.20:16
markwashjbernard: great to hear20:17
arnaud__let's say, you want to download an artifact, what happens? what do you get?20:17
markwashjbernard: so are you sort of blocked/waiting on more progress with artifacts stuff?20:18
jbernardmarkwash: i was going to raise that here actually20:18
soniarvindHi guys, My name is Arvind and I work as OpenStack PM @ VMware. joining the glance IRC for first time. Look forward to learn more about artifacts and other blueprints.20:18
*** sarob has joined #openstack-meeting-alt20:18
markwashsoniarvind: hi good to have you20:18
markwasharnaud__: (not ignoring you, I will come back to your point in one sec)20:19
arnaud__:) cool thks markwash :)20:19
jbernardativelkov: you published the artifact blueprint/etherpads?20:19
*** demorris has joined #openstack-meeting-alt20:19
ativelkovjbernard: not yet, working on that now20:19
markwashjbernard: so the issue right now is, without artifact api structure, there's not really a place for you to code /design stuff, right?20:20
markwashor are you raising some other issue?20:20
jbernardyeah, we need a consensus on direction20:20
jbernardat least, that's my current take20:20
markwashokay makes sense20:21
jbernardthe artifact direction is a good one IMO20:21
markwashjbernard: do you think it would make sense to come up with the list of attributes you would expect the instance template to have?20:21
*** alazarev has quit IRC20:21
jbernardyes20:21
jbernardativelkov: maybe we can sync up when you're at a stopping point in your design20:22
markwashI suggest that because it seems it *might* help drive /verify some of the artifact discussion20:22
markwashfor example, it would be neat if we figure out the set of acceptable answers to arnaud's download/upload question for instances20:22
*** RajeshMohan has quit IRC20:22
ativelkovjbernard: sure. I'll write to the ML as soon as we are ready20:22
jbernardyeah i agree, arnaud__ raises some good questions20:23
*** RajeshMohan has joined #openstack-meeting-alt20:23
jbernardok, based on what I see so far, there is enough to agree on a basic design20:23
markwashokay, it seems like jbernard you have a little bit of a way to move in terms of defining what an instance template would need to include, so let's take a quick look at arnaud's question in more detail, and then see in what form we need to follow up after the meeting20:23
rosmaitaarnaud__: that is a good question ... i think we should follow how it's done with images, /v2/artifact/uuid would give you metadata record, /v2/artifact/uuid/file would give you the data (i.e., the actual artifact)20:24
jbernardwhen ativelkov pushes to the list, then we can hammer out the details20:24
*** _nadya_ has quit IRC20:24
markwashrosmaita: that's a valid approach but I'd love to let the folks driving the artifact api make their suggestion as part of a general proposal20:24
arnaud__markwash: +120:24
markwashmostly wanting to avoid committee design, preferring instead committee review20:25
arnaud__ativelkov: I will let you know my concerns with more details, this way you keep that in mind20:25
arnaud__while designing :)20:25
ativelkovok, sure20:25
markwasharnaud__: so specifically, it seems like you are concerned about what the path is for a consuming service to get an artifact for use20:25
jbernardativelkov: i will send you what an instance template would need to include20:26
arnaud__yes20:26
markwashso I think the we can take that as a request for specific info in any design info20:26
markwashugh20:26
markwashany design info -> any design doc20:26
markwashativelkov: are you doing the initial design? or is it still a question we need to answer after tracking down tims ?20:27
ativelkovI would prefer to sync up with tims, yes20:27
markwashokay great20:28
markwashso, to summarize20:28
*** jcoufal has joined #openstack-meeting-alt20:28
markwash#action ativelkov markwash track down tims somehow and get status, answer the quesiton who is designing this thing20:28
markwash#action jbernard look into instance template requirements and make any thoughts available to artifact api workers20:29
markwashokay20:29
jbernardsounds good20:29
markwashanything else on this topic before we jump into blueprint hell ? :-)20:29
*** sarob has quit IRC20:29
ativelkovnot from my side :)20:29
* markwash opens nether portal20:29
markwash#topic I-3 blueprints20:30
*** openstack changes topic to "I-3 blueprints (Meeting topic: glance)"20:30
markwashFirst one: image-recover (flwang)20:30
*** sarob has joined #openstack-meeting-alt20:30
markwasharen't you glad your baby woke you up for this? :-)20:30
markwash#link https://blueprints.launchpad.net/glance/+spec/image-recover20:30
flwangyep, since I don't want to miss this one20:30
markwashthere is a changeset20:30
markwash#link https://review.openstack.org/6168020:31
*** soniarvind has quit IRC20:31
markwashbut its abandoned20:31
flwangI will submit a patch soon to restore20:31
markwashI have a few questions20:31
flwangit will depends on zhiyan's location status patch20:31
*** soniarvind has joined #openstack-meeting-alt20:31
flwangsure20:31
markwash1) how does a user find out an image/ image location is pending delete ?20:31
markwashbecause I thought we didn't want to expose that to users at all20:31
zhiyanflwang: may i know what's kind of dependencies there?20:31
markwash2) should this be admin-only? how do we make it admin-only? will it be a burden if it is admin-only but still shows up in the api docs as a valid path for users?20:32
flwangmarkwash: I'd like to let the admin can list the images which are in 'pending-delete' status20:32
flwangzhiyan: recover the location from 'pending-delete' to 'active' as well20:32
flwangmarkwash: 2) yes20:33
markwashflwang: can we do it in a way where it does not affect the user-facing api then?20:33
zhiyanflwang: IMO even we have no location status, we can also do pending-delete => active, no?20:33
flwang2) if the user is not admin, he will run into NotFound error IIRC20:33
markwashI'm probably just being a bit stodgy, but I'm very hesitant to change the api for this without more operations folks breaking down my door for this feature20:33
flwangzhiyan: yes, but it will be ugly and more work20:34
*** sarob has quit IRC20:34
markwashflwang: I seem to recall an ML discussion around this, am I correct?20:35
arnaud__flwang: are you also working on the glance-client part?20:35
markwash*this feature20:35
flwangmarkwash: I'm going to add a new api like images/xxx/recover20:35
*** nikhil is now known as nikhil-brb20:35
*** ackerman80 has joined #openstack-meeting-alt20:35
flwangmarkwash: nope? but I'd like to send it if it's necessary :)20:36
markwashthe api design for this feature doesn't feel right to me20:36
markwashI can't really make a clear argument as to why, however20:36
zhiyanflwang: i'm a little confused tbh, seems you are trying to do location-recover but image-recover, am i right? i think they are different20:36
arnaud__zhiyan: +120:37
flwangzhiyan: nope20:37
markwashI guess it seems like image-recover should be separate from the user api completely20:37
zhiyanflwang: since if you doing latter one, maybe* we need a api to list "pending-delete" location instead of image ..20:37
markwashflwang: yeah, an ML discussion, especially if you could include openstack-operators would be nice20:37
flwangzhiyan: when the image is in 'pending-delete', what's the status of location?20:37
zhiyandeleted, currently20:38
markwashI'm tempted to suggest we move this one to J just becuase I"m not yet comfortable with exposing /v2/images/xxx/recover in the main images api20:38
flwangmarkwash: I'm ok20:38
zhiyan+0.5 :)20:38
markwashflwang: you're okay with moving it to J?20:38
rosmaita+0.5 == +120:39
*** krtaylor has joined #openstack-meeting-alt20:39
flwangmarkwash: I'm ok20:39
markwashheh20:39
*** nikhil-brb is now known as nikhil20:39
markwashadding notes in etherpad20:40
zhiyanrosmaita: 0.5 : J is make more sense. but i personally think it will be nice if we can think about my above question..20:40
markwash"Move to J to address concerns about where this is exposed and how it affects pending-deleted locations"20:40
markwashzhiyan: yes, I agree with the idea behind that question20:40
markwashit would be neat if we had an admin only api that said "here are the pending-delete locations" and put /recover on that20:40
markwashbut let's defer that conversation, a lot more bps to look at20:40
markwashNext up! glance.stores flaper8720:41
flwangmarkwash: yes20:41
flaper87o/20:41
zhiyanmarkwash: sure20:41
*** alazarev has joined #openstack-meeting-alt20:41
flwangpending-delete location maybe another topic20:41
*** alazarev has quit IRC20:41
markwashflaper87: there was  a motion to push off the glance.stores integration to J, I'm not actually sure what steps we need to take and when they could happen20:41
markwashflaper87: do you wanna discuss outside this meeting or do you have some quick notes for us?20:41
markwash(if we don't get through all the blueprints I can track down folks offline)20:42
flaper87markwash: I can do both, whatever is best for the meeting. Perhaps, I could start sharing the steps I'm trying to follow20:42
flaper87and we can discuss this based on that20:42
markwashflaper87: that would be fantastic20:42
flaper87ok20:42
flaper87very quickly so I don't get other folks time20:42
markwash#action flaper87 to share steps / timeline for glance.stores for future followup20:43
flaper87markwash: should I do it now? or later in the channel ?20:43
flaper87I can write an ehterpad20:43
flaper87that would be even better20:43
markwashlet's go for later20:43
flaper87+120:43
markwashflaper87: maybe you can try to coordinate a time to discuss with us as well?20:44
zhiyanflaper87: maybe we can reuse https://etherpad.openstack.org/p/right_place_for_glance.store_modules20:44
markwashI should be generally available ish :-)20:44
markwashokay I'm going to skip around to try to hit the easier ones20:44
markwashthe following in my view just need more review attention20:44
markwashcross-service-request-id tracking20:45
markwash#link https://review.openstack.org/#/c/68524/20:45
markwashexpose-owner-in-v220:45
markwash#link https://review.openstack.org/#/c/69887/20:45
markwashimage-locaiotn-selection-strategy20:45
markwash#link https://review.openstack.org/#/c/58482/20:46
markwashand related to that is getting glance tests on testrepository which is working okay for me now20:46
markwash#link https://review.openstack.org/#/c/59699/20:46
*** colinmcnamara has joined #openstack-meeting-alt20:46
flwangmarkwash: I saw there is a +2 from zhiyan, so it would be nice if there is anyone can approve it soon20:46
*** chadlung has quit IRC20:47
flwanghttps://review.openstack.org/#/c/69887/20:47
markwashokay20:47
markwashI'll look again, maybe that's all we need20:47
zhiyanflwang:  for https://review.openstack.org/#/c/69887/ , yes, i think it wil be better if we add a "docImpect" flag20:47
flwangmarkwash: cool20:47
markwashnext: i18n-messages20:47
markwashflwang: any plans for this one in the next few weeks? or defer it to J ?20:48
markwash#link https://blueprints.launchpad.net/glance/+spec/i18n-messages20:48
flwangmarkwash: pls don't defer it :D20:48
markwashokay cool20:48
markwashbut we'll look again next week if there is anything to review ;-)20:48
flwangmarkwash: we can complete it if the reviewers can follow up :)20:48
flwangmarkwash: I think it's the only patch20:49
markwashnext: community-level-v2-sharing (rosmaita )20:49
markwash#link https://blueprints.launchpad.net/glance/+spec/community-level-v2-image-sharing20:49
markwashrosmaita: let's go ahead and make iccha the assignee, sound okay?20:49
rosmaita+120:49
markwashand I think we'll want at least an initial patch in the next 12 days20:49
*** eanxgeek is now known as eanxgeek|log20:50
rosmaitashe's travelling right now, but if she were here, she would say "no problem"20:50
markwashnice20:50
ashwinishe probably wont be able to get started on this until mid next week though20:50
markwashI'll trust you20:50
markwashashwini: :-)20:51
markwashlet's give it a shot20:51
markwashnext: workers  / tasks20:51
markwashI see there's a lot of discusison about this on in the agenda etherpad20:51
nikhiladded some comments in the etherpad20:51
nikhilyep20:51
markwashit sounds like we expect patches soonish?20:52
nikhilya20:52
*** julim has joined #openstack-meeting-alt20:52
nikhilmarkwash: when do they need to be merged in?20:52
*** banix has quit IRC20:52
markwashdo we still need async-processing bp? or can we kick that one out and just have it under Import Workflow ?20:52
markwashor Upload workflow, I think it is called20:52
*** demorris has quit IRC20:52
nikhilwe need a baseline patch by 16th I suppose?20:52
markwashnikhil: by the 18th20:52
nikhilokay, thanks20:53
*** julim has quit IRC20:53
markwashokay let's follow up on these bps on monday20:53
markwashnext, image-location-status (zhiyan)20:54
flaper87ops, my laptop died20:54
flaper87:(20:54
flaper87I'll work on the etherpad20:54
markwashI think this is mostly ready to review, but maybe there is a bit of concern about the first patch20:54
markwash#link https://review.openstack.org/#/c/67079/20:54
*** Barker has quit IRC20:54
markwashflaper87: okay great thanks20:54
zhiyanyes, migration20:54
*** mattgriffin has quit IRC20:54
zhiyanwhat about others? markwash, do you think their shape is good?20:55
markwashzhiyan: I looked, and while I like the idea of a little more clarity about what each is supposed to accomplish they looked mostly good20:55
*** jcoufal has quit IRC20:56
markwashyeah I think I was generally pleased, it may be the only issue is the migration20:56
*** NehaV has quit IRC20:56
*** Ranjitha has quit IRC20:57
markwashzhiyan: I wouldn't mind just taking a crack at the migration, trying to get it to avoid being nullable, would I be stepping on your toes though?20:57
*** NehaV has joined #openstack-meeting-alt20:57
*** julim has joined #openstack-meeting-alt20:58
zhiyanmarkwash: actually i think nullable is ok, but maybe i missunderstanding your concerns..20:58
markwashflaper87: let us know if you need help or just reviews on bug https://review.openstack.org/#/c/59150/20:58
markwashokay20:58
arnaud__"but might complicate future operations" could you share what you have in mind markwash ?20:58
*** demorris has joined #openstack-meeting-alt20:58
flaper87markwash: I need help in the other one20:58
flaper87the virtual_size20:58
flaper87I don't get why it keeps raising that error20:59
markwashflaper87: ah okay yes I missed that one20:59
flaper87I can't replicate the issue20:59
flaper87flwang: tried as well and he wasn't able20:59
flaper87-infra guys can't give me access to that box20:59
markwash#link https://review.openstack.org/#/c/65499/20:59
*** ijw has joined #openstack-meeting-alt20:59
*** vkmc has joined #openstack-meeting-alt20:59
flaper87I tried creating a venv with ubuntu precise20:59
markwash^^ needs help figuring out testing issues20:59
flaper87but nein, it won't replicate the issue20:59
*** rkukura has quit IRC20:59
flaper87and the funny thing is that it's a really trivial migration20:59
*** amytron has joined #openstack-meeting-alt20:59
flaper87it adds an BigInt field and removes it20:59
flaper87no idea why it fails in the gate21:00
markwashzhiyan: I'll try to follow up with you on the migration, ping me if I forget21:00
*** denis_makogon_ has joined #openstack-meeting-alt21:00
markwashokay I htink we need to make way for the next meeting21:00
flaper87markwash: thanks21:00
markwashthanks everybody for helping with the icehouse-3 triage push!21:00
zhiyanmarkwash: ok, thanks.21:00
jokke_thanks markwash21:00
markwash#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Thu Feb  6 21:00:54 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-02-06-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-02-06-20.00.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-02-06-20.00.log.html21:00
*** denis_makogon has quit IRC21:01
*** denis_makogon_ is now known as denis_makogon21:01
*** dmakogon_ has joined #openstack-meeting-alt21:01
*** ativelkov has left #openstack-meeting-alt21:01
*** jokke_ has left #openstack-meeting-alt21:01
*** colinmcnamara has quit IRC21:02
*** NikitaKonovalov_ is now known as NikitaKonovalov21:02
*** amrith has quit IRC21:02
*** amrith has joined #openstack-meeting-alt21:03
*** NehaV has quit IRC21:04
*** sgordon has quit IRC21:04
*** ackerman80 has left #openstack-meeting-alt21:04
*** colinmcnamara has joined #openstack-meeting-alt21:05
*** Barker has joined #openstack-meeting-alt21:05
*** nikhil has quit IRC21:06
*** lblanchard has joined #openstack-meeting-alt21:06
*** ijw has quit IRC21:07
*** ijw has joined #openstack-meeting-alt21:08
*** mattgriffin has joined #openstack-meeting-alt21:09
*** amytron has quit IRC21:11
*** jbernard has left #openstack-meeting-alt21:11
*** mattgriffin has quit IRC21:11
*** ashwini has left #openstack-meeting-alt21:12
*** markwash has quit IRC21:12
*** nikhil__ has joined #openstack-meeting-alt21:13
*** colinmcnamara has quit IRC21:14
*** gokrokve has joined #openstack-meeting-alt21:14
*** jasonb365 has joined #openstack-meeting-alt21:15
*** nikhil__ has quit IRC21:16
*** zhiyan has left #openstack-meeting-alt21:16
*** nikhil__ has joined #openstack-meeting-alt21:16
*** sarob has joined #openstack-meeting-alt21:17
*** lcostantino has quit IRC21:18
*** soniarvind has quit IRC21:23
*** krtaylor has quit IRC21:24
*** DinaBelova is now known as DinaBelova_21:25
*** beyounn has quit IRC21:25
*** jcooley_ has quit IRC21:28
*** jcooley_ has joined #openstack-meeting-alt21:29
*** jjmb has joined #openstack-meeting-alt21:29
*** jcoufal-mobile has joined #openstack-meeting-alt21:31
*** sarob has quit IRC21:33
*** sarob has joined #openstack-meeting-alt21:33
*** d0ugal has joined #openstack-meeting-alt21:34
*** Ranjitha has joined #openstack-meeting-alt21:34
*** d0ugal has quit IRC21:34
*** d0ugal has joined #openstack-meeting-alt21:34
*** dprince has quit IRC21:35
*** d0ugal has quit IRC21:35
*** amrith has quit IRC21:36
*** NehaV has joined #openstack-meeting-alt21:36
*** sarob has quit IRC21:36
*** jjmb has quit IRC21:36
*** sarob has joined #openstack-meeting-alt21:37
*** amrith has joined #openstack-meeting-alt21:38
*** jjmb has joined #openstack-meeting-alt21:40
*** ijw has quit IRC21:41
*** sarob has quit IRC21:41
*** d0ugal has joined #openstack-meeting-alt21:41
*** d0ugal has quit IRC21:41
*** d0ugal has joined #openstack-meeting-alt21:41
*** beyounn has joined #openstack-meeting-alt21:45
*** Alex_H has joined #openstack-meeting-alt21:48
*** Duane_ has quit IRC21:48
*** Duane_ has joined #openstack-meeting-alt21:49
*** betsy has joined #openstack-meeting-alt21:49
*** NehaV has quit IRC21:53
*** Duane_ has quit IRC21:53
*** catherine|3 has joined #openstack-meeting-alt21:54
*** rocky2 has joined #openstack-meeting-alt21:55
*** zehicle_at_dell has joined #openstack-meeting-alt21:56
*** bdpayne has quit IRC21:56
*** demorris has quit IRC21:57
*** doug_shelley66 has quit IRC21:57
*** bdpayne has joined #openstack-meeting-alt21:58
*** jjmb has quit IRC22:00
zehicle_at_dell#meeting start22:01
rocky2#startmeeting refstack22:01
openstackMeeting started Thu Feb  6 22:01:39 2014 UTC and is due to finish in 60 minutes.  The chair is rocky2. Information about MeetBot at http://wiki.debian.org/MeetBot.22:01
*** balajiiyer1 has left #openstack-meeting-alt22:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:01
*** openstack changes topic to " (Meeting topic: refstack)"22:01
openstackThe meeting name has been set to 'refstack'22:01
davidlenwellHello everyone!22:01
zehicle_at_dello/22:02
rocky2Hey!  Don't want to be the chair, but....22:02
zehicle_at_dellcan someone share the link to the page22:02
davidlenwellhttps://etherpad.openstack.org/p/DefCoreRefStackUseCases22:02
zehicle_at_dellrocky2, I can chair22:02
zehicle_at_dell#link https://etherpad.openstack.org/p/DefCoreRefStackUseCases22:02
davidlenwellI need to learn all those bot commands22:02
rocky2I'm swtiching back and forth from #meeting to get them;-)22:03
davidlenwellzehicle_at_dell: how do you want to start.. my meeting style isn't very formal as you may have seen22:03
zehicle_at_dellcan we start w/ a status update22:04
rocky2Is Catherine here?  I'd love to get more detail on the t-cup effort22:04
zehicle_at_dellthen move into blocking issues22:04
catherine|3Yes22:04
zehicle_at_delland plans for the rest of the week w/ help requests22:04
davidlenwellI can go first22:04
rocky2Yes22:04
davidlenwellw/status22:04
rocky2#topic status22:05
*** openstack changes topic to "status (Meeting topic: refstack)"22:05
*** shakayumi has joined #openstack-meeting-alt22:05
*** drray has joined #openstack-meeting-alt22:05
davidlenwellI've been side lined all week per order of of ceo.. I've managed to free up today to only work on refstack.. I've started my data base designs and so far vomited out about 1.5 paragraphs of text for a higher level doc22:06
*** jcoufal-mobile has quit IRC22:06
davidlenwellI usually work really late .. so I imagine come morning there will be an email from me to everyone with further updates and links to documents22:06
rocky2cool22:07
*** michael-yu has quit IRC22:07
zehicle_at_dellso, looking at the page22:08
rocky2more info or should we move to next person?22:08
*** IlyaE has quit IRC22:08
davidlenwellI think those were the only items from me this week22:08
rocky2Yup.  Catherine?22:09
*** david_lyle has quit IRC22:09
*** pdmars has quit IRC22:09
catherine|3David connected me to Alex and get a copy of the dockerfile22:09
davidlenwellI introduced Alex_H and catherine|3 last week.. and sent over Alex_H's docker file.22:10
*** sc68cal_ has quit IRC22:10
*** jjmb has joined #openstack-meeting-alt22:10
zehicle_at_dellAlex_H, said that they'd made progress22:10
catherine|3I made some modificatio nto the file and able to build a container and run  the tempest test22:10
rocky2How long did the test take and what projects were included?22:11
*** NikitaKonovalov is now known as NikitaKonovalov_22:11
rocky2(if you don't have answers, don't worry)22:11
*** shakayumi has quit IRC22:11
catherine|3I am running the test and container from a virutal box from my laptop so it may be slow.  But it ttook about 4 hour to run 1100 test cases22:12
zehicle_at_dellcatherine|3, that aligns w/ our experience22:12
catherine|3how long does it take?22:12
zehicle_at_dellwhat are you using as the target?22:12
zehicle_at_dellthe team was saying 3 hours22:12
catherine|3I build a all in one Hanvana OpenStack KVM cloud in my lab22:13
davidlenwellAre you testing against a real cluster or a devstack install?22:13
davidlenwellahh22:13
zehicle_at_dellreal cluster22:13
catherine|3not devstack22:13
catherine|3a reak one22:13
catherine|3but all in one (controller , compute ...)22:13
catherine|3a real one22:13
davidlenwellpackage install?22:13
catherine|3yes all go well22:13
catherine|3Alex did a good job in resovling the dependency22:14
Alex_Hthanks22:14
*** IlyaE has joined #openstack-meeting-alt22:14
catherine|3Hi Alex22:14
Alex_HHye22:14
zehicle_at_dellI was thinking to have Alex_H duplicate the tcup results against Rackspace22:14
catherine|3all tempest requirement and test_requirement installed with no prolbem.  Test run but slow22:15
catherine|3what is t-cup?22:15
zehicle_at_delltempest in a container22:15
davidlenwellI'm sure thats because it was virtualized twice.. once to virtual box then in a docker container22:15
catherine|3ic22:15
davidlenwellif we could get an openstack cluster with docker computer nodes I imagine it would run a lot faster22:15
zehicle_at_dell#info t-cup: tempest in a container, upload from probe22:16
rocky2Tempest in a teacup is a reference to alice in Wonderland book, also.22:16
catherine|3so far i tested with a static tempest.conf file.  Will test with David's generator next22:16
zehicle_at_delldavidlenwell, my team is working towards that but it's not going to be available in time for us22:16
zehicle_at_dellrocky2, :)22:16
davidlenwellI might set up a node in my house to do that for my own tests22:16
catherine|3will we generate the dcoker image every time from the dockerfile or will we save an image with tempest pre-isntall?22:17
davidlenwellcatherine|3: I will need to change that code to not depend on the database.. but to be fed creditials while its being generated ..22:17
zehicle_at_dellhow far off is being able to expand the test audience for tcup?  I'd like to have some people give it a try22:17
davidlenwellwe decided a while ago it was best to leave creditials out of the database22:17
zehicle_at_dell+122:18
rocky2+122:18
davidlenwellthats maybe an hours work for me to make it work that way.22:18
*** sreshetnyak has quit IRC22:19
rocky2might be able to try it here once you think it will likely run22:19
zehicle_at_dellwould it simplify the tcup work to reduce the # of tests for now?22:19
davidlenwellI think with the config generator its an easy thing22:19
rocky2great idea!22:19
zehicle_at_dellbasically, just do a quick pass22:20
davidlenwellzehicle_at_dell: I've been running just the api tests22:20
zehicle_at_dellthen we can get people to try it and also work on upload22:20
*** ijw has joined #openstack-meeting-alt22:20
zehicle_at_delldavidlenwell, makes sense.  that let's people use their cloud accounts22:20
davidlenwellbut that is because the early model of refstack wasn't designed to run behind enemy lines22:20
catherine|3I can try again with just the API test22:20
catherine|3and see how long22:20
davidlenwellthe api tests are super super fast22:20
davidlenwellmine usually run in seconds22:20
* zehicle_at_dell does openstack espionage22:20
davidlenwellagainst a devstack install22:21
davidlenwellzehicle_at_dell: +122:21
catherine|3There are abot 400+ API test22:21
zehicle_at_dellcool, I think we have a natural scope limit that can help22:21
zehicle_at_dellcan we drop that to 25022:21
catherine|3400+ for JSOB and 400+ for XML22:21
davidlenwellits not very time consuming22:21
zehicle_at_delljust as a temporary measure22:21
rocky2You could leave out the negative tests that have been separated out22:22
davidlenwellalso this config maker is smart22:22
catherine|3no right now I test by path22:22
zehicle_at_dellI don't want to keep it small, just to help people who are testing this get fast results22:22
davidlenwellit logs into keystone and figures out which services are there22:22
catherine|3say if the argument pass in is templest22:22
zehicle_at_dellso we can get to uploading22:22
rocky2Though, currently most of the api tests are not parametric, so they should be pretty fast.22:22
davidlenwellwhen it builds the config .. it leaves out stuff it knows the cloud doesn't have22:22
catherine|3then it would be about 1200+ test cases22:22
zehicle_at_dellhow about this, let's try to get the run down to under 30 seconds for now22:23
davidlenwelldoes that make sense ?22:23
zehicle_at_delland then we can expand it once we have the infrastructure working22:23
*** banix has joined #openstack-meeting-alt22:23
*** beyounn has quit IRC22:23
*** jdob has quit IRC22:23
catherine|3If I just run tempest.api.images22:23
catherine|3that would be about a few mins22:23
rocky2zehicle_at_dell: +122:23
catherine|3I can drop dowm more by just test a handfule of test case with22:24
*** eankutse1 has joined #openstack-meeting-alt22:24
davidlenwellthe extent of my testing with what refstack can do now has been a vmware node on my laptop testing another vmware node running devstack.. so results may very22:24
zehicle_at_dellyy22:24
*** eankutse1 has quit IRC22:24
zehicle_at_dellonce we get the workflow between tcup and refstack working, then we can crank it back up'22:25
davidlenwellI think for getting the software working .. limiting the tests is fine22:25
catherine|3Zehicle_at_dell What is the status of mapping testcase to capability?22:25
davidlenwellyeah .. that22:25
*** jjmb has quit IRC22:25
catherine|3yes we can limit the test22:25
catherine|3for now22:25
zehicle_at_dell#agree limit # of tests while we get integration between t-cup and refstack going22:25
davidlenwellonce the workflow is there I don't care how long tests take22:25
davidlenwellI want all the tests22:25
*** RajeshMohan has quit IRC22:25
zehicle_at_dellonce we have the workflow working for our team, I'm planning to start expanding the number of test people22:26
rocky2I have an old Dell Studio XPS with 6g that will be my "lab" and "outside" machine.  I plan on running at least some devstack based refstack tests on it.22:26
catherine|3so we test all test and filter the result per DefCore definition of capability?22:26
zehicle_at_dellI'd like to get about 10 people in the initial pass22:26
zehicle_at_dellthen open it up and see if we can get 100+ scans22:26
*** RajeshMohan has joined #openstack-meeting-alt22:26
davidlenwellI agree with that22:26
zehicle_at_dellbut we have to be confident that it's working - dont wnat to have to staff a support desk22:26
davidlenwellI think we have that now between you guys and piston22:27
rocky2When we get close, I think I can get a nodepool setup for testing.  We can decide a couple of configurations and either crowbar or compass a couple of configs that we can use for testing.22:27
davidlenwellwe have running clusters we can test againts at anytime22:27
*** eankutse has quit IRC22:27
zehicle_at_dellI'd like to poke the TC and Board to give it a try22:27
zehicle_at_dellbetween them, we should find 10-20 takers22:27
zehicle_at_delland a friendly audience22:27
rocky2very true22:28
zehicle_at_delldo we need to coordinate more on activity for tcup?  it seems like the right people are talking22:28
catherine|3So far we can only run test.  Not dealing with the results yet22:28
davidlenwellI agree..22:28
*** rohit404 has quit IRC22:28
davidlenwellthat is the right path catherine ..22:28
rocky2yes22:29
davidlenwelldealing witht he results is also a solved problem22:29
catherine|3so the results are still i nthe container.  We need to move it out some wjhere22:29
*** lisaclark1 has quit IRC22:29
davidlenwellI've written code than can extract the results from rest repository22:29
*** lisaclark1 has joined #openstack-meeting-alt22:29
davidlenwellI just need to add the part that sends it home to refstack22:29
davidlenwellwhich is easy once the api is finished22:29
catherine|3yes but test repository is now in the contaimer.. e need to resovle container id , ip ....22:29
davidlenwellso you are right to concentrate on the testing .. get that working .. I'll focus on the api .. get that working and we can meet in the middle22:29
zehicle_at_delllet's see if we can get the tcup documented so other people can try it22:30
zehicle_at_delland make upload from tcup a goal for next sprint22:30
davidlenwellso I'm thinking some pyton code will get triggered from the container when its finished22:30
catherine|3yes my next focus is fetching data out of container22:30
davidlenwellthat code will call home22:30
zehicle_at_dellcatherine|3, do we have enough API for you to start that?22:30
*** beyounn has joined #openstack-meeting-alt22:31
davidlenwellhttps://github.com/dlenwell/refstack/blob/master/refstack/common/tester.py  shows how to get data from testr after the test is run22:31
zehicle_at_dell:)22:31
davidlenwellbut we'll need to finish the api methods for recieving data on the refstack side22:31
zehicle_at_dell#topic API for uploading22:31
davidlenwellSo that is the restful api that I am supposed to of design last week.. I am mid-design on it right now today and will have a draft at the end of my day.22:32
davidlenwellit will include methods for recieving results from tcup22:32
*** Ranjitha has quit IRC22:32
rocky2Do we have an idaddress to call "home"?  I'd like to look at result files, processed and not when we get to that point.22:33
davidlenwellthe results them selves probably have enough info to assosiate them the right way22:33
catherine|3rigjt now I am testing stand alone not touching API yet22:33
davidlenwellI think it will be api.refstack.org22:33
rocky2great!22:33
zehicle_at_dell+122:33
davidlenwellcatherine|3: thats good because the api doesn't exist fully22:33
*** lisaclark1 has quit IRC22:34
*** doug_shelley66 has joined #openstack-meeting-alt22:34
catherine|3Perhaps we should have a technical meeting sometime to dive deep some nore22:34
zehicle_at_delldavidlenwell, I'm assuming that the POST can stand alone?22:34
davidlenwellso one task is to create a "called when tests are finished" script..  python would be idea since I've already written the parts we need22:34
davidlenwellzehicle_at_dell: That is a safe assumption22:34
rocky2+122:34
zehicle_at_dellcatherine|3, I can work to arrange.  Topics you'd like to cover?22:34
*** tmckay is now known as _tmckay22:35
davidlenwellI thought this was a technical meeting ?22:35
*** NehaV has joined #openstack-meeting-alt22:35
zehicle_at_dellit is - I think catherine|3 is thinking something face-to-face or voice w/ a white board22:35
davidlenwelloh22:35
davidlenwellI'd love to work on that22:35
catherine|3Topic is the flow of integration ... Wjere is the host that hosted the container.. where the test data destination ...22:36
davidlenwellpiston would love to host it also if sf is easy travel22:36
rocky2I'd like to have a session on how we specify/subset tests from tempest22:36
davidlenwellcatherine|3: so that part of refstack is very flexible22:36
rocky2SF works for me22:36
*** Ranjitha has joined #openstack-meeting-alt22:36
zehicle_at_dellWe're having a board meeting on 3/422:36
zehicle_at_dellwe could do it on 3/3 or 3/522:37
catherine|3Where are you located at David?22:37
zehicle_at_dellwas planning to have a DefCore meeting anyway in SFO on 3/322:37
davidlenwellI live north of LA but work for piston in SFO22:37
zehicle_at_dellso this would fit very nicely22:37
davidlenwellI have to be in sf for an ironic sprint 3/5 and 3/6 anyways .. so that works for me too22:37
catherine|3I leave one hour away from SF22:37
catherine|3I live22:37
davidlenwellawesome .. so I am happy to have and host refstack tech sessions anytime22:38
catherine|3so I thnk that works but that woild be a month from now22:38
zehicle_at_dellLet's plan for 3/3  - I may be pulled into other DefCore work at times22:38
catherine|3meanwhile we IRC and email?22:38
davidlenwellI'll be in sf 2/16 - 2/2022:38
davidlenwellif you can make it into the city we could have a live hacking session.. maybe 2/1922:39
zehicle_at_dellI'm not required if you want to meet22:39
catherine|3oh may be we will visit you in SF 2/16 - 2/20?22:39
zehicle_at_dellbut I may be able to drag Alex_H to the 3/3 meeting22:39
davidlenwellzehicle_at_dell: I'm good with doing it both times22:39
rocky2A mini-hackathon for Davidlenwell and Catherine|3 mid Feb?22:39
catherine|3that is great ..22:39
*** michael-yu has joined #openstack-meeting-alt22:39
zehicle_at_delllet's lock in the 3/3 meeting so I can start working on logistics22:39
davidlenwellrocky2: yes .. that sounds great22:39
catherine|3+122:40
zehicle_at_dellif you can pull together one 2 weeks before, that would be great22:40
*** beyounn has quit IRC22:40
davidlenwellyeah .. lets do both22:40
*** Barker has quit IRC22:40
rocky2+1 twice22:40
*** NehaV has quit IRC22:40
zehicle_at_dellAlex_H, can you check your schedule?  we probably can have you tag along if we work it in advance22:40
*** NehaV has joined #openstack-meeting-alt22:40
*** beyounn has joined #openstack-meeting-alt22:41
Alex_Hok22:41
zehicle_at_dellI'm always behind on the #topics!  should have #topic f2f meeting!22:42
*** jasonb365 has quit IRC22:42
zehicle_at_delldavidlenwell, when you have the upload API, can you also make it public for POST?22:42
davidlenwellyes22:42
rocky2OK.  Well, we seem to have that worked out, so how about #topic Wiki ?22:42
davidlenwellI'll just set it up to accept any subunit in a post22:43
zehicle_at_dell#topic wiki22:43
*** krtaylor has joined #openstack-meeting-alt22:43
davidlenwellI should be able to grab the info about who its from and when it was run and all that fun data from the rresults22:43
zehicle_at_dell#agree API to POST tempest results will be setup as a public endpoint so we can test it22:43
*** jasonb365 has joined #openstack-meeting-alt22:43
davidlenwellabout running a wiki on refstack .org22:43
catherine|3so the latest code is still at https://github.com/dlenwell/refstack ?22:43
rocky2Great. Yup.22:44
davidlenwellcatherine|3: I belive I have the newest code yes22:44
zehicle_at_dellwhy not use the OpenStack wiki?22:44
catherine|3ok thx22:44
rocky2Once there, I'll start populating like crazy.22:44
davidlenwellSo that brings me to another topic ..22:44
davidlenwellyes .. use the openstack wiki .. thats a no brainer22:44
davidlenwellbut if we want to start running things that are services I'd rather the infra team runs them .. we can use sub domains22:45
rocky2Just link wiki.refstacl.org to wiki.openstack.org/wiki/Refstack (close, but I don't think it's correct)22:45
davidlenwellsure .. we can make a cname or something22:45
davidlenwellright now joshua has control over the domain name22:46
zehicle_at_delldavidlenwell, I'm already talking to the OpenStack foundation about that22:46
zehicle_at_dellJonathan Bryce & Mark Collier22:46
zehicle_at_dellwe were thinking that we could get it proved out here for this cycle and then start migrating it to $$$.openstack.org22:47
davidlenwellits easy to get them to run things if you make a puppet config for it and ask monty very nicely22:47
zehicle_at_dellso we'd get under regular governance after Atlanta22:47
davidlenwellperfect22:47
rocky2+122:47
davidlenwellthis is me saying .. I don't want to admin services because I am not best suited as an admin..22:48
* zehicle_at_dell setting up space on OpenStack wiki for RefStack info22:48
davidlenwellI'd preffer a change in the services running required a commit to infra-config to change22:48
rocky2I've got a colleague that can help getting the stackforge zuul/gerrit/jenkins stuff set up for our code base when we're ready to start firing off some CI tests22:49
davidlenwellif we go into official openstack channels we won't need to do that22:49
rocky2even better22:49
davidlenwellstackforge it22:49
davidlenwellessentially22:49
*** beyounn has quit IRC22:50
davidlenwellif the goal is under governance after atlanta we have to think that way now22:50
davidlenwelland not go off and set up our own stuff all over the place22:50
rocky2So, would this go under a "program" like QA or Infra?22:50
davidlenwellzehicle_at_dell: ???22:50
zehicle_at_dellsorry22:50
rocky2Doh.  Forget that last thing I typed.22:50
*** NehaV has quit IRC22:51
*** beyounn has joined #openstack-meeting-alt22:51
zehicle_at_dellwe'd need some tests ;)22:52
davidlenwellI think by then we'll have lots of results to work with22:52
zehicle_at_delltests of the refstack code base22:52
davidlenwelloh that .. yes22:52
davidlenwelldo we have someone who likes to write tests?22:53
rocky2Again, I've got folks.  Just sayin'22:53
zehicle_at_dell#link https://wiki.openstack.org/wiki/Governance/DefCoreCommittee/RefStack22:53
rocky2Cool.22:53
zehicle_at_dell5 minute warning22:53
davidlenwellrocky2: lets talk offline about getting that started22:54
rocky2Will do.22:54
zehicle_at_delldavidlenwell, +1 on getting started on governance22:54
davidlenwellwe didn't write tests because in the hacky stage of things before things are defined I feel like its a huge waste of time22:54
zehicle_at_dellright now, we're talking about a very small surface w/ POST and basic compare22:54
davidlenwellthats doable22:55
davidlenwellI can write the test for that before integrating the api code .. which is the order I'd preffer to do them in22:55
davidlenwellthat way you always have tests for every api call22:55
* zehicle_at_dell sends hug22:55
rocky2Since you're writing a chunk of the api right now, just some simple unit tests that generate a happy path output from a fixed input would be a nice start.22:56
zehicle_at_delllast comments/topics?22:56
davidlenwelllets wrap up in #refstack22:56
rocky2 I love people who believe in TDD!22:56
rocky2And especially those who practice it!22:56
davidlenwelllike I said it depends on if I am developing a product or if its r&d hacking22:57
*** mattgriffin has joined #openstack-meeting-alt22:57
zehicle_at_dellgreat meeting everyone - I feel like we got some things locked down22:57
davidlenwellagreed22:57
zehicle_at_delllooking forward to f2f next month22:57
davidlenwellsame22:57
catherine|3Will we continue meeting next week or on #refstack?22:58
rocky2Understood.  That's why most GUI automated test creation is a waste.  It's always "R&D" so why waste the extra time?22:58
zehicle_at_dellplease keep #refstack open22:58
zehicle_at_dellwe should use this channel for official scheduled meetings22:58
rocky2Yes.  Next week.  Thanks all!22:58
zehicle_at_dell#endmeeting22:58
*** markwash has joined #openstack-meeting-alt22:58
zehicle_at_dell#endmeeting refstack22:59
*** rocky2 has quit IRC22:59
*** amrith has quit IRC22:59
*** david-lyle has joined #openstack-meeting-alt22:59
*** drray has left #openstack-meeting-alt23:01
*** Raymond7 has joined #openstack-meeting-alt23:01
*** amrith has joined #openstack-meeting-alt23:02
*** Raymond7 has left #openstack-meeting-alt23:03
*** amcrn has quit IRC23:03
*** balajiiyer has joined #openstack-meeting-alt23:04
*** RaymondWong has joined #openstack-meeting-alt23:04
*** rocky2 has joined #openstack-meeting-alt23:05
*** amcrn has joined #openstack-meeting-alt23:06
*** sacharya has quit IRC23:07
*** venkatesh has joined #openstack-meeting-alt23:09
*** enikanorov has joined #openstack-meeting-alt23:11
*** Alex_H has left #openstack-meeting-alt23:11
*** eharney has quit IRC23:11
*** enikanorov__ has quit IRC23:12
clarkb#endmeeting23:13
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:13
openstackMeeting ended Thu Feb  6 23:13:59 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-02-06-22.01.html23:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-02-06-22.01.txt23:14
openstackLog:            http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-02-06-22.01.log.html23:14
*** rocky2 has quit IRC23:21
*** jasonb365 has quit IRC23:25
*** beyounn has quit IRC23:29
*** julim has quit IRC23:29
*** lblanchard has quit IRC23:29
*** chadlung has joined #openstack-meeting-alt23:31
*** julienvey has quit IRC23:32
*** lisaclark1 has joined #openstack-meeting-alt23:32
*** banix has quit IRC23:33
*** kevinconway has quit IRC23:34
*** jmontemayor has quit IRC23:35
*** jmontemayor has joined #openstack-meeting-alt23:35
*** yogesh has quit IRC23:36
*** jmontemayor has quit IRC23:39
*** esker has quit IRC23:40
*** sarob has joined #openstack-meeting-alt23:40
*** denis_makogon has quit IRC23:41
*** mozawa has quit IRC23:41
*** lisaclark1 has quit IRC23:42
*** sarob has quit IRC23:45
*** tanisdl has quit IRC23:47
*** ftcjeff has quit IRC23:48
*** amrith has quit IRC23:48
*** yamahata has quit IRC23:49
*** Barker has joined #openstack-meeting-alt23:49
*** bauzas has quit IRC23:53
*** Barker has quit IRC23:55
*** richm has joined #openstack-meeting-alt23:57

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