21:00:09 <flwang> #startmeeting zaqar
21:00:11 <openstack> Meeting started Mon Nov 23 21:00:09 2015 UTC and is due to finish in 60 minutes.  The chair is flwang. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:12 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:15 <openstack> The meeting name has been set to 'zaqar'
21:00:23 <jasondotstar> o/
21:00:37 <flwang> jasondotstar: hey
21:00:44 <flwang> #topic roll call
21:01:14 <flwang> jasondotstar: if there is only you and me, then let's make it as a party instead of meeting :)
21:01:23 * jasondotstar grabs chips and dip
21:02:12 <flwang> jasondotstar: don't want to waste your time, before the others joining, would you mind updating the puppet status?
21:02:19 <flwang> i'm really keen to know it :)
21:02:26 <jasondotstar> sure.
21:02:44 <jasondotstar> so I've got the debian stuff working now
21:02:54 <flwang> jasondotstar: awesome awesome
21:03:06 <jasondotstar> meaning w/ the puppet module you can install it with RPM or DEB based
21:03:32 <jasondotstar> i didn't get a chance to talk to anyone about which conf options to expose
21:03:51 <jasondotstar> so perhaps someone can advise me there
21:03:55 <flwang> jasondotstar: i mentioned that with kgriffs
21:04:05 <jasondotstar> and then,  we need to write the tests
21:04:16 <flwang> who is the funder of zaqar/marconi from Rackspace
21:04:22 <flwang> you know rackspace is running zaqar
21:04:32 <jasondotstar> i didn't know that
21:04:37 <flwang> i asked him to share the conf what rackspace is using
21:04:53 <jasondotstar> right
21:04:53 <flwang> but i haven't got the response, i will ping him again
21:04:58 <jasondotstar> that'd be helpful
21:05:03 <jasondotstar> we can maybe default to those
21:05:09 <flwang> but before that, i can help you
21:05:16 <jasondotstar> *nod*
21:05:17 <jasondotstar> ok
21:05:46 <flwang> jasondotstar: so what do you need for now? a basic reference conf?
21:05:53 <jasondotstar> yes plz
21:05:55 <jasondotstar> that would work
21:06:10 <flwang> jasondotstar: what's the database you're using?
21:06:12 <flwang> mongo?
21:06:18 <jasondotstar> yes mongo.
21:06:56 <flwang> cool, it would be nice if you can give me your email
21:07:06 <jasondotstar> sure
21:07:07 <flwang> so that i can send it to you after it's ready
21:07:33 <jasondotstar> sent
21:07:43 <flwang> jasondotstar: got, cool
21:08:04 <flwang> jasondotstar: did you upload your patch for review?
21:08:31 <flwang> jasondotstar: if so, i can ask my colleague(ops guy) to give it a review/try
21:20:58 <flwang> jasondotstar: still around?
21:28:07 <vkmc> flwang, o/
21:28:31 <flwang> vkmc: i miss you
21:28:52 <flwang> we lost jasondotstar now
21:29:02 <flwang> vkmc: i just confirmed with jasondotstar the puppet status
21:29:13 <flwang> vkmc: basically, we're in good shape
21:29:24 <vkmc> flwang, that's great to hear!
21:29:31 <flwang> vkmc:  we need to provide a ref config for him
21:29:39 <flwang> as the default config file
21:30:38 <vkmc> flwang, we need an operator POV for this probably
21:30:46 <flwang> vkmc: and we definately made some great progress for zaqar client and the docs work, see https://etherpad.openstack.org/p/mitaka-zaqar-assignment
21:31:01 <vkmc> flwang, yeah :) saw the patchsets going up
21:31:09 <flwang> vkmc: i have mentioned that with kgriffs to ask a conf which rackspace is using
21:31:22 <flwang> but i haven't got response, i will ping him again
21:31:37 <flwang> vkmc: so pls review them :)
21:31:54 <vkmc> flwang, sure thing
21:32:12 <vkmc> flwang, I'll try to catch kgriffs myself, he is closer to my tz
21:32:21 <flwang> vkmc: awesome, thanks
21:32:39 <vkmc> flwang, I also had several discussions about docs with Eva-i
21:32:58 <flwang> vkmc: cool, would you like to share them now?
21:33:07 <vkmc> flwang, I'm aware she already told you that she will be an intern in Zaqar for the upcoming Outreachy round
21:33:21 <vkmc> flwang, the internship starts in December, but she is willing to start already... that's very awesome from her :D
21:34:03 <vkmc> flwang, sure, we are laying out things here https://etherpad.openstack.org/p/zaqar-mitaka-docs
21:35:18 <flwang> vkmc: yep, Eva-i is really helpful, she does a great job
21:35:44 <flwang> i'm really happy to see she could be a formal intern for the outreachy project
21:35:56 <vkmc> me too :D
21:35:58 <flwang> as for the docs, anything you want to highlight?
21:36:09 <vkmc> yeah... we will have an important revamp on docs
21:36:24 <vkmc> we are going to remove most of the content we have in the wiki, since it's redundant to some of the content under developer/zaqar
21:36:38 <vkmc> we are going to move the API reference to developer/zaqar
21:37:06 <vkmc> plus we are going to fix the bugs Eva-i pointed out in the etherpad (and if we find more in the way, we are going to add them there)
21:37:33 <vkmc> once we have all the developers docs in place, we are going to start working on some user docs, with configuration samples and use cases
21:37:43 <vkmc> that with the OpenStack Docs team
21:37:54 <flwang> vkmc: sounds a plan
21:38:06 <vkmc> perhaps something we need to define if that change from wiki to developers guide is ok for you
21:38:13 <flwang> vkmc: as you know, i'm working on the spec for config ref and user guides
21:38:25 <vkmc> super
21:38:51 <vkmc> Eva-i checked how other projects are handling docs and perhaps this is the best way
21:39:08 <flwang> vkmc: agree
21:39:25 <vkmc> something that was a bit confusing is that the docs under developer/zaqar are shipped with the code
21:39:33 <vkmc> and those docs contains information on "how to contribute"
21:39:42 <vkmc> but that is an standard for every other OpenStack project
21:39:52 <flwang> vkmc: agree
21:40:12 <vkmc> so yeah, that's pretty much it
21:40:20 <vkmc> I think we are going to start with that soon :)
21:40:38 <vkmc> and then we can help you with the spec for config red and user guides
21:40:50 <flwang> recently, i realized that we focused the zaqar server side too much in previous cycles
21:41:29 <flwang> and we're losing some potential users because of the bad docs, weak client support, etc
21:41:52 <flwang> vkmc: sounds good, really appreciate for your support
21:42:06 <vkmc> flwang, totally agree
21:42:10 <vkmc> this cycle should be to polish that
21:42:29 <vkmc> thanks for leading the effort :)
21:43:43 <flwang> vkmc: so pls pls review the client patches heavily so that we can ask sahara team to start integrate zaqar
21:43:57 <vkmc> flwang, I'm doing that now
21:44:11 <flwang> vkmc: i know you're busy but i have to push you guys, sorry :)
21:44:17 <vkmc> flwang, that's totally fine
21:44:20 <vkmc> we work under pressure
21:45:41 <flwang> vkmc: i will update the assignment etherpad to add the docs work which Eva-i and you're working
21:46:50 <vkmc> flwang, do you want me to do that?
21:47:08 <flwang> vkmc: it would be awesome
21:47:12 <flwang> vkmc: yes, pls
21:47:21 <vkmc> flwang, cool :) will add that after I'm done with the reviews
21:47:49 <flwang> vkmc: btw, for the client work, we obviously need some unti test for cli
21:47:58 <flwang> but we don't have any test for that
21:48:04 <vkmc> oh.. hmm
21:48:25 <flwang> so i will user a separate patch to add a test framework for cli
21:48:46 <vkmc> good point
21:48:46 <vkmc> yes
21:49:12 <flwang> if you're not really comfortable with that, i can do that firstly and then as the other patches to depend on it
21:49:13 <flwang> but
21:49:31 <flwang> it will slow the progress
21:49:38 <flwang> i have to balance :(
21:49:50 <vkmc> nah, we don't have enough resources
21:49:54 <vkmc> we need to move fast
21:50:32 <flwang> vkmc: yep
21:50:50 <flwang> besides, i'm still a fan of queue :D
21:51:00 <flwang> i know flaper87 may beat me, hah
21:51:22 <vkmc> haha no worries, he is not around
21:51:48 <flwang> so i'm working on the comparison between SQS, and other china public cloud's queuing service to figure out the gap
21:52:26 <vkmc> that sounds good
21:52:35 <flwang> basically, the first thing i may propose is allow user to edit the queue's properties
21:52:45 <vkmc> like... metadata?
21:53:00 <flwang> yep, i know, we can do that, but my point is
21:53:14 <flwang> having some reserved properties
21:53:27 <flwang> like the TTL, which we're putting them in conf file
21:53:44 <flwang> not flexible for each queue
21:54:05 <vkmc> not flexible for each message you mean
21:54:46 <flwang> maybe that's not a good example, so pls see this http://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_SetQueueAttributes.html
21:55:11 <vkmc> let see
21:55:11 <flwang> for now, IIRC, we can set the queue's metadata
21:55:13 <flwang> but
21:55:25 <flwang> we're not really using them
21:55:53 <flwang> user can put anything in the queue's matadata, so what?
21:56:04 <flwang> zaqar don't know what they are
21:56:12 <vkmc> that's true
21:56:28 <vkmc> our metadata is just info that users think are important, but we don't do anything with it
21:57:18 <flwang> vkmc: we could/should have some reserved metadata starts with _
21:57:31 <vkmc> flwang, sounds good
21:57:35 <vkmc> something I'm interested about
21:57:43 <flwang> and zaqar can use them to get a more flexiable queue
21:57:48 <vkmc> is in the visibility attribute SQS has
21:58:23 <flwang> vkmc: we can take 2-3 attributes as the first step
21:58:28 <vkmc> sounds good
21:58:53 <vkmc> feature for mitaka? :) v2
21:58:58 <vkmc> mitaka-3
21:59:03 <flwang> v2
21:59:07 <flwang> m-2
21:59:17 <flwang> so that we can have some time to revoke
21:59:26 <flwang> i'm joking :D
22:00:04 <flwang> let's talk in zaqar channel :)
22:00:14 <flwang> thank you, everyone
22:00:19 <flwang> #endmeeting