Tuesday, 2015-01-27

*** aranjan has joined #openstack-meeting00:01
*** VW_ has quit IRC00:02
*** armax has quit IRC00:02
*** andreykurilin_ has quit IRC00:04
*** ijw has joined #openstack-meeting00:05
*** padkrish has quit IRC00:05
*** david_hu__ has quit IRC00:06
*** padkrish has joined #openstack-meeting00:06
*** darrenc is now known as darrenc_afk00:07
*** armax has joined #openstack-meeting00:08
*** padkrish has quit IRC00:10
*** padkrish has joined #openstack-meeting00:13
*** MaxV has joined #openstack-meeting00:14
*** zhhuabj_ has quit IRC00:16
*** darrenc_afk is now known as darrenc00:18
*** baoli has quit IRC00:19
*** baoli has joined #openstack-meeting00:20
*** Mandell has joined #openstack-meeting00:20
*** leeantho has quit IRC00:21
*** fzdarsky|afk has quit IRC00:21
*** leeantho has joined #openstack-meeting00:21
*** zhhuabj_ has joined #openstack-meeting00:22
*** amitgandhinz has joined #openstack-meeting00:23
*** andreykurilin_ has joined #openstack-meeting00:23
*** zhhuabj_ has quit IRC00:25
*** zhhuabj has joined #openstack-meeting00:25
*** _nadya_ has joined #openstack-meeting00:26
*** yingjun has joined #openstack-meeting00:27
*** amitgandhinz has quit IRC00:27
*** ebalduf has quit IRC00:27
*** _nadya_ has quit IRC00:30
*** shashankhegde has joined #openstack-meeting00:32
*** gokrokve has quit IRC00:32
*** adalbas has quit IRC00:34
*** etoews has joined #openstack-meeting00:34
*** leeantho has quit IRC00:35
*** baoli has quit IRC00:35
*** baoli has joined #openstack-meeting00:36
*** dims has quit IRC00:38
*** baoli has quit IRC00:38
*** dims has joined #openstack-meeting00:39
*** fifieldt has joined #openstack-meeting00:39
*** yingjun has quit IRC00:39
*** etoews has quit IRC00:39
*** baoli has joined #openstack-meeting00:39
*** tomoe has joined #openstack-meeting00:39
*** dims has quit IRC00:39
*** sigmavirus24 is now known as sigmavirus24_awa00:40
*** gabriel-bezerra has quit IRC00:41
*** markmcclain has quit IRC00:41
*** thedodd has joined #openstack-meeting00:42
*** gabriel-bezerra has joined #openstack-meeting00:42
*** markmcclain has joined #openstack-meeting00:42
*** atiwari has quit IRC00:44
*** atiwari has joined #openstack-meeting00:44
*** atiwari has quit IRC00:44
*** dims has joined #openstack-meeting00:45
*** Leonr has joined #openstack-meeting00:49
*** tomoe has quit IRC00:49
*** tomoe has joined #openstack-meeting00:50
*** dims has quit IRC00:50
*** Guest19498 has quit IRC00:51
*** andreykurilin_ has quit IRC00:51
*** shengjiemin has joined #openstack-meeting00:52
*** sandywalsh has quit IRC00:52
*** banix has joined #openstack-meeting00:52
*** belmoreira has quit IRC00:53
*** harlowja has quit IRC00:54
*** Leonr has quit IRC00:54
*** stevemar has joined #openstack-meeting00:54
*** jaypipes has quit IRC00:56
*** gokrokve has joined #openstack-meeting00:56
*** dannywilson has quit IRC00:56
*** topol has joined #openstack-meeting00:57
*** kebray has quit IRC00:59
*** gokrokve has quit IRC01:01
*** markmcclain has quit IRC01:01
*** MaxV has quit IRC01:03
*** dulek has quit IRC01:04
*** etoews has joined #openstack-meeting01:04
*** markvoelker has quit IRC01:05
*** carl_baldwin has quit IRC01:06
*** markvoelker has joined #openstack-meeting01:06
*** banix has quit IRC01:07
*** Sukhdev has quit IRC01:08
*** etoews has quit IRC01:08
*** oomichi has joined #openstack-meeting01:08
*** banix has joined #openstack-meeting01:09
*** markvoelker has quit IRC01:10
*** gabriel-bezerra has quit IRC01:13
*** gabriel-bezerra has joined #openstack-meeting01:13
*** armax has quit IRC01:14
*** armax has joined #openstack-meeting01:15
*** gyee has quit IRC01:15
*** ijw has quit IRC01:15
*** gokrokve has joined #openstack-meeting01:16
*** fnaval has quit IRC01:16
*** fnaval has joined #openstack-meeting01:16
*** alexpilotti has joined #openstack-meeting01:18
*** achanda_ has joined #openstack-meeting01:19
*** marun_ has joined #openstack-meeting01:20
*** yamahata has joined #openstack-meeting01:22
*** eghobo has quit IRC01:23
*** achanda has quit IRC01:23
*** achanda_ has quit IRC01:24
*** nagromlt has joined #openstack-meeting01:25
*** yingjun has joined #openstack-meeting01:25
*** marun has quit IRC01:25
*** marun_ is now known as marun01:25
*** crc32 has quit IRC01:25
*** marun has quit IRC01:26
*** otter768 has joined #openstack-meeting01:26
*** armax has quit IRC01:28
*** reed has quit IRC01:28
*** dsetia has quit IRC01:28
*** aranjan has quit IRC01:29
*** bdpayne has quit IRC01:29
*** banix has quit IRC01:31
*** etoews has joined #openstack-meeting01:32
*** otter768 has quit IRC01:32
*** gabriel-bezerra has quit IRC01:33
*** mattgriffin has quit IRC01:34
*** harlowja has joined #openstack-meeting01:35
*** yeungp has quit IRC01:35
*** yingjun has quit IRC01:35
*** yapeng has joined #openstack-meeting01:35
*** suro_ has quit IRC01:38
*** yapeng has quit IRC01:40
*** rmoe has quit IRC01:40
*** noelbk has quit IRC01:42
*** ctlaugh has joined #openstack-meeting01:42
*** gabriel-bezerra has joined #openstack-meeting01:42
*** xuhanp has joined #openstack-meeting01:43
*** sbalukoff has quit IRC01:43
*** yapeng has joined #openstack-meeting01:47
*** bdpayne has joined #openstack-meeting01:48
*** bdpayne has quit IRC01:48
*** gokrokve has quit IRC01:51
*** whenry has quit IRC01:51
*** thedodd has quit IRC01:51
*** eghobo has joined #openstack-meeting01:52
*** armax has joined #openstack-meeting01:53
*** eghobo has quit IRC01:54
*** carl_baldwin has joined #openstack-meeting01:54
*** sbalukoff has joined #openstack-meeting01:56
*** dims has joined #openstack-meeting01:59
*** ChuckC has quit IRC02:01
*** rmoe has joined #openstack-meeting02:01
*** theanalyst has quit IRC02:01
*** ChuckC_ has joined #openstack-meeting02:01
*** haomaiwang has joined #openstack-meeting02:01
*** thomasem has quit IRC02:02
*** theanalyst has joined #openstack-meeting02:04
*** rwsu is now known as rwsu-afk02:05
*** ddieterly has joined #openstack-meeting02:06
*** tomoe_ has joined #openstack-meeting02:07
*** avozza is now known as zz_avozza02:08
*** ChuckC_ has quit IRC02:09
*** ChuckC has joined #openstack-meeting02:09
*** tomoe_ has quit IRC02:09
*** rms_13 has quit IRC02:10
*** tomoe has quit IRC02:11
*** otter768 has joined #openstack-meeting02:14
*** salv-orlando has joined #openstack-meeting02:14
*** padkrish has quit IRC02:15
*** padkrish has joined #openstack-meeting02:15
*** ChuckC_ has joined #openstack-meeting02:15
*** mattgriffin has joined #openstack-meeting02:16
*** salv-orl_ has joined #openstack-meeting02:18
*** salv-orlando has quit IRC02:18
*** ChuckC has quit IRC02:19
*** padkrish has quit IRC02:20
*** carl_baldwin has quit IRC02:20
*** liusheng has quit IRC02:20
*** mberlin has quit IRC02:20
*** ivar-laz_ has joined #openstack-meeting02:21
*** kaisers1 has quit IRC02:21
*** kaisers has joined #openstack-meeting02:21
*** liusheng has joined #openstack-meeting02:21
*** mberlin has joined #openstack-meeting02:21
*** alexpilotti has quit IRC02:22
*** shashankhegde has quit IRC02:22
*** padkrish has joined #openstack-meeting02:24
*** dims has quit IRC02:24
*** ivar-lazzaro has quit IRC02:25
*** ivar-laz_ has quit IRC02:25
*** Mandell has quit IRC02:25
*** armax has quit IRC02:27
*** fnaval has quit IRC02:30
*** tomoe has joined #openstack-meeting02:31
*** etoews has quit IRC02:32
*** noelbk has joined #openstack-meeting02:35
*** tomoe has quit IRC02:36
*** etoews has joined #openstack-meeting02:37
*** dboik has quit IRC02:38
*** gokrokve has joined #openstack-meeting02:40
*** tomoe has joined #openstack-meeting02:40
*** s3wong has quit IRC02:41
*** mwagner_lap has quit IRC02:42
*** etoews has quit IRC02:43
*** fnaval has joined #openstack-meeting02:45
*** yamamoto_ has joined #openstack-meeting02:47
*** yamahata has quit IRC02:48
*** epico has joined #openstack-meeting02:51
*** thedodd has joined #openstack-meeting02:53
*** thedodd has quit IRC02:53
*** mwagner_lap has joined #openstack-meeting02:53
*** etoews has joined #openstack-meeting02:56
*** etoews_ has joined #openstack-meeting02:58
*** etoews has quit IRC02:58
*** dboik has joined #openstack-meeting02:58
*** bdpayne has joined #openstack-meeting02:58
*** padkrish has quit IRC02:59
*** noelbk has quit IRC03:01
*** paragan has joined #openstack-meeting03:02
*** paragan has joined #openstack-meeting03:02
*** tellesnobrega_ has quit IRC03:03
*** devlaps has quit IRC03:03
*** tomoe has quit IRC03:04
*** tomoe has joined #openstack-meeting03:06
*** banix has joined #openstack-meeting03:06
*** VW_ has joined #openstack-meeting03:08
*** ddieterly has quit IRC03:09
*** hemna has joined #openstack-meeting03:09
*** paragan has quit IRC03:09
*** bill_az has quit IRC03:11
*** VW_ has quit IRC03:11
*** sbalukoff has quit IRC03:14
*** yingjun has joined #openstack-meeting03:16
*** tomoe has quit IRC03:17
*** bdpayne has quit IRC03:21
*** tomoe has joined #openstack-meeting03:22
*** paragan has joined #openstack-meeting03:22
*** paragan has joined #openstack-meeting03:22
*** novas0x2a|laptop has quit IRC03:29
*** VW_ has joined #openstack-meeting03:32
*** rushiagr_away is now known as rushiagr03:36
*** noelbk has joined #openstack-meeting03:38
*** mdomsch has quit IRC03:38
*** yapeng has quit IRC03:39
*** hemna has quit IRC03:39
*** mattgriffin has quit IRC03:40
*** kebray has joined #openstack-meeting03:42
*** kebray has quit IRC03:44
*** vozcelik has joined #openstack-meeting03:44
*** hemna has joined #openstack-meeting03:46
*** ayoung is now known as ayoung_ZZzz__03:49
*** anish_ has joined #openstack-meeting03:51
*** hemna has quit IRC03:56
*** dannywilson has joined #openstack-meeting03:57
*** kebray has joined #openstack-meeting03:57
*** dulek has joined #openstack-meeting04:00
*** yingjun has quit IRC04:00
*** rushiagr is now known as rushiagr_away04:01
*** dannywilson has quit IRC04:01
*** hemna has joined #openstack-meeting04:01
*** gokrokve has quit IRC04:03
*** achanda has joined #openstack-meeting04:05
*** spzala has quit IRC04:06
*** mattgriffin has joined #openstack-meeting04:12
*** pradipta_away is now known as pradipta04:12
*** bdpayne has joined #openstack-meeting04:12
*** banix has quit IRC04:16
*** VW_ has quit IRC04:16
*** hemna has quit IRC04:17
*** markvoelker has joined #openstack-meeting04:17
*** changbl has quit IRC04:17
*** JRobinson__ is now known as JRobinson__afk04:19
*** gokrokve has joined #openstack-meeting04:20
*** rajeshr has joined #openstack-meeting04:20
*** VW_ has joined #openstack-meeting04:20
*** etoews_ has quit IRC04:21
*** hemna has joined #openstack-meeting04:21
*** etoews has joined #openstack-meeting04:21
*** shankar has joined #openstack-meeting04:24
*** ijw has joined #openstack-meeting04:25
*** rajeshr has quit IRC04:29
*** JRobinson__afk has quit IRC04:29
*** carl_baldwin has joined #openstack-meeting04:31
*** Mandell has joined #openstack-meeting04:32
*** bdpayne has quit IRC04:33
*** BharatK has joined #openstack-meeting04:33
*** dulek has quit IRC04:35
*** hemna has quit IRC04:36
*** JRobinson__afk has joined #openstack-meeting04:36
*** changbl has joined #openstack-meeting04:37
*** rajeshr has joined #openstack-meeting04:37
*** JRobinson__afk is now known as JRobinson__04:37
*** amotoki has joined #openstack-meeting04:40
*** bdpayne has joined #openstack-meeting04:40
*** shankarprasad has joined #openstack-meeting04:41
*** shankar has quit IRC04:41
*** VW_ has quit IRC04:42
*** sbalukoff has joined #openstack-meeting04:44
*** otter768 has quit IRC04:47
*** alexpilotti has joined #openstack-meeting04:48
*** mtanino has quit IRC04:48
*** changbl has quit IRC04:49
*** hemna has joined #openstack-meeting04:49
*** otter768 has joined #openstack-meeting04:49
*** jungleboyj__ has quit IRC04:50
*** unicell has quit IRC04:50
*** shankarprasad has quit IRC04:51
*** aranjan has joined #openstack-meeting04:53
*** ccrouch has quit IRC04:53
*** rushiagr_away is now known as rushiagr04:54
*** ChuckC_ is now known as ChuckC04:56
*** carl_baldwin has quit IRC04:57
*** otter768 has quit IRC04:59
*** jungleboyj__ has joined #openstack-meeting04:59
*** fnaval has quit IRC04:59
*** jungleboyj__ is now known as jungleboyj05:00
*** fnaval has joined #openstack-meeting05:00
*** akuznetsov has joined #openstack-meeting05:02
*** esker has joined #openstack-meeting05:03
*** achanda has quit IRC05:03
*** carl_baldwin has joined #openstack-meeting05:04
*** fnaval has quit IRC05:04
*** openfly has left #openstack-meeting05:06
*** noslzzp has quit IRC05:06
*** markvoelker has quit IRC05:09
*** achanda has joined #openstack-meeting05:09
*** garyh has quit IRC05:09
*** markvoelker has joined #openstack-meeting05:10
*** harlowja is now known as harlowja_away05:10
*** achanda has quit IRC05:13
*** shengjiemin has quit IRC05:14
*** markvoelker has quit IRC05:14
*** shengjiemin has joined #openstack-meeting05:15
*** salv-orl_ has quit IRC05:16
*** suro_ has joined #openstack-meeting05:22
*** numan has joined #openstack-meeting05:23
*** hemna has quit IRC05:25
*** unicell has joined #openstack-meeting05:26
*** yapeng has joined #openstack-meeting05:28
*** zehicle_ has joined #openstack-meeting05:28
*** nshaikh has joined #openstack-meeting05:30
*** etoews has quit IRC05:31
*** yapeng has quit IRC05:33
*** suro_ has quit IRC05:35
*** ildikov has quit IRC05:36
*** markvoelker has joined #openstack-meeting05:37
*** markvoelker has quit IRC05:38
*** markvoelker has joined #openstack-meeting05:38
*** garyh has joined #openstack-meeting05:40
*** dims has joined #openstack-meeting05:41
*** mrmartin has joined #openstack-meeting05:42
*** markvoelker has quit IRC05:43
*** yingjun has joined #openstack-meeting05:43
*** baoli has quit IRC05:44
*** carl_baldwin has quit IRC05:44
*** baoli has joined #openstack-meeting05:45
*** ajayaa has joined #openstack-meeting05:47
*** baoli has quit IRC05:49
*** dims has quit IRC05:49
*** neeti has joined #openstack-meeting05:50
*** dims has joined #openstack-meeting05:50
*** dims has quit IRC05:52
*** dims has joined #openstack-meeting05:52
*** yamahata has joined #openstack-meeting05:53
*** mrmartin has quit IRC05:56
*** ijw has quit IRC05:57
*** daneyon has joined #openstack-meeting05:57
*** ijw has joined #openstack-meeting05:58
*** daneyon_ has quit IRC05:58
*** markmcclain has joined #openstack-meeting06:01
*** achanda has joined #openstack-meeting06:03
*** thumpba has joined #openstack-meeting06:04
*** liusheng has quit IRC06:04
*** liusheng has joined #openstack-meeting06:04
*** gokrokve_ has joined #openstack-meeting06:05
*** akuznetsov has quit IRC06:05
*** gokrokve has quit IRC06:08
*** gokrokve_ has quit IRC06:10
*** JRobinson__ has quit IRC06:10
*** salv-orlando has joined #openstack-meeting06:11
*** oomichi has quit IRC06:13
*** ildikov has joined #openstack-meeting06:15
*** comay has quit IRC06:19
*** jyuso has quit IRC06:19
*** vozcelik has quit IRC06:20
*** dims has quit IRC06:23
*** dboik has quit IRC06:23
*** liusheng has quit IRC06:24
*** liusheng has joined #openstack-meeting06:25
*** dims has joined #openstack-meeting06:26
*** vigneshvar has joined #openstack-meeting06:27
*** erikmoe has joined #openstack-meeting06:28
*** theanalyst has quit IRC06:30
*** dims has quit IRC06:30
*** markvoelker has joined #openstack-meeting06:31
*** theanalyst has joined #openstack-meeting06:32
*** adahms has quit IRC06:32
*** markvoelker has quit IRC06:36
*** shashankhegde has joined #openstack-meeting06:36
*** shankar has joined #openstack-meeting06:37
*** gokrokve has joined #openstack-meeting06:37
*** gokrokve has quit IRC06:39
*** gokrokve has joined #openstack-meeting06:39
*** zz_avozza is now known as avozza06:41
*** mattgriffin has quit IRC06:44
*** gokrokve has quit IRC06:44
*** mrunge has joined #openstack-meeting06:44
*** aepifanov has joined #openstack-meeting06:45
*** eghobo has joined #openstack-meeting06:45
*** nshaikh has quit IRC06:46
*** shashankhegde has quit IRC06:49
*** shankar has quit IRC06:50
*** shankar has joined #openstack-meeting06:51
*** ajo has joined #openstack-meeting06:52
*** avozza is now known as zz_avozza06:58
*** markvoelker has joined #openstack-meeting06:58
*** otter768 has joined #openstack-meeting07:00
*** markmcclain has quit IRC07:01
*** markvoelker has quit IRC07:04
*** otter768 has quit IRC07:04
*** noelbk has quit IRC07:04
*** SridharG has joined #openstack-meeting07:05
*** bdpayne has quit IRC07:05
*** topol has quit IRC07:10
*** pkoniszewski has joined #openstack-meeting07:12
*** salv-orlando has quit IRC07:16
*** zz_avozza is now known as avozza07:17
*** yapeng has joined #openstack-meeting07:17
*** scheuran has joined #openstack-meeting07:18
*** irenab has joined #openstack-meeting07:18
*** yapeng has quit IRC07:22
*** aranjan has quit IRC07:22
*** irenab has quit IRC07:23
*** asalkeld has joined #openstack-meeting07:23
*** esker has quit IRC07:24
*** shengjiemin has quit IRC07:24
*** belmoreira has joined #openstack-meeting07:24
*** shengjiemin has joined #openstack-meeting07:26
*** nellysmitt has joined #openstack-meeting07:26
*** dims has joined #openstack-meeting07:27
*** doron_afk has joined #openstack-meeting07:28
*** shengjiemin has quit IRC07:30
*** _nadya_ has joined #openstack-meeting07:31
*** dims has quit IRC07:31
*** thumpba has quit IRC07:33
*** shengjiemin has joined #openstack-meeting07:34
*** _nadya_ has quit IRC07:34
*** stevemar has quit IRC07:35
*** suro_ has joined #openstack-meeting07:35
*** gokrokve has joined #openstack-meeting07:37
*** pnavarro has joined #openstack-meeting07:40
*** gokrokve has quit IRC07:42
*** _nadya_ has joined #openstack-meeting07:42
*** mrmartin has joined #openstack-meeting07:44
*** sahid has joined #openstack-meeting07:45
*** eghobo has quit IRC07:46
*** jwang_ has quit IRC07:46
*** jwang_ has joined #openstack-meeting07:46
*** avozza is now known as zz_avozza07:49
*** shengjiemin has quit IRC07:50
*** ijw has quit IRC07:50
*** evgenyf has joined #openstack-meeting07:51
*** berendt has joined #openstack-meeting07:51
*** shengjiemin has joined #openstack-meeting07:55
*** e0ne has joined #openstack-meeting07:55
*** belmoreira has quit IRC07:55
*** wojdev has joined #openstack-meeting07:58
*** _nadya_ has quit IRC07:58
*** _nadya_ has joined #openstack-meeting07:58
*** irenab has joined #openstack-meeting07:59
*** jyuso1 has joined #openstack-meeting07:59
*** markvoelker has joined #openstack-meeting08:00
anteaya#startmeeting third-party08:00
openstackMeeting started Tue Jan 27 08:00:34 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: third-party)"08:00
openstackThe meeting name has been set to 'third_party'08:00
*** safchain has joined #openstack-meeting08:00
anteayahello08:00
anteayaraise your hand if you are here for the third-party meeting08:01
*** MaxV has joined #openstack-meeting08:02
*** liusheng has quit IRC08:02
*** belmoreira has joined #openstack-meeting08:03
*** liusheng has joined #openstack-meeting08:03
*** doron_afk is now known as Guest7707108:03
*** Guest77071 is now known as doron_afk08:03
*** rajeshr has quit IRC08:03
*** Mandell has quit IRC08:04
*** doron_afk is now known as Guest7707108:04
*** markvoelker has quit IRC08:04
*** _nadya_ has quit IRC08:04
*** sergef has joined #openstack-meeting08:05
jyuso1anteaya: hi:)08:05
*** wojdev has quit IRC08:05
*** kebray has quit IRC08:05
*** dzimine has left #openstack-meeting08:06
anteayajyuso1: hello08:06
*** MaxV has quit IRC08:06
anteayaI met Yunhong Jiang today08:06
anteayahe is at the nova mid-cycle08:07
*** irenab has quit IRC08:07
jyuso1anteaya: oh,yes,he is in our team.I've heard about your meeting:)08:07
*** irenab has joined #openstack-meeting08:08
anteayagreat08:08
*** yamahata has quit IRC08:08
anteayaso we talked about nfv testing today08:08
*** MaxV has joined #openstack-meeting08:08
*** harlowja_away has quit IRC08:08
jyuso1anteaya: about nfv ci?08:09
anteayayes we talked about the status of testing nfv08:10
anteayaso I talked about what I knew about your system08:10
*** MaxV has quit IRC08:10
anteayabecause it is my understanding that you are working to test nfv08:10
*** anish_ has quit IRC08:13
*** irenab has quit IRC08:13
anteayajyuso1: am I correct?08:14
*** wojdev has joined #openstack-meeting08:14
*** irenab has joined #openstack-meeting08:14
jyuso1anteaya: sorry,I don't know the nfv testing details in fact.08:15
anteayajyuso1: okay great08:15
anteayawho might?08:15
*** anish_ has joined #openstack-meeting08:15
anteayamight that be adrian?08:15
*** suro_ has quit IRC08:15
jyuso1anteaya: may be heyongli know something about it.08:16
anteayajyuso1: okay08:16
anteayawell nova people are curious08:17
*** irenab has quit IRC08:17
anteayaso if someone from your team started attending the nfv meeting08:17
anteayathat would be great08:17
* anteaya gets link08:17
*** salv-orlando has joined #openstack-meeting08:17
*** irenab has joined #openstack-meeting08:17
jyuso1anteaya: OK,thanks I'll feed back to our team:)08:18
*** irenab has joined #openstack-meeting08:18
anteaya#link https://wiki.openstack.org/wiki/Meetings#Telco_Working_Group_Meeting08:18
anteayathank you08:18
*** matrohon has joined #openstack-meeting08:18
anteayajyuso1: is your ci system commenting on all nova patches now?08:18
*** aranjan has joined #openstack-meeting08:19
jyuso1anteaya: yes08:19
anteayawonderful, great work08:19
anteayajyuso1: are you currently at the point you consider to be your goal?08:19
jyuso1anteaya: Now it's just Nova.but we'll add more CI08:19
anteayajyuso1: what else do you want to test?08:20
*** oomichi has joined #openstack-meeting08:20
jyuso1anteaya: yes.I'm trying to test sr-iov ci now.08:20
anteayaah okay08:21
anteayahow is that coming along?08:21
*** shengjiemin has quit IRC08:21
anteayaso is what you are testing now PCI?08:21
*** yingjun has quit IRC08:21
jyuso1anteaya: I'm stiil confused about multi node CI testing.08:21
anteayajyuso1: yes I can understand that08:22
anteayawhat part are you confused about?08:22
anteayait is a challenging topic08:22
anteayaand we don't have all the pieces in place ourselves08:22
*** wojdev is now known as wojdev_08:22
anteayawhat are you experiencing08:22
jyuso1anteaya: about how to depoly and test..08:22
anteayawhat do you want to do?08:23
*** wojdev has joined #openstack-meeting08:23
*** wojdev has quit IRC08:23
*** aranjan has quit IRC08:23
anteayathen I can better understand how to help08:23
*** _nadya_ has joined #openstack-meeting08:23
jyuso1anteaya: you know I can deploy openstack on single node.It's a project in Jenkins08:24
*** irenab has quit IRC08:24
anteayayou can deploy openstack on a single node yes08:24
anteayathat is our most common use case08:24
jyuso1anteaya: But how could i deploy other "nova-compute"and"openvswitch agent" on the other node in same Jenkins project.08:26
anteayabut multinode is tricky08:26
anteayaright08:26
jyuso1anteaya: may be I should build 2 jenkins project08:26
anteayathat part is difficult08:26
jyuso1anteaya: after project 1 is complete and then trigger project 2?08:26
anteayawell we do have a scenario we are working on to have two nodes available for the same test08:26
anteayabut we havent' got the entire process worked out yet08:27
*** yingjun has joined #openstack-meeting08:27
anteayajyuso1: joe gordon, jogo, is working on that08:27
jyuso1anteaya: can i juse puppet in CI project?08:27
anteayawell it is the creation of the second vm that the inital vm knows about that is the issue08:27
*** dims has joined #openstack-meeting08:28
anteayathat is the structure we are working on creating08:28
*** _nadya_ has quit IRC08:28
anteayaand having quite figured out how to do that08:28
anteayajyuso1: I think that heyongli has talked to jogo in the past08:28
*** shengjiemin has joined #openstack-meeting08:28
*** ijw has joined #openstack-meeting08:29
*** phil__ has joined #openstack-meeting08:29
anteayaI think it might be worthwhile talking to jogo about setting up multinode testing08:29
jyuso1anteaya: oh,may be i should ask him about the detail:)08:29
jyuso1anteaya: thanks08:29
anteayajyuso1: I think that would be a good place to begin08:29
anteayayou might be able to help him accomplish his goal08:29
heyonglianteaya,  we don't cover 2 node testing yet, but let us see what will happen while we setting up SRIOV env.08:29
anteayahello heyongli08:30
anteayaright08:30
anteayaif you need two vms for your test, best to start by talking to jogo08:30
anteayaso that you can make use of what he has accomplished in this area08:30
jyuso1anteaya: may be it is a little different.our test is not based on VM.08:31
heyonglianteaya, we beyond 2 vms, we need two 2 host and 2 vm.08:31
jyuso1anteaya: it is based on physical machine.08:31
anteayaheyongli: oh, two hosts08:31
anteayayes needing two hosts is different from what we are working on08:31
anteayajyuso1: ah yes, so basing it on a physical machine is different08:31
*** moha_hunt has joined #openstack-meeting08:31
anteayaall of our testing is virtual08:31
anteayaso we are in new territory again08:32
jyuso1anteaya: yes.so that's why i just want to know could i use puppet to deploy in CI.:)08:32
anteayaI'm not sure what to say08:32
*** achanda has quit IRC08:32
*** dims has quit IRC08:32
anteayajyuso1: by all means, if you can use puppet to accomplish your task do so08:33
anteayajust know that what you are doing is not like what anyone else has tried to do before08:33
anteayato the best of my knowledge08:33
anteayaso you will hit a lot of obstacles08:33
*** alexpilotti has quit IRC08:33
jyuso1anteaya: yes.that's true.08:34
anteayaand I won't have many answers for you, except to say keep trying08:34
*** jgallard_ has joined #openstack-meeting08:34
anteayaokay yes, use any tool that you think will accomplish the task08:34
jyuso1anteaya: thanks:)08:34
*** ijw has quit IRC08:34
anteayajyuso1: :)08:34
anteayaso keep us posted on your progress08:34
heyonglianteaya,  sure.08:35
anteayaas we are interested in learning what you discover08:35
anteayaheyongli: thank you08:35
*** ijw has joined #openstack-meeting08:35
anteayaso right now, you are testing all nova patches, correct?08:35
anteayaand you are commenting on the patches in gerrit?08:35
heyonglianteaya, you help me a lot , actually08:35
anteayaheyongli: thank you :)08:35
heyongliyes, anteaya08:35
anteayaheyongli: now the tests you are running08:36
anteayaare they the pci tests?08:36
*** suro_ has joined #openstack-meeting08:36
heyonglianteaya, yes, pci tests, let me post you the test cases link08:36
anteayathank you08:36
heyonglihttps://github.com/intel-hw-ci/Intel-Openstack-Hardware-CI/tree/master/pci_testcases08:37
*** gokrokve has joined #openstack-meeting08:37
*** Guest77071 is now known as doron_afk08:37
anteaya#link https://github.com/intel-hw-ci/Intel-Openstack-Hardware-CI/tree/master/pci_testcases08:37
anteayaheyongli: wonderful thank you08:37
anteayawe were talking today about having access to the tests people are running08:38
anteayathanks for sharing the test code08:38
anteaya:)08:38
*** doron_afk is now known as Guest7707108:38
anteayaand you have a link in your log index page08:38
heyongliyes08:38
anteayathat is wonderful08:38
anteayayay08:39
anteayaso you are working on the sr-iov testing now08:39
*** irenab has joined #openstack-meeting08:40
*** MaxV has joined #openstack-meeting08:40
*** Fdot has joined #openstack-meeting08:41
anteayaso did you have anythign you wanted to talk about with me?08:41
*** Guest77071 is now known as doron_afk08:41
anteayawe had talked about your system today during the nova mid-cycle which started today08:41
anteayawhich is why I had all my questions08:41
*** doron_afk is now known as Guest7707108:41
*** gokrokve has quit IRC08:42
*** spandhe has joined #openstack-meeting08:42
*** jlanoux has joined #openstack-meeting08:42
*** suro_ has quit IRC08:42
*** bvandenh has joined #openstack-meeting08:42
*** watanabe_isao has quit IRC08:43
jyuso1anteaya: I think I don't have more question.thanks:)08:43
heyonglianteaya, i know yunhong talk with you , yay08:44
heyonglii have no more share today,08:44
*** sergef has quit IRC08:44
*** wojdev has joined #openstack-meeting08:46
heyonglii had to leave for other work today, anteaya08:46
anteayajyuso1: great thank you08:46
anteayaheyongli: yes he did08:46
anteayaheyongli: it was nice to meet him08:46
anteayaheyongli: thank you08:46
heyonglithank you too, anteaya , bye08:46
anteayaheyongli: bye08:46
*** jcoufal has joined #openstack-meeting08:48
*** jlibosva has joined #openstack-meeting08:49
anteayaI just sent an email to adrian08:49
*** wojdev has quit IRC08:49
anteayato let him know that having him attend the weekly telco meeting would be helpful08:49
*** wojdev has joined #openstack-meeting08:49
*** wojdev has quit IRC08:50
*** wojdev has joined #openstack-meeting08:51
*** achanda has joined #openstack-meeting08:51
*** doude_ has joined #openstack-meeting08:52
*** doude_ has quit IRC08:52
*** doude has quit IRC08:52
*** doude has joined #openstack-meeting08:53
anteayawell heyongli is gone to work and jyuso1 doesnt' have any more questions08:55
anteayaand noone else has made their presence known08:55
anteayaso I am going to end this meeting08:55
anteayathanks to all for attending08:56
anteaya#endmeeting08:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:56
openstackMeeting ended Tue Jan 27 08:56:13 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-01-27-08.00.html08:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-01-27-08.00.txt08:56
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-01-27-08.00.log.html08:56
anteayafour minutes until the nova-net to neutron migration meeting08:56
*** zz_ttrifonow is now known as ttrifonov08:56
spandheanteaya: going through the spec, so it seems we dont plan to do a fully live migration.. right? both the APIs are read-only during DB migration step08:59
*** irenab has quit IRC09:00
anteayaspandhe: let's get your question logged in the meeting09:00
anteayaspandhe: hold on a second09:00
jlibosvahello09:00
obondarevo/09:00
anteaya#startmeeting nova-net-to-neutron-migration09:00
openstackMeeting started Tue Jan 27 09:00:35 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: nova-net-to-neutron-migration)"09:00
openstackThe meeting name has been set to 'nova_net_to_neutron_migration'09:00
anteayajlibosva: hello09:00
spandhehello!09:00
anteayahi obondarev09:00
*** irenab has joined #openstack-meeting09:00
*** markvoelker has joined #openstack-meeting09:00
anteayathis is spandhe09:00
obondarevanteaya: hi09:01
*** otter768 has joined #openstack-meeting09:01
anteayaI met her today and she works with yahoo's deployment09:01
anteayaso she is attending today's meeting09:01
anteayaanyone else here for the migration meeting?09:01
obondarevgreat!09:01
spandheHi obondarev !09:01
anteayagus: you here?09:01
obondarevspandhe: nice to meet you :)09:01
anteayabelmoreira: ping09:01
anteayalet's look at today's agenda09:02
anteaya#link https://wiki.openstack.org/wiki/Meetings/Nova-nettoNeutronMigration09:02
spandheobondarev: I have tried your earlier patch in Yahoo (with few changes) and have tested out successful live migration. I am trying to see thr new approach now.09:02
belmoreirahi, I'm late...09:02
anteayabelmoreira: welcome09:02
anteayaspandhe: let's follow our agenda09:02
anteayaspandhe: then we can have a chance to discuss09:03
obondarevspandhe: cool!09:03
spandheanteaya: ok..09:03
anteaya#topic he state of the Neutron spec (obondarev)09:03
*** openstack changes topic to "he state of the Neutron spec (obondarev) (Meeting topic: nova-net-to-neutron-migration)"09:03
anteayaspandhe: thanks09:03
anteayaso the specs first09:03
anteayaobondarev: take it away09:03
obondarevso for the specs09:03
obondarevjust saw an activity on the specs this morning09:03
anteaya\o/09:03
obondarevmost probably related to the discussion at nova midcycle09:03
*** fzdarsky|afk has joined #openstack-meeting09:03
anteayait was yes09:03
obondarevgus has uploaded new revisions on the specs so he probably knows more than me :)09:03
anteayagus: pingity ping ping09:04
obondarevI'm going to go through them and left comments, if any09:04
anteayaobondarev: wonderful thank you09:04
obondarevanteaya: are you at the midcycle?09:04
anteayaobondarev: I am, I am only there tomorrow morning and then I have to leave for the cinder mid-cycle09:05
anteayathe two overlap09:05
*** markvoelker has quit IRC09:05
obondarevanteaya: ok, great!09:05
anteayaso we discussed the specs today09:05
anteayaand there is agreement to solve the simplest use case, as we have been working to do09:05
*** otter768 has quit IRC09:05
*** yapeng has joined #openstack-meeting09:06
anteayaand I would really like to get at least the first part of the two part spec merged this week09:06
*** ygbo has joined #openstack-meeting09:06
anteayaso that is this patch09:06
anteaya#link https://review.openstack.org/#/c/147723/409:06
anteayaI think we are close09:06
anteayaso if folks can review that then hopefully we can get that polished and finished this week09:06
anteayathat is my goal09:07
obondarevanteaya: is Salvatore at the midcycle as well?09:07
anteayaobondarev: he was there today09:07
anteayaand then had to go to vmware meetings09:07
obondarevI'm asking because one of the comments from Salvatore was his concern on whether we need a proxy in nova at all.09:07
anteayahopefully he will be there tomorrow before I leave09:07
obondarevAs I started to work on it I'd really like this concerns to be sorted asap :)09:07
anteayaobondarev: yes, I saw that09:07
anteayaobondarev: yes09:07
*** xuhanp has quit IRC09:08
anteayaobondarev: can you submit your code to gerrit, so folks can look at it?09:08
obondarevgood to know he's there09:08
anteayahe is, yes09:08
anteayaI was happy to see him09:08
obondarevyeah. I'll try to put a WIP on gerrit this week09:08
obondarevhopefully this will be something that makes sense and not a complete waste of reviewers time09:08
anteayacan you do that today please?09:08
anteayaanything is a start09:08
anteayait is frustrating for me to tell people there will be code and there is no code09:08
obondarevnot sure for today09:09
anteayajust submit what you have09:09
anteayait doesn't have to be perfect09:09
anteayabut anything is better than nothing09:09
obondarevyeah, I know, I'll try09:09
anteayait really holds up discussions when folks have nothing to look at09:09
anteayathank you09:09
anteayaand progress on the second patch of the spec hinges on folks being able to see code09:10
anteayaso we need to have some code to make any progress on https://review.openstack.org/#/c/142456/ in a meaningful way09:10
anteaya#link https://review.openstack.org/#/c/142456/09:10
*** yapeng has quit IRC09:10
anteayaobondarev: seeing what you have written may answer some of salv-orlando's concerns09:11
obondarevanteaya: I see09:11
*** tomoe has quit IRC09:11
*** rajeshr has joined #openstack-meeting09:11
anteayaobondarev: thanks, so anything you have is great09:11
anteayaif folks make you feel unhappy for putting something up in wip state, then let me know09:11
anteayasince you should be supported by showing unfinished coce09:12
anteayacode09:12
anteayaand if you don't, I will address it09:12
obondarevthanks anteaya09:12
anteayathank you09:12
anteayaobondarev: and yes, I want your efforts to be valued, not wasted09:12
obondarevanteaya: appreciate that :)09:13
anteayaso without gus, I'm not sure what else we need to talk about regarding the specs09:13
anteayaobondarev: :)09:13
*** e0ne has quit IRC09:13
anteayadoes anyone else have anything for specs?09:13
jlibosvanope09:13
anteayaor shall we move on?09:13
anteayaokay great, please review them as soon as you are able09:13
anteayamoving on09:13
*** irenab has quit IRC09:14
anteaya#topic the state of implementation (obondarev)09:14
*** openstack changes topic to "the state of implementation (obondarev) (Meeting topic: nova-net-to-neutron-migration)"09:14
obondarevso we already started to talk a bit about implementation I guess09:14
*** irenab has joined #openstack-meeting09:14
obondarevwill try to put a wip on proxy asap09:14
anteayathank you09:15
obondarevI see jlibosva has progress on his DB migration patch09:15
obondarevjlibosva: can you please update?09:15
anteaya#link https://review.openstack.org/#/c/148260/09:15
jlibosvaI'm gonna send new PS soon. I'm rewriting the code structure to be more declarative09:15
anteayajlibosva: great thank you09:15
*** zz_avozza is now known as avozza09:15
obondarevjlibosva: thanks09:15
jlibosvaevery neutron table has its own definition how the table should be populated09:16
jlibosvacurrently I'm in state of getting ports and fixed/floating ips populated and that's the last part09:16
jlibosvaso ETA this week I think prototype should be ready09:16
obondarevjlibosva: perfect!09:16
anteayajlibosva: wonderful work, thank you09:16
belmoreirajlibosva: great09:17
anteayaspandhe: did you have any more comments for obondarev?09:17
*** daneyon has quit IRC09:17
spandheanteaya: I have questions about the previous spec.. mostly because I wasnt involed earlier.. I can talk to him later too...09:17
*** daneyon has joined #openstack-meeting09:18
anteayaspandhe: doens't hurt to ask now09:18
anteayasince this is logged it would be helpful to ask09:18
obondarevspandhe: you mean juo spec, right?09:18
obondarevjuno*09:18
spandheanteaya: ok cool.. obondarev, have questions on kilo specs09:18
obondarevspandhe: ah, ok09:19
*** wojdev has quit IRC09:19
spandheare we not planning to do a live migration? I thought you kind of achieved that in Juno spec.. or at least we did using that code09:19
spandheseems like both the APIs are down during the db migration period.09:19
*** aranjan has joined #openstack-meeting09:20
spandheIs my understanding correct?09:20
obondarevspandhe: right, the first iteration does not include live migration09:20
*** yamamoto_ has quit IRC09:20
obondarevspandhe: but API are partially down09:20
obondarevspandhe: Nova API is down during only initial db migration09:21
obondarevspandhe: then it's up again09:21
spandheobondarev: ok.. whats initial db migration? Also, once the db is migrated, where do new VMs come up? in nova-net land or neutron land?09:21
obondarevspandhe: so after the db migration the source of thruth will be in neutron db09:22
obondarevtruth*09:22
spandheobondarev: ok.. and nova is the active API and the calls are proxied to neutron API, am I right?09:23
*** andreykurilin_ has joined #openstack-meeting09:23
*** derekh has joined #openstack-meeting09:23
obondarevspandhe: nova is the active API, calls are operated by nova-network which will go for data to neutron DB09:24
obondarevspandhe: using special proxy in nova09:24
*** achanda has quit IRC09:24
*** irenab has quit IRC09:25
spandheobondarev: ok thanks.. I am not sure what this special proxy is.. does it help nova in accessing neutron DB? because usually nova user wont have acess to neutron db..09:25
*** tnurlygayanov has joined #openstack-meeting09:25
obondarevyep, it does, it should go to neutron to get data09:26
*** irenab has joined #openstack-meeting09:26
obondarevafter that we can start The big migration loop09:26
spandheobondarev: ok.. thanks! I got the gist now.. I can review the specs and the db migration script..09:26
obondarevspandhe: great! thank you!09:27
anteayaspandhe: thanks for asking09:27
anteayaso implementation09:27
anteayadoes anyone have anything more on implementation?09:27
jlibosvanope09:27
*** erikmoe has quit IRC09:27
obondarevnot from me09:27
spandheanteaya: thanks for giving me the opportunity :)09:28
anteayaspandhe: glad to have your participation09:28
anteayaokay moving on09:28
anteaya#topic documentation09:28
*** openstack changes topic to "documentation (Meeting topic: nova-net-to-neutron-migration)"09:28
anteayaobondarev: you did your part here, thank you09:28
* gus apologises for arriving late.09:28
obondarevnot much to update on the docs side09:28
anteayayes09:28
anteayaactually let's go back09:28
anteaya#undo09:28
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x1ffd090>09:29
*** stannie has joined #openstack-meeting09:29
anteayagus: hello09:29
anteayagus: anything to share in the specs/implementation topics?09:29
*** paragan has quit IRC09:30
gusI put up a new revision a few hours ago that addresses all the comments so far.09:30
*** wojdev_ has joined #openstack-meeting09:30
anteayagus: yes thank you09:30
gusIn particular, it now says that we won't deal with cells in this spec, but we expect that to be a followup.09:30
*** achanda has joined #openstack-meeting09:30
*** erikmoe has joined #openstack-meeting09:30
jlibosvagus: i.e. in L cycle?09:31
anteayabelmoreira: we talked this morning about that09:31
anteayabelmoreira: and understanding that to move forward we need to focus on the simplest use case09:31
*** achanda has quit IRC09:31
anteayabut I am talking with alaski who is one of the authors of cells09:31
*** wojdev_ is now known as wojdev09:32
anteayaand working on figuring out what we can do for your situation, belmoreira09:32
*** paragan has joined #openstack-meeting09:32
gusjlibosva: It's possible, but I doubt it.  It will need some more discussion/involvement from interested parties to make sure we do it in a way that is most useful, and we'll need some much better testing environments than we typically have available (devstack won't cut it).09:32
belmoreiraanteaya: thank you09:32
anteayawhether it is within this initiative or outside it09:32
anteayabelmoreira: we are thinking of you, by all means09:32
*** wojdev has quit IRC09:32
*** yingjun has quit IRC09:32
anteayawe just need to figure out how to keep the migration path moving forward as well, as it has stalled in teh past09:33
jlibosvagus: makes sense. thanks09:33
anteayaso in short, the spec is saying simplest use case09:33
anteayawe are providing some tools which we invite deployers to take and expand to fit their needs09:33
anteayafolks who work with us and have specific needs, such as cern and cells, we will work with to find a path forward09:34
anteayabut that won't make everyone happy09:34
anteayaso we are telling folks that we know that09:34
anteayato set reasonable expectations09:34
*** Guest77071 is now known as doron_afk09:35
anteayamake sense?09:35
belmoreiraanteaya: I think is very reasonable09:35
spandhetotally09:35
anteayabelmoreira: thank you09:35
anteayaspandhe: great thank you09:35
anteayagus: thanks for your input09:35
anteayaany more now that gus is here?09:36
anteayaor back to documentation?09:36
*** irenab has quit IRC09:36
anteayamoving on09:36
anteaya#topic documentation09:36
*** openstack changes topic to "documentation (Meeting topic: nova-net-to-neutron-migration)"09:36
anteayaback again09:36
*** irenab has joined #openstack-meeting09:36
anteayaso obondarev thank you here, emagma has said he will lead this09:36
anteayathe difficulty is the meeting time, which I don't expect him ever to make09:37
obondarevanteaya: awesome!09:37
jlibosvaanteaya: where is he located?09:37
anteayaI get up in the middle of the night but I don't expect others from north america to do so09:37
obondarevanteaya: indeed, we talked about it with him too09:37
jlibosvaah09:37
*** gokrokve has joined #openstack-meeting09:37
anteayajlibosva: in texas I think09:37
anteayaand I got an email from somone named chris cannon who also said he wants to help09:37
anteayawhich is awesome but he is in north america as well09:38
obondarevanteaya: so if we can have an alternate time for this meeting that would be good I think09:38
obondarevjust like we have for neutron team meeting09:38
anteayaso I'm sill looking for somone to attend meetings09:38
anteayaobondarev: I'd like to avoid that acutally09:38
anteayaas disruption in the meeting time reduces effectiveness for the transition period09:38
obondarevanteaya: I see09:39
anteayathis time works for russia, australia and eu09:39
*** pelix has joined #openstack-meeting09:39
anteayawhich is why I picked it09:39
*** gokrokve_ has joined #openstack-meeting09:39
anteayalet's just proceed and hope someone from docs is able to attend meetings09:39
obondarevanteaya: should we find a compromise then?09:39
anteayaobondarev: do you want to ping emagma and ask him what he needs to get started on the docs process?09:39
anteayaI think just ensuring somone talks to emagma is our best way forward09:40
anteayaobondarev: if you would do that, that would be great09:40
obondarevanteaya: agree09:40
obondarevanteaya: sure I can09:40
anteayagreat, thank you09:40
anteayaanything more for docs?09:40
anteaya#topic testing (belmoreira)09:40
*** openstack changes topic to "testing (belmoreira) (Meeting topic: nova-net-to-neutron-migration)"09:40
anteayabelmoreira: anything to say here?09:41
belmoreiraAs ops point of view for now I don't have nothing09:41
anteayaokay great09:41
anteayaI'll proceed09:41
jlibosvaI have something to discuss/think about09:41
anteayaoh okay, jlibosva go ahead09:41
*** gokrokve has quit IRC09:41
jlibosvaDo we plan to test particular tools?09:42
anteayagood question09:42
anteayalet me share something09:42
jlibosvaas I was working with db things, I think some real big bunch of data would be helpful09:42
anteayajlibosva: ah I see09:42
anteayajlibosva: well mikal and jhesketh do test data09:42
anteayawith their db datasets ci09:42
anteayajlibosva: so it might be possible to chat with jhesketh to see how they work with real data09:43
jlibosvaanteaya: is it the turbo-hipster or something else?09:43
anteayaand utilize their approach if possible09:43
anteayaturbo-hipster09:43
jlibosvaok, I'll try to reach out to him09:43
anteayawhich has the name db datasets ci09:43
anteayajlibosva: thank you, I think that would be a good first step09:44
*** irenab has quit IRC09:44
anteayaand at the nova midcycle we discussed testing09:44
jlibosvaanteaya: ok, thank you too for the info09:44
*** gokrokve_ has quit IRC09:44
anteayajlibosva: sure09:44
gusmikal is at nova midcycle, jhesketh is still here in .au if you want me to ask him tomorrow.09:44
anteayaand one suggestion is to package up the tools and let deployers test them09:44
anteayaand incorporate feedback09:44
gus(I feel bad I have no idea how my colleagues' tool works)09:45
anteayagus: yes thank you that would be awesome09:45
anteayagus: ha ha ha09:45
guswill do.09:45
anteayaworking in -infra I had to get over that long ago09:45
anteaya:)09:45
anteayaso belmoreira you mentioned this morning/yesterday to me that you could test the db migration and proxy once you see some code09:46
*** irenab has joined #openstack-meeting09:46
anteayabelmoreira: yes?09:46
*** che-arne|2 has joined #openstack-meeting09:46
anteayaspandhe: would you be able to do the same?09:46
belmoreirathe proxy it will be easier to test09:46
*** che-arne|2 has quit IRC09:47
anteayabelmoreira: great, I'll take what I can get09:47
gustesting is going to be awkward generally for this project, given that the usual devstack/grenade tests aren't so useful (multi-node devstack testing isn't quite ready yet).09:47
spandheanteaya: yup..09:47
anteayaspandhe: great thank you09:47
belmoreiradata migration, I'm still checking how can we do it09:47
anteayagus: yes, I think we are going to have to stumble through testing until we reach a happy place amoungst ourselves09:47
*** che-arne has quit IRC09:47
anteayabelmoreira: great, well don't keep your findings a secret09:47
*** irenab has quit IRC09:48
anteayabelmoreira: once you learn anything, do share so we can figure out how to get the support to make it happen09:48
*** imsurit has joined #openstack-meeting09:48
anteayagus: and yes multi-node did come up today09:48
belmoreiraanteaya: sure09:48
anteayagus: which we are working on but yes, isn't there yet09:48
anteayabelmoreira: thank you09:49
anteayaso for testing, basically we have to have some code and then try some things and share what we tried and keep going until we decide it is good enough09:49
anteayawhich isn't great for satisfying the spec, but I don't know what else to suggest at this point09:49
*** kayaliu_ has joined #openstack-meeting09:50
*** irenab has joined #openstack-meeting09:50
* jhesketh is here09:50
*** yamamoto has joined #openstack-meeting09:50
anteayahello jhesketh09:50
jhesketh(trying to catchup on context)09:50
anteayajhesketh: the tl;dr is we would like your input on testing data migrations09:50
anteayajhesketh: you being the turbo-hipster dude, we were hoping you might have some wisdom to share09:51
jheskethtl;dr answer would be it's worth doing09:51
anteayajhesketh: that is good09:51
*** kaisers has quit IRC09:51
anteayaand worth knowing thank you09:51
jheskethnot necessarily as a 3rd party CI, but at the very least before you upgrade so you know how long it'll take09:51
guswant to be able to test a db migration tool on largish amounts of data.  wondering what your experience is re getting access to that, privacy, etc.09:51
jheskethturbo-hipster is designed in ways to make it difficult to get data out, I did a talk on that at the summit09:52
jheskethlet me find a link09:52
* jlibosva remembers the talk from Atlanta09:52
jheskethhttps://www.youtube.com/watch?v=VeoUpmPim8c09:52
jheskethoh, well, not much has changed09:52
*** kayaliu_ has quit IRC09:52
anteaya#link https://www.youtube.com/watch?v=VeoUpmPim8c09:53
anteayaso jlibosva perhaps you can watch/re-watch that video and follow up with jhesketh if you have questions?09:54
anteayaand of course, anyone else as well09:54
*** aranjan has quit IRC09:54
anteayajhesketh: thank you09:54
gusif we have large nova-net volunteers, then we could set up a similar 3rd party CI migration test.  We have the additional complication that verifying the neutron version matches the nova-net version is itself an interesting exercise.09:54
jlibosvajhesketh: I reserve a slot in your time schedule :)09:55
anteayatrue09:55
anteayaso we have more to discuss on the testing front09:55
anteayalet's all keep that in mind as we move forward and bring questions and comments to next week's meeting09:55
anteayafair?09:55
guswe should be able to do a round trip: migration tool -> nova-neutron-proxy -> back to something that matches the same nova API.09:55
jlibosvaI have still question, how to validate neutron db is correct09:56
anteayajlibosva: ah, another good question09:56
anteayagus: that sound reasonable09:56
jlibosvaspecifically vif migrations09:56
guswe'll need additional testing from the neutron pov however.09:56
*** marcelodieder has joined #openstack-meeting09:56
anteayahmmmm, more thought needed here09:57
*** hichihara has quit IRC09:57
anteayacan we capture these thoughts, questions in the spec comments at all?09:57
jlibosvaack09:57
anteaya#link https://review.openstack.org/#/c/142456/09:57
gusjlibosva: I can't think of any magic answers here - I think we'll just need to add the usual unittests to cover cases we foresee while writing the code as best we can.09:57
*** avozza is now known as zz_avozza09:57
*** zz_avozza is now known as avozza09:57
anteayagus: yes, let's start with what we can do and expand from there09:58
jlibosvagus: I don't think UT would be useful here as it validates implementation. We're more interesting in making sure the actual mapping between two databases is correct. The implementation is not that crucial09:58
anteayajlibosva: is there anyone else doing what you think needs to be done?09:59
anteayacan we copy a current effort at all?09:59
anteayatime to wrap up09:59
gusjlibosva: Agreed.  I don't know how to do that without writing some other new code that will be based on the same possibly incorrect assumptions however :/09:59
anteayalet's comment in the testing section of https://review.openstack.org/#/c/142456/8/specs/kilo/migration-from-nova-net.rst10:00
jlibosvayeah10:00
anteayaand talk more about testing next week10:00
jlibosvaanteaya: I was just thinking loud, I'll try to bring it to specs10:00
anteayaplease review the latest spec10:00
anteayajlibosva: of course, and thank you10:00
anteaya:)10:00
anteayagreat meeting everyone, thank you!10:00
anteayasee you next week10:00
gusyep, suggest things for the spec and I'll attempt to merge them.10:00
anteaya#endmeeting10:00
jlibosvathanks, bye10:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"10:00
*** doron_afk has quit IRC10:01
gusthanks all.10:01
openstackMeeting ended Tue Jan 27 10:00:58 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_net_to_neutron_migration/2015/nova_net_to_neutron_migration.2015-01-27-09.00.html10:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_net_to_neutron_migration/2015/nova_net_to_neutron_migration.2015-01-27-09.00.txt10:01
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_net_to_neutron_migration/2015/nova_net_to_neutron_migration.2015-01-27-09.00.log.html10:01
anteayathank you10:01
obondarevthanks! by!e10:01
belmoreirathanks10:01
*** markvoelker has joined #openstack-meeting10:01
*** salv-orlando has quit IRC10:02
spandhethanks! bye!10:02
jheskethjlibosva: sure, just ping me with any q's :-)10:02
*** salv-orlando has joined #openstack-meeting10:02
*** doron_afk has joined #openstack-meeting10:02
*** irenab has quit IRC10:02
*** dguitarbite has joined #openstack-meeting10:03
*** dguitarbite has joined #openstack-meeting10:03
*** yamamoto has quit IRC10:05
*** spandhe has quit IRC10:05
*** neeti has quit IRC10:06
*** irenab has joined #openstack-meeting10:06
*** markvoelker has quit IRC10:07
*** epico has quit IRC10:08
*** irenab has quit IRC10:09
*** pkoniszewski has quit IRC10:11
*** irenab has joined #openstack-meeting10:12
*** irenab has quit IRC10:13
*** marcelodieder has quit IRC10:13
*** irenab has joined #openstack-meeting10:16
*** dims has joined #openstack-meeting10:16
*** ChrisPriceAB has joined #openstack-meeting10:17
*** irenab has quit IRC10:17
*** irenab has joined #openstack-meeting10:20
*** haomaiwang has quit IRC10:21
*** dims has quit IRC10:21
*** erikmoe has quit IRC10:22
*** dguitarbite has quit IRC10:24
*** dguitarbite has joined #openstack-meeting10:24
*** matrohon has quit IRC10:25
*** derekh has quit IRC10:26
*** marcelodieder has joined #openstack-meeting10:27
*** derekh has joined #openstack-meeting10:27
*** anish_ has quit IRC10:28
*** theanalyst has quit IRC10:32
*** theanalyst has joined #openstack-meeting10:34
*** oanufriev has joined #openstack-meeting10:34
*** gokrokve has joined #openstack-meeting10:37
*** anish_ has joined #openstack-meeting10:39
*** _nadya_ has joined #openstack-meeting10:40
*** yingjun has joined #openstack-meeting10:40
*** irenab has quit IRC10:42
*** gokrokve has quit IRC10:42
*** rajeshr has quit IRC10:44
*** irenab has joined #openstack-meeting10:44
*** e0ne has joined #openstack-meeting10:47
*** irenab has quit IRC10:47
*** shengjiemin has quit IRC10:48
*** jtomasek has joined #openstack-meeting10:48
*** aranjan has joined #openstack-meeting10:50
*** andreykurilin_ has quit IRC10:51
*** andreykurilin_ has joined #openstack-meeting10:51
*** marg7175 has quit IRC10:52
*** bvandenh has quit IRC10:52
*** yapeng has joined #openstack-meeting10:55
*** bvandenh has joined #openstack-meeting10:58
*** evgenyf has quit IRC10:59
*** yapeng has quit IRC10:59
*** otter768 has joined #openstack-meeting11:01
*** yingjun has quit IRC11:03
*** numan has quit IRC11:04
*** yingjun has joined #openstack-meeting11:04
*** avozza is now known as zz_avozza11:05
*** zz_avozza is now known as avozza11:05
*** amakarov_away is now known as amakarov11:06
*** otter768 has quit IRC11:06
*** rajeshr has joined #openstack-meeting11:07
*** marg7175 has joined #openstack-meeting11:07
*** marg7175 has quit IRC11:07
*** marg7175 has joined #openstack-meeting11:08
*** e0ne is now known as e0ne_11:08
*** e0ne_ is now known as e0ne11:09
*** jgallard_ has quit IRC11:09
*** jgallard_ has joined #openstack-meeting11:09
*** tellesnobrega_ has joined #openstack-meeting11:11
*** irenab has joined #openstack-meeting11:13
*** sergef has joined #openstack-meeting11:16
*** tochi has quit IRC11:16
*** jgallard_ has quit IRC11:16
*** irenab has quit IRC11:22
*** aranjan has quit IRC11:23
*** rajeshr has quit IRC11:24
*** rajeshr has joined #openstack-meeting11:29
*** aysyd has joined #openstack-meeting11:30
*** jlanoux_ has joined #openstack-meeting11:31
*** paragan has quit IRC11:33
*** jlanoux has quit IRC11:33
*** andreykurilin_ has quit IRC11:35
*** gokrokve has joined #openstack-meeting11:37
*** anish_ has quit IRC11:38
*** jlanoux has joined #openstack-meeting11:38
*** erikmoe has joined #openstack-meeting11:38
*** irenab has joined #openstack-meeting11:39
*** irenab has quit IRC11:40
*** jlanoux_ has quit IRC11:41
*** gokrokve has quit IRC11:43
*** adalbas has joined #openstack-meeting11:45
*** irenab has joined #openstack-meeting11:46
*** rajeshr has quit IRC11:46
*** irenab has quit IRC11:47
*** irenab has joined #openstack-meeting11:49
*** anish_ has joined #openstack-meeting11:51
*** irenab has quit IRC11:52
*** tellesnobrega_ has quit IRC11:53
*** irenab has joined #openstack-meeting11:53
*** mrmartin has quit IRC11:53
*** irenab has quit IRC11:54
*** shankar has quit IRC11:57
*** irenab has joined #openstack-meeting11:57
*** _nadya_ has quit IRC12:00
*** aysyd has quit IRC12:01
*** erikmoe has quit IRC12:01
*** neeti has joined #openstack-meeting12:03
*** markvoelker has joined #openstack-meeting12:04
*** Mandell has joined #openstack-meeting12:04
*** Mandell has quit IRC12:09
*** markvoelker has quit IRC12:09
*** lazy_prince is now known as killer_prince12:09
*** e0ne is now known as e0ne_12:10
*** mrmartin has joined #openstack-meeting12:12
*** e0ne_ is now known as e0ne12:13
*** sergef has quit IRC12:13
*** irenab has quit IRC12:17
*** asalkeld has quit IRC12:18
*** subscope has quit IRC12:20
*** aranjan has joined #openstack-meeting12:21
*** subscope has joined #openstack-meeting12:29
*** amotoki has quit IRC12:30
*** amotoki has joined #openstack-meeting12:31
*** e0ne is now known as e0ne_12:31
*** achanda has joined #openstack-meeting12:32
*** ajayaa has quit IRC12:32
*** e0ne_ is now known as e0ne12:34
*** amotoki has quit IRC12:35
*** subscope has quit IRC12:35
*** achanda has quit IRC12:36
*** amotoki has joined #openstack-meeting12:37
*** gokrokve has joined #openstack-meeting12:37
*** doron_afk has quit IRC12:38
*** doron_afk has joined #openstack-meeting12:39
*** weshay has joined #openstack-meeting12:41
*** gokrokve has quit IRC12:42
*** baoli has joined #openstack-meeting12:43
*** yapeng has joined #openstack-meeting12:43
*** baoli has quit IRC12:47
*** baoli has joined #openstack-meeting12:47
*** spredzy is now known as spredzy|lunch12:47
*** yapeng has quit IRC12:48
*** _nadya_ has joined #openstack-meeting12:49
*** riwinters has joined #openstack-meeting12:50
*** subscope has joined #openstack-meeting12:51
*** aranjan has quit IRC12:54
*** IanGovett has joined #openstack-meeting12:57
*** anish_ has quit IRC12:57
*** neeti has quit IRC13:02
*** otter768 has joined #openstack-meeting13:02
*** che-arne has joined #openstack-meeting13:03
*** markvoelker has joined #openstack-meeting13:05
*** otter768 has quit IRC13:07
*** ddieterly has joined #openstack-meeting13:07
*** matrohon has joined #openstack-meeting13:09
*** paragan has joined #openstack-meeting13:10
*** paragan has quit IRC13:10
*** paragan has joined #openstack-meeting13:10
*** markvoelker has quit IRC13:10
*** erikmoe has joined #openstack-meeting13:12
*** xuhanp has joined #openstack-meeting13:13
*** fzdarsky|afk is now known as fzdarsky13:15
*** evgenyf has joined #openstack-meeting13:16
*** leifz has quit IRC13:17
*** leifz has joined #openstack-meeting13:20
*** ajayaa has joined #openstack-meeting13:20
*** fnaval has joined #openstack-meeting13:21
*** irenab has joined #openstack-meeting13:22
*** juzuluag has joined #openstack-meeting13:23
*** markvoelker has joined #openstack-meeting13:25
*** Longgeek has joined #openstack-meeting13:26
*** ccrouch has joined #openstack-meeting13:31
*** jungleboyj has quit IRC13:31
*** spredzy|lunch is now known as spredzy13:32
*** alexpilotti has joined #openstack-meeting13:33
*** dprince has joined #openstack-meeting13:34
*** rushiagr is now known as rushiagr_away13:35
*** gokrokve has joined #openstack-meeting13:37
*** vigneshvar has quit IRC13:38
*** Murali has joined #openstack-meeting13:39
*** oomichi has quit IRC13:40
*** rushil has joined #openstack-meeting13:41
*** doude has quit IRC13:41
*** ChrisPriceAB has quit IRC13:41
*** shengjiemin has joined #openstack-meeting13:41
*** doude has joined #openstack-meeting13:41
*** gokrokve has quit IRC13:42
*** bknudson has joined #openstack-meeting13:42
*** cbouch has joined #openstack-meeting13:45
*** yapeng has joined #openstack-meeting13:46
*** gokrokve has joined #openstack-meeting13:47
*** jckasper has joined #openstack-meeting13:48
*** jckasper_ has joined #openstack-meeting13:49
*** aranjan has joined #openstack-meeting13:51
*** dboik_ has joined #openstack-meeting13:51
*** gokrokve has quit IRC13:51
*** prazumovsky has joined #openstack-meeting13:51
*** matrohon has quit IRC13:52
*** jckasper has quit IRC13:52
*** jprovazn has joined #openstack-meeting13:53
*** evgenyf has quit IRC13:53
*** yapeng has quit IRC13:53
*** evgenyf has joined #openstack-meeting13:53
*** sandywalsh has joined #openstack-meeting13:53
*** thomasem has joined #openstack-meeting13:53
*** markvoelker has quit IRC13:54
*** matrohon has joined #openstack-meeting13:54
*** emagana has joined #openstack-meeting13:54
*** thomasem has quit IRC13:54
*** FJB has joined #openstack-meeting13:55
*** thomasem has joined #openstack-meeting13:55
*** irenab has quit IRC13:55
*** matrohon has quit IRC13:55
*** Sukhdev has joined #openstack-meeting13:55
*** matrohon has joined #openstack-meeting13:56
*** ihrachyshka has joined #openstack-meeting13:57
*** bill_az has joined #openstack-meeting13:57
*** rkukura has joined #openstack-meeting13:57
*** rushiagr_away is now known as rushiagr13:58
*** radez_g0n3 is now known as radez13:59
*** mlavalle has joined #openstack-meeting13:59
*** pc_m has joined #openstack-meeting13:59
* anteaya is awake again13:59
mesteryhi13:59
*** tongli has joined #openstack-meeting13:59
roaethi13:59
ihrachyshkao/13:59
mlavallehi13:59
emaganahello!13:59
pc_mhi13:59
rkukurahi13:59
tonglio/14:00
tongliNeutron meeting now?14:00
mesterytongli: yes14:00
russellbo/14:00
HenryG\o14:00
tongli@mestery, cool. thanks.14:00
mesterytongli: Waiting for folks to arrive, will be starting very soon14:00
jlibosvahi14:01
*** matrohon has quit IRC14:01
*** changbl has joined #openstack-meeting14:01
mesterysalv-orlando armax kevinbenton carl_baldwin amotoki dougwig: ping14:01
Sukhdevhello - good morning14:01
*** sergef has joined #openstack-meeting14:01
*** matrohon has joined #openstack-meeting14:02
dougwig Early! :)14:02
roaetquite early14:02
mestery#startmeeting networking14:02
openstackMeeting started Tue Jan 27 14:02:27 2015 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: networking)"14:02
openstackThe meeting name has been set to 'networking'14:02
mestery#link https://wiki.openstack.org/wiki/Network/Meetings Agenda14:02
*** yamahata has joined #openstack-meeting14:03
mesteryThis may be a light meeting today, the main focus I'd like to have is on Kilo-2 work and some time on plugin decomposition14:03
mestery#topic Announcements14:03
*** dhruvdhody has joined #openstack-meeting14:03
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:03
mesteryKilo-2 is in 2 weeks on February 514:03
mestery#link https://wiki.openstack.org/wiki/Kilo_Release_Schedule14:03
mestery#link https://launchpad.net/neutron/+milestone/kilo-214:03
amotokihi14:04
mesteryWe'll spend some time on specific BPs there later in the meeting.14:04
*** lukasa_work has joined #openstack-meeting14:04
*** neelashah has joined #openstack-meeting14:04
mesteryThat's all I had for announcements on the agenda this week. Does anyone have anything else?14:04
mestery#topic Bugs14:05
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:05
*** sean-k-mooney has joined #openstack-meeting14:05
mesteryenikanorov_ enikanorov__: Hi there14:05
enikanorov_mestery: hi14:05
enikanorov_mestery: may we move bugs section to the end of the meeting?14:06
enikanorov_sorry about that14:06
mesteryenikanorov_: Sure! We'll come back to it, no worries.14:06
mestery#topic Docs14:06
*** openstack changes topic to "Docs (Meeting topic: networking)"14:06
mesteryemagana: Hi there!14:06
emaganamestery: hello!14:06
emaganaNetworking guide is going well. We have a legacy implementation14:08
emagana#link https://github.com/ionosphere80/openstack-networking-guide/blob/master/scenario-legacy-ovs/scenario-legacy-ovs.md14:08
mesteryemagana: neat!14:08
emaganaThe idea is to cover what nova-network provides but with overlays network besides VLANs14:08
mesteryemagana: That's a pretty good guide, just scrolling through it now.14:09
emaganaI encourage everybody to provide feedback now on this github account or once it is move to gerrit, which I will provide the link but it is not there yet14:09
*** thomasem has quit IRC14:09
*** rbowen has joined #openstack-meeting14:09
mestery#info Encourage everyone to provide feedback on the networking guide in github for now until it moves to gerrit.14:09
mesteryemagana: Is there a deadline for this feedback?14:10
*** thomasem has joined #openstack-meeting14:10
emaganaJust a reminder for everybody, in order to facilitate the documentation for the people who are not familiar with the Docs tools, this .md format is much more easier to update  ;-)14:10
*** moha_hunt has quit IRC14:10
emaganamestery: No yet! But our target is to complete the guide by mids February14:10
mestery#info Target is to complete networking guide by mid February14:11
mesterythanks emagana!14:11
amotokiemagana: how to feedback? IRC channel? docs ML?14:11
emaganamestery: but I do not think we have a hard deadline. The DVR side has been moving along nicely14:11
ihrachyshkapull requests ;)14:11
mesteryihrachyshka: lol14:11
emaganaamotoki: it depends, if you want to provide changes to the document, just follow the typical git process and you name will be included in the credits of the guide14:12
*** rprakash has joined #openstack-meeting14:12
emaganaif you have few comments, just added directly in git or wait for the official gerrit commit14:12
mesteryamotoki: Do you have plans to present this guide at the Ops Summit in Philly? May be a good idea to get feedback there as well.14:12
mesteryemagana:14:12
mesterySorry. not amotoki :)14:12
emaganamestery: I am planing to attend it but I did not think about present it, good idea! I should!14:13
*** dhruvdhody has quit IRC14:13
mesteryemagana: Yes, would be good to get feedback. Even better if you can get the ops there to collaborate on it ;)14:14
*** dhruvdhody has joined #openstack-meeting14:14
emaganabasicallym you will see all the scenarios that we are covering here:14:14
emagana#link https://github.com/ionosphere80/openstack-networking-guide14:14
mesteryemagana: Looks good14:15
emaganasc68cal is working on a provider network scenario as well  ;-)14:15
emaganamestery: no more from my side!14:15
mesteryemagana: One thing I wanted to bring up was that the LBaaS folks found some issues with docs around LBaaS (dougwig and blogan).14:16
* mestery is looking for the email link14:16
mestery#link http://lists.openstack.org/pipermail/openstack-dev/2015-January/054827.html14:16
mesteryemagana: Just noting it here to keep you aware in case they need help14:16
dougwigthe v2 api docs somehow got released early.  i think a bug got filed, and anne was looking into it.14:16
emaganamestery: we took care of that.. well annegentle did!14:16
mesteryexcellent!14:17
*** ddieterly has quit IRC14:17
*** BrianB_ has joined #openstack-meeting14:17
mesteryOK, anything else on Docs from anyone?14:17
mesteryOK moving on14:18
mestery#topic Plugin Decomposition Status Update14:18
*** openstack changes topic to "Plugin Decomposition Status Update (Meeting topic: networking)"14:18
mesteryI'm happy to see a lot of work going on here! Cheers to those who have already started and are making progress!14:18
*** dhruvdhody has quit IRC14:18
*** ttrifonov is now known as zz_ttrifonov14:19
*** rprakash has quit IRC14:19
mesteryNext week, I'm going to have armax present some stats on where we're at with regards to overall stats of who's started, etc.14:19
mesteryFor now, if anyone has any questions on this, this is a good time to ask for help.14:19
mesteryThe ODL ML2 driver is now fully decomposed, as well as the midokura driver.14:19
mesterySukhdev: How is the Arista driver coming along?14:19
Sukhdevmestery: I am very close14:20
mesterySukhdev: Excellent!14:20
*** rprakash has joined #openstack-meeting14:20
*** dhruvdhody has joined #openstack-meeting14:20
Sukhdevarmax has been helping with UT issue14:20
mesteryKudos to armax for working long hours in helping people over the past few weeks.14:20
ihrachyshkaspeaking of arista, we should consider bug fixes that were discussed recently for review on master to be able to backport14:20
Sukhdevihrachyshka, mestery : I added an item to the agenda to discuss this14:21
mesterySukhdev: Lets discuss that here maybe? Seems to fit right in.14:21
Sukhdevmestery: sounds good14:21
sean-k-mooneyare there currently any example of how to import the ml2 mechisium driver into neutron? ie the in tree part14:21
Sukhdevso, here is the issue -14:22
*** sambetts has joined #openstack-meeting14:22
mesterysean-k-mooney: We'll come back to that, hold on for a minute.14:22
SukhdevWhile we are working on decomp work, we have patches that need backports14:22
Sukhdevihrachyshka: wrote a very good summary describing the issue and solutions14:22
ihrachyshkahasn't https://review.openstack.org/148745 clarified the process for backports and doesn't it say that we should allow bug fixes to go into master even during spin-off?14:22
mesteryihrachyshka: ++, that's the link I was looking for14:23
*** salv-orlando has quit IRC14:23
Sukhdevihrachyshka: correct - but, I still see the patches blocked14:23
mestery#link https://review.openstack.org/14874514:23
*** salv-orlando has joined #openstack-meeting14:23
mesterySukhdev: We should unblock them then. Do you have the links?14:23
ihrachyshkaSukhdev, that's why I encourage people to unblock reviews and proceed with them :)14:23
mesteryihrachyshka: When reviewing these on stable, lets make sure to include https://review.openstack.org/148745 in the review.14:23
Sukhdevyes - give me a sec14:23
*** Longgeek has quit IRC14:23
Sukhdevhttps://review.openstack.org/#/c/147976/14:24
*** aranjan has quit IRC14:24
Sukhdevhttps://review.openstack.org/#/c/148369/14:24
Sukhdevthose are the two14:24
mesteryThanks Sukhdev14:25
*** rbowen has quit IRC14:25
*** dane_leblanc has quit IRC14:25
Sukhdevjuno stable deadline is in few days - if cores can get these approved - then ihrachyshka can help me get them backported14:25
mesterySukhdev: I'll work with armax and ihrachyshka to unblock these for you.14:25
Sukhdevmestery: Thank you so much14:26
*** spzala has joined #openstack-meeting14:27
*** cference has joined #openstack-meeting14:27
mesterysean-k-mooney: You had a question as well now around importing?14:27
emaganaSukhdev: I was reviewing on of them, let me know if you need  one more reviewer  ;-)14:27
dougwigmestery: ping me if you need an extra reviewer on those.14:27
*** noslzzp has joined #openstack-meeting14:27
Sukhdevemagana: thanks - I will ping you14:27
mesterydougwig: Please go ahead now if you want, we need armax on the second one but the first one is open.14:27
sean-k-mooneyyes when the dirver is split out. is there an example of the in tree part that import an ml2 mechisium dirver14:27
*** amitgandhinz has joined #openstack-meeting14:28
mesterysean-k-mooney: Yes, let me grab a link.14:28
mestery#link https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/mechanism_odl.py14:28
dougwigsean-k-mooney: neutron/plugins/ml2/drivers/mechanism_odl.py14:28
sean-k-mooneymestery: thanks14:28
mesterysean-k-mooney: ^^^ Like that?14:28
mesteryOK, anything else on plugin decomposition?14:29
*** dane_leblanc has joined #openstack-meeting14:29
Sukhdevmestery: I have one on ODL- decomp14:29
mesterySukhdev: Please go ahead14:30
*** VW_ has joined #openstack-meeting14:30
SukhdevI notice networking_old is not registered for import  - is it by design?14:30
rprakashHi prakash here can any one tell me if I want to develop anew plugin for ONOS, which one shall I pick to start for a BP14:31
SukhdevIn other words, I can not do sudo python install networking_odl14:31
mesterySukhdev: Yes, you have to manually pull it and install it now, we haven't pushed a release to pypi yet14:31
rprakashor can I add ONOS to ODL like OZC2ODL does?14:31
mesteryrprakash: For a new plugin/driver, you need to file a wishlist bug and keep a thin shim in neutron, the rest needs to be somewhere else.14:31
Sukhdevbut, that is a requirement, right? we all have to do it?14:31
dougwigwell, you could in theory do "pip install -e git+{url}" straight from github, right?14:32
mesteryrprakash: http://specs.openstack.org/openstack/neutron-specs/specs/kilo/core-vendor-decomposition.html14:32
mesteryrprakash: That has instructions14:32
mesterydougwig: Yes14:32
mesterySukhdev: Right14:32
*** carl_baldwin has joined #openstack-meeting14:32
rkukuradane_leblanc: Does the Cisco MD decomposition depend on https://blueprints.launchpad.net/neutron/+spec/ml2-hierarchical-port-binding?14:32
rprakashthanks will follow the link thanks14:32
mesteryrprakash: Once you've looked at that one, please find myself or armax in #openstack-neutron with questions.14:33
dane_leblancrkukura: No, the first pass of decomp should be on the current upstream Nexus plugin, that doesn't have hierarchical port binding14:33
rkukuradane_leblanc: Thanks.14:33
*** dims has joined #openstack-meeting14:33
rprakashThanks will connect back to team14:34
dane_leblancrkukura: But Arvind's work will depend on hierarchical port binding.14:34
mesteryrprakash: Great!14:34
sean-k-mooneymestery: may i ask one more question regarding the import. is there a requirement file that specifies which verion of the networking_odl libary your are importing.14:34
mesterysean-k-mooney: There is not, we haven't released networking-odl yet, so it's just using current master from git.14:35
sean-k-mooneyok thanks that makes sense14:35
mesterysean-k-mooney: Excellent!14:36
*** markvoelker has joined #openstack-meeting14:36
*** yingjun has quit IRC14:37
Sukhdevmestery: I am confused - what do you mean by you OLD has not been released?14:37
*** gokrokve has joined #openstack-meeting14:37
SukhdevAren't people using it?14:37
mesterySukhdev: We haven't released it on pypi yet.14:37
mesteryMeaning, a released version.14:37
mesterySukhdev: It's "released" in that it's public, but there is no version 0.1 released yet :)14:38
Sukhdevmestery: But, if someone wants to install from (say devstack) without requirements.txt file, how does devstack know what to pull?14:38
mesterySukhdev: The ODL devstack work will pull networking-odl itself.14:39
mesterySukhdev: Due to the pluggable devstack work, we have to pull that out of devstack and make it pluggable, which we're doing now.14:39
*** yamahata has quit IRC14:39
dougwigyou could also put FOO=$(pip install git+blah) into your local.conf in the right section.14:39
Sukhdevmestery: Oh so, for Arista MD, do I have to modify the devstack as well?14:39
Sukhdevmestery: I thought if I added requiremnts.txt file, that will do the trick, no?14:40
mesterySukhdev: There are a few ways around this, dougwig proposed another one right there :)14:40
*** mattgriffin has joined #openstack-meeting14:40
mesterySukhdev: That would do it too, but we didn't want to add that into requirements.txt for all these new external sources.14:40
mesteryarmax documented that in the spec and I believe there was a discussion on that earlier as well.14:40
mesterySukhdev: Lets circle back with armax when he's online for that one.14:40
*** marcelodieder has quit IRC14:40
Sukhdevmestery: I am using what dougwig proposed - but, I do not believe it is a scalable and long term solution, no?14:41
Sukhdevmestery: I agree - I will bring it up with armax14:41
mesterySukhdev: Correct14:41
*** gokrokve has quit IRC14:42
mesteryGreat discussions here!14:42
dougwigit scales fine, it's just not terribly user friendly or allowing of self-discovery, which i'm guessing is what you meant.14:42
*** topol has joined #openstack-meeting14:42
Sukhdevdougwig: that is what I meant - sorry :-)14:42
mesteryWe'll leave this spot in the agenda going forward so each week we can work with people who are decomposing their plugins and have questions.14:42
mesteryBut lets move on now.14:42
mestery#topic nova-network to neutron migration14:43
*** openstack changes topic to "nova-network to neutron migration (Meeting topic: networking)"14:43
mesteryanteaya: Hi!14:43
anteayao/14:43
anteayaso we are meeting14:43
anteaya#link http://eavesdrop.openstack.org/meetings/nova_net_to_neutron_migration/14:43
mesteryCool!14:43
anteayaand we have a spec which is a two parter14:43
anteayahere is part one14:43
anteaya#link https://review.openstack.org/#/c/147723/14:43
anteayawe are getting close14:43
mesteryAwesome!14:44
anteayabasically this patch sets expectations of the users of the migration work14:44
*** erikmoe has quit IRC14:44
anteayaone thing that was clear yesterday at the nova mid-cycle is that we need deployers to know that if they are holding out for a push button solution, they will be disappointed14:44
anteayathis was captured in the community impact section of the latest patchset14:44
anteayaI really would like to push for getting this first patch merged by the end of this week14:45
*** rbak__ has quit IRC14:45
anteayathe child patch to this includes the migration path and nova folks want to see some proof of concept code before they sign off on the spce14:45
anteayawhich is fair14:45
mesteryanteaya: Makes sense14:46
anteayajlibosva has a db migration wip patch up14:46
*** VW_ has quit IRC14:46
anteayaand obondarev has told me he will get a wip proxy patch up on gerrit soon14:46
anteayathere is some resistance here, mostly I feel due to his concern about putting up something in wip14:46
anteayabut others need to see the work to be able to offer opinons14:46
anteayaso obondarev heard my concerns and will put something up14:47
*** VW_ has joined #openstack-meeting14:47
anteayaI assured him he would feel supported in doing so14:47
*** AmirBaleghi_ has quit IRC14:47
mesteryanteaya: I love the wording in the "Community Impact" section of gus's spec, nicely done.14:47
anteayaemagana has said he will lead the docs effort14:47
anteayamestery: thanks14:47
anteayaone of the issues is we still don't have anyone doing docs who can attend meetings14:47
anteayaso would be great to have someone here to help emagana14:48
*** gokrokve has joined #openstack-meeting14:48
anteayasomeone named chris emailed me to say he wants to help with docs14:48
anteayaspeak up if you are on irc chris14:48
anteayaalso the cells issue while not in scope for the migration work14:48
anteayais still an issue for cern14:48
anteayaI am talking with alaski to see what we can do here14:49
anteayaand he has told me he would really like a point person in neutron to understand cells impact14:49
*** david-lyle_afk is now known as david-lyle14:49
anteayathe problem being that neutron doesn't talk cells so nova cells users can't use neutron14:49
mesterycern uses cells? Talk about living on the edge ;)14:49
anteayaso we need to address this gap14:49
anteayacern uses cells14:49
mesterycool14:49
ajoyes, they do14:50
emaganaanteaya: it will be great to have someone else because I can't attend the IRC meetings, are too early for me14:50
anteayacells do two things I understand, load balance the scheduler and isolate against failure14:50
*** johnma has joined #openstack-meeting14:50
anteayaso we need to find a neutron person willing to work with alaski on this gap14:50
anteayaemagana: yes Understood14:50
mesteryanteaya: Thanks for the update here.14:50
anteayaemagana: obondarev said he would work with you this week on getting started on docs here14:50
mesteryThere is one more item I'd like to hit on the agenda in a few minutes here yet.14:51
* anteaya stops14:51
*** gokrokve_ has joined #openstack-meeting14:51
anteayathanks14:51
enikanorov_mestery: bugs? ;)14:51
mesteryanteaya: Thanks for the great update here! I encourage folks to attend the migration meetings and work with anteaya.14:51
mesteryenikanorov_: Two items I guess :)14:51
*** jecarey has joined #openstack-meeting14:51
mesteryenikanorov_: You did ask to go last today :P14:51
anteayathank you, and to all who particiapte14:51
*** ndipanov has quit IRC14:51
enikanorov_haha :)14:51
enikanorov_yep14:51
mestery#topic Client Extensibility14:51
*** openstack changes topic to "Client Extensibility (Meeting topic: networking)"14:51
mesteryroaet: You're up :)14:51
roaeto/14:51
roaetI'll go fast.14:52
roaetThis is in regard to the client extensibility bp14:52
mestery#link https://blueprints.launchpad.net/python-neutronclient/+spec/extensible-neutronclient14:52
roaetWe have a change here: https://review.openstack.org/#/c/148318/14:52
mestery#link https://review.openstack.org/#/c/148318/14:52
roaetIt currently only supports shell extensions and models after the nova client extensions14:52
*** ndipanov has joined #openstack-meeting14:52
mesteryamotoki: I'd really like you to review this closely, as you're our most prolofic client reviewer14:52
roaetThis adds 'commands' and what not to the client. Work can be done to add 'commands' to the library if needed.14:52
ajomestery, roaet , looking into the future, shouldn't that work be done in the openstack-sdk14:53
ajo?14:53
amotokiroaet: will look at it14:53
mesteryajo: That's a good point, although roaet's work solves their problem for the current :)14:53
roaetajo: ^14:53
*** gokrokve has quit IRC14:53
ajosure, but may be they want to implement extension mechanism there too, or will face the same problem sooner or later :)14:54
mesteryajo: Valid point. roaet, I'd encourage you to look there too.14:54
roaetajo: absolutely. I'm guessing that'd be a part of the library aforementioned library portion.14:54
amotokiperhaps we need to explore both ways (openstack-sdk/openstackclient and existing neutronclient)14:54
mesteryAlso, I encourage folks to review what roaet has here in the client. amotoki, I'll sync with you on this as well.14:54
* dougwig notes an eery similarity between neutronclient/openstackclient and nova-network/neutron14:54
amotokibut I can't say more because I haven't look into the detail yet.14:54
mesteryOK, thanks roaet !14:54
roaetthanks14:54
mesteryLets leave 5 minutes for bugs, there is a meeting right after this one so we have to end on time :)14:55
mestery#topic Bugs14:55
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:55
mesteryenikanorov_: Hi!14:55
ajo:D14:55
enikanorov_hi14:55
enikanorov_:)14:55
enikanorov_here's a short list of bugs to discuss14:55
mesteryI guess we get to highlight only a few bugs today ;)14:55
enikanorov_https://bugs.launchpad.net/neutron/+bug/141481214:55
russellbrelated to bugs, this patch fixes hyper-v (sorry)  https://review.openstack.org/#/c/150373/14:55
*** jcoufal_ has joined #openstack-meeting14:55
enikanorov_hmm, does bot work?14:55
mesteryMaybe it's busted :)14:55
*** AmirBaleghi has joined #openstack-meeting14:56
enikanorov_ok, this one is related to dvr-job, armax is handling it14:56
*** banix has joined #openstack-meeting14:56
mesteryenikanorov_: It's in the queue I think14:56
russellbyep14:56
enikanorov_second one  "Delete subnet can fail for SLAAC/DHCP_STATELESS with 409" https://bugs.launchpad.net/neutron/+bug/141419914:56
enikanorov_with a patch on review from salv-orlando14:56
*** smillward has quit IRC14:57
enikanorov_back to https://bugs.launchpad.net/neutron/+bug/1382064 - "Failure to allocate tunnel id when creating networks concurrently"14:57
*** sigmavirus24_awa is now known as sigmavirus2414:57
enikanorov_we tried to fix that with changing transaction isolation level14:57
enikanorov_which created more issues that solved14:57
enikanorov_so now there's another patch on review, that employes retry approach similar to nova's14:57
enikanorov_russellb: welcome to review the patch14:58
*** jcoufal has quit IRC14:58
*** lxsli0 has joined #openstack-meeting14:58
enikanorov_russellb: btw, i've rebased your patch on default api_workers on that fix14:58
russellbyeah saw that, thanks14:58
ihrachyshkawith my red hat on, I'd like folks to consider https://bugs.launchpad.net/neutron/+bug/1413042 since currently neutron/kilo is broken on centos7/rhel714:58
enikanorov_https://review.openstack.org/#/c/14926114:58
enikanorov_finally, https://bugs.launchpad.net/neutron/+bug/1411816 - "DB failure during functional job run"14:59
*** ChrisPriceAB has joined #openstack-meeting14:59
enikanorov_that one was fixed by a revert of one of previous commits (tx isolation level change)14:59
*** etoews has joined #openstack-meeting14:59
enikanorov_but it revealed the issue with functional DB tests14:59
enikanorov_which worth to be fixed15:00
mesteryOK, we're at time now I think.15:00
enikanorov_aaand that's it15:00
mesteryenikanorov_: Thanks for the updates on bugs!15:00
markvoelkerOne last thing: don't forget to wish mestery a happy birthday today everybody! https://www.youtube.com/watch?v=2ImgF-gesXE15:00
mesteryI encourage folks to jump into #openstack-neutron to continue15:00
mesterymarkvoelker: lol :)15:00
*** pc_m has left #openstack-meeting15:00
mesteryWe'll see you all next week!15:00
mestery#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Tue Jan 27 15:00:41 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
enikanorov_markvoelker: now you made us look like we've forgotten!15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-01-27-14.02.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-01-27-14.02.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-01-27-14.02.log.html15:00
enikanorov_:)15:00
russellbha @ happy birthday metal15:00
mesteryenikanorov_: :P15:00
rkukuramestery: OK if we retarget https://blueprints.launchpad.net/neutron/+spec/ml2-hierarchical-port-binding for kilo-2 now that the 1st patch merged and matrohon and I figured out why the 2nd broke the DVR tempest tests?15:01
mesterylol15:01
mesteryrkukura: Lets sync with armax on that, can you start ML thread?15:01
rkukuramestery: sure15:01
rkukuramestery: I’ll pull you and armax into an existing thread15:01
rkukuraand the ML15:02
mesteryrkukura: Ack, thanks!15:02
*** margaret__ has joined #openstack-meeting15:02
*** fnaval has quit IRC15:02
*** dhruvdhody has quit IRC15:02
*** markvoelker has quit IRC15:03
*** etoews has joined #openstack-meeting15:03
*** rkukura has left #openstack-meeting15:03
*** markvoelker has joined #openstack-meeting15:03
*** BharatK has quit IRC15:03
*** otter768 has joined #openstack-meeting15:03
*** rwsu-afk has quit IRC15:04
lxsli0anyone here for a scheduler meeting?15:04
*** rbak has joined #openstack-meeting15:05
*** sean-k-mooney has left #openstack-meeting15:05
*** amitgandhinz has quit IRC15:06
*** diga has joined #openstack-meeting15:07
*** ayoung_ZZzz__ is now known as ayoung_snowedin15:07
*** otter768 has quit IRC15:08
*** mlavalle has left #openstack-meeting15:08
*** markvoelker has quit IRC15:09
*** berendt has quit IRC15:09
*** shengjiemin has quit IRC15:10
*** coolsvap is now known as coolsvap|afk15:10
*** salv-orlando has quit IRC15:11
*** emagana has quit IRC15:13
*** emagana has joined #openstack-meeting15:13
*** msdubov_ has joined #openstack-meeting15:14
*** avozza is now known as zz_avozza15:17
*** emagana has quit IRC15:17
*** zz_avozza is now known as avozza15:17
*** dsetia has joined #openstack-meeting15:18
*** sambetts has left #openstack-meeting15:18
*** jhenner has quit IRC15:19
*** AmirBaleghi has quit IRC15:19
*** jhenner has joined #openstack-meeting15:19
*** vijendar has joined #openstack-meeting15:20
*** dims has quit IRC15:20
*** carl_baldwin has quit IRC15:20
*** dims has joined #openstack-meeting15:20
*** aranjan has joined #openstack-meeting15:21
*** shengjiemin has joined #openstack-meeting15:21
*** marcelodieder has joined #openstack-meeting15:22
*** Mandell has joined #openstack-meeting15:22
*** Murali has quit IRC15:23
*** jnrao has joined #openstack-meeting15:23
*** dims has quit IRC15:25
*** yeungp has joined #openstack-meeting15:26
*** kebray has joined #openstack-meeting15:26
*** kebray has quit IRC15:26
*** AmirBaleghi has joined #openstack-meeting15:27
*** kebray has joined #openstack-meeting15:27
*** lukasa_work has left #openstack-meeting15:28
*** fnaval has joined #openstack-meeting15:28
*** neelashah has quit IRC15:28
*** jungleboyj has joined #openstack-meeting15:28
*** yeungp1 has joined #openstack-meeting15:29
*** yeungp has quit IRC15:29
*** ebalduf has joined #openstack-meeting15:29
*** fnaval has quit IRC15:32
*** fnaval has joined #openstack-meeting15:32
*** fnaval has quit IRC15:33
*** zehicle_ has quit IRC15:34
*** xuhanp has quit IRC15:38
*** liusheng has quit IRC15:39
*** liusheng has joined #openstack-meeting15:39
*** evgenyf has quit IRC15:39
*** nelsnelson has joined #openstack-meeting15:39
*** fnaval has joined #openstack-meeting15:40
*** e0ne is now known as e0ne_15:41
*** rwsu has joined #openstack-meeting15:42
*** yapeng has joined #openstack-meeting15:42
*** neelashah has joined #openstack-meeting15:42
*** Sukhdev has quit IRC15:42
*** hemna has joined #openstack-meeting15:43
*** zz_jgrimm is now known as jgrimm15:43
*** kurtmartin has joined #openstack-meeting15:44
*** ddecapit has joined #openstack-meeting15:44
*** markvoelker has joined #openstack-meeting15:46
*** yapeng has quit IRC15:47
*** stevemar has joined #openstack-meeting15:47
*** jhenner has quit IRC15:48
*** nellysmitt has quit IRC15:49
*** FJB has quit IRC15:49
*** ddieterly has joined #openstack-meeting15:49
*** e0ne_ has quit IRC15:51
*** annegent_ has joined #openstack-meeting15:52
*** andreaf_ has quit IRC15:53
*** andreaf_ has joined #openstack-meeting15:53
*** thomasem has quit IRC15:54
*** aranjan has quit IRC15:54
*** nellysmitt has joined #openstack-meeting15:54
*** pradipta is now known as pradipta_away15:55
*** irenab has joined #openstack-meeting15:55
*** stanley5 has joined #openstack-meeting15:56
*** msdubov_ has quit IRC15:56
*** msdubov_ has joined #openstack-meeting15:56
*** stanley5 has quit IRC15:57
*** IanGovett has quit IRC15:57
*** jaypipes has joined #openstack-meeting15:57
*** AlanClark has joined #openstack-meeting15:58
*** thomasem has joined #openstack-meeting15:58
*** IanGovett has joined #openstack-meeting15:58
*** jlibosva has quit IRC15:59
*** nealph_afk is now known as nealph15:59
*** lxsli0 has quit IRC15:59
*** amitgandhinz has joined #openstack-meeting15:59
*** evgenyf has joined #openstack-meeting16:00
*** spzala has quit IRC16:01
*** mrmartin has quit IRC16:03
*** jlibosva has joined #openstack-meeting16:03
*** ildikov has quit IRC16:03
*** SridharG has left #openstack-meeting16:04
*** salv-orlando has joined #openstack-meeting16:05
*** johnma has quit IRC16:07
*** j05h has joined #openstack-meeting16:08
*** salv-orlando has quit IRC16:09
*** Mandell has quit IRC16:10
*** baoli has quit IRC16:10
*** jecarey_ has joined #openstack-meeting16:10
*** jhenner has joined #openstack-meeting16:11
*** mattgrif_ has joined #openstack-meeting16:11
*** sandywalsh_ has joined #openstack-meeting16:11
*** carl_baldwin has joined #openstack-meeting16:11
*** aranjan has joined #openstack-meeting16:12
*** varora- has joined #openstack-meeting16:12
*** thomasem has quit IRC16:13
*** dannywilson has joined #openstack-meeting16:14
*** timrc_ has joined #openstack-meeting16:14
*** msdubov_ has quit IRC16:15
*** jhenner has quit IRC16:15
*** dannywilson has quit IRC16:15
*** dannywilson has joined #openstack-meeting16:15
*** armax has joined #openstack-meeting16:16
*** rakhmerov__ has joined #openstack-meeting16:16
*** rakhmerov has quit IRC16:16
*** aranjan has quit IRC16:16
*** akuznetsova_ has joined #openstack-meeting16:16
*** ildikov has joined #openstack-meeting16:17
*** e0ne has joined #openstack-meeting16:17
*** sandywalsh has quit IRC16:17
*** mattgriffin has quit IRC16:17
*** bdpayne has joined #openstack-meeting16:17
*** varora has quit IRC16:18
*** torgomatic has quit IRC16:18
*** jecarey has quit IRC16:18
*** timrc has quit IRC16:18
*** clarkb has quit IRC16:18
*** cdub has quit IRC16:18
*** akuznetsova has quit IRC16:18
*** cdub has joined #openstack-meeting16:18
*** coolsvap|afk is now known as coolsvap16:18
*** jprovazn has quit IRC16:18
*** msdubov_ has joined #openstack-meeting16:18
*** carl_baldwin has quit IRC16:18
*** ogelbukh has quit IRC16:18
*** torgomatic has joined #openstack-meeting16:18
*** thomasem has joined #openstack-meeting16:19
*** clarkb has joined #openstack-meeting16:19
*** carl_baldwin has joined #openstack-meeting16:19
*** ctlaugh has quit IRC16:19
*** Murali has joined #openstack-meeting16:20
*** ctlaugh has joined #openstack-meeting16:21
*** ogelbukh has joined #openstack-meeting16:21
*** jaypipes has quit IRC16:21
*** imsurit has quit IRC16:21
*** jgravel has joined #openstack-meeting16:24
*** ociuhandu has joined #openstack-meeting16:25
*** ociuhandu has left #openstack-meeting16:25
*** jgravel has left #openstack-meeting16:25
*** rakhmerov__ is now known as rakhmerov16:25
*** matrohon has quit IRC16:26
*** 17WAA14VW has joined #openstack-meeting16:27
*** peekay is now known as pradk16:28
*** prazumovsky has quit IRC16:29
*** kurtmartin has quit IRC16:29
*** jdurgin1 has joined #openstack-meeting16:31
*** daneyon has quit IRC16:31
*** 17WAA14VW is now known as dims16:33
*** Riddhi has joined #openstack-meeting16:33
*** avozza is now known as zz_avozza16:36
*** baoli has joined #openstack-meeting16:38
*** jlibosva has quit IRC16:38
*** salv-orlando has joined #openstack-meeting16:39
*** mattgrif_ has quit IRC16:39
*** spzala has joined #openstack-meeting16:39
*** emagana has joined #openstack-meeting16:39
*** unicell has quit IRC16:40
*** e0ne is now known as e0ne_16:41
*** jlibosva has joined #openstack-meeting16:42
*** dhruvdhody has joined #openstack-meeting16:42
*** scheuran has quit IRC16:43
*** hemna has quit IRC16:44
*** shengjiemin has quit IRC16:46
*** ildikov has quit IRC16:47
*** evgenyf has quit IRC16:47
*** balajiiyer has joined #openstack-meeting16:47
*** irenab has quit IRC16:48
*** bdpayne has quit IRC16:48
*** jlanoux has quit IRC16:49
*** alexpilotti has quit IRC16:49
*** irenab has joined #openstack-meeting16:49
*** ihrachyshka has quit IRC16:51
*** evgenyf has joined #openstack-meeting16:51
*** e0ne_ has quit IRC16:51
*** mattgriffin has joined #openstack-meeting16:52
*** nellysmitt has quit IRC16:52
*** rwsu_ has joined #openstack-meeting16:53
*** eghobo has joined #openstack-meeting16:53
*** comay has joined #openstack-meeting16:53
*** rwsu has quit IRC16:53
*** emagana has quit IRC16:54
*** emagana has joined #openstack-meeting16:54
*** noelbk has joined #openstack-meeting16:54
*** amaretskiy has joined #openstack-meeting16:54
*** dhruvdhody has quit IRC16:55
*** emagana_ has joined #openstack-meeting16:56
*** e0ne has joined #openstack-meeting16:56
*** emagana has quit IRC16:56
*** rvasilets has joined #openstack-meeting16:57
*** Leonr has joined #openstack-meeting16:58
*** alop has joined #openstack-meeting16:59
*** pboldin has joined #openstack-meeting16:59
*** psd has joined #openstack-meeting17:00
*** notmyname has quit IRC17:00
*** bdpayne has joined #openstack-meeting17:00
msdubov_#startmeeting Rally17:00
openstackMeeting started Tue Jan 27 17:00:39 2015 UTC and is due to finish in 60 minutes.  The chair is msdubov_. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: Rally)"17:00
openstackThe meeting name has been set to 'rally'17:00
msdubov_andreykurilin: amaretskiy: aarefiev: jlk: oanufriev: paboldin: pboldin: redixin: rvasilets: Hi17:00
pboldinjo17:00
amaretskiyhi17:00
*** zz_avozza is now known as avozza17:01
aarefievhi17:01
oanufrievhi17:01
*** emagana_ has quit IRC17:01
*** diga has quit IRC17:01
rvasiletshi17:01
msdubov_Let's start17:01
*** aysyd has joined #openstack-meeting17:01
msdubov_#topic Rally release17:01
*** openstack changes topic to "Rally release (Meeting topic: Rally)"17:01
msdubov_So great news guys17:01
*** notmyname has joined #openstack-meeting17:01
*** balajiiyer has left #openstack-meeting17:01
msdubov_Rally now has its first release: https://pypi.python.org/pypi/rally/0.0.117:01
msdubov_0.0.117:01
*** [1]evgenyf has joined #openstack-meeting17:02
*** liusheng has quit IRC17:02
pboldin(cheers)17:02
msdubov_(beer)17:02
*** e0ne_ has joined #openstack-meeting17:02
msdubov_Okay let's move further17:03
*** liusheng has joined #openstack-meeting17:03
*** banix has quit IRC17:03
msdubov_So we are still working on several things that were planned for the 0.0.1 release17:03
msdubov_Let's talk about them17:03
*** phil__ has quit IRC17:03
msdubov_#topic Python 3.4 support17:04
*** openstack changes topic to "Python 3.4 support (Meeting topic: Rally)"17:04
*** rwsu_ is now known as rwsu17:04
msdubov_andreykurilin: How are things going with your patch?17:04
*** otter768 has joined #openstack-meeting17:04
msdubov_andreykurilin: (Hope you are here)17:04
*** evgenyf has quit IRC17:04
*** sigmavirus24 is now known as sigmavirus24_awa17:05
*** sigmavirus24_awa is now known as sigmavirus2417:05
*** e0ne has quit IRC17:06
msdubov_Okay seems like Andrey is not here, so let me give the link to the patch which is going to add Python 3 support: https://review.openstack.org/#/c/148763/17:06
msdubov_It makes the gate-rally-python34 finish in SUCCESS (!)17:06
msdubov_but for some reason fails other jobs17:07
msdubov_So that's now under investigation of andreykurilin17:07
msdubov_#topic Rally API17:07
*** openstack changes topic to "Rally API (Meeting topic: Rally)"17:07
*** jlk has joined #openstack-meeting17:07
msdubov_Another nice thing is the refactoring of rally.api: https://review.openstack.org/149597 https://review.openstack.org/15046817:07
msdubov_Now we are going to use classes with classmethods instead of just methods17:08
*** obondarev has quit IRC17:08
msdubov_Also we are going to unify namings etc.17:08
msdubov_This is what I'm currently working on and I hope it will be merged soon17:08
msdubov_Note that the old API methods are going to be deprecated17:08
*** [1]evgenyf has quit IRC17:08
*** spzala_ has joined #openstack-meeting17:09
*** liusheng has quit IRC17:09
*** otter768 has quit IRC17:09
msdubov_#topic New context classes in Rally17:09
*** openstack changes topic to "New context classes in Rally (Meeting topic: Rally)"17:09
msdubov_pboldin, Could you please tell us a bit about your work?17:09
*** hemna has joined #openstack-meeting17:09
*** rm_work is now known as rm_work|away17:10
pboldinmsdubov_, i'm currently preparing a set of patches for utilities17:10
*** paragan has quit IRC17:10
*** liusheng has joined #openstack-meeting17:10
*** bdpayne has quit IRC17:10
*** BharatK has joined #openstack-meeting17:10
*** bdpayne has joined #openstack-meeting17:10
pboldinmsdubov_: these were separated from the big patch so it is easier to review and merge them17:10
*** aepifanov has quit IRC17:10
*** ajo has quit IRC17:10
msdubov_pboldin:Yep, and what's the functionality they introduce?17:11
pboldinmsdubov_: regarding the `benchmark_image` context there is still discussions going on17:11
*** zz_johnthetubagu is now known as johnthetubaguy17:11
pboldinmsdubov_: one of them is for fixing the informativity of the TimeoutException17:11
*** evgenyf has joined #openstack-meeting17:11
*** sarob has joined #openstack-meeting17:11
pboldinmsdubov_: one another is to create secgroup/keypairs for admin user as well (needed by following patches)17:11
*** spzala has quit IRC17:12
*** spzala_ is now known as spzala17:12
pboldinmsdubov_: third one introduces an eat-all-exceptions context that is to be used in following code as well17:12
pboldinmsdubov_: em17:12
msdubov_pboldin: Sees like that this third context is a nice idea17:12
msdubov_pboldin: Thanks!17:12
*** MarkAtwood has joined #openstack-meeting17:13
msdubov_#topic HTML reports for functional tests17:13
*** openstack changes topic to "HTML reports for functional tests (Meeting topic: Rally)"17:13
msdubov_oanufriev: Any progress on HTML reports in functional tests?17:13
oanufrievno17:14
oanufrievthere is no review of boris_4217:14
*** MaxV has quit IRC17:14
oanufrieveom17:14
*** pboldin1 has joined #openstack-meeting17:15
*** pboldin has quit IRC17:15
msdubov_oanufriev: I also saw another patch from you considering validation, what is it doing?17:15
*** ildikov has joined #openstack-meeting17:16
oanufrievIt's WIP now. The idea is not to create Task db record during validation of task config file17:16
*** doron_afk has quit IRC17:16
oanufrievso, we could say that "This is refactoring of task verification"17:17
oanufrieveom17:17
*** msdubov_ has quit IRC17:17
*** msdubov_ has joined #openstack-meeting17:17
msdubov_oanufriev: Thanks.17:17
*** pboldin1 has quit IRC17:19
*** annegent_ has quit IRC17:19
msdubov_#topic Quotas.neutron_update scenario17:20
*** openstack changes topic to "Quotas.neutron_update scenario (Meeting topic: Rally)"17:20
msdubov_rvasilets: So AFAIK this is the patch you are currently working on - how is the progress there?17:20
*** shashankhegde has joined #openstack-meeting17:20
*** marun has joined #openstack-meeting17:21
*** dboik_ has quit IRC17:21
rvasiletsAs I thing I have finished working on it17:21
rvasiletsAll nits by code was solved17:22
*** ygbo has quit IRC17:22
rvasiletsjenkins says +1)17:22
*** liusheng has quit IRC17:22
rvasiletsI have tested it on devstack17:22
rvasiletsit's working17:22
rvasiletseom17:22
*** aranjan has joined #openstack-meeting17:22
*** liusheng has joined #openstack-meeting17:23
msdubov_rvasilets: Nice! Will review it17:23
rvasiletsThx17:23
msdubov_#topic PostgreSQL support in Rally17:23
*** openstack changes topic to "PostgreSQL support in Rally (Meeting topic: Rally)"17:23
*** rmoe has quit IRC17:23
msdubov_redixin is not here17:24
msdubov_he's made a patch that fixes a couple of postgres-related bugs: https://review.openstack.org/#/c/148907/17:24
*** breton has joined #openstack-meeting17:25
msdubov_and now Rally supports it17:25
msdubov_Another great news actually17:25
*** aranjan has quit IRC17:27
msdubov_#topic Fix in Cinder nested snapshots scenario17:27
*** openstack changes topic to "Fix in Cinder nested snapshots scenario (Meeting topic: Rally)"17:27
msdubov_aarefiev: Hi!17:27
aarefievhi17:27
*** atiwari has joined #openstack-meeting17:27
msdubov_aarefiev: Could you please tell us what was the problem and how you fixed it?17:27
aarefievthere was a problem with deleting order17:27
*** gokrokve_ has quit IRC17:28
aarefievwe try to delete snapshot with related volume17:28
*** thedodd has joined #openstack-meeting17:28
aarefievi fixed it with change deleting order17:28
*** vigneshvar has joined #openstack-meeting17:29
aarefieveom17:29
msdubov_aarefiev: Thanks for the fix!17:29
msdubov_#topic Free discussion17:29
*** openstack changes topic to "Free discussion (Meeting topic: Rally)"17:29
*** baoli has quit IRC17:29
*** auld has quit IRC17:29
aarefievmsdubov_: np17:30
amaretskiyJust to note: I'm currently working on new chart in html report17:30
msdubov_andreykurilin: amaretskiy: aarefiev: jlk: oanufriev: paboldin: pboldin: redixin: rvasilets: Guys I'm exhausted for new topics for today :) Anything to discuss?17:30
amaretskiythis chart is about iterations in parallel17:30
amaretskiyeom17:30
msdubov_amaretskiy: Oh great17:30
rvasiletsNo17:30
*** jaypipes has joined #openstack-meeting17:30
msdubov_amaretskiy: Thanks17:30
*** yapeng has joined #openstack-meeting17:31
msdubov_amaretskiy: Can you provide us with a link so we can see how it looks like?17:32
*** jtomasek has quit IRC17:32
amaretskiyhttp://logs.openstack.org/14/146814/4/check/gate-rally-dsvm-rally/5400cc8/rally-plot/results.html.gz#/SaharaNodeGroupTemplates.create_delete_node_group_templates/overview17:32
amaretskiythis is WIP17:32
amaretskiyi believe today;s patch set will be  good17:33
*** pboldin has joined #openstack-meeting17:33
msdubov_amaretskiy: Great!17:33
*** sahid has quit IRC17:33
*** Murali has quit IRC17:33
msdubov_andreykurilin: amaretskiy: aarefiev: jlk: oanufriev: paboldin: pboldin: redixin: rvasilets: So I believe we can finish our meeting17:34
oanufrievsure17:34
*** belliott has quit IRC17:34
msdubov_oanufriev: =)17:34
rvasiletsAgree17:34
msdubov_#endmeeting17:34
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:34
openstackMeeting ended Tue Jan 27 17:34:30 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:34
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-01-27-17.00.html17:34
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-01-27-17.00.txt17:34
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2015/rally.2015-01-27-17.00.log.html17:34
*** oanufriev has quit IRC17:34
*** msdubov_ has quit IRC17:35
*** kurtmartin has joined #openstack-meeting17:35
*** eghobo has quit IRC17:35
*** yapeng has quit IRC17:36
*** belliott has joined #openstack-meeting17:36
*** dboik has joined #openstack-meeting17:36
*** aranjan has joined #openstack-meeting17:37
*** jcoufal_ has quit IRC17:37
*** rushiagr is now known as rushiagr_away17:40
*** fzdarsky has quit IRC17:41
*** rmoe has joined #openstack-meeting17:41
*** johnthetubaguy is now known as zz_johnthetubagu17:41
*** suro_ has joined #openstack-meeting17:42
*** dprince has quit IRC17:43
*** eghobo has joined #openstack-meeting17:44
*** belmoreira has quit IRC17:44
*** gokrokve has joined #openstack-meeting17:44
*** MarkAtwood has quit IRC17:44
*** vigneshvar has quit IRC17:45
*** leeantho has joined #openstack-meeting17:45
*** lhcheng has joined #openstack-meeting17:45
*** shashankhegde has quit IRC17:46
*** jdurgin1 has quit IRC17:48
*** krykowski has joined #openstack-meeting17:48
*** thumpba has joined #openstack-meeting17:49
*** fzdarsky has joined #openstack-meeting17:49
*** fzdarsky has quit IRC17:49
*** ajo has joined #openstack-meeting17:49
*** safchain has quit IRC17:51
*** krykowski has quit IRC17:51
*** krykowski has joined #openstack-meeting17:51
*** ajayaa is now known as ajayaa_17:52
*** ajayaa_ has quit IRC17:53
-openstackstatus- NOTICE: Gerrit and Zuul will be offline for a few minutes for a security update17:53
*** ajayaa has joined #openstack-meeting17:53
*** evgenyf has quit IRC17:53
*** bdpayne has quit IRC17:54
*** amaretskiy has left #openstack-meeting17:54
*** irenab has quit IRC17:55
*** ayoung_snowedin is now known as ayoung17:55
*** ajayaa has quit IRC17:56
*** auld has joined #openstack-meeting17:56
*** mtanino has joined #openstack-meeting17:56
*** samueldmq has joined #openstack-meeting17:56
*** ajayaa_ has joined #openstack-meeting17:57
*** vigneshvar has joined #openstack-meeting17:57
*** derekh has quit IRC17:58
*** ajayaa_ has quit IRC17:58
*** e0ne_ has quit IRC17:59
*** ajayaa has joined #openstack-meeting17:59
morganfainbergdolphm, ayoung, dstanek, jamielennox, morganfainberg, stevemar, gyee, henrynash, topol, marekd, lbragstad, joesavak, shardy, fabiog, nkinder, lloydm, shrekuma, ksavich, hrybacki, rharwood, grantbow, vdreamarkitex, raildo, rodrigods, amakarov, ajayaa, hogepodge, breton, lhcheng, nonameentername, samueldmq, htruta, amolock https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting17:59
rodrigodso/17:59
dstaneko/17:59
*** henrynash_ has joined #openstack-meeting17:59
jeblairmorganfainberg: hold please17:59
raildoo/17:59
morganfainbergjeblair, sure.17:59
*** ajo has quit IRC17:59
lbragstado/17:59
amakarovo/17:59
bknudsonholding!18:00
stevemaro/18:00
*** banix has joined #openstack-meeting18:00
*** ignacio-scopetta has joined #openstack-meeting18:00
henrynash_hi18:00
*** openstack` has joined #openstack-meeting18:04
samueldmqo/18:04
*** openstack has quit IRC18:04
*** esker has joined #openstack-meeting18:04
jeblairmorganfainberg: try now?18:04
morganfainberg#startmeeting Keystone18:05
openstack`Meeting started Tue Jan 27 18:05:03 2015 UTC and is due to finish in 60 minutes.  The chair is morganfainberg. Information about MeetBot at http://wiki.debian.org/MeetBot.18:05
openstack`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:05
openstack`The meeting name has been set to 'keystone'18:05
*** openstack has joined #openstack-meeting18:05
morganfainberghm, jeblair ^ is that someone camping the name? why openstack is named openstack` ?18:05
*** openstack has quit IRC18:05
*** ivar-lazzaro has joined #openstack-meeting18:05
morganfainberganyway18:05
*** fzdarsky has joined #openstack-meeting18:06
morganfainbergHi! welcome back18:06
morganfainbergpost mid cycle18:06
*** jkremer has joined #openstack-meeting18:06
*** fzdarsky has quit IRC18:06
*** MarkAtwood has joined #openstack-meeting18:06
*** openstack has joined #openstack-meeting18:06
*** openstack is now known as angelamolock18:06
*** openstack` is now known as openstack18:06
*** ChanServ sets mode: +o openstack18:06
angelamolockis that better :)18:06
morganfainbergaha18:06
*** bitblt2 has joined #openstack-meeting18:06
*** harlowja has joined #openstack-meeting18:06
morganfainbergso we have lots of things to go over18:06
*** belliott has left #openstack-meeting18:06
*** s3wong has joined #openstack-meeting18:07
morganfainbergbut for the most part if the patch isn't in gate this week it wont land for k218:07
morganfainbergso review code for BPs and Bugs for this milestone18:07
morganfainberg#link https://launchpad.net/keystone/+milestone/kilo-218:07
morganfainbergso here we go18:07
*** Fdot has quit IRC18:08
morganfainberg#topic The best way to solve name clashing in domain -> project migration.18:08
*** openstack changes topic to "The best way to solve name clashing in domain -> project migration. (Meeting topic: Keystone)"18:08
morganfainbergraildo o/18:08
raildoo/18:08
raildoIn the reseller spec we are proposing that a domain will be a project with some more features( user and groups managemnt). so when hen creating a domain, keystone will also create a projectthat has the same id.18:08
raildoand we a proposing for all existing domains, a sql migration will create a project with an idthat matches the domain_id, but we have a problem in this migration. We can find some clashing names between domains and project, we can't change the domain name in this migration because we have domain specific config file that use this domain name.18:09
*** kebray has quit IRC18:09
*** bvandenh has quit IRC18:09
*** krykowski has quit IRC18:09
raildoSo the question is: What is the best way to solve the clashing name problem in the domains sql migration?18:09
*** krykowski has joined #openstack-meeting18:09
rodrigodsmight have domain-specific files using the name18:10
henrynash_raildo: (well, we *might* have domain specifc config files if the cloud provider is using that feature)18:10
morganfainbergwell 2 things. duplicating data in the project table is probably wrong.18:10
*** auld has quit IRC18:10
atiwariI think we have agreed to migrate all domain to project18:10
*** eye_ has joined #openstack-meeting18:10
atiwariall existing one18:10
*** andreykurilin_ has joined #openstack-meeting18:10
*** thumpba has quit IRC18:10
morganfainbergand 2: the "domain" doesn't own itself in it's project list, so there should be no name-constraint issues18:10
dolphmIf namespacing is preserved, what's the scenario where a conflict can be introduced?18:10
*** kebray has joined #openstack-meeting18:10
rodrigodsmorganfainberg, 2: it doesn't?18:11
morganfainbergnames are unique within a domian, no conflict can occur if you're not adding the "domain-project" to an already existing domain [since domains aren't nested no conflicts]18:11
morganfainbergaren't nested today18:11
raildodolphm, maybe if we can get a token for a domain or a project, with the same name?18:11
morganfainbergrodrigods, if i ask what projects are in domain X, does domain X end up in that list? i think not18:11
morganfainbergsince domain X is not in itself a project within the domain.18:11
*** bdpayne has joined #openstack-meeting18:12
rodrigodsmorganfainberg, I thought they would be returned18:12
rodrigodssince they are just a project with the domain feature18:12
morganfainbergrodrigods, ok but then the domain-project X doesn't show up under it's parent's project list?18:12
dolphmbut, a project is not a child of itself18:13
HaneefWhat is there is an existing installation with project name = domain name?18:13
rodrigodsmorganfainberg, it appears in both lists?18:13
morganfainbergrodrigods, no a project is not a child of itself18:13
rodrigodsmorganfainberg, ok, didn't get right the question18:13
morganfainbergdolphm, beat me to it ;)18:13
dolphmhaneef: namespacing should be preserved, so it doesnt matter18:13
henrynash_morganfainbeg: that was the tack I was on (and if that were true, then we don’t have a clashing issue)….it depends with the project that represents a domain is a fully fledged project in its own right18:13
*** noslzzp has quit IRC18:14
*** achanda has joined #openstack-meeting18:14
*** bdpayne_ has joined #openstack-meeting18:14
dolphmhenrynash_: as opposed to..?18:14
morganfainberghenrynash_, it needs to be a fully fledged project, not sure what it would be otherwise18:14
morganfainbergbut that doesn't change the namespace18:14
*** dulek has joined #openstack-meeting18:14
*** aranjan_ has joined #openstack-meeting18:15
henrynash_morgainberg: so if it IS a fully feldged project, how come it’s not returned in a project list?18:15
*** esker has quit IRC18:15
rodrigodsmorganfainberg, root projects are always domains?18:15
rodrigodsright?18:15
morganfainberghenrynash_, becasue it isn't a child of itself.18:15
*** aranjan has quit IRC18:15
morganfainbergrodrigods, yes.18:15
*** andreykurilin|ho has joined #openstack-meeting18:15
raildorodrigods, right;18:15
*** andreykurilin_ has quit IRC18:15
henrynash_morganfainberg: so I can get_project on it……but not list it (if my only permission visibility is my domain)18:16
morganfainberghenrynash_, if you ask for projects in domain X, domain X does not itself end up in that list18:16
*** ksavich has joined #openstack-meeting18:16
henrynash_morganfainberg: agreed…this is a good conversation, since I’ve been arguing your position up to now!18:17
morganfainberghenrynash_, the same as it works today.18:17
bknudsonif you ask for projects in project X, project X does not itself end up in that list18:17
morganfainbergcorrect18:17
*** bdpayne has quit IRC18:17
rodrigodsmorganfainberg, ok... imagine the following hierarchy18:18
bknudsoncan I have a project named X in project X?18:18
*** ksavich has quit IRC18:18
*** ksavich has joined #openstack-meeting18:18
morganfainbergbknudson, yep, same reason it works today with domains, but you cannot have 2 projects named X in the parent X18:18
henrynash_morganfainberg: so my proposal earlier this week was that we could indeed avoid any name clashes since the uniquness of the project table would be: (‘name’, ‘domain_id’, “domain-ness-flag’)18:18
morganfainbergit can be X all the way down.18:18
*** markmcclain has joined #openstack-meeting18:19
*** timcline has joined #openstack-meeting18:19
*** dsetia has quit IRC18:19
bknudson-- only if the project is a domain.18:19
morganfainbergbknudson, sure.18:19
*** pelix has quit IRC18:19
jamielennoxi don't think you need the domain-ness-flag as part of that unique constraint18:19
*** gyee has joined #openstack-meeting18:20
raildohenrynash_, and I liked this proposal :)18:20
morganfainbergjamielennox, yeah i think you're right18:20
*** krykowski has quit IRC18:20
rodrigodswhy do we need the domain-ness flag and domain_id fields at all?18:20
rodrigodsahh, domain-ness flag for domains that aren't root18:20
jamielennoxrodrigods: because a name is only unique within it's parent18:20
rodrigodsright?18:20
raildomaybe we can remove the domain-ness flag18:20
morganfainbergrodrigods, even if they are root, they need the flag18:21
morganfainbergit is for compat with v3 api, what are my domains18:21
morganfainbergget_domains18:21
morganfainbergneeds to return soemthing sane18:21
*** saurabhs has joined #openstack-meeting18:21
rodrigodsmorganfainberg, if they are root, they are domains (just see if they parent_id=None)18:21
jamielennoxmorganfainberg: are we going to flatten that out in response?18:21
henrynash_so we need to be able to store a project named “Test” in domain “Test”…so something must differentiate between the two18:21
jamielennoxhenrynash_: parent_id18:22
morganfainbergjamielennox, i think the standard v3 call only returns top-level18:22
jamielennoxmorganfainberg: ++18:22
morganfainbergrodrigods, but parent_id would be set if a domain X was under domain Y18:22
morganfainbergboth are domains18:22
*** ddieterly has quit IRC18:22
morganfainbergdon't rely on parent_id being unset18:22
*** ddieterl_ has joined #openstack-meeting18:22
*** markvoelker has quit IRC18:22
morganfainbergdomain-flag is still going to be needed to limit things such as tying an idp to a domain etc.18:22
rodrigodsmorganfainberg, true, that was before I realized why we need the domain-ness flag18:22
*** joesavak has joined #openstack-meeting18:22
jamielennoxmorganfainberg: but in which case do we need the flag at all or is the top level of the tree always domains?18:23
*** noslzzp has joined #openstack-meeting18:23
morganfainbergjamielennox, top of the tree is domains, but domains can be nested under domains18:23
henrynash_don’t we need the flag on every project entry that is a domain?18:23
rodrigods++18:23
jamielennoxright - but do we need the flag further down18:23
morganfainbergjamielennox, lets keep it consistent and always use the flag for a domain18:23
morganfainbergjamielennox, even at the top18:23
jamielennoxhenrynash_: that was the decision from summit - it's early and i'm trying to wrap my head around it again18:23
* topol we can afford the bytes lets use the flag :-)18:24
henrynash_jamielennox:….otherwise how do you know which child is a proejct vs a domain18:24
rodrigodsso we are going to drop the domain_id column ?18:24
morganfainbergrodrigods, no.18:24
morganfainbergrodrigods, you can't18:24
*** markvoelker has joined #openstack-meeting18:24
jamielennoxhenrynash_: beyond compatibility with GET /v3/domains do we care?18:24
*** yeungp1 has quit IRC18:24
*** jroll has quit IRC18:24
bknudsonactually allowing NULL for the field will cost a byte18:24
dolphmmorganfainberg: (in the backend you can - it's just an implementation detail)18:24
*** yeungp has joined #openstack-meeting18:24
rodrigodsmorganfainberg, ah, ok it is an easy way to figure out which is some project's domain without the need to find the root18:25
bknudsona byte per row18:25
morganfainbergdolphm, we could have a separate table but eh.18:25
*** kurtmartin has quit IRC18:25
morganfainbergrodrigods, you still need to tie a project to it's domain.18:25
morganfainbergor a domain to it's parent domain18:25
rodrigods++18:25
morganfainbergwhere parent_id may match domain_id in that latter case, but make the lookups consistent18:25
morganfainbergand nullable domain_id makes sense for top-level projects18:26
morganfainberg or root domains18:26
*** jroll has joined #openstack-meeting18:26
raildomorganfainberg, ++18:26
henrynash_the only (minor) question I had was whether that null domain_id WAS teh domain_ness flag18:26
morganfainberghenrynash_, i think not.18:26
morganfainberghenrynash_, make the is_domain flag explicit18:26
rodrigodshenrynash_, because the domains hierarchy18:27
samueldmqhenrynash_, no, we need domain-ness flag for subdomainss18:27
henrynash_and I’m absolutelyy fine with that18:27
bknudsonif the projects domain id matches the project id then it's a domain.18:27
rodrigodsbknudson, can't be true for subdomains18:27
*** MarkAtwood has quit IRC18:27
gyeeif it quack like a duck, then it must be a duck18:27
samueldmqbknudson, think it works18:28
dolphmwait, we're not inventing new project IDs for every existing domain, are we?18:28
*** jorge_munoz has joined #openstack-meeting18:28
jamielennoxgyee: you're a duck18:28
*** krykowski has joined #openstack-meeting18:28
*** markmcclain has quit IRC18:28
morganfainbergdolphm, no we can't18:28
gyeequack, quack18:28
samueldmqbknudson, and for subdomains we use the parent_id as usual18:28
morganfainbergdolphm, domain_id -> project_id18:28
dolphm++18:28
*** gokrokve_ has joined #openstack-meeting18:28
morganfainbergthe chance for collision should be *very* small18:28
dolphmi'm willing to accept the risk18:28
rodrigodsdolphm, \o/18:29
bknudsonWhen it fails I'll tell them dolphm will fix it.18:29
morganfainbergif there is a collision there there is nothing programatic we can do, operator will need to handle because "which one wins" isn't a quest i want to answer18:29
morganfainbergsome cases project should win. some cases domain should.18:29
raildomorganfainberg, yes, and if happens we can change the domain_id and update every user, group and project to point to this domain, but as you say, this chance is really very small18:29
dolphmmorganfainberg: you're getting way too edge casey :P18:29
morganfainbergdolphm, it should be a near zero risk18:30
*** mattgriffin has quit IRC18:30
dstanekdomain and project ids are specified by the end user right? they are not guid18:30
morganfainbergdolphm, which means... i don't think we need to answer - just protect against it and tell the operator what happened if it breaks18:30
morganfainbergdstanek, uuid418:30
rodrigodsdstanek, uuids18:30
*** jroll has quit IRC18:30
*** jroll has joined #openstack-meeting18:30
samueldmqmorganfainberg, it's the same case to create a new project and get an existing id from the ids generator18:31
morganfainbergin oooooold deployments project could be set by the user18:31
*** jlibosva has quit IRC18:31
morganfainbergproject_id18:31
morganfainberglike... diablo and essex i think18:31
rodrigodsso...18:31
rodrigodswe don't care about name clashing18:31
rodrigodsbut we should add a new constraint18:31
morganfainbergbut domains have always been uuid18:31
rodrigodswhich will be...18:31
*** rprakash has quit IRC18:31
*** MarkAtwood has joined #openstack-meeting18:31
*** spandhe has joined #openstack-meeting18:31
dstanekhmmm...i thought we used ids if provided and if not provided then generated18:31
*** gokrokve has quit IRC18:31
dolphm"the extinction of all life on earth will occur long before you have a collision, even on a version 4 UUID"18:32
morganfainbergdstanek, in most cases we run ._ensure_unique_id18:32
morganfainbergdstanek, which replaces with uuid418:32
*** hemna has quit IRC18:32
morganfainberganyway18:32
dstanekmorganfainberg: i'm thinking v2 projects - other seem fine18:32
morganfainbergok we need to move on18:33
bknudsona 'default' project / domain will need to be created.18:33
morganfainberglots to cover.18:33
morganfainbergwe can discuss this more in -keystone and in review18:33
*** gokrokve_ has quit IRC18:33
dolphmmorganfainberg: even in diablo, i think we just used str(uuid4) instead of .hex18:33
dolphmand eeearly diablo used auto inc ints for tenant IDs18:33
morganfainberg#topic IDP and relationship with domains and projects-that-are-domains18:33
*** openstack changes topic to "IDP and relationship with domains and projects-that-are-domains (Meeting topic: Keystone)"18:33
morganfainbergayoung, raildo o/18:33
*** dzimine has joined #openstack-meeting18:33
*** ajo has joined #openstack-meeting18:34
*** jlibosva has joined #openstack-meeting18:34
rodrigodsdifferent spec than reseller, right? ^18:34
raildoIdp are the domain's container(or should be) and now that we are changing how the domain will works, ayoung have a concern about that, maybe we need to change something in this implementation.18:34
raildoSo I think that this discussion is out of scope of the reseller spec, but we really need to define better this relationship between Idp and project domain-ness (domain).18:34
morganfainbergraildo, i think we covered this at the mid-cycle18:34
raildomorganfainberg, great18:35
*** VW_ has quit IRC18:35
raildoI just don't know the answers :)18:35
morganfainbergan IDP can be tied to a domain. which means that users from that IDP can be mapped to that domain's groups (and only that idp's users)18:35
*** mattgriffin has joined #openstack-meeting18:35
gyeeIdP is indirectly tied to domain via group mapping, but that'll change with directly user mapping18:35
*** jlibosva has quit IRC18:35
morganfainbergif a domain doesn't not have a relationship to the domain, any idp can map to the groups (as we allow today)18:35
*** tongli has quit IRC18:35
morganfainbergthis also opens the door to directly map federated users to an exissting user in keystone18:36
*** spzala has quit IRC18:36
morganfainbergsame restriction18:36
*** jkremer has left #openstack-meeting18:36
rodrigodsmarekd's spec?18:36
raildomorganfainberg, great, so I  think that I don't need to explain nothing about that in the reseller spec, right?18:36
morganfainbergi think marked has a spec.18:36
rodrigodshttps://review.openstack.org/#/c/149071/18:36
dolphmmorganfainberg: many federated users mapping to a single identity is going to be a common use case18:37
rodrigodsgreat18:37
morganfainbergraildo, yep should have no impact on reseller directly18:37
raildomorganfainberg, ok, thanks :)18:37
morganfainbergdolphm, we can always loosen the restriction of number of IDPs to a domain18:37
dolphmmorganfainberg: ++18:37
morganfainbergdolphm, but we started with 1 idp per domain to make sure we get it right. iirc18:37
morganfainbergok next topic18:38
gyeesounds reasonable18:38
dolphmyep18:38
morganfainberg#topic Review Client Release Blockers - ETA on Release Feb 118:38
*** openstack changes topic to "Review Client Release Blockers - ETA on Release Feb 1 (Meeting topic: Keystone)"18:38
morganfainbergjamielennox, o/18:38
*** e0ne has joined #openstack-meeting18:38
*** e0ne is now known as e0ne_18:38
gyeemorganfainberg, but conversely an IdP can map to multiple domains right?18:38
morganfainbergthis also applies to keystonemiddleware18:38
morganfainberggyee, yes. no restriction there [today's usecase]18:38
jamielennoxright - so we want to bump keystoneclient and keystonemiddleware up to a 1 month release cycle18:38
gyeesounds good18:38
jamielennoxso at the start of every month we do a release of both18:38
*** ndipanov is now known as ndipanov_gone18:39
jamielennoxthis means that people need to get back into doing client reviews as the first one of these is planned for 3 days time18:39
bknudsonwhy not weekly?18:39
rodrigods\o/ have two changes in the client18:39
morganfainbergjamielennox, the only exception is RC for the named release there may be an extra release in there or a late release - so we have a clear "this release is the one we released along side of the named openstack release"18:39
rodrigodsto implement basic HMT handling18:39
jamielennoxbknudson: because no one will take me seriously when i push them for reviews every week18:39
jamielennoxmorganfainberg: sure18:40
bknudsonI didn't realize we were waiting for release boundaries to do reviews.18:40
gyeejamielennox, are you doing another rev on this one? https://review.openstack.org/#/c/149071/18:40
samueldmqbknudson, ++18:40
morganfainbergbknudson, we aren't really. just ksc has been slower so this is more of a lets do more consistent releases - this one being the bigger one since we have some stuff backed up18:40
dolphmbknudson: ++18:40
*** markmcclain has joined #openstack-meeting18:41
jamielennoxbknudson: it's partially to just increase the cadence rather than wait for some big feature, but also to set goals for each release18:41
morganfainbergbknudson, if there is no new code, no release is needed18:41
*** ignacio-scopetta has quit IRC18:41
jamielennoxthere is new code ....18:41
jamielennoxand much more stuck in reveiw18:41
morganfainbergjamielennox, there may be a month there isn't. it is unlikely but we're not releasing for the sake of releasing :P18:41
dolphmconversely, if there is a high priority bug fix, it should be released immediately instead of waiting for a scheduled release18:41
morganfainbergdolphm, always18:41
jamielennoxdolphm: ++18:41
*** MarkAtwood has quit IRC18:42
jamielennoxmorganfainberg: i'm looking forward to that time18:42
gyeeis there a way to query reviews based on bug priority?18:42
gyeemaybe using dolphm's next-review?18:42
morganfainberggyee, look at LP, next-review, bugday18:42
morganfainberggyee, plenty of options18:42
bknudsonThere's 66 open reviews in python-keystoneclient18:42
jamielennoxanyway - there are a bunch of things that have yet to see review in client that have been around since december18:42
*** MarkAtwood has joined #openstack-meeting18:42
gyeek18:42
dolphmgyee: http://status.openstack.org/reviews/18:42
*** ignacio-scopetta has joined #openstack-meeting18:42
*** e0ne_ is now known as e0ne18:43
jamielennoxmajor ones are marked in the gist in the channel home pages18:43
gyeedolphm, ah, thank18:43
jamielennoxi'll be around for the next few hours (and in general) if anyone wants to dicuss any of them18:43
morganfainbergso, review code, review more code, please review code18:43
gyeeyes, yes, yes18:43
bknudsonI don't want to have to check all sorts of places for reviews... we've already got launchpad with the bugs and blueprints18:43
morganfainbergbknudson, the only reason to look beyond lp and review.o.o is if you want different sorting metrics18:44
morganfainbergneed to keep moving here.18:44
morganfainberg#topic Domain roles APIs addition18:44
*** ajo has quit IRC18:44
rodrigodshttps://review.openstack.org/#/c/115770/ is almost in the bottom =(18:44
*** openstack changes topic to "Domain roles APIs addition (Meeting topic: Keystone)"18:44
dolphmReviews Guarantee Citizenship18:45
samueldmqo/18:45
morganfainberghenrynash_, samueldmq, o/18:45
samueldmqjust a bit of context ...18:45
*** dgonzalez has quit IRC18:45
gyeedolphm, nice :)18:45
samueldmqa domain role is a list of one or more roles and/or other domain roles, and is name-spaced to a domain18:45
samueldmqdomain roles can be used as part of an assignment, in the same was as you can assign a global role, it's proposed at #link https://review.openstack.org/#/c/13385518:45
samueldmqand I think the general idea is agreed over the community, right?18:45
samueldmqbut regarding the API changes, #link https://review.openstack.org/#/c/13953118:46
samueldmqi) we need a new CRUD for domain-roles, making possible to create and handle domain-role members18:46
samueldmqthis first point is a requirement, as it is a new entity18:46
samueldmqii) to use a domain-role wherever we use a global role, we can create new API for handling assignments or reuse the existent ones for global roles18:46
gyeesamueldmq, only issue I have with domain roles is to explain to people the difference between roles and domain roles18:46
samueldmqfor instance, add PUT /projects/{project_id}/groups/{group_id}/domain_roles/{domain_role_id}  in addition to PUT /projects/{project_id}/groups/{group_id}/roles/{role_id}18:46
gyeepeople = support, customers, doc writers, etc18:46
stevemargyee, ++18:47
stevemari have enough trouble explaining roles18:47
*** dgonzalez has joined #openstack-meeting18:47
samueldmqwell, henrynash_ may correct me if I'm wrong, domain roles will be scoped to domains and then used by domain admins18:47
Haneefgyee: previous name role_groups was better18:47
gyeeyes18:47
henrynash_gyee, stevemar: domain_roles are the customer-centric roles that domain admins can create, that mean something to THEIR customers….and typically domain admins haev no ability to change the policy file18:48
samueldmqthat allow domain admins  to create roles with custom names ..18:48
*** markmcclain has quit IRC18:48
*** ajo has joined #openstack-meeting18:48
dolphmif we don't domains anymore, these just become projects roles which will be super awesome to disambiguate from "roles"18:48
gyeehenrynash_, but we have have ducks!18:49
gyeesorry I mean roles18:49
samueldmqdolphm, ++18:49
*** e0ne has quit IRC18:49
morganfainbergdolphm, ++18:49
*** SergeyLukjanov has quit IRC18:49
henrynash_gyee: how does a domain_admin who works for customer X which is being hosted on a public cloud get to makea global role have impact on policy18:49
*** markmcclain has joined #openstack-meeting18:50
*** bitblt2 has quit IRC18:50
*** markmcclain has quit IRC18:50
gyeecan project roles inherit to other projects?18:50
morganfainberghenrynash_, *handwavey, timey, wimey, future*18:50
*** VW_ has joined #openstack-meeting18:50
henrynash_morganfainberg: really?18:50
dolphmmorganfainberg: sad ++18:50
samueldmqgyee, yes18:50
morganfainbergdolphm, yeah i know18:50
*** gokrokve has joined #openstack-meeting18:50
morganfainbergdynamic policy18:50
samueldmqgyee, you can use it as the same as global roles18:51
morganfainbergthat is how people change policy who are not global.18:51
morganfainbergperproject/perdomain/perwhatever18:51
*** che-arne has quit IRC18:51
morganfainbergayoung has a bunch of specs on it ;)18:51
raildogyee, yes, we implementing this for HMT18:51
dolphmhenrynash_: i think domain admins should be able to define their own additional policy (morgan's dynamic policy) first, and then it makes much more sense to discuss additional role definitions18:51
lbragstad~9 minutes left18:51
gyeeglobal roles? I haven't heard of that since KSL :)18:51
*** markmcclain has joined #openstack-meeting18:51
bknudsongyee: you haven't heard of the admin role?18:52
*** ajo has quit IRC18:52
morganfainbergok we are strapped for time18:52
henrynash_morganfainberg, dolphm: so this is something we agreed at the summit, no?18:52
morganfainberghenrynash_, pretty much-ish just inverting the priority18:52
gyeebknudson, but it's not "global roles"18:52
*** SergeyLukjanov has joined #openstack-meeting18:52
gyeeI am sure dolphm can fill you in on the history of "global roles"18:52
morganfainbergdo dynamic policy then defined roles vs inverse18:52
*** harlowja has quit IRC18:52
morganfainbergok we can do history lessons later18:53
morganfainbergwe need to move on18:53
*** nellysmitt has joined #openstack-meeting18:53
morganfainberg#topic Functional testing changes18:53
*** openstack changes topic to "Functional testing changes (Meeting topic: Keystone)"18:53
morganfainbergdstanek, o/18:53
*** banix has quit IRC18:53
dstanekthis should be quick18:53
*** krykowski has quit IRC18:53
morganfainberg(skipping role inheritance, sorry, we'll come back to it if we have time at the end)18:53
dstaneki wanted to show everyone this: http://paste.openstack.org/show/162858/18:53
samueldmqmorganfainberg, np18:53
*** leonchio_ has joined #openstack-meeting18:53
dstanekand just make sure the side effects were acceptable so i can let others know18:54
bknudsonwhew, it's safe for work.18:54
*** leonchio_ has quit IRC18:54
dstanekbknudson: next one might not be18:54
morganfainbergdstanek, i think that is ok.18:54
morganfainbergdstanek, since we can "not move" until we're sure coverage is comparable18:54
gyeedstanek, I would love to test it out with the SSL authz stuff18:55
bknudsonwhat's needed for "our side" ?18:55
*** markmcclain has quit IRC18:55
*** dzimine has left #openstack-meeting18:55
dstanekyep, ok - it's very similar to the message i had at the mid-cycle, but wanted to make it explicit18:55
bknudsonanything need to be reviewed?18:55
gyeeonly problem is how to get FreeIPA in there to give me some certs18:55
*** baoli has joined #openstack-meeting18:56
*** gokrokve has quit IRC18:56
jamielennoxgyee: do you have a client plugin side for that?18:56
dstanekbknudson: the second part of the spec we ripped in half and then updating the changeset to match18:56
*** markstur has quit IRC18:56
*** gokrokve has joined #openstack-meeting18:56
*** spzala has joined #openstack-meeting18:56
*** BharatK has quit IRC18:56
*** coolsvap is now known as coolsvap|afk18:56
morganfainbergdstanek, i chatted with jeblair about this and gave him a heads up we'd track him down for some specifics18:56
dstanekbknudson: there are a few things i just pushed, but nothing critical - those were config updates18:56
gyeejamielennox, for SSL authz, we just need a dummy adaptor for token_auth18:56
morganfainbergdstanek, of what we can/can't put in the keystone repo etc18:56
morganfainbergvs. devstack18:57
jamielennoxdummy adapter?18:57
morganfainbergvs. *other places*18:57
morganfainberggyee, we're strapped for time, IPA can be discussed outside of this meeting.18:57
lbragstadbknudson: dstanek #link https://review.openstack.org/#/q/status:open+project:openstack/keystone+branch:master+topic:bp/functional-testing,n,z18:57
lbragstad?18:57
*** daneyon has joined #openstack-meeting18:57
jamielennoxgyee: oh - you just want to fake out the auth part and you make the session handle the certs?18:57
morganfainbergjamielennox, cc ^18:57
gyeejamielennox, precisely18:57
gyeesince there are no tokens involved18:57
bknudsonmerge conflict as soon as it was posted.18:57
morganfainbergok so we're going to move on here18:57
morganfainbergi want to get breton his couple minutes18:58
morganfainberg#topic Alembic Status and Blockers18:58
*** openstack changes topic to "Alembic Status and Blockers (Meeting topic: Keystone)"18:58
morganfainbergbreton, o/18:58
bretonThough the spec is not yet accepted, I've almost finished Alembic stuff. It can be found here https://review.openstack.org/#/c/147548/ and here https://review.openstack.org/#/c/150057/ and another patch will arrive soon.18:58
bretonit required some collaboration with oslo_db team, because no one was using their migration_cli feature and we found and fixed some bugs.18:58
bretonfor example, this — https://review.openstack.org/#/c/134885/9 .18:58
bretonmy patches could work without the patch above, but that would require dirty hacks like line 184 on https://review.openstack.org/#/c/147548/8/keystone/tests/test_sql_upgrade.py18:58
bretonBut the hacks are (almost) all in tests.18:58
bretonit will take some time to have:18:58
breton1. required oslo_db's features merged18:58
breton2. oslo_db released18:58
breton3. the new oslo_db landed to keystone18:58
bretonWhat should I do: Wait for the new oslo_db to land in Keystone and remove the hacks or18:58
bretonleave the hacks and remove them in follow-up patches?18:58
*** ivar-lazzaro has quit IRC18:59
bknudsonmy preference is wait for oslo_db.18:59
morganfainbergi would rather wait for oslo_db. if it is going to be before k3 (should be doable)18:59
*** evgenyf has joined #openstack-meeting18:59
dstanekmine too - don't like the idea of monkey patching18:59
*** daneyon_ has joined #openstack-meeting18:59
*** rluethi has left #openstack-meeting19:00
*** ivar-lazzaro has joined #openstack-meeting19:00
bretonok, got it19:00
morganfainbergi'd like this support in kilo but it honestly could wait until L if we can't hit k3, we're still chugging along w/ SQL-A Migrate19:00
morganfainbergbut waiting is a better bet19:00
morganfainbergannnnnnd that is time.19:00
morganfainbergthanks everyone19:00
morganfainberg#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Jan 27 19:00:43 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
*** rushiagr_away is now known as rushiagr19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-01-27-18.05.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-01-27-18.05.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-01-27-18.05.log.html19:00
* morganfainberg makes sure to let -infra do -infra magic :)19:00
clarkbohai19:01
*** markstur has joined #openstack-meeting19:01
nibalizerhello19:01
fungiwe're sidetracked by black magic19:01
jeblair#delaymeeting infra 5 mins19:01
zaroo/19:01
* nibalizer nods emphatic agreement with fungi 19:01
pleia2o/19:02
anteayaoh goodness more meetings19:02
morganfainberganteaya. meeeeeeeeeeeeeeeetttttttttttingsssssssssss19:02
anteayawith music19:02
*** daneyon has quit IRC19:02
*** spzala has quit IRC19:03
*** rm_work|away is now known as rm_work19:03
*** nelsnels_ has joined #openstack-meeting19:03
*** unicell has joined #openstack-meeting19:03
*** breton has left #openstack-meeting19:03
*** padkrish has joined #openstack-meeting19:03
*** unicell has quit IRC19:03
*** unicell has joined #openstack-meeting19:03
ayoungI'm here19:04
*** lhcheng has left #openstack-meeting19:04
*** ksavich has quit IRC19:04
*** Farhan has joined #openstack-meeting19:05
*** otter768 has joined #openstack-meeting19:05
jeblair#startmeeting infra19:06
openstackMeeting started Tue Jan 27 19:06:00 2015 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:06
*** openstack changes topic to " (Meeting topic: infra)"19:06
openstackThe meeting name has been set to 'infra'19:06
*** yolanda has joined #openstack-meeting19:06
cody-somerville\o19:06
*** nelsnelson has quit IRC19:06
jeblair#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:06
*** baoli has quit IRC19:06
*** annegent_ has joined #openstack-meeting19:06
*** auld has joined #openstack-meeting19:06
jeblair#link previous meeting http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-01-20-19.02.html19:06
asselin_hi19:07
krtayloro/19:07
mmedvede__o/19:07
jeblair#topic libc CVE reboot19:07
*** openstack changes topic to "libc CVE reboot (Meeting topic: infra)"19:07
*** ksavich_ has joined #openstack-meeting19:07
jeblairso first, as a public service announcement, we are in the process of rebooting all of our affected hosts due to a vulnerability in libc19:07
jeblairwe've completed nearly all of the hosts running precise, and are awaiting updated packages for our centos hosts19:08
jeblairtrusty is apparently not affected19:08
*** margaret__ has quit IRC19:08
*** baoli has joined #openstack-meeting19:08
clarkbhave we confirmed that? I know I inferred it because it didn't have new packages yet19:09
*** berendt has joined #openstack-meeting19:09
pleia2the security announcement said only 10.04 and 12.04 were impacted19:09
pleia2http://www.ubuntu.com/usn/usn-2485-1/19:09
*** dprince has joined #openstack-meeting19:09
nibalizerthe cve said that it was fixed but the security implications were not recognized at that time19:09
*** otter768 has quit IRC19:09
fungiright, patch to fix it landed a couple years ago19:10
clarkboh good usn has it now19:10
jeblairso it seems plausible that the version in trusty is simply new enough.  i have not indepedently confirmed that19:10
clarkbI see so thats nice19:10
pleia2yep19:10
clarkbwe should probably put more effort into the tusty all the things effort19:10
*** nealph is now known as nealph_afk19:11
*** MarkAtwood has quit IRC19:11
jeblairclarkb: maybe?  but i don't think this is a reason to do so19:11
*** mmedvede__ has quit IRC19:11
*** _nadya_ has quit IRC19:12
clarkbjeblair: ya this particular thing isn't a reason, but it does illustrate why having newer packages can be a good thing19:12
*** markvoelker has quit IRC19:12
*** henrynash_ has quit IRC19:12
fungiwe could just as easily be faced next time with a bug which was only present on trusty19:12
clarkbyup19:12
*** MarkAtwood has joined #openstack-meeting19:12
jeblairclarkb: in this case, yes, but quite often older packages are too old to have new bugs.  things fall on both sides of the knife19:12
fungiif anything, newly-introduced security vulnerabilities are much more frequent than long-fixed newly-discovered ones19:13
jeblairso, yeah, we should move to trusty because it will be supported further in the future than precise19:13
*** baoli_ has joined #openstack-meeting19:13
*** Farhan has left #openstack-meeting19:13
*** ignacio-scopetta has quit IRC19:13
fungiwhich we are doing, here and there at least19:13
*** dsetia has joined #openstack-meeting19:13
jeblair#topic  Schedule next project renames19:13
*** openstack changes topic to "Schedule next project renames (Meeting topic: infra)"19:13
fungii'm open this weekend, or on friday if we want to do a friday afternoon thing19:14
jeblairwe still only have attic moves, but some have been pending for a while19:14
*** markvoelker has joined #openstack-meeting19:14
clarkbI can do saturday or friday but sunday is MURICA day lite19:14
clarkbI will be watching football and smoking meat19:14
anteayaI know annegent_ was asking about the ones she is advocating for19:14
*** Haneef has quit IRC19:14
*** BharatK has joined #openstack-meeting19:15
annegent_please don't let sportsball stop you :)19:15
*** unicell1 has joined #openstack-meeting19:15
*** unicell has quit IRC19:16
fungiindeed, i had forgotten. the joys of not watching commercial television19:16
*** baoli has quit IRC19:16
jeblairfriday then?19:16
clarkbwfm19:16
fungisure19:16
fungi1900 utc? earlier? later?19:17
*** krtaylor has quit IRC19:17
*** ignacio-scopetta has joined #openstack-meeting19:17
*** salv-orlando has quit IRC19:17
jeblair1900 wfm19:17
clarkb1900 wfm19:17
jeblair#agreed rename gerrit projects at 1900utc friday jan 3019:18
jeblairi'll send the email19:18
jeblair#topic Priority Efforts (Swift logs)19:18
*** openstack changes topic to "Priority Efforts (Swift logs) (Meeting topic: infra)"19:18
*** david8hu has joined #openstack-meeting19:19
clarkbI haven't seen jhesketh this morning so I can update here19:19
*** MarkAtwood has quit IRC19:19
clarkbjhesketh wrote a change to look for a magic number in the console log to know when the console log is complete when uploading to swift19:19
*** MarkAtwood has joined #openstack-meeting19:20
*** yapeng has joined #openstack-meeting19:20
clarkbunfortunately it went into an infinite loop because jenkins didn't appear to serve any additional bytes on top of what it originally served19:20
*** banix has joined #openstack-meeting19:20
clarkbcurrent workaround for that is to try 20 wget attempts and upload whatever it gets at that point. still need to figure out why it wasn't serving any more data thouhg19:20
*** zehicle_ has joined #openstack-meeting19:21
clarkbthe other thing that went in recently was better index file generation you should start seeing that today on swift logged logs.19:21
jeblairthat is highly weird19:21
*** ChrisPriceAB has quit IRC19:21
fungiwondering if there's a jetty-side cache or something19:21
clarkbya din't get much time to debug it last night and now libc. Hopefully we can figure it out soon19:21
jeblairclarkb, jhesketh: thanks! :)19:21
fungididn't seem to be apache causing it at any rate19:21
*** achanda has quit IRC19:22
jeblair#topic Priority Efforts (Puppet module split)19:22
*** openstack changes topic to "Priority Efforts (Puppet module split) (Meeting topic: infra)"19:22
jeblairReminder for Sprint: Wednesday January 28, 2015 at 1500 UTC19:22
fungifor those without calendars, that's TOMORROW!19:22
jeblair#link https://wiki.openstack.org/wiki/VirtualSprints#Schedule_of_Upcoming_OpenStack_Virtual_Sprints19:22
jeblair#link https://etherpad.openstack.org/p/puppet-module-split-sprint19:23
jeblairplease sign up on the etherpad ^19:23
jeblair#link https://review.openstack.org/#/q/topic:module-split+status:open,n,z19:23
*** ivar-laz_ has joined #openstack-meeting19:23
asselin_#link https://storyboard.openstack.org/#!/story/30219:23
asselin_Remember to add yourself here too ^^19:23
asselin_link is in etherpad19:23
jeblairasselin_: thanks for your prep work!19:24
*** thedodd has quit IRC19:24
asselin_jeblair, you're welcome19:24
*** yapeng has quit IRC19:24
fungii'm looking forward to reviewing (and possibly breaking/troubleshooting) all the things19:25
jeblairand we'll see everyone tomorrow and hopefully end the day with a bunch of new gerrit repos :)19:25
nibalizer\o/19:25
clarkbshould be good fun19:25
jeblair#topic Priority Efforts (Nodepool DIB)19:25
*** openstack changes topic to "Priority Efforts (Nodepool DIB) (Meeting topic: infra)"19:25
*** MarkAtwood has quit IRC19:25
clarkbno updates since last week on this. I was out most of last week.19:25
jeblairmordred: anything blocking you?19:26
clarkbI did however notice rax snapshot image builds for centos and precise were broken so that should be sorted with the next round of rebuilds19:26
mordredI mean19:26
*** ivar-lazzaro has quit IRC19:26
mordredother than openstack?19:26
jeblairmordred: anything we can help with? :)19:26
mordredjeblair: keep me from killing our cloud providers out of rage?19:26
mordredjeblair: I'm honestly getting quite close, which is why I'm ragey19:26
mordredbut I've discovered a new way in which the rackspace catalog is broken but current tools have been hiding it19:27
*** MarkAtwood has joined #openstack-meeting19:27
clarkbI hope to start work on moving away from unittest specific slaves as soon as the fires go away. I really don't know what the scope of that work is yet though (do we do it for stable branches? etc)19:27
*** radez is now known as radez_g0n319:27
mordredoh - also - any infra-core who isn't watching the shade repo for reviews please do19:27
fungigotta love breakage swept under the rug by tooling19:27
*** harlowja has joined #openstack-meeting19:28
*** evgenyf has quit IRC19:28
jeblairmordred: and anyone with an interest in nodepool19:28
mordredI'm hoping to have a first-pass nodepool patch up today19:28
fungiclarkb: i'm guessing it's coming up with a new job macro which installs the additional packages we don't install on the devstack workers19:28
jeblairsince we want to have shade be good enough to present a sensible interface to nodepool19:28
mordredit will not work - but will be something worth commenting on approach with19:28
yolandamordred, i've been taking a look at that shade project. Mostly i'm missing tests , but maybe is that at an early stage?19:28
mordredyolanda: yes - it's massively missing tests ... I'd love help :)19:28
*** andreykurilin|ho has quit IRC19:29
clarkbfungi: ya which is a non trivial set. which means we need to cache on the images first, etc19:29
*** dims has quit IRC19:29
mordredhowever - I have a question for folks on that ...19:29
fungiclarkb: yep19:29
clarkbfungi: since devstack isn't exactly the set of things you need19:29
mordredany thoughts on how to test that interactions with rackspace and hp public clouds as they exist in the wild work?19:29
mordredbecause I can test against devstack all day long without surfacing any of the issues we've been battling lately19:29
clarkbmordred: spin up a nodepool19:29
fungimordred: we could do it pretty easily with flaky jobs19:30
clarkbmordred: or do ou mean generally?19:30
mordredI mean generally19:30
*** krtaylor has joined #openstack-meeting19:30
fungifalse negative rate would be pretty high19:30
mordredlike, how do I functionally test shade to tell that it works with the real public clouds19:30
yolandamordred, have testing accounts on that providers and launch tests against them instead of fake providers?19:30
mordredI suppose a set of massive fakes that return manually grabbed data as the clouds return it?19:30
nibalizerpuppet does that kind of testing, it turns into a massive workpile whenever the universe changes19:31
*** annegent_ has quit IRC19:31
jeblairmordred: have you seen mimic?  https://github.com/rackerlabs/mimic19:31
jeblairmordred: glyph mentioned it to me a while ago19:31
mordredneat!19:31
mordredmaybe we shodl use that19:31
mordredI wonder if it's bug-for-bug compatible with rax?19:31
jeblairmordred: heh, yeah, there's a thought.  :)19:32
jeblair"Mimic is an API-compatible mock service for Openstack Compute and Rackspace's implementation of Identity and Cloud Load balancers. It is backed by in-memory data structure rather than a potentially expensive database."19:32
*** lukasa_home has joined #openstack-meeting19:32
mordredworth looking at19:32
jeblairi'm kind of divided on this -- part of me is like "why is the word rackspace in there, why can't we have nice openstack things" but then, part of me says "hey, it's an implementation, it still may be worth testing against as-is"19:32
jeblairsince, after all, we _actually_ want to use shade with rackspace :)19:33
mordredyah19:33
mordredthat's kinda where I'm at19:33
*** lukasa_home has left #openstack-meeting19:33
mordredthat rackspace may or may not be an openstack at this point is not the point19:33
mordredthe point is that it's one of my clouds and I need to use it19:33
*** dims has joined #openstack-meeting19:34
jeblairof course, if we have to write a patch to mimic to enable an hpcloud weirdness, that will be... instructive19:34
jeblairor even a normal openstack behavior that rackspace doesn't exhibit19:34
yolandajeblair, mordred, and how can you be aware of any weirdness?19:35
mordredyah. well, I'd hope we can do that with devstack19:35
*** kebray has quit IRC19:35
mordredyolanda: when it breaks my local tests :)19:35
yolandaempiric testing :)19:35
mordredI currently test with a set of very bad scripts in my homedir that I point at rax and hp accounts19:35
jeblairmordred, yolanda: so maybe shade should have a test against devstack using a dsvm node, and a test against mimic19:35
*** annegent_ has joined #openstack-meeting19:35
mordredjeblair: +100019:36
*** ddieterl_ has quit IRC19:36
jeblairso, land of opportunity here :)19:36
jeblairanything else on nodepool dib?19:36
clarkbnot from me19:37
*** e0ne has joined #openstack-meeting19:37
jeblair#topic Priority Efforts (Jobs on trusty)19:37
*** openstack changes topic to "Priority Efforts (Jobs on trusty) (Meeting topic: infra)"19:37
fungidhellmann has graciously started a thread on disabling py3k gating for oslo.messaging and oslo.rootwrap19:37
fungi#link http://lists.openstack.org/pipermail/openstack-dev/2015-January/055270.html19:37
fungiso far discussion seems to be accepting19:38
mordredyay19:38
clarkbI have pointed them at the bugs in question and answered a couple of the things that came up19:38
fungiif there are no major concerns raised by friday, we can go ahead and cut over19:38
*** afazekas has quit IRC19:38
fungii was running a full recheck of all the projects currently successfully gating on 3.3 against 3.4 but lost my held nodes in the great reboot of 201519:38
fungiso in the process of restarting them right now19:39
jeblairwhoopsie19:39
fungibut will know before the day is out if there are any new projects which are failing and have slipped through the cracks19:39
nibalizerfungi: did you reboot the servers or just restart services?19:39
*** annegent_ has quit IRC19:39
fungiand plan to go ahead and whip up the change to switch them later this week19:39
funginibalizer: we rebooted all ubuntu precise servers after updating glibc on them19:40
*** annegent_ has joined #openstack-meeting19:40
*** ignacio-scopett1 has joined #openstack-meeting19:40
* nibalizer nods19:40
*** rushiagr is now known as rushiagr_away19:40
fungianyway, nothing new on that front otherwise19:40
jeblairfungi: thanks, progress!19:40
jeblair#topic Priority Efforts (Zanata)19:41
*** openstack changes topic to "Priority Efforts (Zanata) (Meeting topic: infra)"19:41
fungieta on getting fixed python 3.4 in trusty seems to be sometime in march probabkly19:41
jeblairpleia2: anything we can unblock?19:41
pleia2I don't think so, just sorting out dependency issues now19:41
pleia2https://review.openstack.org/#/c/147947/19:41
clarkbpleia2: I said I would review when in a layover thengot distracted by image building and things19:42
clarkbpleia2: will try to review that change sometime this week19:42
pleia2I'll make a note in the review about what the order should be19:42
jeblair#link https://review.openstack.org/#/c/147947/19:43
*** ignacio-scopetta has quit IRC19:43
*** Mandell has quit IRC19:43
jeblair#topic Options for procedural -2 (jeblair)19:43
*** openstack changes topic to "Options for procedural -2 (jeblair) (Meeting topic: infra)"19:43
jeblairzaro: have you had a chance to look at the current status of the wip plugin?19:43
zarojeblair: sorry, i have not.  will do this week for sure19:44
jeblairzaro: thanks!19:44
jeblair#action zaro look into the current status of the wip plugin and find out if it is ready for use in gerrit 2.9 and could be used for procedural -219:45
jeblair#topic  Upgrading Gerrit (zaro)19:45
*** openstack changes topic to "Upgrading Gerrit (zaro) (Meeting topic: infra)"19:45
*** pboldin has quit IRC19:45
zarozuul-dev is still in a broken state.  need it working to continue testing.19:45
fungiwe've got an ubuntu trusty review-dev built19:45
zarofungi: says he's gonna take a look.19:46
jeblairwhat do we need to do to fix zuul-dev?19:46
fungiand yeah, i'm looking at zuul-dev errors this afternoon19:46
jeblairok.  so we're at "identify problem" stage with zuul-dev19:46
zaroi think something wrong with apache setup.19:46
fungii assume the idea is to test gerrit 2.9.x with zuul19:46
zaroyes, that is the purpose19:46
clarkbnote 2.10 just released right? is it worth moving the target for any features we want/need?19:47
jeblairzaro: you can run your own zuul locally to test19:47
fungiit's almost certainly just apache 2.4 syntax issues with the vhost config19:47
jeblairthat's actually usually what i do19:47
clarkbif not I don't think we go to 2.10 simply because its there19:47
fungibut i haven't looked yet19:47
jeblairi usually reserve zuul-dev for testing zuul19:47
zarojeblair: yes, but need to fix zuul-dev anyway right?19:47
*** evgenyf has joined #openstack-meeting19:47
*** jamielennox has left #openstack-meeting19:47
zaroyeah, i would hold off on 2.10 until users get to 'break it in'19:48
jeblairzaro: i mean, it wouldn't hurt, but i don't think we need to block the gerrit upgrade on it19:48
*** Sukhdev has joined #openstack-meeting19:48
*** adalbas has quit IRC19:49
jeblair#topic  Open discussion19:49
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:49
zarounderstood.  i may take that route.19:49
pleia2nibalizer and I are presenting at fosdem on bits of infra this weekend (so airplanes and things coming up)19:50
*** rushiagr_away is now known as rushiagr19:50
mordredpleia2: enjoy!19:51
mordredpleia2: also, don't forget to drink ALL THE BEER19:51
fungihoping to hack on a nodepool bare-debian dib image later this week or next to see if we can run all our python 3.4 jobs successfully on it, and then that opens us up to be able to test other things on debian if we like19:51
*** ddieterly has joined #openstack-meeting19:51
pleia2mordred :D19:51
jeblairpleia2, nibalizer: yay!  let us know if there's a video19:51
jeblairfungi: ++19:51
*** ddieterly has quit IRC19:51
pleia2will do19:51
anteayapleia2: safe travels19:51
anteayanibalizer: youtoo19:52
nibalizerthanks19:52
*** ddieterly has joined #openstack-meeting19:52
fungibest of luck on your presentations. break several legs or something19:52
clarkbalso eat at toukoul19:52
nibalizer:D19:52
nibalizeri'll be at the puppet contributor summit after fosdem, so can bring up bugs directly with developers, if we have any nonstandard ones lingering19:52
fungiremember to remind the entire audience that we need them to come hack on and review our code ;_19:52
zarolooks like proposal to add a seperate notification channel in gerrit is dead: https://gerrit-review.googlesource.com/#/c/6325919:53
zaronot sure if we want to do anything further to get it upstream?19:53
fungithat's unfortunate19:54
*** auld has quit IRC19:54
*** kebray has joined #openstack-meeting19:54
*** nelsnels_ has quit IRC19:54
*** auld has joined #openstack-meeting19:54
*** nelsnelson has joined #openstack-meeting19:54
fungii'm not quite following why sven abandoned that change19:55
*** nellysmitt has quit IRC19:55
*** tris has quit IRC19:55
fungiit seemed to be active as of yesterday19:55
*** joesavak has quit IRC19:55
zaroi think he's basically thinks that it's fruitless to continue.19:56
*** joesavak has joined #openstack-meeting19:56
*** nelsnelson has quit IRC19:56
clarkbdave borowitz does seem to shoot it down pretty hard with comments yesterday19:56
jeblairhe also said 2 weeks ago "I'm glad this feature is getting implemented."19:56
fungihttps://gerrit-review.googlesource.com/58283 seems to still be open though19:56
*** nelsnelson has joined #openstack-meeting19:57
fungilooks like maybe it's just continying there?19:57
fungier, continuing19:57
zaroit's just the same change. sven only split it up into multiple changes.19:57
*** ebalduf has quit IRC19:57
zaro58283 was the one i worked on with David O.  such wasted effort.19:58
*** neelashah has quit IRC19:59
zaro58283 was the original change, it was too big so sven split it up into 4 smaller changes. 6259 is one of the smaller change.19:59
jeblairit seems like the gist of dave borowitz's comments were about the specificity of the data19:59
jeblairzaro: perhaps you could discuss with dave what kind of data he would be comfortable having in the db19:59
jeblairzaro: because i don't think we need everything in there -- job name, result, and link are pretty universal20:00
*** tris has joined #openstack-meeting20:00
*** marcelodieder has quit IRC20:00
*** enterprisedc has joined #openstack-meeting20:01
jeblairand even his last comment is a suggestion20:01
*** dprince has quit IRC20:01
jeblairzaro: anyway, i hope you find a way to continue, and thanks for trying regardless20:01
jeblairwe're out of time, thanks everyone20:01
jeblair#endmeeting20:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:02
openstackMeeting ended Tue Jan 27 20:02:00 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-01-27-19.06.html20:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-01-27-19.06.txt20:02
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-01-27-19.06.log.html20:02
ttxAnyone here for the TC meeting ?20:02
dhellmanno/20:02
annegent_here20:02
ttxI saw jeblair 30 seconds ago20:02
*** neelashah has joined #openstack-meeting20:02
ttxrussellb, jgriffith, mikal, mordred, devananda, vishy, markmcclain, jeblair, jaypipes, sdague : around ?20:02
jeblairyep20:02
vishyo/20:02
mordredo/20:02
russellbo/20:03
ttxalright, this is quorum20:03
ttx#startmeeting tc20:03
openstackMeeting started Tue Jan 27 20:03:22 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
*** openstack changes topic to " (Meeting topic: tc)"20:03
openstackThe meeting name has been set to 'tc'20:03
ttxOur agenda for today:20:03
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:03
*** yolanda has left #openstack-meeting20:03
*** juzuluag has quit IRC20:03
*** dulek has quit IRC20:03
ttxNote that I added Doug's recent thread to the agenda today, since it's very much related to the proposed changes on Project structure reform20:03
*** novas0x2a|laptop has joined #openstack-meeting20:03
*** persia has quit IRC20:04
*** pboldin has joined #openstack-meeting20:04
ttxhmm, we don't seem to have haypo around20:04
*** persia has joined #openstack-meeting20:04
*** persia has quit IRC20:04
*** persia has joined #openstack-meeting20:04
ttxI guess we can still discuss the issue, I'll play devil's advocate20:04
ttx#topic asyncio: replace eventlet with trollius20:04
*** openstack changes topic to "asyncio: replace eventlet with trollius (Meeting topic: tc)"20:04
ttxSo this topic was raised by haypo at sdague's request20:04
ttx(both of which are not present :)20:05
ttxor is it both of whom? Damn English language20:05
annegent_wait, who's haypo?20:05
russellbif neither are here, doesn't seem urgent to discuss20:05
annegent_heh20:05
ttxthat would be Victor Stinner20:05
annegent_ok20:05
*** roaet has quit IRC20:05
ttxrussellb: ok, let's table it until meeting end20:05
dhellmann++20:05
ttx#undo20:05
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x34a21d0>20:05
*** ebalduf has joined #openstack-meeting20:05
ttx#topic Project structure reform20:05
*** openstack changes topic to "Project structure reform (Meeting topic: tc)"20:05
*** aysyd has quit IRC20:06
ttx* Is the governance repository the long-term place for the project tags (http://lists.openstack.org/pipermail/openstack-dev/2015-January/055151.html)20:06
ttxdhellmann raised this thread just yesterday, but since it objects somehow to the proposed changes, I think it's worth discussing it first20:06
ttxIt primarily objects to using the openstack/governance repository as the home for the project tags20:06
ttxWhile I still strongly support tags as a way to clearly describe code repositories, but I tend to agree that this all could live in a separate repository20:06
ttxs/but//20:06
mordredI'm with dhellmann ... try as I might, I cannot actually find a concrete example of a tag that I think provides useful information20:06
annegent_I did talk to dhellmann yesterday some (in case you were wondering why I hadn't replied on a thread that directly mentioned docs)20:07
*** bradjones has quit IRC20:07
mordredthat isn't already information that exists either elsewhere or is purely an opinion20:07
annegent_I would love to do the data mining on current docs to see if that would be meaningful to devs/ops/users.20:07
dhellmannI have no strong opinion on whether tags are useful. I guess I'm +0 on having them? But none of the semi-useful ones I have seen so far are things that need us to vote on as a governing body.20:07
vishyI think subjective tags have value20:07
ttxI think reference information about projects has value20:07
annegent_well "I" meaning, if I had time20:07
dhellmannvishy: example?20:07
vishyand there will most definitely be subjective tags for the board at least20:07
vishy"core"20:07
*** atiwari1 has joined #openstack-meeting20:07
ttx"compute-base"20:07
mordredvishy: I think subjective tags have value in general, but I can't come up with a concrete example of a tag that has value20:07
dhellmannttx: yeah, I'm not sure it needs to be "tags" is all I'm saying20:07
ttx"coordinated-release"20:08
dhellmannvishy: core won't be a tag, though, right?20:08
zanebI want tags to help project teams know what is important for them to work on (and to whom it is important)20:08
vishyi believe it will be represented witha  tag20:08
*** hemna has joined #openstack-meeting20:08
mordredcore is a meaningless concept20:08
*** stevemar has quit IRC20:08
vishyclearly it will be voted on by the board so the process is different20:08
dhellmann"compute-base" can be discovered by looking at the dependency lists for projects20:08
zaneb1000 little objective tags just says that everything is important to somebody20:08
dhellmann"coordinated-release" can be determined by looking at the release schedule20:08
ttxmordred: if none are useful, then we won't add any. But I already know of 4 that I want to have and are useful20:08
zanebthere's no useful information there20:08
mordredttx: useful to who?20:08
*** stevemar has joined #openstack-meeting20:08
dhellmannneither of those examples requires the governing body of the openstack developer community to approve them if we're giving projects the ability to define their own dependencies and release schedules20:09
vishybut aren’t we as the tc comittee responsible for providing some guidance to the community?20:09
ttxdhellmann: we don't invent any new information with the tags, we just surface that information for our users20:09
ttxthink of it as reference metadata20:09
annegent_I think that the current way you figure out what to run in production is quite word-of-mouth20:09
mordredttx: right. but we don't need to vote as the TC on reference metadata20:09
ttxmordred: all our users ?20:09
jeblairvishy: what kind of guidance should we provide via tags?20:09
annegent_so a reference would be valuable20:09
vishyas an operator I would generally like to know what the tc thinks of a given project20:09
dhellmannttx: it's fine to have them, but I don't think we need to vote on them as a governing body20:09
ttxmordred: that I would agree to20:09
mordredvishy: we never have and probably never will express that opinion20:09
ttxand I said as much to dhellmann on the thread20:09
mordredvishy: if we WERE going to do that, I'd be with you20:09
vishyimordred yes we have20:09
vishywe called it “incubated” and “integrated” before20:10
annegent_we have mordred from a historical perspective20:10
mordredthat was not our opinoin of the project20:10
dhellmannvishy: right, but now we're explicitly doing away with those things20:10
ttxmordred: I'm not sure we'll come up with a tag that needs to be solely decided by the TC, if that's your point20:10
mordredthat was our determination that a project met a process20:10
ttxWe might be actually agreeing20:10
mordredour users, it turns out, don't care about that20:10
*** atiwari has quit IRC20:10
dhellmannttx: yes, that is my point20:10
*** evgenyf has quit IRC20:10
russellbintegrated has been about more than process20:10
david-lyleyou are walking to toward a very tangled web, when there are no qualifications around which pieces work with which, which is what happens if you leave it up to individual projects20:10
vishydhellmann: we are doing away with those specific tags20:10
russellbwe have guideless far more extensive than just process20:10
ttxdhellmann: the proposal sayd: tags can be delegated to another group for maintenance20:11
vishybut to say that we don’t ever need them seems a bit short sighted20:11
ttxdhellmann: this may end up being all of them20:11
annegent_now we want tags or some sort of indicator to enable more tight integration and specific use cases rather than "run the world"20:11
ttxdhellmann: I'm pretty sure it will be "most of them"20:11
dhellmannttx: that's fine. I still think we could "surface" this information by just writing down some product documentation somewhere.20:11
*** dulek has joined #openstack-meeting20:11
zanebdhellmann: the problem with before was that we couldn't communicate different things to different audiences. The fact that we were communicating was not bad in itself20:11
jeblairmordred: to be fair, i believe that in the past we have considered desirability of including a project in openstack when incubating or integrating it.  but i believe that many of us think that is no longer a good idea20:11
jaypipesjeblair: ++20:12
ttxdhellmann: I think there is value in presenting that reference information in some project browsing website. Have it live in some YAML file somewhere helps that website to exist20:12
mordredjeblair: sure. but the one that has been explicitly requested "is this ready for me to run" is one that we actually don't know the answer to until people decide to run it20:12
*** evgenyf has joined #openstack-meeting20:12
jeblairmordred: fully agreed there20:12
ttxI don't think we should expect people to find out that reference information on their own20:12
mordredthat's the only one that I think isn't just procedural or a collection of already existing data from the docs20:12
ttxthat's what we currently do and it fails20:13
david-lylefor projects that build on other projects, heat, horizon, tripleO and ever expanding eco-system means limitations on how much how quickly we can support20:13
*** _nadya_ has joined #openstack-meeting20:13
annegent_ttx: +120:13
*** thedodd has joined #openstack-meeting20:13
ttxSo in summary, I totally agree that the TC shoud not be the body deciding all the tags20:13
ttxI even agree that the TC should not decide most of the tags20:13
ttxbut I still think tags have value20:13
dhellmannif tags had not come up in the context of the big tent discussion, would we have started doing that ourselves? or would we have, for example, asked the new product management group to help us with product documentation?20:14
ttx$and it's our responsibility to provide the framework to handle them20:14
*** bradjones has joined #openstack-meeting20:14
vishyI also agree that we shouldn’t be responsible for all tags20:14
vishyobjective ones can be verified independently20:14
*** markmcclain has joined #openstack-meeting20:14
*** sergef has quit IRC20:14
annegent_we can enable tags as self-service20:14
ttxdhellmann: we tried to provide that info in the past, mostly through wiki landing pages20:14
vishybut I’m not willing to state that we will never want some kind of subjective tagging20:15
mordredvishy: I agree with that20:15
ttxtags are just a way to express that project metadata20:15
vishyand i don’t think people should just be able to throw in arbitrary tags as they see fit20:15
jeblairttx: i'm willing to give them a shot and not disrupt the process we are on, but i also think dhellmann makes a good point that they may simply prove to be unecessary.20:15
mordredvishy: I think I'm just trying to say that I, so far, haven't heard any tag suggestions that I personally think have any value20:15
vishythey need some kind of review process20:15
mordredvishy: but I'm very open to being wrong :)20:15
jeblairi'm certainly no longer willing to say tags are the answer to every question that comes up wrt the big tent :)20:15
mordred++20:15
vishymordred: I don’t have any to propose currently for sure20:15
dhellmannvishy: if we have facts that we want to declare about projects, why does *this group* need to vote on whether they are true?20:16
* jaypipes not a fan of subjective tags, but recognize that some audiences seem to want them20:16
* mordred agrees 100% with vishy then20:16
annegent_I think subjective tags are better than "so and so said this" :)20:16
* mordred tags jaypipes as friendly20:16
markmcclain++20:16
ttxjeblair: I think surfacing reference info has value. I agree that most of that inbfo already exists somewhere20:16
ttxand that in most cases our group is not the best suited to update that info20:17
*** vigneshvar has quit IRC20:17
mikalOh, apparently I am here20:17
ttxBut let me take a step back20:17
annegent_mikal: welcome20:17
* sdague as well 20:17
ttxtags will also be used to answer some questions as the TC and those tags will be directly handled by us20:17
dhellmannhmm, can you give an example?20:18
ttxthe (new) bylaws require that we provide subsets of projects that may be used in trademark license programs20:18
*** madskier has joined #openstack-meeting20:18
ttx(a "TC approved release")20:18
ttxthe way I thought we would answer that question is through a tag20:18
ttxthink "OpenStack Storage powered product"20:18
dhellmanndo we need different sets of projects, or just a list of "put trademarks on these"?20:19
ttxno no20:19
ttxwe need different subsets, which we allow the board to take a subset of for specific trademark programs20:19
ttxsorry can't type faster :)20:20
*** ebalduf has quit IRC20:20
ttxso superset is "all OpenSTack projects"20:20
* dhellmann imagines ttx juggling a glass of wine, a pastry, and a keyboard20:20
mordredand cheese20:20
dhellmannso they want us to suggest which projects might go into which categories?20:20
*** baoli_ has quit IRC20:20
russellbright20:20
ttxBoard has new trademark program, call it "OpenStack inspired dream"20:20
ttxwe define a subset of projects that may be used to that effect20:20
*** timcline has quit IRC20:21
*** kurtmartin has joined #openstack-meeting20:21
ttxand board picks from /that subset/ to establish the trademark program20:21
dhellmannit seems like it ought to be enough to say "this one should be a candidate for trademarks" and let the board decide which go in which programs20:21
russellbwe'll be working on a process for this soon20:21
ttxany or all of the subset we defined20:21
russellbwhich might help clarify things20:21
*** timcline has joined #openstack-meeting20:21
ttxso I was planning to use TC-controlled tag for that, that would be an example of one tag direclty handled by tc20:21
dhellmannif a project ever fit into more than one category, would we ever say "use the trademark in category A but not B"?20:21
ttxI agree we could do it outside of the tag framework20:21
*** openstack has joined #openstack-meeting20:38
*** sendak.freenode.net sets mode: +ns 20:38
*** sendak.freenode.net sets mode: -o openstack20:44
-sendak.freenode.net- *** Notice -- TS for #openstack-meeting changed from 1422391102 to 128266156420:44
*** sendak.freenode.net sets mode: +ct-s 20:44
*** edleafe has joined #openstack-meeting20:44
*** padkrish has joined #openstack-meeting20:44
*** achanda has joined #openstack-meeting20:44
*** roaet has joined #openstack-meeting20:44
*** ajo has joined #openstack-meeting20:44
*** moha_hunt has joined #openstack-meeting20:44
*** sparkycollier has joined #openstack-meeting20:44
*** joesavak has joined #openstack-meeting20:44
*** vigneshvar has joined #openstack-meeting20:44
*** dboik has joined #openstack-meeting20:44
*** lsell has joined #openstack-meeting20:44
*** ivar-lazzaro has joined #openstack-meeting20:44
*** roaet- has joined #openstack-meeting20:44
*** jvrbanac_ has joined #openstack-meeting20:44
*** cyeoh has joined #openstack-meeting20:44
*** nikhil- has joined #openstack-meeting20:44
*** spzala has joined #openstack-meeting20:44
*** Mandell has joined #openstack-meeting20:44
*** joel-coffman has joined #openstack-meeting20:44
*** dprince has joined #openstack-meeting20:44
*** eglynn has joined #openstack-meeting20:44
*** timcline has joined #openstack-meeting20:44
*** terryw has joined #openstack-meeting20:44
*** mgagne_ has joined #openstack-meeting20:44
*** russell_h has joined #openstack-meeting20:44
*** EmilienM has joined #openstack-meeting20:44
*** dtroyer_zz has joined #openstack-meeting20:44
*** russellb has joined #openstack-meeting20:44
*** rossella_s has joined #openstack-meeting20:44
*** rm_work has joined #openstack-meeting20:44
*** tr3buchet1 has joined #openstack-meeting20:44
*** _d34dh0r53_ has joined #openstack-meeting20:44
*** stevebak` has joined #openstack-meeting20:44
*** dendroba` has joined #openstack-meeting20:44
*** dutsmoc has joined #openstack-meeting20:44
*** rainya_ has joined #openstack-meeting20:44
*** madskier has joined #openstack-meeting20:44
*** markmcclain has joined #openstack-meeting20:44
*** bradjones has joined #openstack-meeting20:44
*** thedodd has joined #openstack-meeting20:44
*** _nadya_ has joined #openstack-meeting20:44
*** evgenyf has joined #openstack-meeting20:44
*** dulek has joined #openstack-meeting20:44
*** stevemar has joined #openstack-meeting20:44
*** hemna has joined #openstack-meeting20:44
*** atiwari1 has joined #openstack-meeting20:44
*** persia has joined #openstack-meeting20:44
*** pboldin has joined #openstack-meeting20:44
*** novas0x2a|laptop has joined #openstack-meeting20:44
*** neelashah has joined #openstack-meeting20:44
*** enterprisedc has joined #openstack-meeting20:44
*** tris has joined #openstack-meeting20:44
*** nelsnelson has joined #openstack-meeting20:44
*** auld has joined #openstack-meeting20:44
*** ddieterly has joined #openstack-meeting20:44
*** Sukhdev has joined #openstack-meeting20:44
*** ignacio-scopett1 has joined #openstack-meeting20:44
*** annegent_ has joined #openstack-meeting20:44
*** e0ne has joined #openstack-meeting20:44
*** dims has joined #openstack-meeting20:44
*** krtaylor has joined #openstack-meeting20:44
*** harlowja has joined #openstack-meeting20:44
*** MarkAtwood has joined #openstack-meeting20:44
*** zehicle_ has joined #openstack-meeting20:44
*** banix has joined #openstack-meeting20:44
*** david8hu has joined #openstack-meeting20:44
*** unicell has joined #openstack-meeting20:44
*** BharatK has joined #openstack-meeting20:44
*** markvoelker has joined #openstack-meeting20:44
*** dsetia has joined #openstack-meeting20:44
*** berendt has joined #openstack-meeting20:44
*** ksavich_ has joined #openstack-meeting20:44
*** markstur has joined #openstack-meeting20:44
*** daneyon_ has joined #openstack-meeting20:44
*** gokrokve has joined #openstack-meeting20:44
*** SergeyLukjanov has joined #openstack-meeting20:44
*** VW_ has joined #openstack-meeting20:44
*** dgonzalez has joined #openstack-meeting20:44
*** mattgriffin has joined #openstack-meeting20:44
*** spandhe has joined #openstack-meeting20:44
*** jorge_munoz has joined #openstack-meeting20:44
*** jroll has joined #openstack-meeting20:44
*** yeungp has joined #openstack-meeting20:44
*** noslzzp has joined #openstack-meeting20:44
*** saurabhs has joined #openstack-meeting20:44
*** gyee has joined #openstack-meeting20:44
*** aranjan_ has joined #openstack-meeting20:44
*** bdpayne_ has joined #openstack-meeting20:44
*** eye_ has joined #openstack-meeting20:44
*** s3wong has joined #openstack-meeting20:44
*** angelamolock has joined #openstack-meeting20:44
*** penick has joined #openstack-meeting20:44
*** samueldmq has joined #openstack-meeting20:44
*** mtanino has joined #openstack-meeting20:44
*** leeantho has joined #openstack-meeting20:44
*** eghobo has joined #openstack-meeting20:44
*** suro_ has joined #openstack-meeting20:44
*** rmoe has joined #openstack-meeting20:44
*** jaypipes has joined #openstack-meeting20:44
*** liusheng has joined #openstack-meeting20:44
*** marun has joined #openstack-meeting20:44
*** ildikov has joined #openstack-meeting20:44
*** sarob has joined #openstack-meeting20:44
*** jlk has joined #openstack-meeting20:44
*** notmyname has joined #openstack-meeting20:44
*** alop has joined #openstack-meeting20:44
*** Leonr has joined #openstack-meeting20:44
*** rvasilets has joined #openstack-meeting20:44
*** noelbk has joined #openstack-meeting20:44
*** comay has joined #openstack-meeting20:44
*** rwsu has joined #openstack-meeting20:44
*** Riddhi has joined #openstack-meeting20:44
*** ogelbukh has joined #openstack-meeting20:44
*** ctlaugh has joined #openstack-meeting20:44
*** carl_baldwin has joined #openstack-meeting20:44
*** clarkb has joined #openstack-meeting20:44
*** thomasem has joined #openstack-meeting20:44
*** torgomatic has joined #openstack-meeting20:44
*** cdub has joined #openstack-meeting20:44
*** akuznetsova_ has joined #openstack-meeting20:44
*** rakhmerov has joined #openstack-meeting20:44
*** armax has joined #openstack-meeting20:44
*** dannywilson has joined #openstack-meeting20:44
*** timrc_ has joined #openstack-meeting20:44
*** varora- has joined #openstack-meeting20:44
*** sandywalsh_ has joined #openstack-meeting20:44
*** jecarey_ has joined #openstack-meeting20:44
*** j05h has joined #openstack-meeting20:44
*** amitgandhinz has joined #openstack-meeting20:44
*** IanGovett has joined #openstack-meeting20:44
*** AlanClark has joined #openstack-meeting20:44
*** andreaf_ has joined #openstack-meeting20:44
*** ddecapit has joined #openstack-meeting20:44
*** fnaval has joined #openstack-meeting20:44
*** jungleboyj has joined #openstack-meeting20:44
*** AmirBaleghi has joined #openstack-meeting20:44
*** jnrao has joined #openstack-meeting20:44
*** vijendar has joined #openstack-meeting20:44
*** rbak has joined #openstack-meeting20:44
*** etoews has joined #openstack-meeting20:44
*** ndipanov_gone has joined #openstack-meeting20:44
*** topol has joined #openstack-meeting20:44
*** dane_leblanc has joined #openstack-meeting20:44
*** cference has joined #openstack-meeting20:44
*** BrianB_ has joined #openstack-meeting20:44
*** changbl has joined #openstack-meeting20:44
*** bill_az has joined #openstack-meeting20:44
*** jckasper_ has joined #openstack-meeting20:44
*** cbouch has joined #openstack-meeting20:44
*** bknudson has joined #openstack-meeting20:44
*** doude has joined #openstack-meeting20:44
*** rushil has joined #openstack-meeting20:44
*** ccrouch has joined #openstack-meeting20:44
*** leifz has joined #openstack-meeting20:44
*** subscope has joined #openstack-meeting20:44
*** riwinters has joined #openstack-meeting20:44
*** weshay has joined #openstack-meeting20:44
*** amotoki has joined #openstack-meeting20:44
*** marg7175 has joined #openstack-meeting20:44
*** theanalyst has joined #openstack-meeting20:44
*** dguitarbite has joined #openstack-meeting20:44
*** stannie has joined #openstack-meeting20:44
*** tnurlygayanov has joined #openstack-meeting20:44
*** ijw has joined #openstack-meeting20:44
*** jyuso1 has joined #openstack-meeting20:44
*** jwang_ has joined #openstack-meeting20:44
*** pnavarro has joined #openstack-meeting20:44
*** mrunge has joined #openstack-meeting20:44
*** garyh has joined #openstack-meeting20:44
*** sbalukoff has joined #openstack-meeting20:44
*** mwagner_lap has joined #openstack-meeting20:44
*** mberlin has joined #openstack-meeting20:44
*** ChuckC has joined #openstack-meeting20:44
*** gabriel-bezerra has joined #openstack-meeting20:44
*** nagromlt has joined #openstack-meeting20:44
*** fifieldt has joined #openstack-meeting20:44
*** zhhuabj has joined #openstack-meeting20:44
*** asettle has joined #openstack-meeting20:44
*** martines_ has joined #openstack-meeting20:44
*** sorrison_ has joined #openstack-meeting20:44
*** niclem has joined #openstack-meeting20:44
*** plaurin_ has joined #openstack-meeting20:44
*** aweeks has joined #openstack-meeting20:44
*** julim has joined #openstack-meeting20:44
*** raildo has joined #openstack-meeting20:44
*** dneary has joined #openstack-meeting20:44
*** flwang1 has joined #openstack-meeting20:44
*** Tross1 has joined #openstack-meeting20:44
*** s0mik_ has joined #openstack-meeting20:44
*** killer_prince has joined #openstack-meeting20:44
*** Michalik_ has joined #openstack-meeting20:44
*** zhiyan has joined #openstack-meeting20:44
*** gchamoul has joined #openstack-meeting20:44
*** goodes has joined #openstack-meeting20:44
*** ameade_ has joined #openstack-meeting20:44
*** egallen has joined #openstack-meeting20:44
*** begal-sop has joined #openstack-meeting20:44
*** ctracey has joined #openstack-meeting20:44
*** lpeer__ has joined #openstack-meeting20:44
*** enikanorov__ has joined #openstack-meeting20:44
*** jgrimm has joined #openstack-meeting20:44
*** vishy has joined #openstack-meeting20:44
*** dhouck3 has joined #openstack-meeting20:44
*** maurosr has joined #openstack-meeting20:44
*** simonmcc has joined #openstack-meeting20:44
*** timello_ has joined #openstack-meeting20:44
*** esheffield has joined #openstack-meeting20:44
*** vhoward has joined #openstack-meeting20:44
*** jraim has joined #openstack-meeting20:44
*** eharney has joined #openstack-meeting20:44
*** social has joined #openstack-meeting20:44
*** gentux has joined #openstack-meeting20:44
*** erlon has joined #openstack-meeting20:44
*** alpha_ori has joined #openstack-meeting20:44
*** NikitaKonovalov has joined #openstack-meeting20:44
*** redrobot has joined #openstack-meeting20:44
*** brnelson has joined #openstack-meeting20:44
*** jcooley has joined #openstack-meeting20:44
*** SpamapS has joined #openstack-meeting20:44
*** schwicht has joined #openstack-meeting20:44
*** kairat_kushaev has joined #openstack-meeting20:44
*** jang1 has joined #openstack-meeting20:44
*** Adri2000 has joined #openstack-meeting20:44
*** tteggel has joined #openstack-meeting20:44
*** ilyashakhat has joined #openstack-meeting20:44
*** luis_fdez has joined #openstack-meeting20:44
*** skraynev has joined #openstack-meeting20:44
*** mitz has joined #openstack-meeting20:44
*** nsaje has joined #openstack-meeting20:44
*** mestery has joined #openstack-meeting20:44
*** lifeless has joined #openstack-meeting20:44
*** DuncanT has joined #openstack-meeting20:44
*** ayoung has joined #openstack-meeting20:44
*** nithyag__ has joined #openstack-meeting20:44
*** andreaf has joined #openstack-meeting20:44
*** mikal has joined #openstack-meeting20:44
*** marrusl has joined #openstack-meeting20:44
*** heyongli has joined #openstack-meeting20:44
*** mmedvede has joined #openstack-meeting20:44
*** jpeeler has joined #openstack-meeting20:44
*** sbadia has joined #openstack-meeting20:44
*** sdake has joined #openstack-meeting20:44
*** zz_ttrifonov has joined #openstack-meeting20:44
*** guitarzan has joined #openstack-meeting20:44
*** zul has joined #openstack-meeting20:44
*** masayukig has joined #openstack-meeting20:44
*** ianw has joined #openstack-meeting20:44
*** coolsvap|afk has joined #openstack-meeting20:44
*** troytoman has joined #openstack-meeting20:44
*** aleksandr_null_ has joined #openstack-meeting20:44
*** sgordon has joined #openstack-meeting20:44
*** krugg has joined #openstack-meeting20:44
*** ItSANgo_ has joined #openstack-meeting20:44
*** mtreinish has joined #openstack-meeting20:44
*** pradk has joined #openstack-meeting20:44
*** eren has joined #openstack-meeting20:44
*** anteaya has joined #openstack-meeting20:44
*** Swanson has joined #openstack-meeting20:44
*** jbryce has joined #openstack-meeting20:44
*** dteselkin has joined #openstack-meeting20:44
*** beagles has joined #openstack-meeting20:44
*** d0ugal has joined #openstack-meeting20:44
*** rharwood has joined #openstack-meeting20:44
*** peterstac has joined #openstack-meeting20:44
*** dansmith has joined #openstack-meeting20:44
*** dhellmann has joined #openstack-meeting20:44
*** lbragstad has joined #openstack-meeting20:44
*** a2hill has joined #openstack-meeting20:44
*** lvh has joined #openstack-meeting20:44
*** jgriffith has joined #openstack-meeting20:44
*** anish has joined #openstack-meeting20:44
*** esmute has joined #openstack-meeting20:44
*** B_Smith_ has joined #openstack-meeting20:44
*** crinkle has joined #openstack-meeting20:44
*** willroberts_ has joined #openstack-meeting20:44
*** annegentle has joined #openstack-meeting20:44
*** Adriano_ has joined #openstack-meeting20:44
*** enikanorov_ has joined #openstack-meeting20:44
*** xxj has joined #openstack-meeting20:44
*** rmk has joined #openstack-meeting20:44
*** dvorak has joined #openstack-meeting20:44
*** eikke_ has joined #openstack-meeting20:44
*** mrodden has joined #openstack-meeting20:44
*** docaedo has joined #openstack-meeting20:44
*** francois has joined #openstack-meeting20:44
*** markvan has joined #openstack-meeting20:44
*** krotscheck has joined #openstack-meeting20:44
*** arunkant has joined #openstack-meeting20:44
*** kashyap has joined #openstack-meeting20:44
*** marcoemo1 has joined #openstack-meeting20:44
*** dosaboy_ has joined #openstack-meeting20:44
*** joearnold has joined #openstack-meeting20:44
*** jemangs_ has joined #openstack-meeting20:44
*** rodrigods has joined #openstack-meeting20:44
*** david-lyle has joined #openstack-meeting20:44
*** toabctl has joined #openstack-meeting20:44
*** _elena_ has joined #openstack-meeting20:44
*** ityaptin has joined #openstack-meeting20:44
*** frobware has joined #openstack-meeting20:44
*** psedlak has joined #openstack-meeting20:44
*** kayaliu has joined #openstack-meeting20:44
*** isq has joined #openstack-meeting20:44
*** andreykurilin has joined #openstack-meeting20:44
*** aarefiev has joined #openstack-meeting20:44
*** ozamiatin has joined #openstack-meeting20:44
*** nealph_afk has joined #openstack-meeting20:44
*** jjmb has joined #openstack-meeting20:44
*** llu has joined #openstack-meeting20:44
*** shadower has joined #openstack-meeting20:44
*** zaneb has joined #openstack-meeting20:44
*** jdurgin has joined #openstack-meeting20:44
*** bauwser has joined #openstack-meeting20:44
*** dkranz has joined #openstack-meeting20:44
*** lsmola has joined #openstack-meeting20:44
*** coasterz has joined #openstack-meeting20:44
*** med_ has joined #openstack-meeting20:44
*** jmh has joined #openstack-meeting20:44
*** jehb has joined #openstack-meeting20:44
*** zehicle has joined #openstack-meeting20:44
*** devananda has joined #openstack-meeting20:44
*** mordred has joined #openstack-meeting20:44
*** pfalleno1 has joined #openstack-meeting20:44
*** kragniz has joined #openstack-meeting20:44
*** gilliard has joined #openstack-meeting20:44
*** eglynn-officeafk has joined #openstack-meeting20:44
*** rushiagr has joined #openstack-meeting20:44
*** jhesketh has joined #openstack-meeting20:44
*** jd__ has joined #openstack-meeting20:44
*** gothicmindfood has joined #openstack-meeting20:44
*** jeblair has joined #openstack-meeting20:44
*** kmartin has joined #openstack-meeting20:44
*** boris-42 has joined #openstack-meeting20:44
*** zigo has joined #openstack-meeting20:44
*** sigmavirus24 has joined #openstack-meeting20:44
*** marios has joined #openstack-meeting20:44
*** mdenny has joined #openstack-meeting20:44
*** xek has joined #openstack-meeting20:44
*** sileht has joined #openstack-meeting20:44
*** isviridov has joined #openstack-meeting20:44
*** aloga has joined #openstack-meeting20:44
*** alex_xu has joined #openstack-meeting20:44
*** cody-somerville has joined #openstack-meeting20:44
*** HenryG has joined #openstack-meeting20:44
*** hogepodge has joined #openstack-meeting20:44
*** gus has joined #openstack-meeting20:44
*** sc68cal has joined #openstack-meeting20:44
*** gpocentek has joined #openstack-meeting20:44
*** zeddii has joined #openstack-meeting20:44
*** bnemec has joined #openstack-meeting20:44
*** jrist has joined #openstack-meeting20:44
*** rromans has joined #openstack-meeting20:44
*** rhe00_ has joined #openstack-meeting20:44
*** cburgess has joined #openstack-meeting20:44
*** morganfainberg has joined #openstack-meeting20:44
*** yobber has joined #openstack-meeting20:44
*** mattoliverau has joined #openstack-meeting20:44
*** dougwig has joined #openstack-meeting20:44
*** skarn has joined #openstack-meeting20:44
*** otherjon has joined #openstack-meeting20:44
*** cebruns has joined #openstack-meeting20:44
*** briancline has joined #openstack-meeting20:44
*** sdague has joined #openstack-meeting20:44
*** darrenc has joined #openstack-meeting20:44
*** CaptTofu_ has joined #openstack-meeting20:44
*** asadoughi has joined #openstack-meeting20:44
*** pcarver has joined #openstack-meeting20:44
*** lynxman has joined #openstack-meeting20:44
*** mkoderer has joined #openstack-meeting20:44
*** vkmc has joined #openstack-meeting20:44
*** amakarov has joined #openstack-meeting20:44
*** loquacities has joined #openstack-meeting20:44
*** alaski has joined #openstack-meeting20:44
*** cgoncalves has joined #openstack-meeting20:44
*** mfedosin has joined #openstack-meeting20:44
*** morgabra has joined #openstack-meeting20:44
*** dkehn has joined #openstack-meeting20:44
*** dguerri has joined #openstack-meeting20:44
*** ahale has joined #openstack-meeting20:44
*** bogdando has joined #openstack-meeting20:44
*** wznoinsk has joined #openstack-meeting20:44
*** fc__ has joined #openstack-meeting20:44
*** pleia2 has joined #openstack-meeting20:44
*** gibi has joined #openstack-meeting20:44
*** nibalizer has joined #openstack-meeting20:44
*** toan has joined #openstack-meeting20:44
*** haleyb has joined #openstack-meeting20:44
*** pradipta_away has joined #openstack-meeting20:44
*** erw has joined #openstack-meeting20:44
*** mdavidson has joined #openstack-meeting20:44
*** abramley has joined #openstack-meeting20:44
*** anderstj has joined #openstack-meeting20:44
*** nonameentername has joined #openstack-meeting20:44
*** slagle has joined #openstack-meeting20:44
*** miguelgrinberg has joined #openstack-meeting20:44
*** rosmaita has joined #openstack-meeting20:44
*** davidlenwell has joined #openstack-meeting20:44
*** spredzy has joined #openstack-meeting20:44
*** zaro has joined #openstack-meeting20:44
*** BadCub has joined #openstack-meeting20:44
*** avozza has joined #openstack-meeting20:44
*** csd has joined #openstack-meeting20:44
*** ominakov has joined #openstack-meeting20:44
*** darvon has joined #openstack-meeting20:44
*** kevinbenton has joined #openstack-meeting20:44
*** ekarlso has joined #openstack-meeting20:44
*** dougshelley66 has joined #openstack-meeting20:44
*** antonym has joined #openstack-meeting20:44
*** jesusaurus has joined #openstack-meeting20:44
*** nikhil_k has joined #openstack-meeting20:44
*** asselin_ has joined #openstack-meeting20:44
*** blogan has joined #openstack-meeting20:44
*** jogo has joined #openstack-meeting20:44
*** achudnovets_ has joined #openstack-meeting20:44
*** funzo has joined #openstack-meeting20:44
*** flaper87 has joined #openstack-meeting20:44
*** fouxm has joined #openstack-meeting20:44
*** mfisch has joined #openstack-meeting20:44
*** bewiwi has joined #openstack-meeting20:44
*** s0nea has joined #openstack-meeting20:44
*** niska` has joined #openstack-meeting20:44
*** naotokl has joined #openstack-meeting20:44
*** radez_g0n3 has joined #openstack-meeting20:44
*** bdperkin has joined #openstack-meeting20:44
*** aignatov has joined #openstack-meeting20:44
*** complexmind has joined #openstack-meeting20:44
*** jseutter has joined #openstack-meeting20:44
*** DinaBelova has joined #openstack-meeting20:44
*** clayg has joined #openstack-meeting20:44
*** clds has joined #openstack-meeting20:44
*** wendar has joined #openstack-meeting20:44
*** timfreund has joined #openstack-meeting20:44
*** nijaba has joined #openstack-meeting20:44
*** intr1nsic has joined #openstack-meeting20:44
*** jamespage has joined #openstack-meeting20:44
*** gduan has joined #openstack-meeting20:44
*** shardy has joined #openstack-meeting20:44
*** jcook has joined #openstack-meeting20:44
*** dstanek has joined #openstack-meeting20:44
*** hockeynut has joined #openstack-meeting20:44
*** insequent has joined #openstack-meeting20:44
*** adam_g has joined #openstack-meeting20:44
*** cschwede has joined #openstack-meeting20:44
*** otoolee has joined #openstack-meeting20:44
*** fungi has joined #openstack-meeting20:44
*** dolphm has joined #openstack-meeting20:44
*** jacorob has joined #openstack-meeting20:44
*** ttx has joined #openstack-meeting20:44
*** hugokuo has joined #openstack-meeting20:44
*** zz_johnthetubagu has joined #openstack-meeting20:44
*** sweston has joined #openstack-meeting20:44
*** vipul has joined #openstack-meeting20:44
*** sfineberg has joined #openstack-meeting20:44
*** juice has joined #openstack-meeting20:44
*** lxsli has joined #openstack-meeting20:44
*** chmouel has joined #openstack-meeting20:44
*** tonyb has joined #openstack-meeting20:44
*** mrda-away has joined #openstack-meeting20:44
*** sendak.freenode.net sets mode: +bbbb *!a2fd8292@gateway/web/cgi-irc/kiwiirc.com/ip.162.253.130.146 LLKCKfan!*@* *!*@*/188.47.119.39 *!~rongze@*20:44
*** sendak.freenode.net changes topic to "Project structure reform (Meeting topic: tc)"20:44
*** ChanServ sets mode: +o openstack20:44
ttx#topic Review openstack-specs approval rules20:44
ttxTwo weeks ago we (well, mikal) fast-approved the log guidelines cross-project spec20:44
ttxdhellmann raised that we should have been using "normal TC voting procedures" for that repo20:44
*** joel-coffman has quit IRC20:44
*** openstack changes topic to "Review openstack-specs approval rules (Meeting topic: tc)"20:44
ttxThe original decision on this repo was that any TC member has R+2/W+1 on that repository and could basically tally the votes and rubberstamp consensus20:44
*** padkrish has quit IRC20:44
ttxI'm fine with switching this to normal voting rules (7 YES, or at least 5 YES and more YES than NO)20:44
ttxBut then I'm not sure how we can express that in Gerrit without removing everyone's ability to -120:45
ttxBasically, how do TC members say "NO" ? -2 is a bit of a veto, not a NO.20:45
dhellmannjeblair was going to investigate gerrit config options, right?20:45
*** cbouch has quit IRC20:45
jeblairdhellmann: yes, and i failed due to flying around to conferences and meetings too much :(  i am sorry.20:46
ttxjeblair: should we table this until you get a chance to investigate that ?20:46
sdagueso, honestly, I'm not sure why normal rules are bad. I can get behind stripping +A back to ttx if that's what we want, but I kind of think -2 veto is a feature here20:46
dhellmannjeblair: np20:46
ttxsdague: so you don't want classic TC approval rules20:46
sdaguebecause, really, if a TC member feels that strongly against it, that should stop this20:46
ttxyou want a tweaked version with veto possibility20:46
ttxI'm fine with that20:46
dhellmannsdague: my point was I think we want more than two +2 votes before approval20:46
*** ajo has quit IRC20:47
ttxit's just NOT normal voting rules, that's something else we need to define20:47
ttxCould be at least 7 +2, no -220:47
dhellmannI'm less concerned with vetos, I guess.20:47
*** ddecapit has quit IRC20:47
ttxthat would be easily impletable20:47
ttximplement-able20:48
jeblairif we can come up with requirements like "tc votes visible, tc can/can not veto" etc20:48
jeblairthat would help20:48
*** roaet has left #openstack-meeting20:48
*** angelamolock has quit IRC20:48
jeblairwe do have more options in gerrit than last time we looked at something like this20:48
ttxdhellmann: would "at least 7 +2, no -2" work for you ?20:48
dhellmannjeblair: it sounds like we're circling around the rules we have now, but requiring more +2 before the workflow+1 is enabled20:48
ttxi.e. 7 approvals, no veto20:48
dhellmannttx: yeah, that sounds good20:48
*** ivar-lazzaro has quit IRC20:48
*** markmcclain has quit IRC20:48
dhellmannI thought that's what we were operating with, just doing it by consensus rather than having the tool configured that way20:49
ttxthe difference with "normal voting rules" is that a single -2 can block it, but then like sdague said, it's probably a goiod thing here20:49
dhellmannyeah, I'm willing to go with that20:49
*** ivar-lazzaro has joined #openstack-meeting20:49
russellbwfm, too20:49
mordred++20:49
* dhellmann wonders if anything we do is actually "normal"20:49
*** mrunge has quit IRC20:49
sdagueyeh, I'm fine with that20:49
ttxdhellmann: normal as in "carved in stone in the TC charter"20:49
jeblairi'm pretty sure we can do that either way (veto or not veto), so decide based on what we want, not what our current rules are set up for20:49
ttx#agreed switch openstack-specs approval rules to  "at least 7 +2, no -2"20:50
* jeblair is puzzled20:50
ttxjeblair: we'll probably want to restrict Workflow+1 to tc-chair20:50
*** hemna has quit IRC20:50
jeblairi'm not sure how a tc member is expected to express dissent20:51
ttx-1 ?20:51
sdaguejeblair: -120:51
jeblairand we are not concerned that is indistingushable from any other -1?20:51
*** markmcclain has joined #openstack-meeting20:51
jeblairand are tc members permitted to -2?20:52
sdagueI'm not, we can read the votes20:52
ttxwell, since you need 7 YES for approval, not voting is pretty much the same as -120:52
*** annegent_ has quit IRC20:52
sdaguejeblair: yes20:52
ttxjeblair: yes, to express veto20:52
jeblairand we have no desire to make the tc votes visible as such?20:52
*** rushiagr is now known as rushiagr_away20:53
*** asalkeld has joined #openstack-meeting20:53
jeblairand we _want_ the tc veto, that's not just a compromise based on current configuration?20:53
ttxjeblair: that is how I understand it20:53
*** radez_g0n3 is now known as radez20:53
jeblairbecause i'm pretty sure we can set it up so that tc votes are distinguished from other votes and would not act as a veto20:53
sdagueI personally think the TC veto is important20:53
ttxsdague said: "I kind of think -2 veto is a feature here"20:53
*** liusheng has quit IRC20:54
dhellmannjeblair: https://review.openstack.org/15058120:54
sdagueI don't think that approving a spec over the strong objection of a TC member is a thing we want to do20:54
mordredjeblair: ++20:54
sdaguethat means we failed somewhere else20:54
dhellmannsdague: +120:54
jeblairsdague: i agree it means we failed, i do not agree that we should enable tc members to veto20:54
*** pboldin has quit IRC20:54
ttxif we can't agree between us, how do we expect all PTLs to fall in line with the spec20:54
mordredyah - but we can make the category have -3 as a low bounds, still let TC members vote -2 to  have it not be binding20:54
jeblairwe don't have a veto anywhere else20:54
jeblairi don't know why we're adding it here20:54
*** sparkycollier has quit IRC20:54
jeblairi would veto this suggestion if i could20:54
mordredand I agree with jeblair that I think veto is not actually desired20:54
jeblairbut i can not20:54
mordredjeblair: ++20:55
sdagueall the specs teams have vetos on it20:55
ttxhah20:55
ttxstill time to20:55
ttx#undo20:55
openstackRemoving item from minutes: <ircmeeting.items.Agreed object at 0x2d1f510>20:55
ttxsince we are not agreeing20:55
*** akuznetsov has joined #openstack-meeting20:55
*** annegent_ has joined #openstack-meeting20:55
mordredthis is the TC - not a spec vote - we don't have a veto concept here20:55
dhellmannbut these *are* specs20:55
sdaguebut it's a specs repo20:55
jeblairand when things get contentious, i want us to be able to navigate a way out of it20:55
*** kebray has joined #openstack-meeting20:56
mordredsdague: yes - but we don't approve things with any 2 +2's - we do it by majority vote20:56
sdagueyes, and running over members I don't think is that20:56
*** liusheng has joined #openstack-meeting20:56
*** kebray has quit IRC20:56
mordredwe can still have dissenting votes and often do have at least one or two20:56
sdaguemordred: that's a definition of the governance repo based on it replacing in meeting votes20:56
mordredand I _do_ think it's important to capture and display that  TC member dissented20:56
ttxhmm, looks like we can push this to a thread and clarify the requirements20:56
*** cference has quit IRC20:56
ttxI'd like to cover one more thing in this meeting20:57
mordredttx: ++20:57
ttx#action ttx to raise thread to continue discussion on openstack-specs approval20:57
mordredjust saying - there are more options available to us than we provide to other repos20:57
ttx#topic Open discussion20:57
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:57
ttxI'd like to start the L naming poll this week20:57
russellbyay20:57
ttxWe've been trying with Anita to add first nation names (lilwat or lilooet) to the mix, but for that we need explicit permission from the tribe20:57
ttxAnd we haven't received an answer yet20:57
ttxDo you think we can wait until next week ? Or do we need the name now ?20:57
anteayaI've emailed no response20:57
anteayafirst nations work on their own concept of time20:58
ttxwe can't wait forever, people started to complain20:58
anteayaI don't haev much hope waiting another week will net any useful results20:58
ttxCurrent set is Lizard, London, Liberty, Love20:58
anteayathey haven't acknowledged my email20:58
ttxI'd like to quickcheck that we have at least one TC member supporting every of those names, since the final short list is supposedly our pick20:58
jeblairif the cross-project specs is a function of the tc, it should operate in the same way as the rest of the tc, otherwise i think it loses legitimacy20:58
ttxno need to put in the poll a name nobody would rather not have. I know London and Lizard have supporters, what about Love and Liberty ? I know some people hate those.20:58
jeblair(sorry, i typed most of that before the topic change)20:59
* dhellmann plans to vote London just to be confusing20:59
* ttx supports Lizard20:59
*** stevebak` is now known as stevebaker20:59
vishyi like all the options20:59
ttxanyone up to support Love or Liberty20:59
* russellb supports Love20:59
* anteaya hates Liberty as it is american not canadian20:59
*** rushiagr_away is now known as rushiagr20:59
dhellmannanteaya: ?20:59
anteayaliberty is american20:59
fungianteaya: it only seems american. we don't _actually_ have any either20:59
mordredI'm not thrilled with the list, nor that it's pre-culled20:59
ttxvishy: do you like all the options enough to vouch for Liberty ?21:00
* jeblair plans on calling it lemming anyway21:00
anteayafungi: heh21:00
vishyfungi: wp, wp21:00
* dhellmann follows jeblair 21:00
vishysure21:00
ttxmordred: we plan to address that, I talked with jogo on clarifying the process21:00
vishyi will vouch for liberty21:00
ttxOK then21:00
ttxAnd shall we wait another week ?21:00
mordredttx: I would like to not clarify the process as much as I would like this to not be a marketing exercise21:00
mordredand instead a function of our technical community21:00
mordredthat is, as it should be, fun21:00
vishyis there any reason we can’t do a two phase poll with all options?21:01
vishyis the issue trademark conflicts?21:01
ttxWe need to close the meeting ? Wait another week ?21:01
ttxvishy: yes21:01
dhellmannttx: yeah, let's wait21:01
ttxOK21:01
ttxthx21:01
ttx#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
* jogo wants Lizard21:01
openstackMeeting ended Tue Jan 27 21:01:41 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
*** markmcclain has quit IRC21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-01-27-20.03.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-01-27-20.03.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-01-27-20.03.log.html21:01
*** hashar has joined #openstack-meeting21:01
*** ijw has quit IRC21:02
bknudsongo with cloud formations -- lenticular21:02
*** SergeyLukjanov has quit IRC21:02
ttxcourtesy PTL ping: dhellmann, morganfainberg, notmyname, eglynn, nikhil_k, thingee, asalkeld, david-lyle, mestery, SlickNik, SergeyLukjanov, mikal: around ?21:02
fungiprobably already taken by someone's cloud product21:02
dhellmanno/21:02
mesteryo/21:02
russellbbknudson: heh, there are (self imposed) rules around what is a valid candidate21:02
david-lyleo/21:02
*** zehicle_ has quit IRC21:02
notmynamehello21:02
asalkeldo/21:02
morganfainbergo/21:02
sigmavirus24o/21:02
russellbbknudson: find a place called that in BC, Canada :)21:02
* ttx longs the blessed time where we would decide the name on a whiteboard at the end of the design summit21:03
ttx(Cactus)21:03
eglynno/21:03
ttx#startmeeting crossproject21:03
openstackMeeting started Tue Jan 27 21:03:47 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:03
*** openstack changes topic to " (Meeting topic: crossproject)"21:03
openstackThe meeting name has been set to 'crossproject'21:03
morganfainbergmake people submit ideas at the summit, tally things up at the end.21:03
*** evgenyf has quit IRC21:03
morganfainberg:P21:03
ttxOur agenda for today:21:03
ttx#link http://wiki.openstack.org/Meetings/CrossProjectMeeting21:04
ttxsigmavirus24: around?21:04
*** dulek has quit IRC21:04
*** hemna has joined #openstack-meeting21:04
ttxoh I see you above21:04
sigmavirus24I am21:04
ttx#topic Cross-project DevRef akin to Nova's (@sigmavirus24)21:04
*** raildo is now known as raildo_away21:04
*** openstack changes topic to "Cross-project DevRef akin to Nova's (@sigmavirus24) (Meeting topic: crossproject)"21:04
ttx#link http://docs.openstack.org/developer/nova/devref/development.environment.html21:04
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2015-January/054837.html21:04
sigmavirus24So we discussed this on the mailing list a bit already (thank you ttx)21:05
ttxsigmavirus24: I'll let you introduce the topic21:05
sigmavirus24The basic idea is to have a cross-project reference of the basic requirements to begin developing with/on any of the projects21:05
sigmavirus24Then have a way for each project to list additional dependencies and system setup21:05
lifelesssdague: haypo was working on it21:05
*** SergeyLukjanov has joined #openstack-meeting21:05
*** fnaval has quit IRC21:05
sigmavirus24At this point, what we could use are people willing to help with each project's (sub?)reference and to get the base document started. Also guidance as to where this should live21:06
*** fnaval has joined #openstack-meeting21:06
*** otter768 has joined #openstack-meeting21:06
*** joesavak has quit IRC21:07
asalkeldsigmavirus24, openstack-manual ?21:07
*** ccrouch has left #openstack-meeting21:07
mesteryasalkeld: ++, that's a good spot.21:07
eglynnso is the idea that we list out the super-set of all setup required to develop on *any* project?21:07
sigmavirus24eglynn: right. Most projects have common system dependencies21:07
*** eye_ has quit IRC21:08
eglynnsigmavirus24: sounds reasonable21:08
asalkeldand i'd assume we would have some hooks so we could have some differences in-tree?21:08
annegent_I think it could live in openstack-manuals but the audience is contrib devs so openstack-manuals isn't for that group. I'd say start a new repo21:08
sigmavirus24annegent_: that's what I thought21:08
dhellmannanteaya: where is the infra-manual being published?21:08
annegent_like the infra-manual is a separate repo21:08
sigmavirus24asalkeld: I think the idea would be to have some sub-sections or separate pages for each individual project21:08
annegent_dhellmann: docs.openstack.org/infra-manual21:08
*** evgenyf has joined #openstack-meeting21:08
anteayadocs.openstack.org/infra/manual21:09
*** yapeng has joined #openstack-meeting21:09
dhellmannannegent_: thanks21:09
annegent_sorry http://docs.openstack.org/infra/manual/21:09
dhellmannanteaya: thanks :-)21:09
annegent_heh21:09
*** padkrish has joined #openstack-meeting21:09
anteaya:)21:09
asalkeldsigmavirus24, i'd rather you link to project pages21:09
dhellmannthere is a developer guide in the infra manual: http://docs.openstack.org/infra/manual/developers.html21:09
dhellmannlet's add to that21:09
annegent_sigmavirus24: figure out how to include content from separate repos while you're at it :)21:09
asalkeldcentral docs are more work to add to21:09
dhellmannand let's not put project-specific stuff in the projects because as a new dev OMG that's a pain to flip back and forth21:09
sigmavirus24annegent_: hm. I have an instinct on how to do that but have never tested it =P21:09
dhellmannand really, if our instructions aren't "run devstack once" then meh21:10
annegent_sigmavirus24: try it, you'll like it, then show me how21:10
asalkeldwe already have docs: http://docs.openstack.org/developer/heat/getting_started/index.html21:10
sigmavirus24dhellmann: yeah that was a worry of mine21:10
asalkeldjust link to those (and we remove common stuff)21:10
annegent_dhellmann: it's really about concepts and then troubleshooting21:10
eglynnwould we need a volunteer per-project-per-distro to validate the setup?21:10
eglynn(e.g. one who normally develops ceilo on fedora20, another for ceilo/trusty etc.)21:10
sigmavirus24eglynn: yeah that's the part that Nova's DevRef doesn't handle21:11
*** otter768 has quit IRC21:11
eglynnk21:11
sigmavirus24And that may be harder to maintain21:11
dhellmannannegent_: ok, but if we have instructions for doing something and a tool that does it, they're going to diverge pretty quickly21:11
*** evgenyf has quit IRC21:11
annegent_dhellmann: I think we agree :)21:12
dhellmannannegent_: huzzah! :-)21:12
*** kebray has joined #openstack-meeting21:12
*** evgenyf has joined #openstack-meeting21:12
annegent_per distro is not easy, take it from the install guide experience21:12
*** stevelle has joined #openstack-meeting21:13
sigmavirus24I've heard stories of the per-distro problems in the install guide21:13
annegent_sigmavirus24: it ain't easy21:13
*** yapeng has quit IRC21:13
sigmavirus24dhellmann: but there's also the difference of: "install these dependencies system wide and then get going" and "run devstack for 40 minutes then get started"21:13
sigmavirus24If we're going to tell people to use devstack to set up their systems for development, we should probably make it easier to install the system deps without running ./stack.sh21:14
dhellmannsigmavirus24: I suppose.21:14
morganfainbergmaybe the right answer is to keep the basic starter docs in devstack purview.21:14
ttxI fail to feel disturbance in the Force. Does that mean there is mostly consensus on this topic and we should spend our time on more conflictual issues ?21:14
fungimaybe that's where the docker-oriented dev/devstack environments have a leg up. start this in a container, then hack21:14
morganfainbergsince devstack needs to know how to do all of that anyway21:14
dhellmannsigmavirus24: that's a good idea, maybe a separate script in the devstack repo?21:14
sigmavirus24dhellmann: yeah21:14
morganfainbergdhellmann, ++21:14
sigmavirus24I'm all for that21:14
notmynamewhat if, instead of one (base) document that describes how to set up a dev environment, we instead had one template for how these look and then leave them to the individual projects?21:14
* dhellmann pictures only slightly less confusion than we have now21:15
eglynnif not explicitly per-distro, then at least e.g. "yum install libffi-devel (or the equivalent package for your distro)"?21:15
*** rushiagr is now known as rushiagr_away21:15
asalkeldimho if this is docs on how to run devstack, the docs should just be in devstack21:16
annegent_I wish reed were around to weigh in. He fields all kinds of questions about devstack21:16
funginot long ago i looked at the degree to which contributing.md et cetera diverged across our projects. basically they mostly fork from whatever the satte is in the cookiecutter repo and then head off in their own individual directions21:16
dhellmannmost of these instructions shouldn't be different between the projects, right? "Here's how to find the list of packages to install" or "Here's the tool to install the packages"21:16
dhellmann"here's how to run tests"21:16
annegent_but it's not just devstack, it's a dev environment, building docs, and running tests.21:16
dhellmann"here's how to run the debugger"21:16
eglynnthis is not just devstack, amiright? ... also folks who want to just run "tox -epy27" to run units21:16
dhellmannthat should all work the same, with only the service names changing21:16
morganfainbergdevstack feels like the right place for something like this instead of trying to keep data in now (how many projects?) in sync or even adding just 1 more place, devstack and wherever it is now and then this new place21:17
annegent_heh. you type faster21:17
sigmavirus24eglynn: right21:17
morganfainbergit seems like the data will never be in sync.21:17
sigmavirus24== morganfainberg21:17
dhellmanneglynn: on most projects, you need system packages for the python requirements to install21:17
sigmavirus24libmysql++, libssl, etc. are all necesary21:17
eglynndhellmann: yep, exactly21:17
fungiand the names of those packages differ across distro families and releases21:17
sigmavirus24or required to different degrees21:17
*** atiwari1 has quit IRC21:17
eglynnfungi: precisely my thought above21:18
funginame and count of packages in some cases21:18
*** neelashah has quit IRC21:18
dhellmanneglynn, fungi : and so it is simpler to tell people to use a tool to install them than to write directions for doing it all differently21:18
*** ijw has joined #openstack-meeting21:18
fungi(e.g. some distros split out packages which others keep more monolithic)21:18
dhellmanncurrently, the best tool is devstack, but I do like the idea of splitting that feature out21:18
fungidhellmann: i have no idea which is easier honestly. neither is trivial21:18
eglynndhellmann: yep, great if someone is willing to maintain such a tool21:18
*** atiwari1 has joined #openstack-meeting21:18
eglynn(standing alone from devstack)21:18
morganfainbergif devstack used that tool to install21:18
dhellmannmorganfainberg: right21:19
morganfainbergi think it would make it required to keep up to date21:19
asalkeldhttps://github.com/openstack-dev/devstack/tree/master/files ?21:19
*** madskier has quit IRC21:19
morganfainbergrather than "we hope it stays in sync"21:19
dhellmannasalkeld: right21:19
sigmavirus24morganfainberg: I think that was that was what I imagined for the tool21:19
*** jhenner has joined #openstack-meeting21:19
fungilifeless started on his bindep project a couple years back now, to try to provide a structured mechanism for declaring these sorts of dependencies across distros21:19
sigmavirus24I should have verbalized that though :)21:19
*** SlickNik has joined #openstack-meeting21:19
fungimight be a good place to try to incorporate that sort of logic21:19
*** vigneshvar has quit IRC21:20
asalkeldso doesn't devstack automatically installing this stuff?21:20
dhellmannasalkeld: it does, but the request was for a tool that doesn't do all of the other things devstack does21:20
asalkeldwhy are we documenting it as a manual step?21:20
ttxthe anvil stuff from harlowja had a few ways to encode deps in a distro-agnostic way too21:20
fungi#link http://git.openstack.org/cgit/stackforge/bindep21:20
sigmavirus24yes. splitting that part out of devstack so you don't have to run ./stack.sh is what I imagine will be the best way of moving this forward21:20
dhellmannasalkeld: my point exactly :-)21:21
*** roaet has joined #openstack-meeting21:21
asalkeldreally? odd21:21
*** gokrokve has quit IRC21:21
ttxHmm, obviously this requires more discussion, but we can't dedicate all the meeting to that21:21
sigmavirus24mriedem was the one to suggest this first in glance so this is why it's come up21:21
sigmavirus24right.21:21
harlowjahttps://github.com/stackforge/anvil/blob/master/conf/distros/redhat.yaml if people care :-P21:21
sigmavirus24ttx:  feel free to move on. Maybe we'll get more responses on the ML now =P21:21
ttxHow about someone picks up the thread and continues the discussion there21:21
dtroyer_zzfwiw. tools/install_prereqs.sh exists in devstack to do a lot of the system deps21:21
ttxsigmavirus24: triggering interest in ML thread is one of the goals of this meeting indeed21:22
ttxOK, let's move on21:22
dhellmanndtroyer_zz: cool21:22
*** kurtmartin has joined #openstack-meeting21:22
ttxPlease followup on the thread if you care21:22
*** nellysmitt has joined #openstack-meeting21:22
ttx#topic Avoiding private symbols in Oslo libraries (dhellmann)21:22
*** openstack changes topic to "Avoiding private symbols in Oslo libraries (dhellmann) (Meeting topic: crossproject)"21:22
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2015-January/054810.html21:22
ttxdhellmann: around?21:22
dhellmann#link https://review.openstack.org/#/c/150118/21:22
ttxThis feels more and more like Lightning Talks21:23
dhellmannI wanted to raise this mostly to make sure you had all seen the thread.21:23
bknudsonwe've all done it -- used private symbols21:23
*** roaet has quit IRC21:23
dhellmannAfter we're done with the namespace package moves, we're not going to hold up releases of oslo libs because of unit test breakages in other projects.21:23
bknudsonsometimes because they were that way from oslo-incubator days21:23
*** roaet has joined #openstack-meeting21:23
*** padkrish has quit IRC21:24
asalkelddhellmann, that sounds fine21:24
dhellmannWe'll work with everyone to add fixtures and other APIs as needed as we continue graduations, but for existing stuff we're going to keep moving ahead with cleanups and fixes.21:24
ttxdhellmann:  that sounds fair21:24
*** padkrish has joined #openstack-meeting21:24
dhellmannThat's all I had, unless anyone has questions about it.21:25
eglynndhellmann: not going to hold up releases of oslo libs because of unit test breakages in other projects, where those breakages are caused by usage of oslo private symbols?21:25
dhellmanneglynn: yes, that's right21:26
eglynn(i.e. as opposed to being caused by say an API contract change)21:26
eglynncoolness :)21:26
ttxother questions on that ?21:26
notmynameany migration plan?21:26
dhellmannnotmyname: migration?21:26
notmynamejust tell projects to stop and make them change? or is there a plan for supporting stuff currently in use by published libraries?21:27
dhellmannnotmyname: symbols already clearly marked as private are off-limits. New symbols will be clearly marked.21:27
notmynameok21:27
ttxok, moving on21:27
*** ajo has joined #openstack-meeting21:28
ttx#topic Discuss the importance of getting cross-project reviews of guidelines and how to best go about getting those reviews for the API Working Group (etoews)21:28
*** openstack changes topic to "Discuss the importance of getting cross-project reviews of guidelines and how to best go about getting those reviews for the API Working Group (etoews) (Meeting topic: crossproject)"21:28
bknudsonit's usually pretty easy to change the test to use public symbols instead.21:28
*** stevemar has quit IRC21:28
ttxetoews: o/21:28
etoewshi21:28
etoewsin case anyone isn't familiar with our working group yet...21:28
etoews#link https://wiki.openstack.org/wiki/API_Working_Group21:28
ttxExample guidelines @ https://review.openstack.org/#/c/145579/21:28
*** stevemar has joined #openstack-meeting21:28
*** nellysmitt has quit IRC21:29
etoewsya. so that one turned out reasonably well so far.21:29
asalkeldetoews, is this what our cross project liaison should be doing?21:29
etoewsright21:29
*** padkrish has quit IRC21:29
bknudsonlooks like that one has a lot of reviews and from the right people.21:29
etoewsthe wg also needs to do a better job of reaching out to the CPLs21:29
etoewsbknudson: for that one yes.21:30
eglynnis this voting scheme in force? https://review.openstack.org/#/c/131358/6/doc/source/process.rst21:30
etoewsbut then look at https://review.openstack.org/#/c/141229/21:30
*** sparkycollier has joined #openstack-meeting21:30
eglynn"Once the matter has been discussed there should be no more than 20% (of votes cast) -1 votes."21:30
ttxOne question that comes to mind is should that type of guidelines be retrofitted into an openstack-specs, or do we need two repositories ?21:30
etoewseglynn: yep. that merged. http://specs.openstack.org/openstack/api-wg/process.html21:30
etoewsttx: i think one repo for the time being21:31
dhellmannttx: using the specs repo feels fine21:31
morganfainbergi like the spec repo as a place for this21:32
dhellmannwe're doing something similar with oslo policies: https://review.openstack.org/#/q/status:open+project:openstack/oslo-specs+branch:master+topic:policy,n,z21:32
ttxdhellmann: it's using the  openstack/api-wg repo for now21:32
*** vigneshvar has joined #openstack-meeting21:32
*** baoli has joined #openstack-meeting21:32
ttxbasically, this repo serves both to help draft the guidelines and get it out to be implemented21:32
dhellmannttx: hmm, I hadn't noticed that21:33
ttxwhile we do some of the latter already in openstack-specs21:33
* dhellmann doesn't like the new gerrit UI :-/21:33
ttxhence my question on the potential duplication21:33
fungii lobbied to just use the openstack/specs repo for it originally, but was in the minority21:33
eglynncan we clarify where these guidelines lie on the spectrum ranging from "friendly advice" to "hard mandate"?21:33
ttxfungi: I still think the workgroup needs a place to hack and draft their docs21:33
* eglynn fears that "friendly advice" tends to be respectfully ignored21:33
fungittx: yep, that was a fair counterargument21:34
dhellmannI thought the api-wg repo was going to be for them to draft proposals, but they wouldn't be applied until they were approved in the specs repo. That feels like we're adding extra overhead, now that we have used the specs repo a bit21:34
ttxI'm just wondering if making them stay forever in api-wg doesn't limit the reach/audience needed for the second step21:34
ttxdhellmann: agreed, just checking if that's still the plan21:34
etoewseglynn: at this point they are guidelines, not hard mandate.21:34
ttxbasically I saw the CLI sort thing and ignored the API sort thing21:34
*** dboik has quit IRC21:35
etoewshmmmm...sounds like the specs repo would give us more viz21:35
ttxetoews: do you plan to push them more as mandates ? In which case you would use the specs repo ?21:35
*** harlowja has quit IRC21:35
*** jhenner has quit IRC21:36
ttxI guess if they stay "recommendations" or "guidelines" they could still live in a specific repo21:36
etoewsso far the way most reviews have worked out is that everytime we use the word "must" in a guideline, someone comments to change it to "should"21:36
*** kurtmartin has quit IRC21:36
ttxheh21:36
ttxrings a bell21:36
*** jhenner has joined #openstack-meeting21:36
etoewseven if they were mandated, that "should" give people the wiggle room they want/need.21:37
notmynames/should/may/21:37
etoewsit's basically the language of rfcs21:37
etoewsi'm all for more visibility though. that's why i'm here.21:37
eglynnat one point there was a suggestion that the TC would add some weight to these "recommendations" by explicitly adding their imprimatur21:38
ttxOK, so we have two options for more viz21:38
eglynn... is that still the plan?21:38
*** liusheng has quit IRC21:38
ttxone is just to rpeach that CPLs and PTLs and everyone else should weigh in on api-wgh proposed changes21:38
ttxpreach*21:38
etoewseglynn: see #5 of http://specs.openstack.org/openstack/api-wg/process.html21:38
*** ebalduf has joined #openstack-meeting21:38
*** liusheng has joined #openstack-meeting21:39
ttxtwo is to turn those at some point into API recommendations that would be proposed as openstack-specs21:39
eglynnetoews: a-ha, cool, thanks21:39
ttx(and use api-wg to draft the doc)21:39
*** sabari has joined #openstack-meeting21:39
notmynamehow in the world is that reasonable or scalable with a bit-tent openstack project?21:39
notmyname*big21:39
etoewsttx: those are the option i see21:39
ttxnotmyname: api recommendations ? or openstack-specs ?21:40
*** ijw has quit IRC21:40
ttxetoews: any preference ?21:40
*** Mandell has quit IRC21:40
notmynamettx: the api recommendations along the should to must range. basically finding a One True API that works across all of these projects21:40
etoewsi don't want to speak for the whole wg.21:40
etoewslet me take this back to them. we have a meeting on thursday.21:41
*** _nadya_ has quit IRC21:41
ttxetoews: maybe bring back the two options to them ?21:41
ttxok21:41
etoewsi'll update the cross-project meeting next week.21:41
ttxetoews: sounds good21:42
ttxnotmyname: I don't think they are up to defining a "One True API", mostly about suggesting that the details like sorting are implemented in a coherent way21:42
*** esheffield has quit IRC21:42
etoewsttx: +1 and consistent too21:42
ttxwhich sounds valuable, especially as we add more projects21:43
ttxok, one or two more topics to cover21:43
*** evgenyf has quit IRC21:43
ttxmoving on -- if more complaints about the APi WG goals, that should be raised as a specific thread I think21:43
ttx#topic Progress (or lack thereof) on providing default config files21:44
*** openstack changes topic to "Progress (or lack thereof) on providing default config files (Meeting topic: crossproject)"21:44
ttxin our Dec 16 meeting we discussed the best way to provide "default" config files for projects21:44
ttxThere were lots of solutions proposed, but not real clear single roblem we were trying to solve21:44
ttxThe outcome was to push the discussion to the operators ML to get a clearer sense of the problem we need to solve21:44
fungiyep, and i summarized the discussion on the ops ml21:44
ttxand/or start a cross-project spec21:44
ttxWe also scheduled a status update before end of January, so here we are...21:44
fungi#link http://lists.openstack.org/pipermail/openstack-operators/2014-December/005742.html21:44
ttxfungi: do you have some summary to share ?21:44
fungithat thread sort of petered out without any solid direction21:44
fungii also talked with fifieldt a little and his take was that from the operators he talks to, they wanted config files in git repos21:45
fungifull stop21:45
ttxwould you say it failed to reach the required level of interest on that list ?21:45
fifieldtnot at all :)21:45
fungiwhich someone in the ops community just started doing21:46
ttxor that the Christmas break made it drown ?21:46
fifieldtit's that the options as presented were ill formatted for the audience, ttx21:46
fungi#link http://lists.openstack.org/pipermail/openstack-operators/2015-January/005981.html21:46
asalkeldwell we could go back to generating the config's - just not gating on the results?21:46
*** gokrokve has joined #openstack-meeting21:46
*** cference has joined #openstack-meeting21:46
ttxfifieldt: the effort is stalled again -- what's the best way to make progress there ?21:46
fungiright, i can grasp that we presented technical options to operators and the implication i guess is that they're non-technical creatures?21:46
dhellmannasalkeld: the options available to a deployment depend on the versions of libraries installed *at that deployment* and not just on the application21:47
fifieldtnot technical vs non technical - just "don't care about implementation details" :)21:47
asalkelddhellmann, we provide the global requriements21:47
fungiokay, so they don't care enough about how we solve it to tell us what specifically they need, but care enough to complain when we don't provide what they need?21:47
dhellmannasalkeld: with ranges of versions21:47
asalkelddoubt they really vary that much21:47
morganfainbergbut the view was they want sample configs in git [regardless of how it gets there]?21:47
asalkeldseems like a slim arguemnent21:47
fifieldt* A git repository that has raw, sample configs in it for each project21:47
fifieldtthat will be automagically updated21:47
fifieldt* Raw configs distributed in the tar files we make as part of the release21:47
fifieldtthat's basically it21:48
ttxfifieldt: that's an OR or an AND ?21:48
*** kurtmartin has joined #openstack-meeting21:48
fifieldtand21:48
ttx(non technical question)21:48
ttx:)21:48
*** Sukhdev has quit IRC21:48
*** ijw has joined #openstack-meeting21:48
ttxfungi: I haven't followed the thread, but is fifieldt's description something they clearly voiced ?21:49
*** hashar has quit IRC21:49
dhellmannfifieldt: why do they want these things in git?21:49
morganfainbergttx, i think i see that is the general view.21:49
morganfainbergttx, i'm skimming the thread archive now21:49
fungittx: the git repository idea wasn't really championed in that thread, but i get the impression that not all operators who have a vested interest are on that ml21:49
ttxfungi: is that a description of needs we can act on and propose a strawman solution for ?21:49
fifieldtdhellmann, its raw, easy to use from the filesystem, diffable, changes can be tracked21:50
bknudsonI use the sample config file in git every few days.21:50
fifieldtso this is just my interpretation from talking with a ton of ops21:50
*** akuznetsov has quit IRC21:50
dhellmannfifieldt: ok, tracking changes at least makes sense21:50
fungittx: i pointed out on the ml that the git repo solution is one that anyone could provide without necessarily needing us to solve that, and it seems that's happened already21:50
fifieldtindeed, and it seems to indicate that that method is an acceptable solution21:51
fifieldtso p[ulling that up so its visible could be a next step21:51
ttxfifieldt: would you mind reheating the thread by summarizing the needs like you just did ?21:51
*** _nadya_ has joined #openstack-meeting21:51
ttxThen we can discuss implementation on the other side21:51
fifieldtit's been on my todo list, ttx :)21:51
ttxok, potential progress again!21:51
fungiso straw man proposal would be to let the operator community continue to scratch its itch with the git repo, and possibly still include sample configs in tarballs (though as jeblair pointed out that does complicate sdist creation)21:52
ttxfungi: we can discuss the feasibility of that part if we know that's what they want21:52
fungiagreed21:52
fifieldtI think there'd be a preference for the git repo thing to be produced by upstream21:52
fifieldtrather than in some random personal repo21:52
fungiit's a solution they can contribute though21:53
ttxso let's wait for fifieldt to come back to us with a clear need like he just outlined21:53
fungisince they've worked out the specifics21:53
fifieldtwhat do you need, ttx ?21:53
fifieldtjust post those two bullet points to the list?21:53
fungiand we can just run it21:53
*** Mandell has joined #openstack-meeting21:53
dhellmannfungi: ++21:53
ttxfifieldt: and ask if that would be a consensual solution21:53
ttxif we could provide a technical solution for that21:53
*** dprince has quit IRC21:53
*** moha_hunt has quit IRC21:53
* fifieldt isn;'t sure why it has to be me writing this email, but ok :)21:53
ttxfifieldt: well, you authored this brilliant summary21:54
*** esheffield has joined #openstack-meeting21:54
ttxso we blame you now21:54
*** zehicle_ has joined #openstack-meeting21:55
ttxtime for one more quick thing21:55
fifieldtthe things I get up to at 5am :)21:55
ttx#topic openstack-specs discussion21:55
fungiwe've been trying to get some leadership from the operator community to push this to a conclusion so it doesn't fester21:55
*** openstack changes topic to "openstack-specs discussion (Meeting topic: crossproject)"21:55
*** padkrish has joined #openstack-meeting21:55
ttx* CLI Sorting Argument Guidelines (https://review.openstack.org/#/c/145544/)21:55
ttxThis one has no clear opposition so far21:55
ttxAffected projects are Glance, Cinder, Ironic and Neutron. We have Cinder PTL +1 so far21:55
ttxMissing mestery approval, (nikhil_k and devananda +1ed an earlier version)21:55
ttxOnce we have that (hopefully this week) I think we'll move to TC rubberstamping, unless there is a new objection raised21:55
mesteryttx: I'll re-examine that right now.21:56
ttxSo if you care and haven't expressed your opinion yet, now is the time to do so21:56
ttxWe'll discuss TRACE next meeting21:56
ttx#topic Open discussion & announcements21:56
*** openstack changes topic to "Open discussion & announcements (Meeting topic: crossproject)"21:56
ttxWe had 1:1 syncs today, one week before kilo-2 deadline21:56
*** neelashah has joined #openstack-meeting21:56
ttxLogs at:21:56
ttx#link http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-01-27-07.58.html21:56
ttxWe also expect a Swift release (2.2.2) next week21:57
ttxLast meeting in the middle of the netspit I asked if anyone would be interested in chairing a future cross-project meeting. I'm fine rotating on that job :)21:57
*** tellesnobrega_ has joined #openstack-meeting21:57
ttxPing me if interested21:57
fungii'll be pushing this week to switch projects which are successfully gating on python 3.3 to switch en-masse to 3.4 where possible, so keep an eye out for that (i'll announce on the dev ml too)21:57
ttxAnything else, anyone ?21:57
adam_gJust a friendly reminder, the stable/juno branches will freeze this thursday jan 29th in preparation for the 2014.2.2 next week.  Please get any new backports up for review soon and ping zul if you have any post-freeze exceptions.21:57
bknudsonnaming suggestion: Lougheed21:57
ttxbknudson: a bit late, come back for M :)21:58
*** baoli has quit IRC21:58
bknudsonwhat's the name?21:58
ttxpoll to open next week21:58
ttxbut trademark checks were run21:59
ttxstill hoping we can add Lilwat to the mix (first nation name)21:59
ttxbut probably won't get the approval we need from the tribe22:00
*** baoli has joined #openstack-meeting22:00
ttxin time for the poll22:00
ttxand that closes this meeting22:00
mesterythanks ttx!22:00
ttx#endmeeting22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
openstackMeeting ended Tue Jan 27 22:00:21 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-01-27-21.03.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-01-27-21.03.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-01-27-21.03.log.html22:00
ttxThanks everyone!22:00
*** unicell1 has joined #openstack-meeting22:00
*** Mandell has quit IRC22:00
*** sparkycollier has quit IRC22:01
*** neelashah has quit IRC22:01
*** padkrish_ has joined #openstack-meeting22:01
*** unicell has quit IRC22:02
*** stevelle has left #openstack-meeting22:02
*** brnelson has quit IRC22:02
*** sparkycollier has joined #openstack-meeting22:02
*** jtomasek has joined #openstack-meeting22:03
*** unicell has joined #openstack-meeting22:03
*** spzala has quit IRC22:03
*** padkrish has quit IRC22:03
*** Mandell has joined #openstack-meeting22:03
*** baoli has quit IRC22:04
*** unicell1 has quit IRC22:05
*** aranjan_ has quit IRC22:06
*** aranjan has joined #openstack-meeting22:07
*** rushil has left #openstack-meeting22:08
*** ChuckC_ has joined #openstack-meeting22:09
*** banix has quit IRC22:10
*** kurtmartin has quit IRC22:11
*** cference has quit IRC22:12
*** kurtmartin has joined #openstack-meeting22:12
*** ChuckC has quit IRC22:13
*** neelashah has joined #openstack-meeting22:14
*** liusheng has quit IRC22:14
*** radez is now known as radez_g0n322:17
*** kurtmartin has quit IRC22:17
*** joesavak has joined #openstack-meeting22:17
*** liusheng has joined #openstack-meeting22:17
*** kurtmartin has joined #openstack-meeting22:18
*** darrenc is now known as darrenc_afk22:19
*** dboik has joined #openstack-meeting22:20
*** salv-orlando has joined #openstack-meeting22:22
*** shwetaap has joined #openstack-meeting22:23
*** ChuckC has joined #openstack-meeting22:24
*** Mandell has quit IRC22:25
*** jckasper_ has quit IRC22:25
*** _nadya_ has quit IRC22:26
*** JRobinson__ has joined #openstack-meeting22:26
*** ChuckC_ has quit IRC22:27
*** ChuckC__ has joined #openstack-meeting22:28
*** bill_az has quit IRC22:28
*** ChuckC has quit IRC22:29
*** irenab has joined #openstack-meeting22:29
*** jtomasek has quit IRC22:30
*** Mandell has joined #openstack-meeting22:31
*** kurtmartin has quit IRC22:31
*** kurtmartin has joined #openstack-meeting22:33
*** Mandell has quit IRC22:35
*** ddieterly has quit IRC22:37
*** ddieterl_ has joined #openstack-meeting22:37
*** adahms has joined #openstack-meeting22:38
*** _d34dh0r53_ is now known as d34dh0r5322:38
*** ddieterl_ has quit IRC22:39
*** ddieterly has joined #openstack-meeting22:39
*** jehb has quit IRC22:39
*** ddieterly has quit IRC22:39
*** atiwari2 has joined #openstack-meeting22:39
*** ddieterly has joined #openstack-meeting22:40
*** ddieterly has quit IRC22:41
*** topol has quit IRC22:41
*** ddieterly has joined #openstack-meeting22:41
*** kurtmartin has quit IRC22:41
*** sparkycollier has quit IRC22:41
*** kurtmartin has joined #openstack-meeting22:42
*** atiwari1 has quit IRC22:42
*** angelamolock has joined #openstack-meeting22:44
*** unicell1 has joined #openstack-meeting22:44
*** andreykurilin_ has joined #openstack-meeting22:44
*** harlowja has joined #openstack-meeting22:44
*** unicell has quit IRC22:45
*** BrianB_ has quit IRC22:45
*** pnavarro has quit IRC22:47
*** andreaf_ has quit IRC22:49
*** daneyon_ has quit IRC22:49
*** harlowja_ has joined #openstack-meeting22:49
*** daneyon has joined #openstack-meeting22:49
*** unicell has joined #openstack-meeting22:50
*** harlowja has quit IRC22:50
*** unicell1 has quit IRC22:51
*** unicell has quit IRC22:53
*** dhellmann has quit IRC22:54
*** angelamolock has quit IRC22:55
*** kurtmartin has quit IRC22:55
*** dhellmann has joined #openstack-meeting22:55
*** kurtmartin has joined #openstack-meeting22:56
*** angelamolock has joined #openstack-meeting22:56
*** Mandell has joined #openstack-meeting22:56
*** salv-orlando has quit IRC22:57
*** unicell has joined #openstack-meeting22:57
*** yapeng has joined #openstack-meeting22:57
*** igordcard has joined #openstack-meeting22:58
*** ignacio-scopetta has joined #openstack-meeting22:59
*** tellesnobrega_ has quit IRC22:59
*** jgrimm is now known as zz_jgrimm22:59
*** timcline has quit IRC22:59
*** darrenc_afk is now known as darrenc22:59
*** ignacio-scopett1 has quit IRC23:00
*** IanGovett has quit IRC23:00
*** joesavak has quit IRC23:01
*** liusheng has quit IRC23:01
*** liusheng has joined #openstack-meeting23:01
*** VW_ has quit IRC23:01
*** harlowja_ has quit IRC23:03
*** yapeng has quit IRC23:03
*** sigmavirus24 is now known as sigmavirus24_awa23:03
*** aranjan has quit IRC23:04
*** kurtmartin has quit IRC23:04
*** e0ne has quit IRC23:05
*** unicell has quit IRC23:05
*** aranjan has joined #openstack-meeting23:05
*** kurtmartin has joined #openstack-meeting23:05
*** VW_ has joined #openstack-meeting23:06
*** salv-orlando has joined #openstack-meeting23:06
*** unicell has joined #openstack-meeting23:06
*** otter768 has joined #openstack-meeting23:07
*** stannie has quit IRC23:07
*** hichihara has joined #openstack-meeting23:07
*** VW_ has quit IRC23:08
*** VW_ has joined #openstack-meeting23:08
*** aranjan has quit IRC23:09
*** dulek has joined #openstack-meeting23:10
*** neelashah has quit IRC23:11
*** liusheng has quit IRC23:11
*** andreykurilin_ has quit IRC23:12
*** achanda has quit IRC23:12
*** liusheng has joined #openstack-meeting23:12
*** otter768 has quit IRC23:12
*** bknudson has quit IRC23:12
*** Mandell has quit IRC23:13
*** Riddhi has quit IRC23:14
*** ajo has quit IRC23:14
*** krtaylor has quit IRC23:15
*** angelamolock has quit IRC23:15
*** kurtmartin has quit IRC23:17
*** kurtmartin has joined #openstack-meeting23:18
*** irenab has quit IRC23:18
*** andreykurilin_ has joined #openstack-meeting23:18
*** liusheng has quit IRC23:19
*** liusheng has joined #openstack-meeting23:19
*** vijendar has quit IRC23:23
*** weshay has quit IRC23:24
*** watanabe_isao has joined #openstack-meeting23:24
*** eglynn has quit IRC23:25
*** igordcard has quit IRC23:26
*** liusheng has quit IRC23:26
*** liusheng has joined #openstack-meeting23:27
*** zehicle_ has quit IRC23:27
*** kurtmartin has quit IRC23:27
*** kurtmartin has joined #openstack-meeting23:28
*** ddieterly has quit IRC23:29
*** mgagne_ is now known as mgagne23:29
*** nellysmitt has joined #openstack-meeting23:29
*** aranjan has joined #openstack-meeting23:30
*** amitgandhinz has quit IRC23:30
*** annegent_ has quit IRC23:32
*** kurtmartin has quit IRC23:33
*** nellysmitt has quit IRC23:34
*** jecarey_ has quit IRC23:34
*** markvoelker has quit IRC23:35
*** banix has joined #openstack-meeting23:35
*** jungleboyj has quit IRC23:35
*** jhenner has quit IRC23:35
*** liusheng has quit IRC23:36
*** harlowja has joined #openstack-meeting23:36
*** hemna has quit IRC23:36
*** liusheng has joined #openstack-meeting23:36
*** tochi_ has joined #openstack-meeting23:37
*** baoli has joined #openstack-meeting23:37
*** eglynn has joined #openstack-meeting23:38
*** padkrish_ has quit IRC23:39
*** padkrish has joined #openstack-meeting23:40
*** liusheng has quit IRC23:41
*** liusheng has joined #openstack-meeting23:41
*** etoews_ has joined #openstack-meeting23:44
*** padkrish has quit IRC23:45
*** etoews has quit IRC23:46
*** liusheng has quit IRC23:46
*** liusheng has joined #openstack-meeting23:47
*** saurabhs has left #openstack-meeting23:47
*** ijw has quit IRC23:48
*** banix has quit IRC23:49
*** padkrish has joined #openstack-meeting23:51
*** achanda has joined #openstack-meeting23:52
*** VW_ has quit IRC23:53
*** yamahata has joined #openstack-meeting23:54
*** eglynn has quit IRC23:55
*** markvoelker has joined #openstack-meeting23:55
*** mattgriffin has quit IRC23:55
*** Leon has joined #openstack-meeting23:55
*** andreykurilin_ has quit IRC23:55
*** Leon is now known as Guest1451223:55
*** berendt has quit IRC23:58
*** VW_ has joined #openstack-meeting23:58
*** Leonr has quit IRC23:58
*** VW__ has joined #openstack-meeting23:58
*** salv-orlando has quit IRC23:59

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