| *** yamahata has joined #openstack-meeting-alt | 00:01 | |
| *** balajiiyer1 has quit IRC | 00:04 | |
| *** balajiiyer1 has joined #openstack-meeting-alt | 00:11 | |
| *** sarob has quit IRC | 00:17 | |
| *** sarob has joined #openstack-meeting-alt | 00:17 | |
| *** cweid has quit IRC | 00:18 | |
| *** jmontemayor has quit IRC | 00:18 | |
| *** sarob has quit IRC | 00:22 | |
| *** tanisdl has quit IRC | 00:31 | |
| *** sacharya has joined #openstack-meeting-alt | 00:33 | |
| *** amytron has quit IRC | 00:40 | |
| *** pdmars has quit IRC | 00:43 | |
| *** ViswaV has joined #openstack-meeting-alt | 00:44 | |
| *** IlyaE has joined #openstack-meeting-alt | 00:46 | |
| *** alazarev has joined #openstack-meeting-alt | 00:46 | |
| *** ViswaV has quit IRC | 00:49 | |
| *** rwsu has quit IRC | 01:00 | |
| *** yogesh has joined #openstack-meeting-alt | 01:06 | |
| *** amytron has joined #openstack-meeting-alt | 01:09 | |
| *** jjmb has joined #openstack-meeting-alt | 01:16 | |
| *** venkatesh has joined #openstack-meeting-alt | 01:24 | |
| *** nosnos has joined #openstack-meeting-alt | 01:29 | |
| *** mozawa has joined #openstack-meeting-alt | 01:31 | |
| *** venkatesh has quit IRC | 01:31 | |
| *** amotoki has quit IRC | 01:31 | |
| *** yogesh has quit IRC | 01:34 | |
| *** yogesh has joined #openstack-meeting-alt | 01:35 | |
| *** kebray_ has quit IRC | 01:37 | |
| *** yogesh has quit IRC | 01:39 | |
| *** venkatesh has joined #openstack-meeting-alt | 01:40 | |
| *** venkatesh has quit IRC | 01:41 | |
| *** xuhanp has joined #openstack-meeting-alt | 01:42 | |
| *** alazarev has quit IRC | 01:45 | |
| *** sballe has quit IRC | 01:47 | |
| *** sballe has joined #openstack-meeting-alt | 01:47 | |
| *** sballe has quit IRC | 01:55 | |
| *** sacharya has quit IRC | 01:57 | |
| *** bdpayne has quit IRC | 01:58 | |
| *** IlyaE has quit IRC | 02:12 | |
| *** GheRiver1 has joined #openstack-meeting-alt | 02:13 | |
| *** plomakin_ has joined #openstack-meeting-alt | 02:14 | |
| *** dkehn_ has joined #openstack-meeting-alt | 02:14 | |
| *** dkehn has quit IRC | 02:15 | |
| *** plomakin has quit IRC | 02:15 | |
| *** GheRivero has quit IRC | 02:15 | |
| *** julim has quit IRC | 02:15 | |
| *** DennyZhang has joined #openstack-meeting-alt | 02:20 | |
| *** dkehn_ is now known as dkehn | 02:23 | |
| *** gduan has quit IRC | 02:28 | |
| *** amcrn has quit IRC | 02:29 | |
| *** garyduan has joined #openstack-meeting-alt | 02:33 | |
| *** sc68cal has quit IRC | 02:33 | |
| *** eankutse has joined #openstack-meeting-alt | 02:35 | |
| *** sc68cal has joined #openstack-meeting-alt | 02:36 | |
| *** alazarev has joined #openstack-meeting-alt | 02:43 | |
| *** alazarev has quit IRC | 02:43 | |
| *** julim has joined #openstack-meeting-alt | 02:43 | |
| *** sc68cal has quit IRC | 02:45 | |
| *** yogesh has joined #openstack-meeting-alt | 02:45 | |
| *** sc68cal has joined #openstack-meeting-alt | 02:46 | |
| *** sc68cal has quit IRC | 02:48 | |
| *** nati_ueno has quit IRC | 02:50 | |
| *** yogesh has quit IRC | 02:50 | |
| *** balajiiyer1 has quit IRC | 02:52 | |
| *** sc68cal_ has joined #openstack-meeting-alt | 02:54 | |
| *** sc68cal_ has quit IRC | 02:54 | |
| *** sc68cal_ has joined #openstack-meeting-alt | 02:56 | |
| *** sarob has joined #openstack-meeting-alt | 03:02 | |
| *** doug_shelley66 has quit IRC | 03:07 | |
| *** kebray_ has joined #openstack-meeting-alt | 03:11 | |
| *** NehaV has joined #openstack-meeting-alt | 03:13 | |
| *** banix has quit IRC | 03:24 | |
| *** sarob has quit IRC | 03:25 | |
| *** sarob has joined #openstack-meeting-alt | 03:26 | |
| *** gokrokve has joined #openstack-meeting-alt | 03:29 | |
| *** arnaud___ has quit IRC | 03:30 | |
| *** arnaud__ has quit IRC | 03:31 | |
| *** julim has quit IRC | 03:35 | |
| *** balajiiyer has joined #openstack-meeting-alt | 03:37 | |
| *** sarob has quit IRC | 03:38 | |
| *** kebray_ has quit IRC | 03:38 | |
| *** sarob has joined #openstack-meeting-alt | 03:39 | |
| *** kebray_ has joined #openstack-meeting-alt | 03:40 | |
| *** coolsvap has quit IRC | 03:46 | |
| *** sarob has quit IRC | 03:50 | |
| *** csaba|afk is now known as csaba | 03:51 | |
| *** mat-lowery has joined #openstack-meeting-alt | 03:51 | |
| *** kebray_ has quit IRC | 03:55 | |
| *** banix has joined #openstack-meeting-alt | 03:56 | |
| *** DennyZhang has quit IRC | 03:56 | |
| *** sarob has joined #openstack-meeting-alt | 04:02 | |
| *** kebray_ has joined #openstack-meeting-alt | 04:03 | |
| *** kebray_ has quit IRC | 04:04 | |
| *** sarob has quit IRC | 04:07 | |
| *** amotoki has joined #openstack-meeting-alt | 04:07 | |
| *** harlowja is now known as harlowja_away | 04:07 | |
| *** vipul has quit IRC | 04:08 | |
| *** vipul has joined #openstack-meeting-alt | 04:08 | |
| *** mat-lowery_ has joined #openstack-meeting-alt | 04:12 | |
| *** mat-lowery has quit IRC | 04:13 | |
| *** mat-lowery_ is now known as mat-lowery | 04:13 | |
| *** harlowja_away is now known as harlowja | 04:14 | |
| *** SushilKM has joined #openstack-meeting-alt | 04:14 | |
| *** eankutse has quit IRC | 04:17 | |
| *** cody-somerville has quit IRC | 04:17 | |
| *** kebray_ has joined #openstack-meeting-alt | 04:19 | |
| *** kebray_ has quit IRC | 04:30 | |
| *** cody-somerville has joined #openstack-meeting-alt | 04:31 | |
| *** kebray_ has joined #openstack-meeting-alt | 04:32 | |
| *** kebray_ has quit IRC | 04:38 | |
| *** ijw has quit IRC | 04:40 | |
| *** NehaV has quit IRC | 04:42 | |
| *** SushilKM has quit IRC | 04:43 | |
| *** banix has quit IRC | 04:45 | |
| *** doude has joined #openstack-meeting-alt | 04:46 | |
| *** nosnos_ has joined #openstack-meeting-alt | 04:47 | |
| *** bdpayne has joined #openstack-meeting-alt | 04:49 | |
| *** cody-somerville_ has joined #openstack-meeting-alt | 04:49 | |
| *** banix has joined #openstack-meeting-alt | 04:50 | |
| *** vipuls has joined #openstack-meeting-alt | 04:50 | |
| *** mat-lowery has quit IRC | 04:53 | |
| *** cody-somerville has quit IRC | 04:55 | |
| *** vipul has quit IRC | 04:55 | |
| *** nosnos has quit IRC | 04:55 | |
| *** krtaylor has quit IRC | 04:55 | |
| *** doude_ has quit IRC | 04:55 | |
| *** nadya_ has joined #openstack-meeting-alt | 04:58 | |
| *** krtaylor has joined #openstack-meeting-alt | 05:03 | |
| *** nadya_ has quit IRC | 05:03 | |
| *** banix has quit IRC | 05:06 | |
| *** balajiiyer has quit IRC | 05:08 | |
| *** kebray_ has joined #openstack-meeting-alt | 05:19 | |
| *** bdpayne has quit IRC | 05:25 | |
| *** chandankumar has joined #openstack-meeting-alt | 05:27 | |
| *** gokrokve has quit IRC | 05:38 | |
| *** chandankumar_ has joined #openstack-meeting-alt | 05:39 | |
| *** nati_ueno has joined #openstack-meeting-alt | 05:43 | |
| *** kebray_ has quit IRC | 05:44 | |
| *** bdpayne has joined #openstack-meeting-alt | 05:51 | |
| *** coolsvap has joined #openstack-meeting-alt | 05:53 | |
| *** chandankumar has quit IRC | 06:25 | |
| *** harlowja is now known as harlowja_away | 06:25 | |
| *** balajiiyer1 has joined #openstack-meeting-alt | 06:37 | |
| *** bdpayne has quit IRC | 06:40 | |
| *** balajiiyer1 has quit IRC | 06:41 | |
| *** gokrokve has joined #openstack-meeting-alt | 06:49 | |
| *** gokrokve has quit IRC | 06:54 | |
| *** markwash has quit IRC | 07:08 | |
| *** sergmelikyan has joined #openstack-meeting-alt | 07:09 | |
| *** ityaptin has joined #openstack-meeting-alt | 07:09 | |
| *** markwash has joined #openstack-meeting-alt | 07:11 | |
| *** SergeyLukjanov has joined #openstack-meeting-alt | 07:18 | |
| *** NikitaKonovalov has joined #openstack-meeting-alt | 07:21 | |
| *** dguitarbite has joined #openstack-meeting-alt | 07:23 | |
| *** SushilKM has joined #openstack-meeting-alt | 07:29 | |
| *** SushilKM has quit IRC | 07:29 | |
| *** coolsvap has quit IRC | 07:33 | |
| *** katyafervent has joined #openstack-meeting-alt | 07:33 | |
| *** balajiiyer1 has joined #openstack-meeting-alt | 07:38 | |
| *** balajiiyer1 has quit IRC | 07:42 | |
| *** pnavarro has joined #openstack-meeting-alt | 07:42 | |
| *** coolsvap has joined #openstack-meeting-alt | 07:44 | |
| *** doug_shelley66 has joined #openstack-meeting-alt | 07:46 | |
| *** SergeyLukjanov has quit IRC | 07:47 | |
| *** dguitarbite has quit IRC | 07:48 | |
| *** SergeyLukjanov has joined #openstack-meeting-alt | 07:48 | |
| *** dguitarbite has joined #openstack-meeting-alt | 07:48 | |
| *** sergmelikyan has quit IRC | 07:49 | |
| *** jcoufal has joined #openstack-meeting-alt | 07:50 | |
| *** sergmelikyan has joined #openstack-meeting-alt | 07:54 | |
| *** dguitarbite has quit IRC | 08:10 | |
| *** tnurlygayanov has joined #openstack-meeting-alt | 08:26 | |
| *** doude has left #openstack-meeting-alt | 08:29 | |
| *** balajiiyer1 has joined #openstack-meeting-alt | 08:38 | |
| *** early has quit IRC | 08:40 | |
| *** llu-laptop has joined #openstack-meeting-alt | 08:42 | |
| *** tian has joined #openstack-meeting-alt | 08:42 | |
| *** early has joined #openstack-meeting-alt | 08:42 | |
| *** tsufiev_ has joined #openstack-meeting-alt | 08:42 | |
| *** flaper87|afk is now known as flaper87 | 08:43 | |
| *** balajiiyer1 has quit IRC | 08:43 | |
| *** SergeyLukjanov has quit IRC | 08:44 | |
| *** csaba is now known as csaba|afk | 08:46 | |
| *** nati_ueno has quit IRC | 08:47 | |
| *** rsblendido has joined #openstack-meeting-alt | 08:48 | |
| *** rossella_s has joined #openstack-meeting-alt | 08:48 | |
| *** llu-laptop has left #openstack-meeting-alt | 08:48 | |
| *** aignatov has joined #openstack-meeting-alt | 08:49 | |
| *** shanewang has joined #openstack-meeting-alt | 08:50 | |
| *** shanewang has quit IRC | 08:51 | |
| *** safchain has joined #openstack-meeting-alt | 08:56 | |
| *** _ruhe is now known as ruhe | 09:04 | |
| *** pnavarro has quit IRC | 09:21 | |
| *** SergeyLukjanov has joined #openstack-meeting-alt | 09:25 | |
| *** johnthetubaguy has joined #openstack-meeting-alt | 09:30 | |
| *** sergmelikyan has quit IRC | 09:32 | |
| *** pnavarro has joined #openstack-meeting-alt | 09:33 | |
| *** SushilKM has joined #openstack-meeting-alt | 09:36 | |
| *** johnthetubaguy has quit IRC | 09:38 | |
| *** johnthetubaguy1 has joined #openstack-meeting-alt | 09:38 | |
| *** balajiiyer1 has joined #openstack-meeting-alt | 09:39 | |
| *** SushilKM has quit IRC | 09:41 | |
| *** balajiiyer2 has joined #openstack-meeting-alt | 09:41 | |
| *** balajiiyer1 has quit IRC | 09:44 | |
| *** balajiiyer2 has quit IRC | 09:45 | |
| *** coolsvap has quit IRC | 09:46 | |
| *** derekh has joined #openstack-meeting-alt | 09:52 | |
| *** julienvey has quit IRC | 09:53 | |
| *** nati_ueno has joined #openstack-meeting-alt | 09:58 | |
| *** jtomasek has joined #openstack-meeting-alt | 10:00 | |
| *** plomakin_ has quit IRC | 10:01 | |
| *** plomakin has joined #openstack-meeting-alt | 10:01 | |
| *** nati_ueno has quit IRC | 10:02 | |
| *** mozawa has quit IRC | 10:02 | |
| *** venkatesh has joined #openstack-meeting-alt | 10:05 | |
| *** sergmelikyan has joined #openstack-meeting-alt | 10:05 | |
| *** coolsvap has joined #openstack-meeting-alt | 10:10 | |
| *** SushilKM has joined #openstack-meeting-alt | 10:13 | |
| *** xuhanp has quit IRC | 10:20 | |
| *** SergeyLukjanov has quit IRC | 10:30 | |
| *** jtomasek has quit IRC | 10:34 | |
| *** SushilKM has quit IRC | 10:35 | |
| *** aignatov has quit IRC | 10:37 | |
| *** boris-42 has quit IRC | 10:39 | |
| *** ruhe is now known as _ruhe | 10:42 | |
| *** balajiiyer1 has joined #openstack-meeting-alt | 10:42 | |
| *** nosnos_ has quit IRC | 10:46 | |
| *** balajiiyer1 has quit IRC | 10:46 | |
| *** boris-42 has joined #openstack-meeting-alt | 10:50 | |
| *** venkatesh_ has joined #openstack-meeting-alt | 10:56 | |
| *** jasonb365 has joined #openstack-meeting-alt | 10:57 | |
| *** venkatesh has quit IRC | 10:57 | |
| *** aignatov has joined #openstack-meeting-alt | 11:05 | |
| *** _ruhe is now known as ruhe | 11:06 | |
| *** jprovazn has joined #openstack-meeting-alt | 11:11 | |
| *** jcoufal has quit IRC | 11:14 | |
| *** jcoufal has joined #openstack-meeting-alt | 11:15 | |
| *** venkatesh_ has quit IRC | 11:15 | |
| *** ruhe is now known as _ruhe | 11:18 | |
| *** _ruhe is now known as ruhe | 11:23 | |
| *** boris-42 has quit IRC | 11:29 | |
| *** boris-42 has joined #openstack-meeting-alt | 11:38 | |
| *** csaba|afk is now known as csaba | 11:39 | |
| *** balajiiyer has joined #openstack-meeting-alt | 11:43 | |
| *** yamahata has quit IRC | 11:43 | |
| *** jtomasek has joined #openstack-meeting-alt | 11:46 | |
| *** balajiiyer has quit IRC | 11:47 | |
| *** cody-somerville_ has quit IRC | 11:52 | |
| *** safchain has quit IRC | 11:58 | |
| *** coolsvap has quit IRC | 12:02 | |
| *** ruhe is now known as ruhe_away | 12:05 | |
| *** cody-somerville_ has joined #openstack-meeting-alt | 12:06 | |
| *** ruhe_away is now known as ruhe | 12:08 | |
| *** cody-somerville_ is now known as cody-somerville | 12:10 | |
| *** jasonb365 has quit IRC | 12:16 | |
| *** derekh has quit IRC | 12:23 | |
| *** ruhe is now known as _ruhe | 12:23 | |
| *** balajiiyer1 has joined #openstack-meeting-alt | 12:43 | |
| *** balajiiyer1 has quit IRC | 12:48 | |
| *** _ruhe is now known as ruhe | 12:50 | |
| *** heyongli has joined #openstack-meeting-alt | 12:54 | |
| *** eankutse has joined #openstack-meeting-alt | 12:54 | |
| *** mozawa has joined #openstack-meeting-alt | 12:55 | |
| *** eankutse has quit IRC | 12:56 | |
| *** eankutse has joined #openstack-meeting-alt | 12:56 | |
| *** NikitaKonovalov has quit IRC | 12:57 | |
| *** irenab__ has joined #openstack-meeting-alt | 12:57 | |
| *** derekh has joined #openstack-meeting-alt | 12:57 | |
| *** baoli has joined #openstack-meeting-alt | 12:58 | |
| *** irenab__ is now known as irenab | 12:58 | |
| baoli | #startmeeting PCI passthrough | 13:00 |
|---|---|---|
| openstack | Meeting started Thu Jan 9 13:00:04 2014 UTC and is due to finish in 60 minutes. The chair is baoli. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:00 |
| *** openstack changes topic to " (Meeting topic: PCI passthrough)" | 13:00 | |
| openstack | The meeting name has been set to 'pci_passthrough' | 13:00 |
| baoli | Hi everyone | 13:00 |
| irenab | hi | 13:00 |
| johnthetubaguy1 | hi | 13:00 |
| *** bcrochet|bbl is now known as bcrochet | 13:00 | |
| heyongli | hello | 13:00 |
| *** johnthetubaguy1 is now known as johnthetubaguy | 13:00 | |
| baoli | John, can you lead the discussion today? | 13:00 |
| johnthetubaguy | if you want | 13:01 |
| johnthetubaguy | I would love to talk about this: | 13:01 |
| johnthetubaguy | https://wiki.openstack.org/wiki/Meetings/Passthrough#The_user_view_of_requesting_things | 13:01 |
| johnthetubaguy | what would the nova CLI calls look like | 13:01 |
| johnthetubaguy | when requesting gpu passthrough first | 13:01 |
| *** sadasu has joined #openstack-meeting-alt | 13:02 | |
| *** NikitaKonovalov has joined #openstack-meeting-alt | 13:02 | |
| johnthetubaguy | anyone want to suggest a proposal? | 13:03 |
| irenab | john, I guess it requires flavor creation with extra_spec for GPU device and then regular 'nova boot' | 13:03 |
| *** markvoelker1 has joined #openstack-meeting-alt | 13:03 | |
| johnthetubaguy | +1 on that I think | 13:03 |
| heyongli | current is: nova flavor-key m1.large set "pci_passthrough:alias"="a1:2" | 13:03 |
| heyongli | nova boot --image new1 --key_name test --flavor m1.large 123 | 13:03 |
| johnthetubaguy | right | 13:03 |
| *** BrianB_ has joined #openstack-meeting-alt | 13:04 | |
| johnthetubaguy | I will add that in the wiki | 13:04 |
| irenab | heyongli: and its already supported, right? | 13:04 |
| *** jtomasek has quit IRC | 13:04 | |
| heyongli | yes | 13:04 |
| *** jtomasek has joined #openstack-meeting-alt | 13:05 | |
| johnthetubaguy | so there is a limitation there | 13:05 |
| johnthetubaguy | you only get one PCI passthrough device | 13:05 |
| johnthetubaguy | do we care about that for GPU etc, I think the answer is yet | 13:05 |
| johnthetubaguy | I mean yes | 13:05 |
| irenab | john: you can request number of devices | 13:06 |
| johnthetubaguy | irenab: how? | 13:06 |
| johnthetubaguy | oh, I see | 13:06 |
| irenab | a1:2 => 2 devices | 13:06 |
| heyongli | a1:2, a2:3 | 13:06 |
| johnthetubaguy | but there are all from the same alias | 13:06 |
| heyongli | is also ok | 13:06 |
| johnthetubaguy | ah, so thats a better example | 13:07 |
| johnthetubaguy | we support this today then: a1:2, a2:3 | 13:07 |
| heyongli | and alias support a mixer spec: two 2 type of device | 13:07 |
| irenab | I think you can add another alias too | 13:07 |
| heyongli | you can defien alias: | 13:08 |
| irenab | my feeling is GPU case is quite sovled and we just need to keep it working when adding netowrking case, agree? | 13:08 |
| heyongli | a1={type1} | 13:08 |
| heyongli | then write same: a1={type2} | 13:08 |
| *** eankutse1 has joined #openstack-meeting-alt | 13:08 | |
| heyongli | then you requied a1:2 ,means both type1,and typ2 is ok | 13:08 |
| johnthetubaguy | heyongli: what are the CLI commands for that, I am a bit confused | 13:09 |
| heyongli | in nova configuration now. | 13:09 |
| johnthetubaguy | I added the GPU case here: | 13:09 |
| johnthetubaguy | https://wiki.openstack.org/wiki/Meetings/Passthrough#The_user_view_of_requesting_things | 13:09 |
| heyongli | no API yet | 13:09 |
| johnthetubaguy | I agree we just need to keep it working | 13:09 |
| johnthetubaguy | heyongli: I am talking about the flavor, and what we already have today | 13:09 |
| sadasu | heyongli: cli is confusing ... "x:y"="a:b" would be interpreted as x = a and y = b which is not the case in your CLI | 13:10 |
| heyongli | sadasu: where you see x:y = a:b? | 13:11 |
| johnthetubaguy | hang on, hang on | 13:11 |
| johnthetubaguy | is this valid today | 13:11 |
| johnthetubaguy | nova flavor-key m1.large set "pci_passthrough:alias"=" large_GPU:1,small_GPU:1" | 13:11 |
| sadasu | "pci_passthrough:alias"="a1:2" | 13:11 |
| *** eankutse has quit IRC | 13:11 | |
| baoli | pci_alias='{"name":"Cisco.VIC","vendor_id":"1137","product_id":"0071"}' | 13:11 |
| baoli | this is how it's defined today | 13:11 |
| heyongli | sadasu: this is another problem, john: right ,it works today | 13:11 |
| johnthetubaguy | I don't mind about the alias | 13:11 |
| *** jcoufal has quit IRC | 13:11 | |
| johnthetubaguy | I am trying to ask how the flavor extra specs work today | 13:12 |
| johnthetubaguy | is this valid? | 13:12 |
| johnthetubaguy | nova flavor-key m1.large set "pci_passthrough:alias"=" large_GPU:1,small_GPU:1" | 13:12 |
| *** SushilKM has joined #openstack-meeting-alt | 13:12 | |
| heyongli | johnthetubaguy, it works | 13:12 |
| johnthetubaguy | cool | 13:12 |
| *** SushilKM has left #openstack-meeting-alt | 13:12 | |
| johnthetubaguy | so, we have the user request for vGPU | 13:12 |
| sadasu | I am sure it works...you can make it work...I am just suggesting that it is not very self explanatory | 13:12 |
| johnthetubaguy | now... | 13:12 |
| johnthetubaguy | SRIOV | 13:12 |
| *** eankutse1 has quit IRC | 13:13 | |
| johnthetubaguy | sadasu: it could be better, it could be worse, but I vote we try not to worry about that right now | 13:13 |
| sadasu | ok...get it...lets move to SRIOV | 13:13 |
| heyongli | sadasu: the pci_passthrough:alias, should be this sytle because the scheduler history reason. | 13:13 |
| johnthetubaguy | so first, nova boot direct | 13:14 |
| irenab | SRIOV + neutron, ok? | 13:14 |
| johnthetubaguy | yep | 13:14 |
| irenab | john: suggestion is to add attributes to --nic | 13:15 |
| johnthetubaguy | yep, can we give an example | 13:15 |
| johnthetubaguy | I am trying to type one up and not likeing any of them | 13:15 |
| baoli | Can we go over the jan 8th agenda I posted yesterday? | 13:15 |
| baoli | It contains all the details we have been workign so far | 13:16 |
| johnthetubaguy | OK, we can reference it for sure, I just would love to aggree this user end bit first | 13:16 |
| irenab | baoli: lest go to the last use case | 13:16 |
| *** pdmars has joined #openstack-meeting-alt | 13:17 | |
| irenab | john: do you agree with nova boot format? | 13:17 |
| johnthetubaguy | I can't easily see an example in that text | 13:17 |
| johnthetubaguy | oh wait | 13:17 |
| johnthetubaguy | sorry | 13:17 |
| baoli | nova boot --flavor m1.large --image <image_id> --nic net-id=<net-id>,vnic-type=macvtap,pci-group=<group-name> <vm-name> | 13:17 |
| johnthetubaguy | I am blind | 13:17 |
| johnthetubaguy | macvtap? | 13:17 |
| johnthetubaguy | vs direct vs vnic | 13:17 |
| irenab | or direct or virtio | 13:17 |
| johnthetubaguy | why do we need that? | 13:18 |
| johnthetubaguy | I mean, why do we have three here? | 13:18 |
| baoli | For SRIOV, there is both macvtap and direct | 13:18 |
| *** jtomasek_ has joined #openstack-meeting-alt | 13:18 | |
| *** jcoufal has joined #openstack-meeting-alt | 13:18 | |
| johnthetubaguy | OK, is that not implied by the device type and vif driver config? | 13:18 |
| baoli | With macvtap, it's still pci passthrough but a host macvtap device is involved | 13:19 |
| baoli | Well, the device type and vif driver can support both at the same time on the same device | 13:19 |
| johnthetubaguy | hmm, OK | 13:20 |
| johnthetubaguy | macvtap doesn't look like passthrough | 13:20 |
| johnthetubaguy | it looks like an alternative type of vnic | 13:20 |
| baoli | John, it's one form of PCI passthrough | 13:20 |
| irenab | john, the idea is to work with neutron ML2 plugin that will enable different typpes of vnics | 13:20 |
| baoli | I mean one type | 13:20 |
| *** jtomasek has quit IRC | 13:20 | |
| johnthetubaguy | OK... | 13:21 |
| johnthetubaguy | does the PCI device get attached to the VM? | 13:21 |
| baoli | John, yes. | 13:21 |
| johnthetubaguy | hmm, OK | 13:21 |
| irenab | john: both macvtap and direct are network interfaces on PCI device | 13:21 |
| johnthetubaguy | OK | 13:21 |
| johnthetubaguy | seems like we need that then | 13:22 |
| irenab | direct required vendor driver in the VM and macvtap doesn't | 13:22 |
| baoli | irenab, I think it's the opposite | 13:22 |
| baoli | Irenab, sorry,. you are right | 13:22 |
| johnthetubaguy | so, as a user, I don't want to type all this stuff in, let me suggest something... | 13:22 |
| johnthetubaguy | the user wants a nic-flavor right? | 13:23 |
| johnthetubaguy | defaults to whatever makes sense in your cloud setup | 13:23 |
| baoli | John, we have a special case in which th euser doesn't need to type it | 13:23 |
| irenab | john: exactly | 13:23 |
| johnthetubaguy | but if there are options, the user picks "slow" or "fast" or something like that | 13:23 |
| johnthetubaguy | so I would expect to see... | 13:24 |
| johnthetubaguy | nova boot --flavor m1.large --image <image_id> | 13:24 |
| johnthetubaguy | --nic net-id=<net-id>,vnic-flavor=<slow | fast | foobar> <vm-name> | 13:24 |
| johnthetubaguy | vnic-type is probably better than flavor I guess | 13:25 |
| baoli | John, we don't want to add QoS to this yet, which is a separate effort | 13:25 |
| johnthetubaguy | nova boot --flavor m1.large --image <image_id> | 13:25 |
| johnthetubaguy | Â Â Â Â Â Â Â Â Â Â Â Â Â --nic net-id=<net-id>,vnic-type=<slow | fast | foobar> <vm-name> | 13:25 |
| baoli | But I guess that you can do that | 13:26 |
| johnthetubaguy | this isn't QoS... | 13:26 |
| johnthetubaguy | slow = virtual | 13:26 |
| johnthetubaguy | fast = PCI passthrough | 13:26 |
| heyongli | this mean vnic-type contain vnic-type=macvtap in it? | 13:26 |
| *** safchain has joined #openstack-meeting-alt | 13:26 | |
| irenab | john: agree on this | 13:26 |
| johnthetubaguy | heyongli, the concept represented by vnic-type would include such settings, yes | 13:27 |
| johnthetubaguy | so do we all agree on this: | 13:27 |
| johnthetubaguy | nova boot --flavor m1.large --image <image_id> | 13:27 |
| johnthetubaguy | Â Â Â Â Â Â Â Â Â Â Â Â Â --nic net-id=<net-id>,vnic-type=<slow | fast | foobar> <vm-name> | 13:27 |
| heyongli | i'm ok with it. | 13:27 |
| irenab | john: missing here the 'pointer' to the pool of PCI devices | 13:27 |
| *** jcoufal_ has joined #openstack-meeting-alt | 13:28 | |
| baoli | John, how do you define vnic-type? | 13:28 |
| *** jcoufal has quit IRC | 13:28 | |
| johnthetubaguy | well, thats the question | 13:28 |
| johnthetubaguy | vnic-type is the user concept | 13:28 |
| johnthetubaguy | we need to map that to concrete settings | 13:28 |
| johnthetubaguy | but before we get there, are we OK with the theory of that user facing command? | 13:28 |
| baoli | our original idea was to define a type of vnic that a user would attach its VM to | 13:29 |
| johnthetubaguy | right, thats what I am suggesting here I think... | 13:29 |
| baoli | Can we classify the VNICs to have types of virtio, pci-passthorugh without macvtap, pci-passthourgh with macvta[ | 13:30 |
| baoli | sorry, macvtap | 13:30 |
| johnthetubaguy | the user doesn't care about all that, thats an admin thing, I think | 13:30 |
| johnthetubaguy | the user cares about the offerings, not the implementation | 13:30 |
| johnthetubaguy | at least, thats our general assumption in the current APIs | 13:31 |
| irenab | john: I guess user will be charged differently depending what vnic he has, so probably he should be aware | 13:31 |
| irenab | but logically it should have names meaningful to the user and not technical | 13:31 |
| johnthetubaguy | exactly | 13:31 |
| baoli | #agreed | 13:32 |
| johnthetubaguy | logical names, the users case which one, but they care about the logical name | 13:32 |
| johnthetubaguy | cool… I don't really care what that is, but this works for now I think... | 13:32 |
| johnthetubaguy | boot --flavor m1.large --image <image_id> --nic net-id=<net-id>,nic-type=<slow | fast | foobar> <vm-name> | 13:32 |
| johnthetubaguy | I removed the "v" bit, it seems out of place, but we can have that argument laters | 13:33 |
| irenab | still missing here binding to the PCI devices that allowed for this nic | 13:33 |
| baoli | #agreed | 13:33 |
| johnthetubaguy | irenab: yes, lets do that in a second | 13:33 |
| johnthetubaguy | now one more question... | 13:33 |
| johnthetubaguy | if we have the above, I think we also need this... | 13:34 |
| johnthetubaguy | nova boot --flavor m1.large --image <image_id> --nic port-id=<port-id> | 13:34 |
| johnthetubaguy | i.e. all the port settings come from neutron | 13:34 |
| johnthetubaguy | which means... | 13:34 |
| baoli | John, yes. | 13:34 |
| johnthetubaguy | we probably need this | 13:34 |
| *** xuhanp has joined #openstack-meeting-alt | 13:34 | |
| johnthetubaguy | quantum port-create --fixed-ip subnet_id=<subnet-id>,ip_address=192.168.57.101 <net-id> --nic-type=<slow | fast | foobar> | 13:34 |
| baoli | we had it described in our doc | 13:34 |
| irenab | john: yes, it will be added with the same nic-type attribute | 13:35 |
| johnthetubaguy | cool, appolgies for repeating the obvious | 13:35 |
| johnthetubaguy | just want to get agreement | 13:35 |
| irenab | agree | 13:35 |
| heyongli | agree | 13:35 |
| johnthetubaguy | cool, so does this look correct: | 13:35 |
| johnthetubaguy | https://wiki.openstack.org/wiki/Meetings/Passthrough#The_user_view_of_requesting_things | 13:35 |
| irenab | john: its neutron :) | 13:36 |
| johnthetubaguy | agree, just want to make sure | 13:36 |
| johnthetubaguy | I have little knowlege of neutron these days, but that seems to make sense | 13:36 |
| johnthetubaguy | cool | 13:36 |
| baoli | overall, it looks good | 13:37 |
| johnthetubaguy | so how do we get a mapping from nic-type to macvtap and pci devices | 13:37 |
| johnthetubaguy | I vote macvtap goes into the alias | 13:37 |
| johnthetubaguy | is that crazy? | 13:37 |
| heyongli | +1 | 13:37 |
| irenab | john: do you suggest it to work with flavor? | 13:37 |
| johnthetubaguy | irenab: not really, at least I don't think so | 13:38 |
| johnthetubaguy | irenab: sounds like info that the VIF driver needs | 13:38 |
| irenab | so what do you mean by goes into alias? | 13:38 |
| johnthetubaguy | a good question... | 13:38 |
| heyongli | alias map the nic-type to contain information needed. | 13:39 |
| heyongli | this means the vnic type is one kind of alias | 13:39 |
| *** jtomasek_ has quit IRC | 13:39 | |
| johnthetubaguy | pci_alias='{"name":"Cisco.VIC","vendor_id":"1137","product_id":"0071", "nic-type":"fast", "attach-type":"macvtap"}' | 13:39 |
| heyongli | +1 | 13:40 |
| johnthetubaguy | with nic-type and attach-type as optional, its not that sexy, but could work I think... | 13:40 |
| irenab | not good... | 13:40 |
| baoli | no good | 13:40 |
| irenab | this definition makes it static | 13:40 |
| johnthetubaguy | pci_alias_2='{"name":"Cisco.VIC.Fast","vendor_id":"1137","product_id":"0071", "nic-type":"faster", "attach-type":"direct"}' | 13:40 |
| heyongli | what do you mean static? | 13:40 |
| johnthetubaguy | user chooses "fast" or "faster" | 13:41 |
| irenab | it comes to my previous question regarding pool of available PCI devies for the vnic | 13:41 |
| johnthetubaguy | does that work? | 13:41 |
| irenab | seems you define all of this as part of the alias | 13:41 |
| johnthetubaguy | at the moment, yes | 13:41 |
| baoli | John, if we have done the user's point of view, can we go over the the original post? | 13:42 |
| *** jtomasek has joined #openstack-meeting-alt | 13:42 | |
| johnthetubaguy | baoli: sure, that probably makes sense | 13:42 |
| baoli | Thanks, john | 13:43 |
| irenab | If we want a VM be connected to 3 networks: one via SRIOV direct, one with SRIOV macvtap and one with virtio, how it will be done? | 13:43 |
| johnthetubaguy | this is now | 13:44 |
| johnthetubaguy | one sec... | 13:44 |
| baoli | Thanks Irenab to bring that up | 13:44 |
| *** balajiiyer1 has joined #openstack-meeting-alt | 13:44 | |
| johnthetubaguy | nova boot --flavor m1.large --image <image_id> --nic net-id=<net-id>,nic-type=fast --nic net-id=<net-id>,nic-type=faster <vm-name> | 13:45 |
| johnthetubaguy | •pci_alias='{"name":"Cisco.VIC", devices:[{"vendor_id":"1137","product_id":"0071", address:"*"}],"nic-type":"fast", "attach-type":"macvtap"}' | 13:45 |
| johnthetubaguy | •pci_alias_2='{"name":"Cisco.VIC.Fast",devices:[{"vendor_id":"1137","product_id":"0071", address:"*"}],"nic-type":"faster", "attach-type":"direct"}' | 13:45 |
| heyongli | john, agree | 13:45 |
| johnthetubaguy | hang on, we missed regular... | 13:45 |
| johnthetubaguy | nova boot --flavor m1.large --image <image_id> —nic net-id=<net-id-1> —nic net-id=<net-id-2>,nic-type=fast --nic net-id=<net-id-3>,nic-type=faster  <vm-name> | 13:46 |
| irenab | john: we need the devices that provide network connectivity, how it is going to happen? | 13:47 |
| johnthetubaguy | right, we haven't covered how we implement it | 13:47 |
| johnthetubaguy | just how the user requests it | 13:47 |
| johnthetubaguy | irenab: is that OK for the user request? | 13:48 |
| heyongli | this will works smooth for pci, per my opinion, and the connectivity is also can be a spec of alias | 13:48 |
| irenab | john: if youer has both cisco and mellanox nics, it will have to define cisco_fast and mellanox_fast ... | 13:48 |
| johnthetubaguy | irenab: correct | 13:48 |
| *** balajiiyer1 has quit IRC | 13:48 | |
| johnthetubaguy | unless | 13:48 |
| johnthetubaguy | you want them to share... | 13:48 |
| baoli | John, when you say user, you mean the final user or someone providing the service | 13:48 |
| *** yamahata has joined #openstack-meeting-alt | 13:49 | |
| johnthetubaguy | well we are only really doing the end user at the moment | 13:49 |
| johnthetubaguy | be we should do the PCI alias stuff for the deployer | 13:49 |
| johnthetubaguy | hmm... | 13:49 |
| *** yamahata has quit IRC | 13:50 | |
| johnthetubaguy | pci_alias_2='{"name":"Fast",devices:[{"vendor_id":"1137","product_id":"0071", address:"*","attach-type":"direct"}, {"vendor_id":"123","product_id":"0081", address:"*","attach-type":"macvtap"}],"nic-type":"faster", }' | 13:50 |
| johnthetubaguy | does that work better? | 13:50 |
| *** yamahata has joined #openstack-meeting-alt | 13:51 | |
| irenab | I am not the fan of this alias defintions, but waiting to see how we resolve the network connectivity to agree | 13:51 |
| heyongli | john: just define the pci_alias_2 2 time is works now | 13:51 |
| johnthetubaguy | irenab: what do you mean: "resolve network connectivity"? | 13:51 |
| baoli | John, we are trying to avoid alias on the controller node | 13:51 |
| baoli | first of all | 13:51 |
| sadasu | john: the cisco vic and the mellanox vic could be connected to diff networks | 13:51 |
| sadasu | so they cannot be part of the same alias | 13:52 |
| *** doug_shelley66 has quit IRC | 13:52 | |
| johnthetubaguy | right, thats OK still though, I think | 13:52 |
| baoli | I don't think anyone using pci cares about vendor id, whatsoever | 13:52 |
| sadasu | then both of them would seem equivalent at the time of nova boot | 13:52 |
| johnthetubaguy | baoli: that is a deployer option | 13:52 |
| irenab | how do we make VM to land on the node with PCI devices connecting to the correct provider-network and correct PCI device be allocated | 13:52 |
| *** sballe has joined #openstack-meeting-alt | 13:52 | |
| johnthetubaguy | irenab: OK, thats the scheduling issue then? | 13:53 |
| *** lblanchard has joined #openstack-meeting-alt | 13:53 | |
| irenab | john: agree, but I think that input comes from the nova boot command | 13:53 |
| irenab | either in flavor or --nic | 13:54 |
| johnthetubaguy | right, so let me ramble on about how I see this working… I know its not ideal | 13:54 |
| johnthetubaguy | so, user makes request | 13:54 |
| *** llu-laptop has joined #openstack-meeting-alt | 13:54 | |
| johnthetubaguy | nova looks for required pci devices | 13:54 |
| johnthetubaguy | flavor extra specs or network_info might have them | 13:55 |
| irenab | john: missing scheduler | 13:55 |
| johnthetubaguy | we get a list of required alias | 13:55 |
| *** tianst has joined #openstack-meeting-alt | 13:55 | |
| johnthetubaguy | the scheduler can look at the required alias | 13:55 |
| johnthetubaguy | and filters out hosts that can't meet the requests for all the requested devices | 13:56 |
| johnthetubaguy | i.e. thats some scheduler filter kicking in | 13:56 |
| johnthetubaguy | when the requests gets to the compute node | 13:56 |
| johnthetubaguy | talks to resource manager to claim the resource as normal | 13:56 |
| *** hartsocks has joined #openstack-meeting-alt | 13:57 | |
| johnthetubaguy | compute node sends updates the the scheudler on what devices are available (we can sort out format later) | 13:57 |
| johnthetubaguy | when VM is setup... | 13:57 |
| johnthetubaguy | create domain | 13:57 |
| johnthetubaguy | add any requested devices in the flavor extra specs | 13:57 |
| johnthetubaguy | when plugging vifs | 13:57 |
| johnthetubaguy | vif driver gets extra PCI device info | 13:57 |
| johnthetubaguy | it also gets some lib that points back to nova driver specific ways of plugging PCI devices, and does what it wants to do | 13:58 |
| johnthetubaguy | maybe | 13:58 |
| johnthetubaguy | anyways, that was my general thinking | 13:58 |
| *** shanewang has joined #openstack-meeting-alt | 13:58 | |
| heyongli | john: currently pci works in this way, almost | 13:59 |
| irenab | john: I have to admit I do not see how networking part is resolved ... | 13:59 |
| baoli | Hi John, I think that's how it works today. But we need to resolve network connectivity issue as Irenab has pointed out. We need a PCI device that connects to a physical net | 13:59 |
| johnthetubaguy | well VIF driver gets its config from neutron in regular way | 13:59 |
| johnthetubaguy | combined with PCI alias info from nova | 14:00 |
| johnthetubaguy | it should be able to do what it needs to do | 14:00 |
| johnthetubaguy | at least thats my suggestion | 14:00 |
| heyongli | john: yep, this is also can reslove connectivity problem | 14:00 |
| *** dprince has joined #openstack-meeting-alt | 14:00 | |
| *** balajiiyer1 has joined #openstack-meeting-alt | 14:00 | |
| johnthetubaguy | anyways | 14:01 |
| *** dripton has joined #openstack-meeting-alt | 14:01 | |
| johnthetubaguy | its probably the nova meeting on here now | 14:01 |
| baoli | Time is up. Do you guys want to end the meeting soon? | 14:01 |
| *** PaulMurray has joined #openstack-meeting-alt | 14:01 | |
| irenab | john: PCI alias does not put any info regarding connectivity according to waht you defined previously | 14:01 |
| *** jdob has joined #openstack-meeting-alt | 14:01 | |
| heyongli | irenab: we can extend it | 14:01 |
| *** ndipanov has joined #openstack-meeting-alt | 14:01 | |
| johnthetubaguy | irenab: agreed, that has to come from neutron, in my model | 14:01 |
| shanewang | yes, nova meeting | 14:01 |
| johnthetubaguy | hyongli: its the nova meeting | 14:01 |
| irenab | it can be several mellanox NICs but only one conecting to the physicla network | 14:01 |
| *** gilliard has joined #openstack-meeting-alt | 14:01 | |
| baoli | #endmeeting | 14:01 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 14:01 | |
| openstack | Meeting ended Thu Jan 9 14:01:54 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:01 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-09-13.00.html | 14:01 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-09-13.00.txt | 14:01 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-09-13.00.log.html | 14:02 |
| russellb | #startmeeting nova | 14:02 |
| irenab | can we discuss on openstack-dev next steps for few mins? | 14:02 |
| openstack | Meeting started Thu Jan 9 14:02:27 2014 UTC and is due to finish in 60 minutes. The chair is russellb. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:02 |
| *** jtomasek_ has joined #openstack-meeting-alt | 14:02 | |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:02 |
| *** openstack changes topic to " (Meeting topic: nova)" | 14:02 | |
| openstack | The meeting name has been set to 'nova' | 14:02 |
| russellb | Hello everyone! | 14:02 |
| *** jtomasek has quit IRC | 14:02 | |
| *** garyk has joined #openstack-meeting-alt | 14:02 | |
| hartsocks | whee! | 14:02 |
| russellb | and welcome to the first 1400 UTC nova meeting | 14:02 |
| llu-laptop | ah, nova is here :) | 14:02 |
| johnthetubaguy | hi | 14:02 |
| dripton | hi | 14:02 |
| garyk | hi | 14:02 |
| PaulMurray | hi | 14:03 |
| russellb | #topic general | 14:03 |
| shanewang | hi | 14:03 |
| *** openstack changes topic to "general (Meeting topic: nova)" | 14:03 | |
| llu-laptop | hi | 14:03 |
| russellb | so, we're alternating meeting times for now | 14:03 |
| *** mriedem has joined #openstack-meeting-alt | 14:03 | |
| mriedem | hi | 14:03 |
| russellb | we'll see how it goes. as long as this is attended well, we'll keep it | 14:03 |
| shanewang | and meeting channel. | 14:03 |
| russellb | yeah and channel, oops | 14:03 |
| russellb | i'll update the wiki about that | 14:03 |
| russellb | some general things first ... | 14:03 |
| russellb | nova meetup next month | 14:04 |
| russellb | #link https://wiki.openstack.org/wiki/Nova/IcehouseCycleMeetup | 14:04 |
| russellb | be sure to sign up so we know you're coming | 14:04 |
| *** balajiiyer1 has quit IRC | 14:04 | |
| russellb | if you're able | 14:04 |
| * johnthetubaguy is looking forward to it | 14:04 | |
| russellb | my thinking on the schedule for that was to ... not really have a strict one | 14:04 |
| russellb | perhaps having unconference in the mornings, and open afternoons to just hack on things together | 14:04 |
| russellb | that could be working through tough bugs, design, whatever | 14:04 |
| johnthetubaguy | that sounds quite good | 14:05 |
| hartsocks | I like that. | 14:05 |
| *** noslzzp has joined #openstack-meeting-alt | 14:05 | |
| russellb | ok great | 14:05 |
| russellb | so we'll plan on that for now then | 14:05 |
| russellb | which isn't much of a plan | 14:05 |
| russellb | more of a plan to not plan too much | 14:05 |
| johnthetubaguy | in unconference u can gather friends for the afternoon I guess | 14:05 |
| russellb | sure | 14:05 |
| johnthetubaguy | maybe an etherpad to collect ideas? | 14:05 |
| russellb | that's be good | 14:05 |
| russellb | if anyone creates one before me, just link it from that wiki page | 14:05 |
| *** mspreitz has joined #openstack-meeting-alt | 14:05 | |
| mriedem | yeah, i could move my notes to etherpad | 14:05 |
| russellb | mriedem: perfect | 14:06 |
| garyk | how many people are expected? | 14:06 |
| russellb | i'll check | 14:06 |
| russellb | 20 registered so far | 14:07 |
| *** BrianB_ has quit IRC | 14:07 | |
| *** ndipanov has quit IRC | 14:07 | |
| mriedem | +1 hopefully soon | 14:07 |
| russellb | we have space for a lot more than that :) | 14:07 |
| russellb | should be fun | 14:07 |
| russellb | ok, another thing .... | 14:07 |
| russellb | please put january 20th on your schedule | 14:07 |
| russellb | gate bug fix day | 14:07 |
| garyk | thanks, and one last question: will there be any chance to connect from remote? | 14:07 |
| russellb | we really, really, really need to step it up on that front | 14:07 |
| russellb | garyk: maybe ... hadn't thought about it. we could try hangouts or something | 14:08 |
| shanewang | garyk:+1 | 14:08 |
| garyk | a hangout is a great idea | 14:08 |
| russellb | we can do that at least for the unconference part | 14:08 |
| russellb | the rest may not work well | 14:08 |
| johnthetubaguy | well, should be on IRC for the rest I guess | 14:08 |
| russellb | true | 14:08 |
| hartsocks | Is this Foo Camp (or Bar Camp) style unconference? | 14:08 |
| russellb | well ... | 14:09 |
| *** amotoki has quit IRC | 14:09 | |
| russellb | i don't know about doing pitches and voting | 14:09 |
| russellb | other than maybe on etherpad | 14:09 |
| hartsocks | okay. | 14:09 |
| russellb | i'm not sure we'll have *that* much demand for the time that we have to formally rank stuff | 14:09 |
| *** eankutse has joined #openstack-meeting-alt | 14:09 | |
| *** irenab has quit IRC | 14:09 | |
| russellb | just a guess though | 14:09 |
| russellb | i may just be a dictator on the schedule based on proposals | 14:09 |
| russellb | :-p | 14:09 |
| johnthetubaguy | +1 we give you a veto on a session | 14:10 |
| russellb | heh | 14:10 |
| russellb | ok onward | 14:10 |
| russellb | #topic sub-teams | 14:10 |
| *** openstack changes topic to "sub-teams (Meeting topic: nova)" | 14:10 | |
| llu-laptop | is Jan 20th appropriate for gate bug squash? is 23rd the icehouse-2? | 14:10 |
| russellb | anyone want to give a report on what a sub-group has been working on? | 14:10 |
| *** luqas has joined #openstack-meeting-alt | 14:10 | |
| russellb | llu-laptop: we'll come back to that in a bit | 14:10 |
| * johnthetubaguy raises hand a little | 14:10 | |
| russellb | johnthetubaguy: go for it | 14:11 |
| *** eankutse has quit IRC | 14:11 | |
| garyk | will you bring denis rodman as a side kick? | 14:11 |
| johnthetubaguy | So we are working on getting XenServer images into the node pool | 14:11 |
| *** heyongli has quit IRC | 14:11 | |
| johnthetubaguy | then getting Zuul testing stuff on XenServer | 14:11 |
| *** coolsvap has joined #openstack-meeting-alt | 14:11 | |
| russellb | johnthetubaguy: that's great to hear, good progress? | 14:11 |
| johnthetubaguy | slow progress, and infra-review welcome | 14:11 |
| johnthetubaguy | yeah, its really just not getting reviewed at the moment, but it was over christmas I guess | 14:12 |
| russellb | confident that it's still good icehouse timeframe material? | 14:12 |
| johnthetubaguy | matel is working on it | 14:12 |
| russellb | ok, yeah, holidays put a big delay on everything | 14:12 |
| russellb | nova queue is still recovering from holidays, too | 14:12 |
| johnthetubaguy | russellb: it should be / better be | 14:12 |
| *** ndipanov has joined #openstack-meeting-alt | 14:12 | |
| *** antigluk has joined #openstack-meeting-alt | 14:12 | |
| russellb | cool | 14:12 |
| johnthetubaguy | at least tempest is running well on XenServer | 14:12 |
| russellb | excellent | 14:13 |
| johnthetubaguy | Citrix did some good work on that | 14:13 |
| johnthetubaguy | so, its more a wire up into Zuul exercise | 14:13 |
| *** julim has joined #openstack-meeting-alt | 14:13 | |
| johnthetubaguy | and get an image in rackspace that has XenServer + Devstack domu | 14:13 |
| johnthetubaguy | which is done, just needs more testing, etc | 14:13 |
| russellb | i think that's a cool approach btw, hooking your nodes into infra | 14:13 |
| russellb | instead of running your own zuul/jenkins/etc | 14:14 |
| johnthetubaguy | yeah, fingers crossed | 14:14 |
| russellb | so, i saw you in a PCI discussion before this meeting :) | 14:14 |
| johnthetubaguy | yeah, thats true | 14:15 |
| russellb | what's going on with that | 14:15 |
| johnthetubaguy | I think we agreed on what the user requests could be | 14:15 |
| johnthetubaguy | waiting to here from ijw on confirming that though | 14:15 |
| johnthetubaguy | I wrote up some stuff here: | 14:15 |
| *** eankutse has joined #openstack-meeting-alt | 14:15 | |
| johnthetubaguy | https://wiki.openstack.org/wiki/Meetings/Passthrough#New_Proposal_for_admin_view | 14:15 |
| *** eankutse has quit IRC | 14:15 | |
| *** eankutse has joined #openstack-meeting-alt | 14:15 | |
| johnthetubaguy | The final interactions between Nova and Neutron are less clear to be honest | 14:15 |
| johnthetubaguy | basically we keep this: | 14:16 |
| johnthetubaguy | nova boot --image some_image --flavor flavor_that_has_big_GPU_attached some_name | 14:16 |
| johnthetubaguy | we add this: | 14:16 |
| garyk | are there people from neutron involved here? | 14:16 |
| johnthetubaguy | nova boot --flavor m1.large --image <image_id> --nic net-id=<net-id>,nic-type=<slow | fast | foobar> <vm-name> | 14:16 |
| johnthetubaguy | garyk: possible, but not enough I don't think | 14:16 |
| johnthetubaguy | (where slow is a virtual connection, fast is a PCI passthrough, and foobar is some other type of PCI passthrough) | 14:17 |
| garyk | i know that there are a lot of dicussion that the melanox, intel, cisco etc are having | 14:17 |
| johnthetubaguy | I kinda see it like nova volumes | 14:17 |
| shanewang | I believe cisco guys are from neutron? | 14:17 |
| johnthetubaguy | garyk: those are the folks I was talking | 14:17 |
| johnthetubaguy | just didn't see any non-vendor types | 14:17 |
| garyk | johnthetubaguy: thanks. | 14:17 |
| garyk | will the nic_type have a 'type of service' or be a set of k,v pairs? | 14:18 |
| johnthetubaguy | thats all TBC | 14:18 |
| garyk | ok, thanks | 14:18 |
| johnthetubaguy | just wanted to make sure the user didn't need to know about macvtap, or whatever it is | 14:18 |
| johnthetubaguy | I see it like the user requesting volume types | 14:18 |
| russellb | glad to see some stuff written down, and thanks a bunch for helping with this | 14:18 |
| garyk | maybe it is something worth looking into placing it in a flavor - for example someo gets gold service | 14:19 |
| johnthetubaguy | no worries, seems to be getting somewhere | 14:19 |
| garyk | they could have better connectivity, storage etc. | 14:19 |
| johnthetubaguy | we have some guys from bull.net working on adding PCI passthrough into XenAPI too | 14:19 |
| johnthetubaguy | the reaon I don't like flavor is due to this: | 14:19 |
| johnthetubaguy | nova boot --flavor m1.large --image <image_id> --nic net-id=<net-id-1> --nic net-id=<net-id-2>,nic-type=fast --nic net-id=<net-id-3>,nic-type=faster <vm-name> | 14:19 |
| garyk | that is, we introduce a notion of service levels | 14:19 |
| johnthetubaguy | yeah, I flip flop on this | 14:20 |
| johnthetubaguy | I like flavor being the main thing that gives you what you charge | 14:20 |
| *** tomblank has joined #openstack-meeting-alt | 14:20 | |
| johnthetubaguy | but you can dymanically pick how many nics you want anyways | 14:20 |
| johnthetubaguy | lets see how it works out anyways | 14:20 |
| johnthetubaguy | one question on all this... | 14:21 |
| russellb | ok, any other sub-team reports? | 14:21 |
| * russellb waits | 14:21 | |
| hartsocks | I have a short one. | 14:21 |
| johnthetubaguy | I wonder about moving PCI alias to host aggregates | 14:21 |
| johnthetubaguy | so its more dynamic, rather than in nova.conf | 14:21 |
| russellb | yeah, definitely prefer things to be API driven than config driven where we can | 14:21 |
| johnthetubaguy | OK, I was thinking the same, just wanted to check | 14:22 |
| russellb | sometimes config is a much easier first revision | 14:22 |
| russellb | and that's OK | 14:22 |
| garyk | it could be: nova boot --flavor m1.large … —service_type gold | 14:22 |
| garyk | then the scheduler could take this into account and assign a host that can provide that service | 14:22 |
| garyk | yeah, i can give a scjedulre update | 14:22 |
| garyk | scheduler update if n0nao is not around | 14:22 |
| garyk | johnthetubaguy: yeah, host aggregates could be a soln | 14:22 |
| russellb | but makes sense to move to an API later | 14:22 |
| johnthetubaguy | yeah, they have some stuff on config already | 14:22 |
| garyk | i am in favor of the api. | 14:23 |
| johnthetubaguy | I am kinda trying to just agree what the config should be yet, so thats not a big deal just yet :) | 14:23 |
| * russellb nods | 14:23 | |
| russellb | ok, hartsocks go for it | 14:23 |
| johnthetubaguy | cool, sorry | 14:23 |
| johnthetubaguy | I am all done... | 14:23 |
| russellb | all good :) | 14:23 |
| russellb | good stuff | 14:23 |
| *** SergeyLukjanov has joined #openstack-meeting-alt | 14:23 | |
| hartsocks | Just wanted to say we're looking to get a few bug fixes in for our driver. | 14:24 |
| hartsocks | Those affect the CI stability on Minesweeper. | 14:24 |
| hartsocks | I've spammed the ML about priority order on these. | 14:24 |
| hartsocks | Also | 14:24 |
| hartsocks | http://162.209.83.206/logs/58598/7/ | 14:24 |
| russellb | logs! | 14:25 |
| hartsocks | tada | 14:25 |
| hartsocks | http://162.209.83.206/logs/ | 14:25 |
| russellb | excellent | 14:25 |
| *** matty_dubs|gone is now known as matty_dubs | 14:25 | |
| garyk | There is a etherpad that has all of the vmware I2 issues - https://etherpad.openstack.org/p/vmware-subteam-icehouse-2 | 14:25 |
| hartsocks | We're not confident in the infra's stability yet to do the −1 votes. | 14:25 |
| hartsocks | garyk: thank you, I posted those in the ML post earlier too. | 14:26 |
| russellb | hartsocks: are you planning to move to testing all nova changes at some point? | 14:26 |
| hartsocks | When we can plug the session management issues... | 14:26 |
| russellb | ok, so eventually, that's fine | 14:26 |
| hartsocks | … and an inventory issue we have when adding ESX hosts. | 14:27 |
| johnthetubaguy | is it worth targeting those bugs at I-2, or did you do that already? | 14:27 |
| hartsocks | Eventually will be sooner if we can get more reviews? | 14:27 |
| russellb | heh | 14:27 |
| mriedem | the donkey and the carrot | 14:27 |
| russellb | like i said earlier, nova queue seems to be still recovering from the holidays | 14:27 |
| hartsocks | I'll double check all the listed bugs today. | 14:27 |
| hartsocks | :-) | 14:27 |
| hartsocks | I've said my bit. | 14:27 |
| garyk | minesweeper is doing the following: nova and neutron | 14:27 |
| garyk | here is a list - https://review.openstack.org/#/dashboard/9008 | 14:27 |
| russellb | you guys do seem to be high on these lists ... http://russellbryant.net/openstack-stats/nova-openreviews.html | 14:28 |
| russellb | ok, garyk did you have scheduler notes? | 14:28 |
| hartsocks | yeah, kind of aware of that. | 14:28 |
| garyk | russellb: yes | 14:29 |
| garyk | 1. the gantt tree for the forklift is ready but still are waiting to do development there | 14:29 |
| garyk | the goal will be to cherry pick changes | 14:29 |
| russellb | great | 14:30 |
| garyk | fir all those that are not aware gantt is the forklift of the scheduler nova code to a sperate tree | 14:30 |
| garyk | 2. we spoke yestertday to move the existing scheduler code to support objects (i am posting patches on this) so that the transition to an external scheduler may be easirer | 14:30 |
| russellb | so priorities: 1) keep in sync with nova, 2) get it running as a replacement for nova-scheduler, with n o new features | 14:30 |
| russellb | yeah that'd be nice | 14:31 |
| *** jecarey has quit IRC | 14:31 | |
| garyk | thats about it at the moment. | 14:32 |
| garyk | don dugger did great work with gantt and all the others in infra. kudos to them | 14:32 |
| johnthetubaguy | or use object support to test (1) keep in sync with nova? | 14:32 |
| *** vponomaryov has joined #openstack-meeting-alt | 14:32 | |
| garyk | yeah. hopefully. we still have instance groups in deveopment - pending API support and a few extra filters in the works | 14:32 |
| garyk | the idea of the object support is to remove the db access from the scheduler. this can hopefully leverage the objects that can work with deifferent versions | 14:32 |
| *** doug_shelley66 has joined #openstack-meeting-alt | 14:33 | |
| russellb | direct use of the db API at least? | 14:33 |
| garyk | at the moment the changes we are making is in nova. hopefully these few patches may be approved and then cherry picked | 14:33 |
| russellb | not using objects to talk to db through conductor right? | 14:33 |
| * russellb assumes so | 14:34 | |
| garyk | yes, to talk to the db via conductor. | 14:34 |
| russellb | well, we don't want gantt calling back to nova | 14:34 |
| russellb | so that won't work ... | 14:34 |
| shanewang | garyk: can you point me the patchset? | 14:34 |
| russellb | besides, i thought we were going with the no-db-scheduler blueprint for that | 14:34 |
| russellb | basically not using the db at all anymore | 14:35 |
| russellb | and just giving it a cache and sending it data to update the cache over time | 14:35 |
| shanewang | that is what boris-42 is doing. | 14:35 |
| russellb | right | 14:35 |
| russellb | ok, onward for now | 14:36 |
| russellb | #topic bugs | 14:36 |
| *** openstack changes topic to "bugs (Meeting topic: nova)" | 14:36 | |
| russellb | 193 new bugs | 14:36 |
| russellb | been staying roughly level lately | 14:36 |
| johnthetubaguy | do we have any cool stats of the bugs yet? | 14:37 |
| russellb | well, last month or so anyway | 14:37 |
| russellb | http://webnumbr.com/untouched-nova-bugs | 14:37 |
| garyk | why? can you please clarify | 14:37 |
| garyk | those patch sets for the 'no db' support have drivers where the one example is a sql alchemy one (unless i am misunderstanding) | 14:37 |
| garyk | that is for the host data. | 14:37 |
| garyk | there is the instance data that needs to be updated | 14:37 |
| ndipanov | russellb, so we are cool with those patches | 14:37 |
| ndipanov | russellb, oookay | 14:37 |
| russellb | not sure if my connection is messed up or what, i just caught a bunch of stuff from garyk and ndipanov ... sorry, wasn't trying to ignore you guys | 14:37 |
| johnthetubaguy | +1 | 14:38 |
| russellb | so, also on bugs, https://launchpad.net/nova/+milestone/icehouse-2 | 14:38 |
| russellb | lots of stuff targeted to icehouse-2 | 14:38 |
| russellb | the most concerning parts are all of the critical ones | 14:38 |
| russellb | we're the biggest gate failure offender right now | 14:38 |
| russellb | and pitchforks are coming out | 14:38 |
| russellb | so we really need to put time into this | 14:39 |
| *** markmcclain has quit IRC | 14:39 | |
| russellb | january 20 was proposed as a gate bug fix day by sdague | 14:39 |
| russellb | which is great, but we shouldn't wait until then | 14:39 |
| russellb | i'm trying to clear off my plate so i can start focusing on these bugs | 14:39 |
| russellb | anyone interested in working with me and others on these? | 14:40 |
| johnthetubaguy | I am traveling next week I am afraid :( | 14:40 |
| russellb | i'll allow it :) | 14:40 |
| russellb | well if anyone has some time available, please talk to me | 14:40 |
| russellb | i'm going to try to start organizing a team around these bugs | 14:40 |
| garyk | i am happy to work on bugs | 14:41 |
| russellb | these gate bugs are starting to *massively* impact the gate for everyone | 14:41 |
| russellb | gate queue got over 100 yesterday, approaching over 24 hours for patches to go through | 14:41 |
| russellb | because of so many resets | 14:41 |
| *** eharney has joined #openstack-meeting-alt | 14:41 | |
| russellb | 65 patches deep right now | 14:41 |
| russellb | #link http://lists.openstack.org/pipermail/openstack-dev/2014-January/023785.html | 14:42 |
| russellb | garyk: great, i'll be in touch | 14:42 |
| ndipanov | I'll look into some too next week I hope | 14:42 |
| garyk | regarding the bugs - i wanted us to try and formalize the VM diagnostics and then try and log this information when there is a gate failure - https://wiki.openstack.org/wiki/Nova_VM_Diagnostics | 14:43 |
| *** matty_dubs has left #openstack-meeting-alt | 14:43 | |
| *** GheRiver1 is now known as GheRivero | 14:43 | |
| mriedem | well, any tempest failure | 14:43 |
| garyk | that is, looking at VM diagnostics may help isolate the cause of issues - at least let us know if it was related to the VM, network ir storage | 14:43 |
| garyk | yeah, tempest failures | 14:43 |
| russellb | garyk: that's a good idea | 14:43 |
| russellb | the more data we can collect on failures the better, really | 14:43 |
| russellb | ok, next topic | 14:44 |
| mriedem | dansmith had some ideas on debugging the nova-network related large ops one yesterday | 14:44 |
| mriedem | we should talk to him today about that | 14:44 |
| russellb | mriedem: sounds good! | 14:44 |
| russellb | #topic blueprints | 14:45 |
| *** openstack changes topic to "blueprints (Meeting topic: nova)" | 14:45 | |
| russellb | #link https://launchpad.net/nova/+milestone/icehouse-2 | 14:45 |
| russellb | if you have a blueprint on that list, please make sure the status is accurate | 14:45 |
| russellb | or rather, "Delivery" | 14:45 |
| mriedem | instance type -> flavor will move to i3 | 14:45 |
| russellb | we're going to start deferring "Not Started" blueprints soon to icehouse-3 | 14:45 |
| russellb | mriedem: ok go ahead and bump it | 14:45 |
| mriedem | done | 14:46 |
| *** balajiiyer has joined #openstack-meeting-alt | 14:46 | |
| russellb | so another blueprint issue ... i've greatly appreciated the team effort on blueprint reviews, that has worked well | 14:46 |
| russellb | however, our idea for doing nova-core sponsors for blueprints has been a flop | 14:46 |
| russellb | nobody is doing it | 14:46 |
| russellb | and so virtually everything is Low | 14:46 |
| russellb | and that's not really much better than before | 14:46 |
| ndipanov | russellb, what if the status is inaccurate? | 14:46 |
| russellb | ndipanov: change it :-) | 14:46 |
| russellb | if it's yours you should be able to change it, if not, ask me (or someone on nova-drivers) | 14:47 |
| *** balajiiyer has quit IRC | 14:47 | |
| mriedem | it takes 2 cores to move from Low, i see some bps with 1 sponsor - maybe move to 1 sponsor? | 14:47 |
| ndipanov | russellb, done thanks | 14:47 |
| *** balajiiyer has joined #openstack-meeting-alt | 14:47 | |
| mriedem | 1 +2 doesn't get the patches merged though | 14:47 |
| russellb | right | 14:47 |
| russellb | that's why we were requiring 2 | 14:47 |
| johnthetubaguy | yeah, I think 2 is correct | 14:47 |
| *** hagarth has joined #openstack-meeting-alt | 14:48 | |
| johnthetubaguy | I sponsor the odd patch in the hope someone else joins me | 14:48 |
| russellb | we can either stick with this plan, and try to promote it better | 14:48 |
| russellb | or just punt the whole thing and start trying to sort them based on opinion | 14:48 |
| *** hagarth has left #openstack-meeting-alt | 14:48 | |
| russellb | johnthetubaguy: yeah, i think you and dansmith have done some of that, not many others | 14:48 |
| *** jecarey has joined #openstack-meeting-alt | 14:48 | |
| *** vbellur has joined #openstack-meeting-alt | 14:48 | |
| garyk | how can we get core people interested in blueprints? there are ~25 bp's that are waiting review and are all low. | 14:48 |
| johnthetubaguy | well, I think it reflects the current reality of the review rate though | 14:49 |
| garyk | so that means none are sponsored…. i just feel that a very small percentage of these may even get review cyces | 14:49 |
| russellb | johnthetubaguy: perhaps | 14:49 |
| *** xyang1 has joined #openstack-meeting-alt | 14:49 | |
| russellb | if the vast amount of Low is actually a reflection of our review bandwidth, then we have a whole different problem | 14:49 |
| russellb | i guess the question is ... how many Low blueprints land | 14:49 |
| johnthetubaguy | maybe worth a quick reminder email to nova-core? | 14:49 |
| russellb | here's the icehouse-1 list https://launchpad.net/nova/+milestone/icehouse-1 | 14:49 |
| russellb | johnthetubaguy: yeah, guess we can try that and see | 14:50 |
| russellb | because i still really like the theory behind it :) | 14:50 |
| *** NehaV has joined #openstack-meeting-alt | 14:50 | |
| russellb | better tooling could help too | 14:50 |
| russellb | if looking over these was a more natural part of dev workflow | 14:50 |
| russellb | but that's not a short term fix | 14:50 |
| johnthetubaguy | yeah, to tools could be a lot better, auto adding people to reviews, etc | 14:51 |
| mriedem | i wish the gd whiteboard textarea had timestamps | 14:51 |
| mriedem | and audited for who left the comment | 14:51 |
| russellb | yes the whiteboard sucks | 14:51 |
| garyk | i must be honest it is concerning. ~10 landed and some were just minor issues like configration options | 14:51 |
| johnthetubaguy | +1 | 14:51 |
| johnthetubaguy | +1 to the whiteboard | 14:51 |
| russellb | icehouse-1 isn't the best example ... icehouse-1 snuck up really fast | 14:51 |
| russellb | so it just happened to be what could land very fast | 14:51 |
| johnthetubaguy | true, it was short | 14:51 |
| mriedem | i1 was also summit time | 14:51 |
| johnthetubaguy | havana-2? | 14:51 |
| russellb | right | 14:51 |
| mriedem | h2 didn't have the new model | 14:52 |
| russellb | well havana wasn't using this approach, yeah | 14:52 |
| garyk | and i-2 had xmas and new years. i guess that also has a part. but we are a couple of weeks away and there is a meetup in the middle | 14:52 |
| russellb | that was prioritized based on my opinion largely :-) | 14:52 |
| johnthetubaguy | indeed, just curious on general throughput | 14:52 |
| *** jtomasek_ has quit IRC | 14:52 | |
| hartsocks | personally, my excuse is we had a baby. | 14:52 |
| hartsocks | :-) | 14:52 |
| russellb | hartsocks: heh, that'll be me for Juno | 14:52 |
| mriedem | hartsocks: plan 9 months ahead next time | 14:53 |
| russellb | life happens | 14:53 |
| *** banix has joined #openstack-meeting-alt | 14:53 | |
| hartsocks | mriedem: lol | 14:53 |
| mriedem | sorry honey.... | 14:53 |
| russellb | johnthetubaguy: unfortunately we can't see the h2 list now ... | 14:53 |
| russellb | johnthetubaguy: after the final release everything gets moved to the big havana list | 14:53 |
| johnthetubaguy | yeah, didn't work for me either, old reassignment thing | 14:53 |
| mriedem | i think to get eyes on blueprints, and sponsors, people need to show up to the meeting and bring them up | 14:53 |
| *** jtomasek has joined #openstack-meeting-alt | 14:54 | |
| russellb | heh | 14:54 |
| russellb | well on that note ... | 14:54 |
| mriedem | the new meeting time should help that | 14:54 |
| russellb | #topic open discussion | 14:54 |
| *** openstack changes topic to "open discussion (Meeting topic: nova)" | 14:54 | |
| russellb | open discussion is a good time to ask for eyes on things | 14:54 |
| mriedem | meetup etherpad: https://etherpad.openstack.org/p/nova-icehouse-mid-cycle-meetup-items | 14:54 |
| russellb | mriedem great, add it to the wiki? | 14:54 |
| mriedem | sounds like hyper-v CI is coming along: http://eavesdrop.openstack.org/meetings/hyper_v/2014/hyper_v.2014-01-07-16.01.log.html | 14:54 |
| mriedem | russellb: sure | 14:54 |
| garyk | If possible could people please comment on https://wiki.openstack.org/wiki/Nova_VM_Diagnostics | 14:54 |
| mriedem | i also posted to the ML | 14:54 |
| russellb | thanks | 14:54 |
| russellb | cool | 14:54 |
| mriedem | i'd like eyes on the 3 patches i have in this i2 bp that is moving to i3, these just need another +2: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/flavor-instance-type-dedup,n,z | 14:55 |
| mriedem | well, 2 patches, one is approved | 14:55 |
| mriedem | they are just refactor | 14:55 |
| russellb | wonder how many blueprints aren't approved yet ... *looks* | 14:55 |
| russellb | https://blueprints.launchpad.net/nova/icehouse | 14:55 |
| garyk | regarding the meetup - would it be possible that a day bew devoted to reviews of BP's? that is there will be a bunch of people together. Why not all get heads down and review BP's | 14:55 |
| russellb | not bad, 7 waiting on a blueprint reviewer | 14:56 |
| mriedem | garyk: i have bp review on the etherpad | 14:56 |
| garyk | not the proposed BP but the code | 14:56 |
| garyk | mriedem: thanks! | 14:56 |
| mriedem | russellb: also looking for approval on this https://blueprints.launchpad.net/nova/+spec/aggregate-api-policy | 14:56 |
| mriedem | code looks ready | 14:56 |
| russellb | ah, group code reviews, that could work | 14:56 |
| *** Barker has joined #openstack-meeting-alt | 14:56 | |
| russellb | mriedem: seems fine, approved | 14:57 |
| *** jcorbin has joined #openstack-meeting-alt | 14:57 | |
| mriedem | thanks | 14:57 |
| mriedem | anyone hear any status/progress on docker CI? | 14:57 |
| johnthetubaguy | maybe in utar we could get through the backlog a little? | 14:57 |
| *** rraja has joined #openstack-meeting-alt | 14:57 | |
| mriedem | since they are adding sub-driver for LXC | 14:57 |
| russellb | well, docker folks are not adding that | 14:58 |
| russellb | that's zul | 14:58 |
| *** achirko has joined #openstack-meeting-alt | 14:58 | |
| russellb | johnthetubaguy: yeah hope so, that'd be cool | 14:58 |
| russellb | re: docker CI, i've been in touch with them | 14:58 |
| russellb | they are fully aware of the requirement | 14:58 |
| russellb | and want to meet it, but haven't seen movement yet | 14:58 |
| *** aostapenko has joined #openstack-meeting-alt | 14:58 | |
| russellb | sounds like eric w. is taking over maintaining the docker driver in nova | 14:58 |
| russellb | don't see him here | 14:58 |
| mriedem | ok, i'm hoping to be pleasantly surprised with the hyper-v CI since it's been so quiet | 14:59 |
| *** gregsfortytwo1 has joined #openstack-meeting-alt | 14:59 | |
| russellb | yeah, but it was a nice surprise to see something get spun up | 14:59 |
| mriedem | yup | 14:59 |
| garyk | a change in neutron broke their ci - they are out there :) | 14:59 |
| russellb | nice to see this all seem to come together | 14:59 |
| *** bswartz has joined #openstack-meeting-alt | 14:59 | |
| russellb | oh right, i saw that email | 14:59 |
| russellb | darn windows | 15:00 |
| mriedem | garyk: yeah, i saw alex in -neutron the other day | 15:00 |
| mriedem | talking about it | 15:00 |
| *** scottda has joined #openstack-meeting-alt | 15:00 | |
| *** caitlin56 has joined #openstack-meeting-alt | 15:00 | |
| russellb | alright we're out of time | 15:00 |
| russellb | #openstack-nova is always open for nova chatter :) | 15:00 |
| russellb | thank you everyone! | 15:00 |
| *** akerr has joined #openstack-meeting-alt | 15:01 | |
| russellb | next week we'll be back to 2100 UTC | 15:01 |
| garyk | thanks for time! have a good weekend | 15:01 |
| russellb | and alternating from there | 15:01 |
| russellb | #endmeeting | 15:01 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:01 | |
| openstack | Meeting ended Thu Jan 9 15:01:13 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:01 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/nova/2014/nova.2014-01-09-14.02.html | 15:01 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/nova/2014/nova.2014-01-09-14.02.txt | 15:01 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/nova/2014/nova.2014-01-09-14.02.log.html | 15:01 |
| *** shanewang has quit IRC | 15:01 | |
| *** yportnova has joined #openstack-meeting-alt | 15:01 | |
| *** llu-laptop has left #openstack-meeting-alt | 15:01 | |
| *** mriedem has left #openstack-meeting-alt | 15:01 | |
| *** tianst has quit IRC | 15:01 | |
| bswartz | #startmeeting manila | 15:01 |
| openstack | Meeting started Thu Jan 9 15:01:54 2014 UTC and is due to finish in 60 minutes. The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:01 |
| *** openstack changes topic to " (Meeting topic: manila)" | 15:01 | |
| openstack | The meeting name has been set to 'manila' | 15:01 |
| *** yportnova__ has joined #openstack-meeting-alt | 15:02 | |
| bswartz | good morning/evening everyone | 15:02 |
| *** yportnova__ has quit IRC | 15:02 | |
| caitlin56 | morning | 15:02 |
| yportnova | hi | 15:02 |
| *** markmcclain has joined #openstack-meeting-alt | 15:02 | |
| vbellur | hello | 15:02 |
| achirko | hello | 15:02 |
| aostapenko | evening) | 15:02 |
| vponomaryov | hi | 15:02 |
| rraja | hi | 15:02 |
| csaba | hi | 15:02 |
| bswartz | I can't wait until DST starts up again so this meeting can be later in the day | 15:02 |
| scottda | hello, and nice to meet you | 15:02 |
| bswartz | scottda: welcome! | 15:02 |
| *** mspreitz has left #openstack-meeting-alt | 15:03 | |
| scottda | thanks | 15:03 |
| xyang1 | hi | 15:03 |
| bswartz | i hope everyone had an excellent holiday/new year | 15:03 |
| bswartz | since we cancelled the last 2 meetings, it's been a while since we met | 15:03 |
| vbellur | bswartz: thanks, hope you had a good one too | 15:04 |
| bswartz | I had really hoped to have my illustrations/diagrams of manila ready before this meeting but sadly they're still at the stage of being a giant mess on my whiteboard | 15:04 |
| *** betsy has joined #openstack-meeting-alt | 15:05 | |
| bswartz | so that's something I'm working on resolving later today | 15:05 |
| bswartz | caitlin56: I got your messages last week and I saw the diagram you drew up | 15:05 |
| bswartz | caitlin56: unforatunately I didn't understand it :-( | 15:05 |
| * caitlin56 volunteers to help with diagrams | 15:06 | |
| caitlin56 | Maybe we can go through it later in the day, or as on open topic. | 15:06 |
| *** amytron has quit IRC | 15:06 | |
| bswartz | anyways since the stuff I'm working on isn't ready yet, let's discuss the stuff that is actually going on | 15:06 |
| bswartz | caitlin56: I definitely want to discuss with you -- possibly later in this meeting if there is any interest/time | 15:06 |
| bswartz | #topic development status | 15:07 |
| *** openstack changes topic to "development status (Meeting topic: manila)" | 15:07 | |
| caitlin56 | bswartz: make sense, like you said dealing with already in progress development first makes sense. | 15:07 |
| *** SushilKM has joined #openstack-meeting-alt | 15:07 | |
| bswartz | yportnova: can you summarize the progress of the last few weeks for the team | 15:07 |
| vponomaryov | We have two updates: (1) about network-API and (2) generic multitenant lvm driver | 15:07 |
| yportnova | bswartz: sure | 15:07 |
| bswartz | vponomaryov: or you can provide the update too | 15:08 |
| *** SushilKM has left #openstack-meeting-alt | 15:08 | |
| vponomaryov | 1) https://blueprints.launchpad.net/manila/+spec/join-tenant-network: | 15:08 |
| vponomaryov | After testing realese candidate of network-API for manila, we found out, that it has lots of restrictions due to architecture of API. | 15:08 |
| vponomaryov | For example, security services used to be set depending on protocol (nfs/cifs), but should be based on security service itself (ad, ldap, kerberos). | 15:08 |
| vponomaryov | Also network-info entity used to have only one set of security service, but should be possible to set several, that will be used during share creation, when we choose protocol. | 15:08 |
| vponomaryov | So, all of this leads us to change network API. | 15:09 |
| vponomaryov | Security service entity prototype described here: | 15:09 |
| vponomaryov | https://docs.google.com/a/mirantis.com/document/d/1KIFlOvI_o_641JWIIDIXevuke9IKmun34s4z1VptGPY | 15:09 |
| vponomaryov | Then, we will remake network-info to have multiple security-service entities | 15:09 |
| vponomaryov | Estimation for this: this and all next weak + testing and bugfixing. | 15:09 |
| vponomaryov | After successfull implementation, Manila will have relatively stable API. | 15:09 |
| vponomaryov | 2) https://blueprints.launchpad.net/manila/+spec/generic-driver | 15:09 |
| vponomaryov | before incubation we need working multitenant generic driver, so this can be separated to 3 (three) parts: | 15:09 |
| vponomaryov | - cinder api (DONE) - https://review.openstack.org/#/c/65658/ | 15:09 |
| vponomaryov | - nova api (TODO: Fast to do basing on cinder api) | 15:09 |
| vponomaryov | - driver, that uses methods, which speaks with cinder and nova (TODO) | 15:09 |
| vbellur | when we get to an important change in implementation, like changing the API, can we start communicating on openstack-dev ML? | 15:10 |
| bswartz | vbellur: that's a good idea | 15:11 |
| *** bill_az has joined #openstack-meeting-alt | 15:11 | |
| bswartz | however I wouldn't want to update the ML until after the change has stabilized | 15:11 |
| caitlin56 | yponomaryov: how do you associate a share with a security service? | 15:11 |
| bswartz | caitlin56: you have to create the "network-info" first | 15:12 |
| vponomaryov | caitlin56: security-service -> network-info -> share | 15:12 |
| bswartz | caitlin56: and then you specify the ID of that when you create teh share | 15:12 |
| *** bill_az_ has joined #openstack-meeting-alt | 15:12 | |
| bswartz | every share must have a network-info associated with it, even if the network info implies wide-open/no-security | 15:12 |
| caitlin56 | So each share is part of a "network", each network has one security service? | 15:12 |
| vponomaryov | network info can have sec services, but not mandatory | 15:13 |
| vponomaryov | for neutron plugin, mandatory are net id and subnet id | 15:13 |
| caitlin56 | network_info has 0 or 1 security service? or 0..N security services? | 15:13 |
| vponomaryov | not 0_1, we plan do it 0_N | 15:14 |
| vponomaryov | as for security groups in nova | 15:14 |
| vponomaryov | s/not/now | 15:14 |
| caitlin56 | So then how do you know which security service to use? One per protocol? | 15:14 |
| vponomaryov | share creates with protocol | 15:14 |
| vponomaryov | for protocol purposes will be choosen sec service | 15:15 |
| *** bill_az has left #openstack-meeting-alt | 15:15 | |
| caitlin56 | So there is 0 or 1 security services for each network *and* protocol. right? | 15:15 |
| vponomaryov | for now, yes | 15:15 |
| jcorbin | Is there a work flow diagram for configuring a share from start to finish? | 15:16 |
| bswartz | okay so this is where some documentation and a working example would be helpful | 15:16 |
| bswartz | plus i'm not convinced that "network-info" is the best term to use for what these things are | 15:16 |
| *** sc68cal_ is now known as sc68cal | 15:17 | |
| *** sc68cal has joined #openstack-meeting-alt | 15:17 | |
| bill_az_ | diagram showing class relationships / cardinality would be helpful | 15:17 |
| bswartz | it's very hard to have an intelligent discussion about this stuff if we don't agree on terms | 15:17 |
| caitlin56 | bswartz: agreed, network-info sounds like the logical network (vlan or whatever). | 15:17 |
| caitlin56 | bill_az: ++ | 15:17 |
| jcorbin | bswartz: +1 | 15:18 |
| bswartz | for now, just understand that network-infos are things that exist in manila, and networks/subnets are things that exist in neutron | 15:18 |
| caitlin56 | And there can be multiple manila "networks" within a single neutron network, correct? | 15:18 |
| vponomaryov | we have choosen network-info, because we should choose some name | 15:18 |
| bswartz | manila can associate 0-N network-infos with each subnet in neutron | 15:18 |
| bswartz | and each share has exactly 1 network-info | 15:19 |
| vponomaryov | caitlin56: yes | 15:19 |
| caitlin56 | What you are enabling is the mappping of a corporate intranet that has one network but different windows domains (one for HR, one for Engineering, etc.) | 15:20 |
| bswartz | caitlin56: actually a VLAN corresponds to a neutron subnet | 15:20 |
| bswartz | we could in principle have several network-infos for a single VLAN or subnet | 15:20 |
| vponomaryov | yes, but it is not good in architecture view | 15:20 |
| bswartz | imagine 2 AD domains running on the same subnet | 15:20 |
| caitlin56 | Everyone in a manila-network uses the same security servcie to access shares (for a given protocol). | 15:21 |
| bswartz | caitlin56: I'm not sure that's true | 15:21 |
| bswartz | in my above example (2 AD domains) you could have 2 vservers on the same subnet for a single tenant -- 1 part of each AD domain | 15:22 |
| caitlin56 | bswartz: that's what I'm trying to nail down. What's the wildest configuration a customer can throw at me that I'll be expected to support. | 15:22 |
| bswartz | I ultimately expect that network-infos and vservers will correlate more or less 1-to-1 | 15:23 |
| *** rwsu has joined #openstack-meeting-alt | 15:23 | |
| caitlin56 | But aren't those 2 separate AD domains a "manila-network"? | 15:23 |
| bswartz | exceptions will exist in 2 cases that I can imagine: | 15:23 |
| bswartz | 1) if a vserver runs out of space and a second one is needed for capacity reasons | 15:23 |
| vponomaryov | caitlin56: it is manila-network with two security services | 15:24 |
| vponomaryov | in view of entities in manila | 15:24 |
| *** NehaV has quit IRC | 15:24 | |
| bswartz | 2) if vservers can be shared across 2 networks because the security settings for those 2 networks are "equivalent" insofar as the backend can tell | 15:24 |
| caitlin56 | yponomaryov: then wouldn't you have to specify the security service for each share? | 15:24 |
| *** tsufiev_ has quit IRC | 15:25 | |
| vponomaryov | caitlin56: ids of security services should be linked into netwrok-info entity | 15:25 |
| caitlin56 | That's what I presumed in advance, but you wanted to hang this off of the manila-network. | 15:25 |
| bswartz | caitlin56: I think you're using words that we don't have an agreed definition for | 15:25 |
| bswartz | what do you mean when you say manila-network? | 15:25 |
| caitlin56 | The set of file servers and clients that share common security. | 15:26 |
| caitlin56 | My assumption had been that this was not an object, that you specified the security service for each share. But you said that was not the case. So I'm trying to understand the rules. | 15:26 |
| *** IlyaE has joined #openstack-meeting-alt | 15:27 | |
| bswartz | the network-info is the object inside manila that contains all this info | 15:27 |
| bswartz | network-infos are actually rows in a table, each one has an ID and a bunch of metadata | 15:27 |
| bswartz | The API vponomaryov mentioned manages these new objects | 15:28 |
| caitlin56 | bswartz: so "network-info in manila context" probably should 'manila' as part of its name. Otherwise folks will get confused vs neutron defined networks. | 15:28 |
| *** hartsocks has left #openstack-meeting-alt | 15:28 | |
| bswartz | caitlin56: I agree the name is confusing | 15:28 |
| bswartz | caitlin56: my concern with the term "manila-network" is that I don't want to give people the impression that manila is managing networks (ala nova-network) | 15:29 |
| vponomaryov | bswartz: +1 | 15:29 |
| bswartz | we need a better name | 15:29 |
| vponomaryov | it should describe it as something with needed list of data | 15:29 |
| caitlin56 | Maybe manila-network-context? or manila-secfurity-domain? | 15:29 |
| bswartz | #topic better name for network-infos | 15:29 |
| *** openstack changes topic to "better name for network-infos (Meeting topic: manila)" | 15:30 | |
| *** SushilKM has joined #openstack-meeting-alt | 15:30 | |
| *** NehaV has joined #openstack-meeting-alt | 15:30 | |
| bswartz | anyone want to make some suggestions for a better term? | 15:30 |
| *** SushilKM has left #openstack-meeting-alt | 15:30 | |
| bswartz | just remember that these objects are each directly mapped to neutron subnets | 15:30 |
| vbellur | maybe network-context | 15:31 |
| achirko | secfurity-domain sounds good | 15:31 |
| vponomaryov | neutron is a plugin for this | 15:31 |
| vponomaryov | potentially, it can be something else | 15:31 |
| achirko | with --network argument to specify neutron parameters | 15:31 |
| jcorbin | Can a share only have one of these or multiple of these network-infos? | 15:32 |
| caitlin56 | yponomaryov: what is the name of the handle within maniala that selects neutron typically? | 15:32 |
| bswartz | jcorbin: every share has exactly 1 of these | 15:32 |
| vponomaryov | caitlin56: with config | 15:33 |
| caitlin56 | And this thing defines a *set* of servers, correct? It's not just your LDAP/AD, it is the associated DNS, etc. | 15:33 |
| vponomaryov | yes, "ip for dns" string present too | 15:34 |
| caitlin56 | yponomaryov: what is the configurable's name? That is the name we should use to refer to "neutron". | 15:34 |
| jcorbin | Does this thing define 'connectivity', what the share talks to? | 15:34 |
| *** kevinconway has joined #openstack-meeting-alt | 15:35 | |
| *** rnirmal has joined #openstack-meeting-alt | 15:35 | |
| *** jdob has quit IRC | 15:35 | |
| *** scottda_mobile has joined #openstack-meeting-alt | 15:36 | |
| *** gregsfortytwo1 has quit IRC | 15:36 | |
| *** dimasicv has joined #openstack-meeting-alt | 15:36 | |
| *** jdob has joined #openstack-meeting-alt | 15:36 | |
| yportnova | cailtlin56: "network_plugin" is the name of config option | 15:37 |
| *** amytron has joined #openstack-meeting-alt | 15:37 | |
| bswartz | jcorbin: yes | 15:37 |
| bswartz | the network-info object includes a mapping to a subnet (VLAN) which teh backend can use to provision an IP address if it needs to create a vserver to conenct to that VLAN | 15:37 |
| bswartz | network-context is sounding good to me | 15:37 |
| bswartz | secfurity-domain is the other suggestion I've heard | 15:37 |
| caitlin56 | jcorbin: I believe this thing defines the set of clients that can *successfully* talk to these servers. | 15:38 |
| caitlin56 | I could have a client that does not know what AD/LDAP server to talk to. It can connect to my vserver, but it will not be able to mount a share. | 15:38 |
| *** xuhanp has quit IRC | 15:38 | |
| bswartz | what about "network-security-context" | 15:38 |
| bswartz | or "manila-network-context"? | 15:38 |
| caitlin56 | network-context still sounds like something that belongs to neutron. | 15:38 |
| *** sadasu has quit IRC | 15:38 | |
| caitlin56 | Either of the last two are better. | 15:38 |
| bswartz | any other suggestions? | 15:39 |
| scottda | share-network-context? | 15:39 |
| bswartz | I'd like to call a vote on this | 15:39 |
| caitlin56 | scottda: +1 | 15:39 |
| vponomaryov | network-environment-data | 15:39 |
| bswartz | share-network-context sounds good | 15:39 |
| achirko | network-context and security-domain looks equally good to me | 15:40 |
| *** gregsfortytwo1 has joined #openstack-meeting-alt | 15:40 | |
| jcorbin | I think having the project name in the term is not a good idea. | 15:40 |
| jcorbin | share-network-context +1 | 15:40 |
| caitlin56 | The 'share' makes it clear that we are talking about something more specific than a VLAN. | 15:40 |
| vbellur | share-network-context +1 | 15:40 |
| xyang1 | +1 share-network-context | 15:40 |
| bswartz | share-network-context +1 | 15:41 |
| bswartz | any opposed to share-network-context? | 15:41 |
| bill_az_ | share-network-context +1 | 15:41 |
| vponomaryov | and we will have command like "manila share-network-context-create ..." ? Right? | 15:41 |
| achirko | share-network-context-security-service-add (command which we will support) looks terifying | 15:42 |
| yportnova | Maybe make it shorter like "share-network"? | 15:42 |
| achirko | maybe network-context? | 15:42 |
| bswartz | hmm | 15:42 |
| bswartz | achirko: I agree with caitlin56 that network-context sounds like it should belong to neutron | 15:42 |
| achirko | or security-domain? :) | 15:43 |
| bill_az_ | share-context - it is about more than just network | 15:43 |
| scottda | "share" makes it explicit that we are referring to share management | 15:43 |
| xyang1 | share-netcontext? | 15:43 |
| caitlin56 | It's not like any human will be typing these commands. Everything is going to be scripts. | 15:43 |
| bswartz | I prefer something with the name "share" or "manila" in the name | 15:43 |
| bswartz | I agree that a long name such as share-network-context is a bit painful to read/type | 15:43 |
| caitlin56 | If you are typing it a lot you will be putting it in a script anyway. | 15:44 |
| bswartz | caitlin56: not really -- us poor developers have to type this stuff, and the docs will have to include the full names | 15:44 |
| vbellur | share-nw-context ? | 15:44 |
| *** tomblank has quit IRC | 15:44 | |
| *** tomblank has joined #openstack-meeting-alt | 15:45 | |
| achirko | I don't think we should prepend 'share' - at the end everything in manila is about shares | 15:45 |
| caitlin56 | share-net-context? | 15:46 |
| caitlin56 | or share-net-ctx? | 15:46 |
| vponomaryov | net-ctx and we are deal =) | 15:46 |
| bswartz | share-netcontext seems to be the simplest shortening | 15:46 |
| bswartz | or share-network | 15:46 |
| bswartz | I don't like "nw" or "ctx" they're too short | 15:46 |
| *** alagalah has joined #openstack-meeting-alt | 15:47 | |
| bswartz | how do people feel about share-network-context vs share-network vs share-net-context | 15:47 |
| caitlin56 | achirko: I disagree. When you are writing code this is obvious, but an admin can easily be confused about whether they are being asked to configure manila's use of a neutron object or a manila object. | 15:47 |
| achirko | I like share-network | 15:47 |
| jcorbin | share-network +1 | 15:48 |
| bswartz | share-network +1 | 15:48 |
| vbellur | share-network +1 | 15:48 |
| scottda | share-network +1 | 15:48 |
| yportnova | share-network +1 | 15:48 |
| bswartz | okay that's a bit less terrifying, and still pretty clear what it refers to | 15:48 |
| vponomaryov | share-network +1 | 15:48 |
| caitlin56 | context is almost like "handle", so leaving it off is not terribly confusing. | 15:48 |
| *** dimasicv has quit IRC | 15:48 | |
| bswartz | #agreed network-info will be renamed to share-network | 15:49 |
| bswartz | #topic open-discussion | 15:49 |
| *** openstack changes topic to "open-discussion (Meeting topic: manila)" | 15:49 | |
| *** tomblank1 has joined #openstack-meeting-alt | 15:50 | |
| bswartz | okay so it's my fault that we still don't have clear diagrams/documents explaining what manila is/how it works | 15:50 |
| bswartz | I relaxed too much on vacation :-( | 15:50 |
| bswartz | I'm going to work on that today | 15:50 |
| caitlin56 | Do we want to start discussing object relationships? | 15:50 |
| bswartz | caitlin56: are you available later today? | 15:51 |
| *** PaulMurray has left #openstack-meeting-alt | 15:51 | |
| jcorbin | bwartz: If you need any help let me know. | 15:51 |
| bswartz | I guess I forgot to mention that in case it's no clear from vponomaryov's updates, we're really close to having a fully working implementation of manila with multitenancy | 15:51 |
| caitlin56 | Yes, I'm still at home, so I have to actually finish walking the dog and then go into the office first thought (it not yet 8:00 AM here). | 15:51 |
| *** pballand has joined #openstack-meeting-alt | 15:52 | |
| bswartz | caitlin56: I will ping you after the meeting ends | 15:52 |
| xyang1 | what about NetApp's multitenancy driver? | 15:52 |
| *** tomblank has quit IRC | 15:52 | |
| vponomaryov | xyang1: it is inprogress | 15:52 |
| xyang1 | ok, thanks | 15:52 |
| bswartz | xyang1: it's in gerrit, as a WIP | 15:53 |
| vponomaryov | we should make it work with kerberos and ldap and network-API | 15:53 |
| *** allyn has joined #openstack-meeting-alt | 15:53 | |
| bswartz | vponomaryov: is that change viewable by the public? | 15:53 |
| xyang1 | bswartz: ok, I'll take a look | 15:53 |
| vponomaryov | driver is in gerrit | 15:54 |
| bswartz | in any case I can add xyang1 | 15:54 |
| *** chandankumar_ has quit IRC | 15:54 | |
| *** jmontemayor has joined #openstack-meeting-alt | 15:55 | |
| *** scottda_mobile has quit IRC | 15:56 | |
| *** nam_nguyen has joined #openstack-meeting-alt | 15:56 | |
| bswartz | okay if nobody else has anything we can wrap up | 15:56 |
| bswartz | thanks everyone | 15:56 |
| bswartz | #endmeeting | 15:56 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:56 | |
| openstack | Meeting ended Thu Jan 9 15:56:20 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:56 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-01-09-15.01.html | 15:56 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-01-09-15.01.txt | 15:56 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-01-09-15.01.log.html | 15:56 |
| *** gregsfortytwo1 has left #openstack-meeting-alt | 15:56 | |
| *** jcorbin has left #openstack-meeting-alt | 15:56 | |
| vbellur | thanks | 15:56 |
| *** vbellur has left #openstack-meeting-alt | 15:56 | |
| *** achirko has quit IRC | 15:56 | |
| *** akerr has left #openstack-meeting-alt | 15:56 | |
| *** aostapenko has left #openstack-meeting-alt | 15:56 | |
| bswartz | uh oh | 15:57 |
| bswartz | #endmeeting | 15:57 |
| bswartz | whew | 15:57 |
| bswartz | laggy IRC | 15:57 |
| caitlin56 | bswartz: I should be available to chat on data structuring in about an hour and a half. | 15:57 |
| *** thinrichs has joined #openstack-meeting-alt | 15:57 | |
| caitlin56 | bswartz: or would you prefer after your lunch? | 15:58 |
| *** funzo has quit IRC | 15:59 | |
| *** markmcclain has quit IRC | 16:00 | |
| mestery | hi | 16:00 |
| banix | hi | 16:00 |
| thinrichs | Hi all | 16:00 |
| mestery | #startmeeting networking_policy | 16:00 |
| openstack | Meeting started Thu Jan 9 16:00:36 2014 UTC and is due to finish in 60 minutes. The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
| *** openstack changes topic to " (Meeting topic: networking_policy)" | 16:00 | |
| openstack | The meeting name has been set to 'networking_policy' | 16:00 |
| mestery | Hi banix thinrichs | 16:00 |
| *** michsmit has joined #openstack-meeting-alt | 16:00 | |
| mestery | #link https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy Agenda | 16:00 |
| *** bswartz has left #openstack-meeting-alt | 16:01 | |
| mestery | So, we have a light agenda for today I believe, which will leave lots of time for questions/comments at the end. :) | 16:01 |
| *** funzo has joined #openstack-meeting-alt | 16:01 | |
| mestery | #topic PoC Discussion and Planning | 16:01 |
| *** openstack changes topic to "PoC Discussion and Planning (Meeting topic: networking_policy)" | 16:01 | |
| mestery | So, banix and I had an AI to start writing this up, which we've done. | 16:01 |
| mestery | It's in very early stages, but covers the high level points banix s3wong and myself have been discussing this week. | 16:01 |
| *** prasadv has joined #openstack-meeting-alt | 16:02 | |
| mestery | #link https://docs.google.com/document/d/14UyvBkptmrxB9FsWEP8PEGv9kLqTQbsmlRxnqeF9Be8/edit?usp=sharing Group Policy PoC document | 16:02 |
| *** s3wong has joined #openstack-meeting-alt | 16:02 | |
| alagalah | Morning | 16:02 |
| mestery | s3wong: Hi! | 16:02 |
| s3wong | Hello | 16:02 |
| mestery | alagalah: Morning! | 16:02 |
| alagalah | mestery: hi | 16:02 |
| *** rraja has quit IRC | 16:02 | |
| mestery | So, for those who just joined, were discussing the PoC document now, which is in it's early stages. | 16:02 |
| mestery | https://docs.google.com/document/d/14UyvBkptmrxB9FsWEP8PEGv9kLqTQbsmlRxnqeF9Be8/edit?usp=sharing <--- Link to PoC document (also on Meeting page) | 16:02 |
| *** songole has joined #openstack-meeting-alt | 16:02 | |
| *** FlorianOtel has joined #openstack-meeting-alt | 16:03 | |
| *** vponomaryov has left #openstack-meeting-alt | 16:03 | |
| nam_nguyen | Hi, I'm new here and listening first. | 16:03 |
| *** ilyashakhat has joined #openstack-meeting-alt | 16:03 | |
| mestery | banix s3wong and myself will finish fleshing this out the rest of this week. | 16:03 |
| mestery | nam_nguyen: Welcome to the team! | 16:03 |
| banix | welkome Nam | 16:03 |
| *** caitlin56 has quit IRC | 16:03 | |
| songole | Hi all | 16:04 |
| banix | I should introduce Nam, as one of my colleagues who will be joint us | 16:04 |
| mestery | banix s3wong: Anything to add on PoC at this time? | 16:04 |
| banix | joining us that is | 16:04 |
| mestery | banix: Cool, glad to have more people joining the team! | 16:04 |
| alagalah | nam_nguyen: welcome | 16:04 |
| s3wong | name_nguyen: welcome to the team! | 16:04 |
| nam_nguyen | thx! | 16:04 |
| FlorianOtel | alagalah, mestery Hello boys | 16:04 |
| FlorianOtel | and all :) | 16:04 |
| mestery | FlorianOtel: Great to see you here my friend. :) | 16:04 |
| prasadv | hi this is prasad | 16:04 |
| banix | mestery: No, I think the main issue is how we go about starting the work | 16:04 |
| alagalah | prasadv: hi | 16:04 |
| mestery | banix: I agree. :) | 16:05 |
| FlorianOtel | is this on IRC only, or you guys on hangout / smth else as well ? | 16:05 |
| mestery | prasadv: Good morning! | 16:05 |
| mestery | FlorianOtel: IRC only, we're not as advanced as the ODL stuff. ;) | 16:05 |
| * mestery ducks. | 16:05 | |
| FlorianOtel | ha ;) | 16:05 |
| s3wong | mestery: the document captures in the high level what we need to do now | 16:06 |
| s3wong | though once this is done we would like to test it against a use case, such as three-tier app using Heat template | 16:06 |
| alagalah | Are we planning on assigning each of the 4 bullets out, do like a mini lead per bullet with teams? | 16:06 |
| mestery | s3wong: Lets add the use case to the document, sound good? | 16:07 |
| mestery | alagalah: We haven't decided on the division of labor yet, but if you want to help, that would be great! | 16:07 |
| banix | s3wong: we need to also think about what we need to do on the Heat side; I presume it will be minimal at least to start with | 16:07 |
| alagalah | mestery: yes I do | 16:07 |
| thinrichs | I'm not super familiar with ML2. I have a question or two about the plans. | 16:07 |
| prasadv | we internally built a heat template based on the discussions so far | 16:07 |
| mestery | thinrichs: Shoot! | 16:08 |
| mestery | prasadv: Awesome! We'll lean on you folks for that portion. Sound good banix? | 16:08 |
| s3wong | mestery: banix: sure | 16:08 |
| banix | prasadv: great; share when/if you can | 16:08 |
| thinrichs | For the allow/drop case, I see how we can implement the policy via OVS. But when we start getting to QOS, or some of the other actions, how will that work? | 16:08 |
| prasadv | ok will do. we can put it into poc document | 16:08 |
| banix | mestery: agree | 16:08 |
| thinrichs | Do we only select actions that are implementable in OVS? | 16:09 |
| s3wong | prasadv: wow, that is great! | 16:09 |
| mestery | thinrichs: For QoS in particular, we need to work with scal68 (Sean Collins) who is doing QoS support for ML2+OVS. | 16:09 |
| *** markmcclain has joined #openstack-meeting-alt | 16:10 | |
| alagalah | mestery: et al ... sorry , silly question but is OVS the initial use case with this to be extensible to other platforms later? Or limited? That will change the decisions | 16:10 |
| thinrichs | alagalah: maybe I'm wondering the same kind of thing. | 16:11 |
| banix | initial PoC | 16:11 |
| s3wong | alagalah: ovs is selected as initial PoC ref. impl. | 16:11 |
| mestery | Similar to how the existing Neutron APIs work in ML2, we'll want to make these new extension APIs work the same. | 16:11 |
| *** ashaikh has joined #openstack-meeting-alt | 16:11 | |
| alagalah | I think its ok to limit actions to OVS supported functions but to push features to rely on OVS would mean they would have to be written back in for other platforms | 16:11 |
| mestery | e.g. if you look, they have pre/post methods for both so DB transactions are done in one place. | 16:11 |
| banix | alagalah: thinrichs: Just a PoC; would like to see it used by others | 16:11 |
| alagalah | mestery: thanks, that helps... so it will be more extensible that way | 16:12 |
| *** tomblank has joined #openstack-meeting-alt | 16:12 | |
| *** hemanthravi has joined #openstack-meeting-alt | 16:12 | |
| thinrichs | What if we don't actually have OVS underneath the hood, and instead we are using something that doesn't support QOS? Is the policy just not enforceable? | 16:12 |
| s3wong | alagalah: yes - even the APIs and optional action types will be expanded in the future, I am sure | 16:13 |
| mestery | thinrichs: I think we decided that each MechanismDriver can fail the calls, similar to how it works today in ML2 for existing API calls. | 16:13 |
| alagalah | thinrichs: That was my understanding. Thanks mestery | 16:13 |
| banix | thinrichs: depends on the mechanism driver; can "not" support | 16:13 |
| alagalah | s3wong: thanks | 16:13 |
| thinrichs | And I'm not concerned so much about the PoC--it's that we're defining the language to have actions that are known to not be supported for some technology. | 16:14 |
| *** tomblank1 has quit IRC | 16:14 | |
| thinrichs | But I suppose that some underlying architectures can simply render some policies unenforceable and so the users ought to know not to write those policies. Is that right? | 16:14 |
| s3wong | thinrichs: ha - we talked about that. We will add an API for users to query a set of action capabilities that is supported by a particular plugin | 16:14 |
| *** jasonb365 has joined #openstack-meeting-alt | 16:14 | |
| alagalah | That was my understanding s3wong | 16:15 |
| * mestery nods in agreement. | 16:15 | |
| thinrichs | s3wong: but do we expect Heat to utilize that API before writing policy statements? | 16:15 |
| banix | thinrichs: for QoS we haven't really worked out specifics; can discuss in parallel | 16:15 |
| thinrichs | banix: the details of QoS aren't so important--it's just an example of something that isn't so easy to implement. | 16:15 |
| s3wong | thinrichs: interesting question - how dynamic can a Heat template be? | 16:15 |
| banix | I think we want the infrastructure setup first | 16:15 |
| prasadv | thinrichs: Heat can call and do validation of a template if there is such a call | 16:16 |
| *** markmcclain has quit IRC | 16:16 | |
| thinrichs | Would Heat change the templates it accepts based on whether or not Neutron accepts Qos policies? | 16:16 |
| s3wong | prasadv: Thank You! | 16:16 |
| prasadv | wherein the plugin cannot support | 16:16 |
| thinrichs | So before Heat (or whatever) even generates a UI to accept a template, it calls out to Neutron to figure out what policies it accepts and then customizes the UI so the user doesn't specify things that aren't implementable? | 16:17 |
| prasadv | thinrichs: Instead of changing templates, wouldnt it be better to return error | 16:17 |
| * alagalah nods | 16:18 | |
| banix | I think Heat as is today won't change things dynamically | 16:18 |
| prasadv | thinrichs:THat was original thought to have an query api | 16:18 |
| alagalah | I think the application should re-request | 16:18 |
| thinrichs | prasadv: But suppose the user spends a bunch of time writing a template, and then just gets an error in response? Wouldn't that irritate her? | 16:18 |
| alagalah | Send back an error | 16:18 |
| banix | There is talk of extending Heat to do a lot more but as is it simply tries to create resources specified in template through calls to underlying services | 16:18 |
| s3wong | thinrichs: the user should then consider having a different plugin | 16:19 |
| alagalah | Well we talked about an API to query capabilities, so they should use that to make a template and if a template comes in that cant be fulfilled, we should return error | 16:19 |
| thinrichs | s3wong: the user here doesn't get to change how the cloud is set up--they're just describing an app template. | 16:19 |
| mestery | s3wong: In the case of a public cloud, the user doesn't have control over the plugins. | 16:19 |
| *** tomblank has quit IRC | 16:19 | |
| prasadv | thinrichs: I think plugin can also document what it supports right? though this requires the person to know which plugin is being used. | 16:20 |
| s3wong | in that case, it is up to the cloud provider to publish what it can support | 16:20 |
| ashaikh | thinrichs: i don't think there is an expectation today that every template would just work -- e.g., the public cloud would make clear what it can/can't do | 16:20 |
| thinrichs | s3wong/ashaikh: but there must be UIs for creating templates, right? So suppose the UI tells you you've got 10 different actions you can use but in actuality, there is only allow/drop. | 16:21 |
| alagalah | thinrichs: Teh capability API should handle that shouldn't it ? | 16:21 |
| alagalah | A UI should use that shouldn't it ? Or am I missing something ? | 16:21 |
| mestery | thinrichs: Would it really be hard for the UI to query the plugin and ghost out which ones aren't supported by the underlying plugin? | 16:22 |
| thinrichs | Maybe I'm wondering whether the right interface for Heat is to just say "and give me a policy using actions 1,2,3,4". | 16:23 |
| s3wong | thinrichs: can you apply a Heat template in Horizon today? If so, if there is something within the Heat template that is not supported, would an error show up on Horizon? | 16:23 |
| mestery | thinrichs: Since there is no requirement to use cinder, for example, what if cinder isn't running and the user tries to create volumes in a Heat template? What happens in that case now? | 16:24 |
| mestery | Because there is no "official" definition of what OpenStack is. | 16:24 |
| songole | s3wong: it does. stack creation fails | 16:24 |
| thinrichs | I'm wondering if we would want to hide the details of the actions within higher-level concepts, and those concepts would be hard to define if the set of available actions were different for each plugin. | 16:24 |
| mestery | I think we're solving a problem which is not just related to policy actions IMHO. | 16:24 |
| mestery | OR rather, trying to solve. | 16:24 |
| banix | As prasadv shares with us what they have done on the Heat front, we can discuss further | 16:24 |
| *** IlyaE has quit IRC | 16:25 | |
| s3wong | songole: Thanks! so for thinrichs: it would just fails as you apply the template from get-go | 16:25 |
| thinrichs | Maybe this is all okay. I'll think more and see if anything pops to mind. | 16:25 |
| *** kebray_ has joined #openstack-meeting-alt | 16:25 | |
| mestery | thinrichs banix: Sounds good. | 16:25 |
| banix | mestery: agree. For now the Heat extension for us would be simply capable of creating newly defined Neutron objects | 16:25 |
| *** tomblank has joined #openstack-meeting-alt | 16:25 | |
| mestery | But good to bring these points up thinrichs! | 16:25 |
| prasadv | i agree with mestery. Policy is provding a query api and that help it quite a bit | 16:25 |
| * alagalah agrees with mestery | 16:25 | |
| *** garyk has quit IRC | 16:26 | |
| s3wong | prasadv: Good to have you here to give us actual API consumer to come up with the required APIs | 16:26 |
| mestery | OK, anything else related to the PoC to discuss right now? | 16:26 |
| mestery | Let me assign a few actions: | 16:26 |
| mestery | #action prasadv to add heat details to the PoC document | 16:26 |
| s3wong | mestery: so who is doing what? | 16:27 |
| mestery | #action mestery s3wong banix to flesh out more details in the document and assign tasks to interested parties | 16:27 |
| *** eankutse has quit IRC | 16:27 | |
| mestery | s3wong: Just added that. :) | 16:27 |
| s3wong | mestery: cool :-) | 16:27 |
| *** eankutse has joined #openstack-meeting-alt | 16:27 | |
| mestery | If nothing else on PoC, I'll move the topic to Open Discussion in a minute. | 16:27 |
| banix | Sounds good | 16:27 |
| s3wong | mestery: sure | 16:28 |
| mestery | #topic Open Discussion | 16:28 |
| *** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)" | 16:28 | |
| alagalah | Hi guys, just a nit, but a change was made to the taxonomy document to reflect "1 or more" when it accurately reflected that with a "+" as per the key | 16:28 |
| banix | I will cleanup the original design doc this week. | 16:28 |
| mestery | alagalah: Thanks for the update! | 16:28 |
| mestery | banix: Thank you! | 16:28 |
| alagalah | For classifiers | 16:29 |
| s3wong | alaglah: Thanks! | 16:29 |
| alagalah | Well actually..... | 16:29 |
| alagalah | The update made was wrong... it should be put back to a "+" | 16:29 |
| banix | Won't make any changes as such just a cleanup. | 16:29 |
| alagalah | Any objections to me changing it back? | 16:29 |
| prasadv | I still have an issue with classifiers for cases like L2 firewall not including IP addresses | 16:30 |
| *** sacharya has joined #openstack-meeting-alt | 16:31 | |
| mestery | prasadv: Dually noted, should we flesh that out during the PoC? | 16:31 |
| prasadv | mismith had issues with including them last time. How should we resolve that | 16:31 |
| alagalah | prasadv: Mine was more a cosmetic thing. the taxonom originally had + between policy rule and classifiers which means "1 or more" and it was changed to "1" to reflect "1 or more" | 16:31 |
| s3wong | prasadv: sure, that was never finalized | 16:31 |
| mestery | michsmit: You here? | 16:31 |
| michsmit | yes | 16:31 |
| *** jcoufal_ has quit IRC | 16:31 | |
| prasadv | i am fine with that. we can resolve during PoC | 16:31 |
| mestery | michsmit: Hi. See prasadv comment ^^^^ | 16:31 |
| mestery | michsmit prasadv: OK, cool. | 16:31 |
| michsmit | my assumption was that IP addresses would be limited to external networks | 16:31 |
| s3wong | alagalah: there should only be one classifier per policy-rule, so the '1' looks good | 16:32 |
| michsmit | meaning that policies between groups should avoid IP addresses if at all possible | 16:32 |
| alagalah | Oh! | 16:32 |
| alagalah | s3wong: Thanks! | 16:32 |
| alagalah | s3wong: Is it 0 or 1 ??? | 16:32 |
| alagalah | s3wong: In that case it should be a "?" as per the key | 16:33 |
| s3wong | alagalah: has to be 1, can't be 0 | 16:33 |
| banix | michsmith: agree | 16:33 |
| alagalah | In that case I apologize and I will leave it | 16:33 |
| alagalah | Thank you all for the clarification | 16:33 |
| s3wong | michsmith: agree - never a fan in adding IP address in classifier | 16:33 |
| prasadv | michsmit: I want to see if L2 scenario can be supported with you are saying and get back on that | 16:33 |
| mestery | prasadv: Sounds good! | 16:33 |
| michsmit | prasadv: sure | 16:33 |
| *** mozawa has quit IRC | 16:34 | |
| mestery | OK, anything else to discuss here? | 16:34 |
| *** hemanthravi has quit IRC | 16:34 | |
| s3wong | wow, short meeting :-) | 16:34 |
| mestery | Yay to short meetings! | 16:34 |
| michsmit | +1 to that | 16:34 |
| * alagalah cheers | 16:34 | |
| prasadv | +1 to that | 16:34 |
| banix | Thanks everyone | 16:35 |
| thinrichs | +1 | 16:35 |
| *** hemanthravi has joined #openstack-meeting-alt | 16:35 | |
| mestery | OK, thanks everyone! Looking forward to seeing some PoC action now! :) | 16:35 |
| s3wong | Thanks! | 16:35 |
| mestery | #endmeeting | 16:35 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:35 | |
| nam_nguyen | thx! | 16:35 |
| alagalah | Thanks all | 16:35 |
| openstack | Meeting ended Thu Jan 9 16:35:10 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:35 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-01-09-16.00.html | 16:35 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-01-09-16.00.txt | 16:35 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-01-09-16.00.log.html | 16:35 |
| *** prasadv has quit IRC | 16:35 | |
| *** alagalah has quit IRC | 16:35 | |
| *** songole has quit IRC | 16:35 | |
| *** thinrichs has quit IRC | 16:35 | |
| *** ashaikh has left #openstack-meeting-alt | 16:35 | |
| *** nam_nguyen has left #openstack-meeting-alt | 16:35 | |
| *** venkatesh has joined #openstack-meeting-alt | 16:35 | |
| *** hemanthravi has quit IRC | 16:36 | |
| *** venkatesh has quit IRC | 16:36 | |
| *** FlorianOtel has quit IRC | 16:36 | |
| *** csaba is now known as csaba|afk | 16:37 | |
| *** michsmit has left #openstack-meeting-alt | 16:37 | |
| *** allyn has quit IRC | 16:38 | |
| *** balajiiyer has quit IRC | 16:39 | |
| *** mozawa has joined #openstack-meeting-alt | 16:39 | |
| *** s3wong has quit IRC | 16:40 | |
| *** aignatov has quit IRC | 16:51 | |
| *** pballand has quit IRC | 16:53 | |
| *** hartsocks has joined #openstack-meeting-alt | 17:00 | |
| *** derekh has quit IRC | 17:02 | |
| *** gokrokve has joined #openstack-meeting-alt | 17:03 | |
| *** jasonb365 has quit IRC | 17:03 | |
| *** jtomasek has quit IRC | 17:03 | |
| *** garyk has joined #openstack-meeting-alt | 17:03 | |
| *** NikitaKonovalov has quit IRC | 17:04 | |
| *** BrianB_ has joined #openstack-meeting-alt | 17:09 | |
| *** balajiiyer has joined #openstack-meeting-alt | 17:11 | |
| *** jasonb365 has joined #openstack-meeting-alt | 17:12 | |
| *** tomblank has quit IRC | 17:12 | |
| *** pballand has joined #openstack-meeting-alt | 17:13 | |
| *** eankutse has quit IRC | 17:21 | |
| *** markmcclain has joined #openstack-meeting-alt | 17:21 | |
| *** glucas has left #openstack-meeting-alt | 17:24 | |
| *** arnaud__ has joined #openstack-meeting-alt | 17:25 | |
| *** arnaud has joined #openstack-meeting-alt | 17:25 | |
| *** bdpayne has joined #openstack-meeting-alt | 17:25 | |
| *** ruhe is now known as _ruhe | 17:27 | |
| *** ilyashakhat has quit IRC | 17:36 | |
| *** NikitaKonovalov has joined #openstack-meeting-alt | 17:37 | |
| *** nati_ueno has joined #openstack-meeting-alt | 17:42 | |
| *** ViswaV has joined #openstack-meeting-alt | 17:43 | |
| *** ViswaV has left #openstack-meeting-alt | 17:46 | |
| *** gokrokve has quit IRC | 17:49 | |
| *** paulmo has joined #openstack-meeting-alt | 17:49 | |
| *** safchain has quit IRC | 17:49 | |
| *** balajiiyer has quit IRC | 17:50 | |
| *** BrianB_ has quit IRC | 17:51 | |
| *** eankutse has joined #openstack-meeting-alt | 17:51 | |
| *** luqas has quit IRC | 17:54 | |
| SergeyLukjanov | savanna team meeting will be here in 10 minutes | 17:55 |
| *** mattf has joined #openstack-meeting-alt | 17:55 | |
| *** bob_nettleton has joined #openstack-meeting-alt | 17:56 | |
| *** NikitaKonovalov has quit IRC | 17:56 | |
| *** ViswaV has joined #openstack-meeting-alt | 17:57 | |
| *** dmitryme has joined #openstack-meeting-alt | 17:58 | |
| *** eankutse has quit IRC | 18:00 | |
| *** crobertsrh has joined #openstack-meeting-alt | 18:00 | |
| *** alazarev has joined #openstack-meeting-alt | 18:00 | |
| *** gokrokve has joined #openstack-meeting-alt | 18:01 | |
| *** NikitaKonovalov has joined #openstack-meeting-alt | 18:01 | |
| *** gokrokve has quit IRC | 18:03 | |
| *** lblanchard has quit IRC | 18:03 | |
| *** baoli has quit IRC | 18:04 | |
| *** jasonb365 has quit IRC | 18:05 | |
| *** aignatov has joined #openstack-meeting-alt | 18:05 | |
| *** jmaron has joined #openstack-meeting-alt | 18:05 | |
| *** harlowja_away is now known as harlowja | 18:07 | |
| *** jspeidel has joined #openstack-meeting-alt | 18:08 | |
| *** Duane has joined #openstack-meeting-alt | 18:08 | |
| SergeyLukjanov | savanna folks, are you here? | 18:09 |
| dmitryme | yep | 18:09 |
| aignatov | o/ | 18:09 |
| jspeidel | yes | 18:09 |
| crobertsrh | yessir | 18:09 |
| alazarev | o/ | 18:09 |
| SergeyLukjanov | #startmeeting savanna | 18:10 |
| openstack | Meeting started Thu Jan 9 18:10:37 2014 UTC and is due to finish in 60 minutes. The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:10 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:10 |
| *** openstack changes topic to " (Meeting topic: savanna)" | 18:10 | |
| openstack | The meeting name has been set to 'savanna' | 18:10 |
| jmaron | yep | 18:10 |
| SergeyLukjanov | openstack, thank you sir | 18:10 |
| SergeyLukjanov | #topic Agenda | 18:10 |
| *** openstack changes topic to "Agenda (Meeting topic: savanna)" | 18:10 | |
| SergeyLukjanov | #link https://wiki.openstack.org/wiki/Meetings/SavannaAgenda | 18:10 |
| SergeyLukjanov | #topic Action items from the last meeting | 18:11 |
| *** openstack changes topic to "Action items from the last meeting (Meeting topic: savanna)" | 18:11 | |
| SergeyLukjanov | roadmap improvements are still in my backlog | 18:11 |
| SergeyLukjanov | heh | 18:11 |
| SergeyLukjanov | #action SergeyLukjanov to check that all blueprints created and ping guys to make them if not | 18:11 |
| SergeyLukjanov | #action SergeyLukjanov add links to the blueprints to roadmap | 18:12 |
| SergeyLukjanov | #topic News / updates | 18:12 |
| *** openstack changes topic to "News / updates (Meeting topic: savanna)" | 18:12 | |
| SergeyLukjanov | guys, please | 18:12 |
| SergeyLukjanov | I'm still in vacation, so, not so many news from my side | 18:12 |
| aignatov | nothing specific from me, just reviewed some code today and continue working on adding anti affinity to scaling with heat | 18:12 |
| crobertsrh | I'm currently working on putting the "Java" job type into the dashboard (based on tmckay's Oozie Java action work). | 18:13 |
| aignatov | the first day after holidays :) | 18:13 |
| jspeidel | any update regarding HBASE support? | 18:13 |
| mattf | i've been chipping away at the savanna cli. comments still welcome on https://blueprints.launchpad.net/python-savannaclient/+spec/python-savannaclient-cli - especially around how to handle template creation. | 18:13 |
| alazarev | I've finished IDH plugin initial version: https://review.openstack.org/#/c/56105/ | 18:13 |
| SergeyLukjanov | jspeidel, not yet, I was on holidays/vacation, we'll continue at Monday | 18:13 |
| jspeidel | @SergeyLukjanov ok, thanks | 18:14 |
| SergeyLukjanov | jspeidel, and it's still -1'ed | 18:14 |
| alazarev | jspeidel: as I see IDH waits for your review :) | 18:14 |
| jspeidel | yep, I know :) | 18:14 |
| aignatov | yeh, I see that this patch is WIP | 18:14 |
| * mattf jumps on jspeidel too | 18:14 | |
| * mattf smiles | 18:14 | |
| *** tomblank has joined #openstack-meeting-alt | 18:14 | |
| SergeyLukjanov | any other updates? | 18:15 |
| aignatov | alazarev: patch lgtm to be merged ;) | 18:15 |
| jmaron | edp over neutron private nets is paused while I wait on our neutron setup to resurrect from the dead so I can perform functional testing | 18:15 |
| alazarev | also, I was able to run Pig job via EDP on IDH cluster (https://review.openstack.org/#/c/64323/) | 18:15 |
| mattf | jmaron, neutron issues? | 18:15 |
| mattf | alazarev, awesome | 18:15 |
| jmaron | IT/host issues | 18:15 |
| *** johnthetubaguy has quit IRC | 18:15 | |
| SergeyLukjanov | also I'd like to mention Spark plugin efforts in ML | 18:15 |
| *** paulmo has left #openstack-meeting-alt | 18:16 | |
| SergeyLukjanov | let me find the link | 18:16 |
| jspeidel | @mattf #link https://review.openstack.org/#/c/56105/ | 18:16 |
| mattf | https://blueprints.launchpad.net/savanna/+spec/spark-plugin | 18:16 |
| *** mat-lowery has joined #openstack-meeting-alt | 18:16 | |
| aignatov | #link https://blueprints.launchpad.net/savanna/+spec/spark-plugin | 18:16 |
| SergeyLukjanov | #link http://lists.openstack.org/pipermail/openstack-dev/2014-January/thread.html#23806 | 18:16 |
| aignatov | corrected you mattf :P | 18:16 |
| mattf | aignatov, not the first, won't be the last! | 18:17 |
| SergeyLukjanov | #topic Roadmap update/cleanup | 18:17 |
| *** openstack changes topic to "Roadmap update/cleanup (Meeting topic: savanna)" | 18:17 | |
| SergeyLukjanov | action items are on me | 18:17 |
| SergeyLukjanov | I don't think that we have any updates to roadmap so far | 18:17 |
| aignatov | SergeyLukjanov: these is awesome news, one more plugin, i'm impressed | 18:17 |
| mattf | should we scan the roadmap and give feedback? i've not looked at it since summit. | 18:18 |
| SergeyLukjanov | mattf, I'm afraid that nothing changed | 18:18 |
| *** tmckay has joined #openstack-meeting-alt | 18:18 | |
| SergeyLukjanov | mattf, but it should, I still hope to return back to it and ensure blueprints existence | 18:18 |
| mattf | ack | 18:19 |
| SergeyLukjanov | #topic General discussion | 18:19 |
| *** openstack changes topic to "General discussion (Meeting topic: savanna)" | 18:19 | |
| SergeyLukjanov | #info the icehouse-2 release will be Jan 24 | 18:19 |
| mattf | anyone have suggestions on how to create node group / cluster templates from the cli? | 18:19 |
| SergeyLukjanov | so, be prepared for the code freeze Jan 22 | 18:19 |
| alazarev | mattf: request json? :) | 18:20 |
| mattf | SergeyLukjanov, i'll do another oslo sync for next week, please add an action for me (remind me to do it next thurs) | 18:20 |
| *** balajiiyer has joined #openstack-meeting-alt | 18:20 | |
| aignatov | mattf, not atm, the first thing is yes -json | 18:20 |
| SergeyLukjanov | mattf, you can find some of my thoughts in the CLI blueprint | 18:20 |
| jmaron | savanna template-create < template.json ? | 18:20 |
| mattf | alazarev, i was thinking about that actually. maybe creating only by piping in a json file? | 18:20 |
| jspeidel | alazarev +1 for json request bodhy | 18:20 |
| jspeidel | body | 18:20 |
| aignatov | jmaron: smthg like this | 18:20 |
| mattf | afaict, it's complicated by the fact that template json is plugin specific | 18:21 |
| aignatov | mattf: you can get an idea from heat ;) | 18:21 |
| SergeyLukjanov | #action mattf to sync oslo right before the i2 code freeze | 18:21 |
| mattf | for instance, process names aren't consistent between plugins | 18:21 |
| mattf | and hdp supports more processes than vanilla | 18:22 |
| SergeyLukjanov | I'm ok with piping json template for the first time at least | 18:22 |
| alazarev | mattf: and they will not be consistent because different distros have different namings | 18:22 |
| mattf | i've an action on myself to work out the best way to list processes to help in contructing json, but...that's not very userfiendly | 18:22 |
| SergeyLukjanov | #action SergeyLukjanov to unsure that we'rein sync with global requirements | 18:22 |
| jmaron | there's a precedent for plugin specific template processing in the plugin SPI | 18:22 |
| SergeyLukjanov | #undo | 18:22 |
| openstack | Removing item from minutes: <ircmeeting.items.Action object at 0x30f5350> | 18:22 |
| mattf | alazarev, we could have some consistency tho, NameNode vs NAMENODE etc | 18:22 |
| SergeyLukjanov | #action SergeyLukjanov to ensure that we're in sync with global requirements | 18:23 |
| mattf | (someone needs to fix #undo to print the object string0 | 18:23 |
| mattf | not it | 18:23 |
| SergeyLukjanov | mattf, alazarev, that's a problem of choosing vendor names vs. our common names | 18:23 |
| mattf | seems plugins could maintain a simple map from common name to vendor name | 18:24 |
| jspeidel | mattf, I don't think that we can expect consistency across providers. Each provider should expose names that are meaningful for their stack | 18:24 |
| mattf | set of common names would have to be union of all vendor features tho | 18:24 |
| aignatov | jspeidel: +1 | 18:24 |
| *** yogesh has joined #openstack-meeting-alt | 18:24 | |
| *** lblanchard has joined #openstack-meeting-alt | 18:25 | |
| jmaron | vendor CLI plugins for template processing (akin to SPI)? | 18:25 |
| alazarev | some services could be splited into severel processes, some services are specific for distro, I don't think we need to force namings | 18:25 |
| mattf | jspeidel, so far the examples are somewhat silly tho, the primary difference is all caps for HDP | 18:25 |
| alazarev | mattf: this is because we have only HDP and vanilla | 18:25 |
| jmaron | vanilla: "oozie" HDP: OOZiE_SERVER, OOZIE_CLIENT | 18:25 |
| mattf | so the proposal (well liked) is currently to simple accept json files. that means to actually create a template the user must essentially use horizon and then export it. | 18:26 |
| jspeidel | mattf, agreed that the current differences are simple, but I think that assuming a consistency is a slippery slope | 18:26 |
| mattf | jmaron, thanks for finding a nice example. in this case it seems like the vanilla is simply being less specific | 18:26 |
| alazarev | if we have vanilla, HDP, IDH, cloudera, etc - there will be much more differences | 18:27 |
| jmaron | (to point out less trivial differences) | 18:27 |
| aignatov | don't forget about incoming Spark plugin, I think there will be another set of processes :) | 18:27 |
| mattf | my view on this is we should make using savanna simple and consistent for users, no matter what plugin they are using on the backend | 18:27 |
| mattf | ^^ my guiding rule, which eventually has exceptions | 18:27 |
| *** jasonb365 has joined #openstack-meeting-alt | 18:28 | |
| mattf | aignatov, yeah, set would have to be union of all plugins | 18:28 |
| jspeidel | mattf, agree with usability but don't think the we can dictate to providers what to call components | 18:28 |
| jspeidel | mattf, each plugins users know the names of the components associated with the vendors stack | 18:28 |
| mattf | jspeidel, the vendor would not have to call them something internally, only when representing them out to savanna | 18:28 |
| jmaron | we could follow this already established precedent/convention: https://savanna.readthedocs.org/en/latest/devref/plugin.spi.html#convert-config-plugin-name-version-template-name-cluster-template-create | 18:29 |
| *** ViswaV has quit IRC | 18:30 | |
| mattf | imho, no need to make a decision here. seems to me the pressure is for no change to how the plugins work at the moment. i want to make sure folks are aware of the differences and that they can impact usability. | 18:30 |
| mattf | (they're impacting usability in how i can make the cli already!) | 18:30 |
| jspeidel | mattf, agreed | 18:30 |
| alazarev | mattf: +1 | 18:30 |
| *** xyang1 has quit IRC | 18:31 | |
| * mattf gets off soapbox | 18:31 | |
| *** ViswaV has joined #openstack-meeting-alt | 18:31 | |
| mattf | another related topic - destroy or delete - what's the proper verb for our cli? | 18:32 |
| *** ViswaV has quit IRC | 18:32 | |
| mattf | imho we should just be consistent w/ other clis | 18:32 |
| *** ViswaV has joined #openstack-meeting-alt | 18:32 | |
| jmaron | annihilate | 18:32 |
| mattf | e.g. cluster-destroy or cluster-delete, node-group-template-destroy or node-group-template-delete | 18:32 |
| mattf | obliterate? | 18:32 |
| aignatov | jmaron: lol! | 18:32 |
| *** ViswaV has quit IRC | 18:32 | |
| aignatov | mattf, +1 to be consistent with other clis | 18:33 |
| alazarev | I vote on delete | 18:33 |
| *** ViswaV has joined #openstack-meeting-alt | 18:33 | |
| mattf | aignatov, clis aren't consistent, how would you rank them (nova then keystone then cinder?) | 18:33 |
| aignatov | cluster-delete and node-group-template-delete my vote | 18:33 |
| jmaron | +1 for delete | 18:34 |
| jspeidel | mattf, +1 for delete | 18:34 |
| * mattf starts to see himself s/destroy/delete/g'ing | 18:34 | |
| jspeidel | mattf, should have asked sooner ;) | 18:34 |
| jmaron | s/destroy/euthanize/g | 18:34 |
| * mattf hangs head in shame | 18:34 | |
| mattf | jmaron, you're on fire | 18:34 |
| jmaron | :) | 18:35 |
| mattf | ok, i'll tend to delete and do another pass over other clis | 18:35 |
| tmckay | just checked the REST apis, looks like it is all "delete" there too | 18:35 |
| aignatov | mattf, yep, rely on nova first, imo | 18:35 |
| tmckay | +1 delete | 18:35 |
| mattf | tmckay, delete is the REST verb | 18:35 |
| SergeyLukjanov | I'm ok with both destoy and delete ;) | 18:35 |
| mattf | ok, thanks for the input folks! | 18:36 |
| tmckay | well, true. I was looking at method names. Doubly consistent :) | 18:36 |
| jmaron | SergeyLukjanov: node-template-destroy-and-delete? | 18:36 |
| mattf | fyi - i'm finding all sorts of rough edges in the client, so i'll start writing them up for client v2 | 18:36 |
| mattf | (kinda glad i'm finding rough edges, one reason for doing the cli was to evaluate the usability of the api!) | 18:37 |
| alazarev | destroy-delete-and-remove-completely | 18:37 |
| * mattf hopes someone brings up another topic before we get to exterminate | 18:37 | |
| aignatov | destroy-delete-and-remove-completely-and-run-away | 18:37 |
| * mattf waits for Aliens reference | 18:38 | |
| alazarev | during IDH plugin development I faced with problem that auth token is expired because of long inactivity. Auth token was only needed to take username from image tags. So, I proposed caching for username in node group.extra (https://review.openstack.org/#/c/65402/). | 18:38 |
| alazarev | SergeyLukjanov: you left a comment that this need to be discussed | 18:38 |
| jmaron | *get away from my template you b****!* | 18:38 |
| mattf | jmaron, lol, i was thinking nuke from orbit | 18:38 |
| jmaron | :) | 18:39 |
| mattf | jspeidel, what on earth do you guys have in your break rooms!? | 18:39 |
| aignatov | xD | 18:39 |
| SergeyLukjanov | jmaron, heh, that's a good option :) | 18:39 |
| SergeyLukjanov | alazarev, my concern is extra field ressurection | 18:39 |
| alazarev | SergeyLukjanov: what wrong with it? extra is good | 18:40 |
| mattf | alazarev, SergeyLukjanov, aignatov, does this become a non-issue w/ heat? | 18:40 |
| SergeyLukjanov | alazarev, it's a kind of necrophilia | 18:41 |
| SergeyLukjanov | mattf, extra field? | 18:41 |
| * mattf covers eyes | 18:41 | |
| mattf | SergeyLukjanov, need storing username on image | 18:41 |
| mattf | need for* | 18:41 |
| alazarev | mattf: yes, heat removes the issue, but it would be good to get plugin work before full switch to heat | 18:41 |
| dmitryme | mattf, indeed it is not an issue with the heat | 18:41 |
| mattf | alazarev, how long is "long inactivity"? | 18:41 |
| aignatov | SergeyLukjanov: do you know that we already use extra for hadoop keypairs? | 18:42 |
| mattf | and who's inactivity? | 18:42 |
| mattf | whose* | 18:42 |
| dmitryme | for those who don't know: all instances provisioned by Heat have ec2-user | 18:42 |
| dmitryme | i.e. static username for all images | 18:42 |
| alazarev | mattf: 30+ mins, savanna waits for manager to install something | 18:42 |
| mattf | dmitryme, we could change that via userdata, right? | 18:42 |
| mattf | alazarev, that's not very long imho | 18:42 |
| dmitryme | mattf: change what? :-) | 18:42 |
| mattf | not very long -> up priority | 18:42 |
| mattf | dmitryme, os-user vs ec2-user. it's just ec2-user beacuse that's the cloud-init default? | 18:43 |
| alazarev | mattf: I didn't dig why token expires, but it did | 18:43 |
| SergeyLukjanov | aignatov, yup, I remember | 18:43 |
| dmitryme | mattf: it is Heat default | 18:43 |
| mattf | SergeyLukjanov, alazarev, what about letting in alazarev's change and filing a but to remove it once we go to heat? | 18:43 |
| mattf | dmitryme, ahh | 18:43 |
| mattf | eesh bug* | 18:43 |
| dmitryme | Heat pushes onto instance not only userdata provided by the user, but also some additional scripts | 18:44 |
| dmitryme | one of them sets up ec2-user | 18:44 |
| mattf | dmitryme, i didn't know that, thanks | 18:44 |
| aignatov | dmitry, thx, with heat we will remove username field from registering image | 18:44 |
| alazarev | and, once again… what wrong with extra? engines could use it whatever they need | 18:44 |
| dmitryme | mattf: no problem, it was a surprise for me actually | 18:44 |
| mattf | alazarev, that's kinda what's wrong with it | 18:45 |
| mattf | dmitryme, i'm sure you just saved me a ton of pain later on when i'd be trying to figure out why things are happening when i didn't explicitly ask for them to happenm | 18:45 |
| aignatov | alazarev: I have nothing against extra | 18:45 |
| mattf | alazarev, i'm flexible, ok w/ adding so long as we record the fact that we should later remove it | 18:45 |
| *** ndipanov has quit IRC | 18:46 | |
| dmitryme | alazarev: I would prefer one more specific field in node group, like 'username', not just 'extra' | 18:46 |
| SergeyLukjanov | alazarev, my concern is that we're resurrecting extra for some objects in different patches instead of thinking about the common way to store additional info for objects | 18:46 |
| SergeyLukjanov | custom/optional info | 18:46 |
| alazarev | dmitryme: heat doesn't need such field, what's why I used extra | 18:46 |
| SergeyLukjanov | plugin-specific maybe too | 18:46 |
| SergeyLukjanov | heat needs it too | 18:47 |
| SergeyLukjanov | but it'll be ec2-user | 18:47 |
| alazarev | SergeyLukjanov: extra is a common way, no? | 18:47 |
| SergeyLukjanov | I think that could make it configurable for example | 18:47 |
| SergeyLukjanov | heat guys * | 18:47 |
| *** amcrn has joined #openstack-meeting-alt | 18:47 | |
| SergeyLukjanov | alazarev, not really, we're adding it for each object when we're need it | 18:48 |
| *** nadya_ has joined #openstack-meeting-alt | 18:48 | |
| dmitryme | alazarev: but the plugin does not know which engine is used, Heat or Direct | 18:48 |
| tmckay | hmmm, we have an "extra" in job_binary for EDP. Maybe I should try to stamp that out too | 18:49 |
| dmitryme | so it does not know how to get the username in a uniform way | 18:49 |
| alazarev | SergeyLukjanov: exactly! and I don't see problems here, let's extra be | 18:49 |
| aignatov | tmckay: it is specific EDP extra, don't worry about it :) | 18:49 |
| *** sarob has joined #openstack-meeting-alt | 18:49 | |
| tmckay | is "extra" extra good or extra bad? That is the question | 18:49 |
| mattf | "extra" is a red flag for me, means we missed something in the design | 18:50 |
| aignatov | in EDP it is good | 18:50 |
| alazarev | dmitryme: yes, that's why we have corresponding method in engine. Engine could use extra or don't use | 18:50 |
| tmckay | :) a Python programmer's best friend | 18:50 |
| SergeyLukjanov | tmckay, yup | 18:50 |
| dmitryme | alazarev: we can simply unconditionally set the username field in node group before passing the cluster to the plug | 18:51 |
| dmitryme | IMHO that is much simplier | 18:51 |
| jmaron | dmitryme: I think I like that | 18:51 |
| mattf | dmitryme, nice thought | 18:51 |
| alazarev | mattf: if we keep something important in extra - yes, if it is used for caching or passing params - it's Ok for me | 18:52 |
| *** _ruhe is now known as ruhe | 18:52 | |
| SergeyLukjanov | dmitryme, +1 | 18:52 |
| alazarev | ok, will change to username field, extra was used because of heat only | 18:52 |
| SergeyLukjanov | alazarev, yup, username field looks good | 18:53 |
| aignatov | ok, agreed with username field | 18:53 |
| SergeyLukjanov | probably we can add something to the orchestration engines to be able to override get_username behaviour | 18:53 |
| aignatov | but what should we do with current extra field options in cluster obis? | 18:54 |
| aignatov | https://github.com/openstack/savanna/blob/master/savanna/plugins/vanilla/config_helper.py#L222-L232 | 18:54 |
| mattf | alazarev, thanks for bring this up during the meeting. it helped me understand what you were after w/ that cr | 18:54 |
| tmckay | so, while we're here... | 18:55 |
| tmckay | I think I have just enough time to do more workflow extensions before Jan 22 | 18:55 |
| tmckay | what would people like to see? I know there is a roadmap note somewhere | 18:55 |
| mattf | spark? | 18:55 |
| tmckay | Maybe raw oozie workflows, or streaming | 18:56 |
| tmckay | mattf, I am unaware of oozie/spark integratoin | 18:56 |
| mattf | me too, more a ref to the inbound spark plugin | 18:56 |
| alazarev | aignatov: I vote to move hadoop_private_ssh_key and hadoop_public_ssh_key into fields and remove extra… to be consistent | 18:56 |
| tmckay | also, there is a shell workflow that might be nice | 18:57 |
| aignatov | tmckay: maybe integration tests support of Java added action, updated rest api docs about new action? | 18:57 |
| mattf | alazarev, btw, what do we need the public part of that key for? | 18:57 |
| SergeyLukjanov | alazarev, it's only used by the vanilla plugin now I think, so, it's not good to make it a field | 18:57 |
| tmckay | aignatov, definitely, I was thinking maybe I have enough time after that for another... | 18:57 |
| aignatov | tmckay: what will be after Jan 22? | 18:58 |
| tmckay | Oh, that's just the freeze | 18:58 |
| SergeyLukjanov | tmckay, code freeze for i2 | 18:58 |
| dmitryme | alazarev: do we really need to store these keys for the Vanilla plugin? | 18:58 |
| dmitryme | I can't imagine why? | 18:58 |
| aignatov | dmitryme: we need, it simplify hadoop debugging after install | 18:59 |
| alazarev | SergeyLukjanov: this means that plugins could store data in cluster.extra but can't in node group.extra, that looks strange for me | 18:59 |
| alazarev | dmitryme: to put them on machine during scaling I believe | 19:00 |
| mattf | alazarev, you're not wrong | 19:00 |
| SergeyLukjanov | guys, I'd like to ask you to go through the https://launchpad.net/savanna/+milestone/icehouse-2 and decide what you'd like to do in i2 | 19:00 |
| SergeyLukjanov | we're out of time | 19:00 |
| SergeyLukjanov | thanks all | 19:00 |
| aignatov | tmckay: another thing I thought in EDP would be nice is to implement multiple workflows | 19:00 |
| SergeyLukjanov | #endmeeting | 19:00 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 19:00 | |
| openstack | Meeting ended Thu Jan 9 19:00:55 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 19:00 |
| dmitryme | alazarev: got iyt | 19:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-01-09-18.10.html | 19:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-01-09-18.10.txt | 19:01 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-01-09-18.10.log.html | 19:01 |
| dmitryme | *it | 19:01 |
| aignatov | just more than one action in workflow.xml ^_^ | 19:01 |
| *** hartsocks has left #openstack-meeting-alt | 19:01 | |
| *** jspeidel has left #openstack-meeting-alt | 19:01 | |
| *** mattf has left #openstack-meeting-alt | 19:01 | |
| *** NikitaKonovalov has quit IRC | 19:02 | |
| *** vponomaryov has joined #openstack-meeting-alt | 19:02 | |
| *** bob_nettleton has left #openstack-meeting-alt | 19:02 | |
| *** crobertsrh has left #openstack-meeting-alt | 19:02 | |
| *** nadya_ has quit IRC | 19:09 | |
| *** nadya_ has joined #openstack-meeting-alt | 19:10 | |
| *** SergeyLukjanov has quit IRC | 19:13 | |
| *** rsblendido has quit IRC | 19:14 | |
| *** rossella_s has quit IRC | 19:14 | |
| *** rsblendido has joined #openstack-meeting-alt | 19:15 | |
| *** rossella_s has joined #openstack-meeting-alt | 19:15 | |
| *** rossella_s has quit IRC | 19:15 | |
| *** aignatov has quit IRC | 19:15 | |
| *** eankutse has joined #openstack-meeting-alt | 19:16 | |
| *** tomblank has quit IRC | 19:20 | |
| *** doug_shelley66 has quit IRC | 19:23 | |
| *** doug_shelley66 has joined #openstack-meeting-alt | 19:24 | |
| *** NehaV1 has joined #openstack-meeting-alt | 19:28 | |
| *** doug_shelley66 has quit IRC | 19:30 | |
| *** vgnbkr_1 has quit IRC | 19:30 | |
| *** NehaV has quit IRC | 19:31 | |
| *** rnirmal has quit IRC | 19:33 | |
| *** doug_shelley66 has joined #openstack-meeting-alt | 19:36 | |
| *** rnirmal has joined #openstack-meeting-alt | 19:39 | |
| *** doug_shelley66 has quit IRC | 19:40 | |
| *** IlyaE has joined #openstack-meeting-alt | 19:40 | |
| *** colinmcnamara has joined #openstack-meeting-alt | 19:40 | |
| *** doug_shelley66 has joined #openstack-meeting-alt | 19:40 | |
| *** markmcclain has quit IRC | 19:42 | |
| *** vgnbkr_1 has joined #openstack-meeting-alt | 19:44 | |
| *** ruhe is now known as _ruhe | 19:44 | |
| *** nadya_ has quit IRC | 19:49 | |
| *** sarob has quit IRC | 19:50 | |
| *** sarob has joined #openstack-meeting-alt | 19:51 | |
| *** zhiyan has joined #openstack-meeting-alt | 19:51 | |
| *** sarob has quit IRC | 19:53 | |
| *** sarob has joined #openstack-meeting-alt | 19:53 | |
| *** pballand has quit IRC | 19:53 | |
| *** eshel has quit IRC | 19:56 | |
| *** gokrokve has joined #openstack-meeting-alt | 19:56 | |
| *** markmcclain has joined #openstack-meeting-alt | 19:56 | |
| *** noslzzp has quit IRC | 19:58 | |
| markwash | Any glance folks around? | 20:01 |
| iccha | hey | 20:01 |
| rosmaita | yo! | 20:01 |
| zhiyan | markwash: happy new year markwash, iccha | 20:01 |
| markwash | #startmeeting glance | 20:02 |
| zhiyan | and rosmaita! | 20:02 |
| openstack | Meeting started Thu Jan 9 20:02:06 2014 UTC and is due to finish in 60 minutes. The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot. | 20:02 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 20:02 |
| *** openstack changes topic to " (Meeting topic: glance)" | 20:02 | |
| openstack | The meeting name has been set to 'glance' | 20:02 |
| arnaud | hi | 20:02 |
| markwash | greetings everyone | 20:02 |
| markwash | happy 2014 | 20:02 |
| markwash | agenda link | 20:02 |
| markwash | #link https://etherpad.openstack.org/p/glance-team-meeting-agenda | 20:02 |
| *** nadya_ has joined #openstack-meeting-alt | 20:03 | |
| markwash | a lot of boiler plate to go through I think | 20:03 |
| markwash | so I'll go ahead and get started | 20:03 |
| markwash | #topic mini summit | 20:04 |
| *** openstack changes topic to "mini summit (Meeting topic: glance)" | 20:04 | |
| markwash | I hope folks saw my email announcing the details for the mini summit | 20:04 |
| markwash | #link http://lists.openstack.org/pipermail/openstack-dev/2013-December/023153.html | 20:04 |
| markwash | I've kicked off a draft agenda here | 20:04 |
| markwash | #link https://etherpad.openstack.org/p/glance-mini-summit-agenda | 20:04 |
| arnaud | do you have an idea approximately how many people will attend? | 20:05 |
| markwash | it had some initial looks and feedback | 20:05 |
| markwash | arnaud: I think the upper end is around 25 folks | 20:05 |
| arnaud | ok sounds good! | 20:05 |
| markwash | probably somewhere in the high teens | 20:05 |
| *** vipuls is now known as vipuls-away | 20:05 | |
| *** vipuls-away is now known as vipuls | 20:05 | |
| markwash | so we need your help to make this meeting a success, have a look at the agenda, add to it, add your interest | 20:06 |
| markwash | if there is anything that seems missing let me know | 20:06 |
| markwash | I think by next week we should have enough to start actually scheduling so folks know what they need to prepare in terms of discussion notes / slides / etc | 20:06 |
| iccha | sounds good | 20:06 |
| markwash | this is the first time doing a mini summit for. . um. . all of us? so I guess we'll be playing most of the parts by ear :-) | 20:07 |
| markwash | so we'll try to have fun :-) | 20:07 |
| rosmaita | it's just like a regular summit, only mini | 20:07 |
| markwash | any questions about the summit? | 20:07 |
| *** boris-42 has quit IRC | 20:08 | |
| iccha | so will we have separate time apart from these talks for discussions i hope ( i presume yes_ | 20:08 |
| markwash | yes, I think so | 20:08 |
| markwash | there will be some downtime for sure | 20:09 |
| markwash | and meals etc | 20:09 |
| *** SergeyLukjanov has joined #openstack-meeting-alt | 20:09 | |
| markwash | if you like, we can leave open some time for informal lightning talks etc | 20:09 |
| arnaud | for now, there are ~10 talks, if all of them are 1h, 10h in 2 days, it seems there is time left for discussion | 20:09 |
| markwash | I also thought there might be some room if folks want to do a little hackathon type thing | 20:10 |
| markwash | but I'm not exactly sure what form that would take, and would like to have a good idea before we devote time to it | 20:10 |
| markwash | anyway, food for thought in case anyone especially likes the idea | 20:10 |
| markwash | moving on for today | 20:10 |
| markwash | #topic Icehouse 2 is closing soon | 20:10 |
| *** openstack changes topic to "Icehouse 2 is closing soon (Meeting topic: glance)" | 20:10 | |
| zhiyan | markwash: is there some plan to allow people "attend" the summit remotely who can't go there? like a remote video will be great | 20:11 |
| markwash | zhiyan: hmm, no plan as yet but maybe we can figure something out? it will probably be a terrible timing for you :-) | 20:11 |
| arnaud | +1 do we plan to at least record the talks? | 20:11 |
| iccha | maybe set up etherpads for notes. or use the same one | 20:11 |
| *** SergeyLukjanov has quit IRC | 20:11 | |
| markwash | zhiyan: but since its a small group it is possible that it would be easier to share e.g. with a google hangout or skype or some other software | 20:11 |
| zhiyan | humm...i'm ok for the time, if we have way to attend remotely, i will join on that time :) | 20:12 |
| markwash | heh cool | 20:12 |
| *** jmaron has quit IRC | 20:12 | |
| markwash | iccha: perhaps some rackspace video equipment could be commandeered | 20:12 |
| zhiyan | arnaud: good idea | 20:12 |
| iccha | markwash: fir recording or transmission? will ask around :) | 20:13 |
| markwash | recording I guess is probably easiest and most important | 20:13 |
| markwash | but I would love transmission if somebody knows how to do that | 20:13 |
| zhiyan | markwash: that will be great, transmission. iccha | 20:14 |
| markwash | we are only going to have 1 room / 1 track so transmission might be easier than with the regular summits | 20:14 |
| *** nadya_ has quit IRC | 20:14 | |
| zhiyan | markwash: indeed | 20:14 |
| markwash | anyway, sometimes this stuff turns into a disaster, not much better than nothing, so let's not sink too much into it unless we feel confident | 20:15 |
| markwash | this stuff -> trying to support full remote participation | 20:15 |
| markwash | recording is a clear win, so if that's all we can get so be it | 20:15 |
| markwash | any further mini summit thoughts? | 20:15 |
| iccha | will ask about recording and let u know markwash | 20:16 |
| markwash | cool | 20:16 |
| markwash | On to Icehouse 2 | 20:16 |
| markwash | all my thoughts are there on the meeting agenda page | 20:16 |
| markwash | #link https://launchpad.net/glance/+milestone/icehouse-2 | 20:16 |
| markwash | we've got less than 2 weeks, since we'll probably want to cut on the 20th | 20:17 |
| *** boris-42 has joined #openstack-meeting-alt | 20:17 | |
| markwash | the gate has been really rough lately, even without a crunch time | 20:17 |
| markwash | so I'm expecting very bad weather, so to speak | 20:17 |
| markwash | if you want to land something, you probably need to get it into the gate queue by the middle of next week | 20:17 |
| markwash | and reviewers need to be on hand to help with that process | 20:18 |
| markwash | I will note, we have some blueprints that aren't started yet | 20:18 |
| markwash | should we consider deferring https://blueprints.launchpad.net/glance/+spec/new-download-workflow ? | 20:18 |
| markwash | or is the work just not up to date? | 20:18 |
| markwash | also, flaper87 was working on https://blueprints.launchpad.net/glance/+spec/split-image-size but I haven't seen a patch yet, am I just missing it? | 20:19 |
| iccha | we do not have import script merged yet. so maybe we will have to jump similar hurdles for export | 20:19 |
| iccha | i know nikhil started work on it but not sure where he is at | 20:19 |
| markwash | hmm okay | 20:21 |
| markwash | well, if I don't hear back by tuesday I'm going to defer those two | 20:21 |
| *** vipuls is now known as vipuls-away | 20:21 | |
| markwash | any other thoughts on icehouse-2? questions? | 20:21 |
| arnaud | I think it would be good at the minisumit to have some time allocated to look at what is done, what was expected, what is left | 20:22 |
| arnaud | for icehouse | 20:22 |
| rosmaita | +1 | 20:22 |
| markwash | arnaud: good idea | 20:22 |
| *** ashwini has joined #openstack-meeting-alt | 20:23 | |
| markwash | that should be a good motivating discussion | 20:23 |
| iccha | yeah could tie into the blueprint discussion | 20:23 |
| markwash | and help constrain our wilder plans on some of the other topics | 20:23 |
| iccha | ashwini: says videoeqipment is a yes! | 20:23 |
| markwash | huzzah, thanks ashwini | 20:24 |
| arnaud | nice :) | 20:24 |
| ashwini | sorry joining let but yes i will take care of that | 20:24 |
| ashwini | s/let/late | 20:24 |
| zhiyan | ashwini: iccha thanks | 20:24 |
| markwash | okay cool, let's take a look at the review queue, my favorite topic :-P | 20:24 |
| markwash | #topic review backlog | 20:24 |
| *** openstack changes topic to "review backlog (Meeting topic: glance)" | 20:24 | |
| markwash | I posted a bunch of links in the agenda, not going to repost here | 20:25 |
| markwash | but I think something ameade brought up in the past is still very relevant | 20:25 |
| markwash | I think we're still just trimming our queue with "abandoned due to inactivity" | 20:25 |
| markwash | sad times | 20:25 |
| *** briancli1e is now known as briancline | 20:25 | |
| markwash | we've had queue growth over the past 3 months | 20:26 |
| markwash | I'm a bit afraid we're only going to recover from this when we figure out how to block out some of the noise | 20:27 |
| markwash | in terms of patches that are more churn than value | 20:27 |
| markwash | hopefully some automation around bugs, blueprints, and patches can help that | 20:27 |
| markwash | Anyone have thoughts on how we can fix our review backlog? | 20:27 |
| iccha | is the problem not enough reviews or not enough reviewers or neither or both? | 20:28 |
| iccha | Glance Core team size: 10 (avg 1.0 reviews/day) | 20:29 |
| iccha | Nova Core team size: 19 (avg 2.5 reviews/day) | 20:29 |
| iccha | for 90 days | 20:29 |
| markwash | I suppose the glance core team is a bit inflated, we probably have more like 5 active core members | 20:29 |
| arnaud | some of the core glance are not reviewing code right? | 20:29 |
| markwash | which would bring us up to 2.0 reviews/day | 20:29 |
| *** eharney has quit IRC | 20:30 | |
| *** jmaron has joined #openstack-meeting-alt | 20:30 | |
| markwash | the whole thing needs to be considered against our patch volume as well | 20:30 |
| markwash | we get about 15 patchsets a day | 20:31 |
| markwash | and we get about 4 patches per change | 20:31 |
| markwash | so that's really only about 4 changes per day | 20:31 |
| markwash | oh, 3.7 per day over the past 90 days | 20:31 |
| markwash | of course, the number of reviews needed is something like patchsets / day + changes / day | 20:32 |
| iccha | Changes abandoned in the last 90 days: 97 (1.1/day) | 20:32 |
| markwash | so that has us needing 18.5 reviews a day | 20:32 |
| *** colinmcnamara has quit IRC | 20:33 | |
| markwash | I can see a few ways to affect this | 20:33 |
| markwash | more reviews (more reviewers * more reviews per reviewer) | 20:33 |
| markwash | fewer changes | 20:33 |
| markwash | fewer patchsets per change | 20:33 |
| arnaud | how can you control fewer changes? | 20:34 |
| nikhil___ | hi | 20:34 |
| iccha | more reviews on a given patchset | 20:34 |
| iccha | or more complete reviews | 20:34 |
| markwash | arnaud: I think we can potentially have some automatic -2s that essentially remove changes from consideration | 20:34 |
| arnaud | I see, interesting | 20:34 |
| markwash | arnaud: its essentially figuring out a way to raise the barrier to entry | 20:34 |
| markwash | which isn't considered a good thing by many | 20:35 |
| arnaud | yes I see, a queue before the queue :) | 20:35 |
| markwash | however, I just don't see how we can have much in the way of sanity if our review queue isn't averaging something close to zero | 20:35 |
| iccha | for example jenkins job fialing | 20:35 |
| iccha | on py27 tests or soemthing | 20:35 |
| *** ErikB has joined #openstack-meeting-alt | 20:36 | |
| markwash | iccha: I do feel like maybe something along the lines of better blueprint triage, like you've been looking into, could allow us to say "auto -2" to things that didn't have approved blueprints | 20:36 |
| markwash | I think better bug triage is another part of that picture | 20:36 |
| markwash | since if we tightly control only one of blueprints or bugs, then the uncontrolled one becomes a shunt and everyone with an untagged change will just tag it as a bugfix or blueprint, whichever is easiest | 20:37 |
| markwash | without really adding any value in terms of up-front consideration | 20:37 |
| markwash | oh well, again more food for thought. . if the 5 active core folks we had just all tried to get 4 reviews per day, I think the queue would gradually go down | 20:38 |
| iccha | is there a repo for gerrit or all this automation? | 20:38 |
| markwash | I'm trying to do 10-20 a day to get down to a lower queue level but I burn out kinda fast | 20:38 |
| zhiyan | markwash: cool | 20:39 |
| markwash | zhiyan: thanks so much for your help in that, btw! | 20:39 |
| zhiyan | markwash: np at all | 20:39 |
| markwash | I love how we seem to trade off timezones and the "Needs One More +2" queue :-) | 20:39 |
| zhiyan | markwash: yes, actually that's my first page on the morning | 20:40 |
| markwash | mine too :-) | 20:40 |
| zhiyan | :) | 20:40 |
| iccha | awwww :) | 20:40 |
| iccha | sorry could not help it :p | 20:40 |
| markwash | lol | 20:40 |
| nikhil___ | do you guys use some kinda of special query for that? | 20:40 |
| nikhil___ | sorry jenkins filters dont seem intuitive to me | 20:40 |
| markwash | https://review.openstack.org/#/q/status:open+project:%255Eopenstack.*glance.*+branch:master+label:CodeReview%253D2+-label:CodeReview%253D-1+-+label:CodeReview%253D-2+-label:Approved%253D1,n,z | 20:40 |
| nikhil___ | ty markwash | 20:41 |
| zhiyan | markwash: btw, could you pls share another worth quick-link with me/us? (maybe you can help do that on each meeting) | 20:41 |
| markwash | zhiyan: I don't exactly follow, can you elaborate? | 20:42 |
| *** tomblank has joined #openstack-meeting-alt | 20:42 | |
| zhiyan | markwash: oh, another link, just like this "Needs One More +2" | 20:42 |
| zhiyan | markwash: which can help me/us accelerate review/landing change | 20:42 |
| markwash | sure, what do you want this other link to point to? | 20:43 |
| arnaud | is there anything reviewers (who are not core), can do to accelerate the review process? | 20:43 |
| *** spredzy has joined #openstack-meeting-alt | 20:43 | |
| iccha | reviews from everyone are welcome | 20:44 |
| markwash | well, we could promote some active non-core folks to core | 20:44 |
| iccha | core or not | 20:44 |
| arnaud | (maybe focus of reviews related to approved bp?) | 20:44 |
| markwash | to help move things along? | 20:44 |
| zhiyan | markwash: no particular idea, just want to know your experience | 20:44 |
| markwash | I think -1s are always helpful when needed, also | 20:44 |
| markwash | zhiyan: ah sure thing | 20:44 |
| markwash | zhiyan: I can post all of the ones I use in an email if you like | 20:46 |
| zhiyan | markwash: lzy.dev@gmail.com | 20:46 |
| arnaud | there is something I noticed, is that sometime, reviewers give one review on a patch, and then when the code is updated or whatever, it is harder to get another review.. do you guys have the same feeling? | 20:46 |
| markwash | yeah absolutely | 20:46 |
| iccha | markwash: maybe share it in meeting etherpad? | 20:46 |
| zhiyan | markwash: thanks! | 20:46 |
| iccha | so all of us can have access to it | 20:46 |
| markwash | that's part of the insanity of having such a long queue | 20:46 |
| *** radix__ has quit IRC | 20:46 | |
| markwash | arnaud: if you tend to feed off the bottom of the queue, then the second review after a fix takes forever to loop back around | 20:47 |
| markwash | I wonder if to respond to that we should try to top-feed off of the queue of reviewable items | 20:47 |
| markwash | btw, link to reviewable changes: | 20:47 |
| markwash | https://review.openstack.org/#/q/-label:CodeReview%253C%253D-1+-label:Verified%253C%253D-1+-label:Approved%253E%253D1++-status:workinprogress+-status:draft+-is:starred+-owner:mark.washenberger%2540markwash.net+project:%255Eopenstack.*glance.*,n,z | 20:47 |
| *** ViswaV has quit IRC | 20:47 | |
| *** mat-lowery has quit IRC | 20:47 | |
| markwash | probably want to put in your own name to that filter | 20:47 |
| zhiyan | markwash: cool | 20:49 |
| markwash | the problem with that link I just shared is that its hard to find out when someone simply disagrees with a -1 and doesn't push a new patchset | 20:49 |
| markwash | because any -1 removes you from the queue | 20:49 |
| *** pballand has joined #openstack-meeting-alt | 20:49 | |
| markwash | okay, I wanna open up for discussion, but we can keep talking about reviews | 20:49 |
| markwash | I don't have any action items for this yet, I just want people to know the scale of the problem | 20:49 |
| markwash | #topic open discussion | 20:49 |
| *** openstack changes topic to "open discussion (Meeting topic: glance)" | 20:49 | |
| nikhil___ | about the export script | 20:50 |
| nikhil___ | Have started the work on swift store side of things, Fei had mentioned about working on the filesystem one | 20:50 |
| nikhil___ | he was waiting on the executor to be pushed up | 20:50 |
| arnaud | reviews out? | 20:51 |
| iccha | This is an important change and more diverse reviews the better on this one: https://review.openstack.org/#/c/34801/ | 20:51 |
| nikhil___ | I'm planning to work for next 3-5 days on export and then work on executor | 20:51 |
| nikhil___ | markwash: ^^ | 20:51 |
| markwash | nikhil___: okay great, daily or semi-daily report emails appreciated, they're great reminders for me | 20:51 |
| markwash | don't have to be long or formal at all :-) | 20:52 |
| *** denis_makogon_ has joined #openstack-meeting-alt | 20:52 | |
| *** Duane_ has joined #openstack-meeting-alt | 20:52 | |
| markwash | iccha: does that patch do what you guys want it to at RS? | 20:52 |
| markwash | I've been a bit nervous though I look at it in my queue every day | 20:52 |
| *** denis_makogon has quit IRC | 20:52 | |
| *** denis_makogon_ is now known as denis_makogon | 20:52 | |
| *** dmakogon_ has joined #openstack-meeting-alt | 20:53 | |
| nikhil___ | markwash: sure will start them back on starting tomorrow. (Have just been distracted by either being sick or having my apartment getting flooded), Focus on reviews and MP would be back on next week onwards. | 20:53 |
| markwash | oh my | 20:53 |
| markwash | well I hope your health and apartment are returning to working order! | 20:53 |
| iccha | markwash: it looked like the best temporary solution. it makes me nervous too. thats why not rushing it and would like more eyes on it | 20:53 |
| *** dprince has quit IRC | 20:53 | |
| nikhil___ | thank you! | 20:54 |
| markwash | iccha: okay cool I'll stop avoiding it then :-) | 20:54 |
| arnaud | iccha: will look at it too | 20:55 |
| markwash | Any other thoughts? or shall we close out? I can start my lunch ;-) | 20:55 |
| nikhil___ | markwash: just one comment | 20:55 |
| nikhil___ | I will try to have the tasks demo in the mini summit on RS cloud + swift | 20:56 |
| markwash | oh awesome! | 20:56 |
| *** Duane has quit IRC | 20:56 | |
| markwash | thanks nikhil___ | 20:56 |
| nikhil___ | not sure if I can have it done on filesystem +devstack though | 20:56 |
| nikhil___ | great | 20:56 |
| markwash | that sounds really good | 20:56 |
| markwash | okay, thanks everyone, have a nice rest of your week and weekend | 20:56 |
| rosmaita | bye! | 20:56 |
| arnaud | bye | 20:56 |
| iccha | thanks markwash | 20:56 |
| markwash | think about what you want out of the mini summit! | 20:57 |
| zhiyan | bye! | 20:57 |
| markwash | #endmeeting | 20:57 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 20:57 | |
| openstack | Meeting ended Thu Jan 9 20:57:03 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 20:57 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-01-09-20.02.html | 20:57 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-01-09-20.02.txt | 20:57 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-01-09-20.02.log.html | 20:57 |
| *** Barker has quit IRC | 20:59 | |
| *** lblanchard has quit IRC | 20:59 | |
| *** Barker has joined #openstack-meeting-alt | 20:59 | |
| *** ashwini has left #openstack-meeting-alt | 21:05 | |
| *** eharney has joined #openstack-meeting-alt | 21:05 | |
| *** vipuls-away is now known as vipuls | 21:08 | |
| *** dmitryme has quit IRC | 21:16 | |
| *** gokrokve has quit IRC | 21:21 | |
| *** gokrokve has joined #openstack-meeting-alt | 21:22 | |
| *** julim has quit IRC | 21:22 | |
| *** gokrokve has quit IRC | 21:26 | |
| *** colinmcnamara has joined #openstack-meeting-alt | 21:27 | |
| *** jmaron has quit IRC | 21:28 | |
| *** pballand has quit IRC | 21:29 | |
| *** zhiyan has left #openstack-meeting-alt | 21:35 | |
| *** ViswaV has joined #openstack-meeting-alt | 21:43 | |
| *** ViswaV has quit IRC | 21:44 | |
| *** jmaron has joined #openstack-meeting-alt | 21:44 | |
| *** ViswaV has joined #openstack-meeting-alt | 21:44 | |
| *** sc68cal has quit IRC | 21:46 | |
| *** sc68cal has joined #openstack-meeting-alt | 21:47 | |
| *** DennyZhang has joined #openstack-meeting-alt | 21:47 | |
| *** banix has quit IRC | 21:48 | |
| *** banix has joined #openstack-meeting-alt | 21:49 | |
| *** sarob has quit IRC | 21:50 | |
| *** sarob has joined #openstack-meeting-alt | 21:51 | |
| *** jdob has quit IRC | 21:52 | |
| *** DennyZhang has quit IRC | 21:53 | |
| *** sarob_ has joined #openstack-meeting-alt | 21:53 | |
| *** Duane_ has quit IRC | 21:53 | |
| *** BrianB_ has joined #openstack-meeting-alt | 21:55 | |
| *** sarob has quit IRC | 21:56 | |
| *** mat-lowery has joined #openstack-meeting-alt | 21:56 | |
| *** nati_ueno has quit IRC | 21:56 | |
| *** nati_ueno has joined #openstack-meeting-alt | 21:59 | |
| *** pcm_ has joined #openstack-meeting-alt | 22:01 | |
| *** pdmars has quit IRC | 22:02 | |
| *** nati_ueno has quit IRC | 22:03 | |
| *** dane_ has joined #openstack-meeting-alt | 22:04 | |
| *** nati_ueno has joined #openstack-meeting-alt | 22:04 | |
| *** jmontemayor has quit IRC | 22:06 | |
| *** eankutse has quit IRC | 22:08 | |
| *** markwash has quit IRC | 22:10 | |
| *** pcm_ has quit IRC | 22:11 | |
| *** doug_shelley66 has quit IRC | 22:13 | |
| *** gokrokve has joined #openstack-meeting-alt | 22:14 | |
| *** mestery has quit IRC | 22:16 | |
| *** mestery has joined #openstack-meeting-alt | 22:19 | |
| *** jprovazn has quit IRC | 22:24 | |
| *** markwash has joined #openstack-meeting-alt | 22:24 | |
| *** radix_ has joined #openstack-meeting-alt | 22:27 | |
| *** flaper87 is now known as flaper87|afk | 22:30 | |
| *** NehaV has joined #openstack-meeting-alt | 22:32 | |
| *** ijw has joined #openstack-meeting-alt | 22:33 | |
| *** NehaV1 has quit IRC | 22:34 | |
| *** amytron has quit IRC | 22:35 | |
| *** markwash has quit IRC | 22:35 | |
| *** kebray_ has quit IRC | 22:38 | |
| *** pnavarro has quit IRC | 22:40 | |
| *** BrianB_ has quit IRC | 22:40 | |
| *** rwsu has quit IRC | 22:45 | |
| *** doug_shelley66 has joined #openstack-meeting-alt | 22:46 | |
| *** kebray_ has joined #openstack-meeting-alt | 22:50 | |
| *** nati_ueno has quit IRC | 22:54 | |
| *** markmcclain has quit IRC | 22:54 | |
| *** sacharya has quit IRC | 22:55 | |
| *** nati_ueno has joined #openstack-meeting-alt | 22:56 | |
| *** nati_ueno has quit IRC | 22:57 | |
| *** nati_ueno has joined #openstack-meeting-alt | 22:57 | |
| *** Barker has quit IRC | 22:59 | |
| *** sarob_ has quit IRC | 23:01 | |
| *** vgnbkr_1 has quit IRC | 23:01 | |
| *** sarob has joined #openstack-meeting-alt | 23:01 | |
| *** tmckay is now known as _tmckay | 23:02 | |
| *** vponomaryov has left #openstack-meeting-alt | 23:02 | |
| *** jmaron has quit IRC | 23:02 | |
| *** jmaron has joined #openstack-meeting-alt | 23:04 | |
| *** sarob has quit IRC | 23:06 | |
| *** yogesh has quit IRC | 23:06 | |
| *** yogesh has joined #openstack-meeting-alt | 23:06 | |
| *** denis_makogon has quit IRC | 23:07 | |
| *** jecarey has quit IRC | 23:08 | |
| *** NehaV has quit IRC | 23:11 | |
| *** yogesh has quit IRC | 23:11 | |
| *** yamahata has quit IRC | 23:14 | |
| *** jmaron has quit IRC | 23:17 | |
| *** jasonb365 has quit IRC | 23:20 | |
| *** gduan has joined #openstack-meeting-alt | 23:31 | |
| *** garyduan has quit IRC | 23:33 | |
| *** sacharya has joined #openstack-meeting-alt | 23:36 | |
| *** sballe has quit IRC | 23:36 | |
| *** sballe has joined #openstack-meeting-alt | 23:36 | |
| *** mozawa has quit IRC | 23:39 | |
| *** markwash has joined #openstack-meeting-alt | 23:43 | |
| *** vgnbkr_1 has joined #openstack-meeting-alt | 23:53 | |
| *** vipuls is now known as vipuls-away | 23:56 | |
| *** vipuls-away is now known as vipuls | 23:58 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!