Tuesday, 2014-04-01

*** Tross has joined #openstack-meeting00:02
*** andreaf has quit IRC00:02
*** patelna_ has joined #openstack-meeting00:02
*** rakhmerov has quit IRC00:03
*** eghobo has quit IRC00:03
*** gokrokve has quit IRC00:04
*** crandquist has quit IRC00:05
*** patelna has quit IRC00:05
*** patelna_ has quit IRC00:07
*** Swami has quit IRC00:08
*** banix has joined #openstack-meeting00:09
*** rakhmerov has joined #openstack-meeting00:12
*** shwetaap has quit IRC00:12
*** rakhmerov has quit IRC00:13
*** rakhmerov has joined #openstack-meeting00:14
*** crandquist has joined #openstack-meeting00:15
*** jswarren has quit IRC00:16
*** armax has quit IRC00:17
*** walterheck has quit IRC00:18
*** rakhmerov has quit IRC00:18
*** ivar-lazzaro has quit IRC00:23
*** ildikov_ has quit IRC00:25
*** gokrokve has joined #openstack-meeting00:26
*** matsuhashi has joined #openstack-meeting00:27
*** fawadkhaliq has joined #openstack-meeting00:31
*** qs201 has joined #openstack-meeting00:31
*** bknudson has joined #openstack-meeting00:31
*** IlyaE has quit IRC00:33
*** banix has quit IRC00:37
*** banix has joined #openstack-meeting00:38
*** xuhanp has joined #openstack-meeting00:39
*** markmcclain has quit IRC00:45
*** tomoe_ has joined #openstack-meeting00:45
*** zhikunliu has joined #openstack-meeting00:45
*** pablosan has quit IRC00:48
*** changbl has joined #openstack-meeting00:48
*** pablosan has joined #openstack-meeting00:48
*** amcrn has quit IRC00:49
*** novas0x2a|laptop has quit IRC00:50
*** vjay has joined #openstack-meeting00:51
*** ssurana has quit IRC00:52
*** ssurana has joined #openstack-meeting00:52
*** tsekiyama has joined #openstack-meeting00:52
*** markmcclain has joined #openstack-meeting00:53
*** Tross has quit IRC00:54
*** schwicht has joined #openstack-meeting00:55
*** amcrn has joined #openstack-meeting00:55
*** jjmb has quit IRC00:56
*** ssurana has quit IRC00:56
*** marcoemorais has quit IRC00:56
*** zhiyan_ is now known as zhiyan00:57
*** Sukhdev has quit IRC00:58
*** zigo has quit IRC00:59
*** crc32 has quit IRC00:59
*** pablosan has quit IRC01:00
*** brucer has quit IRC01:00
*** zigo has joined #openstack-meeting01:01
*** jlibosva has joined #openstack-meeting01:06
*** xuhanp has quit IRC01:08
*** banix has quit IRC01:10
*** tomoe_ has quit IRC01:10
*** tomoe_ has joined #openstack-meeting01:10
*** jlibosva has quit IRC01:10
*** mrodden has joined #openstack-meeting01:13
*** rakhmerov has joined #openstack-meeting01:14
*** tomoe_ has quit IRC01:15
*** rossk has quit IRC01:16
*** ameade has joined #openstack-meeting01:17
*** ErikB has quit IRC01:18
*** rakhmerov has quit IRC01:19
*** thomasem has quit IRC01:20
*** tsekiyama has quit IRC01:20
*** ameade has quit IRC01:21
*** SumitNaiksatam has joined #openstack-meeting01:23
*** nosnos has joined #openstack-meeting01:26
*** tsekiyama has joined #openstack-meeting01:26
*** comay has quit IRC01:30
*** beagles has quit IRC01:30
*** neelashah has joined #openstack-meeting01:30
*** jecarey has joined #openstack-meeting01:30
*** yaguang has joined #openstack-meeting01:32
*** neelashah1 has joined #openstack-meeting01:32
*** neelashah has quit IRC01:35
*** shwetaap has joined #openstack-meeting01:35
*** brucer has joined #openstack-meeting01:37
*** balajiiyer has joined #openstack-meeting01:37
*** jjmb has joined #openstack-meeting01:40
*** imsurit has joined #openstack-meeting01:42
*** fawadkhaliq has quit IRC01:46
*** xuhanp has joined #openstack-meeting01:47
*** ItSANgo has quit IRC01:48
*** ItSANgo has joined #openstack-meeting01:49
*** ItSANgo has quit IRC01:49
*** arosen1 has quit IRC01:49
*** fawadkhaliq has joined #openstack-meeting01:49
*** ItSANgo__ has joined #openstack-meeting01:49
*** Mandell has quit IRC01:52
*** crandquist has quit IRC01:54
*** _Alexandra_ has joined #openstack-meeting01:54
*** garyduan has quit IRC01:56
*** gduan has joined #openstack-meeting01:56
*** fawadkhaliq has quit IRC01:59
*** balajiiyer has quit IRC02:00
*** shwetaap has quit IRC02:03
*** adalbas has quit IRC02:03
*** zehicle_at_dell has joined #openstack-meeting02:03
*** zhiyan has left #openstack-meeting02:04
*** zhiyan has joined #openstack-meeting02:05
*** noslzzp has quit IRC02:05
*** weshay has quit IRC02:06
*** jlibosva has joined #openstack-meeting02:07
*** xianghui has joined #openstack-meeting02:09
*** yuanz is now known as yuan02:11
*** doug_shelley66 has quit IRC02:11
*** arnaud has quit IRC02:12
*** jlibosva has quit IRC02:13
*** slagle has quit IRC02:13
*** arnaud has joined #openstack-meeting02:14
*** mcurran has joined #openstack-meeting02:14
*** MrJoshua has joined #openstack-meeting02:14
*** zehicle has quit IRC02:15
*** slagle has joined #openstack-meeting02:15
*** rakhmerov has joined #openstack-meeting02:15
*** MrJoshua has quit IRC02:16
*** MrJoshua has joined #openstack-meeting02:16
*** banix has joined #openstack-meeting02:19
*** rakhmerov has quit IRC02:20
*** paragan has joined #openstack-meeting02:20
*** paragan has joined #openstack-meeting02:20
*** arnaud has quit IRC02:22
*** dims has quit IRC02:23
*** RobinJoe has joined #openstack-meeting02:24
*** RobinJ has joined #openstack-meeting02:24
*** dims has joined #openstack-meeting02:24
*** banix has quit IRC02:24
*** jrodom has joined #openstack-meeting02:25
*** walterheck has joined #openstack-meeting02:28
*** slagle has quit IRC02:28
*** amotoki_ has quit IRC02:30
*** haomaiw__ has quit IRC02:31
*** haomaiwang has joined #openstack-meeting02:32
*** rdxc has quit IRC02:32
*** spzala has quit IRC02:33
*** brucer_ has joined #openstack-meeting02:35
*** brucer has quit IRC02:38
*** shwetaap has joined #openstack-meeting02:38
*** walterheck has quit IRC02:40
*** amcrn has quit IRC02:42
*** david-lyle has joined #openstack-meeting02:44
*** shwetaap has quit IRC02:45
*** jjmb has quit IRC02:47
*** topol has joined #openstack-meeting02:47
*** vjay has quit IRC02:48
*** ErikB has joined #openstack-meeting02:49
*** stevemar has joined #openstack-meeting02:53
*** Leonr has joined #openstack-meeting02:54
*** epico has joined #openstack-meeting02:56
*** markmcclain has quit IRC02:59
*** harlowja is now known as harlowja_away02:59
*** haomai___ has joined #openstack-meeting02:59
*** haomaiwang has quit IRC03:03
*** schwicht has quit IRC03:03
*** shwetaap has joined #openstack-meeting03:03
*** RobinJoe has quit IRC03:04
*** RobinJ has quit IRC03:04
*** shwetaap has quit IRC03:04
*** lcheng has joined #openstack-meeting03:06
*** jecarey_ has joined #openstack-meeting03:07
*** crandquist has joined #openstack-meeting03:09
*** jlibosva has joined #openstack-meeting03:09
*** harlowja_away is now known as harlowja03:09
*** jecarey has quit IRC03:10
*** chandan_kumar has joined #openstack-meeting03:11
*** shwetaap has joined #openstack-meeting03:12
*** radsy has quit IRC03:12
*** RobinJoe has joined #openstack-meeting03:12
*** RobinJ has joined #openstack-meeting03:13
*** yamahata has joined #openstack-meeting03:13
*** jlibosva has quit IRC03:13
*** venkatesh has joined #openstack-meeting03:14
*** rakhmerov has joined #openstack-meeting03:16
*** RobinJoe has quit IRC03:17
*** RobinJoe has joined #openstack-meeting03:18
*** tomoe_ has joined #openstack-meeting03:18
*** rakhmerov has quit IRC03:20
*** matsuhashi has quit IRC03:22
*** paragan has quit IRC03:23
*** jecarey__ has joined #openstack-meeting03:25
*** ErikB has quit IRC03:28
*** tomoe_ has quit IRC03:29
*** jecarey_ has quit IRC03:29
*** tomoe_ has joined #openstack-meeting03:30
*** vjay has joined #openstack-meeting03:32
*** tomoe_ has quit IRC03:34
*** chandan_kumar has quit IRC03:35
*** Leonr has quit IRC03:36
*** nosnos has quit IRC03:37
*** paragan has joined #openstack-meeting03:37
*** Tross has joined #openstack-meeting03:38
*** comay has joined #openstack-meeting03:40
*** alexpilotti has joined #openstack-meeting03:40
*** mattgriffin has joined #openstack-meeting03:41
*** ayoung is now known as ayoung-ZZZzzz__03:41
*** ayoung-ZZZzzz__ has quit IRC03:42
*** banix has joined #openstack-meeting03:42
*** venkatesh has quit IRC03:42
*** Mandell has joined #openstack-meeting03:43
*** tomoe_ has joined #openstack-meeting03:43
*** eghobo has joined #openstack-meeting03:44
*** ErikB1 has joined #openstack-meeting03:44
*** colinmcnamara has joined #openstack-meeting03:46
*** markwash has quit IRC03:47
*** neelashah1 has quit IRC03:47
*** neelashah has joined #openstack-meeting03:48
*** markwash has joined #openstack-meeting03:50
*** alexpilotti has quit IRC03:52
*** shwetaap has quit IRC03:53
*** colinmcnamara has quit IRC03:55
*** _Alexandra_ has quit IRC03:56
*** neelashah has quit IRC03:57
*** RobinJ has quit IRC03:57
*** RobinJoe has quit IRC03:57
*** tomoe_ has quit IRC03:57
*** tomoe_ has joined #openstack-meeting03:58
*** rakhmerov has joined #openstack-meeting03:58
*** ErikB1 has quit IRC03:59
*** chandan_kumar has joined #openstack-meeting03:59
*** chandan_kumar has quit IRC04:01
*** gcb has joined #openstack-meeting04:02
*** tomoe_ has quit IRC04:02
*** lcheng has quit IRC04:03
*** chandan_kumar has joined #openstack-meeting04:06
*** _Alexandra_ has joined #openstack-meeting04:07
*** tomoe_ has joined #openstack-meeting04:09
*** jlibosva has joined #openstack-meeting04:10
*** _Alexandra_ has quit IRC04:12
*** thuc has joined #openstack-meeting04:13
*** thuc_ has joined #openstack-meeting04:13
*** matsuhashi has joined #openstack-meeting04:14
*** jlibosva has quit IRC04:15
*** thuc has quit IRC04:17
*** tomoe_ has quit IRC04:20
*** thuc has joined #openstack-meeting04:21
*** mspreitz has joined #openstack-meeting04:22
*** nosnos has joined #openstack-meeting04:23
*** thuc_ has quit IRC04:24
*** mattgrif_ has joined #openstack-meeting04:25
*** mattgriffin has quit IRC04:25
*** tomoe_ has joined #openstack-meeting04:27
*** bdpayne has quit IRC04:28
*** jrodom has quit IRC04:28
*** akuznetsov has joined #openstack-meeting04:30
*** doug_shelley66 has joined #openstack-meeting04:30
*** ArxCruz has quit IRC04:33
*** ArxCruz has joined #openstack-meeting04:35
*** tsekiyama has quit IRC04:37
*** fawadkhaliq has joined #openstack-meeting04:41
*** akuznetsov has quit IRC04:42
*** akuznetsov has joined #openstack-meeting04:43
*** sandywalsh_ has quit IRC04:44
*** sandywalsh has joined #openstack-meeting04:46
*** gokrokve_ has joined #openstack-meeting04:50
*** banix has quit IRC04:50
*** topol has quit IRC04:51
*** stevemar has quit IRC04:51
*** dburmistrov has joined #openstack-meeting04:52
*** rand738 has quit IRC04:52
*** gokrokve has quit IRC04:53
*** rand738 has joined #openstack-meeting04:53
*** Guest63244 has quit IRC04:54
*** mihgen has joined #openstack-meeting04:55
*** IlyaE has joined #openstack-meeting04:57
*** jrodom has joined #openstack-meeting04:58
*** imsurit has quit IRC04:59
*** zul has quit IRC05:00
*** s3wong has joined #openstack-meeting05:00
*** jodom has joined #openstack-meeting05:00
*** jrodom has quit IRC05:00
*** cody-somerville has quit IRC05:01
*** matsuhas_ has joined #openstack-meeting05:02
*** matsuhas_ has quit IRC05:02
*** cody-somerville has joined #openstack-meeting05:02
*** mrmartin has joined #openstack-meeting05:02
*** zul has joined #openstack-meeting05:04
*** matsuhashi has quit IRC05:05
*** IlyaE has quit IRC05:05
*** jodom has quit IRC05:05
*** matsuhashi has joined #openstack-meeting05:05
*** bdpayne has joined #openstack-meeting05:05
*** akuznetsov has quit IRC05:08
s3wongno service VM meeting?05:10
*** harlowja is now known as harlowja_away05:11
*** jlibosva has joined #openstack-meeting05:11
*** thuc has quit IRC05:13
*** thuc has joined #openstack-meeting05:14
yamahatas3wong: still there?05:14
s3wongyamahata: hello05:14
yamahatasorry for late05:14
s3wongit's OK05:14
yamahata#startmeeting neutron/service#topic05:15
openstackMeeting started Tue Apr  1 05:15:08 2014 UTC and is due to finish in 60 minutes.  The chair is yamahata. Information about MeetBot at http://wiki.debian.org/MeetBot.05:15
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:15
*** openstack changes topic to " (Meeting topic: neutron/service#topic)"05:15
openstackThe meeting name has been set to 'neutron_service_topic'05:15
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:15
openstackMeeting ended Tue Apr  1 05:15:29 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:15
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_service_topic/2014/neutron_service_topic.2014-04-01-05.15.html05:15
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_service_topic/2014/neutron_service_topic.2014-04-01-05.15.txt05:15
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_service_topic/2014/neutron_service_topic.2014-04-01-05.15.log.html05:15
yamahata#startmeeting neutron/servicevm05:15
openstackMeeting started Tue Apr  1 05:15:41 2014 UTC and is due to finish in 60 minutes.  The chair is yamahata. Information about MeetBot at http://wiki.debian.org/MeetBot.05:15
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:15
*** openstack changes topic to " (Meeting topic: neutron/servicevm)"05:15
openstackThe meeting name has been set to 'neutron_servicevm'05:15
yamahata#topic current-status05:16
*** openstack changes topic to "current-status (Meeting topic: neutron/servicevm)"05:16
*** jlibosva has quit IRC05:16
yamahataThe code is under debugging.05:16
yamahataI haven't published the image yet05:17
yamahataThe WIP code is available at github. It's still under debug05:18
*** thuc has quit IRC05:18
yamahata#link https://github.com/yamahata/neutron/tree/adv-svc-vm05:18
*** akuznetsov has joined #openstack-meeting05:19
*** fawadkhaliq has quit IRC05:19
yamahataHopefully I can finish it soon.05:20
yamahataany questions?05:20
*** ildikov_ has joined #openstack-meeting05:20
*** gyee has quit IRC05:20
s3wongI took a look at the DB/API code - briefly05:20
yamahatas3wong: great.05:21
*** qs201 has quit IRC05:21
s3wongI generally want to ask two questions:05:21
yamahatas3wong: Yes?05:21
s3wong(a) there seems to be a lot of elements added to the database05:21
*** zhikunliu has quit IRC05:21
s3wong(b) why is service type used when we are moving to a flavor framework?05:22
yamahataRegarding to (a), do you mean that newly introduced tables/coloumns are too many?05:23
yamahataand that those can be reduced?05:23
*** zhikunliu has joined #openstack-meeting05:23
s3wongyamahata: yes - seems like there are a lot of table/columns introduced05:24
s3wongand I wonder if some of those could be consolidated?05:24
yamahatas3wong: Maybe yes. At least service-context table can/should be removed when the service insertion patch is merged.05:25
yamahatas3wong: do you have ideas?05:26
s3wongyamahata: I do realize the service context patch hasn't been approved yet (in fact, I just talked to SumitNaiksatam this morning)05:26
yamahataI think some columns are duplicated and can be removed.05:26
yamahatas3wong: I see.05:27
*** mrmartin has quit IRC05:27
yamahataOk, the tables should be revised.05:28
s3wongyamahata: what you have now is perhaps what is needed to make it work, but probably better to coordinate with the advanced service subgroup to see where we can work better together05:29
yamahatas3wong: agree. Unfortunately the timeslot for advanced service meeting doesn't work for me.05:30
yamahataanyway we can contact them by other ways.05:30
*** otherwiseguy has quit IRC05:31
s3wongyamahata: understand. Once I understand the service VM framework better, I may be able to act as a liaison (I am part of that subgroup)05:31
yamahatas3wong: Regarding to (b), it's intended to represent what kind of service like lbaas, fwaas.05:32
yamahatas3wong: Agreed, with flavour framework, it should be revised somehow.05:33
s3wongyamahata: certainly flavor framework isn't ready neither; that said, another area that may cause you to change your code05:33
*** dburmistrov has quit IRC05:34
*** Longgeek has joined #openstack-meeting05:35
yamahatas3wong: thank you for feed back05:36
yamahatado you have any other issues/questions?05:36
s3wongyamahata: just these - after doing a first pass through of your posted review05:37
yamahatas3wong: thanks, then next topic05:37
yamahata#topic dividing tasks into smaller ones05:37
*** openstack changes topic to "dividing tasks into smaller ones (Meeting topic: neutron/servicevm)"05:37
yamahataso far there are similar blueprints including servicevm05:38
yamahataI think they (including mine) has mostly same goal. They just describe the same problem from different angle with different terminology05:38
yamahataAt the same time, it would be difficult to reach consensus on whole proposal.05:39
yamahataSo I'd like to divide the proposals into smaller ones which can be treated more easily.05:40
*** bdpayne has quit IRC05:40
*** mattgrif_ has quit IRC05:41
yamahataNow I identified, vm(or device or network resource) management05:41
yamahatacommunication with guest agent(or management layer of the device)05:41
yamahataconfiguration(enabling/disabling) of services05:41
yamahatatracking VM(or device)/service05:42
*** zhiyan is now known as zhiyan_05:42
yamahataThey can be attacked independently and the resulted code can be shared05:42
*** mspreitz has quit IRC05:43
yamahataThus each blueprints can make progress05:43
*** winston-d has left #openstack-meeting05:44
yamahatathe communication with guest agents could be used by other projects, I think.05:44
yamahataThat's what I'm thinking about.05:45
yamahataany thought?05:45
s3wongyamahata: it seems like your code covers quite a lot of the above already?05:46
*** akuznetsov has quit IRC05:46
yamahatas3wong: Yes. The existing code can be a good starting point.05:46
yamahataI'd like to hear from those who can share the code05:47
s3wongyamahata: from the projects you listed, I don't know if any of them had posted code for review yet05:47
yamahataI'll split the patches into smaller patches05:48
s3wongI heard dynamic resource management has code, but I don't know if I saw the patch posted?05:48
*** _nadya_ has joined #openstack-meeting05:48
yamahatas3wong: I don't know neither.05:48
s3wongyamahata: +1 for breaking up the CR into pieces05:49
*** IlyaE has joined #openstack-meeting05:49
s3wongI think for a feature this big, community generally doesn't expect all the code to go in in a big chunk05:49
s3wongbreaking it down makes it easier for review also05:49
*** mattgriffin has joined #openstack-meeting05:52
yamahatalet's split up the features and will see the results05:52
yamahataAre those features worth each blueprints?05:52
s3wongyamahata: do you need someone to help out with some pieces?05:53
*** epico has quit IRC05:53
yamahataMaybe the documentation can be single documentation.05:53
yamahatas3wong: off course. The help is welcome05:53
*** mattgriffin has quit IRC05:53
s3wongyamahata: I think one document is fine - even one bp is fine, since the intent is clear05:53
*** pradipta_away is now known as pradipta05:54
yamahatas3wong: So I won't waste my time to creating many BPs. It's easy.05:54
s3wongbut having pieces worked on by different community members, and submitting patches in sequence (instead of one big chunk) will help05:54
s3wongfor example, for the group-policy project, we also only have one bp and one design doc05:55
s3wongbut many people working on code, and we will integrate to get a PoC done05:55
yamahatas3wong: I see. It encourages me.05:55
s3wongthen the idea is we will submit the CR by components instead of a one shot deal05:55
yamahatasounds reasonable05:56
yamahataHmm so the first thing I do is write down the draft of the division in the doc.05:57
yamahataso that people can cooperate05:57
yamahata#action yamahata  write down the draft of the division in the doc05:57
s3wongyamahata: that would be great. I also believe the email you sent, at least Balaji has shown interest05:57
*** epico has joined #openstack-meeting05:57
s3wonghe just got onto the wrong channel :-)05:58
yamahatas3wong: really? I'd like to reach him, but I wasn't able to.05:58
s3wongyamahata: so if you have the doc with breakdown, and send it again to the list, perhaps we can encourage others to join in to help as well05:58
yamahatasound great idea. Will do05:59
yamahata# action yamahata  the doc with breakdown, and send it again to the list05:59
s3wongyamahata: I just saw his email (though it was already 25 minutes ago), he got onto #openstack-meeting-305:59
yamahataAh. I should have been on IRC on time.05:59
yamahataI haven't seen the mails yet.06:00
s3wongyamahata: Nah - he was on the wrong channel anyway :-)06:00
s3wongI replied to his email, we should ask him to join again, this time on the right channel :-)06:00
yamahatas3wong: anyway we can try next week. On right time on right channel.06:00
*** jrodom has joined #openstack-meeting06:01
yamahataanyother topics?06:01
s3wongNot now - and we reached the end of the meeting time anyway :-)06:01
yamahatanext week06:02
s3wongsure, I will also take a look at the LB patch06:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:02
openstackMeeting ended Tue Apr  1 06:02:27 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_servicevm/2014/neutron_servicevm.2014-04-01-05.15.html06:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_servicevm/2014/neutron_servicevm.2014-04-01-05.15.txt06:02
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_servicevm/2014/neutron_servicevm.2014-04-01-05.15.log.html06:02
*** s3wong has quit IRC06:03
*** bdpayne has joined #openstack-meeting06:03
*** vuil has joined #openstack-meeting06:03
*** jrodom has quit IRC06:06
*** _nadya_ has quit IRC06:07
*** jlibosva has joined #openstack-meeting06:12
*** jlibosva has quit IRC06:17
*** saju_m has joined #openstack-meeting06:21
*** thuc has joined #openstack-meeting06:24
*** sridhar has joined #openstack-meeting06:25
*** nelsnelson has quit IRC06:25
*** bdpayne has quit IRC06:27
*** Fdot has joined #openstack-meeting06:27
*** _nadya_ has joined #openstack-meeting06:27
*** thuc has quit IRC06:29
*** bin has joined #openstack-meeting06:29
*** _nadya_ has quit IRC06:31
*** Fdot_ has joined #openstack-meeting06:31
*** _nadya_ has joined #openstack-meeting06:33
*** _nadya_ has quit IRC06:34
*** Fdot has quit IRC06:34
*** jjmb has joined #openstack-meeting06:37
*** jrodom has joined #openstack-meeting06:37
*** nshaikh has joined #openstack-meeting06:40
*** jjmb has quit IRC06:42
*** jrodom has quit IRC06:42
*** tomoe_ has quit IRC06:43
*** slong has quit IRC06:43
*** tomoe_ has joined #openstack-meeting06:43
*** nosnos has quit IRC06:45
*** nosnos has joined #openstack-meeting06:46
*** tomoe_ has quit IRC06:47
*** mihgen has quit IRC06:48
*** nelsnelson has joined #openstack-meeting06:49
*** flaper87|afk is now known as flaper8706:50
*** mcurran has quit IRC06:50
*** IlyaE has quit IRC06:51
*** mkoderer has joined #openstack-meeting06:51
*** Macaveli has joined #openstack-meeting06:51
*** mrunge has joined #openstack-meeting06:56
*** matsuhashi has quit IRC06:58
*** matsuhashi has joined #openstack-meeting06:58
*** nwidell has joined #openstack-meeting06:58
*** _nadya_ has joined #openstack-meeting07:01
*** jtomasek has joined #openstack-meeting07:01
*** matsuhashi has quit IRC07:03
*** _nadya_ has quit IRC07:03
*** evgenyf has joined #openstack-meeting07:03
*** mrmartin has joined #openstack-meeting07:05
*** matsuhashi has joined #openstack-meeting07:06
*** vuil has quit IRC07:11
*** jlibosva has joined #openstack-meeting07:12
*** bauzas has joined #openstack-meeting07:14
*** luqas has joined #openstack-meeting07:16
*** jcoufal has joined #openstack-meeting07:16
*** IlyaE has joined #openstack-meeting07:17
*** jlibosva has quit IRC07:17
*** sandywalsh_ has joined #openstack-meeting07:22
*** sandywalsh has quit IRC07:25
*** ttrifonov_zZzz is now known as ttrifonov07:25
*** mrda is now known as mrda_away07:29
*** salv-orlando has quit IRC07:30
*** salv-orlando has joined #openstack-meeting07:30
*** ndipanov has joined #openstack-meeting07:33
*** mihgen has joined #openstack-meeting07:35
*** tomoe_ has joined #openstack-meeting07:35
*** marun is now known as maru_afk07:36
*** jgallard has joined #openstack-meeting07:37
*** IlyaE has quit IRC07:37
*** jrodom has joined #openstack-meeting07:38
*** MaxV_ has joined #openstack-meeting07:39
*** phil___ has joined #openstack-meeting07:39
*** MaxV_ has quit IRC07:39
*** lukego has joined #openstack-meeting07:40
*** gokrokve_ has quit IRC07:40
*** gokrokve has joined #openstack-meeting07:41
*** jrodom has quit IRC07:43
*** ArthurBerezin has joined #openstack-meeting07:45
*** gokrokve has quit IRC07:45
*** eghobo has quit IRC07:45
*** tomoe_ has quit IRC07:47
*** tomoe_ has joined #openstack-meeting07:47
*** Longgeek has quit IRC07:48
*** belmoreira has joined #openstack-meeting07:49
*** tomoe_ has quit IRC07:52
*** egallen has joined #openstack-meeting07:52
*** tomoe_ has joined #openstack-meeting07:55
*** MaxV_ has joined #openstack-meeting08:01
*** Longgeek has joined #openstack-meeting08:02
*** ygbo has joined #openstack-meeting08:03
*** matsuhashi has quit IRC08:03
*** sridhar is now known as SridharG08:04
*** matsuhas_ has joined #openstack-meeting08:05
*** ityaptin has quit IRC08:06
*** ityaptin has joined #openstack-meeting08:07
*** egallen_ has joined #openstack-meeting08:11
*** egallen has quit IRC08:12
*** egallen_ is now known as egallen08:12
*** jlibosva has joined #openstack-meeting08:13
*** tanisdl has joined #openstack-meeting08:16
*** nwidell has quit IRC08:16
*** jlibosva has quit IRC08:19
*** derekh has joined #openstack-meeting08:24
*** zhikunliu has quit IRC08:25
*** bgorski has joined #openstack-meeting08:31
*** matsuhas_ has quit IRC08:33
*** jlibosva has joined #openstack-meeting08:35
*** ifarkas has left #openstack-meeting08:36
*** andreaf has joined #openstack-meeting08:37
*** zhiyan_ is now known as zhiyan08:38
*** jrodom has joined #openstack-meeting08:38
*** matsuhashi has joined #openstack-meeting08:38
*** jodom has joined #openstack-meeting08:40
*** jrodom has quit IRC08:40
*** saju_m has quit IRC08:43
*** tomoe_ has quit IRC08:43
*** tomoe_ has joined #openstack-meeting08:44
*** jodom has quit IRC08:45
*** tomoe_ has quit IRC08:48
*** d0ugal_ has quit IRC08:53
*** d0ugal_ has joined #openstack-meeting08:53
*** d0ugal_ is now known as d0ugal08:54
*** d0ugal has quit IRC08:54
*** d0ugal has joined #openstack-meeting08:54
*** d0ugal has quit IRC08:54
*** d0ugal has joined #openstack-meeting08:54
*** saju_m has joined #openstack-meeting08:56
*** afazekas has joined #openstack-meeting08:57
*** nshaikh has quit IRC08:57
*** nwidell has joined #openstack-meeting09:04
*** lukego has quit IRC09:04
*** overlayer has joined #openstack-meeting09:07
*** jlibosva1 has joined #openstack-meeting09:14
*** gokrokve has joined #openstack-meeting09:16
*** jcoufal has quit IRC09:18
*** jlibosva1 has quit IRC09:18
*** pradipta is now known as pradipta_away09:19
*** gokrokve has quit IRC09:21
*** Longgeek has quit IRC09:22
*** chandankumar_ has joined #openstack-meeting09:25
*** xuhanp has quit IRC09:27
*** nwidell has quit IRC09:31
*** Longgeek has joined #openstack-meeting09:33
*** jlibosva1 has joined #openstack-meeting09:36
*** lukego has joined #openstack-meeting09:36
*** rdxc has joined #openstack-meeting09:40
*** jlibosva1 has quit IRC09:41
*** jrodom has joined #openstack-meeting09:41
*** egallen has quit IRC09:42
*** jrodom has quit IRC09:45
*** morganfainberg is now known as morganfainberg_Z09:46
*** gokrokve has joined #openstack-meeting09:47
*** jcoufal has joined #openstack-meeting09:50
*** zoresvit has joined #openstack-meeting09:50
*** gokrokve has quit IRC09:52
*** chandankumar_ has quit IRC09:54
*** david-lyle has quit IRC09:55
*** Macaveli has quit IRC09:58
*** ihrachys is now known as ihrachys|lunch09:59
*** egallen has joined #openstack-meeting09:59
*** Michalik- has joined #openstack-meeting10:00
*** egallen has quit IRC10:03
*** egallen has joined #openstack-meeting10:03
*** safchain has joined #openstack-meeting10:10
*** mrmartin has quit IRC10:11
*** matsuhashi has quit IRC10:14
*** akuznetsov has joined #openstack-meeting10:16
*** jjmb has joined #openstack-meeting10:17
*** akuznetsov has quit IRC10:20
*** jgallard has quit IRC10:20
*** ndipanov has quit IRC10:23
*** yamahata has quit IRC10:24
*** nshaikh has joined #openstack-meeting10:26
*** overlayer has quit IRC10:26
*** overlayer has joined #openstack-meeting10:31
*** DuncanT- has quit IRC10:31
*** DuncanT- has joined #openstack-meeting10:32
*** overlayer has quit IRC10:34
*** akuznetsov has joined #openstack-meeting10:34
*** Macaveli has joined #openstack-meeting10:35
*** rdxc has quit IRC10:35
*** ndipanov has joined #openstack-meeting10:36
*** jlibosva1 has joined #openstack-meeting10:36
*** evgenyf has quit IRC10:37
*** nosnos has quit IRC10:40
*** overlayer has joined #openstack-meeting10:40
*** Macaveli has quit IRC10:41
*** jlibosva1 has quit IRC10:41
*** jrodom has joined #openstack-meeting10:42
*** overlayer has quit IRC10:42
*** Macaveli has joined #openstack-meeting10:43
*** yaguang has quit IRC10:43
*** evgenyf has joined #openstack-meeting10:44
*** brucer_ has quit IRC10:44
*** overlayer has joined #openstack-meeting10:45
*** MaxV_ has quit IRC10:45
*** jrodom has quit IRC10:47
*** schwicht has joined #openstack-meeting10:47
*** gokrokve has joined #openstack-meeting10:48
*** marcusvrn has joined #openstack-meeting10:51
*** mrmartin_ has joined #openstack-meeting10:52
*** gokrokve has quit IRC10:53
*** MaxV_ has joined #openstack-meeting10:53
*** yaguang has joined #openstack-meeting10:55
*** overlayer has quit IRC10:59
*** ArthurBerezin1 has joined #openstack-meeting11:00
*** ArthurBerezin has quit IRC11:04
*** epico has quit IRC11:08
*** nwidell has joined #openstack-meeting11:09
*** ArthurBerezin1 has left #openstack-meeting11:12
*** imsurit has joined #openstack-meeting11:12
*** slagle has joined #openstack-meeting11:14
*** mdurnosvistov1 has joined #openstack-meeting11:15
*** baoli has quit IRC11:15
*** sandywalsh_ is now known as sandywalsh11:18
*** erlon has joined #openstack-meeting11:20
*** egallen has joined #openstack-meeting11:21
*** slagle_ has joined #openstack-meeting11:21
*** slagle has quit IRC11:21
*** ihrachys|lunch is now known as ihrachys11:24
*** jgallard has joined #openstack-meeting11:24
*** ErikB1 has joined #openstack-meeting11:27
*** ominakov has joined #openstack-meeting11:30
*** alexpilotti has joined #openstack-meeting11:34
*** tanisdl has quit IRC11:34
*** kiall_ is now known as Kiall11:36
*** jlibosva1 has joined #openstack-meeting11:37
*** ams0 has joined #openstack-meeting11:40
*** xianghui has quit IRC11:41
*** weshay has joined #openstack-meeting11:41
*** ameade has joined #openstack-meeting11:42
*** jlibosva1 has quit IRC11:42
*** jrodom has joined #openstack-meeting11:42
*** yaguang has quit IRC11:44
*** saju_m has quit IRC11:44
*** ams0 has quit IRC11:46
*** gokrokve has joined #openstack-meeting11:47
*** jrodom has quit IRC11:47
*** d0ugal has quit IRC11:51
*** radez_g0n3 is now known as radez11:51
*** d0ugal has joined #openstack-meeting11:51
*** gokrokve has quit IRC11:52
*** jgallard has quit IRC11:52
*** jgallard has joined #openstack-meeting11:52
*** saju_m has joined #openstack-meeting11:57
*** mrunge has quit IRC11:59
*** baoli has joined #openstack-meeting11:59
*** pdmars has joined #openstack-meeting12:01
*** saju_m has quit IRC12:02
*** jhenner has quit IRC12:02
*** rfolco has joined #openstack-meeting12:03
*** rfolco has quit IRC12:03
*** paragan has quit IRC12:04
*** afazekas has quit IRC12:04
*** rfolco has joined #openstack-meeting12:04
*** Tross has quit IRC12:05
*** jhenner has joined #openstack-meeting12:05
*** ArthurBerezin has joined #openstack-meeting12:06
*** dkranz has joined #openstack-meeting12:09
*** overlayer has joined #openstack-meeting12:10
*** amotoki has quit IRC12:11
*** ArthurBerezin has quit IRC12:12
*** nacim has joined #openstack-meeting12:13
*** lukego has quit IRC12:14
*** eharney has joined #openstack-meeting12:16
*** dcramer_ has quit IRC12:17
*** rakhmerov has quit IRC12:17
*** afazekas has joined #openstack-meeting12:18
*** ndipanov has quit IRC12:18
*** overlayer has quit IRC12:18
*** saju_m has joined #openstack-meeting12:21
*** dims has quit IRC12:22
*** saju_m has quit IRC12:23
*** Michalik- has quit IRC12:24
*** thomasem has joined #openstack-meeting12:26
*** ArthurBerezin has joined #openstack-meeting12:26
*** thomasem_ has joined #openstack-meeting12:27
*** markmcclain has joined #openstack-meeting12:28
*** jjmb has quit IRC12:29
*** ndipanov has joined #openstack-meeting12:30
*** aysyd has joined #openstack-meeting12:30
*** thomasem has quit IRC12:31
*** Tross has joined #openstack-meeting12:33
*** Tross has quit IRC12:33
*** dims_ has joined #openstack-meeting12:34
*** tomoe_ has joined #openstack-meeting12:36
*** Michalik- has joined #openstack-meeting12:37
*** jlibosva1 has joined #openstack-meeting12:38
*** beagles has joined #openstack-meeting12:39
*** erecio has quit IRC12:40
*** saju_m has joined #openstack-meeting12:40
*** jdob has joined #openstack-meeting12:40
*** Tross has joined #openstack-meeting12:41
*** jlibosva1 has quit IRC12:42
*** jgrimm has joined #openstack-meeting12:43
*** jprovazn has joined #openstack-meeting12:45
*** egallen has quit IRC12:46
*** overlayer has joined #openstack-meeting12:47
*** gokrokve has joined #openstack-meeting12:47
*** doug_shelley66 has quit IRC12:47
*** egallen has joined #openstack-meeting12:48
*** lblanchard has joined #openstack-meeting12:49
*** thuc has joined #openstack-meeting12:50
*** zoresvit has quit IRC12:51
*** gokrokve has quit IRC12:52
*** thuc_ has joined #openstack-meeting12:52
*** overlayer has quit IRC12:54
*** jrodom has joined #openstack-meeting12:55
*** jrodom has quit IRC12:55
*** jrodom has joined #openstack-meeting12:55
*** thuc has quit IRC12:55
*** dprince has joined #openstack-meeting12:57
*** marcusvrn has quit IRC12:58
*** zoresvit has joined #openstack-meeting12:59
*** admin0 has joined #openstack-meeting12:59
*** shwetaap has joined #openstack-meeting13:01
*** djoreilly has joined #openstack-meeting13:01
*** sballe has joined #openstack-meeting13:02
*** zoresvit has quit IRC13:02
*** mrmartin_ has quit IRC13:03
*** vjay has quit IRC13:04
*** tomoe_ has quit IRC13:04
*** tomoe_ has joined #openstack-meeting13:05
*** rand738 has quit IRC13:08
*** rand738 has joined #openstack-meeting13:08
*** crandquist has quit IRC13:08
*** jecarey__ has quit IRC13:09
*** tomoe_ has quit IRC13:10
*** dkranz has quit IRC13:10
*** cyrichardson has joined #openstack-meeting13:11
*** afazekas has quit IRC13:13
*** erecio has joined #openstack-meeting13:13
*** saju_m has quit IRC13:15
*** noslzzp has joined #openstack-meeting13:17
*** dcramer_ has joined #openstack-meeting13:18
*** zehicle_at_dell has quit IRC13:19
*** mattgriffin has joined #openstack-meeting13:21
*** eharney has quit IRC13:21
*** jhenner has quit IRC13:23
*** vijendar has joined #openstack-meeting13:23
*** dkranz has joined #openstack-meeting13:24
*** ayoung has joined #openstack-meeting13:24
*** akuznetsov has quit IRC13:26
*** kevinconway has joined #openstack-meeting13:27
*** saju_m has joined #openstack-meeting13:29
*** akuznetsov has joined #openstack-meeting13:29
*** xuhanp has joined #openstack-meeting13:30
*** doug_shelley66 has joined #openstack-meeting13:30
*** esker has joined #openstack-meeting13:31
*** ArthurBerezin has left #openstack-meeting13:31
*** zns has joined #openstack-meeting13:34
*** jgrimm has quit IRC13:34
*** thang_ has joined #openstack-meeting13:34
*** changbl has quit IRC13:35
*** neelashah has joined #openstack-meeting13:35
*** tomoe_ has joined #openstack-meeting13:35
*** jhenner has joined #openstack-meeting13:37
*** julim has joined #openstack-meeting13:38
*** mrunge has joined #openstack-meeting13:38
*** ivasev has joined #openstack-meeting13:39
*** jlibosva1 has joined #openstack-meeting13:39
*** imsurit has quit IRC13:39
*** mwagner_zzz has quit IRC13:40
*** thuc_ has quit IRC13:40
*** caleb_` has joined #openstack-meeting13:40
*** imsurit has joined #openstack-meeting13:41
*** thuc has joined #openstack-meeting13:41
*** prad has joined #openstack-meeting13:41
*** erlon has quit IRC13:42
*** sballe has quit IRC13:43
*** jlibosva1 has quit IRC13:44
*** balajiiyer has joined #openstack-meeting13:44
*** balajiiyer has left #openstack-meeting13:44
*** thuc has quit IRC13:45
*** markmcclain has quit IRC13:45
*** thuc has joined #openstack-meeting13:45
*** vhoward- has left #openstack-meeting13:46
*** paragan has joined #openstack-meeting13:46
*** afazekas has joined #openstack-meeting13:46
*** vhoward- has joined #openstack-meeting13:46
*** gokrokve has joined #openstack-meeting13:47
*** aswadrangnekar has joined #openstack-meeting13:48
*** gokrokve_ has joined #openstack-meeting13:49
*** devvesa has joined #openstack-meeting13:50
*** ams0 has joined #openstack-meeting13:50
*** admin0 has quit IRC13:51
*** gokrokve has quit IRC13:52
*** banix has joined #openstack-meeting13:52
*** admin0 has joined #openstack-meeting13:53
*** lcostantino has joined #openstack-meeting13:53
*** gokrokve_ has quit IRC13:54
*** jecarey has joined #openstack-meeting13:55
*** comay has quit IRC13:55
*** AlanClark has joined #openstack-meeting13:55
*** ams0 has quit IRC13:56
*** caleb_` has quit IRC13:57
*** malini has joined #openstack-meeting13:57
*** afazekas has quit IRC13:57
sc68calWho's here for the IPv6 meeting?14:00
*** stevemar has joined #openstack-meeting14:01
sc68cal#startmeeting ipv6_neutron14:01
openstackMeeting started Tue Apr  1 14:01:44 2014 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: ipv6_neutron)"14:01
openstackThe meeting name has been set to 'ipv6_neutron'14:01
*** zns has quit IRC14:01
*** jecarey has quit IRC14:02
sc68calCurrently, there is mostly a focus on the RC-1 release14:02
*** jecarey has joined #openstack-meeting14:03
sc68calAlso, yesterday during the main meeting it was announced that Neutron is going to be following the lead of Nova and other projects when it comes to blueprints14:03
sc68calmeaning, that blueprints are going to move from Launchpad, to a git repository managed by Gerrit14:03
*** nacim has quit IRC14:04
*** BrianB__ has joined #openstack-meeting14:04
sc68calan e-mail to the ML explaining the move is pending, but if you've been following the ML, you can check out the thread over in Nova to get an idea14:04
baoliyea, just heard about that too.14:04
*** whenry has joined #openstack-meeting14:04
*** rbowen has joined #openstack-meeting14:04
*** aveiga has joined #openstack-meeting14:05
sc68calAlso - I'd like to solicit people's opinions on the way the current subteam is organized14:06
*** topol has joined #openstack-meeting14:06
*** tomoe_ has quit IRC14:06
sc68calFor a while in the beginning, I tried to make an agenda on the wiki for every week's meeting, and follow the same couple of topics each meeting14:06
*** tomoe_ has joined #openstack-meeting14:07
sc68calrecap, blueprints, bugs, open discussion14:07
*** radez is now known as radez_g0n314:07
*** mattgriffin has quit IRC14:08
sc68calBut it's been a one-man process with not a lot of input from everyone else14:08
sc68calIs everyone comfortable with the format, or does there need to be changes?14:08
*** yassine has joined #openstack-meeting14:09
sc68calSome of the other teams have put a lot of stuff on their subteam wiki pages, for each meeeting - and most of the time ours is just a copy and paste of the same bullet points14:10
xuhanpsc68cal, any suggestions about how to include more content in our meeting?14:11
*** zns has joined #openstack-meeting14:11
*** tomoe_ has quit IRC14:11
*** tomoe_ has joined #openstack-meeting14:11
sc68calxuhanp: for a couple of the first meetings I would shoot an e-mail to the ML with a link to the wiki, and ask people to add stuff to the agenda if they wanted to talk about something14:11
xuhanpsc68cal, that sounds helpful!14:12
*** ams0 has joined #openstack-meeting14:13
*** bauzas has quit IRC14:13
*** saju_m has quit IRC14:14
sc68calSo, it's just a thought I had - and I wanted to bring it up with the group and see if there was any feedback. If the current pattern of recap, blueprints, bugs, and open discussion works for everyone, I can continue doing it, but I'll also check our subteam wiki for stuff that people want to talk about14:15
aveigasc68cal: maybe we can solicit a feature request list at the summit?14:15
aveigacontinue as we are until then14:15
*** Tross has quit IRC14:16
sc68calaveiga: that sounds like a good idea - I know the LbaaS team just set up a wiki page for use cases and asked people to start listing theirs14:16
sc68caland shot it to the ML14:16
*** aswadrangnekar has quit IRC14:17
*** otherwiseguy has joined #openstack-meeting14:17
*** rakhmerov has joined #openstack-meeting14:19
*** zhangleiqiang has joined #openstack-meeting14:19
*** jgrimm has joined #openstack-meeting14:20
sc68calSo - I'm not sure what the procedure is for the RCs - when it comes to getting patches like the filtering of RAs from subnet gateways and router devices14:21
aveigaI think it's only bugfixes14:21
aveiganot new stuff14:21
*** markmcclain has joined #openstack-meeting14:21
*** adalbas has joined #openstack-meeting14:21
xuhanpaveiga, my patch is delivered by a bug fix :-)14:22
xuhanpI am having some final tests, and I will ping some core member once I get the -1 address.14:22
aveigawhat I meant was, unless it fixes an issue introduced in RC1, they likely won't accept it until Juno14:22
aveigabut ask anyway14:23
*** eharney has joined #openstack-meeting14:23
xuhanpaveiga, good to know14:23
*** mdurnosvistov1 has quit IRC14:23
xuhanpsince we are talking about security, do we want to consider other security enhancement?14:24
*** caleb_ has joined #openstack-meeting14:24
xuhanpfor IPv614:24
xuhanpthis was also mentioned by Édouard Thuleau on my patch.14:24
xuhanpone question is about if we should drop egress RA like RA guard.14:25
aveigayou mean drop RAs being sent from a VM?14:25
*** tanisdl has joined #openstack-meeting14:26
djoreillythink so, vms have no business sending them14:26
aveigadjoreilly: not true!14:26
sc68cal'Édouard Thuleau'14:26
aveigarun a Load Balancer or firewall in a VM. If it's a gateway for a private tenant network, it issues RAs14:26
djoreillyso they are serice type vms14:27
aveigaI think we should only drop them if they aren't also listed as Neutron gateways for that subnet14:27
xuhanpaveiga, that was my thought. But in that case, since we limit the ingress RA to gateway, why do we need to drop them?14:27
aveigawe shouldn't, that's exaclt my point.  If they're listed, we don't drop them.  If they aren't listed, we can drop them14:28
xuhanpaveiga, even if they are not listed, the RA cannot going into other VMs, right?14:29
xuhanpis the drop necessary?14:29
*** phil_h has quit IRC14:29
*** tanisdl has quit IRC14:29
xuhanpOh. I see your point. you are saying they are already dropped?14:29
aveigayes, I don't think we want to accidentally announce RAs to a provider network, since there might be otehr devices on that network not owned by openstack14:29
xuhanpby default rule?14:29
*** rakhmerov has quit IRC14:29
*** rakhmero_ has joined #openstack-meeting14:29
*** skraynev is now known as skraynev_afk14:30
*** cyrichardson has left #openstack-meeting14:30
xuhanpaveiga, OK. I see.14:30
xuhanpthat maybe something worth improving in Juno.14:30
aveigaI don't think it's a huge risk right now though14:30
aveigayeah, that's a Juno thing14:30
aveigawe'll want to wait for a better SG setup anyway, since this is going to cause a LOT of extra rules in iptables right now14:30
*** sballe has joined #openstack-meeting14:31
aveigaI'm concerned about hurting network performance by installing t oo many of them14:31
sc68calI know there was work being done on adding IPSets support14:31
*** tanisdl has joined #openstack-meeting14:31
*** megan_w|afk is now known as megan_w14:31
aveigasc68cal: that own't help here14:32
sc68calbut that was a long time ago and I haven't heard anything since like...... grizzly summit14:32
aveigathis is rule duplication per VM tap port, not a list of addresses14:32
aveigaxuhanp: why don't you write this as a line item in the subteam wiki and mark it to be addressed in Juno?14:32
xuhanpaveiga, sure. will do.14:33
xuhanp#action xuhanp to write egress rule improvement in wiki and mark it to be addressed in Juno14:34
sc68calI think I have to do it to make openstack pay attention :)14:34
sc68cal #action xuhanp to write egress rule improvement in wiki and mark it to be addressed in Juno14:34
aveigawithout the leading space14:35
sc68cal#action xuhanp to write egress rule improvement in wiki and mark it to be addressed in Juno14:35
*** david-lyle has joined #openstack-meeting14:35
*** jprovazn is now known as jprovazn_afk14:35
xuhanpsc68cal, thanks14:35
*** afazekas has joined #openstack-meeting14:37
xuhanpalso Édouard Thuleau added a PDF about IPv6 security rules from Cisco to help inspire the security enhancement14:37
xuhanp#link http://www.cisco.com/c/dam/en/us/products/collateral/ios-nx-os-software/enterprise-ipv6-solution/aag_c45-707354.pdf14:37
*** belmoreira has quit IRC14:38
sc68calI haven't looked at the PDF yet - but depending on the scope it may be worth a blueprint for just that14:39
*** martines_ has quit IRC14:39
*** bauzas has joined #openstack-meeting14:39
aveigaI think parts of this are worth looking into14:39
aveigasome of it may be overkill and degrade performance though14:39
xuhanpthere are interesting points about Ipv6 snooping14:39
*** jlibosva1 has joined #openstack-meeting14:40
aveigawe're already fixing the RA and DHCPv6 parts14:40
*** thuc_ has joined #openstack-meeting14:42
*** vjay has joined #openstack-meeting14:42
*** rakhmero_ has quit IRC14:43
*** zoresvit has joined #openstack-meeting14:43
*** jlibosva1 has quit IRC14:44
sc68calIf there isn't anything else, I can give everyone 15 minutes back14:44
*** tanisdl has quit IRC14:45
xuhanpsc68cal, a quick question. does anyone has any experience on the unit test of neutron client?14:45
xuhanpI have some trouble with that and need some help14:45
sc68calI have some, from doing the qos api extension14:45
*** tanisdl has joined #openstack-meeting14:45
*** thuc has quit IRC14:45
xuhanpgreat! can I talk to you in neutron IRC?14:45
xuhanpsc68cal, thanks a lot!14:46
sc68caleither that or we can talk over e-mail, I know it's getting late for you14:46
*** kgriffs|afk is now known as kgriffs14:46
xuhanpsc68cal, thanks. Let me try IRC first.14:46
*** thuc_ has quit IRC14:46
sc68calalright everyone - until next week14:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:47
openstackMeeting ended Tue Apr  1 14:47:02 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ipv6_neutron/2014/ipv6_neutron.2014-04-01-14.01.html14:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ipv6_neutron/2014/ipv6_neutron.2014-04-01-14.01.txt14:47
openstackLog:            http://eavesdrop.openstack.org/meetings/ipv6_neutron/2014/ipv6_neutron.2014-04-01-14.01.log.html14:47
*** spzala has joined #openstack-meeting14:47
*** gokrokve has joined #openstack-meeting14:47
*** martines_ has joined #openstack-meeting14:48
*** gokrokve has quit IRC14:51
*** devvesa has left #openstack-meeting14:52
*** gokrokve has joined #openstack-meeting14:53
*** shwetaap has quit IRC14:53
*** shwetaap has joined #openstack-meeting14:54
*** slagle_ is now known as slagle14:55
*** devlaps has joined #openstack-meeting14:55
*** IlyaE has joined #openstack-meeting14:55
*** ayoung has quit IRC14:56
*** thedodd has joined #openstack-meeting14:56
*** lukego has joined #openstack-meeting14:57
n0ano#startmeeting gantt14:59
openstackMeeting started Tue Apr  1 14:59:37 2014 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.14:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:59
*** openstack changes topic to " (Meeting topic: gantt)"14:59
openstackThe meeting name has been set to 'gantt'14:59
*** rdxc has joined #openstack-meeting14:59
n0anoanyone here want to talk about the scheduler?14:59
*** thuc has joined #openstack-meeting15:00
*** mspreitz has joined #openstack-meeting15:00
bauzasbtw. please note France switched to CEST yesterday15:01
n0anobauzas, you have my sympathy, I `hate` daylight savings time :-)15:01
bauzasso, there could be some possibilities that people miss the meeting15:01
*** thuc has quit IRC15:01
* johnthetubaguy raises late hand, that is slightly absent15:01
bauzaswell, that's now 5pm now in France, I prefer CET :D15:01
*** thuc has joined #openstack-meeting15:02
n0anohence OpenStack meetings are always UTC, the meeting follow the sun :-)15:02
n0anoanyway, to begin15:02
n0ano#topic no db scheduler15:02
*** openstack changes topic to "no db scheduler (Meeting topic: gantt)"15:02
*** PaulMurray has joined #openstack-meeting15:02
n0anogiven that this project is effectively deferred until after Juno it's silly to try and talk about it every week...15:03
bauzasjust a fyi, a recent concern about querying host aggregates has been raised where we identified the need of storing AZs and aggs within ComputeNode state15:03
*** carl_baldwin has joined #openstack-meeting15:03
bauzasso, no-db scheduler could possibly be impacted by this15:03
n0anoat the same time I don't want to forget about it so I think we'll put a note about it as a postscript to the agenda but don't need to talk about it15:03
johnthetubaguywell no-db is blocked by the scheduler split at this point, I feel15:04
*** TravT has joined #openstack-meeting15:04
johnthetubaguyits just the AZ info would go into mem-cache, so not sure thats a big one15:04
*** djoreilly has quit IRC15:04
n0anobauzas, so, this is just another case of it's going to wait until after Juno15:04
johnthetubaguyn0ano: I don't think it has too15:04
bauzasjohnthetubaguy: indeed, just a fyi again :)15:04
johnthetubaguyn0ano: only till after that lib is created15:04
PaulMurrayHi all, I seem to have come in half way through a conversation15:04
johnthetubaguyn0ano: then they can use that seam to make it optional15:04
n0anojohnthetubaguy, I was referring to no-db, not the aggregates issue15:05
*** stevemar has quit IRC15:05
johnthetubaguyn0ano: yep, I was meaning thats the solution for no-db, wait for the seam, then use it, so its optional15:05
bauzasanyway, boris-42 told us there were some resource issues for working on no-db, so it will have to wait until Juno :)15:05
*** stevemar has joined #openstack-meeting15:05
johnthetubaguybauzas: it is Juno15:05
boris-42bauzas hi15:05
bauzashi boris-4215:06
n0anoI think we're in violent agreement15:06
boris-42bauzas yep it will wait for juno=)15:06
boris-42bauzas lol=)15:06
*** bdperkin has quit IRC15:06
n0anoboris-42, still think it's important so we don't want to forget about it15:06
johnthetubaguysure, juno is open now15:06
bauzasjohnthetubaguy: well, ok15:06
boris-42n0ano hehe=)15:06
johnthetubaguyneeds nova-specs sorting, etc15:06
boris-42n0ano sorry we have some troubles with Alexei15:07
*** vhoward- has left #openstack-meeting15:07
boris-42n0ano I think I will probably finish that work15:07
boris-42n0ano to avoid unexpected situation this time..15:07
boris-42n0ano was too busy to work on it during icehouse =(15:07
n0anoboris-42, NP, we'll just keep pushing you as the owner, who you get to do the work is your problem15:07
bauzasboris-42: we just discussed about it and said it was worth waiting for sched-lib to be delivered before committing on no-db sched15:08
boris-42n0ano lol=)15:08
boris-42bauzas yep it is hard to make lib without it..15:08
*** bdperkin has joined #openstack-meeting15:08
boris-42bauzas cause you are totally bind to nova data15:08
*** bdperkin has quit IRC15:08
*** bdperkin has joined #openstack-meeting15:08
boris-42bauzas and structuree of nova data15:08
bauzasboris-42: we do baby-steps :)15:08
boris-42bauzas hehe=)15:09
boris-42bauzas yep yep15:09
bauzasboris-42: at the moment, we work on the interfaces15:09
bauzasboris-42: but we need to chase all calls from within the scheduler indeed15:09
boris-42bauzas so you would like to use RPC as interface?15:09
*** ayoung has joined #openstack-meeting15:09
*** jcru has joined #openstack-meeting15:09
*** Gordonz has joined #openstack-meeting15:09
boris-42bauzas I think that interface e.g. (hostname, namespace, values) is the best one15:09
bauzasboris-42: well, I'm teasing the 2nd topic, but we're committed to deliver a sched client15:10
bauzasboris-42: which will take use of the sched rpcapi15:10
bauzasboris-42: baby step, proxying :)15:10
boris-42bauzas I think that it's more important what you have inside15:10
bauzasboris-42: indeed15:10
bauzasboris-42: but we just need to perform one-by-one :)15:11
johnthetubaguythe key point I was thinking, we can make no-db optional right?15:11
boris-42bauzas sure sure15:11
boris-42johnthetubaguy it changes.. the way how scheuler works15:11
n0anojohnthetubaguy, it was my understanding that was the goal15:11
boris-42johnthetubaguy so there is no magic button "turn it off"15:11
johnthetubaguyboris-42: I still think it should be an option, new no-db stuff, or current db stuff15:11
boris-42johnthetubaguy one more separated project?)15:12
bauzasboris-42: nah, just a conf flag :)15:12
boris-42bauzas it has different arch15:12
n0anobauzas, +115:12
johnthetubaguyboris-42: well we are creating gantt, but yeah, just a config flag for this case15:12
boris-42johnthetubaguy it will be different code with different logic..15:12
*** chandankumar_ has joined #openstack-meeting15:12
boris-42johnthetubaguy so only interface could be the same15:12
johnthetubaguyboris-42: best to take it through the nova-specs design review anyways, before the blueprint will be approved15:12
boris-42johnthetubaguy but in that case we should discuss what "interefact" we would like15:13
johnthetubaguyboris-42: right, thats the scheduler lib15:13
bauzasjohnthetubaguy: +1, god loves nova-specs :D15:13
boris-42johnthetubaguy so what I need in no-db is to get updates from host in next way15:13
bauzasboris-42: sounds like we should do peer reviews15:13
boris-42(hostname, namespace, values)15:13
johnthetubaguythe idea is to call some python code with that above interface, right15:13
johnthetubaguythen the old stuff writes to db15:14
bauzasboris-42: because I will proxy the call from the resource tracker15:14
n0anobauzas, I'm thinking we need to hash this out at Atlanta15:14
bauzasn0ano: strong +2 here15:14
johnthetubaguyyour new scheduler driver thingy, does what it needs to do (RPC or whatever)15:14
boris-42johnthetubaguy the problem is one more we are chaining how it works15:14
boris-42johnthetubaguy it's not only driver part15:15
bauzasagain, we're teasing the summit topic :)15:15
boris-42johnthetubaguy it's everything15:15
boris-42johnthetubaguy storing results, filters, processing results, api15:15
n0anobauzas, getting issues out early is good, resolving might have to wait for the summit15:15
boris-42johnthetubaguy there is only one common possible place15:15
bauzasn0ano: my bad, I was saying we're teasing today's meeting topic called 'summit talks" :D15:16
johnthetubaguyboris-42: I think I get the bits you are talking about, but it really needs to be an option, I feel, so people can choose when to migrate to the new method15:16
n0anobauzas, +1 :-)  (I don't mind non-linear converations :-)15:16
johnthetubaguyits about getting the correct seams in the current system, I think15:17
boris-42johnthetubaguy heh let me think about it15:17
boris-42johnthetubaguy how to make it optional=)15:17
boris-42johnthetubaguy separated project seems like a good idea lol=)15:17
johnthetubaguyI think its about a replacement hostmanager, sort of15:17
boris-42johnthetubaguy yep whole stuff..15:17
*** armax has joined #openstack-meeting15:17
johnthetubaguyfor no-db at least15:17
n0anoboris-42, I think optional is important, even if it means changing your design a little15:17
boris-42n0ano the issue that it changes everything=)15:18
bauzasboris-42: I don't remember seeing such a big bang :)15:18
boris-42n0ano so if you would like to make it optimal in gantt we should have common API15:18
mspreitzDoes it even change nova clients?15:18
boris-42mspreitz lol15:18
boris-42mspreitz nope15:18
*** jcoufal has quit IRC15:18
bauzasit's worth reading the spec here :)15:19
boris-42mspreitz but it changes nova.compuetes15:19
mspreitzHeat wants to get out of the business of maintaining its own cache of state...15:19
boris-42bauzas btw I made session15:19
boris-42bauzas so I can describe whole architecture15:19
bauzasboris-42: and I replied :)15:19
*** zehicle has joined #openstack-meeting15:19
boris-42bauzas and seems like I should find time to update docs and learn what was done in Gantt15:19
n0anoboris-42, nothing new has been done in gantt (yet), it is just a forklift of the current scheduler design15:20
bauzasboris-42: ok, let's discuss this in the second next topic :)15:20
*** aveiga has quit IRC15:21
*** stevemar has quit IRC15:21
boris-42bauzas heh=)15:21
boris-42bauzas n0ano ok I have to go now=)15:21
n0anogood seque15:21
boris-42bauzas n0ano  but I will try to organize development of this stuff15:21
boris-42from Mirnatis side15:21
*** Tross has joined #openstack-meeting15:21
n0ano#topic scheduler forklift15:21
*** openstack changes topic to "scheduler forklift (Meeting topic: gantt)"15:21
*** stevemar has joined #openstack-meeting15:21
bauzasboris-42: just take a look at my comment to your proposal in the summit page :)15:21
bauzasboris-42: and ping me later if needed :)15:21
boris-42bauzas ok thanks15:22
*** cjellick has joined #openstack-meeting15:22
*** ildikov_ has quit IRC15:22
bauzasok, so about sched forklift15:22
bauzasa few pointers15:22
*** caleb_ has quit IRC15:22
*** BrianB__ has quit IRC15:22
bauzasthat's the nova-specs bp15:22
*** zns has quit IRC15:22
*** alexpilotti has quit IRC15:22
bauzasfeel free to take a look on it15:22
*** virmitio has joined #openstack-meeting15:23
johnthetubaguy+1 please review15:23
bauzasdraft implementation is in progress15:23
bauzasstill need to adapt based on BP review of course15:23
bauzasand still chasing up issues with unittests :)15:24
bauzaswoah, I was playing with climate CI, this one is huuuge :)15:24
*** pablosan has joined #openstack-meeting15:24
*** Leonr has joined #openstack-meeting15:24
bauzasI really enjoy having 200+ tests failing :)15:24
*** pablosan has quit IRC15:25
n0anobauzas, that doesn't bother me, it normally means something simple and basic is wrong15:25
bauzashence the draft, so as to ramp-up on nova15:25
*** pablosan has joined #openstack-meeting15:25
*** markwash has quit IRC15:25
n0anobauzas, it's the 3 or 4 random failures that cuase headaches15:25
bauzasn0ano: :)15:25
*** nacim has joined #openstack-meeting15:26
*** markwash has joined #openstack-meeting15:26
n0anonote, I have a tendency to not review things until the tests pass, you never know what might need to change15:26
bauzasn0ano: then focus on the BP :)15:26
*** scottda has quit IRC15:26
*** zehicle has quit IRC15:26
bauzasn0ano: Jenkins gave me +1 :)15:26
*** Guest37964 has quit IRC15:26
n0anoon a BP, no bonus points for that :-)15:27
*** zehicle has joined #openstack-meeting15:27
bauzaswell, nothing to add here :)15:27
*** tanisdl has quit IRC15:27
bauzaswaiting reviews on the BP and in progress on the draft implem15:28
n0anosounds like we all need to review and then we can discuss more intelligently15:28
bauzasn0ano: sounds a good option to me :D15:28
*** Macaveli has quit IRC15:28
n0anobauzas, cool, tnx for the work!15:28
n0anomoving on then15:28
n0ano#Atlanta sessions15:28
bauzas#topic :)15:28
n0ano#topic Atlanta sessions15:28
*** openstack changes topic to "Atlanta sessions (Meeting topic: gantt)"15:28
* n0ano sign15:28
*** tanisdl has joined #openstack-meeting15:28
n0anoI search and found 4 proposals so far...15:29
bauzasn0ano: +1, I found 415:29
n0anoNo-db scheduler (boris put the same proposal in twice, I guess he really wants it :-)15:29
bauzasn0ano: 2 of me, 1 from boris-42, one from jay lau15:29
n0anosched hints for VM life cycle (looks good to me)15:29
n0anoForklift & gantt APIs15:30
*** admin0 has quit IRC15:30
*** pablosan is now known as zz_pablosan15:30
n0anoDoes anyone else have plans they know of for more proposals?15:30
bauzaswe should hurry up for cross-project sessions :)15:30
mspreitzBTW, what is the URL for proposals?15:30
*** vkmc has joined #openstack-meeting15:30
bauzasmspreitz: lemme give them to you15:30
bauzashttp://summit.openstack.org/cfp/details/180  : no-db15:30
*** vjay2 has joined #openstack-meeting15:31
bauzashttp://summit.openstack.org/cfp/details/99 : sched hints15:31
n0anomspreitz, for submitting them...15:31
bauzashttp://summit.openstack.org/cfp/details/80 : sched forklift15:31
n0ano#link http://summit.openstack.org/15:31
*** vjay has quit IRC15:31
bauzashttp://summit.openstack.org/cfp/details/140 : gantt API15:31
bauzasthere was a thread in -dev15:31
bauzasstating that proposals for cross-projects should be sent by end of ...15:32
mspreitzpage title says "icehouse"15:32
n0anothreads in -dev can easily get lost in the noise15:32
n0anomspreitz, you sure, its15:32
bauzasmspreitz: that's an April joke :)15:32
*** cjellick has quit IRC15:32
n0anomspreitz, you sure, it says Juno in my browser15:32
bauzasn0ano: +115:33
mspreitzah, it's my browser, inheriting something from before15:33
*** nshaikh has quit IRC15:33
n0anomspreitz, reload is your friend (I get hit with that all the time)15:33
bauzasgot the email15:33
bauzaslemme give you the link15:33
*** egallen has quit IRC15:33
*** shwetaap has quit IRC15:33
mspreitzIt's Firefox's bookmarking code15:33
mspreitzdon't waste meeting time on this15:34
n0anoso, the 4 we have outstanding look good to me but if there are others people want to propose they should do it soon15:34
*** admin0 has joined #openstack-meeting15:34
*** crandquist has joined #openstack-meeting15:34
*** shwetaap has joined #openstack-meeting15:34
*** Tross has quit IRC15:34
bauzas#link http://lists.openstack.org/pipermail/openstack-dev/2014-March/031384.html15:34
bauzasETA April 10th15:35
mspreitzthe listing page has way more than 4 for nova15:35
*** egallen has joined #openstack-meeting15:35
n0anomspreitz, well yeah, I'm only concerned about scheduler/gantt15:35
*** mrodden has quit IRC15:35
bauzasfor submitting cross-project and "other projects" proposals15:35
n0anogeneric nova will have `lots` of proposals15:35
bauzasCtrl+F is worth it15:36
*** scottda has joined #openstack-meeting15:36
n0anoI just wanted to raise the issue of Atlanta sessions so that's enough for today15:37
n0ano#topic opens15:37
*** openstack changes topic to "opens (Meeting topic: gantt)"15:37
*** mtanino has joined #openstack-meeting15:37
n0anoanything else anyone wants to raise today?15:37
*** Guest37964 has joined #openstack-meeting15:37
*** cjellick has joined #openstack-meeting15:38
*** xuhanp has quit IRC15:38
n0anohearing crickets so I'll thank everyone and we'll talk again next week15:38
* bauzas hearing 15:38
n0anotnx all15:38
bauzasn0ano: sure thanks15:38
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:39
openstackMeeting ended Tue Apr  1 15:39:00 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-04-01-14.59.html15:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-04-01-14.59.txt15:39
openstackLog:            http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-04-01-14.59.log.html15:39
*** PaulMurray has quit IRC15:39
*** yassine has quit IRC15:40
*** jlibosva1 has joined #openstack-meeting15:40
*** nwidell has quit IRC15:44
*** caleb_` has joined #openstack-meeting15:45
*** ociuhandu has joined #openstack-meeting15:45
*** zns has joined #openstack-meeting15:45
*** jlibosva1 has quit IRC15:45
*** fawadkhaliq has joined #openstack-meeting15:46
*** dprince has quit IRC15:46
*** virmitio has left #openstack-meeting15:47
*** thuc_ has joined #openstack-meeting15:47
*** mrunge has quit IRC15:47
*** jcoufal has joined #openstack-meeting15:48
*** gyee has joined #openstack-meeting15:49
*** cjellick has quit IRC15:49
*** jmontemayor has joined #openstack-meeting15:49
*** zz_pablosan is now known as pablosan15:49
*** thuc has quit IRC15:50
*** thuc_ has quit IRC15:51
*** ttrifonov is now known as ttrifonov_zZzz15:51
*** mrodden has joined #openstack-meeting15:51
*** cjellick has joined #openstack-meeting15:51
*** Fdot_ has quit IRC15:53
*** dburmistrov has joined #openstack-meeting15:53
*** pablosan is now known as zz_pablosan15:54
*** mdurnosvistov1 has joined #openstack-meeting15:54
*** otherwiseguy has quit IRC15:55
*** julienvey has quit IRC15:55
*** SridharG has quit IRC15:55
*** emagana has quit IRC15:56
*** jmontemayor has quit IRC15:56
*** shwetaap has quit IRC15:56
*** jmontemayor has joined #openstack-meeting15:56
*** jlibosva has quit IRC15:57
*** carl_baldwin has left #openstack-meeting15:58
*** stannie has joined #openstack-meeting15:58
*** changbl has joined #openstack-meeting15:59
*** zz_pablosan is now known as pablosan16:00
*** mspreitz has quit IRC16:00
*** tsekiyama has joined #openstack-meeting16:00
*** nacim has quit IRC16:00
*** jgallard has quit IRC16:00
*** paragan has quit IRC16:00
*** lcheng has joined #openstack-meeting16:01
primeministerp#startmeeting hyper-v16:01
openstackMeeting started Tue Apr  1 16:01:25 2014 UTC and is due to finish in 60 minutes.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: hyper-v)"16:01
openstackThe meeting name has been set to 'hyper_v'16:01
*** Tross has joined #openstack-meeting16:02
primeministerpociuhandu: hi tavi16:02
primeministerpociuhandu: we'll wait for alex16:02
primeministerpluis_fdez: hi luis16:02
primeministerpI don't have much to cover today16:03
*** jdurgin1 has joined #openstack-meeting16:03
*** ccorrigan has quit IRC16:03
primeministerpwe'll wait a couple more minutes to see if others join16:03
*** zehicle has quit IRC16:03
*** eghobo has joined #openstack-meeting16:04
*** safchain has quit IRC16:04
*** sballe_ has joined #openstack-meeting16:05
*** hartsocks has quit IRC16:05
*** sballe has quit IRC16:05
*** ams0 has quit IRC16:05
*** jlibosva has joined #openstack-meeting16:05
*** mspreitz has joined #openstack-meeting16:06
*** hartsocks has joined #openstack-meeting16:07
*** jgallard has joined #openstack-meeting16:08
*** jgallard has quit IRC16:08
primeministerpso looks like others are still tied up16:08
primeministerpI'm going to end the meeting and not take any more time16:08
primeministerpluis_fdez: let's touch base re: puppet modules when you get a chance16:08
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:08
openstackMeeting ended Tue Apr  1 16:08:52 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:08
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2014/hyper_v.2014-04-01-16.01.html16:08
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2014/hyper_v.2014-04-01-16.01.txt16:08
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2014/hyper_v.2014-04-01-16.01.log.html16:08
*** JuanManuelOlle has joined #openstack-meeting16:09
*** JuanManuelOlle has left #openstack-meeting16:10
*** amotoki has joined #openstack-meeting16:10
*** Sukhdev has joined #openstack-meeting16:10
*** doron has joined #openstack-meeting16:11
*** doron is now known as doron_afk16:13
*** mwagner_zzz has joined #openstack-meeting16:16
*** thuc has joined #openstack-meeting16:18
*** thuc has quit IRC16:18
*** thuc has joined #openstack-meeting16:19
*** ArthurBerezin has joined #openstack-meeting16:19
*** imsurit has quit IRC16:19
*** lukego has quit IRC16:20
*** vjay2 has quit IRC16:22
*** egallen has quit IRC16:25
*** mdurnosvistov1 has quit IRC16:25
*** scottda has quit IRC16:25
*** Guest37964 has quit IRC16:25
*** mdurnosvistov1 has joined #openstack-meeting16:26
*** mspreitz has quit IRC16:26
*** shwetaap has joined #openstack-meeting16:27
*** egallen has joined #openstack-meeting16:27
*** dtroyer has quit IRC16:29
*** stevemar2 has joined #openstack-meeting16:30
*** pablosan is now known as zz_pablosan16:30
*** caleb_` has quit IRC16:30
*** ayoung has quit IRC16:30
*** marcoemorais has joined #openstack-meeting16:30
*** dtroyer has joined #openstack-meeting16:30
*** zns has quit IRC16:31
*** ArthurBerezin has left #openstack-meeting16:31
*** maru_afk is now known as marun16:32
*** egallen has quit IRC16:32
*** Sukhdev has quit IRC16:33
*** stevemar has quit IRC16:33
*** sballe_ has quit IRC16:34
*** zns has joined #openstack-meeting16:34
*** Guest37964 has joined #openstack-meeting16:36
*** shwetaap has quit IRC16:36
*** scottda has joined #openstack-meeting16:39
*** kgriffs is now known as kgriffs|afk16:39
*** rakhmerov has joined #openstack-meeting16:40
*** dprince has joined #openstack-meeting16:41
*** ndipanov has quit IRC16:41
*** sushils has joined #openstack-meeting16:42
*** jlibosva1 has joined #openstack-meeting16:42
*** derekh has quit IRC16:44
*** egallen has joined #openstack-meeting16:45
*** ayoung has joined #openstack-meeting16:45
*** zz_pablosan is now known as pablosan16:45
*** jlibosva1 has quit IRC16:46
*** egallen has quit IRC16:47
*** otherwiseguy has joined #openstack-meeting16:50
*** hemna_ has joined #openstack-meeting16:51
*** admin0 has quit IRC16:51
*** phil___ has quit IRC16:52
*** ErikB1 has quit IRC16:53
*** megan_w is now known as megan_w|afk16:53
*** Guest37964 has quit IRC16:53
*** rakhmerov has quit IRC16:53
*** scottda has quit IRC16:53
*** mihgen has quit IRC16:54
*** mrunge has joined #openstack-meeting16:56
*** sushils has quit IRC16:56
*** mihgen has joined #openstack-meeting16:57
*** egallen has joined #openstack-meeting16:57
*** mihgen has quit IRC16:57
*** shwetaap has joined #openstack-meeting16:57
*** scottda has joined #openstack-meeting16:57
*** Guest37964 has joined #openstack-meeting16:57
*** ErikB1 has joined #openstack-meeting16:58
*** fawadkhaliq has quit IRC16:58
*** lbragstad has joined #openstack-meeting16:58
*** Longgeek has quit IRC16:59
*** Longgeek has joined #openstack-meeting16:59
*** SumitNaiksatam has quit IRC17:00
*** henrynash has joined #openstack-meeting17:00
*** Tross has quit IRC17:01
*** mspreitz has joined #openstack-meeting17:01
*** lcostantino has left #openstack-meeting17:01
*** Longgeek has quit IRC17:01
*** nacim has joined #openstack-meeting17:02
*** arosen has quit IRC17:02
*** mrunge has quit IRC17:02
*** armax has quit IRC17:02
*** fawadkhaliq has joined #openstack-meeting17:03
*** jcoufal has quit IRC17:04
*** armax has joined #openstack-meeting17:04
*** zhangleiqiang has quit IRC17:04
*** afazekas is now known as afazekas_noteboo17:05
*** amotoki has quit IRC17:05
*** Sukhdev has joined #openstack-meeting17:05
*** rossk has joined #openstack-meeting17:05
*** dstanek has joined #openstack-meeting17:05
*** arosen has joined #openstack-meeting17:06
*** ygbo has quit IRC17:06
boris-42#startmeeting rally17:07
openstackMeeting started Tue Apr  1 17:07:18 2014 UTC and is due to finish in 60 minutes.  The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot.17:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:07
*** openstack changes topic to " (Meeting topic: rally)"17:07
openstackThe meeting name has been set to 'rally'17:07
boris-42#startmeeting rally17:07
openstackboris-42: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.17:07
boris-42hughsaunders marcoemorais ping17:07
*** afazekas has joined #openstack-meeting17:08
*** walterheck has joined #openstack-meeting17:08
marcoemoraisboris-42: hey17:09
*** walterheck has quit IRC17:09
*** Longgeek has joined #openstack-meeting17:09
*** Sukhdev has quit IRC17:09
*** walterheck has joined #openstack-meeting17:10
boris-42marcoemorais hughsaunders  let's wait a bit of others=)17:10
hughsaundersok :-) i thought i'd missed meeting, but summertime has moved it an hour later :-)17:11
*** sarob has joined #openstack-meeting17:12
*** slagle has quit IRC17:13
*** eyerediskin has joined #openstack-meeting17:13
boris-42hughsaunders hehe=)17:14
boris-42eyerediskin ping17:14
*** harlowja_away is now known as harlowja17:14
* mwagner_zzz in17:14
*** megan_w|afk is now known as megan_w17:14
*** mwagner_zzz is now known as mwagner_17:14
*** ttrifonov_zZzz is now known as ttrifonov17:15
eyerediskinboris-42: pong17:15
*** slagle has joined #openstack-meeting17:15
*** SumitNaiksatam has joined #openstack-meeting17:15
boris-42mwagner_ marcoemorais could you share your emails17:17
boris-42mwagner_ marcoemorais  I would like to share google doc17:17
*** david-lyle is now known as david-lyle_afk17:17
*** jdurgin1 has quit IRC17:18
marcoemoraisboris-42: mmorais@yahoo-inc.com17:18
*** mattgriffin has joined #openstack-meeting17:20
boris-42#topic Rally future road map17:20
*** openstack changes topic to "Rally future road map (Meeting topic: rally)"17:20
*** jlibosva has quit IRC17:20
boris-42mwagner_ marcoemorais eyerediskin mwagner_zzz hughsaunders okay let's start17:20
boris-42Today we have actually only one topic but it's quite a big17:20
boris-42Rally future road map17:21
boris-42So High level things that I would like to say are17:21
*** shwetaap has quit IRC17:22
boris-421) Better cover requirements in benchmarking of other projects (e.g. Marconi and MagnetoDB) that would like to generate 10k-100k requests per sec17:22
boris-42^ It will require a lot of work on Runners17:22
boris-422) Better cover requirements of neutron where we need actually to buid specifc environment before benchmarking (benchmark-context)17:23
*** jackmccann has quit IRC17:23
*** Longgeek_ has joined #openstack-meeting17:23
*** Longgeek has quit IRC17:23
boris-423) Better cover requirements of PaaS (murano, solum, sahara) where we actually are interested not only in measruing API stuff17:24
boris-42but actually how it works at all17:24
boris-42Start working on Operators stuff17:24
boris-42HealthChecks, Better Verification, RestAPI, Better Reporst, Historical data and so on17:25
boris-42Finish profiling=)17:25
*** alexpilotti has joined #openstack-meeting17:25
*** afazekas_noteboo is now known as _afazekas17:25
boris-42And Finially have gates that tests everything=)17:25
*** msdubov has joined #openstack-meeting17:25
*** gdarling has quit IRC17:26
boris-42so that's all=)17:26
marcoemoraisboris-42: done17:26
*** radez_g0n3 is now known as radez17:26
*** ssurana has joined #openstack-meeting17:26
*** zhiyan is now known as zhiyan_17:27
mwagner_boris-42, it would be to be able to quantify performance of thing like #2, in other words, measuring how long it takes to build out the neutron network17:27
*** luqas has quit IRC17:28
boris-42mwagner_ so actually pinguinRaider will try to start work on measuring time in context17:28
boris-42mwagner_ during GSoC 2014 (it's part of his task)17:28
*** vuil has joined #openstack-meeting17:28
*** bdpayne has joined #openstack-meeting17:28
mwagner_making stuff run fast in a guest is easy, getting the env setup in a performant manner is hard17:28
*** thedodd has quit IRC17:29
boris-42mwagner_ yep yep17:29
boris-42mwagner_ this will be a hard work on our context classes17:30
boris-42mwagner_ like we done with "users" context to create users & tenants in parallle17:30
boris-42mwagner_ but seems like it could be imporved more17:30
*** morganfainberg_Z is now known as morganfainberg17:31
boris-42mwagner_ harlowja hughsaunders marcoemorais so we shoud start working on that big document17:31
boris-42 https://docs.google.com/document/d/1cAgyueiQ__tZ_MG5oOxe4q49tyPQcm-Y1469lmeERq8/edit?usp=sharing17:31
hughsaundersboris-42 whats the plan for selectively applying context? add decorator for required contexts, then supply args in config?17:32
boris-42harlowja yep17:32
boris-42hughsaunders yep17:32
boris-42hughsaunders actually it will be a bit more magic=)17:32
boris-42hughsaunders e.g. if there is nothing in "context" config it will put {}17:33
boris-42hughsaunders and try to validate {}17:33
boris-42hughsaunders if it pass like in case of key pair & sec group17:33
boris-42hughsaunders then you don't need to specify them in conf everytime17:33
*** sarob has quit IRC17:35
*** aswadrangnekar has joined #openstack-meeting17:35
*** ildikov_ has joined #openstack-meeting17:35
*** sarob has joined #openstack-meeting17:36
*** MaxV_ has quit IRC17:36
boris-42so does anybody want to discuss anything about RoadMap?)17:37
marcoemoraisboris-42: what abt the distributed runner? are we going to build on top of what python offers in multiprocess17:37
marcoemoraisboris-42: or are we going to use a task queue like celery or ...?17:37
boris-42marcoemorais query17:37
boris-42marcoemorais by distributed I mean a lot of agents17:38
boris-42marcoemorais that can produce load from different host17:38
boris-42marcoemorais cause it's really hard to produce enough big load from one node17:38
marcoemoraisboris-42: yes, exactly17:39
boris-42marcoemorais so we should think how to make it possible with keeping simple way to specify load (e.g. we have now)17:39
boris-42marcoemorais probably just using multiply current scenario runners from different host without any change=)17:39
boris-42marcoemorais but there is a problem (with collecting big amount of data) and storing it17:40
*** TravT has quit IRC17:40
boris-42marcoemorais as well part with deploying runners17:40
boris-42marcoemorais I think eyerediskin may help us with this part ^17:40
marcoemoraisboris-42: I was wondering whether the rally-as-service part would play a role here17:40
*** sarob has quit IRC17:40
boris-42marcoemorais rally-as-a-service is different thing=)17:41
marcoemoraisboris-42: if we have a rally service api, then we can use rpc interface to distribute the load generation17:41
*** henrynash has quit IRC17:41
boris-42marcoemorais I don't think that it is a good idea17:41
boris-42marcoemorais cause I would like to keep the almost same functionality via CLI and aaS17:42
boris-42marcoemorais so we should make runners more separated from project17:42
marcoemoraisboris-42: another way is the task queue, but for that we need to have rally daemon or something on each client to consume the tasks17:42
boris-42marcoemorais yep ^ that I like17:42
boris-42marcoemorais we can reuse serverproviders17:43
*** jlibosva has joined #openstack-meeting17:43
boris-42marcoemorais and instead of deploying openstack run rally agents17:43
boris-42marcoemorais that have simple rpc/http api to accept context and produce some load17:43
harlowjamarcoemorais i wouldn't touch celery :-P17:44
*** TravT has joined #openstack-meeting17:44
harlowjause taskflow ;)17:44
*** tanisdl has quit IRC17:44
boris-42harlowja yep seems like a good place for taskflow17:44
marcoemoraisboris-42 harlowja ok we will use taskflow17:45
boris-42marcoemorais so are you interested in this topic?)17:45
boris-42harlowja using tasfklow ^ better result collector & better result strong17:46
marcoemoraisboris-42: yes I would like to work on this, we can make use of it right away17:46
boris-42marcoemorais ^17:46
harlowjaboris-42 another suggestion, rate-limting load creation17:46
*** chandankumar_ has quit IRC17:46
harlowjawithout some kind of rate-limiting its gonna be hard to control debugging, verifying...17:46
malini& while you are still at task queues, remember marconi ;)17:46
boris-42harlowja marcoroni?)17:48
*** jlibosva has quit IRC17:48
mwagner_also synchronization would be key, ability to make all the agents fire at once17:48
marcoemoraisharlowja boris-42 following up on harlowja idea, what do you think about being able to express the load to put on the cloud in terms of RPS to keystone17:48
boris-42marcoemorais +117:49
boris-42marcoemorais instead of period?)17:49
mwagner_so some scheduling , at 13:00 start 50 agents doing X17:49
harlowjamarcoemorais hopefully not just to keystone right?17:49
*** rakhmerov has joined #openstack-meeting17:49
harlowjamwagner_ i think its more than just start 50 agents doing X, its about controlling how much traffic they produce also17:49
marcoemoraisharlowja: yes, not just keystone — I mistakenly refer to keystone as the uber api17:49
boris-42marcoemorais hmm17:50
boris-42marcoemorais why not just use current runners17:50
boris-42marcoemorais and first request is init17:50
*** bgorski has quit IRC17:50
boris-42marcoemorais to send context objects17:50
boris-42marcoemorais second is multicast17:50
boris-42marcoemorais fire!17:50
boris-42marcoemorais burn openstack=)17:50
harlowjawhen pushing the boundaries of the system it will be better to have some rate control though right :-P17:51
harlowjaless burn, lol17:51
mwagner_harlowja, agreed on the amount of activity, but there are cases when you want them synchronized17:51
harlowjamwagner_ ah, sure17:51
boris-42mwagner_ I am not sure that we need so precise syncronization17:51
*** amcrn has joined #openstack-meeting17:51
eyerediskinmeeting is going to end, but i have a question to all: what do you think about not using google docs, and using wiki instead?17:51
marcoemoraismwagner_: if you require synchronization, why wouldn't you just code that as part of your scenario?17:51
boris-42mwagner_ especially when we will run for few hours benchmark17:51
boris-42mwagner_ it doesn't matter if some runner will start not exactly in the same second17:52
*** jprovazn_afk is now known as jprovazn17:52
boris-42mwagner_ or I am not right?)17:52
msduboveyerediskin, Wiki doesn't provide commenting facilities...17:52
msduboveyerediskin, That's of huge importance17:53
*** Longgeek has joined #openstack-meeting17:53
msduboveyerediskin, Why do you dislike gdocs?17:53
marcoemoraismwagner_: in other words, if you want to test load of operation a1 and a2 in parallel, then you write a scenario which forks and synchronizes to call a1 and a2 in parallel?17:53
*** kgriffs|afk is now known as kgriffs17:53
boris-42eyerediskin I dislike that idea=017:53
mwagner_boris-42, depends on the tests, if there are times where you want to send X requests at the same time17:53
*** Longgeek_ has quit IRC17:54
*** rakhmerov has quit IRC17:54
boris-42mwagner_ so let's write in google doc17:54
mwagner_marcoemorais, boris-42 also thinking of the ability to schedule, every Sat at 15:00 kick of this set of tests17:54
boris-42mwagner_ idead and fantasies=)17:54
msdubovmarcoemorais, Btw I think we also shouldn't require too much complicated coding in scenarios17:54
boris-42mwagner_ it's more operator stuff17:54
*** lukego has joined #openstack-meeting17:54
msdubovmarcoemorais, They should be as simple to write as possible17:54
boris-42mwagner_ it shouldn't be inside benchmark engine17:54
*** jcru has left #openstack-meeting17:55
*** shwetaap has joined #openstack-meeting17:55
boris-42mwagner_ it should be on top of Rally17:55
boris-42mwagner_ it's health performance check part17:55
mwagner_boris-42, my fantasies should *not* be in a google doc ;)17:55
boris-42mwagner_ ^_^17:55
hughsaundersevery week = rally api client + cron ?17:55
*** arnaud has joined #openstack-meeting17:55
*** egallen has quit IRC17:56
boris-42hughsaunders it will be inside Rally aaS17:56
boris-42hughsaunders support of periodic task17:56
eyerediskinbtw https://review.openstack.org/8439417:56
boris-42hughsaunders e.g. operator creates "task config" & specify when to run it17:57
eyerediskinso we have rally-install job17:57
boris-42eyerediskin ^ nice nice!17:57
boris-42mwagner_ so okay write your ideas lol=)17:57
boris-42marcoemorais as well17:57
boris-42mwagner_ marcoemorais  so we will discuss how to cover everybody's usecases=)17:58
hughsaunderseyerediskin: cool17:58
boris-42okay guys future discussion in Rally chat room17:58
*** ttrifonov is now known as ttrifonov_zZzz17:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Tue Apr  1 17:59:03 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-04-01-17.07.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-04-01-17.07.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-04-01-17.07.log.html17:59
*** eyerediskin has left #openstack-meeting17:59
dolphmayoung, bknudson, dstanek, jamielennox, morganfainberg, stevemar, gyee, henrynash, topol, marekd, lbragstad, joesavak, shardy, fabiog, fmarco76: ping17:59
lbragstaddolphm: hey17:59
ayoungIts that time again17:59
bknudsondolphm: hi18:00
*** mtreinish has quit IRC18:00
*** mwagner_ is now known as mwagner_afk18:00
dolphm#startmeeting keystone18:01
openstackMeeting started Tue Apr  1 18:01:11 2014 UTC and is due to finish in 60 minutes.  The chair is dolphm. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:01
dolphm#topic Reminder: don't be a fool18:01
dolphm#topic Reminder: Design summit session proposals open until April 20th18:01
*** zns has quit IRC18:01
*** openstack changes topic to "Reminder: don't be a fool (Meeting topic: keystone)"18:01
*** openstack changes topic to "Reminder: Design summit session proposals open until April 20th (Meeting topic: keystone)"18:01
*** mtreinish has joined #openstack-meeting18:01
bknudsonwe should delete v2 as april fool's joke18:01
ayoungDon't we have like 3000 sessions submitted for Keystone?18:02
morganfainbergbknudson, heh18:02
dolphmthere was also an announcement on the -dev that cross-project sessions will have an earlier deadline than the rest of the summit proposals, so get those in super early18:02
dolphmayoung: i'm afraid to look18:02
morganfainbergdolphm, there are a bunch18:02
gyeeI have more to add18:02
*** caleb_ has joined #openstack-meeting18:02
*** jamielennox has joined #openstack-meeting18:03
*** sridhar has joined #openstack-meeting18:03
dolphmwe're also one session slot short this year versus the last few years (8 vs 9)18:03
*** brich1 has joined #openstack-meeting18:03
ayoungdolphm, we'll end up making buckets and collecting up topics into them, then\18:03
dolphmayoung: of course18:03
dolphmanyway, the fun part:18:04
dolphm#topic Announcement: icehouse-rc1 now available!18:04
*** openstack changes topic to "Announcement: icehouse-rc1 now available! (Meeting topic: keystone)"18:04
ayounggyee, instead of adding, lets pick the set of buckets and figure out what goes where18:04
*** julim has quit IRC18:04
* dolphm "Like during the Havana cycle, Keystone is again the first project to publish a release candidate in preparation for the Icehouse release! Congratulations to the Keystone development team for reaching that milestone first." -ttx18:04
gyeeayoung, absolutely18:04
bknudsonhow do we get fixes into icehouse now?18:04
bknudsonuse the milestone-proposed branch?18:04
dolphmbknudson: so now we have a milestone-proposed branch18:04
ayoungWe are at 22 submissions18:04
dolphmfixes need to land in master first, and milestone-proposed is treated as a stable/ branch18:04
gyeedolphm, ayoung, so you guys going to come up with the bucket list?18:05
*** otherwiseguy has quit IRC18:05
lbragstadand then well cut another rc?18:05
morganfainbergbknudson,dolphm, do we have any outstanding rc2 potentials?18:05
lbragstadif needed?18:05
dolphmcurrently we only have one patchset that i believe needs to get into milestone-proposed, and warrants an rc218:05
ayounggyee, I can make a first pass, sure18:05
dolphm#link https://review.openstack.org/#/c/84457/18:05
dolphmthe +0, -28607 there is not an april fools joke :)18:05
bknudsonwe couldn't even get a clean backport after a week18:05
morganfainbergdolphm, sure.18:06
dolphmbknudson: yeah, the automated job in master made it messy, but thankfully it's just a script to recreate the patch18:06
bknudsonis there another patch to add the xlations back?18:06
dolphmbknudson: this only removes dupes18:06
*** vuil has quit IRC18:06
*** julim has joined #openstack-meeting18:06
dolphmbknudson: so, that's not necessary18:06
topolthat patchset so feels like an april fools joke. really? really?18:06
*** vuil has joined #openstack-meeting18:06
*** derekh has joined #openstack-meeting18:07
dolphmbknudson: rather, just read the script :P https://gist.github.com/dolph/991529318:07
dolphmi should add a comment there as to where it came from -- it was posted as a comment in another bug report18:07
bknudsonit would be nice if we just had the files we wanted... don't they generate the po files? just check those in to replace the existing18:08
*** rockyg has joined #openstack-meeting18:08
*** caleb_ has quit IRC18:08
dolphmbknudson: yeah, i'm not sure what the better long term answer is, but there's clearly a problem we'll need to solve moving forward18:08
lbragstaddolphm: what bug was it posted in?18:08
dolphmand i'm guessing it's *not* "run this script to fix things periodically"18:08
bknudsonthere must be a set of "master" files somewhere18:09
*** zns has joined #openstack-meeting18:09
dolphmlbragstad: https://bugs.launchpad.net/ironic/+bug/1298645/comments/218:09
uvirtbotLaunchpad bug 1298645 in ironic "translated .po files do not contain any translation text" [High,Fix committed]18:09
bknudsondo we want the milestone-proposed files to match the files currently in master ?18:10
dolphmbknudson: master is already ahead18:10
*** caleb_ has joined #openstack-meeting18:10
dolphmbknudson: so, definitely not18:10
dolphmbknudson: i.e. new strings, etc, have landed in master since milestone-proposed was cut18:10
bknudsonthey're already translating juno?18:10
morganfainbergbknudson, no just new / changed string sets18:10
morganfainbergbknudson, by default the translation is the same as the original string.18:11
*** msdubov has left #openstack-meeting18:11
dolphmhorizon seems to be the only project where the translation folks have put in a significant amount of effort18:12
*** sarob has joined #openstack-meeting18:12
*** dkranz has quit IRC18:12
*** sarob has quit IRC18:12
bknudsonok, I'll see if I can run the script and regenerate and compare with master.18:12
dolphmthe rest is mostly getting i18n infrastructure in place18:12
dolphmi've been keeping an eye on launchpad, but if anyone is aware of any issues in milestone-proposed that may warrant an RC2 - please file them / bring them to my attention ASAP18:13
ayoungHere is a proposal for Buckets: Backends, Hierarchy, HTTP, IdP, Performance, Tokens.  Heh, that is only 618:13
*** ominakov has quit IRC18:13
*** _nadya_ has joined #openstack-meeting18:13
*** baoli has quit IRC18:13
morganfainbergayoung, tokens, i think you need to mention tokens again, because tokens.18:14
morganfainbergayoung, ;)18:14
*** Sukhdev has joined #openstack-meeting18:14
gyeeayoung, Client & Middleware?18:14
ayoungdolphm, I'm not certain that translations belong anywhere but Horizon.  There is a pretty strong argument that it is easier to Google for the issue if iti is in only one language than all 20018:14
ayounggyee, client and middleware would be a good additional bucket18:14
dolphmayoung: take it to the mailing list :)18:14
ayoungdolphm, ++18:14
morganfainbergayoung, i'd support that personally18:14
dolphmayoung: there's a couple existing threads on the topic18:14
morganfainbergayoung, though responses from the API might want to be translated18:15
gyeewhat translation, just read the fantastical code!18:15
morganfainbergayoung, e.g. messages (not errors)18:15
morganfainbergif any.18:15
*** jlibosva has joined #openstack-meeting18:15
morganfainberg*shrug*. i like the idea of not translating for ease of error handlings18:15
morganfainbergerm, error searching18:15
ayoungfunny how translations could actually make a problem harder to identify instead of easier18:16
bknudsonour lack of logging makes it hard to figure out what a problem is.18:16
morganfainbergbknudson, ++18:17
bknudsonone of my plans is to try some things and see if I can figure out the problem from the logs18:17
morganfainbergbetter logging would help.18:17
dolphmbknudson: ++18:17
ayoungstevemar2, is http://summit.openstack.org/cfp/details/71  server or client side plugins?18:17
morganfainbergbknudson, somethine worth chatting about at the summit (informal probably)18:17
bknudsonI'll just yell it out in the developer lounge.18:18
morganfainbergbknudson, ++ :)18:18
morganfainbergbknudson, that is unless you have something together before then.18:18
dolphm#topic Icehouse release notes18:19
*** openstack changes topic to "Icehouse release notes (Meeting topic: keystone)"18:19
dolphmso, as soon as we cut RC1 i ran off and got us started on some release notes...18:19
dolphm#link https://wiki.openstack.org/wiki/ReleaseNotes/Icehouse#OpenStack_Identity_.28Keystone.2918:20
dolphmplease review, amend & edit as necessary if i missed anything worthy of advertising to deployers, etc18:20
topolI dont think I have ever heard bknudson yell...18:20
morganfainbergtopol, maybe he yells all the time, just not around you.18:21
dolphmi'm most concerned about changes in keystone.conf that i didn't capture as upgrade notes18:21
*** MaxV_ has joined #openstack-meeting18:21
dolphmand any tricky / heavy migrations we produced18:21
*** thuc has quit IRC18:22
morganfainbergdolphm, i think the only complex migration is the grant table one18:22
dolphmmorganfainberg: ooh, that's a good one to note18:23
morganfainbergconfig file changes, i think mostly it was additions for new features.18:23
*** thuc has joined #openstack-meeting18:24
dstanekor removal of explicity set options and defaulting to the config default...did that change any defaults?18:24
dolphmany changes of default values, beyond the default token duration?18:24
bknudsonthere might have been some deprecations for the move to oslo-incubator db18:24
*** nacim has quit IRC18:24
*** thuc has quit IRC18:24
morganfainbergbknudson, ++18:24
morganfainbergbknudson, those would be good to capture18:24
*** thuc has joined #openstack-meeting18:24
morganfainbergdolphm, oh the mutable domain_id option18:24
morganfainbergdolphm, that is worth capturing.18:25
dolphmmorganfainberg: ooh, non-ideal defaults is a good theme18:25
dolphmthings we want to see changed in juno18:25
lbragstadAPI validation framework?18:25
morganfainbergdolphm, mutable domain_id is false by default we opted (iirc) to say "this is security related" so if osmeone relies on that they need to re-enable it (please, let no one rely on that)18:26
morganfainbergit is one of the few cases i think we ran into a "we're going to break this" decisions18:26
*** dkranz has joined #openstack-meeting18:26
*** erecio has quit IRC18:27
morganfainbergdolphm, ++ on non-optimal defaults18:27
dolphmadded a couple TODO's to the release notes based on the above ^18:27
dstaneki'd love to get real Python 3 support completed in Juno18:28
morganfainbergdstanek, ++18:28
dolphmdstanek: ++18:29
bknudsondstanek: apparently they're going to get it done a pycon18:29
bknudsonat pycon18:29
dstanekbknudson: what project?18:29
jamielennoxdstanek: there is more than just eventlet that is broken with py318:29
dolphmbknudson: get'r* done18:29
dstanekjamielennox: lots :-(18:29
jamielennoxi couldn't make the oslo-incubator db stuff work with py318:29
jamielennoxsqla-migrate is also broken18:30
dstaneklots of olso won't run on 318:30
dolphmjamielennox: i think the next release of sqlalchemy-migrate addresses that18:30
dstaneki just fixed gettextutils this mornin18:30
dolphmjamielennox: they held it back since we were shipping icehouse, IIRC18:30
morganfainbergjamielennox, i'm looking at alembic again since i;m going to do the migration collapse here shortly18:30
ayoungWhat was the comment about everyone shipping non-backwards cmpat releases of Python libraries?18:30
jamielennoxmorganfainberg: yea, i switched kite from sqla-m to alembic for py3 - didn't end up mattering because of the oslodb stuff18:31
morganfainbergjamielennox, yeah.18:31
dolphmmorganfainberg: sort of an expected surprise, but https://bugs.launchpad.net/neutron/+bug/128842718:31
uvirtbotLaunchpad bug 1288427 in neutron "Unsequenced alembic migration files block the gate." [Critical,Fix released]18:31
jamielennoxthere is no common oslo.db librray yet is there?18:31
dolphmjamielennox: no18:31
bknudsonI think the oslo.db is next on the list for oslo library18:32
morganfainbergdolphm, yep, was going to aim for 100% ordered, as much as they "want" to use unordered magic18:32
*** rbowen has quit IRC18:32
dolphmayoung: ?18:32
morganfainbergdolphm, that bug specifically was a concern i wanted to avoid.18:32
ayoungdolphm, looking for the origianal quote, but the punchline was "pycon"18:32
ayoung"How I know it's the week before pycon: everyone is releasing non backwards compatible python library releases breaking OpenStack"  Sean Dague18:33
morganfainbergayoung, OpenStack Gate: The Python Library Regression Test18:34
*** erecio has joined #openstack-meeting18:34
bknudsonwe should freeze our deps18:34
dstanekjamielennox: https://wiki.openstack.org/wiki/Python318:34
morganfainbergbknudson, you mean cap all of them?18:34
dstaneki'm going to update that today so that it's current18:34
bknudsonmorganfainberg: yes, to protect ourselves18:34
morganfainbergbknudson, i think that poses a lot of operational headaches.18:35
morganfainbergbknudson, at one point we capped a lot, but then projects got out of sync and we installed conflicting versions18:35
morganfainbergbknudson, it's an issue with the way pip/pypi works (not unsolvable)18:35
jamielennoxbknudson: it would cause havoc on the distros18:35
bknudsonjust the week before pycon18:35
morganfainbergbknudson, and what jamielennox said18:35
*** Longgeek has quit IRC18:36
jamielennoxdstanek: that page isn't as reassuring as i would have liked - i thought we were a bit closer than that18:37
jamielennoxdstanek: i understand the servers but oslo-incubator should gate on py318:37
*** Longgeek has joined #openstack-meeting18:37
dolphmjamielennox: they likely need to gate before we can :(18:37
bknudsonif we're going to pull in changes from oslo-incubator to keystoneclient...18:38
bknudsonthey'll need to work on py318:38
dstanekdolphm: i'm going to port the olso stuff we currently use to push them in the right direction18:38
dolphmdstanek: awesome!18:38
dolphm#topic Document V3 features (vs V2)18:39
*** openstack changes topic to "Document V3 features (vs V2) (Meeting topic: keystone)"18:39
dolphmmorganfainberg: o/18:39
*** sjcazzol has joined #openstack-meeting18:39
*** ttrifonov_zZzz is now known as ttrifonov18:39
jamielennoxbknudson: not just that - i understand how hard it is to convert existing projects, but i was having to start kite again in a new repo so wanted to have it gated on py3 from the start and it just can't18:39
morganfainbergSo I was chatting with the nova folks and the comment that there was no "list" of what V3 provides over V2 in keystone's api was brought uop18:39
*** walterheck has quit IRC18:39
dolphmrelated: i should also throw out there that, if you missed it, we reverted the deprecation on v2 last week - it's "stable" in milestone-proposed, as is v318:39
morganfainbergshort of the "go look at the identity-api repo"18:39
bknudsonI think the biggest thing projects are running into with v3 is the catalog format change in the token18:39
bknudsonthey have their own ServiceCatalog class that doesn't support the v3 catalog18:40
jamielennoxbknudson: which they shouldn't be parsing manually anyway18:40
dolphmbknudson: auth_token and the client in general should protect everyone from that change :(18:40
dolphmjamielennox: right18:40
morganfainbergThere should be a list of features / differences / reasons to move targeted at projects etc that want to move (this was a request from jogo, and i feel totally reasonable)18:40
jamielennoxdolphm: though we have to pass X_SERVICE_CATALOG as a string - which does make them try it18:40
ayoungdolphm, and if not, then they should use the python-keystoneclient catalog API18:40
dolphmjamielennox: and a different string with v2 vs v3 -- we need to provide an option to give them the same string either way18:41
jamielennoxdolphm: interesting - but i'm not sure if that's a benefit to just making them parse correctly18:41
gyeejamielennox, how about passing the ServiceCatalog object in the request environ18:41
jamielennoxthere is no great advantage of v3 catalog over v218:41
morganfainberggyee, can you.. do that cleanly?18:42
dolphmjamielennox: it's worse, IMO18:42
gyeemorganfainberg, sure18:42
*** novas0x2a|laptop has joined #openstack-meeting18:42
jamielennoxgyee: aparently its not allowed, things coming out of middleware shouldn't be python specific18:42
*** lukego has quit IRC18:42
morganfainberggyee, ok (I haven't looked at that extensively lately)18:42
bknudsonalternatively, we could provide both v2 and v3 catalog in the token response18:42
*** Longgeek has quit IRC18:42
jamielennoxhowever the context middleware and others do it i'm suer18:42
gyeejamielennox, says who?18:42
jamielennoxbknudson: no, it's big enough18:42
bknudsonwould need compression for that.18:42
morganfainbergbknudson, that is bad, the token is massive as is.18:42
gyeethat's how Swift passing their logger object18:42
morganfainbergbknudson, even w/ compression i think it's ugly.18:42
dolphmyou can pass whatever you want through the wsgi environment, auth_token uses strings for historical / backwards compatibility18:43
morganfainbergbknudson, though it might be the "real" solution18:43
dolphmhistorical reasons*18:43
bknudsonI think there are already changes to get the other clients using keystoneclient ServiceCatalog...18:43
bknudsonthere was someone here working on it.18:43
gyeedolphm, right, lets make history by passing service catalog object :)18:43
jamielennoxbknudson: right i've had a go18:43
morganfainbergbknudson, we got cinder there18:43
morganfainbergbknudson, :)18:43
jamielennoxbknudson: the main problem is volume_service_name in a few places18:44
jamielennoxi've added service_name to keystoneclient (not sure if that's merged yet)18:44
jamielennoxi'm not sure if i need to add some sort of selection to others18:44
dolphmgyee: you could just pass a keystoneclient session and call it a day18:44
gyeedolphm, ++18:45
jamielennoxdolphm: ++ that's the hope18:45
jamielennoxno-one should ever need to manage there own service catalog18:45
morganfainbergjamielennox ++++++++18:45
bknudsonother projects seem to be somewhat interested in domains.18:45
bknudsonnot sure if that's a good thing18:45
jamielennoxthis is the volume_service_name issue: https://github.com/openstack/python-cinderclient/blob/master/cinderclient/service_catalog.py#L59-L7118:46
jamielennoxi'm not sure yet if we can work around it in keystoneclient.service_catalog18:46
dolphmbknudson: ++18:46
bknudsonI don't know that we'll have much to say to other projects to use V3 over V2...18:47
bknudsonbut I think our users will prefer V3 over V2.18:48
dolphmjamielennox: that's a mess18:48
morganfainbergbknudson, if we want to convince them to move to V3, we probably need to sell it.18:48
jamielennoxdolphm: yep18:48
*** megan_w is now known as megan_w|afk18:48
morganfainbergbknudson, even if the selling is "new auth everyone wants in v3, use it"18:48
gyeemorganfainberg, we'll need to put up the code for them18:48
morganfainbergand v2 is frozen and will receive new features.18:48
morganfainbergerm wont18:48
jamielennoxbknudson: i don't think it's to the advantage of the projects, it's to the advantage of deployers18:48
bknudsonI think the best way to sell it is if they don't have to make any changes to use it.18:48
*** thedodd has joined #openstack-meeting18:48
morganfainbergbknudson, ++ but there are some cases where they will need some changes.18:48
morganfainbergbknudson, i would hope auth_token would just "do it" for them18:49
dolphmbknudson: or to use it, they delete a lot of code and replace it with a few lines using keystoneclient :)18:49
morganfainbergdolphm, ++18:49
bknudsondolphm: yes, they should be happy to have to maintain less code.18:49
dolphmmorganfainberg: it's damn near ready... three outstanding issues i know of18:49
morganfainbergdolphm, cool.18:49
gyeeyeah, keystoneclient is a hell lot easier to use now18:49
*** Tross has joined #openstack-meeting18:49
ayoungI need to circle back around on the compressed tokens change18:49
gyeethanks to jamielennox18:49
morganfainbergin either case if there is a change that is needed (even if we contribute the code) we need to still say "hey guys, merge this"18:50
*** rakhmerov has joined #openstack-meeting18:50
dolphmmorganfainberg: incompatible service catalog when switching to v3, we still require v2 to authenticate auth_token itself, and i don't think we're using v3/OS-SIMPLECERT/ atm (?) -- then it's just a matter of reversing the default from v2 to v318:50
*** kgriffs is now known as kgriffs|afk18:50
jamielennoxmorganfainberg: to make other projects use client you mean?18:50
morganfainbergjamielennox, yeah18:50
dolphmayoung: target juno-m1 for that18:50
jamielennoxmorganfainberg: yea - i plan to go and do a lot of that18:50
dolphmayoung: if not before the summit18:50
ayoungdolphm, yeah, for the server.  But needs to be in client before that18:50
jamielennoxdolphm: the v2 call in auth_token will be fixed by the plugins from CONF stuff18:51
dolphmjamielennox: ping me throughout that process as well18:51
morganfainbergjamielennox, as long as we have a clear reason why they should support V3, that is an easier sell18:51
morganfainbergjamielennox, as long as we have the clear message, i think we're on the right track.18:51
dolphmayoung: i hopefully only have a few more days of icehouse stuff to worry about, and i can help you get that landed on both sides18:52
gyeejamielennox, you can keep me in the loop as well, I am doing the same thing18:52
morganfainbergand that is what is being looked for. why should they move the api even if we supply the code18:52
dolphmmorganfainberg: if you can get a doc started, i'd be happy to contribute to it as i think of things18:52
morganfainbergdolphm, sounds good. I'll get a wiki page up18:53
*** Longgeek has joined #openstack-meeting18:53
morganfainberg#action morganfainberg to setup wiki for reasons/features of V3 keystone api18:53
morganfainbergdolphm, 7 mins18:53
dolphmmorganfainberg: i was also wondering why it needed to be discrete from the how-we-get-to-v3 bp?18:53
dolphmmorganfainberg: it seems like this would just be the itnro18:54
dolphmWhy v3 & How v318:54
morganfainbergdolphm, sure, but if we're looking for a concise list of differences, it makes sense to have it separate18:54
ayoungThe biggest "why" is domains18:54
*** mspreitz has quit IRC18:54
morganfainberge.g. "why this, and here is what it provides"18:54
gyeeayoung, I can help write that part if you want18:55
morganfainbergvs the "you should do this because users like it"18:55
ayoungas far as how...that is the script stuff that we've been adding to the recent reviews18:55
*** egallen has joined #openstack-meeting18:55
bknudsonif we have hierarchical projects in v3 then that will affect other projects18:55
*** walterheck has joined #openstack-meeting18:55
morganfainbergdolphm, but yes, it's all part of the same documentation18:55
*** tchaypo has joined #openstack-meeting18:55
ayounghttps://review.openstack.org/#/c/82687/  and so on18:55
*** dstanek has quit IRC18:55
morganfainbergdolphm, though the v3 specific changes might also be useful for deployers in absence of the "how to move to v3 as a openstack project"18:55
*** tomoe_ has quit IRC18:55
gyeebknudson, it will be a good discussion in the upcoming summit18:56
ayoungwe need to get a handle on the hierarchical projects...the IDs should not be what determines the hierarchy...18:56
*** tomoe_ has joined #openstack-meeting18:56
jamielennoxayoung: regions have the same problem18:56
ayoungI can't keep up with the discussion or the sample code flying around.18:57
jamielennox(and IMO more quickly relevant)18:57
ayoungjamielennox, yeah, but regions are already implmented in a somewhat sane way, no?18:57
jamielennoxayoung: from client side - how am i supposed to know what region belongs to another?18:57
dolphmregions also don't have an immediately profound effect on every other project18:57
* dolphm 2 min18:58
*** fawadkhaliq has quit IRC18:58
*** evgenyf has quit IRC18:58
ayoungyou mean we need an API to select subregions?18:58
jamielennoxayoung: specifically from a service catalog if you ask for a region and a sub-region of that is present how am i supposed to know that that one is usable?18:58
dolphmayoung: that's basically GET /v3/regions18:58
*** fawadkhaliq has joined #openstack-meeting18:58
ayoungdolphm, agreed, but a good impl that we can say "see this is how hierarchy should be done"  would help the project discussion18:58
dolphmjamielennox: /v3/regions reflects the hierarchy18:58
jamielennoxdolphm: i can't go querying /v3/regions every time i want to query a catalog18:59
topolso a recommendation, it would be great to focus on one stakeholder project to try out v3 and deal with the kinks, bugs, etc and then use that as a reference success story for the other projects18:59
ayoungwhich means Nova18:59
dolphmjamielennox: there's just no correlation between /regions and regions in the service catalog yet ;)18:59
gyeetopol, ++18:59
*** jhesketh has joined #openstack-meeting18:59
*** jcoufal has joined #openstack-meeting18:59
dolphmtopol: ++18:59
jamielennoxdolphm: take US > US-EAST, if US-EAST is present in a service catalog and someone asks for something in the US region - how do it know?18:59
ayoungtimes up19:00
dolphmback to #openstack-keystone :)19:00
topolso for that one project we go all hands on deck and hold their hands to make is successful19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Apr  1 19:00:10 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-04-01-18.01.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-04-01-18.01.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-04-01-18.01.log.html19:00
*** tomoe_ has quit IRC19:00
jeblairanyone around for the infra meeting?19:00
*** balajiiyer1 has joined #openstack-meeting19:00
*** jamielennox has left #openstack-meeting19:00
*** rpodolyaka1 has joined #openstack-meeting19:00
*** lbragstad has left #openstack-meeting19:01
tchaypoI'm here to lurk19:01
jheskethjeblair: yes, but a little wild weather so may drop out19:01
pleia2jhesketh: here too, it's raining in san francisco! ;)19:01
*** aburaschi has joined #openstack-meeting19:01
anteayatchaypo: lurking encouraged19:01
*** brich1 has quit IRC19:01
SergeyLukjanovheh, and here too - snow and rain today - April 1, so...19:02
jeblairmordred, clarkb, fungi, AaronGr: ping19:02
*** ayoung has quit IRC19:02
jeblair#startmeeting infra19:02
openstackMeeting started Tue Apr  1 19:02:19 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
fungiso it is!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
rockygLurking, too :-)19:02
jeblair#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:02
anteayamore new faces/nicks19:02
jeblairagenda ^19:02
*** rakhmerov has quit IRC19:02
jeblair#link http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-03-25-19.01.html19:03
jeblairlast meeting ^19:03
anteayalooks like it is all jeblair on the agenda19:03
jeblair#topic  Actions from last meeting19:03
* anteaya sits back19:03
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:03
jeblairjeblair cname puppetboard.o.o and delete puppet-dashboard.o.o server and dns19:03
jeblairi half did that ^19:03
jeblairthe cname exists in dns now19:03
*** jcoufal has quit IRC19:03
jeblair#link http://puppetboard.openstack.org/19:03
*** jcoufal has joined #openstack-meeting19:03
jeblairi haven't deleted the old server yet though19:04
jeblair#action delete puppet-dashboard.o.o server and dns19:04
jeblair#action jeblair delete puppet-dashboard.o.o server and dns19:04
jeblairjeblair propose organizational cleanup repo renames to infra and then tc lists19:04
jeblairi also half-did that ^19:04
anteayaI see puppetdb.o.o still works19:04
jeblairin that i proposed it to the infra list, where we made some changes19:04
anteayakeep that?19:05
*** balajiiyer1 has left #openstack-meeting19:05
jeblairanteaya: yes it has to, the nodes are configured to report there19:05
* anteaya nods19:05
jeblairso i still need to send a revised version to the tc19:05
jeblair#action jeblair send revised repo rename list to tc19:05
jeblair#topic  Dealing with puppet changes (jeblair)19:06
*** openstack changes topic to "Dealing with puppet changes (jeblair) (Meeting topic: infra)"19:06
*** gothicmindfood has joined #openstack-meeting19:06
*** nibalizer has joined #openstack-meeting19:06
nibalizero/ im here!19:06
*** _nadya_ has quit IRC19:06
jeblairokay.  so we have puppetboard now, which means that theoretically we can land puppet changes and if they break stuff, it's not solely up to infra-root to deal with the carnage19:06
*** rpodolyaka1 has left #openstack-meeting19:06
jeblairbut i think yesterday we saw that we might need a bit more process around making that actually happen19:07
jeblairsince we broke puppet for most of the day, and the infra-root folks fixed it by reverting most of the changes19:07
*** neelashah1 has joined #openstack-meeting19:07
*** neelashah has quit IRC19:07
fungipart of the problem is that puppet manifests can be broken in certain ways which prevent them from being served and subsequently prevent reports from going into puppetdb19:08
*** blamar has joined #openstack-meeting19:08
*** markmcclain has quit IRC19:08
* mordred thinks that's a bug in puppet, btw19:08
clarkbI think this is a particular special case, and involves changes to the master19:08
fungiso the only outward signs we'd have would be of things not happening like we expect, and eventually nodes showing up as stale in puppetboard (after a day or more)19:08
mordredpuppet not being able to compile something seems like a thing you'd want reported :)19:08
*** jlibosva has quit IRC19:09
mordredit seems like we may want to have someone agree to watch puppetboard for success when we land puppet changes19:09
mordredthat person doesn't have to be infra-core per se of course19:09
fungiperhaps we should tune down the 24-hour limit before nodes show up as stale19:09
fungito help mitigate this too19:10
mordredand there is no way to increase the number of reports we keep, right?19:10
fungibut i do agree that having someone watch puppetboard for a report which shows the intended change got applied successfully would be a huge help19:10
*** gokrokve_ has joined #openstack-meeting19:10
jeblairmordred: not yet; apparently that's being worked on19:10
*** eguz has joined #openstack-meeting19:11
mordredepecially for things where it's clear that we want to watch it - such as the nibalizer/AaronGr hiera refactors19:11
jeblairnibalizer: do you know if we can lower the 'stale' timeout as above ^ ?19:11
*** walterheck_ has joined #openstack-meeting19:11
fungibasically the way i spotted it yesterday was that after i approved something which puppet should have updated and went to puppetboard to see when i should expect it to be working, i saw that the server in question hadn't reported for 2 hours19:11
*** dkranz has quit IRC19:11
jeblairmordred: so maybe our process for +A major puppet changes is that we make sure someone is on-deck and watching?19:11
nibalizerjeblair:  the 'unresponsive' you mean?19:12
fungitook me a few minutes to realize that the timestamps on the latest reports were waaay too old to be sane19:12
nibalizerthats a configuration options19:12
jeblairnibalizer: yes19:12
*** thuc has quit IRC19:12
nibalizereasy to change19:12
jeblairwe should be able to set that to, what, 30 mins and be okay?19:12
*** walterheck has quit IRC19:12
*** thuc has joined #openstack-meeting19:12
fungithat would mean three missed reports in a row, so sounds fine to me19:12
*** greghaynes has joined #openstack-meeting19:13
*** wenlock has joined #openstack-meeting19:13
*** ameade has quit IRC19:13
nibalizerI can push that change up today19:13
funginibalizer: thanks a ton19:13
nibalizerno prob19:13
jeblairso how about when a change hase 2 +2 votes, we leave a comment saying "ping an infra-core person in #openstack-infra when you are ready to monitor puppetboard for any adverse effects from this change" ?19:13
mordredjeblair: ++19:13
nibalizeralso, i would like a non-puppet task19:14
*** gokrokve has quit IRC19:14
jeblairand we wait for the driver of that change to ping us, so they drive the scheduling19:14
nibalizersince i love the puppets, but thats not havin me branch out much19:14
funginibalizer: we have plenty of those to choose from19:14
nibalizerjeblair: sounds good19:14
*** gyee has quit IRC19:14
*** denis_makogon has joined #openstack-meeting19:14
nibalizerfungi: where is the task list? and can you pick one thats good to 'warm up' on?19:14
fungi#link https://bugs.launchpad.net/openstack-ci/+bugs?field.tag=low-hanging-fruit19:14
funginibalizer: ^19:15
nibalizeroh perfect19:15
*** eghobo has quit IRC19:15
fungisome hang lower than others, but there's plenty to pick from19:15
*** fawadkhaliq has quit IRC19:15
jeblair#agreed infra-core will ask authors of major puppet changes to "ping an infra-core person in #openstack-infra when you are ready to monitor puppetboard for any adverse effects from this change" before approving19:15
fungijeblair: your plan sounds perfect to me19:15
clarkbyup sounds good19:15
jeblair#action nibalizer propose change to lower puppetboard 'unresponsive' timeout to 30 mins19:16
*** thuc has quit IRC19:17
*** hub_cap has joined #openstack-meeting19:17
jeblaircool; as you can tell from my wild swath of approvals, i'm very excited about getting these changes in.  :)  i hope this makes it smoother.19:17
jeblairanything else on the topic?19:18
fungican't make an omelette without breakign a few chickens19:18
jeblairspeaking of sacrificing poultry...19:18
jeblair#topic  Using storyboard (jeblair)19:18
*** openstack changes topic to "Using storyboard (jeblair) (Meeting topic: infra)"19:18
jeblairstoryboard is getting very close to the criteria where i think we can use it...19:18
fungi(is all i have to say to that)19:18
SergeyLukjanovwas afk, sorry, /me agreed re "[23:15:39]  <jeblair> #agreed infra-core will ask... "19:19
mordredjeblair: ++19:19
jeblairin case you missed it, that criteria, in my mind, solely consists of "it should be able to like track bugs and stuff".19:19
clarkbjeblair: are we going to bother with a migration of infra bugs?19:19
clarkbjeblair: or just start using it naturally and let things die in launchpad19:19
clarkbI assume we will need a migration for the other projects though19:19
mordredI believe we will definitely need a migration for other projects19:19
jeblairthat's more or less what i had in mind for this topic -- how, exactly, would we like to start using it.19:20
anteayaare we have a soft opening?19:20
fungii'm in favor of the attrition model there, but it could be painful for some users19:20
anteayalike having some people/projects using it?19:20
*** gokrokve_ has quit IRC19:20
jeblairanteaya: this should only extend to -infra projects; it's no where near ready for non-infra projects i think19:20
fungiwe could move, say, nodepool bugs to storyboard19:20
fungi(start small)19:20
* anteaya nods19:21
fungisince nodepool isn't broken out from openstack-ci on lp yet19:21
jeblairfungi: good point; start with nodepool, then maybe zuul....19:21
clarkbit may be good to guinea pig a migration with infra though19:21
anteayahow many people work with nodepool bugs?19:21
clarkbso reserve some subset of bugs for that maybe?19:21
SergeyLukjanovprobably, we should move more "active" bugs to storyboard19:21
fungiclarkb: zuul would be something we could potentially migrate, since it's an lp project in its own right now19:21
fungi(i think)19:22
SergeyLukjanovlike gate bugs?19:22
wenlocknot that i know much about story board, but what happens to a project that uses it for openid authentication, sense launchpad provides that... does it continue to go there?19:22
mordredclarkb: I thnk that' a good idea - move infra when we have a migration script19:22
mordredwenlock: at the moment we use launchpad for openid with storyboard19:22
jeblairmordred: storyboard has _all_ projects defined in it; i have a little bit of a concern with that19:22
jeblairmordred: in that i'm not sure how we best convey to people where bugs should be filed19:22
wenlockmordred, ahh cool19:22
*** pablosan is now known as zz_pablosan19:22
jeblairSergeyLukjanov: i think that gate bugs need to stay in storyboard until openstack itself moves19:23
mordredjeblair: we could disable the projects list creation and wipe the db... and/or make a second projects.yaml for storyboard for now19:23
jeblairbecause they are processed by e-r19:23
fungiwenlock: though i gather openstackid is coming along...19:23
fungi#link http://git.openstack.org/cgit/openstack-infra/openstackid/tree/19:23
*** mrmartin has joined #openstack-meeting19:23
SergeyLukjanovjeblair, doesyou mean in launchpad ?19:23
jeblairSergeyLukjanov: yes, sorry, should stay in launchpad19:23
clarkbjeblair: agreed19:23
SergeyLukjanovyup, got it, it's correct re e-r19:23
jeblairso i think even if we move "all" of infra to storyboard, we should keep using openstack-ci on launchpad for gate bugs to facilitate e-r19:24
fungithat makes sense19:24
jeblairmordred: i think that might be a good idea -- only listing projects in storyboard that use storyboard will help people keep track19:24
jeblairalso, if we migrate projects (eg zuul, gear), i think we can close their bug trackers on lp19:25
*** dkranz has joined #openstack-meeting19:25
mordredjeblair: agree. I think that ultimately I Want one projects.yaml - but for now, having two to track the migration makes sense19:25
mordredjeblair: you want me to take that on?19:25
jeblairmordred: that would be swell19:25
mordredalso - krotscheck ... how important are your current storyboard bugs in storyboard?19:25
fungia flag in projects.yaml perhaps, to define whether the project should be in storyboard (or should have a "not ready yet" placeholder on its stories or something)?19:25
jheskethare we going to require stackforge projects to switch?19:25
fungioh, you said that19:25
rockygWhen you close project on LP, need a message to redirect to Storyboard.19:26
mordredkrotscheck: as in - if we wipe stuff from teh current db in anticipation of a move of infra things in ...19:26
jeblair#action mordred make an abbreviated projects.yaml with only projects using storyboard as their primary tracker19:26
clarkbjhesketh: I don't think we have ever forced a bug tracker on stackforge projects19:26
jheskethright, so getting down to one projects file may be tricky19:26
fungirockyg: yeah, worst case when we disable bugs on a project in lp we can update its main overview with a link to storyboard19:26
clarkbjhesketh: however, supporting both launchpad and storyboard may be a pain so we might have to19:26
mordredkrotscheck: do we need to be careful to not bork your datas? or can we just drop and re-create the db?19:26
jeblairmordred: what do we need to delete?19:27
jeblairmordred: we can just delete all projects that != storyboard, right?19:27
*** akuznetsov has quit IRC19:28
mordredjeblair: the existing 250 projects -and I thin kthere are some fake stories in there19:28
mordredjeblair: sure19:28
mordredjeblair: yeah - good point- it's not that hard19:28
jheskethin terms of supporting both launchpad and storyboard is there a plan to manage features provided by jeepyb? For example, if you have "closes-bug xyz" how do we clarify which system that is in19:28
mordredjhesketh: ultimately we don't19:28
jhesketh(currently it looks like story numbers are sequential)19:28
jeblairmordred: what if instead of making another projects.yaml, we just stopped using it for auto-project creation and left that as a manual superuser function for now?19:28
mordredjeblair: fine by me19:28
fungijhesketh: though i think it's something we will need--i just doubt anyone's started planning that bit yet19:29
*** zz_pablosan is now known as pablosan19:29
*** mattgriffin has quit IRC19:29
fungijhesketh: for example, we could s/bug/story/ in our standard commit message headers and comment links19:29
*** malini is now known as malini_afk19:29
mordredif we had a "uses-storyboard" flag in projects.yaml - it would be fairly easy to do a lookup on projects.yaml to see where most things should direct themselves to19:29
*** otherwiseguy has joined #openstack-meeting19:29
fungibit of a pain for people to remember which to use though19:29
mordredwith the exception of gerrit links19:30
fungimordred: good point wrt hooks at least19:30
* ttx lurks19:30
fungiless so for links19:30
jeblairmordred: has anyone volunteered to make a lp -> storyboard import script?19:30
*** walterheck_ has quit IRC19:30
mordredjeblair: I think nibalizer just did19:30
jheskethmordred: so if we have a 'uses-storyboard' flag we could use the one projects file and only set up storyboard for those projects?19:30
jeblairmordred: that's how i read that too.  ;)19:30
mordredjhesketh: yah19:31
jeblairjhesketh: ++19:31
mordredmight be a two-birds/one-stone approach19:31
mordredonly undefined thign will be gerrit comment links19:31
nibalizeri'm down19:31
*** zehicle_at_dell has joined #openstack-meeting19:32
jeblair#action nibalizer write lp->storyboard migration script19:32
fungizaro: i don't suppose new gerrit can make logic decisions in its text linking?19:32
mordreddo comment links have access to project name? they don't do they?19:32
clarkbmordred: they have access to the comment itself, which doesn't have the project name19:32
jeblairnibalizer: there's a bunch of launchpad api using code in jeepyb you can use for reference...19:32
clarkbmordred: I think we will be in a weird spot with commentlinks19:32
mordredbecause if we could get project-name into the data that the javascript has, we could make a javascript callout thing19:33
zarofungi: i'm not aware that's possible.19:33
jeblairnibalizer: no one has ever written a python interface to storyboard, so that'll be exciting and new.  :)19:33
fungizaro: it was wishful thinking. thanks though19:33
nibalizerooo, does it have a rest api ?19:33
mordrednibalizer: it does19:33
nibalizerwell then game on!19:33
jheskethmordred: it's not very neat, but as a short-term if gerrit isn't able to handle it you could send all requests to storyboard and if the project doesn't have 'uses-storyboard' flag it can redirect to launchpad19:33
nibalizernot that i dont LOVE xmlrpc but..19:33
mordredjhesketh: ooh. that's sexy19:33
fungiI LIKE19:33
fungior some decider proxy anyway19:34
*** ociuhandu has left #openstack-meeting19:34
fungidoesn't have to be embedded in storyboard itswlf19:34
jeblaircould that be a bit of wsgi we stack on top of storyboard?19:34
mordredjust to be clear, we can probably be  broken for comment links for the zuul/nodepool move...19:35
jeblairmordred: yeah, i think we can live with that19:35
jeblairjhesketh: can you add a story to the storyboard project about the wsgi/redirect idea?19:35
fungiit would be tolerable for a little while19:36
jheskethjeblair: yep19:36
jeblairokay, i think we have the better part of a plan19:37
mordredI read that word as palm19:37
*** mrmartin has quit IRC19:37
mordredwhich is a very different sentence19:37
jeblair#topic open discussion19:37
*** openstack changes topic to "open discussion (Meeting topic: infra)"19:37
*** caleb_ has quit IRC19:37
*** zns has quit IRC19:38
pleia2I have 2 things, first is that we're very close to retiring old-wiki, of the two outstanding tasks bug 1172440 has a review up that will close it and 1127411 should be pretty trivial (moving apache configs over to static.o.o)19:38
uvirtbotLaunchpad bug 1172440 in openstack-ci "bug day stats should be in openstack-infra" [Medium,In progress] https://launchpad.net/bugs/117244019:38
fungireminder, grizzly is dead, dead, deadski19:38
pleia2bug 112741119:38
jeblairpleia2: wow, that's hard to believe that we could ever retire old-wiki19:38
uvirtbotLaunchpad bug 1127411 in openstack-ci "Move the $project.openstack.org redirects off of old wiki" [Medium,Triaged] https://launchpad.net/bugs/112741119:38
pleia2jeblair: I know!19:38
pleia2I'm excited :)19:39
clarkboh right I need to review that change again19:39
*** aswadrangnekar has left #openstack-meeting19:39
fungideleted the stable/grizzly branches and removed the jobs/d-g support over the weekend19:39
clarkbfungi: woot!19:39
fungiin case anyone asks19:39
clarkbfungi: should we prep the addition of icehouse jobs yet?19:39
mordredfungi: woot!19:39
pleia2my 2nd thing is that I've been chatting with Daisy, things are crazy this time of the cycle but she thinks Pootle will work, wasn't keen on the wiki idea, so she'll pick up Pootle evaluation once translations are done, hopefully we can chat about it again at the summit and start serious work at the beginning of the cycle19:40
fungiclarkb: probably not too early to get started on the config reviews for those. we might even be able to land them before the stable branches exist, not positive though19:40
clarkbpleia2: there is another proposed session to talk about it again19:40
pleia2clarkb: good19:40
*** nealph has quit IRC19:40
pleia2I hadn't paid attention to summit sessions yet19:40
jeblairpleia2: cool, i think having someone really driving that (as you have volunteered to do!) will really help.  :)19:40
fungigrenade jobs would probably have to wait, though... can't upgrade from havana to icehouse sanely when there's no icehouse branch for anything19:41
clarkbfungi: ya, we should probably propose the change then WIP it for now19:41
clarkbif we get that far along before stable/icehouse branches are cut19:41
fungipleia2: i will miss our twice-a-year discussion about moving translations though, if it actually ends up happening this time19:41
fungiin other news, it just dawned on me we have another gauge of how much busier we've gotten... nobody had time for april fools changes to zuul comment strings this year :(19:42
nibalizerno i tried19:43
clarkbjeblair: I will have a zuul change pushed shortly. Mostly want your thoughts on the way the tests have been hacked, to make sure I haven't gotten lost in the woods19:43
nibalizeri just couldn't figure it out19:43
nibalizeri even had two pokemon gifs lined up for pass/failure19:43
pleia2so much pokemon this 1st19:43
jeblairoh that's what that was about ;)19:43
fungipleia2: gotta catch 'em all!19:43
jeblairnibalizer: you may have been able to do it with a commentlink change in gerrit19:43
jesusaurusclarkb: did greghaynes make a change for his thing?19:44
jeblairnibalizer: so 's/FAILURE/<img src...>/'19:44
clarkbjeblair: no19:44
clarkber jesusaurus ^19:44
jheskethso I have an item for the open discussion, we need to configure a swift container to push openstack logs to.. this will allow jobs to individually move over to pushing to swift rather than the big log server19:44
greghaynesYes, too busy :(19:44
mordredjhesketh: I support this19:44
clarkbjhesketh: jeblair: right so I think this is still the biggest unanswered question for me as far as swift goes19:45
fungijhesketh: i can probably add one and get the right creds into hiera19:45
clarkbhave we fixed the CDN is terrible problem yet?19:45
jheskethclarkb: we're not using a CDN19:45
jesusaurusclarkb: what arethe issues with cdn?19:45
fungijhesketh: i did it a while ago, and can probably muddle my way through again19:45
jeblairclarkb: we don't need to use it because we'll be serving them via os-loganalyze19:45
clarkbjhesketh: you have to for public access unless that changed19:45
*** TravT has quit IRC19:45
clarkbjeblair: iirc all public access is via CDN19:45
jheskethI've patched osloganalyze to stream from swift19:45
fungiclarkb: yeah i think if it's in the same account and region as static.o.o, that works right?19:46
*** gokrokve has joined #openstack-meeting19:46
jheskethclarkb: https://review.openstack.org/#/c/76796/19:46
clarkbfungi: accoutn and region shouldn't matter if we give osloganalyze a way to read fro mthere19:46
clarkbfungi: but I think that is as good a place to put it as any19:47
clarkbfungi: reduces latency in theory too19:47
fungiahh, okay. wasn't sure if there were additional controls in place besides just knowing the url19:47
clarkbfungi: there are, pretty sure it will need credentials19:47
clarkbsince this will be not public access19:48
fungiright, 76796 uses them19:48
fungisee the wsgi.conf placeholders19:48
jheskethyeah, so os-loganalyzer now needs a config for swift params19:48
fungithose will need to become vars in a puppet erb in the config repo19:49
clarkbalso, is there any concern that one container won't be enough?19:49
fungiand then we'll put whatever we generate into hiera19:49
* clarkb should probably catch up on the swift stuff later19:49
*** sjcazzol has quit IRC19:49
jheskethclarkb: good question19:49
fungijhesketh: right i know at one point we talked about needing to rotate containers to get around size limits or performance concerns19:49
clarkbfungi: correct, particularly for listings, but osloganalyze can possible deal with that for us too19:50
*** mattgriffin has joined #openstack-meeting19:50
fungiright, if it was just the link count in the container which was at issue, then maybe it's irrelevant now19:50
jeblairyeah that'll be a lot easier to deal with if we aren't trying to figure out a single immutable public url with multiple containers in use19:51
mordredall hail osloganalyze19:51
clarkbfungi: actually, maybe we should put the test logs in the test account19:52
clarkbfungi: that way the resources are segragated based on role19:52
clarkbstatic happens to serve them but they belong to the test account19:52
fungiclarkb: you mean openstackjenkins vs openstackci?19:53
*** TravT has joined #openstack-meeting19:54
jeblairhrm.  i lean toward openstackci -- because we're creating the container19:54
fungii suppose, from a bookkeeping standpoint. but from a security separation standpoint they are more closely related to the systems in the openstackci account which generate the tokens for writing to and then later read from them19:54
*** sdake_ is now known as sdake__19:54
jeblairif jenkins were creating them, i think the openstackjenkins would be more appropriate19:54
*** yamahata has joined #openstack-meeting19:55
jeblairfungi: because, yeah, the security separation is the main benefit there i think19:55
*** slong has joined #openstack-meeting19:55
clarkbI see the security benefit as being the inverse here19:55
fungii see there being only a marginal security benefit regardless19:55
*** slong has quit IRC19:55
clarkbif loganalyze gets owned we only expose the test slaves and their data to corruption/abuse19:56
clarkbwith the other account its everything19:56
*** thuc has joined #openstack-meeting19:56
jeblairclarkb: osloganalyze doesn't have the _account_ credentials regardless19:56
clarkbjeblair: how does it have access then?19:56
fungiyeah, this would be a dedicated api key, right?19:56
clarkbI thought the hp patch to make ^ a thing was never merged to keysteon19:57
jeblairclarkb: wow, i sure hope you can grant read/write access to swift without _also_ giving the ability to spin up servers and delete all data in other services.19:57
* fungi revisits what creds are being handed to openstackwatch for writing to swift19:57
*** baoli has joined #openstack-meeting19:58
*** baoli has quit IRC19:58
*** baoli has joined #openstack-meeting19:59
jheskethfungi: https://github.com/openstack-infra/jeepyb/blob/master/jeepyb/cmd/openstackwatch.py#L12119:59
*** marcoemorais has quit IRC19:59
*** marcoemorais has joined #openstack-meeting19:59
jheskethso I'm not sure about the security but it's something I'll have a look into19:59
*** rakhmerov has joined #openstack-meeting19:59
*** marcoemorais has quit IRC19:59
mordredI'm pretty sure swift has container acls19:59
clarkbwe can use http://www.rackspace.com/blog/reduce-human-error-with-role-based-access-control-for-rackspace-cloud/19:59
mordredthat are not related to the hp patch that didn't merge20:00
*** marcoemorais has joined #openstack-meeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Apr  1 20:00:21 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-04-01-19.02.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-04-01-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-04-01-19.02.log.html20:00
*** gothicmindfood has left #openstack-meeting20:00
*** markmc has joined #openstack-meeting20:00
*** shwetaap has quit IRC20:00
ttxAnyone here for the TC meeting ?20:01
*** akuznetsov has joined #openstack-meeting20:01
*** mattgriffin has quit IRC20:02
*** marcoemorais1 has joined #openstack-meeting20:02
*** zns has joined #openstack-meeting20:02
ttxannegentle, mikal, mordred, jgriffith, vishy, markmcclain, jeblair, lifeless, sdague : around ?20:02
*** markmcclain has joined #openstack-meeting20:03
lifelessttx: somewhat, tripleo-cloud is still fighting stability and thats a critical20:03
*** mwagner_afk has quit IRC20:03
*** rbrady has quit IRC20:03
*** tchaypo has left #openstack-meeting20:03
*** zns has quit IRC20:03
ttx#startmeeting tc20:03
openstackMeeting started Tue Apr  1 20:03:45 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
*** openstack changes topic to " (Meeting topic: tc)"20:03
openstackThe meeting name has been set to 'tc'20:03
ttxOur agenda for today:20:03
*** rakhmerov has quit IRC20:03
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:03
ttx#topic Integrated projects and new requirements: Gap analysis for Keystone20:04
*** openstack changes topic to "Integrated projects and new requirements: Gap analysis for Keystone (Meeting topic: tc)"20:04
ttxOur guest for this week is... dolphm!20:04
ttxdolphm: o/20:04
ttxDid you prepare an etherpad for the analysis ?20:04
dolphmyep! https://etherpad.openstack.org/p/keystone-incubation-integration-requirements20:04
*** marcoemorais has quit IRC20:04
*** radez is now known as radez_g0n320:04
dolphmi crossed out a few things that are fairly given20:04
markmcdolphm, thanks20:04
lifelessttx: specifically, please ping me for input, as I'll miss things - sorry20:05
dolphmand/or not relevant for an already-integrated project20:05
markmcdolphm, you couldn't change your colour to something lighter?20:05
* markmc colour-blind :)20:05
russellbmarkmc: thanks20:05
ttxlifeless: understood20:05
*** derekh has quit IRC20:05
russellbwas burning my eyes20:05
dolphmmarkmc: how's that? i actually just turn off all colors in etherpad completely20:05
ttx#link https://etherpad.openstack.org/p/keystone-incubation-integration-requirements20:05
markmcdolphm, great, thanks20:05
dolphmgear icon -> authorship colors20:05
markmcrandom question to start with20:06
mikaldolphm: so reading through, what's your plan to deprecate the v2 API (if at all)?20:06
mordreddolphm: on the api stability - I've heard folks talking about v2 deprecation but also that v3 isn't supported everywhere yet  - is that a thing that shoudl be poked at?20:06
markmcif the mission is clear, why was there debate as to whether barbican functionality or KDS belongs in keystone20:06
mordredmikal: jinx20:06
russellbwe had a thread on that recently on -dev20:07
dolphmmikal: working to formalize that very soon as part of https://blueprints.launchpad.net/keystone/+spec/document-v2-to-v3-transition20:07
mordredoh good20:07
*** ayoung has joined #openstack-meeting20:07
dolphmmikal: we also discussed a bit today in our keystone meeting, but the gist is that our next step is to start integrating our latest client work into other projects20:07
russellbre keystone v2: http://lists.openstack.org/pipermail/openstack-dev/2014-March/031016.html20:07
*** mdurnosvistov1 has left #openstack-meeting20:07
dolphmmordred: does that answer your question? ^20:07
*** walterheck has joined #openstack-meeting20:07
mordredrussellb: thanks20:07
markmc#link http://lists.openstack.org/pipermail/openstack-dev/2014-March/031016.html20:07
dolphmrussellb: ++20:07
mikaldolphm: cool. What sort of timeline do you have in mind?20:07
mordreddolphm: yup20:07
markmc#link https://blueprints.launchpad.net/keystone/+spec/document-v2-to-v3-transition20:08
russellbttx did a nice job summarizing the ideal workflow for moving toward deprecating v3: http://lists.openstack.org/pipermail/openstack-dev/2014-March/031040.html20:08
dolphmmikal: we'll do our best to help as many projects as we can move to v3 during juno, but my goal is to have all the integrated projects on v3 in 6 months20:08
*** gduan has quit IRC20:09
mikaldolphm: ok, sounds like a good start to me20:09
mordredI think that's an excellent plan20:09
ttxthat plan is valid for all API deprecations btw20:09
markmc#link http://lists.openstack.org/pipermail/openstack-dev/2014-March/031040.html20:09
russellbttx: +120:10
*** garyduan has joined #openstack-meeting20:10
ttxmaybe I should turn that into a wikipage20:10
markmcttx, could be good to add to openstack/governance20:10
markmcas guidelines20:10
russellbyeah, i like that20:10
sdagueone of the questions I had regarding the stable interface, is there seems to be a large amount of work done in keystone client relative to the other clients (which are mostly thin access layers on the API). How does that impact the definition of a stable API?20:10
ttx#action ttx to propose Api deprecation workflow guidance to openstack/governance20:11
russellbthis v2 / v3 situation is really the only concern i had for keystone, and it's an issue that applies more broadly, they just happened to get it brought up very recently20:11
markmcsdague, got an example?20:11
dolphmsdague: referring to session or auth_token or something specifically?20:12
*** Tross has quit IRC20:12
sdaguedolphm: mostly I think on the session and auto_token front20:12
russellbdoes the client do a lot more than "thinly" wrap the API?20:12
ttxdolphm: I have one question, about the middleware and it being shipped with the client library20:12
sdagueit has a pretty substantial caching layer20:12
dolphmttx: your deprecation outline could be a revision to this https://wiki.openstack.org/wiki/APIChangeGuidelines20:12
sdaguewhich was the cause of the last CVE20:12
*** akuznetsov has quit IRC20:13
*** dburmistrov has quit IRC20:13
ttxdolphm: i think that's an artifact from the time where you only had the main project and client library allowed20:13
russellbthe API change guidelines could be modified to be TC curated, as well20:13
ttxNow that we live in a program world, I wonder if the middleware shoudln't just be shipped separately20:13
russellbsomething worth standardizing on20:13
dolphmrussellb: session is intended to manage authentication state for other clients (and dogfooded by keystone)20:13
markmcsdague, when we say "stable API" I assume we mostly mean REST API20:13
sdaguemarkmc: yes, agreed20:13
markmcsdague, python API stability good too, but applies to all libraries we publish20:14
*** Sukhdev has quit IRC20:14
dolphmauth_token shouldn't be seen as much more than a slightly privileged identity client with a unique interface20:14
sdaguebut when we did our keystone & heat & tempest session in HK there was definitely a bunch of disconnect20:14
ttx(my question is slightly off-topic since we talk abot keystone, not keystoneclient, but meh)20:14
sdagueat the time there was almost no keystone direct tested20:14
sdagueit was all through the library20:14
sdagueit's much better now20:14
annegentlettx: russellb: I have a question related to the v2/v3 deprecation messaging -- drawing parallel to the XML deprecation. I can put it in a mailing list post, but generally wanting to define the discussion channels and how do we know we have properly discussed20:15
markmcttx, middleware is API client code, makes conceptual sense to live in keystoneclient IMHO20:15
annegentlenot trying to be off topic but I see parallels20:15
markmcttx, not that I care much either way - just don't see an issue20:15
russellbannegentle: fair20:15
*** Michalik- has quit IRC20:15
dolphmmarkmc: the only issue is packaging -- auth_token may have additional dependencies that a thin client library should not20:15
ttxmarkmc: ok -- it just is an infinite source of vulnerabilities while we don't issue that many on other "clients". I guess we can live with that if it makes conceptual sense20:16
mordreddolphm: so by splitting, you could potentially make having the other client libs consume keystoneclient easier?20:16
annegentlerussellb: it means DocImpact is working, so that's good... just not sure how/when to document the impact20:16
sdagueright, like the fact that there have been a lot of race conditions in the cache layer corrupting tokens20:16
ttxwe could also update the middleware more easily20:16
*** walterheck has quit IRC20:16
sdagueI think we fixed 3 of those this cycle20:16
dolphmmordred: it'd make the dependency graph cleaner - i don't know about easier20:16
mordreddolphm: :)20:16
russellbannegentle: talking about nova XML?  yes, a lot more discussion is needed before any real action is taken IMO20:16
mordreddolphm: easier socially - less extra deps pulled in20:17
ttxotherwise when we bump the middleware for security reasons, we have to collect the new client stuff in the same "release"20:17
dolphmmordred: then sure20:17
annegentlerussellb: okay, I saw a patch with the word deprecation in a message, so I'll follow up on list20:17
markmcall sounds like reasonable reasons to split out20:17
*** Michalik- has joined #openstack-meeting20:18
markmcdolphm, repeating mission/scope question - if the mission is clear, why do you think there was debate as to whether barbican functionality or KDS belongs in keystone ?20:18
russellbannegentle: yes it's marked deprecated, but discussion needed before we can totally pull the plug.  been trying to get usage data from deployers and such.20:18
dolphmwe also do crypto work in keystoneclient, which is consumed by both auth_token and the keystone service -- we'll likely see more of that moving forward20:18
ttxdolphm: if we did that (separate middleware from lib), let's aim for the beginning of a cycle to do it20:18
dolphmttx: ack, i think we have a relevant summit session proposed already20:19
ttxmarkmc: I think it was more of a timing issue originally. Then the debate came from that original suggestion20:19
ttxmarkmc: i.e. we said "in keystone" because we needed it somewhere and keystone was the first consumer20:19
dolphmmarkmc: both deal with secrets/credentials to an extent - i think it's a valid conversation to have20:20
ttxand then when barbican came along I asked "so.. would the KDS still live in keystone ?20:20
dolphmttx: ++20:20
ttxbut wityh barbican positioning as the main purveyor of secrets, I think the KDS makes sense in barbican20:20
sdaguehonestly, on the QA side the keystone team stepped up a lot this cycle. I think we end up hitting v2 API about 2k times (including indirects through keystone client) and v3 API about 500 times over the course of a full tempest run20:20
markmcdolphm, ok, cool - and consensus has been reached now20:20
dolphmttx: ++ KDS is definitely more closely related to barbican than to keystone20:20
*** Tross has joined #openstack-meeting20:21
dolphmsdague: wow, and we're working to reduce API chatter lol20:21
sdaguewe create and tear down a lot of users for tenant isolation20:21
dolphmwe also have a substantial number of functional API tests within keystone.tests20:22
sdagueso keystone gets a nice extra work out from that20:22
sdagueevery tempest class runs under a different user & tenant20:22
ttxLast tricky question... performance. keystone has been ignored in te past due to poor performance. Would you say that today those concerns are no longer valid ?20:22
mordreddolphm: may be out of scope for this meeting - but should we do a keystone-functional test aginst the devstack cloud like we do for swift-functional?20:22
ttxi.e. we don't hit it that much in regular operation so its no longer a performance bnottleneck ?20:22
dolphmstill valid -- but we have two MAJOR changes in the pipeline that will radically improve performance20:22
russellbdolphm: what are they?  tl;dr version :)20:23
ttxnow I'm curious20:23
dolphmin short: ephemeral, compressed PKI tokens w/ revocation events20:23
russellbah, event based revocation instead of polling keystone 1/second from everywhere to check the latest CRL?20:23
jogowill those contain the catalog in them like current PKI tokens?20:23
dolphmno more token backend in sql/memcached/whatever, no more issues with 8k tokens, and faster distribution of revocation events to services needing to validate (and invalidate) tokens quickly20:24
dolphmrussellb: yes20:24
*** gyee has joined #openstack-meeting20:24
russellboslo.messaging notification based or what?20:24
ttxare those changes Juno material ?20:24
dolphmwe landed revocation events in icehouse, but haven't taken advantage20:24
russellbhow do you get the events?20:24
dolphmrussellb: all HTTP right now, but it could be moved to HTTP + messaging20:24
dolphmrussellb: we needed HTTP either way20:24
*** nibalizer has left #openstack-meeting20:25
russellblong polling i guess?20:25
sdaguedolphm: long poll on http?20:25
* markmc thinks we're in the weeds :)20:25
*** shwetaap has joined #openstack-meeting20:25
dolphmrussellb: we're just doing GET /v3/OS-REVOKE/revocations_events and then polling for updates with something like GET /v3/OS-REVOKE/revocations_events?since=<timestamp>20:25
markmcinteresting, but ...20:25
dolphmmarkmc: yeah lol20:25
ttxmarkmc: nice weeds20:25
sdaguemarkmc: fair :)20:25
dolphmanyway, i'd like to move to messaging :)20:25
*** julim has quit IRC20:25
russellbdolphm: that sounds like polling, heh20:25
ttxOK, let's wrap it up20:25
russellbanyway, later is fine :)20:25
ttxI think we didn't find any gap20:25
ttxor I missed them in the flow20:26
dolphmttx: and yes, they should all land in juno20:26
*** Tross has quit IRC20:26
ttxagree ?20:26
russellbttx: agree20:26
sdaguettx: yes, I think so20:26
russellbdolphm: nice work to the whole keystone team20:27
markmcclainttx : yep20:27
ttx#info No gap found between Keystone current state and integration requirements20:27
dolphmcool, thanks everyone20:27
dolphmrussellb: /salute20:27
*** eguz has quit IRC20:27
ttxdolphm: congrats!20:27
*** mrda_away is now known as mrda20:27
ttxfwiw keystone has been hitting releasemanagement deadlines like a swiss clock lately20:27
ttxno feature freeze exception, first out of RC120:27
*** eghobo has joined #openstack-meeting20:28
ttxso it looks very sane20:28
ttxMoving to next topic.20:28
ttx#topic Status update on Defcore progress20:28
*** openstack changes topic to "Status update on Defcore progress (Meeting topic: tc)"20:28
ttxmikal, annegentle, zehicle_at_dell: o/20:28
*** branen has joined #openstack-meeting20:28
ttxI read the summary, looks like you made good progress at the last meeting20:28
mikalSo I missed the most recent meeting20:29
ttx#link https://etherpad.openstack.org/p/openstack-designated-sections20:29
ttxI think annegentle mordred dhellmann russellb markmcclain and jeblair were there for the TC20:30
zehicle_at_dell#link https://etherpad.openstack.org/p/openstack-designated-sections20:30
*** zns has joined #openstack-meeting20:30
* jgriffith missed it sadly20:30
zehicle_at_dellI uploaded the recording and it's on the link20:30
dhellmannI thought that meeting went well. I know I have a much clearer picture of what sort of answer we need to put together.20:30
russellbso i think next step is we need to finish filling out and vetting proposed designated/replaceable sections, yes?20:31
dhellmannrussellb: yes, that todo is to be completed "at or by the juno summit"20:31
zehicle_at_dellwe also have a request to have an official TC approval of the principles20:31
ttxzehicle_at_dell: are there specific PTLs which you need input from which haven't made contact yet ? Which we could track down for you ?20:31
jeblairyes, the most useful things out of that meeting related to scope and direction; we did not get into the details too much; so i think what's in the etherpad is still very much 'strawman'20:32
ttxzehicle_at_dell: The selection principles make sense to me20:32
russellbgenerated by PTLs, collected/blessed by this group?20:32
*** haomai___ has quit IRC20:32
ttxzehicle_at_dell: the selection principles ?20:32
dhellmannrussellb: yes, some combination of that20:32
russellbselection principles seem sane to me20:32
ttx(official approval of the selection principles ?)20:32
dhellmannttx: there is a list in the etherpad20:32
sdaguezehicle_at_dell: consumers ther seems to be defined mostly as operators & packagers?20:32
zehicle_at_dellttx, I think that we'll know which projects are critical soon because they are likely to have  must-pass candidates20:32
*** e-vad has left #openstack-meeting20:33
*** fawadkhaliq has joined #openstack-meeting20:33
zehicle_at_dellttx, that's the title on the wiki page20:33
ttxzehicle_at_dell: OK I'll prepare a proper resolution for approval of the selection principles20:33
ttxzehicle_at_dell: probably for next week meeting given the usual delay20:33
*** jmontemayor has quit IRC20:34
*** lukego has joined #openstack-meeting20:34
markmcwhere are the selection principles?20:34
ttxTC members: if the ones on the etherpad are completely unreasonable for you, speak now20:34
ttxon the etherpad20:34
markmcoh, zehicle_at_dell said wiki20:34
*** kgriffs|afk is now known as kgriffs20:34
sdagueyeh L27 in the etherpad20:34
zehicle_at_dellnot focused enough, etherpad :/20:34
jeblairi think they are reasonable20:35
ttxI like the "cross-platform" one20:35
markmccool, there are other defcore principles on the wiki :)20:35
ttxwe are people of principles20:35
*** jecarey has quit IRC20:35
zehicle_at_dellmarkmc, yes20:35
markmc"balance between the commercial ecosystem and the community ecosystem."20:35
ttx#action ttx to draft TC resolution on selection principles20:35
markmcgiven that this is exclusively about "the commercial use of the brand"20:36
dhellmannwe may need to refine the one on line 40 about developer intent -- ceilometer has some plugin APIs for which we don't expect the pieces to be replaced but they can be supplemented20:36
markmcwhy the reference to the community ecosystem ?20:36
*** megan_w|afk is now known as megan_w20:36
sdaguedhellmann: that's not covered by API extension?20:36
*** haomaiwang has joined #openstack-meeting20:36
zehicle_at_dellmarkmc, because the intent of designated sections is to encourage upstreaming20:36
dhellmannsdague: those plugins are not part of the rest api20:36
mordredmarkmc: we want to incentivize the commercial ecosystem to continue to participate in teh community20:36
*** kgriffs is now known as kgriffs|afk20:36
dhellmannsdague: IIRC, every use of "API" in that doc means "REST API"20:37
markmcok, thanks20:37
*** jcoufal has quit IRC20:37
sdagueok, maybe worth clarifying20:37
russellbby explicitly letting them replace stuff, cool :)20:37
sdaguebecause on something like HEAT, the rest API is really minimal, and the payload is what's important20:37
*** gduan has joined #openstack-meeting20:38
sdaguelike heat without hot, seems no good to me, but hot isn't strictly the rest api20:38
*** garyduan has quit IRC20:38
dhellmannsdague: similar for ceilometer -- we wouldn't want a sample collection plugin to be replaced with one that has different behavior, but adding new ones is allowed20:38
markmcREST starts with Representation20:38
markmcpretty clear payload is part of it20:38
*** zzelle has joined #openstack-meeting20:39
sdaguesure, fair, I guess I don't understand how API extension doesn't cover ceilo then :)20:39
sdaguebut we can go off in the weeds elsewhere20:39
dhellmannsdague: adding a new sample doesn't require any change to the API of ceilometer20:40
zehicle_at_dellgood clarification - we expected that this would be extended in discussion20:40
dhellmannsure :-)20:40
ttxtimeboxing this to 5 more minutes20:40
ttxwell, unless nobody has anything to add, obviously20:41
jeblairttx: that was too effective20:41
ttxjeblair: weird20:41
ttxwell then20:41
ttxnext topic ?20:41
sdaguego for it20:42
ttx#topic More post-graduation expectations20:42
*** openstack changes topic to "More post-graduation expectations (Meeting topic: tc)"20:42
ttx* Add API graduation/post-graduation requirements (https://review.openstack.org/68258)20:42
ttx* Add Heat integration post-graduation expectation (https://review.openstack.org/81773)20:42
ttx* Add Horizon integration post-graduation expectation (https://review.openstack.org/81774)20:42
ttxSince the requirements doc reflects consensual requirements, I waited for majority of approvals on it20:42
ttxOne of them still misses majority vote (https://review.openstack.org/#/c/68258/)20:42
*** caleb_ has joined #openstack-meeting20:42
ttxyep, only 620:42
ttxBut it's been on the table for a few meetings now, so I think we need to make the final vote on it.20:43
markmcweird, that was the least controversial one I thought :)20:43
ttxFinal vote means it should be accepted if it gathers 5 +1s (and less than 5 -1s). So if you don't like it, make sure to cast your vote asap20:43
ttx#info Final vote called on https://review.openstack.org/#/c/68258/20:43
markmcbah, had a draft reply to dhellmann saved there20:43
ttxWill collect the result of the "final vote" tomorrow morning, to give absent members a chance to -1 it :)20:43
ttx(with the current votes it will get accepted tomorrow morning)20:44
*** IlyaE has quit IRC20:44
ttxcomments on that ?20:44
*** dims_ has quit IRC20:44
ttxanyone wants to push the 7th +1 ?20:44
*** stevemar2 is now known as stevemar20:44
dhellmannI think jgriffith just did?20:44
ttxok thx!20:45
ttx#topic Minor governance changes20:45
*** Longgeek has quit IRC20:45
*** openstack changes topic to "Minor governance changes (Meeting topic: tc)"20:45
ttx* Fix post-graduation expectation typo (https://review.openstack.org/83765)20:45
ttxWill just approve that one as typo fix now20:45
*** jecarey has joined #openstack-meeting20:46
*** mspreitz has joined #openstack-meeting20:46
ttxI .. just can't see the typo20:46
dhellmannmissing letter20:47
russellbsometimes i need unified view to see that stuff, heh20:47
ttx#topic Open discussion20:47
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:47
ttxGot one quick question for you all20:47
russellblooks like there's a couple other changes up now20:47
markmcclainlow hanging fruit change: https://review.openstack.org/#/c/84489/20:47
markmcdo we have plans for a TC pow-wow at the summit yet?20:48
ttxHow do you want us to select the cross-project workshops ?20:48
markmcaside from the joint meeting with the board20:48
ttxshould the newly-elected TC members do it ?20:48
ttxShoud the PTL group do it ?20:48
*** walterheck has joined #openstack-meeting20:48
dhellmannmarkmc: didn't we appoint mordred as our meat-space event coordinator?20:48
mordreddhellmann: I book dinners20:48
ttxdhellmann: as long as the event is not held in Paris20:48
mikalmordred: good dinners20:48
dhellmannmordred: they serve meat at dinner20:48
mordreddhellmann: mmm. meat20:49
* markmc does like a good mordred dinner20:49
russellbfogo de chao!20:49
markmcwas thinking whether a non-social pow-wow would be good ?20:49
markmcmaybe before it?20:49
* mordred was going to suggest the same thing20:49
jeblairttx: ptls?20:49
sdaguemarkmc: +1 on non social pow wow20:49
*** sballe has joined #openstack-meeting20:49
dhellmannmarkmc: I like it20:49
russellbsorry i was still thinking about meat20:49
russellbbut +1 on a working session20:49
mordredgetting some space to dive in to deeper tech questions20:50
ttxjeblair: I have no strong opinion on it. The PTLs group already schedule the rest of the summit, so asking them makes sense20:50
dhellmannbefore or after the summit?20:50
dhellmannor during, even?20:50
mordreddhellmann: I vote for before20:50
mikalWe need to decide soon because of travel bookings20:50
ttxI'll be in on the Saturday afternoon20:50
dhellmannmordred: sunday is the board meeting, do you mean before sunday?20:50
russellbttx: PTLs are also very busy with their scheduling, maybe it makes sense for the TC to lead the cross project stuff?20:50
ttxSunday afternoon is the TC/BoD joint thing20:50
mordredoh right20:50
sdaguettx: I think it would be good for at least you to be in on the picking of cross platform talks as release manager20:51
dhellmannrussellb: +120:51
mikalI think Tom wanted a meet the TC thing for the ops thing on Monday too20:51
mikalJust as a heads up20:51
russellbI think it makes sense for the TC to continue to step up as the cross-project leadership group20:51
*** thomasem_ has quit IRC20:51
sdaguerussellb: +120:51
*** rbowen has joined #openstack-meeting20:51
ttxsdague: at the very least I would facilitate that choice (as Foundation crew in charge of design summit org)20:51
markmcclainrussellb: +120:51
russellbfwiw, i'd be happy to help coorindate, as i won't be leading the nova scheduling this time20:51
jgriffithrussellb: I agree as long as I'm on TC :)20:51
* ttx can wear all sorts of hats and be there anyway20:51
sdague+1 for russellb20:51
*** megan_w is now known as megan_w|afk20:51
russellband i'll rope sdague in, and anyone else that wants to help :)20:52
sdagueI can help on that as well, as I get to punt on qa scheduling20:52
russellbsdague: ha20:52
ttxI like the idea of the TC making the final call on those20:52
ttxalso a smaller group so easier to come to consensus20:52
russellbmaybe even use openstack/governance to get approval on the final set of sessions :)20:52
* ttx slaps russellb20:53
* russellb frowns20:53
mikalI guess it depends how many sessions are proposed20:53
*** balajiiyer has joined #openstack-meeting20:53
mikalLots of sessions == harder to get a concensus20:53
jeblairttx: can we see them?20:53
*** crc32 has joined #openstack-meeting20:53
*** MaxV__ has joined #openstack-meeting20:53
ttxjeblair: sure20:53
russellbproposals are all public20:54
ttxhttp://summit.openstack.org/, click on Topic to sort by topic20:54
russellb19 cross-project submissions so far20:54
russellbhow many slots?20:54
ttx21 slots, 19 proposals20:54
sdaguettx: was it decided yet about single vs. double slots?20:54
ttxsome are probably worth double slots20:55
ttxsdague: annegentle suggested we keep 40-min ones20:55
vishyoh i have a cross-project proposal i need to make20:55
*** marcoemorais1 has quit IRC20:55
vishyregarding hierarchical multitenancy20:55
sdagueI'd really like the test matrix one to be double slot, because I think it's going to take a while20:55
*** marcoemorais has joined #openstack-meeting20:55
*** marcoemorais has quit IRC20:55
ttxrigth. i don't want us to just start on a topic and not really close it20:55
markmcremind me how the scheduling is going to work again ?20:55
ttxa design summit session is a good conversatoin opener20:56
*** marcoemorais has joined #openstack-meeting20:56
*** MaxV___ has joined #openstack-meeting20:56
russellboh i see what you mean by double ...20:56
ttxbut in these workshos you'll have a hard time getting the same people around the table again20:56
devanandasdague: ++20:56
*** marcoemorais has quit IRC20:56
ttxso we should definitely consider accepting less and granting a few double slots20:56
*** lukego has quit IRC20:56
*** marcoemorais has joined #openstack-meeting20:56
sdaguemarkmc: 3 tracks on Tuesday for cross project20:56
sdagueno other integrated project tracks that day20:56
jeblairttx: i see at least one that i think should be in infra (openstackid)20:56
markmcsdague, cool, thanks20:56
ttxjeblair: we might want to redirect some, yes20:57
*** jdob has quit IRC20:57
russellband the gantt thing should be nova for now ...20:57
*** MaxV_ has quit IRC20:57
ttxrussellb: well.. I wanted the climate guys around THAt table20:57
sdagueyeh, as always, there are folks that propose to a suboptimal track, we can move some of that around20:57
jeblairsince we're reviewing as a group (or our successors)...20:57
ttxif you need anything moved FROM cross-project workshops track, I can do that20:58
sdaguettx: but climate won't be conflicting right?20:58
jeblairwe might need to put a little effort into trying to get things redirected early20:58
ttxsdague: no they won't20:58
sdagueit's actually better for climate + nova to be in the nova track20:58
russellbttx: this sesesion is separate from the climate stuff IMO20:58
*** blamar has quit IRC20:58
ttxoh, looking20:58
*** rbowen has quit IRC20:58
sdague2 minutes20:58
ttxoh right. Gantt APi interfaces20:58
*** MaxV__ has quit IRC20:58
russellbsdague: i don't think the climate folks really took the "do it in nova" feedback, according to the ML thread that followed the TC meeting.  :-(20:58
ttxthat one shoud be Nova's for sure20:59
russellbttx: k :)20:59
sdaguerussellb: well we can nudge them again :)20:59
jeblairttx: consider this an official request to move openstackid http://summit.openstack.org/cfp/details/159 to infra :)20:59
ttxrussellb: want me to move it now ?20:59
russellbttx: yes20:59
*** erecio has quit IRC20:59
russellbthere's 2 copies of http://summit.openstack.org/cfp/details/18420:59
russellband both should be Nova IMO20:59
ttxdone and done20:59
ttxand we are past time21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
russellbbecause work has to start there21:00
openstackMeeting ended Tue Apr  1 21:00:12 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.txt21:00
*** rakhmerov has joined #openstack-meeting21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-04-01-20.03.log.html21:00
ttxthanks everyone21:00
markmcthanks ttx21:00
jeblairttx: thanks!21:00
*** caleb_ has quit IRC21:00
ttxdhellmann, dolphm, notmyname, jd__, markwash, jgriffith, russellb, stevebaker, david-lyle, markmcclain, hub_cap: around ?21:00
ttxdamn summer time21:00
ttx#startmeeting project21:00
*** blamar has joined #openstack-meeting21:00
openstackMeeting started Tue Apr  1 21:00:59 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: project)"21:01
openstackThe meeting name has been set to 'project'21:01
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:01
ttx#topic Missing RC1s21:01
*** openstack changes topic to "Missing RC1s (Meeting topic: project)"21:01
*** david-lyle_afk is now known as david-lyle21:01
ttxAt this point we are only missing RC1s for Trove and Swift21:01
*** aysyd has quit IRC21:01
notmynamelast few things being resolved in swift21:01
ttxTrove's ETA is tomorrow, Swift ETA is Thursday21:01
ttxin all cases we'd crreate MP branches this week to get depfreeze unfrozen on master21:02
*** patelna has joined #openstack-meeting21:02
*** rfolco has quit IRC21:02
ttx#topic Potential RC2 windows21:02
*** openstack changes topic to "Potential RC2 windows (Meeting topic: project)"21:02
ttxDuring the 1:1s we looked at icehouse-rc-potential bugs21:02
*** rockyg has quit IRC21:03
ttxWe'll let the RC1 get some more testing mileage21:03
ttxand start opening ad-hoc RC2 windows as needed starting Thursday21:03
ttxwe have a few translations issues that need to be fixed21:03
*** doug_shelley66 has quit IRC21:04
*** cyeoh has quit IRC21:04
*** Gordonz has quit IRC21:04
ttxTry to limit use of the icehouse-rc-potential tag to release-critical issues that may make a RC respin warranted21:04
*** blamar has quit IRC21:04
*** caleb_ has joined #openstack-meeting21:05
ttxwe can always include MORE fixes once the window is opened, just lookign at the bugs that got fixed in master in the mean time21:05
*** thang_ has quit IRC21:05
*** henrynash has joined #openstack-meeting21:05
*** rakhmerov has quit IRC21:05
stevebakernow you tell me ;)21:05
ttxI'll keep an eye on the  icehouse-rc-potential lists and we'll be in touch to get those RC windows opened21:05
markmcthings punted til later are moved to icehouse-backport-potential, right?21:05
*** tchaypo has joined #openstack-meeting21:05
ttxmarkmc: yes, this one can be used more as a "makes sense to backport this one" meaning21:06
*** cyeoh has joined #openstack-meeting21:06
*** blamar has joined #openstack-meeting21:06
ttxwhereas icehouse-rc-potential is more "hmm... we really can't release with that in"21:06
ttxother questions on that ?21:06
*** tchaypo has left #openstack-meeting21:06
devanandattx: is the process just to add the icehouse-rc-potential tag on a bug?21:07
ttxdevananda: hmm.. yes ?21:07
*** tchaypo has joined #openstack-meeting21:07
ttxsounds like a tricky question21:07
ttxhope I answered right21:07
*** vuil has quit IRC21:07
ttx#topic Depfreeze exceptions21:07
*** openstack changes topic to "Depfreeze exceptions (Meeting topic: project)"21:07
*** IlyaE has joined #openstack-meeting21:07
ttx#link https://review.openstack.org/#/c/8403021:08
ttxThis one is about skipping pbr 0.7 because it's broken on Windows21:08
*** aburaschi has left #openstack-meeting21:08
ttxThe problem is we are under depfreeze, we had 0.7 around before depfreeze and this affects everyone (unlike, say, happybase)21:08
ttxSo it seems to be precisely the type of bumps depfreeze was meant to prevent21:08
*** marcoemorais has quit IRC21:08
ttxSince the current spec (>=0.6) doesn't prevent the use of 0.8 on Windows setups, I'm not exactly sure why this would be *needed*21:08
*** marcoemorais has joined #openstack-meeting21:08
ttxAm I missing something ?21:08
dhellmannno, I had a similar reaction21:09
*** lukego has joined #openstack-meeting21:09
markmcI guess someone could have the requirements satisfied with 0.7 and it would break windows21:09
markmcbut, obscure to say the least21:10
markmcagree it's not worth ruling out 0.721:10
markmcis it just because it's windows, though?21:10
ttxif the thing was capped to <=0.7 I would agree we should uncap it21:10
*** lblanchard has quit IRC21:10
ttxbut >=0.6 shoulds work for everyone21:10
dhellmannmarkmc: yes, it was just windows, though I don't remember the details21:10
ttxjust use 0.8 if you like it better21:11
russellbif 0.7 was broken on linux, i bet we'd change it to exclude 0.7 ...21:11
markmcI mean, if 0.7 was broken on fedora but working on ubuntu, would we approve this?21:11
markmcmaybe not worth wasting time on the hypothetical21:11
russellbmaybe that's fine, i don't know21:11
markmcif we're happy saying windows is second class citizen21:11
russellbi am :)21:12
ttxmarkmc: I don't think we'd approve something that would shift the work from Fedora to Ubuntu21:12
sdaguewell, I think the point of requirements is here is a valid range of choices21:12
ttxhere I'm not even sure we make it difficult for windows21:12
russellbright, the question is, would we consider 0.7 valid if it broke all linux21:12
russellbflip the situation around21:12
ttxrussellb: it wouldn't pass the gate, surely21:12
russellbpretend it did, somehow :)21:12
russellbjust trying to flip the situation21:13
ttxwell, it's a bit of the root of the issue21:13
sdaguerussellb: if it did, I honestly don't think we'd black list it21:13
sdagueI am sure there are plenty of non working versions in the requirements ranges21:13
sdaguewe don't black list them all21:13
russellbOK, guess all I think markmc was starting to say was "are we making this decision based on "well, it's just windows" ?"21:13
sdaguelike sqla 0.9.0 doesn't actually work21:13
*** bdpayne has quit IRC21:13
*** blamar has quit IRC21:13
markmcwe do sometimes blacklist, though21:13
sdaguemarkmc: we do sometimes21:13
ttxrussellb: no. We are amking this decision as "well, it's past depfreeze"21:13
sdaguemostly if it's the only way through the gate21:14
*** lukego has quit IRC21:14
*** blamar has joined #openstack-meeting21:14
russellbOK, then it's all good21:14
markmcmeh - maybe let's have this debate when we have something that has real practical problems :)21:14
jeblairttx: yeah, i keep re-reading your original problem statement, and i agree it doesn't seem like there is a problem; the requirements we specify include working versions for all platforms21:14
ttxI just wanted to make sure I wasn't overlooking something21:14
russellbi think it's fine21:14
*** dprince has quit IRC21:14
*** pdmars has quit IRC21:14
markmcsorry for the rabbit hole21:14
russellbthey're fun sometimes21:14
ttxI'm pretty sure that's not the onlt dep you need to bump IN YOUR DISTRO to make it work seamlessly with your system21:15
ttxas long as it's in the range we set...21:15
ttxwe don't prevent them from using 0.821:15
dhellmannis this worth a release note?21:15
*** sridhar has quit IRC21:15
ttxdhellmann: maybe21:15
russellbhow committal21:16
ttx#action ttx to add windows pbr0.8 adherence to release notes21:16
dhellmannhow do people install openstack stuff on windows? pip?21:16
ttxrussellb: better ?21:16
russellbha, sure21:16
russellbdhellmann: i have no idea.21:16
* dhellmann hopes not pip21:16
ttxalexpilotti: you don't happen to be around, do you ?21:16
russellbhe's active in -nova right now21:16
* russellb pings in there21:17
ttxoh, cool21:17
jeblairalso, i don't think we have an official support policy for windows21:17
alexpilottirussellb: hi21:17
ttxalexpilotti: we were looking at your depfreeze exception at https://review.openstack.org/#/c/8403021:17
*** bdpayne has joined #openstack-meeting21:18
ttxlooks like the current range >=0.6 would be compatible with windows using pbr0.8 ?21:18
*** blamar has quit IRC21:18
*** jodom has joined #openstack-meeting21:18
alexpilottittx: only 0.7 is flawed21:18
*** blamar has joined #openstack-meeting21:18
ttxso we could avoid breaking distros that only have 0.7 by not doing anything21:18
ttxalexpilotti: then what ? Just use 0.821:18
russellbalexpilotti: key point being the stated requirement doesn't prevent the use of 0.821:19
russellbso trying to decide if a change is needed or not (and we think not)21:19
alexpilottittx: yeah of course, that's why teh patch is >= 0.6,!=0.7 :-)21:19
ttxthe problem is... we froze dependencies a week ago so that distros can enter their own freeze periods21:19
ttxforcing them to bum to 0.8 just for a bug they don't encounter... is weird21:19
ttxif this was out of depfreeze period i would accept it right away21:20
alexpilottirussellb ttx: we distribute anyway the installer with 0.8, it's more for users that incidentally have already 0.721:20
*** jprovazn has quit IRC21:20
alexpilottiand might wonder why nothing works anymore, as the error is not trivial to identify21:20
*** blamar_ has joined #openstack-meeting21:20
ttxalexpilotti: we were thinking of documenting the prb0.8 adherence in the release notes21:20
russellbsounds like if you already have this taken care of with the installer most people use, anyone affected is an incredibly small number21:21
alexpilottittx: fair enough for me!21:21
dhellmannrussellb: +121:21
*** mspreitz has quit IRC21:21
russellbalexpilotti: thanks for joining21:21
*** jrodom has quit IRC21:21
alexpilottithank you guys21:21
ttxalexpilotti: cool. And we'll push the bump to 0.8 as soon as we unfreeze, which should be Friday21:21
alexpilottittx perfect21:21
ttx#topic Seeking Oslo liaisons21:21
*** openstack changes topic to "Seeking Oslo liaisons (Meeting topic: project)"21:21
ttx#link https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons21:22
ttxdhellmann: floor is yours21:22
dhellmannfor juno we are going to formalize the plan jogo came up with for syncing to nova in icehouse, and ask each project to provide a point of contact and helper21:22
*** jodom has quit IRC21:22
dhellmannwe would like to have them in place before the summit, since they may want to attend some oslo sessions21:22
*** vijendar has quit IRC21:23
dhellmannso please ask your teams to volunteer -- at least one person per project21:23
jogodhellmann: ++, I'll volunteer for nova21:23
*** blamar has quit IRC21:23
* russellb done21:23
russellbthanks jogo :-D21:23
dhellmannas I said in my ptl candidacy note, I hope this helps with some of the dependency issues we encountered late in the cycle, for which I didn't have a lot of visibility21:24
dhellmannthanks jogo! please add your details to that wiki page :-)21:24
dhellmannthat's all I have, unless anyone has questions?21:24
ttx#info please volunteer one person per project for https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons21:24
russellbdhellmann: nice work on the plan for juno :)21:24
dhellmannrussellb: thanks :-)21:25
jgriffithdhellmann: I'll wait til I see you in Atl for my questions21:25
ttx#topic Tracking Oslo bugs as they relate to other projects21:25
*** openstack changes topic to "Tracking Oslo bugs as they relate to other projects (Meeting topic: project)"21:25
ttxdhellmann: you again!21:25
dhellmannme again21:25
jogodhellmann: done21:25
*** blamar has joined #openstack-meeting21:25
*** blamar_ has quit IRC21:25
dhellmannso, we had some cases where bugs in other projects were reported against those projects when the changes needed to be made in oslo21:25
*** nwidell has joined #openstack-meeting21:25
dhellmannand then when the bug was moved to oslo, the other project was removed21:25
dhellmannthat made it hard for us to know who had the issue, or how important it was to fix21:26
markmcthese are oslo-incubator bugs? or library bugs?21:26
dhellmannI don't have an answer for this one, so I'm asking for suggestions -- we can do that out of the meeting, but I wanted people to think about it21:26
dhellmannmarkmc: both21:26
*** Dseven has joined #openstack-meeting21:26
jogohopefully the liasons can help with that21:26
russellbseems to make sense for incubator bugs to still be applied to the original project too21:26
markmcIMHO, the answer would be different for both ... no?21:26
markmcwhat russellb is saying :)21:27
dhellmannjogo: yes, I hope so21:27
russellbfor libraries, move the bug, but perhaps note that it was discovered via nova or whatever21:27
dhellmannrussellb: +1, but I wasn't sure if that would mess up tracking21:27
markmcor just mark as Invalid in Nova rather than remove it21:27
russellbmarkmc: even better, +121:27
ttxdhellmann: nothing can mess up tracking. nothing21:27
dhellmannyeah, I like marking invalid, because then we can still have the priority set21:27
ttxalthough... 10 tasks on a bug will make it uneditable.21:28
ttxapart from that, nothing21:28
russellbthough for these cases, we're talking about 2 instead of 121:28
dhellmannttx: well, if we have 2 projects marking something as critical, I'm not sure we need *everyone* listed21:28
ttxrussellb: right. nothing then21:28
russellband project "set launchpad on fire" is in progress :)21:28
ttxalmost there !21:28
markmcfor the oslo-incubator cases, though ...21:28
markmcwe can get over 10 in those21:28
russellbmarkmc: true21:28
russellbbut that's reality21:28
russellbit's important to track the flow of the fix21:29
russellbalways have the launchpad email interface21:29
*** adalbas has quit IRC21:29
russellbor complain to ttx21:29
ttxjeblair: we should have made a Storboard 1.0 announcement for today21:29
bnemecThe solution there is less copying, more graduating.21:29
dhellmannI hope as we move code out of the incubator, that will lower the number of projects syncing21:29
russellbttx: skip to 2.021:29
ttxjeblair: with proxyredirect to LP21:29
dhellmanna lot of them use the low-level libs, but not higher level ones21:29
jeblairttx: hehe :)21:29
dhellmannbnemec: +121:29
*** catohornet has quit IRC21:30
dhellmannok, so if we agree to use "invalid" and set a priority, I think that will help us with planning in oslo21:30
ttxdhellmann: sounds good21:30
russellbfor the library cases?  sure21:30
dhellmannand that should help us figure out what issues other projects are having that we need to give a high priority21:30
dhellmannrussellb: right, and for the incubator it needs to wait to be closed until the sync is done21:30
*** doug_shelley66 has joined #openstack-meeting21:31
russellbmight want to document this on the bug triage wiki page21:31
dhellmann#action dhellmann write up guidelines for tracking bugs against oslo libs and incubator21:31
*** henrynash has quit IRC21:31
ttxdhellmann: done?21:31
dhellmannrussellb: thanks21:31
dhellmannttx: yes21:31
ttx#topic Red Flag District / Blocked blueprints21:31
*** openstack changes topic to "Red Flag District / Blocked blueprints (Meeting topic: project)"21:31
markmcdhellmann turning into a wiki page generating machine21:31
markmcdhellmann, nicely done21:31
dhellmannmarkmc: write down all the things21:31
ttxmorganfainberg: you had an issue to raise iirc21:31
dhellmannI think we just resolved that21:31
morganfainbergttx, o/21:31
ttxbug 127900021:32
uvirtbotLaunchpad bug 1279000 in oslo "db migrate script to set charset=utf8 for all tables" [High,Fix committed] https://launchpad.net/bugs/127900021:32
dhellmannwe're going to change oslo.db to ignore the table that lists the migrations21:32
morganfainbergso it appears that in some cases (e.g. unless the db is created with the correct charset or my.cnf is changed) causes issues with migrations to fail21:32
*** markmc has quit IRC21:32
morganfainbergttx, that is the original bug, but the sanity check needs to ignore the migrate_version table21:32
uvirtbotLaunchpad bug 1279000 in oslo "db migrate script to set charset=utf8 for all tables" [High,Fix committed]21:33
ttxcomment 12 talks about the issue spreading to keystone21:33
morganfainbergwe can fix this easily and ignore that table, but there is the case that anyone using the openstack common migration module will need to be updated for RC.21:33
morganfainbergor alternatively we can document saying that the DBs must be created with the utf8 charset21:33
morganfainbergthe latter is sub-wonderful21:33
morganfainbergbut otherwise any/all projects could be affected by this issue if they're using that oslo module21:34
*** dkranz has quit IRC21:34
ttxany idea which projects are affected ? All of them ?21:34
ttxGlance apparently dodged the bullet on that bug21:34
*** balajiiyer has left #openstack-meeting21:34
ttxmarkwash: ^21:34
morganfainbergttx, unsure, i just duplicated this for keystone about 20 minutes ago21:34
dhellmannttx: glance is using the feature we added to turn off that check21:35
ttxdhellmann: so we need to spread that same fix to all other projects ?21:35
dhellmannttx: no, we need a new fix to ignore this one table and to spread that21:35
morganfainbergdhellmann, ++21:35
ttxoh, ok21:35
dhellmannI'll work on a patch tomorrow, unless morganfainberg or bnemec beat me to it21:36
morganfainbergdhellmann, i'll see what i can do today.21:36
ttxLooks like we could use a NEW bug to track work on that21:36
dhellmannmorganfainberg: ok, that lets bnemec and me approve so that's good21:36
ttxbecause the current one has olso and glance all fixed21:36
dhellmannttx: good point21:36
morganfainbergttx, i'll file the bug in the next couple minutes and we'll need to figure out which projects are using this.21:36
bnemecYeah, and this is kind of a different issue.21:37
devanandadhellmann: is this specific to sqlalchemy-migrate?21:37
dhellmanndevananda: I'm not certain21:37
ttxmorganfainberg: yes, make it icehouse-rc-potential and add atsks for all affected projects21:37
morganfainbergdevananda, if alembic does the same thing, there is code that does the same check21:37
ttxthe other OMG bug would be bug 129934921:37
uvirtbotLaunchpad bug 1299349 in neutron "upstream-translation-update Jenkins job failing" [High,In progress] https://launchpad.net/bugs/129934921:37
morganfainbergdevananda, just alembic specific21:37
markwashit seems like glance needs this fix in its oslo db as well, since its not normal to ignore the utf8 charset check. . no?21:37
ttxalso affects lots of projects21:37
dhellmannmorganfainberg: let's go ahead and add alembic's migration tracking table to your fix21:38
morganfainbergdevananda, i'll verify if alembic has this issue or not and address it in the same fix.21:38
bnemecmarkwash: You'll need it when you turn on utf8 checking.21:38
devanandamorganfainberg: thanks21:38
morganfainbergdevananda, well i'll verify and fix the same way and tag you guys in if needed.21:38
bnemecFor Icehouse Glance should be okay though.21:38
markwashbnemec: it is on by default IIUC21:38
ttxmorganfainberg: ping me with bug number when you have it21:38
morganfainbergttx, sounds good.21:38
ttxmorganfainberg: and thanks for helping coordinate that one21:38
dhellmannmarkwash: I thought you guys were turning it off in your manager?21:38
markwashdhellmann: we have an option to turn off the utf8 charset check21:39
devanandamorganfainberg: quick local check shows ironic's tables as utf8, but alembic_version is latin1 :(21:39
markwashthe option defaults to False which means we still run the check21:39
dhellmannmarkwash: oh, ok, I thought you were just turning it off all the time21:39
* dhellmann is going to run out of battery soon21:40
ttxOK, let's continue this off-meeting. Any other OOPS! bug ?21:40
ttxAny other inter-project blocked work that this meeting could help unblock ?21:40
morganfainbergdevananda, thanks for the check will make sure you're tagged and alembic check is fixed the same way21:40
dhellmannmorganfainberg: thanks21:40
devanandattx: you mentioned i18n stuff earlier21:41
*** thuc has quit IRC21:41
devanandattx: i think ironic was afected by the same issues. I posted a few hours ago with some notes on what we did to resolve it21:41
devanandain case that's helpful to other projects21:41
ttxdevananda: cool. link to post?21:41
*** thuc has joined #openstack-meeting21:41
sdaguethere is an fyi to the group, the clean log enforcement has now been added to the gate (which was talked about a few weeks back).21:42
devananda#link http://lists.openstack.org/pipermail/openstack-dev/2014-April/031572.html21:42
sdaguethe allowed dirty list is pretty long at this point - https://github.com/openstack/tempest/blob/master/tools/check_logs.py#L33-L57  but it's a start21:42
ttx#info clean log enforcement has now been added to the gate21:42
ttx#topic Incubated projects21:42
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:42
ttxironic has its RC1 out now21:43
ttxmarconi is almost there21:43
ttxSergeyLukjanov: how far is sahara ?21:43
SergeyLukjanovsahara rc1 should be on Thu as planned21:43
SergeyLukjanovhttps://launchpad.net/sahara/+milestone/icehouse-rc1 looks fine21:43
ttxSergeyLukjanov: so, when you're ready...21:44
*** vuil has joined #openstack-meeting21:44
ttxyou need to push a version bump to open juno21:44
ttxSergeyLukjanov: setup.cfg must be bumped to 2014.221:44
SergeyLukjanovttx, I already have one in WIP21:44
ttxexample: https://review.openstack.org/#/c/83198/21:44
ttxOh, cool21:44
ttxSo when you're ready, approve that one21:45
ttxand ping me when it merges21:45
ttxthen if you want to do a RC2 you can ping me or create the milestone yourselves21:45
SergeyLukjanovttx, any you'll tag rc1 / create m-p after it?21:45
ttxSergeyLukjanov: yes21:45
SergeyLukjanovttx, ok, thx21:46
ttxother questions ?21:46
SergeyLukjanovttx, I hope to be ready for it on Thu afternoon (in our tz)21:46
*** thuc has quit IRC21:46
ttxI like our tz21:46
ttx#topic Open discussion21:46
*** openstack changes topic to "Open discussion (Meeting topic: project)"21:46
ttxAnything, anyone ?21:46
ttxNote that the deadline for submitting "Other projects" and "Cross-project workshops" sessions suggestions was advanced to April 1021:47
ttx#info deadline for submitting "Other projects" and "Cross-project workshops" sessions suggestions was advanced to April 1021:47
ttxso that we can give early answers21:47
ttxok, if nobody has anything else to mention...21:48
morganfainbergttx, https://bugs.launchpad.net/ironic/+bug/130103621:48
uvirtbotLaunchpad bug 1301036 in oslo "openstack.common.db.sqlalchemy.migration utf8 table check issue on initial migration" [Undecided,New]21:48
*** topol has quit IRC21:49
*** stevemar has quit IRC21:49
ttxmorganfainberg: thx!21:49
*** salv-orlando_ has joined #openstack-meeting21:49
*** enikanorov has joined #openstack-meeting21:49
*** ttrifonov is now known as ttrifonov_zZzz21:49
*** kevinconway_ has joined #openstack-meeting21:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:51
*** MrJoshua_ has joined #openstack-meeting21:51
openstackMeeting ended Tue Apr  1 21:51:41 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2014/project.2014-04-01-21.00.html21:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2014/project.2014-04-01-21.00.txt21:51
* SergeyLukjanov zzzz21:51
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2014/project.2014-04-01-21.00.log.html21:51
russellbttx: thanks!21:51
SergeyLukjanovttx, thank you21:51
ttxthanks all21:51
*** fawadkhaliq has quit IRC21:52
*** fawadkhaliq has joined #openstack-meeting21:52
*** sdake_ has joined #openstack-meeting21:53
*** sdake_ has quit IRC21:53
*** sdake_ has joined #openstack-meeting21:53
*** mtaylor has joined #openstack-meeting21:53
*** jpeeler1 has joined #openstack-meeting21:53
*** sdake_ is now known as sdake_121:53
*** ssurana has left #openstack-meeting21:54
*** ivasev has quit IRC21:54
*** cgoncalv1s has joined #openstack-meeting21:54
*** egallen_ has joined #openstack-meeting21:54
*** DinaBelova2 has joined #openstack-meeting21:54
*** MrJoshua has quit IRC21:54
*** egallen has quit IRC21:54
*** jpeeler has quit IRC21:54
*** ruhe has quit IRC21:54
*** kevinconway has quit IRC21:54
*** salv-orlando has quit IRC21:54
*** jtomasek has quit IRC21:54
*** DinaBelova has quit IRC21:54
*** markvoelker has quit IRC21:54
*** mordred has quit IRC21:54
*** sdake has quit IRC21:54
*** Alexandra_ has quit IRC21:54
*** coasterz has quit IRC21:54
*** enikanorov_ has quit IRC21:54
*** cgoncalves has quit IRC21:54
*** kevinconway_ has quit IRC21:54
*** kevinconway_ has joined #openstack-meeting21:54
*** salv-orlando_ is now known as salv-orlando21:54
*** MrJoshua_ is now known as MrJoshua21:54
*** kevinconway_ is now known as kevinconway21:54
*** egallen_ is now known as egallen21:54
*** DinaBelova2 is now known as DinaBelova21:54
*** caleb_ has quit IRC21:54
*** coasterz has joined #openstack-meeting21:55
*** jtomasek has joined #openstack-meeting21:55
*** ruhe has joined #openstack-meeting21:55
*** Alexandra_ has joined #openstack-meeting21:55
*** rakhmerov has joined #openstack-meeting22:01
*** rkukura has joined #openstack-meeting22:01
*** zehicle has joined #openstack-meeting22:02
*** weshay has quit IRC22:04
*** rakhmerov has quit IRC22:05
*** MaxV___ has quit IRC22:05
*** MaxV_ has joined #openstack-meeting22:05
*** zehicle_at_dell has quit IRC22:05
*** dims_ has joined #openstack-meeting22:06
*** nwidell has quit IRC22:07
*** armax has quit IRC22:07
*** denis_makogon has quit IRC22:08
*** dcramer_ has quit IRC22:08
*** shwetaap has quit IRC22:08
*** stannie has left #openstack-meeting22:10
*** banix has quit IRC22:13
*** egallen has quit IRC22:13
*** alexpilotti has quit IRC22:14
*** sballe has quit IRC22:15
*** dims_ has quit IRC22:18
*** rbowen has joined #openstack-meeting22:19
*** rbowen has joined #openstack-meeting22:19
*** jgrimm has quit IRC22:23
*** jaypipes has joined #openstack-meeting22:24
*** thuc has joined #openstack-meeting22:25
*** thuc has quit IRC22:25
*** thuc has joined #openstack-meeting22:26
*** shwetaap has joined #openstack-meeting22:28
*** kevinconway has quit IRC22:28
*** radsy has joined #openstack-meeting22:29
*** changbl has quit IRC22:32
*** mspreitz has joined #openstack-meeting22:33
*** esker has quit IRC22:34
*** pablosan is now known as zz_pablosan22:35
*** eharney has quit IRC22:35
*** TravT has quit IRC22:36
*** dims_ has joined #openstack-meeting22:36
*** zz_pablosan is now known as pablosan22:38
*** prad has quit IRC22:38
*** thuc has quit IRC22:42
*** thuc has joined #openstack-meeting22:42
*** thedodd has quit IRC22:43
*** rbowen has quit IRC22:44
*** otherwiseguy has quit IRC22:44
*** baoli has quit IRC22:46
*** thuc has quit IRC22:46
*** zzelle has quit IRC22:48
*** shwetaap has quit IRC22:51
*** markmcclain has quit IRC22:52
*** thuc has joined #openstack-meeting22:57
*** thuc has quit IRC22:58
*** armax has joined #openstack-meeting22:59
*** thuc has joined #openstack-meeting22:59
*** armax has quit IRC22:59
*** saschpe has quit IRC23:00
*** rakhmerov has joined #openstack-meeting23:01
*** Leonr has quit IRC23:04
*** rakhmerov has quit IRC23:06
*** yamahata has quit IRC23:08
*** crc32 has quit IRC23:08
*** wenlock has quit IRC23:09
*** MaxV_ has quit IRC23:09
*** saschpe has joined #openstack-meeting23:10
*** gokrokve has quit IRC23:12
*** aarongr_ has joined #openstack-meeting23:14
*** mspreitz has quit IRC23:14
*** david-lyle has quit IRC23:20
*** _afazekas has quit IRC23:21
*** derekh has joined #openstack-meeting23:23
*** lukego has joined #openstack-meeting23:25
*** mspreitz has joined #openstack-meeting23:28
*** caleb_ has joined #openstack-meeting23:29
*** thuc has quit IRC23:30
*** mrodden has quit IRC23:30
*** caleb_ has quit IRC23:31
*** mwagner_afk has joined #openstack-meeting23:32
*** pablosan has quit IRC23:36
*** otherwiseguy has joined #openstack-meeting23:36
*** lukego has quit IRC23:37
*** lcheng has quit IRC23:37
*** jjmb has joined #openstack-meeting23:42
*** jjmb has quit IRC23:43
*** jjmb has joined #openstack-meeting23:43
*** thuc has joined #openstack-meeting23:45
*** brucer has joined #openstack-meeting23:49
*** mspreitz has quit IRC23:49
*** mrodden has joined #openstack-meeting23:56
*** flaper87 is now known as flaper87|afk23:57
*** mspreitz has joined #openstack-meeting23:59
*** aarongr_ has quit IRC23:59

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