Write at the front-5 minutes a day to play with OpenStack (1)

"5 minutes a day with OpenStack" is an OpenStack tutorial, this is the 1th article.
This tutorial has the following two features:

1. system-guided OpenStack  
   

2. re-practicing and balancing theory  
   
   
   

/ol>

Why do you write this?

The simple answer is: because OpenStack learning is difficult, but if you know the value will be very big

Let's start with a self-introduction.

I network name Cloudman, in it this business has been in the past more than 10 years, 05 is to engage in the development of the upper application, Java compared to fire, so the related technology of the EE more. Later into a large IT company, the company's products from the middleware to the operating system, from server to storage, virtualization to cloud computing are involved.

My department is dedicated to the implementation of IT infrastructure services, the project involves servers, storage, networking, virtualization, cloud aspects. And the important task of this department is to expand the company in the latest and hottest areas of the IT market. such as the previous years of virtualization, the two years of cloud computing and big data.

It can be said that this position in the department is very much in line with my technical preference. I have a long-term interest in new technology and learning enthusiasm, so in this department is more than 10 years, and has been engaged in technology, although now the title is an architect, usually still insist on actual hands-on operation, otherwise there will be no sense of security.

Okay, now go back to the OpenStack topic.

I began to contact OpenStack in 2013, although with relatively solid technical skills, after a period of study, or feel OpenStack this thing is not easy to get started, personally think there are several reasons:

2. OpenStack covers a wide range of areas of knowledge
   It can be said to cover all areas of the IT infrastructure. Compute, storage, networking, virtualization, high availability, security, disaster preparedness ... Everything Even people like Cloudman, who work in this field every day, feel a lot of pressure.

4. OpenStack is a platform, not a specific implementation scenario
   The various components of OpenStack use driver architecture to support a variety of specific implementation technologies. For example, OpenStack storage service Cinder only defines the upper-level abstract API, the implementation of the following Driver, such as the LVM-based iSCSI DRIVER,EMC, IBM and other commercial storage products Driver, or open-source distributed storage software, such as Ceph, Glusterfs's driver.

   Because of this architectural flexibility, beginners are not as easy to learn as other specific software products when learning OpenStack.

6. OpenStack itself is a distributed system
   Most of IT are not too familiar with distributed computing. Rushing in directly will be foggy by the myriad of OpenStack components and the way they interact with each other.

Although the OpenStack learning curve is steeper, it's not as big as it is, but OpenStack is now a reality standard for IaaS clouds, and the future is bright enough for us to engage it if we can chew on this bone, it will definitely improve our competitiveness.

Write to WHO to see

The target audience for this tutorial includes:

2. OpenStack Beginner
   Cloudman Learning OpenStack has also experienced a difficult and tortuous process. The main reason for this is that no system has been found to teach OpenStack tutorials, especially for beginners. Most of the information is more scattered, for beginners can not be organically strung together. It was for this reason that I had the idea of writing a tutorial that would allow beginners to learn, master, and practice OpenStack with less detours.

4. OpenStack Implementation Engineer
   Previously said, Cloudman in the company's position is the architect, but in the bones I even more positioning myself as an implementation engineer to the first siege of the village. So this tutorial is also for OpenStack implementers, so they can learn to really master the knowledge, skills, and troubleshooting skills to deploy OpenStack.

6. my own
   Writing this tutorial is also a summary of your own years of learning and practicing OpenStack.
   I think: for knowledge, only to write it and to be able to make other people understand to really know that they have mastered this knowledge.
   
   
   

What is included in the content?

For example, two chunks:

650) this.width=650; "Src=" http://mmbiz.qpic.cn/mmbiz/ Hia4hvyxricqgdh5omcyolth0fwdicefkyo4duibcsxklbb5o5p8ev6yftbvr7fmtibh16fw9nr9v45iapjkgpocuzsg/640?wx_fmt=png &tp=webp&wxfrom=5&wx_lazy=1 "style=" Margin:0px;padding:0px;height:auto;width:auto; "alt=" 640?wx_fmt= Png&tp=webp&wxfrom=5&wx_lazy= "/>

2. Pre-knowledge
   For beginners, there will be "pre-knowledge" of virtualization and cloud computing, which will introduce technologies such as Kvm,iaas.

4. OpenStack Core
   This is the main content, including the architecture of OpenStack and the various core components. There will be a number of cases, procedures, and logs to help you understand how OpenStack components work.
   The goal is to allow you to configure and adapt to your customers ' needs.
   
   
   

What kind of writing method?

In the current era of shared economy, Cloudman felt that the Internet should be used to share knowledge and experience. This tutorial will be published regularly via Cloudman's public number (CLOUDMAN6), 1, 3, 5 per week.

I think there are two benefits of using the public number:

1. View and browse what you've pushed, anytime, anywhere
   

2. Can interact with Cloudman through the public number and ask questions and suggestions
   
   
   

Why call "5 minutes a day to play OpenStack"?

in order to reduce the difficulty of learning and take into account the characteristics of mobile fragmented reading, each push of the content you need to spend5 minutes to finish it .(Note that this isRead, sometimes it may take more time to fully understand, and each time the content contains only 1-3 points of knowledge, which is why I named the tutorial 5 minutes a day to play with OpenStack. Although it is fragmented push, the whole tutorial is systematic, coherent and complete, just piecemeal.

OK, today this 5 minutes is a start, next time we formally started to play with OpenStack.

650) this.width=650; "Src=" http://mmbiz.qpic.cn/mmbiz/ Hia4hvyxricqgdh5omcyolth0fwdicefkyof34258mmt62fwkqjynibqzyictxuxcqewowjzuqre5yiampme3t91onqa/640?wx_fmt=png &tp=webp&wxfrom=5&wx_lazy=1 "style=" Margin:0px;padding:0px;height:auto;width:auto; "alt=" 640?wx_fmt= Png&tp=webp&wxfrom=5&wx_lazy= "/>

This article is from the "Cloudman" blog, make sure to keep this source http://cloudman.blog.51cto.com/10425448/1745873

Write at the front-5 minutes a day to play with OpenStack (1)