14:02:31 #startmeeting freezer 14:02:32 Meeting started Thu Jun 1 14:02:31 2017 UTC and is due to finish in 60 minutes. The chair is szaher. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:33 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:02:35 The meeting name has been set to 'freezer' 14:02:43 Hello everyone 14:02:50 hi 14:03:02 Please find the meeting agenda here https://etherpad.openstack.org/p/freezer_meetings 14:03:18 Let's wait 5 minutes for people to join :) 14:03:21 jiaopengju: hi 14:03:50 hi guys :) 14:04:47 vnogin: Hey Vitaliy 14:05:03 szaher: hi Saad :) 14:05:41 szaher: I've added to etherpad question regarding our goals :) 14:05:48 nice :) 14:06:10 Ok, I hope we can address this one today :) 14:11:43 Ok, Let's start 14:11:47 ? 14:12:03 + 14:12:07 + 14:12:54 #topic Pike uwsgi goal 14:13:21 + 14:13:53 we partially aligned with this goal, so I'll be working on it next just to make sure we finished all Pike goals, then I'll update the governance 14:14:12 If anyone wants to help that would be great 14:15:12 anyway, I will keep you posted of the progress of these goals 14:15:34 anyone wants to comment ? 14:15:36 Move on ? 14:15:55 I think it's partially related to the second issue :) 14:16:02 #topic Decide which blueprints or specs we want to address in the next release cycles 14:16:08 There is non-zero possibility that we can invest more time and efforts to freezer in near future and we need to decide what exactly needs to be done or improved. Guys, can we try to summarize the most required features now? 14:16:31 ok 14:16:58 vnogin: I think that will be really good to agree on now so we can have a long term plane on what needs to be done and we work on it. 14:17:26 ofcouse there will be some urgent goals/needs which we can work on it as long as it's not causing any problems to the original plan 14:18:13 but let's list all features that we want to see it in freezer in the near future first 14:18:45 szaher: yep, that's exactly what I mean 14:18:50 I can provide ansible roles/playbooks for freezer deployment if that is needed 14:18:50 vnogin: We can discuss the long term goals here and then can make an etherpad to write then down 14:19:02 szaher: cool 14:19:04 haad1: That would be nice 14:19:12 to integrate it with opestack-ansible-freezer 14:19:29 vnogin: I think the etherpad with +1 and -1 would be easier to know who wants to have what when ;) 14:19:51 haad1: awesome. We are going to start activity in OSA 14:20:28 haad1: I'm working on a commit which will land in couple of hours, hopefully less to open two repos for freezer-ansible (ansible-role-os_freezer, ansible-role-os_freezer-api) 14:20:46 haad1: where are you based ? 14:20:51 https://blueprints.launchpad.net/freezer/ do we have everything that we need here? 14:21:02 or maybe we forgot something? 14:21:03 Slovakia 14:21:08 vnogin: nope 14:21:10 that's GMT+! 14:21:19 CET 14:21:19 haad1: nice :) like Ireland that nice 14:21:26 yeah 14:23:00 vnogin: the launchpad is outdated, I working slowly on cleaning it so we can have what we really need and may some ideas that we want to discuss later in the launchpad 14:23:38 szaher: I have 3 roles (agent, api, ui) 14:24:10 haad1: Make sense so I need to include the UI as well :) 14:25:11 Would you like to see them 14:25:18 szaher: ceph, api-v2, mysql migration (oslo), ansible roles, multi-DC DR - it seems very required features 14:25:34 szaher: and DOCS!!!! :))) 14:25:39 they do not have proper OSA structure but might be useful for you 14:25:47 yeah docs would be great :) 14:26:16 vnogin: +11111111111 14:26:20 haad1: frankly I think it's good idea to use OSA structure because it's really awesome :) 14:26:25 vnogin: ceph do you mean s3 support? 14:26:27 haad1: that's cool 14:26:34 vnogin: +1 on all of that 14:26:56 jiaopengju: i mean everything related to ceph support (s3 as well) 14:27:11 vnogin: I have soem troubles with it but it works so I'm not complaining 14:27:13 vnogin: get it, thanks 14:27:39 haad1: no-no :) it's really cool :) and I want to review your roles if possible ))) 14:28:44 so if don't have BP or specs for the above mentioned features we need to create them 14:29:15 I've created for ansible, and as far as I remember Dima S. created for oslo 14:29:43 szaher: also there is DR spec in merge conflict 14:29:52 vnogin: :D 14:30:00 https://etherpad.openstack.org/p/BOS-Freezer-brainstorming take a look at this one 14:30:03 szaher: and -1 from my side :)) LOL))) 14:30:16 the brainstorming that we did for boston summit 14:30:39 yep, I remember it 14:32:48 ok, where we are going to collect all info and set -+1 14:33:47 well, what about #link https://etherpad.openstack.org/p/freezer-roadmap 14:37:08 Guys please take a look at it https://etherpad.openstack.org/p/freezer-roadmap and list all features that you think it will help freezer 14:38:42 jiaopengju: I think the discussion also included the s3 driver support, right ? 14:38:51 szaher: yes 14:39:05 Cool! 14:39:26 haad1: What's your availability to contribute to freezer ? 14:39:36 haad1: I mean the ansible part 14:39:56 we are going to have it in production so I'm willing to help 14:39:56 and ofcourse any other part if you want to :) 14:40:06 and contribute 14:40:26 haad1: That's great, are you using it in private cloud or public ? 14:41:09 semi public 14:41:26 haad1: :) OK 14:41:54 haad1: do you DR as well or only backup/restore? 14:42:07 For now only backup/restore 14:42:09 haad1: Could you post your usecase to OpenStack ? 14:42:21 haad1: which release ? 14:42:27 Ocata 14:43:15 szaher: I found the design status of bp(s3-driver-support) is 'Discussion'. And I have wroted a specs documentation about it. Should I start the function realization? 14:43:47 jiaopengju: where is spec now? 14:43:48 For us freezer is part of added value for our users they can backup their vms/data etc with it on our cloud 14:44:01 and do not need to setup their own solution 14:44:11 haad1: storage backend? 14:44:24 swift for us 14:44:32 vnogin: https://review.openstack.org/#/c/469791/2 14:44:33 haad1: cool, thanks 14:44:46 but customer can chose any other for their own backends 14:44:49 jiaopengju: gonna update it :) 14:44:58 jiaopengju: I'll review it later, tnx 14:45:11 thanks 14:45:15 jiaopengju: I mean the blueprint not the specs :) 14:45:26 jiaopengju: -1 from jenkins :) 14:45:29 szaher: but we have one use case where we would like to use isilon provided swift storage 14:45:42 but that doesn't support swift api > 1 14:46:01 so it might require it's own storage backend 14:47:11 haad1: hmmm, Can you explain more about it ? 14:47:19 vnogin: I will update it later 14:48:51 jiaopengju: cool, tnx 14:52:49 Guys, we are running out of time, anyone wants to add anything before we close the meeting ? 14:53:41 please add BP or scep link to the doc 14:53:51 https://etherpad.openstack.org/p/freezer-roadmap 14:54:07 so isilion is a emc based storage array which supports swift v1 api to store files on it 14:54:10 scep=spec 14:54:32 vnogin: for every feature you mean ? 14:54:45 szaher: yep, if we have them 14:54:49 you can configure it in a way that then you can use swift api to upload files it to it 14:55:36 vnogin: Cool! 14:55:48 but it's not part of openstack instalation there for it doesn't have keystone and it only supports swift v1 api 14:56:02 haad1: Nice :), there is not other way to implement a driver directly for your storage ? 14:56:33 szaher: what do you mean by other way 14:56:48 haad1: have a dedicated driver for this storage 14:57:22 we are running out of time guys :(, let 14:57:39 let's continue the discussion in freezer room, OK ? 14:57:50 + 14:58:19 Ok, Thanks everyone :) 14:58:43 thanks guys for yout time 14:58:52 please review roadmap :)) 14:59:23 Ok... 14:59:31 #endmeeting