Martin Liu

Martin Liu

Senior Developer Relations/Advocate, Founder of DevOps China, Microsoft MVP

Martin Liu

3 分钟


Getting Ready for Cloud Computing 2013

[dc]看[/dc]到篇不错的文章,值得分享一下。在最近的三四年里面,厂商都忙着炒作概念,用似云非云的各种虚拟化来对付用户,实际上云计算并没有那么简单,我一直不敢给客户讲,也讲不好的东西就是:对于一个特定的用户,告诉它什么是云?他应该怎么怎么过渡到云?先从那里做起?大致的路径是怎么样的?一旦对应到具体的用户环境里面,以上每个用户的答案都是不同的,感觉没有十足实践经验的人,根本无法和用户达成共鸣和一致。这个和我以前做 ITSM/ITIL 完全不同,在那块领域里面,讲究的是管理的思路和理念,等你做了一些项目之后,你从项目中的总结和提炼,就成了你的炮弹,用在其它新用户身上,用不好,也用不错;管理的学问往往是殊途同归的。而云计算,目前国内真的还属于初级阶段,就像是在 2002 年左右的时候,我们给银行做 ITIL 做服务台一样,对无论是用户和厂商的人来说,还不夸张的说,都是雾里看花。

[tab label=“云计算七大注意事项” first=“yes”]

[list icon=“star”]

    1. 检查和评估您的网络 : 如果数据中心不做网络架构的巨大调整,给云平台配置足够强大的带宽资源,上云计算,基本上就是让用户和运维人员都痛苦不堪,不会有啥好结果。
    1. 建立鼓励员工进谏的机制 : 识别、评估、选择和实施云计算方案的流程需要提前设计好。在每个阶段和过程里让最终用户、开发人员和管理层都充分的参与意见。
    1. 聚焦在立竿见影的运维痛点和功能差距上: 瞄准那些影响最终用户生产力和新上面的应用部署项目上。让云计算的高效和灵活等优势小试牛刀一下,从而验证需求点的准确性和方案的靠谱性。
    1. 先尝后买 : 云计算是最着急投胎的,没有必要大干快上,对于数据中心来说也是一个渐进的温和的改良的过程。选定一个足够小的范围,先尝后买,分区分配扩容,放大项目范围。
    1. 承载应用(App hosting)和 SaaS 应用不能划等号 : 这根本就是个误解,无须多说。
    1. 监控利用率和满意度 : 不管云做的大小,资源都要物尽其用,跟踪最终用户和领导大满意度,与同行用户横向比较数据,找出自己的所处位置和程度。实施反馈机制,让用户驱动云的需求和建设方向。
    1. 眼观六路,站足先机 : 市场风云莫测,业务模式层出不穷,这些都不断催熟这云方案。所以广泛关注,收集跟多信息,为云计算建立多个选项,多种选择总是好事。

[/list] [/tab]

[tab label=“英文原文”]

If you’ve been holding back about moving to the ‘Cloud’, it is time to get onboard the Cloud Computing express.

Not only has every major research firm published market forecasts indicating that Cloud services are growing exponentially, but we see multiplying customer success stories that clearly illustrate the immediate and measurable business benefits of moving to the Cloud.

Here are some simple rules you should follow to help you move ahead in the coming year and successfully leverage today’s rapidly evolving Cloud alternatives:

1. Check your networks: Adopting Cloud solutions doesn’t make sense if you don’t have sufficient bandwidth capabilities. Without adequate connectivity, accessing Cloud services will be like stepping back in time and only frustrate your end-users and executives.

2. Establish policies that encourage employee input: Develop straightforward procedures for identifying, evaluating, selecting and implementing Cloud solutions. Your end-users, developers and executives are being exposed to Software-as-a-Service (SaaS) applications, Platform-as-a-Service (PaaS) solutions and Infrastructure-as-a-Service (IaaS) alternatives every day. Invite them to recommend those they like.

3. Focus on your immediate pain-points and functional gaps: Don’t rip out existing applications that work and cost little to maintain. Instead, target those cumbersome old applications that get in the way of end-user productivity and new applications to fill immediate needs.

4. Start small and try before you buy: One of the greatest advantages of today’s Cloud solutions is that they mitigate many of the risks associated with traditional, legacy applications. Rather than paying for a perpetual license upfront without having an opportunity to test how it will meet your needs, many of today’s Cloud solutions allow you to try them out before you subscribe to them. And, you can start with a small group of users, or a single department, before you roll out the solution across your organization.

5. Recognize that application hosting doesn’t equal Software-as-a-Service (SaaS): There is a growing number of legacy, on-premise software vendors who are offering hosted versions of their applications on a subscription pricing basis and calling them “SaaS” solutions. Although these hosted applications alleviate some of the operational hassles and reduce the upfront cost associated with traditional software deployment, they still fall short of the fundamental benefits of true ‘multitenant’ SaaS solutions, such as ongoing enhancements and aggregated benchmarks. In addition, the legacy software vendors can’t scale their hosted services if their customers are using varying versions of the hosted application.

6. Monitor utilization and measure satisfaction: Track how your end-users and executives are using the SaaS apps and other Cloud services. Be sure the utilization levels justify the current subscription fees to prevent overspending. Investigate how your utilization levels compare with other organizations by requesting benchmark information from SaaS/Cloud vendors. Implement feedback mechanisms to ensure satisfaction and generate new ideas. Use data to determine future service requirements.

7. Stay informed to stay ahead: The Cloud marketplace is changing rapidly from a technological perspective and maturing quickly from a business model point of view. Keeping up on the latest developments may be a challenge, but is also essential to take full advantage of the increasingly powerful solutions being delivered via the Cloud. Maintain an ‘open door’ policy and utilize social networking tools to invite your end-users, executives and others to share information about new services and best practices. [/tab]




This Blog is sharing DevOps and SRE ariticles. I am a Senior Developer Relations/Advocate at Elastic, Founder of DevOps China since 2017, Microsift MVP since 2021, DevOps Institute Ambassador.