CloudShell Environments-as-a-Service Overview
•
0 likes•75 views
- Quali is a B2B software company that delivers IT environments as a service to accelerate digital transformation initiatives for enterprises. - Their CloudShell product automates and orchestrates complex hybrid environments across physical, virtual, and cloud infrastructures for self-service use cases like development, testing, demonstrations, and more. - CloudShell provides blueprint modeling, a catalog of 130+ pre-built integrations, analytics and reporting, and a single-click deployment process to quickly provision environments on any cloud.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to CloudShell Environments-as-a-Service Overview
Similar to CloudShell Environments-as-a-Service Overview (20)
More from Shashi Kiran
More from Shashi Kiran (9)
Recently uploaded
Recently uploaded (20)
CloudShell Environments-as-a-Service Overview
- 1. CloudShell Environments-as-a-Service Shashi Kiran and Roni Dover www.quali.com
- 2. Quali Environments-as-a-Service B2B automation and orchestration software company that delivers IT environments as-a- service accelerating digitization initiatives Company Investors –Dell/EMC, Evergreen Venture Partners and Gemini (Israel). Offices in Santa Clara, CA and Ganey-Tikva (Israel) Customers ~150+ Enterprise and Service Providers including Fortune 1000 and Global 100. 4 of 5 US Cloud Providers, 8 of 10 Telcos, 3 of top 5 banks, 2 of top 3 credit card companies.
- 3. Environment Friendly :-) 01 02 03 Dev/Test Engineering and IT Infrastructure DevOps and Cloud Demo/POC Sales/Sales Engineering and Marketing Customer Support Cyber Security Security and Compliance Cyber Ranger Innovation Velocity Sales Acceleration Security and Compliance
- 4. Complex and Dynamic IT Environments Impede Digitization “I can’t test or QA anything until I have access to everything!” Your new mobile app! SecurityData Center Systems Cloud/ Microservices and Containers Data Middleware Partner/ External API Integration API
- 5. Production Vs. Pre-Production Environments Best Effort Investment 80% Resources Lost Productivity. Increased Time-to-Market Manual and Non-Standard Workflows Fragmented Toolsets Higher Investment and Focus 20% Resources PRODUCTION PRE-PRODUCTION How do you Increase Productivity and Efficiency Across the Entire Lifecycle?
- 6. Traditional Environment Delivery is Challenged IT Ticket IT Fulfilment Rack, Stack, Validate (Fragmented Tools) Consume DAYS / WEEKS / MONTHS!! (Wait Time) Design
- 7. Enterprise Demand a Better Experience No 33% Yes, but no self service 34% Yes, self- service 33% Cost 20% Complexity 41% Compliance 18% Risk 12% Other 9% Automation In Dev/Test Barriers to faster Cloud Adoption >1 month 24% <1 month 49% <1 day 27% Time Taken to Deliver And Provision Infrastructure to Users *Quali 2017 survey Survey of 1300+ Enterprise Responses
- 8. Re-thinking Environment Delivery via Self-Service
- 9. PauseIncrease Efficiency via Save-and-Restore
- 10. Play on any Device Bare Metal PUBLIC/PRIVATE/HYBRID Simple “One-click” Deployment Path Flexibility to Deploy on any Cloud
- 11. ENVIRONMENT Model and Orchestrate (Designer friendly) Rich Modeling – GUI or 100% REST API Powerful Physical/Virtual Orchestration of Full Stack (Layer 1-7) Flexibility of Cloud 1
- 12. Insightful BI and Analytics (Admin Friendly) Cost Metrics For Better Control Resource Utilization Metrics 2
- 13. Self-Service (User friendly) Designed to Collaborate Highly Customizable with Fast Provisioning Reservation and Scheduling Demo Team (9) 3
- 14. CloudShell Product Family 14 • Flagship product • Hybrid and Multi-Cloud • Orchestrates physical and virtual environments On-Premise & Hybrid Cloud PRO • Lightweight version • Single Cloud • Orchestrates virtualized environments Virtual Private or Public Cloud VE Bring Your Own Infrastructure or Cloud Beta Trials for SaaS Product Underway (Invitation Only*)
- 15. Quali CloudShell – A Deeper Dive
- 16. Developers Testers IT Ops DevOps Tools CloudShell – Conceptual Architecture Public Cloud Data Center/ Private Cloud Orchestration Self-service portal Environment-as-a-Service Sandboxes BI/Analytics Visibility
- 17. Workflow Designed for Collaboration Launch Sandboxes “User” - Team Member (Dev/QA/Support/Ops/Sales/ Marketing/Security Publish Self-Service Catalogs Administrator/ IT Manager Design Blueprints Architect (Dev/Test, DevOps/Cloud, Security)
- 19. Blueprint Components Applications Data Physical Infra. Virtual Infra. Services Network Storage Compute Security CLOUD SANDBOX L1-7 FULL STACK ORCHESTRATION Test Tools Blueprint Designer
- 24. CloudShell Community Image and artifact repositories Develop new Integrations “Out-of-the-box” Applications The application catalog can draw from many public, private and open-source repositories Blueprint Designer
- 25. Physical Resources “Cloudification” Blueprint Designer BUILT-IN RESERVATION AND SCHEDULING
- 26. 130+ “Out-of-the-Box” Community Integrations
- 27. Hybrid Environments ENVIRONMENT Database on Premise Secure Connectivity Applications and Public Cloud IaaS Blueprint Designer
- 29. Harness BI and Analytics Cost Metrics For Better Control Resource Utilization Metrics Administrator/ IT Manager
- 30. Deploy Sandboxes on Any Cloud “One-click” Deployment Path User/API
- 31. Environment Automation for CI/CD Pipeline Quali Sandbox Environments Load Security Integration Staging/ Production Dev User/API
- 32. DEMO Azure DC/Private Cloud Hybrid Cloud Environment DevOps CI/CD over Azure On-premises Physical/Virtual Resources Public Cloud
- 33. Three Vectors For Scaling DevOps and IT Automation Agility Accelerating releases, leveraging automation within the pipeline to remove bottlenecks Cloud Control Enjoying the power of hybrid cloud infrastructure without losing control Adopting Self- service Approach Providing environment- as-a-service, supporting multiple users, projects and use cases: dev/test, prod, support, demo
- 34. Stay tuned for more….
Editor's Notes
- https://pixabay.com/en/accomplished-achievement-agreement-3441041/
- Bird’s eye view CloudShell fitting into the overall process Bring your own cloud Manamgement layer over cloud resources CMP with DevOps and IT ops in view
- I’ve been working with many origanizations helping architect solutions for DevOp and Itops and there are ways are three main roles that emerge as key personas in moving the organization forward in scaling the operation. These roles may sometimes overlap Go through each one. I should note that a lot of times the roles come in conflict. The developer wants to progress as fast as possible, the architect wants standard environments, and the administrator does not want to give up control CloudShell helps resolve that by being one transaparent platform serving all three. From that perspective, let me introduce how CloudSHell as a product and platform fits into the picture for each of these personas
- We start with the designers. Simply put CLoudShell provides a more effective way to develop design and create reusable architectures or blueprints in CloudShell terms. I will illustrate more on that on the demo, but they key here is that CloudShell provides an almost vizio like platform in combine different building blocks and connect them into usable enabviornments.
- So what is in an environment? So from CloudShell’s perspective the short answer is ‘everything you need set up and ready to start working’. This includes any infrastructure being allocated and provisioned, an isolated network for the environment in whichever public or private cloud you are using ensure it doesn’t interfere with other activities Connectivity inside the environment and between its components And then climbing up the stack, configuring the application layer, getting the right data for the environment, setting up test tools and orchestrating other cloud native or Saas services I want to drill down into some fo these components to illustrate how the full stack approach is reflected in our solutions. Lets start with the application.
- Cloud agnostic – multiple deployment options support Dynamically map application to infrastructure Provide end-to-end orchestration from infra provisioning to application configuration Utilize public cloud marketplaces
- Cloud agnostic – multiple deployment options support Dynamically map application to infrastructure Provide end-to-end orchestration from infra provisioning to application configuration Utilize public cloud marketplaces
- Cloud agnostic – multiple deployment options support Dynamically map application to infrastructure Provide end-to-end orchestration from infra provisioning to application configuration Utilize public cloud marketplaces
- Cloud agnostic – multiple deployment options support Dynamically map application to infrastructure Provide end-to-end orchestration from infra provisioning to application configuration Utilize public cloud marketplaces
- After discussing virtual and cloud assets, let me talk for a minute about
- Treating it as a cloud I know it sounds presumptuous but to me it means simply not caring about where the resources come from. Allocate resources to users Provide access control and scheduling Spin up virtual resources as needed and de-allcoate when done Transparent hybrid connectivity Support abstract requirements
- Same as with apps, the CloudShell community contains numerous out of the box integrations or Shells as well call them. This ties in to our building block based architecture as any shell imported into CloudShell can be dragged into the visual designer be used in defining the architecture of the environment.
- We talked about Physical and virtual/cloud resources. CloudShell also provides the orchestration to make it transparent to design hybrid workloads. Behind the scenes, VPNs, routers and firewalls can be orchestrated so from the end user experience it doesn’t make any different which appliance is virtual and which appliance is physical. Once we have the complete environment, we can move away from the blueprint designer persona and see how the other roles fit in.
- Environments, once done, are posted to the self service catalog. Here the administrator and manager can apply policies and regulate how resources, private and public cloud can be used How which environments are available to whom and for how long Which clouds are accessible to which group.
- From the other end, the administrator has complete visibility into who’s using which environment. Because Cloudshell connects users to environments to business use cases it provides infrastructure with the context of the activity its used for And that can prove really valuable in understanding resource utilization and cloud consumption
- Finally our user, the SE, developer or testers has a very simple interface to create What we call a sandbox – an instance of that blueprint which exists for a specific duration for a specific activity.
- Of course a user isn’t always a person accessing a web browser, we view API access, CLI and other tools integrating with us as Additional ‘users’ Here is an example we’ll touch more on in the demo, we have sandboxes being used throughout the CI/CD pipeline and the dev/test/deploy cycle
- I would like to summarize with what I continually as the main challenges of Scaling DevOps and IT It seems everyone is moving on three different vectors that are hard to reconcile – adding more automation, adopting self service and at the same time keeping control of cloud expenses and resource utilization CloudShell has the advantage of being a platform that provides a solution which looks at these as one unified problem set while providing transparency between the different roles that helps break silos and increase collaboration
- So we are working on some really exciting and innovative features around DevOps and DevIt that we will soon be announcning. This is really excited and I hope to be able to talk more about these sson.