Tuesday, 2014-08-05

*** jjmb has quit IRC00:02
*** vivek-ebay has quit IRC00:02
*** david-lyle has quit IRC00:03
*** amotoki_ has joined #openstack-meeting00:04
*** JRobinson__ has joined #openstack-meeting00:04
*** Youcef has quit IRC00:04
*** julienvey has joined #openstack-meeting00:05
*** Leonr has quit IRC00:06
*** padkrish has quit IRC00:07
*** VijayB has quit IRC00:07
*** padkrish has joined #openstack-meeting00:07
*** julienvey has quit IRC00:10
*** yingjun has joined #openstack-meeting00:11
*** Leonr has joined #openstack-meeting00:11
*** jdurgin1 has quit IRC00:11
*** padkrish has quit IRC00:11
*** rmoe has quit IRC00:12
*** fnaval has quit IRC00:13
*** gokrokve has quit IRC00:13
*** colinmcnamara has quit IRC00:14
*** Leonr has quit IRC00:14
*** fnaval has joined #openstack-meeting00:14
*** tkay_ has joined #openstack-meeting00:15
*** tkay has quit IRC00:15
*** tkay_ is now known as tkay00:15
*** Murali has joined #openstack-meeting00:15
*** VijayB has joined #openstack-meeting00:18
*** padkrish has joined #openstack-meeting00:18
*** fnaval has quit IRC00:19
*** tsekiyama has quit IRC00:19
*** rmoe has joined #openstack-meeting00:19
*** baoli has joined #openstack-meeting00:21
*** crc32 has quit IRC00:22
*** gangil has quit IRC00:22
*** marcoemorais has quit IRC00:24
*** marcoemorais has joined #openstack-meeting00:24
*** marcoemorais has quit IRC00:24
*** tkay_ has joined #openstack-meeting00:24
*** tkay has quit IRC00:24
*** tkay_ is now known as tkay00:24
*** marcoemorais has joined #openstack-meeting00:24
*** mattgriffin has joined #openstack-meeting00:25
*** celttechie has quit IRC00:25
*** Murali has quit IRC00:25
*** tkay has quit IRC00:26
*** _nadya_ has quit IRC00:26
*** rudrarugge has quit IRC00:27
*** colinmcnamara has joined #openstack-meeting00:28
*** tkay has joined #openstack-meeting00:28
*** carl_baldwin has joined #openstack-meeting00:30
*** tsekiyama has joined #openstack-meeting00:33
*** baoli has quit IRC00:34
*** baoli has joined #openstack-meeting00:35
*** stevemar is now known as maybeiamstevemar00:35
*** carl_baldwin has quit IRC00:36
*** jjmb has joined #openstack-meeting00:38
*** jjmb has quit IRC00:39
*** chuckC has quit IRC00:39
*** manishg has quit IRC00:39
*** Riddhi has joined #openstack-meeting00:39
*** shakamunyi has quit IRC00:43
*** uberj has quit IRC00:44
*** uberj has joined #openstack-meeting00:44
*** tsekiyama has quit IRC00:45
*** mxu has quit IRC00:46
*** aleksandr_null has quit IRC00:47
*** yamamoto has joined #openstack-meeting00:48
*** aleksandr_null has joined #openstack-meeting00:48
*** amcrn has quit IRC00:51
*** patelna_ has quit IRC00:51
*** _nadya_ has joined #openstack-meeting00:52
*** yamamoto has quit IRC00:53
*** rossk_ has quit IRC00:53
*** xianghui has quit IRC00:53
*** padkrish has quit IRC00:58
*** mxin has joined #openstack-meeting00:58
*** gyee has quit IRC00:59
*** slong_ has joined #openstack-meeting01:01
*** slong has quit IRC01:01
*** eankutse has joined #openstack-meeting01:01
*** eankutse has quit IRC01:02
*** eankutse has joined #openstack-meeting01:02
*** bdpayne has quit IRC01:02
*** jjmb has joined #openstack-meeting01:04
*** aysyd has quit IRC01:04
*** Murali has joined #openstack-meeting01:04
*** leeantho_ has quit IRC01:05
*** xianghui has joined #openstack-meeting01:05
*** julienvey has joined #openstack-meeting01:06
*** rudrarugge has joined #openstack-meeting01:08
*** jjmb has quit IRC01:08
*** julienvey has quit IRC01:10
*** shashankhegde has quit IRC01:10
*** vikasd has quit IRC01:10
*** eankutse has quit IRC01:11
*** yingjun has quit IRC01:12
*** Murali has quit IRC01:15
*** christop1eraedo is now known as christopheraedo01:17
*** jergerber has quit IRC01:19
*** baoli has quit IRC01:20
*** baoli has joined #openstack-meeting01:20
*** julienvey has joined #openstack-meeting01:21
*** gokrokve has joined #openstack-meeting01:23
*** dsetia has quit IRC01:24
*** yamamoto_ has joined #openstack-meeting01:24
*** julienvey has quit IRC01:25
*** fnaval has joined #openstack-meeting01:26
*** celttechie has joined #openstack-meeting01:26
*** mxin has quit IRC01:26
*** mxin has joined #openstack-meeting01:26
*** yamamoto_ has quit IRC01:28
*** haleyb has quit IRC01:32
*** tsekiyama has joined #openstack-meeting01:32
*** mberlin has joined #openstack-meeting01:33
*** eghobo has quit IRC01:33
*** mberlin1 has quit IRC01:35
*** ramashri has quit IRC01:35
*** morganfainberg_Z is now known as morganfainberg01:35
*** yaguang has joined #openstack-meeting01:36
*** spzala has quit IRC01:39
*** banix has joined #openstack-meeting01:39
*** baohua has joined #openstack-meeting01:40
*** Murali_ has joined #openstack-meeting01:42
*** mattgriffin has quit IRC01:44
*** otter768 has joined #openstack-meeting01:45
*** jjmb has joined #openstack-meeting01:45
*** baoli has quit IRC01:48
*** nosnos has joined #openstack-meeting01:50
*** mattgriffin has joined #openstack-meeting01:50
*** mattgriffin has quit IRC01:50
*** Murali_ has quit IRC01:52
*** baoli has joined #openstack-meeting01:53
*** novas0x2a|laptop has quit IRC01:53
*** shakamunyi has joined #openstack-meeting01:54
*** tsekiyama has quit IRC01:56
*** yingjun has joined #openstack-meeting01:56
*** fnaval has quit IRC01:57
*** mattgriffin has joined #openstack-meeting01:57
*** tsekiyama has joined #openstack-meeting01:59
*** zhhuabj has joined #openstack-meeting02:00
*** tkay has quit IRC02:01
*** haomaiw__ has quit IRC02:02
*** otter768 has quit IRC02:02
*** haomaiwang has joined #openstack-meeting02:02
*** tkay has joined #openstack-meeting02:03
*** tsekiyama has quit IRC02:03
*** mattgriffin has quit IRC02:03
*** mattgriffin has joined #openstack-meeting02:05
*** marcoemorais has quit IRC02:06
*** ArxCruz has quit IRC02:06
*** jgrimm has joined #openstack-meeting02:07
*** shakamunyi has quit IRC02:07
*** colinmcnamara has quit IRC02:08
*** bdpayne has joined #openstack-meeting02:08
*** Riddhi has quit IRC02:08
*** yamamoto_ has joined #openstack-meeting02:11
*** salv-orlando has quit IRC02:11
*** adalbas has quit IRC02:12
*** safchain has quit IRC02:12
*** moha_hunt has joined #openstack-meeting02:12
*** rudrarugge has quit IRC02:13
*** ivar-lazzaro has quit IRC02:14
*** haomaiw__ has joined #openstack-meeting02:14
*** moha_hunt has quit IRC02:15
*** chuckC has joined #openstack-meeting02:15
*** VijayB has quit IRC02:16
*** sbalukoff has quit IRC02:16
*** haomaiw__ has quit IRC02:17
*** haomaiwang has quit IRC02:18
*** haomaiwang has joined #openstack-meeting02:18
*** sankarshan_away is now known as sankarshan02:18
*** sankarshan is now known as sankarshan_away02:18
*** fnaval has joined #openstack-meeting02:19
*** julienvey has joined #openstack-meeting02:21
*** shakamunyi has joined #openstack-meeting02:22
*** SumitNaiksatam has left #openstack-meeting02:23
*** julienvey has quit IRC02:26
*** hemanthravi has quit IRC02:26
*** yingjun has quit IRC02:27
*** HenryG is now known as HenryG_afk02:27
*** yingjun has joined #openstack-meeting02:27
*** noslzzp has quit IRC02:28
*** yamahata has joined #openstack-meeting02:28
*** SumitNaiksatam has joined #openstack-meeting02:28
*** jjmb has quit IRC02:28
*** dkehnx has quit IRC02:30
*** dkehnx has joined #openstack-meeting02:31
*** carl_baldwin has joined #openstack-meeting02:31
*** yingjun has quit IRC02:32
*** haomaiw__ has joined #openstack-meeting02:33
*** Slower has quit IRC02:34
*** yingjun has joined #openstack-meeting02:35
*** ramashri has joined #openstack-meeting02:35
*** gokrokve_ has joined #openstack-meeting02:35
*** praneet has quit IRC02:35
*** gokrokve_ has quit IRC02:35
*** haomaiwang has quit IRC02:35
*** gokrokve_ has joined #openstack-meeting02:35
*** hrybacki has joined #openstack-meeting02:36
*** gokrokve has quit IRC02:38
*** ramashri has quit IRC02:39
*** epico has joined #openstack-meeting02:39
*** ramashri has joined #openstack-meeting02:39
*** matiu has joined #openstack-meeting02:40
*** matiu has joined #openstack-meeting02:40
*** carl_baldwin has quit IRC02:40
*** gokrokve has joined #openstack-meeting02:45
*** mxin has quit IRC02:46
*** epico has quit IRC02:46
*** Murali has joined #openstack-meeting02:46
*** epico has joined #openstack-meeting02:48
*** mxin has joined #openstack-meeting02:48
*** gokrokve_ has quit IRC02:49
*** yaguang has quit IRC02:49
*** matiu has quit IRC02:49
*** baoli has quit IRC02:50
*** Murali has quit IRC02:51
*** hrybacki has quit IRC02:51
*** mxin has quit IRC02:51
*** mxin has joined #openstack-meeting02:52
*** otter768 has joined #openstack-meeting02:55
*** kashyap has quit IRC02:56
*** kashyap has joined #openstack-meeting02:56
*** bdpayne has quit IRC02:56
*** dkehn has quit IRC02:56
*** funzo has quit IRC02:56
*** dkehn has joined #openstack-meeting02:57
*** Murali_ has joined #openstack-meeting02:57
*** mspreitz has joined #openstack-meeting02:58
*** bdpayne has joined #openstack-meeting03:00
*** yaguang has joined #openstack-meeting03:01
*** gokrokve has quit IRC03:01
*** shashankhegde has joined #openstack-meeting03:01
*** matiu has joined #openstack-meeting03:02
*** vivek-ebay has joined #openstack-meeting03:03
*** funzo has joined #openstack-meeting03:06
*** masayukig has joined #openstack-meeting03:07
*** ramishra has joined #openstack-meeting03:08
*** vivek-ebay has quit IRC03:08
*** arnaud has quit IRC03:11
*** Azher has joined #openstack-meeting03:11
*** julienvey has joined #openstack-meeting03:22
*** Slower has joined #openstack-meeting03:25
*** julienvey has quit IRC03:27
*** Murali_ has quit IRC03:28
*** yingjun has quit IRC03:29
*** Murali has joined #openstack-meeting03:29
*** yingjun has joined #openstack-meeting03:29
*** gokrokve has joined #openstack-meeting03:31
*** armax has quit IRC03:32
*** gokrokve_ has joined #openstack-meeting03:33
*** gokrokve has quit IRC03:33
*** gongysh has joined #openstack-meeting03:33
*** yingjun has quit IRC03:33
*** eghobo has joined #openstack-meeting03:37
*** adahms has quit IRC03:38
*** gokrokve_ has quit IRC03:41
*** gokrokve has joined #openstack-meeting03:42
*** otter768 has quit IRC03:42
*** shashankhegde has quit IRC03:43
*** adahms has joined #openstack-meeting03:43
*** colinmcnamara has joined #openstack-meeting03:43
*** gokrokve has quit IRC03:46
*** Murali has quit IRC03:48
*** Murali_ has joined #openstack-meeting03:48
*** banix has quit IRC03:51
*** gokrokve has joined #openstack-meeting03:54
*** mestery has quit IRC03:55
*** ayoung has quit IRC03:57
*** mestery has joined #openstack-meeting03:58
*** Slower has quit IRC03:59
*** colinmcnamara has quit IRC03:59
*** yingjun has joined #openstack-meeting04:00
*** Murali__ has joined #openstack-meeting04:00
*** Murali_ has quit IRC04:00
*** mxin has quit IRC04:01
*** mxin has joined #openstack-meeting04:01
*** kayaliu_ has joined #openstack-meeting04:03
*** yingjun has quit IRC04:04
*** gongysh has quit IRC04:06
*** pcm_ has quit IRC04:07
*** mxin has quit IRC04:08
*** Riddhi has joined #openstack-meeting04:09
*** shashankhegde has joined #openstack-meeting04:11
*** mestery has quit IRC04:13
*** slong_ has quit IRC04:19
*** mestery has joined #openstack-meeting04:19
*** Murali__ has quit IRC04:19
*** brucer has joined #openstack-meeting04:21
*** slong has joined #openstack-meeting04:21
*** gokrokve has quit IRC04:21
*** gokrokve has joined #openstack-meeting04:22
*** eghobo has quit IRC04:22
*** mxin has joined #openstack-meeting04:23
*** eghobo has joined #openstack-meeting04:23
*** julienvey has joined #openstack-meeting04:23
*** Poornima has joined #openstack-meeting04:24
*** SridharG has joined #openstack-meeting04:24
*** fnaval has quit IRC04:26
*** gokrokve has quit IRC04:26
*** fnaval has joined #openstack-meeting04:27
*** julienvey has quit IRC04:27
*** adahms_ has joined #openstack-meeting04:28
*** shankar has joined #openstack-meeting04:29
*** arnaud has joined #openstack-meeting04:30
*** fnaval has quit IRC04:31
*** adahms has quit IRC04:32
*** gokrokve has joined #openstack-meeting04:32
*** enikanorov has joined #openstack-meeting04:35
*** sbalukoff has joined #openstack-meeting04:38
*** enikanorov__ has joined #openstack-meeting04:41
*** enikanorov has quit IRC04:41
*** k4n0 has joined #openstack-meeting04:43
*** otherwiseguy has quit IRC04:48
*** otherwiseguy has joined #openstack-meeting04:48
*** jgrimm has quit IRC04:49
*** adahms_ has quit IRC04:49
*** adahms has joined #openstack-meeting04:49
*** adahms has quit IRC04:50
*** ildikov_ has quit IRC04:50
*** adahms has joined #openstack-meeting04:51
*** bobmel has joined #openstack-meeting04:51
*** hemanthravi has joined #openstack-meeting04:51
*** gokrokve has quit IRC04:53
*** gokrokve has joined #openstack-meeting04:54
*** morganfainberg is now known as morganfainberg_Z04:54
*** kopparam has joined #openstack-meeting04:54
*** shashankhegde has quit IRC04:55
*** vishwanathj has joined #openstack-meeting04:55
*** rajeshr has joined #openstack-meeting04:56
*** gokrokve has quit IRC04:58
yamahatahi05:00
vishwanathjhello05:00
*** gokrokve has joined #openstack-meeting05:00
*** yingjun has joined #openstack-meeting05:00
bobmelHi05:00
*** gongysh has joined #openstack-meeting05:00
yamahata#startmeeting servicevm-device-manager05:01
openstackMeeting started Tue Aug  5 05:01:07 2014 UTC and is due to finish in 60 minutes.  The chair is yamahata. Information about MeetBot at http://wiki.debian.org/MeetBot.05:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:01
*** openstack changes topic to " (Meeting topic: servicevm-device-manager)"05:01
openstackThe meeting name has been set to 'servicevm_device_manager'05:01
*** nikunj2512 has joined #openstack-meeting05:01
yamahatatoday Karthic is absent05:01
yamahata#topic Announcement05:01
*** openstack changes topic to "Announcement (Meeting topic: servicevm-device-manager)"05:01
*** s3wong has joined #openstack-meeting05:02
yamahataour proposal for openstack summit is here05:02
s3wonghello05:02
*** Riddhi has quit IRC05:02
yamahata#link https://www.openstack.org/vote-paris/Presentation/introducing-tacker-service-vm-project05:02
yamahataLet's promote it05:02
*** dbite has joined #openstack-meeting05:03
yamahataBob may want to fulfil his bio05:03
vishwanathjFYI: i voted 3 stars for it05:03
bobmels3wong: Hi05:03
yamahata#action bobmel fulfil the bio05:04
s3wongbobmel: hello - seems like you aren't using bmelander today :-)05:04
*** mattgriffin has quit IRC05:04
yamahataI uploaded WIP code for l3 routervm05:05
*** yingjun has quit IRC05:05
yamahata#link https://github.com/yamahata/neutron/tree/l3-routervm/neutron l3 routervm WIP code05:05
*** ramishra has quit IRC05:05
yamahataIt's not yet ready for review.05:05
*** ramishra_ has joined #openstack-meeting05:05
bobmelYamahata: where do I update bio?05:05
yamahataProbably only interesting code is https://github.com/yamahata/neutron/blob/l3-routervm/neutron/services/l3_router/vrouter/l3_vrouter_plugin.py05:05
yamahatahttps://github.com/yamahata/neutron/blob/l3-routervm/neutron/services/l3_router/vrouter/l3_vrouter_driver.py05:05
yamahatabobmel: Login the rfp page, then you'll find your bio page05:06
yamahata#link https://www.openstack.org/summit/openstack-paris-summit-2014/call-for-speakers/ login page for call-for-proposal05:06
bobmelyamahata: ok, thanks05:07
yamahataI still working on l3 routervm plugin code.05:07
*** obondarev has joined #openstack-meeting05:07
yamahataSorry delay for api review. I'll do it today05:08
yamahata#topic open discussion05:08
*** openstack changes topic to "open discussion (Meeting topic: servicevm-device-manager)"05:08
*** brucer has quit IRC05:08
yamahataanything to discuss?05:09
*** vkmc has quit IRC05:09
yamahataI'd like to raise the issue of auth token in neutron context05:09
yamahata#link https://review.openstack.org/#/c/111756/ patch to add auth token to neutron context05:09
yamahataDoes it help?05:10
*** otherwiseguy has quit IRC05:10
*** mattgriffin has joined #openstack-meeting05:11
yamahataAlthough just admin account would be used for simplicity for now, in future we'd like to use per tenant token or something05:11
*** mxin has quit IRC05:12
yamahataSeems no idea. Anyway it doesn't harm. I'll just push the patch.05:13
yamahataAnother topic is attach/detach interface to/from vm05:13
*** leeantho has joined #openstack-meeting05:14
yamahataLast week, we discussed a bit. But Bob wasn't there.05:14
yamahataOn behalf of router-interface-attach or plugging driver, we need to interface-attach/detach to vm.05:14
bobmelyamahata: yes, it could be useful. We currently use admin to a void the issue.05:15
yamahatait should be done by servicevm server, not neutron server.05:15
bobmelyamahata: you mean the servicecm05:16
yamahatabobmel: thanks, that encourages me. So I try to make it for Juno.05:16
yamahatabobmel: yes.05:16
yamahataSo I'm thinking of servicevm api like /device/<deviceid>/attach/detach-interface05:16
yamahataoops attach-interface or detach-interface05:17
yamahatabody includes {"port_id": <neutron port id>}05:17
bobmelyamaha: sorry, typo, you mean service VM server makes the call to add/remove vif to service VM?05:17
yamahatabobmel: Right.05:17
yamahatathe api eventually calls nova attach/detach interface with neutron port id05:18
yamahatabobmel: Does it make sense for you?05:18
bobmelyamahata: ok05:18
yamahataOr plugging driver should handle it?05:18
hemanthravican a vif be added after the vm is launched?05:18
*** afazekas has quit IRC05:19
yamahatahemanthravi: Yes05:19
s3wonghotplug?05:19
hemanthravinot all os's support hotplug05:19
yamahatas3wong: yes, pci hot plug05:19
yamahataguest OS support is another story05:20
hemanthraviproperly05:20
*** bdpayne has quit IRC05:20
bobmelyamahata: well, the operation needed to plug a logical service instance, e.g., neutron router, to a Neutron network/subnet, depends on what mechanism is used.05:20
*** deepakcs has joined #openstack-meeting05:20
bobmelVif hotplug is on such mechanism.05:20
yamahatabobmel: Do you mean plugging driver?05:21
*** bdpayne has joined #openstack-meeting05:21
yamahatabobmel: If so, I agree. we need to tell service05:21
*** eguz has joined #openstack-meeting05:21
bobmelyamahata: in our implementation we tried to capture that in what we call a plugin driver.05:21
yamahatabobmel: can you be more specific? Hopefully which code?05:22
bobmelyamahata: one plugging could then handle case with vif hotplug, another could handle case with plugin capable of VLAN trunking all the way to the VM, etc05:23
*** celttechie has quit IRC05:23
*** julienvey has joined #openstack-meeting05:24
*** adahms has quit IRC05:24
*** adahms has joined #openstack-meeting05:24
bobmelyamahata: The code submitted for review contains a plugging driver for VLAN trunking case (as supported by the Cisco N1kv plugin).05:24
yamahatabobmel: I see. A sort of abstraction will be necessary. i.e. plugging driver in your case05:24
yamahata_get_unused_service_vm_trunk_port ?05:25
*** eghobo has quit IRC05:25
bobmelyamahata: yes, that's what we tried to achieve. Perhaps the abstraction needs to evolve but it can handle VLAN trunk case and vif hotplug case.05:26
*** rakesh_hs has joined #openstack-meeting05:26
*** chandankumar has joined #openstack-meeting05:27
yamahatabobmel: Agree, the abstraction will  be evolved from simple cases.05:27
bobmelyamahata: that's an internal function in the VLAN trunk case, the interface is in the __init__ file in the plugging driver directory05:27
*** enikanorov__ has quit IRC05:28
*** julienvey has quit IRC05:28
yamahataanything else to discuss?05:29
bobmelThe driver interface is here: #link: https://review.openstack.org/#/c/101002/12/neutron/plugins/cisco/l3/plugging_drivers/__init__.py05:30
yamahatathank you everyone. see you next week05:30
bobmelOk, bye!05:30
s3wongThanks!05:30
yamahatabobmel: thanks. Now I know where I should look at.05:30
yamahata#endmeeting05:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:30
openstackMeeting ended Tue Aug  5 05:30:57 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-08-05-05.01.html05:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-08-05-05.01.txt05:31
openstackLog:            http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-08-05-05.01.log.html05:31
*** reed has quit IRC05:31
*** vishwanathj has quit IRC05:31
*** hrybacki has joined #openstack-meeting05:31
*** mattgriffin has quit IRC05:32
*** hemanthravi has quit IRC05:32
*** leeantho has quit IRC05:32
*** mspreitz has quit IRC05:32
*** Longgeek has joined #openstack-meeting05:33
*** bobmel has quit IRC05:34
*** hrybacki_ has joined #openstack-meeting05:38
*** hrybacki has quit IRC05:38
*** shakamunyi has quit IRC05:42
*** epico has quit IRC05:43
*** afazekas has joined #openstack-meeting05:45
*** epico has joined #openstack-meeting05:45
*** bdpayne has quit IRC05:54
*** brucer has joined #openstack-meeting05:55
*** mtanino has quit IRC05:56
*** flaper87|afk is now known as flaper8705:56
*** aswadr has joined #openstack-meeting05:58
*** eguz has quit IRC06:01
*** yingjun has joined #openstack-meeting06:01
*** brucer has quit IRC06:01
*** jamespage_ has joined #openstack-meeting06:04
*** jamespage_ has quit IRC06:04
*** yingjun has quit IRC06:06
*** gokrokve has quit IRC06:06
*** shakamunyi has joined #openstack-meeting06:09
*** elynn_ has joined #openstack-meeting06:12
*** ramashri has quit IRC06:16
*** s3wong has quit IRC06:16
*** elynn_ has quit IRC06:21
*** Hayim has joined #openstack-meeting06:22
*** Hayim2 has quit IRC06:22
*** ildikov has joined #openstack-meeting06:23
*** shakamunyi has quit IRC06:24
*** julienvey has joined #openstack-meeting06:24
*** obondarev has quit IRC06:25
*** ngoswami has joined #openstack-meeting06:26
*** doron_afk has joined #openstack-meeting06:27
*** MaxV has joined #openstack-meeting06:28
*** Longgeek has quit IRC06:28
*** Longgeek has joined #openstack-meeting06:28
*** Longgeek has quit IRC06:29
*** Longgeek_ has joined #openstack-meeting06:29
*** julienvey has quit IRC06:29
*** adahms has quit IRC06:30
*** slong has quit IRC06:30
*** Longgeek_ has quit IRC06:31
*** gokrokve has joined #openstack-meeting06:33
*** kayaliu_ has quit IRC06:33
*** gokrokve has quit IRC06:34
*** gokrokve has joined #openstack-meeting06:35
*** pkoniszewski has joined #openstack-meeting06:35
*** Hayim has quit IRC06:37
*** nshaikh has joined #openstack-meeting06:37
*** Hayim has joined #openstack-meeting06:37
*** gokrokve has quit IRC06:40
*** _nadya_ has quit IRC06:40
*** _nadya_ has joined #openstack-meeting06:40
*** flaper87 is now known as flaper87|afk06:41
*** Longgeek has joined #openstack-meeting06:42
*** leeantho has joined #openstack-meeting06:45
*** kayaliu_ has joined #openstack-meeting06:46
*** epico has quit IRC06:47
*** kopparam has quit IRC06:48
*** rakesh_hs2 has joined #openstack-meeting06:49
*** rakesh_hs has quit IRC06:49
*** tkay has left #openstack-meeting06:50
*** shakamunyi has joined #openstack-meeting06:50
*** yingjun has joined #openstack-meeting06:52
*** pblaho has joined #openstack-meeting06:52
*** jjmb has joined #openstack-meeting06:53
*** toshy has joined #openstack-meeting06:55
*** toshy has left #openstack-meeting06:56
*** shakamunyi has quit IRC06:58
*** epico has joined #openstack-meeting06:59
*** ndipanov has joined #openstack-meeting07:02
*** AndrewMichalik has quit IRC07:07
*** _nadya_ has quit IRC07:07
*** Fdot has joined #openstack-meeting07:07
*** berendt has joined #openstack-meeting07:09
*** leeantho has quit IRC07:09
*** rakesh_hs has joined #openstack-meeting07:10
*** rakesh_hs2 has quit IRC07:10
*** Hayim2 has joined #openstack-meeting07:12
*** Hayim has quit IRC07:13
*** mpaolino has joined #openstack-meeting07:13
*** hrybacki_ has quit IRC07:14
*** kayaliu_ has quit IRC07:15
*** kayaliu_ has joined #openstack-meeting07:15
*** evgenyf has joined #openstack-meeting07:15
*** jamespage_ has joined #openstack-meeting07:18
*** kayaliu__ has joined #openstack-meeting07:21
*** chandankumar has quit IRC07:21
*** kayaliu_ has quit IRC07:21
*** rakesh_hs2 has joined #openstack-meeting07:23
*** luqas has joined #openstack-meeting07:23
*** chandankumar has joined #openstack-meeting07:23
*** rakesh_hs has quit IRC07:23
*** chandankumar has quit IRC07:23
*** chandankumar has joined #openstack-meeting07:24
*** luqas has quit IRC07:25
*** zhhuabj has quit IRC07:25
*** zhhuabj has joined #openstack-meeting07:25
*** julienvey has joined #openstack-meeting07:25
*** jgallard has joined #openstack-meeting07:27
*** matrohon has joined #openstack-meeting07:29
*** julienvey has quit IRC07:29
*** jjmb has quit IRC07:30
*** hashar has joined #openstack-meeting07:30
*** dbite has quit IRC07:33
*** luqas has joined #openstack-meeting07:35
*** gokrokve has joined #openstack-meeting07:35
*** gokrokve has quit IRC07:40
*** rakesh_hs2 has quit IRC07:42
*** rakesh_hs has joined #openstack-meeting07:44
*** kopparam has joined #openstack-meeting07:44
*** dbite has joined #openstack-meeting07:45
*** rakesh_hs has quit IRC07:46
*** matrohon has quit IRC07:48
*** salv-orlando has joined #openstack-meeting07:49
*** rakesh_hs has joined #openstack-meeting07:49
*** jamespage_ has quit IRC07:49
*** dbite has quit IRC07:50
*** dbite has joined #openstack-meeting07:50
*** JRobinson__ has quit IRC07:50
*** jamespage_ has joined #openstack-meeting07:51
*** AndrewMichalik has joined #openstack-meeting07:52
*** dbite has quit IRC07:53
*** dbite has joined #openstack-meeting07:54
*** shakamunyi has joined #openstack-meeting07:55
*** jamespage_ has quit IRC07:56
*** marun is now known as marun_afk07:56
*** romcheg1 has joined #openstack-meeting07:58
*** phil has joined #openstack-meeting07:59
*** rwsu has quit IRC07:59
*** phil is now known as Guest6895907:59
*** arnaud has quit IRC08:00
*** e0ne has joined #openstack-meeting08:02
*** jamespage_ has joined #openstack-meeting08:03
*** zz_johnthetubagu is now known as johnthetubaguy08:05
*** maybeiamstevemar has quit IRC08:06
*** alexpilotti has joined #openstack-meeting08:07
*** safchain has joined #openstack-meeting08:09
*** shakamunyi has quit IRC08:10
*** julienvey has joined #openstack-meeting08:10
*** moha_hunt has joined #openstack-meeting08:15
*** romcheg1 has quit IRC08:18
*** romcheg1 has joined #openstack-meeting08:18
*** matrohon has joined #openstack-meeting08:21
*** ngoswami has quit IRC08:32
*** acoles_away is now known as acoles08:34
*** moha_hunt has quit IRC08:35
*** gokrokve has joined #openstack-meeting08:35
*** gokrokve has quit IRC08:37
*** e0ne has quit IRC08:37
*** gokrokve has joined #openstack-meeting08:37
*** jgallard has quit IRC08:40
*** jgallard has joined #openstack-meeting08:41
*** gokrokve has quit IRC08:41
*** ndipanov has quit IRC08:46
*** ndipanov has joined #openstack-meeting08:46
*** ngoswami has joined #openstack-meeting08:47
*** matrohon has quit IRC08:50
*** andreykurilin has joined #openstack-meeting08:51
*** _nadya_ has joined #openstack-meeting08:53
*** e0ne has joined #openstack-meeting08:53
*** igordcard has joined #openstack-meeting08:57
*** salv-orlando has quit IRC08:58
*** jamespage_ has quit IRC09:04
*** jamespage_ has joined #openstack-meeting09:05
*** doron_afk is now known as doron09:08
*** jlibosva has joined #openstack-meeting09:11
*** Longgeek has quit IRC09:14
*** ramishra_ has quit IRC09:15
*** ramishra has joined #openstack-meeting09:15
*** oomichi has quit IRC09:16
*** toan-tran has joined #openstack-meeting09:16
*** ramishra has quit IRC09:20
*** Longgeek has joined #openstack-meeting09:22
*** e0ne has quit IRC09:25
*** lvh has quit IRC09:26
*** lvh has joined #openstack-meeting09:27
*** evgenyf has quit IRC09:28
*** berendt has quit IRC09:29
*** e0ne has joined #openstack-meeting09:29
*** baohua has quit IRC09:30
*** gokrokve has joined #openstack-meeting09:36
*** dbite_ has joined #openstack-meeting09:38
*** dbite has quit IRC09:38
*** dbite has joined #openstack-meeting09:38
*** matrohon has joined #openstack-meeting09:39
*** doron is now known as doron_afk09:42
*** gokrokve has quit IRC09:43
*** enikanorov has joined #openstack-meeting09:44
*** evgenyf has joined #openstack-meeting09:46
*** lvh has quit IRC09:47
*** lvh has joined #openstack-meeting09:47
*** shengjiemin has quit IRC09:48
*** pblaho is now known as pblaho|lunch09:53
*** lvh has quit IRC09:53
*** lvh has joined #openstack-meeting09:53
*** yingjun has quit IRC09:57
*** shakamunyi has joined #openstack-meeting09:57
*** ramishra has joined #openstack-meeting09:58
*** shakamunyi has quit IRC10:01
*** idegtiarov_ has quit IRC10:01
*** shengjiemin has joined #openstack-meeting10:01
*** flaper87|afk is now known as flaper8710:01
*** idegtiarov has joined #openstack-meeting10:02
*** idegtiarov has left #openstack-meeting10:02
*** enikanorov_ has quit IRC10:04
*** enikanorov_ has joined #openstack-meeting10:05
*** yamamoto_ has quit IRC10:08
*** jgallard has quit IRC10:09
*** Guest68959 has quit IRC10:09
*** phil_ has joined #openstack-meeting10:11
*** flaper87 is now known as flaper87|afk10:16
*** e0ne has quit IRC10:18
*** enikanorov__ has joined #openstack-meeting10:21
*** Poornima has quit IRC10:21
*** yamahata has quit IRC10:21
*** enikanorov has quit IRC10:22
*** zhhuabj has quit IRC10:27
*** yamamoto has joined #openstack-meeting10:27
*** zhhuabj has joined #openstack-meeting10:28
*** Hayim2 has quit IRC10:28
*** Hayim has joined #openstack-meeting10:28
*** Hayim2 has joined #openstack-meeting10:34
*** epico has quit IRC10:35
*** Hayim has quit IRC10:35
*** gokrokve has joined #openstack-meeting10:35
*** jamespage_ has quit IRC10:36
*** weshay has joined #openstack-meeting10:37
*** gokrokve has quit IRC10:40
*** Longgeek has quit IRC10:41
*** gongysh has quit IRC10:42
*** Longgeek has joined #openstack-meeting10:42
*** chandankumar has quit IRC10:42
*** Longgeek has quit IRC10:44
*** Longgeek has joined #openstack-meeting10:46
*** hashar is now known as hasharEat10:51
*** Azher has quit IRC10:57
*** pblaho|lunch is now known as pblaho10:58
*** chandankumar has joined #openstack-meeting11:00
*** e0ne has joined #openstack-meeting11:03
*** nosnos has quit IRC11:10
*** salv-orlando has joined #openstack-meeting11:11
*** amotoki_ has quit IRC11:11
*** oanufriev has quit IRC11:12
*** flaviof is now known as flaviof_zzz11:13
*** yaguang has quit IRC11:16
*** jamespage_ has joined #openstack-meeting11:18
*** e0ne has quit IRC11:21
*** e0ne has joined #openstack-meeting11:22
*** rajeshr has quit IRC11:25
*** Hayim2 has quit IRC11:26
*** kopparam has quit IRC11:30
*** kopparam has joined #openstack-meeting11:30
*** jamespage_ has quit IRC11:31
*** jamespage_ has joined #openstack-meeting11:32
*** baoli has joined #openstack-meeting11:32
*** flaper87|afk is now known as flaper8711:33
*** kopparam has quit IRC11:35
*** matiu has quit IRC11:35
*** gokrokve has joined #openstack-meeting11:35
*** jamespage_ has quit IRC11:36
*** jamespage__ has joined #openstack-meeting11:36
*** chandankumar has quit IRC11:37
*** oanufriev has joined #openstack-meeting11:38
*** chandankumar has joined #openstack-meeting11:38
*** berendt has joined #openstack-meeting11:40
*** gokrokve has quit IRC11:40
*** ngoswami has quit IRC11:42
*** kayaliu__ has quit IRC11:42
*** yamamoto has quit IRC11:44
*** e0ne has quit IRC11:44
*** deepakcs has quit IRC11:46
*** vrovachev has joined #openstack-meeting11:47
*** shakamunyi has joined #openstack-meeting11:47
*** matiu has joined #openstack-meeting11:49
*** che-arne has joined #openstack-meeting11:50
*** HenryG_afk has quit IRC11:50
*** yamamoto has joined #openstack-meeting11:51
*** yingjun has joined #openstack-meeting11:52
*** e0ne has joined #openstack-meeting11:53
*** flaper87 is now known as flaper87|afk11:54
*** oanufriev has quit IRC11:55
*** ngoswami has joined #openstack-meeting11:56
*** shakamunyi has quit IRC11:58
*** jamespage_ has joined #openstack-meeting11:59
*** adalbas has joined #openstack-meeting11:59
*** kopparam has joined #openstack-meeting12:01
*** jamespage_ has quit IRC12:01
*** nikunj2512 has quit IRC12:01
*** jamespage__ has quit IRC12:02
*** chandankumar has quit IRC12:02
*** ArxCruz has joined #openstack-meeting12:03
*** kopparam has quit IRC12:05
*** penguinRaider__ has quit IRC12:08
*** banix has joined #openstack-meeting12:09
*** penguinRaider__ has joined #openstack-meeting12:10
*** SridharG has quit IRC12:12
*** dprince has joined #openstack-meeting12:15
*** shankar has quit IRC12:15
*** salv-orlando has quit IRC12:17
*** pdmars has joined #openstack-meeting12:18
*** salv-orlando has joined #openstack-meeting12:19
*** banix has quit IRC12:19
*** yamamoto has quit IRC12:19
*** pdmars has quit IRC12:20
*** yingjun has quit IRC12:20
*** pdmars has joined #openstack-meeting12:21
*** yingjun has joined #openstack-meeting12:21
*** chandankumar has joined #openstack-meeting12:21
*** IanGovett has joined #openstack-meeting12:25
*** yingjun has quit IRC12:25
*** yamamoto has joined #openstack-meeting12:26
*** beagles has joined #openstack-meeting12:27
*** beagles is now known as Guest5007612:27
*** doron_afk is now known as doron12:27
*** Guest50076 is now known as b3nt_pin12:28
*** b3nt_pin is now known as beaglesa12:28
*** beaglesa is now known as b3nt_pin12:28
*** penguinRaider__ has quit IRC12:28
*** penguinRaider__ has joined #openstack-meeting12:29
*** _nadya_ has quit IRC12:31
*** _nadya_ has joined #openstack-meeting12:32
*** aysyd has joined #openstack-meeting12:32
*** luqas has quit IRC12:33
*** colinmcnamara has joined #openstack-meeting12:34
*** flaper87|afk is now known as flaper8712:34
*** gokrokve has joined #openstack-meeting12:35
*** prad has joined #openstack-meeting12:36
*** tongli has joined #openstack-meeting12:36
*** gokrokve has quit IRC12:39
*** SridharG has joined #openstack-meeting12:39
*** cjellick has joined #openstack-meeting12:42
*** miqui has joined #openstack-meeting12:42
*** cjellick has quit IRC12:42
*** igordcard has quit IRC12:43
*** cjellick has joined #openstack-meeting12:43
*** radez_g0n3 is now known as radez12:43
*** cjellick has quit IRC12:44
*** cjellick has joined #openstack-meeting12:44
*** jjmb has joined #openstack-meeting12:45
*** kopparam has joined #openstack-meeting12:47
*** penguinRaider__ has quit IRC12:48
*** penguinRaider__ has joined #openstack-meeting12:49
*** k4n0 has quit IRC12:50
*** kopparam has quit IRC12:50
*** yamamoto has quit IRC12:51
*** kopparam has joined #openstack-meeting12:51
*** berendt has quit IRC12:52
*** kopparam has quit IRC12:55
*** colinmcnamara has quit IRC12:56
*** noslzzp has joined #openstack-meeting12:56
*** trey_h has joined #openstack-meeting12:58
*** penguinRaider__ has quit IRC12:58
*** jecarey has quit IRC12:58
*** penguinRaider__ has joined #openstack-meeting13:00
*** ddieterly has joined #openstack-meeting13:02
*** markmcclain has joined #openstack-meeting13:02
*** yamahata has joined #openstack-meeting13:03
*** jasondotstar has joined #openstack-meeting13:03
*** sarob has quit IRC13:03
*** pblaho has quit IRC13:05
*** pblaho_ has joined #openstack-meeting13:05
*** eankutse has joined #openstack-meeting13:06
*** julim has joined #openstack-meeting13:06
*** ttx has quit IRC13:06
*** vishy has quit IRC13:07
*** insequent has quit IRC13:08
*** dendrobates has quit IRC13:08
*** elrondvega has quit IRC13:08
*** comstud has quit IRC13:09
*** vishy has joined #openstack-meeting13:10
*** radix has quit IRC13:11
*** matty_dubs|gone is now known as matty_dubs13:11
*** stevebaker has quit IRC13:11
*** dtroyer has quit IRC13:12
*** matty_dubs has left #openstack-meeting13:12
*** mgagne has quit IRC13:12
*** dhellmann_ is now known as dhellmann13:12
*** ttx has joined #openstack-meeting13:13
*** ttx has quit IRC13:13
*** ttx has joined #openstack-meeting13:13
*** radix has joined #openstack-meeting13:13
*** mgagne has joined #openstack-meeting13:13
*** dendrobates has joined #openstack-meeting13:13
*** dendrobates has joined #openstack-meeting13:13
*** mgagne is now known as Guest2729513:13
*** comstud has joined #openstack-meeting13:14
*** IanGovett has quit IRC13:14
*** vrovachev has quit IRC13:14
*** jlibosva has quit IRC13:14
*** aleksandr_null has quit IRC13:14
*** alpha_ori has quit IRC13:14
*** rharwood has quit IRC13:14
*** m1dev has quit IRC13:14
*** shanks has quit IRC13:14
*** jaypipes has quit IRC13:14
*** changbl has quit IRC13:14
*** hockeynut has quit IRC13:14
*** mwagner_lap has quit IRC13:14
*** AaronGr has quit IRC13:14
*** johnpur has quit IRC13:14
*** scinawa has quit IRC13:14
*** cody-somerville has quit IRC13:14
*** ItSANgo has quit IRC13:14
*** sdague has quit IRC13:14
*** rodrigods has quit IRC13:14
*** chmouel has quit IRC13:14
*** abramley has quit IRC13:14
*** rainya_ has quit IRC13:14
*** matiu has quit IRC13:14
*** morganfainberg_Z has quit IRC13:14
*** stevebaker has joined #openstack-meeting13:15
*** jgrimm has joined #openstack-meeting13:15
*** dtroyer has joined #openstack-meeting13:15
*** IanGovett has joined #openstack-meeting13:15
*** matiu has joined #openstack-meeting13:15
*** vrovachev has joined #openstack-meeting13:15
*** jlibosva has joined #openstack-meeting13:15
*** aleksandr_null has joined #openstack-meeting13:15
*** alpha_ori has joined #openstack-meeting13:15
*** rharwood has joined #openstack-meeting13:15
*** m1dev has joined #openstack-meeting13:15
*** shanks has joined #openstack-meeting13:15
*** jaypipes has joined #openstack-meeting13:15
*** hockeynut has joined #openstack-meeting13:15
*** mwagner_lap has joined #openstack-meeting13:15
*** AaronGr has joined #openstack-meeting13:15
*** rodrigods has joined #openstack-meeting13:15
*** johnpur has joined #openstack-meeting13:15
*** scinawa has joined #openstack-meeting13:15
*** cody-somerville has joined #openstack-meeting13:15
*** ItSANgo has joined #openstack-meeting13:15
*** sdague has joined #openstack-meeting13:15
*** chmouel has joined #openstack-meeting13:15
*** abramley has joined #openstack-meeting13:15
*** morganfainberg_Z has joined #openstack-meeting13:15
*** rainya_ has joined #openstack-meeting13:15
*** jjmb has quit IRC13:17
*** lbragstad has quit IRC13:18
*** jecarey has joined #openstack-meeting13:18
*** bgmccollum has quit IRC13:18
*** radix has quit IRC13:18
*** radix has joined #openstack-meeting13:19
*** yamamoto has joined #openstack-meeting13:19
*** ttx has quit IRC13:20
*** eranra has joined #openstack-meeting13:20
*** eranra has quit IRC13:21
*** ddieterly has quit IRC13:21
*** vishy has quit IRC13:21
*** ivasev has joined #openstack-meeting13:22
*** jgallard has joined #openstack-meeting13:22
*** SpamapS has quit IRC13:23
*** lbragstad has joined #openstack-meeting13:23
*** radix has quit IRC13:23
*** vishy has joined #openstack-meeting13:23
*** SpamapS has joined #openstack-meeting13:24
*** SpamapS has quit IRC13:24
*** SpamapS has joined #openstack-meeting13:24
*** cyeoh has quit IRC13:24
*** ttx has joined #openstack-meeting13:25
*** ttx has quit IRC13:25
*** ttx has joined #openstack-meeting13:25
*** adam_g has quit IRC13:25
*** balajiiyer has joined #openstack-meeting13:25
*** joesavak has joined #openstack-meeting13:26
*** sarob has joined #openstack-meeting13:26
*** bgmccollum has joined #openstack-meeting13:26
*** kevinconway has joined #openstack-meeting13:26
*** cyeoh has joined #openstack-meeting13:27
*** radix has joined #openstack-meeting13:28
*** che-arne has quit IRC13:29
*** mattgriffin has joined #openstack-meeting13:29
*** balajiiyer has left #openstack-meeting13:29
*** adam_g has joined #openstack-meeting13:29
*** adam_g has quit IRC13:30
*** adam_g has joined #openstack-meeting13:30
*** jckasper__ has quit IRC13:30
*** dhellmann has quit IRC13:32
*** pblaho__ has joined #openstack-meeting13:33
*** dhellmann has joined #openstack-meeting13:33
*** jjmb has joined #openstack-meeting13:33
*** insequent has joined #openstack-meeting13:35
*** gokrokve has joined #openstack-meeting13:35
*** vijendar has joined #openstack-meeting13:35
*** chuck_ has joined #openstack-meeting13:35
*** zul has quit IRC13:36
*** jckasper has joined #openstack-meeting13:36
*** dhellmann has quit IRC13:36
*** mestery is now known as mestery_afk13:36
*** pblaho_ has quit IRC13:37
*** pblaho__ has quit IRC13:37
*** dhellmann has joined #openstack-meeting13:39
*** jungleboyj has quit IRC13:39
*** gokrokve has quit IRC13:40
*** thangp has joined #openstack-meeting13:40
*** luqas has joined #openstack-meeting13:41
*** shakamunyi has joined #openstack-meeting13:42
*** haleyb has joined #openstack-meeting13:42
*** armax has joined #openstack-meeting13:43
*** vkmc has joined #openstack-meeting13:45
*** vkmc has quit IRC13:45
*** vkmc has joined #openstack-meeting13:45
*** temujin has joined #openstack-meeting13:45
*** yeungp has joined #openstack-meeting13:45
*** flaviof_zzz is now known as flaviof13:49
*** otherwiseguy has joined #openstack-meeting13:49
*** shakamunyi has quit IRC13:49
*** gongysh has joined #openstack-meeting13:52
*** neelashah has joined #openstack-meeting13:52
*** neelashah has left #openstack-meeting13:54
*** eharney has joined #openstack-meeting13:56
*** nelsnelson has joined #openstack-meeting13:57
*** flaper87 is now known as flaper87|afk13:57
*** ihrachyshka has joined #openstack-meeting13:58
sc68calwho is ready for some ipv6?13:58
*** romcheg1 has left #openstack-meeting13:58
*** ddieterly has joined #openstack-meeting13:58
*** yamahata has quit IRC13:58
*** neelashah has joined #openstack-meeting13:58
*** yamahata has joined #openstack-meeting13:59
*** neelashah has quit IRC13:59
*** neelashah has joined #openstack-meeting13:59
*** dane_leblanc has joined #openstack-meeting14:00
sc68cal#startmeeting neutron_ipv614:00
openstackMeeting started Tue Aug  5 14:00:45 2014 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_ipv6)"14:00
openstackThe meeting name has been set to 'neutron_ipv6'14:00
baoliHi14:00
sc68calbaoli: hi\14:01
*** jamespage_ has joined #openstack-meeting14:01
*** jamespage_ has quit IRC14:01
sc68cal#info Juno-3 milestone is less than a month away14:02
*** doron is now known as doron_afk14:03
*** Hg_ has joined #openstack-meeting14:04
*** wendar has quit IRC14:04
*** Hg_ is now known as HenryG14:04
*** dendrobates has quit IRC14:04
sc68calLooks like xuhanp isn't on yet14:04
*** ndipanov has quit IRC14:04
HenryGxuhan is on vacation this week14:04
*** wendar has joined #openstack-meeting14:05
sc68calah, ok14:05
*** bgmccollum has quit IRC14:05
*** flaper87|afk is now known as flaper8714:06
sc68calI don't have an agenda for today's meeting, so I'll just turn to open discussion14:06
sc68calWe've done a real great job getting things landed into Juno14:07
HenryGMade some progress on the devstack patch for radvd. I think it should get approved this week.14:07
*** sarob has quit IRC14:07
HenryGThen I can finish up the functional tests14:07
sc68calHenryG: fantastic14:08
baoliyea, a lot of good work in Juno14:08
*** ayoung has joined #openstack-meeting14:08
*** wendar has quit IRC14:08
baoliI'm trying to make progress on the floatingip bug I opened up14:08
*** wendar has joined #openstack-meeting14:08
*** vishy has quit IRC14:09
baoliI'd like to discuss how to tackle it when we have more attendence.14:09
*** matrohon has quit IRC14:09
sc68calbaoli: perhaps a ML post?14:09
baolisc68cal, yea, I can start with that.14:10
*** gokrokve has joined #openstack-meeting14:10
*** dendrobates has joined #openstack-meeting14:10
*** dendrobates has joined #openstack-meeting14:10
*** jckasper has quit IRC14:11
*** yamamoto has quit IRC14:11
*** shakamunyi has joined #openstack-meeting14:11
*** jckasper has joined #openstack-meeting14:11
sc68calOk, cool14:11
*** trey_h has quit IRC14:12
*** bgmccollum has joined #openstack-meeting14:12
*** vijendar has quit IRC14:13
*** vijendar has joined #openstack-meeting14:13
*** trey_h_ has joined #openstack-meeting14:13
*** vijendar has quit IRC14:13
*** vijendar has joined #openstack-meeting14:13
*** trey_h_ has quit IRC14:13
*** trey_h_ has joined #openstack-meeting14:13
*** vishy has joined #openstack-meeting14:13
sc68calDo we have any new BPs to discuss? any new business?14:13
HenryGNot that I am aware of.14:14
baolinot from my side14:14
*** Murali has joined #openstack-meeting14:15
*** HenryG_ has joined #openstack-meeting14:15
*** vivek-ebay has joined #openstack-meeting14:16
*** HenryG has left #openstack-meeting14:16
*** fnaval has joined #openstack-meeting14:16
*** HenryG_ is now known as HenryG14:17
sc68calok, then I'll give everyone back 45 minutes14:17
sc68calI'll be in #openstack-neutron as well as the mailing list, if anything comes up14:18
HenryGthanks, bye14:18
sc68cal#endmeeting14:18
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:18
openstackMeeting ended Tue Aug  5 14:18:20 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-08-05-14.00.html14:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-08-05-14.00.txt14:18
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-08-05-14.00.log.html14:18
*** dane_leblanc has quit IRC14:18
*** mtanino has joined #openstack-meeting14:20
*** matrohon has joined #openstack-meeting14:20
*** gokrokve has quit IRC14:20
*** otherwiseguy has quit IRC14:20
*** gokrokve has joined #openstack-meeting14:21
*** vhoward has joined #openstack-meeting14:21
*** banix has joined #openstack-meeting14:21
*** whenry has joined #openstack-meeting14:22
*** FallenPegasus has joined #openstack-meeting14:24
*** gokrokve has quit IRC14:25
*** jungleboyj has joined #openstack-meeting14:26
*** otherwiseguy has joined #openstack-meeting14:28
*** david-lyle has joined #openstack-meeting14:28
*** jmontemayor has joined #openstack-meeting14:29
*** nikunj2512 has joined #openstack-meeting14:31
*** ramishra has quit IRC14:31
*** ramishra has joined #openstack-meeting14:32
*** shakamunyi has quit IRC14:32
*** jamespage_ has joined #openstack-meeting14:32
*** jamespage_ has quit IRC14:33
*** esheffield has joined #openstack-meeting14:33
*** rakesh_hs has quit IRC14:34
*** ramishra has quit IRC14:34
*** ramishra has joined #openstack-meeting14:34
*** david-ly_ has joined #openstack-meeting14:34
*** david-ly_ is now known as david-lyle_14:35
*** jgrimm has quit IRC14:36
*** nikunj2512 has quit IRC14:36
*** ramishra has quit IRC14:37
*** hrybacki has joined #openstack-meeting14:37
*** david-lyle has quit IRC14:38
*** gongysh has quit IRC14:39
*** gongysh has joined #openstack-meeting14:40
*** Longgeek has quit IRC14:41
*** gongysh has quit IRC14:45
*** _nadya_ has quit IRC14:45
*** hasharEat has quit IRC14:45
*** david-lyle_ is now known as david-lyle14:48
*** ramashri has joined #openstack-meeting14:49
*** doron_afk is now known as doron14:50
*** doron is now known as doron_afk14:50
*** emagana has joined #openstack-meeting14:52
*** Poornima has joined #openstack-meeting14:54
*** chuck_ is now known as zul14:54
*** ramashri has quit IRC14:54
*** zul has quit IRC14:54
*** zul has joined #openstack-meeting14:54
*** ramashri has joined #openstack-meeting14:55
*** ildikov has quit IRC14:55
*** markmcclain1 has joined #openstack-meeting14:57
*** markmcclain has quit IRC14:57
*** n0ano has joined #openstack-meeting14:58
*** emagana has quit IRC14:59
*** vivek-ebay has quit IRC14:59
*** marun_afk is now known as marun14:59
*** mspreitz has joined #openstack-meeting14:59
*** emagana has joined #openstack-meeting14:59
*** ildikov has joined #openstack-meeting15:00
bauzastic tac toc15:00
n0anobauzas, you're too eager :-)15:00
n0ano#startmeeting gantt15:00
openstackMeeting started Tue Aug  5 15:00:46 2014 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: gantt)"15:00
openstackThe meeting name has been set to 'gantt'15:00
*** emagana has quit IRC15:00
*** emagana_ has joined #openstack-meeting15:00
bauzaswell, timezone difference maybe ^^15:00
n0anoAnyone here to talk about the scheduler?15:00
bauzas\o15:01
n0anobauzas, BTW, according to my timestamp, I started exactly at 1500 :-)15:01
*** carl_baldwin has joined #openstack-meeting15:01
bauzas(17:00:46) n0ano: #startmeeting gantt15:01
mspreitzmoi15:01
bauzasbonjour15:02
bauzas:)15:02
n0anojeez, 46 seconds, and I thought I was compulsive :-)15:02
mspreitzthis is the scheduler group, man15:02
n0anomspreitz, good point15:03
*** eankutse1 has joined #openstack-meeting15:03
*** Yathi has joined #openstack-meeting15:03
n0anoOK, in a vain attempt to get serious, let's start15:03
bauzasyeah, you have 60 secs accepted15:03
*** yeungp has quit IRC15:03
n0ano#topic mid-cycle meetup recap\15:03
*** openstack changes topic to "mid-cycle meetup recap\ (Meeting topic: gantt)"15:03
*** jjmb has quit IRC15:03
*** eankutse has quit IRC15:03
*** Leonr has joined #openstack-meeting15:03
n0anodetailed log at the launchpad page\15:04
n0ano#link https://etherpad.openstack.org/p/juno-nova-mid-cycle-meetup15:04
bauzassummary ?15:04
bauzas:)15:04
*** yamahata has quit IRC15:04
n0anoTues morning was the discussion  about gantt15:04
n0anomy take was...15:04
n0ano1)  scheduler lib code being approved...15:05
n0ano2) DB isolation spec exception approved...15:05
bauzas\o/15:05
Yathigreat job guys!15:05
n0ano3)  Jay wants to move resource claims out of compute and into scheduler, need a specific proposal from him before we know if we should gate the split on that...15:06
bauzaswell, my understand was a bit less enthusiastic :)15:06
jaypipesn0ano: yeah, wiorking with yjiang on that15:06
*** gokrokve has joined #openstack-meeting15:06
bauzasscheduler-lib and isolate-sched-db are on their way, that's it :)15:06
n0ano4) n0ano needs to ask on the mailing list if other projects are good about splitting out gantt (neutron said yes at the meetup, containers enthusiastic about it)...15:06
*** chandankumar has quit IRC15:07
*** _nadya_ has joined #openstack-meeting15:07
n0anoI think those are the big points that I took away, bauzas & jaypipes you were there, anything to add?15:07
jaypipesn0ano: nope, that's a good summary15:07
bauzasI wish I would have been there, but Graham Bell helped me a lot15:07
jaypipesheh15:08
bauzasnah, I'm OK with the summary, as I said, work is on-going, more to investigate for the RT move15:08
Yathiwe need to talk to Cinder folks about their enthusiasm for gantt and unified scheduling etc15:08
n0anojaypipes, you're working with yjiang on the resource stuff, do you know when you'll have a BP posted?15:08
n0anobauzas, Yathi +115:09
*** elrondvega has joined #openstack-meeting15:09
jaypipesn0ano: chatting with him this afternoon about it.15:10
n0anojaypipes, so soon, hopefully, that's all we can ask for15:10
jaypipesn0ano: yes15:10
bauzasmaybe an etherpad can help you ?15:10
* bauzas loves the etherpads, eh15:10
jaypipesbauzas: yeah, will create one and fill some stuff in from our conversation15:10
Yathijaypipes: I would love to be part of that discussion15:11
bauzassure, my point was just to overview the basic things before having a spec to review :)15:11
n0anobauzas, +1, I like small groups to do the work, we can review what you come up with15:11
jaypipesYathi: no. no discussion for you! one year.15:11
jaypipesYathi: j/k :) will ping you when I find yj later today15:12
Yathi:)15:12
*** yamamoto has joined #openstack-meeting15:12
Yathijaypipes: sounds good15:12
*** Fdot has quit IRC15:12
*** shakamunyi has joined #openstack-meeting15:12
n0anojaypipes, remarkably good impression of the Soup Nazi on IRC :-)15:12
n0anoanything else to say about the meetup?15:13
jaypipesn0ano: :)15:13
Yathin0ano: other thing to add - was another Soup Nazi treatment for solver scheduler stuff at the mid-cycle meetup :)15:13
YathiSolver Scheduler discussion and spec pushed for Kilo - until after Gantt15:13
* mspreitz wonders what Soup Nazi is15:13
*** yamamoto has quit IRC15:14
n0anomspreitz, Seinfield reference, American pop culture strikes again15:14
*** yamamoto has joined #openstack-meeting15:14
*** thedodd has joined #openstack-meeting15:14
n0anoYathi, yeah, sorry about that, but it's a big change for late in the cycle, you'll have to push early in Juno I think15:14
bauzas+115:15
n0anoanyway, moving on15:15
*** FallenPegasus has quit IRC15:15
Yathin0ano: +1 yup.. will be more aggressive15:15
n0anoYathi, the term is `assertive`, not aggressive :-)15:16
bauzas:)15:16
n0ano#topic forklift effort15:16
*** openstack changes topic to "forklift effort (Meeting topic: gantt)"15:16
bauzas\o15:16
Yathi:) OK!15:16
bauzassooooo15:16
n0anoreally, it's finalizing the two outstanding BPs15:16
bauzasscheduler-lib is waiting reviews15:16
n0anoscheduler lib is waiting for reviews, do we need to get assertive on that?15:16
bauzaswell, tbh, we're having a reviewers bandwidth issue15:17
bauzasjohnthetubaguy gave previously a +2 on it, but it needed rebase due to Extensible RT merge15:17
bauzasunfortunately, ERT was reverted, so I reverted also my patch15:18
johnthetubaguybauzas: RT got reverted though right?15:18
n0anoyeah, I'm not too concerned, I'll be at the nova meeting this week, if they talk about review patches I'll bring this one up15:18
bauzasjohnthetubaguy: yeahn, situation went back to normal15:18
johnthetubaguybauzas: cool, thanks15:18
*** che-arne has joined #openstack-meeting15:18
*** yamamoto has quit IRC15:18
bauzasjohnthetubaguy: ie. both ERT patch and sched-lib patch went back to their previous states15:18
*** ihrachyshka has quit IRC15:19
bauzasso, if ERT goes merged before sched-lib, the latter will require a rebase15:19
n0anobauzas, and vice versa15:19
bauzasn0ano: yeah, life is sometimes hard15:20
bauzas:)15:20
*** plomakin has quit IRC15:20
*** skraynev has quit IRC15:20
*** ilyashakhat_ has quit IRC15:20
*** vrovachev has quit IRC15:20
n0anowe'll see who wins the race, hopefully you15:20
bauzasatm, ERT is in a winning position15:20
bauzasone +2 vs. zero15:20
*** skraynev has joined #openstack-meeting15:20
*** ilyashakhat has joined #openstack-meeting15:20
n0anowe'll see, the race is not over15:21
n0anoanyway, I think scheuler lib is well in hand15:21
bauzascorrect15:21
*** vhoward has left #openstack-meeting15:21
n0anofor DB isolation, we have one +2 on the spec, I think we need another one right?15:21
*** plomakin has joined #openstack-meeting15:21
bauzasisolate-sched-db is having one +215:21
bauzasyeah, need to ask ndipanov15:21
bauzasas he's the 2nd sponsor15:21
bauzasif you all look at https://review.openstack.org/89893, you'll see there are 3 workitems15:22
n0anoI would feel comfortable starting the coding given that it's unlikely the spec will change dramatically between now and final approve, what do you think bauzas15:22
bauzas#1 is the instance group thing, a patch is provided : https://review.openstack.org/#/c/110043/15:23
bauzas#2 is aggregates thing15:23
bauzas#3 is instances thing, I'm on my way for writing a patch on this15:23
*** nshaikh has quit IRC15:23
bauzasshould be done by today or tomorrow15:23
bauzasso, #2 could be done based on #315:23
bauzasn0ano: you expressed interest in coding #2 ?15:24
n0anoI believe that tian is willing to do #2, I'll ping him to make sure he's up for that15:24
bauzasn0ano: sure15:24
bauzasn0ano: I can propose you and tian to wait for patch #315:24
*** Hayim has joined #openstack-meeting15:24
bauzasn0ano: so we'll propose an identical way15:25
bauzasn0ano: should not require a dependency in between #2 and #3 tho15:25
n0anohe's in Shanghai so he won't be able to look at it until tomorrow so basing on #3 should be fine15:25
bauzasas I'm basing my work on ERT15:25
*** doddstack has joined #openstack-meeting15:25
bauzasI'm creating another resource for instances15:25
bauzasand another one for instance's flavors15:25
*** lcheng has joined #openstack-meeting15:26
*** thedodd has quit IRC15:26
*** prad has quit IRC15:26
bauzasthat's it for me15:26
n0anosounds good, we'll see what you come up with for #3 and go from there15:27
bauzasok cool15:27
n0anoI think we're good on the forklift status so moving on15:27
bauzas+115:27
n0ano#topic opens15:28
*** openstack changes topic to "opens (Meeting topic: gantt)"15:28
Yathibauzas: if you want me to take a task item, let me know.. I might have some bandwidth15:28
bauzasYathi: well, atm, we should be good15:28
n0anoYathi, I think we're covered but we'll keep you in mind15:28
*** shakamunyi has quit IRC15:28
bauzasYathi: that's more likely a rewiewing bandwidth that we need15:28
n0anoanything new anyone wants to raise today?15:29
bauzasyep15:29
Yathibauzas: yup I am already reviewing all these gantt patches at the moment..15:29
bauzasdon't know if sahid is there ?15:29
*** eankutse1 has quit IRC15:29
*** eankutse has joined #openstack-meeting15:29
bauzasthere is a Juno BP that has been accepted15:30
bauzaslemme find it15:30
*** med_ has joined #openstack-meeting15:31
*** med_ has quit IRC15:31
*** med_ has joined #openstack-meeting15:31
*** med_ is now known as Guest2624015:31
bauzasgotcha15:32
bauzashttps://review.openstack.org/#/c/85399/15:32
* n0ano that BP must be well hidden15:32
*** e0ne has quit IRC15:32
bauzasyeah, Gerrit searches suck15:32
*** yyywu has joined #openstack-meeting15:32
*** jgrimm has joined #openstack-meeting15:32
bauzasthis BP is validated for Juno and possibly impacting isolate-sched-db15:32
*** e0ne has joined #openstack-meeting15:32
bauzasso, that's more likely a FYI15:32
bauzasI'm on my way to sort this out with sahid15:33
*** eankutse1 has joined #openstack-meeting15:33
n0anoI missed this, I'll have to review the spec15:33
bauzasnah, the spec is merged15:33
bauzas:D15:33
mspreitzwow, that BP is news to me... title makes it look like toes in deep water15:33
n0anopersonal review, not formal voting :-)15:33
*** ngoswami has quit IRC15:33
* mspreitz needs to read and think ab out that spec15:33
bauzasanyway, as I said, we just need to sync our work15:33
n0anomspreitz, what he said15:33
*** eankutse has quit IRC15:34
n0anobauzas, well, if you're in contact with sahid that's about all we can do right now15:34
bauzascorrect, as I said, it was a FYI15:34
bauzasthat's it for me15:34
*** skraynev has quit IRC15:35
*** enikanorov_ has quit IRC15:35
*** ilyashakhat has quit IRC15:35
*** tnurlygayanov has quit IRC15:35
*** plomakin has quit IRC15:35
n0anocool, anything else?15:35
*** enikanorov has joined #openstack-meeting15:35
*** ilyashakhat has joined #openstack-meeting15:35
*** tnurlygayanov has joined #openstack-meeting15:35
*** skraynev has joined #openstack-meeting15:35
n0anoOK, hearing silence, I'll close and we can all go off and do some real work :-)15:35
n0anotnx everyone15:35
*** plomakin has joined #openstack-meeting15:35
n0ano#endmeeting15:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:36
openstackMeeting ended Tue Aug  5 15:36:06 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-08-05-15.00.html15:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-08-05-15.00.txt15:36
openstackLog:            http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-08-05-15.00.log.html15:36
bauzasthanks :)15:38
bauzasn0ano: and thanks again for the bridge setup :-)15:38
*** jlanoux has joined #openstack-meeting15:39
*** ajiang has joined #openstack-meeting15:39
*** ramishra has joined #openstack-meeting15:40
Yathibauzas: any new patches you write, can you please add me as a reviewer, I will know that way the work items for review15:41
bauzasYathi: sure15:41
Yathibauzas: the more I review, I will be able to push patches for gantt and ease your workload too :)15:41
bauzas:)15:41
Yathibauzas: my hands are itching to write code for Gantt :)15:41
Yathibauzas: I mean.. desperately waiting to write scheduler code.. being assertive :)15:42
Yathilike how n0ano pointed out!15:42
bauzas:)15:42
*** marun has quit IRC15:43
Yathibauzas: will catch you later.. signing off now.. bye15:43
bauzasYathi: sure15:43
*** Yathi has quit IRC15:43
*** mspreitz has quit IRC15:44
*** reed has joined #openstack-meeting15:44
*** ramashri has quit IRC15:44
*** marun has joined #openstack-meeting15:45
*** baoli has quit IRC15:45
*** amotoki has quit IRC15:47
uberjmeta-q8315:51
*** doron_afk is now known as doron15:51
*** dsetia has joined #openstack-meeting15:54
*** rmoe has quit IRC15:54
*** gokrokve_ has joined #openstack-meeting15:55
*** kevinconway has quit IRC15:55
*** mtanino has quit IRC15:55
*** marcoemorais has joined #openstack-meeting15:56
*** noslzzp has quit IRC15:56
*** pballand has joined #openstack-meeting15:56
*** noslzzp has joined #openstack-meeting15:57
*** kevinconway has joined #openstack-meeting15:58
*** gokrokve has quit IRC15:58
*** matrohon has quit IRC15:59
*** arnaud has joined #openstack-meeting16:00
primeministerp#startmeeting hyper-v16:00
openstackMeeting started Tue Aug  5 16:00:43 2014 UTC and is due to finish in 60 minutes.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: hyper-v)"16:00
openstackThe meeting name has been set to 'hyper_v'16:00
primeministerpHi everyone16:00
*** virmitio has joined #openstack-meeting16:00
primeministerpvirmitio: hi tim16:01
*** matiu has quit IRC16:01
*** ociuhandu has joined #openstack-meeting16:01
primeministerpociuhandu: hi tavi16:01
ociuhanduhi all16:01
*** ivasev has quit IRC16:01
ociuhanduprimeministerp: hello16:01
*** e0ne has quit IRC16:01
primeministerpluis_fdez: hi luis16:01
*** hashar has joined #openstack-meeting16:01
*** marcoemorais has quit IRC16:02
*** ivasev has joined #openstack-meeting16:02
*** toan-tran has quit IRC16:02
alexpilottihi there16:02
*** fnaval has quit IRC16:02
primeministerpalexpilotti: hey there16:02
*** marcoemorais has joined #openstack-meeting16:02
primeministerpquite the quorum today16:02
primeministerpno vijay16:02
*** jlanoux has quit IRC16:02
primeministerpso some updates on active devel work16:02
*** vermarah_ has joined #openstack-meeting16:02
*** vermarah has joined #openstack-meeting16:02
primeministerp#topic cinder smb3 support16:03
*** openstack changes topic to "cinder smb3 support (Meeting topic: hyper-v)"16:03
primeministerpalexpilotti: you're up16:03
*** Slower has joined #openstack-meeting16:03
*** mtanino has joined #openstack-meeting16:03
primeministerpalexpilotti: smb3 status?16:03
alexpilottisure16:03
alexpilottiso as usual we’re at full steam here16:03
primeministerpalexpilotti: as expected16:04
*** zhhuabj has quit IRC16:04
alexpilottion teh CInder side we already committed the SMB patches since a while16:04
alexpilottifetching them 1sec16:04
primeministerpalexpilotti: manilla as well?16:04
alexpilottiin case some additional volunteers would fancy a review ;-)16:04
*** jmontemayor has quit IRC16:05
*** evgenyf has quit IRC16:05
alexpilotti#link https://review.openstack.org/#/c/106046/16:05
alexpilotti#link https://review.openstack.org/#/c/106057/16:05
*** rmoe has joined #openstack-meeting16:05
primeministerpalexpilotti: awesome thx16:06
*** Murali has quit IRC16:06
alexpilottiso we’ve been asked to rebase teh SMB work on top of another patch16:06
alexpilottinasically an NFS refactoring that reduces some common code16:06
alexpilottiand we have to wait  for that patch to merge before ours are taken into considerations16:06
*** fnaval has joined #openstack-meeting16:06
alexpilottiI’ve been assured that this should happen soon16:07
primeministerpok16:07
*** phil_h has quit IRC16:07
primeministerpon that note16:07
alexpilottiCinder anyway is not Nova, so usually there are no review bandwidth issues that affect us16:07
primeministerp#topic cinder ci iscsi/smb316:07
*** openstack changes topic to "cinder ci iscsi/smb3 (Meeting topic: hyper-v)"16:07
primeministerpociuhandu: where's the automation stand for the cinder tests16:08
ociuhanduprimeministerp: we have the image prepared16:08
ociuhanduprimeministerp: and the scripts16:08
*** phil_h has joined #openstack-meeting16:08
ociuhanduprimeministerp: we’re waiting to clear out the licensing issues16:08
primeministerpociuhandu: which16:08
primeministerpociuhandu: I'll deal w/ that16:09
primeministerpnow16:09
ociuhanduwindows storage server license16:09
primeministerpin the lab we currently should have any issue16:09
primeministerpi have keys16:09
primeministerpif to be used16:09
primeministerper to be used16:09
primeministerpon a bigger scale16:09
primeministerpif we need a kms16:09
*** Murali_ has joined #openstack-meeting16:09
primeministerpor something else16:09
primeministerpI can look into that today16:10
primeministerpand get it resolved today16:10
ociuhanduprimeministerp: alsoi take into account that the license key will be activated for each test16:10
primeministerpociuhandu: fair enough16:10
*** vivek-ebay has joined #openstack-meeting16:10
ociuhanduprimeministerp: that can be an issue we were waiting for an answer on (and also the actual license to be used)16:10
primeministerpociuhandu: can you send me an email with the explict requirements16:10
primeministerpociuhandu: needed for the license and any other reqs16:11
ociuhanduas far as i know the key might have issues if it is being activated more than a certain number of times16:11
primeministerpociuhandu: i'll push some buttens today16:11
ociuhanduprimeministerp: sure thing16:11
primeministerpociuhandu: thx16:11
*** vivek-ebay has quit IRC16:11
primeministerpociuhandu: also can we use the same image for both?16:11
*** vivek-ebay has joined #openstack-meeting16:11
*** hemna_ is now known as hemna16:12
ociuhanduprimeministerp: both what?16:12
*** jrolson has joined #openstack-meeting16:12
primeministerpociuhandu: smb and iscsi16:12
ociuhanduprimeministerp: iscsi and smb?16:12
*** yamamoto has joined #openstack-meeting16:12
primeministerpyes16:12
ociuhanduprimeministerp: yes we can16:12
primeministerpperfecto16:12
primeministerpociuhandu: also can we deploy on iron using ironic yet?16:12
primeministerp;)16:13
*** doron is now known as doron_afk16:13
*** moha_hunt has joined #openstack-meeting16:13
ociuhanduprimeministerp: we also have a few nodes set aside for these tests16:13
primeministerpociuhandu: which?16:13
*** stevemar has joined #openstack-meeting16:13
ociuhandunot iron but cinder CI16:13
primeministerpociuhandu: can we use iron?16:13
ociuhanduso we will not mix the kvm nodes for cinder with the ones for nova and neutron, for the moment16:13
primeministerpi.e. how much ram can we squeeze in16:14
ociuhanduprimeministerp: at the moment we are using kvm, we can discuss about iron later on16:14
ociuhanduwell, from our tests we can squeeze the windows image in about 2 to 3 Gb16:14
primeministerpociuhandu: given our ram issues iron would be better16:14
primeministerpociuhandu: and we can hard set those to pxe16:15
primeministerpociuhandu: if we wanted to use ironic16:15
ociuhanduprimeministerp: given the existing hardware I would not reinstall them so often16:15
primeministerpociuhandu: well neither would i but it would give us a cleaning cycle16:16
primeministerp;)16:16
ociuhanduand also I would not rely on one windows per node as if that node fails we have bigger problems16:16
ociuhanduthe nodes we have are with 32 Gb ram16:16
ociuhanduso quite a lot of instances per node16:16
primeministerpociuhandu: we can probably deal w/ numbers16:16
primeministerpociuhandu: i can't give you ram until RR is done16:16
*** banix has quit IRC16:16
primeministerpociuhandu: anyway16:16
*** yamamoto has quit IRC16:17
primeministerpalexpilotti: nova?16:17
*** openstackstatus has quit IRC16:17
*** openstack has joined #openstack-meeting16:17
*** ChanServ sets mode: +o openstack16:17
*** jmontemayor has joined #openstack-meeting16:17
alexpilottiout of the BPs that got approved16:17
*** eghobo has joined #openstack-meeting16:17
alexpilottiall the code is up and ready16:18
*** marun has quit IRC16:18
alexpilottiand one BP merged already16:18
*** openstackstatus has joined #openstack-meeting16:18
*** ChanServ sets mode: +v openstackstatus16:18
alexpilottispceifially:16:18
alexpilotti# https://review.openstack.org/#/c/108662/16:18
*** marun has joined #openstack-meeting16:18
alexpilotti# https://review.openstack.org/#/c/111291/ (this one needs a rebase)16:18
primeministerpalexpilotti: ok16:19
alexpilotti#link https://review.openstack.org/#/c/106717/16:19
alexpilottithese are the patches for approved BPs waiting to be merged16:19
alexpilottithere’s quite a lof of additional stuff that will be proposed the day in which K opens16:20
primeministerpok16:20
*** rudrarugge has joined #openstack-meeting16:20
alexpilottithe SMB Nova part in particular16:20
alexpilottias anyway it cannot be reviewed until it merges in Cinder, which makes sense16:20
primeministerpalexpilotti: btw we didn't discuss the manilla part16:20
*** ramashri has joined #openstack-meeting16:20
alexpilottiyep16:20
alexpilottimanilla is our list for K16:21
primeministerp#topic manilla16:21
primeministerpalexpilotti: are the blueprints and such in place for that work as well16:21
alexpilottith eoriginal plan was to get stuff in Cinder and Nova for SMB during J16:21
*** rudrarugge has quit IRC16:21
alexpilottiand discuss Manilla in K16:21
alexpilottibut of course plans need to revised :-)16:21
primeministerpok16:22
primeministerpthat's good enough for me now16:22
*** rudrarugge has joined #openstack-meeting16:22
primeministerpanything else to note for nova?16:22
alexpilottion the backports side16:22
alexpilottiwe had backports waiting review for more tha 120 days16:23
alexpilottiafter raising the issue, things got faster16:23
alexpilottiwe got around 10 patches merged for Havana16:23
alexpilottiand 1 for Icehouse16:23
primeministerpgood16:23
primeministerpthanks for catching that16:24
alexpilottinp16:24
alexpilottibeside that we have a few bugs in the works16:24
primeministerp#topic olso/service bus16:24
alexpilottiso16:24
alexpilottiwe have a BP spec up for review16:24
primeministerpgreat16:24
alexpilotti]to add an RPC backend for the Windows Server Service Bus16:25
primeministerpalexpilotti: do you have links?16:25
alexpilottibasically the component used on Azure is also available on premise16:25
*** Hayim has quit IRC16:25
alexpilotti#link https://review.openstack.org/#/c/109863/16:25
*** mtanino has quit IRC16:26
alexpilottiin a nutshell, this allows to replace RabbitMQ or Qpid with the servcie bus16:26
primeministerpthis is awesome16:26
alexpilottiwhich is an important use case for WIndows based scenarios16:26
primeministerpyep16:26
alexpilottiwaiting for review ATM16:26
*** rudrarugge has quit IRC16:26
alexpilottias soon as we have green light we commit the code16:26
primeministerpgreat16:26
primeministerpalexpilotti: the code is currently complete?16:27
alexpilottiunder dev16:27
primeministerpi knew that, how far out?16:27
alexpilottiby the time the specs are approved we’ll publish it unless there are issues16:27
alexpilotti1 week of work16:27
primeministerpalexpilotti: great16:28
alexpilottiATM we’re waiting on it giving priority to the CInder and Nova bits16:28
primeministerpalexpilotti: those are definately more important atm16:28
primeministerpalexpilotti: anthing else?16:28
*** Hayim has joined #openstack-meeting16:28
primeministerpalexpilotti: needing a specifc topic16:28
alexpilottishoudl we discuss OVS?16:29
primeministerpo yes16:29
primeministerp#topic ovs on hyperv16:29
alexpilottiwe are currently merging our port with VMWAre’s work16:29
alexpilottieverything is documented on the OVS ML16:29
alexpilottiissues are available at #link https://github.com/openvswitch/ovs-issues/issues16:30
alexpilottiand every Tue, 1 hr after this meeting we have a meeting on #openvswitch16:30
*** shang has joined #openstack-meeting16:30
*** doddstack has quit IRC16:30
alexpilottito discuss the various tasks16:30
alexpilottiit’s atechnical meeting, mostly related to kernel development16:31
alexpilottibut it’s also a good palce to discuss about strategy and features16:31
*** gangil has joined #openstack-meeting16:31
alexpilottifrom a higher level perspective16:31
primeministerpvery important part of the whole process16:31
alexpilottiso, things are rolling pretty well to say so16:32
primeministerpso we're on target for good things in Paris16:32
alexpilottiah Paris!16:32
alexpilottiplease vote for our sessions!16:32
alexpilottione sec, fetching the links16:32
*** prad has joined #openstack-meeting16:32
*** leeantho has joined #openstack-meeting16:33
alexpilottiOVS session, presented by Justin from VMWare and myself: #link https://www.openstack.org/vote-paris/Presentation/new-platforms-with-open-vswitch-docker-hyper-v-and-intel-dpdk16:33
alexpilottiWindows Heat and Juju workshop: #link https://www.openstack.org/vote-paris/Presentation/deploying-windows-workloads-with-heat-and-juju16:34
alexpilotticompetition for getting a session spot is becoming very fierce, so every vote counts! :-)16:34
alexpilottiBTW we’ll have all the Cloudbase ATCs in Paris16:35
primeministerp#link http://www.openstack.org/vote-paris/Presentation/enabling-openstack-for-multi-hypervisor-support16:35
alexpilottiaround 20 people16:35
primeministerpalexpilotti: great16:35
primeministerpalexpilotti: it will be good to meet everyone16:35
alexpilottiso a great opportunity to meet and discuss features and implementations16:35
primeministerpI'm not entirely sure who's going from our side16:35
*** hashar has quit IRC16:35
primeministerpI know of at least 416:35
primeministerpand that's not on my team16:36
primeministerpok16:36
primeministerpon that note16:36
primeministerpI don't have anything else16:36
primeministerpalexpilotti: ociuhandu virmitio luis_fdez ?16:36
alexpilottime neither16:36
primeministerpif not i'm ending16:36
primeministerp#endmeeting16:36
alexpilottitx folks!16:36
alexpilottiprimeministerp luis_fdez see you!16:37
ociuhanduthanks guys, bye16:37
primeministerp#endmeeting16:37
*** MaxV has quit IRC16:39
*** safchain has quit IRC16:39
*** pkoniszewski has quit IRC16:39
*** jrolson has quit IRC16:40
*** chuckC has quit IRC16:41
*** samcdona has quit IRC16:41
*** vivek-ebay has quit IRC16:42
*** shashankhegde has joined #openstack-meeting16:42
*** rwsu has joined #openstack-meeting16:43
*** vivek-ebay has joined #openstack-meeting16:43
*** ddieterly has quit IRC16:45
*** tbarron has quit IRC16:45
*** rajeshr has joined #openstack-meeting16:46
*** gyee has joined #openstack-meeting16:48
*** emagana_ has quit IRC16:49
*** Murali_ has quit IRC16:49
*** emagana has joined #openstack-meeting16:49
*** penguinRaider__ has quit IRC16:49
*** sarob has joined #openstack-meeting16:50
*** luqas has quit IRC16:51
*** ivar-lazzaro has joined #openstack-meeting16:51
*** flaper87 is now known as flaper87|afk16:51
*** fawadkhaliq has joined #openstack-meeting16:52
*** gyee has quit IRC16:52
*** emagana_ has joined #openstack-meeting16:52
*** atiwari has joined #openstack-meeting16:53
*** marcoemorais has quit IRC16:53
*** emagana has quit IRC16:53
*** marcoemorais has joined #openstack-meeting16:53
*** ajiang has quit IRC16:53
*** morganfainberg_Z is now known as morganfainberg16:55
*** fawadkhaliq has quit IRC16:55
*** gyee has joined #openstack-meeting16:55
*** bdpayne has joined #openstack-meeting16:56
*** penguinRaider__ has joined #openstack-meeting16:57
*** salv-orlando has quit IRC16:57
*** shashankhegde has quit IRC16:58
*** berendt has joined #openstack-meeting16:58
*** ociuhandu has left #openstack-meeting16:59
*** kevinconway has quit IRC16:59
*** arnaud has quit IRC17:00
*** rediskin has joined #openstack-meeting17:01
*** jgallard has quit IRC17:01
*** emagana_ has quit IRC17:02
*** phil_ has quit IRC17:03
*** emagana has joined #openstack-meeting17:03
*** jjmb has joined #openstack-meeting17:05
*** rajeshr has quit IRC17:06
*** ArxCruz has quit IRC17:06
*** emagana has quit IRC17:07
*** emagana has joined #openstack-meeting17:08
*** kragniz_ has quit IRC17:10
*** mspreitz has joined #openstack-meeting17:11
*** samcdona has joined #openstack-meeting17:11
*** reed has quit IRC17:11
*** banix has joined #openstack-meeting17:12
*** shang has quit IRC17:12
*** yamamoto has joined #openstack-meeting17:12
*** mpaolino has quit IRC17:12
*** otherwiseguy has quit IRC17:13
*** manishg has joined #openstack-meeting17:14
*** kragniz has joined #openstack-meeting17:15
*** manishg_ has joined #openstack-meeting17:16
*** chuckC has joined #openstack-meeting17:16
*** yamamoto has quit IRC17:17
*** manishg has quit IRC17:18
*** manishg_ is now known as manishg17:18
*** tr3buchet1 has quit IRC17:19
*** tr3buchet1 has joined #openstack-meeting17:20
*** pblaho__ has joined #openstack-meeting17:20
*** rudrarugge has joined #openstack-meeting17:21
*** tr3buchet1 has quit IRC17:21
*** ramishra has quit IRC17:21
*** tr3buchet1 has joined #openstack-meeting17:22
*** ramishra has joined #openstack-meeting17:22
*** otherwiseguy has joined #openstack-meeting17:23
*** salv-orlando has joined #openstack-meeting17:23
*** Poornima has quit IRC17:24
*** che-arne has quit IRC17:24
*** ihrachyshka has joined #openstack-meeting17:25
*** shashankhegde has joined #openstack-meeting17:26
*** ramishra has quit IRC17:26
*** tkay has joined #openstack-meeting17:30
*** bdpayne has quit IRC17:31
*** bdpayne has joined #openstack-meeting17:33
*** ramashri has quit IRC17:33
*** ramashri has joined #openstack-meeting17:34
*** fnaval has quit IRC17:35
*** fnaval has joined #openstack-meeting17:35
*** tr3buchet1 has quit IRC17:36
*** padkrish has joined #openstack-meeting17:36
*** tr3buchet1 has joined #openstack-meeting17:36
*** yeungp has joined #openstack-meeting17:37
*** sbalukoff has quit IRC17:38
*** johnthetubaguy is now known as zz_johnthetubagu17:38
*** fnaval has quit IRC17:39
*** VijayB_ has joined #openstack-meeting17:41
*** temujin has quit IRC17:41
*** yeungp has quit IRC17:41
*** sbalukoff has joined #openstack-meeting17:41
*** jjmb has quit IRC17:41
*** ramashri has quit IRC17:42
*** yeungp has joined #openstack-meeting17:42
*** ramashri has joined #openstack-meeting17:42
*** amcrn has joined #openstack-meeting17:43
*** evgenyf has joined #openstack-meeting17:43
*** mxin has joined #openstack-meeting17:43
*** baoli has joined #openstack-meeting17:44
*** markmcclain1 has quit IRC17:44
*** masayukig has quit IRC17:44
*** ignacio-scopetta has joined #openstack-meeting17:44
*** e0ne has joined #openstack-meeting17:48
*** arnaud has joined #openstack-meeting17:49
*** masayukig has joined #openstack-meeting17:50
*** Murali_ has joined #openstack-meeting17:51
*** pblaho__ has quit IRC17:52
*** kwss has joined #openstack-meeting17:53
*** aviau has quit IRC17:53
*** ildikov has quit IRC17:56
ayoungKEYSTONE!18:00
hrybacki!18:00
marekdEHLO18:00
marekdwhat's on plate today?18:00
kwsshi18:00
*** arnaud__ has joined #openstack-meeting18:00
*** henrynash has joined #openstack-meeting18:00
ayoungI think we keep arguing about PKI tokens18:01
henrynashand hello to you too18:01
bknudsondolphm: said he wasn't going to be able to make it18:01
ayounghttps://wiki.openstack.org/wiki/Meetings/KeystoneMeeting#Agenda_for_next_meeting18:01
morganfainbergdolphm, ayoung, bknudson, dstanek, jamielennox, morganfainberg, stevemar, gyee, henrynash, topol, marekd, lbragstad, joesavak, shardy, fabiog, fmarco76, nkinder, lloydm, shrekuma, ksavich, hrybacki https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:01
gyee\o18:01
bknudsonthat wiki is looking a little weird18:02
marekdbknudson: ++18:02
bknudsonI blame henrynash18:02
marekd\o/18:02
*** jlibosva has quit IRC18:02
henrynashi do too18:02
gyeemorganfainberg, I may be zoning in-n-out as I have to attend another meeting at the same time :)18:02
hrybackio/18:02
*** tbarron has joined #openstack-meeting18:02
dstaneko/18:02
ayounggyee, we won't notice a difference18:02
morganfainberg#startmeeting Keystone18:02
openstackMeeting started Tue Aug  5 18:02:53 2014 UTC and is due to finish in 60 minutes.  The chair is morganfainberg. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: Keystone)"18:02
stevemaro/18:02
openstackThe meeting name has been set to 'keystone'18:02
morganfainbergok so a relatively short agenda today18:03
morganfainberg#topic Reviewing code18:03
*** openstack changes topic to "Reviewing code (Meeting topic: Keystone)"18:03
morganfainberg#link http://dolphm.com/reviewing-code/18:03
ayoungmorganfainberg, where is "Items we were arguing about last meeting that we didn't resolve?"18:03
morganfainbergbknudson, you said dolphm wasn't going to be making it?18:03
bknudsonmorganfainberg: y, he posted in irc18:03
morganfainbergayoung, add it to the end of the agenda?18:04
morganfainbergok so Dolph wrote a cool blog post about reviewing code18:04
bknudsonsome kind of family emergency18:04
stevemarmorganfainberg, link?18:04
morganfainbergbknudson, *nod*18:04
morganfainberg^^18:04
morganfainberg#link http://dolphm.com/reviewing-code/18:04
*** marcoemorais has quit IRC18:04
stevemaroops18:04
*** arnaud has quit IRC18:04
ayoungThat is "why"18:04
morganfainbergit's worth a read.18:04
*** marcoemorais has joined #openstack-meeting18:04
ayoungI think we need a "how"18:04
ayoungCode reviews suck18:04
ayoungand I suck at code reivews18:05
ayounga couple points:18:05
*** marcoemorais has quit IRC18:05
ayoungif you are going to -1 for a nit.  Don't18:05
henrynashnorth>18:05
ayoungFix it  and resubmit18:05
ayoungor shut up18:05
marekdayoung: ++18:05
morganfainberghenrynash, east18:05
*** marcoemorais has joined #openstack-meeting18:05
bknudsonhere's a review checklist -- https://wiki.openstack.org/wiki/ReviewChecklist18:05
ayoungobviosuly, the first is preferable18:05
morganfainberg#link https://wiki.openstack.org/wiki/ReviewChecklist18:05
*** moha_hunt has quit IRC18:05
ayoungsecond...run through the code.  Ideally in a debugger18:06
henrynashayoung: so is that preferabe?  Would some peopel object to you doing that?18:06
ayoungnothing quite like seeing how the code works18:06
ayounghenrynash, would you?18:06
henrynashayoung: no, but I am always concerend that people take time to grow the thick skins needed to survive in an open source envornment18:06
ayounghenrynash, if its a real nit, then fix it.  If the origianly author has an issue with that, they can revert, or they can accept18:06
morganfainbergideally follow the checklist18:06
*** gduan has quit IRC18:07
bknudsonrequiring the reviewer to submit the fix creates a higher barrier to reviewing.18:07
dstanekayoung: especially for newcomers i'd rather give them the change to fix the nit and feel like a part of the process18:07
morganfainbergbknudson, ++18:07
*** afazekas has quit IRC18:07
dstaneks/change/chance/18:07
ayoungWe.kill.progress.18:07
*** changbl has joined #openstack-meeting18:07
morganfainbergayoung, no we don't.18:07
ayoungWe are not good at this18:07
morganfainbergayoung, we need to use our best judgement on when to submit a fix covering a nit and when not to18:08
ayoungmorganfainberg, we need to start saying yes18:08
ayoungnot always18:08
ayoungbut a hell of a lot more than we do18:08
*** topol has joined #openstack-meeting18:08
morganfainbergayoung, i actually disagree18:08
topolo/18:08
gyeeyes!18:08
henrynashayoung: we do need to educate people a little then on how to take the change that someone else updated to your patch, typical newbie practice probaly wouldn;t know how to do that18:08
morganfainberghenrynash, ++ better than i coudl have said it18:09
morganfainberg(and beat me to the typing)18:09
stevemarhenrynash, i didn't think that was an issue18:09
*** rudrarugge has quit IRC18:09
*** rudrarug_ has joined #openstack-meeting18:09
stevemarbut yeah, i guess it would be18:09
morganfainbergbut the point is valid, don't hesitate to fix a nit if it really is the reason holding up a patch and you can afford to do so, at the very least make sure you clearly mark it as a nit if it is one. other reviewers can override +1/+2 if it's only nits18:10
henrynashagreed18:10
morganfainbergthere shound't be a requirement to fix nits though (on the reviewer)18:10
ayoungI think, also, that if a core fixes a nit, you should still be comfortable +2ing it18:10
ayoungnot just +118:10
ayoungmaybe get the origianl author to +1 before you +a18:11
henrynashayoung: ++18:11
morganfainbergayoung, i'd rather defer that call to dolphm but i don't have an issue with it.18:11
ayoungmorganfainberg, I want to clear the Queue of client changes.18:11
dstaneki don't mind the +2, but i wouldn't +A something that i pushed18:11
*** ildikov has joined #openstack-meeting18:12
henrynashayoung: we just need to make sure that submitters realize we’re helping, not implying they don’t know how to fix their code right18:12
*** evgenyf has quit IRC18:12
henrynashdstanek: +18:12
*** yamamoto has joined #openstack-meeting18:12
ayoungdstanek, I'd +a it after someone else saw it, either the origianl author or another core18:12
stevemarmorganfainberg, then we run the risk of deferring too much to dolphm18:12
morganfainbergstevemar, no i mean policy18:13
stevemaroh you meant the actual rule change..18:13
morganfainbergstevemar, yes18:13
morganfainbergstevemar, not each review :)18:13
*** jamielennox has joined #openstack-meeting18:13
stevemaryep, my bad18:13
*** jprovazn has joined #openstack-meeting18:13
henrynashmorganfainberg: naaah, assign every review that has a nit to dolph18:13
morganfainbergstevemar, it's ok you're on holiday.18:13
*** yamamoto has quit IRC18:14
morganfainbergok i think we've covered most everything here18:14
*** yamamoto has joined #openstack-meeting18:14
ayoungwe've 10 core now.  That should mean that things move faster, not slower18:14
morganfainbergayoung, and it has picked up some speed18:14
dstanekayoung: are things moving slower?18:14
*** e0ne has quit IRC18:14
morganfainbergby view it has improved since we added lbragstad18:15
*** e0ne has joined #openstack-meeting18:15
ayoungWe have two full pages of server reviews and a full page of client reviews.  For the middleware we have half a page18:16
bknudsonwe do seem to be getting more submissions too18:16
morganfainbergayoung, and a bunch of those reviews have been WIP/not touched on jenkins failures.18:16
bknudsonthe specs process has also slowed things down, maybe?18:17
morganfainbergbknudson, it has18:17
ayoungYep.18:17
morganfainbergayoung, we also have some reviews that are pending specs.18:17
ayoungmorganfainberg, yeah.18:17
morganfainbergcode talks as topol likes to say, so spec is up, so is code18:17
bknudsonsince we're expecting a spec to be approved and we're maybe not reviewing those with enough urgency18:17
*** pballand has quit IRC18:17
jamielennox++ i still haven't seen approval/denial of my specs to start doing actual implementation18:18
morganfainbergthe specs also don't see a fast turn-around on comments from the spec authors18:18
jamielennoxwith a blueprint i'd have code in to prove it by now18:18
*** evgenyf has joined #openstack-meeting18:18
morganfainbergi frquently look at specs and see a bunch of the comments and no follow up from the author18:18
ayoungyeah, specs not really what I want18:18
ayoungI want a backlog and code18:18
ayoungspecs are just busywork18:18
*** yamamoto has quit IRC18:19
morganfainberglets defer the spec specific topic.18:19
henrynashayoung; I disagree18:19
ayoungespecially when you post something to get a sense of the rightness of solution and people start attacking grammar18:19
dstanekmorganfainberg: yes, i don't even bother with those18:19
morganfainbergayoung, specifically changing the spec workflow18:19
*** markmcclain has joined #openstack-meeting18:19
*** pballand has joined #openstack-meeting18:19
ayoungmorganfainberg, henrynash specs as documents are a good tool. but specs as fodder for bikeshedding is not18:20
henrynashayoung: on grammar, i do agree!18:20
morganfainbergit is a topic we do need dolphm around for imo, so we can follow up witht hat either in -keystone or next meeting, but i don't think anything we do today will change this week18:20
ayounghenrynash, I would prefer it if the specs were designed to be the final documentation18:21
henrynash(someone needs to explain the bikeshedding analogy to me, doesn’t work in the UK)18:21
ayoungnot the  design18:21
morganfainberghenrynash, bikeshed.org18:21
ayoungdesign should be light and fast, and we should switch to code18:21
bknudsonit's probably too late for juno, how about we have a proposal for specs for kilo?18:21
henrynashmorganfainberg: ahh, all is revealed...18:21
*** vijendar1 has joined #openstack-meeting18:22
ayoungOK...back to "how to do a decent code review"18:22
morganfainbergbknudson, i think if we did what Nova did and have specs open up for the cycle a bit beforehand (so they can be approved pre-<cycle>-1 start) would help a lot18:22
henrynashayoung: agree on teh design side…….and the key things about specs for me is “Is this a sensible thing we want to be doing”18:22
ayoungI thinkgertty is a key piece18:22
ayoungit makes it really easy to do "local checkout"18:23
morganfainbergayoung, lets leave specific tools out of this.18:23
ayoungand I would request that all of you to try it out18:23
ayoungmorganfainberg, no, this is important18:23
ayoungit doesn't have to be gertty, buit it helps18:23
dstanekayoung: gertty isn't great yet18:23
marekdayoung: link?18:23
morganfainbergayoung, no telling folks to use a specific workflow is wrong.18:23
ayoungyou can do it using next-review or whatever18:23
dstanekgit review -d #18:23
ayoung#link https://git.openstack.org/cgit/stackforge/gertty/tree/README.rst18:23
marekdayoung: ty18:23
ayounggertty is rough, I'll admit18:24
morganfainbergayoung, i find gertty to be insufficient atm. it breaks far too much and is too early development18:24
morganfainbergit's cool, but it's not primetime ready yet18:24
ayoungbut the low barrier to check out might be its killer feature18:24
morganfainbergayoung, git review -d #reviewnumber18:24
ayoungalso an option18:24
morganfainbergabout the same barrier to entry18:24
ayoungwhatever works for you, so long as you run through the cdoe with a debugger18:24
*** vijendar has quit IRC18:24
ayoungand...that is the real pain point18:24
ayoung using a debugger with eclipse or pycharm is trivial18:25
ayoungfor the vi users...not so mucjh18:25
ayoungmuch18:25
bknudsongood luck running through the federation code with a debugger... all I have to do is setup apache and mod_shib and a saml provider!18:25
dstanek everyone could use 'next-review' and 'git review -d #' and i think that would be enough18:25
ayounganyone have any advice18:25
ayoungbknudson, funny you should say that18:25
morganfainbergdstanek, ++18:25
ayoungI have a method for remote debugging HTTPD WSGI code now18:25
ayoungI need to complete the blog post18:25
ayoungbut I will; do so18:25
*** julienvey has quit IRC18:26
dstanekayoung: yeah, pydev :-(18:26
morganfainbergdstanek, unfortunately one of the few options18:26
marekdpdb18:26
ayoungdstanek, is there a standard way to remote debug without an IDE for python?18:26
dstaneki use rpdb right now so that i can use real debugging tools18:26
marekdfo vi users....18:26
ayoungmarekd, link?18:26
*** ihrachyshka has quit IRC18:26
*** mxin has quit IRC18:27
bknudsonrpdb??18:27
*** eankutse1 has quit IRC18:27
morganfainberg#link https://pypi.python.org/pypi/rpdb/0.1.418:27
marekdayoung: * pdb for users ;/18:27
dstaneki debug usually in vim, but sometimes in winpdb18:27
bknudsonneat18:27
*** igordcard has joined #openstack-meeting18:27
dstaneki won't install eclipse on principle18:27
morganfainbergdstanek, lol18:27
morganfainbergdstanek, not a bad principle imo18:27
ayoungdstanek, I hear you.  and maybe rpdb is the answer there18:27
dstaneki think winpdb hasn't been updated in a while and unless you really like vim you probably don't want to follow me into vimpdb18:28
*** mxin has joined #openstack-meeting18:28
ayoungmarekd, I assume its :run a listener, run your code, your code attaches to listener at breakpoint?18:28
morganfainbergok, sorry to stop us here, but we have some other topics we need to address18:28
*** Duane has joined #openstack-meeting18:29
marekdayoung: i simply go the the code, add pdb.set_trace() and tun the code...18:29
ayoungfair enough18:29
morganfainbergwe can talk specific tools and howtos in blogs and outside of the meeting if no one minds18:29
ayoung#action marekd to write up using rpdb for Keystone18:29
morganfainberg#topic Federated users have no domain in token18:29
*** openstack changes topic to "Federated users have no domain in token (Meeting topic: Keystone)"18:29
ayoung#action ayoung to write up using pydevd  for Keystone18:29
morganfainbergstevemar, o/18:29
stevemaro/18:29
marekdayoung: i didn't mention rpdb.18:29
morganfainbergstevemar, since you wrote the patch for this, i'll let you lead18:29
stevemaro thx18:30
ayoung#action dstanek to write up using rpdb for Keystone18:30
*** bdpayne has quit IRC18:30
dstanekayoung: ++18:30
stevemarbasically a bunch of things (like non-persistent token model, and middleware) depend on the 'user' portion of the token having a 'domain' section18:30
stevemarbut we don't have that in federation issue tokens18:30
stevemarwe had 2 ideas to solve this18:31
stevemar1) add a dummy domain of 'federated'18:31
ayoungbleh18:31
stevemaror 2) add the idp id18:31
ayoungYAY!18:31
henrynashstevemar: and this is the domain the user is supposed to be owned by?18:31
morganfainberghenrynash, correct18:31
stevemarhenrynash, correct18:31
*** rakesh_hs has joined #openstack-meeting18:31
ayoungOK,  my thought was that idp == domain id is the degenerate case18:31
*** bdpayne has joined #openstack-meeting18:31
stevemarneither will work if you query /v3/domains/{domain_id}18:32
morganfainberg3) fix auth_token / client / etc to not care18:32
ayoungin a more complex case, one Idp could support multiple domains18:32
stevemarright, thx morganfainberg18:32
jamielennoxmorganfainberg: ++18:32
marekdmorganfainberg: which is a cross-project task I guesss ;/18:32
bknudsonwe could make a dummy domain work18:32
jamielennoxwhat is the value to user_domains in the federated case?18:32
morganfainbergmarekd, potentially and could affect external consumers of the token18:32
bknudsonwell, we could make a idp_id domain work, too.18:32
marekdmorganfainberg: exactly.18:32
jamielennoxor in general i guess, why can't they be optional?18:32
*** arnaud has joined #openstack-meeting18:32
*** evgenyf has quit IRC18:32
*** mxin has quit IRC18:32
*** mxin_ has joined #openstack-meeting18:32
ayoungif userid always leads to domain id, we will just be punting on the problem in auth token18:33
morganfainbergjamielennox, because we have sucked at documenting the token format, and we have a few special case formats.18:33
ayoungif you create an idp, you get a  domain to go with it18:33
morganfainbergjamielennox, we should define the format of the token and ensure that it conforms.18:33
*** eankutse has joined #openstack-meeting18:33
morganfainbergayoung, which only works in the SQL assignment backend at the moment18:33
morganfainbergayoung, you *could not* do that with ldap assignment18:33
jamielennoxok, so let's document this correctly, lets and ['user']['idp']['id'] rather than try and stick it into domain18:33
jamielennoxs/and/add18:34
morganfainbergjamielennox, we already have OS-FEDERATED:idp18:34
*** kevinconway has joined #openstack-meeting18:34
morganfainbergjamielennox, most optional items are OS-XXXXX:<something>18:34
morganfainbergin the token iirc18:34
*** banix has quit IRC18:34
ayoungmorganfainberg, LDAP should be treated like any other IdP18:35
jamielennoxok, so it would seem to me that should be enough and we just say that domain id is optional18:35
henrynashayoung: ++18:35
ayoungso the domain id would go in the domain table for LDAP18:35
morganfainbergayoung, ldap assignment not ldap identity18:35
*** Murali___ has joined #openstack-meeting18:35
ayoungmorganfainberg, LDAP assignement  can be hacked to make it work18:35
ayoungits already sick and twisted, you wouldn't even notice18:35
henrynashstevemar: so I assume tt would be obvious to someone procesing token data that this was a federated user so to not expect a domain?18:36
*** igordcard has quit IRC18:36
*** novas0x2a|laptop has joined #openstack-meeting18:37
stevemarhenrynash, well i hope so18:37
*** ignacio-scopetta has quit IRC18:37
ayoungOTOH morganfainberg if we explicitly said that IdP id == domain id, we could change the verbage over time so that IdP replaces domain when talking about users and groups,18:37
*** ignacio-scopetta has joined #openstack-meeting18:37
jamielennoxayoung: that seems worse than just fixing it, because we want a domain to just be a top level project eventually18:38
ayoungso...we could say that on a token we accept either domainid or idp id, and they are treated equivalently?18:38
bknudsonI thought hierarchical multitenancy was taking over domains18:38
*** penick_ has joined #openstack-meeting18:38
stevemarIMO sticking the idpId and the 'federated' dummy key word - are basically the same solution, neither will actually do the token any good18:38
*** Murali_ has quit IRC18:38
marekdhenrynash: i think they should not know what method was used to get a *scoped* token...18:38
henrynashjamielennox: I think actually domain-ness becomes an attribute of a project - i.e. one that allows users & grousp to be owned at that level18:38
bknudsonso I'm wondering why we need the domain id in the token?18:38
ayounghenrynash, yes, but right now, domains own users.  That is what we want to transition18:39
bknudsonso it can be used in policy?18:39
jamielennoxstevemar: right, because if you put idp-id into the domain field then you need to figure out whether it's a real domain id or something else18:39
bknudson(is this the nova identity v3 support work?)18:39
ayoungso...can we remove the domain id for all users then?18:39
*** cjellick has quit IRC18:39
henrynashayoung: sure18:39
morganfainbergbknudson, it's for revocation reasons, e.g. disabling a domain (only option i can think of, may not be a good *enough* option)18:39
jamielennoxhenrynash: ok, but either way i don't think we want to transition the name in that way then18:39
*** Duane has quit IRC18:40
bknudsony, we'd need it for revocation... but we could handle revocation of idp since we do have the idp in the token18:40
henrynashayoung: pretty sure we use domain in prolicy rules18:40
*** ramishra has joined #openstack-meeting18:40
ayoungIt will once again mess up revocation events, but we are used to that18:40
morganfainbergbknudson, right.18:40
morganfainberghenrynash, we do, no one else really does afaict18:40
jamielennoxdoes this mean that we make idp-id a top level concept?18:41
ayoungmorganfainberg, of course they do18:41
jamielennoxassign an id to SQL and LDAP backends18:41
morganfainbergayoung, in policy?18:41
ayoungmorganfainberg, yeah18:41
bknudsonjamielennox: it does seem like idp/federation should be a core concept.18:41
morganfainbergayoung, which project does?18:41
ayoungmorganfainberg, maybe not the other core projects, but end users18:41
*** IlyaE has joined #openstack-meeting18:41
morganfainbergayoung, the user's domain?18:41
jamielennoxbknudson: i think bits of it definetly should be, and IDP id would be one18:41
ayoungpeople are doing unspeakable things out there18:42
henrynashmorganfainberg: wel, it’s about the only way you can create an idea of a “cloud admin”…i.e. users in a special domain with a given role get more powers that others18:42
morganfainberghenrynash, right, keystone absolutely uses it18:42
henrynashayoung: so no, I don’t think we can remove domain_id18:43
ayoung"I've... seen things you people wouldn't believe..."18:43
*** Duane has joined #openstack-meeting18:43
bknudsonso I think we solved it18:43
* ayoung blinks18:44
ayoungwe did?18:44
bknudsonthere was a lull so I assumed that meant we'd solved it18:44
morganfainbergbknudson, lol18:45
morganfainbergso the best option sounds like federated users don't get domain_ids and we fix everything else?18:45
ayoung"lost in time, like [small cough] tears... in... rain. Time..."18:45
jamielennoxagreed18:45
henrynashmorganfainberg: I agree18:45
*** f13o_ has joined #openstack-meeting18:45
marekd+++++18:45
*** cjellick has joined #openstack-meeting18:45
ayoungblah18:45
henrynashbknudson: you were right, master18:46
ayoungeither everyone gets it18:46
ayoungor no one18:46
dstanek"if i can't have it, nobody can"18:46
henrynashtoys, pram, out18:46
ayoungwe've inflicted our half-thought-through domain concept on the rest of openstack.  We can't break it now18:46
morganfainberghenrynash, i think we can probably drop a user's domain id attribute across the board, but it would be a bunch of work18:46
morganfainberghenrynash, in the token that is18:46
ayoungLets make the IdP id the domain id18:46
ayoungand lock them one-to-one18:47
*** cjellick has quit IRC18:47
jamielennoxayoung: that will screw us longer term18:47
ayoungjamielennox, how18:47
jamielennoxbecause we have assumptions on things like domain owns project18:47
ayounghow is that worse than screwing all Openstack deployments by yanking domains18:47
ayoungSo what18:47
*** cjellick has joined #openstack-meeting18:47
ayoungwe can make domains that don't have Idps, just not the reverse18:48
jamielennoxif idp becomes domain then we break the whole existing point of domains18:48
bknudsonhttps://github.com/openstack/identity-api/blob/master/v3/src/markdown/identity-api-v3.md#authentication-responses18:48
ayoungand, in the future we drop domains as the way of talking about users, and only say idps18:48
bknudsonhere's what we document for the response18:48
morganfainbergbknudson, ah, we documented the token that way18:48
morganfainbergbknudson, i guess we can't rip that out then can we?18:48
bknudsonso you're saying for federation there's no "domain" section in "user"?18:48
ayoungWe are stuck with out mistakes.18:48
*** emagana has quit IRC18:48
bknudsonmaybe this would be documented in the federation extension18:49
*** emagana has joined #openstack-meeting18:49
henrynashhow about we think about this is terms of when keystone idenitity becomes an idp18:49
*** evgenyf has joined #openstack-meeting18:49
*** dguerri`afk is now known as dguerri18:50
henrynashsurely we want to ADD an “idp” section to teh token, which woudl be “keystone” for ours, and domain is only required for keystoen idps users18:50
*** pballand has quit IRC18:50
ayounghenrynash, V418:50
bknudsonI don't see anything in the federation spec that says the token format is different -- https://github.com/openstack/identity-api/blob/master/v3/src/markdown/identity-api-v3-os-federation-ext.md18:50
ayoungV3 api is built around the domain concept18:51
*** jcoufal-mobile has joined #openstack-meeting18:51
bknudsonhenrynash: but when we have keystone identity as an idp we might want to simplify it... one domain per identity idp18:51
henrynashV3 was also built around the idea (origionally) taht all users were “visible” vai keystone, which they aren’t with federation18:51
*** Murali___ has quit IRC18:52
morganfainbergi don't want to cut this short but we have one more topic, if henrynash doesn't mind delaying we can continue this convo18:52
henrynashbknudson: so we’d have multiple keystone idps ( to map to the current situation)?18:52
bknudsonhenrynash: y, if you have multiple domains.18:52
*** Murali_ has joined #openstack-meeting18:52
*** baoli has quit IRC18:53
henrynashmorganfainberg: agreed….my only request was so more eyes on: https://review.openstack.org/#/c/99842/18:53
morganfainbergok so lets continue this topic18:53
morganfainberg7 minutes till end fyi18:53
*** baoli has joined #openstack-meeting18:53
*** emagana has quit IRC18:53
morganfainbergi think the question is, should IDPs care about domains (and i don't mean from a grant perspective)18:54
morganfainbergif idps don't care about domains (i don't see the benefit), we don't need to lock it to idp == domain18:54
dstaneki just took a look at the numbers and keystone commits are not slowing down - https://www.dropbox.com/s/4dh3tc8mr1ja94b/Screenshot%202014-08-05%2014.53.18.png18:54
henrynashbknudson: but does that map to how we user external idps today…..e.g. teh facebook idp could assert to multiple domains18:54
*** dbite has quit IRC18:55
*** Duane has quit IRC18:55
bknudsonhenrynash: I thought we were just discussing that idps didn't know anything about domains.18:56
ayounghenrynash, endpoint policy?18:56
morganfainbergbknudson, i think henrynash is claiming that.18:56
bknudsonso an identity idp wouldn't know anything about domains18:56
*** vijendar1 has quit IRC18:57
*** lcheng has quit IRC18:57
morganfainberghenrynash, if i'm understadning you, idps don't care about domains and could assert for any domain today, right?18:57
*** vijendar has joined #openstack-meeting18:57
*** jecarey has quit IRC18:58
bknudsonan identity idp would have to work like any other idp... it returns a bag of attributes that get mapped to user ID and groups18:58
*** Duane has joined #openstack-meeting18:58
ayounghenrynash, what did you want to ask about endpoint policy?18:58
*** lcheng has joined #openstack-meeting18:59
henrynashmorganfainberq: it seems to me that this should be true, I can imagine large idps doin that…I guess teh questions is whether an IdP ID that we store internally can point at multiple domains, or whether we crreate a new reprsentation of that idp (i.e. a new IDP ID) for eavery domain18:59
*** emagana has joined #openstack-meeting18:59
*** jolyonbrown has joined #openstack-meeting18:59
ayounghenrynash, one to one for now,  one to many if it gets requested in the future18:59
*** banix has joined #openstack-meeting18:59
henrynashayoung: morganfainberg: asked if I would defer….I said yes - as long as peopel get eys on teh spec18:59
morganfainberghenrynash, i don't like the tight coupling of idpid to domain_id personally, but i think it adds a lot of overhead and complexity18:59
ayoungKK18:59
*** emagana has quit IRC19:00
morganfainberghenrynash, bknudson, i think we have 2 options at the moment (due to the spec) 1: dummy domain, 2: idpid == domain id19:00
morganfainbergunfortunately that is time :(19:00
*** rockyg has joined #openstack-meeting19:00
morganfainbergtake this back to -keystone19:01
morganfainberg#endmeeting19:01
*** openstack changes topic to "cinder ci iscsi/smb3 (Meeting topic: hyper-v)"19:01
openstackMeeting ended Tue Aug  5 19:01:08 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-08-05-18.02.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-08-05-18.02.txt19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-08-05-18.02.log.html19:01
henrynashmorganfainberg: I think we need to jsut draw out the relationships between mapping table, Idp IDs, IDP entities and domains19:01
*** emagana has joined #openstack-meeting19:01
*** emagana has quit IRC19:01
morganfainberghenrynash, fair enough19:01
*** emagana has joined #openstack-meeting19:01
fungihey ho, let's go?19:01
jeblairhi infra folks?19:01
*** mxin_ has quit IRC19:01
jolyonbrownHi! New here, just hoping to get involved19:02
pleia2o/19:02
asselin_hi19:02
clarkbo/19:02
jeblairjolyonbrown: welcome!19:02
jesusauruso/19:02
jeblair#startmeeting infra19:02
openstackMeeting started Tue Aug  5 19:02:28 2014 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: infra)"19:02
openstackThe meeting name has been set to 'infra'19:02
jeblairour agenda is here:19:02
jeblair#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:02
jeblairsummary from last meeting:19:02
jeblairhttp://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-07-29-19.01.html19:02
jeblair#link http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-07-29-19.01.html19:02
jeblair#topic Puppet module Split out (jesusaurus/nibalizer)19:03
*** openstack changes topic to "Puppet module Split out (jesusaurus/nibalizer) (Meeting topic: infra)"19:03
*** hrybacki has quit IRC19:03
jeblair#link https://review.openstack.org/#/c/99990/19:03
*** hrybacki has joined #openstack-meeting19:03
ianwo/19:03
jesusaurus99990 has been sitting with a couple +1s for a while now, and I'm just wondering what needs to happen to help move that along19:03
jeblairjesusaurus: very good point; i can review it today19:04
jesusaurusdo the cores have any comments/concerns?19:04
*** hrybacki has left #openstack-meeting19:04
* fungi feels partly to blame for not reviewing enough. added to the evening pile19:04
jeblairhopefully another core can too.  i think it was pretty close last time i looked.19:04
pleia2jeblair: looks like it has some overlap with your new https://review.openstack.org/#/c/110730/19:05
clarkbI am still in a review mood I can review it today19:05
pleia2so I'd simplify 110730 in some places to point to jesusaurus' spec19:05
*** kwss has quit IRC19:05
jesusaurusif its just a matter of getting burried in review backlog then i guess this will be a short topic19:05
jeblairi think the last two comments look good -- about how to actually proceed switching each module over19:06
jesusaurusbut i wanted to give people a chance to discuss any concerns they might have19:06
*** evgenyf has quit IRC19:06
clarkbjesusaurus: ya I think with all the travel and summer we haven't kept up at all19:06
*** wenlock has joined #openstack-meeting19:06
pleia2(ah, I do see a note in the bottom of 110730)19:06
clarkbjesusaurus: but we seems to be turning a corner on that so hopefully things start moving19:06
jeblairpleia2: i mentioned this one in my spec; but they actually don't overlap that much.  they are complimentary19:06
fungii feel like i should set aside more time to review specs in general, they just take a good deal longer than the typical code change so it takes getting into the right mindset. not an excuse mind you19:06
jeblairfungi: agreed19:07
jeblairthe specs process is still a learning process :)19:07
nibalizero/19:07
jeblairany further thoughts on this, particularly any process changes once it's approved and we start in on it?19:08
*** ivar-lazzaro has quit IRC19:08
nibalizeri think we should automate it, but i doubt thats controversial19:08
*** jecarey has joined #openstack-meeting19:09
fungias in changes to how we review additions of new puppet modules to config (deny them) or major refactors (encourage extraction first)?19:09
jesusaurusnibalizer: what do you have in mind?19:09
nibalizera script to split it out19:09
nibalizerthen propose the changes19:09
nibalizerwell19:09
nibalizerwe should do one first19:09
nibalizerget our sea legs a bit19:10
nibalizerthen automate it19:10
jeblairnibalizer: then maybe add that script to tools/19:10
nibalizerya19:10
jeblairnibalizer: but i do think we should still do the mods one at a time19:10
nibalizeragreed19:10
jesusaurusagreed19:10
fungii think the major process change once approved is that we need review diligence to avoid backsliding19:10
jeblairfungi: yep19:10
fungino accumulation of new modules, no significant work on existing modules while still in the config tree19:11
jesusaurusalso some modules will be harder than others due to reviews in-flight19:11
jeblairi'm hoping by splitting those up into individual tasks, we can help spread the work around.  in addition to actually doing the split, there will probably be some shepharding needed for the things jesusaurus mentioned19:12
jeblairs/shepharding/cat herding/19:12
*** yamamoto has joined #openstack-meeting19:12
*** aswadr has quit IRC19:12
jeblairanything else, or shall we move on?19:13
jesusaurusalso, once we starting splitting modules out, we will want to test interoperability, so i think we should work on those tests on our first split-out module before we start moving with other modules19:13
*** julienvey has joined #openstack-meeting19:13
*** andreykurilin_ has joined #openstack-meeting19:13
mordredo/19:13
*** otherwiseguy has quit IRC19:13
mordredsorry late19:13
jeblairjesusaurus: good point; also, making the tests on the mods themselves boilerplate19:13
jesusaurusyeah19:13
*** jamielennox has left #openstack-meeting19:13
jeblairi just approved the zuul cloner patches; maybe we can use that to set up integration tests (so we don't have to use devstack-gate)19:14
nibalizerif you look at the storyboard mod that i split manually19:14
nibalizeri added rake tests and such for it19:14
nibalizerand did a history rewrite so that the testing framework lands first19:14
jeblaircool19:14
nibalizerhttps://review.openstack.org/#/c/100370/19:15
jeblairnot sure how i feel about the history rewrite19:15
nibalizeri'd like to see us do storyboard first, since thats the one i've been most working/familiar with, but that runs against the big refactor krotscheck is trying to land19:15
nibalizerjeblair: its a reordeing rebase, no history is lost19:16
clarkbnibalizer: it isn't necessary19:16
clarkbyou just need to put the tests on top as the first change19:16
nibalizerah and have zuul figure it out?19:16
nibalizergross19:16
nibalizerokay19:16
clarkbnibalizer: its not gross19:16
clarkbnibalizer: you push the eixsting history into gerrit as is19:16
clarkbnibalizer: then change one adds .gitreview and tests19:16
* nibalizer is still used to a github style workflow where I do the ordering in my tree 19:17
krotscheckNote: I discovered an outstanding issue with the storyboard module that I had to fix yesterday, the module didn’t check for the existence of git.19:17
*** yamamoto has quit IRC19:17
*** salv-orlando has quit IRC19:17
jesusaurusokay, i think we're pretty much done with this topic now19:18
jeblairi don't want to hold up krotscheck's module since we need to get some changes in to the running server19:18
*** cody-somerville has quit IRC19:18
*** ivar-lazzaro has joined #openstack-meeting19:18
jeblairhow close are their current states?  can we duplicate krotscheck's change onto puppet-storyboard?19:18
*** rwsu has quit IRC19:18
*** salv-orlando has joined #openstack-meeting19:19
*** aviau has joined #openstack-meeting19:19
jeblairnibalizer: ^?19:19
*** pballand has joined #openstack-meeting19:20
*** julienvey has quit IRC19:20
*** Duane has quit IRC19:20
jeblairwell, i imagine we'll probably want to do something like that.  the alternative is to re-do the extraction and force-push, but that's messy and probably not warranted in this case.19:21
*** baoli has quit IRC19:21
jeblair#topc Discussion about the inclusion of git-upstream in Stackforge (dguerri)19:21
jeblair#topic Discussion about the inclusion of git-upstream in Stackforge (dguerri)19:21
*** openstack changes topic to "Discussion about the inclusion of git-upstream in Stackforge (dguerri) (Meeting topic: infra)"19:21
dguerrifirst: hello folks, I am pretty new to these IRC meeting :)19:21
fungiwelcome, dguerri19:21
jeblairdguerri: hi there!19:22
dguerriThis is about adding a new tool to Stackforge --> https://review.openstack.org/10929219:22
*** zehicle_at_dell has joined #openstack-meeting19:22
dguerriI know this is not something that is usually in this agenda, sorry for the hassle...19:22
*** julienvey has joined #openstack-meeting19:22
dguerrito recap: this topic is in openstack-infra agenda as there has been a concern about the name of the tool (anteaya) as it could create confusion with git-review19:22
*** mspreitz has quit IRC19:22
*** baoli has joined #openstack-meeting19:22
*** dhellmann is now known as dhellmann_19:22
dguerriAfter a discussion in #openstack infra, that concern is no longer. anteaya voted with a +1 to that review.19:23
jeblairdguerri: thanks, yeah.  we don't normally weigh in too much on stackforge tools; but are certainly happy to help discuss something like this if it's necessary.19:23
dguerriSo if someone (at their convenience) could review that... that would be great! :)19:23
*** ramishra has quit IRC19:23
*** banix has quit IRC19:23
jeblairit has 2x+2s, i only did not approve it since it was on the agenda19:24
dguerriif there are no other concerns or info request... that's all19:24
dguerriok, thanks!19:24
jeblairso unless any of the core's here have anything to add, we can probably go ahead and push it through19:24
clarkb+119:24
fungiseems fine to me19:24
jeblairdone19:24
dguerricheers ;)19:25
fungimy only concerns were when it was previously being proposed for inclusion in openstack-infra instead, at which time its scope was not as well documented19:25
jeblairdguerri: thanks!  hope to see you around :)19:25
fungifor stackforge it seems fine19:25
*** evgenyf has joined #openstack-meeting19:25
dguerriI will be around, definitely.19:25
jeblairyeah, seems a stretch for infra at the moment, unless we start using it for gerrit or something19:25
*** aviau has quit IRC19:25
jeblair#topic  Outage for proactively migrating jenkins05 to a different host (fungi)19:25
*** openstack changes topic to "Outage for proactively migrating jenkins05 to a different host (fungi) (Meeting topic: infra)"19:25
jeblairistr this happened?19:26
fungijeblair: oh, i took that off the agenda after the last time you loaded it :/19:26
jeblairhaha19:26
fungiit happened, no issues19:26
*** jcoufal-mobile has quit IRC19:26
jeblairexcellent!19:26
fungiwe can move on19:26
jeblair#topic  Pootle upgrade to 2.6.0 RC (pleia2)19:26
*** openstack changes topic to "Pootle upgrade to 2.6.0 RC (pleia2) (Meeting topic: infra)"19:26
mordredfungi: well done19:26
clarkbwoot19:26
clarkbpleia2: do we need this upgrade to allow the demo to happen?19:27
pleia2so we have a demo scheduled with a pootle person on the 18th, so I'm hoping we can get this upgraded to the latest 2.6RC so he can show off all the latest features19:27
clarkbpleia2: I am admittedly a bit behind on the state of things here19:27
jeblairpleia2: 19th?19:27
pleia2er, 19th (but it's the evening of the 18th for us)19:27
*** banix has joined #openstack-meeting19:27
jeblairok19:27
clarkbI am happy to help if I can. I know jeblair has interest in this area so I may just stay out of the way :)19:28
*** cjellick has quit IRC19:28
pleia2I am happy to get familiar with how upgrades happen and help out (might be good practice for all of us), or discuss just wiping what we have and installing fresh19:28
jeblairi'm about to take off from mid-this-week to mid-next-week, so i will be of limited utility19:28
pleia2I'm out thurs-fri this week19:28
*** moha_hunt has joined #openstack-meeting19:28
jeblairpleia2: there's some not at all documented stuff about how i placed the git repos on that server19:28
clarkbjeblair: pootle isn't in puppet right?19:28
pleia2clarkb: right19:29
clarkbjeblair: but I should be able to log into the server and have root?19:29
* clarkb tries to remember what the host's fqdn is19:29
pleia2translate-dev19:29
jeblairpleia2: i was not expecting the time delta between when i "got some stuff working" to when i would "write it up properly in puppet" to be nearly a year...19:29
jeblair:(19:29
*** dguerri is now known as dguerri`afk19:29
pleia2jeblair: yeah :\19:29
jeblairpleia2: so we should probably keep that around because of its institutional knowledge19:30
*** otherwiseguy has joined #openstack-meeting19:30
clarkbyup I have root, pleia2 we can crash course on pootle upgrades between now and monday then do it on monday?19:30
pleia2clarkb: wfm19:30
clarkbjeblair: or would you prefer we spin up a second host and install from scratch? I am happy either way19:30
jeblairit's probably not crazy to try to upgrade that in place, but of course, if you feel like just doing a new server, that's cool too19:30
clarkbjeblair: ok19:30
jeblairthe only other thing on that server is that it contains my not-upstreamed patch to do openid19:31
jeblairupstream has since incorporated a different method of doing openid19:31
*** emagana has quit IRC19:31
jeblairso that will require changing19:31
clarkbjeblair: config change?19:31
pleia2fortunately 2.5.1 is still the stable version, so it's not going to be some huge leap19:31
jeblairclarkb: code change19:31
clarkbjeblair: right but we can use upstreams openid now?19:31
fungipleia2: i'm also around normal hours all next week and am happy to pitch in on it19:31
jeblair(i submitted the change upstream, but he wanted a different approach, which i never got around to writing)19:31
*** emagana has joined #openstack-meeting19:31
clarkbjeblair: or do we need to apply your patch to pootle?19:31
pleia2actually - clarkb can you confirm the version we installed? (I just clicked on "help" but now realized it doesn't specify version)19:31
jeblairclarkb: i hope so, but i do not know.19:32
clarkbpleia2: Pootle==2.5.019:32
clarkbjeblair: rdr19:32
clarkber rgr19:32
pleia2clarkb: ok, thanks19:32
*** cjellick has joined #openstack-meeting19:32
*** fnaval has joined #openstack-meeting19:33
jeblairsounds like a plan, thanks!19:33
pleia2thanks :)19:33
*** padkrish has quit IRC19:33
jeblair#topic  Rename Marconi->Zaqar (flaper87)19:33
*** openstack changes topic to "Rename Marconi->Zaqar (flaper87) (Meeting topic: infra)"19:33
*** emagana_ has joined #openstack-meeting19:33
jeblair#link https://review.openstack.org/#/c/111244/19:33
*** padkrish has joined #openstack-meeting19:34
*** emagana_ has quit IRC19:34
*** cody-somerville has joined #openstack-meeting19:34
fungii'm travelling a bunch this weekend, but can help/run the rename any time next week or after19:34
clarkbI was +2 on a previous patch, need to review current patchset19:34
jeblairi'm also not around this weekend19:34
*** alexpilotti has quit IRC19:34
*** igordcard has joined #openstack-meeting19:34
*** emagana_ has joined #openstack-meeting19:34
clarkbme 319:34
clarkbyou can blame greghaynes for that19:35
fungiflaper87|afk: if you're not really afk, any requested timeline for renaming?19:35
mordredI do not think I should do it myself19:35
jeblairSergeyLukjanov: are you around?19:35
mordredbut SergeyLukjanov and I could probably do it19:35
mordredoh - wait - I'm also not aroudn this weekend. duh19:36
jeblairit's sounding like we may want to tentatively schedule it for the following weekend (16-17)19:36
*** emagana has quit IRC19:36
jeblairalong with the kite rename19:36
nibalizerthere was also something i wanted to move to the attic19:36
* mordred will also not be here the following weekend, nor the weekend after that19:36
clarkbmordred: giving up on weekend hacking?19:37
*** mspreitz has joined #openstack-meeting19:37
nibalizeri think it was this http://git.openstack.org/cgit/openstack-infra/puppet-dashboard/19:37
clarkbjeblair: 16-17 is hard for me but not impossible19:37
mordredclarkb: wedding, burningman, burningman19:37
fungioh, and was there ever a decision on gantt?19:37
clarkbfungi: I thought we were leaving gantt as is because people wanted to move it back there at some point19:37
clarkband we said lets not play musical chairs19:37
jeblairfungi: i think we need to disable access to it19:37
jeblairjraim__: ^ thoughts on moving kite to openstack on the 16-17th ?19:38
jeblairlet's revisit these next week19:38
clarkbwfm19:38
fungiah, right19:38
*** padkrish has quit IRC19:38
jeblair#topic Discuss common location for third party ci system's templates (asselin, krtaylor, joa)19:38
*** openstack changes topic to "Discuss common location for third party ci system's templates (asselin, krtaylor, joa) (Meeting topic: infra)"19:38
fungiagreed19:38
asselin_hi, so in the 3rd party discussion, many of us are using jaypipes's repo19:39
* ttx lurks19:39
asselin_we'd like a common place to leverage each other's work & keep in sync with infra.19:39
*** cjellick has quit IRC19:39
jeblairasselin_: great.  that place is infra19:39
fungii still think rewriting/expanding the third-party.rst would be a welcome place19:39
asselin_fungi, yes, we can do that as part of the change.19:40
clarkbjeblair: right, I think this falls under making infra more consumable19:40
jeblairasselin_: as you've seen from the earlier topics, there's a lot of work to make the puppet modules more reusable19:40
*** cjellick has joined #openstack-meeting19:40
*** henrynash has quit IRC19:40
jeblairasselin_: that's part of it; documentation is part of it...19:40
asselin_yes, we've run in a few issues that hve been fixed.19:40
asselin_I'd like to see documetation + puppet scripts (code) that does it all19:41
*** mpaolino has joined #openstack-meeting19:41
asselin_we're all spending a lot of time figuring out the same things19:41
asselin_3rd party team though was stackforge.19:41
fungiand yeah, as far as any of the scripting/automation side, most of that just speaks to inadequacies in consumability of our tooling (or in some cases, misunderstandings around it, thus shortcomings in documentation)19:41
*** infotect- has quit IRC19:41
*** mpaolino has quit IRC19:42
asselin_If you think o.o infra's the place, even better19:42
*** infotection has joined #openstack-meeting19:42
asselin_fungi, I don't want to see everyone reading documentation and putting pieces togeter to get a ci system up and running.19:42
jeblairasselin_: yep.  the goal is for all of infra to be consumable; it's going to take a bit to get there, including some things like the large puppet refactor underway.19:42
asselin_fungi, I'm find with documentation and a solution19:42
*** infotection has quit IRC19:43
e0neasselin_ infra is very specific to openstack infrastructure19:43
asselin_i.e. something like what jaypipes started, but is now out of sync. https://github.com/jaypipes/os-ext-testing19:43
*** infotection has joined #openstack-meeting19:43
jeblairasselin_: some of the folks working on this want a full system, including gerrit.  the third party folks, not so much.  so one thing you can do is help to make sure that as we move forward, it's modular enough to just run the bits you need.19:44
e0neimo, it would be better to mage infra/config more configurable to use it in 3rd party CIs19:44
jaypipesjeblair: ++19:44
jeblairasselin_: yeah, everyone who does something like that gets out of sync, which is why we're starting on structural changes to help avoid that19:44
jeblairthere are two infra-specs dealing with puppet refactors that are both designed to be initial steps to making this better19:45
asselin_so perhaps we can agree to move to stack forge, to start to bring it in sync with o.o & the changes discussed earlier (puppet refactors)19:45
jeblair(they aren't going to completely get us there, but they will make a big difference)19:46
*** torgomatic has joined #openstack-meeting19:46
*** denis_makogon_ has joined #openstack-meeting19:46
*** johnpur has quit IRC19:46
*** denis_makogon_ is now known as denis_makogon19:46
jolyonbrownsorry for a dumb question.. what is o.o ?19:46
asselin_openstack.org19:46
jolyonbrown:)19:46
*** johnpur has joined #openstack-meeting19:46
clarkbasselin_: I think the issue with going to stackforge is it is misplacing the effort needed19:46
clarkbasselin_: if we start with infra/config you are automagically in sync19:46
fungiideally effort would go into improving the existing tooling rather than writing convenience wrappers around it19:47
*** tr3buchet1 has quit IRC19:47
jesusaurusfungi: ++19:47
*** marcoemorais has quit IRC19:47
*** tr3buchet1 has joined #openstack-meeting19:47
*** marcoemorais has joined #openstack-meeting19:47
e0nefungi: agree with you19:47
asselin_clarkb, ok, so we'll add a special 3rd party starting point in infra/config that 3rd party can use & stay in sync.19:47
krtaylore0ne, we have made several changes to make third-party CI easier to consume19:48
jeblairasselin_: there's a lot of thought about how to use hiera to further refactor what we're doing; it's likely with that in place, we won't really need a separate starting point19:48
*** _nadya_ has quit IRC19:48
e0nekrtaylor: looks like I missed it:(19:49
jeblairasselin_: so i think that's why you're hearing that we want effort to go into infra19:49
*** evgenyf has quit IRC19:49
asselin_ok, I will spend my effort then to see how to make it work inside infra-config19:49
jeblairit's not going to be fast, but in the end, i think it's going to be good, and we can use all the help we can get :)19:49
*** ArxCruz has joined #openstack-meeting19:50
asselin_agreed19:50
jeblairasselin_:  so big things to watch out for are: puppet module split; openstack_project split; hiera related changes19:50
jeblairs/watch out for/help with/ :)19:50
asselin_yeah...good point, I don't want to add it there, just to get split out :)19:51
*** johnpur has quit IRC19:51
mordredasselin_: also, I've been slowly working up ansible things to run the puppet - which _might_ be helpful or things you want to keep an eye on as well19:51
asselin_e0ne, krtaylor anthing else I missed?19:51
krtaylorwe did talk about having some well commented templates19:51
jeblairall right, thanks for bringing this up -- it's hard to overstate the number of people interested in it, and i think it's key to growing the contributor base to infra19:51
mordred++19:52
krtaylorand a place to store them, but I guess that could be documentation19:52
jeblairkrtaylor: cool, check out my proposed "openstack_project" split spec and see how that relates to your idea19:52
*** _nadya_ has joined #openstack-meeting19:52
krtaylorI guess I could plug the Monday third-party meetings too :)19:52
jeblairi'm going to try to move on and get the last couple topics now19:52
krtaylorjeblair, will do19:52
asselin_thanks19:53
jeblair#topic  Switching all projects to trusty by default (clarkb)19:53
*** openstack changes topic to "Switching all projects to trusty by default (clarkb) (Meeting topic: infra)"19:53
mordredclarkb: do it19:53
jeblairclarkb: make it so? :)19:53
*** padkrish has joined #openstack-meeting19:53
clarkbyes :)19:53
clarkbso really I bring this up because I think for at least infra we want to remain as default precise19:53
mordreddo we?19:54
clarkbmordred: all of our nodes are still precise so yes I think so19:54
mordredsorry - mis-parsed your sentence19:54
*** _nadya_ has quit IRC19:54
clarkbI can write a change that switches most everything to trusty and that may break some things and that change can default us to precise19:54
jeblairwe do want to change that; and we'll still be running py2719:54
mordredI thought you were implying that we wanted to stay on precise as an end-goal19:54
*** rwsu has joined #openstack-meeting19:54
clarkbmordred: no no, mostly I just want to change the zuul layout.yaml name .* parameter function to default to trusty19:55
jeblairclarkb: so i wonder what things might break?19:55
mordred++19:55
clarkbthen accomodate for things that should remain precise for now19:55
fungipy33 jobs are going to be a bit of a challenge there19:55
clarkbfungi: py33 is already handled19:55
jeblairclarkb: sounds like a plan19:55
fungisince we need to switch to py34 jobs replacing them19:55
fungialready done?19:55
clarkbfungi: no its not done, but the next item will talk about it :)19:55
jeblair#topic  Switching to tox>=1.7.2 (clarkb)19:55
*** openstack changes topic to "Switching to tox>=1.7.2 (clarkb) (Meeting topic: infra)"19:55
fungioh, got it! ;_19:55
mordredclarkb: do it19:55
clarkbso we currently hardcode py33 jobs to precise19:55
jeblairclarkb: make it so?19:55
clarkbwe should make it so :)19:56
clarkbbut old tox doesn't grok py34 appearnetly19:56
fungiahh, that19:56
mordredwhat? jesus19:56
fungiyep, now i see19:56
mordredthat's stupid19:56
clarkbat least not according to the tox changelog. So before we can move py33 to py34 we need to upgrade tox :)19:56
fungiso for tox 1.7.2 we need to finish the hashseed pinning right?19:56
*** afazekas has joined #openstack-meeting19:56
mordredor move to dox19:56
clarkbmy current thought is to send mail to the list about flipping to trusty and upgrading tox in ~2 weeks19:57
clarkbfungi: well honestly after all the -2s I have gotten I am really starting to think I should just upgrade tox19:57
clarkbmaybe that is too bofhy but its been furstrating19:57
jeblairclarkb: -2s why?19:57
*** reed has joined #openstack-meeting19:57
fungilet them all break and see how fast they change their minds on setting hashseeds?19:57
mordredseriously - that this is a probelm is VERY frustrating to me19:57
clarkbjeblair: our backport process is ridiculous19:57
*** reed has quit IRC19:57
*** reed has joined #openstack-meeting19:57
clarkbjeblair: and you have to do all these things and people wonder why we need to support new tox on old branches and it has been one thing after another in some cases19:58
mordredI mean, I get the thing it's supposed to be doing - but our TESTENV RUNNER should not be doign this19:58
fungiis it just stable backports which are getting -2'd?19:58
clarkbfungi: yes19:58
clarkbfungi: but they will break without the hashseed tox.ini backport19:58
*** manishg has quit IRC19:58
*** swifterdarrell has joined #openstack-meeting19:58
fungii can help advocate for this with the stable branch maintainers. we can't really run a different tox et cetera for testing stable patches, so yes19:58
fungittx: ^19:59
*** andreykurilin1_ has joined #openstack-meeting19:59
jeblairclarkb: it may be worth also bringing this up in the cross project meeting in 1 hour and one minute.19:59
mordred++19:59
clarkbso should I go ahead and say ~2 weeks from now we will be doing this?19:59
fungidefinitely19:59
clarkbjeblair: will do19:59
mordredI'm also not really kidding about moving to dox instead19:59
clarkbmaybe wait on announcement for after the cross project meeting19:59
jeblairmordred: except for ceilometer19:59
jeblairmordred: i mean cinder19:59
*** IanGovett has quit IRC19:59
clarkband tempest19:59
mordredjeblair: cinder doesn't run iscsci in its unittestss19:59
*** eglynn has joined #openstack-meeting19:59
clarkbactually tempest should work nevermind20:00
fungii would let the cross-project meeting know you're doing this in 2 weeks. friendly public service announcement ;_20:00
jeblairmordred: but it might in its functests, and we should not block that20:00
clarkbfungi: :) sounds good20:00
jeblairand we're at time; thanks everyone!20:00
jeblair#endmeeting20:00
*** openstack changes topic to "cinder ci iscsi/smb3 (Meeting topic: hyper-v)"20:00
openstackMeeting ended Tue Aug  5 20:00:37 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-08-05-19.02.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-08-05-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-08-05-19.02.log.html20:00
mordredjeblair: indeed - although I'd like to figure out a way to solve that ... also, it _may_ be possible to do - just not with proper separation20:00
jolyonbrown*Ahem* enjoyed watching this meeting. I’m relatively new to openstack infra (lurked for a while), but looking to get involved (ulterior motive: http://www.openstack.org/vote-paris/Presentation/from-noob-to-root-how-i-got-involved-with-the-openstack-infrastructure-team). Will be bugging the irc channel quite a lot and trying to pick up tasks. If anyone wants anything doing please give me a shout! https://launchpad.net/~jolyo20:00
jolyonbrownn20:00
jeblairttx hold one sec please20:01
*** mtanino has joined #openstack-meeting20:01
*** ChanServ sets mode: +o jeblair20:01
*** jeblair changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:01
mordredjolyonbrown: awesome! welcome20:01
*** tzabal has joined #openstack-meeting20:01
jeblairttx: all clear20:01
*** jeblair sets mode: -o jeblair20:01
boris-42Hi everybody =)20:01
ttxAnyone here for the TC meeting ?20:01
sdagueo/20:01
notmynamehere20:01
markmcclaino/20:01
mordredo/20:01
dhellmann_o/20:01
mikalHeya20:01
jeblairo/20:01
boris-42https://docs.google.com/a/pavlovic.ru/document/d/137zbrz0KJd6uZwoZEu4BkdKiR_Diobantu0GduS7HnA/edit# this is some kind of summary20:01
ttxrussellb, markmc, annegentle, devananda, vishy, jaypipes : around ?20:02
boris-42cause mailing list has a lot of stuff20:02
*** eankutse has quit IRC20:02
vishyo/20:02
ttxboris-42: wait a sec until meeting starts and we get that logged20:02
*** eankutse has joined #openstack-meeting20:02
eglynnttx: markmc is on PTO this week still20:02
boris-42ttx ok I will do20:02
ttxwe now have quorum*20:02
*** annegent_ has joined #openstack-meeting20:02
ttx#startmeeting tc20:02
openstackMeeting started Tue Aug  5 20:02:50 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
jaypipeso/20:02
russellbo/20:02
*** dhellmann_ is now known as dhellmann20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: tc)"20:02
openstackThe meeting name has been set to 'tc'20:02
ttxOur agenda for today is at:20:03
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:03
ttx#topic Rally incubation request20:03
*** wenlock has left #openstack-meeting20:03
*** openstack changes topic to "Rally incubation request (Meeting topic: tc)"20:03
boris-42#link https://docs.google.com/a/pavlovic.ru/document/d/137zbrz0KJd6uZwoZEu4BkdKiR_Diobantu0GduS7HnA/edit# summary of mailing list20:03
ttxSo this is split into two governance changes, one asking for a new program:20:03
*** f13o_ has quit IRC20:03
ttx#link https://review.openstack.org/10850220:03
ttxThe other asking to add Rally for incubation into the integrated release:20:03
*** vivek-ebay has quit IRC20:03
ttx#link https://review.openstack.org/11063820:03
ttxOn the first part there is tension on the need for a separate program20:04
ttxThat tension imho revolves around the two aspects of Rally: performance testing on one side (which is seen as a QA thing), and operators-facing performance ("SLA") monitoring-as-a-service (which is seen as one of several operators tools)20:04
ttxPersonally I see value in more direct integration/collaboration between performance testing and QA, and being under the same program would help20:04
ttxBut then a program around operators tooling is not such a bad idea either20:04
*** TravT has joined #openstack-meeting20:04
*** tr3buchet1 has quit IRC20:05
ttxSo I'm torn on that first review. I'm much more circumspect on Rally incubating to become part of the integrated release, though20:05
mordredttx: I agree with those sentences20:05
*** tr3buchet1 has joined #openstack-meeting20:05
ttxTo me it sounds like a tool that could happily sit on top of "OpenStack"20:05
devanandao/20:05
zehicle_at_dello/20:05
russellbttx: agreed20:05
jeblairwe've certainly discussed performance testing (especially how hard it is to do right) in the qa context before20:05
ttxrather than "in"20:05
dhellmannthere were some comments about rally (re)producing some things that should be in tempest, did we get more detail about what those are?20:05
boris-42devananda so there is tempest.conf generation20:06
sdaguedhellmann: rally has a bunch of statistics collection and reporting pieces around the tempest subunit output20:06
boris-42dhellmann&20:06
devanandasorry for being a bit late. still recovering from last week.20:06
ttxso in summary: I think Rally fills an important role, performance testing is definitely a good idea, so it should fall into some official program, in QA or separate20:06
sdaguethat's my current main objection of function in the wrong place, as I think that should be part of what any tempest user gets at the end of the run20:06
*** cjellick has quit IRC20:07
boris-42sdague yep but in case of making rally launcher for tempest20:07
*** tr3buchet1 has quit IRC20:07
boris-42sdague we can simplify a lot infra patches20:07
dhellmannthat does feel like it should live closer to tempest in terms of code management20:07
boris-42sdague and end users life20:07
devanandasdague: aiui, rally also instruments many things, even in the absense of tempest20:07
ttxand then I'm not sure it *needs* to be in the integrated release, it can very well live in peripheral tooling20:07
boris-42devananda that is true, but we don't want to make a duplication with tempest20:07
mordredin fact, given experience with no-branch tempest ...20:07
dhellmanndevananda: yes, that's the osprofiler part20:07
annegent_if it's SLA management, is it important to track release? SLA for icehouse for example? And does Rally track now with a cloud in production that's on the tip?20:07
boris-42devananda e.g. for running functional testing we would like to use tempeest20:07
russellbtotally agree perf testing / profiling / benchmarking is important and useful ... but feel it needs to be tightly coupled into the QA group to be successful20:07
mordredwe may not WANT it in the integrated release20:07
annegent_mordred: that's my thinking as well20:08
mordredbecause honestly rally probably wants to be able to run against any release of openstack20:08
sdaguedevananda: entirely possible, the point being rally is highly monolythic today20:08
devanandadhellmann: right. the osprofiler bit, as proposed to oslo, seems to fill an important role20:08
annegent_mordred: right20:08
mordredwhich is out-of-band of releases20:08
boris-42mordred yep20:08
dhellmanndevananda: well, if there's going to be a new program managing this stuff, it doesn't need to go into oslo20:08
sdaguewhich makes it actually really hard to sort out what should and should not be different places, because the architecture doesn't currently support that20:08
*** serg_melikyan has joined #openstack-meeting20:08
mordredI think jaypipes made a good point wrt scalr and that on the mailing list20:08
*** akscram has joined #openstack-meeting20:09
boris-42mordred but seems like it was a bit another story?20:09
*** tr3buchet1 has joined #openstack-meeting20:09
mordredI'm very torn, because I think rally has some great stuff and I support its goals and I think it does things taht are useful to operators20:09
boris-42mordred it was developed by one company and so on20:09
*** Alexei_987 has joined #openstack-meeting20:09
*** evgenyf has joined #openstack-meeting20:09
boris-42mordred yep so the idea is to provide official OpenStack API for that20:09
mordredbut also there are clearly parts and places wehre it wants to collaborate more directly with existing things and that keeps being a struggle20:09
boris-42mordred that will bring tempest to operation level as well20:09
boris-42mordred what about doc that I proposed?20:10
dhellmann#link http://stackalytics.com/?release=all&project_type=stackforge&module=rally20:10
mordredhonestly - as a user of a cloud ... I'm not sure I want an API for this - as much as a tool I can point to clouds20:10
sdaguemordred I agree there is a lot of good stuff in rally, but I think it crosses a lot of existing boundaries, and it would be better to get of the parts into the various "upstreams"20:10
mordredit might be nice for us to be able to easily run rally against hp and rax public cloud in infra to get a sense of how they are doing for workload scheduling purposes20:10
boris-42dhellmann #link http://stackalytics.com/?release=juno&project_type=stackforge&module=rally&metric=commits in juno it's better20:10
boris-42dhellmann community is rising and influence of mirantis is less and less and it is nice20:11
devanandadhellmann: hmm, that piechart has one main ingredient...20:11
*** cjellick has joined #openstack-meeting20:11
boris-42devananda yep cause rally was started by me20:11
boris-42devananda and I am in Mirantis lol=)20:11
mikalSo the board also has their tempest sub set thing20:11
dhellmannsdague: it would be useful to have a more specific list of those things and where they might go as part of an approval process20:11
mikalDo we think that should somehow become part of rally?20:11
annegent_mikal: yeah tcup?20:11
mikalannegent_: yeah, that20:12
russellbmikal: no :)20:12
annegent_and do users expect to be able to point a tool at a cloud? and is rally that?20:12
*** tr3buchet1 has quit IRC20:12
boris-42mordred ?20:12
dhellmannrally is for performance testing, not compliance testing20:12
boris-42mordred could you elaborate we already have performance jobs..20:12
*** yamamoto has joined #openstack-meeting20:12
*** tr3buchet1 has joined #openstack-meeting20:12
mordredboris-42: what I'm saying is, to _me_ it's useful to be able to download rally and run it at endpoints20:12
devanandaboris-42: ok, http://stackalytics.com/?release=juno&project_type=stackforge&module=rally&metric=commits looks somewhat bettr20:12
ttxannegent_: I don't expect rally to be run by end users, it's more geared towards cloud operators20:12
mikalannegent_: they're certainly intending tcup to just be a thing you point at an existing cloud20:12
mordredit's not useful for rally to be an endpoint a cloud exposes to me20:12
annegent_dhellmann: ok, that makes sense, but performance does not equal "meets sla"20:12
sdaguedhellmann: honestly, beyond the statistics collection, no. Honestly, I've not dug in further because rally was always off in a corner doing their own thing20:13
*** Duane has joined #openstack-meeting20:13
boris-42mordred ah*20:13
dhellmannannegent_: agreed20:13
boris-42mordred so the idea is to organize some kind of periodic tasks & benchmarks on demands20:13
boris-42mordred so you don't need to install and setup anything20:13
dhellmannsdague: sure, I didn't mean right now, I just meant if the outcome of the discussion is "well, break it up" then we need to work with boris-42 on how20:13
sdaguedhellmann: honestly, I don't think a tool is for "performance testing" or "compliance testing". I think tools run loads, and produce results.20:13
boris-42mordred just run it20:13
zehicle_at_dellwe've had similar discussions around refstack and these use caes20:13
dhellmannsdague: pedant20:13
dhellmann:-)20:14
*** Duane has quit IRC20:14
sdaguedhellmann: maybe, but I think people are getting too wrapped up with intent, vs. function20:14
boris-42dhellmann heh I am not sure how to split rally on parts20:14
*** HenryG has quit IRC20:14
devanandaboris-42: is the REST API you've proposed end-user facing, or only operator-facing?20:14
boris-42dhellmann the major reasons is that we have resources*20:14
mordredboris-42: yes. I understand. I'm giving you feedback as a large cloud enduser that I do not think that API endpoint is something I would ever use20:14
ttxAt this stage, the reason we want Rally as an official OpenStack project is so that we can rely on it to do QA. Not really to serve a benchmark-as-a-service use case imho20:14
boris-42dhellmann admin-facing (in horizon)20:14
mordredboris-42: but I'm very interested in the ability to run such workloads against endpoints I ahve20:14
boris-42devananda ^20:14
boris-42mordred you will be able20:14
boris-42mordred we are going to support 2 modes20:14
dhellmannsdague: I'm not sure I understand the distinction you're making20:14
jeblairttx: which very deftly illustrates the point: rally's performance testing should be in the qa program20:14
boris-42mordred rally as a service and just rally as a cli tool20:14
boris-42mordred cli tool for hackers like me=)20:15
russellbso rally used to seem dev focused ... the results you give devs to improve their code, and the info you give cloud admins are different things20:15
russellbrally wants to do both?20:15
mordredoh - admin facing service20:15
mordredgotcha20:15
boris-42russellb not only20:15
mordrednot an end-user facing service20:15
boris-42russellb we can track for example such things like how much some request work in specific service20:15
*** cjellick has quit IRC20:15
mordred"how is my cloud doing" - not "how is this cloud over here doing"20:15
russellbi'm also sad that i've never seen any nova results :)20:15
boris-42russellb and then operators can manage such sitatuions20:15
boris-42russellb e.g. keystone started working slow we need to do something20:16
russellbboris-42: sounds like a general monitoring thing20:16
ttxjeblair: doesn't mean it can't move to a more "operators tools" program some day20:16
russellbthat we shouldn't be reinventing20:16
*** cjellick has joined #openstack-meeting20:16
ttxok... so:20:16
dhellmannboris-42: do the tests rally uses require admin rights on the cloud?20:16
boris-42dhellmann at this moment yes20:16
boris-42dhellmann but it's high priority task already for couple of months20:16
ttxI think we want Rally to be an official openstack project living in an official openstack program20:16
boris-42dhellmann and we are quite close to remove it20:16
*** yamamoto has quit IRC20:17
devanandaboris-42: so your goal is for rally-cli to be useful for an  end-user to point at a public cloud?20:17
boris-42dhellmann as well adding support of LDAP20:17
sdaguettx: I'm not convinced that's true in the current state honestly20:17
boris-42dhellmann so you can specify pre created users20:17
ttxit should prove itself necessary, and growing in the QA program is probably the best way to achieve that20:17
sdaguethere needs to be some disagregation first20:17
boris-42dhellmann yep for developers espcially20:17
boris-42devananda ^20:17
jeblairttx: i think we want at least the functionality in an official project20:17
markmcclainttx: +120:17
boris-42devananda that don't want to deploy20:17
russellbi think it'd be nice to see an evaluation from the QA program20:17
sdaguejeblair: agreed20:17
russellband how they think it (or parts) could fit in20:17
dhellmannrussellb: +1, that's what I was trying to get at before20:18
jeblairmtreinish: ^20:18
sdaguejeblair: mtreinish is still traveling back from au IIRC20:18
boris-42dhellmann russellb  does that document makes sense?)20:18
*** manishg has joined #openstack-meeting20:18
ttxbasically, we need rally to fill first and foremost the QA needs. It migth need to be tweaked to achieve that20:18
russellbboris-42: it's very opinionated :)20:18
russellbttx: +120:18
ttxTHEN if it can also be resued by operators, all the better20:18
*** gokrokve has joined #openstack-meeting20:18
ttxrused*20:18
boris-42ttx what do you mean by QA needs?20:19
ttxreused*20:19
*** virmitio has left #openstack-meeting20:19
boris-42ttx ahh so using rally for QA at first step?20:19
ttxboris-42: from what I hear here, there are some concerns on how to best fit and avoid duplication of functionality etc20:19
devanandattx: ++ to that. I'm not yet convinced it should be part of the integrated release, but there's clearly a QA (and eventually operational) need to be filled20:19
boris-42ttx so what we do in rally is reuse tempest =)20:19
ttxsolving that, I thinnk, increases the chances of ultimate success for rally20:19
boris-42ttx sure but what about  current POC that we made?20:20
ttxIt will help evolve it from a monolithic product to something that is really part of openstack20:20
boris-42sdague ^20:20
annegent_I'd like to have us think about where an operator / cloud admin toolset lives, does it have to be a program? Does it have to be integrated releases?20:20
mordredannegent_: ++20:20
*** gokrokve_ has quit IRC20:20
sdagueannegent_: agreed20:20
boris-42annegent_ as far as I understand if it present OpenSatck API20:20
annegent_and boris-42 your user base will be a huge part of that20:20
boris-42annegent_ it should be20:20
ttxI'm not closing the door on an operator tooling program... just sayign it's probably not the right timing for it20:21
boris-42ttx I agree with this20:21
*** fnaval has quit IRC20:21
boris-42ttx we should present this API20:21
mordredboris-42: we're saying we're not sold on it presenting an API - and we'd like to take things one step at a time20:21
boris-42ttx before doing such request=)20:21
ttxboris-42: it doesn't have to be in the integrated release to have an API20:21
jaypipesannegent_: ++20:21
boris-42mordred sure baby steps=)20:21
*** fnaval has joined #openstack-meeting20:22
boris-42mordred ttx  what I am worried that if we will be in QA program20:22
sdagueboris-42: that presuposes a very specific way that people want to consume this, instead of, for instance script to fit tempest runs + results into nagios or jmeter or something else that is already on site and used by operators20:22
annegent_boris-42: I'm a bit more conservative in the shared resources, esp. API docs :)20:22
boris-42mordred ttx  we won't be able to extend scope20:22
mordredboris-42: I believe we're also saying that an important first step is figuring out the code duplication relationship with tempest and the monolithic architeceture concerns20:22
boris-42annegent_ we care about docs=)20:22
boris-42annegent_ so there will be docs=)20:22
*** padkrish has quit IRC20:22
ttxboris-42: I think the TC is worried that if it's on its own program it will never reduce scope.20:22
boris-42mordred so in current POC there is no duplication, if tempest won't start doing performance tests20:22
russellbit actually feels like it's trying to do too much20:23
*** rakesh_hs has quit IRC20:23
russellbwithout having fully accomplished step 120:23
*** padkrish has joined #openstack-meeting20:23
sdagueand never really fit well into an integrated environment20:23
boris-42mordred e.g. functional tests are in tempest, and rally can use them or own performance scenarios for testing20:23
sdaguerussellb: agreed20:23
jaypipesACTION thinks that a more effective (for the OpenStack community as a whole and Rally contrib community specifically) plan is to 1) propose OSProfiler for inclusion in the QA program (immediately), b) Propose to governance repo a new program called Operator Tools, with Rally and maybe a couple other projects like StackTach living in the openstack/ namespace, but not incubated or integrated or anything, and c) havi20:23
jaypipes(i.e. forget about incubation/integration etc20:23
boris-42jaypipes +120:24
boris-42jaypipes unties we present API =)20:24
jaypipesand just do the needful and get these worthwhile projects into an operator program that has code in openstack namespace.20:24
jeblairjaypipes: your (c) was cut off20:24
ttxjaypipes: looks like the TC is converging towards making Rally a part of the QA program, and decline incubation at this point20:24
boris-42unitl*20:24
sdaguehonestly, I still want the parts of rally that make more sense back in tempest, like the results pieces separated out first20:24
mordredsdague: ++20:24
ttxwhich is not exactly matching your (b) above20:24
jaypipessdague: I don't disagree with that at all.20:24
boris-42mordred sdague  why not using rally in gates and everywehre?20:24
*** _nadya_ has joined #openstack-meeting20:25
*** thangp has quit IRC20:25
boris-42mordred sdague  for tempest tests, performance tests and other stuff20:25
mordredboris-42: because we're asking you to take the code that should be in tempest and put it there20:25
jaypipessdague: but there's a chunk of stuff in rally roadmap that simply doesn't belong in QA, and I think we need a place to put that code that isn't stackforge, frankly.20:25
sdagueboris-42: right, because those parts should be back in *tempest*20:25
boris-42mordred we are working on that20:25
sdaguejaypipes: agreed20:25
boris-42sdague agree20:25
jeblairmordred: ++20:25
boris-42sdague mordred actually Rally should just call tempest and store results20:25
sdagueboris-42: the parts that would run in the gate, should all be back in tempest.20:25
boris-42sdague mordred  and do some aggreagtion20:25
*** fnaval has quit IRC20:26
sdagueboris-42: right, and what I'm saying is that whole flow should actually be tempest :P20:26
boris-42sdague nope20:26
ttxjaypipes: isn't being included in the QA program as a first step a way to ensure the QA program will be able to live with Rally, though20:26
jaypipesjeblair: sorry! my c) was: c) having the Rally and QA folks work out the differences and do the needful in terms of libifications <-- in other words, what boris and sean are currntyly talking about ;)20:26
boris-42sdague disagree with this20:26
sdagueand the fact that the rally team ran off in a corner instead of contributing to tempest is a big problem20:26
boris-42sdague there is difference between tempest & rally20:26
boris-42sdague they arch is build for different people20:26
ttxI think there is no point in an operators program growing a Rally that the QA team doesn't like20:26
russellbi think it's a problem that it took until now to figure this out20:26
sdaguerussellb: it didn't take this long20:27
boris-42sdague rally is something that should work out of box with own DB and so on20:27
sdagueI've been providing this feedback to the rally team for the last 6 months20:27
sdagueand just threw up my hands20:27
boris-42sdague tempest is bunch of scripts for creating exactly what you need in your CI20:27
*** padkrish has quit IRC20:27
dhellmannboris-42: so rally supports having test scenarios that are not part of tempest?20:27
russellbsdague: good to hear ... i guess i mean it's unfortunate that a proposal is made when there's clearly still such a big gap20:27
jaypipesttx: well, I think *parts* of Rally do belong in the QA program, along with OSProfiler... but I don't think Rally should just ask to go into the QA program now, then in some short time once pieces are pulled out of it, then propose to start up a new Operator Tools program20:27
boris-42dhellmann yep20:27
devanandaboris-42: the scope diagram in rally's repo includes  "deploy openstack cloud", "run tempest", "benchmark", and "generate report"20:27
boris-42dhellmann cause it is impossible to create any load20:27
*** mwagner_lap has quit IRC20:27
russellbsdague: agree it seems it was "off in a corner"20:27
boris-42dhellmann yep it includes some dev cases that were orignial20:28
boris-42devananda ^20:28
devanandaboris-42: I, for one, am quite concerned that this is duplicatign several existing programs' efforts20:28
boris-42devananda so the idea was just to put some glue for using devstack and other stuff20:28
devanandaboris-42: and agree that it's better for the parts that should be in existing projects to be contributed there20:28
boris-42devananda to deploy on what you have20:28
*** cjellick_ has joined #openstack-meeting20:28
*** fredas has joined #openstack-meeting20:28
boris-42devananda it was dev case at the very begging20:28
boris-42devananda but what I saw from different companies nobody is interested in that20:28
mordredboris-42: right. but the thing is, we ALSO had code to do that20:28
boris-42devananda everybody has own clouds20:28
*** evgenyf has quit IRC20:28
boris-42devananda and they need just to get reports=)20:29
ttxOK, so there is agreement around that the incubation request is not warranted, at least not as this early stage, but still discussion on whether we want Rally in QA or in some operator tooling program20:29
boris-42rudrarug_ or debug=)20:29
jeblairboris-42: i think some of us are having trouble seeing the difference between rally and QA scope.  i think we'd like you to try to work it out and incorporate parts of rally in tempest.20:29
boris-42mordred yep I know20:29
mordredboris-42: so, what I personally need to see from you other than good code is an ability to work within other people's designs20:29
mordredboris-42: and to collaborate with existing programs20:29
mordredit's very important20:29
boris-42mordred but if we can have code in one place that can be reused by everybody20:29
devanandamordred: ++20:29
boris-42mordred it means for me to be "open"20:29
russellbmordred: ++20:29
boris-42mordred I agree20:29
annegent_boris-42: I think it's fine to get the discussion, and we're offering input even early20:29
dhellmannboris-42: sometimes that openness means putting things in the right place, not just in a central place20:30
*** evgenyf has joined #openstack-meeting20:30
*** jamespage_ has joined #openstack-meeting20:30
boris-42devananda sure20:30
boris-42dhellmann sure**20:30
mordredboris-42: so let's suggest this - for now, I think it's very important that you figure out which bits of rally actually need to live in tempest with sdague and then get that work done20:30
vishyso it sounds like the main issue is scope creep20:30
vishyi.e. rally needs to be scoped back down to something reasonable20:30
mordredand once that's underway, it seems like we'll be pretty excited about seeing where we can take the next step with rally20:30
mordredno?20:30
*** kevinostoll has joined #openstack-meeting20:30
ttxWe have other items to cover, and I think we won't solve that one today. We should continue the discussion on the mailing-list and the reviews, based on the feedback we just provided20:30
dhellmannvishy: +120:30
davidlenwellboris-42: if you need help with that refstack has some of the same needs from tempest and I have a few people who need things to do.20:31
vishyhonestly i would throw out the operator stuff completely20:31
vishymake it a dev tool20:31
dhellmannmordred: +120:31
russellbvishy: +++20:31
devanandavishy: ++20:31
boris-42mordred https://review.openstack.org/#/c/94473/20:31
boris-42mordred this is major part20:31
boris-42mordred that should be moved out of rally20:31
devanandavishy: the osprofiler work looks MUCH more useful to operators to me20:31
ttxvishy: that means.. in the QA program :)20:31
*** cjellick has quit IRC20:31
dhellmannvishy, russellb : I see some value in an operator tool to look at the full stack performance20:31
vishysure that is fine20:31
vishybut rally is trying to do both20:31
russellbbut let's start with dev tool20:31
vishystart with one20:31
russellbyes, that20:32
russellband make it really awesome at that20:32
gokrokveAs an operator I would prefer well defined service which provides me an information about my current deployment status, rather then having bunch of scripts I have to know how to run and use.20:32
russellbi mean, i've never seen a single set of results for nova20:32
devanandaboris-42: an initial guess, from a previous operator-of-things. Something like osprofiler + the reporting tools would be helpful for operators. but those tools don't need an API20:32
ttxvishy: yes, that's what I meant by suggesting to grow as a QA use case first20:32
boris-42gokrokve but it's goal of rally..20:32
boris-42gokrokve on operators program20:32
sdaguegokrokve: how do you monitor the monitor?20:32
boris-42devananda they already have actually*=)20:32
boris-42devananda they API is special headers and in python clients --profile20:33
dhellmannboris-42: do you have any links to results handy for russellb ?20:33
boris-42devananda btw could you take a look at spec20:33
gokrokveIf it is a service I can use some tools available. If it is a bunch of tests I cant monitor them at all.20:33
boris-42russellb ?20:33
ttxboris-42: do you agree to abandon the incubation request part ? I think we need to discuss the program placement a bit more20:33
dhellmannrussellb: I've seen a few nice graphs, but didn't save the links20:33
dhellmannboris-42: rally output20:33
boris-42ttx +120:33
russellbdhellmann: don't need to see them this minute ...20:33
boris-42ttx it is not time to incubated20:33
boris-42ttx we should disucss program20:33
ttx#agreed Rally incubation request dropped20:33
boris-42dhellmann russellb one sec20:34
ttx#info Still disagreement on whether Rally should be placed under QA program or new "operators tools"-like program20:34
russellbboris-42: don't worry about it20:34
boris-42russellb btw wanna rally perfroamnce job20:34
boris-42russellb in nova?20:34
russellbi'm more concerned about regular results being provided20:34
*** julim has quit IRC20:34
*** vivek-ebay has joined #openstack-meeting20:34
russellbboris-42: of course20:34
boris-42mordred ^=)20:34
boris-42russellb mordred  we will make a patch then20:34
boris-42russellb https://review.openstack.org/#/c/111973/20:34
boris-42russellb take a look at jenkins output20:34
ttxLet's continue that discussion on the ML and the review, please20:34
boris-42russellb http://logs.openstack.org/73/111973/1/check/gate-rally-dsvm-rally/cd94a94/20:35
boris-42russellb in rally-plot you have different presentation of result20:35
boris-42russellb it some kind of functional testing of rally20:35
boris-42russellb this is what was actually run https://github.com/stackforge/rally/blob/master/rally-scenarios/rally.yaml20:35
boris-42russellb sla: max_failure_precent means that job will fail if any of iteration in scenario will fail20:36
dhellmannttx: do you mean discuss the operators tool program on the ML?20:36
ttxI mean present the two options and gather pros/cons20:36
* dhellmann nods20:36
*** jprovazn has quit IRC20:36
ttxI would like ot be sure that the QA team would take it, too20:36
*** padkrish has joined #openstack-meeting20:36
boris-42ttx dhellmann one more thread?20:37
ttxand I think there needs to be more education and reflection on that topic, we won't choose today20:37
*** cjellick_ has quit IRC20:37
mordred++20:37
boris-42ttx +120:37
ttxand we have other topics to cover.20:37
boris-42=)20:37
ttx#topic Integrated projects and new requirements: Gap analysis for Swift20:37
*** openstack changes topic to "Integrated projects and new requirements: Gap analysis for Swift (Meeting topic: tc)"20:37
notmynamehello20:37
ttxnotmyname: o/20:37
* ttx considers having two TC meetings per week20:38
ttx#link https://etherpad.openstack.org/p/swift_gap_analysis20:38
ttxSo.. swift is the last currently-integrated project to go through this20:38
notmynamesorry I couldn't make it a few weeks ago20:38
*** nelsnelson has quit IRC20:38
ttxthe goal again is to make sure currently-integrated projects match the requirements we place on new projects20:39
mordredttx: jogo wants us to meet daily you know ...20:39
ttxand if there is any gap, we have a plan to address it20:39
*** berendt has quit IRC20:39
annegent_so swift didn't get a cease and desist from Apple? :) I kid, I kid.20:39
ttxannegent_: they got one from Taylor Swift20:39
*** vivek-ebay has quit IRC20:39
notmynameheh20:39
annegent_ttx: NO20:39
*** cjellick has joined #openstack-meeting20:40
* dhellmann believes it20:40
*** penick_ has quit IRC20:40
mikalI think John should sing more Taylor Swift songs at summits20:40
* mordred sends Taylor Swift a C&D20:40
*** Alexei_987 has left #openstack-meeting20:40
* mordred is pretty sure his last name was Taylor before she was born20:40
dhellmannmikal: +120:40
*** AlexF_ has joined #openstack-meeting20:40
mordredmikal: ++20:40
ttxnotmyname: so... we have one well-known difference, not sure we can consider it a gap though...20:40
notmynamettx: I agree with that statement :-)20:40
*** vivek-ebay has joined #openstack-meeting20:40
ttxwhich is that swift has its own intra-cycle release schedule20:40
russellbrelease cycle?20:40
*** AlexF_ has quit IRC20:41
ttxWe basically special-case Swift, of all the integrated release pieces, in release scripts to support that... difference20:41
dhellmannew20:41
*** vivek-ebay has quit IRC20:41
notmynamewe fully participate in the integrated release20:41
notmynamebut instead of milestones, we have semantically versioning releases20:42
* reed announces Taylor Swift will be in Paris20:42
*** vivek-ebay has joined #openstack-meeting20:42
*** eglynn has quit IRC20:42
mordredalso, I'm not sure I agree with the answer to * Project should use oslo libraries or oslo-incubator where appropriate20:42
russellbon a different schedule, not just the naming20:42
dhellmannnotmyname: "we do what you want, but something different"?20:42
ttxSpecific versioning which also triggers that special-casing in release scripts20:42
annegent_reed: NO :)20:42
*** radez is now known as radez_g0n320:42
devanandareed: lol20:42
mordredgiven there is no use of oslo whatsoever, I don't think "done" is the right answer20:42
russellbmordred: agreed20:42
annegent_mordred: but they just started using oslosphinx :)20:42
notmynamemordred: jsut today I merged using oslosphinx :-)20:43
mordrednotmyname: neat!20:43
dhellmannannegent_: I'm more interested in oslo.config20:43
mordred:)20:43
*** AlexF_ has joined #openstack-meeting20:43
annegent_dhellmann: Actually, yah, me too20:43
annegent_docs team had to write a scraper20:43
* mordred doesn't necessarily want to push for a particular change - just wants to call a spade a spade20:43
annegent_for config options20:43
dhellmannannegent_: so that's 2 teams special casing things for swift?20:43
ttxnotmyname: I just want to make sure we are different there for a reason -- I just don't want each integrated project to come up with their own variation of release schedule20:43
*** dprince has quit IRC20:43
ttxand if we grant swift an exception, that it's documented as an exception20:44
notmynamettx: ok, so there's a few things going on here so far. hard to handle 2 conversations20:44
notmynamettx: which do you want first?20:44
ttxI was first20:44
ttx:)20:44
notmyname:-)20:44
*** kevinbenton has quit IRC20:44
notmynameok, release cycle20:44
ttxbasically we force new projects to follow the common cycle20:44
ttxincluding dev milestones20:44
notmynamehttps://wiki.openstack.org/wiki/Release_Cycle20:44
notmynamesee the 3rd paragraph20:45
ttxI'm fine to keep the swift exception, but I want to make sure we are doing it for the right reason, and that it's seen as an exception20:45
notmynamethere are a few reasons we do the releases the way we do20:45
notmynamefirst, historical reasons. that's not always a reason to keep doing something some way, but it is one reason20:46
ttxwe no longer give that choice to new projects20:46
mikalI don't personally have a problem with swift's release cycle, and we can always tell new projects that its different for historical reasons20:46
ttxmikal: I would be fine with that20:46
ttxit's different for historical reasons20:46
russellbit affects more than just new projects20:46
russellbit's also a complication for anyone consuming openstack releases20:46
jeblairlet's see if there's any reason other than historical to keep doing it20:46
russellbso it comes at a cost to keep it20:46
markmcclainjust because we've always done something that way doesn't mean we shouldn't consider aligning20:46
dhellmannI would like to understand more about why it's different, though, because "we've always done it that way" isn't really much of a reason20:47
*** IanGovett has joined #openstack-meeting20:47
notmynameI've asked operators at just about every one of the last 4-5 summits, and have been told that they like it. therefore, from swift deployers, I've not heard a request to change it20:47
notmynamemarkmcclain: certainly. I only wanted to point that out20:47
*** cjellick has quit IRC20:47
dhellmannnotmyname: did you ask them if it would bother them if you did change?20:47
russellband are these people only using swift?20:47
ttxnotmyname: don't you think that... difference is also what's causing people to see swift as different and optional in an openstack deployment, though?20:48
ttxI think it cuts both ways20:48
*** cjellick has joined #openstack-meeting20:48
dhellmannttx: +120:48
notmynamedhellmann: most of it is over casual conversation or "poll the room" sort of stuff. some said that's what they liked. it's come up in the design sessions several times.20:48
markmcclainnotmyname: what are the technical/project management benefits to the unique schedule?20:48
ttxmarkmcclain: basically, they do feature-badsed releasing20:49
vishyaccess to features sooner20:49
ttxand also release more often20:49
notmynamemarkmcclain: it works for those who are contributing to and deploying swift. IOW it's not broken from the perspective of those writing the code20:49
dhellmannnotmyname: right, but if the question is "is what we're doing now working for you" that doesn't tell you anything about whether changing would be bad20:49
*** julienvey has quit IRC20:49
*** banix has quit IRC20:49
ttxwhich, given that they are really more stable that the rest of openstack, kind of make sense (faster cadence)20:49
*** crc32 has joined #openstack-meeting20:49
notmynameto be very explicit here, I'm not 100% opposed to changing it. but changing does have a cost (as does keeping it).20:50
annegent_it's a headache to explain in docs, doesn't mean we won't keep doing it for historical reasons, I mean, Google indexes stuff forever20:50
*** fnaval has joined #openstack-meeting20:50
notmynamettx: right. I think the faster access to features and stability has been well-demonstrated over the last 4+ years of semver releases20:50
russellbit's a headache for planning from a distro perspective, too20:50
ttxnotmyname: I think we can consider this an identified "difference" and discuss the pros/cons of alignment20:50
ttxin future discussions20:50
notmynamerussellb: how? distros take the integrated release. which we fully participate in20:50
russellbnotmyname: it's everything in between20:51
notmynamettx: ack20:51
ttx#info identified difference (which needs analysis and justification): different release schedule20:51
ttxnotmyname: maybe address the second concern now20:51
notmynameoslo.config20:51
*** evgenyf has quit IRC20:51
dhellmannlet's talk oslo in general, that was just one example20:51
*** balajiiyer has joined #openstack-meeting20:51
notmynameok, oslo in general20:52
*** jamespage_ has quit IRC20:52
notmynamefirst, we are not going to accept the copy/pasted code externally managed. if it's a library available upstream, then let's consider it20:52
notmynameif it is available, then there are a few questions20:52
notmynamedoes it fix something that is broken20:52
ttxI think in both cases we need to have an open discussion on why being different has more benefits than drawbacks, to justify the unique case20:53
*** balajiiyer has quit IRC20:53
notmynameand what is the impact to deployers (dependencies and upgrades)20:53
*** balajiiyer has joined #openstack-meeting20:53
*** banix has joined #openstack-meeting20:53
dhellmannyeah, I'm less worried about the incubator use. if you don't want that, I don't want to waste time arguing. You'll just have less input into the APIs of the libraries, and I do expect you to use those20:53
notmynamespecifically, oslo.config has grown up after swift's config stuff (which does work) has settled. so I'd be happy to discuss that one in particular20:53
ttx#info identified difference: oslo library adoption20:53
*** andreykurilin1_ has quit IRC20:53
ttxnotmyname: it's also a "be more openstack" or "be less openstack" question imho20:54
*** tzabal has left #openstack-meeting20:54
russellbreally, they both are20:54
jeblairbroken for deployers can also mean for new deployers.  the differences in config and logging across openstack projects are burdensome for people deploying the whole thing.20:54
annegent_ttx: and does a defcore inclusion discussion belong in a gap analysis?20:54
mordredjeblair: ++20:54
ttxnotmyname: given the project history you 're fine with not being openstack where it doesn't help you, but as I said it cuts both ways20:54
russellbannegent_: imo, no20:54
dhellmannjeblair: right, that's a bit reason for oslo to even exist20:55
dhellmann*big20:55
ttxbeing "less openstack" left the door more open to alternate solutions20:55
annegent_russellb: seems like it was already tc-discussed but just checking20:55
mikalannegent_: so, the tc said "integrated release", right?20:55
notmynamettx: I don't like the characterization of "we don't do X, therefore we aren't "more openstack""20:55
mikalannegent_: so I think we've designated swift as code to ship for defcore20:55
ttxnotmyname: see jeblair remark above20:56
russellbnotmyname: but it's when *everyone* else does X20:56
*** kevinbenton has joined #openstack-meeting20:56
annegent_mikal: yep20:56
russellband is happily doing it to converge20:56
ttxnotmyname: for someone that deploys "openstack", swift is configured slightly differently, logs slightly differently20:56
zehicle_at_dellmikal, I thought that the TC chose to get out of designating code20:56
mikalzehicle_at_dell: well, we said we wanted all of the integrated release to be designated20:57
dhellmannrussellb: +120:57
mikalzehicle_at_dell: but that the board could override us if they wanted20:57
russellbmikal: not exactly ...20:57
dhellmannplease let's not re-open that discussion20:57
mordredzehicle_at_dell: what mikal said20:57
russellband that's a totally different topic anyway20:57
zehicle_at_dellmikal, that's not what I remember.20:57
mikalzehicle_at_dell: but this is a side line, let's keep to swift20:57
ttxBut these are difficult questions, that's why I'm not calling them "gaps", as swift lived with those pretty happily so far20:57
dhellmannzehicle_at_dell: we are not talking about defcore right now, please20:57
annegent_sorry, did not mean to derail gap analysis20:57
zehicle_at_delldhellmann, I did not bring it up... was addressing a statement20:57
ttxok, 3 minutes left -- any other area of difference or gap ?20:57
ttxI think we need to have a frank discussion on each of those, but could be a summit thing too, not really urgent20:58
notmynamettx: to summarize oslo usage, there are areas where we do not us oslo where functionality may need to be considered20:58
ttxbut we need to call out all areas20:58
*** banix has quit IRC20:58
ttxwhere current requirements do not fit the swift use case20:58
ttxanything else than release cycle and oslo adoption ?20:58
ttxthere is a blurb about "lifecycle of resources managed by the project should be externalized via notifications"20:59
*** jjmb1 has joined #openstack-meeting20:59
russellbthat falls under the oslo topic to me20:59
ttxnot sure swift does that, but then...20:59
ttxok20:59
notmynamettx: ya, what is that?20:59
dhellmannrussellb: I think that's more for ceilometer integration20:59
russellboslo.messaging notifications21:00
russellbevery other project uses that21:00
*** jjmb1 has quit IRC21:00
ttxok, that falls into the oslo bucket21:00
ttxI think we identified the two key areas then21:00
ttxnotmyname: i'll be in touch on how we can have a healthy discussion about those21:00
notmynamettx: ok21:00
annegent_there's the separate auth that then enables non-keystone installs, but that's not a big concern I don't think, and makes sense for the object storage use21:00
* ttx rushes through a few items21:00
ttx#topic Other governance changes21:01
*** openstack changes topic to "Other governance changes (Meeting topic: tc)"21:01
ttx* Add repository glance.store to glance (https://review.openstack.org/107585)21:01
ttxThis one is missing markwash's +1, then if nobody objects I'll approve it21:01
ttx* use ">" to indicate multiline mission statements (https://review.openstack.org/109021)21:01
ttxThis one is cosmetic, will approve now unless someone yells21:01
ttx#topic Open discussion21:01
*** openstack changes topic to "Open discussion (Meeting topic: tc)"21:01
ttxFamous last words ?21:01
dhellmannin case anyone doesn't know, I've moved from Dreamhost to HP. My new email is doug@doughellmann.com, so please update your address books.21:01
* mordred wins21:01
russellbheh21:02
ttxdhellmann: noted and congrats and all.21:02
dhellmannthanks :-)21:02
vishycan we propose a moratorium on mordred’s hiring practicies21:02
annegent_heh21:02
ttxRemember to think of names to suggest for our user committee nominee21:02
vishyother companies need good engineers too :)21:02
mordredvishy: want a job?21:02
devanandaheh21:02
ttxAlso I raised a "winter is coming" thread about the integrated release21:02
mikalWell, we need to talk about TC balance at some point21:02
reedlol21:02
ttxyou might want to chime in there21:02
russellbmordred: hiring the whole TC?21:02
* mordred may have also responded to ttx winter is coming thread ..21:03
devanandattx: thanks. that's been on my mind (probably all of our minds, I think)21:03
* mordred is sharpening his axe21:03
dhellmannmikal: fwiw, we talked a lot more about oslo than the tc21:03
markmcclainttx: thanks for raising that thread21:03
ttxIf people contributed to the Night Watch we wouldn't have that problem again21:03
ttx#endmeeting21:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:03
openstackMeeting ended Tue Aug  5 21:03:32 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:03
mikaldhellmann: oh, I'm not implying that there is a a hidden agenda21:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-08-05-20.02.html21:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-08-05-20.02.txt21:03
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-08-05-20.02.log.html21:03
mikaldhellmann: just that we should check the bylaw requiremetns for TC diversity21:03
mordredrussellb: they tell me we're spending $1B - I gotta figure out how to put at least some of it to use21:03
russellbthat's a lot.21:03
ttxmikal: not reached yet afaik21:03
ttxnext meeting21:04
dhellmannmikal: IIRC, that was just the board because it's not a general election, but I could be wrong.21:04
mordredrussellb: seems like a lie to me ...21:04
dhellmannmikal: but I do see your point, and did spend some time thinking about it before making my decision21:04
*** marcoemorais has quit IRC21:04
russellbmordred: sounds nice though21:04
*** vivek-ebay has quit IRC21:04
ttxdhellmann, dolphm, notmyname, eglynn, markwash, jgriffith, mikal, zaneb, david-lyle, mestery, SlickNik, SergeyLukjanov: around ?21:04
russellbmarkmcclain: you sticking around for this?21:04
dhellmanno/21:04
mikalttx: hi21:04
notmynamehere21:05
*** marcoemorais has joined #openstack-meeting21:05
zanebo/21:05
ttx#startmeeting project21:05
markmcclainrussellb: yep filling in today21:05
openstackMeeting started Tue Aug  5 21:05:13 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:05
*** VijayB_ has quit IRC21:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:05
*** openstack changes topic to " (Meeting topic: project)"21:05
openstackThe meeting name has been set to 'project'21:05
ttxAgenda for today is available at:21:05
mordredmikal: just to be clear though - if you ever feel as if any of the people working for me actually represent the views of HP, please tell me and I'll have them whipped21:05
*** cschwede has quit IRC21:05
*** vivek-ebay has joined #openstack-meeting21:05
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:05
mikalmordred: lol21:05
* devananda retires from the meetings, gets some more rest, and plans to read the project meeting logs later21:05
ttx#topic Program news21:05
*** openstack changes topic to "Program news (Meeting topic: project)"21:05
david-lyleo/21:05
ttxWe skipped 1:1 syncs today except for Nova (which was skipped last week)21:05
ttxSo the log only includes Nova this week:21:05
ttx#link http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-08-05-08.04.html21:06
ttxIf you have news, you can speak now in #info lines21:06
* SergeyLukjanov here21:06
ttxAnything worth mentioning ?21:06
*** SlickNik has joined #openstack-meeting21:06
*** VijayB_ has joined #openstack-meeting21:06
ttxOK then, probably not... one single item on the agenda then21:07
ttx#topic Nova/Neutron migration and other Neutron gaps21:07
*** openstack changes topic to "Nova/Neutron migration and other Neutron gaps (Meeting topic: project)"21:07
ttxAt the TC meeting last week we reviewed progress on the integration gap coverage plans21:07
ttxNeutron was flagged as needing extra discussion, especially where progress affects Nova21:07
ttxSo we decided to abuse a cross-project meeting to discuss that, since it's really a cross-project issue :)21:07
ttxlast week we skipped it due to nova mid-cycle meetup21:08
russellbjay pipes started a thread about this21:08
ttxso it's happening today21:08
russellb#link http://lists.openstack.org/pipermail/openstack-dev/2014-August/041931.html21:08
*** jjmb has joined #openstack-meeting21:08
sdaguethere was also much discussion at the nova meetup about this given that markmcclain was there21:08
*** coolsvap has quit IRC21:08
*** eglynn has joined #openstack-meeting21:08
mikalYeah, it was good of him to come21:08
mikalVery helpful21:08
* eglynn joins the fun belatedly ...21:09
russellbkind of seems best to continue that thread ... everyone has been in support of cold migration so far21:09
russellbanyone here *not* like that?21:09
*** aysyd has quit IRC21:09
mikalI am ok with that, noting that some people have already done hot migrations21:10
dhellmannseems like a good approach to me, for the reasons stated in the thread21:10
markmcclainI think that documenting cold migration makes the most sense21:10
clarkbalso worth noting that infra/qa is working on making it possible to test this stuff with grenade21:10
*** MarkAtwood has joined #openstack-meeting21:10
russellbclarkb: fancy21:10
clarkbmarkmcclain: so we may have a bit more than just documentation to give people21:10
*** flaviof is now known as flaviof_zzz21:10
dhellmanncool21:10
markmcclainclarkb: cool21:10
russellband as far as the TC is concerned, as long as the two projects are in agreement, we should be fine in terms of the gap21:10
russellbas the requirements are just that a plan of some sort exists, and both projects agree to it21:11
*** jjmb has joined #openstack-meeting21:11
*** jjmb has quit IRC21:11
sdaguerussellb: agreed. I think it's more realistic of what people will actually do as well.21:11
russellbagreed21:11
markmcclain+!21:11
*** yamamoto has joined #openstack-meeting21:11
*** jjmb has joined #openstack-meeting21:11
mikalHeh21:11
*** jjmb has quit IRC21:11
*** jjmb has joined #openstack-meeting21:12
russellbwe all just very peacefully agreed, how nice :)21:12
mikalWe can argue for a bit if you want21:12
ttxwhat what21:12
dhellmanngo team! :-)21:12
mikal:P21:12
russellbnah.21:12
sdagueheh21:12
*** redrobot has joined #openstack-meeting21:12
markmcclainI'll update the wiki to reflect the change21:12
mikalIf someone really really needs a non-cold migration, they can help develop it21:12
russellb#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee/Neutron_Gap_Coverage21:12
sdaguethat being said, something that was slid past was scaling issues in neutron itself.21:12
*** yamamoto_ has joined #openstack-meeting21:12
*** penick has joined #openstack-meeting21:12
sdagueat least at the meetup21:12
*** yamamoto has quit IRC21:12
russellbi think 7 is in the biggest need of clarification21:12
russellbi considered 7 to be the gap that was supposed to cover scaling issues21:13
sdagueand it's worth noting that we're actually finding elastic recheck bugs that we were tracking in the gate in nova show on both rax and hp cloud21:13
russellbbasically, "neutron with open source plugins needs to not suck more"21:13
*** pdmars has quit IRC21:13
russellbi started trying to add more verbiage here: https://etherpad.openstack.org/p/neutron-gap-clarification21:13
clarkbI will send mail about what sdague says shortly21:13
sdagueas in the reasons nodepool gets slow is that neutron falls over21:13
sdagueyeh, clarkb has all the details21:14
* ttx prefers "cold migration" soon rather to "hot migration at the end of time"21:14
russellbttx: +121:14
russellbmarkmcclain: see that link ^^21:14
mikal+121:14
russellbwe really need to nail down gap 7 ...21:14
russellbwhat 7 is supposed to cover i mean21:14
*** coolsvap has joined #openstack-meeting21:14
markmcclainrussellb: yes21:15
russellband would like to update the wiki with the updates to 5,6,7 once there's some consensus around it21:15
russellbposted that to TC list, but no feedback21:16
markmcclaingap7 is only change we might to refine further21:16
markmcclain'par' is too fuzzy of term21:17
*** yamamoto_ has quit IRC21:17
*** cjellick has quit IRC21:18
russellbmarkmcclain: yep, don't have anything concrete21:18
russellbwhich is a problem, of course21:18
russellbi think a write-up of known stability / scalability issues is a good place to start21:19
russellband that could include a summary of work done over the last release or 2 to improve things21:19
mikalThat seems like a fair approach21:19
mikalInstead of just saying "fix everything"21:19
ttxmarkmcclain: should we move to juno-3 all the juno-1 and juno-2 targets in that doc ?21:19
mikalThat could even be just a list of bugs in LP with a tag21:19
russellbbasically need to convince folks that neutron with an open source backend will be as stable and scalable as nova-network21:19
russellbthat's the key21:19
russellbbecause right now a lot of people aren't convinced21:19
russellbthat's the gap i think21:20
markmcclainok that's fine I think we can develop the set of tested limits21:20
russellbok21:20
*** jasondotstar has quit IRC21:20
ttxrussellb: that's a good way of looking at it, yes21:20
*** zehicle_at_dell has quit IRC21:20
ttx"convince folks that neutron with an open source backend will be as stable and scalable as nova-network"21:20
russellbyeah, maybe that's what the gap should say21:21
*** e0ne has quit IRC21:21
russellbanyway, that's all i had for this topic i think21:21
ttxis anyone editing the wiki page, or should I take the lock?21:21
* russellb is not21:21
* markmcclain is not21:21
mikalNope21:21
russellbttx: you see my proposed updates on the etherpad?21:21
ttxok, I'm in21:21
*** e0ne has joined #openstack-meeting21:21
russellbthough some of it is stale already21:21
ttxmarkmcclain: "Gap 3: Neutron as the default in devstack" -> should I move the completion taregt to j3 ?21:22
markmcclainyes21:22
markmcclaingap5  (DVR) is basically done with a few small cleanups in review21:23
markmcclaindiscussed with others on neutron team work on better scale metrics for this milestone21:23
*** lcheng has quit IRC21:23
russellbmarkmcclain: did we ever have the thread about DVR requiring OVS?21:24
* russellb didn't see it21:24
ttxmarkmcclain: is gap 5 done to the point where DVR can be used as eeplacement for Nova multi-host ? Or more work still in-flight to fully support that?21:25
markmcclainttx: it is a functional replacement for multi-host21:25
ttxis it usable enough at this point to serve as a functional replacement?21:25
markmcclainrussellb: the first pass was implementing for OVS since that will perform the best21:25
russellbi'm not sure anyone actually cares21:26
markmcclainrussellb: supporting linuxbridge was on the list for follow up21:26
ttxtrying to see if we can consider it closed, from the gap coverage perspective21:26
russellbi just want to air the question so we have record to point to21:26
russellbttx: i think one last thread is needed21:26
ttxok21:26
russellbpropose that OVS is a requirement21:26
russellband see if anyone objects21:26
*** mspreitz has quit IRC21:26
sdaguerussellb: ++21:26
*** denis_makogon has quit IRC21:26
*** joesavak has quit IRC21:26
russellbprobably not honestly21:26
russellbbut i don't want to assume that21:27
* lifeless is heartily in favour of requiring ovs ;)21:27
sdagueI would only suggest backfilling linuxbridge if people flip out, because I expect at this point most people to be getting on the ovs band wagon21:27
*** e0ne has quit IRC21:27
*** js1123 has joined #openstack-meeting21:27
markmcclainrussellb: I think that linuxbridge can be feasible if we someone to test and shepard any bug fixes21:27
*** eankutse has quit IRC21:27
markmcclainthe ops that want DVR all wanted OVS21:27
ttxok, I edited gap5 status on the wiki21:27
sdaguemarkmcclain: yeh, but I think just putting a stake in the ground and saying you won't is fine as well as long as it's called out21:27
russellbyep21:28
ttxhmm, I should probably use your text, russellb21:28
markmcclainsdague: I'm fine with that21:28
russellbttx: up to you, but it's there if you'd like to use it.  that was the intention :)21:28
ttxrussellb: if markmcclain feels like it matches his status, I'll just copy-paste it now21:29
markmcclainthat works21:30
*** hrybacki has joined #openstack-meeting21:30
ttxok, copypasting...21:30
*** AlexF_ has quit IRC21:30
*** marekd is now known as marekd|away21:31
ttxok saved21:32
russellblgtm21:33
russellbthanks!21:33
ttxmarkmcclain: feeling confident that we can close all in j3?21:33
markmcclainI am… live migration was the one I was most worried about21:33
russellbi'm at least feeling confident that enough good progress will have been made that we should call this cycle a success21:34
mikalExcellent21:34
russellbeven if some bleeds into next cycle21:34
markmcclainnow that we've have another path the other options should items we can close21:34
*** baoli has quit IRC21:35
*** tsekiyama has joined #openstack-meeting21:35
*** rockyg has quit IRC21:36
*** Murali__ has joined #openstack-meeting21:36
*** f13o_ has joined #openstack-meeting21:37
markmcclainttx: looks like you've published the updated wiki?21:37
*** neelashah has quit IRC21:37
ttxyes: <ttx> ok saved21:37
*** annegent_ has quit IRC21:37
ttx#topic Open discussion21:37
*** openstack changes topic to "Open discussion (Meeting topic: project)"21:37
*** hashar has joined #openstack-meeting21:37
markmcclainttx: thanks missed that21:37
*** IlyaE has quit IRC21:39
*** tbarron has quit IRC21:39
jeblairclarkb: ping21:39
*** vijendar has quit IRC21:39
*** Murali_ has quit IRC21:40
*** rudrarug_ has quit IRC21:40
*** rudrarugge has joined #openstack-meeting21:40
sdaguejeblair: we could proxy clarkb's request21:41
clarkboh pong21:41
clarkbsorry21:41
jeblairoh yay21:41
clarkbso a couple related things are coming up21:41
*** jjmb has quit IRC21:41
clarkbI am going to switch the zuul default test node type for all projects to trusty in ~2weeks21:42
clarkbit is currently precise with a bunch of projects set to trusty. All of the integrated projects should be on trusty at this point so not a huge change there21:42
clarkbthe second thing, and I will do this at the same time is, upgrading tox to tox 1.7.2 on all of our test nodes21:43
clarkbyou have probably seen some of my hash seed overrides in tox.ini to make that happen without breaking everything21:43
*** jungleboyj has quit IRC21:43
jeblair(for clarity: stable branches and other exceptions do and will still use precise as appropriate)21:43
*** henrynash has joined #openstack-meeting21:43
*** balajiiyer has quit IRC21:43
clarkbwe need to get those hash seed override changes merged or fix the tests otherwise new tox will break you21:44
clarkbnow this is important so that we can move python3 testing to py34 on trusty as old tox doesn't grok py34. And it will allow us to go back to not caring a whole lot about which version of tox we have installed which has been annoying21:44
dhellmannclarkb: I started running some tests for oslo last week, but didn't finish before my break. Did you do that, or should I continue that work and let you know how it goes?21:44
sdaguettx: so specifically reviews like - https://review.openstack.org/#/c/109751/ - which you have a -2 on21:44
clarkbdhellmann: you should continue doing that and if you give me a list of things you haven't tested yet I cna help too21:45
ttxsdague: ack, needs merge in master first21:45
*** adahms has joined #openstack-meeting21:45
ttxsdague: or do you mean that should go in stable/* FIRST?21:46
jeblairttx: i'm not sure this is the kind of change that rule needs to be applied to21:46
clarkbI intend on sending mail to the list once I can hammer down what my schedule looks like21:46
*** balajiiyer has joined #openstack-meeting21:46
sdaguettx: they should go everywhere all at once21:46
jeblairttx: i think it can go in parallel21:46
sdaguewhat jeblair said21:46
clarkbdhellmann: maybe we can coordinate on that thread and make sure everything is happy21:46
ttxjeblair: OK, no technically a backport21:46
sdaguettx: this is not so much a backport as a "not have everything die in a fire"21:46
jeblairttx: correct21:46
ttxhrm, we have a freeze on stable/icehouse until Thursday... can that wait until then ? Or should I plead to the stable dudes?21:47
clarkbttx: it can probably wait until thursday21:47
ttxi can approve the stable/havana one21:47
clarkbttx: I expect to do this in about 2 weeks. that should give us plenty of time to iron out and merge the things we need to merge21:48
sdaguettx: realize that anyone trying to run the tarballs with new tox for local QA will explode21:48
sdagueso there might be value in getting it into the release21:48
*** sdake has quit IRC21:49
ttxsdague: ok +2/APRVed for stable/havana21:49
*** julienvey has joined #openstack-meeting21:50
*** gokrokve has quit IRC21:50
markmcclainI agree with sdague and the risk is really low21:50
sdagueyeh, the risk is very low. All it does is force a python random see for unit tests21:51
sdaguebecause new tox randomizes that, which is good practice21:51
*** henrynash has quit IRC21:51
ttxI removed my -2 on the stable/icehouse one... just frozen until Thursday now21:51
sdaguebut a lot of our unit tests assume hash ordering21:51
sdaguewhich is bad21:51
ttxSo in other news, we'll have a 2014.1.2 this week21:51
ttx#info Upcoming 2014.1.2 stable release21:52
ttxAnything else, anyone ?21:52
ttxguess not21:53
ttx#endmeeting21:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:53
openstackMeeting ended Tue Aug  5 21:53:40 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2014/project.2014-08-05-21.05.html21:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2014/project.2014-08-05-21.05.txt21:53
ttxThanks everyone!21:53
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2014/project.2014-08-05-21.05.log.html21:53
*** julienvey has quit IRC21:54
SergeyLukjanovttx, thx21:55
SergeyLukjanovttx, btw we're going to have 2014.1.2 for sahara too (probably a few days later then other projects)21:56
ttxSergeyLukjanov: ack21:56
*** MarkAtwood has quit IRC21:58
*** topol has quit IRC21:59
*** ivasev has quit IRC22:00
*** JRobinson__ has joined #openstack-meeting22:00
*** fredas has quit IRC22:04
*** jaypipes has quit IRC22:05
*** pballand has quit IRC22:05
*** Murali__ has quit IRC22:07
*** yamamoto has joined #openstack-meeting22:07
*** Murali_ has joined #openstack-meeting22:07
*** MarkAtwood has joined #openstack-meeting22:08
*** drankis has quit IRC22:10
*** prad has quit IRC22:11
*** IlyaE has joined #openstack-meeting22:11
*** BadCub has quit IRC22:13
*** esheffie2d has quit IRC22:14
*** trey_h_ has quit IRC22:14
*** BadCub has joined #openstack-meeting22:15
*** esheffie1d has joined #openstack-meeting22:15
*** trey_h has joined #openstack-meeting22:15
*** armax has quit IRC22:16
*** hashar has quit IRC22:16
*** ignacio-scopetta has quit IRC22:17
*** trey_h has quit IRC22:19
*** emagana_ has quit IRC22:20
*** emagana has joined #openstack-meeting22:20
*** emagana has quit IRC22:20
*** emagana has joined #openstack-meeting22:21
*** atiwari has quit IRC22:22
*** julienvey has joined #openstack-meeting22:22
*** jjmb has joined #openstack-meeting22:27
*** julienvey has quit IRC22:27
*** vivek-ebay has quit IRC22:28
*** jolyonbrown has quit IRC22:28
*** rudrarug_ has joined #openstack-meeting22:28
*** VijayB_ has quit IRC22:29
*** sdake has joined #openstack-meeting22:31
*** sdake has quit IRC22:31
*** sdake has joined #openstack-meeting22:31
*** rudrarugge has quit IRC22:31
*** atiwari has joined #openstack-meeting22:32
*** VijayB has joined #openstack-meeting22:32
*** trey_h has joined #openstack-meeting22:32
*** rudrarug_ has quit IRC22:33
*** masayukig has quit IRC22:34
*** trey_h has quit IRC22:37
*** shashankhegde has quit IRC22:37
*** Murali__ has joined #openstack-meeting22:38
*** flaviof_zzz is now known as flaviof22:38
*** masayukig has joined #openstack-meeting22:40
*** tr3buchet is now known as asdf22:41
*** shashankhegde has joined #openstack-meeting22:41
*** asdf is now known as rrefsss22:41
*** Murali_ has quit IRC22:42
*** stu has joined #openstack-meeting22:44
*** stu has quit IRC22:44
*** eglynn has quit IRC22:45
*** pballand has joined #openstack-meeting22:45
*** atiwari has quit IRC22:45
*** david-lyle has quit IRC22:46
*** david-lyle has joined #openstack-meeting22:47
*** Murali__ has quit IRC22:47
*** rediskin has left #openstack-meeting22:48
*** vivek-ebay has joined #openstack-meeting22:48
*** Murali_ has joined #openstack-meeting22:49
*** Murali_ has quit IRC22:50
*** changbl has quit IRC22:50
*** david-lyle has quit IRC22:51
*** banix has joined #openstack-meeting22:51
*** rudrarugge has joined #openstack-meeting22:51
*** ayoung has quit IRC22:51
*** vivek-ebay has quit IRC22:53
*** rrefsss is now known as stupidffffff22:53
*** jgrimm has quit IRC22:55
*** otherwiseguy has quit IRC22:56
*** mattgriffin has quit IRC22:56
*** yeungp has quit IRC22:57
*** stupidffffff has quit IRC22:57
*** emagana has quit IRC22:58
*** emagana has joined #openstack-meeting22:58
*** oanufriev has joined #openstack-meeting22:59
*** armax has joined #openstack-meeting22:59
*** eglynn has joined #openstack-meeting23:01
*** kevinconway has quit IRC23:01
*** atiwari has joined #openstack-meeting23:02
*** emagana has quit IRC23:02
*** padkrish has quit IRC23:04
*** padkrish has joined #openstack-meeting23:05
*** andreykurilin_ has quit IRC23:06
*** sarob has quit IRC23:08
*** padkrish_ has joined #openstack-meeting23:08
*** sarob has joined #openstack-meeting23:09
*** padkrish has quit IRC23:09
*** tr3buchet1 is now known as tr3buchet23:10
*** eharney has quit IRC23:10
*** jjmb has quit IRC23:11
*** tr3buchet has quit IRC23:12
*** otherwiseguy has joined #openstack-meeting23:12
*** tr3buchet has joined #openstack-meeting23:12
*** sarob has quit IRC23:13
*** f13o_ has quit IRC23:14
*** vivek-ebay has joined #openstack-meeting23:15
*** jungleboyj has joined #openstack-meeting23:18
*** pballand has quit IRC23:19
*** moha_hunt has quit IRC23:22
*** julienvey has joined #openstack-meeting23:23
*** atiwari has quit IRC23:24
*** pballand has joined #openstack-meeting23:25
*** julienvey has quit IRC23:28
*** banix has quit IRC23:29
*** bdpayne has quit IRC23:30
*** padkrish_ has quit IRC23:31
*** padkrish has joined #openstack-meeting23:31
*** padkrish_ has joined #openstack-meeting23:32
*** bdpayne has joined #openstack-meeting23:33
*** comay has quit IRC23:33
*** comay has joined #openstack-meeting23:33
*** vivek-ebay has quit IRC23:35
*** padkrish has quit IRC23:36
*** balajiiyer has left #openstack-meeting23:36
*** topol has joined #openstack-meeting23:39
*** vivek-ebay has joined #openstack-meeting23:39
*** topol_ has joined #openstack-meeting23:41
*** topol has quit IRC23:41
*** topol_ is now known as topol23:41
*** banix has joined #openstack-meeting23:41
*** jjmb has joined #openstack-meeting23:42
*** topol has quit IRC23:48
*** markmcclain has quit IRC23:48
*** Hayim has quit IRC23:50
*** yingjun has joined #openstack-meeting23:53
*** chuckC has quit IRC23:55
*** rbowen has quit IRC23:59

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