Thursday, 2013-08-01

*** lexinator has quit IRC00:03
*** gyee has quit IRC00:09
*** markpeek has joined #openstack-meeting00:09
*** IlyaE has joined #openstack-meeting00:11
*** lexinator has joined #openstack-meeting00:13
*** rwsu is now known as rwsu-away00:13
*** michchap has quit IRC00:15
*** michchap has joined #openstack-meeting00:16
*** epim has quit IRC00:16
*** pcm_ has quit IRC00:17
*** galstrom_zzz is now known as galstrom00:19
*** alexpilotti has joined #openstack-meeting00:20
*** IlyaE has quit IRC00:21
*** novas0x2a|laptop has quit IRC00:23
*** Mandell has quit IRC00:24
*** Mandell has joined #openstack-meeting00:24
*** sdake_ has quit IRC00:25
*** spzala has quit IRC00:27
*** novas0x2a|laptop has joined #openstack-meeting00:27
*** andrew_plunk has joined #openstack-meeting00:30
*** adalbas has joined #openstack-meeting00:33
*** jecarey has quit IRC00:39
*** IlyaE has joined #openstack-meeting00:39
*** henrynash has quit IRC00:42
*** oNeToWn has joined #openstack-meeting00:43
*** galstrom is now known as galstrom_zzz00:46
*** IlyaE has quit IRC00:50
*** bdpayne has quit IRC00:50
fungigah, i just remembered to pop back in and check it00:56
*** IlyaE has joined #openstack-meeting00:57
*** galstrom_zzz is now known as galstrom00:58
*** changbl has joined #openstack-meeting00:59
*** dkranz has joined #openstack-meeting01:00
*** lexinator has quit IRC01:03
*** IlyaE has quit IRC01:05
*** alexpilotti has quit IRC01:12
*** reed has quit IRC01:13
*** alexpilotti has joined #openstack-meeting01:14
*** oNeToWn has quit IRC01:17
*** danwent has quit IRC01:20
*** ujuc has joined #openstack-meeting01:21
*** alexpilotti has quit IRC01:23
*** brucer_meeting has quit IRC01:23
*** alexpilotti has joined #openstack-meeting01:25
*** vipul is now known as vipul-away01:26
*** brucer has joined #openstack-meeting01:29
*** rongze has joined #openstack-meeting01:32
*** sandywalsh has quit IRC01:33
*** Mandell has quit IRC01:40
*** fnaval_ has joined #openstack-meeting01:43
*** fnaval_ has quit IRC01:43
*** fnaval_ has joined #openstack-meeting01:44
*** michchap has quit IRC01:45
*** lbragstad has joined #openstack-meeting01:46
*** sandywalsh has joined #openstack-meeting01:49
*** alexpilotti has quit IRC01:52
*** tanisdl has quit IRC01:57
*** thomasm has joined #openstack-meeting01:59
*** rods has quit IRC02:00
*** colinmcnamara has joined #openstack-meeting02:02
*** spzala has joined #openstack-meeting02:07
*** ivasev has joined #openstack-meeting02:14
*** spzala has quit IRC02:14
*** michchap has joined #openstack-meeting02:23
*** anteaya has quit IRC02:26
*** andrew_plunk has quit IRC02:26
*** HenryG has joined #openstack-meeting02:34
*** dguitarbite has joined #openstack-meeting02:34
*** vipul-away is now known as vipul02:35
*** anniec has quit IRC02:35
*** anniec has joined #openstack-meeting02:36
*** anniec has quit IRC02:37
*** HenryG has quit IRC02:42
*** lbragstad1 has joined #openstack-meeting02:45
*** michchap has quit IRC02:46
*** lbragstad has quit IRC02:46
*** SergeyLukjanov has joined #openstack-meeting02:50
*** michchap has joined #openstack-meeting02:57
*** yaguang has joined #openstack-meeting02:58
*** michchap has quit IRC02:59
*** michchap has joined #openstack-meeting03:00
*** neelashah has joined #openstack-meeting03:01
*** SergeyLukjanov has quit IRC03:05
*** yaguang has quit IRC03:05
*** rongze has quit IRC03:13
*** brucer has quit IRC03:14
*** danwent has joined #openstack-meeting03:16
*** yaguang_ has joined #openstack-meeting03:19
*** novas0x2a|laptop has quit IRC03:20
*** rongze has joined #openstack-meeting03:21
*** michchap has quit IRC03:23
*** michchap has joined #openstack-meeting03:24
*** stevemar has joined #openstack-meeting03:32
*** otherwiseguy has quit IRC03:33
*** michchap has quit IRC03:33
*** edmund has joined #openstack-meeting03:36
*** galstrom is now known as galstrom_zzz03:42
*** galstrom_zzz is now known as galstrom03:47
*** bdpayne has joined #openstack-meeting03:50
*** bdpayne has quit IRC03:51
*** Mandell has joined #openstack-meeting03:53
*** IlyaE has joined #openstack-meeting03:54
*** otherwiseguy has joined #openstack-meeting03:55
*** galstrom is now known as galstrom_zzz03:59
*** anniec has joined #openstack-meeting04:02
*** anniec_ has joined #openstack-meeting04:03
*** anniec has quit IRC04:06
*** topol has joined #openstack-meeting04:06
*** troytoman is now known as troytoman-away04:09
*** anniec_ has quit IRC04:09
*** nati_ueno has quit IRC04:14
*** IlyaE has quit IRC04:15
*** terriyu has quit IRC04:16
*** amotoki_ has joined #openstack-meeting04:18
*** amotoki has quit IRC04:19
*** IlyaE has joined #openstack-meeting04:19
*** comay has quit IRC04:26
*** stevemar has quit IRC04:27
*** emagana has joined #openstack-meeting04:28
*** neelashah has quit IRC04:28
*** troytoman-away is now known as troytoman04:29
*** edmund has quit IRC04:29
*** garyk has quit IRC04:33
*** afazekas has joined #openstack-meeting04:34
*** brucer has joined #openstack-meeting04:35
*** markmcclain has quit IRC04:36
*** resker has joined #openstack-meeting04:37
*** esker has quit IRC04:40
*** whenry has quit IRC04:40
*** whenry has joined #openstack-meeting04:41
*** troytoman is now known as troytoman-away04:42
*** kebray has joined #openstack-meeting04:44
*** rongze has quit IRC04:51
*** yaguang_ has quit IRC05:00
*** SumitNaiksatam has quit IRC05:01
*** SumitNaiksatam has joined #openstack-meeting05:03
*** glikson has quit IRC05:11
*** IlyaE has quit IRC05:15
*** lastidiot has quit IRC05:20
*** otherwiseguy has quit IRC05:27
*** koolhead11|away has joined #openstack-meeting05:33
*** koolhead11|away is now known as koolhead1105:34
*** glikson has joined #openstack-meeting05:35
*** Daisy has joined #openstack-meeting05:36
*** IlyaE has joined #openstack-meeting05:37
*** markpeek has quit IRC05:40
*** cwolferh has joined #openstack-meeting05:42
*** cwolfe__ has quit IRC05:44
*** glikson has quit IRC05:45
*** dguitarbite has quit IRC05:55
*** michchap has joined #openstack-meeting05:56
*** michchap has quit IRC05:59
*** michchap has joined #openstack-meeting06:00
*** glikson has joined #openstack-meeting06:02
*** kebray has quit IRC06:03
*** garyk has joined #openstack-meeting06:08
*** danwent has quit IRC06:09
*** doron_afk has joined #openstack-meeting06:16
*** schwicht has joined #openstack-meeting06:16
*** michchap has quit IRC06:21
*** yaguang has joined #openstack-meeting06:21
*** rongze has joined #openstack-meeting06:22
*** mrunge has joined #openstack-meeting06:24
*** salv-orlando has joined #openstack-meeting06:25
*** danwent has joined #openstack-meeting06:28
*** whenry has quit IRC06:28
*** jcoufal has joined #openstack-meeting06:31
*** doron_afk has quit IRC06:34
*** emagana has quit IRC06:34
*** mestery_ has joined #openstack-meeting06:34
*** mestery has quit IRC06:36
*** amotoki_ has quit IRC06:37
*** cdub_ has quit IRC06:39
*** Fdot has joined #openstack-meeting06:42
*** salv-orlando has quit IRC06:50
fifieldthi Daisy06:50
ujuchi fifieldt06:51
fifieldthi ujuc06:51
fifieldthow are you?06:52
*** Giang has joined #openstack-meeting06:54
*** enikanorov-w has quit IRC06:54
*** enikanorov-w has joined #openstack-meeting06:54
ujucBusy~.. no work :)06:55
*** IlyaE has quit IRC06:58
*** jpich has joined #openstack-meeting06:59
Fdothello world :)06:59
DaisyI think we have new friends from   Vietnam today.06:59
Gianghi everyone06:59
DaisyHi, Giang.06:59
Gianghi, Daisy06:59
DaisyLet's start.07:00
Daisy#startmeeting OpenStack I18n Meeting07:00
openstackMeeting started Thu Aug  1 07:00:21 2013 UTC and is due to finish in 60 minutes.  The chair is Daisy. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:00
*** openstack changes topic to " (Meeting topic: OpenStack I18n Meeting)"07:00
openstackThe meeting name has been set to 'openstack_i18n_meeting'07:00
DaisyHello everyone. Nice to meet you again.07:00
DaisyWe have new friend today. May you have a simple introduction, Giang?07:00
Giangyes, thanks Daisy07:00
*** henrynash has joined #openstack-meeting07:01
Giangmy name is Giang. I am working for DTT.07:01
GiangDTT is a IT company from Vietnam.07:01
DaisyNow we have ujuc from Korean, Fdot from France, fifieldt from Australia, and Daisy from China.07:01
*** [1]glikson has joined #openstack-meeting07:01
Daisyany friends from Japanese?07:02
Daisyamotoki from Japan said that the daytime meeting is not so convenient for them, because they are doing translation using their spare time.07:03
GiangDTT provides many IT solution for Vietnam and other countries including US, Singapore, ...07:03
fifieldthi Giang!07:03
GiangHi fifieldt. how are you!07:03
fifieldtwell thanks Giang, it's good to meet you :)07:03
DaisyHow do you feel datatime meeting, Giang, ujuc and Fdot ?07:04
Daisydaytime meeting07:04
Giangone of DTT's solution is based on OpenStack which is eGovPlatform07:04
FdotDaisy I really enjoy it :)07:04
Daisythanks, Fdot .07:04
ujucI fine~~.. :))07:04
*** glikson has quit IRC07:04
*** [1]glikson is now known as glikson07:04
Giangi am fine with the meeting time.07:05
DaisyI'm fine too. I don't like night meeting. :)07:05
Daisy#topic Action items from the last meeting07:05
*** openstack changes topic to "Action items from the last meeting (Meeting topic: OpenStack I18n Meeting)"07:05
Fdot9am is always better than 3am ;)07:05
DaisyDaisy to update the wiki page to change the meeting frenquency07:05
DaisyDone. The wiki page is changed.07:05
Daisygabrielcw to take a look at Transifex API to see if it's able to get the translators information.07:05
DaisyThat's done too. Gabriel sent out a mail yesterday.07:05
DaisyThe translator stastics will be a future feature in Transifex.07:06
DaisyGabriel will keep an eye on it.07:06
DaisyAre you ok with the answer, fifieldt ?07:06
* fifieldt reads07:06
fifieldtit seems good progress07:06
*** danwent has quit IRC07:07
fifieldtvery good news07:07
Daisyujuc to follow up why Korean characters cannot be shown in the generated PDF.07:07
DaisyI think we have the answer to ujuc 's problem.07:07
DaisyIf we want to print Korean document, we need Korean font packaged in maven build plug in.07:08
ujucclouddoc-maven-plugin not import korean font.07:08
fifieldtdid david reply yet?07:08
*** egallen has joined #openstack-meeting07:08
Daisyso at last, we will need korean font, Japanese font, Chinese font, Vietnamese font.07:09
ujuci study maven build plugin…. :(07:09
DaisyDoes we need special font for French?07:09
*** IlyaE has joined #openstack-meeting07:09
Daisyso I wonder if it is possible to access the systen font, other than packaged font.07:09
Daisyor else, David will be busy to import so many fonts.07:09
DaisyI have no idea.07:09
fifieldtI don't know how it works either :s07:10
*** eglynn has quit IRC07:10
Daisyso we need David's help to solve the font issue. Daisy will track.07:10
fifieldtbut actually07:10
fifieldtsoon the doc framework07:10
fifieldtwill be under the openstack-infra repository07:10
GiangI do not think you will need vietnamese font 'cos we use unicode07:10
fifieldtso we can modify it without david07:10
Daisy#action Daisy to track the font problem with David.07:11
*** jaimegil has joined #openstack-meeting07:11
DaisyGiang, I will suggest you to do a test.07:11
Daisytest whether there is font issue.07:11
Giangok, no problem07:12
Daisyit's related with document translation. After translation, when generating document, some special font cannot be printed.07:12
Daisy#topic Progress with Japanese doc site07:13
*** openstack changes topic to "Progress with Japanese doc site (Meeting topic: OpenStack I18n Meeting)"07:13
DaisySince there is no Japanese people, I will introduce the progress.07:13
Daisycannot be displayed.07:13
DaisyNow amotoki has developed the website.07:13
*** IlyaE has quit IRC07:14
DaisyIt's under reviewed by Japanese team now.07:14
DaisyHe ( or she? ) will report a bug to openstack-manuals, and requested to add the new index page.07:14
DaisyDocuments are published using Jenkins's job. So we also need a job definition.07:15
DaisyThere is one, but I don't know if it works.07:15
DaisyJapanese team created one draft. I have forwarded to CI team and asked for review.07:15
*** ttrifonov_zZzz is now known as ttrifonov07:15
Daisyno response yet.07:15
DaisyThe publish job will be a little difficult for us, because we don't have much understanding of CI infrastructure.07:16
Daisyfifieldt: do you have any suggestion for such situation?07:17
fifieldtI can take  a look07:17
fifieldtdo you have the review #07:17
Daisyno, I think it's very rough, I don't submit for review.07:17
DaisyJapanese team have a mail sent to i18n mailing list with the job definition.07:17
fifieldtI have written publish jobs before sucessfully07:17
DaisyGreat !07:18
Daisycan I new a bug for CI team about this publish job?07:18
Daisywe need your help.07:18
DaisyI wonder if it is suitable to new a bug , because it may be a new requirement.07:18
fifieldtis it a new requirement? can you forward me the email ?07:18
fifieldtI haven't caught up with my email07:19
Daisynot a bug.07:19
fifieldtif it is easy I can do it tomorrow07:19
fifieldtand ask in #openstack-infra for approval07:19
fifieldtmaybe we can discuss offline07:19
fifieldtto keep the meeting going07:19
DaisyI forwarded to your openstack mail.07:19
Daisy#topic Progress with glossary table in Transifex07:19
*** openstack changes topic to "Progress with glossary table in Transifex (Meeting topic: OpenStack I18n Meeting)"07:19
DaisyFdot: would you like to introduce the progress?07:20
DaisyFdot's team is collecting the glossary now.07:20
FdotDaisy we have started to backport the glossary form the wiki into transifex07:20
* Fdot looking for the url07:21
Fdot#url :07:21
Fdot#url :
Daisywhere is the wiki link?07:21
Daisycan you share with us?07:21
Fdotof course :)07:21
* Fdot is looking for the url 07:22
Fdot#url :
DaisyAre you delete all the old glossarys in Transifex?07:22
*** sushils has joined #openstack-meeting07:23
FdotNo and i have a question about this07:23
FdotThere is 2 glossary in transifex07:23
FdotOne for all the Openstack hub07:23
Fdotand one for the manual part07:23
Fdotwe have started to works on the openstack hub07:24
fifieldtwe use the glossary in the openstack-manuals repo for several of the books07:24
Daisyand maybe there are glossarey for Keystone, Horizon and so on.07:24
Fdotso maybe it would be better to use the manuals 's one07:24
DaisyI think we should use the one in the hub.07:25
Daisyfifieldt is taking about the glossary defined in , right?07:25
GiangDaisy, you mean this one
fifieldtyes Daisy07:25
Daisyright, Fdot 's team si importing the glossary in the wiki to Transifex.07:26
FdotGiang we are importing into
Daisyfifieldt: have you done any comparation between these two glossary?07:26
Fdotbut we would like to know if we use this one or this onr :
fifieldtunfortunately not, Daisy - I just fixed the one in the openstack-manuals repo when we wrote the operations guide07:27
fifieldtit had too many terms that weren;t 100% relevent07:27
DaisyFdot: if we define the hub glossary, can we use it when we are translating openstack-manuals?07:27
fifieldtso did some removing of terms07:27
*** Tien has joined #openstack-meeting07:27
Fdotneed to test :)07:27
* Fdot is looking07:27
Daisyfifieldt: "it had too many terms that weren;t 100% relevent", which one? the wiki one, or the manuals one?07:28
fifieldtthe manuals one07:28
Daisyso you removed a lot?07:28
Fdotin the manual part it is using the manual glossary07:29
fifieldtquite a few Daisy, mainly the very generic ones07:29
fifieldtwhich were more about general computers07:29
fifieldtrather than OpenStack07:29
DaisyI think some of the wiki glossary are not 100% relevent too. My question is where does the wiki glossary come.07:30
DaisyFdot: manuals in OpenStack cannot use the hub glossary definition?07:30
fifieldtI think they are originally the same source07:30
fifieldtI believe the wiki may be the original and it was introduced into the manuals repo but never removed from the wiki, so both kept being updated :)07:31
DaisyFdot: I think we need to do a check. I think probably yes.07:31
Fdotdaisy i don't understand your question :)07:31
DaisyFdot: to check whether openstack-manuals can use the glossary defined in openstack hub.07:31
*** ivasev has quit IRC07:32
Daisydo I make sense?07:32
FdotDaisy yes07:32
Fdotinto a manual project I have made some tests on some works07:32
*** amotoki has joined #openstack-meeting07:32
Daisy#action Fdot to check whether openstack-manuals can use the glossary defined in openstack hub.07:33
DaisyHi, there comes amotoki .07:33
Fdotinto the glossary part (bottom right) the definition are from the manual gloassry and not from the hub glossary07:33
ujuchi :)07:33
Daisyfifieldt: there are two glossary files in common/glossary07:33
Fdotmaybe it can be configurate into the hub or the project configuration07:33
Daisywhich one are you using?07:34
fifieldtopenstack-glossary.xml is just an introduction07:34
fifieldtthe actual entries live in glossary-terms.xml07:34
DaisyFdot: if you need my help, I can. I'm the administrator of openstack hub.07:34
Daisyok. thanks.07:34
FdotDaisy : can you check if we can define into the configuration if we can force the hub glossary ?07:35
*** oNeToWn has joined #openstack-meeting07:35
Daisysure. I can do offline.07:35
Daisy#action Daisy to check if we can define into the configuration if we can force the hub glossary.07:35
Fdotthanks a lot :)07:35
*** sushils has quit IRC07:35
*** cdub_ has joined #openstack-meeting07:36
DaisyFdot: there are two glossary, one is in the wiki, the other is in manuals repository. Some of them may be same, and some of them may be different.07:36
DaisyDo you have any suggestions for such situation?07:36
FdotDaisy : I have asked to one person of my team to check the difference07:37
Fdothe is in holiday this week07:37
Daisywhich one should we use? Or we merge them? How can we track them automatically? Can we do it by program?07:37
FdotI am going to check with him07:37
Fdotand to contact you back about what he has seen07:37
*** sushils has joined #openstack-meeting07:37
*** colinmcnamara has quit IRC07:37
FdotI think they are close07:37
Daisythanks, Fdot . I remember Transifex can import from some format of files into glossary table.07:37
Fdotwe should merge them07:37
DaisyMaybe the file importing can ease this work.07:38
Fdotcould be easier07:39
Fdotthan copying and pasting each words07:39
Daisyright. not sure if there are any API support.07:39
DaisyGlossary mantainance will be a problem for us in future, when our glossary table grows, and when doc team and other team change the glossary.07:40
DaisyAnyway, let's do the import first.07:40
DaisyI have finished all the topics I want to cover.07:41
Daisy#topic Open discussion07:41
Daisywe can move to the open discussion now.07:41
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack I18n Meeting)"07:41
FdotI have a quick question :)07:41
FdotWe are currently looking for working with a translation company for translating the manuals07:41
Fdotbut we can ask to this company to work on transifex07:42
*** rongze has quit IRC07:42
Fdotfirst we have decided to send them the Pdf for working07:42
*** eglynn has joined #openstack-meeting07:42
Fdotbut it is going to be hard after for backporting into transifex07:42
Fdotthe works is going to be important07:42
DaisyFdot: you cannot ask them to work on Transifex?07:43
Fdothave you got any advice on how we vcan proceed07:43
Fdotunfortunatly no07:43
Fdotthey use their own tools07:43
Giangwhy don't you ask it to work on Transifex?07:43
DaisyDo they mind to translate po files directly? Then you can import po files to Transifex.07:43
*** rongze has joined #openstack-meeting07:43
amotokiwe experience Transifex is not a good platform to review the big documents too.07:44
DaisyFdot asks professional translation company to help on the translation.07:44
Giangok, i see07:44
Fdothow did you do amotoki ?07:44
amotokiwe edit po file directly and upload po files to Transifex.07:44
DaisyI agree with amotoki to some extend, actually.07:44
Fdotthe problem with Po file is that it is difficult to understand the context07:45
Fdotyou don't see the whole page07:45
DaisyGenerally speaking, when generating po files, the paragraph sequences are kept the same with source xml files.07:45
Fdotso sometime it is difficult to understand what you are translating07:45
Daisybut when the source xml files are changed, the sequence will not be kept exactly same.07:46
*** yaguang has quit IRC07:46
DaisyThe updated one will be appended at the end.07:46
GiangFdot, i have the same issue.07:46
DaisyThe old one will be deleted.07:46
Daisyamotoki: how is your team feeling when translating po files?07:46
*** sdake has quit IRC07:46
amotokiDaisy: During the review, it is not a problem.07:47
amotokias an advice, we execute "msgfmt --statistics -o /dev/null <PO file>" to check the format.07:47
*** jhenner has joined #openstack-meeting07:47
DaisyWhat editor do you use, amotoki , to translate po file?07:47
amotokiit depends on translators. I prefer to emacs po-mode.07:48
DaisyI think there are some po editors that can help translation.07:48
Daisywhat's this?07:48
amotokiemacs is a very common editor in Unix world :-)07:48
DaisyFdot and Giang, will you try if your translators are ok to translate po files directly, other than using Transifex, but using some po editors.07:49
FdotDaisy I already know the answer they don't really want to work on Po file :(07:50
FdotThey prefere Pdf07:50
Daisythanks for the answer, Fdot.07:50
Giangi have no idea for now07:50
Giangi am working on Transifex and it is ok for me07:50
DaisyIf the paragraph sequence are same, if the po editor can display the english string and translation string well, I personally think po files are all right.07:51
Gianghowever ...07:51
Daisyhowever what? Giang?07:51
Giangwe may have the same issue with Fdot when we want to hire any profressionals to do this job07:51
Daisyyou are so rich that you can hire professional translators.07:52
FdotDaisy :D07:52
amotokiI think translation work consists of two phase: the one is to translate, tranlate, tranlate... and the other is a review and feedback phase.07:52
GiangOpenStack Vietnam team have an idea to ask students to help us07:52
DaisyGood idea, Giang.07:52
amotokiin the translation phase, Transifex is good to some extent, but Transifex.07:53
amotokiTransifex is not so good in the review phase...07:53
Gianghowever, we will not pay them by money but ...07:53
Daisywe have a long way to go to make our translation tools better and better.07:53
Giangby some award for active contributors07:54
DaisyI'm open if soembody can propose new tools and new websites.07:54
GiangIn my case, Transifex is ok07:55
FdotTransifex is a nice tool07:55
Fdotmaybe we should just send some feedback to their team07:55
amotokiI think so too.07:55
Fdotmaybe they will include them ;)07:55
Daisywhat I want to maintain is a good translation system, good usibility, good maintainance, and easy to syncronize with source strings.07:56
DaisyI think Openstack community have some relationship with Transifex community.07:56
Daisyfifieldt may know some.07:56
fifieldtyeah, we're chjatting with transifex guys07:57
fifieldtreed used to work with one of them :)07:57
DaisyI remember our CI team offer to help us to set up our own transifex website if we want.07:57
Daisybut I don't think we need to main our own transifex website till now.07:58
Giangyes, right07:58
Daisyso let's summarize a wish list to Transifex and send to them through some channel?07:58
Fdot+1 \o_07:59
fifieldtsounds good07:59
Daisyamotoki ?07:59
*** SergeyLukjanov has joined #openstack-meeting07:59
Giangfor now, i have only one issue is we do not see the whole context when translating.07:59
amotokiDaisy: agee07:59
Daisyok. so there is an action item to all of the team.08:00
amotokiI am summarizing our experience during the translation of ops-guide now.08:00
Daisy#action each team collect the wish list of Transifex and Daisy to combine them.08:00
Daisyamotoki: when you finish, please let i18n team know. It will be a great reference for all the team.08:01
Daisyany other topics? Time pass very quickly.08:01
amotokiDaisy: sure.08:01
Daisyno topics?08:01
amotokiDaisy: do you have any progress on the source lang in Horizon Transifex?08:01
Daisysorry no.08:01
DaisyI will update with you through email.08:02
Giangok, thanks08:02
Daisy#action Daisy to track the source lang in Horizon08:02
Daisyso I will close the meeting now.08:02
Giangok. see you all08:02
DaisyThank you all for your attendance.08:02
amotokithank you all!08:03
*** openstack changes topic to "OpenStack Meetings ||"08:03
openstackMeeting ended Thu Aug  1 08:03:04 2013 UTC.  Information about MeetBot at . (v 0.1.4)08:03
openstackMinutes (text):
FdotThank you all :)08:03
*** bismigalis has joined #openstack-meeting08:03
*** Giang has quit IRC08:03
Daisynice to talk with you.08:03
FdotLike we say in french : Bonne journée à tous :)08:03
Daisyhehe, I cannot udnerstand.08:03
DaisyI cannot udnerstand French.08:03
fifieldtyet :)08:03
FdotYou can translate : Have a good day all :)08:04
ujucLike fifieldt say in korean: 좋은 하루되세요~ :)08:05
*** Tien has quit IRC08:05
Daisy:) I can say Chinese.08:05
*** yaguang has joined #openstack-meeting08:06
*** Fdot has quit IRC08:06
fifieldt"What is the difference between 좋은 하루 보내세요 and 좋은 하루 되세요?” :P08:06
ujucno~ kkkk08:08
ujucsame hehe08:08
ujucdoing vs having. kk08:08
*** Fdot has joined #openstack-meeting08:11
fifieldtujuc, do you know anything about ?08:12
fifieldtcool :)08:13
ujucHad attended in the last year. Only the first day ...08:14
ujuchehe… ~08:14
fifieldtlearn much? :)08:14
ujucum… yes~08:14
fifieldtcool, maybe we should submit an OpenStack talk08:15
fifieldtI will suggest on the kr facebook group08:15
fifieldtthanks :)08:15
ujucah ~~!08:15
ujucThanks ^^08:15
fifieldtok, time to go prepare dinner08:15
fifieldtthanks :)08:15
ujuc:) bye~ :) keke08:17
*** johnthetubaguy has joined #openstack-meeting08:19
*** johnthetubaguy1 has joined #openstack-meeting08:21
*** johnthetubaguy has quit IRC08:24
*** derekh has joined #openstack-meeting08:27
*** fifieldt has quit IRC08:27
*** topol has quit IRC08:29
*** sushils has quit IRC08:31
*** doron_afk has joined #openstack-meeting08:31
*** schwicht has quit IRC08:31
*** sushils has joined #openstack-meeting08:36
*** slavayssiere has joined #openstack-meeting08:36
*** [1]glikson has joined #openstack-meeting08:36
*** ndipanov_gone is now known as ndipanov08:37
*** tkammer has joined #openstack-meeting08:38
*** glikson has quit IRC08:40
*** [1]glikson is now known as glikson08:40
*** slavayssiere has quit IRC08:42
*** ruhe has joined #openstack-meeting08:44
*** salv-orlando has joined #openstack-meeting09:07
*** Daisy has quit IRC09:10
*** ujuc has quit IRC09:18
*** slavayssiere has joined #openstack-meeting09:18
*** salv-orlando has quit IRC09:21
*** mrunge has quit IRC09:22
*** oNeToWn has quit IRC09:24
*** Yada has joined #openstack-meeting09:24
*** carlp-away is now known as carlp09:30
*** mrunge has joined #openstack-meeting09:34
*** Fdot has quit IRC09:44
*** cdub_ has quit IRC09:51
*** salv-orlando has joined #openstack-meeting10:01
*** [1]glikson has joined #openstack-meeting10:01
*** pnavarro has joined #openstack-meeting10:02
*** glikson has quit IRC10:03
*** [1]glikson is now known as glikson10:03
*** ruhe has quit IRC10:04
*** cdub_ has joined #openstack-meeting10:14
*** cdub_ has quit IRC10:19
*** rods has joined #openstack-meeting10:28
*** topol has joined #openstack-meeting10:39
*** SergeyLukjanov has quit IRC10:41
*** doron_afk is now known as doron10:42
*** ruhe has joined #openstack-meeting10:45
*** yaguang has quit IRC10:53
*** sdake_ has joined #openstack-meeting10:59
*** doron has quit IRC11:03
*** doron has joined #openstack-meeting11:08
*** SergeyLukjanov has joined #openstack-meeting11:11
*** doron has quit IRC11:13
*** [1]glikson has joined #openstack-meeting11:14
*** oNeToWn has joined #openstack-meeting11:15
*** glikson has quit IRC11:16
*** [1]glikson is now known as glikson11:16
*** pnavarro has quit IRC11:17
*** garyk has quit IRC11:18
*** garyk has joined #openstack-meeting11:20
*** cdub_ has joined #openstack-meeting11:20
*** complexmind has joined #openstack-meeting11:23
*** garyk has quit IRC11:25
*** slavayssiere has quit IRC11:29
*** doron has joined #openstack-meeting11:30
*** boris-42 has joined #openstack-meeting11:31
*** [1]glikson has joined #openstack-meeting11:31
*** slavayssiere has joined #openstack-meeting11:31
*** glikson has quit IRC11:33
*** [1]glikson is now known as glikson11:33
*** Positive has joined #openstack-meeting11:35
*** doron has quit IRC11:36
*** Positive is now known as Positive_11:38
*** Positive_ is now known as Positive11:39
*** Positive is now known as Positive_11:39
*** doron has joined #openstack-meeting11:39
*** Positive_ is now known as Positive11:39
*** Positive has quit IRC11:48
*** Positive has joined #openstack-meeting11:48
*** Positive has quit IRC11:48
*** doron is now known as doron_afk11:49
*** henrynash has quit IRC11:49
*** ZangMingJie has quit IRC11:50
*** henrynash has joined #openstack-meeting11:51
*** xBsd has joined #openstack-meeting11:51
*** pcm_ has joined #openstack-meeting11:52
*** alexb_ has quit IRC11:53
*** jasondotstar has quit IRC11:54
*** zul has quit IRC11:54
*** zul has joined #openstack-meeting11:57
*** HenryG has joined #openstack-meeting11:58
*** sandywalsh has quit IRC11:58
*** troytoman-away is now known as troytoman11:58
*** dkranz has quit IRC12:00
*** alexb_ has joined #openstack-meeting12:00
*** doron_afk is now known as doron12:00
*** galstrom_zzz is now known as galstrom12:10
*** sandywalsh has joined #openstack-meeting12:11
*** jaimegil has quit IRC12:11
*** carlp is now known as carlp-away12:15
*** henrynash has quit IRC12:20
*** noslzzp has joined #openstack-meeting12:22
*** xBsd has quit IRC12:22
*** lpabon has joined #openstack-meeting12:24
*** xBsd has joined #openstack-meeting12:24
*** sushils has quit IRC12:26
*** zul has quit IRC12:27
*** zul has joined #openstack-meeting12:27
*** sushils has joined #openstack-meeting12:29
*** pnavarro has joined #openstack-meeting12:29
*** jasondotstar has joined #openstack-meeting12:30
*** complexmind is now known as complexmind__12:30
*** complexmind__ is now known as complexmind12:31
*** ruhe has quit IRC12:32
*** mrunge has quit IRC12:32
*** sushils has quit IRC12:34
*** woodspa has joined #openstack-meeting12:35
*** meteorfox has quit IRC12:35
*** sushils has joined #openstack-meeting12:37
*** thomasm has left #openstack-meeting12:39
*** lpabon has quit IRC12:40
*** doron is now known as doron_afk12:44
*** henrynash has joined #openstack-meeting12:45
*** edmund has joined #openstack-meeting12:47
*** zul has quit IRC12:50
*** galstrom is now known as galstrom_zzz12:50
*** alexpilotti has joined #openstack-meeting12:51
*** zul has joined #openstack-meeting12:51
*** neelashah has joined #openstack-meeting12:54
*** ruhe has joined #openstack-meeting12:54
*** ruhe has quit IRC12:59
*** lbragstad1 has quit IRC13:00
*** zul has quit IRC13:02
*** zul has joined #openstack-meeting13:03
*** yaguang has joined #openstack-meeting13:03
*** slavayssiere has quit IRC13:03
*** cdub_ has quit IRC13:03
*** zehicle_at_dell has joined #openstack-meeting13:05
*** schwicht has joined #openstack-meeting13:07
*** fnaval_ has quit IRC13:13
*** lpabon has joined #openstack-meeting13:15
*** rongze_ has joined #openstack-meeting13:17
*** glikson has quit IRC13:17
*** rongze has quit IRC13:18
*** slavayssiere has joined #openstack-meeting13:22
*** schwicht has quit IRC13:23
*** schwicht has joined #openstack-meeting13:24
*** pcm_ has quit IRC13:24
*** complexmind has quit IRC13:24
*** pcm_ has joined #openstack-meeting13:25
*** meteorfox has joined #openstack-meeting13:28
*** changbl has quit IRC13:29
*** zul has quit IRC13:30
*** lpabon has quit IRC13:30
*** krtaylor has quit IRC13:32
*** amotoki has quit IRC13:32
*** lbragstad has joined #openstack-meeting13:33
*** glikson has joined #openstack-meeting13:34
*** alexpilotti has quit IRC13:36
*** haomaiwang has quit IRC13:38
*** haomaiwang has joined #openstack-meeting13:38
*** jecarey has joined #openstack-meeting13:40
*** [1]glikson has joined #openstack-meeting13:40
*** johnpur has joined #openstack-meeting13:42
*** stackKid has quit IRC13:43
*** glikson has quit IRC13:44
*** [1]glikson is now known as glikson13:44
*** markpeek has joined #openstack-meeting13:45
*** egallen has quit IRC13:46
*** Tacho has joined #openstack-meeting13:46
*** spzala has joined #openstack-meeting13:46
*** dkranz has joined #openstack-meeting13:47
*** pentameter has joined #openstack-meeting13:47
*** shardy is now known as shardy_afk13:49
*** noslzzp has quit IRC13:50
*** fnaval_ has joined #openstack-meeting13:50
*** xBsd has quit IRC13:52
*** anteaya has joined #openstack-meeting13:53
*** bgorski has joined #openstack-meeting13:54
*** xBsd has joined #openstack-meeting13:55
*** noslzzp has joined #openstack-meeting13:55
*** otherwiseguy has joined #openstack-meeting13:55
*** markvan has joined #openstack-meeting13:56
*** Netos has joined #openstack-meeting13:57
*** dhellmann_ is now known as dhellmann13:57
*** egallen has joined #openstack-meeting13:58
*** Tacho has quit IRC13:59
*** Netos is now known as Tacho13:59
*** markwash has joined #openstack-meeting13:59
*** dscannell has joined #openstack-meeting14:00
*** SergeyLukjanov has quit IRC14:01
*** vijendar has joined #openstack-meeting14:03
*** rwsu-away is now known as rwsu14:04
*** johnpur has quit IRC14:05
*** stevemar has joined #openstack-meeting14:05
*** mrodden has joined #openstack-meeting14:07
*** eharney has quit IRC14:09
*** mrodden has quit IRC14:10
*** mrodden has joined #openstack-meeting14:11
*** markmcclain has joined #openstack-meeting14:11
*** zehicle_at_dell has quit IRC14:12
*** xBsd has quit IRC14:12
*** markmcclain has quit IRC14:12
*** mrodden has quit IRC14:12
*** markmcclain has joined #openstack-meeting14:12
*** mrodden has joined #openstack-meeting14:13
*** oNeToWn has quit IRC14:15
*** MarkAtwood has joined #openstack-meeting14:16
*** stackKid has joined #openstack-meeting14:17
*** lexinator has joined #openstack-meeting14:17
*** krtaylor has joined #openstack-meeting14:19
*** sushils has quit IRC14:21
*** lastidiot has joined #openstack-meeting14:22
*** gongysh has joined #openstack-meeting14:23
*** sushils has joined #openstack-meeting14:24
*** yaguang has quit IRC14:24
*** zul has joined #openstack-meeting14:25
*** dscannell has quit IRC14:25
*** andrew_plunk has joined #openstack-meeting14:27
*** slavayssiere has quit IRC14:28
*** terriyu has joined #openstack-meeting14:28
*** galstrom_zzz is now known as galstrom14:29
*** johnpur has joined #openstack-meeting14:30
*** lexinator has quit IRC14:31
*** cdub_ has joined #openstack-meeting14:31
*** adalbas has quit IRC14:34
*** lastidiot has quit IRC14:34
*** egallen has quit IRC14:36
*** AlanClark has joined #openstack-meeting14:36
*** changbl has joined #openstack-meeting14:40
*** johnpur has quit IRC14:42
*** psedlak has joined #openstack-meeting14:43
*** slavayssiere has joined #openstack-meeting14:43
*** johnpur has joined #openstack-meeting14:44
*** johnpur has quit IRC14:44
*** adalbas has joined #openstack-meeting14:46
*** johnthetubaguy1 is now known as johnthetubaguy14:49
*** burt has joined #openstack-meeting14:51
*** zehicle_at_dell has joined #openstack-meeting14:51
*** adalbas has quit IRC14:51
*** lexinator has joined #openstack-meeting14:51
*** andrew_p_ has joined #openstack-meeting14:52
*** michchap has joined #openstack-meeting14:52
*** michchap has quit IRC14:52
*** jmontemayor has joined #openstack-meeting14:52
*** thang_ has joined #openstack-meeting14:53
*** michchap has joined #openstack-meeting14:53
*** andrew_plunk has quit IRC14:54
*** ruhe has joined #openstack-meeting14:57
*** SergeyLukjanov has joined #openstack-meeting14:59
*** lexinator has quit IRC15:00
*** andrew_p_ has quit IRC15:00
*** mrodden has quit IRC15:01
*** andrew_plunk has joined #openstack-meeting15:01
*** eharney has joined #openstack-meeting15:01
*** eharney has quit IRC15:01
*** eharney has joined #openstack-meeting15:01
*** cp16net is now known as cp16net|away15:02
*** krtaylor has quit IRC15:03
*** ivasev has joined #openstack-meeting15:04
*** cdub_ has quit IRC15:04
*** markwash has quit IRC15:04
*** jhenner has quit IRC15:05
*** jlucci has joined #openstack-meeting15:06
*** cp16net|away is now known as cp16net15:07
*** adalbas has joined #openstack-meeting15:08
*** lastidiot has joined #openstack-meeting15:09
*** boris-42 has quit IRC15:11
*** mrodden has joined #openstack-meeting15:12
*** shardy_afk is now known as shardy15:14
*** zehicle_at_dell has quit IRC15:14
*** zehicle_at_dell has joined #openstack-meeting15:14
*** topol has quit IRC15:15
*** kebray has joined #openstack-meeting15:17
*** lexinator has joined #openstack-meeting15:17
*** jlucci has quit IRC15:22
*** Mandell has quit IRC15:24
*** tanisdl has joined #openstack-meeting15:25
*** johnthetubaguy has quit IRC15:30
*** johnthetubaguy has joined #openstack-meeting15:30
*** dscannell has joined #openstack-meeting15:31
*** vijendar has quit IRC15:31
*** rnirmal has joined #openstack-meeting15:37
*** MarkAtwood has left #openstack-meeting15:38
*** markwash has joined #openstack-meeting15:38
*** egallen has joined #openstack-meeting15:38
*** ujuc has joined #openstack-meeting15:38
*** egallen has quit IRC15:38
*** markwash_ has joined #openstack-meeting15:43
*** gongysh has quit IRC15:45
*** markwash has quit IRC15:45
*** markwash_ is now known as markwash15:45
*** haomaiwang has quit IRC15:47
*** SergeyLukjanov has quit IRC15:48
*** tkammer has quit IRC15:51
*** topol has joined #openstack-meeting15:51
*** hemna has joined #openstack-meeting15:52
*** krtaylor has joined #openstack-meeting15:54
*** zul has quit IRC15:58
*** jcoufal has quit IRC15:59
*** SumitNaiksatam has quit IRC16:00
*** sarob has joined #openstack-meeting16:01
*** IlyaE has joined #openstack-meeting16:01
*** ruhe has quit IRC16:01
*** jmontemayor has quit IRC16:10
*** michchap has quit IRC16:11
*** glikson has quit IRC16:12
*** jmontemayor has joined #openstack-meeting16:13
*** gyee has joined #openstack-meeting16:15
*** egallen has joined #openstack-meeting16:16
*** andrew_plunk has left #openstack-meeting16:16
*** lexinator has quit IRC16:16
*** vijendar has joined #openstack-meeting16:18
*** xBsd has joined #openstack-meeting16:19
*** zul has joined #openstack-meeting16:24
*** SergeyLukjanov has joined #openstack-meeting16:25
*** SumitNaiksatam has joined #openstack-meeting16:26
*** rongze has joined #openstack-meeting16:27
*** ujuc has quit IRC16:29
*** epim has joined #openstack-meeting16:29
*** noslzzp has quit IRC16:30
*** rongze_ has quit IRC16:30
*** jmontemayor has quit IRC16:32
*** stevemar has quit IRC16:33
*** jmontemayor has joined #openstack-meeting16:35
*** glikson has joined #openstack-meeting16:36
*** ruhe has joined #openstack-meeting16:39
*** zehicle_at_dell has quit IRC16:40
*** zehicle_at_dell has joined #openstack-meeting16:40
*** Yada has quit IRC16:41
*** xBsd has quit IRC16:43
*** andrew_plunk has joined #openstack-meeting16:44
*** ravikumar_hp has joined #openstack-meeting16:44
*** cp16net is now known as cp16net|away16:44
*** giulivo has joined #openstack-meeting16:48
*** sarob has quit IRC16:49
*** emagana has joined #openstack-meeting16:49
*** sarob has joined #openstack-meeting16:49
*** jmontemayor has quit IRC16:52
*** sarob has quit IRC16:54
*** ruhe has quit IRC16:56
*** burt is now known as burt-afk16:57
sdague#startmeeting qa16:59
openstackMeeting started Thu Aug  1 16:59:41 2013 UTC and is due to finish in 60 minutes.  The chair is sdague. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:59
*** openstack changes topic to " (Meeting topic: qa)"16:59
openstackThe meeting name has been set to 'qa'16:59
sdagueok, who's around for the QA meeting?16:59
sdague#link -
sdague#topic Blueprints17:01
*** openstack changes topic to "Blueprints (Meeting topic: qa)"17:01
*** johnthetubaguy has quit IRC17:01
*** mlavalle has joined #openstack-meeting17:01
sdagueok, status on key blueprints17:01
*** koolhead11 has quit IRC17:01
sdaguelets start on parallel tempest17:01
sdaguemtreinish: you're up17:01
mtreinishso testr is making progress. I've been pushing a lot of code to try and fix the races we're seeing17:01
mtreinishright now I'm stuck with on az create server one which still shows up periodically after I added locking17:02
mtreinishthat is the most common fail right now17:02
dkranzmtreinish: I just saw it again with my skip slow patch17:02
afazekasmtreinish: Do you have link to one fail ?17:02
mtreinishI'm also working on adding tenant isolation to scenario which will fix a security group issue there17:02
mtreinishdkranz: yeah it happens ~30-40% now17:03
mtreinishwithout locking it was every run17:03
mtreinishafazekas: one sec let me pull up the link17:03
sdaguemtreinish: do we do any agregate manip in scenario tests?17:03
afazekasmtresnins: after this change I could add per process isolation :
*** epim has quit IRC17:04
mtreinishsdague: not that I remember but I'd have to double check to be sure17:04
*** nati_ueno has joined #openstack-meeting17:04
sdaguemtreinish: is that the final big bug?17:05
*** boris-42 has joined #openstack-meeting17:05
mtreinishafazekas: what do you mean by per process isolation?17:05
sdagueor are there others hidden behind that one?17:05
afazekasmtreinish: to create user/tenant on every worker process only17:05
mtreinishsdague: hopefully, looking at the build trend: its the only one I've been seeing17:05
afazekasmtreinish: I could be extendable to use predefined list of users, when you are using tempest without admin rights17:05
mtreinishbut there were some other ones that I saw when I first turned it on17:06
*** stevemar has joined #openstack-meeting17:06
*** whenry has joined #openstack-meeting17:06
afazekasList probably means a pair of users per worker process17:06
sdagueafazekas: so that seems like a different optimization, I'd rather not distract from testr right now17:06
mtreinishbut I haven't seen them in over a week17:06
sdagueas we have different per class tenant isolation in there17:06
adalbasi have been investigating one of those mtreinish pointed, i'm collecting info to open a bug if that comes again to happen17:07
sdagueok, we'll probably have to push parallelism17:07
sdagueto shake more out, we had to do that with nova17:07
afazekassdague: the change  has some modeling related improvement anyway17:07
sdagueI was regularly running with 16 process to make it fall apart17:07
*** Mandell has joined #openstack-meeting17:07
mtreinishsdague: yeah but first we've got to sort out the az failure I started working on it with jog0 last night17:07
giulivoI'd like to join the forces and try the testr parallelization myself; can I ask what is the gerrit submission I should checkout?17:08
sdagueafazekas: right, I get that, but right now we have a very limitted number of weeks to get testr in, so focus should be narrowly on that. We can make model improvements post H317:08
mtreinishand I haven't been able to reproduce it locally17:08
dkranzgiulivo: It's already in. Just run the tox for full that uses testr17:08
mtreinishgiulivo: sure, it's actually already running I can go over the details with you after the meeting in -qa17:09
afazekassdague: AFAIK keystone v3 is also a goal17:09
sdagueafazekas: we have to rank goals17:09
sdagueotherwise we don't get them done17:09
sdaguetestr is going to be really key to the last 2 week merge rush for all the projects17:09
sdaguewe can do v3 after H317:10
sdaguethat's why it's currently the only critical blueprint17:10
dkranzsdague: What does "do v3" mean?17:10
mtreinishdkranz: keystone v3 api17:10
sdaguespend time on landing keystone v3 api tests17:10
*** epim has joined #openstack-meeting17:10
dkranzsdague: I don't understand why we can't do that while Matt is working on testr.17:11
giulivothanks mtreinish, dkranz I see that is testenv:all17:11
sdaguedkranz: there is only so much time to go around, so if people are doing that, they aren't helping make sure testr can land17:11
mtreinishgiulivo: and testenv:testr-full, testr-full runs nonvoting on the check queue and all runs periodic17:11
dkranzsdague: What people? We can't have 10 people working on getting testr in.17:12
ravikumar_hpmtreinish: Can you please put readme in api folder17:12
sdaguedkranz: actually, I don't think that's true17:12
sdaguetestr at this point is about chasing race bugs17:12
*** johnthetubaguy has joined #openstack-meeting17:12
sdaguethat's very parallelizable17:12
dkranzsdague: OK. What should we look at?17:13
*** koolhead11 has joined #openstack-meeting17:13
mtreinishravikumar_hp: there is one:
sdagueget testr parallel up, push it hard see where the flakey bits fall out17:13
mtreinishdkranz: yeah it's about running it locally and debugging where it fails17:14
dkranzmtreinish: OK, but let's file bugs so we are not duplicating effort.17:14
ravikumar_hpmtreinish: i mean for running testr17:14
mtreinishthe jenkins job is to help with finding things in a gate like environment and it's found quite a few. I've documented some here:
mtreinishravikumar_hp: oh I can push out an update for the main readme to do that later today17:15
*** bismigalis has quit IRC17:15
mtreinishravikumar_hp: but -t or tox -etestr-full will run it in parallel17:15
*** jpich has quit IRC17:15
ravikumar_hpmtreinish: Thanks17:15
*** derekh has quit IRC17:16
sdagueyep, if we can hang the bugs off the blueprint, that would be good17:16
mtreinishdkranz: I agree, adalbas said he was going to add a tag for testr parallel so we can easily track this17:16
mtreinishyeah the blueprint too17:16
sdaguedkranz: mtreinish told me over lunch you had the interesting idea of switching over to testr single thread for all the jobs now17:17
psedlaksdague: could you please also linkify those urls for debugging-testr-tempest and info those commands for running it? :)17:17
*** thomasbiege has joined #openstack-meeting17:17
dkranzsdague: Yes, because I did not want to maintain nose selection for slow, heat, etc.17:17
dkranzsdague: It seems like testr is solid enough and gives advantages over nose17:17
sdaguedkranz: I like it17:17
sdaguecan you propose the patch for that?17:18
dkranzIt's junk parallel that is broken17:18
dkranzsdague: Yes, as soon as the slow skip goes through.17:18
dkranzsdague: It seems to be working so I will unmark it WIP after the meeting.17:18
sdaguepsedlak: um... do you have the links? :)17:18
psedlak:) ok, i was thinking that only the chair can do it, so sorry :)17:19
sdague#info concerted push on getting testr parallel working before H317:19
mtreinish#info run tempest with testr parallel using: -t or tox -etestr-full17:19
sdague#action dkranz to propose testr non parallel for all tempest job runs, getting us off nose17:19
*** sarob has joined #openstack-meeting17:20
sdaguethis is all going to be awesome when it lands17:20
sdagueand drop average gate times in half17:20
dkranzsdague: Excellent17:20
*** vipul is now known as vipul-away17:21
sdagueok, other blueprints?17:21
*** noslzzp has joined #openstack-meeting17:21
adalbasmtreinish, the tag you mentioned before is the one we add in the bugs, right?17:21
dkranzsdague: I am also going to put some focus on getting heat in.17:21
mlavallesdague: I can report on mine17:21
sdaguemlavalle: go for it17:22
mtreinishadalbas: yeah but I forgot that we can just link it to the speed-up-tempest blueprint17:22
mlavallesdague: this blueprint involves a list of several items17:22
adalbasmtreinish, yes, it makes sense17:22
mlavallesdague: each item requires the following: fix something in a tempest test case, fix something in nova and potentially fix something in Neutron / Neutron client17:22
mlavallesdague: right now I am working on the quotas item. You and I have been talking over Gerrit about the Tempest piece. Last Sunday I pushed the corresponding patchsets for review in nova. You gave a -1 in one of them (not complaining17:22
mlavallesdague: after quotas, I will start with the floating ips items and so on…. I will knock them down one by one17:23
sdaguemlavalle: ok, what's the review again? maybe I should look again17:23
sdaguemlavalle: cool17:23
sdaguethanks much for this17:23
mlavallesdague: so we can expedite his17:23
mlavalleeach time I send patches to nova or Neutron, I'll let you know, so you can help me17:24
sdaguemlavalle: sounds great17:24
dkranzmlavalle: What about the neutron smoke job?17:24
mtreinishmlavalle: I have a concern with adding neutron tests in that the neutron jenkins jobs aren't working at all. So adding more tests we really aren't running them17:24
dkranzmlavalle: It fails but I don't see any errors in the log.17:25
*** reed has joined #openstack-meeting17:25
mtreinishdkranz: it fails during the devstack exercises I believe17:25
sdaguedkranz: it fails really early, I did bring that up in the neutron channel17:25
*** sarob has quit IRC17:25
sdaguemarkmclain said he'd take a look17:25
dkranzmtreinish: Yes, we need to get the neutron gate jobs working first.17:25
mlavalledkranz, mtresinish: that job you are talking about is what I am fixing17:25
dkranzmlavalle: OK, great.17:25
sdaguemlavalle: ok great17:25
mtreinishmlavalle: ok but that review adds tests. I don't think we can merge that until the job is fixed17:26
sdaguemtreinish: no we can merge17:27
sdagueit's running17:27
sdagueso it's not like we're not executing it17:27
mlavallemtreinish: yeah, it's running17:27
sdaguewe're just not voting with it17:27
*** otherwiseguy has quit IRC17:27
mlavallesdague: correct17:27
sdagueI'm ok on that front, as it's not the same bitrot issue17:27
sdagueI just +Aed it17:27
mlavallesdague: thanks17:27
mtreinishsdague: no but the jenkins jobs with neutron doesn't even get to tempest. so how can we be running the tests?17:28
mlavallethat's all17:28
*** andrew_plunk has quit IRC17:28
sdaguemtreinish: oh, right... well17:28
sdagueI +Aed it17:28
sdagueanyway, moving on17:29
sdagueother blueprints?17:29
afazekasmlavalle: next week, I would like to spend more time on the smoke gate instability issues , If you have any info about these issues let me know17:29
dkranzIt would be nice to get rid of exercises17:29
sdaguedkranz: yeh, that's a post H3 thing17:29
mlavalleafazekas: will do17:29
dkranzsdague: Of course17:29
sdagueI think it just needs an audit to make sure scenario >= exercises17:29
sdagueand if so, we disable exercises17:30
sdagueand if not, we enhance scenario tests17:30
sdaguethere is now a scenario test for horizon, which is great17:30
sdagueso we know that you can actually log into horizon17:30
*** vipul-away is now known as vipul17:31
sdagueok next topic17:31
sdague#topic Critical Reviews (sdague)17:31
*** openstack changes topic to "Critical Reviews (sdague) (Meeting topic: qa)"17:31
afazekassdague: nowadays,  we are skiping too many test because of instability issues, it ruins our coverage17:31
sdagueok, what critical reviews are out there right now that need eyes?17:31
sdagueafazekas: ok, lets come back at the end17:32
sdaguelets give people time for critical reviews17:32
*** slavayssiere has quit IRC17:32
mtreinishafazekas: I have issues with that actually but we should take it to the list I feel17:33
mtreinishbecause test runners can easily exclude tests17:33
mtreinishand testr just does it with a regex17:33
*** doron_afk has quit IRC17:33
dkranzmtreinish: I discovered that testr is a pain because it lets you OR regexes but not AND them17:33
afazekasmtreinish: we have about 20 bugs, it will be a long regexp :)17:33
mtreinishafazekas: that patch is not a replacement for the skip decorator17:34
sdagueafazekas: yeh, lets take that to the list17:34
sdagueremember, we're using openstack-dev now with the [qa] tag17:34
dkranzmtreinish: That makes testr regexp ugly. See my 'slow' tag patch for an example.17:34
mtreinishits so he can selectively exclude tests that we don't skip because of an environmental difference17:34
dkranzmtreinish: That is a valid use case.17:35
dkranzmtreinish: The question is just what the best way is17:35
sdagueyeh, I'm leaning towards mtreinish on this one, because there is a way to do it already17:35
sdaguebut let's take it to the list and discuss there, because I think ian needs to be in it17:35
sdagueand this approach probably has other implications for other efforts, like how the cells gate job is going to be approached17:35
sdagueas they've got this issue that cells doesn't implement a lot of nova features17:36
mtreinishdkranz: well, we can always talk to lifeless about adding an exclude option to testr17:36
dkranzsdague: Perhaps we should ask lifeless about allowing regexp exclusion from the command line17:36
dkranzmtreinish: :)17:36
sdague#action move discussion on to the mailing list17:36
sdagueok, other reviews that need attention?17:37
sdaguegoing once17:38
sdagueok, moving on17:40
afazekas1 sec17:40
sdagueok, not moving on17:40
afazekas'InvalidOkCode' exception can simplify the assertion in the test code17:41
afazekasWe just need to assert the OK codes in rest clients17:41
sdagueok, I'll take a look post meeting17:42
sdagueany other reviews?17:42
*** ndipanov is now known as ndipanov_gone17:42
sdagueok, next topic17:42
sdague#topic Call for more Core reviewers (dkranz)17:42
*** openstack changes topic to "Call for more Core reviewers (dkranz) (Meeting topic: qa)"17:42
dkranzWe need more core reviewers17:43
sdagueso our core count remains at 6, and from the numbers those 6 are still the most active reviewers17:43
sdagueI would really like to add more folks, but we do really need folks to be doing at least the level of work as existing cores17:43
dkranzMost of the current reviewers are from Red Hat or IBM17:43
sdagueand having good -1 judgement17:43
sdagueso consider this an extended call for "please review more, even if you aren't a core member" :)17:44
dkranzsdague: We should send this to the list17:44
sdaguebecause the road to becoming a core member is to basically already be doing the work of one, then we add you17:44
sdague#action sdague to send call for more reviewers to the list17:44
*** IlyaE has quit IRC17:45
sdagueok, I think that's the agenda17:45
sdague#topic Open Discussion17:45
*** openstack changes topic to "Open Discussion (Meeting topic: qa)"17:45
mlavallesdague: I'll start doing reviews once I feel comfortable that I am making progress with the Neutron gate job17:45
*** joel-coffman has joined #openstack-meeting17:46
sdaguemlavalle: great, thanks!17:46
*** johnthetubaguy has quit IRC17:46
sdaguein case folks haven't seen that, I've been heads down trying to unify our requirements testing so we don't wedge the gate17:47
sdaguehopefully that lands today17:47
sdaguewe're actually down to a tempest requirements issue now17:47
sdagueany other things from folks?17:47
*** elo has joined #openstack-meeting17:47
mtreinishnothing from me17:48
sdagueanyone else17:48
dkranzPlease review
dkranzThat's it from me.17:49
mlavallemlavalle: nothing from me17:49
sdagueok, great17:50
sdaguelet's call it a meeting17:50
*** nick____ has joined #openstack-meeting17:50
*** glikson has quit IRC17:50
*** openstack changes topic to "OpenStack Meetings ||"17:50
sdaguethanks all17:50
openstackMeeting ended Thu Aug  1 17:50:19 2013 UTC.  Information about MeetBot at . (v 0.1.4)17:50
openstackMinutes (text):
*** psedlak has left #openstack-meeting17:50
*** psedlak has joined #openstack-meeting17:50
*** mlavalle has left #openstack-meeting17:51
*** sarob has joined #openstack-meeting17:51
*** ravikumar_hp has quit IRC17:52
*** eglynn has quit IRC17:54
*** koolhead11 has quit IRC17:55
*** nicolae_ has joined #openstack-meeting17:56
*** sarob has quit IRC17:56
*** vipul is now known as vipul-away17:58
*** egallen has quit IRC17:59
*** vipul-away is now known as vipul18:03
*** benl_ has joined #openstack-meeting18:05
*** henrynash has quit IRC18:06
hyakuhei_Hi all18:06
hyakuhei_Sorry I'm late, had some communication issues18:06
hyakuhei_#startmeeting OpenStack Security Group18:06
openstackMeeting started Thu Aug  1 18:06:54 2013 UTC and is due to finish in 60 minutes.  The chair is hyakuhei_. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:06
*** openstack changes topic to " (Meeting topic: OpenStack Security Group)"18:06
openstackThe meeting name has been set to 'openstack_security_group'18:06
* joel-coffman waves hello18:07
hyakuhei_Hi :) My appologies for not starting this sooner.18:07
hyakuhei_Do we have anyone else with us today?18:07
*** IlyaE has joined #openstack-meeting18:07
hyakuhei_Hi Guys, thanks for waiting around18:07
*** changbl has quit IRC18:08
*** Mandell has quit IRC18:08
hyakuhei_#topic Booksprint followup18:08
*** openstack changes topic to "Booksprint followup (Meeting topic: OpenStack Security Group)"18:08
*** burt-afk is now known as burt18:08
hyakuhei_Right, the book is looking reasonably good at the moment. Does anyone have feedback on suggested improvements?18:08
*** koolhead11 has joined #openstack-meeting18:08
*** lcheng has quit IRC18:09
hyakuhei_I've written up the various security issues we identified during the sprint, I'll send the non-sensitive ones around the ML as a few require blueprints to be drafted18:09
hyakuhei_Any thoughts?18:09
hyakuhei_Fantastic, I'll do that then18:10
joel-coffmansounds good18:10
hyakuhei_#action hyakuhei to send non-sensitive security issues around the OSSG for the group to pick blueprints to run with18:10
*** lcheng has joined #openstack-meeting18:10
eloI'll flush out more of the networking stuff as there is a lot of churn with feature in Havana for Neutron18:10
hyakuhei_I will see if we can pick up a few at HP too18:10
*** benl__ has joined #openstack-meeting18:11
hyakuhei_Great, thanks elo18:11
hyakuhei_Are you familiar with the submission process?18:11
*** xBsd has joined #openstack-meeting18:11
eloin the process of getting up to speed18:11
*** cp16net|away is now known as cp16net18:12
hyakuhei_ok great, feel free to reach out to the group if you run into problems. You can reach out to me directly too if you want18:12
hyakuhei_make sure you ping us when you submit your changes and we'll get the reviewed quickly18:12
*** benl_ has quit IRC18:12
hyakuhei_#topic Items that require OSSG attention18:12
*** openstack changes topic to "Items that require OSSG attention (Meeting topic: OpenStack Security Group)"18:12
hyakuhei_If you're not already aware of it I'd encourage you all to take a look at
hyakuhei_It is a bit of a mess with 9 different patch sets the last time I looked18:13
hyakuhei_And some discussion of wether it's ok to have sensitive information in debug output18:13
hyakuhei_Any thoughts on that last point specifically?18:13
*** andrew_plunk has joined #openstack-meeting18:14
hyakuhei_ok, well if you get the opportunity please dive in and have a look at that18:14
hyakuhei_Also, you'll notice we have security-related reviews being delivered to the OSSG mailing list, this is a good thing, if you see one please take the time to take a look at the review.18:15
hyakuhei_#topic OSSG Logo18:15
*** openstack changes topic to "OSSG Logo (Meeting topic: OpenStack Security Group)"18:15
hyakuhei_Do we have any budding artists in the group?18:15
*** ayoung has quit IRC18:15
joel-coffmannot me18:16
thomasbiegeunfortunately not18:16
hyakuhei_hah, not me either18:16
*** andrew_plunk has quit IRC18:16
hyakuhei_ok, well I guess the quest continues. I'm trying to find out if we can use/modify/adapt the OpenStack logo18:16
thomasbiegeI think a openstack icon with a lock can be made easily18:16
elome either18:16
*** andrew_plunk has joined #openstack-meeting18:16
*** whenry has quit IRC18:17
hyakuhei_thomasbiege: sure it can, if we can get permission to use it18:17
hyakuhei_Ok, I'll see if I can find someone 'creative' :)18:17
*** Mandell has joined #openstack-meeting18:17
hyakuhei_#topic Wiki / OSSG Organisation18:17
*** openstack changes topic to "Wiki / OSSG Organisation (Meeting topic: OpenStack Security Group)"18:17
nicolae_a lock would be easy to add to the openstack logo, i can try create some prototypese18:18
hyakuhei_Does anyone have thoughts on how the OSSG should operate in future, particularly in regard to onboarding new people into the group?18:18
joel-coffmannot particularly18:19
thomasbiegegetting the right people is the interesting part18:19
*** ruhe has joined #openstack-meeting18:19
nicolae_I'm going through this process right now -- well basically reading into source code to know the nuts and bolts of a project, that's the first step i thought of18:19
thomasbiegepeople that have fun and time to bring their expertise into the group18:19
hyakuhei_So I think the group is~70 people at the moment18:20
hyakuhei_which is great18:20
hyakuhei_but some induction / tasking / direction is probably required18:20
*** mestery_ is now known as mestery18:20
hyakuhei_Security peeps are difficult cats to herd at the best of times18:20
nicolae_What about assigning some small tasks, like reviews, as a practice?18:21
hyakuhei_Ok, I'll try to draft something this week and ping it around the group18:21
hyakuhei_nicolae_: excellent idea.18:21
*** gyee has quit IRC18:21
thomasbiegedepends much on their current function and preference in their daily security job18:21
nicolae_They might not be definitive, but getting feedback on the review would surely help "get in" the process18:21
hyakuhei_Yeah, but we can try it, if it doesn't work well that's fine too :)18:22
*** sarob has joined #openstack-meeting18:22
hyakuhei_#action hyakuhei and bryan to discuss new-starter options18:22
hyakuhei_#topic A.O.B18:22
*** openstack changes topic to "A.O.B (Meeting topic: OpenStack Security Group)"18:22
thomasbiegewell we need initioation tasks for the different kind of sec people. development of code, secure design, network, etc18:23
hyakuhei_I think one of the areas we struggle with (OpenStack) is making it easy for the people with the ideas to find the people who can get the work done, reviewed and submitted in the OpenStack world.18:24
hyakuhei_It's less than trivial to do.18:24
thomasbiegeyes, that is a problem I encounter too ATM18:24
hyakuhei_joel-coffman: are you guys doing anything in the world of Swift object encryption?18:24
joel-coffmannot at the moment18:24
joel-coffmanCinder and ephemeral storage only right now18:25
*** eglynn has joined #openstack-meeting18:25
*** mlavalle has joined #openstack-meeting18:25
joel-coffmanI think Mirantis had some patches / blueprints for Swift encryption18:25
*** mlavalle has left #openstack-meeting18:25
* notmyname lurks18:26
hyakuhei_Ah yeah, I think they were pretty bad.18:26
hyakuhei_but that's what I had in the back of my mind at least.#18:26
hyakuhei_I'll go take another look18:26
*** dani4571 has joined #openstack-meeting18:26
hyakuhei_In fact, that's a good newbie task :D18:26
joel-coffmanokay, we didn't look too closely at their proposal since Swift is off our radar at the moment18:27
nicolae_+1! :)18:27
*** sarob has quit IRC18:27
hyakuhei_Ok, does anyone want to take an action to take a look at that and start an on-ML discussion before next week?18:27
hyakuhei_ie. the next meeting18:27
thomasbiegenot me sorry (vacation)18:28
notmynameFWIW, encryption doesn't belong in swift core, most likely. but we can discuss this in more depth when you turn focus to it18:28
nicolae_If that's a newbie task then i can take it, but i won't be ablevto attend the next meeting18:28
joel-coffmanwe're all swamped trying to get our Cinder code reviewed / accepted :(18:28
*** sarob has joined #openstack-meeting18:29
hyakuhei_no worries joel-coffman - perhaps reach out to the OSSG explicitly for support on that ?18:29
*** zul has quit IRC18:29
hyakuhei_We've got a good community of people but their quiet, if you mail the ML regarding some of the review challenges I'm sure you'll get help18:29
hyakuhei_notmyname: can you elaborate on that in 30 seconds?18:30
*** sarob has quit IRC18:30
notmynamehyakuhei_: it either belongs in the client or as the responsibility of the storage volume. either way it is outside the scope of swift18:30
*** sarob has joined #openstack-meeting18:31
joel-coffmanwill do, right now iterating with Cinder folks to address some of their questions18:31
hyakuhei_In the client doesn't work well at all, there are already options for on-premise swift encryption18:31
thomasbiegeok, need to go18:32
notmynamehyakuhei_: the third possibility has to do with a deployer key per-tennant or something. but that too can be implemented as a plug-in and doesn't need to be in the core code18:32
hyakuhei_The volume would need to be aware of the different tenants and how they're indipendantly keyed. Swift needs to be involved because there are all sorts of issues I think, compression, dedupe etc.18:32
notmynamehyakuhei_: nope. same story for compression and dedupe ;-)18:32
hyakuhei_Yeah, I don't really care where it is as long as a) It's not stupid and b) it actually works18:33
notmynamehyakuhei_: valuable features, but not part of the storage engine code base18:33
hyakuhei_notmyname: perhaps we can have an on Mailinglist discussion about it?18:33
hyakuhei_we're over time here.18:33
*** pnavarro has quit IRC18:34
hyakuhei_Thank you everyone, productive meeting! Please feel free to follow-up any conversations on the ML18:34
*** openstack changes topic to "OpenStack Meetings ||"18:34
openstackMeeting ended Thu Aug  1 18:34:24 2013 UTC.  Information about MeetBot at . (v 0.1.4)18:34
notmynamehyakuhei_: I'd love to. especially if it means the issue will be put to rest18:34
openstackMinutes (text):
*** joel-coffman has quit IRC18:34
hyakuhei_notmyname: perfect, mail the ML or me directly18:34
notmynamehyakuhei_: from our perspective (ie swift contributors), the issue has been put to rest. if you bring it up, I'll respond. I won't bring up the issue again myself18:36
*** henrynash has joined #openstack-meeting18:36
*** ruhe_ has joined #openstack-meeting18:36
*** ruhe has quit IRC18:37
*** novas0x2a|laptop has joined #openstack-meeting18:38
*** zehicle_at_dell has quit IRC18:43
*** comay has joined #openstack-meeting18:44
*** vipul is now known as vipul-away18:45
*** henrynash has quit IRC18:47
*** nachi has joined #openstack-meeting18:50
*** nachi_ has joined #openstack-meeting18:50
*** vijendar has quit IRC18:51
*** henrynash has joined #openstack-meeting18:51
*** sdake has joined #openstack-meeting18:52
*** sdake has quit IRC18:52
*** sdake has joined #openstack-meeting18:52
*** otherwiseguy has joined #openstack-meeting18:53
*** vijendar has joined #openstack-meeting18:56
*** Tacho has quit IRC18:56
*** schwicht has quit IRC18:57
*** epim has quit IRC18:58
*** henrynash has quit IRC19:00
*** numero8 has joined #openstack-meeting19:00
*** andrew_plunk has quit IRC19:04
*** epim has joined #openstack-meeting19:04
*** changbl has joined #openstack-meeting19:06
*** sarob has quit IRC19:09
*** akarpinska1 has joined #openstack-meeting19:10
*** akarpinska1 has quit IRC19:12
*** akarpinska1 has joined #openstack-meeting19:12
*** lpabon has joined #openstack-meeting19:16
*** zehicle_at_dell has joined #openstack-meeting19:18
*** vipul-away is now known as vipul19:18
*** boris-42 has quit IRC19:19
*** boris-42 has joined #openstack-meeting19:20
*** otherwiseguy has quit IRC19:22
*** benl__ has quit IRC19:24
*** edmund has quit IRC19:25
*** glikson has joined #openstack-meeting19:25
*** noslzzp has quit IRC19:26
*** benl_ has joined #openstack-meeting19:31
*** sandywalsh has quit IRC19:33
*** rnirmal has quit IRC19:36
*** whenry has joined #openstack-meeting19:36
*** benl__ has joined #openstack-meeting19:38
*** otherwiseguy has joined #openstack-meeting19:39
*** nick____ has quit IRC19:40
*** eglynn has quit IRC19:41
*** benl_ has quit IRC19:42
*** ruhe_ has quit IRC19:45
*** sandywalsh has joined #openstack-meeting19:46
*** benl__ has quit IRC19:52
*** diogogmt has joined #openstack-meeting19:54
*** jlucci has joined #openstack-meeting19:57
*** numero8 has quit IRC19:58
harlowja#start-meeting state-management20:00
harlowja#startmeeting state-management20:01
openstackMeeting started Thu Aug  1 20:01:14 2013 UTC and is due to finish in 60 minutes.  The chair is harlowja. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: state-management)"20:01
openstackThe meeting name has been set to 'state_management'20:01
harlowjahowday all!20:01
changblhello there20:02
harlowjahi hi20:02
harlowjahi hi20:02
* harlowja waits a few for others20:02
*** Guest29511 has joined #openstack-meeting20:03
harlowjajlucci u around, kevin?20:03
*** otherwiseguy has quit IRC20:04
harlowjaok well anyway, all fine20:04
harlowja#topic status20:04
*** openstack changes topic to "status (Meeting topic: state-management)"20:04
harlowjaso i've been trying to rebase the cinder patch and make sure thats all working, currently hitting some CI weirdness20:04
harlowjaworking with the infra folks to try to figure out whats going on20:04
harlowjaalso trying to help do reviews at the same time (and other internal y! stuff)20:05
kebrayharlowja  my apologies, I just got summoned to another meeting.20:05
jlucciYeah I'm here -sorry20:05
jlucciJust got back from Dallas a couple minutes ago20:05
jlucciYeah. I'm that good. haha20:05
harlowjanp, just going through status, not sure if u have anything to mention20:06
*** cp16net is now known as cp16net|away20:06
harlowjakebray i think submitted the speaker session, so thx kebray  :-)20:06
*** epim has quit IRC20:06
jlucciUm -just the distributed stuff online, and about to have a tasfklow video/tutorial thingy online20:06
jlucciWas just going to e-mail it out to openstack-dev20:06
harlowjaabout, wow20:06
harlowjavery cool20:07
harlowjaspeaker abstract btw20:07
harlowja(for HK summit)20:07
jlucciAwesome kebray :D20:07
*** kchenweijie has joined #openstack-meeting20:07
changblgood job, like the abstract20:07
harlowjayahoo will hopefully have a few others, time will tell :)20:07
*** benl_ has joined #openstack-meeting20:07
harlowjachangbl thx for fixing a few issues u found :)20:08
changblnp, the code is written well:)20:08
changbli looked through the code base20:08
harlowjaha, its a continual WIP, thx20:08
changblsure, will keep watching the code :)20:09
harlowjaakarpinska1 anything for u to report, know its late for u so thx for showing up20:09
*** koolhead11 has quit IRC20:09
harlowjadon't give up on blocks, still think it has a place :)20:09
harlowjathx changbl the more eyes the better of course :)20:10
akarpinska1I'm a little bit confused about what I really need to do with my TaskFlow tasks and with my patch. Want to hear some comments about it.20:10
harlowjasure, np20:11
*** xBsd has quit IRC20:12
*** adrian_otto has joined #openstack-meeting20:12
jlucciakarpinska1 - anastasia I'm guessing?20:12
jluccihaha Awesome. Yeah - I'm still looking through that doc you sent out20:12
*** cp16net|away is now known as cp16net20:12
harlowjaso akarpinska1 i put a few review comments up, nothing major, so that will be part 1 i think20:12
harlowjakevin i think will land his db stuff soon to, so then there will be the question of how thats used there to20:13
jlucciAwesome. I'll get to those/doc as soon as I post that video20:13
*** afazekas has quit IRC20:13
kchenweijieyup. got about 2/3 of it commented today20:13
kchenweijietaking a break from commenting for a little bit20:13
kchenweijiebut it will be up there by tomorrow morning at the latest20:14
harlowjaakarpinska1 so also once jlucci i think is ok with the block stuff (or other comments) then i think that will allow for a little more work there, then we can get that in, make more adjustments and such20:14
harlowjakchenweijie sounds great20:14
harlowjamore comments the better :)20:14
*** topol has quit IRC20:14
harlowjaakarpinska1 sound good?20:14
*** obondarev has quit IRC20:14
harlowjaits a in progress library, so nothing will always be clear :)20:14
harlowjaalthough i'll try to help it be, ha20:15
akarpinska1of course20:15
harlowjasounds great20:15
*** obondarev has joined #openstack-meeting20:16
harlowja#topic projects_using20:16
*** openstack changes topic to "projects_using (Meeting topic: state-management)"20:16
harlowjaso if its fine just want to see where we are with other projects on getting usage of taskflow in20:17
harlowjaafter i fix this cinder stuff, i'm gonna try to see about possible nova 'small' use-case soon20:17
*** nati_ueno has quit IRC20:17
*** psedlak has quit IRC20:17
harlowjaakarpinska1 might also be doing another cinder use-case, which is cool20:17
jlucciAwesome - I'm getting ready to start doing some trove integration20:17
harlowjaand jlucci maybe reddwarf/trove20:17
lifelessdkranz: mtreinish: there is regex exclusion20:17
lifelessdkranz: mtreinish: will find you in -qa to follow up.20:17
*** nati_ueno has joined #openstack-meeting20:18
dkranzlifeless: Thanks.20:18
akarpinska1I think, we need to choose one implementation and then apply it to Cinder20:18
jlucciImplementation being patterns, or current task flow vs. new block approach?20:18
akarpinska1Now we have two commands rewritten in different manner20:18
changblCan I ask what is "block"?20:19
*** rnirmal has joined #openstack-meeting20:19
jlucciIt's a new way of running tasks20:19
jlucciI'm sure akarpinska1 can explain it much better than me though. (:20:19
changblwhat is different? any brief intro?20:19
harlowjaakarpinska1 i'm fine with picking one way, just unsure which way still, i think the current refactoring can be adjusted, but i don't want to miss H release for that20:20
*** otherwiseguy has joined #openstack-meeting20:20
akarpinska1There is a documentation
harlowjato me a block is similar to a way to structure a task right20:22
harlowja*structure the way a task set is ran20:22
*** jmontemayor has joined #openstack-meeting20:22
*** nati_ueno has quit IRC20:22
harlowjawhich also can be composed of sub-blocks20:22
*** gyee has joined #openstack-meeting20:22
*** spzala has quit IRC20:23
akarpinska1harlowja: in your implementation there are three types of flows, blocks give us a possibility to combine different behavior in one flow20:23
changblwill read the doc, thanks20:23
harlowjaakarpinska1 ya, which i think is good20:23
harlowjachangbl thx, hopefully it makes it more clear20:24
changblharlowja, np20:24
*** eglynn has joined #openstack-meeting20:24
akarpinska1also I tried to split it on small components to make it flexible to change20:24
*** resker has quit IRC20:24
*** dkranz has quit IRC20:24
*** esker has joined #openstack-meeting20:24
harlowjaya, which is good stuff, i'm still myself trying to figure out how it fits, thats all :)20:25
harlowjathe challenge becomes make something really easy for library users to use, without adding to much new syntax/structure that they need to learn20:25
changblagree, harlowja20:26
harlowjablocks has alot of new structure right now that they must learn, thats my current worry about it20:26
akarpinska1but user need to know only about the blocks20:26
changblas long as it can do the job, the simpler, the better20:26
*** rongze has quit IRC20:27
akarpinska1by default user should know nothing about the actions and builders until he wants to change internal implementation of the flow20:27
*** rongze has joined #openstack-meeting20:28
akarpinska1User will describe his tasks and the flow structure with the blocks. That's all20:28
harlowjasure, sure, not saying its bad or anything, just the block way does require a little bit more learning20:29
*** nati_ueno has joined #openstack-meeting20:29
*** pcm_ has quit IRC20:29
*** ivasev has quit IRC20:30
harlowjai'm still working through my understanding of it also, so it might just be fine :)20:30
*** HenryG has quit IRC20:30
harlowjaits just the harder it is to compose these, the more pushback i think we will get20:30
harlowjathe nice thing about the linear_flow is that it likely solves most of the use-cases of openstack, ha20:31
harlowjai can see the sequential block possibly being the same thing20:31
akarpinska1Yes, like in Cinder create_snapshot, I used only the sequential block20:31
harlowjaya, i'll try to find some time to mess around with the code also, that i think will help20:32
*** nicolae_ has quit IRC20:32
harlowjamaybe jlucci and changbl and others with free time (if any) can also20:32
harlowjasound good akarpinska1 ?20:32
changblsure, will read the code and help with code review20:32
jlucciSounds good20:33
akarpinska1Will be excellent to get feedback20:33
*** IlyaE has quit IRC20:33
harlowjasounds great20:33
harlowjai had another random idea also, but might not be needed if blocks works out20:34
harlowjasomething else to read over, ha20:34
harlowjamight be to much though20:34
harlowjalet me change topic to open discussion, since thats more releated to that :)20:34
harlowja#topic open-discuss20:34
*** openstack changes topic to "open-discuss (Meeting topic: state-management)"20:34
changblone question: shall we have more examples in docs/ ? Those examples are quite helpful20:35
harlowjai think so :)20:35
changblharlowja, great20:36
harlowjai'll try to make some of those up also, jlucci will your video introduce any?20:36
harlowjaakarpinska1 if u have any thoughts on let me know20:36
harlowjait might be to similar to blocks that its not needed20:36
akarpinska1Interesting, trying to understand20:36
jlucciYup. Although the video is geared towards a distributed backend, so the majority of the examples lean more towards that pattern20:36
harlowjasure sure20:37
changbllooking forward your video, jlucci20:37
harlowjachangbl i think after we get some of the DB stuff in it will become really neat with examples20:37
changblharlowja, yep!20:37
harlowjalike start a example process, have it do something, kill it, then see it resume after starting another process up20:38
harlowjalike magic, ha20:38
*** boris-42 has quit IRC20:38
jlucciBut yeah - the DB stuff will provide for a ton of new functionality20:38
harlowjaakarpinska1 the idea was along the line that all these task things could be instrumented in a 'machine' that is devoted to running them with its own concept of 'memory'20:39
harlowjathen openstack is powered by a machine that runs tasks20:39
harlowjawas just an interesting idea :-p20:39
harlowja*not a physical machine, but a mini-one that runs in memory20:39
harlowjaand has enough control over what its running and its own 'memory' that we can just save/restore the machine20:40
akarpinska1I'm trying to imagine how it can be implemented) sounds interesting, but it can be a lot of questions20:40
harlowjawell its similiar to the block stuff i think in a way20:40
harlowjayou have a concept of 'memory' there20:40
harlowjaand a runtime stack (block structure)20:40
akarpinska1flow.kwargs is a memory )20:41
harlowjaso they are similar in that way20:41
harlowjaif we had such machine it could be the base for all other patterns ontop20:41
harlowjablock pattern, linear, ...20:41
akarpinska1I thought about some flows manager, maybe it can be a TaskMachine20:41
harlowjapossibly could be20:42
harlowjathe neat thing about the machine is that i think jlucci and all the dynamic stuff that is wanted there can also use the same machine20:42
*** whenry has quit IRC20:42
harlowjai'm not sure how blocks would fit into the dynamic modification model20:42
jlucciYeah, I'm still working through that20:42
*** cp16net is now known as cp16net|away20:43
*** spzala has joined #openstack-meeting20:43
jlucciNeed to get more familiar with the block code as well before I can really say something one way or the other20:43
harlowjaya, same here :)20:43
changblme too ~20:43
akarpinska1But one problem is that the service executes each command in the separate thread, as I know20:43
harlowjawhat do u mean there20:44
akarpinska1if we have a task machine, OpenStack services must be redesigned not to create a thread for the API request, but to redirect it to the TaskMachine20:44
harlowjawell depends on what level it is integrated with20:45
harlowjaan API request could just use a pool of machines20:45
harlowjaor make a new one20:45
harlowjadoesn't have to be 1:1 since the machine isn't phsyical20:45
akarpinska1one machine for one request?20:45
harlowjawell the machine is just software, so it could be that20:46
*** jmontemayor has quit IRC20:46
harlowjaprobably to complex for the foreseable future i think, but an interesting idea, ha20:46
harlowjamost of openstack i think will do with the basics for a long time, ha20:46
*** jmontemayor has joined #openstack-meeting20:47
harlowja*or be happy with the basics, even just the restructuring into 'tasks' is a big accomplishment20:47
harlowjaso maybe this is at stage ++++++20:47
changblextremely like this is the case:)20:47
*** spzala has quit IRC20:47
*** lpabon has quit IRC20:48
*** cp16net|away is now known as cp16net20:48
*** thomasbiege has quit IRC20:48
harlowjaya, interesting to think about, i'm pretty sure it will take a while to just do the task restructuring in all the projects20:48
akarpinska1one machine for the whole service can easily lock resources20:48
harlowjaya, akarpinska1 i don't think we would want 1 'task' machine20:49
*** dscannell has quit IRC20:49
*** ayoung has joined #openstack-meeting20:49
*** IlyaE has joined #openstack-meeting20:50
harlowjabut if we can offer some neat possiblities, which i think we already are starting to, the more adoption we will get, which is great, but have to keep the complexity low, but features high, not an easy balance :)20:50
akarpinska11 machine for one request is easily to implement =)20:50
harlowjaakarpinska1 ya, it likely is, it becomes an interstsing question if the 'machine' thing could be the base for all task patterns20:50
harlowjabe nice to have 1 lowest level component that everything is built on for said patterns20:51
harlowjablocks, distributed...20:51
akarpinska1In my implementation Flow class is like a flow controller, maybe it could be a machine later20:51
harlowjathe neat thing about the machine is that there can be conditional tasks that let u choose which task to put on the 'machine' stack next20:51
*** vipul is now known as vipul-away20:52
harlowjaakarpinska1 it might be able to20:52
*** woodspa has quit IRC20:53
harlowjaanyway, somethign to think about, think if we can get more project adoption that will be the key for the short-term20:53
harlowjawhich means just beginning to use what we have and adjusting openstack code to use it, while at the same time learning from said adjustments and changing taskflow20:53
*** giulivo has quit IRC20:53
harlowjathen we'll have the best library and the usage in openstack in many places :)20:53
harlowjaa win for all20:53
harlowjasound good to everyone? :)20:54
*** jmontemayor has quit IRC20:54
harlowjasweet! and just in time20:55
harlowjaany further stuff, #openstack-state-management20:55
harlowjakeep up the good work all!20:55
*** meteorfox has quit IRC20:55
changblharlowja, sounds good20:55
akarpinska1agree :)20:56
*** openstack changes topic to "OpenStack Meetings ||"20:56
openstackMeeting ended Thu Aug  1 20:56:26 2013 UTC.  Information about MeetBot at . (v 0.1.4)20:56
openstackMinutes (text):
*** enikanorov has quit IRC21:00
*** SergeyLukjanov has quit IRC21:00
*** cwolferh has quit IRC21:00
*** akarpinska1 has quit IRC21:01
*** benl_ has quit IRC21:01
*** kchenweijie has left #openstack-meeting21:01
*** cwolferh has joined #openstack-meeting21:03
*** rpodolyaka has quit IRC21:03
*** epim has joined #openstack-meeting21:04
*** rpodolyaka has joined #openstack-meeting21:04
*** enikanorov has joined #openstack-meeting21:05
*** vipul-away is now known as vipul21:05
*** henrynash has joined #openstack-meeting21:05
*** IlyaE has quit IRC21:06
*** benl_ has joined #openstack-meeting21:06
*** enikanorov_ has joined #openstack-meeting21:07
*** enikanorov has quit IRC21:09
*** MarkAtwood has joined #openstack-meeting21:12
*** venkatesh has joined #openstack-meeting21:14
*** jecarey has quit IRC21:20
*** gyee has quit IRC21:24
*** markvan has quit IRC21:29
*** whenry has joined #openstack-meeting21:29
*** whenry has quit IRC21:30
*** whenry has joined #openstack-meeting21:30
*** neelashah has quit IRC21:35
*** glikson has quit IRC21:35
*** edmund has joined #openstack-meeting21:35
*** venkatesh has quit IRC21:37
*** jasondotstar has quit IRC21:38
*** fifieldt has joined #openstack-meeting21:40
*** pentameter has quit IRC21:44
*** burt has quit IRC21:49
*** markpeek has quit IRC21:49
*** lbragstad has quit IRC21:53
*** branen__ has joined #openstack-meeting21:53
*** zehicle_at_dell has quit IRC21:54
*** eglynn has quit IRC21:55
*** pcm_ has joined #openstack-meeting21:55
*** spzala has joined #openstack-meeting21:55
*** MarkAtwood has quit IRC21:56
*** Swami has quit IRC21:56
*** spzala has quit IRC21:56
*** pcm_ has quit IRC21:56
*** spzala has joined #openstack-meeting21:56
*** branen_ has quit IRC21:57
*** pcm_ has joined #openstack-meeting21:57
*** Swami has joined #openstack-meeting21:57
*** epim has quit IRC22:00
*** epim has joined #openstack-meeting22:01
*** SumitNaiksatam has quit IRC22:02
*** lexinator has joined #openstack-meeting22:02
*** SumitNaiksatam has joined #openstack-meeting22:04
*** lexinator has quit IRC22:06
*** reed has quit IRC22:07
*** markpeek has joined #openstack-meeting22:07
*** henrynash has quit IRC22:08
*** lcazares has joined #openstack-meeting22:10
*** beagles has quit IRC22:11
lcazaresdoes anybody know about QA meetings? I though it was held Weekly on Thursdays at 1700 UTC?22:14
*** changbl has quit IRC22:14
clarkblcazares: that sounds correct22:14
*** rnirmal has quit IRC22:15
clarkblcazares: there was a meeting today at 1700UTC for QA22:15
*** jasondotstar has joined #openstack-meeting22:15
*** spzala has quit IRC22:16
*** stevemar has quit IRC22:19
*** eglynn has joined #openstack-meeting22:19
*** thang_ has quit IRC22:19
*** SumitNaiksatam has quit IRC22:20
*** henrynash has joined #openstack-meeting22:20
*** lastidiot has quit IRC22:21
*** henrynash has quit IRC22:21
*** mrodden has quit IRC22:27
*** obondarev has quit IRC22:27
*** MarkAtwood has joined #openstack-meeting22:28
*** obondarev has joined #openstack-meeting22:28
*** plomakin has quit IRC22:29
*** agordeev has quit IRC22:29
*** emagana has quit IRC22:29
*** plomakin has joined #openstack-meeting22:29
*** benl_ has quit IRC22:32
*** tedross has quit IRC22:32
*** vijendar has quit IRC22:32
*** benl_ has joined #openstack-meeting22:32
*** krtaylor has quit IRC22:33
*** ogelbukh has quit IRC22:33
*** lexinator has joined #openstack-meeting22:39
*** AlanClark has quit IRC22:43
*** agordeev has joined #openstack-meeting22:43
*** lexinator has quit IRC22:43
*** meteorfox has joined #openstack-meeting22:44
*** ogelbukh has joined #openstack-meeting22:44
*** IlyaE has joined #openstack-meeting22:45
*** mrodden has joined #openstack-meeting22:47
*** galstrom is now known as galstrom_zzz22:48
*** lexinator has joined #openstack-meeting22:49
*** IlyaE has quit IRC22:52
*** IlyaE has joined #openstack-meeting22:53
*** IlyaE has quit IRC22:55
*** benl_ has quit IRC22:55
*** adrian_otto has quit IRC22:59
*** salv-orlando has quit IRC23:02
*** emagana has joined #openstack-meeting23:08
*** fnaval_ has quit IRC23:09
*** bgorski has quit IRC23:10
*** kebray has quit IRC23:17
*** changbl has joined #openstack-meeting23:24
*** benl_ has joined #openstack-meeting23:26
*** markpeek has quit IRC23:26
*** egallen has joined #openstack-meeting23:29
*** benl_ has quit IRC23:33
*** eglynn has quit IRC23:37
*** brucer_ has joined #openstack-meeting23:39
*** brucer has quit IRC23:40
*** nachi_ has quit IRC23:45
*** nachi has quit IRC23:45
*** dani4571 has quit IRC23:45
*** whenry has quit IRC23:51
*** SumitNaiksatam has joined #openstack-meeting23:52
*** lastidiot has joined #openstack-meeting23:52

Generated by 2.14.0 by Marius Gedminas - find it at!