14:00:00 <szaher> #startmeeting freezer
14:00:04 <openstack> Meeting started Thu Jun  8 14:00:00 2017 UTC and is due to finish in 60 minutes.  The chair is szaher. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:07 <openstack> The meeting name has been set to 'freezer'
14:00:18 <slashme> Hello szaher :)
14:00:19 <szaher> Hello guys
14:00:24 <szaher> slashme: hey :)
14:01:19 <szaher> Please check the meeting agenda for today's meeting here https://etherpad.openstack.org/p/freezer_meetings
14:04:22 <vnogin> hi guys
14:04:36 <szaher> vnogin: Hi Vitaliy
14:06:11 <daemontool> hi
14:06:23 <raliev> hey guys :)
14:07:15 <szaher> Hello hello :)
14:07:21 <szaher> Good to see you guys :)
14:07:30 <szaher> https://etherpad.openstack.org/p/freezer_meetings the meeting agenda is here
14:07:38 <szaher> we will start in less than 3 minutes :)
14:10:00 <szaher> Ok, Let's start
14:10:08 <szaher> #topic Pike goals update
14:10:10 <vnogin> szaher: raliev daemontool hi guys, nice to see you )
14:10:18 <daemontool> likewise
14:11:19 <daemontool> what are the Pike goals? do they needs to be defined?
14:11:28 <daemontool> or is there anything already written down?
14:11:59 <szaher> for Pike goal python35, I updated the planned artifacts, so we have the gate job upstream that checks each and every change we do if it's compatible with py35 or not, we might need to add another gate job with some code changes but it will be very little changes hopefully :)
14:12:09 <szaher> daemontool: https://governance.openstack.org/tc/goals/pike/index.html
14:12:37 <daemontool> ok good
14:12:52 <szaher> That was my patch for the planed artifacts for python35 https://review.openstack.org/#/c/466826/
14:13:17 <daemontool> is going to get through very soon
14:13:38 <daemontool> :)
14:13:49 <daemontool> I have a question for pike
14:13:59 <daemontool> if it's not the right time shut me down
14:14:25 <daemontool> what do we do for freezer-dr on Pike
14:14:53 <daemontool> I saw there's a plan from a big openstack enterprise distro
14:14:56 <szaher> daemontool: till now, we don't have that much planed for it!
14:15:03 <daemontool> to include Freezer in their distro in Pike
14:15:15 <daemontool> we should get the requirements so we can start doing something there?
14:15:59 <szaher> daemontool: I have a blueprint in freezer-specs, Let's add this as a topic and discuss it in the meeting later, OK ?
14:16:06 <daemontool> ok thansk
14:16:31 <szaher> regarding the second goal which is deploy api using wsgi (uwsgi) with apache proxy, I did one change and I think we are compliant with it now, I submitted a change for that https://review.openstack.org/#/c/471430/
14:17:21 <szaher> so, hopefully we can move forward with the Pike goals :)
14:17:41 <szaher> #topic Pike-2 milestone
14:18:16 <szaher> I have to release Pike-2 milestone either today or tomorrow (not recommended), It's critically important to release pike-2 :)
14:18:37 <daemontool> ok
14:18:54 <szaher> Please, If there are any urgent patches, come to freezer channel and let me know so we can fix it and include it in Pike-2
14:18:54 <daemontool> is there any new feature that has been added?
14:18:59 <daemontool> ok
14:19:10 <daemontool> I can see it from the changelog anyway
14:19:48 <szaher> daemontool: for me, I've been working all this time or pike goals and fix gate jobs and maintaining bugs and things like that
14:20:10 <daemontool> ok
14:20:17 <szaher> hopefully I will try to update Cinder engine with kforde_ very soon to work like other engines
14:20:26 <daemontool> ah excellent
14:20:47 <szaher> #topic freezer ansible roles repos
14:21:46 <szaher> We need to create 3 new repos for freezer :) openstack-ansible-os_freezer, openstack-ansible-os_freezer-api, openstack-ansible-os_freezer-web-ui
14:22:29 <daemontool> szaher, why not having a single openstack-ansible-os_freezer
14:22:41 <daemontool> it's a bit of overload
14:22:49 <daemontool> having a repo for each component
14:22:53 <vnogin> agree
14:22:58 <daemontool> the ansible playbooks will not be taht much
14:23:16 <daemontool> there will be few files per component
14:23:23 <vnogin> also, I'm trying to figure out why we use separate repos for api and freezer
14:23:30 <Yangyapeng> indeed
14:24:17 <szaher> the change is landed here https://review.openstack.org/#/c/469938/, it needs more work to be create as we need to get some ansible in it to pass the tests first :)
14:24:21 <szaher> daemontool: +1
14:24:28 <daemontool> ok
14:24:35 <szaher> I will change the patch
14:24:38 <daemontool> also if we have the same for puppet
14:24:48 <szaher> we have puppet-freezer and that's it
14:24:50 <daemontool> then we are going to have 3 new repos
14:24:56 <daemontool> ah ok
14:24:58 <daemontool> :P
14:25:02 <szaher> I think, I will create 2 roles for freezer ansible (freezer, freezer-ui)
14:25:08 <daemontool> good
14:25:32 <szaher> i won't be under our control, it goes under ansible guys :)
14:25:41 <daemontool> ok
14:26:14 <szaher> ah, I have an explanation guys for why freezer and freezer-api roles,
14:26:24 <szaher> some hosts needs only freezer and other hosts needs api
14:26:39 <szaher> the api will be on the control plane only and freezer will be on different nodes !
14:27:30 <szaher> or we add the different roles inside os_freezer role ?
14:27:55 <slashme> How about one freezer-ansible repo containing one role per component (python-freezerclien, ui, api, scheduler, agent)
14:27:55 <vnogin> I think we can use tags there
14:28:09 <slashme> vnogin: yup, tag or role
14:28:22 <szaher> Ok, Good :)
14:28:24 <daemontool> yes
14:28:35 <vnogin> for instance https://github.com/openstack/openstack-ansible-os_nova
14:28:52 <vnogin> everything done using one role
14:29:01 <szaher> vnogin: Ok Cool!
14:29:08 <vnogin> controll and user planes
14:29:17 <vnogin> user=data
14:29:33 <szaher> Ok
14:29:54 <szaher> anything else to be added about ansible repos ?
14:30:12 <vnogin> nope
14:30:32 <szaher> :) OK Let's move then
14:30:35 <szaher> #topic heat integration
14:31:10 <szaher> This patch has been here since ages  https://review.openstack.org/#/c/443426/ are we going to do some actual work on it or what ?
14:31:15 <szaher> Yangyapeng: any updates ?
14:31:26 <szaher> did you start doing any work on it ?
14:31:27 <Yangyapeng> here
14:32:03 <Yangyapeng> sorry,
14:32:22 <daemontool> that is important
14:32:31 <daemontool> otherwise any cloudmanger cannot use freezer
14:32:32 <Yangyapeng> szaher has recently been doing a kolla-ansible on business
14:32:59 <daemontool> Yangyapeng, you are an Ansible Tower
14:33:00 <daemontool> :)
14:33:46 <vnogin> LOL)
14:34:01 <Yangyapeng> :(
14:34:29 <szaher> so what is the plan now ?
14:34:41 <szaher> Yangyapeng: will you get the time to do anything on it ?
14:34:50 <Yangyapeng> on june, I may be have to focus on kolla
14:35:28 <daemontool> is there anything else to do in the spec or it can be approved?
14:36:08 <szaher> daemontool: there is some comments, we need to ping heat guys
14:37:08 <daemontool> Rico Lin?
14:37:14 <Yangyapeng> I will again go to ping heat core member
14:37:18 <daemontool> ok
14:37:23 <Yangyapeng> daemontool yeah
14:38:02 <szaher> https://review.openstack.org/#/c/469977/ the governance patch approved
14:38:07 <szaher> sorry update
14:38:21 <daemontool> good good
14:38:33 <szaher> Ok, let's move on ?
14:38:48 <szaher> #topic do we really need pylint and pep8 gates simultaneously
14:39:03 <vnogin> https://review.openstack.org/#/c/469977/  I'll ping Andy and Chris to review it
14:39:12 <daemontool> is it redundant?
14:39:35 <vnogin> Actually I don't understand why we use both... Can someone explane me?
14:39:50 <daemontool> pylint does more than pep8
14:39:51 <szaher> I think they're different
14:40:04 <Yangyapeng> I have ping Rico to review heat Freezer Resource  again :)
14:40:04 <szaher> or at least they do different checks
14:40:05 <daemontool> I don't know if the pep8 checks are executed anyway by pylint
14:40:55 <vnogin> ok, let's gather our requirements and check that we have them in pep8 or pylint
14:42:36 <szaher> Ok, that would be great :)
14:43:34 <szaher> vnogin: that might help https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/projects.yaml or confuse :D
14:44:20 <vnogin> szaher: I'll look into it )
14:44:32 <szaher> Ok Cool!
14:44:41 <szaher> Let's move on ?
14:45:00 <vnogin> +
14:45:16 <szaher> #topic freezer-dr for Pike
14:45:52 <szaher> daemontool: we hope can implement the architecture found here https://www.slideshare.net/saad_asd49/openstack-backup-restore-dr-freezer
14:46:21 <szaher> page 25
14:46:25 <szaher> sorry 26
14:46:25 <daemontool> I'm on a call sorry :((( basically I'd like to have a support
14:46:30 <daemontool> for single VM, group of VMs
14:46:38 <daemontool> or whole compute
14:46:50 <szaher> daemontool: it does support a whole compute now :)
14:47:15 <szaher> daemontool: single/group vms needs more work :) which I would appreciate if we can discuss it together
14:47:33 <vnogin> invite me as well if possible )
14:47:43 <szaher> Let's arrange a hangout call between whoever interested and discuss it in more details
14:47:47 <vnogin> +++
14:47:54 <szaher> vnogin: for sure :)
14:48:49 <slashme> I'd like if it could have a clustering capability
14:49:13 <slashme> Freezer-dr clusters with quorum
14:49:22 <slashme> In order to remove the SPOF
14:49:24 <vnogin> and multi-DC ability
14:49:30 <szaher> that would be great as well, also kind of coordination between different instances of freezer-dr
14:49:30 <slashme> vnogin: +1
14:50:00 <szaher> Cool!, that sounds great :)
14:50:36 <szaher> I will try to schedule a meeting next week about freezer-dr so we can discuss and agree on the effort to be done
14:50:45 <vnogin> great
14:50:59 <szaher> #topic reviews
14:51:14 <szaher> This is critical today to release pike-2
14:51:32 <szaher> if I can get some help merging whatever can be merged that would be great guys
14:51:47 <szaher> I will release pike-2 in 2 hours from now :)
14:51:59 <vnogin> https://review.openstack.org/#/c/472081/ :)
14:52:09 <vnogin> https://review.openstack.org/#/c/471997/
14:53:20 <vnogin> also there are few patches related to bug fixing
14:53:53 <szaher> I will take a look now on exiting patches and what can be merged and let's merge it
14:54:01 <szaher> https://review.openstack.org/#/q/project:openstack/freezer+status:open
14:54:05 <szaher> https://review.openstack.org/#/q/project:openstack/freezer-api+status:open
14:54:11 <szaher> https://review.openstack.org/#/q/project:openstack/python-freezerclient+status:open
14:54:15 <vnogin> however I think they needs to be reviewed more attentive
14:54:24 <szaher> https://review.openstack.org/#/q/project:openstack/freezer-web-ui+status:open
14:54:50 <szaher> I think that was it for today's meeting
14:55:01 <szaher> anyone to add anything before we close ?
14:55:12 <vnogin> please review this one :) https://review.openstack.org/#/c/465867/
14:56:02 <szaher> I'm not sure about this one, you need to specify an enigne
14:57:21 <szaher> Thanks guys
14:57:22 <szaher> #endmeeting