since 4.3 the management-server can tell if systemvm and VR require upgrade, which is great ! but, as of 4.4 it's not working anymore and systemvm must be upgrade as well.
And what if their is another hartbleed issue between release requiring upgrade of systemvm ? Citrix is providing a Python script to CloudPlatform in order to upgrade the systemvm template to a latest 4.3from jun 2014, which is not bad. but... Doing automatic upgrade of system vm is out of scope because of implicated downtime. But could it be possible to implement a naming standard of systemvm template so the management server would detect a newer version of template and ask for upgrade of systemvm and VR? Something like if I have those systemvm templates: - SystemVM Template (XenServer) - systemvm-xenserver-4.3 - systemvm-xenserver-4.4 right now in 4.4 it will use systemvm-xenserver-4.3 template which is not working with acs4.4. Could the detection of a new template be automated? like if I have to upgrade to a newer version withing 4.4, like systemvm-xenserver-4.4.1 ? or Could it be simple to have a Global setting where we define the systemvm-template to use and by default it would be SystemVM Template (*) ? unless something like that is already in place? Thanks, PL
