Wednesday, 2017-01-18

*** zhurong has joined #openstack-karbor00:56
*** zhurong has quit IRC00:56
*** zhurong has joined #openstack-karbor00:56
*** lihi has quit IRC01:27
*** lihi has joined #openstack-karbor01:29
*** diablo_rojo has joined #openstack-karbor01:46
*** diablo_rojo has quit IRC01:48
openstackgerritchenying proposed openstack/karbor: Update the nova backup protection plugin  https://review.openstack.org/41787301:50
*** zhurong has quit IRC03:00
*** zhurong has joined #openstack-karbor03:02
*** tommylikehu has joined #openstack-karbor03:11
openstackgerritwu proposed openstack/python-karborclient: Make command 'karbor provider-show' print pretty  https://review.openstack.org/42123903:12
*** zhurong has quit IRC03:23
openstackgerritMerged openstack/karbor: Remove logging import unused  https://review.openstack.org/42046203:28
*** gouthamr has quit IRC03:28
*** tommylikehu1 has joined #openstack-karbor03:33
*** tommylikehu has quit IRC03:36
*** tommylikehu1 is now known as tommylikehu03:36
openstackgerritOpenStack Proposal Bot proposed openstack/karbor: Updated from global requirements  https://review.openstack.org/41596404:39
chenying_ping saggi07:07
chenying_ping yuvalb07:12
*** yuval has joined #openstack-karbor07:29
yuvalhey chenying_07:29
*** zhurong has joined #openstack-karbor07:37
chenying_yuval Hi As you know, now the nova plugin has backup three images (snapshot image, kernel image, ramdisk image). Are kernel and ramdisk image a must? Can we consider only backuping the snapshot image of the server?07:42
yuvalchenying_: 1) I still didn't understand why nova protection plugin takes a snapshot of the image and backs it up. The image protection is the glance protection plugin's job07:44
yuvalchenying_: 2) kernel and ramdisk are only part of specific image types07:44
yuvalchenying_: regarding image types: http://docs.openstack.org/developer/glance/formats.html07:45
*** zhurong has quit IRC07:46
chenying_yuval 1) This nova plguin refer to the implementment of IBM dragon's soltuion at first.  We can consider developing a new nova plguin using other solution(like nova backup).08:06
yuvalchenying_: do you mean a new plugin in addition to this one?08:09
yuvalchenying_: Can't understand how IBM Dragon relates to that08:10
chenying_yuval  do you mean a new plugin in addition to this one? Yes  IBM Dragon is another backup as a serice project. Some concept and module of karbor come from it.08:12
yuvalchenying_: afaik ibm dragon was a backup as a service project which was never complete. However, this is changes nothing in karbor. The basic nova protection plugin in karbor should be correct08:13
*** yamamoto has quit IRC08:17
chenying_yuval: So what's your opinion about the correct solution of nova plugin. Do you have a plan about developing this plugin?08:22
yuvalchenying_: as I said before, the current implmentation of nova protection plugin creates a snapshot of the server image, which is not what we mean. First, the server may boot from a volume and not an image, second, we already protect the image in the glance protection plugin08:24
chenying_yuval, The server may boot from a volume. -- This is another situation about server. If the server boot from a image, What's the problem with current nova plugins? we also need create a snapshot image about the server.08:42
yuvalchenying_: image is immutable, already protected by glance protection plugin, and any changes are ephemeral08:48
yuvalchenying_: is there a reason to take a snapshot and not use the actual server image protected by glance?08:48
yuvalchenying_: what if you have 30 servers, all boot from the same image? then each checkpoint has 30 image snapshots?08:52
chenying_yuval:  take a snapshot of server to generate a image, this is one step of current nova plugin. It is too late for glance plugins to protect.08:53
yuvalchenying_: I know that it is a step of the current nova plugin, and I think it shouldn't be08:54
yuvalchenying_: what do you mean by 'too late'?08:54
chenying_ what if you have 30 servers, all boot from the same image? then each checkpoint has 30 image snapshots? ------The snapshot image of all 30 servers are different. I don't think the snapshots image is same as the original image.08:56
yuvalchenying_: karbor should not protect ephemeral data of servers08:57
chenying_30 servers, all boot from the same image ---- They just are created with same  original image. It doesn't mean the snapshot are same.08:57
yuvalchenying_: the diff between the base image and the current state is ephemeral and we should not protect it08:57
yuvalif someone wants persistent storate they can use a volume, not an image08:58
yuval*storage08:58
chenying_yuval: What's your mean about ephemeral data? the snapshot image of server?08:58
yuvalchenying_: http://docs.openstack.org/ops-guide/arch-storage.html08:59
yuvalimages are immutable. data written by servers is written either on a volume, or an ephemeral storage09:00
chenying_yuval: I see. If user want to persistence and protect the syetem data of server, the server must boot form a volume not from image.09:06
yuvalchenying_: it can boot from image, but store data on another attached volume09:06
*** yamamoto has joined #openstack-karbor09:07
yuvalchenying_: for example, boot from an ubuntu image, and mount a persistent volume to /var for storing crucial application data09:10
openstackgerritMerged openstack/python-karborclient: Make command 'karbor provider-show' print pretty  https://review.openstack.org/42123909:13
chenying_yuval: boot from an ubuntu image -- If user want to protect all the syestem data (/etc /lib /boot) of the server, how to deal with it.09:13
yuvalchenying_: if this data is in the original image - it is backed up by the glance protection plugin. if the user made changes after the server booted - the changes are epehemeral, they will not be protected by karbor, and they will also be lost on reboot09:14
chenying_yuval: This situation the user need boot from a volume, if he want to portect all the syestem data.09:17
yuvalchenying_: let's say karbor is not part of the game. if the user boots from an image, then all ephemeral changes are lost when the server is shutdown09:19
yuvalchenying_: so if a user wants /etc /lib, ... to survive boot - they should be part of the immutable image or some persistent storage - i.e volume09:20
yuvalchenying_: karbor will not be protecting server ephemeral data09:21
chenying_yuval: I see. If ther server boot from a image, Does it mean that we only need protect all the attached volume of this server.09:22
yuvalglance protection plugin will protect the image, cinder protection plugin will protect the volumes, server protection plugin will protect the server configuration and the 'attachment' to the server's image and/or volumes09:23
yuvalon restore, glance protection plugin will restore the image, cinder protection plugin will restore the volume, nova protection plugin will restore the server, and boot it from the image/volume it is supposed to boot from, and attach volumes, if any, that should be attached09:24
chenying_Yes09:26
chenying_you mean that the backup of server image  is just a use case of glance protection? we don't need take the snapshot image of server in ther nova plugins?09:27
yuvalchenying_: yep09:27
yuvalchenying_: I have to go, let's continue this later/tomorrow09:29
chenying_yuval: Ok. I see. I will think carefully about it.09:30
chenying_yuval: thanks.09:30
yuvalchenying_: :)))09:30
*** yuval has quit IRC09:31
*** yamamoto has quit IRC09:34
*** yamamoto has joined #openstack-karbor09:36
*** yamamoto has quit IRC09:39
openstackgerritzhangshuai proposed openstack/karbor-dashboard: Fix provider show checkpoints page  https://review.openstack.org/42177610:01
openstackgerritchenying proposed openstack/karbor: Update the nova backup protection plugin  https://review.openstack.org/41787310:03
*** yamamoto has joined #openstack-karbor10:55
*** yamamoto has quit IRC11:10
*** yinwei_computer has quit IRC12:49
*** yinwei_computer has joined #openstack-karbor12:51
*** zhurong has joined #openstack-karbor12:53
*** zhurong has quit IRC13:11
*** zhurong has joined #openstack-karbor13:12
*** zhurong has quit IRC13:13
*** tommylikehu_ has joined #openstack-karbor13:21
*** tommylikehu_ has quit IRC13:22
*** tommylikehu_ has joined #openstack-karbor13:22
*** zhurong has joined #openstack-karbor13:32
*** tommylik_ has joined #openstack-karbor13:33
*** tommylikehu_ has quit IRC13:34
*** tommylik_ has quit IRC13:35
*** tommylikehu_ has joined #openstack-karbor13:35
*** yinwei_computer has quit IRC13:42
*** yinwei_computer has joined #openstack-karbor13:44
*** gouthamr has joined #openstack-karbor14:13
*** openstack has joined #openstack-karbor15:20
*** tommylikehu_ has quit IRC15:39
*** Jeffrey4l has quit IRC16:01
*** Jeffrey4l_ has joined #openstack-karbor16:01
*** Jeffrey4l_ is now known as Jeffrey4l16:02
*** gouthamr has quit IRC21:34
*** Jeffrey4l has quit IRC21:35
*** Jeffrey4l has joined #openstack-karbor21:35
*** gouthamr has joined #openstack-karbor21:57
*** tommylikehu_ has joined #openstack-karbor22:59
*** tommylikehu_ has quit IRC23:02
*** Jeffrey4l has quit IRC23:24
*** lihi has quit IRC23:24
*** Jeffrey4l has joined #openstack-karbor23:24
*** lihi has joined #openstack-karbor23:24
*** Jeffrey4l has quit IRC23:29
*** Jeffrey4l has joined #openstack-karbor23:41
*** Jeffrey4l has quit IRC23:42
*** Jeffrey4l has joined #openstack-karbor23:42

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!