> Thanks for replying. > > but service offering is not a flexible solution, you can not easily scale up > or > scale down a vm by a small change(e.g. add 128MB RAM), you have to create > a new service offering just for this additional 128MB RAM, in which took a lot > of time(correct me if I was wrong here). > > So to replicate the simple re-install process by creating new service offering > for each VM, does not sounds to me a very optimal solution.
In a typical cloud deployment, VMs should be always categorized in ranks marking by service offering. Updating one VM in a rank usually means you are creating a new category, this may be a little fussy to isolated case, but in product deployment it benefits a lot when you need to upgrade the whole rank of VMs. Still, reinstall will be definitely slower than recreating from a new service offering > > Just my 2 cents. > > On Mon, Jul 23, 2012 at 11:24 PM, Frank Zhang <[email protected]> > wrote: > > > >> > >> Hi > >> > >> As traditional understanding of re-install means you re-install OS > >> just like you do with a physical server. > >> > >> So you changed the OS while keeped all your IPs, hardwares unchanged. > >> > >> in case of VM, for example, we want to reinstall a centos 5.6 vm to a > >> centos > >> 6.2 template(not iso), seems there is no way to do it but destory-recreate. > > > > This is actually how cloud works. You can recreate a new VM from the > > same service offering, so you hardware not changed apart from IP > > address. But I didn't see it will affect your business in terms of ip > > address change. If it did, you will re-consider your deploy plan as > > your services should be behind a load balancer or DNAT where your > internal ip addresses not exposed to clients. > > If your services rely on static network, for example, distributed > > software using TCP to do discovery must know ip address of all nodes, > > you have to change the configuration manually (However, a > > sophisticated design should have a configuration repo centrally, that would > ease the task of upgrading each node). > > By nature of cloud, static network is not a main concern currently, > > the ip address allocation should be handled by machine, not human. > > > > > > > >> > >> On Mon, Jul 23, 2012 at 10:53 PM, Anthony Xu <[email protected]> > wrote: > >> > Can you elaborate what's re-install? > >> > > >> > Re-install from the same ISO or different ISO? > >> > What's the difference from installing a new VM from ISO? > >> > > >> > In CloudStack , VM is not OS agnostic for some hypervisors. > >> > CloudStack > >> needs to track the VM OS type. > >> > If CloudStack allows installing from ISO for an existing VM, it may > >> > lose the > >> OS type VM information. > >> > > >> > > >> > Anthony > >> > > >> >> -----Original Message----- > >> >> From: Lu Heng [mailto:[email protected]] > >> >> Sent: Monday, July 23, 2012 12:09 PM > >> >> To: [email protected] > >> >> Subject: Re: Re-install VM > >> >> > >> >> Hi > >> >> > >> >> Thanks for replying > >> >> > >> >> And why there is no simple re-install options? > >> >> > >> >> Sounds to me re-install options like tranditional VPS have will > >> >> make life lot ealier than the way you have descriped > >> >> > >> >> On Mon, Jul 23, 2012 at 8:45 PM, Anthony Xu <[email protected]> > >> >> wrote: > >> >> > There is no re-install option. > >> >> > You can create a snapshot after you install a VM from ISO, then > >> >> > you > >> >> can create a template from this snapshot, then you can create a VM > >> >> from the template, the VM should like a freshly reinstalled VM. > >> >> > > >> >> > Anthony > >> >> > > >> >> >> -----Original Message----- > >> >> >> From: Lu Heng [mailto:[email protected]] > >> >> >> Sent: Monday, July 23, 2012 9:25 AM > >> >> >> To: [email protected] > >> >> >> Subject: Re-install VM > >> >> >> > >> >> >> Hi > >> >> >> > >> >> >> We are using CS 3.0.1 and XENSERVER, seems to me there is no > >> >> >> where I can find a re-install option for the VM, does that > >> >> >> means if we want > >> >> to > >> >> >> re-install the system, we either need to do it manually by > >> >> >> console with ISO or we have to destroy it and create a new one? > >> >> >> > >> >> >> -- > >> >> >> -- > >> >> >> Kind regards. > >> >> >> Lu > >> >> >> > >> >> >> This transmission is intended solely for the addressee(s) shown > >> >> above. > >> >> >> It may contain information that is privileged, confidential or > >> >> >> otherwise protected from disclosure. Any review, dissemination > >> >> >> or > >> >> use > >> >> >> of this transmission or its contents by persons other than the > >> >> >> intended addressee(s) is strictly prohibited. If you have > >> >> >> received this transmission in error, please notify this office > >> >> >> immediately > >> >> and > >> >> >> e-mail the original at the sender's address above by replying > >> >> >> to > >> >> this > >> >> >> message and including the text of the transmission received. > >> >> > >> >> > >> >> > >> >> -- > >> >> -- > >> >> Kind regards. > >> >> Lu > >> >> > >> >> This transmission is intended solely for the addressee(s) shown above. > >> >> It may contain information that is privileged, confidential or > >> >> otherwise protected from disclosure. Any review, dissemination or > >> >> use of this transmission or its contents by persons other than the > >> >> intended addressee(s) is strictly prohibited. If you have received > >> >> this transmission in error, please notify this office immediately > >> >> and e-mail the original at the sender's address above by replying > >> >> to this message and including the text of the transmission received. > >> > >> > >> > >> -- > >> -- > >> Kind regards. > >> Lu > >> > >> This transmission is intended solely for the addressee(s) shown above. > >> It may contain information that is privileged, confidential or > >> otherwise protected from disclosure. Any review, dissemination or use > >> of this transmission or its contents by persons other than the > >> intended addressee(s) is strictly prohibited. If you have received > >> this transmission in error, please notify this office immediately and > >> e-mail the original at the sender's address above by replying to this > >> message and including the text of the transmission received. > > > > -- > -- > Kind regards. > Lu > > This transmission is intended solely for the addressee(s) shown above. > It may contain information that is privileged, confidential or otherwise > protected from disclosure. Any review, dissemination or use of this > transmission or its contents by persons other than the intended addressee(s) > is strictly prohibited. If you have received this transmission in error, > please > notify this office immediately and e-mail the original at the sender's address > above by replying to this message and including the text of the transmission > received.
