Hi Rene,
So if you have upgraded 4.5 to 4.11 (or any version upgrade where new system VM
templates are in play) then your 4.5 VRs are by definition destroyed and you
are running with 4.11 VRs. As a result there is nothing to recover – the
rollback mechanism in this case is to roll back DB, destroy all 4.11 VRs (and
anything else unknown to the original DB) – then start up the 4.5 management
servers. At this point CloudStack management will either automatically build
“new” 4.5 VRs – or worst case you do a network restart which recreates the VR.
If you haven’t upgraded the VRs – and they are still running as version 4.5
under a 4.11 management server – then the rollback is a straight forward DB
rollback and management restart – the original VRs will stay in place.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 11/07/2018, 10:49, "Rene Moser" <m...@renemoser.net> wrote:
Hi
While tested v4.11.1 in the lab and upgraded the routers, we came across
the need of "downgrade" the routers after rolled back to ACS to v4.5
(testing upgrade process).
So my proposal is to have a new api for recover the routers to the
system-vm template, AFAICS similar to
https://cloudstack.apache.org/api/apidocs-4.11/apis/recoverVirtualMachine.html
but for routers.
Any thoughts?
Regards
René
dag.sonst...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
