<img src="https://certify.alexametrics.com/atrk.gif?account=VdU0q1FYxz20cv" style="display:none" height="1" width="1" alt="">
Embotics Cloud Management Blog

Webinar Q&A: Cloud Management - Proof of Concept Made Easy

Webinar Q&A - Proof of Concept Made EasyAt the end of each of our webinars, we hold a Q&A session where the audience can ask questions that arose from the webinar content. This blog series highlights some of those questions to expose them to a wider audience.

This week the questions come from the webinar, Cloud Management - Proof of Concept Made Easy, where large scale virtualization expert and VMware vExpert Stuart Burns, and Embotics’ Lead Solutions Architect, Colin Jack gave their perspective on implementing a functional day-one proof of concept (PoC) for a cloud management platform using Embotics vCommander.

Q1: Workflow Approvals - When should they be automated, and when should they not ? What's the right way to approach them?

Stuart: The best way to look at approvals is that you really want to mimic what the business policies are. It's all about what the business wants. For example, if the businesses has small, medium and large systems available to deploy in the service catalog, you might want to say that anything above a medium has to go forward for approval. It really just depends on what the company itself actually want's to do with the product and how much autonomy it wants to give to the users. It's more a business question than a technology question.

Q2: How would quotas help within the approval process?

Colin: When you implement vCommander you are able to set up quotas such that, for example, the engineering department has so much CPU, so much memory, and so much disk. Members of that department can then consume against that quota. So really what you're doing is you're putting boundaries against them, such that they can consume a set of resources, and once they've exhausted those resources, they have to come and ask for more via the approval process. It's really putting some guard rails in place so that people aren't over consuming the offerings that you're putting out there.

If you are on public cloud, we can actually change that so that you can make it based on cost. It's almost like giving somebody your credit card with a limit on it, saying that "you can spend so much in Azure or AWS but once you get your credit card limit, you're not going to be getting any more services."

Q3: It was mentioned that the trial product used Postgres, how does the product scale up when you go to a SQL server?

Colin: When you download vCommander, it's going to come with the Postgres database. We call that the embedded database and there's really no configuration that you need to do for that. That's part of the installation wizard where it will automatically install, and configure the database. For any customer whose implementing at scale or who is always on an SQL instance where they want to have that robustness and reliability, then we will support Microsoft SQL. That way we can scale up to tens of thousands of workloads with that Microsoft SQL server.

Q4: Most cloud platforms, including VMware will have their own management tools that go along with them. What are the advantages of going with a third-party cloud management tool rather than the vendors, own cloud management tools?

Stuart: There are a number of reason's. One of them is you're free to set your own direction. You're not restricted by what company A or company B think you should do. I see it a lot when big businesses go for big solutions, they get their hands tied inadvertently and also, it's a case of the complexity starts to become overbearing with it.

I just think that the way embotics works is that it's platform agnostic. I could actually attach it to anything. And you also don't find that other vendors support easy API integrations apart from with their own products. vCommander is really, really good in that respect.

Q5: With regard to vCommander, which hypervisor and cloud technologists does the product support, does it support multi-tenancy, and are there different licensing models for different components of the product?

Colin: Supported platforms today are, for on-premise, vSphere and Hyper-V. In the Public cloud, we support Azure classic, Azure resource manager, and AWS, and we are always adding new cloud platforms as customers are adopting them, so stay tuned for additions to that list.

vCommander is is fully multi-tenant, and we have service providers whose business relies on a multi tenant product. One of our customers, Peak 10, has 700 of their clients on boarded in a multi-tenant fashion.

As far as licensing goes, when you license vCommander, you're licensing the entire product. You're going to get automation, orchestration, costing, capacity, reporting. All that is under the one license. We're not going to nickel and dime you for different modules. We try to make it simple and allow you to grow into the vCommander product.

You can watch the complete webinar with Stuart and Colin by clicking the link below.

Watch Now

Topics: Cloud Management Platform (CMP) Webinar Workflow POC Proof of Concept Q&A quotas