Re: Rohit Vavaldas - GSoC - 2018

[Rohit vavaldas <ro...@gmail.com>]

Hi Daan,

Can you suggest me on how the new API should handle the virtual router?
As the old router is not able to recognize upgraded system VM. Should a new
VR be created and replace the old one within this API call?
Can you brief me on how the version update procedure which upgrades with
System VMs, be in common ground with upgrade process of individual
instances?

Thanks,
Rohit Vavaldas


On Mon, Feb 26, 2018 at 1:35 PM, Daan Hoogland <da...@gmail.com>
wrote:

> 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/6116f1d77cc2272f75f844a22597b2
> 96aa1f84f7acbd2a4f82127743@%3Cdev.cloudstack.apache.org%3E
> [2]
> https://lists.apache.org/thread.html/fe347ccf41073def042d35b51ce600
> 7a0f3fe898690f5328e40143e1@%3Cdev.cloudstack.apache.org%3E
>
> please feel free to inquire further ...
>
>
>
> On Mon, Feb 26, 2018 at 5:02 PM, Rohit vavaldas <ro...@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
>



-- 
Thanks and Regards
Rohit Vavaldas

Re: Rohit Vavaldas - GSoC - 2018

[Rafael Weingärtner <ra...@gmail.com>]

Just to add some other information. There is a PR to externalize system VMs
templates. Then, administrators would be able to customize system VMs
template as they do with virtual router.

https://github.com/apache/cloudstack/pull/2275

On Sun, Mar 18, 2018 at 1:41 PM, Rohit vavaldas <ro...@gmail.com>
wrote:

> Got it. Thanks Daan.
>
>
> Best,
> Rohit Vavaldas
>
> On Sun, Mar 18, 2018, 4:58 AM Daan Hoogland <da...@gmail.com>
> wrote:
>
> > H Rohit,
> >
> > In the present and prior versions the systemVM template is only upgraded
> on
> > upgrade of the management server. A suitable template had to be
> registered
> > with a specified name before the upgrade and if it wasn't or it had the
> > wrong attributes it won't be registered as the current system template.
> The
> > upgrade of routers is a separate action that is up to the discretion of
> the
> > admin of the network that uses it. It is not the intention to automate it
> > unless we can find a good optional procedure. I can imagine a network
> > administrator being more worried about being up to date than about
> uptime.
> > For such cases it would make sense to automate further.
> >
> > in summary; the upgrade of the template and of the VRs are two different
> > procedures.
> >
> > regards,
> >
> > On Fri, Mar 16, 2018 at 6:44 PM, Rohit vavaldas <rohitvavaldas@gmail.com
> >
> > wrote:
> >
> > > Hi Daan,
> > >
> > > Can you suggest me on how the new API should handle the virtual router?
> > > As the old router is not able to recognize upgraded system VM. Should a
> > new
> > > VR be created and replace the old one within this API call?
> > > Can you brief me on how the version update procedure which upgrades
> with
> > > System VMs, be in common ground with upgrade process of individual
> > > instances?
> > >
> > > Thanks,
> > > Rohit Vavaldas
> > >
> > >
> > > On Mon, Feb 26, 2018 at 1:35 PM, Daan Hoogland <
> daan.hoogland@gmail.com>
> > > wrote:
> > >
> > > > 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/6116f1d77cc2272f75f844a22597b2
> > > > 96aa1f84f7acbd2a4f82127743@%3Cdev.cloudstack.apache.org%3E
> > > > [2]
> > > > https://lists.apache.org/thread.html/fe347ccf41073def042d35b51ce600
> > > > 7a0f3fe898690f5328e40143e1@%3Cdev.cloudstack.apache.org%3E
> > > >
> > > > please feel free to inquire further ...
> > > >
> > > >
> > > >
> > > > On Mon, Feb 26, 2018 at 5:02 PM, Rohit vavaldas <
> > rohitvavaldas@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
> > > >
> > >
> > >
> > >
> > > --
> > > Thanks and Regards
> > > Rohit Vavaldas
> > >
> >
> >
> >
> > --
> > Daan
> >
>



-- 
Rafael Weingärtner

Re: Rohit Vavaldas - GSoC - 2018

[Rohit vavaldas <ro...@gmail.com>]

Got it. Thanks Daan.


Best,
Rohit Vavaldas

On Sun, Mar 18, 2018, 4:58 AM Daan Hoogland <da...@gmail.com> wrote:

> H Rohit,
>
> In the present and prior versions the systemVM template is only upgraded on
> upgrade of the management server. A suitable template had to be registered
> with a specified name before the upgrade and if it wasn't or it had the
> wrong attributes it won't be registered as the current system template. The
> upgrade of routers is a separate action that is up to the discretion of the
> admin of the network that uses it. It is not the intention to automate it
> unless we can find a good optional procedure. I can imagine a network
> administrator being more worried about being up to date than about uptime.
> For such cases it would make sense to automate further.
>
> in summary; the upgrade of the template and of the VRs are two different
> procedures.
>
> regards,
>
> On Fri, Mar 16, 2018 at 6:44 PM, Rohit vavaldas <ro...@gmail.com>
> wrote:
>
> > Hi Daan,
> >
> > Can you suggest me on how the new API should handle the virtual router?
> > As the old router is not able to recognize upgraded system VM. Should a
> new
> > VR be created and replace the old one within this API call?
> > Can you brief me on how the version update procedure which upgrades with
> > System VMs, be in common ground with upgrade process of individual
> > instances?
> >
> > Thanks,
> > Rohit Vavaldas
> >
> >
> > On Mon, Feb 26, 2018 at 1:35 PM, Daan Hoogland <da...@gmail.com>
> > wrote:
> >
> > > 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/6116f1d77cc2272f75f844a22597b2
> > > 96aa1f84f7acbd2a4f82127743@%3Cdev.cloudstack.apache.org%3E
> > > [2]
> > > https://lists.apache.org/thread.html/fe347ccf41073def042d35b51ce600
> > > 7a0f3fe898690f5328e40143e1@%3Cdev.cloudstack.apache.org%3E
> > >
> > > please feel free to inquire further ...
> > >
> > >
> > >
> > > On Mon, Feb 26, 2018 at 5:02 PM, Rohit vavaldas <
> rohitvavaldas@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
> > >
> >
> >
> >
> > --
> > Thanks and Regards
> > Rohit Vavaldas
> >
>
>
>
> --
> Daan
>

Re: Rohit Vavaldas - GSoC - 2018

[Daan Hoogland <da...@gmail.com>]

H Rohit,

In the present and prior versions the systemVM template is only upgraded on
upgrade of the management server. A suitable template had to be registered
with a specified name before the upgrade and if it wasn't or it had the
wrong attributes it won't be registered as the current system template. The
upgrade of routers is a separate action that is up to the discretion of the
admin of the network that uses it. It is not the intention to automate it
unless we can find a good optional procedure. I can imagine a network
administrator being more worried about being up to date than about uptime.
For such cases it would make sense to automate further.

in summary; the upgrade of the template and of the VRs are two different
procedures.

regards,

On Fri, Mar 16, 2018 at 6:44 PM, Rohit vavaldas <ro...@gmail.com>
wrote:

> Hi Daan,
>
> Can you suggest me on how the new API should handle the virtual router?
> As the old router is not able to recognize upgraded system VM. Should a new
> VR be created and replace the old one within this API call?
> Can you brief me on how the version update procedure which upgrades with
> System VMs, be in common ground with upgrade process of individual
> instances?
>
> Thanks,
> Rohit Vavaldas
>
>
> On Mon, Feb 26, 2018 at 1:35 PM, Daan Hoogland <da...@gmail.com>
> wrote:
>
> > 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/6116f1d77cc2272f75f844a22597b2
> > 96aa1f84f7acbd2a4f82127743@%3Cdev.cloudstack.apache.org%3E
> > [2]
> > https://lists.apache.org/thread.html/fe347ccf41073def042d35b51ce600
> > 7a0f3fe898690f5328e40143e1@%3Cdev.cloudstack.apache.org%3E
> >
> > please feel free to inquire further ...
> >
> >
> >
> > On Mon, Feb 26, 2018 at 5:02 PM, Rohit vavaldas <rohitvavaldas@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
> >
>
>
>
> --
> Thanks and Regards
> Rohit Vavaldas
>



-- 
Daan