document/TranslateProject
2
0
Fork 0
mirror of https://github.com/LCTT/TranslateProject.git synced 2025-01-10 22:21:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #23404 from wxy/20210929-Manage-CentOS-Stream-with-Foreman

Browse Source 
TSL&PRF:sources/tech/20210929 Manage CentOS Stream with Foreman.md
This commit is contained in:
Xingyu.Wang 2021-09-30 13:41:36 +08:00 committed by GitHub
commit 9de3b1459c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 164 additions and 171 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

171
sources/tech/20210929 Manage CentOS Stream with Foreman.md
View File

@ -1,171 +0,0 @@
[#]: subject: "Manage CentOS Stream with Foreman"
[#]: via: "https://opensource.com/article/21/9/centos-stream-foreman"
[#]: author: "Melanie Corr https://opensource.com/users/melanie-corr"
[#]: collector: "lujun9972"
[#]: translator: "wxy"
[#]: reviewer: " "
[#]: publisher: " "
[#]: url: " "
Manage CentOS Stream with Foreman
======
This example provides a glimpse into the many options you have to manage
and provision CentOS Stream content in Foreman.
![Puzzle pieces coming together to form a computer screen][1]
In December 2021, CentOS 8 will reach end of life and be replaced by CentOS Stream. One of the major changes between previous iterations of CentOS and CentOS Stream is the lack of minor versions. Centos Stream has adopted a continuous release cycle. From the beginning of this year, developers in the Foreman community started to see the benefits of earlier bug detection and patching that CentOS Stream offers as a result of the continuous releases. We no longer have to wait for the next release to take advantage of the latest changes and bugfixes. [A veteran Linux community enthusiast][2] noted that this move also brings RHEL developers closer than ever to the FOSS community.
However, if you are an administrator of hundreds or thousands of servers, you might want to exercise control over when new packages are added to particular servers. If you are looking for a free open source tool that helps you ensure stability of production servers, while at the same time allowing you to safely pull in the latest changes from Centos Stream for development and testing, this is where Foreman can help. With Foreman, you can manage your Centos Stream content at all stages of the lifecycle environment.
### What is Foreman?
Foreman is a complete lifecycle management tool for physical and virtual servers. With Foreman, system administrators have the power to easily automate repetitive tasks, quickly deploy applications, and proactively manage servers on-premise or in the cloud. Foreman provides enterprise-level solutions for provisioning management, configuration management, and monitoring. Thanks to its plugin architecture, Foreman can be extended in a myriad of ways. Using the Katello plugin, you can use Foreman as a complete content management tool to manage CentOS Stream, among many other content types.
With Foreman and Katello, you can define exactly which packages you want each environment to contain. For example, a Production environment might use packages that have been verified as stable, while a Developer environment might require the latest and greatest package versions available. You can also promote the content views across lifecycle environments. Let's take a look at how Foreman accomplishes this.
We reference the web UI in this article, but Foreman also has a robust CLI and API. The Katello plugin provides a workflow and web UI for the Pulp project, which you can read about more in [this article][3]. We also supply a simple workflow here, but Foreman and the Katello project offer many different configuration options to suit your specific needs.
This article assumes that Foreman and Katello are already installed. For more information about how to do that, see the [Katello installation manual][4].
### Create a Product
The first step is to create a product in Foreman. The product functions as an internal label to store the CentOS Stream repositories.
1. In the Foreman web UI, navigate to **Content** >**Products**, and click **Create Product**.
2. In the **Name** field, enter a name for the product. Foreman automatically completes the **Label** field based on what you have entered for **Name, **and this can't be changed later.
### Add the CentOS Stream repositories to the Product
Now that you have a product, you can use the URLs for the AppStream and BaseOS repositories and add them to your new product.
1. In the Foreman web UI, navigate to **Content** > **Products**, select the product you want to use, and then click **New Repository**.
2. In the **Name** field, enter a name for the repository; for example, **Centos8StreamBaseOS**. Foreman automatically completes the **Label** field based on what you have entered for **Name**.
3. From the **Type** list, select the type of repository, and then select **Yum**.
4. In the **URL** field, enter the URL of the CentOS Stream Baseos repository to use as a source: <http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os/>
5. Select the **Download Policy** list. The default is **On Demand** \- this means that Katello will only download metadata. If you want to download all the packages, change to **Immediate**, which downloads all the packages, which might run into 20-30 GB.
6. Ensure that the **Mirror on Sync** check box is selected. This option ensures that content that is no longer part of the upstream repository is removed during synchronization.
7. Click **Save**.
Repeat these steps to add the AppStream repositories with URLs, for example, <http://mirror.centos.org/centos/8-stream/AppStream/x86_64/os/>. Ensure that you use the closest official CentOS mirror instead.
To perform an immediate synchronization, in your product window, click **Sync Now**. The initial synchronization can take some time. You can watch the synchronization status from **Content &gt; Sync Status.**
After the synchronization completes, you can view the new CentOS Stream operating system in **Hosts &gt; Operating System**. Feel free to edit the name and description to suit your requirements.
If you plan to use configuration management software like Ansible or Puppet, Foreman automatically creates an operating system report. You can turn this option off in **Administe &gt; Settings &gt; Ignore facts for operating system**. It is a good idea to rename the operating system to match the name in the configuration management software. For example, for Puppet, this would be _CentOS 8_.
### Define your infrastructure's Lifecycle Environment
The application life cycle is a concept central to Foreman's content management functions. The application life cycle defines how a particular system and its software look at a specific stage. For example, an application life cycle might be simple; you might only have a _development_ stage and _production_ stage. Foreman provides methods to customize each application life cycle stage in a controlled manner to suit your specifications.
At this point, you must create your lifecycle environment paths:
1. In the Foreman web UI, navigate to **Content** &gt;**Lifecycle Environments**.
2. Click **New Environment Path** to start a new application life cycle.
3. In the **Name** field, enter a name for your environment.
4. In the **Description** field, enter a description for your environment.
5. Click **Save**.
6. Add as many environment paths as you need. For example, you can create _dev_, _test,_ _stage,_ and _production_ environments. To add these environments, click **Add New Environment**, complete the **Name** and **Description** fields, and select the prior environment from the **Prior Environment** list so that you chain them together in the sequence you expect to use.
### Create and publish a Content View
In Foreman, a Content View is a snapshot of your repositories at a particular point in time. Content Views provide the mechanism for isolating package versions in a state that you want to preserve. Content Views have a lot of configurable features that you can use for further refinement. For the purposes of this tutorial, let's keep things simple.
1. In the Foreman web UI, navigate to **Content** &gt; **Content Views** and click **Create New View**.
2. In the **Name** field, enter a name for the view. Foreman automatically completes the **Label** field from the name you enter.
3. In the **Description** field, enter a description of the view.
4. Click **Save** to create the Content View.
5. In your new Content View, click **Yum Content &gt; Add Repositories** in the **Repository Selection** area, click **Add.** For both the BaseOS and Appstream repositories, select packages you want to include, then click **Add Repositories**.
6. Click **Publish New Version** and in the **Description** field, enter information about the version to log changes.
7. Click **Save**.
When you click **Publish New Version**, you create a snapshot of all the content that you have synchronized. This means that every server you subscribe to this Content View will have access only to the package versions in the Content View associated with this lifecycle environment.
Every new Content View and subsequent versions are published first to the Library environment, where you can then promote to additional environments.
### Promote content across lifecycle environments
If you have tested new packages and are satisfied that everything is stable, you can promote your Content View to another lifecycle environment.
1. Navigate to **Content** &gt; **Content Views** and select the Content View that you want to promote.
2. Click the **Versions** tab for the Content View.
3. Select the version you want to promote, and in the **Actions** column, click **Promote**.
4. Select the environment where you want to promote the Content View and click **Promote Version**.
5. Click the **Promote** button again. This time select the lifecycle environment, for example, **Test**, and click **Promote Version**.
6. Finally, click on the **Promote** button again. For example, select the **Production** environment and click **Promote Version**.
The servers that are assigned to that particular environment can now pull from an updated set of packages.
### Create an Activation Key
To register a CentOS Stream server to the content you have defined in a particular lifecycle, you must create an activation key. The activation key is a secure method of sharing credentials with a server. This uses a tool called **subscription-manager** to subscribe the CentOS Stream server to the content.
When you have created the activation key, add the CentOS Stream subscription to the activation key.
1. In the Foreman web UI, navigate to **Content &gt; Activation keys** and click **Create Activation Key**.
2. In the **Name** field, enter the name of the activation key.
3. In the **Description** field, enter a description for the activation key.
4. From the **Environment** list, select the environment to use.
5. From the **Content View** list, select the Content View you created just now.
6. Click **Save**.
### Create a CentOS Stream Host from Foreman managed content
Everything is now set up. With the content you have created contained in a content view, and promoted across lifecycles, you can now provision hosts with exactly the content you want to use and subscribe to the updates you want them to receive.
To create a host in Foreman, navigate to **Hosts &gt; Create Host**.
1. In the **Name** field, enter a name for the host.
2. Click the **Organization** and **Location** tabs to ensure that the provisioning context is automatically set to the current context.
3. From the **Deploy On** list, select **Bare Metal**.
4. Click the **Operating System** tab.
5. From the **Architectures** list, select **x86_64**.
6. From the **Operating System** list, select **CentOS_Stream 8.**
7. Check the **Build Mode** box.
8. For **Media Selection**, select **Synced Content** to use the CentOS Stream content you synced previously.
9. From the **Synced** **Content** list, ensure that CentOS Stream is selected.
10. From the **Partition Table** list, for this demo, select **Kickstart** default, but there are many available options.
11. In the **Root Password** field, enter a root password for your new host.
12. Click the **Interface** tab, and click **Edit,** and add a **Mac address.**
13. Click the **Parameters** tab, and ensure that a parameter exists that provides an activation key. If not, add an activation key.
14. Click **Submit** to save the host entry.
Now the new host is in build mode, which means when you turn it on, it will begin installing the operating system.
If you navigate to **Hosts &gt; Content Hosts,** you can see the full details of the subscriptions, lifecycle environment, and content view that your host is subscribed to.
This example is only a small glimpse into the many options you have to manage and provision CentOS Stream content in Foreman. If you want more detailed information about how you can manage CentOS Stream versions, control the content that your servers have access to, and control and protect the stability of your infrastructure, check out the [Foreman Content Management][5] documentation. With all CentOS Stream content under your control, you can create and register Centos Streams that consume only the content that you specify. For more detailed information on provisioning, see the [Foreman Provisioning][6] documentation. If you have any questions, feedback, or suggestions, you can find the Foreman community at <https://community.theforeman.org/>
--------------------------------------------------------------------------------
via: https://opensource.com/article/21/9/centos-stream-foreman
作者：[Melanie Corr][a]
选题：[lujun9972][b]
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://opensource.com/users/melanie-corr
[b]: https://github.com/lujun9972
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/puzzle_computer_solve_fix_tool.png?itok=U0pH1uwj (Puzzle pieces coming together to form a computer screen)
[2]: https://twitter.com/Det_Conan_Kudo/status/1337366036023218177?s=20
[3]: https://opensource.com/article/20/8/manage-repositories-pulp
[4]: https://docs.theforeman.org/3.0/Installing_Server_on_Red_Hat/index-katello.html
[5]: https://docs.theforeman.org/master/Content_Management_Guide/index-foreman.html
[6]: https://docs.theforeman.org/master/Provisioning_Guide/index-foreman.html

164
translated/tech/20210929 Manage CentOS Stream with Foreman.md Normal file
View File

@ -0,0 +1,164 @@
[#]: subject: "Manage CentOS Stream with Foreman"
[#]: via: "https://opensource.com/article/21/9/centos-stream-foreman"
[#]: author: "Melanie Corr https://opensource.com/users/melanie-corr"
[#]: collector: "lujun9972"
[#]: translator: "wxy"
[#]: reviewer: "wxy"
[#]: publisher: " "
[#]: url: " "
用 Foreman 管理 CentOS Stream
======
> 这个例子让我们看到了在 Foreman 中管理和配置 CentOS Stream 内容的许多选项。
![拼图拼成的电脑屏幕][1]
2021 年 12 月，CentOS 8 将达到生命终点，被 CentOS Stream 取代。CentOS Stream 和 CentOS 之前的迭代之间的主要变化之一是没有小版本。Centos Stream 采用了一个连续的发布周期。从今年年初开始，Foreman 社区的开发者开始看到 CentOS Stream 由于持续发布而提供的更早的错误检测和补丁的好处。我们不再需要等待下一个版本来利用最新的变化和错误修复。[一位资深的 Linux 社区爱好者][2] 指出，此举也使 RHEL 开发者比以往更接近 FOSS 社区。
然而，如果你是一个拥有数百或数千台服务器的管理员，你可能想控制新的软件包何时被添加到特定的服务器。如果你正在寻找一个免费的开源工具，帮助你确保生产服务器的稳定性，同时允许你安全地从 Centos Stream 中拉入最新的变化用于开发和测试，这就是 Foreman 可以帮助你的地方。有了 Foreman，你可以在生命周期环境的各个阶段管理你的 Centos Stream 内容。
### Foreman 介绍
Foreman 是一个完整的物理和虚拟服务器的生命周期管理工具。有了 Foreman，系统管理员有能力轻松实现重复性任务的自动化，快速部署应用程序，并主动管理内部或云中的服务器。Foreman 为<ruby>配备<rt>provisioning</rt></ruby>管理、配置管理和监控提供了企业级解决方案。由于其插件架构，Foreman 可以以无数种方式进行扩展。使用 Katello 插件，你可以把 Foreman 作为一个完整的<ruby>内容管理<rt>content management</rt></ruby>工具来管理 CentOS Stream，以及其他许多内容类型。
通过 Foreman 和 Katello，你可以准确地定义你希望每个环境包含哪些软件包。例如，生产环境可能使用已被验证为稳定的软件包，而开发环境可能需要最新、最先进的软件包版本。你还可以跨生命周期环境推广<ruby>内容视图<rt>content view</rt></ruby>。让我们来看看 Foreman 是如何完成这个任务的。
我们在这篇文章中使用了网页用户界面，但 Foreman 也有一个强大的 CLI 和 API。Katello 插件为 Pulp 项目提供了一个工作流和网页用户界面，你可以在 [这篇文章][3] 中了解更多。我们在这里也提供了一个简单的工作流程，但是 Foreman 和 Katello 项目提供了许多不同的配置选项来满足你的具体需求。
本文假设 Foreman 和 Katello 已经安装完毕。关于如何安装的更多信息，请参阅 [Katello 安装手册][4]。
### 创建一个产品
第一步是在 Foreman 中创建一个<ruby>产品<rt>product</rt></ruby>。该产品的功能是作为一个内部标签来存储 CentOS Stream 存储库。
1. 在 Foreman 网页用户界面，导航到“<ruby>内容<rt>Content</rt></ruby> > <ruby>产品<rt>Products</rt></ruby>”，并点击“<ruby>创建产品<rt>Create Product</rt></ruby>”。
2. 在“<ruby>名称<rt>Name</rt></ruby>”字段中，为产品输入一个名称。Foreman会根据你输入的“<ruby>名称<rt>Name</rt></ruby>”自动完成“<ruby>标签<rt>Label</rt></ruby>”字段，以后不能再更改。
### 将 CentOS Stream 存储库添加到产品中
现在你有了一个产品，你可以使用 AppStream 和 BaseOS 存储库的 URL，并将它们添加到你的新产品中。
1. 在 Foreman 网页用户界面中，导航到 “<ruby>内容<rt>Content</rt></ruby> > <ruby>产品<rt>Products</rt></ruby>”，选择你要使用的产品，然后点击 “<ruby>新存储库<rt>New Repository</rt></ruby>”。
2. 在“<ruby>名称<rt>Name</rt></ruby>”字段中，为存储库输入一个名称；例如，“Centos8StreamBaseOS”。Foreman 会根据你输入的“<ruby>名称<rt>Name</rt></ruby>”，自动完成“<ruby>标签<rt>Label</rt></ruby>”字段。
3. 从“<ruby>类型<rt>Type</rt></ruby>”列表中，选择存储库的类型，然后选择“Yum”。
4. 在 “URL” 字段中，输入 CentOS Stream Baseos 存储库的 URL，作为源： `http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os/`。
5. 选择“<ruby>下载规则<rt>Download Policy</rt></ruby>”列表。默认的是“<ruby>按需<rt>On Demand</rt></ruby>”，这意味着 Katello 将只下载元数据。如果你想下载所有的软件包，请改成“<ruby>即时<rt>Immediate</rt></ruby>”，它可以下载所有的软件包，可能会达到 20-30GB。
6. 确保“<ruby>与镜像同步<rt>Mirror on Sync</rt></ruby>”复选框被选中。这个选项确保在同步过程中，不再是上游存储库的一部分的内容被删除。
7. 点击“<ruby>保存<rt>Save</rt></ruby>”。
重复这些步骤，添加 AppStream 存储库及其 URL，例如，`http://mirror.centos.org/centos/8-stream/AppStream/x86_64/os/`。确保你使用最近的官方 CentOS 镜像来代替它。
要执行立即同步，在你的产品窗口，点击“<ruby>立即同步<rt>Sync Now</rt></ruby>”。最初的同步可能需要一些时间。你可以从“<ruby>内容<rt>Content</rt></ruby> > <ruby>同步状态<rt>Sync Status</rt></ruby>”查看同步状态。
同步完成后，你可以在“<ruby>主机<rt> Hosts</rt></ruby> > <ruby>操作系统<rt>Operating System</rt></ruby>”中查看新的 CentOS Stream 操作系统。请随意编辑名称和描述以满足你的要求。
如果你打算使用 Ansible 或 Puppet 等配置管理软件，Foreman 会自动创建一个操作系统报告。你可以在“<ruby>管理<rt>Administe</rt></ruby> > <ruby>设置<rt>Settings</rt></ruby> > <ruby>忽略操作系统状况<rt>Ignore facts for operating system</rt></ruby>”中关闭这个选项。重命名操作系统以匹配配置管理软件中的名称是一个好主意。例如，对于 Puppet，这将是“CentOS 8”。
### 定义你的基础设施的生命周期环境
应用程序生命周期是 Foreman 的内容管理功能的一个核心概念。应用程序的生命周期定义了一个特定的系统和它的软件在特定阶段的状况。例如，一个应用程序的生命周期可能很简单，你可能只有一个“开发”阶段和“生产”阶段。Foreman 提供了一些方法来以可控的方式定制每个应用生命周期阶段，以适应你的规范。
在这一点上，你必须创建你的生命周期环境路径。
1. 在 Foreman 网页用户界面中，导航到“<ruby>内容<rt>Content</rt></ruby> > <ruby>生命周期环境<rt>Lifecycle Environments</rt></ruby>”。
2. 点击“<ruby>新环境路径<rt>New Environment Path</rt></ruby>”，开始一个新的应用生命周期。
3. 在“<ruby>名称<rt>Name</rt></ruby>”字段中，为你的环境输入一个名称。
4. 在“<ruby>描述<rt>Description</rt></ruby>”字段中，为你的环境输入一个描述。
5. 点击“<ruby>保存<rt>Save</rt></ruby>”。
6. 根据你的需要添加尽可能多的环境路径。例如，你可以创建“dev”、“test”、“stage” 和 “production” 环境。要添加这些环境，点击“添加新环境”，完成“<ruby>名称<rt>Name</rt></ruby>”和“<ruby>描述<rt>Description</rt></ruby>”字段，并从“<ruby>优先环境<rt>Prior Environment*</rt></ruby>”列表中选择先前的环境，这样你就可以按照你预期使用的顺序将它们串联起来。
### 创建和发布一个内容视图
在 Foreman 中，“<ruby>内容视图<rt>Content View</rt></ruby>”是你的存储库在某个特定时间点的快照。内容视图提供了隔离软件包版本到你想保留的状态的机制。内容视图有很多可配置的功能，你可以用它来进一步细化。为了本教程的目的，让我们保持简单。
1. 在 Foreman 网页用户界面中，导航到“<ruby>内容<rt>Content</rt></ruby> > <ruby>内容视图<rt>Content View</rt></ruby>”，并点击“<ruby>创建新视图<rt>Create New View</rt></ruby>”。
2. 在“<ruby>名称<rt>Name</rt></ruby>”字段中，为视图输入一个名称。Foreman 会根据你输入的名称自动完成“<ruby>标签<rt>Label</rt></ruby>”字段。
3. 在“<ruby>描述<rt>Description</rt></ruby>”字段中，输入视图的描述。
4. 单击“<ruby>保存<rt>Save</rt></ruby>”以创建内容视图。
5. 在新的内容视图中，点击“<ruby>Yum 内容<rt>Yum Contents</rt></ruby> > <ruby>添加存储库<rt>Add Repositories</rt></ruby>”，在“<ruby>存储库选择<rt>Repository Selection</rt></ruby>”区域，点击“<ruby>添加<rt>Add</rt></ruby>”。对于 BaseOS 和 Appstream 存储库，选择你想包括的软件包，然后点击“<ruby>添加存储库<rt>Add Repositories</rt></ruby>”。
6. 点击“<ruby>发布新版本<rt>Publish New Version</rt></ruby>”，在“<ruby>描述<rt>Description</rt></ruby>”区域，输入关于版本的信息以记录变化。
7. 单击“<ruby>保存<rt>Save</rt></ruby>”。
当你点击“<ruby>发布新版本<rt>Publish New Version</rt></ruby>”时，你创建了一个你已同步的所有内容的快照。这意味着你订阅此内容视图的每台服务器将只能访问与此生命周期环境相关的内容视图中的软件包版本。
每一个新的内容视图和后续版本都会首先发布到库环境，然后你可以在那里推广到其他环境。
### 跨生命周期环境推广内容
如果你已经测试了新的软件包，并且确信一切都很稳定，你可以把你的内容视图推广到另一个生命周期环境中。
1. 导航到“<ruby>内容<rt>Content</rt></ruby> > <ruby>内容视图<rt>Content Views</rt></ruby>”，选择你想推广的内容视图。
2. 点击内容视图的“<ruby>版本<rt>Versions</rt></ruby>”标签。
3. 选择你想推广的版本，并在“<ruby>操作<rt>Action</rt></ruby>”栏中，点击“<ruby>推广<rt>Promote</rt></ruby>”。
4. 选择你要推广内容视图的环境，并点击“<ruby>推广版本<rt>Promote Version</rt></ruby>”。
5. 再次点击“<ruby>推广<rt>Promote</rt></ruby>”按钮。这次选择生命周期环境，例如，“Test”，然后单击“<ruby>推广版本<rt>Promote Version</rt></ruby>”。
6. 最后，再次点击“<ruby>推广<rt>Promote</rt></ruby>”按钮。例如，选择“Production”环境并点击“<ruby>推广版本<rt>Promote Version</rt></ruby>”。
被分配到该特定环境的服务器现在可以从一套更新的软件包中提取。
### 创建一个激活密钥
为了将 CentOS Stream 服务器注册到你在特定生命周期中定义的内容，你必须创建一个激活密钥。激活密钥是一种与服务器共享凭证的安全方法。这使用了一个叫做“<ruby>订阅管理器<rt>subscription-manager</rt></ruby>的工具来订阅 CentOS Stream 服务器的内容。
当你创建了激活密钥后，将 CentOS Stream 订阅添加到激活密钥中。
1. 在 Foreman 网页用户界面中，导航到“<ruby>内容<rt>Content</rt></ruby> > <ruby>激活密钥<rt>Activation keys</rt></ruby>”，并点击“<ruby>创建激活密钥<rt>Create Activation Key</rt></ruby>”。
2. 在“<ruby>名称<rt>Name</rt></ruby>”栏中，输入激活密钥的名称。
3. 在“<ruby>描述<rt>Description</rt></ruby>”栏中，输入激活密钥的描述。
4. 从“<ruby>环境<rt>Environment</rt></ruby>”列表中，选择要使用的环境。
5. 从“<ruby>内容视图<rt>Content View</rt></ruby>”列表中，选择你刚才创建的内容视图。
6. 点击“<ruby>保存<rt>Save</rt></ruby>”。
###从 Foreman 管理的内容中创建一个 CentOS Stream 主机
现在一切都准备好了。随着你创建的内容包含在内容视图中，并在整个生命周期中推广，你现在可以准确地用你想使用的内容来配置主机，并订阅你想让它们接收的更新。
要在 Foreman 中创建一个主机，请导航到“主机 > 创建主机”。
1. 在“<ruby>名称<rt>Name</rt></ruby>”字段中，为主机输入一个名称。
2. 单击“<ruby>组织<rt>Organization</rt></ruby>”和“<ruby>位置<rt>Location</rt></ruby>”选项卡，以确保配置环境自动设置为当前环境。
3. 从“<ruby>部署在<rt>Deploy On</rt></ruby>”列表中，选择“<ruby>裸金属<rt>Bare Metal</rt></ruby>”。
4. 单击“<ruby>操作系统<rt>Operating System</rt></ruby>”选项卡。
5. 从“<ruby>架构<rt>Architectures</rt></ruby>”列表中，选择“x86_64”。
6. 从“<ruby>操作系统<rt>Operating System</rt></ruby>”列表中，选择“CentOS_Stream 8”。
7. 勾选“<ruby>构建模式<rt>Build Mode</rt></ruby>”框。
8. 对于“<ruby>媒体选择<rt>Media Selection</rt></ruby>”，选择“<ruby>同步的内容<rt>Synced Content</rt></ruby>”来使用你之前同步的 CentOS Stream 内容。
9. 从“<ruby>同步的内容<rt>Synced Content</rt></ruby>”列表中，确保选择 “CentOS Stream”。
10. 从“<ruby>分区表<rt>Partition Table</rt></ruby>”列表中，对于这个演示，选择默认的 “Kickstart”，但有许多可用的选项。
11. 在“<ruby>Root 密码<rt>Root Password</rt></ruby>”栏中，为你的新主机输入一个 root 密码。
12. 点击“<ruby>接口<rt>Interface</rt></ruby>”标签，并点击“<ruby>编辑<rt>Edit</rt></ruby>”，并添加一个 “<ruby>Mac 地址<rt>Mac address</rt></ruby>”。
13. 点击“<ruby>参数<rt>Parameters</rt></ruby>”标签，并确保存在一个提供激活密钥的参数。如果没有，添加一个激活密钥。
14. 点击“<ruby>提交<rt>Submit</rt></ruby>”以保存主机条目。
现在，新的主机处于构建模式，这意味着当你打开它时，它将开始安装操作系统。
如果你导航到“<ruby>主机<rt>Hosts</rt></ruby> > <ruby>内容主机<rt>Content Hosts</rt></ruby>”，你可以看到你的主机所订阅的订阅、生命周期环境和内容视图的全部细节。
这个例子只是对你在 Foreman 中管理和配置 CentOS Stream 内容的众多选项的一个小窥视。如果你想了解更多关于如何管理 CentOS Stream 版本，控制你的服务器可以访问的内容，以及控制和保护你的基础设施的稳定性的详细信息，请查看 [Foreman 内容管理][5] 文档。当所有 CentOS Stream 内容在你的控制之下时，你可以创建和注册 Centos Stream，只使用你指定的内容。有关配备的更多详细信息，请参见 [Foreman 配备][6] 文档。如果你有任何问题、反馈或建议，你可以在 <https://community.theforeman.org/> 找到 Foreman 社区。
--------------------------------------------------------------------------------
via: https://opensource.com/article/21/9/centos-stream-foreman
作者：[Melanie Corr][a]
选题：[lujun9972][b]
译者：[wxy](https://github.com/wxy)
校对：[wxy](https://github.com/wxy)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://opensource.com/users/melanie-corr
[b]: https://github.com/lujun9972
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/puzzle_computer_solve_fix_tool.png?itok=U0pH1uwj (Puzzle pieces coming together to form a computer screen)
[2]: https://twitter.com/Det_Conan_Kudo/status/1337366036023218177?s=20
[3]: https://opensource.com/article/20/8/manage-repositories-pulp
[4]: https://docs.theforeman.org/3.0/Installing_Server_on_Red_Hat/index-katello.html
[5]: https://docs.theforeman.org/master/Content_Management_Guide/index-foreman.html
[6]: https://docs.theforeman.org/master/Provisioning_Guide/index-foreman.html