diff --git a/translation-projects/README-optimization/optimized-README/EulerRobot.README.en.md b/translation-projects/README-optimization/optimized-README/EulerRobot.README.en.md new file mode 100644 index 0000000000000000000000000000000000000000..3a5540cd88a53444122506664bba901907a64b0e --- /dev/null +++ b/translation-projects/README-optimization/optimized-README/EulerRobot.README.en.md @@ -0,0 +1,84 @@ +# EulerRobot + +#### Introduction + +A virtualized automated test project, integrated compilation test, UT test, smoke test, Avocado-VT test,etc. + +#### Description + +- **Service for virtualized components developer** + + Developers can conduct compiling of virtualized components' own branch code, address sanitizing compiling, UT test (including qemu-ut, libvirt-ut, kvm-unit-test), static check and other verifications. Now, qemu and libvirt are available, and can be used to connect to openEuler and upstream. + +- **Service for smoke testing and integration testing of virtualized components** + + You can run smoke testing and integration testing with designated versions, and replace qemu in the running environment with the address sanitization version delivered with openEuler or upstream qemu. + +- **Service for performance testing of virtualized components** + + It provides virtualized benchmark performance testing, including cpu, mem and io. It also provides a performance test model for openEuler virtualization scenarios for a fast performance verification of a designated version. + +- **Service for other DFX testing** + + Subsequently, there will be more services for testing, including UZZ, semantic search and reliability. + +#### Software Architecture + +Based on various virtualized test suits and testing capability, EulerRobot can be conneted to compass-ci in order to provide a virtualized platform for users to verify services.![EulerRobot架构](https://gitee.com/openeuler/EulerRobot/raw/master/docs/design/EulerRobot-architecture.png) + +Test suite sites of relevant virtualization platforms are as follows: + + + + + + + + + +#### Installation + +1. With a compass-ci account, users should be qualified with submitting tasks via compass-ci. For more specific, please refer to . +2. Users should downloads EulerRobot repository and run scrip/autopatch.sh to copy the files to lkp-tests directory. + +#### Instructions + +1. Service for developers + + jobs/openEuler-qemu.yaml - this task provides qemu version compilation, UT test and cppcheck static check. It also supports the configuration of address sanitization compilation, and the compilation of different branches integrated by designated upstream and openEuler. + + jobs/openEuler-libvirt.yaml - this task provides libvirt version compilation and UT test. It also supports the compilation of different branches integrated by upstream and openEuler. + +2. Service for smoking and integration test + + jobs/virttest-depends.yaml - this task needs to be performed before virttest_at/virttest_st. It also builds a dep package of rpm that the test framework and test cases rely on for proper operation. + + jobs/virttest-makepkg.yaml - this task needs to be performed before virttest_at/virttest_st. It also builds a pkg package that runs before test framework deployment and test case deployment. It supports the building of qemu address sanitization version. + + jobs/virttest_at.yaml - this task runs virtualized smoking test in a single-physical host test environment. It also supports the configuration of address sanitization version running on openEuler integrated qemu and upstream qemu. + + jobs/virttest_at_2hosts.yaml - this task runs virtualization test in double-physical host test environment. It also supports the configuration of address sanitization version running on openEuler integrated qemu and upstream qemu. + + jobs/virttest_st.yaml - this task runs virtualization integrated test in a single-physical host test environment. It also supports the configuration of address sanitization version running on openEuler integrated qemu and upstream qemu. + + jobs/virttest_st_2hosts.yaml - this task runs virtualization integrated test in a double-physical host test environment. It also supports the configuration of address sanitization version running on openEuler integrated qemu and upstream qemu. + +3. service for performance test + + To be supplemented. + +#### Contribution + +1. Fork the repository +2. Create Feat_xxx branch +3. Commit your code +4. Create Pull Request + +#### Gitee Feature + +1. You can use Readme_XXX.md to support different languages, such as Readme_en.md, Readme_zh.md +2. Gitee blog [blog.gitee.com](https://blog.gitee.com) +3. Explore open source project +4. The most valuable open source project [GVP](https://gitee.com/gvp) +5. The manual of Gitee +6. The most popular members \ No newline at end of file diff --git a/translation-projects/README-optimization/optimized-README/docs.README.en.md b/translation-projects/README-optimization/optimized-README/docs.README.en.md new file mode 100644 index 0000000000000000000000000000000000000000..7f1198e893c2eca2acf0844d6774d0e61e6fa0fb --- /dev/null +++ b/translation-projects/README-optimization/optimized-README/docs.README.en.md @@ -0,0 +1,62 @@ +# openEuler DOCS + +English | [简体中文](https://gitee.com/openeuler/docs/blob/master/README.md) + +### Introduction + +DOCS contains all documents of the openEuler community, including the release notes, OS installation guide, administrator guide, virtualization and container guide, A-Tune user guide and application development guide and so forth. + +### Searching for a Document in DOCS + +Open the **docs** 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: + +| folder | Guides | +| ------------------ | -------------------------------------- | +| **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* | +| **SecHarden** | *Security Hardening Guide* | +| **Virtualization** | *Virtualization Application Guide* | +| **userGuide** | *openEuler Toolset User Guide* | +| **StratoVirt** | *StratoVirt Virtualization User Guide* | + +### Modifying a Document + +When the openEuler version information is updated, the documents herein also need to be updated. Thank you for providing updates. Please read [information development process guide](https://gitee.com/lss410313/docs/wikis/Home) for a reference. + +### Checking the Relationship Between Versions and Branches + +The DOCS contains the following four branches: + +| Branch | Description | Documentation | +| --------------------- | ------------------------------------------------- | ------------------------------------------------------------ | +| **master** | development branch, as well as the default branch | | +| **stable2-1.0_Base** | 1.0 Base version branch | **DOCS** > **1.0 BASE** on the [openEuler community website](https://openeuler.org/) | +| **stable2-20.03_LTS** | 20.03 LTS version branch | **DOCS** > **20.03 LTS** on the [openEuler community website](https://openeuler.org/) | +| **stable2-20.09** | 20.09 version branch | **DOCS** > **20.09** 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. You can read [pull-request submit guide](https://gitee.com/openeuler/community/blob/master/zh/contributors/pull-request.md) for a reference. + Submit comments: You can submit comments on issues or PRs. You can also comment on the document through **Feedback** on the website document page. + +We are always pleased to receive PRs from you. + +### Member + +#### Maintainer List + +- Rudy_Tan[@rudy_tan](https://gitee.com/rudy_tan) +- amyMaYun[@amy_mayun](https://gitee.com/amy_mayun) +- qiaominna[@qiaominna](https://gitee.com/qiaominna) + +### Contacting Us + +E-mails: [doc@openeuler.org](mailto:doc@openeuler.org) + IRC: #openeuler-doc \ No newline at end of file diff --git a/translation-projects/README-optimization/translated-README/community-issue.README.en.md b/translation-projects/README-optimization/translated-README/community-issue.README.en.md new file mode 100644 index 0000000000000000000000000000000000000000..12ee5e3d25e8023c8e238e386db1756db163e6dc --- /dev/null +++ b/translation-projects/README-optimization/translated-README/community-issue.README.en.md @@ -0,0 +1,25 @@ +# openEuler Issue + +[English](./README.md) | Chinese + +### Introduction + +With many projects in openEuler, it is not easy to decide projects that submit problems to openEuler. + +This repository is to accept these problems. + +### Usage Scenario + +If you are uncertain to where to put your problem, please click here. + +If you find problems in opening this repository, you should track or restore them in this repository. + +If you find problems in other repositories, please open the problems in respective areas; then make comments on new problems and request closure here. + +### Maintainer + +- freesky-edward + +### Attention + +Please do not open any Pull Request in this repository. \ No newline at end of file