14:00:27 #startmeeting sahara 14:00:28 Meeting started Thu Jan 12 14:00:27 2017 UTC and is due to finish in 60 minutes. The chair is vgridnev. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:32 The meeting name has been set to 'sahara' 14:00:36 O/ 14:00:41 o/ 14:00:42 hi everyone 14:00:44 o/ 14:00:50 Hi o/ 14:01:11 o/ 14:01:26 hi 14:03:11 #topic News / updates 14:04:09 o/ 14:04:47 Not so much from me, I'm back from log weekends, and busy with some internal stuff around sahara 14:04:52 updated docs for sahara tempest, continue working on my cli test patch and on ispublic/isprocted patch 14:04:57 usual set of reviews, and not too much on my side in the last weeks (also, vacations!), struggling on internal stuff 14:04:58 I'm still struggling with integration of storm on vanilla plugin, might not be interesting for this cycle anymore. Still interesting and I want to do it, but I'm not the time will suit 14:05:30 recently more concentrate on understanding sahara code and draw some time_sequence of cluster_create related. For upstream, the cdh5.9 support already done and looking for what to do next 14:05:31 added some missing tests to sahara-tests, some internal work also 14:06:19 About release schedule, we have less than 2 weeks until O3 is released 14:06:42 Also, I hope to have Shaifali start sending some patches on API v2 changes in a couple weeks 14:06:54 yay cdh 5.9 14:07:05 and vgridnev is doing a nice job on HDP 2.5 14:07:25 (apart from fixing the access-through-proxy with centos) 14:09:48 Yep, we did cdh 5.9 and HDP 2.5, we need to enable test jobs for that, I'll talks with esikachev about that (he is PTO until end of this week) 14:10:04 Anything else? 14:10:20 and I have invited an intern to work for sahara right now, who called linjiasen. If you all have some job need to do in ocata, we can help you 14:11:28 that is awesome shuyingya, api v2 might be a good thing to work on 14:11:31 Uh, additionally I did announcement that I'm not going to run for Pike as PTL, so I would like to let someone else to run this role in P 14:11:52 tellesnobrega, agreed 14:12:07 I did, indeed 14:12:28 yep, I would like to work on it. 14:12:46 maybe jiasen can help me too if I have internal stuff 14:13:09 shuyingya, you are talking API v2, right? 14:13:16 yes 14:13:31 sure, I can give you a hand with that as well 14:15:47 #link https://etherpad.openstack.org/p/sahara-ptg-pike 14:16:04 tellesnobrega, thanks. 14:16:09 np 14:16:11 Let's start etherpad for Pike's PTG 14:16:26 We can start collecting ideas to this 14:16:52 I'd like to officially thanks vgridnev for all the heavy work he did in his role as PTL! 14:17:13 vgridnev, thanks! 14:17:21 thanks vgridnev! 14:17:42 vgridnev: thanks :) 14:18:16 vgridnev, thanks for the hard work, we all really appreciate 14:18:18 Thanks all, I really appreciate that 14:18:24 :) 14:18:46 o/ 14:20:16 About the pike planning: important part is that we need to work on support of python35 for sahara 14:20:29 #link https://review.openstack.org/#/c/349069/ 14:20:47 vgridnev, yes, I saw an email about that, seems like a really important thing now 14:21:33 #topic Open discussion 14:22:10 Hi all, can we mount an existed volume when cluster creating? I am not familiar with heat. I read the sahara code, looks like it doesn't support. 14:22:35 yep, python35++ 14:22:59 uhm, yeah, so far we test with the creation of new volumes; not sure how complicated it would be to mount an existing volume 14:23:44 then you would probably need a specific node group template only for that node (unless you define some kind of pattern, like "mount volume named 'volume'" or so 14:25:08 Seems like strange thing for me, and yes, there is no support for that now 14:25:28 shuyingya, what is the use case for that? 14:26:45 Yeah, that will be interesting to see use case for that 14:27:24 my colleague tell me our custom would like to creating a cluster and use the data already existed in other volume. 14:28:46 the problem is that this data has to be imported to hdfs at least, I think 14:29:39 even if you would mount this volume to the cluster, you will need to import that into filesystem 14:29:42 it can be interesting, but I agree with vitaly, the data would need to be imported to hdfs 14:30:05 shuyingya, wouldn't it be better to use swift? 14:30:16 or is there a problem with swift? 14:31:50 (or manila) 14:32:08 tosky, true 14:33:15 network broken for a while. this question I also need take more investigation. 14:34:17 shuyingya, it would be interesting to know if the options satisfy the use case, if not you can explain why not and we can work on that 14:35:14 Is there something else we can discuss? 14:35:44 not from my side 14:36:15 tellesnobrega, OK, we can talk about it next time 14:39:39 sorry, was disconnected from bouncer 14:39:59 If there is nothing else we can discuss, let's finish meeting for today 14:40:06 Thanks everyone 14:40:09 #endmeeting