Learn the OpenStack methodology-5 minutes a day to play OpenStack __openstack

As a core tutorial for OpenStack, we have come to the final summary.

OpenStack currently has dozens of modules, this tutorial discusses the most important core modules: Keystone,nova,glance,cinder and neutron. Please look at the following figure:

This figure is truncated from https://www.openstack.org/software/project-navigator/, which is the official 6 Core Service defined by OpenStack. Each module will be measured from three dimensions:

Adoption-Adoption Degree

Maturity-Maturity

Age-Ages

Adoption and maturity are the two key indicators.

Let's look at adoption first. If the adoption of the module can reach 90%, it can basically be said that the module will be deployed as long as the OpenStack is used.

Maturity 8 for full marks, if it is 7, 8 points of the maturity, then the structure of this module is very stable, the function is also very perfect, it should be said to reach the level of production.

In fact, Cloudman in considering the scope of the technical coverage of the tutorial is also a reference to this map, the adoption of degrees and maturity of the module is that we should focus on the technology. As you may have noticed, in the 6 Core Service, Swift was not included in this tutorial. Swift is an object store with a high degree of maturity and is widely used in the Internet industry, but not much in traditional applications. OpenStack is currently used primarily for private clouds, so adoption has been limited to less than 50%. This is also the main reason why Cloudman has not put it into this tutorial for the time being.

We are in an industry with a very fast knowledge update, and if you do not study for two or three years, you risk being eliminated. Learning the new technology is part of the day-to-day work of it practitioners, and since choosing to do this you have to face this reality.

For how to learn new technology, Cloudman has some personal advice, take this opportunity to communicate with you.
what techniques should be preferred to study.

Our time and energy are limited, and new technologies are many, and there is a question of effectiveness that must be considered: mastering the most valuable skills in the least amount of time.

What skills are most valuable?

My first judgment was to choose the skills that will be popular and massively used in the future. For example, OpenStack is already the actual standard of IaaS, community active, and large manufacturers actively participate, more importantly, more and more heavyweight enterprises began to deploy and practice OpenStack, the development momentum is strong. On the other hand OpenStack technical talent gap is very large, scarcity determines the value, so we see the talent market for OpenStack's favor.

Well, suppose we all agree that OpenStack should be learning skills (otherwise you won't read this article:-), so the next question is OpenStack module so much, how do I learn it. Are you all learning? In what order to learn it. This is my second criterion: To learn the skills that adoption and maturity are high .

Adoption high means that the market needs, learning can be used. Maturity High means that the technical framework has been mature and stable, after learning for a considerable period of time is effective, not outdated. Here are two modules for a specific analysis.

Take a look at swift, as I said earlier, this technology is used by internet companies, but traditional companies are currently limited, and if you work in a traditional business, taking the time to learn Swift is certainly not a worthwhile investment. Of course, if you have a clear idea that your company will store objects, that's another story.

Another module is Ceilometer, which belongs to the OpenStack optional service. Please look at the following picture:

Ceilometer's main role is to collect OpenStack performance data and events, for the operational dimension is very important, so we see its adoption can also, 62%. But the maturity level is too low. This is also true, almost OpenStack each version of the Ceilometer architecture and code have a lot of changes, although it is a very promising module, but if we spend too much time to study, it may be more than six months after the effort to learn again, because it may be outdated. For most of OpenStack's technicians, Cloudman does not recommend spending too much energy on ceilometer. Of course, if your responsibility is to achieve OpenStack performance monitoring or metering, ceilometer should be around the ridge.

In the optional service there is a adoption and maturity can also be a module-Heat. This module is used to do choreography, in fact, it is very valuable, such as the virtual machine can be implemented by the auto scaling. Cloudman If you want to update the tutorial, Heat will certainly not miss it.
how to learn.

Simply put: Theory with practice .

It is difficult to master it technology, indeed, such a large and complex architecture as OpenStack. But on the other hand, if you can learn easily, the value of our technical staff is not big. I don't see any company willing to pay a big price for a VMware administrator.

For IT technology, the best way to learn is to learn while practicing. It's not clear at first. The principle and the bottom detail does not matter, first installed on the run, can run a minimum case, first set up perceptual knowledge and positive feedback is very important. Then the document from the architecture to the details, from the principle to the implementation step by step exploration. This is also cloudman in the tutorial to follow the method as far as possible. Each chapter has designed a large number of practical operation links, through screenshots and logs to help you understand the technical points. In the course of the course of writing for one of the experiments I will try different scenes and boundary conditions, and finally presented to everyone is the most typical scene. Very encouraging everyone to follow the experiment, to tell the truth, just look at the tutorial I do not think there will be much, of course, if your purpose is only to understand what OpenStack can do is another matter.
How to use this tutorial.

This tutorial should have two roles for readers:

Beginners can systematically learn OpenStack according to the Order of chapters, and Master OpenStack's theoretical knowledge and practical skills through the experiments in the tutorial.

Experienced operators can use this tutorial as a reference material, in the actual work of a targeted view of the relevant knowledge points. suggestions for continuing to study

If you want to learn more about OpenStack, my advice is to first make sure you have the knowledge of this tutorial, because this is the foundation. The meaning of mastery is that theory can relate to practice. Can deploy, will operate, can see the log, will troubleshoot problems. After that. I believe that when you do this, you already have the ability to self-study other modules or to learn a core service in depth.
The idea of a new tutorial

OpenStack This tutorial is temporarily closed, the reason is "temporary", because there is no other module to meet our previous two selection criteria. When a new module satisfies the criteria, Cloudman will continue to update the tutorial, and for now, it is more promising to Heat and Swift. Again, this is not to say that other modules are not worth learning, just as the content of the tutorial is not appropriate, because the tutorial is for most people. If you have a job or interest in your own needs, of course you can self-study. Take Cloudman, some customers need billing function, I also spent a lot of time to study the Cloudkitty module.

In addition, if there are some new and valuable features in the core module, I will timing update the tutorial.

In addition, what technology satisfies those two choice conditions. If you are sharp enough, believe you will give the answer-the container .

Container is another big trend of cloud computing, and the container ecology that builds around Docker is more and more mature, so Cloudman next tutorial is called "5 minutes a day to play the container technology". In this tutorial, there are several core aspects of the container ecosystem: containers, mirrors, networks, storage, choreography engines, management platforms, and container based PaaS.

Before starting this new tutorial, however, Cloudman also wanted to share with you some of the practical skills and experiences that individuals have summed up and accumulated over the years in OpenStack project practice as a complement to the tutorials. This section will have 10 articles or so, each one a skill or case.

Public number or 1, 3, 5 updates every week, thank you for your company in the past year, 2017 we continue to move forward together.