Singing to the Tune of Sandboxes

Posted by Pascal Joly October 6, 2016
Singing to the Tune of Sandboxes

Next week Quali will be in San Diego for the Delivery of Things conference hosted at the Hard Rock Café downtown San Diego.
I will be presenting on Thursday October 13th at 12pm about Sandboxes as a Service, on how to accelerate the deployment of application infrastructure in the CI/CD pipeline.
In the continuous integration cycle, developers and testers need to quickly deploy new builds onto a set of changing infrastructure components that should provide individual replicas of the production environment.
A plethora of infrastructure orchestration solutions such as Chef, Ansible, Puppet, Openstack Heat, AWS CloudFormation, Docker Compose are available today. However the management and automation of advanced application environment templates remains a piecemeal approach, thus impacting the overall velocity of the application delivery lifecycle. Key components such as security tool, test tools or data store configuration often remain manual tasks.
Cloud Sandboxes can address these limitations by offering an out of the box simplified experience for the blueprint designer while integrating with all the required components to automate accurate replica of the production infrastructure.

If you want to learn more about an innovative way to solve a complex DevOps challenge, make sure to attend this session. By the way, we'll have a booth as well over the duration of the conference. So if you're going to be around , stop by and Hans, our Technical Marketing Manager (and an accomplished guitar player) or myself will have the pleasure to give you a demo.


Streamlining proofs of concept with a self-service demo cloud, part 2

Posted by admin October 5, 2015
Streamlining proofs of concept with a self-service demo cloud, part 2

The first half of this series examined how a demo cloud solution can streamline field tests and proofs of concepts for technology manufacturers, service providers and independent software vendors. Whereas traditional PoCs processes can end up crunched between demanding requirements (i.e., that the solution being demoed work across complex, multi-vendor environments) and shortages of power and cooling resources, as well as space and time, a demo cloud can deliver infrastructure-as-a-service, with commonly used demo environments available through a self-service interface.

"Hosting PoCs in the cloud is a natural fit, allowing the ISV to focus on closing business, without having to worry about the provisioning of hardware and configuring the networking," explained Citrix documentation on the advantages of a demo cloud. "The proof of concept process is greatly simplified; a working demo can be up and running quickly, and prospective customers can see exactly what the experience would feel like for a user.
A significant portion - at least 35 percent by some estimates - of all demo equipment is wasted and/or unproductive, creating a strong business case for streamlined demo clouds that can deliver higher utilization and greater ease of use and ultimately yield shorter and more efficient sales cycles. In this part 2 of our series, we'll wrap up our look at what  demo clouds should provide in order to reduce costs and improve sales cycles.

Streamlining proof of concept testing with a demo cloud
Over time, PoCs often go beyond the basic demonstration of features and come to encompass advanced functional and performance tests. Such tests may require control over the physical connectivity - i.e., by using Layer 1 switches - to ensure accurate network performance. In addition, more complex demos and PoC can typically require control and provisioning of other types of equipment and gear such as traffic generators and custom appliances. Supplying this level of high-fidelity support for demos and PoCs can be challenging because of the range and complexity of infrastructure that needs to be provisioned. However, this is a critical requirement if a demo cloud is going to effectively replace the traditional approach to lugging gear around.

Moreover, an ideal demo cloud, as we noted last time, should easily integrate with management software platforms via APIs, have robust reporting and accounting features, and exhibit highly scalable, maintainable automation. It should have flexible administration and access privileges suitable for many types of users - e.g., developers, systems architects and power users - and ultimately enable non-programmers to create demo environments and leverage prepackaged libraries without having to write their own scripts.

With these requirements as well as those listed in Part 1, the following are key capabilities needed by a cloud solution for enhancing the PoCs process:

  • Scalable environments driven by user input: Engineers can reserve and then extensively customize their environments, with particular input forms that determine orchestration and provisioning. A single catalog can in effect support many different use cases and topologies.
  • Object-based design: Automation workflows can be built with objects that cover provisioning as well as infrastructure resources. Plus, the object library can be dragged and dropped by non-programmers for easy workflow creation.
  • Abstract resources: A system using CloudShell can pick any available resource in order to maximize availability and utilization during the demo.
  • Comprehensive reporting: Administrators can easily keep tabs on device utilization and reservation-to-activation ratios and construct custom dashboards for high-fidelity PoCs.
  • Power user support: Power users can make the most out of CloudShell by doing live customization of environments and creating ones from scratch if need be.

CloudShell is the cloud automation platform purpose build for creating demo and PoC clouds that yield smoother, more efficient PoCs and field tests by simplifying the creation, customization and teardown of environments. As a result, field sales organizations can shorten their sales cycles and remain competitive.

The takeaway: For years, PoCs have been beset by issues with inconsistent resource availability and underutilization of equipment that serve to undermine the demonstration of solutions in complex, multi-vendor environments. A platform like CloudShell creates a demo/PoC cloud with IaaS that can deliver common demo/PoC environments and streamline the process for end users.


Streamlining proofs of concept with a self-service demo and PoC cloud, part 1

Posted by admin March 20, 2015
Streamlining proofs of concept with a self-service demo and PoC cloud, part 1

For technology manufacturers, independent software vendors and even service providers and technology manufacturers, demonstrations and proofs of concept are a critical step in the sales process.  Demonstrations illustrate relevance, while PoCs establish that a given technology, product or service fully satisfies the buyer's particular requirements.

"When capturing a new sale, time is often of the essence," explained a piece of Citrix documentation about utilizing the cloud for PoCs. "Software providers have a finite amount of time to capture customer mindshare, and the competition is trying to beat them to it. Spinning up a customized working demonstration in minutes - versus days or hours - could mean the difference to winning the [purchase order]."

That's the ideal. In the real world, however, PoCs often run into significant challenges and obstacles that result in delayed and sometimes missed sales opportunities:

  • Since demonstrations are about showing relevance, they need to representative  of the customer's environment to speak to the use case.  This creates the challenge of significant prep time for sales engineers to create the right illustrative scenario.
  • Evaluators hold PoCs to a higher standard, as they are trying to certify the solution's technical capability to meet their list of requirements. Accordingly, there's little margin for error.   So engineers are challenged with even more preparation work to construct the environment inclusive of testing tools, etc. that will accomplish the PoC goals.
  • Beyond those challenges, there are real obstacles to delivering timely demo's and PoCs, especially when the infrastructure environment for the product, application or service is complex:
    • First off, if the PoC requires shipping equipment to customer sites, then the process goes down a path littered with potholes.  Huge, costly supplies of products must be maintained in a depot to meet demand.  Equipment wastes most of its time depreciating in the depot, in transit, waiting at the customers' receiving docks, waiting for customers or sales engineers' schedules to align with maintenance windows for installation.  Perhaps 10 percent of equipment is lost, broken or held hostage to customer issues that have nothing to do with sales processes.  In addition, PoCs are easily interrupted due to scheduling problems.  As a result, effective utilization rates for PoC equipment is dismally low.
    • If demo's and PoCs are delivered from a central lab, in most cases the processes for setup are highly manual, which again squanders tons of productive time.

Using a demo cloud to deliver cloud-based, self-service demonstrations and proofs of concept
Demonstration and PoC clouds can address these shortcomings and make life easier for both sales teams and prospective customers. An efficient demo and PoC cloud can, for instance, eliminate the steep capital costs and logistical pitfalls of traditional field-based PoCs and improve the operational efficiency, remote usability, agility and responsiveness of central lab-based PoCs.  Such an infrastructure-as-a-service cloud solution can deliver commonly used demo and PoC environments to teams in the field. The result is shorter sales cycles and increased opportunity pipeline.

A streamlined user experience is imperative when working with a demo cloud. A solution like QualiSystems CloudShell offers the essential features for demo/PoC cloud automation, including:

  • An accessible self-service portal that offers a predefined catalog of demonstration and PoC environments, along with options for power user customization and a reservation system to avoid scheduling conflicts.
  • Dynamic environment provisioning with support a broad range of user inputs, plus automated de-provisioning to return resources to a predictable baseline state.
  • Ability to handle complex demo scenarios, such as ones that go beyond software-only considerations and require the design and publication of complex topologies involving hardware products.
  • Automation reusability, with limited scope objects and a visual orchestration authoring tool.
  • Reporting and accounting so that teams can keep tabs on key performance indicators such as maximizing resource utilization.

Ultimately, a demo/PoC cloud should accelerate the sales process and eliminate the common causes of delay. With deep integration of workflow automation and resource management, a solution like CloudShell also produces significant CAPEX and OPEX savings through increased efficiency and productivity. In a future post, we will look in greater depth at how some other specific demo cloud features lead to easier field tests and PocS.

The takeaway: As tech and telecom sales organizations look to speed up and shorten their sales cycles, they will need to overcome the logistical and productivity blocks to meeting customer demands for demonstrations and PoCs. Using IaaS to offer access to common environments, they can overcome the hurdles that beset PoC testing and prove that products and services can operate across complex, customer-relevant infrastructure environments.