| *** dasp has joined #openstack-fenix | 02:11 | |
| openstackgerrit | Tomi Juvonen proposed x/fenix master: Add live migration support https://review.opendev.org/657390 | 03:14 |
|---|---|---|
| tojuvone | Btw, this is workaround example for live_migration to work on same antiaffinity group within ~70sec, before periodic Nova cache update: http://paste.openstack.org/show/751210/ | 03:30 |
| tojuvone | Example if for Fenix and OpenStack services running in Docker in OPNFV Doctor testing env | 03:31 |
| tojuvone | This is handling at least some of this, while as I commented there, it might not handle it all: https://bugs.launchpad.net/nova/+bug/1821755 | 03:48 |
| openstack | Launchpad bug 1821755 in OpenStack Compute (nova) "live migration break the anti-affinity policy of server group simultaneously" [Medium,In progress] - Assigned to Boxiang Zhu (bxzhu-5355) | 03:48 |
| *** dasp has quit IRC | 04:08 | |
| *** dasp has joined #openstack-fenix | 04:30 | |
| hyunsikyang | Hi tojuvone | 05:15 |
| hyunsikyang | Are you there? | 05:15 |
| tojuvone | hi hyunsikyang | 05:21 |
| hyunsikyang | How are you? | 05:21 |
| tojuvone | Fine, jsut havent had time to sleep the jet lag, but it is weekend soon :) | 05:21 |
| tojuvone | and you? | 05:21 |
| hyunsikyang | So did I, but today is good:) | 05:22 |
| hyunsikyang | Anyway Thank you for your explanation about BP | 05:22 |
| tojuvone | great | 05:22 |
| hyunsikyang | But I have a question aobut your comment:) | 05:22 |
| tojuvone | ok, shoot | 05:22 |
| hyunsikyang | "Yes, you are right. If tacker is not going to support it doesn't belong here. Even if would, it would be a series of BPs and it would then be mentioned to be worked separately. | 05:23 |
| hyunsikyang | " | 05:23 |
| tojuvone | ok... | 05:23 |
| tojuvone | So obviously Tacker do nto implement any VNF upgrade at the same | 05:24 |
| hyunsikyang | Yes. | 05:24 |
| tojuvone | this means one would not mention it | 05:24 |
| tojuvone | if mention it would... | 05:24 |
| hyunsikyang | Ah | 05:24 |
| tojuvone | you would mention it by saying some future work with another blueprint | 05:25 |
| tojuvone | so bigger chagnes might be series of blueprints | 05:25 |
| hyunsikyang | I thought that even it doesn't support it now, it is need to mention it | 05:25 |
| hyunsikyang | as a perspective of VNFM | 05:25 |
| hyunsikyang | yes | 05:25 |
| hyunsikyang | OK | 05:25 |
| tojuvone | you can mention... | 05:25 |
| hyunsikyang | I understood. | 05:25 |
| tojuvone | but then it needs some right section where it is "possible future work" | 05:26 |
| tojuvone | or soemthing like that | 05:26 |
| tojuvone | there might be example somewhere as done Nova BPs | 05:26 |
| tojuvone | seems in nova-specs in "proposed change" you can have a sentence that can tell about some possible future blueprint | 05:34 |
| hyunsikyang | Sorry. I had a meeting suddenly...OK. I will add comment :) | 06:49 |
| *** tojuvone has quit IRC | 09:46 | |
| *** tojuvone has joined #openstack-fenix | 09:46 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!