*** goldyfruit_ has quit IRC | 00:20 | |
*** goldyfruit_ has joined #openstack-freezer | 01:05 | |
*** gengchc has joined #openstack-freezer | 08:45 | |
*** gecong has joined #openstack-freezer | 08:45 | |
*** akotobi has joined #openstack-freezer | 08:53 | |
gengchc | Hello Guys | 08:55 |
---|---|---|
gecong | hi | 08:55 |
gengchc | ping akotobi | 08:56 |
gengchc | #startmeeting freezer | 09:00 |
openstack | 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 09:00 |
*** openstack changes topic to " (Meeting topic: freezer)" | 09:00 | |
openstack | The meeting name has been set to 'freezer' | 09:00 |
akotobi | hi | 09:00 |
gecong | hi | 09:00 |
gengchc | Please look at today's agenda https://etherpad.openstack.org/p/freezer_meetings | 09:00 |
gengchc | Let's start the first topic | 09:01 |
gengchc | #topic Scheduler client-registration - No documentation | 09:01 |
*** openstack changes topic to "Scheduler client-registration - No documentation (Meeting topic: freezer)" | 09:01 | |
akotobi | Yeah, I've tried quite of times. to register scheduler client but no luck, | 09:02 |
akotobi | digging in the code didn't helped to full successful registration | 09:02 |
akotobi | any clue of json format for registration? | 09:03 |
gengchc | Is the scheduler.conf configured incorrectly? With the correct configuration of the file, the start scheduler can be registered correctly. | 09:05 |
gengchc | You can send your conf file later. Let me have a look. | 09:06 |
gengchc | Could you describe the configure about freezer api and scheduler? | 09:07 |
akotobi | Yeah, I will send, scheduler.conf only has "client_id" and "jobs_dir" assigned | 09:08 |
gengchc | We use the freezer , It can work well. | 09:08 |
akotobi | freezer-api on one machine (standalone) configured and scheduler on another VM | 09:09 |
akotobi | Yeah it should work it's more about clarity of how to configure and documentation | 09:09 |
akotobi | do you have example json for registering cllient? | 09:11 |
akotobi | in scheduler | 09:11 |
gengchc | ok. I send the configure to you later by email. Let's start the next topic. | 09:12 |
gengchc | #topic Will submit patch for NOVA engine backup "--timeout" not taking value | 09:13 |
*** openstack changes topic to "Will submit patch for NOVA engine backup "--timeout" not taking value (Meeting topic: freezer)" | 09:13 | |
gengchc | What does it mean? Can you describe it more deatail? | 09:14 |
akotobi | 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 |
akotobi | so backup was getting broken | 09:14 |
akotobi | I hardcoded the value in "/usr/lib/python2.7/site-packages/freezer/engine/nova/nova.py" | 09:15 |
akotobi | line "272" | 09:15 |
akotobi | so I used timeout option and the value didn't apply | 09:16 |
akotobi | only way was to hardcode it | 09:16 |
akotobi | to make it work | 09:16 |
gengchc | Please see : | 09:17 |
gengchc | "job_actions": [ | 09:17 |
gengchc | "cce17ccb-0a0e-4159-bfc2-190a5019ada8", | 09:17 |
gengchc | 3600 | 09:18 |
gengchc | timeout | 09:18 |
gengchc | You can set timeout config to longer. | 09:18 |
akotobi | but I'm not using job action, this happens when I use freezer-agent | 09:19 |
akotobi | by command line | 09:19 |
gengchc | utils.wait_for( | 09:21 |
gengchc | We modify it to conf.timeout . | 09:21 |
akotobi | so value of --timeout will get to "utils.wait_for", right? | 09:22 |
gengchc | Yes. We can improve it. Let's start the third topic? | 09:23 |
akotobi | It's not improving, it's only using default and doesn't let the backup finishes | 09:24 |
akotobi | I can send you later the full debug | 09:24 |
akotobi | yes start the next topic | 09:25 |
gecong | yes , there is problem , we will patch it | 09:25 |
gengchc | #topic Cinder engine? making folder schema | 09:27 |
*** openstack changes topic to "Cinder engine? making folder schema (Meeting topic: freezer)" | 09:27 | |
akotobi | It's just a suggesstion, which if you look Glance & Nova have engine & mode so directory structure is very human readable | 09:28 |
akotobi | but cinder only creates folder structure if volume ID as | 09:28 |
akotobi | for example "9178ed74-0758-48cc-a077-8d6a630034ee" and all data and metadata go under sub-directory | 09:29 |
gecong | only UUID is uniuqe | 09:29 |
gecong | cinder volume name is not unique | 09:30 |
gecong | we can modify it to name-UUID | 09:30 |
akotobi | Yeah, having it as name-UUID will be great | 09:31 |
akotobi | is there any reason that cinder has no "engine"? | 09:31 |
gengchc | Let's start the next topic. | 09:31 |
akotobi | Sure | 09:34 |
gengchc | #topic Docs improvement | 09:35 |
*** openstack changes topic to "Docs improvement (Meeting topic: freezer)" | 09:35 | |
akotobi | 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 |
akotobi | which recently I saw another center is interested in freezer but no documentation to get it installed | 09:36 |
gengchc | We can modify the documents ,if we find any errors. | 09:36 |
akotobi | Where is the link for documentation source? so I can contribute | 09:37 |
gengchc | 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:38 |
akotobi | That's the link for Train https://opendev.org/openstack/freezer/src/branch/stable/train/doc, right? | 09:39 |
gengchc | After meeting, I send the information about the document by email. | 09:39 |
gengchc | https://opendev.org/openstack/freezer/src/branch/master/doc | 09:40 |
gengchc | Let's the next topic? | 09:40 |
akotobi | OK, we can start next topic | 09:41 |
gengchc | #topic Notification mechanism? | 09:41 |
*** openstack changes topic to "Notification mechanism? (Meeting topic: freezer)" | 09:41 | |
gengchc | Can you describe it detail? | 09:41 |
akotobi | Is there any mechanism that send an email or so when backup finishes? | 09:41 |
akotobi | would be great to have something like "--notification-email" and put email so after backup finishes send email | 09:42 |
gengchc | At present, There is not this Notification mechanism. | 09:42 |
gengchc | 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:44 |
gengchc | Let's start the last topic? | 09:45 |
akotobi | Yes right, but I would get that when get scheduler client register, so we can follow up of the complete deployment offline | 09:45 |
akotobi | Yep | 09:45 |
gengchc | #topic BareOS storage type | 09:45 |
*** openstack changes topic to "BareOS storage type (Meeting topic: freezer)" | 09:45 | |
gengchc | What does it mean? | 09:46 |
akotobi | Currently OpenStack getting backup in one machine which has bug cache disk size | 09:46 |
akotobi | and when backup finishes I start BareOS agent to backup | 09:47 |
akotobi | because we store backup in tape library | 09:47 |
akotobi | let me send you a link | 09:47 |
akotobi | https://www.bareos.com/en/what_is_bareos.html | 09:47 |
gecong | OK , after we read the link , we will discuess later | 09:48 |
gengchc | Let's end the meeting. Thanks. | 09:48 |
gengchc | #endmeeting | 09:48 |
*** openstack changes topic to "Freezer is a Python tool that helps you to automate the data backup and restore process. https://launchpad.net/freezer - IRC weekly meeting on #openstack-freezer recurring every Thursday start 4:00 PM - end 5:00 PM GMT - Meetings notes available at: https://etherpad.openstack.org/p/freezer_meetings - Current code reviewers: reldan, samuelBartel" | 09:48 | |
openstack | Meeting ended Tue Nov 26 09:48:35 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:48 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/freezer/2019/freezer.2019-11-26-09.00.html | 09:48 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/freezer/2019/freezer.2019-11-26-09.00.txt | 09:48 |
openstack | Log: http://eavesdrop.openstack.org/meetings/freezer/2019/freezer.2019-11-26-09.00.log.html | 09:48 |
*** gecong has quit IRC | 09:58 | |
*** electrofelix has joined #openstack-freezer | 10:09 | |
*** akotobi has quit IRC | 10:26 | |
*** ivve has joined #openstack-freezer | 10:35 | |
*** electrofelix has quit IRC | 11:43 | |
*** electrofelix has joined #openstack-freezer | 11:43 | |
*** akotobi has joined #openstack-freezer | 11:49 | |
*** akotobi has left #openstack-freezer | 11:52 | |
*** gengchc has quit IRC | 12:44 | |
*** goldyfruit_ has quit IRC | 13:08 | |
*** goldyfruit has joined #openstack-freezer | 14:36 | |
*** goldyfruit_ has joined #openstack-freezer | 14:38 | |
*** goldyfruit has quit IRC | 14:41 | |
*** ivve has quit IRC | 16:02 | |
*** ivve has joined #openstack-freezer | 17:06 | |
*** openstackgerrit has quit IRC | 17:49 | |
*** goldyfruit___ has joined #openstack-freezer | 18:41 | |
*** goldyfruit_ has quit IRC | 18:43 | |
*** electrofelix has quit IRC | 18:50 | |
*** goldyfruit_ has joined #openstack-freezer | 18:51 | |
*** goldyfruit___ has quit IRC | 18:54 | |
*** goldyfruit_ has quit IRC | 19:07 | |
*** goldyfruit has joined #openstack-freezer | 19:09 | |
*** goldyfruit_ has joined #openstack-freezer | 19:19 | |
*** goldyfruit has quit IRC | 19:22 | |
*** goldyfruit___ has joined #openstack-freezer | 20:17 | |
*** goldyfruit_ has quit IRC | 20:20 | |
*** goldyfruit_ has joined #openstack-freezer | 20:21 | |
*** goldyfruit___ has quit IRC | 20:24 | |
*** threestrands has joined #openstack-freezer | 21:27 | |
*** goldyfruit___ has joined #openstack-freezer | 23:13 | |
*** goldyfruit_ has quit IRC | 23:16 | |
*** goldyfruit_ has joined #openstack-freezer | 23:17 | |
*** goldyfruit___ has quit IRC | 23:20 | |
*** goldyfruit_ has quit IRC | 23:49 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!