diff --git a/locale/zh_CN/LC_MESSAGES/FAQ/index.po b/locale/zh_CN/LC_MESSAGES/FAQ/index.po index 34438207..c5e6bbdf 100644 --- a/locale/zh_CN/LC_MESSAGES/FAQ/index.po +++ b/locale/zh_CN/LC_MESSAGES/FAQ/index.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: Clear Linux* Project Docs latest\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-09 14:33-0700\n" +"POT-Creation-Date: 2019-08-29 17:26-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -197,30 +197,54 @@ msgid "" msgstr "" #: ../../FAQ/index.rst:136 -msgid "Is FFmpeg available?" +msgid "Is Microsoft\\* Visual Studio Code\\* available?" msgstr "" #: ../../FAQ/index.rst:138 msgid "" +"Yes. Find the CLI command for installing `VS Code`_ and other FlatPak " +"apps in the `software store`_. Installing FlatPak apps is also covered in" +" our :ref:`tutorial `." +msgstr "" + +#: ../../FAQ/index.rst:142 +msgid "" +"The |CL| team is working on a natively packaged version of Visual Studio " +"Code for future release." +msgstr "" + +#: ../../FAQ/index.rst:145 +msgid "" +"Join a community forum discussion about manually installing and " +"maintaining Visual Studio Code: https://community.clearlinux.org/t/need-" +"native-support-for-vs-code-through-swupd/" +msgstr "" + +#: ../../FAQ/index.rst:153 +msgid "Is FFmpeg available?" +msgstr "" + +#: ../../FAQ/index.rst:155 +msgid "" "`FFmpeg`_ is a multimedia software suite, which is commonly used for " "various media encoding/decoding, streaming, and playback." msgstr "" -#: ../../FAQ/index.rst:141 +#: ../../FAQ/index.rst:158 msgid "" "|CL| does not distribute FFmpeg due to well-known licensing and legal " "complexities (See https://www.ffmpeg.org/legal.html and " "http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html)." msgstr "" -#: ../../FAQ/index.rst:145 +#: ../../FAQ/index.rst:162 msgid "" "Read more in the |CL| repository, including discussion of an alternative " "hardware-based solution: " "https://github.com/clearlinux/distribution/issues/429." msgstr "" -#: ../../FAQ/index.rst:149 +#: ../../FAQ/index.rst:166 msgid "" "While |CL| cannot distribute FFmpeg, a manual solution to build and " "install FFmpeg under :file:`/usr/local` has been shared on the community " @@ -228,29 +252,29 @@ msgid "" "firefox-including-ffmpeg-install." msgstr "" -#: ../../FAQ/index.rst:156 +#: ../../FAQ/index.rst:173 msgid "Is ZFS\\* available?" msgstr "" -#: ../../FAQ/index.rst:158 +#: ../../FAQ/index.rst:175 msgid "" "ZFS is not available with |CL| because of copyright and licensing " "complexities. BTRFS is an alternative filesystem that is available in " "|CL| natively." msgstr "" -#: ../../FAQ/index.rst:162 +#: ../../FAQ/index.rst:179 msgid "" "A user on GitHub notes that the ZFS kernel module can be compiled, built," " and installed manually: " "https://github.com/clearlinux/distribution/issues/631" msgstr "" -#: ../../FAQ/index.rst:168 +#: ../../FAQ/index.rst:185 msgid "Can you add a driver that I need?" msgstr "" -#: ../../FAQ/index.rst:170 +#: ../../FAQ/index.rst:187 msgid "" "If a kernel module is available as part of the Linux kernel source tree " "but not enabled in the |CL| kernels, in many cases the |CL| team will " @@ -258,7 +282,7 @@ msgid "" "https://github.com/clearlinux/distribution/issues" msgstr "" -#: ../../FAQ/index.rst:175 +#: ../../FAQ/index.rst:192 msgid "" "The |CL| team does not typically add out-of-tree kernel modules as a " "matter of practice because of the maintenance overhead. If the driver was" @@ -266,7 +290,7 @@ msgid "" " merge it for similar reasons." msgstr "" -#: ../../FAQ/index.rst:180 +#: ../../FAQ/index.rst:197 msgid "" "Kernel modules can be individually built and installed on |CL|. See the " ":ref:`kernel modules ` page for more information." diff --git a/locale/zh_CN/LC_MESSAGES/get-started/cloud-install/aws-web.po b/locale/zh_CN/LC_MESSAGES/get-started/cloud-install/aws-web.po index 9e3370a7..7472cb0f 100644 --- a/locale/zh_CN/LC_MESSAGES/get-started/cloud-install/aws-web.po +++ b/locale/zh_CN/LC_MESSAGES/get-started/cloud-install/aws-web.po @@ -5,17 +5,19 @@ # FIRST AUTHOR , 2019. # msgid "" -msgstr "Project-Id-Version: Clear Linux* Project Docs latest\n" +msgstr "" +"Project-Id-Version: Clear Linux* Project Docs latest\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-09 14:33-0700\n" -"PO-Revision-Date: 2019-08-29 15:49-0008\n" +"POT-Creation-Date: 2019-08-29 17:26-0700\n" +"PO-Revision-Date: 2019-08-29 15:49-0152\n" "Last-Translator: FULL NAME \n" +"Language: zh_Hans\n" "Language-Team: zh-Hans\n" +"Plural-Forms: nplurals=1; plural=0\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Intel® International Developer Studio Version 4.1.273.0\n" -"Language: zh-Hans\n" +"Generated-By: Babel 2.7.0\n" #: ../../get-started/cloud-install/aws-web.rst:4 msgid "|CL-ATTR| on Amazon Web Services\\*" @@ -26,7 +28,9 @@ msgid "" "This tutorial explains how to create and launch a |CL| :abbr:`AMI (Amazon" " Machine Image)` instance from the :abbr:`AWS\\* (Amazon Web Services)` " "console and complete the following tasks:" -msgstr "本教程介绍如何通过 :abbr:`AWS\\* (Amazon Web Services)` 控制台创建和启动 |CL| :abbr:`AMI (Amazon Machine Image)` 实例以及完成以下任务:" +msgstr "" +"本教程介绍如何通过 :abbr:`AWS\\* (Amazon Web Services)` 控制台创建和启动 |CL| :abbr:`AMI " +"(Amazon Machine Image)` 实例以及完成以下任务:" #: ../../get-started/cloud-install/aws-web.rst:10 msgid "Locate and select the |CL| OS Basic AMI in the AWS Marketplace." @@ -81,7 +85,9 @@ msgid "" "This tutorial uses a |CL| AMI t2.micro instance that is eligible for the " "AWS free tier. To learn more about AWS and setting up an account, visit " "the AWS website at http://aws.amazon.com." -msgstr "本教程使用有资格享受 AWS 免费套餐的 |CL| AMI t2.micro 实例。要了解有关 AWS 和设置帐户的更多信息,请访问 AWS 网站,网址为:http://aws.amazon.com。" +msgstr "" +"本教程使用有资格享受 AWS 免费套餐的 |CL| AMI t2.micro 实例。要了解有关 AWS 和设置帐户的更多信息,请访问 AWS " +"网站,网址为:http://aws.amazon.com。" #: ../../get-started/cloud-install/aws-web.rst:39 msgid "Locate, select, and launch the |CL| Basic AMI" @@ -105,7 +111,9 @@ msgstr "选择此选项将调出 :guilabel:`EC2 Dashboard` 菜单。" msgid "" "To create a new |CL| instance from the :guilabel:`EC2 Dashboard` menu, " "select the :guilabel:`Launch Instance` button as shown in Figure 2:" -msgstr "要从 :guilabel:`EC2 Dashboard` 菜单创建新的 |CL| 实例,请选择图 2 中所示的 :guilabel:`Launch Instance` 按钮:" +msgstr "" +"要从 :guilabel:`EC2 Dashboard` 菜单创建新的 |CL| 实例,请选择图 2 中所示的 :guilabel:`Launch" +" Instance` 按钮:" #: ../../get-started/cloud-install/aws-web.rst:59 msgid "Figure 2: :guilabel:`EC2 Dashboard`" @@ -121,26 +129,34 @@ msgstr "选择此选项将转到 :guilabel:`Step 1: Choose an Amazon Machine Ima msgid "" "To find the :guilabel:`Clear Linux OS Basic` AMI in the :guilabel:`Step " "1: Choose an Amazon Machine Image (AMI)` menu, do the following:" -msgstr "要在 :guilabel:`Step 1: Choose an Amazon Machine Image (AMI)` 菜单中找到 :guilabel:`Clear Linux OS Basic` AMI,请执行以下操作:" +msgstr "" +"要在 :guilabel:`Step 1: Choose an Amazon Machine Image (AMI)` 菜单中找到 " +":guilabel:`Clear Linux OS Basic` AMI,请执行以下操作:" #: ../../get-started/cloud-install/aws-web.rst:68 msgid "" "In the lefthand navigation window, select the :guilabel:`AWS Marketplace`" " menu item to bring up the search bar to :guilabel:`Search AWS " "Marketplace Products`." -msgstr "在左侧导航窗口中,选择 :guilabel:`AWS Marketplace` 菜单项以调出搜索栏并转到 :guilabel:`Search AWS Marketplace Products`。" +msgstr "" +"在左侧导航窗口中,选择 :guilabel:`AWS Marketplace` 菜单项以调出搜索栏并转到 :guilabel:`Search " +"AWS Marketplace Products`。" #: ../../get-started/cloud-install/aws-web.rst:72 msgid "" "In the search bar, type \"clear linux os\" and press the :kbd:`Enter` key" " to search for and locate the :guilabel:`Clear Linux OS Basic` AMI." -msgstr "在搜索栏中键入 \"clear linux os\" 并按 :kbd:`Enter` 键,以搜索并找到 :guilabel:`Clear Linux OS Basic` AMI。" +msgstr "" +"在搜索栏中键入 \"clear linux os\" 并按 :kbd:`Enter` 键,以搜索并找到 :guilabel:`Clear " +"Linux OS Basic` AMI。" #: ../../get-started/cloud-install/aws-web.rst:75 msgid "" "Select the :guilabel:`Clear Linux OS Basic` AMI by clicking the " ":guilabel:`Select` button as shown in Figure 3:" -msgstr "通过点击图 3 中所示的 :guilabel:`Select` 按钮,选择 :guilabel:`Clear Linux OS Basic` AMI:" +msgstr "" +"通过点击图 3 中所示的 :guilabel:`Select` 按钮,选择 :guilabel:`Clear Linux OS Basic` " +"AMI:" #: ../../get-started/cloud-install/aws-web.rst:82 msgid "Figure 3: :guilabel:`Step 1: Choose AMI`" @@ -152,7 +168,9 @@ msgid "" ":guilabel:`Clear Linux OS Basic` AMI along with the pricing details for " "running |CL| on different platform configurations as shown in Figure 4. " "Select the :guilabel:`Continue` button." -msgstr "此时将出现一个弹出对话框,其中显示有关 :guilabel:`Clear Linux OS Basic` AMI 的更多信息以及使用图 4 中所示的不同平台配置运行 |CL| 的定价详细信息。选择 :guilabel:`Continue` 按钮。" +msgstr "" +"此时将出现一个弹出对话框,其中显示有关 :guilabel:`Clear Linux OS Basic` AMI 的更多信息以及使用图 4 " +"中所示的不同平台配置运行 |CL| 的定价详细信息。选择 :guilabel:`Continue` 按钮。" #: ../../get-started/cloud-install/aws-web.rst:93 msgid "Figure 4: :guilabel:`Clear Linux OS Basic`" @@ -171,14 +189,18 @@ msgid "" "Select the :guilabel:`t2.micro` type by clicking the box on the left side" " of the instance and then select the :guilabel:`Review and Launch` button" " to move to the :guilabel:`Step 7: Review the Instance Launch` menu." -msgstr "通过点击实例左侧的框来选择 :guilabel:`t2.micro` 类型,然后选择 :guilabel:`Review and Launch` 按钮以转到 :guilabel:`Step 7: Review the Instance Launch` 菜单。" +msgstr "" +"通过点击实例左侧的框来选择 :guilabel:`t2.micro` 类型,然后选择 :guilabel:`Review and Launch` " +"按钮以转到 :guilabel:`Step 7: Review the Instance Launch` 菜单。" #: ../../get-started/cloud-install/aws-web.rst:109 msgid "" "You can configure the instance details, add additional storage, add tags," " and configure the security group before selecting the :guilabel:`Review " "and Launch` button if you want to further customize this |CL| instance." -msgstr "如果要进一步自定义该 |CL| 实例,您可以在选择 :guilabel:`Review and Launch` 按钮之前配置实例详细信息,添加其他存储,添加标记以及配置安全组。" +msgstr "" +"如果要进一步自定义该 |CL| 实例,您可以在选择 :guilabel:`Review and Launch` " +"按钮之前配置实例详细信息,添加其他存储,添加标记以及配置安全组。" #: ../../get-started/cloud-install/aws-web.rst:114 msgid "" @@ -186,7 +208,10 @@ msgid "" "6, allows you to :guilabel:`Cancel` the process, return to the " ":guilabel:`Previous` screen to change the configuration or " ":guilabel:`Launch` the instance defined." -msgstr "图 6 中所示的 :guilabel:`Step 7: Review the Instance Launch` 菜单可用于 :guilabel:`Cancel` 进程,以及返回到 :guilabel:`Previous` 屏幕以更改配置,或者可用于 :guilabel:`Launch` 已定义的实例。" +msgstr "" +"图 6 中所示的 :guilabel:`Step 7: Review the Instance Launch` 菜单可用于 " +":guilabel:`Cancel` 进程,以及返回到 :guilabel:`Previous` 屏幕以更改配置,或者可用于 " +":guilabel:`Launch` 已定义的实例。" #: ../../get-started/cloud-install/aws-web.rst:123 msgid "Figure 6: :guilabel:`Step 7: Review the Instance Launch`" @@ -197,7 +222,9 @@ msgid "" "Select the :guilabel:`Launch` button. A dialog box appears, as shown in " "Figure 7, asking you to :guilabel:`Select an existing key pair or create " "a new pair`." -msgstr "选择 :guilabel:`Launch` 按钮。此时将出现图 7 中所示的对话框,要求您 :guilabel:`Select an existing key pair or create a new pair`。" +msgstr "" +"选择 :guilabel:`Launch` 按钮。此时将出现图 7 中所示的对话框,要求您 :guilabel:`Select an " +"existing key pair or create a new pair`。" #: ../../get-started/cloud-install/aws-web.rst:133 msgid "Figure 7: :guilabel:`Select an existing key pair or create a new pair`" @@ -216,14 +243,18 @@ msgid "" "Select the :guilabel:`Download Key Pair` button to download the " ":file:`AWSClearTestKey.pem` to your browser's defined :file:`Downloads` " "directory." -msgstr "选择 :guilabel:`Download Key Pair` 按钮,以将 :file:`AWSClearTestKey.pem` 下载到浏览器中定义的 :file:`Downloads` 目录。" +msgstr "" +"选择 :guilabel:`Download Key Pair` 按钮,以将 :file:`AWSClearTestKey.pem` " +"下载到浏览器中定义的 :file:`Downloads` 目录。" #: ../../get-started/cloud-install/aws-web.rst:143 msgid "" "When the file finishes downloading, select the :guilabel:`Launch " "Instances` button to proceed to the :guilabel:`Launch Status` menu shown " "in Figure 8." -msgstr "文件下载完成后,选择 :guilabel:`Launch Instances` 按钮以转到图 8 中所示的 :guilabel:`Launch Status` 菜单。" +msgstr "" +"文件下载完成后,选择 :guilabel:`Launch Instances` 按钮以转到图 8 中所示的 :guilabel:`Launch " +"Status` 菜单。" #: ../../get-started/cloud-install/aws-web.rst:151 msgid "Figure 8: :guilabel:`Launch Status`" @@ -234,14 +265,16 @@ msgid "" "Once the :guilabel:`Launch Status` page changes to what is shown in " "Figure 9, select the :guilabel:`View Instances` button to view your " ":guilabel:`Instances` dashboard." -msgstr " :guilabel:`Launch Status` 页面变为图 9 中所示的页面后,选择 :guilabel:`View Instances` 按钮以显示 :guilabel:`Instances` 仪表板。" +msgstr "" +" :guilabel:`Launch Status` 页面变为图 9 中所示的页面后,选择 :guilabel:`View Instances` " +"按钮以显示 :guilabel:`Instances` 仪表板。" #: ../../get-started/cloud-install/aws-web.rst:161 msgid "Figure 9: :guilabel:`View Instance`" msgstr "图 9: :guilabel:`View Instance`" #: ../../get-started/cloud-install/aws-web.rst:164 -msgid "Connect to your Clear Linux* OS basic instance" +msgid "Connect to your Clear Linux OS basic instance" msgstr "连接到 Clear Linux* 操作系统基本实例" #: ../../get-started/cloud-install/aws-web.rst:166 @@ -250,7 +283,9 @@ msgid "" "|CL| OS basic instance already selected and in the running state. If " "there are other instances available, they are also listed but not " "selected." -msgstr "图 10 中显示了 :guilabel:`Instances` 仪表板和已选择并处于运行状态的新的 |CL| 操作系统基本实例。同时也会显示其他可用的实例(如有),但不会选择这些实例。" +msgstr "" +"图 10 中显示了 :guilabel:`Instances` 仪表板和已选择并处于运行状态的新的 |CL| " +"操作系统基本实例。同时也会显示其他可用的实例(如有),但不会选择这些实例。" #: ../../get-started/cloud-install/aws-web.rst:174 msgid "Figure 10: :guilabel:`Instance Dashboard`" @@ -262,7 +297,9 @@ msgid "" " located at the top of your dashboard. AWS brings up the pop-up dialog " "box shown in Figure 11 describing how to connect to your running " "instance." -msgstr "要连接到正在运行的实例,请点击位于仪表板顶部的 :guilabel:`Connect` 按钮。AWS 将调出图 11 中显示的弹出对话框,该对话框说明了如何连接到正在运行的实例。" +msgstr "" +"要连接到正在运行的实例,请点击位于仪表板顶部的 :guilabel:`Connect` 按钮。AWS 将调出图 11 " +"中显示的弹出对话框,该对话框说明了如何连接到正在运行的实例。" #: ../../get-started/cloud-install/aws-web.rst:186 msgid "Figure 11: :guilabel:`Connect to Your Instance`" @@ -285,7 +322,9 @@ msgid "" "Change the attributes of the :file:`AWSClearTestKey.pem` using the " ":command:`chmod` command as instructed in the dialog box shown in Figure " "11." -msgstr "按照图 11 中显示的对话框中的说明使用 :command:`chmod` 命令更改 :file:`AWSClearTestKey.pem` 的属性。" +msgstr "" +"按照图 11 中显示的对话框中的说明使用 :command:`chmod` 命令更改 :file:`AWSClearTestKey.pem` " +"的属性。" #: ../../get-started/cloud-install/aws-web.rst:206 msgid "" @@ -293,7 +332,10 @@ msgid "" "shown in :ref:`figure 11`. Paste the copied text into " "your terminal, change the text before the `@` sign to the username " "`clear`, and press the :kbd:`Enter` key to execute the command." -msgstr "复制 :ref:`图 11` 中显示的 :guilabel:`Example:` 一节中突出显示的文本。将复制的文本粘贴到终端中,将 `@` 符号前面的文本更改为用户名 `clear`,然后按 :kbd:`Enter` 键以执行命令。" +msgstr "" +"复制 :ref:`图 11` 中显示的 :guilabel:`Example:` " +"一节中突出显示的文本。将复制的文本粘贴到终端中,将 `@` 符号前面的文本更改为用户名 `clear`,然后按 :kbd:`Enter` " +"键以执行命令。" #: ../../get-started/cloud-install/aws-web.rst:215 msgid "" @@ -336,7 +378,9 @@ msgid "" "using the :guilabel:`Instances` dashboard to stop accruing charges. " "Complete the following steps from the :guilabel:`Instances` dashboard to " "stop your AWS |CL| instance from running." -msgstr "完成使用 AWS |CL| 实例后,您必须使用 :guilabel:`Instances` 仪表板停止该实例以使费用停止增加。从 :guilabel:`Instances` 仪表板完成以下步骤以使 AWS |CL| 实例停止运行。" +msgstr "" +"完成使用 AWS |CL| 实例后,您必须使用 :guilabel:`Instances` 仪表板停止该实例以使费用停止增加。从 " +":guilabel:`Instances` 仪表板完成以下步骤以使 AWS |CL| 实例停止运行。" #: ../../get-started/cloud-install/aws-web.rst:255 msgid "Select the :guilabel:`Actions` button to bring up a pull-down menu." @@ -374,7 +418,9 @@ msgid "" "Congratulations! You are up and running with |CL| on AWS. To see what you" " can do with your |CL| instance, visit our :ref:`tutorials ` " "section for examples on using your |CL| system." -msgstr "恭喜!您已启动并运行基于 AWS 的 |CL|。要查看可对 |CL| 实例执行的操作,请参见 :ref:`教程` 一节了解有关使用 |CL| 系统的示例。" +msgstr "" +"恭喜!您已启动并运行基于 AWS 的 |CL|。要查看可对 |CL| 实例执行的操作,请参见 :ref:`教程` " +"一节了解有关使用 |CL| 系统的示例。" #~ msgid "Create and launch |CL-ATTR| from Amazon Web Services" #~ msgstr "" @@ -518,4 +564,3 @@ msgstr "恭喜!您已启动并运行基于 AWS 的 |CL|。要查看可对 |CL| #~ "your AWS |CL| instance from running." #~ msgstr "" - diff --git a/locale/zh_CN/LC_MESSAGES/guides/clear/telemetrics.po b/locale/zh_CN/LC_MESSAGES/guides/clear/telemetrics.po index a01a6265..ca0975b4 100644 --- a/locale/zh_CN/LC_MESSAGES/guides/clear/telemetrics.po +++ b/locale/zh_CN/LC_MESSAGES/guides/clear/telemetrics.po @@ -5,18 +5,19 @@ # FIRST AUTHOR , 2019. # msgid "" -msgstr "Project-Id-Version: Clear Linux* Project Docs latest\n" +msgstr "" +"Project-Id-Version: Clear Linux* Project Docs latest\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-09 14:33-0700\n" -"PO-Revision-Date: 2019-08-29 15:49-0008\n" +"POT-Creation-Date: 2019-08-29 17:26-0700\n" +"PO-Revision-Date: 2019-08-29 15:49-0152\n" "Last-Translator: FULL NAME \n" -"Language: zh-Hans\n" +"Language: zh_Hans\n" "Language-Team: zh-Hans\n" "Plural-Forms: nplurals=2; plural=(n != 1)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Intel® International Developer Studio Version 4.1.273.0\n" +"Generated-By: Babel 2.7.0\n" #: ../../guides/clear/telemetrics.rst:4 msgid "Telemetrics" @@ -34,52 +35,57 @@ msgstr "|CL| 中的遥测为 **opt-in**。遥测客户端未处于活动状态 #: ../../guides/clear/telemetrics.rst:15 msgid "" -"The telemetry functionality adheres to `Intel privacy policies`_ " -"regarding the collection and use of :abbr:`PII (Personally Identifiable " -"Information)` and is open source." -msgstr "遥测功能遵从涉及收集和使用 :abbr:`PII (Personally Identifiable Information)` 的 `英特尔隐私条款 `_,同时也是开源功能。" +"The telemetry functionality adheres to `Intel privacy policies " +"`_ regarding the collection and use of :abbr:`PII (Personally" +" Identifiable Information)` and is open source." +msgstr "" +"遥测功能遵从涉及收集和使用 :abbr:`PII (Personally Identifiable Information)` 的 " +"`英特尔隐私条款 `_,同时也是开源功能。" - -#: ../../guides/clear/telemetrics.rst:19 +#: ../../guides/clear/telemetrics.rst:18 msgid "" "No intentionally identifiable information about the user or system owner " "is collected." msgstr "系统不会蓄意收集涉及用户或系统所有者的可识别身份的信息。" -#: ../../guides/clear/telemetrics.rst:27 +#: ../../guides/clear/telemetrics.rst:26 msgid "Overview" msgstr "概述" -#: ../../guides/clear/telemetrics.rst:29 +#: ../../guides/clear/telemetrics.rst:28 msgid "" "Telemetrics in |CL| is a client and server solution used to collect data " "from running |CL| systems to help quickly identify and fix bugs in the " "OS. Both client and server are customizable, and an API is available on " "the client side for instrumenting your code for debug and analysis." -msgstr "|CL| 中的遥测是用于收集来自正在运行的 |CL| 系统的数据的客户端/服务器解决方案,有助于快速确定和修复操作系统中的错误。客户端和服务器均可定制,而客户端则可使用 API 检测代码,进行调试和分析。" +msgstr "" +"|CL| 中的遥测是用于收集来自正在运行的 |CL| " +"系统的数据的客户端/服务器解决方案,有助于快速确定和修复操作系统中的错误。客户端和服务器均可定制,而客户端则可使用 API " +"检测代码,进行调试和分析。" - -#: ../../guides/clear/telemetrics.rst:34 +#: ../../guides/clear/telemetrics.rst:33 msgid "" "Telemetry, one of the key features of |CL|, enables developers to observe" " and proactively address issues in the OS before end users are impacted." msgstr "借助遥测这一 |CL| 的主要功能,开发人员可在最终用户受到影响之前观察并主动解决操作系统中存在的问题。" -#: ../../guides/clear/telemetrics.rst:37 +#: ../../guides/clear/telemetrics.rst:36 msgid "Telemetrics is a combination word made from:" msgstr "遥测 (Telemetrics) 是由以下项组成的组合词:" -#: ../../guides/clear/telemetrics.rst:39 +#: ../../guides/clear/telemetrics.rst:38 msgid "Telemetry, which is sensing and reporting data." msgstr "遥测 (Telemetry),即感知和报告数据。" -#: ../../guides/clear/telemetrics.rst:40 +#: ../../guides/clear/telemetrics.rst:39 msgid "" "Analytics, which is using visualization and statistical inferencing to " "make sense of the reported data." msgstr "分析 (Analytics),即使用可视化和统计推理探究报告数据的意义。" -#: ../../guides/clear/telemetrics.rst:43 +#: ../../guides/clear/telemetrics.rst:42 msgid "" "|CL| telemetry reports system-level debug/crash information using " "specialized probes. The probes monitor system tasks such as swupd, kernel" @@ -87,111 +93,113 @@ msgid "" "unhandled hardware failures. Telemetry enables real-time issue reporting " "to allow system developers to focus quickly on an issue and monitor " "corrective actions." -msgstr "|CL| 遥测使用专用探针来报告系统级调试/崩溃信息。探针可监控系统任务,例如 swupd、内核 oops、机器错误检查以及未处理硬件故障的 BIOS 错误报告表。遥测可以实时报告问题,以便系统开发人员快速关注问题并监控更正措施。" +msgstr "" +"|CL| 遥测使用专用探针来报告系统级调试/崩溃信息。探针可监控系统任务,例如 swupd、内核 oops、机器错误检查以及未处理硬件故障的 " +"BIOS 错误报告表。遥测可以实时报告问题,以便系统开发人员快速关注问题并监控更正措施。" - -#: ../../guides/clear/telemetrics.rst:49 +#: ../../guides/clear/telemetrics.rst:48 msgid "" "|CL| telemetry is fully customizable and can be used during software " "development for debugging purposes. You can use the libtelemetry library " "in your code to create custom telemetry records. You can also use the " "telem-record-gen utility in script files for light-touch record creation " "where instrumenting code files doesn't make sense." -msgstr "|CL| 遥测支持完全定制,可在软件开发期间用于调试。可以在代码中使用 libtelemetry 库来创建定制遥测记录。还可以在脚本文件中使用 telem-record-gen 实用程序创建轻触记录,其中检测代码文件并无作用。" +msgstr "" +"|CL| 遥测支持完全定制,可在软件开发期间用于调试。可以在代码中使用 libtelemetry 库来创建定制遥测记录。还可以在脚本文件中使用 " +"telem-record-gen 实用程序创建轻触记录,其中检测代码文件并无作用。" - -#: ../../guides/clear/telemetrics.rst:55 +#: ../../guides/clear/telemetrics.rst:54 msgid "" "The |CL| telemetrics solution is an **opt-in** choice on the client side." " By default, the telemetry client is disabled until you choose to enable " "it. Enabling the client is covered in this guide." msgstr "|CL| 遥测解决方案是客户端上的一个选择启用选项。默认情况下,禁用遥测客户端,直到用户选择将其启用。本指南介绍如何启用客户端。" -#: ../../guides/clear/telemetrics.rst:60 +#: ../../guides/clear/telemetrics.rst:59 msgid "Architecture" msgstr "体系架构" -#: ../../guides/clear/telemetrics.rst:62 +#: ../../guides/clear/telemetrics.rst:61 msgid "" "|CL| telemetry has two fundamental components, which are shown in Figure " "1:" msgstr "|CL| 遥测有两大基本组件,如图 1 所示:" -#: ../../guides/clear/telemetrics.rst:64 +#: ../../guides/clear/telemetrics.rst:63 msgid "" "Client: generates and delivers records to the backend server via the " "network." msgstr "客户端:通过网络生成记录并将其传送到后端服务器。" -#: ../../guides/clear/telemetrics.rst:66 +#: ../../guides/clear/telemetrics.rst:65 msgid "" "Backend: receives records sent from the client and displays the " "cumulative content through a specialized web interface." msgstr "后端:接收客户端发来的记录,通过专门的 Web 界面显示累积的内容。" -#: ../../guides/clear/telemetrics.rst:72 +#: ../../guides/clear/telemetrics.rst:71 msgid "Figure 1: :guilabel:`|CL| Telemetry Architecture`" msgstr "图 1: :guilabel:`|CL| Telemetry Architecture`" -#: ../../guides/clear/telemetrics.rst:74 +#: ../../guides/clear/telemetrics.rst:73 msgid "" "The telemetry client provides the front end of the telemetrics solution " "and includes the following components:" msgstr "遥测客户端提供遥测解决方案的前端,同时还包括以下组件:" -#: ../../guides/clear/telemetrics.rst:77 +#: ../../guides/clear/telemetrics.rst:76 msgid "" "telemprobd, which is a daemon that receives and prepares telemetry " "records from probes and spools them to disk." msgstr "telemprobd 是一个守护程序,用于接收并准备探针的遥测记录,并将其假脱机至磁盘。" -#: ../../guides/clear/telemetrics.rst:79 +#: ../../guides/clear/telemetrics.rst:78 msgid "" "telempostd, which is a daemon that manages spooled telemetry records and " "delivers these records according to configurable settings." msgstr "telempostd 是一个守护程序,根据可配置设置管理假脱机的遥测记录并提供这些记录。" -#: ../../guides/clear/telemetrics.rst:81 +#: ../../guides/clear/telemetrics.rst:80 msgid "probes, which collect specific types of data from the operating system." msgstr "probes,从操作系统收集特定类型的数据。" -#: ../../guides/clear/telemetrics.rst:82 +#: ../../guides/clear/telemetrics.rst:81 msgid "" "libtelemetry, which is the API that telemetrics probes use to create " "records." msgstr "libtelemetry,遥测探针用于创建记录的 API。" -#: ../../guides/clear/telemetrics.rst:84 +#: ../../guides/clear/telemetrics.rst:83 msgid "" "The telemetry backend provides the server-side component of the " "telemetrics solution and consists of:" msgstr "遥测后端提供遥测解决方案的服务器端组件且包括:" -#: ../../guides/clear/telemetrics.rst:87 +#: ../../guides/clear/telemetrics.rst:86 msgid "Nginx web server." msgstr "Nginx Web 服务器。" -#: ../../guides/clear/telemetrics.rst:88 +#: ../../guides/clear/telemetrics.rst:87 msgid "Two Flask apps:" msgstr "两个 Flask 应用:" -#: ../../guides/clear/telemetrics.rst:90 +#: ../../guides/clear/telemetrics.rst:89 msgid "" "Collector, which is an ingestion web app for records received from client" " probes." msgstr "Collector,针对从客户端探针所接收记录的接入式网络应用。" -#: ../../guides/clear/telemetrics.rst:92 +#: ../../guides/clear/telemetrics.rst:91 msgid "" "TelemetryUI, which is a web app that exposes different views to visualize" " the telemetry data." msgstr "TelemetryUI,通过不同视图实现遥测数据可视化的网络应用。" -#: ../../guides/clear/telemetrics.rst:94 +#: ../../guides/clear/telemetrics.rst:93 msgid "PostgreSQL as the underlying database server." msgstr "PostgreSQL 作为底层数据库服务器。" -#: ../../guides/clear/telemetrics.rst:98 +#: ../../guides/clear/telemetrics.rst:97 msgid "" "The default telemetry backend server is hosted by the Intel |CL| " "development team and is not viewable outside the Intel firewall. To " @@ -199,11 +207,11 @@ msgid "" "server." msgstr "默认遥测后端服务器由英特尔 |CL| 开发团队托管,且无法在英特尔防火墙之外查看。要收集个人记录,必须设置自己的遥测后端服务器。" -#: ../../guides/clear/telemetrics.rst:103 +#: ../../guides/clear/telemetrics.rst:102 msgid "How to use" msgstr "使用方法" -#: ../../guides/clear/telemetrics.rst:105 +#: ../../guides/clear/telemetrics.rst:104 msgid "" "From a workflow perspective, the |CL| telemetrics system is " "straightforward. On the client side, the main decisions after " @@ -212,25 +220,26 @@ msgid "" "custom backend server, keep the data local to the system, or both. The " "backend server has a more complex setup, but once it's running, it is " "simple to use and configure." -msgstr "从工作流角度来看,|CL| 遥测系统非常简单。在客户端,安装和启用遥测技术之后的主要决策涉及如何处理探针生成的记录数据。可以将数据发送到默认或定制后端服务器,也可将此数据保留在系统本地,或同时执行二者。后端服务器的设置更为复杂,但一旦运行,它就极易使用和配置。" +msgstr "" +"从工作流角度来看,|CL| " +"遥测系统非常简单。在客户端,安装和启用遥测技术之后的主要决策涉及如何处理探针生成的记录数据。可以将数据发送到默认或定制后端服务器,也可将此数据保留在系统本地,或同时执行二者。后端服务器的设置更为复杂,但一旦运行,它就极易使用和配置。" - -#: ../../guides/clear/telemetrics.rst:112 +#: ../../guides/clear/telemetrics.rst:111 msgid "" "This section describes some of the possible scenarios for configuring the" " |CL| telemetrics system, and suggests which ones make sense according to" " your needs." msgstr "本节介绍配置 |CL| 遥测系统的部分潜在场景,并根据需求提供有意义的建议。" -#: ../../guides/clear/telemetrics.rst:117 +#: ../../guides/clear/telemetrics.rst:116 msgid "Scenarios" msgstr "场景" -#: ../../guides/clear/telemetrics.rst:119 +#: ../../guides/clear/telemetrics.rst:118 msgid "Enable telemetry:" msgstr "启用遥测技术:" -#: ../../guides/clear/telemetrics.rst:121 +#: ../../guides/clear/telemetrics.rst:120 msgid "" "Before probes can generate records, the telemetry client daemons must be " "enabled. You can configure the client before enabling by creating a " @@ -238,14 +247,16 @@ msgid "" ":file:`/etc/telemetrics` directory. If you choose to use the default " "settings, records will be sent to the telemetrics backend server managed " "by the |CL| development team at Intel." -msgstr "必须启用遥测客户端守护程序,探针才能生成记录。创建定制 :file:`telemetrics.conf` 文件,将其存储在 :file:`/etc/telemetrics` 目录中,可以在启用前配置客户端。如果选择使用默认设置,则会将记录发送到英特尔 |CL| 开发团队所管理的遥测后端服务器。" +msgstr "" +"必须启用遥测客户端守护程序,探针才能生成记录。创建定制 :file:`telemetrics.conf` 文件,将其存储在 " +":file:`/etc/telemetrics` 目录中,可以在启用前配置客户端。如果选择使用默认设置,则会将记录发送到英特尔 |CL| " +"开发团队所管理的遥测后端服务器。" - -#: ../../guides/clear/telemetrics.rst:128 +#: ../../guides/clear/telemetrics.rst:127 msgid "Save record data locally:" msgstr "本地保存记录数据:" -#: ../../guides/clear/telemetrics.rst:130 +#: ../../guides/clear/telemetrics.rst:129 msgid "" "You can configure the telemetry client to save records locally. This is " "convenient when you want instant feedback during a development cycle, or " @@ -254,46 +265,49 @@ msgid "" "keep the records locally and send to the backend server." msgstr "可以配置遥测客户端,在本地保存记录。在开发周期中需要即时反馈或是认为存在特定于计算机的问题以便跟踪系统问题时,此功能非常方便。可以将客户端设为完全不发送记录,或是将记录保存在本地并发送到后端服务器。" -#: ../../guides/clear/telemetrics.rst:136 +#: ../../guides/clear/telemetrics.rst:135 msgid "Set up a server to collect data:" msgstr "设置服务器以收集数据:" -#: ../../guides/clear/telemetrics.rst:138 +#: ../../guides/clear/telemetrics.rst:137 msgid "" "Whether you are managing a network of |CL| systems or you don't want to " "send records to the default telemetry server, you can set up a backend " "server to collect your records. The backend server can be installed on " "any Linux system and provides the same dashboard as the default server." -msgstr "无论是管理 |CL| 系统网络,还是不想将记录发送到默认遥测服务器,均可设置后端服务器来收集个人记录。后端服务器可安装在任意 Linux 系统上,并为您提供与默认服务器相同的控制台。" +msgstr "" +"无论是管理 |CL| 系统网络,还是不想将记录发送到默认遥测服务器,均可设置后端服务器来收集个人记录。后端服务器可安装在任意 Linux " +"系统上,并为您提供与默认服务器相同的控制台。" - -#: ../../guides/clear/telemetrics.rst:144 +#: ../../guides/clear/telemetrics.rst:143 msgid "Instrument your code with the libtelemetry API:" msgstr "通过 libtelemetry API 检测代码:" -#: ../../guides/clear/telemetrics.rst:146 +#: ../../guides/clear/telemetrics.rst:145 msgid "" "The :command:`telemetrics` bundle includes the libtelemetry C library, " "which exposes an API used by the telemprobd and telempostd daemons. You " "can use these in your applications as well. The API documentation is " "found in the :file:`telemetry.h` file in `Telemetrics client`_ " "repository." -msgstr ":command:`telemetrics` bundle 文件包括 libtelemetry C 库,可以提供 telemprobd 和 telempostd 守护程序所用的 API。同时,也可以在应用程序中使用这些守护程序。相关 API 文档位于 `Telemetrics client`_ 存储库的 :file:`telemetry.h` 文件中。" +msgstr "" +":command:`telemetrics` bundle 文件包括 libtelemetry C 库,可以提供 telemprobd 和 " +"telempostd 守护程序所用的 API。同时,也可以在应用程序中使用这些守护程序。相关 API 文档位于 `Telemetrics " +"client`_ 存储库的 :file:`telemetry.h` 文件中。" - -#: ../../guides/clear/telemetrics.rst:153 +#: ../../guides/clear/telemetrics.rst:152 msgid "Examples" msgstr "示例" -#: ../../guides/clear/telemetrics.rst:160 +#: ../../guides/clear/telemetrics.rst:159 msgid "Enable or disable telemetry" msgstr "启用或禁用遥测" -#: ../../guides/clear/telemetrics.rst:162 +#: ../../guides/clear/telemetrics.rst:161 msgid "Enabling during installation:" msgstr "在安装期间启用:" -#: ../../guides/clear/telemetrics.rst:164 +#: ../../guides/clear/telemetrics.rst:163 msgid "" "During the initial installation of |CL|, you are requested to join the " "stability enhancement program and allow |CL| to collect anonymous reports" @@ -301,18 +315,19 @@ msgid "" "then the telemetry software bundle is not added to your system. Choosing " "to join will automatically enable telemetry on your system after " "installation is complete." -msgstr "在初始安装 |CL| 期间,系统会要求加入稳定性增强计划,允许 |CL| 收集匿名报告,提高系统稳定性。如果选择不加入此计划,则不会将遥测软件 bundle 文件添加到系统中。选择加入此计划,则会在安装完成后自动在系统上启用遥测技术。" +msgstr "" +"在初始安装 |CL| 期间,系统会要求加入稳定性增强计划,允许 |CL| 收集匿名报告,提高系统稳定性。如果选择不加入此计划,则不会将遥测软件 " +"bundle 文件添加到系统中。选择加入此计划,则会在安装完成后自动在系统上启用遥测技术。" - -#: ../../guides/clear/telemetrics.rst:171 +#: ../../guides/clear/telemetrics.rst:170 msgid "Enabling after install:" msgstr "安装后启用:" -#: ../../guides/clear/telemetrics.rst:173 +#: ../../guides/clear/telemetrics.rst:172 msgid "To start telemetry on your system, run the following command:" msgstr "要在系统上启动遥测,请运行以下命令:" -#: ../../guides/clear/telemetrics.rst:179 +#: ../../guides/clear/telemetrics.rst:178 msgid "" "This enables and starts the :command:`telemprobd` and " ":command:`telempostd` daemons. Your system will begin to send telemetry " @@ -320,69 +335,73 @@ msgid "" ":file:`/etc/telemetrics/telemetrics.conf`. If this file does not exist, " "the :command:`telemprobd` and :command:`telempostd` daemons will use the " "file :file:`/usr/share/defaults/telemetrics/telemetrics.conf`." -msgstr "此命令将启用并启动 :command:`telemprobd` 和 :command:`telempostd` 守护程序。系统随即开始将遥测数据发送到文件 :file:`/etc/telemetrics/telemetrics.conf` 中所定义的服务器。如果此文件不存在,:command:`telemprobd` 和 :command:`telempostd` 守护程序则会使用文件 :file:`/usr/share/defaults/telemetrics/telemetrics.conf`。" +msgstr "" +"此命令将启用并启动 :command:`telemprobd` 和 :command:`telempostd` " +"守护程序。系统随即开始将遥测数据发送到文件 :file:`/etc/telemetrics/telemetrics.conf` " +"中所定义的服务器。如果此文件不存在,:command:`telemprobd` 和 :command:`telempostd` " +"守护程序则会使用文件 :file:`/usr/share/defaults/telemetrics/telemetrics.conf`。" - -#: ../../guides/clear/telemetrics.rst:185 +#: ../../guides/clear/telemetrics.rst:184 msgid "Disabling after install:" msgstr "安装后禁用:" -#: ../../guides/clear/telemetrics.rst:187 +#: ../../guides/clear/telemetrics.rst:186 msgid "To disable both of the telemetry daemons, run the following command:" msgstr "要禁用这两个遥测守护程序,请运行以下命令:" -#: ../../guides/clear/telemetrics.rst:193 +#: ../../guides/clear/telemetrics.rst:192 msgid "Opt in to telemetry:" msgstr "选择启用遥测技术:" -#: ../../guides/clear/telemetrics.rst:195 +#: ../../guides/clear/telemetrics.rst:194 msgid "" "To opt-in to the telemetry services, simply enter the opt-in command, " "which also starts the service:" msgstr "要选择启用遥测服务,只需输入选择启用命令,也会启动服务:" -#: ../../guides/clear/telemetrics.rst:202 +#: ../../guides/clear/telemetrics.rst:201 msgid "" "This removes the :file:`/etc/telemetrics/opt-out` file, if it exists, and" " starts the telemetry services." msgstr "此操作将删除 :file:`/etc/telemetrics/opt-out` 文件(如果存在)并启动遥测服务。" -#: ../../guides/clear/telemetrics.rst:207 +#: ../../guides/clear/telemetrics.rst:206 msgid "" "To opt-in but not immediately start telemetry services, you must run the " "command :command:`sudo telemctl stop` after the :command:`opt-in` command" " is entered. Once you are ready to start the service, enter the command " ":command:`sudo telemctl start`." -msgstr "要选择启用而非立即启动遥测服务,则需在输入 :command:`opt-in` 命令后运行命令 :command:`sudo telemctl stop`。准备好启动服务后,输入命令 :command:`sudo telemctl start`。" +msgstr "" +"要选择启用而非立即启动遥测服务,则需在输入 :command:`opt-in` 命令后运行命令 :command:`sudo telemctl " +"stop`。准备好启动服务后,输入命令 :command:`sudo telemctl start`。" - -#: ../../guides/clear/telemetrics.rst:212 +#: ../../guides/clear/telemetrics.rst:211 msgid "Opt out of telemetry:" msgstr "选择禁用遥测技术:" -#: ../../guides/clear/telemetrics.rst:214 +#: ../../guides/clear/telemetrics.rst:213 msgid "" "To stop sending telemetrics data from your system, opt out of the " "telemetry service:" msgstr "要停止发送来自系统的遥测数据,请选择禁用遥测服务:" -#: ../../guides/clear/telemetrics.rst:221 +#: ../../guides/clear/telemetrics.rst:220 msgid "" "This creates the file :file:`/etc/telemetrics/opt-out` and stops the " "telemetry services." msgstr "此操作将创建文件 :file:`/etc/telemetrics/opt-out` 并停止遥测服务。" -#: ../../guides/clear/telemetrics.rst:226 +#: ../../guides/clear/telemetrics.rst:225 msgid "Saving data locally" msgstr "本地保存数据" -#: ../../guides/clear/telemetrics.rst:228 +#: ../../guides/clear/telemetrics.rst:227 msgid "" "This example requires |CL| to be installed and telemetry to be enabled on" " the system." msgstr "本例要求安装 |CL| 并在系统上启用遥测技术。" -#: ../../guides/clear/telemetrics.rst:231 +#: ../../guides/clear/telemetrics.rst:230 msgid "" "To change how records are managed, copy the default " ":file:`/usr/share/defaults/telemetrics/telemetrics.conf` file to " @@ -393,184 +412,199 @@ msgid "" ":file:`/etc`. For each example, and for any time you make changes to the " "configuration file, you must restart the client daemons to pick up the " "changes:" -msgstr "要更改记录的管理方式,请将默认的 :file:`/usr/share/defaults/telemetrics/telemetrics.conf` 文件复制到 :file:`/etc/telemetrics/telemetrics.conf` 并对其进行编辑。:file:`/etc/telemetrics/telemetrics.conf` 文件中的更改会覆盖 :file:`/usr/share/defaults/telemetrics/telemetrics.conf` 文件中的默认值。您可能需要 root 权限才能在 :file:`/etc` 中创建和编辑文件。在每个示例中,每次对配置文件进行更改时,均需重新启动客户端守护程序才能接受更改:" +msgstr "" +"要更改记录的管理方式,请将默认的 :file:`/usr/share/defaults/telemetrics/telemetrics.conf`" +" 文件复制到 :file:`/etc/telemetrics/telemetrics.conf` " +"并对其进行编辑。:file:`/etc/telemetrics/telemetrics.conf` 文件中的更改会覆盖 " +":file:`/usr/share/defaults/telemetrics/telemetrics.conf` 文件中的默认值。您可能需要 " +"root 权限才能在 :file:`/etc` 中创建和编辑文件。在每个示例中,每次对配置文件进行更改时,均需重新启动客户端守护程序才能接受更改:" - -#: ../../guides/clear/telemetrics.rst:245 +#: ../../guides/clear/telemetrics.rst:244 msgid "" "The :command:`telemctl journal` command gives you access to features and " "options of the telemetry journal to assist with system analytics and " "debug. :command:`telemctl journal` has a number of options to help filter" " records. Use :command:`-h` or :command:`--help` to view usage options." -msgstr "使用 :command:`telemctl journal` 命令可以访问遥测日志的各项功能和选项,有助于进行系统分析和调试。:command:`telemctl journal` 提供众多选项来协助过滤记录。使用 :command:`-h` 或 :command:`--help` 查看使用情况选项。" +msgstr "" +"使用 :command:`telemctl journal` " +"命令可以访问遥测日志的各项功能和选项,有助于进行系统分析和调试。:command:`telemctl journal` " +"提供众多选项来协助过滤记录。使用 :command:`-h` 或 :command:`--help` 查看使用情况选项。" - -#: ../../guides/clear/telemetrics.rst:251 +#: ../../guides/clear/telemetrics.rst:250 msgid "Keep a local copy and send records to backend server:" msgstr "保留本地副本并将记录发送到后端服务器:" -#: ../../guides/clear/telemetrics.rst:253 +#: ../../guides/clear/telemetrics.rst:252 msgid "" "To keep a local copy of the telemetry record and also send it on to the " "backend server, we will need to change the " ":guilabel:`record_retention_enabled` configuration key value to " ":guilabel:`true`." -msgstr "要保留遥测记录的本地副本并将其发送到后端服务器,需将 :guilabel:`record_retention_enabled` 配置键值更改为 :guilabel:`true`。" +msgstr "" +"要保留遥测记录的本地副本并将其发送到后端服务器,需将 :guilabel:`record_retention_enabled` 配置键值更改为 " +":guilabel:`true`。" - -#: ../../guides/clear/telemetrics.rst:258 +#: ../../guides/clear/telemetrics.rst:257 msgid "Keep all records -- don't send to backend server:" msgstr "保留所有记录 - 不发送到后端服务器:" -#: ../../guides/clear/telemetrics.rst:260 +#: ../../guides/clear/telemetrics.rst:259 msgid "" "To keep records on the system without sending them to a backend server, " "set the :guilabel:`record_server_delivery_enabled` key value to " ":guilabel:`false`. Note that you will also need to ensure the " ":guilabel:`record_retention_enabled` configuration key value is set to " ":guilabel:`true` or the system will not keep local copies." -msgstr "要保留系统上的记录而不将其发送到后端服务器,请将 :guilabel:`record_server_delivery_enabled` 键值设为 :guilabel:`false`。请注意,您可能还需确保 :guilabel:`record_retention_enabled` 配置键值已设为 :guilabel:`true`,否则系统不会保留本地副本。" +msgstr "" +"要保留系统上的记录而不将其发送到后端服务器,请将 :guilabel:`record_server_delivery_enabled` 键值设为 " +":guilabel:`false`。请注意,您可能还需确保 :guilabel:`record_retention_enabled` " +"配置键值已设为 :guilabel:`true`,否则系统不会保留本地副本。" - -#: ../../guides/clear/telemetrics.rst:266 +#: ../../guides/clear/telemetrics.rst:265 msgid "Keep and send records to custom server:" msgstr "保留记录并将其发送到定制服务器:" -#: ../../guides/clear/telemetrics.rst:268 +#: ../../guides/clear/telemetrics.rst:267 msgid "" "This assumes you have set up a custom server according to the next " "example." msgstr "此操作假设您已根据下例设置了定制服务器。" -#: ../../guides/clear/telemetrics.rst:270 +#: ../../guides/clear/telemetrics.rst:269 msgid "" "The server is identified by the :guilabel:`server` setting, and by " "default records are sent to the |CL| server " ":guilabel:`server=https://clr.telemetry.intel.com/v2/collector`. To " "change this, you can use an IP address or fully qualified domain name." -msgstr "此服务器通过 :guilabel:`server` 设置确定,且默认将记录发送到 |CL| 服务器 :guilabel:`server=https://clr.telemetry.intel.com/v2/collector`。要更改此设置,可使用 IP 地址或完全限定域名。" +msgstr "" +"此服务器通过 :guilabel:`server` 设置确定,且默认将记录发送到 |CL| 服务器 " +":guilabel:`server=https://clr.telemetry.intel.com/v2/collector`。要更改此设置,可使用" +" IP 地址或完全限定域名。" - -#: ../../guides/clear/telemetrics.rst:277 +#: ../../guides/clear/telemetrics.rst:276 msgid "Set up a back-end server to collect telemetry records" msgstr "设置后端服务器以收集遥测记录" -#: ../../guides/clear/telemetrics.rst:279 +#: ../../guides/clear/telemetrics.rst:278 msgid "" "For this example, start with a clean installation of |CL| on a new system" " using the :ref:`bare-metal-install-server` getting started guide and:" msgstr "在本例中,请先使用 :ref:`bare-metal-install-server` 入门指南和以下内容在新系统上完整安装 |CL|:" -#: ../../guides/clear/telemetrics.rst:282 +#: ../../guides/clear/telemetrics.rst:281 msgid "" "Join the :guilabel:`Stability Enhancement Program` to install and enable " "the telemetrics components." msgstr "加入 :guilabel:`Stability Enhancement Program`,安装和启用遥测组件。" -#: ../../guides/clear/telemetrics.rst:285 +#: ../../guides/clear/telemetrics.rst:284 msgid "Select the manual installation method with the following settings:" msgstr "选择采用以下设置的手动安装方法:" -#: ../../guides/clear/telemetrics.rst:287 +#: ../../guides/clear/telemetrics.rst:286 msgid "Set the hostname to :guilabel:`clr-telem-server`," msgstr "将主机名设为 :guilabel:`clr-telem-server`。" -#: ../../guides/clear/telemetrics.rst:288 +#: ../../guides/clear/telemetrics.rst:287 msgid "" "Create an administrative user named :guilabel:`clear` and add this user " "to sudoers" msgstr "创建名为 :guilabel:`clear` 的管理用户并将其添加到 sudo 用户组" -#: ../../guides/clear/telemetrics.rst:291 +#: ../../guides/clear/telemetrics.rst:290 msgid "" "Log in with your administrative user, from your :file:`$HOME` directory, " "run :command:`git` to clone the :guilabel:`telemetrics-backend` " "repository into the :file:`$HOME/telemetrics-backend` directory:" -msgstr "以管理用户身份登录,在 :file:`$HOME` 目录中运行 :command:`git`,将 :guilabel:`telemetrics-backend` 存储库克隆到 :file:`$HOME/telemetrics-backend` 目录:" +msgstr "" +"以管理用户身份登录,在 :file:`$HOME` 目录中运行 :command:`git`,将 :guilabel:`telemetrics-" +"backend` 存储库克隆到 :file:`$HOME/telemetrics-backend` 目录:" - -#: ../../guides/clear/telemetrics.rst:301 +#: ../../guides/clear/telemetrics.rst:300 msgid "" "You may need to set up the :envvar:`https_proxy` environment variable if " "you have issues reaching github.com." msgstr "如果访问 github.com 时出现问题,则最好设置 :envvar:`https_proxy` 环境变量。" -#: ../../guides/clear/telemetrics.rst:304 +#: ../../guides/clear/telemetrics.rst:303 msgid "" "Change your current working directory to :file:`telemetrics-" "backend/scripts`." msgstr "将当前工作目录更改为 :file:`telemetrics-backend/scripts`。" -#: ../../guides/clear/telemetrics.rst:305 +#: ../../guides/clear/telemetrics.rst:304 msgid "" "Before you install the telemetrics backend with the :file:`deploy.sh` " "script file in the next step, here is an explanation of the options to be" " specified:" msgstr "在下一步利用 :file:`deploy.sh` 脚本文件安装遥测后端之前,请查看此处关于指定选项的说明:" -#: ../../guides/clear/telemetrics.rst:308 +#: ../../guides/clear/telemetrics.rst:307 msgid ":command:`-a install` to perform an install" msgstr ":command:`-a install` 用于安装" -#: ../../guides/clear/telemetrics.rst:309 +#: ../../guides/clear/telemetrics.rst:308 msgid ":command:`-d clr` to install to a |CL| distro" msgstr ":command:`-d clr` 用于安装到 |CL| 发行版" -#: ../../guides/clear/telemetrics.rst:310 +#: ../../guides/clear/telemetrics.rst:309 msgid ":command:`-H localhost` to set the domain to localhost" msgstr ":command:`-H localhost` 用于将域设为 localhost" -#: ../../guides/clear/telemetrics.rst:313 +#: ../../guides/clear/telemetrics.rst:312 msgid "" "The :file:`deploy.sh` shell script has minimal error checking and makes " "several changes to your system. Be sure that the options you define on " "the cmdline are correct before proceeding." -msgstr ":file:`deploy.sh` shell 脚本附带小规模错误检查机制,并可对系统进行某些更改。在继续操作之前,请确保您在命令行上定义的选项正确无误。" +msgstr "" +":file:`deploy.sh` shell " +"脚本附带小规模错误检查机制,并可对系统进行某些更改。在继续操作之前,请确保您在命令行上定义的选项正确无误。" - -#: ../../guides/clear/telemetrics.rst:317 +#: ../../guides/clear/telemetrics.rst:316 msgid "" "Run the shell script from the :file:`$HOME/telemetrics-backend/scripts` " "directory:" msgstr "在 :file:`$HOME/telemetrics-backend/scripts` 目录中运行此 shell 脚本:" -#: ../../guides/clear/telemetrics.rst:326 +#: ../../guides/clear/telemetrics.rst:325 msgid "" "The script starts and lists all the defined options and prompts you for " "the :guilabel:`PostgreSQL` database password." msgstr "此脚本将启动并列出所有已定义的选项并提示输入 :guilabel:`PostgreSQL` 数据库密码。" -#: ../../guides/clear/telemetrics.rst:340 +#: ../../guides/clear/telemetrics.rst:339 msgid "" "For the :guilabel:`DB password:`, press the :kbd:`Enter` key to accept " "the default password `postgres`." msgstr "对于 :guilabel:`DB password:`,请按 :kbd:`Enter` 键接受默认密码 `postgres`。" -#: ../../guides/clear/telemetrics.rst:345 +#: ../../guides/clear/telemetrics.rst:344 msgid "" "The :file:`deploy.sh` script uses :command:`sudo` to run commands and you" " may be prompted to enter your user password at any time while the script" " is executing. If this occurs, enter your user password to execute the " ":command:`sudo` command." -msgstr ":file:`deploy.sh` 脚本使用 :command:`sudo` 运行命令,而系统在执行脚本时则随时可能会提示您输入用户密码。如果出现此情况,请输入用户密码,执行 :command:`sudo` 命令。" +msgstr "" +":file:`deploy.sh` 脚本使用 :command:`sudo` " +"运行命令,而系统在执行脚本时则随时可能会提示您输入用户密码。如果出现此情况,请输入用户密码,执行 :command:`sudo` 命令。" - -#: ../../guides/clear/telemetrics.rst:351 +#: ../../guides/clear/telemetrics.rst:350 msgid "" "After all the server components have been installed, you are prompted to " "enter the :guilabel:`PostgreSQL` database password to change it as " "illustrated below:" msgstr "所有服务器组件均已安装后,系统将提示输入 :guilabel:`PostgreSQL` 数据库密码,如下所示对其进行更改:" -#: ../../guides/clear/telemetrics.rst:362 +#: ../../guides/clear/telemetrics.rst:361 msgid "" "Enter `postgres` for the current value of the password and then enter a " "new password, retype it to verify the new password and the " ":guilabel:`PostgreSQL` database password will be updated." -msgstr "输入此密码的当前值 `postgres`,然后输入新密码。接着,再次输入此密码进行验证, :guilabel:`PostgreSQL` 数据库密码随即更新。" +msgstr "" +"输入此密码的当前值 `postgres`,然后输入新密码。接着,再次输入此密码进行验证, :guilabel:`PostgreSQL` " +"数据库密码随即更新。" - -#: ../../guides/clear/telemetrics.rst:366 +#: ../../guides/clear/telemetrics.rst:365 msgid "" "After the installation is complete, you can use your web browser to view " "the new server by opening the browser on the system and typing in " @@ -578,133 +612,139 @@ msgid "" "one shown in Figure 2 below." msgstr "安装完成后,可以打开系统浏览器,在地址栏中输入 localhost,使用 Web 浏览器查看新服务器。您应看到下面图 2 所示的网页。" -#: ../../guides/clear/telemetrics.rst:374 +#: ../../guides/clear/telemetrics.rst:373 msgid "Figure 2: :guilabel:`Telemetry UI`" msgstr "图 2: :guilabel:`Telemetry UI`" -#: ../../guides/clear/telemetrics.rst:377 +#: ../../guides/clear/telemetrics.rst:376 msgid "Create records with telem-record-gen" msgstr "使用 telem-record-gen 创建记录" -#: ../../guides/clear/telemetrics.rst:379 +#: ../../guides/clear/telemetrics.rst:378 msgid "" "The telemetrics bundle provides a record generator tool called `telem-" "record-gen`. This tool can be used to create records from shell scripts " "or the command line when writing a probe in C is not desirable. Records " "are sent to the backend server, and can also be echoed to stdout." -msgstr "遥测 bundle 文件提供名为 `telem-record-gen` 的记录生成器工具。无法以 C 语言编写探针时,便可使用此工具从 shell 脚本或命令行创建记录。记录将发送到后端服务器,同时还可返回 stdout。" +msgstr "" +"遥测 bundle 文件提供名为 `telem-record-gen` 的记录生成器工具。无法以 C 语言编写探针时,便可使用此工具从 shell" +" 脚本或命令行创建记录。记录将发送到后端服务器,同时还可返回 stdout。" - -#: ../../guides/clear/telemetrics.rst:384 +#: ../../guides/clear/telemetrics.rst:383 msgid "There are three ways to supply the payload to the record." msgstr "有三种方法可将有效负载提供给记录。" -#: ../../guides/clear/telemetrics.rst:386 +#: ../../guides/clear/telemetrics.rst:385 msgid "On the command line, use the :command:`-p ` option:" msgstr "在命令行中,使用 :command:`-p ` 选项:" -#: ../../guides/clear/telemetrics.rst:412 +#: ../../guides/clear/telemetrics.rst:411 msgid "" "Specify a file that contains the payload with the option :command:`-P " "path/to/file`." msgstr "通过 :command:`-P path/to/file` 选项指定包含此有效负载的文件。" -#: ../../guides/clear/telemetrics.rst:439 +#: ../../guides/clear/telemetrics.rst:438 msgid "" "If the :command:`-p` or :command:`-P` options are absent, the tool reads " "from stdin so you can use it in a :file:`heredoc` in scripts." -msgstr "如果不使用 :command:`-p` 或 :command:`-P` 选项,此工具则会从 stdin 读取,以便您在脚本的 :file:`heredoc` 中使用。" +msgstr "" +"如果不使用 :command:`-p` 或 :command:`-P` 选项,此工具则会从 stdin 读取,以便您在脚本的 " +":file:`heredoc` 中使用。" - -#: ../../guides/clear/telemetrics.rst:469 +#: ../../guides/clear/telemetrics.rst:468 msgid "Set a static machine id" msgstr "设置静态计算机 ID" -#: ../../guides/clear/telemetrics.rst:471 +#: ../../guides/clear/telemetrics.rst:470 msgid "" "The machine id reported by the telemetry client is rotated every three " "days for privacy reasons. If you wish to have a static machine id for " "testing purposes, you can opt in by creating a file named `opt-in-static-" "machine-id` in the directory :file:`/etc/telemetrics/`." -msgstr "出于隐私,遥测客户端报告的计算机 ID 每三天轮换一次。如果希望获得测试用的静态计算机 ID,则可在 :file:`/etc/telemetrics/` 目录中创建名为 `opt-in-static-machine-id` 的文件来选择启用。" +msgstr "" +"出于隐私,遥测客户端报告的计算机 ID 每三天轮换一次。如果希望获得测试用的静态计算机 ID,则可在 " +":file:`/etc/telemetrics/` 目录中创建名为 `opt-in-static-machine-id` 的文件来选择启用。" - -#: ../../guides/clear/telemetrics.rst:476 +#: ../../guides/clear/telemetrics.rst:475 msgid "Create a directory `telemetrics`." msgstr "创建 `telemetrics` 目录。" -#: ../../guides/clear/telemetrics.rst:483 +#: ../../guides/clear/telemetrics.rst:482 msgid "" "Create the file and replace the \"unique machine ID\" with your desired " "static machine ID." msgstr "创建文件并将 \"unique machine ID\" 替换为所需的静态计算机 ID。" -#: ../../guides/clear/telemetrics.rst:492 +#: ../../guides/clear/telemetrics.rst:491 msgid "The machine ID is different than the system hostname." msgstr "该计算机 ID 不同于系统主机名。" -#: ../../guides/clear/telemetrics.rst:495 +#: ../../guides/clear/telemetrics.rst:494 msgid "Instrument your code with the libtelemetry API" msgstr "通过 libtelemetry API 检测代码" -#: ../../guides/clear/telemetrics.rst:498 +#: ../../guides/clear/telemetrics.rst:497 msgid "Prerequisites" msgstr "必备条件" -#: ../../guides/clear/telemetrics.rst:500 +#: ../../guides/clear/telemetrics.rst:499 msgid "" "Confirm that the telemetrics header file is located on the system at " ":file:`usr/include/telemetry.h` The `latest version`_ of the file can " "also be found on github for reference, but installing the " ":command:`telemetry` bundle will install the header file that matches " "your |CL| version." -msgstr "确认遥测头文件位于系统上的 :file:`usr/include/telemetry.h`。此文件的 `latest version`_ 也可在 Github 上找到,以供参考,但安装 :command:`telemetry` bundle 文件会安装匹配 |CL| 版本的头文件。" +msgstr "" +"确认遥测头文件位于系统上的 :file:`usr/include/telemetry.h`。此文件的 `latest version`_ 也可在 " +"Github 上找到,以供参考,但安装 :command:`telemetry` bundle 文件会安装匹配 |CL| 版本的头文件。" - -#: ../../guides/clear/telemetrics.rst:505 +#: ../../guides/clear/telemetrics.rst:504 msgid "Includes and variables:" msgstr "include 与变量:" -#: ../../guides/clear/telemetrics.rst:507 +#: ../../guides/clear/telemetrics.rst:506 msgid "You must include the following headers in your code to use the API:" msgstr "必须在代码中包含以下标头才能使用 API:" -#: ../../guides/clear/telemetrics.rst:518 +#: ../../guides/clear/telemetrics.rst:517 msgid "" "Use the following code to create the variables needed to hold the data " "for the record to be created:" msgstr "使用下述代码创建所需变量,以容纳用于创建记录的数据:" -#: ../../guides/clear/telemetrics.rst:537 +#: ../../guides/clear/telemetrics.rst:536 msgid "Severity:" msgstr "严重性:" -#: ../../guides/clear/telemetrics.rst:533 +#: ../../guides/clear/telemetrics.rst:532 msgid "" "Type: uint32_t Value: Severity field value. Accepted values are in the " "range 1-4, with 1 being the lowest severity, and 4 being the highest " "severity. Values provided outside of this range are clamped to 1 or 4. " "[low, med, high, crit]" -msgstr "类型:uint32_t 值:“严重性”字段值。可接受值介于 1-4 之间,其中 1 表示严重性最低,4 则表示严重性最高。超出此范围的值将被限定为 1 或 4。[low, med, high, crit]" +msgstr "" +"类型:uint32_t 值:“严重性”字段值。可接受值介于 1-4 之间,其中 1 表示严重性最低,4 则表示严重性最高。超出此范围的值将被限定为" +" 1 或 4。[low, med, high, crit]" - -#: ../../guides/clear/telemetrics.rst:543 +#: ../../guides/clear/telemetrics.rst:542 msgid "Payload_version:" msgstr "Payload_version:" -#: ../../guides/clear/telemetrics.rst:540 +#: ../../guides/clear/telemetrics.rst:539 msgid "" "Type: uint32_t Value: Payload format version. The only supported value " "right now is 1, which indicates that the payload is a freely-formatted " "(unstructured) string. Values greater than 1 are reserved for future use." -msgstr "类型:uint32_t 值:有效负载格式版本。目前唯一支持的值为 1,表示有效负载为自由格式化(非结构化)的字符串。大于 1 的值将保留以供未来使用。" +msgstr "" +"类型:uint32_t 值:有效负载格式版本。目前唯一支持的值为 1,表示有效负载为自由格式化(非结构化)的字符串。大于 1 " +"的值将保留以供未来使用。" - -#: ../../guides/clear/telemetrics.rst:552 +#: ../../guides/clear/telemetrics.rst:551 msgid "Classification:" msgstr "分类:" -#: ../../guides/clear/telemetrics.rst:546 +#: ../../guides/clear/telemetrics.rst:545 msgid "" "Type: char array Value: It should have the form, DOMAIN/PROBENAME/REST: " "DOMAIN is the reverse domain to use as a namespace for the probe (e.g. " @@ -713,34 +753,36 @@ msgid "" "maximum length for the classification string is 122 bytes. Each sub-" "category may be no longer than 40 bytes long. Two / delimiters are " "required." -msgstr "类型:字符数组值:它应采用 DOMAIN/PROBENAME/REST 形式:DOMAIN 是用作探针命名空间的反向域(例如 org.clearlinux),PROBENAME 是探针的名称,REST 则是探针用于对记录进行分类的任意值。分类字符串的最大长度为 122 个字节。每个子类别的长度不超过 40 个字节。需使用两个斜线 (/) 分隔符。" +msgstr "" +"类型:字符数组值:它应采用 DOMAIN/PROBENAME/REST 形式:DOMAIN 是用作探针命名空间的反向域(例如 " +"org.clearlinux),PROBENAME 是探针的名称,REST 则是探针用于对记录进行分类的任意值。分类字符串的最大长度为 122 " +"个字节。每个子类别的长度不超过 40 个字节。需使用两个斜线 (/) 分隔符。" - -#: ../../guides/clear/telemetrics.rst:557 +#: ../../guides/clear/telemetrics.rst:556 msgid "Tm_handle:" msgstr "Tm_handle:" -#: ../../guides/clear/telemetrics.rst:555 +#: ../../guides/clear/telemetrics.rst:554 msgid "" "Type: Telem_ref struct pointer Value: Struct pointer declared by the " "caller, The struct is initialized if the function returns success." msgstr "类型:Telem_ref 结构指针值:调用者声明的结构指针。如果函数返回成功,则初始化此结构。" -#: ../../guides/clear/telemetrics.rst:561 +#: ../../guides/clear/telemetrics.rst:560 msgid "Payload:" msgstr "有效负载:" -#: ../../guides/clear/telemetrics.rst:560 +#: ../../guides/clear/telemetrics.rst:559 msgid "Type: char pointer Value: The payload to set" msgstr "类型:结构指针值:要设置的有效负载" -#: ../../guides/clear/telemetrics.rst:563 +#: ../../guides/clear/telemetrics.rst:562 msgid "" "For this example, we'll set the payload to “hello” by using " ":command:`asprintf()`:" msgstr "在本例中,我们使用 :command:`asprintf()` 将有效负载设为“hello”:" -#: ../../guides/clear/telemetrics.rst:572 +#: ../../guides/clear/telemetrics.rst:571 msgid "" "The functions :command:`asprintf()` and :command:`vasprintf()` are " "analogs of :command:`sprintf(3)` and :command:`vsprintf(3)`, except that " @@ -748,102 +790,112 @@ msgid "" "terminating null byte ('\\0'), and return a pointer to it via the first " "argument. This pointer should be passed to :command:`free(3)` to release " "the allocated storage when it is no longer needed." -msgstr "函数 :command:`asprintf()` 和 :command:`vasprintf()` 与 :command:`sprintf(3)` 和 :command:`vsprintf(3)` 类似,除了它们分配一个足够大的字符串来容纳包括终止空字节 ('\\0') 在内的输出,并通过第一个自变量向其返回一个指针。该指针应传递给 :command:`free(3)`,以便在不再需要时释放已分配的存储空间。" +msgstr "" +"函数 :command:`asprintf()` 和 :command:`vasprintf()` 与 :command:`sprintf(3)`" +" 和 :command:`vsprintf(3)` 类似,除了它们分配一个足够大的字符串来容纳包括终止空字节 ('\\0') " +"在内的输出,并通过第一个自变量向其返回一个指针。该指针应传递给 :command:`free(3)`,以便在不再需要时释放已分配的存储空间。" - -#: ../../guides/clear/telemetrics.rst:579 +#: ../../guides/clear/telemetrics.rst:578 msgid "Create the new telemetry record:" msgstr "创建新的遥测记录:" -#: ../../guides/clear/telemetrics.rst:581 +#: ../../guides/clear/telemetrics.rst:580 msgid "" "The function :command:`tm_create_record()` initializes a telemetry " "record and sets the severity and classification of that record, as well " "as the payload version number. The memory needed to store the telemetry " "record is allocated and should be freed with :command:`tm_free_record()` " "when no longer needed." -msgstr "函数 :command:`tm_create_record()` 可初始化遥测记录并设置此记录的严重性和分类,以及有效负载版本号。存储遥测记录所需的内存已分配,且应在不再需要时通过 :command:`tm_free_record()` 来释放。" +msgstr "" +"函数 :command:`tm_create_record()` " +"可初始化遥测记录并设置此记录的严重性和分类,以及有效负载版本号。存储遥测记录所需的内存已分配,且应在不再需要时通过 " +":command:`tm_free_record()` 来释放。" - -#: ../../guides/clear/telemetrics.rst:594 +#: ../../guides/clear/telemetrics.rst:593 msgid "Set the payload field of a telemetrics record:" msgstr "设置遥测记录的有效负载字段:" -#: ../../guides/clear/telemetrics.rst:596 +#: ../../guides/clear/telemetrics.rst:595 msgid "" "The function :command:`tm_set_payload()` attaches the provided telemetry " "record data to the telemetry record. The current maximum payload size is " "8192b." msgstr "函数 :command:`tm_set_payload()` 可将所提供的遥测记录数据附加到遥测记录中。当前最大有效负载大小为 8192b。" -#: ../../guides/clear/telemetrics.rst:608 +#: ../../guides/clear/telemetrics.rst:607 msgid "" "The :command:`free()` function frees the memory space pointed to by " "`ptr`, which must have been returned by a previous call to " ":command:`malloc()`, :command:`calloc()`, or :command:`realloc()`. " "Otherwise, or if :command:`free(ptr)` has already been called before, " "undefined behavior occurs. If `ptr` is NULL, no operation is performed." -msgstr "函数 :command:`free()` 可释放 `ptr` 指向的内存空间,而 ptr 必须通过先前对 :command:`malloc()`、:command:`calloc()` 或 :command:`realloc()` 的调用返还。否则(或者如果此前曾调用 :command:`free(ptr)`),则会出现未定义的行为。如果 ‘ptr’ 为空,则不会执行任何操作。" +msgstr "" +"函数 :command:`free()` 可释放 `ptr` 指向的内存空间,而 ptr 必须通过先前对 " +":command:`malloc()`、:command:`calloc()` 或 :command:`realloc()` " +"的调用返还。否则(或者如果此前曾调用 :command:`free(ptr)`),则会出现未定义的行为。如果 ‘ptr’ " +"为空,则不会执行任何操作。" - -#: ../../guides/clear/telemetrics.rst:614 +#: ../../guides/clear/telemetrics.rst:613 msgid "Send a record to the telemetrics daemon:" msgstr "将记录发送到遥测守护程序:" -#: ../../guides/clear/telemetrics.rst:616 +#: ../../guides/clear/telemetrics.rst:615 msgid "" "The function :command:`tm_send_record()` delivers the record to the local" " :command:`telemprobd(1)` service. Since the telemetry record was " "allocated by the program it should be freed with " ":command:`tm_free_record()` when it is no longer needed." -msgstr "函数 :command:`tm_send_record()` 向本地 :command:`telemprobd(1)` 服务提供记录。由于遥测记录是程序分配的,因此不再需要时,应通过 :command:`tm_free_record()` 释放。" +msgstr "" +"函数 :command:`tm_send_record()` 向本地 :command:`telemprobd(1)` " +"服务提供记录。由于遥测记录是程序分配的,因此不再需要时,应通过 :command:`tm_free_record()` 释放。" - -#: ../../guides/clear/telemetrics.rst:638 +#: ../../guides/clear/telemetrics.rst:637 msgid "A full sample application with compiling flags:" msgstr "带编译标志的完整示例应用程序:" -#: ../../guides/clear/telemetrics.rst:640 +#: ../../guides/clear/telemetrics.rst:639 msgid "Create a new file :file:`test.c` and add the following code:" msgstr "创建新文件 :file:`test.c` 并添加如下代码:" -#: ../../guides/clear/telemetrics.rst:695 +#: ../../guides/clear/telemetrics.rst:694 msgid "Compile with the gcc compiler, using this command:" msgstr "使用以下命令通过 gcc 编译器进行编译:" -#: ../../guides/clear/telemetrics.rst:702 +#: ../../guides/clear/telemetrics.rst:701 msgid "Test to ensure the program is working:" msgstr "测试以确保程序正在运行:" -#: ../../guides/clear/telemetrics.rst:711 +#: ../../guides/clear/telemetrics.rst:710 msgid "" "A full example of the `heartbeat probe`_ in C is documented in the source" " code." msgstr "源代码中记录了以 C 语言编写的 `heartbeat probe`_ 的完整示例。" -#: ../../guides/clear/telemetrics.rst:715 +#: ../../guides/clear/telemetrics.rst:714 msgid "Reference" msgstr "参考" -#: ../../guides/clear/telemetrics.rst:722 +#: ../../guides/clear/telemetrics.rst:721 msgid "The telemetry API" msgstr "遥测 API" -#: ../../guides/clear/telemetrics.rst:724 +#: ../../guides/clear/telemetrics.rst:723 msgid "" "Installing the :command:`telemetrics` bundle includes the libtelemetry C " "library, which exposes an API used by the telemprobd and telempostd " "daemons. You can use these in your applications as well. The API " "documentation is found in the :file:`telemetry.h` file in `Telemetrics " "client`_ repository." -msgstr "安装 :command:`telemetrics` bundle 文件包括 libtelemetry C 库,可以提供 telemprobd 和 telempostd 守护程序所用的 API。同时,也可以在应用程序中使用这些守护程序。相关 API 文档位于 `Telemetrics client`_ 存储库的 :file:`telemetry.h` 文件中。" +msgstr "" +"安装 :command:`telemetrics` bundle 文件包括 libtelemetry C 库,可以提供 telemprobd 和 " +"telempostd 守护程序所用的 API。同时,也可以在应用程序中使用这些守护程序。相关 API 文档位于 `Telemetrics " +"client`_ 存储库的 :file:`telemetry.h` 文件中。" - -#: ../../guides/clear/telemetrics.rst:730 +#: ../../guides/clear/telemetrics.rst:729 msgid "Client configuration" msgstr "客户端配置" -#: ../../guides/clear/telemetrics.rst:732 +#: ../../guides/clear/telemetrics.rst:731 msgid "" "The telemetry client will look for the configuration file located at " ":file:`/etc/telemetrics/telemetrics.conf` and use it if it exists. If the" @@ -852,42 +904,46 @@ msgid "" "modify or customize the configuration, copy the file from " ":file:`/usr/share/defaults/telemetrics` to :file:`/etc/telemetrics` and " "edit it." -msgstr "遥测客户端会查找位于 :file:`/etc/telemetrics/telemetrics.conf` 中的配置文件。如果存在,则会使用。如果此文件不存在,客户端则会使用位于 :file:`/usr/share/defaults telemetrics/telemetrics.conf` 的默认配置。要修改或定制配置,请将此文件从 :file:`/usr/share/defaults/telemetrics` 复制到 :file:`/etc/telemetrics` 并对其进行编辑。" +msgstr "" +"遥测客户端会查找位于 :file:`/etc/telemetrics/telemetrics.conf` " +"中的配置文件。如果存在,则会使用。如果此文件不存在,客户端则会使用位于 :file:`/usr/share/defaults " +"telemetrics/telemetrics.conf` 的默认配置。要修改或定制配置,请将此文件从 " +":file:`/usr/share/defaults/telemetrics` 复制到 :file:`/etc/telemetrics` " +"并对其进行编辑。" - -#: ../../guides/clear/telemetrics.rst:740 +#: ../../guides/clear/telemetrics.rst:739 msgid "Configuration options" msgstr "配置选项" -#: ../../guides/clear/telemetrics.rst:742 +#: ../../guides/clear/telemetrics.rst:741 msgid "The client uses the following configuration options from the config file:" msgstr "客户端使用配置文件中的以下配置选项:" -#: ../../guides/clear/telemetrics.rst:744 +#: ../../guides/clear/telemetrics.rst:743 msgid "server" msgstr "服务器" -#: ../../guides/clear/telemetrics.rst:745 +#: ../../guides/clear/telemetrics.rst:744 msgid "" "This specifies the web server to which telempostd sends the telemetry " "records." msgstr "此选项指定接收 telempostd 发送的遥测记录的网络服务器。" -#: ../../guides/clear/telemetrics.rst:747 +#: ../../guides/clear/telemetrics.rst:746 msgid "socket_path" msgstr "socket_path" -#: ../../guides/clear/telemetrics.rst:747 +#: ../../guides/clear/telemetrics.rst:746 msgid "" "This specifies the path of the unix domain socket on which the telemprobd" " listens for connections from the probes." msgstr "此选项指定 telemprobd 在其上侦听探针连接的 unix 域套接字路径。" -#: ../../guides/clear/telemetrics.rst:753 +#: ../../guides/clear/telemetrics.rst:752 msgid "spool_dir" msgstr "spool_dir" -#: ../../guides/clear/telemetrics.rst:750 +#: ../../guides/clear/telemetrics.rst:749 msgid "" "This configuration option is related to spooling. If the daemon is not " "able to send the telemetry records to the backend server due to reasons " @@ -896,21 +952,21 @@ msgid "" "directory should be owned by the same user as the daemon." msgstr "此配置选项与假脱机相关。如果守护程序因网络可用性等原因无法将遥测记录发送到后端服务器,则会将记录存储在假脱机目录中。此选项指定了假脱机目录的路径。此目录的所有者应与守护程序的所有者为同一用户。" -#: ../../guides/clear/telemetrics.rst:756 +#: ../../guides/clear/telemetrics.rst:755 msgid "record_expiry" msgstr "record_expiry" -#: ../../guides/clear/telemetrics.rst:756 +#: ../../guides/clear/telemetrics.rst:755 msgid "" "This is the time, in minutes, after which the records in the spool " "directory are deleted by the daemon." msgstr "此选项为时间选项(以分钟为单位)。超过此时间后,守护程序会删除假脱机目录中的记录。" -#: ../../guides/clear/telemetrics.rst:764 +#: ../../guides/clear/telemetrics.rst:763 msgid "spool_process_time" msgstr "spool_process_time" -#: ../../guides/clear/telemetrics.rst:759 +#: ../../guides/clear/telemetrics.rst:758 msgid "" "This specifies the time interval, in seconds, that the daemon waits for " "before checking the spool directory for records. The daemon picks up the " @@ -920,96 +976,102 @@ msgid "" "the daemon finds a record older than the \"record_expiry\" time, then it " "deletes that record. The daemon looks at a maximum of 20 records in a " "single spool run loop." -msgstr "此选项指定了在检查假脱机目录是否存在记录之前,守护程序等待的时间间隔(以秒为单位)。守护程序将按修改日期顺序选取记录,并尝试将记录发送到服务器。它一次最多可发送 10 条记录。如果无法成功发送记录,则会从假脱机目录中删除此记录。如果守护程序找到早于 \"record_expiry\" 时间的记录,则会删除此记录。守护程序在单个假脱机运行循环中最多会查找 20 条记录。" +msgstr "" +"此选项指定了在检查假脱机目录是否存在记录之前,守护程序等待的时间间隔(以秒为单位)。守护程序将按修改日期顺序选取记录,并尝试将记录发送到服务器。它一次最多可发送" +" 10 条记录。如果无法成功发送记录,则会从假脱机目录中删除此记录。如果守护程序找到早于 \"record_expiry\" " +"时间的记录,则会删除此记录。守护程序在单个假脱机运行循环中最多会查找 20 条记录。" - -#: ../../guides/clear/telemetrics.rst:768 +#: ../../guides/clear/telemetrics.rst:767 msgid "rate_limit_enabled" msgstr "rate_limit_enabled" -#: ../../guides/clear/telemetrics.rst:767 +#: ../../guides/clear/telemetrics.rst:766 msgid "" "This determines whether rate-limiting is enabled or disabled. When " "enabled, there is a threshold on both records sent within a window of " "time, and record bytes sent within a window a time." msgstr "此选项将确定是启用还是禁用速率限制。启用后,在某一时间窗口内发送的两个记录均有一个阈值,同时记录在一个窗口内一次发送的字节数。" -#: ../../guides/clear/telemetrics.rst:772 +#: ../../guides/clear/telemetrics.rst:771 msgid "record_burst_limit" msgstr "record_burst_limit" -#: ../../guides/clear/telemetrics.rst:771 +#: ../../guides/clear/telemetrics.rst:770 msgid "" "This is the maximum amount of records allowed to be passed by the daemon " "within the record_window_length of time. If set to -1, the rate-limiting " "for record bursts is disabled." msgstr "此选项是指守护程序在 record_window_length 时间内允许传递的最大记录数。如果将其设为 -1,则会禁用针对记录突发的速率限制。" -#: ../../guides/clear/telemetrics.rst:777 +#: ../../guides/clear/telemetrics.rst:776 msgid "record_window_length" msgstr "record_window_length" -#: ../../guides/clear/telemetrics.rst:775 +#: ../../guides/clear/telemetrics.rst:774 msgid "" "The time, in minutes (0-59), that establishes the window length for the " "record_burst_limit. For example, if record_burst_window=1000 and " "record_window_length=15, then no more than 1000 records can be passed " "within any given fifteen-minute window." -msgstr "此选项为时间选项(以分钟为单位 (0-59)),用于设定 record_burst_limit 的窗口长度。例如:如果 record_burst_window = 1000 且 record_window_length = 15,则在任意给定的 15 分钟窗口内可传递的记录数不会超过 1,000 条。" +msgstr "" +"此选项为时间选项(以分钟为单位 (0-59)),用于设定 record_burst_limit 的窗口长度。例如:如果 " +"record_burst_window = 1000 且 record_window_length = 15,则在任意给定的 15 " +"分钟窗口内可传递的记录数不会超过 1,000 条。" - -#: ../../guides/clear/telemetrics.rst:781 +#: ../../guides/clear/telemetrics.rst:780 msgid "byte_burst_limit" msgstr "byte_burst_limit" -#: ../../guides/clear/telemetrics.rst:780 +#: ../../guides/clear/telemetrics.rst:779 msgid "" "This is the maximum amount of bytes that can be passed by the daemon " "within the byte_window_length of time. If set to -1, the rate-limiting " "for byte bursts is disabled." msgstr "此选项是指守护程序在 byte_window_length 时间内可传递的最大字节数。如果将其设为 -1,则会禁用针对字节突发的速率限制。" -#: ../../guides/clear/telemetrics.rst:784 +#: ../../guides/clear/telemetrics.rst:783 msgid "byte_window_length" msgstr "byte_window_length" -#: ../../guides/clear/telemetrics.rst:784 +#: ../../guides/clear/telemetrics.rst:783 msgid "" "This is the time, in minutes (0-59), that establishes the window length " "for the byte_burst_limit." msgstr "此选项为时间选项(以分钟为单位 (0-59)),用于设定 byte_burst_limit 的窗口长度。" -#: ../../guides/clear/telemetrics.rst:788 +#: ../../guides/clear/telemetrics.rst:787 msgid "rate_limit_strategy" msgstr "rate_limit_strategy" -#: ../../guides/clear/telemetrics.rst:787 +#: ../../guides/clear/telemetrics.rst:786 msgid "" "This is the strategy chosen once the rate-limiting threshold has been " "reached. Currently the options are 'drop' or 'spool', with spool being " "the default. If spool is chosen, records will be spooled and sent at a " "later time." -msgstr "此选项是指在达到速率限制阈值后所选择的策略。目前,选项为“drop”或“spool”,其中 spool 为默认值。如果选择 spool,则会对记录进行假脱机并在以后发送。" +msgstr "" +"此选项是指在达到速率限制阈值后所选择的策略。目前,选项为“drop”或“spool”,其中 spool 为默认值。如果选择 " +"spool,则会对记录进行假脱机并在以后发送。" - -#: ../../guides/clear/telemetrics.rst:793 +#: ../../guides/clear/telemetrics.rst:792 msgid "record_retention_enabled" msgstr "record_retention_enabled" -#: ../../guides/clear/telemetrics.rst:791 +#: ../../guides/clear/telemetrics.rst:790 msgid "" "When this key is enabled (true) the daemon saves a copy of the payload on" " disk from all valid records. To avoid the excessive use of disk space " "only the latest 100 records are kept. The default value for this " "configuration key is false." -msgstr "启用此键 (true) 后,守护程序会在磁盘上保存所有有效记录中有效负载的副本。为避免过多使用磁盘空间,系统仅保留最近的 100 条记录。此配置键的默认值为 false。" +msgstr "" +"启用此键 (true) 后,守护程序会在磁盘上保存所有有效记录中有效负载的副本。为避免过多使用磁盘空间,系统仅保留最近的 100 " +"条记录。此配置键的默认值为 false。" - -#: ../../guides/clear/telemetrics.rst:807 +#: ../../guides/clear/telemetrics.rst:806 msgid "record_server_delivery_enabled" msgstr "record_server_delivery_enabled" -#: ../../guides/clear/telemetrics.rst:796 +#: ../../guides/clear/telemetrics.rst:795 msgid "" "This key controls the delivery of records to server; when enabled " "(default value), the record will be posted to the address in the " @@ -1017,55 +1079,61 @@ msgid "" "records will not be spooled or posted to backend. This configuration key " "can be used in combination with record_retention_enabled to keep copies " "of telemetry records locally only." -msgstr "此键控制向服务器传送记录;启用(默认值)后,会将记录发送到配置文件中所列的地址。如果禁用此配置键 (false),则不会对记录进行假脱机或将记录发布到后端。此配置键可与 record_retention_enabled 搭配使用,仅在本地保留遥测记录的副本。" +msgstr "" +"此键控制向服务器传送记录;启用(默认值)后,会将记录发送到配置文件中所列的地址。如果禁用此配置键 " +"(false),则不会对记录进行假脱机或将记录发布到后端。此配置键可与 record_retention_enabled " +"搭配使用,仅在本地保留遥测记录的副本。" - -#: ../../guides/clear/telemetrics.rst:804 +#: ../../guides/clear/telemetrics.rst:803 msgid "" "Configuration options may change as the telemetry client evolves. Please " "use the comments in the file itself as the most accurate reference for " "configuration." msgstr "随着遥测客户端的发展,配置选项可能会发生变化。请使用文件自身所附带的注释,作为最准确的配置参考。" -#: ../../guides/clear/telemetrics.rst:810 +#: ../../guides/clear/telemetrics.rst:809 msgid "Client run-time options" msgstr "客户端运行时选项" -#: ../../guides/clear/telemetrics.rst:812 +#: ../../guides/clear/telemetrics.rst:811 msgid "" "The |CL| telemetry client provides an admin tool called " ":guilabel:`telemctl` for managing the telemetry services and probes. The " "tool is located in :file:`/usr/bin`. Running it with no argument results " "in the following:" -msgstr "|CL| 遥测客户端提供名为 :guilabel:`telemctl` 的管理工具,可用于管理遥测服务和探针。此工具位于 :file:`/usr/bin`。如果不带参数运行此工具,则会导致如下情况:" +msgstr "" +"|CL| 遥测客户端提供名为 :guilabel:`telemctl` 的管理工具,可用于管理遥测服务和探针。此工具位于 " +":file:`/usr/bin`。如果不带参数运行此工具,则会导致如下情况:" - -#: ../../guides/clear/telemetrics.rst:833 +#: ../../guides/clear/telemetrics.rst:832 msgid "start/stop/restart" msgstr "start/stop/restart" -#: ../../guides/clear/telemetrics.rst:835 +#: ../../guides/clear/telemetrics.rst:834 msgid "" "The commands to start, stop and restart the telemetry services manage all" " required services and probes on the system. There is no need to " "separately start/stop/restart the two client daemons telemprobd and " "telempostd. The :command:`restart` command option will call " ":command:`telemctl stop` followed by :command:`telemctl start` ." -msgstr "用于启动、停止和重新启动遥测服务的命令可以管理系统上所有必要的服务和探针。无需单独启动/停止/重新启动两个客户端守护程序 telemprobd 和 telempostd。:command:`restart` 命令选项将调用 :command:`telemctl stop`,然后调用 :command:`telemctl start`。" +msgstr "" +"用于启动、停止和重新启动遥测服务的命令可以管理系统上所有必要的服务和探针。无需单独启动/停止/重新启动两个客户端守护程序 telemprobd 和" +" telempostd。:command:`restart` 命令选项将调用 :command:`telemctl stop`,然后调用 " +":command:`telemctl start`。" - -#: ../../guides/clear/telemetrics.rst:842 +#: ../../guides/clear/telemetrics.rst:841 msgid "is-active" msgstr "is-active" -#: ../../guides/clear/telemetrics.rst:844 +#: ../../guides/clear/telemetrics.rst:843 msgid "" "The :command:`is-active` option reports whether the two client daemons " "are active. This is useful to verify that the :command:`opt-in` and " ":command:`opt-out` options have taken effect, or to ensure that telemetry" " is functioning on the system. Note that both daemons are verified." -msgstr ":command:`is-active` 选项报告这两个客户端守护程序是否处于活动状态。这有助于验证 :command:`opt-in` 和 :command:`opt-out` 选项是否生效,或确保遥测正在系统上运行。请注意,系统会对两个守护程序都进行验证。" - +msgstr "" +":command:`is-active` 选项报告这两个客户端守护程序是否处于活动状态。这有助于验证 :command:`opt-in` 和 " +":command:`opt-out` 选项是否生效,或确保遥测正在系统上运行。请注意,系统会对两个守护程序都进行验证。" #~ msgid "" #~ "Telemetrics in |CL-ATTR| is a " @@ -1779,4 +1847,3 @@ msgstr ":command:`is-active` 选项报告这两个客户端守护程序是否处 #~ " are verified." #~ msgstr "" - diff --git a/locale/zh_CN/LC_MESSAGES/guides/maintenance/download-verify-decompress.po b/locale/zh_CN/LC_MESSAGES/guides/maintenance/download-verify-decompress.po index ab36aa4f..d46ca62e 100644 --- a/locale/zh_CN/LC_MESSAGES/guides/maintenance/download-verify-decompress.po +++ b/locale/zh_CN/LC_MESSAGES/guides/maintenance/download-verify-decompress.po @@ -5,17 +5,19 @@ # FIRST AUTHOR , 2019. # msgid "" -msgstr "Project-Id-Version: Clear Linux* Project Docs latest\n" +msgstr "" +"Project-Id-Version: Clear Linux* Project Docs latest\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-07-22 12:54-0700\n" -"PO-Revision-Date: 2019-08-29 15:49-0008\n" +"POT-Creation-Date: 2019-08-29 17:26-0700\n" +"PO-Revision-Date: 2019-08-29 15:49-0152\n" "Last-Translator: FULL NAME \n" +"Language: zh_Hans\n" "Language-Team: zh-Hans\n" +"Plural-Forms: nplurals=1; plural=0\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Intel® International Developer Studio Version 4.1.273.0\n" -"Language: zh-Hans\n" +"Generated-By: Babel 2.7.0\n" #: ../../guides/maintenance/download-verify-decompress.rst:4 msgid "Download, verify, and decompress a |CL-ATTR| image" @@ -28,34 +30,44 @@ msgid "" " Follow the steps for your OS." msgstr "本指南介绍可用的 |CL| 映像类型,从何处下载这些映像,如何验证这些映像的完整性以及如何解压缩这些影响。遵循适用您的操作系统的步骤。" -#: ../../reference/image-types.rst:3 +#: ../../reference/image-types.rst +#: /mnt/c/Users/KPUTNAM/Documents/_OTC_TCS/work_dir/git_repos/kp-clear/source/guides/maintenance/download-verify-decompress.rst>:3 +#: :7 +#: :13 +#: :15 +#: :18 +#: :3 +#: :6 +#: :10 +#: /mnt/c/Users/KPUTNAM/Documents/_OTC_TCS/work_dir/git_repos/kp-clear/source/guides/maintenance/download-verify-decompress.rst>:23 +#: :11 +#: /mnt/c/Users/KPUTNAM/Documents/_OTC_TCS/work_dir/git_repos/kp-clear/source/guides/maintenance/download-verify-decompress.rst>:24 +#: :13 +#: :14 +#: :16 +#: :17 +#: :19 +#: :26 +#: :27 +#: :29 +#: :30 +#: :32 +#: :33 +#: :35 +#: :36 +#: :38 +#: :39 +#: :41 +#: :42 +#: :44 +#: :45 +#: :47 +#: :48 +#: :51 +#: :52 +#: :54 +#: :55 +#: :57 +#: :58 +#: , 2019. # msgid "" -msgstr "Project-Id-Version: Clear Linux* Project Docs latest\n" +msgstr "" +"Project-Id-Version: Clear Linux* Project Docs latest\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-09 14:33-0700\n" -"PO-Revision-Date: 2019-08-29 15:49-0008\n" +"POT-Creation-Date: 2019-08-29 17:26-0700\n" +"PO-Revision-Date: 2019-08-29 15:49-0152\n" "Last-Translator: FULL NAME \n" +"Language: zh_Hans\n" "Language-Team: zh-Hans\n" +"Plural-Forms: nplurals=1; plural=0\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Intel® International Developer Studio Version 4.1.273.0\n" -"Language: zh-Hans\n" +"Generated-By: Babel 2.7.0\n" #: ../../guides/maintenance/resource-limits.rst:4 msgid "Resource limits" @@ -23,7 +25,7 @@ msgstr "资源限制" #: ../../guides/maintenance/resource-limits.rst:6 msgid "" -"Linux* systems employ limiting or quota mechanisms to provide quality of " +"Linux systems employ limiting or quota mechanisms to provide quality of " "service for system resources and contain rogue processes." msgstr "Linux* 系统使用限制机制或配额机制为系统资源提供服务质量,并且包含异常进程。" @@ -82,7 +84,9 @@ msgid "" "If needed permanently, the value can be set by creating a " ":file:`/etc/sysctl.d/*.conf` file (see :command:`man sysctl.d` for " "details). For example:" -msgstr "如果需要永久值,可以通过创建 :file:`/etc/sysctl.d/*.conf` 文件来设置值(有关详细信息,请参见 :command:`man sysctl.d`)。例如:" +msgstr "" +"如果需要永久值,可以通过创建 :file:`/etc/sysctl.d/*.conf` 文件来设置值(有关详细信息,请参见 " +":command:`man sysctl.d`)。例如:" #: ../../guides/maintenance/resource-limits.rst:73 msgid "Per-user limits" @@ -93,7 +97,9 @@ msgid "" "For processes not managed by systemd, resource limits can be set for PAM " "logins on a per-user basis with upper and lower limits in the " ":file:`/etc/security/limits.conf` file." -msgstr "对于不由 systemd 管理的进程,可以在 :file:`/etc/security/limits.conf` 文件中使用上限和下限基于用户为 PAM 登录设置资源限制。" +msgstr "" +"对于不由 systemd 管理的进程,可以在 :file:`/etc/security/limits.conf` 文件中使用上限和下限基于用户为 " +"PAM 登录设置资源限制。" #: ../../guides/maintenance/resource-limits.rst:79 msgid "" @@ -117,7 +123,10 @@ msgid "" "control group (cgroup) " "`_ Linux cgroups " "associate related process groups and provide resource accounting." -msgstr "使用 systemd 单元启动的服务的资源限制不遵循正常用户限制,因为进程在单独的 `Linux 控制组 (cgroup) `_ 中启动,Linux cgroup 将相关的进程组相关联并提供资源计帐。" +msgstr "" +"使用 systemd 单元启动的服务的资源限制不遵循正常用户限制,因为进程在单独的 `Linux 控制组 (cgroup) " +"`_ 中启动,Linux " +"cgroup 将相关的进程组相关联并提供资源计帐。" #: ../../guides/maintenance/resource-limits.rst:98 msgid "" @@ -126,12 +135,17 @@ msgid "" " Limit directives. See `process properties section of the systemd.exec " "man page " "`_." -msgstr "可以在相应的单元文件或配置放置目录中使用资源限制指令来控制各个 systemd 服务的资源限制。请参见 `process properties section of the systemd.exec man page `_。" +msgstr "" +"可以在相应的单元文件或配置放置目录中使用资源限制指令来控制各个 systemd 服务的资源限制。请参见 `process properties " +"section of the systemd.exec man page " +"`_。" #: ../../guides/maintenance/resource-limits.rst:103 msgid "" "Resource limits for all systemd services can be controlled with a file in" " the :file:`/etc/systemd/system.conf.d/` directory. For example, to have " "no restriction on the number of open files:" -msgstr "可以使用 :file:`/etc/systemd/system.conf.d/` 目录中的文件来控制所有 systemd 服务的资源限制。例如,要禁用对最大打开文件数的限制:" +msgstr "" +"可以使用 :file:`/etc/systemd/system.conf.d/` 目录中的文件来控制所有 systemd " +"服务的资源限制。例如,要禁用对最大打开文件数的限制:" diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/dlrs.po b/locale/zh_CN/LC_MESSAGES/tutorials/dlrs.po new file mode 100644 index 00000000..f866fb71 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/dlrs.po @@ -0,0 +1,998 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019. +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 2019. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Clear Linux* Project Docs latest\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2019-08-29 17:26-0700\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.7.0\n" + +#: ../../tutorials/dlrs.rst:4 +msgid "Deep Learning Reference Stack" +msgstr "" + +#: ../../tutorials/dlrs.rst:6 +msgid "" +"This guide gives examples for using the Deep Learning Reference stack to " +"run real-world usecases, as well as benchmarking workloads for " +"TensorFlow\\*, PyTorch\\*, and Kubeflow\\* in |CL-ATTR|." +msgstr "" + +#: ../../tutorials/dlrs.rst:14 +msgid "Overview" +msgstr "" + +#: ../../tutorials/dlrs.rst:16 +msgid "" +"We created the Deep Learning Reference Stack to help AI developers " +"deliver the best experience on Intel® Architecture. This stack reduces " +"complexity common with deep learning software components, provides " +"flexibility for customized solutions, and enables you to quickly " +"prototype and deploy Deep Learning workloads. Use this guide to run " +"benchmarking workloads on your solution." +msgstr "" + +#: ../../tutorials/dlrs.rst:23 +msgid "The Deep Learning Reference Stack is available in the following versions:" +msgstr "" + +#: ../../tutorials/dlrs.rst:25 +msgid "" +"`Intel MKL-DNN-VNNI`_, which is optimized using Intel® Math Kernel " +"Library for Deep Neural Networks (Intel® MKL-DNN) primitives and " +"introduces support for Intel® AVX-512 Vector Neural Network Instructions " +"(VNNI)." +msgstr "" + +#: ../../tutorials/dlrs.rst:28 +msgid "" +"`Intel MKL-DNN`_, which includes the TensorFlow framework optimized using" +" Intel® Math Kernel Library for Deep Neural Networks (Intel® MKL-DNN) " +"primitives." +msgstr "" + +#: ../../tutorials/dlrs.rst:31 +msgid "`Eigen`_, which includes `TensorFlow`_ optimized for Intel® architecture." +msgstr "" + +#: ../../tutorials/dlrs.rst:32 +msgid "`PyTorch with OpenBLAS`_, which includes PyTorch with OpenBlas." +msgstr "" + +#: ../../tutorials/dlrs.rst:33 +msgid "" +"`PyTorch with Intel MKL-DNN`_, which includes PyTorch optimized using " +"Intel® Math Kernel Library (Intel® MKL) and Intel MKL-DNN." +msgstr "" + +#: ../../tutorials/dlrs.rst:38 +msgid "" +"To take advantage of the Intel® AVX-512 and VNNI functionality (including" +" the MKL-DNN releases) with the Deep Learning Reference Stack, you must " +"use the following hardware:" +msgstr "" + +#: ../../tutorials/dlrs.rst:41 +msgid "Intel® AVX-512 images require an Intel® Xeon® Scalable Platform" +msgstr "" + +#: ../../tutorials/dlrs.rst:42 +msgid "VNNI requires a 2nd generation Intel® Xeon® Scalable Platform" +msgstr "" + +#: ../../tutorials/dlrs.rst:45 +msgid "Stack features" +msgstr "" + +#: ../../tutorials/dlrs.rst:47 +msgid "`DLRS V4.0`_ release announcement, including benchmark results." +msgstr "" + +#: ../../tutorials/dlrs.rst:48 +msgid "`DLRS V3.0`_ release announcement." +msgstr "" + +#: ../../tutorials/dlrs.rst:49 +msgid "Deep Learning Reference Stack v2.0 including current `PyTorch benchmark`_." +msgstr "" + +#: ../../tutorials/dlrs.rst:51 +msgid "" +"Deep Learning Reference Stack v1.0 including current `TensorFlow " +"benchmark`_ results." +msgstr "" + +#: ../../tutorials/dlrs.rst:53 +msgid "" +"`DLRS Release notes`_ on Github\\* for the latest release of Deep " +"Learning Reference Stack." +msgstr "" + +#: ../../tutorials/dlrs.rst:58 +msgid "" +"The Deep Learning Reference Stack is a collective work, and each piece of" +" software within the work has its own license. Please see the `DLRS " +"Terms of Use`_ for more details about licensing and usage of the Deep " +"Learning Reference Stack." +msgstr "" + +#: ../../tutorials/dlrs.rst:63 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/dlrs.rst:65 +msgid ":ref:`Install ` |CL| on your host system" +msgstr "" + +#: ../../tutorials/dlrs.rst:66 +msgid ":command:`containers-basic` bundle" +msgstr "" + +#: ../../tutorials/dlrs.rst:67 +msgid ":command:`cloud-native-basic` bundle" +msgstr "" + +#: ../../tutorials/dlrs.rst:69 +msgid "" +"In |CL|, :command:`containers-basic` includes Docker\\*, which is " +"required for TensorFlow and PyTorch benchmarking. Use the " +":command:`swupd` utility to check if :command:`containers-basic` and " +":command:`cloud-native-basic` are present:" +msgstr "" + +#: ../../tutorials/dlrs.rst:78 +msgid "" +"To install the :command:`containers-basic` or :command:`cloud-native-" +"basic` bundles, enter:" +msgstr "" + +#: ../../tutorials/dlrs.rst:85 +msgid "" +"Docker is not started upon installation of the :command:`containers-" +"basic` bundle. To start Docker, enter:" +msgstr "" + +#: ../../tutorials/dlrs.rst:92 +msgid "" +"To ensure that Kubernetes is correctly installed and configured, follow " +"the instructions in :ref:`kubernetes`." +msgstr "" + +#: ../../tutorials/dlrs.rst:96 +msgid "Version compatibility" +msgstr "" + +#: ../../tutorials/dlrs.rst:98 +msgid "We validated these steps against the following software package versions:" +msgstr "" + +#: ../../tutorials/dlrs.rst:100 +msgid "|CL| 26240 (Minimum supported version)" +msgstr "" + +#: ../../tutorials/dlrs.rst:101 +msgid "Docker 18.06.1" +msgstr "" + +#: ../../tutorials/dlrs.rst:102 +msgid "Kubernetes 1.11.3" +msgstr "" + +#: ../../tutorials/dlrs.rst:103 +msgid "Go 1.11.12" +msgstr "" + +#: ../../tutorials/dlrs.rst:108 +msgid "" +"The Deep Learning Reference Stack was developed to provide the best user " +"experience when executed on a |CL| host. However, as the stack runs in a" +" container environment, you should be able to complete the following " +"sections of this guide on other Linux* distributions, provided they " +"comply with the Docker*, Kubernetes* and Go* package versions listed " +"above. Look for your distribution documentation on how to update packages" +" and manage Docker services." +msgstr "" + +#: ../../tutorials/dlrs.rst:113 +msgid "TensorFlow single and multi-node benchmarks" +msgstr "" + +#: ../../tutorials/dlrs.rst:115 +msgid "" +"This section describes running the `TensorFlow Benchmarks`_ in single " +"node. For multi-node testing, replicate these steps for each node. These " +"steps provide a template to run other benchmarks, provided that they can " +"invoke TensorFlow." +msgstr "" + +#: ../../tutorials/dlrs.rst:122 +msgid "" +"Performance test results for the Deep Learning Reference Stack and for " +"this guide were obtained using `runc` as the runtime." +msgstr "" + +#: ../../tutorials/dlrs.rst:125 +msgid "" +"Download either the `Eigen`_ or the `Intel MKL-DNN`_ Docker image from " +"`Docker Hub`_." +msgstr "" + +#: ../../tutorials/dlrs.rst:128 ../../tutorials/dlrs.rst:170 +msgid "Run the image with Docker:" +msgstr "" + +#: ../../tutorials/dlrs.rst:137 ../../tutorials/dlrs.rst:178 +msgid "" +"Launching the Docker image with the :command:`-i` argument starts " +"interactive mode within the container. Enter the following commands in " +"the running container." +msgstr "" + +#: ../../tutorials/dlrs.rst:141 +msgid "Clone the benchmark repository in the container:" +msgstr "" + +#: ../../tutorials/dlrs.rst:147 ../../tutorials/dlrs.rst:188 +msgid "Execute the benchmark script:" +msgstr "" + +#: ../../tutorials/dlrs.rst:155 +msgid "" +"You can replace the model with one of your choice supported by the " +"TensorFlow benchmarks." +msgstr "" + +#: ../../tutorials/dlrs.rst:158 +msgid "" +"If you are using an FP32 based model, it can be converted to an int8 " +"model using `Intel® quantization tools`_." +msgstr "" + +#: ../../tutorials/dlrs.rst:162 +msgid "PyTorch single and multi-node benchmarks" +msgstr "" + +#: ../../tutorials/dlrs.rst:164 +msgid "" +"This section describes running the `PyTorch benchmarks`_ for Caffe2 in " +"single node." +msgstr "" + +#: ../../tutorials/dlrs.rst:167 +msgid "" +"Download either the `PyTorch with OpenBLAS`_ or the `PyTorch with Intel " +"MKL-DNN`_ Docker image from `Docker Hub`_." +msgstr "" + +#: ../../tutorials/dlrs.rst:182 +msgid "Clone the benchmark repository:" +msgstr "" + +#: ../../tutorials/dlrs.rst:198 +msgid "Kubeflow multi-node benchmarks" +msgstr "" + +#: ../../tutorials/dlrs.rst:200 +msgid "" +"The benchmark workload runs in a Kubernetes cluster. The guide uses " +"`Kubeflow`_ for the Machine Learning workload deployment on three nodes." +msgstr "" + +#: ../../tutorials/dlrs.rst:205 +msgid "" +"If you choose the Intel® MKL-DNN or Intel® MKL-DNN-VNNI image, your " +"platform must support the Intel® AVX-512 instruction set. Otherwise, an " +"*illegal instruction* error may appear, and you won’t be able to complete" +" this guide." +msgstr "" + +#: ../../tutorials/dlrs.rst:211 +msgid "Kubernetes setup" +msgstr "" + +#: ../../tutorials/dlrs.rst:213 +msgid "" +"Follow the instructions in the :ref:`kubernetes` tutorial to get set up " +"on |CL|. The Kubernetes community also has instructions for creating a " +"cluster, described in `Creating a single control-plane cluster with " +"kubeadm`_." +msgstr "" + +#: ../../tutorials/dlrs.rst:218 +msgid "Kubernetes networking" +msgstr "" + +#: ../../tutorials/dlrs.rst:220 +msgid "" +"We used `flannel`_ as the network provider for these tests. If you prefer" +" a different network layer, refer to the Kubernetes network documentation" +" described in `Creating a single control-plane cluster with kubeadm`_ for" +" setup." +msgstr "" + +#: ../../tutorials/dlrs.rst:225 +msgid "Kubectl" +msgstr "" + +#: ../../tutorials/dlrs.rst:227 +msgid "" +"You can use kubectl to run commands against your Kubernetes cluster. " +"Refer to the `Overview of kubectl`_ for details on syntax and operations." +" Once you have a working cluster on Kubernetes, use the following YAML " +"script to start a pod with a simple shell script, and keep the pod open." +msgstr "" + +#: ../../tutorials/dlrs.rst:232 +msgid "Copy this example.yaml script to your system:" +msgstr "" + +#: ../../tutorials/dlrs.rst:249 +msgid "Execute the script with kubectl:" +msgstr "" + +#: ../../tutorials/dlrs.rst:255 +msgid "" +"This script opens a single pod. More robust solutions would create a " +"deployment or inject a python script or larger shell script into the " +"container." +msgstr "" + +#: ../../tutorials/dlrs.rst:259 +msgid "Images" +msgstr "" + +#: ../../tutorials/dlrs.rst:261 +msgid "" +"You must add `launcher.py`_ to the Docker image to include the Deep " +"Learning Reference Stack and put the benchmarks repo in the correct " +"location. Note that this guide uses Kubeflow v0.4.0, and cannot guarantee" +" results if you use a different version." +msgstr "" + +#: ../../tutorials/dlrs.rst:265 +msgid "From the Docker image, run the following:" +msgstr "" + +#: ../../tutorials/dlrs.rst:274 +msgid "Your entry point becomes: :file:`/opt/launcher.py`." +msgstr "" + +#: ../../tutorials/dlrs.rst:276 +msgid "This builds an image that can be consumed directly by TFJob from Kubeflow." +msgstr "" + +#: ../../tutorials/dlrs.rst:279 +msgid "ksonnet\\*" +msgstr "" + +#: ../../tutorials/dlrs.rst:281 +msgid "" +"Kubeflow uses ksonnet\\* to manage deployments, so you must install it " +"before setting up Kubeflow." +msgstr "" + +#: ../../tutorials/dlrs.rst:284 +msgid "" +"ksonnet was added to the :command:`cloud-native-basic` bundle in |CL| " +"version 27550. If you are using an older |CL| version (not recommended), " +"you must manually install ksonnet as described below." +msgstr "" + +#: ../../tutorials/dlrs.rst:288 +msgid "On |CL|, follow these steps:" +msgstr "" + +#: ../../tutorials/dlrs.rst:299 +msgid "" +"After the ksonnet installation is complete, ensure that binary `ks` is " +"accessible across the environment." +msgstr "" + +#: ../../tutorials/dlrs.rst:303 +msgid "Kubeflow" +msgstr "" + +#: ../../tutorials/dlrs.rst:305 +msgid "" +"Once you have Kubernetes running on your nodes, set up `Kubeflow`_ by " +"following these instructions from the `Getting Started with Kubeflow`_ " +"guide." +msgstr "" + +#: ../../tutorials/dlrs.rst:323 +msgid "Next, deploy the primary package for our purposes: tf-job-operator." +msgstr "" + +#: ../../tutorials/dlrs.rst:333 +msgid "" +"This creates the CustomResourceDefinition (CRD) endpoint to launch a " +"TFJob." +msgstr "" + +#: ../../tutorials/dlrs.rst:336 +msgid "Run a TFJob" +msgstr "" + +#: ../../tutorials/dlrs.rst:338 +msgid "Get the ksonnet registries for deploying TFJobs from `dlrs-tfjob`_." +msgstr "" + +#: ../../tutorials/dlrs.rst:340 +msgid "Install the TFJob components as follows:" +msgstr "" + +#: ../../tutorials/dlrs.rst:348 +msgid "Export the image name to use for the deployment:" +msgstr "" + +#: ../../tutorials/dlrs.rst:356 +msgid "Replace with the image name you specified in previous steps." +msgstr "" + +#: ../../tutorials/dlrs.rst:358 +msgid "" +"Generate Kubernetes manifests for the workloads and apply them using " +"these commands:" +msgstr "" + +#: ../../tutorials/dlrs.rst:368 +msgid "This replicates and deploys three test setups in your Kubernetes cluster." +msgstr "" + +#: ../../tutorials/dlrs.rst:371 +msgid "Results of running this section" +msgstr "" + +#: ../../tutorials/dlrs.rst:373 +msgid "" +"You must parse the logs of the Kubernetes pod to retrieve performance " +"data. The pods will still exist post-completion and will be in " +"‘Completed’ state. You can get the logs from any of the pods to inspect " +"the benchmark results. More information about Kubernetes logging is " +"available in the Kubernetes `Logging Architecture`_ documentation." +msgstr "" + +#: ../../tutorials/dlrs.rst:381 +msgid "TensorFlow Training (TFJob) with Kubeflow and DLRS" +msgstr "" + +#: ../../tutorials/dlrs.rst:383 +msgid "" +"A `TFJob`_ is Kubeflow's custom resource used to run TensorFlow training" +" jobs on Kubernetes. This example shows how to use a TFJob within the " +"DLRS container." +msgstr "" + +#: ../../tutorials/dlrs.rst:385 ../../tutorials/dlrs.rst:509 +msgid "Pre-requisites:" +msgstr "" + +#: ../../tutorials/dlrs.rst:387 ../../tutorials/dlrs.rst:511 +#: ../../tutorials/dlrs.rst:532 +msgid "A running :ref:`kubernetes` cluster" +msgstr "" + +#: ../../tutorials/dlrs.rst:389 +msgid "Deploying Kubeflow with kfctl/kustomize in |CL|" +msgstr "" + +#: ../../tutorials/dlrs.rst:393 +msgid "" +"This example proposes a Kubeflow installation with the binary kfctl " +"maintained by `Arrikto`_. Please download the `kfctl tarball`_ to " +"complete the following steps" +msgstr "" + +#: ../../tutorials/dlrs.rst:395 +msgid "Download, untar and add to your PATH if necessary" +msgstr "" + +#: ../../tutorials/dlrs.rst:404 +msgid "Install `MetalLB`_" +msgstr "" + +#: ../../tutorials/dlrs.rst:410 +msgid "Install Kubeflow resource and TFJob operators" +msgstr "" + +#: ../../tutorials/dlrs.rst:425 +msgid "List the resources" +msgstr "" + +#: ../../tutorials/dlrs.rst:427 +msgid "" +"Deployment takes around 15 minutes (or more depending on the hardware) to" +" be ready to use. After that you can use kubectl to list all the Kubeflow" +" resources deployed and monitor their status." +msgstr "" + +#: ../../tutorials/dlrs.rst:434 +msgid "Submitting TFJobs" +msgstr "" + +#: ../../tutorials/dlrs.rst:436 +msgid "" +"We provide several `DLRS TFJob`_ examples that use the Deep Learning " +"Reference Stack as the base image for creating the containers to run " +"training workloads in your Kubernetes cluster." +msgstr "" + +#: ../../tutorials/dlrs.rst:441 +msgid "Customizing a TFJob" +msgstr "" + +#: ../../tutorials/dlrs.rst:443 +msgid "" +"A TFJob is a resource with a YAML representation like the one below. Edit" +" to use the DLRS image containing the code to be executed and modify the " +"command for your own training code." +msgstr "" + +#: ../../tutorials/dlrs.rst:445 +msgid "" +"If you'd like to modify the number and type of replicas, resources, " +"persistent volumes and environment variables, please refer to the " +"`Kubeflow documentation`_" +msgstr "" + +#: ../../tutorials/dlrs.rst:499 +msgid "" +"For more information, please refer to: * `Distributed TensorFlow`_ * " +"`TFJobs`_" +msgstr "" + +#: ../../tutorials/dlrs.rst:505 +msgid "PyTorch Training (PyTorch Job) with Kubeflow and DLRS" +msgstr "" + +#: ../../tutorials/dlrs.rst:507 +msgid "" +"A `PyTorch Job`_ is Kubeflow's custom resource used to run PyTorch " +"training jobs on Kubernetes. This example builds on the framework set up " +"in the previous example." +msgstr "" + +#: ../../tutorials/dlrs.rst:512 +msgid "" +"Please follow steps 1 - 5 of the previous example to set up your " +"environment." +msgstr "" + +#: ../../tutorials/dlrs.rst:516 +msgid "Submitting PyTorch Jobs" +msgstr "" + +#: ../../tutorials/dlrs.rst:518 +msgid "" +"We provide several `DLRS PytorchJob`_ examples that use the Deep Learning" +" Reference Stack as the base image for creating the container(s) that " +"will run training workloads in your Kubernetes cluster. Select one form " +"the list below:" +msgstr "" + +#: ../../tutorials/dlrs.rst:526 +msgid "Using Kubeflow Seldon and OpenVINO* with the Deep Learning Reference Stack" +msgstr "" + +#: ../../tutorials/dlrs.rst:528 +msgid "" +"`Seldon Core`_ is an open source platform for deploying machine learning" +" models on a Kubernetes cluster. Seldon Core is supported in the `DLRS " +"V4.0`_ release." +msgstr "" + +#: ../../tutorials/dlrs.rst:531 +msgid "Pre-requisites" +msgstr "" + +#: ../../tutorials/dlrs.rst:536 +msgid "" +"Instead of using Arrikto's configuration manifest as shown in the " +"preceeding example, you should use the manifest provided by `Istio`_, for" +" this example, as Seldon deployments depend on it." +msgstr "" + +#: ../../tutorials/dlrs.rst:538 +msgid "Install deployment tools" +msgstr "" + +#: ../../tutorials/dlrs.rst:550 +msgid "Install Helm*" +msgstr "" + +#: ../../tutorials/dlrs.rst:558 +msgid "Clean the environment" +msgstr "" + +#: ../../tutorials/dlrs.rst:564 +msgid "Prepare the DLRS image" +msgstr "" + +#: ../../tutorials/dlrs.rst:566 +msgid "" +"The DLRS base image needs to be rebuilt with the " +"`Dockerfile_openvino_base`_ to add Seldon and the OpenVINO inference " +"engine." +msgstr "" + +#: ../../tutorials/dlrs.rst:572 +msgid "Mount pre-trained models into a persistent volume" +msgstr "" + +#: ../../tutorials/dlrs.rst:574 +msgid "This will also apply all PV manifests to the cluster" +msgstr "" + +#: ../../tutorials/dlrs.rst:582 +msgid "Start a shell for the container used as pv:" +msgstr "" + +#: ../../tutorials/dlrs.rst:588 +msgid "Save pre-trained models" +msgstr "" + +#: ../../tutorials/dlrs.rst:590 +msgid "" +"Now that you're inside the running container, fetch your pre-trained " +"models and save them at `/opt/ml`" +msgstr "" + +#: ../../tutorials/dlrs.rst:598 +msgid "Deploy the model server" +msgstr "" + +#: ../../tutorials/dlrs.rst:600 +msgid "Now you're ready to deploy the model server using the Helm chart provided." +msgstr "" + +#: ../../tutorials/dlrs.rst:615 +msgid "Using the Intel® OpenVINO Model Optimizer" +msgstr "" + +#: ../../tutorials/dlrs.rst:617 +msgid "" +"The Intel OpenVINO toolkit has two primary tools for deep learning, the " +"inference engine and the model optimizer. The inference engine is " +"integrated into the Deep Learning Reference Stack. It is better to use " +"the model optimizer after training the model, and before inference " +"begins. This example will explain how to use the model optimizer by going" +" through a test case with a pre-trained TensorFlow model." +msgstr "" + +#: ../../tutorials/dlrs.rst:619 +msgid "" +"This example uses resources found in the following OpenVino Toolkit " +"documentation." +msgstr "" + +#: ../../tutorials/dlrs.rst:621 +msgid "`Converting a TensorFlow Model`_" +msgstr "" + +#: ../../tutorials/dlrs.rst:623 +msgid "`Converting TensorFlow Object Detection API Models`_" +msgstr "" + +#: ../../tutorials/dlrs.rst:625 +msgid "In this example, you will:" +msgstr "" + +#: ../../tutorials/dlrs.rst:627 ../../tutorials/dlrs.rst:632 +msgid "Download a TensorFlow model" +msgstr "" + +#: ../../tutorials/dlrs.rst:628 ../../tutorials/dlrs.rst:645 +msgid "Clone the Model Optimizer" +msgstr "" + +#: ../../tutorials/dlrs.rst:629 +msgid "Install Prerequisites" +msgstr "" + +#: ../../tutorials/dlrs.rst:630 ../../tutorials/dlrs.rst:678 +msgid "Run the Model Optimizer" +msgstr "" + +#: ../../tutorials/dlrs.rst:634 +msgid "" +"We will be using an OpenVINO supported topology with the Model Optimizer." +" We will use a TensorFlow Inception V2 frozen model." +msgstr "" + +#: ../../tutorials/dlrs.rst:636 +msgid "" +"Navigate to the `OpenVINO TensorFlow Model page`_. Then scroll down to " +"the second section titled \"Supported Frozen Topologies from TensorFlow " +"Object Detection Models Zoo\" and download \"SSD Inception V2 COCO.\"" +msgstr "" + +#: ../../tutorials/dlrs.rst:638 +msgid "" +"Unpack the file into your chosen working directory. For example, if the " +"tar file is in your Downloads folder and you have navigated to the " +"directory you want to extract it into, run:" +msgstr "" + +#: ../../tutorials/dlrs.rst:647 +msgid "" +"Next we need the model optimizer directory, named `dldt`_. This example" +" assumes the parent directory is on the same level as the model " +"directory, ie:" +msgstr "" + +#: ../../tutorials/dlrs.rst:656 +msgid "To clone the Model Optimizer, run this from inside the working directory:" +msgstr "" + +#: ../../tutorials/dlrs.rst:663 +msgid "" +"If you explore the :file:`dldt` directory, you'll see both the inference " +"engine and the model optimizer. We are only concerned with the model " +"optimizer at this stage. Navigating into the model optimizer folder " +"you'll find several python scripts and text files. These are the scripts " +"you call to run the model optimizer." +msgstr "" + +#: ../../tutorials/dlrs.rst:666 +msgid "Install Prerequisites for Model Optimizer" +msgstr "" + +#: ../../tutorials/dlrs.rst:668 +msgid "" +"Install the Python packages required to run the model optimizer by " +"running the script dldt/model-" +"optimizer/install_prerequisites/install_prerequisites_tf.sh." +msgstr "" + +#: ../../tutorials/dlrs.rst:680 +msgid "" +"Running the model optimizer is as simple as calling the appropriate " +"script, however there are many configuration options that are explainedin" +" the documentation" +msgstr "" + +#: ../../tutorials/dlrs.rst:691 +msgid "" +"You should now see three files in your working directory, " +":file:`frozen_inference_graph.bin`, " +":file:`frozen_inference_graph.mapping`, and " +":file:`frozen_inference_graph.xml`. These are your new models in the " +"Intermediate Representation (IR) format and they are ready for use in the" +" OpenVINO Inference Engine." +msgstr "" + +#: ../../tutorials/dlrs.rst:694 +msgid "Using the OpenVino Inference Engine" +msgstr "" + +#: ../../tutorials/dlrs.rst:696 +msgid "" +"This example walks through the basic instructions for using the inference" +" engine." +msgstr "" + +#: ../../tutorials/dlrs.rst:698 +msgid "Starting the Model Server" +msgstr "" + +#: ../../tutorials/dlrs.rst:700 +msgid "" +"The process is similar to how we start `Jupter notebooks` on our " +"containers" +msgstr "" + +#: ../../tutorials/dlrs.rst:702 +msgid "Run this command to spin up a OpenVino model fetched from GCP" +msgstr "" + +#: ../../tutorials/dlrs.rst:709 +msgid "" +"Once the server is setup, use a :command:`grpc` client to communicate " +"with served model:" +msgstr "" + +#: ../../tutorials/dlrs.rst:723 +msgid "The results of these commands will look like this:" +msgstr "" + +#: ../../tutorials/dlrs.rst:766 +msgid "Use Jupyter Notebook" +msgstr "" + +#: ../../tutorials/dlrs.rst:768 +msgid "" +"This example uses the `PyTorch with OpenBLAS`_ container image. After it " +"is downloaded, run the Docker image with :command:`-p` to specify the " +"shared port between the container and the host. This example uses port " +"8888." +msgstr "" + +#: ../../tutorials/dlrs.rst:776 +msgid "" +"After you start the container, launch the Jupyter Notebook. This command " +"is executed inside the container image." +msgstr "" + +#: ../../tutorials/dlrs.rst:783 +msgid "" +"After the notebook has loaded, you will see output similar to the " +"following:" +msgstr "" + +#: ../../tutorials/dlrs.rst:791 +msgid "" +"From your host system, or any system that can access the host's IP " +"address, start a web browser with the following. If you are not running " +"the browser on the host system, replace :command:`127.0.0.1` with the IP " +"address of the host." +msgstr "" + +#: ../../tutorials/dlrs.rst:799 +msgid "Your browser displays the following:" +msgstr "" + +#: ../../tutorials/dlrs.rst:805 +msgid "Figure 1: :guilabel:`Jupyter Notebook`" +msgstr "" + +#: ../../tutorials/dlrs.rst:808 +msgid "" +"To create a new notebook, click :guilabel:`New` and select " +":guilabel:`Python 3`." +msgstr "" + +#: ../../tutorials/dlrs.rst:814 +msgid "Figure 2: Create a new notebook" +msgstr "" + +#: ../../tutorials/dlrs.rst:816 +msgid "A new, blank notebook is displayed, with a cell ready for input." +msgstr "" + +#: ../../tutorials/dlrs.rst:823 +msgid "" +"To verify that PyTorch is working, copy the following snippet into the " +"blank cell, and run the cell." +msgstr "" + +#: ../../tutorials/dlrs.rst:837 +msgid "When you run the cell, your output will look something like this:" +msgstr "" + +#: ../../tutorials/dlrs.rst:843 +msgid "" +"You can continue working in this notebook, or you can download existing " +"notebooks to take advantage of the Deep Learning Reference Stack's " +"optimized deep learning frameworks. Refer to `Jupyter Notebook`_ for " +"details." +msgstr "" + +#: ../../tutorials/dlrs.rst:848 +msgid "Uninstallation" +msgstr "" + +#: ../../tutorials/dlrs.rst:850 +msgid "" +"To uninstall the Deep Learning Reference Stack, you can choose to stop " +"the container so that it is not using system resources, or you can stop " +"the container and delete it to free storage space." +msgstr "" + +#: ../../tutorials/dlrs.rst:854 +msgid "To stop the container, execute the following from your host system:" +msgstr "" + +#: ../../tutorials/dlrs.rst:856 +msgid "Find the container's ID" +msgstr "" + +#: ../../tutorials/dlrs.rst:862 +msgid "This will result in output similar to the following:" +msgstr "" + +#: ../../tutorials/dlrs.rst:869 +msgid "" +"You can then use the ID or container name to stop the container. This " +"example uses the name \"oss\":" +msgstr "" + +#: ../../tutorials/dlrs.rst:877 +msgid "Verify that the container is not running" +msgstr "" + +#: ../../tutorials/dlrs.rst:884 +msgid "To delete the container from your system you need to know the Image ID:" +msgstr "" + +#: ../../tutorials/dlrs.rst:890 +msgid "This command results in output similar to the following:" +msgstr "" + +#: ../../tutorials/dlrs.rst:898 +msgid "To remove an image use the image ID:" +msgstr "" + +#: ../../tutorials/dlrs.rst:914 +msgid "" +"Note that you can execute the :command:`docker rmi` command using only " +"the first few characters of the image ID, provided they are unique on the" +" system." +msgstr "" + +#: ../../tutorials/dlrs.rst:916 +msgid "Once you have removed the image, you can verify it has been deleted with:" +msgstr "" + +#: ../../tutorials/dlrs.rst:923 +msgid "Compiling AIXPRT with OpenMP on DLRS" +msgstr "" + +#: ../../tutorials/dlrs.rst:925 +msgid "" +"To compile AIXPRT for DLRS, you will have to get the community edition of" +" AIXPRT and update the `compile_AIXPRT_source.sh` file.AIXPRT utilizes " +"build configuration files, so to build AIXPRT on the image, copy, the " +"build files from the base image, this can be done by adding these " +"commands to the end of the stacks-tensorflow-mkl dockerfile:" +msgstr "" + +#: ../../tutorials/dlrs.rst:938 +msgid "" +"AIXPRT requires OpenCV. On |CL|, the OpenCV bundle also installs the DLDT" +" components. To use AIXPRT in the DLRS environment you need to either " +"remove the shared libraries for DLDT from :file:`/usr/lib64` before you " +"run the tests, or ensure that the DLDT components in the " +":file:`/usr/local/lib` are being used for AIXPRT. This can be achieved " +"using adding LD_LIBRARY_PATH environment variable before testing." +msgstr "" + +#: ../../tutorials/dlrs.rst:945 +msgid "" +"The updates to the AIXPRT community edition have been captured in the " +"diff file :file:`compile_AIXPRT_source.sh.patch`. The core of these " +"changes relate to the version of model files(2019_R1) we download from " +"the `OpenCV open model zoo`_ and location of the build files, which in " +"our case is `/dldt`. Please refer to the patch files and make changes as " +"necessary to the compile_AIXPRT_source.sh file as required for your " +"environment." +msgstr "" + +#: ../../tutorials/dlrs.rst:949 +msgid "Related topics" +msgstr "" + +#: ../../tutorials/dlrs.rst:951 +msgid "`DLRS V3.0`_ release announcement" +msgstr "" + +#: ../../tutorials/dlrs.rst:952 +msgid "`TensorFlow Benchmarks`_" +msgstr "" + +#: ../../tutorials/dlrs.rst:953 +msgid "`PyTorch benchmarks`_" +msgstr "" + +#: ../../tutorials/dlrs.rst:954 +msgid "`Kubeflow`_" +msgstr "" + +#: ../../tutorials/dlrs.rst:955 +msgid ":ref:`kubernetes` tutorial" +msgstr "" + +#: ../../tutorials/dlrs.rst:956 +msgid "`Jupyter Notebook`_" +msgstr "" + diff --git a/locale/zh_CN/LC_MESSAGES/tutorials/parallels.po b/locale/zh_CN/LC_MESSAGES/tutorials/parallels.po new file mode 100644 index 00000000..85da1f65 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/tutorials/parallels.po @@ -0,0 +1,198 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2019. +# This file is distributed under the same license as the Clear Linux* +# Project Docs package. +# FIRST AUTHOR , 2019. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Clear Linux* Project Docs latest\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2019-08-29 17:26-0700\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.7.0\n" + +#: ../../tutorials/parallels.rst:4 +msgid "Parallels\\* Desktop for Mac\\*" +msgstr "" + +#: ../../tutorials/parallels.rst:6 +msgid "" +"This tutorial describes how to run |CL| Server in :abbr:`CLI (command-" +"line interface)` mode as a guest OS in Parallels Desktop 14 for Mac." +msgstr "" + +#: ../../tutorials/parallels.rst:10 +msgid "" +"Parallels Desktop for Mac is virtualization software that allows other " +"operating systems, such as Linux, to run side-by-side with macOS\\*." +msgstr "" + +#: ../../tutorials/parallels.rst:14 +msgid "Prerequisites" +msgstr "" + +#: ../../tutorials/parallels.rst:16 +msgid "Install Parallels Desktop 14 for Mac." +msgstr "" + +#: ../../tutorials/parallels.rst:19 +msgid "Download ISO image" +msgstr "" + +#: ../../tutorials/parallels.rst:21 +msgid "" +"Download a live-server ISO installation file from " +"https://clearlinux.org/downloads. This tutorial uses |CL| Server 30140 as" +" its example." +msgstr "" + +#: ../../tutorials/parallels.rst:24 +msgid "Unzip the ISO image with the command:" +msgstr "" + +#: ../../tutorials/parallels.rst:31 +msgid "Initialize new VM" +msgstr "" + +#: ../../tutorials/parallels.rst:33 +msgid "" +"Start Parallels and initialize your :abbr:`VM (Virtual Machine)` with the" +" following steps." +msgstr "" + +#: ../../tutorials/parallels.rst:36 +msgid "Go to :menuselection:`File > New`." +msgstr "" + +#: ../../tutorials/parallels.rst:38 +msgid "" +"In the opening dialog window, select :guilabel:`Install Windows or " +"another OS from a DVD or image`, then click :guilabel:`Continue`. (See " +"Figure 1.)" +msgstr "" + +#: ../../tutorials/parallels.rst:45 +msgid "Figure 1: Parallels opening dialog" +msgstr "" + +#: ../../tutorials/parallels.rst:47 +msgid "" +"On the next screen, select :guilabel:`Image File`, then click " +":guilabel:`Select a file...` as shown in Figure 2." +msgstr "" + +#: ../../tutorials/parallels.rst:53 +msgid "Figure 2: Dialog to select source for VM" +msgstr "" + +#: ../../tutorials/parallels.rst:55 +msgid "" +"Select your ISO file. The system displays the warning message \"Unable to" +" detect operating system\", as shown in Figure 3. This message is " +"expected and can be ignored. Click :guilabel:`Continue`." +msgstr "" + +#: ../../tutorials/parallels.rst:62 +msgid "Figure 3: Warning that OS is not detected" +msgstr "" + +#: ../../tutorials/parallels.rst:64 +msgid "" +"You are prompted to select your OS, as shown in Figure 4. Select " +":menuselection:`More Linux > Other Linux` from the drop-down menu and " +"click :guilabel:`Continue`." +msgstr "" + +#: ../../tutorials/parallels.rst:71 +msgid "Figure 4: Select OS from drop-down menu" +msgstr "" + +#: ../../tutorials/parallels.rst:73 +msgid "" +"Name your VM and check :guilabel:`Customize settings before " +"installation`. (See Figure 5.)" +msgstr "" + +#: ../../tutorials/parallels.rst:79 +msgid "Figure 5: Name and Location screen" +msgstr "" + +#: ../../tutorials/parallels.rst:81 +msgid "" +"Click :guilabel:`Create`. The Configuration window for the new VM opens, " +"as shown in Figure 6." +msgstr "" + +#: ../../tutorials/parallels.rst:84 +msgid "Select :menuselection:`Hardware > Boot Order`." +msgstr "" + +#: ../../tutorials/parallels.rst:89 +msgid "Figure 6: VM Configuration window" +msgstr "" + +#: ../../tutorials/parallels.rst:91 +msgid "" +"Expand :guilabel:`Advanced Settings`. Set :guilabel:`BIOS` to “EFI " +"64-bit” and in the :guilabel:`Boot flags` field, enter “vm.bios.efi=1” as" +" shown in Figure 7." +msgstr "" + +#: ../../tutorials/parallels.rst:98 +msgid "Figure 7: Advanced configuration settings" +msgstr "" + +#: ../../tutorials/parallels.rst:100 +msgid "Close the Configuration window and click :guilabel:`Continue`." +msgstr "" + +#: ../../tutorials/parallels.rst:102 +msgid "" +"If camera and microphone access restriction warnings are displayed, you " +"can ignore them." +msgstr "" + +#: ../../tutorials/parallels.rst:106 +msgid "Install |CL| on VM" +msgstr "" + +#: ../../tutorials/parallels.rst:108 +msgid "" +"Follow the prompts and install |CL| using the text-based installer as " +"shown in Figure 8." +msgstr "" + +#: ../../tutorials/parallels.rst:111 +msgid "" +"Refer to :ref:`bare-metal-install-server` for additional installation " +"instructions." +msgstr "" + +#: ../../tutorials/parallels.rst:117 +msgid "Figure 8: On screen instructions from text-based installer" +msgstr "" + +#: ../../tutorials/parallels.rst:119 +msgid "" +"After installation, reboot the VM. You are prompted to log in, as shown " +"in Figure 9. Log in with the credentials you used when you installed |CL|" +" on the VM." +msgstr "" + +#: ../../tutorials/parallels.rst:126 +msgid "Figure 9: Log in prompt" +msgstr "" + +#: ../../tutorials/parallels.rst:129 +msgid "" +"Congratulations! You have successfully set up a |CL| VM using Parallels " +"Desktop for Mac." +msgstr "" + diff --git a/source/FAQ/index.rst b/source/FAQ/index.rst index d43113df..5cfa0866 100644 --- a/source/FAQ/index.rst +++ b/source/FAQ/index.rst @@ -77,9 +77,9 @@ How is software installed and updated? |CL| provides software in the form of :ref:`bundles-guide` and updates software with :ref:`swupd `. -:ref:`FlatPak\* ` is an application virtualization solution that allows -more software to be available to |CL| users by augmenting the software |CL| -packages natively with software available through FlatPak. +:ref:`Flatpak\* ` is an application virtualization solution +that allows more software to be available to |CL| users by augmenting the +software |CL| packages natively with software available through Flatpak. Our goal is to have software packaged natively and made available through bundles whenever possible. @@ -135,9 +135,9 @@ on GitHub: https://github.com/clearlinux/distribution/issues/422 Is Microsoft\* Visual Studio Code\* available? ============================================== -Yes. Find the CLI command for installing `VS Code`_ and other FlatPak apps in -the `software store`_. Installing FlatPak apps is also covered in our -:ref:`tutorial `. +Yes. Find the CLI command for installing `VS Code`_ and other Flatpak apps in +the `software store`_. Installing Flatpak apps is also covered in our +:ref:`tutorial `. The |CL| team is working on a natively packaged version of Visual Studio Code for future release. diff --git a/source/_figures/flatpak/01-install-libreoffice.gif b/source/_figures/flatpak/01-install-libreoffice.gif deleted file mode 100644 index 62775293..00000000 Binary files a/source/_figures/flatpak/01-install-libreoffice.gif and /dev/null differ diff --git a/source/_figures/flatpak/02-openlibreoffice.gif b/source/_figures/flatpak/02-openlibreoffice.gif deleted file mode 100644 index 92ff6b7b..00000000 Binary files a/source/_figures/flatpak/02-openlibreoffice.gif and /dev/null differ diff --git a/source/_figures/flatpak/flatpak-01.png b/source/_figures/flatpak/flatpak-01.png new file mode 100644 index 00000000..8cc7b7cd Binary files /dev/null and b/source/_figures/flatpak/flatpak-01.png differ diff --git a/source/_figures/flatpak/flatpak-02.png b/source/_figures/flatpak/flatpak-02.png new file mode 100644 index 00000000..55f0f6f3 Binary files /dev/null and b/source/_figures/flatpak/flatpak-02.png differ diff --git a/source/_figures/flatpak/flatpak-03.png b/source/_figures/flatpak/flatpak-03.png new file mode 100644 index 00000000..ec4950c5 Binary files /dev/null and b/source/_figures/flatpak/flatpak-03.png differ diff --git a/source/_figures/flatpak/flatpak-04.png b/source/_figures/flatpak/flatpak-04.png new file mode 100644 index 00000000..af9137fa Binary files /dev/null and b/source/_figures/flatpak/flatpak-04.png differ diff --git a/source/_figures/parallels/parallels-01.png b/source/_figures/parallels/parallels-01.png new file mode 100644 index 00000000..9ba5dcc1 Binary files /dev/null and b/source/_figures/parallels/parallels-01.png differ diff --git a/source/_figures/parallels/parallels-02.png b/source/_figures/parallels/parallels-02.png new file mode 100644 index 00000000..7764b351 Binary files /dev/null and b/source/_figures/parallels/parallels-02.png differ diff --git a/source/_figures/parallels/parallels-03.png b/source/_figures/parallels/parallels-03.png new file mode 100644 index 00000000..67bb0d7f Binary files /dev/null and b/source/_figures/parallels/parallels-03.png differ diff --git a/source/_figures/parallels/parallels-04.png b/source/_figures/parallels/parallels-04.png new file mode 100644 index 00000000..672797d6 Binary files /dev/null and b/source/_figures/parallels/parallels-04.png differ diff --git a/source/_figures/parallels/parallels-05.png b/source/_figures/parallels/parallels-05.png new file mode 100644 index 00000000..57bf13e6 Binary files /dev/null and b/source/_figures/parallels/parallels-05.png differ diff --git a/source/_figures/parallels/parallels-06.png b/source/_figures/parallels/parallels-06.png new file mode 100644 index 00000000..32b7bf38 Binary files /dev/null and b/source/_figures/parallels/parallels-06.png differ diff --git a/source/_figures/parallels/parallels-07.png b/source/_figures/parallels/parallels-07.png new file mode 100644 index 00000000..e110b66a Binary files /dev/null and b/source/_figures/parallels/parallels-07.png differ diff --git a/source/_figures/parallels/parallels-08.png b/source/_figures/parallels/parallels-08.png new file mode 100644 index 00000000..668c72dd Binary files /dev/null and b/source/_figures/parallels/parallels-08.png differ diff --git a/source/_figures/parallels/parallels-09.png b/source/_figures/parallels/parallels-09.png new file mode 100644 index 00000000..8a1a2f54 Binary files /dev/null and b/source/_figures/parallels/parallels-09.png differ diff --git a/source/_figures/stacks/dlrs-fig-1.png b/source/_figures/stacks/dlrs-fig-1.png new file mode 100644 index 00000000..8054b120 Binary files /dev/null and b/source/_figures/stacks/dlrs-fig-1.png differ diff --git a/source/_figures/stacks/dlrs-fig-2.png b/source/_figures/stacks/dlrs-fig-2.png new file mode 100644 index 00000000..df7a72ab Binary files /dev/null and b/source/_figures/stacks/dlrs-fig-2.png differ diff --git a/source/_figures/stacks/dlrs-fig-3.png b/source/_figures/stacks/dlrs-fig-3.png new file mode 100644 index 00000000..ce07bbc0 Binary files /dev/null and b/source/_figures/stacks/dlrs-fig-3.png differ diff --git a/source/_figures/stacks/dlrs-fig-4.png b/source/_figures/stacks/dlrs-fig-4.png new file mode 100644 index 00000000..387cda2d Binary files /dev/null and b/source/_figures/stacks/dlrs-fig-4.png differ diff --git a/source/_figures/stacks/dlrs-fig-5.png b/source/_figures/stacks/dlrs-fig-5.png new file mode 100644 index 00000000..6c7923be Binary files /dev/null and b/source/_figures/stacks/dlrs-fig-5.png differ diff --git a/source/_scripts/_python/bundle_lister.py b/source/_scripts/_python/bundle_lister.py index 8d7f533b..5d84288a 100644 --- a/source/_scripts/_python/bundle_lister.py +++ b/source/_scripts/_python/bundle_lister.py @@ -15,6 +15,7 @@ GITHUB_BASE = "https://github.com/clearlinux/clr-bundles/tree/master/bundles/" PATTERN1 = re.compile(r"#\s?\[TITLE]:\w?(.*)") PATTERN2 = re.compile(r"#\s?\[DESCRIPTION]:\w?(.*)") PATTERN3 = re.compile(r"(?<=include)\(.*\)", re.MULTILINE) +PATTERN4 = re.compile(r"(#\s?\[STATUS]):\s?(.*)") def extractor(lines): bundle_title = "title" @@ -22,25 +23,28 @@ def extractor(lines): url = "url" include_list = [] include_unique = [] + status = "status" for i in lines: title = PATTERN1.match(i) desc = PATTERN2.match(i) includes = PATTERN3.findall(i) - + curr_status = PATTERN4.match(i) if title: bundle_title = title.groups(0)[0].strip() if desc: data_desc = desc.groups(0)[0].strip() if url: url = os.path.join(GITHUB_BASE, bundle_title) + if curr_status: + status = curr_status.group(2) if includes: include_text = includes[0].strip("()") include_list.append(include_text) include_unique = set(include_list) - return {"title": bundle_title, "data_desc": data_desc, "include_list": include_unique, "url": url} + return {"title": bundle_title, "data_desc": data_desc, "include_list": include_unique, "url": url, "status": status} -def bundler(): +def main(): data = [] try: git.Git("./cloned_repo/").clone("https://github.com/clearlinux/clr-bundles.git") @@ -62,4 +66,5 @@ def bundler(): with io.open('bundles.html.txt', 'w') as file: file.write(output) -bundler() +if __name__ == "__main__": + main() diff --git a/source/_scripts/_python/template.html b/source/_scripts/_python/template.html index 3173b56b..115379aa 100644 --- a/source/_scripts/_python/template.html +++ b/source/_scripts/_python/template.html @@ -5,7 +5,7 @@ Bundles in Clear Linux* OS - + @@ -31,6 +31,21 @@ {{d.title}} {{d.data_desc}}
+ +
Status: + {% if d.status=="Pending-Delete" %} + {{d.status}} + {% elif d.status=="Active" %} + {{d.status}} + {% elif d.status=="WIP" %} + {{d.status}} + {% elif d.status=="Deprecated" %} + {{d.status}} + {% else %} + {{d.status}} + {% endif %} +
+ {% if d.include_list %}
Includes bundle(s):
    diff --git a/source/_themes/otc_tcs_sphinx_theme/static/tcs_theme.css b/source/_themes/otc_tcs_sphinx_theme/static/tcs_theme.css index d3a39bee..2a7a173d 100644 --- a/source/_themes/otc_tcs_sphinx_theme/static/tcs_theme.css +++ b/source/_themes/otc_tcs_sphinx_theme/static/tcs_theme.css @@ -291,3 +291,19 @@ div#trademarks { background: url(./mag-glass.png) left no-repeat; background-size: 15px 15px; } + +.active-status { + color:#358ccb; +} + +.wip-status { + color:#59ca6b; +} + +.deprecated-status { + color:#f94f24; +} + +.pending-delete-status { + color:#ce2029; +} diff --git a/source/conf.py b/source/conf.py index f96859bb..4b3884b3 100644 --- a/source/conf.py +++ b/source/conf.py @@ -320,7 +320,7 @@ texinfo_documents = [ #texinfo_no_detailmenu = False # If true, generates permalinks on the HTML output. -html_add_permalinks = "" +#html_add_permalinks = "" #suppresses warnings for options that aren't referenced #suppress_warnings = ["ref.option"] diff --git a/source/guides/clear/telemetrics.rst b/source/guides/clear/telemetrics.rst index a2a41395..6e0fa4ab 100644 --- a/source/guides/clear/telemetrics.rst +++ b/source/guides/clear/telemetrics.rst @@ -12,9 +12,8 @@ This guide describes the |CL-ATTR| telemetry solution. .. note:: - The telemetry functionality adheres to `Intel privacy policies`_ regarding - the collection and use of :abbr:`PII (Personally Identifiable Information)` - and is open source. + The telemetry functionality adheres to `Intel privacy policies `_ + regarding the collection and use of :abbr:`PII (Personally Identifiable Information)` and is open source. No intentionally identifiable information about the user or system owner is collected. @@ -859,4 +858,3 @@ functioning on the system. Note that both daemons are verified. .. _Telemetrics client: https://github.com/clearlinux/telemetrics-client/ .. _latest version: https://github.com/clearlinux/telemetrics-client/tree/master/src .. _heartbeat probe: https://github.com/clearlinux/telemetrics-client/tree/master/src/probes/hello.c -.. _Intel privacy policies: https://www.intel.com/content/www/us/en/privacy/intel-privacy-notice.html diff --git a/source/guides/index.rst b/source/guides/index.rst index 3700d8a0..cb435c7b 100644 --- a/source/guides/index.rst +++ b/source/guides/index.rst @@ -14,7 +14,7 @@ The following guides provide step-by-step instructions on using |CL|. Clear Linux =========== -.. toctree:: +.. toctree:: :maxdepth: 1 :glob: diff --git a/source/guides/stacks/dlrs/dlrs.rst b/source/guides/stacks/dlrs/dlrs.rst index b61bde10..60912d8c 100644 --- a/source/guides/stacks/dlrs/dlrs.rst +++ b/source/guides/stacks/dlrs/dlrs.rst @@ -1,4 +1,4 @@ -.. _dlrs: +.. _dlrs2: Deep Learning Reference Stack ############################# @@ -589,4 +589,4 @@ Related topics .. _DLRS Release notes: https://github.com/clearlinux/dockerfiles/blob/master/stacks/dlrs/releasenote.md -.. _Intel® quantization tools: https://github.com/IntelAI/tools/blob/master/tensorflow_quantization/README.md#quantization-tools +.. _Intel® quantization tools: https://github.com/IntelAI/tools/blob/master/tensorflow_quantization/README.md#quantization-tools \ No newline at end of file diff --git a/source/tutorials/dlrs.rst b/source/tutorials/dlrs.rst new file mode 100644 index 00000000..2f633467 --- /dev/null +++ b/source/tutorials/dlrs.rst @@ -0,0 +1,1041 @@ +.. _dlrs: + +Deep Learning Reference Stack +############################# + +This guide gives examples for using the Deep Learning Reference stack to run real-world usecases, as well as benchmarking workloads for TensorFlow\*, +PyTorch\*, and Kubeflow\* in |CL-ATTR|. + +.. contents:: + :local: + :depth: 1 + +Overview +******** + +We created the Deep Learning Reference Stack to help AI developers deliver +the best experience on Intel® Architecture. This stack reduces complexity +common with deep learning software components, provides flexibility for +customized solutions, and enables you to quickly prototype and deploy Deep +Learning workloads. Use this guide to run benchmarking workloads on your +solution. + +The Deep Learning Reference Stack is available in the following versions: + +* `Intel MKL-DNN-VNNI`_, which is optimized using Intel® Math Kernel Library + for Deep Neural Networks (Intel® MKL-DNN) primitives and introduces support + for Intel® AVX-512 Vector Neural Network Instructions (VNNI). +* `Intel MKL-DNN`_, which includes the TensorFlow framework optimized using + Intel® Math Kernel Library for Deep Neural Networks (Intel® MKL-DNN) + primitives. +* `Eigen`_, which includes `TensorFlow`_ optimized for Intel® architecture. +* `PyTorch with OpenBLAS`_, which includes PyTorch with OpenBlas. +* `PyTorch with Intel MKL-DNN`_, which includes PyTorch optimized using Intel® + Math Kernel Library (Intel® MKL) and Intel MKL-DNN. + +.. important:: + + To take advantage of the Intel® AVX-512 and VNNI functionality (including the MKL-DNN releases) with the Deep + Learning Reference Stack, you must use the following hardware: + + * Intel® AVX-512 images require an Intel® Xeon® Scalable Platform + * VNNI requires a 2nd generation Intel® Xeon® Scalable Platform + +Stack features +============== + +* `DLRS V4.0`_ release announcement, including benchmark results. +* `DLRS V3.0`_ release announcement. +* Deep Learning Reference Stack v2.0 including current + `PyTorch benchmark`_. +* Deep Learning Reference Stack v1.0 including current + `TensorFlow benchmark`_ results. +* `DLRS Release notes`_ on Github\* for the latest release of Deep Learning + Reference Stack. + +.. note:: + + The Deep Learning Reference Stack is a collective work, and each piece of + software within the work has its own license. Please see the `DLRS Terms of Use`_ + for more details about licensing and usage of the Deep Learning Reference Stack. + +Prerequisites +============= + +* :ref:`Install ` |CL| on your host system +* :command:`containers-basic` bundle +* :command:`cloud-native-basic` bundle + +In |CL|, :command:`containers-basic` includes Docker\*, which is required for +TensorFlow and PyTorch benchmarking. Use the :command:`swupd` utility to +check if :command:`containers-basic` and :command:`cloud-native-basic` are +present: + +.. code-block:: bash + + sudo swupd bundle-list + +To install the :command:`containers-basic` or :command:`cloud-native-basic` +bundles, enter: + +.. code-block:: bash + + sudo swupd bundle-add containers-basic cloud-native-basic + +Docker is not started upon installation of the :command:`containers-basic` +bundle. To start Docker, enter: + +.. code-block:: bash + + sudo systemctl start docker + +To ensure that Kubernetes is correctly installed and configured, follow the +instructions in :ref:`kubernetes`. + +Version compatibility +===================== + +We validated these steps against the following software package versions: + +* |CL| 26240 (Minimum supported version) +* Docker 18.06.1 +* Kubernetes 1.11.3 +* Go 1.11.12 + + +.. note:: + + The Deep Learning Reference Stack was developed to provide the best user + experience when executed on a |CL| host. However, as the stack runs in a + container environment, you should be able to complete the following sections of this guide on other Linux* distributions, provided they comply with the Docker*, Kubernetes* and Go* package versions listed above. Look for your distribution documentation on how to update packages and manage Docker services. + +TensorFlow single and multi-node benchmarks +******************************************* + +This section describes running the `TensorFlow Benchmarks`_ in single node. +For multi-node testing, replicate these steps for each node. These steps +provide a template to run other benchmarks, provided that they can invoke +TensorFlow. + +.. note:: + + Performance test results for the Deep Learning Reference Stack and for this + guide were obtained using `runc` as the runtime. + +#. Download either the `Eigen`_ or the `Intel MKL-DNN`_ Docker image + from `Docker Hub`_. + +#. Run the image with Docker: + + .. code-block:: bash + + docker run --name --rm -i -t bash + + .. note:: + + Launching the Docker image with the :command:`-i` argument starts + interactive mode within the container. Enter the following commands in + the running container. + +#. Clone the benchmark repository in the container: + + .. code-block:: bash + + git clone http://github.com/tensorflow/benchmarks -b cnn_tf_v1.12_compatible + +#. Execute the benchmark script: + + .. code-block:: bash + + python benchmarks/scripts/tf_cnn_benchmarks/tf_cnn_benchmarks.py --device=cpu --model=resnet50 --data_format=NHWC + +.. note:: + + You can replace the model with one of your choice supported by the + TensorFlow benchmarks. + + If you are using an FP32 based model, it can be converted to an int8 model + using `Intel® quantization tools`_. + +PyTorch single and multi-node benchmarks +**************************************** + +This section describes running the `PyTorch benchmarks`_ for Caffe2 in +single node. + +#. Download either the `PyTorch with OpenBLAS`_ or the `PyTorch with Intel + MKL-DNN`_ Docker image from `Docker Hub`_. + +#. Run the image with Docker: + + .. code-block:: bash + + docker run --name --rm -i -t bash + + .. note:: + + Launching the Docker image with the :command:`-i` argument starts + interactive mode within the container. Enter the following commands in + the running container. + +#. Clone the benchmark repository: + + .. code-block:: bash + + git clone https://github.com/pytorch/pytorch.git + +#. Execute the benchmark script: + + .. code-block:: bash + + cd pytorch/caffe2/python + python convnet_benchmarks.py --batch_size 32 \ + --cpu \ + --model AlexNet + +Kubeflow multi-node benchmarks +****************************** + +The benchmark workload runs in a Kubernetes cluster. The guide uses +`Kubeflow`_ for the Machine Learning workload deployment on three nodes. + +.. warning:: + + If you choose the Intel® MKL-DNN or Intel® MKL-DNN-VNNI image, your platform + must support the Intel® AVX-512 instruction set. Otherwise, an + *illegal instruction* error may appear, and you won’t be able to complete this guide. + + +Kubernetes setup +================ + +Follow the instructions in the :ref:`kubernetes` tutorial to get set up on +|CL|. The Kubernetes community also has instructions for creating a cluster, +described in `Creating a single control-plane cluster with kubeadm`_. + +Kubernetes networking +===================== + +We used `flannel`_ as the network provider for these tests. If you +prefer a different network layer, refer to the Kubernetes network documentation +described in `Creating a single control-plane cluster with kubeadm`_ for setup. + +Kubectl +======= + +You can use kubectl to run commands against your Kubernetes cluster. Refer to +the `Overview of kubectl`_ for details on syntax and operations. Once you have a +working cluster on Kubernetes, use the following YAML script to start a pod with +a simple shell script, and keep the pod open. + +#. Copy this example.yaml script to your system: + + .. code-block:: console + + apiVersion: v1 + kind: Pod + metadata: + name: example-pod + labels: + app: ex-pod + spec: + containers: + - name: ex-pod-container + image: clearlinux/stacks-dlrs-mkl:latest + command: ['/bin/bash', '-c', '--'] + args: [ "while true; do sleep 30; done" ] + +#. Execute the script with kubectl: + + .. code-block:: bash + + kubectl apply –f /example.yaml + +This script opens a single pod. More robust solutions would create a deployment +or inject a python script or larger shell script into the container. + +Images +====== + +You must add `launcher.py`_ to the Docker image to include the Deep +Learning Reference Stack and put the benchmarks repo in the correct +location. Note that this guide uses Kubeflow v0.4.0, and cannot guarantee results if you use a different version. + +From the Docker image, run the following: + +.. code-block:: bash + + mkdir -p /opt + git clone https://github.com/tensorflow/benchmarks.git /opt/tf-benchmarks + cp launcher.py /opt + chmod u+x /opt/* + +Your entry point becomes: :file:`/opt/launcher.py`. + +This builds an image that can be consumed directly by TFJob from Kubeflow. + +ksonnet\* +========= + +Kubeflow uses ksonnet\* to manage deployments, so you must install it +before setting up Kubeflow. + +ksonnet was added to the :command:`cloud-native-basic` bundle in |CL| version +27550. If you are using an older |CL| version (not recommended), you must +manually install ksonnet as described below. + +On |CL|, follow these steps: + +.. code-block:: bash + + swupd bundle-add go-basic-dev + export GOPATH=$HOME/go + export PATH=$PATH:$GOPATH/bin + go get github.com/ksonnet/ksonnet + cd $GOPATH/src/github.com/ksonnet/ksonnet + make install + +After the ksonnet installation is complete, ensure that binary `ks` is +accessible across the environment. + +Kubeflow +======== + +Once you have Kubernetes running on your nodes, set up `Kubeflow`_ by +following these instructions from the `Getting Started with Kubeflow`_ guide. + +.. code-block:: bash + + export KUBEFLOW_SRC=$HOME/kflow + export KUBEFLOW_TAG="v0.4.1" + export KFAPP="kflow_app" + export K8S_NAMESPACE="kubeflow" + + mkdir ${KUBEFLOW_SRC} + cd ${KUBEFLOW_SRC} + ks init ${KFAPP} + cd ${KFAPP} + ks registry add kubeflow github.com/kubeflow/kubeflow/tree/${KUBEFLOW_TAG}/kubeflow + ks pkg install kubeflow/common + ks pkg install kubeflow/tf-training + +Next, deploy the primary package for our purposes: tf-job-operator. + +.. code-block:: bash + + ks env rm default + kubectl create namespace ${K8S_NAMESPACE} + ks env add default --namespace "${K8S_NAMESPACE}" + ks generate tf-job-operator tf-job-operator + ks apply default -c tf-job-operator + +This creates the CustomResourceDefinition (CRD) endpoint to launch a TFJob. + +Run a TFJob +=========== + +#. Get the ksonnet registries for deploying TFJobs from `dlrs-tfjob`_. + +#. Install the TFJob components as follows: + + .. code-block:: bash + + ks registry add dlrs-tfjob github.com/clearlinux/dockerfiles/tree/master/stacks/dlrs/kubeflow/dlrs-tfjob + + ks pkg install dlrs-tfjob/dlrs-bench + +#. Export the image name to use for the deployment: + + .. code-block:: bash + + export DLRS_IMAGE= + + .. note:: + + Replace with the image name you specified in previous steps. + +#. Generate Kubernetes manifests for the workloads and apply them using these + commands: + + .. code-block:: bash + + ks generate dlrs-resnet50 dlrsresnet50 --name=dlrsresnet50 --image=${DLRS_IMAGE} + ks generate dlrs-alexnet dlrsalexnet --name=dlrsalexnet --image=${DLRS_IMAGE} + ks apply default -c dlrsresnet50 + ks apply default -c dlrsalexnet + +This replicates and deploys three test setups in your Kubernetes cluster. + +Results of running this section +=============================== + +You must parse the logs of the Kubernetes pod to retrieve performance +data. The pods will still exist post-completion and will be in +‘Completed’ state. You can get the logs from any of the pods to inspect the +benchmark results. More information about Kubernetes logging is available +in the Kubernetes `Logging Architecture`_ documentation. + + +TensorFlow Training (TFJob) with Kubeflow and DLRS +************************************************** + +A `TFJob`_ is Kubeflow's custom resource used to run TensorFlow training jobs on Kubernetes. This example shows how to use a TFJob within the DLRS container. + +Pre-requisites: + +* A running :ref:`kubernetes` cluster + +#. Deploying Kubeflow with kfctl/kustomize in |CL| + +.. note:: + + This example proposes a Kubeflow installation with the binary kfctl maintained by `Arrikto`_. Please download the `kfctl tarball`_ to complete the following steps + +#. Download, untar and add to your PATH if necessary + + .. code-block:: bash + + KFCTL_URL="https://github.com/kubeflow/kubeflow/releases/download/v0.6.1/kfctl_v0.6.1_linux.tar.gz" + wget -P ${KFCTL_URL} ${KFCTL_PATH} + tar -C ${KFCTL_PATH} -xvf ${KFCTL_PATH}/kfctl_v${kfctl_ver}_linux.tar.gz + export PATH=$PATH:${KFCTL_PATH} + +#. Install `MetalLB`_ + + .. code-block:: bash + + kubectl apply -f https://raw.githubusercontent.com/google/metallb/v0.8.1/manifests/metallb.yaml + +#. Install Kubeflow resource and TFJob operators + + .. code-block:: bash + + # Env variables needed for your deployment + export KFAPP="" + export CONFIG="https://raw.githubusercontent.com/kubeflow/kubeflow/master/bootstrap/config/kfctl_existing_arrikto.yaml" + + kfctl init ${KFAPP} --config=${CONFIG} -V + cd ${KFAPP} + + # deploy Kubeflow: + kfctl generate k8s -V + kfctl apply k8s -V + +#. List the resources + + Deployment takes around 15 minutes (or more depending on the hardware) to be ready to use. After that you can use kubectl to list all the Kubeflow resources deployed and monitor their status. + + .. code-block:: bash + + kubectl get pods -n kubeflow + +Submitting TFJobs +================= + +We provide several `DLRS TFJob`_ examples that use the Deep Learning Reference Stack as the base image for creating the containers to run training workloads in your Kubernetes cluster. + + + +Customizing a TFJob +=================== + +A TFJob is a resource with a YAML representation like the one below. Edit to use the DLRS image containing the code to be executed and modify the command for your own training code. + +If you'd like to modify the number and type of replicas, resources, persistent volumes and environment variables, please refer to the `Kubeflow documentation`_ + +.. code-block:: console + + apiVersion: kubeflow.org/v1beta2 + kind: TFJob + metadata: + generateName: tfjob + namespace: kubeflow + spec: + tfReplicaSpecs: + PS: + replicas: 1 + restartPolicy: OnFailure + template: + spec: + containers: + - name: tensorflow + image: dlrs-image + command: + - python + - -m + - trainer.task + - --batch_size=32 + - --training_steps=1000 + Worker: + replicas: 3 + restartPolicy: OnFailure + template: + spec: + containers: + - name: tensorflow + image: dlrs-image + command: + - python + - -m + - trainer.task + - --batch_size=32 + - --training_steps=1000 + Master: + replicas: 1 + restartPolicy: OnFailure + template: + spec: + containers: + - name: tensorflow + image: dlrs-image + command: + - python + - -m + - trainer.task + - --batch_size=32 + - --training_steps=1000 + +For more information, please refer to: +* `Distributed TensorFlow`_ +* `TFJobs`_ + + +PyTorch Training (PyTorch Job) with Kubeflow and DLRS +***************************************************** + +A `PyTorch Job`_ is Kubeflow's custom resource used to run PyTorch training jobs on Kubernetes. This example builds on the framework set up in the previous example. + +Pre-requisites: + +* A running :ref:`kubernetes` cluster +* Please follow steps 1 - 5 of the previous example to set up your environment. + + +Submitting PyTorch Jobs +======================= + +We provide several `DLRS PytorchJob`_ examples that use the Deep Learning Reference Stack as the base image for creating the container(s) that will run training workloads in your Kubernetes cluster. +Select one form the list below: + + + + + +Using Kubeflow Seldon and OpenVINO* with the Deep Learning Reference Stack +************************************************************************** + +`Seldon Core`_ is an open source platform for deploying machine learning models on a Kubernetes cluster. Seldon Core is supported in the `DLRS V4.0`_ release. + +Pre-requisites +============== +* A running :ref:`kubernetes` cluster + +.. note:: + + Instead of using Arrikto's configuration manifest as shown in the preceeding example, you should use the manifest provided by `Istio`_, for this example, as Seldon deployments depend on it. + +#. Install deployment tools + + .. code-block:: bash + + INSTALL_DIR=$HOME/install_dir + BIN_DIR=${INSTALL_DIR}/bin + SRC_DIR=${INSTALL_DIR}/source + export PATH=${BIN_DIR}:$PATH + + mkdir -p ${BIN_DIR} && mkdir ${SRC_DIR} + cd ${SRC_DIR} + +#. Install Helm* + + .. code-block:: bash + + wget https://get.helm.sh/helm-v2.14.3-linux-amd64.tar.gz && tar xf helm-v2.14.3-linux-amd64.tar.gz + mv linux-amd64/helm ${BIN_DIR}/helm + + +#. Clean the environment + + .. code-block:: bash + + rm -rf ${SRC_DIR}/* + +#. Prepare the DLRS image + + The DLRS base image needs to be rebuilt with the `Dockerfile_openvino_base`_ to add Seldon and the OpenVINO inference engine. + + .. code-block:: bash + + docker build -f Dockerfile_openvino_base -t dlrs_openvino_base:0.1 . + +#. Mount pre-trained models into a persistent volume + + This will also apply all PV manifests to the cluster + + .. code-block:: bash + + kubectl apply -f storage/pv-volume.yaml + kubectl apply -f storage/model-store-pvc.yaml + kubectl apply -f storage/pv-pod.yaml + +#. Start a shell for the container used as pv: + + .. code-block:: bash + + kubectl exec -it hostpath-pvc -- /bin/bash + +#. Save pre-trained models + + Now that you're inside the running container, fetch your pre-trained models and save them at `/opt/ml` + + .. code-block:: bash + + root@hostpath-pvc:/# cd /opt/ml + root@hostpath-pvc:/# # Copy your models here + root@hostpath-pvc:/# # exit + +#. Deploy the model server + + Now you're ready to deploy the model server using the Helm chart provided. + + .. code-block:: bash + + helm install -- name=seldonov-model-server \ + --namespace kubeflow \ + --set openvino.image=dlrs_openvino_base:0.1 \ + --set openvino.model.path=/opt/ml/ \ + --set openvino.model.name= \ + --set openvino.model.input=data \ + --set openvino.model.output=prob + dlrs-seldon/helm/seldon-model-server + + +Using the Intel® OpenVINO Model Optimizer +***************************************** + +The Intel OpenVINO toolkit has two primary tools for deep learning, the inference engine and the model optimizer. The inference engine is integrated into the Deep Learning Reference Stack. It is better to use the model optimizer after training the model, and before inference begins. This example will explain how to use the model optimizer by going through a test case with a pre-trained TensorFlow model. + +This example uses resources found in the following OpenVino Toolkit documentation. + +`Converting a TensorFlow Model`_ + +`Converting TensorFlow Object Detection API Models`_ + +In this example, you will: + +* Download a TensorFlow model +* Clone the Model Optimizer +* Install Prerequisites +* Run the Model Optimizer + +#. Download a TensorFlow model + + We will be using an OpenVINO supported topology with the Model Optimizer. We will use a TensorFlow Inception V2 frozen model. + + Navigate to the `OpenVINO TensorFlow Model page`_. Then scroll down to the second section titled "Supported Frozen Topologies from TensorFlow Object Detection Models Zoo" and download "SSD Inception V2 COCO." + + Unpack the file into your chosen working directory. For example, if the tar file is in your Downloads folder and you have navigated to the directory you want to extract it into, run: + + .. code-block:: bash + + tar -xvf ~/Downloads/ssd_inception_v2_coco_2018_01_28.tar.gz + + +#. Clone the Model Optimizer + + Next we need the model optimizer directory, named `dldt`_. This example assumes the parent directory is on the same level as the model directory, ie: + + .. code-block:: console + + +--Working_Directory + +-- ssd_inception_v2_coco_2018_01_28 + +-- dldt + + + To clone the Model Optimizer, run this from inside the working directory: + + .. code-block:: bash + + git clone https://github.com/opencv/dldt.git + + + If you explore the :file:`dldt` directory, you'll see both the inference engine and the model optimizer. We are only concerned with the model optimizer at this stage. Navigating into the model optimizer folder you'll find several python scripts and text files. These are the scripts you call to run the model optimizer. + + +#. Install Prerequisites for Model Optimizer + + Install the Python packages required to run the model optimizer by running the script dldt/model-optimizer/install_prerequisites/install_prerequisites_tf.sh. + + .. code-block:: bash + + cd dldt/model-optimizer/install_prerequisites/ + ./install_prerequisites_tf.sh + cd ../../.. + + + +#. Run the Model Optimizer + + Running the model optimizer is as simple as calling the appropriate script, however there are many configuration options that are explainedin the documentation + + .. code-block:: bash + + python dldt/model-optimizer/mo_tf.py \ + --input_model=ssd_inception_v2_coco_2018_01_28/frozen_inference_graph.pb \ + --tensorflow_use_custom_operations_config dldt/model-optimizer/extensions/front/tf/ssd_v2_support.json \ + --tensorflow_object_detection_api_pipeline_config ssd_inception_v2_coco_2018_01_28/pipeline.config \ + --reverse_input_channels + + + You should now see three files in your working directory, :file:`frozen_inference_graph.bin`, :file:`frozen_inference_graph.mapping`, and :file:`frozen_inference_graph.xml`. These are your new models in the Intermediate Representation (IR) format and they are ready for use in the OpenVINO Inference Engine. + +Using the OpenVino Inference Engine +*********************************** + +This example walks through the basic instructions for using the inference engine. + +#. Starting the Model Server + + The process is similar to how we start `Jupter notebooks` on our containers + + Run this command to spin up a OpenVino model fetched from GCP + + .. code-block:: bash + + docker run -p 8000:8000 stacks-tensorflow-mkl:latest bash -c ". /workspace/scripts/serve.sh && ie_serving model --model_name resnet --model_path gs://intelai_public_models/resnet_50_i8 --port 8000" + + + Once the server is setup, use a :command:`grpc` client to communicate with served model: + + .. code-block:: bash + + git clone https://github.com/IntelAI/OpenVINO-model-server.git + cd OpenVINO-model-server + pip install -q -r OpenVINO-model-server/example_client/client_requirements.txt + pip install --user -q -r OpenVINO-model-server/example_client/client_requirements.txt + cat OpenVINO-model-server/example_client/client_requirements.txt + cd OpenVINO-model-server/example_client + + python jpeg_classification.py --images_list input_images.txt --grpc_address localhost --grpc_port 8000 --input_name data --output_name prob --size 224 --model_name resnet + + + The results of these commands will look like this: + + .. code-block:: console + + start processing: + Model name: resnet + Images list file: input_images.txt + images/airliner.jpeg (1, 3, 224, 224) ; data range: 0.0 : 255.0 + Processing time: 97.00 ms; speed 2.00 fps 10.35 + Detected: 404 Should be: 404 + images/arctic-fox.jpeg (1, 3, 224, 224) ; data range: 0.0 : 255.0 + Processing time: 16.00 ms; speed 2.00 fps 63.89 + Detected: 279 Should be: 279 + images/bee.jpeg (1, 3, 224, 224) ; data range: 0.0 : 255.0 + Processing time: 14.00 ms; speed 2.00 fps 69.82 + Detected: 309 Should be: 309 + images/golden_retriever.jpeg (1, 3, 224, 224) ; data range: 0.0 : 255.0 + Processing time: 13.00 ms; speed 2.00 fps 75.22 + Detected: 207 Should be: 207 + images/gorilla.jpeg (1, 3, 224, 224) ; data range: 0.0 : 255.0 + Processing time: 11.00 ms; speed 2.00 fps 87.24 + Detected: 366 Should be: 366 + images/magnetic_compass.jpeg (1, 3, 224, 224) ; data range: 0.0 : 247.0 + Processing time: 11.00 ms; speed 2.00 fps 91.07 + Detected: 635 Should be: 635 + images/peacock.jpeg (1, 3, 224, 224) ; data range: 0.0 : 255.0 + Processing time: 9.00 ms; speed 2.00 fps 110.1 + Detected: 84 Should be: 84 + images/pelican.jpeg (1, 3, 224, 224) ; data range: 0.0 : 255.0 + Processing time: 10.00 ms; speed 2.00 fps 103.63 + Detected: 144 Should be: 144 + images/snail.jpeg (1, 3, 224, 224) ; data range: 0.0 : 248.0 + Processing time: 10.00 ms; speed 2.00 fps 104.33 + Detected: 113 Should be: 113 + images/zebra.jpeg (1, 3, 224, 224) ; data range: 0.0 : 255.0 + Processing time: 12.00 ms; speed 2.00 fps 83.04 + Detected: 340 Should be: 340 + Overall accuracy= 100.0 % + Average latency= 19.8 ms + + + +Use Jupyter Notebook +******************** + +This example uses the `PyTorch with OpenBLAS`_ container image. After it is +downloaded, run the Docker image with :command:`-p` to specify the shared port +between the container and the host. This example uses port 8888. + +.. code-block:: bash + + docker run --name pytorchtest --rm -i -t -p 8888:8888 clearlinux/stacks-pytorch-oss bash + +After you start the container, launch the Jupyter Notebook. This +command is executed inside the container image. + +.. code-block:: bash + + jupyter notebook --ip 0.0.0.0 --no-browser --allow-root + +After the notebook has loaded, you will see output similar to the following: + +.. code-block:: console + + To access the notebook, open this file in a browser: file:///.local/share/jupyter/runtime/nbserver-16-open.html + Or copy and paste one of these URLs: + http://(846e526765e3 or 127.0.0.1):8888/?token=6357dbd072bea7287c5f0b85d31d70df344f5d8843fbfa09 + +From your host system, or any system that can access the host's IP address, +start a web browser with the following. If you are not running the browser on +the host system, replace :command:`127.0.0.1` with the IP address of the host. + +.. code-block:: bash + + http://127.0.0.1:8888/?token=6357dbd072bea7287c5f0b85d31d70df344f5d8843fbfa09 + +Your browser displays the following: + +.. figure:: ../_figures/stacks/dlrs-fig-1.png + :scale: 50% + :alt: Jupyter Notebook + +Figure 1: :guilabel:`Jupyter Notebook` + + +To create a new notebook, click :guilabel:`New` and select :guilabel:`Python 3`. + +.. figure:: ../_figures/stacks/dlrs-fig-2.png + :scale: 50% + :alt: Create a new notebook + +Figure 2: Create a new notebook + +A new, blank notebook is displayed, with a cell ready for input. + +.. figure:: ../_figures/stacks/dlrs-fig-3.png + :scale: 50% + :alt: New blank notebook + + +To verify that PyTorch is working, copy the following snippet into the blank +cell, and run the cell. + +.. code-block:: console + + from __future__ import print_function + import torch + x = torch.rand(5, 3) + print(x) + +.. figure:: ../_figures/stacks/dlrs-fig-4.png + :scale: 50% + :alt: Sample code snippet + +When you run the cell, your output will look something like this: + +.. figure:: ../_figures/stacks/dlrs-fig-5.png + :scale: 50% + :alt: code output + +You can continue working in this notebook, or you can download existing +notebooks to take advantage of the Deep Learning Reference Stack's optimized +deep learning frameworks. Refer to `Jupyter Notebook`_ for details. + +Uninstallation +************** + +To uninstall the Deep Learning Reference Stack, you can choose to stop the +container so that it is not using system resources, or you can stop the +container and delete it to free storage space. + +To stop the container, execute the following from your host system: + +#. Find the container's ID + + .. code-block:: bash + + docker container ls + + This will result in output similar to the following: + + .. code-block:: console + + CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES + e131dc71d339 clearlinux/stacks-dlrs-oss "/bin/sh -c 'bash'" 23 seconds ago Up 21 seconds oss + +#. You can then use the ID or container name to stop the container. This example + uses the name "oss": + + .. code-block:: bash + + docker container stop oss + + +#. Verify that the container is not running + + .. code-block:: bash + + docker container ls + + +#. To delete the container from your system you need to know the Image ID: + + .. code-block:: bash + + docker images + + This command results in output similar to the following: + + .. code-block:: console + + REPOSITORY TAG IMAGE ID CREATED SIZE + clearlinux/stacks-dlrs-oss latest 82757ec1648a 4 weeks ago 3.43GB + clearlinux/stacks-dlrs-mkl latest 61c178102228 4 weeks ago 2.76GB + +#. To remove an image use the image ID: + + .. code-block:: bash + + docker rmi 82757ec1648a + + .. code-block:: console + + # docker rmi 827 + Untagged: clearlinux/stacks-dlrs-oss:latest + Untagged: clearlinux/stacks-dlrs-oss@sha256:381f4b604537b2cb7fb5b583a8a847a50c4ed776f8e677e2354932eb82f18898 + Deleted: sha256:82757ec1648a906c504e50e43df74ad5fc333deee043dbfe6559c86908fac15e + Deleted: sha256:e47ecc039d48409b1c62e5ba874921d7f640243a4c3115bb41b3e1009ecb48e4 + Deleted: sha256:50c212235d3c33a3c035e586ff14359d03895c7bc701bb5dfd62dbe0e91fb486 + + + Note that you can execute the :command:`docker rmi` command using only the first few characters of the image ID, provided they are unique on the system. + +#. Once you have removed the image, you can verify it has been deleted with: + + .. code-block:: bash + + docker images + +Compiling AIXPRT with OpenMP on DLRS +************************************ + +To compile AIXPRT for DLRS, you will have to get the community edition of AIXPRT and update the `compile_AIXPRT_source.sh` file.AIXPRT utilizes +build configuration files, so to build AIXPRT on the image, copy, the build files from the base image, this can be done by adding these commands +to the end of the stacks-tensorflow-mkl dockerfile: + + .. code-block:: console + + COPY --from=base /dldt/inference-engine/bin/intel64/Release/ /usr/local/lib/openvino/tools/ + COPY --from=base /dldt/ /dldt/ + COPY ./airxprt/ /workspace/aixprt/ + RUN ./aixprt/install_deps.sh + RUN ./aixprt/install_aixprt.sh + + +AIXPRT requires OpenCV. On |CL|, the OpenCV bundle also installs the DLDT components. To use AIXPRT in the DLRS environment you need to either remove the shared libraries for DLDT from :file:`/usr/lib64` before you run the tests, or ensure that the DLDT components in the :file:`/usr/local/lib` are being used for AIXPRT. This can be achieved using adding LD_LIBRARY_PATH environment variable before testing. + + .. code-block:: bash + + export LD_LIBRARY_PATH=/usr/local/lib + + +The updates to the AIXPRT community edition have been captured in the diff file :file:`compile_AIXPRT_source.sh.patch`. The core of these changes relate to the version of model files(2019_R1) we download from the `OpenCV open model zoo`_ and location of the build files, which in our case is `/dldt`. Please refer to the patch files and make changes as necessary to the compile_AIXPRT_source.sh file as required for your environment. + + +Related topics +************** + +* `DLRS V3.0`_ release announcement +* `TensorFlow Benchmarks`_ +* `PyTorch benchmarks`_ +* `Kubeflow`_ +* :ref:`kubernetes` tutorial +* `Jupyter Notebook`_ + +.. _TensorFlow: https://www.tensorflow.org/ + +.. _Kubeflow: https://www.kubeflow.org/ + +.. _Docker Hub: https://hub.docker.com/ + +.. _TensorFlow Benchmarks: https://www.tensorflow.org/guide/performance/benchmarks + +.. _PyTorch benchmarks: https://github.com/pytorch/pytorch/blob/master/caffe2/python/convnet_benchmarks.py + +.. _Creating a single control-plane cluster with kubeadm: https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/ + +.. _flannel: https://github.com/coreos/flannel + +.. _Getting Started with Kubeflow: https://www.kubeflow.org/docs/started/getting-started/ + +.. _Eigen: https://hub.docker.com/r/clearlinux/stacks-dlrs-oss/ + +.. _Intel MKL-DNN: https://hub.docker.com/r/clearlinux/stacks-dlrs-mkl/ + +.. _PyTorch with OpenBLAS: https://hub.docker.com/r/clearlinux/stacks-pytorch-oss + +.. _PyTorch with Intel MKL-DNN: https://hub.docker.com/r/clearlinux/stacks-pytorch-mkl + +.. _Intel MKL-DNN-VNNI: https://hub.docker.com/r/clearlinux/stacks-dlrs-mkl-vnni + +.. _DLRS V3.0: https://clearlinux.org/stacks/deep-learning-reference-stack-v3 + +.. _DLRS V4.0: https://clearlinux.org/news-blogs/deep-learning-reference-stack-v4 + +.. _dlrs-tfjob: https://github.com/clearlinux/dockerfiles/tree/master/stacks/dlrs/kubeflow/dlrs-tfjob + +.. _Logging Architecture: https://kubernetes.io/docs/concepts/cluster-administration/logging/ + +.. _TensorFlow benchmark: https://clearlinux.org/stacks/deep-learning-reference-stack + +.. _PyTorch benchmark: https://clearlinux.org/stacks/deep-learning-reference-stack-pytorch + +.. _Jupyter Notebook: https://jupyter.org/ + +.. _Overview of kubectl: https://kubernetes.io/docs/reference/kubectl/overview/ + +.. _launcher.py: https://github.com/clearlinux/dockerfiles/tree/master/stacks/dlrs/kubeflow + +.. _DLRS Terms of Use: https://clearlinux.org/stacks/deep-learning/terms-of-use + +.. _DLRS Release notes: https://github.com/clearlinux/dockerfiles/blob/master/stacks/dlrs/releasenote.md + +.. _Seldon Core: https://docs.seldon.io/projects/seldon-core/en/latest/ + +.. _Istio: https://raw.githubusercontent.com/kubeflow/kubeflow/master/bootstrap/config/kfctl_k8s_istio.yaml + +.. _Dockerfile_openvino_base: https://github.com/clearlinux/dockerfiles/blob/master/stacks/dlrs/kubeflow/dlrs-seldon/docker/Dockerfile_openvino_base + +.. _TFJob: https://www.kubeflow.org/docs/components/tftraining + +.. _Arrikto: https://www.kubeflow.org/docs/started/k8s/kfctl-existing-arrikto/ + +.. _kfctl tarball: https://github.com/kubeflow/kubeflow/releases/download/v0.6.1/kfctl_v0.6.1_linux.tar.gz + +.. _MetalLB: https://metallb.universe.tf/ + +.. _Kubeflow documentation: https://www.kubeflow.org/docs/components/tftraining/#what-is-tfjob + +.. _Distributed TensorFlow: https://www.tensorflow.org/deploy/distributed +.. _TFJobs: https://www.kubeflow.org/docs/components/tftraining/ + +.. _Intel® quantization tools: https://github.com/IntelAI/tools/blob/master/tensorflow_quantization/README.md#quantization-tools + +.. _OpenCV open model zoo: https://github.com/opencv/open_model_zoo + +.. _PyTorch Job: https://www.kubeflow.org/docs/components/pytorch/ + +.. _Converting a TensorFlow Model: https://docs.openvinotoolkit.org/latest/_docs_MO_DG_prepare_model_convert_model_Convert_Model_From_TensorFlow.html + +.. _Converting TensorFlow Object Detection API Models: https://docs.openvinotoolkit.org/latest/_docs_MO_DG_prepare_model_convert_model_tf_specific_Convert_Object_Detection_API_Models.html + +.. _OpenVINO TensorFlow Model page: https://docs.openvinotoolkit.org/latest/_docs_MO_DG_prepare_model_convert_model_Convert_Model_From_TensorFlow.html + +.. _dldt: https://github.com/opencv/dldt + +.. _DLRS TFJob: https://github.com/clearlinux/dockerfiles/tree/master/stacks/dlrs/kubeflow/dlrs-tfjob + +.. _DLRS PytorchJob: https://github.com/clearlinux/dockerfiles/tree/master/stacks/dlrs/kubeflow/dlrs-pytorchjob diff --git a/source/tutorials/flatpak.rst b/source/tutorials/flatpak.rst index c186dc00..8cf31331 100644 --- a/source/tutorials/flatpak.rst +++ b/source/tutorials/flatpak.rst @@ -1,103 +1,128 @@ -.. _flatpak: +.. _flatpak-tutorial: -Flatpak\* +Flatpak\* ######### -This tutorial provides all the required steps to install Flatpak as well as -downloading, installing, and running LibreOffice\* on |CL-ATTR|. +`Flatpak`_ is a framework for building and distributing desktop apps on +Linux\*. It allows you to build a single app and install it on different +distributions of Linux. Flatpak apps are available through `Flathub`_ or the +`Clear Linux Store`_. -Please visit the `Flatpak website`_ for more information about Flatpak and -how to use it. You can also `download it here`_. +This tutorial shows how to install a Flatpak app on |CL| using Gnome\* Software +and the command line. -Before you begin -**************** +Prerequisites +************* -This tutorial assumes you have installed |CL| on your host system. -For detailed instructions on installing |CL| on a bare metal system, visit -our :ref:`bare metal installation guide `. +* |CL| installed on host system -Install Flatpak on your host system -=================================== + Refer to :ref:`Get started ` for installation instructions. -Flatpak is included as part of the bundle `desktop`. To install the -application, log in to your user account and enter the following command: +* `desktop-autostart` bundle installed -.. code-block:: bash + Flatpak is included via `desktop`, which is included in the + `desktop-autostart` bundle. The Flathub repository is pre-configured when + the `desktop-autostart` bundle is installed. - sudo swupd bundle-add desktop + Install the `desktop-autostart` bundle with the following command: -Install and run the LibreOffice Flatpak image -============================================= + .. code-block:: bash -Application developers have the option to bundle their applications using -Flatpak to allow the installation of a single distribution of their -application on different distributions of Linux, including |CL|. -Flatpak provides a `list of applications`_ available through Flathub. + sudo swupd bundle-add desktop-autostart -|CL| enables the Flathub repository by default. +Install a Flatpak app with Gnome Software +***************************************** + +|CL| desktop comes with `Gnome Software` installed. Flatpak apps can be +installed from within `Gnome Software`. + +#. Launch `Gnome Software` from your desktop. + +#. Search for the Flatpak app that you want to install, as shown in Figure 1. + + .. figure:: /_figures/flatpak/flatpak-01.png + :scale: 50% + :alt: Searching for Filezilla app in Gnome Software + + Figure 1: Searching for Filezilla app in Gnome Software + +#. When you find the app you want to install, click it to view application + details. + +#. On the app detail page, click the :guilabel:`Install` button, as shown in + Figure 2. + + .. figure:: /_figures/flatpak/flatpak-02.png + :scale: 50% + :alt: Filezilla Flatpak detail page in Gnome Software + + Figure 2: Filezilla Flatpak detail page in Gnome Software + +#. After installation is complete, you will see the new application in your + Gnome applications list, as shown in Figure 3. + + .. figure:: /_figures/flatpak/flatpak-03.png + :scale: 50% + :alt: Newly installed Filezilla application + + Figure 3: Newly installed Filezilla application + +#. Click the application icon to launch the application. + +Install a Flatpak with the command line +*************************************** + +Both Flathub and the Clear Linux Store provide the command line instructions for +installing a Flatpak. Figure 4 shows the command line instructions to install +Filezilla from the Clear Linux Store: + +.. figure:: /_figures/flatpak/flatpak-04.png + :scale: 50% + :alt: Command line instructions to install Filezilla from the Clear Linux Store + + Figure 4: Command line instructions to install Filezilla from the Clear Linux Store + +In this example, we install Filezilla. + +#. Open a terminal and enter the install command for the desired app: + + .. code-block:: bash + + flatpak install flathub org.filezillaproject.Filezilla + + You may be prompted to select which repository to use: + + .. code-block:: bash + + Looking for matches… + Remote ‘flathub’ found in multiple installations: + + 1) system + 2) user + + Which do you want to use (0 to abort)? [0-2]: 2 + + org.filezillaproject.Filezilla permissions: + ipc network ssh-auth wayland x11 + dri file access [1] dbus access [2] + + [1] host, xdg-run/dconf, ~/.config/dconf:ro + [2] ca.desrt.dconf, org.freedesktop.Notifications, org.freedesktop.PowerManagement, + org.gnome.SessionManager -Installing using gnome software -------------------------------- + ID Arch Branch Remote Download + 1. [✓] org.filezillaproject.Filezilla x86_64 stable flathub 11.5 MB / 11.5 MB + 2. [✓] org.filezillaproject.Filezilla.Locale x86_64 stable flathub 4.6 kB / 3.8 MB -All you need to do is to launch `gnome software`, search for the LibreOffice -app, and click the install button. + Installation complete. -.. figure:: /_figures/flatpak/01-install-libreoffice.gif - :alt: install libreoffice step by step +#. After installation, run the application with the following command: - Figure 1: Installing LibreOffice using gnome-software + .. code-block:: bash + flatpak run org.filezillaproject.Filezilla - -Installing using the command line ---------------------------------- - -Open the `gnome-terminal` and type the following command to install the -LibreOffice app. - -.. code-block:: bash - - flatpak install --user flathub org.libreoffice.LibreOffice - Installing in user: - org.libreoffice.LibreOffice/x86_64/stable flathub 2aff77bd5cf1 - permissions: ipc, network, pulseaudio, wayland, x11, dri - file access: host, xdg-run/dconf - dbus access: ca.desrt.dconf, org.gtk.vfs.* - dbus ownership: org.libreoffice.LibreOfficeIpc0 - org.libreoffice.LibreOffice.Locale/x86_64/stable flathub 924157b3b009 - Is this ok [y/n]: y - Installing for user: org.libreoffice.LibreOffice/x86_64/stable from flathub - [####################] 403 metadata, 4661 content objects fetched; 222574 KiB transferred in 99 seconds - Now at 2aff77bd5cf1. - Installing for user: org.libreoffice.LibreOffice.Locale/x86_64/stable from flathub - [####################] 10 metadata, 71 content objects fetched; 1013 KiB transferred in 3 seconds - Now at 924157b3b009. - - -Launch LibreOffice -================== -A new set of icons will appear in your Gnome applications list titled :guilabel:`LibreOffice.` To -execute the application, highlight the application and click on the :guilabel:`LibreOffice` icon. -LibreOffice will start normally. - -.. figure:: /_figures/flatpak/02-openlibreoffice.gif - :alt: Opening LibreOffice app - - Figure 2: Select :guilabel:`LibreOffice` app - -Using the command line ----------------------- - -.. code-block:: bash - - flatpak run org.libreoffice.LibreOffice - - -.. _Flatpak website: http://flatpak.org - -.. _list of applications: http://flatpak.org/apps.html - -.. _download it here: - http://download.documentfoundation.org/libreoffice/flatpak/latest/LibreOffice.flatpak - +.. _Flatpak: https://flatpak.org +.. _Flathub: https://flathub.org +.. _Clear Linux Store: https://clearlinux.org/software diff --git a/source/tutorials/parallels.rst b/source/tutorials/parallels.rst new file mode 100644 index 00000000..66d6858e --- /dev/null +++ b/source/tutorials/parallels.rst @@ -0,0 +1,130 @@ +.. _parallels: + +Parallels\* Desktop for Mac\* +############################# + +This tutorial describes how to run |CL| Server in +:abbr:`CLI (command-line interface)` mode as a guest OS in Parallels Desktop 14 +for Mac. + +Parallels Desktop for Mac is virtualization software that allows other +operating systems, such as Linux, to run side-by-side with macOS\*. + +Prerequisites +************* + +* Install Parallels Desktop 14 for Mac. + +Download ISO image +****************** + +#. Download a live-server ISO installation file from https://clearlinux.org/downloads. + This tutorial uses |CL| Server 30140 as its example. + +#. Unzip the ISO image with the command: + + .. code-block:: bash + + gunzip clear-30140-live-server.iso.xz + +Initialize new VM +***************** + +Start Parallels and initialize your :abbr:`VM (Virtual Machine)` with the +following steps. + +#. Go to :menuselection:`File > New`. + +#. In the opening dialog window, select + :guilabel:`Install Windows or another OS from a DVD or image`, then click + :guilabel:`Continue`. (See Figure 1.) + + .. figure:: /_figures/parallels/parallels-01.png + :alt: Parallels opening dialog + + Figure 1: Parallels opening dialog + +#. On the next screen, select :guilabel:`Image File`, then click + :guilabel:`Select a file...` as shown in Figure 2. + + .. figure:: /_figures/parallels/parallels-02.png + :alt: Dialog to select source for VM + + Figure 2: Dialog to select source for VM + +#. Select your ISO file. The system displays the warning message "Unable to + detect operating system", as shown in Figure 3. This message is expected and + can be ignored. Click :guilabel:`Continue`. + + .. figure:: /_figures/parallels/parallels-03.png + :alt: Warning that OS is not detected + + Figure 3: Warning that OS is not detected + +#. You are prompted to select your OS, as shown in Figure 4. Select + :menuselection:`More Linux > Other Linux` from the drop-down menu and click + :guilabel:`Continue`. + + .. figure:: /_figures/parallels/parallels-04.png + :alt: Select OS from drop-down menu + + Figure 4: Select OS from drop-down menu + +#. Name your VM and check :guilabel:`Customize settings before installation`. + (See Figure 5.) + + .. figure:: /_figures/parallels/parallels-05.png + :alt: Name and Location screen + + Figure 5: Name and Location screen + +#. Click :guilabel:`Create`. The Configuration window for the new VM opens, as + shown in Figure 6. + + Select :menuselection:`Hardware > Boot Order`. + + .. figure:: /_figures/parallels/parallels-06.png + :alt: VM Configuration window + + Figure 6: VM Configuration window + +#. Expand :guilabel:`Advanced Settings`. Set :guilabel:`BIOS` to “EFI 64-bit” + and in the :guilabel:`Boot flags` field, enter “vm.bios.efi=1” as shown in + Figure 7. + + .. figure:: /_figures/parallels/parallels-07.png + :alt: Advanced configuration settings + + Figure 7: Advanced configuration settings + +#. Close the Configuration window and click :guilabel:`Continue`. + + If camera and microphone access restriction warnings are displayed, you can + ignore them. + +Install |CL| on VM +****************** + +#. Follow the prompts and install |CL| using the text-based installer as shown + in Figure 8. + + Refer to :ref:`bare-metal-install-server` for additional installation + instructions. + + .. figure:: /_figures/parallels/parallels-08.png + :alt: On screen instructions from text-based installer + + Figure 8: On screen instructions from text-based installer + +#. After installation, reboot the VM. You are prompted to log in, as shown + in Figure 9. Log in with the credentials you used when you installed |CL| + on the VM. + + .. figure:: /_figures/parallels/parallels-09.png + :alt: Log in prompt + + Figure 9: Log in prompt + + +Congratulations! You have successfully set up a |CL| VM using Parallels +Desktop for Mac.