Thursday, 2014-08-21

*** cyli has quit IRC00:02
*** cyli has joined #openstack-meeting-alt00:02
*** baoli has joined #openstack-meeting-alt00:02
*** walker_ has quit IRC00:04
*** TravT has quit IRC00:06
*** rudrarugge has joined #openstack-meeting-alt00:06
*** baoli has quit IRC00:07
*** rmoe has quit IRC00:10
*** adrian_otto has quit IRC00:11
*** rudrarugge has quit IRC00:12
*** tdruiva has quit IRC00:14
*** harlowja has quit IRC00:15
*** harlowja_ has joined #openstack-meeting-alt00:15
*** dims has joined #openstack-meeting-alt00:16
*** christop1eraedo is now known as christopheraedo00:18
*** rmoe has joined #openstack-meeting-alt00:20
*** gyee_ has quit IRC00:21
*** Riddhi has quit IRC00:25
*** Riddhi has joined #openstack-meeting-alt00:26
*** yamahata has joined #openstack-meeting-alt00:28
*** dane_leblanc has joined #openstack-meeting-alt00:29
*** alazarev has quit IRC00:29
*** cjellick has quit IRC00:30
*** cjellick has joined #openstack-meeting-alt00:30
*** yamahata has quit IRC00:33
*** yamahata has joined #openstack-meeting-alt00:34
*** dane_leblanc has quit IRC00:35
*** cjellick has quit IRC00:35
*** dane_leblanc has joined #openstack-meeting-alt00:37
*** eghobo has quit IRC00:39
*** eghobo has joined #openstack-meeting-alt00:39
*** SumitNaiksatam has joined #openstack-meeting-alt00:43
*** ijw has quit IRC00:47
*** banix has quit IRC00:48
*** bdpayne has quit IRC00:50
*** zhhuabj has quit IRC00:51
*** jcoufal has quit IRC00:55
*** alex_xu has joined #openstack-meeting-alt01:01
*** celttechie_ has quit IRC01:01
*** jjmb has joined #openstack-meeting-alt01:01
*** baoli has joined #openstack-meeting-alt01:03
*** ijw has joined #openstack-meeting-alt01:07
*** dtx00ff has quit IRC01:07
*** baoli has quit IRC01:07
*** yamahata has quit IRC01:09
*** yamahata has joined #openstack-meeting-alt01:09
*** ijw has quit IRC01:11
*** otherwiseguy has quit IRC01:13
*** shakamunyi has joined #openstack-meeting-alt01:17
*** ijw has joined #openstack-meeting-alt01:20
*** tdruiva has joined #openstack-meeting-alt01:21
*** thangp has joined #openstack-meeting-alt01:22
*** otherwiseguy has joined #openstack-meeting-alt01:26
*** richm has quit IRC01:28
*** ijw has quit IRC01:28
*** marcoemorais has quit IRC01:29
*** mwagner_lap has joined #openstack-meeting-alt01:29
*** tdruiva has quit IRC01:29
*** gokrokve has joined #openstack-meeting-alt01:30
*** amotoki has joined #openstack-meeting-alt01:34
*** arnaud has quit IRC01:41
*** dane_leblanc has quit IRC01:43
*** dims has quit IRC01:44
*** dims has joined #openstack-meeting-alt01:44
*** nosnos has joined #openstack-meeting-alt01:44
*** dims has quit IRC01:45
*** dims_ has joined #openstack-meeting-alt01:45
*** mberlin1 has joined #openstack-meeting-alt01:46
*** mberlin has quit IRC01:46
*** ramashri has quit IRC01:48
*** gokrokve has quit IRC01:50
*** adrian_otto has joined #openstack-meeting-alt01:52
*** woodster_ has quit IRC01:55
*** alex_xu has quit IRC01:56
*** baohua has joined #openstack-meeting-alt01:56
*** bdpayne has joined #openstack-meeting-alt02:01
*** spzala has joined #openstack-meeting-alt02:02
*** dims_ has quit IRC02:02
*** dims has joined #openstack-meeting-alt02:03
*** christopheraedo has quit IRC02:03
*** baoli has joined #openstack-meeting-alt02:04
*** gcb_ has joined #openstack-meeting-alt02:04
*** christopheraedo has joined #openstack-meeting-alt02:05
*** gokrokve has joined #openstack-meeting-alt02:06
*** baoli has quit IRC02:08
*** dims has quit IRC02:12
*** dims has joined #openstack-meeting-alt02:12
*** spzala has quit IRC02:14
*** alex_xu has joined #openstack-meeting-alt02:14
*** rcleere has joined #openstack-meeting-alt02:14
*** arnaud has joined #openstack-meeting-alt02:19
*** dims has quit IRC02:22
*** rcleere has quit IRC02:22
*** dims has joined #openstack-meeting-alt02:23
*** rcleere has joined #openstack-meeting-alt02:23
*** shakayumi has joined #openstack-meeting-alt02:24
*** dims has quit IRC02:27
*** dims has joined #openstack-meeting-alt02:27
*** shakamunyi has quit IRC02:28
*** alexiz has joined #openstack-meeting-alt02:30
*** eankutse has joined #openstack-meeting-alt02:33
*** shakayumi has quit IRC02:34
*** dims has quit IRC02:35
*** dims has joined #openstack-meeting-alt02:36
*** hachao has quit IRC02:36
*** hachao has joined #openstack-meeting-alt02:37
*** dims has quit IRC02:40
*** harlowja_ is now known as harlowja_away02:42
*** xuhanp has joined #openstack-meeting-alt02:44
*** ramishra has joined #openstack-meeting-alt02:48
*** ramishra_ has joined #openstack-meeting-alt02:49
*** ramishra has quit IRC02:52
*** dimtruck is now known as zz_dimtruck02:52
*** Riddhi_ has joined #openstack-meeting-alt02:52
*** Riddhi has quit IRC02:53
*** eghobo has quit IRC02:53
*** padkrish has quit IRC02:55
*** cjellick has joined #openstack-meeting-alt03:01
*** cjellick has quit IRC03:01
*** cjellick has joined #openstack-meeting-alt03:02
*** baoli has joined #openstack-meeting-alt03:05
*** balajiiyer has joined #openstack-meeting-alt03:05
*** balajiiyer has left #openstack-meeting-alt03:05
*** mattgriffin has joined #openstack-meeting-alt03:08
*** baoli has quit IRC03:09
*** ramishra_ has quit IRC03:10
*** mattgriffin has quit IRC03:11
*** ramishra has joined #openstack-meeting-alt03:11
*** nelsnelson has joined #openstack-meeting-alt03:12
*** Sukhdev has joined #openstack-meeting-alt03:17
*** ramishra has quit IRC03:18
*** ramishra has joined #openstack-meeting-alt03:19
*** tdruiva has joined #openstack-meeting-alt03:20
*** chandankumar has joined #openstack-meeting-alt03:27
*** eankutse has quit IRC03:34
*** jjmb has quit IRC03:36
*** Riddhi_ has quit IRC03:37
*** zz_dimtruck is now known as dimtruck03:37
*** thangp has quit IRC03:40
*** chandankumar has quit IRC03:44
*** dimtruck is now known as zz_dimtruck03:47
*** esheffield has quit IRC03:47
*** gokrokve has quit IRC03:51
*** shakamunyi has joined #openstack-meeting-alt03:54
*** alexiz has quit IRC03:57
*** kebray has joined #openstack-meeting-alt03:59
*** adrian_otto has quit IRC04:00
*** dtx00ff has joined #openstack-meeting-alt04:01
*** ijw has joined #openstack-meeting-alt04:02
*** baoli has joined #openstack-meeting-alt04:05
*** ijw has quit IRC04:07
*** arnaud has quit IRC04:10
*** baoli has quit IRC04:10
*** arnaud has joined #openstack-meeting-alt04:12
*** akuznetsov has joined #openstack-meeting-alt04:15
*** otherwiseguy has quit IRC04:18
*** otherwiseguy has joined #openstack-meeting-alt04:21
*** prmtl has joined #openstack-meeting-alt04:25
*** walker_ has joined #openstack-meeting-alt04:26
*** alex_xu has quit IRC04:31
*** gokrokve has joined #openstack-meeting-alt04:36
*** gcb_ has quit IRC04:36
*** cjellick_ has joined #openstack-meeting-alt04:47
*** dtx00ff has quit IRC04:48
*** cjellick has quit IRC04:50
*** cjellick_ has quit IRC04:51
*** gcb has joined #openstack-meeting-alt04:53
*** dtx00ff has joined #openstack-meeting-alt04:57
*** otherwiseguy has quit IRC05:01
*** betsy has joined #openstack-meeting-alt05:03
*** dtx00ff has quit IRC05:04
*** dtx00ff has joined #openstack-meeting-alt05:04
*** nelsnelson has quit IRC05:06
*** baoli has joined #openstack-meeting-alt05:06
*** nelsnelson has joined #openstack-meeting-alt05:06
*** baoli has quit IRC05:10
*** Sukhdev has quit IRC05:17
*** bdpayne has quit IRC05:18
*** kebray has quit IRC05:20
*** prmtl has quit IRC05:22
*** teran has quit IRC05:22
*** alex_xu has joined #openstack-meeting-alt05:23
*** bdpayne has joined #openstack-meeting-alt05:24
*** chandankumar has joined #openstack-meeting-alt05:25
*** prmtl has joined #openstack-meeting-alt05:26
*** kebray has joined #openstack-meeting-alt05:27
*** kebray has quit IRC05:27
*** prmtl has quit IRC05:31
*** padkrish has joined #openstack-meeting-alt05:31
*** padkrish has quit IRC05:31
*** padkrish has joined #openstack-meeting-alt05:32
*** adrian_otto has joined #openstack-meeting-alt05:33
*** adrian_otto has quit IRC05:36
*** shakamunyi has quit IRC05:37
*** zz_dimtruck is now known as dimtruck05:38
*** adrian_otto has joined #openstack-meeting-alt05:40
*** ramishra has quit IRC05:41
*** adrian_otto has quit IRC05:42
*** ramishra has joined #openstack-meeting-alt05:42
*** adrian_otto has joined #openstack-meeting-alt05:43
*** adrian_otto has quit IRC05:43
*** adrian_otto has joined #openstack-meeting-alt05:44
*** otherwiseguy has joined #openstack-meeting-alt05:46
*** walker_ has quit IRC05:46
*** ramishra has quit IRC05:47
*** cjellick has joined #openstack-meeting-alt05:48
*** dimtruck is now known as zz_dimtruck05:48
*** ramishra has joined #openstack-meeting-alt05:48
*** otherwiseguy has quit IRC05:55
*** cjellick has quit IRC05:56
*** adrian_otto has quit IRC05:56
*** Sukhdev has joined #openstack-meeting-alt05:56
*** walker_ has joined #openstack-meeting-alt06:00
*** walker__ has joined #openstack-meeting-alt06:02
*** ijw has joined #openstack-meeting-alt06:04
*** walker_ has quit IRC06:04
*** gokrokve_ has joined #openstack-meeting-alt06:05
*** baoli has joined #openstack-meeting-alt06:07
*** gokrokve has quit IRC06:08
*** ijw has quit IRC06:08
*** gokrokve_ has quit IRC06:09
*** shauno_ has quit IRC06:10
*** baoli has quit IRC06:12
*** HeOS has quit IRC06:16
*** bdpayne has quit IRC06:20
*** flaper87|afk is now known as flaper8706:21
*** ramishra has quit IRC06:21
*** _nadya_ has joined #openstack-meeting-alt06:21
*** ramishra has joined #openstack-meeting-alt06:22
*** teran has joined #openstack-meeting-alt06:23
*** prmtl has joined #openstack-meeting-alt06:25
*** arnaud has quit IRC06:25
*** prmtl has quit IRC06:25
*** k4n0 has joined #openstack-meeting-alt06:25
*** teran_ has joined #openstack-meeting-alt06:25
*** prmtl has joined #openstack-meeting-alt06:25
*** _nadya_ has quit IRC06:26
*** teran has quit IRC06:28
*** tdruiva has quit IRC06:28
*** teran has joined #openstack-meeting-alt06:29
*** teran_ has quit IRC06:30
*** teran_ has joined #openstack-meeting-alt06:30
*** SumitNaiksatam_ has joined #openstack-meeting-alt06:33
*** teran has quit IRC06:34
*** jtomasek has joined #openstack-meeting-alt06:34
*** teran_ has quit IRC06:35
*** teran has joined #openstack-meeting-alt06:36
*** SumitNaiksatam has quit IRC06:36
*** SumitNaiksatam_ is now known as SumitNaiksatam06:36
*** teran_ has joined #openstack-meeting-alt06:38
*** teran__ has joined #openstack-meeting-alt06:40
*** tdruiva has joined #openstack-meeting-alt06:40
*** teran has quit IRC06:41
*** teran_ has quit IRC06:43
*** teran__ has quit IRC06:45
*** shauno_ has joined #openstack-meeting-alt06:51
*** shauno_ has quit IRC07:00
*** Sukhdev has quit IRC07:01
*** ujuc has joined #openstack-meeting-alt07:02
*** jcoufal has joined #openstack-meeting-alt07:02
*** walker__ has quit IRC07:03
*** shakamunyi has joined #openstack-meeting-alt07:03
*** shauno_ has joined #openstack-meeting-alt07:05
*** denis_makogon has joined #openstack-meeting-alt07:05
*** denis_makogon has quit IRC07:05
*** padkrish has quit IRC07:07
*** baoli has joined #openstack-meeting-alt07:08
*** padkrish has joined #openstack-meeting-alt07:08
*** shakamunyi has quit IRC07:08
*** deepakcs has joined #openstack-meeting-alt07:10
*** baoli has quit IRC07:12
*** zeddii has quit IRC07:13
*** zeddii has joined #openstack-meeting-alt07:13
*** padkrish has quit IRC07:22
*** shauno_ has quit IRC07:23
*** _nadya_ has joined #openstack-meeting-alt07:24
*** jprovazn has joined #openstack-meeting-alt07:30
*** pkoniszewski has joined #openstack-meeting-alt07:31
*** teran has joined #openstack-meeting-alt07:34
*** zz_dimtruck is now known as dimtruck07:37
*** doude has joined #openstack-meeting-alt07:38
*** shauno_ has joined #openstack-meeting-alt07:38
*** otherwiseguy has joined #openstack-meeting-alt07:38
*** banix has joined #openstack-meeting-alt07:38
*** shauno_ has quit IRC07:43
*** otherwiseguy has quit IRC07:44
*** dimtruck is now known as zz_dimtruck07:47
*** shauno_ has joined #openstack-meeting-alt07:50
*** matrohon has joined #openstack-meeting-alt07:53
*** stannie has joined #openstack-meeting-alt08:00
*** julienvey has joined #openstack-meeting-alt08:03
*** peoplemerge_ has quit IRC08:04
*** shakamunyi has joined #openstack-meeting-alt08:04
*** peoplemerge_ has joined #openstack-meeting-alt08:06
*** ijw has joined #openstack-meeting-alt08:06
*** prmtl has quit IRC08:07
*** prmtl has joined #openstack-meeting-alt08:08
*** ramishra has quit IRC08:08
*** baoli has joined #openstack-meeting-alt08:08
*** shakamunyi has quit IRC08:09
*** ijw has quit IRC08:10
*** Longgeek has joined #openstack-meeting-alt08:10
*** Longgeek has quit IRC08:11
*** Longgeek has joined #openstack-meeting-alt08:12
*** baoli has quit IRC08:13
*** derekh has joined #openstack-meeting-alt08:16
*** ramishra has joined #openstack-meeting-alt08:18
*** kragniz has joined #openstack-meeting-alt08:22
*** kragniz has quit IRC08:27
*** kragniz has joined #openstack-meeting-alt08:29
*** _nadya_ has quit IRC08:31
*** pnavarro has joined #openstack-meeting-alt08:31
*** otherwiseguy has joined #openstack-meeting-alt08:33
*** otherwiseguy has quit IRC08:37
*** ramishra_ has joined #openstack-meeting-alt08:38
*** e0ne has joined #openstack-meeting-alt08:38
*** ramishra has quit IRC08:39
*** _nadya_ has joined #openstack-meeting-alt08:42
*** e0ne has quit IRC08:45
*** igordcard has joined #openstack-meeting-alt08:47
*** mberlin1 has quit IRC08:48
*** mberlin has joined #openstack-meeting-alt09:00
*** zz_johnthetubagu is now known as johnthetubaguy09:01
*** dtx00ff has quit IRC09:04
*** shakamunyi has joined #openstack-meeting-alt09:05
*** ijw has joined #openstack-meeting-alt09:06
*** HeOS has joined #openstack-meeting-alt09:07
*** baoli has joined #openstack-meeting-alt09:09
*** shakamunyi has quit IRC09:09
*** ijw has quit IRC09:11
*** baoli has quit IRC09:14
*** dtx00ff has joined #openstack-meeting-alt09:16
*** funzo has quit IRC09:17
*** funzo has joined #openstack-meeting-alt09:18
*** igordcard has quit IRC09:20
*** dtx00ff has quit IRC09:25
*** igordcard has joined #openstack-meeting-alt09:25
*** dtx00ff has joined #openstack-meeting-alt09:26
*** otherwiseguy has joined #openstack-meeting-alt09:27
*** e0ne has joined #openstack-meeting-alt09:28
*** dtx00ff has quit IRC09:30
*** otherwiseguy has quit IRC09:31
*** otherwiseguy has joined #openstack-meeting-alt09:32
*** banix has quit IRC09:35
*** otherwiseguy has quit IRC09:37
*** teran has quit IRC09:39
*** gcb has quit IRC09:47
*** yamahata has quit IRC09:58
*** baohua has quit IRC10:01
*** tchaypo has joined #openstack-meeting-alt10:01
*** niclem has quit IRC10:02
*** xuhanp has quit IRC10:03
*** teran has joined #openstack-meeting-alt10:06
*** matrohon has quit IRC10:06
*** baoli has joined #openstack-meeting-alt10:10
*** baoli has quit IRC10:14
*** e0ne has quit IRC10:27
*** e0ne has joined #openstack-meeting-alt10:34
*** Longgeek has quit IRC10:35
*** Longgeek has joined #openstack-meeting-alt10:36
*** ramishra_ has quit IRC10:36
*** teran has quit IRC10:39
*** Longgeek has quit IRC10:40
*** ramishra has joined #openstack-meeting-alt10:45
*** jaypipes has quit IRC10:55
*** teran has joined #openstack-meeting-alt10:55
*** jjmb has joined #openstack-meeting-alt11:00
*** ramishra_ has joined #openstack-meeting-alt11:01
*** ramishra_ has quit IRC11:01
*** teran has quit IRC11:02
*** ramishra_ has joined #openstack-meeting-alt11:02
*** ramishra has quit IRC11:05
*** Longgeek has joined #openstack-meeting-alt11:06
*** prmtl has quit IRC11:06
*** prmtl has joined #openstack-meeting-alt11:06
*** Longgeek has quit IRC11:09
*** Longgeek has joined #openstack-meeting-alt11:09
*** baoli has joined #openstack-meeting-alt11:11
*** baoli has quit IRC11:15
*** mikedillion has joined #openstack-meeting-alt11:18
*** e0ne has quit IRC11:18
*** dims has joined #openstack-meeting-alt11:20
*** e0ne has joined #openstack-meeting-alt11:20
*** dims has quit IRC11:20
*** dims has joined #openstack-meeting-alt11:20
*** prmtl has quit IRC11:25
*** teran has joined #openstack-meeting-alt11:25
*** pnavarro has quit IRC11:26
*** teran_ has joined #openstack-meeting-alt11:26
*** amotoki has quit IRC11:28
*** teran has quit IRC11:30
*** mikedillion has quit IRC11:35
*** ramishra_ has quit IRC11:37
*** pnavarro has joined #openstack-meeting-alt11:38
*** deepakcs has quit IRC11:42
*** prmtl has joined #openstack-meeting-alt11:45
*** _nadya_ has quit IRC11:47
*** ramishra has joined #openstack-meeting-alt11:49
*** shauno__ has joined #openstack-meeting-alt11:57
*** shauno_ has quit IRC11:59
*** ramishra has quit IRC12:01
*** prmtl has quit IRC12:02
*** Longgeek has quit IRC12:03
*** teran has joined #openstack-meeting-alt12:03
*** teran_ has quit IRC12:04
*** shauno_ has joined #openstack-meeting-alt12:04
*** teran_ has joined #openstack-meeting-alt12:04
*** ramishra has joined #openstack-meeting-alt12:07
*** shauno__ has quit IRC12:08
*** teran has quit IRC12:08
*** ijw has joined #openstack-meeting-alt12:08
*** prmtl has joined #openstack-meeting-alt12:11
*** baoli has joined #openstack-meeting-alt12:11
*** Longgeek has joined #openstack-meeting-alt12:12
*** Longgeek has quit IRC12:13
*** nosnos has quit IRC12:13
*** ijw has quit IRC12:13
*** Longgeek has joined #openstack-meeting-alt12:14
*** dprince has joined #openstack-meeting-alt12:14
*** satish_ has joined #openstack-meeting-alt12:15
*** baoli has quit IRC12:16
*** niclem has joined #openstack-meeting-alt12:22
*** flaviof is now known as flaviof_zzz12:23
*** ramishra has quit IRC12:24
*** zz_dimtruck is now known as dimtruck12:27
*** woodster_ has joined #openstack-meeting-alt12:28
*** serg_melikyan has quit IRC12:28
*** rushiagr has joined #openstack-meeting-alt12:41
*** flaper87 is now known as flaper87|afk12:44
*** radez_g0n3 is now known as radez12:48
*** ujuc has quit IRC12:50
*** flaviof_zzz is now known as flaviof12:53
*** dims has quit IRC12:54
*** dims has joined #openstack-meeting-alt12:54
*** cjellick has joined #openstack-meeting-alt12:54
*** cjellick has quit IRC12:59
*** satish has joined #openstack-meeting-alt13:01
*** thomasem has joined #openstack-meeting-alt13:02
*** satish_ has quit IRC13:03
*** julim has joined #openstack-meeting-alt13:05
*** xianghuihui has joined #openstack-meeting-alt13:06
*** _nadya_ has joined #openstack-meeting-alt13:07
*** jaypipes has joined #openstack-meeting-alt13:07
*** samstav has quit IRC13:08
*** andreaf has quit IRC13:08
*** xianghui has quit IRC13:09
*** xianghui has joined #openstack-meeting-alt13:10
*** tdruiva has quit IRC13:11
*** xianghui has quit IRC13:12
*** baoli has joined #openstack-meeting-alt13:12
*** xianghui has joined #openstack-meeting-alt13:12
*** xianghuihui has quit IRC13:13
*** satish_ has joined #openstack-meeting-alt13:14
*** richm has joined #openstack-meeting-alt13:14
*** satish has quit IRC13:16
*** eankutse has joined #openstack-meeting-alt13:16
*** baoli has quit IRC13:17
*** prmtl_ has joined #openstack-meeting-alt13:24
*** prmtl has quit IRC13:24
*** ramishra has joined #openstack-meeting-alt13:25
*** betsy has quit IRC13:27
*** ramishra has quit IRC13:29
*** georgelorch has joined #openstack-meeting-alt13:32
*** deepakcs has joined #openstack-meeting-alt13:32
*** ujuc has joined #openstack-meeting-alt13:35
*** thangp has joined #openstack-meeting-alt13:38
*** luizfar has joined #openstack-meeting-alt13:40
*** radez is now known as radez_g0n313:43
*** shauno_ has quit IRC13:44
*** esheffield has joined #openstack-meeting-alt13:45
*** mestery has joined #openstack-meeting-alt13:47
*** tdruiva has joined #openstack-meeting-alt13:47
*** juzuluag has joined #openstack-meeting-alt13:49
*** baohua has joined #openstack-meeting-alt13:50
*** lisaclark1 has joined #openstack-meeting-alt13:52
*** bauzas has joined #openstack-meeting-alt13:55
*** k4n0 has quit IRC13:55
*** mriedem has joined #openstack-meeting-alt13:55
*** sgordon has joined #openstack-meeting-alt13:57
*** armax has joined #openstack-meeting-alt13:58
*** luizfar has quit IRC13:59
*** danpb has joined #openstack-meeting-alt13:59
*** samstav has joined #openstack-meeting-alt14:00
*** luizfar has joined #openstack-meeting-alt14:00
*** adrian_otto has joined #openstack-meeting-alt14:00
*** mestery has quit IRC14:00
*** balajiiyer has joined #openstack-meeting-alt14:01
*** satish has joined #openstack-meeting-alt14:01
dansmithjohnthetubaguy: cuckoo cuckoo14:01
johnthetubaguyyeah14:01
johnthetubaguy#startmeeting nova14:01
openstackMeeting started Thu Aug 21 14:01:25 2014 UTC and is due to finish in 60 minutes.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: nova)"14:01
openstackThe meeting name has been set to 'nova'14:01
johnthetubaguyhello all14:01
mriedemhi!14:01
dansmitho/14:01
pkoniszewskio/14:01
*** mestery has joined #openstack-meeting-alt14:01
leifzo/ after two weeks out.14:01
*** gokrokve has joined #openstack-meeting-alt14:01
bauzas\o14:02
johnthetubaguy#topic Juno Status14:02
*** openstack changes topic to "Juno Status (Meeting topic: nova)"14:02
danpb\o/14:02
johnthetubaguyso the big thing, end of today is Feature Proposal Freeze14:02
johnthetubaguyi.e. all patches for code features must be up for review14:02
johnthetubaguyelse you will need an exception14:02
adrian_ottoo/14:02
*** satish_ has quit IRC14:03
johnthetubaguydansmith: I think we said three core reviews to get an exception this time?14:03
*** kai has joined #openstack-meeting-alt14:03
dansmithjohnthetubaguy: that was the suggestion, based on previous cycles, yeah :)14:03
johnthetubaguydansmith: yeah, I like that14:03
johnthetubaguyanyone against that idea?14:03
bauzass/reviews/reviewers ?14:04
dansmithbauzas: yeah14:04
*** yjiang5 has joined #openstack-meeting-alt14:04
*** mjturek has joined #openstack-meeting-alt14:04
dansmithbauzas: sponsors, if you will14:04
bauzasdansmith: gotcha, tks14:04
*** balajiiyer has left #openstack-meeting-alt14:04
*** zz_gondoi is now known as gondoi14:04
johnthetubaguy#info expect you will need three core developer to sponsor a blueprint if you want a feature proposal freeze exception, same for feature freeze exceptions14:04
*** lisaclark1 has quit IRC14:05
johnthetubaguyOK...14:05
johnthetubaguy#link https://launchpad.net/nova/+milestone/juno-314:05
johnthetubaguyso anyone got any updates on high and medium blueprints they want to discuss14:05
*** rcleere has quit IRC14:05
johnthetubaguyI have tidied up the list so they are all Needs Code Review14:05
*** prmtl_ has quit IRC14:05
johnthetubaguyI am likely to kick out the low blueprints with no code tomorrow morning UK time, unless mikal beats me to it14:06
johnthetubaguydansmith: you send a good ML update a few days back, any major changes there?14:06
*** prmtl has joined #openstack-meeting-alt14:06
johnthetubaguy#info please focus on reviewing the high priority and then medium priority blueprints: https://launchpad.net/nova/+milestone/juno-314:06
dansmithjohnthetubaguy: on the review priorities? I think most of what I had was about the ironic stuff,14:07
dansmithjohnthetubaguy: which is making progress, but I haven't seen anything in the last couple days.. should check this morning14:07
mriedemjohnthetubaguy: the code for this is merged from what i can tell https://blueprints.launchpad.net/nova/+spec/add-differencing-vhdx-resize-support14:07
alaskio/14:07
johnthetubaguymriedem: thanks I need to double check stuff like that after the big kick out14:07
danpbjohnthetubaguy: as mentioned on the mailing list, i think we need to make it a high priority to also review patches which already have one +214:08
johnthetubaguymriedem: if you could link the patch series you know about that would be handy14:08
mriedemjohnthetubaguy: yeah it's in there, it's only 1 patch14:08
danpbjohnthetubaguy: we've got > 100 patches outstanding which have one +2 and no negative feedback some of which are a month old14:08
johnthetubaguydanpb: thats a fair point14:08
johnthetubaguymriedem: oh, I assumed that was the spec14:08
*** dgenin has joined #openstack-meeting-alt14:08
danpbwhich is just totally ridiculous and creating work for ourselves with inevitable rebases14:09
russellbmriedem: updated14:09
mriedemjohnthetubaguy: no i think that missed icehouse so it was ready to go14:09
mriedemrussellb: thanks14:09
mriedemdanpb: some of those are in the tail end of a series, like vmware refactors14:09
mriedemdanpb: it's a good point, it's just not all onesy twosy fixes14:09
johnthetubaguyrussellb: thanks14:09
danpbmriedem: that's a tiny minority of the ones i've looked at so far14:09
*** mestery has quit IRC14:10
mriedemmoving on...14:10
johnthetubaguydanpb: agreed, looking at stuff that already has a +2 makes sense at this point14:10
johnthetubaguyyeah14:10
*** mestery_ has joined #openstack-meeting-alt14:10
johnthetubaguywe know what we need to do14:10
*** ijw has joined #openstack-meeting-alt14:10
johnthetubaguy#info Feature Proposal Freeze August 21st, September 4th Juno-3, FF and SF14:10
*** samstav has quit IRC14:10
johnthetubaguyso all patches need to be in by Sept 4th as a reminder14:10
johnthetubaguyideally well before that14:11
johnthetubaguy#topic Bugs14:11
*** openstack changes topic to "Bugs (Meeting topic: nova)"14:11
*** lisaclark1 has joined #openstack-meeting-alt14:11
johnthetubaguyOK, so there is a new feature on this web page:14:11
johnthetubaguy#link http://54.201.139.117/nova-bugs.html14:11
johnthetubaguy#info see what is in progress and needs reviewing14:11
*** chuckC_ has quit IRC14:11
*** mestery_ is now known as mestery14:11
johnthetubaguyOK, nothing more there I guess14:12
*** vjardin_ has joined #openstack-meeting-alt14:12
johnthetubaguy#topic Gate status14:12
*** openstack changes topic to "Gate status (Meeting topic: nova)"14:12
mriedemgate is fine, had a jsonschema issue yesterday but quickly resolved by dansmith14:12
johnthetubaguycools14:13
dansmith\o/14:13
mriedemsounds like other projects have the same issue, i.e. sahara14:13
johnthetubaguytop work14:13
mriedemthey have a reqs patch to cap jsonschema, but they should probably just update their unit tests14:13
*** baoli has joined #openstack-meeting-alt14:13
johnthetubaguy#topic Mid-cycle summary14:13
*** openstack changes topic to "Mid-cycle summary (Meeting topic: nova)"14:13
johnthetubaguymikal is working on a summary of what happened now14:13
johnthetubaguyetherpad is still there for the other bits14:13
mriedemhe has a lot of nice blog posts already14:13
*** ndipanov has joined #openstack-meeting-alt14:14
mriedemhttp://www.stillhq.com/openstack/juno/000014.html14:14
johnthetubaguy#link https://etherpad.openstack.org/p/juno-nova-mid-cycle-meetup14:14
mriedemactually http://www.stillhq.com/openstack/juno/14:14
johnthetubaguyyeah, there are a few on the minuets14:14
johnthetubaguymriedem: cool, thats the link14:14
johnthetubaguy#link http://www.stillhq.com/openstack/juno/14:14
johnthetubaguyfeedback via the ML I guess14:15
*** ijw has quit IRC14:15
*** samstav has joined #openstack-meeting-alt14:15
johnthetubaguy#topic Open Discussion14:15
*** openstack changes topic to "Open Discussion (Meeting topic: nova)"14:15
adrian_ottoo/ Containers Team Update14:15
johnthetubaguyOK, so the first think is OS profiler14:15
johnthetubaguythats on the agenda14:15
johnthetubaguyboris-42: are you around?14:15
boris-42johnthetubaguy hi there14:16
johnthetubaguy#link https://review.openstack.org/#/c/105096/14:16
boris-42johnthetubaguy what is this meeting about?14:16
johnthetubaguy#link https://review.openstack.org/#/c/105089/14:16
johnthetubaguyboris-42: this is the nova meeting14:16
boris-42johnthetubaguy ahh =)14:16
boris-42johnthetubaguy okay ya14:16
johnthetubaguyboris-42: I think mikal wanted you to talk about the os profiler stuff14:16
*** belliott has joined #openstack-meeting-alt14:16
*** niclem has quit IRC14:16
boris-42johnthetubaguy yep I asked him14:16
boris-42johnthetubaguy I thought it's a bit later14:16
johnthetubaguyOK, jogo is −2 on this, and he will not be awake till later on14:17
boris-42johnthetubaguy so osprofiler stuff is very useful for developers & operators and dev & production enviorments14:17
boris-42johnthetubaguy -2 is cause of politics14:17
boris-42johnthetubaguy not because of code14:17
boris-42johnthetubaguy so you can ignore that -214:17
*** baoli has quit IRC14:17
boris-42johnthetubaguy this is comment of Joe14:17
boris-42blocked until oslo spec is merged: https://review.openstack.org/#/c/103825/14:17
boris-42johnthetubaguy let's talk about osprofiler stuff14:18
danpbis there any nova blueprint for this feature ?14:18
mriedemnope, the blueprint is in oslo14:18
johnthetubaguydanpb: thats my object honestly, there isn't one14:18
boris-42danpb nope, I really don't want to add14:18
mriedemit's one of these cross project things that some projects have adopted already but not nova14:18
boris-42danpb blueprints for every project14:18
boris-42mriedem +114:18
danpbok, where is the olso blueprint ?14:19
boris-42one sec14:19
boris-42danpb14:19
boris-42danpb https://review.openstack.org/#/c/103825/14:19
boris-42danpb this is14:19
*** prmtl has quit IRC14:19
boris-42danpb spec14:19
boris-42danpb for dicussion14:19
*** nelsnelson has quit IRC14:19
*** Leonr has joined #openstack-meeting-alt14:19
*** lisaclark1 has quit IRC14:20
boris-42danpb johnthetubaguy actually more interesting is the way how to use it14:20
boris-42and results14:20
boris-42danpb johnthetubaguy http://boris-42.github.io/ngk.html14:20
boris-42so this shows trace of booting VM via CLI14:20
johnthetubaguyboris-42: OK, I think I will have to stop you, this is taking too long for this meeting with such a wide audience14:20
johnthetubaguyboris-42: what did you want decided today?14:20
*** tobybot11 has joined #openstack-meeting-alt14:20
boris-42johnthetubaguy just to get more reviews on patch14:21
johnthetubaguyboris-42: yes or no for the current approach?14:21
johnthetubaguyOK14:21
boris-42johnthetubaguy actually I hope that nobody will be against14:21
*** lisaclark1 has joined #openstack-meeting-alt14:21
johnthetubaguyso are people happy with a feature coming into nova via an oslo blueprint14:21
boris-42johnthetubaguy mikal as I know is=)14:21
johnthetubaguyin a cross project consistency way14:21
boris-42johnthetubaguy I can't say about all people in openstack14:21
ndipanovjohnthetubaguy, would that be the first?14:21
dansmithjohnthetubaguy: I'd need to review the impact first14:21
*** david-lyle has joined #openstack-meeting-alt14:21
ndipanovnot really I think14:21
boris-42danpb what kind of impact?14:22
dansmithndipanov: the first of this magnitude I think14:22
boris-42dansmith*14:22
danpbunless i'm missing something,the olso spec isn't even approved yet14:22
ndipanovit's not14:22
danpbso isn't it premature to talkl about merging code14:22
boris-42danpb it's not approved, cause I am waiting more poeple14:22
bauzasI'll also put some comments on how it's proposed14:22
ndipanovbut a lot of the comments are some political bikesheding about where it belongs14:22
boris-42danpb I would like to discuss with as much as possible people14:22
danpbto be clear, i think the feature is very useful and desirable14:22
dansmithboris-42: meaning what the impact to nova code is, to decide if I think it needs a spec or not14:22
ndipanovit's been on my list for some time now but never got to it14:22
boris-42dansmith there is no big impact14:22
boris-42dansmith on code14:23
danpbbut it seems pretty late in the day for us to talk about this for nova now isn't it ?14:23
bauzasthe implementation requires an external dependency which is not part of the reqs.txt IIUC14:23
*** nelsnelson has joined #openstack-meeting-alt14:23
johnthetubaguydanpb: thats me feeling here14:23
boris-42bauzas ?14:23
boris-42bauzas it's in global requriemtns14:23
dansmithjohnthetubaguy: certainly too late for juno, right?14:23
johnthetubaguyI think we just need to discuss this one on the ML after people have reviewed the patch14:23
danpbseparately we should definitely clarify how we want to handle things like this from the specs process POV14:23
johnthetubaguydansmith: thats my thinking14:23
danpbbecause we don't want to make people create one spec for every project14:23
leifzthis spec also includes API changes correct?14:24
boris-42danpb ya that sux14:24
johnthetubaguyI see it as having missed the blueprint freeze14:24
danpbbut we need  a way to draw nova teams atttention to the oslo spec14:24
johnthetubaguydanpb: agreed, we should have a way to do that14:24
boris-42johnthetubaguy this feature was discussed since Atlanta summit14:24
boris-42johnthetubaguy and there were cross session14:24
*** ramishra has joined #openstack-meeting-alt14:24
mriedemfwiw for db2 we've created specs for each project14:24
boris-42johnthetubaguy and I addressed all issues14:24
boris-42johnthetubaguy and even more14:24
boris-42=)14:24
mriedemwhich is cross project14:24
boris-42johnthetubaguy so it's not from yestarday14:24
dansmithspecs for each project make sense if the impact is not the same to each project, IMHO14:24
ndipanovmriedem, were you happy with that14:24
ndipanov?14:24
boris-42mriedem imho I don't want to taht=)14:24
johnthetubaguyboris-42: yes, but there were two sessions at once, and I didn't know it impacted nova, etc14:24
mriedemndipanov: each project has different db migration issues with db2 so yeah it made sense14:25
leifzdansmith: +114:25
*** mattgriffin has joined #openstack-meeting-alt14:25
ndipanovok then14:25
danpbmriedem: potentially we could simply create a dummy placeholder nova spec that says no more than "read the oslo spec" as a way to draw attention to it14:25
mriedemboris-42: i'm not saying we wanted to, but it is what it is14:25
mriedemdanpb: sure14:25
johnthetubaguydanpb: that would be reasonable I feel, just to get nova drivers to sign off on it, I like that14:25
boris-42mriedem ya but in this case approach is absolutely the same14:25
boris-42mriedem you need patch in client, you need patch in main project, and they are almost similiar14:25
*** tbarron has joined #openstack-meeting-alt14:26
boris-42mriedem probably some tests are affected but overall it's the same change14:26
dansmithif it touches our API, then it seems like it has to have a spec, right?14:26
dansmitheven if it's just the API bits, and then "look at the oslo spec for the rest of the details"14:26
boris-42dansmith okay guys if you need spec14:26
johnthetubaguydansmith: +1 it changes the paste file14:26
leifzboris-42: the concern I have is getting ops folks to take a look who only look at nova specs and not oslo specs.14:26
boris-42dansmith ant these are rules14:26
boris-42dansmith I can make it14:26
*** n0ano has joined #openstack-meeting-alt14:26
boris-42dansmith but I hope I won't need to wait Kilo?14:26
boris-42dansmith to get it?14:26
johnthetubaguyboris-42: if it needs a spec, its not in juno, I think thats the thing14:27
*** PhilD has joined #openstack-meeting-alt14:27
dansmithboris-42: you do in my opinion14:27
*** lisaclark1 has quit IRC14:27
johnthetubaguydansmith: +114:27
boris-42dansmith okay I will do spec14:27
dansmithjohnthetubaguy: anyway, I think we need to move on, right?14:27
johnthetubaguydansmith: yes14:27
boris-42dansmith or I should wait Kilo?14:27
boris-42dansmith didn't get14:27
dansmithboris-42: kilo14:27
danpbi think that given this is the first time most of core seems to have heard about this feature  Kilo looks like best option14:27
boris-42dansmith nope that is bad thing14:27
johnthetubaguy#info seems like we need to wait for kilo of os profiles, move discussion to ML14:27
ndipanovbeing pragmatic about this - easy perf profiling is a massive win for all, and I would not like to see it blocked on process14:27
boris-42(*facepalm*)14:27
dansmithdanpb: this has had a huge amount of press, I dunno that it's new to everyone,14:27
boris-42sorry guys14:28
dansmithdanpb: it's just unreviewed right now because of the timing I think14:28
boris-42dansmith danpb guys this things can help you in development14:28
boris-42to safe billions of hours14:28
ndipanovif not even millions :)14:28
bauzasI just discovered osprofiler in global reqs14:28
boris-42on fixing different races, and bugs14:28
johnthetubaguytwo or three weeks back, with an approve oslo spec, then we would probably wave it through14:28
boris-42performance issues and so on14:28
boris-42bauzas yep it is14:28
bauzascan't really see why it needs to be there14:28
boris-42bauzas and it is already in galnce14:28
danpbboris-42: no one is debating that this is a useful feature14:28
boris-42bauzas and today will be in cinder14:28
johnthetubaguyright now, we have so much to get juno out the door, we can't really afford the discussion, which sucks14:28
boris-42danpb yep but I really don't see any reason to block it until Kilo14:29
dansmithjohnthetubaguy: right, that14:29
boris-42danpb can we get FFF for it?14:29
boris-42danpb dansmith I can disable it by default14:29
boris-42danpb dansmith if it makes sense14:29
dansmithboris-42: don't make me come up with a meaning for FFF :P14:29
johnthetubaguyboris-42: please request on the ML, ideally with a nova-spec pointing to the merged solo spec14:29
bauzashaving a dependency disabled by default sounds weird to me...14:29
johnthetubaguyanyways, really must move on...14:29
danpbrequesting FFF is reasonable way to continue the discussion14:29
bauzaswe already have numpy as a painful dep...14:29
johnthetubaguyOpening specs for Kilo...?14:30
boris-42bauzas please don't compare osprofiler with numpy14:30
johnthetubaguybut no approvals till we get the process sorted?14:30
boris-42bauzas osprofiler is 200 lines stuff14:30
ndipanovI do think that it being late for J is realistic - just hate for it to be on a process snag14:30
boris-42bauzas without any deependency14:30
*** esker has quit IRC14:30
*** rushiagr is now known as rushiagr_away14:30
danpbyes please, on the grounds that I think we should require any nova design summit session proposal to have some prior discussions or proposal (whether a spec or a wiki page)14:30
*** esheffield has quit IRC14:30
johnthetubaguydanpb: +114:30
boris-42danpb dansmith bauzas guys okay I'll make some email14:31
johnthetubaguyI think we just let people submit for kilo14:31
johnthetubaguyany objections at this point?14:31
mriedemjohnthetubaguy: does it get sorted out later then with the slots thing?14:31
johnthetubaguyjust to be clear, they might not get reviewed till later14:31
*** esheffield has joined #openstack-meeting-alt14:31
danpbyep, no approvals until we're better on top of Juno work14:31
mriedemwas reading through jogo's k blueprint process patches a bit yesterday,14:31
johnthetubaguymriedem: yeah, no approvals still we decide whats happening for approvals (re slots, etc)14:31
mriedemsounds like there is debate about when a spec is required,14:32
danpband review of specs would be low priority for core team given juno code backlog14:32
mriedembut i guess if people want to write them, that's no skin off reviewers backs if they aren't reviewing them14:32
mriedemright14:32
johnthetubaguymriedem: yeah, we were going to slacken it off a bit14:32
johnthetubaguyright, I have no plans to review specs till after feature freeze at this point, but we could let people submit14:32
johnthetubaguyalso with the warning the template may get updated a little14:33
*** kai has quit IRC14:33
johnthetubaguysounds like we are agreed there… do speak up if not14:33
belliotti'm still for getting rid of specs, i know i'm a minority14:33
johnthetubaguy… next is… Power KVM CI?14:33
mriedemjohnthetubaguy: i think that's old14:34
mriedemfrom last week14:34
johnthetubaguyyeah, I think mikal wanted an update or something14:34
mriedemkrtaylor isn't here14:34
johnthetubaguybut I could be wrong14:34
mriedemi'll bug him in -nova14:34
johnthetubaguynever mind, its probably the wrong time of day14:34
dansmithI haven't been seeing it report,14:34
dansmithso I assume no new news14:34
mriedemit's disabled since last monday14:35
danpbPowerKVM CI seems to be either awol or failing or both14:35
dansmithit's disabled now14:35
dansmithbecause it's broken14:35
*** rcleere has joined #openstack-meeting-alt14:35
johnthetubaguyminesweeper is apparently waking back up now?14:35
dansmithno reason or details, AFAIK14:35
*** rcleere has quit IRC14:35
*** kai has joined #openstack-meeting-alt14:35
johnthetubaguy(needed more hardware I was told)14:35
*** otherwiseguy has joined #openstack-meeting-alt14:35
dansmithjohnthetubaguy: MS seems to be very up and down lately, and tjones has been MIA for most of it14:35
mriedemwell MS was busted due to removing the esxi driver i guess14:35
johnthetubaguydansmith: its certainly been very patchy14:36
mriedemthat is sorted out now after several mini-reverts14:36
johnthetubaguyXenServer CI had some blips, but I think BobBall got those sorted now14:36
dansmithmriedem: it's still not running normally14:36
danpbFYI this has some nice reports on CI status  http://ci-stats.cloudbase.it/14:36
dansmithmriedem: I've had a -2 on a spawn refactor patch for a while14:36
mriedemdansmith: yeah saw that14:36
danpbit is a bit better than what mikal's site reports as it shows the trends of CI over time14:36
johnthetubaguynice14:37
* mriedem bookmarks14:37
johnthetubaguyanyways14:37
johnthetubaguyany other stuff?14:37
*** chellygel has left #openstack-meeting-alt14:37
johnthetubaguyadrian_otto: did you have container stuff?14:37
johnthetubaguyadrian_otto: we don't really do sub-team updates, just keeping it to critical release status stuff or breaking updates now14:38
adrian_ottoyes, I have two questions for the Noca team14:38
adrian_otto*Nova14:38
johnthetubaguycool14:38
adrian_otto#link https://review.openstack.org/114044 Containers Service Spec14:38
adrian_otto1) Is a full API spec desired for a high level spec for a new service?14:38
mriedemjohnthetubaguy: i guess i'll have something if you can come back to me14:38
adrian_ottoIt might be better to agree on the concept and propose the API in a series of commits to the stackforge/containers repo in docstrings so we can more easily iterate on specific implementation of the API.14:38
adrian_ottobecause in this week's team meeting we declared an intent to have an OpenStack specific API, and not just adopt Docker's API.14:39
johnthetubaguyadrian_otto: ah, gotcha, maybe a follow up change on the spec?14:39
adrian_ottoplanning that, but I am looking for conceptual guidance14:39
*** ramishra_ has joined #openstack-meeting-alt14:39
*** _nadya_ has quit IRC14:40
dansmiththe whole api spec is probably too large for being in the containers service spec,right?14:40
adrian_ottoexactly14:40
danpbadrian_otto: i think we view the specs as only needing  high level design - focus on concepts, architecture & psuedo code at most14:40
johnthetubaguyyeah, thats fair14:40
adrian_ottothat would make the spec impossible to review14:40
danpbcertainly don't want detailed code technical design in the spec14:40
dansmithsince this is large and new, perhps just iterate on the spec without the api details, and then have your own spec document in your tree as well14:40
*** dmakogon_ is now known as denis_makogon14:40
dansmithdanpb: I think he's asking because we require api snippets in api-affecting specs for nova14:41
johnthetubaguydanpb: honestly we need to set that expectation better, for APIs we make very detailed requirements at the moment, but yeah14:41
adrian_ottook, thanks. Any opposing viewpoints for us to consider on this point?14:41
*** jecarey has quit IRC14:41
adrian_ottoif not, I'll advance to the second question14:41
adrian_otto#link https://review.openstack.org/115328 Stackforge Repo Spec14:41
johnthetubaguyseems good, do what works best I guess14:41
adrian_otto#link https://review.openstack.org/#/c/115328/2/modules/openstack_project/files/gerrit/acls/stackforge/containers.config Comments on PTL for Containers Service14:41
adrian_otto2) Should there be a separate PTL for a new compute program project, or should it be the Nova PTL?14:41
*** ramishra has quit IRC14:42
adrian_ottowe don't yet have a group called compute-ptl14:42
dansmithI think while it's in stackforge, you're totally separate, right?14:42
dansmithI think that's what we agreed on14:42
johnthetubaguyI think we said inside the "compute" program eventually14:42
dansmithso that you can iterate quickly14:42
johnthetubaguyyeah14:42
adrian_ottowell, our intent is for this to be a compute program project14:42
*** satish_ has joined #openstack-meeting-alt14:42
adrian_ottoand I want to properly signal that14:42
dansmithright, so I don't think it matters for the stackforge bootstrapping14:42
adrian_ottoso one thing I could do is make a containers-ptl group, and put a note in the commit message explaining that choice14:43
johnthetubaguyyeah, maybe just say its the nova one, but have your own core list, for now?14:43
danpbthe intent is for this to become part of Nova eventually right14:43
adrian_ottojohnthetubaguy: ok, that would work14:43
dansmithdanpb: part of compute14:43
adrian_ottodanpb: not part of nova, but part of the compute program that Nova belongs to14:43
danpbdansmith: what's the distinction there ?  forever having a  separate core team & ptl ?14:44
johnthetubaguydansmith: +1 in compute program, not in nova tree14:44
adrian_ottoso it will belong to the PTL, who currently only controls Nova14:44
dansmithdanpb: no, not necessarily core14:44
adrian_ottobut will have it's own core group14:44
johnthetubaguyadrian_otto: sounds fine for stackforge14:44
dansmithdanpb: the distinction is two separate projects that share the same PTL and general mission statement (or whatever it's called), but could have different core teams14:44
adrian_ottothe PTL question really only matters for tagging releases14:44
danpbok14:45
adrian_ottoso I honestly don't care who carries that responsibility14:45
dansmithadrian_otto: I don't think we do either, until you're formally part of the program :)14:45
adrian_ottoit will not impeede iterative progress14:45
dansmith(IMHO)14:45
johnthetubaguydansmith: +114:45
bauzaswell, you'll have to follow the Nova release cycle, even as a Stackforge project tho14:45
adrian_ottodansmith: good, thanks14:45
*** tonytan4ever has joined #openstack-meeting-alt14:45
johnthetubaguyadrian_otto: you can always change it I guess14:45
dansmithadrian_otto: if one option is less paperwork than the other, then I'd choose that :)14:45
adrian_ottobauzas: yes!14:45
adrian_otto:-)14:46
bauzasadrian_otto: which is, from my understanding, the first time I'm seeing that14:46
*** satish has quit IRC14:46
johnthetubaguyadrian_otto: cool, sounds like we answered everything now?14:46
adrian_ottook, thanks, those are the two open questions we had. We are iterating on design, and starting on API design work now.14:46
bauzasadrian_otto: because stackforge projects are not possibly following openstack release cycle14:46
johnthetubaguycool14:46
johnthetubaguymriedem: did you have something?14:46
mriedemjohnthetubaguy: yeah on the enforce unique instance uuids patch,14:46
johnthetubaguyah14:46
mriedemhttps://review.openstack.org/#/c/97946/14:46
mriedemt-h actually has some data sets with null instance uuids14:47
bauzasadrian_otto: ping me when you're free about containers vs. gantt, interested by this14:47
mriedemso if you're on a gerrit dashboard and see that review, it has a -114:47
mriedemb/c of t-h14:47
dansmithmriedem: yeah, mikal pointed that out right?14:47
adrian_ottobauzas: yes sir.14:47
mriedemdansmith: yeah14:47
dansmithmriedem: I think he said he was going to figure out where those came from if possible14:47
mriedemjhesketh also commented in the change14:47
mriedemjhesketh basically said he's going to leave it there until the change is merged14:47
mriedemanyway,14:48
mriedemmy question is if that's fine - it's going to detract from reviews, but it's low priority anyway,14:48
mriedemi figured i'd just update the commit message pointing it out14:48
mriedemso i don't have to answer the question 10 times14:48
dansmithyeah, seems fine14:48
johnthetubaguycool14:48
mriedemplus, if that does ever merge, t-h is going to be f'ed until they purge those rows :)14:48
mriedemalright, that's it14:49
johnthetubaguycool14:49
*** tobybot11 has quit IRC14:49
johnthetubaguysounds like that everything, and we are done, any more?14:49
* danpb has an item14:49
johnthetubaguydanpb: fire away14:49
danpbwhat is our guideline for reviewing nova client code changes wrt v3 api14:50
dansmith-2 I think14:50
danpbare we still caring about maintaining the v3 client classes14:50
*** kai has quit IRC14:50
marios14:50
johnthetubaguyhmm, interesting, −2 I guess14:50
danpbbecause it is really tedious reviewing identical code changes to both the v1_1 and v3/ directories14:50
*** tobybot11 has joined #openstack-meeting-alt14:50
dansmithso no new code for those things, I think,14:50
danpbso should we discourage people from changing v3/ directory at this point or not ?14:50
johnthetubaguyyeah, I thought we decided v3 was never going to get exposed as v3, so that should never get merged14:51
dansmithbut removing them is kinda breaking the library-ness of the client14:51
*** xyang1 has joined #openstack-meeting-alt14:51
johnthetubaguydansmith: oh, what did we add?14:51
dansmithbut they won't work past a point, so we should probably make the v3 module in the client raise some exception if you try to use them14:51
dansmithjohnthetubaguy: what do you mean?14:51
johnthetubaguydansmith: yeah, and bump the major version I guess14:51
johnthetubaguydansmith: sorry, its me being slow, didn't think we had any v3 in the client right now14:52
*** ramishra_ has quit IRC14:52
dansmithjohnthetubaguy: we do, don't we? wasn't that a requirement for getting as close as we were to having v3?14:52
*** vponomaryov has joined #openstack-meeting-alt14:52
*** mestery has quit IRC14:52
dansmithjohnthetubaguy: https://github.com/openstack/python-novaclient/tree/master/novaclient/v314:52
vishyminor request: the last three paches for the multiple networks spec are waiting on a single core review on this patch: https://review.openstack.org/#/c/95262/14:52
danpbjohnthetubaguy: well python-novaclient has  novaclient/v3/*.py14:52
johnthetubaguydansmith: yeah, its coming back to me, was just looking there14:53
dansmithyeah, it's really unfortunate,14:53
dansmithbut I think we need to basically replace all those with stubs that fail long-term14:53
dansmithtechnically nobody should be using them, but...14:53
danpband the v3 code is pretty badly out of sync with the v1 dir14:53
dansmithdanpb: yeah14:53
johnthetubaguydansmith: +114:53
johnthetubaguyseems like we should do that ASAP before more people start using that stuff14:53
dansmithdanpb: the v3 patches going into nova that are moving it back to v2.1 are okay to approve of course, but any actual v3 patches should be -2d in nova and novaclient, IMHO14:54
danpbso taking something like this https://review.openstack.org/#/c/115246/    we should -2 that change ?14:54
*** rraja has joined #openstack-meeting-alt14:54
dansmithjohnthetubaguy: maybe, I'm not sure what our messaging has been on that, and technically the client code can be used against, say icehouse14:54
johnthetubaguydansmith: we have a load of jsonscheme stuff up for review, which is basically the crux of v2.1 I supose14:54
dansmithjohnthetubaguy: well, it's not just jsonschema stuff of course14:55
danpbor this one which i approved earlier  https://review.openstack.org/#/c/112130/   we should have made them kill the file changes to v3 ?14:55
dansmithdanpb: yes, -2 I think14:55
*** rushil has joined #openstack-meeting-alt14:55
dansmithdanpb: yes14:55
*** cknight has joined #openstack-meeting-alt14:55
johnthetubaguydansmith: agreed14:55
*** bswartz has joined #openstack-meeting-alt14:56
danpbwe should probably have something in the wiki we note this, or a post to the mailing list to alert contributors that changes to v3 are not wanted anymore14:56
*** bswartz has quit IRC14:56
dansmithdanpb: maybe we wait for the v3 summary from the midcycle,14:56
danpbsomething we can just post a link to in reviews so we don't have to explain it over & over again14:56
johnthetubaguydanpb: yeah, we haven't been very clear on that, we need a nova-drivers meeting soon, to thrash out these kinds of things14:56
dansmithand then send out something on that with the policy impacts?14:56
*** padkrish has joined #openstack-meeting-alt14:56
*** carl_baldwin has joined #openstack-meeting-alt14:56
*** jjmb has quit IRC14:56
danpbdansmith: sounds good14:57
johnthetubaguydansmith: oh, thats a good idea, like follow up with policy impacts code reviews14:57
dansmithI think that would be the  most efficient14:57
johnthetubaguyawesome, so we are basically out of time14:57
johnthetubaguydansmith: +114:57
johnthetubaguybut I found most of that useful, feeback always welcome as we try make these meeting more useful14:57
johnthetubaguyany more that people want to discuss?14:57
PhilDSometimes you have to change the existign V3 files and tests though.   For exampelethe change I have to add two new quotas, they get picked up in the V3 API anyway (and we don't have extensiosn to hide them) - so I assume in that case the V£ changes are stil OK?14:57
dansmithPhilD: I guess only if it's required to pass tests14:58
dansmithbut we're not running tempest on v3 anymore, for example14:58
dansmithso it would just be unit tests I think14:58
*** coolsvap has quit IRC14:58
*** _nadya_ has joined #openstack-meeting-alt14:58
PhilDYeah - its unit test stuff14:58
*** yjiang5 has quit IRC14:59
johnthetubaguyhmm, I guess its going drift more out of sync now, but thats life14:59
johnthetubaguyanyways, time is up14:59
johnthetubaguythanks all14:59
johnthetubaguy#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Thu Aug 21 14:59:30 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova/2014/nova.2014-08-21-14.01.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova/2014/nova.2014-08-21-14.01.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/nova/2014/nova.2014-08-21-14.01.log.html14:59
*** PhilD has left #openstack-meeting-alt14:59
*** mriedem has left #openstack-meeting-alt15:00
*** chuckC_ has joined #openstack-meeting-alt15:00
*** bswartz has joined #openstack-meeting-alt15:00
*** jmontemayor has joined #openstack-meeting-alt15:00
*** warpc_ has quit IRC15:00
bswartz#startmeeting manila15:00
openstackMeeting started Thu Aug 21 15:00:57 2014 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: manila)"15:01
openstackThe meeting name has been set to 'manila'15:01
cknightHi15:01
*** tdruiva has quit IRC15:01
tbarronhi15:01
*** rcleere has joined #openstack-meeting-alt15:01
ameadeo/15:01
xyang1hi15:01
bswartzgood morning/good afternoon/good evening15:01
deepakcshi15:01
vponomaryovhi15:01
rrajahi15:01
*** scottda has joined #openstack-meeting-alt15:01
bswartzwe do have an agend15:01
*** gokrokve_ has joined #openstack-meeting-alt15:01
*** adrian_otto has quit IRC15:01
bswartzbut I'll start with the incubation stuff15:01
bswartzsince I'm getting a bunch of questions about that15:01
*** tdruiva has joined #openstack-meeting-alt15:01
scottdahi15:01
bswartz#topic incubation15:01
*** dustins has joined #openstack-meeting-alt15:01
*** openstack changes topic to "incubation (Meeting topic: manila)"15:01
rushilhi15:01
*** nilesbh has joined #openstack-meeting-alt15:02
*** adrian_otto has joined #openstack-meeting-alt15:02
toabctlhi15:02
vvechkanovhi15:02
*** adrian_otto has quit IRC15:02
*** nileshb has joined #openstack-meeting-alt15:02
dustinso/15:02
bswartzso the TC is mostly positive on it15:02
bswartzbut the vote hasn't completed yet15:02
bswartzfor your reading pleasure:15:02
*** coolsvap has joined #openstack-meeting-alt15:02
bswartz#link http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-08-19-20.02.log.html15:02
bswartzThere is a thread on the ML which explains some of the TC member's hesitance:15:03
bswartz#link http://lists.openstack.org/pipermail/openstack-dev/2014-August/041929.html15:03
*** gondoi is now known as zz_gondoi15:03
bswartzthe actual votes are here:15:03
bswartz#link https://review.openstack.org/#/c/111149/15:03
bswartz#link https://review.openstack.org/#/c/113583/15:04
*** rudrarugge has joined #openstack-meeting-alt15:04
bswartzany questions about all that?15:04
*** padkrish has quit IRC15:04
*** gokrokve_ has quit IRC15:04
xyang1bswartz: how many +1 do we need?15:04
bswartz715:04
bswartzaccording to ttx15:04
deepakcsbswartz, <ttx> 3. The driver/vendor aspect (avoid another Neutron with no first-party driver really viable, getting swamped by driver requests, relationship with glusterfs)15:04
xyang1bswartz: so just missing 115:05
*** gokrokve has quit IRC15:05
deepakcsbswartz, ^^ didn't understand that..15:05
*** padkrish has joined #openstack-meeting-alt15:05
*** gokrokve_ has joined #openstack-meeting-alt15:05
xyang1bswartz: is the -1 blocking?15:05
*** mikedillion has joined #openstack-meeting-alt15:05
bswartzdeepakcs: so many people consider neutron a disaster of a project15:05
vponomaryovxyang1: I guess no15:05
bswartzbecause it's all vendor driven and there is a lack of a software-only implementation supported by the neutron core team15:05
ttxbswartz: You actually need at least 4 YES and more YES than NO, but 7 gives you majority and immediate approval15:05
vponomaryovxyang1: need 7 yes15:05
bswartzmanila doesn't have that problem, because we have a very highly functional generic driver that we support15:06
deepakcsbswartz, relnship with glusterfs.. what is that ? :)15:06
ttxerr.. 5 YES15:06
bswartzttx: thanks for clarification15:06
ttx(ref: http://git.openstack.org/cgit/openstack/governance/tree/reference/charter.rst#n79)15:06
*** ruebenramirez has joined #openstack-meeting-alt15:06
bswartzdeepakcs:  actually I didn't understand the comment about glusterfs15:07
*** dkehn_ has joined #openstack-meeting-alt15:07
toabctlbswartz: so what's the solution for manila to avoid the Neutron scenario? good support for the current generic driver?15:07
bswartzsince we have ttx here, can he explain what he meant?15:07
ttxbswartz: on tha (3) point,15:07
bswartztoabctl: yes that's exactly the plan15:08
*** zz_gondoi is now known as gondoi15:08
bswartzwe have plans to improve the generic driver in terms of scalability and HA15:08
ttxThat's a catch-all for the potential that Manila becomes another Neutron or Cinder15:08
bswartzand also work on any issues with its performance in general (as much as can be done with a software-only driver)15:08
*** marun has joined #openstack-meeting-alt15:08
ameade:q15:09
ameade>.<15:09
ttxbswartz: i.e. you receiveing hate mail from vendors you displease15:09
bswartzttx: I feel that cinder and neutron have gone very different directions culturally15:09
xyang1ttx: what the problem with Cinder?  curious15:09
*** dkehnx has quit IRC15:09
*** dkehn has quit IRC15:09
ttxthere were 3 concerns I lumped into that catch-all15:09
bswartzmy hope is to follow the path of cinder15:09
bswartzno neutron15:09
*** kai has joined #openstack-meeting-alt15:09
bswartzs/no/not/15:10
ttxA. make sure you have an open source solution that works extremely well15:10
*** yamahata has joined #openstack-meeting-alt15:10
ttxrather than a second-class citizen15:10
ttxB. Try to keep the driver requests under control15:10
nileshbopensource meaning - non-vendor-specific?15:10
ttxso that you don't get swamped under them15:10
bswartzttx: do you characterize glusterfs as a second open source solution, or a vendor specific driver?15:10
ttxnileshb: meaning open sourced.15:11
ttxbswartz: glusterfs is open source.15:11
bswartzokay I think we're on the same page then15:11
*** pnavarro has quit IRC15:11
*** pkoniszewski has quit IRC15:11
*** dkehn has joined #openstack-meeting-alt15:11
*** ijw has joined #openstack-meeting-alt15:11
ttxC. clarify the relationship with glusterfs, which I think we just discussed :)15:11
bswartzok15:12
*** sicarie has joined #openstack-meeting-alt15:12
ttxjust trying to learn from experience :)15:12
bswartzany more questions on incubation or should I move on to the agenda?15:12
*** danpb has left #openstack-meeting-alt15:12
xyang1ttx: when will we get verdict15:12
toabctlso is glusterfs the main driver or the current generic driver?15:13
bswartzfwiw, I'm aware of several vendor-specific drivers being worked on, and I'm excited to see them land because I think the existing of multiple drivers will prove our architecture is correct15:13
bswartztoabctl: generic is the one the core team maintains and recommends15:13
ttxxyang1: voting is asynchronous now. If we don't get a majority at next meeting, i'll call for final vote, which triggers the "5+YES and 4-NO" rule I mentioned above15:13
bswartzso far the glusterfs work has been done exclusively by redhat, and we want to see it succeed15:14
toabctlbswartz: ok. thx15:14
*** tdruiva has quit IRC15:14
*** baoli has joined #openstack-meeting-alt15:14
ttxso worst case scenario, middle of next week15:14
xyang1ttx: thanks15:14
*** tuvenen has joined #openstack-meeting-alt15:15
*** tdruiva_ has joined #openstack-meeting-alt15:15
bswartzalright let's move on15:15
bswartz#agenda https://wiki.openstack.org/wiki/Manila/Meetings15:15
*** ijw has quit IRC15:15
*** cjellick has joined #openstack-meeting-alt15:16
bswartz#topic dev status15:16
*** openstack changes topic to "dev status (Meeting topic: manila)"15:16
vponomaryovdev status:15:16
vponomaryov1) LVM driver was removed. Generic driver is default now.15:16
vponomaryov2) 'sid' share access rules were renamed to 'user'15:16
vponomaryov3) Removing dependency of NetApp 7-mode driver for NetApp Cmode driver15:16
vponomaryovbp: #link https://blueprints.launchpad.net/manila/+spec/remove-netapp-7mode-driver15:16
vponomaryovgerrit: #link https://review.openstack.org/11359615:16
vponomaryovstatus: ready for review15:16
vponomaryov4) replacement of sqlalchemy-migrate with alembic15:16
vponomaryovbp: #link https://blueprints.launchpad.net/manila/+spec/alembic-instead-of-sqlalchemy-migrate15:16
vponomaryovgerrit: #link https://review.openstack.org/11095915:16
vponomaryovstatus: ready for review15:16
vponomaryov5) Add support to use default network by multitenant drivers15:17
vponomaryovbp: #link https://blueprints.launchpad.net/manila/+spec/default-network-for-multitenant-drivers15:17
vponomaryovstatus: work in progress15:17
vponomaryovthat's the main15:17
bswartzty vponomaryov15:17
bswartzwe may want to discuss the last one15:17
bswartzwe disucussed it at length earlier this week15:17
bswartzprivately15:17
bswartzoh wait that's the next agenda item15:18
bswartzdoh!15:18
*** tdruiva_ has quit IRC15:18
bswartzany questions on the rest of this stuff15:18
*** catherine_r has joined #openstack-meeting-alt15:18
*** betsy has joined #openstack-meeting-alt15:18
*** baohua_ has joined #openstack-meeting-alt15:18
*** sambork has joined #openstack-meeting-alt15:18
toabctlwhy is the 7-mode driver removed ?15:18
*** baoli has quit IRC15:19
*** dkehn_ is now known as dkehnx15:19
bswartztoabctl: that was the original driver we used as a POC for the manila concept like 2 years ago15:19
rushiltoabctl: according to my understanding it was poorly written.15:19
bswartzit never had multitenant support, and NetApp didn't want to invest in adding multitenant support because netapp had mutlitenant support in the c-mode driver15:19
*** vjardin_ has quit IRC15:19
bswartzrushil: not poorly written, just lacking features15:20
bswartzanyways it served its purpose and we didn't need it anymore15:20
*** bdpayne has joined #openstack-meeting-alt15:20
bswartzsimilar to the 'LVM' driver15:20
rushilbswartz: It can be brought back though, right?15:21
bswartzit's in the git history if someone wants to resurrect it and implement all the missing stuff15:21
toabctlbswartz: but then ONTAP running in 7-mode is no longer supported, right?15:21
*** baohua has quit IRC15:21
bswartztoabctl: correct15:21
toabctlbswartz: ok. thx for clarification.15:22
*** catherine_r has left #openstack-meeting-alt15:22
bswartzso far netapp hasn't expressed an interest in supporting 7mode under manila -- that may change15:22
bswartzokay let's move on15:22
bswartz#topic Discuss blueprint "Add support to use default network by multitenant driver"15:22
*** openstack changes topic to "Discuss blueprint "Add support to use default network by multitenant driver" (Meeting topic: manila)"15:23
*** ramishra has joined #openstack-meeting-alt15:23
bswartz#link https://blueprints.launchpad.net/manila/+spec/default-network-for-multitenant-drivers15:23
*** rwsu has quit IRC15:23
vvechkanovOk, let's discuss blueprint "creating default share network for generic driver".15:23
bswartzvvechkanov: you want to start this one?15:23
*** cjellick has quit IRC15:23
vvechkanovbswarts, yes I can/15:23
*** jprovazn has quit IRC15:23
*** cjellick has joined #openstack-meeting-alt15:24
*** lisaclark1 has joined #openstack-meeting-alt15:24
vvechkanovNow blueprint looks this way:15:24
vvechkanovwe will create default share_network in the service tenant.15:24
vvechkanovThis share network can be created by admin or will be created by manila automatically. This share network will be used for creating shares in any tenant if shared network is not specified in the request.15:25
vvechkanov15:25
vvechkanovut this plan have some problems. User, working in tenant will have shares, which will be created using this default shared network. But user has not acces to service tenant and can't see this shared network. So user will have share, but will not have possibility to look at some options which  network it works.15:25
*** mtanino has joined #openstack-meeting-alt15:26
vvechkanovMay somebody have ideas what can be done to avoid this problem? And is it a big problem that user will not see some configuration options of his hsare?15:26
deepakcsvvechkanov, just confirming.. this idea of using share_network (if not provided) is only applicable to generic driver, rite ?15:26
bswartzvvechkanov: so my feeling on this is that the "default" network shouldn't have any settings that users need to be aware of15:26
*** arnaud__ has joined #openstack-meeting-alt15:26
bswartzit's the admins responsibility to configure it such that it works for all tenants15:27
nileshbwill the default network once created (automatically or by admin) be immutable?15:27
*** gokrokve_ has quit IRC15:27
bswartznileshb: that15:27
vvechkanovdeepakcs, No i'm very sorry it's my mistake. It will be for all drivers.15:27
vvechkanovI jsut forgot to rename blueprint(15:27
bswartznileshb: that's debatable15:27
*** ramishra has quit IRC15:27
*** lisaclark1 has quit IRC15:27
*** gokrokve has joined #openstack-meeting-alt15:27
scottdaI agree with bswartz. Users shouldn't need access to the network.15:27
bswartzthe default network will apply to all drivers15:28
scottdafor configuration, etc15:28
*** esker has joined #openstack-meeting-alt15:28
nileshbso if the admin deletes it and someone creates a share without specifying net-id .. default n/w is already gone15:28
bswartzand the non-multitenant-supporting drivers will use it exclusively15:28
deepakcsvvechkanov, then i am bit confused, for cases where the backend supports multi-tenancy, why would share-network be needed to be enforced ?15:28
vvechkanovnileshb, default network will be created again in this case.15:28
nileshbok .. then the original one .. no more exists .. which might have been used to create some of the previous shares15:29
vvechkanovdeepakcs, this idea works good whan we have flat netwrok in neutron15:29
bswartzso deepakcs: consider the case of someone using the Netapp driver in a flat network environment15:29
bswartzthe netapp driver still needs to create a "share server" (vserver) and we need network info to do that15:30
bswartzthe same is true of the generic driver15:30
*** kevinconway has joined #openstack-meeting-alt15:30
nileshbprobably admin should not be allowed to delete a default n/w .. if it is 'in-use'15:30
*** lisaclark1 has joined #openstack-meeting-alt15:30
bswartzwe need to create a nova VM and it needs to live on a network15:30
*** ruebenramirez has quit IRC15:30
rushilvvechkanov: But what if scenario is when we do not have a flat network?15:30
vvechkanovnileshb, if I understand you correctly... Administrator can't delete share networks if there are shares using it.15:30
vponomaryovnileshb: it would be strange, if admin deletes usable things. In this case he should port shares to another server/network15:31
nileshbvvechkanov: exactly15:31
*** MorAle has joined #openstack-meeting-alt15:31
bswartzif we don't have a flat network, then the default share network may be inaccessible to tenants -- in which case they shoudn't use it15:31
vvechkanovrushil, than nothing changes. User can't create shares without specifing share netwrok15:31
*** greghaynes has left #openstack-meeting-alt15:31
bswartzin fact we may want to consider allowing the admin to explicitly disable it15:31
*** gokrokve has quit IRC15:32
*** otherwiseguy has quit IRC15:32
bswartzI'm feeling pretty strongly that the default SHOULD be immutable as long as its in use15:32
*** otherwiseguy has joined #openstack-meeting-alt15:32
nileshbbswartz: +115:32
bswartzattempts to modify it should fail unless all shares using it are deleted15:32
bswartzthat includes deleting it15:32
*** lisaclark1 has quit IRC15:33
bswartzdeleting the default share network, that is15:33
*** lisaclark1 has joined #openstack-meeting-alt15:33
nileshbdeleting share looks tough15:33
bswartzwhat do you mean?15:33
nileshbdo we allow detach n/w?15:33
vponomaryovnileshb:15:33
bswartzdeleting a share is a basic operation15:33
nileshband reattach those to new n/w15:33
vponomaryovnileshb: no, there are no functionality yet, if you mean migration of shres15:34
vponomaryovs/shres/shares/15:34
nileshbok15:34
bswartzthe design of manila right now requires that shares have a share network and that association can never change15:35
nileshbok got it15:35
*** timcl has joined #openstack-meeting-alt15:35
bswartzit wouldn't be impossibe to change that but it would be really hard15:35
bswartzthe theory is that most tenants will have exactly one share network that they use and this won't be a big deal15:35
bswartztenant with special needs may create more than 115:36
*** chandankumar has quit IRC15:36
bswartzno 2 tenants can share a share network (sorry for overloaded term)15:37
bswartzexcept for the default one15:37
deepakcsbswartz, a dumb Q (maybe)...15:37
xyang1bswartz: why this restriction?15:37
deepakcsbswartz, Do we still need a share-network if the backend manages its own multi-tenancy and User wants the instance to directly connect to backend15:38
deepakcsbswartz, for eg: In case of glusterfs native protocol15:38
bswartzxyang1: it simplifies implementation -- and we never identified any use case where tenants would need to share a share network15:38
*** bdpayne has quit IRC15:38
vponomaryovshare-network belongs to tenant, but it depends on network itself, does two tenants has crossing access or not15:38
vponomaryovdeepakcs: do not forget about security services15:39
bswartzif there is a legitimate reason to have a single share accessed by 2 or more tenants, than can be achieved with virtual routes between those 2 tenant's networks15:39
*** rwsu has joined #openstack-meeting-alt15:39
bswartzbut the share is still owned by 1 tenant and uses his security settings and his network settings15:40
xyang1bswartz: I don't have a specific use case, just thinking about the possibilities15:40
*** baohua_ has quit IRC15:40
bswartzxyang1: we thought about is an discussed it at length several months ago because people asked the same question15:41
deepakcsvponomaryov, not cler to me.. why do  I need a share-network in case of native glusterfs protocol15:41
*** jaypipes has quit IRC15:41
vponomaryovdeepakcs: in case of glusterFS - no15:41
vponomaryovdeepakcs: the concept is required - yes15:41
bswartzI'm comfortable with the decision we arrived at, but we can always revisit stuff if someone has a new use case we didn't consider15:41
deepakcsvponomaryov, ok, but the above discussion said share-network will be created if not supplied15:41
vponomaryovdeepakcs: because it is used for other stuff by other drivers15:41
deepakcsvponomaryov, so not clear if that affects my instance -> glusterfs server path/networking in any way15:42
vponomaryov deepakcs: driver decides use it or not15:42
vponomaryovno15:42
deepakcsvponomaryov, ok, thanks15:42
vponomaryovbecause driver makes decision15:42
deepakcsvponomaryov, ok15:42
vponomaryov=)15:42
bswartzdeepakcs: we need to discuss networking and glusterfs more because I have some ideas that may not match reality15:42
deepakcsbswartz, sure, fire a mail or we can talk on IRC15:43
deepakcsbswartz, due to TZ diff, mail is better15:43
bswartzor maybe we just have some misunderstanding15:43
*** prmtl has joined #openstack-meeting-alt15:43
bswartzmy top priority is to make sure that the generic driver works well in both multitenant and single tenant environments, and that the setup for both is straighforward and easy to understand15:44
bswartzerrr15:44
bswartzI meant flat network not single tenant15:44
*** tuvenen has quit IRC15:44
bswartzI think of flat networks as conceptually single tenant, even though many people use multitenant with flat network15:44
vponomaryovbswartz: actually it works15:44
*** prmtl has quit IRC15:45
vponomaryovbswartz: but only from neutron15:45
*** prmtl has joined #openstack-meeting-alt15:45
bswartzvponomaryov: I know it works -- I just want to make sure it's really easy and straightforward15:45
*** jecarey has joined #openstack-meeting-alt15:45
*** doude has quit IRC15:45
bswartzthe fact that some developers aren't clear on this means we haven't done a good job of communicating how each type of environment should be setup15:46
bswartzwe probably need a wiki that goes into both types of configs15:46
rushilbswartz: +115:46
bswartzthat's another topic though15:46
*** otherwiseguy has quit IRC15:47
*** holser has joined #openstack-meeting-alt15:47
bswartzokay this is vvechkanov's topic though and we've gotten way off track15:47
bswartzvvechkanov: are you clear on what the next step should be?15:48
bswartzor do we need to summarize?15:48
*** adrian_otto has joined #openstack-meeting-alt15:48
vvechkanovYes, as I understand this idea looks good.15:48
bswartzokay15:48
*** bobf has joined #openstack-meeting-alt15:48
*** yamahata has quit IRC15:48
vvechkanovSo I'll provid commit on gerrit and we will look at it, and may be discuus in comments15:49
bswartzokay15:49
bswartzI always feel better debating code rather than abstract ideas in blueprints15:49
*** dgenin has quit IRC15:49
*** denis_makogon has quit IRC15:50
bswartzvponomaryov: let's plan on setting aside some time soon to improve our wiki docs for how to setup both flat and vlan-based networks (perhaps other types too)15:50
*** gondoi is now known as zz_gondoi15:50
*** arnaud__ has quit IRC15:50
*** tatyana has joined #openstack-meeting-alt15:50
bswartzand making sure those docs cover the default network stuff when its done15:50
*** zslot has joined #openstack-meeting-alt15:51
bswartz#topic open discussion15:51
*** openstack changes topic to "open discussion (Meeting topic: manila)"15:51
*** msemenov has joined #openstack-meeting-alt15:51
bswartzokay 9 minutes left -- anyone have another topic to discuss?15:51
nileshbLast week I have submitted GPFS driver code for review15:51
nileshbwhich includes NFS Ganesha support with the ganesha utils15:52
nileshbhttps://review.openstack.org/#/c/114311/15:52
bswartzI'm going to be on vacation at the beach next week -- it's not clear if I'm going to miss this meeting or not, but if I have to miss I'll find someone to run it in my absence15:52
deepakcsbswartz, and I submiited cert-based access type WIP for review (https://review.openstack.org/#/c/114736/). Looking fwd for comments.15:52
nileshbDriver functionality is complete .. it is in WIP state since I am yet to submit unit tests for it15:52
bswartzI'm hoping I'll be available15:52
bswartznileshb: awesome!15:53
*** julienvey has quit IRC15:53
bswartznileshb: I saw it but haven't reviewed it yet15:53
xyang1We submitted VNX driver too: https://review.openstack.org/#/c/115188/15:53
bswartzxyang1: I saw a few submissions15:53
nileshbwe believe the ganesha utils can be enhanced further and can become part of core manila project .. currently those reside under ibm/ dir15:54
*** vkramskikh has joined #openstack-meeting-alt15:54
bswartzjenkins seems unhappy with both15:54
*** zz_gondoi is now known as gondoi15:54
*** jaypipes has joined #openstack-meeting-alt15:54
xyang1xyang1: This is the base driver: https://review.openstack.org/#/c/115037/, VNX driver is the plugin to the base15:54
nileshbthere seems to be some jenkins issue .. not specific to driver code15:54
bswartzare the failures easy to fix?15:54
xyang1bswartz: I couldn't repro the jenkins errors on my setup15:54
bswartzokay we may need to investigate15:54
*** juzuluag has quit IRC15:55
vponomaryovbswartz: ше шы шыыгу Ш ьутешщтув нуыеуквфн15:55
*** padkrish has quit IRC15:55
vponomaryovbswartz: it is issue I mentioned yesterday15:55
bswartzvponomaryov: english?15:55
xyang1vponomaryov: ?15:55
vponomaryovsorry =)15:55
*** ikalnitsky has joined #openstack-meeting-alt15:55
bswartzvponomaryov: I wasn't following the discussion closely enough yesterday15:56
*** jchapman has joined #openstack-meeting-alt15:56
bswartzwhat issue?15:56
xyang1vponomaryov: you have an idea why we hit those errors?15:56
vponomaryovxyang1: dead dependency, it is fixed already15:56
bswartzoh that one15:56
bswartzis the fix merged?15:56
vponomaryovxyang1:just need rerun jobs15:56
*** niclem has joined #openstack-meeting-alt15:56
bswartzrecheck no bug?15:56
vponomaryov"recheck"15:56
xyang1vponomaryov: do we need rebase?15:56
xyang1ok, will try that15:57
bswartzk excellent15:57
nileshbok thanks15:57
*** lukego has joined #openstack-meeting-alt15:57
bswartzso 1 last thing15:57
bswartzJ-3 is coming soon15:57
*** cloudon1 has joined #openstack-meeting-alt15:57
bswartzI'd like to get these drivers reviewed and merged if possible15:58
*** mikedillion has quit IRC15:58
*** ijw has joined #openstack-meeting-alt15:58
*** tzn has joined #openstack-meeting-alt15:58
bswartzso Juno can claim multivendor support in addition to the open source drivers15:58
*** otherwiseguy has joined #openstack-meeting-alt15:59
bswartzlet's prioritize reviews until the J-3 cut date15:59
deepakcsbswartz, and support for new access type too (hpefully) ;-)15:59
*** gyee_ has joined #openstack-meeting-alt15:59
*** adrian-hoban has joined #openstack-meeting-alt15:59
*** e0ne has quit IRC15:59
*** kebray has joined #openstack-meeting-alt15:59
vponomaryov bswartz: do you remember date itself?15:59
nileshb4th Sept?15:59
xyang1bswartz: 9/4?15:59
*** asyriy has joined #openstack-meeting-alt15:59
bswartzdeepakcs: it needs to be complete and mergable soon15:59
*** dilyin has joined #openstack-meeting-alt15:59
*** evgeniyl has joined #openstack-meeting-alt15:59
bswartzso we can do the reviews and get it done15:59
*** mihgen has joined #openstack-meeting-alt16:00
*** mikedillion has joined #openstack-meeting-alt16:00
deepakcsbswartz, given that most of the trust setup is out of band, there isnt much to do in manila..16:00
*** dmahony has joined #openstack-meeting-alt16:00
mihgenhi folks16:00
deepakcsbswartz, I would love to hear from you and others so that i can follow up and help get it merged soon16:00
bswartzif it's not merged by 9/3 then it will need an exception16:00
*** pczesno has joined #openstack-meeting-alt16:00
*** timcl has left #openstack-meeting-alt16:00
*** padkrish has joined #openstack-meeting-alt16:00
bswartzbecause 9/4 will be the branch date16:00
deepakcsbswartz, yeah.16:01
*** vjardin_ has joined #openstack-meeting-alt16:01
bswartzokay we're past time16:01
bswartzthank all16:01
mihgenany fuelers around?16:01
deepakcsbye16:01
bswartzthanks*16:01
xyang1thanks16:01
cknightbye16:01
bswartz#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
openstackMeeting ended Thu Aug 21 16:01:30 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-08-21-15.00.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-08-21-15.00.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-08-21-15.00.log.html16:01
*** rushil has left #openstack-meeting-alt16:01
*** nileshb has quit IRC16:01
*** rraja has quit IRC16:01
christopheraedoHello!16:01
evgeniylHi16:01
*** pczesno has left #openstack-meeting-alt16:01
mihgen#startmeeting fuel16:01
openstackMeeting started Thu Aug 21 16:01:54 2014 UTC and is due to finish in 60 minutes.  The chair is mihgen. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
*** sarob has quit IRC16:01
tatyanahi16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
akislitskyhi16:01
meow-noferhi16:01
*** openstack changes topic to " (Meeting topic: fuel)"16:01
*** jchapman has left #openstack-meeting-alt16:01
openstackThe meeting name has been set to 'fuel'16:01
*** angdraug has joined #openstack-meeting-alt16:02
mihgenhey16:02
mihgentoday vkozhukalov is on vacation so I have to run all these commands )16:02
*** lukego has left #openstack-meeting-alt16:02
*** amnk has joined #openstack-meeting-alt16:02
*** dpyzhov has joined #openstack-meeting-alt16:02
mihgenwho else is here?16:02
dpyzhovhi16:02
angdraugo/16:02
rmoehi16:02
samborkhhi16:02
ikalnitskyo/16:02
christopheraedohi16:02
* dilyin here16:02
msemenovhi16:02
*** scottda has left #openstack-meeting-alt16:02
*** deepakcs has quit IRC16:02
mihgengood16:02
*** cloudon1 has left #openstack-meeting-alt16:03
asyriyhi16:03
vkramskikhhi16:03
*** adrian-hoban has quit IRC16:03
mihgenlet's go over agenda16:03
mihgen#link https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda16:03
*** catherine_r has joined #openstack-meeting-alt16:03
agordeevhi16:03
mihgen#topic 5.1 release status (Fuel, mos-openstack, mos-linux)16:03
*** openstack changes topic to "5.1 release status (Fuel, mos-openstack, mos-linux) (Meeting topic: fuel)"16:03
mihgenso folks we still have bugs, yes, and still can't meet HCF criteria16:03
mihgenfor Fuel we have Galera issues, and many patching issues, as well as a few more other things16:04
*** catherine_r has left #openstack-meeting-alt16:04
*** bdpayne has joined #openstack-meeting-alt16:04
mihgenI think I would pass a voice to folks to talk about Fuel issues first, and then we switch to mos-openstack/mos-linux16:05
mihgen#topic Galera issues16:05
*** openstack changes topic to "Galera issues (Meeting topic: fuel)"16:05
*** rudrarugge has quit IRC16:05
*** akasatkin has joined #openstack-meeting-alt16:05
mihgenholser: please provide us with latest status on this16:05
mihgen#link https://bugs.launchpad.net/bugs/135447916:05
uvirtbotLaunchpad bug 1354479 in fuel "Galera is not syncing on the slaves sometimes" [Critical,In progress]16:05
mihgen#link https://bugs.launchpad.net/bugs/135516216:06
holsermihgen: Finally I found the issue with Galera16:06
uvirtbotLaunchpad bug 1355162 in fuel "[library] MySQL Galera is not operable after controllers hard reset" [High,Confirmed]16:06
*** dmahony has quit IRC16:06
holserThey were caused by high memory consumption caused high swap/in/swap out16:06
mihgenis it the only reason?16:06
holserI made a review to switch from mysqldump to xtrabackup and slightly decreased RAM16:07
*** xyang1 has quit IRC16:07
holserand that helped16:07
holserso now I am making BVT tests with my patch16:07
mihgenholser: do we need to increase ram size for BVT/Fuel CI jobs?16:07
*** caleb_ has joined #openstack-meeting-alt16:08
holseronly that, but xtrabackup helps as it’s much faster so it’s enough not to timout deployment16:08
holsermihgen: we do16:08
mihgenteran_: did you agreed on that? ^^16:08
holseras I showed that comlex deployments with neutron+gre cconsumes up to 3GB RAM16:08
holserps ax -O rss | awk '{ sum += $2 } END {print "Total memory usage =", sum/1024, "MB"}'16:09
holserTotal memory usage = 2691.69 MB
16:09
*** ruebenramirez has joined #openstack-meeting-alt16:09
nurlamihgen: we've already increase ram size for tests to 2.5gb16:09
holserThat’s after deployment, as during deployment it was 3Gb16:09
angdraugxarses also mentioned before that we need 2 vCPUs on test VMs16:09
angdraugwith one vCPU, there's too much context switching16:10
holser2 vCPU should help also16:10
*** yjiang5 has joined #openstack-meeting-alt16:10
mihgennurla: so should we get 3gb instead and 2 vcpu?16:10
mihgenat least for now before we improve consumption if possibl16:10
teran_mihgen: I'd prefer we start to use xtrabackup, I had expirience with that tool it's faster the mysqldump16:11
*** mtanino has quit IRC16:11
angdraugone more thing from xarses (he's having trouble getting online): we should enable KSM on jenkins slaves16:11
mihgenteran_: we will but as I understood we still need 3gb16:11
holserteran_: +1 https://review.openstack.org/#/c/109606/16:11
*** padkrish has quit IRC16:11
nurlathis requirements will be affect vbox users16:12
*** mtanino has joined #openstack-meeting-alt16:12
mihgenalso there was suggestion xdeller in mailing list about in-memory compression16:12
mihgenmight be we need to consider that as well16:12
angdraugmihgen: yup, that's what KSM is for, RAM deduplication16:12
mihgenholser: it's actually great that you nailed that down16:12
tznSKM can be very CPU heavy16:13
tzns/SKM/KSM/16:13
mihgenteran_: in your todo list to take a look on this?16:13
tznit might inpact performance16:13
*** eshumkher has joined #openstack-meeting-alt16:13
angdraugwe have it enabled on the dev server in MTV, it's not too bad wrt CPU16:13
holserI’d use huge pages instead for our libvirt virtual instances16:13
mihgenmay be devops team can try it and see how it works16:14
teran_mihgen: about 3g - currently it's possible but it could make us close eyes on sime performance issues16:14
tzn+1 hugepages16:14
*** bobf has quit IRC16:14
*** ruebenramirez has quit IRC16:14
mihgenholser: what's the decision, 3gb or 2.5 is ok?16:14
tznalthoug we could have better gain with KSM, worth checking16:14
holser2.5 should be ok16:14
*** baoli has joined #openstack-meeting-alt16:14
holserlet’s leave 2.5GB for now16:14
nurla+116:15
mihgenok. cool16:15
*** xarses has joined #openstack-meeting-alt16:15
mihgenlet's move on16:15
mihgen#topic Patching status16:15
holserbut question with 2 vCPU is still open16:15
*** openstack changes topic to "Patching status (Meeting topic: fuel)"16:15
mihgenteran_: pls consider 2 vcpu16:15
teran_mihgen: I saw offer obout RAM compression - that should help, so yeah it's in my todo :)16:15
mihgenkk :)16:15
mihgenpatching shows new areas of issues16:16
teran_mihgen: ok16:16
mihgendeductively we've discovered that python deps of openstack are not gonna be updated during pathing16:17
mihgenso basically oslo.messaging is not updated on node16:17
mihgenjust because puppet doesn't know that it should update this package16:17
*** kebray has quit IRC16:17
mihgenand it's not updated by deps tree16:17
mihgendilyin: what's our action plan on this?16:17
mihgenikalnitsky: any more news on other issues related to patching?16:18
dilyinwe have decided to add missing package installation to Fuel together with service notification16:18
angdraugthat's what we get for using puppet instead of apt/yum to manage dependencies16:18
ikalnitskymihgen: yep. here's the status16:18
dilyinbogdando have made a good patch to integrate oslo.messaging class to controlelr and compute16:19
mihgendilyin: provide a link pls16:19
ikalnitskyThe ceilometer issue:16:19
ikalnitsky#link https://bugs.launchpad.net/fuel/+bug/135449416:19
ikalnitskythe fix is merged, but afaik QA still have some troubles with ceilometer. Need to investigate.16:19
uvirtbotLaunchpad bug 1354494 in fuel/5.1.x "Puppet fails during updating ceilometer node" [Critical,Fix committed]16:19
ikalnitskyThe murano dashboard issue:16:19
ikalnitsky#link https://bugs.launchpad.net/fuel/+bug/135518016:19
ikalnitskyThe patch is already done, but we don't test it yet.16:19
uvirtbotLaunchpad bug 1355180 in fuel/6.0.x "rollback will fail - migration rollback is impossible - need to backup databases" [High,Confirmed]16:19
*** baoli has quit IRC16:19
*** lisaclark1 has quit IRC16:19
ikalnitskyWe finally resolve the issue with Ubuntu HA.16:19
ikalnitsky#link https://bugs.launchpad.net/fuel/+bug/135687316:19
ikalnitskythe fix isn't merged yet, but I made some tests and it works.16:19
uvirtbotLaunchpad bug 1356873 in fuel "[Update] Patching on Ubuntu nova ha failed with Unmet dependencies" [Critical,In progress]16:19
ikalnitskyAs for this16:19
ikalnitsky#link https://bugs.launchpad.net/fuel/+bug/135518016:19
ikalnitskyit was confirmed from the mos side that there're no migrations between 5.0 and 5.0.2. So we can target it for 6.0 and won't fix in 5.1.16:19
dilyinhttps://review.openstack.org/#/c/116011/16:19
ikalnitskythat's all :)16:19
mihgenok, thanks16:20
mihgenI'm wondering on the current testing coverage, how deep did we go, what else to expect16:20
mihgennurla: tatyana ^^16:20
*** MiroslavAnashkin has joined #openstack-meeting-alt16:20
dilyinangdraug, actually we use both puppet and apt/yum and collect troubles from both sides)16:21
tatyananurla: not so deep aswe want - we need to improve our test16:21
tatyanato verify if all deps are updated16:21
*** walker_ has joined #openstack-meeting-alt16:21
nurlaalso we should covered vcenter and cli16:21
tatyanaand meausre downtimes16:22
mihgenok, what about other stuff, like nova-network, murano/sahara16:22
tatyanacovered16:22
mihgentatyana: oh yes, we need to know what happens under real load by rally and patching at the same time16:22
mihgentatyana: good16:22
tatyanawe need to run destructive tess as well on patched ha16:22
tatyanatest16:23
nurlatoday we extend our swarm for run patching against all tests16:23
mihgenok if we turn off primary controller and run patching )16:23
nurlamihgen: O_016:24
ikalnitskymihgen: don't do it, i'm scared16:24
*** Riddhi has joined #openstack-meeting-alt16:24
*** rlpple has joined #openstack-meeting-alt16:24
nurlaand after shutdown cluster too)16:24
*** andreaf has joined #openstack-meeting-alt16:24
mihgenohh. too many cases16:24
*** andreaf has quit IRC16:24
mihgenall right, anything else on patching?16:24
mihgendpyzhov: what about size of tar balls?16:24
*** andreaf has joined #openstack-meeting-alt16:25
*** andreaf has quit IRC16:25
mihgensorry it was not me, but my IRC client )16:25
dpyzhovWell, we can win 2Gb with lrzip16:25
*** andreaf has joined #openstack-meeting-alt16:25
dpyzhovbut it takes 15 minutes to unpack16:25
*** sicarie has quit IRC16:25
xarsesso, a wash16:26
ikalnitskydpyzhov: what about using lrzip only on final tarball ?16:26
christopheraedoI would say better to make it smaller at the expense of time (consider you'll also save time downloading the upgrade package)16:26
dpyzhovI’m playing with fdupes in order to add hardlinks into tarball16:26
dilyinit's possible to provide only incremental repo updates. it will make update tarballs many times smaller. but we have no facilities to generate such diff files yet16:26
*** padkrish has joined #openstack-meeting-alt16:26
*** gokrokve has joined #openstack-meeting-alt16:26
dpyzhovincremental updates are out of scope for 5.116:26
dpyzhovIt’s too dangerous16:26
dpyzhovWe will get new bugs16:27
dilyinyes fdupes can hardlink same file very well. it will free a lot of space on master node but will not help with update tarball size16:27
mihgenyep let's be realistic for 5.116:27
dpyzhovdilyin: we have duplicates in tarball16:27
mihgenif we can do hardlinks way in 5.1, that would be awesome16:27
*** emagana has joined #openstack-meeting-alt16:27
dpyzhovbecause we have two centos repos and two ubuntu repos16:27
mihgenok so dpyzhov - you are trying to get hardlinks working for us?16:28
dpyzhovBut looks like lrzip still better than fdupes16:28
*** ankurrr has left #openstack-meeting-alt16:28
dpyzhovmihgen: yes16:28
dilyinthey are better together16:28
*** lisaclark1 has joined #openstack-meeting-alt16:28
*** lisaclark1 has quit IRC16:28
dpyzhovdilyin: looks like not16:28
*** marcoemorais has joined #openstack-meeting-alt16:28
*** lisaclark1 has joined #openstack-meeting-alt16:28
mihgenok let's move on folks16:28
mihgen#topic remove public IPs from slave nodes16:29
*** openstack changes topic to "remove public IPs from slave nodes (Meeting topic: fuel)"16:29
akasatkinLatest ISO is http://jenkins-product.srt.mirantis.net:8080/view/custom_iso/job/custom_master_iso/65/16:29
akasatkinOption "Assign public network to all nodes" is on the Settings tab in UI and it is disabled by default. I.e. only "controller" and "zabbiz-server" nodes will have Public network by default.16:29
akasatkinBoth HA and non-HA deployments are under testing.16:29
mihgenthere were a lot of complaints about having public IPs assigned to all nodes, even when not needed16:29
akasatkinCurrent problems are: nodes' default gateways point to the master node's IP (Sergey V. to figure out what to do with that), issues with ubuntu/neutron-vlan/ceph deployments (https://bugs.launchpad.net/fuel/+bug/1359834 - not yet reproduced on the last ISO)16:29
uvirtbotLaunchpad bug 1359834 in fuel "[custom iso] Ceph volumes don't work on ubuntu/neutron-vlan" [High,Incomplete]16:29
*** ramashri has joined #openstack-meeting-alt16:30
mihgenxenolog: did you figure out what to do with default gateway?16:30
mihgenakasatkin: cinder is fixed? it was using public net (wrongly)16:30
akasatkinyes, fixed16:30
mihgenok good16:31
*** amnk has quit IRC16:31
angdraugis this feature a risk for 5.1 schedule?16:31
akasatkinceph also works on last ISO. we just started with this configuration on 6516:31
mihgenangdraug: should be actually done16:31
akasatkinbut didn't check other cfg's on last ISO yet16:32
angdraugfor Ceph we still need to merge https://review.openstack.org/11572816:32
*** caleb_ has quit IRC16:32
angdraugotherwise it will raise HEALTH_WARN on every deployment16:32
xenologI can propose two way:16:32
xenolog1. simple  — set default gateway to the master node or to another node, that customer can define16:32
xenolog2. more_powerful — make virtual router, based on controller's and managed by pacemaker.16:32
xenolog1-st way required lot of changes in nailgun/fuelweb16:33
mihgenwhy a lot of changes? should not be so16:34
mihgenin 1st16:34
xenolog2-nd way —required  only puppet-part changes16:34
*** ruebenramirez has joined #openstack-meeting-alt16:35
mihgen1st way should be a way simpler. but we need public IPs gateway for nova-network still16:35
mihgenok let's take it out of the meeting16:35
*** sarob has joined #openstack-meeting-alt16:35
mihgenand discuss in #fuel-dev or ML if needed16:35
mihgenI hope it can be quickly done, otherwise we will have to go back with all of this16:35
xarsesxenolog: working with multiple-cluster networks, i found that l23network will set what ever its passed, we just need to fix nailgun to pass the network you want for default16:36
mihgenok I think we should move on16:36
*** ruebenramirez has quit IRC16:36
xarseswe also need to get a gateway router from the user on the other network16:36
xenologmihgen:16:36
xenolog1. field for IP address definition in fuel-web16:36
xenolog2. network checker, that monitor, that defined router — is a router16:36
xenolog3. new variables in astute.yaml16:36
*** padkrish has quit IRC16:36
*** tdruiva has joined #openstack-meeting-alt16:36
mihgenxenolog: ohh16:37
mihgenok16:37
*** teran has joined #openstack-meeting-alt16:37
mihgenlet's move on16:37
mihgen#topic mos-openstack bugs16:37
*** openstack changes topic to "mos-openstack bugs (Meeting topic: fuel)"16:37
mihgendmitryme: around to provide status?16:37
*** ikalnitsky has left #openstack-meeting-alt16:37
xenolog2-nd way looks like more relaible16:37
dmitrymemihgen: yep, I am here16:37
mihgenxenolog: yeah but seems complicated16:38
xenologbecause don't required from curtomer infrastructure16:38
dmitrymebasically we have two critical bugs left: fixing keystone and memcache interaction16:38
dmitrymeand fixing oslo.messaging <-> rabbitmq interaction16:38
*** dims_ has joined #openstack-meeting-alt16:38
mihgenany progress/estimates on both?16:38
dmitrymefor the first bug it is in the process of debugging16:39
dmitrymeI hope 1-2 days16:39
xenologmihgen: more complicated in implementing, but simpleest in using.16:39
dilyinI guest the first way is better. Just set route to the IP provided by user. If master node goes down it's not a big problem. Internet connection from computes is not strictly required16:39
dmitrymeas for the second one, I’ve already merged the old fix we used in 5.0.1 and right now are testing more proper fix16:39
mihgendilyin: +116:39
mihgenxenolog: dilyin but looks like we need to talk about it over email :)16:39
dmitrymes/I’ve/we’ve/16:40
mihgendmitryme: ok thanks16:40
*** teran_ has quit IRC16:40
dmitrymeit wasn’t me :-)16:40
mihgendmitryme: I hope it's gonna be soon too..16:40
*** dims has quit IRC16:40
mihgenanything else?16:40
dmitrymemihgen: I will discuss it, probably the old fix is good enough for 5.116:40
xenologdilyin:16:40
xenolog> If master node goes down it's not a big problem16:40
xenologmaster node CAN go down — it's i bigest problem!!!16:40
dmitrymemihgen: nope, nothing else16:41
xenologbecause we have min.3 controller and only one master node.16:41
dilyinxenolog, why? what importnat services are left there?16:41
mihgenxenolog: we have no deps on master node, only NTP and partly DNS16:41
angdraugtopic is mos-openstack?16:41
mihgenand that's what we must fix, hopefully in 6.016:41
mihgenshould be easy16:41
mihgendmitryme: thanks16:42
mihgenmoving on16:42
dmitrymeo, I think I should have mentioned issue which should be fixed by sqlalchemy upgrade, it has ‘high’ status, the fix is under review right now16:42
angdrauglink?16:42
mihgendmitryme: ok16:42
xenologif something can иу икщлут - it is when something breaks.16:42
mihgen#topic mos-linux bugs16:42
*** openstack changes topic to "mos-linux bugs (Meeting topic: fuel)"16:42
xenologs/иу икщлут/be broken/g16:42
nurlased16:43
*** caleb_ has joined #openstack-meeting-alt16:43
mihgenmsemenov: around?16:43
mihgenany status on rabbitmq upgrade, iptables.. ?16:43
msemenovmihgen: here16:44
mihgen#link https://bugs.launchpad.net/fuel/+bug/135909616:44
uvirtbotLaunchpad bug 1359096 in fuel "Build iptables 1.4.11 for centos" [High,Confirmed]16:44
angdraugwe also still need yet another ceph update:16:44
angdraug#link https://bugs.launchpad.net/fuel/+bug/134100916:44
uvirtbotLaunchpad bug 1341009 in fuel/5.0.x "[osci] obsolete ceph package in fuel-repository for 5.0.1 and 5.1" [Critical,Fix released]16:44
*** bauzas has left #openstack-meeting-alt16:44
xenologDNS  — this is not enough.16:44
msemenovrequest https://gerrit.mirantis.com/#/c/2108816:44
*** cknight has left #openstack-meeting-alt16:44
msemenovwe have +1 from Evgeny Li16:44
msemenovso it seems we can merge16:45
*** sicarie has joined #openstack-meeting-alt16:45
*** niclem has quit IRC16:45
*** niclem has joined #openstack-meeting-alt16:45
mihgenangdraug: is it that critical with ceph?16:45
xarseswas the python issue resolved?16:46
*** kebray has joined #openstack-meeting-alt16:46
mihgenI'm afraid a bit of any pkgs upgrades if possible16:46
mihgenxarses: what python issue?16:46
angdraugmihgen: it's not critical but it's high priority16:46
msemenovmay be this one? https://bugs.launchpad.net/mos/+bug/134206816:46
uvirtbotLaunchpad bug 1342068 in mos "syslog logging to /dev/log race condition" [Critical,Fix committed]16:46
mihgenangdraug: even high..16:46
angdraugthere's upstart and radosgw related fixes in that version16:46
xarsesmsemenov: correct16:46
msemenovxarses: not reproduced with the fix. So moved to fix committed16:47
angdraugif we're close to HCF I guess we can stay with ceph 0.80.4, but upstream highly recommends an upgrade16:47
xarsesmsemenov: ok, it should be in today's ISO?16:47
*** DMD has joined #openstack-meeting-alt16:47
msemenovxarses: sure16:47
angdraugnurla: do we have confirmation that python /dev/log problem is solved now?16:47
xarsesmsemenov: ok, I will retest my case that caused it to occur all the time16:48
angdraugxarses: yes, patched python packages have hit the 5.1 mirrors yesterday16:48
nurlaangdraug: no, we havn't16:48
*** tonytan4ever has quit IRC16:48
mihgenangdraug: I would skip it if possible, too many things, and we have 3 QA going on vacation next week16:48
nurlabecause nova and neutron issues blocked us16:49
*** vjardin_ has quit IRC16:49
angdraugmihgen: ok :(16:49
*** jaypipes has quit IRC16:49
msemenovas from the conversation with D.Borodaenko, there should be 100% cpu load for services writing to .dev.log16:49
*** rudrarugge has joined #openstack-meeting-alt16:49
msemenovafter restarting rsyslog many times(even during deployment)16:49
xarsesif you restart syslog while they are writing16:49
msemenovand we dont see it16:50
*** kebray has quit IRC16:50
angdraugwe don't have an ISO from today that would have passed centos bvt, why?16:50
xarsesWe will retest today and mark it fix released if i can't see it anymore16:50
*** pballand has joined #openstack-meeting-alt16:51
*** kebray has joined #openstack-meeting-alt16:51
*** tkelsey has joined #openstack-meeting-alt16:51
*** tkelsey has quit IRC16:51
msemenovxarses: and if the bug is still here, please provide deatiled repro steps in the issue16:51
xarsesyes16:51
*** shelleearnold007 has joined #openstack-meeting-alt16:52
mihgennurla: any comment on centos bvt?16:52
mihgennurla: we need bug about it. every build hangs16:52
nurlaok16:52
mihgenok anything else to bring with mos-linux?16:53
nurlaat first look, issue with galera16:53
msemenovlink?16:53
mihgen#topic 6.0 plans and beyond16:54
*** openstack changes topic to "6.0 plans and beyond (Meeting topic: fuel)"16:54
mihgenso we've discussed it a bit previously, just repeating that the main goal is to get Juno working16:54
mihgenthe thing that we still don't test openstack master with current puppet manifests puts us under risk releasing before design summit16:55
mihgenso we should start doing that ASAP and collaborate across teasm16:55
mihgenwe can run a few things in parallel16:55
*** tkelsey has joined #openstack-meeting-alt16:55
mihgenfor now though anyone who can help with reaching HCF should do that.16:55
*** jaypipes has joined #openstack-meeting-alt16:55
*** esker has quit IRC16:56
mihgenthat's it from my side. any questions/suggestions?16:56
*** derekh has quit IRC16:56
mihgenactually forgot about 5.0.216:56
mihgen#topic 5.0.2 milestone16:57
*** openstack changes topic to "5.0.2 milestone (Meeting topic: fuel)"16:57
mihgen#link https://launchpad.net/fuel/+milestone/5.0.216:57
*** lonnieh has joined #openstack-meeting-alt16:57
mihgenthere are a number of bugs over there. We must keep watching them too16:57
mihgenshould be like 95% of back ports to stable branch16:57
*** tmcpeak has joined #openstack-meeting-alt16:57
mihgen#topic other questions16:58
*** openstack changes topic to "other questions (Meeting topic: fuel)"16:58
*** Auktavian has joined #openstack-meeting-alt16:58
*** nkinder has joined #openstack-meeting-alt16:59
christopheraedoLast week I missed a chance to answer question about an open blueprint status.16:59
mihgenlooks like no questions except some we ran in parallel in the office)16:59
christopheraedoAdded in progress and todo work items to the blueprint (https://blueprints.launchpad.net/fuel/+spec/fuel-web-docs-dev-env-restructure)16:59
*** colinmcnamara has joined #openstack-meeting-alt16:59
christopheraedoWill change Fuel pages on OpenStack wiki today/tomorrow. First just re-ordering and improving the organization. Then I'll go through and add/update content over the next few days.16:59
mihgenchristopheraedo: oh yeah16:59
mihgenchristopheraedo: very good17:00
angdraugtime17:00
mihgenthanks17:00
mihgenok guys thanks17:00
*** malini has joined #openstack-meeting-alt17:00
mihgensee you next meeting17:00
*** akasatkin has left #openstack-meeting-alt17:00
tatyanabb17:00
mihgen#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Thu Aug 21 17:00:36 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/fuel/2014/fuel.2014-08-21-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/fuel/2014/fuel.2014-08-21-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/fuel/2014/fuel.2014-08-21-16.01.log.html17:00
*** MiroslavAnashkin has left #openstack-meeting-alt17:00
*** lisaclark1 has quit IRC17:01
apodrepniy_bb17:01
*** sicarie has quit IRC17:01
asyriybye17:01
nkinder#startmeeting openstack security group17:01
openstackMeeting started Thu Aug 21 17:01:59 2014 UTC and is due to finish in 60 minutes.  The chair is nkinder. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: openstack security group)"17:02
openstackThe meeting name has been set to 'openstack_security_group'17:02
*** asyriy has quit IRC17:02
maliniGreetings everyone!17:02
*** mihgen has left #openstack-meeting-alt17:02
tmcpeakhey!17:02
nkinder#topic rollcall17:02
*** openstack changes topic to "rollcall (Meeting topic: openstack security group)"17:02
swestonGreetings17:02
tkelseyhi all17:02
*** angdraug has left #openstack-meeting-alt17:02
nkinderHey OSSG folks17:02
tmcpeakhey nkinder17:02
tmcpeakhow it goes?17:02
nkindernot bad17:02
nkinderhyakuhei_ is unable to make it today17:03
nkinderhe passes on his apologies17:03
tkelseybusy busy man17:03
shelleearnold007Good morning17:03
bdpayneo/ peeps17:03
*** chair6 has joined #openstack-meeting-alt17:04
nkinderwe have a number of topics to cover today17:04
tmcpeakI've got 317:04
*** belliott has left #openstack-meeting-alt17:04
*** abhishekk has joined #openstack-meeting-alt17:04
nkinderwhat topics did others have?17:04
*** sambork has quit IRC17:04
*** sicarie has joined #openstack-meeting-alt17:04
tmcpeakops for the channel, stevedore follow up, qualys follow up17:04
*** lisaclark1 has joined #openstack-meeting-alt17:04
*** colinmcnamara has quit IRC17:05
nkinderok, I have stevedore on my list too17:05
tmcpeakoh good17:05
*** eshumkher has quit IRC17:05
* sicarie sneaks in late17:05
tmcpeakyou take that, I missed last week17:05
*** apodrepniy_ has quit IRC17:05
*** tzn has quit IRC17:05
nkinderalso security guide status, ossns, bandit, the security track for the summit17:05
tmcpeakcool17:05
nkinderso let's dive in17:05
rlppleHi guys17:05
rlppleRandy Perryman here17:05
tmcpeakhi rlpple17:06
nkinderhey rlpple17:06
nkinder#topic summit talks17:06
*** openstack changes topic to "summit talks (Meeting topic: openstack security group)"17:06
nkinderThanks to everyone who submitted talks for the security track!17:06
nkinderThe initial voting has been completed, and I expect that results will be sent out in the near future17:06
*** bknudson has joined #openstack-meeting-alt17:06
tmcpeakany idea how near future?17:06
*** apodrepniy has joined #openstack-meeting-alt17:06
*** teran has quit IRC17:07
nkindertmcpeak: not sure exactly17:07
nkindertmcpeak: I'll try to find out17:07
*** jtomasek has quit IRC17:07
tmcpeakcool17:07
nkinderThe propsals covered a broad range of topics17:07
*** rmoe has quit IRC17:07
*** dkehn has quit IRC17:08
*** _nadya_ has quit IRC17:08
nkinderThere was some "how do I secure things" talks, some threat assesment work, some intrusion detection topics as well17:08
*** julienvey has joined #openstack-meeting-alt17:09
nkinderMixed in were a number of forward looking topics, covering things like barbican, congress, and utilizing projects that are outside of OpenStack right now17:09
*** jjmb has joined #openstack-meeting-alt17:09
*** dkehnx has quit IRC17:10
nkinderoverall, I think there were around 45 proposals, so I think we'll have a nice track!17:10
*** gduan has joined #openstack-meeting-alt17:10
*** tatyana has quit IRC17:10
nkinder#topic stevedore17:10
*** openstack changes topic to "stevedore (Meeting topic: openstack security group)"17:10
*** dkehn has joined #openstack-meeting-alt17:10
tmcpeakawesome!17:10
nkindertmcpeak: take it away17:10
*** atiwari has joined #openstack-meeting-alt17:10
tmcpeakoh, I don't have anything new17:11
*** garyduan has quit IRC17:11
tmcpeakmeant to synch up with you from last week17:11
*** ndipanov has quit IRC17:11
tmcpeakwill start poking through code this week17:11
tmcpeakwho were the others?17:11
*** padkrish has joined #openstack-meeting-alt17:11
tmcpeakmxin?17:11
tmcpeakI don't see him17:11
nkinderI'd recommend checking last weeks IRC logs.  Basically, nobody has really looked into stevedore it seems.17:11
tmcpeakok, if it's just me, that's fine17:11
malinii was supposed to dive in too but nothing attempted yet17:11
tmcpeakI'll have status update next week17:11
tmcpeakcool17:11
*** dkehn_ has joined #openstack-meeting-alt17:11
nkinderI think there is interest, but nobody has jumped in yet17:12
*** dustins has left #openstack-meeting-alt17:12
nkinderBasically, there is some level of trust in loading a plugin via stevedore17:12
tmcpeakI read through the docs and plan to finish code review before next meeting17:12
tmcpeakok, that's fine17:12
nkindertmcpeak: ok, sounds good.  Anything else on stevedore?17:12
tmcpeakwe'll revisit next week17:12
nkinder#topic ossn17:13
*** openstack changes topic to "ossn (Meeting topic: openstack security group)"17:13
*** alkari has joined #openstack-meeting-alt17:13
nkinderWe have a few OSSNs out for review right now.17:13
*** esker has joined #openstack-meeting-alt17:13
*** dkehn__ has joined #openstack-meeting-alt17:13
nkinderOSSN-0020 and OSSN-0023 need reviewers17:14
nkinderI think they are both close17:14
*** dkehn has quit IRC17:14
*** dkehn__ has quit IRC17:14
*** jjmb has quit IRC17:14
nkinderI don't see shohel around, but he had proposed a OSSN-0024 agains the old repo17:14
*** dkehn_ is now known as dkehnx17:14
*** dkehn has joined #openstack-meeting-alt17:14
nkinder#link https://review.openstack.org/11342217:14
nkinderThat's OSSN-0020 that priti was working on17:15
tmcpeaklooks like we have one here too: https://bugs.launchpad.net/glance/+bug/135451217:15
uvirtbotLaunchpad bug 1354512 in ossn "Anonymous user can download public image through Swift" [Undecided,New]17:15
nkindertmcpeak: yep, that was just opened up today17:15
*** baoli has joined #openstack-meeting-alt17:15
nkinderStan has this one out for review...17:15
nkinder#link https://review.openstack.org/11497117:15
nkinderAnd shohel has this one...17:16
nkinder#link https://review.openstack.org/11446017:16
*** DMD has quit IRC17:16
*** esker has quit IRC17:16
nkinderSo if anyone has some time to review any of those, it would be appreciated!17:16
tmcpeakcool, will do17:17
tkelseywill have a look17:17
*** rmoe has joined #openstack-meeting-alt17:17
maliniwill do17:17
nkinder#topic security-guide17:17
*** openstack changes topic to "security-guide (Meeting topic: openstack security group)"17:17
*** juzuluag has joined #openstack-meeting-alt17:17
nkinderbdpayne: how are things progressing on the security guide bugs?17:17
bdpaynequite well actually17:18
bdpaynewe are maintaining a pretty good steady state velocity17:18
bdpaynewith several active contributors17:18
bdpayneso thanks to all involved17:18
nkindergreat!17:18
*** ijw has quit IRC17:18
bdpayneI still owe the group some forward direction on the book17:18
bdpaynewhich I am working on :-)17:18
bdpayne(I promise!)17:18
nkinderbdpayne: You mean in terms of a v2 "roadmap"?17:19
*** ijw has joined #openstack-meeting-alt17:19
bdpayneyes17:19
bdpayneI would like to plot the course for that17:19
bdpayneand also determine how we manage the book with respect to openstack releases and such17:19
bdpaynebtw, we are down to 42 bugs against the book atm17:20
nkinderbdpayne: that will probably be a good topic to talk about at the Summit too (if we don't figure it all out by then)17:20
*** baoli has quit IRC17:20
bdpayneagreed17:20
bdpaynehopefully I'm moving forward at least a bit by then17:20
nkinder:)17:20
*** dkehn has quit IRC17:20
bdpaynebut the summit is a great place for that17:20
*** dkehn has joined #openstack-meeting-alt17:20
bdpayneif others would like to help, you can pluck off a bug from https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=sec-guide17:20
bdpayneplenty of work to be done17:21
bdpayneand sometimes writing is a nice change from coding :-)17:21
bdpayneok, that's all that I have on the book today17:21
nkinderok, thanks17:21
bdpayneunless others have comments / questions / stuff to add17:21
nkindernot from me.  Sounds like good progress on the bugs17:22
bdpayneindeed17:22
nkinder#topic summit17:22
*** openstack changes topic to "summit (Meeting topic: openstack security group)"17:22
nkinderspeaking of the summit, who here is planning on attending?17:22
maliniMalini -- unsure17:23
nkinderIf we have an idea of who is going, we can start to think about OSSG items that we plan to accomplish there17:23
nkinderI'll be there17:23
bdpayneI will be there17:23
swestonI will be there as well17:23
tmcpeakI'll do my best ;)17:23
nkinderI know that hyakuhei_ will be there17:23
*** ijw has quit IRC17:23
tkelseyin not sure17:23
nkindershohel proposed a talk, so he must be planning to attend17:24
nkinderpriti proposed a talk too, so she's in the same boat17:24
nkinderstan too17:24
tmcpeakI'm pretty sure Priti will be there17:24
*** mestery has joined #openstack-meeting-alt17:24
*** harlowja_away is now known as harlowja_17:25
*** lisaclark1 has quit IRC17:25
nkinderok, well given the above I think that it's safe to assume we can get some coverage of doc and threat modeling efforts at a minimum17:25
nkindertmcpeak: I think trying to get some discussion on the gate tests there could be valuable17:26
tmcpeakdefinitely, I hope that summit/dev talks make it, but if not, I'll be running around trying to get attention17:27
tmcpeakI mean attention for the gate tests :P17:27
nkindertmcpeak: It might be worthy of a design session if we have things far enough along at that point.17:27
tmcpeakoh yeah, that's what I mean, design session, not dev17:27
bdpayneyeah, shooting for a design sessions there makes a lot of sense, IMHO17:28
tmcpeakyeah, I'm going to try to get bandit built out with some more tests17:28
nkinderAny other summit related topics from anyone before we talk about bandit some more?17:28
tmcpeakfind some more bugs, and then we can really make a compelling case to why gate tests are useful17:28
nkinderok then...17:28
nkinder#topic bandit17:29
*** openstack changes topic to "bandit (Meeting topic: openstack security group)"17:29
*** yjiang5 has left #openstack-meeting-alt17:29
chair6hi!17:29
nkinderchair6: hey17:29
chair6i emailed a summary of status to the mailing list last week17:29
chair6haven't seen any response, but it's out there and ready for people to write more tests against17:29
nkinderYeah, thanks for sending that out.  I didn't see any replies... :(17:29
chair6i plan on doing some when i have time, but would be good if others could contribute17:29
*** tobybot11 has quit IRC17:30
tmcpeakchair6: I'm going to do some work on that end17:30
bknudsonwhat's the subject of the note?17:30
tmcpeakchair6: I've found a couple other subprocess calls we want to check17:30
*** mattgriffin has quit IRC17:30
tmcpeakOpenStack has a wrapper on subprocess that most components are probably using, so we should check that call too for starters17:30
nkinderI'm planning to look at how we could make it run as a part of the CI (non-voting)17:31
chair6tmcpeak .. i saw your comment on that, and did some digging17:31
nkinderfinding the time to actually do that is a different matter though...17:31
chair6there were a few different examples of what you're describingg17:31
chair6so i wrote a test that identifies any function call, regardless of name, that includes a shell=True argument17:31
*** mestery has quit IRC17:31
tmcpeakflooded in fun?17:31
*** mestery has joined #openstack-meeting-alt17:32
*** mestery has quit IRC17:32
tmcpeakI switched email unfortunately around the exact time you sent it out so I didn't get that ML, can you forward it to me, btw?17:32
chair6will do17:32
*** HeOS has quit IRC17:32
*** mestery has joined #openstack-meeting-alt17:32
*** esker has joined #openstack-meeting-alt17:32
tmcpeakthe other thing we might want to look for is eval17:32
chair6that's about it though .. i plan to keep working on improving the framework, and building out more tests17:33
*** jcoufal has quit IRC17:33
chair6i'll leave the CI-integration piece to you, nkinder17:33
*** dimtruck is now known as zz_dimtruck17:34
*** chandankumar has joined #openstack-meeting-alt17:34
nkinderchair6: ok, sounds good17:34
bknudsonis bandit going to live in github or get pulled into openstack repo?17:34
tmcpeakbknudson: good question17:35
chair6i'd like to get it into an openstack repo17:35
bknudsonI think it would be nice to have gerrit for reviews17:35
*** caleb_ has quit IRC17:35
chair6agreed17:35
maliniinside oslo would be nice17:35
nkinderany other bandit talk?17:35
nkinderand +1 on gerrit for bandit tests17:36
bknudsoncan you point me to the check that bandit is doing now?17:36
bknudsonin github17:36
chair6https://github.com/chair6/bandit/tree/master/plugins is where they're defined17:36
bknudsonchair6: thanks!17:36
bknudsonneat!17:37
chair6want to refactor this at some point, but that's it at the moment :)17:37
*** chandankumar has quit IRC17:37
*** markmcclain has joined #openstack-meeting-alt17:38
nkinder#topic open discussion17:38
*** openstack changes topic to "open discussion (Meeting topic: openstack security group)"17:38
nkinderany other topics from anyone?17:38
tmcpeakops in channel17:38
tmcpeakI think it would be useful to get a few: maybe nkinder, bdpayne, hyakuhei_17:38
tmcpeakjust to keep an eye out for gabriela kind of BS17:38
bdpayneyeah, I agree that this would be useful17:39
*** otherwiseguy has quit IRC17:39
nkinder+117:39
bdpayneI was told that we need to work with one of the general ops types for freenode to get setup17:39
nkindershe was back today (with a different number at the end of her nick)17:39
bdpayneI just haven't had the time to chase that down yet17:39
tmcpeakreally? it should have banned by IP17:39
bdpaynebotnets17:39
*** TravT has joined #openstack-meeting-alt17:39
nkindertmcpeak: it was banned by name17:39
bdpaynelots of ips17:39
bdpaynebut, yeah, I think it was banned by name17:40
bknudsonI found the block button in pidgin17:40
tmcpeakoh, yeah banned by name doesn't work17:40
clarkbbdpayne: we manage ops for the channels you shouldn't need to go to freenode for that17:40
clarkbbdpayne: i thought fungi pointed you at the change to make?17:40
bdpayneoh, perhaps I misunderstood what fungi was saying17:40
bdpayneit sounded like I needed to contact someone to request access17:40
bknudsonmessages to irc should all be signed.17:40
kaihi all,17:41
clarkbbdpayne: what is the channel name?17:41
bdpayneopenstack-security17:41
tmcpeak#openstack-security17:41
kaiis there any status update about threat modeling project?17:41
kaiwanna to join into this project in my free time17:42
*** mfer has joined #openstack-meeting-alt17:42
nkinderkai: There is a separate IRC meeting for that IIRC17:42
nkinderkai: but I'm sure your help would be much appreciated there!17:42
*** Sukhdev has joined #openstack-meeting-alt17:43
clarkbyup its maanged so you need to edit https://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/files/accessbot/channels.yaml to add additional ops17:43
bdpayneoh nice, I'll do that shortly17:43
*** mestery has quit IRC17:43
tmcpeakclarkb: perfect, thanks!17:43
bdpaynethanks clarkb17:43
clarkbunder the channel name do operators: and a yaml list of ops17:43
tmcpeakother thing I had was about qualys17:43
*** lisaclark1 has joined #openstack-meeting-alt17:43
clarkbnote ops need to be registered with nickserv and identified17:43
bdpayneok17:44
tmcpeaksounds good17:44
chair6i'm always idling here so happy to take on ops if you need volunteers17:44
*** lisaclark1 has quit IRC17:45
*** lisaclark1 has joined #openstack-meeting-alt17:45
bdpaynechair6 ok thanks17:46
nkinderanything else from anyone?17:47
tmcpeakqualys discussion17:47
*** SumitNaiksatam has quit IRC17:47
*** holser has left #openstack-meeting-alt17:47
tmcpeaknot really qualys, but I'll call it that for lack of a better one word description17:47
tmcpeak"Gate testing XSS"17:48
*** otherwiseguy has joined #openstack-meeting-alt17:48
shelleearnold007sounds interesting17:48
tmcpeakthis is in regards to gmurphy's original proposition on the ML to figure out root cause of new XSS bugs17:49
*** jprovazn has joined #openstack-meeting-alt17:49
tmcpeakone of the Nebula folks seems to have a pretty good grasp on why this was happening and provided a good explanation17:49
*** catherine_r has joined #openstack-meeting-alt17:50
nkindertmcpeak: I'm not familiar with qualys17:50
tmcpeakbut what I was thinking is that we should integrate some integrated XSS automated tool into gate tests17:50
*** xarses has left #openstack-meeting-alt17:50
tmcpeakqualys is a vulnerability scanner17:50
*** catherine_r has left #openstack-meeting-alt17:50
bdpayneyeah, I spoke with Paul about this... he said that the right people could come together and hammer out a lasting solution in a day or two17:50
nkinderprovided as a service or software?17:51
tmcpeakmy understanding is service17:51
nkinderbdpayne: yeah, that would be a good item to try to get people to hash out at the summit17:51
*** balajiiyer has joined #openstack-meeting-alt17:51
tmcpeakbdpayne: right, so there is the long lasting solution17:51
nkinderbdpayne: it sounds like an architectural sort of change, so it would be best to take place early in the dev. cycle17:51
*** balajiiyer has left #openstack-meeting-alt17:51
tmcpeakbdpayne: but I think there is also room for a gate test here, just to make sure people we don't drift into the same situation again17:52
tmcpeakit sounded like the problem is that new devs come on and just fire out code without understanding the correct way to do things17:52
nkindertmcpeak: yeah, but adding gate jobs after cleaning up the code would catch that17:52
bdpayneagreed on all accounts17:52
tmcpeaknkinder: yeah totally agree17:53
nkindertmcpeak: I think the issue is that the code has bad examples that new devs copy right now17:53
*** elmiko has joined #openstack-meeting-alt17:53
bknudsonthe XSS bugs seem to be poor design decisions17:53
bdpaynefix in early in the cycle, have gate tests to avoid it from happening again17:53
tmcpeakyep17:53
bknudsonfor example, the table code requires you to set an option to escape the input17:53
bknudsonrather than escaping the input by default17:53
nkinderI don't know if gmurphy is planning on attending the summit (I'll check with him)17:53
tmcpeakbknudson: oh really?17:53
bknudsontmcpeak: yes, see the latest XSS bug...17:53
tmcpeakwow, nice17:54
bknudsonhttps://review.openstack.org/#/c/115310/1/openstack_dashboard/dashboards/admin/aggregates/tables.py17:54
tmcpeakseems like an easy enough fix if you educate devs17:54
bknudsonso you have to pass in autoescape=True to escape17:54
clarkbso fwiw anyone can propose a new job and run it experimentally against any project17:54
clarkbso you could just go do a thing and see how it works, if people like it then you can work on making it gating17:55
tmcpeakclarkb: oh cool, I was wondering about that17:55
bdpaynewould it be appropriate to have a security education session at the dev part of the summit?17:55
tmcpeakyou know where there is info on how to do that?17:55
bdpaynelike, security coding best practices for openstack?17:55
tmcpeakbdpayne: +117:56
nkinderbdpayne: targeting XSS issues specifically?17:56
swestonbdpayne: +117:56
*** mattgriffin has joined #openstack-meeting-alt17:56
bdpaynewell, it could hit on some of that17:56
nkinderbdpayne: that seems like a good idea17:56
bdpaynebut I was thinking more broad17:56
bdpaynethis whole discussion just got me thinking17:56
tmcpeakroot wrapper use would probably be pretty useful17:56
bdpaynecarry on ;-)17:56
*** tosky has joined #openstack-meeting-alt17:56
elmikoas an outside observer, i would definitely attend a security education session at summit17:56
sicarie+117:57
tmcpeakelmiko: +117:57
bdpaynecool, good to know17:57
tmcpeakbdpayne, bdpayne, bdpayne17:57
nkinderok, that's a good idea for the design sessions if we have a security track17:57
bdpaynecould also go in a general track or something17:57
tmcpeakthat actually fits in line perfectly with OSSG mission17:57
bdpaynesecurity track at the design sessions... seems unlikely17:57
nkinderyeah, a cross-project/general track17:58
nkinderwhatever track our stuff was in last time17:58
bdpayneyeah, the cross-project thingy17:58
nkinderok, we're getting short on time here17:58
nkinderanything else before we end the meeting?17:58
*** e0ne has joined #openstack-meeting-alt17:59
*** alazarev has joined #openstack-meeting-alt17:59
nkinderok, thanks all!17:59
nkinder#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Thu Aug 21 17:59:57 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
bknudsonthanks17:59
tmcpeakthanks everyone!17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_security_group/2014/openstack_security_group.2014-08-21-17.01.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_security_group/2014/openstack_security_group.2014-08-21-17.01.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_security_group/2014/openstack_security_group.2014-08-21-17.01.log.html18:00
swestonthanks18:00
*** chair6 has left #openstack-meeting-alt18:00
tkelseythanks nkinder, thanks all18:00
*** tmcpeak has left #openstack-meeting-alt18:00
*** tkelsey has quit IRC18:00
*** SumitNaiksatam has joined #openstack-meeting-alt18:00
malinithanks nkinder18:00
*** shelleearnold007 has quit IRC18:00
*** sicarie has quit IRC18:01
rlppleThanks18:01
SergeyLukjanovsahara folks ping18:01
elmikoo/18:01
dmitrymeo/18:01
NikitaKonovalovo/18:01
*** lisaclark1 has left #openstack-meeting-alt18:01
aignatovo/18:01
*** rlpple has left #openstack-meeting-alt18:01
SergeyLukjanovalazarev will chair today's meeting18:01
SergeyLukjanovhm18:02
*** adrian_otto has quit IRC18:02
*** tmckay has joined #openstack-meeting-alt18:02
SergeyLukjanov#startmeeting sahara18:02
openstackMeeting started Thu Aug 21 18:02:52 2014 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: sahara)"18:02
alazarev#startmeeting sahara18:02
tmckayo/18:02
openstackThe meeting name has been set to 'sahara'18:02
openstackalazarev: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.18:02
alazarevops18:03
SergeyLukjanov:)18:03
SergeyLukjanov#chair alazarev18:03
*** kebray has quit IRC18:03
openstackCurrent chairs: SergeyLukjanov alazarev18:03
SergeyLukjanovalazarev, please18:03
alazarevok, let’s start18:03
alazarev#link https://wiki.openstack.org/wiki/Meetings/SaharaAgenda#Next_meetings18:04
alazarev#topic sahara@horizon status (croberts, NikitaKonovalov)18:04
*** openstack changes topic to "sahara@horizon status (croberts, NikitaKonovalov) (Meeting topic: sahara)"18:04
*** mikedillion has quit IRC18:05
NikitaKonovalovOk18:05
aignatovalazarev: you are the chair! ;) something new :)18:05
*** igordcard has quit IRC18:05
dmitrymeNikitaKonovalov: nice status in horizon :-)18:05
aignatovlol18:05
NikitaKonovalovThe change allowing the dashobard work with bootstrapt 3 is merge18:05
tmckayyeah, Ok sounds great18:05
NikitaKonovalovmerged*18:05
alazarevaignatov: yes, and Sergey told about this 2 mins ago :)18:06
NikitaKonovalovfinally18:06
elmikoalazarev: surprise!18:06
SergeyLukjanovalazarev, aignatov, my inet connection is extremely bad today and I'm receiving messages by 1 min batches ;)18:06
*** markmcclain has quit IRC18:06
NikitaKonovalovthere is still a bugfix for templates' copy on review18:06
*** gondoi is now known as zz_gondoi18:06
SergeyLukjanovNikitaKonovalov, that's awesome, so, we'll not have any more several version dropdowns :)18:07
NikitaKonovalovbut that's very small and I hope it will land faster18:07
*** alazarev_ has joined #openstack-meeting-alt18:07
NikitaKonovalovSergeyLukjanov: Yes, the dropdowns now appear in right places only18:07
alazarev_hopefully other patches will land faster18:08
NikitaKonovalovso that's pretty much all from horizon18:08
*** caleb_ has joined #openstack-meeting-alt18:08
*** kebray has joined #openstack-meeting-alt18:08
toskyalazarev: I have request related to horizon and sahara, should I talk about this at the end (open discussion)?18:08
alazarev_tosky: sure18:08
SergeyLukjanov#chair alazarev_18:08
openstackCurrent chairs: SergeyLukjanov alazarev alazarev_18:08
alazarev_#topic News / updates18:09
*** openstack changes topic to "News / updates (Meeting topic: sahara)"18:09
*** bknudson has left #openstack-meeting-alt18:09
elmikoi've been working on getting a prototype of the swift/auth stuff running. it's going well, i'm currently testing the proxy user creation and trust delegation. next step will be authentication JobBinaries using proxy.18:09
*** alazarev has quit IRC18:10
*** alazarev_ is now known as alazarev18:10
alazarevI’ve done series about plugin SPI -> edp engine18:10
*** ijw has joined #openstack-meeting-alt18:10
SergeyLukjanovI'm working on some oslo.* upgrades and going to push new patch sets soon18:10
tmckayI poked around with Oozie security, small discussion during open topics on "code" or "doc fix instead"18:10
*** Auktavian has quit IRC18:10
tmckayand catching up on lots of reviews :)18:11
*** zz_dimtruck is now known as dimtruck18:11
alazarevsomeone else?18:13
*** morganfainberg is now known as morganfainberg_Z18:13
*** lukego has joined #openstack-meeting-alt18:13
alazarevok, let’s move on18:13
alazarevno action items from the previous meeting18:14
alazarev#topic https://wiki.openstack.org/wiki/Juno_Release_Schedule18:14
*** openstack changes topic to "https://wiki.openstack.org/wiki/Juno_Release_Schedule (Meeting topic: sahara)"18:14
*** DMD has joined #openstack-meeting-alt18:14
alazarev#topic Juno release18:14
*** openstack changes topic to "Juno release (Meeting topic: sahara)"18:14
alazarev#link https://wiki.openstack.org/wiki/Juno_Release_Schedule18:14
alazarevSergeyLukjanov: update from you?18:15
SergeyLukjanovnope18:15
SergeyLukjanovops18:16
SergeyLukjanovone moment18:16
SergeyLukjanovwe have some unassigned stuff18:16
elmikoi'm concerned about the schedule for getting all the swift/auth patches together. ideally, when should the patches be in for inclusion in Juno?18:16
*** _nadya_ has joined #openstack-meeting-alt18:16
*** baoli has joined #openstack-meeting-alt18:16
SergeyLukjanov#link https://launchpad.net/sahara/+milestone/juno-318:16
SergeyLukjanovwe need volunteer to verify and close https://blueprints.launchpad.net/sahara/+spec/swift-url-proto-cleanup-deprecations18:16
*** radez_g0n3 is now known as radez18:17
alazarevSergeyLukjanov: I can do it18:17
SergeyLukjanovelmiko, so, we have two weeks to land sahara side patches18:17
SergeyLukjanovalazarev, ok, thx18:17
SergeyLukjanovalazarev, assigned to you18:17
alazarev#action https://blueprints.launchpad.net/sahara/+spec/swift-url-proto-cleanup-deprecations (alazarev)18:18
elmikoSergeyLukjanov: ok, i think it will be close. i'm hopeful to get this all concluded, but i know the testing and integration with gate mayb be cumbersome.18:18
SergeyLukjanovelmiko, do you have estimates on time needed to make this work done?18:18
*** ujuc has quit IRC18:18
elmikoi'm hoping to have a full prototype by the end of next week. then we will need to coordinate about how to test the proxy domains in the gate.18:18
dmitrymeelmiko: also consider putting your patch for early review18:19
elmikohopefully, the patches will be up for review by the end of next week.18:19
elmikodmitryme: thanks, i will18:19
*** malini has quit IRC18:19
*** nelsnelson has quit IRC18:19
alazarevok, let’s continue18:20
alazarev#topic Heat engine backward compatibility18:20
*** openstack changes topic to "Heat engine backward compatibility (Meeting topic: sahara)"18:20
*** baoli has quit IRC18:21
*** _nadya_ has quit IRC18:21
alazarevhttps://bugs.launchpad.net/sahara/+bug/1336525 broke backward compatibility for heat engine18:21
uvirtbotLaunchpad bug 1336525 in sahara "[DOC][HEAT] Document note about ec2-user" [High,Fix released]18:21
alazarevdo we want to simply document this?18:21
SergeyLukjanovнup18:22
SergeyLukjanovyup*18:22
dmitrymealazarev: it is woth noting that it is not the only change which broke backward compatibility, it is just the first one18:22
SergeyLukjanovwe need to make progress on heat engine18:23
*** chellygel has joined #openstack-meeting-alt18:23
*** tonytan4ever has joined #openstack-meeting-alt18:23
aignatovSergeyLukjanov:18:23
aignatovwhat do you mean?18:23
SergeyLukjanovand heat was a beta quality for Icehouse release, so, it's ok18:23
SergeyLukjanovaignatov, I mean that if we need to improve heat engine we could break backward compat for it with Icehouse18:24
alazarevok, we have https://bugs.launchpad.net/sahara/+bug/1357135 to document that18:24
uvirtbotLaunchpad bug 1357135 in sahara "Document changes from #1336525 in upgrade notes" [Undecided,New]18:24
alazarev#link https://bugs.launchpad.net/sahara/+bug/135713518:24
toskyit's not the default choice for installation in fact, if I remember the documentation18:24
alazarev#topic Anti-affinity semantics18:24
*** openstack changes topic to "Anti-affinity semantics (Meeting topic: sahara)"18:24
dmitrymeSergeyLukjanov: I think you meant ‘heat ENGINE is of beta quality” :-)18:24
SergeyLukjanovdmitryme, sure ;)18:24
alazarevand related question abut anti affinity18:24
SergeyLukjanovso, here we have a much more interesting issue - we'd like to update a-a to work using server groups18:25
SergeyLukjanovand I like this idea18:25
*** chellygel has left #openstack-meeting-alt18:25
alazarevserver groups is an openstack way to do it18:25
SergeyLukjanovbut it changes a bit the semantics of a-a18:25
alazarevbut we started anti affinity before server groups were introduced18:25
*** _nadya_ has joined #openstack-meeting-alt18:25
SergeyLukjanovalazarev, please, write the diff between how it'll working18:25
alazarevserver groups now have restriction - each instance could be only in one server group18:26
*** kebray has quit IRC18:26
alazarevso, if nodegroup has several processes we can’t do anti affinity independently18:26
alazarevproposed solution - make one server group per cluster and assign it to all instances that has at least one affected process18:27
*** mikedillion has joined #openstack-meeting-alt18:28
alazarevI made this for heat engine only: https://review.openstack.org/#/c/112159/18:28
*** jtomasek has joined #openstack-meeting-alt18:29
alazarevbecause anti affinity was broken for heat engine at all18:29
aignatovnot at all :)18:29
alazarevso, now we need to decide futher plans18:29
alazarevaignatov: would you recommend way how it works for production? ;)18:30
alazarevso, the first question: are we going to support direct engine for a log time?18:30
SergeyLukjanovso, I think that we should migrate to server groups in both direct and heat engines18:31
SergeyLukjanovfor consistency18:31
dmitrymeI would review at a different angle: we didn’t promised any specific algorithm for a-a in documentation. We just promised that it will work. By this change we do not break the promise, we just change the algorithm. So it is not a backward incompatible change18:31
SergeyLukjanovit doesn't breaks backward compat18:31
SergeyLukjanovand we have no docs about how a-a works18:31
SergeyLukjanovdmitryme, +18:31
alazarevyeap18:31
aignatovI agree with all thoughts, but direct engine should be changed too IMO18:32
*** mikedill_ has joined #openstack-meeting-alt18:32
*** DMD has quit IRC18:32
alazarevbut migration to server groups in direct will break backward compatibility18:32
dmitrymealazarev: why?18:32
alazarevdmitryme: all ‘old’ instances are not in the group18:32
SergeyLukjanov++ for updating direct engine18:32
*** Haiying has joined #openstack-meeting-alt18:32
SergeyLukjanovalazarev, but it'll not break removal of old clusters18:33
dmitrymealazarev: aha, and you can’t assign an existing instance to a group, right?18:33
SergeyLukjanovwe'll add note to the upgrade docs18:33
*** msemenov has quit IRC18:33
*** mikedillion has quit IRC18:33
SergeyLukjanovI think it'll be ok18:33
SergeyLukjanovtmckay, elmiko, any thoughts?18:33
alazarevdmitryme: Sahara need knowledge about ‘old’ way to do that18:33
dmitrymealazarev: I see18:34
alazarevSergeyLukjanov: removal is Ok, it will break scaling only18:34
elmikoi think best not to break backward compat, if possible18:34
SergeyLukjanovalazarev, it could be easily checked by looking for server groups while scaling18:34
*** mikedill_ has quit IRC18:34
alazarevif we are going to remove direct in L for example, I would vote on ‘do not change direct, make engines work differently’18:35
elmikois it possible to migrate "old" style instances to server groups?18:35
*** mikedillion has joined #openstack-meeting-alt18:36
alazarevelmiko: technically - yes, practically - I don’t know18:36
*** gyee_ has quit IRC18:36
tmckayI'm not too familiar with how server groups work, but based on reading, I think I agree with dmitryme -- no broken promises.18:36
*** _nadya_ has quit IRC18:37
*** ruebenramirez has joined #openstack-meeting-alt18:37
tmckayalazarev, good point -- if the engines work differently, that seems okay to me.  Especially if direct is on its way out.18:37
alazarevtmckay: the only difference in behavior is that instances from different anti-affinity groups will be on different hosts now (or errored if there are no enough hosts)18:37
*** banix has joined #openstack-meeting-alt18:37
SergeyLukjanovtmckay, alazarev, I'd like to avoid situation when users will use a-a and it will magically work differently18:38
*** johnthetubaguy is now known as zz_johnthetubagu18:38
SergeyLukjanovso, IMO it's better to upgrade both engines18:38
*** kebray has joined #openstack-meeting-alt18:39
alazarevSergeyLukjanov: we don’t have engine switch policy, all clusters need to be recreated during switch18:39
alazarevSergeyLukjanov: so, very low probability that anyone cares18:39
SergeyLukjanovalazarev, I'm talking about two installations18:39
*** TravT has quit IRC18:40
alazarevI thought a little bit more, I think it is possible to write ‘upgrade’ code that will add existing VMs to group18:41
alazarevin this case we can keep backward compatibility18:41
alazarevdo we have plans to test backward compatibility?18:42
elmiko+1 to the 'upgrade' method18:42
*** sambork has joined #openstack-meeting-alt18:42
alazarevok, will try to do ‘upgrade’ way18:42
SergeyLukjanov+1 for upgrading while scaling for example18:43
alazarev#topic Open discussion18:43
*** openstack changes topic to "Open discussion (Meeting topic: sahara)"18:43
dmitrymealazarev: but the old algorithm can assign two VMs to a single node, while they need to be added to a group by the new algorithm18:43
elmikoSergeyLukjanov: that makes a lot of sense18:43
alazarevdmitryme: this is nova problem, not Sahara :)18:43
dmitrymealazarev: I am just not sure it will works18:43
SergeyLukjanovI have an idea of adding versions to the engines to make validation aware of new/old clusters in case of heat engine18:44
dmitrymes/works/work/18:44
*** Longgeek has quit IRC18:44
SergeyLukjanovI'll propose the lp issue with description and implementation earlier next week18:44
elmiko+1 to versioned engines18:44
alazarevSergeyLukjanov: +2 on versions18:44
dmitryme+1 for versions18:44
*** radez is now known as radez_g0n318:45
elmikoi have a couple questions about when to produce errors for the swift/auth stuff18:45
alazarev#agreed Add Sahara version as cluster property18:45
SergeyLukjanov#agreed upgrade both direct and heat engines to use server groups (try to upgrade cluster while scaling, add notes to upgrade doc)18:45
*** emagana has quit IRC18:45
tmckayfolks, quick opinions on https://review.openstack.org/#/c/115113/.  In short, there is no way really to hide configs/args in Oozie (including swift stuff, old or new).  So, there are 2 choices: secgroup for public networks, and iptables on the Oozie server host for finer control on public/private networks.  I think documentation, leaving the solution up to admins, is the way to go.   I had proposed optional itpables rules applica18:45
*** emagana has joined #openstack-meeting-alt18:46
tmckaySo, doc only, or iptables option, rules set by Sahara with ssh?18:46
elmikoi like doc + iptables option18:46
alazarevmay be we could add provisioning engine and stuff like that too? e.g. to disable scaling with other engine18:46
tmckayI think iptables option is not hard18:47
alazarevtmckay: I think users must do it manually via security groups, ability to specify secgroup is already merged18:47
dmitrymeI like alazarev18:47
*** kai has quit IRC18:47
*** morganfainberg_Z is now known as morganfainberg18:47
alazarevtmckay: +1 on document that18:47
dmitrymeI like alazarev’s point18:47
alazarevdmitryme: (hug)18:47
dmitrymealazarev: :-)18:48
tmckayalazarev, I was talking to elmiko yesterday, with lots of users in the same tenant, anyone who can launch an instance can get on the private network and get to Oozie, so you may want iptables.  But, anyone in the same tenant can get to swift, too.18:48
elmikolol18:48
*** emagana_ has joined #openstack-meeting-alt18:48
tmckayIf Oozie would just screen jobs by user, it would be fine.  But it doesn't.18:48
*** emagana has quit IRC18:49
alazarevtmckay: users in the same tenant are visible to each other by definition, don’t see problem here18:49
*** sgordon has left #openstack-meeting-alt18:49
*** nelsnelson has joined #openstack-meeting-alt18:49
alazarevtmckay: if they need privasy - they can separate tenants18:50
tmckayokay, fine with me.18:50
alazarev*privacy18:50
dmitrymetmckay: I agree with alazarev, user from the same tenant can simply snapshot/terminate instances of another user18:50
tmckaydocumentation on secgroup, note to leave out oozie port recommended18:50
* tmckay still thinks Oozie security could be better18:51
alazarevtmckay: I would say not only oozie, hadoop has plenty of sensitive stuff18:51
elmikoeven with users in the same tenant, you wouldn't want them to get access to each other's creds.18:51
tmckayagreed18:51
tmckayelmiko, apparently, we don't care18:51
*** sambork has quit IRC18:51
*** caleb_ has quit IRC18:51
tmckaysame tenant is one big happy family18:52
tmckayyou better trust all the people in your tenant18:52
elmikoAlice and Bob are working on a project in tenant_A, Bob also has access to tenant_B, if Alice gets Bob's creds, she can now access tenant_B18:52
tmckay:)18:52
alazarev‘happy’ is questional… but one family for sure :)18:52
dmitrymeelmiko: very good point18:52
tmckayelmiko, doh18:52
*** radez_g0n3 is now known as radez18:53
*** nkinder has left #openstack-meeting-alt18:53
elmikoi just like having a binary option for the admin to lock down the Oozie port with iptables. i think it's a simple option.18:53
alazarevwill this be solved with trusts? we don’t store passwords anymore18:53
tmckayelmiko, more complicated, because Alice can also read hadoop logs18:53
elmikoalazarev: it will18:54
tmckayelmiko, I wonder if the job configs are in the hadoop logs, too18:54
tmckayin which case locking down the oozie server doesn't matter18:54
alazarevelmiko: what’s the problem in this case?18:54
elmikotmckay: i think only what we pass through workflow.xml18:54
elmikoalazarev: if the user is only using the trust methodology, no problem.18:54
elmikowhat should we do in a situation where sahara is configured to use proxy, but the user still inputs creds for a data source?18:55
elmikodrop the creds, use them, send a warning, ?18:55
*** kebray has quit IRC18:55
tmckaydrop them, I think18:55
dmitrymeelmiko: I would say “throw an exception”, to be explicit18:56
*** amitgandhinz has joined #openstack-meeting-alt18:56
elmikodmitryme: reject the form, essentially18:56
dmitrymeI mean, return an error, in terms of API18:56
dmitrymeelmiko: yep18:56
*** rudrarug_ has joined #openstack-meeting-alt18:56
dmitrymeI just hate implicit things18:56
elmikook, so if sahara is configured for proxy domains, then it will be a non-issue as no user creds will ever be used.18:57
tmckayelmiko, back up.  is there any way to guard against the Bob and Alice scenario, if workflows can be seen?18:57
elmikodmitryme: agreed. explicit > implicit18:57
*** ametts has joined #openstack-meeting-alt18:57
tmckaycause Alice can get a trust in another tenant, right?18:57
elmikotmckay: it's still a problem if anyone can access a user's creds through the workflow18:57
elmikotmckay: oh that, yea the trust is between Alice and the proxy user18:58
alazarevdo we need creds in workflow?18:58
elmikoalazarev: unfortunately yes18:58
elmikowell, we need to get them to hadoop somehow. if we take oozie out of the mix, then we don't need the workflow.18:58
elmikoas i understand it18:58
tmckayelmiko, so you would still recommend an iptable option (or at least a doc note?)  Part of it for me hinges on what is visible in hadoop logs18:59
alazarevelmiko: for swift? untill swift is patched?18:59
dmitrymeit is my understanding that these will be the creds of proxy user, which will have access to the given tenant only by the means of trust18:59
elmikodmitryme: yes18:59
*** ijw_ has joined #openstack-meeting-alt18:59
*** rudrarugge has quit IRC18:59
elmikoalazarev: currently, we pass the user's creds through workflow. when the swift/auth patch goes through, we will only be passing creds for the proxy user18:59
tmckayelmiko, okay, so you can't cross tenants in that case.  The worst you can do is get auth in the current tenant, which you already have, right?19:00
dmitrymeso, if somebody from the same tenant steals them, he will not be able to access any other tenant Bob has access too19:00
dmitrymes/too/to/19:00
elmikotmckay: yea19:00
elmikodmitryme: yea19:00
*** catherine_r has joined #openstack-meeting-alt19:00
tmckayalright, so public oozie access is still the major issue19:00
elmikothe trust is scoped only to the user and project that the swift container is in19:00
*** tpatil_ has joined #openstack-meeting-alt19:00
*** megan_w_ has joined #openstack-meeting-alt19:01
toskyif may I say one thing before closing...19:01
elmikoin the future we might be able to use something like Barbican and asymmetric keys from the instances to completely remove creds from the process19:01
*** obulpathi has joined #openstack-meeting-alt19:01
tmckaytosky, sure19:01
*** megan_w_ has quit IRC19:01
*** megan_w_ has joined #openstack-meeting-alt19:02
alazarevelmiko: yeap, somewhere in M cycle :)19:02
elmikoalazarev: LOL19:02
toskyone of our intern was working on horizon selenium tests (starting from https://blueprints.launchpad.net/horizon/+spec/selenium-integration-testing) with the goal of horizon/sahara tests19:02
*** juzuluag has quit IRC19:02
*** malini has joined #openstack-meeting-alt19:02
amitgandhinzdo you mind wrapping up, thanks =P we have our poppy meeting starting now....19:02
alazarevops19:02
tmckaymove to the other channel19:02
dmitrymetosky: lets go to #sahara19:02
elmikoamitgandhinz: sorry19:02
alazarev#endmeeting19:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:02
openstackMeeting ended Thu Aug 21 19:02:41 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:02
amitgandhinzthanks19:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2014/sahara.2014-08-21-18.02.html19:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2014/sahara.2014-08-21-18.02.txt19:02
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2014/sahara.2014-08-21-18.02.log.html19:02
amitgandhinz#startmeeting Poppy Weekly Meeting19:02
openstackMeeting started Thu Aug 21 19:02:54 2014 UTC and is due to finish in 60 minutes.  The chair is amitgandhinz. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: Poppy Weekly Meeting)"19:02
openstackThe meeting name has been set to 'poppy_weekly_meeting'19:02
alazarevlet’s continue on sahara channel19:03
alazarevamitgandhinz: sorry19:03
amitgandhinz#topic roll call19:03
*** openstack changes topic to "roll call (Meeting topic: Poppy Weekly Meeting)"19:03
amitgandhinzwho is here for Poppy?19:03
obulpathio/19:03
* megan_w_ is here19:03
ametts\o/19:03
*** ijw_ has quit IRC19:03
catherine_rHere!19:04
amitgandhinzanyone from fastly or maxcdn?19:04
megan_w_or akamia?19:05
megan_w_looks like we might have a short meeting19:05
amitgandhinzpotentially19:05
*** mikedillion has quit IRC19:05
amitgandhinz#topic Review action items19:06
*** openstack changes topic to "Review action items (Meeting topic: Poppy Weekly Meeting)"19:06
amitgandhinz#link: http://eavesdrop.openstack.org/meetings/poppy_weekly_meeting/2014/poppy_weekly_meeting.2014-08-14-19.00.html19:06
*** julim has quit IRC19:06
amitgandhinzcatherine_r: update from you on this19:06
amitgandhinz(1)19:06
catherine_rI've reviewed some of  doc via gerritt review for the issue mentioned in last week's meeting.19:07
amitgandhinz#link: https://review.openstack.org/#/c/113944/19:07
*** tosky has left #openstack-meeting-alt19:07
catherine_rBut I haven't finished that or moved to wiki review. Will work to get more done before next meeting.19:07
amitgandhinzi think good progress is being made on this.  I still need to get the last set of comments handled19:07
*** mikedillion has joined #openstack-meeting-alt19:08
amitgandhinzlets aim to get these docs merged before the next meeting19:08
catherine_rok19:08
amitgandhinz#agreed: catherine_r and amitgandhinz will work to get the docs merged by next meeting: #link https://review.openstack.org/#/c/113944/19:08
*** harlowja_ has quit IRC19:08
amitgandhinzok, item 2 - amitgandhinz to move meetings higher up on the page19:08
amitgandhinz#link: https://wiki.openstack.org/wiki/Poppy19:09
amitgandhinzdone19:09
megan_w_bam19:09
*** Haiying has quit IRC19:09
amitgandhinz(3) amitgandhinz to look into CDNManager in MaxCDN19:09
amitgandhinzthis is not done.  i will carry this over19:09
amitgandhinz#action: amitgandhinz to investigate MaxCDN CDN Manager API for master/sub accounts19:10
*** elmiko has left #openstack-meeting-alt19:10
amitgandhinz(4) is the same as (3) =P19:10
amitgandhinzok moving on ....19:10
*** alazarev has quit IRC19:10
amitgandhinz#topic Updates on Blueprints and Bugs19:10
*** openstack changes topic to "Updates on Blueprints and Bugs (Meeting topic: Poppy Weekly Meeting)"19:10
amitgandhinzi started added the blueprints to launchpad:19:11
amitgandhinz#link: https://blueprints.launchpad.net/poppy19:11
obulpathiyay19:11
obulpathican we get permissions to assign bluetprints and update them?19:11
amitgandhinzwhen creating a branch, be sure to name it bp/<name>19:11
amitgandhinzobulpathi: you cant do that right now?19:12
amitgandhinzhmmm.....19:12
obulpathiyep19:12
obulpathiI am naming my branches that way19:12
amitgandhinz#action: amitgandhinz to investigate permissions so that others in the team can manage bleuprints19:12
obulpathibut when I tried to assign a blueprint to myself .. I could not19:12
amitgandhinzok i will investigate what needs to be done there19:12
amitgandhinzthanks for the heads up19:12
obulpathithanks :)19:12
amitgandhinzwe should try to keep the bp up to date with the correct status19:13
amitgandhinzdo we want to spend time now updating it or do that offline?19:14
megan_w_let's do it now19:14
megan_w_that way we can get a feel for where we're at19:14
amitgandhinzok19:14
megan_w_(unless anyone objects)19:14
*** tmckay has left #openstack-meeting-alt19:15
amitgandhinzi think we have time today19:15
megan_w_agreed19:15
obulpathiagreed19:15
*** harlowja has joined #openstack-meeting-alt19:15
amitgandhinz#link: https://blueprints.launchpad.net/poppy19:15
amitgandhinz#link: https://blueprints.launchpad.net/poppy/+spec/add-docstrings19:15
amitgandhinzametts: can i assign this to you?19:15
amitgandhinzsince you showed eagerness on this previously =P19:15
amettsSure19:16
megan_w_haha19:16
*** lakshmiS has joined #openstack-meeting-alt19:16
*** baoli has joined #openstack-meeting-alt19:17
amitgandhinzhttps://blueprints.launchpad.net/poppy/+spec/cloudfront-driver19:17
amitgandhinzdo you want to continue to drive this one obulpathi?19:17
obulpathiyep19:17
obulpathiplease assign to me19:17
amitgandhinzor should we leave it open so others can also experience CF19:17
*** _nadya_ has joined #openstack-meeting-alt19:17
obulpathiI am open to both options19:17
*** DMD has joined #openstack-meeting-alt19:18
amitgandhinzim inclined to leave it open for knowledge sharing19:18
amitgandhinzthis one also has a dependency tree associated to it19:18
*** emagana_ has quit IRC19:18
amitgandhinz#link: https://blueprints.launchpad.net/poppy/+spec/create-service19:18
obulpathiupdate service and multiple origins issues are open19:18
amitgandhinzno one has starting working on this yet right?19:19
*** emagana has joined #openstack-meeting-alt19:19
*** harlowja has quit IRC19:19
obulpathino from me19:19
amitgandhinzobulpathi: create bugs for those19:19
obulpathiI mean to say I have not working on these19:19
*** julim has joined #openstack-meeting-alt19:20
amitgandhinzbut those are known issues, so lets create a bug to track it19:20
obulpathisure19:20
*** wayne___ has joined #openstack-meeting-alt19:20
obulpathiI will take that19:20
amitgandhinzhttps://bugs.launchpad.net/poppy19:20
*** ramashri has quit IRC19:20
*** radez is now known as radez_g0n319:20
amitgandhinz#link: https://blueprints.launchpad.net/poppy/+spec/docs-getting-started19:20
amitgandhinzthis is in progress/review19:20
*** lakshmiS has quit IRC19:21
amitgandhinzmy name goes on it19:21
amitgandhinzfastly and maxcdn driver stories are in the same boat as CF, so lets leave it open19:22
*** baoli has quit IRC19:22
obulpathifor documentation, can you add my name for getting started with Poppy on Linux/Ubuntu/Fedora?19:22
obulpathiamitgandhinz: ^19:22
amitgandhinzsure, can you create another bp for that19:22
obulpathiok19:23
*** emagana has quit IRC19:23
amitgandhinzok flavors: flavors is making good progress, currently writing the tests for it19:23
amitgandhinzhttps://blueprints.launchpad.net/poppy/+spec/flavors19:23
amitgandhinz#link: https://blueprints.launchpad.net/poppy/+spec/flavors19:24
amitgandhinzthere is a version submitted without the tests that could do with some review love (before the tests land)19:24
amitgandhinz#link: https://review.openstack.org/#/c/115130/19:24
*** morganfainberg has quit IRC19:25
amitgandhinz#link: https://blueprints.launchpad.net/poppy/+spec/health19:25
amitgandhinzthis is obulpathi's right?19:25
obulpathiyes, its is19:25
amitgandhinzstate?19:25
obulpathiping is done, waiting for approval19:25
amitgandhinzi'll put good progress19:26
obulpathihealth  is partially done, waiting for ping to get through19:26
amitgandhinzcool19:26
amitgandhinzdid you address the comments for ping?19:26
obulpathiyes, addresses them and resubmitted the patch19:26
amitgandhinz#link: https://review.openstack.org/#/c/115408/19:26
obulpathis/addresses/addressed/19:26
amitgandhinzok lets get this reviewed19:26
*** padkrish has quit IRC19:26
amitgandhinzok, i dont believe any of the other bp's are being worked on19:27
amitgandhinztonytan4ever: you will need to create a bp for the model stuff you are working on19:27
*** morganfainberg has joined #openstack-meeting-alt19:27
tonytan4everOK19:27
obulpathiCQL tests19:27
obulpathiI started looking into19:27
obulpathican we add it to bps?19:27
*** harlowja has joined #openstack-meeting-alt19:28
amitgandhinzyes we should19:28
*** DMD has quit IRC19:28
amitgandhinzdid you look into the pysandra stuff i posted yesterday19:28
*** mattgriffin has quit IRC19:28
obulpathiyes. looking into pysandra and fakecassandra19:28
obulpathino .. not yesterdays stuff19:28
obulpathiI only looking into jira cards details so far19:28
amitgandhinz#info: pysandra unit testing: http://javasplitter.blogspot.com/2013/01/embedded-cassandra-with-python-and-java.html19:28
*** alazarev has joined #openstack-meeting-alt19:29
amitgandhinzim not sure the viability of it if it helps but may be useful for our tests19:29
obulpathiok, thanks19:29
amitgandhinzok anything else regarding blueprints?19:29
*** arnaud has joined #openstack-meeting-alt19:29
amitgandhinz...19:30
amitgandhinz...19:30
amitgandhinz...19:30
amitgandhinzok moving on19:30
amitgandhinz#topic Permissions to assign and update blueprints19:30
tonytan4everWhile we're waiting for Obu's response, there's the blue print I am working on: https://blueprints.launchpad.net/poppy/+spec/poppy-models19:30
*** openstack changes topic to "Permissions to assign and update blueprints (Meeting topic: Poppy Weekly Meeting)"19:30
amitgandhinzthats easy ;-)19:30
amitgandhinz#action: amitgandhinz to investigate permissions for blueprints19:31
amitgandhinzok anything else on this topic?19:31
amitgandhinzi'll take that silence as a no19:31
tonytan4everI am good wit it.19:31
amitgandhinz#topic Community Involvement19:31
*** openstack changes topic to "Community Involvement (Meeting topic: Poppy Weekly Meeting)"19:32
amitgandhinzok so we need to start ramping up the diversity of the team19:32
megan_w_agreed19:32
*** mattgriffin has joined #openstack-meeting-alt19:32
*** ramashri has joined #openstack-meeting-alt19:32
obulpathi+119:32
amitgandhinzfirst thing i need to do is email the openstack-dev ML with announcing Poppy again19:32
amitgandhinzwe did an initial round during the Atlanta Summit, but didnt get much feedback19:33
*** e0ne has quit IRC19:33
megan_w_i can help make sure our message is clear on that email19:33
megan_w_i think we can do better communicating the value of the project19:33
amettsamitgandhinz: Make sure you include links to wiki, github, et.al. so folks can see the progress that's been made.19:33
*** prmtl has quit IRC19:33
amitgandhinznow that we have a team, and valuable partners, we can go back to the community showing whats been happening19:33
megan_w_agreed.19:33
megan_w_also19:33
amitgandhinzwe might garner more interest when they see akamai, fastly, maxcdn are all on board with the project19:34
*** kebray has joined #openstack-meeting-alt19:34
megan_w_when it comes to provider involvement, i am wondering how we can get them involved more19:34
*** harlowja has quit IRC19:34
megan_w_what do we want from providers?  they'll build their plugins when its time...but they cant really do that until we have the api19:34
amitgandhinzyeh19:34
amettsWhy can't providers help build the API?19:35
amitgandhinzone we have the api and a few plugins, then other providers will prob get more interested19:35
megan_w_so if we're recruiting them, should we be saying, "come give us your input on what a standard api should look like?"19:35
amitgandhinzproviders can if they want to19:35
*** malini has quit IRC19:35
amitgandhinzyeh19:35
megan_w_i thought last week's discussion about account structure was useful19:35
amitgandhinzdefinitely19:35
megan_w_maybe we can promote our agenda better???19:35
amitgandhinzright now the api is very much driven by this team, but i would like to see providers inflluence the design also19:36
megan_w_for example, if they knew we wanted to talk about ssl certs today, would they have come?19:36
obulpathi+119:36
*** Haiying has joined #openstack-meeting-alt19:36
amitgandhinzpotentially19:36
megan_w_yeah me too.  we just need to make it attractive to them19:36
amitgandhinzso lets try finalizing the agenda earlier in the week and then megan_w_ can work her magi19:36
amitgandhinzmagic19:36
megan_w_i don't have any magi19:36
megan_w_only magic19:37
megan_w_amitgandhinz: seems like a good plan19:37
megan_w_and let's try to have a meaty topic everytime19:37
megan_w_even if its just design19:37
amitgandhinz#agreed: amitgandhinz to finalize agenda by Tuesday PM19:37
*** luizfar has quit IRC19:37
amitgandhinz#agreed: megan_w_ to communicate with providers before weekly meeting19:38
megan_w_bam19:38
*** luizfar has joined #openstack-meeting-alt19:38
*** kebray has quit IRC19:38
obulpathialong with providers, if we can bring more poppy deployers (like Rackspace) that will add weight to to Poppy19:38
megan_w_then we can focus on more operators, which will really get providers interested19:38
amitgandhinz#agreed: amitgandhinz and megan_w_ to come up with Grade A meat in the agenda19:38
megan_w_obulpathi: great minds :)19:38
megan_w_I am planning to reach out to HP19:39
obulpathicopying ideas :D19:39
megan_w_they currently work with akamai, i believe19:39
amitgandhinzwhat happened with edgecast?19:39
*** dtx00ff has joined #openstack-meeting-alt19:39
megan_w_we just havent kicked off with them yet19:39
megan_w_their head guy was out for a week19:39
amitgandhinzoh ok19:39
*** mattgriffin has quit IRC19:39
megan_w_we were going to reconvene once he's bakc19:39
amitgandhinzcool19:39
amitgandhinzobulpathi: when was the next local openstack meetup19:40
amitgandhinzit would be good to get on their schedule to talk about Poppy19:40
obulpathitoday19:40
*** harlowja has joined #openstack-meeting-alt19:40
amitgandhinzhaha19:40
amitgandhinzok next month then19:40
obulpathiyes19:40
megan_w_good idea19:40
amitgandhinzdo you want to take charge on that since youre familiar with it?19:40
obulpathisure19:41
amitgandhinz#action: obulpathi to get on the local atlanta Openstack Meetup schedule for poppy19:41
amettsdhellmann^19:41
obulpathiYou want me to schedule a meeting for Poppy? And you wil ldo the presentaiton?19:41
obulpathipresentation19:42
amitgandhinzok i think thats a good step one for community building, and lets see what we can do next19:42
amitgandhinzobulpathi: we both can do the presentation =)19:42
amitgandhinzall of us can get on stage =P19:42
obulpathiamitgandhinz: Yes, I can switch slides :)19:42
amettsIt's only a bar.  There is no stage. :)19:42
*** kebray has joined #openstack-meeting-alt19:42
*** Sukhdev has quit IRC19:42
amitgandhinzwell, not sure if we want to do coyote ugly style presentations19:43
amitgandhinzthat might get awkward19:43
amettsewwww19:43
megan_w_lol19:43
megan_w_ok, let's move on19:43
amitgandhinzlol19:43
obulpathiametts: Yes,I am in touch with dhellman. late response19:43
amitgandhinzok moving on...19:43
amitgandhinz#topic SSL cert provisioning19:43
*** openstack changes topic to "SSL cert provisioning (Meeting topic: Poppy Weekly Meeting)"19:43
*** emagana has joined #openstack-meeting-alt19:43
*** TravT has joined #openstack-meeting-alt19:43
amitgandhinzis there much to discuss here, or should we defer to next time when the providers are present?19:44
*** kebray has quit IRC19:44
amitgandhinzin related news, CloudFront released some SSL enhancements yesterday19:44
megan_w_yeah19:44
megan_w_we definitely need them to have an intelligent disucssion about it19:44
*** kebray has joined #openstack-meeting-alt19:44
megan_w_them= providers19:44
obulpathiamitgandhinz: oh nice19:44
amitgandhinz#link: http://www.zdnet.com/aws-bolsters-cloudfront-security-7000032847/19:45
tonytan4everI think we can do some prep talk, about what we know about the providers.19:45
*** padkrish has joined #openstack-meeting-alt19:45
megan_w_tonytan4ever: take it away19:45
*** _nadya_ has quit IRC19:45
amitgandhinzmegan_w_: you are out the next two meetings19:45
obulpathi#link: from aws website: https://aws.amazon.com/blogs/aws/cloudfront-ssl-ciphers-session-ocsp-pfs/19:45
*** Riddhi has quit IRC19:46
megan_w_yes i am19:46
amitgandhinzyou want to be here for those discussions with the providers?19:46
*** rm_work is now known as rm_work|away19:46
megan_w_perhaps.  we'll talk agenda offline19:46
amitgandhinzok19:46
amettsAnd who will be live-blogging the wedding to #openstack-poppy?19:46
tonytan4everok19:46
*** thomasem has quit IRC19:46
amitgandhinzmoving on...19:46
amitgandhinz#topic Open Discussion19:46
*** openstack changes topic to "Open Discussion (Meeting topic: Poppy Weekly Meeting)"19:46
amitgandhinzametts: we run a cdn service, megan_w_ will be live streaming =P19:47
amettsAh. Of course. :)19:47
megan_w_you know it19:47
megan_w_ametts: any idea when we'll know about our talk proposal?19:47
amitgandhinzok any open discussion items from anyone?19:47
*** stannie has quit IRC19:47
obulpathiMegan will be our first customer?19:47
megan_w_i'd like to plan to demo poppy in paris19:48
amitgandhinzvoting has already closed19:48
amettsmegan_w_: No idea.  I've been watching openstack-dev for clues, but I haven' t seen any.  Should be soon.19:48
megan_w_if we dont get a session accepted, will we still ahve design sessions?19:48
*** ruebenramirez has quit IRC19:48
catherine_rmegan_w_: annegentle said maybe tomorrow...19:49
*** ramashri has quit IRC19:49
megan_w_oh cool19:49
megan_w_thanks catherine_r19:49
obulpathione thing I forgot: AWS does not have an official python client19:49
megan_w_yuck19:49
amettsThey'll have to be rogue/informal design sessions.19:49
obulpathiwe should add it to bp or bugs19:49
megan_w_ok19:49
amettsOnly incubated products get scheduled ones.19:49
megan_w_that's what i was wondering19:49
*** jprovazn has quit IRC19:49
megan_w_good to know19:49
amettsThey didn't even do Unconferences in the Atlanta summit.19:49
megan_w_ok, we'll plan our summit presence once we hear about the session, i guess19:50
megan_w_sounds like that decision is close enough to wait19:50
amitgandhinzyeh, else we just stand outside the eiffel tower holding poppy banners19:50
amitgandhinzmaybe a field trip to normandy ;-)19:50
megan_w_ha19:50
amettsI was going to suggest that we distribute poppy flowers, but that might get us in trouble with customs.19:50
catherine_rgiverny!19:51
catherine_rflowers :-)19:51
megan_w_lol, i was wondering what that was19:51
megan_w_ok, that's it for me.  do we want to tlak about the aws python thing?19:51
amitgandhinzhttp://sharonsantoni.com/2013/06/the-poppy-fields-of-normandy.html19:51
obulpathimegan_w: sure19:52
obulpathithe thing is aws does not have a official python bindings for their API19:52
catherine_ramitgandhinz: Ah... good link.19:52
amitgandhinzobulpathi: can we just fork boto and apply our requirements to it?19:52
obulpathion thei home page: https://aws.amazon.com/blogs/aws/cloudfront-ssl-ciphers-session-ocsp-pfs/19:52
amitgandhinzand then submit back upstream?19:52
*** _nadya_ has joined #openstack-meeting-alt19:52
obulpathiamitgandhinz: yes19:53
obulpathithats the plan for now19:53
amettsWait.19:53
obulpathijust want to share it here19:53
amettsIf you do that in Python, what will you be calling behind the scenes?19:53
amitgandhinzdo what in python?19:53
obulpathiAWS API19:53
obulpathiREST API using "XML"19:54
amettsoic.  I get it now.19:54
amitgandhinzboto already is a python client, its just out of date19:54
amitgandhinzand the patches are slow to apply19:54
*** jtomasek has quit IRC19:54
amitgandhinzso if we fork boto, get the CloudFront pieces to where we need it to be and run with that until they merge it back upstream19:55
amettsYeah, I was just temporarily confused about how we'd use boto if it didn't know anything about CloudFront.19:55
amitgandhinzno, it has CF support, just not things like multiple origins etc which the API supports19:55
obulpathiyes, only some pieces are missing19:56
amettsAh.  Ok.19:56
amitgandhinz#agreed: obulpathi will fork boto and apply necessary enhancements and submit upstream19:56
obulpathigot it19:56
amitgandhinzok any other discussion items?19:56
amitgandhinzwe have 4 minutes19:56
megan_w_not from me19:56
amettsAnyone know a 4-minute song we could sing?19:57
amitgandhinz"shake it off"19:57
amitgandhinz- taylor swift19:57
*** Haiying has quit IRC19:57
megan_w_yeah, i gotta go19:57
amitgandhinzidk if its 4 min tho lol19:57
*** jecarey has quit IRC19:57
amitgandhinz"papi" by J-Lo19:57
amitgandhinzok i think we done here19:58
* ametts thinks amitgandhinz has terrible taste in music19:58
*** malini has joined #openstack-meeting-alt19:58
amitgandhinzgeez, no country, no hip hop19:58
megan_w_later gators19:58
amitgandhinz#endmeeting19:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:58
openstackMeeting ended Thu Aug 21 19:58:41 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/poppy_weekly_meeting/2014/poppy_weekly_meeting.2014-08-21-19.02.html19:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/poppy_weekly_meeting/2014/poppy_weekly_meeting.2014-08-21-19.02.txt19:58
openstackLog:            http://eavesdrop.openstack.org/meetings/poppy_weekly_meeting/2014/poppy_weekly_meeting.2014-08-21-19.02.log.html19:58
*** _nadya_ has quit IRC19:59
*** catherine_r has left #openstack-meeting-alt19:59
arnaud#startmeeting glance20:00
openstackMeeting started Thu Aug 21 20:00:21 2014 UTC and is due to finish in 60 minutes.  The chair is arnaud. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: glance)"20:00
openstackThe meeting name has been set to 'glance'20:00
*** ijw_ has joined #openstack-meeting-alt20:00
arnaudhey!20:00
TravTo/20:00
abhishekko/20:00
arnaudnikhil___,20:01
arnaudzhiyan,20:01
arnaudflaper87|afk,20:01
arnaudgokrokve,20:01
*** ametts has left #openstack-meeting-alt20:01
*** ijw__ has joined #openstack-meeting-alt20:01
arnaudI guess we can get started20:02
rosmaitao/20:02
arnaudhere is the link of the agenda for today20:02
*** obulpathi has left #openstack-meeting-alt20:02
arnaud#link https://etherpad.openstack.org/p/glance-team-meeting-agenda20:02
arnaudso Mark is still on vacation, if I remember correctly, I think he will be back next week20:02
*** ruebenramirez has joined #openstack-meeting-alt20:03
arnaudok, so we can get started with the Murano proposal20:03
arnaud#topic murano20:03
*** openstack changes topic to "murano (Meeting topic: glance)"20:03
*** LakshmiS has joined #openstack-meeting-alt20:04
*** prmtl has joined #openstack-meeting-alt20:04
*** stannie has joined #openstack-meeting-alt20:04
arnaudso, we started the discussion last week, and I would like to take more time to make sure everybody is OK with the proposal20:04
nikhil___o/20:04
arnaudgokrokve, sent an email earlier this week20:04
arnaudlet me find the link :)20:04
*** tdruiva has quit IRC20:04
*** ijw_ has quit IRC20:04
*** amitgandhinz has left #openstack-meeting-alt20:04
*** ijw has quit IRC20:05
arnaudhttps://www.mail-archive.com/openstack-dev%40lists.openstack.org/msg32768.html20:05
arnaudso, the idea is to split the Murano project (to make it fit into existing programs)20:05
*** walker_ has quit IRC20:06
arnaudthe catalog program would include the API piece of Murano basically20:06
*** matrohon has joined #openstack-meeting-alt20:06
*** atiwari has quit IRC20:06
*** kebray has quit IRC20:07
arnaudI think this is good for Glance because 1. this will bring new people contributing to glance (artifact<->murano) 2. I think the split makes sense, and the API fits into the mission that we want to achieve20:08
*** LakshmiS has quit IRC20:08
*** prmtl has quit IRC20:08
*** obulpathi has joined #openstack-meeting-alt20:08
TravTwould API be new service endpoint?20:08
arnaudyep20:08
*** obulpathi has left #openstack-meeting-alt20:09
arnaudthat would not be integrated with Glance20:09
arnaudat least in the short term20:09
*** ijw__ has quit IRC20:09
nikhil___wait, so the code would be in Glance however, the endpoint not?20:09
TravTis there a different between artifacy20:09
arnaudmaybe in the future, we can expect integration20:09
*** tdruiva has joined #openstack-meeting-alt20:09
arnaudbut for now I think this that's the goal20:10
nikhil___arnaud: we have a enable flag basically, then?20:10
TravTrepo and app catalog?20:10
arnaudso, the murano API will consume the artifact api20:10
TravTsorry on phone today and keyboard not cooperating20:10
arnaudin the short term, I don't think we need to worry much about the integration between glance and murano20:11
arnaudthey just share the same program "catalog"20:11
arnaudunfortunately, gokrokve doesn't seem to be around20:11
nikhil___ok, we can discuss details on spec as well20:12
arnaudso, I think the best way is to reply to his email if you have questions and/or concerns20:12
*** kebray has joined #openstack-meeting-alt20:12
nikhil___sounds good20:12
*** satish has joined #openstack-meeting-alt20:12
TravTdoes this mean artifacts API is also separate?20:12
arnaudthis change needs to go through the governance repo and approved by the TC20:12
arnaudno artifact API is in glance API V220:13
arnaudlike metadefs20:13
TravTok20:13
*** _nadya_ has joined #openstack-meeting-alt20:13
arnaud#topic restrict download patch20:14
*** openstack changes topic to "restrict download patch (Meeting topic: glance)"20:14
arnaud#link https://review.openstack.org/#/c/98737/20:14
*** lonnieh has quit IRC20:14
*** jmontemayor has quit IRC20:14
arnaudabhishekk, do you want to say something about it?20:14
tpatil_we are waiting for Mark to review this patch, but would appreciate if others can give their feedback too.20:14
*** satish_ has quit IRC20:15
arnaudok tpatil_, sounds good to me. I tested the patch locally. from my perspective it is OK20:15
arnaudalso, it is one of our target for J-320:15
*** dims has joined #openstack-meeting-alt20:15
arnaud#link https://launchpad.net/glance/+milestone/juno-320:15
tpatil_great!!20:15
tpatil_yes20:15
arnaudso I am confident it will make it tpatil_20:15
tpatil_Thanks20:16
abhishekkarnaud:thank you20:16
*** otherwiseguy has quit IRC20:16
arnaudlet me update the LP BP to mark the status as Need reviews20:16
*** baoli has joined #openstack-meeting-alt20:17
arnaudnext we have20:18
*** matrohon has quit IRC20:18
arnaud#topic Use Launcher/ProcessLauncher to launch services20:18
*** openstack changes topic to "Use Launcher/ProcessLauncher to launch services (Meeting topic: glance)"20:18
arnaud#link https://review.openstack.org/#/c/110867/20:18
*** dims_ has quit IRC20:18
arnaudabhishekk, could you share a bit more what this is doing20:19
arnaudand why we need that in J-320:19
abhishekkarnaud:currently I have finished the integration and fixin of unittests20:19
tpatil_presently, glance api doesn't handle SIGHUP signal successfully so it cannot reload the updated configuration files.20:20
arnauddo you have the links to the patches handy?20:20
abhishekkyes,20:20
abhishekkhttps://review.openstack.org/#/c/110012/20:20
*** tpatil_ has quit IRC20:21
arnaudthanks abhishekk20:21
*** dims has quit IRC20:21
*** tpatil__ has joined #openstack-meeting-alt20:22
*** dims has joined #openstack-meeting-alt20:22
abhishekkyes with this we can able to use features like reload configuration on SIGHUP, graceful shutdown etc20:22
*** baoli has quit IRC20:22
arnaudok, let me look at the patch, I will discuss with Mark when he gets back20:23
*** emagana has quit IRC20:23
*** _nadya_ has quit IRC20:23
abhishekkok20:23
*** emagana has joined #openstack-meeting-alt20:23
tpatil__sounds good, Thanks20:23
arnaudthe feature freeze is20:24
*** georgelorch has quit IRC20:24
arnaudSeptember 4th20:24
arnaud#link https://wiki.openstack.org/wiki/Juno_Release_Schedule20:24
abhishekkyes with two weeks in hand20:25
arnaudyep20:25
nikhil___what's the doc freeze date?20:25
arnaudnot sure tbh20:25
nikhil___and do the(se) DocImapct patches get affected?20:25
nikhil___ok20:25
arnaud#action what's the doc freeze date20:26
rosmaitanikhil___: do you mean the string freeze?20:26
*** radez_g0n3 is now known as radez20:26
*** emagana_ has joined #openstack-meeting-alt20:27
arnaud#topic tasks20:27
*** openstack changes topic to "tasks (Meeting topic: glance)"20:27
nikhil___rosmaita: oh yes, that's the one20:27
arnaudnikhil___, I think we are very close to get it merged very soon :)20:27
nikhil___arnaud: sounds good :D20:27
*** emagana has quit IRC20:27
nikhil___gunna push up a PS later today!!20:27
arnaudI let some comments (mostly minor things)20:28
arnaudok20:28
nikhil___and willing to take on any other related work as necessary we need to get in j320:28
nikhil___like some more testing in glance20:28
rosmaitai think the string freeze is sept 1120:28
*** TravT has quit IRC20:28
nikhil___rosmaita: thanks! that's a relief20:28
arnaudok thanks rosmaita!20:28
nikhil___arnaud: do we target tempest tests for tasks in kilo 1/2 ?20:29
arnaudK-1 would be nice20:29
*** marun has quit IRC20:29
nikhil___and rather try to get glance client support in j320:29
arnaudas soon as we land your patch, I will focus on the task work20:30
nikhil___cool20:30
arnaudthe last bp in the list20:30
arnaudactually20:30
arnaudthe 2 lasts :)20:30
nikhil___#link https://review.openstack.org/#/c/48850/20:30
nikhil___needs rebase and some review (iiuc)20:30
arnaudare 1. GPFS store 2. metadefs20:30
arnaudnikhil___, let's merge first the glance side (your PS) + the task flow PS20:31
arnaudand then we can merge the client, sounds good?20:31
nikhil___ok20:31
*** morganfainberg is now known as morganfainberg_Z20:31
*** caleb_ has joined #openstack-meeting-alt20:32
arnaud#topic gpfs store20:32
*** openstack changes topic to "gpfs store (Meeting topic: glance)"20:32
arnaudanyone has been looking at the patch?20:32
*** dprince has quit IRC20:32
arnaud#link https://review.openstack.org/#/c/80182/20:32
*** TravT has joined #openstack-meeting-alt20:33
arnaudI will try to reach zhiyan since this is an IBM thing20:33
nikhil___yea20:33
arnaudthe problem that I can see with that is glance.store20:34
arnaudso, about glance.store, I started an email thread with flaper87|afk earlier this week20:34
arnaudto try to build the PS gaps20:34
*** atiwari has joined #openstack-meeting-alt20:34
arnaudso, I have been able to build the list for the vmware store, since I have been pushing all of the patches20:35
arnaudbut for the other stores, that's really hard to build the list20:35
arnaudbecause all of the stores haven't been merged at the same time into glance.store20:35
*** julim has quit IRC20:36
arnaud+ some changes happened in glance.store20:36
arnaudso far, we have this list20:36
arnaud#link https://etherpad.openstack.org/p/backports-glance.store20:36
arnaudbut that mostly contain vmware stuff20:36
arnaudso, it's not really relevant20:36
arnaudI am not sure what we want to do with it, flaper87|afk said that he is still working on the infra side20:37
arnaudso we will see...20:37
nikhil___he was also waiting for Mark20:37
arnaudok20:37
arnaudsounds good20:38
*** rm_work|away is now known as rm_work20:38
*** kebray has quit IRC20:38
arnaudok, so last thing we would like to see in J320:38
arnaud#topic metadefs20:38
*** openstack changes topic to "metadefs (Meeting topic: glance)"20:38
arnaudso, I started to look at the DB patch (most of things are fairly mechanical from my pov)20:39
arnaudI know the patches are regularly updated20:39
arnaudTravT, could you share an quick update with us?20:39
*** zeddii has quit IRC20:40
*** ijw has joined #openstack-meeting-alt20:40
*** TravT has quit IRC20:40
nikhil___:)20:40
arnaudnikhil___, have you been looking at the metadefs patches?20:41
nikhil___arnaud: :)20:41
*** ijw_ has joined #openstack-meeting-alt20:41
*** satish has quit IRC20:41
*** lakshmiS has joined #openstack-meeting-alt20:41
nikhil___was going to ask if you got a chance to test it on devstack20:41
wayne___we.re waiting for more re20:42
arnaudso, tbh, I tried to execute what TravT sent20:42
wayne___reviews20:42
arnaudbut it didn't work unfortunately20:42
nikhil___arnaud: my devstack was pre-occupied with tasks for the past few days however, can try this week20:42
nikhil___oh20:42
*** satish has joined #openstack-meeting-alt20:42
nikhil___glad you mentioned :)20:42
arnaudyes, I can imagine nikhil___20:43
*** colinmcnamara has joined #openstack-meeting-alt20:43
*** ijw__ has joined #openstack-meeting-alt20:43
*** ramashri has joined #openstack-meeting-alt20:43
lakshmiSCan you send us the issues you encountered20:43
arnaudI am going to look again at the DB layer tomorrow20:43
*** rudrarug_ has quit IRC20:43
arnaudlakshmiS, the script didn't work the first time somehow, and is not idempotent :)20:43
gokrokvearnaud: Sorry I stuck in a meeting20:43
gokrokvearnaud: But now I can talk :-)20:44
*** TravT has joined #openstack-meeting-alt20:44
*** radez is now known as radez_g0n320:44
arnaudit's failing to to create the patch in Horizon20:44
arnaudI have to manually git commit -a20:44
nikhil___arnaud: is horizon part planned for j3?20:44
*** ijw has quit IRC20:44
*** rudrarugge has joined #openstack-meeting-alt20:44
arnaudnikhil___, I think that's the goal yes20:44
wayne___in process of changes per last review20:45
nikhil___oh20:45
lakshmiSYeah the script was a quickly written.20:45
*** thomasem has joined #openstack-meeting-alt20:45
*** thomasem has quit IRC20:45
TravTsorry keep getting disconnected.20:45
arnaudnp TravT :)20:45
*** kebray has joined #openstack-meeting-alt20:45
*** ijw_ has quit IRC20:46
*** thomasem has joined #openstack-meeting-alt20:46
TravTthe patches for horizon are approved for j320:46
arnaudok20:46
TravThave gotten a couple reviews on one of them and addressed.20:46
arnaudTravT, is there a spec for Horizon?20:46
TravTbut are dependent on client20:46
TravTyeah. blurprints.20:46
arnaudcould you share the link here?20:47
TravThorizon doesn't use specs yet.20:47
TravTlet me find them20:47
arnaudok ok20:47
TravTjust a sec (on phone)20:47
*** morganfainberg_Z is now known as morganfainberg20:47
nikhil___arnaud: metadefs on my list after tasks20:48
arnaudsounds great nikhil___20:48
nikhil___am guessing(hoping) that we do not have artifacts for j320:48
*** ijw__ has quit IRC20:48
TravTon this page #link https://launchpad.net/horizon/+milestone/juno-320:48
*** stevebaker has quit IRC20:49
*** stevebaker has joined #openstack-meeting-alt20:49
*** malini has quit IRC20:49
arnaudok thanks TravT20:49
*** colinmcnamara has quit IRC20:49
TravTany assigned to pawel skowron or me20:49
TravTarnaud: if you have problems with script send in email. I will addrezz20:50
arnaudok TravT20:51
*** wayne___ has quit IRC20:51
arnaud#topic open discussion20:51
*** openstack changes topic to "open discussion (Meeting topic: glance)"20:51
*** lakshmiS has quit IRC20:52
arnaudanyone? :)20:52
nikhil___arnaud: can we compile a list of reviews to be done for j3 so that they can be distributed amongst reviewers and priorotized?20:52
arnaudyes20:52
*** esker has quit IRC20:52
nikhil___etherpad would be nice if gerrit does not support such a functionality20:52
arnaudI will build that list20:53
arnaudand send it to the ML20:53
nikhil___awesome20:53
nikhil___thank you!20:53
arnaudnp20:53
*** thangp has quit IRC20:53
*** lukego has quit IRC20:53
arnaudok, I think we can go back to reviews now :)20:53
arnaudthanks20:53
arnaud#endmeeting20:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:53
openstackMeeting ended Thu Aug 21 20:53:52 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-08-21-20.00.html20:53
abhishekkthank you20:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-08-21-20.00.txt20:53
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-08-21-20.00.log.html20:53
*** SumitNaiksatam has quit IRC20:54
*** abhishekk has quit IRC20:54
*** alazarev has quit IRC20:57
*** gokrokve has quit IRC20:57
*** padkrish has quit IRC20:57
*** megan_w_ has quit IRC20:57
*** alazarev has joined #openstack-meeting-alt20:58
*** megan_w_ has joined #openstack-meeting-alt20:58
*** ijw has joined #openstack-meeting-alt21:01
*** stevebaker has quit IRC21:01
*** stevebaker has joined #openstack-meeting-alt21:02
*** megan_w_ has quit IRC21:02
*** caleb_ has quit IRC21:02
*** mattgriffin has joined #openstack-meeting-alt21:03
*** caleb_ has joined #openstack-meeting-alt21:04
*** ijw has quit IRC21:05
*** TravT has left #openstack-meeting-alt21:05
*** tdruiva has quit IRC21:06
*** manishg has joined #openstack-meeting-alt21:08
*** bswartz has quit IRC21:09
*** tdruiva has joined #openstack-meeting-alt21:09
*** ijw has joined #openstack-meeting-alt21:11
*** ijw has joined #openstack-meeting-alt21:11
*** niclem has quit IRC21:11
*** emagana_ has quit IRC21:16
*** emagana has joined #openstack-meeting-alt21:16
*** padkrish has joined #openstack-meeting-alt21:17
*** baoli has joined #openstack-meeting-alt21:18
*** megan_w_ has joined #openstack-meeting-alt21:18
*** beagles has quit IRC21:18
*** mestery has joined #openstack-meeting-alt21:19
*** caleb_ has quit IRC21:20
*** emagana has quit IRC21:21
*** julienvey has quit IRC21:22
*** baoli has quit IRC21:23
*** beagles has joined #openstack-meeting-alt21:24
*** beagles is now known as Guest599321:24
*** mestery has quit IRC21:25
*** banix_ has joined #openstack-meeting-alt21:26
*** gokrokve has joined #openstack-meeting-alt21:28
*** SumitNaiksatam has joined #openstack-meeting-alt21:28
*** ruebenramirez has quit IRC21:29
*** caleb_ has joined #openstack-meeting-alt21:29
*** banix has quit IRC21:30
*** banix_ is now known as banix21:30
*** mfer has quit IRC21:30
*** tpatil__ has quit IRC21:31
*** emagana has joined #openstack-meeting-alt21:35
*** luizfar has quit IRC21:35
*** luizfar has joined #openstack-meeting-alt21:35
*** tbarron has quit IRC21:35
*** otherwiseguy has joined #openstack-meeting-alt21:38
*** caleb_` has joined #openstack-meeting-alt21:38
*** stannie has quit IRC21:40
*** caleb_ has quit IRC21:41
*** armax has quit IRC21:47
*** eankutse has quit IRC21:51
*** emagana has quit IRC21:51
*** emagana has joined #openstack-meeting-alt21:52
*** caleb_` has quit IRC21:55
*** rbenali has joined #openstack-meeting-alt21:56
*** emagana has quit IRC21:56
*** tonytan4ever has quit IRC21:57
*** Sukhdev has joined #openstack-meeting-alt21:57
*** emagana has joined #openstack-meeting-alt21:57
*** bradjones has quit IRC21:58
*** Guest5993 is now known as b3nt_pin22:01
*** megan_w_ has quit IRC22:01
*** satish has quit IRC22:01
*** megan_w_ has joined #openstack-meeting-alt22:02
*** banix has quit IRC22:03
*** dtx00ff has quit IRC22:03
*** megan_w_ has quit IRC22:06
*** marcoemorais has quit IRC22:07
*** marcoemorais has joined #openstack-meeting-alt22:07
*** flaviof is now known as flaviof_zzz22:07
*** betsy has quit IRC22:08
*** marcoemorais has quit IRC22:09
*** marcoemorais has joined #openstack-meeting-alt22:10
*** marcoemorais has quit IRC22:10
*** marcoemorais has joined #openstack-meeting-alt22:11
*** marcoemorais has quit IRC22:11
*** marcoemorais has joined #openstack-meeting-alt22:11
*** rbenali has quit IRC22:11
*** gokrokve_ has joined #openstack-meeting-alt22:12
*** emagana has quit IRC22:15
*** gokrokve has quit IRC22:15
*** emagana has joined #openstack-meeting-alt22:15
*** jaypipes has quit IRC22:16
*** armax has joined #openstack-meeting-alt22:16
*** marun has joined #openstack-meeting-alt22:17
*** gduan has quit IRC22:17
*** mjturek has quit IRC22:17
*** baoli has joined #openstack-meeting-alt22:19
*** emagana has quit IRC22:20
*** emagana has joined #openstack-meeting-alt22:22
*** baoli has quit IRC22:23
*** thomasem has quit IRC22:24
*** bradjones has joined #openstack-meeting-alt22:25
*** bradjones has quit IRC22:25
*** bradjones has joined #openstack-meeting-alt22:25
*** dtx00ff has joined #openstack-meeting-alt22:28
*** marcoemorais has quit IRC22:31
*** marcoemorais has joined #openstack-meeting-alt22:31
*** marcoemorais has quit IRC22:31
*** marcoemorais has joined #openstack-meeting-alt22:32
*** dtx00ff has quit IRC22:32
*** marcoemorais has quit IRC22:32
*** dtx00ff has joined #openstack-meeting-alt22:32
*** marcoemorais has joined #openstack-meeting-alt22:33
*** emagana has quit IRC22:35
*** emagana has joined #openstack-meeting-alt22:36
*** marcoemorais has quit IRC22:36
*** marcoemorais has joined #openstack-meeting-alt22:37
*** Leonr has quit IRC22:37
*** Haiying has joined #openstack-meeting-alt22:38
*** emagana has quit IRC22:40
*** elo has quit IRC22:40
*** elo has joined #openstack-meeting-alt22:42
*** emagana has joined #openstack-meeting-alt22:42
*** jjmb has joined #openstack-meeting-alt22:42
*** tnurlygayanov_ has joined #openstack-meeting-alt22:49
*** Haiying has quit IRC22:50
*** malini has joined #openstack-meeting-alt22:50
*** ijw has quit IRC22:51
*** shakamunyi has joined #openstack-meeting-alt22:51
*** ijw has joined #openstack-meeting-alt22:52
*** scott-millward has joined #openstack-meeting-alt22:53
*** tdruiva has quit IRC22:53
*** ijw_ has joined #openstack-meeting-alt22:54
*** manishg has left #openstack-meeting-alt22:54
*** padkrish has quit IRC22:54
*** tchaypo has left #openstack-meeting-alt22:54
*** ijw has quit IRC22:57
*** ijw_ has quit IRC23:01
*** ijw has joined #openstack-meeting-alt23:01
*** dtx00ff has quit IRC23:03
*** dimtruck is now known as zz_dimtruck23:03
*** dtx00ff has joined #openstack-meeting-alt23:04
*** mattgriffin has quit IRC23:05
*** colinmcnamara has joined #openstack-meeting-alt23:08
*** marcoemorais has quit IRC23:10
*** marcoemorais has joined #openstack-meeting-alt23:10
*** atiwari has quit IRC23:11
*** pballand has quit IRC23:11
*** otherwiseguy has quit IRC23:11
*** rcleere has quit IRC23:12
*** padkrish has joined #openstack-meeting-alt23:13
*** luizfar has quit IRC23:13
*** marcoemorais has quit IRC23:14
*** marcoemorais has joined #openstack-meeting-alt23:14
*** otherwiseguy has joined #openstack-meeting-alt23:15
*** Sukhdev has quit IRC23:17
*** colinmcnamara has quit IRC23:20
*** baoli has joined #openstack-meeting-alt23:20
*** nelsnelson has quit IRC23:20
*** Sukhdev has joined #openstack-meeting-alt23:23
*** _nadya_ has joined #openstack-meeting-alt23:24
*** baoli has quit IRC23:24
*** ijw_ has joined #openstack-meeting-alt23:25
*** luizfar has joined #openstack-meeting-alt23:26
*** emagana has quit IRC23:28
*** _nadya_ has quit IRC23:28
*** ijw has quit IRC23:28
*** emagana has joined #openstack-meeting-alt23:28
*** bdpayne has quit IRC23:30
*** emagana has quit IRC23:31
*** chuckC_ has quit IRC23:31
*** emagana has joined #openstack-meeting-alt23:31
*** bdpayne has joined #openstack-meeting-alt23:33
*** bdpayne has quit IRC23:33
*** kevinconway has quit IRC23:33
*** tnurlygayanov_ has quit IRC23:34
*** ijw_ has quit IRC23:35
*** ijw has joined #openstack-meeting-alt23:35
*** teran has joined #openstack-meeting-alt23:36
*** alazarev has quit IRC23:37
*** david-lyle has quit IRC23:41
*** Barker has joined #openstack-meeting-alt23:41
*** alex_xu has quit IRC23:42
*** ijw has quit IRC23:45
*** ijw has joined #openstack-meeting-alt23:48
*** nelsnelson has joined #openstack-meeting-alt23:49
*** padkrish has quit IRC23:51
*** gokrokve has joined #openstack-meeting-alt23:53
*** gokrokve_ has quit IRC23:53
*** luizfar has quit IRC23:58
*** kebray has quit IRC23:58
*** gokrokve has quit IRC23:58
*** tdruiva has joined #openstack-meeting-alt23:59
*** otherwiseguy has quit IRC23:59
*** tdruiva has quit IRC23:59
*** alkari has quit IRC23:59
*** oomichi has joined #openstack-meeting-alt23:59

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