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...@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 >
