Red Hat NETWORK PROXY SERVER 3.7 - Informacje Techniczne

Przeglądaj online lub pobierz Informacje Techniczne dla Serwery Red Hat NETWORK PROXY SERVER 3.7 -. Red Hat NETWORK PROXY SERVER 3.7 - System information Instrukcja obsługi

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj

Podsumowanie treści

Strona 1 - Transition Guide

Red Hat Satellite Documentation TeamRed Hat Satellite 6.0Transition GuideTransitioning from Satellite 5 to Satellite 6

Strona 2

Chapter 2. Comparing Satellite 5 and Satellite 6This chapter explores the differences between Red Hat Satellite 5 and Red Hat Satellite 6, especiallyi

Strona 3

Configuration ConfigurationChannelsPuppet RepositoriesProxy services Red HatSatellite Proxy ServerRed HatSatellite Capsule ServerCommand-line tools Va

Strona 4 - Abstract

The Web UI runs through an Apache web server and provides the main entry point forSatellite operations.⁠Fro n t - end APIThe Front-end API provides t

Strona 5 - Table of Contents

⁠Fo remanForeman is an open source application used for provisioning and life cycle management ofphysical and virtual systems. Foreman automatically c

Strona 6

Satellite 6. Instead, Satellite 6 introduces the concept of Capsules, which provide much the samefunctionality.Report a bug2.2.2. Satellit e 6 Capsule

Strona 7 - 1.2. We Need Feedback!

organizations. This is useful for companies with multiple divisions, such a Finance, Marketing,Sales, and so forth. Each organization acts as an indiv

Strona 8 - 1.2. Red Hat Sat ellit e 6

Figu re 2.5. Examp le T o p o lo g y f o r Red Hat Sat ellite 6The main Satellite server retains the management function, while the content and conf

Strona 9

Figu re 2.6 . The Ap p licat io n Lif e Cycle of Red Hat Sat ellite 5The Red Hat Satellite 6 application life cycle is broken up into two key comp

Strona 10

Figu re 2.8. Creat ing New Versio n s of a Co n t ent ViewPublished content views are used with life cycle environments.Report a bugRed Hat Sat el

Strona 11 - 2.1. Syst em Archit ect ures

Chapter 3. Transitioning from Satellite 5 to 6This chapter describes the prerequisites for performing a successful transition from Red HatSatellite 5

Strona 13 - 2.2.1. Satellit e 5 Proxies

Ensure you start with a fully-functional, up-to-date Satellite 5.6 server.Satellite 6 must be correctly installed and configured on a second machine.

Strona 14 - 2.2.2. Satellit e 6 Capsules

# hammer import organization --csv-file /tmp/exports/users.csv --upload-manifests-from /root/manifest-dirPerf o rming t h e T ran sit ionAfter you ha

Strona 15

Upon the future release of Satellite 5.7, it too will be supported as a platform for moving fromSatellite 5 to 6.Upon future releases of Satellite (6.

Strona 16 - 2.4. Applicat ion Life Cycles

NoteNot all of the concepts can be translated between Satellite 5 and 6. Some manual stepsare required to fully populate the newly installed Satellite

Strona 17

Can I use t h e exp o rt t o o ls o n my pro d u ct ion Sat ellite 5.6 syst em?Yes, assuming that you run the tools with sufficient disk space. Di

Strona 18 - Report a bug

activation-keyschannelsconfig-files-latestkickstart-scriptsrepositoriessystem-profilesYou can run the spacewal k-repo rt command to confirm the additi

Strona 19

The expected work flow on the Satellite 5.6 server is to use the spacewal k-expo rt command as awrapper. This wrapper command calls the following comm

Strona 20 - Important

INFO: system-groups : System-groups for all organizationsINFO: config-files-latest : Latest revision of all configuration filesINFO: r

Strona 21

Report a bug3.6.2. T ransferring Export s t o Sat ellit e 6After you have successfully exported all the required entities from your Satellite 5 server

Strona 22

5. Import repositories.6. Import custom channels and cloned channels as content views.7. Import activation keys.8. Import kickstart snippets as te

Strona 23

Red Hat Satellite 6.0 Transition GuideTransitioning from Satellite 5 to Satellite 6Red Hat Satellite Documentatio n Team

Strona 24

# hammer shellhammer> import organization --csv-file /tmp/exports/users.csv --upload-manifests-from /root/manifests --verboseImporting from /tmp/ex

Strona 25

The hammer i mpo rt command logs all output to the ~ /i mpo rt. l o g file. You can use the --l o g fi l e option to any hammer i mpo rt subcommand t

Strona 26

Creating new user: sat5_adminCreating new user: auser1Creating new user: auser2To show the users were created, log in to the WebUI and navigate to Ad

Strona 27

Deleting imported user [8->6].Deleting imported user [9->7].Report a bug3.7.3. T ransit ioning Syst em Groups t o Host Collect ionsRed Hat Sate

Strona 28

Reco mmen d ed Practices fo r Syn chro n iz in g C o n t en tThe default behavior of the hammer i mpo rt repo si to ry command is to not automaticall

Strona 29

# hammer import repository --synchronize --wait --no-async \--csv-file /tmp/exports/repositories.csvCreating new product: PUPPETLABS.COMCreating new r

Strona 30

Report a bug3.7 .4 .2 . Enabling Red Hat Re po sit o riesThe Red Hat repositories are synchronized from the Red Hat Content Delivery Network (CDN).Be

Strona 31 - 3.7.2. Import ing Users

Report a bug3.7.5. T ransit ioning Cust om and Cloned Channels t o Cont ent ViewsRed Hat Satellite 5 uses the concept of cloned channels to restrict

Strona 32

Repository Local_repository_for_custom-clone-master-puppet-rhel6-server-x86_64 is not (fully) synchronized. Retry once synchronization has completed.P

Strona 33

Local_repository [1113->13] already imported.No such content_view: 102Creating new content_view: Clone of Red Hat Enterprise Linux Server (v. 6 for

Strona 34

Legal NoticeCo pyright © 20 14 Red Hat.This do cument is licensed by Red Hat under the Creative Co mmo ns Attributio n-ShareAlike 3.0Unpo rted Licen

Strona 35

You can use the hammer acti vati o n-key l i st --o rg ani zati o n-i d ORG-ID command toverify that the activation keys have been recreated. Ensure

Strona 36

Generate Puppet modules for each Satellite 5 configuration channel.Map any Satellite 5 macros in the configuration files to whatever Puppet facts are

Strona 37

In Satellite 6, this information is stored in Content Hosts. Instead of "system", Satellite 6 uses the term"host" to refer to any

Strona 38

An existing, up-to-date Red Hat Enterprise Linux client systems registered to SAT5.6.An existing, up-to-date Satellite 6 server. In this example, this

Strona 39

You have the necessary system transition packages installed on the Satellite 5 server. To ensurethese packages are installed, run the following comman

Strona 40

8. Configure puppet with the host name of the Satellite or Satellite Capsule that will manage itsconfiguration. In this example, $FQDN represents the

Strona 41

To learn how to unregister from either service please consult this Knowledge Base Article: https://access.redhat.com/kb/docs/DOC-45563The system has b

Strona 42

Chapter 4. Advanced TransitioningThis chapter covers some of the more advanced transitioning scenarios that you might encounter aspart of your deploym

Strona 43 - 3.7 .1 0 .2 . Assum pt io ns

This section provides a total of five different ways to achieve the same result; two examples forSatellite 5 and three examples for Satellite 6.A Sate

Strona 44

Usin g Pyt h o n t o List Available H o st s on Sat ellit e 6This example uses a Python script to connect to Satellite 6, authenticate, and retri

Strona 45

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Strona 46

 :password => $password, :headers => { :accept => :json, :content_type => :json } ).execute results = JSON

Strona 47 - 4.1. T ransit ioning APIs

The examples in this section describe different ways to locate, create, and delete users.Usin g Pyt h o n t o Man age Users on Sat ellite 5This ex

Strona 48

import jsonimport requests# Define Satellite location and login detailsSAT_API = "https://localhost/api/v2/"POST_HEADERS = {'conte

Strona 49

 id = str(id) delete = delete_json(SAT_API + "/users/" + id) #print json.dumps(delete, indent=4)

Strona 50

 :method => :delete, :url => location, :user => $username, :password => $password, :headers =>

Strona 51

adminexample# spacecmd -u admin -p password user_delete exampleINFO: Spacewalk Username: adminINFO: Connected to https://localhost/rpc/api as adminDel

Strona 52

Usin g t h e Command Lin e t o Man age Users on Satellit e 6This example uses the hammer command to perform the same task as the previous examples

Strona 53

If you have already logged in to the Satellite 6 WebUI, you can see the default results of GET requestsat /api/v2/<API-NAME>/. For example:https

Strona 54

# curl -k -u $SATUSER:$SATPASS -X PUT -d '{ "id": 10, "mail": "example@ localhost" }' -H 'Accept: applica

Strona 55

Glossary of TermsThe following terms are used throughout this document. Familiarize yourself with these terms to helpyour understanding of Red Hat Sat

Strona 56

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Strona 57

An External Node Classifier is a Puppet construct that provides additional data for a PuppetMaster to use when configuring Hosts. Red Hat Satellite 6

Strona 58

⁠O rg aniz atio nAn Organization is an isolated collection of systems, content, and other functionality within aSatellite 6 deployment.⁠PermissionThe

Strona 59 - Glossary of Terms

⁠St and ard O p erating En viron men t ( SO E)A Standard Operating Environment (SOE) is a controlled version of the operating system onwhich applic

Strona 60

Revision HistoryRevisio n 2- 02 Fri 21 No v 2014 At h ene ChanPublishing book for the November Async.Revisio n 2- 01 Wed 12 N o v 2014 David O &ap

Strona 61 - G lossary o f T erms

Preface1. Get t ing Help and Giving Feedback1.1. Do You Need Help?If you experience difficulty with a procedure described in this documentation, visit

Strona 62

Chapter 1. Introduction to Red Hat SatelliteThis chapter aims to help Red Hat Satellite 5 administrators understand and draw parallels withRed Hat Sat

Strona 63 - Revision History

systems during the provisioning process, and a much more simplified approach to life cyclemanagement. Satellite 6 also further evolves the inherent ap

Komentarze do niniejszej Instrukcji

Brak uwag