09:00:10 #startmeeting freezer 09:00:11 Meeting started Tue Nov 26 09:00:10 2019 UTC and is due to finish in 60 minutes. The chair is gengchc. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:14 The meeting name has been set to 'freezer' 09:00:30 hi 09:00:36 hi 09:00:46 Please look at today's agenda https://etherpad.openstack.org/p/freezer_meetings 09:01:06 Let's start the first topic 09:01:28 #topic Scheduler client-registration - No documentation 09:02:08 Yeah, I've tried quite of times. to register scheduler client but no luck, 09:02:31 digging in the code didn't helped to full successful registration 09:03:30 any clue of json format for registration? 09:05:41 Is the scheduler.conf configured incorrectly? With the correct configuration of the file, the start scheduler can be registered correctly. 09:06:54 You can send your conf file later. Let me have a look. 09:07:36 Could you describe the configure about freezer api and scheduler? 09:08:08 Yeah, I will send, scheduler.conf only has "client_id" and "jobs_dir" assigned 09:08:54 We use the freezer , It can work well. 09:09:09 freezer-api on one machine (standalone) configured and scheduler on another VM 09:09:47 Yeah it should work it's more about clarity of how to configure and documentation 09:11:04 do you have example json for registering cllient? 09:11:11 in scheduler 09:12:13 ok. I send the configure to you later by email. Let's start the next topic. 09:13:12 #topic Will submit patch for NOVA engine backup "--timeout" not taking value 09:14:26 What does it mean? Can you describe it more deatail? 09:14:37 This one I've got bitten by timeout option which the default value is 10 min (I guess), but instance backup and uploading taking more that 10 min 09:14:48 so backup was getting broken 09:15:16 I hardcoded the value in "/usr/lib/python2.7/site-packages/freezer/engine/nova/nova.py" 09:15:28 line "272" 09:16:01 so I used timeout option and the value didn't apply 09:16:14 only way was to hardcode it 09:16:18 to make it work 09:17:52 Please see : 09:17:55 "job_actions": [ 09:17:57 "cce17ccb-0a0e-4159-bfc2-190a5019ada8", 09:18:01 3600 09:18:02 timeout 09:18:30 You can set timeout config to longer. 09:19:00 but I'm not using job action, this happens when I use freezer-agent 09:19:15 by command line 09:21:10 utils.wait_for( 09:21:54 We modify it to conf.timeout . 09:22:40 so value of --timeout will get to "utils.wait_for", right? 09:23:38 Yes. We can improve it. Let's start the third topic? 09:24:19 It's not improving, it's only using default and doesn't let the backup finishes 09:24:41 I can send you later the full debug 09:25:43 yes start the next topic 09:25:45 yes , there is problem , we will patch it 09:27:43 #topic Cinder engine? making folder schema 09:28:30 It's just a suggesstion, which if you look Glance & Nova have engine & mode so directory structure is very human readable 09:28:50 but cinder only creates folder structure if volume ID as 09:29:25 for example "9178ed74-0758-48cc-a077-8d6a630034ee" and all data and metadata go under sub-directory 09:29:56 only UUID is uniuqe 09:30:19 cinder volume name is not unique 09:30:59 we can modify it to name-UUID 09:31:25 Yeah, having it as name-UUID will be great 09:31:41 is there any reason that cinder has no "engine"? 09:31:42 Let's start the next topic. 09:34:19 Sure 09:35:23 #topic Docs improvement 09:36:04 At the moment as I'm still reading the code, not much of help to contribute code, but really would like to contribute to documentation 09:36:27 which recently I saw another center is interested in freezer but no documentation to get it installed 09:36:29 We can modify the documents ,if we find any errors. 09:37:22 Where is the link for documentation source? so I can contribute 09:38:24 The freezer document is not perfect. We need to spend a lot of energy to improve it. If you feel that there is a problem in any place, you can submit the patch directly 09:39:19 That's the link for Train https://opendev.org/openstack/freezer/src/branch/stable/train/doc, right? 09:39:23 After meeting, I send the information about the document by email. 09:40:21 https://opendev.org/openstack/freezer/src/branch/master/doc 09:40:56 Let's the next topic? 09:41:00 OK, we can start next topic 09:41:04 #topic Notification mechanism? 09:41:26 Can you describe it detail? 09:41:31 Is there any mechanism that send an email or so when backup finishes? 09:42:13 would be great to have something like "--notification-email" and put email so after backup finishes send email 09:42:18 At present, There is not this Notification mechanism. 09:44:16 If the backup finishes, The job's state will change in freezer'api. You can query the job's status by the command freezer job list or freezer job-get *** 09:45:16 Let's start the last topic? 09:45:24 Yes right, but I would get that when get scheduler client register, so we can follow up of the complete deployment offline 09:45:49 Yep 09:45:52 #topic BareOS storage type 09:46:09 What does it mean? 09:46:36 Currently OpenStack getting backup in one machine which has bug cache disk size 09:47:04 and when backup finishes I start BareOS agent to backup 09:47:19 because we store backup in tape library 09:47:25 let me send you a link 09:47:57 https://www.bareos.com/en/what_is_bareos.html 09:48:16 OK , after we read the link , we will discuess later 09:48:26 Let's end the meeting. Thanks. 09:48:35 #endmeeting