Hello Bryan,

Cloudstack gives you super awesome API feature, so yes you run run a Jenkins 
job to provision instances on target host. So you can achieve this via 2 method.

1- Create compute offering in ACS and provide some tag and that tag should be 
present on the HOST as well, i.e one offering with A tag will provision VM on A 
host, create another compute offering with TAG “B’” which will provision VM on 
B host. So you will have 2 compute offerings -

So you write a script i.e in python or any of your fav language  for the API - 
deployVirtualMachine - and specific the required compute_offering_id. Now this 
script can be executed from your Jenkins pipeline

2- Second method is to pass the host_id in the API call - deployVirtualMachine 
call -  so in this you won’t need to create separate compute offering.

https://cloudstack.apache.org/api/apidocs-4.17/apis/deployVirtualMachine.html



Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com>
        www.indiqus.com <https://www.indiqus.com/>




> On 21-Nov-2022, at 7:19 PM, Bryan Tiang <bryantian...@hotmail.com> wrote:
> 
> Hi Vivek,
> 
> Thank for the response.
> 
> Which of these would be the most recommended method? In terms of 
> simplification and efficient maintenance?
> 
> What about CI/CD? Is it possible to integrate our CICD pipeline to deploy 2 
> instances of the same app to 2 different physical servers? If so, I suppose 
> if I use the Host Tag option, I will somehow need to have the pipeline 
> contain those conditions?
> 
> Regards,
> Bryan
> 
> On 21 Nov 2022, at 6:02 PM, Nux <n...@li.nux.ro> wrote:
> 
> A
> 


-- 
This message is intended only for the use of the individual or entity to 
which it is addressed and may contain confidential and/or privileged 
information. If you are not the intended recipient, please delete the 
original message and any copy of it from your computer system. You are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited unless proper authorization has been 
obtained for such action. If you have received this communication in error, 
please notify the sender immediately. Although IndiQus attempts to sweep 
e-mail and attachments for viruses, it does not guarantee that both are 
virus-free and accepts no liability for any damage sustained as a result of 
viruses.

Reply via email to