Not quite as cleanly as you’d hoped it would be..If your constituents have to think about this for longer than a second, you’ve lost your attractionMeans More workload complexityMeans more challenges in meeting SLAsMeans more Cost without proactive management
Only achievable through reduced support needs and automated tools.
So we will stay aheadof the curve by staying up with the latest API’s and disparate technologies that are missing the common control plane.Tech vendors have moved to UCS and VMware lead the way, and even storage with high availability component, and the elasticity that cloud is driving – vendors had to move to a smarter and more converged technologies, and along with that a smarter way of managing these systems. So management has to be able to transverse the nuanced differences between the multivariate vendors. The UI’s and API’s keep changing from these vendors. Dell is a classic example – moving away from host-based agent delivery manage to look at fans, CPU< power supply, cooling and etc. HP did the same thing in their server base mindset. Fast forward to 2012 with dynamic compute environments with systems being spun up and down – there is overhead to every time you add an agent and within Linux there are too many flavors. So Dell gone toward out of band mngt and ID drive system so you can find out temperature even when the box is down – did that by packet over Ethernet. So moved to an off-box independent monitoring element that works for the dynamic datacenter. This means that the WMS-API, we have partnered with Dell. It is the monitoring aspects that highlight the new features of the hardware – without which you ask the means to make decisions and run the business more effectively. Erik to send my iDRAC deck.Out of band monitoring = a physical card. They built a separate control board that sits in the server and its power source is power over Ethernet so if network is up, they can communicate to the device and device can figure out whether the box has power, its state, its configuration including RAID and storage and etc. it’s the converged model – vendors are moving to these new dynamic architectures that require much more detail that just polling an agent.Also – ScienceLogic is seeing more and more of a need to be agentless in nature – there are use-cases in the cloud where agents become potentially more helpful. Ultimately we want o support both – but we see being agentless in order to scale. This is also the story tat we can drive with PowerShell – not the model to put agent into the server (which is Nimsoft’s model) – we want one to many CMDLT. We want to be less dependent on the agent and traverse different security boundaries using the model. Look at Windows slide 13 – windows gateway system that does the traversal into the active directory domain.POLL: Ask before slide 4What do you believe are the most important assets that make you attractive to customers/ What differentiates you from your competition? What makes you attractive to your customers? - PriceValue Added Services SupportSystems Architecture Taking you into the next growth oppty that revolves around SmartIT services (a higher plane of services than the traditional infrastructure-centric services). Evolution example: people used to buy colo and you put your server and OS into it. Then came hosting – where SP would do the bare metal. Then came virtualization, and MSP would do mngt and patching – but user would do day to day care and feeding of the application without owning/worrying about the OS/server. Now where we are going as a SP – in order to compete, you need to think beyond just a hosted exchange offering, and more of as a Mail as a Service offering. Even the UCS will begin to look and feel like running youe standalone server and become commoditized. Need to take out more human element. Even the apps like exchange server that moves – you are going to face the exact same problems of patching, monitoring and etc. but added to this is going to be the addition of orchestration and automation. Beyond spinning up infrastructure – focus should be on customer services. 2 things coming: 1) tail-end is orchestration – automation and orchestrate new customer services (add, move, delete). More self-service of commoditized services, limiting human intervention of provisioning customer services and change mngt – driven through service origination form. E.g. is how gmail allows you to create the acct. Drivers will be price, ease of usage,
Multi-tenancy (Core Competency)Broad range of Data Collection (Core Competency)Root analytics against performance data (Core Competency)High Availability/Resiliency (Core Competency)Support & ServicesPre-integrated Service desk, Asset, DashboardsAutomated Discovery/Correlation/TroubleshootingAsset ManagementEase of Deployment