Thursday, 2013-08-15

*** cyeoh has quit IRC00:04
*** cyeoh has joined #openstack-meeting00:05
*** hemna is now known as hemnafk00:06
*** lbragstad has joined #openstack-meeting00:09
*** rongze_ has joined #openstack-meeting00:10
*** flaper87 is now known as flaper87|afk00:10
*** krtaylor has quit IRC00:12
*** krtaylor has joined #openstack-meeting00:12
*** cbaesema_ has joined #openstack-meeting00:12
*** rongze has quit IRC00:13
*** cbaesema has quit IRC00:13
*** cbaesema_ is now known as cbaesema00:13
*** vijendar has joined #openstack-meeting00:14
*** vaml has quit IRC00:15
*** markpeek has joined #openstack-meeting00:17
*** MarkAtwood has quit IRC00:21
*** yosshy has joined #openstack-meeting00:21
*** adjohn has joined #openstack-meeting00:21
*** openstack has joined #openstack-meeting00:41
*** ChanServ sets mode: +o openstack00:41
*** spenceratx has joined #openstack-meeting00:42
*** vijendar has quit IRC00:42
*** mberwanger has joined #openstack-meeting00:45
*** Daisy has joined #openstack-meeting00:52
*** bdpayne has quit IRC00:53
*** marun has quit IRC00:55
*** adjohn has quit IRC00:57
*** galstrom_zzz is now known as galstrom00:58
DaisyGood moring and Good evening00:58
Daisyanybody there?00:58
*** gabrielcw has joined #openstack-meeting00:59
DaisyGood evening, gabrielcw00:59
*** rwsu is now known as rwsu-away00:59
gabrielcwHello Daisy!01:00
gabrielcwHow are you?01:00
*** mberwanger has quit IRC01:00
DaisyI'm good. Thank you.01:00
DaisyI think it's late for you, right? It's 22pm now?01:00
gabrielcwright! not so late01:00
gabrielcwI go to bed at 12 normally :)01:00
Daisyoh. That's not an early time. :)01:01
*** Mandell has quit IRC01:01
DaisyLet's see if we can get anybody else.01:01
gabrielcwyeah, I agree01:01
gabrielcwso many things to do!01:01
*** galstrom is now known as galstrom_zzz01:01
Daisyagree.01:01
DaisyI don't see Japanese team and Korean team yet.01:02
Daisyanyway, let's start.01:02
gabrielcwok01:02
Daisy#startmeeting OpenStack I18n Meeting01:02
openstackMeeting started Thu Aug 15 01:02:36 2013 UTC and is due to finish in 60 minutes.  The chair is Daisy. Information about MeetBot at http://wiki.debian.org/MeetBot.01:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:02
*** openstack changes topic to " (Meeting topic: OpenStack I18n Meeting)"01:02
openstackThe meeting name has been set to 'openstack_i18n_meeting'01:02
*** spenceratx has left #openstack-meeting01:02
Daisy#topic Action items from the last meeting01:03
*** openstack changes topic to "Action items from the last meeting (Meeting topic: OpenStack I18n Meeting)"01:03
fifieldthi01:03
gabrielcwhello01:03
DaisyGood morning, fifieldt !01:03
Daisywe just starts.01:03
DaisyDaisy to track the font problem with David.01:03
DaisyIt's done.01:03
DaisyKorean team has sent the font file to David, David will cut a release01:04
DaisySo the Korean font issue can be resolved. I don't know if the same issue will happen to other language.01:04
DaisyBut David agreed to change his plugin to enable people to set the font path.01:04
DaisyFdot to check whether openstack-manuals can use the glossary defined in openstack hub.01:04
DaisyFdot is not there.01:05
DaisyDaisy to check if we can define into the configuration if we can force the hub glossary.01:05
DaisyIt's done. But I'm going to cover it in the following topic.01:05
Daisyeach team collect the wish list of Transifex and Daisy to combine them.01:05
DaisyI only got feedback from Giang Duong, the Vietnamese team. I will also cover it in the following topic.01:05
DaisyDaisy to track the source lang in Horizon01:06
DaisySorry I don't get more information. Per my understanding, there is no progress with this issue. I don't have the right to change Horizon project. I think Gabriel Hurley is the key person and I will continue to reach him.01:06
Daisyok. that's all of the action items last meeting.01:06
Daisywe will move to next.01:07
Daisy#topic Progress with Japanese doc site01:07
gabrielcwnice01:07
*** openstack changes topic to "Progress with Japanese doc site (Meeting topic: OpenStack I18n Meeting)"01:07
Daisyfifieldt: I see there is progress with https://review.openstack.org/#/c/3984601:07
*** eharney has joined #openstack-meeting01:07
*** eharney has quit IRC01:07
*** eharney has joined #openstack-meeting01:07
fifieldtyes01:07
Daisywhat's left in your mind?01:07
fifieldtit now passes tests01:07
fifieldtit needs to be merged01:07
fifieldtI'm also not sure whether we merged the docs.openstack.org/ja page01:08
fifieldtdid that happen yet?01:08
*** blamar has joined #openstack-meeting01:08
DaisyI didn't see the page yet.01:08
fifieldtI know the basic design exists01:08
DaisyI will check with Akihiro MOTOKI offline.01:08
fifieldtmaybe we just need to turn it into a patch01:08
fifieldtok01:08
DaisyRight.01:08
Daisyfifieldt: do you think it is possible to enable a parameter in https://review.openstack.org/#/c/39846, so that when we want to add Chinese site, we can simply change the parameter?01:09
*** markmcclain has quit IRC01:09
fifieldtyes, it can likely be modified for this01:10
fifieldtis it OK to iterate?01:10
fifieldtI'm not 100% sure this patch will work01:10
fifieldtso plan to keep it simple first01:10
fifieldtthen make it better later01:10
Daisyok.01:10
Daisygot your point.01:10
Daisy#topic Glossary defined in Transifex01:10
*** openstack changes topic to "Glossary defined in Transifex (Meeting topic: OpenStack I18n Meeting)"01:10
DaisyI checked Transifex.01:11
DaisyA user can create multiple glossaries and attach them to the projects he owns, as long as the project and the glossary share the same source language. The glossaries can be bootstrapped by uploading a CSV file.01:11
DaisyIt looks like it's able to define a glossary and associate all the openstack projects with it. But this action needs an account with all the full access to the hub project Openstack and its related projects. I don't know if there is such account.01:11
fifieldtdon't you have access?01:11
DaisyI did test within my account. I'm able to create a glossary and associate it with all the project (with same source language) I own.01:12
*** macjack has joined #openstack-meeting01:12
DaisyAlthough I'm the maintainer of OpenStack, I'm not able to manage the glossary defined within OpenStack.01:12
fifieldtmmm, odd01:12
fifieldtcan we create a support request with transifex?01:13
DaisyI'm not able to manage other projects, like Nova, Horizon, and etc. Because I'm not the owner.01:13
fifieldtoh, right01:13
fifieldtso there is only ever one owner?01:13
DaisyIt looks like owner is the one who create such project.01:13
fifieldtargh, damn01:13
lifelessthe maintainer can be a team01:14
lifelessoh, sorry, transifex, I dunno.01:14
Daisyright. But it looks like the team don't have the right to manage glossary.01:14
lifelessI was thinking LP.01:14
DaisyHi, lifeless01:14
fifieldtnp01:14
*** lbragstad_ has joined #openstack-meeting01:15
Daisyso I will continue to follow up with this issue. If we fail to do, we can ask help from Transifex. Let's see.01:16
fifieldtok01:16
gabrielcwHello?01:16
DaisyBTW, I find there are several project setting the source language as en_US.01:16
fifieldtoh no01:17
fifieldthi gabrielcw!01:17
DaisyThe source language of Cinder, Glance, Horizon,and Nova are en_US, and others are en.01:17
*** novas0x2a|laptop has quit IRC01:17
gabrielcwoh, some delay here...nevermind01:17
DaisyNow we only meet with problem in Horizon.01:17
DaisyI don't know if this issue will cause problems in other projects.01:17
gabrielcwsorry, i`m not aware of this problem, can you explain shortly?01:18
DaisyAnd, if the source language are different, it's not able to share a same glossary among them, because glossary can only share among projects with same source langauge.01:18
Daisyso...anyway, we need to change the issue.01:18
DaisyI hope I can have the higher right than I have now.01:19
yosshySorry, I'm late. Hello all.01:19
DaisyIt looks like projects of openstack translations are made by different people.01:19
DaisyHi, yosshy01:20
gabrielcwhi01:20
Daisycreated by different people.01:20
Daisyany comments?01:20
Daisy#action: Daisy to continue to track the glossary and source language issue.01:21
Daisylet's move on.01:21
Daisy#topic Transifex requirements/bugs collection01:21
*** openstack changes topic to "Transifex requirements/bugs collection (Meeting topic: OpenStack I18n Meeting)"01:21
DaisyStefano Maffulli suggested us to collect our requirements to translation tool, not only specific to Transifex.01:22
DaisyIf we are not so satisified with Transifex, we can change to other tools.01:22
*** brucer_ has joined #openstack-meeting01:22
*** brucer has quit IRC01:22
DaisyI looked in my old mails and found this:01:22
Daisyhttps://docs.google.com/spreadsheet/ccc?key=0Aqevw3Q-ErDUdFgzT3VNVXQxd095bFgzODRmajJDeVE#gid=001:22
*** herndon has quit IRC01:23
*** adjohn has joined #openstack-meeting01:23
DaisyIt was the original discussion when the community was going to select a translation management tools other than Launchpad.01:23
gabrielcwBesides some minor issues, I like to use Transifex, even the web client01:24
DaisyI don't know your opinion to Transifex. Do you like it? Do you use it? Do you think it can satisy you?01:24
Daisysatisfy you?01:24
Daisyhow about you, yosshy ?01:24
yosshyYes.01:24
*** alexb_ has joined #openstack-meeting01:25
fifieldtthe web client is nice (especially when it has suggestions from the translation memory) but it doesn't show context of the string01:25
gabrielcwthey are very helpful when bugs are found01:25
gabrielcwyeah, true01:25
yosshyWe found that Transfex is not good for review.01:25
gabrielcwI miss the context too01:25
DaisyWhat do you mean, yosshy ?01:25
DaisyYeah, maybe when reviewer does the review, they want to review a whole document, not paragraph.01:26
*** brucer_ has quit IRC01:26
DaisyThat's to documents. not to messages.01:27
*** brucer has joined #openstack-meeting01:27
fifieldtit would be good to have the whole document be displayed, but be able to mark certain paragraphs OK as you go01:27
DaisyI think, Transifex is all right as to message translation.01:27
yosshyYes, but no for long sentences.01:27
*** spzala has quit IRC01:28
Daisymaybe we can look for better tool for document translation.01:28
Daisybut the translation memory share will be a problem if we move documents to other tools.01:28
yosshyI hear that each review is closed if somebody push "reviewed" button on Transfex.01:29
fifieldtyeah - recently I've been translating AskBot, which has excellent translation memory already and it's a lot more fun01:29
Daisyin Transifex?01:29
fifieldtyeah01:29
DaisyAskBot don't have document translation.01:29
fifieldttrue01:29
fifieldtit's just good for strings01:29
fifieldtjust sharing experience :)01:29
Daisycorrect.01:29
Daisylet's continue the discussion with our translation team through mailing list.01:30
DaisyAgain, Transifex is a good tool to translate strings. Even it's not open source, in my opinion, I think it's acceptable.01:31
DaisyI don't know if the community agrees or not if Transifex is not open source any more.01:31
Daisyany other comments? If no, we move to next topic.01:32
gabrielcwthey think they are :) http://help.transifex.com01:32
Daisy#topic Open discussion01:32
yosshyIt looks that amotoki is absent today. He can describe problems to work on Transfex.01:32
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack I18n Meeting)"01:32
Daisyhttps://github.com/transifex/transifex/issues/206#issuecomment-1524320701:33
Daisygabrielcw: Transifex is going to not be open source any more.01:33
*** fnaval_ has joined #openstack-meeting01:34
gabrielcwoh01:34
DaisyI'd like to say something about progress with translation.01:34
yosshyAs a report, japanese team doesn't start the next translation work.01:34
DaisyChinese team is setting up the team now, and then we will start the translation of operation guide.01:35
DaisyI'm going to look for another coordinator in China, yet I didn't find. :)01:36
fifieldtask openstack is now in chinese too: https://ask.openstack.org/zh/01:36
DaisyThanks, fifieldt .01:36
DaisyAs to the priority, I will set Operation guide as the top priority during this period. Do you have opposite opinion?01:37
gabrielcwnope01:37
DaisyWhen we set the priority, I hope the whole translation team can follow it.01:37
DaisySo we focus on one job, when it is finished, we start another one.01:37
gabrielcwyeah, that's good!01:37
Daisyok.01:37
DaisyI'm going to write an update to the whole community. Here is a draft:01:38
Daisyhttps://etherpad.openstack.org/WhatupI18nTeam01:38
*** fnaval_ has quit IRC01:38
DaisyPlease let me know your opinion to expose your name and email in the mailing list. I write down the list of our contact information because I think there may be some people in your country to contact with you in order to understand more about openstack translations.01:39
yosshyamotoki wrote japanese dashboard page of doc.01:39
fifieldtI saw that yosshy, it looks good01:39
Daisyyosshy: where is the link?01:39
gabrielcwI agree,01:39
yosshyyeah.01:39
fifieldtdoes he plan to submit a patch?01:39
fifieldtor should we help to submit the patch?01:40
*** zehicle_at_dell has joined #openstack-meeting01:40
yosshyI'm now looking for the mail with the link...01:40
Daisyoh. I think I know the link. Sorry I just did not understand what was dashboard. :)01:40
fifieldthttp://openstack-ja.github.io/openstack-manuals/ja/01:41
yosshyoh, thank you.01:41
fifieldtmy pleasure01:41
*** fnaval_ has joined #openstack-meeting01:41
yosshyThat's a draft now and we are in review.01:42
*** fnaval_ has quit IRC01:42
Daisyyosshy: is it the first time you join the meeting? I don't see this id before.01:42
*** adjohn has quit IRC01:42
*** fnaval_ has joined #openstack-meeting01:43
*** adjohn has joined #openstack-meeting01:43
fifieldtok01:43
fifieldtthen after the review it will be submitted as a patch01:43
fifieldtsorry, I didn't completely read the emails :)01:43
yosshyNo. I joined the last meeting.01:43
fifieldt吉山?01:44
yosshybut perhaps I have another id. I'm new for webchat.01:44
*** jecarey has joined #openstack-meeting01:44
yosshyYeah. I'm Akira Yoshiyama (吉山).01:44
fifieldt:)01:44
DaisyI know this name: Akira Yoshiyama.01:45
DaisyThank you, yosshy. I just want to make sure I understand who you are. :)01:45
Daisyso any other topics?01:45
*** gongysh has joined #openstack-meeting01:46
Daisyif no, we will close the meeting.01:46
gabrielcwI'm still watching the Tx API for the translators stats01:46
gabrielcwjust a heads up01:46
yosshyok.01:46
DaisyThanks, gabrielcw .01:46
gabrielcwsure01:47
DaisyOur next meeting will be hosted next Month, 5th, Sep01:47
gabrielcwnothing new yet, but they fixed a bug I found recently very quickly01:47
yosshyI see.01:47
gabrielcwwill you guys attend the summit btw?01:47
DaisyYes, I see your email.01:47
DaisyI will. Will you, gabrielcw ?01:48
fifieldtI will be there :)01:48
DaisySurely you will, fifieldt .01:48
gabrielcwOh, I won't...:(01:48
gabrielcwit's very far from here :)01:48
*** martine_ has joined #openstack-meeting01:48
yosshyI hope to join it but...01:49
*** hanrahat has quit IRC01:49
*** lexinator has quit IRC01:49
gabrielcwThere will be some people from hp, but not me01:49
fifieldtI went to the venue01:49
Daisymaybe next time, the summit can be hosed in a city near Brazil.01:49
fifieldtit's awesome :)01:49
gabrielcwin fact this is my off work hours, so...01:49
gabrielcwwe hope so!01:49
Daisyanything else to discuss?01:50
gabrielcwquick question01:50
gabrielcwdo we have a deadline for the translations?01:50
Daisynot exactly deadline.01:50
*** danwent has quit IRC01:50
DaisyI know many people do the translation in their spare time, so there is no deadline in my mind.01:51
DaisyI don't want to push...01:51
gabrielcwyeah, but is there a target date, to try to finish01:51
*** sjing has joined #openstack-meeting01:52
DaisyBut, I think, there should be a deadline within a translation team.01:52
gabrielcwlosse date01:52
gabrielcw*loose01:52
*** shang has joined #openstack-meeting01:52
gabrielcwI understand01:52
Daisythe deadline can be discussed within a translation team, the team can decide, depending on their situation.01:52
yosshyI agree.01:52
DaisyThe top priority work for us are operation guide (documentation ) and Horizion.01:53
gabrielcwright, will you update the priorities in the Tx?01:53
DaisyAs to documentation, I don't have an overall deadline, I want each team to decide. When the document is ready, we can publish to website.01:53
DaisyBut as to the Horizion, when the code strings are frozen, there should be a deadline before the product release.01:54
gabrielcwright01:54
DaisySo when the code strings are frozen, I hope each translation team can focus their time on the Horzion transaltion. Again, this is not mandatory. Which team can finish on the time, which translation can be merged in the product release.01:55
fifieldtsounds reasonable01:55
Daisy:)01:56
DaisyI haven't talked with Horzion team yet.01:56
yosshyI see. We'll discuss about it in the next week because we have a week vacation in Japan.01:56
DaisyI'm going to attend their meeting next week, it's in the early moring, hard for me to catch.01:56
fifieldtenjoy it yosshy :D01:56
yosshyThank you.01:56
DaisyI will repor to you after I talk with Horizon team, about the string forzon time and release time.01:57
Daisyanything else?01:57
Daisyno?01:58
gabrielcwnot for me :)01:58
DaisyI will end up the meeting then.01:58
*** yaguang has joined #openstack-meeting01:58
DaisyThank you for joining !01:58
Daisy#endmeeting01:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"01:58
openstackMeeting ended Thu Aug 15 01:58:29 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)01:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2013/openstack_i18n_meeting.2013-08-15-01.02.html01:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2013/openstack_i18n_meeting.2013-08-15-01.02.txt01:58
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2013/openstack_i18n_meeting.2013-08-15-01.02.log.html01:58
*** yosshy has left #openstack-meeting01:58
gabrielcwThank you all, have a good evening/night01:58
*** haomaiwa_ has quit IRC01:59
*** colinmcnamara has joined #openstack-meeting02:00
*** haomaiwang has joined #openstack-meeting02:01
*** yamahata has quit IRC02:01
*** yamahata has joined #openstack-meeting02:02
*** brucer has quit IRC02:05
*** brucer has joined #openstack-meeting02:05
*** lexinator has joined #openstack-meeting02:05
*** adalbas has quit IRC02:08
*** dscannell has quit IRC02:11
*** marun has joined #openstack-meeting02:14
*** Daisy has quit IRC02:17
*** colinmcnamara has quit IRC02:18
*** marun has quit IRC02:20
*** marun has joined #openstack-meeting02:21
*** gabrielcw has quit IRC02:28
*** marun has quit IRC02:29
*** marun has joined #openstack-meeting02:31
*** ryanpetrello has joined #openstack-meeting02:33
*** dkehn has quit IRC02:36
*** neelashah has joined #openstack-meeting02:45
*** dkehn has joined #openstack-meeting02:46
*** nati_ueno has quit IRC02:51
*** stevemar has joined #openstack-meeting02:53
*** martine_ has quit IRC02:56
*** jasondotstar has quit IRC02:57
*** stevemar has quit IRC03:09
*** cbaesema has quit IRC03:11
*** zehicle has quit IRC03:11
*** zehicle has joined #openstack-meeting03:11
*** xxan0x has joined #openstack-meeting03:17
*** IlyaE has joined #openstack-meeting03:18
*** xxan0x has left #openstack-meeting03:20
*** cbaesema has joined #openstack-meeting03:21
*** markwash has joined #openstack-meeting03:22
*** SergeyLukjanov has joined #openstack-meeting03:22
*** markwash has quit IRC03:24
*** HenryG has quit IRC03:29
*** alexb_ has quit IRC03:31
*** markvan has joined #openstack-meeting03:35
*** martine_ has joined #openstack-meeting03:38
*** zhiyan has joined #openstack-meeting03:43
*** markvan has quit IRC03:48
*** vipul-away is now known as vipul03:56
*** dscannell has joined #openstack-meeting03:56
*** noslzzp has quit IRC04:03
*** noslzzp has joined #openstack-meeting04:04
*** sushils has quit IRC04:04
*** markwash has joined #openstack-meeting04:09
*** dscannell has quit IRC04:12
*** jecarey has quit IRC04:12
*** SergeyLukjanov has quit IRC04:13
*** lbragstad_ has quit IRC04:14
*** martine_ has quit IRC04:21
*** adjohn has quit IRC04:25
*** marun has quit IRC04:34
*** Mandell has joined #openstack-meeting04:39
*** ryanpetrello has quit IRC04:47
*** ryanpetrello has joined #openstack-meeting04:48
*** adjohn has joined #openstack-meeting04:48
*** eharney has quit IRC04:49
*** kashyap` is now known as kashyap04:50
*** vipul is now known as vipul-away04:50
*** stevemar has joined #openstack-meeting04:50
*** ryanpetr_ has joined #openstack-meeting04:54
*** markpeek has quit IRC04:54
*** ryanpetrello has quit IRC04:55
*** afazekas has joined #openstack-meeting04:56
*** ryanpetrello has joined #openstack-meeting04:58
*** ryanpetr_ has quit IRC05:00
*** kebray has joined #openstack-meeting05:02
*** asalkeld is now known as asalkeld_afk05:03
*** MarkAtwood has joined #openstack-meeting05:05
*** sdake_ has quit IRC05:07
*** terriyu has quit IRC05:12
*** neelashah has quit IRC05:13
*** afazekas has quit IRC05:17
*** vincent_hou has quit IRC05:19
*** ryanpetrello has quit IRC05:21
*** garyk has quit IRC05:23
*** fungi has quit IRC05:31
*** noslzzp has quit IRC05:40
*** thomasbiege has joined #openstack-meeting05:43
*** fungi has joined #openstack-meeting05:45
*** thomasbiege has quit IRC05:47
*** mrunge has joined #openstack-meeting05:47
*** kebray has quit IRC05:54
*** nati_ueno has joined #openstack-meeting05:58
*** MarkAtwood has left #openstack-meeting05:59
*** nati_ueno has quit IRC06:00
*** stevemar has quit IRC06:01
*** afazekas has joined #openstack-meeting06:07
*** marun has joined #openstack-meeting06:15
*** xBsd has joined #openstack-meeting06:18
*** afazekas has quit IRC06:19
*** mdurnosvistov has joined #openstack-meeting06:32
*** brucer has quit IRC06:36
*** mdurnosvistov_ has joined #openstack-meeting06:37
*** afazekas has joined #openstack-meeting06:40
*** mdurnosvistov has quit IRC06:41
*** jlucci has quit IRC06:46
*** marun has quit IRC06:47
*** henrynash has joined #openstack-meeting06:49
*** doron_afk has joined #openstack-meeting06:50
*** troytoman is now known as troytoman-away06:51
*** dcaroest has joined #openstack-meeting06:52
*** IlyaE has quit IRC06:52
*** jhenner has joined #openstack-meeting07:03
*** thomasbiege has joined #openstack-meeting07:06
*** ohadlevy has quit IRC07:13
*** ohadlevy has joined #openstack-meeting07:13
*** bnemec has quit IRC07:16
*** cybertron has joined #openstack-meeting07:19
*** Daviey has quit IRC07:22
*** thomasbiege has quit IRC07:23
*** tkammer has joined #openstack-meeting07:24
*** dcaroest has quit IRC07:26
*** thomasbiege has joined #openstack-meeting07:27
*** xBsd has quit IRC07:28
*** Daviey has joined #openstack-meeting07:28
*** thomasbiege has quit IRC07:29
*** thomasbiege has joined #openstack-meeting07:30
*** sungju_ has joined #openstack-meeting07:35
*** sungju_ has quit IRC07:35
*** dcaroest has joined #openstack-meeting07:37
*** xBsd has joined #openstack-meeting07:38
*** xBsd has quit IRC07:42
*** thomasbiege has quit IRC07:47
*** jamespage_ has joined #openstack-meeting07:47
*** mdurnosvistov_ has quit IRC07:47
*** yaguang has quit IRC07:49
*** yaguang has joined #openstack-meeting07:56
*** rods has joined #openstack-meeting07:59
*** adjohn has quit IRC08:07
*** derekh has joined #openstack-meeting08:09
*** euanh has joined #openstack-meeting08:16
*** euanh has left #openstack-meeting08:17
*** ndipanov_gone is now known as ndipanov08:20
*** otherwiseguy has quit IRC08:24
*** asalkeld_afk is now known as asalkeld08:26
*** xBsd has joined #openstack-meeting08:29
*** ohadlevy has quit IRC08:32
*** ohadlevy has joined #openstack-meeting08:34
*** luisg has quit IRC08:34
*** luisg has joined #openstack-meeting08:35
*** thomasbiege has joined #openstack-meeting08:36
*** otherwiseguy has joined #openstack-meeting08:37
*** adjohn has joined #openstack-meeting08:37
*** sjing has quit IRC08:38
*** thomasbiege has quit IRC08:41
*** adjohn has quit IRC08:49
*** adjohn has joined #openstack-meeting08:54
*** jtomasek has joined #openstack-meeting08:57
*** ohadlevy has quit IRC09:01
*** ilyashakhat has quit IRC09:01
*** adjohn has quit IRC09:02
*** ohadlevy has joined #openstack-meeting09:03
*** llu has joined #openstack-meeting09:07
*** henrynash has quit IRC09:13
*** boris-42 has joined #openstack-meeting09:14
*** doron_afk is now known as doron09:17
*** henrynash has joined #openstack-meeting09:17
*** SergeyLukjanov has joined #openstack-meeting09:26
*** sushils has joined #openstack-meeting09:42
*** lbragstad has quit IRC09:49
*** xBsd has quit IRC09:52
*** sungju_ has joined #openstack-meeting09:57
*** lbragstad has joined #openstack-meeting09:57
*** sungju_ has quit IRC09:58
*** psedlak has joined #openstack-meeting10:02
*** isviridov has quit IRC10:09
*** isviridov has joined #openstack-meeting10:09
*** isviridov has quit IRC10:13
*** sushils has quit IRC10:15
*** isviridov has joined #openstack-meeting10:15
*** macjack has quit IRC10:16
*** isviridov has quit IRC10:17
*** isviridov has joined #openstack-meeting10:17
*** yaguang has quit IRC10:20
*** cybertron has quit IRC10:21
*** bnemec has joined #openstack-meeting10:22
*** lbragstad has quit IRC10:25
*** henrynash has quit IRC10:31
*** lbragstad has joined #openstack-meeting10:32
*** blamar has quit IRC10:32
*** lbragstad1 has joined #openstack-meeting10:40
*** lbragstad has quit IRC10:40
*** lbragstad1 has quit IRC10:46
*** gongysh has quit IRC10:48
*** mdomsch has joined #openstack-meeting10:52
*** lbragstad has joined #openstack-meeting10:53
*** mdomsch has quit IRC10:56
*** dprince has joined #openstack-meeting10:59
*** xBsd has joined #openstack-meeting11:01
*** adjohn has joined #openstack-meeting11:02
*** EntropyWorks has quit IRC11:05
*** EntropyWorks has joined #openstack-meeting11:05
*** adjohn has quit IRC11:10
*** doron is now known as doron_afk11:11
*** tkammer has quit IRC11:14
*** Guest71730 is now known as mdurnosvistov11:17
*** danwent has joined #openstack-meeting11:24
*** pcm_ has joined #openstack-meeting11:26
*** chuckieb has joined #openstack-meeting11:32
*** chuckieb has quit IRC11:32
*** chuckieb has joined #openstack-meeting11:39
*** bgorski has quit IRC11:39
*** dprince has quit IRC11:40
*** SergeyLukjanov has quit IRC11:41
*** gongysh has joined #openstack-meeting11:48
*** sushils has joined #openstack-meeting11:56
*** troytoman-away is now known as troytoman12:01
*** fifieldt has quit IRC12:03
*** woodspa has joined #openstack-meeting12:07
*** tkammer has joined #openstack-meeting12:07
*** radez_g0n3 is now known as radez12:08
*** rongze_ has quit IRC12:11
*** rongze has joined #openstack-meeting12:12
*** thomasm has joined #openstack-meeting12:12
*** doron_afk is now known as doron12:18
*** cwolfe__ has joined #openstack-meeting12:21
*** macjack has joined #openstack-meeting12:22
*** adalbas has joined #openstack-meeting12:23
*** cwolferh_ has quit IRC12:24
*** jtomasek_ has joined #openstack-meeting12:28
*** sandywalsh has quit IRC12:31
*** jtomasek has quit IRC12:32
*** dvarga has joined #openstack-meeting12:32
*** mrunge has quit IRC12:32
*** dvarga has quit IRC12:36
*** noslzzp has joined #openstack-meeting12:38
*** lbragstad has quit IRC12:39
*** lblanchard has joined #openstack-meeting12:42
*** kevinconway has joined #openstack-meeting12:45
*** ruhe has joined #openstack-meeting12:46
*** sandywalsh has joined #openstack-meeting12:46
*** haomaiwang has quit IRC12:46
*** rongze has quit IRC12:47
*** dprince has joined #openstack-meeting12:47
*** terriyu has joined #openstack-meeting12:51
*** neelashah has joined #openstack-meeting12:52
*** HenryG has joined #openstack-meeting12:55
*** litong has joined #openstack-meeting12:59
*** ayoung has quit IRC13:00
*** martine has joined #openstack-meeting13:03
*** martine is now known as martine_13:03
*** anteaya has joined #openstack-meeting13:05
*** funzo|afk is now known as funzo13:07
*** vijendar has joined #openstack-meeting13:10
*** markmcclain has joined #openstack-meeting13:13
*** dcramer_ has joined #openstack-meeting13:14
*** dscannell has joined #openstack-meeting13:15
*** eharney has joined #openstack-meeting13:16
*** eharney has quit IRC13:16
*** eharney has joined #openstack-meeting13:16
*** burt has joined #openstack-meeting13:17
*** lbragstad has joined #openstack-meeting13:17
*** edmund1 has quit IRC13:20
*** SergeyLukjanov has joined #openstack-meeting13:21
*** ruhe has quit IRC13:22
*** SergeyLukjanov has quit IRC13:23
*** fnaval_ has quit IRC13:24
*** doron is now known as doron_afk13:25
*** SergeyLukjanov has joined #openstack-meeting13:28
*** markmcclain has quit IRC13:29
*** jtomasek_ is now known as jtomasek13:32
*** jecarey has joined #openstack-meeting13:33
*** jhenner has quit IRC13:35
*** mdenny has joined #openstack-meeting13:38
*** changbl has quit IRC13:39
*** MIDENN_ has quit IRC13:41
*** ayoung has joined #openstack-meeting13:42
*** markpeek has joined #openstack-meeting13:44
*** thang_ has joined #openstack-meeting13:46
*** fnaval_ has joined #openstack-meeting13:47
*** krtaylor has quit IRC13:48
*** dolphm has joined #openstack-meeting13:54
*** armax has joined #openstack-meeting13:55
*** lblanchard1 has joined #openstack-meeting13:56
*** haomaiwang has joined #openstack-meeting13:57
*** spenceratx has joined #openstack-meeting13:57
*** adjohn has joined #openstack-meeting13:57
*** lblanchard has quit IRC13:58
*** pentameter has joined #openstack-meeting13:59
*** markvan has joined #openstack-meeting14:00
*** markvan_ has joined #openstack-meeting14:00
*** blamar has joined #openstack-meeting14:00
*** lpabon has joined #openstack-meeting14:01
*** spenceratx has left #openstack-meeting14:01
*** trobert2 has joined #openstack-meeting14:02
*** trobert2 has quit IRC14:02
*** jasondotstar has joined #openstack-meeting14:02
*** markvan_ has quit IRC14:04
*** markvan_ has joined #openstack-meeting14:04
*** markvan has quit IRC14:04
*** markvan_ is now known as markvan14:05
*** adjohn has quit IRC14:05
*** venkatesh has joined #openstack-meeting14:06
*** blamar has quit IRC14:06
*** blamar has joined #openstack-meeting14:06
*** mrodden has joined #openstack-meeting14:07
*** tanisdl has joined #openstack-meeting14:07
*** kebray has joined #openstack-meeting14:08
*** HenryG_ has joined #openstack-meeting14:09
*** gongysh has quit IRC14:09
*** rnirmal has joined #openstack-meeting14:09
*** SergeyLukjanov has quit IRC14:10
*** lexinator has quit IRC14:11
*** HenryG has quit IRC14:12
*** markmcclain has joined #openstack-meeting14:17
*** huats_ has joined #openstack-meeting14:19
*** huats_ has quit IRC14:19
*** huats_ has joined #openstack-meeting14:19
*** huats has quit IRC14:19
*** kebray has quit IRC14:21
*** SergeyLukjanov has joined #openstack-meeting14:22
*** ruhe has joined #openstack-meeting14:22
*** kebray has joined #openstack-meeting14:22
*** ruhe has quit IRC14:25
*** yhe has joined #openstack-meeting14:28
*** markvan has quit IRC14:28
*** yhe has quit IRC14:29
*** adalbas has quit IRC14:30
*** lexinator has joined #openstack-meeting14:31
*** gatuus has joined #openstack-meeting14:31
*** tkammer has quit IRC14:32
*** rwsu-away is now known as rwsu14:34
*** changbl has joined #openstack-meeting14:36
*** gongysh has joined #openstack-meeting14:37
*** dscannell has quit IRC14:39
*** ruhe has joined #openstack-meeting14:41
*** martine_ has quit IRC14:41
*** randallburt has joined #openstack-meeting14:43
*** danwent has quit IRC14:43
*** randallburt has quit IRC14:43
*** randallburt has joined #openstack-meeting14:43
*** randallburt has left #openstack-meeting14:43
*** BobBall_ has joined #openstack-meeting14:45
*** tkammer has joined #openstack-meeting14:45
*** adalbas has joined #openstack-meeting14:46
*** dolphm has quit IRC14:48
*** hartsocks1 has joined #openstack-meeting14:50
*** hartsocks1 has quit IRC14:50
*** krtaylor has joined #openstack-meeting14:50
*** hartsocks has joined #openstack-meeting14:51
*** BobBall_ has quit IRC14:52
*** hanrahat has joined #openstack-meeting14:52
*** dhellmann_ is now known as dhellmann14:52
*** ruhe has quit IRC14:53
*** ivasev has joined #openstack-meeting14:56
*** doron_afk has quit IRC14:57
*** adjohn has joined #openstack-meeting14:57
*** lexinator has quit IRC14:58
*** edmund has joined #openstack-meeting15:00
*** HenryG_ has quit IRC15:00
*** marun has joined #openstack-meeting15:00
*** leif has joined #openstack-meeting15:01
*** boris-42 has quit IRC15:01
*** leif is now known as Guest8082215:02
*** venkatesh has quit IRC15:04
*** alexb_ has joined #openstack-meeting15:07
*** alexb_ has quit IRC15:09
*** alexb_ has joined #openstack-meeting15:10
*** venkatesh has joined #openstack-meeting15:11
*** lpabon has quit IRC15:11
*** sacharya has joined #openstack-meeting15:11
*** venkatesh has quit IRC15:11
*** dscannell has joined #openstack-meeting15:13
*** nati_ueno has joined #openstack-meeting15:14
*** mdomsch has joined #openstack-meeting15:16
*** lexinator has joined #openstack-meeting15:17
*** afazekas has quit IRC15:17
*** alexb_ has quit IRC15:17
*** alexb_ has joined #openstack-meeting15:18
*** gongysh has quit IRC15:20
*** bdpayne has joined #openstack-meeting15:22
*** troytoman is now known as troytoman-away15:23
*** nati_ueno has quit IRC15:23
*** SergeyLukjanov has quit IRC15:24
*** mrodden has quit IRC15:25
*** ruhe has joined #openstack-meeting15:27
*** adjohn has quit IRC15:27
*** SergeyLukjanov has joined #openstack-meeting15:29
*** zehicle_at_dell has quit IRC15:32
*** lblanchard1 has quit IRC15:33
*** hemna has joined #openstack-meeting15:33
*** lblanchard has joined #openstack-meeting15:35
*** Mandell has quit IRC15:36
*** IlyaE has joined #openstack-meeting15:38
*** markwash has quit IRC15:39
*** mrodden has joined #openstack-meeting15:42
*** markmcclain has quit IRC15:42
*** zehicle has quit IRC15:45
*** gkleiman has joined #openstack-meeting15:46
*** MarkAtwood has joined #openstack-meeting15:47
*** markvan has joined #openstack-meeting15:51
*** kevinconway_ has joined #openstack-meeting15:54
*** burt has quit IRC15:54
*** stevemar has joined #openstack-meeting15:54
*** kevinconway has quit IRC15:56
*** kevinconway_ is now known as kevinconway15:56
*** afazekas has joined #openstack-meeting15:56
*** esker has quit IRC15:58
*** esker has joined #openstack-meeting15:59
*** shang has quit IRC16:02
*** herndon has joined #openstack-meeting16:02
*** zehicle_at_dell has joined #openstack-meeting16:03
*** esker has quit IRC16:04
*** tkammer has quit IRC16:04
*** RajeshMohan has quit IRC16:04
*** RajeshMohan has joined #openstack-meeting16:04
*** changbl has quit IRC16:06
*** zbitter has joined #openstack-meeting16:09
*** lpabon has joined #openstack-meeting16:12
*** zaneb has quit IRC16:12
*** alexb_ has quit IRC16:14
*** krtaylor has quit IRC16:23
*** KurtMartin has joined #openstack-meeting16:25
*** lexinator has quit IRC16:26
*** SergeyLukjanov has quit IRC16:27
*** HenryG has joined #openstack-meeting16:28
*** IlyaE has quit IRC16:29
*** kmartin has quit IRC16:29
*** alexb_ has joined #openstack-meeting16:30
*** comay has quit IRC16:31
*** gatuus has quit IRC16:31
*** lexinator has joined #openstack-meeting16:31
*** gkleiman has quit IRC16:32
*** ruhe has quit IRC16:34
*** krtaylor has joined #openstack-meeting16:37
*** jasondotstar has quit IRC16:39
*** derekh has quit IRC16:41
*** ruhe has joined #openstack-meeting16:42
*** KurtMartin is now known as kmartin16:42
*** thomasbiege has joined #openstack-meeting16:42
*** rongze has joined #openstack-meeting16:45
*** thomasbiege has quit IRC16:46
*** adjohn has joined #openstack-meeting16:46
*** alexb_ has quit IRC16:46
*** lexinator has quit IRC16:48
*** lexinator has joined #openstack-meeting16:49
*** fungi has quit IRC16:49
*** markwash has joined #openstack-meeting16:49
*** fungi has joined #openstack-meeting16:50
*** zhiyan has quit IRC16:50
*** henrynash has joined #openstack-meeting16:51
*** esker_ has joined #openstack-meeting16:52
*** sarob has joined #openstack-meeting16:53
*** mlavalle has joined #openstack-meeting16:53
*** otherwiseguy has quit IRC16:54
*** briancline has joined #openstack-meeting16:54
*** vipul-away is now known as vipul16:54
*** vipul is now known as vipul-away16:55
*** patelna has joined #openstack-meeting16:58
*** luz has joined #openstack-meeting16:58
*** markmcclain has joined #openstack-meeting16:59
*** IlyaE has joined #openstack-meeting16:59
mtreinish#startmeeting qa17:00
openstackMeeting started Thu Aug 15 17:00:07 2013 UTC and is due to finish in 60 minutes.  The chair is mtreinish. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: qa)"17:00
openstackThe meeting name has been set to 'qa'17:00
mtreinishwho do we have here?17:00
mkodererHi17:00
mlavallehi17:00
*** bpb has joined #openstack-meeting17:00
adalbashi17:00
mtreinishtoday's agenda:17:00
mtreinish#link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting17:00
mtreinishit's pretty short today just the usual things no one added anything extra17:01
mtreinishso I guess lets dive into it17:01
mtreinish#topic testr status17:01
*** openstack changes topic to "testr status (Meeting topic: qa)"17:01
mtreinishso my topic is up first17:01
*** jdurgin1 has joined #openstack-meeting17:02
mtreinishearlier this week I got the fix for the last big blocking race condition merged17:02
*** IlyaE has quit IRC17:02
mtreinishand the runs seem fairly stable17:02
mtreinishso I added a parallel run nonvoting to the gate queue on zuul17:02
mtreinishI'm going to watch it for a while to see how stable it seems17:02
mkoderercool17:02
mtreinishand hopefully make it the default sometime in the next week or 217:02
mtreinishright now we're tracking down some other races that have been popping up17:03
*** SumitNaiksatam has quit IRC17:03
*** thomasbiege has joined #openstack-meeting17:03
mtreinishand I hope to get tenant isolation on swift and keystone testing before we green light it17:03
*** ruhe has quit IRC17:03
mtreinishbut we're really close here17:03
mkodereris there a plan to delete all the nose things in the code?17:03
*** IlyaE has joined #openstack-meeting17:03
*** thomasm has left #openstack-meeting17:03
mtreinishmkoderer: yeah at some point, just right now I've been too distracted with trying to get it gating parallel to push the patch17:04
mkoderermtreinish: ok cool17:04
mtreinishmkoderer: feel free to push it yourself if you'd like17:04
mkoderermtreinish: ok shouldn't be hard17:04
mtreinishok, does anyone have anything else on testr?17:05
*** nati_ueno has joined #openstack-meeting17:05
*** sdake has joined #openstack-meeting17:05
*** sdake has quit IRC17:05
*** sdake has joined #openstack-meeting17:05
adalbasmtreinish, i saw you get the tenant_isolation for swift17:05
adalbasdo you still need to get the swift tempest tests locked up ?17:06
mtreinishadalbas: yeah I pushed it out, but it's probably going to need a devstack change to get it working17:06
mtreinishadalbas: probably not if it was a user conflict that was causing the fail17:06
adalbasok17:06
mtreinishadalbas: we can pick this up on the qa channel after the meeting though17:07
adalbassure17:07
mtreinishok, then moving on to the next topic17:07
mtreinish#topic stress tests status17:07
*** openstack changes topic to "stress tests status (Meeting topic: qa)"17:07
mtreinishmkoderer: you're up17:07
*** danwent has joined #openstack-meeting17:07
mkodererso I want to introduce this decorator "stresstest"17:07
mkodererit will automatically set attr type=stress17:08
mkodererwith this I could use subunit to discover all stress test inside the tempest tests17:08
mkodererthats my plan and I am working on that17:08
mkodererif we have this we could go through the test and search for good candidates17:09
mtreinishok, cool so things are in motion with that then17:09
mkodereryes17:09
*** kevinconway has quit IRC17:09
mkodererabout this https://review.openstack.org/#/c/38980/17:09
mtreinishI imagine a lot of tests won't be good candidates for stress tests17:09
mtreinishlike the negative tests :)17:10
mtreinishafazekas: ^^^ are you around?17:10
mkoderermtreinish: thats right.. but I am quite sure we will have some good ones17:10
mkoderercould be that https://review.openstack.org/#/c/38980/ is not needed after my fix17:10
mkodererbut anyway we could use it in the meanwhile17:11
mtreinishmkoderer: ok, yeah might be, you should coordinate with afazekas about that17:11
mtreinishbut he doesn't seem to be around right now17:11
mkodererI think I will chat with afazekas when hes around17:11
mkoderernp17:11
mkodererany other question?17:12
mtreinishmkoderer: ok all sounds good to me. Anything else on the stress test front?17:12
mtreinishmkoderer: nothing from me :)17:12
mkodererok cool :)17:12
afazekasre17:13
mtreinishok then we'll move on to the next topic17:13
mlavallemtreinish: I want to report status on https://blueprints.launchpad.net/tempest/+spec/fix-gate-tempest-devstack-vm-quantum-full17:13
mtreinish#topic other blueprint status17:13
*** openstack changes topic to "other blueprint status (Meeting topic: qa)"17:13
*** lpabon_ has joined #openstack-meeting17:13
*** thomasbiege has quit IRC17:13
*** lpabon_ has quit IRC17:13
mtreinishmlavalle: ok you're up17:13
*** lpabon has quit IRC17:13
*** lpabon_ has joined #openstack-meeting17:13
mlavallemtreinish: we have achieved good progress on this. Several of the items in the BP are already fixed17:13
mlavallemtreinish: we have a shot at getting this done by H-317:14
*** lpabon_ has quit IRC17:14
mtreinishmlavalle: ok cool, that would be great to get the quantum full jobs passing17:14
mlavallemtreinish: I am working now on a nova patch, that is required by one of the tests I am fixing17:14
*** IlyaE has quit IRC17:14
*** colinmcnamara has joined #openstack-meeting17:14
afazekasmlavalle: do you know about a bug related to the failing fixed ip or interface tests ?17:14
mlavallemtresinish: any help I can get with this would be great: https://review.openstack.org/#/c/4132917:15
*** lpabon has joined #openstack-meeting17:15
mlavalleafazekas: no i don't17:15
*** colinmcnamara has quit IRC17:15
mtreinishmlavalle: sure I'll take a look17:15
mlavallethat's it17:16
mtreinishand point some nova cores at it too17:16
*** colinmcnamara has joined #openstack-meeting17:16
mtreinishmlavalle: ok cool, one quick thing about neutron is last week we had to skip another neutron test17:16
afazekashttps://bugs.launchpad.net/neutron/+bug/1189671 another interesting related bug17:17
uvirtbotLaunchpad bug 1189671 in neutron "default quota driver not suitable for production" [Wishlist,In progress]17:17
mtreinishbecause a broken change got merged while the gate was messed up and passing all the tests17:17
mlavallemtreinish: ok, i'll take a look17:17
mlavalleafazekas: i'l take a look17:17
*** Ravikumar_hp has joined #openstack-meeting17:18
afazekasunfortunately  when thet test case was skipped several additional introduced..17:18
mtreinishmlavalle: I can dig up a link but it's one of the bugs marked as critical17:18
mtreinishmarun was working on it yesterday I think17:18
afazekastho know ones are fixed, but something still not ok with the ssh connectivity17:18
marunafazekas: I am looking at it17:19
mlavalleI'll ping marun17:19
marunIt's not ssh that's the problem - it's the metadata service.17:19
afazekasmarun: can you reproduce it ?17:19
marunafazekas: trivially17:19
marunbut i don't know why it's happening.17:19
marunworking on it now17:19
*** jhenner has joined #openstack-meeting17:20
afazekasmarun>: cool17:20
mlavallemarun: i'll let you run with it,…..17:20
mtreinishmlavalle: ok, is there anything else on neutron status?17:20
mlavallei'm done17:21
mtreinishok then are there any other blueprints that need to be discussed17:21
afazekasleaking17:21
*** sdake_ has joined #openstack-meeting17:22
mtreinishafazekas: ok what's going on with that?17:22
afazekaslooks like the original connect  did not liked, so I will introduce different one17:22
afazekasWhich will be designed to clean up at run time, and also report the issues17:23
afazekasbut it will not cover the leakage what is not visible via the api17:23
afazekasand it will relay on the tenant isolation17:24
mtreinishafazekas: will it ensure that the isolated tenants will be cleaned up too?17:24
afazekasjust about the resources in the tenant17:24
mtreinishafazekas: ok17:25
mtreinishis there anything else about resource leakage detection?17:26
afazekasI can restore the previous patch if anybody interested in the global leakage17:27
mtreinishafazekas: do you have a link?17:27
*** HenryG has quit IRC17:27
*** cwolfe__ has quit IRC17:28
*** lpabon has quit IRC17:28
*** SumitNaiksatam has joined #openstack-meeting17:28
afazekashttps://review.openstack.org/#/c/35516/17:28
mtreinishafazekas: ok, I'll take a look at it later and let you know17:29
*** jdurgin1 has quit IRC17:29
afazekasthx17:29
*** herndon has quit IRC17:29
*** Mandell has joined #openstack-meeting17:29
mtreinishok then, moving on:17:29
mtreinish#topic critical reviews17:30
*** openstack changes topic to "critical reviews (Meeting topic: qa)"17:30
mtreinishdoes anyone have any reviews that they like to bring up?17:30
Ravikumar_hpI have one concern17:30
Ravikumar_hpon review process17:30
Ravikumar_hpplease bear with mee17:31
Ravikumar_hpI want to put up my point17:31
Ravikumar_hpI want to raise one concern.17:31
Ravikumar_hpTest developement and contribution seems to be really pain.17:31
Ravikumar_hpIt takes 10 patches to get through even for people contributing to Tempest for more than one year.17:31
Ravikumar_hpWe need to have some policy on reviews.17:31
Ravikumar_hpIt appears many times , some late entrants offer new comments/suggestions when it seems like code review done and one more review cycle.17:31
Ravikumar_hpwe need to refine the process .. Otherwise , it slows down test developement cycle and difficult to maintain contributor's motivation17:31
*** pcm__ has joined #openstack-meeting17:32
afazekasRavikumar_hp: I agree, do you have a recommendation how to do it?17:32
mkodererRavikumar_hp: I understand that point17:32
mkodererbut it's hard to solve that17:32
mtreinishRavikumar_hp: I understand what you're saying but the review process is needed17:32
mtreinishwe need to ensure code quality17:32
mtreinishand review resources are limited17:32
Ravikumar_hpas a group, we need to fix this17:33
mtreinishso sometimes it takes time17:33
Ravikumar_hpnow a days , all the reviews17:33
Ravikumar_hpI can agree for framework design17:33
Ravikumar_hpif test developement takes 10 reviews, then something is wrong17:33
*** krtaylor has quit IRC17:33
Ravikumar_hpIt is not working well17:33
afazekasmtreinish: the small nits can be fixed later17:34
marundisagree17:34
marunYou fix it before merge or it doesn't get fixed17:34
mtreinishmarun: +1 that has been my experience as well17:34
*** pcm_ has quit IRC17:34
Ravikumar_hpwe cannot move forward if one test contribution takes one month / 10 patch reviews17:34
marunMy suggestion is to have a guide for what needs to be done, so at least the criteria is clear.17:34
marunIf the submitter does not follow the guide, then it takes 10 reviews.17:34
patelnathiis is over engineering test code17:34
mkodererthe question is why does it take 10 patchsets17:34
marunIf they do follow the guide, it gets in faster.17:35
patelnain your own company, do qa has 10 or more reviews?17:35
mkodererit's just because of nits.. then it's too much17:35
afazekasmarun: IMHO not the 10 or 100 review is the issue, the 1 month17:35
Ravikumar_hpmany times , reviewers change from patch to patch17:35
marunIn your own company, do you have clear criteria for what is good?17:35
*** danwent has quit IRC17:35
afazekasmarun: waiting on review reply17:35
patelnawe need to be agile in our test development process...I suggest we have 2 to 3 reviews17:35
marunThat's a different issue, though.17:35
Ravikumar_hpif two reviwers take care of one code submission , we can finish in max 3 patches17:36
marunafazekas: timely review vs quality of review17:36
patelnayes - we trust our QA17:36
marunWell, we need that same criteria in tempest.17:36
Ravikumar_hpjust 20 lines of code takes one month - ten patches17:36
marunWe need it in writing, so it isn't just in some people's head.17:36
afazekasmarun: yes17:36
patelnaso lets do 2 things to improve this process (a) define what will code review consists off? a checklist (b) reduce the reviewer to 2 to 317:37
marunRavikumar_hp: So think of a way to fix the problem that does not result in lower review quality.17:37
*** jhenner1 has joined #openstack-meeting17:37
*** jhenner has quit IRC17:37
*** jhenner1 has quit IRC17:37
*** jhenner2 has joined #openstack-meeting17:37
mkodererI don't think that limiting the number of reviewer will be a good solution17:37
mkoderer ^reviewers17:37
patelnait is17:37
afazekasIMHO every typical review issue should be in the HACKING,rst17:37
marun+100017:37
Ravikumar_hpmarun: my suggestion - only TWO reviewers per one submission17:37
marunAnd over time that list should evolve17:37
mtreinishafazekas: yes that should be the case17:37
patelnado anyone know how many reviews dev code goes thru before merge?17:37
mtreinishbut I think we might have some gaps I'm not sure17:37
mkodererRavikumar_hp: only two core reviewers?17:38
marunRavikumar_hp: I don't think that's workable.17:38
afazekassome additional style issue can be tested by flake817:38
marunTwo core people, fine.17:38
patelna+1 Ravikumar_hp17:38
marunBut there are often stakeholders outside of those two17:38
marunLook, tempest is not unique17:38
mkoderer-117:38
marunThere are tons of core projects that have the same challenges.17:38
mtreinishpatelna, Ravikumar_hp: limiting the number of reviews is not the solution17:38
patelnawe have less QA contributors17:38
marunThinking that we are special and need to do something different?  Just silly.17:38
Ravikumar_hpmtreinish: we want good quality , but need to refine so as to minimize patches/cycles, duration17:39
marunHow about maximizing patch quality?17:39
patelnado u want to add more coverage or do less tests and more reviewers -- and then turnign people away as they been frustrated17:39
*** troytoman-away is now known as troytoman17:39
marunTough17:39
*** alexb_ has joined #openstack-meeting17:39
marunIf we don't screen for quality, things fall apart.17:40
mtreinishok I think that this topic has been played out enough. I think we should move on17:40
patelnawe really need to draft a guideline for reviewers/checklist17:40
*** lblanchard has quit IRC17:40
marunSo let's focus on improving patch quality17:40
marunNOT17:40
marunreducing review quantity17:40
mtreinishdoes anyone have any reviews they want to bring up17:40
patelnano one is saying don't screen for the quality -- you are missing the point17:40
mkodererI think if someone feels fruststarted it the best way to have direct communication via IRC...17:40
*** chuckieb|2 has joined #openstack-meeting17:40
afazekashttps://review.openstack.org/#/c/35165/17:40
Ravikumar_hpmtreinish: Thanks17:40
afazekaslooks like I got an opposite  review response at the end, can I return to something  closer to the original version ?17:41
mtreinishafazekas: that's marked as abandonded17:41
mtreinishare there any other reviews? Otherwise we'll move on17:42
afazekasmtreinish: restored17:42
*** chuckieb has quit IRC17:43
mtreinishafazekas: ok cool17:43
mkoderer;)17:43
*** vipul-away is now known as vipul17:44
afazekasI will move back to the original new module / function style unless otherwise requested17:44
mtreinishafazekas: I'll have to take a look in detail after the meeting17:44
*** vaml has joined #openstack-meeting17:44
mtreinishok if there aren't any other reviews that people want to bring attention to then let move on to the open discussion17:45
mtreinish#topic open discussion17:45
*** openstack changes topic to "open discussion (Meeting topic: qa)"17:45
marunI have a testr question17:45
mtreinishmarun: ok17:45
marunAs per discussion yesterday, it appears tempest is broken on py2617:45
marunThe fix would be moving away from setupClass?17:46
*** henrynash has quit IRC17:46
marunIs there a plan/effort underway to accomplish that?17:46
afazekasmarun: IMHO the fixing patch is merged17:46
marunsince yesterday?17:46
*** changbl has joined #openstack-meeting17:46
mtreinishmarun: not currently we use setupClass fairly extensively throughout tempest17:46
mtreinishreworking things to avoid using it would be a huge undertaking17:46
afazekasmarun: the patch was older, but it contained the py 2.6 compatibility step17:47
marunafazekas: are you running successfully on 2.6 then?17:47
marunThis is really important for Red Hat.17:47
marunWe need to run Tempest on RHEL 6.4 with py26.17:48
marunIf anyone is running on 2.6 then I'd be happy to talk offline about what I might be doing wrong.17:48
marunBut if not, then Red Hat will likely want to see a move away from setupClass and will devote resources to making it happen.17:49
*** sdake_ has quit IRC17:49
mtreinishmarun: I know there have been troubles with py26 lately especially after we've been moving to testr17:49
*** malini1 has joined #openstack-meeting17:49
mtreinishbut I don't have py26 on any of my systems so I haven't been able to test things17:49
afazekasmarun: are you using nosetests or testr ?17:50
marunafazekas: testr + py26 is broken because it doesn't seem to invoke setupClass17:50
*** SergeyLukjanov has joined #openstack-meeting17:50
marunafazekas: nose appears to work, but has to be manually invoked17:50
mtreinishmarun: but if you switch back to nose would it work?17:50
afazekasmarun: you can run it with nose on py 2.617:50
marunSo manually run?17:51
mtreinishmarun: ok, then would adding a nondefault job in tox and run tests to use nose solve this17:51
marunmtreinish: +117:51
marunIt's not so much for me, but allowing non-developers to be able to run tempest trivially.17:51
mtreinishmarun: ok that's simple enough17:52
marunOk, cool.17:52
mtreinish#action mtreinish to add options to use nose instead of testr for py26 compat17:52
mtreinishmkoderer: so much for pulling out all the nose references then17:52
marun:)17:52
mkoderermtreinish: yeah17:52
marunrhel'd again ;)17:53
mtreinishok, are there any other topics to discuss in the last 7 min?17:53
malini1do we really want both testr and nose to be invoked, guessing they do not cover exactly the same stuff17:53
*** salv-orlando has quit IRC17:53
marunmalini1: I think the alternative is removing the use of setupClass, which is desirable but costly.17:54
mtreinishmalini1: it would either or. Testr is still the default but if you run with py26 you'll have to use nose17:54
malini1got it -- thanks17:55
mkodereris it a know bug in testr?17:55
mkoderer^known17:55
uvirtbotmkoderer: Error: "known" is not a valid command.17:55
marunmkoderer: yes, I talked with lifeless about it yesterday.17:55
mkodererok - so if this would be fixed we could switch to testr17:56
afazekasmarun: the numbered tests also should be fixed when they are start working17:56
*** Ravikumar_hp has quit IRC17:57
marunmkoderer: if setupClass was not used, then testr + py26 would play nicely17:57
marunafazekas: Ah, yes.17:57
afazekasmarun: it is required to run as a stress test17:57
marunafazekas: Why required for a stress test?17:57
*** dcaroest has quit IRC17:58
marunafazekas: I thought the way to handle order was simply to inline the functionality?17:58
afazekasbecause you specify exactly on test case IE  test method17:58
*** eharney has quit IRC17:58
*** dani4571 has joined #openstack-meeting17:58
mtreinishso we've got ~1 min left. afazekas, marun do you want to pick this up on qa?17:58
*** alexb_ has quit IRC17:58
marunmtreinish: sounds good17:59
afazekasok17:59
*** jasondotstar has joined #openstack-meeting17:59
mtreinishok I guess a good as point as any to stop17:59
mtreinish#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Thu Aug 15 17:59:38 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-08-15-17.00.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-08-15-17.00.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-08-15-17.00.log.html17:59
mtreinishthanks everyone18:00
*** IlyaE has joined #openstack-meeting18:00
*** sarob has quit IRC18:01
*** sarob has joined #openstack-meeting18:01
*** kmartin has quit IRC18:02
bdpayne#startmeeting OpenStack Security Group18:03
openstackMeeting started Thu Aug 15 18:03:30 2013 UTC and is due to finish in 60 minutes.  The chair is bdpayne. Information about MeetBot at http://wiki.debian.org/MeetBot.18:03
*** radez is now known as radez_g0n318:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:03
*** openstack changes topic to " (Meeting topic: OpenStack Security Group)"18:03
openstackThe meeting name has been set to 'openstack_security_group'18:03
bdpaynehi everyone, sorry for the slight start delay18:03
bdpaynewho do we have for the meeting today?18:03
malini1Good morning!18:03
*** welldannit has joined #openstack-meeting18:03
bdpaynemorning malini118:04
*** dani4571 has quit IRC18:04
*** comay has joined #openstack-meeting18:04
bdpayneok, we'll let's get started18:04
bdpayne#topic Previous Action Items18:04
*** openstack changes topic to "Previous Action Items (Meeting topic: OpenStack Security Group)"18:04
bpbBruce and APL here, and Joel coming soon18:04
*** vaml has quit IRC18:05
bdpaynethere have been several action items in recent weeks, let's review those18:05
malini1bdpayne did you still need a tacker for creating the security slide set based on book18:05
bdpayneyes, that would be great18:05
bdpayneyou interested?18:05
malini1I will make time next week for it then18:06
*** sarob has quit IRC18:06
bdpaynegreat, thanks18:06
malini1:)18:06
*** mlavalle has left #openstack-meeting18:06
bdpayne#action malini1 to make an initial OSSG slide deck18:06
bdpaynebasing it on the book is a good start, and I think there were some other ideas in that email thread18:06
malini1will grab them from email thread18:06
bdpaynelooks like some of the other action items were on my plate, so I'll report back here18:07
bdpayneRe OSSG logo18:07
bdpaynemalini1 got some initial ideas out from someone at Intel18:07
bdpaynenow we're looking for someone to do the final graphics work18:07
bdpayneI'm checking with someone18:07
*** vaml has joined #openstack-meeting18:07
bdpayneand Rob is checking with someone at HP as well18:07
bdpayneso hopefully we'll get that wrapped up soon18:08
eloHi. Eric here...18:08
bdpaynemy other action item was to put together a wiki page for getting people started with ossg18:08
bdpaynehere's my work on that18:08
bdpaynehttps://docs.google.com/document/d/1TmygsnqU2MeHMYf_mqIV_dZpDaeLEzR7mGSE9n9SWKk/edit?usp=sharing18:08
bdpayneI wanted to get some other eyes on it before posting to the wiki18:09
*** joel-coffman has joined #openstack-meeting18:09
bdpaynefeel free to comment / edit / etc to improve that writeup18:09
bdpayneperhaps we could take a minute to look over and see if there's any high level comments at this time18:10
* bdpayne will wait for a minute or two18:10
malini1Looks good -- getting involved18:10
*** SumitNaiksatam has quit IRC18:11
elochecking now18:12
*** burt has joined #openstack-meeting18:12
bpblooks reasonable to me also, but I think I'll have a couple of sections to add18:12
bdpayneok, sounds good18:13
bdpaynebpb what sections do you have in mind?18:13
bdpayneI think the more ways we can find for people to help the better18:13
elolooks good at the high level..18:13
joel-coffmanI think it looks good18:14
*** danwent has joined #openstack-meeting18:14
bpbbdpayne: Maybe some references to the security guide, in terms of mapping security controls.18:14
bdpayneahh, so listing specific additions that people could make to the security guide?18:14
*** krtaylor has joined #openstack-meeting18:15
*** ruhe has joined #openstack-meeting18:15
bdpaynewell, we can take this offline18:16
bpbbdpayne:  Yes, but also to use the security guide outline as a reference to point to OpenStack services18:17
bdpaynefor everyone, please let me know if you have any more specific comments, you can email me or just start a thread in the openstack-security mailing list18:17
bdpayne#topic OSSNs18:17
*** lexinator has quit IRC18:17
*** openstack changes topic to "OSSNs (Meeting topic: OpenStack Security Group)"18:17
bdpayneok18:17
bdpayneSo we still have several OSSNs that are up for review18:17
bdpaynehttps://bugs.launchpad.net/ossn18:17
*** troytoman is now known as troytoman-away18:17
bdpayneeyes are certainly welcome there18:18
*** SumitNaiksatam has joined #openstack-meeting18:18
*** SumitNaiksatam has quit IRC18:18
bdpayneI'm not sure what Rob's timeline is for getting those out, but I'm guessing somewhat soon18:18
bdpayne#topic Other Discussion18:19
*** openstack changes topic to "Other Discussion (Meeting topic: OpenStack Security Group)"18:19
malini1i picked up one on https keystone18:19
bdpayneWhat other items would people like to discuss today?18:19
malini1if we have a few minutes, may i ask about "interest" in geo-tagging18:19
bdpaynejoel-coffman I was able to get Vish to review your vol encryption work, hopefully that was helpful18:20
*** lexinator has joined #openstack-meeting18:20
malini1are their customers out there who want to a particular geo to run their VMs and storage18:20
*** alexb_ has joined #openstack-meeting18:20
*** HenryG has joined #openstack-meeting18:20
bdpayneyou mean availability zones?18:20
joel-coffmanyes, thanks so much!!!18:21
malini1:)I knew it was you bdpayne! thanks for getting Vish involved and congratulations joel on that +1 !!18:21
bdpayneor is this some kind of provable gps coords for a resource?18:21
bdpaynejoel-coffman excellent18:21
malini1not really availability zones (that could be both in the same building but on a difgferent power strip)18:21
joel-coffmanmalini1: do you have a link to a blueprint, etc.?18:21
malini1this is more like India/China/USA/Canada type of stuff, for example in CA versusi new hampshire to avoid some sales tax even18:22
malini1not yet written it18:22
*** kmartin has joined #openstack-meeting18:22
joel-coffmanoh, okay18:22
malini1still a bunch of jumbled ideas in my head, the crux being to say a host is in a geo need GPS, with any certificate18:22
bdpayneso provable location?18:23
malini1attached to machine, you can claim it is at X,Y, Z and then move to P,Q,R18:23
*** otherwiseguy has joined #openstack-meeting18:23
*** Mandell has quit IRC18:23
malini1IP based location can happen, 90% accurate, country level granualrity pretty accurate18:23
bdpaynesure18:23
bdpaynebut not perfect18:23
malini1bdpayne, exactly provable location18:23
bdpayneok, yeah, makes sense18:23
*** spzala has joined #openstack-meeting18:23
malini1have any of yourun into customers who want it?18:24
bdpaynethe details would be interesting, but it seems useful18:24
bdpaynenot specifically at my end18:24
*** alexb_ has quit IRC18:25
bdpaynemalini1 any references describing how this would work?18:26
joel-coffmanseems like it could be useful for compliance in certain industries18:26
joel-coffmanbut that's outside my expertise (at least at the moment)18:26
malini1for complaince need provabale, but it we trust the cloud provider, "aggregates" in openstack are adequate to indicate geo18:26
bpbmalini1:  I've heard that some networking components include a GPS reciever, but I haven't verified this.18:27
malini1bpb -- that is an nice  idea -- could be used for provable, would you please send me more info if you find18:28
* bdpayne is now curious18:28
eloJust catching up on thread. I've not heard this from any of our customers that we are involved with at this point.18:28
*** alexb_ has joined #openstack-meeting18:28
bdpaynefrom my end, one big win of a gps receiver would be to have a reliable external time source18:28
bdpayne:-)18:28
malini1bdpayne -- how is that different from NTP? GPS also needs to contact other machines, but you get time and location, 2 for 118:29
bpbmalini1: I'll see if I can find info on this18:30
*** kevinconway has joined #openstack-meeting18:30
bdpaynentp requires connectivity to an ntp server18:30
malini1one of the arguments i have heard for GPS is that data centers hosting compute hosts may be in a bnunker somewhere, unable to grab a GPS dsignal18:30
bdpayneseems like that's an argument against gps18:30
bdpayneok, looks like we're over on time18:31
bdpaynewe can continue this one on the mailing list18:31
bdpaynethanks everyone, see you next week18:31
malini1byeee18:31
joel-coffmanthanks18:31
bdpayne#endmeeting18:31
*** lblanchard has joined #openstack-meeting18:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:31
openstackMeeting ended Thu Aug 15 18:31:37 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-08-15-18.03.html18:31
bpbthanks18:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-08-15-18.03.txt18:31
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-08-15-18.03.log.html18:31
*** joel-coffman has quit IRC18:33
*** alexb_ has quit IRC18:34
*** rnirmal has quit IRC18:35
*** adjohn has quit IRC18:37
*** lblanchard has quit IRC18:38
*** radez_g0n3 is now known as radez18:40
*** vaml has quit IRC18:41
*** bpb has quit IRC18:46
*** novas0x2a|laptop has joined #openstack-meeting18:50
*** rods has quit IRC18:51
*** gokrokve_ has joined #openstack-meeting18:51
*** rnirmal has joined #openstack-meeting18:52
*** lblanchard has joined #openstack-meeting18:52
*** jmontemayor has joined #openstack-meeting18:55
*** herndon has joined #openstack-meeting18:55
*** galstrom_zzz is now known as galstrom18:55
*** salv-orlando has joined #openstack-meeting18:55
*** troytoman-away is now known as troytoman18:57
*** sushils has quit IRC18:59
*** lpabon has joined #openstack-meeting18:59
*** lexinator has quit IRC19:00
*** lpabon has quit IRC19:00
*** numero8 has joined #openstack-meeting19:02
*** jecarey has quit IRC19:02
*** lexinator has joined #openstack-meeting19:02
*** jecarey has joined #openstack-meeting19:03
*** lblanchard1 has joined #openstack-meeting19:03
*** lblanchard has quit IRC19:05
*** lexinator has quit IRC19:11
*** sarob has joined #openstack-meeting19:12
*** anniec has joined #openstack-meeting19:13
*** lexinator has joined #openstack-meeting19:14
*** eharney has joined #openstack-meeting19:14
*** eharney has quit IRC19:14
*** eharney has joined #openstack-meeting19:14
*** vipul is now known as vipul-away19:14
*** markpeek has quit IRC19:15
*** sarob has quit IRC19:17
*** markpeek has joined #openstack-meeting19:18
*** colinmcnamara has quit IRC19:19
*** lpabon has joined #openstack-meeting19:20
*** Mandell has joined #openstack-meeting19:21
*** xBsd has quit IRC19:22
*** macjack has quit IRC19:23
*** vipul-away is now known as vipul19:27
*** benl has joined #openstack-meeting19:28
*** jlucci has joined #openstack-meeting19:32
*** hartsocks1 has joined #openstack-meeting19:39
*** hartsocks has quit IRC19:39
*** xBsd has joined #openstack-meeting19:42
*** lpabon has quit IRC19:42
*** troytoman is now known as troytoman-away19:43
*** hartsocks1 has quit IRC19:43
*** adjohn has joined #openstack-meeting19:48
*** ruhe has quit IRC19:49
*** alexpilotti has joined #openstack-meeting19:49
*** zhiyan has joined #openstack-meeting19:50
*** zhiyan has left #openstack-meeting19:50
*** ajiang has joined #openstack-meeting19:50
*** sushils has joined #openstack-meeting19:52
*** hartsocks has joined #openstack-meeting19:52
*** pcm__ has quit IRC19:52
*** adjohn has quit IRC19:53
*** boris-42 has joined #openstack-meeting19:58
*** anniec has quit IRC20:00
harlowja#startmeeting state-management20:00
openstackMeeting started Thu Aug 15 20:00:10 2013 UTC and is due to finish in 60 minutes.  The chair is harlowja. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: state-management)"20:00
openstackThe meeting name has been set to 'state_management'20:00
harlowjawelcome welcome welcome20:00
harlowja#link https://wiki.openstack.org/wiki/Meetings#State_management_team_meeting20:00
kebrayHello20:01
harlowjahowday20:01
changblhi20:01
harlowjahi20:01
jluccihere - btw20:02
harlowjahey20:02
harlowjathx thx :)20:02
*** lexinator has quit IRC20:03
harlowjaso i think there isn't much status things to report since last time but lets see20:03
harlowja#topic status20:03
*** openstack changes topic to "status (Meeting topic: state-management)"20:03
harlowjawhats everyone doing????20:03
* harlowja been reworking some of kevins persistence code20:03
harlowjaand helping make sure the cinder crowd understands the taskflow code there20:04
harlowja*answering questions and such*20:04
harlowja*or bugs that i might of caused, not to many so far20:04
* kebray evangelizing TaskFlow with other developers at Rackspace. This will make jlucci happy: but, found out another internal team wants to move to TaskFlow, specifically _because_ of celery backed distributed state!20:04
jlucciThat's awesome!20:04
harlowjawoot !20:04
jlucciCan I ask what team? Or is that internal stuffs?20:04
*** lexinator has joined #openstack-meeting20:05
harlowjakebray thx for helping evalgelize, i think its not always the most fun activity :)20:06
kebraya managed cloud team… they want to move to Heat to replace something internal.  But, they have larger Task Orchestration (which will need to be baked around Heat).  They switched their current solution to celery because it was the only thing they could find that solved their specific scale challenges.20:06
kebrayanyway… we can take the details offline.20:07
harlowjainterestingggg20:07
jlucciStill awesome. (:20:07
harlowja:)20:07
jlucciSo, I've been working on fixing up some distributed pep8 related stuff20:08
kebrayharlowja:  I've given a tech talk at 3 of our 5 software development offices in the past two months, and each talk I evangelized both Heat and TaskFlow.  About 125 product folks at Rackspace in total were in attendance across the 3 talks.20:08
harlowjakebray wow20:08
harlowjacool20:08
harlowjajlucci mr.jenkins will be very happy with u20:08
jlucciYeah - still have to fix a couple import things, but that should be done today20:08
jlucciMostly been working on trove related stuff though20:08
jlucciSpinning up a _working_ openstack environment20:09
*** sandywalsh has quit IRC20:09
harlowjacool20:09
*** adjohn has joined #openstack-meeting20:09
jlucciRunning trove test cases, starting to put some taskflow codes in there20:09
jluccietc, etc20:09
harlowjaya, its interesting to see how it feels to use it20:09
kebrayharlowja, is it a good thing I hope?  :-/20:09
harlowjaeach different project is also at a different place where they coudl use it in different ways20:09
harlowjakebray i think its good of course, ha20:10
harlowjabut we are all slightly biased :-P20:10
harlowja*just slightly*20:10
harlowjachangbl any think u've been looking20:11
harlowja*anything20:11
harlowjai'm hoping these persistence adjustments will make it easier to connect zookeepr in20:11
changblharlowja, sorry I did not do much, quite a hectic week. My intern is wrapping up his work here. I will try to do more by next meeting20:11
harlowjanp :)20:11
harlowjai know how it goes, ha20:12
harlowjai think the one at y! is heading out shortly to20:12
harlowjaok, well lets see if we have any topics to talk about for blocks/engines/stuff there20:13
harlowjaif not i think a writeup is underway by the people working on it20:13
harlowja#topic block-engines-flows20:13
*** openstack changes topic to "block-engines-flows (Meeting topic: state-management)"20:13
*** ayoung has quit IRC20:13
harlowjaso overall i think there is alot of neat work being done here to help streamline the various usage of tasks20:13
kebrayharlowja that would be good… I had jlucci explain blocks to me… but, I was struggling to understand… it sounded like another arbitrary primitive.20:14
harlowjaya, we want to make sure that its not a struggle to understand, that will be key20:14
harlowjathe more struggle, the harder it will be for others to see it also20:14
kebrayAnd, once you start mixing flow types with execution engines, things get odd.20:14
jlucciI think if we ended up using blocks, they'd really just be replacing patterns20:14
*** melnikov has joined #openstack-meeting20:14
harlowjapossibly, and engines would replace the internals of what runs the patterns20:15
*** henrynash has joined #openstack-meeting20:15
kebrayah, patterns I meant… things get weird when you start mixing patterns with execution engines.20:15
jlucciOh, yeah. That was another thing -20:15
harlowjamelnikov yt20:15
jlucciI'm 100% in support of separating engines and patterns20:15
jlucciBut, after thinking stuff over more, I really don't think we should mix patterns and engines20:15
jlucciI think a linear engine should only run a linear flow, etc, etc20:15
melnikovyes, i am, hi there20:16
*** numero8 has quit IRC20:16
kebrayIf the user doesn't have a reasonable assurance that a pattern will execute in particular way, then the pattern becomes meaningless other than it's a way to hook things up.20:16
jlucciRight, it seems that if we allow distributed to run on linear, or something similar, we negate the need for patterns at all20:16
jlucciThe only thing that remains relevant are the relations20:16
melnikovjlucci, have you seen http://paste.openstack.org/show/44004/?20:16
jluccirelations between tasks *20:16
harlowjai think melnikov  example there would have seperate engines20:17
melnikovyes, but thay both run linear flow linearly20:17
melnikovand parallel flows in parallel20:17
melnikovand so on20:17
kebrayseparate engines or not, I think one needs a reasonable assurance that a pattern will execute in a particular way.. otherwise what jlucci said is right, all that matters is relations and patterns/blocks become irrelevant.20:18
jlucciOn the flip side as well, if an engine can run any pattern, why make more than one engine?20:18
jlucciWhy not have only one engine run all the patterns20:19
kebraySo, both he linear engine and the distributed engine could execute a linear flow… but, they both should execute it linearly!!20:19
jlucci*in regards to 44004*20:19
melnikovwe may have single-threaded, or multi-threaded, or distributed engines20:19
harlowjakebray i think thats a must, those kind of guarantees we can't ever break20:19
melnikovand choose which is suited best for particular setup20:19
kebraygood point jlucci… only reason to have more engines is one could be easier to setup, but not scale as well… another could require a lot more configuration and setup, but run at service provider scale.20:19
*** flaper87|afk is now known as flaper8720:19
* harlowja this engine stuff is really neat, ha20:20
*** sandywalsh has joined #openstack-meeting20:20
jlucciYeah, there's a ton of possibilities with it - just want to make sure we pick the least complicated one. heh20:20
kebrayso, more than one engine doesn't bother me, as long as the TaskFlow user can reasonably expect a pattern to execute in a way that matches that pattern.20:20
melnikovyes, all engines should provide some common high-level guarantees20:21
melnikovlike, that linear flow is linear20:21
kebraySome patterns have execution benefits over other patterns depending on the flow you want.20:21
kebray+1 melnikov20:22
harlowjaagreed, although i also think that jlucci is right, it will be neat to see how the balance works out20:22
kebrayanyway, write up on blocks would be good… I'm struggling to see where it fits into all this about patterns and engines.20:22
harlowjakebray another thing that i think would be useful, maybe if we can get zane b. involved in some of these ideas that would be pretty benefical20:23
harlowjaeven as just a person that offers some experience from heat20:23
*** alexb_ has joined #openstack-meeting20:23
kebrayagreed harlowja.  Maybe you can convince him to participate in TaskFlow at the summit!   It doesn't look like I'm going to be able to go :-(20:23
harlowjawhatttt20:23
harlowja:(20:23
harlowjado u want me to register that i'm taking a baby with me20:24
*** lpabon has joined #openstack-meeting20:24
harlowjaand u can be da baby20:24
jluccilololol20:24
jlucciDo that20:24
jlucciI want that to happen20:24
harlowjalol20:24
hemnaheh20:24
kebrayoh my.. not where I expected the conversation to go.20:24
hemnaget a room20:25
* kebray asks, so where were we on the agenda?20:25
harlowjalol20:25
hemna:P20:25
changbl:)20:25
harlowjaso melnikov  i think just some writing up would really help20:25
harlowjawhich i think u are doing anyway20:25
*** benl has quit IRC20:25
jluccilol20:25
harlowjai'll see if maybe i can ask zane to look at it and see what he thinks20:26
harlowjabe nice to have said input, since heat has similar components20:26
*** mrodden has quit IRC20:26
kebrayagreed.20:26
harlowja#action melnikov  send out some docs to email list, or IRC, or both20:27
harlowjaeven rough ideas are fine, the engine/blocks/subflows all that are still a WIP i know :)20:27
melnikovharlowja, yes, i was hoping to get something written by the meeting, but did not have enough time20:27
harlowjanp20:28
harlowjathx melnikov20:28
harlowjacool, so lets continue that discussion and see what happens20:29
harlowjanext up any cinder/heat/nova/trove/... topics/discussion20:29
harlowja#topic integration20:29
*** openstack changes topic to "integration (Meeting topic: state-management)"20:29
jlucciTrove stuff is looking pretty promising20:29
kebrayCinder integration for H release is done-done, except answering questions and any bug fixes, correct?   That is SUPER cool btw.20:30
harlowjaso thanks to hemna and jgriffith it has been realitively painless, only a few whitespace issues i caused and maybe a little more20:30
harlowjadone-done, never done-done20:30
hemna:)20:30
harlowjaalways more to do, ha20:30
hemnait's never 'done'20:30
harlowjaits a continuation of space and time20:30
harlowjaha20:30
harlowjaits a start really, i'm gonna help split up the file that i created into pieces, that will help20:31
harlowjaand continue questions, bug fixes, what the heck is this questions20:31
harlowjaand as taskflow gets more features, they should be easily added in20:31
hemnaso what's next for taskflow + cinder?20:31
harlowjaand world peace at the end20:31
hemnataskflow shipped...next up, world peace!20:32
harlowjaha20:32
harlowjaso hemna i'm gonna spend a little time to split up that file with all the tasks, that is part of the plan for me soon20:32
*** IlyaE has quit IRC20:32
harlowjathen i think anastsia might be working on another flow there20:32
hemnaok20:32
hemnathere was the debug wrapper thing as well, which could be helpful as a general purpose thing20:33
harlowjayup20:33
harlowjathat exposes the functionality to do persistence, or event recording, or ...20:33
harlowja*or its one of the ways to expose it20:33
*** gyee has joined #openstack-meeting20:33
harlowjaespecially if u imagine all of cinder using taskflow, then the debug thing becomes pretty awesome20:34
kebrayharlowja can you comment on TaskFlow in Nova?   Is that a "Start evangelizing at the summit" thing and hope a blueprint gets accepted for I release?20:34
harlowjakebray hmmmm, i think there will be something going on there, either me, possibly NTT, possibly others, still underflux20:34
harlowjai hope to re-enter that area and see what happens20:35
kebrayTrove isn't core… so, what's our next core target for integration?20:35
hemnasoren, should we in cinder start to try to implement other capabilities w/ taskflow ?20:35
hemnaerr s/soren/so20:35
*** lblanchard1 is now known as lblanchard20:36
harlowjahemna i think that would be great, of course, but depends on timing/workflows of everyone i think20:36
*** dprince has quit IRC20:36
kebrayhenna The more use of Taskflow the better.. but, as harlowja says, we're biased :-)20:36
harlowjakebray i think it will be nova, glance did mention that they might have a feature there also20:36
hemnaso we just have volume/clone create today right ?20:36
harlowjaright, the main create functionality20:37
hemnamaybe we should create a wiki or something that describes what's left to convert to taskflow20:37
hemnafor cinder20:37
harlowjaagreed20:37
hemnajust want to have it documented20:37
harlowjasure20:37
kebrayI'm also prodding jlucci after trove integration to work on a PoC for Heat.20:37
hemnathen we can see if we can get folks to pick up the remaining for I20:37
*** spenceratx has joined #openstack-meeting20:37
harlowjahemna soudns good, let me start one20:38
hemnaI'd like to see all the main cinder capabilities moved to taskflow, or at least as much as we can in I20:38
hemnaok20:38
harlowja#action harlowja start cinder flow wiki20:38
harlowjaall of cinder capabilities??20:38
harlowjawow20:38
harlowja:)20:38
*** mrodden has joined #openstack-meeting20:38
harlowjahow far do u want to go is a good question :)20:39
harlowjaif u look at the distributed work from jlucci it starts to become the thing that could power cinder20:39
harlowjathen cinder would no longer have an RPC system, but this is likely extremly ambitious20:39
hemnawell the end game for me is to get20:40
hemnacinder into a safe restart capability20:40
hemnaso that if someone tells cinder to shutdown, or it dies20:40
hemnathat we can get cinder to pick up where it left off20:40
hemnaif possible20:40
hemnaIMHO that's the wholy grail for taskflow20:40
harlowjasure, so thats a good goal to, and one that we are aiming for also20:40
jlucciheeh20:40
jlucciI feel like this is the point where I jump up and start preaching distributed20:41
harlowjalol20:41
hemnahush20:41
hemna:P20:41
jlucci:P20:41
*** spzala has quit IRC20:41
harlowjahaha, so i think hemna your case will def be there pretty soon i think20:41
kebrayjlucci, you're gonna get a following yet.. I just know it.20:41
hemnadistributed HA would be nice20:42
hemnaand taskflow helps us get there I believe20:42
jlucciYeah, as of now, distributed provides the "fix this thing and let the workflow continue on" issue, but is still lacking in the "my box caught fire and I need to resume my flow" issue20:42
*** thang_ has quit IRC20:42
hemnayah20:42
*** sushils has quit IRC20:42
hemnataskflow is a good start to that20:42
hemnaat least we'll know where in the process the box caught fire :)20:43
harlowjaya, there is an interesting area that jlucci i think is uncovering really, if u look at all the openstack projects, they execute tasks via some code, using this RPC thing, then if u look at jlucci distributed stuff and taskflow integration u start to see the same thing20:43
jlucciYes. lol We're trying to get all the persistence stuff in right now - harlowja is doing some fixes on that20:43
hemnasome use cases are going to be difficult to reconcile moving to other machines though20:44
hemnain the case of cinder's copy volume to image20:44
hemnathe cinder node mounts the backend volume20:45
hemnaand starts the copy20:45
harlowjasure, i'm pretty sure jlucci has a solution there, haha, like celery has to have it i wuld think20:45
hemnathat mounting would have to be reissued on the next box if the primary burned20:45
*** vipul is now known as vipul-away20:45
*** sushils has joined #openstack-meeting20:45
hemnain this case the process would need to be started over from the beginning I thinks20:45
jlucciAnd that's something taskflow will be able to provide20:46
*** lblanchard has quit IRC20:46
*** bpb has joined #openstack-meeting20:46
harlowjaor from the last checkpoint, which is something we've been figuring out how to semantically support (And actually do)20:46
*** colinmcnamara has joined #openstack-meeting20:46
jlucciI want to see the option of giving the user a "flow failed action"20:46
hemnaah yah, checkpointing.  nice20:46
hemnayah that'd help for sure20:46
harlowjaya, melnikov i think has been thinking about this more than me recently, but def its wanted20:46
hemnacompletely awesome20:47
harlowjathx hemna  :)20:47
*** novas0x2a|laptop has quit IRC20:48
harlowjaalright, just gonna open it up for anything else to discuss since it seems like we are done for now talking about how integration is going20:48
harlowja#topic open-discuss20:48
*** openstack changes topic to "open-discuss (Meeting topic: state-management)"20:48
*** llu-laptop has joined #openstack-meeting20:48
*** novas0x2a|laptop has joined #openstack-meeting20:48
harlowjaany interesting question, that i think we never quite finished is the question releated to persistence20:49
harlowjaand might still be an open question until its a little more flushed out20:49
harlowjawe have some basic concept/idea of what to store, which is great, ha20:50
harlowjamy question though is if there should be a limit to how long we store it20:50
jlucciWhen I first started taskflow stuffs, I had an idea that we sort of "purged as we went along"20:51
melnikovi think checkpoints might provide good answer20:51
jlucciI'm not sure if it's feasible, but the idea is that once you get to a checkpoint,20:51
jlucciyou can sort of consolidate the data up to that point20:51
jlucciYou don't have to keep track of the states of any previous taks or anything like that20:51
harlowjaseems reasonable20:51
jlucciI just worry that someone's gotten to a checkpoint, and wants to roll back to a previous one20:52
jlucciWe have to make sure we store enough data to make that possible20:52
jlucciBut nothing more20:52
jlucciMight be something we solve when we actually start implementing checkpoints though20:52
*** lexinator has quit IRC20:53
harlowjasure, i could see there be an interesting case for checkpoints, for taskflow internal usage20:53
harlowjaand still providing the abilitiy to attach lisenters to a flow so that say cinder can log all the things happening (or store it in there own little api)20:54
harlowjaseems like there is internal storage, which involves checkpoints and state/task/flow information, and then letting say cinder see what is happening in taskflow, and then say cinder can store that and tell people about whats happening if they want20:55
harlowjamake sense?20:55
harlowjaif not thats ok, just brainstorming, ha20:56
*** benl_ has joined #openstack-meeting20:56
jlucciI think so20:56
*** vipul-away is now known as vipul20:56
*** yhe has joined #openstack-meeting20:56
jlucciThis is in line with the restricting what can be accessed from the DB type stuff we talked about yesterday?20:56
harlowjahmmmm, possibly20:57
* harlowja can't remember, ha20:57
harlowjaanyways, we can continue later in #openstack-state-management20:58
harlowjaall are welcome to bug us :)20:58
jlucciSounds good20:58
jlucci:D20:58
harlowjathx again everyone :)20:58
harlowja#endmeeting20:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:58
openstackMeeting ended Thu Aug 15 20:58:28 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/state_management/2013/state_management.2013-08-15-20.00.html20:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/state_management/2013/state_management.2013-08-15-20.00.txt20:58
openstackLog:            http://eavesdrop.openstack.org/meetings/state_management/2013/state_management.2013-08-15-20.00.log.html20:58
*** melnikov has left #openstack-meeting20:59
russellb#startmeeting nova21:00
openstackMeeting started Thu Aug 15 21:00:48 2013 UTC and is due to finish in 60 minutes.  The chair is russellb. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: nova)"21:00
openstackThe meeting name has been set to 'nova'21:00
russellbHello, everyone!21:00
hemnahey21:01
mroddenhi21:01
russellb#link https://wiki.openstack.org/wiki/Meetings/Nova21:01
n0anoo/21:01
NobodyCamo/21:01
hartsockso/21:01
russellbannegentle: around?21:01
alaskihi21:01
cyeohHi21:01
dansmitho/21:01
annegentleo/21:01
russellbgreat21:01
llu-laptopo/21:01
russellb#topic compute admin guide21:01
*** openstack changes topic to "compute admin guide (Meeting topic: nova)"21:01
*** mriedem has joined #openstack-meeting21:01
annegentlewoo I'm up21:01
mriedemhi21:01
*** nati_uen_ has joined #openstack-meeting21:01
russellbannegentle: yep!  what's up?21:01
annegentleso the guide mostly known as the Compute Administration Guide will be likely removed as that title, and distributed to the new Configuration Reference, User Guide, and Operations Guide21:02
annegentleit got really massive, bloated, etc. and we're parting it out.21:02
*** Mr_T has joined #openstack-meeting21:02
*** spenceratx_ has joined #openstack-meeting21:02
*** cwolferh has joined #openstack-meeting21:02
russellbso, restructuring based on target audience?21:02
annegentleI want to make sure you're all good with that, and that I'm not missing some reason not to do that.21:02
russellbmostly anyway21:03
annegentleyes, the audience and their tasks. We find that "admin" and "operator" are mostly synonymous.21:03
* russellb nods21:03
*** jasondotstar has quit IRC21:03
annegentleit may mean some "where'd that page go?" at release time, but I'm hopeful we'll get htat sorted out.21:03
*** spenceratx has quit IRC21:03
*** spenceratx_ is now known as spenceratx21:03
russellbcould just be replaced with a page for a while explaining the split?21:04
*** benl_ has quit IRC21:04
annegentlealso, about 1/4th of docs visitors go to /trunk/, so we'll be working towards only about 2 guides going under the docs.openstack.org/havana umbrella21:04
*** nati_ueno has quit IRC21:04
annegentlerussellb: could be, yeah. I think the move towards only 2 documents under a release umbrella and many documents under /current/ or /trunk/ will help people see where the site's going21:05
*** mdurnosvistov_ has joined #openstack-meeting21:05
annegentlewe'll certainly keep an eye out for patches as you near the features freeze, and help you find the right placement21:05
russellbok, well sounds fine to me, and i appreciate the heads up21:05
*** ayoung has joined #openstack-meeting21:05
*** melwitt has joined #openstack-meeting21:05
russellbany questions or concerns from anyone?21:06
russellbor virtual high fives for the docs team?21:06
*** mdurnosvistov_ has quit IRC21:06
annegentleheh21:06
* dansmith high-fives annashen 21:06
dansmithdammit21:06
* dansmith high-fives annegentle 21:06
dansmithtab fail21:06
annegentleheh heh21:06
*** thomasbiege has joined #openstack-meeting21:06
* annegentle lobs an 'e' to dansmith21:06
dansmithyeah, I suck21:06
russellbi'm sure annashen appreciated the high five, too.21:07
dansmithheh21:07
annegentleI really think the amount of content we have is astonishing, but it also concerns me that it's outdated all the time :)21:07
annegentleso be on the lookout for DocImpact bugs you can pick up because you know the code21:07
annegentlethat's all I got! We're ready for the onslaught :)21:07
*** thomasbiege has quit IRC21:07
russellbyeah ... i wish we did a better job helping keep it up to date, beyond just tagging things with DocImpact21:07
russellbbut i haven't come up with any brilliant suggestions21:08
russellbobviously, getting in there and writing stuff would help :)21:08
russellbbut how to generally encourage that kind of thing as features come in21:08
russellbsomething to think about some more21:08
comstudohmtg21:08
russellbcomstud: way to announce how late you are :-p21:09
annegentleyeah definitely just get it out of your brain onto text of any form21:09
annegentleheh comstud21:09
timello(late) o/21:09
harlowja(late 2) \o21:09
annegentlethe docs team can take it the rest of the way21:09
russellbannegentle: yeah, maybe we'd have better luck just ensuring there's a wiki page21:09
*** luz has quit IRC21:09
russellbensuring the blueprint includes or links to some form of user doc content before the feature patch is merged ... something like that21:10
*** melwitt has quit IRC21:10
annegentlerussellb: we read the blueprint pages as much as possible, those are good places to braindump21:10
russellbyeah, i just don't think we (in nova anyway) really put as much efffort into ensuring the content is there by the end of it21:10
russellbsometimes the user details aren't finalized until they very end of development, and the blueprint content is usually written much earlier21:10
russellbi know you know all of this well :)21:11
annegentlerussellb: we have really good tagging of our docimpact stuff and automated much of it21:11
russellbjust acknowledging that we could and should do better i guess21:11
annegentlerussellb: and, we automated a bunch of config info21:11
russellbnice21:11
*** melwitt has joined #openstack-meeting21:11
annegentlesure, we keep eating the elephant a bite at a time21:11
russellbha21:11
russellbfair enough21:11
russellbanything else?21:11
annegentlethat's it21:11
russellbcool, thanks!21:11
*** kebray has quit IRC21:12
russellb#topic havana-3 status21:12
*** openstack changes topic to "havana-3 status (Meeting topic: nova)"21:12
russellb#link https://launchpad.net/nova/+milestone/havana-321:12
russellbdeadline to have patches *proposed* is EOD Wednesday, August 2121:12
russellbless than 1 week away21:12
*** kebray has joined #openstack-meeting21:12
russellbwe're actually in pretty good shape, lots of stuff is already up for review21:12
russellbthen it'll be an insane review rush up to the feature freeze ...21:13
russellbso with all that said ... let's dive into specific blueprints21:13
russellbany specific ones folks here would like to cover?21:13
russellbanything on this list that people know won't make it and should be deferred?21:13
russellbvishy started a thread about his live snapshot work: http://lists.openstack.org/pipermail/openstack-dev/2013-August/013688.html21:14
russellb#link http://lists.openstack.org/pipermail/openstack-dev/2013-August/013688.html21:14
russellbwe talked about it last week21:14
russellblooks like he's trying to build some consensus around whether that will go in or not21:15
russellbso if you have an interest in the feature, please provide input on that thread21:15
russellbno blueprints anyone wants to cover?  everyone heads down in panic coding mode?  :)21:15
timellohehe21:15
dansmithrussellb: yes21:16
russellbtimello: how's your cold migrations migration coming along?21:16
harlowjaheads down, trying not to panic, ha21:16
mriedemrussellb: this needs review: https://blueprints.launchpad.net/nova/+spec/powervm-configdrive21:16
yjiang5russellb: can low priority one give information?21:16
*** sarob has joined #openstack-meeting21:16
mriedemrussellb: does the blueprint owner just change status to 'needs review'?21:16
russellbmriedem: yeah, or I (or anyone in nova-drivers) can21:17
mriedemok21:17
russellbupdated21:17
russellbyjiang5: sure21:17
timellorussellb: we got some important changes merged, I'm working on in the final step which is move things that are in compute.manager to conductor. Everything from the scheduler have been moved already21:17
timellothere is a WIP for it, hopefully today I'll submit the ready for review patch.21:17
russellbtimello: nice, sounds good21:18
yjiang5timello: possibly we can have some changes to the resource tracker in I release .21:18
timelloyjiang5: yes, plus that...21:18
*** sarob has quit IRC21:19
*** sarob has joined #openstack-meeting21:19
russellbalright, moving on for now then21:19
russellb#topic subteam reports21:19
*** openstack changes topic to "subteam reports (Meeting topic: nova)"21:19
russellbany subteams want to provide an update?21:19
harlowja\0/21:19
*** markwash has quit IRC21:19
hartsockso/21:20
russellbhartsocks: go ahead21:20
hartsocksfolks are heads down the next two weeks… but...21:21
hartsocksWe're tagging bugs with vmware-co-preferred to mark bug fixes or distro people to pull/pay attention to.21:21
russellbvmware-co-preferred?21:21
russellbwhat does that mean?21:21
hartsocksso...21:21
mroddeni was curious about that as well...21:21
hartsocksvmware-co <- vmware company21:21
hartsockspreferred <- fine wine.21:21
russellbok, so, i don't like that.21:21
dansmithyeah.21:21
russellblaunchpad doesn't prevent people from putting whatever tags you want, but, i don't like it21:21
russellbwe don't have redhat-preferred, ibm-preferred, rackpsace-preferred, hp-preferred, etc etc21:22
jog0russellb: there is precident with te cannonistack tag21:22
russellband i don't like that either21:22
hartsocksWell… the idea is we wanted to find a way to mark publicly that these were patches that distro people should look to.21:22
jog0russellb: fare enough, what do you propose instead21:22
hartsocksand… we got the idea from cannonistack.21:22
russellbthat kind of thing is something for your company to figure out using your own system(s)21:22
russellbfor red hat, we have our own public tracker21:23
russellbfor canonical, they have other projects in launchpad21:23
*** trey_h has joined #openstack-meeting21:23
russellbbut using the upstream bugs is not appropriate IMO21:23
*** flaper87 is now known as flaper87|afk21:23
hartsocksI wanted to do this in a way that was public and upstream.21:23
*** sarob has quit IRC21:23
russellbpublic is good, but it belongs on a vmware tracker of some sort21:23
hartsocksThe idea is, I don't want to get into the business of maintaining these lists outside of the public arena.21:23
mroddenwould it be possible to create another launchpad project to use to track upstream project bugs...21:24
hartsocksI'm open to suggestions.21:25
russellbnot using the upstream project bugs for noting your business priorities21:25
russellbis my suggestion :)21:25
hartsocksHopefully we would only have to do this for a little while.21:25
russellbi'm not sure how else to express it21:25
hartsocksWell, the list comes from use-cases that don't flow through without the particular bug-fix.21:25
russellbbut i'm basically -2 on it21:26
clarkbcould you create a new LP org, add the bugs to that org then remove them from nova?21:26
clarkbthen you don't even need to copy pasta21:26
jog0what to do about https://bugs.launchpad.net/nova/+bugs?field.tag=canonistack21:26
hartsocksThese are nova bugs.21:26
russellbjog0: kill the tag preferably21:27
jog0hartsocks: there may be a way to just use the launchpad API to make a list ala rechecks21:27
*** spzala has joined #openstack-meeting21:27
jog0(http://status.openstack.org/rechecks/)21:27
russellbhttps://bugs.launchpad.net/nova/+bugs?field.tag=vmware21:27
russellbtagging something as affecting the driver is perfectly appropriate21:27
hartsocksI'll take out the tags by next weeks' meeting. But we'll need to figure out what else to do.21:28
dansmithhartsocks: presumably anything tagged as vmware-related and high priority == your special list anyway, right?21:28
*** branen_ has joined #openstack-meeting21:28
jog0russellb: this may be worth a ML post to notify canonistack folks as well21:28
russellbsure, or just a more direct ping21:28
russellbi wouldn't kill it without a heads up21:28
russellbso they can make those notes elsewhere21:28
hartsocksdansmith: yes, but… there are fixes we've identified as being necessary to completing a "workflow"21:29
dansmithhartsocks: so if I could offer some experience,21:30
dansmithfrom an org that has done this for a very long time,21:30
hartsocksdansmith: we don't want to have a separate repo or anything for that, just let folks like canonical or whom ever know that's somethin for them to look at.21:30
mroddenbugzilla21:30
clarkbhartsocks: what about making the bug affect both orgs?21:30
clarkbhartsocks: you can manage priority and stuff independently21:30
dansmiththis is why you build a tracker to manager your release and your relationship with your vendors, preferably with slick glue to keep it sync'd upstream21:30
russellb#action get rid of all business-priority related tags in launchpad, to kill off this bad precedent21:30
russellb#undo21:30
russellb#action russellb to get rid of all business-priority related tags in launchpad, to kill off this bad precedent21:30
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x2644910>21:30
*** benl has joined #openstack-meeting21:30
hartsocksdansmith: okay, but I was looking for the simplest thing possible.21:30
russellbhartsocks: but this is what every vendor has to do ...21:30
russellbto keep your business stuff separate from the upstream stuff21:31
russellbbecause they're not the same21:31
dansmithhartsocks: I understand your intentions are good, but it's just not the right way21:31
*** sarob has joined #openstack-meeting21:31
*** branen has quit IRC21:31
hartsocksSo we'll have the vmware tags removed by next meeting. Just have to figure out how else to track this w/o hiding it.21:31
hartsocksThat's not even what I *really* wanted to talk about.21:32
mroddenhartsocks: clarkb's suggestion is what i would do21:32
hartsocksmrodden: I like it because it doesn't involve me figuring out how to build something new.21:32
mroddenright21:32
*** sarob has quit IRC21:32
*** fifieldt has joined #openstack-meeting21:32
*** lexinator has joined #openstack-meeting21:33
hartsocksThanks. Glad I mentioned the topic in meeting.21:33
hartsocksWe are tracking these blueprints:21:33
*** sarob has joined #openstack-meeting21:33
hartsocksProposed, code posted, trying to get in good shape for core-reviewers21:33
hartsocks#link https://blueprints.launchpad.net/nova/+spec/multiple-clusters-managed-by-one-service21:33
hartsocks#link https://blueprints.launchpad.net/nova/+spec/vmware-nova-cinder-support21:33
hartsocks#link https://blueprints.launchpad.net/cinder/+spec/vmware-vmdk-cinder-driver21:33
hartsocks#link https://blueprints.launchpad.net/nova/+spec/improve-vmware-disk-usage21:33
hartsocks#link https://blueprints.launchpad.net/nova/+spec/vmware-image-clone-strategy21:33
hartsocksboom.21:33
*** sarob has quit IRC21:33
*** sarob has joined #openstack-meeting21:34
hartsocksThat's what we hope to get into Havana in *priority* order. Note: priority for health of the driver.21:34
hartsocksThat's EOL for me then.21:34
russellbcool, thanks21:34
russellbharlowja: did you want to give an update?21:35
harlowjadef :)21:35
harlowjaso taskflow has gotten initial integration with cinder, yaaaaaa21:35
*** branen_ has quit IRC21:35
russellbcool21:35
harlowjaotherwise mostly heads down, continuing persistence work there and hoping to get into nova soon :)21:35
harlowjapicking up steam i think, but not to much steam since everyone busy in H3+21:36
russellbso a design summit session giving an update on this library and proposed integration with nova may be a good discussion.21:36
harlowjaagreed21:36
*** shanewang has joined #openstack-meeting21:36
russellbanything else?21:36
harlowja#link https://wiki.openstack.org/wiki/TaskFlow/HavanaSummitPresentationAbstract#Speakers21:36
harlowjathat might happen ;)21:36
*** trey_h has quit IRC21:36
harlowjabut a design summit session sounds great to21:36
russellbah ok.21:37
harlowjathats it with me, thx russellb21:37
russellbk, thx21:37
russellbany other subteams?21:37
harlowjanp :)21:37
n0anoscheduler21:37
russellbn0ano: go for it21:37
n0anolong discussion on Boris' suggested scalability changes to the scheduler, no concensus, definitely post-havana, we'll need some sessions at the next summit21:38
*** mriedem has left #openstack-meeting21:38
n0anothat's about it.21:38
russellbyep, sounds good to me21:38
russellbthanks!21:38
russellb#topic open discussion21:38
*** openstack changes topic to "open discussion (Meeting topic: nova)"21:38
russellbanything else from anyone?21:39
jog0not sure where best to throw this out there but  https://bugs.launchpad.net/nova/+bug/121241821:39
*** colinmcnamara has quit IRC21:39
uvirtbotLaunchpad bug 1212418 in nova "SQLAlchemy performs poorly on large result sets" [Undecided,Confirmed]21:39
jog0SQLA's ORM is a no go for scale21:39
jog03 second DB 50 in sqla21:39
russellbouch21:40
melwittI have posted to ML about possible removal of the security_groups extension from v3 api, if anyone has any input.21:40
russellbhow many instances are we talking about for the 2 seconds vs 53 seconds thing?21:40
comstudthat particular case would be better if we didn't join21:40
jog0so we need to sort that out at the summit21:40
comstudor we change what we join21:40
comstudbut in general, the ORM mapping results does suck21:40
jog0russellb: that was for 600k lines I think which will happen at scale for several calls I think21:41
jog0in general we see this overhead on small calls to just the absolute times are not as bad21:41
*** branen has joined #openstack-meeting21:41
russellbso, sounds like we can make it somewhat better21:41
jog0I hope so21:41
russellb... and then there's the plan for a native mysql driver for some critical bits21:41
* russellb looks at comstud 21:41
dansmithhey!21:42
dansmithdon't distract him21:42
dansmithhe has objects work due21:42
*** afazekas is now known as afazekas_zz21:42
jog0russellb: but we can't just depend on that for everything .. postgres folks21:42
russellbjog0: sure, agreed21:42
*** HenryG has quit IRC21:42
russellbjog0: need to make sqla work as best we can21:42
jog0anyway we need a good plan for this  just an FYI21:42
jog0russellb: we can use it without the ORM for some benifits21:42
comstud:)21:42
cyeohmelwitt: it sounds like it can be removed, just need to preserve the instance create part21:42
russellbsecurity group management?  yeah makes sense to me21:43
yjiang5jog0: comstud should we do something in H release for this performance issue? Or wait till summit discussion?21:43
*** gatuus has joined #openstack-meeting21:43
shanewangjog0: will that go before havana? I mean without orm.21:43
*** neelashah has quit IRC21:43
jog0yjiang5: no ORM wait I think21:43
cyeohrussellb: this is associating/disassociating security groups with instances, originally we thought nova had to been in the loop, but it appears not21:43
jog0but somethings can be done now21:44
jog0like https://bugs.launchpad.net/nova/+bug/121242821:44
uvirtbotLaunchpad bug 1212428 in nova "compute_node_get_all slow as molasses" [Undecided,Confirmed]21:44
russellbcyeoh: ack, sounds good then21:44
shanewangjog0: ack21:44
melwittcyeoh: why keep instance create part? since that's also just a neutron update port?21:44
russellbnova creates the port though, right?21:45
shanewangcomstud: is the orm issue a known issue in sqla?21:45
jog0shanewang: also more analysis about solutions is needed for summit21:45
jog0shanewang: yes21:45
jog0we chatted in  the #sqlalchemy room for abit on it21:46
cyeohrussellb: I'm pretty sure you pass the port that nova should use on the instance creation21:46
comstudthere's some benefit in switching some things to use the core API vs the ORM API21:46
*** SumitNaiksatam has joined #openstack-meeting21:46
dansmithcyeoh, russellb: it can go either way21:46
comstudbut ultimately in my testing, both suck compared to a simple native mysqldb implementationn21:46
shanewangjog0: sad to hear that.21:46
dansmiththe port can be created ahead of time or by nova I think21:46
* russellb sometimes laughs to himself that we use a language like Python and then get surprised sometimes with performance issues :-)21:46
melwittrussellb: if a specific port isn't specified in the create request, one will be created by nova21:47
russellbmelwitt: cool21:47
comstudrussellb: IKR21:47
dansmithwait21:47
dansmithPYTHON IS SLOW?!21:47
russellbIKR?21:47
*** colinmcnamara has joined #openstack-meeting21:47
*** markmcclain has quit IRC21:47
* dansmith heads to tweet the news21:47
jog0:-)21:47
russellbbut if there's a clear usage issue we can change to get a significant performance improvement in a case like this, we should do it21:47
russellbsounds like that may be the case here21:48
dansmithyeah21:48
alaskiI'd like to discuss https://bugs.launchpad.net/nova/+bug/1212798 if there's time21:48
uvirtbotLaunchpad bug 1212798 in nova "quota_usages not decremented properly after per user quota migration" [Undecided,New]21:48
llu-laptophello, looking forward to reviews of this bp https://blueprints.launchpad.net/nova/+spec/utilization-aware-scheduling, it's about the generic framework to have compute manager reporting various metrics for scheduling purpose. Thanks.21:49
russellbalaski: sure, can look at it now21:49
cyeohmelwitt: so you're saying that if you want to set the security group on instance create then we expect the user to create their own port first and setup the security group first?21:49
alaskiI'm pretty sure I'm reading the quota code correctly for my analysis of that issue21:49
alaskiBut what I don't know is the best approach to fix it21:49
alaskithe quota_usages table could be incorrect after that migration21:50
russellbdidn't per user quotas break the world last release too?  :(21:50
*** rnirmal has quit IRC21:50
melwittcyeoh: no, nova will create the port and associate with instance so it gets network. then to apply security group, you query neutron to pull the port using device_id == instance uuid and then do an update port with security group you want21:50
alaskirussellb: that's what I've heard :(21:50
*** ocozalp has joined #openstack-meeting21:50
alaskiI was thinking of a new migration to force a resync of quota_usages21:51
comstudyes they did21:51
russellbyeah, that was my first thought21:51
*** ocozalp has quit IRC21:51
comstudand this looks somewhat familiar21:51
comstudthis bug21:51
russellband if this can't get worked out, then i'm not against ripping it out (again)21:51
alaskithere's code in the sqlalchemy api to resync quotas, but I don't know if I can call that from a migration script yet21:52
cyeohmelwitt: isn't there a problem with a race there where for a while the the instance could have a security group you don't want?21:52
*** lbragstad has quit IRC21:52
alaskiit may need to get rewritten to do the sync21:52
cyeohmelwitt: or more precisely would not have a security group that you do want.21:53
russellbalaski: well, sorry to see this is broken, sounds like you're on the right track for the fix IMO21:53
alaskicool.  I'll try to migration approach21:54
russellbbut if you keep looking at feel like this is more fundamentally busted, please keep me updated21:54
alaskikk.  data integrity is the only issue so far21:54
alaskiwhich should be fixable with a one time sync21:54
russellband migrations are fun right now21:55
russellbwith 10+ patches competing for a migration number21:55
*** jasondotstar has joined #openstack-meeting21:55
russellbkinda messy.21:55
dansmith-ETOOMANYMIGRATIONS21:55
russellbyar21:55
alaskiyeah, mikal seems to have scripted his -1s for conflicts21:55
russellbyeah, he's done some cool work with db CI21:55
*** vijendar has quit IRC21:56
dansmithwhatever, I'll be impressed when he can make a "wah wah waaaah" sound during git-review for those21:56
melwittcyeoh: I guess that's true, without the instance create part the instance would start in the default group, become available, and then afterward the desired group could be added.21:56
jog0I won migration 20821:56
russellbshould we had out migration trophies?21:56
yjiang5PCI has push migration from 197 to 209 now :)21:56
russellbanother code review system, reviewboard, gives out trophies for random things21:57
russellblike, if your review # is a palindrome :-)21:57
melwittcyeoh: I wasn't thinking that would be an problem but I'm not sure the use case21:57
russellbit's silly, and awesome.21:57
bnemecrussellb: +121:57
shanewangjog0: sad to hear that, which means we need rebase:)21:57
*** zul has quit IRC21:57
jog0russellb: yes!21:57
shanewanghi, I have one more question for bug https://bugs.launchpad.net/nova/+bug/1212428, besides removing orm, is that decided to convert the stat table into an id and a stats json? or needs more analysis.21:57
uvirtbotLaunchpad bug 1212428 in nova "compute_node_get_all slow as molasses" [Undecided,Confirmed]21:57
jog0shanewang: thinking now is convert but there was a similar attempt before that didn't work so more thought may be needed21:58
*** stevemar has quit IRC21:58
shanewangjog0: got you21:59
russellbalright, looks like we're out of time for the meeting22:00
russellbthanks everyone!22:00
NobodyCamGood meeting, Thank you22:00
shanewangthank you22:00
jog0thanks russellb22:00
russellbdon't stress too much over the incoming deadlines :-)22:00
russellb#endmeeting22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
openstackMeeting ended Thu Aug 15 22:00:29 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-08-15-21.00.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-08-15-21.00.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-08-15-21.00.log.html22:00
*** shanewang has left #openstack-meeting22:00
*** yhe has quit IRC22:01
*** burt has quit IRC22:01
*** Mr_T has left #openstack-meeting22:02
*** zul has joined #openstack-meeting22:02
*** IlyaE has joined #openstack-meeting22:02
*** ivasev has quit IRC22:03
*** pentameter has quit IRC22:04
*** llu-laptop has quit IRC22:04
*** markvan has quit IRC22:06
*** xBsd has quit IRC22:07
*** gatuus has quit IRC22:07
*** chmouel is now known as chmouel_away22:07
*** spenceratx has left #openstack-meeting22:08
*** bpb has quit IRC22:12
*** alexb_ has quit IRC22:12
*** armax has quit IRC22:14
*** alexb_ has joined #openstack-meeting22:14
*** dcramer_ has quit IRC22:14
*** sacharya has quit IRC22:17
*** markmcclain has joined #openstack-meeting22:18
*** alexb_ has quit IRC22:20
*** vipul is now known as vipul-away22:21
*** gatuus has joined #openstack-meeting22:22
*** alexb_ has joined #openstack-meeting22:23
*** gokrokve_ has quit IRC22:23
*** gatuus has quit IRC22:23
*** tanisdl has quit IRC22:23
*** malini1 has quit IRC22:23
*** benl has quit IRC22:24
*** colinmcnamara has quit IRC22:25
*** jecarey has quit IRC22:25
*** changbl has quit IRC22:25
*** edmund has quit IRC22:26
*** colinmcnamara has joined #openstack-meeting22:26
*** jmontemayor has quit IRC22:27
*** hartsocks has left #openstack-meeting22:32
*** litong has quit IRC22:33
*** nati_uen_ has quit IRC22:34
*** lexinator1 has joined #openstack-meeting22:34
*** lexinator has quit IRC22:35
*** nati_ueno has joined #openstack-meeting22:36
*** esker_ has quit IRC22:36
*** sarob has quit IRC22:38
*** zul has quit IRC22:39
*** ajiang has quit IRC22:39
*** galstrom is now known as galstrom_zzz22:41
*** alexpilotti has quit IRC22:42
*** vipul-away is now known as vipul22:43
*** lbragstad_ has joined #openstack-meeting22:48
*** zul has joined #openstack-meeting22:48
*** armax has joined #openstack-meeting22:48
*** zehicle_at_dell has quit IRC22:52
*** dscannell has quit IRC22:52
*** patelna_ has joined #openstack-meeting22:58
*** patelna has quit IRC23:01
*** IlyaE has quit IRC23:01
*** boris-42 has quit IRC23:01
*** IlyaE has joined #openstack-meeting23:03
*** virajh has joined #openstack-meeting23:07
*** markmcclain has quit IRC23:08
*** vipul is now known as vipul-away23:09
*** zul has quit IRC23:09
*** herndon has quit IRC23:11
*** vaml has joined #openstack-meeting23:11
*** SumitNaiksatam has quit IRC23:17
*** vipul-away is now known as vipul23:17
*** mike has joined #openstack-meeting23:17
*** sarob has joined #openstack-meeting23:17
*** mike is now known as Guest6534523:17
*** SumitNaiksatam has joined #openstack-meeting23:18
*** kebray has quit IRC23:20
*** woodspa has quit IRC23:21
*** adjohn has quit IRC23:21
*** blamar has quit IRC23:21
*** sarob has quit IRC23:22
*** stevemar has joined #openstack-meeting23:23
*** sarob has joined #openstack-meeting23:25
*** markpeek has quit IRC23:29
*** MarkAtwood has quit IRC23:31
*** hanrahat has quit IRC23:32
*** danwent has quit IRC23:33
*** SumitNaiksatam has quit IRC23:33
*** benl has joined #openstack-meeting23:34
*** changbl has joined #openstack-meeting23:35
*** benl has quit IRC23:38
*** fnaval_ has quit IRC23:38
*** rods has joined #openstack-meeting23:39
*** vipul is now known as vipul-away23:45
*** scottda has quit IRC23:45
*** patelna_ has quit IRC23:45
*** IlyaE has quit IRC23:47
*** rods has quit IRC23:48
*** lexinator1 has quit IRC23:50
*** lexinator has joined #openstack-meeting23:51
*** adjohn has joined #openstack-meeting23:52
*** otherwiseguy has quit IRC23:55
*** SergeyLukjanov has quit IRC23:56
*** vipul-away is now known as vipul23:58

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