Hey Rohit, nice to see you here. What you should be looking at is mostly the register template API and service calls and then the update version code for the last version that required an upgrade. Off the top of my head it is in the class Upgrade410to411.java (don't kill me if I'm off by a few chars) next to that there is ofcourse the upgrade process of the individual instances of system VMs. A whole other story, part of which you can find in the discuss thread [1] and a proposal [2] on the mailing list arcghives.
[1] https://lists.apache.org/thread.html/6116f1d77cc2272f75f844a22597b296aa1f84f7acbd2a4f82127743@%3Cdev.cloudstack.apache.org%3E [2] https://lists.apache.org/thread.html/fe347ccf41073def042d35b51ce6007a0f3fe898690f5328e40143e1@%3Cdev.cloudstack.apache.org%3E please feel free to inquire further ... On Mon, Feb 26, 2018 at 5:02 PM, Rohit vavaldas <rohitvaval...@gmail.com> wrote: > Hi, > > I am Rohit Vavaldas, a graduate student pursuing my masters in computer > science at the University of Oklahoma. I am very much interested to work on > CloudStack and excited to participate in GSoC. I am interested to work on > the issue to create an API driven SystemVM upgrade. The current flow of > updating system VM template is to first register newer version of system VM > template using 'registertemplate' API and then invoke 'preparetemplate' on > the above-registered template. So, part of this, what should I be looking > out for to develop this API and also can I please get some more information > in this regard? > > Link to the issue: > > https://issues.apache.org/jira/browse/CLOUDSTACK-10262 > > > > Thanks and Regards > Rohit Vavaldas > -- Daan
