cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chandraprakash mishra <cpmishra...@gmail.com>
Subject Re: how we can avoid conflict if using two separate cs env with common resources
Date Thu, 03 Jul 2014 06:46:31 GMT
is there possible to upgrade CS(with db) with zero downtime ?


On Fri, Jun 27, 2014 at 10:46 PM, Pierre-Luc Dion <pdion@cloudops.com>
wrote:

> Hi chandraprakash,
>
> Yes, there is a process that remove any VMs not managed by cloudstack on
> hypervisors. As far as I know you can't disabled that process.
>
>
>
> *Pierre-Luc DION*
> Architecte de Solution Cloud | Cloud Solutions Architect
> t 855.652.5683
>
> *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
>
>
> On Fri, Jun 27, 2014 at 12:32 PM, chandraprakash mishra <
> cpmishra.20@gmail.com> wrote:
>
> > thanks for replied to me.
> > I need one more help .is there any process/scheduler  is running in CS
> > which delete the vms from hyper-wiser( xen host) if that vms info are not
> > available in database.
> > if it is true,  then how we can disable this service/scheduler for some
> > time.
> >
> >
> >
> >
> > On Thu, Jun 26, 2014 at 6:07 PM, Pierre-Luc Dion <pdion@cloudops.com>
> > wrote:
> >
> > > if you want to run multiple CloudStack env using same networks but
> > > different databases and different version of CloudStack you have to use
> > > seperate secondary storage, at least it have to have a different
> > mountpoint
> > > if they use the same nfs server , ex:  /export/env1, /export/env2
> > > Also two seperate CloudStack env cannot managed the same hypervisor
> > server.
> > > so you will have to have 2 hypervisors hosts, they could be VM on a
> > > physical servers if you only have one physical server.
> > >
> > > On the network side, then you need to pay attention so both envs does
> not
> > > conflict with DHCPs and Vlans,
> > >
> > >
> > >
> > > *Pierre-Luc DION*
> > > Architecte de Solution Cloud | Cloud Solutions Architect
> > > t 855.652.5683
> > >
> > > *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts
> > > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> > > w cloudops.com *|* tw @CloudOps_
> > >
> > >
> > >
> > > On Thu, Jun 26, 2014 at 6:30 AM, chandraprakash mishra <
> > > cpmishra.20@gmail.com> wrote:
> > >
> > > > Hello,
> > > >            I have setup two CS env but both are using same
> > infrastructure
> > > > .Now i am getting a lot of conflict problem due to separate db
> > > >
> > > > Env1-    CS1 --> DB1
> > > >
> > > > Env2-     CS2 --> DB2
> > > >
> > > >
> > > > *Conflict scenario :*
> > > >
> > > > 1) during vm creation it was found that vm-id had been conflicted in
> > xen
> > > > host
> > > > 2) during template creation it was found that template has been
> > > conflicted
> > > > in secondary storage
> > > >      eg.
> > > >                created one template from CS1 and one template from
> CS2
> > > .Now
> > > > both template created vhd file in one folder.
> > > >  .             $ cat 2/204/
> > > >
> > >  160eaf67-a20a-37f0-83c9-326915990efc.vhd
> > > >
> > > >
> > >  392b128e-0b4c-3a8b-9bf5-3488dd026816.vhd
> > > >                                    template.properties
> > > >
> > > > My concern is
> > > >                       1)  how we can avoid conflict  ?
> > > >                       2) is there any option for reserved resources
> and
> > > > avoid conflict ?
> > > >
> > > > --
> > > > Thanks and Regards,
> > > >  cpm
> > > >
> > >
> >
> >
> >
> > --
> > Thanks and Regards,
> > Chandra Prakash Mishra
> > Software engineer,hp
> > 9611424996
> >
>



-- 
Thanks and Regards,
Chandra Prakash Mishra
Software engineer,hp
9611424996

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message