Wednesday, 2013-11-13

*** jasondotstar has quit IRC00:00
*** ItSANgo has quit IRC00:00
*** dolphm has quit IRC00:00
*** gatuus has joined #openstack-meeting00:03
*** rakhmerov has joined #openstack-meeting00:06
*** litong has quit IRC00:07
*** ItSANgo has joined #openstack-meeting00:07
*** masayukig has quit IRC00:09
*** IlyaE has joined #openstack-meeting00:09
*** jsergent has quit IRC00:09
*** rakhmerov has quit IRC00:10
*** sacharya has joined #openstack-meeting00:13
*** IlyaE has quit IRC00:13
*** jasondotstar has joined #openstack-meeting00:14
*** topol has joined #openstack-meeting00:17
*** rnirmal has quit IRC00:17
*** rakhmerov has joined #openstack-meeting00:17
*** matsuhashi has joined #openstack-meeting00:18
*** noslzzp has joined #openstack-meeting00:22
*** hemna has quit IRC00:23
*** jasondotstar has quit IRC00:26
*** jhenner has quit IRC00:27
*** hemna has joined #openstack-meeting00:27
*** rongze has joined #openstack-meeting00:32
*** nati_ueno has joined #openstack-meeting00:34
*** fifieldt has quit IRC00:35
*** jhenner has joined #openstack-meeting00:35
*** jhenner has quit IRC00:36
*** nati_ueno has quit IRC00:36
*** nati_ueno has joined #openstack-meeting00:36
*** rongze has quit IRC00:36
*** nati_ueno has quit IRC00:37
*** dolphm has joined #openstack-meeting00:37
*** nati_ueno has joined #openstack-meeting00:38
*** rfolco has quit IRC00:41
*** jhenner has joined #openstack-meeting00:41
*** nati_ueno has quit IRC00:42
*** jlucci has joined #openstack-meeting00:48
*** sarob has quit IRC00:51
*** hemna has quit IRC00:51
*** tanisdl has quit IRC00:53
*** sandywalsh has quit IRC00:58
*** galstrom_zzz is now known as galstrom01:04
*** dcramer_ has joined #openstack-meeting01:04
*** salv-orlando has quit IRC01:05
*** hemna has joined #openstack-meeting01:05
*** galstrom is now known as galstrom_zzz01:07
*** salv-orlando has joined #openstack-meeting01:08
*** pablosan has quit IRC01:08
*** gyee has quit IRC01:08
*** markwash has quit IRC01:09
*** dolphm has quit IRC01:10
*** lblanchard has quit IRC01:10
*** sushils has quit IRC01:11
*** nosnos has joined #openstack-meeting01:13
*** nosnos has quit IRC01:13
*** nosnos has joined #openstack-meeting01:14
*** schwicht has quit IRC01:16
*** tanisdl has joined #openstack-meeting01:18
*** tanisdl has quit IRC01:18
*** jeffrey4l has joined #openstack-meeting01:19
*** ayoung has joined #openstack-meeting01:20
*** Linz has quit IRC01:20
*** Linz has joined #openstack-meeting01:21
*** tian has joined #openstack-meeting01:22
*** markpeek has joined #openstack-meeting01:23
*** dcramer_ has quit IRC01:23
*** markpeek has quit IRC01:27
*** markpeek has joined #openstack-meeting01:29
*** markpeek has quit IRC01:33
*** hemna has quit IRC01:34
*** pablosan has joined #openstack-meeting01:36
*** dcramer_ has joined #openstack-meeting01:37
*** HenryG has quit IRC01:37
*** vahidh has quit IRC01:39
*** galstrom_zzz is now known as galstrom01:42
*** spzala has quit IRC01:44
*** nermina has quit IRC01:45
*** dcramer_ has quit IRC01:46
*** _ozstacker_ has quit IRC01:46
*** _ozstacker_ has joined #openstack-meeting01:47
*** rongze has joined #openstack-meeting01:50
*** loq_mac has joined #openstack-meeting01:54
*** dolphm has joined #openstack-meeting01:54
*** loq_mac has quit IRC01:54
*** nati_ueno has joined #openstack-meeting01:55
*** rudrarugge has quit IRC01:57
*** ian_ott has joined #openstack-meeting01:57
*** ian_ott has left #openstack-meeting01:57
*** yaguang has joined #openstack-meeting01:58
*** markpeek has joined #openstack-meeting02:01
*** sdake_ has quit IRC02:02
*** jasondotstar has joined #openstack-meeting02:03
*** jasondotstar has quit IRC02:04
*** markpeek has quit IRC02:06
*** dcramer_ has joined #openstack-meeting02:08
*** Linz has quit IRC02:09
*** Linz has joined #openstack-meeting02:09
*** nati_ueno has quit IRC02:09
*** nati_ueno has joined #openstack-meeting02:10
*** gatuus has quit IRC02:21
*** dcramer_ has quit IRC02:22
*** rongze has quit IRC02:23
*** rongze has joined #openstack-meeting02:23
*** changbl has joined #openstack-meeting02:24
*** nosnos_ has joined #openstack-meeting02:27
*** rongze has quit IRC02:27
*** rongze has joined #openstack-meeting02:29
*** noslzzp has quit IRC02:29
*** nati_uen_ has joined #openstack-meeting02:29
*** haomaiwang has joined #openstack-meeting02:30
*** nosnos has quit IRC02:30
*** comay has quit IRC02:30
*** nermina has joined #openstack-meeting02:31
*** nati_ueno has quit IRC02:33
*** suo has joined #openstack-meeting02:34
*** dcramer_ has joined #openstack-meeting02:35
*** jlucci has quit IRC02:37
*** fnaval_ has joined #openstack-meeting02:39
*** lblanchard has joined #openstack-meeting02:41
*** saurabh_ has joined #openstack-meeting02:42
*** hua has joined #openstack-meeting02:42
*** mrodden has quit IRC02:43
*** dolphm has quit IRC02:47
*** dolphm has joined #openstack-meeting02:47
*** armax has left #openstack-meeting02:50
*** sacharya1 has joined #openstack-meeting02:50
*** lblanchard has quit IRC02:50
*** dolphm has quit IRC02:52
*** galstrom is now known as galstrom_zzz02:52
*** sacharya has quit IRC02:53
*** jmontemayor has quit IRC02:54
*** beyounn has joined #openstack-meeting02:54
*** annegentle has quit IRC02:55
*** annegentle has joined #openstack-meeting02:55
*** radez_g0n3 is now known as radez02:56
*** twoputt has quit IRC02:56
*** twoputt_ has quit IRC02:56
*** bnemec has quit IRC02:57
*** galstrom_zzz is now known as galstrom02:57
*** rudrarugge has joined #openstack-meeting02:58
*** fifieldt has joined #openstack-meeting02:59
*** matsuhashi has quit IRC03:02
*** matsuhashi has joined #openstack-meeting03:03
*** matsuhashi has quit IRC03:03
*** thomasem has joined #openstack-meeting03:04
*** nati_uen_ has quit IRC03:04
*** nati_ueno has joined #openstack-meeting03:05
*** novas0x2a|laptop has quit IRC03:05
*** bnemec has joined #openstack-meeting03:05
*** changbl has quit IRC03:06
*** thomasem has quit IRC03:07
*** rudrarugge has quit IRC03:09
*** nati_ueno has quit IRC03:10
*** rudrarugge has joined #openstack-meeting03:10
*** dcramer_ has quit IRC03:10
*** annegentle has quit IRC03:11
*** spzala has joined #openstack-meeting03:11
*** annegentle has joined #openstack-meeting03:12
*** changbl has joined #openstack-meeting03:12
*** matsuhashi has joined #openstack-meeting03:13
*** rudrarugge has quit IRC03:14
*** radix has quit IRC03:18
*** sdake_ has joined #openstack-meeting03:20
*** nati_ueno has joined #openstack-meeting03:27
*** markpeek has joined #openstack-meeting03:27
*** markpeek has quit IRC03:31
*** yaguang has quit IRC03:32
*** yaguang has joined #openstack-meeting03:32
*** rongze has quit IRC03:35
*** rongze has joined #openstack-meeting03:35
*** galstrom is now known as galstrom_zzz03:36
*** jasondotstar has joined #openstack-meeting03:36
*** alexpilotti has joined #openstack-meeting03:37
*** dims has quit IRC03:37
*** markwash has joined #openstack-meeting03:37
*** rongze has quit IRC03:38
*** rongze has joined #openstack-meeting03:38
*** sarob has joined #openstack-meeting03:42
*** matsuhashi has quit IRC03:45
*** matsuhashi has joined #openstack-meeting03:46
*** masayukig has joined #openstack-meeting03:47
*** dcramer_ has joined #openstack-meeting03:48
*** matsuhas_ has joined #openstack-meeting03:49
*** nati_ueno has quit IRC03:49
*** matsuhashi has quit IRC03:50
*** galstrom_zzz is now known as galstrom03:50
*** jlucci has joined #openstack-meeting03:51
*** gongysh has joined #openstack-meeting03:56
*** sarob has quit IRC04:00
*** nati_ueno has joined #openstack-meeting04:06
*** vipul is now known as vipul-away04:07
*** zehicle_at_dell has joined #openstack-meeting04:09
*** spzala has quit IRC04:10
*** jerryz has quit IRC04:11
*** rudrarugge has joined #openstack-meeting04:14
*** rudrarugge has quit IRC04:15
*** jorisroovers has joined #openstack-meeting04:17
*** alexpilotti has quit IRC04:18
*** ArxCruz has quit IRC04:19
*** jorisroovers has quit IRC04:22
*** ArxCruz has joined #openstack-meeting04:22
*** galstrom is now known as galstrom_zzz04:26
*** markpeek has joined #openstack-meeting04:32
*** galstrom_zzz is now known as galstrom04:34
*** jasondotstar has quit IRC04:34
*** markpeek has quit IRC04:36
*** IlyaE has joined #openstack-meeting04:38
*** sandywalsh has joined #openstack-meeting04:39
*** nosnos_ has quit IRC04:44
*** nosnos has joined #openstack-meeting04:44
*** rongze has quit IRC04:52
*** rongze has joined #openstack-meeting04:52
*** rongze has quit IRC04:57
*** dcramer_ has quit IRC04:59
*** jasondotstar has joined #openstack-meeting05:03
*** galstrom is now known as galstrom_zzz05:09
*** jasondotstar has quit IRC05:14
*** vipul-away is now known as vipul05:19
*** jeffrey4l has quit IRC05:25
*** dcramer_ has joined #openstack-meeting05:25
*** macjack has joined #openstack-meeting05:27
*** markpeek has joined #openstack-meeting05:31
*** IlyaE has quit IRC05:31
*** topol has quit IRC05:34
*** jeffrey4l has joined #openstack-meeting05:34
*** markwash has quit IRC05:34
*** jeffrey4l has quit IRC05:34
*** markpeek has quit IRC05:35
*** hemanth__ has joined #openstack-meeting05:36
*** llu has quit IRC05:36
*** hemanth__ has quit IRC05:37
*** sacharya1 has quit IRC05:41
*** fnaval_ has quit IRC05:42
*** Linz has quit IRC05:42
*** garyk has quit IRC05:43
*** pablosan has quit IRC05:48
*** tomoe_ has joined #openstack-meeting05:53
*** rongze has joined #openstack-meeting05:53
*** llu has joined #openstack-meeting05:55
*** coolsvap has joined #openstack-meeting05:57
*** matsuhas_ has quit IRC05:58
*** afazekas has joined #openstack-meeting05:59
*** rongze has quit IRC05:59
*** blamar has quit IRC06:00
*** matsuhashi has joined #openstack-meeting06:00
*** blamar has joined #openstack-meeting06:00
*** sarob has joined #openstack-meeting06:01
*** matsuhashi has quit IRC06:01
*** matsuhashi has joined #openstack-meeting06:02
*** afazekas has quit IRC06:04
*** ctracey has quit IRC06:05
*** sarob has quit IRC06:06
*** denis_makogon has joined #openstack-meeting06:07
*** nati_ueno has quit IRC06:08
*** nati_ueno has joined #openstack-meeting06:09
*** nati_uen_ has joined #openstack-meeting06:11
*** markwash has joined #openstack-meeting06:12
*** nati_ueno has quit IRC06:13
*** nati_ueno has joined #openstack-meeting06:13
*** nati_uen_ has quit IRC06:13
*** dcramer_ has quit IRC06:13
*** afazekas has joined #openstack-meeting06:17
*** IlyaE has joined #openstack-meeting06:21
*** ildikov has joined #openstack-meeting06:23
*** ildikov has quit IRC06:23
*** Swami has joined #openstack-meeting06:24
*** ildikov has joined #openstack-meeting06:24
*** yamahata has joined #openstack-meeting06:26
*** vito-ordaz has joined #openstack-meeting06:29
*** oda-g has joined #openstack-meeting06:30
*** yamahata_ has joined #openstack-meeting06:30
*** oda-g has left #openstack-meeting06:32
*** markpeek has joined #openstack-meeting06:33
*** boris-42 has joined #openstack-meeting06:36
*** Linz has joined #openstack-meeting06:38
*** sarob has joined #openstack-meeting06:45
*** rongze has joined #openstack-meeting06:47
*** IlyaE has quit IRC06:51
*** matsuhashi has quit IRC06:53
*** IlyaE has joined #openstack-meeting06:53
*** matsuhashi has joined #openstack-meeting06:53
*** tomoe__ has joined #openstack-meeting06:56
*** matsuhashi has quit IRC06:57
*** tomoe_ has quit IRC07:00
*** aepifanov has joined #openstack-meeting07:01
*** garyk has joined #openstack-meeting07:05
*** matsuhashi has joined #openstack-meeting07:06
*** nati_ueno has quit IRC07:07
*** flaper87|afk is now known as flaper8707:08
*** nati_ueno has joined #openstack-meeting07:08
*** radix has joined #openstack-meeting07:08
*** doron_afk has joined #openstack-meeting07:09
*** radez is now known as radez_g0n307:11
*** nosnos_ has joined #openstack-meeting07:11
*** nati_ueno has quit IRC07:12
*** markpeek has quit IRC07:13
*** enikanorov has quit IRC07:13
*** nosnos has quit IRC07:14
*** nati_ueno has joined #openstack-meeting07:15
*** radez_g0n3 is now known as radez07:18
*** mrunge has joined #openstack-meeting07:19
*** mrunge has quit IRC07:20
*** mrunge has joined #openstack-meeting07:20
*** vito-ordaz has quit IRC07:22
*** vito-ordaz has joined #openstack-meeting07:22
*** erwan_taf has quit IRC07:23
*** erwan_taf has joined #openstack-meeting07:23
*** yamahata_ has quit IRC07:23
*** IlyaE has quit IRC07:24
*** sarob has quit IRC07:24
*** vito-ordaz has quit IRC07:26
*** vipul is now known as vipul-away07:27
*** jtomasek has joined #openstack-meeting07:27
*** enikanorov has joined #openstack-meeting07:30
*** nosnos_ has quit IRC07:31
*** nosnos has joined #openstack-meeting07:32
*** yamahata_ has joined #openstack-meeting07:32
*** akuznetsov has quit IRC07:34
*** beyounn has quit IRC07:34
*** yamahata_ has quit IRC07:35
*** yamahata_ has joined #openstack-meeting07:35
*** yamahata_ has quit IRC07:35
*** belmoreira has joined #openstack-meeting07:35
*** yamahata_ has joined #openstack-meeting07:35
*** enikanorov has quit IRC07:43
*** enikanorov has joined #openstack-meeting07:46
*** Loquacity has quit IRC07:53
*** sarob has joined #openstack-meeting07:55
*** vipul-away is now known as vipul07:55
*** RajeshMohan has quit IRC07:55
*** RajeshMohan has joined #openstack-meeting07:56
*** Fdot has joined #openstack-meeting07:57
*** tomoe__ has quit IRC08:03
*** tomoe_ has joined #openstack-meeting08:04
*** Loquacity has joined #openstack-meeting08:06
*** sarob has quit IRC08:06
ttxjpich, david-lyle: I'll create the milestones today, as I officialize the icehouse schedule08:07
*** vito-ordaz has joined #openstack-meeting08:07
*** tomoe_ has quit IRC08:08
*** jlucci has quit IRC08:11
*** davidhadas has quit IRC08:11
*** inkerra has joined #openstack-meeting08:13
*** jlibosva has joined #openstack-meeting08:14
*** vito-ordaz has quit IRC08:19
*** vito-ordaz has joined #openstack-meeting08:19
*** Krast has joined #openstack-meeting08:22
*** vito-ordaz has quit IRC08:23
*** Krast has left #openstack-meeting08:26
*** jtomasek has quit IRC08:26
*** nkhare has joined #openstack-meeting08:26
*** jtomasek has joined #openstack-meeting08:28
*** Krast has joined #openstack-meeting08:31
*** sarob has joined #openstack-meeting08:32
*** akuznetsov has joined #openstack-meeting08:34
*** matsuhashi has quit IRC08:36
*** matsuhashi has joined #openstack-meeting08:37
*** sarob has quit IRC08:37
*** sushils has joined #openstack-meeting08:39
*** denis_makogon has quit IRC08:40
*** jorisroovers has joined #openstack-meeting08:45
*** davidhadas has joined #openstack-meeting08:45
*** radez is now known as radez_g0n308:47
*** rossella_s has joined #openstack-meeting08:49
*** SergeyLukjanov has joined #openstack-meeting08:50
*** nati_ueno has quit IRC08:55
*** nprivalova has joined #openstack-meeting09:00
*** nprivalova is now known as nadya_09:01
*** boden has joined #openstack-meeting09:03
*** sarob has joined #openstack-meeting09:03
*** sarob has quit IRC09:08
*** matsuhashi has quit IRC09:08
*** matsuhashi has joined #openstack-meeting09:11
*** bauzas has joined #openstack-meeting09:12
*** johnthetubaguy has joined #openstack-meeting09:13
*** yassine has joined #openstack-meeting09:14
*** Mandell has quit IRC09:15
*** nermina has quit IRC09:16
*** ygbo has joined #openstack-meeting09:18
*** yassine_ has joined #openstack-meeting09:18
*** plomakin has quit IRC09:19
*** Swami has quit IRC09:23
*** SergeyLukjanov is now known as _SergeyLukjanov09:26
*** boris-42 has quit IRC09:27
*** _SergeyLukjanov has quit IRC09:27
*** derekh has joined #openstack-meeting09:28
*** boris-42 has joined #openstack-meeting09:29
*** SergeyLukjanov has joined #openstack-meeting09:32
*** nosnos_ has joined #openstack-meeting09:33
*** jhenner has quit IRC09:35
*** nosnos has quit IRC09:37
*** jorisroovers has quit IRC09:40
*** matsuhashi has quit IRC09:45
*** matsuhashi has joined #openstack-meeting09:46
*** matsuhashi has quit IRC09:51
*** matsuhashi has joined #openstack-meeting09:51
*** doron_afk is now known as doron09:53
*** yamahata_ has quit IRC09:53
*** yamahata_ has joined #openstack-meeting09:53
*** maxdml has quit IRC09:55
bauzas#startmeeting climate09:59
openstackMeeting started Wed Nov 13 09:59:46 2013 UTC and is due to finish in 60 minutes.  The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.09:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:59
*** openstack changes topic to " (Meeting topic: climate)"09:59
openstackThe meeting name has been set to 'climate'09:59
bauzasmorning all09:59
*** yamahata has quit IRC10:00
bauzascould you please raise hands when present ? o/10:00
*** jasondotstar has joined #openstack-meeting10:00
*** thouveng has joined #openstack-meeting10:00
*** scroiset has joined #openstack-meeting10:00
*** f_rossigneux has joined #openstack-meeting10:01
*** rfolco has joined #openstack-meeting10:01
*** f_rossigneux has quit IRC10:01
bauzass/o there ?10:01
*** f_rossigneux has joined #openstack-meeting10:01
scroiseto/10:02
*** boris-42 has quit IRC10:02
*** boris-42 has joined #openstack-meeting10:02
f_rossigneuxHi!10:02
bauzasok, seems like Dina and Nikolay are absent10:03
bauzaslet's wait 10 mins10:03
bauzasand if not present, we will close the room10:03
*** sarob has joined #openstack-meeting10:04
*** Nikolay_St has joined #openstack-meeting10:05
*** jasondotstar has quit IRC10:05
*** Krast has quit IRC10:07
*** davidhadas has quit IRC10:07
*** Krast has joined #openstack-meeting10:07
*** Krast has quit IRC10:07
bauzasNikolay_St: you there ?10:07
*** davidhadas has joined #openstack-meeting10:07
*** sarob has quit IRC10:08
*** ArxCruz has quit IRC10:08
Nikolay_Stbauzas: yeap10:09
bauzasNikolay_St: cool10:09
bauzasNikolay_St: do you know if Dina's present ?10:09
Nikolay_Stshe's taking PTO today10:09
bauzaswhat do you mean by PTO ?10:10
bauzasah ok10:10
bauzasgotcha10:10
Nikolay_Stshe's take a day off10:10
bauzasok, then quickly review the agenda10:10
bauzas#link https://wiki.openstack.org/wiki/Meetings/Climate#Agenda_for_November.2C_1310:11
bauzas#topic Summit review10:11
*** openstack changes topic to "Summit review (Meeting topic: climate)"10:11
bauzasas Dina is not there, we won't discuss about actions to do10:11
Nikolay_Stbauzas: mm... okay10:12
*** SergeyLukjanov is now known as _SergeyLukjanov10:13
*** _SergeyLukjanov has quit IRC10:13
bauzason an overall note, I would say there are various Oslo libs we need to integrate in Climate10:13
bauzasI noted Pecan/WSME (which is not yet part of Oslo)10:14
bauzasOslo.messaging.rpc10:14
bauzasthat's all I noted10:14
Nikolay_Stcan you give me first explonation about it?10:14
bauzasyup10:14
bauzaswe're currently running Flask as WSGI fremework10:15
bauzasthere is a global move to Pecan for most of the Openstack projects, excl. Marconi10:15
bauzasthat should be investigated on our side10:15
bauzasre: oslo.messaging.rpc, it's only about making sure we're using the latest Oslo version for RPC proxying10:16
Nikolay_StI think that's a good point10:17
bauzaswhich is not yet the case10:17
Nikolay_Stboth of it10:17
bauzas#idea Investigate use of Pecan/WSME for API10:18
bauzas#idea Investigate move to oslo.messaging.rpc for RPC proxying10:18
Nikolay_Stor10:18
bauzasthere was also a discussion about two other concerns :10:19
bauzas1/ for virtual leases, instead of modifying Nova code, use Nova V3 extension called "shielved instances"10:20
bauzaswe have to dig in and look what's doing what10:20
bauzasbut on a first glance, it seems it does exactly the same thing as you wish : wipe an instance but keep it in database and do a snapshot before stopping it10:21
Nikolay_StI think I can do it after I finish with tests to API (it's very close to end I think) and manager10:21
Nikolay_StDina said me about 'shielved instances'10:21
bauzas#link https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/plugins/v3/shelve.py10:23
bauzasNikolay_St: cool10:23
Nikolay_Stbauzas: also, I think we need to think about roadmap10:24
Nikolay_Stbauzas: what do you think about it?10:24
bauzasI think that's a good idea10:25
bauzas#action POC using shelved instances10:26
bauzasabout roadmap, I think that should be discussed by email10:26
bauzason openstack-dev@10:26
Nikolay_Stmmm10:26
bauzasso, people interested in Climate could contribute10:26
Nikolay_Stmay be it's better to discuss draft of roadmap inside Climate team10:27
bauzasat first, we need to put all our needs in blueprints10:27
bauzaswell, as said, we first need to collect all our ideas as blueprints10:28
bauzasonce done, we'll triage those10:28
bauzasit should raise a roadmpa10:29
bauzasroadmap10:29
bauzas#action to_all : make sure all the blueprints match the needs, if one is missing, create it10:29
bauzasone last point about physical host reservations, we reviewed the pcloud framework10:30
bauzaschoice is made to switch to AZ instead of Pclouds10:30
bauzas#action Change implementation of ReservationPools from Pclouds to AZ10:31
bauzasI think we're done with this topic10:31
bauzasany other comments about Summit ?10:31
Nikolay_Stnope10:31
Nikolay_StI don't think we loose anything10:32
bauzas#topic Reviews follow-up10:32
*** openstack changes topic to "Reviews follow-up (Meeting topic: climate)"10:32
*** jhenner has joined #openstack-meeting10:33
bauzasso we had previous actions http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-10-28-10.00.html10:33
bauzasManager review to be delivered EOB todays and deps being rebased10:33
bauzasReviews of 52296, 52294, 52903, 52396 and 49363 this week as priority10:33
*** doron is now known as doron_afk10:33
*** marun has joined #openstack-meeting10:34
bauzasI would say the Manager review (45600) is still top priority10:34
*** SergeyLukjanov has joined #openstack-meeting10:35
bauzasI'm taking the action to review the #49 patchset by this week, and if OK, merge it to trunk10:35
bauzas#action bauzas Review Manager code (45600) and if OK, merge it to trunk by end of the week10:35
*** matsuhashi has quit IRC10:36
bauzasNikolay_St: do you have other changes to be reviewed as prioritary ?10:36
*** matsuhashi has joined #openstack-meeting10:36
Nikolay_Stbauzas: api tests as soon as I finish them10:36
Nikolay_Stand then manager test10:36
bauzasok10:36
Nikolay_StI think it'll be ok in 2 days10:37
bauzaswhen do you expect to finish the tests ? By this week ?10:37
bauzasok10:37
bauzaslet's take it as action but for the week after then10:37
*** SergeyLukjanov has quit IRC10:37
Nikolay_Stokay10:37
Nikolay_St#action Review https://review.openstack.org/#/c/52903/ https://review.openstack.org/#/c/53896/ till 25 of November10:38
bauzashttps://review.openstack.org/#/c/52296/ needs to be rebased10:39
bauzaswho can do that ?10:39
Nikolay_Stalmost done10:40
bauzasyup, but I would like to review it quickly and add it to trunk10:40
bauzasand I don't want to both commit and review on the same patchset :)10:40
*** gongysh has quit IRC10:41
*** matsuhashi has quit IRC10:41
bauzasscroiset: would you mind doing it ?10:41
Nikolay_Stwe need to merge manager service first10:41
bauzasNikolay_St: oh, just saw you did it10:42
bauzasyep10:42
*** zero00072 has joined #openstack-meeting10:42
bauzasbut I will probably review both Manager and utils at the same time10:42
*** zero00072 has left #openstack-meeting10:42
bauzas#action bauzas Review 52296 by end of the week10:43
*** ctracey has joined #openstack-meeting10:43
bauzasok, I think we're done with the review priorities10:43
bauzasthe next step would be to review pcloud support (52294) but it will be refactored this week by scroiset10:44
bauzasso Nikolay_St and Dina, you won't have to review our code by this week10:44
bauzasnext week, we would have probably to ask you to review a huge number of reviews thou10:45
bauzasmake sure you dedicate enough time about it10:45
Nikolay_Stoh, sorry about it10:45
bauzasno pb10:45
bauzas#info Physical use-cases reviews will need to be done intensively by next week, make sure dedicating enough time for it10:46
bauzasok, I think w're done with this topic10:47
bauzasany other reviews to discuss ?10:47
*** rongze has quit IRC10:47
bauzasok, last topic then10:48
bauzas#topic open discussion10:48
*** openstack changes topic to "open discussion (Meeting topic: climate)"10:48
bauzasany other concerns to raise, folks ?10:48
*** rongze has joined #openstack-meeting10:48
Nikolay_StI don't think so10:48
bauzasme too10:48
scroisetnop10:48
Nikolay_StCan't remember anything to discuss10:48
bauzasok, closing the conf then, thanks all for your presence10:49
bauzas#endmeeting10:49
*** matsuhashi has joined #openstack-meeting10:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"10:49
openstackMeeting ended Wed Nov 13 10:49:15 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-11-13-09.59.html10:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-11-13-09.59.txt10:49
openstackLog:            http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-11-13-09.59.log.html10:49
*** beagles has quit IRC10:52
*** rongze has quit IRC10:52
*** ArxCruz has joined #openstack-meeting10:54
*** boris-42 has quit IRC10:54
*** Fdot has quit IRC10:55
*** matsuhashi has quit IRC10:56
*** matsuhashi has joined #openstack-meeting10:57
*** Shaan7 has quit IRC10:59
*** matsuhas_ has joined #openstack-meeting11:00
*** matsuhashi has quit IRC11:00
*** coolsvap has quit IRC11:00
*** saurabh_ has quit IRC11:03
*** saurabh_ has joined #openstack-meeting11:04
*** sarob has joined #openstack-meeting11:04
*** beagles has joined #openstack-meeting11:07
*** sarob has quit IRC11:09
*** SergeyLukjanov has joined #openstack-meeting11:12
*** jasondotstar has joined #openstack-meeting11:14
*** SergeyLukjanov has quit IRC11:16
*** jdurgin has quit IRC11:17
*** pcm_ has joined #openstack-meeting11:18
*** SergeyLukjanov has joined #openstack-meeting11:18
*** SergeyLukjanov has quit IRC11:19
*** pcm_ has quit IRC11:25
*** doron_afk is now known as doron11:25
*** pcm_ has joined #openstack-meeting11:25
*** kmartin has quit IRC11:26
*** plomakin has joined #openstack-meeting11:27
*** jdurgin has joined #openstack-meeting11:29
*** boden has quit IRC11:32
*** SergeyLukjanov has joined #openstack-meeting11:35
*** adalbas has joined #openstack-meeting11:38
*** HenryG has joined #openstack-meeting11:45
*** SergeyLukjanov has quit IRC11:45
*** aepifanov has quit IRC11:47
*** nosnos_ has quit IRC11:52
*** nosnos has joined #openstack-meeting11:53
*** nosnos has quit IRC11:53
*** nosnos has joined #openstack-meeting11:54
*** matsuhas_ has quit IRC11:58
*** nosnos has quit IRC11:58
*** matsuhashi has joined #openstack-meeting11:59
*** nosnos has joined #openstack-meeting11:59
*** ndipanov_gone is now known as ndipanov12:03
*** matsuhashi has quit IRC12:03
*** yaguang has quit IRC12:03
*** nosnos has quit IRC12:04
*** sarob has joined #openstack-meeting12:05
*** nadya_ has quit IRC12:07
*** sarob has quit IRC12:09
*** rongze has joined #openstack-meeting12:20
*** sandywalsh has quit IRC12:23
*** fifieldt has quit IRC12:25
*** jasondotstar has quit IRC12:26
*** masayukig has quit IRC12:28
*** masayukig has joined #openstack-meeting12:30
*** nkhare has quit IRC12:32
*** yassine_ has quit IRC12:33
*** yassine has quit IRC12:33
*** yassine has joined #openstack-meeting12:33
*** masayukig has quit IRC12:34
*** sandywalsh has joined #openstack-meeting12:35
*** dims has joined #openstack-meeting12:39
*** matiu has quit IRC12:40
*** doron is now known as doron_afk12:42
*** yaguang has joined #openstack-meeting12:42
*** yaguang has quit IRC12:44
*** yaguang has joined #openstack-meeting12:44
*** masayukig has joined #openstack-meeting12:47
*** masayukig has quit IRC12:47
*** nati_ueno has joined #openstack-meeting12:50
*** nprivalova has joined #openstack-meeting12:52
*** masayukig has joined #openstack-meeting12:55
*** masayukig has quit IRC12:59
*** masayukig has joined #openstack-meeting12:59
*** suo has quit IRC13:00
*** pdmars has joined #openstack-meeting13:01
*** masayukig has quit IRC13:04
*** masayukig has joined #openstack-meeting13:04
*** fnaval_ has joined #openstack-meeting13:04
*** masayukig has quit IRC13:05
*** masayukig has joined #openstack-meeting13:05
*** sarob has joined #openstack-meeting13:05
*** dprince has joined #openstack-meeting13:08
*** rakhmerov has left #openstack-meeting13:09
*** davidhadas has quit IRC13:10
*** sarob has quit IRC13:10
*** galstrom_zzz is now known as galstrom13:11
*** thomasem has joined #openstack-meeting13:12
*** galstrom is now known as galstrom_zzz13:13
*** doron_afk is now known as doron13:16
*** Linz has quit IRC13:18
*** boris-42 has joined #openstack-meeting13:22
*** DuncanT- has quit IRC13:28
*** ilyashakhat has joined #openstack-meeting13:28
*** DuncanT- has joined #openstack-meeting13:29
*** dims has quit IRC13:32
*** dims has joined #openstack-meeting13:32
*** nprivalova has quit IRC13:37
*** eharney has joined #openstack-meeting13:38
*** masayukig has quit IRC13:38
*** masayukig has joined #openstack-meeting13:38
*** topol has joined #openstack-meeting13:39
*** neelashah has joined #openstack-meeting13:40
*** dkranz has joined #openstack-meeting13:40
*** ilyashakhat has quit IRC13:45
*** jasondotstar has joined #openstack-meeting13:45
*** jorisroovers has joined #openstack-meeting13:47
*** nati_ueno has quit IRC13:49
*** nati_ueno has joined #openstack-meeting13:49
*** nati_ueno has quit IRC13:54
*** jorisroovers has quit IRC13:58
*** bgorski has joined #openstack-meeting13:58
*** s3wong has joined #openstack-meeting14:00
*** ywu has joined #openstack-meeting14:01
*** markpeek has joined #openstack-meeting14:04
*** ben_duyujie has joined #openstack-meeting14:05
*** tomoe_ has joined #openstack-meeting14:05
*** s3wong has quit IRC14:05
*** ndipanov_ has joined #openstack-meeting14:05
*** ndipanov has quit IRC14:06
*** dvarga has joined #openstack-meeting14:07
*** lblanchard has joined #openstack-meeting14:09
*** IlyaE has joined #openstack-meeting14:10
*** mjbright has joined #openstack-meeting14:10
*** julim has joined #openstack-meeting14:11
*** nprivalova has joined #openstack-meeting14:13
*** rfolco has quit IRC14:13
*** jtomasek has quit IRC14:14
*** BobBallAway has joined #openstack-meeting14:14
*** jtomasek has joined #openstack-meeting14:15
*** sc68cal has joined #openstack-meeting14:16
*** whenry has quit IRC14:18
*** nermina has joined #openstack-meeting14:21
*** jcoufal-mob has joined #openstack-meeting14:22
*** joesavak has joined #openstack-meeting14:23
*** ndipanov_ is now known as ndipanov14:24
*** jcoufal-mob has quit IRC14:25
*** jcoufal-mob has joined #openstack-meeting14:25
*** rfolco has joined #openstack-meeting14:26
*** whenry has joined #openstack-meeting14:26
*** sc68cal has left #openstack-meeting14:28
*** jcoufal-mob has quit IRC14:30
*** herndon_ has joined #openstack-meeting14:31
*** lbragstad has joined #openstack-meeting14:31
*** weshay has joined #openstack-meeting14:32
*** sushils has quit IRC14:32
*** sushils has joined #openstack-meeting14:36
*** sarob has joined #openstack-meeting14:36
*** oubiwann has joined #openstack-meeting14:36
*** fnaval_ has quit IRC14:37
*** sarob has quit IRC14:40
*** rongze has quit IRC14:44
*** rongze has joined #openstack-meeting14:44
*** alexpilotti has joined #openstack-meeting14:48
*** topol has quit IRC14:48
*** ildikov has quit IRC14:48
*** rongze has quit IRC14:49
*** herndon_ has quit IRC14:51
*** rongze has joined #openstack-meeting14:52
*** dcramer_ has joined #openstack-meeting14:52
*** davidhadas has joined #openstack-meeting14:55
*** fnaval_ has joined #openstack-meeting14:58
*** fnaval_ has quit IRC14:58
*** jecarey has joined #openstack-meeting14:58
*** fnaval_ has joined #openstack-meeting14:58
*** jasondotstar has quit IRC14:58
*** matrohon_ has joined #openstack-meeting14:58
johnthetubaguy#startmeeting XenAPI15:00
openstackMeeting started Wed Nov 13 15:00:04 2013 UTC and is due to finish in 60 minutes.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: XenAPI)"15:00
openstackThe meeting name has been set to 'xenapi'15:00
johnthetubaguyhello everyone15:00
johnthetubaguywho is around for today's meeting?15:00
zigo_Hi!15:00
*** zehicle_at_dell has quit IRC15:01
*** nermina has quit IRC15:01
johnthetubaguycool, waiting for a few others to drop in15:01
johnthetubaguy#topic Blueprints15:02
*** openstack changes topic to "Blueprints (Meeting topic: XenAPI)"15:02
johnthetubaguy#link https://etherpad.openstack.org/p/IcehouseXenAPIRoadmap15:02
johnthetubaguyso we had a good design summit session15:02
johnthetubaguyjust wanted to make sure I got the summary of what we said correct:15:02
johnthetubaguyhttps://etherpad.openstack.org/p/IcehouseNovaSummit15:03
johnthetubaguyThe big headlines are deprecating stuff15:03
johnthetubaguyjust wondering about who is going to come forward for some of the other features15:03
*** vijendar has joined #openstack-meeting15:03
zigo_I'm sorry I missed them... :(15:03
johnthetubaguyand reminding people about getting blueprint in soon, and getting sponsors for those blueprints15:03
BobBallAwaySorry15:04
BobBallAwayI'm here15:04
*** matel has joined #openstack-meeting15:04
BobBallAwaylooks like our clocks were wrong15:04
matelHi15:04
BobBallAwayMate's clock says it's 2 minutes to15:04
matelIt's 14:5815:04
BobBallAwaybut mine says 4 minutes past!15:04
johnthetubaguylol15:05
matelI'm pretty sure someone has already solved this problem.15:05
johnthetubaguyOK, so just wanted to go through my summary of the session15:05
johnthetubaguyhttps://etherpad.openstack.org/p/IcehouseNovaSummit15:05
*** alexpilotti has quit IRC15:05
johnthetubaguymostly just the headlines about deprecating stuff15:05
*** Sukhdev has joined #openstack-meeting15:05
johnthetubaguyThen would be good to talk about blueprints for Icehouse-1 (and maybe Icehouse-2/3)15:06
BobBallAwayThe deprecations should never be headlines... :)15:06
johnthetubaguyah, always headlines else no one reads it15:06
johnthetubaguySo, I have some dodgy draft patchs for: VCPU masking and VIF hotplug for XenAPI, so I will try push those soon15:07
BobBallAwayperfect15:08
johnthetubaguyDid them while waiting for the plane first thing in the morning, so it could be all rubbish, not looked at them again15:08
BobBallAwayMate and I were just discussing VIF hotplug15:08
johnthetubaguyGot a patch for the kernel args stuff, but not seen the KVM patch go in yet, but I may have missed it15:08
johnthetubaguyAnyways, what do we think we want to do in Icehouse-115:09
BobBallAwayGreat15:09
BobBallAwayIs that something that RS wants to use?15:09
BobBallAwayThe kernel args I mean15:09
johnthetubaguyNot yet, as far as I know, I was just bored in the airport, the shops had shut15:09
BobBallAwayWow - airport shops that were shut.  That's new!15:09
johnthetubaguyjust picked some easy stuff to hack on15:09
*** mrodden has joined #openstack-meeting15:09
johnthetubaguyYeah, 2am flight out of HK15:10
*** ilyashakhat has joined #openstack-meeting15:10
BobBallAwayThe real problem with Icehouse-1 is that it's only 4 weeks :(15:10
BobBallAwayI think of all things -1 should be longer than -2 and -315:10
BobBallAway#link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule15:10
BobBallAwayis the release schedule for those who haven't seen it15:10
matelLet's try to find some small items.15:10
BobBallAwayWhen I say 4 weeks, I mean 3 weeks.15:10
BobBallAway4 weeks total, 3 weeks left.15:11
johnthetubaguyright, well if they are bigger then so be it right?15:11
johnthetubaguyjust start now and target Icehouse-215:11
BobBallAwayAbsolutely15:11
johnthetubaguyso whats that list?15:11
BobBallAwayTargetting Icehouse-2 makes sense to me15:11
matelMaybe it's only me, but do we have a proper list, which just lists the items?15:11
johnthetubaguyI want to target icehouse-1, assuming I get them pushed up this week15:11
johnthetubaguyfor those little bits I mentioned, but we can ignore them15:12
johnthetubaguythey are low priority15:12
BobBallAwayI don't think there is a proper list Mate, no15:12
BobBallAwayWe've got the summit etherpad15:12
matelShould we create one?15:12
johnthetubaguyyeah, just the etherpad15:12
BobBallAwaybut that's got multiple lists15:12
matelMaybe a XenAPI wiki page?15:12
BobBallAwayyes - let's create one15:12
johnthetubaguywhy?15:12
matelSo that it's a good starting point?15:12
*** zehicle_at_dell has joined #openstack-meeting15:12
johnthetubaguyjust collaspse the stuff in the etherpad into a single list15:13
BobBallAwayWhy on XenAPI wiki?15:13
johnthetubaguyif thats what we want15:13
BobBallAwayyes agree with John15:13
matelIt would be useful for me to have a proper list.15:13
BobBallAwayhttps://etherpad.openstack.org/p/IcehouseXenAPIRoadmap_Condensed15:13
matelWhich would show the progress...15:13
johnthetubaguywhat is proper? what info are you looking at?15:13
johnthetubaguywell thats the blueprints in launchpad right?15:13
*** jmontemayor has joined #openstack-meeting15:13
matelA list, who is assigned to it, and a link to the blueprint15:13
johnthetubaguywe just need to decide what is worth going into a blueprint for Icehouse15:13
johnthetubaguysure15:14
matelOkay, let me find the perfect launchpad query.15:14
johnthetubaguywell, I think we are probably better doing this offline, and claiming things we want to work on in the etherpad?15:14
matelMy problem with etherpad is that it's a bit too dynamic...15:14
johnthetubaguyits got versions and snapshots etc, just need to use them15:15
johnthetubaguyits ours to use as we please right?15:15
*** jasondotstar has joined #openstack-meeting15:15
johnthetubaguyanyways, feel free to put it into a wiki if that works better for you15:15
matelA launchpad query is fine.15:15
BobBallAwaySee the condensed list I just made15:15
BobBallAwayhttps://etherpad.openstack.org/p/IcehouseXenAPIRoadmap_Condensed15:15
johnthetubaguyjust wondering if we can decide some big "Themes" of stuff we want to do15:15
johnthetubaguycool, so who ones to own the deprecation stuff?15:16
johnthetubaguywants to own^15:16
*** sacharya has joined #openstack-meeting15:16
mateldeprecation stuff - what does that mean?15:16
BobBallAwayAbsolutely not - it's fine to say it's deprecated, but I have no plans to actually remove it15:16
johnthetubaguyyes, we need to add log messages and stuff15:16
johnthetubaguyI can take that on15:17
matelyou guys overuse stuff15:17
BobBallAwaySo you actually see that as a priority?15:17
johnthetubaguyyup15:17
BobBallAwayheh :)15:17
BobBallAwaySo you'll add a BP for that then15:18
johnthetubaguyits extra stuff to maintain otherwise15:18
johnthetubaguyI will do what we need to, not sure what that is yet15:18
matelHow can you specify a blueprint filter?15:18
BobBallAwayI guess you're managing those two too15:18
*** alexpilotti has joined #openstack-meeting15:18
matelhttps://blueprints.launchpad.net/nova/?searchtext=xenapi15:19
matelIs this the list that we need?15:19
johnthetubaguyyeah, that should do the trick15:19
johnthetubaguynot sure if you can tag blueprints, maybe not15:19
BobBallAwayThought you added the kernel command line support John?15:19
matelLet's say this is the list.15:19
BobBallAwayThat's the list of current blueprints15:20
BobBallAwayhowever we need to write new ones for Icehouse15:20
johnthetubaguyindeed15:20
johnthetubaguyso what you fancy for Icehouse15:20
matelOr modify the existing ones.15:20
johnthetubaguymatel: sure, in some cases, could just mark some obsolete as well15:20
BobBallAwayPersonally I fancy us doing vGPU15:21
BobBallAwaybut I haven't sized things to see if that fits15:21
johnthetubaguythats a good one, marketing wise15:21
johnthetubaguyhow about PCI passthrough as well, given thats going to be changing good to get that in there15:22
BobBallAwayIt probably will, but I can't promise anything until next wednesday - we'll be having discussions internally on what we're prioritising15:22
BobBallAwayMaybe15:22
BobBallAwayPCI pass through is a poor-mans vGPU15:22
*** markpeek has quit IRC15:22
BobBallAwayand other people have expressed interest in helping15:22
BobBallAwayso I don't want Citrix to commit to it.15:22
johnthetubaguyOK15:23
BobBallAwayI think we can probably say it's likely to make I-3 - even if we don't do it ourselves15:23
*** topol has joined #openstack-meeting15:23
BobBallAwayDon't need to advertise15:23
johnthetubaguywhy?15:23
BobBallAwayI'm in discussions with someone about it ATM15:23
johnthetubaguyOK, if they can be public it helps people15:24
BobBallAwayit will be entirely public15:24
BobBallAwayor did you mean now?  It's some guys from bull.net who are interested15:24
johnthetubaguywhat I mean is, we can same people are showing an intested, cool15:24
BobBallAwayyup15:25
johnthetubaguywe will need full tempest before Icehouse-215:25
johnthetubaguyI mean 215:25
johnthetubaguygrrr15:25
johnthetubaguyI mean 315:25
BobBallAwayYup15:26
BobBallAwayI'd like to see it in I-1 but realistically it might not make it till I-215:26
BobBallAwaydepends on what we have to do15:26
johnthetubaguyOk15:27
johnthetubaguyI just saw your notes on neutron security groups, thats all15:27
johnthetubaguyis that neutron full tempest?15:27
BobBallAwayyes15:27
johnthetubaguycool15:27
johnthetubaguyusing ML2?15:27
BobBallAwaynova network full tempest is "working"15:27
johnthetubaguyright, in its broken way15:27
*** mdenny has joined #openstack-meeting15:28
*** jasondotstar has quit IRC15:28
BobBallAwayPlease expand?15:28
matelSorry, what's the question here?15:28
BobBallAwayIs neutron using ML215:28
johnthetubaguywell, I think you said the tests were not swesome at the moment15:28
BobBallAwayuhhh I did?15:28
johnthetubaguyI was thinking about neutron + XenServer + ML2 and its status15:29
johnthetubaguyanyways, we can come back to that15:29
matelI don't know, if it's an ML2 config.15:29
matelAfaik ML2 is just a framework, isn't it?15:29
*** wwallnrr__ has joined #openstack-meeting15:29
matelI think secgroups will be broken there as well.15:30
johnthetubaguyduno about ML215:30
johnthetubaguyI got the idea it was the next generation plugin15:30
matelBut the fair answer is that I don't know what is the status of ML2 - XenServer15:31
johnthetubaguybut anyways15:31
johnthetubaguyI added a few more into the back list with my name15:31
johnthetubaguyI notice there is nothing about getting XenServer onto supported APIs further15:31
*** jasondotstar has joined #openstack-meeting15:31
BobBallAwayCorrect15:32
BobBallAwayThat will be a priority again soon15:32
BobBallAwaybut we need changes in XenServre15:32
johnthetubaguywell, that should go on the list I guess15:32
BobBallAwayand they won't fit in Augusta15:32
johnthetubaguyah15:32
BobBallAwayso XenServer changes will be post-Icehouse15:32
johnthetubaguymaybe not on the list then15:32
johnthetubaguyOK...15:32
BobBallAwayhence no point in making changes in Icehouse for them :)15:32
johnthetubaguyso lets move away from blueprints15:32
johnthetubaguywe clearly need to all go away and do our own planning15:32
johnthetubaguybut we have a start15:33
BobBallAwayyes15:33
BobBallAwayThat's our current thinking which is great15:33
johnthetubaguycool15:33
*** ndipanov has quit IRC15:33
BobBallAwaybut all caveated by we need to do internal planning15:33
*** rnirmal has joined #openstack-meeting15:33
*** dolphm has joined #openstack-meeting15:33
BobBallAwaydo you care about live migrate for resize if it's being deprecated?15:34
johnthetubaguyresize down is deprecated15:34
johnthetubaguynot resize up15:34
*** vijendar has quit IRC15:34
BobBallAwayHang on - isn't resize down is to be removed rather than deprecated?15:34
johnthetubaguymaybe that wasn't clear in the session, oops15:34
*** eharney has quit IRC15:35
johnthetubaguywe can't remove it15:35
*** vijendar has joined #openstack-meeting15:35
BobBallAwayoh - why not?15:35
johnthetubaguywe can deprecate it in Icehouse then remove in J15:35
*** coolsvap has joined #openstack-meeting15:35
johnthetubaguyits our agreed contract with users15:35
*** masayukig has quit IRC15:35
matelI guess we can't remove anything - we need to deprecate things first.15:35
matelWhich is good.15:35
BobBallAwaymeh15:35
johnthetubaguyand give them a chance to shout15:35
*** akuznetsov has quit IRC15:35
johnthetubaguyto fix it up themselves, should they want it15:35
BobBallAwaywe change the contract willy nilly in other places :P15:35
*** Sukhdev has quit IRC15:35
BobBallAwaybut fair enough :P15:35
johnthetubaguyyeah, we do define where the contract is firm15:36
johnthetubaguythe API15:36
johnthetubaguyalmost everything else may change15:36
johnthetubaguyRPC must be backwards compatible15:36
BobBallAwayok15:36
*** sarob has joined #openstack-meeting15:36
johnthetubaguyanyways15:36
johnthetubaguy#topic Docs15:36
*** openstack changes topic to "Docs (Meeting topic: XenAPI)"15:37
*** alexpilotti has quit IRC15:37
johnthetubaguyany updates here?15:37
johnthetubaguyany new plans?15:37
*** doron is now known as doron_afk15:37
*** shakayumi has joined #openstack-meeting15:38
BobBallAway'fraid no updates or new plans15:38
BobBallAwaywe need to do it15:38
*** vito-ordaz has joined #openstack-meeting15:38
johnthetubaguysure, we can agree that :)15:38
johnthetubaguy#topic Bugs and QA15:38
*** openstack changes topic to "Bugs and QA (Meeting topic: XenAPI)"15:38
johnthetubaguyany updates on getting tempest running on all commits?15:38
*** otherwiseguy has joined #openstack-meeting15:39
BobBallAwayyes15:39
BobBallAwayThere's lots of work to do and lots of options to look at15:39
BobBallAwayand we might need some hardware - so we'll probably be asking Rackspace if they can help out at all on that :)15:39
BobBallAwayChances are we have to use TripleO to get gating15:39
johnthetubaguyso how have you got running it in the cloud?15:39
BobBallAwaybecause even if we can get it working in RS cloud, we need redundancy and it can't run in HP cloud15:40
johnthetubaguywe can have multiple regions15:40
*** sacharya has quit IRC15:40
BobBallAwayMonty was quite clear about RS vs HP cloud15:40
johnthetubaguyI am worried here about tempest running, not us gating on things15:40
johnthetubaguyI know we should have both to become a gate15:40
BobBallAwayhe didn't mention regions - and I assume he knows about them15:40
BobBallAwayAh, fair enough15:40
*** sarob has quit IRC15:41
johnthetubaguyI worry about tempest tests asap15:41
*** caitlin56 has joined #openstack-meeting15:41
BobBallAwaywell - our focus is gating.  Not sure if we'll be pursuing full tempest non gating15:41
*** herndon_ has joined #openstack-meeting15:41
johnthetubaguywe can talk to him separately about different regions, we have a lot more regions now then when they last looked15:41
johnthetubaguyAh15:41
johnthetubaguycan I look at helping with tempest15:41
johnthetubaguyI don't want to drop out of tree15:41
BobBallAwayAgreed15:41
BobBallAwayWhat are you thinking we'd do though?15:42
johnthetubaguyan non-voting zuul test using rax cloud seems good15:42
BobBallAwayuse xenserver-core on a RS performance flavor?15:42
johnthetubaguyyup15:42
BobBallAwayThat's pretty close now I think/hope... ... ... :)15:42
BobBallAwayas we discussed15:42
johnthetubaguyyes, but you said you were not going to bother with that any more15:42
*** rakhmerov has joined #openstack-meeting15:42
johnthetubaguyI see that as top priority myself15:42
*** sdake has quit IRC15:43
BobBallAwayLet me refresh my memory on the current status then we can sync up outside of the meeting15:43
johnthetubaguyOK15:43
*** doron_afk is now known as doron15:43
*** sdake has joined #openstack-meeting15:43
johnthetubaguywell I am happy to help join up some docs15:43
johnthetubaguydots^15:43
johnthetubaguyif thats what we need to get tempest tests15:43
BobBallAwayAs we talked about at the summit I think the missing piece is that we might need to have a Nova call to boot a VM in HVM mode15:44
johnthetubaguyI can use the same thing to look at cloud-cafe tests, with cells, etc, etc15:44
*** pablosan has joined #openstack-meeting15:44
johnthetubaguywell, we have image sharing soon I hope, which is an alternative15:44
BobBallAwayMaybe15:44
BobBallAwayMonty wanted it to be set up on default images15:44
BobBallAwayrather than a custom made one15:44
BobBallAwaybut perhaps he can be convinced on that15:45
johnthetubaguywell, we can see what we can do15:45
johnthetubaguyit might just mean building the cached template stuff etc could be a little harder15:45
johnthetubaguylets sync up about the options15:45
BobBallAwayyup15:45
*** nprivalova has quit IRC15:46
johnthetubaguy#topic Open Discussion15:46
*** openstack changes topic to "Open Discussion (Meeting topic: XenAPI)"15:46
johnthetubaguyanything else people are worrying about?15:46
matelA q15:46
johnthetubaguymatel: fire away15:46
matelCould we have this meeting in a video conference or something like that?15:46
matelOr what is your idea about it?15:47
*** ndipanov has joined #openstack-meeting15:47
johnthetubaguynot really, IRC is the default, because you get minuets15:47
*** kgriffs_afk is now known as kgriffs15:47
johnthetubaguythere is a phone bridge that openstack has setup15:47
BobBallAwayI think I'd rather see us change the things that mean that the IRC meetings are effective15:47
*** matiu has joined #openstack-meeting15:48
*** vito-ordaz has quit IRC15:48
johnthetubaguysure, basically, what is causing you problems with participating?15:48
johnthetubaguyideas are welcome15:48
*** sneelakantan has joined #openstack-meeting15:48
johnthetubaguylets try them, if its better, we keep them15:48
BobBallAwaythey are not as useful as they should be ATM because the three of us are so close and talk during the week - so it's usually just a reminder of what we've already talked about15:48
*** vito-ordaz has joined #openstack-meeting15:48
johnthetubaguywell, there is no point it just being a reminder, I usually find its new stuff for me15:48
BobBallAwayIf we had more participants from RS or the guys from bull.net (which I'll suggest) then the meeting would make more sense :P15:48
*** pablosan has quit IRC15:49
johnthetubaguywhat time would work for bull.net?15:49
BobBallAwayI don't know - but I'm sure its' not a question of the meeting time.15:49
johnthetubaguythere is little for other at Rax to contribute at the moment, we are not really doing loads of work on the xenapi layer, its mostly all above that15:49
BobBallAwayAs I said - I'll suggest it15:49
johnthetubaguysure, well happy to get bull.net more involved in these meeting, would be good to understand what is blocking participation15:50
johnthetubaguywe could try google hangout or whatever if this really doesn't work for everyone15:50
johnthetubaguybut not sure how much that will buy us15:50
matelOkay, then not do that.15:51
*** jmontemayor has quit IRC15:51
matelI think it would be better if we had more people here.15:51
matelhaving a hangout would be a more closed thing.15:51
BobBallAwayEven if they are only interested parties rather than people coding XenAPI15:51
*** terriyu has joined #openstack-meeting15:52
johnthetubaguywell, not sure who all these people would be, I have invited others working on XenAPI at Rax to drop in when they do related stuff15:52
johnthetubaguybut thats just not very often, apart from chasing down the odd bug15:52
BobBallAwayIt is a shame - cuz there are quite a few commits in the XenAPI tree from others at RS15:53
*** vito-ordaz has quit IRC15:53
*** yaguang has quit IRC15:53
BobBallAwaye.g. one where it would have made a lot of sense was the ghosting work done a while ago, or the memory prediction stuff - they would have been useful to have IRC discussions about rather than discussions on the reviews15:53
matelI suggested the hangout, because sometimes I get lost in the communication, but that might only be me.15:54
johnthetubaguywell, we need to rework all that I think15:54
johnthetubaguyso might be worth it15:54
johnthetubaguythe main issue is this time doesn't work well for most of them15:54
BobBallAwayWell we can move an hour later or to a diff day if that works better15:55
matelWhat time would work for them?15:55
johnthetubaguything is the old time we had that worked fro them, didn't work for you guys15:55
*** xyang1 has joined #openstack-meeting15:55
*** belmoreira has quit IRC15:55
matelWhat's the time that was working for them?15:56
BobBallAwayBut they weren't coming :)15:56
*** maxdml has joined #openstack-meeting15:56
johnthetubaguysure15:56
BobBallAwayIf they were attending the meeting then it would have been a good reason to find a comproimise or stick with that time15:56
johnthetubaguyso lets just see what happens15:56
BobBallAwaybut since it was only us it didn't make sense to do it so late15:56
johnthetubaguyOK15:56
BobBallAwayBut this time should be OK most of the time anyway15:56
matelThe main point here is that we just need to make it clear: these meetings are not useful enough, and we need to understand why is that.15:57
BobBallAwayI used to have my call with Ant at this time15:57
BobBallAway:)15:57
BobBallAwayI agree with Mate - I know you said you get new stuff John - but from my perspective they could be - and should be - more useful than I find them ATM15:57
johnthetubaguyyeah, he is in the texas office, all the nova devs are working from home15:57
BobBallAwayAhh - didn't know that15:58
BobBallAwayso we have to work with west coast? :/15:58
*** saurabh__ has joined #openstack-meeting15:58
johnthetubaguyour lead dev is west coast, comstud15:58
BobBallAwaythat's a pain...15:58
BobBallAwayhadn't realised that15:58
*** joel-coffman has joined #openstack-meeting15:59
BobBallAwayAnyway15:59
BobBallAwaywe're out of time15:59
BobBallAwayJohn - could you have a chat with comstud and see if it's the meeting time that stops him attending, or something else?15:59
BobBallAwaymaybe others in the team you think would be useful16:00
BobBallAwayI'll talk with the bull.net guys to see if they can come sometimes16:00
*** vijendar has quit IRC16:00
johnthetubaguywell I don't think he generally has anything to discuss about XenAPI, he is working on the objects stuff and cells right now16:00
johnthetubaguy#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Nov 13 16:00:33 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-11-13-15.00.html16:00
*** vijendar has joined #openstack-meeting16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-11-13-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-11-13-15.00.log.html16:00
johnthetubaguydamm, sorry bob, meant to let you kill that one16:00
BobBallAwayWell the cells stuff is kinda relevant if we're saying that pools should use cells :)16:00
BobBallAwayoh16:01
johnthetubaguywell, not for six months or more16:01
*** jmontemayor has joined #openstack-meeting16:01
BobBallAwayI'd forgotten :D16:01
*** kartikaditya has joined #openstack-meeting16:01
BobBallAwaygotta run16:01
*** jbernard has joined #openstack-meeting16:01
*** jungleboyj has joined #openstack-meeting16:01
DuncanT-Anybody for the cinder meeting?16:02
*** winston-d has joined #openstack-meeting16:02
jungleboyjYes.  jgriffith said this was the time.  :-)16:02
jbernardi thought one more hour to go, no?16:02
winston-dno, should be now16:02
jungleboyjjbernard: No, DST change.16:02
jbernardahh16:02
*** ehudtr has joined #openstack-meeting16:02
caitlin56i am16:03
*** jmontemayor has quit IRC16:04
*** joesavak has quit IRC16:04
*** jlucci has joined #openstack-meeting16:04
*** joesavak has joined #openstack-meeting16:04
*** jmontemayor has joined #openstack-meeting16:05
*** caitlin56 has quit IRC16:05
* jungleboyj calendar is now updated to GMT. :-)16:06
*** egallen has joined #openstack-meeting16:06
med_no, should be now as the meetings are on UTC16:07
*** shakayumi has quit IRC16:07
*** aepifanov has joined #openstack-meeting16:07
*** sarob has joined #openstack-meeting16:07
*** DrBacchus has quit IRC16:07
DuncanT-Give jgriffith 5 minutes then start without him....16:08
med_and it is 1600 right now16:08
*** ildikov has joined #openstack-meeting16:08
DuncanT-Mentioning his name usually summmons him...16:08
med_he may be mid-commute16:08
DuncanT-He was online 30 mins ago and seemed to have the time shift correct16:09
*** caitlin56 has joined #openstack-meeting16:09
*** Guest82915 has joined #openstack-meeting16:09
*** DrBacchus has joined #openstack-meeting16:09
guitarzansure... jgriffith reminds us all about DST and then doesn't show up16:10
*** sacharya has joined #openstack-meeting16:10
med_heh16:10
*** galstrom_zzz is now known as galstrom16:11
*** vito-ordaz has joined #openstack-meeting16:12
*** sarob has quit IRC16:12
DuncanT-Shall we go anyway?16:13
med_avishay should go imho16:13
DuncanT-#startmeeting Cinder16:13
openstackMeeting started Wed Nov 13 16:13:17 2013 UTC and is due to finish in 60 minutes.  The chair is DuncanT-. Information about MeetBot at http://wiki.debian.org/MeetBot.16:13
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:13
*** openstack changes topic to " (Meeting topic: Cinder)"16:13
openstackThe meeting name has been set to 'cinder'16:13
winston-dDuncanT-: good call16:13
DuncanT-avishay isn't here yet AFAICT16:13
DuncanT-Is Ehud Trainin here?16:14
ehudtryes16:14
jgriffithgo figure16:14
DuncanT-#topic Fencing16:14
*** openstack changes topic to "Fencing (Meeting topic: Cinder)"16:14
DuncanT-Oh, hi Jogn, all yours ;-)16:14
DuncanT-Jogn? John even16:15
jgriffith:)16:15
*** jlucci has quit IRC16:15
jgriffithLooks like Ehud is hanging with Dave W16:15
*** jlucci has joined #openstack-meeting16:15
DuncanT-ehudtr: The stage is all yours....16:15
ehudtrFollowing last dicussion I agree two of your comments regarding the fencing implementation16:15
ehudtrI accept your comment fencing should take care also for detaching the volumes at the Cinder level.16:16
ehudtrI accept your comment it is not necessary to add into Cinder a blacklist of hosts nor an unfence method.16:16
*** zehicle_at_dell has quit IRC16:16
ehudtrI do think it should be possible to fence/force-detach a host through a new method of force-detach-host, rather then trying to change the current detach-volume method to force a detachment at the storage level and use such method for each one of the volumes attached to a host.16:17
*** nkhare has joined #openstack-meeting16:17
*** zehicle_at_dell has joined #openstack-meeting16:17
*** hodos has joined #openstack-meeting16:17
ehudtrfor several reasons16:17
ehudtrIn case of NFS it is not possible to force-detach a volume.16:17
ehudtrIn cases it is possible, there would still be a problem when shared volumes would supported by Cinder16:18
jgriffithehudtr: TBH in NFS we don't really ever detach to begin with :)16:18
*** _ozstacker_ has quit IRC16:18
*** burt has joined #openstack-meeting16:18
ehudtrIt is an optimization, which may be valuable for fast recovery: send 1 request rather than N (e.g. 100) requests16:18
*** ozstacker has joined #openstack-meeting16:19
caitlin56Isn't "NFS support" something the specific volume driver would be responsible for?16:19
*** vijendar has left #openstack-meeting16:19
jgriffithI still have the same concerns I raised previously WRT the complication and potential for errant fencing to occur16:19
*** ryanpetrello has joined #openstack-meeting16:19
ehudtrI think we would like to prevent access at the storage level16:20
caitlin56jgriffith: +116:20
jgriffithMy only other question is "is this a real problem"16:20
jgriffithanybody else have any thoughts on this?16:20
guitarzanis there a proposal written up somewhere?16:21
winston-dlive migration, maybe16:21
DuncanT-I think it is a real problem, yes. We do something very similar to a fence in compute node startup16:21
jgriffithhttps://blueprints.launchpad.net/cinder/+spec/fencing-and-unfencing16:21
guitarzanjgriffith: thanks!16:21
ehudtrFencing is something standard done in HA clusters like pacemaker16:21
*** tomoe_ has quit IRC16:21
winston-dsomeone reported such issue, when using ceph16:21
jgriffithtoo bad this wouldn't apply to Ceph :)16:21
dosaboywinston-d: did they raise a bug for that in the end, i did not see one16:22
*** Dinesh has joined #openstack-meeting16:22
jungleboyjI think as OpenStack is moving to HA we need to be considering how Cinder fits into that.16:22
ehudtrThe current option in openstack to do a rebuild without first fencing is a bug in my opinion16:22
winston-ddosaboy: no, i don't think so.16:22
jgriffithjungleboyj: don't confuse this with HA impl16:22
*** afazekas has quit IRC16:23
jgriffithOk16:23
jgriffithehudtr: sounds like folks are in favor of moving forward on this16:23
*** ildikov has quit IRC16:23
jungleboyjjgriffith: Ah, sorry.16:23
*** bpb has joined #openstack-meeting16:23
jgriffithehudtr: My concerns as I stated are just how to do this cleanly and mitigating having admins shoot themselves16:23
guitarzanas a counter example, we were looking at a way to do the exact opposite and whitelist at the ip level16:23
jgriffithguitarzan: I thnk that's kinda how the LIO target works16:24
*** eharney has joined #openstack-meeting16:24
*** DrBacchus has quit IRC16:24
jgriffithguitarzan: or how it "could" work I guess, right now we just read the connector info but it has hooks to have a white list16:24
*** jorisroovers has joined #openstack-meeting16:25
guitarzanjgriffith: nice, I'll have to look at that16:25
ehudtrI think one possible way to prevent admin to press to easily on the fence botton is enabling only if a host in a failed state16:25
DuncanT-I can see the point of the idea... waiting to see code before I have a strong opinion...16:25
DuncanT-How does cinder know a host is failed?16:25
*** ildikov has joined #openstack-meeting16:25
*** nermina has joined #openstack-meeting16:25
jgriffithguitarzan: https://github.com/openstack/cinder/blob/master/cinder/brick/iscsi/iscsi.py#L44116:25
ehudtrCinder needs not know the host is failed Nova and possibly Heat will know16:26
winston-dDuncanT-: notified by Nova?16:26
caitlin56I agree, cinder cannot determine this itself. It needs to come from other OpenStack components.16:27
jgriffithso add an API call to "notify-invalid-iqn's" or something of the sort?16:27
jgriffithand how is it cleared  :)16:27
jgriffithnova has to then have another command to add something back in16:27
jgriffithhonestly seems like this all needs to happen in nova first16:27
caitlin56Would't it be a one time transition. "Clear any attached volumes held by this compute instance."?16:28
jgriffithI think there's more work there than on this side (ie failure detection etc)16:28
jgriffithcaitlin56: sure, but if you blacklist a node, what happens when it comes back up and you want to add it back in to your cluster16:28
jgriffithYou have to clear it somehow16:28
jgriffithIt's not just clear current attach if I understand ehudtr correctly16:29
caitlin56A node is attempting to re-attach without having been in contact with nova?16:29
jgriffithehudtr: it's clear an attach and prevent that attach from being reconnected no?16:29
jungleboyjjgriffith: I was assuming that this would be managed by Nova and Cinder would just provide the tools.16:29
jgriffiththus the term "fencing"16:29
jgriffithjungleboyj: yes, that's what I'm getting at16:29
jgriffithjungleboyj: a good deal of nova work before getting to Cinder16:29
jgriffithand the Cinder side might not be so tough to implement16:30
jungleboyjjgriffith: +216:30
jgriffithemphasis on *might*16:30
jgriffith:)16:30
caitlin56I can definitely see the need for nova being able to tell Cinder "this guy is gone" but "don't talk to this guy" is something more dangerous.16:30
jungleboyjjgriffith: Just wanted to emphasize that.16:30
caitlin56Couldn't nova use neutron to enforce that without bothering Cinder?16:30
jgriffithcaitlin56: but I think that's what we're talking about... ehudtr ?? ^^16:30
winston-dand that's nova's problem16:30
jgriffithcaitlin56: nope16:31
ehudtrYes, I agree this would be managed by Nova. The fence host is needed to disconnect the host at the storage level16:31
jgriffithI don't want Neutron mucking about with my data path16:31
DuncanT-caitlin56: Nope, neutron doesn't get in the way of storage network usually16:31
jgriffithehudtr: but the question is you also want to prevent the failed node from connecting again right?16:31
jgriffithI think this is where the debate started last week :)16:31
jungleboyjehudtr: The important part is that you don't have the 'failed' host's node attempting to access the storage while the new node is being brought up.16:32
jungleboyjjgriffith: I would assume that is only if a new node has taken over.16:32
caitlin56Such a "failed node" shouldn't be using *any* OpenStack services, right? It's not just Cinder.16:32
jgriffithOk, two more minutes for this topic and then I think we should move on16:33
jgriffithjungleboyj: sure16:33
jgriffithcaitlin56: haha... probably16:33
DuncanT-caitlin56: Some services multiple accesses don't matter... block store it does16:33
jungleboyjcaitlin56: Depends on how it fails.  In situations like this you need to cover all the bases.16:33
jgriffiththis is where I went all wonky in the last discussion :)16:33
ehudtrYes, this was part of the original suggestion, but last meeting you suggested that preventing the failed node attempting during a new node creation may be done in Nova. I checked it and it seems this might be done in Nova only after the attach volume would be moved from nova-compute to nova-conductor.16:34
jgriffithOk... so my proposal:16:34
jgriffithehudtr:16:34
jgriffith1. Take a look at the nova work16:34
jgriffithFocus on things like failure detection16:34
jgriffithHow you would generate a notification16:34
jgriffithwhat would be needed from cinder (if anything versus disabling the initiator files etc)16:35
jgriffith2. After getting things sorted in Nova16:35
ehudtrI know how to do failure detection with Nova16:35
jgriffithGreat, step 1 is almost done then :)16:35
guitarzanhah16:35
jgriffithThen put together the proposal, make sure the Nova team is good with that16:35
jgriffithfrom there we can work on providing an API in Cinder to fence of initiators16:36
jgriffithI'd like to see what the code for that looks like though16:36
jgriffithand how to clear it16:36
jgriffithehudtr: sound reasonable?16:36
ehudtryes16:36
jgriffithDuncanT-: guitarzan jungleboyj caitlin56 ok ^^16:36
jgriffithwinston-d:16:36
DuncanT-Sounds sensible to me16:36
jungleboyjjgriffith: Sounds good to me.  Good summary to keep moving forward.16:36
*** caitlin56 has quit IRC16:37
jgriffithwinston-d: seem like that works for the error case you were thinking of?16:37
*** caitlin56 has joined #openstack-meeting16:37
jgriffithdosaboy: I have no idea how to make this work with Ceph but that's why you're an invaluable asset here :)16:37
jgriffithhemna_: you'll have to figure out FC :)16:37
jgriffithOk...16:38
guitarzanjust go yank the cable out16:38
jgriffithguitarzan: I'm down with that16:38
jgriffithguitarzan: DC Monkey.. fetch me that cable!16:38
*** rongze has quit IRC16:38
hodoshi guys, we at Nexenta are implementing a storage-assisted volume migration; we have run into a problem: there can be multiple storage  hosts connected to a single NFS driver. So there's one-to-many mapping...16:38
winston-ddsfasd16:38
jgriffith#topic patches and release notes16:39
*** rongze has joined #openstack-meeting16:39
jgriffithwinston-d: what's dsfasd?16:39
dosaboyjgriffith: it may actually be easier for ceph since it has the notion of 'watchers'16:39
guitarzanwinston-d: lagging?16:39
jgriffithdosaboy: yeah :)16:39
winston-djgriffith: sorry lagging16:39
jgriffithhaha16:39
DuncanT-hodos: Please wait until the any other business section of the meeting16:39
jgriffithno prob16:39
jgriffithSo quick note on this topic16:39
*** egallen has quit IRC16:39
*** aepifanov has quit IRC16:39
hodosok, sorry )16:39
DuncanT-#topic patches and release notes16:39
*** openstack changes topic to "patches and release notes (Meeting topic: Cinder)"16:39
jgriffithreviewers, I'd like for us when adding a patch that's associated with a BP or a Bug to update the doc/src/index file16:40
*** zbitter has joined #openstack-meeting16:40
jgriffiththat way I don't have to go back and try to do it every milestone :)16:40
jgriffithSame format as what's there16:40
jgriffithsimple summary, link16:40
jgriffithsound reasonable?16:40
jgriffithrolling release notes :)16:40
*** f_rossigneux has quit IRC16:40
*** bill_az has joined #openstack-meeting16:41
* jgriffith takes silence as agreement :)16:41
winston-dsounds good16:41
jungleboyjjgriffith: Sounds reasonable.16:41
jgriffithor just plain lack of interest and apathy16:41
jgriffithkk16:41
jgriffithnow to the hard stuff :)16:41
DuncanT-Something for reviewers to catch I guess...16:41
jgriffithDuncanT-: to catch yes16:41
winston-dwe do agree to write a cinder dev doc, right. make sure this is documented as well16:42
jgriffithnot a horribly big deal but it would be helpful IMO16:42
jungleboyjjgriffith: So just to be clear as a newbie ...16:42
DuncanT-Might be able to get a bot to catch simple cases after a while16:42
jgriffithwinston-d: excelelnt point16:42
jgriffithDuncanT-: hmmm... perhaps a git hook, yes16:42
jungleboyjjgriffith: If I approve something associated with a BP I would need to go update that file with appropriate information?16:42
jgriffithjungleboyj: oh.. no16:42
jgriffithjungleboyj: so the idea is that the submitter would add it16:42
jgriffithwhen core reviews it we should look for that entry16:43
jgriffithif people hate the idea or think it's a waste that's ok16:43
jgriffithjust say so16:43
jgriffithI don't mind doing it the way I have been16:43
caitlin56and if you don't approve patches without that link people should learn very quickly.16:43
jgriffithjust don't complain if your change isn't listed :)16:43
*** zaneb has quit IRC16:43
*** rongze has quit IRC16:43
*** hartsocks has joined #openstack-meeting16:43
jungleboyjjgriffith: Ahhh, ok ... That makes more sense.  Thanks for the clarification.16:43
*** zbitter is now known as zaneb16:43
DuncanT-I'd say we try it for a couple of weeks and see how it works out16:44
jgriffithworks for me16:44
jgriffithtrial basis16:44
jgriffithkk16:44
jgriffith#topic summit summary16:44
jgriffithhmmm16:44
jgriffith#topic summit-summary16:44
jgriffithcome on meetbot16:44
DuncanT-#topic summit-summary16:45
*** openstack changes topic to "summit-summary (Meeting topic: Cinder)"16:45
DuncanT-I started the meeting16:45
jungleboyjIt knows I am also in another summit summary meeting and my head may explode.16:45
*** Mandell has joined #openstack-meeting16:45
jgriffithlol16:45
jgriffithDuncanT-: thanks :)16:45
jgriffithokie16:45
jungleboyjo-)16:45
*** nikhil__|afk is now known as nik16:45
jgriffithI threw a quick overview together: https://etherpad.openstack.org/p/cinder-icehouse-summary16:45
jgriffithof course it's handy to review the etherpads from the sessions16:46
jgriffithbut I wanted to capture the main points in one doc16:46
*** nik is now known as Guest6879916:46
jgriffithI *think* these are the items that we had moderate concensus on16:46
jgriffiththe capabilities reporting maybe not so much... but I'm still pushing to go this route16:46
jgriffithWe can always make things *harder* but I don't know that we should16:47
DuncanT-I'd add that we seemed to agree state machine with atomic transitions was a good route to try, re taskflow16:47
jgriffithDuncanT-: for sure16:47
jgriffithadded16:47
*** doron is now known as doron_afk16:48
jgriffithanything else glaring that I missed (that somebody will actually get to)?16:48
winston-djgriffith: i think most of us in this room agreed on those capabilities16:48
*** davidhadas has quit IRC16:48
caitlin56Making snapshots a first layer object.16:48
jgriffithI left the import out intentionally for now by the way16:48
DuncanT-My take-away from the capabilities reporting was that we couldn't agree on anything at all16:48
jgriffithDuncanT-: I don't think that's really true16:48
*** rongze has joined #openstack-meeting16:48
jgriffithI think one person didn't agree16:48
DuncanT-jgriffith: I see no harm in adding it anyway16:49
jgriffithI think most of us agreed with what i've put on the list16:49
jgriffithwinston-d: I think you may have some other ideas/adds that would be fine as well16:49
jgriffithanyway...16:49
jgriffithanything pressing to add or remove here?16:49
DuncanT-jgriffith: O'll try to BP the stuff that redhat guy eventually explained, since it seemed valuable once I finally understood him16:49
DuncanT-s/O'll/I'll/16:50
jgriffithWe need more thought/info around the ACL's I think16:50
jgriffithDuncanT-: cool16:50
winston-dDuncanT-: can't wait to see the BP16:50
jgriffithDuncanT-: or work off the ehterpad for now16:50
jgriffithwhichever is faster and more effective16:50
jgriffithif we reach concensus prior to the BP it might help :)16:50
DuncanT-jgriffith: Etherpad might be easiest... I'll post a link when I'm done16:51
jgriffithsounds good16:51
*** rossella_s has quit IRC16:51
jgriffithEverybody should feel free to put some notes add question to the etherpad16:51
jgriffithbut the intent is not to open debate16:51
jgriffithjust to focus on what's there and build the ideas up16:51
jgriffithand use that info to build blueprints16:51
jgriffithand assign :)16:51
jgriffithanybody want to talk more on that?16:52
*** vito-ord_ has joined #openstack-meeting16:52
jgriffithif not I believe hodos had some things to talk about16:52
jgriffith#topic open16:52
* jgriffith never learns16:52
*** yassine has quit IRC16:52
DuncanT-#topic open16:52
*** openstack changes topic to "open (Meeting topic: Cinder)"16:52
hodosok so it touches not only Nexenta16:52
jungleboyj:-)16:53
*** gyee has joined #openstack-meeting16:53
jgriffithhodos: back up... what's "it"16:53
jgriffithafraid I ignored you earlier :)16:53
hodosso if we want ot do storage-to-storage migration without routing data through Cinder16:53
hodoson NFS16:53
hodoswe have 2 NFS drivers16:54
*** Mandell has quit IRC16:54
*** akuznetsov has joined #openstack-meeting16:54
caitlin56hodos: our bigger priority is enabling more operations on snapshots. I think the fix required for NFS is too much to tackle by icehouse.16:54
*** vito-ordaz has quit IRC16:54
*** nkhare has quit IRC16:54
*** thingee has joined #openstack-meeting16:54
thingeelawl, time change16:55
hodosso how does the source driver knows what storage host to use on the dest16:55
*** vito-ordaz has joined #openstack-meeting16:55
jgriffiththingee: :)16:55
winston-dthingee: you made it16:55
*** vito-ord_ has quit IRC16:55
jgriffithhodos: scheduler could help with that16:55
caitlin56Speaking of snapshots, I didn't hear any opposition to enabling snapshot replication. Shouldn't that be added to your list jgriffith?16:55
jgriffiththat is it's job after all16:55
hodosyes, but when I issue a command on the source storage driver16:55
hodosi need that info16:56
jgriffithhodos: :)16:56
vito-ordazu16:56
*** shakayumi has joined #openstack-meeting16:56
jgriffithhodos: frankly this is why I hate the whole "I'm going to talk to this backend directly" problem16:56
*** jhenner has quit IRC16:56
vito-ordazupdate_volume_stats for NFS driver not provide information about host16:56
jgriffithI'm not a fan of trying to implement Cinder based replication16:57
hodoshmm16:57
* jgriffith thinks it's a bad idea16:57
thingeewhy does the driver need to know which host (sorry catching up)16:57
caitlin56jgriffith the alternative is inefficient replication16:57
jgriffiththingee: he wants to talk directly from his backend to his *other* backend16:57
*** smurugesan has joined #openstack-meeting16:58
*** joesavak has quit IRC16:58
hodosto *my* other backend16:58
jgriffithcaitlin56: actually the atlernative is cinder doesn't do replication16:58
winston-dvito-ordaz: feel free to add any capability that you want to report,just note that scheduler can only consume some of them (basic ones)16:58
*** joesavak has joined #openstack-meeting16:58
med_maybe hodos is not a "he"16:58
hodosi'am16:58
hodos)16:58
*** garyk has quit IRC16:58
jgriffithmed_: fair16:58
med_or not.16:58
jgriffitheveryone... I aplogize for being gender specific16:58
thingeejgriffith, hodos: what's the use case?16:58
guitarzanthingee: migration from one backend to another16:59
guitarzanhomogeneous16:59
thingeewhy does a driver have to know? shouldn't cinder just be the bridge with that knowledge?16:59
hodosyes, say the same vendor, so these backends know how to talk16:59
vito-ordazproblem it that NFS drivers can control many storage backend at the same time.16:59
thingeeof another backend that meets that requirement...the scheduler will figure16:59
guitarzanthingee: so they can do it more cheaply16:59
winston-dhodos: don't we have a shortcut in migration?16:59
guitarzanit sounds hard to me :)16:59
thingeeso cinder says, hey you two backends, talk to each other17:00
hodos)17:00
thingeethe other backend never initates it is my point17:00
thingeejgriffith: that's time17:00
jgriffithFor the record, I don't think we should even implement replication in Cinder17:00
guitarzangot it17:00
*** jorisroovers has quit IRC17:00
*** jsavak has joined #openstack-meeting17:00
*** tjones has joined #openstack-meeting17:00
guitarzanDuncanT- has to throw the switch today17:00
jgriffithLet the sysadmin setup replication between devices if avaial and create a volume-type for it17:00
DuncanT-Right, I'm afraid we need to move channels17:00
med_yep17:01
DuncanT-#endmeeting17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:01
openstackMeeting ended Wed Nov 13 17:01:02 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-11-13-16.13.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-11-13-16.13.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-11-13-16.13.log.html17:01
*** Guest82915 has left #openstack-meeting17:01
* hartsocks waves17:01
*** inkerra has quit IRC17:01
*** winston-d has left #openstack-meeting17:01
hartsocksWho's around for the VMwareAPI subteam?17:01
tjonesgood morning17:01
rgerganovhi guys17:02
*** joel-coffman has left #openstack-meeting17:02
*** Dinesh has quit IRC17:02
*** caitlin56 has quit IRC17:02
hartsocks#startmeeting VMwareAPI17:03
openstackMeeting started Wed Nov 13 17:03:22 2013 UTC and is due to finish in 60 minutes.  The chair is hartsocks. Information about MeetBot at http://wiki.debian.org/MeetBot.17:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:03
*** openstack changes topic to " (Meeting topic: VMwareAPI)"17:03
openstackThe meeting name has been set to 'vmwareapi'17:03
*** joesavak has quit IRC17:03
*** jbernard has left #openstack-meeting17:03
vito-ordazit's not replication it standard call migrate_volume17:03
*** bauzas has quit IRC17:03
*** joesavak has joined #openstack-meeting17:03
*** thingee has left #openstack-meeting17:04
hartsocksHey folks. Last week was the summit.17:04
hartsocksSo we're just starting our IceHouse efforts.17:04
*** skolathu has joined #openstack-meeting17:04
*** ehudtr has quit IRC17:04
hartsocksI'm going to spend some quality time with the bugs & reviews today and send out a note later.17:05
*** jsavak has quit IRC17:05
hartsocksbut, for today, I'll post the etherpad link Tracy & Gary used during the HK summit.17:05
hartsocks#link #link https://etherpad.openstack.org/p/T4tQMQf5uS17:06
hartsocks#undo17:06
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x39fba10>17:06
hartsocks#link https://etherpad.openstack.org/p/T4tQMQf5uS17:06
*** blamar has quit IRC17:06
hartsocksDo we want to discuss blueprints that came out of that talk?17:06
*** vito-ordaz has quit IRC17:07
tjonesi've started one on the heathcheck (config check) item.  Ive gotten some interest from another team as well17:07
*** scottda has joined #openstack-meeting17:08
*** vito-ordaz has joined #openstack-meeting17:08
*** terriyu has quit IRC17:08
tjoneshttps://launchpad.net/rubick17:08
ogelbukhhi17:08
ogelbukhtjones: hello17:08
tjoneshi ogelbukh17:08
smurugesanHey all, Sabari here. Didn't realize Daylight ended, and we have the meeting an hour earlier.17:08
ogelbukhI confirm we're working on the configuration validation topic17:09
tjonesi have not had a chance to look into your project yet but will today.17:09
*** markvan has joined #openstack-meeting17:09
ogelbukhthanks!17:09
tjonesgreat - lets not duplicate work :-)17:09
ogelbukhtjones: it would be awesome to get your feedback17:09
hartsocksToday I Learned (TIL) project Rubick.17:09
*** sneelakantan has left #openstack-meeting17:09
*** skolathu has quit IRC17:10
tjones:-)  hartsocks it would be great if you can take a look too as this started out as your idea17:10
hartsocksogelbukh: so you are on Rubick?17:10
ogelbukhhartsocks: yes17:10
hartsockstjones: Ideas are cheap, execution is hard. :-)17:10
tjonesLOL17:10
ogelbukhwe're getting it to stackforge atm17:10
hartsocksogelbukh: so we started out (not just me) thinking we should fail-fast if our driver is configured wrong.17:11
ogelbukhwe have a basic framework and reference implementation17:11
ogelbukhfor keystone and couple other services17:11
hartsocksnice17:11
ogelbukhhartsocks: that's reasonable17:11
hartsocksogelbukh: so this project would fit that?17:11
*** vito-ordaz has quit IRC17:12
hartsocksI guess I'm asking if it will be a library, service, or etc.17:12
ogelbukhwell, we're planning it to be a service17:13
ogelbukhbut we're in early stage now17:13
ogelbukhso we could adjust it17:13
ogelbukhfor example, get a library and API service around it17:13
hartsocksnice.17:14
*** rakhmerov has quit IRC17:14
*** jungleboyj has left #openstack-meeting17:15
ogelbukhand as I understand you want some call that will tell if the configuration is valid17:15
*** zehicle_at_dell has quit IRC17:15
ogelbukhas a hook in startup script17:15
ogelbukhcorrect?17:15
hartsocksbasically, I'm all about accomplishing more with less work. If something validates the config already, let's not do that again.17:15
ogelbukh(one option)17:15
ogelbukhok17:15
tjonesyes there were 2 issues - bad config and servce health17:15
*** zehicle_at_dell has joined #openstack-meeting17:16
hartsocksgood point. Service health is a separate but related thing.17:16
ogelbukhyep17:16
ogelbukhhartsocks: tjones: could you explain your vision of service health check?17:17
*** vito-ordaz has joined #openstack-meeting17:17
*** Guest68799 is now known as kin17:17
* hartsocks defers to tjones c17:17
ogelbukhjust check that vCenter API is responsive? or something else?17:17
tjonesperhaps we can meet separately on this once we have a chance to take a look ?  so for checking our connection to VC - we would check that we can talk to it, that the clusters defined are there, that there are hosts in the cluster (other stuff probably)17:18
rgerganovI think there is health service in vCenter17:18
ogelbukhsure17:18
tjonesthere is but this is more checking that the nova.conf info matches what is in VC17:19
ogelbukhthat deserves separate meeting17:19
*** vito-ordaz has quit IRC17:19
ogelbukhand probably more than one )17:19
tjonesogelbukh: yes i am sure more than 1 ;-)17:19
hartsocksokay.17:19
*** vito-ordaz has joined #openstack-meeting17:19
hartsocksWe'll watch that one with interest.17:19
ogelbukhhartsocks: does it worth an action item?17:20
hartsocks#action tjones, hartsocks to follow up with ogelbukh on project Rubick17:20
ogelbukhexcellent!17:20
ogelbukhthanks17:21
tjonesogelbukh: what timezone are you in?17:21
ogelbukhGMT+417:21
tjonesok will schedule appropriately17:21
ogelbukhthx17:22
*** rakhmerov has joined #openstack-meeting17:22
hartsocksAny other interesting/new things to come out of Hong Kong's design summit folks want to talk about?17:22
hartsocksI heard live-snapshots were nixed. I was looking forward to writing that one.17:23
*** vito-ordaz has quit IRC17:23
tjonesi've got a link somewhere with notes…  looking17:24
tjoneshere we go - https://etherpad.openstack.org/p/IcehouseNovaSummit17:24
dimshartsocks, they said NO to discovery of existing vm(s)17:25
*** sushils has quit IRC17:25
*** vuil has joined #openstack-meeting17:25
tjonesdims: they said NO many many times :-D17:25
*** bdpayne has joined #openstack-meeting17:25
hartsocks*lol*17:25
dims:)17:25
dansmithNO17:26
dansmithoh, sorry, it's a reflex17:26
*** jmontemayor has quit IRC17:26
hartsocks*lol*17:26
tjonessee - he did it again ;-)17:26
dimsi have a TODO to write a blueprint for passing hints to select specific datastore / compute based on tags or something else17:27
dimsdansmith, LOL17:27
hartsocksdims: oh! wait...17:27
hartsocks#link https://blueprints.launchpad.net/nova/+spec/vmware-datastore-selection-by-scheduler-filter17:27
hartsocksI wrote this BP up a while ago, 'cuz the way we're doing datastore now is kind of forced by not getting any hints down from the scheduler.17:28
dimsanother feedback was to find a better abstraction other than the virt driver (may be something similar to cells) over time17:28
dansmith+102417:28
dimshartsocks, right, if we can get scheduler to help select something, then the driver would honor that17:28
*** nermina has quit IRC17:29
hartsocksdims: yeah, our current driver design is just the way it is because the scheduler doesn't know about the datastores.17:29
hartsocksdims: however, I don't know much about cells.17:30
hartsocksdims: is that a distributed scheduler design?17:30
*** ben_duyujie has quit IRC17:30
*** ygbo has quit IRC17:31
*** matel has quit IRC17:31
dansmithhartsocks: cells breaks nova up into .. cells17:31
dansmithhartsocks: but specifically, it breaks it up into chunks of things that have their own scheduler inside them, and a group of compute hosts17:31
*** shakayumi has quit IRC17:31
dansmithso something gets scheduled quickly to a cell, and then again within the cell17:32
dimshartsocks, a nova cell would be one implementation is what i heard being said - https://wiki.openstack.org/wiki/Blueprint-nova-compute-cells...someone has to come up with API's so a nova cell or a vsphere impl would be 2 implementations of something higher than a virt driver17:32
dansmiththe way you guys are treating a whole vsphere cluster as a single compute host through the virt driver API is something we want to do away with at some point, and exposing yourself as a cell may be the way to do that17:32
dansmithyou're not the only offender, just the most icky one :)17:32
* hartsocks bows17:33
dimshartsocks, there was general admiration for the minesweeper work. so kudos.17:33
dansmithand I meant "vmware" not "hartsocks" as the target of my "you're" of course17:33
hartsocksIn our defense, we kind of inherited what's there now and had to make it "work" :-)17:33
*** reed has joined #openstack-meeting17:34
hartsocks:-)17:34
dansmithhartsocks: not only that, but there is no higher abstraction in which to plug yourselves in, so it couldn't be any different right now anyway17:34
dimsright17:34
tjonesdansmith: isn't VC like a cell then?17:35
*** vito-ordaz has joined #openstack-meeting17:35
dansmithtjones: I don't actually know the details of VC, VS, etc17:35
hartsocksJust for group knowledge...17:35
dansmithtjones: but anything that hides >1 compute node behind a single virt driver in nova is what we're trying to avoid17:35
ogelbukhconcepts look very similar to me17:35
hartsocksvCenter is a server that binds multiple ESXi together.17:35
*** jsavak has joined #openstack-meeting17:36
dansmithi.e. anything that ends up scheduling underneath nova17:36
ogelbukhthough I'm not an expert in vmware nor in cells17:36
hartsocksthe hypervisor + API are in aggregate called vSphere.17:36
*** beyounn has joined #openstack-meeting17:36
dansmithhartsocks: meaning vcenter is a thing, and vcenter+esx == vsphere ?17:36
hartsocksyeah17:36
hartsocksmore or less.17:36
dansmithokie17:36
hartsocksThe bare hypervisor has API17:37
*** Linz has joined #openstack-meeting17:37
ogelbukhthe main difference between cell and vsphere+vcenter is that cells communicate via rpc17:37
dimshartsocks, problem is right now we implement driver.ComputeDriver - someone needs to define driver.CellDriver and Nova Cell and VC and ovirt would be implementations17:37
hartsocksThe vCenter has API17:37
dansmithso yeah, if the nova driver is managing an ESX, then that's fine. if it's managing a vcenter then it's bad17:37
hartsocksBTW … together all the API are vSphere17:37
ogelbukhwhich would not be a case with VC to my knowledge17:37
*** Linz has quit IRC17:38
*** DrBacchus has joined #openstack-meeting17:38
*** Linz has joined #openstack-meeting17:38
hartsocksvCenter can do some things that are scheduler level… but… I think there are some things it doesn't do.17:38
*** markwash has quit IRC17:39
hartsocksThe API are easier to work with through vCenter… so what I would hope is ...17:39
* hartsocks digs out blueprint17:39
*** DrBacchus has quit IRC17:39
*** joesavak has quit IRC17:39
hartsocks#link https://blueprints.launchpad.net/nova/+spec/vmware-auto-inventory17:39
*** DrBacchus has joined #openstack-meeting17:39
hartsocks… this would be having vCenter just act as an API proxy to the driver.17:40
ogelbukhso some driver will be required in cells17:40
ogelbukhto plug in vc api to replace an rpc17:40
ogelbukhright?17:40
dansmithhartsocks: is vcenter a horizontally scalable service?17:40
hartsocksnot really.17:40
*** luis__ has joined #openstack-meeting17:40
hartsocksit's a kind of management API server.17:41
dansmithhartsocks: then it's pretty uncloudy to use it for more than one compute node, right?17:41
dansmithI don't mean to take up your meeting time with this, it just snowballed17:41
hartsocksheh. I'm kind of bad for letting things go into the weeds.17:41
hartsocksJust to cap this off tho'17:42
tjonesyou can link multiple VC to scale out17:42
*** saurabh__ has left #openstack-meeting17:42
tjoneswow - sorry for the bold - dunno how that happened17:42
hartsockstjones: I don't see bold17:42
tjonesok good - i do17:42
tjoneslooks like shouting17:42
hartsocks*lol*17:42
hartsocksLong and short… I don't think the metaphors match up cleanly so I think we need some creative lee-way...17:43
tjoneshartsocks: i think we need to look into cells and see how this maps out17:44
dansmithagain, cells is not really suitable for this right now,17:44
hartsocksdansmith: is that something we should invest in helping with?17:44
dansmithwe're just saying you seem a lot more like a cell than a virt driver, but I'm happy to have a discussion about the real architecture of vmware stuff so we know what we're talking about17:44
dansmithhartsocks: yes, definitely17:45
hartsockscool.17:45
hartsocks#action vmwareapi team to spend some time with cells17:45
dansmithbut lets have a discussion about what vmware really looks like under the covers sometime before we get too far towards anything17:45
hartsocks#undo17:45
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x3652350>17:45
hartsocksokay how about this...17:45
*** vahidh has joined #openstack-meeting17:46
*** hemna has joined #openstack-meeting17:46
hartsocks#action vmwareapi team to discuss driver and cells with core team17:46
dansmithsure17:46
*** twoputt has joined #openstack-meeting17:47
*** twoputt_ has joined #openstack-meeting17:47
*** vito-ordaz has quit IRC17:47
hartsocks#topic open-discussion17:47
*** openstack changes topic to "open-discussion (Meeting topic: VMwareAPI)"17:47
hartsocksnot that we weren't kind of there already.17:47
hartsocks:-)17:47
tjones:-D17:48
*** vito-ordaz has joined #openstack-meeting17:48
ogelbukh)17:48
*** funzo has quit IRC17:49
hartsocksIf you have a "my pants are on fire" bug… nows the time to mention it :-)17:49
rgerganovis it ok to work on this bug: https://bugs.launchpad.net/nova/+bug/121620917:50
rgerganovor this is in conflict with the scheduler story17:50
rgerganovfrom the blueprint?17:50
*** ndipanov has quit IRC17:51
*** ivar-lazzaro has joined #openstack-meeting17:51
*** galstrom is now known as galstrom_zzz17:51
*** blamar has joined #openstack-meeting17:51
hartsocksrgerganov: IMHO we have to make what's there work reasonably, many of these things will take significant time to iron out… so… especially if it's back-port potential we should still fix it.17:51
*** denis_makogon has joined #openstack-meeting17:51
*** nermina has joined #openstack-meeting17:52
*** vito-ordaz has quit IRC17:52
tjonesvuil: are you working on that one?17:52
tjonesit's assigned to you17:52
hartsocksI'm going to target that one to icehouse-1 … that seems like a significant thing to get working.17:53
rgerganovok17:54
hartsocksrgerganov: thanks for highlighting it.17:54
rgerganovvuil: please tell if you don't mind to help on this17:54
rgerganovsure17:54
*** doron_afk has quit IRC17:54
hartsocks#action followup on +bug/121620917:55
tjonesim looking for him in the other room but he's not around.17:55
hartsocksyeah, we'll have to follow up later. I figured the DST change would mess up some people17:55
hartsocksAnything else folks need to talk about?17:57
*** macjack_ has joined #openstack-meeting17:57
hartsocksOkay.17:58
*** DrBacchus is now known as rcb_lunch17:58
hartsocksWe're over in #openstack-vmware if you want to chat.17:59
hartsocks#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Wed Nov 13 17:59:31 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
tjonesvuil is there too17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-11-13-17.03.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-11-13-17.03.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-11-13-17.03.log.html17:59
*** vito-ordaz has joined #openstack-meeting17:59
*** derekh has quit IRC18:00
*** edleafe has quit IRC18:00
*** gatuus has joined #openstack-meeting18:00
*** rongze has quit IRC18:00
*** edleafe has joined #openstack-meeting18:00
*** macjack has quit IRC18:01
*** rongze has joined #openstack-meeting18:01
*** luis__ has quit IRC18:02
*** vito-ordaz has quit IRC18:02
*** rongze has quit IRC18:05
*** jdurgin1 has joined #openstack-meeting18:06
*** MarkAtwood has quit IRC18:07
*** hartsocks has left #openstack-meeting18:07
*** macjack_ has quit IRC18:09
*** macjack__ has joined #openstack-meeting18:09
*** vito-ordaz has joined #openstack-meeting18:13
*** vito-ordaz has quit IRC18:16
*** mrunge has quit IRC18:17
*** vito-ordaz has joined #openstack-meeting18:17
*** markwash has joined #openstack-meeting18:17
*** jorisroovers has joined #openstack-meeting18:19
*** comay has joined #openstack-meeting18:19
*** jroovers has joined #openstack-meeting18:19
*** armax has joined #openstack-meeting18:20
*** dolphm has quit IRC18:20
*** vito-ordaz has quit IRC18:21
*** jsavak has quit IRC18:22
*** jorisroovers has quit IRC18:23
*** garyk has joined #openstack-meeting18:30
*** rcb_lunch is now known as rbowen18:32
*** johnthetubaguy has quit IRC18:39
*** krtaylor has quit IRC18:43
*** tjones has left #openstack-meeting18:44
*** vito-ordaz has joined #openstack-meeting18:46
*** martines has quit IRC18:46
*** martines has joined #openstack-meeting18:46
*** galstrom_zzz is now known as galstrom18:48
*** rbowen has quit IRC18:49
*** zaitcev has joined #openstack-meeting18:51
*** vito-ordaz has quit IRC18:51
*** vito-ordaz has joined #openstack-meeting18:52
*** esker has joined #openstack-meeting18:52
*** zehicle_at_dell has quit IRC18:53
*** markpeek has joined #openstack-meeting18:55
*** jlucci1 has joined #openstack-meeting18:56
*** Mandell has joined #openstack-meeting18:56
*** lincolnt has joined #openstack-meeting18:56
*** vito-ordaz has quit IRC18:56
*** glange has joined #openstack-meeting18:59
*** jlucci has quit IRC19:00
*** portante has joined #openstack-meeting19:00
notmynameswift meeting time https://wiki.openstack.org/wiki/Meetings/Swift19:01
*** gholt has joined #openstack-meeting19:01
*** jmontemayor has joined #openstack-meeting19:01
*** clayg has joined #openstack-meeting19:01
notmyname#startmeeting swift19:01
openstackMeeting started Wed Nov 13 19:01:35 2013 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: swift)"19:01
openstackThe meeting name has been set to 'swift'19:01
*** peluse has joined #openstack-meeting19:01
notmynamethanks for joining. today's agenda is at https://wiki.openstack.org/wiki/Meetings/Swift19:01
notmynamewho's here19:01
notmyname?19:01
pelusehere19:01
zaitcevo/19:02
portanteo/19:02
torgomatico/19:02
briancline+119:02
koolhead17o/19:02
* clayg lurks19:02
notmynamegreat19:02
lincolnto/19:02
notmynameso first item of business it to figure out the proper way to wrap uuid4(). because reasons19:02
notmyname;-)19:02
notmyname(not really)19:02
*** IlyaE has quit IRC19:03
zaitcevI am confused. How hard can it be?19:03
notmyname#topic HK summit recap19:03
*** openstack changes topic to "HK summit recap (Meeting topic: swift)"19:03
brianclinewe'll need a plugin manager19:03
notmynamethe hong kong summit was great19:03
*** dolphm has joined #openstack-meeting19:03
peluseagreed!19:03
notmynameswift keynote on the first day. kinetic drives. just about every conversation involved storage policies. tons of interest from IBM, HP, and others19:03
notmynamethanks peluse for doing the multi-ring demo19:04
pelusemy pleasure!  I'm just glad it worked :)19:04
notmynameheh19:04
*** macjack__ has quit IRC19:04
notmynameoverall, I was very happy with the summit. part of that, I think, was because we had the hackathon 2 weeks prior19:04
*** joesavak has joined #openstack-meeting19:04
notmynameany other questions or comments about the summit?19:05
peluseI miseed the mercado libre talk but saw it was posted on IRC - good to watch if anyone missed it19:05
notmynameI think koolhead17 has a blog post about it (from a swiftstack perspective) that will go up soon. If needed, I can fill in any other gaps from a general swift perspective19:05
zaitcevcreiht's RAX preso was V.interesting, although he didn't divulge the number of objects19:05
notmynameoh yeah. mercado libre loves swift19:05
notmynameya, RAX talked about 85 PB across their swift clusters (raw)19:06
notmyname20 PB deployed in france by enovance for cloudwatt19:06
*** gatuus has quit IRC19:06
koolhead17Swift ^^19:06
notmynameglobal clusters from concur19:06
creihtzaitcev: :)19:06
*** zehicle_at_dell has joined #openstack-meeting19:06
*** tmeshorer has joined #openstack-meeting19:06
notmynamezaitcev: billions and billions?19:06
*** vito-ordaz has joined #openstack-meeting19:07
claygI think the most interesting part was creiht's sports coat - very snazzy19:07
*** zehicle_at_dell has quit IRC19:07
creihthaha19:07
notmynameprobably part of his new secret job as a spy19:07
*** dvarga has quit IRC19:07
*** macjack has joined #openstack-meeting19:07
pelusedon't sell yourself short clayg - the daemon factory stuff eas very cool19:07
*** zehicle_at_dell has joined #openstack-meeting19:08
claygyeah i suppose I need to finish that up and get up a patch19:08
zaitcevI understand the danger of racing Azure and S3 but I was thinking about how much our containers can take... S3 has some nifty auto-sharding thing, and I am curious if we're at the point where we need it or not.19:08
notmynamethe profiling middleware stuff was very cool. along with clayg's "pluggable" things19:08
claygwhoa!19:08
portantewere the unconference sessions recorded as well?19:08
notmynamezaitcev: we've "always" needed it. and we've always said "just use ssds"19:08
notmynameportante: not AFAIK19:08
notmynameportante: not any tech sessions, actually19:09
portanteoh19:09
portantewould be interested in blog posts on those sessions19:09
notmynamethere was also a really interesting tech session where a potential user went down a list of questions, essentially evaluating swift as the storage engine for a massive global messaging app19:09
portanteclayg: was your "pluggable" things recorded?19:09
*** matrohon has quit IRC19:09
brianclineme as well, I was pulled between the general and design stuff far too much19:09
notmynameI want to try to have that in atlanta again in may19:09
torgomaticatlanta?19:10
notmynamealso, next summit is in atlanta in may19:10
portanteor in the atlantic?19:10
notmynamethen paris in november19:10
pelusehave what in atlanta?19:10
glangethe paris summit is going to be so romantic19:10
notmynamepeluse: a tech session similar to the one LINE did this time where they are asking real-world use case questions about swift19:10
*** dfg has joined #openstack-meeting19:11
peluseahh, gotcha19:11
notmynameglange: nothing like eating snails under the eiffel tower19:11
*** vito-ordaz has quit IRC19:11
notmynameanything else on HK or the summit?19:11
*** sudorandom has joined #openstack-meeting19:11
*** markpeek1 has joined #openstack-meeting19:12
peluseany next steps on the profiling middleware?19:12
notmynamethanks to everyone who participated there19:12
notmynamepeluse: I think it's up for review19:12
portanteany design decisions made?19:12
peluseI think KT was asking for core comm to pick it up right?19:12
notmynameportante: like normal, not really19:12
portantewas it really a design summit for tings?19:12
portantek19:12
notmynameportante: never really has been for swift19:12
*** SergeyLukjanov has joined #openstack-meeting19:12
*** markpeek has quit IRC19:12
*** markpeek2 has joined #openstack-meeting19:12
notmynameportante: that stuff normally happens in irc and in the day-to-day (and now maybe at hackathons)19:12
*** tomerm has joined #openstack-meeting19:13
portantebut nobody else in openstack made sweeping design decisions that affect swift either?19:13
*** dvarga has joined #openstack-meeting19:13
*** tmeshorer has quit IRC19:13
notmynameportante: not that I know of. I'm sure they'll let us know ;-)19:13
torgomaticwell, we are going to be switching to Trove-provisioning for our Mongo databases, which are replacing sqlite19:13
portante:)19:13
torgomaticalso, rabbitmq EVERYWHERE19:13
portantetorgomatic: I hope you are joiking19:13
notmynametorgomatic: before or after using a pluggable library to replace uuid4()?19:13
portantejoking19:13
notmynameok, let's move on :-)19:14
notmyname#topic swift-bench separation19:14
*** openstack changes topic to "swift-bench separation (Meeting topic: swift)"19:14
notmynamethis needs to happen. it's half-done now, which is really the worse place to be19:14
notmynameand volunteers to lead the -ectomy in swift and cleaning up the swift-bench repo?19:15
*** epim has joined #openstack-meeting19:15
*** bauzas has joined #openstack-meeting19:15
notmyname*crickets*19:15
*** CrackerJackMack has joined #openstack-meeting19:15
*** markpeek has joined #openstack-meeting19:15
* portante whistles quietly to himself19:16
*** markpeek2 has quit IRC19:16
* torgomatic takes one giant step backward19:16
zaitcevI thought Sam knew what he was doing there19:16
*** markpeek1 has quit IRC19:16
*** markpeek1 has joined #openstack-meeting19:16
torgomaticI know what needs to happen, but I'm doing other stuff at the moment19:16
notmynameas is everyone else it seems ;-)19:16
claygit's just so easy to not care about patches that want to add dependencies to swiftclient for "reasons" and admit that having bench in repo is sorta handy in a super lazy sort of way.19:16
notmynameclayg: heh, ya19:17
notmynameok, I want to keep it in everyone's mind. still an outstanting TODO19:17
claygBEFORE ICEHOUSE!19:17
* clayg feels a mantra coming on19:17
notmynameI can keep bugging people in day-to-day IRC19:17
notmyname#topic test coverage19:18
*** openstack changes topic to "test coverage (Meeting topic: swift)"19:18
claygyou should tag it to a milestone19:18
*** davidhadas has joined #openstack-meeting19:18
notmynameclayg: ooohh. that's a good way to get it done ;-)19:18
zaitcevI am having a vague feeling that Fedora packaging may win if we separate... I did stuff like that before but I need to see the benefit.19:18
portantehow 'bout create a test that fails until it is done?19:18
notmynamein my catching up after the summit, there were some concerns raised about patches landing that lowered test coverage19:18
claygout coverage went down?19:19
notmynamemostly this is a reminder to make sure that test coverage is checked when doing reviews19:19
notmynamenew patches should have tests for the lines of code they change19:19
*** markpeek2 has joined #openstack-meeting19:20
notmynamebut we don't have a formal gate on that, so it's easy to miss it from time to time19:20
*** markpeek1 has quit IRC19:20
*** markpeek1 has joined #openstack-meeting19:20
claygmoar gates!  moar gates!  moar gates!19:20
*** markpeek has quit IRC19:20
notmynameanyone want to add anything specifically here, or can we leave it at that?19:20
zaitcevI don't see a lot of low-hanging fruit...19:20
zaitcevContainer updater pehrpas19:20
portantenotmyname: I believe there is a POST commit job that runs the coverage, but is not used19:20
claygI'm getting like total 91% on my machine, i thought stuff had been coming up cause people have been adding tests for all that crap we never tested19:21
zaitcevI once was dinged for lowering coverage... That was awful.19:21
* clayg glares at db_replicator19:21
notmynameya, and I'm looking forward to the discoverable constraints thingy landing so that we can add similar coverage to functional tests19:21
notmynamejust saw this in -infra: "turns out swift wasn't designed to run in a single VM "  yay!19:21
claygREWRITE!19:22
zaitcevWhat do you mean wasn't designed? What about SAIO?19:22
*** Mandell has quit IRC19:22
notmynamezaitcev: as in devstack. one replica on one loopback device with one process in one vm19:22
notmyname#topic metadata search API19:22
*** openstack changes topic to "metadata search API (Meeting topic: swift)"19:23
notmynameHP presented on adding a metadata search API into swift19:23
notmynameand softlayer has had something like that for a while19:23
lincolntHi there, I presented.19:23
notmynamelincolnt: you led the talk in HK. take it away19:23
*** vito-ordaz has joined #openstack-meeting19:23
lincolntSee https://wiki.openstack.org/wiki/MetadataSearch19:24
lincolntThe design session went well, thanks everyone for the great feedback!19:24
*** nermina has quit IRC19:24
lincolntBrian Cline (SoftLayer) and I have updated the blueprint and started that Wiki page19:24
*** diogogmt has joined #openstack-meeting19:24
lincolntI posted our strawman API spec we wrote at HP19:24
lincolntAnd the design session slides19:24
*** markpeek2 has quit IRC19:25
portantecan you provide a sample use case?19:25
lincolntWe're developing against that spec for proof-of-concept19:25
claygportante: you have metadata - you want to search it19:25
lincolnttreating Swift as a black box, but we (all) want it to be a new standard API and ref impl for Swift.19:25
portantejust searching x-*-meta-* keys?19:25
notmynameportante: my understanding is that softlayer (IBM) has it, HP wants it, and they don't want there to be 50 different APIs to do it19:26
lincolntportante: "Show me all objects in all containers where the object count > 10 and the last modified time is in the last 30 days and > 1 GB"19:26
claygportante: probably more like content-type and size and last modified and stuff19:26
claygoh heh19:26
* clayg backs away19:26
creihtsearching user meta data would be nice19:26
lincolnt...and BTW where the container-meta-location = "New Zealand" and object-meta-physician = "Smith"19:26
*** nermina has joined #openstack-meeting19:27
tomermthe api support searching both system AND user metadata19:27
brianclineprecisely, we'd like to adopt whatever becomes the standard19:27
lincolntYes, searching system and custom metadata are both spec'd in the API19:27
portanteso we'll need to formally define the system metadata, unless we already do that today?19:27
lincolntThe proposed API is broader and (we hope) more flexible/featureful/extensible than SoftLayer's but they have theirs established so they will be critical to the new API's success19:28
notmynamelincolnt: so what's the next step?19:28
claygi'm keen on doing interesting indexing tricks with container db's, i don't really want "cluster search" and I'm less concerened about the api as long as it's usable.19:28
zaitcevI am wondering if it's a great way to bring the system to its knees by launching queries that chew up CPU19:28
lincolntAsking everyone to review the Wiki, API, slides, and the blueprint pages there...19:28
lincolntGive us your experiences / needs / wishlists for what you'd like to search in Swift metadata...19:28
lincolntPoke holes in the API...19:28
notmynamelincolnt: how do you want feedback?19:28
lincolntSuggest implementations e.g. metadata index stores to use.19:29
notmynamedoes this need to be on the openstack-dev mailing list? do we do it on the wiki? in IRC? what's best for you?19:29
lincolntHow would be best for the community? Add to the Wiki (I'd like, collects in one place)?19:29
*** jlucci1 has quit IRC19:29
brianclinepreferably mailing list for discussion, with the wiki for the evolving idea on what it should look like19:29
notmynamethe mailing list is best for async discussion19:29
*** markpeek has joined #openstack-meeting19:29
notmynameya, what briancline said19:29
lincolntWe (briancline and I) will be sending a openstack-dev email after this, asking for the same inputs19:29
*** markpeek1 has quit IRC19:30
notmynamethe risk is too much "wrap uuid4()" style comments19:30
notmynamelincolnt: great19:30
*** markpeek1 has joined #openstack-meeting19:30
lincolntCool, we can own the Wiki and update it based on email list feedback19:30
*** danwent has joined #openstack-meeting19:30
notmynamesounds good. thanks19:30
notmynameanything else on that topic for this meeting?19:31
brianclinezaitcev: that'll depend largely on what sort of indexing backend one uses, but for as long as we've had it out there I don't think we've had any issues like that19:31
lincolntzaitcev: Yes, good point, query optimizaton will be crucial19:31
*** otherwiseguy has quit IRC19:31
lincolntAnd swift (ha) responses and ingests into the tables19:31
*** sarob has joined #openstack-meeting19:31
gholtnotmyname: We're starting to test ssync in staging now. Hopefully in prod in 2-3 weeks.19:31
lincolntAlso let me introduce tomerm, our primary developer of HP's PoC19:31
notmynamegholt: cool. I saw that you had packaged it19:31
tomermhi19:31
notmynametomerm: hi. welcome19:31
*** sarob has quit IRC19:31
*** markpeek2 has joined #openstack-meeting19:31
lincolntYou can ping either of us, or briancline, on IRC19:32
*** markpeek1 has quit IRC19:32
gholtnotmyname: Oh sorry, I read your question as "anything else" without the "on that topic" ah well ;)19:32
dfgcan I suggest that we fix the whole POST as copy thing if we're going to add metadata searching?19:32
notmynamegholt: :-)19:32
*** markpeek1 has joined #openstack-meeting19:32
*** sarob has joined #openstack-meeting19:32
gholtdfg: How's it broke again?19:32
notmynamedfg: ya, that's a good idea19:32
notmynamegholt: make POSTs update containers so you get fast posts19:32
dfgits not broken- but make it faster for large objects.19:33
dfgif we're going to be searching on metadata being able to do POSTs without COPYing the whole object seems like it'll come in handy19:33
dfgbut maybe not19:33
gholtGotcha, tbh I can't remember why we have the two POST processes anymore. Lol19:34
torgomaticsomething something container sync something something?19:34
lincolntdfg: Please reply to the upcoming openstack-dev email we send on this topic, I think I know what youre talking about, good idea.19:34
claygi mostly remember blaming container sync19:34
dfgi don't think there is a good reason- just time to fix19:34
*** markpeek has quit IRC19:34
notmynameit's an optimization, but I can see how POST would be more popular if metadata searches are available19:34
claygbut I agree the real issue was content-type and container updates19:34
brianclinequick side note, on the SoftLayer side, sudorandom and CrackerJackMack are also extremely familiar with our implementation if questions come up, however their availability may vary for this topic19:34
notmynamekk19:34
claygnotmyname: with the x-delete-at stuff it's already sorta getting in style to run fast-post19:34
dfgi might have gotten unsubscribed from openstack-dev...19:35
notmynamedfg: filtering to /dev/null doesn't count as unsubscribe19:35
CrackerJackMackI'm quasi available via IRC19:35
peluseis there already a bp to address POST w/o copy?19:35
gholtYeah, every once in a while I think Rackspace marks it as spam and bounces everything and you have to resub19:35
clayggholt: sounds like a feature19:36
notmynamegholt: and I'm not sure that's always a wrong choice ;-)19:36
*** markpeek2 has quit IRC19:36
notmynameok, moving on from metadata search19:37
notmynamethanks lincolnt19:37
notmyname#topic timestamps + modified-since headers19:37
*** openstack changes topic to "timestamps + modified-since headers (Meeting topic: swift)"19:37
notmynameportante: you're up19:37
portanteso are folks familiar with the problem?19:37
*** IlyaE has joined #openstack-meeting19:37
notmynamerfc calls for int timestamps?19:37
portantewe store timestamps using microsecond resolution19:37
portantethe http protocol only allows for seconds resolution in last-modified, if-[un]modified-since heasders19:38
portanteso if you HEAD an object after PUTing it19:38
portanteyou get a truncated timestamp: 13.9 ends up being 1319:39
portanteif you then use that last-modified value with if-unmodified-since, you get a 41219:39
portanteif you use that with if-modified-since you'll fetch the object, even though it has not changed19:39
*** markpeek has joined #openstack-meeting19:39
portanteI am not sure what to do about this personally19:39
notmynamelast-modified with "13" gives an error?19:40
*** markpeek1 has quit IRC19:40
*** markpeek1 has joined #openstack-meeting19:40
notmynameerr...if-unmodified-since19:40
torgomaticwell, if you only get second-level resolution with HTTP, we have to treat all same-second updates as identical19:40
*** bgorski has quit IRC19:40
torgomaticso, maybe round up to <second>.99999 ?19:40
notmynametorgomatic: or floor it19:40
notmynameportante: does the normalize timestamp method not account for this?19:41
portanteit does not have anything to do with this19:41
portantethe x-timestamp value comes from the object19:41
portantethe format of the last-modified and if-[un]modified-since headers is http-data format (verbose human readable time string)19:42
notmynamenormalize what comes in on the request. is the question to count it as .99999 or .0?19:42
brianclineflooring seems best19:42
portanteI think we have to ceiling x-timestmap value when returning last-modified, and then do the same when generating datetime objects when comparing the if-* headers19:43
lincolntCould we define a meta HTTP header to hold the microseconds so clients can provide it?19:43
portantelincolnt: that is an option, but clients would have to change19:43
gholtlincolnt: You could, but that doesn't help with all the existing http-based stuff out there.19:43
*** sarob has quit IRC19:44
portanteand we tried changing the http-data format to add the trailing microseconds and some proxies just strip it and reformat the date without it19:44
lincolntright, what youre saying about flooring etc would still have to happen, but allows clients to add it in the future19:44
*** markpeek has quit IRC19:44
*** sarob has joined #openstack-meeting19:44
brianclineif you're performing that in both places, why would it matter whether to floor or ceil it?19:45
zaitcevIf I understood right, the problem is 412. Just make sure it doesn't happen and return the object.19:45
portanteyes, if a request had an x-swift-if-[un]modified-since header, we could accept that full format19:45
notmynamewe return x-timestamp, so if you floor the last-modified value, you satisfy the rfc and give the user the chance to get more accurate19:45
portantewe don't return the x-timestamp value as is19:45
*** Mandell has joined #openstack-meeting19:45
portantethat header I don't think is allowed in responses by default, though I could be wrong19:46
*** markpeek has joined #openstack-meeting19:46
notmynamehmm19:46
portantethe last-modified header is represented by the last_modified property on a Response object, which is a _datetime_property() object19:46
*** markpeek2 has joined #openstack-meeting19:46
portantethat object converts to the string our x-timestamp float value, dropping the microseconds on the flow19:46
portantefloor19:47
notmynameok19:47
zaitcevDo "swift stat" and get X-Timestamp: 1368649471.4737919:47
zaitcevIt started happening a while ago. Before 1.419:48
portanteso we could change last-modified to ceiling and then change the if-[un]modified-since code to ceiling19:48
zaitcevAt the time I found it annoying that it leaked.19:48
torgomaticI mean, fundamentally the problem is: if an object has Last-Modified: Blah, and I make a GET with If-Unmodified-Since: Blah, I want a 304 Not Modified response. Right?19:48
torgomaticor am I misunderstanding things?19:48
portantebut then we have to document that there is a possibility of missing sub-second updates19:48
portanteyes19:48
portantetorgomatic19:48
*** spzala has joined #openstack-meeting19:48
*** sarob has quit IRC19:49
portantezaitcev: not sure we want to rely on that "leak"19:49
*** adalbas has quit IRC19:49
*** markpeek2 has quit IRC19:49
pelusenot I sure I follow the "leak" comment19:49
notmynameis -since inclusive or exclusive?19:49
*** markpeek1 has quit IRC19:50
portantepeluse: I believe zaitcev is saying that we did not return an x-timestamp header in responses before 1.419:50
peluseahh19:50
*** markpeek has quit IRC19:50
zaitcevyes19:50
gholtQuick test that shows the python libs floor: https://gist.github.com/gholt/6963bffe5a20cbded45119:50
*** ChristerThor has joined #openstack-meeting19:51
*** luis__ has joined #openstack-meeting19:52
notmynameportante: does that ^ give you anything?19:52
*** novas0x2a|laptop has joined #openstack-meeting19:52
*** hodos has quit IRC19:52
portantesec19:52
*** sushils has joined #openstack-meeting19:52
notmynameshould we punt this to #openstack-swift in the interest of time?19:53
portantesure19:53
notmyname#topic open discussion19:53
*** openstack changes topic to "open discussion (Meeting topic: swift)"19:53
*** andersonvom has joined #openstack-meeting19:53
notmynameanything else? if not, let's figure out the timestamp stuff19:53
portanteacoles 's work19:53
zaitcevI meant to ask gholt to look out for "DB locked" failrues _in servers servince requests_.19:53
notmynamegholt: RAX is now testing basically at master, including ssync and early quorum19:54
*** arbylee has joined #openstack-meeting19:54
*** epim has quit IRC19:54
zaitcevlike this https://bugs.launchpad.net/swift/+bug/122425319:54
zaitcevApparently it started happening in Havana. No clue why or if it really is the case19:54
portantenotmyname: there has been some discussion about pipelines and adding a manditory header stripper at the left of the pipeline19:54
*** keving1 has joined #openstack-meeting19:55
notmynameportante: ya. alpha_ori has a patch to do nifty things to the pipeline19:55
portanteyes, he does it only for config dir environments19:55
notmynameswifterdarrell skewered it, and alpha_ori will be back in the office late this week or next week19:55
*** DennyZhang has joined #openstack-meeting19:55
*** funzo has joined #openstack-meeting19:55
zaitcevI see "DB locked" in auditors often but whatever, that may be ok unless it prevents repair.19:55
portanteso I am looking at how to do that in general19:55
notmynameportante: use config dirs! ;-)19:55
notmynameacoles: did you have something?19:56
portantenotmyname: sure!19:56
*** sushils has quit IRC19:57
notmynameok, I don't think acoles is here19:58
notmynamethanks everyone for attending19:58
notmynamesee you in two weeks19:58
portantethanks19:58
notmyname#endmeeting19:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:58
openstackMeeting ended Wed Nov 13 19:58:43 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-11-13-19.01.html19:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-11-13-19.01.txt19:58
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-11-13-19.01.log.html19:58
gholtThe only dblocks I recall seeing here are because a user is doing really fast puts, sometimes to the same durn object. Eventually it clears.19:58
*** peluse has left #openstack-meeting19:58
*** sandywalsh has quit IRC19:59
notmynamegholt: zaitcev: that's what async pendings are for, right?19:59
*** sushils has joined #openstack-meeting19:59
*** jsavak has joined #openstack-meeting19:59
gholtYeppers19:59
*** randallburt has joined #openstack-meeting19:59
portanteover to #openstack-swift perhaps?19:59
*** tims has joined #openstack-meeting19:59
zaitcevokay. So without knowing who's holding hte lock we can't tell.19:59
*** dfg has left #openstack-meeting20:00
*** andrew_plunk has joined #openstack-meeting20:00
stevebaker#startmeeting heat20:00
openstackMeeting started Wed Nov 13 20:00:28 2013 UTC and is due to finish in 60 minutes.  The chair is stevebaker. 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: heat)"20:00
*** skraynev_ has joined #openstack-meeting20:00
openstackThe meeting name has been set to 'heat'20:00
stevebaker#topic rollcall20:00
*** mspreitz has joined #openstack-meeting20:00
*** openstack changes topic to "rollcall (Meeting topic: heat)"20:00
randallburthola20:00
andrew_plunkheeey20:00
stevebakerbooyaa20:00
mspreitzhere20:00
jpeelerhi20:00
*** gholt has left #openstack-meeting20:01
*** vito-ord_ has joined #openstack-meeting20:01
*** CrackerJackMack has left #openstack-meeting20:01
timso/20:01
asalkeldo/20:01
*** shardy has joined #openstack-meeting20:01
*** tomerm has left #openstack-meeting20:01
sdakeo/20:01
spzalaHi20:01
skraynev_o/20:01
andersonvomo/20:01
shardyo/20:01
zanebevening20:01
*** adrian_otto has joined #openstack-meeting20:01
arbyleehello20:01
adrian_ottohi20:01
stevebakerhope you've all recovered20:02
stevebakerno actions last meeting, so20:02
zanebnot even close20:02
*** jcru has joined #openstack-meeting20:02
*** tspatzier_ has joined #openstack-meeting20:02
randallburtmostly. more lagged coming back than I was going over.20:02
tspatzier_hi20:02
*** clayg has left #openstack-meeting20:02
stevebaker#topic Adding items to the agenda20:02
*** openstack changes topic to "Adding items to the agenda (Meeting topic: heat)"20:02
*** joesavak has quit IRC20:02
stevebakerAnything to add, so it doesn't get lost in the rolling-scrum of Open Discussion?20:02
stevebaker#link https://wiki.openstack.org/wiki/Meetings/HeatAgenda20:03
*** kwhitney has joined #openstack-meeting20:03
adrian_ottodo you want to do any ODS retrospective?20:03
*** epim has joined #openstack-meeting20:03
stevebakerpost it here and I will add it20:03
shardyadrian_otto: I put an item on the agenda for that20:03
stevebakeradrian_otto: we have Summit review, BPs/actions and prioritization20:03
randallburtadrian_otto:  I think that's already on the agenda20:03
shardySummit review, BPs/actions and prioritization20:03
*** ArxCruz has quit IRC20:03
adrian_ottoI see, tx.20:04
asalkelddo we want to talk about mistral?20:04
sdakeChange scope of Orchestration program to "OpenStack Control Program"20:04
stevebakersure20:04
*** vito-ordaz has quit IRC20:04
sdakecan probably cover that there20:04
randallburtis there much to talk about at this point? I thought its mostly design/planning stages20:04
stevebaker#topic Icehouse API policy (keep adding stuff, or freeze v1 + version bump for new stuff?)20:04
*** openstack changes topic to "Icehouse API policy (keep adding stuff, or freeze v1 + version bump for new stuff?) (Meeting topic: heat)"20:04
shardySo I added this20:05
*** vito-ord_ has quit IRC20:05
sdakei'm not a big fan of rolling new features into an existing api20:05
shardyWanted to discuss our policy on API additions, and also the possiblity of a new version without the tenant in the path20:05
sdakeso i'd suggest freeze20:05
*** ChristerThor has quit IRC20:06
shardysdake: I'm tending to agree with you, but we're already seeing patches adding stuff to the existing API20:06
asalkeldwhat's wrong with new features in a version?20:06
randallburt+1 for revving the api to remove the tenant so we can have sane management -type calls in Icehouse20:06
stevebakercurrently we're not planning on any breaking changes, just additions. This suggests v1_120:06
shardyso we need core to agree the review policy20:06
asalkeld-1 (until I get a reason)20:06
shardyrandallburt: That is where I'm headed :)20:06
zanebyeah, I think additions should go in v1_120:06
sdakewfm20:06
asalkeldobviously changing an api is really bad20:06
mspreitzwhat's wrong with additions in v1?20:06
asalkeldbut adding a standalone new thing?20:07
zaneb-0 on removing the tenant thing, I am unconvinced by the arguments in favor20:07
shardyzaneb: and the removing tenants should be a major bump or also in v1_1?20:07
stevebakerhowever, "Build information API endpoint" is something deployers might want to turn off, which implies we need extensions if we do that20:07
sdakemspreitz some people will end up with v1 without additions, some people will end up with v1 wit hadditions20:07
sdakehow are they to know which additions to use without versioning?20:07
randallburtthe current url scheme is sub-optimal for the managment/monitoring type stuff we want to pull from the api. that's by def a contract breaking change.20:07
mspreitzI thought the API already has a way to query for extensions20:07
zanebshardy: if we did it... dunno, in theory it's manageable by just changing the endpoint?20:07
asalkeldsdake not the job of the api for that20:07
shardyzaneb: How do you do a request which e.g lists multiple tenants stacks if the path impicitly scopes the request?20:07
andrew_plunknew endpoints could potentially break old endpoints, which is why a new version would be safer20:08
*** macjack has quit IRC20:08
zanebshardy: /global/stacks ?20:08
shardyzaneb: I'd like the request scope to be purely based on context, not path20:08
zanebwhy?20:08
shardyzaneb: Maybe that would work, seems less clean than GET /stacks20:08
zanebtrue20:09
shardyand the scope is decided by the roles in the request context20:09
shardyroles/projects/domains20:09
*** tspatzier_ is now known as tspatzier20:09
zanebactually, there's nothing stopping us from adding that alongside the tenant-scoped stuff, since it's just for the management api20:09
andersonvomthe tenant in the url shouldn't be trusted anyway, so it makes little sense to me that it is there in the first place20:09
randallburtandersonvom:  agreed20:09
shardyandersonvom: agree20:09
*** thelorax123 has joined #openstack-meeting20:09
sdakeagree20:10
zaneb"I'd like the request scope to be purely based on context, not path" <- this is the opposite of why HTTP was invented20:10
stevebakerGET /stacks?scope=global <- ?20:10
asalkeldthis needs to be inline with other openstack api20:10
randallburtperhaps we need to discuss this with nova et al?20:10
*** SergeyLukjanov has quit IRC20:10
*** devlaps has joined #openstack-meeting20:10
*** macjack has joined #openstack-meeting20:10
shardyzaneb: well we're implicitly tied to scoping the data we return based on the RBAC profile provided by keystone token validation20:10
shardyso why encode a subset of the stuff in the path?20:11
stevebakerthey have different paths for admin actions20:11
*** sandywalsh has joined #openstack-meeting20:11
shardyThe *heat specific* stuff should be encoded in the path IMHO20:11
*** keving1 has left #openstack-meeting20:11
randallburtstevebaker:  IIRC everyone wants to move away from that tho20:11
shardynot characteristics of the user making the request20:11
stevebakerso we're supposed to be talking about API versioning, not designing v2 ;)20:12
shardystevebaker: the keystone devs said "don't do that" re admin specific endpoints20:12
randallburtstevebaker:  fair point ;)20:12
shardyhas caused them pain apparently20:12
stevebakercan we get back on topic for a bit?20:12
shardystevebaker: sure, I'll follow up with ML/wiki discussion20:12
*** kgriffs is now known as kgriffs_afk20:12
stevebakerwe're going to have minor additions within the scope of a v1_1 *or* extensions20:13
asalkeldif every time we add a feature we put it in a new version, we'll have v100 soon20:13
randallburtstevebaker:  agreed, but I think it matters as to *why* we'd rev the api. is the question if we *should* in Icehouse?20:13
*** luis__ has quit IRC20:13
*** dvarga has quit IRC20:13
stevebakerasalkeld: we have v1_1 for the duration of icehouse20:13
*** dvarga has joined #openstack-meeting20:13
shardyIt could be argued that just adding stuff is OK20:13
asalkeldsince when is the version related to the cycle?20:13
*** zbitter has joined #openstack-meeting20:14
shardyand that a bump is only required when existing interfaces change20:14
randallburtI think just adding stuff doesn't require a contract revision, as long as all the old calls work20:14
asalkeldwe have continuous deployers20:14
stevebakershardy: how do API consumers know if the API they are calling has the feature they need?20:14
*** zaneb has quit IRC20:15
shardystevebaker: That is a good point, but it's not specific to Heat20:15
asalkeldstevebaker, you publish features/capabilties20:15
sdakethey know via the version #:)20:15
randallburtvia the version number.20:15
*** zaitcev has left #openstack-meeting20:15
stevebakerasalkeld: like an extensions introspection call?20:15
shardywell Neutron for example have been adding stuff throughout Havana, haven't they?20:15
asalkeldyeah, just not extensions20:15
randallburtadding stuff without breaking old stuff doesn't need a new version, though. extensions are different and should be versioned independently IMO.20:15
asalkeld+120:16
stevebakerasalkeld: why not extensions?20:16
*** DennyZhang has quit IRC20:16
asalkeldwell we are not talking about 3rd party extensions20:16
*** marun has quit IRC20:16
zbitterstevebaker: alternate answer: suck it and see20:16
*** zbitter is now known as zaneb20:16
asalkeldhow do users figure out the features20:16
randallburtstevebaker:  I think its a slippery slope of compatibility hell. We see it in nova/cloud servers.20:16
shardyzaneb: discovery via 404 ;)20:16
randallburtlol20:17
mspreitzWhat about changes in the HOT language?20:17
mspreitznot changes in the API signature20:17
asalkeldthat's template versioning20:17
randallburtmspreitz:  define "changes"20:17
stevebakermspreitz: different topic20:17
*** sandywalsh has quit IRC20:17
mspreitzOK20:17
shardymspreitz: that is a separate discussion, it's encoded in the template format20:17
mspreitzSo I'm looking forward to the answer to the question about why extensions are different20:18
stevebakerso could a v1.1 rev remain with a /v1/ path or would we have to make it /v1_1/?20:18
asalkeldstevebaker, not sure20:18
randallburtwe'd have to have a /v1.1/ path IMO20:18
shardystevebaker: surely the paths have to differ?20:19
zanebstevebaker: you're supposed to respond to both I believe20:19
asalkeldbut the version is discoverable (not sure why features can't be)20:19
zanebstevebaker: but luckily there's some middleware that handles it all for you20:19
zanebor something20:19
asalkeldseems like abusing the version IMO20:19
randallburtthe version middleware should sort it so that a call to the root of the service shows you what versions are available and what paths they have.20:19
*** nermina has quit IRC20:20
asalkeldso 20min in20:20
zanebyep20:20
shardyMaybe we should move this discussion to the ML and document a policy on API revisions for next week20:20
stevebakerindeed20:20
randallburtI believe the keystone catalog supports different versions as well20:20
randallburtagreed20:20
asalkeld+120:20
stevebakerI'll do this next, because it is related20:21
stevebaker#topic Build information API endpoint (https://review.openstack.org/#/c/55434/)20:21
*** openstack changes topic to "Build information API endpoint (https://review.openstack.org/#/c/55434/) (Meeting topic: heat)"20:21
shardySo I'm still not sure what actual value this provides20:21
*** danwent has quit IRC20:21
sdakeseems like questionable value with potential for abuse20:21
shardyother than providing a shortcut which avoids folks querying their CM tools managing Heat20:21
stevebakerI would find it useful, as long as the call was at least authenticated20:21
randallburteasily identify what version of heat is deployed even if you don't have access to the infra its running on20:21
*** kgriffs_afk is now known as kgriffs20:22
randallburtI believe the latest patch makes it optional as well as authenticated.20:22
shardyrandallburt: Why do you care, unless you're the deployer or an attacker?20:22
randallburtor someone submitting a bug report20:22
shardyIf you're the deployer, you have the info already, via some means20:22
sdakeya, the features are exported via the versioning of the api :)20:22
stevebakerI'd like template_guide to document what version resources and their properties were added (or deprecated)20:22
randallburtor a support technician20:22
randallburtthat doesn't have access to the infra20:23
sdakestevebaker: in that case, the template would fail to validate with an invalid prop20:23
sdakeor invalid versioning of the template20:23
randallburtstevebaker:  that's a different bp, though20:23
zanebyou know, apache used to report it's version number in error pages and stuff20:23
shardyrandallburt: I'm not saying don't provide the info, I'm saying, why does heat have to provide it?20:23
stevebakerthe published version should not be too fine-grained - and deployers would often carry their own patches too20:23
randallburtand a little off topic ;)20:23
zaneband now they don't do that because people use that info to hack it20:23
kebrayshardy customers care.20:23
kebraythey consume the API.20:23
stevebakerrandallburt: my point is that the version becomes an interesting piece of information that a user will want to know20:23
kebraySupport employees care, as we put out a new build, they would like to track that. they don't have access to the infrastructure, only the API.20:24
shardykebray: Ok, so what version do you report, if you have a deployement scaled out running multiple versions of things?20:24
sdakekeybray in this case, the version of the api changes20:24
*** edmund has joined #openstack-meeting20:24
randallburtstevebaker:  agreed. but that sort of supports having it. As a service provider, the information is useful20:24
*** nermina has joined #openstack-meeting20:24
randallburtshardy:  each version of the service would report independently20:25
arbyleesdake: the api doesn't necessarily change if you push out deploys with different configuration options20:25
stevebakershardy: the version should be from whatever engine responded to the version rpc call20:25
*** luis__ has joined #openstack-meeting20:25
*** danwent has joined #openstack-meeting20:25
kebrayshardy, that's the implementer to decide.  e.g. at Rackspace, we might manually bump a version number in a file.  Others may automate the version from a CI tool.  If we return it as a string, it can have whatever info we want.20:25
*** gatuus has joined #openstack-meeting20:25
andersonvomshardy: if you have multiple versions, that would be a useful case to actually find out that different info is being reported.20:25
*** krtaylor has joined #openstack-meeting20:25
sdakeperhaps a different approach is a config option, rather then the git sha20:25
*** dolphm has quit IRC20:25
sdaketo handle arblyee's case20:26
mspreitzOpenStack is not monolithic, so the version is not monolithic20:26
*** bgorski has joined #openstack-meeting20:26
*** dolphm has joined #openstack-meeting20:26
asalkeldI think it's ok if the deployer wants it20:26
randallburtsdake:  that would also be acceptable; that way the deployer can define what it meands20:26
kebraysdake agreed, I don't want a git sha.  This number needs to be understandable by humans, and for our setup, we may choose to have it be an incrementing number.20:26
sdakeok well that approach wfm :)20:26
randallburts/meads/means/20:26
zanebwhat mspreitz said. I don't see how this can be useful20:26
*** danwent has quit IRC20:26
*** sarob has joined #openstack-meeting20:26
stevebakerasalkeld: how do deployers turn it off if it is not an extension? maybe a config option.20:27
shardyandersonvom: but what version do you report, the API you hit, the engine which processes the request, both, versions of the platform it's all running on etc etc?20:27
asalkeldyeah, config option20:27
randallburtshardy:  yes. when would they be different?20:27
kebrayzaneb it's useful for us. I promise. API users need to know when our code has changed, even if nothing about the contract has changed.20:27
zanebkebray: if you as a cloud operator don't know what version of Heat you've rolled out, we really can't help you20:27
*** DandyPandy has quit IRC20:27
lifelesszaneb: wait, what?20:27
* sdake giggles at zaneb20:27
kebrayzaneb I know what version.. the other 4000 employees don't know. I want an API call that allows them to get it.20:27
*** shri has joined #openstack-meeting20:28
*** bauzas has quit IRC20:28
stevebakeralright, lets move this to the review/ml20:28
*** shri has left #openstack-meeting20:28
randallburtok.20:28
shardyrandallburt: you could be running slightly different versions of heat during a live upgrade couldn't you?20:28
lifelesszaneb: I think you need to take some anti-troll pills or something :)20:28
lifelessshardy: I would totally expect that.20:28
stevebaker#topic Summit review, BPs/actions and prioritization20:28
*** openstack changes topic to "Summit review, BPs/actions and prioritization (Meeting topic: heat)"20:28
* sdake for once agrees with lifeless20:28
shardyrandallburt: assume you plan to chase trunk or do rolling updates of some sort20:28
randallburtshardy:  fair point, but that's a very small windo20:28
randallburtwindow20:28
lifelessdepends on the cloud size20:28
lifelessand update frequency20:29
*** macjack has quit IRC20:29
randallburtnew topic, lets move on20:29
lifelessversions are useful, they can get captured in logs for automated post mortems - fin.20:29
shardyrandallburt: but it's that window when things are most likely to break20:29
*** danwent has joined #openstack-meeting20:29
stevebakerI need to triage the blueprint list, but here is where we are at https://launchpad.net/heat/+milestone/icehouse-120:29
shardylifeless: +1, capture in logs, return in error message to (authenticated) users20:29
*** dolphm has quit IRC20:30
stevebakerany general thoughts on summit?20:30
asalkeldtoo many20:30
*** IlyaE has quit IRC20:30
randallburtindeed.20:31
*** sarob has quit IRC20:31
*** sandywalsh has joined #openstack-meeting20:31
sdakemaybe best to let them filter out into the implementation over the next 6 mo20:31
asalkeldwe need to go through the etherpads20:31
asalkeldand make blueprint / fill in current ones20:31
stevebakerI'm a little worried that options for software config have expanded, not reduced. But I still think that arguments need to be augmented with actual code from this point20:32
randallburtstevebaker:  +900120:32
shardystevebaker: do we have an umbrella BP showing the dependent BPs for software-config to happen?20:32
*** grapex has joined #openstack-meeting20:32
*** grapex has left #openstack-meeting20:33
stevebakershardy: I think the blueprints need to be completely rejigged to reflect our refined understanding20:33
*** fnaval_ has quit IRC20:33
asalkeldyeah, time consuming stuff20:33
stevebaker#action stevebaker re-organise software config blueprints20:33
randallburtheavy is the head...20:33
shardystevebaker: Ok, cool, just wondered if we've started a task breakdown for that in particular, since it seems the biggest chunk of work20:33
shardystevebaker: I'll raise some and do a wiki related to the request scoping, trusts, admin, in-instance auth related stuff20:34
stevebakershardy:20:34
stevebakershardy: thanks20:34
*** DandyPandy has joined #openstack-meeting20:34
asalkeldstevebaker, I can help with bp pruning too20:35
shardyWhat are the other big items, autoscaling, ...?20:35
tspatzierstevebaker, for software config which is the master BP? is it hot-software-config?20:35
mspreitzI'm still not clear on how the software config stuff will bootstrap20:35
shardystevebaker: Yeah, get volunteers to help get things into shape or you'll go insane clicking in launchpad :)20:35
stevebakerso as per normal, people should be writing their own blueprints, and setting the Milestone Target based on what they think is achievable20:35
shardystevebaker: My concern was taking the big items, breaking them up and getting folks commited to working on the bits20:36
asalkeldshardy, there was "stack <action> stop_on_error"20:36
asalkeldthat enabled debugging, and retry20:37
stevebakerand you don't *need* something to be approved to work on it, but you carry the risk of being smacked with a banhammer at the end of the process20:37
randallburtwe also should consider some of the incoming requirements from trove and savannah20:37
stevebakerrandallburt: they know to raise blueprints20:37
randallburtif sdake will ever let me use the banhammer… :P20:37
asalkeldrandallburt, yeah we probably need a way of prioritizing those features20:38
randallburtstevebaker:  k. I'll ping hub_cap next week when I'm in SFO20:38
stevebakershardy: I think all the big items have owners who can handle that, apart from software config20:38
stevebakershardy: are there others you are aware of that need breaking down and delegating?20:38
shardystevebaker: Ok, cool, as long as you're happy that's the case and know who they are :)20:38
*** lpabon has joined #openstack-meeting20:39
stevebakerradix, randallburt, autoscaling is big, let us know if help is needed20:39
hub_caphi lo randallburt ill be around20:39
sdakeyes we need to get rolling on autoscaling20:40
shardystevebaker: No, we just discussed a lot last week so wanted to make sure we had owners for all the major items20:40
stevebaker#action stevebaker to go through summit etherpads and make sure all blueprints are raised https://wiki.openstack.org/wiki/Summit/Icehouse/Etherpads#Heat20:40
asalkeldmaybe we can blog about summit?20:40
*** DandyPandy has quit IRC20:40
asalkeldto clarify ideas20:40
randallburtstevebaker:  will do20:40
stevebakermoving on?20:40
asalkeldyeah20:41
randallburtyup20:41
stevebaker#topic Change scope of Orchestration program to "OpenStack Control Program"20:41
*** openstack changes topic to "Change scope of Orchestration program to "OpenStack Control Program" (Meeting topic: heat)"20:41
randallburthere there be dragons.20:41
zanebwhere did this come from?20:41
sdakethis was mostly SpamapS idea, but since he isn't here, I'll suggest it20:41
sdakeyes dragons indeed :)20:41
mspreitzdo tell, why is this a good idea?20:41
shardyWhy?20:41
stevebakermy opinion: Orchestration already means all things to all people, so we just need to redefine what *we* mean by "Orchestration" ;)20:41
sdakehis argument was mostly of the line that "we are doing autoscaling in heat, and we do orchestration"20:41
zanebstevebaker ++20:41
randallburtstevebaker:  +1. Let solum be the new dumping ground20:42
*** dprince has quit IRC20:42
asalkeldSpamapS, also was aiming at mistral I think20:42
sdakeand there are other projects coming online such as qonos and mistral20:42
sdakei think his basic idea was to expand our scope to cover all the things ;)20:42
stevebakerasalkeld: so you think Mistral should be brought into our programme?20:42
mspreitzand "control program" is clearer?20:42
*** DrBacchus has joined #openstack-meeting20:42
asalkeldstevebaker, if we are going to use it for our core flow control20:43
asalkeldit would be nice20:43
sdakemistral controls workflow20:43
sdakeautoscaling api controls autoscale20:43
randallburtwasn't the longer term goal to move autoscale *out* of heat, though?20:43
sdakeheat controls the rest of the stack20:43
sdakethey are all related, in some nebulous way20:43
asalkeldI am not sure on this move20:43
stevebakerrandallburt: autoscaling will still be in the orchestration program though20:43
kebraywe orchestrate autoscaling.  autoscale doesn't necessarily have to be in orchestration.20:44
sdakeone problem it would solve is "how to depend on mistral in an integrated program" like heat20:44
randallburtstevebaker:  fair point20:44
*** sarob has joined #openstack-meeting20:44
*** otherwiseguy has joined #openstack-meeting20:44
stevebaker#topic Mistral20:44
*** openstack changes topic to "Mistral (Meeting topic: heat)"20:44
zanebautoscaling is going to be deeply connected to orchestration, they way we are planning to implement it20:44
asalkeldI don't want us to look like we are trying to take over openstack projects20:44
asalkeldbut if those projects are keen, I have no problem20:45
stevebakerasalkeld: if they belong in orchestration we should make the case, like tusker merging with tripleo20:45
kebrayI'm not convinced Mistral as a solid non-changing clear mission yet.  So, shouldn't spin too many brain cycles on it just yet IMO.20:45
randallburtI don't want us to be a shortcut to integrated status though20:45
shardystevebaker: +1, but we shouldn't redefine our scope to include totally non-orchestration related projects20:45
stevebakerno that wouldn't be the intent20:45
asalkeldI think we can defer this for a while20:45
sdakeclearly we don't want to present an opportunity to game the system20:45
stevebakershardy: agreed20:45
*** fnaval_ has joined #openstack-meeting20:46
sdakebut mistral is related in some way i can't put my finger on to what heat does :)20:46
stevebakerasalkeld: anything technical about Mistral you can present yet?20:46
zanebrandallburt: in theory new projects have to be incubated, even if part of established programs20:46
asalkeldso it's in design20:46
randallburtzaneb:  k20:46
stevebakerasalkeld: do you want to participate in that, so heat20:47
asalkeldwe would need to build it (not head devs)20:47
stevebaker's needs are represented20:47
asalkeldsure20:47
asalkeldI can make sure we get what we need20:47
asalkeldnot sure of the time line tho'20:47
stevebaker#topic Open discussion20:47
*** openstack changes topic to "Open discussion (Meeting topic: heat)"20:47
sdakethey ahave a roadmap20:47
asalkeldlong and winding road<map>20:48
timshttps://blueprints.launchpad.net/heat/+spec/namespace-stack-metadata20:48
randallburtso, does this latest resolution change our status in any way other than calling ourselve's Openstack Orchestration (™)?20:48
timslooking for feedback on namespacing stack-metadata20:48
sdakewell to do such a change, would require tc approval20:48
sdakewhich would require board approval20:48
sdakewhich means steve baker would have to sell it20:48
stevebakertims: is this for horizion presentation hints?20:48
sdakeand I assume we would all have to stand together to agree with the apporach20:48
timsstevebaker: yes20:48
kebrayFor those interested  https://etherpad.openstack.org/p/MistralRoadmap20:49
timsas well as other things20:49
stevebakerlets not call it metadata, please! ;)20:49
zanebrandallburt: not at all20:49
randallburtstevebaker:  lol20:49
randallburtzaneb:  k20:49
timsI'm not attached to the name :)20:49
timsjust a place where we can safely put things that Heat should ignore in the template20:49
shardyYeah metadata is already thrice overloaded20:49
kebraystevebaker  extra data?20:49
*** boris-42 has quit IRC20:49
*** DandyPandy has joined #openstack-meeting20:50
shardytims: Can it just be a comment block?20:50
shardytims: or do you need it parsed and available via the API?20:50
stevebakertims: so maybe a top-level template section which is ignored by heat engine20:50
*** DandyPandy has quit IRC20:50
randallburtshardy:  oh the looks tims gave me when I suggested that.20:50
stevebakershardy: it needs to be structured, for things outside heat to parse20:50
timshaha randallburt20:50
*** DandyPandy has joined #openstack-meeting20:50
shardyOK20:50
randallburtbesides, comments are lost when safeloaded20:50
timsyeah it should be a top level section20:51
kebraymetadata is supposed to be overloaded... it means data about other data.  It applies everywhere.20:51
asalkeldstack level Metadata?20:51
stevebakerimagine a visual template authoring tool, x,y coordinates of where resources are dragged need to be stored somewhere20:51
asalkeldto be inline with resource Metadata20:51
kebrayok, cube conversations just convinced me.  Just call it data :-)20:51
randallburtin the context of Horizon, its actual data though20:51
*** jasond has joined #openstack-meeting20:51
shardykebray: but the template terminology should be distinct, because we already have metadata blocks which actually do stuff20:51
*** vijendar has joined #openstack-meeting20:52
zanebkebray: if we had 50 sections called 'data', I would complain about that too ;)20:52
stevebakerasalkeld: there is no resource metadata in HOT (not exposed anyway)20:52
asalkeldstevebaker, cool:)20:52
timssoo stack-metadata then?20:53
kebrayzaneb what should we call it?20:53
shardystevebaker: Are you sure?  We have a Metadata block in CFN templates?20:53
stevebakertims: so, I think the answer is yes, but we need to bikeshed the name. I think I'd prefer something top-level rather than sprinkling data throughout the template20:53
timsstevebaker: agreed20:53
randallburtstevebaker:  agreed20:53
kebraystevebaker agreed20:53
*** glange has left #openstack-meeting20:54
asalkeldsounds ok20:54
stevebakeromg, we agreed on something!20:54
asalkeld:-O20:54
stevebaker6 minute4s20:54
tims:)20:54
shardyhttps://github.com/openstack/heat-templates/blob/master/hot/F18/WordPress_NoKey.yaml#L9320:54
randallburttims is a consensus builder20:54
shardystevebaker: ^^20:54
zanebkebray: sorry, that was supposed to be a reply to the earlier comment about 'metadata' being intentionally overloaded20:55
* kebray says no worries zaneb 20:55
stevebakershardy: HOT doesn't explicitly ban Metadata yet, but it is not part of the spec and there is no alternative until some bare-bones software config is implemented20:55
radixoh no20:55
radix*shakefist* time zoooooones! :(20:56
randallburtradix: time change getcha didn't it20:56
radixyes :(20:56
stevebakerDST can die in a fire20:56
*** tims has quit IRC20:56
sdakemove to arizona - we roll on UTC :)20:56
*** tims1 has joined #openstack-meeting20:56
radixso, I'm prepping a proposed api spec (actually I started it a long time ago but never published it) for autoscaling20:57
*** rakhmerov has quit IRC20:57
radixI'll post it to the list when I've put it up for comment20:57
zanebcapital20:57
stevebakerlets mosey in a relaxed fashion back to #heat and have a friendly conversation20:58
*** lakshmi_n has joined #openstack-meeting20:58
stevebaker#endmeeting20:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:58
openstackMeeting ended Wed Nov 13 20:58:33 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:58
*** twoputt_ has quit IRC20:58
*** twoputt has quit IRC20:58
radixokie20:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-11-13-20.00.html20:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-11-13-20.00.txt20:58
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-11-13-20.00.log.html20:58
*** tspatzier has left #openstack-meeting20:58
*** randallburt has left #openstack-meeting20:58
*** jasond has left #openstack-meeting20:58
stevebakerthanks all20:58
*** arbylee has left #openstack-meeting20:59
*** mspreitz has left #openstack-meeting20:59
*** skraynev_ has quit IRC20:59
*** andrew_plunk has left #openstack-meeting21:00
*** andersonvom has left #openstack-meeting21:01
*** tanisdl has joined #openstack-meeting21:02
*** ikhudoshyn_ has joined #openstack-meeting21:02
*** Maharajan has joined #openstack-meeting21:03
*** Maharajan has left #openstack-meeting21:04
*** bdpayne has quit IRC21:04
*** bdpayne has joined #openstack-meeting21:05
*** spzala has quit IRC21:08
*** luis__ has quit IRC21:11
*** jamespage_ has joined #openstack-meeting21:12
*** jamespage_ has quit IRC21:13
*** jlibosva has quit IRC21:15
*** BStokes999 has joined #openstack-meeting21:17
*** yamahata__ has joined #openstack-meeting21:17
*** BStokes has quit IRC21:19
*** yamahata_ has quit IRC21:19
*** lpabon has quit IRC21:19
*** julim has quit IRC21:21
*** lakshmi_n has left #openstack-meeting21:22
*** dvarga_ has joined #openstack-meeting21:26
*** dvarga_ has quit IRC21:26
*** rakhmerov has joined #openstack-meeting21:27
*** bgorski has quit IRC21:29
*** dvarga has quit IRC21:29
*** ildikov has quit IRC21:33
*** jmontemayor has quit IRC21:34
*** epim has quit IRC21:38
*** krtaylor has quit IRC21:40
*** luis__ has joined #openstack-meeting21:41
*** luis__ has quit IRC21:45
*** kgriffs is now known as rdaneel21:47
*** jtomasek has quit IRC21:47
*** sudorandom has left #openstack-meeting21:48
*** thelorax123 has quit IRC21:50
*** sdake_ has quit IRC21:50
*** sdake has quit IRC21:51
*** zehicle_at_dell has quit IRC21:51
*** zehicle_at_dell has joined #openstack-meeting21:51
*** ArxCruz has joined #openstack-meeting21:52
*** rdaneel is now known as kgriffs21:53
*** spzala has joined #openstack-meeting21:53
*** vito-ordaz has joined #openstack-meeting21:54
*** sdake has joined #openstack-meeting21:54
*** sdake_ has joined #openstack-meeting21:55
*** sdake_ has quit IRC21:55
*** sdake_ has joined #openstack-meeting21:55
*** krtaylor has joined #openstack-meeting21:56
*** vito-ordaz has quit IRC21:57
*** vito-ord_ has joined #openstack-meeting21:57
*** rakhmerov has quit IRC21:58
*** joesavak has joined #openstack-meeting21:58
*** rakhmerov has joined #openstack-meeting21:58
*** jasondotstar has quit IRC21:59
*** sarob has quit IRC21:59
*** sarob has joined #openstack-meeting22:00
*** oubiwann has quit IRC22:01
*** jsavak has quit IRC22:01
*** rakhmerov has quit IRC22:03
*** sarob has quit IRC22:04
*** ikhudoshyn_ has quit IRC22:04
*** pdmars has quit IRC22:04
*** primiano has joined #openstack-meeting22:06
*** markvan has quit IRC22:06
*** primiano has left #openstack-meeting22:06
*** jsavak has joined #openstack-meeting22:07
*** vuil has quit IRC22:07
*** epim has joined #openstack-meeting22:08
*** joesavak has quit IRC22:11
*** dkranz has quit IRC22:11
*** lincolnt has left #openstack-meeting22:11
*** vuil has joined #openstack-meeting22:13
*** armax has left #openstack-meeting22:15
*** thelorax123 has joined #openstack-meeting22:18
*** weshay has quit IRC22:20
*** danwent has quit IRC22:21
*** bdpayne has quit IRC22:22
*** pcm_ has quit IRC22:22
*** topol has quit IRC22:22
*** bdpayne has joined #openstack-meeting22:22
*** thelorax123 has quit IRC22:23
*** sarob has joined #openstack-meeting22:24
*** jsavak has quit IRC22:30
*** sarob_ has joined #openstack-meeting22:31
*** kgriffs is now known as kgriffs_afk22:33
*** sarob has quit IRC22:35
*** loq_mac has joined #openstack-meeting22:35
*** hemna has quit IRC22:35
*** sarob_ has quit IRC22:36
*** loq_mac has quit IRC22:36
*** epim has quit IRC22:37
*** tims1 has quit IRC22:38
*** jpeeler has quit IRC22:38
*** blamar has quit IRC22:39
*** thomasem has quit IRC22:47
*** flaper87 is now known as flaper87|afk22:47
*** jlucci has joined #openstack-meeting22:48
*** kgriffs_afk is now known as kgriffs22:49
*** vijendar has quit IRC22:50
*** whenry has quit IRC22:50
*** vijendar has joined #openstack-meeting22:50
*** markpeek has joined #openstack-meeting22:51
*** xyang1 has quit IRC22:54
*** vijendar has quit IRC22:55
*** garyduan has quit IRC22:55
*** garyduan has joined #openstack-meeting22:55
*** rakhmerov has joined #openstack-meeting22:59
*** lblanchard has quit IRC23:00
*** sushils has quit IRC23:06
*** burt has quit IRC23:06
*** oubiwann has joined #openstack-meeting23:06
*** nati_ueno has joined #openstack-meeting23:10
*** vuil has quit IRC23:10
*** vuil has joined #openstack-meeting23:10
*** neelashah has quit IRC23:11
*** sushils has joined #openstack-meeting23:12
*** dcramer_ has quit IRC23:14
*** twoputt_ has joined #openstack-meeting23:15
*** twoputt has joined #openstack-meeting23:15
*** denis_makogon has quit IRC23:16
*** zehicle_at_dell has quit IRC23:20
*** diogogmt has quit IRC23:22
*** sacharya has quit IRC23:22
*** eharney has quit IRC23:25
*** mrodden has quit IRC23:25
*** lbragstad has quit IRC23:26
*** sarob has joined #openstack-meeting23:26
*** thinrichs has joined #openstack-meeting23:29
*** thinrichs has left #openstack-meeting23:29
*** otherwiseguy has quit IRC23:29
*** sarob_ has joined #openstack-meeting23:29
*** masayukig has joined #openstack-meeting23:30
*** vito-ordaz has joined #openstack-meeting23:30
*** sarob has quit IRC23:30
*** dkranz has joined #openstack-meeting23:31
*** rakhmerov has quit IRC23:32
*** vito-ord_ has quit IRC23:33
*** adrian_otto has quit IRC23:33
*** vito-ordaz has quit IRC23:35
*** twoputt_ has quit IRC23:36
*** twoputt has quit IRC23:36
*** esker has quit IRC23:37
*** sarob has joined #openstack-meeting23:38
*** sarob_ has quit IRC23:38
*** galstrom is now known as galstrom_zzz23:39
*** beagles has quit IRC23:39
*** sarob has quit IRC23:41
*** sarob has joined #openstack-meeting23:41
*** vuil has quit IRC23:44
*** markpeek has quit IRC23:44
*** vuil has joined #openstack-meeting23:44
*** sarob_ has joined #openstack-meeting23:44
*** sarob has quit IRC23:47
*** tanisdl has quit IRC23:48
*** sarob_ has quit IRC23:49
*** kgriffs is now known as kgriffs_afk23:50
*** jecarey has quit IRC23:53
*** krtaylor has quit IRC23:53
*** beagles has joined #openstack-meeting23:54
*** gyee has quit IRC23:55
*** twoputt_ has joined #openstack-meeting23:57
*** twoputt has joined #openstack-meeting23:57
*** matsuhashi has joined #openstack-meeting23:57
*** sushils has quit IRC23:59

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