Biggest Disappointment About vSphere 5.5 New Feature AppHA (Application High Availability) by Veeam

By admin, September 23, 2013 10:39 am

Just read the following in the latest Veeam Community Forums Digest and it’s quite interesting.

In fact, I use a much simpler method in Windows environment, I simply set the particular services to restart by itself should there be any failure, it worked perfectly so far, no hassle at all. :)

You may remember after sorting through all of the vSphere 5.5 features a few weeks ago; I was most excited for the vSphere AppHA (Application High Availability). Well, I have to admit it turned into my biggest disappointment based on some hands-on experience.

The theory behind this feature sounded excellent: in addition to vSphere HA (high availability) that VMware provided for a few years now (VM monitoring, with automatic VM restart after VM or host failure), the same will now be possible at the application level (application monitoring, with automatic restart of services and/or VM in case of application failure). And because this will be built right into the platform, it’s going to be transparent and easy to use… or so I thought, based on years watching VMware dishing out incredible functionality that was always integrated, intuitive and “just worked”.

I assumed VMware will simply “enlighten” VMware Tools with the ability to detect known applications and monitor key metrics, and also make this framework extensible for custom applications (similar to pre-freeze / post-thaw scripts for application-specific snapshot logic). In case of application failure detected, VMware Tools would throw events into vCenter and first attempt “local” recovery by restarting services, and if that does not help, message vCenter to restart the VM. This architecture would make AppHA work out of box for every VM (including newly added), with zero hassle for admins: huge value that EVERY user would immediately benefit from.

Well, it appears that I assumed too much. In reality, the feature comes with incredible complexity, and is based on legacy architecture I would not expect leading virtualization vendor to release in 2013. First, this feature is not something built into the platform, but rather completely “glued” on top of it. Before you can even start using this feature, you will need to deploy two separate appliances… yes, one was not enough! The first appliance is Hyperic appliance (recent VMware acquisition), which is Microsoft SCOM like tool with ugly web interface (carrying maybe 10% of SCOM functionality), and sporting identical architecture (thus bringing 100% of SCOM complexity along). Second appliance is actual VMware AppHA appliance, which seems to orchestrate “stuff” between Hyperic server and vCenter Server.

And the “best” part? AppHA requires that you deploy special monitoring agents in every VM, so welcome back to the agent management fun we’ve made great strides to avoid (having to remember to install, upgrade, and babysit yet another agent in your VMs). And even worse, you will also need to ensure that every VM is accessible to Hyperic server over the network! Direct network connectivity to a VM from core infrastructure servers? What’s up with that, I thought cloud was all about complete isolation? In other words, just think about all the things you like about agent-free Veeam solutions, remember how you struggled with agent-based solutions before, and apply all that to vSphere AppHA. I totally expected they would simply reuse VMware Tools, because it is the necessary evil we have to live with… but unfortunately, this is not the case.

This is probably the first time ever that VMware delivers the feature that sounds good on paper, but has horrible implementation in reality. It feels very much like a “buy and glue on top” approach, rather than “innovate and build” acquisition. Are we seeing the change of VMware approach to R&D? I honestly hope this was more of an exception, rather than a rule, but this is still worrying and very annoying for me, hardened VMware fan. I will definitely be looking for VMware folks behind AppHA at VMworld Europe next month to discuss this, and understand what’s going on with this feature.

2009年黑馬偉業后又一淘寶奇遇全記錄!

By admin, September 23, 2013 9:33 am

想不到2009年發生黑馬偉業騙人事件大概4年后依然會遇上這樣的事情,當然心情已經沒之前那次差,因為這次賣家騙得實在太儿戲了。

哎,我有時候真想不明白為什么大陸就是有一小批害群之馬為這點芝麻小錢做這樣違背良心的事情,小心有報應,是真的!!!

前主席江澤民曾經訓話香港記者”Too Simple, Sometimes Naive”

要讓人不知,除非己莫為!!!

如果要用廣東話來講,這句最貼切不過: “若要人不知,唔好咁低B!” :)

=========================================
订单编号:410840997432134 成交时间:2013-08-31 13:01 keyida
查看宝贝详情
UT mclaren 迈凯轮F1 麦克拉伦F1 1:18反光镜和雨刮

我的淘宝账号 (2013-09-05 18:58:15):
你没寄吧?呵呵。

keyida(2013-09-06 20:47:24):
怎么没发,有必要骗你吗,我发都发出来了,好歹也是上海发出,至少也得三天

我的淘宝账号 (2013-09-07 18:56:30):
ok.

keyida(2013-09-08 20:03:46):
东西收到了吗

我的淘宝账号 (2013-09-09 19:45:21):
没有啊,怎么会这么久?

我的淘宝账号 (2013-09-09 19:46:12):
9/3到现在6天了,这下看来没戏了。

我的淘宝账号 (2013-09-09 19:47:42):
你自己的快递,如何追踪物件?最后没了等于你倒霉,哎,为什么不要那些专业的
快递公司呢?这点小钱也省。

keyida(2013-09-09 19:48:19):
这是我公司的快递,我发了好多年了

我的淘宝账号 (2013-09-09 19:48:19):
你在线

keyida(2013-09-09 19:48:55):
我现在在西藏出差,18号晚上才能回去,我的快递底单在公司里

我的淘宝账号 (2013-09-09 19:49:38):
惨了,惨得是你。

我的淘宝账号 (2013-09-09 19:49:44):
/:*&*

我的淘宝账号 (2013-09-16 13:37:46):
都16天了,我现在可以肯定你从来都没寄出过,连$50都骗,你真令我汗颜,我想问,
真的值得么?

keyida(2013-09-16 23:07:22):
我也很纳闷,我就是按照你淘宝上的地址发的,你凭哪点说我肯定没给你发出来过
呢?是不是我不回去把单号找出来给你,你就不死心呢?说我骗你50元,我才汗颜
呢,我也可以怀疑你东西收到说没收到,也可以说你骗我50元,目前我的东西发出
来了,快递费也是我这边出的,到底谁吃亏啊,你这样说,你觉得有必要么?

keyida(2013-09-16 23:10:30):
你好坏也看看我的信用评价,我为了骗你这50元,还包快递费,我吃饱了撑着了

keyida(2013-09-21 17:07:32):

keyida(2013-09-21 17:07:39):
这张是啥东西呢

我的淘宝账号 (2013-09-22 08:20:58):
我到现在为止也没收到,可以帮忙跟进一下吗?到底派去那里了?
谢谢。

keyida(2013-09-22 11:28:56):
钱都被退给你了,还有啥必要去跟进呢,你还说我骗钱呢!

keyida(2013-09-22 11:28:56):
钱都被退给你了,还有啥必要去跟进呢,你还说我骗钱呢!

我的淘宝账号 (2013-09-23 09:08:47):
现在过了近3个星期了,是个正常人也不会上你当的。

但如果你真的心中无愧的话,我当时已经讲得很明白要求你用顺风到付,我给全部
运费。但为什么最后你还是选了你自己的方法,然后说追踪不到,请问你用得着给
我省钱吗?

我的淘宝账号 (2013-09-23 09:08:52):
原来到最后你还是骗钱,朋友,这骗人的方法实在太幼稚了,10年前可能还行,现
在哪还有人不用追踪号码发货的啊?

哎,我有时候真想不明白为什么大陆就是有一小批害群之马为这点芝麻小钱做这样

违背良心的事情,小心有报应,是真的!!!

==========================================
淘宝客服
2013-09-17 11:49

您好,关于退款编号:15891128913421的交易退款小二已处理完毕。处理结果为:
退款成功,退款给买家,退款金额为50.0元
自己
2013-09-16 11:35

淘宝小二2013-09-100到现在已经超过4个工作日了,退款情况如何?
自己
2013-09-13 11:19

凭证一片空白,搞什么东东?
自己
2013-09-10 17:48

Thanks淘宝小二!
淘宝客服
2013-09-10 09:17

淘宝已介入处理,请耐心等待
淘宝客服
2013-09-09 19:58

淘宝已经受理退款纠纷,等待淘宝小二处理
自己
2013-09-07 18:31

买家要求淘宝介入处理。
卖家
keyida
2013-09-06 20:54

卖家(keyida)已经拒绝了退款申请,拒绝理由为:早已发货,还在途中,我在外
出差,凭证在公司
请双方友好协议

===========================
退款编号:         15891128913421
申请时间:         2013-09-05 06:30
退款成功时间:         2013-09-17 11:49
退款类型:         卖家已发货,买家未收到货,全额退款
退款状态:         退款成功
退款金额:         50.00 元
退款原因:

其他
退款说明:
物流编号:LP00014643273540发货方式:自己联系物流公司:顺民运单号码:20044092013-
09-0311:04:32卖家已发货该物流公司不支持跟踪信息查询 我的淘宝账号(2013-09-0313:37:23)
:上海顺民快递?电话是什么?网站是什么?eyida(2013-09-0314:31:05):这个快递
使我们公司自己的,是按照你网上的收货地址发的

退款成功。审核支持您,交易金额退给您50.00元,支付给卖家0.00元。