Cloudstack cross zone CI/CD setup

[arpanbht]

Hey guys I need some solutions about how can i make ci/cd working on cross zone setup of cloudstack.

In our on prem architecture we crrently have one zone and inside that zone we have created a internal network of 10.1.0.0/16 under a LAN network of 172.16.17.0/24.

We have made a jenkins setup with one master node and two worker nodes, and currently we can easily do the ci/cd to deploy frontend and backend applications into the vms we create with the ip of 10.1.0.0 network say 10.1.167.54.

Now we want to make a seperate zone where if something goes down on zone 1 the vms will get migrated to other zone, but it will cause some issue:

• If a new vm gets created with a random ip just like this internal network say 10.1.24.123 then we have to use two seperate jenkins to do the ci/cd and trigger the pipeline.

• If we can manage to create a new vm with the exact same ip of the previous vm say 10.1.167.54 then how will jenkins know it belongs to the same zone, cause currently jenkins can only see the vms belongs to its own zone.

We need some help about this, If you guys needs to know some thing please let me know.

[DaanHoogland]

@arpanbht , given that you haven’t got a reply yet, I think your questions are not clear for most. Maybe you need to expand on your topology.

• Where is jenkins being controlled from?
• Is jenkins running in the zone?
• supposing it is, is jenkins the application deployed with CI/CD or is there another one or more that is/are deployed in the same network as where jenkins is running in?
• Why does jenkins need to know which zone it is in, or do you mean where the target app is? (btw listVirtualMachines does return the zone id and zone name)
• What is the failover control? It should know which zone is the active one at any moment.