Red Hat NETWORK PROXY SERVER 3.7 - Informacje Techniczne Pobierz pdf (Strona 47)

Chapter 4. Advanced Transitioning

This chapter covers some of the more advanced transitioning scenarios that you might encounter as

part of your deployment and transition from Satellite 5 to Satellite 6. Each customer is likely to have

slightly different configurations; consequently, it is not possible to cover every scenario that might

arise. Over time, and with customer feedback and more development, coverage of more transition

scenarios may be possible.

4.1. T ransit ioning APIs

Among the many differences between Red Hat Satellite 5 and Satellite 6 are the APIs. Satellite 5 uses

an XMLRPC-based API. Satellite 6 uses a REST-based API. This fundamental difference requires that

any existing scripts or tools that have been integrated with the Satellite 5 API must be reviewed and at

least partially rewritten to call the new Satellite 6 REST APIs.

This section provides some comparisons of how to achieve the same use case within each product.

This is not designed to be a tutorial in any specific programming language, nor are the scripts

secured over HTTPS. They provide a starting point for anyone maintaining Satellite 5 API scripts to

start the transition to the Satellite 6 API.

Important

The Satellite 6 transition tools do not transition Satellite 5 APIs or scripts to Satellite 6. Use

this section as a starting point to begin your own transition process.

Fu rth er In f o rmat io n

You can find further API documentation at the following locations on your own Satellite servers:

Satellite 6: https://satellite6.example.com/apidoc/v2.html

Satellite 5: https://satellite5.example.com/rpc/api

You can also find the Satellite 5 and Satellite 6 API documentation on the Red Hat Customer Portal:

https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/

Report a bug

4 .1.1. Example API Script s

The examples in this section cover the following:

1. Systems and hosts in Red Hat Satellite

Authenticate and request a list of systems (Satellite 5) or hosts (Satellite 6) available to the

user who logged in.

2. Users and Roles

a. Authenticate and request a list of all users visible to the user who logged in.

b. Delete the exampl e user if it exists.

c. Create a new exampl e user and ensure that its role is set to Ad mi ni strato r.

⁠Chapt er 4 . Advanced T ransit ioning

4 3

1 2 ... 42 43 44 45 46 47 48 49 50 51 52 ... 62 63

Brak uwag

Red Hat NETWORK PROXY SERVER 3.7 - Informacje Techniczne Strona 47