This is the storyplot of a company that made a decision to become a Cloud COMPANY. These were already an effective IT outsourcer in the financial industry, numerous customers’ environments running in their data middle. Outsourcing was a wholesome business but they started having some difficulties, due to slow and inefficient provisioning procedures and processes.
Any new request from a customer started a new project, so their customers started exploring public cloud services to get more versatility and speed. For this good reason, the company made a decision to adopt the cloud delivery model and also to offer their customers a self service catalog. Of course a cloud project can’t be done in a single night, so they were cautious in their approach.
Both technology and operational processes would have to be proven before embarking in that challenge, but the traditional waterfall technique made the expected come back show up distant and uncertain. To make things worse, that they had tried to implement a PaaS project with a different vendor plus they had spent big money without tangible return.
I was involved to aid the evaluation of a fresh IaaS catalog that could develop to PaaS and also to self service applications management. I ensured that the Business and IT strategy were in sync and I proposed to start with small steps to validate the approach. I also invited them to meet the criteria the quick wins that they would expect to justify the investment and show the stakeholders an immediate return, so the project resided to reach the expected success enough.
As you understand well, many tasks last too much and pass away before displaying any business come back. We analyzed the current situation and defined another vision. This was the drivers for a distance analysis and for the prioritization of user stories, that we decided to apply in short iterations (sprints of 14 days, according to the Agile Scrum methodology).
Their data middle was mainly predicated on Cisco networks and machines, but this is not the primary reason behind selecting the Cisco software stack for the cloud task. The Cloud Management Platform chosen for the task was the Cisco ONE Business Cloud Suite (aka ECS). One of the most important features considered in your choice was the likelihood to create flexible templates, open as personal service options in the end user catalog later, for the deployment of complicated applications. A set of machines with different functions, and everything the networks had a need to make them work, can be provisioned as a separate and practically separated environment (multi tenancy in a shared infrastructure that offers economy of size).
- Amount in request………
- General Non-fiction
- How does the written text distinguish between firm’s financial structure and its own capital framework
- 403 Computer services revenue25,659
- Strong organizational skills with high level of attention to detail and precision
As a good example, the following picture shows a environment that might be ordered – fully configured – with an individual click. This model-based execution is quicker to create and simpler to maintain, and it could be exposed to the finish users in a manner that they understand and trust soon.
Delegating the configuration to an automatic service gave their customers a faster service and a higher quality (no rework needed because of manual mistakes or missing information). One more element in the architecture is the Stack Designer. It is an instrument provided by the Cisco ECS to generate templates for application provisioning. It requires IaaS themes – manufactured in the infrastructure management coating, that in our case is UCSD, to deploy a topology of servers and systems – and layers the software stack on top of them.
You can decide what software products (or custom applications) must be installed – and configured predicated on the input parameters provided by the end user – including monitoring agents and backup brokers, and save this new template in the repository. The integration with Puppet, an open up source solution used to provision applications, is leveraged to set up and configure the entire software stack from the images in the repository.
The new template can now be offered as a self service option in the catalog, so the end users don’t need to install and configure the program stack themselves. A end-to-end solution is provided, and working and prepared to be used up. All the components of the ECS solution are pre-integrated which makes the project faster than you would expect.