Steps to Building a Private Cloud

If you're considering building a private cloud, there are 5 steps you should take: Standardization, Consolidation, Virtualization, Automation and Orchestration.

1. Standardization:

Standardization is truly the foundation when it comes to building a private cloud, setting you up for success in each subsequent step. During the standardization phase, you'll want to decide which hardware and software components you'll use for the private cloud deployment.

Simplify your environment as much as possible the more disparate your systems, the more complexity and cost you'll incur as you build your private cloud. This is especially true during the automation and orchestration phases, in which custom integration of many systems becomes costly and time consuming. It would be difficult to justify more than one vendor's products in your data center, for example if you're an EMC shop or a NetApp shop, then be just that and avoid one-offs from other vendors. One way to make the justification process work is to avoid the trap of considering only the capital cost of a system look at the total cost of ownership, including the operating costs of managing multiple systems.

A common standardization practice is to build out infrastructure in a pod design. This allows a cookie-cutter approach to scale and results in a very predictable cost model. In this approach, a pod of network, compute and storage with a specific capacity is designed or procured as such. This allows standardization not only for individual components, but also for cabling, rack layout, connectivity and more.

2. Consolidation:

Once you know the systems you'll use to build a private cloud, it's time to consolidate. This is nothing new as the industry has been consolidating servers and storage for years. This phase is about limiting the amount of equipment that will be managed. Replace outdated low-performing equipment with systems that can scale to your needs. For example, if your design requires multiple storage protocols, look for systems that can meet your needs with a single device.

3. Virtualization: Whether you virtualize will depend on both your design and intended delivery model. Most models will require virtualization, but not all. For example, a pure PaaS model (not as common for private cloud) does not necessarily require server virtualization because the platform itself may handle allocation of underlying resources. Network virtualization techniques such as SDN may also be used to provide additional flexibility to network resources.

Don't ignore your standardization during this phase; you'll again want to keep TCO in mind and not be fooled by oversimplified capex arguments.

4. Automation:

So far, you've been mostly concerned about choosing the right systems; automation is the first step in modifying your IT processes. The goal is simple: Change common repetitive manual tasks to automated ones. Automation is the key to freeing up IT staff for more important tasks, such as service deployment. The automation tool set you choose will have a lot to do with the underlying consolidation and standardization decisions made. Not all products will work, or work well, with all hardware.

This is where the benefits of standardization will really shine through. The more standardized the environment, the fewer custom integration points will be required. In some cases, standardization choices can eliminate custom integration points all together. For example standardizing on Vblock, the unified server, storage and networking system created by a joint venture of EMC, Cisco and VMware, comes with Unified Infrastructure Manager, which is already customized to automate the underlying components. Other systems based on standards like CloudStack or OpenStack will also have unified management products.

5. Orchestration:

This is the last stage of the process, and provides the "self-service" functionality of a private cloud architecture. There are two key components you'll want from your orchestration product or suite: a service catalog and a self-service portal. The product you choose should also include trackback/chargeback functionality.

Most orchestration systems are actually a suite of software rather than single product. Many times these separate components came as a result of the vendor's acquisitions or were developed by separate internal business units, and only recently are they working together as an orchestration system. This can lead to integration pains within the orchestration software itself. Assess the integration and maturity of the software before you write your purchase order.

Hardware and software are just part of the process of building a private cloud--many would argue that they're the easy part. Using a staged approach as outlined here should help them remain that way. As you build out a plan and continue down the path, don't forget that people and process are a big part of the deployment.

Bài đăng phổ biến từ blog này

1968 Pontiac Firebird

1968 Pontiac Firebird photos collection, awesome Pontiac Firebird pictures The Pontiac Firebird is an American automobile that was built by Pontiac from the 1967 to the 2002 model years. The Firebird was introduced 23 February 1967, the same model year as the automaker's platform-sharing model, the Chevrolet Camaro. This coincided with the release of the 1967 Mercury Cougar, which shared its platform with another pony car, the Ford Mustang. The name "Firebird" was also previously used by Pontiac's parent company General Motors for the General Motors Firebird 1950s and early-1960s concept cars. First generation Firebirds (1967–1969) The first generation Firebirds had a characteristic Coke bottle styling. Unlike its cousin the Chevrolet Camaro, the Firebird's bumpers were integrated into the design of the front end. The Firebird's rear "slit" taillights were inspired by the Pontiac GTO. Both a two-door hardtop and a convertible were offered throug...

1967 Pontiac GTO

The Pontiac GTO is an American muscle car that was built by Pontiac in generations from 1964 to 1974 model years, and by GM's subsidiary Holden in Australia from 2004 to 2006. 1967 Pontiac GTO 1969 Pontiac GTO the "Judge" The first three generations of the Pontiac GTO was a muscle car of the 1960s and 1970s era.The Pontiac GTO was known as the judge of all muscle cars. the Pontiac GTO is considered by some to have started the trend with all four domestic automakers offering a variety of competing models. 1970 Pontiac GTO "Judge" For the 1964 and 1965 model years, the GTO was an optional package on the intermediate-sized Pontiac Tempest. The GTO became its own model from 1966 to 1971. It became an option package again for the 1972 and 1973 intermediate Le Mans. For 1974, the GTO option package was offered on the compact-sized Ventura. 1971 Pontiac GTO The GTO was selected Motor Trend Car of the Year in 1968.It was the only muscle car in the world which containe...

Greatest muscle cars of all time

Because it is a genre that enthusiasts are passionate about, you are bound to generate some criticism when compiling a list of the 7 greatest muscle cars of all time. However, we stuck its neck out to do just that. Some enthusiasts trace the history of muscle cars to the 1949 Oldsmobile Rocket 88. But the heyday of this genre ran from 1965 to 1970 before collapsing under the weight of higher gas prices, more stringent exhaust emissions regulations and soaring insurance costs. What is a muscle car? There isn't a settled definition, but most experts agree it's a smaller, 2-door car powered by a high-displacement engine typically found in a larger, full-size sedan. Some argue that pony cars, such as the Ford Mustang and Chevrolet Camaro, aren't muscle cars at all, but for this list, we chose not to make that distinction. Manufacturers engineered muscle cars for straight-line speed, inspiring more than an occasional Saturday night drag race between traffic lights. Neither built...

100 cụm động từ tiếng Anh phổ biến nhất kèm ví dụ minh họa

Trong quá trình học tiếng Anh, cụm động từ (phrasal verbs) là một trong những yếu tố ngữ pháp khiến nhiều người học cảm thấy khó khăn. Tuy nhiên, việc sử dụng thành thạo các cụm động từ không chỉ giúp bạn giao tiếp tự nhiên hơn mà còn thể hiện sự hiểu biết sâu sắc về ngôn ngữ này. Bài viết này sẽ giới thiệu 100 cụm động từ thông dụng trong tiếng Anh, giúp bạn nắm bắt được cách sử dụng chúng trong các tình huống giao tiếp hàng ngày. Hãy cùng khám phá và mở rộng vốn từ vựng của mình qua những cụm động từ này nhé! Add up - Cộng lại, tính tổng Ví dụ: The numbers don’t add up; there must be a mistake somewhere. Ask out - Mời ai đó đi chơi Ví dụ: He finally asked her out to dinner after months of hesitation. Back up - Hỗ trợ, sao lưu Ví dụ: Can you back me up during the meeting if I forget something? Blow up - Nổ tung, phóng đại Ví dụ: The balloon blew up when he filled it with too much air. Break down - Hỏng hóc, suy sụp Ví dụ: Our car broke down on the way to the airport...

Netflix gets user reaction when blocking account sharing

Netflix to Make Changes for People Who are Sharing the Same Accounts A lot of users decided to cancel the service after Netflix no longer allowed account sharing in more than 100 countries. Every three months, Brandy Andersen loads her clothes, kitchen supplies, fans, and a small TV into her car to travel to a new city. Her job as an emergency nurse makes her travel frequently between New York, Boston and Washington, as well as remote parts of northern California. Meanwhile, her Netflix account is registered at her home address in the state of Georgia, thousands of kilometers away. Andersen is one of many longtime Netflix customers who are angered by the account sharing block, which began in place in the U.S. last week. After years of encouraging account sharing with each other, Netflix is asking users to set a location, like a subscriber's home address. When logging into an account at this location, anyone can use the account. If the user enters the account from another location, ...

Cortana will stop working on Windows

Hi! I'm Cortana The eight-year-old virtual assistant Cortana on Windows is about to stop working, after Microsoft launched a series of new AI applications. On its support page, Microsoft says it is "making changes to Windows that may affect Cortana users." By the end of 2023, this virtual assistant will no longer appear on its operating system as a standalone application. Cortana first appeared on the Windows Phone mobile operating system to compete with Google Assistant or Apple Siri. Microsoft later expanded the assistant to other platforms, including Android and iOS. Since 2015, Cortana has been deeply integrated into Windows 10 and the Microsoft product ecosystem, supporting users in tasks such as scheduling, tasks, and voice email. According to Microsoft, the change with Cortana will first affect apps in Windows. Other platforms such as Outlook mobile, Teams mobile will still use this virtual assistant. Cortana's death announcement comes after Micorosft introduce...

7 ưu điểm khi học tiếng Anh bằng AI so với cách học truyền thống

Trong thời đại công nghệ 4.0 , trí tuệ nhân tạo (AI) đã và đang cách mạng hóa nhiều lĩnh vực, bao gồm cả giáo dục. Đặc biệt, việc học tiếng Anh bằng AI mang lại nhiều ưu điểm vượt trội so với phương pháp học truyền thống , từ tính cá nhân hóa, sự linh hoạt, đến hiệu quả học tập và chi phí. Bài viết này sẽ phân tích chi tiết 7 ưu điểm nổi bật của việc sử dụng AI trong học tiếng Anh, đồng thời so sánh với các hạn chế của phương pháp truyền thống để làm rõ sự khác biệt. 1. Cá nhân hóa lộ trình học tập Một trong những ưu điểm lớn nhất của việc học tiếng Anh bằng AI là khả năng cá nhân hóa. Các nền tảng AI sử dụng thuật toán phân tích dữ liệu để đánh giá trình độ, thói quen học tập, và điểm yếu của từng người học. Dựa trên thông tin này, AI thiết kế lộ trình học tập phù hợp, tập trung vào những kỹ năng mà người học cần cải thiện nhất. Ví dụ, nếu bạn yếu về phát âm , AI sẽ ưu tiên các bài tập luyện phát âm hoặc hội thoại. Trong khi đó, phương pháp học truyền thống thường áp dụn...

WikiHowBlog

Tìm kiếm Blog này