17:00:11 #startmeeting murano 17:00:11 Meeting started Tue Dec 1 17:00:11 2015 UTC and is due to finish in 60 minutes. The chair is Nikolay_St. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:15 The meeting name has been set to 'murano' 17:00:20 o/ 17:00:23 and it's murano TIIIME! 17:00:26 hi all 17:00:28 hi 17:00:44 ativelkov: and I are both here ) 17:00:57 we don't have much for today, let's start with action items review 17:01:09 #topic Action items review 17:01:11 hi,i'm new. 17:01:22 freerunner: kzaitsev_mb please 17:01:27 hidekazu_: hi 17:01:38 sorry, please. 17:02:00 hidekazu_: do you need explanation about how weekly meetings works? 17:02:10 hi 17:02:18 1) kzaitsev_mb help Li Yingjun with bug #1514692 17:02:18 bug 1514692 in Rally "Murano does not get keystone endpoint when Keystone is configured to use templated catalog" [Undecided,In progress] https://launchpad.net/bugs/1514692 - Assigned to Liyingjun (liyingjun) 17:02:27 well app the patches are merged 17:02:29 no, i read previous log. thanks. 17:02:47 hidekazu_: ok, nice :) 17:02:54 so everything is fine with that item, except, that client gate got blocked for half a day ) 17:03:02 #link https://launchpad.net/bugs/1514692 17:03:21 2) merge dependency blueprints 17:03:26 haven't done that =( 17:03:41 lets move it to next meeting 17:03:51 #action kzaitsev_mb merge dependency blueprints 17:04:15 ok 17:04:17 freerunner: I suupose you'll move the rtfd action to the next meeting too, right? 17:04:52 right? 17:05:04 kzaitsev_mb: here I'am! 17:05:09 Hi guys! 17:05:27 kzaitsev_mb: Yup. Will try to do it ;) 17:05:41 freerunner: kzaitsev_mb thx for updates 17:05:45 #action freerunner add job to Murano CI for building docs for ReadTheDocs 17:06:02 I guess we can move to OpenDiscussion, right? 17:06:28 Nikolay_St: I think you're right ) no agenda for today 17:06:30 #topic Open Discussion 17:06:45 stan invited me to discuss my proposing bp. 17:06:59 hidekazu_: got anything specific? =) or you're just curious about murano? =) 17:07:05 oh cool 17:07:15 please see. 17:07:23 https://review.openstack.org/#/c/246273/ 17:07:32 #link https://review.openstack.org/#/c/246273/ 17:08:53 I want to know what others think about this. 17:09:23 though stan is not here.. 17:09:33 hidekazu_: well community meeting is usually not the best place, cause people would need to read the spec ) 17:09:40 but we'll definitelly give it a read ) 17:10:01 stan_lagun: are you here? 17:10:23 kzaitsev_mb: sorry. you are right. 17:10:31 Nikolay_St: I'm on 2 meetings concurrently :) 17:10:39 oh) 17:10:56 it is a short spec, I think we have time to read it 17:11:58 katyafervent: isn't it better to start openstack-dev list conversation? 17:12:04 just a suggestion 17:12:35 we could, but Stan suggested to come to irc meeting and no one else review this patch ar all 17:12:38 * at all 17:13:17 so it would be good from our side to make it now since we have 40 minutes left and it's open discussion already 17:13:33 stan_lagun is a little bit busy right now, I guess 17:13:58 i need other's opinion. 17:14:45 Actuall my opinion is already there. I'd like to heat what others think 17:14:45 anyone else review is also welcome. 17:15:01 *hear* 17:16:25 our conversation in the review is not short :) 17:16:50 K. So I've got a really short announcement 17:17:01 mitaka-1 is this week. 17:17:09 Actually I don't mind, if this functionality can be easily extended in the future without loosing backward compatibility 17:17:29 I haven't read all comments yet, but generally, I like idea of the spec. I've already saw the same options in other projects. So, if this one will be implemented, in theory. it should increase performance of murano. 17:18:38 I read the spec earlier today and I just wondered why should murano-engine manage workers. sorry it the answer is present - I may miss it 17:18:59 Gonna tag it, probably Thursday. Also gonna release python-client ) 17:19:19 So this is all I wanted to announce =) 17:19:28 kzaitsev_mb: Nice to hear :) 17:19:40 sry, I'm also on 2 meetings concurrently right now ))) 17:19:45 Nikolay_St: we do need them for scalability/HA etc. The question is what proposed approach to be better then alternatives? 17:21:08 stan_lagun: that was I want to say 17:25:13 hidekazu_: so, once again why not deployment tools for this? 17:25:36 can't find an answer for this question in your conversation with stan_lagun 17:27:16 Production environment is need to use deployment tool of course for several machines, i think. 17:30:25 hidekazu_: I'm not against the spec and bp, but I guess you need to be more specific of why you want to do it and why alternatives is not good 17:31:34 you mean best means? 17:31:35 Nikolay_St: that what I was saying. I'm a little bit skeptical about proposed solution but I'm open for an arguments 17:31:51 Because I do have arguments against 17:32:34 for poc etc, easy way is better. 17:33:08 hidekazu_: you mean development environments? 17:33:44 no, such as stress test environment. 17:34:59 fo production enviroment, must create playbooks etc. 17:36:12 and there is also a supervisord who does similar things. Only that it is time proven and very powerful 17:36:27 hidekazu_: we have devstack and puppet-murano 17:36:40 hidekazu_: stan_lagun I've read the spec once again. So I'm not really sure, that workers should be managed by Puppet,, Ansible, etc.. Workers should be spawned as child processes with WSGI help, I think. And shouldn't start manually. 17:38:13 freerunner: I believe that worker management should be external to murano-engine 17:38:53 freerunner: and to Murano API as well 17:40:58 stan_lagun: External? You mean, that murano shouldn't manage workers via wsgi? 17:41:47 stan_lagun: freerunner may be we should create anotheer murano_smthg for workers? 17:42:05 Nikolay_St: looks like reinventing the wheel 17:42:44 stan_lagun: may be, it's a suggestion, nothing more 17:43:55 freerunner: WSGI is also external. What I'm saying is that murano-engine (spec is mainly about engine, isn't it) shouldn't start workers on its own. I think it should be a responsibility of some external system (supervisord, systemd, proper puppets etc) 17:44:49 but again I might be wrong. So what I was asking for is to provide comparison with alternatives in the spec 17:48:44 stan_lagun: hidekazu_ : I'm not sure, that we can find the alternatives, but I agreed in this case. Murano-engine shouldn't start workers by itself. So, using WSGI is a better solution (IMHO), and you can use puppets and other deployment tools just for configure worker count in murano.config. (and start murano services as well, yep) 17:49:33 freerunner: isn't WSGI for http apps? murano-engine doesn't even listen on any port 17:50:21 freerunner: worker count in config is written in spec. 17:54:35 stan_lagun: Khm. Will check it. 17:54:35 i have used puppet, ansible. but not supervisor. ok, i must try to manage workers by those tool. 17:56:13 ok 17:56:24 so, is this all for today, guys? 17:56:31 thanks. 17:58:39 hidekazu_: I recommend you to write a letter with your questions to openstack-dev with [murano] tag in topic. 17:59:16 freerunner, thank you for advise. 17:59:30 hidekazu_: Thank you for your spec ;) 18:00:07 now 3 am at tokyo, bye. 18:00:18 #endmeeting