Microsoft Azure, 360, Windows – Powershell capabilities.
AWS use-cases.
Unified converged infrastructure.
1) Because of the Promise it holds.
Unified Service Provider
The Issue with the model is that it does not take a Multi-Cast scenario into account, whereby significantly more expertise are needed, and more efficiency gained.
Unified Service Provider
Courtesy of www.funnyordie.com
Dilbert slide + Simpson slide.
ITSM- it’s about the federation of cloud, the multicloud, the hybrid cloud – ultimately it is about the unified service layer.
That means that enterprises want to push more of the commoditized aspect of the cloud to their trusted advisor – and having visibility and control through that unified portal. It also means going higher up the stack – and looking for service and sub-service views rather than component and device views.
Unified Service Provider
Keeping Hosting.com Future-proofed
True™ Multi-tenancy: Highly automated, multi-tenant capabilities were built from the ground up providing multiple levels of view segmentation, by user profile, customer profile, geography profile, technology profile, and many other profiles.
Ability to customize dashboards: Intuitive, smart dashboards can be built in 90 seconds, are easy to use and understand, and always updated with the latest information.
Real-time visibility: Reports, analysis, and maps show problems immediately for quick correlation and issue resolution.
Scale: ScienceLogic’s appliance based products are able to easily scale in parallel with Whoa.com’s high growth expectations using super-efficient, built-in upgrade options.
We have helped WHO create the Bentley of Cloud services.
Similarly we work extremely closely with our friends are Cisco, NetApp, VMware and Citrix – with whom we are all partners, and have tight integrations. The open architecture provides automated integrations already established with dozens of other technologies Whoa.com relies on. And we purposefully picked these best of breed partners because of their ability to provide very robust and powerful APIs, exposing incredible details of instrumentation – we have hundreds of powerapps just for the Cisco devices for example. So just like your smartphone provides your with a choice of apps, and context that you’re looking for, so we do the same.
Keeping Hosting.com Future-proofed
Aligns to Hosting.com Vision.
New Powershell content
12 Power-Packs
87 Power-Apps
As an example of how we’re getting there: 724 Collection Objects – this is critical as it’s more objects and metrics than anyone else in the monitoring and management space.
51 Thresholds
114 Event Policies
Windows Server
Windows Event Logs
Exchange Server
Lync Server
SQL Server
Hyper-V Server
SharePoint Server
Active Directory
IIS
DNS
DHCP
A better way to monitor Microsoft Windows systems and applications
A new PowerShell transport mechanism leveraging Windows Remote Management (WinRM); a native Microsoft Windows capability designed for remote management
Many backend enhancements for performance and simplified dynamic application development
A new credential type
This is opertaional big data.
Unified Service Provider
Also in our surveys, when we ask about trusting the cloud – both for reliability and security – it’s notable that people who do NOT use cloud trust is much less (around 6 out of 10 for reliablity and then 5 our of 10 for security) vs. people who use cloud (7 out of 10 and then around 7 out of 10).
SaaS leads usage, but we’ve seen an increase in IaaS and PaaS usage since 2011.
This is talking about how much spoon or fork you want – needs disocervoery and consideration of risk etc.
CloudMapper gives you a single view, of your converged infrastructure, across multiple technologies, and with the ability to drill down to any part of the technologies, wherever it resides, whether it’s internal infrastructure, private cloud data centers, or resources in the public cloud, such as on Amazon Web Services. We cover them all. [CLICK]
Unified Service Provider
This scenario is where a user decides to fire up some EC2 instances. When creating the EC2 instances, the user has the option to say how many EMR (Elastic Map Reduce – uses Hadoop to process large amounts of data) instances they want to spin up with the EC2 instances, they select say 3 and everything fires up. Fast forward a period of time and the process finishes. More often than people would like to admit they will shut down the EC2 instances but forget about the EMR jobs that are sitting in the background having run. This results in what I am calling a "lone wolf" syndrome and there are several EMR jobs, not running, sitting out in the ether costing the company money for resources not being used. Yet no obvious way to detect that they are sitting out in the ether once the EC2 instance has been removed.
With SiLo if you have an EMR job tied to an EC2 instance you'll see it and if you have "lone wolf" you can see that as well, when you view a topology of a VPC (virtual private cloud). It'll just be hanging out. So you can save a fair amount of money by detecting your unused EMRs and RDSs and terminating them.
In many cases, organizations will have multiple VPCs each with its own set of security policies. Service Providers may have hundreds, possibly one or two for every one of their clients. When deploying an instance in AWS you can select from the list of available VPCs. It is quite likely that human error will come into play and you will deploy to the wrong VPC with the wrong security settings. There could be a whole host of security challenges with this scenario or compliance issues. Once deployed, it isn't easy to tell if all of your instances are deployed in the correct VPCs. However, using our dynamic device groups, if you have deployed from an organization, you can quickly see that, for example, an instance is deployed aligned to the right organization but the wrong VPC.
An organization may choose to deploy a number of load balanced EC2 instances across multiple regions and multiple availability zones. Because of Cloudwatch's limitations you can't see a load balanced group across regions and instead would only see EC2 instances per region. This can be a problem because you could have poor performance from your load balanced group but have difficulty seeing which EC2 instances were the culprits. With CloudMapper, you can see in one dynamically updated map all of your load balanced EC2 instances across all regions and could in a matter of seconds detect which of your EC2 instances were causing your load balanced group to have issues.
Imagine you have a number of availability zones and a number of Amazon users. The users are merrily instantiating Amazon instances of the services of their choosing and during the deployment of those services they are asked which availability zone they would like to deploy to. The go with the default and merrily move along. Initially this may not be a problem, but over several deployments the potential for lost money and a greater amount of Risk develops. What may result is instances only in one availability Zone which happens to be the most expensive availability zone. So you have two problems, a great amount of risk because all of your eggs are in one basket, and wasted money as a result of defaulting to the most expensive availability Zone. Currently it isn't easy to see, across all of your accounts and users where resources are deployed. With SiLo all of that will be automatically detected and tracked for you using the CloudMapper. So you can see instantly which availability Zones your resources lie, and whether you can expect increased risk/cost based on that allocation.
We have a lot of parity with Cloudwatch from a billing perspective. Where it gets interesting is when considering trends over time. Since Cloudwatch doesn't keep metrics for a long period of time, it is difficult to track which Availability Zones have a greater likelihood of outages. So you can imagine a scenario where you have the same price for deploying a particular Amazon service in 2 different availability zones but Zone A has a much greater history of outages so it makes sense to deploy in Zone B. Without us, you wouldn't know that and could continue to spend money and deploy to Zones that don't provide the best performance for your dollar.
As an application owner in an enterprise, or as a service provider offering an application as a service, I may want to use Amazon on occasion to offload some of my work. Currently there is no way for me to view the service across both my offsite Amazon resources and my onsite resources in one view. Further, providing that view to my clients is impossible. What we allow with AWS and CloudMapper combined is the ability to (as you know) see an entire service, all of its supporting elements, as well as all of the instances supporting it in the public cloud. Currently they can't do this and would have to view the service from CloudWatch and then their onsite tool, and wouldn't have a holistic view. For example, they could look at EC2 instances in Cloudwatch, but really wouldn't see a correlation with the application running on top of those instances. We give that to them. Further, since no one (other than partially Zenoss) offers the "relationship detection" bit, application owners and service providers can't see how their storage relates with their compute (for example). Further, Zenoss doesn't offer this capability when it comes to a hybrid AWS environment.
So, to summarize this use case, an application owner can't see all of the parts of a service (if it is a hybrid service) or all of the instances of a service (if they have deployed some of the servers running the application along with the storage in AWS and some of them + storage in their own DC). This presents a pretty good challenge if, say, the application being offered as a service based in AWS experiences an outage. He wouldn't know unless he logs into both Cloudwatch and his onsite NMS Tool and monitors both. Further, a service provider offering this service, can't provide a dashboard for their client covering their application and its capabilities.
Unified Service Provider
Today and tomorrow? The underlying cloud providers are becoming compliant!
Going back to the original difficulty that most of these business consumers are faced with – they are demanding not just a serious Hybrid solution, but a multi-cloud environment that best suits each of those business services
Who are their trusted advisors?
Hosting Providers are proving to be the most popular trusted advisor in this process
You, Mr Hosting Provider, become the captain/the orchestrator of the plan.
Unified Service Provider
7 Year Plan to migrate to Public Cloud
Starting with greenfield apps
CIO Concerns
Security
Cost Management
Visibility
Performance & Availability
Managing Hybrid IT
Collapsed planned time to Migrate
7 years down to 3
Cost savings calculated in $m’s
Support for Hybrid IT
Cloud first initiative
Increased Infrastructure Coverage by 500%
5x coverage of infrastructure with 1/5 the FTE requirements
Saving > $2 million
Calculated savings of over $2 million even while factoring prepaid license costs on previous system
Outsourced to HP and Xerox/ACS
No visibility at all..!!