Red Hat Summit Red Hat Summit지원콘솔개발자평가판 시작연락처

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 3. Monthly Patching Example

This chapter explains how to use Satellite to deploy errata to systems each month. In this example, we assume that we are patching systems in March of 2016.

Note

This procedure replicates the functionality of the spacewalk-clone-by-date command that was present in Satellite 5, and was described in this document written by Rich Jerrido: Satellite 5.6 Errata Management Guide. The command-line tool hammer is used in Satellite 6 to perform the same functions that the spacewalk-clone-by-date command performed in Satellite 5.

3.1. Defining a Content View to Filter Errata
링크 복사

In this procedure, we create a Content View, add a filter to the Content View to include the errata in the Content View, and then restrict the filter by date by means of a filter rule.

  1. Create a Content View. 

    # hammer -p PASSWORD content-view create --name='test_cv' --organization="Default Organization"
    Copy to Clipboard Toggle word wrap
    Note

    The previous command passes the password in plaintext. This method is included in this guide for the sake of customers who are used to this method of authentication, but a more secure method of storing passwords, involving the storage of the password in a .yml file, is recommended to our customers and is to be found here: Authentication in the Hammer CLI Guide.

  2. Create a filter for the errata. 

    # hammer -p PASSWORD content-view filter create --name='test_filter' --organization="Default Organization" --content-view='test_cv' --type=erratum
    Copy to Clipboard Toggle word wrap

  3. Create the filter rule with the date.

    In this example, the date is 30 Mar 2016. This rule means that all errata on or after 30 Mar 2016 will be excluded. 

    # hammer -p PASSWORD content-view filter rule create --content-view='filter_test'  --organization="Default Organization"  --content-view-filter='my-filter' --start-date=2016-03-30  --types=security,enhancement,bugfix
    Copy to Clipboard Toggle word wrap

  4. Promote the Content View to the lifecycle environment so that the errata in it are available to that lifecycle environment: 

    $ hammer content-view version promote
  --content-view cv_name \
  --organization-label="Default Organization" --to-lifecycle-environment env_name
    Copy to Clipboard Toggle word wrap

  5. Use the following command to add a repository to a Content View without clobbering the existing list of repositories that have been added to that Content View: 

    $ hammer content-view add-repository --organization-label org_label --name cv_name --repository-id repo_ID
    Copy to Clipboard Toggle word wrap

  6. Apply the errata to the host, using the commands in the Hammer CLI Guide: 

    $ hammer host errata apply --host <hostname> --errata-ids <erratum_ID1>,<erratum_ID2>...
    Copy to Clipboard Toggle word wrap

    For more detail on commands that apply errata to hosts, see Applying Errata to a Content Host in the Hammer CLI Guide.

맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat