Wednesday, 2015-01-14

*** VW_ has quit IRC00:01
*** alexsyip_ has joined #openstack-meeting-300:04
*** armax_ has joined #openstack-meeting-300:04
*** Sukhdev has quit IRC00:05
*** rcleere is now known as rcleere_away00:06
*** ivar-laz_ has quit IRC00:08
*** ivar-lazzaro has joined #openstack-meeting-300:08
*** alexsyip has quit IRC00:09
*** cloudtoa_ has quit IRC00:09
*** armax has quit IRC00:09
*** pkarikh has quit IRC00:09
*** dstanek has quit IRC00:09
*** dstanek has joined #openstack-meeting-300:09
*** armax_ is now known as armax00:09
*** alexsyip_ is now known as alexsyip00:09
*** ivar-lazzaro has quit IRC00:09
*** ivar-lazzaro has joined #openstack-meeting-300:10
*** victor_lowther has joined #openstack-meeting-300:10
*** jraim has joined #openstack-meeting-300:10
*** Longgeek has quit IRC00:10
*** pkarikh has joined #openstack-meeting-300:12
*** VW_ has joined #openstack-meeting-300:17
*** yapeng has joined #openstack-meeting-300:21
*** ctracey has joined #openstack-meeting-300:23
*** yapeng has quit IRC00:26
*** markmcclain has joined #openstack-meeting-300:26
*** markmcclain has quit IRC00:27
*** markmcclain1 has joined #openstack-meeting-300:27
*** david-lyle has joined #openstack-meeting-300:28
*** markmcclain1 has quit IRC00:29
*** markmcclain has joined #openstack-meeting-300:29
*** carl_baldwin has quit IRC00:37
*** tomoe has joined #openstack-meeting-300:38
*** aweeks has joined #openstack-meeting-300:41
*** ameade has joined #openstack-meeting-300:44
*** zhiyan has joined #openstack-meeting-300:48
*** markmcclain has quit IRC00:48
*** sunny_ has joined #openstack-meeting-300:49
*** xuhanp has joined #openstack-meeting-300:49
*** sunny_ has quit IRC00:49
*** sunny_ has joined #openstack-meeting-300:50
*** banix has joined #openstack-meeting-300:50
*** rossella_s has quit IRC00:52
*** jraim has quit IRC00:54
*** dougwig has quit IRC00:54
*** rossella_s has joined #openstack-meeting-300:54
*** markmcclain has joined #openstack-meeting-300:57
*** markmcclain has quit IRC00:58
*** david-lyle has quit IRC00:58
*** markmcclain has joined #openstack-meeting-300:58
*** dougwig has joined #openstack-meeting-300:58
*** david-lyle has joined #openstack-meeting-300:58
*** markmcclain has quit IRC01:00
*** jraim has joined #openstack-meeting-301:00
*** VW_ has quit IRC01:00
*** bpokorny_ has joined #openstack-meeting-301:01
*** xuhanp has quit IRC01:03
*** david-lyle has quit IRC01:05
*** sigmavirus24_awa is now known as sigmavirus2401:05
*** bpokorny has quit IRC01:05
*** rossella_s has quit IRC01:07
*** rossella_s has joined #openstack-meeting-301:08
*** david-lyle has joined #openstack-meeting-301:09
*** sigmavirus24 is now known as sigmavirus24_awa01:11
*** jraim has quit IRC01:13
*** shakamunyi has quit IRC01:13
*** banix has quit IRC01:14
*** GLaupre has joined #openstack-meeting-301:17
*** stanzgy has joined #openstack-meeting-301:18
*** jraim has joined #openstack-meeting-301:19
*** david-lyle has quit IRC01:24
*** ivar-lazzaro has quit IRC01:28
*** ivar-lazzaro has joined #openstack-meeting-301:29
*** david-lyle has joined #openstack-meeting-301:29
*** lsmola has quit IRC01:31
*** bpokorny has joined #openstack-meeting-301:31
*** lsmola has joined #openstack-meeting-301:32
*** bpokorn__ has joined #openstack-meeting-301:32
*** plaurin_ has joined #openstack-meeting-301:33
*** bpokorny_ has quit IRC01:34
*** Sukhdev has joined #openstack-meeting-301:34
*** david-lyle has quit IRC01:35
*** bpokorny has quit IRC01:35
*** markmcclain has joined #openstack-meeting-301:37
*** markmcclain has quit IRC01:38
*** markmcclain has joined #openstack-meeting-301:38
*** banix has joined #openstack-meeting-301:38
*** lazy_prince has quit IRC01:41
*** lazy_prince has joined #openstack-meeting-301:41
*** salv-orlando has quit IRC01:41
*** yapeng has joined #openstack-meeting-301:47
*** sunny_ has quit IRC01:47
*** sunny_ has joined #openstack-meeting-301:50
*** david-lyle has joined #openstack-meeting-301:52
*** sigmavirus24_awa is now known as sigmavirus2401:53
*** rossella_s has quit IRC01:53
*** Longgeek has joined #openstack-meeting-301:55
*** rossella_s has joined #openstack-meeting-301:56
*** banix has quit IRC01:57
*** Piet has joined #openstack-meeting-301:57
*** bpokorn__ has quit IRC01:59
*** david-lyle has quit IRC01:59
*** markmcclain has quit IRC01:59
*** salv-orlando has joined #openstack-meeting-302:00
*** yapeng has quit IRC02:01
*** baoli has quit IRC02:04
*** aweeks has quit IRC02:05
*** zhiyan has quit IRC02:05
*** aweeks has joined #openstack-meeting-302:06
*** zhiyan has joined #openstack-meeting-302:06
*** Longgeek has quit IRC02:11
*** vishy has quit IRC02:11
*** alexsyip has quit IRC02:11
*** baoli has joined #openstack-meeting-302:12
*** edleafe has quit IRC02:13
*** cyeoh has quit IRC02:14
*** sarob has quit IRC02:14
*** sunny_ has quit IRC02:14
*** banix has joined #openstack-meeting-302:14
*** vishy has joined #openstack-meeting-302:15
*** cyeoh has joined #openstack-meeting-302:15
*** ChuckC_ has joined #openstack-meeting-302:16
*** edleafe has joined #openstack-meeting-302:17
*** Rockyg has quit IRC02:18
*** salv-orlando has quit IRC02:19
*** ChuckC has quit IRC02:20
*** julim has quit IRC02:24
*** mwagner_lap has quit IRC02:29
*** yamahata has quit IRC02:31
*** wuhg has joined #openstack-meeting-302:35
*** baoli has quit IRC02:36
*** ivar-laz_ has joined #openstack-meeting-302:39
*** david-lyle has joined #openstack-meeting-302:40
*** mwagner_lap has joined #openstack-meeting-302:41
*** shakamunyi has joined #openstack-meeting-302:41
*** markmcclain has joined #openstack-meeting-302:42
*** ivar-lazzaro has quit IRC02:42
*** markmcclain has quit IRC02:42
*** markmcclain has joined #openstack-meeting-302:42
*** ivar-laz_ has quit IRC02:43
*** sc68cal has quit IRC02:46
*** sc68cal has joined #openstack-meeting-302:47
*** cyeoh has quit IRC02:47
*** shakamunyi has quit IRC02:47
*** lbragstad has quit IRC02:47
*** russellb has quit IRC02:47
*** shakamunyi has joined #openstack-meeting-302:48
*** cyeoh has joined #openstack-meeting-302:48
*** markmcclain has quit IRC02:49
*** markmcclain has joined #openstack-meeting-302:49
*** ctracey has quit IRC02:52
*** victor_lowther has quit IRC02:54
*** zhiyan has quit IRC02:55
*** lbragstad has joined #openstack-meeting-302:55
*** zhiyan has joined #openstack-meeting-302:57
*** ctracey has joined #openstack-meeting-302:58
*** jroll has quit IRC03:00
*** victor_lowther has joined #openstack-meeting-303:00
*** ChuckC has joined #openstack-meeting-303:00
*** russellb has joined #openstack-meeting-303:02
*** gduan has joined #openstack-meeting-303:03
*** garyduan has quit IRC03:04
*** ChuckC_ has quit IRC03:04
*** shakamunyi has quit IRC03:05
*** lbragstad has quit IRC03:08
*** lbragstad has joined #openstack-meeting-303:10
*** jroll has joined #openstack-meeting-303:10
*** russellb has quit IRC03:15
*** Sukhdev has quit IRC03:18
*** jraim has quit IRC03:18
*** plaurin_ has quit IRC03:18
*** jraim has joined #openstack-meeting-303:19
*** yamamoto_ has joined #openstack-meeting-303:21
*** yamahata has joined #openstack-meeting-303:24
*** david-lyle has quit IRC03:25
*** russellb has joined #openstack-meeting-303:25
*** jroll has quit IRC03:26
*** markmcclain has quit IRC03:28
*** aweeks has quit IRC03:29
*** aweeks has joined #openstack-meeting-303:31
*** jroll has joined #openstack-meeting-303:32
*** bauzas has quit IRC03:37
*** clu_ has quit IRC03:38
*** russellb has quit IRC03:38
*** lbragstad has quit IRC03:38
*** bauzas has joined #openstack-meeting-303:39
*** russellb has joined #openstack-meeting-303:39
*** rossella_s has quit IRC03:40
*** comstud has quit IRC03:40
*** comstud has joined #openstack-meeting-303:41
*** salv-orlando has joined #openstack-meeting-303:43
*** rossella_s has joined #openstack-meeting-303:43
*** jraim has quit IRC03:45
*** jraim has joined #openstack-meeting-303:47
*** lbragstad has joined #openstack-meeting-303:47
*** Longgeek has joined #openstack-meeting-303:51
*** amotoki has joined #openstack-meeting-303:53
*** lbragstad has quit IRC04:00
*** rossella_s has quit IRC04:00
*** lbragstad has joined #openstack-meeting-304:02
*** salv-orlando has quit IRC04:02
*** bauzas has quit IRC04:02
*** bauzas has joined #openstack-meeting-304:03
*** bauzas has quit IRC04:07
*** rossella_s has joined #openstack-meeting-304:07
*** markmcclain has joined #openstack-meeting-304:09
*** markmcclain has quit IRC04:10
*** markmcclain1 has joined #openstack-meeting-304:10
*** sigmavirus24 is now known as sigmavirus24_awa04:11
*** arosen has joined #openstack-meeting-304:13
*** bauzas has joined #openstack-meeting-304:14
*** carl_baldwin has joined #openstack-meeting-304:17
*** arosen has quit IRC04:18
*** bauzas has quit IRC04:19
*** sbalukoff has quit IRC04:23
*** bauzas has joined #openstack-meeting-304:30
*** rossella_s has quit IRC04:34
*** flwang has quit IRC04:34
*** sbalukoff has joined #openstack-meeting-304:34
*** salv-orlando has joined #openstack-meeting-304:35
*** rossella_s has joined #openstack-meeting-304:38
*** yamahata has quit IRC04:38
*** yamahata has joined #openstack-meeting-304:39
*** salv-orlando has quit IRC04:39
*** flwang has joined #openstack-meeting-304:41
*** Longgeek has quit IRC04:42
*** bauzas has quit IRC04:42
*** bauzas has joined #openstack-meeting-304:43
*** aleksandr_null has quit IRC04:43
*** Longgeek has joined #openstack-meeting-304:44
*** aleksandr_null has joined #openstack-meeting-304:44
*** markmcclain1 has quit IRC04:45
*** carl_baldwin has quit IRC04:45
*** vishy has quit IRC04:57
*** bauzas has quit IRC04:58
*** banix has quit IRC04:58
*** bauzas has joined #openstack-meeting-305:01
*** vishy has joined #openstack-meeting-305:03
*** lazy_prince is now known as killer_prince05:07
*** Sukhdev_ has joined #openstack-meeting-305:11
*** rossella_s has quit IRC05:12
*** sarob has joined #openstack-meeting-305:15
*** rossella_s has joined #openstack-meeting-305:16
*** sarob has quit IRC05:19
*** zigo has quit IRC05:20
*** zigo has joined #openstack-meeting-305:21
*** rossella_s has quit IRC05:36
*** rossella_s has joined #openstack-meeting-305:36
*** comstud has quit IRC05:38
*** comstud has joined #openstack-meeting-305:41
*** russellb has quit IRC05:49
*** russellb has joined #openstack-meeting-305:49
*** lbragstad has quit IRC05:52
*** bauzas has quit IRC05:53
*** lbragstad has joined #openstack-meeting-305:55
*** bauzas has joined #openstack-meeting-306:00
*** Longgeek has quit IRC06:19
*** salv-orlando has joined #openstack-meeting-306:26
*** baoli has joined #openstack-meeting-306:32
*** Longgeek has joined #openstack-meeting-306:34
*** baoli has quit IRC06:35
*** baoli has joined #openstack-meeting-306:36
*** salv-orlando has quit IRC06:46
*** salv-orlando has joined #openstack-meeting-306:51
*** salv-orlando has quit IRC06:52
*** Longgeek has quit IRC06:53
*** mrunge has joined #openstack-meeting-306:53
*** belmoreira has joined #openstack-meeting-306:57
*** Longgeek has joined #openstack-meeting-306:59
*** JeanBriceCombebi has joined #openstack-meeting-307:02
*** enikanorov__ has quit IRC07:08
*** zhiyan has quit IRC07:08
*** Sukhdev_ has quit IRC07:11
*** zhiyan has joined #openstack-meeting-307:11
*** baoli has quit IRC07:18
*** bauzas has quit IRC07:18
*** armax has quit IRC07:22
*** bauzas has joined #openstack-meeting-307:25
*** iovadia has joined #openstack-meeting-307:28
*** iovadia has quit IRC07:28
*** iovadia has joined #openstack-meeting-307:29
*** yamahata has quit IRC07:29
*** iovadia has joined #openstack-meeting-307:29
*** iovadia has quit IRC07:30
*** iovadia has joined #openstack-meeting-307:30
*** iovadia has quit IRC07:36
*** iovadia has joined #openstack-meeting-307:36
*** iovadia has left #openstack-meeting-307:36
*** iovadia has joined #openstack-meeting-307:36
*** russellb has quit IRC07:37
*** salv-orlando has joined #openstack-meeting-307:38
*** salv-orlando has quit IRC07:39
*** russellb has joined #openstack-meeting-307:40
*** Sukhdev has joined #openstack-meeting-307:44
*** sahid has joined #openstack-meeting-308:02
*** crimmson has joined #openstack-meeting-308:02
*** crimmson has quit IRC08:03
*** GLaupre_ has joined #openstack-meeting-308:03
*** jtomasek has joined #openstack-meeting-308:04
*** iovadia has quit IRC08:06
*** Sukhdev has quit IRC08:13
*** jcoufal has joined #openstack-meeting-308:18
*** sahid has quit IRC08:20
*** sandr8 has quit IRC08:21
*** aleksandr_null has quit IRC08:22
*** GLaupre_ has quit IRC08:22
*** killer_prince is now known as lazy_prince08:22
*** lbragstad has quit IRC08:24
*** marun has quit IRC08:24
*** belmoreira has quit IRC08:26
*** sahid has joined #openstack-meeting-308:27
*** wdutch has joined #openstack-meeting-308:30
*** russellb has quit IRC08:30
*** cyeoh has quit IRC08:30
*** cyeoh has joined #openstack-meeting-308:31
*** lbragstad has joined #openstack-meeting-308:34
*** aleksandr_null has joined #openstack-meeting-308:36
*** sandr8 has joined #openstack-meeting-308:37
*** marun has joined #openstack-meeting-308:38
*** russellb has joined #openstack-meeting-308:39
*** cyeoh has quit IRC08:43
*** safchain has joined #openstack-meeting-308:45
*** matrohon has joined #openstack-meeting-308:46
*** cyeoh has joined #openstack-meeting-308:46
*** watanabe_isao has quit IRC08:47
*** jcoufal has quit IRC08:54
*** jcoufal has joined #openstack-meeting-308:54
*** salv-orlando has joined #openstack-meeting-308:57
*** sbalukoff has quit IRC09:00
*** egallen has joined #openstack-meeting-309:00
*** zz_ttrifonov is now known as ttrifonov09:03
*** salv-orlando has quit IRC09:11
*** sbalukoff has joined #openstack-meeting-309:15
*** mrunge has quit IRC09:16
*** pkoniszewski has joined #openstack-meeting-309:19
*** mrunge has joined #openstack-meeting-309:22
*** MaxV has joined #openstack-meeting-309:24
*** iovadia has joined #openstack-meeting-309:26
*** iovadia has left #openstack-meeting-309:27
*** MaxV has quit IRC09:27
*** MaxV has joined #openstack-meeting-309:27
*** igordcard has joined #openstack-meeting-309:29
*** bluex-pl has joined #openstack-meeting-309:31
*** bluex-pl has quit IRC09:34
*** bluex-pl has joined #openstack-meeting-309:35
*** bluex-pl has quit IRC09:35
*** bluex-pl has joined #openstack-meeting-309:36
*** salv-orlando has joined #openstack-meeting-309:51
*** vishy has quit IRC09:59
*** coolsvap|afk is now known as coolsvap09:59
*** zaro has quit IRC10:04
*** devananda has quit IRC10:04
*** zaro has joined #openstack-meeting-310:08
*** vishy has joined #openstack-meeting-310:10
*** devananda has joined #openstack-meeting-310:10
*** vishy has quit IRC10:21
*** russellb has quit IRC10:22
*** russellb has joined #openstack-meeting-310:26
*** yamamoto_ has quit IRC10:30
*** vishy has joined #openstack-meeting-310:35
*** bluex-pl has left #openstack-meeting-310:35
*** coolsvap is now known as coolsvap|afk10:39
*** coolsvap|afk is now known as coolsvap10:51
*** stanzgy has quit IRC10:53
*** russellb has quit IRC11:00
*** coolsvap is now known as coolsvap|afk11:02
*** alexpilotti has joined #openstack-meeting-311:03
*** russellb has joined #openstack-meeting-311:06
*** coolsvap|afk is now known as coolsvap11:09
*** mrunge has quit IRC11:21
*** GLaupre has quit IRC11:23
*** mrunge has joined #openstack-meeting-311:24
*** sahid has quit IRC11:33
*** lazy_prince is now known as killer_prince11:42
*** yamamoto has joined #openstack-meeting-311:44
*** yamamoto has quit IRC11:44
*** sahid has joined #openstack-meeting-311:55
*** mwagner_lap has quit IRC12:00
*** JeanBriceCombebi has quit IRC12:19
*** xuhanp has joined #openstack-meeting-312:25
*** isviridov_away is now known as isviridov12:32
*** vineetmenon has joined #openstack-meeting-312:36
vineetmenonalaski: if you don't mind, please go thru this https://etherpad.openstack.org/p/Scheduling_ver_0.0912:37
vineetmenonit's a bit different from what you are proposing, but have a look nonetheless12:37
*** tomoe has quit IRC12:40
*** vineetmenon has quit IRC12:42
*** enikanorov_ has joined #openstack-meeting-312:43
*** tomoe has joined #openstack-meeting-312:44
*** egallen_ has joined #openstack-meeting-312:44
*** MaxV has quit IRC12:44
*** sergef has joined #openstack-meeting-312:45
*** egallen has quit IRC12:46
*** egallen_ is now known as egallen12:46
*** zhipeng has joined #openstack-meeting-313:02
*** egallen has quit IRC13:04
*** amotoki_ has joined #openstack-meeting-313:07
*** egallen has joined #openstack-meeting-313:08
*** sahid has quit IRC13:10
*** MaxV has joined #openstack-meeting-313:12
*** baoli has joined #openstack-meeting-313:24
*** baoli has quit IRC13:27
*** baoli has joined #openstack-meeting-313:28
*** sahid has joined #openstack-meeting-313:29
*** Networkn3rd has quit IRC13:33
*** mwagner_lap has joined #openstack-meeting-313:33
*** mestery has quit IRC13:33
*** JeanBriceCombebi has joined #openstack-meeting-313:37
*** devvesa has joined #openstack-meeting-313:42
*** JeanBriceCombebi has quit IRC13:44
*** JeanBriceCombebi has joined #openstack-meeting-313:46
*** sergef has quit IRC13:47
*** egallen_ has joined #openstack-meeting-313:49
*** egallen has quit IRC13:49
*** egallen_ is now known as egallen13:49
*** sigmavirus24_awa is now known as sigmavirus2413:50
*** egallen has quit IRC13:55
*** egallen has joined #openstack-meeting-313:56
*** jcoufal_ has joined #openstack-meeting-314:00
*** julim has joined #openstack-meeting-314:02
*** mestery has joined #openstack-meeting-314:02
*** jcoufal has quit IRC14:02
*** mattfarina has joined #openstack-meeting-314:11
*** banix has joined #openstack-meeting-314:18
*** banix has quit IRC14:21
*** plaurin_ has joined #openstack-meeting-314:26
*** peristeri has joined #openstack-meeting-314:29
*** lblanchard has joined #openstack-meeting-314:30
*** yamahata has joined #openstack-meeting-314:32
*** vineetmenon has joined #openstack-meeting-314:35
*** thomasem has joined #openstack-meeting-314:35
*** mestery has quit IRC14:39
*** armax has joined #openstack-meeting-314:39
*** yamahata has quit IRC14:44
*** yamahata has joined #openstack-meeting-314:45
*** jgrimm is now known as zz_jgrimm14:46
*** armax has quit IRC14:50
*** JeanBriceCombebi has quit IRC14:53
*** JeanBriceCombebi has joined #openstack-meeting-314:53
*** carl_baldwin has joined #openstack-meeting-314:55
*** egallen has quit IRC14:56
*** baoli has quit IRC14:59
*** annegentle_ has joined #openstack-meeting-315:00
*** Sam-I-Am has joined #openstack-meeting-315:00
Sam-I-Amhello15:00
annegentle_hiya15:00
annegentle_zigo: over here ok?15:00
*** egallen has joined #openstack-meeting-315:00
annegentle_ok this one has meetbot, yay15:00
annegentle_#startmeeting Doc Team15:00
openstackMeeting started Wed Jan 14 15:00:50 2015 UTC and is due to finish in 60 minutes.  The chair is annegentle_. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** alexadamov has joined #openstack-meeting-315:00
openstackThe meeting name has been set to 'doc_team'15:00
annegentle_woops15:01
annegentle_#endmeeting15:01
openstackMeeting ended Wed Jan 14 15:01:13 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/doc_team/2015/doc_team.2015-01-14-15.00.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/doc_team/2015/doc_team.2015-01-14-15.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/doc_team/2015/doc_team.2015-01-14-15.00.log.html15:01
annegentle_#startmeeting docteam15:01
openstackMeeting started Wed Jan 14 15:01:24 2015 UTC and is due to finish in 60 minutes.  The chair is annegentle_. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
annegentle_whew15:01
openstackThe meeting name has been set to 'docteam'15:01
annegentle_welcome to 201515:01
annegentle_#topic Action items from last meeting15:01
annegentle_that was sooo long ago :)15:01
Sam-I-Ambeen a while15:01
*** vineetmenon has quit IRC15:02
annegentle_no actions from last time15:02
annegentle_way back in 201415:02
annegentle_moving on15:02
*** zigo2 has joined #openstack-meeting-315:02
annegentle_#topic Specs ready15:02
zigo2hi15:02
annegentle_hi zigo215:02
annegentle_we'll get to install guide in a few15:02
annegentle_I approved the web design spec15:02
annegentle_So the remaining spec for "just" docs is the driver docs15:03
annegentle_doesn't look like we have Andreas here15:03
*** baoli has joined #openstack-meeting-315:03
annegentle_but he sounded like he was hesitant that we hadn't talked to enough driver doc owners15:03
annegentle_my sense is that we need to go forward with the spec and we've shopped it enough15:03
annegentle_so I hope to check in with Andreas and approve it this week15:03
annegentle_#link https://review.openstack.org/#/c/133372/15:04
annegentle_that is the spec15:04
annegentle_ah, it's Tom who's hesitant15:04
*** vineetmenon has joined #openstack-meeting-315:04
annegentle_he has a 2-phase approach that seems reasonable15:04
annegentle_hopefully Andreas can circle back on that15:04
annegentle_Other specs in review are for training, anyone from training want to speak to those?15:04
Sam-I-Ami havent seen him much lately15:05
annegentle_yeah me neither15:05
annegentle_just on epiphany15:05
annegentle_No sarob, surely too early for him15:05
*** pcarver has quit IRC15:05
*** thangp has joined #openstack-meeting-315:05
annegentle_Any other discussion on specs for this release?15:05
*** KLevenstein has joined #openstack-meeting-315:06
annegentle_There's also the networking guide spec from last release being worked this release, I'll leave that for the specialty team reports15:06
annegentle_#topic Specialty teams reports15:06
*** rromans has joined #openstack-meeting-315:06
Sam-I-Amnetworking is here15:06
annegentle_Networking, want to go ahead with the latest? I do appreciate the mailing list posts.15:06
annegentle_go ahead Sam-I-Am15:06
Sam-I-Amsure15:06
Sam-I-Amwe're back to weekly meetings again and met last friday.15:06
*** VW_ has joined #openstack-meeting-315:07
Sam-I-Ami finished the neutron dvr scenario and sent it to the SMEs for review mid-december15:07
Sam-I-Ami received comments and applied some, but still looking for more details on some issues15:07
Sam-I-Ammeanwhile, sean collins has started the provider networking scenario15:07
Sam-I-Amphil is working on converting his L3 HA scenario to the structure used by the other scenarios15:07
Sam-I-Ami'm working on the classic/legacy neutron scenario15:08
Sam-I-Amhopefully most of not all of these scenarios will be ready for conversion to docbook by the end of january15:08
annegentle_ok great15:08
Sam-I-Amor at least ready for sme review15:08
annegentle_and you have good sme support?15:08
Sam-I-Amnext steps include the generic content which i've seen a few patches for15:08
Sam-I-Amit comes and goes15:08
Sam-I-Ama lot of the work has been more or less reading code and reverse engineering15:09
Sam-I-Amat least with the new/experimental stuff like dvr and l3ha15:09
annegentle_yah15:09
*** xuhanp has quit IRC15:09
annegentle_I know trystack pulled DVR back after deploying it15:09
Sam-I-Amwe sort of built from 0 on those, whereas provider networks and classic neutron are somewhat documented15:09
Sam-I-Ami think the scenarios will be very useful since they describe functional environments15:10
annegentle_right15:10
annegentle_yup15:10
Sam-I-Amhopefully all of this is done and published by kilo15:10
Sam-I-Amwhere l3ha and dvr should be more prod ready15:10
annegentle_fingers crossed. you all have a plan and work to the plan so that's ideal15:10
Sam-I-Ampretty much. that's all from me!15:10
annegentle_okay, high availability team, anyone?15:11
Sam-I-Amthey're not highly available yet?15:11
*** AJaeger has joined #openstack-meeting-315:11
Sam-I-Amhi andreas15:11
annegentle_welcome AJaeger :)15:11
*** phil_h has joined #openstack-meeting-315:11
annegentle_So, there's this review: https://review.openstack.org/#/c/143910/15:11
annegentle_that needs work15:11
AJaegersorry for beeing late...15:12
annegentle_and they do have a weekly meeting time now15:12
annegentle_no worries15:12
annegentle_#link https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update15:12
*** taroth1 has joined #openstack-meeting-315:12
*** amotoki_ has quit IRC15:12
annegentle_And they're hanging out in #openstack-haguide15:12
*** pkoniszewski has quit IRC15:12
annegentle_also see15:13
annegentle_#link https://etherpad.openstack.org/p/openstack-haguide-update15:13
annegentle_Anyone here from Security team?15:13
*** erikmwilson has joined #openstack-meeting-315:13
annegentle_I don't know much about their latest status15:13
annegentle_And anyone from Training?15:14
annegentle_Their weekly meeting is on Mondays15:14
annegentle_ok that's it for specialty teams15:14
annegentle_Let's move on15:14
annegentle_#topic Install Guide discussion15:14
annegentle_thanks AJaeger Sam-I-Am and zigo for being here even with the time change15:14
* annegentle_ hangs head in time shame15:15
Sam-I-Amit happens15:15
AJaegerno worries, annegentle_15:15
Sam-I-Ami think we left off just before the debian stuff last meeting15:15
annegentle_we had a good discussion last month about hte current state of each install guide15:15
*** Piet has quit IRC15:15
annegentle_got some overall agreement on what the goals are for install guides that are in docs.openstack.org domain15:16
annegentle_so wanted to talk through possible solutions15:16
annegentle_Here's an etherpad with the ideas so far15:16
annegentle_#link https://etherpad.openstack.org/p/install-guides-upstream15:17
annegentle_right now, Ubuntu/Debian has differences. We could just continue the way things are.15:17
annegentle_We could make those two completely consistent15:17
annegentle_We could stop publishing Debian version until it's consistent15:17
Sam-I-Amannegentle_: right now the debian guide is broken15:18
annegentle_or15:18
Sam-I-Ambased on the bugs i'm seeing15:18
annegentle_Maintain debconf/Debian outside of docs.openstack.org with a matching one for docs.openstack.org15:18
annegentle_or something else I haven't thought of15:18
phil_hMy belief is that we should make them consistent15:18
*** amotoki_ has joined #openstack-meeting-315:18
annegentle_phil_h: that's great, are you able to do that?15:18
*** erikmwilson has quit IRC15:18
phil_hsigh - yes15:19
*** sahid_ has joined #openstack-meeting-315:19
Sam-I-Amannegentle_: i think it would just mean un-debconfing the debian stuff15:19
phil_hI know SAM-I-AM is smiling15:19
annegentle_phil_h: Sam-I-Am: I do think it's pretty straightforward15:19
Sam-I-Amamong other stuff (like packaging bugs i'm seeing)15:19
annegentle_zigo: but where will you publish your debconf one?15:19
*** sahid_ has quit IRC15:19
zigo2please don't remove the debconf stuff from the docs.15:20
annegentle_let's make sure zigo2 and zigo can keep up on his phone15:20
zigo2sorry, I' back home soon.15:20
annegentle_zigo2: but what do we do about the technical debt? I need solutions.15:20
*** sahid_ has joined #openstack-meeting-315:20
Sam-I-Amzigo2: the debian part of the guide has been broken since at least the juno release15:20
annegentle_zigo2: no worries, I'm impressed you can type on your phone :)15:20
zigo2coulld we talk about debian in 15 minz?15:20
*** sahid has quit IRC15:20
Sam-I-Amit keeps getting more and more bugs that no one triages15:20
*** mestery has joined #openstack-meeting-315:21
phil_hAnd the continual need for maintenance15:21
annegentle_AJaeger: was there another technical solution with a conditional chapter we thought of?15:21
annegentle_zigo2: absoluletly, we have other agenda items15:21
* AJaeger doesn't remember anything15:21
annegentle_ok, tabling the Install Guide topic for now15:21
Sam-I-Ammmkay, guess we'll wait15:21
annegentle_#topic Doc tools latest15:22
annegentle_So, clouddocs-maven-plugin will not have a patch with a "split" like I had thought, so that only OpenStack branding is in the stackforge repo15:22
annegentle_Unless I identify someone to do the split, it'll remain where it is.15:22
Sam-I-Amwhat?15:23
annegentle_I'd like to do a 2.1.4 release to get a couple of bug fixes in (there's a nasty one in the Ops Guide) then set it on maintenance only15:23
annegentle_with releases only about every year if we need it15:23
Sam-I-Amwho's working on that these days?15:23
annegentle_Sam-I-Am: no one, that's the point.15:23
annegentle_Sam-I-Am: we have our Sphinx redesign coming15:23
Sam-I-Amright15:23
annegentle_Sam-I-Am: so the only output we need clouddocs-maven-plugin for is the API reference15:23
annegentle_I just want to make sure the doc team knows we have a maintenance plan and the migration plan to Sphinx is what we15:24
annegentle_we're planning on15:24
Sam-I-Ami'm trying to wrap my head around the sphinx thing15:25
rromansroughly what's the timeframe for that migration?15:25
annegentle_rromans: the plan of record is in the blueprint15:25
annegentle_rromans: just End User Guide and Admin User Guide will be migrated by May 201515:25
rromansannegentle_: tnx!15:25
annegentle_#link http://specs.openstack.org/openstack/docs-specs/specs/kilo/migrate-to-new-web-design.html15:26
AJaegerannegentle_, let's make that RST move a separate topic, plesae15:26
annegentle_AJaeger: sure15:26
annegentle_I dont' have anything else on clouddocs-maven-plugin15:26
annegentle_Next topic for Doc tools is Sphinx new theme15:27
annegentle_#topic Sphinx new theme15:27
annegentle_The plan is to create a parallel theme to the "openstack" theme that exists in oslosphinx15:27
annegentle_I'm working on that now15:27
annegentle_it'll be named openstack-doc or some such15:27
annegentle_To ensure we get output like this:15:28
annegentle_#link openstack-homepage.bitballoon.com/docs/book15:28
annegentle_huh. http15:28
*** fischerw has joined #openstack-meeting-315:28
annegentle_#link http://openstack-homepage.bitballoon.com/docs/book15:28
*** jroll has quit IRC15:28
*** jroll has joined #openstack-meeting-315:28
annegentle_I've just started the work based on the landing page15:28
*** GLaupre has joined #openstack-meeting-315:28
AJaegerthanks, annegentle_ !15:28
annegentle_Tom is talking to the Foundation about when/whether to announce a new landing page for docs or not15:29
AJaegerlast comment by him was: Announce after elections15:29
annegentle_AJaeger: ah, was just looking that up15:29
annegentle_thanks15:30
annegentle_AJaeger: do you want to talk about https://review.openstack.org/#/c/142437/ -- the RST conversion?15:30
*** sahid_ has quit IRC15:30
AJaegerannegentle_, sure15:30
*** sahid has joined #openstack-meeting-315:30
AJaegerI started with a proof of concept in a separate directory to see how it looks15:30
*** jackmccann has joined #openstack-meeting-315:30
AJaegerUnfortunately I do not have as much spare time as I had hoped ;(15:31
annegentle_AJaeger: what was the makefile for?15:31
annegentle_AJaeger: I can help, just want to be sure I understand the approach15:31
AJaegerThere're not enough good tools to do the conversation, so it's a basic conversation and then cleaning up afterwards - incl. adding content that was thrown away15:31
AJaegerThe makefile can be deleted.15:31
*** xuhanp has joined #openstack-meeting-315:31
annegentle_AJaeger: my approach was https://wiki.openstack.org/wiki/Documentation/Migrate -- lots of manual cleanup15:31
AJaegerThat was added by sphinx automatically, we don't need it anymore15:31
annegentle_AJaeger: when I did the API docs15:31
annegentle_AJaeger: basically, it's XHTML > RST using pando15:32
annegentle_pando15:32
annegentle_pandoc with a c!15:32
AJaegerannegentle_, wasn't aware of that page15:32
AJaegerYeah, I used pandoc as well ;(15:32
annegentle_:)15:32
annegentle_AJaeger: well do you want me to take the same approach?15:32
annegentle_AJaeger: it seems to work15:32
annegentle_AJaeger: then we'll have to figure out what to do about duplicate files, reuse.15:33
*** GLaupre has quit IRC15:33
AJaegerlet me read the page and then come back. I think it's the best approach.15:33
annegentle_AJaeger: okay15:33
AJaegerQuestion is : Do we copy over to some "temp" directory (like my playground) in smaller steps, or do one large conversion?15:34
*** erikmwilson has joined #openstack-meeting-315:34
AJaegerand we need to figure out translations15:34
*** GLaupre has joined #openstack-meeting-315:34
annegentle_AJaeger: It's always nice to make smaller pieces put together but for the publish we'd need it all at once15:34
*** xuhanp has quit IRC15:34
annegentle_AJaeger: yes15:34
AJaegerplayground gets excluded from translations15:34
annegentle_AJaeger: ah ok15:34
AJaegerWE can use playground for step-by-step and then do a final big switch at the end.15:34
AJaegerplayground does not get published either ;)15:35
annegentle_AJaeger: so I envision it's "Playground to get migrated content, then move to new folder for publish"15:35
AJaegerso, once we're happy, we can publish15:35
AJaegerannegentle_, exactly15:35
annegentle_AJaeger: so should we just merge bits and pieces in playground? I'm good with that approach15:35
AJaegerannegentle_, that's what I'm proposing15:35
zigoI'm back home now.15:35
annegentle_AJaeger: sounds good15:35
annegentle_zigo: great timing15:35
AJaegerthis allows us to work together on it.15:36
annegentle_ok, to wrap up on doc tools15:36
zigoSorry, but I planned today for the meeting at 2pm UTC as planned previously.15:36
annegentle_#info playground is where we can all work on migrating content15:36
Sam-I-Amhi zigo15:36
AJaegerannegentle_, any directory starting with playground ;)15:36
annegentle_#info merge in pieces to playground-, then publish end-user guide once oslosphinx theme is done15:36
annegentle_Seems like we can do that this release15:36
annegentle_Anything else for doc tools? Questions?15:37
alexadamovHi Anne and Andreas, I'm from the Mirantis doc team and can help with RST conversion if needed at playground :)15:37
AJaegeralexadamov, great!15:37
annegentle_alexadamov: excellent! Have you seen https://review.openstack.org/#/c/142437/?15:37
AJaegerhow do we coordinate work? Should we have a wiki page where people sign up for each file?15:37
alexadamovhave no permissions15:37
annegentle_We could use https://wiki.openstack.org/wiki/Documentation/Migrate15:37
*** baoli has quit IRC15:38
AJaegerannegentle_, whatever works ;)15:38
alexadamovWiki looks good!15:38
annegentle_AJaeger: ok cool15:38
annegentle_AJaeger: alexadamov: thanks for the help!15:38
KLevensteinalso interested, btw15:38
annegentle_KLevenstein: excellent thanks15:38
annegentle_Okay let's be sure to leave time for the install guide discussion15:39
annegentle_#topic Install Guide15:39
*** amotoki_ has quit IRC15:39
annegentle_#link http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-12-03-19.02.log.html15:39
annegentle_I also link to last time we met15:39
Sam-I-Ami think so too. wheee.15:40
annegentle_wow we even talked about ceph last time. whew.15:40
annegentle_oh and you got into ansible too hehe15:40
Sam-I-Amyeah. we covered just about everything except the debian situation.15:41
annegentle_Okay so we also talked about how there's no Canonical doc site15:41
annegentle_so the upstream install guide is all that there is for Ubuntu too15:41
Sam-I-Amyeah. our guide is more or less the ubuntu guide. rh/suse are probably supplemental in some way, although a lot of people seem to like our guide.15:41
annegentle_and we all agree, it's important to have ubuntu and debian in upstream15:41
zigoSame for Debian, no other docs out there but the official docs.openstack.org15:42
annegentle_the fiddly bit is that it's maintenance15:42
annegentle_so, zigo doesn't currently agree with the ubuntu simplified way15:42
annegentle_and Sam-I-Am isn't amenable to maintenance of debconf15:42
annegentle_is that accurate?15:42
Sam-I-Amimho, ubuntu and debian could be really similar and maintained mostly together... except the debconf problem. that and the pile of debian docs and packaging bugs that don't get fixed.15:42
Sam-I-Amyeah15:42
Sam-I-Amright now the debian guide is unusable15:43
annegentle_and I'm not making this a sumo wrestling match, just making sure we know who's where15:43
annegentle_:)15:43
Sam-I-Amand thats just a bad thing15:43
zigoSo far, I'm the only person who did the work on the Debconf side, and I don't see it as a big burden.15:43
phil_hMy belief is they should be as similar as possible and if someone wants to maintain debconf stuff put it in an appendix15:43
phil_hthat makes maintanence easier15:43
annegentle_I do think in my head I have some "debconf solution" that involves a separate chapter15:43
*** erikmwilson has quit IRC15:43
zigoSam-I-Am: Could you tell which part is unuseable?15:43
*** tomoe has quit IRC15:43
annegentle_but is that okay with zigo?15:43
annegentle_and yes, please talk thorugh the details15:43
Sam-I-Amzigo: if you want to be responsible for the debian install guide w/ debconf, thats fine. but as it stands, there's a pile of blocker bugs and no one has tested the install guide with juno.15:44
annegentle_Sam-I-Am: can you pull a bug list easily?15:44
Sam-I-Amhttp://tinyurl.com/mpjsqpl15:44
annegentle_let's size this15:44
Sam-I-Amthats a quick search15:44
*** erikmwilson has joined #openstack-meeting-315:44
zigoSam-I-Am: So far, I've been doing all the work, and I'm ok to do more.15:44
zigoThe only issue is that I'm not sure how to pull a relevant bug list.15:44
Sam-I-Amin most cases i've either invalidated them because they're packaging bugs, or assigned them to zigo15:44
Sam-I-Amsome are minor issues, but there's a few that completely break installations15:45
zigoSam-I-Am: Nothing that I'm aware of ... :(15:45
zigoSam-I-Am: I'll make sure to work on them asap.15:45
Sam-I-Ami cant verify these because i dont have a debian installation, but based on what i know about installing openstack, they're big issues.15:45
zigo(when I know)15:45
AJaegerzigo, when I assign a bug in launchpad to you, I don't remember seeing you followup on them.15:45
annegentle_so invalid is when it's a packaging problem that docs can't fix?15:45
AJaegerDon't you get notified about the issues?15:45
Sam-I-Amannegentle_: thats generally what i do15:45
Sam-I-Amannegentle_: and then hope zigo can triage them elsewhere15:45
zigoHow do I list all bugs assigned to me?15:46
Sam-I-Amzigo: advanced search, put you in as the assignee15:46
zigoDo I have the access rights to close bugs too?15:46
Sam-I-Amyes15:46
annegentle_zigo: yes15:46
zigok15:46
Sam-I-Ambugs are automatically closed with patches15:46
zigoI'll try then.15:46
AJaegerzigo, if not - join the documentation bug team15:46
*** matrohon has quit IRC15:46
annegentle_zigo: but is it realistic to ask you? Is there anyone else with interest?15:46
*** zigo2 has quit IRC15:46
AJaegerzigo, if you need help on how to administer bugs, just ask...15:47
annegentle_zigo: I'd be intimidated by doc bugs in the double digits15:47
annegentle_zigo: and want a back up person15:47
AJaegerannegentle_, +115:47
zigoFYI, I've been busy moving from China to France, which may explain my lower activity on the doc over the last months.15:47
Sam-I-Amif we're going to keep the debian-specific content, we need more debian people committed to testing and documentation15:47
annegentle_Sam-I-Am: also, does eliminating debconf really fix most of these doc bugs?15:47
Sam-I-Amone person for docs and packaging isn't enough15:47
zigoI can ask to find someone else.15:48
zigoFYI, Mirantis is moving to Debian, so I'm sure I'll find help.15:48
zigoalexadamov: Could you help?15:48
annegentle_zigo: yeah moving is time-sucking. I could swear, okay, affirm, there is someone else interested.15:48
Sam-I-Amannegentle_: most of the bugs i see with debian are debconf not setting something, or setting something wrong, etc. things we can fix by editing config files.15:48
alexadamovYes for sure15:48
annegentle_alexadamov: it was you! Maybe. I'm not sure. :)15:48
zigoOk, then you got another Mirantis person to help! :)15:48
annegentle_alexadamov: ok, great, thanks.15:48
alexadamovI'm the right person :)15:49
annegentle_alexadamov: how much onboarding do you need for docs? Do you understand our conditionals?15:49
annegentle_I'm happy to set up a meeting for training you on the install guide, not a problem alexadamov15:49
Sam-I-Amthe other issue with debconf is not a technical one. its the fact that debconf removes a lot of the teaching aspect of the guide.15:49
zigoSam-I-Am: I don't agree with that.15:49
alexadamovNo yet. I need to get into15:49
annegentle_Sam-I-Am: zigo yeah I think that's why I'd like to move debconf into an appendix, for the philosophical matchup15:50
zigoSam-I-Am: If there's some missing information within the debconf chapter explaining what Debconf changes, then we can add some more there.15:50
annegentle_zigo: and maybe it already is in a separate chapter15:50
annegentle_Sam-I-Am: but we can't be TOO pendantic here.15:50
annegentle_Sam-I-Am: I'm a pragmatist also15:50
annegentle_Sam-I-Am: some people want the easy button15:50
Sam-I-Amannegentle_: without any openstack experience, easy ends in disaster15:51
*** jackmccann has left #openstack-meeting-315:51
Sam-I-Amannegentle_: sitting in #openstack has told me that15:51
phil_hI agree with Sam-I-AM15:51
Sam-I-Ampeople *really* need to understand all the gory details about openstack before automating it15:51
annegentle_Sam-I-Am: phil_h sure, but we still have to be working in community on community docs.15:52
phil_hI think moving the debconf to an appendix is the best fix for this15:52
zigoSam-I-Am: Again, if you want more explanation of what Debconf does, we can do that.15:52
annegentle_phil_h: that's where I'm at too15:52
phil_hAnn - I agree, don't interpert this as not wanting to help15:52
Sam-I-Amannegentle_: i think it makes sense to eventually say "ok, lets do this with ansible now", but first-timers need to slog up the hill manually15:52
zigoSam-I-Am: Mostly, it just edits things which users would do again, again and again, and avoids typoes.15:52
annegentle_alexadamov: Let's set up a meeting time for me to show you the install guide ropes so to speak15:52
annegentle_alexadamov: what time zone are you in?15:52
zigoSam-I-Am: It doesn't mean you don't need to understand what you do.15:52
alexadamovUTC+215:52
phil_hI want us to move forward and not repeat mistakes of the past15:52
annegentle_alexadamov: ok15:53
Sam-I-Amzigo: thats fine, as long as the documentation provides meta for what's actually going on... perhaps tells people which config files are being edited, etc.15:53
alexadamovthanks!15:53
annegentle_phil_h: I want us to work in the community on docs where multiple opinions are allowed and tested. I think moving debconf to a separate chapter enables that15:53
zigoSam-I-Am: Please open bugs for things you think are missing, and I'll edit them.15:53
Sam-I-Amunfortunately, typos are a right of passing :)15:53
annegentle_#action alexadamov and annegentle to meet to understand Install Guide conditionals15:53
phil_hannegentle_: I agree15:53
zigoSam-I-Am: As much as I know, there's enough in the debconf chapter to understand what happens.15:54
zigoSam-I-Am: For example: http://docs.openstack.org/trunk/install-guide/install/apt-debian/content/debconf-dbconfig-common.html ...15:54
zigoSam-I-Am: Do you think there's missing stuff over there?15:54
zigoThat it's not clear what dbconfig-common does?15:54
annegentle_zigo: do you have time to test the current install guide?15:54
*** Networkn3rd has joined #openstack-meeting-315:54
annegentle_zigo: I think that's what's concerning to Sam-I-Am and us, is the lack of testing15:54
Sam-I-Amzigo: i'd have to look through it all again. first thing, though, if we're going to keep debconf... the guide needs testing.15:54
*** Sukhdev has joined #openstack-meeting-315:54
AJaegerIsn't it more chapters like http://docs.openstack.org/trunk/install-guide/install/apt-debian/content/keystone-install.html ?15:54
zigoannegentle_: I will, yes, but I've been stuck with a libvirt issue over ehre, preventing me from starting instances on my Xen PV VM.15:55
AJaegerWhere debconf automates everything - compared to other distros?15:55
Sam-I-AmAJaeger: yeah, and it doesn't really say whats going on15:55
Sam-I-Amlike... why are we doing this15:55
Sam-I-Amcompared to the ubuntu version:15:55
annegentle_AJaeger: yes15:55
Sam-I-Amhttp://docs.openstack.org/trunk/install-guide/install/apt/content/keystone-install.html15:55
Sam-I-Am"here's what we're doing and why, and here's a look at the config file"15:56
Sam-I-Amdebconf cant automate production environments15:56
Sam-I-Ampeople need to understand those config files15:56
Sam-I-Amso eventually you have to look at them15:56
phil_hSAM-I-AM is correct15:56
annegentle_Sam-I-Am: or phil_h: who can do a patch that shows the separation?15:57
annegentle_that'll let us all review15:57
annegentle_by separation, I mean, making parallele.15:57
Sam-I-Amannegentle_: what do you mean shows the separation?15:57
zigoSam-I-Am: I can look again at the debconf chapter and add what directives in the config files it's changing.15:57
annegentle_which sounds quite the opposite :)15:57
annegentle_phil_h: do you really have time to do it?15:57
annegentle_I'd like a patch to look at15:57
annegentle_zigo: I think it's better if we look at phil_h and Sam-I-Am's idea in a patch15:57
*** sahid has quit IRC15:57
annegentle_zigo: and you spend your time testing when you get libvirt working15:57
phil_hNot sure about time availability15:58
annegentle_wow, 3 minutes remaining.15:58
annegentle_zigo: does that make sense?15:58
Sam-I-Amzigo: basically, prior to each debconf section, there would be a page saying what all is going on here and why... mention the config files edited, services touched, databases created, etc.15:58
*** sahid has joined #openstack-meeting-315:58
annegentle_phil_h: heh. I knew it sounded too easy :)15:58
zigoSam-I-Am: I fully agree with that.15:58
phil_hyes15:58
Sam-I-Amannegentle_: by patch, you mean disable debconf and make it work like ubuntu?15:58
zigoAnd I do want to spend time doing so.15:58
zigoalexadamov: Do you think you could work out patches to do that?15:58
annegentle_honestly phil_h and Sam-I-Am seems like we need a patch -- yep Sam-I-Am, make the debian install guide look like ubuntu15:58
zigoalexadamov: It'd be a huge help if you do.15:58
annegentle_or alexadamov could do it with help15:59
*** carl_baldwin has quit IRC15:59
phil_hSAM-I-AM - lets talk about what we can get done15:59
annegentle_Okay one minute.15:59
annegentle_How about I meet with alexadamov, we map out what a patch looks like15:59
annegentle_then everyone can review15:59
annegentle_the patch15:59
AJaegerannegentle_, go for it ;)15:59
annegentle_yeah?15:59
Sam-I-Amannegentle_: is this the debian-like-ubuntu patch, or the fixes-the-debian-guide patch?16:00
zigoSam-I-Am: There's something you don't understand, "make it work like ubuntu" doesn't work here, it's 2 different distro and 2 different set of packages. I started doing a separate distro install-guide because there was too many "Notes for debian users:"16:00
zigoSam-I-Am: The differences are not only at the debconf vs non-debconf level.16:00
annegentle_Cool16:00
annegentle_zigo: Sam-I-Am: that's where a patch will help16:01
Sam-I-Amzigo: ubuntu and debian shouldnt be very different from a packaging perspective.16:01
annegentle_us all see it16:01
zigoSam-I-Am: For example, there's no plugin packages for Neutron in Debian, all is in neutron-common. There's only a single "nova-consoleproxy" package, nothing specific for noVNC, the Xen console or the Spice one.16:01
annegentle_Okay sorry I have to end it16:01
annegentle_Continue in #openstack-doc please :)16:01
annegentle_#endmeeting16:01
openstackMeeting ended Wed Jan 14 16:01:37 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docteam/2015/docteam.2015-01-14-15.01.html16:01
annegentle_Thanks all for joining!16:01
Sam-I-Amaight, thanks for putting up with us :)16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docteam/2015/docteam.2015-01-14-15.01.txt16:01
zigoSam-I-Am: Well, I could say the same thing for Suse and RedHat...16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/docteam/2015/docteam.2015-01-14-15.01.log.html16:01
*** pkoniszewski has joined #openstack-meeting-316:02
*** evgenyf has joined #openstack-meeting-316:02
*** Sam-I-Am has left #openstack-meeting-316:03
*** KLevenstein has left #openstack-meeting-316:05
*** alexpilotti_ has joined #openstack-meeting-316:10
*** banix has joined #openstack-meeting-316:10
*** alexpilotti has quit IRC16:12
*** alexpilotti_ is now known as alexpilotti16:12
*** markvoelker has joined #openstack-meeting-316:15
*** rromans has left #openstack-meeting-316:21
*** armax has joined #openstack-meeting-316:23
*** pc_m has joined #openstack-meeting-316:23
*** pc_m has left #openstack-meeting-316:24
*** baoli has joined #openstack-meeting-316:26
*** reed has joined #openstack-meeting-316:29
*** Longgeek has quit IRC16:29
*** sbalukoff has quit IRC16:30
*** pkarikh has quit IRC16:30
*** pkarikh has joined #openstack-meeting-316:31
*** devlaps has joined #openstack-meeting-316:31
*** vitorc has quit IRC16:32
*** vitorc has joined #openstack-meeting-316:35
*** carl_baldwin has joined #openstack-meeting-316:35
*** JeanBriceCombebi has quit IRC16:37
*** JeanBriceCombebi has joined #openstack-meeting-316:37
*** markvoelker has quit IRC16:40
*** evgenyf has quit IRC16:41
*** pkarikh has quit IRC16:41
*** pkarikh has joined #openstack-meeting-316:41
*** egallen_ has joined #openstack-meeting-316:44
*** egallen has quit IRC16:46
*** egallen_ is now known as egallen16:46
*** ChuckC_ has joined #openstack-meeting-316:47
*** belmoreira has joined #openstack-meeting-316:50
*** ChuckC has quit IRC16:51
*** SridharRamaswamy has joined #openstack-meeting-316:54
*** Guest8210 is now known as redrobot16:54
*** Networkn3rd has quit IRC16:54
*** Networkn3rd has joined #openstack-meeting-316:55
*** VW_ has quit IRC16:58
*** sarob has joined #openstack-meeting-316:58
*** melwitt has joined #openstack-meeting-316:59
alaski#startmeeting nova_cells17:00
openstackMeeting started Wed Jan 14 17:00:18 2015 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
openstackThe meeting name has been set to 'nova_cells'17:00
vineetmenonhi17:00
bauzasbonjour17:00
bauzas\o17:00
alaskio/17:00
melwitto/17:00
dansmitho/17:00
*** johnthetubaguy has joined #openstack-meeting-317:00
belmoreirao/17:00
alaskiwell, we have a simple agenda today17:01
alaski#topic scheduling17:01
bauzaslink ?17:01
bauzasabout the agenda17:01
alaskihttps://wiki.openstack.org/wiki/Meetings/NovaCellsv2#Agenda17:01
* bauzas is too lazy...17:01
edleafeo/17:01
alaskihttps://review.openstack.org/#/c/141486/ is the current review for cells scheduling17:02
bauzasthanks for having updated it17:02
alaskilast week the consensus was that we would spend this week diving into scheduling17:02
*** mriedem has joined #openstack-meeting-317:03
alaskiso what are the current points of consternation or interest?17:03
*** coolsvap is now known as coolsvap|afk17:03
vineetmenonhow is failure being handled in this scheme?17:04
vineetmenoni mean, are we in a position to discuss details?17:04
bauzasalaski: I'm basically +1 your spec17:04
alaskivineetmenon: some level of detail, yes17:04
belmoreiraalaski: I like this proposal as well17:04
*** egallen_ has joined #openstack-meeting-317:04
alaskivineetmenon: but I would like to get the broad details discussed before getting too deep17:04
bauzasalaski: some details are a bit debatable that said17:04
dansmithagreed, I'm pretty much on board with that spec17:05
*** egallen has quit IRC17:05
*** egallen_ is now known as egallen17:05
bauzasalaski: I'm really concerned about how you plan to persist those request details (for not naming the devil by its name)17:05
johnthetubaguyalaski: I like the general idea, question about the cells v1 support though17:05
*** VW_ has joined #openstack-meeting-317:05
belmoreiraalaski: I have some questions that I'm commenting in the spec but I think we can discuss here as well17:05
*** s3wong has joined #openstack-meeting-317:06
johnthetubaguyalaski: can we not just have the top level scheduler send an RPC to the child scheduler, rather than do a partial decision?17:06
*** JeanBriceCombebi has quit IRC17:06
dansmithjohnthetubaguy: that's really a detail for later, right?17:06
dansmithmeaning,17:06
bauzasjohnthetubaguy: I really like the idea to have the cells API to manage the 2 calls rather than a top sched proxying children17:06
alaskijohnthetubaguy: yes.  but let me elaborate for a sec17:06
dansmiththe concerning bit is handling the api contract, and what happens after the fact to get to a cell,host is something else17:06
*** JeanBriceCombebi has joined #openstack-meeting-317:07
alaskijohnthetubaguy: basically what dansmith said17:07
dansmith\o/17:07
alaskiheh17:07
bauzasdansmith: right17:07
*** MaxV has quit IRC17:07
johnthetubaguyyeah, thats fair17:07
bauzasthat was indeed my 2nd question17:07
bauzasI recall the first one : how do you plan to persist the request17:07
belmoreiraI like the proxy option...17:07
*** vineetmenon_ has joined #openstack-meeting-317:07
alaskibauzas: essentially by persisting what is sent in the API request17:08
alaskibauzas: in a very basic manner for now17:08
*** vineetmenon has quit IRC17:08
dansmithwe need to generate them a uuid17:08
dansmithbut otherwise, if we store what they sent us, plus the uuid, that's enough I think17:08
*** vineetmenon_ is now known as mvineetmenon17:08
alaskiyep, that was my thinking as well17:08
bauzasalaski: so let me say the devil's name, don't you think that http://specs.openstack.org/openstack/nova-specs/specs/kilo/approved/request-spec-object.html would be a dependency FWIW17:09
bauzas?17:09
johnthetubaguyalaski: about the request_spec store, I guess the other way I remember dansmith mentioned was instread having the instance "cache" hold the data from the beginning? But thats a detail really, thats just the how its stored, I agree we need to store it17:09
bauzasprovided that we persist that object of course17:09
*** sarob has quit IRC17:09
*** Longgeek has joined #openstack-meeting-317:10
alaskibauzas: I'm not too concerned about whether we persist the object, or the input that allows the creation of the object17:10
bauzasalaski: well the history showed us that persistency is worth good17:11
alaskibauzas: I don't want to be blocked on the request spec object, but if it's in place I think it would be worth using17:11
*** ttrifonov is now known as zz_ttrifonov17:11
johnthetubaguyI am trying to think about any other APIs that return before creating an object in a specific cell, but I guess instance is the only one…17:11
dansmithbauzas: persistency? :P17:11
dansmithinstance is the big one for sure17:11
bauzasdansmith: aren't we all French, someone said last week in the news ? :)17:11
dansmiththey said persistency? awesome17:11
* bauzas reading a dictionary now17:12
alaskijohnthetubaguy: there might be more, but we'll tackle them as they come up17:12
bauzaseh I was close, only 2 letters to change17:12
*** zz_jgrimm is now known as jgrimm17:12
bauzasalaski: agreed on the plan, we can maybe iterate on what you need first, and integrate with ReqSpec while it comes17:13
alaskijohnthetubaguy: where it's stored is a detail, but what I like about using a separate table for the persistance right now is since the data is short lived we can iterate that store over time without worrying too much about compatibility/versioning17:13
johnthetubaguyalaski: agreed, I was just wondering if going the tasks route will help give us a more general solution than storing "build_request", but I am probably thinking too deep17:13
johnthetubaguyalaski: yeah, agreed, too deep17:13
bauzasalaski: and FYI https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/request-spec-object,n,z is implemented on the object side17:13
johnthetubaguyI agree with having to store "the request" for the reasons you state17:13
alaskibauzas: cool, I'll look into it17:14
bauzassounds like we're in violent agreement then ?17:14
alaskijohnthetubaguy: cool17:14
alaskibauzas: with the broak strokes at least17:14
alaskis/broak/broad/17:14
bauzasalaski: do your homework, create a table and then we'll see how to turn up to the object later on17:14
bauzasalaski: of course, you still need to iterate your spec by adding details on the *persistance*17:15
dansmithyeah, needs fleshing out17:15
alaskiyeah.  so realistically I think this is multiple specs17:15
bauzasalaski: +117:16
bauzaswe need to split out things17:16
bauzasthere is also some scheduling homework17:16
alaskiI can break this out now that there's general agreement, but I'm not sure what we can get moving during the freeze17:16
alaskibut I'll push on what I can17:16
bauzasalaski: are you planning to implement something for Kilo ?17:16
*** banix_ has joined #openstack-meeting-317:17
alaskibauzas: yes17:17
bauzasalaski: I guess then the approved specs, right ?17:17
alaskithere's already approved specs which need implementations17:17
alaskiand I would like to continue into scheduling if we get to that point17:17
bauzasalaski: hence my point, that's not really a problem to rewrite those scheduler specs, as it's not planned for Kilo17:17
alaskihow that's done is an open question right now17:17
bauzasalaski: yeah, but we can work on drafts and merge on L17:18
bauzasalaski: I can see some point where the scheduler should serve CellsV2 as destinations17:18
mvineetmenonthe approved specs are for cell-instance-mapping and scheduler, right17:18
mvineetmenonwhat are you planning to implement in those?17:18
bauzasI mean that the scheduler should provide cells as a result17:18
alaskimvineetmenon: not scheduling17:18
bauzaswell, I think the extra DB thing is already a huge thing :)17:19
alaskibauzas: sure, let's focus on what's approved and iterate on this in the mean time17:19
bauzasalaski: because you need to cable all the bits for creating a 2nd DB17:19
alaskiare there more specifics on scheduling that anyone would like to dive into now?17:19
bauzasalaski: did you work on a POC for this btw. ?17:19
alaskibauzas: I have not17:20
bauzasalaski: again, I think that for scheduling, we need to split this spec into specific items17:20
bauzasand see what's needed to change in the scheduler17:20
bauzasthe current proposal is vague about the capability of providing cells17:20
bauzasdo you plan to merge the Cells V1 scheduler code into the mainstream one ?17:20
bauzasalaski: ^17:20
mvineetmenon.join ##barc-cern-openstack17:21
alaskibauzas: not exactly17:21
bauzasalaski: cool17:21
belmoreirabauzas: how the scheduler will handle the case of the 2 layer approach?17:21
bauzasbelmoreira: I was thinking of extending the Scheduler API17:21
bauzasby adding a new method17:22
belmoreirabut will the top scheduler be aware of everything anyway?17:22
alaskibauzas: there are some filters and weighers for cells that the scheduler should be able to handle.  We'll need to determine the gaps that need to be filled so that can happen17:22
bauzasthat would be the safiest approach, as many bps are planning to work on select_dest()17:22
bauzasalaski: agreed, we need to jump into the details17:22
*** mvineetmenon is now known as vineetmenon17:23
bauzasalaski: and I have to admit I have to dig into the Cells V1 scheduler code, my knowledge being vague on it17:23
belmoreirabauzas: but one of the goals of cells if to split things...17:23
bauzasbelmoreira: I don't get your point ?17:23
alaskibauzas: it's quite similar to the scheduler in it's manner of operation, but it schedules primarily by flavor availability17:23
bauzasalaski: ack17:24
dansmithI thought the plan was to make the scheduling flexible enough to use single-level scheduling by default, but allow 2-level if there was some reason17:24
dansmithlike, a filter that could punt to a second scheduler17:24
*** sergef has joined #openstack-meeting-317:24
vineetmenon***scalalibity*** ?17:24
dansmithbecause with a caching scheduler, I don't really understand why two levels are needed17:24
*** obondarev has quit IRC17:24
*** Longgeek has quit IRC17:24
belmoreiradansmith: in that case the first schedule will only have limited light info, right?17:24
dansmithbelmoreira: no, I don't think so, but it may make lightweight decisions17:25
belmoreiradansmith: for example we have filters enabled in only some cells17:25
johnthetubaguydansmith: I think we should be able to pick from all hosts from all cells in one go, and just tell the caller which cell it was (at least until some level of scale)17:25
dansmithjohnthetubaguy: that's what I'd like, yeah17:26
vineetmenondansmith: so, the first scheduler is powerful enough to select a cell, host tuple?17:26
edleafejohnthetubaguy: +117:26
*** s3wong has quit IRC17:26
dansmithvineetmenon: yeah17:26
johnthetubaguywe would need some extra stuff to filter on cells properties, but that just works17:26
melwittjohnthetubaguy: +117:26
bauzasdansmith: that's possible, provided we define a clear abstraction17:26
bauzasdansmith: at the moment, the mainstream scheduler is host-centric17:27
* vineetmenon is thinking about scalability issues with thousands of nodes17:27
johnthetubaguythe problem is when the caching scheduler's DB call takes so long, its doing nothing else, but we can hopefully ignore that case17:27
*** GLaupre has quit IRC17:27
dansmithwell, I think a cell-aware scheduler is just one that has info about cells and extra filters to make cell-based decisions early in the stack and then host-based decisions once you select a cell17:27
melwittI like dansmith's idea of the flexibility to go to two-level later on17:27
dansmithright, and so once that's properly abstracted,17:27
alaskibauzas: agreed.  no matter the physical setup of the scheduler I think it logically needs to operate on cells and hosts17:27
johnthetubaguyvineetmenon: there were some plans to use kafka as the data store to get incremental updates, a-la no-db-scheduler plan from a few releases back, but I am ignoring that as a detail17:28
dansmithwe should have the ability for a filter to return "contact scheduler at 1.2.3.4 to continue"17:28
dansmithand just let it punt to the next one17:28
johnthetubaguyalaski: I think its a list of hosts, and cell is a property of the host, but its the same difference really17:28
dansmiththat way if you *want* to have lots of schedulers, with different configs, you can write filters such that you'll proceed from top to mid to bottom scheduler before a decision is made17:28
melwitt+117:28
alaskijohnthetubaguy: I disagree, because cells have capabilities on their own with no regards to the hosts17:29
bauzasdansmith: but you mean that a filter would issue a call to a 2nd scheduler ?17:29
johnthetubaguyalaski: thats the same as aggregates today though17:29
dansmithbauzas: or return some result that says "stop what you're doing, pass what you have to $scheduler2 and let it proceed"17:29
belmoreiraalaski: +117:29
bauzasjohnthetubaguy: and that's why we're working on changing how we access that aggregate info17:29
dansmithbauzas: whether that is a result to the client and the client re-queries, or we proxy is an open question, but I don't think it matters much17:29
johnthetubaguyalaski: we can just make those properties of every cell, and it flattens things, and filters/weight just pick which they want to act on17:29
johnthetubaguybut its a detail, and it doesn't change much17:30
dansmithjohnthetubaguy: right, aggregates seem like the way you handle such things to me17:30
bauzasdansmith: interesting, I just need to think about that17:30
dansmithjohnthetubaguy: and keep a host-centric scheduler17:30
edleafebauzas: yeah, this sounds like a subset of aggregates17:30
bauzasdansmith: that sounds like sharding17:30
johnthetubaguydansmith: we can just map cells to aggregates for "v1" support I guess17:30
dansmithjohnthetubaguy: yeah17:30
bauzasjohnthetubaguy: indeed17:30
bauzasanyway, we should put our thoughts in a spec :)17:31
belmoreirajohnthetubaguy: humm17:31
alaskibelmoreira: in answer to your concern, the ability to filter differently for different cells should remain if you need it, it would just be handled in the scheduler rather than in nova17:31
*** yamahata has quit IRC17:32
alaskidansmith: I'm very much in agreement with your statement of things, but not quite sure what exactly host-centric means yet17:32
*** safchain has quit IRC17:32
bauzasbelmoreira: +1 with alaski, that's just a matter of configurating nova-scheduler, not nova-api17:32
dansmithalaski: meaning that the scheduler's goal is to select a host, not to select a cell17:32
alaskidansmith: gotcha, then yeah I'm on the same page17:32
edleafedansmith: +117:33
bauzasalaski: btw. http://specs.openstack.org/openstack/nova-specs/specs/kilo/approved/isolate-scheduler-db-aggregates.html will be the new way for the scheduler to work with aggregates17:33
bauzasthat sounds feasible to map the design but with cells17:34
alaskiso everyone is good with taking this and splitting out some detailed specs to continue the discussion on?17:34
bauzas+117:34
alaskibauzas: thanks, will take a look17:34
dansmithyup17:34
*** banix__ has joined #openstack-meeting-317:34
alaskigreat, moving on then17:34
edleafeyes17:34
alaski#topic open discussion17:34
bauzasI was having an action from last week17:35
dansmithmove to adjourn? :)17:35
dansmithdamn.17:35
bauzaseh17:35
alaskidansmith: hah17:35
*** banix_ has quit IRC17:35
alaskibauzas: any update?17:35
bauzasI'll be very brief, I promise :)17:35
bauzasso, 73 tests failing now17:36
*** jcoufal_ has quit IRC17:36
*** sunny_ has joined #openstack-meeting-317:36
bauzasso I'm about to add a new job like https://github.com/openstack-infra/project-config/blob/f98caac794f6d1327cb7565c446c026cc951a873/jenkins/jobs/devstack-gate.yaml#L816-L829 by adding those 73 tests17:36
vineetmenonanyone figured out the reason for new year +30 bonanza?17:37
bauzaseverybody agrees ?17:37
vineetmenon+117:37
bauzasand I won't touch the job above17:37
bauzasalaski: you ok ?17:38
alaskibauzas: I like that.  If we can get that to voting in a reasonable time it will prevent backslides17:38
bauzasalaski: ok, will do17:38
bauzasthat's it17:38
alaskivineetmenon: I have not.  it's a TODO for me that I haven't done yet17:38
*** banix__ has quit IRC17:38
alaskibauzas: thanks17:39
alaskiI would like to point out https://review.openstack.org/#/c/145922/17:39
*** mrmartin has joined #openstack-meeting-317:39
alaskiand that's it from me17:39
alaskianything else?17:39
belmoreiraalaski: we would like to contribute in the implementation17:39
vineetmenonbelmoreira: +117:40
alaskibelmoreira: great.  ping me outside of the meeting and we can discuss that17:40
belmoreiraalaski: ok17:40
alaskidansmith: anything from you? :)17:41
dansmithmove to adjourn :)17:41
alaskiseconded17:41
bauzassld17:42
bauzassold17:42
alaskimotion passes17:42
alaskithanks everyone!17:42
alaski#endmeeting17:42
bauzasthanks17:42
openstackMeeting ended Wed Jan 14 17:42:26 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-01-14-17.00.html17:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-01-14-17.00.txt17:42
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-01-14-17.00.log.html17:42
belmoreirathanks17:42
*** mriedem has left #openstack-meeting-317:43
vineetmenonbye17:43
*** melwitt has left #openstack-meeting-317:44
*** sarob has joined #openstack-meeting-317:45
*** Longgeek has joined #openstack-meeting-317:49
*** vineetmenon has quit IRC17:50
*** annegentle_ has quit IRC17:51
*** Salman has joined #openstack-meeting-317:54
*** Sukhdev has quit IRC17:54
*** sarob has quit IRC17:54
*** ChuckC has joined #openstack-meeting-317:55
*** ongk has joined #openstack-meeting-317:55
*** Piet has joined #openstack-meeting-317:55
*** sahid has quit IRC17:55
*** devvesa has quit IRC17:57
*** ChuckC_ has quit IRC17:57
*** dconde has joined #openstack-meeting-317:59
*** dconde has quit IRC18:00
*** sbalukoff has joined #openstack-meeting-318:03
*** VW_ has quit IRC18:03
*** Networkn3rd has quit IRC18:06
*** JeanBriceCombebi has quit IRC18:12
*** JeanBriceCombebi has joined #openstack-meeting-318:12
*** Salman has quit IRC18:13
*** banix has quit IRC18:14
*** Salman2 has joined #openstack-meeting-318:15
*** VW_ has joined #openstack-meeting-318:18
*** sarob has joined #openstack-meeting-318:23
*** wuhg has quit IRC18:24
*** mrmartin has quit IRC18:24
*** pkoniszewski has quit IRC18:25
*** banix has joined #openstack-meeting-318:27
*** banix has quit IRC18:29
*** banix has joined #openstack-meeting-318:29
*** mwagner_lap has quit IRC18:35
*** mrmartin has joined #openstack-meeting-318:37
*** yamahata has joined #openstack-meeting-318:40
*** sarob_ has joined #openstack-meeting-318:43
*** eghobo has joined #openstack-meeting-318:45
*** sarob has quit IRC18:45
*** igordcard has quit IRC18:48
*** JeanBriceCombebi has quit IRC18:51
*** Networkn3rd has joined #openstack-meeting-318:54
*** sarob_ is now known as sarob18:54
*** isq has joined #openstack-meeting-318:55
*** isq has quit IRC18:56
*** isq has joined #openstack-meeting-318:57
*** wdutch has quit IRC18:58
*** MaxV has joined #openstack-meeting-319:01
*** johnthetubaguy is now known as zz_johnthetubagu19:05
*** sarob has quit IRC19:08
*** alexpilotti has quit IRC19:10
*** egallen has quit IRC19:13
*** sunny_ has quit IRC19:15
*** pkoniszewski has joined #openstack-meeting-319:16
*** Rockyg has joined #openstack-meeting-319:19
*** sunny_ has joined #openstack-meeting-319:20
*** pkoniszewski has quit IRC19:22
*** pkoniszewski has joined #openstack-meeting-319:23
*** sunny_ has quit IRC19:25
*** jtomasek has quit IRC19:27
*** sunny_ has joined #openstack-meeting-319:28
*** belmoreira has quit IRC19:34
*** phil_h has quit IRC19:38
*** Sukhdev has joined #openstack-meeting-319:46
*** sunny_ has quit IRC19:46
*** sarob has joined #openstack-meeting-319:46
*** wchrisj has joined #openstack-meeting-319:49
*** sunny_ has joined #openstack-meeting-319:52
*** tqtran has joined #openstack-meeting-319:52
*** sarob has quit IRC19:53
*** clu_ has joined #openstack-meeting-319:54
*** zhipeng has quit IRC19:54
*** crobertsrh has joined #openstack-meeting-319:55
*** mwagner_lap has joined #openstack-meeting-319:56
*** bradjones has joined #openstack-meeting-319:56
*** david-lyle_ has joined #openstack-meeting-319:56
*** ericpeterson has joined #openstack-meeting-319:58
*** TravT has joined #openstack-meeting-319:59
*** gary-smith has joined #openstack-meeting-320:00
*** rbertram has joined #openstack-meeting-320:00
mrunge#startmeeting Horizon20:00
*** jgravel has joined #openstack-meeting-320:00
openstackMeeting started Wed Jan 14 20:00:28 2015 UTC and is due to finish in 60 minutes.  The chair is mrunge. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
openstackThe meeting name has been set to 'horizon'20:00
mrungehello there20:00
ericpetersonhello20:00
rbertramhi20:00
rhagartyhello20:00
jgravelhi20:00
gary-smithhello20:01
*** sambetts has joined #openstack-meeting-320:01
*** EmilyW has joined #openstack-meeting-320:01
crobertsrhhello/20:01
*** lhcheng has joined #openstack-meeting-320:01
bradjoneso/20:01
mrunge#chair mrunge david-lyle_20:01
openstackCurrent chairs: david-lyle_ mrunge20:01
mrunge:D20:01
clu_hi20:01
mrungeDavid will show up in a few mins20:01
TravTo/20:01
mrungewe don't have an agenda for today20:02
*** doug-fish has joined #openstack-meeting-320:02
*** EmilyW has quit IRC20:02
*** TravT has quit IRC20:02
gary-smithis it a hidden agenda? :-)20:02
*** EmilyW has joined #openstack-meeting-320:03
*** TravT has joined #openstack-meeting-320:03
*** banix has quit IRC20:03
mrungeso, if I remember right, we did not finish last weeks meeting20:03
sambettso/20:03
mrungeI'll leave announcements for David, when he'll show up20:04
*** robcresswell has joined #openstack-meeting-320:04
mrunge#topic Angular work blockers20:04
mrungeRichard Jones, are you there, by any chance?20:05
mrungeor tqtran ?20:05
TravTwell, we got the version upgrade in as well as angular-bootstrap20:05
tqtranactually, i have something i wanted to bring up, just to gauge community interest20:05
tqtranso kelly from HP have been working on the new angular table stuff20:06
tqtranits available here: https://github.com/ongk/responsive-smart-table20:06
*** banix has joined #openstack-meeting-320:06
tqtranjust wanted to know if people are generally ok with the newer tables looking a bit different20:06
*** sunny_ has quit IRC20:07
*** SridharRamaswamy has quit IRC20:07
mrungetqtran, thanks for sharing!20:07
david-lyle_different how?20:07
tqtranits similar to what piet has shown on envision20:07
*** esp has joined #openstack-meeting-320:07
tqtranwell, similar is the wrong word, its basically the implementation of what piet showed20:07
*** esp has left #openstack-meeting-320:07
TravTSo, you can see the look and feel in the launch instance mocks.20:07
TravThttp://invis.io/SG1YAG2WC20:08
*** absubram has joined #openstack-meeting-320:08
tqtranok silence means we're in the green? haha20:09
rbertramMy general answer is I like it, though I'm still thinking about some of the details. I am involved in discussions on this.20:09
*** david-lyle has joined #openstack-meeting-320:10
rbertramThe question may be: can we break consistency with the existing tables for Kilo?20:10
gary-smithAm I seeing correctly that all row actions are hidden inside of the + ?20:10
TravTgary-smith:20:10
TravTno20:10
mrunge#chair mrunge david-lyle david-lyle_20:10
openstackCurrent chairs: david-lyle david-lyle_ mrunge20:10
TravTthat is actually specific to launch instance20:10
david-lyle_#chair david-lyle20:10
PietDid I hear my name?20:10
openstackCurrent chairs: david-lyle david-lyle_ mrunge20:10
TravTit is how you select one.  This was the result of several weeks of usability testing20:10
tqtrangary-smith: i high recommend that you download the repo above, it has several examples20:11
gary-smithI am looking at the example20:11
david-lyletqtran: can you repost the link for invision?20:11
david-lyleon real screen now20:11
tqtranthe one in the invision is a bit different20:11
tqtranpiet: do you have a link to the one kelly implemented?20:12
david-lyleoops, that was TravT20:12
tqtran  http://invis.io/SG1YAG2WC20:12
TravTok, so that is launch instance20:12
PietFinal Design for Launch Instance http://invis.io/DW1XZIUH220:12
TravThere is an alternate one that shows actions in more of a standard listing table (not a selection table)20:13
TravThttp://invis.io/YA1KV4VTP20:13
* david-lyle munging topics20:13
TravTPiet: if there is a newer one, please share.20:13
robcresswellWhy hide the first row action? Normally the first is shown, usually edit. Seems that would be faster, less clicks, than hiding them all.20:13
tqtranyes, the latest one TravT showed is what kelly implemented20:13
PietJust shared most recent Launch Instance - http://invis.io/DW1XZIUH220:13
david-lylein that case is create flavor the only table action?20:14
TravTdavid-lyle: which one are you referencing?20:14
tqtranhttps://openstack.invisionapp.com/share/YA1KV4VTP#/screens20:15
tqtranim sure we can add more batch actions as needed, its just a mock up20:15
david-lyletqtran: my concern is layout20:16
TravTrobcroswell: i think you are referencing the launch instance mocks.  In that one, if you click the + button, it selects it and pops it to the selected ones.20:16
david-lyleI've talked to Piet and he and seeing examples has convinced me that we can put filtering and actions on different lines20:17
david-lyleallowing us to expose more actoins20:17
TravTrobcrosswell: this one may make it more obvious how that one works: https://openstack.invisionapp.com/share/SG1YAG2WC#/screens/55177821?maintainScrollPosition=false20:17
tqtranunderstood, basically, the question is: are we ok with moving new angular table in this direction? theres still time for us to determine the actual layout, but we can begin work down this road20:17
*** egallen has joined #openstack-meeting-320:17
rbertramtqtran: you want us to focus on the table only, not the overal context?20:18
*** jtomasek has joined #openstack-meeting-320:18
tqtranyes just focus on the table styling primarily20:18
david-lylewe're changing technology stack, there isn't a better time to change look and feel20:18
TravTdavid-lyle: +120:18
david-lyleif we can improve usability, we should20:19
tqtranok perfect, thats all i needed to hear20:19
david-lyleadditionally forcing new tools to look like old is a waste of time IMO20:19
mrungeyes!20:19
wchrisjdavid-lyle: +120:19
mrungeand we were changing that anyways20:19
david-lyleyes20:19
david-lyleSo yeah, move forward20:20
rbertramI agree. So Kilo will have some tables of the old style that have not been converted yet, right?20:20
david-lyleI want to point out for launch instance20:20
david-lylerbertram: yes, but I'm thinking there won't be more than 1 or two in the new format20:21
david-lyleand those would likely be in the wizard20:21
rbertramdavid-lyle: good, making sure we have right expectation20:21
rbertram(foreseeing concerns raised about consistency at end of kilo)20:21
david-lylerbertram: it's never been a concern before ;)20:22
rbertramah, ok20:22
david-lyleback to launch20:22
david-lylewe need to close on the design20:22
david-lyleand move the bp to approved20:22
TravTyes, this will be very helpful. today we had a review with Piet on the in progress styling.20:23
david-lyleunless there is amazing concerns raised in the next day or two, I'm going to move to approved20:23
PietAgreed20:23
TravTbtw, for reference: https://blueprints.launchpad.net/horizon/+spec/launch-instance-redesign20:23
PietSome of the questions I'm seeing are around implementation of the design.  Fully anticipate some compromises due to constraints20:24
david-lyleI feel it's a strong improvement and we can move incrementally from there if necessary20:24
david-lylePiet: that's always a concern when doing design divorced from implementation20:25
rbertramTravT & Piet: is there a central place for input on the new table design? separate from the contexts of the tables.20:25
david-lylethere will be compromises to make20:25
*** pkoniszewski has quit IRC20:25
PietJust as an FYI, I'm trying to set the high level vision for the design.  Try to motivate the group to see the where we can go...20:26
tqtranwhen we're done discussing this, i do have another topic to bring up, this one concerns consolidating javascripts.20:26
TravTrbertram:  this project for now: http://invis.io/YA1KV4VTP20:26
rbertramTravT: thx20:27
TravTI also would like to talk about the base REST API patch, even if r1chardj0n3s isn't here20:27
tqtranyou can go first TravT20:27
TravTthx.20:27
PietReal quick thanks to all of you that helped with the UX design process!20:27
TravTso, we have a lot of dependencies between the launch instance and table designs.20:28
TravTone of them is at least getting the base rest API utility patch landed20:28
TravThttps://review.openstack.org/#/c/13667620:28
TravTcurrent debate seems to be a final question on validation with lhcheng and david-lyle20:28
david-lyleTravT: I talked to Richard about that, I'm trying to get back to it20:28
TravTi put up a potential compromise solution, so would like feedback on that.20:28
*** lhcheng is now known as lhcheng_afk20:29
TravTdavid-lyle: okay.20:29
TravTthen we can focus more on the actual API's and hopefully iterate there20:30
david-lyleI think his point is valid that out interactions with the clients could be made consistent, contracts with the client wrappers20:30
david-lyleI'll try to hit again today20:30
TravTok.  thanks20:30
TravTtqtran: over to you.20:30
tqtranthanks TravT20:31
tqtranso basically, we're going to end up with angular code in openstack_dashboard20:31
tqtranthey belong there because its specific to each panel20:31
tqtranso user identity will have its own js controller file, etc...20:31
tqtranthe way we have it right now, all of your js is in horizon20:32
*** ivar-lazzaro has joined #openstack-meeting-320:32
tqtran*our js20:32
tqtranthe idea was that we only incorporate js libs in horizon, and for panel specific js, we have it in openstack_dashboard20:32
tqtrani have tried pulling most things from horizon, but that doesnt work because we have selenium tests using those js in horizon20:33
tqtranso we're actually stuck with putting most of our legacy js files in horizon20:33
tqtranbut for the new angular js stuff, i propose that we start moving them to openstack_dashboard, wanted to get a consensus on this20:34
rbertramtqtran: what about general directives & even controllers that are used in multiple panels? still in openstack_dashboard?20:34
mrungetqtran, but, if someone would use horizon as framework, he would re-use that js code anyways?20:34
tqtranhttps://review.openstack.org/#/c/141457/ here is the patch20:34
*** sarob has joined #openstack-meeting-320:34
tqtranmrunge: its possible, but the js code is very specific to each panel20:35
tqtranmrunge: its like arguing that our panel code in python today can be reuse as well20:35
mrungedarn, I hoped, it would be a bit more maintainable20:35
TravTwell, some things still will be in horizon20:35
mattfarinatqtran putting the angular code that's specific to a panel in openstack_dashboard makes sense.20:36
tqtranmrunge: https://review.openstack.org/#/c/133767/25/horizon/static/horizon/js/angular/dashboards/hz.identity.users.js here is an example of a controller in js specifically for the users panel20:36
tqtranrbertram, TravT: yes, reusable things like wizard, tables, will still stay in horizon20:36
david-lyletqtran: there will be wizard framework and step content20:36
mrungetqtran, and why the heck can't we put that to openstack_dashboard?20:36
david-lylethose two could be logically split horizon and openstack_dashboard20:37
tqtranmrunge: we could, i wouldnt be oppose to that either20:37
david-lyleI think mrunge is referring to those common base wdigets20:37
mrungedavid-lyle, yes and no20:37
*** sunny_ has joined #openstack-meeting-320:37
david-lylespecific panel content and steps certainly lives in openstack_dashboard, as it does today20:37
mrungeI would like to have stuff separated as much as possible20:38
mrungethis makes it easier to maintain it20:38
david-lyleI could see, more things in openstack_dashboard like usage20:38
david-lylethings used in multiple views20:39
tqtranmrunge: just to clarify, so you're saying that you like it better if the reusable JS components live in horizon, and the panel-specific JS code lives in dashboard?20:40
mrungetqtran, I'd say: yes20:41
tqtranmrunge: ok, then i guess we're all pretty much in agreement20:41
mrunge:D20:41
tqtranone last thing, does it make sense to combine _conf and _scripts?20:41
*** sunny_ has quit IRC20:41
mrungetqtran, nope.20:42
tqtrani think it makes its easier to have all of our js dependencies in one place20:42
mrungetqtran, I added a comment to that patch20:42
tqtrannot sure i understand why we need 220:42
mrungeeasier to read?20:42
*** john-davidge has joined #openstack-meeting-320:42
mrungesmaller files for a dedicated reason rather than a large file with everything mixed up?20:43
tqtranyes, but its very confusing for newer developers. we're generally use to having a single index.html where all of our scripts are loaded20:43
tqtranthe only thing in there are script tags20:43
mrungenew developers are python developers.20:43
tqtrani would argue that its easier to read when all scripts are in one place20:43
mrungeso, almost *everything* is new20:43
mrungeI'm not a friend of huge spaghetti-like files20:44
rhagartyhello20:44
tqtranthe way we have it right now, we have import statements for angular modules in two different places20:45
tqtranits very confusing even to me where i should put my js script20:45
david-lyleI need to look at the content of each again, but unless they serve different purposes, I'm not sure I see the need for a split20:46
david-lyleis one in horizon and one in openstack_dashboard?20:46
*** Rockyg has quit IRC20:46
tqtrannone in openstack atm20:46
mrungedavid-lyle, it's this patch here: https://review.openstack.org/#/c/141457/20:46
tqtranall the js scripts are in horizon20:46
mrungeand I was arguing: no need to move all stuff from one file to another20:47
*** Rockyg has joined #openstack-meeting-320:47
david-lyleI know I looked at this before, trying to resync20:47
tqtranyes, i also introduced the idea in the ML20:47
*** ericpeterson has left #openstack-meeting-320:48
david-lyletqtran: I recall20:49
*** ivar-lazzaro has quit IRC20:50
*** ivar-lazzaro has joined #openstack-meeting-320:50
david-lyleok, I have to look more20:51
tqtranok, just wanted to bring it up so people are aware. im open to feedback and if there is a good reason, im all ears.20:52
gugl2tqtran, TravT question if I have a change which has some js code...I am required to use angularjs now?20:52
*** SridharRamaswamy has joined #openstack-meeting-320:52
TravTActually, we are looking to move to COBOL.20:52
mrungeTravT, +120:53
tqtrangugl2: depends on the change, is it to legacy js code? if it is, then just stick with jquery. but the newer stuff should be angular.20:53
TravTwe are looking at angular for new development and tqtran is working on updating some older things to angular20:53
tqtranTravT: lol COBOL yes, my favorite20:53
rbertramtravt: bet you have an angboard alternative called cobboard20:53
gugl2tqtran, ok, thanks20:53
TravTlol20:53
tqtranrbertram: lol20:53
*** markmcclain has joined #openstack-meeting-320:54
* david-lyle is regretting finding wifi20:54
*** ivar-lazzaro has quit IRC20:54
mrungewe had a patch set celebrating it's first birthday.20:54
mrungecould we get another core to approve https://review.openstack.org/#/c/65793/ ?20:54
tqtrangugl2: http://campus.codeschool.com/courses/shaping-up-with-angular-js/intro interactive tutorial if you're interested20:54
*** ivar-lazzaro has joined #openstack-meeting-320:55
gugl2tqtran, sounds good, thanks.20:55
rbertramIf we are in that part of the meeting - Serial Console https://review.openstack.org/#/c/144659/ is ready for review. But the BP has not gotten any attention.20:55
tqtranmrunge: sounds like you should bug akihiro20:55
rbertramDoes BP have to be approved for patch to merge?20:55
mrungetqtran, yes, but he's not here at the moment20:56
mrungerbertram, I thought it was already approved?20:56
david-lylerbertram: it should be, but it doesn't always happen that way20:56
rbertram:-)20:56
bradjonesQuick update on Curvature topology BP, would really appreciate some UX feedback https://review.openstack.org/#/c/141078/ need to clean up code this afternoon and will remove the -1 workflow tomorrow20:57
mrungerbertram, I mean, the bp should already have been approved?20:57
rbertramhttps://blueprints.launchpad.net/horizon/+spec/serial-console - marked as "needs approval"20:58
TravTbradjones: i do have a question.  will that topology be easy to include in a number of pages?20:58
david-lyledevlaps: around?20:58
*** sunny_ has joined #openstack-meeting-320:59
bradjonesTravT: yeah it should be as long as the page calls the init function and the json is rendered I don't see why not20:59
TravTbradjones: great, because there is some interest in being able to bring it up within context on a few places.21:00
TravTe.g. instance details21:00
david-lyletime's up. Thanks mrunge for leading. Have a great week and I should back in a more full capacity late next week. Thanks everyone.21:00
bradjonesTravT: awesome that sounds good21:00
david-lyle#endmeeting21:00
openstackMeeting ended Wed Jan 14 21:00:58 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-01-14-20.00.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-01-14-20.00.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-01-14-20.00.log.html21:01
TravTthank you!21:01
mrungethanks everyone21:01
bradjonesthanks21:01
*** david-lyle has quit IRC21:01
*** gary-smith has left #openstack-meeting-321:01
*** rbertram has left #openstack-meeting-321:02
*** jgravel has left #openstack-meeting-321:02
*** bradjones has left #openstack-meeting-321:02
*** tqtran has left #openstack-meeting-321:02
*** Rockyg has quit IRC21:04
*** david-lyle_ has quit IRC21:07
*** ongk has left #openstack-meeting-321:07
*** devlaps has quit IRC21:07
*** sambetts has left #openstack-meeting-321:08
*** jrist has quit IRC21:08
*** AJaeger has quit IRC21:11
*** KLevenstein has joined #openstack-meeting-321:11
*** jcoufal has joined #openstack-meeting-321:12
*** KLevenstein has quit IRC21:12
*** sunny_ has quit IRC21:12
*** devlaps has joined #openstack-meeting-321:17
*** mrunge has quit IRC21:20
*** jrist has joined #openstack-meeting-321:21
*** bpokorny has joined #openstack-meeting-321:22
*** sergef has quit IRC21:22
*** erikmwilson has quit IRC21:23
*** jtomasek has quit IRC21:24
*** AJaeger has joined #openstack-meeting-321:24
*** sarob has quit IRC21:24
*** sarob has joined #openstack-meeting-321:25
*** julim has quit IRC21:27
*** sarob has quit IRC21:29
*** erikmwilson has joined #openstack-meeting-321:33
*** robcresswell has quit IRC21:34
*** EmilyW has quit IRC21:35
*** mrmartin has quit IRC21:38
*** egallen has quit IRC21:38
*** sarob has joined #openstack-meeting-321:40
*** Networkn3rd has quit IRC21:40
*** EmilyW has joined #openstack-meeting-321:41
*** egallen has joined #openstack-meeting-321:41
*** david-lyle has joined #openstack-meeting-321:42
*** markmcclain has quit IRC21:44
*** erikmwilson has quit IRC21:45
*** Sukhdev has quit IRC21:45
*** Salman2 has quit IRC21:48
*** david-lyle has quit IRC21:49
*** thangp has quit IRC21:50
*** EmilyW has left #openstack-meeting-321:50
*** erikmwilson has joined #openstack-meeting-321:51
*** absubram has quit IRC21:52
*** erikmwilson has quit IRC21:53
*** crobertsrh is now known as _crobertsrh21:54
*** egallen has quit IRC21:55
*** ivar-lazzaro has quit IRC22:00
*** ivar-lazzaro has joined #openstack-meeting-322:00
*** SridharRamaswamy has quit IRC22:02
*** TravT has quit IRC22:05
*** Rockyg has joined #openstack-meeting-322:06
*** MaxV has quit IRC22:08
*** sunny_ has joined #openstack-meeting-322:13
*** s3wong has joined #openstack-meeting-322:15
*** SridharRamaswamy has joined #openstack-meeting-322:16
*** mattfarina has quit IRC22:18
*** sunny_ has quit IRC22:18
*** nelsnels_ has joined #openstack-meeting-322:21
*** banix has quit IRC22:22
*** VW_ has quit IRC22:22
*** lblanchard has quit IRC22:25
*** nelsnelson has quit IRC22:25
*** lhcheng_afk has left #openstack-meeting-322:25
*** nelsnels_ has quit IRC22:27
*** nelsnelson has joined #openstack-meeting-322:28
*** david-lyle has joined #openstack-meeting-322:33
*** Sukhdev has joined #openstack-meeting-322:33
*** jgrimm is now known as zz_jgrimm22:39
*** ChuckC_ has joined #openstack-meeting-322:41
*** ChuckC_ has quit IRC22:42
*** jcoufal has quit IRC22:43
*** ChuckC has quit IRC22:45
*** markmcclain has joined #openstack-meeting-322:48
*** markmcclain has quit IRC22:52
*** markmcclain has joined #openstack-meeting-322:52
*** markmcclain has quit IRC22:54
*** markmcclain1 has joined #openstack-meeting-322:54
*** SridharRamaswamy has quit IRC22:56
*** VW_ has joined #openstack-meeting-322:58
*** markmcclain1 has quit IRC22:58
*** Rockyg has quit IRC22:58
*** peristeri has quit IRC23:10
*** carl_baldwin has quit IRC23:11
*** Rockyg has joined #openstack-meeting-323:13
*** sunny_ has joined #openstack-meeting-323:14
*** sunny_ has quit IRC23:14
*** david-lyle has quit IRC23:16
*** SridharRamaswamy has joined #openstack-meeting-323:22
*** watanabe_isao has joined #openstack-meeting-323:23
*** watanabe_isao has quit IRC23:23
*** SridharRamaswamy has quit IRC23:23
*** ChuckC_ has joined #openstack-meeting-323:25
*** SridharRamaswamy has joined #openstack-meeting-323:26
*** watanabe_isao has joined #openstack-meeting-323:27
*** SridharRamaswamy has quit IRC23:27
*** SridharRamaswamy has joined #openstack-meeting-323:28
*** SridharRamaswamy has quit IRC23:29
*** SridharRamaswamy has joined #openstack-meeting-323:33
*** SridharRamaswamy has quit IRC23:37
*** reed has quit IRC23:39
*** Rockyg has quit IRC23:42
*** Rockyg has joined #openstack-meeting-323:42
*** wuhg has joined #openstack-meeting-323:44
*** Piet has quit IRC23:48
*** sigmavirus24 is now known as sigmavirus24_awa23:52
*** Rockyg has quit IRC23:55
*** ongk has joined #openstack-meeting-323:55
*** Rockyg has joined #openstack-meeting-323:56
*** SridharRamaswamy has joined #openstack-meeting-323:59

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