<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi,<div class=""><div class="">I am very interested in your Vpnaas and Wallaby test. Because for me, Vpnaas worked without problem with Victoria (I use Centos and kolla-ansible to install Openstack), but impossible to make vpnaas work with Wallaby. I don't understand why and it's hard to get help.</div><div class="">If it works for you, please let me know.</div><div class="">FYI, using Vpnaas in horizon is really easy and very well done.</div><div class="">Franck</div><div class=""><br class=""></div><div class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="" style="orphans: 2; widows: 2; font-family: Calibri, sans-serif; font-size: 11pt; margin: 0cm 0cm 0.0001pt;"></div></div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">Le 17 juil. 2021 à 15:00, Anirudh Gupta <<a href="mailto:anyrude10@gmail.com" class="">anyrude10@gmail.com</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><div dir="auto" class=""><div class="">Hi Radosław</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Thanks for your reply.</div><div dir="auto" class="">Is there any configuration or anything workaround avoid this?</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Regards</div><div dir="auto" class="">Anirudh Gupta<br class=""><br class=""><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Sat, 17 Jul, 2021, 12:27 am Radosław Piliszek, <<a href="mailto:radoslaw.piliszek@gmail.com" class="">radoslaw.piliszek@gmail.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">For the record, in the other mailing thread (on stx) I suggested this<br class="">
should not be happening and it was likely some resource pressure.<br class="">
<br class="">
-yoctozepto<br class="">
<br class="">
On Fri, Jul 16, 2021 at 8:31 PM Anirudh Gupta <<a href="mailto:anyrude10@gmail.com" target="_blank" rel="noreferrer" class="">anyrude10@gmail.com</a>> wrote:<br class="">
><br class="">
> Hi Team,<br class="">
><br class="">
> We have deployed the Openstack Victoria release using Multinode Kolla Ansible deployment.<br class="">
> There are 2 nodes - one for compute and other for Controller+Network<br class="">
><br class="">
> Following the below link, we also upgraded the setup from Victoria to wallaby<br class="">
><br class="">
> <a href="https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html" rel="noreferrer noreferrer" target="_blank" class="">https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html</a><br class="">
><br class="">
> During the Upgrade process, we figured out that the VM which was spawned before Upgrade went to shut off during the middle of Upgrade process and post completion of the upgrade process, we had to manually start the VM again.<br class="">
><br class="">
> Ideally we were expecting that the existing Workloads would remain unimpacted in this process.<br class="">
><br class="">
> Can someone please suggest if our observation is correct or any steps that needs to be taken in order to avoid this?<br class="">
><br class="">
> Regards<br class="">
> Anirudh Gupta<br class="">
</blockquote></div></div></div>
</div></blockquote></div><br class=""></div></body></html>