Hi all,
from what I can find, there are three more or less established/already well
elaborated approaches to simulate a CloudStack instance locallly.
Depending on the target group and their goals, they can have different levels
of fidelity and usability.
1. Obviously CloudStack developers confgure a KVM development environment to
work inside it, this is part of the Apache CloudStack Hackerbook kindly shared
by ShapeBlue. [1]
2. For test scenarios, Hackerbook describes a mocked simulator approach [2]
3. For users for whom the whole cloud system is just a "black box", especially
cloud beginners, there is a single integrated Docker container. [3]
With the rise of CI/CD and infrastructure as code automation practices, where
you just need more or less on demand one or even many versions of the
CloudStack API,
[3] appears to be a crucial building block in the cloud userspace before just
"trying out CloudStack".
So it appears that there might be much demand on a Apache CloudStack
containerized instance:
1. Demand from potential new adopters, for their "Apache CloudStack to go" demos
2. Demand from DevOps/GitOps/SRE/you-name-it enabled teams who implement their
virtual infrastructure for example with Terraform and the CloudStack provider
plugin and want to simulate rollout scenarios.
However, is this true?
* the container simulator hasn't been updated on DockerHub since a couple of
years; is there another place in meantime or will this approach dumped for some
reason?
* there is not so much discussion about this asset on mailing lists; so there
is not so much demand as one might assume?
What do you think?
kind regards
--
Peter Muryshkin
Fraunhofer Gesellschaft
https://www.linkedin.com/in/muryshkin/