Chronicles of a Wandering Mind - Latest Comments in Vmware Springsource and Hyperic: Brave new world and a lot of questions

Re: Vmware Springsource and Hyperic: Brave new world and a lot of questions

Stickers Printing — Sat, 09 Jul 2011 12:17:27 -0000

nice post berkay

Re: Vmware Springsource and Hyperic: Brave new world and a lot of questions

custom stickers — Mon, 30 Aug 2010 05:53:57 -0000

I am agree with Berkay

Re: Vmware Springsource and Hyperic: Brave new world and a lot of questions

Sticker Printing — Mon, 12 Apr 2010 17:16:12 -0000

I really hope VMWare takes a look at acquiring terracotta as well.

Re: Vmware Springsource and Hyperic: Brave new world and a lot of questions

berkay — Thu, 13 Aug 2009 04:25:38 -0000

Agreed.
VMWare may be able to do more than bare metal jvm OS with Springsource, They can go further app the stack and create something like Google App Engine for the enterprise, without the limitations of GAE.

Re: Vmware Springsource and Hyperic: Brave new world and a lot of questions

Bill — Wed, 12 Aug 2009 17:53:27 -0000

Spring is running on the JVM, just like JBoss etc. VMWare do not have to buy a Java framework to do JVM stuff.

VMWare could do a "bare metal" jvm os, and you could run Java app on top of that. You dont need Spring to do that.

Re: Vmware Springsource and Hyperic: Brave new world and a lot of questions

williamlouth — Wed, 12 Aug 2009 04:27:09 -0000

Actually most of the other vendors such as Tivoli, HP and BMC do provide agents for the Java runtime though in most accounts they are disabled because of the large overhead they generally incur and the poor value delivered by what is collected. Tivoli has probably one of the worst track records in this regard followed by HP. Most customers buying into such products are also buying into the complete ITIL product management suite including help desks, cmdbs, slm, bsm,... which is completely out of the range & possibilities of Hyperic and its team.

You are probably right that Hyperic will target specifically Java now considering that SpringSource had indicated that they were going to do a complete rewrite which follows on from two other complete rewrites by JBoss and Hyperic itself. If a complete rewrite is underway then management would probably look to minimize risk and reduce the scope. That said I would not be surprised if Hyperic is not put to rest as VMware has already invested in tooling around its management console(s).

I still think we are a very long way away from are sort of automated dynamic provisioning until we can accurate collect and model the underlying software and system execution models.

Re: Vmware Springsource and Hyperic: Brave new world and a lot of questions

berkay — Wed, 12 Aug 2009 04:04:25 -0000

William,

Thanks for the comment.Hyperic is typically compared to more generic monitoring tools like the ones I've mentioned above which typically don't have an agent on the box and rely on SNMP or WMI. SIGAR alone is a differentiator for Hyperic.

I understand your argument that deeper and more efficient insight into applications is needed to resolve scalability and performance problems (like provided by Jinspire)

By assigning CPU and memory, I was referring to elasticity rather than scalability/performance problem originating from the application. In a VMWare box with 32 CPUs and 128GB memory hosting multiple JVMs, VMWare can potentially change allocation of CPUs and memory to applications based on the load for each app, making better use of the available resources.

Re: Vmware Springsource and Hyperic: Brave new world and a lot of questions

williamlouth — Wed, 12 Aug 2009 02:45:53 -0000

"Hyperic is different than other solutions in the market it’s competing."

What exactly are you referring too? Hyperic is complete void of application interactions and largely relies on process level metrics (no context, no interaction, no activity chain, no correlation) published as MBeans and instrumented by developers of applications and technologies within the stack.

Assigning more cpu does not at all solve a scalability or performance problem in the cloud unless your are aware of the nature & profile of the activities (io bound, cpu bound, mixed) queued and how they interact (bottlenecks) with each other in competing for resources.