From 753deb532516cda8d4850990ae5aa527547f52b6 Mon Sep 17 00:00:00 2001 From: Morisun029 <54652937+Morisun029@users.noreply.github.com> Date: Mon, 20 Jan 2020 20:55:31 +0800 Subject: [PATCH 01/17] translating --- ...117 Use this Python script to find bugs in your Overcloud.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sources/tech/20200117 Use this Python script to find bugs in your Overcloud.md b/sources/tech/20200117 Use this Python script to find bugs in your Overcloud.md index ee167e6f78..5f19f114b4 100644 --- a/sources/tech/20200117 Use this Python script to find bugs in your Overcloud.md +++ b/sources/tech/20200117 Use this Python script to find bugs in your Overcloud.md @@ -1,5 +1,5 @@ [#]: collector: (lujun9972) -[#]: translator: ( ) +[#]: translator: (Morisun029) [#]: reviewer: ( ) [#]: publisher: ( ) [#]: url: ( ) From d07fdf73b2854b65aa8ccfb1d1440c506d9dd22b Mon Sep 17 00:00:00 2001 From: Morisun029 <54652937+Morisun029@users.noreply.github.com> Date: Mon, 20 Jan 2020 21:06:37 +0800 Subject: [PATCH 02/17] translating --- .../20191227 Top CI-CD resources to set you up for success.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sources/tech/20191227 Top CI-CD resources to set you up for success.md b/sources/tech/20191227 Top CI-CD resources to set you up for success.md index 77d2391a5d..d3da7c4d09 100644 --- a/sources/tech/20191227 Top CI-CD resources to set you up for success.md +++ b/sources/tech/20191227 Top CI-CD resources to set you up for success.md @@ -1,5 +1,5 @@ [#]: collector: (lujun9972) -[#]: translator: ( ) +[#]: translator: (Morisun029) [#]: reviewer: ( ) [#]: publisher: ( ) [#]: url: ( ) From d3515333456a10c646bacf17e589238f318871ed Mon Sep 17 00:00:00 2001 From: Morisun029 <54652937+Morisun029@users.noreply.github.com> Date: Mon, 20 Jan 2020 21:18:39 +0800 Subject: [PATCH 03/17] translating --- ...nto Why Hyperbola GNU-Linux is Turning into Hyperbola BSD.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sources/talk/20200117 Insights into Why Hyperbola GNU-Linux is Turning into Hyperbola BSD.md b/sources/talk/20200117 Insights into Why Hyperbola GNU-Linux is Turning into Hyperbola BSD.md index 68ede9acfa..a4d3cf9510 100644 --- a/sources/talk/20200117 Insights into Why Hyperbola GNU-Linux is Turning into Hyperbola BSD.md +++ b/sources/talk/20200117 Insights into Why Hyperbola GNU-Linux is Turning into Hyperbola BSD.md @@ -1,5 +1,5 @@ [#]: collector: (lujun9972) -[#]: translator: ( ) +[#]: translator: ( Morisun029) [#]: reviewer: ( ) [#]: publisher: ( ) [#]: url: ( ) From 520ee538ef2f4f8a3cf6248b37863a0fbcd79d61 Mon Sep 17 00:00:00 2001 From: Morisun029 <54652937+Morisun029@users.noreply.github.com> Date: Fri, 24 Jan 2020 09:33:24 +0800 Subject: [PATCH 04/17] translated --- ...-CD resources to set you up for success.md | 57 ----------------- ...-CD resources to set you up for success.md | 64 +++++++++++++++++++ 2 files changed, 64 insertions(+), 57 deletions(-) delete mode 100644 sources/tech/20191227 Top CI-CD resources to set you up for success.md create mode 100644 translated/tech/20191227 Top CI-CD resources to set you up for success.md diff --git a/sources/tech/20191227 Top CI-CD resources to set you up for success.md b/sources/tech/20191227 Top CI-CD resources to set you up for success.md deleted file mode 100644 index d3da7c4d09..0000000000 --- a/sources/tech/20191227 Top CI-CD resources to set you up for success.md +++ /dev/null @@ -1,57 +0,0 @@ -[#]: collector: (lujun9972) -[#]: translator: (Morisun029) -[#]: reviewer: ( ) -[#]: publisher: ( ) -[#]: url: ( ) -[#]: subject: (Top CI/CD resources to set you up for success) -[#]: via: (https://opensource.com/article/19/12/cicd-resources) -[#]: author: (Jessica Cherry https://opensource.com/users/jrepka) - -Top CI/CD resources to set you up for success -====== -Continuous integration and continuous deployment were key topics in 2019 -as organizations look to achieve seamless, flexible, and scalable -deployments. -![Plumbing tubes in many directions][1] - -This has been a fantastic year for continuous integration/continuous deployment (CI/CD) and the world of DevOps. Opensource.com authors shared how they're moving toward agile and scrum as they focus on seamless, flexible, and scalable deployments. Here are some of the big themes in the CI/CD articles we published this year. - -### Learning and improving your CI/CD skills - -Some of our favorite articles focus on hands-on CI/CD experience and cover a lot of ground as they do. The place to start is always with [Jenkins][2] pipelines, and Bryant Son's [_Building CI/CD pipelines with Jenkins_][3] will give you enough experience to get started building your first pipelines. Daniel Oh's [_Automate user acceptance testing with your DevOps pipeline_][4] provides great information on acceptance testing, including various CI/CD applications you can use for testing in its own right. And my article on [_Security scanning your DevOps pipeline_][5] is a very short, to the point tutorial on how to set up security in a pipeline using the Jenkins platform. - -### Delivery workflow - -While learning how to use and improve your skills with CI/CD, the workflow matters, especially when it comes to pipelines, as Jithin Emmanuel shares in [_Screwdriver: A scalable build platform for continuous delivery_][6]. Emily Burns explains having the flexibility to build exactly what you need with your CI/CD workflow in [_Why Spinnaker matters to CI/CD_][7]. And Willy-Peter Schaub extols the idea of creating a unified pipeline for everything to build consistently in [_One CI/CD pipeline per product to rule them all_][8]. These articles will give you a good sense of what happens after you onboard team members to the workflow process. - -### How CI/CD affects organizations - -2019 was also the year of recognizing CI/CD's business impact and how it affects day-to-day operations. Agnieszka Gancarczyk shares the results of Red Hat's [_Small Scale Scrum vs. Large Scale Scrum_][9] survey, including respondents' differing opinions on scrums, the agile movement, and the impact on teams. Will Kelly covers [_How continuous deployment impacts the entire organization_][10], including the importance of open communication, and Daniel Oh emphasizes the importance of metrics and observability in [_3 types of metric dashboards for DevOps teams_][11]. Last, but far from least, Ann Marie Fred's great article [_Don't test in production? Test in production!_][12] details why it's important for you to test in production—before your customers do. - -We are thankful to the many contributing authors who shared their insights with Opensource.com readers in 2019, and I look forward to learning more from them about the evolution of CI/CD in 2020. - --------------------------------------------------------------------------------- - -via: https://opensource.com/article/19/12/cicd-resources - -作者：[Jessica Cherry][a] -选题：[lujun9972][b] -译者：[译者ID](https://github.com/译者ID) -校对：[校对者ID](https://github.com/校对者ID) - -本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 - -[a]: https://opensource.com/users/jrepka -[b]: https://github.com/lujun9972 -[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/plumbing_pipes_tutorial_how_behind_scenes.png?itok=F2Z8OJV1 (Plumbing tubes in many directions) -[2]: https://jenkins.io/ -[3]: https://opensource.com/article/19/9/intro-building-cicd-pipelines-jenkins -[4]: https://opensource.com/article/19/4/devops-pipeline-acceptance-testing -[5]: https://opensource.com/article/19/7/security-scanning-your-devops-pipeline -[6]: https://opensource.com/article/19/3/screwdriver-cicd -[7]: https://opensource.com/article/19/8/why-spinnaker-matters-cicd -[8]: https://opensource.com/article/19/7/cicd-pipeline-rule-them-all -[9]: https://opensource.com/article/19/3/small-scale-scrum-vs-large-scale-scrum -[10]: https://opensource.com/article/19/7/organizational-impact-continuous-deployment -[11]: https://opensource.com/article/19/7/dashboards-devops-teams -[12]: https://opensource.com/article/19/5/dont-test-production diff --git a/translated/tech/20191227 Top CI-CD resources to set you up for success.md b/translated/tech/20191227 Top CI-CD resources to set you up for success.md new file mode 100644 index 0000000000..31ee2628b4 --- /dev/null +++ b/translated/tech/20191227 Top CI-CD resources to set you up for success.md @@ -0,0 +1,64 @@ +[#]: collector: (lujun9972) +[#]: translator: (Morisun029) +[#]: reviewer: ( ) +[#]: publisher: ( ) +[#]: url: ( ) +[#]: subject: (Top CI/CD resources to set you up for success) +[#]: via: (https://opensource.com/article/19/12/cicd-resources) +[#]: author: (Jessica Cherry https://opensource.com/users/jrepka) + +顶级 CI / CD 资源，助您成功 +====== +随着企业期望实现无缝，灵活和可扩展的部署，持续集成和持续部署成为2019年的关键主题。 +![Plumbing tubes in many directions][1] + +对于 CI / CD 和 DevOps 来说，2019年是非常棒的一年。 Opensource 公司的作者分享了他们专注于无缝，灵活和可扩展部署时是如何朝着敏捷方向发展的。以下是我们2019年发布的 CI / CD 文章中的一些重要主题。 + +### 学习和提高您的 CI / CD 技能 + + +我们最喜欢的一些文章集中在 CI / CD 的实操经验上，并涵盖了许多方面。通常以[Jenkins][2]管道开始，布莱恩特的文章[用 Jenkins 构建 CI/CD 管道][4]（Building CI/CD pipelines with Jenkins）将为您提供足够的经验，以开始构建您的第一个管道。丹尼尔在 [用DevOps 管道进行自动验收测试][4]（Automate user acceptance testing with your DevOps pipeline ）一文中，提供了有关验收测试的重要信息，包括可用于独立测试的各种 CI / CD 应用程序。我写的[安全扫描DevOps 管道][5]（Security scanning your DevOps pipeline ）非常简短，其中的关键点是关于如何使用 Jenkins 平台在管道中设置安全性的教程。 + +### 交付工作流程 + + +威利•彼得•绍布赞扬为所有产品创建统一流水线的想法，以使[每种产品在一个CI / CD 流水线中持续建立起来，以管控所有产品][8]。这些文章将使您更好地了解团队成员加入工作流流程后会发生什么。 + +### CI / CD 如何影响企业 + + +2019年也是认识到 CI / CD 的业务影响以及它如何影响日常运营的一年。 + + + +Agnieszka Gancarczyk 分享了Red Hat[小型Scrum vs.大型Scrum][9] 的调查结果, 包括受访者对srums, + +敏捷运动及其对团队的影响的不同看法。威尔安•凯丽 的[持续部署如何影响企业][10], 包括开放式沟通的重要性，丹尼尔也强调了[DevOps 团队在3 种类型的指表板][11]中指标和可观测性的重要性。最后是安•玛丽•弗雷德的精彩文章： [不要在生产环境中测试？在生产环境中测试！][12] 详细说明了验收测试前在生产环境中测试的重要性。 + +感谢许多贡献者在2019年与 Opensource 的读者分享他们的见解，我期望在2020年里从他们那里了解更多有关 CI / CD 发展的信息。 + +-------------------------------------------------------------------------------- + +via: https://opensource.com/article/19/12/cicd-resources + +作者：[Jessica Cherry][a] +选题：[lujun9972][b] +译者：[Morisun029](https://github.com/译者ID) +校对：[校对者ID](https://github.com/校对者ID) + +本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 + +[a]: https://opensource.com/users/jrepka +[b]: https://github.com/lujun9972 +[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/plumbing_pipes_tutorial_how_behind_scenes.png?itok=F2Z8OJV1 (Plumbing tubes in many directions) +[2]: https://jenkins.io/ +[3]: https://opensource.com/article/19/9/intro-building-cicd-pipelines-jenkins +[4]: https://opensource.com/article/19/4/devops-pipeline-acceptance-testing +[5]: https://opensource.com/article/19/7/security-scanning-your-devops-pipeline +[6]: https://opensource.com/article/19/3/screwdriver-cicd +[7]: https://opensource.com/article/19/8/why-spinnaker-matters-cicd +[8]: https://opensource.com/article/19/7/cicd-pipeline-rule-them-all +[9]: https://opensource.com/article/19/3/small-scale-scrum-vs-large-scale-scrum +[10]: https://opensource.com/article/19/7/organizational-impact-continuous-deployment +[11]: https://opensource.com/article/19/7/dashboards-devops-teams +[12]: https://opensource.com/article/19/5/dont-test-production From edb60f006d958f27f280e0fdbdd8638725dee6b9 Mon Sep 17 00:00:00 2001 From: Morisun029 <54652937+Morisun029@users.noreply.github.com> Date: Fri, 24 Jan 2020 09:34:47 +0800 Subject: [PATCH 05/17] tranlated --- .../20191227 Top CI-CD resources to set you up for success.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/translated/tech/20191227 Top CI-CD resources to set you up for success.md b/translated/tech/20191227 Top CI-CD resources to set you up for success.md index 31ee2628b4..102e53d153 100644 --- a/translated/tech/20191227 Top CI-CD resources to set you up for success.md +++ b/translated/tech/20191227 Top CI-CD resources to set you up for success.md @@ -17,7 +17,7 @@ ### 学习和提高您的 CI / CD 技能 -我们最喜欢的一些文章集中在 CI / CD 的实操经验上，并涵盖了许多方面。通常以[Jenkins][2]管道开始，布莱恩特的文章[用 Jenkins 构建 CI/CD 管道][4]（Building CI/CD pipelines with Jenkins）将为您提供足够的经验，以开始构建您的第一个管道。丹尼尔在 [用DevOps 管道进行自动验收测试][4]（Automate user acceptance testing with your DevOps pipeline ）一文中，提供了有关验收测试的重要信息，包括可用于独立测试的各种 CI / CD 应用程序。我写的[安全扫描DevOps 管道][5]（Security scanning your DevOps pipeline ）非常简短，其中的关键点是关于如何使用 Jenkins 平台在管道中设置安全性的教程。 +我们最喜欢的一些文章集中在 CI / CD 的实操经验上，并涵盖了许多方面。通常以[Jenkins][2]管道开始，布莱恩特的文章[用 Jenkins 构建 CI/CD 管道][4]将为您提供足够的经验，以开始构建您的第一个管道。丹尼尔在 [用DevOps 管道进行自动验收测试][4]一文中，提供了有关验收测试的重要信息，包括可用于独立测试的各种 CI / CD 应用程序。我写的[安全扫描DevOps 管道][5]非常简短，其中的关键点是关于如何使用 Jenkins 平台在管道中设置安全性的教程。 ### 交付工作流程 From 6056bbda6f2b4b227584e92903e70bbcf0db6b72 Mon Sep 17 00:00:00 2001 From: Morisun029 <54652937+Morisun029@users.noreply.github.com> Date: Mon, 27 Jan 2020 18:25:12 +0800 Subject: [PATCH 06/17] translated --- ...n script to find bugs in your Overcloud.md | 178 ----------------- ...n script to find bugs in your Overcloud.md | 185 ++++++++++++++++++ 2 files changed, 185 insertions(+), 178 deletions(-) delete mode 100644 sources/tech/20200117 Use this Python script to find bugs in your Overcloud.md create mode 100644 translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md diff --git a/sources/tech/20200117 Use this Python script to find bugs in your Overcloud.md b/sources/tech/20200117 Use this Python script to find bugs in your Overcloud.md deleted file mode 100644 index 5f19f114b4..0000000000 --- a/sources/tech/20200117 Use this Python script to find bugs in your Overcloud.md +++ /dev/null @@ -1,178 +0,0 @@ -[#]: collector: (lujun9972) -[#]: translator: (Morisun029) -[#]: reviewer: ( ) -[#]: publisher: ( ) -[#]: url: ( ) -[#]: subject: (Use this Python script to find bugs in your Overcloud) -[#]: via: (https://opensource.com/article/20/1/logtool-root-cause-identification) -[#]: author: (Arkady Shtempler https://opensource.com/users/ashtempl) - -Use this Python script to find bugs in your Overcloud -====== -LogTool is a set of Python scripts that helps you investigate root -causes for problems in Overcloud nodes. -![Searching for code][1] - -OpenStack stores and manages a bunch of log files on its Overcloud nodes and Undercloud host. Therefore, it's not easy to use OSP log files to investigate a problem you're having, especially when you don't even know what could have caused the problem. - -If that's your situation, [LogTool][2] makes your life much easier! It saves you the time and work it would otherwise take to investigate the root cause manually. Based on a fuzzy string matching algorithm, LogTool provides all the unique error and warning messages that have occurred in the past. You can export these messages for a particular time period, such as 10 minutes ago, an hour ago, a day ago, and so on, based on timestamp in the log. - -LogTool is a set of Python scripts, and its main module, **PyTool.py**, is executed on the Undercloud host. Some operation modes use additional scripts that are executed directly on Overcloud nodes, such as exporting  errors and warnings from Overcloud logs. - -LogTool supports Python 2 and 3, and you can change the working directory according to your needs: [LogTool_Python2][3] or [LogTool_Python3][4]. - -### Operation modes - -#### 1\. Export errors and warnings from Overcloud logs - -This mode is used to extract all unique **ERROR** and **WARNING** messages from Overcloud nodes that took place in the past. As the user, you're prompted to provide the "since time" and debug level to be used for extraction of errors or warnings. For example, if something went wrong in the last 10 minutes, you're be able to extract error and warning messages for just that time period. - -This operation mode generates a directory containing a result file for each Overcloud node. A result file is a simple text file that is compressed (***.gz**) to reduce the time needed to download it from the Overcloud node. To convert a compressed file to a regular text file, you can use [zcat][5] or a similar tool. Also, some versions of Vi and any recent version of Emacs both support reading compressed data. The result file is divided into sections and contains a table of contents at the bottom. - -There are two kinds of log files LogTool detects on the fly: _Standard_ and _Not Standard_. In _Standard_, each log line has a known and defined structure: timestamp, debug level, msg, and so on. In _Not Standard_, the log's structure is unknown; it could be a third party's logs, for example. In the table of contents, you find a "Section name --> Line number" per section, for example: - - * **Raw Data - extracted Errors/Warnings from standard OSP logs since:** This section contains all extracted Error/Warning messages as-is without any modifications or changes. These messages are the raw data LogTool uses for fuzzy matching analysis. - * **Statistics - Number of Errors/Warnings per standard OSP log since:** In this section, you find the amount of Errors and Warnings per Standard log file. This may help you understand potential components used to search for the root cause of your issue. - * **Statistics - Unique messages, per STANDARD OSP log file since:** This section addresses unique Error and Warning messages since a timestamp you provide. For more details about each unique Error or Warning, search for the same message in the Raw Data section. - * **Statistics - Unique messages per NON STANDARD log file, since any time:** This section contains the unique messages in nonstandard log files. Unfortunately, LogTool cannot handle these log files in the same manner as Standard Log files; therefore, the "since time" you provide on extraction will be ignored, and you'll see all of the unique Errors/Warnings messages ever created. So first, scroll down to the table of contents at the bottom of the result file and review its sections—use the line indexes in the table of contents to jump to the relevant sections, where numbers 3, 4, and 5 are most important. - - - -#### 2\. Download all logs from Overcloud nodes - -Logs from all Overcloud nodes are compressed and downloaded to a local directory on your Undercloud host. - -#### 3\. Grep for a string in all Overcloud logs - -This mode "greps" (searches) a string provided by the user on all Overcloud logs. For example, you might want to see all logged messages for a specific request ID, such as the request ID for a "Create VM" that has failed. - -#### 4\. Check current CPU,RAM and Disk on Overcloud - -This mode displays the current CPU, RAM, and disk info on each Overcloud node. - -#### 5\. Execute user's script - -This enables users to run their own scripts on Overcloud nodes. For instance, say an Overcloud deployment failed, so you need to execute the same procedure on each Controller node to fix that. You can implement a "work around" script and to run it on Controllers using this mode. - -#### 6\. Download relevant logs only, by given timestamp - -This mode downloads only the Overcloud logs with _"Last Modified" > "given by user timestamp."_ For example, if you got an error 10 minutes ago, old log files won't be relevant, so downloading them is unnecessary. In addition, you can't (or shouldn't)  attach large files in some bug reporting tools, so this mode might help with making bug reports. - -#### 7\. Export errors and warnings from Undercloud logs - -This is the same as mode #1 above, but for Undercloud logs. - -#### 8\. Check Unhealthy dockers on the Overcloud - -This mode is used to search for unhealthy Dockers on nodes. - -#### 9\. Download OSP logs and run LogTool locally - -This mode allows you to download OSP logs from Jenkins or Log Storage (for example, **cougar11.scl.lab.tlv.redhat.com**) and to analyze the downloaded logs locally. - -#### 10\. Analyze deployment log on the Undercloud - -This mode may help you understand what went wrong during Overcloud or Undercloud deployment. Deployment logs are generated when the **\--log** option is used, for example, inside the **overcloud_deploy.sh** script; the problem is that such logs are not "friendly," and it's hard to understand what went wrong, especially when verbosity is set to **vv** or more, as this makes the log unreadable with a bunch of data inside it. This mode provides some details about all failed tasks. - -#### 11\. Analyze Gerrit(Zuul) failed gate logs - -This mode is used to analyze Gerrit(Zuul) log files. It automatically downloads all files from a remote Gerrit gate (HTTP download) and analyzes all files locally. - -### Installation - -LogTool is available on GitHub. Clone it to your Undercloud host with: - - -``` -`git clone https://github.com/zahlabut/LogTool.git` -``` - -Some external Python modules are also used by the tool: - -#### Paramiko - -This SSH module is usually installed on Undercloud by default. Use the following command to verify whether it's installed: - - -``` -`ls -a /usr/lib/python2.7/site-packages | grep paramiko` -``` - -If you need to install the module, on your Undercloud, execute the following commands: - - -``` -sudo easy_install pip -sudo pip install paramiko==2.1.1 -``` - -#### BeautifulSoup - -This HTML parser module is used only in modes where log files are downloaded using HTTP. It's used to parse the Artifacts HTML page to get all of the links in it. To install BeautifulSoup, enter this command: - - -``` -`pip install beautifulsoup4` -``` - -You can also use the [requirements.txt][6] file to install all the required modules by executing: - - -``` -`pip install -r requirements.txt` -``` - -### Configuration - -All required parameters are set directly inside the **PyTool.py** script. The defaults are: - - -``` -overcloud_logs_dir = '/var/log/containers' -overcloud_ssh_user = 'heat-admin' -overcloud_ssh_key = '/home/stack/.ssh/id_rsa' -undercloud_logs_dir ='/var/log/containers' -source_rc_file_path='/home/stack/' -``` - -### Usage - -This tool is interactive, so to start it, just enter: - - -``` -cd LogTool -python PyTool.py -``` - -### Troubleshooting LogTool - -Two log files are created on runtime: Error.log and Runtime.log*.* Please add the contents of both in the description of the issue you'd like to open. - -### Limitations - -LogTool is hardcoded to handle files up to 500 MB. - -### LogTool_Python3 script - -Get it at [github.com/zahlabut/LogTool][2] - --------------------------------------------------------------------------------- - -via: https://opensource.com/article/20/1/logtool-root-cause-identification - -作者：[Arkady Shtempler][a] -选题：[lujun9972][b] -译者：[译者ID](https://github.com/译者ID) -校对：[校对者ID](https://github.com/校对者ID) - -本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 - -[a]: https://opensource.com/users/ashtempl -[b]: https://github.com/lujun9972 -[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/search_find_code_python_programming.png?itok=ynSL8XRV (Searching for code) -[2]: https://github.com/zahlabut/LogTool -[3]: https://github.com/zahlabut/LogTool/tree/master/LogTool_Python2 -[4]: https://github.com/zahlabut/LogTool/tree/master/LogTool_Python3 -[5]: https://opensource.com/article/19/2/getting-started-cat-command -[6]: https://github.com/zahlabut/LogTool/blob/master/LogTool_Python3/requirements.txt diff --git a/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md b/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md new file mode 100644 index 0000000000..b8c1393b2b --- /dev/null +++ b/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md @@ -0,0 +1,185 @@ +[#]: collector: (lujun9972) +[#]: translator: (Morisun029) +[#]: reviewer: ( ) +[#]: publisher: ( ) +[#]: url: ( ) +[#]: subject: (Use this Python script to find bugs in your Overcloud) +[#]: via: (https://opensource.com/article/20/1/logtool-root-cause-identification) +[#]: author: (Arkady Shtempler https://opensource.com/users/ashtempl) + +用 Python 脚本发现 Overcloud 中的问题 +====== +LogTool 是一组 Python 脚本，可帮助你找出 Overcloud 节点中问题的根本原因。 +![Searching for code][1] + +OpenStack 在其 Overcloud 节点和 Undercloud 主机上存储和管理了一堆日志文件。因此，使用 OSP 日志文件来排查遇到的问题并不是一件容易的事，尤其在你甚至都不知道是什么原因导致问题时。 + +如果你正处于这种情况，那么 [LogTool][2] 可以使你的生活变得更加轻松！它会为你节省本需要人工排查问题所需的时间和精力。 LogTool 基于模糊字符串匹配算法，可提供过去发生的所有唯一错误和警告信息。你可以根据日志中的时间戳导出特定时间段（例如10分钟前，一个小时前，一天前等）的这些信息。 + +LogTool 是一组 Python 脚本，其主要模块 PyTool.py 在 Undercloud 主机上执行。某些操作模式使用直接在Overcloud 节点上执行的其他脚本，例如从 Overcloud 日志中导出错误和警告信息。 + +LogTool 支持 Python 2 和 Python 3，你可以根据需要更改工作目录：[LogTool_Python2][3] or [LogTool_Python3][4]. + +### 操作方式 + +#### 1\. 从 Overcloud 日志中导出错误和警告信息 + +此模式用于从过去发生的 Overcloud 节点中提取 **错误** 和 **警告** 信息。作为用户，系统将提示你“开始时间”和“调试级别”，以用于提取错误或警告消息。例如，如果在过去10分钟内出了问题，你则可以只提取该时间段内的错误和警告消息。 + + +此操作模式将为每个 Overcloud 节点生成一个包含结果文件的目录。结果文件是经过压缩(***.gz**)的简单文本文件，以减少从 Overcloud 节点下载所需的时间。将压缩文件转换为常规文本文件，可以使用 zcat 或类似工具。此外，Vi 的某些版本和 Emacs 的任何最新版本均支持读取压缩数据。结果文件分为几部分，并在底部包含目录。 + + +LogTool 可以即时检测两种日志文件：标准和非标准。在标准文件中，每条日志行都有一个已知的和已定义的结构：时间戳，调试级别，信息等等。在非标准文件中，日志的结构未知。例如，它可能是第三方的日志。在目录中，你可以找到每个部分的"名称 --> 行号" 例如： + + + * **原始数据 - 从标准 OSP 日志中提取的错误/警告消息:** 这部分包含所有提取的错误/警告消息，没有任何修改或更改。这些消息是 LogTool 用于模糊匹配分析的原始数据。 + + * **统计信息 - 每个标准 OSP 日志的错误/警告信息数量:** 在此部分，你将找到每个标准日志文件的错误和警告数量。这些信息可以帮助你了解用于排查问题根本原因的潜在组件。 + + * **统计信息 - 每个标准 OSP 日志文件的唯一消息:** 这部分提供指定时间戳内的唯一的错误和警告消息。有关每个唯一错误或警告的更多详细信息，请在“原始数据”部分中查找相同的消息。 + + * **统计信息 - 每个非标准日志文件在任意时间的唯一消息:** 此部分包含非标准日志文件中的唯一消息。遗憾的是，LogTool 无法像标准日志文件那样的处理方式处理这些日志文件。因此，在你提取“特定时间”的日志信息时会被忽略，你会看到过去创建的所有唯一的错误/警告消息。因此，首先，向下滚动到结果文件底部的目录并查看其部分-使用目录中的行索引跳到相关部分，其中第3、4和5行的信息最重要。 + + + +#### 2\. 从 Overcloud 节点下载所有日志 + +所有 Overcloud 节点的日志将被压缩并下载到 Undercloud 主机上的本地目录。 + +#### 3\. 所有 Overcloud 日志中使用 Grep 搜索字符串 + + +该模式中使用“greps”来搜索由用户在所有 Overcloud 日志上提供的字符串。例如，你可能希望查看特定请求的所有日志消息，例如，“创建VM”的失败的请求ID。 + +#### 4\. 检查 Overcloud 上当前的 CPU，RAM 和磁盘使用情况 + +该模式显示每个 Overcloud 节点上的当前 CPU，RAM 和磁盘信息。 + +#### 5\. 执行用户脚本 + +该模式使用户可以在 Overcloud 节点上运行自己的脚本。例如，假设 Overcloud 部署失败，你就需要在每个Controller 节点上执行相同的过程来修复该问题。你可以实现“替代方法”脚本，并使用此模式在 Controller 上运行它。 + +#### 6\. 仅按给定的时间戳下载相关日志 + +此模式仅下载 Overcloud 上 “给定的时间戳”的“上次修改时间”的日志。例如，如果10分钟前出现错误，则与旧日志文件就没有关系，因此无需下载。此外，你不能（或不应）在某些错误报告工具中附加大文件，因此此模式可能有助于编写错误报告。 + +#### 7\. 从 Undercloud 日志中导出错误和警告信息 + +这与上面的模式＃1相同。 + +#### 8\. 在 Overcloud 上检查不健康的 docker + +此模式用于在节点上搜索不正常的 Docker。 + +#### 9\. 下载 OSP 日志并在本地运行 LogTool + +此模式允许你从 Jenkins 或 Log Storage 下载 OSP 日志 (例如, **cougar11.scl.lab.tlv.redhat.com**)，并在本地分析。 + +#### 10\. 在 Undercloud 上分析部署日志 + + +此模式可以帮助你了解 Overcloud 或 Undercloud 部署过程中出了什么问题。例如，在**overcloud_deploy.sh** 脚本中，使用 **\--log**选项时会生成部署日志；此类日志的问题是“不友好”，你很难理解是什么出了问题，尤其是当详细程度设置为**vv** 或更高时，使得日志中的数据难以读取。此模式提供有关所有失败任务的详细信息。 + +#### 11\. 分析 Gerrit（Zuul）失败的日志 + +此模式用于分析 Gerrit（Zuul）日志文件。它会自动从远程 Gerrit 门下载所有文件（HTTP下载）并在本地进行分析。 + +### 安装 + +GitHub 上有 LogTool，使用以下命令将其克隆到你的 Undercloud 主机： + + +``` +`git clone https://github.com/zahlabut/LogTool.git` +``` + +该工具还使用了一些外部 Python 模块： + +#### Paramiko + +默认情况下，SSH 模块通常会安装在 Undercloud 上。使用以下命令来验证是否已安装： + + +``` +`ls -a /usr/lib/python2.7/site-packages | grep paramiko` +``` + +如果需要安装模块，请在 Undercloud 上执行以下命令： + + +``` +sudo easy_install pip +sudo pip install paramiko==2.1.1 +``` + +#### BeautifulSoup + +此 HTML 解析器模块仅在使用 HTTP 下载日志文件的模式下使用。它用于解析 Artifacts HTML 页面以获取其中的所有链接。安装 BeautifulSoup，请输入以下命令： + +``` +`pip install beautifulsoup4` +``` + +你还可以通过执行以下命令使用[requirements.txt][6]文件安装所有必需的模块： + + +``` +`pip install -r requirements.txt` +``` + +### 配置 + + +所有必需的参数都直接在**PyTool.py**脚本中设置。默认值为： + +``` +overcloud_logs_dir = '/var/log/containers' +overcloud_ssh_user = 'heat-admin' +overcloud_ssh_key = '/home/stack/.ssh/id_rsa' +undercloud_logs_dir ='/var/log/containers' +source_rc_file_path='/home/stack/' +``` + +### 用法 + +此工具是交互式的，因此要启动它，只需输入： + + +``` +cd LogTool +python PyTool.py +``` + +### 排除 LogTool 故障 + + +在运行时会创建两个日志文件：Error.log 和 Runtime.log*.* 请在你要打开的问题的描述中添加两者的内容。 + +### 局限性 + +LogTool 进行硬编码以处理最大500 MB 的文件。 + +### LogTool_Python3 脚本 + +在 [github.com/zahlabut/LogTool][2] 获取。 + +-------------------------------------------------------------------------------- + +via: https://opensource.com/article/20/1/logtool-root-cause-identification + +作者：[Arkady Shtempler][a] +选题：[lujun9972][b] +译者：[Morisun029](https://github.com/译者ID) +校对：[校对者ID](https://github.com/校对者ID) + +本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 + +[a]: https://opensource.com/users/ashtempl +[b]: https://github.com/lujun9972 +[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/search_find_code_python_programming.png?itok=ynSL8XRV (Searching for code) +[2]: https://github.com/zahlabut/LogTool +[3]: https://github.com/zahlabut/LogTool/tree/master/LogTool_Python2 +[4]: https://github.com/zahlabut/LogTool/tree/master/LogTool_Python3 +[5]: https://opensource.com/article/19/2/getting-started-cat-command +[6]: https://github.com/zahlabut/LogTool/blob/master/LogTool_Python3/requirements.txt From d63930c4dc5b95e50a604b78e368d69419a453e6 Mon Sep 17 00:00:00 2001 From: Morisun029 <54652937+Morisun029@users.noreply.github.com> Date: Mon, 27 Jan 2020 18:49:22 +0800 Subject: [PATCH 07/17] translated From 7e92c4c9bc9c6810088f63935ac001153c9f31cb Mon Sep 17 00:00:00 2001 From: Morisun029 <54652937+Morisun029@users.noreply.github.com> Date: Mon, 27 Jan 2020 18:52:50 +0800 Subject: [PATCH 08/17] translated --- ...0117 Use this Python script to find bugs in your Overcloud.md | 1 - 1 file changed, 1 deletion(-) diff --git a/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md b/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md index b8c1393b2b..82ac2b8da6 100644 --- a/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md +++ b/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md @@ -42,7 +42,6 @@ LogTool 可以即时检测两种日志文件：标准和非标准。在标准文 * **统计信息 - 每个非标准日志文件在任意时间的唯一消息:** 此部分包含非标准日志文件中的唯一消息。遗憾的是，LogTool 无法像标准日志文件那样的处理方式处理这些日志文件。因此，在你提取“特定时间”的日志信息时会被忽略，你会看到过去创建的所有唯一的错误/警告消息。因此，首先，向下滚动到结果文件底部的目录并查看其部分-使用目录中的行索引跳到相关部分，其中第3、4和5行的信息最重要。 - #### 2\. 从 Overcloud 节点下载所有日志 所有 Overcloud 节点的日志将被压缩并下载到 Undercloud 主机上的本地目录。 From 356077306dbe99d676ddcf036f8dd2ebfa346d9f Mon Sep 17 00:00:00 2001 From: Morisun029 <54652937+Morisun029@users.noreply.github.com> Date: Mon, 27 Jan 2020 18:54:31 +0800 Subject: [PATCH 09/17] Update 20200117 Use this Python script to find bugs in your Overcloud.md --- ...0117 Use this Python script to find bugs in your Overcloud.md | 1 - 1 file changed, 1 deletion(-) diff --git a/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md b/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md index 82ac2b8da6..eb2b7609b6 100644 --- a/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md +++ b/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md @@ -129,7 +129,6 @@ sudo pip install paramiko==2.1.1 ### 配置 - 所有必需的参数都直接在**PyTool.py**脚本中设置。默认值为： ``` From 4df8003a85368999c21de0c0eaf80824f1a993b9 Mon Sep 17 00:00:00 2001 From: Morisun029 <54652937+Morisun029@users.noreply.github.com> Date: Mon, 27 Jan 2020 18:58:44 +0800 Subject: [PATCH 10/17] Update 20200117 Use this Python script to find bugs in your Overcloud.md --- ...0117 Use this Python script to find bugs in your Overcloud.md | 1 - 1 file changed, 1 deletion(-) diff --git a/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md b/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md index eb2b7609b6..7ee1142f8e 100644 --- a/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md +++ b/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md @@ -143,7 +143,6 @@ source_rc_file_path='/home/stack/' 此工具是交互式的，因此要启动它，只需输入： - ``` cd LogTool python PyTool.py From d59e7c5e9f2219478ab34e3f27fb30a088c16380 Mon Sep 17 00:00:00 2001 From: Morisun029 <54652937+Morisun029@users.noreply.github.com> Date: Wed, 29 Jan 2020 18:56:34 +0800 Subject: [PATCH 11/17] translated --- ...117 Use this Python script to find bugs in your Overcloud.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md b/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md index 7ee1142f8e..c6e7d17955 100644 --- a/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md +++ b/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md @@ -41,7 +41,6 @@ LogTool 可以即时检测两种日志文件：标准和非标准。在标准文 * **统计信息 - 每个非标准日志文件在任意时间的唯一消息:** 此部分包含非标准日志文件中的唯一消息。遗憾的是，LogTool 无法像标准日志文件那样的处理方式处理这些日志文件。因此，在你提取“特定时间”的日志信息时会被忽略，你会看到过去创建的所有唯一的错误/警告消息。因此，首先，向下滚动到结果文件底部的目录并查看其部分-使用目录中的行索引跳到相关部分，其中第3、4和5行的信息最重要。 - #### 2\. 从 Overcloud 节点下载所有日志 所有 Overcloud 节点的日志将被压缩并下载到 Undercloud 主机上的本地目录。 @@ -170,6 +169,7 @@ via: https://opensource.com/article/20/1/logtool-root-cause-identification 译者：[Morisun029](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID) + 本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 [a]: https://opensource.com/users/ashtempl From 271e95c428174fafa17c906b8b2d65dbd8ca5978 Mon Sep 17 00:00:00 2001 From: Morisun029 <54652937+Morisun029@users.noreply.github.com> Date: Fri, 7 Feb 2020 20:08:19 +0800 Subject: [PATCH 12/17] Revert "Merge pull request #13 from Morisun029/Morisun029-patch-1" This reverts commit 4309ece5f62470e36bb79c5602a03fa9db7f3db6, reversing changes made to 356077306dbe99d676ddcf036f8dd2ebfa346d9f. --- ...0117 Use this Python script to find bugs in your Overcloud.md | 1 + 1 file changed, 1 insertion(+) diff --git a/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md b/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md index c6e7d17955..9e7857796a 100644 --- a/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md +++ b/translated/tech/20200117 Use this Python script to find bugs in your Overcloud.md @@ -142,6 +142,7 @@ source_rc_file_path='/home/stack/' 此工具是交互式的，因此要启动它，只需输入： + ``` cd LogTool python PyTool.py From 2a79b0cb328816492b6aabfeec7ebff20edc2111 Mon Sep 17 00:00:00 2001 From: Morisun029 <54652937+Morisun029@users.noreply.github.com> Date: Fri, 7 Feb 2020 20:31:03 +0800 Subject: [PATCH 13/17] delete a file --- ...-CD resources to set you up for success.md | 64 ------------------- 1 file changed, 64 deletions(-) delete mode 100644 translated/tech/20191227 Top CI-CD resources to set you up for success.md diff --git a/translated/tech/20191227 Top CI-CD resources to set you up for success.md b/translated/tech/20191227 Top CI-CD resources to set you up for success.md deleted file mode 100644 index 102e53d153..0000000000 --- a/translated/tech/20191227 Top CI-CD resources to set you up for success.md +++ /dev/null @@ -1,64 +0,0 @@ -[#]: collector: (lujun9972) -[#]: translator: (Morisun029) -[#]: reviewer: ( ) -[#]: publisher: ( ) -[#]: url: ( ) -[#]: subject: (Top CI/CD resources to set you up for success) -[#]: via: (https://opensource.com/article/19/12/cicd-resources) -[#]: author: (Jessica Cherry https://opensource.com/users/jrepka) - -顶级 CI / CD 资源，助您成功 -====== -随着企业期望实现无缝，灵活和可扩展的部署，持续集成和持续部署成为2019年的关键主题。 -![Plumbing tubes in many directions][1] - -对于 CI / CD 和 DevOps 来说，2019年是非常棒的一年。 Opensource 公司的作者分享了他们专注于无缝，灵活和可扩展部署时是如何朝着敏捷方向发展的。以下是我们2019年发布的 CI / CD 文章中的一些重要主题。 - -### 学习和提高您的 CI / CD 技能 - - -我们最喜欢的一些文章集中在 CI / CD 的实操经验上，并涵盖了许多方面。通常以[Jenkins][2]管道开始，布莱恩特的文章[用 Jenkins 构建 CI/CD 管道][4]将为您提供足够的经验，以开始构建您的第一个管道。丹尼尔在 [用DevOps 管道进行自动验收测试][4]一文中，提供了有关验收测试的重要信息，包括可用于独立测试的各种 CI / CD 应用程序。我写的[安全扫描DevOps 管道][5]非常简短，其中的关键点是关于如何使用 Jenkins 平台在管道中设置安全性的教程。 - -### 交付工作流程 - - -威利•彼得•绍布赞扬为所有产品创建统一流水线的想法，以使[每种产品在一个CI / CD 流水线中持续建立起来，以管控所有产品][8]。这些文章将使您更好地了解团队成员加入工作流流程后会发生什么。 - -### CI / CD 如何影响企业 - - -2019年也是认识到 CI / CD 的业务影响以及它如何影响日常运营的一年。 - - - -Agnieszka Gancarczyk 分享了Red Hat[小型Scrum vs.大型Scrum][9] 的调查结果, 包括受访者对srums, - -敏捷运动及其对团队的影响的不同看法。威尔安•凯丽 的[持续部署如何影响企业][10], 包括开放式沟通的重要性，丹尼尔也强调了[DevOps 团队在3 种类型的指表板][11]中指标和可观测性的重要性。最后是安•玛丽•弗雷德的精彩文章： [不要在生产环境中测试？在生产环境中测试！][12] 详细说明了验收测试前在生产环境中测试的重要性。 - -感谢许多贡献者在2019年与 Opensource 的读者分享他们的见解，我期望在2020年里从他们那里了解更多有关 CI / CD 发展的信息。 - --------------------------------------------------------------------------------- - -via: https://opensource.com/article/19/12/cicd-resources - -作者：[Jessica Cherry][a] -选题：[lujun9972][b] -译者：[Morisun029](https://github.com/译者ID) -校对：[校对者ID](https://github.com/校对者ID) - -本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 - -[a]: https://opensource.com/users/jrepka -[b]: https://github.com/lujun9972 -[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/plumbing_pipes_tutorial_how_behind_scenes.png?itok=F2Z8OJV1 (Plumbing tubes in many directions) -[2]: https://jenkins.io/ -[3]: https://opensource.com/article/19/9/intro-building-cicd-pipelines-jenkins -[4]: https://opensource.com/article/19/4/devops-pipeline-acceptance-testing -[5]: https://opensource.com/article/19/7/security-scanning-your-devops-pipeline -[6]: https://opensource.com/article/19/3/screwdriver-cicd -[7]: https://opensource.com/article/19/8/why-spinnaker-matters-cicd -[8]: https://opensource.com/article/19/7/cicd-pipeline-rule-them-all -[9]: https://opensource.com/article/19/3/small-scale-scrum-vs-large-scale-scrum -[10]: https://opensource.com/article/19/7/organizational-impact-continuous-deployment -[11]: https://opensource.com/article/19/7/dashboards-devops-teams -[12]: https://opensource.com/article/19/5/dont-test-production From 3d4e7d8afbaee356d1bd792ab11d262c57469907 Mon Sep 17 00:00:00 2001 From: Morisun029 <54652937+Morisun029@users.noreply.github.com> Date: Fri, 7 Feb 2020 20:36:48 +0800 Subject: [PATCH 14/17] update --- ...-CD resources to set you up for success.md | 64 +++++++++++++++++++ 1 file changed, 64 insertions(+) create mode 100644 translated/tech/20191227 Top CI-CD resources to set you up for success.md diff --git a/translated/tech/20191227 Top CI-CD resources to set you up for success.md b/translated/tech/20191227 Top CI-CD resources to set you up for success.md new file mode 100644 index 0000000000..102e53d153 --- /dev/null +++ b/translated/tech/20191227 Top CI-CD resources to set you up for success.md @@ -0,0 +1,64 @@ +[#]: collector: (lujun9972) +[#]: translator: (Morisun029) +[#]: reviewer: ( ) +[#]: publisher: ( ) +[#]: url: ( ) +[#]: subject: (Top CI/CD resources to set you up for success) +[#]: via: (https://opensource.com/article/19/12/cicd-resources) +[#]: author: (Jessica Cherry https://opensource.com/users/jrepka) + +顶级 CI / CD 资源，助您成功 +====== +随着企业期望实现无缝，灵活和可扩展的部署，持续集成和持续部署成为2019年的关键主题。 +![Plumbing tubes in many directions][1] + +对于 CI / CD 和 DevOps 来说，2019年是非常棒的一年。 Opensource 公司的作者分享了他们专注于无缝，灵活和可扩展部署时是如何朝着敏捷方向发展的。以下是我们2019年发布的 CI / CD 文章中的一些重要主题。 + +### 学习和提高您的 CI / CD 技能 + + +我们最喜欢的一些文章集中在 CI / CD 的实操经验上，并涵盖了许多方面。通常以[Jenkins][2]管道开始，布莱恩特的文章[用 Jenkins 构建 CI/CD 管道][4]将为您提供足够的经验，以开始构建您的第一个管道。丹尼尔在 [用DevOps 管道进行自动验收测试][4]一文中，提供了有关验收测试的重要信息，包括可用于独立测试的各种 CI / CD 应用程序。我写的[安全扫描DevOps 管道][5]非常简短，其中的关键点是关于如何使用 Jenkins 平台在管道中设置安全性的教程。 + +### 交付工作流程 + + +威利•彼得•绍布赞扬为所有产品创建统一流水线的想法，以使[每种产品在一个CI / CD 流水线中持续建立起来，以管控所有产品][8]。这些文章将使您更好地了解团队成员加入工作流流程后会发生什么。 + +### CI / CD 如何影响企业 + + +2019年也是认识到 CI / CD 的业务影响以及它如何影响日常运营的一年。 + + + +Agnieszka Gancarczyk 分享了Red Hat[小型Scrum vs.大型Scrum][9] 的调查结果, 包括受访者对srums, + +敏捷运动及其对团队的影响的不同看法。威尔安•凯丽 的[持续部署如何影响企业][10], 包括开放式沟通的重要性，丹尼尔也强调了[DevOps 团队在3 种类型的指表板][11]中指标和可观测性的重要性。最后是安•玛丽•弗雷德的精彩文章： [不要在生产环境中测试？在生产环境中测试！][12] 详细说明了验收测试前在生产环境中测试的重要性。 + +感谢许多贡献者在2019年与 Opensource 的读者分享他们的见解，我期望在2020年里从他们那里了解更多有关 CI / CD 发展的信息。 + +-------------------------------------------------------------------------------- + +via: https://opensource.com/article/19/12/cicd-resources + +作者：[Jessica Cherry][a] +选题：[lujun9972][b] +译者：[Morisun029](https://github.com/译者ID) +校对：[校对者ID](https://github.com/校对者ID) + +本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 + +[a]: https://opensource.com/users/jrepka +[b]: https://github.com/lujun9972 +[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/plumbing_pipes_tutorial_how_behind_scenes.png?itok=F2Z8OJV1 (Plumbing tubes in many directions) +[2]: https://jenkins.io/ +[3]: https://opensource.com/article/19/9/intro-building-cicd-pipelines-jenkins +[4]: https://opensource.com/article/19/4/devops-pipeline-acceptance-testing +[5]: https://opensource.com/article/19/7/security-scanning-your-devops-pipeline +[6]: https://opensource.com/article/19/3/screwdriver-cicd +[7]: https://opensource.com/article/19/8/why-spinnaker-matters-cicd +[8]: https://opensource.com/article/19/7/cicd-pipeline-rule-them-all +[9]: https://opensource.com/article/19/3/small-scale-scrum-vs-large-scale-scrum +[10]: https://opensource.com/article/19/7/organizational-impact-continuous-deployment +[11]: https://opensource.com/article/19/7/dashboards-devops-teams +[12]: https://opensource.com/article/19/5/dont-test-production From 97885b764045cee63f1af7b85edc0fcb5c309d7e Mon Sep 17 00:00:00 2001 From: Morisun029 <54652937+Morisun029@users.noreply.github.com> Date: Fri, 7 Feb 2020 20:43:55 +0800 Subject: [PATCH 15/17] Revert "update" This reverts commit 3d4e7d8afbaee356d1bd792ab11d262c57469907. --- ...-CD resources to set you up for success.md | 64 ------------------- 1 file changed, 64 deletions(-) delete mode 100644 translated/tech/20191227 Top CI-CD resources to set you up for success.md diff --git a/translated/tech/20191227 Top CI-CD resources to set you up for success.md b/translated/tech/20191227 Top CI-CD resources to set you up for success.md deleted file mode 100644 index 102e53d153..0000000000 --- a/translated/tech/20191227 Top CI-CD resources to set you up for success.md +++ /dev/null @@ -1,64 +0,0 @@ -[#]: collector: (lujun9972) -[#]: translator: (Morisun029) -[#]: reviewer: ( ) -[#]: publisher: ( ) -[#]: url: ( ) -[#]: subject: (Top CI/CD resources to set you up for success) -[#]: via: (https://opensource.com/article/19/12/cicd-resources) -[#]: author: (Jessica Cherry https://opensource.com/users/jrepka) - -顶级 CI / CD 资源，助您成功 -====== -随着企业期望实现无缝，灵活和可扩展的部署，持续集成和持续部署成为2019年的关键主题。 -![Plumbing tubes in many directions][1] - -对于 CI / CD 和 DevOps 来说，2019年是非常棒的一年。 Opensource 公司的作者分享了他们专注于无缝，灵活和可扩展部署时是如何朝着敏捷方向发展的。以下是我们2019年发布的 CI / CD 文章中的一些重要主题。 - -### 学习和提高您的 CI / CD 技能 - - -我们最喜欢的一些文章集中在 CI / CD 的实操经验上，并涵盖了许多方面。通常以[Jenkins][2]管道开始，布莱恩特的文章[用 Jenkins 构建 CI/CD 管道][4]将为您提供足够的经验，以开始构建您的第一个管道。丹尼尔在 [用DevOps 管道进行自动验收测试][4]一文中，提供了有关验收测试的重要信息，包括可用于独立测试的各种 CI / CD 应用程序。我写的[安全扫描DevOps 管道][5]非常简短，其中的关键点是关于如何使用 Jenkins 平台在管道中设置安全性的教程。 - -### 交付工作流程 - - -威利•彼得•绍布赞扬为所有产品创建统一流水线的想法，以使[每种产品在一个CI / CD 流水线中持续建立起来，以管控所有产品][8]。这些文章将使您更好地了解团队成员加入工作流流程后会发生什么。 - -### CI / CD 如何影响企业 - - -2019年也是认识到 CI / CD 的业务影响以及它如何影响日常运营的一年。 - - - -Agnieszka Gancarczyk 分享了Red Hat[小型Scrum vs.大型Scrum][9] 的调查结果, 包括受访者对srums, - -敏捷运动及其对团队的影响的不同看法。威尔安•凯丽 的[持续部署如何影响企业][10], 包括开放式沟通的重要性，丹尼尔也强调了[DevOps 团队在3 种类型的指表板][11]中指标和可观测性的重要性。最后是安•玛丽•弗雷德的精彩文章： [不要在生产环境中测试？在生产环境中测试！][12] 详细说明了验收测试前在生产环境中测试的重要性。 - -感谢许多贡献者在2019年与 Opensource 的读者分享他们的见解，我期望在2020年里从他们那里了解更多有关 CI / CD 发展的信息。 - --------------------------------------------------------------------------------- - -via: https://opensource.com/article/19/12/cicd-resources - -作者：[Jessica Cherry][a] -选题：[lujun9972][b] -译者：[Morisun029](https://github.com/译者ID) -校对：[校对者ID](https://github.com/校对者ID) - -本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 - -[a]: https://opensource.com/users/jrepka -[b]: https://github.com/lujun9972 -[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/plumbing_pipes_tutorial_how_behind_scenes.png?itok=F2Z8OJV1 (Plumbing tubes in many directions) -[2]: https://jenkins.io/ -[3]: https://opensource.com/article/19/9/intro-building-cicd-pipelines-jenkins -[4]: https://opensource.com/article/19/4/devops-pipeline-acceptance-testing -[5]: https://opensource.com/article/19/7/security-scanning-your-devops-pipeline -[6]: https://opensource.com/article/19/3/screwdriver-cicd -[7]: https://opensource.com/article/19/8/why-spinnaker-matters-cicd -[8]: https://opensource.com/article/19/7/cicd-pipeline-rule-them-all -[9]: https://opensource.com/article/19/3/small-scale-scrum-vs-large-scale-scrum -[10]: https://opensource.com/article/19/7/organizational-impact-continuous-deployment -[11]: https://opensource.com/article/19/7/dashboards-devops-teams -[12]: https://opensource.com/article/19/5/dont-test-production From 40865a5e3eff782497f00e63d9634989a89dc77f Mon Sep 17 00:00:00 2001 From: Morisun029 <54652937+Morisun029@users.noreply.github.com> Date: Fri, 7 Feb 2020 20:51:09 +0800 Subject: [PATCH 16/17] translated --- ...-CD resources to set you up for success.md | 64 +++++++++++++++++++ 1 file changed, 64 insertions(+) create mode 100644 translated/tech/20191227 Top CI-CD resources to set you up for success.md diff --git a/translated/tech/20191227 Top CI-CD resources to set you up for success.md b/translated/tech/20191227 Top CI-CD resources to set you up for success.md new file mode 100644 index 0000000000..102e53d153 --- /dev/null +++ b/translated/tech/20191227 Top CI-CD resources to set you up for success.md @@ -0,0 +1,64 @@ +[#]: collector: (lujun9972) +[#]: translator: (Morisun029) +[#]: reviewer: ( ) +[#]: publisher: ( ) +[#]: url: ( ) +[#]: subject: (Top CI/CD resources to set you up for success) +[#]: via: (https://opensource.com/article/19/12/cicd-resources) +[#]: author: (Jessica Cherry https://opensource.com/users/jrepka) + +顶级 CI / CD 资源，助您成功 +====== +随着企业期望实现无缝，灵活和可扩展的部署，持续集成和持续部署成为2019年的关键主题。 +![Plumbing tubes in many directions][1] + +对于 CI / CD 和 DevOps 来说，2019年是非常棒的一年。 Opensource 公司的作者分享了他们专注于无缝，灵活和可扩展部署时是如何朝着敏捷方向发展的。以下是我们2019年发布的 CI / CD 文章中的一些重要主题。 + +### 学习和提高您的 CI / CD 技能 + + +我们最喜欢的一些文章集中在 CI / CD 的实操经验上，并涵盖了许多方面。通常以[Jenkins][2]管道开始，布莱恩特的文章[用 Jenkins 构建 CI/CD 管道][4]将为您提供足够的经验，以开始构建您的第一个管道。丹尼尔在 [用DevOps 管道进行自动验收测试][4]一文中，提供了有关验收测试的重要信息，包括可用于独立测试的各种 CI / CD 应用程序。我写的[安全扫描DevOps 管道][5]非常简短，其中的关键点是关于如何使用 Jenkins 平台在管道中设置安全性的教程。 + +### 交付工作流程 + + +威利•彼得•绍布赞扬为所有产品创建统一流水线的想法，以使[每种产品在一个CI / CD 流水线中持续建立起来，以管控所有产品][8]。这些文章将使您更好地了解团队成员加入工作流流程后会发生什么。 + +### CI / CD 如何影响企业 + + +2019年也是认识到 CI / CD 的业务影响以及它如何影响日常运营的一年。 + + + +Agnieszka Gancarczyk 分享了Red Hat[小型Scrum vs.大型Scrum][9] 的调查结果, 包括受访者对srums, + +敏捷运动及其对团队的影响的不同看法。威尔安•凯丽 的[持续部署如何影响企业][10], 包括开放式沟通的重要性，丹尼尔也强调了[DevOps 团队在3 种类型的指表板][11]中指标和可观测性的重要性。最后是安•玛丽•弗雷德的精彩文章： [不要在生产环境中测试？在生产环境中测试！][12] 详细说明了验收测试前在生产环境中测试的重要性。 + +感谢许多贡献者在2019年与 Opensource 的读者分享他们的见解，我期望在2020年里从他们那里了解更多有关 CI / CD 发展的信息。 + +-------------------------------------------------------------------------------- + +via: https://opensource.com/article/19/12/cicd-resources + +作者：[Jessica Cherry][a] +选题：[lujun9972][b] +译者：[Morisun029](https://github.com/译者ID) +校对：[校对者ID](https://github.com/校对者ID) + +本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 + +[a]: https://opensource.com/users/jrepka +[b]: https://github.com/lujun9972 +[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/plumbing_pipes_tutorial_how_behind_scenes.png?itok=F2Z8OJV1 (Plumbing tubes in many directions) +[2]: https://jenkins.io/ +[3]: https://opensource.com/article/19/9/intro-building-cicd-pipelines-jenkins +[4]: https://opensource.com/article/19/4/devops-pipeline-acceptance-testing +[5]: https://opensource.com/article/19/7/security-scanning-your-devops-pipeline +[6]: https://opensource.com/article/19/3/screwdriver-cicd +[7]: https://opensource.com/article/19/8/why-spinnaker-matters-cicd +[8]: https://opensource.com/article/19/7/cicd-pipeline-rule-them-all +[9]: https://opensource.com/article/19/3/small-scale-scrum-vs-large-scale-scrum +[10]: https://opensource.com/article/19/7/organizational-impact-continuous-deployment +[11]: https://opensource.com/article/19/7/dashboards-devops-teams +[12]: https://opensource.com/article/19/5/dont-test-production From 96c2f966ec1e33ffac137ba7fac5ca3db70eebdb Mon Sep 17 00:00:00 2001 From: Morisun029 <54652937+Morisun029@users.noreply.github.com> Date: Sat, 8 Feb 2020 18:36:28 +0800 Subject: [PATCH 17/17] delete source file --- ...-CD resources to set you up for success.md | 57 ------------------- 1 file changed, 57 deletions(-) delete mode 100644 sources/tech/20191227 Top CI-CD resources to set you up for success.md diff --git a/sources/tech/20191227 Top CI-CD resources to set you up for success.md b/sources/tech/20191227 Top CI-CD resources to set you up for success.md deleted file mode 100644 index d3da7c4d09..0000000000 --- a/sources/tech/20191227 Top CI-CD resources to set you up for success.md +++ /dev/null @@ -1,57 +0,0 @@ -[#]: collector: (lujun9972) -[#]: translator: (Morisun029) -[#]: reviewer: ( ) -[#]: publisher: ( ) -[#]: url: ( ) -[#]: subject: (Top CI/CD resources to set you up for success) -[#]: via: (https://opensource.com/article/19/12/cicd-resources) -[#]: author: (Jessica Cherry https://opensource.com/users/jrepka) - -Top CI/CD resources to set you up for success -====== -Continuous integration and continuous deployment were key topics in 2019 -as organizations look to achieve seamless, flexible, and scalable -deployments. -![Plumbing tubes in many directions][1] - -This has been a fantastic year for continuous integration/continuous deployment (CI/CD) and the world of DevOps. Opensource.com authors shared how they're moving toward agile and scrum as they focus on seamless, flexible, and scalable deployments. Here are some of the big themes in the CI/CD articles we published this year. - -### Learning and improving your CI/CD skills - -Some of our favorite articles focus on hands-on CI/CD experience and cover a lot of ground as they do. The place to start is always with [Jenkins][2] pipelines, and Bryant Son's [_Building CI/CD pipelines with Jenkins_][3] will give you enough experience to get started building your first pipelines. Daniel Oh's [_Automate user acceptance testing with your DevOps pipeline_][4] provides great information on acceptance testing, including various CI/CD applications you can use for testing in its own right. And my article on [_Security scanning your DevOps pipeline_][5] is a very short, to the point tutorial on how to set up security in a pipeline using the Jenkins platform. - -### Delivery workflow - -While learning how to use and improve your skills with CI/CD, the workflow matters, especially when it comes to pipelines, as Jithin Emmanuel shares in [_Screwdriver: A scalable build platform for continuous delivery_][6]. Emily Burns explains having the flexibility to build exactly what you need with your CI/CD workflow in [_Why Spinnaker matters to CI/CD_][7]. And Willy-Peter Schaub extols the idea of creating a unified pipeline for everything to build consistently in [_One CI/CD pipeline per product to rule them all_][8]. These articles will give you a good sense of what happens after you onboard team members to the workflow process. - -### How CI/CD affects organizations - -2019 was also the year of recognizing CI/CD's business impact and how it affects day-to-day operations. Agnieszka Gancarczyk shares the results of Red Hat's [_Small Scale Scrum vs. Large Scale Scrum_][9] survey, including respondents' differing opinions on scrums, the agile movement, and the impact on teams. Will Kelly covers [_How continuous deployment impacts the entire organization_][10], including the importance of open communication, and Daniel Oh emphasizes the importance of metrics and observability in [_3 types of metric dashboards for DevOps teams_][11]. Last, but far from least, Ann Marie Fred's great article [_Don't test in production? Test in production!_][12] details why it's important for you to test in production—before your customers do. - -We are thankful to the many contributing authors who shared their insights with Opensource.com readers in 2019, and I look forward to learning more from them about the evolution of CI/CD in 2020. - --------------------------------------------------------------------------------- - -via: https://opensource.com/article/19/12/cicd-resources - -作者：[Jessica Cherry][a] -选题：[lujun9972][b] -译者：[译者ID](https://github.com/译者ID) -校对：[校对者ID](https://github.com/校对者ID) - -本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 - -[a]: https://opensource.com/users/jrepka -[b]: https://github.com/lujun9972 -[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/plumbing_pipes_tutorial_how_behind_scenes.png?itok=F2Z8OJV1 (Plumbing tubes in many directions) -[2]: https://jenkins.io/ -[3]: https://opensource.com/article/19/9/intro-building-cicd-pipelines-jenkins -[4]: https://opensource.com/article/19/4/devops-pipeline-acceptance-testing -[5]: https://opensource.com/article/19/7/security-scanning-your-devops-pipeline -[6]: https://opensource.com/article/19/3/screwdriver-cicd -[7]: https://opensource.com/article/19/8/why-spinnaker-matters-cicd -[8]: https://opensource.com/article/19/7/cicd-pipeline-rule-them-all -[9]: https://opensource.com/article/19/3/small-scale-scrum-vs-large-scale-scrum -[10]: https://opensource.com/article/19/7/organizational-impact-continuous-deployment -[11]: https://opensource.com/article/19/7/dashboards-devops-teams -[12]: https://opensource.com/article/19/5/dont-test-production