Thursday, 2014-02-13

*** dkehn__ is now known as dkehn_00:00
*** banix has joined #openstack-meeting-alt00:03
*** chadlung has quit IRC00:06
*** tanisdl_ has joined #openstack-meeting-alt00:06
*** dkehn has quit IRC00:06
*** dkehn has joined #openstack-meeting-alt00:07
*** colinmcnamara has quit IRC00:08
*** dkehn_ has quit IRC00:09
*** dkehn is now known as dkehn_00:09
*** harlowja is now known as harlowja_away00:09
*** dkehn_ has quit IRC00:09
*** lyle has quit IRC00:10
*** tanisdl has quit IRC00:10
*** tanisdl_ is now known as tanisdl00:10
*** dkehn has joined #openstack-meeting-alt00:10
*** dkehn_ has joined #openstack-meeting-alt00:10
*** lyle has joined #openstack-meeting-alt00:12
*** pballand has quit IRC00:16
*** svetlanad has quit IRC00:20
*** ijw has quit IRC00:21
*** banix has quit IRC00:22
*** dkehn__ has joined #openstack-meeting-alt00:23
*** ijw_ has joined #openstack-meeting-alt00:25
*** krtaylor has joined #openstack-meeting-alt00:25
*** dkehn__ has quit IRC00:26
*** dkehn_ has quit IRC00:26
*** dkehn has quit IRC00:26
*** dkehn__ has joined #openstack-meeting-alt00:27
*** dkehn has joined #openstack-meeting-alt00:28
*** amrith has joined #openstack-meeting-alt00:35
*** Ranjitha has quit IRC00:38
*** banix has joined #openstack-meeting-alt00:39
*** colinmcnamara has joined #openstack-meeting-alt00:39
*** gokrokve_ has quit IRC00:41
*** gokrokve has joined #openstack-meeting-alt00:41
*** SushilKM has quit IRC00:44
*** SushilKM has joined #openstack-meeting-alt00:45
*** gokrokve has quit IRC00:45
*** yamahata has joined #openstack-meeting-alt00:49
*** ijw_ has quit IRC00:55
*** ijw has joined #openstack-meeting-alt00:56
*** david-lyle has joined #openstack-meeting-alt00:58
*** ijw has quit IRC01:00
*** pballand has joined #openstack-meeting-alt01:03
*** SushilKM has quit IRC01:05
*** cody-somerville has quit IRC01:06
*** tanisdl has quit IRC01:06
*** jjmb has joined #openstack-meeting-alt01:08
*** igormarnat_ has joined #openstack-meeting-alt01:08
*** david-lyle has quit IRC01:11
*** ijw has joined #openstack-meeting-alt01:16
*** dkehn_ has joined #openstack-meeting-alt01:17
*** IlyaE has quit IRC01:17
*** cody-somerville has joined #openstack-meeting-alt01:18
*** dkehn_ has quit IRC01:19
*** dkehn has quit IRC01:19
*** dkehn_ has joined #openstack-meeting-alt01:20
*** dkehn__ has quit IRC01:20
*** ijw has quit IRC01:20
*** ijw has joined #openstack-meeting-alt01:21
*** dkehn has joined #openstack-meeting-alt01:21
*** ijw has quit IRC01:25
*** michael-yu has joined #openstack-meeting-alt01:26
*** atiwari has quit IRC01:34
*** michael-yu has quit IRC01:35
*** vkmc has quit IRC01:37
*** xuhanp has joined #openstack-meeting-alt01:39
*** david-lyle has joined #openstack-meeting-alt01:40
*** colinmcnamara has quit IRC01:41
*** harlowja_away is now known as harlowja01:43
*** bdpayne has quit IRC01:45
*** saurabhs has left #openstack-meeting-alt01:48
*** richm has quit IRC01:51
*** ijw has joined #openstack-meeting-alt01:53
*** igormarnat_ has quit IRC01:55
*** nosnos has joined #openstack-meeting-alt02:00
*** Barker has joined #openstack-meeting-alt02:01
*** sarob has quit IRC02:08
*** irenab_ has joined #openstack-meeting-alt02:09
*** sarob has joined #openstack-meeting-alt02:09
*** sballe_ has joined #openstack-meeting-alt02:09
*** dukhlov__ has joined #openstack-meeting-alt02:10
*** amotoki__ has joined #openstack-meeting-alt02:10
*** jecarey_ has joined #openstack-meeting-alt02:11
*** harlowja_ has joined #openstack-meeting-alt02:13
*** SergeyLukjanov has quit IRC02:13
*** aignatov_ has quit IRC02:13
*** sc68cal has quit IRC02:13
*** mtaylor has joined #openstack-meeting-alt02:13
*** dteselkin_ has joined #openstack-meeting-alt02:13
*** sarob has quit IRC02:14
*** mikal_ has joined #openstack-meeting-alt02:14
*** dteselkin has quit IRC02:14
*** DinaBelova_ has quit IRC02:14
*** mikal has quit IRC02:14
*** ogelbukh1 has joined #openstack-meeting-alt02:14
*** bnemec_ has joined #openstack-meeting-alt02:15
*** SergeyLukjanov has joined #openstack-meeting-alt02:15
*** amrith has quit IRC02:15
*** irenab has quit IRC02:15
*** amotoki_ has quit IRC02:15
*** NikitaKonovalov has quit IRC02:15
*** cgoncalves has quit IRC02:15
*** Guest5331 has quit IRC02:15
*** arnaud has quit IRC02:15
*** mordred has quit IRC02:15
*** SpamapS has quit IRC02:15
*** dukhlov_ has quit IRC02:15
*** bnemec has quit IRC02:15
*** csaba|afk has quit IRC02:15
*** megan_w has quit IRC02:15
*** ruhe has quit IRC02:15
*** kevinbenton has quit IRC02:15
*** kin_ has quit IRC02:15
*** haleyb has quit IRC02:15
*** gpocente1 has joined #openstack-meeting-alt02:15
*** nosnos_ has joined #openstack-meeting-alt02:15
*** arnaud has joined #openstack-meeting-alt02:15
*** plomakin_ has joined #openstack-meeting-alt02:15
*** Barker_ has joined #openstack-meeting-alt02:15
*** davidlenwell_ has joined #openstack-meeting-alt02:15
*** dkehn__ has joined #openstack-meeting-alt02:16
*** sc68cal has joined #openstack-meeting-alt02:16
*** jecarey__ has joined #openstack-meeting-alt02:16
*** megan_w has joined #openstack-meeting-alt02:17
*** kevinbenton has joined #openstack-meeting-alt02:17
*** haleyb has joined #openstack-meeting-alt02:17
*** csaba|afk has joined #openstack-meeting-alt02:18
*** b3nt_pin has joined #openstack-meeting-alt02:18
*** baoli has joined #openstack-meeting-alt02:18
*** amrith has joined #openstack-meeting-alt02:18
*** dmakogon_ has quit IRC02:18
*** plomakin has quit IRC02:18
*** dmakogon_ has joined #openstack-meeting-alt02:18
*** ZangMingJie has joined #openstack-meeting-alt02:18
*** david-lyle has quit IRC02:18
*** dkehn_ has quit IRC02:18
*** esheffield has quit IRC02:18
*** cgoncalv1s has joined #openstack-meeting-alt02:19
*** mtreinish has quit IRC02:19
*** esmute has quit IRC02:19
*** Barker has quit IRC02:19
*** pballand has quit IRC02:19
*** yamahata has quit IRC02:19
*** lyle has quit IRC02:19
*** doug_shelley66 has quit IRC02:19
*** jecarey has quit IRC02:19
*** beagles has quit IRC02:19
*** gyee has quit IRC02:19
*** ogelbukh has quit IRC02:19
*** ZangMing1ie has quit IRC02:19
*** sballe has quit IRC02:19
*** questionmask_ has quit IRC02:19
*** harlowja has quit IRC02:19
*** yamahata_ has quit IRC02:19
*** gpocentek has quit IRC02:19
*** RajeshMohan has quit IRC02:19
*** ZangMingJie has quit IRC02:20
*** ogelbukh1 has quit IRC02:20
*** ZangMingJie has joined #openstack-meeting-alt02:20
*** esmute has joined #openstack-meeting-alt02:22
*** jecarey_ has quit IRC02:22
*** nosnos has quit IRC02:22
*** banix has quit IRC02:22
*** davidlenwell has quit IRC02:22
*** cody-somerville has quit IRC02:23
*** aignatov_ has joined #openstack-meeting-alt02:23
*** jecarey_ has joined #openstack-meeting-alt02:23
*** aignatov_ is now known as aignatov02:23
*** abramley has quit IRC02:24
*** NikitaKonovalov_ has joined #openstack-meeting-alt02:24
*** kevinbenton_ has joined #openstack-meeting-alt02:24
*** SpamapS has joined #openstack-meeting-alt02:24
*** esmute has quit IRC02:25
*** jocker__ has joined #openstack-meeting-alt02:25
*** NikitaKonovalov_ is now known as NikitaKonovalov02:26
*** yamahata__ has joined #openstack-meeting-alt02:26
*** DinaBelova_ has joined #openstack-meeting-alt02:26
*** DinaBelova_ is now known as DinaBelova02:27
*** abramley has joined #openstack-meeting-alt02:27
*** ZangMing1ie has joined #openstack-meeting-alt02:27
*** ruhe has joined #openstack-meeting-alt02:27
*** cody-somerville has joined #openstack-meeting-alt02:27
*** davidlenwell has joined #openstack-meeting-alt02:28
*** esmute has joined #openstack-meeting-alt02:28
*** david-lyle has joined #openstack-meeting-alt02:28
*** yamahata has joined #openstack-meeting-alt02:28
*** SpamapS has quit IRC02:29
*** kin_ has joined #openstack-meeting-alt02:29
*** julim has quit IRC02:30
*** SpamapS has joined #openstack-meeting-alt02:30
*** coolsvap has quit IRC02:30
*** dripton_ has joined #openstack-meeting-alt02:30
*** dripton has quit IRC02:30
*** sballe_ has quit IRC02:32
*** ruhe has quit IRC02:32
*** julim_ has joined #openstack-meeting-alt02:32
*** julim_ has quit IRC02:32
*** NikitaKonovalov has quit IRC02:32
*** nosnos has joined #openstack-meeting-alt02:32
*** ZangMingJie has quit IRC02:33
*** amrith has quit IRC02:33
*** baoli has quit IRC02:33
*** b3nt_pin has quit IRC02:33
*** csaba|afk has quit IRC02:33
*** kevinbenton has quit IRC02:33
*** megan_w has quit IRC02:33
*** jecarey__ has quit IRC02:33
*** dkehn__ has quit IRC02:33
*** Barker_ has quit IRC02:33
*** davidlenwell_ has quit IRC02:33
*** nosnos_ has quit IRC02:33
*** gpocente1 has quit IRC02:33
*** arnaud has quit IRC02:33
*** RaymondWong has quit IRC02:33
*** kevinbenton_ is now known as kevinbenton02:33
*** amrith has joined #openstack-meeting-alt02:34
*** flwang has quit IRC02:34
*** aignatov has quit IRC02:34
*** hemanth has joined #openstack-meeting-alt02:34
*** irenab has joined #openstack-meeting-alt02:34
*** dkehn has quit IRC02:35
*** DinaBelova has quit IRC02:35
*** dmakogon_ has quit IRC02:35
*** dmakogon_ has joined #openstack-meeting-alt02:36
*** SpamapS has quit IRC02:36
*** SpamapS has joined #openstack-meeting-alt02:36
*** SpamapS has quit IRC02:36
*** SpamapS has joined #openstack-meeting-alt02:36
*** gpocentek has joined #openstack-meeting-alt02:37
*** dripton__ has joined #openstack-meeting-alt02:37
*** megan_w has joined #openstack-meeting-alt02:38
*** NikitaKonovalov has joined #openstack-meeting-alt02:38
*** csaba|afk has joined #openstack-meeting-alt02:38
*** dripton_ has quit IRC02:38
*** ruhe has joined #openstack-meeting-alt02:38
*** irenab_ has quit IRC02:38
*** mtreinish has joined #openstack-meeting-alt02:38
*** sballe has joined #openstack-meeting-alt02:38
*** julim has joined #openstack-meeting-alt02:38
*** Barker has joined #openstack-meeting-alt02:39
*** Barker has quit IRC02:39
*** aignatov_ has joined #openstack-meeting-alt02:39
*** cgoncalv1s has quit IRC02:40
*** aignatov_ is now known as aignatov02:40
*** DinaBelova_ has joined #openstack-meeting-alt02:40
*** esheffield has joined #openstack-meeting-alt02:40
*** cgoncalves has joined #openstack-meeting-alt02:40
*** cgoncalves has quit IRC02:40
*** cgoncalves has joined #openstack-meeting-alt02:40
*** DinaBelova_ is now known as DinaBelova02:41
*** amotoki_ has joined #openstack-meeting-alt02:41
*** dkehn_ has joined #openstack-meeting-alt02:42
*** esker has joined #openstack-meeting-alt02:42
*** megan_w has quit IRC02:42
*** bnemec has joined #openstack-meeting-alt02:43
*** arnaud has joined #openstack-meeting-alt02:44
*** hemanth has quit IRC02:45
*** mattgriffin1 has quit IRC02:45
*** mattgriffin has joined #openstack-meeting-alt02:45
*** gduan has joined #openstack-meeting-alt02:45
*** esheffield has quit IRC02:45
*** SergeyLukjanov2 has joined #openstack-meeting-alt02:45
*** esheffie1d has joined #openstack-meeting-alt02:45
*** DinaBelova has quit IRC02:45
*** plomakin has joined #openstack-meeting-alt02:45
*** russellb_ has joined #openstack-meeting-alt02:45
*** hemanth has joined #openstack-meeting-alt02:46
*** slagle_ has joined #openstack-meeting-alt02:46
*** iccha_ has joined #openstack-meeting-alt02:46
*** ameade_ has joined #openstack-meeting-alt02:47
*** b3nt_pin has joined #openstack-meeting-alt02:47
*** DinaBelova_ has joined #openstack-meeting-alt02:47
*** csaba|afk has quit IRC02:47
*** DinaBelova_ is now known as DinaBelova02:47
*** hgedikli1 has joined #openstack-meeting-alt02:48
*** dhellmann_ has joined #openstack-meeting-alt02:48
*** motoki has joined #openstack-meeting-alt02:48
*** mikal has joined #openstack-meeting-alt02:49
*** lyle has joined #openstack-meeting-alt02:49
*** arnaud has quit IRC02:49
*** dteselkin has joined #openstack-meeting-alt02:49
*** nosnos has quit IRC02:49
*** david-lyle has quit IRC02:49
*** kevinbenton has quit IRC02:49
*** sc68cal has quit IRC02:49
*** plomakin_ has quit IRC02:49
*** SergeyLukjanov has quit IRC02:49
*** bnemec_ has quit IRC02:49
*** mikal_ has quit IRC02:49
*** dteselkin_ has quit IRC02:49
*** amotoki__ has quit IRC02:50
*** xuhanp has quit IRC02:50
*** krtaylor has quit IRC02:50
*** rwsu has quit IRC02:50
*** arnaud__ has quit IRC02:50
*** lifeless has quit IRC02:50
*** amotoki has quit IRC02:50
*** NearlyFunctional has quit IRC02:50
*** jrist has quit IRC02:50
*** slagle has quit IRC02:50
*** dhellmann has quit IRC02:50
*** hgedikli has quit IRC02:50
*** anteaya has quit IRC02:50
*** shanks has quit IRC02:50
*** garyduan has quit IRC02:50
*** iccha has quit IRC02:50
*** ameade has quit IRC02:50
*** russellb has quit IRC02:50
*** SergeyLukjanov2 is now known as SergeyLukjanov02:50
*** dhellmann_ is now known as dhellmann02:50
*** russellb_ is now known as russellb02:50
*** sc68cal has joined #openstack-meeting-alt02:51
*** kevinbenton has joined #openstack-meeting-alt02:51
*** arnaud has joined #openstack-meeting-alt02:51
*** NikitaKonovalov_ has joined #openstack-meeting-alt02:52
*** SumitNaiksatam has joined #openstack-meeting-alt02:52
*** shanks has joined #openstack-meeting-alt02:53
*** mtreinish_ has joined #openstack-meeting-alt02:54
*** Leonr has joined #openstack-meeting-alt02:55
*** nosnos has joined #openstack-meeting-alt02:56
*** anteaya has joined #openstack-meeting-alt02:56
*** NikitaKonovalov has quit IRC02:57
*** mtreinish has quit IRC02:57
*** NikitaKonovalov_ is now known as NikitaKonovalov02:57
*** mtreinish_ is now known as mtreinish02:57
*** megan_w has joined #openstack-meeting-alt02:57
*** jrist has joined #openstack-meeting-alt02:57
*** NearlyFunctiona1 has joined #openstack-meeting-alt02:57
*** SushilKM has joined #openstack-meeting-alt02:57
*** ijw has quit IRC02:58
*** lifeless has joined #openstack-meeting-alt02:58
*** krtaylor has joined #openstack-meeting-alt03:00
*** sarob has joined #openstack-meeting-alt03:01
*** rwsu has joined #openstack-meeting-alt03:01
*** csaba|afk has joined #openstack-meeting-alt03:02
*** dklyle has joined #openstack-meeting-alt03:03
*** pleia2 has quit IRC03:03
*** sarob has quit IRC03:03
*** pleia2 has joined #openstack-meeting-alt03:04
*** HenryG has quit IRC03:04
*** sarob has joined #openstack-meeting-alt03:04
*** sc68cal has quit IRC03:04
*** lyle has quit IRC03:04
*** jocker__ has quit IRC03:04
*** hemanth has quit IRC03:05
*** hemanth_ has joined #openstack-meeting-alt03:05
*** sarob has quit IRC03:08
*** bdpayne has joined #openstack-meeting-alt03:08
*** yamahata__ has quit IRC03:09
*** sc68cal has joined #openstack-meeting-alt03:10
*** yamahata__ has joined #openstack-meeting-alt03:10
*** jocker__ has joined #openstack-meeting-alt03:11
*** flwang has joined #openstack-meeting-alt03:13
*** ijw has joined #openstack-meeting-alt03:15
*** eankutse has joined #openstack-meeting-alt03:17
*** esker has quit IRC03:17
*** bdpayne has quit IRC03:18
*** Haiying has joined #openstack-meeting-alt03:19
*** dkehn_ has quit IRC03:21
*** balajiiyer has joined #openstack-meeting-alt03:21
*** balajiiyer has left #openstack-meeting-alt03:22
*** dkehn has joined #openstack-meeting-alt03:22
*** esker has joined #openstack-meeting-alt03:24
*** 20WAA7JFX has joined #openstack-meeting-alt03:29
*** gyee has joined #openstack-meeting-alt03:29
*** baoli has joined #openstack-meeting-alt03:29
*** RajeshMohan has joined #openstack-meeting-alt03:29
*** flaper87|afk has quit IRC03:29
*** flaper87|afk has joined #openstack-meeting-alt03:29
*** harlowja_ has quit IRC03:30
*** harlowja_ has joined #openstack-meeting-alt03:30
*** shanks has quit IRC03:30
*** shanks has joined #openstack-meeting-alt03:30
*** Leonr has quit IRC03:30
*** Leonr has joined #openstack-meeting-alt03:30
*** csaba|afk has quit IRC03:30
*** csaba|afk has joined #openstack-meeting-alt03:30
*** dklyle has quit IRC03:30
*** dklyle has joined #openstack-meeting-alt03:30
*** yamahata__ has quit IRC03:30
*** yamahata__ has joined #openstack-meeting-alt03:30
*** ijw has quit IRC03:30
*** ijw has joined #openstack-meeting-alt03:30
*** ijw has quit IRC03:49
*** ijw has joined #openstack-meeting-alt03:49
*** ijw has quit IRC03:54
*** gokrokve has joined #openstack-meeting-alt03:55
*** arnaud has quit IRC03:58
*** chandan_kumar has joined #openstack-meeting-alt03:58
*** 20WAA7JFX has quit IRC03:58
*** Leonr has quit IRC04:01
*** eankutse has quit IRC04:04
*** IlyaE has joined #openstack-meeting-alt04:05
*** gduan has quit IRC04:07
*** garyduan has joined #openstack-meeting-alt04:07
*** chandan_kumar has quit IRC04:09
*** chandan_kumar has joined #openstack-meeting-alt04:10
*** sarob has joined #openstack-meeting-alt04:14
*** garyduan has quit IRC04:17
*** garyduan has joined #openstack-meeting-alt04:17
*** sarob has quit IRC04:19
*** ogelbukh1 has joined #openstack-meeting-alt04:20
*** lazy has joined #openstack-meeting-alt04:20
*** lazy is now known as Guest4938304:21
*** mikal has quit IRC04:26
*** mikal has joined #openstack-meeting-alt04:27
*** SushilKM has quit IRC04:29
*** amrith has quit IRC04:32
*** SushilKM has joined #openstack-meeting-alt04:34
*** Haiying has quit IRC04:36
*** amrith has joined #openstack-meeting-alt04:36
*** irenab has quit IRC04:40
*** amcrn has quit IRC04:42
*** Haiying has joined #openstack-meeting-alt04:43
*** Guest49383 has quit IRC04:48
*** SushilKM has quit IRC04:52
*** SushilKM has joined #openstack-meeting-alt05:00
*** cadenzajon has quit IRC05:05
*** krtaylor has quit IRC05:06
*** SushilKM has quit IRC05:07
*** krtaylor has joined #openstack-meeting-alt05:11
*** Haiying has quit IRC05:14
*** DinaBelova is now known as DinaBelova_05:15
*** jecarey_ has quit IRC05:15
*** IlyaE has quit IRC05:15
*** krtaylor has joined #openstack-meeting-alt05:19
*** Guest49383 has joined #openstack-meeting-alt05:23
*** ijw has joined #openstack-meeting-alt05:37
*** ijw has joined #openstack-meeting-alt05:37
*** gyee has quit IRC05:40
*** bdpayne has joined #openstack-meeting-alt05:40
*** amcrn has joined #openstack-meeting-alt05:42
*** chandankumar_ has joined #openstack-meeting-alt05:49
*** chandankumar_ has quit IRC05:49
*** chandankumar_ has joined #openstack-meeting-alt05:50
*** chandankumar_ has quit IRC05:52
*** dkehn has quit IRC05:52
*** chandan_kumar has quit IRC05:53
*** chandan_kumar has joined #openstack-meeting-alt05:54
*** dkehn has joined #openstack-meeting-alt05:54
*** gokrokve has quit IRC05:54
*** gokrokve has joined #openstack-meeting-alt05:55
*** bdpayne has quit IRC05:55
*** rohit404 has joined #openstack-meeting-alt05:56
*** gokrokve has quit IRC05:58
*** ijw has quit IRC06:00
*** ijw has joined #openstack-meeting-alt06:00
*** SushilKM has joined #openstack-meeting-alt06:02
*** dkehn_ has joined #openstack-meeting-alt06:05
*** amotoki_ has quit IRC06:09
*** ijw_ has joined #openstack-meeting-alt06:12
*** ijw has quit IRC06:15
*** sarob has joined #openstack-meeting-alt06:31
*** marun has quit IRC06:40
*** _nadya_ has joined #openstack-meeting-alt06:41
*** harlowja_ is now known as harlowja_away06:44
*** ijw_ has quit IRC06:46
*** ijw has joined #openstack-meeting-alt06:46
*** ijw has quit IRC06:51
*** akuznetsov has quit IRC06:58
*** rohit404 has quit IRC06:58
*** akuznetsov has joined #openstack-meeting-alt06:59
*** motoki has quit IRC07:00
*** mattgriffin has quit IRC07:03
*** mahipal has joined #openstack-meeting-alt07:03
*** _nadya_ has quit IRC07:03
*** denis_makogon has joined #openstack-meeting-alt07:04
*** mattgriffin has joined #openstack-meeting-alt07:05
*** akuznetsov has quit IRC07:06
*** akuznetsov has joined #openstack-meeting-alt07:10
*** mattgriffin has quit IRC07:10
*** ijw has joined #openstack-meeting-alt07:14
*** madhami has joined #openstack-meeting-alt07:17
*** dkehn__ has joined #openstack-meeting-alt07:19
*** jtomasek has joined #openstack-meeting-alt07:19
*** sarob has quit IRC07:21
*** dkehn__ has quit IRC07:21
*** sarob has joined #openstack-meeting-alt07:21
*** dkehn__ has joined #openstack-meeting-alt07:21
*** madhami has quit IRC07:22
*** IlyaE has joined #openstack-meeting-alt07:22
*** dkehn_ has quit IRC07:22
*** madhami has joined #openstack-meeting-alt07:22
*** dkehn has quit IRC07:22
*** madhami has quit IRC07:22
*** IlyaE has quit IRC07:23
*** jtomasek has quit IRC07:23
*** dkehn has joined #openstack-meeting-alt07:24
*** amytron has joined #openstack-meeting-alt07:25
*** jtomasek has joined #openstack-meeting-alt07:25
*** sarob has quit IRC07:26
*** flaper87|afk is now known as flaper8707:33
*** amytron has quit IRC07:56
*** denis_makogon_ has joined #openstack-meeting-alt07:59
*** denis_makogon has quit IRC08:02
*** SushilKM has quit IRC08:08
*** akuznetsov has quit IRC08:12
*** SpamapS has quit IRC08:14
*** SpamapS has joined #openstack-meeting-alt08:15
*** SpamapS has quit IRC08:15
*** SpamapS has joined #openstack-meeting-alt08:15
*** aignatov has quit IRC08:15
*** persia has quit IRC08:16
*** aignatov_ has joined #openstack-meeting-alt08:17
*** aignatov_ is now known as aignatov08:17
*** lifeless has quit IRC08:17
*** persia has joined #openstack-meeting-alt08:18
*** persia is now known as Guest4378108:18
*** lifeless has joined #openstack-meeting-alt08:19
*** Guest43781 has quit IRC08:20
*** Guest43781 has joined #openstack-meeting-alt08:20
*** Guest43781 is now known as persia08:20
*** sarob has joined #openstack-meeting-alt08:22
*** sarob has quit IRC08:28
*** jcoufal has joined #openstack-meeting-alt08:35
*** mattgriffin has joined #openstack-meeting-alt08:36
*** mattgriffin has quit IRC08:42
*** d0ugal has joined #openstack-meeting-alt08:49
*** d0ugal has quit IRC08:49
*** d0ugal has joined #openstack-meeting-alt08:49
*** saju_m has joined #openstack-meeting-alt08:50
*** nacim has joined #openstack-meeting-alt09:00
*** derekh has joined #openstack-meeting-alt09:09
*** flwang has quit IRC09:20
*** sarob has joined #openstack-meeting-alt09:25
*** rsblendido has joined #openstack-meeting-alt09:25
*** rossella_s has joined #openstack-meeting-alt09:25
*** denis_makogon_ has quit IRC09:28
*** ijw has quit IRC09:30
*** DinaBelova_ is now known as DinaBelova09:32
*** julienvey has joined #openstack-meeting-alt09:46
*** balajiiyer has joined #openstack-meeting-alt09:49
*** balajiiyer has quit IRC09:50
*** sarob has quit IRC09:57
*** zhiyan has joined #openstack-meeting-alt09:58
*** akuznetsov has joined #openstack-meeting-alt10:14
*** dmakogon_ is now known as denis_makogon10:19
*** sarob has joined #openstack-meeting-alt10:22
*** sergmelikyan has joined #openstack-meeting-alt10:31
*** rwmjones is now known as rwmjones_biab10:34
*** jocker__ has quit IRC10:41
*** sarob has quit IRC10:55
*** sarob has joined #openstack-meeting-alt11:22
*** rwmjones_biab is now known as rwmjones11:24
*** notmyname has quit IRC11:29
*** pleia2 has quit IRC11:31
*** ijw has joined #openstack-meeting-alt11:31
*** dhellmann has quit IRC11:31
*** dhellmann has joined #openstack-meeting-alt11:32
*** pleia2 has joined #openstack-meeting-alt11:32
*** notmyname has joined #openstack-meeting-alt11:32
*** dkehn_ has joined #openstack-meeting-alt11:32
*** krtaylor has quit IRC11:33
*** sc68cal has quit IRC11:34
*** dkehn_ has quit IRC11:35
*** dkehn__ has quit IRC11:35
*** dkehn has quit IRC11:35
*** dkehn_ has joined #openstack-meeting-alt11:35
*** ijw has quit IRC11:36
*** sc68cal has joined #openstack-meeting-alt11:37
*** dkehn has joined #openstack-meeting-alt11:37
*** krtaylor has joined #openstack-meeting-alt11:38
*** zhiyan is now known as zhiyan_11:39
*** mattgriffin has joined #openstack-meeting-alt11:40
*** mattgriffin has quit IRC11:45
*** sankarshan_away is now known as sankarshan11:50
*** sarob has quit IRC11:55
*** vkmc has joined #openstack-meeting-alt12:09
*** vkmc has joined #openstack-meeting-alt12:09
*** jcooley has quit IRC12:17
*** mahipal has quit IRC12:18
*** jcooley has joined #openstack-meeting-alt12:20
*** yamahata has quit IRC12:22
*** d0ugal_ has joined #openstack-meeting-alt12:22
*** sarob has joined #openstack-meeting-alt12:22
*** d0ugal has quit IRC12:25
*** d0ugal_ is now known as d0ugal12:27
*** d0ugal has quit IRC12:27
*** d0ugal has joined #openstack-meeting-alt12:28
*** d0ugal has quit IRC12:28
*** d0ugal has joined #openstack-meeting-alt12:28
*** baoli has quit IRC12:39
*** baoli has joined #openstack-meeting-alt12:40
*** NikitaKonovalov is now known as NikitaKonovalov_12:43
*** xuhanp has joined #openstack-meeting-alt12:47
*** sballe has quit IRC12:50
*** sballe has joined #openstack-meeting-alt12:51
*** sarob has quit IRC12:55
*** irenab has joined #openstack-meeting-alt12:58
*** BrianB_ has joined #openstack-meeting-alt12:58
*** rkukura has joined #openstack-meeting-alt13:00
baoli#startmeeting PCI Passthrough13:00
openstackMeeting started Thu Feb 13 13:00:25 2014 UTC and is due to finish in 60 minutes.  The chair is baoli. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: PCI Passthrough)"13:00
openstackThe meeting name has been set to 'pci_passthrough'13:00
rkukurahi13:00
baoliHi13:00
BrianB_hi13:00
irenabhi13:01
*** stannie has quit IRC13:01
*** flwang has joined #openstack-meeting-alt13:01
baoliLet's wait a couple of minutes for Yongli13:02
b3nt_pinhi13:02
*** b3nt_pin is now known as beagles13:02
*** jprovazn has joined #openstack-meeting-alt13:02
beagles(sorry my nick was flipped)13:02
baoliHi beagles13:02
irenabhi13:02
irenabshort update on nova bug I raised before, Itzik pushed the fix  https://review.openstack.org/#/c/59093/13:03
irenabbaoli: there is a code that gets provider network physical_netowrk attributes, take a look13:04
baoliirenab, sure13:04
*** jcoufal has quit IRC13:04
*** pdmars has joined #openstack-meeting-alt13:05
*** jcoufal has joined #openstack-meeting-alt13:05
irenabrkukura: any objections on vnic_type patch?13:05
*** NikitaKonovalov_ is now known as NikitaKonovalov13:05
rkukurairenab: I never got back to my review of that yesterday, but I will today13:05
*** stannie has joined #openstack-meeting-alt13:06
irenabI'll probably push slight fixes to mainly fix alembic migration failure13:06
*** sadasu has joined #openstack-meeting-alt13:08
baoliI think that we should get started.13:09
baoliI guess that everyone has seen the emails on the Nova BPs pending for approval13:10
*** nosnos has quit IRC13:10
*** dprince has joined #openstack-meeting-alt13:10
sadasuyes13:11
baolirkukura, do you see any issues for the neutron sriov related BPs being approved?13:11
irenabbaoli: yes, John sent the email13:11
*** heyongli has joined #openstack-meeting-alt13:12
rkukuraWe are still waiting for markmclain to approve the vnic_type BP, right?13:12
heyonglibaoli, sorry my network can not reach this meeting for a while.13:12
baoliHi heyongli13:12
irenabrkukura: I think mestery approved and need salvatore to look at this too.13:13
*** jdob has joined #openstack-meeting-alt13:14
rkukurairenab: Its all set13:14
irenabrkukura: Cool, so just need you time for review :-)13:14
rkukuraAre there separate BPs for each SR-IOV MD?13:15
rkukuraI see https://blueprints.launchpad.net/neutron/+spec/ml2-sriov-nic-switch13:15
irenabrkukura: yes, I posted it13:16
*** Barker has joined #openstack-meeting-alt13:16
irenabrkukura: will start to bring it once vnic_type in good shape13:17
rkukuraIs there still work to do for https://blueprints.launchpad.net/neutron/+spec/pci-passthrough-sriov?13:17
baolirkukura, good question. I opened it for neutron related sriov works13:18
sadasuI think this work is covered in Irena's BP13:18
irenabrkukura: it comes to common parts for every SRIOV plugin13:19
sadasubut we might keep it around, to support Neutron changes when the full blown Nova changes come in13:19
irenabI think sadasu and I need to see if/how common parts can be extracted in order to eliminate code duplication13:19
sadasuirenab: agreed13:19
irenabstill need to see if there is SRIOVMDBase or some DBMixin13:20
baoliSo seems that we are in good shape from neutron side13:20
sadasuyeah, I looked at it a little bit13:20
baoliNow that yongli has joined, let's talk about nova side of things13:20
irenabsadsu: I think you are ahead of me here, so any inputs you have, please share13:21
rkukuraWe'll need to get at least the 1st of those BPs approved, and some code in review by Tuesday to make icehouse13:21
irenabrkukura: How we can do it without binding:profile?13:21
baolirkukura, which BP specifically?13:21
*** sarob has joined #openstack-meeting-alt13:22
rkukuraThe binding-profile BP is approved,and will be in review today I expect13:22
*** esker has quit IRC13:23
*** sankarshan is now known as sankarshan_away13:23
*** sankarshan_away is now known as sankarshan13:23
baolirkukura, that sounds great13:23
*** esker has joined #openstack-meeting-alt13:23
rkukuraWhichever BP(s) actually define the keys used in binding:vif_details and binding:profile, and implement the MD(s)13:23
baolisadasu, what about your BP? is it approved?13:24
sadasubaoli: yes, its approved ....putting up code shortly for review13:24
irenabrkukura: I'll update the above BP to mention the attributes baoli summarized on wiki13:25
rkukurasadasu: Link to your BP?13:25
baolisadasu, cool13:25
irenabbaoli: switch to nova?13:26
baoliirenab, is there a BP for your MD? You said that you are going to bring it up once the vnic bp is in good shape?13:26
sadasurkukura: https://blueprints.launchpad.net/neutron/+spec/ml2-ucs-manager-mechanism-driver13:27
irenabbaoli: yes, https://blueprints.launchpad.net/neutron/+spec/ml2-sriov-nic-switch is mine.13:27
rkukurasadasu:: found https://blueprints.launchpad.net/neutron/+spec/ml2-ucs-manager-mechanism-driver, and that it is approved13:27
baoliI'll put all of them in the meeting wiki13:27
baolicool. let's switch to nova13:27
irenabStill need the old Mellanox Plugin as MD due to InfiniBand support, so had to push it with no regards to surrent design13:27
*** esker has quit IRC13:28
irenabs/surrent/current13:28
*** lblanchard has joined #openstack-meeting-alt13:29
*** Guest60092 has joined #openstack-meeting-alt13:29
*** sballe has quit IRC13:29
*** sballe has joined #openstack-meeting-alt13:29
baoliWith regard to the nova BPs, we need to decide what to do if they won't be approved for icehouse. Any comments?13:29
*** Guest60092 has quit IRC13:30
irenabbaoli: not sure what we can do13:31
heyongliit's hard part13:31
sadasurkukura: how has this type of scenario worked in the past?13:31
*** ijw has joined #openstack-meeting-alt13:32
*** alex-hw has joined #openstack-meeting-alt13:32
heyonglii have no idea, yunhong talked with john in meetup, there still some concert should be resolved,13:32
rkukuraWe need to find supportive nova core reviewers, and deal with any legitimate objections/concerns13:33
*** mozawa has joined #openstack-meeting-alt13:34
irenabmaybe if we continue with the code and even its accepted in J-1, it can be backported13:34
*** agileclipse has joined #openstack-meeting-alt13:34
heyonglicode will continue, definitely13:35
rkukuraRight now, it seems that one nova core has not been supportive, but is he raising valid concerns other than just core reviewing workload?13:35
baoliI thought Russell would look at this. But his email seems to indicate that his hands are full13:35
heyongliaggregate is the one of problem13:35
*** ijw has quit IRC13:37
sadasuheyongli: are u planning to rework your design to include host-aggregates?13:37
heyongliat leas i should considerate it carefully13:37
heyongliand post some idea about it13:38
baoliI put together an agenda for today earlier: https://wiki.openstack.org/wiki/Meetings/Passthrough#Agenda_on_Feb._13th.2C_201413:38
sadasuI think you'll likely end up getting the same comment from other cores13:38
baoliIt talks about what we need from nova generic support13:38
heyongliyunhong also try to split the basic support to another bp, but can not make it13:40
baoliI think that we discussed host aggregates extensively, and thought in its current shape it won't support our requeirements13:41
heyonglibaoli, this the major gap13:41
heyongliAn API to retrieve a PCI device that is linked to the original PCI request.13:41
baoliheyongli, any comments on that?13:42
heyonglifor this, is it can be done by  pci_manager.get_instance_pci_devs and plus a function find the device by specs, what do you thinks about such approach?13:43
sadasubaoli: can we put a section in your wiki, just to capture that reasoning?13:44
baoliheyongli, what do you mean by specs?13:44
sadasuI think it is spread out in emails and IRCs13:44
heyongli{ key: v, ...}13:44
baolisadasu, about the aggregate?13:44
heyongliwhich wiki, did i miss it?13:44
sadasubaoli: yes13:45
heyongliour reason is not strong enough for john, i think13:45
sadasubaoli: don't want to add more to your plate...but trying to help13:45
baoliheyongli, it won't work in this case: if you have similar requests in both the nova flavor and the --nic request13:46
heyonglibaoli , can you make a example?13:47
baoliheyongli, I sent you an email about my proposal, you didn't get back to me13:47
heyonglibaoli, i might miss it?13:47
heyonglii will check it later. ooh, i take one day leave at  tomorrow13:47
*** kmak has joined #openstack-meeting-alt13:47
baoliheyongli, it was a few weeks back, and also other emails that talk about it.13:48
heyonglibaoli, even similer, but you can make the request's all spec to the function13:48
*** yamahata has joined #openstack-meeting-alt13:48
heyonglibaoli, sorry for this, i did take a long vacation.13:49
heyongliif we had get_pci_device_by_specs(pci_devs, specs)13:50
heyonglithe specs can translate from a request13:50
baoliheyongli, taking the existing pci alias for example, you can have the alias specified in the flavor, at the same time, the alias can be used in the --nic option.13:50
heyongliget_specs_from_request(request)13:50
heyonglionly if they are have any diffrent , this can work13:50
heyongliif same, no need to get recognized, i think.13:51
heyonglionly problem might be, if network and regular pci share same alias, we should find a 'free' one in libvirt config layer13:52
baoliheyongli, so get_pci_device_by_specs() would return a list of pci devices. Which one to pick?13:52
baoliheyongli, let me forward you my email again. It basically uses the cookie approach, and it's very simple13:53
*** bugsduggan has joined #openstack-meeting-alt13:53
heyonglibaoli, i try to make a cookie version ever, but seems more like hack one, i drop it. anyway, this is code detail, and we can discuss offline in mail.13:54
*** nwidell has joined #openstack-meeting-alt13:55
*** markwash has joined #openstack-meeting-alt13:55
*** sarob has quit IRC13:55
heyonglibaoli, forward that to yunhong also and to mail list, yunhong might quick response when i take my short vacation13:56
*** zhiyan_ is now known as zhiyan13:56
heyongliany way you list base support of nova is what i think, this cool13:57
baoliheyongli, he had it already. You were on the mailing list, I beleive13:57
irenabany change regarding daily meetings?13:57
*** colinmcnamara has joined #openstack-meeting-alt13:57
*** gokrokve has joined #openstack-meeting-alt13:57
*** Guest49383 has quit IRC13:57
heyonglibaoli, sorry again, once we find the way, code is very soon13:57
heyongliirenab, 2 meeting might enough?13:58
baoliheyongli, we need to agree on what is needed, and the way to do it,13:58
heyonglisure.13:59
irenabheyongli: I think we may try Mon and Wed + updates on mails if needed13:59
heyongliirenab, i'm ok with it14:00
*** arnaud__ has joined #openstack-meeting-alt14:00
sadasu2 times a week is good14:00
baoliOk, let's say the next meeting is Monday. And If needed, we can have one on Wednesday.14:00
irenabagree14:00
heyonglicool14:00
*** mattgriffin has joined #openstack-meeting-alt14:00
rkukura+114:01
*** koofoss has joined #openstack-meeting-alt14:01
rkukuraI'm likely to miss Monday's meeting, but not sure14:01
baoliThe channel is still open, can we go on for a little bit longer?14:01
rkukuraIf so, I'll read the logs.14:01
markwashis the pci-passthrough meeting over?14:02
baolimarkwash, you need the channel? Sorry, I'll end the meeting now14:02
baoli#endmeeting14:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:03
openstackMeeting ended Thu Feb 13 14:03:30 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-02-13-13.00.html14:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-02-13-13.00.txt14:03
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-02-13-13.00.log.html14:03
*** jokke_ has joined #openstack-meeting-alt14:03
markwashbaoli: thanks!14:03
*** heyongli has quit IRC14:03
markwash#startmeeting glance14:03
openstackMeeting started Thu Feb 13 14:03:48 2014 UTC and is due to finish in 60 minutes.  The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot.14:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
*** openstack changes topic to " (Meeting topic: glance)"14:03
openstackThe meeting name has been set to 'glance'14:03
flwang\o/14:03
*** rohit404 has joined #openstack-meeting-alt14:04
*** sadasu has quit IRC14:04
rosmaitao/14:04
arnaud__hi!!14:04
gokrokveHi!!14:04
jokke_Ehlo14:04
markwashHi folks!14:04
flwangrosmaita: morning14:05
hemanth_0/14:05
markwashI was busy at the nova meetup yesterday and have not prepared the agenda very much14:05
markwashhemanth_ has an item he woulld like to discuss14:05
markwashand some time after that I'd like to run through the icehouse-3 blueprints again to see what progress we've made or if there are other changes we should make14:05
*** miaykz has joined #openstack-meeting-alt14:06
*** alex-hw has quit IRC14:06
markwash#topic suspending and image (hemanth_)14:06
*** openstack changes topic to "suspending and image (hemanth_) (Meeting topic: glance)"14:06
markwashhemanth_: would you like to introduce the idea?14:06
hemanth_markwash: sure14:06
hemanth_with import, we can see a wide range of images getting imported into the cloud. Most of these may be created outside the cloud and thereby may not be very trusted14:08
hemanth_so, in the event we see a 'bad' image getting imported, we need a way to stop further operations on this image.14:08
hemanth_like booting servers off of it and sharing it further with other users14:09
markwashso is this sort of an admin api use case?14:09
rosmaitai think it's not so much the import action itself, it's just the existence of a "bad" image in the cloud14:09
flwanghemanth_: so it sounds like an admin operation14:10
flwang?14:10
rosmaitacould protect with policies14:10
hemanth_markwash, flwang: one of the use cases admin bp, yes14:10
flwangrosmaita: +114:10
rosmaitacould also be a user-level operation in some clouds14:10
*** jmaron has joined #openstack-meeting-alt14:10
flwangseems we should say the import action make the bad image possibility more bigger14:11
jokke_How about user flagging possibility?14:11
markwashif an image is suspended, no one can boot it? or no one its shared with can boot it?14:11
rosmaitaflwang: not necessarily, you can take a snapshot of a current server and shar that14:11
*** vponomaryov has joined #openstack-meeting-alt14:11
rosmaitamarkwash: i think no one can boot it14:11
hemanth_markwash: no one can boot it14:11
rosmaitabut we don't control booting, so i guess no one can download it?14:12
flwanghemanth_: could we just mark the image with a reserved tag?14:12
zhiyanrosmaita: and don't expose direct location maybe14:12
*** Guest50701 has joined #openstack-meeting-alt14:12
rosmaitawell, for this to be effective I guess no locations should be exposed14:13
arnaud__is it the responsibility of Glance of checking if a guest OS is trusted?14:13
rosmaitaarnaud__: i don't think so14:14
flwangarnaud__: +1, and I think it's hard to detect14:14
*** rkukura has left #openstack-meeting-alt14:14
rosmaitabut we do need to supply a way to stop user of images under investigation14:14
Guest15113arnaud__: no, however the catalog needs to have a way to flag that14:14
hemanth_arnaud__: not glance's responsibility but we want glance to know abut such an image14:14
*** jbernard has joined #openstack-meeting-alt14:14
*** Guest15113 is now known as nikhil__14:14
flwanghemanth_: I agree from this POV14:14
rosmaitaall i can thnink of as a current option, is just delete the image14:14
flwangnikhil__: hey there14:15
rosmaitawhich is really bad in event of a mistake14:15
nikhil__hey14:15
arnaud__ok, so this might look silly but why would you keep this image in your cloud?14:15
zhiyanactually i'm a little trend to think that client side, e.g. nova (or others like cinder ?) should also do some change to take care that flag..14:15
rosmaitathe other image statuses don't seem appropriate , e.g., queued14:15
rosmaitaarnaud__: in case you are wrong14:15
rosmaitathis is a public cloud use case, i guess14:15
zhiyanlike do a check before vm snapshot14:15
zhiyanto prevent guest upload a bad image14:16
flwangzhiyan: check what?14:16
rosmaitazhiyan: what flwang said14:16
zhiyanflag within the metadata14:16
hemanth_zhiyan: if the instance was booted from a suspended image?14:16
markwashdarn it, I started talking in the wrong chat room :-(14:16
arnaud__lol14:16
hemanth_hah14:16
flwangwelcome back to earth, markwash14:17
zhiyanhemanth_: i think it is14:17
nikhil__arnaud__: to do more checks on the image and determine it's usability14:17
markwashhaha14:17
markwashI was thinking, it seems like this could be done with protected properties and client-side behavior as well14:17
nikhil__markwash: copy pasting your chat from other window14:17
markwashit seems like restricting download is a bit heavy-handed14:17
arnaud__nikhil__: ok so the admin is still able to download the image14:18
nikhil__arnaud__: may be (optionally)14:18
arnaud__nikhil__: otherwise, how can you check something that you cannot get14:18
arnaud__:)14:18
zhiyanmarkwash: (i'm thinking latter one maybe using image handler in nova...)14:18
hemanth_markwash: +1 but that would be an implicit way of doing things maybe?14:18
nikhil__arnaud__: yeah, something like that restricting the image to validator or auditor of some sort14:18
arnaud__I see14:18
*** eankutse has joined #openstack-meeting-alt14:19
nikhil__09:15:14 [ markwash] its an interesting idea, its a bit hard to think of how it might work though, since it seems like glance doesn't really control the booting process14:19
hemanth_markwash: like as a user if I see my image in state 'suspended' I would know there is something wrong14:19
nikhil__09:15:24 [ markwash] and restricting download is a bit heavy handed14:19
nikhil__09:15:46 [ markwash] maybe there could be a protected property "suspended" that nova would honor?14:19
*** eankutse has quit IRC14:19
nikhil__09:16:16 [ markwash] or something that functions equivalently?14:19
rosmaitaarnaud__ you could restrict/allow access by policies14:19
*** eankutse has joined #openstack-meeting-alt14:19
*** haleyb has quit IRC14:19
arnaud__rosmaita: ok this makes sense14:19
markwashhemanth_:  I think you could still see "suspended = yes" on the image14:19
flwangFWIW, I think we need a way to avoid the bad image be spreaded14:20
*** AlanClark has joined #openstack-meeting-alt14:20
rosmaitamarkwash: i don't like the nova-honor-flag idea, if we know at the glance level that this is not a good image, should handle it here14:20
arnaud__a bad image can be still shared?14:20
nikhil__nope14:20
rosmaitaarnaud__ i think yes14:20
rosmaitawhy not, no one can boot from it?14:21
zhiyanflwang: avoid the bad image be used. usage including: download; direct access via location info; snapshot vm which based on that bad image...and others?14:21
rosmaitaand if bad, it will ultimately be destroyed14:21
*** kevinconway has joined #openstack-meeting-alt14:21
rosmaitaif a mistake, un-suspend, and no harm done14:21
markwashrosmaita: so suspended would prevent download and make sharing behave as 'private' ?14:21
flwangmarkwash: sounds reasonable14:21
rosmaitai don't know if we need to affect sharing14:22
flwangit would a suspend/resume14:22
rosmaitaas long as you can't boot14:22
arnaud__+1 flwang14:22
rosmaitai'm thinking we don't have to make it too complicated14:22
markwashI guess its just, there is no "image.boot" action :-)14:22
*** sarob has joined #openstack-meeting-alt14:22
rosmaitaright, so that's why no-download14:22
flwangrosmaita: I prefer to prevent sharing14:22
markwashthat's the only reason I feel a bit weird about it14:23
rosmaitawell, look at it this way14:23
rosmaitabooting is the thing we want to prevent ultimately14:23
rosmaitabut right now, we just don't want anyone using the image14:23
arnaud__is you do an image-list, do you plan to have the image listed? yes I assume14:24
rosmaitayes14:24
arnaud__s/is/if14:24
flwangarnaud__: yes, it will be there14:24
rosmaitawith status 'suspended' or 'inactive'14:24
markwashwell, the general problem description makes a lot of sense to me, and it seems like the proposed approach has merit14:24
flwangflwang: and I would like to see there is a tag or property indicating the suspending status14:25
markwashso, blueprint?14:25
flwangrosmaita: are you saying add a new status?14:25
rosmaitaflwang: yes, that's what i think14:25
nikhil__my assumption might be a bit pessimistic however, feel like we should not allow sharing14:25
rosmaitaneed to settle whether that's a good idea befoe going to a bp, i think14:25
rosmaita(a new status, i mea)14:25
rosmaitas/mea/mean/14:26
*** irenab has quit IRC14:26
zhiyanprobably adding a new status is a easy way to go: https://github.com/openstack/nova/blob/master/nova/compute/api.py#L60014:26
nikhil__as that would mean that validator is being trusted and that may not always be true14:26
nikhil__as we want to restrict bad images and allow "only" good images14:26
hemanth_I like adding a new status14:26
nikhil__all shades of gray should be considered bad images, no?14:26
markwashrosmaita: I think we can go with the new status strategy as the currently planned approach and write up the blueprint and spec?14:26
rosmaitahemanth: want to work with me on this?14:27
markwashwe also need to think about how users will find out about this, probably through nova or cinder14:27
hemanth_rosmaita: gladly14:27
zhiyanhemanth_: so i think it will be better if you can create a bp, and give a definition for "suspend".14:27
rosmaitazhiyan: +114:27
hemanth_zhiyan: sure14:27
markwashI think you should also consider the case of nova server rebuild14:27
flwangmarkwash: and I would like to see some thoughts from the consumer POV14:27
flwangsuch as Nova, Ironic..14:27
zhiyanflwang: and cinder14:28
rosmaitaok, we will add some options14:28
zhiyanimage <==> volume conversion14:28
markwashokay, next up14:28
markwash#topic status checkin for artifacts api14:28
*** openstack changes topic to "status checkin for artifacts api (Meeting topic: glance)"14:28
*** saju_m has quit IRC14:28
markwashjbernard: i have not had time to digest your email14:29
gokrokveHi14:29
markwashgokrokve: hi there!14:29
gokrokveWe have submitted couple new BPs14:29
jbernardmarkwash: the response was good, a few minor issues14:29
arnaud__gokrokve: could you share URL here?14:30
gokrokvehttps://blueprints.launchpad.net/glance/+spec/artifact-repository-api14:30
gokrokveHm. There should be another BP for datamodel, but I don't see it.14:32
gokrokveI will open it.14:32
markwashso it looks like we're making some progress in the design phase14:32
*** venkatesh has joined #openstack-meeting-alt14:33
markwashgokrokve: based on our discussions I'll be very easy to see the data model bp :-)14:33
iccha_hey14:33
gokrokveYes. We have a question about storage.14:33
flwangiccha_: hey there14:33
arnaud__hi iccha_!14:33
gokrokveI think it will be possible to use existing storage drivers to store artifacts.14:33
jbernardi hope so :)14:34
*** esker has joined #openstack-meeting-alt14:34
gokrokveGreat. So we will abb BP for that too.14:34
zhiyangokrokve: do you think if we need some new interface to store driver?14:34
*** esker has quit IRC14:34
gokrokvezhiyan: No. Artifacts itself just text files or binaries.14:34
markwashokay cool14:34
zhiyangokrokve: thanks14:34
*** esker has joined #openstack-meeting-alt14:35
*** ywu has joined #openstack-meeting-alt14:35
markwashso more blueprints from gokrokve14:35
markwashand jbernard after a little more feedback on the instance template stuff will share it a bit more widely14:35
markwashsounds good to me14:35
*** nwidell has quit IRC14:35
gokrokveAs I see now, artifact will be parsed by plugin during upload and then glance will store it as a solid entity.14:35
zhiyangokrokve: but iirc, you had mentioned versionning, maybe it's another case..14:35
jbernardyep, i think it should come together nicely14:35
arnaud__gokrokve: what do you mean by solid entity?14:36
gokrokveGlance do not split or modify them for storing.14:36
rosmaitagokrokve: +1 for solid entity14:36
arnaud__does that mean that if an artifact contain (1 metadata file, 1 binary, 1 image) it will be a solid entity?14:37
zhiyanA little confused on "plugin", glance now doesn't support api extension/plugin mechanism14:37
gokrokveYes, it should be apackage which has one ID.14:37
markwashwell, I think there's a lot of details we'll need to see in the context of the blueprints14:37
gokrokvezhiyan: We plan to add this in artifacts API14:37
markwashits a little confusing to find out about them trickle by trickle14:38
arnaud__but can you still access only the metadata file for example, without accessing the binary?14:38
flwangmarkwash: it would be nice if there is a wiki page associated with the bp14:38
flwangarnaud__: let discuss the details in Glance channel?14:38
arnaud__yes14:38
*** akuznetsov has quit IRC14:38
arnaud__sure14:38
gokrokvearnaud__: I dont think so. Metadata will be stored separately14:38
jbernardit will be nice when this is all documented14:39
flwanggokrokve: yep, since glance can store metadata14:39
gokrokveThe idea was that Glance artifact plugin can parse artifact content ant pass some data to associated metadata14:39
markwashfor my part, I pitched the instance template idea somewhat here at the nova meetup14:39
markwashand it was met with some support14:39
markwashit seems like once we get it going, we can add a nova extension that allows booting through instance templates14:40
rosmaitait might be good to do a FAQ on this so we can ask questions and see the vision on one page14:40
gokrokvejbernard: Sure. We are working on that. We had no much time for that during this week as we are working on Murano incubation documents now.14:40
flwangmarkwash: sounds cool14:40
markwashand it should not require a ton of internal nova changes14:40
arnaud__flwang: I have the ovf use case in mind and I would like to store the ovf and the image associated as an artifact. In this case I don't want the ovf to be stored as metadata. I want to make sure this use case is covered14:40
markwashre FAQ and more documentation, I don't really think we should do design review in this meeting14:40
zhiyanmarkwash: so mark, i think seems we'd better start to think about plugin framework for glance .. seems, for now i'm not sure the "plugin" in this context is working on which level14:40
*** sarob has quit IRC14:40
markwashmostly just checking in to see what folks are working on, and do the design review with documents offline14:41
flwangarnaud__: I was thinking the ovf case as well, we can discuss that offline14:41
arnaud__flwang: yes sure :)14:41
flwangarnaud__: I think it's not very related to this, right?14:41
markwashzhiyan: yes, its unclear from the details given here, but I believe the plugin aspect will make plenty of sense later14:41
arnaud__flwang: I think we need more details about the scope of artifacts. so let's wait for some initial doc :)14:42
markwashlet's have a look at blueprints for icehouse-314:42
markwash#topic blueprints for icehouse-314:42
*** openstack changes topic to "blueprints for icehouse-3 (Meeting topic: glance)"14:42
zhiyanmarkwash: i just think this part seems is  dedicated then artifacts api14:42
markwash#link https://launchpad.net/glance/+milestone/icehouse-314:42
*** NehaV has joined #openstack-meeting-alt14:42
markwashnikhil__: any new work available for async / export / import?14:43
markwashis it more obvious now which of those bps should be in icehouse and which should not?14:43
nikhil__markwash: we found some more complications added to both import and export script which was demonstrated in the summit (it's still internal)14:44
nikhil__I'm working through it to fiure out how and what we can scrap things from it to make them pluggable14:44
markwashnikhil__: previously we said maybe the async bp could be dropped and track the work under "import" does that sound okay?14:45
nikhil__so, in short did not get enough time to push up a new MP however, have come to a better idea of what needs to be done14:45
*** nwidell has joined #openstack-meeting-alt14:45
*** nwidell has quit IRC14:45
nikhil__markwash: many of the previous MPs are under that so, may be move them or rename it?14:45
nikhil__not sure how the process works14:45
*** NehaV1 has joined #openstack-meeting-alt14:46
nikhil__that = async bp14:46
markwashare the MPs still out and active in gerrit?14:46
markwashor are these ones that have merged?14:46
flwangnikhil__: maybe you just need to update the commit message?14:46
*** rraja has joined #openstack-meeting-alt14:46
nikhil__yeah, the merged ones14:46
markwashfor merged ones it doesn't matter14:46
nikhil__and one of flwang's glanceclient MP is out in gerrit14:46
flwangnikhil__: I don't think we need care aout the merged14:46
markwashokay, then I'm going to mark asynch as superceded by import14:47
nikhil__sure14:47
flwangnikhil__: we can just leave the glance client patch there14:47
markwashmoving on to glance.stores14:47
*** aostapenko has joined #openstack-meeting-alt14:47
markwashflaper87: you've put together some documents about the glance.store approach14:47
*** NehaV has quit IRC14:47
markwashI have not digested them yet14:47
flaper87markwash: yup14:47
flaper87I linked it to the blueprint14:47
markwashcool14:48
flaper87in case other folks want to chime it14:48
flaper87in14:48
*** aostapenko has left #openstack-meeting-alt14:48
flaper87I'd love to have some feedback from other folks14:48
markwash#link https://etherpad.openstack.org/p/glance-store-package14:48
flaper87about the migration plan I wrote there14:48
markwashsounds good, let's take the feedback onto some designated section of the etherpad, if that's okay14:49
markwashand we'll leave this one in14:49
markwash#topic image location status property14:49
*** openstack changes topic to "image location status property (Meeting topic: glance)"14:49
markwashit looks like the code was updated and some merged for the migration, correct?14:49
markwashzhiyan: ^14:49
zhiyanmarkwash: yes just been merged (and catch a race condition bug)14:50
*** aostapenko has joined #openstack-meeting-alt14:50
markwashzhiyan: all the code for this is up for review now, correct?14:50
markwashso I could mark the blueprint as "needs code review"14:50
zhiyanmarkwash: YES, pls folks give reviews thanks14:50
markwashzhiyan: thanks!14:50
zhiyanmarkwash: thanks mark14:50
markwash#topic virtual image size14:51
*** openstack changes topic to "virtual image size (Meeting topic: glance)"14:51
markwash#link https://blueprints.launchpad.net/glance/+spec/split-image-size14:51
nikhil__win 2614:51
markwashflaper87: it looks like you have code up for both the migration and api bits14:51
markwashso this just needs review as well?14:51
flaper87markwash: it was actually approved earlier today but it conflicted with zhiyan patch14:52
flaper87so, I just rebased it and it's up waiting for a ninja approve14:52
flaper87:D14:52
markwashokay great14:52
zhiyan(i believe 033 migration version is been used by location status db change)14:52
flaper87zhiyan: right14:52
flaper87I allocated 3414:52
markwash#topic i18n message improvements (flwang)14:53
*** openstack changes topic to "i18n message improvements (flwang) (Meeting topic: glance)"14:53
markwash#link https://blueprints.launchpad.net/glance/+spec/i18n-messages14:53
markwashflwang: is all the code up for this as well?14:53
zhiyanflwang: i will revist it on my tomorrow morning14:53
flwangmarkwash: the patch has been reviewed several rounds, and no more patch for this bp14:53
flwangzhiyan: thanks14:53
markwashflwang: great, I'll look again soon as well14:53
flwangmarkwash: yes14:53
flwangmarkwash: cool, thanks14:53
markwash#topic community-level sharing14:54
*** openstack changes topic to "community-level sharing (Meeting topic: glance)"14:54
markwashiccha_: you have some questions about the initial direction on this one14:54
iccha_i think i am going along with rosmaita s proposal in wiki14:54
iccha_and started work on it14:54
markwashgreat!14:54
markwashokay I think that covers our blueprints for icehouse-3 that have >low priority14:55
zhiyanthank you markwash14:55
markwashhas anyone had a chance to look at this bug14:55
markwash#link https://bugs.launchpad.net/glance/+bug/123686814:55
markwashthere has been code up for a while14:56
zhiyanmarkwash: tbh, iiuc, i think that metadata query is necessary, since14:56
*** balajiiyer has joined #openstack-meeting-alt14:56
zhiyanmarkwash: the status of image can be change via another client upload request, under concurrent context14:57
*** balajiiyer has left #openstack-meeting-alt14:57
*** achirko has joined #openstack-meeting-alt14:57
markwashhmm, but I thought the goal was to make it so that we *only* update to active or killed if no other client has already changed it from 'saving' ?14:57
zhiyanmarkwash: i think that just is what dosaboy try to prevent by this fixes14:58
*** richm has joined #openstack-meeting-alt14:58
*** csaba|afk is now known as csaba14:58
zhiyanmarkwash: so dosaboy need a query14:58
zhiyanto mark sure the *current* status of the image14:58
markwashhmm, maybe we better follow up in the review due to time limitations14:59
zhiyansure14:59
markwashjust wanted to keep the priority on this one high :-)14:59
*** bill_az_ has joined #openstack-meeting-alt14:59
*** bswartz has joined #openstack-meeting-alt14:59
markwashall right, I've got a 15 hour drive to catch14:59
bugsdugganSomething to draw your attention to - python-swiftclient enabling SSL cert checking https://review.openstack.org/#/c/69187/14:59
bugsdugganjust FYI14:59
*** vbellur has joined #openstack-meeting-alt14:59
markwashbugsduggan: thanks!15:00
markwashbye folks!15:00
iccha_bye markwash !15:00
flwangbye15:00
bugsduggan\o15:00
arnaud__bye15:00
flwangthanks, markwash15:00
zhiyangood luck15:00
markwashzhiyan: I have a day full of driving, could not message you privately for some reason, but unfortunately I have to go and won't be back until tomorrow15:00
markwash#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Thu Feb 13 15:00:50 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-02-13-14.03.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-02-13-14.03.txt15:00
*** jbernard has left #openstack-meeting-alt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-02-13-14.03.log.html15:00
zhiyanmarkwash: ok np15:01
*** xyang2 has joined #openstack-meeting-alt15:01
*** Ranjitha has joined #openstack-meeting-alt15:01
*** bugsduggan has left #openstack-meeting-alt15:01
bswartz#startmeeting manila15:01
openstackMeeting started Thu Feb 13 15:01:55 2014 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: manila)"15:01
openstackThe meeting name has been set to 'manila'15:02
*** jokke_ has left #openstack-meeting-alt15:02
*** japplewhite has joined #openstack-meeting-alt15:02
aostapenkohello everyone :)15:02
bswartzgood morning / good evening everyone15:02
*** koofoss has quit IRC15:02
xyang2hi15:02
scottdahi all15:02
achirkohello15:02
bswartz#link https://wiki.openstack.org/wiki/ManilaMeetings15:02
vponomaryovhi15:02
csabahello15:02
rrajahi15:02
*** Barker has quit IRC15:02
vbellurhi15:02
bill_az_Hi everyone15:03
bswartz#topic incubation15:03
*** openstack changes topic to "incubation (Meeting topic: manila)"15:03
bswartzSo we've been talking to the TC again about incubation15:03
*** arnaud__ has quit IRC15:03
bswartzthe official requirements are ever-changing, but here is the current list:15:03
bswartz#link http://git.openstack.org/cgit/openstack/governance/tree/reference/incubation-integration-requirements15:03
bswartzthe main things that affect us here are:15:04
bswartz** Reviews should follow the same criteria as OpenStack projects (2 +2s before +A)15:04
*** haleyb has joined #openstack-meeting-alt15:04
*** akuznetsov has joined #openstack-meeting-alt15:04
bswartz** Project must have a diverse core reviewers team (more than 4 people)15:04
*** ndn9797 has joined #openstack-meeting-alt15:04
ndn9797Hi all..15:05
bswartzerr15:05
bswartzthere's another one I can't find15:05
*** markwash has quit IRC15:05
vponomaryov** Project APIs should be reasonably stable15:05
bswartzBut clearly the intention from the TC is that we need to be a large team with multiple contributing entities15:05
vbellurbswartz: do we have a ballpark for the definition of large?15:06
bswartzinterestingly, the requirement that the code should be production-ready seems to have disappeared15:07
bswartzvbellur: ** Project must have a diverse core reviewers team (more than 4 people)15:07
vbellurbswartz: ok15:08
bswartzand while it doesn't say so specifically, I think it's expected that those people don't all work for the same organization15:08
*** pballand has joined #openstack-meeting-alt15:08
bswartzso those of you who are making large contributions but are not in the core team I'm looking to grow the core team15:09
bswartzreviews are also greatly appreciated -- especially because my time for core reviews is unfortunately limitted15:09
bswartzs/core/code/15:09
bswartzso enough on that, read the doc if you're interested15:10
bswartz#topic Atlanta Summit15:10
*** openstack changes topic to "Atlanta Summit (Meeting topic: manila)"15:10
bswartzSo I know that Atlanta is still a long ways off15:10
bswartzhowever, it's looking like NetApp will be able to sponsor some conference sessions specifically for Manila15:10
vbellurbswartz: that sounds great15:11
bswartzWe would like to be able to show off some demos of Manila doing cool things15:11
bswartzso between now and then I've asked the dev team to start working on stuff like Horizon plugins in addition to core manila stuff15:12
eskerHere's our checklist for incubation "to do's"15:12
eskerhttps://wiki.openstack.org/wiki/Manila/Graduation15:12
bswartzesker: hey!15:12
bswartzgood morning15:12
eskerbswartz: good morning15:13
bswartzThere are probably some other features we could add which aren't strictly necessary but would demo nicely, such as volume_type support15:13
eskershare_type15:13
esker;-)15:13
bswartzvolume_type support is something we've always known we needed to add but a possible demo in atlanta ups the priority of that work15:14
bswartzesker: I actually prefer volume_type over share_type for several reasons15:14
bswartzbut whatever it's called, it's functionality we need to add15:14
bswartzI'm looking for other ideas for features we could add or fix up that would contribute to a more successful demo15:15
bswartzand between now and Atlanta I'll be doing checkpoints against our progress towards that end15:15
xyang2is this demo netapp only, or will it include other backends?15:15
bswartzanything else on this before we move on?15:15
bill_az_it would be good to show multi-backend if possible - backends for several vendors working together is a good openstack thing15:16
scottdaI don't see a blueprint for file-type of share-type. Is there one?15:16
eskerI think demonstrating multiple backends would be fantastic15:16
*** Barker has joined #openstack-meeting-alt15:16
bswartzxyang2: the more backends the better -- demonstrating multibackend support with multiple hardware vendors would be very compelling I think15:16
xyang2that's true15:16
bswartzat this time I think we can commit to showing off the generic backend and the netapp backend15:17
bswartzwe have some time to add others15:17
xyang2or maybe you can show some recorded demo of other backends15:17
xyang2are you going to do live demo15:17
bswartzheh, live demos carry a certain amount of risk15:18
*** jergerber has joined #openstack-meeting-alt15:18
bswartzI don't think we've decided on that yet15:18
xyang2right15:18
vbellura failure in a live demo makes it look authentic :)15:18
bswartzin principle we could do a live demo, but recorded would be the fallback plan15:18
*** banix has joined #openstack-meeting-alt15:18
bswartzvbellur: hah!15:18
bswartzokay next topic15:19
bswartz#topic dev status15:19
*** openstack changes topic to "dev status (Meeting topic: manila)"15:19
*** akuznetsov has quit IRC15:19
eskera failure in a live demo would be tolerated better in a design summit session... but we're proposing to do this in the conference format.  I'd prefer to avoid folks leaving w/ a negative impression (especially  since it'll like be the first exposure for most to Manila).15:19
bswartzvponomaryov: do you have status for us this week?15:20
vponomaryovyes, sure15:20
vponomaryovDev status:15:20
vponomaryov1) Activation/deactivation api: https://blueprints.launchpad.net/manila/+spec/share-network-activation-api15:20
vponomaryovGerrit:15:20
vponomaryov(server) https://review.openstack.org/#/c/71936/15:20
vponomaryov(client) https://review.openstack.org/#/c/71497/15:20
vponomaryov2) Generic driver has been merged - https://review.openstack.org/#/c/67182/15:20
vponomaryov3) NetApp Cmode driver - https://review.openstack.org/#/c/59100/15:20
vponomaryovFinal stage of review.15:20
vponomaryov4) Horizon intagration estimation: it is upto 10 man-days.15:21
vponomaryov5) Volume types estimation: https://docs.google.com/document/d/1q1cz5TRBAXTev9hyswIGCy7lCPFE3slzmc9I-nwWrlw/edit?usp=sharing15:21
vponomaryovnow, OPEN ITEMS:15:21
vponomaryova) options "image" and "flavor" for share-network-activation api command15:21
*** zhiyan has left #openstack-meeting-alt15:22
vponomaryovb) update devstack plugin for using generic driver?15:22
vponomaryovdependencies: lightweight image, and reliable storage for it. Implementation of activation api for share-networks.15:22
vponomaryovTODO:15:22
*** Barker has quit IRC15:22
vponomaryov- implement support of share-network activation/deactivation for generic and cmode driver after resolving open item for (1).15:22
*** sarob has joined #openstack-meeting-alt15:22
*** akuznetsov has joined #openstack-meeting-alt15:22
vponomaryov- horizon integration and testing15:22
vponomaryov- volume types integration and testing15:22
vponomaryovthats all for status15:23
bswartzvponomaryov: wow15:23
bswartzyou're always well prepared vponomaryov15:23
vponomaryov=)15:24
bswartzokay so the activation API needs some discussing15:24
bswartzI was reviewing it and I saw some stuff I didn't like15:24
vponomaryovso, activation api is considered as admin-api only15:24
*** ftcjeff has joined #openstack-meeting-alt15:25
vponomaryovthere are default values for image and flavor for service VM15:25
bswartzvponomaryov: why wouldn't we want tenants to be able to call it?15:25
*** zhiyan has joined #openstack-meeting-alt15:25
vponomaryovhm, we need clarify one thing15:25
vponomaryovwe have tenant admins15:26
vponomaryovand we have cluster admin15:26
bswartzisn't the point of the API so that tenants can error check the values they passed in for share-network-create?15:26
*** zhiyan is now known as zhiyan_15:26
vponomaryovno, share-network-create doesn't have check15:27
vponomaryovit is another api command15:27
*** sarob has quit IRC15:27
bswartzI don't see any scenario where it's safe to allow tenants to start up a VM in the service network that's running a tenant-created glance image15:27
bswartzvponomaryov: right, it's separate, but the reason we're adding it is so that they can call the second API to force the vserver to get created right away15:28
vponomaryovyes, create VM, it is needed for Generic driver15:28
bswartzI think tenant should be allowed to force the VM to be created, but they should not be allowed to control the glance image or nova flavor under any circumstance15:29
*** chandankumar_ has joined #openstack-meeting-alt15:29
*** chandan_kumar has quit IRC15:29
*** Ranjitha has quit IRC15:30
vponomaryovif it is admin of tenant, why we should restrict to set custom image or flavor15:30
bswartzthe flavor because the VM will be outside their quota and we don't want to allow tenants to abuse that15:31
*** Barker has joined #openstack-meeting-alt15:31
*** jcoufal has quit IRC15:31
bswartzthe glance image because the VM will have routes to the backend network and therefore represents a security risk if mailcious software is installed in the glance image15:31
bswartzwe have to assume that the tenant/user of manila may be evil and want to try to takeover the openstack cluster15:32
*** IlyaE has joined #openstack-meeting-alt15:33
vponomaryovOk, I see your point15:33
bswartznote that there's nothing to prevent a user today from creating a glance image with nfsd/samba and runninging it themselves if they want to self-serve file access on top of a cinder provided-volume15:34
*** marun has joined #openstack-meeting-alt15:34
bswartzthey just won't be able to do that through manila15:34
bswartzalso -- it's important that backend-specific details of the generic driver do no bleed through to the tenant-facing API15:35
bswartzbecause the tenant should be unaware of which backend they are talking to15:35
vponomaryovthere is no problem with it, while it is optional15:36
bswartzthose parameters would need to be admin-only in order to be safe15:36
bswartzbut I don't see the point of admin-only parameters which overlap with values in cinder.conf15:36
bswartzI'd like the APIs themselves to be tenant-accessible15:36
bswartzwith no optional parameters15:36
bswartzthe use case is:15:37
*** pballand has quit IRC15:37
bswartz1) create share network15:37
bswartz2) activate share network (using new API)15:37
bswartz3) find out if there are any errors with the config15:37
bswartz4) create shares15:37
bswartzactually we could add a flag to create share network which optionally activates it too15:38
bswartzbut it's important to allow creating a share network and not activiating it15:38
bswartz(at least I think it is)15:38
*** colinmcnamara has quit IRC15:38
bswartzenough on that15:39
csababswartz: let me talk on service vm image project15:39
bswartzCongrats to us for the generic driver going upstream!15:39
bswartzcsaba: just a moment15:39
csabasorryh15:39
*** atiwari has joined #openstack-meeting-alt15:40
*** baoli_ has joined #openstack-meeting-alt15:40
bswartzI'm still reviewing the NetApp driver -- anyone who wants to help please do today15:40
bswartzvponomaryov mentioned the 2 new items we're looking at after the drivers are in15:40
bswartzvponomaryov: did you want to talk about a lightweight image?15:41
*** dripton__ is now known as dripton_shovelin15:41
vponomaryovbswartz: csaba wanted to say about it15:41
*** baoli_ has quit IRC15:41
bswartzoh I get it15:41
*** baoli has quit IRC15:41
csabas/vponomaryov/csaba/ :)15:41
bswartzI didn't get the relation15:41
bswartzlol15:41
*** betsy has quit IRC15:42
bswartz#topic lightweight service VM image15:42
*** openstack changes topic to "lightweight service VM image (Meeting topic: manila)"15:42
csabayep15:42
bswartzcsaba go ahead15:42
*** baoli has joined #openstack-meeting-alt15:42
csabaso took cirros, lp:cirros15:42
csabawhich is a fine project but was a bit bit-rotten15:42
csabaconverted to git with buildroot as submodule15:43
*** sankarshan is now known as sankarshan_away15:43
csabaas cirros is just a buildroot customization/wrapper project15:43
csabaand added all stuff that we need / can make use of for the service vm15:43
csaba#link https://github.com/csabahenk/cirros15:43
csaba#link https://github.com/csabahenk/cirros/commits/manila-service-generic15:44
csabaso  manila-service-generic is the branch you should build from15:44
bswartzcsaba: this is awesome15:44
*** xuhanp has quit IRC15:44
csabawe need community testing as we don't have yet a deployment with generic driver15:44
aostapenkocsaba: thanks15:45
vponomaryovcsaba: sounds great15:45
csabawill build and publish images soon15:45
csababut in the meantime you can try to build yours15:45
*** jmontemayor has joined #openstack-meeting-alt15:45
csabaof course any comment / contribution is welcome :)15:46
*** jecarey has joined #openstack-meeting-alt15:46
bswartzso I'm not in favor of mandating a standard image -- I would rather document the requirements for the image and allow deployers to make their own -- but providing a reference image will be HUGELY helpful15:47
bswartzI bet that 90%+ of admins will probably stick with the reference image15:47
bswartzthe question is how to distribute and promote the reference imge15:47
bswartzimage15:47
bswartzbecause we're basically talking about another project15:48
bswartzcsaba: what are the chances of your changes going back upstream to cirros?15:48
csababswartz: well its a further customization for specific purposes15:48
csabacirros' original ambition is to be a demo image15:49
csabaa toy not a tool15:49
bswartzyeah I get that15:49
vponomaryovI whould like to have that toy for testing =)15:49
bswartzbut if we don't push the changes back into cirros the alternative is to maintain our own branch or else fork it15:49
csabaso I didn't think of merging back15:49
csabacirros is not changing since a while15:50
bswartzwe would want the bits for the modified cirros image to be underthe control of the manila-core team if we're going to promote it as a reference image and use it for tempest testing, etc15:50
csababut yeah I can notify the original author what's his plans and optionon15:51
*** ndn9797 has quit IRC15:51
*** atiwari has quit IRC15:51
csabawhere would the ref images be hosted?15:51
bswartzcsaba: how is cirros hosted now?15:51
csabacode is on launchpad15:52
eskerlaunchpad15:52
eskerhttps://launchpad.net/cirros/+download15:52
bswartzno not the source -- the binary15:52
csabaimages are community contributions I think\15:52
eskerlook again... binaries are there15:52
bswartzoh I see the releases are there too15:52
vponomaryovTempest has next: http://download.cirros-cloud.net/0.3.1/cirros-0.3.1-x86_64-uec.tar.gz15:52
bswartzwell we should do something like this15:53
bswartzperhaps a manila-reference-image project on LP15:53
bswartzwith the same governance as manila and python-manilaclient15:54
bswartzuh oh the power is looking unstable here in RTP15:54
bswartzmy connection may drop, so let's wrap up the meeting15:54
bswartz#topic open discussion15:54
*** openstack changes topic to "open discussion (Meeting topic: manila)"15:54
*** aignatov is now known as aignatov_15:54
eskerwould prefer to just use the existing cirros project if the maintainers are agreeable15:55
bswartzesker: it's just smoser who maintains it15:55
csabaesker: the scope is different IMHO15:55
bswartzesker: and it sounds like smoser is not particularly active anyways15:55
eskerOkay... the linux distro tree grows another branch15:56
bswartza very small branch, but yes15:56
bswartzlinux distros are a dime a dozen though15:56
bswartzanyone else have something?15:56
bill_az_regarding ganesha nfs - admin functions - has anyone played with that much yet? Things like adding / removing exports are a bit difficult today15:56
bswartzbill_az_: that's good feedback -- I wasn't aware15:57
bill_az_adding export requires editting ganesha conf and restarting server - there is dbus interface, but not fully baked yet15:57
bill_az_I was wondering if anyone else has experimented with this?15:57
vbellurbill_az_: I believe there is ongoing work to avoid restarting the server?15:57
bswartzI would love to start using ganesha so we can shake out issues and start filing bugs with that project15:57
eskerhow is ganesha nfs used in this context?  Are we not using in kernel NFS in the cirros branch?15:58
bill_az_vbellur:  that's correct - planned for later this year is my understanding.15:58
bswartzthe sooner we find the bugs the sooner we can get them fixed and start using it heavily15:58
bswartzesker: this is regarding the gateway-mediated multitenancy15:58
bswartzstuff that's needed by GlusterFS, etc15:58
eskerah, okay15:58
bill_az_I've written some wrappers that I'm using with gpfs share driver -15:58
bswartzthe generic driver does not use ganesha currently15:58
*** agileclipse has quit IRC15:59
bswartzalthough we could decide to change that if ganehsa proves to be better15:59
*** alagalah has joined #openstack-meeting-alt15:59
alagalahMorning15:59
bswartzand that's about all we have time for15:59
bswartzthanks everyone15:59
aostapenkothanks, bye15:59
vponomaryovthanks15:59
bswartz#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu Feb 13 16:00:04 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-02-13-15.01.html16:00
eskerconcern w/ ganesha is sustainability... I feel better about in-kernel NFS being well maintained on an ongoing basis16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-02-13-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-02-13-15.01.log.html16:00
*** achirko has quit IRC16:00
eskerwrt the reference image16:00
mesteryGood morning Group Policy folks!16:00
banixHello Neutron Policy makers!16:00
marunmorning16:00
bswartzpls move the discussion to #openstack-manila16:00
mestery#startmeeting networking_policy16:00
openstackMeeting started Thu Feb 13 16:00:43 2014 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: networking_policy)"16:00
openstackThe meeting name has been set to 'networking_policy'16:00
banixmestery: Hi; made a minor change to the agenda just a minute ago; added a line essentially16:00
mestery#link https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy Agenda16:01
mesterybanix: Great!16:01
*** VINOD has joined #openstack-meeting-alt16:01
mesterySo, it's been 2 weeks since we've met. The OpenDaylight Summit pulled some of us away for the past two weeks.16:01
mesterySo, lets review Action Items first.16:01
mestery#topic Action Item Review16:01
*** openstack changes topic to "Action Item Review (Meeting topic: networking_policy)"16:01
mesterySumitNaiksatam: Here?16:01
*** rraja has left #openstack-meeting-alt16:01
*** bswartz has left #openstack-meeting-alt16:02
mesteryThe shared github has changed from the project page, SumitNaiksatam has setup a new one.16:02
mesteryI will update the meeting page with the details, apologies for not having done that now.16:02
mesteryBut banix and s3wong are aware of this already.16:02
*** Leonr has joined #openstack-meeting-alt16:02
banixmestery: Could you please also write a couple of lines about how the git is to be used; with having own branches wtc16:03
mesteryFYI: The new link is this: https://github.com/noironetworks/neutron-group-policy16:03
mesterybanix: Yes, SumitNaiksatam added some notes on that, I'll add an action item to that effect.16:03
banixmestery: as Sumit suggested so we are all on the same page16:03
mesteryGood call.16:03
banixmestery: thanks.16:03
marunis there a reason not to use stackforge?16:03
mesterymarun: That's another good question.16:03
maruncode review on github stinks16:04
banixmarun: what are the benefits16:04
banixmarun: I see16:04
mesterymarun: Do we get gerrit reviews on stackforge?16:04
marunwe do16:04
marunand we can tie into openstack ci16:04
marun(presuming we have something to test)16:04
banixmarun: we do :)16:04
mesterymarun: Thanks for bringing this up. I think this bears looking into, seems like we should do this.16:05
banix+116:05
*** bdpayne has joined #openstack-meeting-alt16:05
mesterymarun: I'll have SumitNaiksatam talk with you since he setup the other github.16:05
marunmestery: ok, sounds good16:05
mestery#action SumitNaiksatam and marun to discuss moving shared code to stackforge.16:05
mesteryThanks!16:05
*** lblanchard1 has joined #openstack-meeting-alt16:06
mesteryOK next action item for review.16:06
mestery#link https://docs.google.com/document/d/14UyvBkptmrxB9FsWEP8PEGv9kLqTQbsmlRxnqeF9Be8/edit?usp=sharing API Document16:06
*** lblanchard has quit IRC16:06
mesteryThis is basically taken from the overall Group Policy Document16:06
mesteryI think, given this, I'd like to deprecate this one and focus on the Group Policy Document.16:06
mesteryThoughts?16:06
mestery#undo16:07
*** mtaylor is now known as mordred16:07
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x2f42110>16:07
mestery#link https://docs.google.com/a/mestery.com/document/d/1b_ywmSTKYW4PBjhkXREPePRgVmz-Uwv_Bb-i7Jaqsu4/edit API Document16:07
mesterySorry, wrong link16:07
mesteryThat's the correct one.16:07
*** mordred has quit IRC16:07
*** mordred has joined #openstack-meeting-alt16:07
mesterybanix: Thoughts on this, given the overlap?16:07
mesteryI wasn't sure what this separate document was buying us.16:07
banixmestery: yes sure16:07
banixagree16:07
*** saju_m has joined #openstack-meeting-alt16:08
mestery#link https://docs.google.com/document/d/1ZbOFxAoibZbJmDWx1oOrOsDcov6Cuom5aaBIrupCD9E/edit?usp=sharing Group Policy Architecture Document16:08
mesterys3wong: Are you here by chance?16:08
mesteryOK, I'll speak with s3wong offline about this.16:09
banixwe need to review the last doc to make sure it is up to date16:09
mesterybanix: You mean that the separate API doc hasn't added something different?16:09
banixmestery: yes16:09
*** venkatesh has quit IRC16:09
mesterybanix: good call. I'll assign an AI for me, you and s3wong to do that.16:10
banixsounds good16:10
*** VINOD has quit IRC16:10
mestery#action banix s3wong mestery to collapse separate API document back into Group Policy Architecture Document16:10
mesteryThanks banix16:10
mesteryOK, that's all I had for action items on the agenda.16:11
mestery#topic PoC16:11
*** openstack changes topic to "PoC (Meeting topic: networking_policy)"16:11
mesteryOn the topic of the PoC, s3wong sent out an initial API diff, SumitNaiksatam is in process of adding that into a shared github now.16:11
*** Florian_away has joined #openstack-meeting-alt16:11
*** Florian_away is now known as FlorianOtel16:11
mesteryHas anyone else started work on anything else yet?16:12
banixI have also worked on the database model for new group policy tables16:12
alagalahNot yet16:12
alagalahbanix: is that documented anywhere?16:12
mesterybanix: Nice work!16:12
alagalahbanix: Sorry :) Yes that's awesome!16:12
banixI will push up the code as soon as we decide how to do it16:12
*** ijw has joined #openstack-meeting-alt16:13
mesterybanix: Great! Lets sort out stackforge vs. github as well.16:13
mesteryI mean, before the push of your code.16:14
banixmestery: yes, then you guys can have a look and see how it is and we can make changes as necessary16:14
mesterybanix: Cool!16:14
mesteryWe also need to start on the agent side code as well, and eventually implement the new APIs in ML2 and the openvswitch MD.16:15
*** nwidell has joined #openstack-meeting-alt16:16
banixmestery: sounds good16:16
*** chandankumar__ has joined #openstack-meeting-alt16:16
banixwe have people assigned to that part?16:16
marunagents, hmmm.  I'll need to follow up afterwards on that topic.16:16
*** dripton_shovelin is now known as dripton16:17
mesterymarun: Ideally we do this using ODL once that gets into the tree.16:17
* mestery just realized he had moved this meeting to an hour later, and yet most of us showed up at this time ...16:17
mesteryI was wondering where s3wong and SumitNaiksatam were. :)16:17
mesteryI wonder if we should continue or come back in 45 minutes?16:17
banixso that is what Sumit was referring to! a new time!16:18
banix:)16:18
mesteryMan, I am dense this morning.16:18
maruntempest meeting is in 45m :(16:18
mesteryOn this channel? I thought I had checked that!16:18
banixI missed that change of time16:18
marunno, #openstack-meeting.  but it would be a conflict for me16:18
mesterymarun: OK.16:19
mesterymarun: what about 1800 UTC? Is that better?16:19
marunmestery: yes, better16:19
*** chandankumar_ has quit IRC16:19
mesterySo, 1800UTC on Thursday's is booked, unless we get another IRC channel for meetings. :)16:20
mesteryThe FWaaS meeting is at 1800UTC on Wednesday16:20
mesteryDoes Monday/Friday work for people?16:20
mesteryOR should we try 1900 UTC :)16:20
mestery1900 UTC is free on most days for this meeting.16:21
banixmestery: 1900 UTC on Thurs works for me16:21
maruni have no potential conflicts m/w/f16:22
mesterymarun: At 1900 UTC?16:22
maruni can't make it today, but usually that time is fine16:22
mesteryOK, looks like Thursday 1900 UTC is the best time for this meeting going forward then.16:23
mesteryI'll send out an updated meeting invite, and this time BCC banix so he gets a copy :)16:24
mestery#action mestery to move this meeting to 1900 UTC Thursday going forward16:24
banixmestery: thanks :)16:24
* cgoncalves waves and agrees :)16:24
mestery:)16:24
mesteryOK, since s3wong and SumitNaiksatam aren't here, I propose we adjourn this now, and for today, come back in 35 minutes for a quick syncup with those folks and others as well.16:25
*** pballand has joined #openstack-meeting-alt16:25
mesterySound ok to everyone?16:25
alagalahack16:25
*** betsy has joined #openstack-meeting-alt16:25
banixyes16:25
alagalahI won't be here but I'll read the transcript later today16:25
*** vbellur has left #openstack-meeting-alt16:25
mesteryalagalah and marun: Thanks for dropping by to the early version of this one, we'll look forward to seeing you folks next week at the new 1900 UTC slot. :)16:26
marun:)16:26
mesteryOK, we'll see everyone back here in 35 minutes!16:26
mesteryThanks!16:26
mestery#endmeeting16:26
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:26
openstackMeeting ended Thu Feb 13 16:26:21 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:26
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-02-13-16.00.html16:26
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-02-13-16.00.txt16:26
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-02-13-16.00.log.html16:26
*** FlorianOtel is now known as Florian_away16:26
*** Florian_away has left #openstack-meeting-alt16:26
*** demorris has joined #openstack-meeting-alt16:27
*** david-lyle has joined #openstack-meeting-alt16:31
*** IlyaE has quit IRC16:33
*** Duane_ has joined #openstack-meeting-alt16:36
*** alagalah has quit IRC16:37
*** gyee has joined #openstack-meeting-alt16:37
*** chandankumar__ has quit IRC16:38
*** chandan_kumar has joined #openstack-meeting-alt16:41
*** miaykz has quit IRC16:46
*** Duane_ has quit IRC16:47
*** Duane_ has joined #openstack-meeting-alt16:48
*** csaba is now known as csaba|afk16:48
*** Duane_ has quit IRC16:52
*** jtomasek has quit IRC16:54
*** DinaBelova is now known as DinaBelova_16:55
*** thinrichs has joined #openstack-meeting-alt16:55
*** jpich has joined #openstack-meeting-alt16:56
*** nwidell has quit IRC17:00
*** DinaBelova_ is now known as DinaBelova17:00
*** s3wong has joined #openstack-meeting-alt17:00
*** NikitaKonovalov is now known as NikitaKonovalov_17:00
mesteryHi folks :17:00
mestery:)17:00
thinrichsHi all.17:00
banixhi17:00
mestery#startmeeting networking_policy17:00
openstackMeeting started Thu Feb 13 17:00:49 2014 UTC and is due to finish in 60 minutes.  The chair is mestery. 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: networking_policy)"17:00
openstackThe meeting name has been set to 'networking_policy'17:00
s3wongHello, guys!17:00
mesteryOK first order of business: Meeting times :)17:01
SumitNaiksatamhi all!17:01
mesterybanix, myself, marun, alagalah, and a few others forgot this time.17:01
mesterySo we met an hour earlier before we realized that.17:01
mesterySecond is that this slot won't work for marun going forward.17:01
*** gokrokve has quit IRC17:01
mesterySo, long story short, will 1900 UTC Thursday work for everyone going forward?17:01
*** shivharis has joined #openstack-meeting-alt17:01
*** Duane_ has joined #openstack-meeting-alt17:01
s3wongmestery: really? You initiated the time change :-)17:01
*** gokrokve has joined #openstack-meeting-alt17:02
SumitNaiksatammestery: to confirm, that is 11 AM PST?17:02
shivharishi17:02
mesteryI know I know. :)17:02
SumitNaiksatammestery: sorry, timezone challenged :-)17:02
mesteryMy calendar invite for myself still said 1600 UTC :(17:02
* mestery clearly didn't have enough coffee this mornig.17:02
*** prasadv has joined #openstack-meeting-alt17:02
banixyes 11am pst17:02
mesterySo, 1900UTC Thursday going forward starting next weke, is that good for folks?17:02
banix2pm est17:02
SumitNaiksatambanix: thanks17:02
mestery#link http://www.scc-ares-races.org/generalinfo/utcchart.html Timezone conversion page17:03
SumitNaiksatambanix: just wanted to make sure we have the same understanding :-P17:03
banixThis will change when we do daylight saving17:03
s3wongmestery: banix: since you guys already had the meeting, we have nothing to talk about? :-)17:04
mesteryYes, indeed.17:04
banixSumitNaiksatam: I know :)17:04
mesterys3wong: :P17:04
mesterySo we're good on the meeting time change?17:04
mesteryGoing once ... going twice ...17:04
prasadvyes17:04
banix+117:04
mestery#action mestery to change this meeting to be at 1900UTC Thursdays on #openstack-meeting-alt going forward17:04
shivharisoops this meeting is over? my bad.17:05
mesteryshivharis: Nope.17:05
mesteryWe'll have it now today, but going forward starting next week we'll move it.17:05
shivharisrelief17:05
mesteryThere was a conflict for some folks at this time due to the QA meeting.17:05
shivharisk17:05
mesteryOK.17:05
mestery#topic Shared repository for work17:05
*** openstack changes topic to "Shared repository for work (Meeting topic: networking_policy)"17:05
*** mandeep has joined #openstack-meeting-alt17:05
*** hemanthravi has joined #openstack-meeting-alt17:05
mesteryThe next topic is the shared repository17:05
*** gokrokve has quit IRC17:06
mesterySumitNaiksatam has setup a shared github, but there was talk of using stackforge instead.17:06
mesteryUnfourtanetly marun was the one who suggested this, and he can't be here right now (unless I just got his attention and he pops over for a minute).17:06
mandeepCan we use stack forge for a neutron repo?17:06
mesterymandeep: That was what marun was indicating, yes.17:06
marun(hoping, anyway)17:06
SumitNaiksatammestery: my understanding was that stack forge is generally used for a new project or one which is being incubated17:07
mesterySumitNaiksatam: Yes, that was my understanding as well, I think you're right.17:07
mandeepI did look into that yesterday, but I did not see any repo on stack forge for a core project, and I am sure that they all have enough projects that would need colaboration17:07
SumitNaiksatammestery: in this case my anticipation was that this current activity of merging branches would be short-lived17:07
SumitNaiksatammandeep: yeah, i agree that would amount to a fork of neutron17:08
SumitNaiksatamin general, my thinking was that we want to get to gerrit at the earliest17:08
mesterySo given this is likely to be 3-4 patches which we can link together, maybe stackforge is overkill?17:08
mandeepYes, I would think so.17:08
*** songole has joined #openstack-meeting-alt17:08
SumitNaiksatammestery: i think so, and not only that, i would prefer to do this on gerrit17:08
SumitNaiksatammestery: so we can have dependency of patches already in review17:09
SumitNaiksatammestery: we can mark them WIP to being with17:09
*** HenryG has joined #openstack-meeting-alt17:09
mesteryMakes sense.17:09
mandeepSumit: Yes that would be very convenient17:09
SumitNaiksatamthat would put all of this firmly on the roadmap17:09
mesteryAgreed. banix, thoughts on this? s3wong?17:09
SumitNaiksatamand we can also run our own tempests test from our CI on it17:09
SumitNaiksatamwhile we are developing it17:10
marunso we're not far away from simply submitting patches directly to neutron?17:10
mesterymarun: For the APIs, yes, we are close I believe.17:10
SumitNaiksatammarun: my thinking was we can get to that pretty soon17:10
*** Guest50701 has quit IRC17:10
shivharisWIP on github +117:10
banixSo the patches won't get in anytime soon. will they?17:10
marunmestery: i guess I'm not sure why we'd need WIP on github then17:10
s3wongmestery: so business as usual, no stack forge?17:10
hemanthravi+1 github17:10
marunwe could pretty easily submit directly to neutron and mark as WIP17:11
marungerrit maintains persistent git branches, after all17:11
mesterymarun: OK, that makes sense then.17:11
SumitNaiksatammarun: we wanted to merge work from a few people, so more of a convenience thing, rather than having to exchange diffs in emails17:11
mandeepYes, but we need a branch for collaboration, and the repo set up by Sumit would be the right place to do that17:11
mandeep(just repeated what Sumit said ;-)17:12
marunyou can do the same thing with gerrit, though, and have all the tools available.17:12
marunanyway, whatever works for you guys.17:12
s3wongSo what is the conclusion?17:12
mesterySounds like potential short-term github if needed, but moving very fast to WIP upstream patches.17:13
mandeepPersonally I prefer a github repo, so I would recommend to use the repo setup by sumit17:13
banixSo let me understand this. We use the github for now and move to gerrit17:13
mandeepYes17:13
mandeep(that is my underdstanding)17:13
s3wongOK17:14
*** sacharya has joined #openstack-meeting-alt17:14
banixSounds good; Let's do it this way.17:14
mestery#action SumitNaiksatam to update meeting page with temporary shared github address17:15
*** tanisdl has joined #openstack-meeting-alt17:15
mestery#note Use shared github for short-term collaboration, moving quickly to upstream WIP patches.17:15
*** ylobankov1 has joined #openstack-meeting-alt17:15
SumitNaiksatammestery: ok, will sync with you17:15
mesteryThanks SumitNaiksatam!17:15
mestery#topic PoC Code17:16
*** openstack changes topic to "PoC Code (Meeting topic: networking_policy)"17:16
mesterySo, there is movement on the API front between SumitNaiksatam and s3wong.17:16
SumitNaiksatammestery s3wong: working on it17:16
s3wongYes, I will pull a personal branch, check it into that, and do a pull request to the main branch - that is the procedure now, right?17:17
SumitNaiksatams3wong: no pull request required17:17
SumitNaiksatams3wong: lets keep the master to mirror upstream17:17
SumitNaiksatams3wong: we can merge other branches17:18
mandeepwe can send a pull request to a colaboration branch17:18
s3wongSumitNaiksatam: OK17:18
SumitNaiksatammandeep: yeah, thats what i meant17:18
banixmandeep: can you write a couple of lines as to what to do and post it to the wiki so we are on the same page17:18
mandeepAnd that allows us to use github comments to do any discussion17:18
mandeepbanix: will do17:18
banixmandeep: thanks17:19
s3wongbanix: don't know if you looked at my diff so far - one thing to note. You and I had been back and forth on action as Neutron object; so far, since each action type has different structure, I put action as Neutron object for now17:19
mestery#action mandeep to update wiki with collaboration instructions17:19
banixs3wong: yes that's how I am doing it on the model side as well; will look more closely17:20
s3wongbanix: cool17:20
mesteryOK, anything else to talk about regarding PoC this week?17:21
*** atiwari has joined #openstack-meeting-alt17:21
s3wongmestery: well - how are you doing on the agent side? :-)17:21
mesterys3wong: Not good, lets put it that way. :)17:21
mesteryI will have more to update next week as well. :)17:22
mestery#topic OpenDaylight Policy Proposal17:23
*** openstack changes topic to "OpenDaylight Policy Proposal (Meeting topic: networking_policy)"17:23
mesteryI know s3wong and banix and others are aware, but there is an equivalent proposal in OpenDaylight moving forward now.17:23
mestery#link https://wiki.opendaylight.org/view/Project_Proposals:Application_Policy_Plugin OpenDaylight Policy Proposal17:23
s3wongmestery: Oh, we are going to talk about the ODL project here too?17:23
mesteryJust wanted to note it here for people.17:23
*** _nadya_ has joined #openstack-meeting-alt17:23
mesterys3wong: Given how the two tie together, and how the ODL ML2 MechanismDriver is getting close to merging, it makes sense a bit.17:24
mesteryMostly just wanted to bring this up here.17:24
mesteryTo keep people aware.17:24
*** chandan_kumar has quit IRC17:24
mesteryWe'll want to tie this into the ODL MechanismDriver as well once we get to that point and the APIs are implemented on the ODL side.17:24
s3wongmestery: the ODL ML2 mechanisum driver will definitely make it to Icehouse, I suppose?17:24
mesterys3wong: We just need third party testing, which the Linux Foundation assures me will be ready next week. Fingers crossed.17:25
mesteryThe code has seen multiple reviews, so it's looking good.17:25
mesteryFor reference:17:25
mestery#link https://review.openstack.org/#/c/69775/ OpenDaylight ML2 review17:25
mestery#topic Integration with Network Services17:25
*** openstack changes topic to "Integration with Network Services (Meeting topic: networking_policy)"17:26
mesterybanix this is your item correct?17:26
mesteryYou added this one?17:26
banixYes, I see as we get the basic stuff worked out there are a couple of broad directions that we need to look at17:26
prasadvalso network aware scheduling.. What is it?17:27
banixOne being how our framework integrates with network services, advanced services, service chaining work17:27
mesteryprasadv: That was added by debo dutta, but he's not here, so I thought we'd punt that for today.17:27
s3wongbanix: if we feel ambitious, we should add 'redirect' action before the J-Summit17:27
mesterys3wong: +1 to that17:27
banixthe other being integration with other types of policy work such as scheduling related work17:27
banixs3wong: that should be our goal17:28
s3wongbanix: I noticed that as well - a Nova project, right?17:28
banixand as we start looking at that we need to see how we can reuse service if posseble17:28
mesterybanix: makes sense17:28
songolebanix: service reuse - are you talking about multi-tenancy?17:29
banixs3wong: correct; and some work on the Heat side17:29
s3wongAlso, after the basic PoC working, I would need to contact Sean to get the 'qos' action set defined17:29
mesterys3wong: That makes sense as well!17:30
*** Duane__ has joined #openstack-meeting-alt17:30
banixsongole: Not really; just as we try to implement redirect, we need to somehow specify/refer to a middle box like a LB or a FW. Right?17:31
s3wongbanix: nice - would be great to see us (network policy) working with Nova team to have Heat driving the whole infra, eventually17:31
songolebanix: got it17:31
banixs3wong:  yes I think mystery will have more to say on that front17:32
banixmastery that is17:32
banixmestery!17:32
s3wongit is indeed a mystery :-)17:32
songolesumit: could you also setup a heat repo as well? thanks17:32
hemanthraviwe are starting on adding heat support for the apis from s3wong17:33
banixhemanthravi: great. thx.17:33
s3wongI agree, songole and hemanthravi need a collaboration repo for their code as well17:33
*** Duane_ has quit IRC17:33
mesterySumitNaiksatam: Can you add heat repositories?17:34
SumitNaiksatammestery: sure17:34
prasadvshould we start talking about redirect action since we have the first action into PoC17:34
songoleSumitNaiksatam: thanks17:35
mesteryprasadv: I think that's what s3wong was implying.17:35
SumitNaiksatamsongole: sorry, missed your earlier comment17:35
s3wongprasadv: I don't mind, we still have 25 minutes17:35
mandeepIs there a related blueprint in Heat as well?17:36
prasadvwe probably have to define the service Ids for redirect action and the management of the list17:37
*** nacim has quit IRC17:37
s3wongprasadv: currently the 'redirect' list isn't mandated to be ordered, so to implement a chain, we need that17:37
banixSo shall we consider a use case for redirect that we work through and see what we need to do to get there?17:38
prasadvinstead of having a list should it be UUID and the actual list is defined outside?17:38
songolemandeep: there is no BP yet for heat updates.17:38
*** Ranjitha has joined #openstack-meeting-alt17:39
*** NikitaKonovalov_ is now known as NikitaKonovalov17:39
s3wongprasadv: that's one way. If the service chain is itself a Neutron object, we simply set {'redirect': list: {'uuid'}}17:39
s3wongbut if you want tenants to define the chain via policy API, you can also set 'deny', then 'redirect' to a ordered list of UUIDs specifying the desired services17:40
prasadvs3wong:redirect to list, does it mean it gets redirected to all the items in the list?17:40
SumitNaiksatams3wong: i would like to better understand the requirements from the neutron service chain17:40
s3wongprasadv: yes17:41
SumitNaiksatami have been involved in incubating that feature for a while (along with mandeep and mestery) here17:41
*** jtomasek has joined #openstack-meeting-alt17:41
SumitNaiksatamwe were initially planning to get it into I3, but that seems a stretch17:42
s3wongSumitNaiksatam: yes, actually I would like your opinion on this as well - since you have been driving the Neutron service chaining project17:42
mesteryWe should maybe sketch out a user case for the service redirect in the document to start with.17:42
banixSumitNaiksatam: Could you tell us a bit about the status of that work17:42
*** BrianB_ has quit IRC17:42
SumitNaiksatami can carry over feedback from this discussion into that17:42
prasadvs3wong: I assume the UUID in the list is a neutron object right?17:42
s3wongprasadv: Yes17:42
SumitNaiksatams3wong banix: sure17:42
SumitNaiksatammestery: is this the right time to discuss this?17:42
banixmestery: agree17:43
prasadvmestery: I agree17:43
mesteryMaybe we should move this to a use case discussion in the document SumitNaiksatam?17:43
s3wongSumitNaiksatam: if you can do it in 17 minutes :-) !!!17:43
SumitNaiksatammestery: sure17:43
*** Ranjitha has quit IRC17:43
SumitNaiksatams3wong banix mestery: why don't we go offline on this, and have this as an agenda item on the next meeting?17:43
*** demorris has quit IRC17:44
banixLet me start an email on the ML17:44
mesteryMakes sense.17:44
mesteryPerfect17:44
*** jpich has quit IRC17:44
s3wongSumitNaiksatam: Sure17:44
banixyes agree17:44
mestery#topic Open Discussion17:44
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"17:44
mesteryAnything else for this week?17:44
*** Ranjitha has joined #openstack-meeting-alt17:44
*** demorris has joined #openstack-meeting-alt17:44
banixmestery: you wanted to talk about scheduling policies?17:44
mesterybanix: No, that was someone else.17:45
mesteryWe'll do that next week perhaps.17:45
banixok17:45
s3wongmestery: make sure we invite him to the right time next time :-)17:45
banixlet's meet at 1900 UTC again17:45
banixjust kidding :)17:45
mesteryhahahahahahah17:45
*** _nadya_ has quit IRC17:46
mesteryOK, 1900 UTC next week!17:46
mesteryThanks everyone!17:46
mestery#endmeeting17:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:46
s3wongThanks!17:46
openstackMeeting ended Thu Feb 13 17:46:11 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:46
hemanthravithanks17:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-02-13-17.00.html17:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-02-13-17.00.txt17:46
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-02-13-17.00.log.html17:46
songolethanks17:46
*** mandeep has left #openstack-meeting-alt17:46
*** thinrichs has quit IRC17:46
*** prasadv has quit IRC17:47
SumitNaiksatamthanks, bye17:47
*** crobertsrh has joined #openstack-meeting-alt17:48
*** shivharis has quit IRC17:48
*** hemanthravi has quit IRC17:51
*** alazarev has joined #openstack-meeting-alt17:54
*** colinmcnamara has joined #openstack-meeting-alt17:56
*** bdpayne_ has joined #openstack-meeting-alt17:59
*** s3wong has quit IRC17:59
*** bob_nettleton has joined #openstack-meeting-alt18:00
SergeyLukjanovsavanna folks, are you around?18:00
bob_nettletonhere18:00
SergeyLukjanov#startmeeting savanna18:00
openstackMeeting started Thu Feb 13 18:00:54 2014 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: savanna)"18:00
openstackThe meeting name has been set to 'savanna'18:00
*** tmckay has joined #openstack-meeting-alt18:00
SergeyLukjanovlet's wait for several more mins18:01
SergeyLukjanovI see tmckay is here too18:01
SergeyLukjanovjspeidel, jmaron, ping18:01
tmckayI'm here18:01
SergeyLukjanovhm18:02
*** bdpayne has quit IRC18:02
SergeyLukjanovbob_nettleton, should we wait for Jon/John?18:03
*** loquacities has quit IRC18:03
SergeyLukjanovtmckay, and for Chad?18:03
bob_nettletonSergeyLukjanov, I think so.  let me see if I can get a hold of them.18:03
crobertsrhI'm here18:03
SergeyLukjanovcrobertsrh o/18:03
*** loquacities has joined #openstack-meeting-alt18:03
NikitaKonovalovo/18:03
*** ErikB has joined #openstack-meeting-alt18:04
*** stannie has quit IRC18:04
*** sreshetnyak has joined #openstack-meeting-alt18:04
*** jprovazn has quit IRC18:04
SergeyLukjanovErikB o/18:04
*** dmitryme has joined #openstack-meeting-alt18:05
ErikBHello18:05
dmitrymehello18:05
ylobankov1hello18:05
sreshetnyakhi18:05
SergeyLukjanovok, let's start18:05
SergeyLukjanov#topic Agenda18:06
*** openstack changes topic to "Agenda (Meeting topic: savanna)"18:06
SergeyLukjanov#info https://wiki.openstack.org/wiki/Meetings/SavannaAgenda#Agenda_for_February.2C_1318:06
SergeyLukjanov#undo18:06
openstackRemoving item from minutes: <ircmeeting.items.Info object at 0x31f8110>18:06
SergeyLukjanov#link https://wiki.openstack.org/wiki/Meetings/SavannaAgenda#Agenda_for_February.2C_1318:06
SergeyLukjanov#topic Mission Statement re-wording18:06
*** openstack changes topic to "Mission Statement re-wording (Meeting topic: savanna)"18:06
SergeyLukjanovsmall intro18:06
SergeyLukjanovI'm working on adding our official mission statement to OpenStack governance doc18:06
SergeyLukjanovand I received some comments from tc18:07
*** RaymondWong has joined #openstack-meeting-alt18:07
SergeyLukjanovto make it simpler and remove some marketing like stuff18:07
*** ijw has quit IRC18:07
*** ijw has joined #openstack-meeting-alt18:08
SergeyLukjanov#link https://review.openstack.org/#/c/71045/1/reference/programs.yaml18:08
SergeyLukjanovhere you can find some commets18:08
SergeyLukjanovand you can see a ML thread about it18:08
SergeyLukjanovaignatov and alazarev are already +1'd the mission statement re-wording proposed by dhellmann18:09
SergeyLukjanovTo provide a scalable data processing stack and associated management interfaces.18:09
SergeyLukjanov"To provide a scalable data processing stack and associated management interfaces."18:09
SergeyLukjanovinstead of "To provide the OpenStack community with an open, cutting edge, performant and scalable data processing stack and associated management interfaces."18:09
SergeyLukjanovso, we're in OpenStack, so no need to add OpenStack and open18:10
alazarevI really like new wording18:10
SergeyLukjanovand cutting edge, performant looks quite marketing instead of proposing our mission18:10
SergeyLukjanovso, it's lgtm18:10
SergeyLukjanovany thoughts?18:10
*** Barker has quit IRC18:11
tmckay+118:11
dmitrymeI don't have a preference here18:11
ErikB+118:11
SergeyLukjanovanyway, let's vote for it18:11
SergeyLukjanovlet me remember how to do it ;)18:12
*** esker has quit IRC18:12
*** ijw has quit IRC18:12
SergeyLukjanov#startvote Approve mission statement "To provide a scalable data processing stack and associated management interfaces."? Yes, No, Abstain18:12
openstackBegin voting on: Approve mission statement "To provide a scalable data processing stack and associated management interfaces."? Valid vote options are Yes, No, Abstain.18:12
openstackVote using '#vote OPTION'. Only your last vote counts.18:12
SergeyLukjanov#vote Yes18:12
crobertsrh#vote Yes18:12
dmitryme#vote abstain18:12
ErikB#vote Yes18:13
*** esker has joined #openstack-meeting-alt18:13
*** songole has quit IRC18:13
NikitaKonovalov#vote Yes18:13
ylobankov1#vote Yes18:13
SergeyLukjanovtmckay, jmaron, bob_nettleton, sreshetnyak, ping18:13
*** derekh has quit IRC18:13
tmckay#vote Yes18:13
bob_nettleton#vote Yes18:14
alazarev@vote Yes18:14
alazarev#vote Yes18:14
SergeyLukjanov1 min left18:15
*** _nadya_ has joined #openstack-meeting-alt18:15
*** harlowja_away is now known as harlowja_18:15
sreshetnyak#vote Yes18:16
SergeyLukjanovok18:17
SergeyLukjanov#endvote18:17
openstackVoted on "Approve mission statement "To provide a scalable data processing stack and associated management interfaces."?" Results are18:17
openstackYes (9): bob_nettleton, ylobankov1, NikitaKonovalov, crobertsrh, tmckay, ErikB, SergeyLukjanov, alazarev, sreshetnyak18:17
openstackAbstain (1): dmitryme18:17
SergeyLukjanovI think that's enough18:18
*** esker has quit IRC18:18
SergeyLukjanov#info agreed on new mission statement18:19
SergeyLukjanov#topic Project naming collision18:19
*** openstack changes topic to "Project naming collision (Meeting topic: savanna)"18:19
SergeyLukjanovthe much more painful topic18:19
SergeyLukjanovso, we have tons of options in the etherpad18:19
SergeyLukjanovhttps://etherpad.openstack.org/p/savanna-renaming18:20
SergeyLukjanov#link https://etherpad.openstack.org/p/savanna-renaming18:20
SergeyLukjanovnow, we should filter out some bad options and I'd like to setup voting for it18:20
SergeyLukjanovcommon CIVS with N winners18:21
SergeyLukjanovfor 3 days18:21
SergeyLukjanovto have results early Monday18:21
SergeyLukjanovany thoughts on N=?18:21
ErikBN=318:21
dmitrymeAre we going to have second voting?18:22
alazarevhow many rounds will be?18:22
dmitrymeI mean the second voting to pick best from these N options18:22
SergeyLukjanovwe have more than 60 options anyway O_O18:22
SergeyLukjanovdmitryme, yup18:22
SergeyLukjanovI think that we should have some good options to discuss18:23
dmitrymeIf we have two rounds, I would propose N=10 or 1518:23
SergeyLukjanovdmitryme, I'm thinking about 10% of proposed options18:24
SergeyLukjanovthe voting will require folks to sort options18:24
SergeyLukjanovbut I'm afraid that sort 60 options could be quite difficult18:25
dmitryme6? As far as I understand during the second voting we will have to pick 3-5 best and send them to the legal guys hoping that some of them could be used as a name18:25
alazarevso, first round is for 60 -> N, second is for N -> 1, right?18:25
NikitaKonovalovlet's sort them alphabetically :)18:25
SergeyLukjanovalazarev, dmitryme, I think that we send about 5-6 options to check18:26
SergeyLukjanovso, it could be done after the first pass if we see good results18:26
SergeyLukjanovIMO sorting 60 options good produce very random results ;)18:26
dmitrymeregarding sorting, imho it is not that difficult to sort 60 options. Though it will take some time, yes :-)18:26
tmckayI would be fine with designating representatives to cull the list initially18:28
SergeyLukjanovtmckay, hm, not sure that I understand you correctly18:28
alazarev3 rounds could make it more seamless, something like 60->15, 15->3, 3->118:29
tmckay2 or 3 folks to unanimously toss options in the garbage18:29
tmckay"no, no, no, no, no" if all agree, gets the list from 60 to something much smaller very fast18:29
tmckayLike many of my fine elephant references --> "No!" :)18:30
tmckayMy son last night suggested "Mudbath"18:30
tmckaybut I'm also okay with starting with the entire 6018:30
SergeyLukjanovtmckay, I'm mostly agree with you18:31
*** ijw has joined #openstack-meeting-alt18:31
SergeyLukjanovwe have 30 mins left and many folks here18:31
SergeyLukjanovso, we could wipe out some of options18:31
SergeyLukjanovfor example, I'd like to wipe out elephants directly related names18:32
*** SumitNaiksatam has quit IRC18:32
dmitrymeSergey: could we list them there?18:32
dmitrymejust to be sure18:32
SergeyLukjanovfolks, feel free to propose option removal18:33
SergeyLukjanovwhile I'm collecting the list of elephants ;)18:33
*** ijw_ has joined #openstack-meeting-alt18:34
SergeyLukjanovpooram, dubare, pahan, ElephantHouse, Stable, StableMaster, Slonic/Slonik, Oliphaunt, Babar, Elmer, Batyr, Hathi, Dumbo, Kamama, Barnum18:36
SergeyLukjanovheh, looks like I've collected all of them18:36
dmitrymeOliphaunt - I really like it :-)18:36
dmitrymehave no objections to remove other names18:36
*** ijw has quit IRC18:37
dmitrymeany one else supporting Oliphaunt or other names?18:37
dmitrymein no, lets remove them18:37
SergeyLukjanovmm18:38
SergeyLukjanovany thoughts folks?18:38
alazarev+1 on removing elephants18:38
ylobankov1I don't like all18:38
SergeyLukjanovlet's wait for several more mins18:39
SergeyLukjanovelephant topic is really not very good if we'd like to be not only Hadoop guys18:39
tmckaygood point.  But it's fun :)18:40
dmitrymewhile waiting, I propose removing Lift and Crane. These are mine but so far nobody supported them. So it make sense to remove them from the start18:40
SergeyLukjanovok18:41
bob_nettleton"Lift" is also the name of a popular Scala Web framework as well.18:41
SergeyLukjanovyup and I don't really like it ;)18:41
SergeyLukjanovI mean scala framework18:42
*** yogesh has joined #openstack-meeting-alt18:42
SergeyLukjanov#info agreed to remove all elephants related names: pooram, dubare, pahan, ElephantHouse, Stable, StableMaster, Slonic/Slonik, Oliphaunt, Babar, Elmer, Batyr, Hathi, Dumbo, Kamama, Barnum from naming options18:42
SergeyLukjanovany other names to remove?18:42
jmaronsorry I'm late - had to shovel out of the "heart attack" snow that fell today18:42
SergeyLukjanovjmaron, hey18:42
SergeyLukjanovjmaron, we'd like to filter out some options from https://etherpad.openstack.org/p/savanna-renaming18:43
SergeyLukjanovbefore voting for top N18:43
SergeyLukjanovjmaron, so, you could propose any names or group of them to be wiped so far18:43
jmaronk18:43
*** pballand has quit IRC18:43
*** akuznetsov has quit IRC18:44
*** pballand has joined #openstack-meeting-alt18:44
SergeyLukjanovI think the following could be wiped out too - TroopMaster, TroopCommander, HerdMaster, HerdCommander, ElephantHouse18:44
alazarevwhat about savanna modifications? Probably they need to be removed too, savana, savannah, zavana18:44
*** cadenzajon has joined #openstack-meeting-alt18:44
dmitrymeagree to remove both lists18:45
SergeyLukjanovalazarev, savannah is a gnu project, savana is misspelled18:45
SergeyLukjanovso, removing them anyway :(18:45
SergeyLukjanovzavana sounds like we're trying to save savanna18:45
*** ywu has quit IRC18:46
jmaronare we going with an "elephant" theme?  saw that somewhere on the page18:46
SergeyLukjanovjmaron, we've just agreed to remove any elephant-related options18:47
jmarondoh!  got it18:47
jmaron*puts away Hadrian idea*18:47
*** IlyaE has joined #openstack-meeting-alt18:47
SergeyLukjanovadditionally, there are some potential trademark issues, but I'm not a lawyer to determine which are important and which are not18:48
SergeyLukjanovbut something like Compas could be removed anyway18:48
SergeyLukjanov(used by Huawei for their deployment framework, presented in the Havana summit)18:48
SergeyLukjanovany objections about removing "TroopMaster, TroopCommander, HerdMaster, HerdCommander, ElephantHouse"?18:49
jmaron+118:49
tmckay+118:49
SergeyLukjanovand I'd like to remove Safari from the list, don't want to fight with Apple ;)18:49
dmitryme+1 on removing safari18:50
alazarev+118:50
ylobankov1+118:50
SergeyLukjanovadditionally, it'll be great to keep name length <= savanna18:50
SergeyLukjanovany other proposals for removing options?18:51
*** rossella_s has quit IRC18:51
SergeyLukjanovtmckay, thx for the idea18:51
alazarevwhy? the only reason I heart is pep fight18:51
alazarevpep818:51
jmaronhate to add one, but just had a thought:  anyone like "proscenium"?  the stage area in front of the scaenae frons was known as the "proscenium", meaning "in front of the scenery". A proscenium arch creates a "window" around the scenery and performers18:52
*** marun has quit IRC18:52
SergeyLukjanovalazarev, pep8 fight and it's easier to write short names, it's not a requirement, just good factor18:52
*** rsblendido has quit IRC18:52
*** eankutse has quit IRC18:52
tmckayiCluster18:52
SergeyLukjanovjmaron, I'm afraid that my english is to bad to pronounce it18:52
jmaronfair enough ;)18:53
tmckaybecause everything with an "i" is perfect18:53
dmitrymejmaron: no, sorry, do not like it18:53
SergeyLukjanovtmckay, iData iProcessing18:53
*** colinmcnamara has quit IRC18:53
tmckaynow you're talking ;-)18:53
*** NehaV1 has quit IRC18:53
SergeyLukjanov:)18:55
SergeyLukjanov#info agreed to remove "TroopMaster, TroopCommander, HerdMaster, HerdCommander, ElephantHouse"18:56
SergeyLukjanovIIRC, there are no meetings after us, so we can have some additional time18:56
*** michael-yu has joined #openstack-meeting-alt18:56
SergeyLukjanovany more options removing proposals?18:56
SergeyLukjanovSpectrum18:57
SergeyLukjanovhttp://en.wikipedia.org/wiki/Spectrum - 85809044, Software as a Service (SaaS), namely, cloud-based enterprise software for transactional and non-transactional data, file management, workflow management, and data search capabilities; Software as a Service (SaaS), namely, cloud-based computer software for use in product development, manufacturing, and supply chain processes18:57
SergeyLukjanovshould we remove it?18:57
dmitrymeI don't like Waza, Hananama, Kamama18:57
dmitrymeSpectrum sounds not bad imho18:58
SergeyLukjanovdmitryme, me too, I don't know Mandarin and Cherokee18:58
SergeyLukjanovany objections for removing Waza, Hananama, Kamama?18:58
jmaronif it already has a wiki entry, it's probably a problem18:58
tmckayno objectoins18:59
jmaron+1 to removing those18:59
SergeyLukjanovdmitryme, it's sounds good, but looks like an overlap18:59
dmitrymeSergeyLukjanov: doh, ok18:59
SergeyLukjanovSpectrum tags: aaS, cloud, data search18:59
*** NehaV has joined #openstack-meeting-alt19:00
SergeyLukjanovso, I think it'll be safer to remove it19:00
SergeyLukjanov#info agreed to remove Waza, Hananama, Kamama19:00
SergeyLukjanovok, let's end on it with options removal19:01
SergeyLukjanovwe should have about 30 options19:01
SergeyLukjanovand let's sort them to have 10 options left to discuss them19:01
SergeyLukjanovI'll setup voting latertoday19:01
*** ajo has joined #openstack-meeting-alt19:01
*** IlyaE has quit IRC19:02
SergeyLukjanovlet's have a super short news section19:02
SergeyLukjanov#topc News / updates19:02
SergeyLukjanovylobankov1, tmckay, bob_nettleton, alazarev, dmitryme, jmaron, ping19:02
SergeyLukjanovsreshetnyak19:02
*** _nadya_ has quit IRC19:02
SergeyLukjanovI'm working on renewal of our config sample stuff19:02
dmitrymeI'am further working on Agent remote, today started HDP cluster with it19:03
SergeyLukjanovand going to write some new tempest tests19:03
jmaronwaiting for folks to review HDP 2 commit19:03
bob_nettletonYesterday, I submitted my initial patch for the HDP diskimage-builder images to "savanna-image-elements".  I'm working through the various review comments, and hope to upload an updated patch later today.19:03
ylobankov1I was working on adding tests for Cinder19:03
SergeyLukjanovjmaron, trying to do it, it's big enough, so, will require some more time19:03
alazarevI'm adding IDH 3.0.2 to IDH plugin, should not be too hard19:03
*** michael-yu has quit IRC19:03
jmaronfair enough.  thank god I held off on refactoring ;)19:03
tmckayEDP streaming mapreduce and java actions are in, job types fixed up, old Jar type completely gone.  I haven't started any new EDP actions yet.19:03
dmitrymemore importantly, I've found that we incorrectly used eventlet.monkey_patch - it should be called as early in application as possible. Now fixing it19:03
tmckayStarted looking at testing around python-savannaclient19:04
ylobankov1In addition, I am going to write  a few tests for tempest19:04
jmaronhave a commit almost ready for bug 1271349.  needed to add some savanna.conf settings so I look forward to a spirited review ;)19:04
SergeyLukjanovjmaron, a big thank you for separating refactoring to the next patch :)19:04
SergeyLukjanovhow're planning to attend summit in May?19:05
jmaronwill explain need for settings in commit message (in addition to documentation added as part of commit)19:05
jmaronwill go if management approves19:06
crobertsrhMostly just bug work on savanna dashboard.  Streaming MapReduce should be ready to go.  Also, I will be out next week (gone curling).19:06
tmckayI should be at summit in Atlanta in May19:06
*** amuller has joined #openstack-meeting-alt19:06
SergeyLukjanovbtw, I'll be there too19:06
SergeyLukjanovthanks for the updates19:07
SergeyLukjanovlet's end the meeting and have open discussions in #savanna channel19:07
SergeyLukjanovthank you all19:07
SergeyLukjanov#endmeeting19:07
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:07
openstackMeeting ended Thu Feb 13 19:07:50 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:07
openstackMinutes:        http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-02-13-18.00.html19:07
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-02-13-18.00.txt19:07
openstackLog:            http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-02-13-18.00.log.html19:07
*** bob_nettleton has left #openstack-meeting-alt19:08
*** NikitaKonovalov is now known as NikitaKonovalov_19:09
*** tmckay has left #openstack-meeting-alt19:09
*** Duane_ has joined #openstack-meeting-alt19:10
*** NikitaKonovalov_ is now known as NikitaKonovalov19:11
*** flwang has quit IRC19:14
*** Duane__ has quit IRC19:14
*** asomya has joined #openstack-meeting-alt19:14
*** sreshetnyak has quit IRC19:15
*** colinmcnamara has joined #openstack-meeting-alt19:16
*** Duane__ has joined #openstack-meeting-alt19:18
*** NikitaKonovalov is now known as NikitaKonovalov_19:18
*** crobertsrh has left #openstack-meeting-alt19:19
*** devlaps has joined #openstack-meeting-alt19:20
*** sarob has joined #openstack-meeting-alt19:22
*** Duane_ has quit IRC19:22
*** asomya has left #openstack-meeting-alt19:26
*** sarob has quit IRC19:29
*** flwang has joined #openstack-meeting-alt19:30
*** demorris_ has joined #openstack-meeting-alt19:31
*** IlyaE has joined #openstack-meeting-alt19:32
*** SushilKM has joined #openstack-meeting-alt19:32
*** eankutse has joined #openstack-meeting-alt19:33
*** demorris has quit IRC19:33
*** demorris_ is now known as demorris19:33
*** alazarev has quit IRC19:34
*** amytron has joined #openstack-meeting-alt19:39
*** NikitaKonovalov_ is now known as NikitaKonovalov19:42
*** gyee has quit IRC19:43
*** amuller has quit IRC19:44
*** NikitaKonovalov is now known as NikitaKonovalov_19:47
*** arnaud___ has joined #openstack-meeting-alt19:48
*** arnaud__ has joined #openstack-meeting-alt19:48
*** dmitryme has quit IRC19:49
*** NikitaKonovalov_ is now known as NikitaKonovalov19:49
*** alazarev has joined #openstack-meeting-alt19:50
*** rohit404 has quit IRC19:52
*** rohit404 has joined #openstack-meeting-alt19:54
*** ylobankov1 has left #openstack-meeting-alt19:55
*** colinmcnamara has quit IRC19:58
*** NikitaKonovalov is now known as NikitaKonovalov_19:59
*** NikitaKonovalov_ is now known as NikitaKonovalov20:00
*** DinaBelova is now known as DinaBelova_20:05
*** eankutse1 has joined #openstack-meeting-alt20:06
*** julienvey_ has joined #openstack-meeting-alt20:07
*** eankutse has quit IRC20:07
*** julienvey_ has quit IRC20:07
*** demorris_ has joined #openstack-meeting-alt20:07
*** NehaV1 has joined #openstack-meeting-alt20:07
*** boris-42_ has quit IRC20:07
*** DinaBelova_ is now known as DinaBelova20:08
*** _nadya_ has joined #openstack-meeting-alt20:08
*** demorris has quit IRC20:08
*** demorris_ is now known as demorris20:08
*** NehaV has quit IRC20:09
*** ijw_ has quit IRC20:14
*** _nadya_ has quit IRC20:14
*** saju_m has quit IRC20:19
*** ftcjeff has quit IRC20:23
*** rohit404 has quit IRC20:23
*** ftcjeff has joined #openstack-meeting-alt20:23
*** amuller has joined #openstack-meeting-alt20:23
*** jrist is now known as jrist-afk20:24
*** jrist-afk is now known as jrist20:24
*** SushilKM has left #openstack-meeting-alt20:24
*** eanxgeek|log is now known as eanxgeek20:25
*** xyang2 has quit IRC20:25
*** cadenzajon has quit IRC20:26
*** rohit404 has joined #openstack-meeting-alt20:27
*** Sukhdev has joined #openstack-meeting-alt20:27
*** boris-42_ has joined #openstack-meeting-alt20:34
*** rohit404 has quit IRC20:34
*** amuller has quit IRC20:43
*** eanxgeek is now known as eanxgeek|log20:45
*** IlyaE has quit IRC20:46
*** IlyaE has joined #openstack-meeting-alt20:48
*** SumitNaiksatam has joined #openstack-meeting-alt20:49
*** Sukhdev has quit IRC20:50
*** gokrokve has joined #openstack-meeting-alt20:51
*** NikitaKonovalov is now known as NikitaKonovalov_20:51
*** ijw has joined #openstack-meeting-alt20:52
*** NikitaKonovalov_ is now known as NikitaKonovalov20:54
*** SumitNaiksatam has quit IRC20:54
*** zehicle_at_dell has joined #openstack-meeting-alt20:58
*** Barker has joined #openstack-meeting-alt21:02
*** denis_makogon_ has joined #openstack-meeting-alt21:05
*** denis_makogon has quit IRC21:09
*** denis_makogon_ is now known as denis_makogon21:10
*** dmakogon_ has joined #openstack-meeting-alt21:10
*** DinaBelova is now known as DinaBelova_21:10
*** NikitaKonovalov is now known as NikitaKonovalov_21:11
*** slagle_ is now known as slagle21:17
*** derekh has joined #openstack-meeting-alt21:23
*** marun has joined #openstack-meeting-alt21:24
*** cadenzajon has joined #openstack-meeting-alt21:26
*** jtomasek has quit IRC21:27
*** amcrn has quit IRC21:29
*** cody-somerville has quit IRC21:31
*** cody-somerville has joined #openstack-meeting-alt21:33
*** cody-somerville has quit IRC21:33
*** cody-somerville has joined #openstack-meeting-alt21:33
*** catherineD has joined #openstack-meeting-alt21:35
*** colinmcnamara has joined #openstack-meeting-alt21:35
*** jecarey has quit IRC21:36
*** derekh is now known as derekh_afk21:39
*** bdpayne has joined #openstack-meeting-alt21:39
*** gokrokve has quit IRC21:39
*** gokrokve has joined #openstack-meeting-alt21:40
*** kfarr has joined #openstack-meeting-alt21:41
*** bdpayne_ has quit IRC21:43
*** gokrokve has quit IRC21:44
*** kfarr has quit IRC21:47
*** rocky2 has joined #openstack-meeting-alt21:49
*** alazarev has quit IRC21:50
*** SumitNaiksatam has joined #openstack-meeting-alt21:51
*** alazarev has joined #openstack-meeting-alt21:51
*** bdpayne has quit IRC21:55
*** bdpayne has joined #openstack-meeting-alt21:59
*** rocky2 is now known as rockyg22:00
*** gokrokve has joined #openstack-meeting-alt22:01
*** IlyaE has quit IRC22:01
*** IlyaE has joined #openstack-meeting-alt22:02
zehicle_at_dello/22:05
zehicle_at_dellsorry, running late22:05
*** jdob has quit IRC22:05
*** arborism has joined #openstack-meeting-alt22:05
*** jmaron has left #openstack-meeting-alt22:05
catherineDHere22:06
*** teDC has joined #openstack-meeting-alt22:08
*** arborism is now known as amcrn22:09
*** jecarey has joined #openstack-meeting-alt22:10
*** pdmars has quit IRC22:13
zehicle_at_dellsorry all, still not really on.  can someone else start and moderate?22:13
rockygOops.  I started int the wrong meeting.22:15
rockygstartmeeting RefStack22:15
rockygstartmeeting RefStack22:16
rockyg#startmeeting RefStack22:16
openstackMeeting started Thu Feb 13 22:16:57 2014 UTC and is due to finish in 60 minutes.  The chair is rockyg. Information about MeetBot at http://wiki.debian.org/MeetBot.22:16
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:16
*** openstack changes topic to " (Meeting topic: RefStack)"22:17
openstackThe meeting name has been set to 'refstack'22:17
rockygOK.  We're Started.22:17
catherineDCatherineD is here22:17
rockyg#link  http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-02-13-22.07.html22:18
rockygRoll call again to get it in the minutes:  catherineD?22:19
catherineDHere22:19
RaymondWongRaymondWong22:19
rockygAnyone Else?22:19
zehicle_at_dello/22:19
teDC:)22:19
rockygExcellent.  Let's start with Status.  Tcup?22:19
rockyg#topic Tcup22:20
*** openstack changes topic to "Tcup (Meeting topic: RefStack)"22:20
*** japplewhite has quit IRC22:20
*** japplewhite has joined #openstack-meeting-alt22:20
rockygCatherine, Raymond, Alex_H, any status on Tcup, tempest, etc?22:20
catherineDt-cup (Docker) working last step is to call API and script to ship data from container to Refstack22:21
catherineDNow configure with a number of  testcases that only take 33 sec to finish for debug22:21
rockygCool.  so this is the connect with Davidlenwell s stuff22:21
catherineDyes22:21
davidlenwellHi everyone22:22
rockygHey, davidlenwell, did you catch the last from catherineD?22:22
davidlenwellcatherineD and I synced earlier today .. so we should be on teh same page22:23
rockygWhere does the code live?22:23
rockygAnd can anyone build it?22:23
zehicle_at_dellAlex has the code, but he needs direction on where to put it22:24
davidlenwellI instructed him to make a git hub repo weeks ago22:24
zehicle_at_dellhe may need more help, where do you want it22:24
rockygAnd that was an action item from last week:  Will it go to stackforge or directly into openstack?22:24
davidlenwellneither for now22:24
zehicle_at_dellI can work w/ him 1x122:24
*** gokrokve has quit IRC22:25
davidlenwellI'd like it if it was a stand alone repository called docker-tempest or something to that effect22:25
*** gokrokve has joined #openstack-meeting-alt22:25
zehicle_at_dellwe could do that22:25
davidlenwellcatherineD and I talked earlier about keeping scripts in the refstack repository for now22:25
zehicle_at_dellwhat about refstack-tcup?22:25
davidlenwellthere is a scripts directory I believe .. it could just be put there22:26
*** sballe has quit IRC22:26
zehicle_at_delldavidlenwell, I think I'd rahter keep it in the refstack for now22:26
davidlenwellI like that22:26
rockygOK.  I really think that we should get it into stackforge.  A colleague I plan to introduce next week can help tie it into the CI.  We can do no voting until we call it.  Until then, one of the existing refstack repositories.  I agree with refstack.22:26
zehicle_at_dellso, it would be controlled by the gates22:26
*** sballe has joined #openstack-meeting-alt22:26
zehicle_at_dellrockyg, +122:26
davidlenwellso what he should do is fork refstack from me22:26
rockygI type too much.22:26
zehicle_at_dellI will show him how to do that22:26
davidlenwellrockyg: we will ..22:26
davidlenwellzehicle_at_dell: then have him add the script .. commit and send a pull request22:27
catherineDRigjt now we are working on building config file from default file .. once that is done any one can run t-cup22:27
zehicle_at_dell:) time he learned how to do that anyway22:27
*** gokrokve_ has joined #openstack-meeting-alt22:27
rockygGreat.22:27
davidlenwellrockyg:  I absolutely want this in stackforge .. but we are a little too dissorgiized just yet22:27
catherineDDavid should we show the doc that we discuss this morning ..22:27
davidlenwellI am hoping by the begining of march we can do that22:27
davidlenwellcatherineD: perhaps .22:28
catherineDRaymond could you ping the link ...22:28
davidlenwellcatherineD and I had a phone conversation earlier and identified the area they can contribute to22:28
catherineDthat way we can ping point the script that need to be written ..22:28
rockygJerry, the guy I mentioned, just got one of our projects working in Stackforge.  He shephearded along from just a repository to running unit tests now.  voting but not blocking.22:28
davidlenwellwe don't have tests yet22:29
RaymondWonghttps://drive.google.com/file/d/0Bw1YqO1DEg6SbUxwQ1NraFpFaXc/edit?usp=sharing22:29
davidlenwelland we are about to rewrite a lot of things .. which I guess is fine to do in stackforge22:29
rockygSo, no need for the test stuff, but still CI.22:29
*** marun has quit IRC22:29
*** gokrokve has quit IRC22:29
rockygJust skimmed the doc.  I'll review it this week and maybe comment.  Looks good, at the high level, though22:30
rockygHow about we get the current code all into repositories and the structure we want and when CatherineD, RaymondWong and davidlenwell say it's good enough, we do the transfer?22:31
davidlenwellrockyg: +122:32
rockyg#ActionItem Tcup and API devs provide repository location and date to transfer to Stackforge.22:32
rockygWe'll need to know how many repositories and names to go with them for stackforge.22:33
davidlenwellif we keep it all in the same repo that gets easier22:33
rockyg+122:33
davidlenwellwe can always split things off later on22:33
rockygReady for next topic?  API and DB okay?22:33
*** Alex_H has joined #openstack-meeting-alt22:33
davidlenwellsure22:34
*** Alex_H is now known as alex_d-qoi22:34
rockyg#topic API and DB22:34
*** openstack changes topic to "API and DB (Meeting topic: RefStack)"22:34
rockygI kinda hope someone is typing status or something in;-)22:35
*** jmontemayor has quit IRC22:35
davidlenwellSo the api and cb are in the same state as last week ..22:36
davidlenwellI was told I could stop working on this spike I've been on .. then the next day our ceo said no dice .. get back on it .. honestly its stressing me out a bit because refstack is my baby22:36
*** lblanchard1 has quit IRC22:36
rockygdavidlenwell:  OK.  It looks like a review of the API calls in the google doc posted above would be good if you haven't already.  That gives us some;-)22:37
davidlenwellyeah .. we talked about that one the phone today with catherineD and RaymondWong... some of those aren't needed .. and we've planned some facetime next week while I am in town.. so i imagine we'll nail them down22:38
rockygI think as long as you can keep providing some mentoring to the rest, we're doing fine.22:38
davidlenwellyeah .. progress is happening22:39
davidlenwellwhich makes me happy22:39
*** Duane__ has quit IRC22:39
rockygReady for next topic?  Documentation ok?22:39
davidlenwellsure22:39
rockyg#topic Documentation22:39
*** openstack changes topic to "Documentation (Meeting topic: RefStack)"22:39
zehicle_at_delllet's add a topic for meetings22:39
catherineDWe discussed with David.  In the Google doc we will work on the Test and Results processsing but need the dependency section ...22:39
rockygGreat.  I'm itching to glue all these bits of information together.22:40
rockygIf it's OK by everybody, I'll start a RefStack page on the OpenStack Wiki and start some wordsmithing and capturing all the links.22:41
davidlenwellI am all for writing as much documentation abotu this stuff as possible .. and we can go in depth but what I feel like is missing is the intro to refstack higher level document22:41
davidlenwellrockyg: please do22:41
*** NehaV1 has left #openstack-meeting-alt22:41
zehicle_at_dellI created a stub for that last meeting22:41
rockygAgreed. Cool.  Not the one under governance?22:41
zehicle_at_dell#link https://wiki.openstack.org/wiki/Governance/DefCoreCommittee/RefStack22:41
davidlenwellI saw the governance one .. not  one for high level engineering .. or intro to22:42
rockygOK.  I think Governance is the even higher level.  Mission, etc.  I'll link more technical homepage to that one so once this one is found, you can follow to techy stuff if you want.22:42
zehicle_at_delllet's start w/ something and we can divide as we go22:43
rockygI'll also put the skeleton into the governance one to match what is expected.22:43
davidlenwellsounds good22:43
zehicle_at_dellgovernance will be tied to DefCore, so that should be interested22:43
zehicle_at_dellinteresting22:43
*** eankutse1 has quit IRC22:43
*** eankutse has joined #openstack-meeting-alt22:43
rockygyeah, been following that discussion;-)22:43
rockygOK, ready for meeting topic?22:44
davidlenwellsure22:44
rockyg#topic Meetings22:44
*** openstack changes topic to "Meetings (Meeting topic: RefStack)"22:44
davidlenwellare we talking about meetings like this one .. or some face time in the bay area?22:44
catherineDBTW, since Raymond will be working on Tempest Result processing ... Has DefCore had any mapping among capability and testcases?22:44
zehicle_at_dellyes22:45
catherineDWe need a modlel to start coding22:45
zehicle_at_dell#link https://docs.google.com/spreadsheet/ccc?key=0Av62KoL8f9kAdEJTWnFWejJySnFXZmxWdnowTDhUSVE&usp=drive_web#gid=022:45
zehicle_at_dellwe have the capabilities map per test22:45
rockygmapping:  there are a couple of PTLs that will be starting on that real soon now22:46
zehicle_at_dellworking on picking the must-pass (that's a lot of work)22:46
zehicle_at_dellwould be GREAT to have help22:46
rockygYou betcha.  How about we have a meeting and pick out some obvious need to haves and start building strawman model?22:47
*** eankutse has quit IRC22:47
zehicle_at_dellrockyg, yes!  I will set one up.  We're overdue to a criteria meeting22:48
zehicle_at_dellwill likely be 2 hours next week.22:48
catherineDwhat is column I in the spreadsheet22:48
zehicle_at_dellyou're welcome to review in that spread sheet22:48
*** amytron has quit IRC22:48
zehicle_at_dell# of tests in the capability (I think)22:49
zehicle_at_dellI did J->W22:49
rockygI'm not seeing *any* of those columns ;-(22:49
rockyg:-(22:50
*** betsy has quit IRC22:50
zehicle_at_dellsee? ScoreStableCompleteDiscoverableIaaSToolsClientsFoundationFutureDoc'dLegacyClusterBasePublic22:50
zehicle_at_dellrow 2?22:50
*** rcurran has joined #openstack-meeting-alt22:50
*** colinmcnamara has quit IRC22:51
rockygDoh!  The grey tabs at the bottom.22:51
catherineDSo this original spreadsheet was from me.  Column G through W was added.  We just need to understand what it means so that we can process the test results.  We will take a look and send out question in email22:52
*** rcurran has quit IRC22:52
zehicle_at_dellyy, I added them22:52
zehicle_at_dellsorry, troytoman-away added G-I22:53
catherineDperfect we need this to start coding once we understand it ...22:53
*** colinmcnamara has joined #openstack-meeting-alt22:53
rockyg#ActionItem  Criteria meeting to follow weekly meeting on 2/2022:53
*** amrith has quit IRC22:53
*** beagles has quit IRC22:54
rockygWe're meeting at Piston on 2/19 (Still on davidlenwell?) and can also do some prep work.22:54
*** amrith has joined #openstack-meeting-alt22:54
zehicle_at_dellgreat! can we have a dial in?22:54
davidlenwelllet me email the group about that later today .. I need to make sure I have the conf room that day22:54
davidlenwellof course22:54
*** Alex_H has joined #openstack-meeting-alt22:55
davidlenwellbut I am pretty sure we can make it work .. refstack is very important to piston22:55
rockygIf you don't we could do it down in Santa Clara.  I can get a room.22:55
davidlenwellI'm sure we'll be fine22:55
davidlenwellI just confirmed with the schedule .. should be fine22:55
zehicle_at_dellwe also have the 3/3 meeting22:56
catherineDGreat, I think that will be productive ..22:56
davidlenwellI'll email an invite22:56
rockygBetter food up where you are.22:56
zehicle_at_delldavidlenwell, is Piston hosting that one too?22:56
*** alex_d-qoi has quit IRC22:56
davidlenwellzehicle_at_dell: not sure on that ..22:56
davidlenwellI haven't even booked my travel for that one yet22:56
rockygLet us know.  We can scrounge rooms down the peninsula way.22:57
zehicle_at_dellI'm planning to be there22:57
davidlenwellI'll plan my travel next week while I am up in the office22:57
davidlenwellwe'd be happy to host .. but it would depend on the dead count and scheduling22:58
rockygGreat!  Micky Hart gonna join us?22:58
zehicle_at_dellzombies count in that?22:58
davidlenwellhead count22:58
davidlenwellI always count zombies22:58
catherineD:-)22:58
rockygAnd members of the band;-)22:59
*** esker has joined #openstack-meeting-alt22:59
zehicle_at_dellI'll check w/ Josh22:59
zehicle_at_dellwe're planning a more general DefCore meeting at the same time22:59
davidlenwelljosh and I also are participating in an ironic sprint thing that is supposed to be that week also22:59
catherineDwe are at the Top of the hour22:59
rockygOK.  Anything else for meetings?  I think I can capture what we've got here into more cogent notes.23:00
davidlenwellI think we've covered everything23:00
rockygDang!  I wanted to talk about all these other efforts that are also planning to use Tempest (Rally, etc) and whether there might be synergy.23:00
zehicle_at_dellI'm ok23:00
*** SumitNaiksatam has quit IRC23:00
zehicle_at_dellthanks all, sorry about the late start23:00
catherineDthx everyone!23:00
rockygI'll put it on the agenda for next week.23:00
davidlenwellsounds good23:00
rockygAnything else?23:01
rockyg#endmeeting23:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:01
openstackMeeting ended Thu Feb 13 23:01:15 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-02-13-22.16.html23:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-02-13-22.16.txt23:01
openstackLog:            http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-02-13-22.16.log.html23:01
*** Alex_H has left #openstack-meeting-alt23:02
*** amcrn_ has joined #openstack-meeting-alt23:03
*** pballand has quit IRC23:03
*** SumitNaiksatam has joined #openstack-meeting-alt23:04
*** amcrn has quit IRC23:05
*** hdd_ has quit IRC23:07
*** rockyg has quit IRC23:08
*** sarob has joined #openstack-meeting-alt23:09
*** _nadya_ has joined #openstack-meeting-alt23:15
*** _nadya_ has quit IRC23:19
*** zehicle_at_dell has quit IRC23:19
*** sacharya has quit IRC23:22
*** sarob has quit IRC23:31
*** bdpayne_ has joined #openstack-meeting-alt23:32
*** sarob has joined #openstack-meeting-alt23:32
*** yogesh has quit IRC23:34
*** bdpayne has quit IRC23:35
*** gokrokve_ has quit IRC23:39
*** gokrokve has joined #openstack-meeting-alt23:39
*** mozawa has quit IRC23:41
*** amrith has quit IRC23:42
*** gokrokve has quit IRC23:44
*** amrith has joined #openstack-meeting-alt23:44
*** ftcjeff has quit IRC23:45
*** dhellmann is now known as dhellmann_23:45
*** Leonr has quit IRC23:45
*** xuhanp has joined #openstack-meeting-alt23:47
*** SumitNaiksatam has quit IRC23:48
*** demorris has quit IRC23:51
*** denis_makogon has quit IRC23:52
*** gokrokve has joined #openstack-meeting-alt23:54
*** derekh_afk is now known as derekh23:56
*** sarob_ has joined #openstack-meeting-alt23:56
*** SumitNaiksatam has joined #openstack-meeting-alt23:57
*** kevinconway has quit IRC23:57
*** arnaud__1 has joined #openstack-meeting-alt23:59
*** amrith has quit IRC23:59

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