| *** flwang has joined #openstack-zaqar | 00:06 | |
| *** flwang has quit IRC | 00:23 | |
| *** akanksha_ has quit IRC | 00:28 | |
| *** akanksha_ has joined #openstack-zaqar | 00:30 | |
| *** flwang has joined #openstack-zaqar | 00:31 | |
| *** flwang1 has joined #openstack-zaqar | 00:44 | |
| *** flwang has quit IRC | 00:47 | |
| *** Qiming has joined #openstack-zaqar | 01:08 | |
| *** stanchan has quit IRC | 01:11 | |
| *** flwang has joined #openstack-zaqar | 01:13 | |
| *** flwang1 has quit IRC | 01:15 | |
| *** mdnadeem_ has joined #openstack-zaqar | 01:27 | |
| *** flwang has quit IRC | 01:33 | |
| *** csoukup has joined #openstack-zaqar | 01:46 | |
| *** david-ly_ has joined #openstack-zaqar | 02:31 | |
| *** david-lyle has quit IRC | 02:33 | |
| *** stanchan has joined #openstack-zaqar | 02:57 | |
| *** achanda has joined #openstack-zaqar | 03:27 | |
| *** david-lyle has joined #openstack-zaqar | 03:37 | |
| *** david-ly_ has quit IRC | 03:40 | |
| *** mdnadeem_ has quit IRC | 04:15 | |
| *** mdnadeem_ has joined #openstack-zaqar | 04:33 | |
| *** mdnadeem_ has quit IRC | 04:39 | |
| *** mdnadeem_ has joined #openstack-zaqar | 05:27 | |
| *** Qiming has quit IRC | 06:11 | |
| *** Qiming has joined #openstack-zaqar | 06:14 | |
| *** stanchan has quit IRC | 06:28 | |
| *** khushbu_ has joined #openstack-zaqar | 06:48 | |
| *** khushbu_ has quit IRC | 06:51 | |
| *** khushbu_ has joined #openstack-zaqar | 06:58 | |
| *** khushbu_ has quit IRC | 06:59 | |
| *** flaper87 has quit IRC | 07:17 | |
| *** flaper87 has joined #openstack-zaqar | 07:17 | |
| *** akanksha_ has quit IRC | 07:28 | |
| *** achanda has quit IRC | 07:29 | |
| *** itisha has quit IRC | 07:31 | |
| *** exploreshaifali_ has joined #openstack-zaqar | 07:37 | |
| *** venkat_ has joined #openstack-zaqar | 08:47 | |
| venkat_ | Hi, I configured "redis" as zaqar backend in local.conf as a part of devstack installation | 08:49 |
|---|---|---|
| venkat_ | once devstack installation completed, I am seeing redis only as backend why sqlalchemy is not configured ? | 08:49 |
| venkat_ | last time, I got information from ryansb & therve saying redis is used as message_store and sqlalchemy for mgmt_store | 08:51 |
| venkat_ | but I didn't saw this in zaqar.conf after devstack installation completed | 08:51 |
| venkat_ | seeing only redis configuration - [drivers] storage = redis [drivers:storage:redis] uri = redis://localhost:6379 | 08:52 |
| venkat_ | I am seeing plugin.sh has redis & sqlalchemy configuration parts if redis is choosen as zaqar backend | 08:55 |
| venkat_ | https://github.com/openstack/zaqar/blob/master/devstack/plugin.sh | 08:55 |
| venkat_ | I configured & installed kilo devstack and observed only redis configuration in zaqar.conf and missing sqlalchemy conf part.. | 08:55 |
| venkat_ | any clues here ? pls correct me with comments.. | 08:56 |
| *** diga has joined #openstack-zaqar | 09:15 | |
| *** venkat_ has quit IRC | 09:40 | |
| *** Qiming has quit IRC | 10:08 | |
| *** venkat_ has joined #openstack-zaqar | 10:21 | |
| *** diga has quit IRC | 10:42 | |
| *** venkat__ has joined #openstack-zaqar | 10:43 | |
| *** venkat_ has quit IRC | 10:44 | |
| *** venkat__ has quit IRC | 10:45 | |
| *** Qiming has joined #openstack-zaqar | 11:03 | |
| *** flwang has joined #openstack-zaqar | 11:11 | |
| *** Qiming has quit IRC | 11:32 | |
| *** Qiming has joined #openstack-zaqar | 11:32 | |
| *** Qiming has quit IRC | 11:37 | |
| *** shaifali__ has joined #openstack-zaqar | 11:41 | |
| *** khushbu_ has joined #openstack-zaqar | 11:48 | |
| *** venkat_ has joined #openstack-zaqar | 11:50 | |
| venkat_ | Hi | 11:51 |
| venkat_ | how I can configure sqlalchemy in zaqar as mgmt_store | 11:52 |
| venkat_ | configured redis as message_store uri = redis://localhost:6379 | 11:53 |
| venkat_ | any clues here ? | 11:53 |
| Eva-i | vkmc: ping | 12:04 |
| *** flwang has quit IRC | 12:09 | |
| *** khushbu_ has quit IRC | 12:13 | |
| therve | venkat_, in drivers you set management_store to sqlalchemy | 12:14 |
| therve | And then you fill the drivers:management_store:sqlalchemy section | 12:15 |
| *** shaifali__ has quit IRC | 12:16 | |
| venkat_ | therve: yes.. what is the url looks like ? for redis, I configured redis://localhost:6379 | 12:16 |
| *** khushbu_ has joined #openstack-zaqar | 12:17 | |
| *** shaifali__ has joined #openstack-zaqar | 12:17 | |
| therve | venkat_, Something like mysql://localhost/zaqar | 12:18 |
| therve | Probably with user:password somewhere | 12:19 |
| *** shaifali__ is now known as exploreshaifail | 12:20 | |
| exploreshaifail | as of I know, sqlalchemy is no more supported by zaqar | 12:20 |
| therve | exploreshaifail, It still is for the management part | 12:21 |
| exploreshaifail | oh, okay. Thanks therve :) | 12:23 |
| venkat_ | exploreshaifail, is it true ? in that case only mongodb & redis are supported as backend in zaqar ? | 12:23 |
| exploreshaifail | venkat_, as therve said, sqlalchemy is still there for management part :) | 12:23 |
| *** sriram has joined #openstack-zaqar | 12:24 | |
| *** sriram has quit IRC | 12:24 | |
| *** khushbu_ has quit IRC | 12:24 | |
| venkat_ | I configured redis in [drivers] storage = redis [drivers:storage:redis] uri = redis://localhost:6379 and it worked | 12:25 |
| *** khushbu_ has joined #openstack-zaqar | 12:25 | |
| venkat_ | here, redis is used for both message & mgmt store ? | 12:25 |
| therve | No just message | 12:25 |
| therve | "storage" == "message" | 12:25 |
| *** exploreshaifali_ has quit IRC | 12:25 | |
| venkat_ | therve, I configured redis during devstack kilo installation and didn't found anything related to sqlalchemy in zaqar.conf.. | 12:26 |
| venkat_ | therve, how mgmt part is handled by zaqar ? | 12:26 |
| therve | venkat_, How did you configure it? | 12:26 |
| *** flwang has joined #openstack-zaqar | 12:27 | |
| venkat_ | therve, configured redis in local.conf as ZAQAR_BACKEND=redis | 12:27 |
| therve | Ah using devstack you mean | 12:27 |
| therve | Well I guess it doesn't work this way | 12:28 |
| venkat_ | I ran couple of APIs and everything worked | 12:28 |
| venkat_ | seen only this configuration w.r.to backend in zaqar.conf - [drivers] storage = redis [drivers:storage:redis] uri = redis://localhost:6379 | 12:29 |
| venkat_ | in this case, how mgmt part is handled by zaqar ? | 12:33 |
| *** dynarro has joined #openstack-zaqar | 12:38 | |
| therve | It's possible it's only related to pooling? | 12:42 |
| therve | I don't know | 12:42 |
| venkat_ | therve, oh ok | 12:44 |
| venkat_ | flaper87, any comments on my question w.r.to sqlalchemy ? | 12:45 |
| *** venkat_ has quit IRC | 12:52 | |
| *** exploreshaifail has quit IRC | 12:53 | |
| *** khushbu_ has quit IRC | 12:57 | |
| *** amitgandhinz has joined #openstack-zaqar | 13:04 | |
| *** venkat_ has joined #openstack-zaqar | 13:05 | |
| flwang | venkat_: can you repeat your question about sqlalchemy? | 13:06 |
| flwang | vkmc: ping | 13:06 |
| venkat_ | flwang, I configured redis as backend as a part of devstack installation and it configured redis as message & mgmt store in zaqar.conf as [drivers] storage = redis [drivers:storage:redis] uri = redis://localhost:6379 | 13:09 |
| ryansb | IIRC you can't use redis as a management store | 13:09 |
| ryansb | pretty sure you need to use either the sqla management store or the mongo one | 13:09 |
| flwang | venkat_: ryansb is right. zaqar doesn't support use redis as mgmt driver | 13:10 |
| venkat_ | flwang, I didn't found anything relate to sqlalchemy in zaqar.conf | 13:10 |
| flwang | venkat_: based on my experience, sqlalchemy + redis works fine | 13:10 |
| flwang | venkat_: are you looking for the conf for sqlalchemy? | 13:11 |
| venkat_ | flwang, ok. but when I configured redis as backend in local.conf as ZAQAR_BACKEND=redis.. I am seeing only redis stuff in zaqar.conf and didn't found sqlalchemy stuff | 13:11 |
| flwang | venkat_: i think it's a limitation of the devstack script | 13:12 |
| venkat_ | flwang, I tried API calls and it worked! my doubt is how mgmt part is handled by zaqar without sqlalchemy configuration ? | 13:12 |
| flwang | venkat_: pls define 'worked' :) | 13:13 |
| flwang | did you mean redis+redis work for you? | 13:13 |
| venkat_ | flwang, I tried creating queue, adding message, deleting queue, listing queues | 13:13 |
| flwang | venkat_: it's possible | 13:14 |
| flwang | venkat_: i believe you will run into errors if you try actions for pool and flavor | 13:14 |
| flwang | like create a pool | 13:15 |
| venkat_ | oh ok.. I didn't tried them | 13:15 |
| venkat_ | flwant, can you provide me how I can configure sqlalchemy as mgmt store in zaqar.conf ? | 13:15 |
| flwang | vkmc: ryansb: flaper87: therve: pls help review the release note of L https://wiki.openstack.org/wiki/ReleaseNotes/Liberty#OpenStack_Messaging_Service_.28Zaqar.29 | 13:16 |
| flwang | venkat_: sure, wait a min | 13:16 |
| venkat_ | flwang, sure | 13:16 |
| flwang | venkat_: http://paste.openstack.org/show/476021/ | 13:20 |
| venkat_ | flwang, we need to create zaqar.db in sql db ? | 13:21 |
| flwang | venkat_: i'm using sqlite | 13:21 |
| *** Qiming has joined #openstack-zaqar | 13:21 | |
| venkat_ | flwang, ok.. one more doubt - sqlalchemy is configured under [pooling:catalog]. what is its usage ? can u please provide ur comments ? | 13:23 |
| flwang | IIRC, under [pooling:catalog], there is only enable_virtual_pool | 13:25 |
| flwang | venkat_: what did you mean 'sqlalchemy is configured under [pooling:catalog]'? | 13:26 |
| venkat_ | flwang, sample config generated by oslo has this - [pooling:catalog] # # From zaqar.storage.pooling # # Catalog storage driver. (string value) #storage = sqlalchemy | 13:26 |
| venkat_ | in zaqar.conf | 13:27 |
| flwang | the pooling catalog is always placed in the management node | 13:30 |
| flwang | that means the pooling/catalog info is always stored in sqlalchemy or mongodb | 13:31 |
| flwang | venkat_: i don't have a sample conf in hand now, will generate it later to take a look | 13:31 |
| venkat_ | oh if we provide sqlalchemy here under pooling:catalog then it will refer mgmt store details in zaqar.conf and use it ? | 13:32 |
| flwang | venkat_: it should. but i always put the backend info under [drivers], like "management_store = sqlalchemy" | 13:33 |
| venkat_ | flwang, ok | 13:33 |
| venkat_ | flwang, do you have tried APIs using curl for pool and flavor in handy for reference.. I need to explore & understand them.. | 13:35 |
| *** khushbu_ has joined #openstack-zaqar | 13:38 | |
| *** csoukup has quit IRC | 13:38 | |
| *** nate_gone is now known as njohnston | 13:50 | |
| flwang | venkat_: yep, wait a mon | 13:55 |
| venkat_ | flwang, sure | 13:56 |
| *** sriram has joined #openstack-zaqar | 13:56 | |
| *** khushbu_ has quit IRC | 13:56 | |
| flwang | https://wiki.openstack.org/wiki/Zaqar/specs/api/v1.1 | 13:57 |
| vkmc | flwang, looks good! | 13:58 |
| venkat_ | flwang, I saw them.. | 13:59 |
| venkat_ | flwang, thanks | 13:59 |
| *** flwang has quit IRC | 14:01 | |
| *** flwang has joined #openstack-zaqar | 14:04 | |
| venkat_ | flwang, if I have two zaqar setups and want to migrate data stored in mongodb to another setup. Is there a way to do this ? why I am asking this question is any solution is available to migrate one setup queue data to another setup ? | 14:04 |
| flwang | i think you can add the database as a pool | 14:05 |
| venkat_ | like active & stand-by scenario during failure cases | 14:05 |
| flwang | but it depends on if you were using pooling | 14:06 |
| *** csoukup has joined #openstack-zaqar | 14:06 | |
| venkat_ | flwang, didn't got! | 14:08 |
| *** ametts has joined #openstack-zaqar | 14:08 | |
| *** khushbu_ has joined #openstack-zaqar | 14:08 | |
| flwang | venkat_: zaqar is using pooling to get that | 14:08 |
| flwang | venkat_: for the transport layer, you can use haproxy | 14:09 |
| flwang | for storage layer, you can use pooling and the HA of the database | 14:09 |
| venkat_ | flwang, then I need to have only one db which will be accessed by two setups (active & standby) | 14:10 |
| flwang | venkat_: i don't think 'setup' is a good word under this case, but technically yes. you can search haproxy to get more info | 14:13 |
| venkat_ | flwang, I can use haproxy to load balance | 14:13 |
| venkat_ | flwang, my question is - I have two setups (zaqar with mongdb) ie., active & standby. Users able to create queues etc using active setup and lets suppose if active setup is down due to hardware failure and I want to migrate data available in mongodb to standby setup and resume it | 14:15 |
| venkat_ | flwang, how I can migrate data available on active to standby ? | 14:16 |
| flwang | venkat_: for that case, like i mentioned above, you're worrying about the database side | 14:17 |
| flwang | for that case, you should use pooling | 14:17 |
| venkat_ | flwang, can u provide more details please ? | 14:18 |
| flwang | make the database as a pool name | 14:18 |
| flwang | s/name/node | 14:18 |
| flwang | venkat_: does that make any sense? | 14:19 |
| venkat_ | flwang, when I have pool name. How I can create queues on a pool ? | 14:19 |
| venkat_ | flwang, if I have database as a pool name.. how I can configure it in zaqar.conf ? | 14:21 |
| *** exploreshaifali_ has joined #openstack-zaqar | 14:24 | |
| Eva-i | Hello. Is it okay that after performing tests on zaqar, there are undropped databases left in mongodb (about 6GB)? | 14:27 |
| flwang | you can get more info from the wiki link i sent above | 14:30 |
| venkat_ | flwang, I saw pool related api's but how I can create a queue and store in respective pool ? | 14:32 |
| Eva-i | Maybe databases must be properly wiped out during tearDown() | 14:32 |
| Eva-i | ? | 14:32 |
| flwang | when you create a pool, you need to give the uri of the db | 14:33 |
| flwang | have database as a pool node not pool name | 14:34 |
| Eva-i | vkmc: what do you think? | 14:35 |
| venkat_ | flwang, let me ask one question - if I create a pool with one uri and how I can create a queue on this pool ? | 14:36 |
| *** kgriffs|afk is now known as kgriffs | 14:39 | |
| venkat_ | flwang, whatever we create pool, queue, message posted to queue etc will be stored in backend ie., mongodb | 14:42 |
| *** khushbu_ has quit IRC | 14:42 | |
| venkat_ | flwang, where zaqar stores data in mongodb ? I mean any DB will be created by default ? | 14:45 |
| *** flwang has quit IRC | 14:49 | |
| venkat_ | flwang, I am seeing zaqar created db's like zaqar_queues, zaqar_messages_p0, zaqar_subscriptions etc on mongodb.. so if I copy these dbs to another mongodb setup during setup failure scenarios | 14:53 |
| vkmc | Eva-i, I think that is a bug, there should be no traces after running the tests | 14:53 |
| vkmc | venkat_, you can specify the db in the configuration file (zaqar.conf) | 14:54 |
| venkat_ | vkmc, you mean to say.. I can create a db and provide the same in zaqar.conf and zaqar will created required databases like zaqar_queues, zaqar_messages_p0, zaqar_subscriptions etc on mentioned db ? | 14:56 |
| vkmc | venkat_, exactly | 14:56 |
| vkmc | venkat_, regarding the queue creation within a pool, IIRC Zaqar manages this automatically | 14:56 |
| vkmc | I'm looking for the docs for it | 14:56 |
| vkmc | to make sure | 14:56 |
| vkmc | well, cannot find the official docs but here is one blog post that will shed some light on how pools work http://blog.flaper87.org/post/zaqar-pools-explained/ | 14:57 |
| vkmc | we use a weighted algorithm to manage pools | 14:57 |
| venkat_ | vkmc, if there is a failure in one setup then I can copy our created db to another mongodb setup and link or configure the same and use it | 14:57 |
| vkmc | venkat_, I'd say so, yes | 14:58 |
| vkmc | the only information we store is related to queues/topics and messages, nothing about the host where they live | 14:59 |
| Eva-i | vkmc: Alright. I can fix those. I already found a way to drop databases in one of the affected tests. But the way involves accessing private variable. :o | 14:59 |
| Eva-i | vkmc: I would like to talk about dropping databases later. | 14:59 |
| venkat_ | vkmc, but I am not clear with pools ie., when I create/register multiple pools in zaqar using API's and if I say create queue.. where it will create queue on which pool ? | 15:00 |
| vkmc | Eva-i, that sounds good, let's discuss that in the weekly meeting as well | 15:00 |
| Eva-i | vkmc: okay | 15:01 |
| venkat_ | vkmc, I am not seeing any pool parameter provided while creating a queue! | 15:04 |
| vkmc | venkat_, that is determined by the distribution algorithm automatically | 15:09 |
| vkmc | you cannot say "put this queue on this pool" | 15:09 |
| vkmc | please read the blog post so its more understandable how the pools work | 15:09 |
| venkat_ | vkmc, so zaqar will decide and use existing pools accordingly! | 15:11 |
| vkmc | venkat_, exactly | 15:11 |
| vkmc | queues are distributed according to the load in each pool | 15:12 |
| venkat_ | vkmc, how load is distributed ? any config is required in zaqar ? | 15:13 |
| vkmc | venkat_, the algorithm we are currently using is depicted in http://blog.flaper87.org/post/zaqar-pools-explained/ | 15:13 |
| venkat_ | vkmc, oh zaqar will do automatically then.. users can't control it as a part of configuration | 15:14 |
| vkmc | exactly | 15:14 |
| exploreshaifali_ | vkmc, I thought flavors have some role in connecting pools and queues, is it true or not? | 15:15 |
| vkmc | exploreshaifali_, flavors define the capabilities of a pool | 15:16 |
| vkmc | e.g. FIFO | 15:16 |
| venkat_ | vkmc, in that case.. if there is a need to migrate zaqar data from one setup to another setup then I need to copy all existing pool db's and db's created by zaqar in mongodb | 15:16 |
| vkmc | venkat_, yeah, I think migration can handled that way | 15:16 |
| vkmc | can be* | 15:17 |
| vkmc | still, I don't have production experience with Zaqar and cannot confirm it | 15:17 |
| vkmc | maybe there is an easier way | 15:17 |
| vkmc | flwang and flaper87 can relate later | 15:17 |
| venkat_ | vkmc, ok | 15:17 |
| exploreshaifali_ | all right, Thanks vkmc :) | 15:18 |
| venkat_ | exploreshaifali, what are the capabilities of a pool.. I am seeing only "durable" parameter under it.. is there any other available ? | 15:18 |
| exploreshaifali_ | venkat_, we can have different pools with different capabilities | 15:21 |
| exploreshaifali_ | like mongodb have different capabilities than redis | 15:22 |
| exploreshaifali_ | so another capability can be speed | 15:22 |
| exploreshaifali_ | which will come from redis | 15:22 |
| exploreshaifali_ | and durability will come from mongodb | 15:23 |
| vkmc | venkat_, https://github.com/openstack/zaqar/blob/master/zaqar/storage/base.py#L47-L51 | 15:24 |
| exploreshaifali_ | I think capabilty comes from storage type only, is it correct vkmc ? | 15:24 |
| vkmc | yes | 15:24 |
| vkmc | that's correct | 15:24 |
| venkat_ | ok | 15:25 |
| vkmc | fifo, claims, durability, at least once delivery and high-throughput are the base capabilities | 15:25 |
| exploreshaifali_ | ok.... the above link also explain thing :) | 15:25 |
| exploreshaifali_ | Thanks viki | 15:25 |
| exploreshaifali_ | :D | 15:25 |
| venkat_ | thanks | 15:25 |
| vkmc | mongodb can have them all, as needed | 15:25 |
| exploreshaifali_ | does that mean theoretically we can have only 3 types of flavor because zaqar support only 3 database atm? | 15:26 |
| vkmc | redis doesn't allow durability, but it allows the rest of them | 15:26 |
| vkmc | we don't have only 3 types of flavors... the flavors are defined by the operator according to their needs | 15:26 |
| vkmc | the stores then define if its possible to have the set of capabilities for the defined flavor | 15:27 |
| *** ametts has quit IRC | 15:27 | |
| vkmc | e.g. you cannot define a flavor with the durability capability for a redis pool | 15:27 |
| exploreshaifali_ | hmm.... make sense | 15:28 |
| vkmc | we have to do a very important work with documentation | 15:28 |
| exploreshaifali_ | so a pool can have only one flavor, obviously | 15:28 |
| vkmc | >.< | 15:28 |
| vkmc | yes | 15:29 |
| exploreshaifali_ | I going to write a blog for pools and flavor of zaqar | 15:29 |
| exploreshaifali_ | :p | 15:29 |
| exploreshaifali_ | its something always people ask | 15:29 |
| vkmc | that would be awesome | 15:29 |
| vkmc | then we can make a wiki from them | 15:29 |
| exploreshaifali_ | yup | 15:30 |
| exploreshaifali_ | but it will not as awesome as you are | 15:30 |
| exploreshaifali_ | :P | 15:30 |
| exploreshaifali_ | haha | 15:30 |
| vkmc | I wouldn't say that, you are as awesome as every other contributor here in Zaqar :) | 15:31 |
| exploreshaifali_ | again not as awesome as you are | 15:31 |
| exploreshaifali_ | ;) | 15:31 |
| exploreshaifali_ | never mind, I will beat you one day | 15:31 |
| exploreshaifali_ | :D | 15:31 |
| *** venkat_ has quit IRC | 15:32 | |
| exploreshaifali_ | gtg dinner :) | 15:33 |
| *** exploreshaifali_ has quit IRC | 15:33 | |
| vkmc | enjoy! | 15:33 |
| *** ametts has joined #openstack-zaqar | 15:34 | |
| *** khushbu_ has joined #openstack-zaqar | 15:49 | |
| *** khushbu_ has quit IRC | 16:15 | |
| *** Qiming has quit IRC | 16:18 | |
| *** malini has joined #openstack-zaqar | 16:25 | |
| *** malini has left #openstack-zaqar | 16:26 | |
| *** dynarro has quit IRC | 16:35 | |
| *** achanda has joined #openstack-zaqar | 17:07 | |
| *** khushbu_ has joined #openstack-zaqar | 17:10 | |
| openstackgerrit | Eva Balycheva proposed openstack/zaqar: Make websocket run in correct logging mode https://review.openstack.org/233746 | 17:29 |
| *** achanda has quit IRC | 17:43 | |
| *** achanda has joined #openstack-zaqar | 17:47 | |
| *** khushbu_ has quit IRC | 18:01 | |
| *** stanchan has joined #openstack-zaqar | 18:10 | |
| *** stanchan_ has joined #openstack-zaqar | 18:24 | |
| *** stanchan has quit IRC | 18:25 | |
| *** itisha has joined #openstack-zaqar | 18:25 | |
| *** stanchan_ has quit IRC | 18:36 | |
| *** achanda has quit IRC | 19:54 | |
| *** AAzza has quit IRC | 20:06 | |
| *** AAzza has joined #openstack-zaqar | 20:08 | |
| *** njohnston is now known as nate_gone | 20:16 | |
| *** exploreshaifali has joined #openstack-zaqar | 20:18 | |
| *** achanda has joined #openstack-zaqar | 20:28 | |
| *** amitgandhinz has quit IRC | 20:31 | |
| *** itisha has quit IRC | 20:31 | |
| *** amitgandhinz has joined #openstack-zaqar | 20:34 | |
| *** amitgandhinz has quit IRC | 20:35 | |
| *** amitgandhinz has joined #openstack-zaqar | 20:36 | |
| jasondotstar | meeting today? | 21:07 |
| jasondotstar | vkmc, flaper87 ^ | 21:07 |
| *** nate_gone is now known as njohnston | 21:07 | |
| vkmc | oh yes | 21:08 |
| vkmc | flaper87, can you chair the meeting? | 21:08 |
| *** kgriffs is now known as kgriffs|afk | 21:08 | |
| vkmc | apparently no | 21:09 |
| vkmc | ok | 21:09 |
| vkmc | I'll do that | 21:09 |
| vkmc | jasondotstar, started the meeting | 21:11 |
| jasondotstar | ack | 21:11 |
| vkmc | flaper87 | 21:11 |
| vkmc | ryansb, therve | 21:11 |
| vkmc | Eva-i, | 21:11 |
| vkmc | exploreshaifali, | 21:11 |
| mdnadeem_ | vkmc: This time i am also there to attain the meeting :) | 21:14 |
| vkmc | yes! | 21:15 |
| vkmc | mdnadeem_, feel free to join | 21:15 |
| vkmc | we can maybe leave your comments in the log regarding pools for flaper87 and flwang to see later | 21:16 |
| mdnadeem_ | vkmc: Thanks :) | 21:16 |
| vkmc | #openstack-meeting-3 | 21:17 |
| mdnadeem_ | I have a thought for the pool group : Please have a look at this link | 21:19 |
| mdnadeem_ | http://paste.openstack.org/show/475989/ | 21:20 |
| vkmc | mdnadeem_, join us in the meeting and we can discuss this in the open discussion :) | 21:20 |
| mdnadeem_ | vkmc: yah , sure | 21:20 |
| *** zhiyan has quit IRC | 21:20 | |
| *** sriram has quit IRC | 21:25 | |
| *** ameade has quit IRC | 21:26 | |
| *** Caleb-- has quit IRC | 21:38 | |
| *** Caleb-- has joined #openstack-zaqar | 21:40 | |
| vkmc | mdnadeem_, we are about to start open discussion, want to join #openstack-meeting-3? | 21:51 |
| mdnadeem_ | vkmc: yes plz | 21:53 |
| *** csoukup has quit IRC | 21:53 | |
| *** amitgandhinz has quit IRC | 21:57 | |
| *** achanda has quit IRC | 22:01 | |
| vkmc | mdnadeem_, k, we ran out of time | 22:02 |
| mdnadeem_ | vkmc: yah , so lets start it. | 22:03 |
| exploreshaifali | so vkmc will you reply on thread pointing about "openstack message message post" and giving "pool-flavor" option, with which we will not to deprecate other endpoints | 22:03 |
| exploreshaifali | or you wanna me to do that? | 22:03 |
| exploreshaifali | mdnadeem_, \o | 22:04 |
| vkmc | exploreshaifali, I can reply to that :) sorry I haven't replied earlier | 22:04 |
| vkmc | let's see what other people have to say about it | 22:04 |
| exploreshaifali | sure :) | 22:04 |
| exploreshaifali | Thanks viki! | 22:04 |
| exploreshaifali | :D | 22:05 |
| vkmc | thanks to you Shaifali! | 22:05 |
| exploreshaifali | :) | 22:05 |
| mdnadeem_ | exploreshaifali: can i have thread link? | 22:05 |
| exploreshaifali | sure | 22:06 |
| * Eva-i reading mdnadeem_'s paste | 22:06 | |
| exploreshaifali | mdnadeem_, http://lists.openstack.org/pipermail/openstack-dev/2015-October/076269.html | 22:06 |
| vkmc | oh I missed the line with the paste | 22:07 |
| * vkmc reading mdnadeem_'s paste too | 22:07 | |
| * exploreshaifali too | 22:08 | |
| mdnadeem_ | exploreshaifali: Its a sound good, I think we should implement it. | 22:08 |
| vkmc | btw exploreshaifali, I'll try to contact someone in UX to provide some feedback about the mockups | 22:08 |
| exploreshaifali | will be great vkmc :) but before that I want zaqar people point of view | 22:09 |
| vkmc | makes sense | 22:09 |
| *** stanchan has joined #openstack-zaqar | 22:09 | |
| exploreshaifali | :) | 22:09 |
| vkmc | let's delay that then :D | 22:09 |
| exploreshaifali | mdnadeem_, yes, but than vkmc gave another idea to have "pool-flavor' only for zaqar's flavor commands | 22:10 |
| exploreshaifali | haha vkmc of course! | 22:10 |
| exploreshaifali | :D | 22:10 |
| *** achanda has joined #openstack-zaqar | 22:10 | |
| mdnadeem_ | exploreshaifali: That can also be done. We should try to keep same same formate for all zaqar commands. | 22:14 |
| exploreshaifali | make sense. | 22:15 |
| exploreshaifali | so vkmc ^^ | 22:16 |
| exploreshaifali | I think pool-flavor will be okay, will not violate formate as such | 22:17 |
| vkmc | so, looking at the api description | 22:17 |
| exploreshaifali | the problem with "message " is impact with on other commands, like "openstack message message post" | 22:17 |
| vkmc | https://wiki.openstack.org/wiki/Zaqar/specs/api/v1.1#Queue_Flavors <- | 22:17 |
| exploreshaifali | mdnadeem_, ^^ | 22:17 |
| vkmc | queue-flavors sounds nicer | 22:18 |
| vkmc | openstack queue-flavor create | 22:18 |
| vkmc | openstack queue-flavor get | 22:18 |
| exploreshaifali | but flavor are more attached with pools, right? they are to expose pools only | 22:18 |
| vkmc | openstack queue-flavor delete | 22:18 |
| vkmc | I know | 22:18 |
| exploreshaifali | I think logically poll-flavor is more correct | 22:18 |
| exploreshaifali | pool-flavor* | 22:19 |
| mdnadeem_ | agree ^^ | 22:19 |
| vkmc | yeah | 22:19 |
| exploreshaifali | so we will move ahead on ML for this | 22:20 |
| vkmc | sounds good to me | 22:20 |
| vkmc | :) | 22:20 |
| exploreshaifali | lets now read mdnadeem_ 's pool idea | 22:20 |
| exploreshaifali | :P | 22:20 |
| mdnadeem_ | thanks :) | 22:21 |
| exploreshaifali | :D | 22:21 |
| *** ameade has joined #openstack-zaqar | 22:21 | |
| mdnadeem_ | exploreshaifali:vkmc: I really feel, there should be a method which list all group present in the env. | 22:22 |
| exploreshaifali | make sense | 22:23 |
| mdnadeem_ | such that a user can link their flavor to a particular pool group | 22:23 |
| mdnadeem_ | vkmc: ^^ | 22:24 |
| mdnadeem_ | Eva-i: ^^ | 22:24 |
| *** zhiyan has joined #openstack-zaqar | 22:25 | |
| exploreshaifali | mdnadeem_, what does a group specify for pool? | 22:25 |
| Eva-i | What is pool group? | 22:25 |
| exploreshaifali | like flavor do capabilities | 22:25 |
| vkmc | Eva-i, http://blog.flaper87.org/post/zaqar-pools-explained/ | 22:27 |
| mdnadeem_ | flavor link with a particular group, and under that group there can be multiple pools | 22:27 |
| vkmc | :) | 22:27 |
| *** achanda has quit IRC | 22:29 | |
| mdnadeem_ | so at the end flavor capability link with group according to the pools (backend storage)attached to this group. | 22:31 |
| Eva-i | Okay, thank you | 22:32 |
| mdnadeem_ | lets say we create multiple pools on different node, having same capability say durable, so we can group all pool to a group(and link durable capability to this group) | 22:33 |
| *** flwang has joined #openstack-zaqar | 22:33 | |
| mdnadeem_ | make sense? | 22:33 |
| mdnadeem_ | <exploreshaifali>:vkmc: ^^ | 22:34 |
| exploreshaifali | but this can be done with flavor solely , why group? | 22:34 |
| mdnadeem_ | exploreshaifali: capability depends on storage pool, so you must have to link a flavor to a prticular pool group | 22:36 |
| exploreshaifali | okay | 22:37 |
| vkmc | flaper87, if you have a moment later, add a note about the upgrade to MongoDB 3.0 and which is the minimum version of MongoDB we currently support https://wiki.openstack.org/wiki/ReleaseNotes/Liberty#OpenStack_Messaging_Service_.28Zaqar.29 | 22:38 |
| exploreshaifali | Thanks mdnadeem_ :) | 22:38 |
| mdnadeem_ | exploreshaifali: Please have a look at create flavor on : https://wiki.openstack.org/wiki/Zaqar/specs/api/v1.1 | 22:38 |
| exploreshaifali | okay | 22:38 |
| * exploreshaifali looking | 22:39 | |
| mdnadeem_ | flwang: Please have a look at http://paste.openstack.org/show/475989/ | 22:39 |
| mdnadeem_ | flawng: give your openion. | 22:40 |
| flwang | mdnadeem_: no problem | 22:40 |
| flwang | mdnadeem_: is that the concern you mentioned to vkmc ? | 22:41 |
| vkmc | mdnadeem_, yeah | 22:41 |
| mdnadeem_ | yes | 22:41 |
| vkmc | :) | 22:41 |
| flwang | vkmc: mdnadeem_: i mentioned the same issue with flaper87, we admit it's a limitation of current pool group | 22:43 |
| vkmc | oh cool, I missed that discussion | 22:43 |
| flwang | IIRC, the only reason we didn't do that is because we don't want to change the API too often | 22:43 |
| *** ametts has quit IRC | 22:44 | |
| mdnadeem_ | flwang: in near future, may be we change it ? | 22:46 |
| flwang | mdnadeem_: yes | 22:46 |
| flwang | mdnadeem_: it would be nice if you can propose a spec so that we can review it with an official flow :) | 22:46 |
| flwang | thanks for raising this | 22:47 |
| mdnadeem_ | flwang: That sound good, sure i will do it | 22:47 |
| vkmc | it doesn't seem we will need to change too much | 22:47 |
| vkmc | s/will/would/ | 22:47 |
| vkmc | at least not to broke the backwards compatibility | 22:48 |
| mdnadeem_ | vkmc:flwang: sure, I would love to work upon it | 22:48 |
| vkmc | this change could be transparent for the operator | 22:48 |
| flwang | vkmc: yep, i agree | 22:48 |
| flwang | vkmc: i can't remember if there is any other reason why we didn't do that | 22:48 |
| vkmc | flwang, hmm not that I can recall now... maybe flaper87 has an objection about it | 22:49 |
| vkmc | but in the meantime, I think it makes sense to start considering it as a possible change for M | 22:49 |
| flwang | may be just b/c the limited resource :D | 22:49 |
| *** kgriffs|afk is now known as kgriffs | 22:49 | |
| vkmc | yeah heh, that is probably the case | 22:49 |
| vkmc | mdnadeem_, thanks for volunteering to tackle this down, it would be a great addition | 22:50 |
| mdnadeem_ | vkmc: :) | 22:50 |
| flwang | my littler hacker is around, so may be there is a 'no' which i want to say 'yes' :) | 22:51 |
| vkmc | flwang, haha | 22:51 |
| exploreshaifali | haha | 22:52 |
| flwang | exploreshaifali: hi | 22:52 |
| vkmc | flwang, how is he doing? enjoying holidays? | 22:52 |
| exploreshaifali | flwang, hi | 22:52 |
| flwang | vkmc: yep, really happy everyday | 22:52 |
| vkmc | that's great to hear | 22:52 |
| flwang | vkmc: i would like to put his name on the horizon demo's leader, would you mind? | 22:53 |
| vkmc | flwang, with the only condition that you take him to the working session | 22:53 |
| flwang | exploreshaifali: i saw your mail about the client | 22:53 |
| exploreshaifali | what is his name? | 22:53 |
| flwang | i'm happy to use 'messaging' as the prefix for all zaqar commands | 22:53 |
| exploreshaifali | flwang, okay, so what are your views? | 22:53 |
| flwang | and i have already worked out a simple patch | 22:53 |
| flwang | for that | 22:53 |
| flwang | exploreshaifali: for v1, we should keep back compatibility | 22:54 |
| flwang | for v2, we can just use that | 22:55 |
| exploreshaifali | flwang, cool, but vkmc pointed one thing, the impact that other commands will get, for eg "openstack message message post" | 22:55 |
| exploreshaifali | so rather than changing all command, we can only use "pool-flavor" for Zaqar's flavor? | 22:56 |
| flwang | "openstack messaging message post" is the cost we should pay :) | 22:56 |
| exploreshaifali | no problem :) | 22:56 |
| mdnadeem_ | <exploreshaifali>: Can we use "zaqar" word inplace of message, like others use nova list | 22:57 |
| vkmc | oh that could work as well | 22:57 |
| vkmc | openstack zaqar message pos t | 22:57 |
| * vkmc likes | 22:57 | |
| exploreshaifali | +1 | 22:57 |
| vkmc | and maybe once for all everybody learns how to spell zaqar :D | 22:58 |
| flwang | that's another option | 22:58 |
| vkmc | haha | 22:58 |
| mdnadeem_ | :) | 22:58 |
| exploreshaifali | LOL | 22:58 |
| flwang | [[[[[[[[[[[[[[[[[[[[ | 22:58 |
| flwang | sorry, above msg is from my little hacker | 22:58 |
| vkmc | little hacker seems to like lisp | 22:58 |
| exploreshaifali | flwang, also I want your opinions for Zaqar UI | 22:59 |
| flwang | vkmc: lol | 22:59 |
| vkmc | flwang, some new version with [ instead of ( :P | 22:59 |
| flwang | exploreshaifali: i'm going to reply that mail, but i can give a summary at here | 22:59 |
| exploreshaifali | sure, thanks | 22:59 |
| flwang | exploreshaifali: 1. both the pool and flavor panel should be placed under 'admin' instead of 'project' | 23:00 |
| exploreshaifali | ok | 23:00 |
| *** itisha has joined #openstack-zaqar | 23:00 | |
| vkmc | good point | 23:01 |
| vkmc | flwang++ | 23:01 |
| mdnadeem_ | +1 | 23:01 |
| *** david-ly_ has joined #openstack-zaqar | 23:01 | |
| exploreshaifali | vkmc++ | 23:01 |
| exploreshaifali | :P | 23:01 |
| flwang | 2. for the style, we can just follow the normal way | 23:01 |
| flwang | like the image panel | 23:01 |
| *** david-lyle has quit IRC | 23:02 | |
| exploreshaifali | ok | 23:02 |
| flwang | 3. we need the 'queue' panel and 'subscription' panel either, which has higher priority than 'pool' and 'flavor', IMHO | 23:03 |
| flwang | 4. we need to figure out where to hold the source code | 23:03 |
| flwang | in a new dashboard project or horizon | 23:04 |
| flwang | if we can get it in horizon repo, it would be a big win | 23:04 |
| *** david-lyle has joined #openstack-zaqar | 23:04 | |
| *** david-ly_ has quit IRC | 23:04 | |
| flwang | 5. I can't remember the #5 :D | 23:05 |
| exploreshaifali | so I wii confirm it with horizon developers, if we can add zaqar ui code there | 23:05 |
| exploreshaifali | hahaha | 23:05 |
| flwang | exploreshaifali: based on my discussion with horizon team, we can't do that :( | 23:06 |
| exploreshaifali | I will make the changes as you pointed and post on thread about the changes made | 23:06 |
| flwang | but maybe now there are some difference | 23:06 |
| exploreshaifali | oh :/ | 23:06 |
| exploreshaifali | cool! will check once :) | 23:06 |
| flwang | FWIW, horizon support is very important for zaqar | 23:07 |
| flwang | thank you so much for working on this | 23:07 |
| flwang | exploreshaifali: pls feel free let me know if you need any help | 23:07 |
| exploreshaifali | thanks for letting me know its value :) | 23:07 |
| exploreshaifali | sure thing, and thanks for help :) | 23:08 |
| flwang | exploreshaifali: will you go to tokyo? | 23:08 |
| exploreshaifali | flwang, ^ | 23:08 |
| exploreshaifali | yes | 23:08 |
| flwang | exploreshaifali: awesome, we can talk more details there | 23:08 |
| exploreshaifali | I have added one design session for Zaqar UI https://etherpad.openstack.org/p/Mitaka-Zaqar | 23:08 |
| exploreshaifali | sure | 23:08 |
| flwang | exploreshaifali: coooooooooooooooool | 23:08 |
| exploreshaifali | :D | 23:09 |
| vkmc | uber-cool | 23:09 |
| flwang | exploreshaifali: will it be a demo? | 23:09 |
| exploreshaifali | I think a working demo will be ready by next summit | 23:10 |
| exploreshaifali | but will try as much as I can cover till tokyo summit | 23:10 |
| exploreshaifali | atm getting BP ready | 23:10 |
| vkmc | demo as in mockups for us to watch is already awesome | 23:10 |
| vkmc | :D | 23:10 |
| exploreshaifali | https://blueprints.launchpad.net/horizon/+spec/zaqar-ui | 23:10 |
| mdnadeem_ | exploreshaifali: sound great :) | 23:10 |
| exploreshaifali | oh yea, sure vkmc | 23:11 |
| exploreshaifali | :D | 23:11 |
| exploreshaifali | mdnadeem_, yes! | 23:11 |
| *** flwang has quit IRC | 23:13 | |
| mdnadeem_ | exploreshaifali: vkmc: flawng: I am worried about zaqar documentation | 23:13 |
| vkmc | nothing to worry about... something to work on in the next couple of weeks though | 23:14 |
| exploreshaifali | mdnadeem_, don't worry we have started discussion abot it as well | 23:14 |
| Eva-i | I really wish I could actively participate in your cheerful conversation, but sometimes I still can't open my mouth because of lack of the knowledge. | 23:14 |
| exploreshaifali | mdnadeem_, you can add your ideas https://etherpad.openstack.org/p/zaqar-mitaka-docs | 23:14 |
| mdnadeem_ | are we going to prepare spec doc for v2 , just like v1.1? | 23:14 |
| exploreshaifali | Eva-i, chill, this is the case with everyone | 23:14 |
| exploreshaifali | I also don't understand many stuff many times | 23:15 |
| vkmc | Eva-i, your POV is very useful... there are some things we usually forget because we already got used to them heh | 23:15 |
| mdnadeem_ | Eva-i: same here too | 23:15 |
| exploreshaifali | but being persistence is the key :) | 23:15 |
| exploreshaifali | Eva-i, mdnadeem_ same here too | 23:16 |
| exploreshaifali | :P | 23:16 |
| exploreshaifali | * this is the case with everyone who are new | 23:16 |
| mdnadeem_ | vkmc: exploreshaifali: So let me know if i can help you guys in documentation part in any way, | 23:18 |
| Eva-i | Novices are a good tools to find inconsistencies hidden from core developer's eyes =) | 23:18 |
| Eva-i | *are good tools | 23:18 |
| vkmc | Eva-i, indeed | 23:18 |
| exploreshaifali | sure thing mdnadeem_ :) | 23:18 |
| exploreshaifali | Eva-i, absolutely | 23:18 |
| vkmc | mdnadeem_, if you can start some docs for pools/flavors it would be really appreciated | 23:18 |
| vkmc | since you were working on that | 23:18 |
| vkmc | :) | 23:18 |
| mdnadeem_ | exploreshaifali: Sure , i will prepare it very soon | 23:19 |
| mdnadeem_ | *vkmc ^^ | 23:19 |
| exploreshaifali | Thanks mdnadeem_ :) | 23:19 |
| exploreshaifali | ;) | 23:19 |
| vkmc | great, thanks mdnadeem_! | 23:19 |
| mdnadeem_ | :) | 23:19 |
| mdnadeem_ | vkmc:exploreshaifali:flwang: Please have a look at this bug :https://bugs.launchpad.net/zaqar/+bug/1503997 | 23:20 |
| openstack | Launchpad bug 1503997 in zaqar " Creating a pool or flavor with an existing name should through an Exception" [Undecided,New] - Assigned to MD NADEEM (mail2nadeem92) | 23:20 |
| mdnadeem_ | Please give your opinions | 23:21 |
| exploreshaifali | mdnadeem_ we had a discussion on this bug previously, I think you need noise from vkmc | 23:22 |
| mdnadeem_ | vkmc: ^^ | 23:23 |
| vkmc | mdnadeem_, definitely a bug | 23:24 |
| vkmc | I thought that maybe we were using the create endpoint to create/update pool/flavors, but then I remembered we have patch for that | 23:24 |
| mdnadeem_ | vkmc: exploreshaifali: same was click at my mind also :) | 23:25 |
| vkmc | performance-wise shouldn't be so hard, since the db for pools/flavors is in control plane | 23:25 |
| vkmc | so checking if a key exists should not be so complex | 23:26 |
| mdnadeem_ | vkmc: yes, its simple | 23:27 |
| *** flwang has joined #openstack-zaqar | 23:28 | |
| flwang | exploreshaifali: still around? | 23:28 |
| mdnadeem_ | vkmc: exploreshaifali: So am i suppose to start working on it , or should i wait to get it confirm by some one | 23:28 |
| exploreshaifali | yes yes flwang | 23:28 |
| flwang | exploreshaifali: did i lost any msg? | 23:28 |
| mdnadeem_ | flwang: We are talking about https://bugs.launchpad.net/zaqar/+bug/1503997 | 23:29 |
| openstack | Launchpad bug 1503997 in zaqar " Creating a pool or flavor with an existing name should through an Exception" [Undecided,New] - Assigned to MD NADEEM (mail2nadeem92) | 23:29 |
| exploreshaifali | flwang, no, we will discuss more in summit by that time I will prepare first version of mockups | 23:29 |
| flwang | exploreshaifali: ok, got it | 23:31 |
| exploreshaifali | :D | 23:31 |
| exploreshaifali | flwang, did you got the last point, that you forgot? | 23:32 |
| exploreshaifali | :P | 23:32 |
| flwang | exploreshaifali: ah, yes | 23:32 |
| exploreshaifali | :D | 23:32 |
| flwang | 5. racksapce has already implemented a GUI for zaqar/marconi | 23:33 |
| flwang | maybe we get some inspirations from that | 23:33 |
| exploreshaifali | oh.... okay, Thanks for information, I will make sure to look at it as well | 23:33 |
| flwang | exploreshaifali: i can help implement a PoC for the queue and subscription if you would like to show a demo at summit | 23:34 |
| exploreshaifali | PoC? | 23:35 |
| flwang | proof of concept | 23:35 |
| exploreshaifali | flwang, sure thing for demo | 23:35 |
| exploreshaifali | cool, so I am suppose to prepare a working mock-ups demo | 23:36 |
| exploreshaifali | that contain, message, notification tabs | 23:36 |
| flwang | ok, it would be cool | 23:36 |
| flwang | exploreshaifali: just let me know if you need help | 23:37 |
| exploreshaifali | under each there will be pools, flavor, queues, subscription | 23:37 |
| exploreshaifali | flwang, we will keep message and notification separate in UI, right? | 23:37 |
| flwang | exploreshaifali: i don't think we need a message panel, we need a queue panel | 23:41 |
| flwang | and yes, they are separated | 23:41 |
| flwang | just think aloud, we need more discussion | 23:41 |
| exploreshaifali | okay | 23:41 |
| exploreshaifali | thanks flwang :) | 23:41 |
| flwang | exploreshaifali: thank you for working on this | 23:42 |
| exploreshaifali | :D | 23:42 |
| flwang | exploreshaifali: you can create a patch for horizon repo, then we can review it and get some feedback from horizon team | 23:44 |
| flwang | for now, we just need to mark it as WIP | 23:44 |
| flwang | does that make sense? | 23:44 |
| exploreshaifali | flwang, yes, but I don't know where I am suppose to start from in horizon | 23:45 |
| exploreshaifali | or you want a blank patch? | 23:45 |
| flwang | exploreshaifali: oh, so the demo you mean is just some images for the style, not a working demo, right? | 23:46 |
| exploreshaifali | yes, the mock-ups | 23:47 |
| flwang | ah | 23:47 |
| flwang | exploreshaifali: ok | 23:47 |
| exploreshaifali | well, let see if I can dive into there code and figure out to make working demo possible | 23:47 |
| exploreshaifali | what is your timezone flwang ? | 23:47 |
| flwang | exploreshaifali: UTC+8 | 23:48 |
| exploreshaifali | because I will need to ask loads of questions till mockups get ready | 23:48 |
| exploreshaifali | okay | 23:48 |
| flwang | exploreshaifali: but i'm in vacation now, you can send mail to me | 23:48 |
| exploreshaifali | at this time you will be available mostly, right? | 23:48 |
| flwang | flwang@catalyst.net.nz | 23:48 |
| exploreshaifali | great :) | 23:48 |
| exploreshaifali | Thanks flwang :) | 23:48 |
| flwang | exploreshaifali: yes? :D | 23:48 |
| flwang | create panel in horizon is super easy | 23:49 |
| exploreshaifali | cool | 23:49 |
| exploreshaifali | yes, I also believe so | 23:49 |
| exploreshaifali | :D | 23:49 |
| flwang | my concern is if our zaqar is really ready for some functions, like the notification | 23:49 |
| exploreshaifali | I don't think it is for notification | 23:50 |
| flwang | yep, for a demo | 23:50 |
| flwang | i think we just need queue, pool and flavor, or just queue and pool to cover the 'project' and 'admin' panel | 23:51 |
| exploreshaifali | flwang, so in admin we will have pool and in project pannel we will have queue? | 23:52 |
| flwang | exploreshaifali: yep, that's my current thought in my mind ;) | 23:53 |
| exploreshaifali | okay :) | 23:53 |
| flwang | besides, we can take SQS and rackspace's UI as reference | 23:53 |
| exploreshaifali | sure thing, I did saw SQS but could't make much sense from it as I thought to have only pools and flavors | 23:55 |
| exploreshaifali | will look at rackspace's UI | 23:56 |
| flwang | exploreshaifali: awesome, thanks | 23:58 |
| exploreshaifali | :) | 23:59 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!