Hey Guys, I do watch you for quite some time and I wanted to thank you for all the amazing content you put here on UA-cam :) got a question: How do you handling content view promotion to different lifecycle environments? Are U doing this manually or in an automated way and intervene only if problem occurs e.g. on dev so then it would not appear on prod servers? Because managing content view promotion manually seems to me like a lot of work, so just wanna know your real life experience. Thank you
Hello @Rich, could you explain a little more about the history of the 50 Red Hat Satellite Infrastructure Subscription licenses? I understand that these 50 licenses are intended to be used for capsule servers only? is that right? because I checked my subscription and found that they were used by normal vms! how can we prevent their use by other vms? Could you please explain the advantages to us? because it was not clear to me and I am about to install satellite 6.15 and I would like to follow your recommendations. THANKS
To limit satellite subscriptions used by regular RHEL servers, you can create a manifest to hold the subscriptions and make them unavailable to other hosts. Let's call the manifest HOLD. Follow these steps: Create a Subscription Manifest: Log in to the Red Hat Customer Portal. Navigate to the “Subscriptions” tab. Select “Subscription Allocations” and create a new allocation for your Satellite server. Add the required Red Hat Satellite Infrastructure subscriptions to this allocation you wish to make unavailable. As your infrastructure grows and you need more Satellite Infrastructure subscriptions, you can quickly move them from the HOLD manifest to your active manifest. This way, the subscriptions become available for your hosts to consume.
@@maikcat9723 RHEL8 still has ~5 years left on its normal 10 year lifecycle, then it will get some extended lifecycle as well (at least 2 years with an add-on subscription). So it’s still going to be supported by satellite for “a while”.
Thanks for the big up @eric!
Hey Guys, I do watch you for quite some time and I wanted to thank you for all the amazing content you put here on UA-cam :) got a question: How do you handling content view promotion to different lifecycle environments? Are U doing this manually or in an automated way and intervene only if problem occurs e.g. on dev so then it would not appear on prod servers? Because managing content view promotion manually seems to me like a lot of work, so just wanna know your real life experience. Thank you
Hello @Rich, could you explain a little more about the history of the 50 Red Hat Satellite Infrastructure Subscription licenses? I understand that these 50 licenses are intended to be used for capsule servers only? is that right? because I checked my subscription and found that they were used by normal vms! how can we prevent their use by other vms? Could you please explain the advantages to us? because it was not clear to me and I am about to install satellite 6.15 and I would like to follow your recommendations. THANKS
To limit satellite subscriptions used by regular RHEL servers, you can create a manifest to hold the subscriptions and make them unavailable to other hosts. Let's call the manifest HOLD. Follow these steps:
Create a Subscription Manifest:
Log in to the Red Hat Customer Portal.
Navigate to the “Subscriptions” tab.
Select “Subscription Allocations” and create a new allocation for your Satellite server.
Add the required Red Hat Satellite Infrastructure subscriptions to this allocation you wish to make unavailable.
As your infrastructure grows and you need more Satellite Infrastructure subscriptions, you can quickly move them from the HOLD manifest to your active manifest. This way, the subscriptions become available for your hosts to consume.
Hey Guys, where to find the satellite 6.15 http proxy config on the webui ?
foreman 3.13 will drop support for rhel8 , curious to see what redhat will do with satellite...
@@maikcat9723 RHEL8 still has ~5 years left on its normal 10 year lifecycle, then it will get some extended lifecycle as well (at least 2 years with an add-on subscription). So it’s still going to be supported by satellite for “a while”.