Hi Lucian,
I see that you're using cloudstack2, just "cloudstack and select
"CloudHosting" from "provisioning type, in case you want to provision accounts
"flexible accounts" where a customer can use the resources to build custom VMs.
If not, you can go with Single VPS, where the resources
You need the hostname , or can choose the generated hostname
On Wed, Mar 31, 2021 at 8:51 PM wrote:
> Hi Lucian,
>
> I see that you're using cloudstack2, just "cloudstack and select
> "CloudHosting" from "provisioning type, in case you want to provision
> accounts "flexible accounts" where a
Hi there Nicolas,
why is actually interaction important in this context? I read that you want to
enable developers to quickly run and check the results.
For my own scenario I had a requirement to have a set of functional tests only
seeing ACS as a blackbox to have a "sanity check" of the
I agree with Rohit, if people want to improve mavin ux that’s fine, but keep it
a Marvin thing.
- Marvin outputs a file that says what passed and what failed.
- A GUI is going to need constant ongoing maintenance for it to be able to
understand tests to give meaningful additional information
Thanks for starting this thread Abhishek. I think all 'allocated' API response
keys (irrespective of type such as CPU, RAM, storage/disk etc) across all
list/metrics APIs should consider overprovisioning factor.
For example, if the total resource value/limit is 100 and overprovisioning
factor
sureshanaparti commented on a change in pull request #205:
URL:
https://github.com/apache/cloudstack-documentation/pull/205#discussion_r604711626
##
File path: source/adminguide/storage.rst
##
@@ -121,6 +121,14 @@ OCFS2. In this case the CloudStack does not attempt to
mount
Hi devs,
There have been recurring issues and changes for API responses not considering
the over-provisioning factor while reporting metrics for hosts, clusters, etc.
https://github.com/apache/cloudstack/issues/4778
https://github.com/apache/cloudstack/pull/4850
