13:00:12 #startmeeting evoque 13:00:12 Meeting started Wed Nov 25 13:00:12 2015 UTC and is due to finish in 60 minutes. The chair is Liuqing. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:15 The meeting name has been set to 'evoque' 13:00:27 hello 13:00:38 hi 13:01:02 today's agenda : https://wiki.openstack.org/wiki/Evoque/Meetings#Agenda_.282015-11-25_1300_UTC.29 13:01:13 go through the agenda 13:02:33 #topic OpenStack SDK 13:03:42 we need to integrate with openstack service so we will use openstack sdk 13:04:33 #link https://github.com/openstack/python-openstacksdk 13:05:24 who has time to research the lib 13:06:15 it include nova/glance/neutron/heat/murano client 13:06:25 but not very hard to use . 13:06:53 what is the purpose? 13:07:11 such create instance/volume 13:07:18 oo 13:08:02 we would use it as evoque client? 13:08:28 someone said murano =) I'm not sure about the context of the meeting, but I'm available to help with murano part, if any assistance is required =) 13:08:53 typical user case , user could apply one instance in the ticket, while someone approve that ticket , the end node will crear instance for it 13:09:14 kzaitsev_mb, it me lawrancejing in tokyo, beers 13:10:03 evoque will use the sdk not client 13:10:26 kzaitsev_mb It is very kind of you 13:11:50 #topic Use SpiffWorkflow as the default workflow engine 13:12:24 sorry for hijacking, just wanted to be around if you'll need any assistance — feel free to ping me. =) 13:12:51 i have complete the default workflow framework, and we can use SpiffWorkflow as the default workflow engine 13:12:59 but the patch is in process 13:13:33 link: https://review.openstack.org/#/c/247521/ add SpiffWorkflow to global-requirements 13:13:48 kzaitsev_mb, it ok, thanks 13:14:10 and the patch need reviews 13:14:52 and now the dashboard could list the workflows 13:15:15 how about devstack process,zhurong 13:16:03 i thought now is right time to enable devstack plugin 13:16:19 It will be in process 13:16:37 OK 13:16:45 a little busy this week 13:17:21 #topic project scope 13:17:42 just now i said the typical user case of evoque 13:18:04 user could apply one instance in the ticket, while someone approve that ticket , the end node will create instance for the user 13:18:17 well, any other cases? 13:18:47 https://wiki.openstack.org/wiki/Evoque has some simple user case 13:20:10 two kinds of user cases: one will communication with other OpenStack service such as nova, cinder, neutron, another won't 13:20:49 our project will focus the two kinds of user cases 13:21:17 this is our project scope, i think 13:22:26 and few minutes later, we can talk about the topic via webex 13:22:44 any thought for the topic? 13:23:04 the first one is OpenStack service, what is the other? 13:25:12 other user case: use has will create ticket such as "my instance is very slow", and such ticket will transition to service team or ops team which will defind in workflow 13:26:12 and this kind of ticket won't communicate with OpenStack service 13:26:33 OK, I got it 13:27:47 but i thought we could focus the user case relevant to OpenStack serivce 13:28:51 I agree 13:29:23 another user case is very easy, just CRUD oprations. 13:29:45 the workflow is very important part of evoque 13:31:06 gongysh_: are you here? 13:31:36 Yes, I think we could get it in the webex then (*^__^*) 13:31:48 OK 13:31:55 last thing 13:32:08 https://review.openstack.org/#/c/247521/ the patch need code review from you guys 13:32:33 so we go to the webex :https://demo.webex.com.cn/demo/j.php?MTID=mba8c59b584c857b44c281828340c49ac 13:32:35 meeting number: 511140309 13:32:41 password: 99cloud!@# 13:33:11 OK 13:34:13 After a minute 13:34:33 yea 13:35:22 could we end the meeting here? 13:36:05 OK 13:36:09 #endmeeting