Merge pull request MichaelCade#59 from LeslieLeung/zh_cn

feat: Chinese ver.

README.md

@@ -4,6 +4,8 @@
  <img src="logo.png?raw=true" alt="90DaysOfDevOps Logo" width="50%" height="50%" />
 </p>
 
+English Version | [中文版本](zh_cn/README.md)
+
 This repository is used to document my journey on getting a better foundational knowledge of DevOps. I will be starting this journey on the 1st January 2022 but the idea is that we take 90 days which just so happens to be January 1st to March 31st. 
 
 The reason for documenting these days is so that others can take something from it and also hopefully enhance the resources. 

zh_cn/Days/day01.md

@@ -0,0 +1,62 @@
+---
+title: '#90DaysOfDevOps - Introduction - Day 1'
+published: false
+description: 90DaysOfDevOps - Introduction
+tags: "devops, 90daysofdevops, learning"
+cover_image: null
+canonical_url: null
+id: 1048731
+---
+## 简介 - Day 1 
+
+Day 1 of our 90 days and adventure to learn a good foundational understanding of DevOps and tools that help with a DevOps mindset. 
+
+This learning journey started for me a few years back but my focus then was around virtualisation platforms and cloud based technologies, I was looking mostly into Infrastructure as Code and Application configuration management with Terraform and Chef. 
+
+Fast forward to March 2021, I was given an amazing opportunity to concentrate my efforts around the Cloud Native strategy at Kasten by Veeam. Which was going to be a massive focus on Kubernetes and DevOps and the community surrounding these technologies. I started my learning journey and quickly realised there was a very wide world aside from just learning the fundamentals of Kubernetes and Containerisation and it was then when I started speaking to the community and learning more and more about the DevOps culture, tooling and processes so I started documenting some of the areas I wanted to learn in public. 
+
+[So you want to learn DevOps?](https://blog.kasten.io/devops-learning-curve)
+
+## 开始我们的旅程吧
+
+If you read the above blog you will see this is a high level contents for my learning journey and I will say at this point I am no where near an expert in any of these sections but what I wanted to do was share some resources both FREE and some paid for but an option for both as we all have different circumstances. 
+
+Over the next 90 days I want to document these resources and cover those foundational areas, I would love for the community to also get involved share your journey and resources so we can learn in public and help each other. 
+
+You will see from the opening readme in the project repository that I have split things into sections and it is basically 12 weeks plus 6 days. The first 6 days we will explore the fundamentals of DevOps in general before diving into some of the specific areas, by no way is this list exhaustive and again would love for the community to assist in making this a useful resource. 
+
+Another resource I will share at this point that I think everyone should have a good look at and maybe create your own mind map for yourself and your interest and position is the following: 
+
+[DevOps Roadmap](https://roadmap.sh/devops)
+
+I found this a great resource when I was creating my initial list and blog post on this topic. You can also see there are other areas that go into a lot more detail outside of the 12 topics I have listed here in this repository. 
+
+## 第一步 - 什么是 DevOps? 
+
+There are so many blog articles and YouTube videos to list here, but as we start the 90 day challenge and we focus on spending around an hour a day learning something new or about DevOps I thought it was good to get some of the high level of "what DevOps is" down to begin. 
+
+Firstly, DevOps is not a tool. You cannot buy it, it is not a software sku or an open source GitHub repository you can download. It is also not a programming language, it is also not some dark art magic either. 
+
+DevOps is a way to do smarter things in Software Development. - Hold up... But if you are not a software developer should you turn away right now and not dive into this project??? No Not at all, Stay... Because DevOps brings together a combination of software development and operations. I mentioned earlier that I was more on the VM side and that would generally fall under the Operations side of the house, but within the community there are people with all different backgrounds where DevOps is 100% going to benefit the individual, Developers, Operations and QA Engineers all can equally learn these best practices by having a better understanding of DevOps. 
+
+DevOps is a set of practices that help to reach the goal of this movement: reducing the time between the ideation phase of a product and its release in production to the end-user or whomever it could be an internal team or customer. 
+
+Another area we will dive into in this first week is around **The Agile Methodology** DevOps and Agile are widely adopted together to achieve continuous delivery of your **Application** 
+
+The high level take away is with a DevOps mindset or culture its about taking a way the long drawn out software release process from potentially years to being able to drop smaller releases more frequently. The other key fundamental to take away here is it's about breaking down silos between the teams I previously mentioned, Developers, Operations and QA. 
+
+From a DevOps perspective, **Development, Testing and Deployment** all land with the DevOps team. 
+
+The final point I will make is to make this as effective and efficient as possible we must leverage **Automation** 
+
+## Resources 
+
+I am always open to adding additional resources to these readme files as it is here as a learning tool.  
+
+My advice is to watch all of the below and hopefully you also picked something up from the text and explanations above. 
+
+- [DevOps in 5 Minutes](https://www.youtube.com/watch?v=Xrgk023l4lI)
+- [What is DevOps? Easy Way](https://www.youtube.com/watch?v=_Gpe1Zn-1fE&t=43s)
+- [DevOps roadmap 2022 | Success Roadmap 2022](https://www.youtube.com/watch?v=7l_n97Mt0ko)
+
+If you made it this far then you will know if this is where you want to be or not. See you on [Day 2](day02.md).  

zh_cn/Days/day02.md

@@ -0,0 +1,67 @@
+---
+title: '#90DaysOfDevOps - Responsibilities of a DevOps Engineer - Day 2'
+published: false
+description: 90DaysOfDevOps - Responsibilities of a DevOps Engineer
+tags: 'devops, 90daysofdevops, learning'
+cover_image: null
+canonical_url: null
+id: 1048699
+---
+## Responsibilities of a DevOps Engineer 
+
+Hopefully you are coming into this off the back of going through the resources and post on [Day1 of #90DaysOfDevOps](day01.md) 
+
+It was briefly touched on in the first post but now we must get deeper into this concept and understand that there are two main parts when creating an application. We have the **Development** part where software developers program the application and test it. Then we have the **Operations** part where the application is deployed and maintained on a server. 
+
+## DevOps is the link between the two
+
+To get to grips with DevOps or the tasks in which a DevOps engineer would be carrying out we need to understand the tools or the process and overview of those and how they come together. 
+
+Everything starts with the application! You will see so much throughout that it is all about the application when it comes to DevOps.
+
+Developers will create an application, this can be done with many different technology stacks and lets leave that to the imagination for now as we get into this later. This can also involve many different programming languages, build tools, code repository etc. 
+
+As a DevOps engineer you won't be programming the application but having a good understanding of the concepts of how a developer works and the systems, tools and processes they are using is key to success. 
+
+At a very high level you are going to need to know how the application is configured to talk to all of its required services or data services and then also sprinkle a requirement of how this can or should be tested. 
+
+The application will need to be deployed somewhere, lets keep it generally simple here and make this a server, doesn't matter where but a server. This is then expected to be accessed by the customer or end user depending on the application that has been created. 
+
+This server needs to run somewhere, on-premises, in a public cloud, serverless (Ok I have gone too far, we won't be covering serverless but its an option and more and more enterprises are heading this way) Someone needs to create and configure these servers and get them ready for the application to run. Now this element might land to you as a DevOps engineer to deploy and configure these servers. 
+
+These servers will have to run an Operating System and generally speaking this is going to be Linux but we have a whole section or week where we cover some of the foundational knowledge you should gain here. 
+
+It is also likely that we need to communicate with other services in our network or environment, so we also need to have that level of knowledge around networking and configuring that, this might to some degree also land at the feet of the DevOps engineer. Again we will cover this in more detail in a dedicated section talking all things DNS, DHCP, Load Balancing etc. 
+
+## Jack of all trades, Master of none 
+
+I will say at this point though, you don't need to be a Network or Infrastructure specialist you need a foundational knowledge of how to get things up and running and talking to each other, much the same as maybe having a foundational knowledge of a programming language but you don't need to be a developer. However you might be coming into this as a specialist in an area and that is a great footing to adapt to other areas. 
+
+You will also most likely not take over the management of these servers or the application on a daily basis. 
+
+We have been talking about servers but the likelihood is that your application will be developed to run as containers, Which still runs on a server for the most part but you will also need an understanding of not only virtualisation, Cloud Infrastructure as a Service (IaaS) but also containerisation as well, The focus in these 90 days will be more catered towards containers. 
+
+## High Level Overview
+
+On one side we have our developers creating new features and functionality (as well as bug fixes) for the application. 
+
+On the other side we have some sort of environment, infrastructure or servers which are configured and managed to run this application and communitcate with all its required services. 
+
+The big question is how do we get those features and bug fixes into our production and make it available to those end users? 
+
+How do we release the new application version? This is one of the main tasks for a DevOps engineer, and the important thing here is not to just figure out how to do this once but we need to do this continuously and in an automated, efficient way which also needs to include testing! 
+
+This is where we are going to end this day of learning, hopefully this was useful. Over the next few days we are going to dive a little deeper into some more areas of DevOps and then we will get into the sections that dive deeper into the tooling and processes and the benefits of these. 
+
+## Resources 
+
+I am always open to adding additional resources to these readme files as it is here as a learning tool.  
+
+My advice is to watch all of the below and hopefully you also picked something up from the text and explanations above. 
+- [What is DevOps? - TechWorld with Nana](https://www.youtube.com/watch?v=0yWAtQ6wYNM)
+- [What is DevOps? - GitHub YouTube](https://www.youtube.com/watch?v=kBV8gPVZNEE)
+- [What is DevOps? - IBM YouTube](https://www.youtube.com/watch?v=UbtB4sMaaNM)
+- [What is DevOps? - AWS ](https://aws.amazon.com/devops/what-is-devops/)
+- [What is DevOps? - Microsoft](https://docs.microsoft.com/en-us/devops/what-is-devops)
+
+If you made it this far then you will know if this is where you want to be or not. See you on [Day 3](day03.md).