Hi!!
I have the same error but I can't find this variable in trove.conf
Do you have the solution to this?
Thanks
--
View this message in context:
http://openstack.10931.n7.nabble.com/trove-ocata-error-tp136919p137859.html
Sent from the Operators mailing list archive at Nabble.com.
Hi Saverio, All Operators
It will be good if I came to know how evacuation of resized instances is
handled from mitaka onwards. It will help me to understand how I can proceed
with Ocata.
Thank you,
Abhishek
-Original Message-
From: Saverio Proto [mailto:ziopr...@gmail.com]
Sent:
Hello,
as far as I know from the Openstack survey there is a very small
number of production environments with more than 100 servers running
already Ocata.
you probably will have to find your self that information and report
back to the list.
thank you
Saverio
2017-07-10 10:27 GMT+02:00
Hi Saverio,
Thank you for reply.
Currently we are using Ocata release for Openstack.
Please let me know if you get any update.
Thank you,
Abhishek
-Original Message-
From: Saverio Proto [mailto:ziopr...@gmail.com]
Sent: Monday, July 10, 2017 12:52 PM
To: Kekane, Abhishek
Cc:
Hello Abhishek,
I am sorry I dont have an answer for your question. I would have to
try my self everything to give answer because I never experienced this
use case you describe.
I would suggest also to specify what version of Openstack you are
working with. Because the behaviour can change a lot
Hi Operators,
Could you please let me know your opinion on below scenario? It will help me to
proceed my work.
Thank you,
Abhishek
-Original Message-
From: Kekane, Abhishek [mailto:abhishek.kek...@nttdata.com]
Sent: Tuesday, July 04, 2017 2:52 PM
To: OpenStack Development Mailing
