Thursday, 2017-08-10

*** jiaopengju has joined #openstack-karbor00:30
*** yamamoto_ has quit IRC00:37
*** yamamoto has joined #openstack-karbor00:39
*** liujiong has joined #openstack-karbor00:51
*** saggi has joined #openstack-karbor01:27
openstackgerritchenying proposed openstack/karbor master: Spec: Implement policies in code  https://review.openstack.org/49214301:44
openstackgerritPengju Jiao proposed openstack/karbor master: Fix log info error  https://review.openstack.org/49234302:04
*** edisonxiang has joined #openstack-karbor02:44
*** yamamoto has quit IRC03:36
*** yamamoto has joined #openstack-karbor03:47
*** yamamoto has quit IRC03:48
*** yamamoto has joined #openstack-karbor03:49
*** gouthamr has joined #openstack-karbor04:31
*** gouthamr has quit IRC05:16
*** liujiong has quit IRC05:44
*** liujiong has joined #openstack-karbor05:45
*** yamamoto has quit IRC06:01
*** yamamoto has joined #openstack-karbor06:05
openstackgerritMerged openstack/karbor master: Ignore plan parameters for unloaded plugins  https://review.openstack.org/49205406:06
openstackgerritMerged openstack/karbor master: Imported Translations from Zanata  https://review.openstack.org/49199906:29
*** saggi has quit IRC06:33
*** saggi has joined #openstack-karbor06:39
openstackgerritYuval Brik proposed openstack/karbor-dashboard master: Plan: send only parameters for protected resources  https://review.openstack.org/49239306:39
jiaopengjuping yuval07:22
yuvalhey jiaopengju07:22
jiaopengjuyuval chenying: I am doing the integration with freezer and found some issues. Freezer can backup two tpye of openstack resources: volume and nova instance(contains image, network or system volume). I try to use freezer plugin support volume resource and server resource, but failed.07:26
yuvaljiaopengju: what kind of failure?07:27
chenyingJust now I and jiaopengju discuss the freezer plugin, he want to support volume and server in one plugin.07:27
jiaopengjuyuval chenying: It is because that karbor will split server resource into ‘image, volume, network’07:28
jiaopengjuyuval: but freezer supports nova instance backup, which already contains image, volume and network07:29
yuvaljiaopengju: "nova instance backup" - freezer feature or nova feature?07:29
jiaopengjuyuval: freezer feature07:29
yuvaljiaopengju: this is exactly why we then protection plugins have 3 kinds of "contexts"07:30
jiaopengjuyuval: I think the root of this issue is that the resource graph is stable for all providers07:31
yuvaljiaopengju: the first one is the ProtectionPlugin instance itself, which is created in the context of the whole operation07:31
yuvaljiaopengju: the second one is the Operation instance which is created in the context of the operation for each resource07:31
yuvaljiaopengju: the third one is the ProtectionPlugin class variables, which persist across the lifetime of the service, but that's less important07:32
yuvaljiaopengju: what I'm saying is: consider an operation spanning multiple resource types, like freezer's nova instance backup07:32
yuvaljiaopengju: Karbor will create a Protection Plugin for volume and image, which can just gather the volume and image information or even do nothing07:33
yuvaljiaopengju: then the protection plugin for server can initiate the freezer operation for the nova server, backuping the image and volume as well07:34
yuvaljiaopengju: what do you mean "is stable for all providers"?07:37
jiaopengjuyuval: can not be changed07:38
jiaopengjuyuval: you mean that I can use ‘do nothing ’ when creating Protection Plugin?07:39
yuvaljiaopengju: a protection plugin can be "registered" for multiple resource (using the 'get_supported_resources_types' method)07:40
jiaopengjuyuval: Yes, I have used this07:40
yuvaljiaopengju: you can create a freezer plugin which will be registered for 'image', 'volume', 'server'07:41
yuvaljiaopengju: it will do nothin for image and volume, and for server, it will protect/restore all three07:41
chenyingjiaopengju mean that now the resource dependency in karbor only consider the default usecase. For example, in karbor the volume mount to a server all the sub reousrce of this servce. But in freezer's plugin usecase,  he want to backup service meatadata and bootable volume when taskflow pass a service id to this plugin.07:43
jiaopengjuyuval: when doing server backup( the server contains system volume), it seems karbor will send two request to freezer, one for server, one for system volume07:43
chenyinghe think only the no bootable volume are the sub resource of the server in his usecase.07:43
yuvaljiaopengju: I don't get it. You said freezer has "nova instance backup" which takes care of server+image+volume07:44
jiaopengjuyuval: yes. But the task flow was generated by karbor07:45
yuvaljiaopengju: if so, then for a volume and an image, do nothing. For a server, protect all three07:45
yuvaljiaopengju: then register your plugin to volume and image and do a no-op07:45
jiaopengjuyuval: As you say, how can I do volume backup in the same plugin?07:46
jiaopengjuyuval: I want to support both freezer server and freezer volume in one plugin07:46
chenyingjiaopengju: In this usecase, you need devlep anonther plugin only backup volume.07:46
yuvalchenying: no need, just see if the volume is attached07:47
yuvalchenying: if it is attached - leave it to the server call to backup. If not attached, call freezer to back it up07:47
yuvalchenying: we can actually try to see if the attached server is in the plan or not, but that's an edge case07:48
chenyingOr as yuval said, you also can check the attached or not attached in one plugin itself.07:49
jiaopengjuyuval chenying: freezer server backup, only backup the system volme07:50
jiaopengjuyuval chenying: so if we have a nova instance, which has a system volume and two other data volume(also attached) ?07:51
yuvaljiaopengju: call freezer only for the server (and if I understand what you say correctly, freezer will take care of the volumes)07:52
jiaopengjuyuval: freezer only care of system volume when doing server backup07:53
jiaopengjuyuval: not data volumes07:53
yuvaljiaopengju: then for volumes, use freezer to backup data volumes only, and in server backup, call freezer. On restore, restore them all and attach07:53
yuvaljiaopengju: pretty sure you can query cinder to understand if the volume is attached and whether a server is using it to boot from (aka system volume)07:54
jiaopengjuyuval: get it , I understand what you mena07:54
yuvaljiaopengju: :)07:54
jiaopengjuyuval:  thank you !07:54
yuvaljiaopengju: no, thank you! :D07:55
yuvaljiaopengju: feel free to consult more if you want07:55
jiaopengjuyuval: I would like to do that :)07:56
yuvalchenying: any idea why our gate keep failing with timeouts?08:00
chenyingyuval I only know the fullstack test about volume restore, the error is in cinder-backup service, these are some exceptions about rpc when restore a volume. I ask the guy from cinder team to ses this error several times, he also can not find the reason.08:07
yuvalchenying: :\08:08
yuvalchenying: frustrating08:08
chenyingyuval cinder project jenkins don't have a test for volume restore.08:08
chenyingyuval: I aslo think the fullstack of karbor spend too much time to run all the tests.08:12
yuvalchenying: do you suggest we remove them?08:12
chenyingyuval nearly one hour and half.08:12
yuvalchenying: only the devstack takes half an hour08:13
chenyingyuval: don't remove. For example, there are several fullstack tests about volume restore, only need one test to run actual volume restore, other tests can use the provider of noop.conf.08:15
yuvalchenying: I agree08:15
chenyingyuval: The test about test_scheduled_operations_create_and_scheduled aslo take too much time. The tests about checkpoint are tested already, this test aslo can use noop provider.08:18
chenyingyuval We only need test the scheduler in this one, we don't need actually test  volume backup and restore.08:19
*** yamamoto has quit IRC08:27
*** yamamoto has joined #openstack-karbor08:28
*** yamamoto has quit IRC08:31
*** yamamoto has joined #openstack-karbor08:32
yuvalchenying: have you tested karbor lately? On a deployment?08:47
chenyingyuval: I only have one deployment. all the services are enable.08:49
chenyingyuval I do all the test and development in this depolyment.08:50
yuvalchenying: are all services up to date? I'm getting some weird things, want to know if you found them also08:50
chenyingyuval  only karbor service is up to date. Other serivces are installed at Jul 11.08:52
openstackgerritchenying proposed openstack/karbor master: Add Protectable Plugins Development Guide doc to Karbor  https://review.openstack.org/49244209:06
openstackgerritchenying proposed openstack/karbor master: Add the extra_info parameter when checkpoint being created manually  https://review.openstack.org/49244709:27
chenyingyuval: If you get some weird things about your environment, it's better to instatll a new devstack environment. I often do like this. :D At least the devstack environment in karbor jinkens can expose most of failures about karbor.09:48
openstackgerritchenying proposed openstack/karbor master: [WIP]Optimize the execution time of karbor fullstack tests  https://review.openstack.org/49245709:51
*** jiaopengju has quit IRC10:14
*** yamamoto has quit IRC10:21
*** liujiong has quit IRC10:22
*** yamamoto has joined #openstack-karbor10:25
*** yamamoto has quit IRC10:28
*** yamamoto has joined #openstack-karbor10:28
*** jiaopengju_ has joined #openstack-karbor10:31
*** yamamoto has quit IRC10:41
yuvalchenying: I have a fresh devstack10:49
*** yamamoto has joined #openstack-karbor11:09
*** yamamoto_ has joined #openstack-karbor11:20
*** yamamoto has quit IRC11:24
*** NatanBro has joined #openstack-karbor11:54
*** jiaopengju__ has joined #openstack-karbor12:36
*** jiaopengju_ has quit IRC12:39
openstackgerritYuval Brik proposed openstack/karbor master: Support swift auth domain name  https://review.openstack.org/49252312:51
*** gouthamr has joined #openstack-karbor14:00
*** jiaopengju__ has quit IRC14:44
*** yamamoto_ has quit IRC15:08
*** yamamoto has joined #openstack-karbor15:10
*** yamamoto has quit IRC15:11
*** saggi has quit IRC15:31
*** saggi has joined #openstack-karbor15:36
*** saggi has quit IRC15:39
*** saggi- has joined #openstack-karbor15:39
*** saggi- is now known as saggi15:39
*** yamamoto has joined #openstack-karbor16:12
*** saggi- has joined #openstack-karbor16:16
*** yamamoto has quit IRC16:17
*** saggi has quit IRC16:19
*** saggi- is now known as saggi16:19
*** NatanBro has quit IRC16:30
*** gouthamr_ has joined #openstack-karbor17:51
*** gouthamr has quit IRC17:51
*** openstackgerrit has quit IRC19:03
*** gouthamr_ has quit IRC20:50
*** gouthamr has joined #openstack-karbor21:23
*** yamamoto has joined #openstack-karbor22:51
*** lihi has quit IRC23:10
*** dimak has quit IRC23:10
*** dimak has joined #openstack-karbor23:11
*** lihi has joined #openstack-karbor23:11
*** gouthamr has quit IRC23:12
*** yamamoto has quit IRC23:33
*** yamamoto has joined #openstack-karbor23:40

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