diff --git a/.gitee/ISSUE_TEMPLATE.en.md b/.gitee/ISSUE_TEMPLATE.en.md deleted file mode 100644 index 458911819fd4e6cbadc9228ff1d2f3e0a4d39d06..0000000000000000000000000000000000000000 --- a/.gitee/ISSUE_TEMPLATE.en.md +++ /dev/null @@ -1,23 +0,0 @@ -**Is this a BUG REPORT or FEATURE REQUEST?**: - -> Uncomment only one, leave it on its own line: -> -> - bug -> -> - feature - - -**What happened**: - -**What you expected to happen**: - -**How to reproduce it (as minimally and precisely as possible)**: - -**Anything else we need to know?**: - -**Environment**: -- Version: -- OS (e.g. from /etc/os-release): -- Kernel (e.g. `uname -a`): -- Install tools: -- Others: diff --git a/.gitee/ISSUE_TEMPLATE.zh-CN.md b/.gitee/ISSUE_TEMPLATE.zh-CN.md deleted file mode 100644 index d83eeb568385f4b57166ad51ccb6c414f5f061b7..0000000000000000000000000000000000000000 --- a/.gitee/ISSUE_TEMPLATE.zh-CN.md +++ /dev/null @@ -1,22 +0,0 @@ -**这是一个bug还是新特性?**: - -> 以下两者二选一，请保留一项: -> -> - bug -> -> - 特性 - - -**发生结果**: - -**期望结果**: - -**如何重现（尽量详细）**: - -**补充说明?**: - -**环境情况**: -- 版本: -- 操作系统版本 (e.g. from /etc/os-release): -- 内核版本 (e.g. `uname -a`): -- 其它: diff --git a/.gitee/PULL_REQUEST_TEMPLATE.en.md b/.gitee/PULL_REQUEST_TEMPLATE.en.md deleted file mode 100644 index fb9f653795bc13e5cced21eb4e7a96d655a23c59..0000000000000000000000000000000000000000 --- a/.gitee/PULL_REQUEST_TEMPLATE.en.md +++ /dev/null @@ -1,15 +0,0 @@ - - -**What this PR does / why we need it**: - -**Which issue this PR fixes** *(optional, in `fixes #(, fixes #, ...)` format, will close that issue when PR gets merged)*: fixes # - -**Special notes for your reviewer**: - -**Release note**: - -```release-note -``` diff --git a/.gitee/PULL_REQUEST_TEMPLATE.zh-CN.md b/.gitee/PULL_REQUEST_TEMPLATE.zh-CN.md deleted file mode 100644 index f731c6335b44ab9a37a3006406ddbe062bc3fa86..0000000000000000000000000000000000000000 --- a/.gitee/PULL_REQUEST_TEMPLATE.zh-CN.md +++ /dev/null @@ -1,15 +0,0 @@ - - -**PR功能描述 / 为什么需要这个合入**: - -**该PR关联的issue** *(格式为fixes #, 或者resolves #)*: fixes # - -**希望检视人员了解**: - -**Release note**: - -```release-note -``` diff --git a/.gitignore b/.gitignore deleted file mode 100644 index 1516e93b72f23cfe2ab4c75ea88b19a12ccc9a1a..0000000000000000000000000000000000000000 --- a/.gitignore +++ /dev/null @@ -1,2 +0,0 @@ -public -resources/_gen diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index d7c6119bfa7e3a01bbe2b405dc1f125890462a72..0000000000000000000000000000000000000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,167 +0,0 @@ -# How to contribute - -### Brief Introduction - -This project is [Apache 2.0](LICENSE) licensed and accepts contributions via pull requests. This document outlines some of the conventions on commit message formatting, contact points for developers and other resources to make getting your contribution easier. - -Before you start, NOTICE that ```master``` branch is development version. ```stable``` branch -provided for customers and users. So all code modifications SHOULD be submitted to -```master``` branch, ```stable``` branch won't accept any commits. - -This repository is integrated by website which will provide the final outline, so please only maintain docs in this repository. -anything others like styles, js are maintained in website as a combined hugo theme. - -Contents oranganized by hugo book which is a framework helping build our own book. -please refer to hugo book [website](https://github.com/alex-shpak/hugo-book) for more detailed information. - -All files are written with MarkDown syntax, please note: If you want to add internal links, -be careful to point to the .html pages corresponding to the .md pages of the folder. - -### Debug local - -This doc only provides running test on linux, please prepare linux server before running -following commands. - -1. Install hugo on server - -hugo can be installed easily after nodejs is ready. - -``` -curl -L https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_extended_0.56.3_Linux-64bit.tar.gz | tar -xz && \ - mv hugo /usr/local/bin/ -``` - -2. Running this repository locally - -``` -hugo serve --bind 0.0.0.0 --port 80 --baseUrl / -``` - -The website will serving on http://your-server-ip:80 - - -### Debug with docker - -1. Build Image - -``` -docker build -t docs:v0.0.1 . -``` - -note: here ```docs``` is the image name, you can change it as you need. - -2. Running in container - -``` -docker run -p 80:80 -d docs:v0.0.1 > docs.pid -``` - -The website will serving on http://your-server-ip:80 - -3. Stopping the container - -``` -docker rm -f `cat docs.pid` && rm -f docs.pid -``` - -***Note***: -The defalut language(en) will serving on http://your-server-ip/ -Other language(zh) will serving on http://your-server-ip/zh - -### Add/Modify file - -Before openning a PR, running locally and have a check would be good step that will help -your commits be merged quickly. - -There are two kinds of Markdown file, one is the content files which locates in ```content/docs``` folder. -the other one is the menu file which locates in ```content/menu``` folder. please remember to update menu if -adding new file. - -Note: menu file home file name must be named ```home.md```. - -## Getting help - -- IRC: TODO -- Mail: TODO - -## Report issues - -A great way to contribute to the project is to send a detailed report when you encounter an issue. We always appreciate a well-written, thorough bug report and feature propose, and will thank you for it! - -### Issues format - -When reporting issues, refer to this format: - -- Is this a BUG REPORT or FEATURE REQUEST? -- What happened? -- What you expected to happen? -- What happened? -- How to reproduce it (as minimally and precisely as possible) -- Anything else we need to know? -- Environment - -See more about [ISSUE_TEMPLATE](.github/ISSUE_TEMPLATE.md). - -## Submit pull requests - -If you are a beginner and expect this project as the gate to open source world, this tutorial is one of the best -choices for you. Just follow the guidance and you will find the pleasure to becoming a contributor. - -### Step 1: Fork repository - -Before making modifications of this project, you need to make sure that this project have been forked to your own -repository. It means that there will be parallel development between this repo and your own repo, so be careful -to avoid the inconsistency between these two repos. - -### Step 2: Clone the remote repository - -If you want to download the code to the local machine, ```git``` is the best way: -``` -git clone https://your_repo_url/projectname.git -``` - -### Step 3: Develop code locally - -To avoid inconsistency between multiple branches, we SUGGEST checking out to a new branch: -``` -git checkout -b new_branch_name origin/master -``` -Then you can change the code arbitrarily. - -### Step 4: Push the code to the remote repository - -After updating the code, you should push the update in the formal way: -``` -git add . -git status (Check the update status) -git commit -m "Your commit title" -git commit --amend (Add the concrete description of your commit) -git push origin new_branch_name -``` - -### Step 5: Pull a request to repository - -In the last step, your need to pull a compare request between your new branch and development branch. After -finishing the pull request, the CI will be automatically set up for building test. - -### Pull requests format - -When submitting pull requests, refer to this format: - -- What this PR does / why we need it? -- Which issue this PR fixes? -- Special notes for your reviewer -- Release note - -See more about [PULL_REQUEST_TEMPLATE](.github/PULL_REQUEST_TEMPLATE.md). - -### Code style - -```TO BE DEFINED``` - - - - - - - diff --git a/Dockerfile b/Dockerfile deleted file mode 100644 index c2012b2450287d3d54be186d230e4efcf98f3f73..0000000000000000000000000000000000000000 --- a/Dockerfile +++ /dev/null @@ -1,24 +0,0 @@ -FROM nginx - -MAINTAINER Edward Lee - -RUN apt-get update && \ - apt install curl -y && \ - apt-get install git -y - -ENV HUGO_VERSION=0.68.1 - -RUN mkdir -p /usr/local/src && \ - cd /usr/local/src && \ - curl -L https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_extended_${HUGO_VERSION}_Linux-64bit.tar.gz | tar -xz && \ - mv hugo /usr/local/bin/ - -COPY . /src/ -RUN cd /src/ && /usr/local/bin/hugo -b / && \ - cp -rf /src/public/* /usr/share/nginx/html/ && \ - chmod -R 755 /usr/share/nginx/html - -ENV RUN_USER nginx -ENV RUN_GROUP nginx -EXPOSE 80 -ENTRYPOINT nginx -g "daemon off;" diff --git a/LICENSE b/LICENSE deleted file mode 100644 index 261eeb9e9f8b2b4b0d119366dda99c6fd7d35c64..0000000000000000000000000000000000000000 --- a/LICENSE +++ /dev/null @@ -1,201 +0,0 @@ - Apache License - Version 2.0, January 2004 - http://www.apache.org/licenses/ - - TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - - 1. Definitions. - - "License" shall mean the terms and conditions for use, reproduction, - and distribution as defined by Sections 1 through 9 of this document. - - "Licensor" shall mean the copyright owner or entity authorized by - the copyright owner that is granting the License. - - "Legal Entity" shall mean the union of the acting entity and all - other entities that control, are controlled by, or are under common - control with that entity. For the purposes of this definition, - "control" means (i) the power, direct or indirect, to cause the - direction or management of such entity, whether by contract or - otherwise, or (ii) ownership of fifty percent (50%) or more of the - outstanding shares, or (iii) beneficial ownership of such entity. - - "You" (or "Your") shall mean an individual or Legal Entity - exercising permissions granted by this License. - - "Source" form shall mean the preferred form for making modifications, - including but not limited to software source code, documentation - source, and configuration files. - - "Object" form shall mean any form resulting from mechanical - transformation or translation of a Source form, including but - not limited to compiled object code, generated documentation, - and conversions to other media types. - - "Work" shall mean the work of authorship, whether in Source or - Object form, made available under the License, as indicated by a - copyright notice that is included in or attached to the work - (an example is provided in the Appendix below). - - "Derivative Works" shall mean any work, whether in Source or Object - form, that is based on (or derived from) the Work and for which the - editorial revisions, annotations, elaborations, or other modifications - represent, as a whole, an original work of authorship. For the purposes - of this License, Derivative Works shall not include works that remain - separable from, or merely link (or bind by name) to the interfaces of, - the Work and Derivative Works thereof. - - "Contribution" shall mean any work of authorship, including - the original version of the Work and any modifications or additions - to that Work or Derivative Works thereof, that is intentionally - submitted to Licensor for inclusion in the Work by the copyright owner - or by an individual or Legal Entity authorized to submit on behalf of - the copyright owner. For the purposes of this definition, "submitted" - means any form of electronic, verbal, or written communication sent - to the Licensor or its representatives, including but not limited to - communication on electronic mailing lists, source code control systems, - and issue tracking systems that are managed by, or on behalf of, the - Licensor for the purpose of discussing and improving the Work, but - excluding communication that is conspicuously marked or otherwise - designated in writing by the copyright owner as "Not a Contribution." - - "Contributor" shall mean Licensor and any individual or Legal Entity - on behalf of whom a Contribution has been received by Licensor and - subsequently incorporated within the Work. - - 2. Grant of Copyright License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - copyright license to reproduce, prepare Derivative Works of, - publicly display, publicly perform, sublicense, and distribute the - Work and such Derivative Works in Source or Object form. - - 3. Grant of Patent License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - (except as stated in this section) patent license to make, have made, - use, offer to sell, sell, import, and otherwise transfer the Work, - where such license applies only to those patent claims licensable - by such Contributor that are necessarily infringed by their - Contribution(s) alone or by combination of their Contribution(s) - with the Work to which such Contribution(s) was submitted. If You - institute patent litigation against any entity (including a - cross-claim or counterclaim in a lawsuit) alleging that the Work - or a Contribution incorporated within the Work constitutes direct - or contributory patent infringement, then any patent licenses - granted to You under this License for that Work shall terminate - as of the date such litigation is filed. - - 4. Redistribution. You may reproduce and distribute copies of the - Work or Derivative Works thereof in any medium, with or without - modifications, and in Source or Object form, provided that You - meet the following conditions: - - (a) You must give any other recipients of the Work or - Derivative Works a copy of this License; and - - (b) You must cause any modified files to carry prominent notices - stating that You changed the files; and - - (c) You must retain, in the Source form of any Derivative Works - that You distribute, all copyright, patent, trademark, and - attribution notices from the Source form of the Work, - excluding those notices that do not pertain to any part of - the Derivative Works; and - - (d) If the Work includes a "NOTICE" text file as part of its - distribution, then any Derivative Works that You distribute must - include a readable copy of the attribution notices contained - within such NOTICE file, excluding those notices that do not - pertain to any part of the Derivative Works, in at least one - of the following places: within a NOTICE text file distributed - as part of the Derivative Works; within the Source form or - documentation, if provided along with the Derivative Works; or, - within a display generated by the Derivative Works, if and - wherever such third-party notices normally appear. The contents - of the NOTICE file are for informational purposes only and - do not modify the License. You may add Your own attribution - notices within Derivative Works that You distribute, alongside - or as an addendum to the NOTICE text from the Work, provided - that such additional attribution notices cannot be construed - as modifying the License. - - You may add Your own copyright statement to Your modifications and - may provide additional or different license terms and conditions - for use, reproduction, or distribution of Your modifications, or - for any such Derivative Works as a whole, provided Your use, - reproduction, and distribution of the Work otherwise complies with - the conditions stated in this License. - - 5. Submission of Contributions. Unless You explicitly state otherwise, - any Contribution intentionally submitted for inclusion in the Work - by You to the Licensor shall be under the terms and conditions of - this License, without any additional terms or conditions. - Notwithstanding the above, nothing herein shall supersede or modify - the terms of any separate license agreement you may have executed - with Licensor regarding such Contributions. - - 6. Trademarks. This License does not grant permission to use the trade - names, trademarks, service marks, or product names of the Licensor, - except as required for reasonable and customary use in describing the - origin of the Work and reproducing the content of the NOTICE file. - - 7. Disclaimer of Warranty. Unless required by applicable law or - agreed to in writing, Licensor provides the Work (and each - Contributor provides its Contributions) on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or - implied, including, without limitation, any warranties or conditions - of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A - PARTICULAR PURPOSE. You are solely responsible for determining the - appropriateness of using or redistributing the Work and assume any - risks associated with Your exercise of permissions under this License. - - 8. Limitation of Liability. In no event and under no legal theory, - whether in tort (including negligence), contract, or otherwise, - unless required by applicable law (such as deliberate and grossly - negligent acts) or agreed to in writing, shall any Contributor be - liable to You for damages, including any direct, indirect, special, - incidental, or consequential damages of any character arising as a - result of this License or out of the use or inability to use the - Work (including but not limited to damages for loss of goodwill, - work stoppage, computer failure or malfunction, or any and all - other commercial damages or losses), even if such Contributor - has been advised of the possibility of such damages. - - 9. Accepting Warranty or Additional Liability. While redistributing - the Work or Derivative Works thereof, You may choose to offer, - and charge a fee for, acceptance of support, warranty, indemnity, - or other liability obligations and/or rights consistent with this - License. However, in accepting such obligations, You may act only - on Your own behalf and on Your sole responsibility, not on behalf - of any other Contributor, and only if You agree to indemnify, - defend, and hold each Contributor harmless for any liability - incurred by, or claims asserted against, such Contributor by reason - of your accepting any such warranty or additional liability. - - END OF TERMS AND CONDITIONS - - APPENDIX: How to apply the Apache License to your work. - - To apply the Apache License to your work, attach the following - boilerplate notice, with the fields enclosed by brackets "[]" - replaced with your own identifying information. (Don't include - the brackets!) The text should be enclosed in the appropriate - comment syntax for the file format. We also recommend that a - file or class name and description of purpose be included on the - same "printed page" as the copyright notice for easier - identification within third-party archives. - - Copyright [yyyy] [name of copyright owner] - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. diff --git a/README-en.md b/README-en.md deleted file mode 100644 index 3715c1b9a700b9fb9986d3f39b7c48477e26da8c..0000000000000000000000000000000000000000 --- a/README-en.md +++ /dev/null @@ -1,46 +0,0 @@ -# openEuler DOCS - -### Introduction - -DOCS contains all documents of the openEuler community, including the release notes, OS installation guide, administrator guide, virtualization, container, and A-Tune user guides, and application development guide. - -### Searching for a Document in DOCS - -Open the **content** folder. The folder contains documents in Chinese (**zh** folder) and English (**en** folder). The English document is used as an example. In the **en** folder, the **docs** folder contains the content of a specific document, and the **menu** folder contains the overview of the document. -Open the **docs** folder. The relationship between guides and folders is as follows: -* **A-Tune**: *A-Tune User Guide* -* **Administrator**: *Administrator Guide* -* **ApplicationDev**: *Application Development Guide* -* **Container**: *Container User Guide* -* **Installation**: *Installation Guide* -* **Quickstart**: *Quick Start* -* **Releasenotes**: *Release Notes* -* **Virtualization**: *Virtualization Application Guide* - - -### Modifying a Document - -When the openEuler version information is updated, the documents herein also need to be updated. Thank you for providing updates. - -### Checking the Relationship Between Versions and Branches -The DOCS contains the following three branches: - -* **master**: development branch, which is the default branch -* **stable-1.0\_Base**: 1.0 Base version branch, which is displayed in **DOCS** > **1.0 BASE** on the [openEuler community website](https://openeuler.org/) -* **stable-20.03\_LTS**: 20.03 LTS version branch, which is displayed in **DOCS** > **20.03 LTS** on the [openEuler community website](https://openeuler.org/) - -### Participating in SIG -Create or reply to an issue: You can discuss an issue by creating or replying to an issue. -Submit a Pull Request (PR): You can participate in SIG by submitting a PR. -Submit comments: You can submit comments on issues or PRs. -We are always pleased to receive PRs from you. - -### Member -#### Maintainer List -- Rudy_Tan (@rudy_tan) -- amyMaYun (@amy_mayun) -- fhxing (@fhxing168) - -### Contacting Us -E-mails: dev@openeuler.org -IRC: #openeuler-doc \ No newline at end of file diff --git a/README.md b/README.md deleted file mode 100644 index c84d8fee9e82481d4cc330ae2c6e45ce1df7283b..0000000000000000000000000000000000000000 --- a/README.md +++ /dev/null @@ -1,46 +0,0 @@ -# openEuler 文档 - -### 介绍 - -Docs包含了openEuler社区的所有文档，包括发行说明、操作系统安装，管理员指南，虚拟化和容器的使用指导，A-Tune使用指导，应用开发指导等内容。 -### 如何在Docs中查找文档 - -打开“content”文件夹，该文件夹包含了中文（“zh”文件夹）和英文（“en”文件夹）两种语言文档，以中文文档举例进行说明。 -在“zh”文件夹中，“docs”文件夹包含了具体文档的内容，“menu”包含了文档的大纲内容。 -打开“docs”文件夹，各手册和文件夹对应关系如下。 -* A-Tune文件夹对应：A-Tune用户指南 -* Adminnistration文件夹对应手册为：管理员指南 -* ApplicationDev文件夹对应手册为：应用开发指南 -* Container文件夹对应手册为：容器用户指南 -* Installation文件夹对应手册为：安装指南 -* Quickstart文件夹对应手册为：快速入门 -* Releasenotes文件夹对应手册为：发行说明 -* Virtualization文件夹对应手册为：虚拟化应用指南 - - -### 如何修改文档 - -当openEuler版本信息有刷新时，这里文档也需要刷新。很感谢您愿意提供刷新内容。 -请阅读[资料开发流程指导](https://gitee.com/lss410313/docs/wikis/Home)进行操作参考。 - -### 如何查看版本分支对应关系 -Docs包含了如下3个分支： -* master：开发分支，为默认分支。 -* stable-1.0_Base：1.0 Base版本分支，分支内容呈现在[openEuler社区](https://openeuler.org/)网站“文档->1.0 BASE。 -* stable-20.03_LTS：20.03 LTS版本分支，分支内容呈现在[openEuler社区](https://openeuler.org/)网站“文档->20.03 LTS”。 - -### 如何参与SIG -建立或回复 issue：欢迎通过建立或回复 issue 来讨论。 -提交PR：欢迎通过提交PR的方式参与SIG。具体操作方法可参考[PR提交指南](https://gitee.com/openeuler/community/blob/master/zh/contributors/pull-request.md)。 -提交评论：欢迎在issue或PR中提交评论。 -重要的事说三遍：欢迎提交 PR！欢迎提交 PR！欢迎提交 PR！ - -### 成员 -#### Maintainer 列表 -- Rudy_Tan(@rudy_tan) -- amyMaYun(@amy_mayun) -- fhxing(@fhxing168) - -### 如何联系我们 -邮件列表: dev@openeuler.org -IRC: #openeuler-doc \ No newline at end of file diff --git a/archetypes/default.md b/archetypes/default.md deleted file mode 100644 index 00e77bd79be44872c0b29256b03799c2fb00c10d..0000000000000000000000000000000000000000 --- a/archetypes/default.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: "{{ replace .Name "-" " " | title }}" -date: {{ .Date }} -draft: true ---- - diff --git a/assets/_custom.scss b/assets/_custom.scss deleted file mode 100644 index 9132fb60596fd0cce86d47583cba560f13bc7a95..0000000000000000000000000000000000000000 --- a/assets/_custom.scss +++ /dev/null @@ -1 +0,0 @@ -@import "variables"; diff --git a/config.toml b/config.toml deleted file mode 100644 index ffde1551e438cd8963e1682fa5d1d8645eec6c90..0000000000000000000000000000000000000000 --- a/config.toml +++ /dev/null @@ -1,68 +0,0 @@ -# hugo server --minify --themesDir ... --baseURL=http://0.0.0.0:1313/example - -baseURL = '/' -title = 'Hugo Book' -theme = 'project' -disableKinds = ['taxonomy', 'taxonomyTerm'] -# themesDir = '../..' - -# Book configuration -disablePathToLower = true -enableGitInfo = true -defaultContentLanguage = "en" -defaultContentLanguageInSubdir = false - -uglyURLs = true - -# Code highlight -# pygmentsStyle = 'monokailight' -pygmentsCodeFences = true - -[params] - # (Optional, default 6) Set how many table of contents levels to be showed on page. - # Use false to hide ToC, note that 0 will default to 6 (https://gohugo.io/functions/default/) - # You can also specify this parameter per page in front matter - BookToC = 3 - - # (Optional, default none) Set leaf bundle to render as side menu - # When not specified file structure and weights will be used - BookMenuBundle = '/menu' - - # (Optional, default docs) Specify section of content to render as menu - # You can also set value to '*' to render all sections to menu - #BookSection = 'docs' - - # (Optional) This value is duplicate of $link-color for making active link highlight in menu bundle mode - # BookMenuBundleActiveLinkColor = '\#004ed0' - - # Set source repository location. - # Used for 'Last Modified' and 'Edit this page' links. - BookRepo = 'https://gitee.com/openeuler/docs' - - # Enable "Edit this page" links for 'doc' page type. - # Disabled by default. Uncomment to enable. Requires 'BookRepo' param. - # Path must point to 'content' directory of repo. - BookEditPath = 'master/content' - - # Configure the date format used on the pages - # - In git information - # - In blog posts - BookDateFormat = 'Jan 2, 2006' - - # (Optional, default true) Enables search function with lunr.js, - # Index is built on fly, therefore it might slowdown your website. - BookSearch = true - - bookFlatSection = true - bookHidden = true - - -[languages] - -[languages.en] - languageCode = "en-us" - contentDir = "content/en" - -[languages.zh] - languageCode = "zh-cn" - contentDir = "content/zh" diff --git a/config.yaml b/config.yaml deleted file mode 100644 index 59d0ddc5a69c14e3094489dabec67dc5c68deffe..0000000000000000000000000000000000000000 --- a/config.yaml +++ /dev/null @@ -1,50 +0,0 @@ -# hugo server --minify --themesDir ... --baseURL=http://0.0.0.0:1313/example - -baseURL: https://example.com/ -title: Hugo Book -theme: hugo-book -disableKinds: ['taxonomy', 'taxonomyTerm'] -# themesDir: ../.. - -# Book configuration -disablePathToLower: true -enableGitInfo: true - -# Code highlight -# pygmentsStyle: monokailight -pygmentsCodeFences: true - -params: - # (Optional, default 6) Set how many table of contents levels to be showed on page. - # Use false/off to hide ToC, note that 0 will default to 6 (https://gohugo.io/functions/default/) - # You can also specify this parameter per page in front matter - BookToC: 3 - - # (Optional, default none) Set leaf bundle to render as side menu - # When not specified file structure and weights will be used - BookMenuBundle: /menu - - # (Optional, default docs) Specify section of content to render as menu - # You can also set value to '*' to render all sections to menu - BookSection: docs - - # (Optional) This value is duplicate of $link-color for making active link highlight in menu bundle mode - # BookMenuBundleActiveLinkColor: "\#004ed0" - - # Set source repository location. - # Used for 'Last Modified' and 'Edit this page' links. - BookRepo: https://github.com/alex-shpak/hugo-book - - # Enable "Edit this page" links for 'doc' page type. - # Disabled by default. Uncomment to enable. Requires 'BookRepo' param. - # Path must point to 'content' directory of repo. - BookEditPath: edit/master/exampleSite/content - - # Configure the date format used on the pages - # - In git information - # - In blog posts - BookDateFormat: 'Jan 2, 2006' - - # (Optional, default true) Enables search function with lunr.js, - # Index is built on fly, therefore it might slowdown your website. - BookSearch: true diff --git a/content/en/docs/Installation/figures/adding-the-inst-noverifyssl-parameter.png b/content/en/docs/Installation/figures/adding-the-inst-noverifyssl-parameter.png deleted file mode 100644 index f56a7dd0c45acf8a4c3a735ed623eaccd19bfaef..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/adding-the-inst-noverifyssl-parameter.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/advanced-user-configuration.png b/content/en/docs/Installation/figures/advanced-user-configuration.png deleted file mode 100644 index c7d708ba1b466b514c978b738f67b15723f8bc2e..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/advanced-user-configuration.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/completing-the-installation.png b/content/en/docs/Installation/figures/completing-the-installation.png deleted file mode 100644 index 6e7fb79328124e1eb03d7c2aa57d4bcb3b592d3c..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/completing-the-installation.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/creating-a-user.png b/content/en/docs/Installation/figures/creating-a-user.png deleted file mode 100644 index 8203597a9f82d2aac03987fd9c381d55eb6b40c8..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/creating-a-user.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/disk-encryption-password.png b/content/en/docs/Installation/figures/disk-encryption-password.png deleted file mode 100644 index ba84e060133644910ff199376e11d2929cfe8d47..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/disk-encryption-password.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/error-message.png b/content/en/docs/Installation/figures/error-message.png deleted file mode 100644 index 0349567af5b1695a611b8c32219b469bcf2170e8..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/error-message.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/installation-process.png b/content/en/docs/Installation/figures/installation-process.png deleted file mode 100644 index 202ef0ce7f371417d6371867c1f3bfff6d07cd91..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/installation-process.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/installation-summary.png b/content/en/docs/Installation/figures/installation-summary.png deleted file mode 100644 index d74f2eeae91338c4e8a9a9c03b19361df89ac388..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/installation-summary.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/installation-wizard.png b/content/en/docs/Installation/figures/installation-wizard.png deleted file mode 100644 index 0ee099a675eee71fdeb3ba3ad0f30e0be20d7af3..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/installation-wizard.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/manual-partitioning-page.png b/content/en/docs/Installation/figures/manual-partitioning-page.png deleted file mode 100644 index c14540e86c178f28d34be24eebd8c487ca377783..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/manual-partitioning-page.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/password-of-the-root-account.png b/content/en/docs/Installation/figures/password-of-the-root-account.png deleted file mode 100644 index 16f77d9ce59c0bf082915c2e958513fcc6244af9..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/password-of-the-root-account.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/selecting-a-language.png b/content/en/docs/Installation/figures/selecting-a-language.png deleted file mode 100644 index 2f41e205b0c8f97eee950e8ce3f44b953f1c2c71..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/selecting-a-language.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/selecting-installation-software.png b/content/en/docs/Installation/figures/selecting-installation-software.png deleted file mode 100644 index 79ea7b97705c91af1fa6cd8fb47a0a15fa3607cf..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/selecting-installation-software.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/semi-automatic-installation.png b/content/en/docs/Installation/figures/semi-automatic-installation.png deleted file mode 100644 index dcdfb60e3e77594c59cfbaaece61881347cd4032..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/semi-automatic-installation.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/setting-a-system-language.png b/content/en/docs/Installation/figures/setting-a-system-language.png deleted file mode 100644 index 79f6d5b959abaa20d077e3d0d82a2cb05bc428d6..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/setting-a-system-language.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/setting-date-and-time.png b/content/en/docs/Installation/figures/setting-date-and-time.png deleted file mode 100644 index 9a18de4816560da52bd5e6f6a5d8c0f1a0ddde13..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/setting-date-and-time.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/setting-the-installation-destination.png b/content/en/docs/Installation/figures/setting-the-installation-destination.png deleted file mode 100644 index 7dd9ba0fd65069492156fc31d3b9adbc7965de98..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/setting-the-installation-destination.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/setting-the-installation-source.png b/content/en/docs/Installation/figures/setting-the-installation-source.png deleted file mode 100644 index 94990f7c3071d7153203a2d75cf6632b1505beda..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/setting-the-installation-source.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/setting-the-keyboard-layout.png b/content/en/docs/Installation/figures/setting-the-keyboard-layout.png deleted file mode 100644 index 9aa9d72da79ca7d89c36949926ff272edc83592c..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/setting-the-keyboard-layout.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/setting-the-network-and-host-name.png b/content/en/docs/Installation/figures/setting-the-network-and-host-name.png deleted file mode 100644 index ddfb08fac47b8b4681cca2f5ce18c4258f365ac0..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/setting-the-network-and-host-name.png and /dev/null differ diff --git a/content/en/docs/Installation/figures/starting-installation.png b/content/en/docs/Installation/figures/starting-installation.png deleted file mode 100644 index fb9ca40b29b63430744920c88e8069a92a3d2ff2..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Installation/figures/starting-installation.png and /dev/null differ diff --git a/content/en/docs/Quickstart/figures/advanced-user-configuration.png b/content/en/docs/Quickstart/figures/advanced-user-configuration.png deleted file mode 100644 index c7d708ba1b466b514c978b738f67b15723f8bc2e..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Quickstart/figures/advanced-user-configuration.png and /dev/null differ diff --git a/content/en/docs/Quickstart/figures/completing-the-installation.png b/content/en/docs/Quickstart/figures/completing-the-installation.png deleted file mode 100644 index 6e7fb79328124e1eb03d7c2aa57d4bcb3b592d3c..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Quickstart/figures/completing-the-installation.png and /dev/null differ diff --git a/content/en/docs/Quickstart/figures/creating-a-user.png b/content/en/docs/Quickstart/figures/creating-a-user.png deleted file mode 100644 index 8203597a9f82d2aac03987fd9c381d55eb6b40c8..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Quickstart/figures/creating-a-user.png and /dev/null differ diff --git a/content/en/docs/Quickstart/figures/installation-summary.png b/content/en/docs/Quickstart/figures/installation-summary.png deleted file mode 100644 index d74f2eeae91338c4e8a9a9c03b19361df89ac388..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Quickstart/figures/installation-summary.png and /dev/null differ diff --git a/content/en/docs/Quickstart/figures/installation-wizard.png b/content/en/docs/Quickstart/figures/installation-wizard.png deleted file mode 100644 index 0ee099a675eee71fdeb3ba3ad0f30e0be20d7af3..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Quickstart/figures/installation-wizard.png and /dev/null differ diff --git a/content/en/docs/Quickstart/figures/password-of-the-root-account.png b/content/en/docs/Quickstart/figures/password-of-the-root-account.png deleted file mode 100644 index 16f77d9ce59c0bf082915c2e958513fcc6244af9..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Quickstart/figures/password-of-the-root-account.png and /dev/null differ diff --git a/content/en/docs/Quickstart/figures/selecting-a-language.png b/content/en/docs/Quickstart/figures/selecting-a-language.png deleted file mode 100644 index 2f41e205b0c8f97eee950e8ce3f44b953f1c2c71..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Quickstart/figures/selecting-a-language.png and /dev/null differ diff --git a/content/en/docs/Quickstart/figures/selecting-installation-software.png b/content/en/docs/Quickstart/figures/selecting-installation-software.png deleted file mode 100644 index 79ea7b97705c91af1fa6cd8fb47a0a15fa3607cf..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Quickstart/figures/selecting-installation-software.png and /dev/null differ diff --git a/content/en/docs/Quickstart/figures/setting-the-installation-destination.png b/content/en/docs/Quickstart/figures/setting-the-installation-destination.png deleted file mode 100644 index 7dd9ba0fd65069492156fc31d3b9adbc7965de98..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Quickstart/figures/setting-the-installation-destination.png and /dev/null differ diff --git a/content/en/docs/Quickstart/figures/starting-installation.png b/content/en/docs/Quickstart/figures/starting-installation.png deleted file mode 100644 index fb9ca40b29b63430744920c88e8069a92a3d2ff2..0000000000000000000000000000000000000000 Binary files a/content/en/docs/Quickstart/figures/starting-installation.png and /dev/null differ diff --git a/content/en/menu/index.md b/content/en/menu/index.md deleted file mode 100644 index c954b2d3f2f749220a4042b26bdfe00f8b4334b4..0000000000000000000000000000000000000000 --- a/content/en/menu/index.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -headless: true - - ---- - -- [Terms of Use]({{< relref "./docs/Releasenotes/terms-of-use.md" >}}) -- [Release Notes]({{< relref "./docs/Releasenotes/release_notes.md" >}}) - - [User Notice]({{< relref "./docs/Releasenotes/user-notice.md" >}}) - - [Introduction]({{< relref "./docs/Releasenotes/introduction.md" >}}) - - [Installing the OS]({{< relref "./docs/Releasenotes/installing-the-os.md" >}}) - - [Key Features]({{< relref "./docs/Releasenotes/key-features.md" >}}) - - [Known Issues]({{< relref "./docs/Releasenotes/known-issues.md" >}}) - - [Resolved Issues]({{< relref "./docs/Releasenotes/resolved-issues.md" >}}) - - [Common Vulnerabilities and Exposures \(CVE\)]({{< relref "./docs/Releasenotes/common-vulnerabilities-and-exposures-(cve).md" >}}) - - [Source Code]({{< relref "./docs/Releasenotes/source-code.md" >}}) - - [Contribution]({{< relref "./docs/Releasenotes/contribution.md" >}}) - - [Acknowledgement]({{< relref "./docs/Releasenotes/acknowledgement.md" >}}) - -- [Quick Start]({{< relref "./docs/Quickstart/quick-start.md" >}}) -- [Installation Guide]({{< relref "./docs/Installation/Installation.md" >}}) - - [Installation Preparations]({{< relref "./docs/Installation/installation-preparations.md" >}}) - - [Installation Mode]({{< relref "./docs/Installation/installation-mode.md" >}}) - - [Installation Guideline]({{< relref "./docs/Installation/installation-guideline.md" >}}) - - [Using Kickstart for Automatic Installation]({{< relref "./docs/Installation/using-kickstart-for-automatic-installation.md" >}}) - - [FAQs]({{< relref "./docs/Installation/faqs.md" >}}) - -- [Administrator Guide]({{< relref "./docs/Administration/administration.md" >}}) - - [Viewing System Information]({{< relref "./docs/Administration/viewing-system-information.md" >}}) - - [Basic Configuration]({{< relref "./docs/Administration/basic-configuration.md" >}}) - - [User and User Group Management]({{< relref "./docs/Administration/user-and-user-group-management.md" >}}) - - [Using the DNF to Manage Software Packages]({{< relref "./docs/Administration/using-the-dnf-to-manage-software-packages.md" >}}) - - [Service Management]({{< relref "./docs/Administration/service-management.md" >}}) - - [Process Management]({{< relref "./docs/Administration/process-management.md" >}}) - - [Configuring the Network]({{< relref "./docs/Administration/configuring-the-network.md" >}}) - - [Managing Hard Disks Through LVM]({{< relref "./docs/Administration/managing-hard-disks-through-lvm.md" >}}) - - [Using the KAE]({{< relref "./docs/Administration/using-the-kae.md" >}}) - - [Configuring Services]({{< relref "./docs/Administration/configuring-services.md" >}}) - - [Configuring the Repo Server]({{< relref "./docs/Administration/configuring-the-repo-server.md" >}}) - - [Configuring the FTP Server]({{< relref "./docs/Administration/configuring-the-ftp-server.md" >}}) - - [Configuring the Web Server]({{< relref "./docs/Administration/configuring-the-web-server.md" >}}) - - [Setting Up the Database Server]({{< relref "./docs/Administration/setting-up-the-database-server.md" >}}) - - [FAQs]({{< relref "./docs/Administration/faqs.md" >}}) - - -- [Virtualization User Guide]({{< relref "./docs/Virtualization/virtualization.md" >}}) - - [Introduction to Virtualization]({{< relref "./docs/Virtualization/introduction-to-virtualization.md" >}}) - - [Installation to Virtualization]({{< relref "./docs/Virtualization/installation-to-virtualization.md" >}}) - - [Environment Preparation]({{< relref "./docs/Virtualization/environment-preparation.md" >}}) - - [VM Configuration]({{< relref "./docs/Virtualization/vm-configuration.md" >}}) - - [Managing VMs]({{< relref "./docs/Virtualization/managing-vms.md" >}}) - - [VM Live Migration]({{< relref "./docs/Virtualization/vm-live-migration.md" >}}) - - [System Resource Management]({{< relref "./docs/Virtualization/system-resource-management.md" >}}) - - [Managing Devices]({{< relref "./docs/Virtualization/managing-devices.md" >}}) - - [Best Practices]({{< relref "./docs/Virtualization/best-practices.md" >}}) - - [Appendix]({{< relref "./docs/Virtualization/appendix.md" >}}) - - -- [Container User Guide]({{< relref "./docs/Container/container.md" >}}) - - [iSulad Container Engine]({{< relref "./docs/Container/isulad-container-engine.md" >}}) - - [Installation, Upgrade and Uninstallation]({{< relref "./docs/Container/installation-upgrade-Uninstallation.md" >}}) - - [Installation and Configuration]({{< relref "./docs/Container/installation-configuration.md" >}}) - - [Upgrade Methods]({{< relref "./docs/Container/upgrade-methods.md" >}}) - - [Uninstallation]({{< relref "./docs/Container/uninstallation.md" >}}) - - - [Application Scenarios]({{< relref "./docs/Container/application-scenarios.md" >}}) - - [Container Management]({{< ref "./docs/Container/container-management.md" >}}) - - [Interconnection with the CNI Network]({{< ref "./docs/Container/interconnection-with-the-cni-network.md" >}}) - - [Container Resource Management]({{< ref "./docs/Container/container-resource-management.md" >}}) - - [Privileged Container]({{< ref "./docs/Container/privileged-container.md" >}}) - - [CRI]({{< ref "./docs/Container/cri.md" >}}) - - [Image Management]({{< ref "./docs/Container/image-management.md" >}}) - - [Checking the Container Health Status]({{< ref "./docs/Container/checking-the-container-health-status.md" >}}) - - [Querying Information]({{< ref "./docs/Container/querying-information.md" >}}) - - [Security Features]({{< ref "./docs/Container/security-features.md" >}}) - - [Supporting OCI hooks]({{< ref "./docs/Container/supporting-oci-hooks.md" >}}) - - [Appendix]({{< ref "./docs/Container/appendix.md" >}}) - - - [System Container]({{< relref "./docs/Container/system-container.md" >}}) - - [Installation Guideline]({{< relref "./docs/Container/installation-guideline.md" >}}) - - [Usage Guide]({{< relref "./docs/Container/usage-guide.md" >}}) - - [Specifying Rootfs to Create a Container]({{< ref "./docs/Container/specifying-rootfs-to-create-a-container.md" >}}) - - [Using systemd to Start a Container]({{< ref "./docs/Container/using-systemd-to-start-a-container.md" >}}) - - [Reboot or Shutdown in a Container]({{< ref "./docs/Container/reboot-or-shutdown-in-a-container.md" >}}) - - [Configurable Cgroup Path]({{< ref "./docs/Container/configurable-cgroup-path.md" >}}) - - [Writable Namespace Kernel Parameters]({{< ref "./docs/Container/writable-namespace-kernel-parameters.md" >}}) - - [Shared Memory Channels]({{< ref "./docs/Container/shared-memory-channels.md" >}}) - - [Dynamically Loading the Kernel Module]({{< ref "./docs/Container/dynamically-loading-the-kernel-module.md" >}}) - - [Environment Variable Persisting]({{< ref "./docs/Container/environment-variable-persisting.md" >}}) - - [Maximum Number of Handles]({{< ref "./docs/Container/maximum-number-of-handles.md" >}}) - - [Security and Isolation]({{< ref "./docs/Container/security-and-isolation.md" >}}) - - [Dynamically Managing Container Resources \(syscontainer-tools\)]({{< ref "./docs/Container/dynamically-managing-container-resources-(syscontainer-tools).md" >}}) - - [Appendix]({{< ref "./docs/Container/appendix-1.md" >}}) - - - [Secure Container]({{< relref "./docs/Container/secure-container.md" >}}) - - [Installation and Deployment]({{< relref "./docs/Container/installation-and-deployment-1.md" >}}) - - [Application Scenarios]({{< relref "./docs/Container/application-scenarios-2.md" >}}) - - [Managing the Lifecycle of a Secure Container]({{< ref "./docs/Container/managing-the-lifecycle-of-a-secure-container.md" >}}) - - [Configuring Resources for a Secure Container]({{< ref "./docs/Container/configuring-resources-for-a-secure-container.md" >}}) - - [Configuring Networking for a Secure Container]({{< ref "./docs/Container/configuring-networking-for-a-secure-container.md" >}}) - - [Monitoring Secure Containers]({{< ref "./docs/Container/monitoring-secure-containers.md" >}}) - - [Appendix]({{< ref "./docs/Container/appendix-2.md" >}}) - - - [Docker Container]({{< relref "./docs/Container/docker-container.md" >}}) - - [Installation and Deployment]({{< relref "./docs/Container/installation-and-deployment-2.md" >}}) - - [Container Management]({{< ref "./docs/Container/container-management-1.md" >}}) - - [Image Management]({{< ref "./docs/Container/image-management-1.md" >}}) - - [Command Reference]({{< ref "./docs/Container/command-reference.md" >}}) - - [Container Engine]({{< ref "./docs/Container/container-engine.md" >}}) - - [Container Management]({{< ref "./docs/Container/container-management-2.md" >}}) - - [Image Management]({{< ref "./docs/Container/image-management-2.md" >}}) - - [Statistics]({{< ref "./docs/Container/statistics.md" >}}) - - -- [A-Tune User Guide]({{< relref "./docs/A-Tune/A-Tune.md" >}}) - - [Getting to Know A-Tune]({{< relref "./docs/A-Tune/getting-to-know-a-tune.md" >}}) - - [Installation and Deployment]({{< relref "./docs/A-Tune/installation-and-deployment.md" >}}) - - [Application Scenarios]({{< relref "./docs/A-Tune/application-scenarios.md" >}}) - - [FAQs]({{< relref "./docs/A-Tune/faqs.md" >}}) - - [Appendixes]({{< relref "./docs/A-Tune/appendixes.md" >}}) - - - -- [Application Development Guide]({{< relref "./docs/ApplicationDev/application-development.md" >}}) - - [Preparation]({{< relref "./docs/ApplicationDev/preparation.md" >}}) - - [Using GCC for Compilation]({{< relref "./docs/ApplicationDev/using-gcc-for-compilation.md" >}}) - - [Using Make for Compilation]({{< relref "./docs/ApplicationDev/using-make-for-compilation.md" >}}) - - [Using JDK for Compilation]({{< relref "./docs/ApplicationDev/using-jdk-for-compilation.md" >}}) - - [Building an RPM Package]({{< relref "./docs/ApplicationDev/building-an-rpm-package.md" >}}) \ No newline at end of file diff --git a/content/zh/docs/Installation/FAQ-1.md b/content/zh/docs/Installation/FAQ-1.md deleted file mode 100644 index 284a0108acfff0cd1b7879554f302299f5675164..0000000000000000000000000000000000000000 --- a/content/zh/docs/Installation/FAQ-1.md +++ /dev/null @@ -1,27 +0,0 @@ -# FAQ - - -- [FAQ](#faq) - - [树莓派启动失败](#树莓派启动失败) - - [问题现象](#问题现象) - - [原因分析](#原因分析) - - [解决方法](#解决方法) - - - -## 树莓派启动失败 - -### 问题现象 - -将 openEuler 发布的树莓派镜像刷写入 SD 卡后，树莓派启动失败。 - -### 原因分析 - -刷写 openEuler 发布的树莓派镜像后，树莓派启动失败，大致有以下几种情况： - -1. 下载的镜像文件不完整，请确保该镜像通过完整性校验。 -2. 镜像写入 SD 卡过程中出现问题，多出现在 Windows 环境下使用应用软件刷写镜像到 SD 卡的情况。 - -### 解决方法 - -将完整的镜像重新刷写入 SD 卡。 diff --git "a/content/zh/docs/Installation/figures/root\345\257\206\347\240\201.png" "b/content/zh/docs/Installation/figures/root\345\257\206\347\240\201.png" deleted file mode 100644 index b5bf8835c1b04a8ec679a34fdd20b0419b081431..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/root\345\257\206\347\240\201.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\345\210\206\345\214\272\346\211\251\345\256\271.png" "b/content/zh/docs/Installation/figures/\345\210\206\345\214\272\346\211\251\345\256\271.png" deleted file mode 100644 index 37a6ef7a2371a9a5518f6d2ce0dc6d36fc71fe1b..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\345\210\206\345\214\272\346\211\251\345\256\271.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\345\210\233\345\273\272\347\224\250\346\210\267.png" "b/content/zh/docs/Installation/figures/\345\210\233\345\273\272\347\224\250\346\210\267.png" deleted file mode 100644 index 9c2208da7baf239a879277d53374037d9ff48410..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\345\210\233\345\273\272\347\224\250\346\210\267.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\345\215\212\350\207\252\345\212\250-new.png" "b/content/zh/docs/Installation/figures/\345\215\212\350\207\252\345\212\250-new.png" deleted file mode 100644 index dcdfb60e3e77594c59cfbaaece61881347cd4032..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\345\215\212\350\207\252\345\212\250-new.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\345\242\236\345\212\240inst-noverifyssl\345\217\202\346\225\260.png" "b/content/zh/docs/Installation/figures/\345\242\236\345\212\240inst-noverifyssl\345\217\202\346\225\260.png" deleted file mode 100644 index f56a7dd0c45acf8a4c3a735ed623eaccd19bfaef..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\345\242\236\345\212\240inst-noverifyssl\345\217\202\346\225\260.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\345\256\211\350\243\205\345\274\225\345\257\274\347\225\214\351\235\242.png" "b/content/zh/docs/Installation/figures/\345\256\211\350\243\205\345\274\225\345\257\274\347\225\214\351\235\242.png" deleted file mode 100644 index 0ee099a675eee71fdeb3ba3ad0f30e0be20d7af3..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\345\256\211\350\243\205\345\274\225\345\257\274\347\225\214\351\235\242.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\345\256\211\350\243\205\346\246\202\350\247\210.png" "b/content/zh/docs/Installation/figures/\345\256\211\350\243\205\346\246\202\350\247\210.png" deleted file mode 100644 index d64da9c1ad2a4afc657eb50f1e4439b5b870ea2a..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\345\256\211\350\243\205\346\246\202\350\247\210.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\345\256\211\350\243\205\346\272\220.png" "b/content/zh/docs/Installation/figures/\345\256\211\350\243\205\346\272\220.png" deleted file mode 100644 index 25a28495bad27f26cac8ce19009d2c780d92f0fd..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\345\256\211\350\243\205\346\272\220.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\345\256\211\350\243\205\347\233\256\346\240\207\344\275\215\347\275\256.png" "b/content/zh/docs/Installation/figures/\345\256\211\350\243\205\347\233\256\346\240\207\344\275\215\347\275\256.png" deleted file mode 100644 index 4c13cb4faff2f8a4292ec5d940e63aa80e268f1d..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\345\256\211\350\243\205\347\233\256\346\240\207\344\275\215\347\275\256.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\345\256\211\350\243\205\350\277\207\347\250\213.png" "b/content/zh/docs/Installation/figures/\345\256\211\350\243\205\350\277\207\347\250\213.png" deleted file mode 100644 index 9278b364149636a26a21409afc1342aa1c546ddb..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\345\256\211\350\243\205\350\277\207\347\250\213.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\345\256\214\346\210\220\345\256\211\350\243\205.png" "b/content/zh/docs/Installation/figures/\345\256\214\346\210\220\345\256\211\350\243\205.png" deleted file mode 100644 index b54d9ef9c15affd3f41ce6622be66d883ef7e744..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\345\256\214\346\210\220\345\256\211\350\243\205.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\345\274\200\345\247\213\345\256\211\350\243\205.png" "b/content/zh/docs/Installation/figures/\345\274\200\345\247\213\345\256\211\350\243\205.png" deleted file mode 100644 index 1a5771d8f56ef2472f488e3524d0d0bc91827d10..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\345\274\200\345\247\213\345\256\211\350\243\205.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\346\211\213\345\212\250\345\210\206\345\214\272.png" "b/content/zh/docs/Installation/figures/\346\211\213\345\212\250\345\210\206\345\214\272.png" deleted file mode 100644 index f56b1aba62237b74ecc60c1cf9eee9b5cd4902c0..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\346\211\213\345\212\250\345\210\206\345\214\272.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\346\227\245\346\234\237\345\222\214\346\227\266\351\227\264.png" "b/content/zh/docs/Installation/figures/\346\227\245\346\234\237\345\222\214\346\227\266\351\227\264.png" deleted file mode 100644 index 33b528bb77d0d6b0f51da604e2bad89e3a9daafe..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\346\227\245\346\234\237\345\222\214\346\227\266\351\227\264.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\347\233\230\347\254\246.png" "b/content/zh/docs/Installation/figures/\347\233\230\347\254\246.png" deleted file mode 100644 index b49213bd19cb5b9cdac6ce25564be17df2810d72..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\347\233\230\347\254\246.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\347\243\201\347\233\230\345\212\240\345\257\206\345\217\243\344\273\244.png" "b/content/zh/docs/Installation/figures/\347\243\201\347\233\230\345\212\240\345\257\206\345\217\243\344\273\244.png" deleted file mode 100644 index c76b59d3214da2c55119f0300103be0b9c2d8792..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\347\243\201\347\233\230\345\212\240\345\257\206\345\217\243\344\273\244.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\347\275\221\347\273\234\345\222\214\344\270\273\346\234\272\345\220\215.png" "b/content/zh/docs/Installation/figures/\347\275\221\347\273\234\345\222\214\344\270\273\346\234\272\345\220\215.png" deleted file mode 100644 index 24aee8cb2ca13e004d2439ffd89de047c330b58c..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\347\275\221\347\273\234\345\222\214\344\270\273\346\234\272\345\220\215.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\350\216\267\345\217\226IP.png" "b/content/zh/docs/Installation/figures/\350\216\267\345\217\226IP.png" deleted file mode 100644 index 26b6f8f60a36c4b43ebebe4dbdce169ade4b13ae..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\350\216\267\345\217\226IP.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\350\257\255\350\250\200\346\224\257\346\214\201.png" "b/content/zh/docs/Installation/figures/\350\257\255\350\250\200\346\224\257\346\214\201.png" deleted file mode 100644 index a7ddd3a5a6c3c6f377675af294a978d12480ff87..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\350\257\255\350\250\200\346\224\257\346\214\201.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\350\275\257\344\273\266\351\200\211\346\213\251.png" "b/content/zh/docs/Installation/figures/\350\275\257\344\273\266\351\200\211\346\213\251.png" deleted file mode 100644 index 011be38bc7b0030cde009574831b1a5d5a356a1f..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\350\275\257\344\273\266\351\200\211\346\213\251.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\351\200\211\346\213\251\350\257\255\350\250\200.png" "b/content/zh/docs/Installation/figures/\351\200\211\346\213\251\350\257\255\350\250\200.png" deleted file mode 100644 index 738853f1685aeaf2fc7a135f9f13443341f42c48..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\351\200\211\346\213\251\350\257\255\350\250\200.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\351\205\215\347\275\256\351\224\231\350\257\257\346\217\220\347\244\272.png" "b/content/zh/docs/Installation/figures/\351\205\215\347\275\256\351\224\231\350\257\257\346\217\220\347\244\272.png" deleted file mode 100644 index 0349567af5b1695a611b8c32219b469bcf2170e8..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\351\205\215\347\275\256\351\224\231\350\257\257\346\217\220\347\244\272.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\351\224\256\347\233\230\345\270\203\345\261\200.png" "b/content/zh/docs/Installation/figures/\351\224\256\347\233\230\345\270\203\345\261\200.png" deleted file mode 100644 index d91d52d773a277d91ebaccbd7e9ae7d770e6528b..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\351\224\256\347\233\230\345\270\203\345\261\200.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/figures/\351\253\230\347\272\247\347\224\250\346\210\267\351\205\215\347\275\256.png" "b/content/zh/docs/Installation/figures/\351\253\230\347\272\247\347\224\250\346\210\267\351\205\215\347\275\256.png" deleted file mode 100644 index 9a87dffd881b279a4b8c40c798e917a9ac7a3ede..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Installation/figures/\351\253\230\347\272\247\347\224\250\346\210\267\351\205\215\347\275\256.png" and /dev/null differ diff --git "a/content/zh/docs/Installation/\345\256\211\350\243\205\345\207\206\345\244\207-1.md" "b/content/zh/docs/Installation/\345\256\211\350\243\205\345\207\206\345\244\207-1.md" deleted file mode 100644 index 41f27886ddf0917cd3a694d068872ef1f493dac7..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\345\256\211\350\243\205\345\207\206\345\244\207-1.md" +++ /dev/null @@ -1,118 +0,0 @@ -# 安装准备 - -介绍安装前需要考虑软硬件兼容性状况，以及相关的配置和准备工作。 - - -- [安装准备](#安装准备) - - [获取安装源](#获取安装源) - - [镜像完整性校验](#镜像完整性校验) - - [简介](#简介) - - [前提条件](#前提条件) - - [操作指导](#操作指导) - - [安装要求](#安装要求) - - [硬件兼容支持](#硬件兼容支持) - - [最小硬件要求](#最小硬件要求) - - - -## 获取安装源 - -在安装开始前，您需要获取 openEuler 发布的树莓派镜像及其校验文件。 - -1. 登录[openEuler社区](https://openeuler.org)网站。 -2. 单击“下载”。 -3. 单击“获取ISO：”后面的“Link”，显示版本列表。 -4. 单击“openEuler-20.09”，进入 openEuler 20.09 版本下载列表。 -5. 单击“RaspberryPi”，进入树莓派镜像的下载列表。 - - aarch64：AArch64 架构的镜像。 - -6. 单击“aarch64”，进入树莓派 AArch64 架构镜像的下载列表。 -7. 单击“openEuler-20.09-RaspberryPi.aarch64.img.xz”，将 openEuler 发布的树莓派镜像下载到本地。 -8. 单击“openEuler-20.09-RaspberryPi.aarch64.img.xz.sha256sum”，将 openEuler 发布的树莓派镜像的校验文件下载到本地。 - -## 镜像完整性校验 - -### 简介 - -为了防止软件包在传输过程中由于网络原因或者存储设备原因出现下载不完整的问题，在获取到软件包后，需要对软件包的完整性进行校验，通过了校验的软件包才能部署。 - -这里通过对比校验文件中记录的校验值和手动方式计算的文件校验值，判断软件包是否完整。若两个值相同，说明下载的文件完整，否则，下载的文件完整性被破坏，请重新获取软件包。 - -### 前提条件 - -在校验镜像文件的完整性之前，需要准备如下文件： - -镜像文件：openEuler-20.09-RaspberryPi.aarch64.img.xz - -校验文件：openEuler-20.09-RaspberryPi.aarch64.img.xz.sha256sum - -### 操作指导 - -文件完整性校验操作步骤如下： - -1. 获取校验文件中的校验值。执行命令如下： - - ``` - $ cat openEuler-20.09-RaspberryPi.aarch64.img.xz.sha256sum - ``` - -2. 计算文件的 sha256 校验值。执行命令如下： - - ``` - $ sha256sum openEuler-20.09-RaspberryPi.aarch64.img.xz - ``` - - 命令执行完成后，输出校验值。 - -3. 对比步骤 1 和步骤 2 计算的校验值是否一致。 - - 如果校验值一致说明下载的文件完整性没有破坏，如果校验值不一致则可以确认文件完整性已被破坏，需要重新获取。 - -## 安装要求 - -在树莓派环境上安装 openEuler 操作系统，则树莓派需要满足如下的硬件兼容性和最小硬件要求。 - -### 硬件兼容支持 - -openEuler 树莓派版本镜像目前支持树莓派 3B/3B+/4B。 - -### 最小硬件要求 - -openEuler 树莓派版本镜像所需的最小硬件要求如[表1](#tff48b99c9bf24b84bb602c53229e2542)所示。 - -**表 1** 最小硬件要求 - - - - - - - - - - - - - - - - - - - - - - -

部件名称

-

最小硬件要求

-

说明

-

树莓派版本

-
  • 树莓派 3B
  • 树莓派 3B+
  • 树莓派 4B
-

-

-

内存

-

不小于 2GB（为了获得更好的应用体验，建议至少 4GB）

-

-

-

硬盘

-

为了获得更好的应用体验，建议不小于 8GB

-

-

-
diff --git "a/content/zh/docs/Installation/\345\256\211\350\243\205\345\234\250\346\234\215\345\212\241\345\231\250.md" "b/content/zh/docs/Installation/\345\256\211\350\243\205\345\234\250\346\234\215\345\212\241\345\231\250.md" deleted file mode 100644 index e69de29bb2d1d6434b8b29ae775ad8c2e48c5391..0000000000000000000000000000000000000000 diff --git "a/content/zh/docs/Installation/\345\256\211\350\243\205\345\234\250\346\240\221\350\216\223\346\264\276.md" "b/content/zh/docs/Installation/\345\256\211\350\243\205\345\234\250\346\240\221\350\216\223\346\264\276.md" deleted file mode 100644 index e69de29bb2d1d6434b8b29ae775ad8c2e48c5391..0000000000000000000000000000000000000000 diff --git "a/content/zh/docs/Installation/\345\256\211\350\243\205\346\214\207\345\257\274-1.md" "b/content/zh/docs/Installation/\345\256\211\350\243\205\346\214\207\345\257\274-1.md" deleted file mode 100644 index 73ea046de2099e3662fcb3f365b7df861e9f2929..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\345\256\211\350\243\205\346\214\207\345\257\274-1.md" +++ /dev/null @@ -1,180 +0,0 @@ -# 安装指导 - -本章介绍将“[树莓派镜像刷写入 SD 卡](安装方式介绍-1.html)”后，启用树莓派的主要过程。 - - -- [安装指导](#安装指导) - - [启动系统](#启动系统) - - [登录系统](#登录系统) - - [配置系统](#配置系统) - - [扩展根目录分区](#扩展根目录分区) - - [连接 WIFI](#连接-wifi) - - - -## 启动系统 - -将刷写镜像后的 SD 卡插入树莓派，通电启用。 - -树莓派硬件相关信息请参考[树莓派官网](https://www.raspberrypi.org/)。 - -## 登录系统 - -登录树莓派有以下两种方式： - -1. 本地登录 - - 树莓派连接显示器（树莓派视频输出接口为 Micro HDMI）、键盘、鼠标后，启动树莓派，可以看到树莓派启动日志输出到显示器上。待树莓派启动成功，输入用户名（root）和密码（openEuler12#$）登录。 - -2. ssh 远程登录 - 树莓派默认采用 DHCP 的方式自动获取 IP。如果树莓派连接已知路由器，可登录路由器查看，新增的 IP 即为树莓派 IP。 - - **图 1** 获取 IP - ![](figures/获取IP.png "获取 IP") - - 从上图看到，树莓派对应 IP 为：192.168.31.109，使用命令 `ssh root@192.168.1.109` 后输入密码 `openEuler12#$`，即可远程登录树莓派。 - -## 配置系统 - -### 扩展根目录分区 - -默认根目录分区空间比较小，在使用之前，需要对分区进行扩容。 - -请按照以下步骤扩展根目录分区： - -1. 在 root 权限下执行 `fdisk -l` 命令查看磁盘分区信息。命令和回显如下： - - ``` - # fdisk -l - Disk /dev/mmcblk0: 14.86 GiB, 15931539456 bytes, 31116288 sectors - Units: sectors of 1 * 512 = 512 bytes - Sector size (logical/physical): 512 bytes / 512 bytes - I/O size (minimum/optimal): 512 bytes / 512 bytes - Disklabel type: dos - Disk identifier: 0xf2dc3842 - - Device Boot Start End Sectors Size Id Type - /dev/mmcblk0p1 * 8192 593919 585728 286M c W95 FAT32 (LBA) - /dev/mmcblk0p2 593920 1593343 999424 488M 82 Linux swap / Solaris - /dev/mmcblk0p3 1593344 5044223 3450880 1.7G 83 Linux - ``` - - SD 卡对应盘符为 /dev/mmcblk0，包括 3 个分区，分别为 - - - /dev/mmcblk0p1：引导分区 - - /dev/mmcblk0p2：交换分区 - - /dev/mmcblk0p3：根目录分区 - - 这里我们需要将根目录分区 `/dev/mmcblk0p3` 进行扩容。 - -2. 在 root 权限下执行 `fdisk /dev/mmcblk0` 命令进入到交互式命令行界面，按照以下步骤扩展分区，如[图3](#zh-cn_topic_0151920806_f6ff7658b349942ea87f4521c0256c315)所示。 - - 1. 输入 `p`，查看分区信息。 - - 记录分区 `/dev/mmcblk0p3` 的起始扇区号，即 `/dev/mmcblk0p3` 分区信息中 `Start` 列的值，示例中为 `1593344`。 - - 2. 输入 `d`，删除分区。 - 3. 输入 `3` 或直接按 `Enter`，删除序号为 `3` 的分区，即 `/dev/mmcblk0p3` 分区。 - 4. 输入 `n`，创建新的分区。 - 5. 输入 `p` 或直接按 `Enter`，创建 `Primary` 类型的分区。 - 6. 输入 `3` 或直接按 `Enter`，创建序号为 `3` 的分区，即 `/dev/mmcblk0p3` 分区。 - 7. 输入新分区的起始扇区号，即第 `1` 步中记录的起始扇区号，示例中为 `1593344`。 - - >![](public_sys-resources/icon-notice.gif) **须知：** - >请勿直接按“Enter”或使用默认参数。 - - 8. 按 `Enter`，使用默认的最后一个扇区号作为新分区的终止扇区号。 - 9. 输入 `N`，不修改扇区标记。 - 10. 输入 `w`，保存分区设置并退出交互式命令行界面。 - - **图 3** 分区扩容 - ![](figures/分区扩容.png "分区扩容") - -3. 在 root 权限下执行 `fdisk -l` 命令查看磁盘分区信息，以确保磁盘分区正确。命令和回显如下： - - ``` - # fdisk -l - Disk /dev/mmcblk0: 14.86 GiB, 15931539456 bytes, 31116288 sectors - Units: sectors of 1 * 512 = 512 bytes - Sector size (logical/physical): 512 bytes / 512 bytes - I/O size (minimum/optimal): 512 bytes / 512 bytes - Disklabel type: dos - Disk identifier: 0xf2dc3842 - - Device Boot Start End Sectors Size Id Type - /dev/mmcblk0p1 * 8192 593919 585728 286M c W95 FAT32 (LBA) - /dev/mmcblk0p2 593920 1593343 999424 488M 82 Linux swap / Solaris - /dev/mmcblk0p3 1593344 31116287 29522944 14.1G 83 Linux - ``` - -4. 在 root 权限下执行 `resize2fs /dev/mmcblk0p3`，增大未加载的文件系统大小。 -5. 执行 `df -lh` 命令查看磁盘空间信息，以确保根目录分区已扩展。 - - >![](public_sys-resources/icon-notice.gif) **须知：** - >如果根目录分区未扩展，可执行 `reboot` 命令重启树莓派之后再在 root 权限下执行 `resize2fs /dev/mmcblk0p3`。 - -### 连接 WIFI - -请按照以下步骤连接 WIFI： - -1. 查看 IP 和网卡信息 - - `ip a` - - 获取无线网卡 wlan0 信息： - - ``` - 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 - link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 - inet 127.0.0.1/8 scope host lo - valid_lft forever preferred_lft forever - inet6 ::1/128 scope host - valid_lft forever preferred_lft forever - 2: eth0: mtu 1500 qdisc mq state UP group default qlen 1000 - link/ether dc:a6:32:50:de:57 brd ff:ff:ff:ff:ff:ff - inet 192.168.31.109/24 brd 192.168.31.255 scope global dynamic noprefixroute eth0 - valid_lft 41570sec preferred_lft 41570sec - inet6 fe80::cd39:a969:e647:3043/64 scope link noprefixroute - valid_lft forever preferred_lft forever - 3: wlan0: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 - link/ether e2:e6:99:89:47:0c brd ff:ff:ff:ff:ff:ff - ``` - -2. 扫描可以连接的 WIFI 信息 - - `nmcli dev wifi` - -3. 连接 WIFI - - 在 root 权限下执行 `nmcli dev wifi connect SSID password PWD` 命令连接 WIFI。 - - 其中，`SSID` 为上一步扫描到的可供连接的 WIFI 的 SSID，`PWD` 为对应 WIFI 的密码。例如，`SSID` 为 `openEuler-wifi`，密码为 `12345678`，则连接该 WIFI 命令为：`nmcli dev wifi connect openEuler-wifi password 12345678`，连接成功： - - ``` - Device 'wlan0' successfully activated with '26becaab-4adc-4c8e-9bf0-1d63cf5fa3f1'. - ``` - -4. 查看 IP 和无线网卡信息 - - `ip a` - - ``` - 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 - link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 - inet 127.0.0.1/8 scope host lo - valid_lft forever preferred_lft forever - inet6 ::1/128 scope host - valid_lft forever preferred_lft forever - 2: eth0: mtu 1500 qdisc mq state UP group default qlen 1000 - link/ether dc:a6:32:50:de:57 brd ff:ff:ff:ff:ff:ff - inet 192.168.31.109/24 brd 192.168.31.255 scope global dynamic noprefixroute eth0 - valid_lft 41386sec preferred_lft 41386sec - inet6 fe80::cd39:a969:e647:3043/64 scope link noprefixroute - valid_lft forever preferred_lft forever - 3: wlan0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 - link/ether dc:a6:32:50:de:58 brd ff:ff:ff:ff:ff:ff - inet 192.168.31.110/24 brd 192.168.31.255 scope global dynamic noprefixroute wlan0 - valid_lft 43094sec preferred_lft 43094sec - inet6 fe80::394:d086:27fa:deba/64 scope link noprefixroute - valid_lft forever preferred_lft forever - ``` diff --git "a/content/zh/docs/Installation/\345\256\211\350\243\205\346\226\271\345\274\217\344\273\213\347\273\215-1.md" "b/content/zh/docs/Installation/\345\256\211\350\243\205\346\226\271\345\274\217\344\273\213\347\273\215-1.md" deleted file mode 100644 index 65fffe05b708b975c7396619ec86397ca8964f73..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\345\256\211\350\243\205\346\226\271\345\274\217\344\273\213\347\273\215-1.md" +++ /dev/null @@ -1,113 +0,0 @@ -# 安装方式介绍 - ->![](public_sys-resources/icon-notice.gif) **须知：** ->- 硬件仅支持树莓派 3B/3B+/4B。 ->- 采用刷写镜像到 SD 卡方式安装。本章节提供 Windows/Linux/Mac 上刷写镜像的操作方法。 ->- 本章节使用的镜像是参考“[安装准备](安装准备-1.html)”获取 openEuler 的树莓派版本镜像。 - - - -- [安装方式介绍](#安装方式介绍) - - [Windows 下刷写镜像](#windows-下刷写镜像) - - [格式化 SD 卡](#格式化-sd-卡) - - [写入 SD 卡](#写入-sd-卡) - - [Linux 下刷写镜像](#linux-下刷写镜像) - - [查看磁盘分区信息](#查看磁盘分区信息) - - [卸载 SD 卡挂载点](#卸载-sd-卡挂载点) - - [写入 SD 卡](#写入-sd-卡-1) - - [Mac 下刷写镜像](#mac-下刷写镜像) - - [查看磁盘分区信息](#查看磁盘分区信息-1) - - [卸载 SD 卡挂载点](#卸载-sd-卡挂载点-1) - - [写入 SD 卡](#写入-sd-卡-2) - - - -## Windows 下刷写镜像 - -本节以 Windows 10 为例，介绍如何在 Windows 环境下将镜像刷写到 SD 卡。 - -### 格式化 SD 卡 - -请按照以下步骤格式化 SD 卡： - -1. 下载并安装格式化 SD 卡工具，以下操作以 SD Card Formatter 格式化工具为例。 -2. 打开 SD Card Formatter，在 “Select card” 中选择需要格式化的 SD 卡的盘符。 - - 若 SD 卡之前未安装过镜像，盘符只有一个。在 “Select card” 中选择需要格式化的 SD 卡对应盘符。 - - 若 SD 卡之前安装过镜像，盘符会有一个或多个。如下图所示，该 SD 卡对应三个盘符：E、G、H。在 “Select card” 中选择需要格式化的 SD 卡对应 boot 分区盘符 E。 - - **图 1** 盘符 - ![](figures/盘符.png "盘符") - -3. 在 “Formatting options” 中选择格式化方式。默认为 “Qick format”。 -4. 单击“Format”开始格式化。界面通过进度条显示格式化进度。 -5. 格式化完成后会弹出 “Formatting was successfully completed” 的提示框，单击“确定”完成格式化。 - -### 写入 SD 卡 - ->![](public_sys-resources/icon-notice.gif) **须知：** ->如果获取的是压缩后的镜像文件“openEuler-20.09-RaspberryPi.aarch64.img.xz”，需要先将压缩文件解压得到 “openEuler-20.09-RaspberryPi.aarch64.img”镜像文件。 - -请按照以下步骤将“openEuler-20.09-RaspberryPi.aarch64.img”镜像文件写入 SD 卡： - -1. 下载并安装刷写镜像的工具，以下操作以 Win32 Disk Imager 工具为例。 -2. 右键选择“以管理员身份运行”，打开 Win32 Disk Imager。 -3. 在“映像文件”中选择 img 格式的镜像文件路径。 -4. 在“设备”中选择待写入的 SD 卡盘符。 -5. 单击“写入”。界面通过任务进度条显示写入 SD 卡的进度。 -6. 写入完成后会弹出 “写入成功” 的提示框，单击“OK”完成写入。 - -## Linux 下刷写镜像 - -本节介绍如何在 Linux 环境下将镜像刷写到SD卡。 - -### 查看磁盘分区信息 - -在 root 权限下执行 `fdisk -l` 获取 SD 卡磁盘信息，例如 SD 卡对应磁盘为 /dev/sdb。 - -### 卸载 SD 卡挂载点 - -1. 执行 `df -lh` 命令查看当前已挂载的卷。 -2. 如果 SD 卡对应的分区未挂载，则跳过该步骤；如果 SD 卡对应分区已挂载，如 SD 卡对应的两个分区 /dev/sdb1 和 /dev/sdb3 已挂载，则需要卸载对应分区，在 root 权限下执行以下命令： - - `umount /dev/sdb1` - - `umount /dev/sdb3` - -### 写入 SD 卡 - -1. 如果获取的是压缩后的镜像，需要先执行 `xz -d openEuler-20.09-RaspberryPi.aarch64.img.xz` 命令将压缩文件解压得到“openEuler-20.09-RaspberryPi.aarch64.img”镜像文件；否则，跳过该步骤。 -2. 将镜像 `openEuler-20.09-RaspberryPi.aarch64.img` 刷写入 SD 卡，在 root 权限下执行以下命令： - - `dd bs=4M if=openEuler-20.09-RaspberryPi.aarch64.img of=/dev/sdb` - - >![](public_sys-resources/icon-note.gif) **说明：** - >一般情况下，将块大小设置为 4M。如果写入失败或者写入的镜像无法使用，可以尝试将块大小设置为 1M 重新写入，但是设置为 1M 比较耗时。 - -## Mac 下刷写镜像 - -本节介绍如何在 Mac 环境下将镜像刷写到SD卡。 - -### 查看磁盘分区信息 - -在 root 权限下执行 `diskutil list` 获取 SD 卡磁盘信息，例如 SD 卡对应磁盘为 /dev/disk3。 - -### 卸载 SD 卡挂载点 - -1. 执行 `df -lh` 命令查看当前已挂载的卷。 -2. 如果 SD 卡对应的分区未挂载，则跳过该步骤；如果 SD 卡对应分区已挂载，如 SD 卡对应的两个分区 /dev/disk3s1 和 /dev/disk3s3 已挂载，则需要卸载对应分区，在 root 权限下执行以下命令： - - `diskutil umount /dev/disk3s1` - - `diskutil umount /dev/disk3s3` - -### 写入 SD 卡 - -1. 如果获取的是压缩后的镜像，需要先执行 `xz -d openEuler-20.09-RaspberryPi.aarch64.img.xz` 命令将压缩文件解压得到“openEuler-20.09-RaspberryPi.aarch64.img”镜像文件；否则，跳过该步骤。 -2. 将镜像 `openEuler-20.09-RaspberryPi.aarch64.img` 刷入 SD 卡，在 root 权限下执行以下命令： - - `dd bs=4m if=openEuler-20.09-RaspberryPi.aarch64.img of=/dev/sdb` - - >![](public_sys-resources/icon-note.gif) **说明：** - >一般情况下，将块大小设置为 4m。如果写入失败或者写入的镜像无法使用，可以尝试将块大小设置为 1m 重新写入，但是设置为 1m 比较耗时。 diff --git "a/content/zh/docs/Installation/\346\233\264\345\244\232\350\265\204\346\272\220.md" "b/content/zh/docs/Installation/\346\233\264\345\244\232\350\265\204\346\272\220.md" deleted file mode 100644 index 8782e7d2468b4bbb59dbef0bfc93384de20cdce9..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Installation/\346\233\264\345\244\232\350\265\204\346\272\220.md" +++ /dev/null @@ -1,4 +0,0 @@ -# 参考资料 - -- [如何构建树莓派镜像文件](https://gitee.com/openeuler/raspberrypi/blob/master/documents/openEuler镜像的构建.md) -- [如何使用树莓派](https://gitee.com/openeuler/raspberrypi/blob/master/documents/树莓派使用.md) \ No newline at end of file diff --git "a/content/zh/docs/Quickstart/figures/root\345\257\206\347\240\201.png" "b/content/zh/docs/Quickstart/figures/root\345\257\206\347\240\201.png" deleted file mode 100644 index b5bf8835c1b04a8ec679a34fdd20b0419b081431..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Quickstart/figures/root\345\257\206\347\240\201.png" and /dev/null differ diff --git "a/content/zh/docs/Quickstart/figures/\345\210\233\345\273\272\347\224\250\346\210\267.png" "b/content/zh/docs/Quickstart/figures/\345\210\233\345\273\272\347\224\250\346\210\267.png" deleted file mode 100644 index 9c2208da7baf239a879277d53374037d9ff48410..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Quickstart/figures/\345\210\233\345\273\272\347\224\250\346\210\267.png" and /dev/null differ diff --git "a/content/zh/docs/Quickstart/figures/\345\256\211\350\243\205\345\274\225\345\257\274\347\225\214\351\235\242.png" "b/content/zh/docs/Quickstart/figures/\345\256\211\350\243\205\345\274\225\345\257\274\347\225\214\351\235\242.png" deleted file mode 100644 index 0ee099a675eee71fdeb3ba3ad0f30e0be20d7af3..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Quickstart/figures/\345\256\211\350\243\205\345\274\225\345\257\274\347\225\214\351\235\242.png" and /dev/null differ diff --git "a/content/zh/docs/Quickstart/figures/\345\256\211\350\243\205\346\246\202\350\247\210.png" "b/content/zh/docs/Quickstart/figures/\345\256\211\350\243\205\346\246\202\350\247\210.png" deleted file mode 100644 index d64da9c1ad2a4afc657eb50f1e4439b5b870ea2a..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Quickstart/figures/\345\256\211\350\243\205\346\246\202\350\247\210.png" and /dev/null differ diff --git "a/content/zh/docs/Quickstart/figures/\345\256\211\350\243\205\347\233\256\346\240\207\344\275\215\347\275\256.png" "b/content/zh/docs/Quickstart/figures/\345\256\211\350\243\205\347\233\256\346\240\207\344\275\215\347\275\256.png" deleted file mode 100644 index 4c13cb4faff2f8a4292ec5d940e63aa80e268f1d..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Quickstart/figures/\345\256\211\350\243\205\347\233\256\346\240\207\344\275\215\347\275\256.png" and /dev/null differ diff --git "a/content/zh/docs/Quickstart/figures/\345\256\214\346\210\220\345\256\211\350\243\205.png" "b/content/zh/docs/Quickstart/figures/\345\256\214\346\210\220\345\256\211\350\243\205.png" deleted file mode 100644 index b54d9ef9c15affd3f41ce6622be66d883ef7e744..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Quickstart/figures/\345\256\214\346\210\220\345\256\211\350\243\205.png" and /dev/null differ diff --git "a/content/zh/docs/Quickstart/figures/\345\274\200\345\247\213\345\256\211\350\243\205.png" "b/content/zh/docs/Quickstart/figures/\345\274\200\345\247\213\345\256\211\350\243\205.png" deleted file mode 100644 index 1a5771d8f56ef2472f488e3524d0d0bc91827d10..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Quickstart/figures/\345\274\200\345\247\213\345\256\211\350\243\205.png" and /dev/null differ diff --git "a/content/zh/docs/Quickstart/figures/\350\275\257\344\273\266\351\200\211\346\213\251.png" "b/content/zh/docs/Quickstart/figures/\350\275\257\344\273\266\351\200\211\346\213\251.png" deleted file mode 100644 index 011be38bc7b0030cde009574831b1a5d5a356a1f..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Quickstart/figures/\350\275\257\344\273\266\351\200\211\346\213\251.png" and /dev/null differ diff --git "a/content/zh/docs/Quickstart/figures/\351\200\211\346\213\251\350\257\255\350\250\200.png" "b/content/zh/docs/Quickstart/figures/\351\200\211\346\213\251\350\257\255\350\250\200.png" deleted file mode 100644 index 738853f1685aeaf2fc7a135f9f13443341f42c48..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Quickstart/figures/\351\200\211\346\213\251\350\257\255\350\250\200.png" and /dev/null differ diff --git "a/content/zh/docs/Quickstart/figures/\351\253\230\347\272\247\347\224\250\346\210\267\351\205\215\347\275\256.png" "b/content/zh/docs/Quickstart/figures/\351\253\230\347\272\247\347\224\250\346\210\267\351\205\215\347\275\256.png" deleted file mode 100644 index 9a87dffd881b279a4b8c40c798e917a9ac7a3ede..0000000000000000000000000000000000000000 Binary files "a/content/zh/docs/Quickstart/figures/\351\253\230\347\272\247\347\224\250\346\210\267\351\205\215\347\275\256.png" and /dev/null differ diff --git a/content/zh/docs/Releasenotes/README.md b/content/zh/docs/Releasenotes/README.md deleted file mode 100644 index 63751f53f739f8a7c2bf8e8431e7d59f5dad323a..0000000000000000000000000000000000000000 --- a/content/zh/docs/Releasenotes/README.md +++ /dev/null @@ -1,43 +0,0 @@ -# 组件分类 - -**应用和基础服务** -- 包括Application && Base-service - -**编程语言和编译器** -- 包括Programming-language && Compiler && sig-golang && sig-perl-modules && sig-python-modules - -**运行时和中间件** -- 包括Runtime && sig-ai-bigdata && sig-ROS && DB - -**虚拟化和容器** -- 包括Virt && oVirt && iSulad && Docker && sig-android-middleware - -**集群管理** -- 包括sig-Ha && sig-Kubernetes - -**内核** -- 包括Kernel - -**安全** -- 包括SIG-Security_facility && sig-bounds_checking_function - -**硬件和芯片使能** -- sig-RaspberryPi && sig-RISC-V && sig-Compatibility-Infra - -**文件系统** -- 包括Storage & sig-ceph - -**计算和加速库** -- 包括Computing && kae - -**网络** -- 包括Network && dpdk && sig-REDF - -**桌面** -- 包括Desktop && sig-mate-desktop && sig-UKUI && xfce && GNOME && sig-DDE - -**系统工具** -- 包括System-tool && A-Tune && dev-utils && sig-EasyLife - -**其它** -- 包括other && private \ No newline at end of file diff --git a/content/zh/docs/Releasenotes/release_notes.md b/content/zh/docs/Releasenotes/release_notes.md deleted file mode 100644 index b8f6f7d801aaa764c4f3b2a854e54c2e0677bb31..0000000000000000000000000000000000000000 --- a/content/zh/docs/Releasenotes/release_notes.md +++ /dev/null @@ -1 +0,0 @@ -本文是 openEuler 20.09 LTS 版本的发行说明。 \ No newline at end of file diff --git a/content/zh/docs/Releasenotes/zh-cn_bookmap_0225720059.md b/content/zh/docs/Releasenotes/zh-cn_bookmap_0225720059.md deleted file mode 100644 index 843daf755b25db9714413552d037bdb0d9715945..0000000000000000000000000000000000000000 --- a/content/zh/docs/Releasenotes/zh-cn_bookmap_0225720059.md +++ /dev/null @@ -1,14 +0,0 @@ -# 版本发行说明 - -- [法律声明](法律声明.md) -- [用户须知](用户须知.md) -- [简介](简介.md) -- [系统安装](系统安装.md) -- [关键特性](关键特性.md) -- [已知问题](已知问题.md) -- [已修复问题](已修复问题.md) -- [CVE漏洞](CVE漏洞.md) -- [源代码](源代码.md) -- [参与贡献](参与贡献.md) -- [致谢](致谢.md) - diff --git "a/content/zh/docs/Releasenotes/\345\205\263\351\224\256\347\211\271\346\200\247.md" "b/content/zh/docs/Releasenotes/\345\205\263\351\224\256\347\211\271\346\200\247.md" deleted file mode 100644 index 310894c2ba830da82ff91ca63dd6daeb8468b7b3..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Releasenotes/\345\205\263\351\224\256\347\211\271\346\200\247.md" +++ /dev/null @@ -1,41 +0,0 @@ -# 关键特性 - -**编程语言和编译器** -- JDK8优化：APPCDS特性支持、crc32硬加速指令支持。 -- GCC优化：循环优化、自动矢量化、全局优化。 - -**运行时和中间件** -- QVisor：轻量级虚拟化Runtime。 -- iSula轻量级容器解决方案，统一IoT，边缘和云计算容器解决方案。 - -**虚拟化** -- Kunpeng虚拟化特性：CPU和内存热插拔、NMI Watchdog、KVM Custom、SmartPolling。 -- 可信启动度量：vTPM机制支撑启动阶段的对各个部件的可信度量。 -- VMTOP工具：虚拟机组件配套DFX工具，支持抓取虚拟机陷出开销，调度时延等各种数据。 - -**内核** -- TLB Range 指令支持：批量TLB invalid提升性能，MMU gather减少TLBi调用。 -- Numa aware qspinlock支持：减少跨NUMA节点的Cache/总线冲突。 -- Ktask并行化支持：内核任务并行化框架支持，内核任务并行化运行。 -- 内存系统锁优化：vmalloc分配大锁优化、Pagecache锁优化。 - -**安全** -- CloudEncalve支持：提供机密计算统一框架、南向屏蔽SGX和TrustZone的差异，北向提供统一API和SDK。 -- IMA支持：完整性度量机制 - -**硬件和芯片使能** -- Raspberry Pi支持：Raspberry系列板卡支持。 - -**计算和加速库** -- 摘要算法SM3，支持异步模型 -- 对称加密算法SM4，支持异步模型，支持CTR/XTS/CBC模式 -- 对称加密算法AES，支持异步模型，支持ECB/CTR/XTS/CBC模式 -- 非对称算法RSA，支持异步模型，支持Key Sizes 1024/2048/3072/4096 -- 密钥协商算法DH，支持异步模型，支持Key Sizes 768/1024/1536/2048/3072/4096 - -**桌面** -- UKUI：麒麟操作系统的默认桌面环境，其布局、风格和使用习惯接近传统Windows - -**系统工具** -- A-Tune：智能系统性能优化引擎，推理出业务特征，配置最佳的系统参数合，使业务处于最优运行状态 -- A-OPS： 内核热升级框架，以及配套工具 diff --git "a/content/zh/docs/Releasenotes/\345\267\262\344\277\256\345\244\215\351\227\256\351\242\230.md" "b/content/zh/docs/Releasenotes/\345\267\262\344\277\256\345\244\215\351\227\256\351\242\230.md" deleted file mode 100644 index 5000634b5d83b42b9a4e668826a8f44439baf98d..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Releasenotes/\345\267\262\344\277\256\345\244\215\351\227\256\351\242\230.md" +++ /dev/null @@ -1,243 +0,0 @@ -# 已修复问题 - -完整问题清单请参见[完整问题清单](https://gitee.com/organizations/src-openeuler/issues)。 - -完整的内核提交记录请参见[提交记录](https://gitee.com/openeuler/kernel/commits/openEuler-1.0-LTS)。 - -**应用和基础服务** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**编程语言和编译器** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**运行时和中间件** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**虚拟化和容器** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**集群管理** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**内核** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**安全** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**硬件和芯片使能** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**文件系统** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**计算和加速库** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**网络** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**桌面** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**系统工具** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**其它** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
\ No newline at end of file diff --git "a/content/zh/docs/Releasenotes/\345\267\262\347\237\245\351\227\256\351\242\230.md" "b/content/zh/docs/Releasenotes/\345\267\262\347\237\245\351\227\256\351\242\230.md" deleted file mode 100644 index 7730294041314d5b9e4e2904f56a2babbbb0c732..0000000000000000000000000000000000000000 --- "a/content/zh/docs/Releasenotes/\345\267\262\347\237\245\351\227\256\351\242\230.md" +++ /dev/null @@ -1,238 +0,0 @@ -# 已知问题 -**应用和基础服务** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**编程语言和编译器** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**运行时和中间件** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**虚拟化和容器** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**集群管理** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**内核** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**安全** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**硬件和芯片使能** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**文件系统** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**计算和加速库** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**网络** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**桌面** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**系统工具** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
- -**其它** - - - - - - - - - - -

ISSUE

-

问题描述

-

I1BJTF

-

DEMO

-
diff --git a/content/zh/docs/userguide/images/Maintainer.jpg b/content/zh/docs/userguide/images/Maintainer.jpg deleted file mode 100644 index da0d5f1b5d928eca3a0d63795f59c55331136065..0000000000000000000000000000000000000000 Binary files a/content/zh/docs/userguide/images/Maintainer.jpg and /dev/null differ diff --git a/content/zh/docs/userguide/images/PatchTracking.jpg b/content/zh/docs/userguide/images/PatchTracking.jpg deleted file mode 100644 index e12afd6227c18c333f289b9aa71abf608d8058a0..0000000000000000000000000000000000000000 Binary files a/content/zh/docs/userguide/images/PatchTracking.jpg and /dev/null differ diff --git a/content/zh/docs/userguide/pkgship.md b/content/zh/docs/userguide/pkgship.md deleted file mode 100644 index 937597d4f3a3e2d1a84fbeb71cb2e2371655b155..0000000000000000000000000000000000000000 --- a/content/zh/docs/userguide/pkgship.md +++ /dev/null @@ -1,192 +0,0 @@ -pkgship -=== - -# 介绍 -pkgship是一款管理OS软件包依赖关系，提供依赖和被依赖关系完整图谱的查询工具，pkgship提供软件包依赖查询、生命周期管理、补丁查询等功能。 -1. 软件包依赖查询：方便社区人员在软件包引入、更新和删除的时候了解软件的影响范围。 -2. 生命周期管理：跟踪上游软件包发布状态，方便维护人员了解当前软件状态，及时升级到合理的版本。 -3. 补丁查询：方便社区人员了解openEuler软件包的补丁情况以及提取补丁内容。 - -# 架构 -系统采用flask-restful开发，使用SQLAlchemy ORM查询框架，同时支持mysql和sqlite两种数据库，可以通过配置文件的更改使用哪种数据库。 - -# 软件下载 -* Repo源挂载地址：https://repo.openeuler.org/ -* 源码获取地址：https://gitee.com/openeuler/openEuler-Advisor/tree/master/packageship -* rpm包获取地址：https://117.78.1.88/project/show/openEuler:Mainline - -# 安装工具 -工具安装可通过以下两种方式实现。 - -* 先使用dnf挂载pkgship软件在所在repo源（具体方法可参考[应用开发指南](https://openeuler.org/zh/docs/20.03_LTS/docs/ApplicationDev/%E5%BC%80%E5%8F%91%E7%8E%AF%E5%A2%83%E5%87%86%E5%A4%87.html)），然后执行如下指令下载以及安装pkgship及其依赖。 - - ``` - dnf install pkgship - ``` - -* 先下载pkgship的rpm包，然后执行如下命令进行安装（其中“x.x-x”表示版本号，请用实际情况代替）。 - - ``` - rpm -ivh pkgship-x.x-x.oe1.noarch.rpm - ``` - - 或者 - - ``` - dnf install pkgship-x.x-x.oe1.noarch.rpm - ``` - -# 配置参数 -1. 在配置文件中对相应参数进行配置，系统的默认配置文件存放在 /etc/pkgship/packge.ini，请根据实际情况进行配置更改。 - - ``` - vim /etc/pkgship/package.ini - ``` - -2. 创建初始化数据库的yaml配置文件： - conf.yaml 文件默认存放在 /etc/pkgship/ 路径下，pkgship会通过该配置读取要建立的数据库名称以及需要导入的sqlite文件。conf.yaml 示例如下所示。 - - ``` - - dbname:openEuler-20.03-LTS - src_db_file: - - /etc/pkgship/src.sqlite - bin_db_file: - - /etc/pkgship/bin.sqlite - status:enable - priority:1 - ``` - -> 如需更改存放路径，请更改package.ini下的 init_conf_path 选项 - - -# 服务启动和停止 -pkgship使用uWSGI web服务器,启动和停止命令如下所示。 -``` -pkgshipd start - -pkgshipd stop -``` -# 工具使用 -1. 数据库初始化。 - - ``` - pkgship init - ``` - -2. 单包查询。 - - 查询源码包(sourceName)在所有数据库中的信息 。 - - ``` - pkgship single sourceName - ``` - - 查询当前源码包(sourceName)在指定数据库(dbName)中的信息。 - ``` - pkgship single sourceName -db dbName - ``` - -3. 所有包查询。 - 查询所有数据库下包含的所有包的信息。 - - ``` - pkgship list - ``` - - 查询指定数据库(dbName)下的所有包的信息。 - ``` - pkgship list -db dbName - ``` - -4. 安装依赖查询。 - 查询二进制包(binaryName)的安装依赖，按照默认优先级查询数据库。 - - ``` - pkgship installdep binaryName - ``` - - 在指定数据库(dbName)下查询二进制包(binaryName)的所有安装依赖，按照先后顺序指定数据库查询的优先级。 - ``` - pkgship installdep binaryName -dbs dbName1 dbName2... - ``` - -5. 编译依赖查询。 - 查询源码包(sourceName)的所有编译依赖，按照默认优先级查询数据库。 - - ``` - pkgship builddep sourceName - ``` - - 在指定数据库(dbName)下查询源码包(sourceName)的所有安装依赖，按照先后顺序指定数据库查询的优先级。 - ``` - pkgship builddep sourceName -dbs dbName1 dbName2... - ``` - -6. 自编译自安装依赖查询。 - 查询二进制包(binaryName)的安装和编译依赖，按照默认优先级查询数据库。 - - ``` - pkgship selfbuild binaryName - ``` - - 查询源码包(sourceName )的安装和编译依赖，按照默认优先级查询数据库。 - ``` - pkgship selfbuild sourceName -t source - ``` - 其他参数: - - -dbs 指定数据库优先级。 - - ``` - 示例:pkgship selfbuild binaryName -dbs dbName1 dbName2 - ``` - -s 是否查询自编译依赖。其中0表示不查询自编译依赖，1表示查询自编译依赖，默认为0，可以指定1。 - - ``` - 查询自编译示例:pkgship selfbuild sourceName -t source -s 1 - ``` - -w 是否查询对应包的子包。其中0表示不查询对应子包，1表示查询对应子包，默认为0，可以指定1。 - - ``` - 查询子包示例:pkgship selfbuild binaryName -w 1 - ``` - -7. 被依赖查询。 - 查询源码包(sourceName)在某数据库(dbName)中被哪些包所依赖，查询结果默认不包含对应二进制包的子包 。 - - ``` - pkgship bedepend sourceName -db dbName - ``` - - 使查询结果包含二进制包的子包加入参数 -w。 - ``` - pkgship bedepend sourceName -db dbName -w 1 - ``` - -8. 包信息记录修改。 - 变更数据库中(dbName)源码包(sourceName)的maintainer为Newmaintainer 。 - - ``` - pkgship updatepkg sourceName db dbName -m Newmaintainer - ``` - - 变更数据库中(dbName)源码包(sourceName)的maintainlevel为Newmaintainlevel，值在1～4之间。 - - ``` - pkgship updatepkg sourceName db dbName -l Newmaintainlevel - ``` - - 同时变更数据库中(dbName)源码包(sourceName)的maintainer 为Newmaintainer和变更 maintainlevel为Newmaintainlevel。 - - ``` - pkgship updatepkg sourceName db dbName -m Newmaintainer -l Newmaintainlevel - ``` -9. 数据库删除。 - 删除指定数据库(dbName)。 - - ``` - pkgship rm db dbName - ``` - - - diff --git "a/content/zh/docs/userguide/\346\246\202\350\277\260.md" "b/content/zh/docs/userguide/\346\246\202\350\277\260.md" deleted file mode 100644 index 74490c61e7f085f49758d903630e79fcb1949a00..0000000000000000000000000000000000000000 --- "a/content/zh/docs/userguide/\346\246\202\350\277\260.md" +++ /dev/null @@ -1,2 +0,0 @@ -本文主要介绍在openEuler 发行版本过程中使用到的工具集，主要包含工具的介绍，安装以及使用等方面内容。 - diff --git "a/content/zh/docs/userguide/\350\241\245\344\270\201\345\267\245\345\205\267.md" "b/content/zh/docs/userguide/\350\241\245\344\270\201\345\267\245\345\205\267.md" deleted file mode 100644 index fcef036b2d38c89832d60ba8bae32f2c3d7540ec..0000000000000000000000000000000000000000 --- "a/content/zh/docs/userguide/\350\241\245\344\270\201\345\267\245\345\205\267.md" +++ /dev/null @@ -1,254 +0,0 @@ -补丁跟踪 -=== - - -# 简介 - -在 openEuler 发行版开发过程，需要及时更新上游社区各个软件包的最新代码，修改功能 bug 及安全问题，确保发布的 openEuler 发行版尽可能避免缺陷和漏洞。 - -本工具对软件包进行补丁管理，主动监控上游社区提交，自动生成补丁，并自动提交 issue 给对应的 maintainer，同时自动验证补丁基础功能，减少验证工作量支持 maintainer 快速决策。 - -# 架构 - -## C/S架构 - -补丁跟踪采用 C/S 架构。 - -服务端(patch-tracking) ：负责执行补丁跟踪任务，包括：维护跟踪项，识别上游仓库分支代码变更并形成补丁文件，向 Gitee 提交 issue 及 PR，同时 patch-tracking 提供 RESTful 接口，用于对跟踪项进行增删改查操作。 - -客户端：即命令行工具（patch-tracking-cli），通过调用 patch-tracking 的 RESTful 接口，实现对跟踪项的增删改查操作。 - -## 核心流程 - -* 补丁跟踪服务流程 - -**主要步骤：** - -1. 命令行工具写入跟踪项。 -2. 自动从跟踪项配置的上游仓库（例如Github）获取补丁文件。 -3. 创建临时分支，将获取到的补丁文件提交到临时分支。 -4. 自动提交issue到对应项目，并生成关联 issue 的 PR。 - -PatchTracking - -* Maintainer对提交的补丁处理流程 - -**主要步骤：** -1. Maintainer分析临时分支中的补丁文件，判断是否合入。 -2. 执行构建，构建成功后判断是否合入PR。 - -![Maintainer](images/Maintainer.jpg) - -## 数据结构 - -* Tracking表 - -| 序号 | 名称 | 说明 | 类型 | 键 | 允许空 | -|:----:| ----| ----| ----| ----| ----| -| 1 | id | 自增补丁跟踪项序号 | int | - | NO | -| 2 | version_control | 上游SCM的版本控制系统类型 | String | - | NO | -| 3 | scm_repo | 上游SCM仓库地址 | String | - | NO | -| 4 | scm_branch | 上游SCM跟踪分支 | String | - | NO | -| 5 | scm_commit | 上游代码最新处理过的Commit ID | String | - | YES | -| 6 | repo | 包源码在Gitee的仓库地址 | String | Primary | NO | -| 7 | branch | 包源码在Gitee的仓库分支 | String | Primary | NO | -| 8 | enabled | 是否启动跟踪 | Boolean | -| NO | - -* Issue表 - -| 序号 | 名称 | 说明 | 类型 | 键 | 允许空 | -|:----:| ----| ----| ----| ----| ----| -| 1 | issue | issue编号 | String | Primary | NO | -| 2 | repo | 包源码在Gitee的仓库地址 | String | - | NO | -| 3 | branch | 包源码在Gitee的仓库分支 | String | - | NO | - -# 工具部署 - -## 环境要求 - ->* 安装 Python 3.7及以上版本 ->* 已安装 pip3。 - -## 安装依赖 - -执行如下命令安装依赖包。 - -```shell script -yum install -y gcc python3-devel openssl-devel -pip3 install flask flask-sqlalchemy flask-apscheduler requests flask_httpauth -pip3 install -I uwsgi -``` - -## 安装工具 - -执行如下命令安装工具包（其中”x.x.x”表示版本号，请用实际情况代替）。 - -```shell script -rpm -ivh patch-tracking-xxx.rpm -``` - -## 配置参数 - -在配置文件中对相应参数进行配置，配置文件路径为 `/etc/patch-tracking/settings.conf`。 - -1. 配置服务监听地址。 - - ``` - LISTEN = "127.0.0.1:5001" - ``` - -2. GitHub Token， 用于访问托管在 GitHub 上游开源软件仓的仓库信息 ， 生成 GitHub Token 的方法参考 [Creating a personal access token](https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token) 。 - - ``` - GITHUB_ACCESS_TOKEN = "" - ``` - -3. 对于托管在gitee上的需要跟踪的仓库，配置一个有该仓库权限的gitee的token，用于提交patch文件，提交issue，提交PR等操作。 - - ``` - GITEE_ACCESS_TOKEN = "" - ``` - -4. 定时扫描数据库中是否有新增或修改的跟踪项，对扫描到的跟踪项执行获取上游补丁任务，在这里配置扫描的时间间隔，数字单位是秒。 - - ``` - SCAN_DB_INTERVAL = 3600 - ``` - -5. 命令行工具运行过程中，POST接口需要填写进行认证的用户名和口令哈希值。 - - ``` - USER = "admin" - - PASSWORD = "" - ``` - - > `USER`默认值为`admin`。 - -​ 执行如下指令，获取口令的哈希值，其中Test@123为设置的口令。 - -``` -[root]# generate_password Test@123 -pbkdf2:sha256:150000$w38eLeRm$ebb5069ba3b4dda39a698bd1d9d7f5f848af3bd93b11e0cde2b28e9e34bfbbae -``` - -> `口令值`需要满足如下复杂度要求： -> -> * 长度大于等于6个字符 -> * 必须包含大写字母、小写字母、数字、特殊字符（~!@#%^*-_=+） - - 将口令的哈希值`pbkdf2:sha256:150000$w38eLeRm$ebb5069ba3b4dda39a698bd1d9d7f5f848af3bd93b11e0cde2b28e9e34bfbbae`配置到`PASSWORD = ""`引号中。 - -## 启动补丁跟踪服务 - -可以使用以下两种方式启动服务。 - -* 使用systemd方式。 - - ``` - systemctl start patch-tracking - ``` - -* 直接执行可执行程序。 - - ``` - /usr/bin/patch-tracking - ``` - -# 工具使用 - -## 添加跟踪项 - -将需要跟踪的软件仓库和分支与其上游开源软件仓库与分支关联起来，可以通过以下三种方式实现。 - -### 命令行直接添加 - -参数含义： ->--user ：POST接口需要进行认证的用户名，同settings.conf中的USER参数 \ ---password ：POST接口需要进行认证的口令，为settings.conf中的PASSWORD哈希值对应的实际的口令字符串 \ ---server ：启动Patch Tracking服务的URL，例如：127.0.0.1:5001 \ ---version_control ：上游仓库版本的控制工具，只支持github \ ---repo： 需要进行跟踪的仓库名称，格式：组织/仓库 \ ---branch ：需要进行跟踪的仓库的分支名称 \ ---scm_repo ：被跟踪的上游仓库的仓库名称，github格式：组织/仓库 \ ---scm_branch： 被跟踪的上游仓库的仓库的分支 \ ---enable ：是否自动跟踪该仓库 - -例如： -```shell script -patch-tracking-cli --server 127.0.0.1:5001 --user admin --password Test@123 --version_control github --repo testPatchTrack/testPatch1 --branch master --scm_repo BJMX/testPatch01 --scm_branch test --enable true -``` - -### 指定文件添加 - -参数含义： ->--server ：启动Patch Tracking服务的URL，例如：127.0.0.1:5001 \ ---user ：POST接口需要进行认证的用户名，同settings.conf中的USER参数 \ ---password ：POST接口需要进行认证的口令，为settings.conf中的PASSWORD哈希值对应的实际的口令字符串 \ ---file ：yaml文件路径 - -将仓库、分支、版本管理工具、是否启动监控等信息写入yaml文件（例如tracking.yaml），文件路径作为`--file`的入参调用命令。 - -例如： -```shell script -patch-tracking-cli --server 127.0.0.1:5001 --user admin --password Test@123 --file tracking.yaml -``` - -yaml文件内容格式如下，冒号左边的内容不可修改，右边内容根据实际情况填写。 - -```shell script -version_control: github -scm_repo: xxx/xxx -scm_branch: master -repo: xxx/xxx -branch: master -enabled: true -``` - ->version_control ：上游仓库版本的控制工具，只支持github \ -scm_repo ：被跟踪的上游仓库的仓库名称，github格式：组织/仓库 \ -scm_branch ：被跟踪的上游仓库的仓库的分支 \ -repo ：需要进行跟踪的仓库名称，格式：组织/仓库 \ -branch ：需要进行跟踪的仓库的分支名称 \ -enable ：是否自动跟踪该仓库 - -### 指定目录添加 - -在指定的目录，例如`test_yaml`下放入多个`xxx.yaml`文件，执行如下命令，记录指定目录下所有yaml文件的跟踪项。 - -参数含义： ->--user ：POST接口需要进行认证的用户名，同settings.conf中的USER参数 \ ---password ：POST接口需要进行认证的口令，为settings.conf中的PASSWORD哈希值对应的实际的口令字符串 \ ---server ：启动Patch Tracking服务的URL，例如：127.0.0.1:5001 \ ---dir ：存放yaml文件目录的路径 - -```shell script -patch-tracking-cli --server 127.0.0.1:5001 --user admin --password Test@123 --dir /home/Work/test_yaml/ -``` - -## 查询跟踪项 - -```shell script -curl -k https:///tracking -``` -例如： -```shell script -curl -k https://127.0.0.1:5001/tracking -``` - -## 查询生成的 Issue 列表 - -```shell script -curl -k https:///issue -``` -例如： -```shell script -curl -k https://127.0.0.1:5001/issue -``` - -## 码云查看 issue 及 PR - -登录Gitee上进行跟踪的软件项目，在该项目的Issues和Pull Requests页签下，可以查看到名为`[patch tracking] TIME`，例如` [patch tracking] 20200713101548`的条目，该条目即是刚生成的补丁文件的issue和对应PR。 - - - diff --git a/content/zh/menu/index.md b/content/zh/menu/index.md deleted file mode 100644 index 1d6d99d870b18d22a517af3574a05d86ae517626..0000000000000000000000000000000000000000 --- a/content/zh/menu/index.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -headless: true ---- -- [法律声明]({{< relref "./docs/Releasenotes/法律声明.md" >}}) -- [发行说明]({{< relref "./docs/Releasenotes/release_notes.md" >}}) - - [用户须知]({{< relref "./docs/Releasenotes/用户须知.md" >}}) - - [简介]({{< relref "./docs/Releasenotes/简介.md" >}}) - - [系统安装]({{< relref "./docs/Releasenotes/系统安装.md" >}}) - - [关键特性]({{< relref "./docs/Releasenotes/关键特性.md" >}}) - - [已知问题]({{< relref "./docs/Releasenotes/已知问题.md" >}}) - - [已修复问题]({{< relref "./docs/Releasenotes/已修复问题.md" >}}) - - [CVE漏洞]({{< relref "./docs/Releasenotes/CVE漏洞.md" >}}) - - [源代码]({{< relref "./docs/Releasenotes/源代码.md" >}}) - - [参与贡献]({{< relref "./docs/Releasenotes/参与贡献.md" >}}) - - [致谢]({{< relref "./docs/Releasenotes/致谢.md" >}}) - -- [快速入门]({{< relref "./docs/Quickstart/quick-start.md" >}}) - -- [安装指南]({{< relref "./docs/Installation/installation.md" >}}) - - [安装在服务器]({{< relref "./docs/Installation/安装在服务器.md" >}}) - - [安装准备]({{< relref "./docs/Installation/安装准备.md" >}}) - - [安装方式介绍]({{< relref "./docs/Installation/安装方式介绍.md" >}}) - - [安装指导]({{< relref "./docs/Installation/安装指导.md" >}}) - - [使用kickstart自动化安装]({{< relref "./docs/Installation/使用kickstart自动化安装.md" >}}) - - [FAQ]({{< relref "./docs/Installation/FAQ.md" >}}) - - [安装在树莓派]({{< relref "./docs/Installation/安装在树莓派.md" >}}) - - [安装准备]({{< relref "./docs/Installation/安装准备-1.md" >}}) - - [安装方式介绍]({{< relref "./docs/Installation/安装方式介绍-1.md" >}}) - - [安装指导]({{< relref "./docs/Installation/安装指导-1.md" >}}) - - [FAQ]({{< relref "./docs/Installation/FAQ-1.md" >}}) - - [更多资源]({{< relref "./docs/Installation/更多资源.md" >}}) - - -- [管理员指南]({{< relref "./docs/Administration/administration.md" >}}) - - [查看系统信息]({{< relref "./docs/Administration/查看系统信息.md" >}}) - - [基础配置]({{< relref "./docs/Administration/基础配置.md" >}}) - - [管理用户和用户组]({{< relref "./docs/Administration/管理用户和用户组.md" >}}) - - [使用DNF管理软件包]({{< relref "./docs/Administration/使用DNF管理软件包.md" >}}) - - [管理服务]({{< relref "./docs/Administration/管理服务.md" >}}) - - [管理进程]({{< relref "./docs/Administration/管理进程.md" >}}) - - [配置网络]({{< relref "./docs/Administration/配置网络.md" >}}) - - [使用LVM管理硬盘]({{< relref "./docs/Administration/使用LVM管理硬盘.md" >}}) - - [使用KAE加速引擎]({{< relref "./docs/Administration/使用KAE加速引擎.md" >}}) - - [搭建服务]({{< relref "./docs/Administration/搭建服务.md" >}}) - - [搭建repo服务器]({{< relref "./docs/Administration/搭建repo服务器.md" >}}) - - [搭建FTP服务器]({{< relref "./docs/Administration/搭建FTP服务器.md" >}}) - - [搭建web服务器]({{< relref "./docs/Administration/搭建web服务器.md" >}}) - - [搭建数据库服务器]({{< relref "./docs/Administration/搭建数据库服务器.md" >}}) - - [FAQ]({{< relref "./docs/Administration/FAQ-54.md" >}}) - - -- [虚拟化用户指南]({{< relref "./docs/Virtualization/virtualization.md" >}}) - - [认识虚拟化]({{< relref "./docs/Virtualization/认识虚拟化.md" >}}) - - [安装虚拟化]({{< relref "./docs/Virtualization/安装虚拟化.md" >}}) - - [准备使用环境]({{< relref "./docs/Virtualization/准备使用环境.md" >}}) - - [虚拟机配置]({{< relref "./docs/Virtualization/虚拟机配置.md" >}}) - - [管理虚拟机]({{< relref "./docs/Virtualization/管理虚拟机.md" >}}) - - [热迁移虚拟机]({{< relref "./docs/Virtualization/热迁移虚拟机.md" >}}) - - [管理系统资源]({{< relref "./docs/Virtualization/管理系统资源.md" >}}) - - [管理设备]({{< relref "./docs/Virtualization/管理设备.md" >}}) - - [最佳实践]({{< relref "./docs/Virtualization/最佳实践.md" >}}) - - [附录]({{< relref "./docs/Virtualization/附录.md" >}}) - - -- [容器用户指南]({{< relref "./docs/Container/container.md" >}}) - - [iSula容器引擎]({{< relref "./docs/Container/iSula容器引擎.md" >}}) - - [安装、升级与卸载]({{< relref "./docs/Container/安装-升级与卸载.md" >}}) - - [安装与配置]({{< relref "./docs/Container/安装与配置.md" >}}) - - [升级]({{< relref "./docs/Container/升级.md" >}}) - - [卸载]({{< relref "./docs/Container/卸载.md" >}}) - - [使用指南]({{< relref "./docs/Container/使用指南.md" >}}) - - [容器管理]({{< relref "./docs/Container/容器管理.md" >}}) - - [支持CNI网络]({{< relref "./docs/Container/支持CNI网络.md" >}}) - - [特权容器]({{< relref "./docs/Container/特权容器.md" >}}) - - [CRI接口]({{< relref "./docs/Container/CRI接口.md" >}}) - - [镜像管理]({{< relref "./docs/Container/镜像管理.md" >}}) - - [容器健康状态检查]({{< relref "./docs/Container/容器健康状态检查.md" >}}) - - [查询信息]({{< relref "./docs/Container/查询信息.md" >}}) - - [安全特性]({{< relref "./docs/Container/安全特性.md" >}}) - - [支持OCI hooks]({{< relref "./docs/Container/支持OCI-hooks.md" >}}) - - [附录]({{< relref "./docs/Container/附录.md" >}}) - - - [系统容器]({{< relref "./docs/Container/系统容器.md" >}}) - - [安装指导]({{< relref "./docs/Container/安装指导.md" >}}) - - [使用指南]({{< relref "./docs/Container/使用指南-1.md" >}}) - - [指定rootfs创建容器]({{< relref "./docs/Container/指定rootfs创建容器.md" >}}) - - [通过systemd启动容器]({{< relref "./docs/Container/通过systemd启动容器.md" >}}) - - [容器内reboot/shutdown]({{< relref "./docs/Container/容器内reboot-shutdown.md" >}}) - - [cgroup路径可配置]({{< relref "./docs/Container/cgroup路径可配置.md" >}}) - - [namespace化内核参数可写]({{< relref "./docs/Container/namespace化内核参数可写.md" >}}) - - [共享内存通道]({{< relref "./docs/Container/共享内存通道.md" >}}) - - [动态加载内核模块]({{< relref "./docs/Container/动态加载内核模块.md" >}}) - - [环境变量持久化]({{< relref "./docs/Container/环境变量持久化.md" >}}) - - [最大句柄数限制]({{< relref "./docs/Container/最大句柄数限制.md" >}}) - - [安全性和隔离性]({{< relref "./docs/Container/安全性和隔离性.md" >}}) - - [容器资源动态管理]({{< relref "./docs/Container/容器资源动态管理.md" >}}) - - [附录]({{< relref "./docs/Container/附录-2.md" >}}) - - - [安全容器]({{< relref "./docs/Container/安全容器.md" >}}) - - [安装与配置]({{< relref "./docs/Container/安装与配置-2.md" >}}) - - [使用方法]({{< relref "./docs/Container/使用方法-1.md" >}}) - - [管理安全容器的生命周期]({{< relref "./docs/Container/管理安全容器的生命周期.md" >}}) - - [为安全容器配置资源]({{< relref "./docs/Container/为安全容器配置资源.md" >}}) - - [为安全容器配置网络]({{< relref "./docs/Container/为安全容器配置网络.md" >}}) - - [监控安全容器]({{< relref "./docs/Container/监控安全容器.md" >}}) - - [附录]({{< relref "./docs/Container/附录-3.md" >}}) - - - [Docker容器]({{< relref "./docs/Container/Docker容器.md" >}}) - - [安装配置]({{< relref "./docs/Container/安装配置-3.md" >}}) - - [容器管理]({{< relref "./docs/Container/容器管理-3.md" >}}) - - [镜像管理]({{< relref "./docs/Container/镜像管理-3.md" >}}) - - [命令行参考]({{< relref "./docs/Container/命令行参考.md" >}}) - - [容器引擎]({{< relref "./docs/Container/容器引擎-4.md" >}}) - - [容器管理]({{< relref "./docs/Container/容器管理-4.md" >}}) - - [镜像管理]({{< relref "./docs/Container/镜像管理-4.md" >}}) - - [统计信息]({{< relref "./docs/Container/统计信息-4.md" >}}) - - [isula-build构建工具]({{< relref "./docs/Container/isula-build构建工具.md" >}}) - - -- [A-Tune用户指南]({{< relref "./docs/A-Tune/A-Tune.md" >}}) - - [认识A-Tune]({{< relref "./docs/A-Tune/认识A-Tune.md" >}}) - - [安装与部署]({{< relref "./docs/A-Tune/安装与部署.md" >}}) - - [使用方法]({{< relref "./docs/A-Tune/使用方法.md" >}}) - - [常见问题与解决方法]({{< relref "./docs/A-Tune/常见问题与解决方法.md" >}}) - - [附录]({{< relref "./docs/A-Tune/附录.md" >}}) - - -- [应用开发指南]({{< relref "./docs/ApplicationDev/application-development.md" >}})userguide - - [开发环境准备]({{< relref "./docs/ApplicationDev/开发环境准备.md" >}}) - - [使用GCC编译]({{< relref "./docs/ApplicationDev/使用GCC编译.md" >}}) - - [使用make编译]({{< relref "./docs/ApplicationDev/使用make编译.md" >}}) - - [使用JDK编译]({{< relref "./docs/ApplicationDev/使用JDK编译.md" >}}) - - [构建RPM包]({{< relref "./docs/ApplicationDev/构建RPM包.md" >}}) - -- [openEuler工具集用户指南]({{< relref "./docs/userguide/概述.md" >}}) - - [补丁工具]({{< relref "./docs/userguide/补丁工具.md" >}}) - - [pkgship]({{< relref "./docs/userguide/pkgship.md" >}}) \ No newline at end of file diff --git a/docs/.vuepress/components/docs/docsList.vue b/docs/.vuepress/components/docs/docsList.vue new file mode 100644 index 0000000000000000000000000000000000000000..94a22b2410782321a7f154c545ace0937155f042 --- /dev/null +++ b/docs/.vuepress/components/docs/docsList.vue @@ -0,0 +1,397 @@ + + + + + + diff --git a/docs/.vuepress/config.js b/docs/.vuepress/config.js new file mode 100644 index 0000000000000000000000000000000000000000..00745f5e579df449f3ee53e11da9eef7d5d20826 --- /dev/null +++ b/docs/.vuepress/config.js @@ -0,0 +1,51 @@ +module.exports = { + home: false, + title: '', + description: '', + head: [ + ['link', { + rel: 'icon', + href: '/favicon.ico' + }], + ['meta', { + name: 'viewport', + content: 'width=device-width,initial-scale=1,user-scalable=no' + }] + ], + markdown: { + lineNumbers: false + }, + plugins: [ + [require('./sitePlugin.js')] + ], + locales: { + '/': { + lang: 'zh', + title: '', + description: '' + }, + '/en/': { + lang: 'en', + title: '', + description: '' + }, + '/zh/': { + lang: 'zh', + title: '', + description: '' + } + }, + themeConfig: { + dateFormat: 'YYYY-MM-DD', + locales: { + 'en': { + lang: require('./lang/en.js') + }, + 'zh': { + lang: require('./lang/zh.js') + } + }, + smoothScroll: true + + } +} \ No newline at end of file diff --git a/docs/.vuepress/enhanceApp.js b/docs/.vuepress/enhanceApp.js new file mode 100644 index 0000000000000000000000000000000000000000..c0d36b53f1f5b3b141728ffc4dae02574c7a5fe0 --- /dev/null +++ b/docs/.vuepress/enhanceApp.js @@ -0,0 +1,73 @@ +import ElementUI from 'element-ui'; +import './public/style/theme/index.css'; +import './public/style/base.css'; +import locale from 'element-ui/lib/locale/lang/en' +import'./public/style/markdown.less'; +import './public/style/font-en.css'; +import './public/style/font-cn.css'; + +export default ({ + Vue +}) => { + let checkLoop = false; + let checkImport = false; + Vue.mixin({ + data () { + return { + i18n: {}, + + } + }, + mounted () { + if(this.$router && this.$frontmatter) { + document.title = this.$frontmatter.title || 'openeuler'; + } + if(!checkImport){ + if (window.location.href.includes('/en/')) { + checkImport = true; + Vue.use(ElementUI, {locale}); + Vue.prototype.$isCn = false; + } else { + checkImport = true; + Vue.use(ElementUI); + Vue.prototype.$isCn = true; + } + } + }, + created () { + let pagesArr = []; + if(!checkLoop){ + checkLoop = true; + this.$sitePages.forEach(item => { + if(this.$lang === 'zh' && item.path.includes('/zh/')) { + pagesArr.push(item); + } else if(this.$lang === 'en' && !item.path.includes('/zh/')) { + pagesArr.push(item); + } + }) + this.$sitePages = pagesArr; + const originalPush = this.$router.push; + this.$router.push = function push(location) { + return originalPush.call(this, location).catch(err => err); + } + } + + const locales = this.$site; + if(this.$router){ + this.i18n = locales.themeConfig.locales[this.$lang].lang; + } + + }, + methods : { + resolvePath(path){ + if(path){ + const targetLocale = this.$lang === "zh" ? "/zh" : "/en"; + return targetLocale + path; + } + + } + } + }) + + +} \ No newline at end of file diff --git a/docs/.vuepress/lang/en.js b/docs/.vuepress/lang/en.js new file mode 100644 index 0000000000000000000000000000000000000000..76074c0ce6db6a2a24a366dc99f8761c7044a6d4 --- /dev/null +++ b/docs/.vuepress/lang/en.js @@ -0,0 +1,8 @@ +/** + * @file 国际化英文配置主入口 + * */ + +module.exports = { + common: require('./lang-modules/common').en, + documentation: require('./lang-modules/documentation').en +}; \ No newline at end of file diff --git a/docs/.vuepress/lang/lang-modules/common.js b/docs/.vuepress/lang/lang-modules/common.js new file mode 100644 index 0000000000000000000000000000000000000000..fff21511a563183aa44e6271230e373cc97a8515 --- /dev/null +++ b/docs/.vuepress/lang/lang-modules/common.js @@ -0,0 +1,298 @@ +/** + * @file 公共模块国际化配置入口 + * */ + +module.exports = { + cn: { + SEARCH_PLACE_HOLDER: '输入内容', + NAV_ROUTER_CONFIG: [{ + PATH: '/download/', + NAME: '下载', + CHILDREN: [], + CLASS: [] + }, + { + PATH: '/documentation/', + NAME: '文档', + CHILDREN: [], + OTHER_CHILDREN: [ + { + PATH: '/docs/' + } + ], + CLASS: [] + }, + { + PATH: '', + NAME: '互动', + CHILDREN: [{ + NAME: '新闻', + PATH: '/interaction/news-list/' + }, + { + NAME: '博客', + PATH: '/interaction/blog-list/' + }, + { + NAME: '直播', + PATH: '/interaction/live-list/' + }, + { + NAME: '沙龙', + PATH: '/interaction/salon-list/' + }, + { + NAME: '峰会', + PATH: '/interaction/summit-list/' + } + ], + OTHER_CHILDREN: [ + { + PATH: '/news/' + }, + { + PATH: '/blog/' + } + ], + CLASS: [] + }, + { + PATH: '', + NAME: '社区', + CHILDREN: [{ + NAME: '贡献攻略', + PATH: '/community/contribution/' + }, + { + NAME: '行为守则', + PATH: '/community/conduct/' + }, + { + NAME: '邮件列表', + PATH: '/community/mailing-list/' + }, + { + NAME: '认证服务', + PATH: '/community/certification-services/' + } + ], + CLASS: [] + }, + { + PATH: '', + NAME: 'SIG', + CHILDREN: [{ + NAME: '查看SIG', + PATH: '/sig/sig-list/' + }, + { + NAME: '申请流程', + PATH: '/sig/sig-guidance/' + }, + { + NAME: '角色说明', + PATH: '/sig/role-description/' + } + ], + CLASS: [] + }, + { + PATH: '', + NAME: '安全', + CHILDREN: [{ + NAME: '漏洞管理', + PATH: '/security/vulnerability-reporting/' + }, + { + NAME: '安全公告', + PATH: '/security/safety-bulletin/' + }, + { + NAME: 'CVE', + PATH: '/security/cve/' + } + ], + CLASS: [] + } + ], + LANG: 'EN', + GITTE: '源码', + GITTE_RESOURCE_LIST: [{ + NAME: '代码仓', + URL: 'https://gitee.com/openeuler' + }, + { + NAME: '软件包仓', + URL: 'https://gitee.com/src-openeuler' + } + ], + FOOTER: { + MAIL: 'contact@openeuler.org', + COPY_RIGHT: '版权所有 © 2020 openEuler 保留一切权利', + RIGHT_LIST: [{ + NAME: '品牌', + URL: '/other/brand/' + }, + { + NAME: '隐私政策', + URL: '/other/privacy/' + }, + { + NAME: '法律声明', + URL: '/other/legal/' + } + ], + QR_CODE: '扫码关注公众号' + }, + BUILDING:{ + BUILDING:'建设中', + BUILDINGMES:'敬请期待...' + } + }, + en: { + SEARCH_PLACE_HOLDER: 'Input content', + NAV_ROUTER_CONFIG: [{ + PATH: '/download/', + NAME: 'Download', + CHILDREN: [], + CLASS: [] + }, + { + PATH: '/documentation/', + NAME: 'Documentation', + CHILDREN: [], + OTHER_CHILDREN: [ + { + PATH: '/docs/' + } + ], + CLASS: [] + }, + { + PATH: '', + NAME: 'Connect', + CHILDREN: [{ + NAME: 'News', + PATH: '/interaction/news-list/' + }, + { + NAME: 'Blog', + PATH: '/interaction/blog-list/' + }, + { + NAME: 'Live', + PATH: '/interaction/live-list/' + }, + { + NAME: 'Meetups', + PATH: '/interaction/salon-list/' + }, + { + NAME: 'Summit', + PATH: '/interaction/summit-list/' + } + ], + OTHER_CHILDREN: [ + { + PATH: '/news/' + }, + { + PATH: '/blog/' + } + ], + CLASS: [] + }, + { + PATH: '', + NAME: 'Community', + CHILDREN: [{ + NAME: 'Contribution', + PATH: '/community/contribution/' + }, + { + NAME: 'Convention', + PATH: '/community/conduct/' + }, + { + NAME: 'Mail lists', + PATH: '/community/mailing-list/' + }, + { + NAME: 'Certification', + PATH: '/community/certification-services/' + } + ], + CLASS: [] + }, + { + PATH: '', + NAME: 'SIG', + CHILDREN: [{ + NAME: 'SIG lists', + PATH: '/sig/sig-list/' + }, + { + NAME: 'Application', + PATH: '/sig/sig-guidance/' + }, + { + NAME: 'Characters', + PATH: '/sig/role-description/' + } + ], + CLASS: [] + }, + { + PATH: '', + NAME: 'Security', + CHILDREN: [{ + NAME: 'Vulnerability management', + PATH: '/security/vulnerability-reporting/' + }, + { + NAME: 'Security advisories', + PATH: '/security/safety-bulletin/' + }, + { + NAME: 'CVE', + PATH: '/security/cve/' + } + ], + CLASS: [] + } + ], + LANG: '中', + GITTE: 'Source code', + GITTE_RESOURCE_LIST: [{ + NAME: 'Code sources', + URL: 'https://gitee.com/openeuler' + }, + { + NAME: 'Package sources', + URL: 'https://gitee.com/src-openeuler' + } + ], + FOOTER: { + MAIL: 'contact@openeuler.org', + COPY_RIGHT: 'Copyright © 2020 openEuler. All rights reserved.', + RIGHT_LIST: [{ + NAME: 'TradeMark', + URL: '/other/brand/' + }, + { + NAME: 'Legal', + URL: '/other/legal/' + }, + { + NAME: 'Privacy', + URL: '/other/privacy/' + } + ], + QR_CODE: 'Wechat Subscription' + }, + BUILDING:{ + BUILDING:'Building', + BUILDINGMES:'Coming Soon...' + } + } +}; \ No newline at end of file diff --git a/docs/.vuepress/lang/lang-modules/documentation.js b/docs/.vuepress/lang/lang-modules/documentation.js new file mode 100644 index 0000000000000000000000000000000000000000..a01b872887240e9135a2f78fd803fca1daae4027 --- /dev/null +++ b/docs/.vuepress/lang/lang-modules/documentation.js @@ -0,0 +1,24 @@ +/** + * @file 文档模块国际化配置入口 + * */ + +module.exports = { + cn: { + DOCS_LABEL: '文档', + VERSION: '版本', + SELECT_VERSION_LABLE: '选择版本', + PREVIOUS: '上一篇', + NEXT: '下一篇', + FEEDBACK: '意见反馈', + MENU: '目录', + }, + en: { + DOCS_LABEL: 'Docs', + VERSION: 'Version', + SELECT_VERSION_LABLE: 'Select Version', + PREVIOUS: 'Previous', + NEXT: 'Next', + FEEDBACK: 'Feedback', + MENU: 'Menu', + } +}; \ No newline at end of file diff --git a/docs/.vuepress/lang/zh.js b/docs/.vuepress/lang/zh.js new file mode 100644 index 0000000000000000000000000000000000000000..4e1712862d38c4003859410998fc698b595bcab1 --- /dev/null +++ b/docs/.vuepress/lang/zh.js @@ -0,0 +1,8 @@ +/** + * @file 国际化中文配置主入口 + * */ + +module.exports = { + common: require('./lang-modules/common').cn, + documentation: require('./lang-modules/documentation').cn +}; \ No newline at end of file diff --git a/docs/.vuepress/public/code-source.svg b/docs/.vuepress/public/code-source.svg new file mode 100644 index 0000000000000000000000000000000000000000..c044996f0b09411c324a00549ef0b27cadea17e3 --- /dev/null +++ b/docs/.vuepress/public/code-source.svg @@ -0,0 +1,15 @@ + + + Outlined/UI/code source + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/favicon.ico b/docs/.vuepress/public/favicon.ico new file mode 100644 index 0000000000000000000000000000000000000000..fdd736fe42537d70ef8b56d91ce5924dba089a04 Binary files /dev/null and b/docs/.vuepress/public/favicon.ico differ diff --git a/docs/.vuepress/public/fonts/FZLTCHJW.TTF b/docs/.vuepress/public/fonts/FZLTCHJW.TTF new file mode 100644 index 0000000000000000000000000000000000000000..2ba2430be2cfc3bb6de1f2870b6d5364ad69e1e3 Binary files /dev/null and b/docs/.vuepress/public/fonts/FZLTCHJW.TTF differ diff --git a/docs/.vuepress/public/fonts/FZLTHBJW.TTF b/docs/.vuepress/public/fonts/FZLTHBJW.TTF new file mode 100644 index 0000000000000000000000000000000000000000..a6a18957d20cd931c7d2c47428e9c01e2b01bae2 Binary files /dev/null and b/docs/.vuepress/public/fonts/FZLTHBJW.TTF differ diff --git a/docs/.vuepress/public/fonts/FZLTHJW.TTF b/docs/.vuepress/public/fonts/FZLTHJW.TTF new file mode 100644 index 0000000000000000000000000000000000000000..379dc975c37291aa56568ff1f078ed12345a280e Binary files /dev/null and b/docs/.vuepress/public/fonts/FZLTHJW.TTF differ diff --git a/docs/.vuepress/public/fonts/FZLTXHJW.TTF b/docs/.vuepress/public/fonts/FZLTXHJW.TTF new file mode 100644 index 0000000000000000000000000000000000000000..d1ea19d3babffe691b857797a2429d635a07174c Binary files /dev/null and b/docs/.vuepress/public/fonts/FZLTXHJW.TTF differ diff --git a/docs/.vuepress/public/fonts/FZLTXIHJW.TTF b/docs/.vuepress/public/fonts/FZLTXIHJW.TTF new file mode 100644 index 0000000000000000000000000000000000000000..5800b22a5e222d3a42a35fb91b020f806520ed23 Binary files /dev/null and b/docs/.vuepress/public/fonts/FZLTXIHJW.TTF differ diff --git a/docs/.vuepress/public/fonts/FZLTZHJW.TTF b/docs/.vuepress/public/fonts/FZLTZHJW.TTF new file mode 100644 index 0000000000000000000000000000000000000000..6bdccda72632dbcb6d3be649c42fdf67043ea2f0 Binary files /dev/null and b/docs/.vuepress/public/fonts/FZLTZHJW.TTF differ diff --git a/docs/.vuepress/public/fonts/HuaweiSans-Bold.ttf b/docs/.vuepress/public/fonts/HuaweiSans-Bold.ttf new file mode 100644 index 0000000000000000000000000000000000000000..f3a838546d3141c6684098f77bdaa763db8e5ffe Binary files /dev/null and b/docs/.vuepress/public/fonts/HuaweiSans-Bold.ttf differ diff --git a/docs/.vuepress/public/fonts/HuaweiSans-Light.ttf b/docs/.vuepress/public/fonts/HuaweiSans-Light.ttf new file mode 100644 index 0000000000000000000000000000000000000000..d3b3ac183eab2eb6e69b7b49905157b72dffdf47 Binary files /dev/null and b/docs/.vuepress/public/fonts/HuaweiSans-Light.ttf differ diff --git a/docs/.vuepress/public/fonts/HuaweiSans-Medium.ttf b/docs/.vuepress/public/fonts/HuaweiSans-Medium.ttf new file mode 100644 index 0000000000000000000000000000000000000000..6878ed7c64b5f0d0ac4c24f3fcbfba9aa90e58a1 Binary files /dev/null and b/docs/.vuepress/public/fonts/HuaweiSans-Medium.ttf differ diff --git a/docs/.vuepress/public/fonts/HuaweiSans-Regular.ttf b/docs/.vuepress/public/fonts/HuaweiSans-Regular.ttf new file mode 100644 index 0000000000000000000000000000000000000000..3118eaffb6d174531b17061c8c133b591256e152 Binary files /dev/null and b/docs/.vuepress/public/fonts/HuaweiSans-Regular.ttf differ diff --git a/docs/.vuepress/public/fonts/HuaweiSans-Thin.ttf b/docs/.vuepress/public/fonts/HuaweiSans-Thin.ttf new file mode 100644 index 0000000000000000000000000000000000000000..37d7a55332f1748b8fe2726fad411a7da86af4f0 Binary files /dev/null and b/docs/.vuepress/public/fonts/HuaweiSans-Thin.ttf differ diff --git a/docs/.vuepress/public/fonts/Roboto-Black.ttf b/docs/.vuepress/public/fonts/Roboto-Black.ttf new file mode 100644 index 0000000000000000000000000000000000000000..86ec2b29ba56a3d6c45f1a8584ff3780fa70c60e Binary files /dev/null and b/docs/.vuepress/public/fonts/Roboto-Black.ttf differ diff --git a/docs/.vuepress/public/fonts/Roboto-BlackItalic.ttf b/docs/.vuepress/public/fonts/Roboto-BlackItalic.ttf new file mode 100644 index 0000000000000000000000000000000000000000..1904c99b2c81e3e278d3c373f397b38049824d4c Binary files /dev/null and b/docs/.vuepress/public/fonts/Roboto-BlackItalic.ttf differ diff --git a/docs/.vuepress/public/fonts/Roboto-Bold.ttf b/docs/.vuepress/public/fonts/Roboto-Bold.ttf new file mode 100644 index 0000000000000000000000000000000000000000..91ec21227866ca9d1cf77ec13660b7b85ec900dd Binary files /dev/null and b/docs/.vuepress/public/fonts/Roboto-Bold.ttf differ diff --git a/docs/.vuepress/public/fonts/Roboto-BoldCondensed.ttf b/docs/.vuepress/public/fonts/Roboto-BoldCondensed.ttf new file mode 100644 index 0000000000000000000000000000000000000000..d7ea8833ba369ec975846497e5fa05741295eacf Binary files /dev/null and b/docs/.vuepress/public/fonts/Roboto-BoldCondensed.ttf differ diff --git a/docs/.vuepress/public/fonts/Roboto-BoldCondensedItalic.ttf b/docs/.vuepress/public/fonts/Roboto-BoldCondensedItalic.ttf new file mode 100644 index 0000000000000000000000000000000000000000..3c9635a9f0ccc304ddeadc16c5d1fd3a37c68ef7 Binary files /dev/null and b/docs/.vuepress/public/fonts/Roboto-BoldCondensedItalic.ttf differ diff --git a/docs/.vuepress/public/fonts/Roboto-BoldItalic.ttf b/docs/.vuepress/public/fonts/Roboto-BoldItalic.ttf new file mode 100644 index 0000000000000000000000000000000000000000..4013bf88a5e7b4e9ca4f8e53774d4f0a1346b52b Binary files /dev/null and b/docs/.vuepress/public/fonts/Roboto-BoldItalic.ttf differ diff --git a/docs/.vuepress/public/fonts/Roboto-Condensed.ttf b/docs/.vuepress/public/fonts/Roboto-Condensed.ttf new file mode 100644 index 0000000000000000000000000000000000000000..6e7575a16a42802678855523efd2cb17cee01a86 Binary files /dev/null and b/docs/.vuepress/public/fonts/Roboto-Condensed.ttf differ diff --git a/docs/.vuepress/public/fonts/Roboto-CondensedItalic.ttf b/docs/.vuepress/public/fonts/Roboto-CondensedItalic.ttf new file mode 100644 index 0000000000000000000000000000000000000000..5ed712c9bde5cf7229eefaa8268dc027a8a06ea5 Binary files /dev/null and b/docs/.vuepress/public/fonts/Roboto-CondensedItalic.ttf differ diff --git a/docs/.vuepress/public/fonts/Roboto-Italic.ttf b/docs/.vuepress/public/fonts/Roboto-Italic.ttf new file mode 100644 index 0000000000000000000000000000000000000000..9f49ffd869194a92c2e71895169488cb4d037a00 Binary files /dev/null and b/docs/.vuepress/public/fonts/Roboto-Italic.ttf differ diff --git a/docs/.vuepress/public/fonts/Roboto-Light.ttf b/docs/.vuepress/public/fonts/Roboto-Light.ttf new file mode 100644 index 0000000000000000000000000000000000000000..d43e943312e0f2c653815dd791d93f94f0abd73f Binary files /dev/null and b/docs/.vuepress/public/fonts/Roboto-Light.ttf differ diff --git a/docs/.vuepress/public/fonts/Roboto-LightItalic.ttf b/docs/.vuepress/public/fonts/Roboto-LightItalic.ttf new file mode 100644 index 0000000000000000000000000000000000000000..c11442ce5c5c3d1ba5880fa6fb778af61004ff71 Binary files /dev/null and b/docs/.vuepress/public/fonts/Roboto-LightItalic.ttf differ diff --git a/docs/.vuepress/public/fonts/Roboto-Medium.ttf b/docs/.vuepress/public/fonts/Roboto-Medium.ttf new file mode 100644 index 0000000000000000000000000000000000000000..87983419893a8952c3f286dc56d37fb94e320da0 Binary files /dev/null and b/docs/.vuepress/public/fonts/Roboto-Medium.ttf differ diff --git a/docs/.vuepress/public/fonts/Roboto-MediumItalic.ttf b/docs/.vuepress/public/fonts/Roboto-MediumItalic.ttf new file mode 100644 index 0000000000000000000000000000000000000000..5e866375e6d46984cca27f4b62d0e7082388763b Binary files /dev/null and b/docs/.vuepress/public/fonts/Roboto-MediumItalic.ttf differ diff --git a/docs/.vuepress/public/fonts/Roboto-Regular.ttf b/docs/.vuepress/public/fonts/Roboto-Regular.ttf new file mode 100644 index 0000000000000000000000000000000000000000..7d9a6c4c32d7e920b549caf531e390733496b6e0 Binary files /dev/null and b/docs/.vuepress/public/fonts/Roboto-Regular.ttf differ diff --git a/docs/.vuepress/public/fonts/Roboto-Thin.ttf b/docs/.vuepress/public/fonts/Roboto-Thin.ttf new file mode 100644 index 0000000000000000000000000000000000000000..861d63adb6dee256c5d63879c323d27b5b0b047b Binary files /dev/null and b/docs/.vuepress/public/fonts/Roboto-Thin.ttf differ diff --git a/docs/.vuepress/public/fonts/Roboto-ThinItalic.ttf b/docs/.vuepress/public/fonts/Roboto-ThinItalic.ttf new file mode 100644 index 0000000000000000000000000000000000000000..e65145f371d04239e075d1841b0f5a98238ccc3c Binary files /dev/null and b/docs/.vuepress/public/fonts/Roboto-ThinItalic.ttf differ diff --git a/docs/.vuepress/public/fonts/icomoon.eot b/docs/.vuepress/public/fonts/icomoon.eot new file mode 100644 index 0000000000000000000000000000000000000000..296ebc035c5b8d333fc5b33d192e9aab34674455 Binary files /dev/null and b/docs/.vuepress/public/fonts/icomoon.eot differ diff --git a/docs/.vuepress/public/fonts/icomoon.svg b/docs/.vuepress/public/fonts/icomoon.svg new file mode 100644 index 0000000000000000000000000000000000000000..5993cbfc3e08ce844a2560a3c02a5b559c3db9a4 --- /dev/null +++ b/docs/.vuepress/public/fonts/icomoon.svg @@ -0,0 +1,13 @@ + + + +Generated by IcoMoon + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/fonts/icomoon.ttf b/docs/.vuepress/public/fonts/icomoon.ttf new file mode 100644 index 0000000000000000000000000000000000000000..4d22f59786856202df95442ab1af225a53a7a1e3 Binary files /dev/null and b/docs/.vuepress/public/fonts/icomoon.ttf differ diff --git a/docs/.vuepress/public/fonts/icomoon.woff b/docs/.vuepress/public/fonts/icomoon.woff new file mode 100644 index 0000000000000000000000000000000000000000..04a91af85e46766f2d489439cef5f58fa209467b Binary files /dev/null and b/docs/.vuepress/public/fonts/icomoon.woff differ diff --git a/docs/.vuepress/public/footer-logo.png b/docs/.vuepress/public/footer-logo.png new file mode 100644 index 0000000000000000000000000000000000000000..e029c8d7daad57c231228b2140a505fcf93b8e79 Binary files /dev/null and b/docs/.vuepress/public/footer-logo.png differ diff --git a/docs/.vuepress/public/footer-logo.svg b/docs/.vuepress/public/footer-logo.svg new file mode 100644 index 0000000000000000000000000000000000000000..f7c0b544604181a8af602653b8fd3d19ca2edc00 --- /dev/null +++ b/docs/.vuepress/public/footer-logo.svg @@ -0,0 +1,29 @@ + + + openEuler + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/community/conduct/conduct-banner.png b/docs/.vuepress/public/img/community/conduct/conduct-banner.png new file mode 100644 index 0000000000000000000000000000000000000000..f1ffc39b4c05f1871f7a1523c851b904a44f35ba Binary files /dev/null and b/docs/.vuepress/public/img/community/conduct/conduct-banner.png differ diff --git a/docs/.vuepress/public/img/community/contribution/bkg-community.png b/docs/.vuepress/public/img/community/contribution/bkg-community.png new file mode 100644 index 0000000000000000000000000000000000000000..a6c2a2737b0a4712b8c93e62ae1a02fe79b8551b Binary files /dev/null and b/docs/.vuepress/public/img/community/contribution/bkg-community.png differ diff --git a/docs/.vuepress/public/img/community/contribution/cla.gif b/docs/.vuepress/public/img/community/contribution/cla.gif new file mode 100644 index 0000000000000000000000000000000000000000..be333ead07fbaf303203246f7334e1acfb49eb38 Binary files /dev/null and b/docs/.vuepress/public/img/community/contribution/cla.gif differ diff --git a/docs/.vuepress/public/img/community/contribution/cla.png b/docs/.vuepress/public/img/community/contribution/cla.png new file mode 100644 index 0000000000000000000000000000000000000000..498a372eef9a051e317406d6ca0a588e7f840f14 Binary files /dev/null and b/docs/.vuepress/public/img/community/contribution/cla.png differ diff --git a/docs/.vuepress/public/img/community/contribution/commit.gif b/docs/.vuepress/public/img/community/contribution/commit.gif new file mode 100644 index 0000000000000000000000000000000000000000..7deaf9b0881dacd2c0d947adc82a3c3ce6a78451 Binary files /dev/null and b/docs/.vuepress/public/img/community/contribution/commit.gif differ diff --git a/docs/.vuepress/public/img/community/contribution/commit.png b/docs/.vuepress/public/img/community/contribution/commit.png new file mode 100644 index 0000000000000000000000000000000000000000..66e5cc2e4cdc9fb28ba8e8a43a6914056a645ee1 Binary files /dev/null and b/docs/.vuepress/public/img/community/contribution/commit.png differ diff --git a/docs/.vuepress/public/img/community/contribution/contribution.gif b/docs/.vuepress/public/img/community/contribution/contribution.gif new file mode 100644 index 0000000000000000000000000000000000000000..1bffb75b840cb28c3a8686e31be94c5b8fdad210 Binary files /dev/null and b/docs/.vuepress/public/img/community/contribution/contribution.gif differ diff --git a/docs/.vuepress/public/img/community/contribution/contribution.png b/docs/.vuepress/public/img/community/contribution/contribution.png new file mode 100644 index 0000000000000000000000000000000000000000..73f4dd43c44393c300cfd49817102a43c295c4bd Binary files /dev/null and b/docs/.vuepress/public/img/community/contribution/contribution.png differ diff --git a/docs/.vuepress/public/img/community/contribution/issue.gif b/docs/.vuepress/public/img/community/contribution/issue.gif new file mode 100644 index 0000000000000000000000000000000000000000..2542e6e7711be33b5002148ad6951d81ad2658b2 Binary files /dev/null and b/docs/.vuepress/public/img/community/contribution/issue.gif differ diff --git a/docs/.vuepress/public/img/community/contribution/issue.png b/docs/.vuepress/public/img/community/contribution/issue.png new file mode 100644 index 0000000000000000000000000000000000000000..b53c5ca8cf0319a034a78f5d81c0bd61d5b271b3 Binary files /dev/null and b/docs/.vuepress/public/img/community/contribution/issue.png differ diff --git a/docs/.vuepress/public/img/community/contribution/plane1.svg b/docs/.vuepress/public/img/community/contribution/plane1.svg new file mode 100644 index 0000000000000000000000000000000000000000..d3c782241325e89a14e3d91838dff8f423b823d7 --- /dev/null +++ b/docs/.vuepress/public/img/community/contribution/plane1.svg @@ -0,0 +1,44 @@ + + + 编组 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/community/contribution/plane2.svg b/docs/.vuepress/public/img/community/contribution/plane2.svg new file mode 100644 index 0000000000000000000000000000000000000000..5421b6fe6e4f5784baf337359a7769f6dd8d65bd --- /dev/null +++ b/docs/.vuepress/public/img/community/contribution/plane2.svg @@ -0,0 +1,38 @@ + + + 编组备份 13 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/community/contribution/plane3.svg b/docs/.vuepress/public/img/community/contribution/plane3.svg new file mode 100644 index 0000000000000000000000000000000000000000..ccb5e7ecd136c2ce6034dea33a5bf802ead65fea --- /dev/null +++ b/docs/.vuepress/public/img/community/contribution/plane3.svg @@ -0,0 +1,45 @@ + + + 编组备份 14 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/community/contribution/plane4.svg b/docs/.vuepress/public/img/community/contribution/plane4.svg new file mode 100644 index 0000000000000000000000000000000000000000..90cae325f14aa8842437cf4e4c7a0a68dd33c4d7 --- /dev/null +++ b/docs/.vuepress/public/img/community/contribution/plane4.svg @@ -0,0 +1,38 @@ + + + 编组备份 15 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/community/contribution/rode1.svg b/docs/.vuepress/public/img/community/contribution/rode1.svg new file mode 100644 index 0000000000000000000000000000000000000000..81a1fb6925d9856d3c412521c7217ca5041f9299 --- /dev/null +++ b/docs/.vuepress/public/img/community/contribution/rode1.svg @@ -0,0 +1,10 @@ + + + 路径 4 + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/community/contribution/rode2.svg b/docs/.vuepress/public/img/community/contribution/rode2.svg new file mode 100644 index 0000000000000000000000000000000000000000..9273536b627a315b6b5e98ebeb39d0975dc3b117 --- /dev/null +++ b/docs/.vuepress/public/img/community/contribution/rode2.svg @@ -0,0 +1,10 @@ + + + 路径 10备份 2 + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/community/contribution/rode3.svg b/docs/.vuepress/public/img/community/contribution/rode3.svg new file mode 100644 index 0000000000000000000000000000000000000000..0f6a4f2039155748a9923547500bce0410966125 --- /dev/null +++ b/docs/.vuepress/public/img/community/contribution/rode3.svg @@ -0,0 +1,10 @@ + + + 路径 11备份 2 + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/community/contribution/rode4.svg b/docs/.vuepress/public/img/community/contribution/rode4.svg new file mode 100644 index 0000000000000000000000000000000000000000..fa31d14c710d327be36eeae3b4f37879d646d4a5 --- /dev/null +++ b/docs/.vuepress/public/img/community/contribution/rode4.svg @@ -0,0 +1,10 @@ + + + 路径 12备份 2 + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/community/contribution/sig.gif b/docs/.vuepress/public/img/community/contribution/sig.gif new file mode 100644 index 0000000000000000000000000000000000000000..da518c4b7dea160d64bbb3d1edf284d8332decb0 Binary files /dev/null and b/docs/.vuepress/public/img/community/contribution/sig.gif differ diff --git a/docs/.vuepress/public/img/community/contribution/sig.png b/docs/.vuepress/public/img/community/contribution/sig.png new file mode 100644 index 0000000000000000000000000000000000000000..5e5768aaae7fa2db9dfce2ee8d18e58edd4df24d Binary files /dev/null and b/docs/.vuepress/public/img/community/contribution/sig.png differ diff --git a/docs/.vuepress/public/img/community/maillist/mail-banner.png b/docs/.vuepress/public/img/community/maillist/mail-banner.png new file mode 100644 index 0000000000000000000000000000000000000000..a14a2a59373557caf728c6bf5a55ae3e91ecebc0 Binary files /dev/null and b/docs/.vuepress/public/img/community/maillist/mail-banner.png differ diff --git a/docs/.vuepress/public/img/community/maillist/mail1.png b/docs/.vuepress/public/img/community/maillist/mail1.png new file mode 100644 index 0000000000000000000000000000000000000000..f486e3d5d8fd3bac93bdb0136f1ca38bfa7fcd9c Binary files /dev/null and b/docs/.vuepress/public/img/community/maillist/mail1.png differ diff --git a/docs/.vuepress/public/img/community/maillist/mail2.png b/docs/.vuepress/public/img/community/maillist/mail2.png new file mode 100644 index 0000000000000000000000000000000000000000..e6a033f7099461b773cb8c4219fd513847916ee1 Binary files /dev/null and b/docs/.vuepress/public/img/community/maillist/mail2.png differ diff --git a/docs/.vuepress/public/img/community/maillist/mail3.png b/docs/.vuepress/public/img/community/maillist/mail3.png new file mode 100644 index 0000000000000000000000000000000000000000..9795cd8e49755564370e9a8d3e89b3f50b02f2b3 Binary files /dev/null and b/docs/.vuepress/public/img/community/maillist/mail3.png differ diff --git a/docs/.vuepress/public/img/community/maillist/mail4.png b/docs/.vuepress/public/img/community/maillist/mail4.png new file mode 100644 index 0000000000000000000000000000000000000000..259f1a4f4e10997f218bdfb712ae2b358731a732 Binary files /dev/null and b/docs/.vuepress/public/img/community/maillist/mail4.png differ diff --git a/docs/.vuepress/public/img/docs/docs-administration.svg b/docs/.vuepress/public/img/docs/docs-administration.svg new file mode 100644 index 0000000000000000000000000000000000000000..b3cc597426881b998faa3a97f9d39279070e593e --- /dev/null +++ b/docs/.vuepress/public/img/docs/docs-administration.svg @@ -0,0 +1,35 @@ + + + Outlined/UI/paper + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/docs/docs-application.svg b/docs/.vuepress/public/img/docs/docs-application.svg new file mode 100644 index 0000000000000000000000000000000000000000..420fd3367982d6a00b15227843c8523fdf4aa25f --- /dev/null +++ b/docs/.vuepress/public/img/docs/docs-application.svg @@ -0,0 +1,35 @@ + + + Outlined/UI/paper + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/docs/docs-banner.png b/docs/.vuepress/public/img/docs/docs-banner.png new file mode 100644 index 0000000000000000000000000000000000000000..6c2d09c2b4cc505d4241005ff3fd08b1bd315787 Binary files /dev/null and b/docs/.vuepress/public/img/docs/docs-banner.png differ diff --git a/docs/.vuepress/public/img/docs/docs-exploit.svg b/docs/.vuepress/public/img/docs/docs-exploit.svg new file mode 100644 index 0000000000000000000000000000000000000000..f1c31d57d6220a9f46b6aa72b6fbb06a4242395e --- /dev/null +++ b/docs/.vuepress/public/img/docs/docs-exploit.svg @@ -0,0 +1,33 @@ + + + Outlined/UI/paper + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/docs/docs-installation.svg b/docs/.vuepress/public/img/docs/docs-installation.svg new file mode 100644 index 0000000000000000000000000000000000000000..74ae68531a12ab916409cfacc42e7fd3c159691c --- /dev/null +++ b/docs/.vuepress/public/img/docs/docs-installation.svg @@ -0,0 +1,35 @@ + + + Outlined/UI/paper + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/docs/docs-quickstart.svg b/docs/.vuepress/public/img/docs/docs-quickstart.svg new file mode 100644 index 0000000000000000000000000000000000000000..44640ff4701f05fd1d4208ca208420a89b00b7c3 --- /dev/null +++ b/docs/.vuepress/public/img/docs/docs-quickstart.svg @@ -0,0 +1,35 @@ + + + Outlined/UI/paper + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/docs/docs-releasenotes.svg b/docs/.vuepress/public/img/docs/docs-releasenotes.svg new file mode 100644 index 0000000000000000000000000000000000000000..85905737ad8776896fba55fb3e50c04d8141816b --- /dev/null +++ b/docs/.vuepress/public/img/docs/docs-releasenotes.svg @@ -0,0 +1,35 @@ + + + Outlined/UI/paper + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/docs/docs-user.svg b/docs/.vuepress/public/img/docs/docs-user.svg new file mode 100644 index 0000000000000000000000000000000000000000..194a8c69372e61a26e0be5fe10d273e50a6d1423 --- /dev/null +++ b/docs/.vuepress/public/img/docs/docs-user.svg @@ -0,0 +1,35 @@ + + + Outlined/UI/paper + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/docs/icon-document.svg b/docs/.vuepress/public/img/docs/icon-document.svg new file mode 100644 index 0000000000000000000000000000000000000000..6fffb75e09883cececcbe4408025e6d35b3005aa --- /dev/null +++ b/docs/.vuepress/public/img/docs/icon-document.svg @@ -0,0 +1,9 @@ + + + Style + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/events/20200707-openeluer-live-01.png b/docs/.vuepress/public/img/events/20200707-openeluer-live-01.png new file mode 100644 index 0000000000000000000000000000000000000000..a92d6676fd3400602e5cfe2e6fb7ca146b5cd809 Binary files /dev/null and b/docs/.vuepress/public/img/events/20200707-openeluer-live-01.png differ diff --git a/docs/.vuepress/public/img/events/20200723-openeluer-live-01.jpg b/docs/.vuepress/public/img/events/20200723-openeluer-live-01.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38d92688e1ae340fe801b03608762368eab277c0 Binary files /dev/null and b/docs/.vuepress/public/img/events/20200723-openeluer-live-01.jpg differ diff --git a/docs/.vuepress/public/img/events/2020hdc/1.png b/docs/.vuepress/public/img/events/2020hdc/1.png new file mode 100644 index 0000000000000000000000000000000000000000..2e3ddfc52ff02647abbfb7b00877afe978b39105 Binary files /dev/null and b/docs/.vuepress/public/img/events/2020hdc/1.png differ diff --git a/docs/.vuepress/public/img/events/2020hdc/2.png b/docs/.vuepress/public/img/events/2020hdc/2.png new file mode 100644 index 0000000000000000000000000000000000000000..5c9387f46288bd1ef66844c75b19be73b8f2d0a9 Binary files /dev/null and b/docs/.vuepress/public/img/events/2020hdc/2.png differ diff --git a/docs/.vuepress/public/img/events/2020hdc/3.png b/docs/.vuepress/public/img/events/2020hdc/3.png new file mode 100644 index 0000000000000000000000000000000000000000..cbbc21c6d35c40cd8334b97db191b37f64d24042 Binary files /dev/null and b/docs/.vuepress/public/img/events/2020hdc/3.png differ diff --git a/docs/.vuepress/public/img/events/banner-20200104.png b/docs/.vuepress/public/img/events/banner-20200104.png new file mode 100644 index 0000000000000000000000000000000000000000..526c2a4b0a8a537628239450f3c669f3210b873f Binary files /dev/null and b/docs/.vuepress/public/img/events/banner-20200104.png differ diff --git a/docs/.vuepress/public/img/events/hdc202001.png b/docs/.vuepress/public/img/events/hdc202001.png new file mode 100644 index 0000000000000000000000000000000000000000..b8d1109ecfd3a90b056af11f3d7523783fa3f954 Binary files /dev/null and b/docs/.vuepress/public/img/events/hdc202001.png differ diff --git a/docs/.vuepress/public/img/events/summer-2020-wechat-2.jpg b/docs/.vuepress/public/img/events/summer-2020-wechat-2.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb5014bbe9ab505ec2cfa816f5a4c5c35619c19d Binary files /dev/null and b/docs/.vuepress/public/img/events/summer-2020-wechat-2.jpg differ diff --git a/docs/.vuepress/public/img/events/summer-2020-wechat-3.jpg b/docs/.vuepress/public/img/events/summer-2020-wechat-3.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b38edab65a93fc0d438e6cdafe349e8a1e8beab4 Binary files /dev/null and b/docs/.vuepress/public/img/events/summer-2020-wechat-3.jpg differ diff --git a/docs/.vuepress/public/img/events/summer-2020-wechat.jpg b/docs/.vuepress/public/img/events/summer-2020-wechat.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb5014bbe9ab505ec2cfa816f5a4c5c35619c19d Binary files /dev/null and b/docs/.vuepress/public/img/events/summer-2020-wechat.jpg differ diff --git a/docs/.vuepress/public/img/events/summer1.png b/docs/.vuepress/public/img/events/summer1.png new file mode 100644 index 0000000000000000000000000000000000000000..1c70db56fc81ebad385d99a2c096921177bc6472 Binary files /dev/null and b/docs/.vuepress/public/img/events/summer1.png differ diff --git a/docs/.vuepress/public/img/events/summer2.png b/docs/.vuepress/public/img/events/summer2.png new file mode 100644 index 0000000000000000000000000000000000000000..1f820d76a629efd4abc9387ac3474efc6d8fc673 Binary files /dev/null and b/docs/.vuepress/public/img/events/summer2.png differ diff --git a/docs/.vuepress/public/img/events/summer3.jpeg b/docs/.vuepress/public/img/events/summer3.jpeg new file mode 100644 index 0000000000000000000000000000000000000000..742330cab433b13e925c638bcbfa7af15cff12bf Binary files /dev/null and b/docs/.vuepress/public/img/events/summer3.jpeg differ diff --git a/docs/.vuepress/public/img/home/1.jpg b/docs/.vuepress/public/img/home/1.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65bcb649a522f7c3a9bd97870f2f8620bbc0963c Binary files /dev/null and b/docs/.vuepress/public/img/home/1.jpg differ diff --git a/docs/.vuepress/public/img/home/2.png b/docs/.vuepress/public/img/home/2.png new file mode 100644 index 0000000000000000000000000000000000000000..caea8e2e8e49846568b5999937ca2586848bf30d Binary files /dev/null and b/docs/.vuepress/public/img/home/2.png differ diff --git a/docs/.vuepress/public/img/home/Banner0.gif b/docs/.vuepress/public/img/home/Banner0.gif new file mode 100644 index 0000000000000000000000000000000000000000..7dfb1c2ed726f5ea56e1cf08b773375f36942aa3 Binary files /dev/null and b/docs/.vuepress/public/img/home/Banner0.gif differ diff --git a/docs/.vuepress/public/img/home/Banner1.gif b/docs/.vuepress/public/img/home/Banner1.gif new file mode 100644 index 0000000000000000000000000000000000000000..6f0dec78dbbb88a013b304ec4b85e27540d2c694 Binary files /dev/null and b/docs/.vuepress/public/img/home/Banner1.gif differ diff --git a/docs/.vuepress/public/img/home/Banner2.gif b/docs/.vuepress/public/img/home/Banner2.gif new file mode 100644 index 0000000000000000000000000000000000000000..e345c5e3337d15c9cf9a1d3dd2b25b8bdb4d7e63 Binary files /dev/null and b/docs/.vuepress/public/img/home/Banner2.gif differ diff --git a/docs/.vuepress/public/img/home/BannerS.gif b/docs/.vuepress/public/img/home/BannerS.gif new file mode 100644 index 0000000000000000000000000000000000000000..8f90f7eb1026849daadc8cb8b93199a33f8ab2df Binary files /dev/null and b/docs/.vuepress/public/img/home/BannerS.gif differ diff --git a/docs/.vuepress/public/img/home/BannerVideo.png b/docs/.vuepress/public/img/home/BannerVideo.png new file mode 100644 index 0000000000000000000000000000000000000000..a018409cf867863b51a83d6d3e51b3227576a4fd Binary files /dev/null and b/docs/.vuepress/public/img/home/BannerVideo.png differ diff --git a/docs/.vuepress/public/img/home/Card1.png b/docs/.vuepress/public/img/home/Card1.png new file mode 100644 index 0000000000000000000000000000000000000000..2a39d97fab94afbd156f325c4a4d224606ccb361 Binary files /dev/null and b/docs/.vuepress/public/img/home/Card1.png differ diff --git a/docs/.vuepress/public/img/home/Card2.png b/docs/.vuepress/public/img/home/Card2.png new file mode 100644 index 0000000000000000000000000000000000000000..52d1b9a53eb8e90d660dd7c15e3212cb36276b72 Binary files /dev/null and b/docs/.vuepress/public/img/home/Card2.png differ diff --git a/docs/.vuepress/public/img/home/Card3.png b/docs/.vuepress/public/img/home/Card3.png new file mode 100644 index 0000000000000000000000000000000000000000..2a39d97fab94afbd156f325c4a4d224606ccb361 Binary files /dev/null and b/docs/.vuepress/public/img/home/Card3.png differ diff --git a/docs/.vuepress/public/img/home/Card4.png b/docs/.vuepress/public/img/home/Card4.png new file mode 100644 index 0000000000000000000000000000000000000000..6cd484dcd0829a8e23b7ccb0da23928a3747804e Binary files /dev/null and b/docs/.vuepress/public/img/home/Card4.png differ diff --git a/docs/.vuepress/public/img/home/Gitee.png b/docs/.vuepress/public/img/home/Gitee.png new file mode 100644 index 0000000000000000000000000000000000000000..6bcf1963425e55703f50aac62d345ae068d9365d Binary files /dev/null and b/docs/.vuepress/public/img/home/Gitee.png differ diff --git a/docs/.vuepress/public/img/home/areaECS.svg b/docs/.vuepress/public/img/home/areaECS.svg new file mode 100644 index 0000000000000000000000000000000000000000..ffc2c67263363a9cbb3a287e560f717638e58612 --- /dev/null +++ b/docs/.vuepress/public/img/home/areaECS.svg @@ -0,0 +1,39 @@ + + + 编组 2备份 3 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/areaHardware.svg b/docs/.vuepress/public/img/home/areaHardware.svg new file mode 100644 index 0000000000000000000000000000000000000000..cb5a1f92eb4a77970d8c586a2fe41870cd40dcd5 --- /dev/null +++ b/docs/.vuepress/public/img/home/areaHardware.svg @@ -0,0 +1,66 @@ + + + 编组 2备份 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/areaPai.png b/docs/.vuepress/public/img/home/areaPai.png new file mode 100644 index 0000000000000000000000000000000000000000..6f60bd7a9d6926a82119a34eb3f99c8d535ca07b Binary files /dev/null and b/docs/.vuepress/public/img/home/areaPai.png differ diff --git a/docs/.vuepress/public/img/home/areaVirtual.svg b/docs/.vuepress/public/img/home/areaVirtual.svg new file mode 100644 index 0000000000000000000000000000000000000000..78639b2633538d0d8b3534b725f1c5ce24737e6b --- /dev/null +++ b/docs/.vuepress/public/img/home/areaVirtual.svg @@ -0,0 +1,53 @@ + + + 编组 2备份 2 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/arrow.svg b/docs/.vuepress/public/img/home/arrow.svg new file mode 100644 index 0000000000000000000000000000000000000000..56c9a462d0d37aab24a7a268e1b5a27d60d10a57 --- /dev/null +++ b/docs/.vuepress/public/img/home/arrow.svg @@ -0,0 +1,12 @@ + + + Outlined/UI/button_arrow_down + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/arrowUp.svg b/docs/.vuepress/public/img/home/arrowUp.svg new file mode 100644 index 0000000000000000000000000000000000000000..bdddebb17ce0d59681adf1258d888f61059bff2a --- /dev/null +++ b/docs/.vuepress/public/img/home/arrowUp.svg @@ -0,0 +1,9 @@ + + + Style + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/bannerSummer.png b/docs/.vuepress/public/img/home/bannerSummer.png new file mode 100644 index 0000000000000000000000000000000000000000..56f8a0bd122b66da7558b0cdf77cfe2c7ff2b966 Binary files /dev/null and b/docs/.vuepress/public/img/home/bannerSummer.png differ diff --git a/docs/.vuepress/public/img/home/blogImg.png b/docs/.vuepress/public/img/home/blogImg.png new file mode 100644 index 0000000000000000000000000000000000000000..489f8ab6f8a9ad556a696b152d6d8a07858d7567 Binary files /dev/null and b/docs/.vuepress/public/img/home/blogImg.png differ diff --git a/docs/.vuepress/public/img/home/cetc.png b/docs/.vuepress/public/img/home/cetc.png new file mode 100644 index 0000000000000000000000000000000000000000..5718b33196fc418204c0f00082add49a0baaceed Binary files /dev/null and b/docs/.vuepress/public/img/home/cetc.png differ diff --git a/docs/.vuepress/public/img/home/developer/caihaomin.png b/docs/.vuepress/public/img/home/developer/caihaomin.png new file mode 100644 index 0000000000000000000000000000000000000000..f2610a9583dfbf297181273073874fdf394dd24f Binary files /dev/null and b/docs/.vuepress/public/img/home/developer/caihaomin.png differ diff --git a/docs/.vuepress/public/img/home/developer/dongjian.png b/docs/.vuepress/public/img/home/developer/dongjian.png new file mode 100644 index 0000000000000000000000000000000000000000..e7d9e52494fd7aac6ab7d5999602180cfc8cddf6 Binary files /dev/null and b/docs/.vuepress/public/img/home/developer/dongjian.png differ diff --git a/docs/.vuepress/public/img/home/developer/dukaitian.png b/docs/.vuepress/public/img/home/developer/dukaitian.png new file mode 100644 index 0000000000000000000000000000000000000000..fa1b5fe37d8c3a01d6a433d6ab3df18ff0ba5782 Binary files /dev/null and b/docs/.vuepress/public/img/home/developer/dukaitian.png differ diff --git a/docs/.vuepress/public/img/home/developer/hexiaowen.png b/docs/.vuepress/public/img/home/developer/hexiaowen.png new file mode 100644 index 0000000000000000000000000000000000000000..ffe7ebf26ef83a9ac6e01ccb6de41923e3181b81 Binary files /dev/null and b/docs/.vuepress/public/img/home/developer/hexiaowen.png differ diff --git a/docs/.vuepress/public/img/home/developer/hufen.png b/docs/.vuepress/public/img/home/developer/hufen.png new file mode 100644 index 0000000000000000000000000000000000000000..1f7b9b9e1bc18699414f069587dc8c390794a0d2 Binary files /dev/null and b/docs/.vuepress/public/img/home/developer/hufen.png differ diff --git a/docs/.vuepress/public/img/home/developer/lifeng.png b/docs/.vuepress/public/img/home/developer/lifeng.png new file mode 100644 index 0000000000000000000000000000000000000000..bb895bf17cae9d9c2827f4c39ce9d8f2f903b3b0 Binary files /dev/null and b/docs/.vuepress/public/img/home/developer/lifeng.png differ diff --git a/docs/.vuepress/public/img/home/developer/liuzhiqiang.png b/docs/.vuepress/public/img/home/developer/liuzhiqiang.png new file mode 100644 index 0000000000000000000000000000000000000000..f0e7a9c76320f2c4bc595cdc97fd7a51e3459331 Binary files /dev/null and b/docs/.vuepress/public/img/home/developer/liuzhiqiang.png differ diff --git a/docs/.vuepress/public/img/home/developer/wubo.png b/docs/.vuepress/public/img/home/developer/wubo.png new file mode 100644 index 0000000000000000000000000000000000000000..3486f3a971c838038bc04b3ddd6efe10fcdec7ec Binary files /dev/null and b/docs/.vuepress/public/img/home/developer/wubo.png differ diff --git a/docs/.vuepress/public/img/home/developer/xiexiuqi.png b/docs/.vuepress/public/img/home/developer/xiexiuqi.png new file mode 100644 index 0000000000000000000000000000000000000000..ddb861e07f8ead9856e2c7d6b7d9dea7003a1b54 Binary files /dev/null and b/docs/.vuepress/public/img/home/developer/xiexiuqi.png differ diff --git a/docs/.vuepress/public/img/home/developer/xiezhipeng.png b/docs/.vuepress/public/img/home/developer/xiezhipeng.png new file mode 100644 index 0000000000000000000000000000000000000000..345d74af088868749204598e966d8308d7c34412 Binary files /dev/null and b/docs/.vuepress/public/img/home/developer/xiezhipeng.png differ diff --git a/docs/.vuepress/public/img/home/developer/xiongwei.png b/docs/.vuepress/public/img/home/developer/xiongwei.png new file mode 100644 index 0000000000000000000000000000000000000000..df0b390ed900102155ccc2bb31a2525d40573372 Binary files /dev/null and b/docs/.vuepress/public/img/home/developer/xiongwei.png differ diff --git a/docs/.vuepress/public/img/home/developer/zhanghailiang.png b/docs/.vuepress/public/img/home/developer/zhanghailiang.png new file mode 100644 index 0000000000000000000000000000000000000000..cc9153f61ca01f296caf784ce14a5cd97aaed07e Binary files /dev/null and b/docs/.vuepress/public/img/home/developer/zhanghailiang.png differ diff --git a/docs/.vuepress/public/img/home/developer/zhengxian.png b/docs/.vuepress/public/img/home/developer/zhengxian.png new file mode 100644 index 0000000000000000000000000000000000000000..41122093d6bcd4e184d902decf113a84eb7e751d Binary files /dev/null and b/docs/.vuepress/public/img/home/developer/zhengxian.png differ diff --git a/docs/.vuepress/public/img/home/developer/zhuchunyi.png b/docs/.vuepress/public/img/home/developer/zhuchunyi.png new file mode 100644 index 0000000000000000000000000000000000000000..be8db69600087470df45d0770ade1b6f268074f4 Binary files /dev/null and b/docs/.vuepress/public/img/home/developer/zhuchunyi.png differ diff --git a/docs/.vuepress/public/img/home/developer/zhujianwei.png b/docs/.vuepress/public/img/home/developer/zhujianwei.png new file mode 100644 index 0000000000000000000000000000000000000000..76252096602db5144c1a2af6f24b8084938d82c0 Binary files /dev/null and b/docs/.vuepress/public/img/home/developer/zhujianwei.png differ diff --git a/docs/.vuepress/public/img/home/developer/zhuyanpeng.png b/docs/.vuepress/public/img/home/developer/zhuyanpeng.png new file mode 100644 index 0000000000000000000000000000000000000000..29e4f863548995bffef70e49ad00830194bc74a7 Binary files /dev/null and b/docs/.vuepress/public/img/home/developer/zhuyanpeng.png differ diff --git a/docs/.vuepress/public/img/home/email.png b/docs/.vuepress/public/img/home/email.png new file mode 100644 index 0000000000000000000000000000000000000000..952ad2383f1e8617c5069d290b18fbb90a915a2f Binary files /dev/null and b/docs/.vuepress/public/img/home/email.png differ diff --git a/docs/.vuepress/public/img/home/eventDate.svg b/docs/.vuepress/public/img/home/eventDate.svg new file mode 100644 index 0000000000000000000000000000000000000000..c4afbf3da17ce03a838066e03507963d1b209c74 --- /dev/null +++ b/docs/.vuepress/public/img/home/eventDate.svg @@ -0,0 +1,9 @@ + + + 形状结合 + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/eventImg.png b/docs/.vuepress/public/img/home/eventImg.png new file mode 100644 index 0000000000000000000000000000000000000000..99da38de48d1f4605590c706975040b7dcc1d74d Binary files /dev/null and b/docs/.vuepress/public/img/home/eventImg.png differ diff --git a/docs/.vuepress/public/img/home/homeActive.gif b/docs/.vuepress/public/img/home/homeActive.gif new file mode 100644 index 0000000000000000000000000000000000000000..c668ff307c380e09dad3508b092bcae1deb4400f Binary files /dev/null and b/docs/.vuepress/public/img/home/homeActive.gif differ diff --git a/docs/.vuepress/public/img/home/hopeEdge.png b/docs/.vuepress/public/img/home/hopeEdge.png new file mode 100644 index 0000000000000000000000000000000000000000..3b84a646e7f7c24a16a9ff62d74d5eef8acc1ad7 Binary files /dev/null and b/docs/.vuepress/public/img/home/hopeEdge.png differ diff --git a/docs/.vuepress/public/img/home/icon-mute.svg b/docs/.vuepress/public/img/home/icon-mute.svg new file mode 100644 index 0000000000000000000000000000000000000000..28fef0592e9baedaf338a223d189e7d960c7b45d --- /dev/null +++ b/docs/.vuepress/public/img/home/icon-mute.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/icon-pause.svg b/docs/.vuepress/public/img/home/icon-pause.svg new file mode 100644 index 0000000000000000000000000000000000000000..a808afed2c61ff850f224e2641992f871b48a882 --- /dev/null +++ b/docs/.vuepress/public/img/home/icon-pause.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/icon-play.svg b/docs/.vuepress/public/img/home/icon-play.svg new file mode 100644 index 0000000000000000000000000000000000000000..281e51314d8aec2c9388e0d4ac152495abdb997c --- /dev/null +++ b/docs/.vuepress/public/img/home/icon-play.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/icon-voice.svg b/docs/.vuepress/public/img/home/icon-voice.svg new file mode 100644 index 0000000000000000000000000000000000000000..e3054ed03767eeadc92c1be08b3ff0b7bb0df9c3 --- /dev/null +++ b/docs/.vuepress/public/img/home/icon-voice.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/iscas.png b/docs/.vuepress/public/img/home/iscas.png new file mode 100644 index 0000000000000000000000000000000000000000..613a2758572573041f3b549e4c88877f9ddbdde0 Binary files /dev/null and b/docs/.vuepress/public/img/home/iscas.png differ diff --git a/docs/.vuepress/public/img/home/kunpeng.png b/docs/.vuepress/public/img/home/kunpeng.png new file mode 100644 index 0000000000000000000000000000000000000000..d7672d12bec4db5b2c6143109b843eb74bfdbbb3 Binary files /dev/null and b/docs/.vuepress/public/img/home/kunpeng.png differ diff --git a/docs/.vuepress/public/img/home/medal.svg b/docs/.vuepress/public/img/home/medal.svg new file mode 100644 index 0000000000000000000000000000000000000000..3ebd4bf64f104e2fa3296f486fa527bc5b087749 --- /dev/null +++ b/docs/.vuepress/public/img/home/medal.svg @@ -0,0 +1,26 @@ + + + 编组 + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/mulan.png b/docs/.vuepress/public/img/home/mulan.png new file mode 100644 index 0000000000000000000000000000000000000000..7cefee5ce27ec24bbf7b3b056f7e4cd353df28d8 Binary files /dev/null and b/docs/.vuepress/public/img/home/mulan.png differ diff --git a/docs/.vuepress/public/img/home/newsImg.png b/docs/.vuepress/public/img/home/newsImg.png new file mode 100644 index 0000000000000000000000000000000000000000..17efec21a55605cdb1533c86f5f57ee7f33ada9d Binary files /dev/null and b/docs/.vuepress/public/img/home/newsImg.png differ diff --git a/docs/.vuepress/public/img/home/pengcheng.png b/docs/.vuepress/public/img/home/pengcheng.png new file mode 100644 index 0000000000000000000000000000000000000000..32a48876528760f599c87aed49cf21a9166ce821 Binary files /dev/null and b/docs/.vuepress/public/img/home/pengcheng.png differ diff --git a/docs/.vuepress/public/img/home/planeLeft.svg b/docs/.vuepress/public/img/home/planeLeft.svg new file mode 100644 index 0000000000000000000000000000000000000000..2608f34122cecbf7c2fbcb63ddab651bd038edf4 --- /dev/null +++ b/docs/.vuepress/public/img/home/planeLeft.svg @@ -0,0 +1,37 @@ + + + 编组 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/planeMiddle.svg b/docs/.vuepress/public/img/home/planeMiddle.svg new file mode 100644 index 0000000000000000000000000000000000000000..cf0f0560f7319387e505529c754974f601597b50 --- /dev/null +++ b/docs/.vuepress/public/img/home/planeMiddle.svg @@ -0,0 +1,44 @@ + + + 编组 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/planeRight.svg b/docs/.vuepress/public/img/home/planeRight.svg new file mode 100644 index 0000000000000000000000000000000000000000..3f75cc7649a4ff90a944055ed6ae079525c55e47 --- /dev/null +++ b/docs/.vuepress/public/img/home/planeRight.svg @@ -0,0 +1,37 @@ + + + 编组 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/play-btn.gif b/docs/.vuepress/public/img/home/play-btn.gif new file mode 100644 index 0000000000000000000000000000000000000000..55f7bb03b6286d9971b23f8623b0a243ce2f0c7f Binary files /dev/null and b/docs/.vuepress/public/img/home/play-btn.gif differ diff --git a/docs/.vuepress/public/img/home/prev-detail.svg b/docs/.vuepress/public/img/home/prev-detail.svg new file mode 100644 index 0000000000000000000000000000000000000000..ec88be4c8e3c92f9de01f58a5437d3d35c0c3bc3 --- /dev/null +++ b/docs/.vuepress/public/img/home/prev-detail.svg @@ -0,0 +1,9 @@ + + + Style + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/prev.svg b/docs/.vuepress/public/img/home/prev.svg new file mode 100644 index 0000000000000000000000000000000000000000..95ec059b11d49f761fcda142c4a1348fc17d3399 --- /dev/null +++ b/docs/.vuepress/public/img/home/prev.svg @@ -0,0 +1,19 @@ + + + Shape + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/qiling.png b/docs/.vuepress/public/img/home/qiling.png new file mode 100644 index 0000000000000000000000000000000000000000..ff955aa86806f88c01e82df38de790a7fb85edac Binary files /dev/null and b/docs/.vuepress/public/img/home/qiling.png differ diff --git a/docs/.vuepress/public/img/home/rodeLeft.svg b/docs/.vuepress/public/img/home/rodeLeft.svg new file mode 100644 index 0000000000000000000000000000000000000000..21c189a14833bd15ab0a49519ae3fe3f8490faa3 --- /dev/null +++ b/docs/.vuepress/public/img/home/rodeLeft.svg @@ -0,0 +1,9 @@ + + + 路径 4 + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/rodeMiddle.svg b/docs/.vuepress/public/img/home/rodeMiddle.svg new file mode 100644 index 0000000000000000000000000000000000000000..303b612a102976dfca72e564a13f9e4305bdba16 --- /dev/null +++ b/docs/.vuepress/public/img/home/rodeMiddle.svg @@ -0,0 +1,9 @@ + + + 路径 8 + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/rodeRight.svg b/docs/.vuepress/public/img/home/rodeRight.svg new file mode 100644 index 0000000000000000000000000000000000000000..4acb81fceda33b866b0465dc1a1d2e4be3b69534 --- /dev/null +++ b/docs/.vuepress/public/img/home/rodeRight.svg @@ -0,0 +1,9 @@ + + + 路径 9 + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/sourceApply.gif b/docs/.vuepress/public/img/home/sourceApply.gif new file mode 100644 index 0000000000000000000000000000000000000000..ad13f7d4c415f8300ea2b4176207db0533f73a9a Binary files /dev/null and b/docs/.vuepress/public/img/home/sourceApply.gif differ diff --git a/docs/.vuepress/public/img/home/sourceMail.gif b/docs/.vuepress/public/img/home/sourceMail.gif new file mode 100644 index 0000000000000000000000000000000000000000..cf17e742422a3850e194e95a014fad91353f4dca Binary files /dev/null and b/docs/.vuepress/public/img/home/sourceMail.gif differ diff --git a/docs/.vuepress/public/img/home/step-move-1.gif b/docs/.vuepress/public/img/home/step-move-1.gif new file mode 100644 index 0000000000000000000000000000000000000000..618b1a961281c7abf0ceeb775e66b2411ee004bf Binary files /dev/null and b/docs/.vuepress/public/img/home/step-move-1.gif differ diff --git a/docs/.vuepress/public/img/home/step-move-2.gif b/docs/.vuepress/public/img/home/step-move-2.gif new file mode 100644 index 0000000000000000000000000000000000000000..49316a39b1bf20b57613edb3234374a23882aeaf Binary files /dev/null and b/docs/.vuepress/public/img/home/step-move-2.gif differ diff --git a/docs/.vuepress/public/img/home/step-move-3.gif b/docs/.vuepress/public/img/home/step-move-3.gif new file mode 100644 index 0000000000000000000000000000000000000000..7dce8fe0e6884454846977f6ce004b940281bbc2 Binary files /dev/null and b/docs/.vuepress/public/img/home/step-move-3.gif differ diff --git a/docs/.vuepress/public/img/home/step-move-4.gif b/docs/.vuepress/public/img/home/step-move-4.gif new file mode 100644 index 0000000000000000000000000000000000000000..20bb85a0dafb9859ff3b05ac31c22cacbae5a960 Binary files /dev/null and b/docs/.vuepress/public/img/home/step-move-4.gif differ diff --git a/docs/.vuepress/public/img/home/step.png b/docs/.vuepress/public/img/home/step.png new file mode 100644 index 0000000000000000000000000000000000000000..ef2d201cf5e1868ce597582e92e4086841f2be71 Binary files /dev/null and b/docs/.vuepress/public/img/home/step.png differ diff --git a/docs/.vuepress/public/img/home/step1.png b/docs/.vuepress/public/img/home/step1.png new file mode 100644 index 0000000000000000000000000000000000000000..13121a69c60d8803d65299829376320b3f3feedb Binary files /dev/null and b/docs/.vuepress/public/img/home/step1.png differ diff --git a/docs/.vuepress/public/img/home/step2.png b/docs/.vuepress/public/img/home/step2.png new file mode 100644 index 0000000000000000000000000000000000000000..20a4311513887556464402ace16231138cda77ce Binary files /dev/null and b/docs/.vuepress/public/img/home/step2.png differ diff --git a/docs/.vuepress/public/img/home/step3.png b/docs/.vuepress/public/img/home/step3.png new file mode 100644 index 0000000000000000000000000000000000000000..2270b1f3e426a6dd44d1d26bff3510fc40cb37cb Binary files /dev/null and b/docs/.vuepress/public/img/home/step3.png differ diff --git a/docs/.vuepress/public/img/home/step4.png b/docs/.vuepress/public/img/home/step4.png new file mode 100644 index 0000000000000000000000000000000000000000..14875f7f576b42bbe4754168af146b9abc4fd90a Binary files /dev/null and b/docs/.vuepress/public/img/home/step4.png differ diff --git a/docs/.vuepress/public/img/home/tongxin.png b/docs/.vuepress/public/img/home/tongxin.png new file mode 100644 index 0000000000000000000000000000000000000000..45b3b528538ce6c19698b5a6b4cbcfe16808cb4d Binary files /dev/null and b/docs/.vuepress/public/img/home/tongxin.png differ diff --git a/docs/.vuepress/public/img/home/turbo.png b/docs/.vuepress/public/img/home/turbo.png new file mode 100644 index 0000000000000000000000000000000000000000..369b6e9033156c4cad99172c9f479e6d61ed669d Binary files /dev/null and b/docs/.vuepress/public/img/home/turbo.png differ diff --git a/docs/.vuepress/public/img/home/userEmail.svg b/docs/.vuepress/public/img/home/userEmail.svg new file mode 100644 index 0000000000000000000000000000000000000000..43b8b8c59998937c48afb31623f2cb806dd91bb3 --- /dev/null +++ b/docs/.vuepress/public/img/home/userEmail.svg @@ -0,0 +1,9 @@ + + + Style + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/userName.svg b/docs/.vuepress/public/img/home/userName.svg new file mode 100644 index 0000000000000000000000000000000000000000..c3a52713c8c93a38d5ea5cb71bd395f1e5e8f8c5 --- /dev/null +++ b/docs/.vuepress/public/img/home/userName.svg @@ -0,0 +1,9 @@ + + + Style + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/home/webBanner0.png b/docs/.vuepress/public/img/home/webBanner0.png new file mode 100644 index 0000000000000000000000000000000000000000..017ae6775f9ff655bef9278916da3ec470d47edc Binary files /dev/null and b/docs/.vuepress/public/img/home/webBanner0.png differ diff --git a/docs/.vuepress/public/img/home/webBanner1.png b/docs/.vuepress/public/img/home/webBanner1.png new file mode 100644 index 0000000000000000000000000000000000000000..84428ad2ee8c2f903b7bfaf2c1b1cf2bc962ec3c Binary files /dev/null and b/docs/.vuepress/public/img/home/webBanner1.png differ diff --git a/docs/.vuepress/public/img/home/webBanner2.png b/docs/.vuepress/public/img/home/webBanner2.png new file mode 100644 index 0000000000000000000000000000000000000000..017ae6775f9ff655bef9278916da3ec470d47edc Binary files /dev/null and b/docs/.vuepress/public/img/home/webBanner2.png differ diff --git a/docs/.vuepress/public/img/home/webBannerSummer.png b/docs/.vuepress/public/img/home/webBannerSummer.png new file mode 100644 index 0000000000000000000000000000000000000000..f7e475540f2fbe8fc151db33e2dcf43fc8a19b77 Binary files /dev/null and b/docs/.vuepress/public/img/home/webBannerSummer.png differ diff --git a/docs/.vuepress/public/img/home/webBannerVideo.png b/docs/.vuepress/public/img/home/webBannerVideo.png new file mode 100644 index 0000000000000000000000000000000000000000..5383107b1b1851a8c5a0892cb46be25120beb39f Binary files /dev/null and b/docs/.vuepress/public/img/home/webBannerVideo.png differ diff --git a/docs/.vuepress/public/img/news/20190708/1.png b/docs/.vuepress/public/img/news/20190708/1.png new file mode 100644 index 0000000000000000000000000000000000000000..79bf4a90140230d72e86069da0877018c1e6ef93 Binary files /dev/null and b/docs/.vuepress/public/img/news/20190708/1.png differ diff --git a/docs/.vuepress/public/img/news/20190829ai/20190829_ai_summit_01.png b/docs/.vuepress/public/img/news/20190829ai/20190829_ai_summit_01.png new file mode 100644 index 0000000000000000000000000000000000000000..7cc0abfa89c6f8fd6b0f77e20d994c01d06c308d Binary files /dev/null and b/docs/.vuepress/public/img/news/20190829ai/20190829_ai_summit_01.png differ diff --git a/docs/.vuepress/public/img/news/20190829ai/20190829_ai_summit_02.png b/docs/.vuepress/public/img/news/20190829ai/20190829_ai_summit_02.png new file mode 100644 index 0000000000000000000000000000000000000000..ac988c047436f92e6427a1727c1486e2ceeb24ff Binary files /dev/null and b/docs/.vuepress/public/img/news/20190829ai/20190829_ai_summit_02.png differ diff --git a/docs/.vuepress/public/img/news/20190829ai/20190829_ai_summit_03.png b/docs/.vuepress/public/img/news/20190829ai/20190829_ai_summit_03.png new file mode 100644 index 0000000000000000000000000000000000000000..e579b6f23bbf41efdf39a73a329625416cea1d98 Binary files /dev/null and b/docs/.vuepress/public/img/news/20190829ai/20190829_ai_summit_03.png differ diff --git a/docs/.vuepress/public/img/news/20190829ai/20190829_ai_summit_04.png b/docs/.vuepress/public/img/news/20190829ai/20190829_ai_summit_04.png new file mode 100644 index 0000000000000000000000000000000000000000..e579b6f23bbf41efdf39a73a329625416cea1d98 Binary files /dev/null and b/docs/.vuepress/public/img/news/20190829ai/20190829_ai_summit_04.png differ diff --git a/docs/.vuepress/public/img/news/20190829ai/20190829_ai_summit_05.png b/docs/.vuepress/public/img/news/20190829ai/20190829_ai_summit_05.png new file mode 100644 index 0000000000000000000000000000000000000000..d6b8b9701a816a7b12a72eeba3de2f482accdac3 Binary files /dev/null and b/docs/.vuepress/public/img/news/20190829ai/20190829_ai_summit_05.png differ diff --git a/docs/.vuepress/public/img/news/20190918hc/20190918_hc_01.png b/docs/.vuepress/public/img/news/20190918hc/20190918_hc_01.png new file mode 100644 index 0000000000000000000000000000000000000000..4db6cb52de304783edb0953f27c66be2c6411afe Binary files /dev/null and b/docs/.vuepress/public/img/news/20190918hc/20190918_hc_01.png differ diff --git a/docs/.vuepress/public/img/news/20190918hc/20190918_hc_02.png b/docs/.vuepress/public/img/news/20190918hc/20190918_hc_02.png new file mode 100644 index 0000000000000000000000000000000000000000..af22d392706a287ed0692f222de29068a8175204 Binary files /dev/null and b/docs/.vuepress/public/img/news/20190918hc/20190918_hc_02.png differ diff --git a/docs/.vuepress/public/img/news/20190918hc/20190918_hc_03.png b/docs/.vuepress/public/img/news/20190918hc/20190918_hc_03.png new file mode 100644 index 0000000000000000000000000000000000000000..30fb4a1b6626df3de6c1c2b71fc52be01c61fb20 Binary files /dev/null and b/docs/.vuepress/public/img/news/20190918hc/20190918_hc_03.png differ diff --git a/docs/.vuepress/public/img/news/20190918hc/20190918_hc_04.png b/docs/.vuepress/public/img/news/20190918hc/20190918_hc_04.png new file mode 100644 index 0000000000000000000000000000000000000000..9aa5dce3a4822ff497424a29b9f5824dc8afb9bf Binary files /dev/null and b/docs/.vuepress/public/img/news/20190918hc/20190918_hc_04.png differ diff --git a/docs/.vuepress/public/img/news/20191001/history.jpeg b/docs/.vuepress/public/img/news/20191001/history.jpeg new file mode 100644 index 0000000000000000000000000000000000000000..f169a72befdf8787b47c32e29f7b160628bed016 Binary files /dev/null and b/docs/.vuepress/public/img/news/20191001/history.jpeg differ diff --git a/docs/.vuepress/public/img/news/mwc/mwc_20190626_shanghai.png b/docs/.vuepress/public/img/news/mwc/mwc_20190626_shanghai.png new file mode 100644 index 0000000000000000000000000000000000000000..449028629c1e4eaf151babe6b0b0793674bce13f Binary files /dev/null and b/docs/.vuepress/public/img/news/mwc/mwc_20190626_shanghai.png differ diff --git a/docs/.vuepress/public/img/news/mwc/mwc_20190626_shanghai_2.png b/docs/.vuepress/public/img/news/mwc/mwc_20190626_shanghai_2.png new file mode 100644 index 0000000000000000000000000000000000000000..5901777e842fcd39d08dae57331ed76690a75e72 Binary files /dev/null and b/docs/.vuepress/public/img/news/mwc/mwc_20190626_shanghai_2.png differ diff --git a/docs/.vuepress/public/img/news/mwc/mwc_20190626_shanghai_banner.png b/docs/.vuepress/public/img/news/mwc/mwc_20190626_shanghai_banner.png new file mode 100644 index 0000000000000000000000000000000000000000..bcf7de6360a9db59a3afc1ee2b0036368ccec8f7 Binary files /dev/null and b/docs/.vuepress/public/img/news/mwc/mwc_20190626_shanghai_banner.png differ diff --git a/docs/.vuepress/public/img/news/news-banner.png b/docs/.vuepress/public/img/news/news-banner.png new file mode 100644 index 0000000000000000000000000000000000000000..87f634eb7e6f80cbfdd119d980b78635909d65f0 Binary files /dev/null and b/docs/.vuepress/public/img/news/news-banner.png differ diff --git a/docs/.vuepress/public/img/news/summit20190723/summit_20190723_beijing.png b/docs/.vuepress/public/img/news/summit20190723/summit_20190723_beijing.png new file mode 100644 index 0000000000000000000000000000000000000000..e5ed43ed41b5202166248293bcbeb5d4385061ee Binary files /dev/null and b/docs/.vuepress/public/img/news/summit20190723/summit_20190723_beijing.png differ diff --git a/docs/.vuepress/public/img/news/summit20190723/summit_20190723_beijing_01.png b/docs/.vuepress/public/img/news/summit20190723/summit_20190723_beijing_01.png new file mode 100644 index 0000000000000000000000000000000000000000..b68a7bc19037c20abf1c2158e3c6a3d6598ef95c Binary files /dev/null and b/docs/.vuepress/public/img/news/summit20190723/summit_20190723_beijing_01.png differ diff --git a/docs/.vuepress/public/img/news/summit20190723/summit_20190723_beijing_02.png b/docs/.vuepress/public/img/news/summit20190723/summit_20190723_beijing_02.png new file mode 100644 index 0000000000000000000000000000000000000000..fd4a16b77b71703b90c68f956e7b6a3116b8a7a5 Binary files /dev/null and b/docs/.vuepress/public/img/news/summit20190723/summit_20190723_beijing_02.png differ diff --git a/docs/.vuepress/public/img/news/summit20190723/summit_20190723_beijing_03.png b/docs/.vuepress/public/img/news/summit20190723/summit_20190723_beijing_03.png new file mode 100644 index 0000000000000000000000000000000000000000..65d0388fa421ebb7b42097510594407cf2655c98 Binary files /dev/null and b/docs/.vuepress/public/img/news/summit20190723/summit_20190723_beijing_03.png differ diff --git a/docs/.vuepress/public/img/news/summit20190723/summit_20190723_beijing_banner.png b/docs/.vuepress/public/img/news/summit20190723/summit_20190723_beijing_banner.png new file mode 100644 index 0000000000000000000000000000000000000000..50a16244555bbcdb2c277293dd273cf3e1981d21 Binary files /dev/null and b/docs/.vuepress/public/img/news/summit20190723/summit_20190723_beijing_banner.png differ diff --git a/docs/.vuepress/public/img/other/brand/Style.png b/docs/.vuepress/public/img/other/brand/Style.png new file mode 100644 index 0000000000000000000000000000000000000000..d24c88882af2800b75e5b16f577238afce3c3c77 Binary files /dev/null and b/docs/.vuepress/public/img/other/brand/Style.png differ diff --git a/docs/.vuepress/public/img/other/brand/brand-banner.png b/docs/.vuepress/public/img/other/brand/brand-banner.png new file mode 100644 index 0000000000000000000000000000000000000000..aa1913645c5e4329cd9bf9be3ac70d4aca3ac97e Binary files /dev/null and b/docs/.vuepress/public/img/other/brand/brand-banner.png differ diff --git a/docs/.vuepress/public/img/other/brand/horizontal-center.pdf b/docs/.vuepress/public/img/other/brand/horizontal-center.pdf new file mode 100644 index 0000000000000000000000000000000000000000..7ef326b8c9c00a32e50fe22d988b0868af3626e4 Binary files /dev/null and b/docs/.vuepress/public/img/other/brand/horizontal-center.pdf differ diff --git a/docs/.vuepress/public/img/other/brand/horizontal-center.png b/docs/.vuepress/public/img/other/brand/horizontal-center.png new file mode 100644 index 0000000000000000000000000000000000000000..c4148e13e03ee3f42de88b90f98dc29d3e688c1e Binary files /dev/null and b/docs/.vuepress/public/img/other/brand/horizontal-center.png differ diff --git a/docs/.vuepress/public/img/other/brand/horizontal-center.svg b/docs/.vuepress/public/img/other/brand/horizontal-center.svg new file mode 100644 index 0000000000000000000000000000000000000000..c106e748685999800b505a022289813aebbc8f53 --- /dev/null +++ b/docs/.vuepress/public/img/other/brand/horizontal-center.svg @@ -0,0 +1,11 @@ + + + 5@3x + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/other/brand/horizontal-left.pdf b/docs/.vuepress/public/img/other/brand/horizontal-left.pdf new file mode 100644 index 0000000000000000000000000000000000000000..525bc4091f32158e23d94a07a68dc16667ecd9d7 Binary files /dev/null and b/docs/.vuepress/public/img/other/brand/horizontal-left.pdf differ diff --git a/docs/.vuepress/public/img/other/brand/horizontal-left.png b/docs/.vuepress/public/img/other/brand/horizontal-left.png new file mode 100644 index 0000000000000000000000000000000000000000..2f6b37b4ab92666ee1a73673db7fceb22956fa7b Binary files /dev/null and b/docs/.vuepress/public/img/other/brand/horizontal-left.png differ diff --git a/docs/.vuepress/public/img/other/brand/horizontal-left.svg b/docs/.vuepress/public/img/other/brand/horizontal-left.svg new file mode 100644 index 0000000000000000000000000000000000000000..54944f68ed90d99856644637f986042bfed72a3a --- /dev/null +++ b/docs/.vuepress/public/img/other/brand/horizontal-left.svg @@ -0,0 +1,11 @@ + + + 3@3x + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/other/brand/horizontal-right.pdf b/docs/.vuepress/public/img/other/brand/horizontal-right.pdf new file mode 100644 index 0000000000000000000000000000000000000000..aa6bb747021456106dbf575a4ef202f4dcac0832 Binary files /dev/null and b/docs/.vuepress/public/img/other/brand/horizontal-right.pdf differ diff --git a/docs/.vuepress/public/img/other/brand/horizontal-right.png b/docs/.vuepress/public/img/other/brand/horizontal-right.png new file mode 100644 index 0000000000000000000000000000000000000000..1af29f61ae526cce18ef5364b242c83d25e78d44 Binary files /dev/null and b/docs/.vuepress/public/img/other/brand/horizontal-right.png differ diff --git a/docs/.vuepress/public/img/other/brand/horizontal-right.svg b/docs/.vuepress/public/img/other/brand/horizontal-right.svg new file mode 100644 index 0000000000000000000000000000000000000000..464234f407a418651b0c2a6d6f8faf25432e0b98 --- /dev/null +++ b/docs/.vuepress/public/img/other/brand/horizontal-right.svg @@ -0,0 +1,11 @@ + + + 4@3x + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/other/brand/vertical-center.pdf b/docs/.vuepress/public/img/other/brand/vertical-center.pdf new file mode 100644 index 0000000000000000000000000000000000000000..b5a529fa2825de56cde0b668314bb24f89fbb0d9 Binary files /dev/null and b/docs/.vuepress/public/img/other/brand/vertical-center.pdf differ diff --git a/docs/.vuepress/public/img/other/brand/vertical-center.png b/docs/.vuepress/public/img/other/brand/vertical-center.png new file mode 100644 index 0000000000000000000000000000000000000000..efbd84139866f6ac30aa51c3afd11cc9e727bdc5 Binary files /dev/null and b/docs/.vuepress/public/img/other/brand/vertical-center.png differ diff --git a/docs/.vuepress/public/img/other/brand/vertical-center.svg b/docs/.vuepress/public/img/other/brand/vertical-center.svg new file mode 100644 index 0000000000000000000000000000000000000000..2ff364ca4ab8fdc552819df9d41b1758dd567911 --- /dev/null +++ b/docs/.vuepress/public/img/other/brand/vertical-center.svg @@ -0,0 +1,11 @@ + + + 2@3x + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/other/brand/vertical-left.pdf b/docs/.vuepress/public/img/other/brand/vertical-left.pdf new file mode 100644 index 0000000000000000000000000000000000000000..4281bd30fad8e73499b386e897bb4bb9e2b31396 Binary files /dev/null and b/docs/.vuepress/public/img/other/brand/vertical-left.pdf differ diff --git a/docs/.vuepress/public/img/other/brand/vertical-left.png b/docs/.vuepress/public/img/other/brand/vertical-left.png new file mode 100644 index 0000000000000000000000000000000000000000..b64a2275bef24acb10bdcb661f74daba2c5d1674 Binary files /dev/null and b/docs/.vuepress/public/img/other/brand/vertical-left.png differ diff --git a/docs/.vuepress/public/img/other/brand/vertical-left.svg b/docs/.vuepress/public/img/other/brand/vertical-left.svg new file mode 100644 index 0000000000000000000000000000000000000000..f106321adf201ee404d1d1bc41bca0e782badccd --- /dev/null +++ b/docs/.vuepress/public/img/other/brand/vertical-left.svg @@ -0,0 +1,11 @@ + + + 1@3x + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/other/brand/vertical-right.pdf b/docs/.vuepress/public/img/other/brand/vertical-right.pdf new file mode 100644 index 0000000000000000000000000000000000000000..266d3c9d1912757fc72f9e24002c32ca035c6b1a Binary files /dev/null and b/docs/.vuepress/public/img/other/brand/vertical-right.pdf differ diff --git a/docs/.vuepress/public/img/other/brand/vertical-right.png b/docs/.vuepress/public/img/other/brand/vertical-right.png new file mode 100644 index 0000000000000000000000000000000000000000..4098032924aa829f373d826bc66cb1df41bd6957 Binary files /dev/null and b/docs/.vuepress/public/img/other/brand/vertical-right.png differ diff --git a/docs/.vuepress/public/img/other/brand/vertical-right.svg b/docs/.vuepress/public/img/other/brand/vertical-right.svg new file mode 100644 index 0000000000000000000000000000000000000000..db80f7bf67fb882b8b63714a9ef0a6502bedba8b --- /dev/null +++ b/docs/.vuepress/public/img/other/brand/vertical-right.svg @@ -0,0 +1,11 @@ + + + 6@3x + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/other/search/search-icon.svg b/docs/.vuepress/public/img/other/search/search-icon.svg new file mode 100644 index 0000000000000000000000000000000000000000..b762ccf871c7bd9057eda589bf4c037c43637503 --- /dev/null +++ b/docs/.vuepress/public/img/other/search/search-icon.svg @@ -0,0 +1,9 @@ + + + Style + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/public/img/other/search/search.png b/docs/.vuepress/public/img/other/search/search.png new file mode 100644 index 0000000000000000000000000000000000000000..ce0f4572102639db08e4a171a2514fb3ae052771 Binary files /dev/null and b/docs/.vuepress/public/img/other/search/search.png differ diff --git a/docs/.vuepress/public/lang.png b/docs/.vuepress/public/lang.png new file mode 100644 index 0000000000000000000000000000000000000000..4d968b6ba46e2d3fabf1d0806c5f32ef96e30c4d Binary files /dev/null and b/docs/.vuepress/public/lang.png differ diff --git a/docs/.vuepress/public/logo-mobile.png b/docs/.vuepress/public/logo-mobile.png new file mode 100644 index 0000000000000000000000000000000000000000..fff504caecf69767431c3d3ccb0dfa8ab0160d57 Binary files /dev/null and b/docs/.vuepress/public/logo-mobile.png differ diff --git a/docs/.vuepress/public/menu-mobile.png b/docs/.vuepress/public/menu-mobile.png new file mode 100644 index 0000000000000000000000000000000000000000..aaa0e59a59327cde15d49037b5a01f1bee3c1f3b Binary files /dev/null and b/docs/.vuepress/public/menu-mobile.png differ diff --git a/docs/.vuepress/public/openeuler.png b/docs/.vuepress/public/openeuler.png new file mode 100644 index 0000000000000000000000000000000000000000..db468c0f8d33c64cbc58b4c3d6266447ff6ff192 Binary files /dev/null and b/docs/.vuepress/public/openeuler.png differ diff --git a/docs/.vuepress/public/qrcode.png b/docs/.vuepress/public/qrcode.png new file mode 100644 index 0000000000000000000000000000000000000000..ea524b978506fb77676aee485d468f2af3abd51a Binary files /dev/null and b/docs/.vuepress/public/qrcode.png differ diff --git a/docs/.vuepress/public/search.png b/docs/.vuepress/public/search.png new file mode 100644 index 0000000000000000000000000000000000000000..11ee04ea7e4fa8872035b5b1451e3f8e06954f9b Binary files /dev/null and b/docs/.vuepress/public/search.png differ diff --git a/docs/.vuepress/public/style/base.css b/docs/.vuepress/public/style/base.css new file mode 100644 index 0000000000000000000000000000000000000000..bdd6103c52ba9a7c52012bc6834d385135248272 --- /dev/null +++ b/docs/.vuepress/public/style/base.css @@ -0,0 +1,264 @@ +/* CSS Document */ +/*css reset*/ +html { + box-sizing: border-box; +} + +*, +*:before, +*:after { + box-sizing: inherit; +} + +body, +div, +dl, +dt, +dd, +ul, +ol, +li, +h1, +h2, +h3, +h4, +h5, +h6, +pre, +form, +fieldset, +input, +textarea, +p, +blockquote, +th, +td { + margin: 0; + padding: 0; +} + +table { + border-collapse: collapse; + border-spacing: 0; +} + +fieldest, +img { + border: 0; +} + +address, +caption, +cite, +code, +dfn, +em, +strong, +th, +var { + font-style: normal; + font-weight: normal; +} + +ol, +ul { + list-style: none; +} + +caption, +th { + text-align: left; +} + +h1, +h2, +h3, +h4, +h5, +h6 { + font-size: 100%; + font-weight: normal; +} + +p:before, +q:after { + content: ""; +} + +abbr, +acronym { + border: 0; +} + +/*定位*/ +.tl { + text-align: left; +} + +.tc { + text-align: center; +} + +.tr { + text-align: right; +} + +.bc { + margin-left: auto; + margin-right: auto; +} + +.fl { + float: left; +} + +.fr { + float: right; +} + +.cb { + clear: both; +} + +.cl { + clear: left; +} + +.cr { + clear: right; +} + +.clearfix:after { + content: "."; + display: block; + height: 0; + clear: both; + visibility: hidden; +} + +.clearfix { + display: inline-block; +} + +.fade-in { + opacity: 0; + transition: 0.8s all ease-out; + transform: scale(0.8); +} +.font-hjw { + font-family: FZLTHJW; +} +.font-chjw { + font-family: FZLTCHJW; +} +.font-hbjw { + font-family: FZLTHBJW; +} +.font-xihjw { + font-family: FZLTXIHJW; +} +.font-zhjw { + font-family: FZLTZHJW; +} +.font-hwbold { + font-family: HuaweiSans-Bold; +} +.font-hwlight { + font-family: HuaweiSans-Light; +} +.font-hwmedium { + font-family: HuaweiSans-Medium; +} +.font-hw { + font-family: HuaweiSans; +} +.font-hwthin { + font-family: HuaweiSans-Thin; +} +.font-rblack { + font-family: Roboto-Black; +} +.font-rblackItalic { + font-family: Roboto-BlackItalic; +} +.font-rbold { + font-family: Roboto-Bold; +} +.font-rboldCondensed { + font-family: Roboto-BoldCondensed; +} +.font-rboldCondensedItalic { + font-family: Roboto-BoldCondensedItalic; +} +.font-rboldItalic { + font-family: Roboto-BoldItalic; +} +.font-rcondensed { + font-family: Roboto-Condensed; +} +.font-rcondensedItalic { + font-family: Roboto-CondensedItalic; +} +.font-ritalic { + font-family: Roboto-Italic; +} +.font-rlight { + font-family: Roboto-Light; +} +.font-rlightItalic { + font-family: Roboto-LightItalic; +} +.font-rmedium { + font-family: Roboto-Medium; +} +.font-rmediumItalic { + font-family: Roboto-MediumItalic; +} +.font-rregular { + font-family: Roboto-Regular; +} +.font-rthin { + font-family: Roboto-Thin; +} +.font-rthinItalic { + font-family: Roboto-ThinItalic; +} + +@font-face { + font-family: 'icomoon'; + src: url('../fonts/icomoon.eot?4mtq8t'); + src: url('../fonts/icomoon.eot?4mtq8t#iefix') format('embedded-opentype'), + url('../fonts/icomoon.ttf?4mtq8t') format('truetype'), + url('../fonts/icomoon.woff?4mtq8t') format('woff'), + url('../fonts/icomoon.svg?4mtq8t#icomoon') format('svg'); + font-weight: normal; + font-style: normal; + font-display: block; + } + + [class^="icon-"], [class*=" icon-"] { + /* use !important to prevent issues with browser extensions that change fonts */ + font-family: 'icomoon' !important; + speak: never; + font-style: normal; + font-weight: normal; + font-variant: normal; + text-transform: none; + line-height: 1; + + /* Better Font Rendering =========== */ + -webkit-font-smoothing: antialiased; + -moz-osx-font-smoothing: grayscale; + } + + .icon-menu:before { + content: "\e900"; + } + + .icon-arrow:before { + content: "\e901"; + } + + .icon-search:before { + content: "\e902"; + } \ No newline at end of file diff --git a/docs/.vuepress/public/style/font-cn.css b/docs/.vuepress/public/style/font-cn.css new file mode 100644 index 0000000000000000000000000000000000000000..8537bf5d9561360d990a5cd9198fdc2a051e705f --- /dev/null +++ b/docs/.vuepress/public/style/font-cn.css @@ -0,0 +1,25 @@ +@font-face { + font-family: "FZLTHJW"; + src: url(../fonts/FZLTHJW.TTF); +} +@font-face { + font-family: "FZLTCHJW"; + src: url(../fonts/FZLTCHJW.TTF); +} + +@font-face { + font-family: "FZLTHBJW"; + src: url(../fonts/FZLTHBJW.TTF); +} +@font-face { + font-family: "FZLTXHJW"; + src: url(../fonts/FZLTXHJW.TTF); +} +@font-face { + font-family: "FZLTXIHJW"; + src: url(../fonts/FZLTXIHJW.TTF); +} +@font-face { + font-family: "FZLTZHJW"; + src: url(../fonts/FZLTZHJW.TTF); +} \ No newline at end of file diff --git a/docs/.vuepress/public/style/font-en.css b/docs/.vuepress/public/style/font-en.css new file mode 100644 index 0000000000000000000000000000000000000000..2951a6a9657b0aed6a7ea8b4f67b21c8a3aff358 --- /dev/null +++ b/docs/.vuepress/public/style/font-en.css @@ -0,0 +1,85 @@ +@font-face { + font-family: "HuaweiSans-Bold"; + src: url(../fonts/HuaweiSans-Bold.ttf); +} +@font-face { + font-family: "HuaweiSans-Light"; + src: url(../fonts/HuaweiSans-Light.ttf); +} +@font-face { + font-family: "HuaweiSans-Medium"; + src: url(../fonts/HuaweiSans-Medium.ttf); +} +@font-face { + font-family: "HuaweiSans"; + src: url(../fonts/HuaweiSans-Regular.ttf); +} +@font-face { + font-family: "HuaweiSans-Thin"; + src: url(../fonts/HuaweiSans-Thin.ttf); +} + +@font-face { + font-family: "Roboto-Black"; + src: url(../fonts/Roboto-Black.ttf); +} +@font-face { + font-family: "Roboto-BlackItalic"; + src: url(../fonts/Roboto-BlackItalic.ttf); +} +@font-face { + font-family: "Roboto-Bold"; + src: url(../fonts/Roboto-Bold.ttf); +} +@font-face { + font-family: "Roboto-BoldCondensed"; + src: url(../fonts/Roboto-BoldCondensed.ttf); +} +@font-face { + font-family: "Roboto-BoldCondensedItalic"; + src: url(../fonts/Roboto-BoldCondensedItalic.ttf); +} +@font-face { + font-family: "Roboto-BoldItalic"; + src: url(../fonts/Roboto-BoldItalic.ttf); +} +@font-face { + font-family: "Roboto-Condensed"; + src: url(../fonts/Roboto-Condensed.ttf); +} +@font-face { + font-family: "Roboto-CondensedItalic"; + src: url(../fonts/Roboto-CondensedItalic.ttf); +} +@font-face { + font-family: "Roboto-Italic"; + src: url(../fonts/Roboto-Italic.ttf); +} +@font-face { + font-family: "Roboto-Light"; + src: url(../fonts/Roboto-Light.ttf); +} +@font-face { + font-family: "Roboto-LightItalic"; + src: url(../fonts/Roboto-LightItalic.ttf); +} +@font-face { + font-family: "Roboto-Medium"; + src: url(../fonts/Roboto-Medium.ttf); +} +@font-face { + font-family: "Roboto-MediumItalic"; + src: url(../fonts/Roboto-MediumItalic.ttf); +} +@font-face { + font-family: "Roboto-Regular"; + src: url(../fonts/Roboto-Regular.ttf); +} +@font-face { + font-family: "Roboto-Thin"; + src: url(../fonts/Roboto-Thin.ttf); +} +@font-face { + font-family: "Roboto-ThinItalic"; + src: url(../fonts/Roboto-ThinItalic.ttf); +} \ No newline at end of file diff --git a/docs/.vuepress/public/style/markdown.less b/docs/.vuepress/public/style/markdown.less new file mode 100644 index 0000000000000000000000000000000000000000..be0b84158b2132a37afdaf061a5d1fe4d7218cf9 --- /dev/null +++ b/docs/.vuepress/public/style/markdown.less @@ -0,0 +1,133 @@ +.lang-en { + .markdown { + h2, h3, h4, h5{ + font-family: HuaweiSans-Medium; + } + p, ul li { + font-family: Roboto-Regular; + } + } +} +.markdown { + width: 1120px; + margin: 0 auto; + margin-bottom: 200px; + @media (max-width: 1000px) { + width: 100%; + padding: 0 30px; + margin-bottom: 80px; + margin-top: 40px; + } + div[class*="language-"]{ + background:rgba(225,230,238,0.3); + border:1px solid rgba(151,151,151,1); + border-radius: 0; + pre{ + padding: 1em; + margin: .5em 0; + overflow: auto; + code{ + color:rgba(0,0,0,0.5); + } + } + } + h2 { + line-height: 24px; + font-size: 24px; + margin: 40px 0 20px; + font-family: FZLTHJW; + @media (max-width: 1000px) { + font-size: 18px; + line-height: 18px; + font-family: FZLTCHJW; + margin: 30px 0 20px; + } + } + h3 { + line-height: 20px; + font-size: 20px; + margin: 30px 0 20px; + font-family: FZLTHJW; + @media (max-width: 1000px) { + font-size: 16px; + line-height: 16px; + font-family: FZLTCHJW; + margin: 30px 0 20px; + } + } + h4 { + line-height: 18px; + font-size: 18px; + margin: 30px 0 20px; + font-family: FZLTHJW; + @media (max-width: 1000px) { + font-size: 15px; + line-height: 15px; + font-family: FZLTCHJW; + margin: 30px 0 20px; + } + } + h5 { + line-height: 16px; + font-size: 16px; + margin: 30px 0 20px; + font-family: FZLTHJW; + @media (max-width: 1000px) { + font-size: 14px; + line-height: 14px; + font-family: FZLTCHJW; + margin: 30px 0 20px; + } + } + p, ul li, ol li { + font-size: 14px; + color: rgba(0, 0, 0, .5); + line-height: 24px; + font-family: FZLTXIHJW; + letter-spacing: 0.8px; + @media (max-width: 1000px) { + line-height: 30px; + } + a { + color: #002fa7; + text-decoration: none; + cursor: pointer; + } + b{ + color: rgba(0, 0, 0, 1); + } + } + a[href^='#'] { + display: none; + } + table { + width: 100%; + font-size: 14px; + tr { + height: 60px; + color: rgba(0, 0, 0, .5); + @media (max-width: 1000px) { + height: 52px; + } + th { + color: #000; + } + th, td { + padding-left: 30px; + @media (max-width: 1000px) { + padding-left: 10px; + } + } + } + tr:nth-child(odd) { + th, td { + background-color: #f2f2f2; + } + + } + } + ul, ol { + list-style: initial; + padding-left: 30px; + } +} \ No newline at end of file diff --git a/docs/.vuepress/public/style/theme/fonts/element-icons.ttf b/docs/.vuepress/public/style/theme/fonts/element-icons.ttf new file mode 100644 index 0000000000000000000000000000000000000000..91b74de36778b0ff8958d37d07ce70fb3b26f50b Binary files /dev/null and b/docs/.vuepress/public/style/theme/fonts/element-icons.ttf differ diff --git a/docs/.vuepress/public/style/theme/fonts/element-icons.woff b/docs/.vuepress/public/style/theme/fonts/element-icons.woff new file mode 100644 index 0000000000000000000000000000000000000000..02b9a2539e425a7a8c244faba92527602be76212 Binary files /dev/null and b/docs/.vuepress/public/style/theme/fonts/element-icons.woff differ diff --git a/docs/.vuepress/public/style/theme/index.css b/docs/.vuepress/public/style/theme/index.css new file mode 100644 index 0000000000000000000000000000000000000000..6b3ad7d47edf6e18086c82d104e440f861e3afa0 --- /dev/null +++ b/docs/.vuepress/public/style/theme/index.css @@ -0,0 +1 @@ +@charset "UTF-8";.el-pagination--small .arrow.disabled,.el-table .hidden-columns,.el-table td.is-hidden>*,.el-table th.is-hidden>*,.el-table--hidden{visibility:hidden}.el-input__suffix,.el-tree.is-dragging .el-tree-node__content *{pointer-events:none}.el-dropdown .el-dropdown-selfdefine:focus:active,.el-dropdown .el-dropdown-selfdefine:focus:not(.focusing),.el-message__closeBtn:focus,.el-message__content:focus,.el-popover:focus,.el-popover:focus:active,.el-popover__reference:focus:hover,.el-popover__reference:focus:not(.focusing),.el-rate:active,.el-rate:focus,.el-tooltip:focus:hover,.el-tooltip:focus:not(.focusing),.el-upload-list__item.is-success:active,.el-upload-list__item.is-success:not(.focusing):focus{outline-width:0}@font-face{font-family:element-icons;src:url(fonts/element-icons.woff) format("woff"),url(fonts/element-icons.ttf) format("truetype");font-weight:400;font-display:"auto";font-style:normal}[class*=" el-icon-"],[class^=el-icon-]{font-family:element-icons!important;speak:none;font-style:normal;font-weight:400;font-variant:normal;text-transform:none;line-height:1;vertical-align:baseline;display:inline-block;-webkit-font-smoothing:antialiased;-moz-osx-font-smoothing:grayscale}.el-icon-ice-cream-round:before{content:"\e6a0"}.el-icon-ice-cream-square:before{content:"\e6a3"}.el-icon-lollipop:before{content:"\e6a4"}.el-icon-potato-strips:before{content:"\e6a5"}.el-icon-milk-tea:before{content:"\e6a6"}.el-icon-ice-drink:before{content:"\e6a7"}.el-icon-ice-tea:before{content:"\e6a9"}.el-icon-coffee:before{content:"\e6aa"}.el-icon-orange:before{content:"\e6ab"}.el-icon-pear:before{content:"\e6ac"}.el-icon-apple:before{content:"\e6ad"}.el-icon-cherry:before{content:"\e6ae"}.el-icon-watermelon:before{content:"\e6af"}.el-icon-grape:before{content:"\e6b0"}.el-icon-refrigerator:before{content:"\e6b1"}.el-icon-goblet-square-full:before{content:"\e6b2"}.el-icon-goblet-square:before{content:"\e6b3"}.el-icon-goblet-full:before{content:"\e6b4"}.el-icon-goblet:before{content:"\e6b5"}.el-icon-cold-drink:before{content:"\e6b6"}.el-icon-coffee-cup:before{content:"\e6b8"}.el-icon-water-cup:before{content:"\e6b9"}.el-icon-hot-water:before{content:"\e6ba"}.el-icon-ice-cream:before{content:"\e6bb"}.el-icon-dessert:before{content:"\e6bc"}.el-icon-sugar:before{content:"\e6bd"}.el-icon-tableware:before{content:"\e6be"}.el-icon-burger:before{content:"\e6bf"}.el-icon-knife-fork:before{content:"\e6c1"}.el-icon-fork-spoon:before{content:"\e6c2"}.el-icon-chicken:before{content:"\e6c3"}.el-icon-food:before{content:"\e6c4"}.el-icon-dish-1:before{content:"\e6c5"}.el-icon-dish:before{content:"\e6c6"}.el-icon-moon-night:before{content:"\e6ee"}.el-icon-moon:before{content:"\e6f0"}.el-icon-cloudy-and-sunny:before{content:"\e6f1"}.el-icon-partly-cloudy:before{content:"\e6f2"}.el-icon-cloudy:before{content:"\e6f3"}.el-icon-sunny:before{content:"\e6f6"}.el-icon-sunset:before{content:"\e6f7"}.el-icon-sunrise-1:before{content:"\e6f8"}.el-icon-sunrise:before{content:"\e6f9"}.el-icon-heavy-rain:before{content:"\e6fa"}.el-icon-lightning:before{content:"\e6fb"}.el-icon-light-rain:before{content:"\e6fc"}.el-icon-wind-power:before{content:"\e6fd"}.el-icon-baseball:before{content:"\e712"}.el-icon-soccer:before{content:"\e713"}.el-icon-football:before{content:"\e715"}.el-icon-basketball:before{content:"\e716"}.el-icon-ship:before{content:"\e73f"}.el-icon-truck:before{content:"\e740"}.el-icon-bicycle:before{content:"\e741"}.el-icon-mobile-phone:before{content:"\e6d3"}.el-icon-service:before{content:"\e6d4"}.el-icon-key:before{content:"\e6e2"}.el-icon-unlock:before{content:"\e6e4"}.el-icon-lock:before{content:"\e6e5"}.el-icon-watch:before{content:"\e6fe"}.el-icon-watch-1:before{content:"\e6ff"}.el-icon-timer:before{content:"\e702"}.el-icon-alarm-clock:before{content:"\e703"}.el-icon-map-location:before{content:"\e704"}.el-icon-delete-location:before{content:"\e705"}.el-icon-add-location:before{content:"\e706"}.el-icon-location-information:before{content:"\e707"}.el-icon-location-outline:before{content:"\e708"}.el-icon-location:before{content:"\e79e"}.el-icon-place:before{content:"\e709"}.el-icon-discover:before{content:"\e70a"}.el-icon-first-aid-kit:before{content:"\e70b"}.el-icon-trophy-1:before{content:"\e70c"}.el-icon-trophy:before{content:"\e70d"}.el-icon-medal:before{content:"\e70e"}.el-icon-medal-1:before{content:"\e70f"}.el-icon-stopwatch:before{content:"\e710"}.el-icon-mic:before{content:"\e711"}.el-icon-copy-document:before{content:"\e718"}.el-icon-full-screen:before{content:"\e719"}.el-icon-switch-button:before{content:"\e71b"}.el-icon-aim:before{content:"\e71c"}.el-icon-crop:before{content:"\e71d"}.el-icon-odometer:before{content:"\e71e"}.el-icon-time:before{content:"\e71f"}.el-icon-bangzhu:before{content:"\e724"}.el-icon-close-notification:before{content:"\e726"}.el-icon-microphone:before{content:"\e727"}.el-icon-turn-off-microphone:before{content:"\e728"}.el-icon-position:before{content:"\e729"}.el-icon-postcard:before{content:"\e72a"}.el-icon-message:before{content:"\e72b"}.el-icon-chat-line-square:before{content:"\e72d"}.el-icon-chat-dot-square:before{content:"\e72e"}.el-icon-chat-dot-round:before{content:"\e72f"}.el-icon-chat-square:before{content:"\e730"}.el-icon-chat-line-round:before{content:"\e731"}.el-icon-chat-round:before{content:"\e732"}.el-icon-set-up:before{content:"\e733"}.el-icon-turn-off:before{content:"\e734"}.el-icon-open:before{content:"\e735"}.el-icon-connection:before{content:"\e736"}.el-icon-link:before{content:"\e737"}.el-icon-cpu:before{content:"\e738"}.el-icon-thumb:before{content:"\e739"}.el-icon-female:before{content:"\e73a"}.el-icon-male:before{content:"\e73b"}.el-icon-guide:before{content:"\e73c"}.el-icon-news:before{content:"\e73e"}.el-icon-price-tag:before{content:"\e744"}.el-icon-discount:before{content:"\e745"}.el-icon-wallet:before{content:"\e747"}.el-icon-coin:before{content:"\e748"}.el-icon-money:before{content:"\e749"}.el-icon-bank-card:before{content:"\e74a"}.el-icon-box:before{content:"\e74b"}.el-icon-present:before{content:"\e74c"}.el-icon-sell:before{content:"\e6d5"}.el-icon-sold-out:before{content:"\e6d6"}.el-icon-shopping-bag-2:before{content:"\e74d"}.el-icon-shopping-bag-1:before{content:"\e74e"}.el-icon-shopping-cart-2:before{content:"\e74f"}.el-icon-shopping-cart-1:before{content:"\e750"}.el-icon-shopping-cart-full:before{content:"\e751"}.el-icon-smoking:before{content:"\e752"}.el-icon-no-smoking:before{content:"\e753"}.el-icon-house:before{content:"\e754"}.el-icon-table-lamp:before{content:"\e755"}.el-icon-school:before{content:"\e756"}.el-icon-office-building:before{content:"\e757"}.el-icon-toilet-paper:before{content:"\e758"}.el-icon-notebook-2:before{content:"\e759"}.el-icon-notebook-1:before{content:"\e75a"}.el-icon-files:before{content:"\e75b"}.el-icon-collection:before{content:"\e75c"}.el-icon-receiving:before{content:"\e75d"}.el-icon-suitcase-1:before{content:"\e760"}.el-icon-suitcase:before{content:"\e761"}.el-icon-film:before{content:"\e763"}.el-icon-collection-tag:before{content:"\e765"}.el-icon-data-analysis:before{content:"\e766"}.el-icon-pie-chart:before{content:"\e767"}.el-icon-data-board:before{content:"\e768"}.el-icon-data-line:before{content:"\e76d"}.el-icon-reading:before{content:"\e769"}.el-icon-magic-stick:before{content:"\e76a"}.el-icon-coordinate:before{content:"\e76b"}.el-icon-mouse:before{content:"\e76c"}.el-icon-brush:before{content:"\e76e"}.el-icon-headset:before{content:"\e76f"}.el-icon-umbrella:before{content:"\e770"}.el-icon-scissors:before{content:"\e771"}.el-icon-mobile:before{content:"\e773"}.el-icon-attract:before{content:"\e774"}.el-icon-monitor:before{content:"\e775"}.el-icon-search:before{content:"\e778"}.el-icon-takeaway-box:before{content:"\e77a"}.el-icon-paperclip:before{content:"\e77d"}.el-icon-printer:before{content:"\e77e"}.el-icon-document-add:before{content:"\e782"}.el-icon-document:before{content:"\e785"}.el-icon-document-checked:before{content:"\e786"}.el-icon-document-copy:before{content:"\e787"}.el-icon-document-delete:before{content:"\e788"}.el-icon-document-remove:before{content:"\e789"}.el-icon-tickets:before{content:"\e78b"}.el-icon-folder-checked:before{content:"\e77f"}.el-icon-folder-delete:before{content:"\e780"}.el-icon-folder-remove:before{content:"\e781"}.el-icon-folder-add:before{content:"\e783"}.el-icon-folder-opened:before{content:"\e784"}.el-icon-folder:before{content:"\e78a"}.el-icon-edit-outline:before{content:"\e764"}.el-icon-edit:before{content:"\e78c"}.el-icon-date:before{content:"\e78e"}.el-icon-c-scale-to-original:before{content:"\e7c6"}.el-icon-view:before{content:"\e6ce"}.el-icon-loading:before{content:"\e6cf"}.el-icon-rank:before{content:"\e6d1"}.el-icon-sort-down:before{content:"\e7c4"}.el-icon-sort-up:before{content:"\e7c5"}.el-icon-sort:before{content:"\e6d2"}.el-icon-finished:before{content:"\e6cd"}.el-icon-refresh-left:before{content:"\e6c7"}.el-icon-refresh-right:before{content:"\e6c8"}.el-icon-refresh:before{content:"\e6d0"}.el-icon-video-play:before{content:"\e7c0"}.el-icon-video-pause:before{content:"\e7c1"}.el-icon-d-arrow-right:before{content:"\e6dc"}.el-icon-d-arrow-left:before{content:"\e6dd"}.el-icon-arrow-up:before{content:"\e6e1"}.el-icon-arrow-down:before{content:"\e6df"}.el-icon-arrow-right:before{content:"\e6e0"}.el-icon-arrow-left:before{content:"\e6de"}.el-icon-top-right:before{content:"\e6e7"}.el-icon-top-left:before{content:"\e6e8"}.el-icon-top:before{content:"\e6e6"}.el-icon-bottom:before{content:"\e6eb"}.el-icon-right:before{content:"\e6e9"}.el-icon-back:before{content:"\e6ea"}.el-icon-bottom-right:before{content:"\e6ec"}.el-icon-bottom-left:before{content:"\e6ed"}.el-icon-caret-top:before{content:"\e78f"}.el-icon-caret-bottom:before{content:"\e790"}.el-icon-caret-right:before{content:"\e791"}.el-icon-caret-left:before{content:"\e792"}.el-icon-d-caret:before{content:"\e79a"}.el-icon-share:before{content:"\e793"}.el-icon-menu:before{content:"\e798"}.el-icon-s-grid:before{content:"\e7a6"}.el-icon-s-check:before{content:"\e7a7"}.el-icon-s-data:before{content:"\e7a8"}.el-icon-s-opportunity:before{content:"\e7aa"}.el-icon-s-custom:before{content:"\e7ab"}.el-icon-s-claim:before{content:"\e7ad"}.el-icon-s-finance:before{content:"\e7ae"}.el-icon-s-comment:before{content:"\e7af"}.el-icon-s-flag:before{content:"\e7b0"}.el-icon-s-marketing:before{content:"\e7b1"}.el-icon-s-shop:before{content:"\e7b4"}.el-icon-s-open:before{content:"\e7b5"}.el-icon-s-management:before{content:"\e7b6"}.el-icon-s-ticket:before{content:"\e7b7"}.el-icon-s-release:before{content:"\e7b8"}.el-icon-s-home:before{content:"\e7b9"}.el-icon-s-promotion:before{content:"\e7ba"}.el-icon-s-operation:before{content:"\e7bb"}.el-icon-s-unfold:before{content:"\e7bc"}.el-icon-s-fold:before{content:"\e7a9"}.el-icon-s-platform:before{content:"\e7bd"}.el-icon-s-order:before{content:"\e7be"}.el-icon-s-cooperation:before{content:"\e7bf"}.el-icon-bell:before{content:"\e725"}.el-icon-message-solid:before{content:"\e799"}.el-icon-video-camera:before{content:"\e772"}.el-icon-video-camera-solid:before{content:"\e796"}.el-icon-camera:before{content:"\e779"}.el-icon-camera-solid:before{content:"\e79b"}.el-icon-download:before{content:"\e77c"}.el-icon-upload2:before{content:"\e77b"}.el-icon-upload:before{content:"\e7c3"}.el-icon-picture-outline-round:before{content:"\e75f"}.el-icon-picture-outline:before{content:"\e75e"}.el-icon-picture:before{content:"\e79f"}.el-icon-close:before{content:"\e6db"}.el-icon-check:before{content:"\e6da"}.el-icon-plus:before{content:"\e6d9"}.el-icon-minus:before{content:"\e6d8"}.el-icon-help:before{content:"\e73d"}.el-icon-s-help:before{content:"\e7b3"}.el-icon-circle-close:before{content:"\e78d"}.el-icon-circle-check:before{content:"\e720"}.el-icon-circle-plus-outline:before{content:"\e723"}.el-icon-remove-outline:before{content:"\e722"}.el-icon-zoom-out:before{content:"\e776"}.el-icon-zoom-in:before{content:"\e777"}.el-icon-error:before{content:"\e79d"}.el-icon-success:before{content:"\e79c"}.el-icon-circle-plus:before{content:"\e7a0"}.el-icon-remove:before{content:"\e7a2"}.el-icon-info:before{content:"\e7a1"}.el-icon-question:before{content:"\e7a4"}.el-icon-warning-outline:before{content:"\e6c9"}.el-icon-warning:before{content:"\e7a3"}.el-icon-goods:before{content:"\e7c2"}.el-icon-s-goods:before{content:"\e7b2"}.el-icon-star-off:before{content:"\e717"}.el-icon-star-on:before{content:"\e797"}.el-icon-more-outline:before{content:"\e6cc"}.el-icon-more:before{content:"\e794"}.el-icon-phone-outline:before{content:"\e6cb"}.el-icon-phone:before{content:"\e795"}.el-icon-user:before{content:"\e6e3"}.el-icon-user-solid:before{content:"\e7a5"}.el-icon-setting:before{content:"\e6ca"}.el-icon-s-tools:before{content:"\e7ac"}.el-icon-delete:before{content:"\e6d7"}.el-icon-delete-solid:before{content:"\e7c9"}.el-icon-eleme:before{content:"\e7c7"}.el-icon-platform-eleme:before{content:"\e7ca"}.el-icon-loading{-webkit-animation:rotating 2s linear infinite;animation:rotating 2s linear infinite}.el-icon--right{margin-left:5px}.el-icon--left{margin-right:5px}@-webkit-keyframes rotating{0%{-webkit-transform:rotateZ(0);transform:rotateZ(0)}100%{-webkit-transform:rotateZ(360deg);transform:rotateZ(360deg)}}@keyframes rotating{0%{-webkit-transform:rotateZ(0);transform:rotateZ(0)}100%{-webkit-transform:rotateZ(360deg);transform:rotateZ(360deg)}}.el-pagination{white-space:nowrap;padding:2px 5px;color:#303133;font-weight:700}.el-pagination::after,.el-pagination::before{display:table;content:""}.el-pagination::after{clear:both}.el-pagination button,.el-pagination span:not([class*=suffix]){display:inline-block;font-size:13px;min-width:35.5px;height:28px;line-height:28px;vertical-align:top;-webkit-box-sizing:border-box;box-sizing:border-box}.el-pagination .el-input__inner{text-align:center;-moz-appearance:textfield;line-height:normal}.el-pagination .el-input__suffix{right:0;-webkit-transform:scale(.8);transform:scale(.8)}.el-pagination .el-select .el-input{width:100px;margin:0 5px}.el-pagination .el-select .el-input .el-input__inner{padding-right:25px;border-radius:3px}.el-pagination button{border:none;padding:0 6px;background:0 0}.el-pagination button:focus{outline:0}.el-pagination button:hover{color:#002FA7}.el-pagination button:disabled{color:#3F3F3F;background-color:#FFF;cursor:not-allowed}.el-pagination .btn-next,.el-pagination .btn-prev{background:center center no-repeat #FFF;background-size:16px;cursor:pointer;margin:0;color:#303133}.el-pagination .btn-next .el-icon,.el-pagination .btn-prev .el-icon{display:block;font-size:12px;font-weight:700}.el-pagination .btn-prev{padding-right:12px}.el-pagination .btn-next{padding-left:12px}.el-pagination .el-pager li.disabled{color:#3F3F3F;cursor:not-allowed}.el-pager li,.el-pager li.btn-quicknext:hover,.el-pager li.btn-quickprev:hover{cursor:pointer}.el-pagination--small .btn-next,.el-pagination--small .btn-prev,.el-pagination--small .el-pager li,.el-pagination--small .el-pager li.btn-quicknext,.el-pagination--small .el-pager li.btn-quickprev,.el-pagination--small .el-pager li:last-child{border-color:transparent;font-size:12px;line-height:22px;height:22px;min-width:22px}.el-pagination--small .more::before,.el-pagination--small li.more::before{line-height:24px}.el-pagination--small button,.el-pagination--small span:not([class*=suffix]){height:22px;line-height:22px}.el-pagination--small .el-pagination__editor,.el-pagination--small .el-pagination__editor.el-input .el-input__inner{height:22px}.el-pagination__sizes{margin:0 10px 0 0;font-weight:400;color:#606266}.el-pagination__sizes .el-input .el-input__inner{font-size:13px;padding-left:8px}.el-pagination__sizes .el-input .el-input__inner:hover{border-color:#002FA7}.el-pagination__total{margin-right:10px;font-weight:400;color:#606266}.el-pagination__jump{margin-left:24px;font-weight:400;color:#606266}.el-pagination__jump .el-input__inner{padding:0 3px}.el-pagination__rightwrapper{float:right}.el-pagination__editor{line-height:18px;padding:0 2px;height:28px;text-align:center;margin:0 2px;-webkit-box-sizing:border-box;box-sizing:border-box;border-radius:3px}.el-pager,.el-pagination.is-background .btn-next,.el-pagination.is-background .btn-prev{padding:0}.el-pagination__editor.el-input{width:50px}.el-pagination__editor.el-input .el-input__inner{height:28px}.el-pagination__editor .el-input__inner::-webkit-inner-spin-button,.el-pagination__editor .el-input__inner::-webkit-outer-spin-button{-webkit-appearance:none;margin:0}.el-pagination.is-background .btn-next,.el-pagination.is-background .btn-prev,.el-pagination.is-background .el-pager li{margin:0 5px;background-color:#f4f4f5;color:#606266;min-width:30px;border-radius:2px}.el-pagination.is-background .btn-next.disabled,.el-pagination.is-background .btn-next:disabled,.el-pagination.is-background .btn-prev.disabled,.el-pagination.is-background .btn-prev:disabled,.el-pagination.is-background .el-pager li.disabled{color:#3F3F3F}.el-pagination.is-background .el-pager li:not(.disabled):hover{color:#002FA7}.el-pagination.is-background .el-pager li:not(.disabled).active{background-color:#002FA7;color:#FFF}.el-dialog,.el-pager li{background:#FFF;-webkit-box-sizing:border-box}.el-pagination.is-background.el-pagination--small .btn-next,.el-pagination.is-background.el-pagination--small .btn-prev,.el-pagination.is-background.el-pagination--small .el-pager li{margin:0 3px;min-width:22px}.el-pager,.el-pager li{vertical-align:top;margin:0;display:inline-block}.el-pager{-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;list-style:none;font-size:0}.el-date-table,.el-table th{-webkit-user-select:none;-moz-user-select:none}.el-pager .more::before{line-height:30px}.el-pager li{padding:0 4px;font-size:13px;min-width:35.5px;height:28px;line-height:28px;box-sizing:border-box;text-align:center}.el-menu--collapse .el-menu .el-submenu,.el-menu--popup{min-width:200px}.el-pager li.btn-quicknext,.el-pager li.btn-quickprev{line-height:28px;color:#303133}.el-pager li.btn-quicknext.disabled,.el-pager li.btn-quickprev.disabled{color:#3F3F3F}.el-pager li.active+li{border-left:0}.el-pager li:hover{color:#002FA7}.el-pager li.active{color:#002FA7;cursor:default}@-webkit-keyframes v-modal-in{0%{opacity:0}}@-webkit-keyframes v-modal-out{100%{opacity:0}}.el-dialog{position:relative;margin:0 auto 50px;border-radius:2px;-webkit-box-shadow:0 1px 3px rgba(0,0,0,.3);box-shadow:0 1px 3px rgba(0,0,0,.3);box-sizing:border-box;width:50%}.el-dialog.is-fullscreen{width:100%;margin-top:0;margin-bottom:0;height:100%;overflow:auto}.el-dialog__wrapper{position:fixed;top:0;right:0;bottom:0;left:0;overflow:auto;margin:0}.el-dialog__header{padding:20px 20px 10px}.el-dialog__headerbtn{position:absolute;top:20px;right:20px;padding:0;background:0 0;border:none;outline:0;cursor:pointer;font-size:16px}.el-dialog__headerbtn .el-dialog__close{color:#909399}.el-dialog__headerbtn:focus .el-dialog__close,.el-dialog__headerbtn:hover .el-dialog__close{color:#002FA7}.el-dialog__title{line-height:24px;font-size:18px;color:#303133}.el-dialog__body{padding:30px 20px;color:#606266;font-size:14px;word-break:break-all}.el-dialog__footer{padding:10px 20px 20px;text-align:right;-webkit-box-sizing:border-box;box-sizing:border-box}.el-dialog--center{text-align:center}.el-dialog--center .el-dialog__body{text-align:initial;padding:25px 25px 30px}.el-dialog--center .el-dialog__footer{text-align:inherit}.dialog-fade-enter-active{-webkit-animation:dialog-fade-in .3s;animation:dialog-fade-in .3s}.dialog-fade-leave-active{-webkit-animation:dialog-fade-out .3s;animation:dialog-fade-out .3s}@-webkit-keyframes dialog-fade-in{0%{-webkit-transform:translate3d(0,-20px,0);transform:translate3d(0,-20px,0);opacity:0}100%{-webkit-transform:translate3d(0,0,0);transform:translate3d(0,0,0);opacity:1}}@keyframes dialog-fade-in{0%{-webkit-transform:translate3d(0,-20px,0);transform:translate3d(0,-20px,0);opacity:0}100%{-webkit-transform:translate3d(0,0,0);transform:translate3d(0,0,0);opacity:1}}@-webkit-keyframes dialog-fade-out{0%{-webkit-transform:translate3d(0,0,0);transform:translate3d(0,0,0);opacity:1}100%{-webkit-transform:translate3d(0,-20px,0);transform:translate3d(0,-20px,0);opacity:0}}@keyframes dialog-fade-out{0%{-webkit-transform:translate3d(0,0,0);transform:translate3d(0,0,0);opacity:1}100%{-webkit-transform:translate3d(0,-20px,0);transform:translate3d(0,-20px,0);opacity:0}}.el-autocomplete{position:relative;display:inline-block}.el-autocomplete-suggestion{margin:5px 0;-webkit-box-shadow:0 2px 12px 0 rgba(0,0,0,.1);box-shadow:0 2px 12px 0 rgba(0,0,0,.1);border-radius:4px;border:1px solid #E4E7ED;-webkit-box-sizing:border-box;box-sizing:border-box;background-color:#FFF}.el-dropdown-menu,.el-menu--collapse .el-submenu .el-menu{z-index:10;-webkit-box-shadow:0 2px 12px 0 rgba(0,0,0,.1)}.el-autocomplete-suggestion__wrap{max-height:280px;padding:10px 0;-webkit-box-sizing:border-box;box-sizing:border-box}.el-autocomplete-suggestion__list{margin:0;padding:0}.el-autocomplete-suggestion li{padding:0 20px;margin:0;line-height:34px;cursor:pointer;color:#606266;font-size:14px;list-style:none;white-space:nowrap;overflow:hidden;text-overflow:ellipsis}.el-autocomplete-suggestion li.highlighted,.el-autocomplete-suggestion li:hover{background-color:#F5F7FA}.el-autocomplete-suggestion li.divider{margin-top:6px;border-top:1px solid #000}.el-autocomplete-suggestion li.divider:last-child{margin-bottom:-6px}.el-autocomplete-suggestion.is-loading li{text-align:center;height:100px;line-height:100px;font-size:20px;color:#999}.el-autocomplete-suggestion.is-loading li::after{display:inline-block;content:"";height:100%;vertical-align:middle}.el-autocomplete-suggestion.is-loading li:hover{background-color:#FFF}.el-autocomplete-suggestion.is-loading .el-icon-loading{vertical-align:middle}.el-dropdown{display:inline-block;position:relative;color:#606266;font-size:14px}.el-dropdown .el-button-group{display:block}.el-dropdown .el-button-group .el-button{float:none}.el-dropdown .el-dropdown__caret-button{padding-left:5px;padding-right:5px;position:relative;border-left:none}.el-dropdown .el-dropdown__caret-button::before{content:'';position:absolute;display:block;width:1px;top:5px;bottom:5px;left:0;background:rgba(255,255,255,.5)}.el-dropdown .el-dropdown__caret-button.el-button--default::before{background:rgba(187,187,187,.5)}.el-dropdown .el-dropdown__caret-button:hover::before{top:0;bottom:0}.el-dropdown .el-dropdown__caret-button .el-dropdown__icon{padding-left:0}.el-dropdown__icon{font-size:12px;margin:0 3px}.el-dropdown-menu{position:absolute;top:0;left:0;padding:10px 0;margin:5px 0;background-color:#FFF;border:1px solid #EBEEF5;border-radius:4px;box-shadow:0 2px 12px 0 rgba(0,0,0,.1)}.el-dropdown-menu__item{list-style:none;line-height:36px;padding:0 20px;margin:0;font-size:14px;color:#606266;cursor:pointer;outline:0}.el-dropdown-menu__item:focus,.el-dropdown-menu__item:not(.is-disabled):hover{background-color:#e6eaf6;color:#3359b9}.el-dropdown-menu__item i{margin-right:5px}.el-dropdown-menu__item--divided{position:relative;margin-top:6px;border-top:1px solid #EBEEF5}.el-dropdown-menu__item--divided:before{content:'';height:6px;display:block;margin:0 -20px;background-color:#FFF}.el-dropdown-menu__item.is-disabled{cursor:default;color:#bbb;pointer-events:none}.el-dropdown-menu--medium{padding:6px 0}.el-dropdown-menu--medium .el-dropdown-menu__item{line-height:30px;padding:0 17px;font-size:14px}.el-dropdown-menu--medium .el-dropdown-menu__item.el-dropdown-menu__item--divided{margin-top:6px}.el-dropdown-menu--medium .el-dropdown-menu__item.el-dropdown-menu__item--divided:before{height:6px;margin:0 -17px}.el-dropdown-menu--small{padding:6px 0}.el-dropdown-menu--small .el-dropdown-menu__item{line-height:27px;padding:0 15px;font-size:13px}.el-dropdown-menu--small .el-dropdown-menu__item.el-dropdown-menu__item--divided{margin-top:4px}.el-dropdown-menu--small .el-dropdown-menu__item.el-dropdown-menu__item--divided:before{height:4px;margin:0 -15px}.el-dropdown-menu--mini{padding:3px 0}.el-dropdown-menu--mini .el-dropdown-menu__item{line-height:24px;padding:0 10px;font-size:12px}.el-dropdown-menu--mini .el-dropdown-menu__item.el-dropdown-menu__item--divided{margin-top:3px}.el-dropdown-menu--mini .el-dropdown-menu__item.el-dropdown-menu__item--divided:before{height:3px;margin:0 -10px}.el-menu{border-right:solid 1px #e6e6e6;list-style:none;position:relative;margin:0;padding-left:0;background-color:#FFF}.el-menu--horizontal>.el-menu-item:not(.is-disabled):focus,.el-menu--horizontal>.el-menu-item:not(.is-disabled):hover,.el-menu--horizontal>.el-submenu .el-submenu__title:hover{background-color:#fff}.el-menu::after,.el-menu::before{display:table;content:""}.el-menu::after{clear:both}.el-menu.el-menu--horizontal{border-bottom:solid 1px #e6e6e6}.el-menu--horizontal{border-right:none}.el-menu--horizontal>.el-menu-item{float:left;height:60px;line-height:60px;margin:0;border-bottom:2px solid transparent;color:#909399}.el-menu--horizontal>.el-menu-item a,.el-menu--horizontal>.el-menu-item a:hover{color:inherit}.el-menu--horizontal>.el-submenu{float:left}.el-menu--horizontal>.el-submenu:focus,.el-menu--horizontal>.el-submenu:hover{outline:0}.el-menu--horizontal>.el-submenu:focus .el-submenu__title,.el-menu--horizontal>.el-submenu:hover .el-submenu__title{color:#303133}.el-menu--horizontal>.el-submenu.is-active .el-submenu__title{border-bottom:2px solid #002FA7;color:#303133}.el-menu--horizontal>.el-submenu .el-submenu__title{height:60px;line-height:60px;border-bottom:2px solid transparent;color:#909399}.el-menu--horizontal>.el-submenu .el-submenu__icon-arrow{position:static;vertical-align:middle;margin-left:8px;margin-top:-3px}.el-menu--horizontal .el-menu .el-menu-item,.el-menu--horizontal .el-menu .el-submenu__title{background-color:#FFF;float:none;height:36px;line-height:36px;padding:0 10px;color:#909399}.el-menu--horizontal .el-menu .el-menu-item.is-active,.el-menu--horizontal .el-menu .el-submenu.is-active>.el-submenu__title{color:#303133}.el-menu--horizontal .el-menu-item:not(.is-disabled):focus,.el-menu--horizontal .el-menu-item:not(.is-disabled):hover{outline:0;color:#303133}.el-menu--horizontal>.el-menu-item.is-active{border-bottom:2px solid #002FA7;color:#303133}.el-menu--collapse{width:64px}.el-menu--collapse>.el-menu-item [class^=el-icon-],.el-menu--collapse>.el-submenu>.el-submenu__title [class^=el-icon-]{margin:0;vertical-align:middle;width:24px;text-align:center}.el-menu--collapse>.el-menu-item .el-submenu__icon-arrow,.el-menu--collapse>.el-submenu>.el-submenu__title .el-submenu__icon-arrow{display:none}.el-menu--collapse>.el-menu-item span,.el-menu--collapse>.el-submenu>.el-submenu__title span{height:0;width:0;overflow:hidden;visibility:hidden;display:inline-block}.el-menu--collapse>.el-menu-item.is-active i{color:inherit}.el-menu--collapse .el-submenu{position:relative}.el-menu--collapse .el-submenu .el-menu{position:absolute;margin-left:5px;top:0;left:100%;border:1px solid #E4E7ED;border-radius:2px;box-shadow:0 2px 12px 0 rgba(0,0,0,.1)}.el-menu-item,.el-submenu__title{height:56px;line-height:56px;position:relative;-webkit-box-sizing:border-box;white-space:nowrap;list-style:none}.el-menu--collapse .el-submenu.is-opened>.el-submenu__title .el-submenu__icon-arrow{-webkit-transform:none;transform:none}.el-menu--popup{z-index:100;border:none;padding:5px 0;border-radius:2px;-webkit-box-shadow:0 2px 12px 0 rgba(0,0,0,.1);box-shadow:0 2px 12px 0 rgba(0,0,0,.1)}.el-menu--popup-bottom-start{margin-top:5px}.el-menu--popup-right-start{margin-left:5px;margin-right:5px}.el-menu-item{font-size:14px;color:#303133;padding:0 20px;cursor:pointer;-webkit-transition:border-color .3s,background-color .3s,color .3s;transition:border-color .3s,background-color .3s,color .3s;box-sizing:border-box}.el-menu-item *{vertical-align:middle}.el-menu-item i{color:#909399}.el-menu-item:focus,.el-menu-item:hover{outline:0;background-color:#e6eaf6}.el-menu-item.is-disabled{opacity:.25;cursor:not-allowed;background:0 0!important}.el-menu-item [class^=el-icon-]{margin-right:5px;width:24px;text-align:center;font-size:18px;vertical-align:middle}.el-menu-item.is-active{color:#002FA7}.el-menu-item.is-active i{color:inherit}.el-submenu{list-style:none;margin:0;padding-left:0}.el-submenu__title{font-size:14px;color:#303133;padding:0 20px;cursor:pointer;-webkit-transition:border-color .3s,background-color .3s,color .3s;transition:border-color .3s,background-color .3s,color .3s;box-sizing:border-box}.el-submenu__title *{vertical-align:middle}.el-submenu__title i{color:#909399}.el-submenu__title:focus,.el-submenu__title:hover{outline:0;background-color:#e6eaf6}.el-submenu__title.is-disabled{opacity:.25;cursor:not-allowed;background:0 0!important}.el-submenu__title:hover{background-color:#e6eaf6}.el-submenu .el-menu{border:none}.el-submenu .el-menu-item{height:50px;line-height:50px;padding:0 45px;min-width:200px}.el-submenu__icon-arrow{position:absolute;top:50%;right:20px;margin-top:-7px;-webkit-transition:-webkit-transform .3s;transition:-webkit-transform .3s;transition:transform .3s;transition:transform .3s,-webkit-transform .3s;font-size:12px}.el-submenu.is-active .el-submenu__title{border-bottom-color:#002FA7}.el-submenu.is-opened>.el-submenu__title .el-submenu__icon-arrow{-webkit-transform:rotateZ(180deg);transform:rotateZ(180deg)}.el-submenu.is-disabled .el-menu-item,.el-submenu.is-disabled .el-submenu__title{opacity:.25;cursor:not-allowed;background:0 0!important}.el-submenu [class^=el-icon-]{vertical-align:middle;margin-right:5px;width:24px;text-align:center;font-size:18px}.el-menu-item-group>ul{padding:0}.el-menu-item-group__title{padding:7px 0 7px 20px;line-height:normal;font-size:12px;color:#909399}.el-radio-button__inner,.el-radio-group{display:inline-block;line-height:1;vertical-align:middle}.horizontal-collapse-transition .el-submenu__title .el-submenu__icon-arrow{-webkit-transition:.2s;transition:.2s;opacity:0}.el-radio-group{font-size:0}.el-radio-button{position:relative;display:inline-block;outline:0}.el-radio-button__inner{white-space:nowrap;background:#FFF;border:1px solid #BBB;font-weight:500;border-left:0;color:#606266;-webkit-appearance:none;text-align:center;-webkit-box-sizing:border-box;box-sizing:border-box;outline:0;margin:0;position:relative;cursor:pointer;-webkit-transition:all .3s cubic-bezier(.645,.045,.355,1);transition:all .3s cubic-bezier(.645,.045,.355,1);padding:12px 20px;font-size:14px;border-radius:0}.el-radio-button__inner.is-round{padding:12px 20px}.el-radio-button__inner:hover{color:#002FA7}.el-radio-button__inner [class*=el-icon-]{line-height:.9}.el-radio-button__inner [class*=el-icon-]+span{margin-left:5px}.el-radio-button:first-child .el-radio-button__inner{border-left:1px solid #BBB;border-radius:4px 0 0 4px;-webkit-box-shadow:none!important;box-shadow:none!important}.el-radio-button__orig-radio{opacity:0;outline:0;position:absolute;z-index:-1}.el-radio-button__orig-radio:checked+.el-radio-button__inner{color:#FFF;background-color:#002FA7;border-color:#002FA7;-webkit-box-shadow:-1px 0 0 0 #002FA7;box-shadow:-1px 0 0 0 #002FA7}.el-radio-button__orig-radio:disabled+.el-radio-button__inner{color:#3F3F3F;cursor:not-allowed;background-image:none;background-color:#FFF;border-color:#EBEEF5;-webkit-box-shadow:none;box-shadow:none}.el-radio-button__orig-radio:disabled:checked+.el-radio-button__inner{background-color:#F2F6FC}.el-radio-button:last-child .el-radio-button__inner{border-radius:0 4px 4px 0}.el-popover,.el-radio-button:first-child:last-child .el-radio-button__inner{border-radius:4px}.el-radio-button--medium .el-radio-button__inner{padding:10px 20px;font-size:14px;border-radius:0}.el-radio-button--medium .el-radio-button__inner.is-round{padding:10px 20px}.el-radio-button--small .el-radio-button__inner{padding:9px 15px;font-size:12px;border-radius:0}.el-radio-button--small .el-radio-button__inner.is-round{padding:9px 15px}.el-radio-button--mini .el-radio-button__inner{padding:5px 15px;font-size:12px;border-radius:0}.el-radio-button--mini .el-radio-button__inner.is-round{padding:5px 15px}.el-radio-button:focus:not(.is-focus):not(:active):not(.is-disabled){-webkit-box-shadow:0 0 2px 2px #002FA7;box-shadow:0 0 2px 2px #002FA7}.el-switch{display:-webkit-inline-box;display:-ms-inline-flexbox;display:inline-flex;-webkit-box-align:center;-ms-flex-align:center;align-items:center;position:relative;font-size:14px;line-height:20px;height:20px;vertical-align:middle}.el-switch__core,.el-switch__label{display:inline-block;cursor:pointer}.el-switch.is-disabled .el-switch__core,.el-switch.is-disabled .el-switch__label{cursor:not-allowed}.el-switch__label{-webkit-transition:.2s;transition:.2s;height:20px;font-size:14px;font-weight:500;vertical-align:middle;color:#303133}.el-switch__label.is-active{color:#002FA7}.el-switch__label--left{margin-right:10px}.el-switch__label--right{margin-left:10px}.el-switch__label *{line-height:1;font-size:14px;display:inline-block}.el-switch__input{position:absolute;width:0;height:0;opacity:0;margin:0}.el-switch__core{margin:0;position:relative;width:40px;height:20px;border:1px solid #BBB;outline:0;border-radius:10px;-webkit-box-sizing:border-box;box-sizing:border-box;background:#BBB;-webkit-transition:border-color .3s,background-color .3s;transition:border-color .3s,background-color .3s;vertical-align:middle}.el-switch__core:after{content:"";position:absolute;top:1px;left:1px;border-radius:100%;-webkit-transition:all .3s;transition:all .3s;width:16px;height:16px;background-color:#FFF}.el-switch.is-checked .el-switch__core{border-color:#002FA7;background-color:#002FA7}.el-switch.is-checked .el-switch__core::after{left:100%;margin-left:-17px}.el-switch.is-disabled{opacity:.6}.el-switch--wide .el-switch__label.el-switch__label--left span{left:10px}.el-switch--wide .el-switch__label.el-switch__label--right span{right:10px}.el-switch .label-fade-enter,.el-switch .label-fade-leave-active{opacity:0}.el-select-dropdown{position:absolute;z-index:1001;border:1px solid #E4E7ED;border-radius:4px;background-color:#FFF;-webkit-box-shadow:0 2px 12px 0 rgba(0,0,0,.1);box-shadow:0 2px 12px 0 rgba(0,0,0,.1);-webkit-box-sizing:border-box;box-sizing:border-box;margin:5px 0}.el-select-dropdown.is-multiple .el-select-dropdown__item.selected{color:#002FA7;background-color:#FFF}.el-select-dropdown.is-multiple .el-select-dropdown__item.selected.hover{background-color:#F5F7FA}.el-select-dropdown.is-multiple .el-select-dropdown__item.selected::after{position:absolute;right:20px;font-family:element-icons;content:"\e6da";font-size:12px;font-weight:700;-webkit-font-smoothing:antialiased;-moz-osx-font-smoothing:grayscale}.el-select-dropdown .el-scrollbar.is-empty .el-select-dropdown__list{padding:0}.el-select-dropdown__empty{padding:10px 0;margin:0;text-align:center;color:#999;font-size:14px}.el-select-dropdown__wrap{max-height:274px}.el-select-dropdown__list{list-style:none;padding:6px 0;margin:0;-webkit-box-sizing:border-box;box-sizing:border-box}.el-select-dropdown__item{font-size:14px;padding:0 20px;position:relative;white-space:nowrap;overflow:hidden;text-overflow:ellipsis;color:#606266;height:34px;line-height:34px;-webkit-box-sizing:border-box;box-sizing:border-box;cursor:pointer}.el-select-dropdown__item.is-disabled{color:#3F3F3F;cursor:not-allowed}.el-select-dropdown__item.is-disabled:hover{background-color:#FFF}.el-select-dropdown__item.hover,.el-select-dropdown__item:hover{background-color:#F5F7FA}.el-select-dropdown__item.selected{color:#002FA7;font-weight:700}.el-select-group{margin:0;padding:0}.el-select-group__wrap{position:relative;list-style:none;margin:0;padding:0}.el-select-group__wrap:not(:last-of-type){padding-bottom:24px}.el-select-group__wrap:not(:last-of-type)::after{content:'';position:absolute;display:block;left:20px;right:20px;bottom:12px;height:1px;background:#E4E7ED}.el-select-group__title{padding-left:20px;font-size:12px;color:#909399;line-height:30px}.el-select-group .el-select-dropdown__item{padding-left:20px}.el-select{display:inline-block;position:relative}.el-select .el-select__tags>span{display:contents}.el-select:hover .el-input__inner{border-color:#3F3F3F}.el-select .el-input__inner{cursor:pointer;padding-right:35px}.el-select .el-input__inner:focus{border-color:#002FA7}.el-select .el-input .el-select__caret{color:#3F3F3F;font-size:14px;-webkit-transition:-webkit-transform .3s;transition:-webkit-transform .3s;transition:transform .3s;transition:transform .3s,-webkit-transform .3s;-webkit-transform:rotateZ(180deg);transform:rotateZ(180deg);cursor:pointer}.el-select .el-input .el-select__caret.is-reverse{-webkit-transform:rotateZ(0);transform:rotateZ(0)}.el-select .el-input .el-select__caret.is-show-close{font-size:14px;text-align:center;-webkit-transform:rotateZ(180deg);transform:rotateZ(180deg);border-radius:100%;color:#3F3F3F;-webkit-transition:color .2s cubic-bezier(.645,.045,.355,1);transition:color .2s cubic-bezier(.645,.045,.355,1)}.el-select .el-input .el-select__caret.is-show-close:hover{color:#909399}.el-select .el-input.is-disabled .el-input__inner{cursor:not-allowed}.el-select .el-input.is-disabled .el-input__inner:hover{border-color:#E4E7ED}.el-select .el-input.is-focus .el-input__inner{border-color:#002FA7}.el-select>.el-input{display:block}.el-select__input{border:none;outline:0;padding:0;margin-left:15px;color:#666;font-size:14px;-webkit-appearance:none;-moz-appearance:none;appearance:none;height:28px;background-color:transparent}.el-select__input.is-mini{height:14px}.el-select__close{cursor:pointer;position:absolute;top:8px;z-index:1000;right:25px;color:#3F3F3F;line-height:18px;font-size:14px}.el-select__close:hover{color:#909399}.el-select__tags{position:absolute;line-height:normal;white-space:normal;z-index:1;top:50%;-webkit-transform:translateY(-50%);transform:translateY(-50%);display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-align:center;-ms-flex-align:center;align-items:center;-ms-flex-wrap:wrap;flex-wrap:wrap}.el-select .el-tag__close{margin-top:-2px}.el-select .el-tag{-webkit-box-sizing:border-box;box-sizing:border-box;border-color:transparent;margin:2px 0 2px 6px;background-color:#f0f2f5}.el-select .el-tag__close.el-icon-close{background-color:#3F3F3F;right:-7px;top:0;color:#FFF}.el-select .el-tag__close.el-icon-close:hover{background-color:#909399}.el-table,.el-table__expanded-cell{background-color:#FFF}.el-select .el-tag__close.el-icon-close::before{display:block;-webkit-transform:translate(0,.5px);transform:translate(0,.5px)}.el-table{position:relative;overflow:hidden;-webkit-box-sizing:border-box;box-sizing:border-box;-webkit-box-flex:1;-ms-flex:1;flex:1;width:100%;max-width:100%;font-size:14px;color:#606266}.el-table--mini,.el-table--small,.el-table__expand-icon{font-size:12px}.el-table__empty-block{min-height:60px;text-align:center;width:100%;display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-pack:center;-ms-flex-pack:center;justify-content:center;-webkit-box-align:center;-ms-flex-align:center;align-items:center}.el-table__empty-text{line-height:60px;width:50%;color:#909399}.el-table__expand-column .cell{padding:0;text-align:center}.el-table__expand-icon{position:relative;cursor:pointer;color:#666;-webkit-transition:-webkit-transform .2s ease-in-out;transition:-webkit-transform .2s ease-in-out;transition:transform .2s ease-in-out;transition:transform .2s ease-in-out,-webkit-transform .2s ease-in-out;height:20px}.el-table__expand-icon--expanded{-webkit-transform:rotate(90deg);transform:rotate(90deg)}.el-table__expand-icon>.el-icon{position:absolute;left:50%;top:50%;margin-left:-5px;margin-top:-5px}.el-table__expanded-cell[class*=cell]{padding:20px 50px}.el-table__expanded-cell:hover{background-color:transparent!important}.el-table__placeholder{display:inline-block;width:20px}.el-table__append-wrapper{overflow:hidden}.el-table--fit{border-right:0;border-bottom:0}.el-table--fit td.gutter,.el-table--fit th.gutter{border-right-width:1px}.el-table--scrollable-x .el-table__body-wrapper{overflow-x:auto}.el-table--scrollable-y .el-table__body-wrapper{overflow-y:auto}.el-table thead{color:#909399;font-weight:500}.el-table thead.is-group th{background:#F5F7FA}.el-table th,.el-table tr{background-color:#FFF}.el-table td,.el-table th{padding:12px 0;min-width:0;-webkit-box-sizing:border-box;box-sizing:border-box;text-overflow:ellipsis;vertical-align:middle;position:relative;text-align:left}.el-table td.is-center,.el-table th.is-center{text-align:center}.el-table td.is-right,.el-table th.is-right{text-align:right}.el-table td.gutter,.el-table th.gutter{width:15px;border-right-width:0;border-bottom-width:0;padding:0}.el-table--medium td,.el-table--medium th{padding:10px 0}.el-table--small td,.el-table--small th{padding:8px 0}.el-table--mini td,.el-table--mini th{padding:6px 0}.el-table .cell,.el-table--border td:first-child .cell,.el-table--border th:first-child .cell{padding-left:10px}.el-table tr input[type=checkbox]{margin:0}.el-table td,.el-table th.is-leaf{border-bottom:1px solid #EBEEF5}.el-table th.is-sortable{cursor:pointer}.el-table th{overflow:hidden;-ms-user-select:none;user-select:none}.el-table th>.cell{display:inline-block;-webkit-box-sizing:border-box;box-sizing:border-box;position:relative;vertical-align:middle;padding-left:10px;padding-right:10px;width:100%}.el-table th>.cell.highlight{color:#002FA7}.el-table th.required>div::before{display:inline-block;content:"";width:8px;height:8px;border-radius:50%;background:#ff4d51;margin-right:5px;vertical-align:middle}.el-table td div{-webkit-box-sizing:border-box;box-sizing:border-box}.el-table td.gutter{width:0}.el-table .cell{-webkit-box-sizing:border-box;box-sizing:border-box;overflow:hidden;text-overflow:ellipsis;white-space:normal;word-break:break-all;line-height:23px;padding-right:10px}.el-table .cell.el-tooltip{white-space:nowrap;min-width:50px}.el-table--border,.el-table--group{border:1px solid #EBEEF5}.el-table--border::after,.el-table--group::after,.el-table::before{content:'';position:absolute;background-color:#EBEEF5;z-index:1}.el-table--border::after,.el-table--group::after{top:0;right:0;width:1px;height:100%}.el-table::before{left:0;bottom:0;width:100%;height:1px}.el-table--border{border-right:none;border-bottom:none}.el-table--border.el-loading-parent--relative{border-color:transparent}.el-table--border td,.el-table--border th,.el-table__body-wrapper .el-table--border.is-scrolling-left~.el-table__fixed{border-right:1px solid #EBEEF5}.el-table--border th.gutter:last-of-type{border-bottom:1px solid #EBEEF5;border-bottom-width:1px}.el-table--border th,.el-table__fixed-right-patch{border-bottom:1px solid #EBEEF5}.el-table__fixed,.el-table__fixed-right{position:absolute;top:0;left:0;overflow-x:hidden;overflow-y:hidden;-webkit-box-shadow:0 0 10px rgba(0,0,0,.12);box-shadow:0 0 10px rgba(0,0,0,.12)}.el-table__fixed-right::before,.el-table__fixed::before{content:'';position:absolute;left:0;bottom:0;width:100%;height:1px;background-color:#EBEEF5;z-index:4}.el-table__fixed-right-patch{position:absolute;top:-1px;right:0;background-color:#FFF}.el-table__fixed-right{top:0;left:auto;right:0}.el-table__fixed-right .el-table__fixed-body-wrapper,.el-table__fixed-right .el-table__fixed-footer-wrapper,.el-table__fixed-right .el-table__fixed-header-wrapper{left:auto;right:0}.el-table__fixed-header-wrapper{position:absolute;left:0;top:0;z-index:3}.el-table__fixed-footer-wrapper{position:absolute;left:0;bottom:0;z-index:3}.el-table__fixed-footer-wrapper tbody td{border-top:1px solid #EBEEF5;background-color:#F5F7FA;color:#606266}.el-table__fixed-body-wrapper{position:absolute;left:0;top:37px;overflow:hidden;z-index:3}.el-table__body-wrapper,.el-table__footer-wrapper,.el-table__header-wrapper{width:100%}.el-table__footer-wrapper{margin-top:-1px}.el-table__footer-wrapper td{border-top:1px solid #EBEEF5}.el-table__body,.el-table__footer,.el-table__header{table-layout:fixed;border-collapse:separate}.el-table__footer-wrapper,.el-table__header-wrapper{overflow:hidden}.el-table__footer-wrapper tbody td,.el-table__header-wrapper tbody td{background-color:#F5F7FA;color:#606266}.el-table__body-wrapper{overflow:hidden;position:relative}.el-table__body-wrapper.is-scrolling-left~.el-table__fixed,.el-table__body-wrapper.is-scrolling-none~.el-table__fixed,.el-table__body-wrapper.is-scrolling-none~.el-table__fixed-right,.el-table__body-wrapper.is-scrolling-right~.el-table__fixed-right{-webkit-box-shadow:none;box-shadow:none}.el-picker-panel,.el-table-filter{-webkit-box-shadow:0 2px 12px 0 rgba(0,0,0,.1)}.el-table__body-wrapper .el-table--border.is-scrolling-right~.el-table__fixed-right{border-left:1px solid #EBEEF5}.el-table .caret-wrapper{display:-webkit-inline-box;display:-ms-inline-flexbox;display:inline-flex;-webkit-box-orient:vertical;-webkit-box-direction:normal;-ms-flex-direction:column;flex-direction:column;-webkit-box-align:center;-ms-flex-align:center;align-items:center;height:34px;width:24px;vertical-align:middle;cursor:pointer;overflow:initial;position:relative}.el-table .sort-caret{width:0;height:0;border:5px solid transparent;position:absolute;left:7px}.el-table .sort-caret.ascending{border-bottom-color:#3F3F3F;top:5px}.el-table .sort-caret.descending{border-top-color:#3F3F3F;bottom:7px}.el-table .ascending .sort-caret.ascending{border-bottom-color:#002FA7}.el-table .descending .sort-caret.descending{border-top-color:#002FA7}.el-table .hidden-columns{position:absolute;z-index:-1}.el-table--striped .el-table__body tr.el-table__row--striped td{background:#FAFAFA}.el-table--striped .el-table__body tr.el-table__row--striped.current-row td{background-color:#e6eaf6}.el-table__body tr.hover-row.current-row>td,.el-table__body tr.hover-row.el-table__row--striped.current-row>td,.el-table__body tr.hover-row.el-table__row--striped>td,.el-table__body tr.hover-row>td{background-color:#F5F7FA}.el-table__body tr.current-row>td{background-color:#e6eaf6}.el-table__column-resize-proxy{position:absolute;left:200px;top:0;bottom:0;width:0;border-left:1px solid #EBEEF5;z-index:10}.el-table__column-filter-trigger{display:inline-block;line-height:34px;cursor:pointer}.el-table__column-filter-trigger i{color:#909399;font-size:12px;-webkit-transform:scale(.75);transform:scale(.75)}.el-table--enable-row-transition .el-table__body td{-webkit-transition:background-color .25s ease;transition:background-color .25s ease}.el-table--enable-row-hover .el-table__body tr:hover>td{background-color:#F5F7FA}.el-table--fluid-height .el-table__fixed,.el-table--fluid-height .el-table__fixed-right{bottom:0;overflow:hidden}.el-table [class*=el-table__row--level] .el-table__expand-icon{display:inline-block;width:20px;line-height:20px;height:20px;text-align:center;margin-right:3px}.el-table-column--selection .cell{padding-left:14px;padding-right:14px}.el-table-filter{border:1px solid #EBEEF5;border-radius:2px;background-color:#FFF;box-shadow:0 2px 12px 0 rgba(0,0,0,.1);-webkit-box-sizing:border-box;box-sizing:border-box;margin:2px 0}.el-date-table td,.el-date-table td div{height:30px;-webkit-box-sizing:border-box}.el-table-filter__list{padding:5px 0;margin:0;list-style:none;min-width:100px}.el-table-filter__list-item{line-height:36px;padding:0 10px;cursor:pointer;font-size:14px}.el-table-filter__list-item:hover{background-color:#e6eaf6;color:#3359b9}.el-table-filter__list-item.is-active{background-color:#002FA7;color:#FFF}.el-table-filter__content{min-width:100px}.el-table-filter__bottom{border-top:1px solid #EBEEF5;padding:8px}.el-table-filter__bottom button{background:0 0;border:none;color:#606266;cursor:pointer;font-size:13px;padding:0 3px}.el-date-table td.in-range div,.el-date-table td.in-range div:hover,.el-date-table.is-week-mode .el-date-table__row.current div,.el-date-table.is-week-mode .el-date-table__row:hover div{background-color:#F2F6FC}.el-table-filter__bottom button:hover{color:#002FA7}.el-table-filter__bottom button:focus{outline:0}.el-table-filter__bottom button.is-disabled{color:#3F3F3F;cursor:not-allowed}.el-table-filter__wrap{max-height:280px}.el-table-filter__checkbox-group{padding:10px}.el-table-filter__checkbox-group label.el-checkbox{display:block;margin-right:5px;margin-bottom:8px;margin-left:5px}.el-table-filter__checkbox-group .el-checkbox:last-child{margin-bottom:0}.el-date-table{font-size:12px;-ms-user-select:none;user-select:none}.el-date-table.is-week-mode .el-date-table__row:hover td.available:hover{color:#606266}.el-date-table.is-week-mode .el-date-table__row:hover td:first-child div{margin-left:5px;border-top-left-radius:15px;border-bottom-left-radius:15px}.el-date-table.is-week-mode .el-date-table__row:hover td:last-child div{margin-right:5px;border-top-right-radius:15px;border-bottom-right-radius:15px}.el-date-table td{width:32px;padding:4px 0;box-sizing:border-box;text-align:center;cursor:pointer;position:relative}.el-date-table td div{padding:3px 0;box-sizing:border-box}.el-date-table td span{width:24px;height:24px;display:block;margin:0 auto;line-height:24px;position:absolute;left:50%;-webkit-transform:translateX(-50%);transform:translateX(-50%);border-radius:50%}.el-date-table td.next-month,.el-date-table td.prev-month{color:#3F3F3F}.el-date-table td.today{position:relative}.el-date-table td.today span{color:#002FA7;font-weight:700}.el-date-table td.today.end-date span,.el-date-table td.today.start-date span{color:#FFF}.el-date-table td.available:hover{color:#002FA7}.el-date-table td.current:not(.disabled) span{color:#FFF;background-color:#002FA7}.el-date-table td.end-date div,.el-date-table td.start-date div{color:#FFF}.el-date-table td.end-date span,.el-date-table td.start-date span{background-color:#002FA7}.el-date-table td.start-date div{margin-left:5px;border-top-left-radius:15px;border-bottom-left-radius:15px}.el-date-table td.end-date div{margin-right:5px;border-top-right-radius:15px;border-bottom-right-radius:15px}.el-date-table td.disabled div{background-color:#F5F7FA;opacity:1;cursor:not-allowed;color:#3F3F3F}.el-date-table td.selected div{margin-left:5px;margin-right:5px;background-color:#F2F6FC;border-radius:15px}.el-date-table td.selected div:hover{background-color:#F2F6FC}.el-date-table td.selected span{background-color:#002FA7;color:#FFF;border-radius:15px}.el-date-table td.week{font-size:80%;color:#606266}.el-month-table,.el-year-table{font-size:12px;border-collapse:collapse}.el-date-table th{padding:5px;color:#606266;font-weight:400;border-bottom:solid 1px #EBEEF5}.el-month-table{margin:-1px}.el-month-table td{text-align:center;padding:8px 0;cursor:pointer}.el-month-table td div{height:48px;padding:6px 0;-webkit-box-sizing:border-box;box-sizing:border-box}.el-month-table td.today .cell{color:#002FA7;font-weight:700}.el-month-table td.today.end-date .cell,.el-month-table td.today.start-date .cell{color:#FFF}.el-month-table td.disabled .cell{background-color:#F5F7FA;cursor:not-allowed;color:#3F3F3F}.el-month-table td.disabled .cell:hover{color:#3F3F3F}.el-month-table td .cell{width:60px;height:36px;display:block;line-height:36px;color:#606266;margin:0 auto;border-radius:18px}.el-month-table td .cell:hover{color:#002FA7}.el-month-table td.in-range div,.el-month-table td.in-range div:hover{background-color:#F2F6FC}.el-month-table td.end-date div,.el-month-table td.start-date div{color:#FFF}.el-month-table td.end-date .cell,.el-month-table td.start-date .cell{color:#FFF;background-color:#002FA7}.el-month-table td.start-date div{border-top-left-radius:24px;border-bottom-left-radius:24px}.el-month-table td.end-date div{border-top-right-radius:24px;border-bottom-right-radius:24px}.el-month-table td.current:not(.disabled) .cell{color:#002FA7}.el-year-table{margin:-1px}.el-year-table .el-icon{color:#303133}.el-year-table td{text-align:center;padding:20px 3px;cursor:pointer}.el-year-table td.today .cell{color:#002FA7;font-weight:700}.el-year-table td.disabled .cell{background-color:#F5F7FA;cursor:not-allowed;color:#3F3F3F}.el-year-table td.disabled .cell:hover{color:#3F3F3F}.el-year-table td .cell{width:48px;height:32px;display:block;line-height:32px;color:#606266;margin:0 auto}.el-year-table td .cell:hover,.el-year-table td.current:not(.disabled) .cell{color:#002FA7}.el-date-range-picker{width:646px}.el-date-range-picker.has-sidebar{width:756px}.el-date-range-picker table{table-layout:fixed;width:100%}.el-date-range-picker .el-picker-panel__body{min-width:513px}.el-date-range-picker .el-picker-panel__content{margin:0}.el-date-range-picker__header{position:relative;text-align:center;height:28px}.el-date-range-picker__header [class*=arrow-left]{float:left}.el-date-range-picker__header [class*=arrow-right]{float:right}.el-date-range-picker__header div{font-size:16px;font-weight:500;margin-right:50px}.el-date-range-picker__content{float:left;width:50%;-webkit-box-sizing:border-box;box-sizing:border-box;margin:0;padding:16px}.el-date-range-picker__content.is-left{border-right:1px solid #e4e4e4}.el-date-range-picker__content .el-date-range-picker__header div{margin-left:50px;margin-right:50px}.el-date-range-picker__editors-wrap{-webkit-box-sizing:border-box;box-sizing:border-box;display:table-cell}.el-date-range-picker__editors-wrap.is-right{text-align:right}.el-date-range-picker__time-header{position:relative;border-bottom:1px solid #e4e4e4;font-size:12px;padding:8px 5px 5px;display:table;width:100%;-webkit-box-sizing:border-box;box-sizing:border-box}.el-date-range-picker__time-header>.el-icon-arrow-right{font-size:20px;vertical-align:middle;display:table-cell;color:#303133}.el-date-range-picker__time-picker-wrap{position:relative;display:table-cell;padding:0 5px}.el-date-range-picker__time-picker-wrap .el-picker-panel{position:absolute;top:13px;right:0;z-index:1;background:#FFF}.el-date-picker{width:322px}.el-date-picker.has-sidebar.has-time{width:434px}.el-date-picker.has-sidebar{width:438px}.el-date-picker.has-time .el-picker-panel__body-wrapper{position:relative}.el-date-picker .el-picker-panel__content{width:292px}.el-date-picker table{table-layout:fixed;width:100%}.el-date-picker__editor-wrap{position:relative;display:table-cell;padding:0 5px}.el-date-picker__time-header{position:relative;border-bottom:1px solid #e4e4e4;font-size:12px;padding:8px 5px 5px;display:table;width:100%;-webkit-box-sizing:border-box;box-sizing:border-box}.el-date-picker__header{margin:12px;text-align:center}.el-date-picker__header--bordered{margin-bottom:0;padding-bottom:12px;border-bottom:solid 1px #EBEEF5}.el-date-picker__header--bordered+.el-picker-panel__content{margin-top:0}.el-date-picker__header-label{font-size:16px;font-weight:500;padding:0 5px;line-height:22px;text-align:center;cursor:pointer;color:#606266}.el-date-picker__header-label.active,.el-date-picker__header-label:hover{color:#002FA7}.el-date-picker__prev-btn{float:left}.el-date-picker__next-btn{float:right}.el-date-picker__time-wrap{padding:10px;text-align:center}.el-date-picker__time-label{float:left;cursor:pointer;line-height:30px;margin-left:10px}.time-select{margin:5px 0;min-width:0}.time-select .el-picker-panel__content{max-height:200px;margin:0}.time-select-item{padding:8px 10px;font-size:14px;line-height:20px}.time-select-item.selected:not(.disabled){color:#002FA7;font-weight:700}.time-select-item.disabled{color:#E4E7ED;cursor:not-allowed}.time-select-item:hover{background-color:#F5F7FA;font-weight:700;cursor:pointer}.el-date-editor{position:relative;display:inline-block;text-align:left}.el-date-editor.el-input,.el-date-editor.el-input__inner{width:220px}.el-date-editor--monthrange.el-input,.el-date-editor--monthrange.el-input__inner{width:300px}.el-date-editor--daterange.el-input,.el-date-editor--daterange.el-input__inner,.el-date-editor--timerange.el-input,.el-date-editor--timerange.el-input__inner{width:350px}.el-date-editor--datetimerange.el-input,.el-date-editor--datetimerange.el-input__inner{width:400px}.el-date-editor--dates .el-input__inner{text-overflow:ellipsis;white-space:nowrap}.el-date-editor .el-icon-circle-close{cursor:pointer}.el-date-editor .el-range__icon{font-size:14px;margin-left:-5px;color:#3F3F3F;float:left;line-height:32px}.el-date-editor .el-range-input,.el-date-editor .el-range-separator{height:100%;margin:0;text-align:center;display:inline-block;font-size:14px}.el-date-editor .el-range-input{-webkit-appearance:none;-moz-appearance:none;appearance:none;border:none;outline:0;padding:0;width:39%;color:#606266}.el-date-editor .el-range-input::-webkit-input-placeholder{color:#3F3F3F}.el-date-editor .el-range-input::-ms-input-placeholder{color:#3F3F3F}.el-date-editor .el-range-input::placeholder{color:#3F3F3F}.el-date-editor .el-range-separator{padding:0 5px;line-height:32px;width:5%;color:#303133}.el-date-editor .el-range__close-icon{font-size:14px;color:#3F3F3F;width:25px;display:inline-block;float:right;line-height:32px}.el-range-editor.el-input__inner{display:-webkit-inline-box;display:-ms-inline-flexbox;display:inline-flex;-webkit-box-align:center;-ms-flex-align:center;align-items:center;padding:3px 10px}.el-range-editor .el-range-input{line-height:1}.el-range-editor.is-active,.el-range-editor.is-active:hover{border-color:#002FA7}.el-range-editor--medium.el-input__inner{height:36px}.el-range-editor--medium .el-range-separator{line-height:28px;font-size:14px}.el-range-editor--medium .el-range-input{font-size:14px}.el-range-editor--medium .el-range__close-icon,.el-range-editor--medium .el-range__icon{line-height:28px}.el-range-editor--small.el-input__inner{height:32px}.el-range-editor--small .el-range-separator{line-height:24px;font-size:13px}.el-range-editor--small .el-range-input{font-size:13px}.el-range-editor--small .el-range__close-icon,.el-range-editor--small .el-range__icon{line-height:24px}.el-range-editor--mini.el-input__inner{height:28px}.el-range-editor--mini .el-range-separator{line-height:20px;font-size:12px}.el-range-editor--mini .el-range-input{font-size:12px}.el-range-editor--mini .el-range__close-icon,.el-range-editor--mini .el-range__icon{line-height:20px}.el-range-editor.is-disabled{background-color:#F5F7FA;border-color:#E4E7ED;color:#3F3F3F;cursor:not-allowed}.el-range-editor.is-disabled:focus,.el-range-editor.is-disabled:hover{border-color:#E4E7ED}.el-range-editor.is-disabled input{background-color:#F5F7FA;color:#3F3F3F;cursor:not-allowed}.el-range-editor.is-disabled input::-webkit-input-placeholder{color:#3F3F3F}.el-range-editor.is-disabled input::-ms-input-placeholder{color:#3F3F3F}.el-range-editor.is-disabled input::placeholder{color:#3F3F3F}.el-range-editor.is-disabled .el-range-separator{color:#3F3F3F}.el-picker-panel{color:#606266;border:1px solid #E4E7ED;box-shadow:0 2px 12px 0 rgba(0,0,0,.1);background:#FFF;border-radius:4px;line-height:30px;margin:5px 0}.el-popover,.el-time-panel{-webkit-box-shadow:0 2px 12px 0 rgba(0,0,0,.1)}.el-picker-panel__body-wrapper::after,.el-picker-panel__body::after{content:"";display:table;clear:both}.el-picker-panel__content{position:relative;margin:15px}.el-picker-panel__footer{border-top:1px solid #e4e4e4;padding:4px;text-align:right;background-color:#FFF;position:relative;font-size:0}.el-picker-panel__shortcut{display:block;width:100%;border:0;background-color:transparent;line-height:28px;font-size:14px;color:#606266;padding-left:12px;text-align:left;outline:0;cursor:pointer}.el-picker-panel__shortcut:hover{color:#002FA7}.el-picker-panel__shortcut.active{background-color:#e6f1fe;color:#002FA7}.el-picker-panel__btn{border:1px solid #dcdcdc;color:#333;line-height:24px;border-radius:2px;padding:0 20px;cursor:pointer;background-color:transparent;outline:0;font-size:12px}.el-picker-panel__btn[disabled]{color:#ccc;cursor:not-allowed}.el-picker-panel__icon-btn{font-size:12px;color:#303133;border:0;background:0 0;cursor:pointer;outline:0;margin-top:8px}.el-picker-panel__icon-btn:hover{color:#002FA7}.el-picker-panel__icon-btn.is-disabled{color:#bbb}.el-picker-panel__icon-btn.is-disabled:hover{cursor:not-allowed}.el-picker-panel__link-btn{vertical-align:middle}.el-picker-panel [slot=sidebar],.el-picker-panel__sidebar{position:absolute;top:0;bottom:0;width:110px;border-right:1px solid #e4e4e4;-webkit-box-sizing:border-box;box-sizing:border-box;padding-top:6px;background-color:#FFF;overflow:auto}.el-picker-panel [slot=sidebar]+.el-picker-panel__body,.el-picker-panel__sidebar+.el-picker-panel__body{margin-left:110px}.el-time-spinner.has-seconds .el-time-spinner__wrapper{width:33.3%}.el-time-spinner__wrapper{max-height:190px;overflow:auto;display:inline-block;width:50%;vertical-align:top;position:relative}.el-time-spinner__wrapper .el-scrollbar__wrap:not(.el-scrollbar__wrap--hidden-default){padding-bottom:15px}.el-time-spinner__input.el-input .el-input__inner,.el-time-spinner__list{padding:0;text-align:center}.el-time-spinner__wrapper.is-arrow{-webkit-box-sizing:border-box;box-sizing:border-box;text-align:center;overflow:hidden}.el-time-spinner__wrapper.is-arrow .el-time-spinner__list{-webkit-transform:translateY(-32px);transform:translateY(-32px)}.el-time-spinner__wrapper.is-arrow .el-time-spinner__item:hover:not(.disabled):not(.active){background:#FFF;cursor:default}.el-time-spinner__arrow{font-size:12px;color:#909399;position:absolute;left:0;width:100%;z-index:1;text-align:center;height:30px;line-height:30px;cursor:pointer}.el-time-spinner__arrow:hover{color:#002FA7}.el-time-spinner__arrow.el-icon-arrow-up{top:10px}.el-time-spinner__arrow.el-icon-arrow-down{bottom:10px}.el-time-spinner__input.el-input{width:70%}.el-time-spinner__list{margin:0;list-style:none}.el-time-spinner__list::after,.el-time-spinner__list::before{content:'';display:block;width:100%;height:80px}.el-time-spinner__item{height:32px;line-height:32px;font-size:12px;color:#606266}.el-time-spinner__item:hover:not(.disabled):not(.active){background:#F5F7FA;cursor:pointer}.el-time-spinner__item.active:not(.disabled){color:#303133;font-weight:700}.el-time-spinner__item.disabled{color:#3F3F3F;cursor:not-allowed}.el-time-panel{margin:5px 0;border:1px solid #E4E7ED;background-color:#FFF;box-shadow:0 2px 12px 0 rgba(0,0,0,.1);border-radius:2px;position:absolute;width:180px;left:0;z-index:1000;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;-webkit-box-sizing:content-box;box-sizing:content-box}.el-slider__button,.el-slider__button-wrapper{-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none}.el-time-panel__content{font-size:0;position:relative;overflow:hidden}.el-time-panel__content::after,.el-time-panel__content::before{content:"";top:50%;position:absolute;margin-top:-15px;height:32px;z-index:-1;left:0;right:0;-webkit-box-sizing:border-box;box-sizing:border-box;padding-top:6px;text-align:left;border-top:1px solid #E4E7ED;border-bottom:1px solid #E4E7ED}.el-time-panel__content::after{left:50%;margin-left:12%;margin-right:12%}.el-time-panel__content::before{padding-left:50%;margin-right:12%;margin-left:12%}.el-time-panel__content.has-seconds::after{left:calc(100% / 3 * 2)}.el-time-panel__content.has-seconds::before{padding-left:calc(100% / 3)}.el-time-panel__footer{border-top:1px solid #e4e4e4;padding:4px;height:36px;line-height:25px;text-align:right;-webkit-box-sizing:border-box;box-sizing:border-box}.el-time-panel__btn{border:none;line-height:28px;padding:0 5px;margin:0 5px;cursor:pointer;background-color:transparent;outline:0;font-size:12px;color:#303133}.el-time-panel__btn.confirm{font-weight:800;color:#002FA7}.el-time-range-picker{width:354px;overflow:visible}.el-time-range-picker__content{position:relative;text-align:center;padding:10px}.el-time-range-picker__cell{-webkit-box-sizing:border-box;box-sizing:border-box;margin:0;padding:4px 7px 7px;width:50%;display:inline-block}.el-time-range-picker__header{margin-bottom:5px;text-align:center;font-size:14px}.el-time-range-picker__body{border-radius:2px;border:1px solid #E4E7ED}.el-popover{position:absolute;background:#FFF;min-width:150px;border:1px solid #EBEEF5;padding:12px;z-index:2000;color:#606266;line-height:1.4;text-align:justify;font-size:14px;box-shadow:0 2px 12px 0 rgba(0,0,0,.1);word-break:break-all}.el-popover--plain{padding:18px 20px}.el-popover__title{color:#303133;font-size:16px;line-height:1;margin-bottom:12px}.v-modal-enter{-webkit-animation:v-modal-in .2s ease;animation:v-modal-in .2s ease}.v-modal-leave{-webkit-animation:v-modal-out .2s ease forwards;animation:v-modal-out .2s ease forwards}@keyframes v-modal-in{0%{opacity:0}}@keyframes v-modal-out{100%{opacity:0}}.v-modal{position:fixed;left:0;top:0;width:100%;height:100%;opacity:.5;background:#000}.el-popup-parent--hidden{overflow:hidden}.el-message-box{display:inline-block;width:420px;padding-bottom:10px;vertical-align:middle;background-color:#FFF;border-radius:4px;border:1px solid #EBEEF5;font-size:18px;-webkit-box-shadow:0 2px 12px 0 rgba(0,0,0,.1);box-shadow:0 2px 12px 0 rgba(0,0,0,.1);text-align:left;overflow:hidden;-webkit-backface-visibility:hidden;backface-visibility:hidden}.el-message-box__wrapper{position:fixed;top:0;bottom:0;left:0;right:0;text-align:center}.el-message-box__wrapper::after{content:"";display:inline-block;height:100%;width:0;vertical-align:middle}.el-message-box__header{position:relative;padding:15px 15px 10px}.el-message-box__title{padding-left:0;margin-bottom:0;font-size:18px;line-height:1;color:#303133}.el-message-box__headerbtn{position:absolute;top:15px;right:15px;padding:0;border:none;outline:0;background:0 0;font-size:16px;cursor:pointer}.el-form-item.is-error .el-input__inner,.el-form-item.is-error .el-input__inner:focus,.el-form-item.is-error .el-textarea__inner,.el-form-item.is-error .el-textarea__inner:focus,.el-message-box__input input.invalid,.el-message-box__input input.invalid:focus{border-color:#F56C6C}.el-message-box__headerbtn .el-message-box__close{color:#909399}.el-message-box__headerbtn:focus .el-message-box__close,.el-message-box__headerbtn:hover .el-message-box__close{color:#002FA7}.el-message-box__content{padding:10px 15px;color:#606266;font-size:14px}.el-message-box__container{position:relative}.el-message-box__input{padding-top:15px}.el-message-box__status{position:absolute;top:50%;-webkit-transform:translateY(-50%);transform:translateY(-50%);font-size:24px!important}.el-message-box__status::before{padding-left:1px}.el-message-box__status+.el-message-box__message{padding-left:36px;padding-right:12px}.el-message-box__status.el-icon-success{color:#67C23A}.el-message-box__status.el-icon-info{color:#909399}.el-message-box__status.el-icon-warning{color:#E6A23C}.el-message-box__status.el-icon-error{color:#F56C6C}.el-message-box__message{margin:0}.el-message-box__message p{margin:0;line-height:24px}.el-message-box__errormsg{color:#F56C6C;font-size:12px;min-height:18px;margin-top:2px}.el-message-box__btns{padding:5px 15px 0;text-align:right}.el-message-box__btns button:nth-child(2){margin-left:10px}.el-message-box__btns-reverse{-webkit-box-orient:horizontal;-webkit-box-direction:reverse;-ms-flex-direction:row-reverse;flex-direction:row-reverse}.el-message-box--center{padding-bottom:30px}.el-message-box--center .el-message-box__header{padding-top:30px}.el-message-box--center .el-message-box__title{position:relative;display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-align:center;-ms-flex-align:center;align-items:center;-webkit-box-pack:center;-ms-flex-pack:center;justify-content:center}.el-message-box--center .el-message-box__status{position:relative;top:auto;padding-right:5px;text-align:center;-webkit-transform:translateY(-1px);transform:translateY(-1px)}.el-message-box--center .el-message-box__message{margin-left:0}.el-message-box--center .el-message-box__btns,.el-message-box--center .el-message-box__content{text-align:center}.el-message-box--center .el-message-box__content{padding-left:27px;padding-right:27px}.msgbox-fade-enter-active{-webkit-animation:msgbox-fade-in .3s;animation:msgbox-fade-in .3s}.msgbox-fade-leave-active{-webkit-animation:msgbox-fade-out .3s;animation:msgbox-fade-out .3s}@-webkit-keyframes msgbox-fade-in{0%{-webkit-transform:translate3d(0,-20px,0);transform:translate3d(0,-20px,0);opacity:0}100%{-webkit-transform:translate3d(0,0,0);transform:translate3d(0,0,0);opacity:1}}@keyframes msgbox-fade-in{0%{-webkit-transform:translate3d(0,-20px,0);transform:translate3d(0,-20px,0);opacity:0}100%{-webkit-transform:translate3d(0,0,0);transform:translate3d(0,0,0);opacity:1}}@-webkit-keyframes msgbox-fade-out{0%{-webkit-transform:translate3d(0,0,0);transform:translate3d(0,0,0);opacity:1}100%{-webkit-transform:translate3d(0,-20px,0);transform:translate3d(0,-20px,0);opacity:0}}@keyframes msgbox-fade-out{0%{-webkit-transform:translate3d(0,0,0);transform:translate3d(0,0,0);opacity:1}100%{-webkit-transform:translate3d(0,-20px,0);transform:translate3d(0,-20px,0);opacity:0}}.el-breadcrumb{font-size:14px;line-height:1}.el-breadcrumb::after,.el-breadcrumb::before{display:table;content:""}.el-breadcrumb::after{clear:both}.el-breadcrumb__separator{margin:0 9px;font-weight:700;color:#3F3F3F}.el-breadcrumb__separator[class*=icon]{margin:0 6px;font-weight:400}.el-breadcrumb__item{float:left}.el-breadcrumb__inner{color:#606266}.el-breadcrumb__inner a,.el-breadcrumb__inner.is-link{font-weight:700;text-decoration:none;-webkit-transition:color .2s cubic-bezier(.645,.045,.355,1);transition:color .2s cubic-bezier(.645,.045,.355,1);color:#303133}.el-breadcrumb__inner a:hover,.el-breadcrumb__inner.is-link:hover{color:#002FA7;cursor:pointer}.el-breadcrumb__item:last-child .el-breadcrumb__inner,.el-breadcrumb__item:last-child .el-breadcrumb__inner a,.el-breadcrumb__item:last-child .el-breadcrumb__inner a:hover,.el-breadcrumb__item:last-child .el-breadcrumb__inner:hover{font-weight:400;color:#606266;cursor:text}.el-breadcrumb__item:last-child .el-breadcrumb__separator{display:none}.el-form--label-left .el-form-item__label{text-align:left}.el-form--label-top .el-form-item__label{float:none;display:inline-block;text-align:left;padding:0 0 10px}.el-form--inline .el-form-item{display:inline-block;margin-right:10px;vertical-align:top}.el-form--inline .el-form-item__label{float:none;display:inline-block}.el-form--inline .el-form-item__content{display:inline-block;vertical-align:top}.el-form--inline.el-form--label-top .el-form-item__content{display:block}.el-form-item{margin-bottom:22px}.el-form-item::after,.el-form-item::before{display:table;content:""}.el-form-item::after{clear:both}.el-form-item .el-form-item{margin-bottom:0}.el-form-item--mini.el-form-item,.el-form-item--small.el-form-item{margin-bottom:18px}.el-form-item .el-input__validateIcon{display:none}.el-form-item--medium .el-form-item__content,.el-form-item--medium .el-form-item__label{line-height:36px}.el-form-item--small .el-form-item__content,.el-form-item--small .el-form-item__label{line-height:32px}.el-form-item--small .el-form-item__error{padding-top:2px}.el-form-item--mini .el-form-item__content,.el-form-item--mini .el-form-item__label{line-height:28px}.el-form-item--mini .el-form-item__error{padding-top:1px}.el-form-item__label-wrap{float:left}.el-form-item__label-wrap .el-form-item__label{display:inline-block;float:none}.el-form-item__label{text-align:right;vertical-align:middle;float:left;font-size:16px;color:#606266;line-height:40px;padding:0 12px 0 0;-webkit-box-sizing:border-box;box-sizing:border-box}.el-form-item__content{line-height:40px;position:relative;font-size:14px}.el-form-item__content::after,.el-form-item__content::before{display:table;content:""}.el-form-item__content::after{clear:both}.el-form-item__content .el-input-group{vertical-align:top}.el-form-item__error{color:#F56C6C;font-size:12px;line-height:1;padding-top:4px;position:absolute;top:100%;left:0}.el-form-item__error--inline{position:relative;top:auto;left:auto;display:inline-block;margin-left:10px}.el-form-item.is-required:not(.is-no-asterisk) .el-form-item__label-wrap>.el-form-item__label:before,.el-form-item.is-required:not(.is-no-asterisk)>.el-form-item__label:before{content:'*';color:#F56C6C;margin-right:4px}.el-form-item.is-error .el-input-group__append .el-input__inner,.el-form-item.is-error .el-input-group__prepend .el-input__inner{border-color:transparent}.el-form-item.is-error .el-input__validateIcon{color:#F56C6C}.el-form-item--feedback .el-input__validateIcon{display:inline-block}.el-tabs__header{padding:0;position:relative;margin:0 0 15px}.el-tabs__active-bar{position:absolute;bottom:0;left:0;height:2px;background-color:#002FA7;z-index:1;-webkit-transition:-webkit-transform .3s cubic-bezier(.645,.045,.355,1);transition:-webkit-transform .3s cubic-bezier(.645,.045,.355,1);transition:transform .3s cubic-bezier(.645,.045,.355,1);transition:transform .3s cubic-bezier(.645,.045,.355,1),-webkit-transform .3s cubic-bezier(.645,.045,.355,1);list-style:none}.el-tabs__new-tab{float:right;border:1px solid #d3dce6;height:18px;width:18px;line-height:18px;margin:12px 0 9px 10px;border-radius:3px;text-align:center;font-size:12px;color:#d3dce6;cursor:pointer;-webkit-transition:all .15s;transition:all .15s}.el-collapse-item__arrow,.el-tabs__nav{-webkit-transition:-webkit-transform .3s}.el-tabs__new-tab .el-icon-plus{-webkit-transform:scale(.8,.8);transform:scale(.8,.8)}.el-tabs__new-tab:hover{color:#002FA7}.el-tabs__nav-wrap{overflow:hidden;margin-bottom:-1px;position:relative}.el-tabs__nav-wrap::after{content:"";position:absolute;left:0;bottom:0;width:100%;height:2px;background-color:#E4E7ED;z-index:1}.el-tabs--border-card>.el-tabs__header .el-tabs__nav-wrap::after,.el-tabs--card>.el-tabs__header .el-tabs__nav-wrap::after{content:none}.el-tabs__nav-wrap.is-scrollable{padding:0 20px;-webkit-box-sizing:border-box;box-sizing:border-box}.el-tabs__nav-scroll{overflow:hidden}.el-tabs__nav-next,.el-tabs__nav-prev{position:absolute;cursor:pointer;line-height:44px;font-size:12px;color:#909399}.el-tabs__nav-next{right:0}.el-tabs__nav-prev{left:0}.el-tabs__nav{white-space:nowrap;position:relative;transition:-webkit-transform .3s;transition:transform .3s;transition:transform .3s,-webkit-transform .3s;float:left;z-index:2}.el-tabs__nav.is-stretch{min-width:100%;display:-webkit-box;display:-ms-flexbox;display:flex}.el-tabs__nav.is-stretch>*{-webkit-box-flex:1;-ms-flex:1;flex:1;text-align:center}.el-tabs__item{padding:0 20px;height:40px;-webkit-box-sizing:border-box;box-sizing:border-box;line-height:40px;display:inline-block;list-style:none;font-size:14px;font-weight:500;color:#303133;position:relative}.el-tabs__item:focus,.el-tabs__item:focus:active{outline:0}.el-tabs__item:focus.is-active.is-focus:not(:active){-webkit-box-shadow:0 0 2px 2px #002FA7 inset;box-shadow:0 0 2px 2px #002FA7 inset;border-radius:3px}.el-tabs__item .el-icon-close{border-radius:50%;text-align:center;-webkit-transition:all .3s cubic-bezier(.645,.045,.355,1);transition:all .3s cubic-bezier(.645,.045,.355,1);margin-left:5px}.el-tabs__item .el-icon-close:before{-webkit-transform:scale(.9);transform:scale(.9);display:inline-block}.el-tabs__item .el-icon-close:hover{background-color:#3F3F3F;color:#FFF}.el-tabs__item.is-active{color:#002FA7}.el-tabs__item:hover{color:#002FA7;cursor:pointer}.el-tabs__item.is-disabled{color:#3F3F3F;cursor:default}.el-tabs__content{overflow:hidden;position:relative}.el-tabs--card>.el-tabs__header{border-bottom:1px solid #E4E7ED}.el-tabs--card>.el-tabs__header .el-tabs__nav{border:1px solid #E4E7ED;border-bottom:none;border-radius:4px 4px 0 0;-webkit-box-sizing:border-box;box-sizing:border-box}.el-tabs--card>.el-tabs__header .el-tabs__active-bar{display:none}.el-tabs--card>.el-tabs__header .el-tabs__item .el-icon-close{position:relative;font-size:12px;width:0;height:14px;vertical-align:middle;line-height:15px;overflow:hidden;top:-1px;right:-2px;-webkit-transform-origin:100% 50%;transform-origin:100% 50%}.el-tabs--card>.el-tabs__header .el-tabs__item.is-active.is-closable .el-icon-close,.el-tabs--card>.el-tabs__header .el-tabs__item.is-closable:hover .el-icon-close{width:14px}.el-tabs--card>.el-tabs__header .el-tabs__item{border-bottom:1px solid transparent;border-left:1px solid #E4E7ED;-webkit-transition:color .3s cubic-bezier(.645,.045,.355,1),padding .3s cubic-bezier(.645,.045,.355,1);transition:color .3s cubic-bezier(.645,.045,.355,1),padding .3s cubic-bezier(.645,.045,.355,1)}.el-tabs--card>.el-tabs__header .el-tabs__item:first-child{border-left:none}.el-tabs--card>.el-tabs__header .el-tabs__item.is-closable:hover{padding-left:13px;padding-right:13px}.el-tabs--card>.el-tabs__header .el-tabs__item.is-active{border-bottom-color:#FFF}.el-tabs--card>.el-tabs__header .el-tabs__item.is-active.is-closable{padding-left:20px;padding-right:20px}.el-tabs--border-card{background:#FFF;border:1px solid #BBB;-webkit-box-shadow:0 2px 4px 0 rgba(0,0,0,.12),0 0 6px 0 rgba(0,0,0,.04);box-shadow:0 2px 4px 0 rgba(0,0,0,.12),0 0 6px 0 rgba(0,0,0,.04)}.el-tabs--border-card>.el-tabs__content{padding:15px}.el-tabs--border-card>.el-tabs__header{background-color:#F5F7FA;border-bottom:1px solid #E4E7ED;margin:0}.el-tabs--border-card>.el-tabs__header .el-tabs__item{-webkit-transition:all .3s cubic-bezier(.645,.045,.355,1);transition:all .3s cubic-bezier(.645,.045,.355,1);border:1px solid transparent;margin-top:-1px;color:#909399}.el-tabs--border-card>.el-tabs__header .el-tabs__item+.el-tabs__item,.el-tabs--border-card>.el-tabs__header .el-tabs__item:first-child{margin-left:-1px}.el-tabs--border-card>.el-tabs__header .el-tabs__item.is-active{color:#002FA7;background-color:#FFF;border-right-color:#BBB;border-left-color:#BBB}.el-tabs--border-card>.el-tabs__header .el-tabs__item:not(.is-disabled):hover{color:#002FA7}.el-tabs--border-card>.el-tabs__header .el-tabs__item.is-disabled{color:#3F3F3F}.el-tabs--border-card>.el-tabs__header .is-scrollable .el-tabs__item:first-child{margin-left:0}.el-tabs--bottom .el-tabs__item.is-bottom:nth-child(2),.el-tabs--bottom .el-tabs__item.is-top:nth-child(2),.el-tabs--top .el-tabs__item.is-bottom:nth-child(2),.el-tabs--top .el-tabs__item.is-top:nth-child(2){padding-left:0}.el-tabs--bottom .el-tabs__item.is-bottom:last-child,.el-tabs--bottom .el-tabs__item.is-top:last-child,.el-tabs--top .el-tabs__item.is-bottom:last-child,.el-tabs--top .el-tabs__item.is-top:last-child{padding-right:0}.el-tabs--bottom .el-tabs--left>.el-tabs__header .el-tabs__item:nth-child(2),.el-tabs--bottom .el-tabs--right>.el-tabs__header .el-tabs__item:nth-child(2),.el-tabs--bottom.el-tabs--border-card>.el-tabs__header .el-tabs__item:nth-child(2),.el-tabs--bottom.el-tabs--card>.el-tabs__header .el-tabs__item:nth-child(2),.el-tabs--top .el-tabs--left>.el-tabs__header .el-tabs__item:nth-child(2),.el-tabs--top .el-tabs--right>.el-tabs__header .el-tabs__item:nth-child(2),.el-tabs--top.el-tabs--border-card>.el-tabs__header .el-tabs__item:nth-child(2),.el-tabs--top.el-tabs--card>.el-tabs__header .el-tabs__item:nth-child(2){padding-left:20px}.el-tabs--bottom .el-tabs--left>.el-tabs__header .el-tabs__item:last-child,.el-tabs--bottom .el-tabs--right>.el-tabs__header .el-tabs__item:last-child,.el-tabs--bottom.el-tabs--border-card>.el-tabs__header .el-tabs__item:last-child,.el-tabs--bottom.el-tabs--card>.el-tabs__header .el-tabs__item:last-child,.el-tabs--top .el-tabs--left>.el-tabs__header .el-tabs__item:last-child,.el-tabs--top .el-tabs--right>.el-tabs__header .el-tabs__item:last-child,.el-tabs--top.el-tabs--border-card>.el-tabs__header .el-tabs__item:last-child,.el-tabs--top.el-tabs--card>.el-tabs__header .el-tabs__item:last-child{padding-right:20px}.el-tabs--bottom .el-tabs__header.is-bottom{margin-bottom:0;margin-top:10px}.el-tabs--bottom.el-tabs--border-card .el-tabs__header.is-bottom{border-bottom:0;border-top:1px solid #BBB}.el-tabs--bottom.el-tabs--border-card .el-tabs__nav-wrap.is-bottom{margin-top:-1px;margin-bottom:0}.el-tabs--bottom.el-tabs--border-card .el-tabs__item.is-bottom:not(.is-active){border:1px solid transparent}.el-tabs--bottom.el-tabs--border-card .el-tabs__item.is-bottom{margin:0 -1px -1px}.el-tabs--left,.el-tabs--right{overflow:hidden}.el-tabs--left .el-tabs__header.is-left,.el-tabs--left .el-tabs__header.is-right,.el-tabs--left .el-tabs__nav-scroll,.el-tabs--left .el-tabs__nav-wrap.is-left,.el-tabs--left .el-tabs__nav-wrap.is-right,.el-tabs--right .el-tabs__header.is-left,.el-tabs--right .el-tabs__header.is-right,.el-tabs--right .el-tabs__nav-scroll,.el-tabs--right .el-tabs__nav-wrap.is-left,.el-tabs--right .el-tabs__nav-wrap.is-right{height:100%}.el-tabs--left .el-tabs__active-bar.is-left,.el-tabs--left .el-tabs__active-bar.is-right,.el-tabs--right .el-tabs__active-bar.is-left,.el-tabs--right .el-tabs__active-bar.is-right{top:0;bottom:auto;width:2px;height:auto}.el-tabs--left .el-tabs__nav-wrap.is-left,.el-tabs--left .el-tabs__nav-wrap.is-right,.el-tabs--right .el-tabs__nav-wrap.is-left,.el-tabs--right .el-tabs__nav-wrap.is-right{margin-bottom:0}.el-tabs--left .el-tabs__nav-wrap.is-left>.el-tabs__nav-next,.el-tabs--left .el-tabs__nav-wrap.is-left>.el-tabs__nav-prev,.el-tabs--left .el-tabs__nav-wrap.is-right>.el-tabs__nav-next,.el-tabs--left .el-tabs__nav-wrap.is-right>.el-tabs__nav-prev,.el-tabs--right .el-tabs__nav-wrap.is-left>.el-tabs__nav-next,.el-tabs--right .el-tabs__nav-wrap.is-left>.el-tabs__nav-prev,.el-tabs--right .el-tabs__nav-wrap.is-right>.el-tabs__nav-next,.el-tabs--right .el-tabs__nav-wrap.is-right>.el-tabs__nav-prev{height:30px;line-height:30px;width:100%;text-align:center;cursor:pointer}.el-tabs--left .el-tabs__nav-wrap.is-left>.el-tabs__nav-next i,.el-tabs--left .el-tabs__nav-wrap.is-left>.el-tabs__nav-prev i,.el-tabs--left .el-tabs__nav-wrap.is-right>.el-tabs__nav-next i,.el-tabs--left .el-tabs__nav-wrap.is-right>.el-tabs__nav-prev i,.el-tabs--right .el-tabs__nav-wrap.is-left>.el-tabs__nav-next i,.el-tabs--right .el-tabs__nav-wrap.is-left>.el-tabs__nav-prev i,.el-tabs--right .el-tabs__nav-wrap.is-right>.el-tabs__nav-next i,.el-tabs--right .el-tabs__nav-wrap.is-right>.el-tabs__nav-prev i{-webkit-transform:rotateZ(90deg);transform:rotateZ(90deg)}.el-tabs--left .el-tabs__nav-wrap.is-left>.el-tabs__nav-prev,.el-tabs--left .el-tabs__nav-wrap.is-right>.el-tabs__nav-prev,.el-tabs--right .el-tabs__nav-wrap.is-left>.el-tabs__nav-prev,.el-tabs--right .el-tabs__nav-wrap.is-right>.el-tabs__nav-prev{left:auto;top:0}.el-tabs--left .el-tabs__nav-wrap.is-left>.el-tabs__nav-next,.el-tabs--left .el-tabs__nav-wrap.is-right>.el-tabs__nav-next,.el-tabs--right .el-tabs__nav-wrap.is-left>.el-tabs__nav-next,.el-tabs--right .el-tabs__nav-wrap.is-right>.el-tabs__nav-next{right:auto;bottom:0}.el-tabs--left .el-tabs__active-bar.is-left,.el-tabs--left .el-tabs__nav-wrap.is-left::after{right:0;left:auto}.el-tabs--left .el-tabs__nav-wrap.is-left.is-scrollable,.el-tabs--left .el-tabs__nav-wrap.is-right.is-scrollable,.el-tabs--right .el-tabs__nav-wrap.is-left.is-scrollable,.el-tabs--right .el-tabs__nav-wrap.is-right.is-scrollable{padding:30px 0}.el-tabs--left .el-tabs__nav-wrap.is-left::after,.el-tabs--left .el-tabs__nav-wrap.is-right::after,.el-tabs--right .el-tabs__nav-wrap.is-left::after,.el-tabs--right .el-tabs__nav-wrap.is-right::after{height:100%;width:2px;bottom:auto;top:0}.el-tabs--left .el-tabs__nav.is-left,.el-tabs--left .el-tabs__nav.is-right,.el-tabs--right .el-tabs__nav.is-left,.el-tabs--right .el-tabs__nav.is-right{float:none}.el-tabs--left .el-tabs__item.is-left,.el-tabs--left .el-tabs__item.is-right,.el-tabs--right .el-tabs__item.is-left,.el-tabs--right .el-tabs__item.is-right{display:block}.el-tabs--left.el-tabs--card .el-tabs__active-bar.is-left,.el-tabs--right.el-tabs--card .el-tabs__active-bar.is-right{display:none}.el-tabs--left .el-tabs__header.is-left{float:left;margin-bottom:0;margin-right:10px}.el-tabs--left .el-tabs__nav-wrap.is-left{margin-right:-1px}.el-tabs--left .el-tabs__item.is-left{text-align:right}.el-tabs--left.el-tabs--card .el-tabs__item.is-left{border-left:none;border-right:1px solid #E4E7ED;border-bottom:none;border-top:1px solid #E4E7ED;text-align:left}.el-tabs--left.el-tabs--card .el-tabs__item.is-left:first-child{border-right:1px solid #E4E7ED;border-top:none}.el-tabs--left.el-tabs--card .el-tabs__item.is-left.is-active{border:1px solid #E4E7ED;border-right-color:#fff;border-left:none;border-bottom:none}.el-tabs--left.el-tabs--card .el-tabs__item.is-left.is-active:first-child{border-top:none}.el-tabs--left.el-tabs--card .el-tabs__item.is-left.is-active:last-child{border-bottom:none}.el-tabs--left.el-tabs--card .el-tabs__nav{border-radius:4px 0 0 4px;border-bottom:1px solid #E4E7ED;border-right:none}.el-tabs--left.el-tabs--card .el-tabs__new-tab{float:none}.el-tabs--left.el-tabs--border-card .el-tabs__header.is-left{border-right:1px solid #dfe4ed}.el-tabs--left.el-tabs--border-card .el-tabs__item.is-left{border:1px solid transparent;margin:-1px 0 -1px -1px}.el-tabs--left.el-tabs--border-card .el-tabs__item.is-left.is-active{border-color:#d1dbe5 transparent}.el-tabs--right .el-tabs__header.is-right{float:right;margin-bottom:0;margin-left:10px}.el-tabs--right .el-tabs__nav-wrap.is-right{margin-left:-1px}.el-tabs--right .el-tabs__nav-wrap.is-right::after{left:0;right:auto}.el-tabs--right .el-tabs__active-bar.is-right{left:0}.el-tabs--right.el-tabs--card .el-tabs__item.is-right{border-bottom:none;border-top:1px solid #E4E7ED}.el-tabs--right.el-tabs--card .el-tabs__item.is-right:first-child{border-left:1px solid #E4E7ED;border-top:none}.el-tabs--right.el-tabs--card .el-tabs__item.is-right.is-active{border:1px solid #E4E7ED;border-left-color:#fff;border-right:none;border-bottom:none}.el-tabs--right.el-tabs--card .el-tabs__item.is-right.is-active:first-child{border-top:none}.el-tabs--right.el-tabs--card .el-tabs__item.is-right.is-active:last-child{border-bottom:none}.el-tabs--right.el-tabs--card .el-tabs__nav{border-radius:0 4px 4px 0;border-bottom:1px solid #E4E7ED;border-left:none}.el-tabs--right.el-tabs--border-card .el-tabs__header.is-right{border-left:1px solid #dfe4ed}.el-tabs--right.el-tabs--border-card .el-tabs__item.is-right{border:1px solid transparent;margin:-1px -1px -1px 0}.el-tabs--right.el-tabs--border-card .el-tabs__item.is-right.is-active{border-color:#d1dbe5 transparent}.slideInLeft-transition,.slideInRight-transition{display:inline-block}.slideInRight-enter{-webkit-animation:slideInRight-enter .3s;animation:slideInRight-enter .3s}.slideInRight-leave{position:absolute;left:0;right:0;-webkit-animation:slideInRight-leave .3s;animation:slideInRight-leave .3s}.slideInLeft-enter{-webkit-animation:slideInLeft-enter .3s;animation:slideInLeft-enter .3s}.slideInLeft-leave{position:absolute;left:0;right:0;-webkit-animation:slideInLeft-leave .3s;animation:slideInLeft-leave .3s}@-webkit-keyframes slideInRight-enter{0%{opacity:0;-webkit-transform-origin:0 0;transform-origin:0 0;-webkit-transform:translateX(100%);transform:translateX(100%)}to{opacity:1;-webkit-transform-origin:0 0;transform-origin:0 0;-webkit-transform:translateX(0);transform:translateX(0)}}@keyframes slideInRight-enter{0%{opacity:0;-webkit-transform-origin:0 0;transform-origin:0 0;-webkit-transform:translateX(100%);transform:translateX(100%)}to{opacity:1;-webkit-transform-origin:0 0;transform-origin:0 0;-webkit-transform:translateX(0);transform:translateX(0)}}@-webkit-keyframes slideInRight-leave{0%{-webkit-transform-origin:0 0;transform-origin:0 0;-webkit-transform:translateX(0);transform:translateX(0);opacity:1}100%{-webkit-transform-origin:0 0;transform-origin:0 0;-webkit-transform:translateX(100%);transform:translateX(100%);opacity:0}}@keyframes slideInRight-leave{0%{-webkit-transform-origin:0 0;transform-origin:0 0;-webkit-transform:translateX(0);transform:translateX(0);opacity:1}100%{-webkit-transform-origin:0 0;transform-origin:0 0;-webkit-transform:translateX(100%);transform:translateX(100%);opacity:0}}@-webkit-keyframes slideInLeft-enter{0%{opacity:0;-webkit-transform-origin:0 0;transform-origin:0 0;-webkit-transform:translateX(-100%);transform:translateX(-100%)}to{opacity:1;-webkit-transform-origin:0 0;transform-origin:0 0;-webkit-transform:translateX(0);transform:translateX(0)}}@keyframes slideInLeft-enter{0%{opacity:0;-webkit-transform-origin:0 0;transform-origin:0 0;-webkit-transform:translateX(-100%);transform:translateX(-100%)}to{opacity:1;-webkit-transform-origin:0 0;transform-origin:0 0;-webkit-transform:translateX(0);transform:translateX(0)}}@-webkit-keyframes slideInLeft-leave{0%{-webkit-transform-origin:0 0;transform-origin:0 0;-webkit-transform:translateX(0);transform:translateX(0);opacity:1}100%{-webkit-transform-origin:0 0;transform-origin:0 0;-webkit-transform:translateX(-100%);transform:translateX(-100%);opacity:0}}@keyframes slideInLeft-leave{0%{-webkit-transform-origin:0 0;transform-origin:0 0;-webkit-transform:translateX(0);transform:translateX(0);opacity:1}100%{-webkit-transform-origin:0 0;transform-origin:0 0;-webkit-transform:translateX(-100%);transform:translateX(-100%);opacity:0}}.el-tree{position:relative;cursor:default;background:#FFF;color:#606266}.el-tree__empty-block{position:relative;min-height:60px;text-align:center;width:100%;height:100%}.el-tree__empty-text{position:absolute;left:50%;top:50%;-webkit-transform:translate(-50%,-50%);transform:translate(-50%,-50%);color:#909399;font-size:14px}.el-tree__drop-indicator{position:absolute;left:0;right:0;height:1px;background-color:#002FA7}.el-tree-node{white-space:nowrap;outline:0}.el-tree-node:focus>.el-tree-node__content{background-color:#F5F7FA}.el-tree-node.is-drop-inner>.el-tree-node__content .el-tree-node__label{background-color:#002FA7;color:#fff}.el-tree-node__content{display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-align:center;-ms-flex-align:center;align-items:center;height:26px;cursor:pointer}.el-tree-node__content>.el-tree-node__expand-icon{padding:6px}.el-tree-node__content>label.el-checkbox{margin-right:8px}.el-tree-node__content:hover{background-color:#F5F7FA}.el-tree.is-dragging .el-tree-node__content{cursor:move}.el-tree.is-dragging.is-drop-not-allow .el-tree-node__content{cursor:not-allowed}.el-tree-node__expand-icon{cursor:pointer;color:#3F3F3F;font-size:12px;-webkit-transform:rotate(0);transform:rotate(0);-webkit-transition:-webkit-transform .3s ease-in-out;transition:-webkit-transform .3s ease-in-out;transition:transform .3s ease-in-out;transition:transform .3s ease-in-out,-webkit-transform .3s ease-in-out}.el-tree-node__expand-icon.expanded{-webkit-transform:rotate(90deg);transform:rotate(90deg)}.el-tree-node__expand-icon.is-leaf{color:transparent;cursor:default}.el-tree-node__label{font-size:14px}.el-tree-node__loading-icon{margin-right:8px;font-size:14px;color:#3F3F3F}.el-tree-node>.el-tree-node__children{overflow:hidden;background-color:transparent}.el-tree-node.is-expanded>.el-tree-node__children{display:block}.el-tree--highlight-current .el-tree-node.is-current>.el-tree-node__content{background-color:#ebeef8}.el-alert{width:100%;padding:8px 16px;margin:0;-webkit-box-sizing:border-box;box-sizing:border-box;border-radius:4px;position:relative;background-color:#FFF;overflow:hidden;opacity:1;display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-align:center;-ms-flex-align:center;align-items:center;-webkit-transition:opacity .2s;transition:opacity .2s}.el-alert.is-light .el-alert__closebtn{color:#3F3F3F}.el-alert.is-dark .el-alert__closebtn,.el-alert.is-dark .el-alert__description{color:#FFF}.el-alert.is-center{-webkit-box-pack:center;-ms-flex-pack:center;justify-content:center}.el-alert--success.is-light{background-color:#f0f9eb;color:#67C23A}.el-alert--success.is-light .el-alert__description{color:#67C23A}.el-alert--success.is-dark{background-color:#67C23A;color:#FFF}.el-alert--info.is-light{background-color:#f4f4f5;color:#909399}.el-alert--info.is-dark{background-color:#909399;color:#FFF}.el-alert--info .el-alert__description{color:#909399}.el-alert--warning.is-light{background-color:#fdf6ec;color:#E6A23C}.el-alert--warning.is-light .el-alert__description{color:#E6A23C}.el-alert--warning.is-dark{background-color:#E6A23C;color:#FFF}.el-alert--error.is-light{background-color:#fef0f0;color:#F56C6C}.el-alert--error.is-light .el-alert__description{color:#F56C6C}.el-alert--error.is-dark{background-color:#F56C6C;color:#FFF}.el-alert__content{display:table-cell;padding:0 8px}.el-alert__icon{font-size:16px;width:16px}.el-alert__icon.is-big{font-size:28px;width:28px}.el-alert__title{font-size:13px;line-height:18px}.el-alert__title.is-bold{font-weight:700}.el-alert .el-alert__description{font-size:12px;margin:5px 0 0}.el-alert__closebtn{font-size:12px;opacity:1;position:absolute;top:12px;right:15px;cursor:pointer}.el-alert-fade-enter,.el-alert-fade-leave-active,.el-loading-fade-enter,.el-loading-fade-leave-active,.el-notification-fade-leave-active{opacity:0}.el-alert__closebtn.is-customed{font-style:normal;font-size:13px;top:9px}.el-notification{display:-webkit-box;display:-ms-flexbox;display:flex;width:330px;padding:14px 26px 14px 13px;border-radius:8px;-webkit-box-sizing:border-box;box-sizing:border-box;border:1px solid #EBEEF5;position:fixed;background-color:#FFF;-webkit-box-shadow:0 2px 12px 0 rgba(0,0,0,.1);box-shadow:0 2px 12px 0 rgba(0,0,0,.1);-webkit-transition:opacity .3s,left .3s,right .3s,top .4s,bottom .3s,-webkit-transform .3s;transition:opacity .3s,left .3s,right .3s,top .4s,bottom .3s,-webkit-transform .3s;transition:opacity .3s,transform .3s,left .3s,right .3s,top .4s,bottom .3s;transition:opacity .3s,transform .3s,left .3s,right .3s,top .4s,bottom .3s,-webkit-transform .3s;overflow:hidden}.el-notification.right{right:16px}.el-notification.left{left:16px}.el-notification__group{margin-left:13px;margin-right:8px}.el-notification__title{font-weight:700;font-size:16px;color:#303133;margin:0}.el-notification__content{font-size:14px;line-height:21px;margin:6px 0 0;color:#606266;text-align:justify}.el-notification__content p{margin:0}.el-notification__icon{height:24px;width:24px;font-size:24px}.el-notification__closeBtn{position:absolute;top:18px;right:15px;cursor:pointer;color:#909399;font-size:16px}.el-notification__closeBtn:hover{color:#606266}.el-notification .el-icon-success{color:#67C23A}.el-notification .el-icon-error{color:#F56C6C}.el-notification .el-icon-info{color:#909399}.el-notification .el-icon-warning{color:#E6A23C}.el-notification-fade-enter.right{right:0;-webkit-transform:translateX(100%);transform:translateX(100%)}.el-notification-fade-enter.left{left:0;-webkit-transform:translateX(-100%);transform:translateX(-100%)}.el-input-number{position:relative;display:inline-block;width:180px;line-height:30px}.el-input-number .el-input{display:block}.el-input-number .el-input__inner{-webkit-appearance:none;padding-left:42px;padding-right:42px;text-align:center}.el-input-number__decrease,.el-input-number__increase{position:absolute;z-index:1;top:1px;width:32px;height:auto;text-align:center;background:#F5F7FA;color:#606266;cursor:pointer;font-size:13px}.el-input-number__decrease:hover,.el-input-number__increase:hover{color:#002FA7}.el-input-number__decrease:hover:not(.is-disabled)~.el-input .el-input__inner:not(.is-disabled),.el-input-number__increase:hover:not(.is-disabled)~.el-input .el-input__inner:not(.is-disabled){border-color:#002FA7}.el-input-number__decrease.is-disabled,.el-input-number__increase.is-disabled{color:#3F3F3F;cursor:not-allowed}.el-input-number__increase{right:1px;border-radius:0 4px 4px 0;border-left:1px solid #BBB}.el-input-number__decrease{left:1px;border-radius:4px 0 0 4px;border-right:1px solid #BBB}.el-input-number.is-disabled .el-input-number__decrease,.el-input-number.is-disabled .el-input-number__increase{border-color:#E4E7ED;color:#E4E7ED}.el-input-number.is-disabled .el-input-number__decrease:hover,.el-input-number.is-disabled .el-input-number__increase:hover{color:#E4E7ED;cursor:not-allowed}.el-input-number--medium{width:200px;line-height:34px}.el-input-number--medium .el-input-number__decrease,.el-input-number--medium .el-input-number__increase{width:36px;font-size:14px}.el-input-number--medium .el-input__inner{padding-left:43px;padding-right:43px}.el-input-number--small{width:130px;line-height:30px}.el-input-number--small .el-input-number__decrease,.el-input-number--small .el-input-number__increase{width:32px;font-size:13px}.el-input-number--small .el-input-number__decrease [class*=el-icon],.el-input-number--small .el-input-number__increase [class*=el-icon]{-webkit-transform:scale(.9);transform:scale(.9)}.el-input-number--small .el-input__inner{padding-left:39px;padding-right:39px}.el-input-number--mini{width:130px;line-height:26px}.el-input-number--mini .el-input-number__decrease,.el-input-number--mini .el-input-number__increase{width:28px;font-size:12px}.el-input-number--mini .el-input-number__decrease [class*=el-icon],.el-input-number--mini .el-input-number__increase [class*=el-icon]{-webkit-transform:scale(.8);transform:scale(.8)}.el-input-number--mini .el-input__inner{padding-left:35px;padding-right:35px}.el-input-number.is-without-controls .el-input__inner{padding-left:15px;padding-right:15px}.el-input-number.is-controls-right .el-input__inner{padding-left:15px;padding-right:42px}.el-input-number.is-controls-right .el-input-number__decrease,.el-input-number.is-controls-right .el-input-number__increase{height:auto;line-height:15px}.el-input-number.is-controls-right .el-input-number__decrease [class*=el-icon],.el-input-number.is-controls-right .el-input-number__increase [class*=el-icon]{-webkit-transform:scale(.8);transform:scale(.8)}.el-input-number.is-controls-right .el-input-number__increase{border-radius:0 4px 0 0;border-bottom:1px solid #BBB}.el-input-number.is-controls-right .el-input-number__decrease{right:1px;bottom:1px;top:auto;left:auto;border-right:none;border-left:1px solid #BBB;border-radius:0 0 4px}.el-input-number.is-controls-right[class*=medium] [class*=decrease],.el-input-number.is-controls-right[class*=medium] [class*=increase]{line-height:17px}.el-input-number.is-controls-right[class*=small] [class*=decrease],.el-input-number.is-controls-right[class*=small] [class*=increase]{line-height:15px}.el-input-number.is-controls-right[class*=mini] [class*=decrease],.el-input-number.is-controls-right[class*=mini] [class*=increase]{line-height:13px}.el-tooltip__popper{position:absolute;border-radius:4px;padding:10px;z-index:2000;font-size:12px;line-height:1.2;min-width:10px;word-wrap:break-word}.el-tooltip__popper .popper__arrow,.el-tooltip__popper .popper__arrow::after{position:absolute;display:block;width:0;height:0;border-color:transparent;border-style:solid}.el-tooltip__popper .popper__arrow{border-width:6px}.el-tooltip__popper .popper__arrow::after{content:" ";border-width:5px}.el-progress-bar__inner::after,.el-row::after,.el-row::before,.el-slider::after,.el-slider::before,.el-slider__button-wrapper::after,.el-upload-cover::after{content:""}.el-tooltip__popper[x-placement^=top]{margin-bottom:12px}.el-tooltip__popper[x-placement^=top] .popper__arrow{bottom:-6px;border-top-color:#303133;border-bottom-width:0}.el-tooltip__popper[x-placement^=top] .popper__arrow::after{bottom:1px;margin-left:-5px;border-top-color:#303133;border-bottom-width:0}.el-tooltip__popper[x-placement^=bottom]{margin-top:12px}.el-tooltip__popper[x-placement^=bottom] .popper__arrow{top:-6px;border-top-width:0;border-bottom-color:#303133}.el-tooltip__popper[x-placement^=bottom] .popper__arrow::after{top:1px;margin-left:-5px;border-top-width:0;border-bottom-color:#303133}.el-tooltip__popper[x-placement^=right]{margin-left:12px}.el-tooltip__popper[x-placement^=right] .popper__arrow{left:-6px;border-right-color:#303133;border-left-width:0}.el-tooltip__popper[x-placement^=right] .popper__arrow::after{bottom:-5px;left:1px;border-right-color:#303133;border-left-width:0}.el-tooltip__popper[x-placement^=left]{margin-right:12px}.el-tooltip__popper[x-placement^=left] .popper__arrow{right:-6px;border-right-width:0;border-left-color:#303133}.el-tooltip__popper[x-placement^=left] .popper__arrow::after{right:1px;bottom:-5px;margin-left:-5px;border-right-width:0;border-left-color:#303133}.el-tooltip__popper.is-dark{background:#303133;color:#FFF}.el-tooltip__popper.is-light{background:#FFF;border:1px solid #303133}.el-tooltip__popper.is-light[x-placement^=top] .popper__arrow{border-top-color:#303133}.el-tooltip__popper.is-light[x-placement^=top] .popper__arrow::after{border-top-color:#FFF}.el-tooltip__popper.is-light[x-placement^=bottom] .popper__arrow{border-bottom-color:#303133}.el-tooltip__popper.is-light[x-placement^=bottom] .popper__arrow::after{border-bottom-color:#FFF}.el-tooltip__popper.is-light[x-placement^=left] .popper__arrow{border-left-color:#303133}.el-tooltip__popper.is-light[x-placement^=left] .popper__arrow::after{border-left-color:#FFF}.el-tooltip__popper.is-light[x-placement^=right] .popper__arrow{border-right-color:#303133}.el-tooltip__popper.is-light[x-placement^=right] .popper__arrow::after{border-right-color:#FFF}.el-slider::after,.el-slider::before{display:table}.el-slider__button-wrapper .el-tooltip,.el-slider__button-wrapper::after{vertical-align:middle;display:inline-block}.el-slider::after{clear:both}.el-slider__runway{width:100%;height:6px;margin:16px 0;background-color:#E4E7ED;border-radius:3px;position:relative;cursor:pointer;vertical-align:middle}.el-slider__runway.show-input{margin-right:160px;width:auto}.el-slider__runway.disabled{cursor:default}.el-slider__runway.disabled .el-slider__bar{background-color:#3F3F3F}.el-slider__runway.disabled .el-slider__button{border-color:#3F3F3F}.el-slider__runway.disabled .el-slider__button-wrapper.dragging,.el-slider__runway.disabled .el-slider__button-wrapper.hover,.el-slider__runway.disabled .el-slider__button-wrapper:hover{cursor:not-allowed}.el-slider__runway.disabled .el-slider__button.dragging,.el-slider__runway.disabled .el-slider__button.hover,.el-slider__runway.disabled .el-slider__button:hover{-webkit-transform:scale(1);transform:scale(1);cursor:not-allowed}.el-slider__button-wrapper,.el-slider__stop{-webkit-transform:translateX(-50%);position:absolute}.el-slider__input{float:right;margin-top:3px;width:130px}.el-slider__input.el-input-number--mini{margin-top:5px}.el-slider__input.el-input-number--medium{margin-top:0}.el-slider__input.el-input-number--large{margin-top:-2px}.el-slider__bar{height:6px;background-color:#002FA7;border-top-left-radius:3px;border-bottom-left-radius:3px;position:absolute}.el-slider__button-wrapper{height:36px;width:36px;z-index:1001;top:-15px;transform:translateX(-50%);background-color:transparent;text-align:center;user-select:none;line-height:normal}.el-slider__button-wrapper::after{height:100%}.el-slider__button-wrapper.hover,.el-slider__button-wrapper:hover{cursor:-webkit-grab;cursor:grab}.el-slider__button-wrapper.dragging{cursor:-webkit-grabbing;cursor:grabbing}.el-slider__button{width:16px;height:16px;border:2px solid #002FA7;background-color:#FFF;border-radius:50%;-webkit-transition:.2s;transition:.2s;user-select:none}.el-image-viewer__btn,.el-step__icon-inner{-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none}.el-slider__button.dragging,.el-slider__button.hover,.el-slider__button:hover{-webkit-transform:scale(1.2);transform:scale(1.2)}.el-slider__button.hover,.el-slider__button:hover{cursor:-webkit-grab;cursor:grab}.el-slider__button.dragging{cursor:-webkit-grabbing;cursor:grabbing}.el-slider__stop{height:6px;width:6px;border-radius:100%;background-color:#FFF;transform:translateX(-50%)}.el-slider__marks{top:0;left:12px;width:18px;height:100%}.el-slider__marks-text{position:absolute;-webkit-transform:translateX(-50%);transform:translateX(-50%);font-size:14px;color:#909399;margin-top:15px}.el-slider.is-vertical{position:relative}.el-slider.is-vertical .el-slider__runway{width:6px;height:100%;margin:0 16px}.el-slider.is-vertical .el-slider__bar{width:6px;height:auto;border-radius:0 0 3px 3px}.el-slider.is-vertical .el-slider__button-wrapper{top:auto;left:-15px;-webkit-transform:translateY(50%);transform:translateY(50%)}.el-slider.is-vertical .el-slider__stop{-webkit-transform:translateY(50%);transform:translateY(50%)}.el-slider.is-vertical.el-slider--with-input{padding-bottom:58px}.el-slider.is-vertical.el-slider--with-input .el-slider__input{overflow:visible;float:none;position:absolute;bottom:22px;width:36px;margin-top:15px}.el-slider.is-vertical.el-slider--with-input .el-slider__input .el-input__inner{text-align:center;padding-left:5px;padding-right:5px}.el-slider.is-vertical.el-slider--with-input .el-slider__input .el-input-number__decrease,.el-slider.is-vertical.el-slider--with-input .el-slider__input .el-input-number__increase{top:32px;margin-top:-1px;border:1px solid #BBB;line-height:20px;-webkit-box-sizing:border-box;box-sizing:border-box;-webkit-transition:border-color .2s cubic-bezier(.645,.045,.355,1);transition:border-color .2s cubic-bezier(.645,.045,.355,1)}.el-slider.is-vertical.el-slider--with-input .el-slider__input .el-input-number__decrease{width:18px;right:18px;border-bottom-left-radius:4px}.el-slider.is-vertical.el-slider--with-input .el-slider__input .el-input-number__increase{width:19px;border-bottom-right-radius:4px}.el-slider.is-vertical.el-slider--with-input .el-slider__input .el-input-number__increase~.el-input .el-input__inner{border-bottom-left-radius:0;border-bottom-right-radius:0}.el-slider.is-vertical.el-slider--with-input .el-slider__input:hover .el-input-number__decrease,.el-slider.is-vertical.el-slider--with-input .el-slider__input:hover .el-input-number__increase{border-color:#3F3F3F}.el-slider.is-vertical.el-slider--with-input .el-slider__input:active .el-input-number__decrease,.el-slider.is-vertical.el-slider--with-input .el-slider__input:active .el-input-number__increase{border-color:#002FA7}.el-slider.is-vertical .el-slider__marks-text{margin-top:0;left:15px;-webkit-transform:translateY(50%);transform:translateY(50%)}.el-loading-parent--relative{position:relative!important}.el-loading-parent--hidden{overflow:hidden!important}.el-loading-mask{position:absolute;z-index:2000;background-color:rgba(255,255,255,.9);margin:0;top:0;right:0;bottom:0;left:0;-webkit-transition:opacity .3s;transition:opacity .3s}.el-loading-mask.is-fullscreen{position:fixed}.el-loading-mask.is-fullscreen .el-loading-spinner{margin-top:-25px}.el-loading-mask.is-fullscreen .el-loading-spinner .circular{height:50px;width:50px}.el-loading-spinner{top:50%;margin-top:-21px;width:100%;text-align:center;position:absolute}.el-col-pull-0,.el-col-pull-1,.el-col-pull-10,.el-col-pull-11,.el-col-pull-13,.el-col-pull-14,.el-col-pull-15,.el-col-pull-16,.el-col-pull-17,.el-col-pull-18,.el-col-pull-19,.el-col-pull-2,.el-col-pull-20,.el-col-pull-21,.el-col-pull-22,.el-col-pull-23,.el-col-pull-24,.el-col-pull-3,.el-col-pull-4,.el-col-pull-5,.el-col-pull-6,.el-col-pull-7,.el-col-pull-8,.el-col-pull-9,.el-col-push-0,.el-col-push-1,.el-col-push-10,.el-col-push-11,.el-col-push-12,.el-col-push-13,.el-col-push-14,.el-col-push-15,.el-col-push-16,.el-col-push-17,.el-col-push-18,.el-col-push-19,.el-col-push-2,.el-col-push-20,.el-col-push-21,.el-col-push-22,.el-col-push-23,.el-col-push-24,.el-col-push-3,.el-col-push-4,.el-col-push-5,.el-col-push-6,.el-col-push-7,.el-col-push-8,.el-col-push-9,.el-row{position:relative}.el-loading-spinner .el-loading-text{color:#002FA7;margin:3px 0;font-size:14px}.el-loading-spinner .circular{height:42px;width:42px;-webkit-animation:loading-rotate 2s linear infinite;animation:loading-rotate 2s linear infinite}.el-loading-spinner .path{-webkit-animation:loading-dash 1.5s ease-in-out infinite;animation:loading-dash 1.5s ease-in-out infinite;stroke-dasharray:90,150;stroke-dashoffset:0;stroke-width:2;stroke:#002FA7;stroke-linecap:round}.el-loading-spinner i{color:#002FA7}@-webkit-keyframes loading-rotate{100%{-webkit-transform:rotate(360deg);transform:rotate(360deg)}}@keyframes loading-rotate{100%{-webkit-transform:rotate(360deg);transform:rotate(360deg)}}@-webkit-keyframes loading-dash{0%{stroke-dasharray:1,200;stroke-dashoffset:0}50%{stroke-dasharray:90,150;stroke-dashoffset:-40px}100%{stroke-dasharray:90,150;stroke-dashoffset:-120px}}@keyframes loading-dash{0%{stroke-dasharray:1,200;stroke-dashoffset:0}50%{stroke-dasharray:90,150;stroke-dashoffset:-40px}100%{stroke-dasharray:90,150;stroke-dashoffset:-120px}}.el-row{-webkit-box-sizing:border-box;box-sizing:border-box}.el-row::after,.el-row::before{display:table}.el-row::after{clear:both}.el-row--flex{display:-webkit-box;display:-ms-flexbox;display:flex}.el-col-0,.el-row--flex:after,.el-row--flex:before{display:none}.el-row--flex.is-justify-center{-webkit-box-pack:center;-ms-flex-pack:center;justify-content:center}.el-row--flex.is-justify-end{-webkit-box-pack:end;-ms-flex-pack:end;justify-content:flex-end}.el-row--flex.is-justify-space-between{-webkit-box-pack:justify;-ms-flex-pack:justify;justify-content:space-between}.el-row--flex.is-justify-space-around{-ms-flex-pack:distribute;justify-content:space-around}.el-row--flex.is-align-middle{-webkit-box-align:center;-ms-flex-align:center;align-items:center}.el-row--flex.is-align-bottom{-webkit-box-align:end;-ms-flex-align:end;align-items:flex-end}[class*=el-col-]{float:left;-webkit-box-sizing:border-box;box-sizing:border-box}.el-upload--picture-card,.el-upload-dragger{-webkit-box-sizing:border-box;cursor:pointer}.el-col-0{width:0%}.el-col-offset-0{margin-left:0}.el-col-pull-0{right:0}.el-col-push-0{left:0}.el-col-1{width:4.16667%}.el-col-offset-1{margin-left:4.16667%}.el-col-pull-1{right:4.16667%}.el-col-push-1{left:4.16667%}.el-col-2{width:8.33333%}.el-col-offset-2{margin-left:8.33333%}.el-col-pull-2{right:8.33333%}.el-col-push-2{left:8.33333%}.el-col-3{width:12.5%}.el-col-offset-3{margin-left:12.5%}.el-col-pull-3{right:12.5%}.el-col-push-3{left:12.5%}.el-col-4{width:16.66667%}.el-col-offset-4{margin-left:16.66667%}.el-col-pull-4{right:16.66667%}.el-col-push-4{left:16.66667%}.el-col-5{width:20.83333%}.el-col-offset-5{margin-left:20.83333%}.el-col-pull-5{right:20.83333%}.el-col-push-5{left:20.83333%}.el-col-6{width:25%}.el-col-offset-6{margin-left:25%}.el-col-pull-6{right:25%}.el-col-push-6{left:25%}.el-col-7{width:29.16667%}.el-col-offset-7{margin-left:29.16667%}.el-col-pull-7{right:29.16667%}.el-col-push-7{left:29.16667%}.el-col-8{width:33.33333%}.el-col-offset-8{margin-left:33.33333%}.el-col-pull-8{right:33.33333%}.el-col-push-8{left:33.33333%}.el-col-9{width:37.5%}.el-col-offset-9{margin-left:37.5%}.el-col-pull-9{right:37.5%}.el-col-push-9{left:37.5%}.el-col-10{width:41.66667%}.el-col-offset-10{margin-left:41.66667%}.el-col-pull-10{right:41.66667%}.el-col-push-10{left:41.66667%}.el-col-11{width:45.83333%}.el-col-offset-11{margin-left:45.83333%}.el-col-pull-11{right:45.83333%}.el-col-push-11{left:45.83333%}.el-col-12{width:50%}.el-col-offset-12{margin-left:50%}.el-col-pull-12{position:relative;right:50%}.el-col-push-12{left:50%}.el-col-13{width:54.16667%}.el-col-offset-13{margin-left:54.16667%}.el-col-pull-13{right:54.16667%}.el-col-push-13{left:54.16667%}.el-col-14{width:58.33333%}.el-col-offset-14{margin-left:58.33333%}.el-col-pull-14{right:58.33333%}.el-col-push-14{left:58.33333%}.el-col-15{width:62.5%}.el-col-offset-15{margin-left:62.5%}.el-col-pull-15{right:62.5%}.el-col-push-15{left:62.5%}.el-col-16{width:66.66667%}.el-col-offset-16{margin-left:66.66667%}.el-col-pull-16{right:66.66667%}.el-col-push-16{left:66.66667%}.el-col-17{width:70.83333%}.el-col-offset-17{margin-left:70.83333%}.el-col-pull-17{right:70.83333%}.el-col-push-17{left:70.83333%}.el-col-18{width:75%}.el-col-offset-18{margin-left:75%}.el-col-pull-18{right:75%}.el-col-push-18{left:75%}.el-col-19{width:79.16667%}.el-col-offset-19{margin-left:79.16667%}.el-col-pull-19{right:79.16667%}.el-col-push-19{left:79.16667%}.el-col-20{width:83.33333%}.el-col-offset-20{margin-left:83.33333%}.el-col-pull-20{right:83.33333%}.el-col-push-20{left:83.33333%}.el-col-21{width:87.5%}.el-col-offset-21{margin-left:87.5%}.el-col-pull-21{right:87.5%}.el-col-push-21{left:87.5%}.el-col-22{width:91.66667%}.el-col-offset-22{margin-left:91.66667%}.el-col-pull-22{right:91.66667%}.el-col-push-22{left:91.66667%}.el-col-23{width:95.83333%}.el-col-offset-23{margin-left:95.83333%}.el-col-pull-23{right:95.83333%}.el-col-push-23{left:95.83333%}.el-col-24{width:100%}.el-col-offset-24{margin-left:100%}.el-col-pull-24{right:100%}.el-col-push-24{left:100%}@media only screen and (max-width:767px){.el-col-xs-0{display:none;width:0%}.el-col-xs-offset-0{margin-left:0}.el-col-xs-pull-0{position:relative;right:0}.el-col-xs-push-0{position:relative;left:0}.el-col-xs-1{width:4.16667%}.el-col-xs-offset-1{margin-left:4.16667%}.el-col-xs-pull-1{position:relative;right:4.16667%}.el-col-xs-push-1{position:relative;left:4.16667%}.el-col-xs-2{width:8.33333%}.el-col-xs-offset-2{margin-left:8.33333%}.el-col-xs-pull-2{position:relative;right:8.33333%}.el-col-xs-push-2{position:relative;left:8.33333%}.el-col-xs-3{width:12.5%}.el-col-xs-offset-3{margin-left:12.5%}.el-col-xs-pull-3{position:relative;right:12.5%}.el-col-xs-push-3{position:relative;left:12.5%}.el-col-xs-4{width:16.66667%}.el-col-xs-offset-4{margin-left:16.66667%}.el-col-xs-pull-4{position:relative;right:16.66667%}.el-col-xs-push-4{position:relative;left:16.66667%}.el-col-xs-5{width:20.83333%}.el-col-xs-offset-5{margin-left:20.83333%}.el-col-xs-pull-5{position:relative;right:20.83333%}.el-col-xs-push-5{position:relative;left:20.83333%}.el-col-xs-6{width:25%}.el-col-xs-offset-6{margin-left:25%}.el-col-xs-pull-6{position:relative;right:25%}.el-col-xs-push-6{position:relative;left:25%}.el-col-xs-7{width:29.16667%}.el-col-xs-offset-7{margin-left:29.16667%}.el-col-xs-pull-7{position:relative;right:29.16667%}.el-col-xs-push-7{position:relative;left:29.16667%}.el-col-xs-8{width:33.33333%}.el-col-xs-offset-8{margin-left:33.33333%}.el-col-xs-pull-8{position:relative;right:33.33333%}.el-col-xs-push-8{position:relative;left:33.33333%}.el-col-xs-9{width:37.5%}.el-col-xs-offset-9{margin-left:37.5%}.el-col-xs-pull-9{position:relative;right:37.5%}.el-col-xs-push-9{position:relative;left:37.5%}.el-col-xs-10{width:41.66667%}.el-col-xs-offset-10{margin-left:41.66667%}.el-col-xs-pull-10{position:relative;right:41.66667%}.el-col-xs-push-10{position:relative;left:41.66667%}.el-col-xs-11{width:45.83333%}.el-col-xs-offset-11{margin-left:45.83333%}.el-col-xs-pull-11{position:relative;right:45.83333%}.el-col-xs-push-11{position:relative;left:45.83333%}.el-col-xs-12{width:50%}.el-col-xs-offset-12{margin-left:50%}.el-col-xs-pull-12{position:relative;right:50%}.el-col-xs-push-12{position:relative;left:50%}.el-col-xs-13{width:54.16667%}.el-col-xs-offset-13{margin-left:54.16667%}.el-col-xs-pull-13{position:relative;right:54.16667%}.el-col-xs-push-13{position:relative;left:54.16667%}.el-col-xs-14{width:58.33333%}.el-col-xs-offset-14{margin-left:58.33333%}.el-col-xs-pull-14{position:relative;right:58.33333%}.el-col-xs-push-14{position:relative;left:58.33333%}.el-col-xs-15{width:62.5%}.el-col-xs-offset-15{margin-left:62.5%}.el-col-xs-pull-15{position:relative;right:62.5%}.el-col-xs-push-15{position:relative;left:62.5%}.el-col-xs-16{width:66.66667%}.el-col-xs-offset-16{margin-left:66.66667%}.el-col-xs-pull-16{position:relative;right:66.66667%}.el-col-xs-push-16{position:relative;left:66.66667%}.el-col-xs-17{width:70.83333%}.el-col-xs-offset-17{margin-left:70.83333%}.el-col-xs-pull-17{position:relative;right:70.83333%}.el-col-xs-push-17{position:relative;left:70.83333%}.el-col-xs-18{width:75%}.el-col-xs-offset-18{margin-left:75%}.el-col-xs-pull-18{position:relative;right:75%}.el-col-xs-push-18{position:relative;left:75%}.el-col-xs-19{width:79.16667%}.el-col-xs-offset-19{margin-left:79.16667%}.el-col-xs-pull-19{position:relative;right:79.16667%}.el-col-xs-push-19{position:relative;left:79.16667%}.el-col-xs-20{width:83.33333%}.el-col-xs-offset-20{margin-left:83.33333%}.el-col-xs-pull-20{position:relative;right:83.33333%}.el-col-xs-push-20{position:relative;left:83.33333%}.el-col-xs-21{width:87.5%}.el-col-xs-offset-21{margin-left:87.5%}.el-col-xs-pull-21{position:relative;right:87.5%}.el-col-xs-push-21{position:relative;left:87.5%}.el-col-xs-22{width:91.66667%}.el-col-xs-offset-22{margin-left:91.66667%}.el-col-xs-pull-22{position:relative;right:91.66667%}.el-col-xs-push-22{position:relative;left:91.66667%}.el-col-xs-23{width:95.83333%}.el-col-xs-offset-23{margin-left:95.83333%}.el-col-xs-pull-23{position:relative;right:95.83333%}.el-col-xs-push-23{position:relative;left:95.83333%}.el-col-xs-24{width:100%}.el-col-xs-offset-24{margin-left:100%}.el-col-xs-pull-24{position:relative;right:100%}.el-col-xs-push-24{position:relative;left:100%}}@media only screen and (min-width:768px){.el-col-sm-0{display:none;width:0%}.el-col-sm-offset-0{margin-left:0}.el-col-sm-pull-0{position:relative;right:0}.el-col-sm-push-0{position:relative;left:0}.el-col-sm-1{width:4.16667%}.el-col-sm-offset-1{margin-left:4.16667%}.el-col-sm-pull-1{position:relative;right:4.16667%}.el-col-sm-push-1{position:relative;left:4.16667%}.el-col-sm-2{width:8.33333%}.el-col-sm-offset-2{margin-left:8.33333%}.el-col-sm-pull-2{position:relative;right:8.33333%}.el-col-sm-push-2{position:relative;left:8.33333%}.el-col-sm-3{width:12.5%}.el-col-sm-offset-3{margin-left:12.5%}.el-col-sm-pull-3{position:relative;right:12.5%}.el-col-sm-push-3{position:relative;left:12.5%}.el-col-sm-4{width:16.66667%}.el-col-sm-offset-4{margin-left:16.66667%}.el-col-sm-pull-4{position:relative;right:16.66667%}.el-col-sm-push-4{position:relative;left:16.66667%}.el-col-sm-5{width:20.83333%}.el-col-sm-offset-5{margin-left:20.83333%}.el-col-sm-pull-5{position:relative;right:20.83333%}.el-col-sm-push-5{position:relative;left:20.83333%}.el-col-sm-6{width:25%}.el-col-sm-offset-6{margin-left:25%}.el-col-sm-pull-6{position:relative;right:25%}.el-col-sm-push-6{position:relative;left:25%}.el-col-sm-7{width:29.16667%}.el-col-sm-offset-7{margin-left:29.16667%}.el-col-sm-pull-7{position:relative;right:29.16667%}.el-col-sm-push-7{position:relative;left:29.16667%}.el-col-sm-8{width:33.33333%}.el-col-sm-offset-8{margin-left:33.33333%}.el-col-sm-pull-8{position:relative;right:33.33333%}.el-col-sm-push-8{position:relative;left:33.33333%}.el-col-sm-9{width:37.5%}.el-col-sm-offset-9{margin-left:37.5%}.el-col-sm-pull-9{position:relative;right:37.5%}.el-col-sm-push-9{position:relative;left:37.5%}.el-col-sm-10{width:41.66667%}.el-col-sm-offset-10{margin-left:41.66667%}.el-col-sm-pull-10{position:relative;right:41.66667%}.el-col-sm-push-10{position:relative;left:41.66667%}.el-col-sm-11{width:45.83333%}.el-col-sm-offset-11{margin-left:45.83333%}.el-col-sm-pull-11{position:relative;right:45.83333%}.el-col-sm-push-11{position:relative;left:45.83333%}.el-col-sm-12{width:50%}.el-col-sm-offset-12{margin-left:50%}.el-col-sm-pull-12{position:relative;right:50%}.el-col-sm-push-12{position:relative;left:50%}.el-col-sm-13{width:54.16667%}.el-col-sm-offset-13{margin-left:54.16667%}.el-col-sm-pull-13{position:relative;right:54.16667%}.el-col-sm-push-13{position:relative;left:54.16667%}.el-col-sm-14{width:58.33333%}.el-col-sm-offset-14{margin-left:58.33333%}.el-col-sm-pull-14{position:relative;right:58.33333%}.el-col-sm-push-14{position:relative;left:58.33333%}.el-col-sm-15{width:62.5%}.el-col-sm-offset-15{margin-left:62.5%}.el-col-sm-pull-15{position:relative;right:62.5%}.el-col-sm-push-15{position:relative;left:62.5%}.el-col-sm-16{width:66.66667%}.el-col-sm-offset-16{margin-left:66.66667%}.el-col-sm-pull-16{position:relative;right:66.66667%}.el-col-sm-push-16{position:relative;left:66.66667%}.el-col-sm-17{width:70.83333%}.el-col-sm-offset-17{margin-left:70.83333%}.el-col-sm-pull-17{position:relative;right:70.83333%}.el-col-sm-push-17{position:relative;left:70.83333%}.el-col-sm-18{width:75%}.el-col-sm-offset-18{margin-left:75%}.el-col-sm-pull-18{position:relative;right:75%}.el-col-sm-push-18{position:relative;left:75%}.el-col-sm-19{width:79.16667%}.el-col-sm-offset-19{margin-left:79.16667%}.el-col-sm-pull-19{position:relative;right:79.16667%}.el-col-sm-push-19{position:relative;left:79.16667%}.el-col-sm-20{width:83.33333%}.el-col-sm-offset-20{margin-left:83.33333%}.el-col-sm-pull-20{position:relative;right:83.33333%}.el-col-sm-push-20{position:relative;left:83.33333%}.el-col-sm-21{width:87.5%}.el-col-sm-offset-21{margin-left:87.5%}.el-col-sm-pull-21{position:relative;right:87.5%}.el-col-sm-push-21{position:relative;left:87.5%}.el-col-sm-22{width:91.66667%}.el-col-sm-offset-22{margin-left:91.66667%}.el-col-sm-pull-22{position:relative;right:91.66667%}.el-col-sm-push-22{position:relative;left:91.66667%}.el-col-sm-23{width:95.83333%}.el-col-sm-offset-23{margin-left:95.83333%}.el-col-sm-pull-23{position:relative;right:95.83333%}.el-col-sm-push-23{position:relative;left:95.83333%}.el-col-sm-24{width:100%}.el-col-sm-offset-24{margin-left:100%}.el-col-sm-pull-24{position:relative;right:100%}.el-col-sm-push-24{position:relative;left:100%}}@media only screen and (min-width:992px){.el-col-md-0{display:none;width:0%}.el-col-md-offset-0{margin-left:0}.el-col-md-pull-0{position:relative;right:0}.el-col-md-push-0{position:relative;left:0}.el-col-md-1{width:4.16667%}.el-col-md-offset-1{margin-left:4.16667%}.el-col-md-pull-1{position:relative;right:4.16667%}.el-col-md-push-1{position:relative;left:4.16667%}.el-col-md-2{width:8.33333%}.el-col-md-offset-2{margin-left:8.33333%}.el-col-md-pull-2{position:relative;right:8.33333%}.el-col-md-push-2{position:relative;left:8.33333%}.el-col-md-3{width:12.5%}.el-col-md-offset-3{margin-left:12.5%}.el-col-md-pull-3{position:relative;right:12.5%}.el-col-md-push-3{position:relative;left:12.5%}.el-col-md-4{width:16.66667%}.el-col-md-offset-4{margin-left:16.66667%}.el-col-md-pull-4{position:relative;right:16.66667%}.el-col-md-push-4{position:relative;left:16.66667%}.el-col-md-5{width:20.83333%}.el-col-md-offset-5{margin-left:20.83333%}.el-col-md-pull-5{position:relative;right:20.83333%}.el-col-md-push-5{position:relative;left:20.83333%}.el-col-md-6{width:25%}.el-col-md-offset-6{margin-left:25%}.el-col-md-pull-6{position:relative;right:25%}.el-col-md-push-6{position:relative;left:25%}.el-col-md-7{width:29.16667%}.el-col-md-offset-7{margin-left:29.16667%}.el-col-md-pull-7{position:relative;right:29.16667%}.el-col-md-push-7{position:relative;left:29.16667%}.el-col-md-8{width:33.33333%}.el-col-md-offset-8{margin-left:33.33333%}.el-col-md-pull-8{position:relative;right:33.33333%}.el-col-md-push-8{position:relative;left:33.33333%}.el-col-md-9{width:37.5%}.el-col-md-offset-9{margin-left:37.5%}.el-col-md-pull-9{position:relative;right:37.5%}.el-col-md-push-9{position:relative;left:37.5%}.el-col-md-10{width:41.66667%}.el-col-md-offset-10{margin-left:41.66667%}.el-col-md-pull-10{position:relative;right:41.66667%}.el-col-md-push-10{position:relative;left:41.66667%}.el-col-md-11{width:45.83333%}.el-col-md-offset-11{margin-left:45.83333%}.el-col-md-pull-11{position:relative;right:45.83333%}.el-col-md-push-11{position:relative;left:45.83333%}.el-col-md-12{width:50%}.el-col-md-offset-12{margin-left:50%}.el-col-md-pull-12{position:relative;right:50%}.el-col-md-push-12{position:relative;left:50%}.el-col-md-13{width:54.16667%}.el-col-md-offset-13{margin-left:54.16667%}.el-col-md-pull-13{position:relative;right:54.16667%}.el-col-md-push-13{position:relative;left:54.16667%}.el-col-md-14{width:58.33333%}.el-col-md-offset-14{margin-left:58.33333%}.el-col-md-pull-14{position:relative;right:58.33333%}.el-col-md-push-14{position:relative;left:58.33333%}.el-col-md-15{width:62.5%}.el-col-md-offset-15{margin-left:62.5%}.el-col-md-pull-15{position:relative;right:62.5%}.el-col-md-push-15{position:relative;left:62.5%}.el-col-md-16{width:66.66667%}.el-col-md-offset-16{margin-left:66.66667%}.el-col-md-pull-16{position:relative;right:66.66667%}.el-col-md-push-16{position:relative;left:66.66667%}.el-col-md-17{width:70.83333%}.el-col-md-offset-17{margin-left:70.83333%}.el-col-md-pull-17{position:relative;right:70.83333%}.el-col-md-push-17{position:relative;left:70.83333%}.el-col-md-18{width:75%}.el-col-md-offset-18{margin-left:75%}.el-col-md-pull-18{position:relative;right:75%}.el-col-md-push-18{position:relative;left:75%}.el-col-md-19{width:79.16667%}.el-col-md-offset-19{margin-left:79.16667%}.el-col-md-pull-19{position:relative;right:79.16667%}.el-col-md-push-19{position:relative;left:79.16667%}.el-col-md-20{width:83.33333%}.el-col-md-offset-20{margin-left:83.33333%}.el-col-md-pull-20{position:relative;right:83.33333%}.el-col-md-push-20{position:relative;left:83.33333%}.el-col-md-21{width:87.5%}.el-col-md-offset-21{margin-left:87.5%}.el-col-md-pull-21{position:relative;right:87.5%}.el-col-md-push-21{position:relative;left:87.5%}.el-col-md-22{width:91.66667%}.el-col-md-offset-22{margin-left:91.66667%}.el-col-md-pull-22{position:relative;right:91.66667%}.el-col-md-push-22{position:relative;left:91.66667%}.el-col-md-23{width:95.83333%}.el-col-md-offset-23{margin-left:95.83333%}.el-col-md-pull-23{position:relative;right:95.83333%}.el-col-md-push-23{position:relative;left:95.83333%}.el-col-md-24{width:100%}.el-col-md-offset-24{margin-left:100%}.el-col-md-pull-24{position:relative;right:100%}.el-col-md-push-24{position:relative;left:100%}}@media only screen and (min-width:1200px){.el-col-lg-0{display:none;width:0%}.el-col-lg-offset-0{margin-left:0}.el-col-lg-pull-0{position:relative;right:0}.el-col-lg-push-0{position:relative;left:0}.el-col-lg-1{width:4.16667%}.el-col-lg-offset-1{margin-left:4.16667%}.el-col-lg-pull-1{position:relative;right:4.16667%}.el-col-lg-push-1{position:relative;left:4.16667%}.el-col-lg-2{width:8.33333%}.el-col-lg-offset-2{margin-left:8.33333%}.el-col-lg-pull-2{position:relative;right:8.33333%}.el-col-lg-push-2{position:relative;left:8.33333%}.el-col-lg-3{width:12.5%}.el-col-lg-offset-3{margin-left:12.5%}.el-col-lg-pull-3{position:relative;right:12.5%}.el-col-lg-push-3{position:relative;left:12.5%}.el-col-lg-4{width:16.66667%}.el-col-lg-offset-4{margin-left:16.66667%}.el-col-lg-pull-4{position:relative;right:16.66667%}.el-col-lg-push-4{position:relative;left:16.66667%}.el-col-lg-5{width:20.83333%}.el-col-lg-offset-5{margin-left:20.83333%}.el-col-lg-pull-5{position:relative;right:20.83333%}.el-col-lg-push-5{position:relative;left:20.83333%}.el-col-lg-6{width:25%}.el-col-lg-offset-6{margin-left:25%}.el-col-lg-pull-6{position:relative;right:25%}.el-col-lg-push-6{position:relative;left:25%}.el-col-lg-7{width:29.16667%}.el-col-lg-offset-7{margin-left:29.16667%}.el-col-lg-pull-7{position:relative;right:29.16667%}.el-col-lg-push-7{position:relative;left:29.16667%}.el-col-lg-8{width:33.33333%}.el-col-lg-offset-8{margin-left:33.33333%}.el-col-lg-pull-8{position:relative;right:33.33333%}.el-col-lg-push-8{position:relative;left:33.33333%}.el-col-lg-9{width:37.5%}.el-col-lg-offset-9{margin-left:37.5%}.el-col-lg-pull-9{position:relative;right:37.5%}.el-col-lg-push-9{position:relative;left:37.5%}.el-col-lg-10{width:41.66667%}.el-col-lg-offset-10{margin-left:41.66667%}.el-col-lg-pull-10{position:relative;right:41.66667%}.el-col-lg-push-10{position:relative;left:41.66667%}.el-col-lg-11{width:45.83333%}.el-col-lg-offset-11{margin-left:45.83333%}.el-col-lg-pull-11{position:relative;right:45.83333%}.el-col-lg-push-11{position:relative;left:45.83333%}.el-col-lg-12{width:50%}.el-col-lg-offset-12{margin-left:50%}.el-col-lg-pull-12{position:relative;right:50%}.el-col-lg-push-12{position:relative;left:50%}.el-col-lg-13{width:54.16667%}.el-col-lg-offset-13{margin-left:54.16667%}.el-col-lg-pull-13{position:relative;right:54.16667%}.el-col-lg-push-13{position:relative;left:54.16667%}.el-col-lg-14{width:58.33333%}.el-col-lg-offset-14{margin-left:58.33333%}.el-col-lg-pull-14{position:relative;right:58.33333%}.el-col-lg-push-14{position:relative;left:58.33333%}.el-col-lg-15{width:62.5%}.el-col-lg-offset-15{margin-left:62.5%}.el-col-lg-pull-15{position:relative;right:62.5%}.el-col-lg-push-15{position:relative;left:62.5%}.el-col-lg-16{width:66.66667%}.el-col-lg-offset-16{margin-left:66.66667%}.el-col-lg-pull-16{position:relative;right:66.66667%}.el-col-lg-push-16{position:relative;left:66.66667%}.el-col-lg-17{width:70.83333%}.el-col-lg-offset-17{margin-left:70.83333%}.el-col-lg-pull-17{position:relative;right:70.83333%}.el-col-lg-push-17{position:relative;left:70.83333%}.el-col-lg-18{width:75%}.el-col-lg-offset-18{margin-left:75%}.el-col-lg-pull-18{position:relative;right:75%}.el-col-lg-push-18{position:relative;left:75%}.el-col-lg-19{width:79.16667%}.el-col-lg-offset-19{margin-left:79.16667%}.el-col-lg-pull-19{position:relative;right:79.16667%}.el-col-lg-push-19{position:relative;left:79.16667%}.el-col-lg-20{width:83.33333%}.el-col-lg-offset-20{margin-left:83.33333%}.el-col-lg-pull-20{position:relative;right:83.33333%}.el-col-lg-push-20{position:relative;left:83.33333%}.el-col-lg-21{width:87.5%}.el-col-lg-offset-21{margin-left:87.5%}.el-col-lg-pull-21{position:relative;right:87.5%}.el-col-lg-push-21{position:relative;left:87.5%}.el-col-lg-22{width:91.66667%}.el-col-lg-offset-22{margin-left:91.66667%}.el-col-lg-pull-22{position:relative;right:91.66667%}.el-col-lg-push-22{position:relative;left:91.66667%}.el-col-lg-23{width:95.83333%}.el-col-lg-offset-23{margin-left:95.83333%}.el-col-lg-pull-23{position:relative;right:95.83333%}.el-col-lg-push-23{position:relative;left:95.83333%}.el-col-lg-24{width:100%}.el-col-lg-offset-24{margin-left:100%}.el-col-lg-pull-24{position:relative;right:100%}.el-col-lg-push-24{position:relative;left:100%}}@media only screen and (min-width:1920px){.el-col-xl-0{display:none;width:0%}.el-col-xl-offset-0{margin-left:0}.el-col-xl-pull-0{position:relative;right:0}.el-col-xl-push-0{position:relative;left:0}.el-col-xl-1{width:4.16667%}.el-col-xl-offset-1{margin-left:4.16667%}.el-col-xl-pull-1{position:relative;right:4.16667%}.el-col-xl-push-1{position:relative;left:4.16667%}.el-col-xl-2{width:8.33333%}.el-col-xl-offset-2{margin-left:8.33333%}.el-col-xl-pull-2{position:relative;right:8.33333%}.el-col-xl-push-2{position:relative;left:8.33333%}.el-col-xl-3{width:12.5%}.el-col-xl-offset-3{margin-left:12.5%}.el-col-xl-pull-3{position:relative;right:12.5%}.el-col-xl-push-3{position:relative;left:12.5%}.el-col-xl-4{width:16.66667%}.el-col-xl-offset-4{margin-left:16.66667%}.el-col-xl-pull-4{position:relative;right:16.66667%}.el-col-xl-push-4{position:relative;left:16.66667%}.el-col-xl-5{width:20.83333%}.el-col-xl-offset-5{margin-left:20.83333%}.el-col-xl-pull-5{position:relative;right:20.83333%}.el-col-xl-push-5{position:relative;left:20.83333%}.el-col-xl-6{width:25%}.el-col-xl-offset-6{margin-left:25%}.el-col-xl-pull-6{position:relative;right:25%}.el-col-xl-push-6{position:relative;left:25%}.el-col-xl-7{width:29.16667%}.el-col-xl-offset-7{margin-left:29.16667%}.el-col-xl-pull-7{position:relative;right:29.16667%}.el-col-xl-push-7{position:relative;left:29.16667%}.el-col-xl-8{width:33.33333%}.el-col-xl-offset-8{margin-left:33.33333%}.el-col-xl-pull-8{position:relative;right:33.33333%}.el-col-xl-push-8{position:relative;left:33.33333%}.el-col-xl-9{width:37.5%}.el-col-xl-offset-9{margin-left:37.5%}.el-col-xl-pull-9{position:relative;right:37.5%}.el-col-xl-push-9{position:relative;left:37.5%}.el-col-xl-10{width:41.66667%}.el-col-xl-offset-10{margin-left:41.66667%}.el-col-xl-pull-10{position:relative;right:41.66667%}.el-col-xl-push-10{position:relative;left:41.66667%}.el-col-xl-11{width:45.83333%}.el-col-xl-offset-11{margin-left:45.83333%}.el-col-xl-pull-11{position:relative;right:45.83333%}.el-col-xl-push-11{position:relative;left:45.83333%}.el-col-xl-12{width:50%}.el-col-xl-offset-12{margin-left:50%}.el-col-xl-pull-12{position:relative;right:50%}.el-col-xl-push-12{position:relative;left:50%}.el-col-xl-13{width:54.16667%}.el-col-xl-offset-13{margin-left:54.16667%}.el-col-xl-pull-13{position:relative;right:54.16667%}.el-col-xl-push-13{position:relative;left:54.16667%}.el-col-xl-14{width:58.33333%}.el-col-xl-offset-14{margin-left:58.33333%}.el-col-xl-pull-14{position:relative;right:58.33333%}.el-col-xl-push-14{position:relative;left:58.33333%}.el-col-xl-15{width:62.5%}.el-col-xl-offset-15{margin-left:62.5%}.el-col-xl-pull-15{position:relative;right:62.5%}.el-col-xl-push-15{position:relative;left:62.5%}.el-col-xl-16{width:66.66667%}.el-col-xl-offset-16{margin-left:66.66667%}.el-col-xl-pull-16{position:relative;right:66.66667%}.el-col-xl-push-16{position:relative;left:66.66667%}.el-col-xl-17{width:70.83333%}.el-col-xl-offset-17{margin-left:70.83333%}.el-col-xl-pull-17{position:relative;right:70.83333%}.el-col-xl-push-17{position:relative;left:70.83333%}.el-col-xl-18{width:75%}.el-col-xl-offset-18{margin-left:75%}.el-col-xl-pull-18{position:relative;right:75%}.el-col-xl-push-18{position:relative;left:75%}.el-col-xl-19{width:79.16667%}.el-col-xl-offset-19{margin-left:79.16667%}.el-col-xl-pull-19{position:relative;right:79.16667%}.el-col-xl-push-19{position:relative;left:79.16667%}.el-col-xl-20{width:83.33333%}.el-col-xl-offset-20{margin-left:83.33333%}.el-col-xl-pull-20{position:relative;right:83.33333%}.el-col-xl-push-20{position:relative;left:83.33333%}.el-col-xl-21{width:87.5%}.el-col-xl-offset-21{margin-left:87.5%}.el-col-xl-pull-21{position:relative;right:87.5%}.el-col-xl-push-21{position:relative;left:87.5%}.el-col-xl-22{width:91.66667%}.el-col-xl-offset-22{margin-left:91.66667%}.el-col-xl-pull-22{position:relative;right:91.66667%}.el-col-xl-push-22{position:relative;left:91.66667%}.el-col-xl-23{width:95.83333%}.el-col-xl-offset-23{margin-left:95.83333%}.el-col-xl-pull-23{position:relative;right:95.83333%}.el-col-xl-push-23{position:relative;left:95.83333%}.el-col-xl-24{width:100%}.el-col-xl-offset-24{margin-left:100%}.el-col-xl-pull-24{position:relative;right:100%}.el-col-xl-push-24{position:relative;left:100%}}@-webkit-keyframes progress{0%{background-position:0 0}100%{background-position:32px 0}}.el-upload{display:inline-block;text-align:center;cursor:pointer;outline:0}.el-upload__input{display:none}.el-upload__tip{font-size:12px;color:#606266;margin-top:7px}.el-upload iframe{position:absolute;z-index:-1;top:0;left:0;opacity:0;filter:alpha(opacity=0)}.el-upload--picture-card{background-color:#fbfdff;border:1px dashed #c0ccda;border-radius:6px;box-sizing:border-box;width:148px;height:148px;line-height:146px;vertical-align:top}.el-upload--picture-card i{font-size:28px;color:#8c939d}.el-upload--picture-card:hover,.el-upload:focus{border-color:#002FA7;color:#002FA7}.el-upload:focus .el-upload-dragger{border-color:#002FA7}.el-upload-dragger{background-color:#fff;border:1px dashed #d9d9d9;border-radius:6px;box-sizing:border-box;width:360px;height:180px;text-align:center;position:relative;overflow:hidden}.el-upload-dragger .el-icon-upload{font-size:67px;color:#3F3F3F;margin:40px 0 16px;line-height:50px}.el-upload-dragger+.el-upload__tip{text-align:center}.el-upload-dragger~.el-upload__files{border-top:1px solid #BBB;margin-top:7px;padding-top:5px}.el-upload-dragger .el-upload__text{color:#606266;font-size:14px;text-align:center}.el-upload-dragger .el-upload__text em{color:#002FA7;font-style:normal}.el-upload-dragger:hover{border-color:#002FA7}.el-upload-dragger.is-dragover{background-color:rgba(32,159,255,.06);border:2px dashed #002FA7}.el-upload-list{margin:0;padding:0;list-style:none}.el-upload-list__item{-webkit-transition:all .5s cubic-bezier(.55,0,.1,1);transition:all .5s cubic-bezier(.55,0,.1,1);font-size:14px;color:#606266;line-height:1.8;margin-top:5px;position:relative;-webkit-box-sizing:border-box;box-sizing:border-box;border-radius:4px;width:100%}.el-upload-list__item .el-progress{position:absolute;top:20px;width:100%}.el-upload-list__item .el-progress__text{position:absolute;right:0;top:-13px}.el-upload-list__item .el-progress-bar{margin-right:0;padding-right:0}.el-upload-list__item:first-child{margin-top:10px}.el-upload-list__item .el-icon-upload-success{color:#67C23A}.el-upload-list__item .el-icon-close{display:none;position:absolute;top:5px;right:5px;cursor:pointer;opacity:.75;color:#606266}.el-upload-list__item .el-icon-close:hover{opacity:1}.el-upload-list__item .el-icon-close-tip{display:none;position:absolute;top:5px;right:5px;font-size:12px;cursor:pointer;opacity:1;color:#002FA7}.el-upload-list__item:hover{background-color:#F5F7FA}.el-upload-list__item:hover .el-icon-close{display:inline-block}.el-upload-list__item:hover .el-progress__text{display:none}.el-upload-list__item.is-success .el-upload-list__item-status-label{display:block}.el-upload-list__item.is-success .el-upload-list__item-name:focus,.el-upload-list__item.is-success .el-upload-list__item-name:hover{color:#002FA7;cursor:pointer}.el-upload-list__item.is-success:focus:not(:hover) .el-icon-close-tip{display:inline-block}.el-upload-list__item.is-success:active .el-icon-close-tip,.el-upload-list__item.is-success:focus .el-upload-list__item-status-label,.el-upload-list__item.is-success:hover .el-upload-list__item-status-label,.el-upload-list__item.is-success:not(.focusing):focus .el-icon-close-tip{display:none}.el-upload-list.is-disabled .el-upload-list__item:hover .el-upload-list__item-status-label{display:block}.el-upload-list__item-name{color:#606266;display:block;margin-right:40px;overflow:hidden;padding-left:4px;text-overflow:ellipsis;-webkit-transition:color .3s;transition:color .3s;white-space:nowrap}.el-upload-list__item-name [class^=el-icon]{height:100%;margin-right:7px;color:#909399;line-height:inherit}.el-upload-list__item-status-label{position:absolute;right:5px;top:0;line-height:inherit;display:none}.el-upload-list__item-delete{position:absolute;right:10px;top:0;font-size:12px;color:#606266;display:none}.el-upload-list__item-delete:hover{color:#002FA7}.el-upload-list--picture-card{margin:0;display:inline;vertical-align:top}.el-upload-list--picture-card .el-upload-list__item{overflow:hidden;background-color:#fff;border:1px solid #c0ccda;border-radius:6px;-webkit-box-sizing:border-box;box-sizing:border-box;width:148px;height:148px;margin:0 8px 8px 0;display:inline-block}.el-upload-list--picture-card .el-upload-list__item .el-icon-check,.el-upload-list--picture-card .el-upload-list__item .el-icon-circle-check{color:#FFF}.el-upload-list--picture-card .el-upload-list__item .el-icon-close,.el-upload-list--picture-card .el-upload-list__item:hover .el-upload-list__item-status-label{display:none}.el-upload-list--picture-card .el-upload-list__item:hover .el-progress__text{display:block}.el-upload-list--picture-card .el-upload-list__item-name{display:none}.el-upload-list--picture-card .el-upload-list__item-thumbnail{width:100%;height:100%}.el-upload-list--picture-card .el-upload-list__item-status-label{position:absolute;right:-15px;top:-6px;width:40px;height:24px;background:#13ce66;text-align:center;-webkit-transform:rotate(45deg);transform:rotate(45deg);-webkit-box-shadow:0 0 1pc 1px rgba(0,0,0,.2);box-shadow:0 0 1pc 1px rgba(0,0,0,.2)}.el-upload-list--picture-card .el-upload-list__item-status-label i{font-size:12px;margin-top:11px;-webkit-transform:rotate(-45deg);transform:rotate(-45deg)}.el-upload-list--picture-card .el-upload-list__item-actions{position:absolute;width:100%;height:100%;left:0;top:0;cursor:default;text-align:center;color:#fff;opacity:0;font-size:20px;background-color:rgba(0,0,0,.5);-webkit-transition:opacity .3s;transition:opacity .3s}.el-upload-list--picture-card .el-upload-list__item-actions::after{display:inline-block;content:"";height:100%;vertical-align:middle}.el-upload-list--picture-card .el-upload-list__item-actions span{display:none;cursor:pointer}.el-upload-list--picture-card .el-upload-list__item-actions span+span{margin-left:15px}.el-upload-list--picture-card .el-upload-list__item-actions .el-upload-list__item-delete{position:static;font-size:inherit;color:inherit}.el-upload-list--picture-card .el-upload-list__item-actions:hover{opacity:1}.el-upload-list--picture-card .el-upload-list__item-actions:hover span{display:inline-block}.el-upload-list--picture-card .el-progress{top:50%;left:50%;-webkit-transform:translate(-50%,-50%);transform:translate(-50%,-50%);bottom:auto;width:126px}.el-upload-list--picture-card .el-progress .el-progress__text{top:50%}.el-upload-list--picture .el-upload-list__item{overflow:hidden;z-index:0;background-color:#fff;border:1px solid #c0ccda;border-radius:6px;-webkit-box-sizing:border-box;box-sizing:border-box;margin-top:10px;padding:10px 10px 10px 90px;height:92px}.el-upload-list--picture .el-upload-list__item .el-icon-check,.el-upload-list--picture .el-upload-list__item .el-icon-circle-check{color:#FFF}.el-upload-list--picture .el-upload-list__item:hover .el-upload-list__item-status-label{background:0 0;-webkit-box-shadow:none;box-shadow:none;top:-2px;right:-12px}.el-upload-list--picture .el-upload-list__item:hover .el-progress__text{display:block}.el-upload-list--picture .el-upload-list__item.is-success .el-upload-list__item-name{line-height:70px;margin-top:0}.el-upload-list--picture .el-upload-list__item.is-success .el-upload-list__item-name i{display:none}.el-upload-list--picture .el-upload-list__item-thumbnail{vertical-align:middle;display:inline-block;width:70px;height:70px;float:left;position:relative;z-index:1;margin-left:-80px;background-color:#FFF}.el-upload-list--picture .el-upload-list__item-name{display:block;margin-top:20px}.el-upload-list--picture .el-upload-list__item-name i{font-size:70px;line-height:1;position:absolute;left:9px;top:10px}.el-upload-list--picture .el-upload-list__item-status-label{position:absolute;right:-17px;top:-7px;width:46px;height:26px;background:#13ce66;text-align:center;-webkit-transform:rotate(45deg);transform:rotate(45deg);-webkit-box-shadow:0 1px 1px #ccc;box-shadow:0 1px 1px #ccc}.el-upload-list--picture .el-upload-list__item-status-label i{font-size:12px;margin-top:12px;-webkit-transform:rotate(-45deg);transform:rotate(-45deg)}.el-upload-list--picture .el-progress{position:relative;top:-7px}.el-upload-cover{position:absolute;left:0;top:0;width:100%;height:100%;overflow:hidden;z-index:10;cursor:default}.el-upload-cover::after{display:inline-block;height:100%;vertical-align:middle}.el-upload-cover img{display:block;width:100%;height:100%}.el-upload-cover__label{position:absolute;right:-15px;top:-6px;width:40px;height:24px;background:#13ce66;text-align:center;-webkit-transform:rotate(45deg);transform:rotate(45deg);-webkit-box-shadow:0 0 1pc 1px rgba(0,0,0,.2);box-shadow:0 0 1pc 1px rgba(0,0,0,.2)}.el-upload-cover__label i{font-size:12px;margin-top:11px;-webkit-transform:rotate(-45deg);transform:rotate(-45deg);color:#fff}.el-upload-cover__progress{display:inline-block;vertical-align:middle;position:static;width:243px}.el-upload-cover__progress+.el-upload__inner{opacity:0}.el-upload-cover__content{position:absolute;top:0;left:0;width:100%;height:100%}.el-upload-cover__interact{position:absolute;bottom:0;left:0;width:100%;height:100%;background-color:rgba(0,0,0,.72);text-align:center}.el-upload-cover__interact .btn{display:inline-block;color:#FFF;font-size:14px;cursor:pointer;vertical-align:middle;-webkit-transition:opacity .3s cubic-bezier(.23,1,.32,1),-webkit-transform .3s cubic-bezier(.23,1,.32,1);transition:opacity .3s cubic-bezier(.23,1,.32,1),-webkit-transform .3s cubic-bezier(.23,1,.32,1);transition:transform .3s cubic-bezier(.23,1,.32,1),opacity .3s cubic-bezier(.23,1,.32,1);transition:transform .3s cubic-bezier(.23,1,.32,1),opacity .3s cubic-bezier(.23,1,.32,1),-webkit-transform .3s cubic-bezier(.23,1,.32,1);margin-top:60px}.el-upload-cover__interact .btn span{opacity:0;-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.el-upload-cover__interact .btn:not(:first-child){margin-left:35px}.el-upload-cover__interact .btn:hover{-webkit-transform:translateY(-13px);transform:translateY(-13px)}.el-upload-cover__interact .btn:hover span{opacity:1}.el-upload-cover__interact .btn i{color:#FFF;display:block;font-size:24px;line-height:inherit;margin:0 auto 5px}.el-upload-cover__title{position:absolute;bottom:0;left:0;background-color:#FFF;height:36px;width:100%;overflow:hidden;text-overflow:ellipsis;white-space:nowrap;font-weight:400;text-align:left;padding:0 10px;margin:0;line-height:36px;font-size:14px;color:#303133}.el-upload-cover+.el-upload__inner{opacity:0;position:relative;z-index:1}.el-progress{position:relative;line-height:1}.el-progress__text{font-size:14px;color:#606266;display:inline-block;vertical-align:middle;margin-left:10px;line-height:1}.el-progress__text i{vertical-align:middle;display:block}.el-progress--circle,.el-progress--dashboard{display:inline-block}.el-progress--circle .el-progress__text,.el-progress--dashboard .el-progress__text{position:absolute;top:50%;left:0;width:100%;text-align:center;margin:0;-webkit-transform:translate(0,-50%);transform:translate(0,-50%)}.el-progress--circle .el-progress__text i,.el-progress--dashboard .el-progress__text i{vertical-align:middle;display:inline-block}.el-progress--without-text .el-progress__text{display:none}.el-progress--without-text .el-progress-bar{padding-right:0;margin-right:0;display:block}.el-progress-bar,.el-progress-bar__inner::after,.el-progress-bar__innerText,.el-spinner{display:inline-block;vertical-align:middle}.el-progress--text-inside .el-progress-bar{padding-right:0;margin-right:0}.el-progress.is-success .el-progress-bar__inner{background-color:#67C23A}.el-progress.is-success .el-progress__text{color:#67C23A}.el-progress.is-warning .el-progress-bar__inner{background-color:#E6A23C}.el-progress.is-warning .el-progress__text{color:#E6A23C}.el-progress.is-exception .el-progress-bar__inner{background-color:#F56C6C}.el-progress.is-exception .el-progress__text{color:#F56C6C}.el-progress-bar{padding-right:50px;width:100%;margin-right:-55px;-webkit-box-sizing:border-box;box-sizing:border-box}.el-progress-bar__outer{height:6px;border-radius:100px;background-color:#EBEEF5;overflow:hidden;position:relative;vertical-align:middle}.el-progress-bar__inner{position:absolute;left:0;top:0;height:100%;background-color:#002FA7;text-align:right;border-radius:100px;line-height:1;white-space:nowrap;-webkit-transition:width .6s ease;transition:width .6s ease}.el-card,.el-message{border-radius:4px;overflow:hidden}.el-progress-bar__inner::after{height:100%}.el-progress-bar__innerText{color:#FFF;font-size:12px;margin:0 5px}@keyframes progress{0%{background-position:0 0}100%{background-position:32px 0}}.el-time-spinner{width:100%;white-space:nowrap}.el-spinner-inner{-webkit-animation:rotate 2s linear infinite;animation:rotate 2s linear infinite;width:50px;height:50px}.el-spinner-inner .path{stroke:#ececec;stroke-linecap:round;-webkit-animation:dash 1.5s ease-in-out infinite;animation:dash 1.5s ease-in-out infinite}@-webkit-keyframes rotate{100%{-webkit-transform:rotate(360deg);transform:rotate(360deg)}}@keyframes rotate{100%{-webkit-transform:rotate(360deg);transform:rotate(360deg)}}@-webkit-keyframes dash{0%{stroke-dasharray:1,150;stroke-dashoffset:0}50%{stroke-dasharray:90,150;stroke-dashoffset:-35}100%{stroke-dasharray:90,150;stroke-dashoffset:-124}}@keyframes dash{0%{stroke-dasharray:1,150;stroke-dashoffset:0}50%{stroke-dasharray:90,150;stroke-dashoffset:-35}100%{stroke-dasharray:90,150;stroke-dashoffset:-124}}.el-message{min-width:380px;-webkit-box-sizing:border-box;box-sizing:border-box;border-width:1px;border-style:solid;border-color:#EBEEF5;position:fixed;left:50%;top:20px;-webkit-transform:translateX(-50%);transform:translateX(-50%);background-color:#edf2fc;-webkit-transition:opacity .3s,top .4s,-webkit-transform .4s;transition:opacity .3s,top .4s,-webkit-transform .4s;transition:opacity .3s,transform .4s,top .4s;transition:opacity .3s,transform .4s,top .4s,-webkit-transform .4s;padding:15px 15px 15px 20px;display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-align:center;-ms-flex-align:center;align-items:center}.el-message.is-center{-webkit-box-pack:center;-ms-flex-pack:center;justify-content:center}.el-message.is-closable .el-message__content{padding-right:16px}.el-message p{margin:0}.el-message--info .el-message__content{color:#909399}.el-message--success{background-color:#f0f9eb;border-color:#e1f3d8}.el-message--success .el-message__content{color:#67C23A}.el-message--warning{background-color:#fdf6ec;border-color:#faecd8}.el-message--warning .el-message__content{color:#E6A23C}.el-message--error{background-color:#fef0f0;border-color:#fde2e2}.el-message--error .el-message__content{color:#F56C6C}.el-message__icon{margin-right:10px}.el-message__content{padding:0;font-size:14px;line-height:1}.el-message__closeBtn{position:absolute;top:50%;right:15px;-webkit-transform:translateY(-50%);transform:translateY(-50%);cursor:pointer;color:#3F3F3F;font-size:16px}.el-message__closeBtn:hover{color:#909399}.el-message .el-icon-success{color:#67C23A}.el-message .el-icon-error{color:#F56C6C}.el-message .el-icon-info{color:#909399}.el-message .el-icon-warning{color:#E6A23C}.el-message-fade-enter,.el-message-fade-leave-active{opacity:0;-webkit-transform:translate(-50%,-100%);transform:translate(-50%,-100%)}.el-badge{position:relative;vertical-align:middle;display:inline-block}.el-badge__content{background-color:#F56C6C;border-radius:10px;color:#FFF;display:inline-block;font-size:12px;height:18px;line-height:18px;padding:0 6px;text-align:center;white-space:nowrap;border:1px solid #FFF}.el-badge__content.is-fixed{position:absolute;top:0;right:10px;-webkit-transform:translateY(-50%) translateX(100%);transform:translateY(-50%) translateX(100%)}.el-rate__icon,.el-rate__item{position:relative;display:inline-block}.el-badge__content.is-fixed.is-dot{right:5px}.el-badge__content.is-dot{height:8px;width:8px;padding:0;right:0;border-radius:50%}.el-badge__content--primary{background-color:#002FA7}.el-badge__content--success{background-color:#67C23A}.el-badge__content--warning{background-color:#E6A23C}.el-badge__content--info{background-color:#909399}.el-badge__content--danger{background-color:#F56C6C}.el-card{border:1px solid #EBEEF5;background-color:#FFF;color:#303133;-webkit-transition:.3s;transition:.3s}.el-card.is-always-shadow,.el-card.is-hover-shadow:focus,.el-card.is-hover-shadow:hover{-webkit-box-shadow:0 2px 12px 0 rgba(0,0,0,.1);box-shadow:0 2px 12px 0 rgba(0,0,0,.1)}.el-card__header{padding:18px 20px;border-bottom:1px solid #EBEEF5;-webkit-box-sizing:border-box;box-sizing:border-box}.el-card__body{padding:20px}.el-rate{height:20px;line-height:1}.el-rate__item{font-size:0;vertical-align:middle}.el-rate__icon{font-size:18px;margin-right:6px;color:#3F3F3F;-webkit-transition:.3s;transition:.3s}.el-rate__decimal,.el-rate__icon .path2{position:absolute;top:0;left:0}.el-rate__icon.hover{-webkit-transform:scale(1.15);transform:scale(1.15)}.el-rate__decimal{display:inline-block;overflow:hidden}.el-step.is-vertical,.el-steps{display:-webkit-box;display:-ms-flexbox}.el-rate__text{font-size:14px;vertical-align:middle}.el-steps{display:flex}.el-steps--simple{padding:13px 8%;border-radius:4px;background:#F5F7FA}.el-steps--horizontal{white-space:nowrap}.el-steps--vertical{height:100%;-webkit-box-orient:vertical;-webkit-box-direction:normal;-ms-flex-flow:column;flex-flow:column}.el-step{position:relative;-ms-flex-negative:1;flex-shrink:1}.el-step:last-of-type .el-step__line{display:none}.el-step:last-of-type.is-flex{-ms-flex-preferred-size:auto!important;flex-basis:auto!important;-ms-flex-negative:0;flex-shrink:0;-webkit-box-flex:0;-ms-flex-positive:0;flex-grow:0}.el-step:last-of-type .el-step__description,.el-step:last-of-type .el-step__main{padding-right:0}.el-step__head{position:relative;width:100%}.el-step__head.is-process{color:#303133;border-color:#303133}.el-step__head.is-wait{color:#3F3F3F;border-color:#3F3F3F}.el-step__head.is-success{color:#67C23A;border-color:#67C23A}.el-step__head.is-error{color:#F56C6C;border-color:#F56C6C}.el-step__head.is-finish{color:#002FA7;border-color:#002FA7}.el-step__icon{position:relative;z-index:1;display:-webkit-inline-box;display:-ms-inline-flexbox;display:inline-flex;-webkit-box-pack:center;-ms-flex-pack:center;justify-content:center;-webkit-box-align:center;-ms-flex-align:center;align-items:center;width:24px;height:24px;font-size:14px;-webkit-box-sizing:border-box;box-sizing:border-box;background:#FFF;-webkit-transition:.15s ease-out;transition:.15s ease-out}.el-step__icon.is-text{border-radius:50%;border:2px solid;border-color:inherit}.el-step__icon.is-icon{width:40px}.el-step__icon-inner{display:inline-block;user-select:none;text-align:center;font-weight:700;line-height:1;color:inherit}.el-step__icon-inner[class*=el-icon]:not(.is-status){font-size:25px;font-weight:400}.el-step__icon-inner.is-status{-webkit-transform:translateY(1px);transform:translateY(1px)}.el-step__line{position:absolute;border-color:inherit;background-color:#3F3F3F}.el-step__line-inner{display:block;border-width:1px;border-style:solid;border-color:inherit;-webkit-transition:.15s ease-out;transition:.15s ease-out;-webkit-box-sizing:border-box;box-sizing:border-box;width:0;height:0}.el-step__main{white-space:normal;text-align:left}.el-step__title{font-size:16px;line-height:38px}.el-step__title.is-process{font-weight:700;color:#303133}.el-step__title.is-wait{color:#3F3F3F}.el-step__title.is-success{color:#67C23A}.el-step__title.is-error{color:#F56C6C}.el-step__title.is-finish{color:#002FA7}.el-step__description{padding-right:10%;margin-top:-5px;font-size:12px;line-height:20px;font-weight:400}.el-step__description.is-process{color:#303133}.el-step__description.is-wait{color:#3F3F3F}.el-step__description.is-success{color:#67C23A}.el-step__description.is-error{color:#F56C6C}.el-step__description.is-finish{color:#002FA7}.el-step.is-horizontal{display:inline-block}.el-step.is-horizontal .el-step__line{height:2px;top:11px;left:0;right:0}.el-step.is-vertical{display:flex}.el-step.is-vertical .el-step__head{-webkit-box-flex:0;-ms-flex-positive:0;flex-grow:0;width:24px}.el-step.is-vertical .el-step__main{padding-left:10px;-webkit-box-flex:1;-ms-flex-positive:1;flex-grow:1}.el-step.is-vertical .el-step__title{line-height:24px;padding-bottom:8px}.el-step.is-vertical .el-step__line{width:2px;top:0;bottom:0;left:11px}.el-step.is-vertical .el-step__icon.is-icon{width:24px}.el-step.is-center .el-step__head,.el-step.is-center .el-step__main{text-align:center}.el-step.is-center .el-step__description{padding-left:20%;padding-right:20%}.el-step.is-center .el-step__line{left:50%;right:-50%}.el-step.is-simple{display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-align:center;-ms-flex-align:center;align-items:center}.el-step.is-simple .el-step__head{width:auto;font-size:0;padding-right:10px}.el-step.is-simple .el-step__icon{background:0 0;width:16px;height:16px;font-size:12px}.el-step.is-simple .el-step__icon-inner[class*=el-icon]:not(.is-status){font-size:18px}.el-step.is-simple .el-step__icon-inner.is-status{-webkit-transform:scale(.8) translateY(1px);transform:scale(.8) translateY(1px)}.el-step.is-simple .el-step__main{position:relative;display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-align:stretch;-ms-flex-align:stretch;align-items:stretch;-webkit-box-flex:1;-ms-flex-positive:1;flex-grow:1}.el-step.is-simple .el-step__title{font-size:16px;line-height:20px}.el-step.is-simple:not(:last-of-type) .el-step__title{max-width:50%;word-break:break-all}.el-step.is-simple .el-step__arrow{-webkit-box-flex:1;-ms-flex-positive:1;flex-grow:1;display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-align:center;-ms-flex-align:center;align-items:center;-webkit-box-pack:center;-ms-flex-pack:center;justify-content:center}.el-step.is-simple .el-step__arrow::after,.el-step.is-simple .el-step__arrow::before{content:'';display:inline-block;position:absolute;height:15px;width:1px;background:#3F3F3F}.el-step.is-simple .el-step__arrow::before{-webkit-transform:rotate(-45deg) translateY(-4px);transform:rotate(-45deg) translateY(-4px);-webkit-transform-origin:0 0;transform-origin:0 0}.el-step.is-simple .el-step__arrow::after{-webkit-transform:rotate(45deg) translateY(4px);transform:rotate(45deg) translateY(4px);-webkit-transform-origin:100% 100%;transform-origin:100% 100%}.el-step.is-simple:last-of-type .el-step__arrow{display:none}.el-carousel{position:relative}.el-carousel--horizontal{overflow-x:hidden}.el-carousel--vertical{overflow-y:hidden}.el-carousel__container{position:relative;height:300px}.el-carousel__arrow{border:none;outline:0;padding:0;margin:0;height:36px;width:36px;cursor:pointer;-webkit-transition:.3s;transition:.3s;border-radius:50%;background-color:rgba(31,45,61,.11);color:#FFF;position:absolute;top:50%;z-index:10;-webkit-transform:translateY(-50%);transform:translateY(-50%);text-align:center;font-size:12px}.el-carousel__arrow--left{left:16px}.el-carousel__arrow--right{right:16px}.el-carousel__arrow:hover{background-color:rgba(31,45,61,.23)}.el-carousel__arrow i{cursor:pointer}.el-carousel__indicators{position:absolute;list-style:none;margin:0;padding:0;z-index:2}.el-carousel__indicators--horizontal{bottom:0;left:50%;-webkit-transform:translateX(-50%);transform:translateX(-50%)}.el-carousel__indicators--vertical{right:0;top:50%;-webkit-transform:translateY(-50%);transform:translateY(-50%)}.el-carousel__indicators--outside{bottom:26px;text-align:center;position:static;-webkit-transform:none;transform:none}.el-carousel__indicators--outside .el-carousel__indicator:hover button{opacity:.64}.el-carousel__indicators--outside button{background-color:#3F3F3F;opacity:.24}.el-carousel__indicators--labels{left:0;right:0;-webkit-transform:none;transform:none;text-align:center}.el-carousel__indicators--labels .el-carousel__button{height:auto;width:auto;padding:2px 18px;font-size:12px}.el-carousel__indicators--labels .el-carousel__indicator{padding:6px 4px}.el-carousel__indicator{background-color:transparent;cursor:pointer}.el-carousel__indicator:hover button{opacity:.72}.el-carousel__indicator--horizontal{display:inline-block;padding:12px 4px}.el-carousel__indicator--vertical{padding:4px 12px}.el-carousel__indicator--vertical .el-carousel__button{width:2px;height:15px}.el-carousel__indicator.is-active button{opacity:1}.el-carousel__button{display:block;opacity:.48;width:30px;height:2px;background-color:#FFF;border:none;outline:0;padding:0;margin:0;cursor:pointer;-webkit-transition:.3s;transition:.3s}.el-carousel__item,.el-carousel__mask{height:100%;top:0;left:0;position:absolute}.carousel-arrow-left-enter,.carousel-arrow-left-leave-active{-webkit-transform:translateY(-50%) translateX(-10px);transform:translateY(-50%) translateX(-10px);opacity:0}.carousel-arrow-right-enter,.carousel-arrow-right-leave-active{-webkit-transform:translateY(-50%) translateX(10px);transform:translateY(-50%) translateX(10px);opacity:0}.el-carousel__item{width:100%;display:inline-block;overflow:hidden;z-index:0}.el-carousel__item.is-active{z-index:2}.el-carousel__item.is-animating{-webkit-transition:-webkit-transform .4s ease-in-out;transition:-webkit-transform .4s ease-in-out;transition:transform .4s ease-in-out;transition:transform .4s ease-in-out,-webkit-transform .4s ease-in-out}.el-carousel__item--card{width:50%;-webkit-transition:-webkit-transform .4s ease-in-out;transition:-webkit-transform .4s ease-in-out;transition:transform .4s ease-in-out;transition:transform .4s ease-in-out,-webkit-transform .4s ease-in-out}.el-carousel__item--card.is-in-stage{cursor:pointer;z-index:1}.el-carousel__item--card.is-in-stage.is-hover .el-carousel__mask,.el-carousel__item--card.is-in-stage:hover .el-carousel__mask{opacity:.12}.el-carousel__item--card.is-active{z-index:2}.el-carousel__mask{width:100%;background-color:#FFF;opacity:.24;-webkit-transition:.2s;transition:.2s}.el-fade-in-enter,.el-fade-in-leave-active,.el-fade-in-linear-enter,.el-fade-in-linear-leave,.el-fade-in-linear-leave-active,.fade-in-linear-enter,.fade-in-linear-leave,.fade-in-linear-leave-active{opacity:0}.fade-in-linear-enter-active,.fade-in-linear-leave-active{-webkit-transition:opacity .2s linear;transition:opacity .2s linear}.el-fade-in-linear-enter-active,.el-fade-in-linear-leave-active{-webkit-transition:opacity .2s linear;transition:opacity .2s linear}.el-fade-in-enter-active,.el-fade-in-leave-active{-webkit-transition:all .3s cubic-bezier(.55,0,.1,1);transition:all .3s cubic-bezier(.55,0,.1,1)}.el-zoom-in-center-enter-active,.el-zoom-in-center-leave-active{-webkit-transition:all .3s cubic-bezier(.55,0,.1,1);transition:all .3s cubic-bezier(.55,0,.1,1)}.el-zoom-in-center-enter,.el-zoom-in-center-leave-active{opacity:0;-webkit-transform:scaleX(0);transform:scaleX(0)}.el-zoom-in-top-enter-active,.el-zoom-in-top-leave-active{opacity:1;-webkit-transform:scaleY(1);transform:scaleY(1);-webkit-transition:opacity .3s cubic-bezier(.23,1,.32,1),-webkit-transform .3s cubic-bezier(.23,1,.32,1);transition:opacity .3s cubic-bezier(.23,1,.32,1),-webkit-transform .3s cubic-bezier(.23,1,.32,1);transition:transform .3s cubic-bezier(.23,1,.32,1),opacity .3s cubic-bezier(.23,1,.32,1);transition:transform .3s cubic-bezier(.23,1,.32,1),opacity .3s cubic-bezier(.23,1,.32,1),-webkit-transform .3s cubic-bezier(.23,1,.32,1);-webkit-transform-origin:center top;transform-origin:center top}.el-zoom-in-top-enter,.el-zoom-in-top-leave-active{opacity:0;-webkit-transform:scaleY(0);transform:scaleY(0)}.el-zoom-in-bottom-enter-active,.el-zoom-in-bottom-leave-active{opacity:1;-webkit-transform:scaleY(1);transform:scaleY(1);-webkit-transition:opacity .3s cubic-bezier(.23,1,.32,1),-webkit-transform .3s cubic-bezier(.23,1,.32,1);transition:opacity .3s cubic-bezier(.23,1,.32,1),-webkit-transform .3s cubic-bezier(.23,1,.32,1);transition:transform .3s cubic-bezier(.23,1,.32,1),opacity .3s cubic-bezier(.23,1,.32,1);transition:transform .3s cubic-bezier(.23,1,.32,1),opacity .3s cubic-bezier(.23,1,.32,1),-webkit-transform .3s cubic-bezier(.23,1,.32,1);-webkit-transform-origin:center bottom;transform-origin:center bottom}.el-zoom-in-bottom-enter,.el-zoom-in-bottom-leave-active{opacity:0;-webkit-transform:scaleY(0);transform:scaleY(0)}.el-zoom-in-left-enter-active,.el-zoom-in-left-leave-active{opacity:1;-webkit-transform:scale(1,1);transform:scale(1,1);-webkit-transition:opacity .3s cubic-bezier(.23,1,.32,1),-webkit-transform .3s cubic-bezier(.23,1,.32,1);transition:opacity .3s cubic-bezier(.23,1,.32,1),-webkit-transform .3s cubic-bezier(.23,1,.32,1);transition:transform .3s cubic-bezier(.23,1,.32,1),opacity .3s cubic-bezier(.23,1,.32,1);transition:transform .3s cubic-bezier(.23,1,.32,1),opacity .3s cubic-bezier(.23,1,.32,1),-webkit-transform .3s cubic-bezier(.23,1,.32,1);-webkit-transform-origin:top left;transform-origin:top left}.el-zoom-in-left-enter,.el-zoom-in-left-leave-active{opacity:0;-webkit-transform:scale(.45,.45);transform:scale(.45,.45)}.collapse-transition{-webkit-transition:.3s height ease-in-out,.3s padding-top ease-in-out,.3s padding-bottom ease-in-out;transition:.3s height ease-in-out,.3s padding-top ease-in-out,.3s padding-bottom ease-in-out}.horizontal-collapse-transition{-webkit-transition:.3s width ease-in-out,.3s padding-left ease-in-out,.3s padding-right ease-in-out;transition:.3s width ease-in-out,.3s padding-left ease-in-out,.3s padding-right ease-in-out}.el-list-enter-active,.el-list-leave-active{-webkit-transition:all 1s;transition:all 1s}.el-list-enter,.el-list-leave-active{opacity:0;-webkit-transform:translateY(-30px);transform:translateY(-30px)}.el-opacity-transition{-webkit-transition:opacity .3s cubic-bezier(.55,0,.1,1);transition:opacity .3s cubic-bezier(.55,0,.1,1)}.el-collapse{border-top:1px solid #EBEEF5;border-bottom:1px solid #EBEEF5}.el-collapse-item.is-disabled .el-collapse-item__header{color:#bbb;cursor:not-allowed}.el-collapse-item__header{display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-align:center;-ms-flex-align:center;align-items:center;height:48px;line-height:48px;background-color:#FFF;color:#303133;cursor:pointer;border-bottom:1px solid #EBEEF5;font-size:13px;font-weight:500;-webkit-transition:border-bottom-color .3s;transition:border-bottom-color .3s;outline:0}.el-collapse-item__arrow{margin:0 8px 0 auto;transition:-webkit-transform .3s;transition:transform .3s;transition:transform .3s,-webkit-transform .3s;font-weight:300}.el-collapse-item__arrow.is-active{-webkit-transform:rotate(90deg);transform:rotate(90deg)}.el-collapse-item__header.focusing:focus:not(:hover){color:#002FA7}.el-collapse-item__header.is-active{border-bottom-color:transparent}.el-collapse-item__wrap{will-change:height;background-color:#FFF;overflow:hidden;-webkit-box-sizing:border-box;box-sizing:border-box;border-bottom:1px solid #EBEEF5}.el-cascader__tags,.el-tag{-webkit-box-sizing:border-box}.el-collapse-item__content{padding-bottom:25px;font-size:13px;color:#303133;line-height:1.769230769230769}.el-collapse-item:last-child{margin-bottom:-1px}.el-popper .popper__arrow,.el-popper .popper__arrow::after{position:absolute;display:block;width:0;height:0;border-color:transparent;border-style:solid}.el-popper .popper__arrow{border-width:6px;-webkit-filter:drop-shadow(0 2px 12px rgba(0, 0, 0, .03));filter:drop-shadow(0 2px 12px rgba(0, 0, 0, .03))}.el-popper .popper__arrow::after{content:" ";border-width:6px}.el-popper[x-placement^=top]{margin-bottom:12px}.el-popper[x-placement^=top] .popper__arrow{bottom:-6px;left:50%;margin-right:3px;border-top-color:#EBEEF5;border-bottom-width:0}.el-popper[x-placement^=top] .popper__arrow::after{bottom:1px;margin-left:-6px;border-top-color:#FFF;border-bottom-width:0}.el-popper[x-placement^=bottom]{margin-top:12px}.el-popper[x-placement^=bottom] .popper__arrow{top:-6px;left:50%;margin-right:3px;border-top-width:0;border-bottom-color:#EBEEF5}.el-popper[x-placement^=bottom] .popper__arrow::after{top:1px;margin-left:-6px;border-top-width:0;border-bottom-color:#FFF}.el-popper[x-placement^=right]{margin-left:12px}.el-popper[x-placement^=right] .popper__arrow{top:50%;left:-6px;margin-bottom:3px;border-right-color:#EBEEF5;border-left-width:0}.el-popper[x-placement^=right] .popper__arrow::after{bottom:-6px;left:1px;border-right-color:#FFF;border-left-width:0}.el-popper[x-placement^=left]{margin-right:12px}.el-popper[x-placement^=left] .popper__arrow{top:50%;right:-6px;margin-bottom:3px;border-right-width:0;border-left-color:#EBEEF5}.el-popper[x-placement^=left] .popper__arrow::after{right:1px;bottom:-6px;margin-left:-6px;border-right-width:0;border-left-color:#FFF}.el-tag{background-color:#e6eaf6;border-color:#ccd5ed;display:inline-block;height:32px;padding:0 10px;line-height:30px;font-size:12px;color:#002FA7;border-width:1px;border-style:solid;border-radius:4px;box-sizing:border-box;white-space:nowrap}.el-tag.is-hit{border-color:#002FA7}.el-tag .el-tag__close{color:#002fa7}.el-tag .el-tag__close:hover{color:#FFF;background-color:#002fa7}.el-tag.el-tag--info{background-color:#f4f4f5;border-color:#e9e9eb;color:#909399}.el-tag.el-tag--info.is-hit{border-color:#909399}.el-tag.el-tag--info .el-tag__close{color:#909399}.el-tag.el-tag--info .el-tag__close:hover{color:#FFF;background-color:#909399}.el-tag.el-tag--success{background-color:#f0f9eb;border-color:#e1f3d8;color:#67c23a}.el-tag.el-tag--success.is-hit{border-color:#67C23A}.el-tag.el-tag--success .el-tag__close{color:#67c23a}.el-tag.el-tag--success .el-tag__close:hover{color:#FFF;background-color:#67c23a}.el-tag.el-tag--warning{background-color:#fdf6ec;border-color:#faecd8;color:#e6a23c}.el-tag.el-tag--warning.is-hit{border-color:#E6A23C}.el-tag.el-tag--warning .el-tag__close{color:#e6a23c}.el-tag.el-tag--warning .el-tag__close:hover{color:#FFF;background-color:#e6a23c}.el-tag.el-tag--danger{background-color:#fef0f0;border-color:#fde2e2;color:#f56c6c}.el-tag.el-tag--danger.is-hit{border-color:#F56C6C}.el-tag.el-tag--danger .el-tag__close{color:#f56c6c}.el-tag.el-tag--danger .el-tag__close:hover{color:#FFF;background-color:#f56c6c}.el-tag .el-icon-close{border-radius:50%;text-align:center;position:relative;cursor:pointer;font-size:12px;height:16px;width:16px;line-height:16px;vertical-align:middle;top:-1px;right:-5px}.el-tag .el-icon-close::before{display:block}.el-tag--dark{background-color:#002fa7;border-color:#002fa7;color:#fff}.el-tag--dark.is-hit{border-color:#002FA7}.el-tag--dark .el-tag__close{color:#fff}.el-tag--dark .el-tag__close:hover{color:#FFF;background-color:#3359b9}.el-tag--dark.el-tag--info{background-color:#909399;border-color:#909399;color:#fff}.el-tag--dark.el-tag--info.is-hit{border-color:#909399}.el-tag--dark.el-tag--info .el-tag__close{color:#fff}.el-tag--dark.el-tag--info .el-tag__close:hover{color:#FFF;background-color:#a6a9ad}.el-tag--dark.el-tag--success{background-color:#67c23a;border-color:#67c23a;color:#fff}.el-tag--dark.el-tag--success.is-hit{border-color:#67C23A}.el-tag--dark.el-tag--success .el-tag__close{color:#fff}.el-tag--dark.el-tag--success .el-tag__close:hover{color:#FFF;background-color:#85ce61}.el-tag--dark.el-tag--warning{background-color:#e6a23c;border-color:#e6a23c;color:#fff}.el-tag--dark.el-tag--warning.is-hit{border-color:#E6A23C}.el-tag--dark.el-tag--warning .el-tag__close{color:#fff}.el-tag--dark.el-tag--warning .el-tag__close:hover{color:#FFF;background-color:#ebb563}.el-tag--dark.el-tag--danger{background-color:#f56c6c;border-color:#f56c6c;color:#fff}.el-tag--dark.el-tag--danger.is-hit{border-color:#F56C6C}.el-tag--dark.el-tag--danger .el-tag__close{color:#fff}.el-tag--dark.el-tag--danger .el-tag__close:hover{color:#FFF;background-color:#f78989}.el-tag--plain{background-color:#fff;border-color:#99acdc;color:#002fa7}.el-tag--plain.is-hit{border-color:#002FA7}.el-tag--plain .el-tag__close{color:#002fa7}.el-tag--plain .el-tag__close:hover{color:#FFF;background-color:#002fa7}.el-tag--plain.el-tag--info{background-color:#fff;border-color:#d3d4d6;color:#909399}.el-tag--plain.el-tag--info.is-hit{border-color:#909399}.el-tag--plain.el-tag--info .el-tag__close{color:#909399}.el-tag--plain.el-tag--info .el-tag__close:hover{color:#FFF;background-color:#909399}.el-tag--plain.el-tag--success{background-color:#fff;border-color:#c2e7b0;color:#67c23a}.el-tag--plain.el-tag--success.is-hit{border-color:#67C23A}.el-tag--plain.el-tag--success .el-tag__close{color:#67c23a}.el-tag--plain.el-tag--success .el-tag__close:hover{color:#FFF;background-color:#67c23a}.el-tag--plain.el-tag--warning{background-color:#fff;border-color:#f5dab1;color:#e6a23c}.el-tag--plain.el-tag--warning.is-hit{border-color:#E6A23C}.el-tag--plain.el-tag--warning .el-tag__close{color:#e6a23c}.el-tag--plain.el-tag--warning .el-tag__close:hover{color:#FFF;background-color:#e6a23c}.el-tag--plain.el-tag--danger{background-color:#fff;border-color:#fbc4c4;color:#f56c6c}.el-tag--plain.el-tag--danger.is-hit{border-color:#F56C6C}.el-tag--plain.el-tag--danger .el-tag__close{color:#f56c6c}.el-tag--plain.el-tag--danger .el-tag__close:hover{color:#FFF;background-color:#f56c6c}.el-tag--medium{height:28px;line-height:26px}.el-tag--medium .el-icon-close{-webkit-transform:scale(.8);transform:scale(.8)}.el-tag--small{height:24px;padding:0 8px;line-height:22px}.el-tag--small .el-icon-close{-webkit-transform:scale(.8);transform:scale(.8)}.el-tag--mini{height:20px;padding:0 5px;line-height:19px}.el-tag--mini .el-icon-close{margin-left:-3px;-webkit-transform:scale(.7);transform:scale(.7)}.el-cascader{display:inline-block;position:relative;font-size:14px;line-height:32px}.el-cascader:not(.is-disabled):hover .el-input__inner{cursor:pointer;border-color:#3F3F3F}.el-cascader .el-input .el-input__inner:focus,.el-cascader .el-input.is-focus .el-input__inner{border-color:#002FA7}.el-cascader .el-input{cursor:pointer}.el-cascader .el-input .el-input__inner{text-overflow:ellipsis}.el-cascader .el-input .el-icon-arrow-down{-webkit-transition:-webkit-transform .3s;transition:-webkit-transform .3s;transition:transform .3s;transition:transform .3s,-webkit-transform .3s;font-size:14px}.el-cascader .el-input .el-icon-arrow-down.is-reverse{-webkit-transform:rotateZ(180deg);transform:rotateZ(180deg)}.el-cascader .el-input .el-icon-circle-close:hover{color:#909399}.el-cascader--medium{font-size:14px;line-height:36px}.el-cascader--small{font-size:13px;line-height:32px}.el-cascader--mini{font-size:12px;line-height:28px}.el-cascader.is-disabled .el-cascader__label{z-index:2;color:#3F3F3F}.el-cascader__dropdown{margin:5px 0;font-size:14px;background:#FFF;border:1px solid #E4E7ED;border-radius:4px;-webkit-box-shadow:0 2px 12px 0 rgba(0,0,0,.1);box-shadow:0 2px 12px 0 rgba(0,0,0,.1)}.el-cascader__tags{position:absolute;left:0;right:30px;top:50%;-webkit-transform:translateY(-50%);transform:translateY(-50%);display:-webkit-box;display:-ms-flexbox;display:flex;-ms-flex-wrap:wrap;flex-wrap:wrap;line-height:normal;text-align:left;box-sizing:border-box}.el-cascader__tags .el-tag{display:-webkit-inline-box;display:-ms-inline-flexbox;display:inline-flex;-webkit-box-align:center;-ms-flex-align:center;align-items:center;max-width:100%;margin:2px 0 2px 6px;text-overflow:ellipsis;background:#f0f2f5}.el-cascader__tags .el-tag:not(.is-hit){border-color:transparent}.el-cascader__tags .el-tag>span{-webkit-box-flex:1;-ms-flex:1;flex:1;overflow:hidden;text-overflow:ellipsis}.el-cascader__tags .el-tag .el-icon-close{-webkit-box-flex:0;-ms-flex:none;flex:none;background-color:#3F3F3F;color:#FFF}.el-cascader__tags .el-tag .el-icon-close:hover{background-color:#909399}.el-cascader__suggestion-panel{border-radius:4px}.el-cascader__suggestion-list{max-height:204px;margin:0;padding:6px 0;font-size:14px;color:#606266;text-align:center}.el-cascader__suggestion-item{display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-pack:justify;-ms-flex-pack:justify;justify-content:space-between;-webkit-box-align:center;-ms-flex-align:center;align-items:center;height:34px;padding:0 15px;text-align:left;outline:0;cursor:pointer}.el-cascader__suggestion-item:focus,.el-cascader__suggestion-item:hover{background:#F5F7FA}.el-cascader__suggestion-item.is-checked{color:#002FA7;font-weight:700}.el-cascader__suggestion-item>span{margin-right:10px}.el-cascader__empty-text{margin:10px 0;color:#3F3F3F}.el-cascader__search-input{-webkit-box-flex:1;-ms-flex:1;flex:1;height:24px;min-width:60px;margin:2px 0 2px 15px;padding:0;color:#606266;border:none;outline:0;-webkit-box-sizing:border-box;box-sizing:border-box}.el-cascader__search-input::-webkit-input-placeholder{color:#3F3F3F}.el-cascader__search-input::-ms-input-placeholder{color:#3F3F3F}.el-cascader__search-input::placeholder{color:#3F3F3F}.el-color-predefine{display:-webkit-box;display:-ms-flexbox;display:flex;font-size:12px;margin-top:8px;width:280px}.el-color-predefine__colors{display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-flex:1;-ms-flex:1;flex:1;-ms-flex-wrap:wrap;flex-wrap:wrap}.el-color-predefine__color-selector{margin:0 0 8px 8px;width:20px;height:20px;border-radius:4px;cursor:pointer}.el-color-predefine__color-selector:nth-child(10n+1){margin-left:0}.el-color-predefine__color-selector.selected{-webkit-box-shadow:0 0 3px 2px #002FA7;box-shadow:0 0 3px 2px #002FA7}.el-color-predefine__color-selector>div{display:-webkit-box;display:-ms-flexbox;display:flex;height:100%;border-radius:3px}.el-color-predefine__color-selector.is-alpha{background-image:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAwAAAAMCAIAAADZF8uwAAAAGUlEQVQYV2M4gwH+YwCGIasIUwhT25BVBADtzYNYrHvv4gAAAABJRU5ErkJggg==)}.el-color-hue-slider{position:relative;-webkit-box-sizing:border-box;box-sizing:border-box;width:280px;height:12px;background-color:red;padding:0 2px}.el-color-hue-slider__bar{position:relative;background:-webkit-gradient(linear,left top,right top,from(red),color-stop(17%,#ff0),color-stop(33%,#0f0),color-stop(50%,#0ff),color-stop(67%,#00f),color-stop(83%,#f0f),to(red));background:linear-gradient(to right,red 0,#ff0 17%,#0f0 33%,#0ff 50%,#00f 67%,#f0f 83%,red 100%);height:100%}.el-color-hue-slider__thumb{position:absolute;cursor:pointer;-webkit-box-sizing:border-box;box-sizing:border-box;left:0;top:0;width:4px;height:100%;border-radius:1px;background:#fff;border:1px solid #f0f0f0;-webkit-box-shadow:0 0 2px rgba(0,0,0,.6);box-shadow:0 0 2px rgba(0,0,0,.6);z-index:1}.el-color-hue-slider.is-vertical{width:12px;height:180px;padding:2px 0}.el-color-hue-slider.is-vertical .el-color-hue-slider__bar{background:-webkit-gradient(linear,left top,left bottom,from(red),color-stop(17%,#ff0),color-stop(33%,#0f0),color-stop(50%,#0ff),color-stop(67%,#00f),color-stop(83%,#f0f),to(red));background:linear-gradient(to bottom,red 0,#ff0 17%,#0f0 33%,#0ff 50%,#00f 67%,#f0f 83%,red 100%)}.el-color-hue-slider.is-vertical .el-color-hue-slider__thumb{left:0;top:0;width:100%;height:4px}.el-color-svpanel{position:relative;width:280px;height:180px}.el-color-svpanel__black,.el-color-svpanel__white{position:absolute;top:0;left:0;right:0;bottom:0}.el-color-svpanel__white{background:-webkit-gradient(linear,left top,right top,from(#fff),to(rgba(255,255,255,0)));background:linear-gradient(to right,#fff,rgba(255,255,255,0))}.el-color-svpanel__black{background:-webkit-gradient(linear,left bottom,left top,from(#000),to(rgba(0,0,0,0)));background:linear-gradient(to top,#000,rgba(0,0,0,0))}.el-color-svpanel__cursor{position:absolute}.el-color-svpanel__cursor>div{cursor:head;width:4px;height:4px;-webkit-box-shadow:0 0 0 1.5px #fff,inset 0 0 1px 1px rgba(0,0,0,.3),0 0 1px 2px rgba(0,0,0,.4);box-shadow:0 0 0 1.5px #fff,inset 0 0 1px 1px rgba(0,0,0,.3),0 0 1px 2px rgba(0,0,0,.4);border-radius:50%;-webkit-transform:translate(-2px,-2px);transform:translate(-2px,-2px)}.el-color-alpha-slider{position:relative;-webkit-box-sizing:border-box;box-sizing:border-box;width:280px;height:12px;background:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAwAAAAMCAIAAADZF8uwAAAAGUlEQVQYV2M4gwH+YwCGIasIUwhT25BVBADtzYNYrHvv4gAAAABJRU5ErkJggg==)}.el-color-alpha-slider__bar{position:relative;background:-webkit-gradient(linear,left top,right top,from(rgba(255,255,255,0)),to(white));background:linear-gradient(to right,rgba(255,255,255,0) 0,#fff 100%);height:100%}.el-color-alpha-slider__thumb{position:absolute;cursor:pointer;-webkit-box-sizing:border-box;box-sizing:border-box;left:0;top:0;width:4px;height:100%;border-radius:1px;background:#fff;border:1px solid #f0f0f0;-webkit-box-shadow:0 0 2px rgba(0,0,0,.6);box-shadow:0 0 2px rgba(0,0,0,.6);z-index:1}.el-color-alpha-slider.is-vertical{width:20px;height:180px}.el-color-alpha-slider.is-vertical .el-color-alpha-slider__bar{background:-webkit-gradient(linear,left top,left bottom,from(rgba(255,255,255,0)),to(white));background:linear-gradient(to bottom,rgba(255,255,255,0) 0,#fff 100%)}.el-color-alpha-slider.is-vertical .el-color-alpha-slider__thumb{left:0;top:0;width:100%;height:4px}.el-color-dropdown{width:300px}.el-color-dropdown__main-wrapper{margin-bottom:6px}.el-color-dropdown__main-wrapper::after{content:"";display:table;clear:both}.el-color-dropdown__btns{margin-top:6px;text-align:right}.el-color-dropdown__value{float:left;line-height:26px;font-size:12px;color:#000;width:160px}.el-color-dropdown__btn{border:1px solid #dcdcdc;color:#333;line-height:24px;border-radius:2px;padding:0 20px;cursor:pointer;background-color:transparent;outline:0;font-size:12px}.el-color-dropdown__btn[disabled]{color:#ccc;cursor:not-allowed}.el-color-dropdown__btn:hover{color:#002FA7;border-color:#002FA7}.el-color-dropdown__link-btn{cursor:pointer;color:#002FA7;text-decoration:none;padding:15px;font-size:12px}.el-color-dropdown__link-btn:hover{color:tint(#002FA7,20%)}.el-color-picker{display:inline-block;position:relative;line-height:normal;height:40px}.el-color-picker.is-disabled .el-color-picker__trigger{cursor:not-allowed}.el-color-picker--medium{height:36px}.el-color-picker--medium .el-color-picker__trigger{height:36px;width:36px}.el-color-picker--medium .el-color-picker__mask{height:34px;width:34px}.el-color-picker--small{height:32px}.el-color-picker--small .el-color-picker__trigger{height:32px;width:32px}.el-color-picker--small .el-color-picker__mask{height:30px;width:30px}.el-color-picker--small .el-color-picker__empty,.el-color-picker--small .el-color-picker__icon{-webkit-transform:translate3d(-50%,-50%,0) scale(.8);transform:translate3d(-50%,-50%,0) scale(.8)}.el-color-picker--mini{height:28px}.el-color-picker--mini .el-color-picker__trigger{height:28px;width:28px}.el-color-picker--mini .el-color-picker__mask{height:26px;width:26px}.el-color-picker--mini .el-color-picker__empty,.el-color-picker--mini .el-color-picker__icon{-webkit-transform:translate3d(-50%,-50%,0) scale(.8);transform:translate3d(-50%,-50%,0) scale(.8)}.el-color-picker__mask{height:38px;width:38px;border-radius:4px;position:absolute;top:1px;left:1px;z-index:1;cursor:not-allowed;background-color:rgba(255,255,255,.7)}.el-color-picker__trigger{display:inline-block;-webkit-box-sizing:border-box;box-sizing:border-box;height:40px;width:40px;padding:4px;border:1px solid #e6e6e6;border-radius:4px;font-size:0;position:relative;cursor:pointer}.el-color-picker__color{position:relative;display:block;-webkit-box-sizing:border-box;box-sizing:border-box;border:1px solid #999;border-radius:2px;width:100%;height:100%;text-align:center}.el-color-picker__color.is-alpha{background-image:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAwAAAAMCAIAAADZF8uwAAAAGUlEQVQYV2M4gwH+YwCGIasIUwhT25BVBADtzYNYrHvv4gAAAABJRU5ErkJggg==)}.el-color-picker__color-inner{position:absolute;left:0;top:0;right:0;bottom:0}.el-color-picker__empty,.el-color-picker__icon{top:50%;left:50%;font-size:12px;position:absolute}.el-color-picker__empty{color:#999;-webkit-transform:translate3d(-50%,-50%,0);transform:translate3d(-50%,-50%,0)}.el-color-picker__icon{display:inline-block;width:100%;-webkit-transform:translate3d(-50%,-50%,0);transform:translate3d(-50%,-50%,0);color:#FFF;text-align:center}.el-color-picker__panel{position:absolute;z-index:10;padding:6px;-webkit-box-sizing:content-box;box-sizing:content-box;background-color:#FFF;border:1px solid #EBEEF5;border-radius:4px;-webkit-box-shadow:0 2px 12px 0 rgba(0,0,0,.1);box-shadow:0 2px 12px 0 rgba(0,0,0,.1)}.el-textarea{position:relative;display:inline-block;width:100%;vertical-align:bottom;font-size:14px}.el-textarea__inner{display:block;resize:vertical;padding:5px 15px;line-height:1.5;-webkit-box-sizing:border-box;box-sizing:border-box;width:100%;font-size:inherit;color:#606266;background-color:#FFF;background-image:none;border:1px solid #BBB;border-radius:4px;-webkit-transition:border-color .2s cubic-bezier(.645,.045,.355,1);transition:border-color .2s cubic-bezier(.645,.045,.355,1)}.el-textarea__inner::-webkit-input-placeholder{color:#3F3F3F}.el-textarea__inner::-ms-input-placeholder{color:#3F3F3F}.el-textarea__inner::placeholder{color:#3F3F3F}.el-textarea__inner:hover{border-color:#3F3F3F}.el-textarea__inner:focus{outline:0;border-color:#002FA7}.el-textarea .el-input__count{color:#909399;background:#FFF;position:absolute;font-size:12px;bottom:5px;right:10px}.el-textarea.is-disabled .el-textarea__inner{background-color:#F5F7FA;border-color:#E4E7ED;color:#3F3F3F;cursor:not-allowed}.el-textarea.is-disabled .el-textarea__inner::-webkit-input-placeholder{color:#3F3F3F}.el-textarea.is-disabled .el-textarea__inner::-ms-input-placeholder{color:#3F3F3F}.el-textarea.is-disabled .el-textarea__inner::placeholder{color:#3F3F3F}.el-textarea.is-exceed .el-textarea__inner{border-color:#F56C6C}.el-textarea.is-exceed .el-input__count{color:#F56C6C}.el-input{position:relative;font-size:14px;display:inline-block;width:100%}.el-input::-webkit-scrollbar{z-index:11;width:6px}.el-input::-webkit-scrollbar:horizontal{height:6px}.el-input::-webkit-scrollbar-thumb{border-radius:5px;width:6px;background:#b4bccc}.el-input::-webkit-scrollbar-corner{background:#fff}.el-input::-webkit-scrollbar-track{background:#fff}.el-input::-webkit-scrollbar-track-piece{background:#fff;width:6px}.el-input .el-input__clear{color:#3F3F3F;font-size:14px;cursor:pointer;-webkit-transition:color .2s cubic-bezier(.645,.045,.355,1);transition:color .2s cubic-bezier(.645,.045,.355,1)}.el-input .el-input__clear:hover{color:#909399}.el-input .el-input__count{height:100%;display:-webkit-inline-box;display:-ms-inline-flexbox;display:inline-flex;-webkit-box-align:center;-ms-flex-align:center;align-items:center;color:#909399;font-size:12px}.el-input .el-input__count .el-input__count-inner{background:#FFF;line-height:initial;display:inline-block;padding:0 5px}.el-input__inner{-webkit-appearance:none;background-color:#FFF;background-image:none;border-radius:4px;border:1px solid #BBB;-webkit-box-sizing:border-box;box-sizing:border-box;color:#606266;display:inline-block;font-size:inherit;height:32px;line-height:32px;outline:0;padding:0 15px;-webkit-transition:border-color .2s cubic-bezier(.645,.045,.355,1);transition:border-color .2s cubic-bezier(.645,.045,.355,1);width:100%}.el-input__prefix,.el-input__suffix{position:absolute;top:0;-webkit-transition:all .3s;height:100%;color:#3F3F3F;text-align:center}.el-input__inner::-webkit-input-placeholder{color:#3F3F3F}.el-input__inner::-ms-input-placeholder{color:#3F3F3F}.el-input__inner::placeholder{color:#3F3F3F}.el-input__inner:hover{border-color:#3F3F3F}.el-input.is-active .el-input__inner,.el-input__inner:focus{border-color:#002FA7;outline:0}.el-input__suffix{right:5px;transition:all .3s}.el-input__suffix-inner{pointer-events:all}.el-input__prefix{left:5px;transition:all .3s}.el-input__icon{height:100%;width:25px;text-align:center;-webkit-transition:all .3s;transition:all .3s;line-height:32px}.el-input__icon:after{content:'';height:100%;width:0;display:inline-block;vertical-align:middle}.el-input__validateIcon{pointer-events:none}.el-input.is-disabled .el-input__inner{background-color:#F5F7FA;border-color:#E4E7ED;color:#3F3F3F;cursor:not-allowed}.el-input.is-disabled .el-input__inner::-webkit-input-placeholder{color:#3F3F3F}.el-input.is-disabled .el-input__inner::-ms-input-placeholder{color:#3F3F3F}.el-input.is-disabled .el-input__inner::placeholder{color:#3F3F3F}.el-input.is-disabled .el-input__icon{cursor:not-allowed}.el-link,.el-transfer-panel__filter .el-icon-circle-close{cursor:pointer}.el-input.is-exceed .el-input__inner{border-color:#F56C6C}.el-input.is-exceed .el-input__suffix .el-input__count{color:#F56C6C}.el-input--suffix .el-input__inner{padding-right:30px}.el-input--prefix .el-input__inner{padding-left:30px}.el-input--medium{font-size:14px}.el-input--medium .el-input__inner{height:36px;line-height:36px}.el-input--medium .el-input__icon{line-height:36px}.el-input--small{font-size:13px}.el-input--small .el-input__inner{height:32px;line-height:32px}.el-input--small .el-input__icon{line-height:32px}.el-input--mini{font-size:12px}.el-input--mini .el-input__inner{height:28px;line-height:28px}.el-input--mini .el-input__icon{line-height:28px}.el-input-group{line-height:normal;display:inline-table;width:100%;border-collapse:separate;border-spacing:0}.el-input-group>.el-input__inner{vertical-align:middle;display:table-cell}.el-input-group__append,.el-input-group__prepend{background-color:#F5F7FA;color:#909399;vertical-align:middle;display:table-cell;position:relative;border:1px solid #BBB;border-radius:4px;padding:0 20px;width:1px;white-space:nowrap}.el-input-group--prepend .el-input__inner,.el-input-group__append{border-top-left-radius:0;border-bottom-left-radius:0}.el-input-group--append .el-input__inner,.el-input-group__prepend{border-top-right-radius:0;border-bottom-right-radius:0}.el-input-group__append:focus,.el-input-group__prepend:focus{outline:0}.el-input-group__append .el-button,.el-input-group__append .el-select,.el-input-group__prepend .el-button,.el-input-group__prepend .el-select{display:inline-block;margin:-10px -20px}.el-input-group__append button.el-button,.el-input-group__append div.el-select .el-input__inner,.el-input-group__append div.el-select:hover .el-input__inner,.el-input-group__prepend button.el-button,.el-input-group__prepend div.el-select .el-input__inner,.el-input-group__prepend div.el-select:hover .el-input__inner{border-color:transparent;background-color:transparent;color:inherit;border-top:0;border-bottom:0}.el-input-group__append .el-button,.el-input-group__append .el-input,.el-input-group__prepend .el-button,.el-input-group__prepend .el-input{font-size:inherit}.el-input-group__prepend{border-right:0}.el-input-group__append{border-left:0}.el-input-group--append .el-select .el-input.is-focus .el-input__inner,.el-input-group--prepend .el-select .el-input.is-focus .el-input__inner{border-color:transparent}.el-input__inner::-ms-clear{display:none;width:0;height:0}.el-transfer{font-size:14px}.el-transfer__buttons{display:inline-block;vertical-align:middle;padding:0 30px}.el-transfer__button{display:block;margin:0 auto;padding:10px;border-radius:50%;color:#FFF;background-color:#002FA7;font-size:0}.el-transfer-panel__item+.el-transfer-panel__item,.el-transfer__button [class*=el-icon-]+span{margin-left:0}.el-transfer__button.is-with-texts{border-radius:4px}.el-transfer__button.is-disabled,.el-transfer__button.is-disabled:hover{border:1px solid #BBB;background-color:#F5F7FA;color:#3F3F3F}.el-transfer__button:first-child{margin-bottom:10px}.el-transfer__button:nth-child(2){margin:0}.el-transfer__button i,.el-transfer__button span{font-size:14px}.el-transfer-panel{border:1px solid #EBEEF5;border-radius:4px;overflow:hidden;background:#FFF;display:inline-block;vertical-align:middle;width:200px;max-height:100%;-webkit-box-sizing:border-box;box-sizing:border-box;position:relative}.el-transfer-panel__body{height:246px}.el-transfer-panel__body.is-with-footer{padding-bottom:40px}.el-transfer-panel__list{margin:0;padding:6px 0;list-style:none;height:246px;overflow:auto;-webkit-box-sizing:border-box;box-sizing:border-box}.el-transfer-panel__list.is-filterable{height:194px;padding-top:0}.el-transfer-panel__item{height:30px;line-height:30px;padding-left:15px;display:block!important}.el-transfer-panel__item.el-checkbox{color:#606266}.el-transfer-panel__item:hover{color:#002FA7}.el-transfer-panel__item.el-checkbox .el-checkbox__label{width:100%;overflow:hidden;text-overflow:ellipsis;white-space:nowrap;display:block;-webkit-box-sizing:border-box;box-sizing:border-box;padding-left:24px;line-height:30px}.el-transfer-panel__item .el-checkbox__input{position:absolute;top:8px}.el-transfer-panel__filter{text-align:center;margin:15px;-webkit-box-sizing:border-box;box-sizing:border-box;display:block;width:auto}.el-transfer-panel__filter .el-input__inner{height:32px;width:100%;font-size:12px;display:inline-block;-webkit-box-sizing:border-box;box-sizing:border-box;border-radius:16px;padding-right:10px;padding-left:30px}.el-transfer-panel__filter .el-input__icon{margin-left:5px}.el-transfer-panel .el-transfer-panel__header{height:40px;line-height:40px;background:#F5F7FA;margin:0;padding-left:15px;border-bottom:1px solid #EBEEF5;-webkit-box-sizing:border-box;box-sizing:border-box;color:#000}.el-transfer-panel .el-transfer-panel__header .el-checkbox{display:block;line-height:40px}.el-transfer-panel .el-transfer-panel__header .el-checkbox .el-checkbox__label{font-size:16px;color:#303133;font-weight:400}.el-transfer-panel .el-transfer-panel__header .el-checkbox .el-checkbox__label span{position:absolute;right:15px;color:#909399;font-size:12px;font-weight:400}.el-divider__text,.el-link{font-weight:500;font-size:14px}.el-transfer-panel .el-transfer-panel__footer{height:40px;background:#FFF;margin:0;padding:0;border-top:1px solid #EBEEF5;position:absolute;bottom:0;left:0;width:100%;z-index:1}.el-transfer-panel .el-transfer-panel__footer::after{display:inline-block;content:"";height:100%;vertical-align:middle}.el-container,.el-timeline-item__node{display:-webkit-box;display:-ms-flexbox}.el-transfer-panel .el-transfer-panel__footer .el-checkbox{padding-left:20px;color:#606266}.el-transfer-panel .el-transfer-panel__empty{margin:0;height:30px;line-height:30px;padding:6px 15px 0;color:#909399;text-align:center}.el-transfer-panel .el-checkbox__label{padding-left:8px}.el-transfer-panel .el-checkbox__inner{height:14px;width:14px;border-radius:3px}.el-transfer-panel .el-checkbox__inner::after{height:6px;width:3px;left:4px}.el-container{display:flex;-webkit-box-orient:horizontal;-webkit-box-direction:normal;-ms-flex-direction:row;flex-direction:row;-webkit-box-flex:1;-ms-flex:1;flex:1;-ms-flex-preferred-size:auto;flex-basis:auto;-webkit-box-sizing:border-box;box-sizing:border-box;min-width:0}.el-container.is-vertical,.el-drawer{-webkit-box-orient:vertical;-webkit-box-direction:normal}.el-aside,.el-header{-webkit-box-sizing:border-box}.el-container.is-vertical{-ms-flex-direction:column;flex-direction:column}.el-header{padding:0 20px;box-sizing:border-box;-ms-flex-negative:0;flex-shrink:0}.el-aside{overflow:auto;box-sizing:border-box;-ms-flex-negative:0;flex-shrink:0}.el-footer,.el-main{-webkit-box-sizing:border-box}.el-main{display:block;-webkit-box-flex:1;-ms-flex:1;flex:1;-ms-flex-preferred-size:auto;flex-basis:auto;overflow:auto;box-sizing:border-box;padding:20px}.el-footer{padding:0 20px;box-sizing:border-box;-ms-flex-negative:0;flex-shrink:0}.el-timeline{margin:0;font-size:14px;list-style:none}.el-timeline .el-timeline-item:last-child .el-timeline-item__tail{display:none}.el-timeline-item{position:relative;padding-bottom:20px}.el-timeline-item__wrapper{position:relative;padding-left:28px;top:-3px}.el-timeline-item__tail{position:absolute;left:4px;height:100%;border-left:2px solid #E4E7ED}.el-timeline-item__icon{color:#FFF;font-size:13px}.el-timeline-item__node{position:absolute;background-color:#E4E7ED;border-radius:50%;display:flex;-webkit-box-pack:center;-ms-flex-pack:center;justify-content:center;-webkit-box-align:center;-ms-flex-align:center;align-items:center}.el-image__error,.el-timeline-item__dot{display:-webkit-box;display:-ms-flexbox}.el-timeline-item__node--normal{left:-1px;width:12px;height:12px}.el-timeline-item__node--large{left:-2px;width:14px;height:14px}.el-timeline-item__node--primary{background-color:#002FA7}.el-timeline-item__node--success{background-color:#67C23A}.el-timeline-item__node--warning{background-color:#E6A23C}.el-timeline-item__node--danger{background-color:#F56C6C}.el-timeline-item__node--info{background-color:#909399}.el-timeline-item__dot{position:absolute;display:flex;-webkit-box-pack:center;-ms-flex-pack:center;justify-content:center;-webkit-box-align:center;-ms-flex-align:center;align-items:center}.el-timeline-item__content{color:#303133}.el-timeline-item__timestamp{color:#909399;line-height:1;font-size:13px}.el-timeline-item__timestamp.is-top{margin-bottom:8px;padding-top:4px}.el-timeline-item__timestamp.is-bottom{margin-top:8px}.el-link{display:-webkit-inline-box;display:-ms-inline-flexbox;display:inline-flex;-webkit-box-orient:horizontal;-webkit-box-direction:normal;-ms-flex-direction:row;flex-direction:row;-webkit-box-align:center;-ms-flex-align:center;align-items:center;-webkit-box-pack:center;-ms-flex-pack:center;justify-content:center;vertical-align:middle;position:relative;text-decoration:none;outline:0;padding:0}.el-link.is-underline:hover:after{content:"";position:absolute;left:0;right:0;height:0;bottom:0;border-bottom:1px solid #002FA7}.el-link.el-link--default:after,.el-link.el-link--primary.is-underline:hover:after,.el-link.el-link--primary:after{border-color:#002FA7}.el-link.is-disabled{cursor:not-allowed}.el-link [class*=el-icon-]+span{margin-left:5px}.el-link.el-link--default{color:#606266}.el-link.el-link--default:hover{color:#002FA7}.el-link.el-link--default.is-disabled{color:#3F3F3F}.el-link.el-link--primary{color:#002FA7}.el-link.el-link--primary:hover{color:#3359b9}.el-link.el-link--primary.is-disabled{color:#8097d3}.el-link.el-link--danger.is-underline:hover:after,.el-link.el-link--danger:after{border-color:#F56C6C}.el-link.el-link--danger{color:#F56C6C}.el-link.el-link--danger:hover{color:#f78989}.el-link.el-link--danger.is-disabled{color:#fab6b6}.el-link.el-link--success.is-underline:hover:after,.el-link.el-link--success:after{border-color:#67C23A}.el-link.el-link--success{color:#67C23A}.el-link.el-link--success:hover{color:#85ce61}.el-link.el-link--success.is-disabled{color:#b3e19d}.el-link.el-link--warning.is-underline:hover:after,.el-link.el-link--warning:after{border-color:#E6A23C}.el-link.el-link--warning{color:#E6A23C}.el-link.el-link--warning:hover{color:#ebb563}.el-link.el-link--warning.is-disabled{color:#f3d19e}.el-link.el-link--info.is-underline:hover:after,.el-link.el-link--info:after{border-color:#909399}.el-link.el-link--info{color:#909399}.el-link.el-link--info:hover{color:#a6a9ad}.el-link.el-link--info.is-disabled{color:#c8c9cc}.el-divider{background-color:#BBB;position:relative}.el-divider--horizontal{display:block;height:1px;width:100%;margin:24px 0}.el-divider--vertical{display:inline-block;width:1px;height:1em;margin:0 8px;vertical-align:middle;position:relative}.el-divider__text{position:absolute;background-color:#FFF;padding:0 20px;color:#303133}.el-image__error,.el-image__placeholder{background:#F5F7FA}.el-divider__text.is-left{left:20px;-webkit-transform:translateY(-50%);transform:translateY(-50%)}.el-divider__text.is-center{left:50%;-webkit-transform:translateX(-50%) translateY(-50%);transform:translateX(-50%) translateY(-50%)}.el-divider__text.is-right{right:20px;-webkit-transform:translateY(-50%);transform:translateY(-50%)}.el-image__error,.el-image__inner,.el-image__placeholder{width:100%;height:100%}.el-image{position:relative;display:inline-block;overflow:hidden}.el-image__inner{vertical-align:top}.el-image__inner--center{position:relative;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);transform:translate(-50%,-50%);display:block}.el-image__error{display:flex;-webkit-box-pack:center;-ms-flex-pack:center;justify-content:center;-webkit-box-align:center;-ms-flex-align:center;align-items:center;font-size:14px;color:#3F3F3F;vertical-align:middle}.el-image__preview{cursor:pointer}.el-image-viewer__wrapper{position:fixed;top:0;right:0;bottom:0;left:0}.el-image-viewer__btn{position:absolute;z-index:1;display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-align:center;-ms-flex-align:center;align-items:center;-webkit-box-pack:center;-ms-flex-pack:center;justify-content:center;border-radius:50%;opacity:.8;cursor:pointer;-webkit-box-sizing:border-box;box-sizing:border-box;user-select:none}.el-button,.el-checkbox{-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none}.el-image-viewer__close{top:40px;right:40px;width:40px;height:40px;font-size:40px}.el-image-viewer__canvas{width:100%;height:100%;display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-pack:center;-ms-flex-pack:center;justify-content:center;-webkit-box-align:center;-ms-flex-align:center;align-items:center}.el-image-viewer__actions{left:50%;bottom:30px;-webkit-transform:translateX(-50%);transform:translateX(-50%);width:282px;height:44px;padding:0 23px;background-color:#606266;border-color:#fff;border-radius:22px}.el-image-viewer__actions__inner{width:100%;height:100%;text-align:justify;cursor:default;font-size:23px;color:#fff;display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-align:center;-ms-flex-align:center;align-items:center;-ms-flex-pack:distribute;justify-content:space-around}.el-image-viewer__next,.el-image-viewer__prev{top:50%;width:44px;height:44px;font-size:24px;color:#fff;background-color:#606266;border-color:#fff}.el-image-viewer__prev{-webkit-transform:translateY(-50%);transform:translateY(-50%);left:40px}.el-image-viewer__next{-webkit-transform:translateY(-50%);transform:translateY(-50%);right:40px;text-indent:2px}.el-image-viewer__mask{position:absolute;width:100%;height:100%;top:0;left:0;opacity:.5;background:#000}.viewer-fade-enter-active{-webkit-animation:viewer-fade-in .3s;animation:viewer-fade-in .3s}.viewer-fade-leave-active{-webkit-animation:viewer-fade-out .3s;animation:viewer-fade-out .3s}@-webkit-keyframes viewer-fade-in{0%{-webkit-transform:translate3d(0,-20px,0);transform:translate3d(0,-20px,0);opacity:0}100%{-webkit-transform:translate3d(0,0,0);transform:translate3d(0,0,0);opacity:1}}@keyframes viewer-fade-in{0%{-webkit-transform:translate3d(0,-20px,0);transform:translate3d(0,-20px,0);opacity:0}100%{-webkit-transform:translate3d(0,0,0);transform:translate3d(0,0,0);opacity:1}}@-webkit-keyframes viewer-fade-out{0%{-webkit-transform:translate3d(0,0,0);transform:translate3d(0,0,0);opacity:1}100%{-webkit-transform:translate3d(0,-20px,0);transform:translate3d(0,-20px,0);opacity:0}}@keyframes viewer-fade-out{0%{-webkit-transform:translate3d(0,0,0);transform:translate3d(0,0,0);opacity:1}100%{-webkit-transform:translate3d(0,-20px,0);transform:translate3d(0,-20px,0);opacity:0}}.el-button{display:inline-block;line-height:1;white-space:nowrap;cursor:pointer;background:#FFF;border:1px solid #BBB;color:#606266;-webkit-appearance:none;text-align:center;-webkit-box-sizing:border-box;box-sizing:border-box;outline:0;margin:0;-webkit-transition:.1s;transition:.1s;font-weight:500;padding:12px 20px;font-size:14px;border-radius:4px}.el-button+.el-button{margin-left:10px}.el-button:focus,.el-button:hover{color:#002FA7;border-color:#b3c1e5;background-color:#e6eaf6}.el-button:active{color:#002a96;border-color:#002a96;outline:0}.el-button::-moz-focus-inner{border:0}.el-button [class*=el-icon-]+span{margin-left:5px}.el-button.is-plain:focus,.el-button.is-plain:hover{background:#FFF;border-color:#002FA7;color:#002FA7}.el-button.is-active,.el-button.is-plain:active{color:#002a96;border-color:#002a96}.el-button.is-plain:active{background:#FFF;outline:0}.el-button.is-disabled,.el-button.is-disabled:focus,.el-button.is-disabled:hover{color:#3F3F3F;cursor:not-allowed;background-image:none;background-color:#FFF;border-color:#EBEEF5}.el-button.is-disabled.el-button--text{background-color:transparent}.el-button.is-disabled.is-plain,.el-button.is-disabled.is-plain:focus,.el-button.is-disabled.is-plain:hover{background-color:#FFF;border-color:#EBEEF5;color:#3F3F3F}.el-button.is-loading{position:relative;pointer-events:none}.el-button.is-loading:before{pointer-events:none;content:'';position:absolute;left:-1px;top:-1px;right:-1px;bottom:-1px;border-radius:inherit;background-color:rgba(255,255,255,.35)}.el-button.is-round{border-radius:20px;padding:12px 23px}.el-button.is-circle{border-radius:50%;padding:12px}.el-button--primary{color:#FFF;background-color:#002FA7;border-color:#002FA7}.el-button--primary:focus,.el-button--primary:hover{background:#3359b9;border-color:#3359b9;color:#FFF}.el-button--primary.is-active,.el-button--primary:active{background:#002a96;border-color:#002a96;color:#FFF}.el-button--primary:active{outline:0}.el-button--primary.is-disabled,.el-button--primary.is-disabled:active,.el-button--primary.is-disabled:focus,.el-button--primary.is-disabled:hover{color:#FFF;background-color:#8097d3;border-color:#8097d3}.el-button--primary.is-plain{color:#002FA7;background:#e6eaf6;border-color:#99acdc}.el-button--primary.is-plain:focus,.el-button--primary.is-plain:hover{background:#002FA7;border-color:#002FA7;color:#FFF}.el-button--primary.is-plain:active{background:#002a96;border-color:#002a96;color:#FFF;outline:0}.el-button--primary.is-plain.is-disabled,.el-button--primary.is-plain.is-disabled:active,.el-button--primary.is-plain.is-disabled:focus,.el-button--primary.is-plain.is-disabled:hover{color:#6682ca;background-color:#e6eaf6;border-color:#ccd5ed}.el-button--success{color:#FFF;background-color:#67C23A;border-color:#67C23A}.el-button--success:focus,.el-button--success:hover{background:#85ce61;border-color:#85ce61;color:#FFF}.el-button--success.is-active,.el-button--success:active{background:#5daf34;border-color:#5daf34;color:#FFF}.el-button--success:active{outline:0}.el-button--success.is-disabled,.el-button--success.is-disabled:active,.el-button--success.is-disabled:focus,.el-button--success.is-disabled:hover{color:#FFF;background-color:#b3e19d;border-color:#b3e19d}.el-button--success.is-plain{color:#67C23A;background:#f0f9eb;border-color:#c2e7b0}.el-button--success.is-plain:focus,.el-button--success.is-plain:hover{background:#67C23A;border-color:#67C23A;color:#FFF}.el-button--success.is-plain:active{background:#5daf34;border-color:#5daf34;color:#FFF;outline:0}.el-button--success.is-plain.is-disabled,.el-button--success.is-plain.is-disabled:active,.el-button--success.is-plain.is-disabled:focus,.el-button--success.is-plain.is-disabled:hover{color:#a4da89;background-color:#f0f9eb;border-color:#e1f3d8}.el-button--warning{color:#FFF;background-color:#E6A23C;border-color:#E6A23C}.el-button--warning:focus,.el-button--warning:hover{background:#ebb563;border-color:#ebb563;color:#FFF}.el-button--warning.is-active,.el-button--warning:active{background:#cf9236;border-color:#cf9236;color:#FFF}.el-button--warning:active{outline:0}.el-button--warning.is-disabled,.el-button--warning.is-disabled:active,.el-button--warning.is-disabled:focus,.el-button--warning.is-disabled:hover{color:#FFF;background-color:#f3d19e;border-color:#f3d19e}.el-button--warning.is-plain{color:#E6A23C;background:#fdf6ec;border-color:#f5dab1}.el-button--warning.is-plain:focus,.el-button--warning.is-plain:hover{background:#E6A23C;border-color:#E6A23C;color:#FFF}.el-button--warning.is-plain:active{background:#cf9236;border-color:#cf9236;color:#FFF;outline:0}.el-button--warning.is-plain.is-disabled,.el-button--warning.is-plain.is-disabled:active,.el-button--warning.is-plain.is-disabled:focus,.el-button--warning.is-plain.is-disabled:hover{color:#f0c78a;background-color:#fdf6ec;border-color:#faecd8}.el-button--danger{color:#FFF;background-color:#F56C6C;border-color:#F56C6C}.el-button--danger:focus,.el-button--danger:hover{background:#f78989;border-color:#f78989;color:#FFF}.el-button--danger.is-active,.el-button--danger:active{background:#dd6161;border-color:#dd6161;color:#FFF}.el-button--danger:active{outline:0}.el-button--danger.is-disabled,.el-button--danger.is-disabled:active,.el-button--danger.is-disabled:focus,.el-button--danger.is-disabled:hover{color:#FFF;background-color:#fab6b6;border-color:#fab6b6}.el-button--danger.is-plain{color:#F56C6C;background:#fef0f0;border-color:#fbc4c4}.el-button--danger.is-plain:focus,.el-button--danger.is-plain:hover{background:#F56C6C;border-color:#F56C6C;color:#FFF}.el-button--danger.is-plain:active{background:#dd6161;border-color:#dd6161;color:#FFF;outline:0}.el-button--danger.is-plain.is-disabled,.el-button--danger.is-plain.is-disabled:active,.el-button--danger.is-plain.is-disabled:focus,.el-button--danger.is-plain.is-disabled:hover{color:#f9a7a7;background-color:#fef0f0;border-color:#fde2e2}.el-button--info{color:#FFF;background-color:#909399;border-color:#909399}.el-button--info:focus,.el-button--info:hover{background:#a6a9ad;border-color:#a6a9ad;color:#FFF}.el-button--info.is-active,.el-button--info:active{background:#82848a;border-color:#82848a;color:#FFF}.el-button--info:active{outline:0}.el-button--info.is-disabled,.el-button--info.is-disabled:active,.el-button--info.is-disabled:focus,.el-button--info.is-disabled:hover{color:#FFF;background-color:#c8c9cc;border-color:#c8c9cc}.el-button--info.is-plain{color:#909399;background:#f4f4f5;border-color:#d3d4d6}.el-button--info.is-plain:focus,.el-button--info.is-plain:hover{background:#909399;border-color:#909399;color:#FFF}.el-button--info.is-plain:active{background:#82848a;border-color:#82848a;color:#FFF;outline:0}.el-button--info.is-plain.is-disabled,.el-button--info.is-plain.is-disabled:active,.el-button--info.is-plain.is-disabled:focus,.el-button--info.is-plain.is-disabled:hover{color:#bcbec2;background-color:#f4f4f5;border-color:#e9e9eb}.el-button--text,.el-button--text.is-disabled,.el-button--text.is-disabled:focus,.el-button--text.is-disabled:hover,.el-button--text:active{border-color:transparent}.el-button--medium{padding:10px 20px;font-size:14px;border-radius:4px}.el-button--mini,.el-button--small{font-size:12px;border-radius:3px}.el-button--medium.is-round{padding:10px 20px}.el-button--medium.is-circle{padding:10px}.el-button--small,.el-button--small.is-round{padding:9px 15px}.el-button--small.is-circle{padding:9px}.el-button--mini,.el-button--mini.is-round{padding:5px 15px}.el-button--mini.is-circle{padding:5px}.el-button--text{color:#002FA7;background:0 0;padding-left:0;padding-right:0}.el-button--text:focus,.el-button--text:hover{color:#3359b9;border-color:transparent;background-color:transparent}.el-button--text:active{color:#002a96;background-color:transparent}.el-button-group{display:inline-block;vertical-align:middle}.el-button-group::after,.el-button-group::before{display:table;content:""}.el-button-group::after{clear:both}.el-button-group>.el-button{float:left;position:relative}.el-button-group>.el-button+.el-button{margin-left:0}.el-button-group>.el-button.is-disabled{z-index:1}.el-button-group>.el-button:first-child{border-top-right-radius:0;border-bottom-right-radius:0}.el-button-group>.el-button:last-child{border-top-left-radius:0;border-bottom-left-radius:0}.el-button-group>.el-button:first-child:last-child{border-radius:4px}.el-button-group>.el-button:first-child:last-child.is-round{border-radius:20px}.el-button-group>.el-button:first-child:last-child.is-circle{border-radius:50%}.el-button-group>.el-button:not(:first-child):not(:last-child){border-radius:0}.el-button-group>.el-button:not(:last-child){margin-right:-1px}.el-button-group>.el-button.is-active,.el-button-group>.el-button:active,.el-button-group>.el-button:focus,.el-button-group>.el-button:hover{z-index:1}.el-button-group>.el-dropdown>.el-button{border-top-left-radius:0;border-bottom-left-radius:0;border-left-color:rgba(255,255,255,.5)}.el-button-group .el-button--primary:first-child{border-right-color:rgba(255,255,255,.5)}.el-button-group .el-button--primary:last-child{border-left-color:rgba(255,255,255,.5)}.el-button-group .el-button--primary:not(:first-child):not(:last-child){border-left-color:rgba(255,255,255,.5);border-right-color:rgba(255,255,255,.5)}.el-button-group .el-button--success:first-child{border-right-color:rgba(255,255,255,.5)}.el-button-group .el-button--success:last-child{border-left-color:rgba(255,255,255,.5)}.el-button-group .el-button--success:not(:first-child):not(:last-child){border-left-color:rgba(255,255,255,.5);border-right-color:rgba(255,255,255,.5)}.el-button-group .el-button--warning:first-child{border-right-color:rgba(255,255,255,.5)}.el-button-group .el-button--warning:last-child{border-left-color:rgba(255,255,255,.5)}.el-button-group .el-button--warning:not(:first-child):not(:last-child){border-left-color:rgba(255,255,255,.5);border-right-color:rgba(255,255,255,.5)}.el-button-group .el-button--danger:first-child{border-right-color:rgba(255,255,255,.5)}.el-button-group .el-button--danger:last-child{border-left-color:rgba(255,255,255,.5)}.el-button-group .el-button--danger:not(:first-child):not(:last-child){border-left-color:rgba(255,255,255,.5);border-right-color:rgba(255,255,255,.5)}.el-button-group .el-button--info:first-child{border-right-color:rgba(255,255,255,.5)}.el-button-group .el-button--info:last-child{border-left-color:rgba(255,255,255,.5)}.el-button-group .el-button--info:not(:first-child):not(:last-child){border-left-color:rgba(255,255,255,.5);border-right-color:rgba(255,255,255,.5)}.el-calendar{background-color:#fff}.el-calendar__header{display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-pack:justify;-ms-flex-pack:justify;justify-content:space-between;padding:12px 20px;border-bottom:1px solid #EBEEF5}.el-backtop,.el-page-header{display:-webkit-box;display:-ms-flexbox}.el-calendar__title{color:#000;-ms-flex-item-align:center;align-self:center}.el-calendar__body{padding:12px 20px 35px}.el-calendar-table{table-layout:fixed;width:100%}.el-calendar-table thead th{padding:12px 0;color:#606266;font-weight:400}.el-calendar-table:not(.is-range) td.next,.el-calendar-table:not(.is-range) td.prev{color:#3F3F3F}.el-backtop,.el-calendar-table td.is-today{color:#002FA7}.el-calendar-table td{border-bottom:1px solid #EBEEF5;border-right:1px solid #EBEEF5;vertical-align:top;-webkit-transition:background-color .2s ease;transition:background-color .2s ease}.el-calendar-table td.is-selected{background-color:#F2F8FE}.el-calendar-table tr:first-child td{border-top:1px solid #EBEEF5}.el-calendar-table tr td:first-child{border-left:1px solid #EBEEF5}.el-calendar-table tr.el-calendar-table__row--hide-border td{border-top:none}.el-calendar-table .el-calendar-day{-webkit-box-sizing:border-box;box-sizing:border-box;padding:8px;height:85px}.el-calendar-table .el-calendar-day:hover{cursor:pointer;background-color:#F2F8FE}.el-backtop{position:fixed;background-color:#FFF;width:40px;height:40px;border-radius:50%;display:flex;-webkit-box-align:center;-ms-flex-align:center;align-items:center;-webkit-box-pack:center;-ms-flex-pack:center;justify-content:center;font-size:20px;-webkit-box-shadow:0 0 6px rgba(0,0,0,.12);box-shadow:0 0 6px rgba(0,0,0,.12);cursor:pointer;z-index:5}.el-backtop:hover{background-color:#F2F6FC}.el-page-header{display:flex;line-height:24px}.el-page-header__left{display:-webkit-box;display:-ms-flexbox;display:flex;cursor:pointer;margin-right:40px;position:relative}.el-page-header__left::after{content:"";position:absolute;width:1px;height:16px;right:-20px;top:50%;-webkit-transform:translateY(-50%);transform:translateY(-50%);background-color:#BBB}.el-checkbox,.el-checkbox__input{display:inline-block;position:relative;white-space:nowrap}.el-page-header__left .el-icon-back{font-size:18px;margin-right:6px;-ms-flex-item-align:center;align-self:center}.el-page-header__title{font-size:14px;font-weight:500}.el-page-header__content{font-size:18px;color:#303133}.el-checkbox{color:#606266;font-weight:500;font-size:14px;cursor:pointer;user-select:none;margin-right:30px}.el-checkbox-button__inner,.el-radio{font-weight:500;-moz-user-select:none;-webkit-user-select:none;-ms-user-select:none}.el-checkbox.is-bordered{padding:9px 20px 9px 10px;border-radius:4px;border:1px solid #BBB;-webkit-box-sizing:border-box;box-sizing:border-box;line-height:normal;height:40px}.el-checkbox.is-bordered.is-checked{border-color:#002FA7}.el-checkbox.is-bordered.is-disabled{border-color:#EBEEF5;cursor:not-allowed}.el-checkbox.is-bordered+.el-checkbox.is-bordered{margin-left:10px}.el-checkbox.is-bordered.el-checkbox--medium{padding:7px 20px 7px 10px;border-radius:4px;height:36px}.el-checkbox.is-bordered.el-checkbox--medium .el-checkbox__label{line-height:17px;font-size:14px}.el-checkbox.is-bordered.el-checkbox--medium .el-checkbox__inner{height:14px;width:14px}.el-checkbox.is-bordered.el-checkbox--small{padding:5px 15px 5px 10px;border-radius:3px;height:32px}.el-checkbox.is-bordered.el-checkbox--small .el-checkbox__label{line-height:15px;font-size:12px}.el-checkbox.is-bordered.el-checkbox--small .el-checkbox__inner{height:12px;width:12px}.el-checkbox.is-bordered.el-checkbox--small .el-checkbox__inner::after{height:6px;width:2px}.el-checkbox.is-bordered.el-checkbox--mini{padding:3px 15px 3px 10px;border-radius:3px;height:28px}.el-checkbox.is-bordered.el-checkbox--mini .el-checkbox__label{line-height:12px;font-size:12px}.el-checkbox.is-bordered.el-checkbox--mini .el-checkbox__inner{height:12px;width:12px}.el-checkbox.is-bordered.el-checkbox--mini .el-checkbox__inner::after{height:6px;width:2px}.el-checkbox__input{cursor:pointer;outline:0;line-height:1;vertical-align:middle}.el-checkbox__input.is-disabled .el-checkbox__inner{background-color:#edf2fc;border-color:#BBB;cursor:not-allowed}.el-checkbox__input.is-disabled .el-checkbox__inner::after{cursor:not-allowed;border-color:#3F3F3F}.el-checkbox__input.is-disabled .el-checkbox__inner+.el-checkbox__label{cursor:not-allowed}.el-checkbox__input.is-disabled.is-checked .el-checkbox__inner{background-color:#F2F6FC;border-color:#BBB}.el-checkbox__input.is-disabled.is-checked .el-checkbox__inner::after{border-color:#3F3F3F}.el-checkbox__input.is-disabled.is-indeterminate .el-checkbox__inner{background-color:#F2F6FC;border-color:#BBB}.el-checkbox__input.is-disabled.is-indeterminate .el-checkbox__inner::before{background-color:#3F3F3F;border-color:#3F3F3F}.el-checkbox__input.is-checked .el-checkbox__inner,.el-checkbox__input.is-indeterminate .el-checkbox__inner{background-color:#002FA7;border-color:#002FA7}.el-checkbox__input.is-disabled+span.el-checkbox__label{color:#3F3F3F;cursor:not-allowed}.el-checkbox__input.is-checked .el-checkbox__inner::after{-webkit-transform:rotate(45deg) scaleY(1);transform:rotate(45deg) scaleY(1)}.el-checkbox__input.is-checked+.el-checkbox__label{color:#002FA7}.el-checkbox__input.is-focus .el-checkbox__inner{border-color:#002FA7}.el-checkbox__input.is-indeterminate .el-checkbox__inner::before{content:'';position:absolute;display:block;background-color:#FFF;height:2px;-webkit-transform:scale(.5);transform:scale(.5);left:0;right:0;top:5px}.el-checkbox__input.is-indeterminate .el-checkbox__inner::after{display:none}.el-checkbox__inner{display:inline-block;position:relative;border:1px solid #BBB;border-radius:4px;-webkit-box-sizing:border-box;box-sizing:border-box;width:14px;height:14px;background-color:#FFF;z-index:1;-webkit-transition:border-color .25s cubic-bezier(.71,-.46,.29,1.46),background-color .25s cubic-bezier(.71,-.46,.29,1.46);transition:border-color .25s cubic-bezier(.71,-.46,.29,1.46),background-color .25s cubic-bezier(.71,-.46,.29,1.46)}.el-checkbox__inner:hover{border-color:#002FA7}.el-checkbox__inner::after{-webkit-box-sizing:content-box;box-sizing:content-box;content:"";border:1px solid #FFF;border-left:0;border-top:0;height:7px;left:4px;position:absolute;top:1px;-webkit-transform:rotate(45deg) scaleY(0);transform:rotate(45deg) scaleY(0);width:3px;-webkit-transition:-webkit-transform .15s ease-in .05s;transition:-webkit-transform .15s ease-in .05s;transition:transform .15s ease-in .05s;transition:transform .15s ease-in .05s,-webkit-transform .15s ease-in .05s;-webkit-transform-origin:center;transform-origin:center}.el-checkbox__original{opacity:0;outline:0;position:absolute;margin:0;width:0;height:0;z-index:-1}.el-checkbox-button,.el-checkbox-button__inner{display:inline-block;position:relative}.el-checkbox__label{display:inline-block;padding-left:10px;line-height:19px;font-size:14px}.el-checkbox:last-of-type{margin-right:0}.el-checkbox-button__inner{line-height:1;white-space:nowrap;vertical-align:middle;cursor:pointer;background:#FFF;border:1px solid #BBB;border-left:0;color:#606266;-webkit-appearance:none;text-align:center;-webkit-box-sizing:border-box;box-sizing:border-box;outline:0;margin:0;-webkit-transition:all .3s cubic-bezier(.645,.045,.355,1);transition:all .3s cubic-bezier(.645,.045,.355,1);padding:12px 20px;font-size:14px;border-radius:0}.el-checkbox-button__inner.is-round{padding:12px 20px}.el-checkbox-button__inner:hover{color:#002FA7}.el-checkbox-button__inner [class*=el-icon-]{line-height:.9}.el-radio,.el-radio__input{line-height:1;outline:0;white-space:nowrap}.el-checkbox-button__inner [class*=el-icon-]+span{margin-left:5px}.el-checkbox-button__original{opacity:0;outline:0;position:absolute;margin:0;z-index:-1}.el-radio,.el-radio__inner,.el-radio__input{position:relative;display:inline-block}.el-checkbox-button.is-checked .el-checkbox-button__inner{color:#FFF;background-color:#002FA7;border-color:#002FA7;-webkit-box-shadow:-1px 0 0 0 #6682ca;box-shadow:-1px 0 0 0 #6682ca}.el-checkbox-button.is-checked:first-child .el-checkbox-button__inner{border-left-color:#002FA7}.el-checkbox-button.is-disabled .el-checkbox-button__inner{color:#3F3F3F;cursor:not-allowed;background-image:none;background-color:#FFF;border-color:#EBEEF5;-webkit-box-shadow:none;box-shadow:none}.el-checkbox-button.is-disabled:first-child .el-checkbox-button__inner{border-left-color:#EBEEF5}.el-checkbox-button:first-child .el-checkbox-button__inner{border-left:1px solid #BBB;border-radius:4px 0 0 4px;-webkit-box-shadow:none!important;box-shadow:none!important}.el-checkbox-button.is-focus .el-checkbox-button__inner{border-color:#002FA7}.el-checkbox-button:last-child .el-checkbox-button__inner{border-radius:0 4px 4px 0}.el-checkbox-button--medium .el-checkbox-button__inner{padding:10px 20px;font-size:14px;border-radius:0}.el-checkbox-button--medium .el-checkbox-button__inner.is-round{padding:10px 20px}.el-checkbox-button--small .el-checkbox-button__inner{padding:9px 15px;font-size:12px;border-radius:0}.el-checkbox-button--small .el-checkbox-button__inner.is-round{padding:9px 15px}.el-checkbox-button--mini .el-checkbox-button__inner{padding:5px 15px;font-size:12px;border-radius:0}.el-checkbox-button--mini .el-checkbox-button__inner.is-round{padding:5px 15px}.el-checkbox-group{font-size:0}.el-radio,.el-radio--medium.is-bordered .el-radio__label{font-size:14px}.el-radio{color:#606266;cursor:pointer;margin-right:30px}.el-cascader-node>.el-radio,.el-radio:last-child{margin-right:0}.el-radio.is-bordered{padding:12px 20px 0 10px;border-radius:4px;border:1px solid #BBB;-webkit-box-sizing:border-box;box-sizing:border-box;height:40px}.el-radio.is-bordered.is-checked{border-color:#002FA7}.el-radio.is-bordered.is-disabled{cursor:not-allowed;border-color:#EBEEF5}.el-radio__input.is-disabled .el-radio__inner,.el-radio__input.is-disabled.is-checked .el-radio__inner{background-color:#F5F7FA;border-color:#E4E7ED}.el-radio.is-bordered+.el-radio.is-bordered{margin-left:10px}.el-radio--medium.is-bordered{padding:10px 20px 0 10px;border-radius:4px;height:36px}.el-radio--mini.is-bordered .el-radio__label,.el-radio--small.is-bordered .el-radio__label{font-size:12px}.el-radio--medium.is-bordered .el-radio__inner{height:14px;width:14px}.el-radio--small.is-bordered{padding:8px 15px 0 10px;border-radius:3px;height:32px}.el-radio--small.is-bordered .el-radio__inner{height:12px;width:12px}.el-radio--mini.is-bordered{padding:6px 15px 0 10px;border-radius:3px;height:28px}.el-radio--mini.is-bordered .el-radio__inner{height:12px;width:12px}.el-radio__input{cursor:pointer;vertical-align:middle}.el-radio__input.is-disabled .el-radio__inner{cursor:not-allowed}.el-radio__input.is-disabled .el-radio__inner::after{cursor:not-allowed;background-color:#F5F7FA}.el-radio__input.is-disabled .el-radio__inner+.el-radio__label{cursor:not-allowed}.el-radio__input.is-disabled.is-checked .el-radio__inner::after{background-color:#3F3F3F}.el-radio__input.is-disabled+span.el-radio__label{color:#3F3F3F;cursor:not-allowed}.el-radio__input.is-checked .el-radio__inner{border-color:#002FA7;background:#002FA7}.el-radio__input.is-checked .el-radio__inner::after{-webkit-transform:translate(-50%,-50%) scale(1);transform:translate(-50%,-50%) scale(1)}.el-radio__input.is-checked+.el-radio__label{color:#002FA7}.el-radio__input.is-focus .el-radio__inner{border-color:#002FA7}.el-radio__inner{border:1px solid #BBB;border-radius:100%;width:14px;height:14px;background-color:#FFF;cursor:pointer;-webkit-box-sizing:border-box;box-sizing:border-box}.el-radio__inner:hover{border-color:#002FA7}.el-radio__inner::after{width:4px;height:4px;border-radius:100%;background-color:#FFF;content:"";position:absolute;left:50%;top:50%;-webkit-transform:translate(-50%,-50%) scale(0);transform:translate(-50%,-50%) scale(0);-webkit-transition:-webkit-transform .15s ease-in;transition:-webkit-transform .15s ease-in;transition:transform .15s ease-in;transition:transform .15s ease-in,-webkit-transform .15s ease-in}.el-radio__original{opacity:0;outline:0;position:absolute;z-index:-1;top:0;left:0;right:0;bottom:0;margin:0}.el-radio:focus:not(.is-focus):not(:active):not(.is-disabled) .el-radio__inner{-webkit-box-shadow:0 0 2px 2px #002FA7;box-shadow:0 0 2px 2px #002FA7}.el-radio__label{font-size:14px;padding-left:10px}.el-scrollbar{overflow:hidden;position:relative}.el-scrollbar:active>.el-scrollbar__bar,.el-scrollbar:focus>.el-scrollbar__bar,.el-scrollbar:hover>.el-scrollbar__bar{opacity:1;-webkit-transition:opacity 340ms ease-out;transition:opacity 340ms ease-out}.el-scrollbar__wrap{overflow:scroll;height:100%}.el-scrollbar__wrap--hidden-default{scrollbar-width:none}.el-scrollbar__wrap--hidden-default::-webkit-scrollbar{width:0;height:0}.el-scrollbar__thumb{position:relative;display:block;width:0;height:0;cursor:pointer;border-radius:inherit;background-color:rgba(144,147,153,.3);-webkit-transition:.3s background-color;transition:.3s background-color}.el-scrollbar__thumb:hover{background-color:rgba(144,147,153,.5)}.el-scrollbar__bar{position:absolute;right:2px;bottom:2px;z-index:1;border-radius:4px;opacity:0;-webkit-transition:opacity 120ms ease-out;transition:opacity 120ms ease-out}.el-scrollbar__bar.is-vertical{width:6px;top:2px}.el-scrollbar__bar.is-vertical>div{width:100%}.el-scrollbar__bar.is-horizontal{height:6px;left:2px}.el-scrollbar__bar.is-horizontal>div{height:100%}.el-cascader-panel{display:-webkit-box;display:-ms-flexbox;display:flex;border-radius:4px;font-size:14px}.el-cascader-panel.is-bordered{border:1px solid #E4E7ED;border-radius:4px}.el-cascader-menu{min-width:180px;-webkit-box-sizing:border-box;box-sizing:border-box;color:#606266;border-right:solid 1px #E4E7ED}.el-cascader-menu:last-child{border-right:none}.el-cascader-menu:last-child .el-cascader-node{padding-right:20px}.el-cascader-menu__wrap{height:204px}.el-cascader-menu__list{position:relative;min-height:100%;margin:0;padding:6px 0;list-style:none;-webkit-box-sizing:border-box;box-sizing:border-box}.el-avatar,.el-drawer{-webkit-box-sizing:border-box;overflow:hidden}.el-cascader-menu__hover-zone{position:absolute;top:0;left:0;width:100%;height:100%;pointer-events:none}.el-cascader-menu__empty-text{position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);transform:translate(-50%,-50%);text-align:center;color:#3F3F3F}.el-cascader-node{position:relative;display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-align:center;-ms-flex-align:center;align-items:center;padding:0 30px 0 20px;height:34px;line-height:34px;outline:0}.el-cascader-node.is-selectable.in-active-path{color:#606266}.el-cascader-node.in-active-path,.el-cascader-node.is-active,.el-cascader-node.is-selectable.in-checked-path{color:#002FA7;font-weight:700}.el-cascader-node:not(.is-disabled){cursor:pointer}.el-cascader-node:not(.is-disabled):focus,.el-cascader-node:not(.is-disabled):hover{background:#F5F7FA}.el-cascader-node.is-disabled{color:#3F3F3F;cursor:not-allowed}.el-cascader-node__prefix{position:absolute;left:10px}.el-cascader-node__postfix{position:absolute;right:10px}.el-cascader-node__label{-webkit-box-flex:1;-ms-flex:1;flex:1;padding:0 10px;white-space:nowrap;overflow:hidden;text-overflow:ellipsis}.el-cascader-node>.el-radio .el-radio__label{padding-left:0}.el-avatar{display:inline-block;box-sizing:border-box;text-align:center;color:#fff;background:#C0C4CC;width:40px;height:40px;line-height:40px;font-size:14px}.el-avatar>img{display:block;height:100%;vertical-align:middle}.el-drawer,.el-drawer__header{display:-webkit-box;display:-ms-flexbox}.el-avatar--circle{border-radius:50%}.el-avatar--square{border-radius:4px}.el-avatar--icon{font-size:18px}.el-avatar--large{width:40px;height:40px;line-height:40px}.el-avatar--medium{width:36px;height:36px;line-height:36px}.el-avatar--small{width:28px;height:28px;line-height:28px}.el-drawer.btt,.el-drawer.ttb,.el-drawer__container{left:0;right:0;width:100%}.el-drawer.ltr,.el-drawer.rtl,.el-drawer__container{top:0;bottom:0;height:100%}@-webkit-keyframes el-drawer-fade-in{0%{opacity:0}100%{opacity:1}}@keyframes el-drawer-fade-in{0%{opacity:0}100%{opacity:1}}@-webkit-keyframes rtl-drawer-in{0%{-webkit-transform:translate(100%,0);transform:translate(100%,0)}100%{-webkit-transform:translate(0,0);transform:translate(0,0)}}@keyframes rtl-drawer-in{0%{-webkit-transform:translate(100%,0);transform:translate(100%,0)}100%{-webkit-transform:translate(0,0);transform:translate(0,0)}}@-webkit-keyframes rtl-drawer-out{0%{-webkit-transform:translate(0,0);transform:translate(0,0)}100%{-webkit-transform:translate(100%,0);transform:translate(100%,0)}}@keyframes rtl-drawer-out{0%{-webkit-transform:translate(0,0);transform:translate(0,0)}100%{-webkit-transform:translate(100%,0);transform:translate(100%,0)}}@-webkit-keyframes ltr-drawer-in{0%{-webkit-transform:translate(-100%,0);transform:translate(-100%,0)}100%{-webkit-transform:translate(0,0);transform:translate(0,0)}}@keyframes ltr-drawer-in{0%{-webkit-transform:translate(-100%,0);transform:translate(-100%,0)}100%{-webkit-transform:translate(0,0);transform:translate(0,0)}}@-webkit-keyframes ltr-drawer-out{0%{-webkit-transform:translate(0,0);transform:translate(0,0)}100%{-webkit-transform:translate(-100%,0);transform:translate(-100%,0)}}@keyframes ltr-drawer-out{0%{-webkit-transform:translate(0,0);transform:translate(0,0)}100%{-webkit-transform:translate(-100%,0);transform:translate(-100%,0)}}@-webkit-keyframes ttb-drawer-in{0%{-webkit-transform:translate(0,-100%);transform:translate(0,-100%)}100%{-webkit-transform:translate(0,0);transform:translate(0,0)}}@keyframes ttb-drawer-in{0%{-webkit-transform:translate(0,-100%);transform:translate(0,-100%)}100%{-webkit-transform:translate(0,0);transform:translate(0,0)}}@-webkit-keyframes ttb-drawer-out{0%{-webkit-transform:translate(0,0);transform:translate(0,0)}100%{-webkit-transform:translate(0,-100%);transform:translate(0,-100%)}}@keyframes ttb-drawer-out{0%{-webkit-transform:translate(0,0);transform:translate(0,0)}100%{-webkit-transform:translate(0,-100%);transform:translate(0,-100%)}}@-webkit-keyframes btt-drawer-in{0%{-webkit-transform:translate(0,100%);transform:translate(0,100%)}100%{-webkit-transform:translate(0,0);transform:translate(0,0)}}@keyframes btt-drawer-in{0%{-webkit-transform:translate(0,100%);transform:translate(0,100%)}100%{-webkit-transform:translate(0,0);transform:translate(0,0)}}@-webkit-keyframes btt-drawer-out{0%{-webkit-transform:translate(0,0);transform:translate(0,0)}100%{-webkit-transform:translate(0,100%);transform:translate(0,100%)}}@keyframes btt-drawer-out{0%{-webkit-transform:translate(0,0);transform:translate(0,0)}100%{-webkit-transform:translate(0,100%);transform:translate(0,100%)}}.el-drawer{position:absolute;box-sizing:border-box;background-color:#FFF;display:flex;-ms-flex-direction:column;flex-direction:column;-webkit-box-shadow:0 8px 10px -5px rgba(0,0,0,.2),0 16px 24px 2px rgba(0,0,0,.14),0 6px 30px 5px rgba(0,0,0,.12);box-shadow:0 8px 10px -5px rgba(0,0,0,.2),0 16px 24px 2px rgba(0,0,0,.14),0 6px 30px 5px rgba(0,0,0,.12)}.el-drawer.rtl{-webkit-animation:rtl-drawer-out .3s;animation:rtl-drawer-out .3s;right:0}.el-drawer__open .el-drawer.rtl{-webkit-animation:rtl-drawer-in .3s 1ms;animation:rtl-drawer-in .3s 1ms}.el-drawer.ltr{-webkit-animation:ltr-drawer-out .3s;animation:ltr-drawer-out .3s;left:0}.el-drawer__open .el-drawer.ltr{-webkit-animation:ltr-drawer-in .3s 1ms;animation:ltr-drawer-in .3s 1ms}.el-drawer.ttb{-webkit-animation:ttb-drawer-out .3s;animation:ttb-drawer-out .3s;top:0}.el-drawer__open .el-drawer.ttb{-webkit-animation:ttb-drawer-in .3s 1ms;animation:ttb-drawer-in .3s 1ms}.el-drawer.btt{-webkit-animation:btt-drawer-out .3s;animation:btt-drawer-out .3s;bottom:0}.el-drawer__open .el-drawer.btt{-webkit-animation:btt-drawer-in .3s 1ms;animation:btt-drawer-in .3s 1ms}.el-drawer__wrapper{position:fixed;top:0;right:0;bottom:0;left:0;overflow:hidden;margin:0}.el-drawer__header{-webkit-box-align:center;-ms-flex-align:center;align-items:center;color:#72767b;display:flex;margin-bottom:32px;padding:20px 20px 0}.el-drawer__header>:first-child{-webkit-box-flex:1;-ms-flex:1;flex:1}.el-drawer__title{margin:0;-webkit-box-flex:1;-ms-flex:1;flex:1;line-height:inherit;font-size:1rem}.el-drawer__close-btn{border:none;cursor:pointer;font-size:20px;color:inherit;background-color:transparent}.el-drawer__body{-webkit-box-flex:1;-ms-flex:1;flex:1}.el-drawer__body>*{-webkit-box-sizing:border-box;box-sizing:border-box}.el-drawer__container{position:relative}.el-drawer-fade-enter-active{-webkit-animation:el-drawer-fade-in .3s;animation:el-drawer-fade-in .3s}.el-drawer-fade-leave-active{animation:el-drawer-fade-in .3s reverse}.el-popconfirm__main{display:-webkit-box;display:-ms-flexbox;display:flex;-webkit-box-align:center;-ms-flex-align:center;align-items:center}.el-popconfirm__icon{margin-right:5px}.el-popconfirm__action{text-align:right;margin:0} \ No newline at end of file diff --git a/docs/.vuepress/public/submenu-arrow.svg b/docs/.vuepress/public/submenu-arrow.svg new file mode 100644 index 0000000000000000000000000000000000000000..b1e041263a5c55d307ffdcee5626eb1b503ac899 --- /dev/null +++ b/docs/.vuepress/public/submenu-arrow.svg @@ -0,0 +1,28 @@ + + + 编组 + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/.vuepress/sitePlugin.js b/docs/.vuepress/sitePlugin.js new file mode 100644 index 0000000000000000000000000000000000000000..525d827c955d3647e1d1f2f6ce002706d3783e3c --- /dev/null +++ b/docs/.vuepress/sitePlugin.js @@ -0,0 +1,18 @@ +module.exports = (options = {}, ctx) => { + return { + enhanceAppFiles() { + let pages = [] + ctx.pages.forEach(item => { + pages.push({ + path: item.regularPath, + frontmatter: item.frontmatter + }) + }); + pages = JSON.stringify(pages); + return { + name: 'dynamic-code', + content: `export default ({ Vue }) => { Vue.prototype.$sitePages = ${pages}}` + } + } + } +} \ No newline at end of file diff --git a/docs/.vuepress/theme/components/CustomFooter.vue b/docs/.vuepress/theme/components/CustomFooter.vue new file mode 100644 index 0000000000000000000000000000000000000000..992c806292eb52e82d87b228c10d1a2d7547df84 --- /dev/null +++ b/docs/.vuepress/theme/components/CustomFooter.vue @@ -0,0 +1,148 @@ + + + + + diff --git a/docs/.vuepress/theme/components/CustomHeader.vue b/docs/.vuepress/theme/components/CustomHeader.vue new file mode 100644 index 0000000000000000000000000000000000000000..2aea47b1368b9bc94d960575779dca0e0905e245 --- /dev/null +++ b/docs/.vuepress/theme/components/CustomHeader.vue @@ -0,0 +1,744 @@ + + + + + diff --git a/docs/.vuepress/theme/global-components/Badge.vue b/docs/.vuepress/theme/global-components/Badge.vue new file mode 100644 index 0000000000000000000000000000000000000000..53951f9d505dfb5ece39c10c5656db6cfd0915d0 --- /dev/null +++ b/docs/.vuepress/theme/global-components/Badge.vue @@ -0,0 +1,44 @@ + + + diff --git a/docs/.vuepress/theme/index.js b/docs/.vuepress/theme/index.js new file mode 100644 index 0000000000000000000000000000000000000000..baaf102ba77679ad628a048ee533986f6e8bc870 --- /dev/null +++ b/docs/.vuepress/theme/index.js @@ -0,0 +1,59 @@ +const path = require('path') + +// Theme API. +module.exports = (options, ctx) => { + const { themeConfig, siteConfig } = ctx + + // resolve algolia + const isAlgoliaSearch = ( + themeConfig.algolia + || Object + .keys(siteConfig.locales && themeConfig.locales || {}) + .some(base => themeConfig.locales[base].algolia) + ) + + const enableSmoothScroll = themeConfig.smoothScroll === true + + return { + alias () { + return { + '@AlgoliaSearchBox': isAlgoliaSearch + ? path.resolve(__dirname, 'components/AlgoliaSearchBox.vue') + : path.resolve(__dirname, 'noopModule.js') + } + }, + + plugins: [ + ['@vuepress/active-header-links', options.activeHeaderLinks], + '@vuepress/search', + '@vuepress/plugin-nprogress', + ['container', { + type: 'tip', + defaultTitle: { + '/': 'TIP', + '/zh/': '提示' + } + }], + ['container', { + type: 'warning', + defaultTitle: { + '/': 'WARNING', + '/zh/': '注意' + } + }], + ['container', { + type: 'danger', + defaultTitle: { + '/': 'WARNING', + '/zh/': '警告' + } + }], + ['container', { + type: 'details', + before: info => `
${info ? `${info}` : ''}\n`, + after: () => '
\n' + }], + ['smooth-scroll', enableSmoothScroll] + ] + } +} diff --git a/docs/.vuepress/theme/layouts/404.vue b/docs/.vuepress/theme/layouts/404.vue new file mode 100644 index 0000000000000000000000000000000000000000..6d4f4a0491ff0c910d9ac8d925763a7d9df96dee --- /dev/null +++ b/docs/.vuepress/theme/layouts/404.vue @@ -0,0 +1,49 @@ + + + + + diff --git a/docs/.vuepress/theme/layouts/DocDetails.vue b/docs/.vuepress/theme/layouts/DocDetails.vue new file mode 100644 index 0000000000000000000000000000000000000000..b0ba40272cd8daebb8cd116db830a8fd73704c6e --- /dev/null +++ b/docs/.vuepress/theme/layouts/DocDetails.vue @@ -0,0 +1,622 @@ + + + + + diff --git a/docs/.vuepress/theme/layouts/Layout.vue b/docs/.vuepress/theme/layouts/Layout.vue new file mode 100644 index 0000000000000000000000000000000000000000..497b916121d18585e85decf984f373dad35662b6 --- /dev/null +++ b/docs/.vuepress/theme/layouts/Layout.vue @@ -0,0 +1,55 @@ + + + + diff --git a/docs/.vuepress/theme/noopModule.js b/docs/.vuepress/theme/noopModule.js new file mode 100644 index 0000000000000000000000000000000000000000..b1c6ea436a540020ff61f01dea449d5b39367b27 --- /dev/null +++ b/docs/.vuepress/theme/noopModule.js @@ -0,0 +1 @@ +export default {} diff --git a/docs/.vuepress/theme/styles/arrow.styl b/docs/.vuepress/theme/styles/arrow.styl new file mode 100644 index 0000000000000000000000000000000000000000..20bffc0dc87339fa3b52d35e5ea17995d5cdb9f8 --- /dev/null +++ b/docs/.vuepress/theme/styles/arrow.styl @@ -0,0 +1,22 @@ +@require './config' + +.arrow + display inline-block + width 0 + height 0 + &.up + border-left 4px solid transparent + border-right 4px solid transparent + border-bottom 6px solid $arrowBgColor + &.down + border-left 4px solid transparent + border-right 4px solid transparent + border-top 6px solid $arrowBgColor + &.right + border-top 4px solid transparent + border-bottom 4px solid transparent + border-left 6px solid $arrowBgColor + &.left + border-top 4px solid transparent + border-bottom 4px solid transparent + border-right 6px solid $arrowBgColor diff --git a/docs/.vuepress/theme/styles/code.styl b/docs/.vuepress/theme/styles/code.styl new file mode 100644 index 0000000000000000000000000000000000000000..9d3aa9a54130c6fef1c3b818d7e6898f4231975b --- /dev/null +++ b/docs/.vuepress/theme/styles/code.styl @@ -0,0 +1,137 @@ +{$contentClass} + code + color lighten($textColor, 20%) + padding 0.25rem 0.5rem + margin 0 + font-size 0.85em + background-color rgba(27,31,35,0.05) + border-radius 3px + .token + &.deleted + color #EC5975 + &.inserted + color $accentColor + +{$contentClass} + pre, pre[class*="language-"] + line-height 1.4 + padding 1.25rem 1.5rem + margin 0.85rem 0 + background-color $codeBgColor + border-radius 6px + overflow auto + code + color #fff + padding 0 + background-color transparent + border-radius 0 + +div[class*="language-"] + position relative + background-color $codeBgColor + border-radius 6px + .highlight-lines + user-select none + padding-top 1.3rem + position absolute + top 0 + left 0 + width 100% + line-height 1.4 + .highlighted + background-color rgba(0, 0, 0, 66%) + pre, pre[class*="language-"] + background transparent + position relative + z-index 1 + &::before + position absolute + z-index 3 + top 0.8em + right 1em + font-size 0.75rem + color rgba(255, 255, 255, 0.4) + &:not(.line-numbers-mode) + .line-numbers-wrapper + display none + &.line-numbers-mode + .highlight-lines .highlighted + position relative + &:before + content ' ' + position absolute + z-index 3 + left 0 + top 0 + display block + width $lineNumbersWrapperWidth + height 100% + background-color rgba(0, 0, 0, 66%) + pre + padding-left $lineNumbersWrapperWidth + 1 rem + vertical-align middle + .line-numbers-wrapper + position absolute + top 0 + width $lineNumbersWrapperWidth + text-align center + color rgba(255, 255, 255, 0.3) + padding 1.25rem 0 + line-height 1.4 + br + user-select none + .line-number + position relative + z-index 4 + user-select none + font-size 0.85em + &::after + content '' + position absolute + z-index 2 + top 0 + left 0 + width $lineNumbersWrapperWidth + height 100% + border-radius 6px 0 0 6px + border-right 1px solid rgba(0, 0, 0, 66%) + background-color $codeBgColor + + +for lang in $codeLang + div{'[class~="language-' + lang + '"]'} + &:before + content ('' + lang) + +div[class~="language-javascript"] + &:before + content "js" + +div[class~="language-typescript"] + &:before + content "ts" + +div[class~="language-markup"] + &:before + content "html" + +div[class~="language-markdown"] + &:before + content "md" + +div[class~="language-json"]:before + content "json" + +div[class~="language-ruby"]:before + content "rb" + +div[class~="language-python"]:before + content "py" + +div[class~="language-bash"]:before + content "sh" + +div[class~="language-php"]:before + content "php" + +@import '~prismjs/themes/prism-tomorrow.css' diff --git a/docs/.vuepress/theme/styles/config.styl b/docs/.vuepress/theme/styles/config.styl new file mode 100644 index 0000000000000000000000000000000000000000..9e403210fd385f823fbf9796fd51b4fc4f1843aa --- /dev/null +++ b/docs/.vuepress/theme/styles/config.styl @@ -0,0 +1 @@ +$contentClass = '.theme-default-content' diff --git a/docs/.vuepress/theme/styles/custom-blocks.styl b/docs/.vuepress/theme/styles/custom-blocks.styl new file mode 100644 index 0000000000000000000000000000000000000000..5b868166a434c112c09b5b2d525521f6de2c8d81 --- /dev/null +++ b/docs/.vuepress/theme/styles/custom-blocks.styl @@ -0,0 +1,44 @@ +.custom-block + .custom-block-title + font-weight 600 + margin-bottom -0.4rem + &.tip, &.warning, &.danger + padding .1rem 1.5rem + border-left-width .5rem + border-left-style solid + margin 1rem 0 + &.tip + background-color #f3f5f7 + border-color #42b983 + &.warning + background-color rgba(255,229,100,.3) + border-color darken(#ffe564, 35%) + color darken(#ffe564, 70%) + .custom-block-title + color darken(#ffe564, 50%) + a + color $textColor + &.danger + background-color #ffe6e6 + border-color darken(red, 20%) + color darken(red, 70%) + .custom-block-title + color darken(red, 40%) + a + color $textColor + &.details + display block + position relative + border-radius 2px + margin 1.6em 0 + padding 1.6em + background-color #eee + h4 + margin-top 0 + figure, p + &:last-child + margin-bottom 0 + padding-bottom 0 + summary + outline none + cursor pointer diff --git a/docs/.vuepress/theme/styles/index.styl b/docs/.vuepress/theme/styles/index.styl new file mode 100644 index 0000000000000000000000000000000000000000..976bfb04479e199d178ebce67f08060e62e75ba3 --- /dev/null +++ b/docs/.vuepress/theme/styles/index.styl @@ -0,0 +1,201 @@ +@require './config' +@require './code' +@require './custom-blocks' +@require './arrow' +@require './wrapper' +@require './toc' + +html, body + padding 0 + margin 0 + background-color #fff + +body + font-family -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen, Ubuntu, Cantarell, "Fira Sans", "Droid Sans", "Helvetica Neue", sans-serif + -webkit-font-smoothing antialiased + -moz-osx-font-smoothing grayscale + font-size 16px + color $textColor + +.page + padding-left $sidebarWidth + +.navbar + position fixed + z-index 20 + top 0 + left 0 + right 0 + height $navbarHeight + background-color #fff + box-sizing border-box + border-bottom 1px solid $borderColor + +.sidebar-mask + position fixed + z-index 9 + top 0 + left 0 + width 100vw + height 100vh + display none + +.sidebar + font-size 16px + background-color #fff + width $sidebarWidth + position fixed + z-index 10 + margin 0 + top $navbarHeight + left 0 + bottom 0 + box-sizing border-box + border-right 1px solid $borderColor + overflow-y auto + +{$contentClass}:not(.custom) + @extend $wrapper + > *:first-child + margin-top $navbarHeight + + a:hover + text-decoration underline + + p.demo + padding 1rem 1.5rem + border 1px solid #ddd + border-radius 4px + + img + max-width 100% + +{$contentClass}.custom + padding 0 + margin 0 + + img + max-width 100% + +a + font-weight 500 + color $accentColor + text-decoration none + +p a code + font-weight 400 + color $accentColor + +kbd + background #eee + border solid 0.15rem #ddd + border-bottom solid 0.25rem #ddd + border-radius 0.15rem + padding 0 0.15em + +blockquote + font-size 1rem + color #999; + border-left .2rem solid #dfe2e5 + margin 1rem 0 + padding .25rem 0 .25rem 1rem + + & > p + margin 0 + +ul, ol + padding-left 1.2em + +strong + font-weight 600 + +h1, h2, h3, h4, h5, h6 + font-weight 600 + line-height 1.25 + + {$contentClass}:not(.custom) > & + margin-top (0.5rem - $navbarHeight) + padding-top ($navbarHeight + 1rem) + margin-bottom 0 + + &:first-child + margin-top -1.5rem + margin-bottom 1rem + + + p, + pre, + .custom-block + margin-top 2rem + + &:hover .header-anchor + opacity: 1 + +h1 + font-size 2.2rem + +h2 + font-size 1.65rem + padding-bottom .3rem + border-bottom 1px solid $borderColor + +h3 + font-size 1.35rem + +a.header-anchor + font-size 0.85em + float left + margin-left -0.87em + padding-right 0.23em + margin-top 0.125em + opacity 0 + + &:hover + text-decoration none + +code, kbd, .line-number + font-family source-code-pro, Menlo, Monaco, Consolas, "Courier New", monospace + +p, ul, ol + line-height 1.7 + +hr + border 0 + border-top 1px solid $borderColor + +table + border-collapse collapse + margin 1rem 0 + display: block + overflow-x: auto + +tr + border-top 1px solid #dfe2e5 + + &:nth-child(2n) + background-color #f6f8fa + +th, td + border 1px solid #dfe2e5 + padding .6em 1em + +.theme-container + &.sidebar-open + .sidebar-mask + display: block + + &.no-navbar + {$contentClass}:not(.custom) > h1, h2, h3, h4, h5, h6 + margin-top 1.5rem + padding-top 0 + + .sidebar + top 0 + + +@media (min-width: ($MQMobile + 1px)) + .theme-container.no-sidebar + .sidebar + display none + + .page + padding-left 0 + +@require 'mobile.styl' diff --git a/docs/.vuepress/theme/styles/mobile.styl b/docs/.vuepress/theme/styles/mobile.styl new file mode 100644 index 0000000000000000000000000000000000000000..f5bd32739d774a8d69a60ae282630eaf2ac2b72f --- /dev/null +++ b/docs/.vuepress/theme/styles/mobile.styl @@ -0,0 +1,37 @@ +@require './config' + +$mobileSidebarWidth = $sidebarWidth * 0.82 + +// narrow desktop / iPad +@media (max-width: $MQNarrow) + .sidebar + font-size 15px + width $mobileSidebarWidth + .page + padding-left $mobileSidebarWidth + +// wide mobile +@media (max-width: $MQMobile) + .sidebar + top 0 + padding-top $navbarHeight + transform translateX(-100%) + transition transform .2s ease + .page + padding-left 0 + .theme-container + &.sidebar-open + .sidebar + transform translateX(0) + &.no-navbar + .sidebar + padding-top: 0 + +// narrow mobile +@media (max-width: $MQMobileNarrow) + h1 + font-size 1.9rem + {$contentClass} + div[class*="language-"] + margin 0.85rem -1.5rem + border-radius 0 diff --git a/docs/.vuepress/theme/styles/toc.styl b/docs/.vuepress/theme/styles/toc.styl new file mode 100644 index 0000000000000000000000000000000000000000..d3e71069ba79f12ab46681be457be98e88156184 --- /dev/null +++ b/docs/.vuepress/theme/styles/toc.styl @@ -0,0 +1,3 @@ +.table-of-contents + .badge + vertical-align middle diff --git a/docs/.vuepress/theme/styles/wrapper.styl b/docs/.vuepress/theme/styles/wrapper.styl new file mode 100644 index 0000000000000000000000000000000000000000..a99262c71ab374f473eeccd01c1cd970c3ccf89c --- /dev/null +++ b/docs/.vuepress/theme/styles/wrapper.styl @@ -0,0 +1,9 @@ +$wrapper + max-width $contentWidth + margin 0 auto + padding 2rem 2.5rem + @media (max-width: $MQNarrow) + padding 2rem + @media (max-width: $MQMobileNarrow) + padding 1.5rem + diff --git a/docs/.vuepress/theme/util/index.js b/docs/.vuepress/theme/util/index.js new file mode 100644 index 0000000000000000000000000000000000000000..4433bb3c5fad61ec8a51d1cbe6ba485e92847802 --- /dev/null +++ b/docs/.vuepress/theme/util/index.js @@ -0,0 +1,243 @@ +export const hashRE = /#.*$/ +export const extRE = /\.(md|html)$/ +export const endingSlashRE = /\/$/ +export const outboundRE = /^[a-z]+:/i + +export function normalize (path) { + return decodeURI(path) + .replace(hashRE, '') + .replace(extRE, '') +} + +export function getHash (path) { + const match = path.match(hashRE) + if (match) { + return match[0] + } +} + +export function isExternal (path) { + return outboundRE.test(path) +} + +export function isMailto (path) { + return /^mailto:/.test(path) +} + +export function isTel (path) { + return /^tel:/.test(path) +} + +export function ensureExt (path) { + if (isExternal(path)) { + return path + } + const hashMatch = path.match(hashRE) + const hash = hashMatch ? hashMatch[0] : '' + const normalized = normalize(path) + + if (endingSlashRE.test(normalized)) { + return path + } + return normalized + '.html' + hash +} + +export function isActive (route, path) { + const routeHash = decodeURIComponent(route.hash) + const linkHash = getHash(path) + if (linkHash && routeHash !== linkHash) { + return false + } + const routePath = normalize(route.path) + const pagePath = normalize(path) + return routePath === pagePath +} + +export function resolvePage (pages, rawPath, base) { + if (isExternal(rawPath)) { + return { + type: 'external', + path: rawPath + } + } + if (base) { + rawPath = resolvePath(rawPath, base) + } + const path = normalize(rawPath) + for (let i = 0; i < pages.length; i++) { + if (normalize(pages[i].regularPath) === path) { + return Object.assign({}, pages[i], { + type: 'page', + path: ensureExt(pages[i].path) + }) + } + } + console.error(`[vuepress] No matching page found for sidebar item "${rawPath}"`) + return {} +} + +function resolvePath (relative, base, append) { + const firstChar = relative.charAt(0) + if (firstChar === '/') { + return relative + } + + if (firstChar === '?' || firstChar === '#') { + return base + relative + } + + const stack = base.split('/') + + // remove trailing segment if: + // - not appending + // - appending to trailing slash (last segment is empty) + if (!append || !stack[stack.length - 1]) { + stack.pop() + } + + // resolve relative path + const segments = relative.replace(/^\//, '').split('/') + for (let i = 0; i < segments.length; i++) { + const segment = segments[i] + if (segment === '..') { + stack.pop() + } else if (segment !== '.') { + stack.push(segment) + } + } + + // ensure leading slash + if (stack[0] !== '') { + stack.unshift('') + } + + return stack.join('/') +} + +/** + * @param { Page } page + * @param { string } regularPath + * @param { SiteData } site + * @param { string } localePath + * @returns { SidebarGroup } + */ +export function resolveSidebarItems (page, regularPath, site, localePath) { + const { pages, themeConfig } = site + + const localeConfig = localePath && themeConfig.locales + ? themeConfig.locales[localePath] || themeConfig + : themeConfig + + const pageSidebarConfig = page.frontmatter.sidebar || localeConfig.sidebar || themeConfig.sidebar + if (pageSidebarConfig === 'auto') { + return resolveHeaders(page) + } + + const sidebarConfig = localeConfig.sidebar || themeConfig.sidebar + if (!sidebarConfig) { + return [] + } else { + const { base, config } = resolveMatchingConfig(regularPath, sidebarConfig) + if (config === 'auto') { + return resolveHeaders(page) + } + return config + ? config.map(item => resolveItem(item, pages, base)) + : [] + } +} + +/** + * @param { Page } page + * @returns { SidebarGroup } + */ +function resolveHeaders (page) { + const headers = groupHeaders(page.headers || []) + return [{ + type: 'group', + collapsable: false, + title: page.title, + path: null, + children: headers.map(h => ({ + type: 'auto', + title: h.title, + basePath: page.path, + path: page.path + '#' + h.slug, + children: h.children || [] + })) + }] +} + +export function groupHeaders (headers) { + // group h3s under h2 + headers = headers.map(h => Object.assign({}, h)) + let lastH2 + headers.forEach(h => { + if (h.level === 2) { + lastH2 = h + } else if (lastH2) { + (lastH2.children || (lastH2.children = [])).push(h) + } + }) + return headers.filter(h => h.level === 2) +} + +export function resolveNavLinkItem (linkItem) { + return Object.assign(linkItem, { + type: linkItem.items && linkItem.items.length ? 'links' : 'link' + }) +} + +/** + * @param { Route } route + * @param { Array | Array | [link: string]: SidebarConfig } config + * @returns { base: string, config: SidebarConfig } + */ +export function resolveMatchingConfig (regularPath, config) { + if (Array.isArray(config)) { + return { + base: '/', + config: config + } + } + for (const base in config) { + if (ensureEndingSlash(regularPath).indexOf(encodeURI(base)) === 0) { + return { + base, + config: config[base] + } + } + } + return {} +} + +function ensureEndingSlash (path) { + return /(\.html|\/)$/.test(path) + ? path + : path + '/' +} + +function resolveItem (item, pages, base, groupDepth = 1) { + if (typeof item === 'string') { + return resolvePage(pages, item, base) + } else if (Array.isArray(item)) { + return Object.assign(resolvePage(pages, item[0], base), { + title: item[1] + }) + } else { + const children = item.children || [] + if (children.length === 0 && item.path) { + return Object.assign(resolvePage(pages, item.path, base), { + title: item.title + }) + } + return { + type: 'group', + path: item.path, + title: item.title, + sidebarDepth: item.sidebarDepth, + children: children.map(child => resolveItem(child, pages, base, groupDepth + 1)), + collapsable: item.collapsable !== false + } + } +} diff --git a/docs/en/README.md b/docs/en/README.md new file mode 100644 index 0000000000000000000000000000000000000000..220ce21228f13476fde1425338e6edfb50c7b431 --- /dev/null +++ b/docs/en/README.md @@ -0,0 +1,4 @@ +--- +title: "openEuler" + +--- \ No newline at end of file diff --git a/content/en/docs/A-Tune/A-Tune.md b/docs/en/docs/20.03_LTS/docs/A-Tune/A-Tune.md similarity index 100% rename from content/en/docs/A-Tune/A-Tune.md rename to docs/en/docs/20.03_LTS/docs/A-Tune/A-Tune.md diff --git a/content/en/docs/A-Tune/appendixes.md b/docs/en/docs/20.03_LTS/docs/A-Tune/appendixes.md similarity index 100% rename from content/en/docs/A-Tune/appendixes.md rename to docs/en/docs/20.03_LTS/docs/A-Tune/appendixes.md diff --git a/content/en/docs/A-Tune/application-scenarios.md b/docs/en/docs/20.03_LTS/docs/A-Tune/application-scenarios.md similarity index 99% rename from content/en/docs/A-Tune/application-scenarios.md rename to docs/en/docs/20.03_LTS/docs/A-Tune/application-scenarios.md index 924170be9956171063f74f8a718545db93e55907..cbac0bf1c1114edc27d3e7c5c936e3711b5f4bd4 100644 --- a/content/en/docs/A-Tune/application-scenarios.md +++ b/docs/en/docs/20.03_LTS/docs/A-Tune/application-scenarios.md @@ -91,7 +91,7 @@ Support WorkloadTypes: ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >If the value of Active is **true**, the profile is activated. In the example, the profile of the default type is activated. ## Workload Type Analysis and Auto Optimization @@ -209,7 +209,7 @@ The **example.conf** file can be written as follows \(the following optimizati Collect the global resource usage and OS status information during service running, and save the collected information to a CSV output file as the input dataset for model training. ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >- This command depends on the sampling tools such as perf, mpstat, vmstat, iostat, and sar. >- Currently, only the Kunpeng 920 CPU is supported. You can run the **dmidecode -t processor** command to check the CPU model. @@ -574,7 +574,7 @@ Use the specified project file to search the dynamic space for parameters and fi #### Format ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >Before running the command, ensure that the following conditions are met: >1. The YAML configuration file of the server has been edited and placed in the **/etc/atuned/tuning/** directory on the server by the server administrator. >2. The YAML configuration file of the client has been edited and placed in an arbitrary directory on the client. @@ -604,7 +604,7 @@ Use the specified project file to search the dynamic space for parameters and fi - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >The preceding two parameters must be used at the same time, and the -p parameter must be followed by the specific project name. diff --git a/content/en/docs/A-Tune/faqs.md b/docs/en/docs/20.03_LTS/docs/A-Tune/faqs.md similarity index 100% rename from content/en/docs/A-Tune/faqs.md rename to docs/en/docs/20.03_LTS/docs/A-Tune/faqs.md diff --git a/content/en/docs/A-Tune/figures/en-us_image_0213178479.png b/docs/en/docs/20.03_LTS/docs/A-Tune/figures/en-us_image_0213178479.png similarity index 100% rename from content/en/docs/A-Tune/figures/en-us_image_0213178479.png rename to docs/en/docs/20.03_LTS/docs/A-Tune/figures/en-us_image_0213178479.png diff --git a/content/en/docs/A-Tune/figures/en-us_image_0213178480.png b/docs/en/docs/20.03_LTS/docs/A-Tune/figures/en-us_image_0213178480.png similarity index 100% rename from content/en/docs/A-Tune/figures/en-us_image_0213178480.png rename to docs/en/docs/20.03_LTS/docs/A-Tune/figures/en-us_image_0213178480.png diff --git a/content/en/docs/A-Tune/figures/en-us_image_0214540398.png b/docs/en/docs/20.03_LTS/docs/A-Tune/figures/en-us_image_0214540398.png similarity index 100% rename from content/en/docs/A-Tune/figures/en-us_image_0214540398.png rename to docs/en/docs/20.03_LTS/docs/A-Tune/figures/en-us_image_0214540398.png diff --git a/content/en/docs/A-Tune/figures/en-us_image_0227497000.png b/docs/en/docs/20.03_LTS/docs/A-Tune/figures/en-us_image_0227497000.png similarity index 100% rename from content/en/docs/A-Tune/figures/en-us_image_0227497000.png rename to docs/en/docs/20.03_LTS/docs/A-Tune/figures/en-us_image_0227497000.png diff --git a/content/en/docs/A-Tune/figures/en-us_image_0227497343.png b/docs/en/docs/20.03_LTS/docs/A-Tune/figures/en-us_image_0227497343.png similarity index 100% rename from content/en/docs/A-Tune/figures/en-us_image_0227497343.png rename to docs/en/docs/20.03_LTS/docs/A-Tune/figures/en-us_image_0227497343.png diff --git a/content/en/docs/A-Tune/figures/en-us_image_0231122163.png b/docs/en/docs/20.03_LTS/docs/A-Tune/figures/en-us_image_0231122163.png similarity index 100% rename from content/en/docs/A-Tune/figures/en-us_image_0231122163.png rename to docs/en/docs/20.03_LTS/docs/A-Tune/figures/en-us_image_0231122163.png diff --git a/content/en/docs/A-Tune/getting-to-know-a-tune.md b/docs/en/docs/20.03_LTS/docs/A-Tune/getting-to-know-a-tune.md similarity index 99% rename from content/en/docs/A-Tune/getting-to-know-a-tune.md rename to docs/en/docs/20.03_LTS/docs/A-Tune/getting-to-know-a-tune.md index 03415ded0cdc5fe96a42f1d872a45dde1ede6c4d..732048c9023e25a04c245f777a175c33c3fbc731 100644 --- a/content/en/docs/A-Tune/getting-to-know-a-tune.md +++ b/docs/en/docs/20.03_LTS/docs/A-Tune/getting-to-know-a-tune.md @@ -19,7 +19,7 @@ To address the preceding challenges, openEuler launches A-Tune. A-Tune is an AI-based engine that optimizes system performance. It uses AI technologies to precisely profile business scenarios, discover and infer business characteristics, so as to make intelligent decisions, match with the optimal system parameter configuration combination, and give recommendations, ensuring the optimal business running status. -![](figures/en-us_image_0227497000.png) +![](./figures/en-us_image_0227497000.png) ## Architecture @@ -29,7 +29,7 @@ The following figure shows the A-Tune core technical architecture, which consist - System profile layer: consists of the labeling and learning subsystems. The labeling subsystem is used to cluster service models, and the learning subsystem is used to learn and classify service models. - Interaction system layer: monitors and configures various system resources and executes optimization policies. -![](figures/en-us_image_0227497343.png) +![](./figures/en-us_image_0227497343.png) ## Supported Features and Service Models diff --git a/content/en/docs/A-Tune/installation-and-deployment.md b/docs/en/docs/20.03_LTS/docs/A-Tune/installation-and-deployment.md similarity index 97% rename from content/en/docs/A-Tune/installation-and-deployment.md rename to docs/en/docs/20.03_LTS/docs/A-Tune/installation-and-deployment.md index 96a1e025d01cdf9261809680afb1e6e42115feaf..6b9b5bd530908a0eff76d74de2aa87396bd1df54 100644 --- a/content/en/docs/A-Tune/installation-and-deployment.md +++ b/docs/en/docs/20.03_LTS/docs/A-Tune/installation-and-deployment.md @@ -47,7 +47,7 @@ A-Tune can be installed in single-node or distributed mode. The installation modes are as follows: -![](figures/en-us_image_0231122163.png) +![](./figures/en-us_image_0231122163.png)    @@ -86,7 +86,7 @@ To install the A-Tune, perform the following steps: 4. Install an A-Tune server. - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >In this step, both the server and client software packages are installed. For the single-node deployment, skip **Step 5**. ``` @@ -237,6 +237,6 @@ After the A-Tune is installed, you need to start the A-Tune service. If the following information is displayed, the service is started successfully: - ![](figures/en-us_image_0214540398.png) + ![](./figures/en-us_image_0214540398.png) diff --git a/content/en/docs/A-Tune/public_sys-resources/icon-caution.gif b/docs/en/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-caution.gif similarity index 100% rename from content/en/docs/A-Tune/public_sys-resources/icon-caution.gif rename to docs/en/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-caution.gif diff --git a/content/en/docs/A-Tune/public_sys-resources/icon-danger.gif b/docs/en/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-danger.gif similarity index 100% rename from content/en/docs/A-Tune/public_sys-resources/icon-danger.gif rename to docs/en/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-danger.gif diff --git a/content/en/docs/A-Tune/public_sys-resources/icon-note.gif b/docs/en/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-note.gif similarity index 100% rename from content/en/docs/A-Tune/public_sys-resources/icon-note.gif rename to docs/en/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-note.gif diff --git a/content/en/docs/A-Tune/public_sys-resources/icon-notice.gif b/docs/en/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-notice.gif similarity index 100% rename from content/en/docs/A-Tune/public_sys-resources/icon-notice.gif rename to docs/en/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-notice.gif diff --git a/content/en/docs/A-Tune/public_sys-resources/icon-tip.gif b/docs/en/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-tip.gif similarity index 100% rename from content/en/docs/A-Tune/public_sys-resources/icon-tip.gif rename to docs/en/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-tip.gif diff --git a/content/en/docs/A-Tune/public_sys-resources/icon-warning.gif b/docs/en/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-warning.gif similarity index 100% rename from content/en/docs/A-Tune/public_sys-resources/icon-warning.gif rename to docs/en/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-warning.gif diff --git a/content/en/docs/Administration/administration.md b/docs/en/docs/20.03_LTS/docs/Administration/administration.md similarity index 100% rename from content/en/docs/Administration/administration.md rename to docs/en/docs/20.03_LTS/docs/Administration/administration.md diff --git a/content/en/docs/Administration/basic-configuration.md b/docs/en/docs/20.03_LTS/docs/Administration/basic-configuration.md similarity index 98% rename from content/en/docs/Administration/basic-configuration.md rename to docs/en/docs/20.03_LTS/docs/Administration/basic-configuration.md index 65e7e6167e256f1511eef3039dd677ca70f5660e..617937b9bf1e85b2a9d6ae00f227c3ef2f39678c 100644 --- a/content/en/docs/Administration/basic-configuration.md +++ b/docs/en/docs/20.03_LTS/docs/Administration/basic-configuration.md @@ -71,7 +71,7 @@ For example, if you want to use Simplified Chinese as the locale, run the follow # localectl set-locale LANG=zh_CN.UTF-8 ``` -> ![](public_sys-resources/icon-note.gif) **NOTE:** +> ![](./public_sys-resources/icon-note.gif) **NOTE:** > After the modification, log in again or run the command `source /etc/locale.conf` as the user **root** to update the configuration file for the modification to take effect: @@ -161,7 +161,7 @@ System clock synchronized: no Your system clock can be automatically synchronized with a remote server using the Network Time Protocol (NTP). Run the following command as the user **root** to enable or disable NTP. The value of _boolean_ is **yes** or **no**, indicating that the NTP is enabled or disabled for automatic system clock synchronization. Change the value based on the site requirements. -> ![](public_sys-resources/icon-note.gif) **NOTE:** +> ![](./public_sys-resources/icon-note.gif) **NOTE:** If the remote NTP server is enabled to automatically synchronize the system clock, you cannot manually change the date and time. If you need to manually change the date or time, ensure that automatic NTP system clock synchronization is disabled. You can run the **timedatectl set-ntp no** command to disable the NTP service. ``` @@ -176,7 +176,7 @@ For example, to enable automatic remote time synchronization, run the following #### Changing the Current Date -> ![](public_sys-resources/icon-note.gif) **NOTE:** +> ![](./public_sys-resources/icon-note.gif) **NOTE:** Before changing the date, ensure that automatic NTP system clock synchronization has been disabled. Run the following command as the user **root** to change the current date. In the command, _YYYY_ indicates the year, _MM_ indicates the month, and _DD_ indicates the day. Change them based on the site requirements. @@ -193,7 +193,7 @@ For example, to change the current date to August 14, 2019, run the following co #### Changing the Current Time -> ![](public_sys-resources/icon-note.gif) **NOTE:** +> ![](./public_sys-resources/icon-note.gif) **NOTE:** Before changing the time, ensure that automatic NTP system clock synchronization has been disabled. To change the current time, run the following command as the user **root**. In the command, _HH_ indicates the hour, _MM_ indicates the minute, and _SS_ indicates the second. Change them based on the site requirements. @@ -457,7 +457,7 @@ The memory reserved for kdump must be added to the bootargs in the **/boot/efi/E | General solution| crashkernel=2048M,high| If the memory size is less than 4 GB, 256 MB is reserved for kdump. If the memory size is greater than 4 GB, 2048 MB is reserved for kdump. 256 + 2048 MB in total.| | Economical solution| crashkernel=1024M,high| If the memory size is less than 4 GB, 256 MB is reserved for kdump. If the memory size is greater than 4 GB, 1024 MB is reserved for kdump. 256 + 1024 MB in total. It is recommended that kdump files not be dumped using the network in scenarios where the system memory size is less than 512 GB. In VM scenarios, you can reduce the reserved memory. You are advised to set crashkernel to 512M or crashkernel to 256M,high.| -> ![](public_sys-resources/icon-note.gif) **NOTE:** +> ![](./public_sys-resources/icon-note.gif) **NOTE:** > > If kdump files are not dumped using the network, you need to set the kdump file system not to pack network drivers. Loading the network driver requires a large amount of memory. As a result, the memory reserved for kdump may be insufficient and kdump may fail. Therefore, you are advised to disable network drivers. diff --git a/content/en/docs/Administration/configuring-services.md b/docs/en/docs/20.03_LTS/docs/Administration/configuring-services.md similarity index 100% rename from content/en/docs/Administration/configuring-services.md rename to docs/en/docs/20.03_LTS/docs/Administration/configuring-services.md diff --git a/content/en/docs/Administration/configuring-the-ftp-server.md b/docs/en/docs/20.03_LTS/docs/Administration/configuring-the-ftp-server.md similarity index 99% rename from content/en/docs/Administration/configuring-the-ftp-server.md rename to docs/en/docs/20.03_LTS/docs/Administration/configuring-the-ftp-server.md index 98104b86eed332120d8b8de539b866cb996812bb..e841f0f63bc612e9e07973d8ae8e67c8f11cd14d 100644 --- a/content/en/docs/Administration/configuring-the-ftp-server.md +++ b/docs/en/docs/20.03_LTS/docs/Administration/configuring-the-ftp-server.md @@ -87,7 +87,7 @@ To start, stop, or restart the vsftpd service, run the corresponding command as tcp6 0 0 :::21 :::* LISTEN 19716/vsftpd ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >If the **netstat** command does not exist, run the **dnf install net-tools** command to install the **net-tools** software and then run the **netstat** command. - Stopping the vsftpd services @@ -170,7 +170,7 @@ You can modify the vsftpd configuration file to control user permissions. [Tabl ### Default Configuration Description ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >The configuration content in this document is for reference only. You can modify the content based on the site requirements \(for example, security hardening requirements\). In the openEuler system, vsftpd does not open to anonymous users by default. Run the vim command to view the main configuration file. The content is as follows: @@ -385,7 +385,7 @@ ftp> bye 221 Goodbye. ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >If the **ftp** command does not exist, run the **dnf install ftp** command as the **root** user to install the **ftp** software and then run the **ftp** command. ## Configuring a Firewall @@ -478,7 +478,7 @@ Generally, the get or mget command is used to download files. ftp> mget *.* ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >- In this case, a message is displayed each time a file is downloaded. To block the prompt information, run the **prompt off** command before running the **mget \*.\*** command. >- The files are downloaded to the current directory on the Linux host. For example, if you run the ftp command in /home/myopenEuler/, all files are downloaded to /home/myopenEuler/. diff --git a/content/en/docs/Administration/configuring-the-network.md b/docs/en/docs/20.03_LTS/docs/Administration/configuring-the-network.md similarity index 99% rename from content/en/docs/Administration/configuring-the-network.md rename to docs/en/docs/20.03_LTS/docs/Administration/configuring-the-network.md index 370ae8c6afdd5762779bfa1bf1a3da3a14eec05a..737b7af99d79325505cd8e5e80f27d497732dfeb 100644 --- a/content/en/docs/Administration/configuring-the-network.md +++ b/docs/en/docs/20.03_LTS/docs/Administration/configuring-the-network.md @@ -27,7 +27,7 @@ ### Using the nmcli Command ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >The network configuration configured by running the **nmcli** command takes effect immediately and will not be lost after the system restarts. @@ -93,7 +93,7 @@ enp3s0 c88d7b69-f529-35ca-81ab-aa729ac542fd ethernet enp3s0 virbr0 ba552da6-f014-49e3-91fa-ec9c388864fa bridge virbr0 ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >In the command output, **NAME** indicates the connection ID \(name\). After a network connection is added, the corresponding configuration file is generated and associated with the corresponding device. To check for available devices, run the following command: @@ -159,7 +159,7 @@ To add a static IPv4 network connection, run the following command: nmcli connection add type ethernet con-name connection-name ifname interface-name ip4 address gw4 address ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >To add an IPv6 address and related gateway information, use the **ip6** and **gw6** options. For example, to create a static connection configuration file named **net-static**, run the following command as the **root** user: @@ -321,7 +321,7 @@ $ nmcli connection show id 'Wifi ' | grep mtu ### Using the ip Command ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >The network configuration configured using the **ip** command takes effect immediately, but the configuration will be lost after the system restarts. @@ -413,7 +413,7 @@ In the preceding command, **192.168.2.1** is the IP address of the target netw ### Configuring the Network Through the ifcfg File ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >The network configured in the **ifcfg** file does not take effect immediately. You need to run the **systemctl reload NetworkManager** command as the **root** user to restart the network service for the configuration to take effect. #### Configuring a Static Network @@ -486,7 +486,7 @@ There are three types of host names: **static**, **transient**, and **pretty* - **transient**: Dynamic host name, which is maintained by the kernel. The initial value is a static host name. The default value is **localhost**. The value can be changed when the DHCP or mDNS server is running. - **pretty**: Flexible host name, which can be set in any form \(including special characters/blanks\). Static and transient host names are subject to the general domain name restrictions. ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >Static and transient host names can contain only letters \(a–z and A–Z\), digits \(0–9\), hyphens \(-\), underlines \(\_\), and periods \(.\). The host names cannot start or end with a period \(.\) or contain two consecutive periods \(.\). The host name can contain a maximum of 64 characters. ### Configuring a Host Name by Running the **hostnamectl** Command @@ -498,7 +498,7 @@ Run the following command to view the current host name: $ hostnamectl status ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >If no option is specified in the command, the **status** option is used by default. #### Setting All Host Names @@ -684,7 +684,7 @@ Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkMa Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/8) ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >If an interface is in **up** state, run the **ifdown** _enp3s0_ command to change the state to **down**. In the command, _enp3s0_ indicates the actual NIC name. After that, enable all the slave interfaces to enable the bonding \(do not set them to **Down**\). @@ -834,7 +834,7 @@ Both IPv6 and IPv4 addresses can be obtained through DHCP as the **root** user. } ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >- \: a 32-digit integer, indicating the enterprise ID. The enterprise is registered through the IANA. >- \: a 16-digit integer, indicating the length of the vendor class string. >- \: character string of the vendor class to be set, for example, HWHW. @@ -865,7 +865,7 @@ Both IPv6 and IPv4 addresses can be obtained through DHCP as the **root** user. } ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >In substring \(option dhcp6.vendor-class, 6, 10\), the start position of the substring is 6, because the substring contains four bytes of and two bytes of . The end position of the substring is 6+. In this example, the vendor class string is HWHW, and the length of the string is 4. Therefore, the end position of the substring is 6 + 4 = 10. You can specify and as required. On the server: @@ -894,7 +894,7 @@ struct sockaddr_in6 { }; ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >sin6\_scope\_id: a 32-bit integer. For the link-local address, it identifies the index of the specified interface. For the link-range sin6\_addr, it identifies the index of the specified interface. For the site-range sin6\_addr, it is used as the site identifier \(the site-local address has been discarded\). When the link-local address is used for socket communication, the interface index corresponding to the address needs to be specified when the destination address is constructed. Generally, you can use the if\_nametoindex function to convert an interface name into an interface index number. Details are as follows: @@ -945,7 +945,7 @@ PERSISTENT_DHCLIENT=yes|no|1|0 - DHCPV6C: **no** indicates that an IPv6 address is statically configured, and **yes** indicates that the DHCPv6 dhclient is enabled to dynamically obtain the IPv6 address. - PERSISTENT\_DHCLIENT: **no|0** indicates that the IPv4 dhclient process is configured as nonpersistent. If the dhclient sends a request packet to the DHCP server but does not receive any response, the dhclient exits after a period of time and the exit value is 2. **yes|1** indicates that the IPv4 dhclient process is configured to be persistent. The dhclient process repeatedly sends request packets to the DHCP server. **If PERSISTENT\_DHCLIENT is not configured, dhclient of IPv4 is set to yes|1 by default.** - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >The PERSISTENT\_DHCLIENT configuration takes effect only for IPv4 and does not take effect for IPv6-related dhclient -6 processes. By default, the persistence configuration is not performed for IPv6. @@ -1298,6 +1298,6 @@ $ActionQueueType Direct $MainMsgQueueType Direct ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >- In direct mode, the queue size is reduced by 1. Therefore, one log is reserved in the queue for the next log output. >- The direct mode degrades the rsyslog performance of the server. diff --git a/content/en/docs/Administration/configuring-the-repo-server.md b/docs/en/docs/20.03_LTS/docs/Administration/configuring-the-repo-server.md similarity index 92% rename from content/en/docs/Administration/configuring-the-repo-server.md rename to docs/en/docs/20.03_LTS/docs/Administration/configuring-the-repo-server.md index 6399f5afef0c40891d748774022984c4bd8b2fc9..b0ba0980b51b4f46b01ed1f974f99db6a9493afd 100644 --- a/content/en/docs/Administration/configuring-the-repo-server.md +++ b/docs/en/docs/20.03_LTS/docs/Administration/configuring-the-repo-server.md @@ -1,7 +1,7 @@ # Configuring the Repo Server ->![](public_sys-resources/icon-note.gif) **NOTE:** -> openEuler provides multiple repo sources for users online. For details about the repo sources, see [System Installation](../Releasenotes/installing-the-os.html). If you cannot obtain the openEuler repo source online, you can use the ISO release package provided by openEuler to create a local openEuler repo source. This section uses the **openEuler-20.03-LTS-aarch64-dvd.iso** file as an example. Modify the ISO file as required. +>![](./public_sys-resources/icon-note.gif) **NOTE:** +> openEuler provides multiple repo sources for users online. For details about the repo sources, see [System Installation](./../Releasenotes/installing-the-os.html). If you cannot obtain the openEuler repo source online, you can use the ISO release package provided by openEuler to create a local openEuler repo source. This section uses the **openEuler-20.03-LTS-aarch64-dvd.iso** file as an example. Modify the ISO file as required. @@ -99,7 +99,7 @@ You can update the repo source in either of the following ways: In this command, --update indicates the update, and --workers indicates the number of threads, which can be customized. -> ![](public_sys-resources/icon-note.gif) **NOTE:** +> ![](./public_sys-resources/icon-note.gif) **NOTE:** If the command output contains "createrepo: command not found", run the **dnf install createrepo** command as the **root** user to install the **createrepo** softeware. ## Deploying the Remote Repo Source @@ -112,7 +112,7 @@ Install openEuler OS and deploy the repo source using Nginx on openEuler OS. 2. After installing Nginx, configure /etc/nginx/nginx.conf as the **root** user. - > ![](public_sys-resources/icon-note.gif) **NOTE:** + > ![](./public_sys-resources/icon-note.gif) **NOTE:** The configuration content in this document is for reference only. You can configure the content based on the site requirements (for example, security hardening requirements). ``` @@ -172,7 +172,7 @@ The configuration content in this document is for reference only. You can config - [Figure 1](#en-us_topic_0151920971_fd25e3f1d664b4087ae26631719990a71) indicates that the Nginx service is started successfully. **Figure 1** The Nginx service is successfully started. -![](figures/the-nginx-service-is-successfully-started.png "the-nginx-service-is-successfully-started") +![](./figures/the-nginx-service-is-successfully-started.png "the-nginx-service-is-successfully-started") - If the Nginx service fails to be started, view the error information. @@ -180,8 +180,8 @@ The configuration content in this document is for reference only. You can config $ systemctl status nginx.service --full ``` - **Figure 2** Nginx startup failure - ![](figures/nginx-startup-failure.png "nginx-startup-failure") + **Figure 2** Nginx startup failure + ![](./figures/nginx-startup-failure.png "nginx-startup-failure") As shown in [Figure 2](#en-us_topic_0151920971_f1f9f3d086e454b9cba29a7cae96a4c54), the Nginx service fails to be created because the /var/spool/nginx/tmp/client\_body directory fails to be created. You need to manually create the directory as the **root** user. Similar problems are solved as follows: @@ -229,7 +229,7 @@ The configuration content in this document is for reference only. You can config 4. After the Nginx service is configured, you can use the IP address to access the web page, as shown in [Figure 3](#en-us_topic_0151921017_fig1880404110396). **Figure 3** Nginx deployment succeeded -![](figures/nginx-deployment-succeeded.png "nginx-deployment-succeeded") +![](./figures/nginx-deployment-succeeded.png "nginx-deployment-succeeded") 5. Use either of the following methods to add the repo source to the /usr/share/nginx/repo directory: @@ -274,7 +274,7 @@ You can configure the built repo as the yum source and create the \*\*\*.repo co gpgkey=file:///home/openEuler/srv/repo/RPM-GPG-KEY-openEuler ``` - > ![](public_sys-resources/icon-note.gif) **NOTE:** + > ![](./public_sys-resources/icon-note.gif) **NOTE:** > > - The repoid in \[repoid\] indicates the ID of the software repository. Repoids in all .repo configuration files must be unique. In the example, repoid is set to **base**. > - **name** indicates the string that the software repository describes. @@ -298,7 +298,7 @@ You can configure the built repo as the yum source and create the \*\*\*.repo co gpgkey=http://192.168.139.209/RPM-GPG-KEY-openEuler ``` - > ![](public_sys-resources/icon-note.gif) **NOTE:** + > ![](./public_sys-resources/icon-note.gif) **NOTE:** > 192.168.139.209 is an example. Replace it with the actual IP address. - If the openEuler repo source provided by openEuler is used as the yum source, the content of **openEuler.repo** is as follows (the aarch64-based OS repo source is used as an example): diff --git a/content/en/docs/Administration/configuring-the-web-server.md b/docs/en/docs/20.03_LTS/docs/Administration/configuring-the-web-server.md similarity index 98% rename from content/en/docs/Administration/configuring-the-web-server.md rename to docs/en/docs/20.03_LTS/docs/Administration/configuring-the-web-server.md index 080c8e167d71925c97fd52da903bc40758e72e50..c915961e7b8231156bd3d35f4d58db3afc153345 100644 --- a/content/en/docs/Administration/configuring-the-web-server.md +++ b/docs/en/docs/20.03_LTS/docs/Administration/configuring-the-web-server.md @@ -41,7 +41,7 @@ You can use the systemctl tool to manage the httpd service, including starting, # dnf install httpd ``` - For more information about service management, see [Service Management](service-management.html). + For more information about service management, see [Service Management](./service-management.html). - To start, stop, and restart the httpd service, you must have the root permission. @@ -61,7 +61,7 @@ You can use the systemctl tool to manage the httpd service, including starting, ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >If the running Apache HTTP server functions as a secure server, a password is required after the system is started. The password is an encrypted private SSL key. #### Stopping the Service @@ -155,7 +155,7 @@ If the following information is displayed, the syntax of the configuration file Syntax OK ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >- Before modifying the configuration file, back up the original file so that the configuration file can be quickly restored if a fault occurs. >- The modified configuration file takes effect only after the web service is restarted. @@ -194,7 +194,7 @@ For example, to load the asis DSO module, perform the following steps: ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >**Common httpd commands** >- httpd -v: views the httpd version number. >- httpd -l: views the static modules compiled into the httpd program. @@ -313,7 +313,7 @@ Nginx is a lightweight web server which also acts as a reverse proxy server and ### Installing Nginx -1. Configure the local yum source. For details, see [Configuring the Repo Server](configuring-the-repo-server.html). +1. Configure the local yum source. For details, see [Configuring the Repo Server](./configuring-the-repo-server.html). 2. Clear the cache. ``` @@ -347,7 +347,7 @@ You can use the systemctl tool to manage the Nginx service, including starting, #### Prerequisites - Ensure that the Nginx service has been installed. If not, install it by referring to [Installing Nginx](#installing-nginx). - For more information about service management, see [Service Management](service-management.html). + For more information about service management, see [Service Management](./service-management.html). - To start, stop, and restart the Nginx service, you must have the **root** permission. @@ -367,7 +367,7 @@ You can use the systemctl tool to manage the Nginx service, including starting, ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >If the running Nginx server functions as a secure server, a password is required after the system is started. The password is an encrypted private SSL key. #### Stopping the Service @@ -457,7 +457,7 @@ Although the default configuration can be used in most cases, you need to be fam If the command output contains **syntax is ok**, the syntax of the configuration file is correct. ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >- Before modifying the configuration file, back up the original file so that the configuration file can be quickly restored if a fault occurs. >- The modified configuration file takes effect only after the web service is restarted. diff --git a/content/en/docs/Administration/faqs.md b/docs/en/docs/20.03_LTS/docs/Administration/faqs.md similarity index 80% rename from content/en/docs/Administration/faqs.md rename to docs/en/docs/20.03_LTS/docs/Administration/faqs.md index 5fc145d13b938d547d649182d524a22e2eb9c73d..b681539769b2558932d71c2caa9951524aa22ae6 100644 --- a/content/en/docs/Administration/faqs.md +++ b/docs/en/docs/20.03_LTS/docs/Administration/faqs.md @@ -7,6 +7,7 @@ - [Failed to Compile MariaDB Using rpmbuild](#failed-to-compile-mariadb-using-rpmbuild) - [Failed to Start the SNTP Service Using the Default Configuration](#failed-to-start-the-sntp-service-using-the-default-configuration) - [Installation Failure Caused by Software Package Conflict, File Conflict, or Missing Software Package](#installation-failure-caused-by-software-package-conflict-file-conflict-or-missing-software-package) + - [Why Do OpenSSH-related Packages Fail to Be Installed when the OpenSSH Software Package Is Upgraded in Default DNF Update Mode?](#Why-Do-OpenSSH-related-Packages-Fail-to-Be-Installed-when-the-OpenSSH-Software-Package-Is-Upgraded-in-Default-DNF-Update-Mode) ## Why Is the Memory Usage of the libvirtd Service Queried by Running the systemctl and top Commands Different? @@ -162,3 +163,32 @@ If a software package is missing, perform the following steps \(the missed softw ``` 3. Perform the upgrade again. + +## Why Do OpenSSH-related Packages Fail to Be Installed when the OpenSSH Software Package Is Upgraded in Default DNF Update Mode? + +### Symptom + +When the OpenSSH software package is upgraded in default DNF update mode, a message indicating that the OpenSSH-related packages cannot be installed is displayed as follows: + ``` +cannot install both openssh-7.8p1-8.oe1.aarch64 and openssh-8.2p1-5.oe1.aarch64 + +cannot install both openssh-7.8p1-8.oe1.aarch64 and openssh-8.2p1-4.oe1.aarch64 + +cannot install the best update condidate for package openssh-clients-8.2p1-5.oe1.aarch64 + +cannot install the best update condidate for package openssh-8.2p1-5.oe1.aarch64 + ``` + +### Possible Cause + +By default, the best mode of the DNF package manager (the corresponding parameter is **--best**) is enabled. The **--best** option for DNF always tries to upgrade to the latest version available even if dependencies cannot be satisfied. By enabling the DNF best mode by default, the user will be reminded that a later package version is available but it fails to satisfy the dependencies. If a problem occurs, the DNF displays a message to notify the user of the problem. The openEuler Community developers are looking to make this default setting change in case that a security fix package cannot be upgraded due to dependency issues, under the current premise that it could be silently ignored and the user would not be aware. In addition, using the DNF best mode will quickly alert developers to problems in upgrade paths. + +### Solution + +A **--nobest** option for DNF will be available to override or disable the default behavior, allowing the user to properly upgrade the security fix package when the package to be upgraded has dependency issues. + +Open source software developers of openEuler 20.03-LTS have identified this scenario during the upgrade of the security fix version of the OpenSSH software package. It is recommended that users select a proper upgrade mode based on the preceding analysis. openEuler also provides users with specific instructions on the upgrade operation: + + ``` + dnf update –y –nobest openssh + ``` \ No newline at end of file diff --git "a/content/en/docs/Administration/figures/\346\220\255\345\273\272\346\225\260\346\215\256\347\233\230-0.png" b/docs/en/docs/20.03_LTS/docs/Administration/figures/Creating_DataDisk-0.png similarity index 100% rename from "content/en/docs/Administration/figures/\346\220\255\345\273\272\346\225\260\346\215\256\347\233\230-0.png" rename to docs/en/docs/20.03_LTS/docs/Administration/figures/Creating_DataDisk-0.png diff --git "a/content/en/docs/Administration/figures/\346\220\255\345\273\272\346\225\260\346\215\256\347\233\230.png" b/docs/en/docs/20.03_LTS/docs/Administration/figures/Creating_DataDisk.png similarity index 100% rename from "content/en/docs/Administration/figures/\346\220\255\345\273\272\346\225\260\346\215\256\347\233\230.png" rename to docs/en/docs/20.03_LTS/docs/Administration/figures/Creating_DataDisk.png diff --git a/content/en/docs/Administration/figures/d1376b2a-d036-41c4-b852-e8368f363b5e-1.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/d1376b2a-d036-41c4-b852-e8368f363b5e-1.png similarity index 100% rename from content/en/docs/Administration/figures/d1376b2a-d036-41c4-b852-e8368f363b5e-1.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/d1376b2a-d036-41c4-b852-e8368f363b5e-1.png diff --git a/content/en/docs/Administration/figures/d1376b2a-d036-41c4-b852-e8368f363b5e.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/d1376b2a-d036-41c4-b852-e8368f363b5e.png similarity index 100% rename from content/en/docs/Administration/figures/d1376b2a-d036-41c4-b852-e8368f363b5e.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/d1376b2a-d036-41c4-b852-e8368f363b5e.png diff --git a/content/en/docs/Administration/figures/en-us_image_0229622729.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0229622729.png similarity index 100% rename from content/en/docs/Administration/figures/en-us_image_0229622729.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0229622729.png diff --git a/content/en/docs/Administration/figures/en-us_image_0229622789.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0229622789.png similarity index 100% rename from content/en/docs/Administration/figures/en-us_image_0229622789.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0229622789.png diff --git a/content/en/docs/Administration/figures/en-us_image_0230050789.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0230050789.png similarity index 100% rename from content/en/docs/Administration/figures/en-us_image_0230050789.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0230050789.png diff --git a/content/en/docs/Administration/figures/en-us_image_0231143189.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231143189.png similarity index 100% rename from content/en/docs/Administration/figures/en-us_image_0231143189.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231143189.png diff --git a/content/en/docs/Administration/figures/en-us_image_0231143191.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231143191.png similarity index 100% rename from content/en/docs/Administration/figures/en-us_image_0231143191.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231143191.png diff --git a/content/en/docs/Administration/figures/en-us_image_0231143193.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231143193.png similarity index 100% rename from content/en/docs/Administration/figures/en-us_image_0231143193.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231143193.png diff --git a/content/en/docs/Administration/figures/en-us_image_0231143195.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231143195.png similarity index 100% rename from content/en/docs/Administration/figures/en-us_image_0231143195.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231143195.png diff --git a/content/en/docs/Administration/figures/en-us_image_0231143196.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231143196.png similarity index 100% rename from content/en/docs/Administration/figures/en-us_image_0231143196.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231143196.png diff --git a/content/en/docs/Administration/figures/en-us_image_0231143197.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231143197.png similarity index 100% rename from content/en/docs/Administration/figures/en-us_image_0231143197.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231143197.png diff --git a/content/en/docs/Administration/figures/en-us_image_0231143198.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231143198.png similarity index 100% rename from content/en/docs/Administration/figures/en-us_image_0231143198.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231143198.png diff --git a/content/en/docs/Administration/figures/en-us_image_0231563132.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231563132.png similarity index 100% rename from content/en/docs/Administration/figures/en-us_image_0231563132.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231563132.png diff --git a/content/en/docs/Administration/figures/en-us_image_0231563134.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231563134.png similarity index 100% rename from content/en/docs/Administration/figures/en-us_image_0231563134.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231563134.png diff --git a/content/en/docs/Administration/figures/en-us_image_0231563135.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231563135.png similarity index 100% rename from content/en/docs/Administration/figures/en-us_image_0231563135.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231563135.png diff --git a/content/en/docs/Administration/figures/en-us_image_0231563136.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231563136.png similarity index 100% rename from content/en/docs/Administration/figures/en-us_image_0231563136.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/en-us_image_0231563136.png diff --git a/content/en/docs/Administration/figures/example-command-output.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/example-command-output.png similarity index 100% rename from content/en/docs/Administration/figures/example-command-output.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/example-command-output.png diff --git "a/content/en/docs/Administration/figures/\347\231\273\345\275\225.png" b/docs/en/docs/20.03_LTS/docs/Administration/figures/login.png similarity index 100% rename from "content/en/docs/Administration/figures/\347\231\273\345\275\225.png" rename to docs/en/docs/20.03_LTS/docs/Administration/figures/login.png diff --git a/content/en/docs/Administration/figures/mariadb-logical-architecture.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/mariadb-logical-architecture.png similarity index 100% rename from content/en/docs/Administration/figures/mariadb-logical-architecture.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/mariadb-logical-architecture.png diff --git a/content/en/docs/Administration/figures/nginx-deployment-succeeded.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/nginx-deployment-succeeded.png similarity index 100% rename from content/en/docs/Administration/figures/nginx-deployment-succeeded.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/nginx-deployment-succeeded.png diff --git a/content/en/docs/Administration/figures/nginx-startup-failure.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/nginx-startup-failure.png similarity index 100% rename from content/en/docs/Administration/figures/nginx-startup-failure.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/nginx-startup-failure.png diff --git a/content/en/docs/Administration/figures/postgres.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/postgres.png similarity index 100% rename from content/en/docs/Administration/figures/postgres.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/postgres.png diff --git a/content/en/docs/Administration/figures/postgresql-architecture.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/postgresql-architecture.png similarity index 100% rename from content/en/docs/Administration/figures/postgresql-architecture.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/postgresql-architecture.png diff --git a/content/en/docs/Administration/figures/the-nginx-service-is-successfully-started.png b/docs/en/docs/20.03_LTS/docs/Administration/figures/the-nginx-service-is-successfully-started.png similarity index 100% rename from content/en/docs/Administration/figures/the-nginx-service-is-successfully-started.png rename to docs/en/docs/20.03_LTS/docs/Administration/figures/the-nginx-service-is-successfully-started.png diff --git a/content/en/docs/Administration/managing-hard-disks-through-lvm.md b/docs/en/docs/20.03_LTS/docs/Administration/managing-hard-disks-through-lvm.md similarity index 99% rename from content/en/docs/Administration/managing-hard-disks-through-lvm.md rename to docs/en/docs/20.03_LTS/docs/Administration/managing-hard-disks-through-lvm.md index 45c63cd6e2a964cc0857e8be9103f0f62584b4f1..10e5910556072e84aefd1d61cecf406d0f0d2fb0 100644 --- a/content/en/docs/Administration/managing-hard-disks-through-lvm.md +++ b/docs/en/docs/20.03_LTS/docs/Administration/managing-hard-disks-through-lvm.md @@ -60,10 +60,10 @@ When disks are managed using LVM, file systems are distributed on multiple disks ## Installing the LVM ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >The LVM has been installed on the openEuler OS by default. You can run the **rpm -qa | grep lvm2** command to check whether it is installed. If the command output contains "lvm2", the LVM has been installed. In this case, skip this section. If no information is output, the LVM is not installed. Install it by referring to this section. -1. Configure the local yum source. For details, see [Configuring the Repo Server](configuring-the-repo-server.html). +1. Configure the local yum source. For details, see [Configuring the Repo Server](./configuring-the-repo-server.html). 2. Clear the cache. ``` @@ -358,7 +358,7 @@ In the preceding information: - _lvname_: device file corresponding to the LV whose attributes are to be displayed. If this option is not set, attributes of all LVs are displayed. - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >Device files corresponding to LVs are stored in the VG directory. For example, if LV **lv1** is created in VG **vg1**, the device file corresponding to **lv1** is **/dev/vg1/lv1**. diff --git a/content/en/docs/Administration/process-management.md b/docs/en/docs/20.03_LTS/docs/Administration/process-management.md similarity index 99% rename from content/en/docs/Administration/process-management.md rename to docs/en/docs/20.03_LTS/docs/Administration/process-management.md index e745e2271bdefd0a6a940ca09e88ff61d8547874..4032595e9628a73264e53976e363328e2a4cb716 100644 --- a/content/en/docs/Administration/process-management.md +++ b/docs/en/docs/20.03_LTS/docs/Administration/process-management.md @@ -111,7 +111,7 @@ Both the top and the ps commands can display a list of currently running process [Figure 1](#en-us_topic_0151921029_f289234fcdbac453796200d80e9889cd1) provides an example output of the top command. **Figure 1** Example command output -![](figures/example-command-output.png "example-command-output") +![](./figures/example-command-output.png "example-command-output") ### kill Command The **kill** command is used to terminate a process regardless of whether the process is running in foreground or background. It differs from the combo key **Ctrl+c**, which can terminate only foreground processes. The kill command is used to terminate a process regardless of whether the process is running in foreground or background. The reason for terminating a background process can be heavy use of CPU resources or deadlock. @@ -310,7 +310,7 @@ For example, to create a crontab file for the userexample user, perform the foll After the new file is installed, you will find a file named userexample in the **/var/spool/cron** directory. This file is the required crontab file. ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >Do not restart the cron service after a crontab file is modified, because the cron service, once started, reads the crontab file every minute to check whether there are commands that need to be executed periodically. You do not need to restart the **cron** service after modifying the **crontab** file. #### /etc/crontab File @@ -328,7 +328,7 @@ HOME=/ 42 4 1 * * root run-parts /etc/cron.monthly //Run scripts in the /etc/cron.monthly directory once a month. ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >If the **run-parts** parameter is deleted, a script name instead of a directory name is executed. ## Suspending/Resuming a Process diff --git a/content/en/docs/Administration/public_sys-resources/icon-caution.gif b/docs/en/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-caution.gif similarity index 100% rename from content/en/docs/Administration/public_sys-resources/icon-caution.gif rename to docs/en/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-caution.gif diff --git a/content/en/docs/Administration/public_sys-resources/icon-danger.gif b/docs/en/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-danger.gif similarity index 100% rename from content/en/docs/Administration/public_sys-resources/icon-danger.gif rename to docs/en/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-danger.gif diff --git a/content/en/docs/Administration/public_sys-resources/icon-note.gif b/docs/en/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-note.gif similarity index 100% rename from content/en/docs/Administration/public_sys-resources/icon-note.gif rename to docs/en/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-note.gif diff --git a/content/en/docs/Administration/public_sys-resources/icon-notice.gif b/docs/en/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-notice.gif similarity index 100% rename from content/en/docs/Administration/public_sys-resources/icon-notice.gif rename to docs/en/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-notice.gif diff --git a/content/en/docs/Administration/public_sys-resources/icon-tip.gif b/docs/en/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-tip.gif similarity index 100% rename from content/en/docs/Administration/public_sys-resources/icon-tip.gif rename to docs/en/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-tip.gif diff --git a/content/en/docs/Administration/public_sys-resources/icon-warning.gif b/docs/en/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-warning.gif similarity index 100% rename from content/en/docs/Administration/public_sys-resources/icon-warning.gif rename to docs/en/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-warning.gif diff --git a/content/en/docs/Administration/service-management.md b/docs/en/docs/20.03_LTS/docs/Administration/service-management.md similarity index 98% rename from content/en/docs/Administration/service-management.md rename to docs/en/docs/20.03_LTS/docs/Administration/service-management.md index 58457238c65e283618308bc13ea644c034a77fd8..f7950c0494a2d0714b2cef3d08edd88b4e90a9a0 100644 --- a/content/en/docs/Administration/service-management.md +++ b/docs/en/docs/20.03_LTS/docs/Administration/service-management.md @@ -115,13 +115,6 @@ In systemd, the targets of most actions are units, which are resources systemd k

A group of hierarchically organized units that manage system processes.

-

Snapshot unit

- -

.snapshot

- -

A saved state of the systemd manager.

- -

Socket unit

.socket

@@ -710,7 +703,7 @@ Give root password for maintenance (or press Control-D to continue): ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >You need to restart the system to enter the normal working mode from the rescue mode. ### Changing to Emergency Mode @@ -728,7 +721,7 @@ Give root password for maintenance (or press Control-D to continue): ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >You need to restart the system to enter the normal working mode from the emergency mode. ## Shutting Down, Suspending, and Hibernating the Operating System diff --git a/content/en/docs/Administration/setting-up-the-database-server.md b/docs/en/docs/20.03_LTS/docs/Administration/setting-up-the-database-server.md similarity index 95% rename from content/en/docs/Administration/setting-up-the-database-server.md rename to docs/en/docs/20.03_LTS/docs/Administration/setting-up-the-database-server.md index c88049f01333ce83b94cb8d52d8979a4eeca1df7..a9757479a689e1a9b7480bba7862a9daf29a9120 100644 --- a/content/en/docs/Administration/setting-up-the-database-server.md +++ b/docs/en/docs/20.03_LTS/docs/Administration/setting-up-the-database-server.md @@ -32,7 +32,7 @@ [Figure 1](#fig26022387391) shows the PostgreSQL architecture and [Table 1](#table62020913417) describes the main processes. **Figure 1** PostgreSQL architecture -![](figures/postgresql-architecture.png "postgresql-architecture") +![](./figures/postgresql-architecture.png "postgresql-architecture") **Table 1** Main processes in PostgreSQL @@ -109,14 +109,14 @@ ### Configuring the Environment ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >The following environment configuration is for reference only. Configure the environment based on the site requirements. #### Disabling the Firewall and Automatic Startup ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >It is recommended that firewall be disabled in the test environment to prevent network impact. Configure the firewall based on actual requirements. 1. Stop the firewall service as the **root** user. @@ -131,7 +131,7 @@ # systemctl disable firewalld ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >The automatic startup is automatically disabled as the firewall is disabled. @@ -146,7 +146,7 @@ #### Creating a User Group and a User ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >In the server environment, independent users are assigned to each process to implement permission isolation for security purposes. The user group and user are created for the OS, not for the database. 1. Create a PostgreSQL user or user group as the **root** user. @@ -168,7 +168,7 @@ #### Creating Data Drives ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >- When testing the ultimate performance, you are advised to attach NVMe SSDs with better I/O performance to create PostgreSQL test instances to avoid the impact of disk I/O on the performance test result. This section uses NVMe SSDs as an example. For details, see Step 1 to Step 4. >- In a non-performance test, run the following command as the **root** user to create a data directory. Then skip this section. > \# mkdir /data @@ -206,7 +206,7 @@ #### Installing PostgreSQL -1. Configure the local yum source. For details, see [Configuring the Repo Server](configuring-the-repo-server.html). +1. Configure the local yum source. For details, see [Configuring the Repo Server](./configuring-the-repo-server.html). 2. Clear the cache. ``` @@ -238,7 +238,7 @@ ##### Initializing the Database ->![](public_sys-resources/icon-notice.gif) **NOTICE:** +>![](./public_sys-resources/icon-notice.gif) **NOTICE:** >Perform this step as the postgres user. 1. Switch to the created PostgreSQL user. @@ -270,7 +270,7 @@ If the following information is displayed, the PostgreSQL processes have been started. - ![](figures/postgres.png) + ![](./figures/postgres.png) ##### Logging In to the Database @@ -281,9 +281,9 @@ $ /usr/bin/psql -U postgres ``` - ![](figures/登录.png) + ![](./figures/login.png) - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >You do not need to enter a password when logging in to the database for the first time. @@ -295,7 +295,7 @@ postgres=#alter user postgres with password '123456'; ``` - ![](figures/en-us_image_0230050789.png) + ![](./figures/en-us_image_0230050789.png) ##### Exiting the Database @@ -708,7 +708,7 @@ postgres=# \l; You can run the **DROP DATABASE** statement or **dropdb** command to delete a database. The **dropdb** command encapsulates the **DROP DATABASE** statement and needs to be executed on the shell GUI instead of the database GUI. ->![](public_sys-resources/icon-caution.gif) **CAUTION:** +>![](./public_sys-resources/icon-caution.gif) **CAUTION:** >Exercise caution when deleting a database. Once a database is deleted, all tables and data in the database will be deleted. ``` @@ -802,7 +802,7 @@ The MariaDB database management system is a branch of MySQL and is maintained by [Figure 2](#fig13492418164520) shows the MariaDB architecture. **Figure 2** MariaDB logical architecture -![](figures/mariadb-logical-architecture.png "mariadb-logical-architecture") +![](./figures/mariadb-logical-architecture.png "mariadb-logical-architecture") When MariaDB receives a SQL statement, the execution process is as follows: @@ -824,14 +824,14 @@ Each storage engine manages and stores data in different ways, and supports diff ### Configuring the Environment ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >The following environment configuration is for reference only. Configure the environment based on the site requirements. #### Disabling the Firewall and Automatic Startup ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >It is recommended that firewall be disabled in the test environment to prevent network impact. Configure the firewall based on actual requirements. 1. Stop the firewall service as the **root** user. @@ -846,7 +846,7 @@ Each storage engine manages and stores data in different ways, and supports diff # systemctl disable firewalld ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >The automatic startup is automatically disabled as the firewall is disabled. @@ -861,7 +861,7 @@ Each storage engine manages and stores data in different ways, and supports diff #### Creating a User Group and a User ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >In the server environment, independent users are assigned to each process to implement permission isolation for security purposes. The user group and user are created for the OS, not for the database. 1. Create a MySQL user or user group as the **root** user. @@ -885,7 +885,7 @@ Each storage engine manages and stores data in different ways, and supports diff #### Creating Data Drives ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >- If a performance test needs to be performed, an independent drive is required for the data directory. You need to format and mount the drive. For details, see Method 1 or Method 2. >- In a non-performance test, run the following command as the **root** user to create a data directory. Then skip this section. > \# mkdir /data @@ -923,13 +923,13 @@ Each storage engine manages and stores data in different ways, and supports diff In the last line, **/dev/nvme0n1p1** is only an example. - ![](figures/搭建数据盘.png) + ![](./figures/Creating_DataDisk.png) ##### Method 2: Using LVM for Drive Management as the **root** user ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >Install the LVM2 package in the image as follows: ->1. Configure the local yum source. For details, see [Configuring the Repo Server](configuring-the-repo-server.html). If the repository has been configured, skip this step. +>1. Configure the local yum source. For details, see [Configuring the Repo Server](./configuring-the-repo-server.html). If the repository has been configured, skip this step. >2. Install LVM2. > **\# yum install lvm2** @@ -971,7 +971,7 @@ Each storage engine manages and stores data in different ways, and supports diff In the last line, **/dev/datavg/datalv** is only an example. - ![](figures/d1376b2a-d036-41c4-b852-e8368f363b5e.png) + ![](./figures/d1376b2a-d036-41c4-b852-e8368f363b5e.png) #### Creating a Database Directory and Granting Permissions @@ -991,7 +991,7 @@ Each storage engine manages and stores data in different ways, and supports diff #### Installing MariaDB -1. Configure the local yum source. For details, see [Configuring the Repo Server](configuring-the-repo-server.html). +1. Configure the local yum source. For details, see [Configuring the Repo Server](./configuring-the-repo-server.html). 2. Clear the cache. ``` @@ -1041,7 +1041,7 @@ Each storage engine manages and stores data in different ways, and supports diff After the command is executed, the system prompts you to enter the password. The password is the one set in [2](#li197143190587). - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >Run the **\\q** or **exit** command to exit the database. @@ -1174,7 +1174,7 @@ In the preceding information: - **FOR 'username'@'hostname'**: specifies the username and hostname whose password is to be changed. This parameter is optional. - **PASSWORD\('newpassword'\)**: indicates that the **PASSWORD\(\)** function is used to set a new password. That is, the new password must be transferred to the **PASSWORD\(\)** function for encryption. ->![](public_sys-resources/icon-caution.gif) **CAUTION:** +>![](./public_sys-resources/icon-caution.gif) **CAUTION:** >The **PASSWORD\(\)** function is a unidirectional encryption function. Once encrypted, the original plaintext cannot be decrypted. If the **FOR** clause is not added to the **SET PASSWORD** statement, the password of the current user is changed. @@ -1198,7 +1198,7 @@ Use the **DROP USER** statement to delete one or more user accounts and relate DROP USER 'username1'@'hostname1' [,'username2'@'hostname2']...; ``` ->![](public_sys-resources/icon-caution.gif) **CAUTION:** +>![](./public_sys-resources/icon-caution.gif) **CAUTION:** >The deletion of users does not affect the tables, indexes, or other database objects that they have created, because the database does not record the accounts that have created these objects. The **DROP USER** statement can be used to delete one or more database accounts and their original permissions. @@ -1321,7 +1321,7 @@ In the preceding command, **databasename** indicates the database name. You can run the **DROP DATABASE** statement to delete a database. ->![](public_sys-resources/icon-caution.gif) **CAUTION:** +>![](./public_sys-resources/icon-caution.gif) **CAUTION:** >Exercise caution when deleting a database. Once a database is deleted, all tables and data in the database will be deleted. ``` @@ -1451,14 +1451,14 @@ The Structured Query Language \(SQL\) used by MySQL is the most common standard ### Configuring the Environment ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >The following environment configuration is for reference only. Configure the environment based on the site requirements. #### Disabling the Firewall and Automatic Startup ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >It is recommended that firewall be disabled in the test environment to prevent network impact. Configure the firewall based on actual requirements. 1. Stop the firewall service as the **root** user. @@ -1473,7 +1473,7 @@ The Structured Query Language \(SQL\) used by MySQL is the most common standard # systemctl disable firewalld ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >The automatic startup is automatically disabled as the firewall is disabled. @@ -1488,7 +1488,7 @@ The Structured Query Language \(SQL\) used by MySQL is the most common standard #### Creating a User Group and a User ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >In the server environment, independent users are assigned to each process to implement permission isolation for security purposes. The user group and user are created for the OS, not for the database. 1. Create a MySQL user or user group as the **root** user. @@ -1512,7 +1512,7 @@ The Structured Query Language \(SQL\) used by MySQL is the most common standard #### Creating Data Drives ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >- If a performance test needs to be performed, an independent drive is required for the data directory. You need to format and mount the drive. For details, see Method 1 or Method 2. >- In a non-performance test, run the following command as the **root** user to create a data directory. Then skip this section. > \# mkdir /data @@ -1550,13 +1550,13 @@ The Structured Query Language \(SQL\) used by MySQL is the most common standard In the last line, **/dev/nvme0n1p1** is only an example. - ![](figures/搭建数据盘-0.png) + ![](./figures/Creating_DataDisk-0.png) ##### Method 2: Using LVM for Drive Management as the **root** user ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >Install the LVM2 package in the image as follows: ->1. Configure the local yum source. For details, see [Configuring the Repo Server](configuring-the-repo-server.html). If the repository has been configured, skip this step. +>1. Configure the local yum source. For details, see [Configuring the Repo Server](./configuring-the-repo-server.html). If the repository has been configured, skip this step. >2. Install LVM2. > **\# yum install lvm2** @@ -1598,7 +1598,7 @@ The Structured Query Language \(SQL\) used by MySQL is the most common standard In the last line, **/dev/datavg/datalv** is only an example. - ![](figures/d1376b2a-d036-41c4-b852-e8368f363b5e-1.png) + ![](./figures/d1376b2a-d036-41c4-b852-e8368f363b5e-1.png) #### Creating a Database Directory and Granting Permissions @@ -1618,8 +1618,19 @@ The Structured Query Language \(SQL\) used by MySQL is the most common standard #### Installing MySQL - -1. Configure the local yum source. For details, see [Configuring the Repo Server](configuring-the-repo-server.html). +>![](./public_sys-resources/icon-note.gif) **NOTE:** +> For 20.03 LTS, if you run the **rpm -Uvh XXX** command (XXX indicates the version, for example, mysql-8.0.21-1.oe1.aarch64.rpm) to upgrade mysql-8.0.17-3.oe1 to the latest version, the functions are unavailable after the upgrade. You can use either of the following methods to upgrade the version. The following uses the upgrade from mysql-8.0.17-3.oe1 to mysql-8.0.21-1.oe1 as an example: +>- Method 1: Run the following upgrade command: +> ``` +> # rpm -Uvh mysql-8.0.21-1.oe1.aarch64.rpm --noscripts +> ``` +>- Method 2: Run the following commands to uninstall the MySQL of the earlier version and then install the MySQL of the new version: +> ``` +> # rpm -e mysql-8.0.17-3.oe1 +> # rpm -ivh mysql-8.0.21-1.oe1.aarch64.rpm +> ``` + +1. Configure the local yum source. For details, see [Configuring the Repo Server](./configuring-the-repo-server.html). 2. Clear the cache. ``` @@ -1682,9 +1693,9 @@ The Structured Query Language \(SQL\) used by MySQL is the most common standard $ cat /etc/my.cnf ``` - ![](figures/en-us_image_0231563132.png) + ![](./figures/en-us_image_0231563132.png) - >![](public_sys-resources/icon-caution.gif) **CAUTION:** + >![](./public_sys-resources/icon-caution.gif) **CAUTION:** >In the configuration file, **basedir** specifies the software installation path. Change it based on actual situation. 3. Change the group and user of the **/etc/my.cnf** file to **mysql:mysql** as the **root** user. @@ -1700,7 +1711,7 @@ The Structured Query Language \(SQL\) used by MySQL is the most common standard # echo export PATH=$PATH:/usr/local/mysql/bin >> /etc/profile ``` - >![](public_sys-resources/icon-caution.gif) **CAUTION:** + >![](./public_sys-resources/icon-caution.gif) **CAUTION:** >In the command, **/usr/local/mysql/bin** is the absolute path of the **bin** files in the MySQL software installation directory. Change it based on actual situation. 2. Run the following command as the **root** user to make the environment variables take effect: @@ -1711,7 +1722,7 @@ The Structured Query Language \(SQL\) used by MySQL is the most common standard 3. Initialize the database as the **root** user. - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >The second line from the bottom contains the initial password, which will be used when you log in to the database. ``` @@ -1725,7 +1736,7 @@ The Structured Query Language \(SQL\) used by MySQL is the most common standard 4. Start the database. - >![](public_sys-resources/icon-caution.gif) **CAUTION:** + >![](./public_sys-resources/icon-caution.gif) **CAUTION:** >Start MySQL as user **mysql** if it is the first time to start the database service. If you start MySQL as user **root**, a message will be displayed indicating that the **mysql.log** file is missing. If you start MySQL as user **mysql**, the **mysql.log** file will be generated in the **/data/mysql/log** directory. No error will be displayed if you start the database as user **root** again. 1. Modify the file permission as the **root** user. @@ -1750,7 +1761,7 @@ The Structured Query Language \(SQL\) used by MySQL is the most common standard 5. Log in to the database. - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >- Enter the initial password generated during database initialization \([3](#li15634560582)\). >- If MySQL is installed by using an RPM package obtained from the official website, the **mysqld** file is located in the **/usr/sbin** directory. Ensure that the directory specified in the command is correct. @@ -1758,7 +1769,7 @@ The Structured Query Language \(SQL\) used by MySQL is the most common standard $ /usr/local/mysql/bin/mysql -uroot -p -S /data/mysql/run/mysql.sock ``` - ![](figures/en-us_image_0231563134.png) + ![](./figures/en-us_image_0231563134.png) 6. Configure the database accounts and passwords. 1. After logging in to the database, change the password of user **root** for logging in to the database. @@ -1780,7 +1791,7 @@ The Structured Query Language \(SQL\) used by MySQL is the most common standard mysql>flush privileges; ``` - ![](figures/en-us_image_0231563135.png) + ![](./figures/en-us_image_0231563135.png) 7. Exit the database. @@ -1790,7 +1801,7 @@ The Structured Query Language \(SQL\) used by MySQL is the most common standard mysql>exit ``` - ![](figures/en-us_image_0231563136.png) + ![](./figures/en-us_image_0231563136.png) #### Uninstalling MySQL @@ -1943,7 +1954,7 @@ Use the **DROP USER** statement to delete one or more user accounts and relate DROP USER 'username1'@'hostname1' [,'username2'@'hostname2']...; ``` ->![](public_sys-resources/icon-caution.gif) **CAUTION:** +>![](./public_sys-resources/icon-caution.gif) **CAUTION:** >The deletion of users does not affect the tables, indexes, or other database objects that they have created, because the database does not record the accounts that have created these objects. The **DROP USER** statement can be used to delete one or more database accounts and their original permissions. @@ -2065,7 +2076,7 @@ In the preceding command, _databasename_ indicates the database name. Run the **DROP DATABASE** statement to delete a database. ->![](public_sys-resources/icon-caution.gif) **CAUTION:** +>![](./public_sys-resources/icon-caution.gif) **CAUTION:** >Exercise caution when deleting a database. Once a database is deleted, all tables and data in the database will be deleted. ``` diff --git a/content/en/docs/Administration/user-and-user-group-management.md b/docs/en/docs/20.03_LTS/docs/Administration/user-and-user-group-management.md similarity index 97% rename from content/en/docs/Administration/user-and-user-group-management.md rename to docs/en/docs/20.03_LTS/docs/Administration/user-and-user-group-management.md index a63178022f5bebfc4764bc4302eadf80708b2003..34306a56e606bf88006cfc3bb3340a854306ab44 100644 --- a/content/en/docs/Administration/user-and-user-group-management.md +++ b/docs/en/docs/20.03_LTS/docs/Administration/user-and-user-group-management.md @@ -48,7 +48,7 @@ For example, to create a user named userexample, run the following command as th # useradd userexample ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >If no prompt is displayed, the user is successfully created. After the user is created, run the **passwd** command to assign a password to the user. A new account without a password will be banned. To view information about the new user, run the **id** command: @@ -96,7 +96,7 @@ Retype new password: passwd: all authentication tokens updated successfully. ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >If the command output contains **BAD PASSWORD: The password fails the dictionary check - it is too simplistic/sytematic**, the password is too simple and needs to be reset. ### Modifying a User Account @@ -161,7 +161,7 @@ For example, run the following command to delete user Test: If you also need to delete the user's home directory and all contents in the directory, run the **userdel** command with the -r option to delete them recursively. ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >You are not advised to directly delete a user who has logged in to the system. To forcibly delete a user, run the **userdel -f** _Test_ command. ### Granting Rights to a Common User @@ -213,7 +213,7 @@ The information configured in the **/etc/sudoers** file is as follows: This indicates that newuser1 on the ted1 host can run the **useradd** and **userdel** commands as the user **root**. - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >- You can define multiple aliases in a line and separate them with colons \(:\). >- You can add an exclamation mark \(!\) before a command or a command alias to make the command or the command alias invalid. >- There are two keywords: ALL and NOPASSWD. ALL indicates all files, hosts, or commands, and NOPASSWD indicates that no password is required. @@ -297,7 +297,7 @@ For example, run the following command to delete user group Test: # groupdel Test ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >The user's primary group cannot be directly deleted. To forcibly delete a user's primary group, run the **groupdel -f** _Test_ command. ### Adding a User to a Group or Removing a User from a Group diff --git a/content/en/docs/Administration/using-the-dnf-to-manage-software-packages.md b/docs/en/docs/20.03_LTS/docs/Administration/using-the-dnf-to-manage-software-packages.md similarity index 98% rename from content/en/docs/Administration/using-the-dnf-to-manage-software-packages.md rename to docs/en/docs/20.03_LTS/docs/Administration/using-the-dnf-to-manage-software-packages.md index 4f2074cc13cc035f17b1184fd1d6cb83eab94c61..6a686762701d4f405776c0797fe34431e8078f29 100644 --- a/content/en/docs/Administration/using-the-dnf-to-manage-software-packages.md +++ b/docs/en/docs/20.03_LTS/docs/Administration/using-the-dnf-to-manage-software-packages.md @@ -2,7 +2,7 @@ DNF is a Linux software package management tool used to manage RPM software packages. The DNF can query software package information, obtain software packages from a specified software library, automatically process dependencies to install or uninstall software packages, and update the system to the latest available version. ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >- DNF is fully compatible with YUM and provides YUM-compatible command lines and APIs for extensions and plug-ins. >- You must have the administrator rights to use the DNF. All commands in this chapter must be executed by the administrator. @@ -130,7 +130,7 @@ The repository part allows you to customize openEuler software source repositori baseurl=repository_url ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >openEuler provides an online image source at [https://repo.openeuler.org/](https://repo.openeuler.org/). For example, if the openEuler 20.03 version is aarch64, the **baseurl** can be set to [https://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/](https://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/). Common options are as follows: @@ -160,7 +160,7 @@ The repository part allows you to customize openEuler software source repositori - Configuring the .repo file in the /etc/yum.repos.d directory - openEuler provides multiple repo sources for users online. For details about the repo sources, see [System Installation](../Releasenotes/installing-the-os.md.html). This section uses the OS repo source of the AArch64 architecture as an example. + openEuler provides multiple repo sources for users online. For details about the repo sources, see [System Installation](./../Releasenotes/installing-the-os.md.html). This section uses the OS repo source of the AArch64 architecture as an example. For example, run the following command as the **root** user to add the openeuler repo source to the openEuler_aarch64.repo file. @@ -178,7 +178,7 @@ The repository part allows you to customize openEuler software source repositori ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** > - **enabled** indicates whether to enable the software source repository. The value can be **1** or **0**. The default value is **1**, indicating that the software source repository is enabled. > - **gpgkey** is the public key used to verify the signature. @@ -356,8 +356,8 @@ The following is an example: # dnf install httpd ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** ->If the RPM package fails to be installed, see [Installation Failure Caused by Software Package Conflict, File Conflict, or Missing Software Package](faqs.html#installation-failure-caused-by-software-package-conflict-file-conflict-or-missing-software-package). +>![](./public_sys-resources/icon-note.gif) **NOTE:** +>If the RPM package fails to be installed, see [Installation Failure Caused by Software Package Conflict, File Conflict, or Missing Software Package](./faqs.html#installation-failure-caused-by-software-package-conflict-file-conflict-or-missing-software-package). ### Downloading Software Packages To download the software package using the DNF, run the following command as the user **root**: diff --git a/content/en/docs/Administration/using-the-kae.md b/docs/en/docs/20.03_LTS/docs/Administration/using-the-kae.md similarity index 97% rename from content/en/docs/Administration/using-the-kae.md rename to docs/en/docs/20.03_LTS/docs/Administration/using-the-kae.md index 66b0fd514d36a969872499fac630e00f9c55c890..e5bff76a309d992a96a3b455b3f20b1500a9843d 100644 --- a/content/en/docs/Administration/using-the-kae.md +++ b/docs/en/docs/20.03_LTS/docs/Administration/using-the-kae.md @@ -80,7 +80,7 @@ The KAE applies to the following scenarios, as shown in [Table 1](#table1191582 ##### Environment Requirements - The accelerator engine is enabled on TaiShan 200 servers. ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >- You need to import the accelerator license. For details, see section "License Management" in the [TaiShan Rack Server iBMC \(V500 or Later\) User Guide](https://support.huawei.com/enterprise/en/doc/EDOC1100121685/426cffd9?idPath=7919749|9856522|21782478|8060757). >- If the accelerator is used in the physical machine scenario, the SMMU must be disabled. For details, see the [TaiShan 200 Server BIOS Parameter Reference](https://support.huawei.com/enterprise/en/doc/EDOC1100088647). @@ -138,7 +138,7 @@ The KAE applies to the following scenarios, as shown in [Table 1](#table1191582 3. Use SSH to copy all accelerator engine software package to the created directory. 4. In the directory, run the **rpm -ivh** command to install the accelerator engine software packages. - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >Install the **libwd** package first because the **libkae** package installation depends on the **libwd** package. ``` @@ -282,7 +282,7 @@ You can run the following commands to test some accelerator functions. ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >\#After KAE acceleration, the signature performance is improved from 724.1 sign/s to 2819 sign/s. - Use the OpenSSL software algorithm to test the asynchronous RSA performance. @@ -304,7 +304,7 @@ You can run the following commands to test some accelerator functions. ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >\#After KAE acceleration, the asynchronous RSA signature performance is improved from 735.7 sign/s to 54384.1 sign/s. - Use the OpenSSL software algorithm to test the performance of the SM4 CBC mode. @@ -332,7 +332,7 @@ You can run the following commands to test some accelerator functions. ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >After KAE acceleration, the SM4 CBC mode performance is improved from 82312.53 kbit/s to 383317.33 kbit/s when the input data block size is 8 MB. - Use the OpenSSL software algorithm to test the SM3 mode performance. @@ -359,7 +359,7 @@ You can run the following commands to test some accelerator functions. ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >After KAE acceleration, the SM3 algorithm performance is improved from 52428.80 kbit/s to 668292.44 kbit/s when the input data block size is 8 MB. - Use the OpenSSL software algorithm to test the asynchronous performance of the AES algorithm in CBC mode. @@ -388,7 +388,7 @@ You can run the following commands to test some accelerator functions. ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >- The AES algorithm supports only asynchronous usage when the data length is 256 KB or less. >- After KAE acceleration, the AES algorithm performance is improved from 1123328.00 kbit/s to 3996774.40 kbit/s when the input data block size is 100 KB. @@ -405,15 +405,15 @@ You can run the **rpm -Uvh** command to upgrade the accelerator software. The command and output are as follows: - ![](figures/en-us_image_0231143189.png) + ![](./figures/en-us_image_0231143189.png) - ![](figures/en-us_image_0231143191.png) + ![](./figures/en-us_image_0231143191.png) 5. Run the **rpm -qa** command to check whether the upgrade is successful. Ensure that the queried version is the latest version. - ![](figures/en-us_image_0231143193.png) + ![](./figures/en-us_image_0231143193.png) - ![](figures/en-us_image_0231143195.png) + ![](./figures/en-us_image_0231143195.png) 6. Restart the system or run the following commands to manually uninstall the drivers of the earlier version, load the drivers of the latest version, and check whether the new drivers are successfully loaded. @@ -458,16 +458,16 @@ You do not need the accelerator engine software or you want to install new accel 3. Run the **rpm -e** command to uninstall the accelerator engine software packages. The following is an example: - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >Due to the dependency relationships, the **libkae** package must be uninstalled before the **libwd** package. - ![](figures/en-us_image_0231143196.png) + ![](./figures/en-us_image_0231143196.png) - ![](figures/en-us_image_0231143197.png) + ![](./figures/en-us_image_0231143197.png) 4. Run the **rpm -qa |grep** command to check whether the uninstallation is successful. - ![](figures/en-us_image_0231143198.png) + ![](./figures/en-us_image_0231143198.png) ## Querying Logs @@ -511,7 +511,7 @@ You do not need the accelerator engine software or you want to install new accel ## Acceleration Engine Application ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >If you have not purchased the engine license, you are advised not to use the KAE engine to invoke the corresponding algorithms. Otherwise, the performance of the OpenSSL encryption algorithm may be affected. diff --git a/content/en/docs/Administration/viewing-system-information.md b/docs/en/docs/20.03_LTS/docs/Administration/viewing-system-information.md similarity index 87% rename from content/en/docs/Administration/viewing-system-information.md rename to docs/en/docs/20.03_LTS/docs/Administration/viewing-system-information.md index 460bfa3bfff0bf5e5a08802b9e44037442e36086..322c28ac81b19afab4a59e2d0aff4a61a360311b 100644 --- a/content/en/docs/Administration/viewing-system-information.md +++ b/docs/en/docs/20.03_LTS/docs/Administration/viewing-system-information.md @@ -11,10 +11,10 @@ ``` $ cat /etc/os-release NAME="openEuler" - VERSION="20.09" + VERSION="20.03 (LTS)" ID="openEuler" - VERSION_ID="20.09" - PRETTY_NAME="openEuler 20.09" + VERSION_ID="20.03" + PRETTY_NAME="openEuler 20.03 (LTS)" ANSI_COLOR="0;31" ``` diff --git a/content/en/docs/ApplicationDev/application-development.md b/docs/en/docs/20.03_LTS/docs/ApplicationDev/application-development.md similarity index 96% rename from content/en/docs/ApplicationDev/application-development.md rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/application-development.md index d80e8b2f7d0a55040966ae74f04c1a3b2cde40b2..3aa54bc8eaf7e4d5925e303516445c2371a3f01c 100644 --- a/content/en/docs/ApplicationDev/application-development.md +++ b/docs/en/docs/20.03_LTS/docs/ApplicationDev/application-development.md @@ -29,13 +29,13 @@ The symbols that may be found in this document are defined as follows. -

+

![](./figures/en-us_image_0229243712.png）

Indicates a potentially hazardous situation which, if not avoided, could result in equipment damage, data loss, performance deterioration, or unanticipated results.

NOTICE is used to address practices not related to personal injury.

-

+

![](./figures/en-us_image_0229243671.png）

Supplements the important information in the main text.

NOTE is used to address information not related to personal injury, equipment damage, and environment deterioration.

@@ -80,7 +80,7 @@ The symbols that may be found in this document are defined as follows.

Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected.

-

{ x | y | ... }*

+

{ x | y | ... }\*

Optional items are grouped in brackets and separated by vertical bars. A minimum of one or a maximum of all can be selected.

diff --git a/content/en/docs/ApplicationDev/building-an-rpm-package.md b/docs/en/docs/20.03_LTS/docs/ApplicationDev/building-an-rpm-package.md similarity index 98% rename from content/en/docs/ApplicationDev/building-an-rpm-package.md rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/building-an-rpm-package.md index ff247ecf8f7e7e0ab0d52d6355ab02a75eee4a19..67eb3ad260d5840c53f246ae9cf8f74ad4b40b47 100644 --- a/content/en/docs/ApplicationDev/building-an-rpm-package.md +++ b/docs/en/docs/20.03_LTS/docs/ApplicationDev/building-an-rpm-package.md @@ -513,7 +513,7 @@ This section describes how to build an RPM software package online on OBS. #### Building an Existing Software Package ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >- If you use OBS for the first time, register an individual account on the OBS web page. >- With this method, you must copy the modified code and commit it to the code directory before performing the following operations. The code directory is specified in the **\_service** file. @@ -526,7 +526,7 @@ To modify the source code of the existing software and build the modified source 5. Click **Branch package**. In the displayed dialog box, click **Accept**, as shown in [Figure 1](#fig77646143214). **Figure 1** **Branch Confirmation** page - ![](figures/branch-confirmation-page.png "branch-confirmation-page") + ![](./figures/branch-confirmation-page.png "branch-confirmation-page") 6. Click the **\_service** file to go to the editing page, modify the file content, and click **Save**. An example of the **\_service** file content is as follows. _userCodeURL_ and _userCommitID_ indicate the user code path and commission version number or branch, respectively. @@ -544,14 +544,14 @@ To modify the source code of the existing software and build the modified source ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >Click **Save** to save the **\_service** file. OBS downloads the source code from the specified URL to the software directory of the corresponding OBS project based on the **\_service** file description and replaces the original file. For example, the **kernel** directory of the **openEuler:Mainline** project in the preceding example. 7. After the files are copied and replaced, OBS automatically starts to build the RPM software package. Wait until the build is complete and view the build status in the status bar on the right. - **succeeded**: The build is successful. You can click **succeeded** to view the build logs, as shown in [Figure 2](#fig10319114217337). **Figure 2** **Succeeded** page - ![](figures/succeeded-page.png "succeeded-page") + ![](./figures/succeeded-page.png "succeeded-page") - **failed**: The build failed. Click **failed** to view error logs, locate the fault, and rebuild again. - **unresolvable**: The build is not performed. The possible cause is that the dependency is missing. @@ -570,23 +570,23 @@ To add a new software package on the OBS web page, perform the following steps: 5. Click **Delete package** to delete the software package in the new subproject, as shown in [Figure 3](#fig18306181103615). **Figure 3** Deleting a software package from a subproject - ![](figures/deleting-a-software-package-from-a-subproject.png "deleting-a-software-package-from-a-subproject") + ![](./figures/deleting-a-software-package-from-a-subproject.png "deleting-a-software-package-from-a-subproject") - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >The purpose of creating a project by using existing software is to inherit the dependency such as the environment. Therefore, you need to delete these files. 6. Click **Create Package**. On the page that is displayed, enter the software package name, title, and description, and click **Create** to create a software package, as shown in [Figure 4](#fig6762111693811) and [Figure 5](#fig18351153518389). **Figure 4** **Create Package** page - ![](figures/create-package-page.png "create-package-page") + ![](./figures/create-package-page.png "create-package-page") **Figure 5** Creating a software package - ![](figures/creating-a-software-package.png "creating-a-software-package") + ![](./figures/creating-a-software-package.png "creating-a-software-package") 7. Click **Add file** to upload the .spec file and the file to be compiled \(specified in the .spec file\), as shown in [Figure 6](#fig1475845284011). **Figure 6** **Add file** page - ![](figures/add-file-page.png "add-file-page") + ![](./figures/add-file-page.png "add-file-page") 8. After the file is uploaded, OBS automatically starts to build the RPM software package. Wait until the build is complete and view the build status in the status bar on the right. - **succeeded**: The build is successful. You can click **succeeded** to view the build logs. @@ -604,15 +604,15 @@ After the RPM software package is built, perform the following operations to obt 2. Click **All Projects** and find the project corresponding to the required software package, for example, **openEuler:Mainline**. 3. Click the name of the required software package in the project. The software package details page is displayed, for example, the **kernel** page in the preceding example. -1. Click the **Repositories** tab. On the software repository management page that is displayed, click **Enable** in **Publish Flag** to enable the RPM software package download function \(the status changes from ![](figures/en-us_image_0229243704.png) to ![](figures/en-us_image_0229243702.png)\), as shown in [Figure 7](#fig17480830144217). +1. Click the **Repositories** tab. On the software repository management page that is displayed, click **Enable** in **Publish Flag** to enable the RPM software package download function \(the status changes from ![](./figures/en-us_image_0229243704.png) to ![](./figures/en-us_image_0229243702.png)\), as shown in [Figure 7](#fig17480830144217). **Figure 7** **Repositories** page - ![](figures/repositories-page.png "repositories-page") + ![](./figures/repositories-page.png "repositories-page") 2. Click the project name in the **Repository** column. On the RPM software package download page that is displayed, click **Download** on the right of the RPM software package to download the RPM software package, as shown in [Figure 8](#fig12152145615438). **Figure 8** RPM software package download page - ![](figures/rpm-software-package-download-page.png "rpm-software-package-download-page") + ![](./figures/rpm-software-package-download-page.png "rpm-software-package-download-page") ### Building a Software Package Using OSC @@ -633,7 +633,7 @@ You have obtained the **root** permission, and have configured a repo source f # dnf install osc build ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >The compilation of RPM software packages depends on build. 2. Configure the OSC. @@ -732,7 +732,7 @@ You have obtained the **root** permission, and have configured a repo source f $ osc buildlog standard_aarch64 aarch64 ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >You can also open the created project on the web client to view the build logs. @@ -788,7 +788,7 @@ To use the OSC tool of OBS to add a new software package, perform the following $ osc buildlog standard_aarch64 aarch64 ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >You can also open the created project on the web client to view the build logs. @@ -807,6 +807,6 @@ The parameters in the command are described as follows. You can modify the param - _standard\_aarch64_: repository name. - _aarch64_: repository architecture name. ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >You can also obtain the software package built using OSC from the web page. For details, see [Obtaining the Software Package](#obtaining-the-software-package). diff --git a/content/en/docs/ApplicationDev/figures/add-file-page.png b/docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/add-file-page.png similarity index 100% rename from content/en/docs/ApplicationDev/figures/add-file-page.png rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/add-file-page.png diff --git a/content/en/docs/ApplicationDev/figures/branch-confirmation-page.png b/docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/branch-confirmation-page.png similarity index 100% rename from content/en/docs/ApplicationDev/figures/branch-confirmation-page.png rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/branch-confirmation-page.png diff --git a/content/en/docs/ApplicationDev/figures/create-package-page.png b/docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/create-package-page.png similarity index 100% rename from content/en/docs/ApplicationDev/figures/create-package-page.png rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/create-package-page.png diff --git a/content/en/docs/ApplicationDev/figures/creating-a-software-package.png b/docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/creating-a-software-package.png similarity index 100% rename from content/en/docs/ApplicationDev/figures/creating-a-software-package.png rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/creating-a-software-package.png diff --git a/content/en/docs/ApplicationDev/figures/deleting-a-software-package-from-a-subproject.png b/docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/deleting-a-software-package-from-a-subproject.png similarity index 100% rename from content/en/docs/ApplicationDev/figures/deleting-a-software-package-from-a-subproject.png rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/deleting-a-software-package-from-a-subproject.png diff --git a/content/en/docs/ApplicationDev/figures/en-us_image_0229243671.png b/docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/en-us_image_0229243671.png similarity index 100% rename from content/en/docs/ApplicationDev/figures/en-us_image_0229243671.png rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/en-us_image_0229243671.png diff --git a/content/en/docs/ApplicationDev/figures/en-us_image_0229243702.png b/docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/en-us_image_0229243702.png similarity index 100% rename from content/en/docs/ApplicationDev/figures/en-us_image_0229243702.png rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/en-us_image_0229243702.png diff --git a/content/en/docs/ApplicationDev/figures/en-us_image_0229243704.png b/docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/en-us_image_0229243704.png similarity index 100% rename from content/en/docs/ApplicationDev/figures/en-us_image_0229243704.png rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/en-us_image_0229243704.png diff --git a/content/en/docs/ApplicationDev/figures/en-us_image_0229243712.png b/docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/en-us_image_0229243712.png similarity index 100% rename from content/en/docs/ApplicationDev/figures/en-us_image_0229243712.png rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/en-us_image_0229243712.png diff --git a/content/en/docs/ApplicationDev/figures/repositories-page.png b/docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/repositories-page.png similarity index 100% rename from content/en/docs/ApplicationDev/figures/repositories-page.png rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/repositories-page.png diff --git a/content/en/docs/ApplicationDev/figures/rpm-software-package-download-page.png b/docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/rpm-software-package-download-page.png similarity index 100% rename from content/en/docs/ApplicationDev/figures/rpm-software-package-download-page.png rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/rpm-software-package-download-page.png diff --git a/content/en/docs/ApplicationDev/figures/succeeded-page.png b/docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/succeeded-page.png similarity index 100% rename from content/en/docs/ApplicationDev/figures/succeeded-page.png rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/figures/succeeded-page.png diff --git a/content/en/docs/ApplicationDev/preparation.md b/docs/en/docs/20.03_LTS/docs/ApplicationDev/preparation.md similarity index 90% rename from content/en/docs/ApplicationDev/preparation.md rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/preparation.md index 32e097dab4e27478964471a5317f770204c5fb71..5b03fc1adf9e672b7b21863a5e2003f30b65d953 100644 --- a/content/en/docs/ApplicationDev/preparation.md +++ b/docs/en/docs/20.03_LTS/docs/ApplicationDev/preparation.md @@ -117,7 +117,7 @@ The openEuler OS is required. -For details about how to install the openEuler OS, see the \[*openEuler 20.09 Installation Guide*\](../Installation/Installation.html ). On the **SOFTWARE SELECTION** page, select **Development Tools** in the **Add-Ons for Selected Environment** area. +For details about how to install the openEuler OS, see the \[*openEuler 20.03 LTS Installation Guide*\](./../Installation/Installation.html ). On the **SOFTWARE SELECTION** page, select **Development Tools** in the **Add-Ons for Selected Environment** area. ## Configuring a Repo Source @@ -125,38 +125,42 @@ Configure an online yum source by directly obtaining the online openEuler repo s ### Configuring a Repo Source by Directly Obtaining the Repo Source File -> ![](public_sys-resources/icon-note.gif) **NOTE:** -> openEuler provides multiple repo sources for users online. For details about the repo sources, see [System Installation](../Releasenotes/installing-the-os.html). This section uses the **openEuler\_aarch64.repo** file as an example to describe how to configure the OS repo source as the yum source. +> ![](./public_sys-resources/icon-note.gif) **NOTE:** +> openEuler provides multiple repo sources for users online. For details about the repo sources, see [System Installation](./../Releasenotes/installing-the-os.html). This section uses the **openEuler\_aarch64.repo** file as an example to describe how to configure the OS repo source as the yum source. 1. Go to the yum source directory and check the .repo configuration file in the directory. ``` $ cd /etc/yum.repos.d $ ls - openEuler.repo + openEuler_aarch64.repo ``` 2. Edit the **openEuler\_aarch64.repo** file as the **root** user. Configure the online openEuler repo source as the yum source. ``` - # vi openEuler.repo + # vi openEuler_aarch64.repo ``` Edit the **openEuler\_aarch64.repo** file as follows: ``` [osrepo] + name=osrepo - baseurl=http://repo.openeuler.org/openEuler-20.09/OS/aarch64/ + + baseurl=http://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/ + enabled=1 + gpgcheck=1 - gpgkey=http://repo.openeuler.org/openEuler-20.09/OS/aarch64/RPM-GPG-KEY-openEuler + gpgkey=http://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/RPM-GPG-KEY-openEuler ``` **** - > ![](public_sys-resources/icon-note.gif) **NOTE:** + > ![](./public_sys-resources/icon-note.gif) **NOTE:** > > - The repoid in \[*repoid* \] indicates the ID of the software repository. Repoids in all .repo configuration files must be unique. In the example, repoid is set to **base**. > - **name** indicates the string that the software repository describes. @@ -168,8 +172,8 @@ Configure an online yum source by directly obtaining the online openEuler repo s ### Configuring a Repo Source by Mounting an ISO File -> ![](public_sys-resources/icon-note.gif) ********NOTE:******** -> openEuler provides multiple ISO release packages. For details about each ISO release package, see [System Installation](../Releasenotes/installing-the-os.html). This section uses the **openEuler-20.09-aarch64-dvd.iso** file and **openEuler-20.09-aarch64-dvd.iso.sha256sum** verification file as examples. Modify them based on the actual requirements. +> ![](./public_sys-resources/icon-note.gif) ********NOTE:******** +> openEuler provides multiple ISO release packages. For details about each ISO release package, see [System Installation](./../Releasenotes/installing-the-os.html). This section uses the **openEuler-20.03-LTS-aarch64-dvd.iso** file and **openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum** verification file as examples. Modify them based on the actual requirements. 1. Download the ISO release package. @@ -181,7 +185,7 @@ Configure an online yum source by directly obtaining the online openEuler repo s 3. Click the link provided after **Download ISO**. The download list is displayed. - 4. Select the version to be downloaded, for example, openEuler 20.03 LTS. Then, click **openEuler-20.09**. The download list is displayed. + 4. Select the version to be downloaded, for example, openEuler 20.03 LTS. Then, click **openEuler-20.03-LTS**. The download list is displayed. 5. Click **ISO**. The ISO download list is displayed. @@ -191,9 +195,9 @@ Configure an online yum source by directly obtaining the online openEuler repo s 6. Click **aarch64**. - 7. Click **openEuler-20.09-aarch64-dvd.iso** to download the openEuler release package to the local host. + 7. Click **openEuler-20.03-LTS-aarch64-dvd.iso** to download the openEuler release package to the local host. - 8. Click **openEuler-20.09-aarch64-dvd.iso.sha256sum** to download the openEuler verification file to the local host. + 8. Click **openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum** to download the openEuler verification file to the local host. 9. Log in to the openEuler OS and create a directory for storing the release package and verification file, for example, ~/iso\*\*. @@ -211,7 +215,7 @@ Configure an online yum source by directly obtaining the online openEuler repo s 3. Click the link provided after **Download ISO**. The download list is displayed. - 4. Select the version to be downloaded, for example, openEuler 20.09. Then, click **openEuler-20.09**. The download list is displayed. + 4. Select the version to be downloaded, for example, openEuler 20.03 LTS. Then, click **openEuler-20.03-LTS**. The download list is displayed. 5. Click **ISO**. The ISO download list is displayed. @@ -221,9 +225,9 @@ Configure an online yum source by directly obtaining the online openEuler repo s 6. Click **aarch64**. - 7. Right-click **openEuler-20.09-aarch64-dvd.iso** and choose **Copy URL** from the shortcut menu to copy the address of the openEuler release package. + 7. Right-click **openEuler-20.03-LTS-aarch64-dvd.iso** and choose **Copy URL** from the shortcut menu to copy the address of the openEuler release package. - 8. Right-click **openEuler-20.09-aarch64-dvd.iso.sha256sum** and choose **Copy URL** from the shortcut menu to copy the address of the openEuler verification file. + 8. Right-click **openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum** and choose **Copy URL** from the shortcut menu to copy the address of the openEuler verification file. 9. Log in to the openEuler OS, create a directory (for example, **~/iso**) for storing the release package and verification file, and switch to the directory. @@ -244,13 +248,13 @@ Configure an online yum source by directly obtaining the online openEuler repo s 1. Obtain the verification value in the verification file. ``` - $ cat openEuler-20.09-aarch64-dvd.iso.sha256sum + $ cat openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum ``` 2. Calculate the SHA256 verification value of the openEuler release package. ``` - $ sha256sum openEuler-20.09-aarch64-dvd.iso + $ sha256sum openEuler-20.03-LTS-aarch64-dvd.iso ``` After the command is run, the verification value is displayed. @@ -266,7 +270,7 @@ Configure an online yum source by directly obtaining the online openEuler repo s The following is an example: ``` - # mount /home/iso/openEuler-20.09-aarch64-dvd.iso /mnt/ + # mount /home/iso/openEuler-20.03-LTS-aarch64-dvd.iso /mnt/ ``` The mounted **mnt** directory is as follows: @@ -290,24 +294,28 @@ Configure an online yum source by directly obtaining the online openEuler repo s ``` $ cd /etc/yum.repos.d $ ls - openEuler.repo + openEuler_aarch64.repo ``` 6. Edit the **openEuler\_aarch64.repo** file as the **root** user. Configure the local openEuler repo source created in step [3](#li6236932222) as the yum source. ``` - # vi openEuler.repo + # vi openEuler_aarch64.repo ``` Edit the **openEuler\_aarch64.repo** file as follows: ``` - [localosrepo] + [localosrepo] + name=localosrepo + baseurl=file:///mnt + enabled=1 + gpgcheck=1 - gpgkey=file:///mnt/RPM-GPG-KEY-openEuler + gpgkey=file:///mnt/RPM-GPG-KEY-openEuler ``` ## Installing the Software Package diff --git a/content/en/docs/ApplicationDev/public_sys-resources/icon-caution.gif b/docs/en/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-caution.gif similarity index 100% rename from content/en/docs/ApplicationDev/public_sys-resources/icon-caution.gif rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-caution.gif diff --git a/content/en/docs/ApplicationDev/public_sys-resources/icon-danger.gif b/docs/en/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-danger.gif similarity index 100% rename from content/en/docs/ApplicationDev/public_sys-resources/icon-danger.gif rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-danger.gif diff --git a/content/en/docs/ApplicationDev/public_sys-resources/icon-note.gif b/docs/en/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-note.gif similarity index 100% rename from content/en/docs/ApplicationDev/public_sys-resources/icon-note.gif rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-note.gif diff --git a/content/en/docs/ApplicationDev/public_sys-resources/icon-notice.gif b/docs/en/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-notice.gif similarity index 100% rename from content/en/docs/ApplicationDev/public_sys-resources/icon-notice.gif rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-notice.gif diff --git a/content/en/docs/ApplicationDev/public_sys-resources/icon-tip.gif b/docs/en/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-tip.gif similarity index 100% rename from content/en/docs/ApplicationDev/public_sys-resources/icon-tip.gif rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-tip.gif diff --git a/content/en/docs/ApplicationDev/public_sys-resources/icon-warning.gif b/docs/en/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-warning.gif similarity index 100% rename from content/en/docs/ApplicationDev/public_sys-resources/icon-warning.gif rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-warning.gif diff --git a/content/en/docs/ApplicationDev/using-gcc-for-compilation.md b/docs/en/docs/20.03_LTS/docs/ApplicationDev/using-gcc-for-compilation.md similarity index 99% rename from content/en/docs/ApplicationDev/using-gcc-for-compilation.md rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/using-gcc-for-compilation.md index 173ff7bd287c0671f1bf091738445f8c6eff8731..bd66aaf38282ff97ec281d35e0af4dfb933f0e17 100644 --- a/content/en/docs/ApplicationDev/using-gcc-for-compilation.md +++ b/docs/en/docs/20.03_LTS/docs/ApplicationDev/using-gcc-for-compilation.md @@ -312,7 +312,7 @@ If you choose to search for a DLL, to ensure that the DLL can be linked when the $ export LD\_LIBRARY\_PATH=libraryDIR:$LD\_LIBRARY\_PATH - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >**LD\_LIBRARY\_PATH** is an environment variable of the DLL. If the DLL is not in the default directories \(**/lib** and **/usr/lib**\), you need to specify the environment variable **LD\_LIBRARY\_PATH**. - Add the DLL path **libaryDIR** to **/etc/ld.so.conf** and run **ldconfig**, or use the DLL path **libaryDIR** as a parameter to run **ldconfig**. diff --git a/content/en/docs/ApplicationDev/using-jdk-for-compilation.md b/docs/en/docs/20.03_LTS/docs/ApplicationDev/using-jdk-for-compilation.md similarity index 100% rename from content/en/docs/ApplicationDev/using-jdk-for-compilation.md rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/using-jdk-for-compilation.md diff --git a/content/en/docs/ApplicationDev/using-make-for-compilation.md b/docs/en/docs/20.03_LTS/docs/ApplicationDev/using-make-for-compilation.md similarity index 100% rename from content/en/docs/ApplicationDev/using-make-for-compilation.md rename to docs/en/docs/20.03_LTS/docs/ApplicationDev/using-make-for-compilation.md diff --git a/content/en/docs/Container/appendix-1.md b/docs/en/docs/20.03_LTS/docs/Container/appendix-1.md similarity index 100% rename from content/en/docs/Container/appendix-1.md rename to docs/en/docs/20.03_LTS/docs/Container/appendix-1.md diff --git a/content/en/docs/Container/appendix-2.md b/docs/en/docs/20.03_LTS/docs/Container/appendix-2.md similarity index 99% rename from content/en/docs/Container/appendix-2.md rename to docs/en/docs/20.03_LTS/docs/Container/appendix-2.md index 483c1d83b6e4135f70aafb888058366c50342ace..5f8bd66983e6f629d444b4266394a13fde79ac44 100644 --- a/content/en/docs/Container/appendix-2.md +++ b/docs/en/docs/20.03_LTS/docs/Container/appendix-2.md @@ -6,7 +6,7 @@ ## configuration.toml ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >The value of each field in the **configuration.toml** file is subject to the **configuration.toml** file in the **kata-containers-<**_version_**\>.rpm package**. You cannot set any field in the configuration file. ``` @@ -127,7 +127,7 @@ experimental: enables the experimental feature, which does not support user-defi

Sets the name of the NIC on a host.

-

Mandatory. The value can contain a maximum of 15 characters, including letters, digits, underscores (_), hyphens (-), and periods (.). It must start with a letter. The device name must be unique on the same host.

+

Mandatory. The value can contain a maximum of 15 characters, including letters, digits, underscores (\_), hyphens (-), and periods (.). It must start with a letter. The device name must be unique on the same host.

name

diff --git a/content/en/docs/Container/appendix.md b/docs/en/docs/20.03_LTS/docs/Container/appendix.md similarity index 100% rename from content/en/docs/Container/appendix.md rename to docs/en/docs/20.03_LTS/docs/Container/appendix.md diff --git a/content/en/docs/Container/application-scenarios-2.md b/docs/en/docs/20.03_LTS/docs/Container/application-scenarios-2.md similarity index 100% rename from content/en/docs/Container/application-scenarios-2.md rename to docs/en/docs/20.03_LTS/docs/Container/application-scenarios-2.md diff --git a/content/en/docs/Container/application-scenarios.md b/docs/en/docs/20.03_LTS/docs/Container/application-scenarios.md similarity index 100% rename from content/en/docs/Container/application-scenarios.md rename to docs/en/docs/20.03_LTS/docs/Container/application-scenarios.md diff --git a/content/en/docs/Container/checking-the-container-health-status.md b/docs/en/docs/20.03_LTS/docs/Container/checking-the-container-health-status.md similarity index 100% rename from content/en/docs/Container/checking-the-container-health-status.md rename to docs/en/docs/20.03_LTS/docs/Container/checking-the-container-health-status.md diff --git a/content/en/docs/Container/command-reference.md b/docs/en/docs/20.03_LTS/docs/Container/command-reference.md similarity index 100% rename from content/en/docs/Container/command-reference.md rename to docs/en/docs/20.03_LTS/docs/Container/command-reference.md diff --git a/content/en/docs/Container/configurable-cgroup-path.md b/docs/en/docs/20.03_LTS/docs/Container/configurable-cgroup-path.md similarity index 100% rename from content/en/docs/Container/configurable-cgroup-path.md rename to docs/en/docs/20.03_LTS/docs/Container/configurable-cgroup-path.md diff --git a/content/en/docs/Container/configuring-networking-for-a-secure-container.md b/docs/en/docs/20.03_LTS/docs/Container/configuring-networking-for-a-secure-container.md similarity index 98% rename from content/en/docs/Container/configuring-networking-for-a-secure-container.md rename to docs/en/docs/20.03_LTS/docs/Container/configuring-networking-for-a-secure-container.md index ae4bbcea38c500e6eab7603423c1d5c23d7433f1..001355c89d3ee5d8426dfd8bb199310105275cfb 100644 --- a/content/en/docs/Container/configuring-networking-for-a-secure-container.md +++ b/docs/en/docs/20.03_LTS/docs/Container/configuring-networking-for-a-secure-container.md @@ -117,7 +117,7 @@ Related commands are as follows: null ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >If an IP address is specified for an NIC that is successfully added, Kata adds a default route whose destination is in the same network segment as the IP address of the NIC. In the preceding example, after the NIC is added, the following route is added to the container: >``` >[root@6ec7a98 /]# ip route @@ -197,7 +197,7 @@ Related commands are as follows: - **gateway**: Next-hop gateway of the route. When **"dest":"default"** is configured, the gateway is mandatory. In other cases, this parameter is optional. - **device**: Name of the NIC corresponding to the route, which is mandatory. The value contains a maximum of 15 characters. - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >If a route is added for the loopback device **lo** in the container, the device name corresponding to the **device** field in the route configuration file is **lo**. 4. **Run the following command to delete a specified route:** @@ -228,7 +228,7 @@ Related commands are as follows: null ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >- In the input fields, **dest** is mandatory, and both **device** and **gateway** are optional. Kata performs fuzzy match based on different fields and deletes the corresponding routing rules. For example, if **dest** is set to an IP address, all rules of this IP address will be deleted. >- If the route of the loopback device **lo** in the container is deleted, the device name corresponding to the **device** field in the route configuration file is **lo**. @@ -238,7 +238,7 @@ Related commands are as follows: $ cat ./test-iface.json | kata-runtime kata-network del-iface 6ec7a98 - ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >When deleting an NIC, you can only delete it based on the **name** field in the NIC container. Kata does not identify other fields. The following describes the output of the **kata-runtime kata-network del-iface **command for deleting NICs: @@ -317,7 +317,7 @@ The secure container provides an API for adding the **ipvs** command and setti kata-runtime kata-ipvs ipvsadm --restore - < ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >By default, the NAT mode is used for adding a single real server. To add real servers in batches, you need to manually add the **-m** option to use the NAT mode. >The following is an example of the rule file content: >-A -t 10.10.11.12:100 -s rr -p 3000 @@ -337,7 +337,7 @@ The secure container provides an API for adding the **ipvs** command and setti kata-runtime kata-ipvs ipvsadm --parameters "--set 100 100 200" ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >1. Each container supports a maximum of 20000 iptables rules \(5000 services and three servers/services\). Both add-service and add-server are rules. >2. Before importing rules in batches, you need to clear existing rules. >3. No concurrent test scenario exists. diff --git a/content/en/docs/Container/configuring-resources-for-a-secure-container.md b/docs/en/docs/20.03_LTS/docs/Container/configuring-resources-for-a-secure-container.md similarity index 98% rename from content/en/docs/Container/configuring-resources-for-a-secure-container.md rename to docs/en/docs/20.03_LTS/docs/Container/configuring-resources-for-a-secure-container.md index 09c05bf98473557a452aa9d67b4f2aed5ec89a11..ded03af6d5b7f39ab1e55bb239fec3a7687b45f2 100644 --- a/content/en/docs/Container/configuring-resources-for-a-secure-container.md +++ b/docs/en/docs/20.03_LTS/docs/Container/configuring-resources-for-a-secure-container.md @@ -45,7 +45,7 @@ When a pod is started, all containers in the pod share the same net namespace an Socket(s): 4 ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >The maximum number of CPUs that can be configured is the number of CPUs \(excluding isolated cores\) that can run on the OS. The minimum number of CPUs is 0.5. 2. Configure CPU resources for running a container. @@ -98,7 +98,7 @@ When a pod is started, all containers in the pod share the same net namespace an 3. Configure CPU hot swap. - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >The CPU hot swap function of the secure container requires the virtualization component QEMU. The **enable\_cpu\_memory\_hotplug** option in the kata-runtime configuration file **config.toml** is used to enable or disable CPU and memory hot swap. The default value is **false**, indicating that CPU and memory hot swap is disabled. If the value is **true**, CPU and memory hot swap is enabled. @@ -157,7 +157,7 @@ When a pod is started, all containers in the pod share the same net namespace an    - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >The pause container is only a placeholder container and does not have any workload. Therefore, when a lightweight VM is started, the CPU allocated by default can be shared by other containers. Therefore, you only need to hot add three CPUs to the lightweight VM for the new container started in the preceding example. - After the container where the CPU is hot added is stopped, the CPU is removed when the container is started. @@ -187,7 +187,7 @@ When a pod is started, all containers in the pod share the same net namespace an Swap: 0 0 0 ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >- If the memory size of a lightweight VM is not set using **--annotation com.github.containers.virtcontainers.sandbox\_mem**, the lightweight VM uses 1 GB memory by default. >- The minimum memory size of a pod in a secure container is 1 GB, and the maximum memory size is 256 GB. If the memory size allocated to a user exceeds 256 GB, an undefined error may occur. Currently, secure containers do not support the scenario where the memory size exceeds 256 GB. @@ -216,7 +216,7 @@ When a pod is started, all containers in the pod share the same net namespace an The memory hot add function is also configured by the **enable\_cpu\_memory\_hotplug** option in the kata-runtime configuration file **config.toml**. For details, see [3](#limiting-cpu-resources.md#en-us_topic_0183903699_li2167326144011). - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >Currently, memory resources support hot add only. The **-m** option is reused in kata-runtime to implement the memory hot add function. The sum of the **-m** options of all containers in a pod is collected to determine the number of memories to be hot added to a lightweight VM. @@ -255,7 +255,7 @@ When a pod is started, all containers in the pod share the same net namespace an Swap: 0 0 0 ``` - >![](public_sys-resources/icon-note.gif) **NOTE:** + >![](./public_sys-resources/icon-note.gif) **NOTE:** >The pause container is only a placeholder container and does not have any workload. Therefore, the memory allocated to the lightweight VM during startup can be shared by other containers. You only need to hot add 3 GB memory to the lightweight VM for the new container started in the preceding example. @@ -334,7 +334,7 @@ The secure container reuses the **--files-limit** option in the **docker run* docker run -tid --runtime kata-runtime --network none --annotation io.kubernetes.docker.type=podsandbox --files-limit bash ``` ->![](public_sys-resources/icon-note.gif) **NOTE:** +>![](./public_sys-resources/icon-note.gif) **NOTE:** >- If the value of **--files-limit** is less than the default minimum value **1024** and is not **0**, the maximum number of file descriptors that can be opened by the QEMU process of the secure container is set to the minimum value **1024**. >- If the value of **--files-limit** is 0, the maximum number of file descriptors that can be opened by the QEMU process of the secure container is the default value obtained by dividing the maximum number of file descriptors that can be opened by the system \(/proc/sys/fs/file-max\) by 400. >- If the maximum number of file descriptors that can be opened by the QEMU process of the secure container is not displayed when the secure container is started, the maximum number of file descriptors that can be opened by the QEMU process of the secure container is the same as the system default value. diff --git a/content/en/docs/Container/container-engine.md b/docs/en/docs/20.03_LTS/docs/Container/container-engine.md similarity index 99% rename from content/en/docs/Container/container-engine.md rename to docs/en/docs/20.03_LTS/docs/Container/container-engine.md index 58147841a9fd75a8cf9ab7dcfe3fb0c627af57b1..5b8e754314ec95d9f920c49da86af5b650de6898 100644 --- a/content/en/docs/Container/container-engine.md +++ b/docs/en/docs/20.03_LTS/docs/Container/container-engine.md @@ -128,9 +128,7 @@ The **docker** command supports the following parameters:

Parameter to be executed when a container is started.

For example, set the native.umask parameter.

-
#The umask value of the started container is 0022.
---exec-opt native.umask=normal 
-
+
#The umask value of the started container is 0022.--exec-opt native.umask=normal 
 #The umask value of the started container is 0027 (default value).
 --exec-opt  native.umask=secure    

 
Note: If native.umask is also configured in docker create or docker run command, the configuration in command is used.

diff --git a/content/en/docs/Container/container-management-1.md b/docs/en/docs/20.03_LTS/docs/Container/container-management-1.md
similarity index 99%
rename from content/en/docs/Container/container-management-1.md
rename to docs/en/docs/20.03_LTS/docs/Container/container-management-1.md
index 6b22156ca3dbc69a130f7d4bc1ce3c42a72f3654..0619fdd77430868ca53239aee2d6f4aea8cb2ec4 100644
--- a/content/en/docs/Container/container-management-1.md
+++ b/docs/en/docs/20.03_LTS/docs/Container/container-management-1.md
@@ -578,7 +578,7 @@ When the container is running, the health check status is written into the conta
 }
 ```
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >-   A maximum of five health check status records can be stored in a container. The last five records are saved.  
 >-   Only one health check configuration item can take effect in a container at a time. The later items configured in the Dockerfile will overwrite the earlier ones. Configurations during container creation will overwrite those in images.  
 >-   In the Dockerfile, you can set  **HEALTHCHECK NONE**  to cancel the health check configuration in a referenced image. When a container is running, you can set  **--no-healthcheck**  to cancel the health check configuration in an image. Do not configure the health check and  **--no-healthcheck**  parameters at the same time during the startup.  
diff --git a/content/en/docs/Container/container-management-2.md b/docs/en/docs/20.03_LTS/docs/Container/container-management-2.md
similarity index 99%
rename from content/en/docs/Container/container-management-2.md
rename to docs/en/docs/20.03_LTS/docs/Container/container-management-2.md
index dbde4ac1f49c094e1d763b50d7473915598c4c1b..1ce5d85ff343c2f1e84c0cc1f0d917d373236146 100644
--- a/content/en/docs/Container/container-management-2.md
+++ b/docs/en/docs/20.03_LTS/docs/Container/container-management-2.md
@@ -1029,7 +1029,7 @@ Example:
 $ sudo docker restart busybox
 ```
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >During the container restart, if a process in the  **D**  or  **Z**  state exists in the container, the container may fail to be restarted. In this case, you need to analyze the cause of the  **D**  or  **Z**  state of the process in the container. Restart the container after the  **D**  or  **Z**  state of the process in the container is released.  
 
 ## rm
diff --git a/content/en/docs/Container/container-management.md b/docs/en/docs/20.03_LTS/docs/Container/container-management.md
similarity index 99%
rename from content/en/docs/Container/container-management.md
rename to docs/en/docs/20.03_LTS/docs/Container/container-management.md
index 3597e9b292bee333c781a3a8e28614c22fccb41b..cc81d13b9c691fb1efc0253043f442eedf07bfe6 100644
--- a/content/en/docs/Container/container-management.md
+++ b/docs/en/docs/20.03_LTS/docs/Container/container-management.md
@@ -740,12 +740,12 @@ The following table lists the parameters supported by the  **run**  command.
     
     
 
-    >![](public_sys-resources/icon-notice.gif) **NOTICE:**   
+    >![](./public_sys-resources/icon-notice.gif) **NOTICE:**   
     >Scenario 1: Mount  **/home/test1**  and then  **/home/test2**. In this case, the content in  **/home/test1**  overwrites the content in  **/mnt**. As a result, the  **abc**  directory does not exist in  **/mnt**, and mounting** /home/test2**  to  **/mnt/abc**  fails.  
     >Scenario 2: Mount  **/home/test2**  and then  **/home/test1**. In this case, the content of  **/mnt**  is replaced with the content of  **/home/test1**  during the second mounting. In this way, the content mounted during the first mounting from  **/home/test2**  to  **/mnt/abc**  is overwritten.  
     >The first scenario is not supported. For the second scenario, users need to understand the risk of data access failures.  
 
-    >![](public_sys-resources/icon-notice.gif) **NOTICE:**   
+    >![](./public_sys-resources/icon-notice.gif) **NOTICE:**   
     >-   In high concurrency scenarios \(200 containers are concurrently started\), the memory management mechanism of Glibc may cause memory holes and large virtual memory \(for example, 10 GB\). This problem is caused by the restriction of the Glibc memory management mechanism in the high concurrency scenario, but not by memory leakage. Therefore, the memory consumption does not increase infinitely. You can set the  **MALLOC\_ARENA\_MAX**  environment variable to reduce the virtual memory and increase the probability of reducing the physical memory. However, this environment variable will cause the iSulad concurrency performance to deteriorate. Set this environment variable based on the site requirements.  
     >    ```  
     >    To balance performance and memory usage, set MALLOC_ARENA_MAX to 4. (The iSulad performance deterioration on the ARM64 server is controlled by less than 10%.)  
@@ -1241,7 +1241,7 @@ The following table lists the parameters supported by the  **inspect**  command.
 
 ### Constraints
 
--   Lightweight containers do not support the output in \{\{.State\}\} format but support the output in the \{\{json .State\}\} format. The  **-f**  parameter is not supported when the object is an image.
+-   Lightweight containers do not support the output in \{ \{.State\} \} format but support the output in the \{ \{json .State\} \} format. The  **-f**  parameter is not supported when the object is an image.
 
 ### Example
 
diff --git a/content/en/docs/Container/container-resource-management.md b/docs/en/docs/20.03_LTS/docs/Container/container-resource-management.md
similarity index 99%
rename from content/en/docs/Container/container-resource-management.md
rename to docs/en/docs/20.03_LTS/docs/Container/container-resource-management.md
index b09a880f1ec839182e397772a70fc16f8c3ae63f..3b7166202e7354619bb61d14e55eaa1d0386e9c3 100644
--- a/content/en/docs/Container/container-resource-management.md
+++ b/docs/en/docs/20.03_LTS/docs/Container/container-resource-management.md
@@ -168,7 +168,7 @@ To restrict a container to use a specific CPU, add  **--cpuset-cpus number**  wh
 isula run -tid --cpuset-cpus 0,2-3 busybox sh
 ```
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >You can check whether the configuration is successful. For details, see "Querying Information About a Single Container."  
 
 ## Restricting the Memory Usage of a Running Container
@@ -459,7 +459,7 @@ overlay                  10.0M     10.0M         0 100% /
 
     When using iSulad with the quota function to switch data disks, ensure that the data disks to be switched are mounted using the  **prjquota**  option and the mounting mode of the  **/var/lib/isulad/storage/overlay2**  directory is the same as that of the  **/var/lib/isulad**  directory.
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >Before switching the data disk, ensure that the mount point of  **/var/lib/isulad/storage/overlay2**  is unmounted.  
 
 
diff --git a/content/en/docs/Container/container.md b/docs/en/docs/20.03_LTS/docs/Container/container.md
similarity index 100%
rename from content/en/docs/Container/container.md
rename to docs/en/docs/20.03_LTS/docs/Container/container.md
diff --git a/content/en/docs/Container/cri.md b/docs/en/docs/20.03_LTS/docs/Container/cri.md
similarity index 99%
rename from content/en/docs/Container/cri.md
rename to docs/en/docs/20.03_LTS/docs/Container/cri.md
index 00bd00dd44c01724efe4a38d020d4c5d5c436732..cd412f0664db94d13f0fcbe4e3c9cd08245022cf 100644
--- a/content/en/docs/Container/cri.md
+++ b/docs/en/docs/20.03_LTS/docs/Container/cri.md
@@ -44,7 +44,7 @@ The current CRI version is v1alpha1. For official API description, access the fo
 
 iSulad uses the API description file of version 1.14 used by Pass, which is slightly different from the official API description file. API description in this document prevails.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >The listening IP address of the CRI WebSocket streaming service is  **127.0.0.1**  and the port number is  **10350**. The port number can be configured in the  **--websocket-server-listening-port**  command or in the  **daemon.json**  configuration file.  
 
 ## APIs
diff --git a/content/en/docs/Container/docker-container.md b/docs/en/docs/20.03_LTS/docs/Container/docker-container.md
similarity index 100%
rename from content/en/docs/Container/docker-container.md
rename to docs/en/docs/20.03_LTS/docs/Container/docker-container.md
diff --git a/content/en/docs/Container/dynamically-loading-the-kernel-module.md b/docs/en/docs/20.03_LTS/docs/Container/dynamically-loading-the-kernel-module.md
similarity index 96%
rename from content/en/docs/Container/dynamically-loading-the-kernel-module.md
rename to docs/en/docs/20.03_LTS/docs/Container/dynamically-loading-the-kernel-module.md
index ae2efef6eef35d14072b5f71877a710d98bc93a3..7c1458075e1501d1422440e86b86ad3f3512467d 100644
--- a/content/en/docs/Container/dynamically-loading-the-kernel-module.md
+++ b/docs/en/docs/20.03_LTS/docs/Container/dynamically-loading-the-kernel-module.md
@@ -5,7 +5,7 @@ Dynamically Loading the Kernel Module
 
 ## Function Description
 
-Services in a container may depend on some kernel modules. You can set environment variables to dynamically load the kernel modules required by services in the container to the host before the system container starts. This feature must be used together with isulad-hooks. For details, see  [Dynamically Managing Container Resources \(syscontainer-tools\)](dynamically-managing-container-resources-(syscontainer-tools).md).
+Services in a container may depend on some kernel modules. You can set environment variables to dynamically load the kernel modules required by services in the container to the host before the system container starts. This feature must be used together with isulad-hooks. For details, see  [Dynamically Managing Container Resources \(syscontainer-tools\)](./dynamically-managing-container-resources-(syscontainer-tools).md).
 
 ## Parameter Description
 
@@ -50,7 +50,7 @@ nf_defrag_ipv6         20480  2 nf_conntrack,ip_vs
 libcrc32c              16384  3 nf_conntrack,nf_nat,ip_vs
 ```
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >-   isulad-tools must be installed on the host.  
 >-   **--hooks-spec**  must be set to  **isulad hooks**.  
 
diff --git a/content/en/docs/Container/dynamically-managing-container-resources-(syscontainer-tools).md b/docs/en/docs/20.03_LTS/docs/Container/dynamically-managing-container-resources-(syscontainer-tools).md
similarity index 99%
rename from content/en/docs/Container/dynamically-managing-container-resources-(syscontainer-tools).md
rename to docs/en/docs/20.03_LTS/docs/Container/dynamically-managing-container-resources-(syscontainer-tools).md
index 50f9a0602506b9d40ce5c640e5c7664fef3b3cd1..1c0aa377631d6c50d51d63b5b89fba237f1f658f 100644
--- a/content/en/docs/Container/dynamically-managing-container-resources-(syscontainer-tools).md
+++ b/docs/en/docs/20.03_LTS/docs/Container/dynamically-managing-container-resources-(syscontainer-tools).md
@@ -254,7 +254,7 @@ In the preceding format:
     Add network interface to container 2aaca5c1af7c (eth3,eth1) done
     ```
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >When adding a virtual or physical NIC, ensure that the NIC is in the idle state. Adding a NIC in use will disconnect the system network.  
 
 
diff --git a/content/en/docs/Container/environment-variable-persisting.md b/docs/en/docs/20.03_LTS/docs/Container/environment-variable-persisting.md
similarity index 100%
rename from content/en/docs/Container/environment-variable-persisting.md
rename to docs/en/docs/20.03_LTS/docs/Container/environment-variable-persisting.md
diff --git a/content/en/docs/Container/figures/en-us_image_0183048952.png b/docs/en/docs/20.03_LTS/docs/Container/figures/en-us_image_0183048952.png
similarity index 100%
rename from content/en/docs/Container/figures/en-us_image_0183048952.png
rename to docs/en/docs/20.03_LTS/docs/Container/figures/en-us_image_0183048952.png
diff --git a/content/en/docs/Container/figures/en-us_image_0221924926.png b/docs/en/docs/20.03_LTS/docs/Container/figures/en-us_image_0221924926.png
similarity index 100%
rename from content/en/docs/Container/figures/en-us_image_0221924926.png
rename to docs/en/docs/20.03_LTS/docs/Container/figures/en-us_image_0221924926.png
diff --git a/content/en/docs/Container/figures/en-us_image_0221924927.png b/docs/en/docs/20.03_LTS/docs/Container/figures/en-us_image_0221924927.png
similarity index 100%
rename from content/en/docs/Container/figures/en-us_image_0221924927.png
rename to docs/en/docs/20.03_LTS/docs/Container/figures/en-us_image_0221924927.png
diff --git a/content/en/docs/Container/figures/relationship-between-the-secure-container-and-peripheral-components.png b/docs/en/docs/20.03_LTS/docs/Container/figures/relationship-between-the-secure-container-and-peripheral-components.png
similarity index 100%
rename from content/en/docs/Container/figures/relationship-between-the-secure-container-and-peripheral-components.png
rename to docs/en/docs/20.03_LTS/docs/Container/figures/relationship-between-the-secure-container-and-peripheral-components.png
diff --git "a/content/en/docs/Container/figures/\345\256\211\345\205\250\345\256\271\345\231\250\346\241\206\346\236\2661.png" b/docs/en/docs/20.03_LTS/docs/Container/figures/sec-container.png
similarity index 100%
rename from "content/en/docs/Container/figures/\345\256\211\345\205\250\345\256\271\345\231\250\346\241\206\346\236\2661.png"
rename to docs/en/docs/20.03_LTS/docs/Container/figures/sec-container.png
diff --git a/content/en/docs/Container/image-management-1.md b/docs/en/docs/20.03_LTS/docs/Container/image-management-1.md
similarity index 100%
rename from content/en/docs/Container/image-management-1.md
rename to docs/en/docs/20.03_LTS/docs/Container/image-management-1.md
diff --git a/content/en/docs/Container/image-management-2.md b/docs/en/docs/20.03_LTS/docs/Container/image-management-2.md
similarity index 100%
rename from content/en/docs/Container/image-management-2.md
rename to docs/en/docs/20.03_LTS/docs/Container/image-management-2.md
diff --git a/content/en/docs/Container/image-management.md b/docs/en/docs/20.03_LTS/docs/Container/image-management.md
similarity index 100%
rename from content/en/docs/Container/image-management.md
rename to docs/en/docs/20.03_LTS/docs/Container/image-management.md
diff --git a/content/en/docs/Container/installation-and-deployment-1.md b/docs/en/docs/20.03_LTS/docs/Container/installation-and-deployment-1.md
similarity index 100%
rename from content/en/docs/Container/installation-and-deployment-1.md
rename to docs/en/docs/20.03_LTS/docs/Container/installation-and-deployment-1.md
diff --git a/content/en/docs/Container/installation-and-deployment-2.md b/docs/en/docs/20.03_LTS/docs/Container/installation-and-deployment-2.md
similarity index 99%
rename from content/en/docs/Container/installation-and-deployment-2.md
rename to docs/en/docs/20.03_LTS/docs/Container/installation-and-deployment-2.md
index 287c55db39ee38d50a510bb350e0394fa426ec53..e001954b7c15c4d9daa8d8ab930826bf67c20bcf 100644
--- a/content/en/docs/Container/installation-and-deployment-2.md
+++ b/docs/en/docs/20.03_LTS/docs/Container/installation-and-deployment-2.md
@@ -52,12 +52,12 @@ cat /etc/docker/daemon.json
 
 Re-configuring various running directories and files \(including  **--graph**  and  **--exec-root**\) may cause directory conflicts or file attribute changes, affecting the normal use of applications.
 
->![](public_sys-resources/icon-notice.gif) **NOTICE:**   
+>![](./public_sys-resources/icon-notice.gif) **NOTICE:**   
 >Therefore, the specified directories or files should be used only by Docker to avoid file attribute changes and security issues caused by conflicts.  
 
 -   Take  **--graph**  as an example. When  **/new/path/**  is used as the new root directory of the daemon, if a file exists in  **/new/path/**  and the directory or file name conflicts with that required by Docker \(for example,  **containers**,  **hooks**, and  **tmp**\), Docker may update the original directory or file attributes, including the owner and permission.
 
->![](public_sys-resources/icon-notice.gif) **NOTICE:**   
+>![](./public_sys-resources/icon-notice.gif) **NOTICE:**   
 >From Docker 17.05, the  **--graph**  parameter is marked as  **Deprecated**  and replaced with the  **--data-root**  parameter.  
 
 ### Daemon Network Configuration
@@ -72,7 +72,7 @@ The default  **umask**  value of the main container process and exec process is
 
 The default value of  **umask**  is  **0027**  when Docker starts a container. You can change the value to  **0022**  by running the  **--exec-opt native.umask=normal**  command during container startup.
 
->![](public_sys-resources/icon-notice.gif) **NOTICE:**   
+>![](./public_sys-resources/icon-notice.gif) **NOTICE:**   
 >If  **native.umask**  is configured in  **docker create**  or  **docker run**  command, its value is used.  
 
 For details, see the parameter description in  [4.6.2.4 create](#create.md#EN-US_TOPIC_0184808242)  and  [4.6.2.16 run](#container-management-40.md#EN-US_TOPIC_0184808238).
@@ -145,7 +145,7 @@ The following uses  **-w /var/lib/docker -k docker**  as an example to describe
 [root@localhost signal]# auditctl -l | grep docker -w /var/lib/docker/ -p rwxa -k docker
 ```
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >**-p \[r|w|x|a\]**  and  **-w**  are used together to monitor the read, write, execution, and attribute changes \(such as timestamp changes\) of the directory. In this case, any file or directory operation in the  **/var/lib/docker**  directory will be recorded in the  **audit.log**  file. As a result, too many logs will be recorded in the  **audit.log**  file, which severely affects the memory or CPU usage of the auditd, and further affects the OS. For example, logs similar to the following will be recorded in the  **/var/log/audit/audit.log**  file each time the  **ls /var/lib/docker/containers**  command is executed:  
 
 ```
@@ -447,7 +447,7 @@ When a system is unexpectedly powered off or system panic occurs, Docker daemon
     -   Cache construction: The cache construction information will be deleted after the node is restarted.
     -   Metadata stored in containerd: Metadata stored in containerd will be recreated when a container is started. Therefore, the metadata stored in containerd will be deleted when the node is restarted.
 
-        >![](public_sys-resources/icon-note.gif) **NOTE:**   
+        >![](./public_sys-resources/icon-note.gif) **NOTE:**   
         >If you want to manually clear data and restore the environment, you can set the environment variable  **DISABLE\_CRASH\_FILES\_DELETE**  to  **true**  to disable the function of clearing DB files when the daemon process is restarted due to power-off.  
 
 
diff --git a/content/en/docs/Container/installation-configuration.md b/docs/en/docs/20.03_LTS/docs/Container/installation-configuration.md
similarity index 99%
rename from content/en/docs/Container/installation-configuration.md
rename to docs/en/docs/20.03_LTS/docs/Container/installation-configuration.md
index 0ac4a800c3f0d9de03fdd6e22ce1f9db5919c743..50f0d97008c28b7b1441fae52af44bc0ff695998 100644
--- a/content/en/docs/Container/installation-configuration.md
+++ b/docs/en/docs/20.03_LTS/docs/Container/installation-configuration.md
@@ -1,7 +1,7 @@
 # Installation and Configuration 
 
 
-- [Installation and Configuration](installation-configuration)
+- [Installation and Configuration](./installation-configuration)
     - [Installation Methods](#installation-methods)
     - [Deployment Configuration](#deployment-configuration)
         - [Configuration Mode](#configuration-mode)
@@ -39,7 +39,7 @@ This section describes two installation methods.
 
 The iSulad server daemon  **isulad**  can be configured with a configuration file or by running the  **isulad --xxx**  command. The priority in descending order is as follows: CLI \> configuration file \> default configuration in code.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >If systemd is used to manage the iSulad process, modify the  **OPTIONS**  field in the  **/etc/sysconfig/iSulad**  file, which functions the same as using the CLI.  
 
 -   **CLI**
@@ -485,7 +485,7 @@ The iSulad server daemon  **isulad**  can be configured with a configuration fil
     }
     ```
 
-    >![](public_sys-resources/icon-notice.gif) **NOTICE:**   
+    >![](./public_sys-resources/icon-notice.gif) **NOTICE:**   
     >The default configuration file  **/etc/isulad/daemon.json**  is for reference only. Configure it based on site requirements.  
 
 
@@ -500,14 +500,14 @@ The iSulad server daemon  **isulad**  can be configured with a configuration fil
 
 
 
-
*

+
\*

 
 
/etc/default/isulad/

 
 
Stores the OCI configuration file and hook template file of iSulad. The file configuration permission is set to 0640, and the sysmonitor check permission is set to 0550.

 
 
-
*

+
\*

 
 
/etc/isulad/

 
@@ -528,35 +528,35 @@ The iSulad server daemon  **isulad**  can be configured with a configuration fil
 
File for storing the iSulad PIDs. It is also a file lock to prevent multiple iSulad instances from being started.

 
 
-
*

+
\*

 
 
/run/lxc/

 
 
Lock file, which is created during iSulad running.

 
 
-
*

+
\*

 
 
/var/run/isulad/

 
 
Real-time communication cache file, which is created during iSulad running.

 
 
-
*

+
\*

 
 
/var/run/isula/

 
 
Real-time communication cache file, which is created during iSulad running.

 
 
-
*

+
\*

 
 
/var/lib/lcr/

 
 
Temporary directory of the LCR component.

 
 
-
*

+
\*

 
 
/var/lib/isulad/

 
@@ -588,7 +588,7 @@ The iSulad server daemon  **isulad**  can be configured with a configuration fil
 
 -   Log file management:
 
-    >![](public_sys-resources/icon-notice.gif) **NOTICE:**   
+    >![](./public_sys-resources/icon-notice.gif) **NOTICE:**   
     >Log function interconnection: logs are managed by systemd as iSulad is and then transmitted to rsyslogd. By default, rsyslog restricts the log writing speed. You can add the configuration item  **$imjournalRatelimitInterval 0**  to the  **/etc/rsyslog.conf**  file and restart the rsyslogd service.  
 
 -   Restrictions on command line parameter parsing
@@ -782,7 +782,7 @@ Mode 1 is used for the server, and mode 2 for the client if the two-way authenti
 
 Mode 2 is used for the server and the client if the unidirectional authentication mode is used for communication.
 
->![](public_sys-resources/icon-notice.gif) **NOTICE:**   
+>![](./public_sys-resources/icon-notice.gif) **NOTICE:**   
 >-   If RPM is used for installation, the server configuration can be modified in the  **/etc/isulad/daemon.json**  and  **/etc/sysconfig/iSulad**  files.  
 >-   Two-way authentification is recommended as it is more secure than non-authentication or unidirectional authentication.  
 >-   GRPC open-source component logs are not taken over by iSulad. To view gRPC logs, set the environment variables  **gRPC\_VERBOSITY**  and  **gRPC\_TRACE**  as required.  
diff --git a/content/en/docs/Container/installation-guideline.md b/docs/en/docs/20.03_LTS/docs/Container/installation-guideline.md
similarity index 100%
rename from content/en/docs/Container/installation-guideline.md
rename to docs/en/docs/20.03_LTS/docs/Container/installation-guideline.md
diff --git a/content/en/docs/Container/installation-upgrade-Uninstallation.md b/docs/en/docs/20.03_LTS/docs/Container/installation-upgrade-Uninstallation.md
similarity index 100%
rename from content/en/docs/Container/installation-upgrade-Uninstallation.md
rename to docs/en/docs/20.03_LTS/docs/Container/installation-upgrade-Uninstallation.md
diff --git a/content/en/docs/Container/interconnection-with-the-cni-network.md b/docs/en/docs/20.03_LTS/docs/Container/interconnection-with-the-cni-network.md
similarity index 99%
rename from content/en/docs/Container/interconnection-with-the-cni-network.md
rename to docs/en/docs/20.03_LTS/docs/Container/interconnection-with-the-cni-network.md
index eea018fcb02e3f99dfaa79f1a67766156aeaaba1..ea181545190975bf2c889636a7975a51db940254 100644
--- a/content/en/docs/Container/interconnection-with-the-cni-network.md
+++ b/docs/en/docs/20.03_LTS/docs/Container/interconnection-with-the-cni-network.md
@@ -114,7 +114,7 @@ If  **--network-plugin=cni**  is configured for iSulad and the default network p
 
 When StopPodSandbox is called, the interface for removing a pod from the CNI network list will be called to clear network resources.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >1. Before calling the RemovePodSandbox interface, you must call the StopPodSandbox interface at least once.  
 >2. If StopPodSandbox fails to call the CNI, residual network resources may exist.  
 
diff --git a/content/en/docs/Container/isulad-container-engine.md b/docs/en/docs/20.03_LTS/docs/Container/isulad-container-engine.md
similarity index 93%
rename from content/en/docs/Container/isulad-container-engine.md
rename to docs/en/docs/20.03_LTS/docs/Container/isulad-container-engine.md
index 5e5299c966d38474dfd602f0b4f100388a2609ba..54cd5ca2112776a9d584b4eb2e5132607a5dd743 100644
--- a/content/en/docs/Container/isulad-container-engine.md
+++ b/docs/en/docs/20.03_LTS/docs/Container/isulad-container-engine.md
@@ -8,5 +8,5 @@ Compared with Docker, iSulad is a new container solution with a unified architec
 **Figure  1**  Unified container architecture  
 
 
-![](figures/en-us_image_0183048952.png)
+![](./figures/en-us_image_0183048952.png)
 
diff --git a/content/en/docs/Container/managing-the-lifecycle-of-a-secure-container.md b/docs/en/docs/20.03_LTS/docs/Container/managing-the-lifecycle-of-a-secure-container.md
similarity index 97%
rename from content/en/docs/Container/managing-the-lifecycle-of-a-secure-container.md
rename to docs/en/docs/20.03_LTS/docs/Container/managing-the-lifecycle-of-a-secure-container.md
index d6a2cb3265d314e699a7a3cb198f033657724011..c16a2ee9a8a087af3d2b3643aba0a162d85f8b2a 100644
--- a/content/en/docs/Container/managing-the-lifecycle-of-a-secure-container.md
+++ b/docs/en/docs/20.03_LTS/docs/Container/managing-the-lifecycle-of-a-secure-container.md
@@ -36,7 +36,7 @@ To start a secure container, perform the following steps:
     isula run -tid --runtime kata-runtime --network none busybox 
     ```
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >The secure container supports the CNI network only and does not support the CNM network. The  **-p**  and  **--expose**  options cannot be used to expose container ports. When using a secure container, you need to specify the  **--net=none**  option.  
 
 4.  Start a pod.
@@ -101,7 +101,7 @@ The pause container functions only as a placeholder container. Therefore, if you
 docker exec -ti  
 ```
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >1.  If the preceding command has no response because another host runs the  **docker restart**  or  **docker stop**  command to access the same container, you can press  **Ctrl**+**P**+**Q**  to exit the operation.  
 >2.  If the  **-d**  option is used, the command is executed in the background and no error information is displayed. The exit code cannot be used to determine whether the command is executed correctly.  
 
diff --git a/content/en/docs/Container/maximum-number-of-handles.md b/docs/en/docs/20.03_LTS/docs/Container/maximum-number-of-handles.md
similarity index 100%
rename from content/en/docs/Container/maximum-number-of-handles.md
rename to docs/en/docs/20.03_LTS/docs/Container/maximum-number-of-handles.md
diff --git a/content/en/docs/Container/monitoring-secure-containers.md b/docs/en/docs/20.03_LTS/docs/Container/monitoring-secure-containers.md
similarity index 100%
rename from content/en/docs/Container/monitoring-secure-containers.md
rename to docs/en/docs/20.03_LTS/docs/Container/monitoring-secure-containers.md
diff --git a/content/en/docs/Container/privileged-container.md b/docs/en/docs/20.03_LTS/docs/Container/privileged-container.md
similarity index 100%
rename from content/en/docs/Container/privileged-container.md
rename to docs/en/docs/20.03_LTS/docs/Container/privileged-container.md
diff --git a/content/en/docs/Container/public_sys-resources/icon-caution.gif b/docs/en/docs/20.03_LTS/docs/Container/public_sys-resources/icon-caution.gif
similarity index 100%
rename from content/en/docs/Container/public_sys-resources/icon-caution.gif
rename to docs/en/docs/20.03_LTS/docs/Container/public_sys-resources/icon-caution.gif
diff --git a/content/en/docs/Container/public_sys-resources/icon-danger.gif b/docs/en/docs/20.03_LTS/docs/Container/public_sys-resources/icon-danger.gif
similarity index 100%
rename from content/en/docs/Container/public_sys-resources/icon-danger.gif
rename to docs/en/docs/20.03_LTS/docs/Container/public_sys-resources/icon-danger.gif
diff --git a/content/en/docs/Container/public_sys-resources/icon-note.gif b/docs/en/docs/20.03_LTS/docs/Container/public_sys-resources/icon-note.gif
similarity index 100%
rename from content/en/docs/Container/public_sys-resources/icon-note.gif
rename to docs/en/docs/20.03_LTS/docs/Container/public_sys-resources/icon-note.gif
diff --git a/content/en/docs/Container/public_sys-resources/icon-notice.gif b/docs/en/docs/20.03_LTS/docs/Container/public_sys-resources/icon-notice.gif
similarity index 100%
rename from content/en/docs/Container/public_sys-resources/icon-notice.gif
rename to docs/en/docs/20.03_LTS/docs/Container/public_sys-resources/icon-notice.gif
diff --git a/content/en/docs/Container/public_sys-resources/icon-tip.gif b/docs/en/docs/20.03_LTS/docs/Container/public_sys-resources/icon-tip.gif
similarity index 100%
rename from content/en/docs/Container/public_sys-resources/icon-tip.gif
rename to docs/en/docs/20.03_LTS/docs/Container/public_sys-resources/icon-tip.gif
diff --git a/content/en/docs/Container/public_sys-resources/icon-warning.gif b/docs/en/docs/20.03_LTS/docs/Container/public_sys-resources/icon-warning.gif
similarity index 100%
rename from content/en/docs/Container/public_sys-resources/icon-warning.gif
rename to docs/en/docs/20.03_LTS/docs/Container/public_sys-resources/icon-warning.gif
diff --git a/content/en/docs/Container/querying-information.md b/docs/en/docs/20.03_LTS/docs/Container/querying-information.md
similarity index 100%
rename from content/en/docs/Container/querying-information.md
rename to docs/en/docs/20.03_LTS/docs/Container/querying-information.md
diff --git a/content/en/docs/Container/reboot-or-shutdown-in-a-container.md b/docs/en/docs/20.03_LTS/docs/Container/reboot-or-shutdown-in-a-container.md
similarity index 100%
rename from content/en/docs/Container/reboot-or-shutdown-in-a-container.md
rename to docs/en/docs/20.03_LTS/docs/Container/reboot-or-shutdown-in-a-container.md
diff --git a/content/en/docs/Container/secure-container.md b/docs/en/docs/20.03_LTS/docs/Container/secure-container.md
similarity index 90%
rename from content/en/docs/Container/secure-container.md
rename to docs/en/docs/20.03_LTS/docs/Container/secure-container.md
index 5f5e7b51446f18fc11dd1fc025e6cef8d8467c36..0be359e1b7e5c03ad5503c059141f3131c203050 100644
--- a/content/en/docs/Container/secure-container.md
+++ b/docs/en/docs/20.03_LTS/docs/Container/secure-container.md
@@ -12,7 +12,7 @@ Secure containers are isolated by the virtualization layers. Containers on the s
 **Figure  1**  Secure container architecture  
 
 
-![](figures/安全容器框架1.png)
+![](./figures/sec-container.png)
 
 Secure containers are closely related to the concept of pod in Kubernetes. Kubernetes is the open-source ecosystem standard for the container scheduling management platform. It defines a group of container runtime interfaces \(CRIs\).
 
@@ -25,5 +25,5 @@ In a secure container, you can start a single container or start a pod.
 [Figure 2](#fig17734185518269)  shows the relationship between the secure container and peripheral components.
 
 **Figure  2**  Relationship between the secure container and peripheral components  
-![](figures/relationship-between-the-secure-container-and-peripheral-components.png "relationship-between-the-secure-container-and-peripheral-components")
+![](./figures/relationship-between-the-secure-container-and-peripheral-components.png "relationship-between-the-secure-container-and-peripheral-components")
 
diff --git a/content/en/docs/Container/security-and-isolation.md b/docs/en/docs/20.03_LTS/docs/Container/security-and-isolation.md
similarity index 99%
rename from content/en/docs/Container/security-and-isolation.md
rename to docs/en/docs/20.03_LTS/docs/Container/security-and-isolation.md
index ad8608788471782846e03fca5bc8336732c8caf1..ada1aada90a1c37d05acf92751d5ed5c0f461eb8 100644
--- a/content/en/docs/Container/security-and-isolation.md
+++ b/docs/en/docs/20.03_LTS/docs/Container/security-and-isolation.md
@@ -49,7 +49,7 @@ In system containers, you can configure the  **--user-remap**  API parameter to
 
 ### Usage Guide
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >Before specifying the  **--user-remap**  parameter, configure an offset value for UIDs and GIDs of all directories and files in rootfs. The offset value should be equal to that for  _uid_  and  _gid_  in  **--user-remap**.  
 >For example, run the following command to offset UIDs and GIDs of all files in the  **dev**  directory with 100000:  
 >chown 100000:100000 dev  
@@ -187,7 +187,7 @@ You can configure the startup parameters of the iSulad container engine to speci
     -   Alice can perform any container operations:  **\{"name":"policy\_5","users":\["alice"\],"actions":\["container"\]\}**
     -   Alice can perform any container operations, but the request type can only be  **get**:  **\{"name":"policy\_5","users":\["alice"\],"actions":\["container"\], "readonly":true\}**
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >-   **action**  indicates that regular expressions are supported.  
     >-   **users**  indicates that regular expressions are not supported.  
     >-   Users configured in  **users**  must be unique. That is, a user cannot match multiple rules.  
diff --git a/content/en/docs/Container/security-features.md b/docs/en/docs/20.03_LTS/docs/Container/security-features.md
similarity index 98%
rename from content/en/docs/Container/security-features.md
rename to docs/en/docs/20.03_LTS/docs/Container/security-features.md
index 09eab1a3e499c34b36687f3d232d9a9ad0833839..667f89a14a263b34ef6ce9ca001524cd907fe09b 100644
--- a/content/en/docs/Container/security-features.md
+++ b/docs/en/docs/20.03_LTS/docs/Container/security-features.md
@@ -47,7 +47,7 @@ Use  **--security-opt**  to transfer the configuration file to the container whe
 isula run -itd --security-opt seccomp=/path/to/seccomp/profile.json rnd-dockerhub.huawei.com/official/busybox
 ```
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >1.  When the configuration file is transferred to the container by using  **--security-opt**  during container creation, the default configuration file \(**/etc/isulad/seccomp\_default.json**\) is used.  
 >2.  When  **--security-opt**  is set to  **unconfined**  during container creation, system calls are not filtered for the container.  
 >3.  **/path/to/seccomp/profile.json**  must be an absolute path.  
@@ -133,7 +133,7 @@ The configuration file template is as follows:
 }
 ```
 
->![](public_sys-resources/icon-notice.gif) **NOTICE:**   
+>![](./public_sys-resources/icon-notice.gif) **NOTICE:**   
 >-   **defaultAction**  and  **syscalls**: The types of their corresponding actions are the same, but their values must be different. The purpose is to ensure that each syscall has a default action. Clear definitions in the syscall array shall prevail. As long as the values of  **defaultAction**  and  **action**  are different, no action conflicts will occur. The following actions are supported:  
 >    **SCMP\_ACT\_ERRNO**: forbids calling syscalls and displays error information.  
 >    **SCMP\_ACT\_ALLOW**: allows calling syscalls.  
@@ -217,7 +217,7 @@ Security-Enhanced Linux \(SELinux\) is a Linux kernel security module that provi
 -   The introduction of SELinux affects the performance. Therefore, evaluate the scenario before setting SELinux. Enable the SELinux function for the daemon and set the SELinux configuration in the container only when necessary.
 -   When you configure labels for a mounted volume, the source directory cannot be a subdirectory of  **/**,  **/usr**,  **/etc**,  **/tmp**,  **/home**,  **/run**,  **/var**,  **/root**, or  **/usr**.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >-   iSulad does not support labeling the container file system. To ensure that the container file system and configuration directory are labeled with the container access permission, run the  **chcon**  command to label them.  
 >-   If SELinux access control is enabled for iSulad, you are advised to add a label to the  **/var/lib/isulad**  directory before starting daemon. Files and folders generated in the directory during container creation inherit the label by default. For example:  
 >    ```  
diff --git a/content/en/docs/Container/shared-memory-channels.md b/docs/en/docs/20.03_LTS/docs/Container/shared-memory-channels.md
similarity index 99%
rename from content/en/docs/Container/shared-memory-channels.md
rename to docs/en/docs/20.03_LTS/docs/Container/shared-memory-channels.md
index b82de5bda7d032e6e7545a7ea4f9391ca77be228..f00335a8fe96cb4b9e08c181566800601a15d63a 100644
--- a/content/en/docs/Container/shared-memory-channels.md
+++ b/docs/en/docs/20.03_LTS/docs/Container/shared-memory-channels.md
@@ -52,7 +52,7 @@ dd: error writing '/testdir/test.file': No space left on device
 33554432 bytes (34 MB, 32 MiB) copied, 0.0766899 s, 438 MB/s
 ```
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >-   If  **--host-channel**  is used for size limit, the file size is constrained by the memory limit in the container. \(The OOM error may occur when the memory usage reaches the upper limit.\)  
 >-   If a user creates a shared file on the host, the file size is not constrained by the memory limit in the container.  
 >-   If you need to create a shared file in the container and the service is memory-intensive, you can add the value of  **--host-channel**  to the original value of the container memory limit, eliminating the impact.  
diff --git a/content/en/docs/Container/specifying-rootfs-to-create-a-container.md b/docs/en/docs/20.03_LTS/docs/Container/specifying-rootfs-to-create-a-container.md
similarity index 98%
rename from content/en/docs/Container/specifying-rootfs-to-create-a-container.md
rename to docs/en/docs/20.03_LTS/docs/Container/specifying-rootfs-to-create-a-container.md
index ada346f99c309b483c72ccc808132126159ca8e8..8b0763f4d276fbf56c952c00acc251abbf1160ac 100644
--- a/content/en/docs/Container/specifying-rootfs-to-create-a-container.md
+++ b/docs/en/docs/20.03_LTS/docs/Container/specifying-rootfs-to-create-a-container.md
@@ -44,6 +44,6 @@ If the local rootfs path is  **/root/myrootfs**, run the following command to st
 # isula run  -tid --system-container --external-rootfs /root/myrootfs none init
 ```
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >Rootfs is a user-defined file system. Prepare it by yourself. For example, a rootfs is generated after the TAR package of container images is decompressed.  
 
diff --git a/content/en/docs/Container/statistics.md b/docs/en/docs/20.03_LTS/docs/Container/statistics.md
similarity index 100%
rename from content/en/docs/Container/statistics.md
rename to docs/en/docs/20.03_LTS/docs/Container/statistics.md
diff --git a/content/en/docs/Container/supporting-oci-hooks.md b/docs/en/docs/20.03_LTS/docs/Container/supporting-oci-hooks.md
similarity index 100%
rename from content/en/docs/Container/supporting-oci-hooks.md
rename to docs/en/docs/20.03_LTS/docs/Container/supporting-oci-hooks.md
diff --git a/content/en/docs/Container/system-container.md b/docs/en/docs/20.03_LTS/docs/Container/system-container.md
similarity index 100%
rename from content/en/docs/Container/system-container.md
rename to docs/en/docs/20.03_LTS/docs/Container/system-container.md
diff --git a/content/en/docs/Container/uninstallation.md b/docs/en/docs/20.03_LTS/docs/Container/uninstallation.md
similarity index 100%
rename from content/en/docs/Container/uninstallation.md
rename to docs/en/docs/20.03_LTS/docs/Container/uninstallation.md
diff --git a/content/en/docs/Container/upgrade-methods.md b/docs/en/docs/20.03_LTS/docs/Container/upgrade-methods.md
similarity index 95%
rename from content/en/docs/Container/upgrade-methods.md
rename to docs/en/docs/20.03_LTS/docs/Container/upgrade-methods.md
index 31e8df2eeb06351021eb2036e056d338fe9f4cf4..5294263ed82402538f59fb9cfe43f950e9b367e8 100644
--- a/content/en/docs/Container/upgrade-methods.md
+++ b/docs/en/docs/20.03_LTS/docs/Container/upgrade-methods.md
@@ -8,7 +8,7 @@
 
 -   For an upgrade between major versions, for example, upgrading 1.x.x to 2.x.x, save the current configuration file  **/etc/isulad/daemon.json**, uninstall the existing iSulad software package, install the iSulad software package to be upgraded, and restore the configuration file.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >-   You can run the  **sudo rpm -qa |grep iSulad**  or  **isula version**  command to check the iSulad version.  
 >-   If you want to manually perform upgrade between patch versions of a major version, run the following command to download the RPM packages of iSulad and all its dependent libraries:  
 >    ```  
diff --git a/content/en/docs/Container/usage-guide.md b/docs/en/docs/20.03_LTS/docs/Container/usage-guide.md
similarity index 100%
rename from content/en/docs/Container/usage-guide.md
rename to docs/en/docs/20.03_LTS/docs/Container/usage-guide.md
diff --git a/content/en/docs/Container/using-systemd-to-start-a-container.md b/docs/en/docs/20.03_LTS/docs/Container/using-systemd-to-start-a-container.md
similarity index 100%
rename from content/en/docs/Container/using-systemd-to-start-a-container.md
rename to docs/en/docs/20.03_LTS/docs/Container/using-systemd-to-start-a-container.md
diff --git a/content/en/docs/Container/writable-namespace-kernel-parameters.md b/docs/en/docs/20.03_LTS/docs/Container/writable-namespace-kernel-parameters.md
similarity index 100%
rename from content/en/docs/Container/writable-namespace-kernel-parameters.md
rename to docs/en/docs/20.03_LTS/docs/Container/writable-namespace-kernel-parameters.md
diff --git a/content/en/docs/Installation/Installation.md b/docs/en/docs/20.03_LTS/docs/Installation/Installation.md
similarity index 100%
rename from content/en/docs/Installation/Installation.md
rename to docs/en/docs/20.03_LTS/docs/Installation/Installation.md
diff --git a/content/en/docs/Installation/faqs.md b/docs/en/docs/20.03_LTS/docs/Installation/faqs.md
similarity index 95%
rename from content/en/docs/Installation/faqs.md
rename to docs/en/docs/20.03_LTS/docs/Installation/faqs.md
index b6124125082eb59ce3098cdc78e8aa12f7dde748..8f99d3d603f60cc73c3365248d49980bb42331b0 100644
--- a/content/en/docs/Installation/faqs.md
+++ b/docs/en/docs/20.03_LTS/docs/Installation/faqs.md
@@ -41,7 +41,7 @@ The NetworkManager and network services are network service management tools. So
 
 -   If the NetworkManager service is used, run the  **nmcli**  command or modify the configuration file to configure the network \(such as the IP address and route\). Do not run the  **ip**,  **ifconfig**, or  **route**  command to configure the network.
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >When the NetworkManager service is enabled and you run commands such as  **ip**,  **ifconfig**, and  **route**  to configure the network, the configurations will be overwritten by NetworkManager.  
 
     To check whether NetworkManager is enabled, run the following command:
@@ -50,7 +50,7 @@ The NetworkManager and network services are network service management tools. So
     systemctl status NetworkManager
     ```
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >For details about the use of the  **nmcli**  command, see the execution result of the  **nmcli --help**  or  **man nmcli**  command.  
 
 -   If you want to run commands such as  **ip**,  **ifconfig**, and  **route**  commands to manage network information, run the following command to disable the NetworkManager service:
@@ -66,7 +66,7 @@ The NetworkManager and network services are network service management tools. So
 
 openEuler enters emergency mode after it is powered on.
 
-![](figures/en-us_image_0229291264.jpg)
+![](./figures/en-us_image_0229291264.jpg)
 
 ### Possible Causes
 
@@ -79,7 +79,7 @@ An unexpected system power-off, and low I/O performance of disks may also cause
 1.  Enter the password of the  **root**  account to log in to openEuler.
 2.  Check and restore files by using the file system check \(fsck\) tool, and restart openEuler.
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >The fsck tool checks and maintains inconsistent file systems. If the system is powered off or a disk is faulty, run the  **fsck**  command to check file systems. Run the  **fsck.ext3 -h**  and  **fsck.ext4 -h**  commands to view the usage method of the fsck tool.  
 
 
@@ -167,7 +167,7 @@ Check whether the installation source is abnormal. Use the new installation sour
 
 Run the  **systemctl status kdump**  command. The following information is displayed, indicating that no memory is reserved.
 
-![](figures/en-us_image_0229291280.png)
+![](./figures/en-us_image_0229291280.png)
 
 ### Possible Cause
 
@@ -187,7 +187,7 @@ For the scenario where the OS has been installed
 
     If the following information is displayed, the kdump status is  **active**, indicating that the kdump service is enabled. No further action is required.
 
-    ![](figures/en-us_image_0229291272.png)
+    ![](./figures/en-us_image_0229291272.png)
 
 
 ### Parameter Description
@@ -254,7 +254,7 @@ The following table describes the parameters of the memory reserved for the kdum
 If openEuler was installed on a logical volume consisting of multiple disks, an error message will be displayed as shown in  [Figure 1](#fig115949762617)  when you attempt to select one of the disks for reinstallation. 
 
 **Figure  1**  Error message  
-![](figures/error-message.png "error-message")
+![](./figures/error-message.png "error-message")
 
 ### Possible Cause
 
@@ -270,7 +270,7 @@ The logical volume formed by multiple disks is equivalent to a volume group. The
     vgs
     ```
 
-    ![](figures/en-us_image_0231657950.png)
+    ![](./figures/en-us_image_0231657950.png)
 
 2.  Run the following command to delete the volume group:
 
@@ -284,7 +284,7 @@ The logical volume formed by multiple disks is equivalent to a volume group. The
     systemctl restart anaconda
     ```
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >You can also press  **Ctrl**+**Alt**+**F6**  to return to the GUI and click  **Refresh**  in the lower right corner to refresh the storage configuration.  
 
 
@@ -295,7 +295,7 @@ The logical volume formed by multiple disks is equivalent to a volume group. The
 During the installation of openEuler on an x86 PM in UEFI mode, the system stays at the "No bootable device" page and the installation cannot continue because  **secure boot**  is set to  **enabled**  \(by default, it is set to  **disabled**\), as shown in  [Figure 2](#fig115949762617).
 
 **Figure  2**  Dialog box showing "No bootable device"   
-![](figures/dialog-box-showing-no-bootable-device.png "dialog-box-showing-no-bootable-device")
+![](./figures/dialog-box-showing-no-bootable-device.png "dialog-box-showing-no-bootable-device")
 
 ### Possible Cause
 
@@ -307,16 +307,16 @@ Access the BIOS, set  **secure boot**  to  **disabled**, and reinstall the openE
 
 1.  During the system startup, press  **F11**  and enter the password  **Admin@9000**  to access the BIOS.
 
-    ![](figures/bios.png)
+    ![](./figures/bios.png)
 
 2.  Choose  **Administer Secure Boot**.
 
-    ![](figures/security.png)
+    ![](./figures/security.png)
 
 3.  Set  **Enforce Secure Boot**  to  **Disabled**.
 
-    ![](figures/enforce-secure-boot.png)
+    ![](./figures/enforce-secure-boot.png)
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >After  **Enforce Secure Boot**  is set to  **Disabled**, save the settings, and exit. Then, reinstall the system.  
 
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/adding-the-inst-noverifyssl-parameter.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/adding-the-inst-noverifyssl-parameter.png
new file mode 100644
index 0000000000000000000000000000000000000000..dc92fedd71a5331af870e449f843ecd0eefc9278
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/adding-the-inst-noverifyssl-parameter.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/advanced-user-configuration.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/advanced-user-configuration.png
new file mode 100644
index 0000000000000000000000000000000000000000..3a27f8b5371323cf27dae8dd7e8549ff1e1f8c4b
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/advanced-user-configuration.png differ
diff --git a/content/en/docs/Installation/figures/bios.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/bios.png
similarity index 100%
rename from content/en/docs/Installation/figures/bios.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/bios.png
diff --git a/content/en/docs/Installation/figures/completing-the-automatic-installation.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/completing-the-automatic-installation.png
similarity index 100%
rename from content/en/docs/Installation/figures/completing-the-automatic-installation.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/completing-the-automatic-installation.png
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/completing-the-configuration.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/completing-the-configuration.png
new file mode 100644
index 0000000000000000000000000000000000000000..f37cb873d920e8969d507cc5bce85d265e9321e8
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/completing-the-configuration.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/completing-the-installation.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/completing-the-installation.png
new file mode 100644
index 0000000000000000000000000000000000000000..4f339374e1f2ce5d912625f2fc6c59c24a4a9dcc
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/completing-the-installation.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/creating-a-user.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/creating-a-user.png
new file mode 100644
index 0000000000000000000000000000000000000000..e62fa5b13359d2ffe926217dacd183a70a609cc5
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/creating-a-user.png differ
diff --git a/content/en/docs/Installation/figures/dialog-box-showing-no-bootable-device.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/dialog-box-showing-no-bootable-device.png
similarity index 100%
rename from content/en/docs/Installation/figures/dialog-box-showing-no-bootable-device.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/dialog-box-showing-no-bootable-device.png
diff --git a/content/en/docs/Installation/figures/drive-icon.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/drive-icon.png
similarity index 100%
rename from content/en/docs/Installation/figures/drive-icon.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/drive-icon.png
diff --git a/content/en/docs/Installation/figures/en-us_image_0229291229.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291229.png
similarity index 100%
rename from content/en/docs/Installation/figures/en-us_image_0229291229.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291229.png
diff --git a/content/en/docs/Installation/figures/en-us_image_0229291236.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291236.png
similarity index 100%
rename from content/en/docs/Installation/figures/en-us_image_0229291236.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291236.png
diff --git a/content/en/docs/Installation/figures/en-us_image_0229291243.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291243.png
similarity index 100%
rename from content/en/docs/Installation/figures/en-us_image_0229291243.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291243.png
diff --git a/content/en/docs/Installation/figures/en-us_image_0229291247.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291247.png
similarity index 100%
rename from content/en/docs/Installation/figures/en-us_image_0229291247.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291247.png
diff --git a/content/en/docs/Installation/figures/en-us_image_0229291264.jpg b/docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291264.jpg
similarity index 100%
rename from content/en/docs/Installation/figures/en-us_image_0229291264.jpg
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291264.jpg
diff --git a/content/en/docs/Installation/figures/en-us_image_0229291270.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291270.png
similarity index 100%
rename from content/en/docs/Installation/figures/en-us_image_0229291270.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291270.png
diff --git a/content/en/docs/Installation/figures/en-us_image_0229291272.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291272.png
similarity index 100%
rename from content/en/docs/Installation/figures/en-us_image_0229291272.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291272.png
diff --git a/content/en/docs/Installation/figures/en-us_image_0229291280.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291280.png
similarity index 100%
rename from content/en/docs/Installation/figures/en-us_image_0229291280.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291280.png
diff --git a/content/en/docs/Installation/figures/en-us_image_0229291286.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291286.png
similarity index 100%
rename from content/en/docs/Installation/figures/en-us_image_0229291286.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229291286.png
diff --git a/content/en/docs/Installation/figures/en-us_image_0229420473.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229420473.png
similarity index 100%
rename from content/en/docs/Installation/figures/en-us_image_0229420473.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0229420473.png
diff --git a/content/en/docs/Installation/figures/en-us_image_0231657950.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0231657950.png
similarity index 100%
rename from content/en/docs/Installation/figures/en-us_image_0231657950.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/en-us_image_0231657950.png
diff --git a/content/en/docs/Installation/figures/enforce-secure-boot.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/enforce-secure-boot.png
similarity index 100%
rename from content/en/docs/Installation/figures/enforce-secure-boot.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/enforce-secure-boot.png
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/error-message.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/error-message.png
new file mode 100644
index 0000000000000000000000000000000000000000..c5802a2b7a750eed8429ec06c7e4919a3d161a9e
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/error-message.png differ
diff --git a/content/en/docs/Installation/figures/image-dialog-box.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/image-dialog-box.png
similarity index 100%
rename from content/en/docs/Installation/figures/image-dialog-box.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/image-dialog-box.png
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/installation-process.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/installation-process.png
new file mode 100644
index 0000000000000000000000000000000000000000..986c9b5c25887ed6cec0dc8d5ad1269dc3ff3ddb
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/installation-process.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/installation-summary.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/installation-summary.png
new file mode 100644
index 0000000000000000000000000000000000000000..403b9a53202f2f62e97676aefb92924c263e1b14
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/installation-summary.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/installation-wizard.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/installation-wizard.png
new file mode 100644
index 0000000000000000000000000000000000000000..69c5254413574903fc55c5eafb935a83837549e0
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/installation-wizard.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/manual-partitioning-page.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/manual-partitioning-page.png
new file mode 100644
index 0000000000000000000000000000000000000000..55d3806c7157d92438b22c6f9dc438d88374395e
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/manual-partitioning-page.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/password-of-the-root-account.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/password-of-the-root-account.png
new file mode 100644
index 0000000000000000000000000000000000000000..1b62043d52df903e9cd5221002d89b6d2e9cfefa
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/password-of-the-root-account.png differ
diff --git a/content/en/docs/Installation/figures/restart-icon.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/restart-icon.png
similarity index 100%
rename from content/en/docs/Installation/figures/restart-icon.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/restart-icon.png
diff --git a/content/en/docs/Installation/figures/security.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/security.png
similarity index 100%
rename from content/en/docs/Installation/figures/security.png
rename to docs/en/docs/20.03_LTS/docs/Installation/figures/security.png
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/selecting-a-language.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/selecting-a-language.png
new file mode 100644
index 0000000000000000000000000000000000000000..7230029ddd5c0fc0cbe5b9f220c5e380aed9927e
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/selecting-a-language.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/selecting-installation-software.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/selecting-installation-software.png
new file mode 100644
index 0000000000000000000000000000000000000000..72561ef0c81ff8041105bc27e45ddf1c57b7e0a1
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/selecting-installation-software.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/semi-automatic-installation.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/semi-automatic-installation.png
new file mode 100644
index 0000000000000000000000000000000000000000..82218558de7ffacb4835087c90c0206b52f89198
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/semi-automatic-installation.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-a-system-language.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-a-system-language.png
new file mode 100644
index 0000000000000000000000000000000000000000..7ffc671d569299622ed0c7b750df239b9ea0237e
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-a-system-language.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-date-and-time.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-date-and-time.png
new file mode 100644
index 0000000000000000000000000000000000000000..badc16d9057f523038b2cd7c8e3cba3d079388e0
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-date-and-time.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-the-installation-destination.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-the-installation-destination.png
new file mode 100644
index 0000000000000000000000000000000000000000..49a06b3f62da737a366e5b0da3b25ca66726bae2
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-the-installation-destination.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-the-installation-source.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-the-installation-source.png
new file mode 100644
index 0000000000000000000000000000000000000000..f4fd3be75ad97683d399b28a793d70ffd824126a
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-the-installation-source.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-the-keyboard-layout.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-the-keyboard-layout.png
new file mode 100644
index 0000000000000000000000000000000000000000..073140233a81bc565c5320c75544dbbfdd14af6c
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-the-keyboard-layout.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-the-network-and-host-name.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-the-network-and-host-name.png
new file mode 100644
index 0000000000000000000000000000000000000000..c817a3842537be83d546a70fa034022816653d6b
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/setting-the-network-and-host-name.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Installation/figures/starting-installation.png b/docs/en/docs/20.03_LTS/docs/Installation/figures/starting-installation.png
new file mode 100644
index 0000000000000000000000000000000000000000..4bd779430c0dd891099dffbd7b65298eae0dea58
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Installation/figures/starting-installation.png differ
diff --git a/content/en/docs/Installation/installation-guideline.md b/docs/en/docs/20.03_LTS/docs/Installation/installation-guideline.md
similarity index 85%
rename from content/en/docs/Installation/installation-guideline.md
rename to docs/en/docs/20.03_LTS/docs/Installation/installation-guideline.md
index ba60382a03ef42ae52b1d368b26d8f9d0e23fd9c..ed94820b26dfa2984daedee8212a82172e45d84b 100644
--- a/content/en/docs/Installation/installation-guideline.md
+++ b/docs/en/docs/20.03_LTS/docs/Installation/installation-guideline.md
@@ -33,37 +33,37 @@ This section describes how to install openEuler using a CD-ROM. The installation
 
 Load the ISO image of openEuler from the CD/DVD-ROM drive of the server and restart the server. The procedure is as follows:
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >Before the installation, ensure that the server boots from the CD/DVD-ROM drive preferentially. The following steps describe how to install the openEuler using the virtual CD/DVD-ROM drive on the baseboard management controller \(BMC\). Installing the openEuler from a physical drive is simple. After the installation starts, the procedure for the physical drive is the same as that of the virtual drive.  
 
 1.  On the toolbar, click the icon shown in the following figure.
 
     **Figure  1**  Drive icon  
-    ![](figures/drive-icon.png "drive-icon")
+    ![](./figures/drive-icon.png "drive-icon")
 
     An image dialog box is displayed, as shown in the following figure.
 
     **Figure  2**  Image dialog box  
-    ![](figures/image-dialog-box.png "image-dialog-box")
+    ![](./figures/image-dialog-box.png "image-dialog-box")
 
 2.  Select  **Image File**  and then click  **Browse**. The  **Open**  dialog box is displayed.
 3.  Select the image file and click  **Open**. In the image dialog box, click  **Connect**. If  **Connect**  changes to  **Disconnect**, the virtual CD/DVD-ROM drive is connected to the server.
 4.  On the toolbar, click the restart icon shown in the following figure to restart the device.
 
     **Figure  3**  Restart icon  
-    ![](figures/restart-icon.png "restart-icon")
+    ![](./figures/restart-icon.png "restart-icon")
 
 
 ### Installation Wizard
 
 A boot menu is displayed after the system is booted using the boot medium. In addition to options for starting the installation program, some other options are available on the boot menu. During system installation, the  **Test this media & install openEuler 20.03 LTS**  mode is used by default. Press the arrow keys on the keyboard to change the selection, and press  **Enter**  when the desired option is highlighted.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >-   If you do not perform any operations within 1 minute, the system automatically selects the default option  **Test this media & install openEuler 20.03 LTS**  and enters the installation page.  
->-   During PM installation, if you cannot use the arrow keys to select boot options and the system does not respond after you press  **Enter**, click  ![](figures/en-us_image_0229420473.png)  on the BMC page and configure  **Key & Mouse Reset**.  
+>-   During PM installation, if you cannot use the arrow keys to select boot options and the system does not respond after you press  **Enter**, click  ![](./figures/en-us_image_0229420473.png)  on the BMC page and configure  **Key & Mouse Reset**.  
 
 **Figure  4**  Installation Wizard  
-![](figures/installation-wizard.png "installation-wizard")
+![](./figures/installation-wizard.png "installation-wizard")
 
 Installation wizard options are described as follows:
 
@@ -95,7 +95,7 @@ Perform graphical installation operations using a keyboard.
 After the installation starts, the system will prompt the language that is used during the configuration installation process. English is configured by default, as shown in  [Figure 5](#en-us_topic_0186390093_en-us_topic_0122145864_fig144630179151). Configure another language as required.
 
 **Figure  5**  Selecting a language  
-![](figures/selecting-a-language.png "selecting-a-language")
+![](./figures/selecting-a-language.png "selecting-a-language")
 
 After configurations, click  **Continue**. The main installation configuration page is displayed.
 
@@ -110,7 +110,7 @@ Some configuration items are matched with safety symbols. A safety symbol will d
 If you want to exit the installation, click  **Exit**. The message "Are you sure you want to exit the installation program?" is displayed. Click  **Yes**  in the dialog box to go back to the installation wizard page.
 
 **Figure  6**  Installation summary  
-![](figures/installation-summary.png "installation-summary")
+![](./figures/installation-summary.png "installation-summary")
 
 ## Setting the Keyboard Layout
 
@@ -120,7 +120,7 @@ On the  **INSTALLATION SUMMARY**  page, click  **KEYBOARD**. You can add or dele
 -   To test the keyboard layout: On the left white box, click to select the keyboard layout, click the inside of the right text box, and enter the text to ensure that the keyboard layout can work properly.
 
 **Figure  7**  Setting the keyboard layout  
-![](figures/setting-the-keyboard-layout.png "setting-the-keyboard-layout")
+![](./figures/setting-the-keyboard-layout.png "setting-the-keyboard-layout")
 
 After the setting is complete, click  **Done**  in the upper left corner to go back to the  **INSTALLATION SUMMARY**  page.
 
@@ -128,12 +128,12 @@ After the setting is complete, click  **Done**  in the upper left corner to go b
 
 On the  **INSTALLATION SUMMARY**  page, click  **LANGUAGE SUPPORT**  to set the system language, as shown in  [Figure 8](#en-us_topic_0186390098_en-us_topic_0122145772_fig187301927172619). Set another language as required, such as Chinese.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >-   If you select Chinese, the system does not display Chinese characters after you log in to the system using VNC, because VNC does not support Chinese characters. If you log in to the system in SSH mode, Chinese characters will be displayed.  
 >-   If you select English, there will be no impact.  
 
 **Figure  8**  Setting a system language  
-![](figures/setting-a-system-language.png "setting-a-system-language")
+![](./figures/setting-a-system-language.png "setting-a-system-language")
 
 After the setting is complete, click  **Done**  in the upper left corner to go back to the  **INSTALLATION SUMMARY**  page.
 
@@ -145,12 +145,12 @@ When setting the time zone, you can click a specific city on the map with the mo
 
 If your city is not displayed on the map or in the drop-down list, select the nearest city in the same time zone.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >-   Before manually setting the time zone, disable the network time synchronization function in the upper right corner.  
 >-   If you want to use the network time, ensure that the network can connect to the remote NTP server. For details about how to set the network, see [Setting the Network and Host Name](#setting-the-network-and-host-name).  
 
 **Figure  9**  Setting date and time  
-![](figures/setting-date-and-time.png "setting-date-and-time")
+![](./figures/setting-date-and-time.png "setting-date-and-time")
 
 After the setting is complete, click  **Done**  in the upper left corner to go back to the  **INSTALLATION SUMMARY**  page.
 
@@ -161,17 +161,17 @@ On the  **INSTALLATION SUMMARY**  page, click  **INSTALLATION SOURCE**  to locat
 If you use a CD/DVD-ROM for installation, the installation program automatically detects and displays the installation source information. You can use the default settings.  [Figure 10](#en-us_topic_0186390100_en-us_topic_0144427079_fig93633295132)  shows an example.
 
 **Figure  10**  Setting the installation source  
-![](figures/setting-the-installation-source.png "setting-the-installation-source")
+![](./figures/setting-the-installation-source.png "setting-the-installation-source")
 
 When you use the network for installation, if the HTTPS server uses a private certificate, press  **e**  on the installation wizard page to go to the parameter editing page and add the  **inst.noverifyssl**  parameter, as shown in  [Figure 11](#fig113517811415).
 
 **Figure  11**  Adding the  **inst.noverifyssl**  parameter  
-![](figures/adding-the-inst-noverifyssl-parameter.png "adding-the-inst-noverifyssl-parameter")
+![](./figures/adding-the-inst-noverifyssl-parameter.png "adding-the-inst-noverifyssl-parameter")
 
 After the setting is complete, click  **Done**  in the upper left corner to go back to the  **INSTALLATION SUMMARY**  page.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
->During the installation, if you have any questions about configuring the installation source, see [An Exception Occurs During the Selection of the Installation Source](faqs.html#an-exception-occurs-during-the-selection-of-the-installation-source).  
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
+>During the installation, if you have any questions about configuring the installation source, see [An Exception Occurs During the Selection of the Installation Source](./faqs.html#an-exception-occurs-during-the-selection-of-the-installation-source).  
 
 ## Selecting Installation Software
 
@@ -180,9 +180,9 @@ On the  **INSTALLATION SUMMARY**  page, click  **SOFTWARE SELECTION**  to specif
 Based on the actual requirements, select  **Minimal Install**  on the left box and select an add-on in the  **Add-Ons for Selected Environment**  area on the right, as shown in  [Figure 12](#en-us_topic_0186390261_en-us_topic_0122145865_fig03031519101414).
 
 **Figure  12**  Selecting installation software  
-![](figures/selecting-installation-software.png "selecting-installation-software")
+![](./figures/selecting-installation-software.png "selecting-installation-software")
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >-   In  **Minimal Install**  mode, not all packages in the installation source will be installed. If the required package is not installed, you can mount the installation source to the local PC and configure a repo source, and use DNF to install the package.  
 >-   If you select  **Virtual Host**, the virtualization components QEMU, libvirt, and edk2 are installed by default. You can select whether to install the OVS component in the add-on area.  
 
@@ -192,19 +192,19 @@ After the setting is complete, click  **Done**  in the upper left corner to go b
 
 On the  **INSTALLATION SUMMARY**  page, click  **INSTALLATION DESTINATION**  to select the OS installation disk and partition.
 
-You can view available local storage devices in  [Figure 13](#fig1195417125015). 
+You can view available local storage devices in  [Figure 13](#fig1195417125015). You can also add an attached device or a network disk specified by clicking  **Add a disk**.
 
->![](public_sys-resources/icon-notice.gif) **NOTICE:**   
+>![](./public_sys-resources/icon-notice.gif) **NOTICE:**   
 >When selecting the device to be installed, you are advised not to use the NVMe SSD storage medium as the OS installation disk.  
 
 **Figure  13**  Setting the installation destination  
-![](figures/setting-the-installation-destination.png "setting-the-installation-destination")
+![](./figures/setting-the-installation-destination.png "setting-the-installation-destination")
 
 ### Storage Configuration
 
 On the  **INSTALLATION DESTINATION**  page, configure storage for system partition. You can either manually configure partitions or select  **Automatic**  to automatically configure partitioning.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >-   During partitioning, to ensure system security and performance, you are advised to divide the device into the following partitions:  **/boot**,  **/var**,  **/var/log**,  **/var/log/audit**,  **/home**, and  **/tmp**.  
 >-   If the system is configured with the swap partition, the swap partition is used when the physical memory of the system is insufficient. Although the swap partition can be used to expand the physical memory, if the swap partition is used due to insufficient memory, the system response slows and the system performance deteriorates. Therefore, you are not advised to configure the swap partition in the system with sufficient physical memory or the performance sensitive system.  
 >-   If you need to split a logical volume group, select  **Custom**  to manually partition the logical volume group. On the  **MANUAL PARTITIONING**  page, click  **Modify**  in the  **Volume Group**  area to reconfigure the logical volume group.  
@@ -218,14 +218,14 @@ Select  **Automatic**  if the software is installed in a new storage device or t
 If you need to manually partition the disk, click  **Customize**  and click  **Done**  in the upper left corner. The following page is displayed.
 
 **Figure  14**  MANUAL PARTITIONING page  
-![](figures/manual-partitioning-page.png "manual-partitioning-page")
+![](./figures/manual-partitioning-page.png "manual-partitioning-page")
 
 On the  **MANUAL PARTITIONING**  page, you can partition the disk in either of the following ways:
 
 -   Automatic creation: Click  **Click here to create them automatically**. The system automatically assigns four mount points according to the available storage space:  **/boot**,  **/**,  **/boot/efi**, and  **swap**.
--   Manual creation: Click  ![](figures/en-us_image_0229291243.png)  to add a mount point. It is recommended that the expected capacity of each mount point not exceed the available space.
+-   Manual creation: Click  ![](./figures/en-us_image_0229291243.png)  to add a mount point. It is recommended that the expected capacity of each mount point not exceed the available space.
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >If the expected capacity of the mount point exceeds the available space, the system allocates the remaining available space to the mount point.  
 
 
@@ -240,7 +240,7 @@ The installation program automatically detects a local access interface. The det
 In the lower left box, enter the host name. The host name can be the fully quantified domain name \(FQDN\) in the format of hostname.domainname or the brief host name in the format of hostname.
 
 **Figure  15**  Setting the network and host name  
-![](figures/setting-the-network-and-host-name.png "setting-the-network-and-host-name")
+![](./figures/setting-the-network-and-host-name.png "setting-the-network-and-host-name")
 
 After the setting is complete, click  **Done**  in the upper left corner to go back to the  **INSTALLATION SUMMARY**  page.
 
@@ -249,14 +249,14 @@ After the setting is complete, click  **Done**  in the upper left corner to go b
 On the installation page, after all the mandatory items are configured, the safety symbols will disappear. Then, you can click  **Begin Installation**  to install the system.
 
 **Figure  16**  Starting installation  
-![](figures/starting-installation.png "starting-installation")
+![](./figures/starting-installation.png "starting-installation")
 
 ## Configurations During Installation
 
 After the installation starts, the overall installation progress and the progress of writing the software package to the system are displayed.
 
 **Figure  17**  Installation process  
-![](figures/installation-process.png "installation-process")
+![](./figures/installation-process.png "installation-process")
 
 During the process of installing software packages, you need to configure the root password and create users.
 
@@ -268,19 +268,39 @@ The password of the  **root**  user or the password of the new user must meet th
 2.  A password must contain at least three of the following types: uppercase letters, lowercase letters, digits, and special characters.
 3.  A password must be different from the account name.
 4.  A password cannot contain words in the dictionary.
+    -   Querying a dictionary
+
+        In the installed openEuler environment, you can run the following command to export the dictionary library file  **dictionary.txt**, and then check whether the password is in the dictionary.
+
+        ```
+        cracklib-unpacker /usr/share/cracklib/pw_dict > dictionary.txt
+        ```
+
+    -   Modifying a dictionary
+        1.  Modify the exported dictionary library file, and then run the following command to update the dictionary library:
+
+            ```
+            # create-cracklib-dict dictionary.txt
+            ```
+
+        2.  Run the following command to add another dictionary file  **custom.txt**  to the original dictionary library.
+
+            ```
+            # create-cracklib-dict dictionary.txt custom.txt
+            ```
+
+
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
-    > In the installed openEuler environment, you can run the `cracklib-unpacker /usr/share/cracklib/pw_dict > dictionary.txt` command to export the dictionary library file  **dictionary.txt**, and then check whether the password is in the dictionary.
 
 ### Setting the Root User Password
 
 Click  **Root Password**. In the displayed dialog box, as shown in  [Figure 18](#en-us_topic_0186390266_en-us_topic_0122145909_fig1323165793018), enter a password and re-enter to confirm.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >The root password is required to be configured at the same time of installing software packages. Otherwise, the installation will fail. A  **root**  account is used for performing critical system administration tasks. It is not recommended to use this account for daily work or system access.  
 
 **Figure  18**  Password of the  **root**  account  
-![](figures/password-of-the-root-account.png "password-of-the-root-account")
+![](./figures/password-of-the-root-account.png "password-of-the-root-account")
 
 After configuration, click  **Done**  in the left-upper corner to switch back to the installation process page.
 
@@ -289,23 +309,23 @@ After configuration, click  **Done**  in the left-upper corner to switch back to
 Click  **User Creation**.  [Figure 19](#en-us_topic_0186390266_en-us_topic_0122145909_fig1237715313319)  shows the page for creating a user. Enter a username and set a password. By clicking  **Advanced**, you can also configure a home directory and a user group, as shown in  [Figure 20](#en-us_topic_0186390266_en-us_topic_0122145909_fig128716531312).
 
 **Figure  19**  Creating a user  
-![](figures/creating-a-user.png "creating-a-user")
+![](./figures/creating-a-user.png "creating-a-user")
 
 **Figure  20**  Advanced user configuration  
-![](figures/advanced-user-configuration.png "advanced-user-configuration")
+![](./figures/advanced-user-configuration.png "advanced-user-configuration")
 
 After configuration, click  **Done**  in the left-upper corner to switch back to the installation process page.
 
 Click  **Finish**. The configuration of openEuler is complete.
 
-![](figures/completing-the-configuration.png)
+![](./figures/completing-the-configuration.png)
 
 ## Completing the Installation
 
 openEuler has been installed, as shown in  [Figure 21](#en-us_topic_0186390267_en-us_topic_0122145917_fig1429512116338). Click  **Reboot**  to restart the system.
 
 **Figure  21**  Completing the installation  
-![](figures/completing-the-installation.png "completing-the-installation")
+![](./figures/completing-the-installation.png "completing-the-installation")
 
 -   If the physical DVD-ROM is used to install the OS and the DVD-ROM drive is not automatically ejected during the restart, manually remove the DVD-ROM. Then, the openEuler CLI login page is displayed.
 -   If the virtual DVD-ROM drive is used to install the OS, change the server boot option to  **Hard Disk**  and restart the server. Then, the openEuler CLI login page is displayed.
diff --git a/content/en/docs/Installation/installation-mode.md b/docs/en/docs/20.03_LTS/docs/Installation/installation-mode.md
similarity index 88%
rename from content/en/docs/Installation/installation-mode.md
rename to docs/en/docs/20.03_LTS/docs/Installation/installation-mode.md
index b0920a914013fed75d526eabc37a3158bc9d5451..0d7ada2a90d93d366bffed25908304dcd53ea7cd 100644
--- a/content/en/docs/Installation/installation-mode.md
+++ b/docs/en/docs/20.03_LTS/docs/Installation/installation-mode.md
@@ -1,7 +1,7 @@
 # Installation Mode
 
->![](public_sys-resources/icon-notice.gif) **NOTICE:**   
->-   Only TaiShan 200 and FusionServer Pro servers are supported. For details about the supported server models, see [Hardware Compatibility](installation-preparations.html#hardware-compatibility). Only a virtualization platform created by the virtualization components \(openEuler as the host OS and QEMU and KVM provided in the release package\) of openEuler and the x86 virtualization platform of Huawei public cloud are supported.  
+>![](./public_sys-resources/icon-notice.gif) **NOTICE:**   
+>-   Only TaiShan 200 and FusionServer Pro servers are supported. For details about the supported server models, see [Hardware Compatibility](./installation-preparations.html#hardware-compatibility). Only a virtualization platform created by the virtualization components \(openEuler as the host OS and QEMU and KVM provided in the release package\) of openEuler and the x86 virtualization platform of Huawei public cloud are supported.  
 >-   Currently, only installation modes such as CD-ROM, USB flash drive, network, QCOW2 image, and private image are supported. In addition, only the x86 virtualization platform of Huawei public cloud supports the private image installation mode. 
 
 
@@ -35,7 +35,7 @@ If you have obtained a CD/DVD-ROM, install the OS using the CD/DVD-ROM. If you h
 
 Perform the following operations to start the installation:
 
->![](C:/Users/Administrator/Downloads/openDocs/docs/content/en/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >Set the system to preferentially boot from the CD/DVD-ROM drive. Take the BIOS as an example. You need to move the  **CD/DVD-ROM Drive**  option under  **Boot Type Order**  to the top.  
 
 1.  Disconnect all drives that are not required, such as USB drives.
@@ -59,7 +59,7 @@ Pay attention to the capacity of the USB flash drive. The USB flash drive must h
     [ 170.171135] sd 5:0:0:0: [sdb] Attached SCSI removable disk
     ```
 
-    >![](C:/Users/Administrator/Downloads/openDocs/docs/content/en/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >Take the  **sdb**  USB flash drive as an example.  
 
 2.  Switch to user  **root**. When running the  **su**  command, you need to enter the password.
@@ -113,7 +113,7 @@ Pay attention to the capacity of the USB flash drive. The USB flash drive must h
 
 Perform the following operations to start the installation:
 
->![](C:/Users/Administrator/Downloads/openDocs/docs/content/en/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >Set the system to preferentially boot from the USB flash drive. Take the BIOS as an example. You need to move the  **USB**  option under  **Boot Type Order**  to the top.  
 
 1.  Disconnect all drives that are not required.
@@ -131,8 +131,8 @@ If the target hardware is installed with a PXE-enabled NIC, we can configure it
 
 For installation through the network using PXE, the client uses a PXE-enabled NIC to send a broadcast request for DHCP information and IP address to the network. The DHCP server provides the client with an IP address and other network information, such as the IP address or host name of the DNS and FTP server \(which provides the files required for starting the installation program\), and the location of the files on the server.
 
->![](C:/Users/Administrator/Downloads/openDocs/docs/content/en/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:**   
->The TFTP, DHCP, and HTTP server configurations are not described here. For details, see  [Full-automatic Installation Guide](using-kickstart-for-automatic-installation.html#full-automatic-installation-guide).  
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
+>The TFTP, DHCP, and HTTP server configurations are not described here. For details, see  [Full-automatic Installation Guide](./using-kickstart-for-automatic-installation.html#full-automatic-installation-guide).  
 
 ## Installation Through a QCOW2 Image
 
@@ -178,7 +178,7 @@ Perform the following operations to start the installation:
 5.  Create a VM.
 6.  Start the VM.
 
-For details, see the  [*openEuler 20.03 LTS Virtualization User Guide*](../Virtualization/virtualization.html).
+For details, see the  [*openEuler 20.03 LTS Virtualization User Guide*](./../Virtualization/virtualization.html).
 
 ## Installation Through a Private Image
 
diff --git a/content/en/docs/Installation/installation-preparations.md b/docs/en/docs/20.03_LTS/docs/Installation/installation-preparations.md
similarity index 97%
rename from content/en/docs/Installation/installation-preparations.md
rename to docs/en/docs/20.03_LTS/docs/Installation/installation-preparations.md
index d2c7c150e474250a861a0d9f47c4869ecb53600d..fcfccb21443114d1929794b56fd62cb9c61766c2 100644
--- a/content/en/docs/Installation/installation-preparations.md
+++ b/docs/en/docs/20.03_LTS/docs/Installation/installation-preparations.md
@@ -47,7 +47,7 @@ Perform the following operations to obtain the openEuler release package:
 
 ## Release Package Integrity Check
 
->![](C:/Users/Administrator/Downloads/openDocs/docs/content/en/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >This section describes how to verify the integrity of the release package in the AArch64 architecture. The procedure for verifying the integrity of the release package in the x86\_64 architecture is the same.  
 
 ### Introduction
@@ -71,13 +71,13 @@ To verify the file integrity, perform the following operations:
 1.  Obtain the verification value in the verification file. Run the following command:
 
     ```
-    #cat openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum 
+    $ cat openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum 
     ```
 
 2.  Calculate the SHA256 verification value of the file. Run the following command:
 
     ```
-    #sha256sum openEuler-20.03-LTS-aarch64-dvd.iso
+    $ sha256sum openEuler-20.03-LTS-aarch64-dvd.iso
     ```
 
     After the command is run, the verification value is displayed.
@@ -94,7 +94,7 @@ To install the openEuler OS on a PM, the PM must meet the following hardware com
 
 You need to take hardware compatibility into account during openEuler installation.  [Table 1](#table14948632047)  describes the types of supported servers.
 
->![](C:/Users/Administrator/Downloads/openDocs/docs/content/en/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >
 >-   TaiShan 200 servers are backed by Huawei Kunpeng 920 processors.  
 >-   Currently, only Huawei TaiShan and FusionServer Pro servers are supported. More servers from other vendors will be supported in the future.  
diff --git a/content/en/docs/Installation/public_sys-resources/icon-caution.gif b/docs/en/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-caution.gif
similarity index 100%
rename from content/en/docs/Installation/public_sys-resources/icon-caution.gif
rename to docs/en/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-caution.gif
diff --git a/content/en/docs/Installation/public_sys-resources/icon-danger.gif b/docs/en/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-danger.gif
similarity index 100%
rename from content/en/docs/Installation/public_sys-resources/icon-danger.gif
rename to docs/en/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-danger.gif
diff --git a/content/en/docs/Installation/public_sys-resources/icon-note.gif b/docs/en/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-note.gif
similarity index 100%
rename from content/en/docs/Installation/public_sys-resources/icon-note.gif
rename to docs/en/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-note.gif
diff --git a/content/en/docs/Installation/public_sys-resources/icon-notice.gif b/docs/en/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-notice.gif
similarity index 100%
rename from content/en/docs/Installation/public_sys-resources/icon-notice.gif
rename to docs/en/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-notice.gif
diff --git a/content/en/docs/Installation/public_sys-resources/icon-tip.gif b/docs/en/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-tip.gif
similarity index 100%
rename from content/en/docs/Installation/public_sys-resources/icon-tip.gif
rename to docs/en/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-tip.gif
diff --git a/content/en/docs/Installation/public_sys-resources/icon-warning.gif b/docs/en/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-warning.gif
similarity index 100%
rename from content/en/docs/Installation/public_sys-resources/icon-warning.gif
rename to docs/en/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-warning.gif
diff --git a/content/en/docs/Installation/using-kickstart-for-automatic-installation.md b/docs/en/docs/20.03_LTS/docs/Installation/using-kickstart-for-automatic-installation.md
similarity index 94%
rename from content/en/docs/Installation/using-kickstart-for-automatic-installation.md
rename to docs/en/docs/20.03_LTS/docs/Installation/using-kickstart-for-automatic-installation.md
index e461976b19b6b557ac6d2d3af4d082a70e1d3aff..34d3c1816a2063a70fd0962f87148383f3f93a09 100644
--- a/content/en/docs/Installation/using-kickstart-for-automatic-installation.md
+++ b/docs/en/docs/20.03_LTS/docs/Installation/using-kickstart-for-automatic-installation.md
@@ -88,7 +88,7 @@ To use kickstart to perform semi-automatic installation of openEuler, perform th
 
 **Environment Preparation**
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >Before the installation, ensure that the firewall of the HTTP server is disabled. Run the following command to disable the firewall:  
 >```  
 >iptables -F  
@@ -106,7 +106,7 @@ To use kickstart to perform semi-automatic installation of openEuler, perform th
 
     ```
     # mkdir /var/www/html/ks
-    #vim /var/www/html/ks/openEuler-ks.cfg ===>The file can be obtained by modifying the anaconda-ks.cfg file automatically generated from openEuler.
+    #vim /var/www/html/ks/openEuler-ks.cfg ===>The file can be obtained by modifying the anaconda-ks.cfg file automatically generated from openEuler, or can be created using the system-config-kickstart tool.
     ====================================
     ***Modify the following information as required.***
     #version=DEVEL
@@ -156,7 +156,7 @@ To use kickstart to perform semi-automatic installation of openEuler, perform th
     =====================================
     ```
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >The method of generating the password ciphertext is as follows:  
     >\# python3  
     >Python 3.7.0 \(default, Apr  1 2019, 00:00:00\)  
@@ -175,10 +175,10 @@ To use kickstart to perform semi-automatic installation of openEuler, perform th
 **Installing the System**
 
 1.  The installation selection dialog box is displayed. 
-    1.  On the installation wizard page in [Starting the Installation](installation-guideline.html#starting-the-installation), select  **Install openEuler 20.03 LTS**  and press  **e**.
+    1.  On the installation wizard page in [Starting the Installation](./installation-guideline.html#starting-the-installation), select  **Install openEuler 20.03 LTS**  and press  **e**.
     2.  Add  **inst.ks=http://server ip/ks/openEuler-ks.cfg**  to the startup parameters.
 
-        ![](figures/semi-automatic-installation.png)
+        ![](./figures/semi-automatic-installation.png)
 
     3.  Press  **Ctrl**+**x**  to start the automatic installation.
 
@@ -186,7 +186,7 @@ To use kickstart to perform semi-automatic installation of openEuler, perform th
 
     After the installation is complete, the system automatically restarts. Then, the installation page is displayed again. Shut down the computer and change startup option to start from the hard disk preferentially.
 
-    ![](figures/completing-the-automatic-installation.png)
+    ![](./figures/completing-the-automatic-installation.png)
 
 
 ## Full-automatic Installation Guide
@@ -207,7 +207,7 @@ To use kickstart to perform full-automatic installation of openEuler, perform th
 
 **Environment Preparation**
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >Before the installation, ensure that the firewall of the HTTP server is disabled. Run the following command to disable the firewall:  
 >```  
 >iptables -F  
@@ -271,7 +271,7 @@ To use kickstart to perform full-automatic installation of openEuler, perform th
     # System language
     lang zh_CN.UTF-8
     #Use http installation source
-    url  --url=http://192.168.122.1/openEuler/
+    url  --url=//192.168.122.1/openEuler/
     %post
     #enable kdump
     sed  -i "s/ ro / ro crashkernel=1024M,high /" /boot/efi/EFI/openEuler/grub.cfg
@@ -315,7 +315,7 @@ To use kickstart to perform full-automatic installation of openEuler, perform th
     
     ### BEGIN /etc/grub.d/10_linux ###
     menuentry 'Install openEuler 20.03 LTS' --class red --class gnu-linux --class gnu --class os {
-            set root=(tftp,192.168.122.1)
+            set root=(tftp,192.168.1.1)
             linux /vmlinuz ro inst.geoloc=0 console=ttyAMA0 console=tty0 rd.iscsi.waitnet=0 inst.ks=http://192.168.122.1/ks/openEuler-ks.cfg
             initrd /initrd.img
     }
@@ -336,7 +336,7 @@ To use kickstart to perform full-automatic installation of openEuler, perform th
     filename "grubaa64.efi";  # pxelinux location of the startup file;
     next-server 192.168.122.1;     # (IMPORTANT) TFTP server IP address;
     subnet 192.168.122.0 netmask 255.255.255.0 {
-    option routers 192.168.122.1; # Gateway address
+    option routers 192.168.111.1; # Gateway address
     option subnet-mask 255.255.255.0; # Subnet mask
     range dynamic-bootp 192.168.122.50 192.168.122.200; # Dynamic IP address range
     default-lease-time 21600;
@@ -351,14 +351,14 @@ To use kickstart to perform full-automatic installation of openEuler, perform th
 
 1.  On the  **Start boot option**  screen, press  **F2**  to boot from the PXE and start automatic installation.
 
-    ![](figures/en-us_image_0229291270.png)
+    ![](./figures/en-us_image_0229291270.png)
 
-    ![](figures/en-us_image_0229291286.png)
+    ![](./figures/en-us_image_0229291286.png)
 
-    ![](figures/en-us_image_0229291247.png)
+    ![](./figures/en-us_image_0229291247.png)
 
 2.  The automatic installation window is displayed.
 3.  Verify that the installation is complete.
 
-    ![](figures/completing-the-automatic-installation.png)
+    ![](./figures/completing-the-automatic-installation.png)
 
diff --git a/docs/en/docs/20.03_LTS/docs/Quickstart/figures/advanced-user-configuration.png b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/advanced-user-configuration.png
new file mode 100644
index 0000000000000000000000000000000000000000..3a27f8b5371323cf27dae8dd7e8549ff1e1f8c4b
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/advanced-user-configuration.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Quickstart/figures/completing-the-installation.png b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/completing-the-installation.png
new file mode 100644
index 0000000000000000000000000000000000000000..4f339374e1f2ce5d912625f2fc6c59c24a4a9dcc
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/completing-the-installation.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Quickstart/figures/creating-a-user.png b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/creating-a-user.png
new file mode 100644
index 0000000000000000000000000000000000000000..e62fa5b13359d2ffe926217dacd183a70a609cc5
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/creating-a-user.png differ
diff --git a/content/en/docs/Quickstart/figures/drive-icon.png b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/drive-icon.png
similarity index 100%
rename from content/en/docs/Quickstart/figures/drive-icon.png
rename to docs/en/docs/20.03_LTS/docs/Quickstart/figures/drive-icon.png
diff --git a/content/en/docs/Quickstart/figures/en-us_image_0229420473.png b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/en-us_image_0229420473.png
similarity index 100%
rename from content/en/docs/Quickstart/figures/en-us_image_0229420473.png
rename to docs/en/docs/20.03_LTS/docs/Quickstart/figures/en-us_image_0229420473.png
diff --git a/content/en/docs/Quickstart/figures/image-dialog-box.png b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/image-dialog-box.png
similarity index 100%
rename from content/en/docs/Quickstart/figures/image-dialog-box.png
rename to docs/en/docs/20.03_LTS/docs/Quickstart/figures/image-dialog-box.png
diff --git a/docs/en/docs/20.03_LTS/docs/Quickstart/figures/installation-summary.png b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/installation-summary.png
new file mode 100644
index 0000000000000000000000000000000000000000..403b9a53202f2f62e97676aefb92924c263e1b14
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/installation-summary.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Quickstart/figures/installation-wizard.png b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/installation-wizard.png
new file mode 100644
index 0000000000000000000000000000000000000000..fa877dc25ad84e623449add69460a8b617ed9c60
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/installation-wizard.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Quickstart/figures/password-of-the-root-account.png b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/password-of-the-root-account.png
new file mode 100644
index 0000000000000000000000000000000000000000..1b62043d52df903e9cd5221002d89b6d2e9cfefa
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/password-of-the-root-account.png differ
diff --git a/content/en/docs/Quickstart/figures/restart-icon.png b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/restart-icon.png
similarity index 100%
rename from content/en/docs/Quickstart/figures/restart-icon.png
rename to docs/en/docs/20.03_LTS/docs/Quickstart/figures/restart-icon.png
diff --git a/docs/en/docs/20.03_LTS/docs/Quickstart/figures/selecting-a-language.png b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/selecting-a-language.png
new file mode 100644
index 0000000000000000000000000000000000000000..7230029ddd5c0fc0cbe5b9f220c5e380aed9927e
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/selecting-a-language.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Quickstart/figures/selecting-installation-software.png b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/selecting-installation-software.png
new file mode 100644
index 0000000000000000000000000000000000000000..72561ef0c81ff8041105bc27e45ddf1c57b7e0a1
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/selecting-installation-software.png differ
diff --git a/content/en/docs/Quickstart/figures/setting-the-boot-device.png b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/setting-the-boot-device.png
similarity index 100%
rename from content/en/docs/Quickstart/figures/setting-the-boot-device.png
rename to docs/en/docs/20.03_LTS/docs/Quickstart/figures/setting-the-boot-device.png
diff --git a/docs/en/docs/20.03_LTS/docs/Quickstart/figures/setting-the-installation-destination.png b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/setting-the-installation-destination.png
new file mode 100644
index 0000000000000000000000000000000000000000..49a06b3f62da737a366e5b0da3b25ca66726bae2
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/setting-the-installation-destination.png differ
diff --git a/docs/en/docs/20.03_LTS/docs/Quickstart/figures/starting-installation.png b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/starting-installation.png
new file mode 100644
index 0000000000000000000000000000000000000000..4bd779430c0dd891099dffbd7b65298eae0dea58
Binary files /dev/null and b/docs/en/docs/20.03_LTS/docs/Quickstart/figures/starting-installation.png differ
diff --git a/content/en/docs/Quickstart/public_sys-resources/icon-caution.gif b/docs/en/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-caution.gif
similarity index 100%
rename from content/en/docs/Quickstart/public_sys-resources/icon-caution.gif
rename to docs/en/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-caution.gif
diff --git a/content/en/docs/Quickstart/public_sys-resources/icon-danger.gif b/docs/en/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-danger.gif
similarity index 100%
rename from content/en/docs/Quickstart/public_sys-resources/icon-danger.gif
rename to docs/en/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-danger.gif
diff --git a/content/en/docs/Quickstart/public_sys-resources/icon-note.gif b/docs/en/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-note.gif
similarity index 100%
rename from content/en/docs/Quickstart/public_sys-resources/icon-note.gif
rename to docs/en/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-note.gif
diff --git a/content/en/docs/Quickstart/public_sys-resources/icon-notice.gif b/docs/en/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-notice.gif
similarity index 100%
rename from content/en/docs/Quickstart/public_sys-resources/icon-notice.gif
rename to docs/en/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-notice.gif
diff --git a/content/en/docs/Quickstart/public_sys-resources/icon-tip.gif b/docs/en/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-tip.gif
similarity index 100%
rename from content/en/docs/Quickstart/public_sys-resources/icon-tip.gif
rename to docs/en/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-tip.gif
diff --git a/content/en/docs/Quickstart/public_sys-resources/icon-warning.gif b/docs/en/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-warning.gif
similarity index 100%
rename from content/en/docs/Quickstart/public_sys-resources/icon-warning.gif
rename to docs/en/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-warning.gif
diff --git a/content/en/docs/Quickstart/quick-start.md b/docs/en/docs/20.03_LTS/docs/Quickstart/quick-start.md
similarity index 89%
rename from content/en/docs/Quickstart/quick-start.md
rename to docs/en/docs/20.03_LTS/docs/Quickstart/quick-start.md
index aec39101da082efdc375548a4fe42db476f92dfa..6fd7028cdd53e11f3bda2e891f86822bb27b305f 100644
--- a/content/en/docs/Quickstart/quick-start.md
+++ b/docs/en/docs/20.03_LTS/docs/Quickstart/quick-start.md
@@ -129,13 +129,13 @@ To prevent incomplete download of the software package due to network or storage
 1.  Obtain the verification value in the verification file. Run the following command:
 
     ```
-    #cat openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum 
+    $ cat openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum 
     ```
 
 2.  Calculate the SHA256 verification value of the file. Run the following command:
 
     ```
-    #sha256sum openEuler-20.03-LTS-aarch64-dvd.iso
+    $ sha256sum openEuler-20.03-LTS-aarch64-dvd.iso
     ```
 
     After the command is run, the verification value is displayed.
@@ -156,7 +156,7 @@ To prevent incomplete download of the software package due to network or storage
     Set  **Effective**  and  **Boot Medium**  to  **One-time**  and  **DVD-ROM**, respectively, and click  **Save**, as shown in  [Figure 1](#fig1011938131018).
 
     **Figure  1**  Setting the boot device  
-    ![](figures/setting-the-boot-device.png "setting-the-boot-device")
+    ![](./figures/setting-the-boot-device.png "setting-the-boot-device")
 
 3.  Choose  **Remote Console**  from the main menu. The  **Remote Console**  page is displayed.
 
@@ -165,28 +165,28 @@ To prevent incomplete download of the software package due to network or storage
 4.  On the toolbar, click the icon shown in the following figure.
 
     **Figure  2**  Drive icon  
-    ![](figures/drive-icon.png "drive-icon")
+    ![](./figures/drive-icon.png "drive-icon")
 
     An image dialog box is displayed, as shown in the following figure.
 
     **Figure  3**  Image dialog box  
-    ![](figures/image-dialog-box.png "image-dialog-box")
+    ![](./figures/image-dialog-box.png "image-dialog-box")
 
 5.  Select  **Image File**  and then click  **Browse**. The  **Open**  dialog box is displayed.
 6.  Select the image file and click  **Open**. In the image dialog box, click  **Connect**. If  **Connect**  changes to  **Disconnect**, the virtual CD/DVD-ROM drive is connected to the server.
 7.  On the toolbar, click the restart icon shown in the following figure to restart the device.
 
     **Figure  4**  Restart icon  
-    ![](figures/restart-icon.png "restart-icon")
+    ![](./figures/restart-icon.png "restart-icon")
 
 8.  A boot menu is displayed after the system restarts, as shown in  [Figure 5](#fig1648754873314).
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >-   If you do not perform any operations within 1 minute, the system automatically selects the default option  **Test this media & install openEuler 20.03 LTS**  and enters the installation page.  
-    >-   During PM installation, if you cannot use the arrow keys to select boot options and the system does not respond after you press  **Enter**, click  ![](figures/en-us_image_0229420473.png)  on the BMC page and configure  **Key & Mouse Reset**.  
+    >-   During PM installation, if you cannot use the arrow keys to select boot options and the system does not respond after you press  **Enter**, click  ![](./figures/en-us_image_0229420473.png)  on the BMC page and configure  **Key & Mouse Reset**.  
 
     **Figure  5**  Installation Wizard  
-    
+    ![](./figures/installation-wizard.png)
 
 9.  On the installation wizard page, press  **Enter**  to select the default option  **Test this media & install openEuler 20.03 LTS**  to enter the GUI installation page.
 
@@ -197,7 +197,7 @@ After entering the GUI installation page, perform the following operations to in
 1.  Set an installation language. The default language is English. You can change the language based on the site requirements, as shown in  [Figure 6](#fig874344811484).
 
     **Figure  6**  Selecting a language  
-    
+    ![](./figures/selecting-a-language.png)
 
 2.  On the  **INSTALLATION SUMMARY**  page, set configuration items based on the site requirements.
 
@@ -206,16 +206,16 @@ After entering the GUI installation page, perform the following operations to in
     -   You can click  **Begin Installation**  to install the system only when all alarms are cleared.
 
     **Figure  7**  Installation summary  
-    
+    ![](./figures/installation-summary.png)
 
     1.  Select  **Software Selection**  to set configuration items.
 
         Based on the site requirements, select  **Minimal Install**  on the left box and select an add-on in the  **Add-Ons for Selected Environment**  area on the right, as shown in  [Figure 8](#fig1133717611109).
 
         **Figure  8**  Selecting installation software  
-        
+        ![](./figures/selecting-installation-software.png)
 
-        >![](public_sys-resources/icon-note.gif) **NOTE:**   
+        >![](./public_sys-resources/icon-note.gif) **NOTE:**   
         >-   In  **Minimal Install**  mode, not all packages in the installation source will be installed. If the required package is not installed, you can mount the installation source to the local PC and configure a repo source, and use DNF to install the package.  
         >-   If you select  **Virtual Host**, the virtualization components QEMU, libvirt, and edk2 are installed by default. You can select whether to install the OVS component in the add-on area.  
 
@@ -223,17 +223,15 @@ After entering the GUI installation page, perform the following operations to in
 
     2.  Select  **Installation Destination**  to set configuration items.
 
-        On the  **INSTALLATION DESTINATION**  page, select a local storage device. 
+        On the  **INSTALLATION DESTINATION**  page, select a local storage device or click  **Add a disk**  to add a specified additional device or network device. You also need to configure the storage to partition the system. You can either manually configure partitions or select  **Automatic**  to automatically configure partitioning. Select  **Automatic**  if the software is installed in a new storage device or the data in the storage device is not required, as shown in  [Figure 9](#fig153381468101).
 
-        >![](public_sys-resources/icon-notice.gif) **NOTICE:**   
+        >![](./public_sys-resources/icon-notice.gif) **NOTICE:**   
         >When selecting the device to be installed, you are advised not to use the NVMe SSD storage medium as the OS installation disk.  
 
-        You also need to configure the storage to partition the system. You can either manually configure partitions or select  **Automatic**  to automatically configure partitioning. Select  **Automatic**  if the software is installed in a new storage device or the data in the storage device is not required, as shown in  [Figure 9](#fig153381468101).
-
         **Figure  9**  Setting the installation destination  
-        
+        ![](./figures/setting-the-installation-destination.png)
 
-        >![](public_sys-resources/icon-note.gif) **NOTE:**   
+        >![](./public_sys-resources/icon-note.gif) **NOTE:**   
         >-   During partitioning, to ensure system security and performance, you are advised to divide the device into the following partitions:  **/boot**,  **/var**,  **/var/log**,  **/var/log/audit**,  **/home**, and  **/tmp**.  
         >-   If the system is configured with the swap partition, the swap partition is used when the physical memory of the system is insufficient. Although the swap partition can be used to expand the physical memory, if the swap partition is used due to insufficient memory, the system response slows and the system performance deteriorates. Therefore, you are not advised to configure the swap partition in the system with sufficient physical memory or the performance sensitive system.  
         >-   If you need to split a logical volume group, select  **Custom**  to manually partition the logical volume group. On the  **MANUAL PARTITIONING**  page, click  **Modify**  in the  **Volume Group**  area to reconfigure the logical volume group.  
@@ -245,13 +243,13 @@ After entering the GUI installation page, perform the following operations to in
 3.  Click  **Begin Installation**  to install the system, as shown in  [Figure 10](#fig1717019357392).
 
     **Figure  10**  Starting installation  
-    
+    ![](./figures/starting-installation.png)
 
 4.  Set the root user password.
 
     Click  **Root Password**. In the displayed dialog box, as shown in  [Figure 11](#en-us_topic_0186390266_en-us_topic_0122145909_fig1323165793018), enter a password and re-enter to confirm.
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >The  **root**  password must be configured when you install software packages. Otherwise, the installation will fail. A  **root**  account is used for performing critical system administration tasks. It is not recommended to use this account for daily work or system access.  
 
     The password of the  **root**  user must meet the password complexity requirements. Otherwise, the password configuration or user creation will fail. The password complexity requirements are as follows:
@@ -260,22 +258,39 @@ After entering the GUI installation page, perform the following operations to in
     -   A password must contain at least three of the following types: uppercase letters, lowercase letters, digits, and special characters.
     -   A password must be different from the account name.
     -   A password cannot contain words in the dictionary.
-    
-        >![](public_sys-resources/icon-note.gif) **NOTE:**   
-        > In the installed openEuler environment, you can run the `cracklib-unpacker /usr/share/cracklib/pw_dict > dictionary.txt` command to export the dictionary library file  **dictionary.txt**, and then check whether the password is in the dictionary.
+        -   Querying a dictionary
+
+            In the installed openEuler environment, you can run the following command to export the dictionary library file  **dictionary.txt**, and then check whether the password is in the dictionary.
+
+            ```
+            cracklib-unpacker /usr/share/cracklib/pw_dict > dictionary.txt
+            ```
+
+        -   Modifying a dictionary
+            -   Modify the exported dictionary library file, and then run the following command to update the dictionary library:
+
+                ```
+                create-cracklib-dict dictionary.txt
+                ```
+
+            -   Run the following command to add another dictionary file  **custom.txt**  to the original dictionary library.
+
+                ```
+                create-cracklib-dict dictionary.txt custom.txt
+                ```
     
     **Figure  11**  Password of the  **root**  account  
-    
+    ![](./figures/password-of-the-root-account.png)
     
 5.  Create a user.
 
     Click  **User Creation**.  [Figure 12](#en-us_topic_0186390266_en-us_topic_0122145909_fig1237715313319)  shows the page for creating a user. Enter a username and set a password. The password complexity requirements are the same as those of the user  **root**. By clicking  **Advanced**, you can also configure a home directory and a user group, as shown in  [Figure 13](#en-us_topic_0186390266_en-us_topic_0122145909_fig128716531312).
 
     **Figure  12**  Creating a user  
-    
+    ![](./figures/creating-a-user.png)
 
     **Figure  13**  Advanced user configuration  
-    
+    ![](./figures/advanced-user-configuration.png)
 
     After configuration, click  **Done**  in the left-upper corner to switch back to the installation process page.
 
@@ -284,7 +299,7 @@ After entering the GUI installation page, perform the following operations to in
     openEuler has been installed, as shown in  [Figure 14](#en-us_topic_0186390267_en-us_topic_0122145917_fig1429512116338). Click  **Reboot**  to restart the system.
 
     **Figure  14**  Completing the installation  
-    
+    ![](./figures/completing-the-installation.png)
 
 
 ## Viewing System Information
@@ -302,10 +317,10 @@ After the system is installed and restarted, the system CLI login page is displa
     ```
     # cat /etc/os-release
     NAME="openEuler"
-    VERSION="20.09"
+    VERSION="20.03 (LTS)"
     ID="openEuler"
-    VERSION_ID="20.09"
-    PRETTY_NAME="openEuler 20.09"
+    VERSION_ID="20.03"
+    PRETTY_NAME="openEuler 20.03 (LTS)"
     ANSI_COLOR="0;31"
     ```
 
diff --git a/content/en/docs/Releasenotes/acknowledgement.md b/docs/en/docs/20.03_LTS/docs/Releasenotes/acknowledgement.md
similarity index 100%
rename from content/en/docs/Releasenotes/acknowledgement.md
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/acknowledgement.md
diff --git a/content/en/docs/Releasenotes/common-vulnerabilities-and-exposures-(cve).md b/docs/en/docs/20.03_LTS/docs/Releasenotes/common-vulnerabilities-and-exposures-(cve).md
similarity index 100%
rename from content/en/docs/Releasenotes/common-vulnerabilities-and-exposures-(cve).md
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/common-vulnerabilities-and-exposures-(cve).md
diff --git a/content/en/docs/Releasenotes/contribution.md b/docs/en/docs/20.03_LTS/docs/Releasenotes/contribution.md
similarity index 100%
rename from content/en/docs/Releasenotes/contribution.md
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/contribution.md
diff --git a/content/en/docs/Releasenotes/installing-the-os.md b/docs/en/docs/20.03_LTS/docs/Releasenotes/installing-the-os.md
similarity index 99%
rename from content/en/docs/Releasenotes/installing-the-os.md
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/installing-the-os.md
index bf34200af0a9f62c2c345a42b8f31b24253346d0..290189a13e6f84d111e1832be2e5c83c38b4270b 100644
--- a/content/en/docs/Releasenotes/installing-the-os.md
+++ b/docs/en/docs/20.03_LTS/docs/Releasenotes/installing-the-os.md
@@ -149,7 +149,7 @@ The following table lists the [openEuler release files](http://repo.openeuler.or
 
 
Memory

 
-
32G*4 2933MHz

+
32G\*4 2933MHz

 
 
 
RAID controller card

diff --git a/content/en/docs/Releasenotes/introduction.md b/docs/en/docs/20.03_LTS/docs/Releasenotes/introduction.md
similarity index 100%
rename from content/en/docs/Releasenotes/introduction.md
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/introduction.md
diff --git a/content/en/docs/Releasenotes/key-features.md b/docs/en/docs/20.03_LTS/docs/Releasenotes/key-features.md
similarity index 99%
rename from content/en/docs/Releasenotes/key-features.md
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/key-features.md
index 9590ee5de7e7c3e07ea69341207b44d69c1db228..f85e47a3cc1ee274bb4c15256edc5e0e5e54db79 100644
--- a/content/en/docs/Releasenotes/key-features.md
+++ b/docs/en/docs/20.03_LTS/docs/Releasenotes/key-features.md
@@ -27,3 +27,5 @@
     -   Memory virtualization optimization: The Kunpeng hardware feature is used to improve the memory loading speed during VM startup.
     -   Storage virtualization optimization: NUMA affinity self-binding is optimized for the iSCSI module **kworker** to improve the I/O performance of IP SAN disks.
 
+
+
diff --git a/content/en/docs/Releasenotes/known-issues.md b/docs/en/docs/20.03_LTS/docs/Releasenotes/known-issues.md
similarity index 72%
rename from content/en/docs/Releasenotes/known-issues.md
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/known-issues.md
index aad4be328d247d0ea0bf51c9163aaf856318f4e1..ac86061d133364bdc1b02d0c0eade760704a4927 100644
--- a/content/en/docs/Releasenotes/known-issues.md
+++ b/docs/en/docs/20.03_LTS/docs/Releasenotes/known-issues.md
@@ -8,4 +8,13 @@
 -   CVE-2015-9541: When Qt attempts to parse the abnormal SVG files which are constructed to launch exponential XML entity extension attacks, the memory may be insufficient. For details about the discussion, click  [https://codereview.qt-project.org/c/qt/qtbase/+/293909](https://codereview.qt-project.org/c/qt/qtbase/+/293909).
 -   Before compiling some open-source packages, you need to install basic software such as GDB, GCC, and make. Otherwise, the compilation fails due to lack of dependency.
 -   AArch64 and x86\_64 have different definitions of the character type. As a result, an error is reported during the self-check using Coreutils, Augeas, and Diffutils. You can add the  **--fsigned-char**  compilation option to solve the problem.
-
+-   For 20.03 LTS, if you run the **rpm -Uvh XXX** command (XXX indicates the version, for example, mysql-8.0.21-1.oe1.aarch64.rpm) to upgrade mysql-8.0.17-3.oe1 to the latest version, the functions are unavailable after the upgrade. You can use either of the following methods to upgrade the version. The following uses the upgrade from mysql-8.0.17-3.oe1 to mysql-8.0.21-1.oe1 as an example:  
+    -  Method 1: Run the following upgrade command:  
+        ``` 
+        # rpm -Uvh mysql-8.0.21-1.oe1.aarch64.rpm --noscripts 
+        ```
+    -  Method 2: Run the following commands to uninstall the MySQL of the earlier version and then install the MySQL of the new version:
+        ```
+        # rpm -e mysql-8.0.17-3.oe1      
+        # rpm -ivh mysql-8.0.21-1.oe1.aarch64.rpm
+        ```
\ No newline at end of file
diff --git a/content/en/docs/Releasenotes/public_sys-resources/icon-caution.gif b/docs/en/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-caution.gif
similarity index 100%
rename from content/en/docs/Releasenotes/public_sys-resources/icon-caution.gif
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-caution.gif
diff --git a/content/en/docs/Releasenotes/public_sys-resources/icon-danger.gif b/docs/en/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-danger.gif
similarity index 100%
rename from content/en/docs/Releasenotes/public_sys-resources/icon-danger.gif
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-danger.gif
diff --git a/content/en/docs/Releasenotes/public_sys-resources/icon-note.gif b/docs/en/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-note.gif
similarity index 100%
rename from content/en/docs/Releasenotes/public_sys-resources/icon-note.gif
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-note.gif
diff --git a/content/en/docs/Releasenotes/public_sys-resources/icon-notice.gif b/docs/en/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-notice.gif
similarity index 100%
rename from content/en/docs/Releasenotes/public_sys-resources/icon-notice.gif
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-notice.gif
diff --git a/content/en/docs/Releasenotes/public_sys-resources/icon-tip.gif b/docs/en/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-tip.gif
similarity index 100%
rename from content/en/docs/Releasenotes/public_sys-resources/icon-tip.gif
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-tip.gif
diff --git a/content/en/docs/Releasenotes/public_sys-resources/icon-warning.gif b/docs/en/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-warning.gif
similarity index 100%
rename from content/en/docs/Releasenotes/public_sys-resources/icon-warning.gif
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-warning.gif
diff --git a/content/en/docs/Releasenotes/release_notes.md b/docs/en/docs/20.03_LTS/docs/Releasenotes/release_notes.md
similarity index 100%
rename from content/en/docs/Releasenotes/release_notes.md
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/release_notes.md
diff --git a/content/en/docs/Releasenotes/resolved-issues.md b/docs/en/docs/20.03_LTS/docs/Releasenotes/resolved-issues.md
similarity index 100%
rename from content/en/docs/Releasenotes/resolved-issues.md
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/resolved-issues.md
diff --git a/content/en/docs/Releasenotes/source-code.md b/docs/en/docs/20.03_LTS/docs/Releasenotes/source-code.md
similarity index 84%
rename from content/en/docs/Releasenotes/source-code.md
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/source-code.md
index c6a18531937da2a5a63e5ed41689230f3d068784..e8e41391360885baba774fecef9a255a2c6ff987 100644
--- a/content/en/docs/Releasenotes/source-code.md
+++ b/docs/en/docs/20.03_LTS/docs/Releasenotes/source-code.md
@@ -5,5 +5,5 @@ openEuler contains two code repositories:
 -   Code repository:  [https://gitee.com/openeuler](https://gitee.com/openeuler)
 -   Software package repository:  [https://gitee.com/src-openeuler](https://gitee.com/src-openeuler)
 
-The openEuler release packages also provide the source ISO files. For details, see  [Installing the OS](installing-the-os.md).
+The openEuler release packages also provide the source ISO files. For details, see  [Installing the OS](./installing-the-os.md).
 
diff --git a/content/en/docs/Releasenotes/terms-of-use.md b/docs/en/docs/20.03_LTS/docs/Releasenotes/terms-of-use.md
similarity index 100%
rename from content/en/docs/Releasenotes/terms-of-use.md
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/terms-of-use.md
diff --git a/content/en/docs/Releasenotes/user-notice.md b/docs/en/docs/20.03_LTS/docs/Releasenotes/user-notice.md
similarity index 100%
rename from content/en/docs/Releasenotes/user-notice.md
rename to docs/en/docs/20.03_LTS/docs/Releasenotes/user-notice.md
diff --git a/content/en/docs/Virtualization/appendix.md b/docs/en/docs/20.03_LTS/docs/Virtualization/appendix.md
similarity index 100%
rename from content/en/docs/Virtualization/appendix.md
rename to docs/en/docs/20.03_LTS/docs/Virtualization/appendix.md
diff --git a/content/en/docs/Virtualization/best-practices.md b/docs/en/docs/20.03_LTS/docs/Virtualization/best-practices.md
similarity index 99%
rename from content/en/docs/Virtualization/best-practices.md
rename to docs/en/docs/20.03_LTS/docs/Virtualization/best-practices.md
index c2b4164230dd668da1cad297852c496e09e71a50..2f7a1173fd0bb734f917ab37626d2422e7dabe88 100644
--- a/content/en/docs/Virtualization/best-practices.md
+++ b/docs/en/docs/20.03_LTS/docs/Virtualization/best-practices.md
@@ -20,7 +20,7 @@
 
 If compute resources are sufficient, the halt-polling feature can be used to enable VMs to obtain performance similar to that of physical machines. If the halt-polling feature is not enabled, the host allocates CPU resources to other processes when the vCPU exits due to idle timeout. When the halt-polling feature is enabled on the host, the vCPU of the VM performs polling when it is idle. The polling duration depends on the actual configuration. If the vCPU is woken up during the polling, the vCPU can continue to run without being scheduled from the host. This reduces the scheduling overhead and improves the VM system performance.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >The halt-polling mechanism ensures that the vCPU thread of the VM responds in a timely manner. However, when the VM has no load, the host also performs polling. As a result, the host detects that the CPU usage of the vCPU is high, but the actual CPU usage of the VM is not high.  
 
 #### Instructions
@@ -313,7 +313,7 @@ QEMU guest agent \(qemu-ga\) is a daemon running within VMs. It allows users on
 
 In some scenarios with high security requirements, qemu-ga provides the blacklist function to prevent internal information leakage of VMs. You can use a blacklist to selectively shield some functions provided by qemu-ga.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >The qemu-ga installation package is  **qemu-guest-agent-**_xx_**.rpm**. It is not installed on openEuler by default.  _xx_  indicates the actual version number.  
 
 #### Procedure
@@ -364,7 +364,7 @@ To add a qemu-ga blacklist, perform the following steps:
     root       727     1  0 08:17 ?        00:00:00 /usr/bin/qemu-ga --method=virtio-serial --path=/dev/virtio-ports/org.qemu.guest_agent.0 --blacklist=guest-file-open guest-file-close guest-file-read guest-file-write guest-file-seek guest-file-flush -F/etc/qemu-ga/fsfreeze-hook
     ```
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >For more information about qemu-ga, visit  [https://wiki.qemu.org/Features/GuestAgent](https://wiki.qemu.org/Features/GuestAgent).  
 
 
diff --git a/content/en/docs/Virtualization/environment-preparation.md b/docs/en/docs/20.03_LTS/docs/Virtualization/environment-preparation.md
similarity index 99%
rename from content/en/docs/Virtualization/environment-preparation.md
rename to docs/en/docs/20.03_LTS/docs/Virtualization/environment-preparation.md
index 3124c15cc358b2f58047b191002a18611334056d..dd5010c7694264e7d1cd892184caca13b9e9046d 100644
--- a/content/en/docs/Virtualization/environment-preparation.md
+++ b/docs/en/docs/20.03_LTS/docs/Virtualization/environment-preparation.md
@@ -114,7 +114,7 @@ To enable the VM to communicate with external networks, you need to configure th
 This section describes how to set up a Linux bridge and an Open vSwitch bridge to connect a VM to the network. You can select a bridge type based on the site requirements.
 
 **Figure  1**  Virtual network structure  
-![](figures/virtual-network-structure.png "virtual-network-structure")
+![](./figures/virtual-network-structure.png "virtual-network-structure")
 
 ### Setting Up a Linux Bridge
 
diff --git a/content/en/docs/Virtualization/figures/en-us_image_0218587435.png b/docs/en/docs/20.03_LTS/docs/Virtualization/figures/en-us_image_0218587435.png
similarity index 100%
rename from content/en/docs/Virtualization/figures/en-us_image_0218587435.png
rename to docs/en/docs/20.03_LTS/docs/Virtualization/figures/en-us_image_0218587435.png
diff --git a/content/en/docs/Virtualization/figures/en-us_image_0218587436.png b/docs/en/docs/20.03_LTS/docs/Virtualization/figures/en-us_image_0218587436.png
similarity index 100%
rename from content/en/docs/Virtualization/figures/en-us_image_0218587436.png
rename to docs/en/docs/20.03_LTS/docs/Virtualization/figures/en-us_image_0218587436.png
diff --git a/content/en/docs/Virtualization/figures/kvm-architecture.png b/docs/en/docs/20.03_LTS/docs/Virtualization/figures/kvm-architecture.png
similarity index 100%
rename from content/en/docs/Virtualization/figures/kvm-architecture.png
rename to docs/en/docs/20.03_LTS/docs/Virtualization/figures/kvm-architecture.png
diff --git a/content/en/docs/Virtualization/figures/status-transition-diagram.png b/docs/en/docs/20.03_LTS/docs/Virtualization/figures/status-transition-diagram.png
similarity index 100%
rename from content/en/docs/Virtualization/figures/status-transition-diagram.png
rename to docs/en/docs/20.03_LTS/docs/Virtualization/figures/status-transition-diagram.png
diff --git a/content/en/docs/Virtualization/figures/virtual-network-structure.png b/docs/en/docs/20.03_LTS/docs/Virtualization/figures/virtual-network-structure.png
similarity index 100%
rename from content/en/docs/Virtualization/figures/virtual-network-structure.png
rename to docs/en/docs/20.03_LTS/docs/Virtualization/figures/virtual-network-structure.png
diff --git a/content/en/docs/Virtualization/figures/virtualized-architecture.png b/docs/en/docs/20.03_LTS/docs/Virtualization/figures/virtualized-architecture.png
similarity index 100%
rename from content/en/docs/Virtualization/figures/virtualized-architecture.png
rename to docs/en/docs/20.03_LTS/docs/Virtualization/figures/virtualized-architecture.png
diff --git a/content/en/docs/Virtualization/installation-to-virtualization.md b/docs/en/docs/20.03_LTS/docs/Virtualization/installation-to-virtualization.md
similarity index 98%
rename from content/en/docs/Virtualization/installation-to-virtualization.md
rename to docs/en/docs/20.03_LTS/docs/Virtualization/installation-to-virtualization.md
index d49588392512857b973c8a159aa2a3b27e051cf4..950342281c19dee5ec1222082ba48ba09dd35fb5 100644
--- a/content/en/docs/Virtualization/installation-to-virtualization.md
+++ b/docs/en/docs/20.03_LTS/docs/Virtualization/installation-to-virtualization.md
@@ -49,7 +49,7 @@ The minimum hardware requirements for installing virtualization components on op
     ```
 
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >The KVM module is integrated in the openEuler kernel and does not need to be installed separately.  
 
 ### Verifying the Installation
diff --git a/content/en/docs/Virtualization/introduction-to-virtualization.md b/docs/en/docs/20.03_LTS/docs/Virtualization/introduction-to-virtualization.md
similarity index 97%
rename from content/en/docs/Virtualization/introduction-to-virtualization.md
rename to docs/en/docs/20.03_LTS/docs/Virtualization/introduction-to-virtualization.md
index a97608208c1538e076c478f6f1a78b7706cd025f..0abe43ba5f4a5d869f2c8a5c68cbac325d9a4f83 100644
--- a/content/en/docs/Virtualization/introduction-to-virtualization.md
+++ b/docs/en/docs/20.03_LTS/docs/Virtualization/introduction-to-virtualization.md
@@ -7,7 +7,7 @@ In computer technologies, virtualization is a resource management technology. It
 Virtualization enables multiple virtual machines \(VMs\) to run on a physical server. The VMs share the processor, memory, and I/O resources of the physical server, but are logically isolated from each other. In the virtualization technology, the physical server is called a host machine, the VM running on the host machine is called a guest, and the operating system \(OS\) running on the VM is called a guest OS. A layer of software, called the virtualization layer, exists between a host machine and a VM to simulate virtual hardware. This virtualization layer is called a VM monitor, as shown in the following figure.
 
 **Figure  1**  Virtualized architecture 
-![](figures/virtualized-architecture.png "virtualized-architecture")
+![](./figures/virtualized-architecture.png "virtualized-architecture")
 
 ## Virtualized Architecture
 
@@ -25,7 +25,7 @@ Currently, mainstream virtualization technologies are classified into two types
 Kernel-based Virtual Machine \(KVM\) is a kernel module of Linux. It makes Linux a hypervisor.  [Figure 2](#fig310953013541)  shows the KVM architecture. KVM does not simulate any hardware device. It is used to enable virtualization capabilities provided by the hardware, such as Intel VT-x, AMD-V, Arm virtualization extensions. The user-mode QEMU simulates the mainboard, memory, and I/O devices. The user-mode QEMU works with the kernel KVM module to simulate VM hardware. The guest OS runs on the hardware simulated by the QEMU and KVM.
 
 **Figure  2**  KVM architecture
-![](figures/kvm-architecture.png "kvm-architecture")
+![](./figures/kvm-architecture.png "kvm-architecture")
 
 ## Virtualization Components
 
diff --git a/content/en/docs/Virtualization/managing-devices.md b/docs/en/docs/20.03_LTS/docs/Virtualization/managing-devices.md
similarity index 99%
rename from content/en/docs/Virtualization/managing-devices.md
rename to docs/en/docs/20.03_LTS/docs/Virtualization/managing-devices.md
index 9b963276fc2c671e42a9b8ec48889e01e6302b20..5a99b0e168c3ce88a5b09cb4544d46c4333a7d4f 100644
--- a/content/en/docs/Virtualization/managing-devices.md
+++ b/docs/en/docs/20.03_LTS/docs/Virtualization/managing-devices.md
@@ -283,7 +283,7 @@ PCI passthrough directly assigns a physical PCI device on the host to a VM. The
 
 
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >VFIO passthrough is implemented by IOMMU group. Devices are divided to IOMMU groups based on access control services \(ACS\) on hardware. Devices in the same IOMMU group can be assigned to only one VM. If multiple functions on a PCI device belong to the same IOMMU group, they can be directly assigned to only one VM as well.  
 
 ### SR-IOV Passthrough
@@ -292,7 +292,7 @@ PCI passthrough directly assigns a physical PCI device on the host to a VM. The
 
 Single Root I/O Virtualization \(SR-IOV\) is a hardware-based virtualization solution. With the SR-IOV technology, a physical function \(PF\) can provide multiple virtual functions \(VFs\), and each VF can be directly assigned to a VM. This greatly improves hardware resource utilization and I/O performance of VMs. A typical application scenario is SR-IOV passthrough for NICs. With the SR-IOV technology, a physical NIC \(PF\) can function as multiple VF NICs, and then the VFs can be directly assigned to VMs.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >-   SR-IOV requires the support of physical hardware. Before using SR-IOV, ensure that the hardware device to be directly assigned supports SR-IOV and the device driver on the host OS works in SR-IOV mode.  
 >-   The following describes how to query the NIC model:  
 >In the following command output, values in the first column indicate the PCI numbers of NICs, and  **19e5:1822**  indicates the vendor ID and device ID of the NIC.  
@@ -450,7 +450,7 @@ To configure SR-IOV passthrough for a NIC, perform the following steps:
     
     
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >Disabling the SR-IOV function:  
     >To disable the SR-IOV function after the VM is stopped and no VF is in use, run the following command:  
     >The following uses the Hi1822 NIC \(corresponding network interface name: eth0\) as an example:  
@@ -605,7 +605,7 @@ To configure USB passthrough, perform the following steps:
 
 The VM system may be damaged due to virus damage, system file deletion by mistake, or incorrect formatting. As a result, the system cannot be started. To quickly restore a damaged system, openEuler provides the storage snapshot function. openEuler can create a snapshot that records the VM status at specific time points without informing users \(usually within a few seconds\). The snapshot can be used to restore the VM to the status when the snapshots were taken. For example, a damaged system can be quickly restored with the help of snapshots, which improves system reliability.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >Currently, storage snapshots can be QCOW2 and RAW images only. Block devices are not supported.  
 
 ### Procedure
diff --git a/content/en/docs/Virtualization/managing-vms.md b/docs/en/docs/20.03_LTS/docs/Virtualization/managing-vms.md
similarity index 98%
rename from content/en/docs/Virtualization/managing-vms.md
rename to docs/en/docs/20.03_LTS/docs/Virtualization/managing-vms.md
index d2ba205d45693d00d596d65e8e4b2fb5b5aa572b..14d5ef0e3cf3f01687a4de1d49d34356702676e2 100644
--- a/content/en/docs/Virtualization/managing-vms.md
+++ b/docs/en/docs/20.03_LTS/docs/Virtualization/managing-vms.md
@@ -36,7 +36,7 @@ A VM can be in one of the following status:
 VMs in different status can be converted, but certain rules must be met.  [Figure 1](#fig671014583483)  describes the common rules for transiting the VM status.
 
 **Figure  1**  Status transition diagram  
-![](figures/status-transition-diagram.png "status-transition-diagram")
+![](./figures/status-transition-diagram.png "status-transition-diagram")
 
 ##### VM ID
 
@@ -71,7 +71,7 @@ In libvirt, a created VM instance is called a  **domain**, which describes the c
 
 
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >Run the  **virsh**  command to query the VM ID and UUID. For details, see  [Querying VM Information](#querying-vm-information).  
 
 #### Management Commands
@@ -499,7 +499,7 @@ Before logging in to a VM using a client, such as RealVNC or TightVNC, ensure th
 -   You have obtained the VNC listening port of the VM. This port is automatically allocated when the client is started. Generally, the port number is  **5900 + x**  \(_x_  is a positive integer and increases in ascending order based on the VM startup sequence.  **5900**  is invisible to users.\)
 -   If a password has been set for the VNC, you also need to obtain the VNC password of the VM.
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >To set a password for the VM VNC, edit the XML configuration file of the VM. That is, add the  **passwd**  attribute to the  **graphics**  element and set the attribute value to the password to be configured. For example, to set the VNC password of the VM to  **n8VfjbFK**, configure the XML file as follows:  
     >```  
     >      
@@ -518,7 +518,7 @@ Before logging in to a VM using a client, such as RealVNC or TightVNC, ensure th
     :3
     ```
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >To log in to the VNC, you need to configure firewall rules to allow the connection of the VNC port. The reference command is as follows, where  _X_  is  **5900 + Port number**, for example,  **5903**.  
     >```  
     >firewall-cmd --zone=public --add-port=X/tcp  
@@ -533,7 +533,7 @@ Before logging in to a VM using a client, such as RealVNC or TightVNC, ensure th
 
 By default, the VNC server and client transmit data in plaintext. Therefore, the communication content may be intercepted by a third party. To improve security, openEuler allows the VNC server to configure the Transport Layer Security \(TLS\) mode for encryption and authentication. TLS implements encrypted communication between the VNC server and client to prevent communication content from being intercepted by third parties.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >-   To use the TLS encryption authentication mode, the VNC client must support the TLS mode \(for example, TigerVNC\). Otherwise, the VNC client cannot be connected.  
 >-   The TLS encryption authentication mode is configured at the host level. After this feature is enabled, the TLS encryption authentication mode is enabled for the VNC clients of all VMs running on the host.  
 
@@ -552,7 +552,7 @@ To enable the TLS encryption authentication mode for the VNC, perform the follow
 
 2.  Create a certificate and a private key file for the VNC. The following uses GNU TLS as an example.
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >To use GNU TLS, install the gnu-utils software package in advance.  
 
     1.  Create a certificate file issued by the Certificate Authority \(CA\).
@@ -644,7 +644,7 @@ To enable the TLS encryption authentication mode for the VNC, perform the follow
 
 5.  Copy the generated client certificates  **ca-cert.pem**,  **client-cert.pem**, and  **client-key.pem**  to the VNC client. After the TLS certificate of the VNC client is configured, you can use VNC TLS to log in to the VM.
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >-   For details about how to configure the VNC client certificate, see the usage description of each client.  
     >-   For details about how to log in to the VM, see Logging In Using VNC Passwords.  
 
diff --git a/content/en/docs/Virtualization/public_sys-resources/icon-caution.gif b/docs/en/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-caution.gif
similarity index 100%
rename from content/en/docs/Virtualization/public_sys-resources/icon-caution.gif
rename to docs/en/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-caution.gif
diff --git a/content/en/docs/Virtualization/public_sys-resources/icon-danger.gif b/docs/en/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-danger.gif
similarity index 100%
rename from content/en/docs/Virtualization/public_sys-resources/icon-danger.gif
rename to docs/en/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-danger.gif
diff --git a/content/en/docs/Virtualization/public_sys-resources/icon-note.gif b/docs/en/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-note.gif
similarity index 100%
rename from content/en/docs/Virtualization/public_sys-resources/icon-note.gif
rename to docs/en/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-note.gif
diff --git a/content/en/docs/Virtualization/public_sys-resources/icon-notice.gif b/docs/en/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-notice.gif
similarity index 100%
rename from content/en/docs/Virtualization/public_sys-resources/icon-notice.gif
rename to docs/en/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-notice.gif
diff --git a/content/en/docs/Virtualization/public_sys-resources/icon-tip.gif b/docs/en/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-tip.gif
similarity index 100%
rename from content/en/docs/Virtualization/public_sys-resources/icon-tip.gif
rename to docs/en/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-tip.gif
diff --git a/content/en/docs/Virtualization/public_sys-resources/icon-warning.gif b/docs/en/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-warning.gif
similarity index 100%
rename from content/en/docs/Virtualization/public_sys-resources/icon-warning.gif
rename to docs/en/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-warning.gif
diff --git a/content/en/docs/Virtualization/system-resource-management.md b/docs/en/docs/20.03_LTS/docs/Virtualization/system-resource-management.md
similarity index 99%
rename from content/en/docs/Virtualization/system-resource-management.md
rename to docs/en/docs/20.03_LTS/docs/Virtualization/system-resource-management.md
index 998e47d7cd29478435ca7989fb03d60dbac6d24f..7491c3b76a18de4c2271d0e7bc6414ebc5a713ab 100644
--- a/content/en/docs/Virtualization/system-resource-management.md
+++ b/docs/en/docs/20.03_LTS/docs/Virtualization/system-resource-management.md
@@ -253,7 +253,7 @@ To improve VM performance, you can specify NUMA nodes for a VM using the VM XML
 
     If the vCPU of the VM is bound to the physical CPU of  **node 0**, the performance deterioration caused by the vCPU accessing the remote memory can be avoided.
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >-   The sum of memory allocated to the VM cannot exceed the remaining available memory of the NUMA node. Otherwise, the VM may fail to start.  
     >-   You are advised to bind the VM memory and vCPU to the same NUMA node to avoid the performance deterioration caused by vCPU access to the remote memory. For example, bind the vCPU to NUMA node 0 as well.  
 
@@ -288,7 +288,7 @@ After Guest NUMA is configured in the VM XML configuration file, you can view th
   
 ```
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >-   ****  provides the NUMA topology function for VMs.  **cell id**  indicates the vNode ID,  **cpus**  indicates the vCPU ID, and  **memory**  indicates the memory size on the vNode.  
 >-   If you want to use Guest NUMA to provide better performance, configure <**numatune\>**  and  ****  so that the vCPU and memory are distributed on the same physical NUMA node.  
 >    -   **cellid**  in  ****  corresponds to  **cell id**  in  ****.  **mode**  can be set to  **strict**  \(apply for memory from a specified node strictly. If the memory is insufficient, the application fails.\),  **preferred**  \(apply for memory from a node first. If the memory is insufficient, apply for memory from another node\), or  **interleave**  \(apply for memory from a specified node in cross mode\).;  **nodeset**  indicates the specified physical NUMA node.  
diff --git a/content/en/docs/Virtualization/user-and-administrator-guide.md b/docs/en/docs/20.03_LTS/docs/Virtualization/user-and-administrator-guide.md
similarity index 99%
rename from content/en/docs/Virtualization/user-and-administrator-guide.md
rename to docs/en/docs/20.03_LTS/docs/Virtualization/user-and-administrator-guide.md
index eb75d5342560e396d81dfa5ec83bd0f0a5877a46..47646f59b84e0a9b7e9952054286eba74f6ebdd1 100644
--- a/content/en/docs/Virtualization/user-and-administrator-guide.md
+++ b/docs/en/docs/20.03_LTS/docs/Virtualization/user-and-administrator-guide.md
@@ -26,7 +26,7 @@ This chapter describes how to create VMs on the virtualization platform, manage
 
 If compute resources are sufficient, the halt-polling feature can be used to enable VMs to obtain performance similar to that of physical machines. If the halt-polling feature is not enabled, the host allocates CPU resources to other processes when the vCPU exits due to idle timeout. When the halt-polling feature is enabled on the host, the vCPU of the VM performs polling when it is idle. The polling duration depends on the actual configuration. If the vCPU is woken up during the polling, the vCPU can continue to run without being scheduled from the host. This reduces the scheduling overhead and improves the VM system performance.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >The halt-polling mechanism ensures that the vCPU thread of the VM responds in a timely manner. However, when the VM has no load, the host also performs polling. As a result, the host detects that the CPU usage of the vCPU is high, but the actual CPU usage of the VM is not high.  
 
 ##### Instructions
@@ -319,7 +319,7 @@ QEMU guest agent \(qemu-ga\) is a daemon running within VMs. It allows users on
 
 In some scenarios with high security requirements, qemu-ga provides the blacklist function to prevent internal information leakage of VMs. You can use a blacklist to selectively shield some functions provided by qemu-ga.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >The qemu-ga installation package is  **qemu-guest-agent-**_xx_**.rpm**. It is not installed on openEuler by default.  _xx_  indicates the actual version number.  
 
 ##### Procedure
@@ -370,7 +370,7 @@ To add a qemu-ga blacklist, perform the following steps:
     root       727     1  0 08:17 ?        00:00:00 /usr/bin/qemu-ga --method=virtio-serial --path=/dev/virtio-ports/org.qemu.guest_agent.0 --blacklist=guest-file-open guest-file-close guest-file-read guest-file-write guest-file-seek guest-file-flush -F/etc/qemu-ga/fsfreeze-hook
     ```
 
-    >![](public_sys-resources/icon-note.gif) **NOTE:**   
+    >![](./public_sys-resources/icon-note.gif) **NOTE:**   
     >For more information about qemu-ga, visit  [https://wiki.qemu.org/Features/GuestAgent](https://wiki.qemu.org/Features/GuestAgent).  
 
 
diff --git a/content/en/docs/Virtualization/virtualization.md b/docs/en/docs/20.03_LTS/docs/Virtualization/virtualization.md
similarity index 100%
rename from content/en/docs/Virtualization/virtualization.md
rename to docs/en/docs/20.03_LTS/docs/Virtualization/virtualization.md
diff --git a/content/en/docs/Virtualization/vm-configuration.md b/docs/en/docs/20.03_LTS/docs/Virtualization/vm-configuration.md
similarity index 99%
rename from content/en/docs/Virtualization/vm-configuration.md
rename to docs/en/docs/20.03_LTS/docs/Virtualization/vm-configuration.md
index a290a4a05d92b6440a67f627f3857f5cde638164..0a627ecaa8ca65035fb624a73c40db25138206ac 100644
--- a/content/en/docs/Virtualization/vm-configuration.md
+++ b/docs/en/docs/20.03_LTS/docs/Virtualization/vm-configuration.md
@@ -371,7 +371,7 @@ The bus is a channel for information communication between components of a compu
 
 The PCIe bus is a typical tree structure and has good scalability. The buses are associated with each other by using a controller. The following uses the PCIe bus as an example to describe how to configure a bus topology for a VM.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >The bus configuration is complex. If the device topology does not need to be precisely controlled, the default bus configuration automatically generated by libvirt can be used.  
 
 #### Elements
@@ -573,7 +573,7 @@ In addition to storage devices and network devices, some external devices need t
 
 For example, in the following example, the VM emulator path, pty serial port, VirtIO media device, USB tablet, USB keyboard, and VNC graphics device are configured.
 
->![](public_sys-resources/icon-note.gif) **NOTE:**   
+>![](./public_sys-resources/icon-note.gif) **NOTE:**   
 >When  **type**  of  **graphics**  is set to  **VNC**, you are advised to set the  **passwd**  attribute, that is, the password for logging in to the VM using VNC.  
 
 ```
diff --git a/content/en/docs/Virtualization/vm-live-migration.md b/docs/en/docs/20.03_LTS/docs/Virtualization/vm-live-migration.md
similarity index 100%
rename from content/en/docs/Virtualization/vm-live-migration.md
rename to docs/en/docs/20.03_LTS/docs/Virtualization/vm-live-migration.md
diff --git a/docs/en/docs/20.03_LTS/menu/menu.json b/docs/en/docs/20.03_LTS/menu/menu.json
new file mode 100644
index 0000000000000000000000000000000000000000..b8ab674c853546ad453366cc21ad63c7386452d0
--- /dev/null
+++ b/docs/en/docs/20.03_LTS/menu/menu.json
@@ -0,0 +1,433 @@
+[{
+    "label": "Terms of Use",
+    "path": "docs/Releasenotes/terms-of-use",
+    "children": []
+}, {
+    "label": "Release Notes",
+    "path": "docs/Releasenotes/release_notes",
+    "children": [{
+        "label": "User Notice",
+        "path": "docs/Releasenotes/user-notice",
+        "children": []
+    }, {
+        "label": "Introduction",
+        "path": "docs/Releasenotes/introduction",
+        "children": []
+    }, {
+        "label": "Installing the OS",
+        "path": "docs/Releasenotes/installing-the-os",
+        "children": []
+    }, {
+        "label": "Key Features",
+        "path": "docs/Releasenotes/key-features",
+        "children": []
+    }, {
+        "label": "Known Issues",
+        "path": "docs/Releasenotes/known-issues",
+        "children": []
+    }, {
+        "label": "Resolved Issues",
+        "path": "docs/Releasenotes/resolved-issues",
+        "children": []
+    }, {
+        "label": "Common Vulnerabilities and Exposures \\(CVE\\)",
+        "path": "docs/Releasenotes/common-vulnerabilities-and-exposures-(cve)",
+        "children": []
+    }, {
+        "label": "Source Code",
+        "path": "docs/Releasenotes/source-code",
+        "children": []
+    }, {
+        "label": "Contribution",
+        "path": "docs/Releasenotes/contribution",
+        "children": []
+    }, {
+        "label": "Acknowledgement",
+        "path": "docs/Releasenotes/acknowledgement",
+        "children": []
+    }]
+}, {
+    "label": "Quick Start",
+    "path": "docs/Quickstart/quick-start",
+    "children": []
+}, {
+    "label": "Installation Guide",
+    "path": "docs/Installation/Installation",
+    "children": [{
+        "label": "Installation Preparations",
+        "path": "docs/Installation/installation-preparations",
+        "children": []
+    }, {
+        "label": "Installation Mode",
+        "path": "docs/Installation/installation-mode",
+        "children": []
+    }, {
+        "label": "Installation Guideline",
+        "path": "docs/Installation/installation-guideline",
+        "children": []
+    }, {
+        "label": "Using Kickstart for Automatic Installation",
+        "path": "docs/Installation/using-kickstart-for-automatic-installation",
+        "children": []
+    }, {
+        "label": "FAQs",
+        "path": "docs/Installation/faqs",
+        "children": []
+    }]
+}, {
+    "label": "Administrator Guide",
+    "path": "docs/Administration/administration",
+    "children": [{
+        "label": "Viewing System Information",
+        "path": "docs/Administration/viewing-system-information",
+        "children": []
+    }, {
+        "label": "Basic Configuration",
+        "path": "docs/Administration/basic-configuration",
+        "children": []
+    }, {
+        "label": "User and User Group Management",
+        "path": "docs/Administration/user-and-user-group-management",
+        "children": []
+    }, {
+        "label": "Using the DNF to Manage Software Packages",
+        "path": "docs/Administration/using-the-dnf-to-manage-software-packages",
+        "children": []
+    }, {
+        "label": "Service Management",
+        "path": "docs/Administration/service-management",
+        "children": []
+    }, {
+        "label": "Process Management",
+        "path": "docs/Administration/process-management",
+        "children": []
+    }, {
+        "label": "Configuring the Network",
+        "path": "docs/Administration/configuring-the-network",
+        "children": []
+    }, {
+        "label": "Managing Hard Disks Through LVM",
+        "path": "docs/Administration/managing-hard-disks-through-lvm",
+        "children": []
+    }, {
+        "label": "Using the KAE",
+        "path": "docs/Administration/using-the-kae",
+        "children": []
+    }, {
+        "label": "Configuring Services",
+        "path": "docs/Administration/configuring-services",
+        "children": [{
+            "label": "Configuring the Repo Server",
+            "path": "docs/Administration/configuring-the-repo-server",
+            "children": []
+        }, {
+            "label": "Configuring the FTP Server",
+            "path": "docs/Administration/configuring-the-ftp-server",
+            "children": []
+        }, {
+            "label": "Configuring the Web Server",
+            "path": "docs/Administration/configuring-the-web-server",
+            "children": []
+        }, {
+            "label": "Setting Up the Database Server",
+            "path": "docs/Administration/setting-up-the-database-server",
+            "children": []
+        }]
+    }, {
+        "label": "FAQs",
+        "path": "docs/Administration/faqs",
+        "children": []
+    }]
+}, {
+    "label": "Virtualization User Guide",
+    "path": "docs/Virtualization/virtualization",
+    "children": [{
+        "label": "Introduction to Virtualization",
+        "path": "docs/Virtualization/introduction-to-virtualization",
+        "children": []
+    }, {
+        "label": "Installation to Virtualization",
+        "path": "docs/Virtualization/installation-to-virtualization",
+        "children": []
+    }, {
+        "label": "Environment Preparation",
+        "path": "docs/Virtualization/environment-preparation",
+        "children": []
+    }, {
+        "label": "VM Configuration",
+        "path": "docs/Virtualization/vm-configuration",
+        "children": []
+    }, {
+        "label": "Managing VMs",
+        "path": "docs/Virtualization/managing-vms",
+        "children": []
+    }, {
+        "label": "VM Live Migration",
+        "path": "docs/Virtualization/vm-live-migration",
+        "children": []
+    }, {
+        "label": "System Resource Management",
+        "path": "docs/Virtualization/system-resource-management",
+        "children": []
+    }, {
+        "label": "Managing Devices",
+        "path": "docs/Virtualization/managing-devices",
+        "children": []
+    }, {
+        "label": "Best Practices",
+        "path": "docs/Virtualization/best-practices",
+        "children": []
+    }, {
+        "label": "Appendix",
+        "path": "docs/Virtualization/appendix",
+        "children": []
+    }]
+}, {
+    "label": "Container User Guide",
+    "path": "docs/Container/container",
+    "children": [{
+        "label": "iSulad Container Engine",
+        "path": "docs/Container/isulad-container-engine",
+        "children": [{
+            "label": "Installation, Upgrade and Uninstallation",
+            "path": "docs/Container/installation-upgrade-Uninstallation",
+            "children": [{
+                "label": "Installation and Configuration",
+                "path": "docs/Container/installation-configuration",
+                "children": []
+            }, {
+                "label": "Upgrade Methods",
+                "path": "docs/Container/upgrade-methods",
+                "children": []
+            }, {
+                "label": "Uninstallation",
+                "path": "docs/Container/uninstallation",
+                "children": []
+            }]
+        }, {
+            "label": "Application Scenarios",
+            "path": "docs/Container/application-scenarios",
+            "children": [{
+                "label": "Container Management",
+                "path": "docs/Container/container-management",
+                "children": []
+            }, {
+                "label": "Interconnection with the CNI Network",
+                "path": "docs/Container/interconnection-with-the-cni-network",
+                "children": []
+            }, {
+                "label": "Container Resource Management",
+                "path": "docs/Container/container-resource-management",
+                "children": []
+            }, {
+                "label": "Privileged Container",
+                "path": "docs/Container/privileged-container",
+                "children": []
+            }, {
+                "label": "CRI",
+                "path": "docs/Container/cri",
+                "children": []
+            }, {
+                "label": "Image Management",
+                "path": "docs/Container/image-management",
+                "children": []
+            }, {
+                "label": "Checking the Container Health Status",
+                "path": "docs/Container/checking-the-container-health-status",
+                "children": []
+            }, {
+                "label": "Querying Information",
+                "path": "docs/Container/querying-information",
+                "children": []
+            }, {
+                "label": "Security Features",
+                "path": "docs/Container/security-features",
+                "children": []
+            }, {
+                "label": "Supporting OCI hooks",
+                "path": "docs/Container/supporting-oci-hooks",
+                "children": []
+            }]
+        }, {
+            "label": "Appendix",
+            "path": "docs/Container/appendix",
+            "children": []
+        }]
+    }, {
+        "label": "System Container",
+        "path": "docs/Container/system-container",
+        "children": [{
+            "label": "Installation Guideline",
+            "path": "docs/Container/installation-guideline",
+            "children": []
+        }, {
+            "label": "Usage Guide",
+            "path": "docs/Container/usage-guide",
+            "children": [{
+                "label": "Specifying Rootfs to Create a Container",
+                "path": "docs/Container/specifying-rootfs-to-create-a-container",
+                "children": []
+            }, {
+                "label": "Using systemd to Start a Container",
+                "path": "docs/Container/using-systemd-to-start-a-container",
+                "children": []
+            }, {
+                "label": "Reboot or Shutdown in a Container",
+                "path": "docs/Container/reboot-or-shutdown-in-a-container",
+                "children": []
+            }, {
+                "label": "Configurable Cgroup Path",
+                "path": "docs/Container/configurable-cgroup-path",
+                "children": []
+            }, {
+                "label": "Writable Namespace Kernel Parameters",
+                "path": "docs/Container/writable-namespace-kernel-parameters",
+                "children": []
+            }, {
+                "label": "Shared Memory Channels",
+                "path": "docs/Container/shared-memory-channels",
+                "children": []
+            }, {
+                "label": "Dynamically Loading the Kernel Module",
+                "path": "docs/Container/dynamically-loading-the-kernel-module",
+                "children": []
+            }, {
+                "label": "Environment Variable Persisting",
+                "path": "docs/Container/environment-variable-persisting",
+                "children": []
+            }, {
+                "label": "Maximum Number of Handles",
+                "path": "docs/Container/maximum-number-of-handles",
+                "children": []
+            }, {
+                "label": "Security and Isolation",
+                "path": "docs/Container/security-and-isolation",
+                "children": []
+            }, {
+                "label": "Dynamically Managing Container Resources \\(syscontainer-tools\\)",
+                "path": "docs/Container/dynamically-managing-container-resources-(syscontainer-tools)",
+                "children": []
+            }]
+        }, {
+            "label": "Appendix",
+            "path": "docs/Container/appendix-1",
+            "children": []
+        }]
+    }, {
+        "label": "Secure Container",
+        "path": "docs/Container/secure-container",
+        "children": [{
+            "label": "Installation and Deployment",
+            "path": "docs/Container/installation-and-deployment-1",
+            "children": []
+        }, {
+            "label": "Application Scenarios",
+            "path": "docs/Container/application-scenarios-2",
+            "children": [{
+                "label": "Managing the Lifecycle of a Secure Container",
+                "path": "docs/Container/managing-the-lifecycle-of-a-secure-container",
+                "children": []
+            }, {
+                "label": "Configuring Resources for a Secure Container",
+                "path": "docs/Container/configuring-resources-for-a-secure-container",
+                "children": []
+            }, {
+                "label": "Configuring Networking for a Secure Container",
+                "path": "docs/Container/configuring-networking-for-a-secure-container",
+                "children": []
+            }, {
+                "label": "Monitoring Secure Containers",
+                "path": "docs/Container/monitoring-secure-containers",
+                "children": []
+            }]
+        }, {
+            "label": "Appendix",
+            "path": "docs/Container/appendix-2",
+            "children": []
+        }]
+    }, {
+        "label": "Docker Container",
+        "path": "docs/Container/docker-container",
+        "children": [{
+            "label": "Installation and Deployment",
+            "path": "docs/Container/installation-and-deployment-2",
+            "children": []
+        }, {
+            "label": "Container Management",
+            "path": "docs/Container/container-management-1",
+            "children": []
+        }, {
+            "label": "Image Management",
+            "path": "docs/Container/image-management-1",
+            "children": []
+        }, {
+            "label": "Command Reference",
+            "path": "docs/Container/command-reference",
+            "children": [{
+                "label": "Container Engine",
+                "path": "docs/Container/container-engine",
+                "children": []
+            }, {
+                "label": "Container Management",
+                "path": "docs/Container/container-management-2",
+                "children": []
+            }, {
+                "label": "Image Management",
+                "path": "docs/Container/image-management-2",
+                "children": []
+            }, {
+                "label": "Statistics",
+                "path": "docs/Container/statistics",
+                "children": []
+            }]
+        }]
+    }]
+}, {
+    "label": "A-Tune User Guide",
+    "path": "docs/A-Tune/A-Tune",
+    "children": [{
+        "label": "Getting to Know A-Tune",
+        "path": "docs/A-Tune/getting-to-know-a-tune",
+        "children": []
+    }, {
+        "label": "Installation and Deployment",
+        "path": "docs/A-Tune/installation-and-deployment",
+        "children": []
+    }, {
+        "label": "Application Scenarios",
+        "path": "docs/A-Tune/application-scenarios",
+        "children": []
+    }, {
+        "label": "FAQs",
+        "path": "docs/A-Tune/faqs",
+        "children": []
+    }, {
+        "label": "Appendixes",
+        "path": "docs/A-Tune/appendixes",
+        "children": []
+    }]
+}, {
+    "label": "Application Development Guide",
+    "path": "docs/ApplicationDev/application-development",
+    "children": [{
+        "label": "Preparation",
+        "path": "docs/ApplicationDev/preparation",
+        "children": []
+    }, {
+        "label": "Using GCC for Compilation",
+        "path": "docs/ApplicationDev/using-gcc-for-compilation",
+        "children": []
+    }, {
+        "label": "Using Make for Compilation",
+        "path": "docs/ApplicationDev/using-make-for-compilation",
+        "children": []
+    }, {
+        "label": "Using JDK for Compilation",
+        "path": "docs/ApplicationDev/using-jdk-for-compilation",
+        "children": []
+    }, {
+        "label": "Building an RPM Package",
+        "path": "docs/ApplicationDev/building-an-rpm-package",
+        "children": []
+    }]
+}]
\ No newline at end of file
diff --git a/docs/en/docs/path/path.json b/docs/en/docs/path/path.json
new file mode 100644
index 0000000000000000000000000000000000000000..489cb63270c6aabd8d4d54eaec551aa844696184
--- /dev/null
+++ b/docs/en/docs/path/path.json
@@ -0,0 +1,89 @@
+[
+    {
+        "value": "1.0_Base",
+        "name": "1.0 BASE",
+        "docs": [
+            {
+                "title": "Install",
+                "doc": [
+                    {
+                        "img": "/img/docs/docs-installation.svg",
+                        "path": "/docs/Installation/Installation.html",
+                        "name": "Installation Guide"
+                    }
+                ]
+            }
+        ]
+    },
+    {
+        "value": "20.03_LTS",
+        "name": "20.03 LTS",
+        "docs": [
+            {
+                "title": "About",
+                "doc": [
+                    {
+                        "img": "/img/docs/docs-releasenotes.svg",
+                        "path": "/docs/Releasenotes/release_notes.html",
+                        "name": "Release Notes"
+                    }
+                ]
+            },
+            {
+                "title": "Install",
+                "doc": [
+                    {
+                        "img": "/img/docs/docs-quickstart.svg",
+                        "path": "/docs/Quickstart/quick-start.html",
+                        "name": "Quick Start"
+                    },
+                    {
+                        "img": "/img/docs/docs-installation.svg",
+                        "path": "/docs/Installation/Installation.html",
+                        "name": "Installation Guide"
+                    }
+                ]
+            },
+            {
+                "title": "Mgmt",
+                "doc": [
+                    {
+                        "img": "/img/docs/docs-administration.svg",
+                        "path": "/docs/Administration/administration.html",
+                        "name": "Administrator Guide"
+                    }
+                ]
+            },
+            {
+                "title": "Use",
+                "doc": [
+                    {
+                        "img": "/img/docs/docs-user.svg",
+                        "path": "/docs/Virtualization/virtualization.html",
+                        "name": "Virtualization User Guide"
+                    },
+                    {
+                        "img": "/img/docs/docs-user.svg",
+                        "path": "/docs/Container/container.html",
+                        "name": "Container User Guide"
+                    },
+                    {
+                        "img": "/img/docs/docs-user.svg",
+                        "path": "/docs/A-Tune/A-Tune.html",
+                        "name": "A-Tune User Guide"
+                    }
+                ]
+            },
+            {
+                "title": "Dev",
+                "doc": [
+                    {
+                        "img": "/img/docs/docs-application.svg",
+                        "path": "/docs/ApplicationDev/application-development.html",
+                        "name": "Application Development Guide"
+                    }
+                ]
+            }
+        ]
+    }
+]
\ No newline at end of file
diff --git a/docs/en/documentation/README.md b/docs/en/documentation/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..fdcdac580235f4bd4d680131a698564e0734a967
--- /dev/null
+++ b/docs/en/documentation/README.md
@@ -0,0 +1,7 @@
+---
+title: "Documentation"
+
+---
+
+  
+
\ No newline at end of file
diff --git a/docs/zh/README.md b/docs/zh/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..bfdf916f2efe1030352d19588c9e670576178bf2
--- /dev/null
+++ b/docs/zh/README.md
@@ -0,0 +1,3 @@
+---
+title: "openEuler"
+---
\ No newline at end of file
diff --git a/content/zh/docs/A-Tune/A-Tune.md b/docs/zh/docs/20.03_LTS/docs/A-Tune/A-Tune.md
similarity index 100%
rename from content/zh/docs/A-Tune/A-Tune.md
rename to docs/zh/docs/20.03_LTS/docs/A-Tune/A-Tune.md
diff --git a/content/zh/docs/A-Tune/figures/zh-cn_image_0213178479.png b/docs/zh/docs/20.03_LTS/docs/A-Tune/figures/zh-cn_image_0213178479.png
similarity index 100%
rename from content/zh/docs/A-Tune/figures/zh-cn_image_0213178479.png
rename to docs/zh/docs/20.03_LTS/docs/A-Tune/figures/zh-cn_image_0213178479.png
diff --git a/content/zh/docs/A-Tune/figures/zh-cn_image_0213178480.png b/docs/zh/docs/20.03_LTS/docs/A-Tune/figures/zh-cn_image_0213178480.png
similarity index 100%
rename from content/zh/docs/A-Tune/figures/zh-cn_image_0213178480.png
rename to docs/zh/docs/20.03_LTS/docs/A-Tune/figures/zh-cn_image_0213178480.png
diff --git a/content/zh/docs/A-Tune/figures/zh-cn_image_0214540398.png b/docs/zh/docs/20.03_LTS/docs/A-Tune/figures/zh-cn_image_0214540398.png
similarity index 100%
rename from content/zh/docs/A-Tune/figures/zh-cn_image_0214540398.png
rename to docs/zh/docs/20.03_LTS/docs/A-Tune/figures/zh-cn_image_0214540398.png
diff --git a/content/zh/docs/A-Tune/figures/zh-cn_image_0227497000.png b/docs/zh/docs/20.03_LTS/docs/A-Tune/figures/zh-cn_image_0227497000.png
similarity index 100%
rename from content/zh/docs/A-Tune/figures/zh-cn_image_0227497000.png
rename to docs/zh/docs/20.03_LTS/docs/A-Tune/figures/zh-cn_image_0227497000.png
diff --git a/content/zh/docs/A-Tune/figures/zh-cn_image_0227497343.png b/docs/zh/docs/20.03_LTS/docs/A-Tune/figures/zh-cn_image_0227497343.png
similarity index 100%
rename from content/zh/docs/A-Tune/figures/zh-cn_image_0227497343.png
rename to docs/zh/docs/20.03_LTS/docs/A-Tune/figures/zh-cn_image_0227497343.png
diff --git a/content/zh/docs/A-Tune/figures/zh-cn_image_0231122163.png b/docs/zh/docs/20.03_LTS/docs/A-Tune/figures/zh-cn_image_0231122163.png
similarity index 100%
rename from content/zh/docs/A-Tune/figures/zh-cn_image_0231122163.png
rename to docs/zh/docs/20.03_LTS/docs/A-Tune/figures/zh-cn_image_0231122163.png
diff --git a/content/zh/docs/A-Tune/public_sys-resources/icon-caution.gif b/docs/zh/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-caution.gif
similarity index 100%
rename from content/zh/docs/A-Tune/public_sys-resources/icon-caution.gif
rename to docs/zh/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-caution.gif
diff --git a/content/zh/docs/A-Tune/public_sys-resources/icon-danger.gif b/docs/zh/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-danger.gif
similarity index 100%
rename from content/zh/docs/A-Tune/public_sys-resources/icon-danger.gif
rename to docs/zh/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-danger.gif
diff --git a/content/zh/docs/A-Tune/public_sys-resources/icon-note.gif b/docs/zh/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-note.gif
similarity index 100%
rename from content/zh/docs/A-Tune/public_sys-resources/icon-note.gif
rename to docs/zh/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-note.gif
diff --git a/content/zh/docs/A-Tune/public_sys-resources/icon-notice.gif b/docs/zh/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-notice.gif
similarity index 100%
rename from content/zh/docs/A-Tune/public_sys-resources/icon-notice.gif
rename to docs/zh/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-notice.gif
diff --git a/content/zh/docs/A-Tune/public_sys-resources/icon-tip.gif b/docs/zh/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-tip.gif
similarity index 100%
rename from content/zh/docs/A-Tune/public_sys-resources/icon-tip.gif
rename to docs/zh/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-tip.gif
diff --git a/content/zh/docs/A-Tune/public_sys-resources/icon-warning.gif b/docs/zh/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-warning.gif
similarity index 100%
rename from content/zh/docs/A-Tune/public_sys-resources/icon-warning.gif
rename to docs/zh/docs/20.03_LTS/docs/A-Tune/public_sys-resources/icon-warning.gif
diff --git "a/content/zh/docs/A-Tune/\344\275\277\347\224\250\346\226\271\346\263\225.md" "b/docs/zh/docs/20.03_LTS/docs/A-Tune/\344\275\277\347\224\250\346\226\271\346\263\225.md"
similarity index 99%
rename from "content/zh/docs/A-Tune/\344\275\277\347\224\250\346\226\271\346\263\225.md"
rename to "docs/zh/docs/20.03_LTS/docs/A-Tune/\344\275\277\347\224\250\346\226\271\346\263\225.md"
index 9839fd35342575be2482db35d4c716361c24d917..16fb03c38fec493ad37d1b96c318c2042c6a4a05 100644
--- "a/content/zh/docs/A-Tune/\344\275\277\347\224\250\346\226\271\346\263\225.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/A-Tune/\344\275\277\347\224\250\346\226\271\346\263\225.md"
@@ -89,7 +89,7 @@ Support WorkloadTypes:
 
 ```
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >Active为true表示当前激活的profile，示例表示当前激活的是default类型对应的profile。  
 
 ## 分析负载类型并自优化
@@ -203,7 +203,7 @@ example.conf 可以参考如下方式书写（以下各优化项非必填，仅
 
 采集业务运行时系统的全局资源使用情况以及OS的各项状态信息，并将收集的结果保存到csv格式的输出文件中，作为模型训练的输入数据集。
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >-   本命令依赖采样工具perf，mpstat，vmstat，iostat，sar。  
 >-   CPU型号目前仅支持鲲鹏920，可通过dmidecode -t processor检查CPU型号。  
 
@@ -556,7 +556,7 @@ A-Tune提供了最佳配置的自动搜索能力，免去人工反复做参数
 
 ### 命令格式
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >在运行命令前，需要满足如下条件：  
 >1.  编辑好服务端yaml配置文件，且需要服务端管理员将该配置文件放到服务端的/etc/atuned/tuning/目录下。  
 >2.  编辑好客户端yaml配置文件并放在客户端任一目录。  
@@ -587,7 +587,7 @@ A-Tune提供了最佳配置的自动搜索能力，免去人工反复做参数
     
     
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >当使用参数时，上述两个参数需要同时使用，且-p参数后需要跟具体的项目名称。  
 
 
diff --git "a/content/zh/docs/A-Tune/\345\256\211\350\243\205\344\270\216\351\203\250\347\275\262.md" "b/docs/zh/docs/20.03_LTS/docs/A-Tune/\345\256\211\350\243\205\344\270\216\351\203\250\347\275\262.md"
similarity index 97%
rename from "content/zh/docs/A-Tune/\345\256\211\350\243\205\344\270\216\351\203\250\347\275\262.md"
rename to "docs/zh/docs/20.03_LTS/docs/A-Tune/\345\256\211\350\243\205\344\270\216\351\203\250\347\275\262.md"
index ba4ec2d291b4cad7ddaf9ec6e4ca274aed275547..c1591cf19afdf16062a421443104e1fbdc49ba7d 100644
--- "a/content/zh/docs/A-Tune/\345\256\211\350\243\205\344\270\216\351\203\250\347\275\262.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/A-Tune/\345\256\211\350\243\205\344\270\216\351\203\250\347\275\262.md"
@@ -47,7 +47,7 @@ A-Tune支持单机模式和分布式模式安装：
 
 两种安装模式的简单图示如下：
 
-![](figures/zh-cn_image_0231122163.png)
+![](./figures/zh-cn_image_0231122163.png)
 
 ### 安装操作
 
@@ -84,7 +84,7 @@ A-Tune支持单机模式和分布式模式安装：
 
 4.  安装A-Tune服务端。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >本步骤会同时安装服务端和客户端软件包，对于单机部署模式，请跳过**步骤5**。  
 
     ```
@@ -230,6 +230,6 @@ A-Tune安装完成后，需要启动A-Tune服务才能使用。
 
     若回显为如下，则服务启动成功。
 
-    ![](figures/zh-cn_image_0214540398.png)
+    ![](./figures/zh-cn_image_0214540398.png)
 
 
diff --git "a/content/zh/docs/A-Tune/\345\270\270\350\247\201\351\227\256\351\242\230\344\270\216\350\247\243\345\206\263\346\226\271\346\263\225.md" "b/docs/zh/docs/20.03_LTS/docs/A-Tune/\345\270\270\350\247\201\351\227\256\351\242\230\344\270\216\350\247\243\345\206\263\346\226\271\346\263\225.md"
similarity index 100%
rename from "content/zh/docs/A-Tune/\345\270\270\350\247\201\351\227\256\351\242\230\344\270\216\350\247\243\345\206\263\346\226\271\346\263\225.md"
rename to "docs/zh/docs/20.03_LTS/docs/A-Tune/\345\270\270\350\247\201\351\227\256\351\242\230\344\270\216\350\247\243\345\206\263\346\226\271\346\263\225.md"
diff --git "a/content/zh/docs/A-Tune/\350\256\244\350\257\206A-Tune.md" "b/docs/zh/docs/20.03_LTS/docs/A-Tune/\350\256\244\350\257\206A-Tune.md"
similarity index 99%
rename from "content/zh/docs/A-Tune/\350\256\244\350\257\206A-Tune.md"
rename to "docs/zh/docs/20.03_LTS/docs/A-Tune/\350\256\244\350\257\206A-Tune.md"
index 25ad1784b7ae566694af07a31cb79e5974d068e2..49d6d8be42e98773d46b42091c62fc728273836c 100644
--- "a/content/zh/docs/A-Tune/\350\256\244\350\257\206A-Tune.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/A-Tune/\350\256\244\350\257\206A-Tune.md"
@@ -19,7 +19,7 @@
 
 A-Tune是一款基于AI开发的系统性能优化引擎，它利用人工智能技术，对业务场景建立精准的系统画像，感知并推理出业务特征，进而做出智能决策，匹配并推荐最佳的系统参数配置组合，使业务处于最佳运行状态。
 
-![](figures/zh-cn_image_0227497000.png)
+![](./figures/zh-cn_image_0227497000.png)
 
 ## 架构
 
@@ -29,7 +29,7 @@ A-Tune核心技术架构如下图，主要包括智能决策、系统画像和
 -   系统画像层：主要包括标注和学习系统，标注系统用于业务模型的聚类，学习系统用于业务模型的学习和分类。
 -   交互系统层：用于各类系统资源的监控和配置，调优策略执行在本层进行。
 
-![](figures/zh-cn_image_0227497343.png)
+![](./figures/zh-cn_image_0227497343.png)
 
 ## 支持特性与业务模型
 
diff --git "a/content/zh/docs/A-Tune/\351\231\204\345\275\225.md" "b/docs/zh/docs/20.03_LTS/docs/A-Tune/\351\231\204\345\275\225.md"
similarity index 100%
rename from "content/zh/docs/A-Tune/\351\231\204\345\275\225.md"
rename to "docs/zh/docs/20.03_LTS/docs/A-Tune/\351\231\204\345\275\225.md"
diff --git a/content/zh/docs/Administration/FAQ-54.md b/docs/zh/docs/20.03_LTS/docs/Administration/FAQ-54.md
similarity index 80%
rename from content/zh/docs/Administration/FAQ-54.md
rename to docs/zh/docs/20.03_LTS/docs/Administration/FAQ-54.md
index 4f2b420466c5793add418c2f551ce62c12d405cc..b70c27841cefaf9f812a4239b4b1320142630dc6 100644
--- a/content/zh/docs/Administration/FAQ-54.md
+++ b/docs/zh/docs/20.03_LTS/docs/Administration/FAQ-54.md
@@ -7,6 +7,7 @@
     - [使用rpmbuild编译mariadb失败](#使用rpmbuild编译mariadb失败)
     - [使用默认配置启动SNTP服务失败](#使用默认配置启动sntp服务失败)
     - [安装时出现软件包冲突、文件冲突或缺少软件包导致安装失败](#安装时出现软件包冲突文件冲突或缺少软件包导致安装失败)
+    - [通过dnf update 默认方式升级openssh软件包时无法安装openssh相关包](#通过dnf-update-默认方式升级openssh软件包时无法安装openssh相关包)
 
 
 
@@ -177,3 +178,34 @@ Error:
         ```
 
 3.  重新进行升级操作。
+
+
+## 通过dnf update 默认方式升级openssh软件包时无法安装openssh相关包
+
+### 问题现象
+
+通过dnf update 默认方式升级openssh软件包时会出现无法安装openssh相关包，提示如下：
+
+
+ ```
+ cannot install both openssh-7.8p1-8.oe1.aarch64 and openssh-8.2p1-5.oe1.aarch64
+ cannot install both openssh-7.8p1-8.oe1.aarch64 and openssh-8.2p1-4.oe1.aarch64
+ cannot install the best update condidate for package openssh-clients-8.2p1-5.oe1.aarch64
+ cannot install the best update condidate for package openssh-8.2p1-5.oe1.aarch64
+
+ ```
+
+### 原因分析
+
+DNF 默认情况下会启用DNF包管理器的“best”模式（对应的参数为--best），该默认选型将始终尝试将升级的包升级到可用的最高版本，即使最高版本无法完全满足它需要的依赖关系。如果使用默认启用的DNF best模式，将提醒用户更新的软件包版本可用但不能满足依赖性。如果出现问题，DNF会提示用户相关依赖问题，以便用户知道。openEuler社区开发人员正在寻求进行此默认更改，以防由于依赖性问题导致无法进行安全修复程序包升级，在当前前提下，它可能会被默默忽略而用户不会意识到。此外，使用DNF最佳模式将迅速提醒开发人员升级路径中的问题。  
+
+### 解决方案
+
+DNF的--nobest选项可用于覆盖/关闭默认的“best”行为，以使用户需要升级的包存在依赖问题的场景下可以正常进行安全修改程序包的升级。  
+本次openEuler 20.03-LTS版本中开发人员已识别到在openssh包安全修复版本升级过程中会存在该场景，建议用户了解上面的分析的情况下，选择合理的升级方式，openEuler同步给出具体升级示例操作：  
+
+
+ ```
+ dnf update –y –nobest openssh
+ 
+ ```
\ No newline at end of file
diff --git a/content/zh/docs/Administration/administration.md b/docs/zh/docs/20.03_LTS/docs/Administration/administration.md
similarity index 100%
rename from content/zh/docs/Administration/administration.md
rename to docs/zh/docs/20.03_LTS/docs/Administration/administration.md
diff --git "a/content/zh/docs/Administration/figures/\346\220\255\345\273\272\346\225\260\346\215\256\347\233\230-0.png" b/docs/zh/docs/20.03_LTS/docs/Administration/figures/Creating_DataDisk-0.png
similarity index 100%
rename from "content/zh/docs/Administration/figures/\346\220\255\345\273\272\346\225\260\346\215\256\347\233\230-0.png"
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/Creating_DataDisk-0.png
diff --git "a/content/zh/docs/Administration/figures/\346\220\255\345\273\272\346\225\260\346\215\256\347\233\230.png" b/docs/zh/docs/20.03_LTS/docs/Administration/figures/Creating_DataDisk.png
similarity index 100%
rename from "content/zh/docs/Administration/figures/\346\220\255\345\273\272\346\225\260\346\215\256\347\233\230.png"
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/Creating_DataDisk.png
diff --git a/content/zh/docs/Administration/figures/D1376B2A-D036-41C4-B852-E8368F363B5E-1.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/D1376B2A-D036-41C4-B852-E8368F363B5E-1.png
similarity index 100%
rename from content/zh/docs/Administration/figures/D1376B2A-D036-41C4-B852-E8368F363B5E-1.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/D1376B2A-D036-41C4-B852-E8368F363B5E-1.png
diff --git a/content/zh/docs/Administration/figures/D1376B2A-D036-41C4-B852-E8368F363B5E.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/D1376B2A-D036-41C4-B852-E8368F363B5E.png
similarity index 100%
rename from content/zh/docs/Administration/figures/D1376B2A-D036-41C4-B852-E8368F363B5E.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/D1376B2A-D036-41C4-B852-E8368F363B5E.png
diff --git "a/content/zh/docs/Administration/figures/MariaDB\351\200\273\350\276\221\346\236\266\346\236\204.png" b/docs/zh/docs/20.03_LTS/docs/Administration/figures/Logical_architecture_MariaDB.png
similarity index 100%
rename from "content/zh/docs/Administration/figures/MariaDB\351\200\273\350\276\221\346\236\266\346\236\204.png"
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/Logical_architecture_MariaDB.png
diff --git "a/content/zh/docs/Administration/figures/PostgreSql\346\236\266\346\236\204.png" b/docs/zh/docs/20.03_LTS/docs/Administration/figures/PostgreSQL_architecture.png
similarity index 100%
rename from "content/zh/docs/Administration/figures/PostgreSql\346\236\266\346\236\204.png"
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/PostgreSQL_architecture.png
diff --git "a/content/zh/docs/Administration/figures/top\346\230\276\347\244\272.png" b/docs/zh/docs/20.03_LTS/docs/Administration/figures/Top_Display.png
similarity index 100%
rename from "content/zh/docs/Administration/figures/top\346\230\276\347\244\272.png"
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/Top_Display.png
diff --git "a/content/zh/docs/Administration/figures/\347\231\273\345\275\225.png" b/docs/zh/docs/20.03_LTS/docs/Administration/figures/login.png
similarity index 100%
rename from "content/zh/docs/Administration/figures/\347\231\273\345\275\225.png"
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/login.png
diff --git "a/content/zh/docs/Administration/figures/nginx\351\203\250\347\275\262\346\210\220\345\212\237.png" b/docs/zh/docs/20.03_LTS/docs/Administration/figures/nginx-deploy-success.png
similarity index 100%
rename from "content/zh/docs/Administration/figures/nginx\351\203\250\347\275\262\346\210\220\345\212\237.png"
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/nginx-deploy-success.png
diff --git "a/content/zh/docs/Administration/figures/nginx\346\234\215\345\212\241\345\220\257\345\212\250\345\244\261\350\264\245.png" b/docs/zh/docs/20.03_LTS/docs/Administration/figures/nginx-start-failed.png
similarity index 100%
rename from "content/zh/docs/Administration/figures/nginx\346\234\215\345\212\241\345\220\257\345\212\250\345\244\261\350\264\245.png"
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/nginx-start-failed.png
diff --git "a/content/zh/docs/Administration/figures/nginx\346\234\215\345\212\241\345\220\257\345\212\250\346\210\220\345\212\237.png" b/docs/zh/docs/20.03_LTS/docs/Administration/figures/nginx-start-success.png
similarity index 100%
rename from "content/zh/docs/Administration/figures/nginx\346\234\215\345\212\241\345\220\257\345\212\250\346\210\220\345\212\237.png"
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/nginx-start-success.png
diff --git a/content/zh/docs/Administration/figures/postgres.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/postgres.png
similarity index 100%
rename from content/zh/docs/Administration/figures/postgres.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/postgres.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0229622729.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0229622729.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0229622729.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0229622729.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0229622789.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0229622789.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0229622789.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0229622789.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0230050789.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0230050789.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0230050789.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0230050789.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231143176.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143176.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231143176.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143176.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231143177.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143177.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231143177.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143177.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231143178.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143178.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231143178.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143178.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231143180.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143180.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231143180.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143180.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231143181.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143181.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231143181.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143181.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231143183.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143183.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231143183.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143183.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231143185.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143185.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231143185.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143185.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231143187.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143187.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231143187.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143187.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231143189.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143189.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231143189.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143189.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231143191.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143191.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231143191.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143191.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231143193.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143193.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231143193.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143193.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231143195.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143195.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231143195.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143195.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231143196.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143196.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231143196.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143196.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231143197.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143197.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231143197.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143197.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231143198.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143198.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231143198.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231143198.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231563132.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231563132.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231563132.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231563132.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231563134.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231563134.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231563134.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231563134.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231563135.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231563135.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231563135.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231563135.png
diff --git a/content/zh/docs/Administration/figures/zh-cn_image_0231563136.png b/docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231563136.png
similarity index 100%
rename from content/zh/docs/Administration/figures/zh-cn_image_0231563136.png
rename to docs/zh/docs/20.03_LTS/docs/Administration/figures/zh-cn_image_0231563136.png
diff --git a/content/zh/docs/Administration/public_sys-resources/icon-caution.gif b/docs/zh/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-caution.gif
similarity index 100%
rename from content/zh/docs/Administration/public_sys-resources/icon-caution.gif
rename to docs/zh/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-caution.gif
diff --git a/content/zh/docs/Administration/public_sys-resources/icon-danger.gif b/docs/zh/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-danger.gif
similarity index 100%
rename from content/zh/docs/Administration/public_sys-resources/icon-danger.gif
rename to docs/zh/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-danger.gif
diff --git a/content/zh/docs/Administration/public_sys-resources/icon-note.gif b/docs/zh/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-note.gif
similarity index 100%
rename from content/zh/docs/Administration/public_sys-resources/icon-note.gif
rename to docs/zh/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-note.gif
diff --git a/content/zh/docs/Administration/public_sys-resources/icon-notice.gif b/docs/zh/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-notice.gif
similarity index 100%
rename from content/zh/docs/Administration/public_sys-resources/icon-notice.gif
rename to docs/zh/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-notice.gif
diff --git a/content/zh/docs/Administration/public_sys-resources/icon-tip.gif b/docs/zh/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-tip.gif
similarity index 100%
rename from content/zh/docs/Administration/public_sys-resources/icon-tip.gif
rename to docs/zh/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-tip.gif
diff --git a/content/zh/docs/Administration/public_sys-resources/icon-warning.gif b/docs/zh/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-warning.gif
similarity index 100%
rename from content/zh/docs/Administration/public_sys-resources/icon-warning.gif
rename to docs/zh/docs/20.03_LTS/docs/Administration/public_sys-resources/icon-warning.gif
diff --git "a/content/zh/docs/Administration/\344\275\277\347\224\250DNF\347\256\241\347\220\206\350\275\257\344\273\266\345\214\205.md" "b/docs/zh/docs/20.03_LTS/docs/Administration/\344\275\277\347\224\250DNF\347\256\241\347\220\206\350\275\257\344\273\266\345\214\205.md"
similarity index 95%
rename from "content/zh/docs/Administration/\344\275\277\347\224\250DNF\347\256\241\347\220\206\350\275\257\344\273\266\345\214\205.md"
rename to "docs/zh/docs/20.03_LTS/docs/Administration/\344\275\277\347\224\250DNF\347\256\241\347\220\206\350\275\257\344\273\266\345\214\205.md"
index 91cffb82946202d9805fc1d6d2a53be00374398f..c188c85f00a982221fcea0078575219d7abac7ce 100644
--- "a/content/zh/docs/Administration/\344\275\277\347\224\250DNF\347\256\241\347\220\206\350\275\257\344\273\266\345\214\205.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Administration/\344\275\277\347\224\250DNF\347\256\241\347\220\206\350\275\257\344\273\266\345\214\205.md"
@@ -1,598 +1,598 @@
-# 使用DNF管理软件包
-
-DNF是一款Linux软件包管理工具，用于管理RPM软件包。DNF可以查询软件包信息，从指定软件库获取软件包，自动处理依赖关系以安装或卸载软件包，以及更新系统到最新可用版本。
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->-   DNF与YUM完全兼容，提供了YUM兼容的命令行以及为扩展和插件提供的API。  
->-   使用DNF需要管理员权限，本章所有命令需要在管理员权限下执行。  
-
-
-- [使用DNF管理软件包](#使用dnf管理软件包)
-    - [配置DNF](#配置dnf)
-        - [DNF配置文件](#dnf配置文件)
-        - [创建本地软件源仓库](#创建本地软件源仓库)
-        - [添加、启用和禁用软件源](#添加启用和禁用软件源)
-    - [管理软件包](#管理软件包)
-        - [搜索软件包](#搜索软件包)
-        - [列出软件包清单](#列出软件包清单)
-        - [显示RPM包信息](#显示rpm包信息)
-        - [安装RPM包](#安装rpm包)
-        - [下载软件包](#下载软件包)
-        - [删除软件包](#删除软件包)
-    - [管理软件包组](#管理软件包组)
-        - [列出软件包组清单](#列出软件包组清单)
-        - [显示软件包组信息](#显示软件包组信息)
-        - [安装软件包组](#安装软件包组)
-        - [删除软件包组](#删除软件包组)
-    - [检查并更新](#检查并更新)
-        - [检查更新](#检查更新)
-        - [升级](#升级)
-        - [更新所有的包和它们的依赖](#更新所有的包和它们的依赖)
-
-
-
-## 配置DNF
-
-
-
-### DNF配置文件
-
-DNF 的主要配置文件是 /etc/dnf/dnf.conf，该文件包含两部分：
-
--   “main”部分保存着DNF的全局设置。
-
--   “repository”部分保存着软件源的设置，可以有一个或多个“repository”。
-
-另外，在/etc/yum.repos.d 目录中保存着一个或多个repo源相关文件，它们也可以定义不同的“repository”。
-
-所以openEuler软件源的配置一般有两种方式，一种是直接配置/etc/dnf/dnf.conf文件中的“repository”部分，另外一种是在/etc/yum.repos.d目录下增加.repo文件。
-
-#### 配置main部分
-
-/etc/dnf/dnf.conf 文件包含的“main”部分，配置示例如下：
-
-```
-[main]
-gpgcheck=1
-installonly_limit=3
-clean_requirements_on_remove=True
-best=True
-```
-
-常用选项说明：
-
-**表 1**  main参数说明
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
参数

-
说明

-
cachedir

-
缓存目录，该目录用于存储RPM包和数据库文件。

-
keepcache

-
可选值是1和0，表示是否要缓存已安装成功的那些RPM包及头文件，默认值为0，即不缓存。

-
debuglevel

-
设置dnf生成的debug信息。取值范围：[0-10]，数值越大会输出越详细的debug信息。默认值为2，设置为0表示不输出debug信息。

-
clean_requirements_on_remove

-
删除在dnf remove期间不再使用的依赖项，如果软件包是通过DNF安装的，而不是通过显式用户请求安装的，则只能通过clean_requirements_on_remove删除软件包，即它是作为依赖项引入的。 默认值为True。

-
best

-
升级包时，总是尝试安装其最高版本，如果最高版本无法安装，则提示无法安装的原因并停止安装。默认值为True。

-
obsoletes

-
可选值1和0，设置是否允许更新陈旧的RPM包。默认值为1，表示允许更新。

-
gpgcheck

-
可选值1和0，设置是否进行gpg校验。默认值为1，表示需要进行校验。

-
plugins

-
可选值1和0，表示启用或禁用dnf插件。默认值为1，表示启用dnf插件。

-
installonly_limit

-
设置可以同时安装“installonlypkgs”指令列出包的数量。默认值为3，不建议降低此值。

-

-
-#### 配置repository部分
-
-repository部分允许您定义定制化的openEuler软件源仓库，各个仓库的名称不能相同，否则会引起冲突。配置repository部分有两种方式，一种是直接配置/etc/dnf/dnf.conf文件中的“repository”部分，另外一种是配置/etc/yum.repos.d目录下的.repo文件。
-
--   直接配置/etc/dnf/dnf.conf文件中的“repository”部分
-
-    下面是\[repository\]部分的一个最小配置示例：
-
-    ```
-    [repository]
-    name=repository_name
-    baseurl=repository_url
-    ```
-
-    >![](public_sys-resources/icon-note.gif) **说明：**   
-    >openEuler提供在线的镜像源，地址：[https://repo.openeuler.org/](https://repo.openeuler.org/)。以 openEuler 20.03的aarch64版本为例，baseurl可配置为[https://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/](https://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/)。  
-
-    选项说明：
-
-    **表 2**  repository参数说明
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
参数

-    
说明

-    
name=repository_name

-    
软件仓库（repository ）描述的字符串。

-    
baseurl=repository_url

-    
软件仓库（repository ）的地址。

-    
  • 使用http协议的网络位置：例如 http://path/to/repo
  • 使用ftp协议的网络位置：例如 ftp://path/to/repo
  • 本地位置：例如 file:///path/to/local/repo

-    

-
-
--   配置/etc/yum.repos.d目录下的.repo文件
-
-    openEuler提供了多种repo源供用户在线使用，各repo源含义可参考[系统安装]({{< relref "../Releasenotes/系统安装.md" >}})，以AArch64架构的OS repo源为例。使用root权限在openEuler_aarch64.repo文件中添加openEuler repo源，示例如下：
-
-    ```
-    # vi /etc/yum.repos.d/openEuler_aarch64.repo
-    ```
-
-    ```
-    [osrepo]
-    name=osrepo
-    baseurl=https://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/
-    enabled=1
-    gpgcheck=1
-    gpgkey=https://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/RPM-GPG-KEY-openEuler
-
-    ```
-
-    >![](public_sys-resources/icon-note.gif) **说明：**   
-    > - enabled为是否启用该软件源仓库，可选值为1和0。默认值为1，表示启用该软件源仓库。
-	> - gpgkey为验证签名用的公钥。
-	
-
-#### 显示当前配置
-
--   要显示当前的配置信息：
-
-    ```
-    dnf config-manager --dump
-    ```
-
--   要显示相应软件源的配置，首先查询repo id：
-
-    ```
-    dnf repolist
-    ```
-
-    然后执行如下命令，显示对应id的软件源配置，其中  _repository_  为查询得到的repo id：
-
-    ```
-    dnf config-manager --dump repository
-    ```
-
--   您也可以使用一个全局正则表达式，来显示所有匹配部分的配置：
-
-    ```
-    dnf config-manager --dump glob_expression
-    ```
-
-
-### 创建本地软件源仓库
-
-要建立一个本地软件源仓库，请按照下列步骤操作。
-
-1.  安装createrepo软件包。在root权限下执行如下命令：
-
-    ```
-    dnf install createrepo
-    ```
-
-2.  将需要的软件包复制到一个目录下，如/mnt/local\_repo/ 。
-3.  创建软件源，执行以下命令：
-
-    ```
-    createrepo --database /mnt/local_repo
-    ```
-
-
-### 添加、启用和禁用软件源
-
-本节将介绍如何通过“dnf config-manager”命令添加、启用和禁用软件源仓库。
-
-#### 添加软件源
-
-要定义一个新的软件源仓库，您可以在 /etc/dnf/dnf.conf 文件中添加“repository”部分，或者在/etc/yum.repos.d/目录下添加“.repo”文件进行说明。建议您通过添加“.repo”的方式，每个软件源都有自己对应的“.repo”文件，以下介绍该方式的操作方法。
-
-要在您的系统中添加一个这样的源，请在root权限下执行如下命令，执行完成之后会在/etc/yum.repos.d/目录下生成对应的repo文件。其中  _repository\_url_  为repo源地址，详情请参见[表2](#zh-cn_topic_0151921080_t2df9dceb0ff64b2f8db8ec5cd779792a)。
-
-```
-dnf config-manager --add-repo repository_url
-```
-
-#### 启用软件源
-
-要启用软件源，请在root权限下执行如下命令，其中  _repository_  为新增.repo文件中的repo id（可通过dnf repolist查询）：
-
-```
-dnf config-manager --set-enable repository
-```
-
-您也可以使用一个全局正则表达式，来启用所有匹配的软件源。其中  _glob\_expression_  为对应的正则表达式，用于同时匹配多个repo id：
-
-```
-dnf config-manager --set-enable glob_expression
-```
-
-#### 禁用软件源
-
-要禁用软件源，请在root权限下执行如下命令：
-
-```
-dnf config-manager --set-disable repository
-```
-
-同样的，您也可以使用一个全局正则表达式来禁用所有匹配的软件源：
-
-```
-dnf config-manager --set-disable glob_expression
-```
-
-## 管理软件包
-
-使用dnf能够让您方便的进行查询、安装、删除软件包等操作。
-
-### 搜索软件包
-
-您可以使用rpm包名称、缩写或者描述搜索需要的RPM包，使用命令如下：
-
-```
-dnf search term
-```
-
-示例如下：
-
-```
-$   dnf search httpd
-========================================== N/S matched: httpd ==========================================
-httpd.aarch64 : Apache HTTP Server
-httpd-devel.aarch64 : Development interfaces for the Apache HTTP server
-httpd-manual.noarch : Documentation for the Apache HTTP server
-httpd-tools.aarch64  : Tools for use with the Apache HTTP Server
-libmicrohttpd.aarch64  : Lightweight library for embedding a webserver in applications
-mod_auth_mellon.aarch64  : A SAML 2.0 authentication module for the Apache Httpd Server
-mod_dav_svn.aarch64  : Apache httpd module for Subversion server
-```
-
-### 列出软件包清单
-
-要列出系统中所有已安装的以及可用的RPM包信息，使用命令如下：
-
-```
-dnf list all
-```
-
-要列出系统中特定的RPM包信息，使用命令如下：
-
-```
-dnf list glob_expression...
-```
-
-示例如下：
-
-```
-$ dnf list httpd
-Available Packages
-httpd.aarch64              2.4.34-8.h5.oe1           Local
-```
-
-### 显示RPM包信息
-
-要显示一个或者多个RPM包信息，使用命令如下：
-
-```
-dnf info package_name...
-```
-
-例如搜索，命令如下：
-
-```
-$ dnf info httpd
-Available Packages
-Name        : httpd
-Version     : 2.4.34
-Release     : 8.h5.oe1
-Arch        : aarch64 
-Size        : 1.2 M
-Repo        : Local
-Summary     : Apache HTTP Server
-URL         : http://httpd.apache.org/
-License     : ASL 2.0
-Description : The Apache HTTP Server is a powerful, efficient, and extensible
-            : web server.
-```
-
-### 安装RPM包
-
-要安装一个软件包及其所有未安装的依赖，请在root权限下执行如下命令：
-
-```
-dnf install package_name
-```
-
-您也可以通过添加软件包名字同时安装多个软件包。配置文件/etc/dnf/dnf.conf添加参数strict=False，运行dnf命令参数添加\-\-setopt=strict=0。请在root权限下执行如下命令：
-
-```
-dnf install package_name package_name... --setopt=strict=0
-```
-
-示例如下：
-
-```
-# dnf install httpd
-```
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->安装RPM包过程中，若出现安装失败，可参考[安装时出现软件包冲突、文件冲突或缺少软件包导致安装失败](FAQ-54.html#安装时出现软件包冲突文件冲突或缺少软件包导致安装失败)。  
-
-### 下载软件包
-
-使用dnf下载软件包，请在root权限下输入如下命令：
-
-```
-dnf download package_name
-```
-
-如果需要同时下载未安装的依赖，则加上\-\-resolve，使用命令如下：
-
-```
-dnf download --resolve package_name
-```
-
-示例如下：
-
-```
-# dnf download --resolve httpd
-```
-
-### 删除软件包
-
-要卸载软件包以及相关的依赖软件包，请在root权限下执行如下命令：
-
-```
-dnf remove package_name...
-```
-
-示例如下：
-
-```
-# dnf remove totem
-```
-
-## 管理软件包组
-
-软件包集合是服务于一个共同的目的一组软件包，例如系统工具集等。使用dnf可以对软件包组进行安装/删除等操作，使相关操作更高效。
-
-### 列出软件包组清单
-
-使用summary参数，可以列出系统中所有已安装软件包组、可用的组，可用的环境组的数量，命令如下：
-
-```
-dnf groups summary
-```
-
-使用示例如下：
-
-```
-# dnf groups summary
-Last metadata expiration check: 0:11:56 ago on Sat 17 Aug 2019 07:45:14 PM CST.
-Available Groups: 8
-```
-
-要列出所有软件包组和它们的组ID ，命令如下：
-
-```
-dnf group list
-```
-
-使用示例如下：
-
-```
-# dnf group list
-Last metadata expiration check: 0:10:32 ago on Sat 17 Aug 2019 07:45:14 PM CST.
-Available Environment Groups:
-   Minimal Install
-   Custom Operating System
-   Server
-Available Groups:
-   Development Tools
-   Graphical Administration Tools
-   Headless Management
-   Legacy UNIX Compatibility
-   Network Servers
-   Scientific Support
-   Security Tools
-   System Tools
-
-```
-
-### 显示软件包组信息
-
-要列出包含在一个软件包组中必须安装的包和可选包，使用命令如下：
-
-```
-dnf group info glob_expression...
-```
-
-例如显示Development Tools信息，示例如下：
-
-```
-# dnf group info "Development Tools"
-Last metadata expiration check: 0:14:54 ago on Wed 05 Jun 2019 08:38:02 PM CST.
-
-Group: Development Tools
- Description: A basic development environment.
- Mandatory Packages:
-   binutils
-   glibc-devel
-   make
-   pkgconf
-   pkgconf-m4
-   pkgconf-pkg-config
-   rpm-sign
- Optional Packages:
-   expect
-```
-
-### 安装软件包组
-
-每一个软件包组都有自己的名称以及相应的ID（groupid），您可以使用软件包组名称或它的ID进行安装。
-
-要安装一个软件包组，请在root权限下执行如下命令：
-
-```
-dnf group install group_name
-```
-
-```
-dnf group install groupid
-```
-
-例如安装Development Tools相应的软件包组，命令如下：
-
-```
-# dnf group install "Development Tools" 
-```
-
-```
-# dnf group install development
-```
-
-### 删除软件包组
-
-要卸载软件包组，您可以使用软件包组名称或它的ID，在root权限下执行如下命令：
-
-```
-dnf group remove group_name
-```
-
-```
-dnf group remove groupid
-```
-
-例如删除Development Tools相应的软件包组，命令如下：
-
-```
-# dnf group remove "Development Tools" 
-```
-
-```
-# dnf group remove development
-```
-
-## 检查并更新
-
-dnf可以检查您的系统中是否有软件包需要更新。您可以通过dnf列出需要更新的软件包，并可以选择一次性全部更新或者只对指定包进行更新。
-
-### 检查更新
-
-如果您需要显示当前系统可用的更新，使用命令如下：
-
-```
-dnf check-update
-```
-
-使用实例如下：
-
-```
-# dnf check-update
-Last metadata expiration check: 0:02:10 ago on Sun 01 Sep 2019 11:28:07 PM  CST.
-
-anaconda-core.aarch64       19.31.123-1.14             updates
-anaconda-gui.aarch64        19.31.123-1.14             updates
-anaconda-tui.aarch64        19.31.123-1.14             updates
-anaconda-user-help.aarch64  19.31.123-1.14             updates
-anaconda-widgets.aarch64    19.31.123-1.14             updates
-bind-libs.aarch64           32:9.9.4-29.3              updates
-bind-libs-lite.aarch64      32:9.9.4-29.3              updates
-bind-license.noarch         32:9.9.4-29.3              updates
-bind-utils.aarch64          32:9.9.4-29.3              updates
-...
-```
-
-### 升级
-
-如果您需要升级单个软件包，在root权限下执行如下命令：
-
-```
-dnf update package_name
-```
-
-例如升级rpm包，示例如下：
-
-```
-# dnf update anaconda-gui.aarch64
-Last metadata expiration check: 0:02:10 ago on Sun 01 Sep 2019 11:30:27 PM  CST.
-Dependencies Resolved
-================================================================================
- Package                  Arch         Version              Repository     Size
-================================================================================
-Updating:
- anaconda-gui             aarch64      19.31.123-1.14       updates       461 k
- anaconda-core            aarch64      19.31.123-1.14       updates       1.4 M
- anaconda-tui             aarch64      19.31.123-1.14       updates       274 k
- anaconda-user-help       aarch64      19.31.123-1.14       updates       315 k
- anaconda-widgets         aarch64      19.31.123-1.14       updates       748 k
-
-Transaction Summary
-================================================================================
-Upgrade  5 Package
-
-Total download size: 3.1 M
-Is this ok [y/N]:
-```
-
-类似的，如果您需要升级软件包组，在root权限下执行如下命令：
-
-```
-dnf group update group_name
-```
-
-### 更新所有的包和它们的依赖
-
-要更新所有的包和它们的依赖，在root权限下执行如下命令：
-
-```
-dnf update
-```
+# 使用DNF管理软件包
+
+DNF是一款Linux软件包管理工具，用于管理RPM软件包。DNF可以查询软件包信息，从指定软件库获取软件包，自动处理依赖关系以安装或卸载软件包，以及更新系统到最新可用版本。
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>-   DNF与YUM完全兼容，提供了YUM兼容的命令行以及为扩展和插件提供的API。  
+>-   使用DNF需要管理员权限，本章所有命令需要在管理员权限下执行。  
+
+
+- [使用DNF管理软件包](#使用dnf管理软件包)
+    - [配置DNF](#配置dnf)
+        - [DNF配置文件](#dnf配置文件)
+        - [创建本地软件源仓库](#创建本地软件源仓库)
+        - [添加、启用和禁用软件源](#添加启用和禁用软件源)
+    - [管理软件包](#管理软件包)
+        - [搜索软件包](#搜索软件包)
+        - [列出软件包清单](#列出软件包清单)
+        - [显示RPM包信息](#显示rpm包信息)
+        - [安装RPM包](#安装rpm包)
+        - [下载软件包](#下载软件包)
+        - [删除软件包](#删除软件包)
+    - [管理软件包组](#管理软件包组)
+        - [列出软件包组清单](#列出软件包组清单)
+        - [显示软件包组信息](#显示软件包组信息)
+        - [安装软件包组](#安装软件包组)
+        - [删除软件包组](#删除软件包组)
+    - [检查并更新](#检查并更新)
+        - [检查更新](#检查更新)
+        - [升级](#升级)
+        - [更新所有的包和它们的依赖](#更新所有的包和它们的依赖)
+
+
+
+## 配置DNF
+
+
+
+### DNF配置文件
+
+DNF 的主要配置文件是 /etc/dnf/dnf.conf，该文件包含两部分：
+
+-   “main”部分保存着DNF的全局设置。
+
+-   “repository”部分保存着软件源的设置，可以有一个或多个“repository”。
+
+另外，在/etc/yum.repos.d 目录中保存着一个或多个repo源相关文件，它们也可以定义不同的“repository”。
+
+所以openEuler软件源的配置一般有两种方式，一种是直接配置/etc/dnf/dnf.conf文件中的“repository”部分，另外一种是在/etc/yum.repos.d目录下增加.repo文件。
+
+#### 配置main部分
+
+/etc/dnf/dnf.conf 文件包含的“main”部分，配置示例如下：
+
+```
+[main]
+gpgcheck=1
+installonly_limit=3
+clean_requirements_on_remove=True
+best=True
+```
+
+常用选项说明：
+
+**表 1**  main参数说明
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
参数

+
说明

+
cachedir

+
缓存目录，该目录用于存储RPM包和数据库文件。

+
keepcache

+
可选值是1和0，表示是否要缓存已安装成功的那些RPM包及头文件，默认值为0，即不缓存。

+
debuglevel

+
设置dnf生成的debug信息。取值范围：[0-10]，数值越大会输出越详细的debug信息。默认值为2，设置为0表示不输出debug信息。

+
clean_requirements_on_remove

+
删除在dnf remove期间不再使用的依赖项，如果软件包是通过DNF安装的，而不是通过显式用户请求安装的，则只能通过clean_requirements_on_remove删除软件包，即它是作为依赖项引入的。 默认值为True。

+
best

+
升级包时，总是尝试安装其最高版本，如果最高版本无法安装，则提示无法安装的原因并停止安装。默认值为True。

+
obsoletes

+
可选值1和0，设置是否允许更新陈旧的RPM包。默认值为1，表示允许更新。

+
gpgcheck

+
可选值1和0，设置是否进行gpg校验。默认值为1，表示需要进行校验。

+
plugins

+
可选值1和0，表示启用或禁用dnf插件。默认值为1，表示启用dnf插件。

+
installonly_limit

+
设置可以同时安装“installonlypkgs”指令列出包的数量。默认值为3，不建议降低此值。

+

+
+#### 配置repository部分
+
+repository部分允许您定义定制化的openEuler软件源仓库，各个仓库的名称不能相同，否则会引起冲突。配置repository部分有两种方式，一种是直接配置/etc/dnf/dnf.conf文件中的“repository”部分，另外一种是配置/etc/yum.repos.d目录下的.repo文件。
+
+-   直接配置/etc/dnf/dnf.conf文件中的“repository”部分
+
+    下面是\[repository\]部分的一个最小配置示例：
+
+    ```
+    [repository]
+    name=repository_name
+    baseurl=repository_url
+    ```
+
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
+    >openEuler提供在线的镜像源，地址：[https://repo.openeuler.org/](https://repo.openeuler.org/)。以 openEuler 20.03的aarch64版本为例，baseurl可配置为[https://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/](https://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/)。  
+
+    选项说明：
+
+    **表 2**  repository参数说明
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
参数

+    
说明

+    
name=repository_name

+    
软件仓库（repository ）描述的字符串。

+    
baseurl=repository_url

+    
软件仓库（repository ）的地址。

+    
  • 使用http协议的网络位置：例如 http://path/to/repo
  • 使用ftp协议的网络位置：例如 ftp://path/to/repo
  • 本地位置：例如 file:///path/to/local/repo

+    

+
+
+-   配置/etc/yum.repos.d目录下的.repo文件
+
+    openEuler提供了多种repo源供用户在线使用，各repo源含义可参考[系统安装](./../Releasenotes/系统安装.md)，以AArch64架构的OS repo源为例。使用root权限在openEuler_aarch64.repo文件中添加openEuler repo源，示例如下：
+
+    ```
+    # vi /etc/yum.repos.d/openEuler_aarch64.repo
+    ```
+
+    ```
+    [osrepo]
+    name=osrepo
+    baseurl=https://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/
+    enabled=1
+    gpgcheck=1
+    gpgkey=https://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/RPM-GPG-KEY-openEuler
+
+    ```
+
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
+    > - enabled为是否启用该软件源仓库，可选值为1和0。默认值为1，表示启用该软件源仓库。
+	> - gpgkey为验证签名用的公钥。
+	
+
+#### 显示当前配置
+
+-   要显示当前的配置信息：
+
+    ```
+    dnf config-manager --dump
+    ```
+
+-   要显示相应软件源的配置，首先查询repo id：
+
+    ```
+    dnf repolist
+    ```
+
+    然后执行如下命令，显示对应id的软件源配置，其中  _repository_  为查询得到的repo id：
+
+    ```
+    dnf config-manager --dump repository
+    ```
+
+-   您也可以使用一个全局正则表达式，来显示所有匹配部分的配置：
+
+    ```
+    dnf config-manager --dump glob_expression
+    ```
+
+
+### 创建本地软件源仓库
+
+要建立一个本地软件源仓库，请按照下列步骤操作。
+
+1.  安装createrepo软件包。在root权限下执行如下命令：
+
+    ```
+    dnf install createrepo
+    ```
+
+2.  将需要的软件包复制到一个目录下，如/mnt/local\_repo/ 。
+3.  创建软件源，执行以下命令：
+
+    ```
+    createrepo --database /mnt/local_repo
+    ```
+
+
+### 添加、启用和禁用软件源
+
+本节将介绍如何通过“dnf config-manager”命令添加、启用和禁用软件源仓库。
+
+#### 添加软件源
+
+要定义一个新的软件源仓库，您可以在 /etc/dnf/dnf.conf 文件中添加“repository”部分，或者在/etc/yum.repos.d/目录下添加“.repo”文件进行说明。建议您通过添加“.repo”的方式，每个软件源都有自己对应的“.repo”文件，以下介绍该方式的操作方法。
+
+要在您的系统中添加一个这样的源，请在root权限下执行如下命令，执行完成之后会在/etc/yum.repos.d/目录下生成对应的repo文件。其中  _repository\_url_  为repo源地址，详情请参见[表2](#zh-cn_topic_0151921080_t2df9dceb0ff64b2f8db8ec5cd779792a)。
+
+```
+dnf config-manager --add-repo repository_url
+```
+
+#### 启用软件源
+
+要启用软件源，请在root权限下执行如下命令，其中  _repository_  为新增.repo文件中的repo id（可通过dnf repolist查询）：
+
+```
+dnf config-manager --set-enable repository
+```
+
+您也可以使用一个全局正则表达式，来启用所有匹配的软件源。其中  _glob\_expression_  为对应的正则表达式，用于同时匹配多个repo id：
+
+```
+dnf config-manager --set-enable glob_expression
+```
+
+#### 禁用软件源
+
+要禁用软件源，请在root权限下执行如下命令：
+
+```
+dnf config-manager --set-disable repository
+```
+
+同样的，您也可以使用一个全局正则表达式来禁用所有匹配的软件源：
+
+```
+dnf config-manager --set-disable glob_expression
+```
+
+## 管理软件包
+
+使用dnf能够让您方便的进行查询、安装、删除软件包等操作。
+
+### 搜索软件包
+
+您可以使用rpm包名称、缩写或者描述搜索需要的RPM包，使用命令如下：
+
+```
+dnf search term
+```
+
+示例如下：
+
+```
+$   dnf search httpd
+========================================== N/S matched: httpd ==========================================
+httpd.aarch64 : Apache HTTP Server
+httpd-devel.aarch64 : Development interfaces for the Apache HTTP server
+httpd-manual.noarch : Documentation for the Apache HTTP server
+httpd-tools.aarch64  : Tools for use with the Apache HTTP Server
+libmicrohttpd.aarch64  : Lightweight library for embedding a webserver in applications
+mod_auth_mellon.aarch64  : A SAML 2.0 authentication module for the Apache Httpd Server
+mod_dav_svn.aarch64  : Apache httpd module for Subversion server
+```
+
+### 列出软件包清单
+
+要列出系统中所有已安装的以及可用的RPM包信息，使用命令如下：
+
+```
+dnf list all
+```
+
+要列出系统中特定的RPM包信息，使用命令如下：
+
+```
+dnf list glob_expression...
+```
+
+示例如下：
+
+```
+$ dnf list httpd
+Available Packages
+httpd.aarch64              2.4.34-8.h5.oe1           Local
+```
+
+### 显示RPM包信息
+
+要显示一个或者多个RPM包信息，使用命令如下：
+
+```
+dnf info package_name...
+```
+
+例如搜索，命令如下：
+
+```
+$ dnf info httpd
+Available Packages
+Name        : httpd
+Version     : 2.4.34
+Release     : 8.h5.oe1
+Arch        : aarch64 
+Size        : 1.2 M
+Repo        : Local
+Summary     : Apache HTTP Server
+URL         : http://httpd.apache.org/
+License     : ASL 2.0
+Description : The Apache HTTP Server is a powerful, efficient, and extensible
+            : web server.
+```
+
+### 安装RPM包
+
+要安装一个软件包及其所有未安装的依赖，请在root权限下执行如下命令：
+
+```
+dnf install package_name
+```
+
+您也可以通过添加软件包名字同时安装多个软件包。配置文件/etc/dnf/dnf.conf添加参数strict=False，运行dnf命令参数添加\-\-setopt=strict=0。请在root权限下执行如下命令：
+
+```
+dnf install package_name package_name... --setopt=strict=0
+```
+
+示例如下：
+
+```
+# dnf install httpd
+```
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>安装RPM包过程中，若出现安装失败，可参考[安装时出现软件包冲突、文件冲突或缺少软件包导致安装失败](./FAQ-54.html#安装时出现软件包冲突文件冲突或缺少软件包导致安装失败)。  
+
+### 下载软件包
+
+使用dnf下载软件包，请在root权限下输入如下命令：
+
+```
+dnf download package_name
+```
+
+如果需要同时下载未安装的依赖，则加上\-\-resolve，使用命令如下：
+
+```
+dnf download --resolve package_name
+```
+
+示例如下：
+
+```
+# dnf download --resolve httpd
+```
+
+### 删除软件包
+
+要卸载软件包以及相关的依赖软件包，请在root权限下执行如下命令：
+
+```
+dnf remove package_name...
+```
+
+示例如下：
+
+```
+# dnf remove totem
+```
+
+## 管理软件包组
+
+软件包集合是服务于一个共同的目的一组软件包，例如系统工具集等。使用dnf可以对软件包组进行安装/删除等操作，使相关操作更高效。
+
+### 列出软件包组清单
+
+使用summary参数，可以列出系统中所有已安装软件包组、可用的组，可用的环境组的数量，命令如下：
+
+```
+dnf groups summary
+```
+
+使用示例如下：
+
+```
+# dnf groups summary
+Last metadata expiration check: 0:11:56 ago on Sat 17 Aug 2019 07:45:14 PM CST.
+Available Groups: 8
+```
+
+要列出所有软件包组和它们的组ID ，命令如下：
+
+```
+dnf group list
+```
+
+使用示例如下：
+
+```
+# dnf group list
+Last metadata expiration check: 0:10:32 ago on Sat 17 Aug 2019 07:45:14 PM CST.
+Available Environment Groups:
+   Minimal Install
+   Custom Operating System
+   Server
+Available Groups:
+   Development Tools
+   Graphical Administration Tools
+   Headless Management
+   Legacy UNIX Compatibility
+   Network Servers
+   Scientific Support
+   Security Tools
+   System Tools
+
+```
+
+### 显示软件包组信息
+
+要列出包含在一个软件包组中必须安装的包和可选包，使用命令如下：
+
+```
+dnf group info glob_expression...
+```
+
+例如显示Development Tools信息，示例如下：
+
+```
+# dnf group info "Development Tools"
+Last metadata expiration check: 0:14:54 ago on Wed 05 Jun 2019 08:38:02 PM CST.
+
+Group: Development Tools
+ Description: A basic development environment.
+ Mandatory Packages:
+   binutils
+   glibc-devel
+   make
+   pkgconf
+   pkgconf-m4
+   pkgconf-pkg-config
+   rpm-sign
+ Optional Packages:
+   expect
+```
+
+### 安装软件包组
+
+每一个软件包组都有自己的名称以及相应的ID（groupid），您可以使用软件包组名称或它的ID进行安装。
+
+要安装一个软件包组，请在root权限下执行如下命令：
+
+```
+dnf group install group_name
+```
+
+```
+dnf group install groupid
+```
+
+例如安装Development Tools相应的软件包组，命令如下：
+
+```
+# dnf group install "Development Tools" 
+```
+
+```
+# dnf group install development
+```
+
+### 删除软件包组
+
+要卸载软件包组，您可以使用软件包组名称或它的ID，在root权限下执行如下命令：
+
+```
+dnf group remove group_name
+```
+
+```
+dnf group remove groupid
+```
+
+例如删除Development Tools相应的软件包组，命令如下：
+
+```
+# dnf group remove "Development Tools" 
+```
+
+```
+# dnf group remove development
+```
+
+## 检查并更新
+
+dnf可以检查您的系统中是否有软件包需要更新。您可以通过dnf列出需要更新的软件包，并可以选择一次性全部更新或者只对指定包进行更新。
+
+### 检查更新
+
+如果您需要显示当前系统可用的更新，使用命令如下：
+
+```
+dnf check-update
+```
+
+使用实例如下：
+
+```
+# dnf check-update
+Last metadata expiration check: 0:02:10 ago on Sun 01 Sep 2019 11:28:07 PM  CST.
+
+anaconda-core.aarch64       19.31.123-1.14             updates
+anaconda-gui.aarch64        19.31.123-1.14             updates
+anaconda-tui.aarch64        19.31.123-1.14             updates
+anaconda-user-help.aarch64  19.31.123-1.14             updates
+anaconda-widgets.aarch64    19.31.123-1.14             updates
+bind-libs.aarch64           32:9.9.4-29.3              updates
+bind-libs-lite.aarch64      32:9.9.4-29.3              updates
+bind-license.noarch         32:9.9.4-29.3              updates
+bind-utils.aarch64          32:9.9.4-29.3              updates
+...
+```
+
+### 升级
+
+如果您需要升级单个软件包，在root权限下执行如下命令：
+
+```
+dnf update package_name
+```
+
+例如升级rpm包，示例如下：
+
+```
+# dnf update anaconda-gui.aarch64
+Last metadata expiration check: 0:02:10 ago on Sun 01 Sep 2019 11:30:27 PM  CST.
+Dependencies Resolved
+================================================================================
+ Package                  Arch         Version              Repository     Size
+================================================================================
+Updating:
+ anaconda-gui             aarch64      19.31.123-1.14       updates       461 k
+ anaconda-core            aarch64      19.31.123-1.14       updates       1.4 M
+ anaconda-tui             aarch64      19.31.123-1.14       updates       274 k
+ anaconda-user-help       aarch64      19.31.123-1.14       updates       315 k
+ anaconda-widgets         aarch64      19.31.123-1.14       updates       748 k
+
+Transaction Summary
+================================================================================
+Upgrade  5 Package
+
+Total download size: 3.1 M
+Is this ok [y/N]:
+```
+
+类似的，如果您需要升级软件包组，在root权限下执行如下命令：
+
+```
+dnf group update group_name
+```
+
+### 更新所有的包和它们的依赖
+
+要更新所有的包和它们的依赖，在root权限下执行如下命令：
+
+```
+dnf update
+```
diff --git "a/content/zh/docs/Administration/\344\275\277\347\224\250KAE\345\212\240\351\200\237\345\274\225\346\223\216.md" "b/docs/zh/docs/20.03_LTS/docs/Administration/\344\275\277\347\224\250KAE\345\212\240\351\200\237\345\274\225\346\223\216.md"
similarity index 97%
rename from "content/zh/docs/Administration/\344\275\277\347\224\250KAE\345\212\240\351\200\237\345\274\225\346\223\216.md"
rename to "docs/zh/docs/20.03_LTS/docs/Administration/\344\275\277\347\224\250KAE\345\212\240\351\200\237\345\274\225\346\223\216.md"
index da7e0e65396e5d3b6ec0186f2d591df1fd2e27ff..5a7894aa18b1e16fea8509629a328ed1b197ae15 100644
--- "a/content/zh/docs/Administration/\344\275\277\347\224\250KAE\345\212\240\351\200\237\345\274\225\346\223\216.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Administration/\344\275\277\347\224\250KAE\345\212\240\351\200\237\345\274\225\346\223\216.md"
@@ -80,7 +80,7 @@ KAE加速引擎主要有以下应用场景，如[表1](#table11915824163418)所
 
 -   TaiShan 200服务器，开启加速引擎功能
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >-   需要导入加速器许可证，具体操作请参考《[TaiShan 机架服务器 iBMC \(V500及以上\) 用户指南](https://support.huawei.com/enterprise/zh/doc/EDOC1100121687)》中“许可证管理”章节。  
 >-   物理机场景使用加速器需要关闭SMMU，具体操作请参考《[TaiShan 200服务器BIOS参数参考](https://support.huawei.com/enterprise/zh/doc/EDOC1100088653)》。  
 
@@ -141,7 +141,7 @@ KAE加速引擎主要有以下应用场景，如[表1](#table11915824163418)所
 3.  使用SSH远程登录工具，将所有加速引擎软件包拷贝到已建好的目录下。
 4.  在存放加速引擎软件包目录下，使用rpm -ivh命令安装加速器引擎软件包。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >由于libkae包的安装依赖libwd包，所以libwd的安装必须先于libkae。  
 
     ```
@@ -286,7 +286,7 @@ hisi_zip-1.2.10-4.oe1.aarch64
     ```
 
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >使用KAE引擎加速后签名性能从724.1 sign/s提升到2819sign/s。  
 
 -   使用OpenSSL的软件算法测试异步RSA性能。
@@ -308,7 +308,7 @@ hisi_zip-1.2.10-4.oe1.aarch64
     ```
 
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >使用KAE引擎加速后异步RSA签名性能从735.7 sign/s提升到 54384.1sign/s。  
 
 -   使用OpenSSL的软件算法测试SM4 CBC模式性能。
@@ -336,7 +336,7 @@ hisi_zip-1.2.10-4.oe1.aarch64
     ```
 
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >使用KAE加速后SM4 CBC模式在输入数据块大小为8M时，从82312.53k/s提升到383317.33k/s。  
 
 -   使用OpenSSL的软件算法测试SM3模式性能。
@@ -363,7 +363,7 @@ hisi_zip-1.2.10-4.oe1.aarch64
     ```
 
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >使用KAE加速后SM3算法在输入数据块大小为8M时，从52428.80 k/s提升到668292.44k/s。  
 
 -   使用OpenSSL软件算法测试AES算法CBC模式异步性能。
@@ -392,7 +392,7 @@ hisi_zip-1.2.10-4.oe1.aarch64
     ```
 
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >-   AES仅支持数据长度为256KB及以下场景的异步使用。  
 >-   使用KAE加速后AES算法在输入数据块为100K大小时，从1123328.00k/s提升到3996774.40 k/s 。  
 
@@ -411,15 +411,15 @@ hisi_zip-1.2.10-4.oe1.aarch64
 
     命令和信息回显如下所示。
 
-    ![](figures/zh-cn_image_0231143189.png)
+    ![](./figures/zh-cn_image_0231143189.png)
 
-    ![](figures/zh-cn_image_0231143191.png)
+    ![](./figures/zh-cn_image_0231143191.png)
 
 5.  使用rpm -qa  命令查询是否升级成功。确认查询到的版本是最新的升级后版本。
 
-    ![](figures/zh-cn_image_0231143193.png)
+    ![](./figures/zh-cn_image_0231143193.png)
 
-    ![](figures/zh-cn_image_0231143195.png)
+    ![](./figures/zh-cn_image_0231143195.png)
 
 6.  重启系统或通过命令行手动卸载旧版本驱动，然后加载新版本驱动，并查看是否加载成功
 
@@ -466,16 +466,16 @@ hisi_zip-1.2.10-4.oe1.aarch64
 
 3.  通过rpm -e 命令卸载加速引擎软件包。示例如下。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >由于存在依赖关系，卸载libwd前须先卸载libkae引擎软件包。  
 
-    ![](figures/zh-cn_image_0231143196.png)
+    ![](./figures/zh-cn_image_0231143196.png)
 
-    ![](figures/zh-cn_image_0231143197.png)
+    ![](./figures/zh-cn_image_0231143197.png)
 
 4.  使用rpm -qa |grep 软件包名命令查询是否卸载成功。
 
-    ![](figures/zh-cn_image_0231143198.png)
+    ![](./figures/zh-cn_image_0231143198.png)
 
 
 ## 日志查询
@@ -519,7 +519,7 @@ hisi_zip-1.2.10-4.oe1.aarch64
 
 ## 加速引擎的应用
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >如果用户未购买引擎许可证，建议用户不要通过kae引擎调用相应算法，否则可能会影响openssl加密算法的性能。  
 ### KAE引擎使用示例代码
 
diff --git "a/content/zh/docs/Administration/\344\275\277\347\224\250LVM\347\256\241\347\220\206\347\241\254\347\233\230.md" "b/docs/zh/docs/20.03_LTS/docs/Administration/\344\275\277\347\224\250LVM\347\256\241\347\220\206\347\241\254\347\233\230.md"
similarity index 99%
rename from "content/zh/docs/Administration/\344\275\277\347\224\250LVM\347\256\241\347\220\206\347\241\254\347\233\230.md"
rename to "docs/zh/docs/20.03_LTS/docs/Administration/\344\275\277\347\224\250LVM\347\256\241\347\220\206\347\241\254\347\233\230.md"
index 3add822aacd8b9d070e747d11a9de35cb7c464bc..08be596ebd0403fabd21c2642755cad5e8c22ec0 100644
--- "a/content/zh/docs/Administration/\344\275\277\347\224\250LVM\347\256\241\347\220\206\347\241\254\347\233\230.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Administration/\344\275\277\347\224\250LVM\347\256\241\347\220\206\347\241\254\347\233\230.md"
@@ -61,10 +61,10 @@ LVM是逻辑卷管理（Logical Volume Manager）的简称，它是Linux环境
 
 ## 安装
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >openEuler操作系统默认已安装LVM。可通过**rpm -qa | grep lvm2**命令查询，若打印信息中包含“lvm2”信息，则表示已安装LVM，可跳过本章节内；若无任何打印信息，则表示未安装，可参考本章节内容进行安装。  
 
-1.  配置本地yum源，详细信息请参考[搭建repo服务器](搭建repo服务器.html)。
+1.  配置本地yum源，详细信息请参考[搭建repo服务器](./搭建repo服务器.html)。
 2.  清除缓存。
 
     ```
@@ -372,7 +372,7 @@ lvdisplay [option] [lvname]
     
 -   lvname：指定要显示属性的逻辑卷对应的设备文件。如果省略，则显示所有的逻辑卷属性。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >逻辑卷对应的设备文件保存在卷组目录下，例如：在卷组vg1上创建一个逻辑卷lv1，则此逻辑卷对应的设备文件为/dev/vg1/lv1。  
 
 
diff --git "a/content/zh/docs/Administration/\345\237\272\347\241\200\351\205\215\347\275\256.md" "b/docs/zh/docs/20.03_LTS/docs/Administration/\345\237\272\347\241\200\351\205\215\347\275\256.md"
similarity index 96%
rename from "content/zh/docs/Administration/\345\237\272\347\241\200\351\205\215\347\275\256.md"
rename to "docs/zh/docs/20.03_LTS/docs/Administration/\345\237\272\347\241\200\351\205\215\347\275\256.md"
index 316b2356e1af95e44845e63a785082a96d0ab422..b901d3b20b513087b23e67edfa8d9849cce8a1ac 100644
--- "a/content/zh/docs/Administration/\345\237\272\347\241\200\351\205\215\347\275\256.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Administration/\345\237\272\347\241\200\351\205\215\347\275\256.md"
@@ -1,470 +1,470 @@
-# 基础配置
-
-
-- [基础配置](#基础配置)
-    - [设置语言环境](#设置语言环境)
-        - [显示当前语言环境状态](#显示当前语言环境状态)
-        - [列出可用的语言环境](#列出可用的语言环境)
-        - [设置语言环境](#设置语言环境-1)
-    - [设置键盘](#设置键盘)
-        - [显示当前设置](#显示当前设置)
-        - [列出可用的键盘布局](#列出可用的键盘布局)
-        - [设置键盘布局](#设置键盘布局)
-    - [设置日期和时间](#设置日期和时间)
-        - [使用timedatectl命令设置](#使用timedatectl命令设置)
-        - [使用date命令设置](#使用date命令设置)
-        - [使用hwclock命令设置](#使用hwclock命令设置)
-    - [设置kdump](#设置kdump)
-        - [设置kdump预留内存](#设置kdump预留内存)
-        - [预留内存推荐值](#预留内存推荐值)
-        - [禁用网络相关驱动](#禁用网络相关驱动)
-
-
-
-
-## 设置语言环境
-
-您可以通过localectl修改系统的语言环境，对应的参数设置保存在/etc/locale.conf文件中。这些参数会在系统启动过程中被systemd的守护进程读取。
-
-### 显示当前语言环境状态
-
-显示当前语言环境，命令如下：
-
-```
-$ localectl status
-```
-
-例如显示系统当前的设置，命令和输出如下：
-
-```
-$ localectl status
-   System Locale: LANG=zh_CN.UTF-8
-       VC Keymap: cn
-      X11 Layout: cn
-```
-
-### 列出可用的语言环境
-
-显示当前可用的语言环境，命令如下：
-
-```
-$ localectl list-locales
-```
-
-例如显示当前系统中所有可用的中文环境，命令和输出如下：
-
-```
-$ localectl list-locales | grep zh
-zh_CN.UTF-8
-```
-
-### 设置语言环境
-
-要设置语言环境，在root权限下执行如下命令，其中  _locale_  是您要设置的语言类型，取值范围可通过**localectl list-locales**获取，请根据实际情况修改。
-
-```
-# localectl set-locale LANG=locale
-```
-
-例如设置为简体中文语言环境，在root权限下执行如下命令：
-
-```
-# localectl set-locale LANG=zh_CN.UTF-8
-```
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->修改后需要重新登录或者在root权限下执行`source /etc/locale.conf`命令刷新配置文件，使修改生效。  
-
-
-## 设置键盘
-
-您可以通过localectl修改系统的键盘设置，对应的参数设置保存在/etc/locale.conf文件中。这些参数，会在系统启动的早期被systemd的守护进程读取。
-
-### 显示当前设置
-
-显示当前键盘设置，命令如下：
-
-```
-$ localectl status
-```
-
-例如显示系统当前的设置，命令和输出如下：
-
-```
-$ localectl status
-   System Locale: LANG=zh_CN.UTF-8
-       VC Keymap: cn
-      X11 Layout: cn
-```
-
-### 列出可用的键盘布局
-
-显示当前可用的键盘布局，命令如下：
-
-```
-$ localectl list-keymaps
-```
-
-例如显示系统当前的中文键盘布局，命令和输出如下：
-
-```
-$ localectl list-keymaps | grep cn
-cn
-```
-
-### 设置键盘布局
-
-设置键盘布局，在root权限下执行如下命令，其中  _map_  是您想要设置的键盘类型，取值范围可通过**localectl list-keymaps**获取，请根据实际情况修改：
-
-```
-# localectl set-keymap map
-```
-
-此时设置的键盘布局同样也会应用到图形界面中。
-
-设置完成后，查看当前状态：
-
-```
-$ localectl status
-   System Locale: LANG=zh_CN.UTF-8
-       VC Keymap: cn
-      X11 Layout: us
-```
-
-## 设置日期和时间
-
-本节介绍如何通过timedatectl、date、hwclock命令来设置系统的日期、时间和时区等。
-
-
-
-### 使用timedatectl命令设置
-
-#### 显示日期和时间
-
-显示当前的日期和时间，命令如下：
-
-```
-$ timedatectl
-```
-
-例如显示系统当前的日期和时间，命令和输出如下：
-
-```
-$ timedatectl
-               Local time: Mon 2019-09-30 04:05:00 EDT
-           Universal time: Mon 2019-09-30 08:05:00 UTC
-                 RTC time: Mon 2019-09-30 08:05:00
-                Time zone: America/New_York (EDT, -0400)
-System clock synchronized: no
-              NTP service: inactive
-          RTC in local TZ: no
-```
-
-#### 通过远程服务器进行时间同步
-
-您可以启用NTP远程服务器进行系统时钟的自动同步。是否启用NTP，可在root权限下执行如下命令进行设置。其中  _boolean_  可取值yes和no，分别表示启用和不启用NTP进行系统时钟自动同步，请根据实际情况修改。
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->若启用了NTP远程服务器进行系统时钟自动同步，则不能手动修改日期和时间。若需要手动修改日期或时间，则需确保已经关闭NTP系统时钟自动同步。可执行**timedatectl set-ntp**  no命令进行关闭。  
-
-```
-# timedatectl set-ntp boolean
-```
-
-例如开启自动远程时间同步，命令如下：
-
-```
-# timedatectl set-ntp yes
-```
-
-#### 修改日期
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->修改日期前，请确保已经关闭NTP系统时钟自动同步。  
-
-修改当前的日期，在root权限下执行如下命令，其中  _YYYY_  代表年份，_MM_  代表月份，_DD_  代表某天，请根据实际情况修改：
-
-```
-# timedatectl set-time YYYY-MM-DD
-```
-
-例如修改当前的日期为2019年8月14号，命令如下：
-
-```
-# timedatectl set-time '2019-08-14'
-```
-
-#### 修改时间
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->修改时间前，请确保已经关闭NTP系统时钟自动同步。  
-
-修改当前的时间，在root权限下执行如下命令，其中  _HH_  代表小时，_MM_  代表分钟，_SS_  代表秒，请根据实际情况修改：
-
-```
-# timedatectl set-time HH:MM:SS
-```
-
-例如修改当前的时间为15点57分24秒，命令如下：
-
-```
-# timedatectl set-time 15:57:24
-```
-
-#### 修改时区
-
-显示当前可用时区，命令如下：
-
-```
-$ timedatectl list-timezones
-```
-
-要修改当前的时区，在root权限下执行如下命令，其中  _time\_zone_  是您想要设置的时区，请根据实际情况修改：
-
-```
-# timedatectl set-timezone time_zone
-```
-
-例如修改当前的时区，首先查询所在地域的可用时区，此处以Asia为例：
-
-```
-# timedatectl list-timezones | grep Asia
-Asia/Aden
-Asia/Almaty
-Asia/Amman
-Asia/Anadyr
-Asia/Aqtau
-Asia/Aqtobe
-Asia/Ashgabat
-Asia/Baghdad
-Asia/Bahrain
-……
-
-Asia/Seoul
-Asia/Shanghai
-Asia/Singapore
-Asia/Srednekolymsk
-Asia/Taipei
-Asia/Tashkent
-Asia/Tbilisi
-Asia/Tehran
-Asia/Thimphu
-Asia/Tokyo
-```
-
-然后修改当前的时区为“Asia/Shanghai”，命令如下：
-
-```
-# timedatectl set-timezone Asia/Shanghai
-```
-
-### 使用date命令设置
-
-#### 显示当前的日期和时间
-
-显示当前的日期和时间，命令如下：
-
-```
-$ date
-```
-
-默认情况下，date命令显示本地时间。要显示UTC时间，添加\-\-utc或-u参数：
-
-```
-$ date --utc
-```
-
-要自定义对应的输出信息格式，添加 +"format" 参数：
-
-```
-$ date +"format"
-```
-
-**表 1**  参数说明
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
格式参数

-
说明

-
%H

-
小时以HH格式（例如 17）。

-
%M

-
分钟以MM格式（例如 37）。

-
%S

-
秒以SS格式（例如 25）。

-
%d

-
日期以DD格式（例如 15）。

-
%m

-
月份以MM格式（例如 07）。

-
%Y

-
年份以YYYY格式（例如 2019）。

-
%Z

-
时区缩写（例如CEST）。

-
%F

-
日期整体格式为YYYY-MM-DD（例如 2019-7-15），等同%Y-%m-%d。

-
%T

-
时间整体格式为HH:MM:SS（例如 18:30:25），等同%H:%M:%S。

-

-
-实际使用示例如下：
-
--   显示当前的日期和本地时间。
-
-    ```
-    $ date 
-    2019年 08月 17日 星期六 17:26:34 CST
-    ```
-
--   显示当前的日期和UTC时间。
-
-    ```
-    $ date --utc
-    2019年 08月 17日 星期六 09:26:18 UTC
-    ```
-
--   自定义date命令的输出。
-
-    ```
-    $ date +"%Y-%m-%d %H:%M"
-    2019-08-17 17:24
-    ```
-
-
-#### 修改时间
-
-要修改当前的时间，添加\-\-set或者-s参数。在root权限下执行如下命令，其中  _HH_  代表小时，_MM_  代表分钟，_SS_  代表秒，请根据实际情况修改：
-
-```
-# date --set HH:MM:SS
-```
-
-默认情况下， date命令设置本地时间。要设置UTC时间，添加\-\-utc或-u参数：
-
-```
-# date --set HH:MM:SS --utc
-```
-
-例如修改当前的时间为23点26分00秒，在root权限下执行如下命令：
-
-```
-# date --set 23:26:00
-```
-
-#### 修改日期
-
-修改当前的日期，添加\-\-set或者-s参数。在root权限下执行如下命令，其中  _YYYY_  代表年份，_MM_  代表月份，_DD_  代表某天，请根据实际情况修改：
-
-```
-# date --set YYYY-MM-DD
-```
-
-例如修改当前的日期为2019年11月2日，命令如下：
-
-```
-# date --set 2019-11-02
-```
-
-### 使用hwclock命令设置
-
-可以使用 hwclock 命令设置硬件时钟RTC \(Real Time Clock\) 。
-
-#### 硬件时钟和系统时钟
-
-Linux 将时钟分为：
-
--   系统时钟 \(System Clock\) ：当前Linux Kernel中的时钟。
--   硬件时钟 RTC：主板上由电池供电的主板硬件时钟，该时钟可以在BIOS的 "Standard BIOS Feature" 项中进行设置。
-
-当Linux启动时，会读取硬件时钟，并根据硬件时间来设置系统时间。
-
-#### 显示日期和时间
-
-显示当前硬件的日期和时间，在root权限下执行如下命令：
-
-```
-# hwclock
-```
-
-例如显示当前硬件的日期和时间，命令和输出如下：
-
-```
-# hwclock
-2019-08-26 10:18:42.528948+08:00
-```
-
-#### 设置日期和时间
-
-修改当前硬件的日期和时间，在root权限下执行如下命令，其中  _dd_  表示日，_mm_  表示月份，_yyyy_  表示年份，_HH_  表示小时，_MM_  表示分钟，请根据实际情况修改：
-
-```
-# hwclock --set --date "dd mm yyyy HH:MM"
-```
-
-例如修改当前的时间为2019年10月21日21点17分，命令如下：
-
-```
-# hwclock --set --date "21 Oct 2019 21:17" --utc
-```
-
-## 设置kdump
-本节介绍如何设置kdump预留内存及kdump配置文件参数修改。
-
-
-
-### 设置kdump预留内存
-#### 预留内存参数格式
-
-kdump预留内存参数必须添加到内核启动参数中，配置文件为/boot/efi/EFI/openEuler/grub.cfg，openEuler发布版本中默认已经添加，可以根据实际使用情况调整。添加和修改启动参数后，重启系统生效。kdump预留内存参数格式如下：
-
-| 内核启动参数             | 描述                                        | 默认值           | 备注                                                         |
-|--------------------|-------------------------------------------|---------------|------------------------------------------------------------|
-| crashkernel=x      | 在4G以下的物理内存预留x大小的内存给kdump使用。               | x86版本默认配置512M | 该配置方法只在4G以下内存预留，必须保证4G以下连续可用内存足够预留。                        |
-| crashkernel=x@y    | 在y起始地址预留x大小的内存给kdump使用。                   | 未使用           | 需要确保y起始地址的x大小的内存未被其他模块预留。                                  |
-| crashkernel=x,high | 在4G以下的物理内存中预留256M内存，在4G以上预留x大小内存给kdump使用。 | arm64版本默认配置1024M,high           | 需要确保4G以下有256M连续可用的物理内存，4G以上有连续的x大小的连续物理内存。实际预留内存大小为256M+x。 |
-| crashkernel=x,low crashkernel=y,high | 在4G以下的物理内存中预留x大小，在4G以上预留y大小内存给kdump使用。                                          | 未使用              | 需要确保4G以下有连续的x大小物理内存，4G以上有连续的y大小物理内存。                                                           |
-
-
-### 预留内存推荐值
-| 推荐方案 | 预留参数                   | 参数说明                                         |
-|------|------------------------|----------------------------------------------|
-| 通用方案 | crashkernel=2048M,high | 4G以下预留256M，4G以上预留2048M内存给kdump使用。共256+2048M。 |
-| 经济方案 | crashkernel=1024M,high | 4G以下预留256M，4G以上预留1024M内存给kdump使用。共256+1024M。 推荐系统512G内存以内的场景，并不使用网络转储kdump文件。对于虚拟机场景，可以适当减少内存预留值，推荐虚拟机设置为crashkernel=512M或者crashkernel=256M,high |
->![](public_sys-resources/icon-note.gif) **说明：**   
->不通过网络转储kdump文件时，需要设置kdump文件系统不打包网络相关驱动。网络驱动加载需要申请较大内存，可能导致预留内存不足，kdump失败。因此建议禁用网络相关驱动。
-
-
-### 禁用网络相关驱动
-kdump配置文件（/etc/kdump.conf）中，dracut参数可以设置裁剪的驱动模块，可以将网络驱动配置到裁剪驱动列表中，让kdump文件系统中不加载该驱动，修改配置文件后，重启kdump服务生效。dracut参数配置如下所示：
-
-`dracut_args --omit-drivers "mdio-gpi usb_8dev et1011c rt2x00usb bcm-phy-lib mac80211_hwsim rtl8723be rndis_host hns3_cae amd vrf rtl8192cu mt76x02-lib int51x1 ppp_deflate team_mode_loadbalance smsc911x aweth bonding mwifiex_usb hnae dnet rt2x00pci vaser_pci hdlc_ppp marvell rtl8xxxu mlxsw_i2c ath9k_htc rtl8150 smc91x cortina at803x rockchip cxgb4 spi_ks8995 mt76x2u smsc9420 mdio-cavium bnxt_en ch9200 dummy macsec ice mt7601u rtl8188ee ixgbevf net1080 liquidio_vf be2net mlxsw_switchx2 gl620a xilinx_gmii2rgmii ppp_generic rtl8192de sja1000_platform ath10k_core cc770_platform realte igb c_can_platform c_can ethoc dm9601 smsc95xx lg-vl600 ifb enic ath9 mdio-octeon ppp_mppe ath10k_pci cc770 team_mode_activebackup marvell10g hinic rt2x00lib mlx4_en iavf broadcom igc c_can_pci alx rtl8192se rtl8723ae microchip lan78xx atl1c rtl8192c-common almia ax88179_178a qed netxen_nic brcmsmac rt2800usb e1000 qla3xxx mdio-bitbang qsemi mdio-mscc-miim plx_pci ipvlan r8152 cx82310_eth slhc mt76x02-usb ems_pci xen-netfront usbnet pppoe mlxsw_minimal mlxsw_spectrum cdc_ncm rt2800lib rtl_usb hnae3 ath9k_common ath9k_hw catc mt76 hns_enet_drv ppp_async huawei_cdc_ncm i40e rtl8192ce dl2 qmi_wwan mii peak_usb plusb can-dev slcan amd-xgbe team_mode_roundrobin ste10Xp thunder_xcv pptp thunder_bgx ixgbe davicom icplus tap tun smsc75xx smsc dlci hns_dsaf mlxsw_core rt2800mmi softing uPD60620 vaser_usb dp83867 brcmfmac mwifiex_pcie mlx4_core micrel team macvlan bnx2 virtio_net rtl_pci zaurus hns_mdi libcxgb hv_netvsc nicvf mt76x0u teranetics mlxfw cdc_eem qcom-emac pppox mt76-usb sierra_net i40evf bcm87xx mwifiex pegasus rt2x00mmi sja1000 ena hclgevf cnic cxgb4vf ppp_synctty iwlmvm team_mode_broadcast vxlan vsockmon hdlc_cisc rtl8723-common bsd_comp fakelb dp83822 dp83tc811 cicada fm10 8139t sfc hs geneve hclge xgene-enet-v2 cdc_mbim hdlc asix netdevsim rt2800pci team_mode_random lxt ems_usb mlxsw_pci sr9700 mdio-thunder mlxsw_switchib macvtap atlantic cdc_ether mcs7830 nicpf mdi peak_pci atl1e cdc_subset ipvtap btcoexist mt76x0-common veth slip iwldvm bcm7xxx vitesse netconsole epic100 myri10ge r8169 qede microchip_t1 liquidi bnx2x brcmutil mwifiex_sdi mlx5_core rtlwifi vmxnet3 nlmon hns3 hdlc_raw esd_usb2 atl2 mt76x2-common iwlwifi mdio-bcm-unimac national ath rtwpci rtw88 nfp rtl8821ae fjes thunderbolt-net 8139cp atl1 mscc vcan dp83848 dp83640 hdlc_fr e1000e ipheth net_failover aquantia rtl8192ee igbvf rocker intel-xway tg3" --omit "ramdisk network ifcfg qemu-net" --install "chmod" --nofscks`
+# 基础配置
+
+
+- [基础配置](#基础配置)
+    - [设置语言环境](#设置语言环境)
+        - [显示当前语言环境状态](#显示当前语言环境状态)
+        - [列出可用的语言环境](#列出可用的语言环境)
+        - [设置语言环境](#设置语言环境-1)
+    - [设置键盘](#设置键盘)
+        - [显示当前设置](#显示当前设置)
+        - [列出可用的键盘布局](#列出可用的键盘布局)
+        - [设置键盘布局](#设置键盘布局)
+    - [设置日期和时间](#设置日期和时间)
+        - [使用timedatectl命令设置](#使用timedatectl命令设置)
+        - [使用date命令设置](#使用date命令设置)
+        - [使用hwclock命令设置](#使用hwclock命令设置)
+    - [设置kdump](#设置kdump)
+        - [设置kdump预留内存](#设置kdump预留内存)
+        - [预留内存推荐值](#预留内存推荐值)
+        - [禁用网络相关驱动](#禁用网络相关驱动)
+
+
+
+
+## 设置语言环境
+
+您可以通过localectl修改系统的语言环境，对应的参数设置保存在/etc/locale.conf文件中。这些参数会在系统启动过程中被systemd的守护进程读取。
+
+### 显示当前语言环境状态
+
+显示当前语言环境，命令如下：
+
+```
+$ localectl status
+```
+
+例如显示系统当前的设置，命令和输出如下：
+
+```
+$ localectl status
+   System Locale: LANG=zh_CN.UTF-8
+       VC Keymap: cn
+      X11 Layout: cn
+```
+
+### 列出可用的语言环境
+
+显示当前可用的语言环境，命令如下：
+
+```
+$ localectl list-locales
+```
+
+例如显示当前系统中所有可用的中文环境，命令和输出如下：
+
+```
+$ localectl list-locales | grep zh
+zh_CN.UTF-8
+```
+
+### 设置语言环境
+
+要设置语言环境，在root权限下执行如下命令，其中  _locale_  是您要设置的语言类型，取值范围可通过**localectl list-locales**获取，请根据实际情况修改。
+
+```
+# localectl set-locale LANG=locale
+```
+
+例如设置为简体中文语言环境，在root权限下执行如下命令：
+
+```
+# localectl set-locale LANG=zh_CN.UTF-8
+```
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>修改后需要重新登录或者在root权限下执行`source /etc/locale.conf`命令刷新配置文件，使修改生效。  
+
+
+## 设置键盘
+
+您可以通过localectl修改系统的键盘设置，对应的参数设置保存在/etc/locale.conf文件中。这些参数，会在系统启动的早期被systemd的守护进程读取。
+
+### 显示当前设置
+
+显示当前键盘设置，命令如下：
+
+```
+$ localectl status
+```
+
+例如显示系统当前的设置，命令和输出如下：
+
+```
+$ localectl status
+   System Locale: LANG=zh_CN.UTF-8
+       VC Keymap: cn
+      X11 Layout: cn
+```
+
+### 列出可用的键盘布局
+
+显示当前可用的键盘布局，命令如下：
+
+```
+$ localectl list-keymaps
+```
+
+例如显示系统当前的中文键盘布局，命令和输出如下：
+
+```
+$ localectl list-keymaps | grep cn
+cn
+```
+
+### 设置键盘布局
+
+设置键盘布局，在root权限下执行如下命令，其中  _map_  是您想要设置的键盘类型，取值范围可通过**localectl list-keymaps**获取，请根据实际情况修改：
+
+```
+# localectl set-keymap map
+```
+
+此时设置的键盘布局同样也会应用到图形界面中。
+
+设置完成后，查看当前状态：
+
+```
+$ localectl status
+   System Locale: LANG=zh_CN.UTF-8
+       VC Keymap: cn
+      X11 Layout: us
+```
+
+## 设置日期和时间
+
+本节介绍如何通过timedatectl、date、hwclock命令来设置系统的日期、时间和时区等。
+
+
+
+### 使用timedatectl命令设置
+
+#### 显示日期和时间
+
+显示当前的日期和时间，命令如下：
+
+```
+$ timedatectl
+```
+
+例如显示系统当前的日期和时间，命令和输出如下：
+
+```
+$ timedatectl
+               Local time: Mon 2019-09-30 04:05:00 EDT
+           Universal time: Mon 2019-09-30 08:05:00 UTC
+                 RTC time: Mon 2019-09-30 08:05:00
+                Time zone: America/New_York (EDT, -0400)
+System clock synchronized: no
+              NTP service: inactive
+          RTC in local TZ: no
+```
+
+#### 通过远程服务器进行时间同步
+
+您可以启用NTP远程服务器进行系统时钟的自动同步。是否启用NTP，可在root权限下执行如下命令进行设置。其中  _boolean_  可取值yes和no，分别表示启用和不启用NTP进行系统时钟自动同步，请根据实际情况修改。
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>若启用了NTP远程服务器进行系统时钟自动同步，则不能手动修改日期和时间。若需要手动修改日期或时间，则需确保已经关闭NTP系统时钟自动同步。可执行**timedatectl set-ntp**  no命令进行关闭。  
+
+```
+# timedatectl set-ntp boolean
+```
+
+例如开启自动远程时间同步，命令如下：
+
+```
+# timedatectl set-ntp yes
+```
+
+#### 修改日期
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>修改日期前，请确保已经关闭NTP系统时钟自动同步。  
+
+修改当前的日期，在root权限下执行如下命令，其中  _YYYY_  代表年份，_MM_  代表月份，_DD_  代表某天，请根据实际情况修改：
+
+```
+# timedatectl set-time YYYY-MM-DD
+```
+
+例如修改当前的日期为2019年8月14号，命令如下：
+
+```
+# timedatectl set-time '2019-08-14'
+```
+
+#### 修改时间
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>修改时间前，请确保已经关闭NTP系统时钟自动同步。  
+
+修改当前的时间，在root权限下执行如下命令，其中  _HH_  代表小时，_MM_  代表分钟，_SS_  代表秒，请根据实际情况修改：
+
+```
+# timedatectl set-time HH:MM:SS
+```
+
+例如修改当前的时间为15点57分24秒，命令如下：
+
+```
+# timedatectl set-time 15:57:24
+```
+
+#### 修改时区
+
+显示当前可用时区，命令如下：
+
+```
+$ timedatectl list-timezones
+```
+
+要修改当前的时区，在root权限下执行如下命令，其中  _time\_zone_  是您想要设置的时区，请根据实际情况修改：
+
+```
+# timedatectl set-timezone time_zone
+```
+
+例如修改当前的时区，首先查询所在地域的可用时区，此处以Asia为例：
+
+```
+# timedatectl list-timezones | grep Asia
+Asia/Aden
+Asia/Almaty
+Asia/Amman
+Asia/Anadyr
+Asia/Aqtau
+Asia/Aqtobe
+Asia/Ashgabat
+Asia/Baghdad
+Asia/Bahrain
+……
+
+Asia/Seoul
+Asia/Shanghai
+Asia/Singapore
+Asia/Srednekolymsk
+Asia/Taipei
+Asia/Tashkent
+Asia/Tbilisi
+Asia/Tehran
+Asia/Thimphu
+Asia/Tokyo
+```
+
+然后修改当前的时区为“Asia/Shanghai”，命令如下：
+
+```
+# timedatectl set-timezone Asia/Shanghai
+```
+
+### 使用date命令设置
+
+#### 显示当前的日期和时间
+
+显示当前的日期和时间，命令如下：
+
+```
+$ date
+```
+
+默认情况下，date命令显示本地时间。要显示UTC时间，添加\-\-utc或-u参数：
+
+```
+$ date --utc
+```
+
+要自定义对应的输出信息格式，添加 +"format" 参数：
+
+```
+$ date +"format"
+```
+
+**表 1**  参数说明
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
格式参数

+
说明

+
%H

+
小时以HH格式（例如 17）。

+
%M

+
分钟以MM格式（例如 37）。

+
%S

+
秒以SS格式（例如 25）。

+
%d

+
日期以DD格式（例如 15）。

+
%m

+
月份以MM格式（例如 07）。

+
%Y

+
年份以YYYY格式（例如 2019）。

+
%Z

+
时区缩写（例如CEST）。

+
%F

+
日期整体格式为YYYY-MM-DD（例如 2019-7-15），等同%Y-%m-%d。

+
%T

+
时间整体格式为HH:MM:SS（例如 18:30:25），等同%H:%M:%S。

+

+
+实际使用示例如下：
+
+-   显示当前的日期和本地时间。
+
+    ```
+    $ date 
+    2019年 08月 17日 星期六 17:26:34 CST
+    ```
+
+-   显示当前的日期和UTC时间。
+
+    ```
+    $ date --utc
+    2019年 08月 17日 星期六 09:26:18 UTC
+    ```
+
+-   自定义date命令的输出。
+
+    ```
+    $ date +"%Y-%m-%d %H:%M"
+    2019-08-17 17:24
+    ```
+
+
+#### 修改时间
+
+要修改当前的时间，添加\-\-set或者-s参数。在root权限下执行如下命令，其中  _HH_  代表小时，_MM_  代表分钟，_SS_  代表秒，请根据实际情况修改：
+
+```
+# date --set HH:MM:SS
+```
+
+默认情况下， date命令设置本地时间。要设置UTC时间，添加\-\-utc或-u参数：
+
+```
+# date --set HH:MM:SS --utc
+```
+
+例如修改当前的时间为23点26分00秒，在root权限下执行如下命令：
+
+```
+# date --set 23:26:00
+```
+
+#### 修改日期
+
+修改当前的日期，添加\-\-set或者-s参数。在root权限下执行如下命令，其中  _YYYY_  代表年份，_MM_  代表月份，_DD_  代表某天，请根据实际情况修改：
+
+```
+# date --set YYYY-MM-DD
+```
+
+例如修改当前的日期为2019年11月2日，命令如下：
+
+```
+# date --set 2019-11-02
+```
+
+### 使用hwclock命令设置
+
+可以使用 hwclock 命令设置硬件时钟RTC \(Real Time Clock\) 。
+
+#### 硬件时钟和系统时钟
+
+Linux 将时钟分为：
+
+-   系统时钟 \(System Clock\) ：当前Linux Kernel中的时钟。
+-   硬件时钟 RTC：主板上由电池供电的主板硬件时钟，该时钟可以在BIOS的 "Standard BIOS Feature" 项中进行设置。
+
+当Linux启动时，会读取硬件时钟，并根据硬件时间来设置系统时间。
+
+#### 显示日期和时间
+
+显示当前硬件的日期和时间，在root权限下执行如下命令：
+
+```
+# hwclock
+```
+
+例如显示当前硬件的日期和时间，命令和输出如下：
+
+```
+# hwclock
+2019-08-26 10:18:42.528948+08:00
+```
+
+#### 设置日期和时间
+
+修改当前硬件的日期和时间，在root权限下执行如下命令，其中  _dd_  表示日，_mm_  表示月份，_yyyy_  表示年份，_HH_  表示小时，_MM_  表示分钟，请根据实际情况修改：
+
+```
+# hwclock --set --date "dd mm yyyy HH:MM"
+```
+
+例如修改当前的时间为2019年10月21日21点17分，命令如下：
+
+```
+# hwclock --set --date "21 Oct 2019 21:17" --utc
+```
+
+## 设置kdump
+本节介绍如何设置kdump预留内存及kdump配置文件参数修改。
+
+
+
+### 设置kdump预留内存
+#### 预留内存参数格式
+
+kdump预留内存参数必须添加到内核启动参数中，配置文件为/boot/efi/EFI/openEuler/grub.cfg，openEuler发布版本中默认已经添加，可以根据实际使用情况调整。添加和修改启动参数后，重启系统生效。kdump预留内存参数格式如下：
+
+| 内核启动参数             | 描述                                        | 默认值           | 备注                                                         |
+|--------------------|-------------------------------------------|---------------|------------------------------------------------------------|
+| crashkernel=x      | 在4G以下的物理内存预留x大小的内存给kdump使用。               | x86版本默认配置512M | 该配置方法只在4G以下内存预留，必须保证4G以下连续可用内存足够预留。                        |
+| crashkernel=x@y    | 在y起始地址预留x大小的内存给kdump使用。                   | 未使用           | 需要确保y起始地址的x大小的内存未被其他模块预留。                                  |
+| crashkernel=x,high | 在4G以下的物理内存中预留256M内存，在4G以上预留x大小内存给kdump使用。 | arm64版本默认配置1024M,high           | 需要确保4G以下有256M连续可用的物理内存，4G以上有连续的x大小的连续物理内存。实际预留内存大小为256M+x。 |
+| crashkernel=x,low crashkernel=y,high | 在4G以下的物理内存中预留x大小，在4G以上预留y大小内存给kdump使用。                                          | 未使用              | 需要确保4G以下有连续的x大小物理内存，4G以上有连续的y大小物理内存。                                                           |
+
+
+### 预留内存推荐值
+| 推荐方案 | 预留参数                   | 参数说明                                         |
+|------|------------------------|----------------------------------------------|
+| 通用方案 | crashkernel=2048M,high | 4G以下预留256M，4G以上预留2048M内存给kdump使用。共256+2048M。 |
+| 经济方案 | crashkernel=1024M,high | 4G以下预留256M，4G以上预留1024M内存给kdump使用。共256+1024M。 推荐系统512G内存以内的场景，并不使用网络转储kdump文件。对于虚拟机场景，可以适当减少内存预留值，推荐虚拟机设置为crashkernel=512M或者crashkernel=256M,high |
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>不通过网络转储kdump文件时，需要设置kdump文件系统不打包网络相关驱动。网络驱动加载需要申请较大内存，可能导致预留内存不足，kdump失败。因此建议禁用网络相关驱动。
+
+
+### 禁用网络相关驱动
+kdump配置文件（/etc/kdump.conf）中，dracut参数可以设置裁剪的驱动模块，可以将网络驱动配置到裁剪驱动列表中，让kdump文件系统中不加载该驱动，修改配置文件后，重启kdump服务生效。dracut参数配置如下所示：
+
+`dracut_args --omit-drivers "mdio-gpi usb_8dev et1011c rt2x00usb bcm-phy-lib mac80211_hwsim rtl8723be rndis_host hns3_cae amd vrf rtl8192cu mt76x02-lib int51x1 ppp_deflate team_mode_loadbalance smsc911x aweth bonding mwifiex_usb hnae dnet rt2x00pci vaser_pci hdlc_ppp marvell rtl8xxxu mlxsw_i2c ath9k_htc rtl8150 smc91x cortina at803x rockchip cxgb4 spi_ks8995 mt76x2u smsc9420 mdio-cavium bnxt_en ch9200 dummy macsec ice mt7601u rtl8188ee ixgbevf net1080 liquidio_vf be2net mlxsw_switchx2 gl620a xilinx_gmii2rgmii ppp_generic rtl8192de sja1000_platform ath10k_core cc770_platform realte igb c_can_platform c_can ethoc dm9601 smsc95xx lg-vl600 ifb enic ath9 mdio-octeon ppp_mppe ath10k_pci cc770 team_mode_activebackup marvell10g hinic rt2x00lib mlx4_en iavf broadcom igc c_can_pci alx rtl8192se rtl8723ae microchip lan78xx atl1c rtl8192c-common almia ax88179_178a qed netxen_nic brcmsmac rt2800usb e1000 qla3xxx mdio-bitbang qsemi mdio-mscc-miim plx_pci ipvlan r8152 cx82310_eth slhc mt76x02-usb ems_pci xen-netfront usbnet pppoe mlxsw_minimal mlxsw_spectrum cdc_ncm rt2800lib rtl_usb hnae3 ath9k_common ath9k_hw catc mt76 hns_enet_drv ppp_async huawei_cdc_ncm i40e rtl8192ce dl2 qmi_wwan mii peak_usb plusb can-dev slcan amd-xgbe team_mode_roundrobin ste10Xp thunder_xcv pptp thunder_bgx ixgbe davicom icplus tap tun smsc75xx smsc dlci hns_dsaf mlxsw_core rt2800mmi softing uPD60620 vaser_usb dp83867 brcmfmac mwifiex_pcie mlx4_core micrel team macvlan bnx2 virtio_net rtl_pci zaurus hns_mdi libcxgb hv_netvsc nicvf mt76x0u teranetics mlxfw cdc_eem qcom-emac pppox mt76-usb sierra_net i40evf bcm87xx mwifiex pegasus rt2x00mmi sja1000 ena hclgevf cnic cxgb4vf ppp_synctty iwlmvm team_mode_broadcast vxlan vsockmon hdlc_cisc rtl8723-common bsd_comp fakelb dp83822 dp83tc811 cicada fm10 8139t sfc hs geneve hclge xgene-enet-v2 cdc_mbim hdlc asix netdevsim rt2800pci team_mode_random lxt ems_usb mlxsw_pci sr9700 mdio-thunder mlxsw_switchib macvtap atlantic cdc_ether mcs7830 nicpf mdi peak_pci atl1e cdc_subset ipvtap btcoexist mt76x0-common veth slip iwldvm bcm7xxx vitesse netconsole epic100 myri10ge r8169 qede microchip_t1 liquidi bnx2x brcmutil mwifiex_sdi mlx5_core rtlwifi vmxnet3 nlmon hns3 hdlc_raw esd_usb2 atl2 mt76x2-common iwlwifi mdio-bcm-unimac national ath rtwpci rtw88 nfp rtl8821ae fjes thunderbolt-net 8139cp atl1 mscc vcan dp83848 dp83640 hdlc_fr e1000e ipheth net_failover aquantia rtl8192ee igbvf rocker intel-xway tg3" --omit "ramdisk network ifcfg qemu-net" --install "chmod" --nofscks`
diff --git "a/content/zh/docs/Administration/\346\220\255\345\273\272FTP\346\234\215\345\212\241\345\231\250.md" "b/docs/zh/docs/20.03_LTS/docs/Administration/\346\220\255\345\273\272FTP\346\234\215\345\212\241\345\231\250.md"
similarity index 99%
rename from "content/zh/docs/Administration/\346\220\255\345\273\272FTP\346\234\215\345\212\241\345\231\250.md"
rename to "docs/zh/docs/20.03_LTS/docs/Administration/\346\220\255\345\273\272FTP\346\234\215\345\212\241\345\231\250.md"
index f77d385e17dec27ef5d1fccce199932bca11d848..d1cbc9f4337f20bf1a976623d797d9225cc3fa6b 100644
--- "a/content/zh/docs/Administration/\346\220\255\345\273\272FTP\346\234\215\345\212\241\345\231\250.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Administration/\346\220\255\345\273\272FTP\346\234\215\345\212\241\345\231\250.md"
@@ -92,7 +92,7 @@ FTP的正常工作需要使用到多个网络端口，服务器端会使用到
     tcp6       0      0 :::21                   :::*                    LISTEN      19716/vsftpd
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >如果没有**netstat**命令，可以执行**dnf install net-tools**命令安装后再使用**netstat**命令。  
     
 -   停止vsftpd服务
@@ -173,7 +173,7 @@ FTP的正常工作需要使用到多个网络端口，服务器端会使用到
 
 ### 默认配置说明
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >文档中的配置内容仅供参考，请用户根据实际情况（例如安全加固需要）进行修改。  
 
 openEuler系统中 ，vsftpd默认不开放匿名用户，使用vim命令查看主配置文件，其内容如下：
@@ -390,7 +390,7 @@ ftp> bye
 221 Goodbye.
 ```
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >如果没有**ftp**命令，可以在root权限下执行**dnf install ftp**命令安装后再使用**ftp**命令。  
 
 
@@ -488,7 +488,7 @@ ftp>
     ftp> mget *.*
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >-   此时每下载一个文件，都会有提示信息。如果要屏蔽提示信息，则在 **mget \*.\*** 命令前先执行**prompt off**  
     >-   文件都被下载到Linux主机的当前目录下。比如，在/home/myopenEuler/下运行的ftp命令，则文件都下载到/home/myopenEuler/下。  
 
diff --git "a/content/zh/docs/Administration/\346\220\255\345\273\272repo\346\234\215\345\212\241\345\231\250.md" "b/docs/zh/docs/20.03_LTS/docs/Administration/\346\220\255\345\273\272repo\346\234\215\345\212\241\345\231\250.md"
similarity index 89%
rename from "content/zh/docs/Administration/\346\220\255\345\273\272repo\346\234\215\345\212\241\345\231\250.md"
rename to "docs/zh/docs/20.03_LTS/docs/Administration/\346\220\255\345\273\272repo\346\234\215\345\212\241\345\231\250.md"
index dcc2d240f784cbf274403312525b67d3ae6da91f..68bc81cb552f29dbea880446f48b66beef08b7c8 100644
--- "a/content/zh/docs/Administration/\346\220\255\345\273\272repo\346\234\215\345\212\241\345\231\250.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Administration/\346\220\255\345\273\272repo\346\234\215\345\212\241\345\231\250.md"
@@ -1,400 +1,400 @@
-# 搭建repo服务器
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->openEuler提供了多种repo源供用户在线使用，各repo源含义可参考[系统安装](../Releasenotes/系统安装.md)。若用户无法在线获取openEuler repo源，则可使用openEuler提供的ISO发布包创建为本地openEuler repo源。本章节中以openEuler-20.03-LTS-aarch64-dvd.iso发布包为例，请根据实际需要的ISO发布包进行修改。
-
-
-
-- [搭建repo服务器](#搭建repo服务器)
-    - [概述](#概述)
-    - [创建/更新本地repo源](#创建更新本地repo源)
-        - [获取ISO发布包](#获取iso发布包)
-        - [挂载ISO创建repo源](#挂载iso创建repo源)
-        - [创建本地repo源](#创建本地repo源)
-        - [更新repo源](#更新repo源)
-    - [部署远端repo源](#部署远端repo源)
-        - [nginx安装与配置](#nginx安装与配置)
-        - [启动nginx服务](#启动nginx服务)
-        - [repo源部署](#repo源部署)
-    - [使用repo源](#使用repo源)
-        - [repo配置为yum源（软件源）](#repo配置为yum源软件源)
-        - [repo优先级](#repo优先级)
-        - [dnf相关命令](#dnf相关命令)
-
-
-
-## 概述
-
-将openEuler提供的ISO发布包openEuler-20.03-LTS-aarch64-dvd.iso创建为repo源，如下以使用nginx进行repo源部署，提供http服务为例进行说明。
-
-## 创建/更新本地repo源
-
-使用mount挂载，将openEuler的ISO发布包openEuler-20.03-LTS-aarch64-dvd.iso创建为repo源，并能够对repo源进行更新。
-### 获取ISO发布包
-
-请从如下网址获取openEuler的ISO发布包：
-
-[https://repo.openeuler.org/openEuler-20.03-LTS/ISO/](https://repo.openeuler.org/openEuler-20.03-LTS/ISO/)
-
-### 挂载ISO创建repo源
-
-在root权限下使用mount命令挂载ISO发布包。
-
-示例如下：
-
-```
-# mount /home/openEuler/openEuler-20.03-LTS-aarch64-dvd.iso /mnt/
-```
-
-挂载好的mnt目录如下：
-
-```
-.
-│── boot.catalog
-│── docs
-│── EFI
-│── images
-│── Packages
-│── repodata
-│── TRANS.TBL
-└── RPM-GPG-KEY-openEuler
-```
-
-其中，Packages为rpm包所在的目录，repodata为repo源元数据所在的目录，RPM-GPG-KEY-openEuler为openEuler的签名公钥。
-
-### 创建本地repo源
-
-可以拷贝ISO发布包中相关文件至本地目录以创建本地repo源，示例如下：
-
-```
-# mount /home/openEuler/openEuler-20.03-LTS-aarch64-dvd.iso /mnt/
-$ mkdir -p ~/srv/repo/
-$ cp -r /mnt/Packages ~/srv/repo/
-$ cp -r /mnt/repodata ~/srv/repo/
-$ cp -r /mnt/RPM-GPG-KEY-openEuler ~/srv/repo/
-```
-
-从而本地repo目录如下：
-
-```
-.
-│── Packages
-│── repodata
-└── RPM-GPG-KEY-openEuler
-```
-
-Packages为rpm包所在的目录，repodata为repo源元数据所在的目录，RPM-GPG-KEY-openEuler为openEuler的签名公钥。
-
-### 更新repo源
-
-更新repo源有两种方式：
-
--   通过新版本的ISO更新已有的repo源，与创建repo源的方式相同，即挂载ISO发布包或重新拷贝ISO发布包至本地目录。
-
--   在repo源的Packages目录下添加rpm包，然后通过createrepo命令更新repo源
-
-    ```
-    $ createrepo --update --workers=10 ~/srv/repo
-    ```
-
-    其中，\-\-update表示更新，\-\-workers表示线程数，可自定义。
-    
-    >![](public_sys-resources/icon-note.gif) **说明：**   
-    >若命令打印信息为“createrepo：未找到命令”，则表示未安装createrepo软件，可在root权限下执行**dnf install createrepo**进行安装。  
-
-
-## 部署远端repo源
-
-安装openEuler操作系统，在openEuler上通过nginx部署repo源。
-### nginx安装与配置
-
-1.  请自行下载nginx工具并在root权限下安装nginx。
-2.  安装nginx之后，在root权限下配置/etc/nginx/nginx.conf。
-
-    >![](public_sys-resources/icon-note.gif) **说明：**   
-    >文档中的配置内容仅供参考，请用户根据实际情况（例如安全加固需要）进行配置。  
-
-    ```
-    user  nginx;
-    worker_processes  auto;                          # 建议设置为core-1
-    error_log  /var/log/nginx/error.log  warn;       # log存放位置
-    pid        /var/run/nginx.pid;
-    
-    events {
-        worker_connections  1024;
-    }
-    
-    http {
-        include       /etc/nginx/mime.types;
-        default_type  application/octet-stream;
-    
-        log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
-                          '$status $body_bytes_sent "$http_referer" '
-                          '"$http_user_agent" "$http_x_forwarded_for"';
-    
-        access_log  /var/log/nginx/access.log  main;
-        sendfile        on;
-        keepalive_timeout  65;
-    
-        server {
-            listen       80;
-            server_name  localhost;                 # 服务器名（url）
-            client_max_body_size 4G;
-            root         /usr/share/nginx/repo;                 # 服务默认目录
-    
-            location / {
-                autoindex            on;            # 开启访问目录下层文件
-                autoindex_exact_size on;
-                autoindex_localtime  on; 
-            }
-    
-        }
-    
-    }
-    ```
-
-
-### 启动nginx服务
-
-1.  在root权限下通过systemd启动nginx服务：
-
-    ```
-    # systemctl enable nginx
-    # systemctl start nginx
-    ```
-
-2.  nginx是否启动成功可通过下面命令查看：
-
-    ```
-    $ systemctl status nginx
-    ```
-
-    - [图1](#zh-cn_topic_0151920971_fd25e3f1d664b4087ae26631719990a71)表示nginx服务启动成功
-
-        **图 1**  nginx服务启动成功  
-        ![](figures/nginx服务启动成功.png "nginx服务启动成功")
-
-    - 若nginx服务启动失败，查看错误信息：
-
-    ```
-    $ systemctl status nginx.service --full
-    ```
-
-        **图 2**  nginx服务启动失败  
-        ![](figures/nginx服务启动失败.png "nginx服务启动失败")
-
-    如[图2](#zh-cn_topic_0151920971_f1f9f3d086e454b9cba29a7cae96a4c54)所示nginx服务创建失败，是由于目录/var/spool/nginx/tmp/client\_body创建失败，在root权限下手动进行创建，类似的问题也这样处理：
-
-    ```
-    # mkdir -p /var/spool/nginx/tmp/client_body
-    # mkdir -p /var/spool/nginx/tmp/proxy
-    # mkdir -p /var/spool/nginx/tmp/fastcgi
-    # mkdir -p /usr/share/nginx/uwsgi_temp
-    # mkdir -p /usr/share/nginx/scgi_temp
-    ```
-
-
-### repo源部署
-
-1.  在root权限下创建nginx配置文件/etc/nginx/nginx.conf中指定的目录/usr/share/nginx/repo：
-
-    ```
-    # mkdir -p /usr/share/nginx/repo
-    ```
-
-2.  在root权限下修改目录/usr/share/nginx/repo的权限：
-
-    ```
-    # chmod -R 755 /usr/share/nginx/repo
-    ```
-
-3.  设置防火墙规则，开启nginx设置的端口（此处为80端口），在root权限下通过firewall设置端口开启：
-
-    ```
-    # firewall-cmd --add-port=80/tcp --permanent
-    # firewall-cmd --reload
-    ```
-
-    在root权限下查询80端口是否开启成功，输出为yes则表示80端口开启成功：
-
-    ```
-    # firewall-cmd --query-port=80/tcp
-    ```
-
-    也可在root权限下通过iptables来设置80端口开启：
-
-    ```
-    # iptables -I INPUT -p tcp --dport 80 -j ACCEPT
-    ```
-
-4.  nginx服务设置好之后，即可通过ip直接访问网页，如[图3](#zh-cn_topic_0151921017_fig1880404110396)：
-
-    **图 3**  nginx部署成功  
-    ![](figures/nginx部署成功.png "nginx部署成功")
-
-5.  通过下面几种方式将repo源放入到/usr/share/nginx/repo下：
-    - 在root权限下拷贝镜像中相关文件至/usr/share/nginx/repo下，并修改目录权限。
-
-        ```
-        # mount /home/openEuler/openEuler-20.03-LTS-aarch64-dvd.iso  /mnt/
-        # cp -r /mnt/Packages /usr/share/nginx/repo
-        # cp -r /mnt/repodata /usr/share/nginx/repo
-        # cp -r /mnt/RPM-GPG-KEY-openEuler /usr/share/nginx/repo
-        # chmod -R 755 /usr/share/nginx/repo
-        ```
-    
-        openEuler-20.03-LTS-aarch64-dvd.iso存放在/home/openEuler目录下。
-    
-    - 使用root在/usr/share/nginx/repo下创建repo源的软链接。
-    
-        ```
-        # ln -s /mnt /usr/share/nginx/repo/os
-        ```
-    
-        /mnt为已经创建好的repo源，/usr/share/nginx/repo/os将指向/mnt。
-
-
-
-## 使用repo源
-
-repo可配置为yum源，yum（全称为 Yellow dog Updater, Modified）是一个Shell前端软件包管理器。基于RPM包管理，能够从指定的服务器自动下载RPM包并且安装，可以自动处理依赖性关系，并且一次安装所有依赖的软体包，无须繁琐地一次次下载和安装。
-### repo配置为yum源（软件源）
-
-构建好的repo可以配置为yum源使用，在/etc/yum.repos.d/目录下使用root权限创建\*\*\*.repo的配置文件（必须以.repo为扩展名），分为本地和http服务器配置yum源两种方式：
-
--   配置本地yum源
-
-    在/etc/yum.repos.d目录下创建openEuler.repo文件，使用构建的本地repo源作为yum源，openEuler.repo的内容如下：
-
-    ```
-    [base]
-    name=base
-    baseurl=file:///home/openEuler/srv/repo
-    enabled=1
-    gpgcheck=1
-    gpgkey=file:///home/openEuler/srv/repo/RPM-GPG-KEY-openEuler
-    ```
-
-    >![](public_sys-resources/icon-note.gif) **说明：**   
-    > - \[*repoid*\]中的repoid为软件仓库（repository）的ID号，所有.repo配置文件中的各repoid不能重复，必须唯一。示例中repoid设置为**base**。
-    > - name为软件仓库描述的字符串。
-    > - baseurl为软件仓库的地址。
-    > - enabled为是否启用该软件源仓库，可选值为1和0。默认值为1，表示启用该软件源仓库。
-    > - gpgcheck可设置为1或0，1表示进行gpg（GNU Private Guard）校验，0表示不进行gpg校验，gpgcheck可以确定rpm包的来源是有效和安全的。  
-    > - gpgkey为验证签名用的公钥。  
-
--   配置http服务器yum源
-
-    在/etc/yum.repos.d目录下创建openEuler.repo文件。
-	
-	-   若使用用户部署的http服务端的repo源作为yum源，openEuler.repo的内容如下：
-
-        ```
-        [base]
-        name=base
-        baseurl=http://192.168.139.209/
-        enabled=1
-        gpgcheck=1
-        gpgkey=http://192.168.139.209/RPM-GPG-KEY-openEuler
-        ```
-
-        >![](public_sys-resources/icon-note.gif) **说明：**   
-        >“192.168.139.209”为示例地址，请用户根据实际情况进行配置。  
-
-	-   若使用openEuler提供的openEuler repo源作为yum源，以AArch64架构的OS repo源为例，openEuler.repo的内容如下：
-	
-        ```
-        [base]
-        name=base
-        baseurl=http://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/
-        enabled=1
-        gpgcheck=1
-        gpgkey=http://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/RPM-GPG-KEY-openEuler
-        ```
-
-
-
-### repo优先级
-
-当有多个repo源时，可通过在.repo文件的priority参数设置repo的优先级（如果不设置，默认优先级是99，当相同优先级的源中存在相同rpm包时，会安装最新的版本）。其中，1为最高优先级，99为最低优先级，如给openEuler.repo配置优先级为2：
-
-```
-[base]
-name=base
-baseurl=http://192.168.139.209/
-enabled=1
-priority=2
-gpgcheck=1
-gpgkey=http://192.168.139.209/RPM-GPG-KEY-openEuler
-```
-
-### dnf相关命令
-
-dnf命令在安装升级时能够自动解析包的依赖关系，一般的使用方式如下：
-
-```
-dnf  
-```
-
-常用的命令如下：
-
--   安装，需要在root权限下执行。
-
-    ```
-    # dnf install 
-    ```
-
--   升级，需要在root权限下执行。
-
-    ```
-    # dnf update 
-    ```
-
--   回退，需要在root权限下执行。
-
-    ```
-    # dnf downgrade 
-    ```
-
--   检查更新
-
-    ```
-    $ dnf check-update
-    ```
-
--   卸载，需要在root权限下执行。
-
-    ```
-    # dnf remove 
-    ```
-
--   查询
-
-    ```
-    $ dnf search 
-    ```
-
--   本地安装，需要在root权限下执行。
-
-    ```
-    # dnf localinstall 
-    ```
-
--   查看历史记录
-
-    ```
-    $ dnf history
-    ```
-
--   清除缓存目录
-
-    ```
-    $ dnf clean all
-    ```
-
--   更新缓存
-
-    ```
-    $ dnf makecache
-    ```
-
+# 搭建repo服务器
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>openEuler提供了多种repo源供用户在线使用，各repo源含义可参考[系统安装](./../Releasenotes/系统安装.md)。若用户无法在线获取openEuler repo源，则可使用openEuler提供的ISO发布包创建为本地openEuler repo源。本章节中以openEuler-20.03-LTS-aarch64-dvd.iso发布包为例，请根据实际需要的ISO发布包进行修改。
+
+
+
+- [搭建repo服务器](#搭建repo服务器)
+    - [概述](#概述)
+    - [创建/更新本地repo源](#创建更新本地repo源)
+        - [获取ISO发布包](#获取iso发布包)
+        - [挂载ISO创建repo源](#挂载iso创建repo源)
+        - [创建本地repo源](#创建本地repo源)
+        - [更新repo源](#更新repo源)
+    - [部署远端repo源](#部署远端repo源)
+        - [nginx安装与配置](#nginx安装与配置)
+        - [启动nginx服务](#启动nginx服务)
+        - [repo源部署](#repo源部署)
+    - [使用repo源](#使用repo源)
+        - [repo配置为yum源（软件源）](#repo配置为yum源软件源)
+        - [repo优先级](#repo优先级)
+        - [dnf相关命令](#dnf相关命令)
+
+
+
+## 概述
+
+将openEuler提供的ISO发布包openEuler-20.03-LTS-aarch64-dvd.iso创建为repo源，如下以使用nginx进行repo源部署，提供http服务为例进行说明。
+
+## 创建/更新本地repo源
+
+使用mount挂载，将openEuler的ISO发布包openEuler-20.03-LTS-aarch64-dvd.iso创建为repo源，并能够对repo源进行更新。
+### 获取ISO发布包
+
+请从如下网址获取openEuler的ISO发布包：
+
+[https://repo.openeuler.org/openEuler-20.03-LTS/ISO/](https://repo.openeuler.org/openEuler-20.03-LTS/ISO/)
+
+### 挂载ISO创建repo源
+
+在root权限下使用mount命令挂载ISO发布包。
+
+示例如下：
+
+```
+# mount /home/openEuler/openEuler-20.03-LTS-aarch64-dvd.iso /mnt/
+```
+
+挂载好的mnt目录如下：
+
+```
+.
+│── boot.catalog
+│── docs
+│── EFI
+│── images
+│── Packages
+│── repodata
+│── TRANS.TBL
+└── RPM-GPG-KEY-openEuler
+```
+
+其中，Packages为rpm包所在的目录，repodata为repo源元数据所在的目录，RPM-GPG-KEY-openEuler为openEuler的签名公钥。
+
+### 创建本地repo源
+
+可以拷贝ISO发布包中相关文件至本地目录以创建本地repo源，示例如下：
+
+```
+# mount /home/openEuler/openEuler-20.03-LTS-aarch64-dvd.iso /mnt/
+$ mkdir -p ~/srv/repo/
+$ cp -r /mnt/Packages ~/srv/repo/
+$ cp -r /mnt/repodata ~/srv/repo/
+$ cp -r /mnt/RPM-GPG-KEY-openEuler ~/srv/repo/
+```
+
+从而本地repo目录如下：
+
+```
+.
+│── Packages
+│── repodata
+└── RPM-GPG-KEY-openEuler
+```
+
+Packages为rpm包所在的目录，repodata为repo源元数据所在的目录，RPM-GPG-KEY-openEuler为openEuler的签名公钥。
+
+### 更新repo源
+
+更新repo源有两种方式：
+
+-   通过新版本的ISO更新已有的repo源，与创建repo源的方式相同，即挂载ISO发布包或重新拷贝ISO发布包至本地目录。
+
+-   在repo源的Packages目录下添加rpm包，然后通过createrepo命令更新repo源
+
+    ```
+    $ createrepo --update --workers=10 ~/srv/repo
+    ```
+
+    其中，\-\-update表示更新，\-\-workers表示线程数，可自定义。
+    
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
+    >若命令打印信息为“createrepo：未找到命令”，则表示未安装createrepo软件，可在root权限下执行**dnf install createrepo**进行安装。  
+
+
+## 部署远端repo源
+
+安装openEuler操作系统，在openEuler上通过nginx部署repo源。
+### nginx安装与配置
+
+1.  请自行下载nginx工具并在root权限下安装nginx。
+2.  安装nginx之后，在root权限下配置/etc/nginx/nginx.conf。
+
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
+    >文档中的配置内容仅供参考，请用户根据实际情况（例如安全加固需要）进行配置。  
+
+    ```
+    user  nginx;
+    worker_processes  auto;                          # 建议设置为core-1
+    error_log  /var/log/nginx/error.log  warn;       # log存放位置
+    pid        /var/run/nginx.pid;
+    
+    events {
+        worker_connections  1024;
+    }
+    
+    http {
+        include       /etc/nginx/mime.types;
+        default_type  application/octet-stream;
+    
+        log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
+                          '$status $body_bytes_sent "$http_referer" '
+                          '"$http_user_agent" "$http_x_forwarded_for"';
+    
+        access_log  /var/log/nginx/access.log  main;
+        sendfile        on;
+        keepalive_timeout  65;
+    
+        server {
+            listen       80;
+            server_name  localhost;                 # 服务器名（url）
+            client_max_body_size 4G;
+            root         /usr/share/nginx/repo;                 # 服务默认目录
+    
+            location / {
+                autoindex            on;            # 开启访问目录下层文件
+                autoindex_exact_size on;
+                autoindex_localtime  on; 
+            }
+    
+        }
+    
+    }
+    ```
+
+
+### 启动nginx服务
+
+1.  在root权限下通过systemd启动nginx服务：
+
+    ```
+    # systemctl enable nginx
+    # systemctl start nginx
+    ```
+
+2.  nginx是否启动成功可通过下面命令查看：
+
+    ```
+    $ systemctl status nginx
+    ```
+
+    - [图1](#zh-cn_topic_0151920971_fd25e3f1d664b4087ae26631719990a71)表示nginx服务启动成功
+
+        **图 1**  nginx服务启动成功  
+        ![](./figures/nginx-start-success.png "nginx服务启动成功")
+
+    - 若nginx服务启动失败，查看错误信息：
+
+    ```
+    $ systemctl status nginx.service --full
+    ```
+
+    **图 2**  nginx服务启动失败  
+    ![](./figures/nginx-start-failed.png "nginx服务启动失败")
+
+    如[图2](#zh-cn_topic_0151920971_f1f9f3d086e454b9cba29a7cae96a4c54)所示nginx服务创建失败，是由于目录/var/spool/nginx/tmp/client\_body创建失败，在root权限下手动进行创建，类似的问题也这样处理：
+
+    ```
+    # mkdir -p /var/spool/nginx/tmp/client_body
+    # mkdir -p /var/spool/nginx/tmp/proxy
+    # mkdir -p /var/spool/nginx/tmp/fastcgi
+    # mkdir -p /usr/share/nginx/uwsgi_temp
+    # mkdir -p /usr/share/nginx/scgi_temp
+    ```
+
+
+### repo源部署
+
+1.  在root权限下创建nginx配置文件/etc/nginx/nginx.conf中指定的目录/usr/share/nginx/repo：
+
+    ```
+    # mkdir -p /usr/share/nginx/repo
+    ```
+
+2.  在root权限下修改目录/usr/share/nginx/repo的权限：
+
+    ```
+    # chmod -R 755 /usr/share/nginx/repo
+    ```
+
+3.  设置防火墙规则，开启nginx设置的端口（此处为80端口），在root权限下通过firewall设置端口开启：
+
+    ```
+    # firewall-cmd --add-port=80/tcp --permanent
+    # firewall-cmd --reload
+    ```
+
+    在root权限下查询80端口是否开启成功，输出为yes则表示80端口开启成功：
+
+    ```
+    # firewall-cmd --query-port=80/tcp
+    ```
+
+    也可在root权限下通过iptables来设置80端口开启：
+
+    ```
+    # iptables -I INPUT -p tcp --dport 80 -j ACCEPT
+    ```
+
+4.  nginx服务设置好之后，即可通过ip直接访问网页，如[图3](#zh-cn_topic_0151921017_fig1880404110396)：
+
+    **图 3**  nginx部署成功  
+    ![](./figures/nginx-deploy-success.png "nginx部署成功")
+
+5.  通过下面几种方式将repo源放入到/usr/share/nginx/repo下：
+    - 在root权限下拷贝镜像中相关文件至/usr/share/nginx/repo下，并修改目录权限。
+
+        ```
+        # mount /home/openEuler/openEuler-20.03-LTS-aarch64-dvd.iso  /mnt/
+        # cp -r /mnt/Packages /usr/share/nginx/repo
+        # cp -r /mnt/repodata /usr/share/nginx/repo
+        # cp -r /mnt/RPM-GPG-KEY-openEuler /usr/share/nginx/repo
+        # chmod -R 755 /usr/share/nginx/repo
+        ```
+    
+        openEuler-20.03-LTS-aarch64-dvd.iso存放在/home/openEuler目录下。
+    
+    - 使用root在/usr/share/nginx/repo下创建repo源的软链接。
+    
+        ```
+        # ln -s /mnt /usr/share/nginx/repo/os
+        ```
+    
+        /mnt为已经创建好的repo源，/usr/share/nginx/repo/os将指向/mnt。
+
+
+
+## 使用repo源
+
+repo可配置为yum源，yum（全称为 Yellow dog Updater, Modified）是一个Shell前端软件包管理器。基于RPM包管理，能够从指定的服务器自动下载RPM包并且安装，可以自动处理依赖性关系，并且一次安装所有依赖的软体包，无须繁琐地一次次下载和安装。
+### repo配置为yum源（软件源）
+
+构建好的repo可以配置为yum源使用，在/etc/yum.repos.d/目录下使用root权限创建\*\*\*.repo的配置文件（必须以.repo为扩展名），分为本地和http服务器配置yum源两种方式：
+
+-   配置本地yum源
+
+    在/etc/yum.repos.d目录下创建openEuler.repo文件，使用构建的本地repo源作为yum源，openEuler.repo的内容如下：
+
+    ```
+    [base]
+    name=base
+    baseurl=file:///home/openEuler/srv/repo
+    enabled=1
+    gpgcheck=1
+    gpgkey=file:///home/openEuler/srv/repo/RPM-GPG-KEY-openEuler
+    ```
+
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
+    > - \[*repoid*\]中的repoid为软件仓库（repository）的ID号，所有.repo配置文件中的各repoid不能重复，必须唯一。示例中repoid设置为**base**。
+    > - name为软件仓库描述的字符串。
+    > - baseurl为软件仓库的地址。
+    > - enabled为是否启用该软件源仓库，可选值为1和0。默认值为1，表示启用该软件源仓库。
+    > - gpgcheck可设置为1或0，1表示进行gpg（GNU Private Guard）校验，0表示不进行gpg校验，gpgcheck可以确定rpm包的来源是有效和安全的。  
+    > - gpgkey为验证签名用的公钥。  
+
+-   配置http服务器yum源
+
+    在/etc/yum.repos.d目录下创建openEuler.repo文件。
+	
+	-   若使用用户部署的http服务端的repo源作为yum源，openEuler.repo的内容如下：
+
+        ```
+        [base]
+        name=base
+        baseurl=http://192.168.139.209/
+        enabled=1
+        gpgcheck=1
+        gpgkey=http://192.168.139.209/RPM-GPG-KEY-openEuler
+        ```
+
+        >![](./public_sys-resources/icon-note.gif) **说明：**   
+        >“192.168.139.209”为示例地址，请用户根据实际情况进行配置。  
+
+	-   若使用openEuler提供的openEuler repo源作为yum源，以AArch64架构的OS repo源为例，openEuler.repo的内容如下：
+	
+        ```
+        [base]
+        name=base
+        baseurl=http://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/
+        enabled=1
+        gpgcheck=1
+        gpgkey=http://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/RPM-GPG-KEY-openEuler
+        ```
+
+
+
+### repo优先级
+
+当有多个repo源时，可通过在.repo文件的priority参数设置repo的优先级（如果不设置，默认优先级是99，当相同优先级的源中存在相同rpm包时，会安装最新的版本）。其中，1为最高优先级，99为最低优先级，如给openEuler.repo配置优先级为2：
+
+```
+[base]
+name=base
+baseurl=http://192.168.139.209/
+enabled=1
+priority=2
+gpgcheck=1
+gpgkey=http://192.168.139.209/RPM-GPG-KEY-openEuler
+```
+
+### dnf相关命令
+
+dnf命令在安装升级时能够自动解析包的依赖关系，一般的使用方式如下：
+
+```
+dnf  
+```
+
+常用的命令如下：
+
+-   安装，需要在root权限下执行。
+
+    ```
+    # dnf install 
+    ```
+
+-   升级，需要在root权限下执行。
+
+    ```
+    # dnf update 
+    ```
+
+-   回退，需要在root权限下执行。
+
+    ```
+    # dnf downgrade 
+    ```
+
+-   检查更新
+
+    ```
+    $ dnf check-update
+    ```
+
+-   卸载，需要在root权限下执行。
+
+    ```
+    # dnf remove 
+    ```
+
+-   查询
+
+    ```
+    $ dnf search 
+    ```
+
+-   本地安装，需要在root权限下执行。
+
+    ```
+    # dnf localinstall 
+    ```
+
+-   查看历史记录
+
+    ```
+    $ dnf history
+    ```
+
+-   清除缓存目录
+
+    ```
+    $ dnf clean all
+    ```
+
+-   更新缓存
+
+    ```
+    $ dnf makecache
+    ```
+
diff --git "a/content/zh/docs/Administration/\346\220\255\345\273\272web\346\234\215\345\212\241\345\231\250.md" "b/docs/zh/docs/20.03_LTS/docs/Administration/\346\220\255\345\273\272web\346\234\215\345\212\241\345\231\250.md"
similarity index 98%
rename from "content/zh/docs/Administration/\346\220\255\345\273\272web\346\234\215\345\212\241\345\231\250.md"
rename to "docs/zh/docs/20.03_LTS/docs/Administration/\346\220\255\345\273\272web\346\234\215\345\212\241\345\231\250.md"
index b0878f072c7e5585f45877ba0756ea253b75a119..47a06bc374adce4ce9442eb593b1a7a6778dbe88 100644
--- "a/content/zh/docs/Administration/\346\220\255\345\273\272web\346\234\215\345\212\241\345\231\250.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Administration/\346\220\255\345\273\272web\346\234\215\345\212\241\345\231\250.md"
@@ -39,7 +39,7 @@ openEuler系统中的web服务器版本是Apache HTTP服务器2.4版本，即htt
     # dnf install httpd
     ```
 
-    更多关于管理服务的内容，请参见[管理服务](管理服务.html)。
+    更多关于管理服务的内容，请参见[管理服务](./管理服务.html)。
 
 -   启动、停止和重启httpd服务，需要使用root权限。
 
@@ -60,7 +60,7 @@ openEuler系统中的web服务器版本是Apache HTTP服务器2.4版本，即htt
     ```
 
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >假如正在运行的Apache HTTP服务器作为一个安全服务器，系统开机启动后需要密码，这个密码使用的是加密的私有SSL密钥。  
 
 #### 停止服务
@@ -157,7 +157,7 @@ $ systemctl is-active httpd
 Syntax OK
 ```
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >-   在修改配置文件之前，请先备份原始文件，以便出现问题时能够快速恢复配置文件。  
 >-   需要重启web服务，才能使修改后的配置文件生效。  
 
@@ -198,7 +198,7 @@ httpd服务是一个模块化的应用，它和许多动态共享对象DSO（Dyn
     ```
 
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >**httpd 的常用命令**  
 >
 >-   httpd -v : 查看httpd的版本号。  
@@ -316,7 +316,7 @@ Nginx 是一款轻量级的 Web 服务器/反向代理服务器及电子邮件
 
 ### 安装
 
-1.  配置本地yum源，详细信息请参考[搭建repo服务器](搭建repo服务器.html)。
+1.  配置本地yum源，详细信息请参考[搭建repo服务器](./搭建repo服务器.html)。
 2.  清除缓存。
 
     ```
@@ -352,7 +352,7 @@ Nginx 是一款轻量级的 Web 服务器/反向代理服务器及电子邮件
 
 -   为了能够使用nginx服务，请确保您的系统中已经安装nginx服务。若未安装，可参考[安装](#安装)进行安装。
 
-    更多关于管理服务的内容，请参见[管理服务](管理服务.html)。
+    更多关于管理服务的内容，请参见[管理服务](./管理服务.html)。
 
 -   启动、停止和重启nginx服务，需要使用root权限。
 
@@ -373,7 +373,7 @@ Nginx 是一款轻量级的 Web 服务器/反向代理服务器及电子邮件
     ```
 
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >假如正在运行的nginx服务器作为一个安全服务器，系统开机启动后需要密码，这个密码使用的是加密的私有SSL密钥。  
 
 #### 停止服务
@@ -466,7 +466,7 @@ $ systemctl is-active nginx
 
 如果回显信息中有“syntax is ok”，说明配置文件语法正确。
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >-   在修改配置文件之前，请先备份原始文件，以便出现问题时能够快速恢复配置文件。  
 >-   需要重启web服务，才能使修改后的配置文件生效。  
 
diff --git "a/content/zh/docs/Administration/\346\220\255\345\273\272\346\225\260\346\215\256\345\272\223\346\234\215\345\212\241\345\231\250.md" "b/docs/zh/docs/20.03_LTS/docs/Administration/\346\220\255\345\273\272\346\225\260\346\215\256\345\272\223\346\234\215\345\212\241\345\231\250.md"
similarity index 94%
rename from "content/zh/docs/Administration/\346\220\255\345\273\272\346\225\260\346\215\256\345\272\223\346\234\215\345\212\241\345\231\250.md"
rename to "docs/zh/docs/20.03_LTS/docs/Administration/\346\220\255\345\273\272\346\225\260\346\215\256\345\272\223\346\234\215\345\212\241\345\231\250.md"
index a6a66a23842316b8a1329110c09784b8b207e0c1..5b641d86c709aa044d760100948cd5c84264138e 100644
--- "a/content/zh/docs/Administration/\346\220\255\345\273\272\346\225\260\346\215\256\345\272\223\346\234\215\345\212\241\345\231\250.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Administration/\346\220\255\345\273\272\346\225\260\346\215\256\345\272\223\346\234\215\345\212\241\345\231\250.md"
@@ -28,7 +28,7 @@
 PostgreSQL的架构如[图1](#fig26022387391)所示，主要进程说明如[表1](#table62020913417)所示。
 
 **图 1**  PostgreSql架构  
-![](figures/PostgreSql架构.png "PostgreSql架构")
+![](./figures/PostgreSQL_architecture.png)
 
 **表 1**  PostgreSql中的主要进程说明
 
@@ -105,11 +105,11 @@ PostgreSQL的架构如[图1](#fig26022387391)所示，主要进程说明如[表1
 
 ### 配置环境
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >以下环境配置仅为参考示例，具体配置视实际需求做配置  
 #### 关闭防火墙并取消开机自启动
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >测试环境下通常会关闭防火墙以避免部分网络因素影响，视实际需求做配置。  
 
 1.  在root权限下停止防火墙。
@@ -124,7 +124,7 @@ PostgreSQL的架构如[图1](#fig26022387391)所示，主要进程说明如[表1
     # systemctl disable firewalld
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >执行disable命令关闭防火墙的同时，也取消了开机自启动。  
 
 
@@ -139,7 +139,7 @@ PostgreSQL的架构如[图1](#fig26022387391)所示，主要进程说明如[表1
 
 #### 创建组和用户
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >服务器环境下，为了系统安全，通常会为进程分配单独的用户，以实现权限隔离。本章节创建的组和用户都是操作系统层面的，不是数据库层面的。  
 
 1.  在root权限下创建PostgreSQL用户（组）。
@@ -161,7 +161,7 @@ PostgreSQL的架构如[图1](#fig26022387391)所示，主要进程说明如[表1
 
 #### 搭建数据盘
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >-   测试极限性能时，建议单独挂载IO性能更优的NVME SSD存储介质创建PostgreSQL测试实例，避免磁盘IO对性能测试结果的影响，本文以单独挂载NVME SSD为例，参考步骤1\~步骤4。  
 >-   非性能测试时，在root权限下执行以下命令，创建数据目录即可。然后跳过本小节：  
 >    \# mkdir /data  
@@ -197,7 +197,7 @@ PostgreSQL的架构如[图1](#fig26022387391)所示，主要进程说明如[表1
 ### 安装、运行和卸载
 #### 安装
 
-1.  配置本地yum源，详细信息请参考[搭建repo服务器](搭建repo服务器.html)。
+1.  配置本地yum源，详细信息请参考[搭建repo服务器](./搭建repo服务器.html)。
 2.  清除缓存。
 
     ```
@@ -226,7 +226,7 @@ PostgreSQL的架构如[图1](#fig26022387391)所示，主要进程说明如[表1
 #### 运行
 ##### 初始化数据库
 
->![](public_sys-resources/icon-notice.gif) **须知：**   
+>![](./public_sys-resources/icon-notice.gif) **须知：**   
 >此步骤在postgres用户下操作。  
 
 1.  切换到已创建的PostgreSQL用户。
@@ -258,7 +258,7 @@ PostgreSQL的架构如[图1](#fig26022387391)所示，主要进程说明如[表1
 
     命令执行后，打印信息如下图所示，PostgreSQL相关进程已经正常启动了。
 
-    ![](figures/postgres.png)
+    ![](./figures/postgres.png)
 
 
 ##### 登录数据库
@@ -269,9 +269,9 @@ PostgreSQL的架构如[图1](#fig26022387391)所示，主要进程说明如[表1
     $ /usr/bin/psql -U postgres
     ```
 
-    ![](figures/登录.png)
+    ![](./figures/login.png)
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >初次登录数据库，无需密码。  
 
 
@@ -283,7 +283,7 @@ PostgreSQL的架构如[图1](#fig26022387391)所示，主要进程说明如[表1
     postgres=#alter user postgres with password '123456';
     ```
 
-    ![](figures/zh-cn_image_0230050789.png)
+    ![](./figures/zh-cn_image_0230050789.png)
 
 
 ##### 退出数据库
@@ -702,7 +702,7 @@ postgres=# \l;
 
 可以使用DROP DATABASE语句或dropdb来删除数据库。dropdb是对DROP DATABASE命令的封装，需要在shell界面执行，而不是在数据库界面。
 
->![](public_sys-resources/icon-caution.gif) **注意：**   
+>![](./public_sys-resources/icon-caution.gif) **注意：**   
 >删除数据库要谨慎操作，一旦删除，数据库中的所有表和数据都会删除。  
 
 ```
@@ -797,7 +797,7 @@ MariaDB数据库管理系统是MySQL的一个分支，主要由开源社区在
 MariaDB的架构如[图2](#fig13492418164520)所示。
 
 **图 2**  MariaDB逻辑架构  
-![](figures/MariaDB逻辑架构.png "MariaDB逻辑架构")
+![](./figures/Logical_architecture_MariaDB.png "MariaDB逻辑架构")
 
 当Mariadb接受到Sql语句时，其详细的执行过程如下：
 
@@ -819,11 +819,11 @@ MariaDB的架构如[图2](#fig13492418164520)所示。
 
 ### 配置环境
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >以下环境配置仅为参考示例，具体配置视实际需求做配置  
 #### 关闭防火墙并取消开机自启动
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >测试环境下通常会关闭防火墙以避免部分网络因素影响，视实际需求做配置。  
 
 1.  在root权限下停止防火墙。
@@ -838,7 +838,7 @@ MariaDB的架构如[图2](#fig13492418164520)所示。
     # systemctl disable firewalld
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >执行disable命令关闭防火墙的同时，也取消了开机自启动。  
 
 
@@ -853,7 +853,7 @@ MariaDB的架构如[图2](#fig13492418164520)所示。
 
 #### 创建组和用户
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >服务器环境下，为了系统安全，通常会为进程分配单独的用户，以实现权限隔离。本章节创建的组和用户都是操作系统层面的，不是数据库层面的。  
 
 1.  在root权限下创建MySQL用户（组）。
@@ -877,7 +877,7 @@ MariaDB的架构如[图2](#fig13492418164520)所示。
 
 #### 搭建数据盘
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >-   进行性能测试时，数据目录使用单独硬盘，需要对硬盘进行格式化并挂载，参考方法一或者方法二  
 >-   非性能测试时，在root权限下执行以下命令，创建数据目录即可。然后跳过本小节：  
 >    \#mkdir /data  
@@ -916,15 +916,15 @@ MariaDB的架构如[图2](#fig13492418164520)所示。
 
     其中，/dev/nvme0n1p1为示例，具体名称以实际情况为准。
 
-    ![](figures/搭建数据盘.png)
+    ![](./figures/Creating_DataDisk.png)
 
 
 ##### 方法二：在root权限下使用LVM进行磁盘管理
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >此步骤需要安装镜像中的lvm2相关包，步骤如下：  
 >
->1.  配置本地yum源，详细信息请参考[搭建repo服务器](搭建repo服务器.html)。如果已经执行，则可跳过此步。  
+>1.  配置本地yum源，详细信息请参考[搭建repo服务器](./搭建repo服务器.html)。如果已经执行，则可跳过此步。  
 >2.  在root权限下执行命令安装lvm2。  
 >   **\# yum install lvm2**  
 
@@ -966,7 +966,7 @@ MariaDB的架构如[图2](#fig13492418164520)所示。
 
     其中，/dev/datavg/datalv为示例，具体名称以实际情况为准。
 
-    ![](figures/D1376B2A-D036-41C4-B852-E8368F363B5E.png)
+    ![](./figures/D1376B2A-D036-41C4-B852-E8368F363B5E.png)
 
 
 #### 创建数据库目录并且授权
@@ -984,7 +984,7 @@ MariaDB的架构如[图2](#fig13492418164520)所示。
 ### 安装、运行和卸载
 #### 安装
 
-1.  配置本地yum源，详细信息请参考[搭建repo服务器](搭建repo服务器.html)。
+1.  配置本地yum源，详细信息请参考[搭建repo服务器](./搭建repo服务器.html)。
 2.  清除缓存。
 
     ```
@@ -1034,7 +1034,7 @@ MariaDB的架构如[图2](#fig13492418164520)所示。
 
     命令执行后提示输入密码。密码为[2](#li197143190587)中设置的密码。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >执行 **\\q** 或者 **exit** 可退出数据库。  
 
 
@@ -1169,7 +1169,7 @@ SET PASSWORD FOR 'username'@'hostname' = PASSWORD('newpassword');
 -   FOR 'username'@'hostname'：FOR字句，可选项，指定欲修改密码的用户名及主机名。
 -   PASSWORD\('newpassword'\)：表示使用函数PASSWORD\(\)设置新口令，即新口令必须传递到函数PASSWORD\(\)中进行加密。
 
->![](public_sys-resources/icon-caution.gif) **注意：**   
+>![](./public_sys-resources/icon-caution.gif) **注意：**   
 >PASSWORD\(\)函数为单向加密函数，一旦加密后不能解密出原明文。  
 
 在SET PASSWORD语句中，若不加上FOR子句，表示修改当前用户的密码。
@@ -1194,7 +1194,7 @@ FOR字句中必须以'username'@'hostname'的格式给定，username为账户的
 DROP USER 'username1'@'hostname1' [,'username2'@'hostname2']…;
 ```
 
->![](public_sys-resources/icon-caution.gif) **注意：**   
+>![](./public_sys-resources/icon-caution.gif) **注意：**   
 >用户的删除不会影响他们之前所创建的表、索引或其他数据库对象，因为数据库并不会记录创建了这些对象的账号。  
 
 DROP USER语句可用于删除一个或多个数据库账号，并删除其原有权限。
@@ -1320,7 +1320,7 @@ USE databasename;
 
 可以使用DROP DATABASE语句来删除数据库。
 
->![](public_sys-resources/icon-caution.gif) **注意：**   
+>![](./public_sys-resources/icon-caution.gif) **注意：**   
 >删除数据库要谨慎操作，一旦删除，数据库中的所有表和数据都会删除。  
 
 ```
@@ -1450,11 +1450,11 @@ MySQL所使用的SQL语言是用于访问数据库的最常用标准化语言。
 
 ### 配置环境
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >以下环境配置仅为参考示例，具体配置视实际需求做配置  
 #### 关闭防火墙并取消开机自启动
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >测试环境下通常会关闭防火墙以避免部分网络因素影响，视实际需求做配置。  
 
 1.  在root权限下停止防火墙。
@@ -1469,7 +1469,7 @@ MySQL所使用的SQL语言是用于访问数据库的最常用标准化语言。
     # systemctl disable firewalld
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >执行disable命令关闭防火墙的同时，也取消了开机自启动。  
 
 
@@ -1484,7 +1484,7 @@ MySQL所使用的SQL语言是用于访问数据库的最常用标准化语言。
 
 #### 创建组和用户
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >服务器环境下，为了系统安全，通常会为进程分配单独的用户，以实现权限隔离。本章节创建的组和用户都是操作系统层面的，不是数据库层面的。  
 
 1.  在root权限下创建MySQL用户（组）。
@@ -1508,7 +1508,7 @@ MySQL所使用的SQL语言是用于访问数据库的最常用标准化语言。
 
 #### 搭建数据盘
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >-   进行性能测试时，数据目录使用单独硬盘，需要对硬盘进行格式化并挂载，参考方法一或者方法二  
 >-   非性能测试时，在root权限下执行以下命令，创建数据目录即可。然后跳过本小节：  
 >    \# mkdir /data  
@@ -1547,14 +1547,14 @@ MySQL所使用的SQL语言是用于访问数据库的最常用标准化语言。
 
     其中，/dev/nvme0n1p1为示例，具体名称以实际情况为准。
 
-    ![](figures/搭建数据盘-0.png)
+    ![](./figures/Creating_DataDisk-0.png)
 
 
 ##### 方法二：在root权限下使用LVM进行磁盘管理
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >此步骤需要安装镜像中的lvm2相关包，步骤如下：  
->1.  配置本地yum源，详细信息请参考[搭建repo服务器](搭建repo服务器.html)。如果已经执行，则可跳过此步。  
+>1.  配置本地yum源，详细信息请参考[搭建repo服务器](./搭建repo服务器.html)。如果已经执行，则可跳过此步。  
 >2.  执行命令安装lvm2。  
 >    **\#yum install lvm2**  
 
@@ -1596,7 +1596,7 @@ MySQL所使用的SQL语言是用于访问数据库的最常用标准化语言。
 
     其中，/dev/datavg/datalv为示例，具体名称以实际情况为准。
 
-    ![](figures/D1376B2A-D036-41C4-B852-E8368F363B5E-1.png)
+    ![](./figures/D1376B2A-D036-41C4-B852-E8368F363B5E-1.png)
 
 
 #### 创建数据库目录并且授权
@@ -1613,8 +1613,18 @@ MySQL所使用的SQL语言是用于访问数据库的最常用标准化语言。
 
 ### 安装、运行和卸载
 #### 安装
-
-1.  配置本地yum源，详细信息请参考[搭建repo服务器](搭建repo服务器.html)章节。
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>针对20.03LTS版本，如果用户从mysql-8.0.17-3.oe1版本升级到较新版本，使用rpm -Uvh xxx（其中XXX指具体的版本，例如mysql-8.0.21-1.oe1.aarch64.rpm）命令，升级后功能不可用，可以通过以下两种方式进行版本升级（以mysql-8.0.17-3.oe1升级到mysql-8.0.21-1.oe1举例）：
+>- 方法1，执行如下升级命令实现：  
+>   ``` 
+>   # rpm -Uvh mysql-8.0.21-1.oe1.aarch64.rpm --noscripts 
+>   ```
+>- 方法2，先卸载旧版本的mysql，再安装新版本的mysql，命令如下：
+>   ```
+>   # rpm -e mysql-8.0.17-3.oe1       
+>   # rpm -ivh mysql-8.0.21-1.oe1.aarch64.rpm
+>   ``` 
+1.  配置本地yum源，详细信息请参考[搭建repo服务器](./搭建repo服务器.html)章节。
 2.  清除缓存。
 
     ```
@@ -1677,9 +1687,9 @@ MySQL所使用的SQL语言是用于访问数据库的最常用标准化语言。
         $ cat /etc/my.cnf
         ```
 
-        ![](figures/zh-cn_image_0231563132.png)
+        ![](./figures/zh-cn_image_0231563132.png)
 
-        >![](public_sys-resources/icon-caution.gif) **注意：**   
+        >![](./public_sys-resources/icon-caution.gif) **注意：**   
         >其中basedir为软件安装路径，请根据实际情况修改。  
 
     3.  在root权限下修改/etc/my.cnf文件的组和用户为mysql:mysql
@@ -1695,7 +1705,7 @@ MySQL所使用的SQL语言是用于访问数据库的最常用标准化语言。
         # echo export  PATH=$PATH:/usr/local/mysql/bin  >> /etc/profile
         ```
 
-        >![](public_sys-resources/icon-caution.gif) **注意：**   
+        >![](./public_sys-resources/icon-caution.gif) **注意：**   
         >其中PATH中的“/usr/local/mysql/bin“路径，为MySQL软件安装目录下的bin文件的绝对路径。请根据实际情况修改。  
 
     2.  在root权限下使环境变量配置生效。
@@ -1706,7 +1716,7 @@ MySQL所使用的SQL语言是用于访问数据库的最常用标准化语言。
 
 3.  在root权限下初始化数据库。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >本步骤倒数第2行中有初始密码，请注意保存，登录数据库时需要使用。  
 
     ```
@@ -1720,7 +1730,7 @@ MySQL所使用的SQL语言是用于访问数据库的最常用标准化语言。
 
 4.  启动数据库。
 
-    >![](public_sys-resources/icon-caution.gif) **注意：**   
+    >![](./public_sys-resources/icon-caution.gif) **注意：**   
     >如果第一次启动数据库服务，以root用户启动数据库，则启动时会提示缺少mysql.log文件而导致失败。使用mysql用户启动之后，会在/data/mysql/log目录下生成mysql.log文件，再次使用root用户启动则不会报错。  
 
     1.  在root权限下修改文件权限。
@@ -1745,7 +1755,7 @@ MySQL所使用的SQL语言是用于访问数据库的最常用标准化语言。
 
 5.  登录数据库。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >-   提示输入密码时，请输入[3](#li15634560582)产生的初始密码。  
     >-   如果采用官网RPM安装方式，则mysql文件在/usr/bin目录下。登录数据库的命令根据实际情况修改。  
 
@@ -1753,7 +1763,7 @@ MySQL所使用的SQL语言是用于访问数据库的最常用标准化语言。
     $ /usr/local/mysql/bin/mysql -uroot -p  -S /data/mysql/run/mysql.sock
     ```
 
-    ![](figures/zh-cn_image_0231563134.png)
+    ![](./figures/zh-cn_image_0231563134.png)
 
 6.  配置数据库帐号密码。
     1.  登录数据库以后，修改通过root用户登录数据库的密码。
@@ -1775,7 +1785,7 @@ MySQL所使用的SQL语言是用于访问数据库的最常用标准化语言。
         mysql> flush privileges;
         ```
 
-        ![](figures/zh-cn_image_0231563135.png)
+        ![](./figures/zh-cn_image_0231563135.png)
 
 7.  退出数据库。
 
@@ -1785,7 +1795,7 @@ MySQL所使用的SQL语言是用于访问数据库的最常用标准化语言。
     mysql> exit
     ```
 
-    ![](figures/zh-cn_image_0231563136.png)
+    ![](./figures/zh-cn_image_0231563136.png)
 
 
 #### 卸载
@@ -1941,7 +1951,7 @@ FOR字句中必须以'username'@'hostname'的格式给定，username为账户的
 DROP USER 'username1'@'hostname1' [,'username2'@'hostname2']…;
 ```
 
->![](public_sys-resources/icon-caution.gif) **注意：**   
+>![](./public_sys-resources/icon-caution.gif) **注意：**   
 >用户的删除不会影响他们之前所创建的表、索引或其他数据库对象，因为数据库并不会记录创建了这些对象的账号。  
 
 DROP USER语句可用于删除一个或多个数据库账号，并删除其原有权限。
@@ -2067,7 +2077,7 @@ USE databasename;
 
 可以使用DROP DATABASE语句来删除数据库。
 
->![](public_sys-resources/icon-caution.gif) **注意：**   
+>![](./public_sys-resources/icon-caution.gif) **注意：**   
 >删除数据库要谨慎操作，一旦删除，数据库中的所有表和数据都会删除。  
 
 ```
diff --git "a/content/zh/docs/Administration/\346\220\255\345\273\272\346\234\215\345\212\241.md" "b/docs/zh/docs/20.03_LTS/docs/Administration/\346\220\255\345\273\272\346\234\215\345\212\241.md"
similarity index 100%
rename from "content/zh/docs/Administration/\346\220\255\345\273\272\346\234\215\345\212\241.md"
rename to "docs/zh/docs/20.03_LTS/docs/Administration/\346\220\255\345\273\272\346\234\215\345\212\241.md"
diff --git "a/content/zh/docs/Administration/\346\237\245\347\234\213\347\263\273\347\273\237\344\277\241\346\201\257.md" "b/docs/zh/docs/20.03_LTS/docs/Administration/\346\237\245\347\234\213\347\263\273\347\273\237\344\277\241\346\201\257.md"
similarity index 75%
rename from "content/zh/docs/Administration/\346\237\245\347\234\213\347\263\273\347\273\237\344\277\241\346\201\257.md"
rename to "docs/zh/docs/20.03_LTS/docs/Administration/\346\237\245\347\234\213\347\263\273\347\273\237\344\277\241\346\201\257.md"
index c96e6112cdf7d80a9728c91607f194c1e810d926..b39442fe9ae3b06880a5a7ba45841bc7c8ce2ad4 100644
--- "a/content/zh/docs/Administration/\346\237\245\347\234\213\347\263\273\347\273\237\344\277\241\346\201\257.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Administration/\346\237\245\347\234\213\347\263\273\347\273\237\344\277\241\346\201\257.md"
@@ -1,46 +1,46 @@
-# 查看系统信息
-
--   查看系统信息，命令如下：
-
-    ```
-    $ cat /etc/os-release
-    ```
-
-    例如，命令和输出如下：
-
-    ```
-    $ cat /etc/os-release
-    NAME="openEuler"
-    VERSION="20.09"
-    ID="openEuler"
-    VERSION_ID="20.09"
-    PRETTY_NAME="openEuler 20.09"
-    ANSI_COLOR="0;31"
-    ```
-
-
--   查看系统相关的资源信息。
-
-    查看CPU信息，命令如下：
-
-    ```
-    $ lscpu
-    ```
-
-    查看内存信息，命令如下：
-
-    ```
-    $ free
-    ```
-
-    查看磁盘信息，命令如下：
-
-    ```
-    $ fdisk -l
-    ```
-
--   查看系统资源实时信息，命令如下：
-
-    ```
-    $ top
-    ```
+# 查看系统信息
+
+-   查看系统信息，命令如下：
+
+    ```
+    $ cat /etc/os-release
+    ```
+
+    例如，命令和输出如下：
+
+    ```
+    $ cat /etc/os-release
+    NAME="openEuler"
+    VERSION="20.03 (LTS)"
+    ID="openEuler"
+    VERSION_ID="20.03"
+    PRETTY_NAME="openEuler 20.03 (LTS)"
+    ANSI_COLOR="0;31"
+    ```
+
+
+-   查看系统相关的资源信息。
+
+    查看CPU信息，命令如下：
+
+    ```
+    $ lscpu
+    ```
+
+    查看内存信息，命令如下：
+
+    ```
+    $ free
+    ```
+
+    查看磁盘信息，命令如下：
+
+    ```
+    $ fdisk -l
+    ```
+    查看系统资源实时信息，命令如下：
+
+    ```
+    $ top
+    ```
+
diff --git "a/content/zh/docs/Administration/\347\256\241\347\220\206\346\234\215\345\212\241.md" "b/docs/zh/docs/20.03_LTS/docs/Administration/\347\256\241\347\220\206\346\234\215\345\212\241.md"
similarity index 98%
rename from "content/zh/docs/Administration/\347\256\241\347\220\206\346\234\215\345\212\241.md"
rename to "docs/zh/docs/20.03_LTS/docs/Administration/\347\256\241\347\220\206\346\234\215\345\212\241.md"
index 4ad3fba84371272ea948a9ef2a52d4af97faf311..9ad11554dbbc02828fb74e04f65b703e2af51382 100644
--- "a/content/zh/docs/Administration/\347\256\241\347\220\206\346\234\215\345\212\241.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Administration/\347\256\241\347\220\206\346\234\215\345\212\241.md"
@@ -53,148 +53,89 @@ systemd开启和监督整个系统是基于unit的概念。unit是由一个与
 
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
-
-
-
-
-
-
-
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
unit名称

 
后缀名

 
描述

 

 
Service unit

 
.service

 
系统服务。

 
Target unit

 
.target

 
一组systemd units。

 
Automount unit

 
.automount

 
文件系统挂载点。

 
Device unit

 
.device

 
内核识别的设备文件。

 
Mount unit

 
.mount

 
文件系统挂载点。

 
Path unit

 
.path

 
在一个文件系统中的文件或目录。

 
Scope unit

 
.scope

 
外部创建的进程。

 
Slice unit

 
.slice

 
一组用于管理系统进程分层组织的units。

 
Snapshot unit

-
.snapshot

-
systemd manager的保存状态。

-
Socket unit

 
.socket

 
一个进程间通信的Socket。

 
Swap unit

 
.swap

 
swap设备或者swap文件。

 
Timer unit

 
.timer

 
systemd计时器。

 

 

 
@@ -205,37 +146,25 @@ systemd开启和监督整个系统是基于unit的概念。unit是由一个与
 
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
-
 
路径

 
描述

 

 
/usr/lib/systemd/system/

 
随安装的RPM产生的systemd units。

 
/run/systemd/system/

 
在运行时创建systemd units。

 
/etc/systemd/system/

 
由系统管理员创建和管理的systemd units。

 

 

 
@@ -795,7 +724,7 @@ Give root password for maintenance
 (or press Control-D to continue):
 ```
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >用户需要重启系统，从救援模式进入正常模式。  
 
 ### 切换到紧急模式
@@ -814,7 +743,7 @@ Give root password for maintenance
 (or press Control-D to continue):
 ```
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >用户需要重启系统，从紧急模式进入正常模式。  
 
 ## 关闭、暂停和休眠系统
diff --git "a/content/zh/docs/Administration/\347\256\241\347\220\206\347\224\250\346\210\267\345\222\214\347\224\250\346\210\267\347\273\204.md" "b/docs/zh/docs/20.03_LTS/docs/Administration/\347\256\241\347\220\206\347\224\250\346\210\267\345\222\214\347\224\250\346\210\267\347\273\204.md"
similarity index 97%
rename from "content/zh/docs/Administration/\347\256\241\347\220\206\347\224\250\346\210\267\345\222\214\347\224\250\346\210\267\347\273\204.md"
rename to "docs/zh/docs/20.03_LTS/docs/Administration/\347\256\241\347\220\206\347\224\250\346\210\267\345\222\214\347\224\250\346\210\267\347\273\204.md"
index f207145e2f27c81a56a4999da2bc1637ef2d19a2..200ffcae1af23f3d10bbdceb857e541d88a3c630 100644
--- "a/content/zh/docs/Administration/\347\256\241\347\220\206\347\224\250\346\210\267\345\222\214\347\224\250\346\210\267\347\273\204.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Administration/\347\256\241\347\220\206\347\224\250\346\210\267\345\222\214\347\224\250\346\210\267\347\273\204.md"
@@ -52,7 +52,7 @@ useradd [options] username
 # useradd userexample
 ```
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >没有任何提示，表明用户建立成功。这时并没有设置用户的口令，请使用passwd命令修改用户的密码，没有设置密码的新账号不能登录系统。  
 
 
@@ -101,7 +101,7 @@ Retype new password:
 passwd: all authentication tokens updated successfully.
 ```
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >若打印信息中出现“BAD PASSWORD: The password fails the dictionary check - it is too simplistic/sytematic”，表示设置的密码过于简单，建议设置复杂度较高的密码。  
 
 ### 修改用户账号
@@ -171,7 +171,7 @@ usermod -e MM/DD/YY username
 
 如果想同时删除该用户的主目录以及其中所有内容，要使用-r参数递归删除。
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >不建议直接删除已经进入系统的用户，如果需要强制删除，请使用 userdel -f  _Test_  命令。  
 
 ### 管理员账户授权
@@ -223,7 +223,7 @@ sudo /usr/sbin/useradd newuserl
 
     这一句说明ted1主机上的newuser1具有以root用户权限执行useradd，userdel命令的功能。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >-   可以在一行定义多个别名，中间用冒号 \(:\) 隔开。  
     >-   可在命令或命令别名之前加上感叹号 \(!\)，使该命令或命令别名无效。  
     >-   有两个关键词：ALL和NOPASSWD。ALL意味着“所有”（所有文件、所有主机或所有命令），NOPASSWD意味着不用密码。  
@@ -312,7 +312,7 @@ groupmod -n newgroupname oldgroupname
 # groupdel Test
 ```
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >groupdel不能直接删除用户的主组，如果需要强制删除用户主组，请使用 groupdel -f  _Test_  命令。  
 
 ### 将用户加入用户组或从用户组中移除
diff --git "a/content/zh/docs/Administration/\347\256\241\347\220\206\350\277\233\347\250\213.md" "b/docs/zh/docs/20.03_LTS/docs/Administration/\347\256\241\347\220\206\350\277\233\347\250\213.md"
similarity index 98%
rename from "content/zh/docs/Administration/\347\256\241\347\220\206\350\277\233\347\250\213.md"
rename to "docs/zh/docs/20.03_LTS/docs/Administration/\347\256\241\347\220\206\350\277\233\347\250\213.md"
index e966f9c0d46a438942975c562345ec3b1bc4d99b..d2ed83f8847d12f953ef9290261e2d9e62538d25 100644
--- "a/content/zh/docs/Administration/\347\256\241\347\220\206\350\277\233\347\250\213.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Administration/\347\256\241\347\220\206\350\277\233\347\250\213.md"
@@ -1,350 +1,350 @@
-# 管理进程
-
-操作系统管理多个用户的请求和多个任务。大多数系统都只有一个CPU和一个主要存储，但一个系统可能有多个二级存储磁盘和多个输入/输出设备。操作系统管理这些资源并在多个用户间共享资源，当用户提出一个请求时，造成好像系统被用户独占的假象。实际上操作系统监控着一个等待执行的任务队列，这些任务包括用户任务、操作系统任务、邮件和打印任务等。本章节将从用户的角度讲述如何控制进程。
-
-
-- [管理进程](#管理进程)
-    - [查看进程](#查看进程)
-        - [who命令](#who命令)
-        - [ps命令](#ps命令)
-        - [top命令](#top命令)
-        - [kill命令](#kill命令)
-    - [调度启动进程](#调度启动进程)
-        - [定时运行一批程序（at）](#定时运行一批程序at)
-        - [周期性运行一批程序（cron）](#周期性运行一批程序cron)
-    - [挂起/恢复进程](#挂起恢复进程)
-
-
-## 查看进程
-
-Linux是一个多任务系统，经常需要对这些进程进行一些调配和管理。要进行管理，首先就要知道现在的进程情况：有哪些进程、进程的状态如何等。Linux提供了多种命令来了解进程的状况。
-
-### who命令
-
-who命令主要用于查看当前系统中的用户情况。如果用户想和其他用户建立即时通讯，比如使用talk命令，那么首先要确定的就是该用户确实在线上，不然talk进程就无法建立起来。又如，系统管理员希望监视每个登录的用户此时此刻的所作所为，也要使用who命令。who命令应用起来非常简单，可以比较准确地掌握用户的情况，所以使用非常广泛。
-
-例如查看系统中的用户及其状态。使用如下：
-
-```
-$ who
-admin     tty1         Jul 28 15:55
-admin     pts/0        Aug  5 15:46 (192.168.0.110)
-admin     pts/2        Jul 29 19:52 (192.168.0.110)
-root     pts/3        Jul 30 12:07 (192.168.0.110)
-root     pts/4        Jul 31 10:29 (192.168.0.144)
-root     pts/5        Jul 31 14:52 (192.168.0.11)
-root     pts/6        Aug  6 10:12 (192.168.0.234)
-root     pts/8        Aug  6 11:34 (192.168.0.234)
-```
-
-### ps命令
-
-ps命令是最基本又非常强大的进程查看命令。使用该命令可以确定有哪些进程正在运行和运行的状态、进程是否结束、进程有没有僵尸、哪些进程占用了过多的资源等，大部分进程信息都是可以通过执行该命令得到的。
-
-ps命令最常用的还是用来监控后台进程的工作情况，因为后台进程是不与屏幕、键盘这些标准输入/输出设备进行通信的，所以如果需要检测其状况，就可使用ps命令。ps命令的常见选项如[表1](#zh-cn_topic_0151921029_t34619d964a3d41ad8694189ec383359c)所示。
-
-**表 1**  选项说明
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
选项

-
描述

-
-e

-
显示所有进程。

-
-f

-
全格式。

-
-h

-
不显示标题。

-
-l

-
使用长格式。

-
-w

-
宽行输出。

-
-a

-
显示终端上的所有进程，包括其他用户的进程。

-
-r

-
只显示正在运行的进程。

-
-x

-
显示没有控制终端的进程。

-

-
-例如显示系统中终端上的所有进行进程。命令如下：
-
-```
-$ ps -a
-  PID TTY          TIME CMD
-12175 pts/6    00:00:00 bash
-24526 pts/0    00:00:00 vsftpd
-29478 pts/5    00:00:00 ps
-32461 pts/0    1-01:58:33 sh
-```
-
-### top命令
-
-top命令和ps命令的基本作用是相同的，显示系统当前的进程和其他状况，但是top是一个动态显示过程，即可以通过用户按键来不断刷新进程的当前状态，如果在前台执行该命令，它将独占前台，直到用户终止该程序为止。其实top命令提供了实时的对系统处理器的状态监视。它将显示系统中CPU的任务列表。该命令可以按CPU使用、内存使用和执行时间对任务进行排序，而且该命令的很多特性都可以通过交互式命令或者在定制文件中进行设定。
-
-top命令输出的实例如[图1](#zh-cn_topic_0151921029_f289234fcdbac453796200d80e9889cd1)所示：
-
-**图 1**  top显示  
-![](figures/top显示.png "top显示")
-
-### kill命令
-
-当需要中断一个前台进程的时候，通常足使用“Ctrl+c”组合键，而对于后台进程不能用组合键来终止，这时就可以使用kill命令。该命令可以终止前台和后台进程。终止后台进程的原因包括：该进程占用CPU的时间过多、该进程已经死锁等。
-
-kill命令是通过向进程发送指定的信号来结束进程的。如果没有指定发送的信号，那么默认值为TERM信号。TERM信号将终止所有不能捕获该信号的进程。至于那些可以捕获该信号的进程可能就需要使用KILL信号（它的编号为9），而该信号不能被捕捉。
-
-kill命令的浯法格式有以下两种方式：
-
-```
-kill [-s 信号 | -p] [-a] 进程号…
-kill -l [信号]
-```
-
-其中进程号可以通过ps命令的输出得到。-s选项是给程序发送指定的信号，详细的信号可以用“kill -l”命令查看；-p选项只显示指定进程的ID号。
-
-杀死pid为1409的进程，在root权限下执行如下命令：
-
-```
-# kill -9 1409
-```
-
-显示所有的信号及其编号对应关系，示例如下：
-
-```
-$ kill -l
- 1) SIGHUP       2) SIGINT       3) SIGQUIT      4) SIGILL       5) SIGTRAP
- 6) SIGABRT      7) SIGBUS       8) SIGFPE       9) SIGKILL     10) SIGUSR1
-11) SIGSEGV     12) SIGUSR2     13) SIGPIPE     14) SIGALRM     15) SIGTERM
-16) SIGSTKFLT   17) SIGCHLD     18) SIGCONT     19) SIGSTOP     20) SIGTSTP
-21) SIGTTIN     22) SIGTTOU     23) SIGURG      24) SIGXCPU     25) SIGXFSZ
-26) SIGVTALRM   27) SIGPROF     28) SIGWINCH    29) SIGIO       30) SIGPWR
-31) SIGSYS      34) SIGRTMIN    35) SIGRTMIN+1  36) SIGRTMIN+2  37) SIGRTMIN+3
-38) SIGRTMIN+4  39) SIGRTMIN+5  40) SIGRTMIN+6  41) SIGRTMIN+7  42) SIGRTMIN+8
-43) SIGRTMIN+9  44) SIGRTMIN+10 45) SIGRTMIN+11 46) SIGRTMIN+12 47) SIGRTMIN+13
-48) SIGRTMIN+14 49) SIGRTMIN+15 50) SIGRTMAX-14 51) SIGRTMAX-13 52) SIGRTMAX-12
-53) SIGRTMAX-11 54) SIGRTMAX-10 55) SIGRTMAX-9  56) SIGRTMAX-8  57) SIGRTMAX-7
-58) SIGRTMAX-6  59) SIGRTMAX-5  60) SIGRTMAX-4  61) SIGRTMAX-3  62) SIGRTMAX-2
-63) SIGRTMAX-1  64) SIGRTMAX
-```
-
-## 调度启动进程
-
-有时候需要对系统进行一些比较费时而且占用资源的维护工作，这些工作适合在深夜进行，这时候用户就可以事先进行调度安排，指定任务运行的时间或者场合，到时候系统会自动完成这些任务。要使用自动启动进程的功能，就需要掌握以下几个启动命令。
-
-
-
-### 定时运行一批程序（at）
-
-#### at命令
-
-用户使用at命令在指定时刻执行指定的命令序列。该命令至少需要指定一个命令和一个执行时间。at命令可以只指定时间，也可以时间和日期一起指定。
-
-at命令的语法格式如下：
-
-```
- at [-V] [-q 队列] [-f 文件名] [-mldbv] 时间
- at -c 作业 [作业…]
-```
-
-#### 设置时间
-
-at允许使用一套相当复杂的时间指定方法，比如：
-
--   接受在当天的hh:mm（小时：分钟）式的时间指定。如果该时间已经过去，那么就放存第二天执行。
--   使用midnight（深夜）、noon（中午）、teatime（饮茶时间，一般是下午4点）等比较模糊的词语来指定时间。
--   采用12小时计时制，即在时间后面加上AM（上午）或者PM（下午）来说明是上午还是下午。
--   指定命令执行的具体日期，指定格式为month day（月日）或者mm/dd/yy（月/日/年）或者dd.mm.yy（日.月.年）。指定的日期必须跟在指定时间的后面。
-
-上面介绍的都是绝对计时法，其实还可以使用相对计时法，这对于安排不久就要执行的命令是很有好处的。指定格式为now+count time-units，now就是当前时间，time-units是时间单位，这里可以是minutes（分钟）、hours（小时）、days（天）、weeks（星期）。count是时间的数量，究竟是几天，还是几小时等。还有一种计时方法就是直接使用today（今天）、tomorrow（明天）来指定完成命令的时间。下面通过一些例子来说明具体用法。
-
-例如指定在今天下午4:30执行某个命令。假设现在时间是中午12:30，2019年6月7日，可用命令格式如下：
-
-```
- at 4:30pm
- at 16:30
- at 16:30 today
- at now+4 hours
- at now+ 240 minutes
- at 16:30 7.6.19
- at 16:30 6/7/19
- at 16:30 Jun 7
-```
-
-以上这些命令表达的意义是完全一样的，所以在安排时间的时候完全可以根据个人喜好和具体情况自由选择。一般采用绝对时间的24小时计时法可以避免由于用户自己的疏忽造成计时错误，例如上例可以写成：at 16:30 6/7/19。
-
-#### 执行权限
-
-对于at命令来说，需要定时执行的命令是从标准输入或者使用-f选项指定的文件中读取并执行的。如果at命令是从一个使用su命令切换到用户shell中执行的，那么当前用户被认为是执行用户，所有的错误和输出结果都会送给这个用户。但是如果有邮件送出的话，收到邮件的将是原来的用户，也就是登录时shell的所有者。
-
-例如在6月8日上午10点执行slocate -u命令。在root权限下执行命令如下：
-
-```
-# at  10:00  6/8/19
-at> slocate -u
-at>
-[1]+   Stopped    at  10:00  6/8/19
-```
-
-上面的结果中，输入at命令之后，会出现提示符at\>，提示用户输入命令，在此输入了slocate -u，然后按回车键。还可以输入多条命令，当所有要执行的命令输入结束后，按Ctrl+d键结束at命令。
-
-在任何情况下，管理员账户都可以使用这个命令。对于其他用户来说，是否可以使用就取决于/etc/at.allow和/etc/at.deny文件。
-
-### 周期性运行一批程序（cron）
-
-前面介绍at命令都会在一定时间内完成一定任务，但是它只能执行一次。也就是说，当指定了运行命令后，系统在指定时间完成任务，以后就不再执行了。但是在很多情况下需要周期性重复执行一些命令，这时候就需要使用cron命令来完成任务。
-
-#### 运行机制
-
-首先cron命令会搜索/var/spool/cron目录，寻找以/etc/passwd文件中的用户名命名的crontab文件，被找到的这种文件将装入内存。比如一个用户名为userexample的用户，对应的crontab文件应该是/var/spool/cron/userexample，即以该用户命名的crontab文件存放在/var/spool/cron目录下面。
-
-cron命令还将搜索/etc/crontab文件，这个文件是用不同的格式写成的。cron启动以后，它将首先检查是否有用户设置了crontab文件，如果没有就转入睡眠状态，释放系统资源。所以该后台进程占用资源极少，它每分钟被换醒一次，查看当前是否有需要运行的命令。
-
-命令执行结束后，任何输出都将作为邮件发送给crontab的所有者，或者是/etc/crontab文件中MAILTO环境变量中指定的用户。这是cron的工作原理，但是cron命令的执行不需要用户干涉，用户只需要修改crontab中要执行的命令。
-
-#### crontab命令
-
-crontab命令用于安装、删除或者显示用于驱动cron后台进程的表格。用户把需要执行的命令序列放到crontab文件中以获得执行，而且每个用户都可以有自己的crontab文件。
-
-crontab命令的常用方法如下：
-
--   crontab -u   //设置某个用户的cron服务，root用户在执行crontab时需要此参数。
--   crontab -l    //列出某个用户cron服务的详细内容。
--   crontab -r   //删除某个用户的cron服务。
--   crontab -e  //编辑某个用户的cron服务。
-
-例如root查看自己的cron设置。命令如下：
-
-```
-# crontab -u root -l
-```
-
-#### crontab文件
-
-在crontab文件中输入需要执行的命令和时间。该文件中每行都包括6个域，其中前5个域是指定命令被执行的时间，最后一个域是要被执行的命令。每个域之间使用空格或者制表符分隔。格式如下：
-
-```
-minute hour day-of-month month-of-year day-of-week commands
-```
-
-对于每一项的说明如所示。
-
-**表 2**  参数说明
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
参数

-
描述

-
minute

-
分钟（0~59）。

-
hour

-
小时（0~23）。

-
day-of-month

-
一个月的第几天（1~31）。

-
month-of-year

-
一年的第几个月（1~12）。

-
day-of-week

-
一周的星期几（0~6），0代表星期天。

-
commands

-
需要执行的命令。

-

-
-这些项都不能为空，必须指定值。除了数字还有几个特殊的符号“\*”、“/”和“-”、“，”。其中，\*代表所有的取值范围内的数字，/代表每的意思，“\*/5”表示每5个单位，“-”代表从某个数字到某个数字，“，”分开几个离散时数字。对于要执行的命令，调用的时候需要写出命令的完整路径。
-
-例如晚上18点到22点之间每两个小时，在/tmp/test.txt文件中加入sleepy文本。在crontab文件中对应的行如下：
-
-```
-* 18-22/2 * * * echo "sleepy" >> /tmp/test.txt
-```
-
-每次编辑完某个用户的cron设置后，cron自动在/var/spool/cron下生成一个与此用户同名的文件。此用户的cron信息都记录在这个文件中，这个文件是不可以直接编辑的，只可以用crontab -e来编辑。用户也可以另外建立一个文件，使用“cron文件名”命令导入cron设置。
-
-假设有个用户名为userexample，它需要为自己创建的一个crontab文件。步骤如下：
-
-1.  首先可以使用任何文本编辑器建立一个新文件，并将向该文件加入需要运行的命令和要定期执行的时间，假设该文件为 \~/userexample.cron。
-2.  然后在root权限下使用crontab命令安装这个文件，使用crontab命令使之成为该用户的crontab文件。命令如下：
-
-    ```
-    # crontab -u userexample ~/userexample.cron
-    ```
-
-
-这样crontab文件就建立好了，可以转到/var/spool/cron目录下面查看，发现多了一个userexample文件。这个文件就是所需的crontab文件。
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->cron启动后，每过一分钟读一次crontab文件，检查是否要执行里面的命令。因此该文件被修改后不需要重新启动cron服务。  
-
-#### 编辑配置文件
-
-cron服务每分钟不仅要读一次/var/spool/cron内的所有文件，还需要读一次/etc/crontab，因此通过配置这个文件也能得到cron的服务。用crontab配置是针对某个用户的，而编辑/etc/crontab是针对系统的任务。此文件的文件格式如下：
-
-```
-SHELL=/bin/sh
-PATH=/usr/bin:/usr/sbin:/sbin:/bin:/usr/lib/news/bin
-MAILTO=root  //如果出现错误，或者有数据输出，数据作为邮件发给这个账号
-HOME=/
-#  run-parts
-01  * * * *   root run-parts /etc/cron.hourly     //每个小时执行一次/etc/cron.hourly里的脚本
-02 4 * * *   root run-parts /etc/cron.daily    //每天执行一次/etc/cron.daily里的脚本
-22 4 * * 0  root run-parts /etc/cron.weekly     //每周执行一次/etc/cron.weekly里的脚本
-42 4 1  * *  root run-parts /etc/cron.monthly     //每月执行一次/etc/cron.monthly里的脚本
-```
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->如果去掉run-parts参数，其后面就是运行的某个脚本名，而不是目录名。  
-
-## 挂起/恢复进程
-
-作业控制允许进程挂起并可以在需要时恢复进程的运行，被挂起的作业恢复后将从中止处开始继续运行。只要在键盘上按Ctrl+Z键，即可挂起当前的前台作业。在键盘上按Ctrl+Z键后，将挂起当前执行的命令cat。使用jobs命令可以显示shell的作业清单，包括具体的作业、作业号以及作业当前所处的状态。
-
-恢复进程执行时，有两种选择：用fg命令将挂起的作业放回到前台执行；用bg命令将挂起的作业放到后台执行。灵活使用上述命令，将给自己带来很大的方便。
-
+# 管理进程
+
+操作系统管理多个用户的请求和多个任务。大多数系统都只有一个CPU和一个主要存储，但一个系统可能有多个二级存储磁盘和多个输入/输出设备。操作系统管理这些资源并在多个用户间共享资源，当用户提出一个请求时，造成好像系统被用户独占的假象。实际上操作系统监控着一个等待执行的任务队列，这些任务包括用户任务、操作系统任务、邮件和打印任务等。本章节将从用户的角度讲述如何控制进程。
+
+
+- [管理进程](#管理进程)
+    - [查看进程](#查看进程)
+        - [who命令](#who命令)
+        - [ps命令](#ps命令)
+        - [top命令](#top命令)
+        - [kill命令](#kill命令)
+    - [调度启动进程](#调度启动进程)
+        - [定时运行一批程序（at）](#定时运行一批程序at)
+        - [周期性运行一批程序（cron）](#周期性运行一批程序cron)
+    - [挂起/恢复进程](#挂起恢复进程)
+
+
+## 查看进程
+
+Linux是一个多任务系统，经常需要对这些进程进行一些调配和管理。要进行管理，首先就要知道现在的进程情况：有哪些进程、进程的状态如何等。Linux提供了多种命令来了解进程的状况。
+
+### who命令
+
+who命令主要用于查看当前系统中的用户情况。如果用户想和其他用户建立即时通讯，比如使用talk命令，那么首先要确定的就是该用户确实在线上，不然talk进程就无法建立起来。又如，系统管理员希望监视每个登录的用户此时此刻的所作所为，也要使用who命令。who命令应用起来非常简单，可以比较准确地掌握用户的情况，所以使用非常广泛。
+
+例如查看系统中的用户及其状态。使用如下：
+
+```
+$ who
+admin     tty1         Jul 28 15:55
+admin     pts/0        Aug  5 15:46 (192.168.0.110)
+admin     pts/2        Jul 29 19:52 (192.168.0.110)
+root     pts/3        Jul 30 12:07 (192.168.0.110)
+root     pts/4        Jul 31 10:29 (192.168.0.144)
+root     pts/5        Jul 31 14:52 (192.168.0.11)
+root     pts/6        Aug  6 10:12 (192.168.0.234)
+root     pts/8        Aug  6 11:34 (192.168.0.234)
+```
+
+### ps命令
+
+ps命令是最基本又非常强大的进程查看命令。使用该命令可以确定有哪些进程正在运行和运行的状态、进程是否结束、进程有没有僵尸、哪些进程占用了过多的资源等，大部分进程信息都是可以通过执行该命令得到的。
+
+ps命令最常用的还是用来监控后台进程的工作情况，因为后台进程是不与屏幕、键盘这些标准输入/输出设备进行通信的，所以如果需要检测其状况，就可使用ps命令。ps命令的常见选项如[表1](#zh-cn_topic_0151921029_t34619d964a3d41ad8694189ec383359c)所示。
+
+**表 1**  选项说明
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
选项

+
描述

+
-e

+
显示所有进程。

+
-f

+
全格式。

+
-h

+
不显示标题。

+
-l

+
使用长格式。

+
-w

+
宽行输出。

+
-a

+
显示终端上的所有进程，包括其他用户的进程。

+
-r

+
只显示正在运行的进程。

+
-x

+
显示没有控制终端的进程。

+

+
+例如显示系统中终端上的所有进行进程。命令如下：
+
+```
+$ ps -a
+  PID TTY          TIME CMD
+12175 pts/6    00:00:00 bash
+24526 pts/0    00:00:00 vsftpd
+29478 pts/5    00:00:00 ps
+32461 pts/0    1-01:58:33 sh
+```
+
+### top命令
+
+top命令和ps命令的基本作用是相同的，显示系统当前的进程和其他状况，但是top是一个动态显示过程，即可以通过用户按键来不断刷新进程的当前状态，如果在前台执行该命令，它将独占前台，直到用户终止该程序为止。其实top命令提供了实时的对系统处理器的状态监视。它将显示系统中CPU的任务列表。该命令可以按CPU使用、内存使用和执行时间对任务进行排序，而且该命令的很多特性都可以通过交互式命令或者在定制文件中进行设定。
+
+top命令输出的实例如[图1](#zh-cn_topic_0151921029_f289234fcdbac453796200d80e9889cd1)所示：
+
+**图 1**  top显示  
+![](./figures/Top_Display.png)
+
+### kill命令
+
+当需要中断一个前台进程的时候，通常足使用“Ctrl+c”组合键，而对于后台进程不能用组合键来终止，这时就可以使用kill命令。该命令可以终止前台和后台进程。终止后台进程的原因包括：该进程占用CPU的时间过多、该进程已经死锁等。
+
+kill命令是通过向进程发送指定的信号来结束进程的。如果没有指定发送的信号，那么默认值为TERM信号。TERM信号将终止所有不能捕获该信号的进程。至于那些可以捕获该信号的进程可能就需要使用KILL信号（它的编号为9），而该信号不能被捕捉。
+
+kill命令的浯法格式有以下两种方式：
+
+```
+kill [-s 信号 | -p] [-a] 进程号…
+kill -l [信号]
+```
+
+其中进程号可以通过ps命令的输出得到。-s选项是给程序发送指定的信号，详细的信号可以用“kill -l”命令查看；-p选项只显示指定进程的ID号。
+
+杀死pid为1409的进程，在root权限下执行如下命令：
+
+```
+# kill -9 1409
+```
+
+显示所有的信号及其编号对应关系，示例如下：
+
+```
+$ kill -l
+ 1) SIGHUP       2) SIGINT       3) SIGQUIT      4) SIGILL       5) SIGTRAP
+ 6) SIGABRT      7) SIGBUS       8) SIGFPE       9) SIGKILL     10) SIGUSR1
+11) SIGSEGV     12) SIGUSR2     13) SIGPIPE     14) SIGALRM     15) SIGTERM
+16) SIGSTKFLT   17) SIGCHLD     18) SIGCONT     19) SIGSTOP     20) SIGTSTP
+21) SIGTTIN     22) SIGTTOU     23) SIGURG      24) SIGXCPU     25) SIGXFSZ
+26) SIGVTALRM   27) SIGPROF     28) SIGWINCH    29) SIGIO       30) SIGPWR
+31) SIGSYS      34) SIGRTMIN    35) SIGRTMIN+1  36) SIGRTMIN+2  37) SIGRTMIN+3
+38) SIGRTMIN+4  39) SIGRTMIN+5  40) SIGRTMIN+6  41) SIGRTMIN+7  42) SIGRTMIN+8
+43) SIGRTMIN+9  44) SIGRTMIN+10 45) SIGRTMIN+11 46) SIGRTMIN+12 47) SIGRTMIN+13
+48) SIGRTMIN+14 49) SIGRTMIN+15 50) SIGRTMAX-14 51) SIGRTMAX-13 52) SIGRTMAX-12
+53) SIGRTMAX-11 54) SIGRTMAX-10 55) SIGRTMAX-9  56) SIGRTMAX-8  57) SIGRTMAX-7
+58) SIGRTMAX-6  59) SIGRTMAX-5  60) SIGRTMAX-4  61) SIGRTMAX-3  62) SIGRTMAX-2
+63) SIGRTMAX-1  64) SIGRTMAX
+```
+
+## 调度启动进程
+
+有时候需要对系统进行一些比较费时而且占用资源的维护工作，这些工作适合在深夜进行，这时候用户就可以事先进行调度安排，指定任务运行的时间或者场合，到时候系统会自动完成这些任务。要使用自动启动进程的功能，就需要掌握以下几个启动命令。
+
+
+
+### 定时运行一批程序（at）
+
+#### at命令
+
+用户使用at命令在指定时刻执行指定的命令序列。该命令至少需要指定一个命令和一个执行时间。at命令可以只指定时间，也可以时间和日期一起指定。
+
+at命令的语法格式如下：
+
+```
+ at [-V] [-q 队列] [-f 文件名] [-mldbv] 时间
+ at -c 作业 [作业…]
+```
+
+#### 设置时间
+
+at允许使用一套相当复杂的时间指定方法，比如：
+
+-   接受在当天的hh:mm（小时：分钟）式的时间指定。如果该时间已经过去，那么就放存第二天执行。
+-   使用midnight（深夜）、noon（中午）、teatime（饮茶时间，一般是下午4点）等比较模糊的词语来指定时间。
+-   采用12小时计时制，即在时间后面加上AM（上午）或者PM（下午）来说明是上午还是下午。
+-   指定命令执行的具体日期，指定格式为month day（月日）或者mm/dd/yy（月/日/年）或者dd.mm.yy（日.月.年）。指定的日期必须跟在指定时间的后面。
+
+上面介绍的都是绝对计时法，其实还可以使用相对计时法，这对于安排不久就要执行的命令是很有好处的。指定格式为now+count time-units，now就是当前时间，time-units是时间单位，这里可以是minutes（分钟）、hours（小时）、days（天）、weeks（星期）。count是时间的数量，究竟是几天，还是几小时等。还有一种计时方法就是直接使用today（今天）、tomorrow（明天）来指定完成命令的时间。下面通过一些例子来说明具体用法。
+
+例如指定在今天下午4:30执行某个命令。假设现在时间是中午12:30，2019年6月7日，可用命令格式如下：
+
+```
+ at 4:30pm
+ at 16:30
+ at 16:30 today
+ at now+4 hours
+ at now+ 240 minutes
+ at 16:30 7.6.19
+ at 16:30 6/7/19
+ at 16:30 Jun 7
+```
+
+以上这些命令表达的意义是完全一样的，所以在安排时间的时候完全可以根据个人喜好和具体情况自由选择。一般采用绝对时间的24小时计时法可以避免由于用户自己的疏忽造成计时错误，例如上例可以写成：at 16:30 6/7/19。
+
+#### 执行权限
+
+对于at命令来说，需要定时执行的命令是从标准输入或者使用-f选项指定的文件中读取并执行的。如果at命令是从一个使用su命令切换到用户shell中执行的，那么当前用户被认为是执行用户，所有的错误和输出结果都会送给这个用户。但是如果有邮件送出的话，收到邮件的将是原来的用户，也就是登录时shell的所有者。
+
+例如在6月8日上午10点执行slocate -u命令。在root权限下执行命令如下：
+
+```
+# at  10:00  6/8/19
+at> slocate -u
+at>
+[1]+   Stopped    at  10:00  6/8/19
+```
+
+上面的结果中，输入at命令之后，会出现提示符at\>，提示用户输入命令，在此输入了slocate -u，然后按回车键。还可以输入多条命令，当所有要执行的命令输入结束后，按Ctrl+d键结束at命令。
+
+在任何情况下，管理员账户都可以使用这个命令。对于其他用户来说，是否可以使用就取决于/etc/at.allow和/etc/at.deny文件。
+
+### 周期性运行一批程序（cron）
+
+前面介绍at命令都会在一定时间内完成一定任务，但是它只能执行一次。也就是说，当指定了运行命令后，系统在指定时间完成任务，以后就不再执行了。但是在很多情况下需要周期性重复执行一些命令，这时候就需要使用cron命令来完成任务。
+
+#### 运行机制
+
+首先cron命令会搜索/var/spool/cron目录，寻找以/etc/passwd文件中的用户名命名的crontab文件，被找到的这种文件将装入内存。比如一个用户名为userexample的用户，对应的crontab文件应该是/var/spool/cron/userexample，即以该用户命名的crontab文件存放在/var/spool/cron目录下面。
+
+cron命令还将搜索/etc/crontab文件，这个文件是用不同的格式写成的。cron启动以后，它将首先检查是否有用户设置了crontab文件，如果没有就转入睡眠状态，释放系统资源。所以该后台进程占用资源极少，它每分钟被换醒一次，查看当前是否有需要运行的命令。
+
+命令执行结束后，任何输出都将作为邮件发送给crontab的所有者，或者是/etc/crontab文件中MAILTO环境变量中指定的用户。这是cron的工作原理，但是cron命令的执行不需要用户干涉，用户只需要修改crontab中要执行的命令。
+
+#### crontab命令
+
+crontab命令用于安装、删除或者显示用于驱动cron后台进程的表格。用户把需要执行的命令序列放到crontab文件中以获得执行，而且每个用户都可以有自己的crontab文件。
+
+crontab命令的常用方法如下：
+
+-   crontab -u   //设置某个用户的cron服务，root用户在执行crontab时需要此参数。
+-   crontab -l    //列出某个用户cron服务的详细内容。
+-   crontab -r   //删除某个用户的cron服务。
+-   crontab -e  //编辑某个用户的cron服务。
+
+例如root查看自己的cron设置。命令如下：
+
+```
+# crontab -u root -l
+```
+
+#### crontab文件
+
+在crontab文件中输入需要执行的命令和时间。该文件中每行都包括6个域，其中前5个域是指定命令被执行的时间，最后一个域是要被执行的命令。每个域之间使用空格或者制表符分隔。格式如下：
+
+```
+minute hour day-of-month month-of-year day-of-week commands
+```
+
+对于每一项的说明如所示。
+
+**表 2**  参数说明
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
参数

+
描述

+
minute

+
分钟（0~59）。

+
hour

+
小时（0~23）。

+
day-of-month

+
一个月的第几天（1~31）。

+
month-of-year

+
一年的第几个月（1~12）。

+
day-of-week

+
一周的星期几（0~6），0代表星期天。

+
commands

+
需要执行的命令。

+

+
+这些项都不能为空，必须指定值。除了数字还有几个特殊的符号“\*”、“/”和“-”、“，”。其中，\*代表所有的取值范围内的数字，/代表每的意思，“\*/5”表示每5个单位，“-”代表从某个数字到某个数字，“，”分开几个离散时数字。对于要执行的命令，调用的时候需要写出命令的完整路径。
+
+例如晚上18点到22点之间每两个小时，在/tmp/test.txt文件中加入sleepy文本。在crontab文件中对应的行如下：
+
+```
+* 18-22/2 * * * echo "sleepy" >> /tmp/test.txt
+```
+
+每次编辑完某个用户的cron设置后，cron自动在/var/spool/cron下生成一个与此用户同名的文件。此用户的cron信息都记录在这个文件中，这个文件是不可以直接编辑的，只可以用crontab -e来编辑。用户也可以另外建立一个文件，使用“cron文件名”命令导入cron设置。
+
+假设有个用户名为userexample，它需要为自己创建的一个crontab文件。步骤如下：
+
+1.  首先可以使用任何文本编辑器建立一个新文件，并将向该文件加入需要运行的命令和要定期执行的时间，假设该文件为 \~/userexample.cron。
+2.  然后在root权限下使用crontab命令安装这个文件，使用crontab命令使之成为该用户的crontab文件。命令如下：
+
+    ```
+    # crontab -u userexample ~/userexample.cron
+    ```
+
+
+这样crontab文件就建立好了，可以转到/var/spool/cron目录下面查看，发现多了一个userexample文件。这个文件就是所需的crontab文件。
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>cron启动后，每过一分钟读一次crontab文件，检查是否要执行里面的命令。因此该文件被修改后不需要重新启动cron服务。  
+
+#### 编辑配置文件
+
+cron服务每分钟不仅要读一次/var/spool/cron内的所有文件，还需要读一次/etc/crontab，因此通过配置这个文件也能得到cron的服务。用crontab配置是针对某个用户的，而编辑/etc/crontab是针对系统的任务。此文件的文件格式如下：
+
+```
+SHELL=/bin/sh
+PATH=/usr/bin:/usr/sbin:/sbin:/bin:/usr/lib/news/bin
+MAILTO=root  //如果出现错误，或者有数据输出，数据作为邮件发给这个账号
+HOME=/
+#  run-parts
+01  * * * *   root run-parts /etc/cron.hourly     //每个小时执行一次/etc/cron.hourly里的脚本
+02 4 * * *   root run-parts /etc/cron.daily    //每天执行一次/etc/cron.daily里的脚本
+22 4 * * 0  root run-parts /etc/cron.weekly     //每周执行一次/etc/cron.weekly里的脚本
+42 4 1  * *  root run-parts /etc/cron.monthly     //每月执行一次/etc/cron.monthly里的脚本
+```
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>如果去掉run-parts参数，其后面就是运行的某个脚本名，而不是目录名。  
+
+## 挂起/恢复进程
+
+作业控制允许进程挂起并可以在需要时恢复进程的运行，被挂起的作业恢复后将从中止处开始继续运行。只要在键盘上按Ctrl+Z键，即可挂起当前的前台作业。在键盘上按Ctrl+Z键后，将挂起当前执行的命令cat。使用jobs命令可以显示shell的作业清单，包括具体的作业、作业号以及作业当前所处的状态。
+
+恢复进程执行时，有两种选择：用fg命令将挂起的作业放回到前台执行；用bg命令将挂起的作业放到后台执行。灵活使用上述命令，将给自己带来很大的方便。
+
diff --git "a/content/zh/docs/Administration/\351\205\215\347\275\256\347\275\221\347\273\234.md" "b/docs/zh/docs/20.03_LTS/docs/Administration/\351\205\215\347\275\256\347\275\221\347\273\234.md"
similarity index 97%
rename from "content/zh/docs/Administration/\351\205\215\347\275\256\347\275\221\347\273\234.md"
rename to "docs/zh/docs/20.03_LTS/docs/Administration/\351\205\215\347\275\256\347\275\221\347\273\234.md"
index 9da7a61e63c1da6388f52e3dd4a2c1bd40172e65..635329334aa4889191e863df5492a6ffe3fb93dc 100644
--- "a/content/zh/docs/Administration/\351\205\215\347\275\256\347\275\221\347\273\234.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Administration/\351\205\215\347\275\256\347\275\221\347\273\234.md"
@@ -1,1333 +1,1333 @@
-# 配置网络
-
-
-- [配置网络](#配置网络)
-    - [配置 IP](#配置-ip)
-        - [使用nmcli命令](#使用nmcli命令)
-        - [使用ip命令](#使用ip命令)
-        - [通过ifcfg文件配置网络](#通过ifcfg文件配置网络)
-    - [配置主机名](#配置主机名)
-        - [简介](#简介)
-        - [使用hostnamectl配置主机名](#使用hostnamectl配置主机名)
-        - [使用nmcli配置主机名](#使用nmcli配置主机名)
-    - [配置网络绑定](#配置网络绑定)
-        - [使用nmcli](#使用nmcli)
-        - [使用命令行](#使用命令行)
-    - [IPv6使用差异说明（vs IPv4）](#ipv6使用差异说明vs-ipv4)
-        - [约束限制](#约束限制)
-        - [配置说明](#配置说明)
-        - [FAQ](#faq)
-
-
-
-
-## 配置 IP
-
-
-### 使用nmcli命令
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->使用nmcli命令配置的网络配置可以立即生效且系统重启后配置也不会丢失。  
-
-
-
-#### nmcli介绍
-
-nmcli是NetworkManager的一个命令行工具，它提供了使用命令行配置由NetworkManager管理网络连接的方法。nmcli命令的基本格式为：
-
-```
- nmcli [OPTIONS] OBJECT { COMMAND | help }
-```
-
-其中，OBJECT选项可以是general、networking、radio、connection或device等。在日常使用中，最常使用的是-t, \-\-terse（用于脚本）、-p, \-\-pretty选项（用于用户）及-h, \-\-help选项，用户可以使用“ nmcli help”获取更多参数及使用信息。
-
-```
-$ nmcli help
-```
-
-常用命令使用举例如下：
-
--   显示NetworkManager状态：
-
-    ```
-    $ nmcli general status
-    ```
-
--   显示所有连接：
-
-    ```
-    $ nmcli connection show
-    ```
-
--   只显示当前活动连接，如下所示添加 -a, \-\-active：
-
-    ```
-    $ nmcli connection show --active
-    ```
-
--   显示由NetworkManager识别到设备及其状态：
-
-    ```
-    $ nmcli device status
-    ```
-
--   使用nmcli工具启动和停止网络接口，在root权限下执行如下命令：
-
-    ```
-    # nmcli connection up id enp3s0
-    # nmcli device disconnect enp3s0
-    ```
-
-
-#### 设置网络连接
-
-列出目前可用的网络连接：
-
-```
-$ nmcli con show
-
-
-NAME    UUID                                  TYPE      DEVICE
-enp4s0  5afce939-400e-42fd-91ee-55ff5b65deab  ethernet  enp4s0
-enp3s0  c88d7b69-f529-35ca-81ab-aa729ac542fd  ethernet  enp3s0
-virbr0  ba552da6-f014-49e3-91fa-ec9c388864fa  bridge    virbr0
-```
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->输出结果中的NAME字段代表连接ID（名称）。  
-
-添加一个网络连接会生成相应的配置文件，并与相应的设备关联。检查可用的设备，方法如下：
-
-```
-$ nmcli dev status
-
-DEVICE      TYPE      STATE      CONNECTION
-enp3s0      ethernet  connected  enp3s0
-enp4s0      ethernet  connected  enp4s0
-virbr0      bridge    connected  virbr0
-lo          loopback  unmanaged  --
-virbr0-nic  tun       unmanaged  --
-```
-
-
-##### 配置动态IP连接
-
-###### 配置IP
-
-要使用 DHCP 分配网络时，可以使用动态IP配置添加网络配置文件，命令格式如下：
-
-```
-nmcli connection add type ethernet con-name connection-name ifname interface-name
-```
-
-例如创建名为net-test的动态连接配置文件，在root权限下使用以下命令：
-
-```
-# nmcli connection add type ethernet con-name net-test ifname enp3s0
-Connection 'net-test' (a771baa0-5064-4296-ac40-5dc8973967ab) successfully added.
-```
-
-NetworkManager 会将参数 connection.autoconnect 设定为 yes，并将设置保存到 “/etc/sysconfig/network-scripts/ifcfg-net-test”文件中，在该文件中会将 ONBOOT 设置为 yes。
-
-###### 激活连接并检查状态
-
-在root权限下使用以下命令激活网络连接：
-
-```
-# nmcli con up net-test 
-Connection successfully activated (D-Bus active path:/org/freedesktop/NetworkManager/ActiveConnection/5)
-```
-
-检查这些设备及连接的状态，使用以下命令：
-
-```
-$ nmcli device status
-
-DEVICE      TYPE      STATE      CONNECTION
-enp4s0      ethernet  connected  enp4s0
-enp3s0      ethernet  connected  net-test
-virbr0      bridge    connected  virbr0
-lo          loopback  unmanaged  --
-virbr0-nic  tun       unmanaged  --
-```
-
-##### 配置静态IP连接
-
-###### 配置IP
-
-添加静态 IPv4 配置的网络连接，可使用以下命令：
-
-```
-nmcli connection add type ethernet con-name connection-name ifname interface-name ip4 address gw4 address
-```
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->如果要添加 IPv6 地址和网关信息，使用 ip6 和 gw6 选项。  
-
-例如创建名为 net-static的静态连接配置文件，在root权限下使用以下命令：
-
-```
-# nmcli con add type ethernet con-name net-static ifname enp3s0 ip4 192.168.0.10/24 gw4 192.168.0.254
-```
-
-还可为该设备同时指定 IPv6 地址和网关，示例如下：
-
-```
-# nmcli con add type ethernet con-name test-lab ifname enp3s0 ip4 192.168.0.10/24 gw4 192.168.0.254 ip6 abbe::**** gw6 2001:***::*
-Connection 'net-static' (63aa2036-8665-f54d-9a92-c3035bad03f7) successfully added.
-```
-
-NetworkManager 会将其内部参数 ipv4.method 设定为 manual，将 connection.autoconnect 设定为yes，并将设置写入 /etc/sysconfig/network-scripts/ifcfg-my-office 文件，其中会将对应 BOOTPROTO 设定为 none，将 ONBOOT 设定为 yes。
-
-设定两个 IPv4 DNS 服务器地址，在root权限下使用以下命令：
-
-```
-# nmcli con mod net-static ipv4.dns "*.*.*.* *.*.*.*"
-```
-
-设置两个 IPv6 DNS 服务器地址，在root权限下使用以下命令：
-
-```
-# nmcli con mod net-static ipv6.dns "2001:4860:4860::**** 2001:4860:4860::****"
-```
-
-###### 激活连接并检查状态
-
-激活新的网络连接，在root权限下使用以下命令：
-
-```
-# nmcli con up net-static ifname enp3s0
-Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/6)
-```
-
-检查这些设备及连接的状态，使用以下命令：
-
-```
-$ nmcli device status
-
-DEVICE      TYPE      STATE      CONNECTION
-enp4s0      ethernet  connected  enp4s0
-enp3s0      ethernet  connected  net-static
-virbr0      bridge    connected  virbr0
-lo          loopback  unmanaged  --
-virbr0-nic  tun       unmanaged  --
-```
-
-查看配置的连接详情，使用以下命令（使用 -p, \-\-pretty 选项在输出结果中添加标题和分段）：
-
-```
-$ nmcli -p con show net-static 
-===============================================================================
-Connection profile details (net-static )
-===============================================================================
-connection.id:                          net-static
-connection.uuid:                        b9f18801-6084-4aee-af28-c8f0598ff5e1
-connection.stable-id:                   --
-connection.type:                        802-3-ethernet
-connection.interface-name:              enp3s0
-connection.autoconnect:                 yes
-connection.autoconnect-priority:        0
-connection.autoconnect-retries:         -1 (default)
-connection.multi-connect:               0 (default)
-connection.auth-retries:                -1
-connection.timestamp:                   1578988781
-connection.read-only:                   no
-connection.permissions:                 --
-connection.zone:                        --
-connection.master:                      --
-connection.slave-type:                  --
-connection.autoconnect-slaves:          -1 (default)
-connection.secondaries:                 --
-connection.gateway-ping-timeout:        0
-connection.metered:                     unknown
-connection.lldp:                        default
-connection.mdns:                        -1 (default)
-connection.llmnr:                       -1 (default)
-```
-
-##### 添加 Wi-Fi 连接
-
-使用以下命令查看可用 Wi-Fi 访问点：
-
-```
-$ nmcli dev wifi list
-```
-
-使用以下命令生成使用的静态 IP 配置，但允许自动 DNS 地址分配的 Wi-Fi 连接：
-
-```
-$ nmcli con add con-name Wifi ifname wlan0 type wifi ssid MyWifi ip4 192.168.100.101/24 gw4 192.168.100.1
-```
-
-请使用以下命令设定 WPA2 密码，例如 “answer”：
-
-```
-$ nmcli con modify Wifi wifi-sec.key-mgmt wpa-psk
-$ nmcli con modify Wifi wifi-sec.psk answer
-```
-
-使用以下命令更改 Wi-Fi 状态：
-
-```
-$ nmcli radio wifi [ on | off ]
-```
-
-##### 更改属性
-
-请使用以下命令检查具体属性，比如 mtu：
-
-```
-$ nmcli connection show id 'Wifi ' | grep mtu
-802-11-wireless.mtu: auto
-```
-
-使用如下命令更改设置的属性：
-
-```
-$ nmcli connection modify id 'Wifi ' 802-11-wireless.mtu 1350
-```
-
-使用如下命令确认更改：
-
-```
-$ nmcli connection show id 'Wifi ' | grep mtu
-802-11-wireless.mtu: 1350
-```
-
-#### 配置静态路由
-
--   使用nmcli命令为网络连接配置静态路由，使用命令如下：
-
-    ```
-    $ nmcli connection modify enp3s0 +ipv4.routes "192.168.122.0/24 10.10.10.1"
-    ```
-
-
--   使用编辑器配置静态路由，使用如下命令：
-
-    ```
-    $ nmcli con edit type ethernet con-name enp3s0
-    ===| nmcli interactive connection editor |===
-    Adding a new '802-3-ethernet' connection
-    Type 'help' or '?' for available commands.
-    Type 'describe [.]' for detailed property description.
-    You may edit the following settings: connection, 802-3-ethernet (ethernet), 802-1x, ipv4, ipv6, dcb
-    nmcli> set ipv4.routes 192.168.122.0/24 10.10.10.1
-    nmcli>
-    nmcli> save persistent
-    Saving the connection with 'autoconnect=yes'. That might result in an immediate activation of the connection.
-    Do you still want to save? [yes] yes
-    Connection 'enp3s0' (1464ddb4-102a-4e79-874a-0a42e15cc3c0) successfully saved.
-    nmcli> quit
-    ```
-
-
-### 使用ip命令
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->使用ip命令配置的网络配置可以立即生效但系统重启后配置会丢失。  
-
-
-
-#### 配置IP地址
-
-使用ip命令为接口配置地址，命令格式如下，其中  _interface-name_  为网卡名称。
-
-```
-ip addr [ add | del ] address dev interface-name
-```
-
-##### 配置静态地址
-在root权限下，配置设置IP地址，使用示例如下：
-
-```
-# ip address add 192.168.0.10/24 dev enp3s0
-```
-
-查看配置结果，在root权限使用如下命令：
-
-```
-# ip addr show dev enp3s0
-2: enp3s0:  mtu 1500 qdisc fq_codel state UP group default qlen 1000
-    link/ether 52:54:00:aa:ad:4a brd ff:ff:ff:ff:ff:ff
-    inet 192.168.202.248/16 brd 192.168.255.255 scope global dynamic noprefixroute enp3s0
-       valid_lft 9547sec preferred_lft 9547sec
-    inet 192.168.0.10/24 scope global enp3s0
-       valid_lft forever preferred_lft forever
-    inet6 fe80::32e8:cc22:9db2:f4d4/64 scope link noprefixroute
-       valid_lft forever preferred_lft forever
-```
-
-##### 配置多个地址
-ip 命令支持为同一接口分配多个地址，可在root权限下重复多次使用 ip 命令实现分配多个地址。使用示例如下：
-
-```
-# ip address add 192.168.2.223/24 dev enp4s0
-# ip address add 192.168.4.223/24 dev enp4s0
-# ip addr
-
-3: enp4s0:  mtu 1500 qdisc fq_codel state UP group default qlen 1000
-    link/ether 52:54:00:aa:da:e2 brd ff:ff:ff:ff:ff:ff
-    inet 192.168.203.12/16 brd 192.168.255.255 scope global dynamic noprefixroute enp4s0
-       valid_lft 8389sec preferred_lft 8389sec
-    inet 192.168.2.223/24 scope global enp4s0
-       valid_lft forever preferred_lft forever
-    inet 192.168.4.223/24 scope global enp4s0
-       valid_lft forever preferred_lft forever
-    inet6 fe80::1eef:5e24:4b67:f07f/64 scope link noprefixroute
-       valid_lft forever preferred_lft forever
-```
-
-#### 配置静态路由
-
-如果需要静态路由，可使用 ip route add 命令在路由表中添加，使用 ip route del 命令删除。最常使用的 ip route 命令格式如下：
-
-```
-ip route [ add | del | change | append | replace ] destination-address
-```
-
-在root权限下使用 ip route 命令显示当前的 IP 路由表。示例如下：
-
-```
-# ip route
-
-default via 192.168.0.1 dev enp3s0 proto dhcp metric 100
-default via 192.168.0.1 dev enp4s0 proto dhcp metric 101
-192.168.0.0/16 dev enp3s0 proto kernel scope link src 192.168.202.248 metric 100
-192.168.0.0/16 dev enp4s0 proto kernel scope link src 192.168.203.12 metric 101
-192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
-```
-
-在主机地址中添加一个静态路由，在 root 权限下，使用以下命令格式：
-
-```
-ip route add 192.168.2.1 via 10.0.0.1 [dev interface-name]
-```
-
-其中 192.168.2.1 是用点分隔的十进制符号中的 IP 地址，10.0.0.1 是下一个跃点，_interface-name_  是进入下一个跃点的退出接口。
-
-要在网络中添加一个静态路由，即代表 IP 地址范围的 IP 地址，请在root权限下运行以下命令格式：
-
-```
-ip route add 192.168.2.0/24 via 10.0.0.1 [dev interface-name]
-```
-
-其中 192.168.2.1 是目标网络的 IP 地址，10.0.0.1 是网络前缀，_interface-name_  为网卡名称。
-
-### 通过ifcfg文件配置网络
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->通过ifcfg文件配置的网络配置不会立即生效，需要在root权限下执行**systemctl reload NetworkManager**命令以重启网络服务后才生效。  
-
-#### 配置静态网络
-
-以enp4s0网络接口进行静态网络设置为例，通过在root权限下修改ifcfg文件实现，在/etc/sysconfig/network-scripts/目录中生成名为ifcfg-enp4s0的文件中，修改参数配置，示例如下：
-
-```
-TYPE=Ethernet
-PROXY_METHOD=none
-BROWSER_ONLY=no
-BOOTPROTO=none
-IPADDR=192.168.0.10
-PREFIX=24
-DEFROUTE=yes
-IPV4_FAILURE_FATAL=no
-IPV6INIT=yes
-IPV6_AUTOCONF=yes
-IPV6_DEFROUTE=yes
-IPV6_FAILURE_FATAL=no
-IPV6_ADDR_GEN_MODE=stable-privacy
-NAME=enp4s0static
-UUID=08c3a30e-c5e2-4d7b-831f-26c3cdc29293
-DEVICE=enp4s0
-ONBOOT=yes
-```
-
-#### 配置动态网络
-
-要通过ifcfg文件为em1接口配置动态网络，请按照如下操作在/etc/sysconfig/network-scripts/目录中生成名为 ifcfg-em1 的文件，示例如下：
-
-```
-DEVICE=em1
-BOOTPROTO=dhcp
-ONBOOT=yes
-```
-
-要配置一个向DHCP服务器发送不同的主机名的接口，请在ifcfg文件中新增一行内容，如下所示：
-
-```
-DHCP_HOSTNAME=hostname
-```
-
-要配置忽略由DHCP服务器发送的路由，防止网络服务使用从DHCP服务器接收的DNS服务器更新/etc/resolv.conf。请在ifcfg文件中新增一行内容，如下所示：
-
-```
-PEERDNS=no
-```
-
-要配置一个接口使用具体DNS服务器，请将参数PEERDNS=no，并在ifcfg文件中添加以下行：
-
-```
-DNS1=ip-address
-DNS2=ip-address
-```
-
-其中ip-address是DNS服务器的地址。这样就会让网络服务使用指定的DNS服务器更新/etc/resolv.conf。
-
-#### 配置默认网关
-
-在确定默认网关时，首先解析 /etc/sysconfig/network 文件，然后解析 ifcfg 文件 ，将最后读取的 GATEWAY 的取值作为路由表中的默认路由。
-
-在动态网络环境中，使用 NetworkManager 管理主机时，建议设置为由 DHCP 来分配。
-
-## 配置主机名
-
-
-### 简介
-
-hostname有三种类型：static、transient和pretty。
-
--   static：静态主机名，可由用户自行设置，并保存在/etc/hostname 文件中。
--   transient：动态主机名，由内核维护，初始是 static 主机名，默认值为“localhost”。可由DHCP或mDNS在运行时更改。
--   pretty：灵活主机名，允许使用自由形式（包括特殊/空白字符）进行设置。静态/动态主机名遵从域名的通用限制。
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->static和transient主机名只能包含a-z、A-Z、0-9、“-”、“\_”和“.”，不能在开头或结尾处使用句点，不允许使用两个相连的句点，大小限制为 64 个字符。  
-
-### 使用hostnamectl配置主机名
-
-#### 查看所有主机名
-查看当前的主机名，使用如下命令：
-
-```
-$ hostnamectl status
-```
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->如果命令未指定任何选项，则默认使用status选项。  
-
-#### 设定所有主机名
-在root权限下，设定系统中的所有主机名，使用如下命令：
-
-```
-# hostnamectl set-hostname name
-```
-
-#### 设定特定主机名
-在root权限下，通过不同的参数来设定特定主机名，使用如下命令：
-
-```
-# hostnamectl set-hostname name [option...]
-```
-
-其中option可以是\-\-pretty、\-\-static、\-\-transient中的一个或多个选项。
-
-如果\-\-static或\-\-transient与\-\-pretty选项一同使用时，则会将static和transient主机名简化为pretty主机名格式，使用“-”替换空格，并删除特殊字符。
-
-当设定pretty主机名时，如果主机名中包含空格或单引号，需要使用引号。命令示例如下：
-
-```
-# hostnamectl set-hostname "Stephen's notebook" --pretty
-```
-
-#### 清除特定主机名
-要清除特定主机名，并将其还原为默认形式，在root权限下，使用如下命令：
-
-```
-# hostnamectl set-hostname "" [option...]
-```
-
-其中 "" 是空白字符串，option是\-\-pretty、\-\-static和\-\-transient中的一个或多个选项。
-
-#### 远程更改主机名
-在远程系统中运行hostnamectl命令时，要使用-H，\-\-host 选项，在root权限下使用如下命令：
-
-```
-# hostnamectl set-hostname -H [username]@hostname new_hostname
-```
-
-其中hostname是要配置的远程主机，username为自选项，new\_hostname为新主机名。hostnamectl会通过SSH连接到远程系统。
-
-### 使用nmcli配置主机名
-
-查询static主机名，使用如下命令：
-
-```
-$ nmcli general hostname
-```
-
-在root权限下，将static主机名设定为host-server，使用如下命令：
-
-```
-# nmcli general hostname host-server
-```
-
-要让系统hostnamectl感知到static主机名的更改，在root权限下，重启hostnamed服务，使用如下命令：
-
-```
-# systemctl restart systemd-hostnamed
-```
-
-## 配置网络绑定
-
-
-### 使用nmcli
-
--   创建名为mybond0的绑定，使用示例如下：
-
-    ```
-    $ nmcli con add type bond con-name mybond0 ifname mybond0 mode active-backup
-    ```
-
--   添加从属接口，使用示例如下：
-
-    ```
-    $ nmcli con add type bond-slave ifname enp3s0 master mybond0
-    ```
-
-    要添加其他从属接口，重复上一个命令，并在命令中使用新的接口，使用示例如下：
-
-    ```
-    $ nmcli con add type bond-slave ifname enp4s0 master mybond0
-    Connection 'bond-slave-enp4s0' (05e56afc-b953-41a9-b3f9-0791eb49f7d3) successfully added.
-    ```
-
--   要启动绑定，则必须首先启动从属接口，使用示例如下：
-
-    ```
-    $ nmcli con up bond-slave-enp3s0
-    Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/14)
-    ```
-
-    ```
-    $ nmcli con up bond-slave-enp4s0
-    Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/15)
-    ```
-
-    现在可以启动绑定，使用示例如下：
-
-    ```
-    $ nmcli con up mybond0
-    Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/16)
-    ```
-
-
-### 使用命令行
-
-
-
-#### 检查是否已安装Bonding内核模块
-
-在系统中默认已加载相应模块。要载入绑定模块，可在root权限下使用如下命令：
-
-```
-# modprobe --first-time bonding
-```
-
-显示该模块的信息，可在root权限下使用如下命令：
-
-```
-# modinfo bonding
-```
-
-更多命令请在root权限下使用modprobe \-\-help查看。
-
-#### 创建频道绑定接口
-
-要创建绑定接口，可在root权限下通过在 /etc/sysconfig/network-scripts/ 目录中创建名为 ifcfg-bondN 的文件（使用接口号码替换 N，比如 0）。
-
-根据要绑定接口类型的配置文件来编写相应的内容，比如网络接口。接口配置文件示例如下：
-
-```
-DEVICE=bond0
-NAME=bond0
-TYPE=Bond
-BONDING_MASTER=yes
-IPADDR=192.168.1.1
-PREFIX=24
-ONBOOT=yes
-BOOTPROTO=none
-BONDING_OPTS="bonding parameters separated by spaces"
-```
-
-#### 创建从属接口
-
-创建频道绑定接口后，必须在从属接口的配置文件中添加 MASTER 和 SLAVE 指令。
-
-例如将两个网络接口enp3s0 和 enp4s0 以频道方式绑定，其配置文件示例分别如下：
-
-```
-TYPE=Ethernet
-NAME=bond-slave-enp3s0
-UUID=3b7601d1-b373-4fdf-a996-9d267d1cac40
-DEVICE=enp3s0
-ONBOOT=yes
-MASTER=bond0
-SLAVE=yes
-```
-
-```
-TYPE=Ethernet
-NAME=bond-slave-enp4s0
-UUID=00f0482c-824f-478f-9479-abf947f01c4a
-DEVICE=enp4s0
-ONBOOT=yes
-MASTER=bond0
-SLAVE=yes
-```
-
-#### 激活频道绑定
-
-要激活绑定，则需要启动所有从属接口。请在root权限下，运行以下命令：
-
-```
-# ifup enp3s0
-Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/7)
-```
-
-```
-# ifup enp4s0
-Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/8)
-```
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->对于已经处于“up”状态的接口，请首先使用“ifdown  _enp3s0_  ”命令修改状态为down，其中  _enp3s0_  为实际网卡名称。  
-
-完成后，启动所有从属接口以便启动绑定（不将其设定为 “down”）。
-
-要让 NetworkManager 感知到系统所做的修改，在每次修改后，请在root权限下，运行以下命令：
-
-```
-# nmcli con load /etc/sysconfig/network-scripts/ifcfg-device
-```
-
-查看绑定接口的状态，请在root权限下运行以下命令：
-
-```
-# ip link show
-
-1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
-    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
-2: enp3s0:  mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
-    link/ether 52:54:00:aa:ad:4a brd ff:ff:ff:ff:ff:ff
-3: enp4s0:  mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
-    link/ether 52:54:00:aa:da:e2 brd ff:ff:ff:ff:ff:ff
-4: virbr0:  mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
-    link/ether 86:a1:10:fb:ef:07 brd ff:ff:ff:ff:ff:ff
-5: virbr0-nic:  mtu 1500 qdisc fq_codel master virbr0 state DOWN mode DEFAULT group default qlen 1000
-    link/ether 52:54:00:29:35:4c brd ff:ff:ff:ff:ff:ff
-```
-
-#### 创建多个绑定
-
-系统会为每个绑定创建一个频道绑定接口，包括 BONDING\_OPTS 指令。使用这个配置方法可让多个绑定设备使用不同的配置。请按照以下操作创建多个频道绑定接口：
-
--   创建多个 ifcfg-bondN 文件，文件中包含 BONDING\_OPTS 指令，让网络脚本根据需要创建绑定接口。
--   创建或编辑要绑定的现有接口配置文件，添加 SLAVE 指令。
--   使用 MASTER 指令工具在频道绑定接口中分配要绑定的接口，即从属接口。
-
-以下是频道绑定接口配置文件示例：
-
-```
-DEVICE=bondN
-NAME=bondN
-TYPE=Bond
-BONDING_MASTER=yes
-IPADDR=192.168.1.1
-PREFIX=24
-ONBOOT=yes
-BOOTPROTO=none
-BONDING_OPTS="bonding parameters separated by spaces"
-```
-
-在这个示例中，使用绑定接口的号码替换 N。例如要创建两个接口，则需要使用正确的 IP 地址创建两个配置文件 ifcfg-bond0 和 ifcfg-bond1。
-
-## IPv6使用差异说明（vs IPv4）
-
-
-
-### 约束限制
-
--   chrony支持全局地址（global address），不支持链路本地地址（link-local address）。
--   Firefox支持通过http/https协议访问全局地址（global address），不支持链路本地地址（link-local address）。
-
-### 配置说明
-#### 设置接口设备MTU值
-
-##### 概述
-
-IPv6场景中会发现整个路由路径中的最小mtu的值作为当前链接的PMTU的值，源端根据PMTU的值确定是否进行分片发送，而在整个路径中的其它设备将不再需要进行分片处理，从而可以降低中间路由设备的负载大小。其中IPv6 PMTU设置的最小值为1280。
-
-##### 设置接口设备的mtu
-
-如果在配置了IPv6地址的接口上设置mtu的值小于1280（IPv6 PMTU设置的最小值），则会导致该接口的IPv6地址被删除。并且无法再次添加IPv6地址。所以在IPv6场景中，对接口设备的mtu的配置一定要大于等于1280。
-请在root权限下运行如下命令查看具体现象：
-
-```
-# ip addr show enp3s0
-3: enp3s0:  mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
-    link/ether 52:54:00:62:xx:xx brd ff:ff:ff:ff:xx:xx
-    inet 10.41.125.236/16 brd 10.41.255.255 scope global noprefixroute dynamic enp3s0
-       valid_lft 38663sec preferred_lft 38663sec
-    inet6 2001:222::2/64 scope global
-       valid_lft forever preferred_lft forever
-```
-
-```
-# ip link set dev enp3s0 mtu 1200
-# ip addr show enp3s0
-3: enp3s0:  mtu 1200 qdisc pfifo_fast state UP group default qlen 1000
-    link/ether 52:54:00:62:xx:xx brd ff:ff:ff:ff:xx:xx
-    inet 10.41.125.236/16 brd 10.41.255.255 scope global noprefixroute dynamic enp3s0
-       valid_lft 38642sec preferred_lft 38642sec
-```
-
-```
-# ip addr add 2001:222::2/64 dev enp3s0
-RTNETLINK answers: No buffer space available
-```
-
-```
-# ip link set dev enp3s0 mtu 1500
-# ip addr show enp3s0
-3: enp3s0:  mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
-    link/ether 52:54:00:62:xx:xx brd ff:ff:ff:ff:xx:xx
-    inet 10.41.125.236/16 brd 10.41.255.255 scope global noprefixroute dynamic enp3s0
-       valid_lft 38538sec preferred_lft 38538sec
-```
-
-```
-# ip addr add 2001:222::2/64 dev enp3s0
-# ip addr show enp3s0
-3: enp3s0:  mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
-    link/ether 52:54:00:62:xx:xx brd ff:ff:ff:ff:xx:xx
-    inet 10.41.125.236/16 brd 10.41.255.255 scope global noprefixroute dynamic enp3s0
-       valid_lft 38531sec preferred_lft 38531sec
-    inet6 2001:222::2/64 scope global
-       valid_lft forever preferred_lft forever
-```
-
-#### 有状态自动配置IPv6地址
-
-##### 概述
-
-IPv6与IPv4都可以在root权限下通过DHCP的方式获得IP地址。IPv6地址有两种配置方式：无状态自动配置和有状态自动配置。
-
--   无状态自动配置
-
-    不需要DHCP服务进行管理，设备根据网络RA（路由公告）获得网络前缀，或者link-local地址为固定fe80::。而接口ID则根据ifcfg配置IPV6\_ADDR\_GEN\_MODE的具体设置来进行自动获得：
-
-    1.  IPv6\_ADDR\_GEN\_MODE="stable-privacy" 则根据设备及网络环境来确定一个随机接口ID。
-    2.  IPv6\_ADDR\_GEN\_MODE="EUI64" 则根据设备MAC地址来确定接口ID。
-
--   有状态自动配置：需要DHCP服务器进行管理分配，服从DHCPv6协议来从DHCPv6服务器端租赁IPv6地址。
-
-    在有状态自动配置IPv6地址时，DHCPv6服务端可以通过客户端设置的vendor class将客户端进行分类，不同类别分配不同地址段的IPv6地址。在IPv4场景中，客户端可以直接用dhclient的-V选项来设置vendor-class-identifier，DHCP服务端在配置文件中根据vendor-class-identifier来对客户端进行分类处理。而IPv6场景中，如果使用同样的方法对客户端分类，则分类并不会生效。
-
-    ```
-    dhclient -6  -V  
-    ```
-
-    这是由于DHCPv6和DHCP协议存在较大差异，DHCPv6的可选项中使用vendor-class-option替代了DHCP中的vendor-class-identifier。而dhclient的-V选项并不能设置vendor-class-option。
-
-
-##### 有状态自动配置IPv6地址时dhclient设置vendor class方法
-
--   在客户端使用配置文件方式添加对vendor class的设置，使用方法如下：
-
-    客户端配置文件（/etc/dhcp/dhclient6.conf），文件位置可以自定义，在使用时需要通过dhclient -cf选项来指定配置文件：
-
-    ```
-    option dhcp6.vendor-class code 16 = {integer 32, integer 16, string};
-    interface "enp3s0" {
-            send dhcp6.vendor-class   ;
-    }
-    ```
-
-    >![](public_sys-resources/icon-note.gif) **说明：**   
-    >-   \，32位整型数字，企业标识号，企业通过IANA注册。  
-    >-   \，16位整型数字，vendor class字符串长度。  
-    >-   \，要设置的vendor class字符串，例如：“HWHW”。  
-
-    客户端使用方法：
-
-    ```
-    dhclient -6  -cf /etc/dhcp/dhclient6.conf
-    ```
-
-
--   DHCPv6服务端配置文件（/etc/dhcp/dhcpd6.conf），需要dhcpd -cf选项来指定该配置文件：
-
-    ```
-    option dhcp6.vendor-class code 16 = {integer 32, integer 16, string};
-    subnet6 fc00:4:12:ffff::/64 {
-            class "hw" {
-                    match if substring ( option dhcp6.vendor-class, 6, 10 ) = "HWHW";
-            }
-            pool6 {
-                    allow members of "hw";
-                    range6 fc00:4:12:ffff::ff10 fc00:4:12:ffff::ff20;
-            }
-            pool6 {
-                    allow unknown clients;
-                    range6 fc00:4:12:ffff::100 fc00:4:12:ffff::120;
-            }
-    }
-    ```
-
-    >![](public_sys-resources/icon-note.gif) **说明：**   
-    >substring \( option dhcp6.vendor-class, 6, 10 \) 其中子字符串的开始位置为6，因为前面包含4个字节的和2个字节的。而子字符串的结束位置位：6+。这里vendor class string为“HWHW”，字符串的长度为4，所以子字符串的结束位置为6+4=10。用户可以根据实际需要来确定及相应的。  
-
-    服务端使用方法：
-
-    ```
-    dhcpd -6 -cf /etc/dhcp/dhcpd6.conf 
-    ```
-
-
-#### 内核支持socket相关系统调用
-
-##### 概述
-
-IPv6地址长度扩展到128比特，所以有足够的IPv6地址可供分配使用。同时IPv6头相比IPv4头进行了简化，并增强了IPv6的自动配置功能。IPv6地址分为单播地址，组播地址和任意播地址。常用的单播地址又包含：链路本地地址（link-local address），唯一本地地址（Unique local address）和全局地址（global address）。由于IPv6的全局地址十分充足，唯一本地地址一般不被使用（其前身为站点本地地址（site-local address），已于2004年被废弃）。当前主要使用的单播地址为：链路本地地址（link-local address）和全局地址（global address）。当前内核支持socket系统调用，在使用单播地址的链路本地地址和全局地址时存在差异。
-
-##### link-local地址和global地址在socket调用时的差异
-
-RFC 2553： Basic Socket Interface Extensions for IPv6 定义sockaddr\_in6的数据结构如下；
-
-```
-struct sockaddr_in6 {     
-    uint8_t         sin6_len;       /* length of this struct */     
-    sa_family_t     sin6_family;    /* AF_INET6 */     
-    in_port_t       sin6_port;      /* transport layer port # */     
-    uint32_t        sin6_flowinfo;  /* IPv6 flow information */     
-    struct in6_addr sin6_addr;      /* IPv6 address */     
-    uint32_t        sin6_scope_id;  /* set of interfaces for a scope */ 
-}; 
-```
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->sin6\_scope\_id： 32位整型，对于链路本地地址（link-local address），对于链路范围的sin6\_addr，它可以用来标识指定的接口索引号。如果是站点范围的sin6\_addr，则用来作为站点的标识符（站点本地地址已被抛弃）。  
-
-在使用link-local地址进行socket通信时，在构造目的地址时，需要制定该地址所对应的接口索引号。一般可以通过if\_nametoindex函数将接口名转化为接口索引号。具体方式如下，
-
-```
-int port = 1234;
-int sk_fd;
-int iff_index = 0;
-char iff_name[100] = "enp3s0";
-char * ll_addr[100] = "fe80::123:456:789";
-struct sockaddr_in6 server_addr;
-
-memset(&server_addr,0,sizeof(structsockaddr_in6));
-iff_index=if_nametoindex(iff_name);
-
-server_addr.sin6_family=AF_INET6;
-server_addr.sin6_port=htons(port);
-server_addr.sin6_scope_id=iff_index;
-inet_pton(AF_INET6, ll_addr, &(server_addr.sin6_addr));
-
-sk_fd=socket(AF_INET6, SOCK_STREAM, IPPROTO_TCP);
-connect(sk_fd, (struct sockaddr *)&server_addr, sizeof(struct sockaddr_in6));
-```
-
-#### IPv4的dhclient守护进程持久化配置
-
-##### 概述
-
-通过NetworkManager服务来管理网络服务时，如果接口ifcfg-配置文件中配置了DHCP方式获得IP地址，则相应地NetworkManager服务会拉起dhclient守护进程来通过DHCP协议方式来从DHCP服务器获取IP地址。
-
-dhclient提供了"-1"选项来决定dhclient进程在未获得DHCP服务响应时，是会不断持久化尝试请求地址还是会尝试时间超时后退出。针对IPv4的dhclient守护进程，可以在ifcfg-配置文件中设置PERSISTENT\_DHCLIENT来决定是否设置IPv4的dhclient进程的持久化。
-
-##### 约束限制
-
-1.  当dhclient进程在运行中被杀死，network服务无法自动将其拉起，可靠性需要用户自己保障。
-2.  配置了持久化选项PERSISTENT\_DHCLIENT，需要确保有相应的DHCP服务器。如果在拉起network时无可用DHCP服务器，dhclient进程不断尝试发送请求包但无回应，则会导致network服务卡死直到network服务超时失败。由于network服务在拉起多个网卡的IPv4 dhclient进程时，是通过串行的方式来拉起的。如果有网卡配置了持久化而DHCP服务器没有准备好，则会导致network服务在给该网卡获取IPv4地址超时卡死，进而导致后续网卡无法获得IPv4/IPv6地址。
-
-以上两种约束限制是特殊的应用场景，需要用户自己进行可靠性保障。
-
-##### IPv4 DHCP和IPv6 DHCPv6方式获取地址的配置差异
-
-可以通过配置接口ifcfg-参数来分别实现IPv4和IPv6通过DHCP/DHCPv6协议来动态获取IP地址，具体配置说明如下；
-
-```
-BOOTPROTO=none|bootp|dhcp
-DHCPV6C=yes|no
-PERSISTENT_DHCLIENT=yes|no|1|0
-```
-
--   BOOTPROTO： none表示静态配置IPv4地址，bootp|dhcp则会拉起DHCP dhclient来动态获取IPv4地址。
--   DHCPV6C： no表示静态配置IPv6地址，yes则会拉起DHCPv6 dhclient来动态获取IPv6地址。
--   PERSISTENT\_DHCLIENT：no|0表示IPv4的dhclient进程配置为“非持久化”，当dhclient向DHCP服务器发送一次请求报文而无响应，则会间隔一段时间后退出，退出值为2。yes|1则表示IPv4的dhclient进程配置为“持久化”，dhclient会向DHCP服务器反复发送请求报文。**如果没有配置PERSISTENT\_DHCLIENT项，则IPv4的dhclient会默认设置为“持久化”**。
-
-    >![](public_sys-resources/icon-note.gif) **说明：**   
-    >PERSISTENT\_DHCLIENT配置只针对IPv4生效，对IPv6相关dhclient -6进程不生效，IPv6默认不进行持久化配置。  
-
-
-#### iproute相关命令配置IPv4与IPv6时的差异说明
-
-##### 概述
-
-由于IPv4和IPv6是两个不同的协议标准，iproute相关命令在使用方法上存在一定的差异。本章节主要梳理iproute包中用户经常使用到命令在IPv4和IPv6使用方面的差异，从而可以更好地指导用户使用iproute包中相关命令。
-
-iproute相关命令均需要在root权限下运行。
-
-##### IPv6地址的生命周期
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
IPv6状态

-
解释

-
tentative

-
临时状态：刚添加地址还处于地址重复检测DAD过程

-
preferred

-
首选状态：完成DAD过程，没有收到相应的NA报文，表示该地址没有冲突。

-
deprecated

-
弃用状态：地址有一定的使用时限（valid_lft和preferred_lft），preferred_lft到期后地址会变化deprecated状态。

-
该状态下的地址不能用于创建新的连接，但是原有的连接可以继续使用。

-
invalid

-
无效状态：使用时限超过preferred_lft一段时间后仍然没有成功进行租约续约，则valid_lft时间到后地址状态会被设置为invalid，表示该地址不可以再被使用。

-

-
-其它说明：
-
--   preferred\_lft：preferred lifetime，地址为首选状态的寿命，preferred\_lft没有到期的地址可以用于正常通信使用，若有多个preferred地址则按照内核具体机制选择地址。
--   valid\_lft： valid lifetime，地址有效的寿命，在\[preferred\_lft, valid\_lft\]时间段内该地址不能被用于新建连接，已经创建的连接继续有效。
-
-##### ip link 命令
-
-命令：
-
-```
-ip link set IFNAME mtu MTU
-```
-
-IPv6中PMTU的最小值为1280，如果mtu值设置小于1280则会导致IPv6地址丢失。其它设备无法ping通该IPv6地址。
-
-##### ip addr命令
-
-1.  命令：
-
-    ```
-    ip [-6] addr add IFADDR dev IFNAME
-    ```
-
-    添加IPv6地址可以选择添加-6选项也可以不添加，ip addr命令会根据具体地址类型来判断是ipv4地址还是IPv6地址。
-
-    如果指定“-6”选项，但是IFADDR 是ipv4地址则会有错误返回。
-
-2.  命令：
-
-    ```
-    ip [-6] addr add IFADDR  dev IFNAME [home|nodad]
-    ```
-
-    \[home|nodad\] 选项只针对IPv6地址有效。
-
-    -   home：将该地址指定为RFC 6275中定义的家庭地址。（这是移动节点从家庭链路获取的地址， 是移动节点的永久地址，如果移动节点保持在相同的归属链路中，则各种实体之间的通信照常进行。）
-    -   nodad：配置该项（仅限IPv6）添加此地址时不执行重复地址检测DAD（RFC 4862）。如果一台设备上多个接口通过nodad配置了多个相同的IPv6地址，则会按照接口顺序使用该IPv6地址。同一个接口上不能添加一个nodad一个非nodad的相同IPv6地址。因为两个地址是一样的，所以会报“RTNETLINK answers: File exists”。
-
-3.  命令：
-
-    ```
-    ip [-6] addr del IFADDR dev IFNAME
-    ```
-
-    删除IPv6地址可以选择添加-6选项也可以不添加，ip addr del命令会根据具体地址类型来判断是ipv4地址还是IPv6地址。
-
-4.  命令：
-
-    ```
-    ip [-6] addr show dev IFNAME [tentative|-tentative|deprecated|-deprecated|dadfailed|-dadfailed|temporary]
-    ```
-
-    -   不指定-6选项，则会同时打印IPv4和IPv6地址。指定-6选项则只打印IPv6地址。
-    -   \[tentative|-tentative|deprecated|-deprecated|dadfailed|-dadfailed|temporary\]，这些选项只针对IPv6，可以根据IPv6地址状态对地址进行筛选查看。
-        1.  tentative：（仅限IPv6）仅列出尚未通过重复地址检测的地址。
-        2.  -tentative：（仅限IPv6）仅列出当前未处于重复地址检测过程中的地址。
-        3.  deprecated：（仅限IPv6）仅列出已弃用的地址。
-        4.  -deprecated：（仅限IPv6）仅列出未弃用的地址。
-        5.  dadfailed：（仅限IPv6）仅列出重复地址检测失败的地址。
-        6.  -dadfailed：（仅限IPv6）仅列出未重复地址检测失败的地址。
-        7.  temporary：（仅限IPv6）仅列出临时地址
-
-
-
-##### ip route命令
-
-1.  命令：
-
-    ```
-    ip [-6] route add ROUTE [mtu lock MTU]
-    ```
-
-    -   -6选项：添加IPv6路由可以选择添加-6选项也可以不添加，ip route命令会根据具体地址类型来判断是IPv4地址还是IPv6地址。
-
-    -   mtu lock MTU：锁定路由的MTU值。如果不锁定MTU，则MTU的值则可能在PMTUD过程中被内核改变。如果锁定MTU，则不会尝试PMTUD，所有IPv4包都将不设置DF位发出，IPv6包则会按照MTU进行分段处理。
-
-2.  命令：
-
-    ```
-    ip [-6] route del ROUTE
-    ```
-
-    删除IPv6路由可以选择添加-6选项也可以不添加，ip route命令会根据具体地址类型来判断是IPv4地址还是IPv6地址。
-
-
-##### ip rule命令
-
-1.  命令：
-
-    ```
-    ip [-6] rule list
-    ```
-
-    -6选项：设置-6选项打印IPv6的策略路由，不设置-6选项打印IPv4的策略路由。所以需要根据具体协议类型来配置-6选项。
-
-2.  命令：
-
-    ```
-    ip [-6] rule [add|del] [from|to] ADDR table TABLE pref PREF
-    ```
-
-    -6选项：IPv6相关的策略路由表项需要设置-6选项，否则会报错：“Error: Invalid source address.”。相应地，IPv4相关的策略路由表项不可以设置-6选项，否则会报错：“Error: Invalid source address.”。
-
-
-#### NetworkManager服务配置差异说明
-
-##### 概述
-
-NetworkManager服务使用ifup/ifdown的逻辑接口定义进行高级网络设置。其参数大多数都是在/etc/sysconfig/network和/etc/sysconfig/network-scripts/ifcfg-两个配置文件设置。前者为全局设置，后者为指定网卡的设置，当两者有冲突时，后者生效。
-
-##### 配置差异说明
-
-其中在/etc/sysconfig/network下的配置差异有：
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
IPv4

-
IPv6

-
含义说明

-
NA

-
IPV6FORWARDING=yes|no

-
IPv6转发，默认不转发。

-
NA

-
IPV6_AUTOCONF=yes|no

-
IPv6转发打开是no，否则是yes。

-
NA

-
IPV6_ROUTER=yes|no

-
IPv6转发打开是yes，否则是no。

-
NA

-
IPV6_AUTOTUNNEL=yes|no

-
指定Tunnel为自动隧道模式，默认是no。

-
GATEWAY

-
IPV6_DEFAULTGW=<IPv6 address[%interface]> (optional)

-
在IPv6中设置默认网关。

-
NA

-
IPV6_DEFAULTDEV=<interface> (optional)

-
指定默认转发的网卡。

-
NA

-
IPV6_RADVD_PIDFILE=<pid-file> (optional)

-
默认ipv6_radvd_pid路径：/var/run/radvd/radvd.pid。

-
NA

-
IPV6_RADVD_TRIGGER_ACTION=startstop|reload|restart|SIGHUP (optional)

-
radvd默认触发动作。

-

-
-而在/etc/sysconfig/network-scripts/ifcfg-下的差异主要有：
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
IPv4

-
IPv6

-
含义说明

-
IPADDRn

-
IPV6ADDR=<IPv6 address>[/<prefix length>]

-
ip地址。

-
PREFIXn

-
NA

-
网络前缀，网络别名和ppp无效，优先级高于NETMASK。

-
NETMASKn

-
NA

-
子网掩码，仅用于别名和ppp。

-
GATEWAY

-
IPV6_DEFAULTGW=<IPv6 address[%interface]> (optional)

-
默认网关。

-
MTU

-
IPV6_MTU=<MTU of link> (optional)

-
默认MTU。

-
IPV4_FAILURE_FATAL=yes|no

-
IPV6_FAILURE_FATAL

-
默认值是no。若设置为yes，dhclient失败ifup-eth会直接退出。

-
NA

-
IPV6_PRIVACY=rfc3041

-
默认禁用。

-
NA

-
IPV6INIT=yes|no

-
默认开启IPv6。

-
NA

-
IPV6FORWARDING=yes|no

-
默认关闭，已废弃。

-

-
-### FAQ
-#### iscsi-initiator-utils不支持登录fe80 IPv6地址
-
-##### 问题现象
-
-客户端通过IPv6登录iscsi服务端时，使用如“iscsiadm -m node -p ipv6address -l”的命令格式登录，如果是全局地址（global address），直接替换将命令范例中的“ipv6address”替换为全局地址即可；但如果是链路本地地址（link-local address，fe80开头的IPv6地址）则无法使用，因为iscsi-initiator-utils目前机制还不支持用链路本地地址（link-local address）地址登录iscsi服务端。
-
-##### 原因分析
-
-如果使用格式如“iscsiadm -m node -p fe80::xxxx -l”登录，会登录超时返回，这是因为使用链路本地地址必须指定接口，否则使用iscsi\_io\_tcp\_connect函数调用connect函数会失败，并且产生标准错误码22。
-
-如果使用格式如“iscsiadm -m node -p fe80::xxxx%enp3s0 -l”登录时，iscsi\_addr\_match函数会将地址“fe80::xxxx%enp3s0”与服务端返回的node信息中的地址“fe80::xxxx”对比，对比结果不匹配，导致登录失败。
-
-因此，**iscsi-initiator-utils目前机制还不支持用链路本地地址（link-local address）登录iscsi服务端**。
-
-#### 网卡down掉之后，IPv6地址丢失
-
-##### 问题现象
-
-通过ip link down+up网卡或ifconfig down+up网卡命令，将网卡down掉之后再上线，查看网卡上配置的ip地址，发现ipv4地址不丢失，而配置的IPv6地址丢失。
-
-##### 原因分析
-
-内核中的处理逻辑为如果网卡设置为down状态，会清空所有IPv4及IPv6地址，将网卡重新up之后，ipv4地址自动恢复，网卡上自动配置的IPv6链路本地地址也会恢复，但是其他IPv6地址默认会丢失。如果需要保留这些IPv6地址，可以通过“sysctl -w net.ipv6.conf.<网卡名\>.keep\_addr\_on\_down=1”来实现。
-
-#### bond口已具有多个IPv6地址时，添加或删除IPv6地址耗时过久
-
-##### 问题现象
-
-下列方式配置或删除（包括flush）IPv6地址方式，X为动态变化的低16位，并且配置在bond口时，耗时会随已配置的IPv6地址数量成数倍增加。例如由4个物理网卡组成的bond口添加IPv6地址时，单线程添加删除3000 IPv6地址均需大概5分钟，而普通物理网卡耗时在10秒内。
-
-```
-ip a add/del 192:168::18:X/64 dev DEVICE
-```
-
-##### 原因分析
-
-bond口在添加IPv6地址时，会生成IPv6组播地址，并进行同步到所有的物理网卡上，此耗时会随IPv6数量增加而增加，导致耗时过长。
-
-##### 解决方法
-
-IPv6的组播地址是由IPv6地址的低24位与33-33-ff组合生成，组播地址过多会导致添加删除耗时增加，如果生成的组播地址为少量，耗时不会受此影响。
-
-建议添加IPv6地址时，可保持低24位一致，保持高位变动，单网卡中仅需一个网段的一个地址即可与外部正常通信，此配置更符合常规使用。
-
-#### Rsyslog在IPv4和IPv6混合使用场景中日志传输延迟
-
-##### 问题现象
-
-rsyslog客户端配置文件同时配置IPv4和IPv6地址，且端口配置相同的情况下，服务端收集log时会概率性出现日志打印延迟。
-
-##### 原因分析
-
-延迟是因为rsyslog内部存在缓冲队列机制，默认情况下需要缓冲区队列达到一定数量才会写入文件。
-
-##### 解决方法
-
-可在root权限下通过配置Direct模式，关闭缓冲队列机制解决该问题。在rsyslog远程传输服务端的/etc/rsyslog.d目录下新增的远程传输配置文件中，最开头增加如下配置：
-
-```
-$ActionQueueType Direct
-$MainMsgQueueType Direct
-```
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->-   Direct模式减少队列大小为1，所以在队列中会保留1条日志到下次日志打印；  
->-   Direct模式会降低服务器端的rsyslog性能。  
+# 配置网络
+
+
+- [配置网络](#配置网络)
+    - [配置 IP](#配置-ip)
+        - [使用nmcli命令](#使用nmcli命令)
+        - [使用ip命令](#使用ip命令)
+        - [通过ifcfg文件配置网络](#通过ifcfg文件配置网络)
+    - [配置主机名](#配置主机名)
+        - [简介](#简介)
+        - [使用hostnamectl配置主机名](#使用hostnamectl配置主机名)
+        - [使用nmcli配置主机名](#使用nmcli配置主机名)
+    - [配置网络绑定](#配置网络绑定)
+        - [使用nmcli](#使用nmcli)
+        - [使用命令行](#使用命令行)
+    - [IPv6使用差异说明（vs IPv4）](#ipv6使用差异说明vs-ipv4)
+        - [约束限制](#约束限制)
+        - [配置说明](#配置说明)
+        - [FAQ](#faq)
+
+
+
+
+## 配置 IP
+
+
+### 使用nmcli命令
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>使用nmcli命令配置的网络配置可以立即生效且系统重启后配置也不会丢失。  
+
+
+
+#### nmcli介绍
+
+nmcli是NetworkManager的一个命令行工具，它提供了使用命令行配置由NetworkManager管理网络连接的方法。nmcli命令的基本格式为：
+
+```
+ nmcli [OPTIONS] OBJECT { COMMAND | help }
+```
+
+其中，OBJECT选项可以是general、networking、radio、connection或device等。在日常使用中，最常使用的是-t, \-\-terse（用于脚本）、-p, \-\-pretty选项（用于用户）及-h, \-\-help选项，用户可以使用“ nmcli help”获取更多参数及使用信息。
+
+```
+$ nmcli help
+```
+
+常用命令使用举例如下：
+
+-   显示NetworkManager状态：
+
+    ```
+    $ nmcli general status
+    ```
+
+-   显示所有连接：
+
+    ```
+    $ nmcli connection show
+    ```
+
+-   只显示当前活动连接，如下所示添加 -a, \-\-active：
+
+    ```
+    $ nmcli connection show --active
+    ```
+
+-   显示由NetworkManager识别到设备及其状态：
+
+    ```
+    $ nmcli device status
+    ```
+
+-   使用nmcli工具启动和停止网络接口，在root权限下执行如下命令：
+
+    ```
+    # nmcli connection up id enp3s0
+    # nmcli device disconnect enp3s0
+    ```
+
+
+#### 设置网络连接
+
+列出目前可用的网络连接：
+
+```
+$ nmcli con show
+
+
+NAME    UUID                                  TYPE      DEVICE
+enp4s0  5afce939-400e-42fd-91ee-55ff5b65deab  ethernet  enp4s0
+enp3s0  c88d7b69-f529-35ca-81ab-aa729ac542fd  ethernet  enp3s0
+virbr0  ba552da6-f014-49e3-91fa-ec9c388864fa  bridge    virbr0
+```
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>输出结果中的NAME字段代表连接ID（名称）。  
+
+添加一个网络连接会生成相应的配置文件，并与相应的设备关联。检查可用的设备，方法如下：
+
+```
+$ nmcli dev status
+
+DEVICE      TYPE      STATE      CONNECTION
+enp3s0      ethernet  connected  enp3s0
+enp4s0      ethernet  connected  enp4s0
+virbr0      bridge    connected  virbr0
+lo          loopback  unmanaged  --
+virbr0-nic  tun       unmanaged  --
+```
+
+
+##### 配置动态IP连接
+
+###### 配置IP
+
+要使用 DHCP 分配网络时，可以使用动态IP配置添加网络配置文件，命令格式如下：
+
+```
+nmcli connection add type ethernet con-name connection-name ifname interface-name
+```
+
+例如创建名为net-test的动态连接配置文件，在root权限下使用以下命令：
+
+```
+# nmcli connection add type ethernet con-name net-test ifname enp3s0
+Connection 'net-test' (a771baa0-5064-4296-ac40-5dc8973967ab) successfully added.
+```
+
+NetworkManager 会将参数 connection.autoconnect 设定为 yes，并将设置保存到 “/etc/sysconfig/network-scripts/ifcfg-net-test”文件中，在该文件中会将 ONBOOT 设置为 yes。
+
+###### 激活连接并检查状态
+
+在root权限下使用以下命令激活网络连接：
+
+```
+# nmcli con up net-test 
+Connection successfully activated (D-Bus active path:/org/freedesktop/NetworkManager/ActiveConnection/5)
+```
+
+检查这些设备及连接的状态，使用以下命令：
+
+```
+$ nmcli device status
+
+DEVICE      TYPE      STATE      CONNECTION
+enp4s0      ethernet  connected  enp4s0
+enp3s0      ethernet  connected  net-test
+virbr0      bridge    connected  virbr0
+lo          loopback  unmanaged  --
+virbr0-nic  tun       unmanaged  --
+```
+
+##### 配置静态IP连接
+
+###### 配置IP
+
+添加静态 IPv4 配置的网络连接，可使用以下命令：
+
+```
+nmcli connection add type ethernet con-name connection-name ifname interface-name ip4 address gw4 address
+```
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>如果要添加 IPv6 地址和网关信息，使用 ip6 和 gw6 选项。  
+
+例如创建名为 net-static的静态连接配置文件，在root权限下使用以下命令：
+
+```
+# nmcli con add type ethernet con-name net-static ifname enp3s0 ip4 192.168.0.10/24 gw4 192.168.0.254
+```
+
+还可为该设备同时指定 IPv6 地址和网关，示例如下：
+
+```
+# nmcli con add type ethernet con-name test-lab ifname enp3s0 ip4 192.168.0.10/24 gw4 192.168.0.254 ip6 abbe::**** gw6 2001:***::*
+Connection 'net-static' (63aa2036-8665-f54d-9a92-c3035bad03f7) successfully added.
+```
+
+NetworkManager 会将其内部参数 ipv4.method 设定为 manual，将 connection.autoconnect 设定为yes，并将设置写入 /etc/sysconfig/network-scripts/ifcfg-my-office 文件，其中会将对应 BOOTPROTO 设定为 none，将 ONBOOT 设定为 yes。
+
+设定两个 IPv4 DNS 服务器地址，在root权限下使用以下命令：
+
+```
+# nmcli con mod net-static ipv4.dns "*.*.*.* *.*.*.*"
+```
+
+设置两个 IPv6 DNS 服务器地址，在root权限下使用以下命令：
+
+```
+# nmcli con mod net-static ipv6.dns "2001:4860:4860::**** 2001:4860:4860::****"
+```
+
+###### 激活连接并检查状态
+
+激活新的网络连接，在root权限下使用以下命令：
+
+```
+# nmcli con up net-static ifname enp3s0
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/6)
+```
+
+检查这些设备及连接的状态，使用以下命令：
+
+```
+$ nmcli device status
+
+DEVICE      TYPE      STATE      CONNECTION
+enp4s0      ethernet  connected  enp4s0
+enp3s0      ethernet  connected  net-static
+virbr0      bridge    connected  virbr0
+lo          loopback  unmanaged  --
+virbr0-nic  tun       unmanaged  --
+```
+
+查看配置的连接详情，使用以下命令（使用 -p, \-\-pretty 选项在输出结果中添加标题和分段）：
+
+```
+$ nmcli -p con show net-static 
+===============================================================================
+Connection profile details (net-static )
+===============================================================================
+connection.id:                          net-static
+connection.uuid:                        b9f18801-6084-4aee-af28-c8f0598ff5e1
+connection.stable-id:                   --
+connection.type:                        802-3-ethernet
+connection.interface-name:              enp3s0
+connection.autoconnect:                 yes
+connection.autoconnect-priority:        0
+connection.autoconnect-retries:         -1 (default)
+connection.multi-connect:               0 (default)
+connection.auth-retries:                -1
+connection.timestamp:                   1578988781
+connection.read-only:                   no
+connection.permissions:                 --
+connection.zone:                        --
+connection.master:                      --
+connection.slave-type:                  --
+connection.autoconnect-slaves:          -1 (default)
+connection.secondaries:                 --
+connection.gateway-ping-timeout:        0
+connection.metered:                     unknown
+connection.lldp:                        default
+connection.mdns:                        -1 (default)
+connection.llmnr:                       -1 (default)
+```
+
+##### 添加 Wi-Fi 连接
+
+使用以下命令查看可用 Wi-Fi 访问点：
+
+```
+$ nmcli dev wifi list
+```
+
+使用以下命令生成使用的静态 IP 配置，但允许自动 DNS 地址分配的 Wi-Fi 连接：
+
+```
+$ nmcli con add con-name Wifi ifname wlan0 type wifi ssid MyWifi ip4 192.168.100.101/24 gw4 192.168.100.1
+```
+
+请使用以下命令设定 WPA2 密码，例如 “answer”：
+
+```
+$ nmcli con modify Wifi wifi-sec.key-mgmt wpa-psk
+$ nmcli con modify Wifi wifi-sec.psk answer
+```
+
+使用以下命令更改 Wi-Fi 状态：
+
+```
+$ nmcli radio wifi [ on | off ]
+```
+
+##### 更改属性
+
+请使用以下命令检查具体属性，比如 mtu：
+
+```
+$ nmcli connection show id 'Wifi ' | grep mtu
+802-11-wireless.mtu: auto
+```
+
+使用如下命令更改设置的属性：
+
+```
+$ nmcli connection modify id 'Wifi ' 802-11-wireless.mtu 1350
+```
+
+使用如下命令确认更改：
+
+```
+$ nmcli connection show id 'Wifi ' | grep mtu
+802-11-wireless.mtu: 1350
+```
+
+#### 配置静态路由
+
+-   使用nmcli命令为网络连接配置静态路由，使用命令如下：
+
+    ```
+    $ nmcli connection modify enp3s0 +ipv4.routes "192.168.122.0/24 10.10.10.1"
+    ```
+
+
+-   使用编辑器配置静态路由，使用如下命令：
+
+    ```
+    $ nmcli con edit type ethernet con-name enp3s0
+    ===| nmcli interactive connection editor |===
+    Adding a new '802-3-ethernet' connection
+    Type 'help' or '?' for available commands.
+    Type 'describe [.]' for detailed property description.
+    You may edit the following settings: connection, 802-3-ethernet (ethernet), 802-1x, ipv4, ipv6, dcb
+    nmcli> set ipv4.routes 192.168.122.0/24 10.10.10.1
+    nmcli>
+    nmcli> save persistent
+    Saving the connection with 'autoconnect=yes'. That might result in an immediate activation of the connection.
+    Do you still want to save? [yes] yes
+    Connection 'enp3s0' (1464ddb4-102a-4e79-874a-0a42e15cc3c0) successfully saved.
+    nmcli> quit
+    ```
+
+
+### 使用ip命令
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>使用ip命令配置的网络配置可以立即生效但系统重启后配置会丢失。  
+
+
+
+#### 配置IP地址
+
+使用ip命令为接口配置地址，命令格式如下，其中  _interface-name_  为网卡名称。
+
+```
+ip addr [ add | del ] address dev interface-name
+```
+
+##### 配置静态地址
+在root权限下，配置设置IP地址，使用示例如下：
+
+```
+# ip address add 192.168.0.10/24 dev enp3s0
+```
+
+查看配置结果，在root权限使用如下命令：
+
+```
+# ip addr show dev enp3s0
+2: enp3s0:  mtu 1500 qdisc fq_codel state UP group default qlen 1000
+    link/ether 52:54:00:aa:ad:4a brd ff:ff:ff:ff:ff:ff
+    inet 192.168.202.248/16 brd 192.168.255.255 scope global dynamic noprefixroute enp3s0
+       valid_lft 9547sec preferred_lft 9547sec
+    inet 192.168.0.10/24 scope global enp3s0
+       valid_lft forever preferred_lft forever
+    inet6 fe80::32e8:cc22:9db2:f4d4/64 scope link noprefixroute
+       valid_lft forever preferred_lft forever
+```
+
+##### 配置多个地址
+ip 命令支持为同一接口分配多个地址，可在root权限下重复多次使用 ip 命令实现分配多个地址。使用示例如下：
+
+```
+# ip address add 192.168.2.223/24 dev enp4s0
+# ip address add 192.168.4.223/24 dev enp4s0
+# ip addr
+
+3: enp4s0:  mtu 1500 qdisc fq_codel state UP group default qlen 1000
+    link/ether 52:54:00:aa:da:e2 brd ff:ff:ff:ff:ff:ff
+    inet 192.168.203.12/16 brd 192.168.255.255 scope global dynamic noprefixroute enp4s0
+       valid_lft 8389sec preferred_lft 8389sec
+    inet 192.168.2.223/24 scope global enp4s0
+       valid_lft forever preferred_lft forever
+    inet 192.168.4.223/24 scope global enp4s0
+       valid_lft forever preferred_lft forever
+    inet6 fe80::1eef:5e24:4b67:f07f/64 scope link noprefixroute
+       valid_lft forever preferred_lft forever
+```
+
+#### 配置静态路由
+
+如果需要静态路由，可使用 ip route add 命令在路由表中添加，使用 ip route del 命令删除。最常使用的 ip route 命令格式如下：
+
+```
+ip route [ add | del | change | append | replace ] destination-address
+```
+
+在root权限下使用 ip route 命令显示当前的 IP 路由表。示例如下：
+
+```
+# ip route
+
+default via 192.168.0.1 dev enp3s0 proto dhcp metric 100
+default via 192.168.0.1 dev enp4s0 proto dhcp metric 101
+192.168.0.0/16 dev enp3s0 proto kernel scope link src 192.168.202.248 metric 100
+192.168.0.0/16 dev enp4s0 proto kernel scope link src 192.168.203.12 metric 101
+192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
+```
+
+在主机地址中添加一个静态路由，在 root 权限下，使用以下命令格式：
+
+```
+ip route add 192.168.2.1 via 10.0.0.1 [dev interface-name]
+```
+
+其中 192.168.2.1 是用点分隔的十进制符号中的 IP 地址，10.0.0.1 是下一个跃点，_interface-name_  是进入下一个跃点的退出接口。
+
+要在网络中添加一个静态路由，即代表 IP 地址范围的 IP 地址，请在root权限下运行以下命令格式：
+
+```
+ip route add 192.168.2.0/24 via 10.0.0.1 [dev interface-name]
+```
+
+其中 192.168.2.1 是目标网络的 IP 地址，10.0.0.1 是网络前缀，_interface-name_  为网卡名称。
+
+### 通过ifcfg文件配置网络
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>通过ifcfg文件配置的网络配置不会立即生效，需要在root权限下执行**systemctl reload NetworkManager**命令以重启网络服务后才生效。  
+
+#### 配置静态网络
+
+以enp4s0网络接口进行静态网络设置为例，通过在root权限下修改ifcfg文件实现，在/etc/sysconfig/network-scripts/目录中生成名为ifcfg-enp4s0的文件中，修改参数配置，示例如下：
+
+```
+TYPE=Ethernet
+PROXY_METHOD=none
+BROWSER_ONLY=no
+BOOTPROTO=none
+IPADDR=192.168.0.10
+PREFIX=24
+DEFROUTE=yes
+IPV4_FAILURE_FATAL=no
+IPV6INIT=yes
+IPV6_AUTOCONF=yes
+IPV6_DEFROUTE=yes
+IPV6_FAILURE_FATAL=no
+IPV6_ADDR_GEN_MODE=stable-privacy
+NAME=enp4s0static
+UUID=08c3a30e-c5e2-4d7b-831f-26c3cdc29293
+DEVICE=enp4s0
+ONBOOT=yes
+```
+
+#### 配置动态网络
+
+要通过ifcfg文件为em1接口配置动态网络，请按照如下操作在/etc/sysconfig/network-scripts/目录中生成名为 ifcfg-em1 的文件，示例如下：
+
+```
+DEVICE=em1
+BOOTPROTO=dhcp
+ONBOOT=yes
+```
+
+要配置一个向DHCP服务器发送不同的主机名的接口，请在ifcfg文件中新增一行内容，如下所示：
+
+```
+DHCP_HOSTNAME=hostname
+```
+
+要配置忽略由DHCP服务器发送的路由，防止网络服务使用从DHCP服务器接收的DNS服务器更新/etc/resolv.conf。请在ifcfg文件中新增一行内容，如下所示：
+
+```
+PEERDNS=no
+```
+
+要配置一个接口使用具体DNS服务器，请将参数PEERDNS=no，并在ifcfg文件中添加以下行：
+
+```
+DNS1=ip-address
+DNS2=ip-address
+```
+
+其中ip-address是DNS服务器的地址。这样就会让网络服务使用指定的DNS服务器更新/etc/resolv.conf。
+
+#### 配置默认网关
+
+在确定默认网关时，首先解析 /etc/sysconfig/network 文件，然后解析 ifcfg 文件 ，将最后读取的 GATEWAY 的取值作为路由表中的默认路由。
+
+在动态网络环境中，使用 NetworkManager 管理主机时，建议设置为由 DHCP 来分配。
+
+## 配置主机名
+
+
+### 简介
+
+hostname有三种类型：static、transient和pretty。
+
+-   static：静态主机名，可由用户自行设置，并保存在/etc/hostname 文件中。
+-   transient：动态主机名，由内核维护，初始是 static 主机名，默认值为“localhost”。可由DHCP或mDNS在运行时更改。
+-   pretty：灵活主机名，允许使用自由形式（包括特殊/空白字符）进行设置。静态/动态主机名遵从域名的通用限制。
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>static和transient主机名只能包含a-z、A-Z、0-9、“-”、“\_”和“.”，不能在开头或结尾处使用句点，不允许使用两个相连的句点，大小限制为 64 个字符。  
+
+### 使用hostnamectl配置主机名
+
+#### 查看所有主机名
+查看当前的主机名，使用如下命令：
+
+```
+$ hostnamectl status
+```
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>如果命令未指定任何选项，则默认使用status选项。  
+
+#### 设定所有主机名
+在root权限下，设定系统中的所有主机名，使用如下命令：
+
+```
+# hostnamectl set-hostname name
+```
+
+#### 设定特定主机名
+在root权限下，通过不同的参数来设定特定主机名，使用如下命令：
+
+```
+# hostnamectl set-hostname name [option...]
+```
+
+其中option可以是\-\-pretty、\-\-static、\-\-transient中的一个或多个选项。
+
+如果\-\-static或\-\-transient与\-\-pretty选项一同使用时，则会将static和transient主机名简化为pretty主机名格式，使用“-”替换空格，并删除特殊字符。
+
+当设定pretty主机名时，如果主机名中包含空格或单引号，需要使用引号。命令示例如下：
+
+```
+# hostnamectl set-hostname "Stephen's notebook" --pretty
+```
+
+#### 清除特定主机名
+要清除特定主机名，并将其还原为默认形式，在root权限下，使用如下命令：
+
+```
+# hostnamectl set-hostname "" [option...]
+```
+
+其中 "" 是空白字符串，option是\-\-pretty、\-\-static和\-\-transient中的一个或多个选项。
+
+#### 远程更改主机名
+在远程系统中运行hostnamectl命令时，要使用-H，\-\-host 选项，在root权限下使用如下命令：
+
+```
+# hostnamectl set-hostname -H [username]@hostname new_hostname
+```
+
+其中hostname是要配置的远程主机，username为自选项，new\_hostname为新主机名。hostnamectl会通过SSH连接到远程系统。
+
+### 使用nmcli配置主机名
+
+查询static主机名，使用如下命令：
+
+```
+$ nmcli general hostname
+```
+
+在root权限下，将static主机名设定为host-server，使用如下命令：
+
+```
+# nmcli general hostname host-server
+```
+
+要让系统hostnamectl感知到static主机名的更改，在root权限下，重启hostnamed服务，使用如下命令：
+
+```
+# systemctl restart systemd-hostnamed
+```
+
+## 配置网络绑定
+
+
+### 使用nmcli
+
+-   创建名为mybond0的绑定，使用示例如下：
+
+    ```
+    $ nmcli con add type bond con-name mybond0 ifname mybond0 mode active-backup
+    ```
+
+-   添加从属接口，使用示例如下：
+
+    ```
+    $ nmcli con add type bond-slave ifname enp3s0 master mybond0
+    ```
+
+    要添加其他从属接口，重复上一个命令，并在命令中使用新的接口，使用示例如下：
+
+    ```
+    $ nmcli con add type bond-slave ifname enp4s0 master mybond0
+    Connection 'bond-slave-enp4s0' (05e56afc-b953-41a9-b3f9-0791eb49f7d3) successfully added.
+    ```
+
+-   要启动绑定，则必须首先启动从属接口，使用示例如下：
+
+    ```
+    $ nmcli con up bond-slave-enp3s0
+    Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/14)
+    ```
+
+    ```
+    $ nmcli con up bond-slave-enp4s0
+    Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/15)
+    ```
+
+    现在可以启动绑定，使用示例如下：
+
+    ```
+    $ nmcli con up mybond0
+    Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/16)
+    ```
+
+
+### 使用命令行
+
+
+
+#### 检查是否已安装Bonding内核模块
+
+在系统中默认已加载相应模块。要载入绑定模块，可在root权限下使用如下命令：
+
+```
+# modprobe --first-time bonding
+```
+
+显示该模块的信息，可在root权限下使用如下命令：
+
+```
+# modinfo bonding
+```
+
+更多命令请在root权限下使用modprobe \-\-help查看。
+
+#### 创建频道绑定接口
+
+要创建绑定接口，可在root权限下通过在 /etc/sysconfig/network-scripts/ 目录中创建名为 ifcfg-bondN 的文件（使用接口号码替换 N，比如 0）。
+
+根据要绑定接口类型的配置文件来编写相应的内容，比如网络接口。接口配置文件示例如下：
+
+```
+DEVICE=bond0
+NAME=bond0
+TYPE=Bond
+BONDING_MASTER=yes
+IPADDR=192.168.1.1
+PREFIX=24
+ONBOOT=yes
+BOOTPROTO=none
+BONDING_OPTS="bonding parameters separated by spaces"
+```
+
+#### 创建从属接口
+
+创建频道绑定接口后，必须在从属接口的配置文件中添加 MASTER 和 SLAVE 指令。
+
+例如将两个网络接口enp3s0 和 enp4s0 以频道方式绑定，其配置文件示例分别如下：
+
+```
+TYPE=Ethernet
+NAME=bond-slave-enp3s0
+UUID=3b7601d1-b373-4fdf-a996-9d267d1cac40
+DEVICE=enp3s0
+ONBOOT=yes
+MASTER=bond0
+SLAVE=yes
+```
+
+```
+TYPE=Ethernet
+NAME=bond-slave-enp4s0
+UUID=00f0482c-824f-478f-9479-abf947f01c4a
+DEVICE=enp4s0
+ONBOOT=yes
+MASTER=bond0
+SLAVE=yes
+```
+
+#### 激活频道绑定
+
+要激活绑定，则需要启动所有从属接口。请在root权限下，运行以下命令：
+
+```
+# ifup enp3s0
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/7)
+```
+
+```
+# ifup enp4s0
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/8)
+```
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>对于已经处于“up”状态的接口，请首先使用“ifdown  _enp3s0_  ”命令修改状态为down，其中  _enp3s0_  为实际网卡名称。  
+
+完成后，启动所有从属接口以便启动绑定（不将其设定为 “down”）。
+
+要让 NetworkManager 感知到系统所做的修改，在每次修改后，请在root权限下，运行以下命令：
+
+```
+# nmcli con load /etc/sysconfig/network-scripts/ifcfg-device
+```
+
+查看绑定接口的状态，请在root权限下运行以下命令：
+
+```
+# ip link show
+
+1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
+    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+2: enp3s0:  mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
+    link/ether 52:54:00:aa:ad:4a brd ff:ff:ff:ff:ff:ff
+3: enp4s0:  mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
+    link/ether 52:54:00:aa:da:e2 brd ff:ff:ff:ff:ff:ff
+4: virbr0:  mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
+    link/ether 86:a1:10:fb:ef:07 brd ff:ff:ff:ff:ff:ff
+5: virbr0-nic:  mtu 1500 qdisc fq_codel master virbr0 state DOWN mode DEFAULT group default qlen 1000
+    link/ether 52:54:00:29:35:4c brd ff:ff:ff:ff:ff:ff
+```
+
+#### 创建多个绑定
+
+系统会为每个绑定创建一个频道绑定接口，包括 BONDING\_OPTS 指令。使用这个配置方法可让多个绑定设备使用不同的配置。请按照以下操作创建多个频道绑定接口：
+
+-   创建多个 ifcfg-bondN 文件，文件中包含 BONDING\_OPTS 指令，让网络脚本根据需要创建绑定接口。
+-   创建或编辑要绑定的现有接口配置文件，添加 SLAVE 指令。
+-   使用 MASTER 指令工具在频道绑定接口中分配要绑定的接口，即从属接口。
+
+以下是频道绑定接口配置文件示例：
+
+```
+DEVICE=bondN
+NAME=bondN
+TYPE=Bond
+BONDING_MASTER=yes
+IPADDR=192.168.1.1
+PREFIX=24
+ONBOOT=yes
+BOOTPROTO=none
+BONDING_OPTS="bonding parameters separated by spaces"
+```
+
+在这个示例中，使用绑定接口的号码替换 N。例如要创建两个接口，则需要使用正确的 IP 地址创建两个配置文件 ifcfg-bond0 和 ifcfg-bond1。
+
+## IPv6使用差异说明（vs IPv4）
+
+
+
+### 约束限制
+
+-   chrony支持全局地址（global address），不支持链路本地地址（link-local address）。
+-   Firefox支持通过http/https协议访问全局地址（global address），不支持链路本地地址（link-local address）。
+
+### 配置说明
+#### 设置接口设备MTU值
+
+##### 概述
+
+IPv6场景中会发现整个路由路径中的最小mtu的值作为当前链接的PMTU的值，源端根据PMTU的值确定是否进行分片发送，而在整个路径中的其它设备将不再需要进行分片处理，从而可以降低中间路由设备的负载大小。其中IPv6 PMTU设置的最小值为1280。
+
+##### 设置接口设备的mtu
+
+如果在配置了IPv6地址的接口上设置mtu的值小于1280（IPv6 PMTU设置的最小值），则会导致该接口的IPv6地址被删除。并且无法再次添加IPv6地址。所以在IPv6场景中，对接口设备的mtu的配置一定要大于等于1280。
+请在root权限下运行如下命令查看具体现象：
+
+```
+# ip addr show enp3s0
+3: enp3s0:  mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
+    link/ether 52:54:00:62:xx:xx brd ff:ff:ff:ff:xx:xx
+    inet 10.41.125.236/16 brd 10.41.255.255 scope global noprefixroute dynamic enp3s0
+       valid_lft 38663sec preferred_lft 38663sec
+    inet6 2001:222::2/64 scope global
+       valid_lft forever preferred_lft forever
+```
+
+```
+# ip link set dev enp3s0 mtu 1200
+# ip addr show enp3s0
+3: enp3s0:  mtu 1200 qdisc pfifo_fast state UP group default qlen 1000
+    link/ether 52:54:00:62:xx:xx brd ff:ff:ff:ff:xx:xx
+    inet 10.41.125.236/16 brd 10.41.255.255 scope global noprefixroute dynamic enp3s0
+       valid_lft 38642sec preferred_lft 38642sec
+```
+
+```
+# ip addr add 2001:222::2/64 dev enp3s0
+RTNETLINK answers: No buffer space available
+```
+
+```
+# ip link set dev enp3s0 mtu 1500
+# ip addr show enp3s0
+3: enp3s0:  mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
+    link/ether 52:54:00:62:xx:xx brd ff:ff:ff:ff:xx:xx
+    inet 10.41.125.236/16 brd 10.41.255.255 scope global noprefixroute dynamic enp3s0
+       valid_lft 38538sec preferred_lft 38538sec
+```
+
+```
+# ip addr add 2001:222::2/64 dev enp3s0
+# ip addr show enp3s0
+3: enp3s0:  mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
+    link/ether 52:54:00:62:xx:xx brd ff:ff:ff:ff:xx:xx
+    inet 10.41.125.236/16 brd 10.41.255.255 scope global noprefixroute dynamic enp3s0
+       valid_lft 38531sec preferred_lft 38531sec
+    inet6 2001:222::2/64 scope global
+       valid_lft forever preferred_lft forever
+```
+
+#### 有状态自动配置IPv6地址
+
+##### 概述
+
+IPv6与IPv4都可以在root权限下通过DHCP的方式获得IP地址。IPv6地址有两种配置方式：无状态自动配置和有状态自动配置。
+
+-   无状态自动配置
+
+    不需要DHCP服务进行管理，设备根据网络RA（路由公告）获得网络前缀，或者link-local地址为固定fe80::。而接口ID则根据ifcfg配置IPV6\_ADDR\_GEN\_MODE的具体设置来进行自动获得：
+
+    1.  IPv6\_ADDR\_GEN\_MODE="stable-privacy" 则根据设备及网络环境来确定一个随机接口ID。
+    2.  IPv6\_ADDR\_GEN\_MODE="EUI64" 则根据设备MAC地址来确定接口ID。
+
+-   有状态自动配置：需要DHCP服务器进行管理分配，服从DHCPv6协议来从DHCPv6服务器端租赁IPv6地址。
+
+    在有状态自动配置IPv6地址时，DHCPv6服务端可以通过客户端设置的vendor class将客户端进行分类，不同类别分配不同地址段的IPv6地址。在IPv4场景中，客户端可以直接用dhclient的-V选项来设置vendor-class-identifier，DHCP服务端在配置文件中根据vendor-class-identifier来对客户端进行分类处理。而IPv6场景中，如果使用同样的方法对客户端分类，则分类并不会生效。
+
+    ```
+    dhclient -6  -V  
+    ```
+
+    这是由于DHCPv6和DHCP协议存在较大差异，DHCPv6的可选项中使用vendor-class-option替代了DHCP中的vendor-class-identifier。而dhclient的-V选项并不能设置vendor-class-option。
+
+
+##### 有状态自动配置IPv6地址时dhclient设置vendor class方法
+
+-   在客户端使用配置文件方式添加对vendor class的设置，使用方法如下：
+
+    客户端配置文件（/etc/dhcp/dhclient6.conf），文件位置可以自定义，在使用时需要通过dhclient -cf选项来指定配置文件：
+
+    ```
+    option dhcp6.vendor-class code 16 = {integer 32, integer 16, string};
+    interface "enp3s0" {
+            send dhcp6.vendor-class   ;
+    }
+    ```
+
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
+    >-   \，32位整型数字，企业标识号，企业通过IANA注册。  
+    >-   \，16位整型数字，vendor class字符串长度。  
+    >-   \，要设置的vendor class字符串，例如：“HWHW”。  
+
+    客户端使用方法：
+
+    ```
+    dhclient -6  -cf /etc/dhcp/dhclient6.conf
+    ```
+
+
+-   DHCPv6服务端配置文件（/etc/dhcp/dhcpd6.conf），需要dhcpd -cf选项来指定该配置文件：
+
+    ```
+    option dhcp6.vendor-class code 16 = {integer 32, integer 16, string};
+    subnet6 fc00:4:12:ffff::/64 {
+            class "hw" {
+                    match if substring ( option dhcp6.vendor-class, 6, 10 ) = "HWHW";
+            }
+            pool6 {
+                    allow members of "hw";
+                    range6 fc00:4:12:ffff::ff10 fc00:4:12:ffff::ff20;
+            }
+            pool6 {
+                    allow unknown clients;
+                    range6 fc00:4:12:ffff::100 fc00:4:12:ffff::120;
+            }
+    }
+    ```
+
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
+    >substring \( option dhcp6.vendor-class, 6, 10 \) 其中子字符串的开始位置为6，因为前面包含4个字节的和2个字节的。而子字符串的结束位置位：6+。这里vendor class string为“HWHW”，字符串的长度为4，所以子字符串的结束位置为6+4=10。用户可以根据实际需要来确定及相应的。  
+
+    服务端使用方法：
+
+    ```
+    dhcpd -6 -cf /etc/dhcp/dhcpd6.conf 
+    ```
+
+
+#### 内核支持socket相关系统调用
+
+##### 概述
+
+IPv6地址长度扩展到128比特，所以有足够的IPv6地址可供分配使用。同时IPv6头相比IPv4头进行了简化，并增强了IPv6的自动配置功能。IPv6地址分为单播地址，组播地址和任意播地址。常用的单播地址又包含：链路本地地址（link-local address），唯一本地地址（Unique local address）和全局地址（global address）。由于IPv6的全局地址十分充足，唯一本地地址一般不被使用（其前身为站点本地地址（site-local address），已于2004年被废弃）。当前主要使用的单播地址为：链路本地地址（link-local address）和全局地址（global address）。当前内核支持socket系统调用，在使用单播地址的链路本地地址和全局地址时存在差异。
+
+##### link-local地址和global地址在socket调用时的差异
+
+RFC 2553： Basic Socket Interface Extensions for IPv6 定义sockaddr\_in6的数据结构如下；
+
+```
+struct sockaddr_in6 {     
+    uint8_t         sin6_len;       /* length of this struct */     
+    sa_family_t     sin6_family;    /* AF_INET6 */     
+    in_port_t       sin6_port;      /* transport layer port # */     
+    uint32_t        sin6_flowinfo;  /* IPv6 flow information */     
+    struct in6_addr sin6_addr;      /* IPv6 address */     
+    uint32_t        sin6_scope_id;  /* set of interfaces for a scope */ 
+}; 
+```
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>sin6\_scope\_id： 32位整型，对于链路本地地址（link-local address），对于链路范围的sin6\_addr，它可以用来标识指定的接口索引号。如果是站点范围的sin6\_addr，则用来作为站点的标识符（站点本地地址已被抛弃）。  
+
+在使用link-local地址进行socket通信时，在构造目的地址时，需要制定该地址所对应的接口索引号。一般可以通过if\_nametoindex函数将接口名转化为接口索引号。具体方式如下，
+
+```
+int port = 1234;
+int sk_fd;
+int iff_index = 0;
+char iff_name[100] = "enp3s0";
+char * ll_addr[100] = "fe80::123:456:789";
+struct sockaddr_in6 server_addr;
+
+memset(&server_addr,0,sizeof(structsockaddr_in6));
+iff_index=if_nametoindex(iff_name);
+
+server_addr.sin6_family=AF_INET6;
+server_addr.sin6_port=htons(port);
+server_addr.sin6_scope_id=iff_index;
+inet_pton(AF_INET6, ll_addr, &(server_addr.sin6_addr));
+
+sk_fd=socket(AF_INET6, SOCK_STREAM, IPPROTO_TCP);
+connect(sk_fd, (struct sockaddr *)&server_addr, sizeof(struct sockaddr_in6));
+```
+
+#### IPv4的dhclient守护进程持久化配置
+
+##### 概述
+
+通过NetworkManager服务来管理网络服务时，如果接口ifcfg-配置文件中配置了DHCP方式获得IP地址，则相应地NetworkManager服务会拉起dhclient守护进程来通过DHCP协议方式来从DHCP服务器获取IP地址。
+
+dhclient提供了"-1"选项来决定dhclient进程在未获得DHCP服务响应时，是会不断持久化尝试请求地址还是会尝试时间超时后退出。针对IPv4的dhclient守护进程，可以在ifcfg-配置文件中设置PERSISTENT\_DHCLIENT来决定是否设置IPv4的dhclient进程的持久化。
+
+##### 约束限制
+
+1.  当dhclient进程在运行中被杀死，network服务无法自动将其拉起，可靠性需要用户自己保障。
+2.  配置了持久化选项PERSISTENT\_DHCLIENT，需要确保有相应的DHCP服务器。如果在拉起network时无可用DHCP服务器，dhclient进程不断尝试发送请求包但无回应，则会导致network服务卡死直到network服务超时失败。由于network服务在拉起多个网卡的IPv4 dhclient进程时，是通过串行的方式来拉起的。如果有网卡配置了持久化而DHCP服务器没有准备好，则会导致network服务在给该网卡获取IPv4地址超时卡死，进而导致后续网卡无法获得IPv4/IPv6地址。
+
+以上两种约束限制是特殊的应用场景，需要用户自己进行可靠性保障。
+
+##### IPv4 DHCP和IPv6 DHCPv6方式获取地址的配置差异
+
+可以通过配置接口ifcfg-参数来分别实现IPv4和IPv6通过DHCP/DHCPv6协议来动态获取IP地址，具体配置说明如下；
+
+```
+BOOTPROTO=none|bootp|dhcp
+DHCPV6C=yes|no
+PERSISTENT_DHCLIENT=yes|no|1|0
+```
+
+-   BOOTPROTO： none表示静态配置IPv4地址，bootp|dhcp则会拉起DHCP dhclient来动态获取IPv4地址。
+-   DHCPV6C： no表示静态配置IPv6地址，yes则会拉起DHCPv6 dhclient来动态获取IPv6地址。
+-   PERSISTENT\_DHCLIENT：no|0表示IPv4的dhclient进程配置为“非持久化”，当dhclient向DHCP服务器发送一次请求报文而无响应，则会间隔一段时间后退出，退出值为2。yes|1则表示IPv4的dhclient进程配置为“持久化”，dhclient会向DHCP服务器反复发送请求报文。**如果没有配置PERSISTENT\_DHCLIENT项，则IPv4的dhclient会默认设置为“持久化”**。
+
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
+    >PERSISTENT\_DHCLIENT配置只针对IPv4生效，对IPv6相关dhclient -6进程不生效，IPv6默认不进行持久化配置。  
+
+
+#### iproute相关命令配置IPv4与IPv6时的差异说明
+
+##### 概述
+
+由于IPv4和IPv6是两个不同的协议标准，iproute相关命令在使用方法上存在一定的差异。本章节主要梳理iproute包中用户经常使用到命令在IPv4和IPv6使用方面的差异，从而可以更好地指导用户使用iproute包中相关命令。
+
+iproute相关命令均需要在root权限下运行。
+
+##### IPv6地址的生命周期
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
IPv6状态

+
解释

+
tentative

+
临时状态：刚添加地址还处于地址重复检测DAD过程

+
preferred

+
首选状态：完成DAD过程，没有收到相应的NA报文，表示该地址没有冲突。

+
deprecated

+
弃用状态：地址有一定的使用时限（valid_lft和preferred_lft），preferred_lft到期后地址会变化deprecated状态。

+
该状态下的地址不能用于创建新的连接，但是原有的连接可以继续使用。

+
invalid

+
无效状态：使用时限超过preferred_lft一段时间后仍然没有成功进行租约续约，则valid_lft时间到后地址状态会被设置为invalid，表示该地址不可以再被使用。

+

+
+其它说明：
+
+-   preferred\_lft：preferred lifetime，地址为首选状态的寿命，preferred\_lft没有到期的地址可以用于正常通信使用，若有多个preferred地址则按照内核具体机制选择地址。
+-   valid\_lft： valid lifetime，地址有效的寿命，在\[preferred\_lft, valid\_lft\]时间段内该地址不能被用于新建连接，已经创建的连接继续有效。
+
+##### ip link 命令
+
+命令：
+
+```
+ip link set IFNAME mtu MTU
+```
+
+IPv6中PMTU的最小值为1280，如果mtu值设置小于1280则会导致IPv6地址丢失。其它设备无法ping通该IPv6地址。
+
+##### ip addr命令
+
+1.  命令：
+
+    ```
+    ip [-6] addr add IFADDR dev IFNAME
+    ```
+
+    添加IPv6地址可以选择添加-6选项也可以不添加，ip addr命令会根据具体地址类型来判断是ipv4地址还是IPv6地址。
+
+    如果指定“-6”选项，但是IFADDR 是ipv4地址则会有错误返回。
+
+2.  命令：
+
+    ```
+    ip [-6] addr add IFADDR  dev IFNAME [home|nodad]
+    ```
+
+    \[home|nodad\] 选项只针对IPv6地址有效。
+
+    -   home：将该地址指定为RFC 6275中定义的家庭地址。（这是移动节点从家庭链路获取的地址， 是移动节点的永久地址，如果移动节点保持在相同的归属链路中，则各种实体之间的通信照常进行。）
+    -   nodad：配置该项（仅限IPv6）添加此地址时不执行重复地址检测DAD（RFC 4862）。如果一台设备上多个接口通过nodad配置了多个相同的IPv6地址，则会按照接口顺序使用该IPv6地址。同一个接口上不能添加一个nodad一个非nodad的相同IPv6地址。因为两个地址是一样的，所以会报“RTNETLINK answers: File exists”。
+
+3.  命令：
+
+    ```
+    ip [-6] addr del IFADDR dev IFNAME
+    ```
+
+    删除IPv6地址可以选择添加-6选项也可以不添加，ip addr del命令会根据具体地址类型来判断是ipv4地址还是IPv6地址。
+
+4.  命令：
+
+    ```
+    ip [-6] addr show dev IFNAME [tentative|-tentative|deprecated|-deprecated|dadfailed|-dadfailed|temporary]
+    ```
+
+    -   不指定-6选项，则会同时打印IPv4和IPv6地址。指定-6选项则只打印IPv6地址。
+    -   \[tentative|-tentative|deprecated|-deprecated|dadfailed|-dadfailed|temporary\]，这些选项只针对IPv6，可以根据IPv6地址状态对地址进行筛选查看。
+        1.  tentative：（仅限IPv6）仅列出尚未通过重复地址检测的地址。
+        2.  -tentative：（仅限IPv6）仅列出当前未处于重复地址检测过程中的地址。
+        3.  deprecated：（仅限IPv6）仅列出已弃用的地址。
+        4.  -deprecated：（仅限IPv6）仅列出未弃用的地址。
+        5.  dadfailed：（仅限IPv6）仅列出重复地址检测失败的地址。
+        6.  -dadfailed：（仅限IPv6）仅列出未重复地址检测失败的地址。
+        7.  temporary：（仅限IPv6）仅列出临时地址
+
+
+
+##### ip route命令
+
+1.  命令：
+
+    ```
+    ip [-6] route add ROUTE [mtu lock MTU]
+    ```
+
+    -   -6选项：添加IPv6路由可以选择添加-6选项也可以不添加，ip route命令会根据具体地址类型来判断是IPv4地址还是IPv6地址。
+
+    -   mtu lock MTU：锁定路由的MTU值。如果不锁定MTU，则MTU的值则可能在PMTUD过程中被内核改变。如果锁定MTU，则不会尝试PMTUD，所有IPv4包都将不设置DF位发出，IPv6包则会按照MTU进行分段处理。
+
+2.  命令：
+
+    ```
+    ip [-6] route del ROUTE
+    ```
+
+    删除IPv6路由可以选择添加-6选项也可以不添加，ip route命令会根据具体地址类型来判断是IPv4地址还是IPv6地址。
+
+
+##### ip rule命令
+
+1.  命令：
+
+    ```
+    ip [-6] rule list
+    ```
+
+    -6选项：设置-6选项打印IPv6的策略路由，不设置-6选项打印IPv4的策略路由。所以需要根据具体协议类型来配置-6选项。
+
+2.  命令：
+
+    ```
+    ip [-6] rule [add|del] [from|to] ADDR table TABLE pref PREF
+    ```
+
+    -6选项：IPv6相关的策略路由表项需要设置-6选项，否则会报错：“Error: Invalid source address.”。相应地，IPv4相关的策略路由表项不可以设置-6选项，否则会报错：“Error: Invalid source address.”。
+
+
+#### NetworkManager服务配置差异说明
+
+##### 概述
+
+NetworkManager服务使用ifup/ifdown的逻辑接口定义进行高级网络设置。其参数大多数都是在/etc/sysconfig/network和/etc/sysconfig/network-scripts/ifcfg-两个配置文件设置。前者为全局设置，后者为指定网卡的设置，当两者有冲突时，后者生效。
+
+##### 配置差异说明
+
+其中在/etc/sysconfig/network下的配置差异有：
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
IPv4

+
IPv6

+
含义说明

+
NA

+
IPV6FORWARDING=yes|no

+
IPv6转发，默认不转发。

+
NA

+
IPV6_AUTOCONF=yes|no

+
IPv6转发打开是no，否则是yes。

+
NA

+
IPV6_ROUTER=yes|no

+
IPv6转发打开是yes，否则是no。

+
NA

+
IPV6_AUTOTUNNEL=yes|no

+
指定Tunnel为自动隧道模式，默认是no。

+
GATEWAY

+
IPV6_DEFAULTGW=<IPv6 address[%interface]> (optional)

+
在IPv6中设置默认网关。

+
NA

+
IPV6_DEFAULTDEV=<interface> (optional)

+
指定默认转发的网卡。

+
NA

+
IPV6_RADVD_PIDFILE=<pid-file> (optional)

+
默认ipv6_radvd_pid路径：/var/run/radvd/radvd.pid。

+
NA

+
IPV6_RADVD_TRIGGER_ACTION=startstop|reload|restart|SIGHUP (optional)

+
radvd默认触发动作。

+

+
+而在/etc/sysconfig/network-scripts/ifcfg-下的差异主要有：
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
IPv4

+
IPv6

+
含义说明

+
IPADDRn

+
IPV6ADDR=<IPv6 address>[/<prefix length>]

+
ip地址。

+
PREFIXn

+
NA

+
网络前缀，网络别名和ppp无效，优先级高于NETMASK。

+
NETMASKn

+
NA

+
子网掩码，仅用于别名和ppp。

+
GATEWAY

+
IPV6_DEFAULTGW=<IPv6 address[%interface]> (optional)

+
默认网关。

+
MTU

+
IPV6_MTU=<MTU of link> (optional)

+
默认MTU。

+
IPV4_FAILURE_FATAL=yes|no

+
IPV6_FAILURE_FATAL

+
默认值是no。若设置为yes，dhclient失败ifup-eth会直接退出。

+
NA

+
IPV6_PRIVACY=rfc3041

+
默认禁用。

+
NA

+
IPV6INIT=yes|no

+
默认开启IPv6。

+
NA

+
IPV6FORWARDING=yes|no

+
默认关闭，已废弃。

+

+
+### FAQ
+#### iscsi-initiator-utils不支持登录fe80 IPv6地址
+
+##### 问题现象
+
+客户端通过IPv6登录iscsi服务端时，使用如“iscsiadm -m node -p ipv6address -l”的命令格式登录，如果是全局地址（global address），直接替换将命令范例中的“ipv6address”替换为全局地址即可；但如果是链路本地地址（link-local address，fe80开头的IPv6地址）则无法使用，因为iscsi-initiator-utils目前机制还不支持用链路本地地址（link-local address）地址登录iscsi服务端。
+
+##### 原因分析
+
+如果使用格式如“iscsiadm -m node -p fe80::xxxx -l”登录，会登录超时返回，这是因为使用链路本地地址必须指定接口，否则使用iscsi\_io\_tcp\_connect函数调用connect函数会失败，并且产生标准错误码22。
+
+如果使用格式如“iscsiadm -m node -p fe80::xxxx%enp3s0 -l”登录时，iscsi\_addr\_match函数会将地址“fe80::xxxx%enp3s0”与服务端返回的node信息中的地址“fe80::xxxx”对比，对比结果不匹配，导致登录失败。
+
+因此，**iscsi-initiator-utils目前机制还不支持用链路本地地址（link-local address）登录iscsi服务端**。
+
+#### 网卡down掉之后，IPv6地址丢失
+
+##### 问题现象
+
+通过ip link down+up网卡或ifconfig down+up网卡命令，将网卡down掉之后再上线，查看网卡上配置的ip地址，发现ipv4地址不丢失，而配置的IPv6地址丢失。
+
+##### 原因分析
+
+内核中的处理逻辑为如果网卡设置为down状态，会清空所有IPv4及IPv6地址，将网卡重新up之后，ipv4地址自动恢复，网卡上自动配置的IPv6链路本地地址也会恢复，但是其他IPv6地址默认会丢失。如果需要保留这些IPv6地址，可以通过“sysctl -w net.ipv6.conf.<网卡名\>.keep\_addr\_on\_down=1”来实现。
+
+#### bond口已具有多个IPv6地址时，添加或删除IPv6地址耗时过久
+
+##### 问题现象
+
+下列方式配置或删除（包括flush）IPv6地址方式，X为动态变化的低16位，并且配置在bond口时，耗时会随已配置的IPv6地址数量成数倍增加。例如由4个物理网卡组成的bond口添加IPv6地址时，单线程添加删除3000 IPv6地址均需大概5分钟，而普通物理网卡耗时在10秒内。
+
+```
+ip a add/del 192:168::18:X/64 dev DEVICE
+```
+
+##### 原因分析
+
+bond口在添加IPv6地址时，会生成IPv6组播地址，并进行同步到所有的物理网卡上，此耗时会随IPv6数量增加而增加，导致耗时过长。
+
+##### 解决方法
+
+IPv6的组播地址是由IPv6地址的低24位与33-33-ff组合生成，组播地址过多会导致添加删除耗时增加，如果生成的组播地址为少量，耗时不会受此影响。
+
+建议添加IPv6地址时，可保持低24位一致，保持高位变动，单网卡中仅需一个网段的一个地址即可与外部正常通信，此配置更符合常规使用。
+
+#### Rsyslog在IPv4和IPv6混合使用场景中日志传输延迟
+
+##### 问题现象
+
+rsyslog客户端配置文件同时配置IPv4和IPv6地址，且端口配置相同的情况下，服务端收集log时会概率性出现日志打印延迟。
+
+##### 原因分析
+
+延迟是因为rsyslog内部存在缓冲队列机制，默认情况下需要缓冲区队列达到一定数量才会写入文件。
+
+##### 解决方法
+
+可在root权限下通过配置Direct模式，关闭缓冲队列机制解决该问题。在rsyslog远程传输服务端的/etc/rsyslog.d目录下新增的远程传输配置文件中，最开头增加如下配置：
+
+```
+$ActionQueueType Direct
+$MainMsgQueueType Direct
+```
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>-   Direct模式减少队列大小为1，所以在队列中会保留1条日志到下次日志打印；  
+>-   Direct模式会降低服务器端的rsyslog性能。  
diff --git a/content/zh/docs/ApplicationDev/application-development.md b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/application-development.md
similarity index 95%
rename from content/zh/docs/ApplicationDev/application-development.md
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/application-development.md
index 21d1513b77eeacb2a4fe6da5049bb2796fe4fb2c..979200523d58f11d2907ae3b5c83efbb4d7bb89d 100644
--- a/content/zh/docs/ApplicationDev/application-development.md
+++ b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/application-development.md
@@ -29,13 +29,13 @@
 
 
 
-

+
![](./figures/en-us_image_0229243712.png）

 
 
用于传递设备或环境安全警示信息，若不避免，可能会导致设备损坏、数据丢失、设备性能降低或其它不可预知的结果。

 
“注意”不涉及人身伤害。

 
 
-

+
![](./figures/en-us_image_0229243671.png）

 
 
用于突出重要/关键信息、最佳实践和小窍门等。

 
“说明”不是安全警示信息，不涉及人身、设备及环境伤害。

@@ -80,7 +80,7 @@
 
表示从两个或多个选项中选取一个或者不选。

 
 
-
{ x | y | ... }*

+
{ x | y | ... }\*

 
 
表示从两个或多个选项中选取多个，最少选取一个，最多选取所有选项。

 
diff --git "a/content/zh/docs/ApplicationDev/figures/Add-file\351\241\265\351\235\242.png" b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/add-file-page.png
similarity index 100%
rename from "content/zh/docs/ApplicationDev/figures/Add-file\351\241\265\351\235\242.png"
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/add-file-page.png
diff --git "a/content/zh/docs/ApplicationDev/figures/Branch-Confirmation\351\241\265\351\235\242.png" b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/branch-confirmation-page.png
similarity index 100%
rename from "content/zh/docs/ApplicationDev/figures/Branch-Confirmation\351\241\265\351\235\242.png"
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/branch-confirmation-page.png
diff --git "a/content/zh/docs/ApplicationDev/figures/Create-Package\351\241\265\351\235\242.png" b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/create-package-page.png
similarity index 100%
rename from "content/zh/docs/ApplicationDev/figures/Create-Package\351\241\265\351\235\242.png"
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/create-package-page.png
diff --git "a/content/zh/docs/ApplicationDev/figures/\345\210\233\345\273\272\350\275\257\344\273\266\345\214\205\344\277\241\346\201\257\345\241\253\345\206\231\351\241\265\351\235\242.png" b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/creating-a-software-package.png
similarity index 100%
rename from "content/zh/docs/ApplicationDev/figures/\345\210\233\345\273\272\350\275\257\344\273\266\345\214\205\344\277\241\346\201\257\345\241\253\345\206\231\351\241\265\351\235\242.png"
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/creating-a-software-package.png
diff --git "a/content/zh/docs/ApplicationDev/figures/\345\210\240\351\231\244\345\255\220\345\267\245\347\250\213\344\270\255\350\275\257\344\273\266\345\214\205.png" b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/deleting-a-software-package-from-a-subproject.png
similarity index 100%
rename from "content/zh/docs/ApplicationDev/figures/\345\210\240\351\231\244\345\255\220\345\267\245\347\250\213\344\270\255\350\275\257\344\273\266\345\214\205.png"
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/deleting-a-software-package-from-a-subproject.png
diff --git "a/content/zh/docs/ApplicationDev/figures/Repositories\351\241\265\351\235\242.png" b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/repositories-page.png
similarity index 100%
rename from "content/zh/docs/ApplicationDev/figures/Repositories\351\241\265\351\235\242.png"
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/repositories-page.png
diff --git "a/content/zh/docs/ApplicationDev/figures/RPM\350\275\257\344\273\266\345\214\205\344\270\213\350\275\275\351\241\265\351\235\242.png" b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/rpm-software-package-download-page.png
similarity index 100%
rename from "content/zh/docs/ApplicationDev/figures/RPM\350\275\257\344\273\266\345\214\205\344\270\213\350\275\275\351\241\265\351\235\242.png"
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/rpm-software-package-download-page.png
diff --git "a/content/zh/docs/ApplicationDev/figures/succeeded\347\232\204\351\241\265\351\235\242.png" b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/succeeded-page.png
similarity index 100%
rename from "content/zh/docs/ApplicationDev/figures/succeeded\347\232\204\351\241\265\351\235\242.png"
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/succeeded-page.png
diff --git a/content/zh/docs/ApplicationDev/figures/zh-cn_image_0229243671.png b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/zh-cn_image_0229243671.png
similarity index 100%
rename from content/zh/docs/ApplicationDev/figures/zh-cn_image_0229243671.png
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/zh-cn_image_0229243671.png
diff --git a/content/zh/docs/ApplicationDev/figures/zh-cn_image_0229243702.png b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/zh-cn_image_0229243702.png
similarity index 100%
rename from content/zh/docs/ApplicationDev/figures/zh-cn_image_0229243702.png
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/zh-cn_image_0229243702.png
diff --git a/content/zh/docs/ApplicationDev/figures/zh-cn_image_0229243704.png b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/zh-cn_image_0229243704.png
similarity index 100%
rename from content/zh/docs/ApplicationDev/figures/zh-cn_image_0229243704.png
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/zh-cn_image_0229243704.png
diff --git a/content/zh/docs/ApplicationDev/figures/zh-cn_image_0229243712.png b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/zh-cn_image_0229243712.png
similarity index 100%
rename from content/zh/docs/ApplicationDev/figures/zh-cn_image_0229243712.png
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/figures/zh-cn_image_0229243712.png
diff --git a/content/zh/docs/ApplicationDev/public_sys-resources/icon-caution.gif b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-caution.gif
similarity index 100%
rename from content/zh/docs/ApplicationDev/public_sys-resources/icon-caution.gif
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-caution.gif
diff --git a/content/zh/docs/ApplicationDev/public_sys-resources/icon-danger.gif b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-danger.gif
similarity index 100%
rename from content/zh/docs/ApplicationDev/public_sys-resources/icon-danger.gif
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-danger.gif
diff --git a/content/zh/docs/ApplicationDev/public_sys-resources/icon-note.gif b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-note.gif
similarity index 100%
rename from content/zh/docs/ApplicationDev/public_sys-resources/icon-note.gif
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-note.gif
diff --git a/content/zh/docs/ApplicationDev/public_sys-resources/icon-notice.gif b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-notice.gif
similarity index 100%
rename from content/zh/docs/ApplicationDev/public_sys-resources/icon-notice.gif
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-notice.gif
diff --git a/content/zh/docs/ApplicationDev/public_sys-resources/icon-tip.gif b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-tip.gif
similarity index 100%
rename from content/zh/docs/ApplicationDev/public_sys-resources/icon-tip.gif
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-tip.gif
diff --git a/content/zh/docs/ApplicationDev/public_sys-resources/icon-warning.gif b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-warning.gif
similarity index 100%
rename from content/zh/docs/ApplicationDev/public_sys-resources/icon-warning.gif
rename to docs/zh/docs/20.03_LTS/docs/ApplicationDev/public_sys-resources/icon-warning.gif
diff --git "a/content/zh/docs/ApplicationDev/\344\275\277\347\224\250GCC\347\274\226\350\257\221.md" "b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/\344\275\277\347\224\250GCC\347\274\226\350\257\221.md"
similarity index 99%
rename from "content/zh/docs/ApplicationDev/\344\275\277\347\224\250GCC\347\274\226\350\257\221.md"
rename to "docs/zh/docs/20.03_LTS/docs/ApplicationDev/\344\275\277\347\224\250GCC\347\274\226\350\257\221.md"
index 6a987cb35038cf518d4e999e0a4a6844171d61a6..994fdee00a8f058f7b5a3efef701601573f456a7 100644
--- "a/content/zh/docs/ApplicationDev/\344\275\277\347\224\250GCC\347\274\226\350\257\221.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/\344\275\277\347\224\250GCC\347\274\226\350\257\221.md"
@@ -311,7 +311,7 @@ $ gcc main.c libtest.so -o app.out
 
     $ export LD\_LIBRARY\_PATH=libraryDIR:$LD\_LIBRARY\_PATH
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >LD\_LIBRARY\_PATH为动态库的环境变量。当运行动态库时，若动态库不在缺省文件夹（/lib 和/usr/lib）下，则需要指定环境变量LD\_LIBRARY\_PATH。  
 
 -   把动态库所在路径libaryDIR增加 /etc/ld.so.conf中然后执行ldconfig或者以动态库所在路径libaryDIR为参数执行ldconfig。
diff --git "a/content/zh/docs/ApplicationDev/\344\275\277\347\224\250JDK\347\274\226\350\257\221.md" "b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/\344\275\277\347\224\250JDK\347\274\226\350\257\221.md"
similarity index 100%
rename from "content/zh/docs/ApplicationDev/\344\275\277\347\224\250JDK\347\274\226\350\257\221.md"
rename to "docs/zh/docs/20.03_LTS/docs/ApplicationDev/\344\275\277\347\224\250JDK\347\274\226\350\257\221.md"
diff --git "a/content/zh/docs/ApplicationDev/\344\275\277\347\224\250make\347\274\226\350\257\221.md" "b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/\344\275\277\347\224\250make\347\274\226\350\257\221.md"
similarity index 100%
rename from "content/zh/docs/ApplicationDev/\344\275\277\347\224\250make\347\274\226\350\257\221.md"
rename to "docs/zh/docs/20.03_LTS/docs/ApplicationDev/\344\275\277\347\224\250make\347\274\226\350\257\221.md"
diff --git "a/content/zh/docs/ApplicationDev/\345\274\200\345\217\221\347\216\257\345\242\203\345\207\206\345\244\207.md" "b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/\345\274\200\345\217\221\347\216\257\345\242\203\345\207\206\345\244\207.md"
similarity index 88%
rename from "content/zh/docs/ApplicationDev/\345\274\200\345\217\221\347\216\257\345\242\203\345\207\206\345\244\207.md"
rename to "docs/zh/docs/20.03_LTS/docs/ApplicationDev/\345\274\200\345\217\221\347\216\257\345\242\203\345\207\206\345\244\207.md"
index a08946a37e886d5c20ac895c0020585773ea8fd4..4bd20dd7b6a3241d115380f19330e28167146631 100644
--- "a/content/zh/docs/ApplicationDev/\345\274\200\345\217\221\347\216\257\345\242\203\345\207\206\345\244\207.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/\345\274\200\345\217\221\347\216\257\345\242\203\345\207\206\345\244\207.md"
@@ -58,7 +58,7 @@
     
     
硬盘

     
-    
为了获得更好的应用体验，建议不小于120GB）

+    
为了获得更好的应用体验，建议不小于120GB

     
     
支持IDE、SATA、SAS等接口的硬盘。

     
@@ -115,7 +115,7 @@
 
 操作系统要求为openEuler操作系统。
 
-openEuler操作系统具体安装方法请参考[openEuler 20.09 安装指南]({{< relref "../Installation/Installation.md" >}})，其中“软件选择”页面的“已选环境的附加选项”中将“开发工具”勾选。
+openEuler操作系统具体安装方法请参考[openEuler 20.03 LTS 安装指南](./../Installation/Installation.md)，其中“软件选择”页面的“已选环境的附加选项”中将“开发工具”勾选。
 
 ## 配置openEuler yum源（软件源）
 
@@ -123,39 +123,42 @@ openEuler操作系统具体安装方法请参考[openEuler 20.09 安装指南]({
 
 ### 通过直接获取在线的openEuler repo源配置在线yum源
 
->![](public_sys-resources/icon-note.gif) **说明：**   
->openEuler提供了多种repo源供用户在线使用，各repo源含义可参考[系统安装]({{< relref "../Releasenotes/系统安装.md" >}})。本操作以AArch64架构的OS repo源为例将其配置为yum源。
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>openEuler提供了多种repo源供用户在线使用，各repo源含义可参考[系统安装](./../Releasenotes/系统安装.md)。本操作以AArch64架构的OS repo源为例将其配置为yum源。
 
 1.  进入到yum源目录并查看目录下的.repo配置文件。
 
     ```
     $ cd /etc/yum.repos.d
 	$ ls
-	openEuler.repo
+	openEuler_aarch64.repo
     ```
 
-2.  在root权限下编辑openEuler.repo文件，将在线的openEuler repo源配置为yum源。
+2.  在root权限下编辑openEuler_aarch64.repo文件，将在线的openEuler repo源配置为yum源。
 
     ```
-    # vi openEuler.repo
+    # vi openEuler_aarch64.repo
     ```
 
-    编辑openEuler.repo文件的内容如下：
+    编辑openEuler_aarch64.repo文件的内容如下：
 	
 	
 	```
     [osrepo]
+
     name=osrepo
-    baseurl=http://repo.openeuler.org/openEuler-20.09/OS/aarch64/
+
+    baseurl=http://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/
+
     enabled=1
 
     gpgcheck=1
-    gpgkey=http://repo.openeuler.org/openEuler-20.09/OS/aarch64/RPM-GPG-KEY-openEuler
+	gpgkey=http://repo.openeuler.org/openEuler-20.03-LTS/OS/aarch64/RPM-GPG-KEY-openEuler
 	```
 
     ****
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
 	> - \[*repoid*\]中的repoid为软件仓库（repository）的ID号，所有.repo配置文件中的各repoid不能重复，必须唯一。示例中repoid设置为**osrepo**。	
 	> - name为软件仓库描述的字符串。	
 	> - baseurl为软件仓库的地址。	
@@ -165,23 +168,23 @@ openEuler操作系统具体安装方法请参考[openEuler 20.09 安装指南]({
 
 ### 通过挂载ISO创建本地openEuler repo源配置本地yum源
 
->![](public_sys-resources/icon-note.gif) **说明：**   
->openEuler提供了多种ISO发布包，各ISO发布包含义可参考[系统安装]({{< relref "../Releasenotes/系统安装.md" >}})。本操作以openEuler-20.09-aarch64-dvd.iso发布包和openEuler-20.09-aarch64-dvd.iso.sha256sum校验文件为例，请根据实际需要的ISO发布包和校验文件进行修改。  
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>openEuler提供了多种ISO发布包，各ISO发布包含义可参考[系统安装](./../Releasenotes/系统安装.md)。本操作以openEuler-20.03-LTS-aarch64-dvd.iso发布包和openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum校验文件为例，请根据实际需要的ISO发布包和校验文件进行修改。  
 
 1.  下载ISO发布包。
     -   通过跨平台文件传输工具下载ISO镜像
         1.  登录openEuler社区，网址为：[https://openeuler.org](https://openeuler.org)。
         2.  单击“下载”，进入下载页面。
         3.  单击“获取ISO：”后面的“Link”，显示版本列表。
-        4.  选择需要下载的版本，如openEuler 20.09，则单击“openEuler-20.09”，进入下载列表。
+        4.  选择需要下载的版本，如openEuler 20.03 LTS，则单击“openEuler-20.03-LTS”，进入下载列表。
         5.  单击“ISO”，进入ISO下载列表。
             -   aarch64：AArch64架构的ISO。
             -   x86\_64：x86\_64架构的ISO。
             -   source：openEuler源码ISO。
 
         6.  单击“aarch64”。
-        7.  单击“openEuler-20.09-aarch64-dvd.iso”，将openEuler发布包下载到本地。
-        8.  单击“openEuler-20.09-aarch64-dvd.iso.sha256sum”，将openEuler校验文件下载到本地。
+        7.  单击“openEuler-20.03-LTS-aarch64-dvd.iso”，将openEuler发布包下载到本地。
+        8.  单击“openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum”，将openEuler校验文件下载到本地。
         9.  登录openEuler操作系统，新建用于存放发布包和检验文件的目录,如“~/iso”。
 
             ```
@@ -194,15 +197,15 @@ openEuler操作系统具体安装方法请参考[openEuler 20.09 安装指南]({
         1.  登录openEuler社区，网址为：[https://openeuler.org](https://openeuler.org)。
         2.  单击“下载”，进入下载页面。
         3.  单击“获取ISO：”后面的“Link”，显示版本列表。
-        4.  选择需要下载的版本，如openEuler 20.03 LTS，则单击“openEuler-20.09”，进入下载列表。
+        4.  选择需要下载的版本，如openEuler 20.03 LTS，则单击“openEuler-20.03-LTS”，进入下载列表。
         5.  单击“ISO”，进入ISO下载列表。
             -   aarch64：AArch64架构的ISO。
             -   x86\_64：x86\_64架构的ISO。
             -   source：openEuler源码ISO。
 
         6.  单击“aarch64”。
-        7.  右键单击“openEuler-20.09-aarch64-dvd.iso”，单击“复制链接地址”，将openEuler发布包地址记录好。
-        8.  右键单击“openEuler-20.09-aarch64-dvd.iso.sha256sum”，单击“复制链接地址”，将openEuler校验文件地址记录好。
+        7.  右键单击“openEuler-20.03-LTS-aarch64-dvd.iso”，单击“复制链接地址”，将openEuler发布包地址记录好。
+        8.  右键单击“openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum”，单击“复制链接地址”，将openEuler校验文件地址记录好。
         9.  登录openEuler操作系统，新建用于存放发布包和检验文件的目录,如“~/iso”，并切换到该目录。
 
             ```
@@ -222,13 +225,13 @@ openEuler操作系统具体安装方法请参考[openEuler 20.09 安装指南]({
     1.  获取校验文件中的校验值。
 
         ```
-        $ cat openEuler-20.09-aarch64-dvd.iso.sha256sum
+        $ cat openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum
         ```
 
     2.  计算openEuler发布包的sha256校验值。
 
         ```
-        $ sha256sum openEuler-20.09-aarch64-dvd.iso 
+        $ sha256sum openEuler-20.03-LTS-aarch64-dvd.iso 
         ```
 
         命令执行完成后，输出校验值。
@@ -244,7 +247,7 @@ openEuler操作系统具体安装方法请参考[openEuler 20.09 安装指南]({
     示例如下：
 
     ```
-    # mount /home/iso/openEuler-20.09-aarch64-dvd.iso /mnt/
+    # mount /home/iso/openEuler-20.03-LTS-aarch64-dvd.iso /mnt/
     ```
 
     挂载好的mnt目录如下：
@@ -268,25 +271,29 @@ openEuler操作系统具体安装方法请参考[openEuler 20.09 安装指南]({
     ```
     $ cd /etc/yum.repos.d
 	$ ls
-	openEuler.repo
+	openEuler_aarch64.repo
     ```
 
-2.  在root权限下编辑openEuler.repo文件，将[3](#li6236932222)中创建的repo源配置为本地yum源。
+2.  在root权限下编辑openEuler_aarch64.repo文件，将[3](#li6236932222)中创建的repo源配置为本地yum源。
 
     ```
-    # vi openEuler.repo
+    # vi openEuler_aarch64.repo
     ```
 
-    编辑openEuler.repo文件的内容如下：
+    编辑openEuler_aarch64.repo文件的内容如下：
 
     ```
-    [localosrepo]
+	[localosrepo]
+
     name=localosrepo
+
     baseurl=file:///mnt
+
     enabled=1
+
     gpgcheck=1
-    gpgkey=file:///mnt/RPM-GPG-KEY-openEuler
-    ```
+	gpgkey=file:///mnt/RPM-GPG-KEY-openEuler
+	```
 
 
 
diff --git "a/content/zh/docs/ApplicationDev/\346\236\204\345\273\272RPM\345\214\205.md" "b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/\346\236\204\345\273\272RPM\345\214\205.md"
similarity index 97%
rename from "content/zh/docs/ApplicationDev/\346\236\204\345\273\272RPM\345\214\205.md"
rename to "docs/zh/docs/20.03_LTS/docs/ApplicationDev/\346\236\204\345\273\272RPM\345\214\205.md"
index e8251e05948a8ccce8c978014fc84e26a71ca12c..0622edf569a26838ec2d12b824ded555d27ad9ea 100644
--- "a/content/zh/docs/ApplicationDev/\346\236\204\345\273\272RPM\345\214\205.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/ApplicationDev/\346\236\204\345\273\272RPM\345\214\205.md"
@@ -510,7 +510,7 @@ OBS使用工程组织软件包。基础的权限控制、相关的存仓库和
 
 #### 构建已有软件包
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >-   若为首次使用，请首先在OBS网页注册个人账号。  
 >-   该方法需要拷贝修改后的代码，因此，请在执行下述操作前完成代码修改并提交到正确的代码路径。代码路径会在\_service文件中指定。  
 
@@ -523,7 +523,7 @@ OBS使用工程组织软件包。基础的权限控制、相关的存仓库和
 5.  单击“Branch package”，在弹出的确认页面单击“Accept”确认创建子工程，如[图1](#fig77646143214)所示。
 
     **图 1**  Branch Confirmation页面  
-    ![](figures/Branch-Confirmation页面.png "Branch-Confirmation页面")
+    ![](./figures/branch-confirmation-page.png)
 
 6.  单击“\_service”文件进入编辑页面，修改\_service内容后点击“Save”保存该文件。\_service内容示例如下，其中 _userCodeURL_、 _userCommitID_ 分别为用户代码托管路径、用户代码提交版本号或分支。
 
@@ -541,14 +541,14 @@ OBS使用工程组织软件包。基础的权限控制、相关的存仓库和
     
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >单击“Save”保存\_service文件后，OBS服务会根据\_service文件描述，从指定的url下载源码到OBS对应工程的软件目录下并替换原有文件，例如上述例子中 “openEuler:Mainline”工程的kernel目录。  
 
 7.  文件拷贝并替换完成后，OBS会自动开始构建RPM软件包。等待构建完成，并查看右侧状态栏的构建状态。
     -   succeeded：构建成功。用户可以单击“succeeded”查看构建日志，如[图2](#fig10319114217337)所示。
 
         **图 2**  succeeded的页面  
-        ![](figures/succeeded的页面.png "succeeded的页面")
+        ![](./figures/succeeded-page.png)
 
     -   failed：构建失败。请单击“failed”查看错误日志进行问题定位后重新构建。
     -   unresolvable：未进行构建，可能由于缺失依赖。
@@ -567,23 +567,23 @@ OBS使用工程组织软件包。基础的权限控制、相关的存仓库和
 5.  单击“Delete package”，删除新创建子工程中的软件包，如[图3](#fig18306181103615)所示。
 
     **图 3**  删除子工程中软件包  
-    ![](figures/删除子工程中软件包.png "删除子工程中软件包")
+    ![](./figures/deleting-a-software-package-from-a-subproject.png)
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >通过已有软件创建新工程是为了继承环境等依赖，而不需要实际的文件，所以这里需要把这些文件删除。  
 
 6.  单击“Create Package”，在弹出的页面输入软件包名称、标题和软件包描述，然后单击“Create”创建软件包，分别如[图4](#fig6762111693811)、[图5](#fig18351153518389)所示。
 
     **图 4**  Create Package页面  
-    ![](figures/Create-Package页面.png "Create-Package页面")
+    ![](./figures/create-package-page.png)
 
     **图 5**  创建软件包信息填写页面  
-    ![](figures/创建软件包信息填写页面.png "创建软件包信息填写页面")
+    ![](./figures/creating-a-software-package.png)
 
 7.  在页面中单击“Add file”上传spec文件和需要编译的文件（在spec文件中指定），如[图6](#fig1475845284011)所示。
 
     **图 6**  Add file页面  
-    ![](figures/Add-file页面.png "Add-file页面")
+    ![](./figures/add-file-page.png)
 
 8.  文件上传成功后，OBS会自动开始构建RPM软件包。等待构建完成，并查看右侧状态栏的构建状态。
     -   succeed：构建成功。用户可以单击“succeeded”查看构建日志。
@@ -601,15 +601,15 @@ RPM软件包构建完成后，通过网页端获取对应RPM软件包的方法
 2.  单击“All Projects”找到所需软件包的对应工程，例如“openEuler:Mainline”。
 3.  在工程下单击所需软件包的包名，进入该软件包详请页面。例如上述例子中的kernel页面。
 
-1.  选择Repositories页签进入软件包的软件仓库管理页面，在Publish Flag中通过单击选择“Enable”开启（状态由![](figures/zh-cn_image_0229243704.png)变为![](figures/zh-cn_image_0229243702.png)）对应的RPM软件包下载功能，如[图7](#fig17480830144217)所示。
+1.  选择Repositories页签进入软件包的软件仓库管理页面，在Publish Flag中通过单击选择“Enable”开启（状态由![](./figures/zh-cn_image_0229243704.png)变为![](./figures/zh-cn_image_0229243702.png)）对应的RPM软件包下载功能，如[图7](#fig17480830144217)所示。
 
     **图 7**  Repositories页面  
-    ![](figures/Repositories页面.png "Repositories页面")
+    ![](./figures/repositories-page.png)
 
 2.  单击Repository列的构建工程名称，进入RPM软件包下载页面，单击RPM软件包右侧的“Download”即可下载对应RPM软件包，如[图8](#fig12152145615438)所示。
 
     **图 8**  RPM软件包下载页面  
-    ![](figures/RPM软件包下载页面.png "RPM软件包下载页面")
+    ![](./figures/rpm-software-package-download-page.png)
 
 
 ### 使用osc构建软件包
@@ -630,7 +630,7 @@ RPM软件包构建完成后，通过网页端获取对应RPM软件包的方法
     # dnf install osc build
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >编译RPM软件包的过程中会依赖build。  
 
 2.  配置osc。
@@ -729,7 +729,7 @@ RPM软件包构建完成后，通过网页端获取对应RPM软件包的方法
     $ osc buildlog standard_aarch64  aarch64
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >用户也可以通过网页端打开自己创建的对应工程，查看构建日志。  
 
 
@@ -785,7 +785,7 @@ RPM软件包构建完成后，通过网页端获取对应RPM软件包的方法
     $ osc buildlog standard_aarch64  aarch64
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >用户也可以通过网页端打开自己创建的对应工程，查看构建日志。  
 
 
@@ -804,5 +804,5 @@ $ osc getbinaries home:testUser:branches:openEuler:Mainline my-first-obs-package
 -   _standard\_aarch64_  ：仓库名称
 -   _aarch64_  ：仓库架构名称
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >使用osc构建的软件包也可以在网页端获取，获取方式请参见[获取软件包](#获取软件包)。  
diff --git "a/content/zh/docs/Container/CRI\346\216\245\345\217\243.md" "b/docs/zh/docs/20.03_LTS/docs/Container/CRI\346\216\245\345\217\243.md"
similarity index 99%
rename from "content/zh/docs/Container/CRI\346\216\245\345\217\243.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/CRI\346\216\245\345\217\243.md"
index 26b0321a4da95e83bf5b7b2e65d1c5fe10280ab4..9283ab8500c01ef0312d500da2a11632f9575ec3 100644
--- "a/content/zh/docs/Container/CRI\346\216\245\345\217\243.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/CRI\346\216\245\345\217\243.md"
@@ -45,7 +45,7 @@ CRI API 接口是由kubernetes 推出的容器运行时接口，CRI定义了容
 
 ISulad使用的为pass使用的1.14版本API描述文件，与官方API略有出入，以本文档描述的接口为准。
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >CRI接口websocket流式服务，服务端侦听地址为127.0.0.1，端口为10350，端口可通过命令行--websocket-server-listening-port参数接口或者daemon.json配置文件进行配置。  
 
 ## 接口
diff --git "a/content/zh/docs/Container/Docker\345\256\271\345\231\250.md" "b/docs/zh/docs/20.03_LTS/docs/Container/Docker\345\256\271\345\231\250.md"
similarity index 91%
rename from "content/zh/docs/Container/Docker\345\256\271\345\231\250.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/Docker\345\256\271\345\231\250.md"
index c6d46c4ffb1d9f71dd6be3be7947412bfcd0d66b..07b0b5833155d630566cd03b73f66148baea5e73 100644
--- "a/content/zh/docs/Container/Docker\345\256\271\345\231\250.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/Docker\345\256\271\345\231\250.md"
@@ -1,9 +1,9 @@
-# Docker容器
-
-Docker是一个开源的Linux容器引擎项目， 用以实现应用的快速打包、部署和交付。Docker的英文本意是码头工人，码头工人的工作就是将商品打包到container\(集装箱\)并且搬运container、装载container。 对应到Linux中，Docker就是将app打包到container，通过container实现app在各种平台上的部署、运行。Docker通过Linux Container技术将app变成一个标准化的、可移植的、自管理的组件，从而实现应用的“一次构建，到处运行”。Docker技术特点就是：应用快速发布、部署简单、管理方便，应用密度更高。
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->Docker容器的安装和使用需要root权限。
-
-
-
+# Docker容器
+
+Docker是一个开源的Linux容器引擎项目， 用以实现应用的快速打包、部署和交付。Docker的英文本意是码头工人，码头工人的工作就是将商品打包到container\(集装箱\)并且搬运container、装载container。 对应到Linux中，Docker就是将app打包到container，通过container实现app在各种平台上的部署、运行。Docker通过Linux Container技术将app变成一个标准化的、可移植的、自管理的组件，从而实现应用的“一次构建，到处运行”。Docker技术特点就是：应用快速发布、部署简单、管理方便，应用密度更高。
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>Docker容器的安装和使用需要root权限。
+
+
+
diff --git "a/content/zh/docs/Container/cgroup\350\267\257\345\276\204\345\217\257\351\205\215\347\275\256.md" "b/docs/zh/docs/20.03_LTS/docs/Container/cgroup\350\267\257\345\276\204\345\217\257\351\205\215\347\275\256.md"
similarity index 99%
rename from "content/zh/docs/Container/cgroup\350\267\257\345\276\204\345\217\257\351\205\215\347\275\256.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/cgroup\350\267\257\345\276\204\345\217\257\351\205\215\347\275\256.md"
index 97bc19b7ff48e23587c93512b5dffc8391cc1d67..d737c0cd97db19684ae5821a30045bc5e51ef071 100644
--- "a/content/zh/docs/Container/cgroup\350\267\257\345\276\204\345\217\257\351\205\215\347\275\256.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/cgroup\350\267\257\345\276\204\345\217\257\351\205\215\347\275\256.md"
@@ -1,11 +1,11 @@
-# cgroup路径可配置
-## 功能描述
-
-系统容器提供在宿主机上进行容器资源隔离和预留的能力。通过\--cgroup-parent参数，可以将容器使用的cgroup目录指定到某个特定目录下，从而达到灵活分配宿主机资源的目的。例如可以设置容器a、b、c的cgroup父路径为/lxc/cgroup1，容器d、e、f的cgroup父路径为/lxc/cgroup2，这样通过cgroup路径将容器分为两个group，实现容器cgroup组层面的资源隔离。
-
-## 参数说明
-
-
+# cgroup路径可配置
+## 功能描述
+
+系统容器提供在宿主机上进行容器资源隔离和预留的能力。通过\--cgroup-parent参数，可以将容器使用的cgroup目录指定到某个特定目录下，从而达到灵活分配宿主机资源的目的。例如可以设置容器a、b、c的cgroup父路径为/lxc/cgroup1，容器d、e、f的cgroup父路径为/lxc/cgroup2，这样通过cgroup路径将容器分为两个group，实现容器cgroup组层面的资源隔离。
+
+## 参数说明
+
+
 
-
命令

 		
 
参数

@@ -22,11 +22,11 @@
 
 

 

-
-除了通过命令行指定单个系统容器对应的cgroup父路径外，还可通过修改iSulad容器引擎启动配置文件，指定所有容器的cgroup路径。
-
-
+
+
+除了通过命令行指定单个系统容器对应的cgroup父路径外，还可通过修改iSulad容器引擎启动配置文件，指定所有容器的cgroup路径。
+
+
 
-
配置文件路径

 		
 
配置项

@@ -43,53 +43,53 @@
 
 

 

-
-## 约束限制
-
--   如果daemon端和客户端都设置了cgroup parent参数，最终以客户端指定的\--cgroup-parent生效。
--   如果已启动容器A，然后启动容器B，容器B的cgroup父路径指定为容器A的cgroup路径，在删除容器的时候需要先删除容器B再删除容器A，否则会导致cgroup资源残留。
-
-## 使用示例
-
-启动系统容器，指定--cgroup-parent参数：
-
-```
-[root@localhost ~]# isula run -tid --cgroup-parent /lxc/cgroup123 --system-container --external-rootfs /root/myrootfs none init
-115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
-```
-
-查看容器init进程的cgroup信息：
-
-```
-[root@localhost ~]# isula inspect -f "{{json .State.Pid}}" 11
-22167
-[root@localhost ~]# cat /proc/22167/cgroup
-13:blkio:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
-12:perf_event:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
-11:cpuset:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
-10:pids:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
-9:rdma:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
-8:devices:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
-7:hugetlb:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
-6:memory:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
-5:net_cls,net_prio:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
-4:cpu,cpuacct:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
-3:files:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
-2:freezer:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
-1:name=systemd:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e/init.scope
-0::/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
-```
-
-可以看到容器的cgroup父路径被设置为/sys/fs/cgroup//lxc/cgroup123
-
-同时，对于所有容器cgroup父路径的设置可以配置一下容器daemon文件，例如：
-
-```
-{
-         "cgroup-parent": "/lxc/cgroup123",
-}
-```
-
-然后重启容器引擎，配置生效。
-
+
+
+## 约束限制
+
+-   如果daemon端和客户端都设置了cgroup parent参数，最终以客户端指定的\--cgroup-parent生效。
+-   如果已启动容器A，然后启动容器B，容器B的cgroup父路径指定为容器A的cgroup路径，在删除容器的时候需要先删除容器B再删除容器A，否则会导致cgroup资源残留。
+
+## 使用示例
+
+启动系统容器，指定--cgroup-parent参数：
+
+```
+[root@localhost ~]# isula run -tid --cgroup-parent /lxc/cgroup123 --system-container --external-rootfs /root/myrootfs none init
+115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
+```
+
+查看容器init进程的cgroup信息：
+
+```
+[root@localhost ~]# isula inspect -f "{{json .State.Pid}}" 11
+22167
+[root@localhost ~]# cat /proc/22167/cgroup
+13:blkio:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
+12:perf_event:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
+11:cpuset:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
+10:pids:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
+9:rdma:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
+8:devices:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
+7:hugetlb:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
+6:memory:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
+5:net_cls,net_prio:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
+4:cpu,cpuacct:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
+3:files:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
+2:freezer:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
+1:name=systemd:/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e/init.scope
+0::/lxc/cgroup123/115878a4dfc7c5b8c62ef8a4b44f216485422be9a28f447a4b9ecac4609f332e
+```
+
+可以看到容器的cgroup父路径被设置为/sys/fs/cgroup//lxc/cgroup123
+
+同时，对于所有容器cgroup父路径的设置可以配置一下容器daemon文件，例如：
+
+```
+{
+         "cgroup-parent": "/lxc/cgroup123",
+}
+```
+
+然后重启容器引擎，配置生效。
+
diff --git a/content/zh/docs/Container/container.md b/docs/zh/docs/20.03_LTS/docs/Container/container.md
similarity index 97%
rename from content/zh/docs/Container/container.md
rename to docs/zh/docs/20.03_LTS/docs/Container/container.md
index 72e34041ee1ac1eeebcdb11b258e6d5dac3d27f6..c86353b2a248e0fa2233e64b712164bc2c68c82a 100644
--- a/content/zh/docs/Container/container.md
+++ b/docs/zh/docs/20.03_LTS/docs/Container/container.md
@@ -1,18 +1,18 @@
-## 概述
-
-openEuler软件包中同时提供了轻量化容器引擎iSulad与docker engine两种容器引擎。
-
-同时根据不同使用场景，提供多种容器形态，包括：
-
--   适合大部分通用场景的普通容器
--   适合强隔离与多租户场景的安全容器
--   适合使用systemd管理容器内业务场景的系统容器
-
-本文档提供容器引擎的安装和使用方法以及各个容器形态的部署使用方法。
-
-## 读者对象
-
-本文档主要适用于使用openEuler并需要安装容器的用户。用户需要具备以下经验和技能：
-
--   熟悉Linux基本操作
+## 概述
+
+openEuler软件包中同时提供了轻量化容器引擎iSulad与docker engine两种容器引擎。
+
+同时根据不同使用场景，提供多种容器形态，包括：
+
+-   适合大部分通用场景的普通容器
+-   适合强隔离与多租户场景的安全容器
+-   适合使用systemd管理容器内业务场景的系统容器
+
+本文档提供容器引擎的安装和使用方法以及各个容器形态的部署使用方法。
+
+## 读者对象
+
+本文档主要适用于使用openEuler并需要安装容器的用户。用户需要具备以下经验和技能：
+
+-   熟悉Linux基本操作
 -   对容器有一定了解
\ No newline at end of file
diff --git a/content/zh/docs/Container/figures/kata-arch.png b/docs/zh/docs/20.03_LTS/docs/Container/figures/kata-arch.png
similarity index 100%
rename from content/zh/docs/Container/figures/kata-arch.png
rename to docs/zh/docs/20.03_LTS/docs/Container/figures/kata-arch.png
diff --git "a/content/zh/docs/Container/figures/\345\256\211\345\205\250\345\256\271\345\231\250\344\270\216\345\221\250\350\276\271\347\273\204\344\273\266\347\232\204\345\205\263\347\263\273.png" b/docs/zh/docs/20.03_LTS/docs/Container/figures/sec-container.png
similarity index 100%
rename from "content/zh/docs/Container/figures/\345\256\211\345\205\250\345\256\271\345\231\250\344\270\216\345\221\250\350\276\271\347\273\204\344\273\266\347\232\204\345\205\263\347\263\273.png"
rename to docs/zh/docs/20.03_LTS/docs/Container/figures/sec-container.png
diff --git a/content/zh/docs/Container/figures/zh-cn_image_0183048952.png b/docs/zh/docs/20.03_LTS/docs/Container/figures/zh-cn_image_0183048952.png
similarity index 100%
rename from content/zh/docs/Container/figures/zh-cn_image_0183048952.png
rename to docs/zh/docs/20.03_LTS/docs/Container/figures/zh-cn_image_0183048952.png
diff --git a/content/zh/docs/Container/figures/zh-cn_image_0221924926.png b/docs/zh/docs/20.03_LTS/docs/Container/figures/zh-cn_image_0221924926.png
similarity index 100%
rename from content/zh/docs/Container/figures/zh-cn_image_0221924926.png
rename to docs/zh/docs/20.03_LTS/docs/Container/figures/zh-cn_image_0221924926.png
diff --git a/content/zh/docs/Container/figures/zh-cn_image_0221924927.png b/docs/zh/docs/20.03_LTS/docs/Container/figures/zh-cn_image_0221924927.png
similarity index 100%
rename from content/zh/docs/Container/figures/zh-cn_image_0221924927.png
rename to docs/zh/docs/20.03_LTS/docs/Container/figures/zh-cn_image_0221924927.png
diff --git "a/content/zh/docs/Container/iSula\345\256\271\345\231\250\345\274\225\346\223\216.md" "b/docs/zh/docs/20.03_LTS/docs/Container/iSula\345\256\271\345\231\250\345\274\225\346\223\216.md"
similarity index 91%
rename from "content/zh/docs/Container/iSula\345\256\271\345\231\250\345\274\225\346\223\216.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/iSula\345\256\271\345\231\250\345\274\225\346\223\216.md"
index 51486cb5ee2f391e11455f67c81d9a47aede5d60..3386c47f47f6dfa6374eea93d6e38dd19360eb4b 100644
--- "a/content/zh/docs/Container/iSula\345\256\271\345\231\250\345\274\225\346\223\216.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/iSula\345\256\271\345\231\250\345\274\225\346\223\216.md"
@@ -1,11 +1,11 @@
-# iSula容器引擎
-
-iSula通用容器引擎相比Docker，是一种新的容器解决方案，提供统一的架构设计来满足CT和IT领域的不同需求。相比Golang编写的Docker，轻量级容器使用C/C++实现，具有轻、灵、巧、快的特点，不受硬件规格和架构的限制，底噪开销更小，可应用领域更为广泛。
-
-容器统一架构如[图1](#zh-cn_topic_0182207099_fig10763114141217)所示。
-
-**图 1**  容器统一架构  
-
-
-![](figures/zh-cn_image_0183048952.png)
-
+# iSula容器引擎
+
+iSula通用容器引擎相比Docker，是一种新的容器解决方案，提供统一的架构设计来满足CT和IT领域的不同需求。相比Golang编写的Docker，轻量级容器使用C/C++实现，具有轻、灵、巧、快的特点，不受硬件规格和架构的限制，底噪开销更小，可应用领域更为广泛。
+
+容器统一架构如[图1](#zh-cn_topic_0182207099_fig10763114141217)所示。
+
+**图 1**  容器统一架构  
+
+
+![](./figures/zh-cn_image_0183048952.png)
+
diff --git "a/content/zh/docs/Container/isula-build\346\236\204\345\273\272\345\267\245\345\205\267.md" "b/docs/zh/docs/20.03_LTS/docs/Container/isula-build\345\256\271\345\231\250\345\217\221\345\270\203\344\273\266\346\236\204\345\273\272\345\267\245\345\205\267.md"
similarity index 57%
rename from "content/zh/docs/Container/isula-build\346\236\204\345\273\272\345\267\245\345\205\267.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/isula-build\345\256\271\345\231\250\345\217\221\345\270\203\344\273\266\346\236\204\345\273\272\345\267\245\345\205\267.md"
index 174a2ed26e8a86923768c59c958a65a9c9414f6e..0fd7bfab195d37f3413dd4cce47607cf6f735572 100644
--- "a/content/zh/docs/Container/isula-build\346\236\204\345\273\272\345\267\245\345\205\267.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/isula-build\345\256\271\345\231\250\345\217\221\345\270\203\344\273\266\346\236\204\345\273\272\345\267\245\345\205\267.md"
@@ -1,798 +1,727 @@
-# isula-build容器镜像构建
-
-## 概述
-
-### 简介
-
-isula-build是iSula团队推出的容器镜像构建工具，安装部署过程简单，通过Dockerfile文件可以迅速构建出容器镜像。其中，isula-build提供命令行工具，isula-builder常驻后台，处理客户端请求。
-
-- 该工具目前所支持功能：
-  1. ctr-img，构建容器镜像。
-     1. build，根据给定dockerfile构建出容器镜像。
-     2. images，列出本地容器镜像。
-     3. import，导入容器基础镜像。
-     4. load，导入层叠镜像。
-     5. rm，删除本地镜像。
-     6. save，导出容器镜像至本地磁盘。
-     7. tag，给本地容器镜像打tag。
-  2. login，登陆容器镜像仓库。
-  3. logout，登出容器镜像仓库。
-  4. version，查看版本号。
-- isula-build包含主要特性：
-  1. 兼容Dockerfile语法。
-  3. 支持文件系统扩展属性，如Selinux、IMA、EVM等。
-  4. 支持多种镜像导出格式，可以直接将构建镜像结果推送至iSulad或docker。
-
-### 快速引导
-
-#### 安装部署
-
-- rpm包安装
-
-  ```
-  sudo rpm -ivh isula-build-*.rpm && systemctl start isula-build
-  ```
-
-- yum安装
-
-  推荐该方式，只需要配置openEuler yum源即可。
-
-  ```
-  sudo yum install -y isula-build && systemctl start isula-build
-  ```
-
-  说明：
-
-  isula-build 构建时依赖 runc，当你安装时需要再安装单独的docker-runc或完整的docker-engine。
-
-#### 示例
-
-- 新建buildDir目录，在该目录下创建一个dockerfile文件，内容如下：
-
-  ```
-  FROM busybox:latest
-  MAINTAINER "someone"
-  RUN ["touch", "bar"]
-  LABEL foo=bar
-  EXPOSE 8888/udp
-  EXPOSE 9999/tcp
-  ENV a=hello
-  ARG word
-  ADD ./* /home/
-  COPY ./* /home/dir1/
-  VOLUME ["var/log"]
-  STOPSIGNAL 15
-  HEALTHCHECK  --interval=5m --timeout=3s --retries=1 
-  CMD ["pwd"]
-  SHELL ["pwd"]
-  ```
-
-- 在该目录下使用isula-build构建镜像，过程如下：
-
-  ```
-  $ sudo isula-build ctr-img build -f dockerfile .
-  STEP  1: FROM busybox:latest
-  STEP  2: MAINTAINER "someone"
-  STEP  3: RUN ["touch", "bar"]
-  STEP  4: LABEL foo=bar
-  STEP  5: EXPOSE 8888/udp
-  STEP  6: EXPOSE 9999/tcp
-  STEP  7: ENV a=hello
-  STEP  8: ARG word
-  STEP  9: ADD ./* /home/
-  STEP 10: COPY ./* /home/dir1/
-  STEP 11: VOLUME ["var/log"]
-  STEP 12: STOPSIGNAL 15
-  STEP 13: HEALTHCHECK --interval=5m --timeout=3s --retries=1 CMD ["pwd"]
-  STEP 14: SHELL ["pwd"]
-  Getting image source signatures
-  Copying blob sha256:e9235582825a2691b1c91a96580e358c99acfd48082cbf1b92fd2ba4a791efc3
-  Copying blob sha256:dc3bca97af8b81508c343b13a08493c7809b474dc25986fcbae90c6722201be3
-  Copying config sha256:9ec92a8819f9da1b06ea9ff83307ff859af2959b70bfab101f6a325b1a211549
-  Writing manifest to image destination
-  Storing signatures
-  Build success with image id: 9ec92a8819f9da1b06ea9ff83307ff859af2959b70bfab101f6a325b1a211549
-  ```
-
-- 列出所构建镜像。
-
-  ```
-  $ sudo isula-build ctr-img images
-  -----------------  -----------  ----------------  ----------------------------------------------    
-      REPOSITORY         TAG          IMAGE ID                       CREATED        
-  ------------------  ----------  ----------------  ----------------------------------------------       
-         foo            latest      9ec92a8819f9        2020-06-11 07:45:39.265106109 +0000 UTC
-  ```
-
-- 删除镜像。
-
-  ```
-  $ sudo isula-build ctr-img rm 9ec92a8819f9
-  Deleted: sha256:86567f7a01b04c662a9657aac436e8d63ecebb26da4252abb016d177721fa11b
-  ```
-
-#### 重点特性
-
-- isula-build兼容dockerfile语法。
-- isula-build可以将构建好的容器镜像直接导入到iSulad、dockerd、registry和本地tar包。
-
-  
-
-#### 集成
-
-关于iSulad和docker的集成，详情见[与容器引擎集成](#与容器引擎集成)。
-
-### 注意事项
-
-关于相关约束限制以及与docker build的区别详情见[使用注意事项](#使用注意事项)。
-
-
-
-## 使用指南
-
-### 配置
-
-isula-builder 包含如下配置文件：
-
-- /etc/isula-build/configuration.toml：isula-builder 总配置文件，包含设置 isula-builder 日志级别、持久化目录和运行时目录、OCI runtime等。
-  1. debug：设置是否打开debug日志，可选参数：true、false。
-  2. loglevel：设置日志级别，可选参数：“debug”、“info”、“warn”、“error”。
-  3. run_root：设置运行时数据根目录。
-  4. data_root：设置本地持久化目录。
-  5. runtime：设置runtime种类，目前支持runc。
-- /etc/isula-build/storage.toml: 本地持久化存储的配置文件，包含所使用的存储驱动的配置。
-  1. driver：存储驱动类型，目前支持overlay2。
-  2. runroot：临时存储目录。
-  3. graphroot：可读写的镜像存储目录。
-  4. 更多设置可参考 [containers-storage.conf.5.md](https://github.com/containers/storage/blob/master/docs/containers-storage.conf.5.md)。
-- /etc/isula-build/registries.toml : 针对各个镜像仓库的配置文件，含可用的镜像仓库列表、镜像仓库黑名单。
-  1. registries.search：镜像仓库搜索域，在此list的镜像仓库可以被感知，不在此列的不被感知。
-  2. registries.insecure：可访问的不安全镜像仓库地址，在此列表中的镜像仓库将不会通过鉴权，不推荐使用。
-  3. 更多设置可参考 [containers-registries.conf.5.md](https://github.com/containers/image/blob/master/docs/containers-registries.conf.5.md)。
-- /etc/isula-build/policy.json：镜像pull/push策略文件。注：当前不支持对其进行配置
-
-在启动 isula-builder 服务之前，先对服务按需配置，在还未熟悉配置的情况下，也可以直接使用rpm包安装的默认配置直接启动服务。
-
-说明：
-
-以上配置文件，isula-build 支持最大 1M 的配置文件。
-
-### 启动服务
-
-#### 通过systemd启动
-
-1. 配置需在上述配置文件中进行修改。
-
-   - 启动 isula-build 服务：
-
-     ```
-     systemctl start isula-build.service
-     ```
-
-   - 停止 isula-build 服务：
-
-     ```
-     systemctl stop isula-build.service
-     ```
-
-   - 重启 isula-builder 服务：
-
-     ```
-     systemctl restart isula-build.service
-     ```
-
-   - 查看 isula-build 服务的运行日志：
-
-     ```
-     journalctl -u isula-build
-     ```
-
-2. 修改完配置文件后，需使用如下命令使配置生效。
-
-   ```
-   systemctl daemon-reload
-   ```
-
-#### 直接运行二进制启动
-
-部分配置可通过isula-builder的flag进行设置，例如：
-
-```
-isula-builder --dataroot "/var/lib/isula-build" --debug=false
-```
-
-#### isula-builder目前支持的flags
-
-```
-      --dataroot string         persistent dir (default "/var/lib/isula-build")  
-  -D, --debug                   print debugging information (default true)  
-  -h, --help                    help for isula-builder      
-      --log-level string        The log level to be used. Either "debug", "info", "warn" or "error". (default "info")      
-      --runroot string          runtime dir (default "/var/run/isula-build")      
-      --storage-driver string   storage-driver (default "overlay")      
-      --storage-opt strings     storage driver option (default [overlay.mountopt=nodev])      
-      --version                 version for isula-builder
-```
-
-- -d, --debug: 是否开启调测模式。
-- --log-level: 日志级别，支持 "debug", "info", "warn" or "error"，默认为 "info"。
-- --dataroot: 本地持久化路径，默认为"/var/lib/isula-build/"。
-- --runroot: 运行时路径，默认为"/var/run/isula-build/"。
-- --storage-driver：底层存储驱动类型。
-- --storage-opt: 底层存储驱动配置。
-
-当命令行启动参数中传递了与配置文件相同的配置选项，优先使用命令行参数启动。
-
-### 子命令使用
-
-目前 isula-build提供了如下对于容器镜像（ctr-img）操作的功能：
-
-- build，根据给定dockerfile构建出容器镜像。
-- images，列出本地容器镜像。
-- import，导入容器基础镜像。
-- load，导入层叠镜像。
-- rm，删除本地容器镜像。
-- save, 导出层叠镜像至本地磁盘。
-- tag，给本地容器镜像打tag。
-
-同时提供了如下通用指令：
-
-- info，查看isula-build的运行环境和系统信息。
-- login，登入远端容器镜像仓库。
-- logout，从远端容器镜像仓库登出。
-- version，查看isula-build和isula-builder的版本号。
-- completion（隐式提供），生成bash环境命令补全脚本。
-
-#### 容器镜像构建
-
-```
-isula-build ctr-img build
-```
-
-其中 build 包含如下 flags：
-
-1. --build-arg：string列表，构建过程中需要用到的变量。
-2. --build-static：KV值，构建二进制一致性。目前包含如下K值：
-   1. build-time：string，使用固定时间戳来构建容器镜像；时间戳格式为“YYYY-MM-DD HH-MM-SS”。
-3. -f, --filename：string，Dockerfile的路径，不指定则是使用当前路径的Dockerfile文件。
-4. --iidfile：string，输出 image ID 到本地文件。
-5. -o, --output：string，镜像导出的方式和路径。
-6. --proxy：布尔值，继承主机侧环境的proxy环境变量（默认为true）。
-7. --tag：string，设置构建成功的镜像的tag值。
-8. --cap-add：string列表，构建过程中RUN指令所需要的权限。
-
-以下为各个 flags 的详解。
-
-- **--build-arg**
-
-  从命令行接受参数作为Dockerfile中的参数，用法：
-
-  ```
-  isula-build ctr-img build --build-arg foo=bar -f Dockerfile
-  ```
-
-  ```
-  $ echo "This is bar file" > bar.txt
-  $ cat Dockerfile_arg
-  FROM busybox
-  ARG foo
-  ADD ${foo}.txt .
-  RUN cat ${foo}.txt
-  $ sudo isula-build ctr-img build --build-arg foo=bar -f Dockerfile_arg
-  STEP  1: FROM busybox
-  Getting image source signatures
-  Copying blob sha256:8f52abd3da461b2c0c11fda7a1b53413f1a92320eb96525ddf92c0b5cde781ad
-  Copying config sha256:e4db68de4ff27c2adfea0c54bbb73a61a42f5b667c326de4d7d5b19ab71c6a3b
-  Writing manifest to image destinationStoring signatures
-  STEP  2: ARG foo
-  STEP  3: ADD ${foo}.txt .
-  STEP  4: RUN cat ${foo}.txt
-  This is bar file
-  Getting image source signatures
-  Copying blob sha256:6194458b07fcf01f1483d96cd6c34302ffff7f382bb151a6d023c4e80ba3050a
-  Copying blob sha256:6bb56e4a46f563b20542171b998cb4556af4745efc9516820eabee7a08b7b869
-  Copying config sha256:39b62a3342eed40b41a1bcd9cd455d77466550dfa0f0109af7a708c3e895f9a2
-  Writing manifest to image destination
-  Storing signatures
-  Build success with image id: 39b62a3342eed40b41a1bcd9cd455d77466550dfa0f0109af7a708c3e895f9a2
-  ```
-
-- **--build-static**
-
-  指定为静态构建，则isula-build会消除所有时间戳差异，同时消除其他构建过程差异，包括：容器ID、hsotname等, 最终构建出能满足BEP要求的容器镜像。
-
-  在使用isula-build进行容器镜像构建时，假如给 build 子命令一个固定的时间戳，并在限定如下条件的时候：
-
-  - 构建环境前后保持一致。
-  - 构建Dockerfile前后保持一致。
-  - 构建产生的中间数据前后保持一致。
-  - 构建命令相同。
-  - 第三方库版本一致。
-
-  对于容器镜像构建，isula-build支持相同的Dockerfile。如果构建环境相同，则多次构建生成的镜像内容和镜像ID相同。
-
-  --build-static接受k=v形式的键值对选项，当前支持的选项有：
-
-  - build-time：字符串类型。构建静态镜像的固定时间戳，格式为“YYYY-MM-DD HH-MM-SS”。时间戳影响diff层创建修改时间的文件属性。
-
-    使用方式如下：
-
-    ```
-    $ sudo isula-build ctr-img build -f Dockerfile --build-static='build-time=2020-05-23 10:55:33' .
-    ```
-
-    以此方式，同一环境多次构建出来的容器镜像和镜像ID均会保持一致。
-
-- **--iidfile**
-
-  将构建的镜像ID输出到文件，用法：
-
-  ```
-  isula-build ctr-img build --iidfile testfile
-  ```
-
-  ```
-  $ sudo isula-build ctr-img build -f Dockerfile_arg --iidfile testfile
-  
-  $ cat testfile
-  76cbeed38a8e716e22b68988a76410eaf83327963c3b29ff648296d5cd15ce7b
-  ```
-
-- **-o, --output**
-
-  目前 -o, --output 支持如下形式：
-
-  - `isulad:image:tag`：将构建成功的镜像直接推送到 iSulad。比如：`-o isulad:busybox:latest`。同时需要注意如下约束：
-    - isula-build 和 iSulad 必须在同一个节点上
-    - tag必须配置
-    - isula-build client端需要将构建成功的镜像暂存成 /var/tmp/isula-build-tmp-%v.tar 再导入至 iSulad，用户需要保证 /var/tmp/ 目录有足够磁盘空间
-  - `docker-daemon:image:tag`：将构建成功的镜像直接推送到 Docker daemon。比如：`-o docker-daemon:busybox:latest`。同时需要注意如下约束：
-    - isula-build 和 docker 必须在同一个节点上
-    - tag必须配置
-  - `docker://registry.example.com/repository:tag`：将构建成功的镜像直接推送到远端镜像仓库。比如：`-o docker://localhost:5000/library/busybox:latest`。
-  - `docker-archive:/:image:tag`：将构建成功的镜像以Docker image的格式保存至本地。比如：`-o docker-archive:/root/image.tar:busybox:latest`。
-
-  除去各个flags之外，build子命令的命令行最后还会接收一个argument，该argument类型是string，意义为context，即该Dockerfile构建环境的上下文。该参数默认值为isula-build被执行的当前路径。该路径会影响 .dockerignore 和 Dockerfile的ADD/COPY指令 所检索的路径。
-
-- **--proxy**
-
-  选择构建时RUN指令启动的容器是否从环境上继承proxy相关环境变量"http_proxy","https_proxy","ftp_proxy","no_proxy","HTTP_PROXY","HTTPS_PROXY","FTP_PROXY","NO_PROXY"，默认为true。
-
-  当用户在Dockerfile配置proxy相关ARG或ENV，将覆盖所继承的环境变量。
-
-  注意：若client与daemon不在同一个终端运行，所能继承的环境变量为daemon所在终端的环境变量。
-
-- **--tag**
-
-  设置镜像构建成功之后，该镜像在本地磁盘存储时的tag。
-
-- **--cap-add**
-
-  添加构建过程中RUN指令所需权限，用法：
-
-  ```
-  isula-build ctr-img build --cap-add CAP_SYS_ADMIN --cap-add CAP_SYS_PTRACE -f Dockerfile
-  ```
-
-说明：
-
-isula-build最大支持并发构建100个容器镜像、支持Dockerfile最大1M、支持 .dockerignore 最大 1M
-
-#### 查看本地持久化构建镜像
-
-可通过images命令查看当前本地持久化存储的镜像：
-
-```
-$ sudo isula-build ctr-img images
-----------------------------------------------  -----------  -----------------  --------------------------  ------------ 
-REPOSITORY                                      TAG          IMAGE ID           CREATED                     SIZE
-----------------------------------------------  -----------  -----------------  --------------------------  ------------ 
-localhost:5000/library/alpine                   latest       a24bb4013296       2020-20-19 19:59:197        5.85 MB 
-                                                 39b62a3342ee       2020-20-38 38:66:387        1.45 MB
-----------------------------------------------  -----------  -----------------  --------------------------  ------------
-```
-
-#### 导入容器基础镜像
-
-openEuler会随版本发布一个容器基础镜像，比如openEuler-docker.x86_64.tar.xz。可以通过ctr-img import指令将它导入。
-
-命令原型如下：
-
-```
-isula-build ctr-img import [flags]
-```
-
-使用举例：
-
-```
-$ sudo isula-build ctr-img import ./openEuler-docker.x86_64.tar.xz openeuler:20.03
-Import success with image id: 7317851cd2ab33263eb293f68efee9d724780251e4e92c0fb76bf5d3c5585e37
-$ sudo isula-build ctr-img images
-----------------------------------------------  --------------------  -----------------  ------------------------  ------------ 
-REPOSITORY                                      TAG                   IMAGE ID           CREATED                   SIZE
-----------------------------------------------  --------------------  -----------------  ------------------------  ------------ 
-openeuler                                       20.03                 7317851cd2ab       2020-08-01 06:25:34       500 MB
-----------------------------------------------  --------------------  -----------------  ------------------------  ------------
-```
-
-说明：
-
-isula-build 支持导入最大1G的容器基础镜像
-
-#### 导入层叠镜像
-
-层叠镜像指的是通过 docker save 或 isula-build ctr-img save 等指令，将一个构建完成的镜像保存至本地之后，镜像压缩包内是一层一层 layer.tar 的镜像包。可以通过 ctr-img load 指令将它导入至 isula-build。
-
-命令原型如下：
-
-```
-isula-build ctr-img load [flags]
-```
-
-使用举例如下：
-
-```
-$ sudo isula-build ctr-img load -i ubuntu.tarGetting image source signatures
-Copying blob sha256:cf612f747e0fbcc1674f88712b7bc1cd8b91cf0be8f9e9771235169f139d507c
-Copying blob sha256:f934e33a54a60630267df295a5c232ceb15b2938ebb0476364192b1537449093
-Copying blob sha256:943edb549a8300092a714190dfe633341c0ffb483784c4fdfe884b9019f6a0b4
-Copying blob sha256:e7ebc6e16708285bee3917ae12bf8d172ee0d7684a7830751ab9a1c070e7a125
-Copying blob sha256:bf6751561805be7d07d66f6acb2a33e99cf0cc0a20f5fd5d94a3c7f8ae55c2a1
-Copying blob sha256:c1bd37d01c89de343d68867518b1155cb297d8e03942066ecb44ae8f46b608a3
-Copying blob sha256:a84e57b779297b72428fc7308e63d13b4df99140f78565be92fc9dbe03fc6e69
-Copying blob sha256:14dd68f4c7e23d6a2363c2320747ab88986dfd43ba0489d139eeac3ac75323b2
-Copying blob sha256:a2092d776649ea2301f60265f378a02405539a2a68093b2612792cc65d00d161
-Copying blob sha256:879119e879f682c04d0784c9ae7bc6f421e206b95d20b32ce1cb8a49bfdef202
-Copying blob sha256:e615448af51b848ecec00caeaffd1e30e8bf5cffd464747d159f80e346b7a150
-Copying blob sha256:f610bd1e9ac6aa9326d61713d552eeefef47d2bd49fc16140aa9bf3db38c30a4
-Copying blob sha256:bfe0a1336d031bf5ff3ce381e354be7b2bf310574cc0cd1949ad94dda020cd27
-Copying blob sha256:f0f15db85788c1260c6aa8ad225823f45c89700781c4c793361ac5fa58d204c7
-Copying config sha256:c07ddb44daa97e9e8d2d68316b296cc9343ab5f3d2babc5e6e03b80cd580478e
-Writing manifest to image destination
-Storing signatures
-Loaded image as c07ddb44daa97e9e8d2d68316b296cc9343ab5f3d2babc5e6e03b80cd580478e
-```
-
-说明：
-
-- isula-build load命令仅支持导入包含单个层叠镜像的镜像压缩文件
-- isula-build 支持导入最大50G的容器层叠镜像
-
-#### 删除本地持久化镜像
-
-可通过rm命令删除当前本地持久化存储的镜像
-
-目前支持的flags有：
-
-```
-Flags:  
-  -a, --all     remove all images  
-  -h, --help    help for rm 
-  -p, --prune   remove all untagged images
-```
-
-这些flags分别：
-
-- -a, --all：删除所有本地持久化存储的镜像。
-
-- -p, --prune：删除所有没有tag的本地持久化存储的镜像。
-
-  使用举例：
-
-  ```
-  isula-build ctr-img rm -p
-  ```
-
-  ```
-  $ sudo isula-build ctr-img rm -p
-  Deleted: sha256:78731c1dde25361f539555edaf8f0b24132085b7cab6ecb90de63d72fa00c01d
-  Deleted: sha256:eeba1bfe9fca569a894d525ed291bdaef389d28a88c288914c1a9db7261ad12c
-  ```
-
-#### 导出层叠镜像
-
-可通过save命令导出层叠镜像到本地磁盘。命令原型如下：
-
-```
-isula-build ctr-img save [REPOSITORY:TAG]|imageID -o xx.tar
-```
-
-通过镜像名字/tag进行导出：
-
-```
-$ sudo isula-build ctr-img save busybox:latest -o busybox.tar
-Getting image source signatures
-Copying blob sha256:50644c29ef5a27c9a40c393a73ece2479de78325cae7d762ef3cdc19bf42dd0a
-Copying blob sha256:824082a6864774d5527bda0d3c7ebd5ddc349daadf2aa8f5f305b7a2e439806f
-Copying blob sha256:5f70bf18a086007016e948b04aed3b82103a36bea41755b6cddfaf10ace3c6ef
-Copying config sha256:21c3e96ac411242a0e876af269c0cbe9d071626bdfb7cc79bfa2ddb9f7a82db6
-Writing manifest to image destination
-Storing signatures
-Save success with image: busybox:latest
-```
-
-通过ImageID进行导出：
-
-```
-$ sudo isula-build ctr-img save 21c3e96ac411 -o busybox.tar
-Getting image source signatures
-Copying blob sha256:50644c29ef5a27c9a40c393a73ece2479de78325cae7d762ef3cdc19bf42dd0a
-Copying blob sha256:824082a6864774d5527bda0d3c7ebd5ddc349daadf2aa8f5f305b7a2e439806f
-Copying blob sha256:5f70bf18a086007016e948b04aed3b82103a36bea41755b6cddfaf10ace3c6ef
-Copying config sha256:21c3e96ac411242a0e876af269c0cbe9d071626bdfb7cc79bfa2ddb9f7a82db6
-Writing manifest to image destination
-Storing signatures
-Save success with image: 21c3e96ac411
-```
-
-#### 查看运行环境与系统信息
-
-可以通过“isula-build info”指令查看
-
-命令原型如下：
-
-```
-isula-build info [flags]
-```
-
-支持如下Flags：
-
-- -H, --human-readable  布尔值，以常用内存表示格式打印内存信息，使用1000次幂
-
-  使用举例：
-
-  ```
-  $ sudo 
-  isula-build info -H
-  General:  
-    MemTotal:     7.63 GB  
-    MemFree:      757 MB  
-    SwapTotal:    8.3 GB  
-    SwapFree:     8.25 GB  
-    OCI Runtime:  runc  
-    DataRoot:     /var/lib/isula-build/  
-    RunRoot:      /var/run/isula-build/  
-    Builders:     0  
-    Goroutines:   12
-  Store:  
-    Storage Driver:     overlay  
-    Backing Filesystem: extfs
-  Registry:  
-    Search Registries:   
-      oepkgs.net
-    Insecure Registries:    
-      localhost:5000    
-      oepkgs.net
-  ```
-
-#### 与远程镜像仓库认证
-
-可以通过 login 或 logout 命令来与远程镜像仓库交互
-
-- **Login 使用**：
-
-  ```
-  isula-build login mydockerhub.io
-  ```
-
-  你可以运行 login 命令来登录远程镜像仓库
-
-  目前支持的flag有：
-
-  ```
-  Flags:  
-    -p, --password-stdin    Read password from stdin  
-    -u, --username string   Username to access registry
-  ```
-
-  通过stdin输入密码：
-
-  ```
-  $ cat creds.txt | sudo isula-build login -u cooper -p mydockerhub.io
-  Login Succeeded
-  ```
-
-  通过交互式输入密码：
-
-  ```
-  $ sudo isula-build login mydockerhub.io -u cooper
-  Password:
-  Login Succeeded
-  ```
-
-- **Logout 使用**：
-
-  ```
-  isula-build logout mydockerhub.io
-  ```
-
-  你可以运行 logout 命令来登出远程镜像仓库。
-
-  目前支持的flag有：
-
-  ```
-  Flags:  
-    -a, --all   Logout all registries
-  ```
-
-  Flags解释如下：
-
-  -a, --all：登出所有的镜像仓库。
-
-  ```
-  $ sudo isula-build logout -a  
-    Removed authentications
-  ```
-
-#### 版本查询
-
-可通过version命令查看当前版本信息：
-
-```
-$ sudo isula-build version
-Client:
-  Version:       0.9.2
-  Go Version:    go1.13.3
-  Git Commit:    ccb2a13
-  Built:         Sat Aug 22 08:06:47 2020
-  OS/Arch:       linux/amd64
-
-Server:
-  Version:       0.9.2
-  Go Version:    go1.13.3
-  Git Commit:    ccb2a13
-  Built:         Sat Aug 22 08:06:47 2020
-  OS/Arch:       linux/amd64
-```
-
-说明：
-
-isula-build completion 和 isula-builder completion 命令用于生成bash命令补全脚本。该命令为命令行框架隐式提供，不会显示在help信息中。
-
-
-
-### 与容器引擎集成
-
-isula-build可以与iSulad和docker集成，将构建好的容器镜像导入到容器引擎的本地存储中。
-
-#### 与iSulad集成
-
-支持将构建成功的镜像直接导出到iSulad。命令行举例：
-
-```
-$ sudo isula-build ctr-img build -f Dockerfile -o isulad:busybox:2.0
-```
-
-通过在-o参数中指定iSulad，将构建好的容器镜像导出到iSulad，可以通过isula images查询。
-
-说明：
-
-要求isula-build和iSulad在同一节点。
-
-#### 与Docker集成
-
-支持将构建成功的镜像直接导出到Docker daemon。命令行举例：
-
-```
-$ sudo isula-build ctr-img build -f Dockerfile -o docker-daemon:busybox:2.0
-```
-
-通过在-o参数中指定docker-daemon，将构建好的容器镜像导出到docker, 可以通过docker images查询。
-
-说明：
-
-要求isula-build和Docker在同一节点。
-
-
-
-## 使用注意事项
-
-本章节主要介绍在使用isula-build构建镜像时相关的约束和限制，以及与docker build的差异。
-
-### 约束和限制
-
-1. 直接导出镜像到iSulad或docker daemon时，必须指定tag。
-2. 直接导出镜像到iSulad时，isula-build client端需要将构建成功的镜像暂存成 `/var/tmp/isula-build-tmp-%v.tar` 再导入至 iSulad，用户需要保证 /var/tmp/ 目录有足够磁盘空间；同时如果在导出过程中 isula-build client进程被KILL或Ctrl+C终止，需要依赖用户手动清理 `/var/tmp/isula-build-tmp-%v.tar` 文件。
-3. 用户需保证OCI runtime(runc)可执行文件的安全性，避免被恶意替换。
-4. isula-build不支持将持久化工作目录dataroot配置在内存盘上，比如tmpfs。
-5. isula-build目前仅支持使用overlay2为底层graphdriver。
-6. isula-build当前仅支持Docker镜像。
-7. 用户需保证Dockerfile文件的权限为仅当前用户可读写，避免别的用户进行篡改。
-8. 目前仅支持使用主机网络。
-9. 导出的镜像压缩格式，目前仅支持tar.gz格式。
-10. stage name不能以数字开头、stage name的长度限制为64个字符
-
-### 与docker差异
-
-- isula-build兼容dockerfile语法，但与docker build相比，使用isula-build进行镜像构建和docker build的差异如下：
-  1. 在每一个镜像构建stage完成后做一次提交，而不是按行提交。
-  2. isula-build暂不支持缓存。
-  3. 仅RUN指令在构建容器中执行。
-  4. 目前不支持history。
-  5. isula-build的stage name支持以数字开头。
-  6. isula-build的stage name最长可为64个字符。
-  7. ADD指令目前不支持远端URL形式。
-  8. 暂不支持对单次构建进行资源限额，可采取对isula-builder配置资源限额的方式进行限制。
-- isula-build与docker的其它差异如下：
-  1. 统计镜像大小时，isula-build是直接计算每层tar包大小之和，而docker是通过解压tar遍历diff目录计算文件大小之和，因此通过`isula-build ctr-img images`查看的镜像大小与`docker images`的显示上有一定差异。
-
-### 与Dockerfile语法上的差异
-
-1. 暂不支持ADD指令提供的来源是远端url。
-
-   
-
-## 附录
-
-### 命令行参数说明
-
-**表1** ctr-img build 命令参数列表
-
-| **命令**      | **参数**       | **说明**                                                     |
-| ------------- | -------------- | ------------------------------------------------------------ |
-| ctr-img build | --build-arg    | string列表，构建过程中需要用到的变量                         |
-|               | --build-static | KV值，构建二进制一致性。目前包含如下K值：- build-time：string，使用固定时间戳来构建容器镜像；时间戳格式为“YYYY-MM-DD HH-MM-SS” |
-|               | -f, --filename | string，Dockerfile的路径，不指定则是使用当前路径的Dockerfile文件 |
-|               | --iidfile      | string，输出 image ID 到本地文件                             |
-|               | -o, --output   | string，镜像导出的方式和路径                                 |
-|               | --proxy        | 布尔值，继承主机侧环境的proxy环境变量（默认为true）          |
-|               | --tag          | string，给构建的镜像添加tag                                  |
-|               | --cap-add      | string列表，构建过程中RUN指令所需要的权限                    |
-
-**表2** ctr-img load 命令参数列表
-
-| **命令**     | **参数**    | **说明**                          |
-| ------------ | ----------- | --------------------------------- |
-| ctr-img load | -i, --input | string，需要导入的本地tar包的路径 |
-
-**表3** ctr-img rm 命令参数列表
-
-| **命令**   | **参数**    | **说明**                                      |
-| ---------- | ----------- | --------------------------------------------- |
-| ctr-img rm | -a, --all   | 布尔值，删除所有本地持久化存储的镜像          |
-|            | -p, --prune | 布尔值，删除所有没有tag的本地持久化存储的镜像 |
-
-**表4** ctr-img save 命令参数列表
-
-| **命令**     | **参数**     | **说明**                           |
-| ------------ | ------------ | ---------------------------------- |
-| ctr-img save | -o, --output | string，镜像导出后在本地的存储路径 |
-
-**表5** login 命令参数列表
-
-| **命令** | **参数**             | **说明**                                                |
-| -------- | -------------------- | ------------------------------------------------------- |
-| login    | -p, --password-stdin | 布尔值，是否通过stdin读入密码；或采用交互式界面输入密码 |
-|          | -u, --username       | string，登陆镜像仓库所使用的用户名                      |
-
-**表6** logout 命令参数列表
-
-| **命令** | **参数**  | **说明**                             |
-| -------- | --------- | ------------------------------------ |
-| logout   | -a, --all | 布尔值，是否登出所有已登陆的镜像仓库 |
-
-### 通信矩阵
-
-isula-build两个组件进程之间通过unix socket套接字文件进行通信，无端口通信。
-
-### 文件与权限
-
-1. isula-build 所有的操作均需要使用 root 权限。
-
-2. isula-build 运行涉及文件权限如下表所示：
-
-   | **文件路径**                                | **文件/文件夹权限** | **说明**                                                     |
-   | ------------------------------------------- | ------------------- | ------------------------------------------------------------ |
-   | /usr/bin/isula-build                        | 550                 | 命令行工具二进制文件。                                       |
-   | /usr/bin/isula-builder                      | 550                 | 服务端isula-builder进程二进制文件。                          |
-   | /usr/lib/systemd/system/isula-build.service | 640                 | systemd配置文件，用于管理isula-build服务。                   |
-   | /etc/isula-build/configuration.toml         | 600                 | isula-builder 总配置文件，包含设置 isula-builder 日志级别、持久化目录和运行时目录、OCI runtime等。 |
-   | /etc/isula-build/policy.json                | 600                 | 签名验证策略文件的语法文件。                                 |
-   | /etc/isula-build/registries.toml            | 600                 | 针对各个镜像仓库的配置文件，含可用的镜像仓库列表、镜像仓库黑名单。 |
-   | /etc/isula-build/storage.toml               | 600                 | 本地持久化存储的配置文件，包含所使用的存储驱动的配置。       |
-   | /var/run/isula_build.sock                   | 600                 | 服务端isula-builder的本地套接字。                            |
-   | /var/lib/isula-build                        | 700                 | 本地持久化目录。                                             |
-   | /var/run/isula-build                        | 700                 | 本地运行时目录。                                             |
-   | /var/tmp/isula-build-tmp-*.tar              | 600                 | 镜像导出至iSulad时的本地暂存目录。                           |
-
-   
\ No newline at end of file
+# isula-build: 容器发布件构建工具
+
+## 概述
+
+isula-build是iSula容器团队推出的容器发布件构建工具，安装部署过程简单，目前支持通过Dockerfile文件快速构建容器镜像。
+
+isula-build采用服务端/客户端模式，其中，isula-build为客户端，提供了命令行工具，isula-builder 服务端常驻后台，处理客户端请求。
+
+## 安装 isula-build
+
+- yum安装
+
+  推荐该方式，只需要配置openEuler yum源即可。
+
+  ```sh
+  sudo yum install -y isula-build
+  ```
+  
+- rpm包安装
+
+  ```sh
+  sudo rpm -ivh isula-build-*.rpm
+  ```
+
+说明：
+
+isula-build 构建 Dockerfile 内的 RUN 指令时依赖可执行文件 runc ，需要 isula-build 的运行环境上预装好 runc。安装方式视用户使用场景而定，如果用户不需要使用完整的 docker-engine 工具链，则可以仅安装 docker-runc rpm包：
+
+```sh
+sudo yum install -y docker-runc
+```
+
+如果用户同样会使用完整的 docker-engine 工具链，则可以安装 docker-engine rpm包，它同样会包含可执行文件 runc ：
+
+```sh
+sudo yum install -y docker-engine
+```
+
+
+
+## 简单的使用示例
+
+以下提供一个简单的使用示例，介绍从Dockerfile文件的编写，到通过它进行容器镜像的构建，到查看构建完成之后的容器镜像，最终将它从本地进行删除。
+
+1. 新建一个目录，在该目录下创建 Dockerfile 文件，内容如下：
+
+
+```dockerfile
+FROM alpine:latest
+LABEL foo=bar
+COPY ./* /home/dir1/
+```
+
+2. 在该目录下使用 isula-build 构建镜像，过程如下：
+
+```sh
+$ sudo isula-build ctr-img build -f dockerfile .
+STEP  1: FROM alpine:latest
+STEP  2: LABEL foo=bar
+STEP  3: COPY ./* /home/dir1/
+Getting image source signatures
+Copying blob sha256:e9235582825a2691b1c91a96580e358c99acfd48082cbf1b92fd2ba4a791efc3
+Copying blob sha256:dc3bca97af8b81508c343b13a08493c7809b474dc25986fcbae90c6722201be3
+Copying config sha256:9ec92a8819f9da1b06ea9ff83307ff859af2959b70bfab101f6a325b1a211549
+Writing manifest to image destination
+Storing signatures
+Build success with image id: 9ec92a8819f9da1b06ea9ff83307ff859af2959b70bfab101f6a325b1a211549
+```
+
+3. 列出所构建镜像。
+
+```sh
+$ sudo isula-build ctr-img images
+-----------------  -----------  ----------------  ----------------------------------------------    
+    REPOSITORY         TAG          IMAGE ID                       CREATED        
+------------------  ----------  ----------------  ----------------------------------------------       
+       foo            latest      9ec92a8819f9        2020-06-11 07:45:39.265106109 +0000 UTC
+```
+
+4. 删除镜像。
+
+```sh
+$ sudo isula-build ctr-img rm 9ec92a8819f9
+Deleted: sha256:86567f7a01b04c662a9657aac436e8d63ecebb26da4252abb016d177721fa11b
+```
+
+
+
+## 使用指南
+
+### 配置 isula-build 服务端
+
+在安装完 isula-build 软件包之后，systemd 管理服务会以 isula-build 软件包自带的 isula-build 服务端默认配置启动 isula-build 服务。如果 isula-build 服务端的默认配置文件不能满足用户的需求，可以参考如下介绍进行定制化配置。需要注意的是，修改完默认配置之后，需要重启 isula-build 服务端使新配置生效，具体操作可参考下一章节。
+
+目前 isula-build 服务端包含如下配置文件：
+
+- /etc/isula-build/configuration.toml：isula-builder 总体配置文件，用于设置 isula-builder 日志级别、持久化目录和运行时目录、OCI runtime等。其中各参数含义如下：
+  - debug：设置是否打开debug日志，可选参数：true、false。
+  - loglevel：设置日志级别，可选参数：“debug”、“info”、“warn”、“error”。
+  - run_root：设置运行时数据根目录。
+  - data_root：设置本地持久化目录。
+  - runtime：设置runtime种类，目前支持runc。
+
+- /etc/isula-build/storage.toml: 本地持久化存储的配置文件，包含所使用的存储驱动的配置。
+  - driver：存储驱动类型，目前支持overlay2。
+  
+    更多设置可参考 [containers-storage.conf.5.md](https://github.com/containers/storage/blob/master/docs/containers-storage.conf.5.md)。
+  
+- /etc/isula-build/registries.toml : 针对各个镜像仓库的配置文件。
+  - registries.search：镜像仓库搜索域，在此list的镜像仓库可以被感知，不在此列的不被感知。
+  - registries.insecure：可访问的不安全镜像仓库地址，在此列表中的镜像仓库将不会通过鉴权，不推荐使用。
+ 
+    更多设置可参考 [containers-registries.conf.5.md](https://github.com/containers/image/blob/master/docs/containers-registries.conf.5.md)。
+  
+- /etc/isula-build/policy.json：镜像pull/push策略文件。注：当前不支持对其进行配置
+
+说明：以上配置文件，isula-build 支持最大 1M 的配置文件。
+
+### 管理 isula-build 服务端
+
+目前 openEuler 采用 systemd 管理软件服务，isula-build 软件包已经自带了 systemd 的服务文件，用户安装完 isula-build 软件包之后可以直接通过 systemd 工具对它进行服务启停等操作。用户同样可以手动启动 isula-build 服务端软件。需要注意的是，同一个节点上不可以同时启动多个 isula-build 服务端软件。
+
+#### 通过 systemd 管理
+
+用户可以通过如下 systemd 的标准指令控制 isula-build 服务的启动、停止、重启等动作：
+
+- 启动 isula-build 服务：
+
+```sh
+sudo systemctl start isula-build.service
+```
+
+- 停止 isula-build 服务：
+
+```sh
+sudo systemctl stop isula-build.service
+```
+
+- 重启 isula-builder 服务：
+
+```sh
+sudo systemctl restart isula-build.service
+```
+
+
+isula-build 软件包安装的 systemd 服务文件保存在 `/usr/lib/systemd/system/isula-build.service`。如果用户需要修改 isula-build 服务的 systemd 配置，可以修改该文件，执行如下命令使配置生效，之后再根据上面提到的 systemd 管理指令重启 isula-build 服务
+
+```sh
+sudo systemctl daemon-reload
+```
+
+#### 直接运行 isula-build 服务端
+
+通过手动运行 isula-build 服务端的方式启动 isula-builder，可通过直接配置 isula-build 服务端的 flag 对其进行设置，例如：
+
+```sh
+sudo isula-builder --dataroot "/var/lib/isula-build" --debug=false
+```
+
+isula-build 服务端目前支持的flags如下：
+
+- -D, --debug: 是否开启调测模式。
+- --log-level: 日志级别，支持 "debug", "info", "warn" or "error"，默认为 "info"。
+- --dataroot: 本地持久化路径，默认为"/var/lib/isula-build/"。
+- --runroot: 运行时路径，默认为"/var/run/isula-build/"。
+- --storage-driver：底层存储驱动类型。
+- --storage-opt: 底层存储驱动配置。
+
+说明：当命令行启动参数中传递了与配置文件相同的配置选项，优先使用命令行参数启动。
+
+
+
+### isula-build 子命令使用
+
+目前 isula-build 提供如下命令行指令：
+
+- ctr-img，容器镜像管理。含如下子命令
+  - build，根据给定dockerfile构建出容器镜像。
+  - images，列出本地容器镜像。
+  - import，导入容器基础镜像。
+  - load，导入层叠镜像。
+  - rm，删除本地容器镜像。
+  - save, 导出层叠镜像至本地磁盘。
+  - tag，给本地容器镜像打tag。
+
+- info，查看isula-build的运行环境和系统信息。
+- login，登录远端容器镜像仓库。
+- logout，退出远端容器镜像仓库。
+- version，查看isula-build和isula-builder的版本号。
+
+以下按照上述维度依次详细介绍这些命令行指令的使用。
+
+#### ctr-img: 容器镜像管理
+
+isula-build 将所有容器镜像管理相关命令划分在子命令 `ctr-img` 下，命令原型为：
+
+```
+isula-build ctr-img [command]
+```
+
+
+
+##### build: 容器镜像构建
+
+```
+isula-build ctr-img build
+```
+
+其中 build 包含如下 flags：
+
+1. --build-arg：string列表，构建过程中需要用到的变量。
+2. --build-static：KV值，构建二进制一致性。目前包含如下K值：
+   1. build-time：string，使用固定时间戳来构建容器镜像；时间戳格式为“YYYY-MM-DD HH-MM-SS”。
+3. -f, --filename：string，Dockerfile的路径，不指定则是使用当前路径的Dockerfile文件。
+4. --iidfile：string，输出 image ID 到本地文件。
+5. -o, --output：string，镜像导出的方式和路径。
+6. --proxy：布尔值，继承主机侧环境的proxy环境变量（默认为true）。
+7. --tag：string，设置构建成功的镜像的tag值。
+8. --cap-add：string列表，构建过程中RUN指令所需要的权限。
+
+以下为各个 flags 的详解。
+
+- **--build-arg**
+
+  从命令行接受参数作为Dockerfile中的参数，用法：
+
+  ```
+  isula-build ctr-img build --build-arg foo=bar -f Dockerfile
+  ```
+
+  ```
+  $ echo "This is bar file" > bar.txt
+  $ cat Dockerfile_arg
+  FROM busybox
+  ARG foo
+  ADD ${foo}.txt .
+  RUN cat ${foo}.txt
+  $ sudo isula-build ctr-img build --build-arg foo=bar -f Dockerfile_arg
+  STEP  1: FROM busybox
+  Getting image source signatures
+  Copying blob sha256:8f52abd3da461b2c0c11fda7a1b53413f1a92320eb96525ddf92c0b5cde781ad
+  Copying config sha256:e4db68de4ff27c2adfea0c54bbb73a61a42f5b667c326de4d7d5b19ab71c6a3b
+  Writing manifest to image destinationStoring signatures
+  STEP  2: ARG foo
+  STEP  3: ADD ${foo}.txt .
+  STEP  4: RUN cat ${foo}.txt
+  This is bar file
+  Getting image source signatures
+  Copying blob sha256:6194458b07fcf01f1483d96cd6c34302ffff7f382bb151a6d023c4e80ba3050a
+  Copying blob sha256:6bb56e4a46f563b20542171b998cb4556af4745efc9516820eabee7a08b7b869
+  Copying config sha256:39b62a3342eed40b41a1bcd9cd455d77466550dfa0f0109af7a708c3e895f9a2
+  Writing manifest to image destination
+  Storing signatures
+  Build success with image id: 39b62a3342eed40b41a1bcd9cd455d77466550dfa0f0109af7a708c3e895f9a2
+  ```
+
+- **--build-static**
+
+  指定为静态构建，则isula-build会消除所有时间戳差异，同时消除其他构建过程差异，包括：容器ID、hsotname等, 最终构建出能满足BEP要求的容器镜像。
+
+  在使用isula-build进行容器镜像构建时，假如给 build 子命令一个固定的时间戳，并在限定如下条件的时候：
+
+  - 构建环境前后保持一致。
+  - 构建Dockerfile前后保持一致。
+  - 构建产生的中间数据前后保持一致。
+  - 构建命令相同。
+  - 第三方库版本一致。
+
+  对于容器镜像构建，isula-build支持相同的Dockerfile。如果构建环境相同，则多次构建生成的镜像内容和镜像ID相同。
+
+  --build-static接受k=v形式的键值对选项，当前支持的选项有：
+
+  - build-time：字符串类型。构建静态镜像的固定时间戳，格式为“YYYY-MM-DD HH-MM-SS”。时间戳影响diff层创建修改时间的文件属性。
+
+    使用示例如下：
+
+    ```sh
+    $ sudo isula-build ctr-img build -f Dockerfile --build-static='build-time=2020-05-23 10:55:33' .
+    ```
+
+    以此方式，同一环境多次构建出来的容器镜像和镜像ID均会保持一致。
+
+- **--iidfile**
+
+  将构建的镜像ID输出到文件，用法：
+
+  ```
+  isula-build ctr-img build --iidfile filename
+  ```
+  
+  使用示例如下：
+
+  ```sh
+  $ sudo isula-build ctr-img build -f Dockerfile_arg --iidfile testfile
+  
+  $ cat testfile
+  76cbeed38a8e716e22b68988a76410eaf83327963c3b29ff648296d5cd15ce7b
+  ```
+
+- **-o, --output**
+
+  目前 -o, --output 支持如下形式：
+
+  - `isulad:image:tag`：将构建成功的镜像直接推送到 iSulad。比如：`-o isulad:busybox:latest`。同时需要注意如下约束：
+    - isula-build 和 iSulad 必须在同一个节点上
+    - tag必须配置
+    - isula-build client端需要将构建成功的镜像暂存成 `/var/tmp/isula-build-tmp-%v.tar` 再导入至 iSulad，用户需要保证 `/var/tmp/` 目录有足够磁盘空间
+  - `docker-daemon:image:tag`：将构建成功的镜像直接推送到 Docker daemon。比如：`-o docker-daemon:busybox:latest`。同时需要注意如下约束：
+    - isula-build 和 docker 必须在同一个节点上
+    - tag必须配置
+  - `docker://registry.example.com/repository:tag`：将构建成功的镜像直接推送到远端镜像仓库。比如：`-o docker://localhost:5000/library/busybox:latest`。
+  - `docker-archive:/:image:tag`：将构建成功的镜像以Docker image的格式保存至本地。比如：`-o docker-archive:/root/image.tar:busybox:latest`。
+
+  除去各个flags之外，build子命令的命令行最后还会接收一个argument，该argument类型是string，意义为context，即该Dockerfile构建环境的上下文。该参数默认值为isula-build被执行的当前路径。该路径会影响 .dockerignore 和 Dockerfile的ADD/COPY指令 所检索的路径。
+
+- **--proxy**
+
+  选择构建时RUN指令启动的容器是否从环境上继承proxy相关环境变量"http_proxy","https_proxy","ftp_proxy","no_proxy","HTTP_PROXY","HTTPS_PROXY","FTP_PROXY","NO_PROXY"，默认为true。
+
+  当用户在Dockerfile配置proxy相关ARG或ENV，将覆盖所继承的环境变量。
+
+  注意：若client与daemon不在同一个终端运行，所能继承的环境变量为daemon所在终端的环境变量。
+
+- **--tag**
+
+  设置镜像构建成功之后，该镜像在本地磁盘存储时的tag。
+
+- **--cap-add**
+
+  添加构建过程中RUN指令所需权限，用法：
+
+  ```
+  isula-build ctr-img build --cap-add CAP_SYS_ADMIN --cap-add CAP_SYS_PTRACE -f Dockerfile
+  ```
+
+说明：
+
+isula-build最大支持并发构建100个容器镜像、支持Dockerfile最大1M、支持 .dockerignore 最大 1M
+
+##### image: 查看本地持久化构建镜像
+
+可通过images命令查看当前本地持久化存储的镜像：
+
+```sh
+$ sudo isula-build ctr-img images
+----------------------------------------------  -----------  -----------------  --------------------------  ------------ 
+REPOSITORY                                      TAG          IMAGE ID           CREATED                     SIZE
+----------------------------------------------  -----------  -----------------  --------------------------  ------------ 
+localhost:5000/library/alpine                   latest       a24bb4013296       2020-20-19 19:59:197        5.85 MB 
+                                                 39b62a3342ee       2020-20-38 38:66:387        1.45 MB
+----------------------------------------------  -----------  -----------------  --------------------------  ------------
+```
+
+##### import: 导入容器基础镜像
+
+openEuler会随版本发布一个容器基础镜像，比如openEuler-docker.x86_64.tar.xz。可以通过ctr-img import指令将它导入。
+
+命令原型如下：
+
+```
+isula-build ctr-img import [flags]
+```
+
+使用举例：
+
+```sh
+$ sudo isula-build ctr-img import ./openEuler-docker.x86_64.tar.xz openeuler:20.03
+Import success with image id: 7317851cd2ab33263eb293f68efee9d724780251e4e92c0fb76bf5d3c5585e37
+$ sudo isula-build ctr-img images
+----------------------------------------------  --------------------  -----------------  ------------------------  ------------ 
+REPOSITORY                                      TAG                   IMAGE ID           CREATED                   SIZE
+----------------------------------------------  --------------------  -----------------  ------------------------  ------------ 
+openeuler                                       20.03                 7317851cd2ab       2020-08-01 06:25:34       500 MB
+----------------------------------------------  --------------------  -----------------  ------------------------  ------------
+```
+
+说明：
+
+isula-build 支持导入最大1G的容器基础镜像
+
+##### load: 导入层叠镜像
+
+层叠镜像指的是通过 docker save 或 isula-build ctr-img save 等指令，将一个构建完成的镜像保存至本地之后，镜像压缩包内是一层一层 layer.tar 的镜像包。可以通过 ctr-img load 指令将它导入至 isula-build。
+
+命令原型如下：
+
+```
+isula-build ctr-img load [flags]
+```
+
+使用示例如下：
+
+```sh
+$ sudo isula-build ctr-img load -i ubuntu.tarGetting image source signatures
+Copying blob sha256:cf612f747e0fbcc1674f88712b7bc1cd8b91cf0be8f9e9771235169f139d507c
+Copying blob sha256:f934e33a54a60630267df295a5c232ceb15b2938ebb0476364192b1537449093
+Copying blob sha256:943edb549a8300092a714190dfe633341c0ffb483784c4fdfe884b9019f6a0b4
+Copying blob sha256:e7ebc6e16708285bee3917ae12bf8d172ee0d7684a7830751ab9a1c070e7a125
+Copying blob sha256:bf6751561805be7d07d66f6acb2a33e99cf0cc0a20f5fd5d94a3c7f8ae55c2a1
+Copying blob sha256:c1bd37d01c89de343d68867518b1155cb297d8e03942066ecb44ae8f46b608a3
+Copying blob sha256:a84e57b779297b72428fc7308e63d13b4df99140f78565be92fc9dbe03fc6e69
+Copying blob sha256:14dd68f4c7e23d6a2363c2320747ab88986dfd43ba0489d139eeac3ac75323b2
+Copying blob sha256:a2092d776649ea2301f60265f378a02405539a2a68093b2612792cc65d00d161
+Copying blob sha256:879119e879f682c04d0784c9ae7bc6f421e206b95d20b32ce1cb8a49bfdef202
+Copying blob sha256:e615448af51b848ecec00caeaffd1e30e8bf5cffd464747d159f80e346b7a150
+Copying blob sha256:f610bd1e9ac6aa9326d61713d552eeefef47d2bd49fc16140aa9bf3db38c30a4
+Copying blob sha256:bfe0a1336d031bf5ff3ce381e354be7b2bf310574cc0cd1949ad94dda020cd27
+Copying blob sha256:f0f15db85788c1260c6aa8ad225823f45c89700781c4c793361ac5fa58d204c7
+Copying config sha256:c07ddb44daa97e9e8d2d68316b296cc9343ab5f3d2babc5e6e03b80cd580478e
+Writing manifest to image destination
+Storing signatures
+Loaded image as c07ddb44daa97e9e8d2d68316b296cc9343ab5f3d2babc5e6e03b80cd580478e
+```
+
+说明：
+
+- isula-build load命令仅支持导入包含单个层叠镜像的镜像压缩文件
+- isula-build 支持导入最大50G的容器层叠镜像
+
+##### rm: 删除本地持久化镜像
+
+可通过rm命令删除当前本地持久化存储的镜像。命令原型为：
+
+```
+isula-build ctr-img rm IMAGE [IMAGE...] [FLAGS]
+```
+
+目前支持的 flags 为：
+
+- -a, --all：删除所有本地持久化存储的镜像。
+
+- -p, --prune：删除所有没有tag的本地持久化存储的镜像。
+
+使用示例如下：
+
+```sh
+$ sudo isula-build ctr-img rm -p
+Deleted: sha256:78731c1dde25361f539555edaf8f0b24132085b7cab6ecb90de63d72fa00c01d
+Deleted: sha256:eeba1bfe9fca569a894d525ed291bdaef389d28a88c288914c1a9db7261ad12c
+```
+
+##### save: 导出层叠镜像
+
+可通过save命令导出层叠镜像到本地磁盘。命令原型如下：
+
+```
+isula-build ctr-img save [REPOSITORY:TAG]|imageID -o xx.tar
+```
+
+以下示例通过 `image/tag` 的形式将镜像进行导出：
+
+```sh
+$ sudo isula-build ctr-img save busybox:latest -o busybox.tar
+Getting image source signatures
+Copying blob sha256:50644c29ef5a27c9a40c393a73ece2479de78325cae7d762ef3cdc19bf42dd0a
+Copying blob sha256:824082a6864774d5527bda0d3c7ebd5ddc349daadf2aa8f5f305b7a2e439806f
+Copying blob sha256:5f70bf18a086007016e948b04aed3b82103a36bea41755b6cddfaf10ace3c6ef
+Copying config sha256:21c3e96ac411242a0e876af269c0cbe9d071626bdfb7cc79bfa2ddb9f7a82db6
+Writing manifest to image destination
+Storing signatures
+Save success with image: busybox:latest
+```
+
+以下示例通过 `ImageID` 的形式将镜像进行导出：
+
+```sh
+$ sudo isula-build ctr-img save 21c3e96ac411 -o busybox.tar
+Getting image source signatures
+Copying blob sha256:50644c29ef5a27c9a40c393a73ece2479de78325cae7d762ef3cdc19bf42dd0a
+Copying blob sha256:824082a6864774d5527bda0d3c7ebd5ddc349daadf2aa8f5f305b7a2e439806f
+Copying blob sha256:5f70bf18a086007016e948b04aed3b82103a36bea41755b6cddfaf10ace3c6ef
+Copying config sha256:21c3e96ac411242a0e876af269c0cbe9d071626bdfb7cc79bfa2ddb9f7a82db6
+Writing manifest to image destination
+Storing signatures
+Save success with image: 21c3e96ac411
+```
+
+#### info: 查看运行环境与系统信息
+
+可以通过“isula-build info”指令查看 isula-build 目前的运行环境与系统信息。命令原型如下：
+
+```
+isula-build info [flags]
+```
+
+支持如下Flags：
+
+- -H, --human-readable  布尔值，以常用内存表示格式打印内存信息，使用1000次幂
+
+使用示例：
+
+```sh
+  $ sudo 
+  isula-build info -H
+  General:  
+    MemTotal:     7.63 GB  
+    MemFree:      757 MB  
+    SwapTotal:    8.3 GB  
+    SwapFree:     8.25 GB  
+    OCI Runtime:  runc  
+    DataRoot:     /var/lib/isula-build/  
+    RunRoot:      /var/run/isula-build/  
+    Builders:     0  
+    Goroutines:   12
+  Store:  
+    Storage Driver:     overlay  
+    Backing Filesystem: extfs
+  Registry:  
+    Search Registries:   
+      oepkgs.net
+    Insecure Registries:    
+      localhost:5000    
+      oepkgs.net
+```
+
+#### login: 登录远端镜像仓库
+
+用户可以运行 login 命令来登录远程镜像仓库。命令原型如下：
+
+```
+isula-build login SERVER [FLAGS]
+```
+
+目前支持的flag有：
+
+```
+Flags:  
+  -p, --password-stdin    Read password from stdin  
+  -u, --username string   Username to access registry
+```
+
+通过stdin输入密码：
+
+```sh
+$ cat creds.txt | sudo isula-build login -u cooper -p mydockerhub.io
+Login Succeeded
+```
+
+通过交互式输入密码：
+
+```sh
+$ sudo isula-build login mydockerhub.io -u cooper
+Password:
+Login Succeeded
+```
+
+#### logout: 退出远端镜像仓库
+
+用户可以运行 logout 命令来登出远程镜像仓库。命令原型如下：
+
+```
+isula-build logout [SERVER] [FLAGS]
+```
+
+目前支持的flag有：
+
+```
+Flags:  
+  -a, --all   Logout all registries
+```
+
+使用示例如下：
+
+```sh
+$ sudo isula-build logout -a  
+  Removed authentications
+```
+
+#### version: 版本查询
+
+可通过version命令查看当前版本信息：
+
+```sh
+$ sudo isula-build version
+Client:
+  Version:       0.9.2
+  Go Version:    go1.13.3
+  Git Commit:    ccb2a13
+  Built:         Sat Aug 22 08:06:47 2020
+  OS/Arch:       linux/amd64
+
+Server:
+  Version:       0.9.2
+  Go Version:    go1.13.3
+  Git Commit:    ccb2a13
+  Built:         Sat Aug 22 08:06:47 2020
+  OS/Arch:       linux/amd64
+```
+
+
+
+说明：
+
+isula-build completion 和 isula-builder completion 命令用于生成bash命令补全脚本。该命令为命令行框架隐式提供，不会显示在help信息中。
+
+
+
+### 直接集成容器引擎
+
+isula-build可以与iSulad和docker集成，将构建好的容器镜像导入到容器引擎的本地存储中。
+
+#### 与iSulad集成
+
+支持将构建成功的镜像直接导出到iSulad。命令行举例：
+
+```sh
+$ sudo isula-build ctr-img build -f Dockerfile -o isulad:busybox:2.0
+```
+
+通过在-o参数中指定iSulad，将构建好的容器镜像导出到iSulad，可以通过isula images查询。
+
+说明：
+
+要求isula-build和iSulad在同一节点。
+
+#### 与Docker集成
+
+支持将构建成功的镜像直接导出到Docker daemon。命令行举例：
+
+```sh
+$ sudo isula-build ctr-img build -f Dockerfile -o docker-daemon:busybox:2.0
+```
+
+通过在-o参数中指定docker-daemon，将构建好的容器镜像导出到docker, 可以通过docker images查询。
+
+说明：
+
+要求isula-build和Docker在同一节点。
+
+
+
+## 使用注意事项
+
+本章节主要介绍在使用 isula-build 工具时相关的约束和限制，以及与 docker 相关指令上的行为差异。
+
+### 约束和限制
+
+1. 直接导出镜像到iSulad或docker daemon时，必须指定tag。
+2. 直接导出镜像到iSulad时，isula-build client端需要将构建成功的镜像暂存成 `/var/tmp/isula-build-tmp-%v.tar` 再导入至 iSulad，用户需要保证 /var/tmp/ 目录有足够磁盘空间；同时如果在导出过程中 isula-build client进程被KILL或Ctrl+C终止，需要依赖用户手动清理 `/var/tmp/isula-build-tmp-%v.tar` 文件。
+3. 用户需保证OCI runtime(runc)可执行文件的安全性，避免被恶意替换。
+4. isula-build不支持将持久化工作目录dataroot配置在内存盘上，比如tmpfs。
+5. isula-build目前仅支持使用overlay2为底层graphdriver。
+6. isula-build当前仅支持Docker镜像。
+7. 用户需保证Dockerfile文件的权限为仅当前用户可读写，避免别的用户进行篡改。
+8. 目前仅支持使用主机网络。
+9. 导出的镜像压缩格式，目前仅支持tar.gz格式。
+10. stage name不能以数字开头、stage name的长度限制为64个字符
+
+### 与docker差异
+
+- isula-build 兼容 dockerfile 语法，但与 docker build 所支持的指令和构建行为相比，存在如下差异：
+  - isula-build 在每一个镜像构建stage完成后做一次提交，而不是每执行 Dockerfile的一行就提交一次。
+  - isula-build 暂不支持构建缓存。
+  - isula-build 仅在构建RUN指令时会启动构建容器。
+  - 目前不支持docker镜像格式的history功能。
+  - isula-build 的stage name支持以数字开头。
+  - isula-build 的stage name最长可为64个字符。
+  - isula-build 暂不支持对单次Dockerfile的构建进行资源限制。如有资源限制需求，可通过对 isula-builder 服务端配置资源限额的方式进行限制。
+- isula-build 与 docker 其它指令的差异如下：
+  - 通过`isula-build ctr-img images`查看的镜像大小与`docker images`的显示上有一定差异。这是因为统计镜像大小时，isula-build是直接计算每层tar包大小之和，而docker是通过解压tar遍历diff目录计算文件大小之和，因此存在统计上的差异。
+
+### 与Dockerfile语法上的差异
+
+- isula-build 目前不支持Dockerfile里的ADD指令提供的数据来源是远端url。
+
+   
+  
+
+## 附录
+
+### 命令行参数说明
+
+**表1** ctr-img build 命令参数列表
+
+| **命令**      | **参数**       | **说明**                                                     |
+| ------------- | -------------- | ------------------------------------------------------------ |
+| ctr-img build | --build-arg    | string列表，构建过程中需要用到的变量                         |
+|               | --build-static | KV值，构建二进制一致性。目前包含如下K值：- build-time：string，使用固定时间戳来构建容器镜像；时间戳格式为“YYYY-MM-DD HH-MM-SS” |
+|               | -f, --filename | string，Dockerfile的路径，不指定则是使用当前路径的Dockerfile文件 |
+|               | --iidfile      | string，输出 image ID 到本地文件                             |
+|               | -o, --output   | string，镜像导出的方式和路径                                 |
+|               | --proxy        | 布尔值，继承主机侧环境的proxy环境变量（默认为true）          |
+|               | --tag          | string，给构建的镜像添加tag                                  |
+|               | --cap-add      | string列表，构建过程中RUN指令所需要的权限                    |
+
+**表2** ctr-img load 命令参数列表
+
+| **命令**     | **参数**    | **说明**                          |
+| ------------ | ----------- | --------------------------------- |
+| ctr-img load | -i, --input | string，需要导入的本地tar包的路径 |
+
+**表3** ctr-img rm 命令参数列表
+
+| **命令**   | **参数**    | **说明**                                      |
+| ---------- | ----------- | --------------------------------------------- |
+| ctr-img rm | -a, --all   | 布尔值，删除所有本地持久化存储的镜像          |
+|            | -p, --prune | 布尔值，删除所有没有tag的本地持久化存储的镜像 |
+
+**表4** ctr-img save 命令参数列表
+
+| **命令**     | **参数**     | **说明**                           |
+| ------------ | ------------ | ---------------------------------- |
+| ctr-img save | -o, --output | string，镜像导出后在本地的存储路径 |
+
+**表5** login 命令参数列表
+
+| **命令** | **参数**             | **说明**                                                |
+| -------- | -------------------- | ------------------------------------------------------- |
+| login    | -p, --password-stdin | 布尔值，是否通过stdin读入密码；或采用交互式界面输入密码 |
+|          | -u, --username       | string，登陆镜像仓库所使用的用户名                      |
+
+**表6** logout 命令参数列表
+
+| **命令** | **参数**  | **说明**                             |
+| -------- | --------- | ------------------------------------ |
+| logout   | -a, --all | 布尔值，是否登出所有已登陆的镜像仓库 |
+
+### 通信矩阵
+
+isula-build两个组件进程之间通过unix socket套接字文件进行通信，无端口通信。
+
+### 文件与权限
+
+- isula-build 所有的操作均需要使用 root 权限。
+
+
+   
diff --git "a/content/zh/docs/Container/namespace\345\214\226\345\206\205\346\240\270\345\217\202\346\225\260\345\217\257\345\206\231.md" "b/docs/zh/docs/20.03_LTS/docs/Container/namespace\345\214\226\345\206\205\346\240\270\345\217\202\346\225\260\345\217\257\345\206\231.md"
similarity index 99%
rename from "content/zh/docs/Container/namespace\345\214\226\345\206\205\346\240\270\345\217\202\346\225\260\345\217\257\345\206\231.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/namespace\345\214\226\345\206\205\346\240\270\345\217\202\346\225\260\345\217\257\345\206\231.md"
index ab34a713fb0b997cc055fbade3220571e13ffcca..74e4f950a65614579fc534ab9ce57d77fcbce2d9 100644
--- "a/content/zh/docs/Container/namespace\345\214\226\345\206\205\346\240\270\345\217\202\346\225\260\345\217\257\345\206\231.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/namespace\345\214\226\345\206\205\346\240\270\345\217\202\346\225\260\345\217\257\345\206\231.md"
@@ -1,20 +1,20 @@
-# namespace化内核参数可写
-
-## 功能描述
-
-对于运行在容器内的业务，如数据库，大数据，包括普通应用，有对部分内核参数进行设置和调整的需求，以满足最佳的业务运行性能和可靠性。内核参数要么不允许修改，要么全部允许修改（特权容器）：
-
-在不允许用户在容器内修改时，只提供了--sysctl外部接口，而且容器内不能灵活修改参数值。
-
-在允许用户在容器内修改时，部分内核参数是全局有效的，某个容器修改后，会影响主机上所有的程序，安全性降低。
-
-  
-
-系统容器提供--ns-change-opt参数，可以指定namespace化的内核参数在容器内动态设置，当前仅支持net、ipc。
-
-## 参数说明
-
-
+# namespace化内核参数可写
+
+## 功能描述
+
+对于运行在容器内的业务，如数据库，大数据，包括普通应用，有对部分内核参数进行设置和调整的需求，以满足最佳的业务运行性能和可靠性。内核参数要么不允许修改，要么全部允许修改（特权容器）：
+
+在不允许用户在容器内修改时，只提供了--sysctl外部接口，而且容器内不能灵活修改参数值。
+
+在允许用户在容器内修改时，部分内核参数是全局有效的，某个容器修改后，会影响主机上所有的程序，安全性降低。
+
+  
+
+系统容器提供--ns-change-opt参数，可以指定namespace化的内核参数在容器内动态设置，当前仅支持net、ipc。
+
+## 参数说明
+
+
 
-
命令

 		
 
参数

@@ -46,45 +46,45 @@
 
 

 

-
-## 约束限制
-
--   如果容器启动同时指定了--privileged（特权容器）和--ns-change-opt，则--ns-change-opt不生效。
-
-## 使用示例
-
-启动容器， 指定--ns-change-opt=net：
-
-```
-[root@localhost ~]# isula run -tid --ns-change-opt net --system-container --external-rootfs /root/myrootfs none init
-4bf44a42b4a14fdaf127616c90defa64b4b532b18efd15b62a71cbf99ebc12d2
-[root@localhost ~]# isula exec -it 4b mount | grep /proc/sys
-proc on /proc/sys type proc (ro,nosuid,nodev,noexec,relatime)
-proc on /proc/sysrq-trigger type proc (ro,nosuid,nodev,noexec,relatime)
-proc on /proc/sys/net type proc (rw,nosuid,nodev,noexec,relatime)
-```
-
-可以看到容器内/proc/sys/net挂载点为rw，说明net相关的namespace化的内核参数具有读写权限。
-
-再启动一个容器，指定--ns-change-opt=ipc：
-
-```
-[root@localhost ~]# isula run -tid --ns-change-opt ipc --system-container --external-rootfs /root/myrootfs none init
-c62e5e5686d390500dab2fa76b6c44f5f8da383a4cbbeac12cfada1b07d6c47f
-[root@localhost ~]# isula exec -it c6 mount | grep /proc/sys
-proc on /proc/sys type proc (ro,nosuid,nodev,noexec,relatime)
-proc on /proc/sysrq-trigger type proc (ro,nosuid,nodev,noexec,relatime)
-proc on /proc/sys/kernel/shmmax type proc (rw,nosuid,nodev,noexec,relatime)
-proc on /proc/sys/kernel/shmmni type proc (rw,nosuid,nodev,noexec,relatime)
-proc on /proc/sys/kernel/shmall type proc (rw,nosuid,nodev,noexec,relatime)
-proc on /proc/sys/kernel/shm_rmid_forced type proc (rw,nosuid,nodev,noexec,relatime)
-proc on /proc/sys/kernel/msgmax type proc (rw,nosuid,nodev,noexec,relatime)
-proc on /proc/sys/kernel/msgmni type proc (rw,nosuid,nodev,noexec,relatime)
-proc on /proc/sys/kernel/msgmnb type proc (rw,nosuid,nodev,noexec,relatime)
-proc on /proc/sys/kernel/sem type proc (rw,nosuid,nodev,noexec,relatime)
-proc on /proc/sys/fs/mqueue type proc (rw,nosuid,nodev,noexec,relatime)
-```
-
-可以看到容器内ipc相关的内核参数挂载点为rw，说明ipc相关的namespace化的内核参数具有读写权限。
-
+
+
+## 约束限制
+
+-   如果容器启动同时指定了--privileged（特权容器）和--ns-change-opt，则--ns-change-opt不生效。
+
+## 使用示例
+
+启动容器， 指定--ns-change-opt=net：
+
+```
+[root@localhost ~]# isula run -tid --ns-change-opt net --system-container --external-rootfs /root/myrootfs none init
+4bf44a42b4a14fdaf127616c90defa64b4b532b18efd15b62a71cbf99ebc12d2
+[root@localhost ~]# isula exec -it 4b mount | grep /proc/sys
+proc on /proc/sys type proc (ro,nosuid,nodev,noexec,relatime)
+proc on /proc/sysrq-trigger type proc (ro,nosuid,nodev,noexec,relatime)
+proc on /proc/sys/net type proc (rw,nosuid,nodev,noexec,relatime)
+```
+
+可以看到容器内/proc/sys/net挂载点为rw，说明net相关的namespace化的内核参数具有读写权限。
+
+再启动一个容器，指定--ns-change-opt=ipc：
+
+```
+[root@localhost ~]# isula run -tid --ns-change-opt ipc --system-container --external-rootfs /root/myrootfs none init
+c62e5e5686d390500dab2fa76b6c44f5f8da383a4cbbeac12cfada1b07d6c47f
+[root@localhost ~]# isula exec -it c6 mount | grep /proc/sys
+proc on /proc/sys type proc (ro,nosuid,nodev,noexec,relatime)
+proc on /proc/sysrq-trigger type proc (ro,nosuid,nodev,noexec,relatime)
+proc on /proc/sys/kernel/shmmax type proc (rw,nosuid,nodev,noexec,relatime)
+proc on /proc/sys/kernel/shmmni type proc (rw,nosuid,nodev,noexec,relatime)
+proc on /proc/sys/kernel/shmall type proc (rw,nosuid,nodev,noexec,relatime)
+proc on /proc/sys/kernel/shm_rmid_forced type proc (rw,nosuid,nodev,noexec,relatime)
+proc on /proc/sys/kernel/msgmax type proc (rw,nosuid,nodev,noexec,relatime)
+proc on /proc/sys/kernel/msgmni type proc (rw,nosuid,nodev,noexec,relatime)
+proc on /proc/sys/kernel/msgmnb type proc (rw,nosuid,nodev,noexec,relatime)
+proc on /proc/sys/kernel/sem type proc (rw,nosuid,nodev,noexec,relatime)
+proc on /proc/sys/fs/mqueue type proc (rw,nosuid,nodev,noexec,relatime)
+```
+
+可以看到容器内ipc相关的内核参数挂载点为rw，说明ipc相关的namespace化的内核参数具有读写权限。
+
diff --git a/content/zh/docs/Container/public_sys-resources/icon-caution.gif b/docs/zh/docs/20.03_LTS/docs/Container/public_sys-resources/icon-caution.gif
similarity index 100%
rename from content/zh/docs/Container/public_sys-resources/icon-caution.gif
rename to docs/zh/docs/20.03_LTS/docs/Container/public_sys-resources/icon-caution.gif
diff --git a/content/zh/docs/Container/public_sys-resources/icon-danger.gif b/docs/zh/docs/20.03_LTS/docs/Container/public_sys-resources/icon-danger.gif
similarity index 100%
rename from content/zh/docs/Container/public_sys-resources/icon-danger.gif
rename to docs/zh/docs/20.03_LTS/docs/Container/public_sys-resources/icon-danger.gif
diff --git a/content/zh/docs/Container/public_sys-resources/icon-note.gif b/docs/zh/docs/20.03_LTS/docs/Container/public_sys-resources/icon-note.gif
similarity index 100%
rename from content/zh/docs/Container/public_sys-resources/icon-note.gif
rename to docs/zh/docs/20.03_LTS/docs/Container/public_sys-resources/icon-note.gif
diff --git a/content/zh/docs/Container/public_sys-resources/icon-notice.gif b/docs/zh/docs/20.03_LTS/docs/Container/public_sys-resources/icon-notice.gif
similarity index 100%
rename from content/zh/docs/Container/public_sys-resources/icon-notice.gif
rename to docs/zh/docs/20.03_LTS/docs/Container/public_sys-resources/icon-notice.gif
diff --git a/content/zh/docs/Container/public_sys-resources/icon-tip.gif b/docs/zh/docs/20.03_LTS/docs/Container/public_sys-resources/icon-tip.gif
similarity index 100%
rename from content/zh/docs/Container/public_sys-resources/icon-tip.gif
rename to docs/zh/docs/20.03_LTS/docs/Container/public_sys-resources/icon-tip.gif
diff --git a/content/zh/docs/Container/public_sys-resources/icon-warning.gif b/docs/zh/docs/20.03_LTS/docs/Container/public_sys-resources/icon-warning.gif
similarity index 100%
rename from content/zh/docs/Container/public_sys-resources/icon-warning.gif
rename to docs/zh/docs/20.03_LTS/docs/Container/public_sys-resources/icon-warning.gif
diff --git "a/content/zh/docs/Container/\344\270\272\345\256\211\345\205\250\345\256\271\345\231\250\351\205\215\347\275\256\347\275\221\347\273\234.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\344\270\272\345\256\211\345\205\250\345\256\271\345\231\250\351\205\215\347\275\256\347\275\221\347\273\234.md"
similarity index 96%
rename from "content/zh/docs/Container/\344\270\272\345\256\211\345\205\250\345\256\271\345\231\250\351\205\215\347\275\256\347\275\221\347\273\234.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\344\270\272\345\256\211\345\205\250\345\256\271\345\231\250\351\205\215\347\275\256\347\275\221\347\273\234.md"
index e6b1cc316d0cb8ee4a113f020bc45630a3bf9c65..4e744a60c5f1b6a1a0cf15e22adee35e52e97697 100644
--- "a/content/zh/docs/Container/\344\270\272\345\256\211\345\205\250\345\256\271\345\231\250\351\205\215\347\275\256\347\275\221\347\273\234.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\344\270\272\345\256\211\345\205\250\345\256\271\345\231\250\351\205\215\347\275\256\347\275\221\347\273\234.md"
@@ -46,7 +46,7 @@
     
     
必选

     
-    
设置网卡的主机端名字。支持字母、数字、下划线“_”、“-” 以及“.”字符，必须以字母开头，且长度不超过15。需要确保同一个宿主机上device不能重复。

+    
设置网卡的主机端名字。支持字母、数字、下划线“\_”、“-” 以及“.”字符，必须以字母开头，且长度不超过15。需要确保同一个宿主机上device不能重复。

     
     
     
name

@@ -114,7 +114,7 @@
         null
         ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >当网卡添加成功时，如果为其指定了IP地址，则kata会为新添加的网卡添加一条destination为同网段地址的默认路由，如上例中添加网卡之后容器内有如下路由被添加：  
     >```  
     >[root@6ec7a98 /]# ip route  
@@ -194,7 +194,7 @@
     -   gateway：设置路由的下一跳网关。设置"dest":"default"时，gateway必选；其他情况可选。
     -   device：必选。设置路由对应的网卡名称，最长支持15字符。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >如果为容器内的回环设备lo添加路由时，路由配置文件中的"device"字段对应的设备名称为"lo"。  
 
 4.  **删除指定路由**
@@ -225,7 +225,7 @@
         null
         ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >-   输入字段中dest为必选，device/gateway均为可选。kata根据不同字段进行模糊匹配，删除对应的路由规则。例如指定了dest为某个IP，则所有该IP的规则都会被删除。  
     >-   如果删除的是容器内回环设备lo的路由时，路由配置文件中的"device"字段对应的设备名称为"lo"。  
 
@@ -235,7 +235,7 @@
     $ cat ./test-iface.json | kata-runtime kata-network del-iface 6ec7a98 -
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >删除网卡时，仅根据网卡容器内名称（name字段）来删除。即便填写其他字段，kata也不会使用。  
 
     kata-runtime kata-network del-iface删除网卡命令执行返回结果说明：
@@ -314,7 +314,7 @@
     kata-runtime kata-ipvs ipvsadm --restore -  <  <规则文件路径> 
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >单条添加时默认使用NAT模式，批量导入时添加真实服务器需手动添加-m参数使用NAT模式。  
     >规则文件内容示例：  
     >-A -t 10.10.11.12:100 -s rr -p  3000  
@@ -334,7 +334,7 @@
     kata-runtime kata-ipvs ipvsadm --parameters "--set 100 100 200" 
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >1.  每个容器支持iptables规则数量最大为20000条（5k service，3个server/service），add-service和add-server都算作规则。  
     >2.  批量导入前需清空已有规则。  
     >3.  不存在并发测试场景。  
diff --git "a/content/zh/docs/Container/\344\270\272\345\256\211\345\205\250\345\256\271\345\231\250\351\205\215\347\275\256\350\265\204\346\272\220.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\344\270\272\345\256\211\345\205\250\345\256\271\345\231\250\351\205\215\347\275\256\350\265\204\346\272\220.md"
similarity index 98%
rename from "content/zh/docs/Container/\344\270\272\345\256\211\345\205\250\345\256\271\345\231\250\351\205\215\347\275\256\350\265\204\346\272\220.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\344\270\272\345\256\211\345\205\250\345\256\271\345\231\250\351\205\215\347\275\256\350\265\204\346\272\220.md"
index 55aa35dfaaefe14d7d0afc5507bf98745601f98e..f0856085a8c84257048b870cd811577390165ec4 100644
--- "a/content/zh/docs/Container/\344\270\272\345\256\211\345\205\250\345\256\271\345\231\250\351\205\215\347\275\256\350\265\204\346\272\220.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\344\270\272\345\256\211\345\205\250\345\256\271\345\231\250\351\205\215\347\275\256\350\265\204\346\272\220.md"
@@ -45,7 +45,7 @@
     Socket(s):           4
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >CPU个数可以设置的最大值为当前OS上可供运行的CPU值（除去隔离核），最小值为0.5个CPU。  
 
 2.  配置容器CPU运行资源
@@ -98,7 +98,7 @@
 
 3.  配置CPU热插拔功能
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >安全容器CPU热插拔功能需要虚拟化组件qemu支持CPU热插拔。  
 
     kata-runtime配置文件config.toml中**enable\_cpu\_memory\_hotplug**选项负责开启和禁用CPU和内存热插拔。默认取值为false，表示禁用CPU和内存热插拔功能；取值为true，表示开启CPU和内存热插拔功能。
@@ -157,7 +157,7 @@
 
       
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >由于pause容器只是一个占位容器没有工作负载，所以轻量级虚机启动时默认分配的1个CPU可以被其它容器共享，因此上面例子中启动的新容器只需要再热插3个CPU到轻量级虚机中即可。  
 
     -   当停止热插了CPU的容器后，启动容器时热插进去的CPU也会被拔出。
@@ -187,7 +187,7 @@
     Swap:             0           0           0
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >-   如果没有通过--annotation com.github.containers.virtcontainers.sandbox\_mem显示地设置轻量级虚机的内存大小，则轻量级虚机默认使用的内存大小为1GB。  
     >-   安全容器一个Pod的最小内存规格是1GB，支持的最大内存规格是256GB。如果用户分配的内存规格超过256GB，可能会出现未定义的错误，安全容器暂不支持超过256GB的大内存场景。  
 
@@ -216,7 +216,7 @@
 
     同配置CPU热插拔功能一样，MEM的热插功能也是由kata-runtime配置文件config.toml中**enable\_cpu\_memory\_hotplug**选项配置，用法参见[3](#限制CPU资源.md#zh-cn_topic_0183903699_li2167326144011)。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >内存资源当前只支持热插，不支持内存热拔。  
 
     kata-runtime中复用了**-m**选项实现了MEM热插的功能，通过统计Pod中所有容器的**-m**选项的和，然后确定需要热插多少内存到轻量级虚机中，例如，
@@ -255,7 +255,7 @@
     Swap:             0           0           0
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >由于pause容器只是一个占位容器没有工作负载，所以轻量级虚机启动时分配的内存可以被其它容器共享使用，因此上面例子中启动的新容器只需要再热插3GB的内存到轻量级虚机中即可。  
 
 
@@ -334,7 +334,7 @@
 docker run -tid --runtime kata-runtime --network none --annotation io.kubernetes.docker.type=podsandbox --files-limit   bash
 ```
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >-   如果**--files-limit**选项的取值小于安全容器默认设置的最小值1024且不为0时，安全容器qemu进程最多可以打开的文件描述符数量会被设置为最小值1024。  
 >-   如果**--files-limit**选项的取值为0时，安全容器qemu进程最多可以打开的文件描述符数量为系统可以打开文件描述符的最大值/proc/sys/fs/file-max除以400后得到的默认值。  
 >-   如果启动安全容器时没有显示指定**--files-limit**可以打开的文件描述符的上限，安全容器qemu进程可以打开的文件描述符数量的上限和系统默认值保持一致。  
diff --git "a/content/zh/docs/Container/\344\275\277\347\224\250\346\214\207\345\215\227-1.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\344\275\277\347\224\250\346\214\207\345\215\227-1.md"
similarity index 93%
rename from "content/zh/docs/Container/\344\275\277\347\224\250\346\214\207\345\215\227-1.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\344\275\277\347\224\250\346\214\207\345\215\227-1.md"
index 2efb60fa790ddcf4c7b4d56646680ff91db30cd6..36943fc57b1829a1629916b8d7f691d4a76f6b66 100644
--- "a/content/zh/docs/Container/\344\275\277\347\224\250\346\214\207\345\215\227-1.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\344\275\277\347\224\250\346\214\207\345\215\227-1.md"
@@ -16,5 +16,5 @@ isula create/run [OPTIONS] [COMMAND] [ARG...]
 -   COMMAND：系统容器启动后执行的命令。
 -   ARG：系统容器启动后执行命令对应的参数。
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >系统容器的使用需要root权限。 
diff --git "a/content/zh/docs/Container/\344\275\277\347\224\250\346\214\207\345\215\227.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\344\275\277\347\224\250\346\214\207\345\215\227.md"
similarity index 94%
rename from "content/zh/docs/Container/\344\275\277\347\224\250\346\214\207\345\215\227.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\344\275\277\347\224\250\346\214\207\345\215\227.md"
index 204d1b97fd50e5fbcfe66866410676bff526c889..a4caa9131f31b3532b9c9c2c34726a07405941ea 100644
--- "a/content/zh/docs/Container/\344\275\277\347\224\250\346\214\207\345\215\227.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\344\275\277\347\224\250\346\214\207\345\215\227.md"
@@ -1,18 +1,18 @@
-# 使用指南
-
-本章介绍iSula容器引擎的使用方法。
->![](public_sys-resources/icon-note.gif) **说明：**
->iSulad的所有使用操作均需要使用root权限。
-
-
-- [容器管理](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E5%AE%B9%E5%99%A8%E7%AE%A1%E7%90%86.html)
-- [支持CNI网络](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E6%94%AF%E6%8C%81CNI%E7%BD%91%E7%BB%9C.html)
-- [容器资源管理](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E5%AE%B9%E5%99%A8%E8%B5%84%E6%BA%90%E7%AE%A1%E7%90%86.html)
-- [特权容器](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E7%89%B9%E6%9D%83%E5%AE%B9%E5%99%A8.html)
-- [CRI接口](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/CRI%E6%8E%A5%E5%8F%A3.html)
-- [镜像管理](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E9%95%9C%E5%83%8F%E7%AE%A1%E7%90%86.html)
-- [容器健康状态检查](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E5%AE%B9%E5%99%A8%E5%81%A5%E5%BA%B7%E7%8A%B6%E6%80%81%E6%A3%80%E6%9F%A5.html)
-- [查询信息](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E6%9F%A5%E8%AF%A2%E4%BF%A1%E6%81%AF.html)
-- [安全特性](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E5%AE%89%E5%85%A8%E7%89%B9%E6%80%A7.html)
-- [支持OCI hooks](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E6%94%AF%E6%8C%81OCI-hooks.html)
-
+# 使用指南
+
+本章介绍iSula容器引擎的使用方法。
+>![](./public_sys-resources/icon-note.gif) **说明：**
+>iSulad的所有使用操作均需要使用root权限。
+
+
+- [容器管理](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E5%AE%B9%E5%99%A8%E7%AE%A1%E7%90%86.html)
+- [支持CNI网络](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E6%94%AF%E6%8C%81CNI%E7%BD%91%E7%BB%9C.html)
+- [容器资源管理](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E5%AE%B9%E5%99%A8%E8%B5%84%E6%BA%90%E7%AE%A1%E7%90%86.html)
+- [特权容器](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E7%89%B9%E6%9D%83%E5%AE%B9%E5%99%A8.html)
+- [CRI接口](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/CRI%E6%8E%A5%E5%8F%A3.html)
+- [镜像管理](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E9%95%9C%E5%83%8F%E7%AE%A1%E7%90%86.html)
+- [容器健康状态检查](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E5%AE%B9%E5%99%A8%E5%81%A5%E5%BA%B7%E7%8A%B6%E6%80%81%E6%A3%80%E6%9F%A5.html)
+- [查询信息](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E6%9F%A5%E8%AF%A2%E4%BF%A1%E6%81%AF.html)
+- [安全特性](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E5%AE%89%E5%85%A8%E7%89%B9%E6%80%A7.html)
+- [支持OCI hooks](https://openeuler.org/zh/docs/20.03_LTS/docs/Container/%E6%94%AF%E6%8C%81OCI-hooks.html)
+
diff --git "a/content/zh/docs/Container/\344\275\277\347\224\250\346\226\271\346\263\225-1.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\344\275\277\347\224\250\346\226\271\346\263\225-1.md"
similarity index 63%
rename from "content/zh/docs/Container/\344\275\277\347\224\250\346\226\271\346\263\225-1.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\344\275\277\347\224\250\346\226\271\346\263\225-1.md"
index 3df844abdc6d73e07372440ee141020c273a2c03..d72a36cfbb143542b48c4ae537063aa86b74aad7 100644
--- "a/content/zh/docs/Container/\344\275\277\347\224\250\346\226\271\346\263\225-1.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\344\275\277\347\224\250\346\226\271\346\263\225-1.md"
@@ -1,6 +1,6 @@
 # 使用方法
 
 本章介绍安全容器的使用方法。
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >安全容器的使用需要root权限。 
 
diff --git "a/content/zh/docs/Container/\345\205\261\344\272\253\345\206\205\345\255\230\351\200\232\351\201\223.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\205\261\344\272\253\345\206\205\345\255\230\351\200\232\351\201\223.md"
similarity index 98%
rename from "content/zh/docs/Container/\345\205\261\344\272\253\345\206\205\345\255\230\351\200\232\351\201\223.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\205\261\344\272\253\345\206\205\345\255\230\351\200\232\351\201\223.md"
index 159542efcb7f7bec800d96159ec79e41909892fc..ec3b77a3bb5c4264a83d3321ab7d58555bff8718 100644
--- "a/content/zh/docs/Container/\345\205\261\344\272\253\345\206\205\345\255\230\351\200\232\351\201\223.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\345\205\261\344\272\253\345\206\205\345\255\230\351\200\232\351\201\223.md"
@@ -1,12 +1,12 @@
-# 共享内存通道
-
-## 功能描述
-
-系统容器提供容器与主机进程通过共享内存进行通信的功能，通过在容器创建时配置\--host-channel参数，可以在容器与主机之间共享同一tmpfs，从而达到主机与容器间通信的功能。
-
-## 参数说明
-
-
+# 共享内存通道
+
+## 功能描述
+
+系统容器提供容器与主机进程通过共享内存进行通信的功能，通过在容器创建时配置\--host-channel参数，可以在容器与主机之间共享同一tmpfs，从而达到主机与容器间通信的功能。
+
+## 参数说明
+
+
 
-
命令

 		
 
参数

@@ -28,29 +28,29 @@
 
 

 

-
-## 约束限制
-
--   宿主机上挂载的tmpfs的生命周期为从容器启动到容器删除，容器删除并解除对空间的占用后会移除这片空间。
--   容器删除时会将宿主机上挂载tmpfs的路径删除，所以不允许使用宿主机上已存在的目录。
--   为了宿主机上非root用户运行的进程能够与容器内进行通信，宿主机上tmpfs挂载的权限为1777。
-
-## 使用示例
-
-创建容器时指定\--host-channel参数：
-
-```
-[root@localhost ~]# isula run --rm -it --host-channel /testdir:/testdir:rw:32M --system-container --external-rootfs /root/myrootfs none init 
-root@3b947668eb54:/# dd if=/dev/zero of=/testdir/test.file bs=1024 count=64K 
-dd: error writing '/testdir/test.file': No space left on device 
-32769+0 records in 
-32768+0 records out 
-33554432 bytes (34 MB, 32 MiB) copied, 0.0766899 s, 438 MB/s
-```
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->-   使用--host-channel大小限制时，若在容器内创建共享文件，则会受到容器内的内存配额限制（在容器内存使用达到极限时可能会产生oom）。  
->-   若用户在主机端创建共享文件，则不受容器内的内存配额限制。  
->-   若用户需要在容器内创建共享文件，且业务为内存密集型，可以通过设置容器内存配额为在原本基础上加上--host-channel配置的大小来消除影响。  
-
+
+
+## 约束限制
+
+-   宿主机上挂载的tmpfs的生命周期为从容器启动到容器删除，容器删除并解除对空间的占用后会移除这片空间。
+-   容器删除时会将宿主机上挂载tmpfs的路径删除，所以不允许使用宿主机上已存在的目录。
+-   为了宿主机上非root用户运行的进程能够与容器内进行通信，宿主机上tmpfs挂载的权限为1777。
+
+## 使用示例
+
+创建容器时指定\--host-channel参数：
+
+```
+[root@localhost ~]# isula run --rm -it --host-channel /testdir:/testdir:rw:32M --system-container --external-rootfs /root/myrootfs none init 
+root@3b947668eb54:/# dd if=/dev/zero of=/testdir/test.file bs=1024 count=64K 
+dd: error writing '/testdir/test.file': No space left on device 
+32769+0 records in 
+32768+0 records out 
+33554432 bytes (34 MB, 32 MiB) copied, 0.0766899 s, 438 MB/s
+```
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>-   使用--host-channel大小限制时，若在容器内创建共享文件，则会受到容器内的内存配额限制（在容器内存使用达到极限时可能会产生oom）。  
+>-   若用户在主机端创建共享文件，则不受容器内的内存配额限制。  
+>-   若用户需要在容器内创建共享文件，且业务为内存密集型，可以通过设置容器内存配额为在原本基础上加上--host-channel配置的大小来消除影响。  
+
diff --git "a/content/zh/docs/Container/\345\212\250\346\200\201\345\212\240\350\275\275\345\206\205\346\240\270\346\250\241\345\235\227.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\212\250\346\200\201\345\212\240\350\275\275\345\206\205\346\240\270\346\250\241\345\235\227.md"
similarity index 97%
rename from "content/zh/docs/Container/\345\212\250\346\200\201\345\212\240\350\275\275\345\206\205\346\240\270\346\250\241\345\235\227.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\212\250\346\200\201\345\212\240\350\275\275\345\206\205\346\240\270\346\250\241\345\235\227.md"
index d5c65f9e4ea5c4b5047863f2acaba8ff08772c0e..0c6b898f04273d31bb1cac263b68a138095cc69d 100644
--- "a/content/zh/docs/Container/\345\212\250\346\200\201\345\212\240\350\275\275\345\206\205\346\240\270\346\250\241\345\235\227.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\345\212\250\346\200\201\345\212\240\350\275\275\345\206\205\346\240\270\346\250\241\345\235\227.md"
@@ -1,12 +1,12 @@
-# 动态加载内核模块
-
-## 功能描述
-
-容器内业务可能依赖某些内核模块，可通过设置环境变量的方式，在系统容器启动前动态加载容器中业务需要的内核模块到宿主机，此特性需要配合syscontainer-hooks一起使用，具体使用可参看"容器资源动态管理（syscontainer-tools）"章节。
-
-## 参数说明
-
-
+# 动态加载内核模块
+
+## 功能描述
+
+容器内业务可能依赖某些内核模块，可通过设置环境变量的方式，在系统容器启动前动态加载容器中业务需要的内核模块到宿主机，此特性需要配合syscontainer-hooks一起使用，具体使用可参看"容器资源动态管理（syscontainer-tools）"章节。
+
+## 参数说明
+
+
 
-
命令

 		
 
参数

@@ -23,31 +23,31 @@
 
 

 

-
-## 约束限制
-
--   如果加载的内核模块是未经过验证的，或者跟宿主机已有模块冲突的场景，会导致宿主机出现不可预知问题，在做加载内核模块时需要谨慎操作。
--   动态加载内核模块通过将需要加载的内核模块传递给容器，此功能是依靠syscontainer-tools捕获到容器启动的环境变量实现，依赖syscontainer-tools的正确安装部署。
--   加载的内核模块需要手动进行删除。
-
-## 使用示例
-
-启动系统容器时，指定-e KERNEL\_MODULES参数，待系统容器启动后，可以看到ip\_vs模块被成功加载到内核中。
-
-```
-[root@localhost ~]# lsmod | grep ip_vs
-[root@localhost ~]# isula run -tid -e KERNEL_MODULES=ip_vs,ip_vs_wrr --hook-spec /etc/syscontainer-tools/hookspec.json --system-container --external-rootfs /root/myrootfs none init
-ae18c4281d5755a1e153a7bff6b3b4881f36c8e528b9baba8a3278416a5d0980
-[root@localhost ~]# lsmod | grep ip_vs
-ip_vs_wrr              16384  0
-ip_vs                 176128  2 ip_vs_wrr
-nf_conntrack          172032  7 xt_conntrack,nf_nat,nf_nat_ipv6,ipt_MASQUERADE,nf_nat_ipv4,nf_conntrack_netlink,ip_vs
-nf_defrag_ipv6         20480  2 nf_conntrack,ip_vs
-libcrc32c              16384  3 nf_conntrack,nf_nat,ip_vs
-```
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->-   宿主机需要安装syscontainer-tools。  
->-   需要指定--hooks-spec为syscontainer hooks。  
-
+
+
+## 约束限制
+
+-   如果加载的内核模块是未经过验证的，或者跟宿主机已有模块冲突的场景，会导致宿主机出现不可预知问题，在做加载内核模块时需要谨慎操作。
+-   动态加载内核模块通过将需要加载的内核模块传递给容器，此功能是依靠syscontainer-tools捕获到容器启动的环境变量实现，依赖syscontainer-tools的正确安装部署。
+-   加载的内核模块需要手动进行删除。
+
+## 使用示例
+
+启动系统容器时，指定-e KERNEL\_MODULES参数，待系统容器启动后，可以看到ip\_vs模块被成功加载到内核中。
+
+```
+[root@localhost ~]# lsmod | grep ip_vs
+[root@localhost ~]# isula run -tid -e KERNEL_MODULES=ip_vs,ip_vs_wrr --hook-spec /etc/syscontainer-tools/hookspec.json --system-container --external-rootfs /root/myrootfs none init
+ae18c4281d5755a1e153a7bff6b3b4881f36c8e528b9baba8a3278416a5d0980
+[root@localhost ~]# lsmod | grep ip_vs
+ip_vs_wrr              16384  0
+ip_vs                 176128  2 ip_vs_wrr
+nf_conntrack          172032  7 xt_conntrack,nf_nat,nf_nat_ipv6,ipt_MASQUERADE,nf_nat_ipv4,nf_conntrack_netlink,ip_vs
+nf_defrag_ipv6         20480  2 nf_conntrack,ip_vs
+libcrc32c              16384  3 nf_conntrack,nf_nat,ip_vs
+```
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>-   宿主机需要安装syscontainer-tools。  
+>-   需要指定--hooks-spec为syscontainer hooks。  
+
diff --git "a/content/zh/docs/Container/\345\215\207\347\272\247.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\215\207\347\272\247.md"
similarity index 94%
rename from "content/zh/docs/Container/\345\215\207\347\272\247.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\215\207\347\272\247.md"
index b9ffd7f394b64640a1b98cd2461ad41a4fdb2fa1..c93a36cbeb91dde4ffd6d783f1608b2bec9a6a64 100644
--- "a/content/zh/docs/Container/\345\215\207\347\272\247.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\345\215\207\347\272\247.md"
@@ -8,7 +8,7 @@
 
 -   若为不同大版本之间的升级，例如从1.x.x版本升级到2.x.x版本，请先保存当前的配置文件/etc/isulad/daemon.json，并卸载已安装的iSulad软件包，然后安装待升级的iSulad软件包，随后恢复配置文件。
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >-   可通过** sudo rpm -qa |grep iSulad**  或  **isula version**  命令确认当前iSulad的版本号。  
 >-   相同大版本之间，如果希望手动升级，请下载iSulad及其所有依赖库的RPM包进行升级，参考命令如下：  
 >    ```  
diff --git "a/content/zh/docs/Container/\345\215\270\350\275\275.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\215\270\350\275\275.md"
similarity index 100%
rename from "content/zh/docs/Container/\345\215\270\350\275\275.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\215\270\350\275\275.md"
diff --git "a/content/zh/docs/Container/\345\221\275\344\273\244\350\241\214\345\217\202\350\200\203.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\221\275\344\273\244\350\241\214\345\217\202\350\200\203.md"
similarity index 100%
rename from "content/zh/docs/Container/\345\221\275\344\273\244\350\241\214\345\217\202\350\200\203.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\221\275\344\273\244\350\241\214\345\217\202\350\200\203.md"
diff --git "a/content/zh/docs/Container/\345\256\211\345\205\250\345\256\271\345\231\250.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\345\205\250\345\256\271\345\231\250.md"
similarity index 89%
rename from "content/zh/docs/Container/\345\256\211\345\205\250\345\256\271\345\231\250.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\345\205\250\345\256\271\345\231\250.md"
index 59dfe5bf88d08372051bf6863ebc7a19312655fd..9c07b50a15d1b43b47734be29ec99af8bd6b3f46 100644
--- "a/content/zh/docs/Container/\345\256\211\345\205\250\345\256\271\345\231\250.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\345\205\250\345\256\271\345\231\250.md"
@@ -7,7 +7,7 @@
 安全容器是使用虚拟化层进行容器间的隔离，同一个主机上不同的容器间运行互相不受影响。
 
 **图 1**  安全容器架构 
-![](figures/kata-arch.png)
+![](./figures/kata-arch.png)
 
 安全容器与Kubernetes中的Pod概念紧密联系，Kubernetes为容器调度管理平台的开源生态标准，它定义了一组容器操作相关接口（Container Runtime Interface 简称CRI）。
 
@@ -20,8 +20,8 @@
 安全容器与周边组件的关系如[图2](#fig17734185518269)所示。
 
 **图 2**  安全容器与周边组件的关系  
-![](figures/安全容器与周边组件的关系.png "安全容器与周边组件的关系")
+![](./figures/sec-container.png)
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >安全容器的安装和使用需要使用root权限。  
 
diff --git "a/content/zh/docs/Container/\345\256\211\345\205\250\346\200\247\345\222\214\351\232\224\347\246\273\346\200\247.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\345\205\250\346\200\247\345\222\214\351\232\224\347\246\273\346\200\247.md"
similarity index 99%
rename from "content/zh/docs/Container/\345\256\211\345\205\250\346\200\247\345\222\214\351\232\224\347\246\273\346\200\247.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\345\205\250\346\200\247\345\222\214\351\232\224\347\246\273\346\200\247.md"
index 200736c81e65491a747287f965ca92f53ea6ff4d..a7e3676cf7e1eade5c0366b1bc6a0f7778ef724e 100644
--- "a/content/zh/docs/Container/\345\256\211\345\205\250\346\200\247\345\222\214\351\232\224\347\246\273\346\200\247.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\345\205\250\346\200\247\345\222\214\351\232\224\347\246\273\346\200\247.md"
@@ -46,7 +46,7 @@ user namespace是将容器的root映射到主机的普通用户，使得容器
 
 ### 使用指导
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >指定--user-remap参数前，请先将rootfs下所有目录和文件的uid和gid做整体偏移，偏移量为--user-remap指定uid和gid的偏移量。  
 >例如将dev目录的uid和gid整体uid和gid偏移100000的参考命令为：  
 >chown 100000:100000 dev  
@@ -184,7 +184,7 @@ exit
     -   Alice可以执行任何container操作：\{"name":"policy\_5","users":\["alice"\],"actions":\["container"\]\}。
     -   Alice可以执行任何container操作，但请求的种类只能是get：\{"name":"policy\_5","users":\["alice"\],"actions":\["container"\], "readonly":true \}。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >-   配置中匹配action支持正则表达式。  
     >-   users不支持正则表达式。  
     >-   users不能有重复用户，即同一用户不能被多条规则匹配。  
diff --git "a/content/zh/docs/Container/\345\256\211\345\205\250\347\211\271\346\200\247.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\345\205\250\347\211\271\346\200\247.md"
similarity index 98%
rename from "content/zh/docs/Container/\345\256\211\345\205\250\347\211\271\346\200\247.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\345\205\250\347\211\271\346\200\247.md"
index 2b42fa30891ad70be07fdea0620f7c9fe89f0d09..9c7701ba978e0d052be1fa1f5482e50324560c31 100644
--- "a/content/zh/docs/Container/\345\256\211\345\205\250\347\211\271\346\200\247.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\345\205\250\347\211\271\346\200\247.md"
@@ -31,7 +31,7 @@ seccomp（**secure computing** **mode**）是linux kernel从2.6.23版本开始
 isula run -itd --security-opt seccomp=/path/to/seccomp/profile.json rnd-dockerhub.huawei.com/official/busybox
 ```
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >1.  创建容器时通过--security-opt将配置文件传给容器时，采用默认配置文件（/etc/isulad/seccomp\_default.json）。  
 >2.  创建容器时--security-opt设置为unconfined时，对容器不过滤系统调用。  
 >3.  “/path/to/seccomp/profile.json”需要是绝对路径。  
@@ -117,7 +117,7 @@ isula run --rm -it --security-opt seccomp:/path/to/seccomp/profile.json rnd-dock
 }
 ```
 
->![](public_sys-resources/icon-notice.gif) **须知：**   
+>![](./public_sys-resources/icon-notice.gif) **须知：**   
 >-   defaultAction、syscalls：对应的action的类型是一样的，但其值是不能一样的，目的就是让所有的syscal都有一个默认的action，并且如果syscalls数组中有明确的定义，就以syscalls中的为准，由于defaultAction、action的值不一样，就能保证action不会有冲突。当前支持的action有：  
 >    "SCMP\_ACT\_ERRNO"：禁止，并打印错误信息。  
 >    "SCMP\_ACT\_ALLOW"：允许。  
@@ -196,7 +196,7 @@ SELinux\(Security-Enhanced Linux\)是一个Linux内核的安全模块，提供
 -   引入SELinux会影响性能，设置SELinux之前需要对场景进行评估，确定必要时打开daemon端SELinux开关并设置容器SELinux配置
 -   对挂载卷进行标签配置时，源目录不允许为/、/usr、/etc、/tmp、/home、/run、/var、/root以及/usr的子目录。
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >-   目前iSulad不支持对容器的文件系统打标签，确保容器文件系统及配置目录打上容器可访问标签，需使用chcon命令对其打上标签。  
 >-   若iSulad启用SELinux访问控制，建议daemon启动前对/var/lib/isulad目录打上标签，容器容器创建时目录下生产的文件及文件夹将默认继承其标签，例如：  
 >    ```  
diff --git "a/content/zh/docs/Container/\345\256\211\350\243\205-\345\215\207\347\272\247\344\270\216\345\215\270\350\275\275.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\350\243\205-\345\215\207\347\272\247\344\270\216\345\215\270\350\275\275.md"
similarity index 100%
rename from "content/zh/docs/Container/\345\256\211\350\243\205-\345\215\207\347\272\247\344\270\216\345\215\270\350\275\275.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\350\243\205-\345\215\207\347\272\247\344\270\216\345\215\270\350\275\275.md"
diff --git "a/content/zh/docs/Container/\345\256\211\350\243\205\344\270\216\351\205\215\347\275\256-2.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\350\243\205\344\270\216\351\205\215\347\275\256-2.md"
similarity index 100%
rename from "content/zh/docs/Container/\345\256\211\350\243\205\344\270\216\351\205\215\347\275\256-2.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\350\243\205\344\270\216\351\205\215\347\275\256-2.md"
diff --git "a/content/zh/docs/Container/\345\256\211\350\243\205\344\270\216\351\205\215\347\275\256.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\350\243\205\344\270\216\351\205\215\347\275\256.md"
similarity index 99%
rename from "content/zh/docs/Container/\345\256\211\350\243\205\344\270\216\351\205\215\347\275\256.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\350\243\205\344\270\216\351\205\215\347\275\256.md"
index ba1a4f3a5434cc5ca2b683eae10c1f446cf03b3a..9a50d5a39df14d4a8054a7adf0fdb39a1476cfe3 100644
--- "a/content/zh/docs/Container/\345\256\211\350\243\205\344\270\216\351\205\215\347\275\256.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\350\243\205\344\270\216\351\205\215\347\275\256.md"
@@ -1,6 +1,6 @@
 # 安装与配置
 本章介绍iSulad的安装、安装后配置，以及升级和卸载的方法。
->![](public_sys-resources/icon-note.gif) **说明：**
+>![](./public_sys-resources/icon-note.gif) **说明：**
 >iSulad的安装、升级、卸载均需要使用root权限。
 
 
@@ -43,7 +43,7 @@ iSulad 安装完成后，可以根据需要进行相关配置。
 
 轻量级容器引擎（iSulad）服务端daemon为isulad，isulad可以通过配置文件进行配置，也可以通过命令行的方式进行配置，例如：isulad --xxx，优先级从高到低是：命令行方式\>配置文件\>代码中默认配置。
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >如果采用systemd管理iSulad进程，修改/etc/sysconfig/iSulad文件中的OPTIONS字段，等同于命令行方式进行配置。  
 
 -   **命令行方式**
@@ -489,12 +489,11 @@ iSulad 安装完成后，可以根据需要进行相关配置。
     }
     ```
 
-    >![](public_sys-resources/icon-notice.gif) **须知：**   
+    >![](./public_sys-resources/icon-notice.gif) **须知：**   
     >默认配置文件/etc/isulad/daemon.json仅供参考，请根据实际需要进行配置  
 
 
 ### 存储说明
-
 
 
@@ -504,14 +503,14 @@ iSulad 安装完成后，可以根据需要进行相关配置。
 
-
-
@@ -532,35 +531,35 @@ iSulad 安装完成后，可以根据需要进行相关配置。
 
-
-
-
-
-
@@ -592,7 +591,7 @@ iSulad 安装完成后，可以根据需要进行相关配置。
 
 -   日志文件管理：
 
-    >![](public_sys-resources/icon-notice.gif) **须知：**   
+    >![](./public_sys-resources/icon-notice.gif) **须知：**   
     >日志功能对接： iSulad由systemd管理，日志也由systemd管理，然后传输给rsyslogd。rsyslog默认会对写日志速度有限制，可以通过修改/etc/rsyslog.conf文件，增加"$imjournalRatelimitInterval 0"配置项，然后重启rsyslogd的服务即可。  
 
 -   命令行参数解析限制
@@ -786,7 +785,7 @@ iSulad采用C/S模式进行设计，在默认情况，iSulad守护进程isulad
 
 如果需要采用单向认证方式进行通讯，则服务端采用模式2，客户端采用模式2。
 
->![](public_sys-resources/icon-notice.gif) **须知：**   
+>![](./public_sys-resources/icon-notice.gif) **须知：**   
 >-   采用RPM安装方式时，服务端配置可通过/etc/isulad/daemon.json以及/etc/sysconfig/iSulad配置修改  
 >-   相比非认证或者单向认证方式，双向认证具备更高的安全性，推荐使用双向认证的方式进行通讯  
 >-   GRPC开源组件日志不由iSulad进行接管，如果需要查看GRPC相关日志，请按需设置GRPC\_VERBOSITY和GRPC\_TRACE环境变量  
diff --git "a/content/zh/docs/Container/\345\256\211\350\243\205\346\214\207\345\257\274.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\350\243\205\346\214\207\345\257\274.md"
similarity index 84%
rename from "content/zh/docs/Container/\345\256\211\350\243\205\346\214\207\345\257\274.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\350\243\205\346\214\207\345\257\274.md"
index fbcd663a6015c6b18d9b3b7e887ac5b045549b08..fcf2db30db8519b5fad347b79784a77788e783b0 100644
--- "a/content/zh/docs/Container/\345\256\211\350\243\205\346\214\207\345\257\274.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\350\243\205\346\214\207\345\257\274.md"
@@ -1,31 +1,31 @@
-# 安装指导
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->系统容器的安装需要使用root权限。 
-
-1.  首先需要安装iSulad容器引擎。
-
-    ```
-    # yum install iSulad
-    ```
-
-2.  安装系统容器依赖包。
-
-    ```
-    # yum install syscontainer-tools authz lxcfs-tools lxcfs
-    ```
-
-3.  查看iSulad是否已经启动。
-
-    ```
-    # systemctl status isulad
-    ```
-
-4.  开启lxcfs和authz服务。
-
-    ```
-    # systemctl start lxcfs
-    # systemctl start authz
-    ```
-
-
+# 安装指导
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>系统容器的安装需要使用root权限。 
+
+1.  首先需要安装iSulad容器引擎。
+
+    ```
+    # yum install iSulad
+    ```
+
+2.  安装系统容器依赖包。
+
+    ```
+    # yum install syscontainer-tools authz lxcfs-tools lxcfs
+    ```
+
+3.  查看iSulad是否已经启动。
+
+    ```
+    # systemctl status isulad
+    ```
+
+4.  开启lxcfs和authz服务。
+
+    ```
+    # systemctl start lxcfs
+    # systemctl start authz
+    ```
+
+
diff --git "a/content/zh/docs/Container/\345\256\211\350\243\205\351\205\215\347\275\256-3.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\350\243\205\351\205\215\347\275\256-3.md"
similarity index 98%
rename from "content/zh/docs/Container/\345\256\211\350\243\205\351\205\215\347\275\256-3.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\350\243\205\351\205\215\347\275\256-3.md"
index 12d586d56f7a819ae6437f0321f5d018d24970a3..84202b96449118f548e6a0bdac2e2ab3a96be1f3 100644
--- "a/content/zh/docs/Container/\345\256\211\350\243\205\351\205\215\347\275\256-3.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\211\350\243\205\351\205\215\347\275\256-3.md"
@@ -52,12 +52,12 @@ cat /etc/docker/daemon.json
 
 用户需要明白重新指定各种运行目录和文件（包括--graph、--exec-root等），可能会存在目录冲突，或文件属性变换，对应用的正常使用造成影响。
 
->![](public_sys-resources/icon-notice.gif) **须知：**   
+>![](./public_sys-resources/icon-notice.gif) **须知：**   
 >用户指定的目录或文件应为docker专用，避免冲突导致的文件属性变化带来安全问题。  
 
 -   以--graph为例，当我们使用/new/path/作为daemon新的Root Dir时，如果/new/path/下已经存在文件，且目录或文件名与docker需要使用的目录或文件名冲突（例如： containers、hooks、tmp等目录）时，docker可能会更新原有目录或文件的属性，包括属主、权限等为自己的属主和权限。
 
->![](public_sys-resources/icon-notice.gif) **须知：**   
+>![](./public_sys-resources/icon-notice.gif) **须知：**   
 >从docker-17.05开始，--graph参数被标记为Deprecated，用新的参数--data-root替代。  
 
 ### daemon自带网络配置
@@ -72,7 +72,7 @@ cat /etc/docker/daemon.json
 
 docker启动容器时的默认umask值为0027，可以在dockerd启动时，使用--exec-opt native.umask=normal参数将容器启动时的umask修改为0022。
 
->![](public_sys-resources/icon-notice.gif) **须知：**   
+>![](./public_sys-resources/icon-notice.gif) **须知：**   
 >如果docker create/run也配置了native.umask参数，则以docker create/run中的配置为准。  
 
 详细的配置见[docker create](#create.md#ZH-CN_TOPIC_0184808242)和[docker run](#run.md#ZH-CN_TOPIC_0184808254)章节的参数说明。
@@ -145,7 +145,7 @@ docker支持配置audit，但不是强制的。例如：
 [root@localhost signal]# auditctl -l | grep docker -w /var/lib/docker/ -p rwxa -k docker
 ```
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >-p \[r|w|x|a\] 和-w一起使用，观察用户对这个目录的读、写、执行或者属性变化（如时间戳变化）。这样的话，在/var/lib/docker目录下的任何文件、目录操作，都会打印日志到audit.log中，从而会有太多的日志往audit.log中记录，会严重地影响auditd， 比如内存、cpu占用等，进而影响os的运行。例如：每次执行"ls /var/lib/docker/containers"都会有类似如下日志记录到/var/log/audit/audit.log中。  
 
 ```
@@ -441,7 +441,7 @@ Error response from daemon: oci runtime error: container with id exists: xxxxxx
     -   构建缓存，构建缓存信息会在重启后删除。
     -   containerd保存的元数据，由于启动容器会重建containerd元数据，重启节点会清理containerd中保存的元数据。
 
-        >![](public_sys-resources/icon-note.gif) **说明：**   
+        >![](./public_sys-resources/icon-note.gif) **说明：**   
         >用户若选择采用手动清理恢复环境的方式，可通过配置环境变量“DISABLE\_CRASH\_FILES\_DELETE=true”屏蔽daemon掉电重启时db文件清理功能。  
 
 
diff --git "a/content/zh/docs/Container/\345\256\271\345\231\250\345\201\245\345\272\267\347\212\266\346\200\201\346\243\200\346\237\245.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\345\201\245\345\272\267\347\212\266\346\200\201\346\243\200\346\237\245.md"
similarity index 100%
rename from "content/zh/docs/Container/\345\256\271\345\231\250\345\201\245\345\272\267\347\212\266\346\200\201\346\243\200\346\237\245.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\345\201\245\345\272\267\347\212\266\346\200\201\346\243\200\346\237\245.md"
diff --git "a/content/zh/docs/Container/\345\256\271\345\231\250\345\206\205reboot-shutdown.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\345\206\205reboot-shutdown.md"
similarity index 98%
rename from "content/zh/docs/Container/\345\256\271\345\231\250\345\206\205reboot-shutdown.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\345\206\205reboot-shutdown.md"
index 14508d324269ffafe4592db409c74aee17837129..fed94bfad7f1cb583826e4c20847dd8aaf351105 100644
--- "a/content/zh/docs/Container/\345\256\271\345\231\250\345\206\205reboot-shutdown.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\345\206\205reboot-shutdown.md"
@@ -1,12 +1,12 @@
-# 容器内reboot/shutdown
-
-## 功能描述
-
-系统容器支持在容器内执行reboot和shutdown命令。执行reboot命令效果同重启容器一致；执行shutdown命令效果同停止容器一致。
-
-## 参数说明
-
-
+# 容器内reboot/shutdown
+
+## 功能描述
+
+系统容器支持在容器内执行reboot和shutdown命令。执行reboot命令效果同重启容器一致；执行shutdown命令效果同停止容器一致。
+
+## 参数说明
+
+
文件名

 		
 

 
*

+
\*

 		
 
/etc/default/isulad/

 		
 
存放isulad的OCI配置文件和钩子模板文件，文件夹下的配置文件权限设置为0640，sysmonitor检查脚本权限为0550

 		
 
*

+
\*

 		
 
/etc/isulad/

 
存放isulad的PID，同时也是一个文件锁防止启动多个isulad实例

 		
 
*

+
\*

 		
 
/run/lxc/

 		
 
文件锁文件，isula运行过程创建的文件

 		
 
*

+
\*

 		
 
/var/run/isulad/

 		
 
实时通讯缓存文件，isulad运行过程创建的文件

 		
 
*

+
\*

 		
 
/var/run/isula/

 		
 
实时通讯缓存文件，isula运行过程创建的文件

 		
 
*

+
\*

 		
 
/var/lib/lcr/

 		
 
LCR 组件临时目录

 		
 
*

+
\*

 		
 
/var/lib/isulad/

 		
 

-
命令

 		
 
参数

@@ -25,55 +25,55 @@
 
 

 

-
-## 约束限制
-
--   shutdown功能，依赖于不同的OS，以实际容器运行环境对应OS为准。
--   执行“shutdown -h now”命令关闭系统时，不能多次占用console。例如“isula run -ti”命令打开一个console，在另一个host bash中isula attach该容器，会打开另一个console，此时执行shutdown会失败。
-
-## 使用示例
-
--   容器启动时指定\--restart on-reboot参数，示例如下：
-
-    ```
-    [root@localhost ~]# isula run -tid --restart on-reboot --system-container --external-rootfs /root/myrootfs none init
-    106faae22a926e22c828a0f2b63cf5c46e5d5986ea8a5b26de81390d0ed9714f
-    ```
-
-
--   进入容器执行reboot命令：
-
-    ```
-    [root@localhost ~]# isula exec -it 10 bash
-    [root@localhost /]# reboot
-    ```
-
-    查看容器是否重启：
-
-    ```
-    [root@localhost ~]# isula exec -it 10 ps aux
-    USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
-    root         1  0.1  0.0  21588  9504 ?        Ss   12:11   0:00 init
-    root        14  0.1  0.0  27024  9376 ?        Ss   12:11   0:00 /usr/lib/system
-    root        17  0.0  0.0  18700  5876 ?        Ss   12:11   0:00 /usr/lib/system
-    dbus        22  0.0  0.0   9048  3624 ?        Ss   12:11   0:00 /usr/bin/dbus-d
-    root        26  0.0  0.0   8092  3012 ?        Rs+  12:13   0:00 ps aux
-    ```
-
--   进入容器执行shutdown命令：
-
-    ```
-    [root@localhost ~]# isula exec -it 10 bash
-    [root@localhost /]# shutdown -h now
-    [root@localhost /]# [root@localhost ~]#
-    ```
-
-    检查容器是否停止：
-
-    ```
-    [root@localhost ~]# isula exec -it 10 bash
-    Error response from daemon: Exec container error;Container is not running:106faae22a926e22c828a0f2b63cf5c46e5d5986ea8a5b26de81390d0ed9714f
-    ```
-
-
+
+
+## 约束限制
+
+-   shutdown功能，依赖于不同的OS，以实际容器运行环境对应OS为准。
+-   执行“shutdown -h now”命令关闭系统时，不能多次占用console。例如“isula run -ti”命令打开一个console，在另一个host bash中isula attach该容器，会打开另一个console，此时执行shutdown会失败。
+
+## 使用示例
+
+-   容器启动时指定\--restart on-reboot参数，示例如下：
+
+    ```
+    [root@localhost ~]# isula run -tid --restart on-reboot --system-container --external-rootfs /root/myrootfs none init
+    106faae22a926e22c828a0f2b63cf5c46e5d5986ea8a5b26de81390d0ed9714f
+    ```
+
+
+-   进入容器执行reboot命令：
+
+    ```
+    [root@localhost ~]# isula exec -it 10 bash
+    [root@localhost /]# reboot
+    ```
+
+    查看容器是否重启：
+
+    ```
+    [root@localhost ~]# isula exec -it 10 ps aux
+    USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
+    root         1  0.1  0.0  21588  9504 ?        Ss   12:11   0:00 init
+    root        14  0.1  0.0  27024  9376 ?        Ss   12:11   0:00 /usr/lib/system
+    root        17  0.0  0.0  18700  5876 ?        Ss   12:11   0:00 /usr/lib/system
+    dbus        22  0.0  0.0   9048  3624 ?        Ss   12:11   0:00 /usr/bin/dbus-d
+    root        26  0.0  0.0   8092  3012 ?        Rs+  12:13   0:00 ps aux
+    ```
+
+-   进入容器执行shutdown命令：
+
+    ```
+    [root@localhost ~]# isula exec -it 10 bash
+    [root@localhost /]# shutdown -h now
+    [root@localhost /]# [root@localhost ~]#
+    ```
+
+    检查容器是否停止：
+
+    ```
+    [root@localhost ~]# isula exec -it 10 bash
+    Error response from daemon: Exec container error;Container is not running:106faae22a926e22c828a0f2b63cf5c46e5d5986ea8a5b26de81390d0ed9714f
+    ```
+
+
diff --git "a/content/zh/docs/Container/\345\256\271\345\231\250\345\274\225\346\223\216-4.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\345\274\225\346\223\216-4.md"
similarity index 99%
rename from "content/zh/docs/Container/\345\256\271\345\231\250\345\274\225\346\223\216-4.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\345\274\225\346\223\216-4.md"
index a230e281993e13fb393c217bbce61dde05a1d314..1741c561a9434ae2a973e997ddcd8d7d59eb26c9 100644
--- "a/content/zh/docs/Container/\345\256\271\345\231\250\345\274\225\346\223\216-4.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\345\274\225\346\223\216-4.md"
@@ -125,11 +125,7 @@ docker命令支持多个参数选项，对于参数选项有以下约定：
 
 
设置运行时执行选项。

 
例如支持native.umask选项：

-
# 启动的容器umask值为0022 
---exec-opt native.umask=normal 
-
-# 启动的容器umask值为0027（默认值）
---exec-opt  native.umask=secure    

+
# 启动的容器umask值为0022 --exec-opt native.umask=normal # 启动的容器umask值为0027（默认值）--exec-opt  native.umask=secure

 
注意如果docker  create/run也配置了native.umask参数则以docker create/run中的配置为准。

 
 
diff --git "a/content/zh/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206-3.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206-3.md"
similarity index 99%
rename from "content/zh/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206-3.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206-3.md"
index 65e7d9a39a25be5d622e281a186159cafdb619ed..02e00cf5715d2c0768d035ccda20e25f368414f3 100644
--- "a/content/zh/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206-3.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206-3.md"
@@ -575,7 +575,7 @@ CONTAINER ID        IMAGE               COMMAND             CREATED
 }
 ```
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >-   容器内健康检查的状态信息最多保存5条。会保存最后得到的5条记录。  
 >-   容器内健康检查相关配置同时最多只能有一条生效。Dockerfile中配置的靠后的条目会覆盖靠前的；容器创建时的配置会覆盖镜像中的。  
 >-   在Dockerfile中可以通过 HEALTHCHECK NONE来取消引用的镜像中的健康检查配置。在容器运行时可以通过配置--no-healthcheck来取消镜像中的健康检查配置。不允许在启动时同时配置健康检查相关选项与--no-healthcheck选项。  
diff --git "a/content/zh/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206-4.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206-4.md"
similarity index 99%
rename from "content/zh/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206-4.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206-4.md"
index 9f9f5c15d95632319573d095b2a74399259b31e9..23b7f49276f5739e2525259eb331e28fdd3856d4 100644
--- "a/content/zh/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206-4.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206-4.md"
@@ -1079,7 +1079,7 @@ b15976967abb        busybox:latest        "bash"              34 seconds ago
 $ sudo docker restart busybox
 ```
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >容器在restart过程中，如果容器内存在D状态或Z状态的进程，可能会导致容器重启失败，这需要进一步分析导致容器内进程D状态或Z状态的原因，待容器内进程D状态或Z状态解除后，再进行容器restart操作。  
 
 ## rm
diff --git "a/content/zh/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206.md"
similarity index 99%
rename from "content/zh/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206.md"
index 6d25ee645462cd89a5720dd2113c98053f4f29b0..a08a762216b753ad10e2902644b9976e6a0b3384 100644
--- "a/content/zh/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\347\256\241\347\220\206.md"
@@ -561,11 +561,6 @@ run命令支持参数参考下表。
 
即使没有连接到容器的标准输入，也要保持容器的标准输入打开

 
 
-
--log-driver

-
-
设置日志驱动，支持syslog和json-file。

-
-
 
--log-opt=[]

 
 
日志驱动程序选项，默认禁用记录容器串口日志功能，可以通过"--log-opt disable-log=false"来开启。

@@ -743,19 +738,19 @@ run命令支持参数参考下表。
     
     
 
-    >![](public_sys-resources/icon-notice.gif) **须知：**   
+    >![](./public_sys-resources/icon-notice.gif) **须知：**   
     >第一种情况，先挂载/home/test1，然后挂载/home/test2，这种情况会导致/home/test1的内容覆盖掉原来/mnt下面的内容，这样可能导致/mnt下面不存在abc目录，这样会导致挂载/home/test2到/mnt/abc失败。  
     >第二种情况，先挂载/home/test2，然后挂载/home/test1。这种情况，第二次的挂载会把/mnt的内容替换为/home/test1的内容，这样第一次挂载的/home/test2到/mnt/abc的内容就看不到了。  
     >因此，不支持第一种使用方式；第二种使用用户需要了解这种数据无法访问的风险  
 
-    >![](public_sys-resources/icon-notice.gif) **须知：**   
+    >![](./public_sys-resources/icon-notice.gif) **须知：**   
     >-   高并发场景（并发启动200容器）下，glibc的内存管理机制会导致内存空洞以及虚拟内存较大（例如10GB）的问题。该问题是高并发场景下glibc内存管理机制的限制，而不是内存泄露，不会导致内存消耗无限增大。可以通过设置MALLOC\_ARENA\_MAX环境变量来减少虚拟内存的问题，而且可以增大减少物理内存的概率。但是这个环境变量会导致iSulad的并发性能下降，需要用户根据实际情况做配置。  
     >    ```  
     >    参考实践情况，平衡性能和内存，可以设置MALLOC_ARENA_MAX为4。（在arm64服务器上面对iSulad的性能影响在10%以内）  
     >    配置方法：  
     >    1. 手动启动iSulad的场景，可以直接export MALLOC_ARENA_MAX=4，然后再启动iSulad即可。  
     >    2. systemd管理iSulad的场景，可以修改/etc/sysconfig/iSulad，增加一条MALLOC_ARENA_MAX=4即可。  
-    >    ```
+    >    ```  
 
 
 ### 示例
@@ -1244,7 +1239,7 @@ inspect命令支持参数参考下表。
 
 ### 约束限制
 
--   轻量级容器不支持format为“\{\{.State\}\}”的格式化输出，支持“\{\{json .State\}\}”的json格式化输出。当inspect镜像时，不支持-f参数。
+-   轻量级容器不支持format为“\{ \{.State\} \}”的格式化输出，支持“\{ \{json .State\} \}”的json格式化输出。当inspect镜像时，不支持-f参数。
 
 ### 示例
 
diff --git "a/content/zh/docs/Container/\345\256\271\345\231\250\350\265\204\346\272\220\345\212\250\346\200\201\347\256\241\347\220\206.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\350\265\204\346\272\220\345\212\250\346\200\201\347\256\241\347\220\206.md"
similarity index 99%
rename from "content/zh/docs/Container/\345\256\271\345\231\250\350\265\204\346\272\220\345\212\250\346\200\201\347\256\241\347\220\206.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\350\265\204\346\272\220\345\212\250\346\200\201\347\256\241\347\220\206.md"
index c09fa4af20f3643963297e7a371796c88cf78262..5ab7230555dceebb3c97339c67f29bdee5687168 100644
--- "a/content/zh/docs/Container/\345\256\271\345\231\250\350\265\204\346\272\220\345\212\250\346\200\201\347\256\241\347\220\206.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\350\265\204\346\272\220\345\212\250\346\200\201\347\256\241\347\220\206.md"
@@ -253,7 +253,7 @@ container\_id：容器id。
     Add network interface to container 2aaca5c1af7c (eth3,eth1) done
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >添加虚拟网卡或物理网卡时，请确保网卡处于空闲状态，添加正在使用的网卡会导致系统网络断开。  
 
 
diff --git "a/content/zh/docs/Container/\345\256\271\345\231\250\350\265\204\346\272\220\347\256\241\347\220\206.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\350\265\204\346\272\220\347\256\241\347\220\206.md"
similarity index 99%
rename from "content/zh/docs/Container/\345\256\271\345\231\250\350\265\204\346\272\220\347\256\241\347\220\206.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\350\265\204\346\272\220\347\256\241\347\220\206.md"
index 20223d146e428ef50ec37117298c54a0f9aefedc..ce610af5f7d2a3934630027b5f0497edd0291666 100644
--- "a/content/zh/docs/Container/\345\256\271\345\231\250\350\265\204\346\272\220\347\256\241\347\220\206.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\345\256\271\345\231\250\350\265\204\346\272\220\347\256\241\347\220\206.md"
@@ -166,7 +166,7 @@ create/run时可以指定下列参数。
 isula run -tid --cpuset-cpus 0,2-3 busybox sh
 ```
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >是否设置成功，请参见“查询单个容器信息”章节。  
 
 ## 限制运行时的内存
@@ -457,7 +457,7 @@ overlay                  10.0M     10.0M         0 100% /
 
     使用限额功能的isulad切换数据盘时，需要保证被切换的数据盘使用\`prjquota\`选项挂载，且/var/lib/isulad/storage/overlay2目录的挂载方式与/var/lib/isulad相同。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >切换数据盘时需要保证/var/lib/isulad/storage/overlay2的挂载点被卸载。  
 
 
diff --git "a/content/zh/docs/Container/\346\214\207\345\256\232rootfs\345\210\233\345\273\272\345\256\271\345\231\250.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\346\214\207\345\256\232rootfs\345\210\233\345\273\272\345\256\271\345\231\250.md"
similarity index 97%
rename from "content/zh/docs/Container/\346\214\207\345\256\232rootfs\345\210\233\345\273\272\345\256\271\345\231\250.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\346\214\207\345\256\232rootfs\345\210\233\345\273\272\345\256\271\345\231\250.md"
index 7a5ab73002b37ece92515761b5b5742557ae6443..dd6a08280d086eaabbe4e98baf9428e663fcf03d 100644
--- "a/content/zh/docs/Container/\346\214\207\345\256\232rootfs\345\210\233\345\273\272\345\256\271\345\231\250.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\346\214\207\345\256\232rootfs\345\210\233\345\273\272\345\256\271\345\231\250.md"
@@ -1,12 +1,12 @@
-# 指定rootfs创建容器
-
-## 功能描述
-
-系统容器不同于普通容器，普通容器需要指定一个容器镜像来启动，而系统容器通过参数 \--external-rootfs 指定一个本地的根文件系统rootfs（Root File System）来启动，rootfs包含了容器运行时依赖的操作系统环境。
-
-## 参数说明
-
-
+# 指定rootfs创建容器
+
+## 功能描述
+
+系统容器不同于普通容器，普通容器需要指定一个容器镜像来启动，而系统容器通过参数 \--external-rootfs 指定一个本地的根文件系统rootfs（Root File System）来启动，rootfs包含了容器运行时依赖的操作系统环境。
+
+## 参数说明
+
+
 
-
命令

 		
 
参数

@@ -23,24 +23,24 @@
 
 

 

-
-## 约束限制
-
--   参数--external-rootfs指定的rootfs目录必须为绝对路径，不能为相对路径。
--   参数--external-rootfs指定的rootfs目录必须为一个完整运行的操作系统环境，否则容器会启动失败。
--   容器删除时，不会删除--external-rootfs指定的rootfs目录。
--   不支持在x86环境上运行基于arm rootfs的容器，也不支持在arm环境上运行基于x86 rootfs的容器。
--   同一份rootfs，不建议启动多个容器实例，即同一份rootfs只供一个生命周期内的容器实例使用。
-
-## 使用示例
-
-假设本地rootfs的路径为/root/myrootfs，那么启动一个系统容器的命令如下：
-
-```
-# isula run  -tid --system-container --external-rootfs /root/myrootfs none init
-```
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->rootfs为自定义的文件系统，请用户自行准备。例如容器镜像的tar包解压后，即为一个rootfs。  
-
+
+
+## 约束限制
+
+-   参数--external-rootfs指定的rootfs目录必须为绝对路径，不能为相对路径。
+-   参数--external-rootfs指定的rootfs目录必须为一个完整运行的操作系统环境，否则容器会启动失败。
+-   容器删除时，不会删除--external-rootfs指定的rootfs目录。
+-   不支持在x86环境上运行基于arm rootfs的容器，也不支持在arm环境上运行基于x86 rootfs的容器。
+-   同一份rootfs，不建议启动多个容器实例，即同一份rootfs只供一个生命周期内的容器实例使用。
+
+## 使用示例
+
+假设本地rootfs的路径为/root/myrootfs，那么启动一个系统容器的命令如下：
+
+```
+# isula run  -tid --system-container --external-rootfs /root/myrootfs none init
+```
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>rootfs为自定义的文件系统，请用户自行准备。例如容器镜像的tar包解压后，即为一个rootfs。  
+
diff --git "a/content/zh/docs/Container/\346\224\257\346\214\201CNI\347\275\221\347\273\234.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\346\224\257\346\214\201CNI\347\275\221\347\273\234.md"
similarity index 96%
rename from "content/zh/docs/Container/\346\224\257\346\214\201CNI\347\275\221\347\273\234.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\346\224\257\346\214\201CNI\347\275\221\347\273\234.md"
index a5444e4e8ed3b52005b1ef851998c10d045731c5..cb48737268e36d2c83e8af8cfa56e644d99d6acc 100644
--- "a/content/zh/docs/Container/\346\224\257\346\214\201CNI\347\275\221\347\273\234.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\346\224\257\346\214\201CNI\347\275\221\347\273\234.md"
@@ -14,12 +14,6 @@
 
 实现CRI接口对接CNI网络的能力，包括CNI网络配置文件的解析、CNI网络的加入和退出。Pod需要支持网络时，例如通过canal等容器网络插件提供网络能力，那么需要CRI接口能够和canal实现对接，并且调用canal的接口，为Pod提供网络能力。
 
-CNI配置文件相关行为描述：
-
-- 对--cni-conf-dir目录下的合法配置文件名进行字典排序，取第一个合法配置作为default网络平面的配置；
-- 每隔5s对配置目录进行扫描，重新加载更新CNI配置；
-- CRI Status接口不更新CNI的网络配置；
-
 ## 接口
 
 CNI对用户可见的接口，主要涉及CNI网络配置和Pod配置中CNI网络相关的项。
@@ -123,7 +117,7 @@ Pod配置中和网络相关的还有port\_mappings项，用于设置Pod的端口
 
 StopPodSandbox的时候，会调用退出CNI网络的接口，清理网络相关的资源。
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >1. 在调用RemovePodSandbox接口之前，至少要调用一次StopPodSandbox接口  
 >2. StopPodSandbox调用CNI接口失败，可能导致的网络资源残留。  
 
diff --git "a/content/zh/docs/Container/\346\224\257\346\214\201OCI-hooks.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\346\224\257\346\214\201OCI-hooks.md"
similarity index 100%
rename from "content/zh/docs/Container/\346\224\257\346\214\201OCI-hooks.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\346\224\257\346\214\201OCI-hooks.md"
diff --git "a/content/zh/docs/Container/\346\234\200\345\244\247\345\217\245\346\237\204\346\225\260\351\231\220\345\210\266.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\346\234\200\345\244\247\345\217\245\346\237\204\346\225\260\351\231\220\345\210\266.md"
similarity index 98%
rename from "content/zh/docs/Container/\346\234\200\345\244\247\345\217\245\346\237\204\346\225\260\351\231\220\345\210\266.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\346\234\200\345\244\247\345\217\245\346\237\204\346\225\260\351\231\220\345\210\266.md"
index d17c211009369ef71b3d8c4482bcc054f065428a..4de230203107c3f2b4a9c11c9b8a2349a400c2bb 100644
--- "a/content/zh/docs/Container/\346\234\200\345\244\247\345\217\245\346\237\204\346\225\260\351\231\220\345\210\266.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\346\234\200\345\244\247\345\217\245\346\237\204\346\225\260\351\231\220\345\210\266.md"
@@ -1,12 +1,12 @@
-# 最大句柄数限制
-
-## 功能描述
-
-系统容器支持对容器内使用文件句柄数进行限制，文件句柄包括普通文件句柄和网络套接字，启动容器时，可以通过指定--files-limit参数限制容器内打开的最大句柄数。
-
-## 参数说明
-
-
+# 最大句柄数限制
+
+## 功能描述
+
+系统容器支持对容器内使用文件句柄数进行限制，文件句柄包括普通文件句柄和网络套接字，启动容器时，可以通过指定--files-limit参数限制容器内打开的最大句柄数。
+
+## 参数说明
+
+
 
-
命令

 		
 
参数

@@ -24,33 +24,33 @@
 
 

 

-
-## 约束限制
-
--   如果\--files-limit指定的值太小，可能会导致系统容器无法通过exec执行命令，报"open too many  files"错误，所以files limit的值应该设置大一些。
--   文件句柄包括普通文件句柄和网络套接字。
-
-## 使用示例
-
-使用\--files-limit限制容器内打开文件句柄数需要内核支持files cgroup，可以执行以下命令查看：
-
-```
-[root@localhost ~]# cat /proc/1/cgroup | grep files
-10:files:/
-```
-
-结果显示files，说明内核支持files cgroup。
-
-容器启动指定--files-limit参数，并检查files.limit参数是否成功写入：
-
-```
-[root@localhost ~]# isula run  -tid --files-limit 1024 --system-container  --external-rootfs /tmp/root-fs  empty init 01e82fcf97d4937aa1d96eb8067f9f23e4707b92de152328c3fc0ecb5f64e91d 
-[root@localhost ~]# isula exec -it 01e82fcf97d4 bash 
-[root@localhost ~]# cat /sys/fs/cgroup/files/files.limit 
-1024 
-
-```
-
-可以看出，容器内文件句柄数被成功限制。
-
+
+
+## 约束限制
+
+-   如果\--files-limit指定的值太小，可能会导致系统容器无法通过exec执行命令，报"open too many  files"错误，所以files limit的值应该设置大一些。
+-   文件句柄包括普通文件句柄和网络套接字。
+
+## 使用示例
+
+使用\--files-limit限制容器内打开文件句柄数需要内核支持files cgroup，可以执行以下命令查看：
+
+```
+[root@localhost ~]# cat /proc/1/cgroup | grep files
+10:files:/
+```
+
+结果显示files，说明内核支持files cgroup。
+
+容器启动指定--files-limit参数，并检查files.limit参数是否成功写入：
+
+```
+[root@localhost ~]# isula run  -tid --files-limit 1024 --system-container  --external-rootfs /tmp/root-fs  empty init 01e82fcf97d4937aa1d96eb8067f9f23e4707b92de152328c3fc0ecb5f64e91d 
+[root@localhost ~]# isula exec -it 01e82fcf97d4 bash 
+[root@localhost ~]# cat /sys/fs/cgroup/files/files.limit 
+1024 
+
+```
+
+可以看出，容器内文件句柄数被成功限制。
+
diff --git "a/content/zh/docs/Container/\346\237\245\350\257\242\344\277\241\346\201\257.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\346\237\245\350\257\242\344\277\241\346\201\257.md"
similarity index 100%
rename from "content/zh/docs/Container/\346\237\245\350\257\242\344\277\241\346\201\257.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\346\237\245\350\257\242\344\277\241\346\201\257.md"
diff --git "a/content/zh/docs/Container/\347\211\271\346\235\203\345\256\271\345\231\250.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\347\211\271\346\235\203\345\256\271\345\231\250.md"
similarity index 100%
rename from "content/zh/docs/Container/\347\211\271\346\235\203\345\256\271\345\231\250.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\347\211\271\346\235\203\345\256\271\345\231\250.md"
diff --git "a/content/zh/docs/Container/\347\216\257\345\242\203\345\217\230\351\207\217\346\214\201\344\271\205\345\214\226.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\347\216\257\345\242\203\345\217\230\351\207\217\346\214\201\344\271\205\345\214\226.md"
similarity index 98%
rename from "content/zh/docs/Container/\347\216\257\345\242\203\345\217\230\351\207\217\346\214\201\344\271\205\345\214\226.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\347\216\257\345\242\203\345\217\230\351\207\217\346\214\201\344\271\205\345\214\226.md"
index 22d36c8ab32d16d7812596ba14d792c34379f0c0..1127d322cf4670ae291e7b20812efe0f573c5c18 100644
--- "a/content/zh/docs/Container/\347\216\257\345\242\203\345\217\230\351\207\217\346\214\201\344\271\205\345\214\226.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\347\216\257\345\242\203\345\217\230\351\207\217\346\214\201\344\271\205\345\214\226.md"
@@ -1,12 +1,12 @@
-# 环境变量持久化
-
-## 功能描述
-
-系统容器支持通过指定--env-target-file接口参数将env变量持久化到容器rootfs目录下的配置文件中。
-
-## 参数说明
-
-
+# 环境变量持久化
+
+## 功能描述
+
+系统容器支持通过指定--env-target-file接口参数将env变量持久化到容器rootfs目录下的配置文件中。
+
+## 参数说明
+
+
 
-
命令

 		
 
参数

@@ -23,26 +23,26 @@
 
 

 

-
-## 约束限制
-
--   --env-target-file指定的目标文件如果存在的话，大小不能超过10MB。
--   --env-target-file指定的参数为rootfs目录下的绝对路径。
--   如果--env和目标文件里面的env出现冲突，以--env指定值的参数为准。
-
-## 使用示例
-
-启动系统容器，指定env环境变量和--env-target-file参数：
-
-```
-[root@localhost ~]# isula run -tid -e abc=123 --env-target-file /etc/environment --system-container --external-rootfs /root/myrootfs none init
-b75df997a64da74518deb9a01d345e8df13eca6bcc36d6fe40c3e90ea1ee088e
-[root@localhost ~]# isula exec b7 cat /etc/environment
-PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
-TERM=xterm
-abc=123
-```
-
-可以看到容器的env变量（abc=123）已经持久化到/etc/environment配置文件中。
-
+
+
+## 约束限制
+
+-   --env-target-file指定的目标文件如果存在的话，大小不能超过10MB。
+-   --env-target-file指定的参数为rootfs目录下的绝对路径。
+-   如果--env和目标文件里面的env出现冲突，以--env指定值的参数为准。
+
+## 使用示例
+
+启动系统容器，指定env环境变量和--env-target-file参数：
+
+```
+[root@localhost ~]# isula run -tid -e abc=123 --env-target-file /etc/environment --system-container --external-rootfs /root/myrootfs none init
+b75df997a64da74518deb9a01d345e8df13eca6bcc36d6fe40c3e90ea1ee088e
+[root@localhost ~]# isula exec b7 cat /etc/environment
+PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
+TERM=xterm
+abc=123
+```
+
+可以看到容器的env变量（abc=123）已经持久化到/etc/environment配置文件中。
+
diff --git "a/content/zh/docs/Container/\347\233\221\346\216\247\345\256\211\345\205\250\345\256\271\345\231\250.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\347\233\221\346\216\247\345\256\211\345\205\250\345\256\271\345\231\250.md"
similarity index 96%
rename from "content/zh/docs/Container/\347\233\221\346\216\247\345\256\211\345\205\250\345\256\271\345\231\250.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\347\233\221\346\216\247\345\256\211\345\205\250\345\256\271\345\231\250.md"
index 35acb6ad27a8156a9c537f7dd2bb6453cd0084f7..7e7785a55e798b064c4186b983228e9fbaec12ea 100644
--- "a/content/zh/docs/Container/\347\233\221\346\216\247\345\256\211\345\205\250\345\256\271\345\231\250.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\347\233\221\346\216\247\345\256\211\345\205\250\345\256\271\345\231\250.md"
@@ -1,144 +1,144 @@
-# 监控安全容器
-
-## 描述
-
-kata events命令用于显示指定容器状态。包括但不限于容器内存、CPU、Pid、 Blkio、大页内存、网络等信息。
-
-## 用法
-
-```
-kata-runtime events [command options] 
-```
-
-## 参数
-
--   \-- interval value：设置查询周期。如果不使用该参数，默认查询周期为5秒。
--   \--stats： 显示容器信息并退出查询。
-
-## 前置条件
-
-要查询的容器状态必须为running，否则报错：Container ID \(\) does not exist。
-
-该命令只支持查询监控一个容器的状态
-
-## 示例
-
--   每隔三秒显示容器状态。
-
-    ```
-    $ kata-runtime events --interval 3s 5779b2366f47
-    {
-        "data": {
-            "blkio": {},
-            "cpu": {
-                "throttling": {},
-                "usage": {
-                    "kernel": 130000000,
-                    "percpu": [
-                        214098440
-                    ],
-                    "total": 214098440,
-                    "user": 10000000
-                }
-            },
-            "hugetlb": {},
-            "intel_rdt": {},
-            "interfaces": [
-                {
-                    "name": "lo",
-                    "rx_bytes": 0,
-                    "rx_dropped": 0,
-                    "rx_errors": 0,
-                    "rx_packets": 0,
-                    "tx_bytes": 0,
-                    "tx_dropped": 0,
-                    "tx_errors": 0,
-                    "tx_packets": 0
-                }
-            ],
-            "memory": {
-                "cache": 827392,
-                "kernel": {
-                    "failcnt": 0,
-                    "limit": 9223372036854771712,
-                    "max": 421888,
-                    "usage": 221184
-                },
-                "kernelTCP": {
-                    "failcnt": 0,
-                    "limit": 0
-                },
-                "raw": {
-                    "active_anon": 49152,
-                    "active_file": 40960,
-                    "cache": 827392,
-                    "dirty": 0,
-                    "hierarchical_memory_limit": 9223372036854771712,
-                    "hierarchical_memsw_limit": 9223372036854771712,
-                    "inactive_anon": 0,
-                    "inactive_file": 839680,
-                    "mapped_file": 540672,
-                    "pgfault": 6765,
-                    "pgmajfault": 0,
-                    "pgpgin": 12012,
-                    "pgpgout": 11803,
-                    "rss": 4096,
-                    "rss_huge": 0,
-                    "shmem": 32768,
-                    "swap": 0,
-                    "total_active_anon": 49152,
-                    "total_active_file": 40960,
-                    "total_cache": 827392,
-                    "total_dirty": 0,
-                    "total_inactive_anon": 0,
-                    "total_inactive_file": 839680,
-                    "total_mapped_file": 540672,
-                    "total_pgfault": 6765,
-                    "total_pgmajfault": 0,
-                    "total_pgpgin": 12012,
-                    "total_pgpgout": 11803,
-                    "total_rss": 4096,
-                    "total_rss_huge": 0,
-                    "total_shmem": 32768,
-                    "total_swap": 0,
-                    "total_unevictable": 0,
-                    "total_writeback": 0,
-                    "unevictable": 0,
-                    "writeback": 0
-                },
-                "swap": {
-                    "failcnt": 0,
-                    "limit": 9223372036854771712,
-                    "max": 34201600,
-                    "usage": 1204224
-                },
-                "usage": {
-                    "failcnt": 0,
-                    "limit": 9223372036854771712,
-                    "max": 34201600,
-                    "usage": 1204224
-                }
-            },
-            "pids": {
-                "current": 1
-            },
-            "tcp": {},
-            "tcp6": {},
-            "udp": {},
-            "udp6": {}
-        },
-        "id": "5779b2366f47cd1468ebb1ba7c52cbdde3c7d3a5f2af3eefadc8356700fc860b",
-        "type": "stats"
-    }
-    ```
-
-
--   显示容器状态并立即返回
-
-    ```
-    kata-runtime events --stats 
-    ```
-
-    该命令返回内容的格式与上一条相同，区别为只显示一次信息后便退出。
-
-
+# 监控安全容器
+
+## 描述
+
+kata events命令用于显示指定容器状态。包括但不限于容器内存、CPU、Pid、 Blkio、大页内存、网络等信息。
+
+## 用法
+
+```
+kata-runtime events [command options] 
+```
+
+## 参数
+
+-   \-- interval value：设置查询周期。如果不使用该参数，默认查询周期为5秒。
+-   \--stats： 显示容器信息并退出查询。
+
+## 前置条件
+
+要查询的容器状态必须为running，否则报错：Container ID \(\) does not exist。
+
+该命令只支持查询监控一个容器的状态
+
+## 示例
+
+-   每隔三秒显示容器状态。
+
+    ```
+    $ kata-runtime events --interval 3s 5779b2366f47
+    {
+        "data": {
+            "blkio": {},
+            "cpu": {
+                "throttling": {},
+                "usage": {
+                    "kernel": 130000000,
+                    "percpu": [
+                        214098440
+                    ],
+                    "total": 214098440,
+                    "user": 10000000
+                }
+            },
+            "hugetlb": {},
+            "intel_rdt": {},
+            "interfaces": [
+                {
+                    "name": "lo",
+                    "rx_bytes": 0,
+                    "rx_dropped": 0,
+                    "rx_errors": 0,
+                    "rx_packets": 0,
+                    "tx_bytes": 0,
+                    "tx_dropped": 0,
+                    "tx_errors": 0,
+                    "tx_packets": 0
+                }
+            ],
+            "memory": {
+                "cache": 827392,
+                "kernel": {
+                    "failcnt": 0,
+                    "limit": 9223372036854771712,
+                    "max": 421888,
+                    "usage": 221184
+                },
+                "kernelTCP": {
+                    "failcnt": 0,
+                    "limit": 0
+                },
+                "raw": {
+                    "active_anon": 49152,
+                    "active_file": 40960,
+                    "cache": 827392,
+                    "dirty": 0,
+                    "hierarchical_memory_limit": 9223372036854771712,
+                    "hierarchical_memsw_limit": 9223372036854771712,
+                    "inactive_anon": 0,
+                    "inactive_file": 839680,
+                    "mapped_file": 540672,
+                    "pgfault": 6765,
+                    "pgmajfault": 0,
+                    "pgpgin": 12012,
+                    "pgpgout": 11803,
+                    "rss": 4096,
+                    "rss_huge": 0,
+                    "shmem": 32768,
+                    "swap": 0,
+                    "total_active_anon": 49152,
+                    "total_active_file": 40960,
+                    "total_cache": 827392,
+                    "total_dirty": 0,
+                    "total_inactive_anon": 0,
+                    "total_inactive_file": 839680,
+                    "total_mapped_file": 540672,
+                    "total_pgfault": 6765,
+                    "total_pgmajfault": 0,
+                    "total_pgpgin": 12012,
+                    "total_pgpgout": 11803,
+                    "total_rss": 4096,
+                    "total_rss_huge": 0,
+                    "total_shmem": 32768,
+                    "total_swap": 0,
+                    "total_unevictable": 0,
+                    "total_writeback": 0,
+                    "unevictable": 0,
+                    "writeback": 0
+                },
+                "swap": {
+                    "failcnt": 0,
+                    "limit": 9223372036854771712,
+                    "max": 34201600,
+                    "usage": 1204224
+                },
+                "usage": {
+                    "failcnt": 0,
+                    "limit": 9223372036854771712,
+                    "max": 34201600,
+                    "usage": 1204224
+                }
+            },
+            "pids": {
+                "current": 1
+            },
+            "tcp": {},
+            "tcp6": {},
+            "udp": {},
+            "udp6": {}
+        },
+        "id": "5779b2366f47cd1468ebb1ba7c52cbdde3c7d3a5f2af3eefadc8356700fc860b",
+        "type": "stats"
+    }
+    ```
+
+
+-   显示容器状态并立即返回
+
+    ```
+    kata-runtime events --stats 
+    ```
+
+    该命令返回内容的格式与上一条相同，区别为只显示一次信息后便退出。
+
+
diff --git "a/content/zh/docs/Container/\347\256\241\347\220\206\345\256\211\345\205\250\345\256\271\345\231\250\347\232\204\347\224\237\345\221\275\345\221\250\346\234\237.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\347\256\241\347\220\206\345\256\211\345\205\250\345\256\271\345\231\250\347\232\204\347\224\237\345\221\275\345\221\250\346\234\237.md"
similarity index 96%
rename from "content/zh/docs/Container/\347\256\241\347\220\206\345\256\211\345\205\250\345\256\271\345\231\250\347\232\204\347\224\237\345\221\275\345\221\250\346\234\237.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\347\256\241\347\220\206\345\256\211\345\205\250\345\256\271\345\231\250\347\232\204\347\224\237\345\221\275\345\221\250\346\234\237.md"
index 17648bbfddb7319853dd551af9a320e892548515..dce9e2e799bc6bd71df97264fe3839feca7505dc 100644
--- "a/content/zh/docs/Container/\347\256\241\347\220\206\345\256\211\345\205\250\345\256\271\345\231\250\347\232\204\347\224\237\345\221\275\345\221\250\346\234\237.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\347\256\241\347\220\206\345\256\211\345\205\250\345\256\271\345\231\250\347\232\204\347\224\237\345\221\275\345\221\250\346\234\237.md"
@@ -34,7 +34,7 @@
     isula run -tid --runtime kata-runtime --network none busybox 
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >安全容器网络使用仅支持CNI网络，不支持CNM网络，不支持使用-p和--expose暴露容器端口，使用安全容器时需指定参数--net=none。  
 
 4.  启动一个Pod
@@ -99,7 +99,7 @@ docker rm -f 
 docker exec -ti  
 ```
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >1.  如遇到docker exec -ti进入容器的同时，另一终端执行docker restart或者docker stop命令造成exec界面卡住的情况，可使用Ctrl+P+Q退出docker exec操作界面。  
 >2.  如果使用-d参数则命令在后台执行，不会打印错误信息，其退出码也不能作为命令执行是否正确的判断依据。  
 
diff --git "a/content/zh/docs/Container/\347\263\273\347\273\237\345\256\271\345\231\250.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\347\263\273\347\273\237\345\256\271\345\231\250.md"
similarity index 99%
rename from "content/zh/docs/Container/\347\263\273\347\273\237\345\256\271\345\231\250.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\347\263\273\347\273\237\345\256\271\345\231\250.md"
index f9432195d79c18e57e4f49fe5094a2be80aea1c4..9990642dc705743d0b96b5dd53930e30b3984431 100644
--- "a/content/zh/docs/Container/\347\263\273\347\273\237\345\256\271\345\231\250.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\347\263\273\347\273\237\345\256\271\345\231\250.md"
@@ -1,2 +1,2 @@
-# 系统容器
+# 系统容器
 系统容器主要应对在重计算、高性能、大并发的场景下，重型应用和业务云化的问题。相比较虚拟机技术，系统容器可直接继承物理机特性，同时具备性能更优良，较少overhead的优点。从系统资源分配来看，系统容器在有限资源上相比虚拟机可分配更多计算单元，降低成本，通过系统容器可以构建产品的差异化竞争力，提供计算密度更高，价格更便宜，性能更优良的的计算单元实例。
\ No newline at end of file
diff --git "a/content/zh/docs/Container/\347\273\237\350\256\241\344\277\241\346\201\257-4.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\347\273\237\350\256\241\344\277\241\346\201\257-4.md"
similarity index 100%
rename from "content/zh/docs/Container/\347\273\237\350\256\241\344\277\241\346\201\257-4.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\347\273\237\350\256\241\344\277\241\346\201\257-4.md"
diff --git "a/content/zh/docs/Container/\351\200\232\350\277\207systemd\345\220\257\345\212\250\345\256\271\345\231\250.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\351\200\232\350\277\207systemd\345\220\257\345\212\250\345\256\271\345\231\250.md"
similarity index 98%
rename from "content/zh/docs/Container/\351\200\232\350\277\207systemd\345\220\257\345\212\250\345\256\271\345\231\250.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\351\200\232\350\277\207systemd\345\220\257\345\212\250\345\256\271\345\231\250.md"
index 401fe4720d49081620d8808d069728b6c042be46..a70e8dc59002233c3ddddb0a67c315f919c28b0d 100644
--- "a/content/zh/docs/Container/\351\200\232\350\277\207systemd\345\220\257\345\212\250\345\256\271\345\231\250.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\351\200\232\350\277\207systemd\345\220\257\345\212\250\345\256\271\345\231\250.md"
@@ -1,12 +1,12 @@
-# 通过systemd启动容器
-
-## 功能描述
-
-系统容器与普通容器最大的差异就在于容器启动的init进程，普通容器无法通过systemd启动系统服务，而系统容器具备这个能力，通过在启动容器时指定\--system-contianer参数可以使能systemd服务。
-
-## 参数说明
-
-
+# 通过systemd启动容器
+
+## 功能描述
+
+系统容器与普通容器最大的差异就在于容器启动的init进程，普通容器无法通过systemd启动系统服务，而系统容器具备这个能力，通过在启动容器时指定\--system-contianer参数可以使能systemd服务。
+
+## 参数说明
+
+
 
-
命令

 		
 
参数

@@ -23,66 +23,66 @@
 
 

 

-
-## 约束限制
-
--   systemd服务需要调用一些特殊系统调用，包括mount、umount2、unshare、reboot以及name\_to\_handle\_at，所以在不开启特权容器标签的情况下，系统容器打开了调用上述接口的权限。
--   系统容器都是init启动，init进程不响应表示正常退出的SIGTERM信号，stop默认在10s之后才会强制杀死容器。如果需要快速结束，可以手动指定stop的超时时间。
--   \--system-container必须配合\--external-rootfs参数一起使用。
--   系统容器内支持运行各类服务，服务的启停通过systemctl来管理，服务之间可能会出现相互依赖关系导致异常情况下某些服务进程出现D/Z状态，使得容器无法正常退出。
--   系统容器内的某些服务进程可能会影响其它操作结果，例如容器内若运行了NetworkManager服务，可能会影响向容器添加网卡的行为（网卡添加成功然后被NetworkManger停掉），导致不可预期的结果。
--   系统容器和主机暂时无法实现udev事件隔离，所以fstab配置也暂不支持。
--   systemd服务可能和libcgroup提供的cgconfig服务在功能上出现冲突，建议在容器内去掉libcgroup相关的包或者配置cgconfig服务的Delegate值为no。
-
-## 使用示例
-
--   指定\--system-container和\--external-rootfs参数启动系统容器。
-
-    ```
-    [root@localhost ~]# isula run -tid -n systest01 --system-container --external-rootfs /root/myrootfs none init
-    ```
-
--   执行以上命令后容器成功运行，通过exec进容器查看进程信息，可看到systemd服务已启动。
-
-    ```
-    [root@localhost ~]# isula exec -it systest01 bash
-    [root@localhost /]# ps -ef
-    UID        PID  PPID  C STIME TTY          TIME CMD
-    root         1     0  2 06:49 ?        00:00:00 init
-    root        14     1  2 06:49 ?        00:00:00 /usr/lib/systemd/systemd-journal
-    root        16     1  0 06:49 ?        00:00:00 /usr/lib/systemd/systemd-network
-    dbus        23     1  0 06:49 ?        00:00:00 /usr/bin/dbus-daemon --system --
-    root        25     0  0 06:49 ?        00:00:00 bash
-    root        59    25  0 06:49 ?        00:00:00 ps –ef
-    ```
-
-
--   容器内执行systemctl命令查看服务状态，可看到服务被systemd管理。
-
-    ```
-    [root@localhost /]# systemctl status dbus
-    ● dbus.service - D-Bus System Message Bus
-       Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset:
-    disabled)
-       Active: active (running) since Mon 2019-07-22 06:49:38 UTC; 2min 5
-    8s ago
-         Docs: man:dbus-daemon(1)
-     Main PID: 23 (dbus-daemon)
-       CGroup: /system.slice/dbus.service
-               └─23 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidf
-    ile --systemd-activation --syslog-only
-     
-    Jul 22 06:49:38 localhost systemd[1]: Started D-Bus System Message Bus.
-    ```
-
--   容器内通过systemctl stop/start服务，可看到服务被systemd管理。
-
-    ```
-    [root@localhost /]# systemctl stop dbus
-    Warning: Stopping dbus.service, but it can still be activated by:
-      dbus.socket
-    [root@localhost /]# systemctl start dbus
-    ```
-
-
+
+
+## 约束限制
+
+-   systemd服务需要调用一些特殊系统调用，包括mount、umount2、unshare、reboot以及name\_to\_handle\_at，所以在不开启特权容器标签的情况下，系统容器打开了调用上述接口的权限。
+-   系统容器都是init启动，init进程不响应表示正常退出的SIGTERM信号，stop默认在10s之后才会强制杀死容器。如果需要快速结束，可以手动指定stop的超时时间。
+-   \--system-container必须配合\--external-rootfs参数一起使用。
+-   系统容器内支持运行各类服务，服务的启停通过systemctl来管理，服务之间可能会出现相互依赖关系导致异常情况下某些服务进程出现D/Z状态，使得容器无法正常退出。
+-   系统容器内的某些服务进程可能会影响其它操作结果，例如容器内若运行了NetworkManager服务，可能会影响向容器添加网卡的行为（网卡添加成功然后被NetworkManger停掉），导致不可预期的结果。
+-   系统容器和主机暂时无法实现udev事件隔离，所以fstab配置也暂不支持。
+-   systemd服务可能和libcgroup提供的cgconfig服务在功能上出现冲突，建议在容器内去掉libcgroup相关的包或者配置cgconfig服务的Delegate值为no。
+
+## 使用示例
+
+-   指定\--system-container和\--external-rootfs参数启动系统容器。
+
+    ```
+    [root@localhost ~]# isula run -tid -n systest01 --system-container --external-rootfs /root/myrootfs none init
+    ```
+
+-   执行以上命令后容器成功运行，通过exec进容器查看进程信息，可看到systemd服务已启动。
+
+    ```
+    [root@localhost ~]# isula exec -it systest01 bash
+    [root@localhost /]# ps -ef
+    UID        PID  PPID  C STIME TTY          TIME CMD
+    root         1     0  2 06:49 ?        00:00:00 init
+    root        14     1  2 06:49 ?        00:00:00 /usr/lib/systemd/systemd-journal
+    root        16     1  0 06:49 ?        00:00:00 /usr/lib/systemd/systemd-network
+    dbus        23     1  0 06:49 ?        00:00:00 /usr/bin/dbus-daemon --system --
+    root        25     0  0 06:49 ?        00:00:00 bash
+    root        59    25  0 06:49 ?        00:00:00 ps –ef
+    ```
+
+
+-   容器内执行systemctl命令查看服务状态，可看到服务被systemd管理。
+
+    ```
+    [root@localhost /]# systemctl status dbus
+    ● dbus.service - D-Bus System Message Bus
+       Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset:
+    disabled)
+       Active: active (running) since Mon 2019-07-22 06:49:38 UTC; 2min 5
+    8s ago
+         Docs: man:dbus-daemon(1)
+     Main PID: 23 (dbus-daemon)
+       CGroup: /system.slice/dbus.service
+               └─23 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidf
+    ile --systemd-activation --syslog-only
+     
+    Jul 22 06:49:38 localhost systemd[1]: Started D-Bus System Message Bus.
+    ```
+
+-   容器内通过systemctl stop/start服务，可看到服务被systemd管理。
+
+    ```
+    [root@localhost /]# systemctl stop dbus
+    Warning: Stopping dbus.service, but it can still be activated by:
+      dbus.socket
+    [root@localhost /]# systemctl start dbus
+    ```
+
+
diff --git "a/content/zh/docs/Container/\351\225\234\345\203\217\347\256\241\347\220\206-3.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\351\225\234\345\203\217\347\256\241\347\220\206-3.md"
similarity index 100%
rename from "content/zh/docs/Container/\351\225\234\345\203\217\347\256\241\347\220\206-3.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\351\225\234\345\203\217\347\256\241\347\220\206-3.md"
diff --git "a/content/zh/docs/Container/\351\225\234\345\203\217\347\256\241\347\220\206-4.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\351\225\234\345\203\217\347\256\241\347\220\206-4.md"
similarity index 100%
rename from "content/zh/docs/Container/\351\225\234\345\203\217\347\256\241\347\220\206-4.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\351\225\234\345\203\217\347\256\241\347\220\206-4.md"
diff --git "a/content/zh/docs/Container/\351\225\234\345\203\217\347\256\241\347\220\206.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\351\225\234\345\203\217\347\256\241\347\220\206.md"
similarity index 87%
rename from "content/zh/docs/Container/\351\225\234\345\203\217\347\256\241\347\220\206.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\351\225\234\345\203\217\347\256\241\347\220\206.md"
index f89089da77ba00f09e2892adc50a9e7a179289b9..386ef9bf53c523e77117c1c1054beb4236ff88d5 100644
--- "a/content/zh/docs/Container/\351\225\234\345\203\217\347\256\241\347\220\206.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\351\225\234\345\203\217\347\256\241\347\220\206.md"
@@ -1,420 +1,377 @@
-# 镜像管理
-
-
-
-- [镜像管理](#镜像管理)
-    - [docker镜像管理](#docker镜像管理)
-        - [登录到镜像仓库](#登录到镜像仓库)
-        - [从镜像仓库退出登录](#从镜像仓库退出登录)
-        - [从镜像仓库拉取镜像](#从镜像仓库拉取镜像)
-        - [删除镜像](#删除镜像)
-        - [加载镜像](#加载镜像)
-        - [列出镜像](#列出镜像)
-        - [检视镜像](#检视镜像)
-        - [双向认证](#双向认证)
-    - [embedded镜像管理](#embedded镜像管理)
-        - [加载镜像](#加载镜像-1)
-        - [列出镜像](#列出镜像-1)
-        - [检视镜像](#检视镜像-1)
-        - [删除镜像](#删除镜像-1)
-
-
-
-
-## docker镜像管理
-
-### 登录到镜像仓库
-
-#### 描述
-
-isula login命令用于登录到镜像仓库。登录成功后可以使用isula pull命令从该镜像仓库拉取镜像。如果镜像仓库不需要密码，则拉取镜像前不需要执行该命令。
-
-#### 用法
-
-```
-isula login [OPTIONS] SERVER
-```
-
-#### 参数
-
-login命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表1 表1-20 login命令参数列表" 。
-
-#### 示例
-
-```
-$ isula login -u abc my.csp-edge.com:5000
-
-Login Succeeded
-```
-
-### 从镜像仓库退出登录
-
-#### 描述
-
-isula logout命令用于从镜像仓库退出登录。退出登录成功后再执行isula pull命令从该镜像仓库拉取镜像会因为未认证而拉取失败。
-
-#### 用法
-
-```
-isula logout SERVER
-```
-
-#### 参数
-
-logout命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表2 logout命令参数列表"。
-
-#### 示例
-
-```
-$ isula logout my.csp-edge.com:5000
-Logout Succeeded
-```
-
-### 从镜像仓库拉取镜像
-
-#### 描述
-
-从镜像仓库拉取镜像到本地。
-
-#### 用法
-
-```
-isula pull [OPTIONS] NAME[:TAG|@DIGEST]
-```
-
-#### 参数
-
-login命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表3 pull命令参数列表"。
-
-#### 示例
-
-```
-$ isula pull localhost:5000/official/busybox
-Image "localhost:5000/official/busybox" pulling
-Image "localhost:5000/official/busybox@sha256:bf510723d2cd2d4e3f5ce7e93bf1e52c8fd76831995ac3bd3f90ecc866643aff" pulled
-```
-
-### 删除镜像
-
-#### 描述
-
-删除一个或多个镜像。
-
-#### 用法
-
-```
-isula rmi [OPTIONS] IMAGE [IMAGE...]
-```
-
-#### 参数
-
-rmi命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表4 rmi命令参数列表"。
-
-#### 示例
-
-```
-$ isula rmi rnd-dockerhub.huawei.com/official/busybox
-Image "rnd-dockerhub.huawei.com/official/busybox" removed
-```
-
-### 加载镜像
-
-#### 描述
-
-从一个tar包加载镜像。该tar包必须是使用docker save命令导出的tar包或格式一致的tar包。
-
-#### 用法
-
-```
-isula load [OPTIONS]
-```
-
-#### 参数
-
-load命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表5 load命令参数列表"。
-
-#### 示例
-
-```
-$ isula load -i busybox.tar
-Load image from "/root/busybox.tar" success
-```
-
-### 列出镜像
-
-#### 描述
-
-列出当前环境中所有镜像。
-
-#### 用法
-
-```
-isula images
-```
-
-#### 参数
-
-images命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表6 images命令参数列表"。
-
-#### 示例
-
-```
-$ isula images
-REF                                              IMAGE ID             CREATED              SIZE
-rnd-dockerhub.huawei.com/official/busybox:latest e4db68de4ff2         2019-06-15 08:19:54  1.376 MB
-```
-
-### 检视镜像
-
-#### 描述
-
-返回该镜像的配置信息。可以使用-f参数过滤出需要的信息。
-
-#### 用法
-
-```
-isula inspect [options] CONTAINER|IMAGE [CONTAINER|IMAGE...]
-```
-
-#### 参数
-
-inspect命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表7 inspect命令参数列表"。
-
-#### 示例
-
-```
-$ isula inspect -f "{{json .image.id}}" rnd-dockerhub.huawei.com/official/busybox
-"e4db68de4ff27c2adfea0c54bbb73a61a42f5b667c326de4d7d5b19ab71c6a3b"
-```
-
-### 双向认证
-
-#### 描述
-
-开启该功能后isulad和镜像仓库之间的通信采用https通信，isulad和镜像仓库都会验证对方的合法性。
-
-#### 用法
-
-要支持该功能，需要镜像仓库支持该功能，同时isulad也需要做相应的配置：
-
-1.  修改isulad的配置\(默认路径/etc/isulad/daemon.json\)，将配置里的use-decrypted-key项配置为false。
-2.  需要将相关的证书放置到/etc/isulad/certs.d目录下对应的镜像仓库命名的文件夹下，证书具体的生成方法见docker的官方链接：
-    -   [https://docs.docker.com/engine/security/certificates/](https://docs.docker.com/engine/security/certificates/)
-    -   [https://docs.docker.com/engine/security/https/](https://docs.docker.com/engine/security/https/)
-
-
-1.  执行systemctl restart isulad重启isulad。
-
-#### 参数
-
-可以在/etc/isulad/daemon.json中配置参数，也可以在启动isulad时携带参数：
-
-```
-isulad --use-decrypted-key=false
-```
-
-#### 示例
-
-配置use-decrypted-key参数为false
-
-```
-$ cat /etc/isulad/daemon.json
-{
-    "group": "isulad",
-    "graph": "/var/lib/isulad",
-    "state": "/var/run/isulad",
-    "engine": "lcr",
-    "log-level": "ERROR",
-    "pidfile": "/var/run/isulad.pid",
-    "log-opts": {
-        "log-file-mode": "0600",
-        "log-path": "/var/lib/isulad",
-        "max-file": "1",
-        "max-size": "30KB"
-    },
-    "log-driver": "stdout",
-    "hook-spec": "/etc/default/isulad/hooks/default.json",
-    "start-timeout": "2m",
-    "storage-driver": "overlay2",
-    "storage-opts": [
-        "overlay2.override_kernel_check=true"
-    ],
-    "registry-mirrors": [
-        "docker.io"
-    ],
-    "insecure-registries": [
-        "rnd-dockerhub.huawei.com"
-    ],
-    "pod-sandbox-image": "",
-    "image-opt-timeout": "5m",
-    "native.umask": "secure",
-    "network-plugin": "",
-    "cni-bin-dir": "",
-    "cni-conf-dir": "",
-    "image-layer-check": false,
-    "use-decrypted-key": false,
-    "insecure-skip-verify-enforce": false
-}
-```
-
-将证书放到对应的目录下
-
-```
-$ pwd
-/etc/isulad/certs.d/my.csp-edge.com:5000
-$ ls
-ca.crt  tls.cert  tls.key
-```
-
-重启isulad
-
-```
-$ systemctl restart isulad
-```
-
-执行pull命令从仓库下载镜像
-
-```
-$ isula pull my.csp-edge.com:5000/busybox
-Image "my.csp-edge.com:5000/busybox" pulling
-Image "my.csp-edge.com:5000/busybox@sha256:f1bdc62115dbfe8f54e52e19795ee34b4473babdeb9bc4f83045d85c7b2ad5c0" pulled
-```
-
-## embedded镜像管理
-
-### 加载镜像
-
-#### 描述
-
-根据embedded镜像的manifest加载镜像。注意--type的值必须填写embedded。
-
-#### 用法
-
-```
-isula load [OPTIONS] --input=FILE --type=TYPE
-```
-
-#### 参数
-
-load命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表5 load命令参数列表"。
-
-#### 示例
-
-```
-$ isula load -i test.manifest --type embedded
-Load image from "/root/work/bugfix/tmp/ci_testcase_data/embedded/img/test.manifest" success
-```
-
-### 列出镜像
-
-#### 描述
-
-列出当前环境中所有镜像。
-
-#### 用法
-
-```
-isula images [OPTIONS]
-```
-
-#### 参数
-
-images命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表6 images命令参数列表"。
-
-#### 示例
-
-```
-$ isula images
-REF                            IMAGE ID             CREATED              SIZE
-test:v1                        9319da1f5233         2018-03-01 10:55:44  1.273 MB
-```
-
-### 检视镜像
-
-#### 描述
-
-返回该镜像的配置信息。可以使用-f参数过滤出需要的信息。
-
-#### 用法
-
-```
-isula inspect [options] CONTAINER|IMAGE [CONTAINER|IMAGE...]
-```
-
-#### 参数
-
-inspect命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表7 inspect命令参数列表"。
-
-#### 示例
-
-```
-$ isula inspect -f "{{json .created}}" test:v1
-"2018-03-01T15:55:44.322987811Z"
-```
-
-### 删除镜像
-
-#### 描述
-
-删除一个或多个镜像。
-
-#### 用法
-
-```
-isula rmi [OPTIONS] IMAGE [IMAGE...]
-```
-
-#### 参数
-
-rmi命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表4 rmi命令参数列表"。
-
-#### 示例
-
-```
-$ isula rmi test:v1
-Image "test:v1" removed
-```
-
-### 添加名称
-
-#### 描述
-
-给镜像添加一个名称。
-
-#### 用法
-
-```
-isula tag SOURCE_IMAGE[:TAG] TARGET_IMAGE[:TAG]
-```
-
-#### 参数
-
-tag命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表8 tag命令参数列表"。
-
-#### 示例
-
-```
-$ isula tag test:v1 test:v2
-```
-
-### 导入镜像
-
-#### 描述
-
-将tar格式的rootfs导入生成一个新的镜像，该tar包必须是通过export命令导出的tar包。
-
-#### 用法
-
-```
-isula export [command options] [ID|NAME]
-```
-
-#### 参数
-
-export命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表9 export命令参数列表"。
-
-#### 示例
-
-```
-$ isula export -o test.tar containername
-```
+# 镜像管理
+
+
+
+- [镜像管理](#镜像管理)
+    - [docker镜像管理](#docker镜像管理)
+        - [登录到镜像仓库](#登录到镜像仓库)
+        - [从镜像仓库退出登录](#从镜像仓库退出登录)
+        - [从镜像仓库拉取镜像](#从镜像仓库拉取镜像)
+        - [删除镜像](#删除镜像)
+        - [加载镜像](#加载镜像)
+        - [列出镜像](#列出镜像)
+        - [检视镜像](#检视镜像)
+        - [双向认证](#双向认证)
+    - [embedded镜像管理](#embedded镜像管理)
+        - [加载镜像](#加载镜像-1)
+        - [列出镜像](#列出镜像-1)
+        - [检视镜像](#检视镜像-1)
+        - [删除镜像](#删除镜像-1)
+
+
+
+
+## docker镜像管理
+
+### 登录到镜像仓库
+
+#### 描述
+
+isula login命令用于登录到镜像仓库。登录成功后可以使用isula pull命令从该镜像仓库拉取镜像。如果镜像仓库不需要密码，则拉取镜像前不需要执行该命令。
+
+#### 用法
+
+```
+isula login [OPTIONS] SERVER
+```
+
+#### 参数
+
+login命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表1 表1-20 login命令参数列表" 。
+
+#### 示例
+
+```
+$ isula login -u abc my.csp-edge.com:5000
+
+Login Succeeded
+```
+
+### 从镜像仓库退出登录
+
+#### 描述
+
+isula logout命令用于从镜像仓库退出登录。退出登录成功后再执行isula pull命令从该镜像仓库拉取镜像会因为未认证而拉取失败。
+
+#### 用法
+
+```
+isula logout SERVER
+```
+
+#### 参数
+
+logout命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表2 logout命令参数列表"。
+
+#### 示例
+
+```
+$ isula logout my.csp-edge.com:5000
+Logout Succeeded
+```
+
+### 从镜像仓库拉取镜像
+
+#### 描述
+
+从镜像仓库拉取镜像到本地。
+
+#### 用法
+
+```
+isula pull [OPTIONS] NAME[:TAG|@DIGEST]
+```
+
+#### 参数
+
+login命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表3 pull命令参数列表"。
+
+#### 示例
+
+```
+$ isula pull localhost:5000/official/busybox
+Image "localhost:5000/official/busybox" pulling
+Image "localhost:5000/official/busybox@sha256:bf510723d2cd2d4e3f5ce7e93bf1e52c8fd76831995ac3bd3f90ecc866643aff" pulled
+```
+
+### 删除镜像
+
+#### 描述
+
+删除一个或多个镜像。
+
+#### 用法
+
+```
+isula rmi [OPTIONS] IMAGE [IMAGE...]
+```
+
+#### 参数
+
+rmi命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表4 rmi命令参数列表"。
+
+#### 示例
+
+```
+$ isula rmi rnd-dockerhub.huawei.com/official/busybox
+Image "rnd-dockerhub.huawei.com/official/busybox" removed
+```
+
+### 加载镜像
+
+#### 描述
+
+从一个tar包加载镜像。该tar包必须是使用docker save命令导出的tar包或格式一致的tar包。
+
+#### 用法
+
+```
+isula load [OPTIONS]
+```
+
+#### 参数
+
+load命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表5 load命令参数列表"。
+
+#### 示例
+
+```
+$ isula load -i busybox.tar
+Load image from "/root/busybox.tar" success
+```
+
+### 列出镜像
+
+#### 描述
+
+列出当前环境中所有镜像。
+
+#### 用法
+
+```
+isula images
+```
+
+#### 参数
+
+images命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表6 images命令参数列表"。
+
+#### 示例
+
+```
+$ isula images
+REF                                              IMAGE ID             CREATED              SIZE
+rnd-dockerhub.huawei.com/official/busybox:latest e4db68de4ff2         2019-06-15 08:19:54  1.376 MB
+```
+
+### 检视镜像
+
+#### 描述
+
+返回该镜像的配置信息。可以使用-f参数过滤出需要的信息。
+
+#### 用法
+
+```
+isula inspect [options] CONTAINER|IMAGE [CONTAINER|IMAGE...]
+```
+
+#### 参数
+
+inspect命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表7 inspect命令参数列表"。
+
+#### 示例
+
+```
+$ isula inspect -f "{{json .image.id}}" rnd-dockerhub.huawei.com/official/busybox
+"e4db68de4ff27c2adfea0c54bbb73a61a42f5b667c326de4d7d5b19ab71c6a3b"
+```
+
+### 双向认证
+
+#### 描述
+
+开启该功能后isulad和镜像仓库之间的通信采用https通信，isulad和镜像仓库都会验证对方的合法性。
+
+#### 用法
+
+要支持该功能，需要镜像仓库支持该功能，同时isulad也需要做相应的配置：
+
+1.  修改isulad的配置\(默认路径/etc/isulad/daemon.json\)，将配置里的use-decrypted-key项配置为false。
+2.  需要将相关的证书放置到/etc/isulad/certs.d目录下对应的镜像仓库命名的文件夹下，证书具体的生成方法见docker的官方链接：
+    -   [https://docs.docker.com/engine/security/certificates/](https://docs.docker.com/engine/security/certificates/)
+    -   [https://docs.docker.com/engine/security/https/](https://docs.docker.com/engine/security/https/)
+
+
+1.  执行systemctl restart isulad重启isulad。
+
+#### 参数
+
+可以在/etc/isulad/daemon.json中配置参数，也可以在启动isulad时携带参数：
+
+```
+isulad --use-decrypted-key=false
+```
+
+#### 示例
+
+配置use-decrypted-key参数为false
+
+```
+$ cat /etc/isulad/daemon.json
+{
+    "group": "isulad",
+    "graph": "/var/lib/isulad",
+    "state": "/var/run/isulad",
+    "engine": "lcr",
+    "log-level": "ERROR",
+    "pidfile": "/var/run/isulad.pid",
+    "log-opts": {
+        "log-file-mode": "0600",
+        "log-path": "/var/lib/isulad",
+        "max-file": "1",
+        "max-size": "30KB"
+    },
+    "log-driver": "stdout",
+    "hook-spec": "/etc/default/isulad/hooks/default.json",
+    "start-timeout": "2m",
+    "storage-driver": "overlay2",
+    "storage-opts": [
+        "overlay2.override_kernel_check=true"
+    ],
+    "registry-mirrors": [
+        "docker.io"
+    ],
+    "insecure-registries": [
+        "rnd-dockerhub.huawei.com"
+    ],
+    "pod-sandbox-image": "",
+    "image-opt-timeout": "5m",
+    "native.umask": "secure",
+    "network-plugin": "",
+    "cni-bin-dir": "",
+    "cni-conf-dir": "",
+    "image-layer-check": false,
+    "use-decrypted-key": false,
+    "insecure-skip-verify-enforce": false
+}
+```
+
+将证书放到对应的目录下
+
+```
+$ pwd
+/etc/isulad/certs.d/my.csp-edge.com:5000
+$ ls
+ca.crt  tls.cert  tls.key
+```
+
+重启isulad
+
+```
+$ systemctl restart isulad
+```
+
+执行pull命令从仓库下载镜像
+
+```
+$ isula pull my.csp-edge.com:5000/busybox
+Image "my.csp-edge.com:5000/busybox" pulling
+Image "my.csp-edge.com:5000/busybox@sha256:f1bdc62115dbfe8f54e52e19795ee34b4473babdeb9bc4f83045d85c7b2ad5c0" pulled
+```
+
+## embedded镜像管理
+
+### 加载镜像
+
+#### 描述
+
+根据embedded镜像的manifest加载镜像。注意--type的值必须填写embedded。
+
+#### 用法
+
+```
+isula load [OPTIONS] --input=FILE --type=TYPE
+```
+
+#### 参数
+
+load命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表5 load命令参数列表"。
+
+#### 示例
+
+```
+$ isula load -i test.manifest --type embedded
+Load image from "/root/work/bugfix/tmp/ci_testcase_data/embedded/img/test.manifest" success
+```
+
+### 列出镜像
+
+#### 描述
+
+列出当前环境中所有镜像。
+
+#### 用法
+
+```
+isula images [OPTIONS]
+```
+
+#### 参数
+
+images命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表6 images命令参数列表"。
+
+#### 示例
+
+```
+$ isula images
+REF                            IMAGE ID             CREATED              SIZE
+test:v1                        9319da1f5233         2018-03-01 10:55:44  1.273 MB
+```
+
+### 检视镜像
+
+#### 描述
+
+返回该镜像的配置信息。可以使用-f参数过滤出需要的信息。
+
+#### 用法
+
+```
+isula inspect [options] CONTAINER|IMAGE [CONTAINER|IMAGE...]
+```
+
+#### 参数
+
+inspect命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表7 inspect命令参数列表"。
+
+#### 示例
+
+```
+$ isula inspect -f "{{json .created}}" test:v1
+"2018-03-01T15:55:44.322987811Z"
+```
+
+### 删除镜像
+
+#### 描述
+
+删除一个或多个镜像。
+
+#### 用法
+
+```
+isula rmi [OPTIONS] IMAGE [IMAGE...]
+```
+
+#### 参数
+
+rmi命令支持参数请参见"附录 > 命令行参数说明" 章节的 "表4 rmi命令参数列表"。
+
+#### 示例
+
+```
+$ isula rmi test:v1
+Image "test:v1" removed
+```
+
diff --git "a/content/zh/docs/Container/\351\231\204\345\275\225-2.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\351\231\204\345\275\225-2.md"
similarity index 100%
rename from "content/zh/docs/Container/\351\231\204\345\275\225-2.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\351\231\204\345\275\225-2.md"
diff --git "a/content/zh/docs/Container/\351\231\204\345\275\225-3.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\351\231\204\345\275\225-3.md"
similarity index 99%
rename from "content/zh/docs/Container/\351\231\204\345\275\225-3.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\351\231\204\345\275\225-3.md"
index 0e73dca0d1fbe538ba4ae637e6c434d9676cd229..ae47613246784147f91d844289ac99e09eed616a 100644
--- "a/content/zh/docs/Container/\351\231\204\345\275\225-3.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\351\231\204\345\275\225-3.md"
@@ -5,7 +5,7 @@
 
 ## configuration-toml配置说明
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >configuration.toml配置文件中各个字段的取值以kata-containers-.rpm包中的configuration.toml文件为准，不支持用户对配置文件中的字段任意取值。  
 
 ```
@@ -133,7 +133,7 @@ experimental ：开启实验特性，不支持用户自定义配置
 
 
设置网卡的容器内名称

 
-
必选。支持字母、数字、下划线“_”、“-” 以及“.”字符，必须以字母开头，且长度不超过15。需要确保同一个Sandbox内name不能重复。

+
必选。支持字母、数字、下划线“\_”、“-” 以及“.”字符，必须以字母开头，且长度不超过15。需要确保同一个Sandbox内name不能重复。

 
 
 
IPAddresses

diff --git "a/content/zh/docs/Container/\351\231\204\345\275\225.md" "b/docs/zh/docs/20.03_LTS/docs/Container/\351\231\204\345\275\225.md"
similarity index 94%
rename from "content/zh/docs/Container/\351\231\204\345\275\225.md"
rename to "docs/zh/docs/20.03_LTS/docs/Container/\351\231\204\345\275\225.md"
index 0757c9f93bbaac874755bff8e0293fdc40c608c8..858096ce5f302f179f7831fae4b0cfc04fe604a4 100644
--- "a/content/zh/docs/Container/\351\231\204\345\275\225.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Container/\351\231\204\345\275\225.md"
@@ -214,51 +214,6 @@
 
 
 
-**表 8**  tag命令参数列表
-
-
-
-
-
-
-
-
-
-
-
-
命令

-
参数

-
说明

-
tag

-
-H, --host

-
指定要连接的iSulad socket文件路径

-

-
-

-
-**表 9**  import命令参数列表
-
-
-
-
-
-
-
-
-
-
-
-
命令

-
参数

-
说明

-
import

-
-H, --host

-
指定要连接的iSulad socket文件路径

-

-
-

-
-
 ## CNI配置参数
 
 **表 1**  CNI单网络配置参数
diff --git a/content/zh/docs/Installation/FAQ.md b/docs/zh/docs/20.03_LTS/docs/Installation/FAQ.md
similarity index 94%
rename from content/zh/docs/Installation/FAQ.md
rename to docs/zh/docs/20.03_LTS/docs/Installation/FAQ.md
index 07a428057c41869e9b8ead8489e8b4d764cb543f..f5a869a4e7700852f4ef7459e12ab52f553d69e2 100644
--- a/content/zh/docs/Installation/FAQ.md
+++ b/docs/zh/docs/20.03_LTS/docs/Installation/FAQ.md
@@ -41,7 +41,7 @@ NetworkManager、network两个服务均是网络服务管理包，两个服务
 
 -   如果使用NetworkManager管理服务，则必须使用nmcli命令或修改配置文件来配置网络（如IP、路由等），而不能使用ip/ifconfig/route命令来配置。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >在开启NetworkManager服务的场景下，使用ip/ifconfig/route等命令配置网络，则一段时间后配置会被NetworkManager覆盖，导致 ip/ifconfig/route配置不生效。  
 
     查看NetworkManager 服务是否开启：
@@ -50,7 +50,7 @@ NetworkManager、network两个服务均是网络服务管理包，两个服务
     systemctl status NetworkManager
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >nmcli命令使用参考“nmcli \--help”或者“man  nmcli”。  
 
 -   如果要使用ip/ifconfig/route等命令来管理网络，请先关闭NetworkManager服务，使用如下命令：
@@ -66,7 +66,7 @@ NetworkManager、network两个服务均是网络服务管理包，两个服务
 
 openEuler系统开机后进入emergency模式，如下图所示：
 
-![](figures/zh-cn_image_0229291264.jpg)
+![](./figures/zh-cn_image_0229291264.jpg)
 
 ### 原因分析
 
@@ -79,7 +79,7 @@ openEuler系统开机后进入emergency模式，如下图所示：
 1.  用户直接输入root账号的密码，登录系统。
 2.  使用fsck工具，检测并修复文件系统，然后重启。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >fsck（file system check）用来检查和维护不一致的文件系统。若系统掉电或磁盘发生问题，可利用fsck命令对文件系统进行检查。 用户可以通过“fsck.ext3 -h”、“fsck.ext4 -h”命令查看fsck的使用方法。  
 
 
@@ -167,7 +167,7 @@ UUID=afcc811f-4b20-42fc-9d31-7307a8cfe0df /boot ext4 defaults,x-systemd.device-t
 
 执行systemctl status kdump命令，显示状态信息如下，提示无预留内存。
 
-![](figures/zh-cn_image_0229291280.png)
+![](./figures/zh-cn_image_0229291280.png)
 
 ### 原因分析
 
@@ -187,7 +187,7 @@ kdump服务需要系统预留一段内存用于运行kdump内核，而当前系
 
     若回显如下，即kdump的状态为active，说明kdump已使能，操作结束。
 
-    ![](figures/zh-cn_image_0229291272.png)
+    ![](./figures/zh-cn_image_0229291272.png)
 
 
 ### 参数说明
@@ -254,7 +254,7 @@ kdump内核预留内存参数说明如下：
 在安装系统时，如果之前的系统选择多块磁盘组成逻辑卷进行安装，再次安装时，如果只选择了其中的一块或几块磁盘，没有全部选择，在保存配置时提示配置错误，如[图1](#fig115949762617)所示。
 
 **图 1**  配置错误提示  
-![](figures/配置错误提示.png "配置错误提示")
+![](./figures/Configuration_error_prompt.png)
 
 ### 原因分析
 
@@ -270,7 +270,7 @@ kdump内核预留内存参数说明如下：
     vgs
     ```
 
-    ![](figures/zh-cn_image_0231657950.png)
+    ![](./figures/zh-cn_image_0231657950.png)
 
 2.  执行如下命令，删除卷组。
 
@@ -284,7 +284,7 @@ kdump内核预留内存参数说明如下：
     systemctl restart anaconda
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >图形模式下也可以按“Ctrl+Alt+F6”回到图形界面，点击[图1](#fig115949762617)右下角的“Refresh”刷新存储配置生效。  
 
 
@@ -295,7 +295,7 @@ kdump内核预留内存参数说明如下：
 x86物理机安装系统时，由于设置了BIOS选项security boot 为enable（默认是disable），导致系统一直停留在“No bootable device”提示界面，无法继续安装，如[图2](#fig115949762617)所示。
 
 **图 2**  “No bootable device”提示界面  
-![](figures/No-bootable-device-提示界面.png "No-bootable-device-提示界面")
+![](./figures/No-bootable-device.png)
 
 ### 原因分析
 
@@ -307,16 +307,16 @@ x86物理机安装系统时，由于设置了BIOS选项security boot 为enable
 
 1.  系统启动时，按“F11”，输入密码“Admin@9000”进入BIOS。
 
-    ![](figures/BIOS.png)
+    ![](./figures/BIOS.png)
 
 2.  选择进入Administer Secure Boot。
 
-    ![](figures/security.png)
+    ![](./figures/security.png)
 
 3.  设置Enforce Secure Boot为Disabled。
 
-    ![](figures/选择.png)
+    ![](./figures/select.png)
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >设置security boot为disable之后，保存退出，重新安装即可。  
 
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/Advanced_User_Configuration.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Advanced_User_Configuration.png
new file mode 100644
index 0000000000000000000000000000000000000000..63f6c87eec6758e97c976c07171343d28569d011
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Advanced_User_Configuration.png differ
diff --git "a/content/zh/docs/Installation/figures/\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205\345\256\214\346\210\220.png" b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Automatic_installation_complete.png
similarity index 100%
rename from "content/zh/docs/Installation/figures/\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205\345\256\214\346\210\220.png"
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/Automatic_installation_complete.png
diff --git a/content/zh/docs/Installation/figures/BIOS.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/BIOS.png
similarity index 100%
rename from content/zh/docs/Installation/figures/BIOS.png
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/BIOS.png
diff --git "a/content/zh/docs/Installation/figures/\345\205\211\351\251\261\345\233\276\346\240\207.png" b/docs/zh/docs/20.03_LTS/docs/Installation/figures/CD-ROM_drive_icon.png
similarity index 100%
rename from "content/zh/docs/Installation/figures/\345\205\211\351\251\261\345\233\276\346\240\207.png"
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/CD-ROM_drive_icon.png
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/Configuration_error_prompt.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Configuration_error_prompt.png
new file mode 100644
index 0000000000000000000000000000000000000000..c5802a2b7a750eed8429ec06c7e4919a3d161a9e
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Configuration_error_prompt.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/Ending_Configuration-new.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Ending_Configuration-new.png
new file mode 100644
index 0000000000000000000000000000000000000000..db408008865e51d7f92f0cb767b1cb61e3e12793
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Ending_Configuration-new.png differ
diff --git "a/content/zh/docs/Installation/figures/\351\225\234\345\203\217\345\257\271\350\257\235\346\241\206.png" b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Image_dialog_box.png
similarity index 100%
rename from "content/zh/docs/Installation/figures/\351\225\234\345\203\217\345\257\271\350\257\235\346\241\206.png"
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/Image_dialog_box.png
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/Installation_Overview.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Installation_Overview.png
new file mode 100644
index 0000000000000000000000000000000000000000..e30f776c50915918005be529363b2e15de9fe432
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Installation_Overview.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/Installation_Procedure.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Installation_Procedure.png
new file mode 100644
index 0000000000000000000000000000000000000000..9ea395847259ea6a60883ead1edbef81e622afe6
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Installation_Procedure.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/Installation_source.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Installation_source.png
new file mode 100644
index 0000000000000000000000000000000000000000..74ada559531d806e31ac6fda3e45fff1e2fe3c50
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Installation_source.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/Installation_wizard.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Installation_wizard.png
new file mode 100644
index 0000000000000000000000000000000000000000..69c5254413574903fc55c5eafb935a83837549e0
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Installation_wizard.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/Keyboard_layout.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Keyboard_layout.png
new file mode 100644
index 0000000000000000000000000000000000000000..9bb4e1b0fd26df0011a10c707e2191f934500893
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Keyboard_layout.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/Manual_partitioning.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Manual_partitioning.png
new file mode 100644
index 0000000000000000000000000000000000000000..89bd1b2afb39bb9ec1e8e331449f885f31dfe756
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Manual_partitioning.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/NetworkandHostName.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/NetworkandHostName.png
new file mode 100644
index 0000000000000000000000000000000000000000..3d0c759016fe3bb43f44258c62cd7c5b4afbda27
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/NetworkandHostName.png differ
diff --git "a/content/zh/docs/Installation/figures/No-bootable-device-\346\217\220\347\244\272\347\225\214\351\235\242.png" b/docs/zh/docs/20.03_LTS/docs/Installation/figures/No-bootable-device.png
similarity index 100%
rename from "content/zh/docs/Installation/figures/No-bootable-device-\346\217\220\347\244\272\347\225\214\351\235\242.png"
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/No-bootable-device.png
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/Semi-automatic-new.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Semi-automatic-new.png
new file mode 100644
index 0000000000000000000000000000000000000000..82218558de7ffacb4835087c90c0206b52f89198
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Semi-automatic-new.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/Target_installation_position.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Target_installation_position.png
new file mode 100644
index 0000000000000000000000000000000000000000..af0980e3a8e2d2510d00b6012e4aef70936b584e
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/Target_installation_position.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/add_inst-noverifyssl.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/add_inst-noverifyssl.png
new file mode 100644
index 0000000000000000000000000000000000000000..dc92fedd71a5331af870e449f843ecd0eefc9278
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/add_inst-noverifyssl.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/choosesoftware.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/choosesoftware.png
new file mode 100644
index 0000000000000000000000000000000000000000..8330bf28b910ab88420e0ba1fb43a49b21a3374f
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/choosesoftware.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/completeinstall.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/completeinstall.png
new file mode 100644
index 0000000000000000000000000000000000000000..91d38b80cf2310a7427788feb089da8d106b97b5
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/completeinstall.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/createuser.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/createuser.png
new file mode 100644
index 0000000000000000000000000000000000000000..3650c7ed70883500b636ae2acecee78d5724f7d8
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/createuser.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/dateandtime.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/dateandtime.png
new file mode 100644
index 0000000000000000000000000000000000000000..9b433ac4f14140ff75841e786a040bf991bec0db
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/dateandtime.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/languagesupport.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/languagesupport.png
new file mode 100644
index 0000000000000000000000000000000000000000..47b451e97e87bfb17bc0c8039f262c5ffff84ca2
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/languagesupport.png differ
diff --git "a/content/zh/docs/Installation/figures/\351\207\215\345\220\257\345\233\276\346\240\207.png" b/docs/zh/docs/20.03_LTS/docs/Installation/figures/restarticon.png
similarity index 100%
rename from "content/zh/docs/Installation/figures/\351\207\215\345\220\257\345\233\276\346\240\207.png"
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/restarticon.png
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/root_password.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/root_password.png
new file mode 100644
index 0000000000000000000000000000000000000000..131863338be6ea5925cadd75483c08c34ec9856c
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/root_password.png differ
diff --git a/content/zh/docs/Installation/figures/security.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/security.png
similarity index 100%
rename from content/zh/docs/Installation/figures/security.png
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/security.png
diff --git "a/content/zh/docs/Installation/figures/\351\200\211\346\213\251.png" b/docs/zh/docs/20.03_LTS/docs/Installation/figures/select.png
similarity index 100%
rename from "content/zh/docs/Installation/figures/\351\200\211\346\213\251.png"
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/select.png
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/selectlanguage.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/selectlanguage.png
new file mode 100644
index 0000000000000000000000000000000000000000..44e736d20c86098b0e69e0a7027103871d19032b
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/selectlanguage.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Installation/figures/startinstall.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/startinstall.png
new file mode 100644
index 0000000000000000000000000000000000000000..227ec876dc1b0d6cbe6991c1bce1fc0837a344c0
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Installation/figures/startinstall.png differ
diff --git a/content/zh/docs/Installation/figures/zh-cn_image_0229291229.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291229.png
similarity index 100%
rename from content/zh/docs/Installation/figures/zh-cn_image_0229291229.png
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291229.png
diff --git a/content/zh/docs/Installation/figures/zh-cn_image_0229291236.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291236.png
similarity index 100%
rename from content/zh/docs/Installation/figures/zh-cn_image_0229291236.png
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291236.png
diff --git a/content/zh/docs/Installation/figures/zh-cn_image_0229291243.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291243.png
similarity index 100%
rename from content/zh/docs/Installation/figures/zh-cn_image_0229291243.png
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291243.png
diff --git a/content/zh/docs/Installation/figures/zh-cn_image_0229291247.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291247.png
similarity index 100%
rename from content/zh/docs/Installation/figures/zh-cn_image_0229291247.png
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291247.png
diff --git a/content/zh/docs/Installation/figures/zh-cn_image_0229291264.jpg b/docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291264.jpg
similarity index 100%
rename from content/zh/docs/Installation/figures/zh-cn_image_0229291264.jpg
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291264.jpg
diff --git a/content/zh/docs/Installation/figures/zh-cn_image_0229291270.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291270.png
similarity index 100%
rename from content/zh/docs/Installation/figures/zh-cn_image_0229291270.png
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291270.png
diff --git a/content/zh/docs/Installation/figures/zh-cn_image_0229291272.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291272.png
similarity index 100%
rename from content/zh/docs/Installation/figures/zh-cn_image_0229291272.png
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291272.png
diff --git a/content/zh/docs/Installation/figures/zh-cn_image_0229291280.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291280.png
similarity index 100%
rename from content/zh/docs/Installation/figures/zh-cn_image_0229291280.png
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291280.png
diff --git a/content/zh/docs/Installation/figures/zh-cn_image_0229291286.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291286.png
similarity index 100%
rename from content/zh/docs/Installation/figures/zh-cn_image_0229291286.png
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229291286.png
diff --git a/content/zh/docs/Installation/figures/zh-cn_image_0229420473.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229420473.png
similarity index 100%
rename from content/zh/docs/Installation/figures/zh-cn_image_0229420473.png
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0229420473.png
diff --git a/content/zh/docs/Installation/figures/zh-cn_image_0231657950.png b/docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0231657950.png
similarity index 100%
rename from content/zh/docs/Installation/figures/zh-cn_image_0231657950.png
rename to docs/zh/docs/20.03_LTS/docs/Installation/figures/zh-cn_image_0231657950.png
diff --git a/content/zh/docs/Installation/installation.md b/docs/zh/docs/20.03_LTS/docs/Installation/installation.md
similarity index 100%
rename from content/zh/docs/Installation/installation.md
rename to docs/zh/docs/20.03_LTS/docs/Installation/installation.md
diff --git a/content/zh/docs/Installation/public_sys-resources/icon-caution.gif b/docs/zh/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-caution.gif
similarity index 100%
rename from content/zh/docs/Installation/public_sys-resources/icon-caution.gif
rename to docs/zh/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-caution.gif
diff --git a/content/zh/docs/Installation/public_sys-resources/icon-danger.gif b/docs/zh/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-danger.gif
similarity index 100%
rename from content/zh/docs/Installation/public_sys-resources/icon-danger.gif
rename to docs/zh/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-danger.gif
diff --git a/content/zh/docs/Installation/public_sys-resources/icon-note.gif b/docs/zh/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-note.gif
similarity index 100%
rename from content/zh/docs/Installation/public_sys-resources/icon-note.gif
rename to docs/zh/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-note.gif
diff --git a/content/zh/docs/Installation/public_sys-resources/icon-notice.gif b/docs/zh/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-notice.gif
similarity index 100%
rename from content/zh/docs/Installation/public_sys-resources/icon-notice.gif
rename to docs/zh/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-notice.gif
diff --git a/content/zh/docs/Installation/public_sys-resources/icon-tip.gif b/docs/zh/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-tip.gif
similarity index 100%
rename from content/zh/docs/Installation/public_sys-resources/icon-tip.gif
rename to docs/zh/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-tip.gif
diff --git a/content/zh/docs/Installation/public_sys-resources/icon-warning.gif b/docs/zh/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-warning.gif
similarity index 100%
rename from content/zh/docs/Installation/public_sys-resources/icon-warning.gif
rename to docs/zh/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-warning.gif
diff --git "a/content/zh/docs/Installation/\344\275\277\347\224\250kickstart\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205.md" "b/docs/zh/docs/20.03_LTS/docs/Installation/\344\275\277\347\224\250kickstart\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205.md"
similarity index 91%
rename from "content/zh/docs/Installation/\344\275\277\347\224\250kickstart\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205.md"
rename to "docs/zh/docs/20.03_LTS/docs/Installation/\344\275\277\347\224\250kickstart\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205.md"
index ccf0fcdc377b462e1f9c5428b37e703e588b3176..459dc1544f089fd1e6fd9916041ac56ad0636b2c 100644
--- "a/content/zh/docs/Installation/\344\275\277\347\224\250kickstart\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Installation/\344\275\277\347\224\250kickstart\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205.md"
@@ -80,7 +80,7 @@ TFTP（Trivial File Transfer Protocol，简单文件传输协议），该协议
 
 -   物理机/虚拟机（虚拟机创建可参考对应厂商的资料）。包括使用kickstart工具进行自动化安装的计算机和被安装的计算机。
 -   httpd：存放kickstart文件。
--   ISO： openEuler-20.09-beta-aarch64-dvd.iso
+-   ISO： openEuler-20.03-LTS-aarch64-dvd.iso
 
 ### 操作步骤
 
@@ -88,7 +88,7 @@ TFTP（Trivial File Transfer Protocol，简单文件传输协议），该协议
 
 **环境准备**
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >安装之前，请确保http服务器的防火墙处于关闭状态。关闭防火墙可参照如下命令：  
 >```  
 >iptables -F  
@@ -106,7 +106,7 @@ TFTP（Trivial File Transfer Protocol，简单文件传输协议），该协议
 
     ```
     # mkdir /var/www/html/ks
-    # vim /var/www/html/ks/openEuler-ks.cfg ===>根据已安装openEuler系统自动生成的anaconda-ks.cfg修改得到
+    # vim /var/www/html/ks/openEuler-ks.cfg ===>根据已安装openEuler系统自动生成的anaconda-ks.cfg修改得到，也可以使用system-config-kickstart工具做成
     ====================================
     ***以下内容需要根据实际需求进行修改***
     #version=DEVEL
@@ -156,7 +156,7 @@ TFTP（Trivial File Transfer Protocol，简单文件传输协议），该协议
     =====================================
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >密码密文生成方式：  
     >\# python3  
     >Python 3.7.0 \(default, Apr  1 2019, 00:00:00\)  
@@ -175,10 +175,10 @@ TFTP（Trivial File Transfer Protocol，简单文件传输协议），该协议
 **安装系统**
 
 1.  启动系统进入安装选择界面。
-    1.  在“[启动安装](安装指导.html#启动安装)”中的“安装引导界面”中选择“Install openEuler 20.09-beta”，并按下“e”键。
+    1.  在“[启动安装](./安装指导.html#启动安装)”中的“安装引导界面”中选择“Install openEuler 20.03 LTS”，并按下“e”键。
     2.  启动参数中追加“inst.ks=http://server ip/ks/openEuler-ks.cfg”。
 
-        ![](figures/半自动-new.png)
+        ![](./figures/Semi-automatic-new.png)
 
     3.  按“Ctrl+x”，开始系统的自动安装。
 
@@ -186,7 +186,7 @@ TFTP（Trivial File Transfer Protocol，简单文件传输协议），该协议
 
     系统安装完毕以后会自动重启，然后再次进入到安装界面，此时关闭计算机，调整启动顺序（优先从硬盘启动）。
 
-    ![](figures/自动化安装完成.png)
+    ![](./figures/Automatic_installation_complete.png)
 
 
 ## 全自动化安装指导
@@ -199,7 +199,7 @@ TFTP（Trivial File Transfer Protocol，简单文件传输协议），该协议
 -   httpd：存放kickstart文件。
 -   tftp：提供vmlinuz和initrd文件。
 -   dhcpd/pxe：提供DHCP服务。
--   ISO：openEuler-20.09-beta-aarch64-dvd.iso。
+-   ISO：openEuler-20.03-LTS-aarch64-dvd.iso。
 
 ### 操作步骤
 
@@ -207,7 +207,7 @@ TFTP（Trivial File Transfer Protocol，简单文件传输协议），该协议
 
 **环境准备**
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >安装之前，请确保http服务器的防火墙处于关闭状态。关闭防火墙可参照如下命令：  
 >```  
 >iptables -F  
@@ -249,7 +249,7 @@ TFTP（Trivial File Transfer Protocol，简单文件传输协议），该协议
 3.  安装源的制作。
 
     ```
-    # mount openEuler-20.09-beta-aarch64-dvd.iso /mnt
+    # mount openEuler-20.03-LTS-aarch64-dvd.iso /mnt
     # cp -r /mnt/* /var/www/html/openEuler/
     ```
 
@@ -271,7 +271,7 @@ TFTP（Trivial File Transfer Protocol，简单文件传输协议），该协议
     # System language
     lang zh_CN.UTF-8
     #Use http installation source
-    url  --url=http://192.168.122.1/openEuler/
+    url  --url=//192.168.122.1/openEuler/
     %post
     #enable kdump
     sed  -i "s/ ro / ro crashkernel=1024M,high /" /boot/efi/EFI/openEuler/grub.cfg
@@ -314,8 +314,8 @@ TFTP（Trivial File Transfer Protocol，简单文件传输协议），该协议
     
     
     ### BEGIN /etc/grub.d/10_linux ###
-    menuentry 'Install openEuler 20.09-beta' --class red --class gnu-linux --class gnu --class os {
-            set root=(tftp,192.168.122.1)
+    menuentry 'Install openEuler 20.03 LTS' --class red --class gnu-linux --class gnu --class os {
+            set root=(tftp,192.168.1.1)
             linux /vmlinuz ro inst.geoloc=0 console=ttyAMA0 console=tty0 rd.iscsi.waitnet=0 inst.ks=http://192.168.122.1/ks/openEuler-ks.cfg
             initrd /initrd.img
     }
@@ -336,7 +336,7 @@ TFTP（Trivial File Transfer Protocol，简单文件传输协议），该协议
     filename "grubaa64.efi"; 　　 # pxelinux 启动文件位置;
     next-server 192.168.122.1;　　# (重要)TFTP Server 的IP地址;
     subnet 192.168.122.0 netmask 255.255.255.0 {
-    option routers 192.168.122.1; # 网关地址
+    option routers 192.168.111.1; # 网关地址
     option subnet-mask 255.255.255.0; # 子网掩码
     range dynamic-bootp 192.168.122.50 192.168.122.200; # 动态ip范围
     default-lease-time 21600;
@@ -351,14 +351,14 @@ TFTP（Trivial File Transfer Protocol，简单文件传输协议），该协议
 
 1.  在“Start boot option”界面按下“F2”选择从网络pxe启动，开始自动化安装。
 
-    ![](figures/zh-cn_image_0229291270.png)
+    ![](./figures/zh-cn_image_0229291270.png)
 
-    ![](figures/zh-cn_image_0229291286.png)
+    ![](./figures/zh-cn_image_0229291286.png)
 
-    ![](figures/zh-cn_image_0229291247.png)
+    ![](./figures/zh-cn_image_0229291247.png)
 
 2.  进入系统全自动化安装界面。
 3.  确认系统安装完毕。
 
-    ![](figures/自动化安装完成.png)
+    ![](./figures/Automatic_installation_complete.png)
 
diff --git "a/content/zh/docs/Installation/\345\256\211\350\243\205\345\207\206\345\244\207.md" "b/docs/zh/docs/20.03_LTS/docs/Installation/\345\256\211\350\243\205\345\207\206\345\244\207.md"
similarity index 92%
rename from "content/zh/docs/Installation/\345\256\211\350\243\205\345\207\206\345\244\207.md"
rename to "docs/zh/docs/20.03_LTS/docs/Installation/\345\256\211\350\243\205\345\207\206\345\244\207.md"
index 31b4eb9b7205099ee0ca942bd18b389f78be8896..d78039353154f50ed018f00de3494c9d00128e06 100644
--- "a/content/zh/docs/Installation/\345\256\211\350\243\205\345\207\206\345\244\207.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Installation/\345\256\211\350\243\205\345\207\206\345\244\207.md"
@@ -1,241 +1,238 @@
-# 安装准备
-
-介绍安装前需要考虑软硬件兼容性状况，以及相关的配置和准备工作。
-
-
-- [安装准备](#安装准备)
-    - [获取安装源](#获取安装源)
-    - [发布包完整性校验](#发布包完整性校验)
-        - [简介](#简介)
-        - [前提条件](#前提条件)
-        - [操作指导](#操作指导)
-    - [物理机的安装要求](#物理机的安装要求)
-        - [硬件兼容支持](#硬件兼容支持)
-        - [最小硬件要求](#最小硬件要求)
-    - [虚拟机的安装要求](#虚拟机的安装要求)
-        - [虚拟化平台兼容性](#虚拟化平台兼容性)
-        - [最小虚拟化空间要求](#最小虚拟化空间要求)
-
-
-
-## 获取安装源
-
-在安装开始前，您需要获取openEuler的发布包和校验文件。
-
-> ![](public_sys-resources/icon-note.gif) **说明：**   
-> AArch64架构的发布包支持UEFI模式，x86\_64架构的发布包支持UEFI模式和Legacy模式。
-
-请按以下步骤获取openEuler的发布包和校验文件：
-
-1.  登录[openEuler社区](https://openeuler.org)网站。
-2.  单击“下载”。
-3.  单击“获取ISO：”后面的“Link”，显示版本列表。
-4.  单击“openEuler-20.09-beta”，进入openEuler 20.09 beta版本下载列表。
-5.  单击“ISO”，进入ISO下载列表。
-    -   aarch64：AArch64架构的ISO。
-    -   x86\_64：x86\_64架构的ISO。
-    -   source：openEuler源码ISO。
-
-6.  根据实际待安装环境的架构选择需要下载的openEuler的发布包和校验文件。
-    -   若为AArch64架构。
-        1.  单击“aarch64”。
-        2.  单击“openEuler-20.09-beta-aarch64-dvd.iso”，将openEuler发布包下载到本地。
-        3.  单击“openEuler-20.09-beta-aarch64-dvd.iso.sha256sum”，将openEuler校验文件下载到本地。
-
-    -   若为x86\_64架构。
-        1.  单击“x86\_64”。
-        2.  单击“openEuler-20.09-beta-x86\_64-dvd.iso”，将openEuler发布包下载到本地。
-        3.  单击“openEuler-20.09-beta-x86\_64-dvd.iso.sha256sum”，将openEuler校验文件下载到本地。
-
-## 发布包完整性校验
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->本章节以AArch64架构的发布包完整性校验为例，x86\_64架构的发布包完整性校验的操作方法相同。   
-
-### 简介
-
-为了防止软件包在传输过程中由于网络原因或者存储设备原因出现下载不完整的问题，在获取到软件包后，需要对软件包的完整性进行校验，通过了校验的软件包才能部署。
-
-这里通过对比校验文件中记录的校验值和手动方式计算的iso文件校验值，判断软件包是否完成。若两个值相同，说明iso文件完整，否则，iso完整性被破坏，请重新获取iso发布包。
-
-### 前提条件
-
-在校验发布包完整性之前，需要准备如下文件：
-
-iso文件：openEuler-20.09-beta-aarch64-dvd.iso
-
-校验文件：openEuler-20.09-beta-aarch64-dvd.iso.sha256sum
-
-### 操作指导
-
-文件完整性校验操作步骤如下：
-
-1.  获取校验文件中的校验值。执行命令如下：
-
-    ```
-    $ cat openEuler-20.09-beta-aarch64-dvd.iso.sha256sum 
-    ```
-
-2.  计算文件的sha256校验值。执行命令如下：
-
-    ```
-    $ sha256sum openEuler-20.09-beta-aarch64-dvd.iso
-    ```
-
-    命令执行完成后，输出校验值。
-
-3.  对比步骤1和步骤2计算的校验值是否一致。
-
-    如果校验值一致说明iso文件完整性没有破坏，如果校验值不一致则可以确认文件完整性已被破坏，需要重新获取。
-
-## 物理机的安装要求
-
-若需要在物理机环境上安装openEuler操作系统，则物理机需要满足如下的硬件兼容性和最小硬件要求。
-
-### 硬件兼容支持
-
-openEuler安装时，应注意硬件兼容性方面的问题，当前已支持的服务器类型如[表1](#table14948632047)所示。
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->
->-   TaiShan 200服务器基于华为鲲鹏920处理器。  
->-   当前仅支持华为TaiShan服务器和FusionServer Pro 机架服务器，后续将逐步增加对其他厂商服务器的支持。  
-
-**表 1**  支持的服务器类型
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
服务器形态

-
服务器名称

-
服务器型号

-
机架服务器

-
TaiShan 200

-
2280均衡型

-
机架服务器

-
FusionServer Pro 机架服务器

-
FusionServer Pro 2288H V5

-
 说明： 
服务器要求配置Avago 3508 RAID控制卡和启用LOM-X722网卡。

-

-

-
-### 最小硬件要求
-
-openEuler所需的最小硬件要求如[表2](#tff48b99c9bf24b84bb602c53229e2541)所示。
-
-**表 2**  最小硬件要求
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
部件名称

-
最小硬件要求

-
说明

-
架构

-
  • AArch64
  • x86_64

-
  • 支持Arm的64位架构。
  • 支持Intel的x86 64位架构。

-
CPU

-
  • 华为鲲鹏920系列CPU
  • Intel® Xeon®处理器

-
-

-
内存

-
不小于4GB（为了获得更好的应用体验，建议不小于8GB）

-
-

-
硬盘

-
为了获得更好的应用体验，建议不小于120GB）

-
支持IDE、SATA、SAS等接口的硬盘。

-

-
-## 虚拟机的安装要求
-
-若需要在虚拟机环境上安装openEuler操作系统，则虚拟机需要满足如下的虚拟化平台兼容性和最小虚拟化要求。
-
-### 虚拟化平台兼容性
-
-openEuler安装时，应注意虚拟化平台兼容性的问题，当前已支持的虚拟化平台为：
-
--   openEuler自有的虚拟化组件（HostOS为openEuler，虚拟化组件为发布包中的qemu、KVM）创建的虚拟化平台。
--   华为公有云的x86虚拟化平台。
-
-### 最小虚拟化空间要求
-
-openEuler所需的最小虚拟化空间要求如[表3](#tff48b99c9bf24b84bb602c53229e2541)所示。
-
-**表 3**  最小虚拟化空间要求
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
部件名称

-
最小虚拟化空间要求

-
说明

-
架构

-
  • AArch64
  • x86_64

-
-

-
CPU

-
2个CPU

-
-

-
内存

-
不小于4GB（为了获得更好的应用体验，建议不小于8GB）

-
-

-
硬盘

-
不小于32GB（为了获得更好的应用体验，建议不小于120GB）

-
-

-

-
-
-
+# 安装准备
+
+介绍安装前需要考虑软硬件兼容性状况，以及相关的配置和准备工作。
+
+
+- [安装准备](#安装准备)
+    - [获取安装源](#获取安装源)
+    - [发布包完整性校验](#发布包完整性校验)
+        - [简介](#简介)
+        - [前提条件](#前提条件)
+        - [操作指导](#操作指导)
+    - [物理机的安装要求](#物理机的安装要求)
+        - [硬件兼容支持](#硬件兼容支持)
+        - [最小硬件要求](#最小硬件要求)
+    - [虚拟机的安装要求](#虚拟机的安装要求)
+        - [虚拟化平台兼容性](#虚拟化平台兼容性)
+        - [最小虚拟化空间要求](#最小虚拟化空间要求)
+
+
+
+## 获取安装源
+
+在安装开始前，您需要获取openEuler的发布包和校验文件。
+
+请按以下步骤获取openEuler的发布包和校验文件：
+
+1.  登录[openEuler社区](https://openeuler.org)网站。
+2.  单击“下载”。
+3.  单击“获取ISO：”后面的“Link”，显示版本列表。
+4.  单击“openEuler-20.03-LTS”，进入openEuler 20.03 LTS版本下载列表。
+5.  单击“ISO”，进入ISO下载列表。
+    -   aarch64：AArch64架构的ISO。
+    -   x86\_64：x86\_64架构的ISO。
+    -   source：openEuler源码ISO。
+
+6.  根据实际待安装环境的架构选择需要下载的openEuler的发布包和校验文件。
+    -   若为AArch64架构。
+        1.  单击“aarch64”。
+        2.  单击“openEuler-20.03-LTS-aarch64-dvd.iso”，将openEuler发布包下载到本地。
+        3.  单击“openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum”，将openEuler校验文件下载到本地。
+
+    -   若为x86\_64架构。
+        1.  单击“x86\_64”。
+        2.  单击“openEuler-20.03-LTS-x86\_64-dvd.iso”，将openEuler发布包下载到本地。
+        3.  单击“openEuler-20.03-LTS-x86\_64-dvd.iso.sha256sum”，将openEuler校验文件下载到本地。
+
+## 发布包完整性校验
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>本章节以AArch64架构的发布包完整性校验为例，x86\_64架构的发布包完整性校验的操作方法相同。   
+
+### 简介
+
+为了防止软件包在传输过程中由于网络原因或者存储设备原因出现下载不完整的问题，在获取到软件包后，需要对软件包的完整性进行校验，通过了校验的软件包才能部署。
+
+这里通过对比校验文件中记录的校验值和手动方式计算的iso文件校验值，判断软件包是否完成。若两个值相同，说明iso文件完整，否则，iso完整性被破坏，请重新获取iso发布包。
+
+### 前提条件
+
+在校验发布包完整性之前，需要准备如下文件：
+
+iso文件：openEuler-20.03-LTS-aarch64-dvd.iso
+
+校验文件：openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum
+
+### 操作指导
+
+文件完整性校验操作步骤如下：
+
+1.  获取校验文件中的校验值。执行命令如下：
+
+    ```
+    $ cat openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum 
+    ```
+
+2.  计算文件的sha256校验值。执行命令如下：
+
+    ```
+    $ sha256sum openEuler-20.03-LTS-aarch64-dvd.iso
+    ```
+
+    命令执行完成后，输出校验值。
+
+3.  对比步骤1和步骤2计算的校验值是否一致。
+
+    如果校验值一致说明iso文件完整性没有破坏，如果校验值不一致则可以确认文件完整性已被破坏，需要重新获取。
+
+## 物理机的安装要求
+
+若需要在物理机环境上安装openEuler操作系统，则物理机需要满足如下的硬件兼容性和最小硬件要求。
+
+### 硬件兼容支持
+
+openEuler安装时，应注意硬件兼容性方面的问题，当前已支持的服务器类型如[表1](#table14948632047)所示。
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>
+>-   TaiShan 200服务器基于华为鲲鹏920处理器。  
+>-   当前仅支持华为TaiShan服务器和FusionServer Pro 机架服务器，后续将逐步增加对其他厂商服务器的支持。  
+
+**表 1**  支持的服务器类型
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
服务器形态

+
服务器名称

+
服务器型号

+
机架服务器

+
TaiShan 200

+
2280均衡型

+
机架服务器

+
FusionServer Pro 机架服务器

+
FusionServer Pro 2288H V5

+
 说明： 
服务器要求配置Avago 3508 RAID控制卡和启用LOM-X722网卡。

+

+

+
+### 最小硬件要求
+
+openEuler所需的最小硬件要求如[表2](#tff48b99c9bf24b84bb602c53229e2541)所示。
+
+**表 2**  最小硬件要求
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
部件名称

+
最小硬件要求

+
说明

+
架构

+
  • AArch64
  • x86_64

+
  • 支持Arm的64位架构。
  • 支持Intel的x86 64位架构。

+
CPU

+
  • 华为鲲鹏920系列CPU
  • Intel® Xeon®处理器

+
-

+
内存

+
不小于4GB（为了获得更好的应用体验，建议不小于8GB）

+
-

+
硬盘

+
为了获得更好的应用体验，建议不小于120GB

+
支持IDE、SATA、SAS等接口的硬盘。

+

+
+## 虚拟机的安装要求
+
+若需要在虚拟机环境上安装openEuler操作系统，则虚拟机需要满足如下的虚拟化平台兼容性和最小虚拟化要求。
+
+### 虚拟化平台兼容性
+
+openEuler安装时，应注意虚拟化平台兼容性的问题，当前已支持的虚拟化平台为：
+
+-   openEuler自有的虚拟化组件（HostOS为openEuler，虚拟化组件为发布包中的qemu、KVM）创建的虚拟化平台。
+-   华为公有云的x86虚拟化平台。
+
+### 最小虚拟化空间要求
+
+openEuler所需的最小虚拟化空间要求如[表3](#tff48b99c9bf24b84bb602c53229e2541)所示。
+
+**表 3**  最小虚拟化空间要求
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
部件名称

+
最小虚拟化空间要求

+
说明

+
架构

+
  • AArch64
  • x86_64

+
-

+
CPU

+
2个CPU

+
-

+
内存

+
不小于4GB（为了获得更好的应用体验，建议不小于8GB）

+
-

+
硬盘

+
不小于32GB（为了获得更好的应用体验，建议不小于120GB）

+
-

+

+
+
+
diff --git "a/content/zh/docs/Installation/\345\256\211\350\243\205\346\214\207\345\257\274.md" "b/docs/zh/docs/20.03_LTS/docs/Installation/\345\256\211\350\243\205\346\214\207\345\257\274.md"
similarity index 64%
rename from "content/zh/docs/Installation/\345\256\211\350\243\205\346\214\207\345\257\274.md"
rename to "docs/zh/docs/20.03_LTS/docs/Installation/\345\256\211\350\243\205\346\214\207\345\257\274.md"
index e120f9e6650022b6922f41cadd53cae795781790..8789bb64ea9a2dd376b390e8bfecc3dfcdc5ac75 100644
--- "a/content/zh/docs/Installation/\345\256\211\350\243\205\346\214\207\345\257\274.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Installation/\345\256\211\350\243\205\346\214\207\345\257\274.md"
@@ -1,324 +1,329 @@
-# 安装指导
-
-本章以光盘安装为例介绍安装openEuler，其他安装方式除在启动安装时的引导方式不同外，待启动安装后则安装流程相同，在此不再说明。
-
-
-- [安装指导](#安装指导)
-    - [启动安装](#启动安装)
-        - [使用光盘引导安装](#使用光盘引导安装)
-        - [安装引导界面](#安装引导界面)
-        - [图形化模式安装](#图形化模式安装)
-    - [设置安装程序语言](#设置安装程序语言)
-    - [进入安装界面](#进入安装界面)
-    - [设置键盘](#设置键盘)
-    - [设置系统语言](#设置系统语言)
-    - [设置时间和日期](#设置时间和日期)
-    - [设置安装源](#设置安装源)
-    - [选择安装软件](#选择安装软件)
-    - [设置安装目的地](#设置安装目的地)
-        - [存储配置](#存储配置)
-    - [设置网络和主机名](#设置网络和主机名)
-    - [设置根密码](#设置根密码)
-        - [密码复杂度](#密码复杂度)
-    - [创建用户](#创建用户)
-    - [开始安装](#开始安装)
-    - [安装过程](#安装过程)
-    - [安装完成](#安装完成)
-
-
-
-## 启动安装
-
-### 使用光盘引导安装
-
-在服务器的光驱中加载openEuler安装镜像，重启服务器，具体步骤如下。
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->在安装开始前，需要保证服务器启动选项为光驱优先。安装步骤以BMC挂载虚拟光驱进行光盘安装的操作举例。通过物理光驱安装的操作简单，启动安装后的流程相同，在此不再说明。  
-
-1.  在虚拟界面工具栏中，单击虚拟光驱工具如下图所示。
-
-    **图 1**  光驱图标  
-    ![](figures/光驱图标.png "光驱图标")
-
-    弹出镜像对话框，如下图所示。
-
-    **图 2**  镜像对话框  
-    ![](figures/镜像对话框.png "镜像对话框")
-
-2.  在镜像对话框中，选择“镜像文件”， 并单击“浏览”。弹出“打开”对话框。
-3.  选择镜像文件，单击“打开”。然后在镜像对话框中，单击“连接”。当“连接”显示为“断开”后，表示虚拟光驱已连接到服务器。
-4.  在工具栏中，单击重启工具重启设备，如下图所示。
-
-    **图 3**  重启图标  
-    ![](figures/重启图标.png "重启图标")
-
-
-### 安装引导界面
-
-系统使用引导介质完成引导后会显示引导菜单。该引导菜单除启动安装程序外还提供一些选项。安装系统时，默认采用“Test this media & install openEuler 20.09-beta”方式进行安装。如果要选择默认选项之外的选项，请使用键盘中的“↑”和“↓”方向键进行选择，并在选项为高亮状态时按“Enter”。
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->-   如果60秒内未按任何键，系统将从默认选项“Test this media & install openEuler 20.09-beta”自动进入安装界面。  
->-   安装物理机时，如果使用键盘上下键无法选择启动选项，按“Enter”键无响应，可以单击BMC界面上的鼠标控制图标“![](figures/zh-cn_image_0229420473.png)”，设置“键鼠复位”。  
-
-**图 4**  安装引导界面  
-![](figures/安装引导界面.png "安装引导界面")
-
-安装引导选项说明如下：
-
--   Install openEuler 20.09-beta —— 在您的服务器上使用图形用户界面模式安装。
-
--   Test this media & install openEuler 20.09-beta —— 默认选项，在您的服务器上使用图形用户界面模式安装，但在启动安装程序前会进行安装介质的完整性检查。
-
--   Troubleshooting —— 问题定位模式，系统无法正常安装时使用。进入问题定位模式后，有如下两个选项。
-    -   Install openEuler 20.09-beta in basic graphics mode —— 简单图形安装模式，该模式下在系统启动并运行之前不启动视频驱动程序。
-    -   Rescue the openEuler system —— 救援模式，用于修复系统。该模式下输出定向到VNC或BMC（Baseboard Management Controller）端，串口不可用。
-
-在安装引导界面，按“e”进入已选选项的参数编辑界面，按“c”进入命令行模式。
-
-### 图形化模式安装
-
-在“安装引导界面”中选择“Test this media & install openEuler 20.09-beta”进入图形化模式安装。
-
-可以通过键盘操作图形化安装程序。
-
--   “Tab”、“shift Tab”：界面控件（按钮、区域框、复选框等）间的移动。
--   “↑”、“↓”方向键：列表里的移动。
--   “←”、“→”方向键：水平工具条和表条间移动。
--   “空格”、“Enter”：选择或删除高亮显示的选项、展开或折叠下拉菜单。
--   “Alt”+“快捷键”：选择快捷键所在的控件，其中快捷键可通过按住Alt高亮（加下划线）显示。
-
-## 设置安装程序语言
-
-启动安装后，在进入安装程序主界面之前，系统会提示用户设置安装过程中使用的语言。当前默认为英语，用户可根据实际情况进行调整，如[图5](#zh-cn_topic_0186390093_zh-cn_topic_0122145864_fig144630179151)所示，选择“中文”。
-
-**图 5**  选择语言  
-![](figures/选择语言.png "选择语言")
-
-完成设置后，单击“继续”，进入安装设置主界面。
-
-如果您想退出安装，可以单击“退出”并在弹出的“您确定要退出安装程序吗？”对话框中单击“是”重新进入“安装引导界面”。
-
-## 进入安装界面
-
-系统安装程序正常启动后，会进入[图6](#zh-cn_topic_0186390094_zh-cn_topic_0122145883_fig5969171592212)所示的安装设置主界面。用户可以进行时间、语言、安装源、网络、安装位置等相关设置。
-
-部分配置项会有告警符号，用户完成该选项配置后，告警符号消失。当界面上不存在告警符号时，用户才能单击“开始安装”进行系统安装。
-
-如果您想退出安装，可以单击“退出”并在弹出的“您确定要退出安装程序吗？”对话框中单击“是”重新进入“安装引导界面”。
-
-**图 6**  安装概览  
-![](figures/安装概览.png "安装概览")
-
-## 设置键盘
-
-在“安装概览”页面中选择“键盘”，用户可以在系统中添加或者删除多个键盘布局。
-
--   要查看键盘布局，请在左侧选框中单击选中该键盘布局，然后单击下面的“键盘”按钮。
--   要测试键盘布局，请在左侧选框中添加键盘布局，然后在右上角键盘图标处进行点击切换为目标键盘，单击右侧文本框内部，输入文本以确认所选键盘布局可正常工作。
-
-**图 7**  键盘布局  
-![](figures/键盘布局.png "键盘布局")
-
-设置完成后，请单击左上角“完成”返回“安装概览”页面。
-
-## 设置系统语言
-
-在“安装概览”页面中选择“语言支持”，设置系统的语言。如[图8](#zh-cn_topic_0186390098_zh-cn_topic_0122145772_fig187301927172619)所示，用户也可根据实际情况进行调整，选择“中文”。
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->若选择“中文”，系统安装完成后，使用VNC登录不支持中文显示，使用串口登录支持中文显示，使用SSH登录时是否支持中文显示与使用的SSH客户端有关。若选择“English”，则无影响。  
-
-**图 8**  语言支持  
-![](figures/语言支持.png "语言支持")
-
-设置完成后，请单击左上角“完成”返回“安装概览”页面。
-
-## 设置时间和日期
-
-在“安装概览”页面中选择“时间和日期”，设置系统的时区、日期、时间等。
-
-设置时区时，用户可通过鼠标在地图上单击指定的城市，也可以通过页面顶部的“地区”和“城市”下拉菜单中进行选择，如[图9](#zh-cn_topic_0186390096_zh-cn_topic_0122145900_fig1260162652312)所示。
-
-如果您所在城市没有出现在地图或下拉菜单中，请选择同一时区中离您最近的城市。
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->-   手动设置时区时，请先关闭右上角“网络时间”同步开关。  
->-   如需使用网络时间，请保证网络能连通远程NTP服务器，设置网络具体请参见“[设置网络和主机名](#设置网络和主机名)”。  
-
-**图 9**  日期和时间  
-![](figures/日期和时间.png "日期和时间")
-
-设置完成后，请单击左上角“完成”返回“安装概览”页面。
-
-## 设置安装源
-
-在“安装概览”页面中选择“安装源”，指定安装源的位置。
-
-当使用完整光盘安装，安装程序会自动探测并显示安装源信息，用户直接使用默认配置即可，不需要进行设置，如[图10](#zh-cn_topic_0186390100_zh-cn_topic_0144427079_fig93633295132)所示。
-
-**图 10**  安装源  
-![](figures/安装源.png "安装源")
-
-当使用网络https源进行安装的时候，如果https服务器使用的是私有证书，则需要在安装引导界面按“e”进入已选选项的参数编辑界面，在参数中增加inst.noverifyssl参数，如[图11](#fig113517811415)所示。
-
-**图 11**  增加inst.noverifyssl参数  
-![](figures/增加inst-noverifyssl参数.png "增加inst-noverifyssl参数")
-
-设置完成后，请单击左上角“完成”返回“安装概览”页面。
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->安装过程中，如果“设置安装源”有疑问，可参考“[选择安装源出现异常](FAQ.html#选择安装源出现异常)”。  
-
-## 选择安装软件
-
-在“安装概览”页面中选择“软件选择”，指定需要安装的软件包。
-
-用户需要根据实际的业务需求，在左侧选择一个“最小安装”，在右侧选择安装环境的附加选项，如[图12](#zh-cn_topic_0186390261_zh-cn_topic_0122145865_fig03031519101414)所示。
-
-**图 12**  软件选择  
-![](figures/软件选择.png "软件选择")
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->-   在最小安装的环境下，并非安装源中所有的包都会安装。如果用户需要使用的包未安装，可将安装源挂载到本地制作repo源，通过DNF工具单独安装。  
->-   选择“虚拟化主机”时会默认安装虚拟化组件qemu、libvirt、edk2，且可在附件选项处选择是否安装ovs等组件。    
-
-设置完成后，请单击左上角“完成”返回“安装概览”页面。
-
-## 设置安装目的地
-
-在“安装概览”页面中选择“安装目的地”，设置操作系统的安装磁盘及分区。
-
-在[图13](#fig1195417125015)所示的页面中您可以看到计算机中的本地可用存储设备。
-
->![](public_sys-resources/icon-notice.gif) **须知：**   
->在选择您需要安装的设备时，建议不要选择NVMe SSD存储介质作为操作系统的安装磁盘。  
-
-**图 13**  安装目标位置  
-![](figures/安装目标位置.png "安装目标位置")
-
-### 存储配置
-
-在“安装目标位置”界面，您需要进行存储配置以便对系统分区。您可以手动配置分区，也可以选择让安装程序自动分区。
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->-   在进行分区时，出于系统性能和安全的考虑，建议您划分如下单独分区：/boot、/var、/var/log 、/var/log/audit、/home、/tmp。  
->-   系统如果配置了swap分区，当系统的物理内存不够用时，会使用swap分区。虽然 swap分区可以增大物理内存大小的限制，但是如果由于内存不足使用到swap分区，会增加系统的响应时间，性能变差。因此在物理内存充足或者性能敏感的系统中，不建议配置swap分区。  
->-   如果需要拆分逻辑卷组则需要选择“自定义”进行手动分区，并在“手动分区”界面单击“卷组”区域中的“修改”按钮重新配置卷组。  
-
-**自动**
-
-如果是在未使用过的存储设备中执行全新安装，或者不需要保留该存储设备中任何数据，建议选择“自动”进行自动分区。
-
-若您需要对数据进行加密，您可以在“安装目标位置”界面选择“加密我的数据”，并单击左上角“完成”，出现如[图14](#fig_setcode)所示的“磁盘加密口令”对话框。请分别在“口令”和“确认”中输入相同的加密口令，且口令需要符合密码复杂度，具体请参考[密码复杂度](#密码复杂度)。设置完成后，请单击“保存口令”返回“安装概览”页面。
-
->![](figures/zh-cn_image_0229291229.png)   
->若口令丢失，将无法找回，且无法访问所有加密的分区以及其中的数据。请妥善保管口令。
-
-**图 14** 磁盘加密口令   
-![](figures/磁盘加密口令.png "磁盘加密口令")
-
-**自定义**
-
-若用户需进行手动分区，选择“自定义”按钮，并单击左上角“完成”，出现手动分区界面。
-
-在“手动分区”界面可以通过如下两种方式进行分区，分区完成后如[图15](#fig1277151815248)所示。
-
-- 自动创建：在界面单击“点击这里自动创建它们”，系统会根据可用的存储空间，自动分出4个挂载点：/boot 、/、/boot/efi、swap。
-
-- 手动创建：单击“![](figures/zh-cn_image_0229291243.png)”添加新挂载点，建议每个挂载点的期望容量不超过可用空间。
-
-    >![](public_sys-resources/icon-note.gif) **说明：**   
-    >若设置的挂载点期望容量超过了可用空间，系统将剩余的可用空间全部分配给该挂载点。  
-
-**图 15**  手动分区  
-![](figures/手动分区.png "手动分区")
-
-若您需要对数据进行加密，您可以在需要加密的挂载点的“设备类型”区域中选择“加密”，并单击左上角“完成”，出现如[图14](#fig_setcode)所示的“磁盘加密口令”对话框。请分别在“口令”和“确认”中输入相同的加密口令，且口令需要符合密码复杂度，具体请参考[密码复杂度](#密码复杂度)。设置完成后，请单击“保存口令”返回“手动分区”界面。
-
->![](figures/zh-cn_image_0229291229.png)   
->若口令丢失，将无法找回，且无法访问所有加密的分区以及其中的数据。请妥善保管口令。
-
-设置完成后，请单击左上角“完成”返回“安装概览”页面。
-
-## 设置网络和主机名
-
-在“安装概览”页面中选择“网络和主机名”，设置系统的网络功能。
-
-安装程序会自动探测可本地访问的接口。探测到的接口列在左侧方框中，右侧显示相应的接口详情，如[图16](#zh-cn_topic_0186390264_zh-cn_topic_0122145831_fig123700157297)所示。用户可以通过页面右上角的开关，来开启或者关闭网络接口。用户还可以单击“配置”以配置选中的接口。
-
-用户可在页面下方“主机名”字段输入主机名。主机名可以是完全限定域名（FQDN），其格式为hostname.domainname；也可以是简要主机名，其格式为hostname。
-
-**图 16**  网络和主机名  
-![](figures/网络和主机名.png "网络和主机名")
-
-设置完成后，请单击左上角“完成”返回“安装概览”页面。
-
-## 设置根密码
-
-在“安装概览”页面中选择“根密码”，弹出设置“ROOT密码”界面，如[图17](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig1323165793018)所示，根据[密码复杂度](#密码复杂度)输入密码并再次输入密码进行确认。
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->
->- root帐户是用来执行关键系统管理任务，不建议您在日常工作及系统访问时使用root帐户。
->
->- 在“ROOT密码”界面若选择“锁定root帐户”则root帐户将禁用。  
-
-**图 17**  root密码  
-![](figures/root密码.png "root密码")
-
-### 密码复杂度
-
-用户设置的root用户密码或新创建用户的密码均需要满足密码复杂度要求，否则会导致密码设置或用户创建失败。设置密码的复杂度的要求如下：
-
-1.  口令长度至少8个字符。
-2.  口令至少包含大写字母、小写字母、数字和特殊字符中的任意3种。
-3.  口令不能和账号一样。
-4.  口令不能使用字典词汇。
-
-    >![](public_sys-resources/icon-note.gif) **说明：**   
-    > 在已装好的openEuler环境中，可以通过`cracklib-unpacker /usr/share/cracklib/pw_dict > dictionary.txt`命令导出字典库文件dictionary.txt，用户可以查询密码是否在该字典中。
-
-完成设置后，单击左上角的“完成”返回“安装概览”页面。
-
-## 创建用户
-
-在“安装概览”页面中选择“创建用户”，弹出“创建用户”的界面如[图18](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig1237715313319)所示。输入用户名，并设置密码。另外您还可以通过“高级”选项设置用户主目录、用户组等，如[图19](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig128716531312)所示。
-
-**图 18**  创建用户  
-![](figures/创建用户.png "创建用户")
-
-**图 19**  高级用户配置  
-![](figures/高级用户配置.png "高级用户配置")
-
-完成设置后，单击左上角的“完成”返回“安装概览”页面。
-
-
-## 开始安装
-
-在安装界面上完成所有必填选项的配置后，界面上的警告会消失。此时，用户可以单击“开始安装”进行系统安装。
-
-**图 20**  开始安装  
-![](figures/开始安装.png "开始安装")
-
-## 安装过程
-
-开始安装后会出现进度页面，显示安装进度及所选软件包写入系统的进度，如[图21](zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig1590863119306)所示。
-
->![](figures/zh-cn_image_0229291229.png)   
->若系统安装过程中，单击“退出”，或复位、下电服务器，则安装过程被中断，系统将不可用，需要重新进行安装。
-
-**图 21**  安装过程  
-![](figures/安装过程.png "安装过程")
-
-
-## 安装完成
-
-此刻，openEuler已完成安装，如[图22](#zh-cn_topic_0186390267_zh-cn_topic_0122145917_fig1429512116338)所示。单击“重启系统”后，系统将重新启动。
-
-**图 22**  完成安装  
-![](figures/完成安装.png "完成安装")
-
--   如果当前使用物理光盘安装操作系统，且在重启过程中安装光盘没有自动弹出，请手动取出光盘，则可以直接进入openEuler命令行登录界面。
--   如果当前使用虚拟光驱安装操作系统，则需要修改服务器的启动项为“硬盘”，然后重启服务器，则可以直接进入openEuler命令行登录界面。
+# 安装指导
+
+本章以光盘安装为例介绍安装openEuler，其他安装方式除在启动安装时的引导方式不同外，待启动安装后则安装流程相同，在此不再说明。
+
+
+- [安装指导](#安装指导)
+    - [启动安装](#启动安装)
+        - [使用光盘引导安装](#使用光盘引导安装)
+        - [安装引导界面](#安装引导界面)
+        - [图形化模式安装](#图形化模式安装)
+    - [设置安装程序语言](#设置安装程序语言)
+    - [进入安装界面](#进入安装界面)
+    - [设置键盘](#设置键盘)
+    - [设置系统语言](#设置系统语言)
+    - [设置时间和日期](#设置时间和日期)
+    - [设置安装源](#设置安装源)
+    - [选择安装软件](#选择安装软件)
+    - [设置安装位置](#设置安装位置)
+        - [存储配置](#存储配置)
+    - [设置网络和主机名](#设置网络和主机名)
+    - [开始安装](#开始安装)
+    - [安装过程配置](#安装过程配置)
+        - [密码复杂度](#密码复杂度)
+        - [设置root密码](#设置root密码)
+        - [创建用户](#创建用户)
+    - [安装完成](#安装完成)
+
+
+
+## 启动安装
+
+### 使用光盘引导安装
+
+在服务器的光驱中加载openEuler安装镜像，重启服务器，具体步骤如下。
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>在安装开始前，需要保证服务器启动选项为光驱优先。安装步骤以BMC挂载虚拟光驱进行光盘安装的操作举例。通过物理光驱安装的操作简单，启动安装后的流程相同，在此不再说明。  
+
+1.  在虚拟界面工具栏中，单击虚拟光驱工具如下图所示。
+
+    **图 1**  光驱图标  
+    ![](./figures/CD-ROM_drive_icon.png)
+
+    弹出镜像对话框，如下图所示。
+
+    **图 2**  镜像对话框  
+    ![](./figures/Image_dialog_box.png)
+
+2.  在镜像对话框中，选择“镜像文件”， 并单击“浏览”。弹出“打开”对话框。
+3.  选择镜像文件，单击“打开”。然后在镜像对话框中，单击“连接”。当“连接”显示为“断开”后，表示虚拟光驱已连接到服务器。
+4.  在工具栏中，单击重启工具重启设备，如下图所示。
+
+    **图 3**  重启图标  
+    ![](./figures/restarticon.png)
+
+
+### 安装引导界面
+
+系统使用引导介质完成引导后会显示引导菜单。该引导菜单除启动安装程序外还提供一些选项。安装系统时，默认采用“Test this media & install openEuler 20.03 LTS”方式进行安装。如果要选择默认选项之外的选项，请使用键盘中的“↑”和“↓”方向键进行选择，并在选项为高亮状态时按“Enter”。
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>-   如果60秒内未按任何键，系统将从默认选项“Test this media & install openEuler 20.03 LTS”自动进入安装界面。  
+>-   安装物理机时，如果使用键盘上下键无法选择启动选项，按“Enter”键无响应，可以单击BMC界面上的鼠标控制图标“![](./figures/zh-cn_image_0229420473.png)”，设置“键鼠复位”。  
+
+**图 4**  安装引导界面  
+![](./figures/Installation_wizard.png)
+
+安装引导选项说明如下：
+
+-   Install openEuler 20.03 LTS —— 在您的服务器上使用图形用户界面模式安装。
+
+-   Test this media & install openEuler 20.03 LTS —— 默认选项，在您的服务器上使用图形用户界面模式安装，但在启动安装程序前会进行安装介质的完整性检查。
+
+-   Troubleshooting —— 问题定位模式，系统无法正常安装时使用。进入问题定位模式后，有如下两个选项。
+    -   Install openEuler 20.03-LTS in basic graphics mode —— 简单图形安装模式，该模式下在系统启动并运行之前不启动视频驱动程序。
+    -   Rescue the openEuler system —— 救援模式，用于修复系统。该模式下输出定向到VNC或BMC（Baseboard Management Controller）端，串口不可用。
+
+在安装引导界面，按“e”进入已选选项的参数编辑界面，按“c”进入命令行模式。
+
+### 图形化模式安装
+
+在“安装引导界面”中选择“Test this media & install openEuler 20.03 LTS”进入图形化模式安装。
+
+可以通过键盘操作图形化安装程序。
+
+-   “Tab”、“shift Tab”：界面控件（按钮、区域框、复选框等）间的移动。
+-   “↑”、“↓”方向键：列表里的移动。
+-   “←”、“→”方向键：水平工具条和表条间移动。
+-   “空格”、“Enter”：选择或删除高亮显示的选项、展开或折叠下拉菜单。
+-   “Alt”+“快捷键”：选择快捷键所在的控件，其中快捷键可通过按住Alt高亮（加下划线）显示。
+
+## 设置安装程序语言
+
+启动安装后，在进入安装程序主界面之前，系统会提示用户设置安装过程中使用的语言。当前默认为英语，用户可根据实际情况进行调整，如[图5](#zh-cn_topic_0186390093_zh-cn_topic_0122145864_fig144630179151)所示，选择“中文”。
+
+**图 5**  选择语言  
+![](./figures/selectlanguage.png)
+
+完成设置后，单击“继续”，进入安装设置主界面。
+
+如果您想退出安装，可以单击“退出”并在弹出的“您确定要退出安装程序吗？”对话框中单击“是”重新进入“安装引导界面”。
+
+## 进入安装界面
+
+系统安装程序正常启动后，会进入[图6](#zh-cn_topic_0186390094_zh-cn_topic_0122145883_fig5969171592212)所示的安装设置主界面。用户可以进行时间、语言、安装源、网络、安装位置等相关设置。
+
+部分配置项会有告警符号，用户完成该选项配置后，告警符号消失。当界面上不存在告警符号时，用户才能单击“开始安装”进行系统安装。
+
+如果您想退出安装，可以单击“退出”并在弹出的“您确定要退出安装程序吗？”对话框中单击“是”重新进入“安装引导界面”。
+
+**图 6**  安装概览  
+![](./figures/Installation_Overview.png)
+
+## 设置键盘
+
+在“安装概览”页面中选择“键盘”，用户可以在系统中添加或者删除多个键盘布局。
+
+-   要查看键盘布局，请在左侧选框中单击选中该键盘布局，然后单击下面的“键盘”按钮。
+-   要测试键盘布局，请在左侧选框中添加键盘布局，然后在右上角键盘图标处进行点击切换为目标键盘，单击右侧文本框内部，输入文本以确认所选键盘布局可正常工作。
+
+**图 7**  键盘布局  
+![](./figures/Keyboard_layout.png)
+
+设置完成后，请单击左上角“完成”返回“安装概览”页面。
+
+## 设置系统语言
+
+在“安装概览”页面中选择“语言支持”，设置系统的语言。如[图8](#zh-cn_topic_0186390098_zh-cn_topic_0122145772_fig187301927172619)所示，用户也可根据实际情况进行调整，选择“中文”。
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>若选择“中文”，系统安装完成后，使用VNC登录不支持中文显示，使用串口或者SSH等方式登录支持中文显示。若选择“English”，则无影响。  
+
+**图 8**  语言支持  
+![](./figures/languagesupport.png)
+
+设置完成后，请单击左上角“完成”返回“安装概览”页面。
+
+## 设置时间和日期
+
+在“安装概览”页面中选择“时间和日期”，设置系统的时区、日期、时间等。
+
+设置时区时，用户可通过鼠标在地图上单击指定的城市，也可以通过页面顶部的“地区”和“城市”下拉菜单中进行选择，如[图9](#zh-cn_topic_0186390096_zh-cn_topic_0122145900_fig1260162652312)所示。
+
+如果您所在城市没有出现在地图或下拉菜单中，请选择同一时区中离您最近的城市。
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>-   手动设置时区时，请先关闭右上角“网络时间”同步开关。  
+>-   如需使用网络时间，请保证网络能连通远程NTP服务器，设置网络具体请参见“[设置网络和主机名](#设置网络和主机名)”。  
+
+**图 9**  日期和时间  
+![](./figures/dateandtime.png)
+
+设置完成后，请单击左上角“完成”返回“安装概览”页面。
+
+## 设置安装源
+
+在“安装概览”页面中选择“安装源”，指定安装源的位置。
+
+当使用完整光盘安装，安装程序会自动探测并显示安装源信息，用户直接使用默认配置即可，不需要进行设置，如[图10](#zh-cn_topic_0186390100_zh-cn_topic_0144427079_fig93633295132)所示。
+
+**图 10**  安装源  
+![](./figures/Installation_source.png)
+
+当使用网络https源进行安装的时候，如果https服务器使用的是私有证书，则需要在安装引导界面按“e”进入已选选项的参数编辑界面，在参数中增加inst.noverifyssl参数，如[图11](#fig113517811415)所示。
+
+**图 11**  增加inst.noverifyssl参数  
+![](./figures/add_inst-noverifyssl.png)
+
+设置完成后，请单击左上角“完成”返回“安装概览”页面。
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>安装过程中，如果“设置安装源”有疑问，可参考“[选择安装源出现异常](./FAQ.html#选择安装源出现异常)”。  
+
+## 选择安装软件
+
+在“安装概览”页面中选择“软件选择”，指定需要安装的软件包。
+
+用户需要根据实际的业务需求，在左侧选择一个“最小安装”，在右侧选择安装环境的附加选项，如[图12](#zh-cn_topic_0186390261_zh-cn_topic_0122145865_fig03031519101414)所示。
+
+**图 12**  软件选择  
+![](./figures/choosesoftware.png)
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>-   在最小安装的环境下，并非安装源中所有的包都会安装。如果用户需要使用的包未安装，可将安装源挂载到本地制作repo源，通过DNF工具单独安装。  
+>-   选择“虚拟化主机”时会默认安装虚拟化组件qemu、libvirt、edk2，且可在附件选项处选择是否安装ovs等组件。    
+
+设置完成后，请单击左上角“完成”返回“安装概览”页面。
+
+## 设置安装位置
+
+在“安装概览”页面中选择“安装位置”，设置操作系统的安装磁盘及分区。
+
+在[图13](#fig1195417125015)所示的页面中您可以看到计算机中的本地可用存储设备。您还可以通过单击“添加磁盘”，添加指定的附加设备或者网络设备。
+
+>![](./public_sys-resources/icon-notice.gif) **须知：**   
+>在选择您需要安装的设备时，建议不要选择NVMe SSD存储介质作为操作系统的安装磁盘。  
+
+**图 13**  安装目标位置  
+![](./figures/Target_installation_position.png)
+
+### 存储配置
+
+在“安装目标位置”界面，您需要进行存储配置以便对系统分区。您可以手动配置分区，也可以选择让安装程序自动分区。
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>-   在进行分区时，出于系统性能和安全的考虑，建议您划分如下单独分区：/boot、/var、/var/log 、/var/log/audit、/home、/tmp。  
+>-   系统如果配置了swap分区，当系统的物理内存不够用时，会使用swap分区。虽然 swap分区可以增大物理内存大小的限制，但是如果由于内存不足使用到swap分区，会增加系统的响应时间，性能变差。因此在物理内存充足或者性能敏感的系统中，不建议配置swap分区。  
+>-   如果需要拆分逻辑卷组则需要选择“自定义”进行手动分区，并在“手动分区”界面单击“卷组”区域中的“修改”按钮重新配置卷组。  
+
+**自动**
+
+如果是在未使用过的存储设备中执行全新安装，或者不需要保留该存储设备中任何数据，建议选择“自动”进行自动分区。
+
+**自定义**
+
+若用户需进行手动分区，选择“自定义”按钮，并单击左上角“完成”，出现如下手动分区界面。
+
+**图 14**  手动分区  
+![](./figures/Manual_partitioning.png)
+
+在“手动分区”界面可以通过如下两种方式进行分区。
+
+-   自动创建：在界面单击“点击这里自动创建它们”，系统会根据可用的存储空间，自动分出4个挂载点：/boot 、/、/boot/efi、swap。
+-   手动创建：单击“![](./figures/zh-cn_image_0229291243.png)”添加新挂载点，建议每个挂载点的期望容量不超过可用空间。
+
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
+    >若设置的挂载点期望容量超过了可用空间，系统将剩余的可用空间全部分配给该挂载点。  
+
+
+设置完成后，请单击左上角“完成”返回“安装概览”页面。
+
+## 设置网络和主机名
+
+在“安装概览”页面中选择“网络和主机名”，设置系统的网络功能。
+
+安装程序会自动探测可本地访问的接口。探测到的接口列在左侧方框中，右侧显示相应的接口详情，如[图15](#zh-cn_topic_0186390264_zh-cn_topic_0122145831_fig123700157297)所示。用户可以通过页面右上角的开关，来开启或者关闭网络接口。用户还可以单击“配置”以配置选中的接口。
+
+用户可在页面下方“主机名”字段输入主机名。主机名可以是完全限定域名（FQDN），其格式为hostname.domainname；也可以是简要主机名，其格式为hostname。
+
+**图 15**  网络和主机名  
+![](./figures/NetworkandHostName.png)
+
+设置完成后，请单击左上角“完成”返回“安装概览”页面。
+
+## 开始安装
+
+在安装界面上完成所有必填选项的配置后，界面上的警告会消失。此时，用户可以单击“开始安装”进行系统安装。
+
+**图 16**  开始安装  
+![](./figures/startinstall.png)
+
+## 安装过程配置
+
+开始安装后会出现进度页面，显示安装进度及所选软件包写入系统的进度。
+
+**图 17**  安装过程  
+![](./figures/Installation_Procedure.png )
+
+安装软件包的过程中，需要用户配置root密码、根据个人需求可以创建用户。
+
+### 密码复杂度
+
+用户设置的root用户密码或新创建用户的密码均需要满足密码复杂度要求，否则会导致密码设置或用户创建失败。设置密码的复杂度的要求如下：
+
+1.  口令长度至少8个字符。
+2.  口令至少包含大写字母、小写字母、数字和特殊字符中的任意3种。
+3.  口令不能和账号一样。
+4.  口令不能使用字典词汇。
+    -   查询字典
+
+        在已装好的openEuler环境中，可以通过如下命令导出字典库文件dictionary.txt，用户可以查询密码是否在该字典中。
+
+        ```
+        cracklib-unpacker /usr/share/cracklib/pw_dict > dictionary.txt
+        ```
+
+    -   修改字典
+        1.  修改上面导出的字典文件，执行如下命令更新系统字典库。
+
+            ```
+            # create-cracklib-dict dictionary.txt
+            ```
+
+        2.  在原字典库基础上新增其他字典内容custom.txt。
+
+            ```
+            # create-cracklib-dict dictionary.txt custom.txt
+            ```
+
+
+
+
+### 设置root密码
+
+单击“root密码”，弹出设置密码界面如[图18](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig1323165793018)所示，输入密码并再次输入密码进行确认。
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>root密码需要在安装软件包的同时进行配置，如果不配置该密码则无法完成安装。root账户是用来执行关键系统管理任务，不建议您在日常工作及系统访问时使用root账户。  
+
+**图 18**  root密码  
+![](./figures/root_password.png)
+
+完成设置后，单击左上角的“完成”返回安装过程界面。
+
+### 创建用户
+
+单击“创建用户”，弹出创建用户的界面如[图19](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig1237715313319)所示。输入用户名，并设置密码。另外您还可以通过“高级”选项设置用户主目录、用户组等，如[图20](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig128716531312)所示。
+
+**图 19**  创建用户  
+![](./figures/createuser.png)
+
+**图 20**  高级用户配置  
+![](./figures/Advanced_User_Configuration.png)
+
+完成设置后，单击左上角的“完成”返回安装过程界面。
+
+单击“结束配置”，完成openEuler的相关配置。
+
+![](./figures/Ending_Configuration-new.png)
+
+## 安装完成
+
+此刻，openEuler已完成安装，如[图21](#zh-cn_topic_0186390267_zh-cn_topic_0122145917_fig1429512116338)所示。单击“重启”后，系统将重新启动。
+
+**图 21**  完成安装  
+![](./figures/completeinstall.png)
+
+-   如果当前使用物理光盘安装操作系统，且在重启过程中安装光盘没有自动弹出，请手动取出光盘，则可以直接进入openEuler命令行登录界面。
+-   如果当前使用虚拟光驱安装操作系统，则需要修改服务器的启动项为“硬盘”，然后重启服务器，则可以直接进入openEuler命令行登录界面。
diff --git "a/content/zh/docs/Installation/\345\256\211\350\243\205\346\226\271\345\274\217\344\273\213\347\273\215.md" "b/docs/zh/docs/20.03_LTS/docs/Installation/\345\256\211\350\243\205\346\226\271\345\274\217\344\273\213\347\273\215.md"
similarity index 85%
rename from "content/zh/docs/Installation/\345\256\211\350\243\205\346\226\271\345\274\217\344\273\213\347\273\215.md"
rename to "docs/zh/docs/20.03_LTS/docs/Installation/\345\256\211\350\243\205\346\226\271\345\274\217\344\273\213\347\273\215.md"
index d8d0dfc4ac471a4c83255ba38e7eacc1d417cbdc..df3964172ce4861ffec14a790f0c58cea76a6b75 100644
--- "a/content/zh/docs/Installation/\345\256\211\350\243\205\346\226\271\345\274\217\344\273\213\347\273\215.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Installation/\345\256\211\350\243\205\346\226\271\345\274\217\344\273\213\347\273\215.md"
@@ -1,209 +1,209 @@
-# 安装方式介绍
-
->![](public_sys-resources/icon-notice.gif) **须知：**   
->-   硬件服务器仅支持Taishan 200服务器和FusionServer Pro 机架服务器，具体支持的服务器型号可参考“[硬件兼容支持](安装准备.html#硬件兼容支持)”；虚拟化平台仅支持openEuler自有的虚拟化组件（HostOS为openEuler，虚拟化组件为发布包中的qemu、KVM）创建的虚拟化平台和华为公有云的x86虚拟化平台。  
->-   安装方式当前仅支持光盘、USB盘安装、网络安装、qcow2镜像安装和私有镜像安装。其中仅华为公有云的x86虚拟化平台支持私有镜像安装。
-
-
-- [安装方式介绍](#安装方式介绍)
-    - [通过光盘安装](#通过光盘安装)
-        - [准备安装源](#准备安装源)
-        - [启动安装](#启动安装)
-    - [通过USB盘安装](#通过usb盘安装)
-        - [准备安装源](#准备安装源-1)
-        - [启动安装](#启动安装-1)
-    - [使用PXE通过网络安装](#使用pxe通过网络安装)
-    - [通过qcow2镜像安装](#通过qcow2镜像安装)
-        - [制作qcow2镜像](#制作qcow2镜像)
-        - [启动安装](#启动安装-2)
-    - [通过私有镜像安装](#通过私有镜像安装)
-        - [制作私有镜像](#制作私有镜像)
-        - [启动安装](#启动安装-3)
-
-
-
-## 通过光盘安装
-
-本节介绍如何使用或者制作光盘安装源，并介绍相应的操作步骤，指导用户进行安装。
-
-### 准备安装源
-
-如果您获取的是系统安装光盘，那么可以直接使用光盘安装系统。如果您获取的是系统ISO镜像，可以通过刻录软件将系统的ISO镜像刻录到DVD中，使用刻录完成的DVD安装系统。
-
-### 启动安装
-
-根据以下步骤启动安装程序：
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->您需要先设置您的系统优先从光盘进行启动引导。以BIOS为例，您需要将“Boot Type Order”中的“CD/DVD-ROM Drive”选项调整到首位。  
-
-1.  断开所有安装不需要的驱动器，比如USB。
-2.  启动您的计算机系统。
-3.  在计算机中插入安装光盘。
-4.  重启计算机系统。
-
-在短暂的延迟后会出现图形化引导界面，该界面包含不同引导选项。如果您在一分钟内未进行任何操作，安装程序将自动以默认选项开始运行。
-
-## 通过USB盘安装
-
-本节介绍如何制作USB盘安装源，并介绍基本的操作步骤，指导用户进行安装。
-
-### 准备安装源
-
-您需要注意USB盘容量的大小，它必须有足够的的空间放下整个镜像，建议USB盘空间大于16G。
-
-1.  将USB盘连接到该系统中，并执行 dmesg 命令查看相关的日志信息。在该日志的最后可以看到刚刚连接的USB盘所生成的一组信息，应类似如下：
-
-    ```
-    [ 170.171135] sd 5:0:0:0: [sdb] Attached SCSI removable disk
-    ```
-
-    >![](public_sys-resources/icon-note.gif) **说明：**   
-    >连接的USB盘名称以sdb进行举例。  
-
-2.  切换为root用户。使用su命令，需要输入相应的密码。
-
-    ```
-    $ su - root
-    ```
-
-3.  确保USB盘没有被挂载。使用如下命令进行查询：
-
-    ```
-    # findmnt /dev/sdb
-    ```
-
-    - 如果执行此命令后无输出，表明未挂载，可以继续执行下一步。
-
-    - 如果输出以下信息，表明USB盘已经自动挂载。
-
-        ```
-        # findmnt /dev/sdb
-        TARGET   SOURCE   FSTYPE  OPTIONS
-        /mnt/iso /dev/sdb iso9660 ro,relatime
-        ```
-
-        此时，您需要使用umount命令卸载该设备。
-
-        ```
-        # umount /mnt/iso
-        ```
-
-4.  使用dd命令将ISO安装镜像直接写入USB盘：
-
-    ```
-    # dd if=/path/to/image.iso of=/dev/device bs=blocksize
-    ```
-
-    使用您下载的ISO镜像文件的完整路径替换 /path/to/image.iso，使用之前由 dmesg 命令给出的设备名称替换device，同时设置合理的块大小（例如：512k）替换 blocksize，这样可以加快写入进度。
-
-    例如：如果该ISO镜像文件位于 /home/testuser/Downloads/openEuler-20.09-beta-aarch64-dvd.iso，同时探测到的设备名称为sdb，则该命令如下：
-
-    ```
-    # dd if=/home/testuser/Downloads/openEuler-20.09-beta-aarch64-dvd.iso of=/dev/sdb bs=512k
-    ```
-
-5.  等待镜像写入完成，拔掉USB盘。
-
-    镜像写入过程中不会有进度显示，当\#号再次出现时，表明写入完成。退出root账户，拔掉USB盘。此时，您可以使用该USB盘作为系统的安装源。
-
-
-### 启动安装
-
-请根据以下步骤启动安装程序：
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->您需要先设置您的系统优先从USB进行启动引导。以BIOS为例，您需要将“Boot Type Order”中的USB选项调整到首位。  
-
-1.  断开所有安装不需要的驱动器。
-2.  打开您的计算机系统。
-3.  在计算机中插入USB盘。
-4.  重启计算机系统。
-
-在短暂的延迟后会出现图形化引导页面，该页面包含不同引导选项。如果您在一分钟内未进行任何操作，安装程序将自动开始安装。
-
-## 使用PXE通过网络安装
-
-要使用 PXE 引导，您需要正确配置服务器以及您的计算机需支持 PXE 的网络接口。
-
-如果目标硬件安装有支持PXE的网络接口卡，我们可以配置它从其他网络系统的文件而不是本地介质（如光盘）来引导计算机并执行Anaconda安装程序。
-
-对于PXE网络安装，客户机通过支持PXE的网卡，向网络发送请求DHCP信息的广播，请求IP地址等信息。DHCP服务器给客户机提供一个IP地址和其他网络信息如域名服务器、ftp服务器（它提供启动安装程序所必须的文件）的IP地址或主机名，以及服务器上文件的位置。
-
->![](public_sys-resources/icon-note.gif) **说明：**   
->此处不详细讨论tftp、DHCP、http等服务器配置，相关详细配置请参考“[全自动化安装指导](使用kickstart自动化安装.html#全自动化安装指导)”。  
-
-## 通过qcow2镜像安装
-
-本节介绍如何使用或者制作qcow2镜像，并介绍相应的操作步骤，指导用户进行安装。
-
-### 制作qcow2镜像
-
-1.  安装qemu-img软件包。
-
-    ```
-    # dnf install -y qemu-img
-    ```
-
-2.  使用qemu-img工具的create命令，创建镜像文件，命令格式为：
-
-    ```
-    $ qemu-img create -f  -o   
-    ```
-
-    其中，各参数含义如下：
-
-    -   _imgFormat_  ：镜像格式，取值为raw, qcow2等。
-    -   _fileOption_  ：文件选项，用于设置镜像文件的特性，如指定后端镜像文件，压缩，加密等特性。
-    -   _fileName_  ：文件名称。
-    -   _diskSize_  ：磁盘大小，用于指定块磁盘设备的大小，支持的单位有K、M、G、T，分别代表KiB、MiB、GiB、TiB。
-
-    例如，创建一个磁盘设备大小为32GB、格式为qcow2的镜像文件openEuler-imge.qcow2，命令和回显如下：
-
-    ```
-    $ qemu-img create -f qcow2 openEuler-image.qcow2 32G
-    Formatting 'openEuler-image.qcow2', fmt=qcow2 size=34359738368 cluster_size=65536 lazy_refcounts=off refcount_bits=16
-    ```
-
-
-### 启动安装
-
-根据以下步骤启动安装程序：
-
-1.  准备qcow2镜像文件。
-2.  准备虚拟机网络。
-3.  准备UEFI引导工具集EDK II。
-4.  准备虚拟机XML配置文件。
-5.  创建虚拟机。
-6.  启动虚拟机。
-
-各步骤详细的操作请参考《[openEuler 20.09 beta 虚拟化用户指南](../Virtualization/virtualization.html)》。
-
-## 通过私有镜像安装
-
-本节介绍如何使用或者制作私有镜像，并介绍相应的操作步骤，指导用户进行安装。
-
-### 制作私有镜像
-
-制作私有镜像的方法请参见[《镜像服务用户指南》](https://support.huaweicloud.com/usermanual-ims/zh-cn_topic_0013901628.html)。
-
-### 启动安装
-
-华为公有云的x86虚拟化平台的启动请参见[ 弹性云服务器 ECS的用户指南](https://support.huaweicloud.com/wtsnew-ecs/index.html)。
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+# 安装方式介绍
+
+>![](./public_sys-resources/icon-notice.gif) **须知：**   
+>-   硬件服务器仅支持Taishan 200服务器和FusionServer Pro 机架服务器，具体支持的服务器型号可参考“[硬件兼容支持](./安装准备.html#硬件兼容支持)”；虚拟化平台仅支持openEuler自有的虚拟化组件（HostOS为openEuler，虚拟化组件为发布包中的qemu、KVM）创建的虚拟化平台和华为公有云的x86虚拟化平台。  
+>-   安装方式当前仅支持光盘、USB盘安装、网络安装、qcow2镜像安装和私有镜像安装。其中仅华为公有云的x86虚拟化平台支持私有镜像安装。
+
+
+- [安装方式介绍](#安装方式介绍)
+    - [通过光盘安装](#通过光盘安装)
+        - [准备安装源](#准备安装源)
+        - [启动安装](#启动安装)
+    - [通过USB盘安装](#通过usb盘安装)
+        - [准备安装源](#准备安装源-1)
+        - [启动安装](#启动安装-1)
+    - [使用PXE通过网络安装](#使用pxe通过网络安装)
+    - [通过qcow2镜像安装](#通过qcow2镜像安装)
+        - [制作qcow2镜像](#制作qcow2镜像)
+        - [启动安装](#启动安装-2)
+    - [通过私有镜像安装](#通过私有镜像安装)
+        - [制作私有镜像](#制作私有镜像)
+        - [启动安装](#启动安装-3)
+
+
+
+## 通过光盘安装
+
+本节介绍如何使用或者制作光盘安装源，并介绍相应的操作步骤，指导用户进行安装。
+
+### 准备安装源
+
+如果您获取的是系统安装光盘，那么可以直接使用光盘安装系统。如果您获取的是系统ISO镜像，可以通过刻录软件将系统的ISO镜像刻录到DVD中，使用刻录完成的DVD安装系统。
+
+### 启动安装
+
+根据以下步骤启动安装程序：
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>您需要先设置您的系统优先从光盘进行启动引导。以BIOS为例，您需要将“Boot Type Order”中的“CD/DVD-ROM Drive”选项调整到首位。  
+
+1.  断开所有安装不需要的驱动器，比如USB。
+2.  启动您的计算机系统。
+3.  在计算机中插入安装光盘。
+4.  重启计算机系统。
+
+在短暂的延迟后会出现图形化引导界面，该界面包含不同引导选项。如果您在一分钟内未进行任何操作，安装程序将自动以默认选项开始运行。
+
+## 通过USB盘安装
+
+本节介绍如何制作USB盘安装源，并介绍基本的操作步骤，指导用户进行安装。
+
+### 准备安装源
+
+您需要注意USB盘容量的大小，它必须有足够的的空间放下整个镜像，建议USB盘空间大于16G。
+
+1.  将USB盘连接到该系统中，并执行 dmesg 命令查看相关的日志信息。在该日志的最后可以看到刚刚连接的USB盘所生成的一组信息，应类似如下：
+
+    ```
+    [ 170.171135] sd 5:0:0:0: [sdb] Attached SCSI removable disk
+    ```
+
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
+    >连接的USB盘名称以sdb进行举例。  
+
+2.  切换为root用户。使用su命令，需要输入相应的密码。
+
+    ```
+    $ su - root
+    ```
+
+3.  确保USB盘没有被挂载。使用如下命令进行查询：
+
+    ```
+    # findmnt /dev/sdb
+    ```
+
+    - 如果执行此命令后无输出，表明未挂载，可以继续执行下一步。
+
+    - 如果输出以下信息，表明USB盘已经自动挂载。
+
+        ```
+        # findmnt /dev/sdb
+        TARGET   SOURCE   FSTYPE  OPTIONS
+        /mnt/iso /dev/sdb iso9660 ro,relatime
+        ```
+
+        此时，您需要使用umount命令卸载该设备。
+
+        ```
+        # umount /mnt/iso
+        ```
+
+4.  使用dd命令将ISO安装镜像直接写入USB盘：
+
+    ```
+    # dd if=/path/to/image.iso of=/dev/device bs=blocksize
+    ```
+
+    使用您下载的ISO镜像文件的完整路径替换 /path/to/image.iso，使用之前由 dmesg 命令给出的设备名称替换device，同时设置合理的块大小（例如：512k）替换 blocksize，这样可以加快写入进度。
+
+    例如：如果该ISO镜像文件位于 /home/testuser/Downloads/openEuler-20.03-LTS-aarch64-dvd.iso，同时探测到的设备名称为sdb，则该命令如下：
+
+    ```
+    # dd if=/home/testuser/Downloads/openEuler-20.03-LTS-aarch64-dvd.iso of=/dev/sdb bs=512k
+    ```
+
+5.  等待镜像写入完成，拔掉USB盘。
+
+    镜像写入过程中不会有进度显示，当\#号再次出现时，表明写入完成。退出root账户，拔掉USB盘。此时，您可以使用该USB盘作为系统的安装源。
+
+
+### 启动安装
+
+请根据以下步骤启动安装程序：
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>您需要先设置您的系统优先从USB进行启动引导。以BIOS为例，您需要将“Boot Type Order”中的USB选项调整到首位。  
+
+1.  断开所有安装不需要的驱动器。
+2.  打开您的计算机系统。
+3.  在计算机中插入USB盘。
+4.  重启计算机系统。
+
+在短暂的延迟后会出现图形化引导页面，该页面包含不同引导选项。如果您在一分钟内未进行任何操作，安装程序将自动开始安装。
+
+## 使用PXE通过网络安装
+
+要使用 PXE 引导，您需要正确配置服务器以及您的计算机需支持 PXE 的网络接口。
+
+如果目标硬件安装有支持PXE的网络接口卡，我们可以配置它从其他网络系统的文件而不是本地介质（如光盘）来引导计算机并执行Anaconda安装程序。
+
+对于PXE网络安装，客户机通过支持PXE的网卡，向网络发送请求DHCP信息的广播，请求IP地址等信息。DHCP服务器给客户机提供一个IP地址和其他网络信息如域名服务器、ftp服务器（它提供启动安装程序所必须的文件）的IP地址或主机名，以及服务器上文件的位置。
+
+>![](./public_sys-resources/icon-note.gif) **说明：**   
+>此处不详细讨论tftp、DHCP、http等服务器配置，相关详细配置请参考“[全自动化安装指导](./使用kickstart自动化安装.html#全自动化安装指导)”。  
+
+## 通过qcow2镜像安装
+
+本节介绍如何使用或者制作qcow2镜像，并介绍相应的操作步骤，指导用户进行安装。
+
+### 制作qcow2镜像
+
+1.  安装qemu-img软件包。
+
+    ```
+    # dnf install -y qemu-img
+    ```
+
+2.  使用qemu-img工具的create命令，创建镜像文件，命令格式为：
+
+    ```
+    $ qemu-img create -f  -o   
+    ```
+
+    其中，各参数含义如下：
+
+    -   _imgFormat_  ：镜像格式，取值为raw, qcow2等。
+    -   _fileOption_  ：文件选项，用于设置镜像文件的特性，如指定后端镜像文件，压缩，加密等特性。
+    -   _fileName_  ：文件名称。
+    -   _diskSize_  ：磁盘大小，用于指定块磁盘设备的大小，支持的单位有K、M、G、T，分别代表KiB、MiB、GiB、TiB。
+
+    例如，创建一个磁盘设备大小为32GB、格式为qcow2的镜像文件openEuler-imge.qcow2，命令和回显如下：
+
+    ```
+    $ qemu-img create -f qcow2 openEuler-image.qcow2 32G
+    Formatting 'openEuler-image.qcow2', fmt=qcow2 size=34359738368 cluster_size=65536 lazy_refcounts=off refcount_bits=16
+    ```
+
+
+### 启动安装
+
+根据以下步骤启动安装程序：
+
+1.  准备qcow2镜像文件。
+2.  准备虚拟机网络。
+3.  准备UEFI引导工具集EDK II。
+4.  准备虚拟机XML配置文件。
+5.  创建虚拟机。
+6.  启动虚拟机。
+
+各步骤详细的操作请参考《[openEuler 20.03 LTS 虚拟化用户指南](./../Virtualization/virtualization.html)》。
+
+## 通过私有镜像安装
+
+本节介绍如何使用或者制作私有镜像，并介绍相应的操作步骤，指导用户进行安装。
+
+### 制作私有镜像
+
+制作私有镜像的方法请参见[《镜像服务用户指南》](https://support.huaweicloud.com/usermanual-ims/zh-cn_topic_0013901628.html)。
+
+### 启动安装
+
+华为公有云的x86虚拟化平台的启动请参见[ 弹性云服务器 ECS的用户指南](https://support.huaweicloud.com/wtsnew-ecs/index.html)。
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/Advanced_User_Configuration.png b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/Advanced_User_Configuration.png
new file mode 100644
index 0000000000000000000000000000000000000000..63f6c87eec6758e97c976c07171343d28569d011
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/Advanced_User_Configuration.png differ
diff --git "a/content/zh/docs/Quickstart/figures/\345\205\211\351\251\261\345\233\276\346\240\207.png" b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/CD-ROM_drive_icon.png
similarity index 100%
rename from "content/zh/docs/Quickstart/figures/\345\205\211\351\251\261\345\233\276\346\240\207.png"
rename to docs/zh/docs/20.03_LTS/docs/Quickstart/figures/CD-ROM_drive_icon.png
diff --git "a/content/zh/docs/Quickstart/figures/\351\225\234\345\203\217\345\257\271\350\257\235\346\241\206.png" b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/Image_dialog_box.png
similarity index 100%
rename from "content/zh/docs/Quickstart/figures/\351\225\234\345\203\217\345\257\271\350\257\235\346\241\206.png"
rename to docs/zh/docs/20.03_LTS/docs/Quickstart/figures/Image_dialog_box.png
diff --git a/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/Installation_Overview.png b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/Installation_Overview.png
new file mode 100644
index 0000000000000000000000000000000000000000..e30f776c50915918005be529363b2e15de9fe432
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/Installation_Overview.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/Installation_wizard.png b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/Installation_wizard.png
new file mode 100644
index 0000000000000000000000000000000000000000..c4a6f41ef2ba73946e78d6cd422193b87edd90c8
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/Installation_wizard.png differ
diff --git "a/content/zh/docs/Quickstart/figures/\350\256\276\347\275\256\347\263\273\347\273\237\345\220\257\345\212\250\351\241\271.png" b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/Setting_the_System_Boot_Option.png
similarity index 100%
rename from "content/zh/docs/Quickstart/figures/\350\256\276\347\275\256\347\263\273\347\273\237\345\220\257\345\212\250\351\241\271.png"
rename to docs/zh/docs/20.03_LTS/docs/Quickstart/figures/Setting_the_System_Boot_Option.png
diff --git a/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/Target_installation_position.png b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/Target_installation_position.png
new file mode 100644
index 0000000000000000000000000000000000000000..af0980e3a8e2d2510d00b6012e4aef70936b584e
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/Target_installation_position.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/chooselanguage.png b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/chooselanguage.png
new file mode 100644
index 0000000000000000000000000000000000000000..44e736d20c86098b0e69e0a7027103871d19032b
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/chooselanguage.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/choosesoftware.png b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/choosesoftware.png
new file mode 100644
index 0000000000000000000000000000000000000000..8330bf28b910ab88420e0ba1fb43a49b21a3374f
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/choosesoftware.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/completeinstall.png b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/completeinstall.png
new file mode 100644
index 0000000000000000000000000000000000000000..91d38b80cf2310a7427788feb089da8d106b97b5
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/completeinstall.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/createuser.png b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/createuser.png
new file mode 100644
index 0000000000000000000000000000000000000000..3650c7ed70883500b636ae2acecee78d5724f7d8
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/createuser.png differ
diff --git "a/content/zh/docs/Quickstart/figures/\351\207\215\345\220\257\345\233\276\346\240\207.png" b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/restarticon.png
similarity index 100%
rename from "content/zh/docs/Quickstart/figures/\351\207\215\345\220\257\345\233\276\346\240\207.png"
rename to docs/zh/docs/20.03_LTS/docs/Quickstart/figures/restarticon.png
diff --git a/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/rootpassword.png b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/rootpassword.png
new file mode 100644
index 0000000000000000000000000000000000000000..131863338be6ea5925cadd75483c08c34ec9856c
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/rootpassword.png differ
diff --git a/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/startinstall.png b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/startinstall.png
new file mode 100644
index 0000000000000000000000000000000000000000..227ec876dc1b0d6cbe6991c1bce1fc0837a344c0
Binary files /dev/null and b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/startinstall.png differ
diff --git a/content/zh/docs/Quickstart/figures/zh-cn_image_0229420473.png b/docs/zh/docs/20.03_LTS/docs/Quickstart/figures/zh-cn_image_0229420473.png
similarity index 100%
rename from content/zh/docs/Quickstart/figures/zh-cn_image_0229420473.png
rename to docs/zh/docs/20.03_LTS/docs/Quickstart/figures/zh-cn_image_0229420473.png
diff --git a/content/zh/docs/Quickstart/public_sys-resources/icon-caution.gif b/docs/zh/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-caution.gif
similarity index 100%
rename from content/zh/docs/Quickstart/public_sys-resources/icon-caution.gif
rename to docs/zh/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-caution.gif
diff --git a/content/zh/docs/Quickstart/public_sys-resources/icon-danger.gif b/docs/zh/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-danger.gif
similarity index 100%
rename from content/zh/docs/Quickstart/public_sys-resources/icon-danger.gif
rename to docs/zh/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-danger.gif
diff --git a/content/zh/docs/Quickstart/public_sys-resources/icon-note.gif b/docs/zh/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-note.gif
similarity index 100%
rename from content/zh/docs/Quickstart/public_sys-resources/icon-note.gif
rename to docs/zh/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-note.gif
diff --git a/content/zh/docs/Quickstart/public_sys-resources/icon-notice.gif b/docs/zh/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-notice.gif
similarity index 100%
rename from content/zh/docs/Quickstart/public_sys-resources/icon-notice.gif
rename to docs/zh/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-notice.gif
diff --git a/content/zh/docs/Quickstart/public_sys-resources/icon-tip.gif b/docs/zh/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-tip.gif
similarity index 100%
rename from content/zh/docs/Quickstart/public_sys-resources/icon-tip.gif
rename to docs/zh/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-tip.gif
diff --git a/content/zh/docs/Quickstart/public_sys-resources/icon-warning.gif b/docs/zh/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-warning.gif
similarity index 100%
rename from content/zh/docs/Quickstart/public_sys-resources/icon-warning.gif
rename to docs/zh/docs/20.03_LTS/docs/Quickstart/public_sys-resources/icon-warning.gif
diff --git a/content/zh/docs/Quickstart/quick-start.md b/docs/zh/docs/20.03_LTS/docs/Quickstart/quick-start.md
similarity index 73%
rename from content/zh/docs/Quickstart/quick-start.md
rename to docs/zh/docs/20.03_LTS/docs/Quickstart/quick-start.md
index af4f8156b546009cd0357043d216f93d063d4a5b..a3f7415b597e1e5c35287e5b135a09051f293402 100644
--- a/content/zh/docs/Quickstart/quick-start.md
+++ b/docs/zh/docs/20.03_LTS/docs/Quickstart/quick-start.md
@@ -1,6 +1,6 @@
 # 快速入门
 
-本文档以TaiShan 200服务器上安装openEuler 20.09 beta为例，旨在指导用户快速地安装和使用openEuler操作系统，更详细的安装要求和安装方法请参考《[openEuler 20.09 beta 安装指南](../Installation/installation.html)》。
+本文档以TaiShan 200服务器上安装openEuler 20.03 LTS为例，旨在指导用户快速地安装和使用openEuler操作系统，更详细的安装要求和安装方法请参考《[openEuler 20.03 LTS 安装指南](https://openeuler.org/zh/docs/20.03_LTS/docs/Installation/installation.html)》。
 
 
 - [快速入门](#快速入门)
@@ -87,7 +87,7 @@
     
     
硬盘

     
-    
为了获得更好的应用体验，建议不小于120GB）

+    
为了获得更好的应用体验，建议不小于120GB

     
     
支持IDE、SATA、SAS等接口的硬盘。

     
@@ -100,13 +100,10 @@
 
 请按以下步骤获取openEuler的发布包和校验文件：
 
-> ![](public_sys-resources/icon-note.gif) **说明：**   
-> AArch64架构的发布包支持UEFI模式，x86\_64架构的发布包支持UEFI模式和Legacy模式。
-
 1.  登录[openEuler社区](https://openeuler.org)网站。
 2.  单击“下载”。
 3.  单击“获取ISO：”后面的“Link”，显示版本列表。
-4.  单击“openEuler-20.09-beta”，进入openEuler 20.09 beta版本下载列表。
+4.  单击“openEuler-20.03-LTS”，进入openEuler 20.03 LTS版本下载列表。
 5.  单击“ISO”，进入ISO下载列表。
     -   aarch64：AArch64架构的ISO。
     -   x86\_64：x86\_64架构的ISO。
@@ -115,13 +112,13 @@
 6.  根据实际待安装环境的架构选择需要下载的openEuler的发布包和校验文件。
     -   若为AArch64架构。
         1.  单击“aarch64”。
-        2.  单击“openEuler-20.09-beta-aarch64-dvd.iso”，将openEuler发布包下载到本地。
-        3.  单击“openEuler-20.09-beta-aarch64-dvd.iso.sha256sum”，将openEuler校验文件下载到本地。
+        2.  单击“openEuler-20.03-LTS-aarch64-dvd.iso”，将openEuler发布包下载到本地。
+        3.  单击“openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum”，将openEuler校验文件下载到本地。
 
     -   若为x86\_64架构。
         1.  单击“x86\_64”。
-        2.  单击“openEuler-20.09-beta-x86\_64-dvd.iso”，将openEuler发布包下载到本地。
-        3.  单击“openEuler-20.09-beta-x86\_64-dvd.iso.sha256sum”，将openEuler校验文件下载到本地。
+        2.  单击“openEuler-20.03-LTS-x86\_64-dvd.iso”，将openEuler发布包下载到本地。
+        3.  单击“openEuler-20.03-LTS-x86\_64-dvd.iso.sha256sum”，将openEuler校验文件下载到本地。
 
 
 
@@ -132,13 +129,13 @@
 1.  获取校验文件中的校验值。执行命令如下：
 
     ```
-    $ cat openEuler-20.09-beta-aarch64-dvd.iso.sha256sum 
+    $ cat openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum 
     ```
 
 2.  计算文件的sha256校验值。执行命令如下：
 
     ```
-    $ sha256sum openEuler-20.09-beta-aarch64-dvd.iso
+    $ sha256sum openEuler-20.03-LTS-aarch64-dvd.iso
     ```
 
     命令执行完成后，输出校验值。
@@ -156,7 +153,7 @@
     将“引导介质有效期”和“引导介质”分别设置为“单次有效”和“光驱”，并单击“保存”以保存配置。如[图1](#fig1011938131018)所示。
 
     **图 1**  设置系统启动项  
-    ![](figures/设置系统启动项.png "设置系统启动项")
+    ![](./figures/Setting_the_System_Boot_Option.png)
 
 3.  在上方标题栏中，选择“远程控制”，在左侧导航树中选择“远程控制”，显示“远程控制”界面。
 
@@ -165,30 +162,30 @@
 4.  在虚拟界面工具栏中，单击虚拟光驱工具如下图所示。
 
     **图 2**  光驱图标  
-    ![](figures/光驱图标.png "光驱图标")
+    ![](./figures/CD-ROM_drive_icon.png)
 
     弹出镜像对话框，如下图所示。
 
     **图 3**  镜像对话框  
-    ![](figures/镜像对话框.png "镜像对话框")
+    ![](./figures/Image_dialog_box.png)
 
 5.  在镜像对话框中，选择“镜像文件”， 并单击“浏览”。弹出“打开”对话框。
 6.  选择镜像文件，单击“打开”。然后在镜像对话框中，单击“连接”。当“连接”显示为“断开”后，表示虚拟光驱已连接到服务器。
 7.  在工具栏中，单击重启工具重启设备，如下图所示。
 
     **图 4**  重启图标  
-    ![](figures/重启图标.png "重启图标")
+    ![](./figures/restarticon.png)
 
 8.  设备重启后进入到openEuler操作系统安装引导界面，如[图5](#fig1648754873314)所示。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
-    >-   如果60秒内未按任何键，系统将从默认选项“Test this media & install openEuler 20.09-beta”自动进入安装界面。  
-    >-   安装物理机时，如果使用键盘上下键无法选择启动选项，按“Enter”键无响应，可以单击BMC界面上的鼠标控制图标“![](figures/zh-cn_image_0229420473.png)”，设置“键鼠复位”。  
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
+    >-   如果60秒内未按任何键，系统将从默认选项“Test this media & install openEuler 20.03 LTS”自动进入安装界面。  
+    >-   安装物理机时，如果使用键盘上下键无法选择启动选项，按“Enter”键无响应，可以单击BMC界面上的鼠标控制图标“![](./figures/zh-cn_image_0229420473.png)”，设置“键鼠复位”。  
 
     **图 5**  安装引导界面  
-    
+    ![](./figures/Installation_wizard.png)
 
-9.  在安装引导界面，按“Enter”，进入默认选项“Test this media & install openEuler 20.09-beta”的图形化安装界面。
+9.  在安装引导界面，按“Enter”，进入默认选项“Test this media & install openEuler 20.03 LTS”的图形化安装界面。
 
 ## 安装
 
@@ -197,111 +194,114 @@
 1.  设置安装语言，默认为英语，用户可根据实际情况进行调整，如[图6](#fig874344811484)所示，选择“中文”。
 
     **图 6**  选择语言  
-    
+    ![](./figures/chooselanguage.png)
 
-2. 在安装概览界面，根据实际情况设置各配置项。
+2.  在安装概览界面，根据实际情况设置各配置项。
 
     -   配置项有告警符号的，表示用户必须完成该选项配置后，告警符号消失，才能进行下一步操作。
     -   配置项无告警符号的，表示该配置项已有默认配置。
     -   所有配置项均无告警符号时用户才能单击“开始安装”进行系统安装。
 
     **图 7**  安装概览  
-    
+    ![](./figures/Installation_Overview.png)
 
     1.  选择“软件选择”，设置“软件选择”配置项。
 
         用户需要根据实际的业务需求，在左侧选择一个“最小安装”，在右侧选择安装环境的附加选项，如[图8](#fig1133717611109)所示。
 
         **图 8**  软件选择  
-        
+        ![](./figures/choosesoftware.png)
 
-        >![](public_sys-resources/icon-note.gif) **说明：**   
+        >![](./public_sys-resources/icon-note.gif) **说明：**   
         >-   在最小安装的环境下，并非安装源中所有的包都会安装。如果用户需要使用的包未安装，可将安装源挂载到本地制作repo源，通过DNF工具单独安装。  
         >-   选择“虚拟化主机”时会默认安装虚拟化组件qemu、libvirt、edk2，且可在附件选项处选择是否安装ovs等组件。  
 
         设置完成后，请单击左上角“完成”返回“安装概览”页面。
 
-    2. 选择“安装目的地”，设置“安装目的地”配置项。
+    2.  选择“安装位置”，设置“安装位置”配置项。
 
-        在安装位置页面中，您可以选择计算机中的本地可用存储设备。
+        在安装位置页面中，您可以选择计算机中的本地可用存储设备，也可以通过单击“添加磁盘”，添加指定的附加设备或者网络设备。您还需要进行存储配置以便对系统分区。您可以手动配置分区，也可以选择让安装程序自动分区。如果是在未使用过的存储设备中执行全新安装，或者不需要保留该存储设备中任何数据，建议选择“自动”进行自动分区。如[图9](#fig153381468101)所示。
 
-        >![](public_sys-resources/icon-notice.gif) **须知：**   
+        >![](./public_sys-resources/icon-notice.gif) **须知：**   
         >在选择您需要安装的设备时，建议不要选择NVMe SSD存储介质作为操作系统的安装磁盘。  
-        
-        您还需要进行存储配置以便对系统分区。您可以手动配置分区，也可以选择让安装程序自动分区。如果是在未使用过的存储设备中执行全新安装，或者不需要保留该存储设备中任何数据，建议选择“自动”进行自动分区。如[图9](#fig153381468101)所示。
-        
-        若您需要对数据进行加密，若您选择“自动”进行自动分区时，则可以在“安装目标位置”界面选择“加密我的数据”；若您选择“自定义”进行手动分区时，则可以在“手动分区”界面中单击需要加密的挂载点并在“设备类型”区域中选择“加密”。然后单击左上角“完成”，设置磁盘加密口令。磁盘加密口令需要符合密码复杂度，具体请参考[密码复杂度](#密码复杂度)。
 
         **图 9**  安装目标位置  
-        
+        ![](./figures/Target_installation_position.png)
 
-        >![](public_sys-resources/icon-note.gif) **说明：**   
+        >![](./public_sys-resources/icon-note.gif) **说明：**   
         >-   在进行分区时，出于系统性能和安全的考虑，建议您划分如下单独分区：/boot、/var、/var/log 、/var/log/audit、/home、/tmp。  
         >-   系统如果配置了swap分区，当系统的物理内存不够用时，会使用swap分区。虽然 swap分区可以增大物理内存大小的限制，但是如果由于内存不足使用到swap分区，会增加系统的响应时间，性能变差。因此在物理内存充足或者性能敏感的系统中，不建议配置swap分区。  
         >-   如果需要拆分逻辑卷组则需要选择“自定义”进行手动分区，并在“手动分区”界面单击“卷组”区域中的“修改”按钮重新配置卷组。  
 
         设置完成后，请单击左上角“完成”返回“安装概览”页面。
 
-    3. 选择“根密码”，设置“根密码”配置项。
-
-        在“ROOT密码”页面中，如[图10](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig1323165793018)所示，根据[密码复杂度](#密码复杂度)输入密码并再次输入密码进行确认。
-
-        >![](public_sys-resources/icon-note.gif) **说明：**   
-        >
-        >- root帐户是用来执行关键系统管理任务，不建议您在日常工作及系统访问时使用root帐户。
-        >
-        >- 在“ROOT密码”界面若选择“锁定root帐户”则root帐户将禁用。  
+    3.  设置其他配置项，其他配置项可以使用默认配置。
 
-        **密码复杂度** 
+3.  单击“开始安装”进行系统安装，如[图10](#fig1717019357392)所示。
 
-        用户设置的root用户密码或新创建用户的密码均需要满足密码复杂度要求，否则会导致密码设置或用户创建失败。设置密码的复杂度的要求如下：
+    **图 10**  开始安装  
+    ![](./figures/startinstall.png)
 
-        1. 口令长度至少8个字符。
+4.  设置root密码。
 
-        2. 口令至少包含大写字母、小写字母、数字和特殊字符中的任意3种。
+    单击“root密码”，弹出设置密码界面如[图11](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig1323165793018)所示，输入密码并再次输入密码进行确认。
 
-        3. 口令不能和账号一样。
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
+    >root密码需要在安装软件包的同时进行配置，如果不配置该密码则无法完成安装。root账户是用来执行关键系统管理任务，不建议您在日常工作及系统访问时使用root账户。  
 
-        4. 口令不能使用字典词汇。
+    用户设置的root密码需要满足如下密码复杂度要求，否则会导致密码设置或用户创建失败。
 
-            >![](public_sys-resources/icon-note.gif) **说明：**   
-            > 在已装好的openEuler环境中，可以通过`cracklib-unpacker /usr/share/cracklib/pw_dict > dictionary.txt`命令导出字典库文件dictionary.txt，用户可以查询密码是否在该字典中。
+    -   口令长度至少8个字符。
+    -   口令至少包含大写字母、小写字母、数字和特殊字符中的任意3种。
+    -   口令不能和账号一样。
+    -   口令不能使用字典词汇。
+        -   查询字典
 
-        **图 10**  root密码  
-        ![](figures/root密码.png "root密码")
+            在已装好的openEuler环境中，可以通过如下命令导出字典库文件dictionary.txt，用户可以查询密码是否在该字典中。
 
-        设置完成后，单击左上角的“完成”返回“安装概览”页面。
+            ```
+            cracklib-unpacker /usr/share/cracklib/pw_dict > dictionary.txt
+            ```
 
-    4. 选择“创建用户”，设置“创建用户”配置项。
+        -   修改字典
+            -   修改上面导出的字典文件，执行如下命令更新系统字典库。
 
-        在创建用户的界面如[图11](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig1237715313319)所示。输入用户名，并设置密码，其中密码复杂度要求与root密码复杂度要求一致。另外您还可以通过“高级”选项设置用户主目录、用户组等，如[图12](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig128716531312)所示。
+                ```
+                create-cracklib-dict dictionary.txt
+                ```
 
-        **图 11**  创建用户  
-        
+            -   在原字典库基础上新增其他字典内容custom.txt。
 
-        **图 12**  高级用户配置  
-        ![](figures/高级用户配置.png "高级用户配置")
+                ```
+                create-cracklib-dict dictionary.txt custom.txt
+                ```
+    
+    **图 11**  root密码  
+    ![](./figures/rootpassword.png)
+    
+5.  创建用户。
 
-        完成设置后，单击左上角的“完成”返回“安装概览”页面。
+    单击“创建用户”，弹出创建用户的界面如[图12](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig1237715313319)所示。输入用户名，并设置密码，其中密码复杂度要求与root密码复杂度要求一致。另外您还可以通过“高级”选项设置用户主目录、用户组等，如[图13](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig128716531312)所示。
 
-    5. 设置其他配置项，其他配置项可以使用默认配置。
+    **图 12**  创建用户  
+    ![](./figures/createuser.png)
 
-3.  单击“开始安装”进行系统安装，如[图13](#fig1717019357392)所示。
+    **图 13**  高级用户配置  
+    ![](./figures/Advanced_User_Configuration.png)
 
-    **图 13**  开始安装  
-    
+    完成设置后，单击左上角的“完成”返回安装过程界面。
 
 6.  安装完成后重启系统。
 
     openEuler完成安装，如[图14](#zh-cn_topic_0186390267_zh-cn_topic_0122145917_fig1429512116338)所示。单击“重启”后，系统将重新启动。
 
     **图 14**  完成安装  
-    
+    ![](./figures/completeinstall.png)
 
 
 ## 查看系统信息
 
-系统安装完成并重启后直接进入系统命令行登录界面，输入安装过程中设置的用户和密码，进入openEuler操作系统，查看如下系统信息。若需要进行系统管理和配置操作，请参考《[openEuler 20.09 beta 管理员指南](../Administration/administration.html)》。
+系统安装完成并重启后直接进入系统命令行登录界面，输入安装过程中设置的用户和密码，进入openEuler操作系统，查看如下系统信息。若需要进行系统管理和配置操作，请参考《[openEuler 20.03 LTS 管理员指南](https://openeuler.org/zh/docs/20.03_LTS/docs/Administration/administration.html)》。
 
 -   查看系统信息，命令如下：
 
@@ -312,12 +312,12 @@
     例如，命令和输出如下：
 
     ```
-    $ cat /etc/os-release
+    # cat /etc/os-release
     NAME="openEuler"
-    VERSION="20.09"
+    VERSION="20.03 (LTS)"
     ID="openEuler"
-    VERSION_ID="20.09"
-    PRETTY_NAME="openEuler 20.09"
+    VERSION_ID="20.03"
+    PRETTY_NAME="openEuler 20.03 (LTS)"
     ANSI_COLOR="0;31"
     ```
 
diff --git "a/content/zh/docs/Releasenotes/CVE\346\274\217\346\264\236.md" "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/CVE\346\274\217\346\264\236.md"
similarity index 100%
rename from "content/zh/docs/Releasenotes/CVE\346\274\217\346\264\236.md"
rename to "docs/zh/docs/20.03_LTS/docs/Releasenotes/CVE\346\274\217\346\264\236.md"
diff --git a/content/zh/docs/Releasenotes/public_sys-resources/icon-caution.gif b/docs/zh/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-caution.gif
similarity index 100%
rename from content/zh/docs/Releasenotes/public_sys-resources/icon-caution.gif
rename to docs/zh/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-caution.gif
diff --git a/content/zh/docs/Releasenotes/public_sys-resources/icon-danger.gif b/docs/zh/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-danger.gif
similarity index 100%
rename from content/zh/docs/Releasenotes/public_sys-resources/icon-danger.gif
rename to docs/zh/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-danger.gif
diff --git a/content/zh/docs/Releasenotes/public_sys-resources/icon-note.gif b/docs/zh/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-note.gif
similarity index 100%
rename from content/zh/docs/Releasenotes/public_sys-resources/icon-note.gif
rename to docs/zh/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-note.gif
diff --git a/content/zh/docs/Releasenotes/public_sys-resources/icon-notice.gif b/docs/zh/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-notice.gif
similarity index 100%
rename from content/zh/docs/Releasenotes/public_sys-resources/icon-notice.gif
rename to docs/zh/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-notice.gif
diff --git a/content/zh/docs/Releasenotes/public_sys-resources/icon-tip.gif b/docs/zh/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-tip.gif
similarity index 100%
rename from content/zh/docs/Releasenotes/public_sys-resources/icon-tip.gif
rename to docs/zh/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-tip.gif
diff --git a/content/zh/docs/Releasenotes/public_sys-resources/icon-warning.gif b/docs/zh/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-warning.gif
similarity index 100%
rename from content/zh/docs/Releasenotes/public_sys-resources/icon-warning.gif
rename to docs/zh/docs/20.03_LTS/docs/Releasenotes/public_sys-resources/icon-warning.gif
diff --git a/docs/zh/docs/20.03_LTS/docs/Releasenotes/release_notes.md b/docs/zh/docs/20.03_LTS/docs/Releasenotes/release_notes.md
new file mode 100644
index 0000000000000000000000000000000000000000..6bae599cc4903bdc759f4e679f5a875d77b5e9ef
--- /dev/null
+++ b/docs/zh/docs/20.03_LTS/docs/Releasenotes/release_notes.md
@@ -0,0 +1 @@
+本文是 openEuler 20.03 LTS 版本的发行说明。
\ No newline at end of file
diff --git a/docs/zh/docs/20.03_LTS/docs/Releasenotes/zh-cn_bookmap_0225720059.md b/docs/zh/docs/20.03_LTS/docs/Releasenotes/zh-cn_bookmap_0225720059.md
new file mode 100644
index 0000000000000000000000000000000000000000..5d775e30182a7156ece2c9bb4a4e0f4afa6fe288
--- /dev/null
+++ b/docs/zh/docs/20.03_LTS/docs/Releasenotes/zh-cn_bookmap_0225720059.md
@@ -0,0 +1,14 @@
+# 版本发行说明
+
+-   [法律声明](./法律声明.md)
+-   [用户须知](./用户须知.md)
+-   [简介](./简介.md)
+-   [系统安装](./系统安装.md)
+-   [关键特性](./关键特性.md)
+-   [已知问题](./已知问题.md)
+-   [已修复问题](./已修复问题.md)
+-   [CVE漏洞](./CVE漏洞.md)
+-   [源代码](./源代码.md)
+-   [参与贡献](./参与贡献.md)
+-   [致谢](./致谢.md)
+
diff --git "a/docs/zh/docs/20.03_LTS/docs/Releasenotes/\345\205\263\351\224\256\347\211\271\346\200\247.md" "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/\345\205\263\351\224\256\347\211\271\346\200\247.md"
new file mode 100644
index 0000000000000000000000000000000000000000..357859efa19f59c4ec9846ee92cbca9694676a3d
--- /dev/null
+++ "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/\345\205\263\351\224\256\347\211\271\346\200\247.md"
@@ -0,0 +1,30 @@
+# 关键特性
+
+-   iSula轻量级容器解决方案，统一IoT，边缘和云计算容器解决方案
+    -   缩短三级调用链，百容器内存资源占用相比Docker引擎显著下降
+    -   支持CRI/OCI标准开源接口，灵活对接runc、kata等多种OCI运行时
+    -   通过Smart-loading智能镜像下载技术，显著提升镜像下载速度
+    -   安全容器：虚拟化技术和容器技术的有机结合，安全容器具有更好的隔离性
+    -   系统容器：支持本地文件系统启动，可实现快速部署。支持部署systemd，提升user namespace隔离性
+
+-   Kunpeng加速引擎（KAE），支持加解密加速
+    -   摘要算法SM3，支持异步模型
+    -   对称加密算法SM4，支持异步模型，支持CTR/XTS/CBC模式
+    -   对称加密算法AES，支持异步模型，支持ECB/CTR/XTS/CBC模式
+    -   非对称算法RSA，支持异步模型，支持Key Sizes 1024/2048/3072/4096
+    -   密钥协商算法DH，支持异步模型，支持Key Sizes 768/1024/1536/2048/3072/4096
+
+
+-   A-Tune智能系统性能优化引擎，推理出业务特征，配置最佳的系统参数合，使业务处于最优运行状态。
+-   增强glibc/zlib/gzip性能，充分利用AArch64的neon指令集，提升基础库性能。
+-   内核特性增强
+    -   支持ARM64内核热补丁
+    -   Numa Aware Qspinlock：减少跨NUMA节点的Cache/总线冲突
+    -   通过优化 IOVA 页表查找和页表释放算法，提升 I/O MMU 子系统性能
+    -   根据 ARM64 指令以及流水线特点，优化 CRC32 及 checksum 实现，大幅提升数据校验性能
+    -   支持 ARM v8.4 MPAM（Memory System Resource Partitioning and Monitoring）
+-   虚拟化特性增强
+    -   中断虚拟化优化：IRQfd路径注入中断优化，大幅提升高性能直通设备（网卡、SSD磁盘等）性能
+    -   内存虚拟化优化：借助鲲鹏硬件特性，提升虚拟机启动内存加载速度
+    -   存储虚拟化优化：iSCSI模块kworker的NUMA亲和性自绑定优化，提升IPSAN磁盘的IO性能
+
diff --git "a/content/zh/docs/Releasenotes/\345\217\202\344\270\216\350\264\241\347\214\256.md" "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/\345\217\202\344\270\216\350\264\241\347\214\256.md"
similarity index 100%
rename from "content/zh/docs/Releasenotes/\345\217\202\344\270\216\350\264\241\347\214\256.md"
rename to "docs/zh/docs/20.03_LTS/docs/Releasenotes/\345\217\202\344\270\216\350\264\241\347\214\256.md"
diff --git "a/docs/zh/docs/20.03_LTS/docs/Releasenotes/\345\267\262\344\277\256\345\244\215\351\227\256\351\242\230.md" "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/\345\267\262\344\277\256\345\244\215\351\227\256\351\242\230.md"
new file mode 100644
index 0000000000000000000000000000000000000000..005aa7bea6fefb62e02f84f743d8e8a88ec07f91
--- /dev/null
+++ "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/\345\267\262\344\277\256\345\244\215\351\227\256\351\242\230.md"
@@ -0,0 +1,75 @@
+# 已修复问题
+
+完整问题清单请参见[完整问题清单](https://gitee.com/organizations/src-openeuler/issues)。
+
+完整的内核提交记录请参见[提交记录](https://gitee.com/openeuler/kernel/commits/openEuler-1.0-LTS)。
+
+已修复问题请参见[表1](#table249714911433)。
+
+**表 1**  修复问题列表
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
ISSUE

+
问题描述

+
I1BJTF

+
【kernel bug】arm机器上lscpu命令无法显示cpu主频，cpu cache错误

+
I1BWPD

+
使用isula/crictl pull镜像失败

+
I1BV56

+
delete redundant gpg sig file for shadow-4.6

+
I1BV38

+
unbuffer命令不可用

+
I1BA9B

+
arping -w参数失效

+
I1AV3S

+
跑最新LTP中的pty03用例，必现oops

+
I1AZ1I

+
启动500个定时任务，4~5分钟后，任务处理不过来，系统会卡死

+
I1AH2C

+
启动kata容器失败抓到warning信息不足定位，需要打印更多报错

+
I1AGXO

+
kata-runtime远程模式下isula rm -f没有执行kill导致残留

+
I1AF39

+
ext4文件系统上触发open时发现softlockup

+
I1ADUD

+
kubectl创建pod导致isulad崩溃

+

+
diff --git "a/docs/zh/docs/20.03_LTS/docs/Releasenotes/\345\267\262\347\237\245\351\227\256\351\242\230.md" "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/\345\267\262\347\237\245\351\227\256\351\242\230.md"
new file mode 100644
index 0000000000000000000000000000000000000000..4050f4ea80bd390900fffd4fbab03091f6cc05cf
--- /dev/null
+++ "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/\345\267\262\347\237\245\351\227\256\351\242\230.md"
@@ -0,0 +1,21 @@
+# 已知问题
+
+-   内核FIPS启动模式还未经过完整认证，FIPS启动可能存在问题。[I17Z18](https://gitee.com/src-openeuler/crypto-policies/issues/I17Z18?from=project-issue)
+-   使用libvirt启动glusterfs虚拟机，每次会有300字节的内存泄漏。讨论详情请参见[社区讨论](https://github.com/gluster/glusterfs/issues/818)。[I185CH](https://gitee.com/src-openeuler/glusterfs/issues/I185CH?from=project-issue)
+-   使用libvirt接口连续执行磁盘热插拔操作，概率性出现热拔接口返回成功，但磁盘未真正拔除，也不能再次热插和热拔该磁盘。关闭虚拟机后再启动可恢复正常。[I1C72L](https://gitee.com/src-openeuler/qemu/issues/I1C72L?from=project-issue)
+-   使用x86\_64虚拟机安装时，极小概率可能出现未知安装异常，请再次安装恢复。[I1C8HS](https://gitee.com/src-openeuler/anaconda/issues/I1C8HS?from=project-issue)
+-   CVE-2012-0039在本地应用程序通过调用g\_str\_hash函数，调用该接口的应用会持续消耗CPU，导致拒绝服务攻击，社区已经明确不解决。
+-   CVE-2015-9541通过构造异常的SVG文档进行指数级XML实体扩展攻击，当Qt尝试解析SVG时，可能会发生内存不足的情况。讨论详情请参见[社区讨论](https://codereview.qt-project.org/c/qt/qtbase/+/293909)。
+-   部分开源包编译前需要提前安装gdb，gcc，make等基础软件，否则会由于缺少依赖而编译失败。
+-   AArch64和x86\_64在char类型上定义不一致，导致coreutils，augeas，diffutils自检报错，请增加--fsigned-char编译选项解决。
+-   针对20.03LTS版本，如果用户从mysql-8.0.17-3.oe1版本升级到较新版本，使用rpm -Uvh xxx（其中XXX指具体的版本，例如mysql-8.0.21-1.oe1.aarch64.rpm）命令，升级后功能不可用，可以通过以下两种方式进行版本升级（以mysql-8.0.17-3.oe1升级到mysql-8.0.21-1.oe1举例）：  
+    - 方法1，执行如下升级命令实现：  
+        ``` 
+        # rpm -Uvh mysql-8.0.21-1.oe1.aarch64.rpm --noscripts 
+        ```
+    - 方法2，先卸载旧版本的mysql，再安装新版本的mysql，命令如下：
+        ```
+        # rpm -e mysql-8.0.17-3.oe1      
+        # rpm -ivh mysql-8.0.21-1.oe1.aarch64.rpm
+        ```
+
diff --git "a/content/zh/docs/Releasenotes/\346\263\225\345\276\213\345\243\260\346\230\216.md" "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/\346\263\225\345\276\213\345\243\260\346\230\216.md"
similarity index 64%
rename from "content/zh/docs/Releasenotes/\346\263\225\345\276\213\345\243\260\346\230\216.md"
rename to "docs/zh/docs/20.03_LTS/docs/Releasenotes/\346\263\225\345\276\213\345\243\260\346\230\216.md"
index 9769a3f5cfcd23d6e98b030f9b933935330b23b4..333a56434fd39d9fe8ea65edf8781340dd607470 100644
--- "a/content/zh/docs/Releasenotes/\346\263\225\345\276\213\345\243\260\346\230\216.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/\346\263\225\345\276\213\345\243\260\346\230\216.md"
@@ -1,14 +1,14 @@
 # 法律声明
 
-**版权所有 © 2020 openEuler社区。**
+**版权所有 © 2020 华为技术有限公司。**
 
 您对“本文档”的复制、使用、修改及分发受知识共享\(Creative Commons\)署名—相同方式共享4.0国际公共许可协议\(以下简称“CC BY-SA 4.0”\)的约束。为了方便用户理解，您可以通过访问[https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)  了解CC BY-SA 4.0的概要 \(但不是替代\)。CC BY-SA 4.0的完整协议内容您可以访问如下网址获取：[https://creativecommons.org/licenses/by-sa/4.0/legalcode](https://creativecommons.org/licenses/by-sa/4.0/legalcode)。
 
 **商标声明**
 
-openEuler为openEuler社区的商标。本文档提及的其他所有商标或注册商标，由各自的所有人拥有。
+openEuler为华为技术有限公司的商标。本文档提及的其他所有商标或注册商标，由各自的所有人拥有。
 
 **免责声明**
 
-本文档仅作为使用指导，除非适用法强制规定或者双方有明确书面约定, openEuler社区对本文档中的所有陈述、信息和建议不做任何明示或默示的声明或保证，包括但不限于不侵权，时效性或满足特定目的的担保。
+本文档仅作为使用指导，除非适用法强制规定或者双方有明确书面约定, 华为技术有限公司对本文档中的所有陈述、信息和建议不做任何明示或默示的声明或保证，包括但不限于不侵权，时效性或满足特定目的的担保。
 
diff --git "a/content/zh/docs/Releasenotes/\346\272\220\344\273\243\347\240\201.md" "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/\346\272\220\344\273\243\347\240\201.md"
similarity index 100%
rename from "content/zh/docs/Releasenotes/\346\272\220\344\273\243\347\240\201.md"
rename to "docs/zh/docs/20.03_LTS/docs/Releasenotes/\346\272\220\344\273\243\347\240\201.md"
diff --git "a/content/zh/docs/Releasenotes/\347\224\250\346\210\267\351\241\273\347\237\245.md" "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/\347\224\250\346\210\267\351\241\273\347\237\245.md"
similarity index 50%
rename from "content/zh/docs/Releasenotes/\347\224\250\346\210\267\351\241\273\347\237\245.md"
rename to "docs/zh/docs/20.03_LTS/docs/Releasenotes/\347\224\250\346\210\267\351\241\273\347\237\245.md"
index f612df3f64d1e43279f0a7cbbb27b04128bcff22..b80cae46660533e422916e2df9cf9a2ed55188ca 100644
--- "a/content/zh/docs/Releasenotes/\347\224\250\346\210\267\351\241\273\347\237\245.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/\347\224\250\346\210\267\351\241\273\347\237\245.md"
@@ -1,6 +1,5 @@
 # 用户须知
 
--   openEuler版本号计数规则由openEuler x.x变更为以年月为版本号，以便用户了解版本发布时间，例如openEuler 20.09表示发布时间为2020年9月。
--   [Python核心团队](https://www.python.org/dev/peps/pep-0373/#update)已经于2020年1月停止对Python 2的维护。2020年，openEuler 20.09 LTS仅修复Python 2的致命CVE，并将于2020年12月31日全面停止维护。请您尽快切换到Python 3。
+-   openEuler版本号计数规则由openEuler x.x变更为以年月为版本号，以便用户了解版本发布时间，例如openEuler 20.03表示发布时间为2020年3月。
+-   [Python核心团队](https://www.python.org/dev/peps/pep-0373/#update)已经于2020年1月停止对Python 2的维护。2020年，openEuler 20.03 LTS仅修复Python 2的致命CVE，并将于2020年12月31日全面停止维护。请您尽快切换到Python 3。
 
-* [Python核心团队](https://www.python.org/dev/peps/pep-0373/#update)已经于2020年1月停止对Python 2的维护。2020年，openEuler 20.03 LTS仅修复Python 2的致命CVE，并将于2020年12月31日全面停止维护。请您尽快切换到Python 3。
\ No newline at end of file
diff --git "a/content/zh/docs/Releasenotes/\347\256\200\344\273\213.md" "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/\347\256\200\344\273\213.md"
similarity index 99%
rename from "content/zh/docs/Releasenotes/\347\256\200\344\273\213.md"
rename to "docs/zh/docs/20.03_LTS/docs/Releasenotes/\347\256\200\344\273\213.md"
index a93e39988321b9f901e74f729323f23828cb2196..5d32c5e38bc6012d6d1f0afb1c1e7f1fbda8fc0c 100644
--- "a/content/zh/docs/Releasenotes/\347\256\200\344\273\213.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/\347\256\200\344\273\213.md"
@@ -1,4 +1,4 @@
-# 简介
-
-openEuler是一款开源操作系统。当前openEuler内核源于Linux，支持鲲鹏及其它多种处理器，能够充分释放计算芯片的潜能，是由全球开源贡献者构建的高效、稳定、安全的开源操作系统，适用于数据库、大数据、云计算、人工智能等应用场景。同时，openEuler是一个面向全球的操作系统开源社区，通过社区合作，打造创新平台，构建支持多处理器架构、统一和开放的操作系统，推动软硬件应用生态繁荣发展。
-
+# 简介
+
+openEuler是一款开源操作系统。当前openEuler内核源于Linux，支持鲲鹏及其它多种处理器，能够充分释放计算芯片的潜能，是由全球开源贡献者构建的高效、稳定、安全的开源操作系统，适用于数据库、大数据、云计算、人工智能等应用场景。同时，openEuler是一个面向全球的操作系统开源社区，通过社区合作，打造创新平台，构建支持多处理器架构、统一和开放的操作系统，推动软硬件应用生态繁荣发展。
+
diff --git "a/content/zh/docs/Releasenotes/\347\263\273\347\273\237\345\256\211\350\243\205.md" "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/\347\263\273\347\273\237\345\256\211\350\243\205.md"
similarity index 43%
rename from "content/zh/docs/Releasenotes/\347\263\273\347\273\237\345\256\211\350\243\205.md"
rename to "docs/zh/docs/20.03_LTS/docs/Releasenotes/\347\263\273\347\273\237\345\256\211\350\243\205.md"
index 7788d15a0a44c493ae690387e9ea496a7ad6d27a..31c26a6a865942547e511fa14c5161fbac7c7c42 100644
--- "a/content/zh/docs/Releasenotes/\347\263\273\347\273\237\345\256\211\350\243\205.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/\347\263\273\347\273\237\345\256\211\350\243\205.md"
@@ -2,167 +2,91 @@
 
 ## 发布件
 
-openEuler发布件包括[ISO发布包](http://repo.openeuler.org/openEuler-20.09-LTS/ISO/)、[虚拟机镜像](http://repo.openeuler.org/openEuler-20.09-LTS/virtual_machine_img/)、[容器镜像](http://repo.openeuler.org/openEuler-20.09-LTS/docker_img/)和[repo源](http://repo.openeuler.org/openEuler-20.09-LTS/)。ISO发布包请参见[表1](#table8396719144315)。容器清单参见[表3](#table1276911538154)。repo源方便在线使用，repo源目录请参见[表4](#table953512211576)。
+[openEuler发布件](http://repo.openeuler.org/openEuler-20.03-LTS/)如下表所示，包括ISO发布包、容器镜像、虚拟机镜像和方便在线使用的repo源。
 
-**表 1**  发布ISO列表
+**表 1**  openEuler发布件
 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
名称

-
描述

-
openEuler-20.09-LTS-aarch64-dvd.iso

-
AArch64架构的基础安装ISO，包含了运行最小系统的核心组件

-
openEuler-20.09-LTS-everything-aarch64-dvd.iso

-
AArch64架构的全量安装ISO，包含了运行完整系统所需的全部组件

-
openEuler-20.09-LTS-debuginfo-aarch64-dvd.iso

-
AArch64架构下openEuler的调试ISO，包含了调试所需的符号表信息

-
openEuler-20.09-LTS-x86_64-dvd.iso

-
x86_64架构的基础安装ISO，包含了运行最小系统的核心组件

-
openEuler-20.09-LTS-everything-x86_64-dvd.iso

-
x86_64架构的全量安装ISO，包含了运行完整系统所需的全部组件

-
openEuler-20.09-LTS-debuginfo-x86_64-dvd.iso

-
x86_64架构下openEuler的调试ISO，包含了调试所需的符号表信息

-
openEuler-20.09-LTS-source-dvd.iso

-
openEuler源码ISO

-

-
-**表 2**  虚拟机镜像
-
-
-
-
-
-
-
-
-
-
-
-
-
-
名称

-
描述

-
openEuler-20.09-LTS.aarch64.qcow2.xz

-
AArch64架构下openEuler虚拟机镜像

-
openEuler-20.09-LTS.x86_64.qcow2.xz

-
x86_64架构下openEuler虚拟机镜像

-

-
->![](public_sys-resources/icon-note.gif) **说明：**   
->虚拟机镜像root用户默认密码为：openEuler12\#$，首次登录后请及时修改。  
-
-**表 3**  容器镜像列表
-
-
-
-
+
名称

-
描述

-

+
+
+	
+	
+	
-
-
-
-
-
+
+	
+	
+	
+
+
+	
+	
+	
+
+
+	
+	
+	
+
+
+	
+	
+	
+
+
+	
+	
+
+
+	
+	
+
+
+	
+	
+
+
+	
+	
+
+
+	
+	
+
+
+	
+	
-
目录类别描述
 

 
openEuler-docker.aarch64.tar.xz

-
AArch64架构下openEuler容器镜像

-
openEuler-docker.x86_64.tar.xz

-
x86_64架构下openEuler容器镜像

-
ISOISO发布包目录下区分AArch64架构、x86架构和source的ISO发布包。其中：
+		
    
+			
  • openEuler-20.03-LTS-aarch64-dvd.iso、openEuler-20.03-LTS-x86_64-dvd.iso：分别为AArch64架构、x86架构的openEuler基础安装软件包ISO，包含openEuler操作系统运行的基础组件，满足开发者基础的开发要求。
    • 
+			
  • openEuler-20.03-LTS-everything-aarch64-dvd.iso、openEuler-20.03-LTS-everything-x86_64-dvd.iso：分别为AArch64架构、x86架构的openEuler全量软件包ISO，除openEuler基础安装软件包的所有软件外，还包含了openEuler社区中已验证的软件包。满足开发者更高级的开发要求。
    • 
+			
  • openEuler-20.03-LTS-debuginfo-aarch64-dvd.iso、openEuler-20.03-LTS-debuginfo-x86_64-dvd.iso：分别为AArch64架构、x86架构的openEuler调试软件包ISO，包含了调试所需的符号表信息，用于软件功能和性能调试。
    • 
+			
  • openEuler-20.03-LTS-source-dvd.iso：openEuler社区所有源码软件包ISO，方便开发者离线使用。
    • 
+		

+		
说明：
+			
每个ISO发布包均有对应的校验文件，用于ISO发布包的完整性校验。

+		

+	
docker_img容器镜像openEuler容器镜像，仅提供基本的bash环境，作为基础容器镜像使用。目录下区分AArch64架构和x86架构。
+		
说明：
+			
容器镜像有对应的校验文件，用于容器镜像的完整性校验。

+		

+	
virtual_machine_img虚拟机镜像
openEuler虚拟机镜像，仅提供基本的运行环境，缩短虚拟机部署时间。目录下区分AArch64架构和x86架构。

+		
说明：
+			

+				
    
+					
  • 虚拟机镜像root用户默认密码为：openEuler12#$，首次登录后请及时修改。
    • 
+					
  • 虚拟机镜像有对应的校验文件，用于虚拟机镜像的完整性校验。
    • 
+				

+			

+		

+	
EPOLrepo源openEuler第三方软件包的repo源，主要来源于第三方和社区贡献，由提供方负责维护。目录下区分AArch64架构和x86架构。
OSopenEuler基础安装软件包的repo源，提供在线下和版本升级功能，软件包内容和ISO发布包中的基础安装软件包ISO相同。目录下区分AArch64架构和x86架构。
debuginfoopenEuler调试软件包的repo源，提供在线下载功能，软件包内容和ISO发布包中的调试软件包ISO相同。目录下区分AArch64架构和x86架构。
everythingopenEuler全量软件包的repo源，提供在线下载和版本升级功能，软件包内容和ISO发布包中的全量软件包ISO相同。目录下区分AArch64架构和x86架构。
extrasopenEuler扩展软件包的repo源，用于因新增特性而引入的新的软件包发布。目录下区分AArch64架构和x86架构。
sourceopenEuler社区所有源码软件包的repo源，方便开发者在线使用。
updateopenEuler升级软件包的repo源，用于已发布版本的bug、CVE的修复和部分软件因特性增强后的更新发布。提供在线下载和版本内软件升级功能。目录下区分AArch64架构和x86架构。
 

 

 
-**表 4**  repo源列表
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
目录

-
描述

-
ISO

-
存放ISO镜像

-
OS

-
存放基础软件包源

-
debuginfo

-
存放调试包源

-
docker_img

-
存放容器镜像

-
virtual_machine_img

-
存放虚拟机镜像

-
everything

-
存放全量软件包源

-
extras

-
存放扩展软件包源

-
source

-
存放源码软件源

-
update

-
存放升级软件包源

-
EPOL

-
存放openEuler扩展包

-

 
 ## 最小硬件要求
 
-安装 openEuler 20.09 LTS 所需的最小硬件要求如[表5](#zh-cn_topic_0182825778_tff48b99c9bf24b84bb602c53229e2541)所示。
+安装 openEuler 20.03 LTS 所需的最小硬件要求如[表5](#zh-cn_topic_0182825778_tff48b99c9bf24b84bb602c53229e2541)所示。
 
 **表 5**  最小硬件要求
 
@@ -192,6 +116,7 @@ openEuler发布件包括[ISO发布包](http://repo.openeuler.org/openEuler-20.09
 
 
 
+
 ## 硬件兼容性
 
 openEuler已验证支持的服务器和各部件典型配置请参见[表6](#zh-cn_topic_0227922427_table39822012)。openEuler后续将逐步增加对其他服务器的支持，也欢迎广大合作伙伴/开发者参与贡献和验证。
@@ -224,7 +149,7 @@ openEuler已验证支持的服务器和各部件典型配置请参见[表6](#zh-
 
 
内存

 
-
32G*4 2933MHz

+
32G\*4 2933MHz

 
 
 
RAID卡

diff --git "a/content/zh/docs/Releasenotes/\350\207\264\350\260\242.md" "b/docs/zh/docs/20.03_LTS/docs/Releasenotes/\350\207\264\350\260\242.md"
similarity index 100%
rename from "content/zh/docs/Releasenotes/\350\207\264\350\260\242.md"
rename to "docs/zh/docs/20.03_LTS/docs/Releasenotes/\350\207\264\350\260\242.md"
diff --git "a/content/zh/docs/Virtualization/figures/KVM\346\236\266\346\236\204\345\233\276.png" b/docs/zh/docs/20.03_LTS/docs/Virtualization/figures/kvm-architecture.png
similarity index 100%
rename from "content/zh/docs/Virtualization/figures/KVM\346\236\266\346\236\204\345\233\276.png"
rename to docs/zh/docs/20.03_LTS/docs/Virtualization/figures/kvm-architecture.png
diff --git "a/content/zh/docs/Virtualization/figures/\347\212\266\346\200\201\350\275\254\346\215\242\345\233\276.png" b/docs/zh/docs/20.03_LTS/docs/Virtualization/figures/status-transition-diagram.png
similarity index 100%
rename from "content/zh/docs/Virtualization/figures/\347\212\266\346\200\201\350\275\254\346\215\242\345\233\276.png"
rename to docs/zh/docs/20.03_LTS/docs/Virtualization/figures/status-transition-diagram.png
diff --git "a/content/zh/docs/Virtualization/figures/\350\231\232\346\213\237\347\275\221\347\273\234\347\273\223\346\236\204\345\233\276.png" b/docs/zh/docs/20.03_LTS/docs/Virtualization/figures/virtual-network-structure.png
similarity index 100%
rename from "content/zh/docs/Virtualization/figures/\350\231\232\346\213\237\347\275\221\347\273\234\347\273\223\346\236\204\345\233\276.png"
rename to docs/zh/docs/20.03_LTS/docs/Virtualization/figures/virtual-network-structure.png
diff --git "a/content/zh/docs/Virtualization/figures/\350\231\232\346\213\237\345\214\226\346\236\266\346\236\204.png" b/docs/zh/docs/20.03_LTS/docs/Virtualization/figures/virtualized-architecture.png
similarity index 100%
rename from "content/zh/docs/Virtualization/figures/\350\231\232\346\213\237\345\214\226\346\236\266\346\236\204.png"
rename to docs/zh/docs/20.03_LTS/docs/Virtualization/figures/virtualized-architecture.png
diff --git a/content/zh/docs/Virtualization/figures/zh-cn_image_0218587435.png b/docs/zh/docs/20.03_LTS/docs/Virtualization/figures/zh-cn_image_0218587435.png
similarity index 100%
rename from content/zh/docs/Virtualization/figures/zh-cn_image_0218587435.png
rename to docs/zh/docs/20.03_LTS/docs/Virtualization/figures/zh-cn_image_0218587435.png
diff --git a/content/zh/docs/Virtualization/figures/zh-cn_image_0218587436.png b/docs/zh/docs/20.03_LTS/docs/Virtualization/figures/zh-cn_image_0218587436.png
similarity index 100%
rename from content/zh/docs/Virtualization/figures/zh-cn_image_0218587436.png
rename to docs/zh/docs/20.03_LTS/docs/Virtualization/figures/zh-cn_image_0218587436.png
diff --git a/content/zh/docs/Virtualization/public_sys-resources/icon-caution.gif b/docs/zh/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-caution.gif
similarity index 100%
rename from content/zh/docs/Virtualization/public_sys-resources/icon-caution.gif
rename to docs/zh/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-caution.gif
diff --git a/content/zh/docs/Virtualization/public_sys-resources/icon-danger.gif b/docs/zh/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-danger.gif
similarity index 100%
rename from content/zh/docs/Virtualization/public_sys-resources/icon-danger.gif
rename to docs/zh/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-danger.gif
diff --git a/content/zh/docs/Virtualization/public_sys-resources/icon-note.gif b/docs/zh/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-note.gif
similarity index 100%
rename from content/zh/docs/Virtualization/public_sys-resources/icon-note.gif
rename to docs/zh/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-note.gif
diff --git a/content/zh/docs/Virtualization/public_sys-resources/icon-notice.gif b/docs/zh/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-notice.gif
similarity index 100%
rename from content/zh/docs/Virtualization/public_sys-resources/icon-notice.gif
rename to docs/zh/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-notice.gif
diff --git a/content/zh/docs/Virtualization/public_sys-resources/icon-tip.gif b/docs/zh/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-tip.gif
similarity index 100%
rename from content/zh/docs/Virtualization/public_sys-resources/icon-tip.gif
rename to docs/zh/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-tip.gif
diff --git a/content/zh/docs/Virtualization/public_sys-resources/icon-warning.gif b/docs/zh/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-warning.gif
similarity index 100%
rename from content/zh/docs/Virtualization/public_sys-resources/icon-warning.gif
rename to docs/zh/docs/20.03_LTS/docs/Virtualization/public_sys-resources/icon-warning.gif
diff --git a/content/zh/docs/Virtualization/virtualization.md b/docs/zh/docs/20.03_LTS/docs/Virtualization/virtualization.md
similarity index 100%
rename from content/zh/docs/Virtualization/virtualization.md
rename to docs/zh/docs/20.03_LTS/docs/Virtualization/virtualization.md
diff --git "a/content/zh/docs/Virtualization/\345\207\206\345\244\207\344\275\277\347\224\250\347\216\257\345\242\203.md" "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\345\207\206\345\244\207\344\275\277\347\224\250\347\216\257\345\242\203.md"
similarity index 98%
rename from "content/zh/docs/Virtualization/\345\207\206\345\244\207\344\275\277\347\224\250\347\216\257\345\242\203.md"
rename to "docs/zh/docs/20.03_LTS/docs/Virtualization/\345\207\206\345\244\207\344\275\277\347\224\250\347\216\257\345\242\203.md"
index a8f6b5340b4e8409187aabab0a618890f04f89f3..2d65647994d3c8720fe4721e4fc2af564642ecf2 100644
--- "a/content/zh/docs/Virtualization/\345\207\206\345\244\207\344\275\277\347\224\250\347\216\257\345\242\203.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\345\207\206\345\244\207\344\275\277\347\224\250\347\216\257\345\242\203.md"
@@ -58,7 +58,7 @@
     例如，查询openEuler-image.qcow2镜像磁盘空间大小的命令和回显如下，说明该镜像磁盘空间大小为4GiB。
 
     ```
-    $ qemu-img info openEuler-image.qcow2 
+    $ qemu-img info openEuler-image.qcow2
     image: openEuler-image.qcow2
     file format: qcow2
     virtual size: 4.0G (4294967296 bytes)
@@ -93,7 +93,7 @@
     例如，上述openEuler-image.qcow2镜像磁盘空间已扩展到24GiB，命令和回显如下：
 
     ```
-    $ qemu-img info openEuler-image.qcow2 
+    $ qemu-img info openEuler-image.qcow2
     image: openEuler-image.qcow2
     file format: qcow2
     virtual size: 24G (25769803776 bytes)
@@ -116,7 +116,7 @@
 本节给出搭建Linux网桥和Open vSwitch网桥的方法，使虚拟机连接到网络，用户可以根据情况选择搭建网桥的类型。
 
 **图 1**  虚拟网络结构图  
-![](figures/虚拟网络结构图.png "虚拟网络结构图")
+![](./figures/virtual-network-structure.png)
 
 ### 搭建Linux网桥
 
@@ -392,10 +392,7 @@ openEuler虚拟化使用virsh管理虚拟机。如果希望在非root用户使
    ```
    export LIBVIRT_DEFAULT_URI="qemu:///system"
    ```
-   执行如下命令，使配置生效。
-   ```
-   $ source ~/.bashrc
-   ```
+
 5. 在虚拟机XML配置文件中的domain根元素中添加如下内容，使qemu-kvm进程可以访问磁盘镜像文件。
 
    ```
diff --git "a/content/zh/docs/Virtualization/\345\256\211\350\243\205\350\231\232\346\213\237\345\214\226.md" "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\345\256\211\350\243\205\350\231\232\346\213\237\345\214\226.md"
similarity index 98%
rename from "content/zh/docs/Virtualization/\345\256\211\350\243\205\350\231\232\346\213\237\345\214\226.md"
rename to "docs/zh/docs/20.03_LTS/docs/Virtualization/\345\256\211\350\243\205\350\231\232\346\213\237\345\214\226.md"
index c8ab1946b98e428ef417ec4283560a9556783606..a5fa839014d0350c8db502803a811d97be212b4a 100644
--- "a/content/zh/docs/Virtualization/\345\256\211\350\243\205\350\231\232\346\213\237\345\214\226.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\345\256\211\350\243\205\350\231\232\346\213\237\345\214\226.md"
@@ -53,7 +53,7 @@
     ```
 
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >KVM模块已经集成在openEuler内核中，因此不需要单独安装。  
 
 ### 验证安装是否成功
diff --git "a/content/zh/docs/Virtualization/\346\234\200\344\275\263\345\256\236\350\267\265.md" "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\346\234\200\344\275\263\345\256\236\350\267\265.md"
similarity index 98%
rename from "content/zh/docs/Virtualization/\346\234\200\344\275\263\345\256\236\350\267\265.md"
rename to "docs/zh/docs/20.03_LTS/docs/Virtualization/\346\234\200\344\275\263\345\256\236\350\267\265.md"
index 9626b4e460a7c35d0cdffa0164f84529251dc2e6..655ebd4b7ffcd2286b909ead42db82f9499ff706 100644
--- "a/content/zh/docs/Virtualization/\346\234\200\344\275\263\345\256\236\350\267\265.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\346\234\200\344\275\263\345\256\236\350\267\265.md"
@@ -24,7 +24,7 @@
 
 在计算资源充足的情况下，为使虚拟机获得接近物理机的性能，可以使用halt-polling特性。没有使用halt-polling特性时，当vCPU空闲退出后，主机会把CPU资源分配给其他进程使用。当主机开启halt-polling特性时，虚拟机vCPU处于空闲时会polling一段时间，polling的时间由具体配置决定。若该vCPU在polling期间被唤醒，可以不从主机侧调度而继续运行，减少了调度流程的开销，从而在一定程度上提高了虚拟机系统的性能。
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >halt-polling的机制保证虚拟机的vCPU线程的及时响应，但在虚拟机空载的时候，主机侧也会polling，导致主机看到vCPU所在CPU占用率比较高，而实际虚拟机内部CPU占用率并不高。  
 
 #### 操作指导
@@ -317,7 +317,7 @@ qemu-ga（Qemu Guest Agent）它是运行在虚拟机内部的守护进程，它
 
 在一些对安全要求较高的使用场景，为了防止虚拟机内部信息泄露，qemu-ga提供了黑名单功能，用户可以通过黑名单选择性屏蔽qemu-ga提供的部分功能。
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >qemu-ga对应的安装包是qemu-guest-agent-xx.rpm，openEuler默认不安装。xx为实际版本号。  
 
 #### 操作方法
@@ -368,7 +368,7 @@ qemu-ga（Qemu Guest Agent）它是运行在虚拟机内部的守护进程，它
     root       727     1  0 08:17 ?        00:00:00 /usr/bin/qemu-ga --method=virtio-serial --path=/dev/virtio-ports/org.qemu.guest_agent.0 --blacklist=guest-file-open guest-file-close guest-file-read guest-file-write guest-file-seek guest-file-flush -F/etc/qemu-ga/fsfreeze-hook
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >更多关于qemu-ga的资料可以参见[https://wiki.qemu.org/Features/GuestAgent](https://wiki.qemu.org/Features/GuestAgent)。  
 
 
diff --git "a/content/zh/docs/Virtualization/\347\203\255\350\277\201\347\247\273\350\231\232\346\213\237\346\234\272.md" "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\347\203\255\350\277\201\347\247\273\350\231\232\346\213\237\346\234\272.md"
similarity index 100%
rename from "content/zh/docs/Virtualization/\347\203\255\350\277\201\347\247\273\350\231\232\346\213\237\346\234\272.md"
rename to "docs/zh/docs/20.03_LTS/docs/Virtualization/\347\203\255\350\277\201\347\247\273\350\231\232\346\213\237\346\234\272.md"
diff --git "a/content/zh/docs/Virtualization/\347\256\241\347\220\206\347\263\273\347\273\237\350\265\204\346\272\220.md" "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\347\256\241\347\220\206\347\263\273\347\273\237\350\265\204\346\272\220.md"
similarity index 98%
rename from "content/zh/docs/Virtualization/\347\256\241\347\220\206\347\263\273\347\273\237\350\265\204\346\272\220.md"
rename to "docs/zh/docs/20.03_LTS/docs/Virtualization/\347\256\241\347\220\206\347\263\273\347\273\237\350\265\204\346\272\220.md"
index fdbab66cedfa539d53f0869f2d509daf2bfb8610..0452ffee472f07471233d9e8af34b199aa4675ea 100644
--- "a/content/zh/docs/Virtualization/\347\256\241\347\220\206\347\263\273\347\273\237\350\265\204\346\272\220.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\347\256\241\347\220\206\347\263\273\347\273\237\350\265\204\346\272\220.md"
@@ -246,7 +246,7 @@ QEMU主进程绑定特性是将QEMU主进程绑定到特定的物理CPU范围内
         hvm
       
     ```
-    >![](public_sys-resources/icon-note.gif) **说明：**  
+    >![](./public_sys-resources/icon-note.gif) **说明：**  
     > placement的值必须是static；当前CPU数目是虚拟机启动后默认的CPU数目；热插CPU数目上限是虚拟机CPU热插能到达的上限值，该值不能超过Hypervisor支持的虚拟机最大CPU规格及GuestOS支持的最大CPU规格。
 
 -   使用virsh命令执行虚拟机CPU热插操作
@@ -262,7 +262,7 @@ QEMU主进程绑定特性是将QEMU主进程绑定到特定的物理CPU范围内
     --live: 选项，选填。在线生效。
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**  
+    >![](./public_sys-resources/icon-note.gif) **说明：**  
     > CPU上线依赖虚拟机内部操作，故CPU热插后需要Guest内部实现CPU自动上线或手动上线。
 
 
@@ -315,7 +315,7 @@ NUMA（Non Uniform Memory Access Architecture） 模式是一种分布式存储
 
     假设虚拟机的vCPU也绑定在NODE0的物理CPU上，就可以避免由于vCPU访问远端内存带来的性能下降。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >-   分配给虚拟机的内存不要超过该NUMA节点剩余的可用内存，否则可能导致虚拟机启动失败。  
     >-   建议虚拟机内存和vCPU都绑定在同一NUMA节点，避免vCPU访问远端内存造成性能下降。例如将上例中vCPU也绑定在NUMA node 0上。  
 
@@ -350,7 +350,7 @@ NUMA（Non Uniform Memory Access Architecture） 模式是一种分布式存储
   
 ```
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >-   项提供虚拟机内部呈现NUMA拓扑功能，“cell id”表示vNode编号，“cpus”表示vCPU编号，“memory”表示对应vNode上的内存大小。  
 >-   如果希望通过Guest NUMA提供更好的性能，则需要配置和，使vCPU和对应的内存分布在同一个物理NUMA NODE上：  
 >    -   中的“cellid”和中的“cell id”是对应的；“mode”可以配置为“strict”（严格从指定node上申请内存，内存不够则失败）、“preferred”（优先从某一node上申请内存，如果不够则从其他node上申请）、“interleave”（从指定的node上交叉申请内存）；“nodeset”表示指定物理NUMA NODE。  
@@ -397,7 +397,7 @@ NUMA（Non Uniform Memory Access Architecture） 模式是一种分布式存储
     ```
     上述xml表示为虚拟机配置32G初始内存，预留256个槽位号，最大支持1TB内存上限，2个NUMA node的配置为：
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >其中：
     >-   maxMemory字段中slots号表示预留的内存插槽，最大为256；
     >-   maxMemory表示虚拟机支持的最大物理内存上限；
diff --git "a/content/zh/docs/Virtualization/\347\256\241\347\220\206\350\231\232\346\213\237\346\234\272.md" "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\347\256\241\347\220\206\350\231\232\346\213\237\346\234\272.md"
similarity index 98%
rename from "content/zh/docs/Virtualization/\347\256\241\347\220\206\350\231\232\346\213\237\346\234\272.md"
rename to "docs/zh/docs/20.03_LTS/docs/Virtualization/\347\256\241\347\220\206\350\231\232\346\213\237\346\234\272.md"
index 0cc5312a72d3b9d1ca0f2aa9034454eaf726e821..c44d01d67c29eb945ff2efcbe2971811c97c0003 100644
--- "a/content/zh/docs/Virtualization/\347\256\241\347\220\206\350\231\232\346\213\237\346\234\272.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\347\256\241\347\220\206\350\231\232\346\213\237\346\234\272.md"
@@ -36,7 +36,7 @@
 虚拟机不同状态之间可以相关转换，但必须满足一定规则。虚拟机不同状态之间的转换常用规则如[图1](#fig671014583483)所示。
 
 **图 1**  状态转换图  
-![](figures/状态转换图.png "状态转换图")
+![](./figures/status-transition-diagram.png)
 
 #### 虚拟机标识
 
@@ -71,7 +71,7 @@
 
 
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >可通过virsh命令查询虚拟机Id和UUID，操作方法请参见[查询虚拟机信息](#查询虚拟机信息)章节内容。  
 
 ### 管理命令
@@ -223,7 +223,7 @@ virsh   
         # virsh undefine  
         ```
 
-        其中为销毁虚拟机的策略，可取值：
+        其中\为销毁虚拟机的策略，可取值：
 
         nvram：销毁虚拟机的同时删除其对应的nvram文件。
 
@@ -499,7 +499,7 @@ Libvirt组件提供了一组查询虚拟机状态信息的命令，包括虚拟
 -   虚拟机的VNC侦听端口，该端口一般在客户机启动时自动分配，一般为5900 + x（x为正整数，按照虚拟机启动的顺序递增，且5900对用户不可见）。
 -   如果VNC设置了密码，还需要获取虚拟机的VNC密码。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >为虚拟机VNC配置密码，需要编辑虚拟机XML配置文件，即为graphics元素新增一个passwd属性，属性的值为要配置的密码。例如，将虚拟机的VNC密码配置为n8VfjbFK的XML配置参考如下：  
     >```  
     >      
@@ -517,7 +517,7 @@ Libvirt组件提供了一组查询虚拟机状态信息的命令，包括虚拟
     :3
     ```
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >登录 VNC 需要配置防火墙规则，允许 VNC 端口的连接。参考命令如下，其中X为数值“5900 + 端口号” ，例如本例中为5903。  
     >```  
     >firewall-cmd --zone=public --add-port=X/tcp  
@@ -532,7 +532,7 @@ Libvirt组件提供了一组查询虚拟机状态信息的命令，包括虚拟
 
 VNC服务端和客户端默认采用明文方式进行数据传输，因此通信内容可能被第三方截获。为了提升安全性，openEuler支持VNC服务端配置TLS模式进行加密认证。TLS（Tansport Layer Security）即传输层安全，可以实现VNC服务端和客户端之间加密通信，从而防止通信内容被第三方截获。
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >-   使用TLS加密认证模式需要VNC客户端支持TLS模式（例如TigerVNC），否则无法连接到VNC客户端。  
 >-   TLS加密认证模式配置粒度为主机服务器级别，开启该特性后，主机上正在运行的所有虚拟机对应的VNC客户端都将开启TLS加密认证模式。  
 
@@ -551,7 +551,7 @@ VNC开启TLS加密认证模式的操作步骤如下：
 
 2.  为VNC创建证书和私钥文件。此处以GNU TLS为例进行说明。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >使用GNU TLS，请提前安装好gnu-utils软件包。  
 
     1.  制作证书颁发机构CA（Certificate Authority）的证书文件。
@@ -643,7 +643,7 @@ VNC开启TLS加密认证模式的操作步骤如下：
 
 5.  将生成的客户端证书ca-cert.pem，client-cert.pem和client-key.pem拷贝到VNC客户端。配置VNC客户端的TLS证书后即可使用VNC TLS登录。
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >-   VNC客户端证书的配置请参见各客户端对应的使用说明，由用户自行配置。  
     >-   登录虚拟机的方式请参见“使用VNC密码登录”。  
 
diff --git "a/content/zh/docs/Virtualization/\347\256\241\347\220\206\350\256\276\345\244\207.md" "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\347\256\241\347\220\206\350\256\276\345\244\207.md"
similarity index 97%
rename from "content/zh/docs/Virtualization/\347\256\241\347\220\206\350\256\276\345\244\207.md"
rename to "docs/zh/docs/20.03_LTS/docs/Virtualization/\347\256\241\347\220\206\350\256\276\345\244\207.md"
index ead838eec1a2ac6427abc6f3d504109217f853f9..067c3eb5e65af2525e1522f766d261778d31d881 100644
--- "a/content/zh/docs/Virtualization/\347\256\241\347\220\206\350\256\276\345\244\207.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\347\256\241\347\220\206\350\256\276\345\244\207.md"
@@ -274,7 +274,7 @@ PCI直通是指将host上的物理PCI设备直接呈现给一台虚拟机，供
 
 
PCI设备呈现的Guest内bdf号。

 
-
[0x03-0x1e](slot范围)

+
[0x03-0x1e](./slot范围)

 
说明：

 
  • domain为域信息，bus为总线号，slot为插槽号，function为功能
  • 除了slot插槽号，这里其余均默认为0。
  • 第一个slot插槽号0x00被系统占用，第二个slot号0x01被IDE控制器和USB控制器占用，第三个slot号0x02被video占用。
  • 最后一个slot号0x1f被pvchannel占用。

 
@@ -282,7 +282,7 @@ PCI直通是指将host上的物理PCI设备直接呈现给一台虚拟机，供
 
 
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >VFIO直通方式的最小直通单位是iommu\_group，host根据硬件上的ACS位，来划分iommu\_group。同一个iommu\_group中的设备只允许直通给同一台虚拟机（一个PCI设备上的若干个function，如果属于同一个iommu\_group，只允许直通给一个虚拟机使用）。  
 
 ### SR-IOV直通
@@ -291,7 +291,7 @@ PCI直通是指将host上的物理PCI设备直接呈现给一台虚拟机，供
 
 SR-IOV（Single Root I/O Virtualizaiton）是一种基于硬件的虚拟化解决方案，通过SR-IOV技术可以将一个PF（Physical Function）虚拟成多个VF（Virtual Function），每个VF都可以单独被直通给一个虚拟机，极大地提升了硬件资源利用率和虚拟机的I/O性能。一种典型的应用场景就是网卡SR-IOV设备直通，利用SR-IOV技术可以将一个物理网卡（PF）虚拟成多个VF网卡，再把VF直通给虚拟机使用。
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >-   SR-IOV需要物理硬件支持，使用SR-IOV前请确保要直通的硬件设备支持该能力，并且Host侧的设备驱动程序工作在SR-IOV模式下。  
 >-   查询网卡具体型号的办法如下：  
 >例如下述回显，第一列为网卡的PCI号，19e5:1822为网卡的厂商号设备号。  
@@ -447,7 +447,7 @@ SR-IOV（Single Root I/O Virtualizaiton）是一种基于硬件的虚拟化解
     
     
 
-    >![](public_sys-resources/icon-note.gif) **说明：**   
+    >![](./public_sys-resources/icon-note.gif) **说明：**   
     >关闭SR-IOV功能。  
     >在虚拟机使用完毕后（虚拟机关机，所有的VF均没有在使用中的时候），若要关闭SR-IOV功能。执行操作如下：  
     >这里以Hi1822网卡（eth0对应PF的网口名称）为例：  
@@ -457,7 +457,7 @@ SR-IOV（Single Root I/O Virtualizaiton）是一种基于硬件的虚拟化解
 
 #### HPRE加速器SR-IOV直通
 
-加速器引擎是TaiShan 200服务器基于Kunpeng 920处理器提供的硬件加速解决方案。HPRE加速器用于加速SSL/TLS应用，可以显著降低处理器消耗，提高处理器效率。  
+加速器引擎是TaiShan 200服务器基于Kunpeng 920服务器提供的硬件加速解决方案。HPRE加速器用于加速SSL/TLS应用，可以显著降低处理器消耗，提高处理器效率。  
 在鲲鹏服务器上，需要把主机Host上的HPRE加速器的VF直通给虚拟机，供虚拟机内部业务使用。
 
 **表 1**  HPRE加速器说明
@@ -472,7 +472,7 @@ SR-IOV（Single Root I/O Virtualizaiton）是一种基于硬件的虚拟化解
 | 最大VF数量  | 一个HPRE PF最多支持创建63个VF                                                                       |
 
 
->![](public_sys-resources/icon-note.gif) **说明：**  
+>![](./public_sys-resources/icon-note.gif) **说明：**  
 >当虚拟机正在使用VF设备时，不允许卸载Host上的驱动，加速器不支持热插拔。  
 >VF操作(VFNUMS为0表示关闭VF，hpre_num用来标识具体的加速器设备)：  
 >```
@@ -555,8 +555,8 @@ USB设备的XML描述：
 
 ```
 
--   
，其中，m表示该USB设备在主机上的bus地址，n表示device ID编号。
--   
 表示该USB设备要挂载到虚拟机指定的USB控制器。其中x表示控制器ID，与虚拟机所配置的USB控制器index编号相对应，y表示port地址。用户配置直通USB设备的时候需要配置这个字段，确保设备挂载的控制器与预期相符。
+-   \
，其中，m表示该USB设备在主机上的bus地址，n表示device ID编号。
+-   \
 表示该USB设备要挂载到虚拟机指定的USB控制器。其中x表示控制器ID，与虚拟机所配置的USB控制器index编号相对应，y表示port地址。用户配置直通USB设备的时候需要配置这个字段，确保设备挂载的控制器与预期相符。
 
 #### 配置方法
 
@@ -624,7 +624,7 @@ USB设备的XML描述：
 
 虚拟机在使用过程中可能由于病毒对系统的破坏、系统文件被误删除或误格式化等原因造成虚拟机系统损坏导致系统无法启动。为了使损坏的系统快速恢复，openEuler提供了存储快照功能。openEuler可以在用户不感知的情况下制作虚拟机在某一时刻的快照（制作通常指需要几秒钟），该快照能帮助用户将磁盘快速恢复到某一时刻的状态，例如系统损坏后能快速恢复系统，从而提升系统可靠性。
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >当前存储快照只支持raw、qcow2格式镜像，不支持block块设备。  
 
 ### 操作步骤
diff --git "a/content/zh/docs/Virtualization/\350\231\232\346\213\237\346\234\272\351\205\215\347\275\256.md" "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\350\231\232\346\213\237\346\234\272\351\205\215\347\275\256.md"
similarity index 99%
rename from "content/zh/docs/Virtualization/\350\231\232\346\213\237\346\234\272\351\205\215\347\275\256.md"
rename to "docs/zh/docs/20.03_LTS/docs/Virtualization/\350\231\232\346\213\237\346\234\272\351\205\215\347\275\256.md"
index 9988f532a1c95fa71b2c3e5ada56d7eb41b81def..0b52022529450f012c9c5bbd30aca38c9b5b4b33 100644
--- "a/content/zh/docs/Virtualization/\350\231\232\346\213\237\346\234\272\351\205\215\347\275\256.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\350\231\232\346\213\237\346\234\272\351\205\215\347\275\256.md"
@@ -375,7 +375,7 @@ XML配置文件中使用元素“interface”，其属性“type”表示虚拟
 
 PCIe总线是一种典型的树结构，具有比较好的扩展性，总线之间通过控制器关联，这里以PCIe总线为例介绍如何为虚拟机配置总线拓扑。
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >总线的配置相对比较繁琐，若不需要精确控制设备拓扑结构，可以使用libvirt自动生成的缺省总线配置。  
 
 #### 元素介绍
@@ -386,9 +386,9 @@ controller：控制器元素，表示一个总线。
 
 -   属性type：控制器必选属性，表示总线类型。常用取值有“pci”、“usb”、“scsi”、“virtio-serial”、“fdc”、“ccid”。
 -   属性index：控制器必选属性，表示控制器的总线“bus”编号（编号从0开始），可以在地址元素“address”元素中使用。
--   属性model：控制器必选属性，表示控制器的具体型号，其可选择的值与控制器类型“type”的值相关，对应关系及含义请参见[表4](#table191911761111)。
+-   属性model：控制器必选属性，表示控制器的具体型号，其可选择的值与控制器类型“type”的值相关，对应关系及含义请参见[表1](#table191911761111)。
 -   子元素address：为设备或控制器指定其在总线网络中的挂载位置。
-    -   属性type：设备地址类型。常用取值有“pci”、“usb”、“drive”。address的type类型不同， 对应的属性也不同，常用type属性值及其该取值下address的属性请参见[表5](#table1200165711314)。
+    -   属性type：设备地址类型。常用取值有“pci”、“usb”、“drive”。address的type类型不同， 对应的属性也不同，常用type属性值及其该取值下address的属性请参见[表2](#table1200165711314)。
 
 -   子元素model：控制器具体型号的名称。
     -   属性name：指定控制器具体型号的名称，和父元素controller中的属性model对应。
@@ -577,7 +577,7 @@ controller：控制器元素，表示一个总线。
 
 例如，在下面的示例中，配置了虚拟机的模拟器路径，pty串口、virtio媒体设备、USB写字板、USB键盘以及VNC图形设备。
 
->![](public_sys-resources/icon-note.gif) **说明：**   
+>![](./public_sys-resources/icon-note.gif) **说明：**   
 >graphics的type配置为VNC时，建议配置属性passwd，即使用VNC登录时的密码。  
 
 ```
diff --git "a/content/zh/docs/Virtualization/\350\256\244\350\257\206\350\231\232\346\213\237\345\214\226.md" "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\350\256\244\350\257\206\350\231\232\346\213\237\345\214\226.md"
similarity index 96%
rename from "content/zh/docs/Virtualization/\350\256\244\350\257\206\350\231\232\346\213\237\345\214\226.md"
rename to "docs/zh/docs/20.03_LTS/docs/Virtualization/\350\256\244\350\257\206\350\231\232\346\213\237\345\214\226.md"
index 0f66103873ba477981c238a88442a5a128e3fbb3..988bf7f8a38ee656cd9ef293ebad10130d55beb7 100644
--- "a/content/zh/docs/Virtualization/\350\256\244\350\257\206\350\231\232\346\213\237\345\214\226.md"
+++ "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\350\256\244\350\257\206\350\231\232\346\213\237\345\214\226.md"
@@ -1,90 +1,90 @@
-# 认识虚拟化
-
-## 简介
-
-在计算机技术中，虚拟化是一种资源管理技术，它将计算机的各种实体资源（处理器、内存、磁盘、网络适配器等）予以抽象，转换后呈现并可供分割、组合为一个或多个计算机配置环境。这种资源管理技术打破了实体结构不可分割的障碍，使这些资源在虚拟化后不受现有资源的架设方式、地域或物理配置限制，从而让用户可以更好地应用计算机硬件资源，提高资源利用率。
-
-虚拟化使得一台物理服务器上可以运行多台虚拟机，虚拟机共享物理机的处理器、内存、I/O资源等，但逻辑上虚拟机之间是互相隔离的。在虚拟化技术中，通常将这个物理服务器称为宿主机，宿主机上运行的虚拟机也叫客户机，虚拟机内部运行的操作系统称为客户机操作系统。在宿主机和虚拟机之间存在一层叫虚拟化层的软件，用于实现虚拟硬件的模拟，通常这个虚拟化层被称为虚拟机监视器，如下图所示：
-
-**图 1**  虚拟化架构  
-![](figures/虚拟化架构.png "虚拟化架构")
-
-## 虚拟化架构
-
-当前的主流虚拟化技术按照VMM（Virtual Machine Monitor）实现结构不同分为两种：
-
--   Hypervisor模型
-
-    在这种模型中，VMM被看做是一个完备的操作系统，同时还具备虚拟化功能，VMM直接管理所有的物理资源，包括处理器，内存和I/O设备等。
-
--   宿主模型
-
-    这种模型中，物理资源是由宿主机操作系统管理，宿主机操作系统是传统的操作系统，如Linux，Windows等，宿主机操作系统不提供虚拟化能力，提供虚拟化能力的VMM作为系统的一个驱动或者软件运行在宿主操作系统上，VMM通过调用host OS的服务获得资源，实现处理器，内存和I/O设备的模拟，这种模型的虚拟化实现有KVM、Virtual Box等。
-
-
-KVM（Kernel-based Virtual Machine）即基于内核的虚拟机，是Linux的一个内核模块，该内核模块使Linux成为一个hypervisor。KVM架构如[图2](#fig310953013541)所示。KVM本身未模拟任何硬件设备，它用于使能硬件提供的虚拟化能力，比如Intel VT-x, AMD-V, ARM virtualization extensions等。主板、内存及I/O等设备的模拟由用户态的QEMU完成。用户态QEMU配合内核KVM模块共同完成虚拟机的硬件模拟，客户操作系统运行在QEMU和KVM模拟的硬件上。
-
-**图 2**  KVM架构图  
-![](figures/KVM架构图.png "KVM架构图")
-
-## 虚拟化组件
-
-openEuler软件包中提供的虚拟化相关组件：
-
--   KVM：提供核心的虚拟化基础设施，使Linux系统成为一个hypervisor，支持多个虚拟机同时在该主机上运行。
--   QEMU：模拟处理器并提供一组设备模型，配合KVM实现基于硬件的虚拟化模拟加速。
--   Libvirt：为管理虚拟机提供工具集，主要包含统一、稳定、开放的应用程序接口（API）、守护进程 （Libvirtd）和一个默认命令行管理工具（virsh）。
--   Open vSwitch：为虚拟机提供虚拟网络的工具集，支持编程扩展，以及标准的管理接口和协议（如NetFlow， sFlow，IPFIX， RSPAN， CLI， LACP， 802.1ag）。
-
-## 虚拟化特点
-
-业界普遍认可虚拟化有以下特点：
-
--   分区
-
-    虚拟化可以对一台物理服务器进行软件逻辑分割，实现运行多台不同规格的虚拟机（虚拟服务器）。
-
-
--   隔离
-
-    虚拟化能够模拟虚拟硬件，为虚拟机运行完整操作系统提供硬件条件，每个虚拟机内部操作系统都是独立的，互相隔离的。例如一台虚拟机的操作系统由于故障或者受到恶意破坏而崩溃，其他虚拟机内部的操作系统和应用不会受到任何影响。
-
-
--   封装性
-
-    以虚拟机为粒度封装，优秀的封装性使得虚拟机比物理机更灵活，可以实现虚拟机的热迁移、快照、克隆等功能，实现数据中心的快速部署和自动化运维。
-
-
--   硬件无关
-
-    经过虚拟化层的抽象后，虚拟机与底层的硬件没有直接的绑定关系，可以在其他服务器上不加修改地运行虚拟机。
-
-
-## 虚拟化优势
-
-虚拟化为数据中心的基础设施带来了众多优势：
-
--   灵活性和可扩展性
-
-    用户可以根据需求进行动态资源分配和回收，满足动态变化的业务需求，同时也可以根据不同的产品需求，规划不同的虚拟机规格，在不改变物理资源配置的情况下进行规模调整。
-
-
--   更高的可用性和更好的运维手段
-
-    虚拟化提供热迁移，快照，热升级，容灾自动恢复等运维手段，可以在不影响用户的情况下对物理资源进行删除、升级或变更，提高了业务连续性，同时可以实现自动化运维。
-
-
--   提高安全性
-
-    虚拟化提供了操作系统级的隔离，同时实现基于硬件提供的处理器操作特权级控制，相比简单的共享机制具有更高的安全性，可实现对数据和服务进行可控和安全的访问。
-
-
--   更高的资源利用率
-
-    虚拟化可支持实现物理资源和资源池的动态共享，提高资源利用率。
-
-
-## openEuler虚拟化
-
-openEuler提供了支持AArch64和x86_64处理器架构的KVM虚拟化组件。
-
+# 认识虚拟化
+
+## 简介
+
+在计算机技术中，虚拟化是一种资源管理技术，它将计算机的各种实体资源（处理器、内存、磁盘、网络适配器等）予以抽象，转换后呈现并可供分割、组合为一个或多个计算机配置环境。这种资源管理技术打破了实体结构不可分割的障碍，使这些资源在虚拟化后不受现有资源的架设方式、地域或物理配置限制，从而让用户可以更好地应用计算机硬件资源，提高资源利用率。
+
+虚拟化使得一台物理服务器上可以运行多台虚拟机，虚拟机共享物理机的处理器、内存、I/O资源等，但逻辑上虚拟机之间是互相隔离的。在虚拟化技术中，通常将这个物理服务器称为宿主机，宿主机上运行的虚拟机也叫客户机，虚拟机内部运行的操作系统称为客户机操作系统。在宿主机和虚拟机之间存在一层叫虚拟化层的软件，用于实现虚拟硬件的模拟，通常这个虚拟化层被称为虚拟机监视器，如下图所示：
+
+**图 1**  虚拟化架构  
+![](./figures/virtualized-architecture.png)
+
+## 虚拟化架构
+
+当前的主流虚拟化技术按照VMM（Virtual Machine Monitor）实现结构不同分为两种：
+
+-   Hypervisor模型
+
+    在这种模型中，VMM被看做是一个完备的操作系统，同时还具备虚拟化功能，VMM直接管理所有的物理资源，包括处理器，内存和I/O设备等。
+
+-   宿主模型
+
+    这种模型中，物理资源是由宿主机操作系统管理，宿主机操作系统是传统的操作系统，如Linux，Windows等，宿主机操作系统不提供虚拟化能力，提供虚拟化能力的VMM作为系统的一个驱动或者软件运行在宿主操作系统上，VMM通过调用host OS的服务获得资源，实现处理器，内存和I/O设备的模拟，这种模型的虚拟化实现有KVM、Virtual Box等。
+
+
+KVM（Kernel-based Virtual Machine）即基于内核的虚拟机，是Linux的一个内核模块，该内核模块使Linux成为一个hypervisor。KVM架构如[图2](#fig310953013541)所示。KVM本身未模拟任何硬件设备，它用于使能硬件提供的虚拟化能力，比如Intel VT-x, AMD-V, ARM virtualization extensions等。主板、内存及I/O等设备的模拟由用户态的QEMU完成。用户态QEMU配合内核KVM模块共同完成虚拟机的硬件模拟，客户操作系统运行在QEMU和KVM模拟的硬件上。
+
+**图 2**  KVM架构图  
+![](./figures/kvm-architecture.png)
+
+## 虚拟化组件
+
+openEuler软件包中提供的虚拟化相关组件：
+
+-   KVM：提供核心的虚拟化基础设施，使Linux系统成为一个hypervisor，支持多个虚拟机同时在该主机上运行。
+-   QEMU：模拟处理器并提供一组设备模型，配合KVM实现基于硬件的虚拟化模拟加速。
+-   Libvirt：为管理虚拟机提供工具集，主要包含统一、稳定、开放的应用程序接口（API）、守护进程 （Libvirtd）和一个默认命令行管理工具（virsh）。
+-   Open vSwitch：为虚拟机提供虚拟网络的工具集，支持编程扩展，以及标准的管理接口和协议（如NetFlow， sFlow，IPFIX， RSPAN， CLI， LACP， 802.1ag）。
+
+## 虚拟化特点
+
+业界普遍认可虚拟化有以下特点：
+
+-   分区
+
+    虚拟化可以对一台物理服务器进行软件逻辑分割，实现运行多台不同规格的虚拟机（虚拟服务器）。
+
+
+-   隔离
+
+    虚拟化能够模拟虚拟硬件，为虚拟机运行完整操作系统提供硬件条件，每个虚拟机内部操作系统都是独立的，互相隔离的。例如一台虚拟机的操作系统由于故障或者受到恶意破坏而崩溃，其他虚拟机内部的操作系统和应用不会受到任何影响。
+
+
+-   封装性
+
+    以虚拟机为粒度封装，优秀的封装性使得虚拟机比物理机更灵活，可以实现虚拟机的热迁移、快照、克隆等功能，实现数据中心的快速部署和自动化运维。
+
+
+-   硬件无关
+
+    经过虚拟化层的抽象后，虚拟机与底层的硬件没有直接的绑定关系，可以在其他服务器上不加修改地运行虚拟机。
+
+
+## 虚拟化优势
+
+虚拟化为数据中心的基础设施带来了众多优势：
+
+-   灵活性和可扩展性
+
+    用户可以根据需求进行动态资源分配和回收，满足动态变化的业务需求，同时也可以根据不同的产品需求，规划不同的虚拟机规格，在不改变物理资源配置的情况下进行规模调整。
+
+
+-   更高的可用性和更好的运维手段
+
+    虚拟化提供热迁移，快照，热升级，容灾自动恢复等运维手段，可以在不影响用户的情况下对物理资源进行删除、升级或变更，提高了业务连续性，同时可以实现自动化运维。
+
+
+-   提高安全性
+
+    虚拟化提供了操作系统级的隔离，同时实现基于硬件提供的处理器操作特权级控制，相比简单的共享机制具有更高的安全性，可实现对数据和服务进行可控和安全的访问。
+
+
+-   更高的资源利用率
+
+    虚拟化可支持实现物理资源和资源池的动态共享，提高资源利用率。
+
+
+## openEuler虚拟化
+
+openEuler提供了支持AArch64和x86_64处理器架构的KVM虚拟化组件。
+
diff --git "a/content/zh/docs/Virtualization/\351\231\204\345\275\225.md" "b/docs/zh/docs/20.03_LTS/docs/Virtualization/\351\231\204\345\275\225.md"
similarity index 100%
rename from "content/zh/docs/Virtualization/\351\231\204\345\275\225.md"
rename to "docs/zh/docs/20.03_LTS/docs/Virtualization/\351\231\204\345\275\225.md"
diff --git a/docs/zh/docs/20.03_LTS/menu/menu.json b/docs/zh/docs/20.03_LTS/menu/menu.json
new file mode 100644
index 0000000000000000000000000000000000000000..feda7c972add3d4e1c0301a84b10899c73169861
--- /dev/null
+++ b/docs/zh/docs/20.03_LTS/menu/menu.json
@@ -0,0 +1,429 @@
+[{
+    "label": "法律声明",
+    "path": "docs/Releasenotes/法律声明",
+    "children": []
+}, {
+    "label": "发行说明",
+    "path": "docs/Releasenotes/release_notes",
+    "children": [{
+        "label": "用户须知",
+        "path": "docs/Releasenotes/用户须知",
+        "children": []
+    }, {
+        "label": "简介",
+        "path": "docs/Releasenotes/简介",
+        "children": []
+    }, {
+        "label": "系统安装",
+        "path": "docs/Releasenotes/系统安装",
+        "children": []
+    }, {
+        "label": "关键特性",
+        "path": "docs/Releasenotes/关键特性",
+        "children": []
+    }, {
+        "label": "已知问题",
+        "path": "docs/Releasenotes/已知问题",
+        "children": []
+    }, {
+        "label": "已修复问题",
+        "path": "docs/Releasenotes/已修复问题",
+        "children": []
+    }, {
+        "label": "CVE漏洞",
+        "path": "docs/Releasenotes/CVE漏洞",
+        "children": []
+    }, {
+        "label": "源代码",
+        "path": "docs/Releasenotes/源代码",
+        "children": []
+    }, {
+        "label": "参与贡献",
+        "path": "docs/Releasenotes/参与贡献",
+        "children": []
+    }, {
+        "label": "致谢",
+        "path": "docs/Releasenotes/致谢",
+        "children": []
+    }]
+}, {
+    "label": "快速入门",
+    "path": "docs/Quickstart/quick-start",
+    "children": []
+}, {
+    "label": "安装指南",
+    "path": "docs/Installation/installation",
+    "children": [{
+        "label": "安装准备",
+        "path": "docs/Installation/安装准备",
+        "children": []
+    }, {
+        "label": "安装方式介绍",
+        "path": "docs/Installation/安装方式介绍",
+        "children": []
+    }, {
+        "label": "安装指导",
+        "path": "docs/Installation/安装指导",
+        "children": []
+    }, {
+        "label": "使用kickstart自动化安装",
+        "path": "docs/Installation/使用kickstart自动化安装",
+        "children": []
+    }, {
+        "label": "FAQ",
+        "path": "docs/Installation/FAQ",
+        "children": []
+    }]
+}, {
+    "label": "管理员指南",
+    "path": "docs/Administration/administration",
+    "children": [{
+        "label": "查看系统信息",
+        "path": "docs/Administration/查看系统信息",
+        "children": []
+    }, {
+        "label": "基础配置",
+        "path": "docs/Administration/基础配置",
+        "children": []
+    }, {
+        "label": "管理用户和用户组",
+        "path": "docs/Administration/管理用户和用户组",
+        "children": []
+    }, {
+        "label": "使用DNF管理软件包",
+        "path": "docs/Administration/使用DNF管理软件包",
+        "children": []
+    }, {
+        "label": "管理服务",
+        "path": "docs/Administration/管理服务",
+        "children": []
+    }, {
+        "label": "管理进程",
+        "path": "docs/Administration/管理进程",
+        "children": []
+    }, {
+        "label": "配置网络",
+        "path": "docs/Administration/配置网络",
+        "children": []
+    }, {
+        "label": "使用LVM管理硬盘",
+        "path": "docs/Administration/使用LVM管理硬盘",
+        "children": []
+    }, {
+        "label": "使用KAE加速引擎",
+        "path": "docs/Administration/使用KAE加速引擎",
+        "children": []
+    }, {
+        "label": "搭建服务",
+        "path": "docs/Administration/搭建服务",
+        "children": [{
+            "label": "搭建repo服务器",
+            "path": "docs/Administration/搭建repo服务器",
+            "children": []
+        }, {
+            "label": "搭建FTP服务器",
+            "path": "docs/Administration/搭建FTP服务器",
+            "children": []
+        }, {
+            "label": "搭建web服务器",
+            "path": "docs/Administration/搭建web服务器",
+            "children": []
+        }, {
+            "label": "搭建数据库服务器",
+            "path": "docs/Administration/搭建数据库服务器",
+            "children": []
+        }]
+    }, {
+        "label": "FAQ",
+        "path": "docs/Administration/FAQ-54",
+        "children": []
+    }]
+}, {
+    "label": "虚拟化用户指南",
+    "path": "docs/Virtualization/virtualization",
+    "children": [{
+        "label": "认识虚拟化",
+        "path": "docs/Virtualization/认识虚拟化",
+        "children": []
+    }, {
+        "label": "安装虚拟化",
+        "path": "docs/Virtualization/安装虚拟化",
+        "children": []
+    }, {
+        "label": "准备使用环境",
+        "path": "docs/Virtualization/准备使用环境",
+        "children": []
+    }, {
+        "label": "虚拟机配置",
+        "path": "docs/Virtualization/虚拟机配置",
+        "children": []
+    }, {
+        "label": "管理虚拟机",
+        "path": "docs/Virtualization/管理虚拟机",
+        "children": []
+    }, {
+        "label": "热迁移虚拟机",
+        "path": "docs/Virtualization/热迁移虚拟机",
+        "children": []
+    }, {
+        "label": "管理系统资源",
+        "path": "docs/Virtualization/管理系统资源",
+        "children": []
+    }, {
+        "label": "管理设备",
+        "path": "docs/Virtualization/管理设备",
+        "children": []
+    }, {
+        "label": "最佳实践",
+        "path": "docs/Virtualization/最佳实践",
+        "children": []
+    }, {
+        "label": "附录",
+        "path": "docs/Virtualization/附录",
+        "children": []
+    }]
+}, {
+    "label": "容器用户指南",
+    "path": "docs/Container/container",
+    "children": [{
+        "label": "iSula容器引擎",
+        "path": "docs/Container/iSula容器引擎",
+        "children": [{
+            "label": "安装、升级与卸载",
+            "path": "docs/Container/安装-升级与卸载",
+            "children": [{
+                "label": "安装与配置",
+                "path": "docs/Container/安装与配置",
+                "children": []
+            }, {
+                "label": "升级",
+                "path": "docs/Container/升级",
+                "children": []
+            }, {
+                "label": "卸载",
+                "path": "docs/Container/卸载",
+                "children": []
+            }]
+        }, {
+            "label": "使用指南",
+            "path": "docs/Container/使用指南",
+            "children": [{
+                "label": "容器管理",
+                "path": "docs/Container/容器管理",
+                "children": []
+            }, {
+                "label": "支持CNI网络",
+                "path": "docs/Container/支持CNI网络",
+                "children": []
+            }, {
+                "label": "特权容器",
+                "path": "docs/Container/特权容器",
+                "children": []
+            }, {
+                "label": "CRI接口",
+                "path": "docs/Container/CRI接口",
+                "children": []
+            }, {
+                "label": "镜像管理",
+                "path": "docs/Container/镜像管理",
+                "children": []
+            }, {
+                "label": "容器健康状态检查",
+                "path": "docs/Container/容器健康状态检查",
+                "children": []
+            }, {
+                "label": "查询信息",
+                "path": "docs/Container/查询信息",
+                "children": []
+            }, {
+                "label": "安全特性",
+                "path": "docs/Container/安全特性",
+                "children": []
+            }, {
+                "label": "支持OCI hooks",
+                "path": "docs/Container/支持OCI-hooks",
+                "children": []
+            }]
+        }, {
+            "label": "附录",
+            "path": "docs/Container/附录",
+            "children": []
+        }]
+    }, {
+        "label": "系统容器",
+        "path": "docs/Container/系统容器",
+        "children": [{
+            "label": "安装指导",
+            "path": "docs/Container/安装指导",
+            "children": []
+        }, {
+            "label": "使用指南",
+            "path": "docs/Container/使用指南-1",
+            "children": [{
+                "label": "指定rootfs创建容器",
+                "path": "docs/Container/指定rootfs创建容器",
+                "children": []
+            }, {
+                "label": "通过systemd启动容器",
+                "path": "docs/Container/通过systemd启动容器",
+                "children": []
+            }, {
+                "label": "容器内reboot/shutdown",
+                "path": "docs/Container/容器内reboot-shutdown",
+                "children": []
+            }, {
+                "label": "cgroup路径可配置",
+                "path": "docs/Container/cgroup路径可配置",
+                "children": []
+            }, {
+                "label": "namespace化内核参数可写",
+                "path": "docs/Container/namespace化内核参数可写",
+                "children": []
+            }, {
+                "label": "共享内存通道",
+                "path": "docs/Container/共享内存通道",
+                "children": []
+            }, {
+                "label": "动态加载内核模块",
+                "path": "docs/Container/动态加载内核模块",
+                "children": []
+            }, {
+                "label": "环境变量持久化",
+                "path": "docs/Container/环境变量持久化",
+                "children": []
+            }, {
+                "label": "最大句柄数限制",
+                "path": "docs/Container/最大句柄数限制",
+                "children": []
+            }, {
+                "label": "安全性和隔离性",
+                "path": "docs/Container/安全性和隔离性",
+                "children": []
+            }, {
+                "label": "容器资源动态管理",
+                "path": "docs/Container/容器资源动态管理",
+                "children": []
+            }]
+        }, {
+            "label": "附录",
+            "path": "docs/Container/附录-2",
+            "children": []
+        }]
+    }, {
+        "label": "安全容器",
+        "path": "docs/Container/安全容器",
+        "children": [{
+            "label": "安装与配置",
+            "path": "docs/Container/安装与配置-2",
+            "children": []
+        }, {
+            "label": "使用方法",
+            "path": "docs/Container/使用方法-1",
+            "children": [{
+                "label": "管理安全容器的生命周期",
+                "path": "docs/Container/管理安全容器的生命周期",
+                "children": []
+            }, {
+                "label": "为安全容器配置资源",
+                "path": "docs/Container/为安全容器配置资源",
+                "children": []
+            }, {
+                "label": "为安全容器配置网络",
+                "path": "docs/Container/为安全容器配置网络",
+                "children": []
+            }, {
+                "label": "监控安全容器",
+                "path": "docs/Container/监控安全容器",
+                "children": []
+            }]
+        }, {
+            "label": "附录",
+            "path": "docs/Container/附录-3",
+            "children": []
+        }]
+    }, {
+        "label": "Docker容器",
+        "path": "docs/Container/Docker容器",
+        "children": [{
+            "label": "安装配置",
+            "path": "docs/Container/安装配置-3",
+            "children": []
+        }, {
+            "label": "容器管理",
+            "path": "docs/Container/容器管理-3",
+            "children": []
+        }, {
+            "label": "镜像管理",
+            "path": "docs/Container/镜像管理-3",
+            "children": []
+        }, {
+            "label": "命令行参考",
+            "path": "docs/Container/命令行参考",
+            "children": [{
+                "label": "容器引擎",
+                "path": "docs/Container/容器引擎-4",
+                "children": []
+            }, {
+                "label": "容器管理",
+                "path": "docs/Container/容器管理-4",
+                "children": []
+            }, {
+                "label": "镜像管理",
+                "path": "docs/Container/镜像管理-4",
+                "children": []
+            }, {
+                "label": "统计信息",
+                "path": "docs/Container/统计信息-4",
+                "children": []
+            }]
+        }]
+    }]
+}, {
+    "label": "A-Tune用户指南",
+    "path": "docs/A-Tune/A-Tune",
+    "children": [{
+        "label": "认识A-Tune",
+        "path": "docs/A-Tune/认识A-Tune",
+        "children": []
+    }, {
+        "label": "安装与部署",
+        "path": "docs/A-Tune/安装与部署",
+        "children": []
+    }, {
+        "label": "使用方法",
+        "path": "docs/A-Tune/使用方法",
+        "children": []
+    }, {
+        "label": "常见问题与解决方法",
+        "path": "docs/A-Tune/常见问题与解决方法",
+        "children": []
+    }, {
+        "label": "附录",
+        "path": "docs/A-Tune/附录",
+        "children": []
+    }]
+}, {
+    "label": "应用开发指南",
+    "path": "docs/ApplicationDev/application-development",
+    "children": [{
+        "label": "开发环境准备",
+        "path": "docs/ApplicationDev/开发环境准备",
+        "children": []
+    }, {
+        "label": "使用GCC编译",
+        "path": "docs/ApplicationDev/使用GCC编译",
+        "children": []
+    }, {
+        "label": "使用make编译",
+        "path": "docs/ApplicationDev/使用make编译",
+        "children": []
+    }, {
+        "label": "使用JDK编译",
+        "path": "docs/ApplicationDev/使用JDK编译",
+        "children": []
+    }, {
+        "label": "构建RPM包",
+        "path": "docs/ApplicationDev/构建RPM包",
+        "children": []
+    }]
+}]
\ No newline at end of file
diff --git a/docs/zh/docs/path/path.json b/docs/zh/docs/path/path.json
new file mode 100644
index 0000000000000000000000000000000000000000..4f70da00622558a7cbe0fd39050001e0441acd96
--- /dev/null
+++ b/docs/zh/docs/path/path.json
@@ -0,0 +1,138 @@
+[
+    {
+        "value": "1.0_Base",
+        "name": "1.0 BASE",
+        "docs": [
+            {
+                "title": "了解",
+                "doc": [
+                    {
+                        "img": "/img/docs/docs-releasenotes.svg",
+                        "path": "/docs/Releasenotes/release_notes.html",
+                        "name": "发行说明"
+                    }
+                ]
+            },
+            {
+                "title": "安装",
+                "doc": [
+                    {
+                        "img": "/img/docs/docs-installation.svg",
+                        "path": "/docs/Installation/installation.html",
+                        "name": "安装指南"
+                    }
+                ]
+            },
+            {
+                "title": "管理",
+                "doc": [
+                    {
+                        "img": "/img/docs/docs-administration.svg",
+                        "path": "/docs/Administration/administration.html",
+                        "name": "管理员指南"
+                    }
+                ]
+            },
+            {
+                "title": "使用",
+                "doc": [
+                    {
+                        "img": "/img/docs/docs-user.svg",
+                        "path": "/docs/Virtualization/virtualization.html",
+                        "name": "虚拟化用户指南"
+                    },
+                    {
+                        "img": "/img/docs/docs-user.svg",
+                        "path": "/docs/Container/container.html",
+                        "name": "容器用户指南"
+                    },
+                    {
+                        "img": "/img/docs/docs-user.svg",
+                        "path": "/docs/SecHarden/secHarden.html",
+                        "name": "安全加固"
+                    }
+                ]
+            },
+            {
+                "title": "开发",
+                "doc": [
+                    {
+                        "img":"/img/docs/docs-exploit.svg",
+                        "name": "应用开发指南"
+                    }
+                ]
+            }
+        ]
+    },
+    {
+        "value": "20.03_LTS",
+        "name": "20.03 LTS",
+        "docs": [
+            {
+                "title": "了解",
+                "doc": [
+                    {
+                        "img": "/img/docs/docs-releasenotes.svg",
+                        "path": "/docs/Releasenotes/release_notes.html",
+                        "name": "发行说明"
+                    }
+                ]
+            },
+            {
+                "title": "安装",
+                "doc": [
+                    {
+                        "img": "/img/docs/docs-quickstart.svg",
+                        "path": "/docs/Quickstart/quick-start.html",
+                        "name": "快速入门"
+                    },
+                    {
+                        "img": "/img/docs/docs-installation.svg",
+                        "path": "/docs/Installation/installation.html",
+                        "name": "安装指南"
+                    }
+                ]
+            },
+            {
+                "title": "管理",
+                "doc": [
+                    {
+                        "img": "/img/docs/docs-administration.svg",
+                        "path": "/docs/Administration/administration.html",
+                        "name": "管理员指南"
+                    }
+                ]
+            },
+            {
+                "title": "使用",
+                "doc": [
+                    {
+                        "img": "/img/docs/docs-user.svg",
+                        "path": "/docs/Virtualization/virtualization.html",
+                        "name": "虚拟化用户指南"
+                    },
+                    {
+                        "img": "/img/docs/docs-user.svg",
+                        "path": "/docs/Container/container.html",
+                        "name": "容器用户指南"
+                    },
+                    {
+                        "img": "/img/docs/docs-user.svg",
+                        "path": "/docs/A-Tune/A-Tune.html",
+                        "name": "A-Tune用户指南"
+                    }
+                ]
+            },
+            {
+                "title": "开发",
+                "doc": [
+                    {
+                        "img": "/img/docs/docs-application.svg",
+                        "path": "/docs/ApplicationDev/application-development.html",
+                        "name": "应用开发指南"
+                    }
+                ]
+            }
+        ]
+    }
+]
\ No newline at end of file
diff --git a/docs/zh/documentation/README.md b/docs/zh/documentation/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..032ef7ef2e950bb2c56ae61a4b7854d665ddebbf
--- /dev/null
+++ b/docs/zh/documentation/README.md
@@ -0,0 +1,6 @@
+---
+title: "文档"
+---
+
+  
+
\ No newline at end of file
diff --git a/package.json b/package.json
new file mode 100644
index 0000000000000000000000000000000000000000..4e85cf8d689964a53fa8621a3ed53526c8fd56b8
--- /dev/null
+++ b/package.json
@@ -0,0 +1,18 @@
+{
+  "name": "website-v2",
+  "version": "0.0.1",
+  "description": "",
+  "main": "index.js",
+  "scripts": {
+    "dev": "vuepress dev docs",
+    "build": "vuepress build docs"
+  },
+  "keywords": [],
+  "author": "",
+  "license": "",
+  "dependencies": {
+    "element-ui": "^2.13.2",
+    "less-loader": "^6.2.0",
+    "vuepress": "^1.5.2"
+  }
+}
diff --git a/rdocs/en/openEuler 1.0 Installation Guide.pdf b/rdocs/en/openEuler 1.0 Installation Guide.pdf
deleted file mode 100644
index 7a6a2cdb852d5f2502e13b5b8ce46a915072410f..0000000000000000000000000000000000000000
Binary files a/rdocs/en/openEuler 1.0 Installation Guide.pdf and /dev/null differ
diff --git a/rdocs/en/openEuler 20.03 LTS A-Tune User Guide.pdf b/rdocs/en/openEuler 20.03 LTS A-Tune User Guide.pdf
deleted file mode 100644
index c5a43911b4fa7839ab5f5eb0bc38818c8bb8b34a..0000000000000000000000000000000000000000
Binary files a/rdocs/en/openEuler 20.03 LTS A-Tune User Guide.pdf and /dev/null differ
diff --git a/rdocs/en/openEuler 20.03 LTS Administrator Guide.pdf b/rdocs/en/openEuler 20.03 LTS Administrator Guide.pdf
deleted file mode 100644
index 2039b90984988ae4c8e0214ebd9f033fd8490ebd..0000000000000000000000000000000000000000
Binary files a/rdocs/en/openEuler 20.03 LTS Administrator Guide.pdf and /dev/null differ
diff --git a/rdocs/en/openEuler 20.03 LTS Application Development Guide.pdf b/rdocs/en/openEuler 20.03 LTS Application Development Guide.pdf
deleted file mode 100644
index 5c132a743d2c7b3a27c15397c7c3acdebc8a8d1e..0000000000000000000000000000000000000000
Binary files a/rdocs/en/openEuler 20.03 LTS Application Development Guide.pdf and /dev/null differ
diff --git a/rdocs/en/openEuler 20.03 LTS Container User Guide.pdf b/rdocs/en/openEuler 20.03 LTS Container User Guide.pdf
deleted file mode 100644
index 79804395bd8605d0e1566405e066b66b911aff6c..0000000000000000000000000000000000000000
Binary files a/rdocs/en/openEuler 20.03 LTS Container User Guide.pdf and /dev/null differ
diff --git a/rdocs/en/openEuler 20.03 LTS Installation Guide.pdf b/rdocs/en/openEuler 20.03 LTS Installation Guide.pdf
deleted file mode 100644
index 9e72c47cae20bb7f523d4423d1c87c492a1a9d51..0000000000000000000000000000000000000000
Binary files a/rdocs/en/openEuler 20.03 LTS Installation Guide.pdf and /dev/null differ
diff --git a/rdocs/en/openEuler 20.03 LTS Release Description.pdf b/rdocs/en/openEuler 20.03 LTS Release Description.pdf
deleted file mode 100644
index 0efe706b9efd66f89a25d84ad6fdb037ef341e06..0000000000000000000000000000000000000000
Binary files a/rdocs/en/openEuler 20.03 LTS Release Description.pdf and /dev/null differ
diff --git a/rdocs/en/openEuler 20.03 LTS Virtualization User Guide.pdf b/rdocs/en/openEuler 20.03 LTS Virtualization User Guide.pdf
deleted file mode 100644
index 45b7a82a4f2e40d6fa1f145e7fce50c8a9b91a7f..0000000000000000000000000000000000000000
Binary files a/rdocs/en/openEuler 20.03 LTS Virtualization User Guide.pdf and /dev/null differ
diff --git "a/rdocs/zh/date20200101/openEuler 1.0 \345\256\211\350\243\205\346\214\207\345\215\227.pdf" "b/rdocs/zh/date20200101/openEuler 1.0 \345\256\211\350\243\205\346\214\207\345\215\227.pdf"
deleted file mode 100644
index 576eb0a1f8cdcffd68ec60df3dce8c0e729f8e7f..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/date20200101/openEuler 1.0 \345\256\211\350\243\205\346\214\207\345\215\227.pdf" and /dev/null differ
diff --git "a/rdocs/zh/date20200101/openEuler 1.0 \347\256\241\347\220\206\345\221\230\346\214\207\345\215\227.pdf" "b/rdocs/zh/date20200101/openEuler 1.0 \347\256\241\347\220\206\345\221\230\346\214\207\345\215\227.pdf"
deleted file mode 100644
index 032fae106298bef8d9f3dc2381c478904fd0236a..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/date20200101/openEuler 1.0 \347\256\241\347\220\206\345\221\230\346\214\207\345\215\227.pdf" and /dev/null differ
diff --git "a/rdocs/zh/date20200101/openEuler 1.0 \350\231\232\346\213\237\345\214\226\347\224\250\346\210\267\346\214\207\345\215\227.pdf" "b/rdocs/zh/date20200101/openEuler 1.0 \350\231\232\346\213\237\345\214\226\347\224\250\346\210\267\346\214\207\345\215\227.pdf"
deleted file mode 100644
index 5c9df30f521b0b5adf71044b7e87de4018b610b8..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/date20200101/openEuler 1.0 \350\231\232\346\213\237\345\214\226\347\224\250\346\210\267\346\214\207\345\215\227.pdf" and /dev/null differ
diff --git "a/rdocs/zh/date20200115/openEuler 1.0 \345\256\211\350\243\205\346\214\207\345\215\227.pdf" "b/rdocs/zh/date20200115/openEuler 1.0 \345\256\211\350\243\205\346\214\207\345\215\227.pdf"
deleted file mode 100644
index b6e6ddd880a473f80821501031441927b99712f3..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/date20200115/openEuler 1.0 \345\256\211\350\243\205\346\214\207\345\215\227.pdf" and /dev/null differ
diff --git "a/rdocs/zh/date20200115/openEuler 1.0 \347\211\210\346\234\254\345\217\221\350\241\214\350\257\264\346\230\216.pdf" "b/rdocs/zh/date20200115/openEuler 1.0 \347\211\210\346\234\254\345\217\221\350\241\214\350\257\264\346\230\216.pdf"
deleted file mode 100644
index 639ab676d80da674b1edc47480cbacd3b590a2ff..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/date20200115/openEuler 1.0 \347\211\210\346\234\254\345\217\221\350\241\214\350\257\264\346\230\216.pdf" and /dev/null differ
diff --git "a/rdocs/zh/date20200115/openEuler 1.0 \347\256\241\347\220\206\345\221\230\346\214\207\345\215\227.pdf" "b/rdocs/zh/date20200115/openEuler 1.0 \347\256\241\347\220\206\345\221\230\346\214\207\345\215\227.pdf"
deleted file mode 100644
index 6bf63ab9e446c95e194af64ecf7308abc3ba74e2..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/date20200115/openEuler 1.0 \347\256\241\347\220\206\345\221\230\346\214\207\345\215\227.pdf" and /dev/null differ
diff --git "a/rdocs/zh/date20200115/openEuler 1.0 \350\231\232\346\213\237\345\214\226\347\224\250\346\210\267\346\214\207\345\215\227.pdf" "b/rdocs/zh/date20200115/openEuler 1.0 \350\231\232\346\213\237\345\214\226\347\224\250\346\210\267\346\214\207\345\215\227.pdf"
deleted file mode 100644
index be501ab13eee41e6cba3070ab220c0e9a47cbfdf..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/date20200115/openEuler 1.0 \350\231\232\346\213\237\345\214\226\347\224\250\346\210\267\346\214\207\345\215\227.pdf" and /dev/null differ
diff --git "a/rdocs/zh/date20200207Base/openEuler 1.0 Base \347\211\210\346\234\254\345\217\221\350\241\214\350\257\264\346\230\216.pdf" "b/rdocs/zh/date20200207Base/openEuler 1.0 Base \347\211\210\346\234\254\345\217\221\350\241\214\350\257\264\346\230\216.pdf"
deleted file mode 100644
index c766d7b2eaf6da74e8fc525b595d5bb826b45774..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/date20200207Base/openEuler 1.0 Base \347\211\210\346\234\254\345\217\221\350\241\214\350\257\264\346\230\216.pdf" and /dev/null differ
diff --git "a/rdocs/zh/date20200207Base/openEuler 1.0 \345\256\211\350\243\205\346\214\207\345\215\227.pdf" "b/rdocs/zh/date20200207Base/openEuler 1.0 \345\256\211\350\243\205\346\214\207\345\215\227.pdf"
deleted file mode 100644
index 15bf70973654b6207c6921b5e58756aac752f638..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/date20200207Base/openEuler 1.0 \345\256\211\350\243\205\346\214\207\345\215\227.pdf" and /dev/null differ
diff --git "a/rdocs/zh/date20200207Base/openEuler 1.0 \345\256\271\345\231\250\347\224\250\346\210\267\346\214\207\345\215\227.pdf" "b/rdocs/zh/date20200207Base/openEuler 1.0 \345\256\271\345\231\250\347\224\250\346\210\267\346\214\207\345\215\227.pdf"
deleted file mode 100644
index 41141857a5e3251a251f8e2cc3d17d1a3dea0525..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/date20200207Base/openEuler 1.0 \345\256\271\345\231\250\347\224\250\346\210\267\346\214\207\345\215\227.pdf" and /dev/null differ
diff --git "a/rdocs/zh/date20200207Base/openEuler 1.0 \347\256\241\347\220\206\345\221\230\346\214\207\345\215\227.pdf" "b/rdocs/zh/date20200207Base/openEuler 1.0 \347\256\241\347\220\206\345\221\230\346\214\207\345\215\227.pdf"
deleted file mode 100644
index 9069a0f35cec4d4876826af08d71223f4790ce91..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/date20200207Base/openEuler 1.0 \347\256\241\347\220\206\345\221\230\346\214\207\345\215\227.pdf" and /dev/null differ
diff --git "a/rdocs/zh/date20200207Base/openEuler 1.0 \350\231\232\346\213\237\345\214\226\347\224\250\346\210\267\346\214\207\345\215\227.pdf" "b/rdocs/zh/date20200207Base/openEuler 1.0 \350\231\232\346\213\237\345\214\226\347\224\250\346\210\267\346\214\207\345\215\227.pdf"
deleted file mode 100644
index f42bf90865210637e48a83cecc6d427cf726035d..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/date20200207Base/openEuler 1.0 \350\231\232\346\213\237\345\214\226\347\224\250\346\210\267\346\214\207\345\215\227.pdf" and /dev/null differ
diff --git "a/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS A-Tune\347\224\250\346\210\267\346\214\207\345\215\227.pdf" "b/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS A-Tune\347\224\250\346\210\267\346\214\207\345\215\227.pdf"
deleted file mode 100644
index e1b232819ded604e5156ba01f582bd2563e0f91f..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS A-Tune\347\224\250\346\210\267\346\214\207\345\215\227.pdf" and /dev/null differ
diff --git "a/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \345\215\207\347\272\247\346\214\207\345\257\274\344\271\246.pdf" "b/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \345\215\207\347\272\247\346\214\207\345\257\274\344\271\246.pdf"
deleted file mode 100644
index 04e04bb92dcdc7265fa18e147d1bd1c857bf1426..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \345\215\207\347\272\247\346\214\207\345\257\274\344\271\246.pdf" and /dev/null differ
diff --git "a/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \345\256\211\350\243\205\346\214\207\345\215\227.pdf" "b/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \345\256\211\350\243\205\346\214\207\345\215\227.pdf"
deleted file mode 100644
index 6c2b9eef6dea506d9cc731b4aa83054a3163e45c..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \345\256\211\350\243\205\346\214\207\345\215\227.pdf" and /dev/null differ
diff --git "a/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \345\256\271\345\231\250\347\224\250\346\210\267\346\214\207\345\215\227.pdf" "b/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \345\256\271\345\231\250\347\224\250\346\210\267\346\214\207\345\215\227.pdf"
deleted file mode 100644
index ce957156f9c572455eaa16eb7f627258d7244cb4..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \345\256\271\345\231\250\347\224\250\346\210\267\346\214\207\345\215\227.pdf" and /dev/null differ
diff --git "a/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \345\272\224\347\224\250\345\274\200\345\217\221\346\214\207\345\215\227.pdf" "b/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \345\272\224\347\224\250\345\274\200\345\217\221\346\214\207\345\215\227.pdf"
deleted file mode 100644
index 7b120d4c9d07fbd2822b457b233c55e57d4cc4c3..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \345\272\224\347\224\250\345\274\200\345\217\221\346\214\207\345\215\227.pdf" and /dev/null differ
diff --git "a/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \347\211\210\346\234\254\345\217\221\350\241\214\350\257\264\346\230\216.pdf" "b/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \347\211\210\346\234\254\345\217\221\350\241\214\350\257\264\346\230\216.pdf"
deleted file mode 100644
index 39fcb1398029a87f3c2d499a9bbf1643f34e2f17..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \347\211\210\346\234\254\345\217\221\350\241\214\350\257\264\346\230\216.pdf" and /dev/null differ
diff --git "a/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \347\256\241\347\220\206\345\221\230\346\214\207\345\215\227.pdf" "b/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \347\256\241\347\220\206\345\221\230\346\214\207\345\215\227.pdf"
deleted file mode 100644
index 262ef388677ae150e2062085396e1aed6e1235c9..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \347\256\241\347\220\206\345\221\230\346\214\207\345\215\227.pdf" and /dev/null differ
diff --git "a/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \350\231\232\346\213\237\345\214\226\347\224\250\346\210\267\346\214\207\345\215\227.pdf" "b/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \350\231\232\346\213\237\345\214\226\347\224\250\346\210\267\346\214\207\345\215\227.pdf"
deleted file mode 100644
index 072b911c841e83f70865a171eb7df99f4357b874..0000000000000000000000000000000000000000
Binary files "a/rdocs/zh/openEuler 20.03 LTS_20200324/openEuler 20.03 LTS \350\231\232\346\213\237\345\214\226\347\224\250\346\210\267\346\214\207\345\215\227.pdf" and /dev/null differ
diff --git a/themes/project/.travis.yml b/themes/project/.travis.yml
deleted file mode 100644
index baaea454a3f0e7ee7f045783d88f4c10add3e56e..0000000000000000000000000000000000000000
--- a/themes/project/.travis.yml
+++ /dev/null
@@ -1,2 +0,0 @@
-language: generic
-script: docker run --rm -it -v $(pwd)/exampleSite:/src -v $(pwd):/src/themes/hugo-book klakegg/hugo:ext-alpine --enableGitInfo=false
diff --git a/themes/project/LICENSE b/themes/project/LICENSE
deleted file mode 100644
index e7a669ab2fdc6f7401b8472af82b0444db0ec8ed..0000000000000000000000000000000000000000
--- a/themes/project/LICENSE
+++ /dev/null
@@ -1,20 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2018 Alex Shpak
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the "Software"), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
-the Software, and to permit persons to whom the Software is furnished to do so,
-subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
-FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
-COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
-IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
-CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
diff --git a/themes/project/README.md b/themes/project/README.md
deleted file mode 100644
index 35f45040833b81f824c6a27836a57a88e765049d..0000000000000000000000000000000000000000
--- a/themes/project/README.md
+++ /dev/null
@@ -1,275 +0,0 @@
-# Hugo Book Theme
-
-[![Build Status](https://travis-ci.org/alex-shpak/hugo-book.svg?branch=master)](https://travis-ci.org/alex-shpak/hugo-book)
-[![Hugo](https://img.shields.io/badge/hugo-0.55-blue.svg)](https://gohugo.io)
-[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
-
-### [Hugo](https://gohugo.io) documentation theme as simple as plain book
-
-![Screenshot](https://github.com/alex-shpak/hugo-book/blob/master/images/screenshot.png)
-
-- [Features](#features)
-- [Installation](#installation)
-- [Menu](#menu)
-- [Configuration](#configuration)
-- [Shortcodes](#shortcodes)
-- [Contributing](#contributing)
-
-## Features
-
-- Clean simple design
-- Mobile friendly
-- Customisable
-- Designed to not interfere with other layouts
-- Zero initial configuration
-- Handy shortcodes
-
-## Requirements
-
-- Hugo 0.55 or higher
-- Hugo extended version, read more [here](https://gohugo.io/news/0.48-relnotes/)
-
-## Installation
-
-Navigate to your hugo project root and run:
-
-```
-git submodule add https://github.com/alex-shpak/hugo-book themes/book
-```
-
-Then run hugo (or set `theme = "book"`/`theme: book` in configuration file)
-
-```
-hugo server --minify --theme book
-```
-
-### Creating site from scratch
-
-Below is example how to create new site from scratch
-
-```sh
-hugo new site mydocs; cd mydocs
-git init
-git submodule add https://github.com/alex-shpak/hugo-book themes/book
-cp -R themes/book/exampleSite/content .
-```
-
-```sh
-hugo server --minify --theme book
-```
-
-## Menu
-
-### File tree menu (default)
-
-By default theme will render pages from `content/docs` section as menu in a tree structure.  
-You can set `title` and `weight` in front matter of pages to adjust order and titles in menu.
-
-### Leaf bundle menu
-
-You can also use leaf bundle and content of it's `index.md` as menu.  
-Given you have this file structure
-
-```
-├── content
-│   ├── docs
-│   │   ├── page-one.md
-│   │   └── page-two.md
-│   └── posts
-│       ├── post-one.md
-│       └── post-two.md
-```
-
-Create file `content/docs/menu/index.md` with content
-
-```md
-+++
-headless = true
-+++
-
-- [Book Example](/docs/)
-  - [Page One](/docs/page-one)
-  - [Page Two](/docs/page-two)
-- [Blog](/posts)
-```
-
-And Enable it by settings `BookMenuBundle: /menu` in Site configuration
-
-- [Example menu](https://github.com/alex-shpak/hugo-book/blob/master/exampleSite/content/menu/index.md)
-- [Example config file](https://github.com/alex-shpak/hugo-book/blob/master/exampleSite/config.yaml)
-- [Leaf bundles](https://gohugo.io/content-management/page-bundles/)
-
-## Blog
-
-Simple blog supported for section `posts`
-
-## Configuration
-
-### Site Configuration
-
-There are few configuration options you can add to your `config.toml` file.  
-You can also see `yaml` example [here](https://github.com/alex-shpak/hugo-book/blob/master/exampleSite/config.yaml).
-
-```toml
-# (Optional) Set this to true if you use capital letters in file names
-disablePathToLower = true
-
-# (Optional) Set this to true to enable 'Last Modified by' date and git author
-#  information on 'doc' type pages.
-enableGitInfo = true
-
-# (Optional) Theme is intended for documentation use, therefore it doesn't render taxonomy.
-# You can remove related files with config below
-disableKinds = ['taxonomy', 'taxonomyTerm']
-
-[params]
-# (Optional, default 6) Set how many table of contents levels to be showed on page.
-# Use false to hide ToC, note that 0 will default to 6 (https://gohugo.io/functions/default/)
-# You can also specify this parameter per page in front matter
-BookToC = 3
-
-# (Optional, default none) Set leaf bundle to render as side menu
-# When not specified file structure and weights will be used
-BookMenuBundle = '/menu'
-
-# (Optional, default docs) Specify section of content to render as menu
-# You can also set value to "*" to render all sections to menu
-BookSection = 'docs'
-
-# (Optional) This value is duplicate of $link-color for making active link highlight in menu bundle mode
-# BookMenuBundleActiveLinkColor = '\#004ed0'
-
-# Set source repository location.
-# Used for 'Last Modified' and 'Edit this page' links.
-BookRepo = 'https://github.com/alex-shpak/hugo-book'
-
-# Enable 'Edit this page' links for 'doc' page type.
-# Disabled by default. Uncomment to enable. Requires 'BookRepo' param.
-# Path must point to 'content' directory of repo.
-BookEditPath = 'edit/master/exampleSite/content'
-
-# (Optional, default January 2, 2006) Configure the date format used on the pages
-# - In git information
-# - In blog posts
-BookDateFormat = 'Jan 2, 2006'
-
-# (Optional, default true) Enables search function with lunr.js, 
-# Index is built on fly, therefore it might slowdown your website.
-BookSearch = true
-```
-
-### Page Configuration
-
-You can specify additional params per page in front matter
-
-```toml
-# Set type to 'docs' if you want to render page outside of configured section or if you render section other than 'docs'
-type = 'docs'
-
-# Set page weight to re-arrange items in file-tree menu (if BookMenuBundle not set)
-weight = 10
-
-# (Optional) Set to mark page as flat section in file-tree menu (if BookMenuBundle not set)
-bookFlatSection = true
-
-# (Optional) Set true to hide page or section from side menu (if BookMenuBundle not set)
-bookHidden = true
-
-# (Optional) Set how many levels of ToC to show. use 'false' to hide ToC completely
-bookToC = 3
-```
-
-### Partials
-
-There are few empty partials you can override in `layouts/partials/`
-
-| Partial                                         | Placement                              |
-| ----------------------------------------------- | -------------------------------------- |
-| `layouts/partials/docs/inject/head.html`        | Before closing `` tag            |
-| `layouts/partials/docs/inject/body.html`        | Before closing `` tag            |
-| `layouts/partials/docs/inject/footer.html`      | After page content                     |
-| `layouts/partials/docs/inject/menu-before.html` | At the beginning of `