Tuesday, 2014-09-02

*** amitgandhinz has joined #openstack-zaqar01:00
*** amitgandhinz has quit IRC01:05
openstackgerritPeng Fei Wang proposed a change to openstack/zaqar: Not permitted to delete pools which are used by flavor  https://review.openstack.org/11770601:40
wpfflwang:   would you please check https://review.openstack.org/#/c/117706/ again?01:41
*** vkmc has quit IRC01:44
flwangwpf: looking...01:47
wpfthanks01:47
flwangwpf: I still have question about the https://review.openstack.org/#/c/117706/3/zaqar/queues/storage/mongodb/pools.py01:49
wpfflwang:  what's that01:50
flwangwpf: IIUC, you're searching flavor with the name, right?01:50
wpfflwang:  I am searching the flavor with pool name01:51
wpfbut not the flavor name01:51
flwangwpf: ah, got it01:52
wpf:P01:52
flwangI would say the short name in mongo is hard to reflect its meaning01:52
wpfyes,  I have to go to the header of the source file to get it01:53
flwangsorry for the misunderstanding01:55
wpfnp01:55
flwangbtw, this is the architecture of the rating system of us, we(catalyst it) will opensource it soon  http://paste.openstack.org/show/104046/01:56
wpfgreat, I will check it later, Thanks01:57
wpfwill it be a separated project ?01:57
flwangI think so, but totally depends :)01:58
wpfgot it01:58
*** jeffrey4l has quit IRC02:24
*** wpf has quit IRC02:58
*** wpf has joined #openstack-zaqar03:09
*** wpf has quit IRC03:17
*** prashanthr_ has joined #openstack-zaqar03:41
*** prashanthr_ has quit IRC03:50
*** wpf has joined #openstack-zaqar03:57
*** amitgandhinz has joined #openstack-zaqar04:02
*** amitgandhinz has quit IRC04:06
*** chandankumar has joined #openstack-zaqar04:11
*** wpf has quit IRC04:12
*** wpf has joined #openstack-zaqar04:31
*** wpf has quit IRC04:38
*** chandankumar has quit IRC04:38
*** chandankumar has joined #openstack-zaqar04:51
*** amitgandhinz has joined #openstack-zaqar05:02
*** amitgandhinz has quit IRC05:07
*** wpf has joined #openstack-zaqar05:14
*** wpf has quit IRC05:21
*** prashanthr_ has joined #openstack-zaqar05:28
*** flwang1 has joined #openstack-zaqar05:31
*** wpf has joined #openstack-zaqar05:33
*** wpf has quit IRC05:40
*** wpf has joined #openstack-zaqar05:42
*** flwang1 has quit IRC05:48
*** wpf has quit IRC05:49
*** wpf has joined #openstack-zaqar05:50
*** wpf has quit IRC05:57
*** wpf has joined #openstack-zaqar06:00
*** amitgandhinz has joined #openstack-zaqar06:03
*** amitgandhinz has quit IRC06:07
*** wpf has quit IRC06:08
openstackgerritOpenStack Proposal Bot proposed a change to openstack/zaqar: Imported Translations from Transifex  https://review.openstack.org/11826006:08
*** jeffrey4l has joined #openstack-zaqar06:15
*** wpf has joined #openstack-zaqar06:17
*** wpf has quit IRC06:24
*** flaper87|afk is now known as flaper8706:26
*** jimhoagland has joined #openstack-zaqar06:28
*** jimhoagland has quit IRC06:32
*** wpf has joined #openstack-zaqar06:44
*** prashanthr_ has quit IRC06:48
*** wpf has quit IRC06:51
*** wpf has joined #openstack-zaqar06:59
*** chandankumar has quit IRC07:01
*** openstackgerrit has quit IRC07:02
*** amitgandhinz has joined #openstack-zaqar07:04
wpfflaper87:  ping07:06
flaper87wpf: pong07:06
wpfflaper87:  you deliver your PS about checking pool in flavor first ,  then my PS which checking flavor in pool failed ,  -:)07:07
*** prashanthr_ has joined #openstack-zaqar07:07
wpfsince the recursive use07:07
wpfin __init__  , you refer to the pool controller,  I refer to the flavor controller,    :P,07:08
wpfI'd fixed it07:08
wpfprashanthr_:  ping07:08
*** amitgandhinz has quit IRC07:08
flaper87wpf: hahaha, in my defense, I didn't know it got merge until very late at night07:10
flaper87wpf: as promissed, we discussed it at the meeting07:11
flaper87wpf: your patch is good to go07:11
wpfglad to hear that,  I will deliver the PS soon07:11
*** echevemaster has quit IRC07:16
*** jeffrey4l has quit IRC07:21
*** prashanthr_ has quit IRC07:31
*** jeffrey4l has joined #openstack-zaqar07:33
*** flaper87 is now known as flaper87|afk07:43
*** flaper87|afk is now known as flaper8707:48
*** wpf has quit IRC07:53
*** amitgandhinz has joined #openstack-zaqar08:04
*** amitgandhinz has quit IRC08:09
*** jeffrey4l has quit IRC08:09
*** jeffrey4l has joined #openstack-zaqar08:36
*** flaper87 is now known as flaper87|afk08:37
*** flaper87|afk is now known as flaper8708:50
*** amitgandhinz has joined #openstack-zaqar09:05
*** amitgandhinz has quit IRC09:09
*** wpf has joined #openstack-zaqar09:14
*** wpf has quit IRC09:22
*** flwang1 has joined #openstack-zaqar09:42
*** amitgandhinz has joined #openstack-zaqar10:05
*** amitgandhinz has quit IRC10:10
*** flwang1 has quit IRC10:37
*** wpf has joined #openstack-zaqar10:52
*** wpf has quit IRC10:59
*** amitgandhinz has joined #openstack-zaqar11:06
*** amitgandhinz has quit IRC11:11
*** wpf has joined #openstack-zaqar11:15
*** vkmc has joined #openstack-zaqar12:00
*** vkmc has quit IRC12:00
*** vkmc has joined #openstack-zaqar12:00
vkmcmorning!12:02
flaper87vkmc: goooooooooooooooooooooooooooooood morning12:04
flaper87vkmc: today I worked on the headers changes blueprint so we can rid of it12:04
flaper87we can get rid*12:04
flaper87https://review.openstack.org/#/q/status:open+project:openstack/zaqar+branch:master+topic:bp/api-v1,n,z12:04
flaper87there are 3 patches there, ready to be reviewed12:04
flaper87they should be easy to review12:04
flaper87as in, fast and painless12:04
vkmcflaper87, that's awesomeeeeee12:05
vkmclemme check that :D12:05
flaper87I won't be around much this afternoon because I'm heading back home. I'd really appreciate it if you can ask kgriffs|afk and malini to review those patches too12:05
flaper87also, I updated our graduation wiki: https://wiki.openstack.org/wiki/Zaqar/Incubation/Graduation#Graduation_Requirements12:06
flaper87I could use some review there12:06
vkmcsure no problem, I can do that12:06
flaper87On a very very very related note, I just remembered the penguins pictures you sent last year12:06
flaper87:P12:07
flaper87Did they come visiting this year too? :D12:07
*** amitgandhinz has joined #openstack-zaqar12:07
flaper87those penguins were so cool12:07
vkmchaha yeah, they come to breed every year on June12:08
flaper87vkmc: mmh, wait. Weren't you based in Buenos Aires? I didn't know it had beaches.12:08
* flaper87 checks the map12:08
vkmcI live in Bahia Blanca, to the south12:09
flaper87s/had/has/12:09
flaper87ohhh, that explains it12:09
vkmcbut I have family in Puerto Madryn (Patagonia)12:09
vkmcwhich is even further south12:10
flaper87ahhh, which  is probably where the penguins love to go :D12:11
flaper87I need to add that to my "Before Dying" list12:11
*** amitgandhinz has quit IRC12:12
flaper87Go and feed a wild penguin12:12
vkmcexactly! :)12:12
vkmcyou are welcome to come12:12
vkmcyou cannot take them home12:12
flaper87if it is wearing a red hat, that's a bonus12:12
vkmcthat's the only downside of it12:12
flaper87yeah, I remember you said :/12:13
flaper87well, in my case it's probably good12:13
flaper87I can't even keep a plant alive12:13
vkmclol12:15
flaper87vkmc: kgriffs|afk malini alcabrera|afk I saw some patches that fix typos and help strings. Lets hold back on approving those until we're in FeatureFreeze. The gate is quite loaded now12:15
vkmcroger that12:16
vkmcoh btw, are you familiar with how to add a requirement to the docs gate?12:17
vkmcwhere should that be?12:17
vkmcI couldn't find that yesterday12:17
vkmcis for the API ref, it's failing because it doesn't have python-zaqarclient http://logs.openstack.org/90/116390/8/check/gate-zaqar-docs/6f39805/console.html12:18
flaper87vkmc: I've never done that but I can help you figuring it out12:18
flaper87why do we depend on zaqarclient for the docs?12:18
vkmcflaper87, the bench tool is using zaqarclient12:19
flaper87aaaaaaahhh, right. in order to generate things it has to import python modules12:19
vkmcand it looks like autodoc requires to have all the dependencies12:19
flaper87wait12:21
flaper87I think it should go in zaqar's requirements file12:21
flaper87add python-zaqarclient to the requirements file12:21
flaper87vkmc: ^12:22
vkmcI added it yesterday and abandoned the patch because it thought it wasn't a good idea to depend on our client12:22
vkmcdo you think it's harmless?12:22
flaper87It's harmless but I don't like it anyway12:23
vkmccurrently that requirement is in the bench-requirements.txt12:23
flaper87mmh12:23
flaper87so wait12:23
flaper87tox -evenv -- python setup.py build_sphinx12:23
flaper87vkmc: ^ add the deps var to the venv section in tox.ini12:24
vkmc:D12:24
flaper87vkmc: in other words. Add this https://github.com/openstack/zaqar/blob/master/tox.ini#L1412:24
flaper87here https://github.com/openstack/zaqar/blob/master/tox.ini#L3912:24
flaper87and make sure bench-requirements is in there12:25
flaper87#FuckTheSystem12:25
vkmcyaaaaay12:25
flaper87you should do the same for the `docs` seciont12:25
flaper87section12:25
flaper87vkmc: ^12:25
* flaper87 wonders why that gate uses venv instead of docs12:26
flaper87Ignorance is bless, I guess12:26
vkmcadding bench-requirements to testenv should do the trick12:27
vkmctestenv:docs specializes testenv12:27
vkmcor do you mean another docs section?12:28
flaper87I meant that one, yes!12:28
flaper87ok12:28
vkmcthanks Fla :) will try that out12:29
*** wpf has quit IRC12:43
*** itisit has joined #openstack-zaqar12:44
flaper87bbl13:05
flaper87reviews everyone. Today is the last chance to approve patches for new features13:06
flaper87everything else will have to go through FFE13:06
flaper87have a great day13:06
*** flaper87 is now known as flaper87|afk13:06
vkmcttfn!13:07
* vkmc reviewing13:07
*** amitgandhinz has joined #openstack-zaqar13:07
*** amitgandhinz has quit IRC13:12
*** ametts has joined #openstack-zaqar13:20
*** malini1 has joined #openstack-zaqar13:39
*** itisit has quit IRC13:42
malini1hello!13:44
vkmchi malini1!13:48
*** itisit has joined #openstack-zaqar13:48
malini1heyy vkmc!13:48
malini1I just noticed that we are in the TC meeting today https://wiki.openstack.org/wiki/Governance/TechnicalCommittee13:49
vkmcmalini1, yup! today at 20UTC we have the first meeting :)13:51
*** amitgandhinz has joined #openstack-zaqar14:03
*** openstackgerrit has joined #openstack-zaqar14:06
*** cpallares has joined #openstack-zaqar14:09
*** kgriffs|afk is now known as kgriffs14:15
*** sgotliv has joined #openstack-zaqar14:20
*** malini1 has quit IRC14:27
*** malini1 has joined #openstack-zaqar14:27
*** wpf has joined #openstack-zaqar14:39
*** alcabrera|afk is now known as alcabrera14:45
*** wpf has quit IRC14:47
vkmckgriffs, o/16:11
kgriffshowdy16:11
vkmcheya :)16:12
*** earnThis has joined #openstack-zaqar16:12
vkmchow is it going? anything I could do to help you with the Redis patch?16:12
vkmchi earnThis!16:12
earnThisHi vkmc, how is everything?16:13
kgriffsvkmc: glad you asked!16:14
openstackgerritKurt Griffiths proposed a change to openstack/zaqar: Fix Redis message controller getting stuck in while loop  https://review.openstack.org/11839216:14
openstackgerritKurt Griffiths proposed a change to openstack/zaqar: Implement claim and message expiration logic for Redis  https://review.openstack.org/11839316:14
openstackgerritKurt Griffiths proposed a change to openstack/zaqar: Calculate stats dynamically instead of using side counters  https://review.openstack.org/11839416:14
kgriffsvkmc: I could use help writing a command script to call the driver's gc function. My thought was that is could be run as a cron job on the web heads..16:15
kgriffsit could just load the zaqar.conf file16:15
vkmcearnThis, all good! and you? :)16:15
kgriffsneed to make sure that it calls the pool driver's gc if pooling is enabled, which will in turn call all the drivers' GCs16:15
vkmckgriffs, I see16:16
kgriffsAlso, there is a TODO in the driver gc function - it should check the last GC time and skip GC if the last one was started recently16:16
kgriffs(since deployers will want to run this on multiple web heads, perhaps all of them, for HA)16:16
kgriffsvkmc: any doc patches I can help review?16:17
vkmcit makes sense yes... let's make it happen :)16:17
kgriffsthanks!16:17
vkmcnp!16:17
vkmckgriffs, yes please, this one should get merged ASAP https://review.openstack.org/#/c/114530/16:18
vkmcflaper87|afk already gave me his blessing16:18
vkmcother docs patch are having problems with dependency, I have to find a workaround for that16:18
*** prashanthr_ has joined #openstack-zaqar16:18
prashanthr_good morning :)16:19
vkmcand... flaper87|afk asked us to review his patches for the API v1 https://review.openstack.org/#/q/status:open+project:openstack/zaqar+branch:master+topic:bp/api-v1,n,z16:19
vkmcyooo prashanthr_ o/16:19
kgriffskk16:19
prashanthr_vkmc : ha ha :)16:19
prashanthr_good morning16:19
vkmcgood evening :)16:20
prashanthr_thank you16:20
earnThisvkmc, all is good up here as well16:20
vkmcearnThis, that's great to hear16:21
vkmcearnThis, I'm afraid the bug you were looking into has been taken and fixed for somebody else16:22
vkmcearnThis, here is the review if you want to take a look https://review.openstack.org/#/c/118094/16:22
prashanthr_kgriffs: Good morning :)16:22
kgriffso/16:22
kgriffsgood evening!16:22
prashanthr_thank you :)16:23
prashanthr_Was browsing through redis code today :) looks so different from where I left and so awesome now !16:23
earnThisvkmc, yea i know, i subscribed to the bug reports,  when i got a chance to look at it this weekend i was notified of the fix.  bummer16:24
*** wpf has joined #openstack-zaqar16:24
prashanthr_kgriffs: I am planning to start work on the driver again from tomorrow.  Can you give me a brief overview from where I could restart contributing?16:25
kgriffsprashanthr_: ah, good question16:25
vkmcearnThis, yeah :( but well, there are another fish in the sea!16:25
earnThisvkmc: exactly16:27
kgriffshmmm16:27
vkmcmaybe prashanthr_ want to take the gc script?16:28
kgriffsso, I think we will need to close this blueprint today16:28
kgriffshttps://blueprints.launchpad.net/zaqar/+spec/redis-storage-driver16:28
vkmcI'm ok with it :)16:28
kgriffsthat means anything left under work items as TODO will need to be moved to a bug(s)16:28
prashanthr_vkmc: That would be a good place to start with.16:28
kgriffsprashanthr_: did you see my thoughts on that script above?16:29
kgriffsactually...16:29
kgriffswe need that script today16:29
kgriffsI think the other TODO items could wait16:29
prashanthr_kgriffs: No. I have not yet seen that.16:29
kgriffsok, let me recap16:30
kgriffsneed to make sure that it calls the pool driver's gc if pooling is enabled, which will in turn call all the drivers' GCs16:30
vkmcprashanthr_, kgriffs thoughs about gc here http://paste.openstack.org/show/104830/16:30
kgriffswhat vkmc said ^^^16:30
kgriffs:)16:30
vkmchaha :)16:31
prashanthr_vkmc: ROFL16:31
prashanthr_:)16:31
kgriffsok, it doesn't matter to me who does it, but we need it done in the next few hours16:31
vkmcquicker paster in the far west16:31
kgriffsit will need to depend on my latest patches16:31
kgriffs...which I just submitted a few minutes ago, :p16:32
prashanthr_kgriffs: Next few hours might be tough for me :(16:32
kgriffsvkmc: possible for you? If not, I'll have to try and carve out time to do it16:32
kgriffslike I said, that is the last outstanding item - other TODOs can wait until tomorrow/later this week16:33
*** sgotliv has quit IRC16:34
vkmckgriffs, sure thing, I may ask you for some guidance but I think I can manage16:35
prashanthr_kgriffs: What's to be done for redis clusters ?16:35
kgriffsok. I was thinking you could register an entry point for the command16:35
kgriffsprashanthr_: idk. that was my question, actually16:35
*** earnThis_ has joined #openstack-zaqar16:35
kgriffsdoes redis-py magically work with cluster and handle failover?16:36
prashanthr_kgriffs: looks like redis-py does not support clusters16:37
* prashanthr_ first impression16:37
kgriffsprashanthr_: oh oh.16:38
kgriffswell, we may be able to call that a bug and fix it tomorrow16:38
kgriffsprashanthr_: can you work on that?16:38
prashanthr_kgriffs: Sure I can.16:38
*** earnThis has quit IRC16:38
prashanthr_would this come under j-3 deadline ?16:38
kgriffshmmm16:39
kgriffswe need some way to guarantee HA16:40
*** earnThis_ has quit IRC16:40
kgriffsif we can't guarantee 100% durability due to async replication using redis master-slave functionality that comes out of the box, then we may need to push that to kilo16:40
kgriffshmmm16:41
kgriffsprashanthr_: does redis cluster always shard keys across nodes?16:41
kgriffshmmm16:42
kgriffsif so, we can't use it. It is still a WIP as well.16:42
kgriffsI think this is what we actually want: http://redis.io/topics/sentinel16:43
prashanthr_kgriffs: Yes it does shard keys16:44
prashanthr_I will look into redis sentinel16:44
kgriffsok.16:45
*** earnThis has joined #openstack-zaqar16:45
kgriffsstep 1 is to try and get redis-py working with sentinel16:45
vkmckgriffs, regarding the gc script, you were thinking on a bash script right?16:46
kgriffsstep 2 would be to see if there is any trick we can do to "wait" until a message has been replicated to a secondary node. Perhaps by polling secondaries. That would guarantee a message isn't lost if the master crashes before being able to replicate to the slave16:46
kgriffsvkmc: nah, just a python program16:46
kgriffsala marconi-server16:47
kgriffscmd/server.py16:47
prashanthr_kgriffs: I will work along this direction16:47
prashanthr_so we will have a new fork of redis-py ?16:48
kgriffsprashanthr_: mmm, I'd rather not if we can avoid it.16:48
prashanthr_would I have to contribute to redis-py now ?16:48
kgriffslet's see what is required to support master-slave failover16:48
kgriffsif we can do it without patching redis-py, that would be great16:49
kgriffsif there is no way we can, then we will need to submit a PR16:49
prashanthr_kgriffs: Sure.16:50
kgriffsre step 2 - hold off on that until all our other TODO items on that bp are completed16:50
kgriffs(listed under "work items")16:50
prashanthr_kgriffs: Sure.16:50
kgriffscool, sounds like a plan16:50
kgriffsvkmc: does that make sense re the script16:50
vkmckgriffs, it does!16:53
kgriffscool16:53
vkmcbrb, off to lunch :)16:53
kgriffso/16:53
vkmc\o16:53
prashanthr_brb16:56
*** prashanthr_ is now known as prashanthr_|afk16:56
*** reed has joined #openstack-zaqar16:59
*** wpf has quit IRC17:04
*** earnThis has quit IRC17:17
*** earnThis has joined #openstack-zaqar17:19
*** earnThis has quit IRC17:29
openstackgerritKurt Griffiths proposed a change to openstack/zaqar: Calculate stats dynamically instead of using side counters  https://review.openstack.org/11839417:31
openstackgerritKurt Griffiths proposed a change to openstack/zaqar: Switch Redis driver modules over to oslo.utils.timeutils  https://review.openstack.org/11841317:31
*** prashanthr_|afk has quit IRC17:34
*** cpallares has quit IRC17:39
kgriffsvkmc: reviewed https://review.openstack.org/#/c/114530/17:57
kgriffswould you like to fix them now, or in a bug patch?17:58
*** earnThis has joined #openstack-zaqar18:02
*** earnThis has quit IRC18:07
*** earnThis has joined #openstack-zaqar18:10
kgriffsmalini: ping18:18
openstackgerritKurt Griffiths proposed a change to openstack/zaqar: Switch Redis driver modules over to oslo.utils.timeutils  https://review.openstack.org/11841318:26
openstackgerritKurt Griffiths proposed a change to openstack/zaqar: Calculate stats dynamically instead of using side counters  https://review.openstack.org/11839418:26
openstackgerritKurt Griffiths proposed a change to openstack/zaqar: Implement claim and message expiration logic for Redis  https://review.openstack.org/11839318:26
malini1kgriffs: pong18:30
kgriffsmalini: I could use your help setting up a Tsung test against my bare metal cluster later this week18:30
kgriffsand hi, how are you btw. :)18:30
malini1kgriffs: sure18:30
* kgriffs needs to stop being all business18:30
malini1good :)18:30
kgriffscool, glad to hear it.18:31
malini1no worries..I have a hard time with the how are you part too :D18:31
kgriffsre tsung, I can do the legwork, but may need some hand-holding. :p18:31
malini1kgriffs: what tests/scenarios do you want to run ?18:31
kgriffsmalini1: as many as possible - whatever you already have18:32
malini1oz & co were working on automating the tsung setup18:32
kgriffsoh18:32
malini1I will chk how far along they are . if we can use tht, it'll be super easy18:32
kgriffsdefinitely18:32
kgriffsI just need something spun up in IAD18:32
malini1b/w I am going to be out next week. So I'll try to get this done by Thursday18:33
kgriffsok, that would be super great!18:33
kgriffsthanks18:34
* kgriffs owes malini1 big time18:34
malini1do you need the tsung servers in bare metal?18:34
kgriffshmmm, good question18:34
kgriffsideally, yes, to mitigate noisy neighbor18:34
kgriffsbut if it turns out to be a huge pain, then we can probably get by with VMs18:35
malini1I'll give tht a try18:35
malini1b/w you are going to be in the TC meeting today, rt?18:35
kgriffsyeah18:35
kgriffsvkmc: see my comments here. what do you think? https://review.openstack.org/#/c/114530/18:38
vkmckgriffs, replied inline!18:40
* kgriffs blushes18:40
kgriffssorry, should have hit refresh18:40
vkmchaha I *just* replied :)18:40
kgriffskapow!18:41
kgriffsre "Good point, but Zaqar will throw an exception for some operations if there is no Client-ID header. How we can make this clearer?"18:41
kgriffsI think we are conflting Client-ID with auth18:41
kgriffsauthentication does not automatically insert Client-ID or anything.18:42
vkmcyeah18:42
vkmcI think it read it on the wiki18:42
kgriffsWAH?18:42
kgriffs #docbug18:42
vkmc> If auth is not enabled, clients must provide the X-Project-Id header themselves.18:42
kgriffsperhaps project-ID header?18:42
vkmcyeah18:43
vkmcmy bad18:43
vkmchttps://wiki.openstack.org/wiki/Zaqar/specs/api/v1#Authentication18:43
kgriffsah, ok18:43
kgriffsthat works18:43
kgriffsdid you also see the comment at the very bottom18:44
kgriffs"shows default" ==> "shows the default"18:44
vkmcyeap, the 'Done' comment never arrived :p18:44
kgriffsok18:44
kgriffsthen on these18:44
kgriffshttps://review.openstack.org/#/c/114530/5/doc/user-guide/zaqar-config-ref/common/tables/zaqar-drivers.xml18:44
vkmcthe only comment that worries me a bit is the sqlite parameter in drivers18:44
kgriffswe can hit those in a followup patch18:44
vkmclet's do so18:45
kgriffsyeah, something is odd there - probably requires looking at how that default option is defined in the code18:45
kgriffsrock on18:45
kgriffsthanks!18:45
openstackgerritVictoria Martínez de la Cruz proposed a change to openstack/zaqar: Zaqar configuration reference docs  https://review.openstack.org/11453018:46
vkmcnp :)18:47
kgriffsalso in a future patch (NIT):18:49
kgriffs"The zaqar.conf configuration file is an INI file format as explained in"18:49
kgriffs"is an" ==> "uses"18:49
kgriffs"is an" ==> "uses an"18:49
*** flaper87|afk is now known as flaper8718:49
* vkmc hides18:49
kgriffswait18:50
kgriffs"If auth is not enabled, clients must provide the authentication header themselves."18:50
flaper87o/18:50
kgriffswere you planning to put that in a followup patch?18:50
vkmcoops no18:50
vkmcI change authentication header for X-Project-ID18:50
vkmcand fix the nit18:50
flaper87vkmc: kgriffs can I get +As on these patches ? https://review.openstack.org/#/q/status:open+project:openstack/zaqar+branch:master+topic:bp/api-v1,n,z18:51
flaper87:D :D :D18:51
flaper87Anything I should review?18:51
kgriffshttps://review.openstack.org/#/c/118301/18:51
kgriffshttps://review.openstack.org/#/c/118301/1/zaqar/common/transport/wsgi/helpers.py18:51
kgriffsjust a nit there18:52
kgriffsflaper87: pls take a look at my redis patches18:52
kgriffspretty please with a cherry on top. :D18:52
kgriffsbrb (lunch)18:53
*** cpallares has joined #openstack-zaqar18:53
flaper87kgriffs: kk, lemme fix that18:53
flaper87kgriffs: TC meeting in 1h18:54
flaper87:)18:54
*** ametts has quit IRC18:54
openstackgerritFlavio Percoco proposed a change to openstack/zaqar: Don't return content_location anymore  https://review.openstack.org/11830418:55
openstackgerritFlavio Percoco proposed a change to openstack/zaqar: Make Client-ID a required header  https://review.openstack.org/11831518:55
openstackgerritFlavio Percoco proposed a change to openstack/zaqar: Make X-Project-ID a required header  https://review.openstack.org/11830118:55
flaper87kgriffs: vkmc ^^^^^^^^^^^^^^ Can I haz +2A ?18:55
vkmcflaper87, will think about it18:57
flaper87:018:57
vkmcI'm kidding with ya :)19:00
*** saera has joined #openstack-zaqar19:01
*** wpf has joined #openstack-zaqar19:02
*** jeffrey4l has quit IRC19:02
openstackgerritVictoria Martínez de la Cruz proposed a change to openstack/zaqar: Zaqar configuration reference docs  https://review.openstack.org/11453019:04
vkmckgriffs, I added the whole context for the Project-ID header role in authentication... just in case it's misleading19:14
flaper87vkmc: I'll wait for kgriffs to review that docs patch19:15
flaper87:D19:15
vkmcflaper87, sure thing19:16
*** jeffrey4l has joined #openstack-zaqar19:22
*** ametts has joined #openstack-zaqar19:24
vkmcok, do you guys agree to add python-crontab for the gc cron job or do you have something better in mind?19:24
*** malini1 has quit IRC19:25
*** earnThis has quit IRC19:25
vkmcflaper87, &19:25
vkmc^19:26
kgriffshmm19:26
vkmcor kgriffs :)19:26
flaper87mmhh19:26
kgriffsfor now, could we just document this so operator can do it manually?19:26
*** earnThis has joined #openstack-zaqar19:26
kgriffsI mean, they just need to add a line to crontab to run zaqar-gc command (or whatever we call it)19:26
vkmcsure19:27
kgriffswe could just recommend running the script once a minute19:27
flaper87+1 to leave this to the operator19:27
kgriffsor they can use a different tool if they want19:27
vkmcok :)19:27
kgriffs(cron-like tool, I mean, to run the script)19:28
vkmcyeah, os level19:28
kgriffsI think all we need to do is register the entry point with zaqar is installed19:28
kgriffsflaper87:19:32
kgriffshttps://review.openstack.org/#/c/118301/2/zaqar/common/transport/wsgi/helpers.py19:32
kgriffsDo we have a bug somewhere for cleaning up error response messages across the board?19:32
kgriffsif not, we should. :)19:32
kgriffsthey are a form of docs19:33
flaper87agreed19:33
flaper87I don't think we have one19:33
flaper87I remember seeing one19:33
flaper87but that was probably fixed19:33
flaper87I'll look and create one if there isn't one19:33
kgriffscool, much thanks!19:34
openstackgerritCindy Pallares proposed a change to openstack/zaqar: First patch and first review docs  https://review.openstack.org/11536919:36
kgriffsoh, hey, that's a nice little patch. should be easy to review, heh heh19:36
* kgriffs drops link https://review.openstack.org/#/c/118392/19:36
* kgriffs keeps on walking, trying to act nonchalant19:37
vkmckgriffs, I'm thinking... instead of doing a script for gc19:42
vkmcwouldn't be easier to add a gc-period conf19:42
vkmcand call it every certain value of time?19:43
vkmcbecause if we want to write an isolated script for it... we need to recover the instance of the server, get the controllers and then call the gc function19:43
vkmcor maybe I'm thinking that wrong19:44
kgriffshmmm19:44
*** saera has quit IRC19:44
vkmcplus, I'm not certain on how safe it is if we leave it to the operator19:45
kgriffsso, regarding the first point about how to wire things up19:46
kgriffsyou could instantiate Bootstrap19:46
kgriffsand then just use bootstrap.storage19:46
vkmcall right.. that is how I was doing it19:47
vkmcserver = bootstrap.Bootstrap(conf)19:47
kgriffsoh, don't try to get controllers19:47
kgriffsjust do server.storage.gc()19:47
vkmcoh <319:47
kgriffsIn one of my patches I added a gc method to the storage class19:48
vkmcyeah, here 'Implement claim and message expiration logic for Redis'19:48
vkmcI added the dependency to it19:49
kgriffsregarding your second point... yes it would be one less thing for the operator to worry about if we just did the gc19:49
kgriffsyou could do that as a daemon with it's own timer19:49
kgriffsor you could do it "inline" - fire off a worker thread or something when the driver is instantiated19:49
kgriffsmy thought was for now to just optimize for what is quickest to code19:50
vkmcyeah19:50
kgriffswhich means not worrying about trying to do our own schduler19:50
vkmclet's have it done and we can optimize later :)19:50
vkmclet's follow the first approach19:50
vkmcwith a 'regular' amount of time19:51
vkmcand then we can make it configurable19:51
vkmcor do it inline19:51
*** reed has quit IRC19:51
kgriffsmmm, I still think cron job is even easier for us19:51
kgriffs(than doing a daemon)19:51
kgriffswhat do you think?19:51
kgriffsflaper87: thoughts?19:52
vkmcyeah it's easier, that way we simply instantiate boostrap and call the gc function in storage19:52
kgriffsvkmc: with a daemon you have to bring in upstart/systemd or whatever to keep it always running19:52
vkmcyeah19:53
kgriffsthe benefit is that you can run more frequently than cron allows, but I don't think we necessarily need that here19:53
vkmcI don't think that too19:54
vkmc(meeting in 5!)19:54
kgriffsI mean, we can always make it fancier later... but right now something is a whole lot better than nothing, so I vote for doing the simplest thing that could possibly work. :p19:54
vkmctrue that :D19:55
* flaper87 reads backlog19:55
flaper87mmh, yeah. Probably a cron job is better for now19:55
flaper87I'd like to avoid playing with daemons and adding more pids to monitor19:55
flaper87ok, everyone in #openstack-meeting19:56
vkmc\o/19:57
flaper87May the force be with you19:57
kgriffsoh be wise. what can I say more?19:59
earnThishi all, is it ok for a newbie to sit in on the meeting?20:00
flaper87earnThis: absolutely20:00
flaper87earnThis: and feel free to speak up if you feel like it20:00
kgriffsplease do20:00
flaper87earnThis: FYI, this is the graduation meeting (first of 2) for Zaqar20:01
earnThisthanks and flaper87, good to know20:01
*** yograterol has joined #openstack-zaqar20:03
*** malini1 has joined #openstack-zaqar20:12
*** malini1 has quit IRC20:17
*** malini1 has joined #openstack-zaqar20:17
*** sgotliv has joined #openstack-zaqar20:34
*** sgotliv has quit IRC20:36
*** sgotliv has joined #openstack-zaqar20:36
*** flwang1 has joined #openstack-zaqar20:36
*** flwang1 has quit IRC20:37
*** ekarlso has joined #openstack-zaqar20:39
ekarlsono integration fo you guys yet ?20:39
kgriffsTBD20:48
notmynameekarlso: I'm guessing flaper87 has a lot of adrenaline flowing right now (based on my experience with TC meetings)20:49
ekarlso:p20:50
ekarlsonotmyname: what's swift's usecase ?20:50
notmynameekarlso: 2 off the top of my head20:50
notmyname1) stop using swift itself as a queue20:51
notmynameright now we use "queues" in swift to implement a few features20:51
notmynameeg container sync, expiring objects, container reconciler (for policies)20:51
notmynamethe current method is to make a container and use the listing as a queue of stuff to work on. I'd like to explore zaqar for this20:52
notmyname2) I'd like to explore zaqar for global replication (ie region to region)20:53
flaper87notmyname: oh yeah, holding it to avoid saying stupid thing20:53
notmyname3) zaqar functionality is _great_ for doing log processing/utilization/etc (shhh don't say this in the TC meeting or you'll be told that ceilometer is fine)20:53
notmynameflaper87: I completely understand what you're feeling right now. step 1: go get a beer and vent. step 2: jump through the hoops :-(20:54
notmynameekarlso: so that's my off-the-top-of-my-head use cases for zaqar in swift20:54
ekarlsonotmyname: :D20:55
notmynamenote, those are a service thing, ie infrastructure, rather than some end-user functionality20:55
notmyname(to counter a point made in the meeting)20:55
*** alcabrera is now known as alcabrera|afk20:57
notmynameekarlso: I don't know if zaqar would be used in each of those cases or not, but _definitely_ worth exploring20:57
flaper87notmyname: does Whisky work?20:58
flaper87I beat you mean anything with alcohol20:58
flaper87:D20:58
notmynameekarlso: not only that, but you can talk to cloud providers (especially the rackspace cloud files guys) about the reality that their customers are today using swift as a queue and it's really terrible for ops20:58
flaper87anyway, thanks for your support there guys20:58
notmynameflaper87: whisky and whiskey both are fine. my personal preference is tequila20:58
flaper87notmyname: The *first* shot of tequila is always a good idea20:59
flaper87:D20:59
ekarlsoiu live close to Imperia btw flaper87 ?20:59
notmynameflaper87: if you're doing shots, you're doing it wrong. fine tequila is to be sipped :-)20:59
notmynameflaper87: I'm actually kindof shocked to see data plane vs control plane be an issue. has that come up before as a blocker (not the misconceptions, but that being a blocked-by-policy thing)?21:00
flaper87ekarlso: not that far but I wouldn't call it close. I'm based in Lake Como21:01
flaper87notmyname: yup, it was last time21:01
vkmcI felt there is certain interest to get the project integrated21:02
vkmcbut there are some misconceptions of what Zaqar is and what is the state of it21:02
notmynameflaper87: wow. but there are many other projects that do data plane things21:02
kgriffsttx said something about mordred having strong feeling around data-plane vs. control plane. I wonder if he is the main driver of that concern.21:03
flaper87notmyname: exactly, that's why the concern now is: "Do we want another data plane project?"21:04
flaper87or something along that line21:04
notmynamekgriffs: he had an email a while back saying that he's been thinking of openstack as provisioning existing things. but IMo that doesn't actually reflect quite a few projects21:05
flaper87notmyname: and IMHO, that doesn't make much sense21:05
flaper87I think that's a very close view of what openstack can actually do - or actually does.21:06
flaper87ok guys, I gtg now! thanks all for being there and working hard to get us here.21:07
notmynameflaper87: so keystone (service catalogs and tokens), glance (image management), swift (object storage), ceilometer (metrics or whatever), heat (provisioning), barbican (key management) are all ok. but zaqar isn't? seems _really_ strange21:07
kgriffsflaper87: thank you21:07
notmynameie those are all examples of data plane things21:07
flaper87notmyname: you said it :D21:07
kgriffsgood examples21:07
kgriffsflaper87: you can use those as examples in your writeup21:08
flaper87kgriffs: +121:08
*** itisit has quit IRC21:08
*** flaper87 is now known as flaper87|afk21:09
ekarlsoso later on if someone wants to add a thing like Google DataFlow21:09
ekarlsowonder how that would turn out with the TC : p21:09
vkmc+121:09
vkmcthanks notmyname :)21:10
ekarlsoor any of the other "high level" products that they offer21:10
openstackgerritVictoria Martínez de la Cruz proposed a change to openstack/zaqar: Adds a manual garbage collector script  https://review.openstack.org/11846821:10
*** ametts has quit IRC21:10
vkmcflaper87|afk, still there? could you +A this? https://review.openstack.org/#/c/114530/21:11
vkmcpleeeeeeeeeease21:11
kgriffsalcabrera|afk, flwang: around? need some help on reviews: ^^^21:11
vkmckgriffs, I'm probably missing something in the gc script, let me know21:12
vkmcI have to rush now, but I'll be back later21:12
kgriffsok, thanks!21:12
ekarlsowhat's the v2 api gonna be like vs 1.1 ?21:13
flwangkgriffs: o/21:21
*** malini1 has quit IRC21:28
openstackgerritVictoria Martínez de la Cruz proposed a change to openstack/zaqar: Adds a manual garbage collector script  https://review.openstack.org/11846821:28
kgriffsekarlso: the team is still brainstorming on that. the proposed session/discussion for Paris summit would be to do further brainstorming and then decide whether it is important to do v2 for kilo, and if so, what should be in it.21:30
kgriffsekarlso: some thoughts here. the page is a little old, and I just tried to update it a little, but flaper87|afk will be the point man on this discussion.21:32
kgriffshttps://wiki.openstack.org/wiki/Zaqar/specs/api/v2.0#Marconi_API_v2.021:32
kgriffsflwang: we have a bunch of patches that could use some reviews - pretty please with a cherry on top?21:34
flwangkgriffs: yep, i'm working on that21:35
kgriffsthanks21:35
*** vkmc has quit IRC21:35
* kgriffs gives flwang a truckload of Pop-Tarts™21:35
flwangkgriffs: so busy recently for some internal stuff21:35
flwang:-D21:36
openstackgerritA change was merged to openstack/zaqar: Make X-Project-ID a required header  https://review.openstack.org/11830121:45
openstackgerritA change was merged to openstack/zaqar: Don't return content_location anymore  https://review.openstack.org/11830421:45
*** cpallares has quit IRC21:52
*** earnThis has quit IRC22:06
*** wpf has quit IRC22:06
openstackgerritA change was merged to openstack/zaqar: Zaqar configuration reference docs  https://review.openstack.org/11453022:16
*** amitgandhinz has quit IRC22:22
*** wpf has joined #openstack-zaqar22:22
*** amitgandhinz has joined #openstack-zaqar22:22
*** echevemaster has joined #openstack-zaqar22:24
*** amitgandhinz has quit IRC22:27
*** wpf has quit IRC22:29
*** vkmc has joined #openstack-zaqar22:30
*** vkmc has quit IRC22:30
*** vkmc has joined #openstack-zaqar22:30
*** sgotliv has quit IRC22:33
echevemasterflaper87|afk: Was problem of the tarball retrieved by github, with the openstack tarball works like a charm22:36
echevemasterhttps://copr.fedoraproject.org/coprs/echevemaster/openstack-zaqar/build/30465/22:36
echevemasterNow, I'll work with zaqar-client and make the review request.22:37
echevemasterFYI.22:37
vkmcechevemaster, yaay, good to hear you solve that out22:38
vkmcechevemaster, thanks22:38
echevemastervkmc: thanks to you :)22:41
echevemasterat the end was problem of the source; but would be great if the openstack tarballs have a good semantic versioning22:41
echevemasterthe tarball is named as zaqar_master.22:41
echevemasterand the launchpad tarball still has not renamed22:41
echevemasterso, the only good version that exists is this http://tarballs.openstack.org/zaqar/zaqar-master.tar.gz22:42
echevemasters/openstack tarballs/openstack zaqar tarballs22:42
*** wpf has joined #openstack-zaqar22:43
vkmcgood to know22:50
vkmcfor future reference22:50
vkmc:)22:52
*** yograterol has quit IRC23:38
*** reed has joined #openstack-zaqar23:47

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