Satellite 6 - Deprecated API calls

Latest response

Does anyone on the Satellite Team have a "solution" for the API calls that are marked as deprecated? Some of these are pretty handy, and I don't want to waste a bunch of time coding them into something then have to re-engineer it later on when these calls disappear.

TIA

System errata

Resource Description
GET /katello/api/systems/:system_id/errata DEPRECATED List errata available for the content host
PUT /katello/api/systems/:system_id/errata/apply DEPRECATED Schedule errata for installation
GET /katello/api/systems/:system_id/errata/:id DEPRECATED Retrieve a single errata for a system
System packages

Resource Description
PUT /katello/api/systems/:system_id/packages/install DEPRECATED Install packages remotely
PUT /katello/api/systems/:system_id/packages/upgrade DEPRECATED Update packages remotely
PUT /katello/api/systems/:system_id/packages/upgrade_all DEPRECATED Update packages remotely
PUT /katello/api/systems/:system_id/packages/remove DEPRECATED Uninstall packages remotely
Systems

Resource Description
GET /katello/api/systems DEPRECATED List content hosts
POST /katello/api/systems/post_index DEPRECATED List content hosts when you have a query string parameter that will cause a 414.
GET /katello/api/organizations/:organization_id/systems DEPRECATED List content hosts in an organization
GET /katello/api/environments/:environment_id/systems DEPRECATED List content hosts in environment
GET /katello/api/host_collections/:host_collection_id/systems DEPRECATED List content hosts in a host collection
POST /katello/api/systems DEPRECATED Register a content host
POST /katello/api/environments/:environment_id/systems DEPRECATED Register a content host in environment
POST /katello/api/host_collections/:host_collection_id/systems DEPRECATED Register a content host in environment
PUT /katello/api/systems/:id DEPRECATED Update content host information
GET /katello/api/systems/:id DEPRECATED Show a content host
GET /katello/api/systems/:id/available_host_collections DEPRECATED List host collections the content host does not belong to
DELETE /katello/api/systems/:id DEPRECATED Unregister a content host
GET /katello/api/systems/:id/packages DEPRECATED List packages installed on the content host
PUT /katello/api/systems/:id/refresh_subscriptions DEPRECATED Trigger a refresh of subscriptions, auto-attaching if enabled
GET /katello/api/environments/:environment_id/systems/report DEPRECATED Get content host reports for the environment
GET /katello/api/organizations/:organization_id/systems/report DEPRECATED Get content host reports for the organization
GET /katello/api/systems/:id/pools DEPRECATED List pools a content host is subscribed to
GET /katello/api/systems/:id/releases DEPRECATED Show releases available for the content host
GET /katello/api/systems/:id/events List Candlepin events for the content host

Responses

Anyone? Just checked the Katello Documentation and I can see that the API calls are still supported in katello 2.4, so they are obviously still supported upstream.

http://www.katello.org/docs/2.4/api/index.html

I am also interested in this topic Will, perhaps raising a support case will get you the answer you need more promptly?

We had a support case open for a specific set of queries, and during the course of that conversation we asked about the desecrated calls, but were told they didn't see any mention of the deprecation in the documentation. I opened a case this morning to specifically question the documentation. (01575295) I figured with Rich and the other Satellite team members occasionally perusing these questions (and a few emails to specific team members) I would have gotten an answer from one of them by now.

Man I know we've all heard this already.. but in case you are following along

"....there would be replacement for those deprecated calls in 6.2" - Red Hat Support

6.2.0 is apparently going to have all the things..

I'd add a little more color to this statement. As part of the 'Host Unification' feature of 6.2, we are unifying the underlying database entries for both content (Katello) & configuration (Foreman).

In Satellite 6.0 and 6.1, a registered host, depending on whether it was registered for content or config (or both) was represented as either a content-host or a host. This makes it difficult to do a lot of things (especially via the API) as there isn't 'one source of truth' that defines a host. This makes it challenging to add new features. And confusing as a user since 'All Hosts' didn't actually mean 'every system registered to Satellite regardless of how it is managed'. (It really means 'All Hosts that are under configuration management). Plus if you are an API user, you have to get content stuff from /katello/api/systems, and the rest from /api/v2/hosts, which is painful at best.

In Satellite 6.2, the content related attributes (such as subscriptions and the like) become part of host object. (and will be accessible via /api/v2/hosts).

Rich thanks for the feedback. Looking forward to seeing 'Host Unification' in action and not having to reference two separate API's either!!!

Hi Rich,

is there any word on a Beta or GA date for Satellite 6.2? These features would be very useful as are the other items proposed to be included.

Doug

Doug,

I have been told through support "ETA for Satellite 6.2 is Q2 2016", not sure if this suggests April or June delivery of GA. I have also asked about access to a 6.2 Beta and been told it isn't currently possible.

This is correct. Normally a beta (for existing Satellite customers & selected non-Satellite customers) is released ~45-60 days prior to GA.

Rich,

I appreciate you sharing this information about planned features on the forum, but I am concerned there isn't a more formal way to get visibility into the Satellite 6.2 roadmap.

When planning implementations for customers, it's useful to know what to expect (and when). Would it be possible for Red Hat to start a Satellite 6.2 development blog? or at least provide a more comprehensive list of expected features like you have in this post?

The problem I am finding is that Satellite 6.x discussion, bugs and feature requests etc. are private in Bugzilla.

I would hate for the Satellite team to overcommit to certain goals for 6.2 and then everyone be upset that they didn't meet those goals, but by the same token a lot of us are waiting for 6.2 because we 'hear' about certain things we need in order to proceed with our production implementations. Some sort of discussion or blog around what is coming would be nice.

Dave Caplan gave a nice presentation at Summit on Satellite and highlighted some of the things that would be coming in 6.2 (last slide) but I think this list might be a bit dated now.

https://videos.cdn.redhat.com/summit2015/presentations/13706_red-hat-satellite-6-roadmap-demonstration.pdf

There a few ways that you can stay 'in the know' with regards to Satellite development / roadmap.

On the direct customer side, reach out to your account team for an updated roadmap session.

On the partner side, our partner/channel account team is probably the best resource.

Visit us at a Customer Convergence Event

Today, we have the Red Hat Satellite Blog, which we've used primarily for major announcements. We have plans in the very near term to expand the frequency and topics that we blog about.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.