Environment as a Service

FAQ

Concepts

Environment as a Service is a common name for products that provide on-demand access to automated environments for different purposes like DevOps, security, demos, training and more

We are all familiar with the terms “development environment”, “test environments”, “staging environment”, “production environment”, “demo environment”. Have you ever tried to look at what is common to them?

An Environment is a collection of components that need to be provisioned, deployed and orchestrated in order to perform a task – like developing, testing, demoing or deploying to production. The environment consists of applications and 3rd party services, deployed on infrastructure, and in some cases also data.

The important thing about an environment is that it is not limited to any single technology – the scope of the environment is the business need.

A blueprint environment is a template that defines all the components in the environment. A blueprint is important because it is an automation plan – it documents everything that is going to happen when the environment is automatically setup. In automation, the value is in re-use. And therefore, the more you re-use your blueprint, the more valuable your automation becomes.

Using blueprints for automating environments makes it possible to unleash the power of automation, while also introducing some guardrails on cost and security. Win-win!

A Sandbox is a time-limited environment which is typically used for pre-production purposes like development and testing, or for evaluating technologies, training and demos. 

Often it would seem quite similar to the production environment – the important difference is that sandboxes are ephemeral and will be torn down after a limited time.

Environment as a Service helps get end-users of environments (like developers, testers, sales engineers and operation engineers) the speed they need without losing control of cost and security.

Many times it’s quite easy to start automating for people with some coding skills, and the complex part comes later – how do we make automation maintainable and scalable? how can distributed teams get access to it? how do we make sure we tear down what we so quickly setup? how do we make sure it’s not abused?

Environment as a Service products help solve these challenges. For the end user they provide all the benefits of automation and infrastructure-as-code. For those responsible for cost, security and compliance – they provide control without becoming a bottleneck

CloudShell Colony includes out-of-the-box plugins for Azure DevOps, Jenkins and Team City, enabling you to easily deploy environments directly from your own release pipeline. It also includes an extensive REST API that can be utilized in any of your existing tools. We continuously release new integrations! Contact us! to discuss supporting your own DevOps toolchain.

Yes! Environments are not tied to any specific technology. Modular support for cloud providers and technologies in environments enables extension for any additional technologies that aren’t already built-in so you don’t need to worry about the next big technology. Automate on!

Yes! Environments are not tied to any specific technology. Modular support for cloud providers and technologies in environments enables extension for any additional technologies that aren’t already built-in so you don’t need to worry about the next big technology. Automate on!

Lab as a Service (LaaS) is an approach for transforming your organization lab to a cloud where users can get self-service, on-demand access to the lab resources, as well as share and collaborate on lab environments in order to support multiple teams and business groups within your organization.

A Shell provides CloudShell users a standard approach to interact with and automate different environment elements, like physical devices and virtual applications. Shells are open source and based on python. In the CloudShell community, you can find certified out-of-box Shells for common technologies, and it is also possible to independently create Shells based on existing standards using the Developer guide.

Shells offer a standard approach that can combine multiple technologies and be shared through our developer community.

Shells and the CloudShell Pro plugin integration are open-sourced. Our integrations are open, based on python, and available in our community integration page. There’s a comprehensive developer guide on the topic of extending CloudShell as well as a free SDK.

CloushShell Pro

CloudShell Pro Shells make it possible to easily offer multiple technologies in environments. Our python Shells are open and available on our community

The Shells part in CloudShell Pro is open sourced. The Shells we develop are all open and available on our community

In the open CloudShell Pro community you can find free Shells and plugins, ask questions, get information, get involved and directly interact with our product team.

CloudShell Pro documentation is all open. You can access it from CloudShell Pro, but it’s also available online help.quali.com

CloudShell Pro integrations include Shells that make it possible for CloudShell Pro to support a wide and extensible array of technologies in environments. It also includes plug-ins to a variety of ecosystems tools like Jenkins, Jfrog, Atlassian, and more. All integrations are free and open-source, and available to download in the community integration page, all available to download freely at our community integration section.

CloudShell Colony

If you’re investing an excessive amount of time in creating, maintaining and debugging environments, you should give us a try! Our mission is to allow all pipeline stakeholders (both human and automated) to create, consume and share reusable environments in a scalable way, support easy debugging and govern the use of cloud infrastructure.

CloudShell Colony is a managed infrastructure-as-code solution. It was designed and built to solve the main pain points of infrastructure-as-code. When modeling your environments with CloudShell Colony, you can focus on defining your application requirements (e.g. artifacts, variables, networking & compute requirements and test data) while we set up the required infrastructure for you, by translating your application requirements into either AWS Cloud Formation or Azure template.

CloudShell Colony is software as a service. So deploying it is as simple as just signing up: https://app.cloudshellcolony.com/sign_up

CloudShell includes out-of-the-box plugins for Azure DevOps, Jenkins, Team City and more, enabling you to easily deploy environments directly from your own release pipeline. It also includes an extensive REST API that can be utilized in any of your existing tools. We continuously release new integrations! Contact us! to discuss supporting your own DevOps toolchain.

Training and Service

Quali offers online and live training options for CloudShell Pro customers. 

User can take self-paced training courses at Quali University https://www.quali.com/university/

Users can access the CloudShell Pro support portal here: https://support.quali.com/

Quali customers also have a dedicated support team including account managers, customer success managers, and support engineers.

CloudShell Colony is software as a service. So deploying it is as simple as just signing up: https://app.cloudshellcolony.com/sign_up