| *** jasondotstar has quit IRC | 00:42 | |
| *** bradjones has quit IRC | 01:21 | |
| *** bradjones has joined #openstack-zaqar | 01:29 | |
| *** bradjones has quit IRC | 01:29 | |
| *** bradjones has joined #openstack-zaqar | 01:29 | |
| *** jasondotstar has joined #openstack-zaqar | 02:09 | |
| *** jasondotstar has joined #openstack-zaqar | 02:10 | |
| *** jasondotstar has quit IRC | 02:24 | |
| *** csoukup has joined #openstack-zaqar | 02:31 | |
| *** Yanyanhu has joined #openstack-zaqar | 02:45 | |
| *** c_soukup has joined #openstack-zaqar | 03:27 | |
| *** csoukup has quit IRC | 03:30 | |
| *** c_soukup has quit IRC | 03:59 | |
| *** achanda has joined #openstack-zaqar | 04:23 | |
| *** achanda has quit IRC | 04:32 | |
| *** achanda has joined #openstack-zaqar | 05:02 | |
| *** fifieldt has joined #openstack-zaqar | 05:10 | |
| *** achanda has quit IRC | 05:31 | |
| *** exploreshaifali has joined #openstack-zaqar | 06:19 | |
| *** boris-42 has quit IRC | 06:42 | |
| exploreshaifali | flaper87, Mooooooooooooooorning :D | 07:46 |
|---|---|---|
| exploreshaifali | I am not sure why we use flavors for zaqar, I only know about nova-flavors | 07:47 |
| exploreshaifali | okay, I will read it here https://wiki.openstack.org/wiki/Zaqar/specs/api/v1.1#Queue_Flavors | 07:48 |
| flaper87 | exploreshaifali: on the phone, bbib (sorry) | 07:51 |
| exploreshaifali | no issues :) | 07:52 |
| flaper87 | exploreshaifali: tl;dr: Flavors expose pools | 07:52 |
| *** jyuso1 has joined #openstack-zaqar | 07:53 | |
| *** dynarro has joined #openstack-zaqar | 08:02 | |
| exploreshaifali | ok | 08:05 |
| flaper87 | dynarro: exploreshaifali has a question for you about flavors | 08:12 |
| exploreshaifali | dynarro, Hi Girl! | 08:12 |
| dynarro | exploreshaifali: tell me everything? | 08:12 |
| dynarro | exploreshaifali: hellooo | 08:13 |
| exploreshaifali | dynarro, I want to know everything about flavors with Zaqar | 08:13 |
| exploreshaifali | we create flavors for diff queues? | 08:13 |
| dynarro | so, basically flavors have the purpose of exposing pools | 08:18 |
| dynarro | we don't create flavors for different queues, but they are shared | 08:19 |
| dynarro | by shared I mean, that we use one flavor for different queues | 08:21 |
| exploreshaifali | ok | 08:21 |
| exploreshaifali | so flavor will define hardware requirements for queues | 08:21 |
| exploreshaifali | let say we have 2 flavors - f1 and f2 | 08:22 |
| flaper87 | exploreshaifali: they are not like nova's flavors | 08:24 |
| flaper87 | The term is... overloaded | 08:24 |
| exploreshaifali | ok | 08:24 |
| flaper87 | A flavor defines the kind of storage | 08:24 |
| flaper87 | For instance, you'd have different pools with different capabilities | 08:24 |
| flaper87 | redis has different capabilities than mongodb | 08:24 |
| exploreshaifali | yes | 08:24 |
| flaper87 | You could have a "super-fast" flavor that sits on top of redis | 08:24 |
| flaper87 | and a "durable" flavor on top of mongodb | 08:25 |
| exploreshaifali | so at present as zaqar support only mongodb and redis, we can have only two flavors? | 08:26 |
| exploreshaifali | *two diff flavors | 08:26 |
| flaper87 | in theory, yes, two different *kind* of flavors | 08:27 |
| flaper87 | based on the capabilities of the storage drivers we support | 08:27 |
| exploreshaifali | okay | 08:30 |
| exploreshaifali | flaper87, btw just to confirm, by driver you mean python drivers that we used for connecting database with python programs | 08:33 |
| exploreshaifali | right? | 08:33 |
| exploreshaifali | like pymongo | 08:33 |
| vkmc | hellooooooooooooo | 08:33 |
| exploreshaifali | vkmc, helllllllllllllllllllooooooooooooooo :) | 08:34 |
| vkmc | exploreshaifali, driver is, technically, a piece of software that let's you interact with another piece of software | 08:35 |
| flaper87 | exploreshaifali: no, in this case I meant the redis/mongodb drivers | 08:35 |
| flaper87 | monthly reminder: https://speakerdeck.com/flaper87/iaas-beyond-infrastructure?slide=10 | 08:36 |
| exploreshaifali | yes, here we were talking that we can have diff flavors based on storage driver capabilites | 08:36 |
| exploreshaifali | ok | 08:37 |
| exploreshaifali | vkmc, diga said he will work on pools support, so I will take flavors support | 08:39 |
| vkmc | great | 08:39 |
| exploreshaifali | :) | 08:40 |
| flaper87 | exploreshaifali: you'll need to work dynarro is doing to complete the flavors part | 08:40 |
| vkmc | that is, complete dynarro's work in cli side | 08:42 |
| exploreshaifali | okay, that mean what dynarro did for zaqar client flavors same I am suppose to do for cli? | 08:44 |
| vkmc | exploreshaifali, you need to create the interface for the support dynarro added for flavors in the client | 08:44 |
| vkmc | client == library that makes easier to use zaqar | 08:44 |
| vkmc | cli = command line interface that uses the client to perform operations | 08:45 |
| vkmc | flaper87 == big italian gummybear | 08:45 |
| exploreshaifali | LOL | 08:45 |
| exploreshaifali | yes yes, I understand that part | 08:45 |
| vkmc | great | 08:46 |
| vkmc | just making sure, it used to confuse me a lot | 08:46 |
| exploreshaifali | I understand well how in 3 diff ways one can use OpenStack | 08:46 |
| exploreshaifali | :P | 08:46 |
| exploreshaifali | but I want to know why we have python apis? vkmc | 08:47 |
| exploreshaifali | because they allow user to interegrate it with their python code? | 08:47 |
| vkmc | yeah | 08:51 |
| vkmc | it makes easier for people wanting to use Zaqar (or any other OpenStack component) | 08:52 |
| vkmc | s/it makes easier/it makes it easier | 08:52 |
| vkmc | they simply need the client library | 08:52 |
| vkmc | and instead of, for example, curl'ing to the messages endpoint to post a message | 08:53 |
| vkmc | they issue a "client.post_message('lalala')" | 08:53 |
| vkmc | from their python application | 08:53 |
| vkmc | and the client is needed for a similar reason | 08:54 |
| exploreshaifali | our direct users(the one who will use apis) are not the one who will deploy their web apps on clouds that are based on openstack? | 08:54 |
| exploreshaifali | they are the one who will build one more layer on the top of openstack to provide clouds? | 08:54 |
| exploreshaifali | and that is why they need apis? | 08:55 |
| vkmc | don't confuse api's with python client | 08:55 |
| exploreshaifali | oh... ok. I did that :P | 08:56 |
| vkmc | if we don't provide a client, the users will need to create it in order to use zaqar in their applications | 08:56 |
| vkmc | the api specifies how software components should interact | 08:56 |
| vkmc | basically what we have here https://wiki.openstack.org/wiki/Zaqar/specs/api/v1.1 | 08:57 |
| vkmc | and the client is just a library that wraps how you interact with the api | 08:58 |
| vkmc | the client provides an easy way to send messages to the api :) | 08:58 |
| vkmc | does that make sense? | 08:58 |
| exploreshaifali | yes yes | 08:58 |
| vkmc | kewl | 08:58 |
| exploreshaifali | please can you give one example what applications client have/develop for which they need pythonclients | 08:59 |
| exploreshaifali | s/ applications client/ applications user | 09:00 |
| vkmc | so, imagine an mobile advertising application | 09:01 |
| exploreshaifali | ok | 09:01 |
| vkmc | they need to retrieve information from different mobiles | 09:01 |
| vkmc | a good way to multiplex the tasks is using a persistent messaging system, like Zaqar | 09:02 |
| vkmc | so imagine how their software would look like | 09:02 |
| vkmc | you would have two parts: a server software (it will handle the information) and a guest software (in the mobile, will get the data from the user) | 09:04 |
| vkmc | the guest can create queue and post data from the user to the queue | 09:05 |
| vkmc | and then the server will recover that data and "do something" with that data in the server side | 09:05 |
| vkmc | imagine that the software is written in python | 09:05 |
| vkmc | its easier for this imaginary customer to have a client and issue commands like "zaqar.create_queue()" | 09:06 |
| vkmc | inside their own software | 09:06 |
| vkmc | that create a wsgi request, put the data into it, make sure it is valid, and send it | 09:06 |
| vkmc | s/that/than | 09:06 |
| vkmc | you will need to have a zaqar server deployment, but it will be easier for you to use it from your python application | 09:08 |
| vkmc | exploreshaifali, you can see it now? | 09:08 |
| exploreshaifali | yes!! | 09:09 |
| exploreshaifali | vkmc, Thank You! | 09:10 |
| vkmc | :) | 09:10 |
| vkmc | cool | 09:10 |
| vkmc | np | 09:10 |
| exploreshaifali | it is clear to me, and similar things for rest other components of openstack also | 09:10 |
| vkmc | yeah | 09:11 |
| exploreshaifali | like i want to store something on swift databse(which runs on my server), so I can use zaqar to send data from mobile to swift server | 09:11 |
| vkmc | yeah | 09:11 |
| exploreshaifali | there on swift I will need to code something that will accept these messages? | 09:12 |
| exploreshaifali | of couse yes | 09:12 |
| exploreshaifali | which will be zaqar claim and processing part | 09:12 |
| vkmc | you could have a software that retrieves data from a zaqar queue and puts that data in your swift database | 09:12 |
| vkmc | using the clients | 09:12 |
| vkmc | buuuuuut, we will have a swift driver in the near future | 09:13 |
| vkmc | so that will be easier | 09:13 |
| vkmc | (that use case) | 09:13 |
| exploreshaifali | okay! :D | 09:13 |
| exploreshaifali | vkmc, that means for all most all operations we do(as customer) we will need some messaging agent to interact with openstack? | 09:14 |
| vkmc | not really | 09:15 |
| vkmc | it depends on the use case, actually | 09:15 |
| exploreshaifali | clients applications, will need some messaging agents | 09:15 |
| *** dguerri` is now known as dguerri | 09:31 | |
| *** jyuso1 has quit IRC | 09:40 | |
| *** dynarro has quit IRC | 09:47 | |
| *** Yanyanhu has quit IRC | 09:52 | |
| *** Yanyanhu has joined #openstack-zaqar | 09:53 | |
| *** Yanyanhu has quit IRC | 09:53 | |
| *** malini has joined #openstack-zaqar | 10:07 | |
| *** jasondotstar has joined #openstack-zaqar | 10:41 | |
| *** jasondotstar has quit IRC | 11:06 | |
| *** malini has quit IRC | 11:33 | |
| *** malini has joined #openstack-zaqar | 11:45 | |
| *** dynarro has joined #openstack-zaqar | 11:45 | |
| *** malini has quit IRC | 11:46 | |
| *** malini has joined #openstack-zaqar | 11:46 | |
| *** malini has quit IRC | 11:58 | |
| *** malini has joined #openstack-zaqar | 12:14 | |
| *** exploreshaifali has quit IRC | 12:27 | |
| *** malini has quit IRC | 12:32 | |
| *** exploreshaifali has joined #openstack-zaqar | 12:46 | |
| ryansb | morning folks | 12:47 |
| vkmc | morning ryansb! | 12:47 |
| *** tmu has quit IRC | 12:53 | |
| *** malini has joined #openstack-zaqar | 12:57 | |
| *** malini has quit IRC | 12:57 | |
| *** sriram has joined #openstack-zaqar | 13:03 | |
| *** sriram has quit IRC | 13:03 | |
| *** sriram has joined #openstack-zaqar | 13:03 | |
| *** mpanetta has joined #openstack-zaqar | 13:48 | |
| *** malini has joined #openstack-zaqar | 13:51 | |
| *** amitgandhinz has joined #openstack-zaqar | 13:53 | |
| *** csoukup has joined #openstack-zaqar | 14:03 | |
| *** kgriffs|afk is now known as kgriffs | 14:07 | |
| *** csoukup has quit IRC | 14:15 | |
| *** kgriffs is now known as kgriffs|afk | 14:16 | |
| flaper87 | ryansb: yo yo yo! | 14:19 |
| flaper87 | vkmc: mind taking a look at dynarro's patch on zaqar-server ? | 14:19 |
| *** kgriffs|afk is now known as kgriffs | 14:20 | |
| vkmc | sure | 14:20 |
| *** exploreshaifali has quit IRC | 14:24 | |
| dynarro | vkmc: I did'n quite understand the last comment you made on the commit message of this patch https://review.openstack.org/#/c/190706/1 | 14:25 |
| vkmc | dynarro, oh, that I never explained... my bad | 14:26 |
| dynarro | vkmc: like should I replace that part with what you said? | 14:26 |
| vkmc | in order to gerrit to update your launchpad blueprint you need to put the keyword "blueprint" plus the name of the blueprint you are working on and the patch belongs to | 14:26 |
| vkmc | in this case "api-v1.1" | 14:27 |
| dynarro | oh ok, so I should just add blueprint api-v1.1 and then the name of the blueprint? | 14:29 |
| vkmc | api-v1.1 is the name of the blueprint | 14:30 |
| openstackgerrit | Flavio Percoco proposed openstack/zaqar: Add support for pymongo 3.0.2 https://review.openstack.org/176855 | 14:30 |
| dynarro | k k | 14:31 |
| openstackgerrit | Doraly Navarro proposed openstack/python-zaqarclient: Added support to pools and flavors https://review.openstack.org/190706 | 14:33 |
| dynarro | vkmc: it works!!! ^ | 14:34 |
| dynarro | I'm about to cry =D | 14:34 |
| vkmc | yeaaah :D | 14:35 |
| vkmc | awesome! | 14:35 |
| angvp | dynarro: :') | 14:35 |
| * flaper87 slaps dynarro to make sure he cries | 14:36 | |
| flaper87 | :P | 14:36 |
| dynarro | angvp: I felt like a tear when I saw all that green OKs! | 14:37 |
| dynarro | jk | 14:37 |
| * flaper87 is really really really un-caffeinated today | 14:37 | |
| dynarro | flaper87: hey! | 14:37 |
| flaper87 | dynarro: sup? | 14:38 |
| angvp | dynarro: it feels awesome right?! i don't have this sensation yet in this project, hope soon :P | 14:38 |
| dynarro | angvp: it feels great! I'm sure you will :) | 14:39 |
| *** exploreshaifali has joined #openstack-zaqar | 14:48 | |
| *** openstackgerrit has quit IRC | 15:05 | |
| *** openstackgerrit has joined #openstack-zaqar | 15:05 | |
| openstackgerrit | Flavio Percoco proposed openstack/zaqar: Add support for pymongo 3.0.2 https://review.openstack.org/176855 | 15:12 |
| *** diga has quit IRC | 15:32 | |
| *** csoukup has joined #openstack-zaqar | 15:33 | |
| *** exploreshaifali has quit IRC | 15:53 | |
| *** exploreshaifali has joined #openstack-zaqar | 16:03 | |
| *** achanda has joined #openstack-zaqar | 16:12 | |
| *** dguerri is now known as dguerri` | 16:15 | |
| flaper87 | vkmc: reviewed ws. Sorry for the delay | 16:16 |
| vkmc | its ok | 16:16 |
| vkmc | thanks | 16:16 |
| flaper87 | kragniz: any chance you can address my comment on the policy spec? | 16:18 |
| flaper87 | I'll +2 after that :D | 16:18 |
| *** achanda_ has joined #openstack-zaqar | 16:21 | |
| flaper87 | dynarro: you need to add this to your client's patch | 16:24 |
| flaper87 | Depends-on: I36445838f532e9f282a4f839a0f583257c1f13d9 | 16:24 |
| flaper87 | in the commit message | 16:24 |
| dynarro | flaper87: oooh | 16:24 |
| *** achanda has quit IRC | 16:24 | |
| flaper87 | (that alphanumeric string is the change-id of your change in zaqar) | 16:24 |
| flaper87 | The change vkmc hasn't reviewed yet | 16:24 |
| flaper87 | you know | 16:24 |
| dynarro | lOL | 16:25 |
| flaper87 | the one she said she was going to review | 16:25 |
| flaper87 | yeah, THAT ONE! | 16:25 |
| flaper87 | :P | 16:25 |
| *** dguerri` is now known as dguerri | 16:25 | |
| * vkmc hides | 16:25 | |
| openstackgerrit | Doraly Navarro proposed openstack/python-zaqarclient: Added support to pools and flavors https://review.openstack.org/190706 | 16:27 |
| *** achanda_ has quit IRC | 16:31 | |
| *** dynarro has quit IRC | 16:31 | |
| *** dguerri is now known as dguerri` | 16:32 | |
| *** openstackgerrit has quit IRC | 16:33 | |
| *** openstackgerrit has joined #openstack-zaqar | 16:34 | |
| *** fifieldt_ has joined #openstack-zaqar | 16:43 | |
| *** fifieldt has quit IRC | 16:45 | |
| *** malini has quit IRC | 16:45 | |
| *** exploreshaifali has quit IRC | 16:52 | |
| *** achanda has joined #openstack-zaqar | 16:57 | |
| openstackgerrit | Merged openstack/zaqar: Added 'pool name' and 'flavor name' to response https://review.openstack.org/190550 | 17:00 |
| *** achanda has quit IRC | 17:02 | |
| *** exploreshaifali has joined #openstack-zaqar | 17:03 | |
| *** achanda has joined #openstack-zaqar | 17:05 | |
| *** achanda has quit IRC | 17:11 | |
| *** achanda has joined #openstack-zaqar | 17:18 | |
| openstackgerrit | Merged openstack/zaqar: Update version for Liberty https://review.openstack.org/192416 | 17:19 |
| *** achanda_ has joined #openstack-zaqar | 17:22 | |
| *** achanda has quit IRC | 17:25 | |
| *** achanda_ has quit IRC | 17:33 | |
| *** achanda has joined #openstack-zaqar | 17:54 | |
| *** kgriffs is now known as kgriffs|afk | 18:09 | |
| *** achanda has quit IRC | 18:17 | |
| *** fifieldt_ has quit IRC | 19:12 | |
| *** openstackgerrit has quit IRC | 19:16 | |
| *** openstackgerrit has joined #openstack-zaqar | 19:16 | |
| *** fifieldt_ has joined #openstack-zaqar | 19:29 | |
| *** kgriffs|afk is now known as kgriffs | 19:35 | |
| *** exploreshaifali has quit IRC | 19:57 | |
| *** kgriffs is now known as kgriffs|afk | 20:03 | |
| *** kgriffs|afk is now known as kgriffs | 20:03 | |
| *** achanda has joined #openstack-zaqar | 20:19 | |
| *** achanda_ has joined #openstack-zaqar | 20:23 | |
| *** achanda has quit IRC | 20:26 | |
| *** achanda_ has quit IRC | 20:38 | |
| *** dguerri` is now known as dguerri | 20:55 | |
| *** csoukup has quit IRC | 21:13 | |
| *** sriram has quit IRC | 21:19 | |
| *** mpanetta has quit IRC | 21:19 | |
| *** openstackgerrit has quit IRC | 21:24 | |
| *** openstackgerrit has joined #openstack-zaqar | 21:24 | |
| *** achanda has joined #openstack-zaqar | 21:36 | |
| *** achanda has quit IRC | 21:42 | |
| *** amitgandhinz has quit IRC | 22:01 | |
| *** dguerri is now known as dguerri` | 22:34 | |
| *** jasondotstar has joined #openstack-zaqar | 22:45 | |
| *** ametts has quit IRC | 23:14 | |
| *** kgriffs is now known as kgriffs|afk | 23:38 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!