Monday, 2015-11-30

*** openstack has joined #openstack-zaqar15:45
*** flaper87 has joined #openstack-zaqar15:46
*** vkmc has joined #openstack-zaqar15:48
*** cpallares has joined #openstack-zaqar15:49
*** dmowrer has quit IRC15:51
*** dmowrer has joined #openstack-zaqar15:51
*** dmowrer has quit IRC15:56
*** jasondotstar has joined #openstack-zaqar15:58
*** amitgandhinz has joined #openstack-zaqar16:02
*** sriram has joined #openstack-zaqar16:02
*** openstackstatus has joined #openstack-zaqar16:16
*** ChanServ sets mode: +v openstackstatus16:16
*** dmowrer has joined #openstack-zaqar16:21
*** dynarro has quit IRC16:33
*** achanda_ has quit IRC16:41
*** malini has joined #openstack-zaqar16:43
*** AAzza has quit IRC16:44
*** AAzza has joined #openstack-zaqar16:44
*** malini1 has joined #openstack-zaqar16:45
*** malini has quit IRC16:47
*** achanda has joined #openstack-zaqar16:59
*** flwang1 has joined #openstack-zaqar17:07
flwang1vkmc: ping17:09
*** boris-42_ has quit IRC17:15
*** malini1 has left #openstack-zaqar17:17
*** tej has joined #openstack-zaqar17:37
vkmcflwang1, pong17:37
*** tej has quit IRC17:37
*** tej has joined #openstack-zaqar17:39
*** achanda has quit IRC17:54
*** flwang has quit IRC18:17
*** davideagnello has joined #openstack-zaqar18:22
*** tej has quit IRC18:22
*** VeggieMeat has quit IRC18:22
*** VeggieMeat_ has joined #openstack-zaqar18:22
*** tej has joined #openstack-zaqar18:24
flwang1vkmc: did you join the weekly meeting?18:25
vkmcflwang1, freenode was down, it was cancelled18:25
flwang1vkmc: ah, ok, not bad :)18:26
vkmc:/18:26
vkmcapparently they were getting some ddos attacks18:26
vkmcso it was nonsense for three hours more or less18:26
sriramyep, I saw that on the freenode's twitter18:27
sriramI couldnt get in today morning either.18:27
mpanettaYeah it has been broken pretty badly18:27
vkmcsriram, mpanetta o/18:29
*** tej has quit IRC18:29
mpanettavkmc: Hiya :)18:29
sriramhah vkmc: o/ to you too!18:29
*** ametts has quit IRC18:33
flwang1vkmc: thanks18:33
flwang1vkmc: can you revisit https://review.openstack.org/#/c/248982/ ?18:34
vkmcflwang1, for nothing :( the only thing I could do was insanely test all the webclients and host/port combination18:34
vkmcanyhow18:34
vkmcI added in the wiki that maybe we can gather later today, at 21UTC18:34
vkmcsure18:34
*** flwang has joined #openstack-zaqar18:38
flwang1vkmc: ok, cool18:40
flwang1thanks18:40
*** flwang1 has quit IRC18:45
*** achanda has joined #openstack-zaqar18:52
*** tej has joined #openstack-zaqar19:09
*** c_soukup has joined #openstack-zaqar19:28
*** csoukup has quit IRC19:32
*** flwang1 has joined #openstack-zaqar19:46
*** dmowrer_ has joined #openstack-zaqar19:55
*** dmowrer has quit IRC19:56
*** c_soukup has quit IRC20:06
*** tej has quit IRC20:10
*** achanda has quit IRC20:31
*** amitgandhinz has quit IRC20:31
flwangryansb: are you happy with this way https://review.openstack.org/#/c/248502/4/zaqarclient/queues/v1/flavor.py to fix the object initialize issue?  for pool and flavor20:38
ryansbyeah, that works for me20:38
flwangryansb: if so, i can upload a new patch set to MD's patch, and let' get it in, because it's blocking the pool list patch for v120:39
flwangryansb: awesome :)20:39
ryansbsure sure20:39
flwangryansb: pls keep going to review the others and I will let you know when there is new patch set :D20:39
flwangcheers20:39
ryansbsure20:39
*** c_soukup has joined #openstack-zaqar20:45
*** dmowrer_ has quit IRC20:46
*** dmowrer has joined #openstack-zaqar20:46
Eva-iryansb: flwang: vkmc: mdnadeem: isn't it a meeting time?21:02
flwangEva-i: let's cancel it and we can discuss in zaqar channel21:04
flwangvkmc: ryansb: how do you think?21:05
Eva-iflwang: I think we decided to make meeting in zaqar channel21:05
ryansbI don't think it's a meeting time - we canceled the meeting this morning due to DDoS on freenode21:05
Eva-i"We will gather on #openstack-zaqar channel at 21UTC."21:05
Eva-iOkay21:05
flwangEva-i: i thought, but seems it's a little bit late for ryansb and vkmc21:05
flwangEva-i: anything you want to talk?21:06
flwangEva-i: i'm here :)21:06
ryansboh, well then21:06
ryansbI'm here :)21:06
ryansbit's only 4pm for me, so let's get going21:07
flwangryansb: cool21:07
Eva-iflwang: ryansb: how do you think, where the instruction for zaqar-bench should be located? Are non-contributors use this tool?21:07
Eva-i*using21:07
ryansbI don't really think so, I think the user base for zaqar-bench is developers looking for performance regressions21:08
Eva-iI mean, should it be located in contributor guide or user guide21:08
flwangEva-i: are you talking about docs for bench?21:08
flwangor just the bench code?21:08
Eva-iryansb: okay21:09
Eva-iflwang: docs for bench21:09
flwangEva-i: we could have a section for it in developer docs21:10
flwangnot user guide21:10
flwangEva-i: anything we should discuss about the bench docs?21:11
Eva-iflwang: ryansb: alright, I agree with you21:11
Eva-iflwang: well, I'm going to move zaqar-bench instruction from README.rst to contributor docs21:11
Eva-iflwang: README.rst will just point to the instruction21:12
flwangEva-i: works for me21:12
flwangOk, so let's go through the topics today. currently in my mind are followings:21:13
flwang1. zaqar client patches review21:13
flwang2. docs21:14
flwang3. zaqar UI21:14
flwang4. more queues attributes21:14
Eva-iOk21:15
flwang5. puppet zaqar21:15
flwangok, so firstly21:15
flwangwe still need heavily review for our client patches21:15
flwangclient/cli is the  only interface for now for zaqar21:16
flwangthat means anybody want to give zaqar a try21:16
flwangthey will install zaqar with devstack21:16
flwangand then start to create a queue, post messages, get messages21:16
flwangif there is any step failed in this process21:16
flwangthey may won't open a bug, they will just throw zaqar away and say 'holly shxt'21:17
Eva-iflwang: you're right21:18
flwangwhat i wan to say is, the zaqar client is a very critical interface for us, we should always make sure it works21:18
flwangso21:18
flwanglet's review the patch, fix any bug, and getting it work and more and more stable21:19
flwangwe have functional test for zaqar client, but unfortunately, it doesn't work now, which i'm working on21:19
ryansbwhat's stopping it from working, atm?21:20
flwangryansb: therve: if you guys can give a hand for this https://review.openstack.org/#/c/250125/ it would be awesome21:20
flwangnot sure why, but now zaqar client can't get the openstack credentials21:20
flwangbased on monty taylor's suggestion i'm using osc config, but seems it doesn't work or i still missed something21:21
flwangif we can get it work, it could be great gate for us to make sure zaqar client and zaqar server work together21:22
flwangEva-i: it would be nice if you can start review the zaqar client code21:22
Eva-iflwang: yes, I'm sorry I still haven't started. Other things in Zaqar just were more interesting for me.... But okay, I'll stop doing other things and focus on the client.21:24
flwangEva-i: no no, it's ok, i'm happy you're putting effort on zaqar, especially the docs21:28
ryansbdocs are about as important to first-timers as the client, tbh21:28
flwangryansb: totally agree21:29
openstackgerritMerged openstack/python-zaqarclient: Add `flavor` support for v2  https://review.openstack.org/24541421:29
flwangryansb: i have got some complains for our docs since we don't have published user guide for now21:30
*** tej has joined #openstack-zaqar21:30
ryansbcool deal21:30
flwangryansb: Eva-i: https://review.openstack.org/#/c/247189/21:33
flwangwe have talked with docs team to publish zaqar's config ref21:33
flwangand user guide https://blueprints.launchpad.net/openstack-manuals/+spec/zaqar-user-guide21:34
Eva-iflwang do you have a spec for user guide written?21:34
flwangbesides, we still need a api -ref like this http://developer.openstack.org/api-ref-share-v2.html21:34
flwangEva-i: not yet, you can pick if you want :)21:34
Eva-iyes, we need all three things21:34
Eva-iflwang: alright, I'll write a spec for user guide21:35
flwangEva-i: cooooooool21:36
Eva-iflwang: but for now should I focus on the client reviews?21:36
Eva-iflwang: what would you like?21:36
flwangEva-i: the docs :)21:36
Eva-iflwang: okay, nice =)21:36
flwangand you can start to review the client with slow steps :)21:37
flwangjust balance it ;)21:37
*** ametts has joined #openstack-zaqar21:37
Eva-iflwang: oh, okay21:37
flwang3. zaqar UI21:38
flwangnot sure if anybody has the UI experience in our team21:38
*** amitgandhinz has joined #openstack-zaqar21:38
flwangbut we should start to make it happen anyhow21:38
flwangnow we have created the repo21:38
Eva-iI have a small UI experience.21:39
flwangEva-i: it would be cool21:39
flwangi crated a customzed billing panel for our horizon, so i assume it should be similar21:40
Eva-iflwang: can I take a look at billing panel?21:40
flwangi will submit a start patch this/next week and let's get the queue panel work before M-221:40
flwangi mean by the end of m-221:40
flwangEva-i: sorry, now it's not open sourced21:41
flwangbut we will publish it21:41
Eva-iflwang: users will be able to work with queues through UI in horizon?21:41
flwangEva-i: yes, create queue, set queue attributes, etc21:41
flwangjust like what you can do on SQS21:42
Eva-iflwang: Oh. Maybe I shouldn't deleted my amazon account in august...21:44
Eva-i*shouldn't have deleted21:44
flwangEva-i: oh, why do you want to do that?21:44
flwangit won't charge you anything if you just don't use it21:44
flwangfor SQS, it starts to bill you when you exceed 1M requests, IIRC21:45
Eva-iflwang: my amazon free tier is expired, would I still able to test SQS for free?21:46
ryansbEva-i: fwiw, I use AWS for my backups, hosting 4 static sites, and DNS. (my free tier expired) it's only ~4 bucks a month21:47
ryansbso if you only ever play with SQS, your bill should be like...10 cents21:48
Eva-iryansb: okay21:48
ryansbit's $0.00000050 per SQS Request21:49
*** Haunted has joined #openstack-zaqar21:50
ryansbso 500 nanodollars21:50
HauntedHi21:50
mpanettaThat breaks the bank :P21:51
HauntedHi?21:51
Eva-ihello21:51
HauntedHow was Thanksgiving?21:51
HauntedHello21:53
HauntedWhy is nobody responding?21:54
ryansbhey Haunted, how's it going?21:54
HauntedGood21:54
HauntedHow about you?21:54
Eva-iHaunted: there are people in the chat from different countries, many of them don't have this holiday.21:55
Hauntedok21:55
HauntedIs this a meeting of some kind?21:56
flwangHaunted: yep, our normal meeting is rescheduled since the freenode down21:56
Hauntedok21:56
flwangHaunted: anything you would like to discuss?21:56
HauntedWhen and here is your normal meeting?21:57
ryansbYeah, but most of the time #openstack-zaqar is jus a hangout for zaqar users/contributors21:57
HauntedWhen and where is your normal meeting?21:57
ryansbhttp://eavesdrop.openstack.org/#Zaqar_Team_Meeting21:57
Hauntedok21:57
HauntedThanks21:57
ryansbit's in #openstack-meeting-3, at 2100 UTC or 1500 UTC alternating21:57
ryansbthis week would have been a 1500UTC week, but due to rain^Wfreenode DDoS we rescheduled21:58
Hauntedok21:58
flwangok, anything else for the UI topic?21:59
flwangotherwise, let's move to next one21:59
Hauntedok21:59
Hauntedwe can move on21:59
flwang4. more queue attributes21:59
flwangi haven't registered a blueprint for that, will do that today21:59
HauntedGood idea.21:59
flwangbasically, the idea is adding more reserved attributes for queue, just like SQS and other queue services didi22:00
Hauntedok22:00
flwangfor now, even though we support metadata for queue22:00
flwangbut it's not used much22:00
flwangfor now, we only support '_flavor'22:01
flwangwe should/could support more attributes for queue to get a flexible queue, see http://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_SetQueueAttributes.html22:02
Haunted#openstack-meeting-alt22:02
Hauntedsorry22:02
ryansbyeah, definitely do a blueprint22:03
ryansbI'm not sure what we need immediately22:03
*** csoukup_ has joined #openstack-zaqar22:04
flwangryansb: it's not a critical feature for sure :)22:05
Eva-iflwang: I don't have an opinion for this22:05
HauntedMe neither22:05
flwangryansb: another feature i would like to implement is delay queue or dead letter queue22:05
*** c_soukup has quit IRC22:06
flwangdepends on the resource :)22:08
flwangjasondotstar: any updates for puppet work?22:08
ryansbalright folks, I've got to head out, seeya tomorrow (or later today, depending on your tz's)22:09
flwangok, anything else you guys would like to talk?22:09
flwangryansb: see you, thanks22:10
HauntedIn the description it says Meetings every Monday @ 21:00 UTC/15:00 UTC22:10
Hauntedbut you said this isn't your normal meeting channel22:10
Hauntedor is this where meetings are normal conducted?22:11
Eva-iryansb: good bye22:11
Hauntedryansb is this your normal meeting channel?22:12
flwangHaunted: the normal meeting channel is #openstack-meeting-322:12
flwang#openstack-meeting-3, at 2100 UTC or 1500 UTC alternating22:12
Hauntedon the top of this chat it says Meetings every Monday @ 21:00 UTC/15:00 UTC22:12
Hauntedim a bit confused22:13
flwangthere was a freenode issue, so we meet at here again22:14
flwangdoes that make sense?22:14
Hauntedso this is where you meet temporarily?22:14
Hauntedfor a period of time?22:14
openstackgerritMerged openstack/python-zaqarclient: Add `pool` support for v2  https://review.openstack.org/24541222:15
flwangHaunted: hmm... this is the normal channel for Zaqar team22:16
flwangbut for weekly formal meeting, we use #openstack-meeting-322:16
*** csoukup_ has quit IRC22:16
Hauntedflwang but temporarily your formal meetings will be here?22:17
Eva-iHaunted: no, our formal meeting will not be here.22:18
Eva-i*meetings22:18
Hauntedis this a formal meeting right now?22:18
flwangHaunted: for random discussion, we always use this channel22:18
flwangHaunted: you can call it 'formal' or not22:19
Hauntedok22:19
flwangit doesn't really matter, TBH22:19
Hauntedwhere is this meeting normaly done?22:19
flwangHaunted: again, #openstack-meeting-322:19
flwang:)22:19
Hauntedok, but on the top of this page it says Meetings every Monday @ 21:00 UTC/15:00 UTC22:20
flwangEva-i: can you help explain? :)22:20
flwangi'm not a native english speacker :)22:20
Eva-iflwang: I think I'm not able22:20
flwangHaunted: could you let me know what r u looking for?22:21
Hauntedif the meetings were not usually done here, why does it say Meetings every Monday @ 21:00 UTC/15:00 UTC22:21
flwangare you going to join our weekly meeting in the future?22:21
HauntedI might22:22
Eva-iflwang: the only explanation I have that Haunted might be mocking us =)22:22
flwangHaunted: if so, just always join this channel22:22
HauntedIm not mocking nobody22:22
flwangHaunted: and you will be notified if there is anything changed22:23
flwangHaunted: let's back to discuss messaging instaed of meeting22:23
Hauntedok, so the meeting that is happening now is always on here?22:23
flwangHaunted: are you going to coding for zaqar or deploy?22:23
Hauntedyes22:23
Hauntedzaqar22:24
flwangforget the meeting time22:24
flwangwe're always here22:24
Hauntedare we having a meeting now?22:24
flwangHaunted: https://etherpad.openstack.org/p/mitaka-zaqar-assignment22:24
flwangthat's our focus for mitada release22:24
Eva-iflwang: I think meeting is ended, right?22:25
flwangEva-i: oh, yep22:25
flwangsorry22:25
Hauntedok22:25
flwangHaunted: let me know if you're interested in any part22:25
Hauntedok22:25
flwangso that we can work out a task for you22:25
Hauntedok22:26
flwangHaunted: glad to see you're interested in zaqar22:26
Hauntedia this OpenStack Queing notification Service22:26
*** csoukup_ has joined #openstack-zaqar22:27
flwangHaunted: why you ask?22:27
Hauntedbecause on the top of the channel thats what it sys.22:27
flwangHaunted: then yep22:27
Hauntedok22:28
HauntedActually, no I don't want the job.22:32
Hauntedflwang i don't want the job22:33
*** sriram has quit IRC22:38
*** Haunted has left #openstack-zaqar22:40
*** amitgandhinz has quit IRC22:44
*** dmowrer has quit IRC22:45
*** mpanetta has quit IRC22:46
*** ametts has quit IRC23:04
jasondotstarflwang: hey... just got your msg... nothing worthy to report just yet. I'm getting there.23:05
flwangjasondotstar: ah, ok, did you see the mail i sent to kgriffs ?23:08
*** tej has quit IRC23:08
jasondotstaryeah23:08
jasondotstarI saw it earlier today23:08
flwangjasondotstar: nice23:08
jasondotstarhopefully we'll get some info23:08
flwangkgriffs when you see this message, pls check your mailbox :)23:08
flwangjasondotstar: thanks23:10
jasondotstarsure, np23:10
kgriffsSorry for the delay; I just replied. Hopefully Balaji can assist.23:13
flwangkgriffs: awesome, thanks a lot23:14
kgriffssure thing. And BTW, I'm still working on those questions; I was on holiday all last week, but will see if I can put together some thoughts this week23:15
*** kui has joined #openstack-zaqar23:20
flwangkgriffs: thank you soooo much23:21
*** barra204 has quit IRC23:38
*** shakamunyi has joined #openstack-zaqar23:38
*** flwang1 has quit IRC23:51
*** Qiming has joined #openstack-zaqar23:57
*** Qiming has quit IRC23:59
*** Qiming has joined #openstack-zaqar23:59

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