It's been quite a while since I worked on CloudStack but I think you
may be able to achieve your goal with a shared network.
You'll loose much of the built-in network flexibility in CloudStack,
but that is most likely also the point.
--
Erik
On Tue, Dec 3, 2019 at 8:12 PM Andrija Panic wrote:
>
That's true.
You can experiment with Dedicating a host to the customer. I can't advise
(from top of my head) if also the customer's VR will be created there (but
you can do one-time live migrate if needed to that host) - all customer VMs
will be created on this host while there are free resources
Yes, I thought about your idea, but I would not introduce too many hops...
in addition I cannot manage Public IPs directly from Barracuda VA.
Is there a kind of parameter I can configure to deploy all costumer's
instance on tha same VR's host?
On Tue, Dec 3, 2019 at 6:57 PM Andrija Panic
wrote:
Hi,
it's not possible to completely replace (i.e. not without complete ACS code
base change), but you might want to see if the following helps:
- Assign one or more (as required, one at minimum) additional Public IPs on
the VR, and then configure Static Nat from that Public IP to the internal