Red Hat NETWORK PROXY SERVER 3.7 - Technické informace

Procházejte online nebo si stáhněte Technické informace pro Servery Red Hat NETWORK PROXY SERVER 3.7 -. Red Hat NETWORK PROXY SERVER 3.7 - System information Uživatelská příručka

  • Stažení
  • Přidat do mých příruček
  • Tisk

Shrnutí obsahu

Strany 1 - Transition Guide

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

Strany 2

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

Strany 3

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

Strany 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

Strany 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

Strany 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

Strany 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

Strany 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

Strany 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

Strany 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

Strany 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

Strany 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.

Strany 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

Strany 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.

Strany 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

Strany 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

Strany 18 - Report a bug

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

Strany 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

Strany 20 - Important

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

Strany 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

Strany 22

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

Strany 23

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

Strany 24

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

Strany 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

Strany 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

Strany 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

Strany 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

Strany 29

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

Strany 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

Strany 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

Strany 32

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

Strany 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

Strany 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

Strany 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

Strany 36

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

Strany 37

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

Strany 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

Strany 39

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

Strany 40

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

Strany 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

Strany 42

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

Strany 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

Strany 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

Strany 45

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

Strany 46

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

Strany 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

Strany 48

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

Strany 49

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

Strany 50

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

Strany 51

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

Strany 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

Strany 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

Strany 54

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

Strany 55

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

Strany 56

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

Strany 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

Strany 58

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

Strany 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

Strany 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

Strany 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

Strany 62

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

Strany 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

Komentáře k této Příručce

Žádné komentáře