I'm looking to possibly use SAM for managing my RHEL subscriptions
locally. We are Foreman users, but are not interested in using a full
blown Katello installation at this time due to the fact that we can not
make it work with our existing Foreman deployment.
I'm looking at the SAM documentation [1] and noticed that it's actually
installing a version of Katello? What is the relationship between Katello
and the standalone SAM product offering? Is SAM going away (am I wasting
my time)?
SAM-1.4, which was released a year or so ago, is supported on RHEL6. It is based on the katello upstream project but before the merge with foreman.
When SAM-6 is released, it will still be based on katello but this time after the merge with foreman. The features of SAM are strictly limited to subscription management and basic content consumption. (There are no content views, no remote package installation, etc.) The release date of SAM-6 has not been published yet.
In terms of where to invest time, SAM-1.4 is a supported product. That said, if it were me I would try to get a copy of Sat-6.1 to use until SAM-6 is released since there will not be an in-place migration of SAM-1.4 to SAM-6. (Note that I am an engineer so do not have insights into how likely it is you could convince biz dev for a license.
Please let us know how you end up proceeding.
···
----- Original Message -----
> Hi,
>
> I'm looking to possibly use SAM for managing my RHEL subscriptions
> locally. We are Foreman users, but are not interested in using a full
> blown Katello installation at this time due to the fact that we can not
> make it work with our existing Foreman deployment.
>
> I'm looking at the SAM documentation [1] and noticed that it's actually
> installing a version of Katello? What is the relationship between Katello
> and the standalone SAM product offering? Is SAM going away (am I wasting
> my time)?
>
> Thanks,
>
> Josh
>
> [1]
> https://access.redhat.com/documentation/en-US/Red_Hat_Subscription_Management/1/html/Using_Subscription_Asset_Manager/SAM-Installation.html#Installation_Prerequisites
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
I have a similar query related to the relationship between SAM and Katello.
However, I am looking at how one would create a Red Manifest to import into
Katello. On the Red Hat portal it appears one has to create an
"Subscription Management Application". Of those there are two options
"Satellite" and "Subscription Asset Management Organization". My logic
tells me that we should use the latter since if we create a "Satellite"
instance we may be expected to pay for it. However, when trying to create
the SAM we have to enter the version. How would one find out, using Katello
tools, what the related version of SAM is at any point in time?
Also, can anyone clarify how SAM relates specifically to Katello and/or
Candlepin?
···
On Monday, June 15, 2015 at 9:56:50 AM UTC-5, Josh wrote:
>
> Hi,
>
> I'm looking to possibly use SAM for managing my RHEL subscriptions
> locally. We are Foreman users, but are not interested in using a full
> blown Katello installation at this time due to the fact that we can not
> make it work with our existing Foreman deployment.
>
> I'm looking at the SAM documentation [1] and noticed that it's actually
> installing a version of Katello? What is the relationship between Katello
> and the standalone SAM product offering? Is SAM going away (am I wasting
> my time)?
>
> Thanks,
>
> Josh
>
> [1]
> https://access.redhat.com/documentation/en-US/Red_Hat_Subscription_Management/1/html/Using_Subscription_Asset_Manager/SAM-Installation.html#Installation_Prerequisites
>
Thanks for the feedback! I think I'm going to skip SAM-1.4 all together,
and wait until SAM-6 is released. I would love to be able to just add this
functionality to my existing Foreman installation (as a plugin), so
hopefully that will be possible in the future as well. Sat 6.1 includes
"SAM-6," already, right?
Thanks
Josh
···
On Mon, Jun 15, 2015 at 11:30 AM, Tom McKay wrote:
----- Original Message -----
Hi,
I’m looking to possibly use SAM for managing my RHEL subscriptions
locally. We are Foreman users, but are not interested in using a full
blown Katello installation at this time due to the fact that we can not
make it work with our existing Foreman deployment.
I’m looking at the SAM documentation [1] and noticed that it’s actually
installing a version of Katello? What is the relationship between
Katello
and the standalone SAM product offering? Is SAM going away (am I wasting
my time)?
SAM-1.4, which was released a year or so ago, is supported on RHEL6. It is
based on the katello upstream project but before the merge with foreman.
When SAM-6 is released, it will still be based on katello but this time
after the merge with foreman. The features of SAM are strictly limited to
subscription management and basic content consumption. (There are no
content views, no remote package installation, etc.) The release date of
SAM-6 has not been published yet.
In terms of where to invest time, SAM-1.4 is a supported product. That
said, if it were me I would try to get a copy of Sat-6.1 to use until SAM-6
is released since there will not be an in-place migration of SAM-1.4 to
SAM-6. (Note that I am an engineer so do not have insights into how likely
it is you could convince biz dev for a license.
Do you know if SAM-6 is out yet? I still only see SAM-1.4 on the RH
website.
···
On Mon, Jun 15, 2015 at 11:30 AM, Tom McKay wrote:
----- Original Message -----
Hi,
I’m looking to possibly use SAM for managing my RHEL subscriptions
locally. We are Foreman users, but are not interested in using a full
blown Katello installation at this time due to the fact that we can not
make it work with our existing Foreman deployment.
I’m looking at the SAM documentation [1] and noticed that it’s actually
installing a version of Katello? What is the relationship between
Katello
and the standalone SAM product offering? Is SAM going away (am I wasting
my time)?
SAM-1.4, which was released a year or so ago, is supported on RHEL6. It is
based on the katello upstream project but before the merge with foreman.
When SAM-6 is released, it will still be based on katello but this time
after the merge with foreman. The features of SAM are strictly limited to
subscription management and basic content consumption. (There are no
content views, no remote package installation, etc.) The release date of
SAM-6 has not been published yet.
In terms of where to invest time, SAM-1.4 is a supported product. That
said, if it were me I would try to get a copy of Sat-6.1 to use until SAM-6
is released since there will not be an in-place migration of SAM-1.4 to
SAM-6. (Note that I am an engineer so do not have insights into how likely
it is you could convince biz dev for a license.
SAM is based off an earlier version of katello before the integration
with foreman. Most features have been disabled with the exception of
basic subscription management. As for the version of the manifest to
try, use the latest version you can see.
– bk
···
On 02/08/2016 02:26 PM, Lesley Kimmel wrote:
> All;
>
> I have a similar query related to the relationship between SAM and
> Katello. However, I am looking at how one would create a Red Manifest to
> import into Katello. On the Red Hat portal it appears one has to create
> an "Subscription Management Application". Of those there are two options
> "Satellite" and "Subscription Asset Management Organization". My logic
> tells me that we should use the latter since if we create a "Satellite"
> instance we may be expected to pay for it. However, when trying to
> create the SAM we have to enter the version. How would one find out,
> using Katello tools, what the related version of SAM is at any point in
> time?
>
> Also, can anyone clarify how SAM relates specifically to Katello and/or
> Candlepin?
>
There is no updated version of SAM available today.
– bk
···
On 02/08/2016 03:49 PM, Josh Baird wrote:
> Do you know if SAM-6 is out yet? I still only see SAM-1.4 on the RH
> website.
>
> On Mon, Jun 15, 2015 at 11:30 AM, Tom McKay > wrote:
>
>
>
> ----- Original Message -----
> > Hi,
> >
> > I'm looking to possibly use SAM for managing my RHEL subscriptions
> > locally. We are Foreman users, but are not interested in using a
> full
> > blown Katello installation at this time due to the fact that we
> can not
> > make it work with our existing Foreman deployment.
> >
> > I'm looking at the SAM documentation [1] and noticed that it's
> actually
> > installing a version of Katello? What is the relationship
> between Katello
> > and the standalone SAM product offering? Is SAM going away (am I
> wasting
> > my time)?
> >
> > Thanks,
> >
> > Josh
> >
> > [1]
> >
> https://access.redhat.com/documentation/en-US/Red_Hat_Subscription_Management/1/html/Using_Subscription_Asset_Manager/SAM-Installation.html#Installation_Prerequisites
> >
> > --
> > You received this message because you are subscribed to the
> Google Groups
> > "Foreman users" group.
> > To unsubscribe from this group and stop receiving emails from it,
> send an
> > email to foreman-users+unsubscribe@googlegroups.com
> .
> > To post to this group, send email to
> foreman-users@googlegroups.com .
> > Visit this group at http://groups.google.com/group/foreman-users.
> > For more options, visit https://groups.google.com/d/optout.
> >
>
> SAM-1.4, which was released a year or so ago, is supported on RHEL6.
> It is based on the katello upstream project but before the merge
> with foreman.
>
> When SAM-6 is released, it will still be based on katello but this
> time after the merge with foreman. The features of SAM are strictly
> limited to subscription management and basic content consumption.
> (There are no content views, no remote package installation, etc.)
> The release date of SAM-6 has not been published yet.
>
> In terms of where to invest time, SAM-1.4 is a supported product.
> That said, if it were me I would try to get a copy of Sat-6.1 to use
> until SAM-6 is released since there will not be an in-place
> migration of SAM-1.4 to SAM-6. (Note that I am an engineer so do not
> have insights into how likely it is you could convince biz dev for a
> license. :)
>
> Please let us know how you end up proceeding.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to foreman-users+unsubscribe@googlegroups.com
> .
> To post to this group, send email to foreman-users@googlegroups.com
> .
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to foreman-users+unsubscribe@googlegroups.com
> .
> To post to this group, send email to foreman-users@googlegroups.com
> .
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
----- Original Message -----
> Hi,
>
> I'm looking to possibly use SAM for managing my RHEL subscriptions
> locally. We are Foreman users, but are not interested in using a
full
> blown Katello installation at this time due to the fact that we
can not
> make it work with our existing Foreman deployment.
>
> I'm looking at the SAM documentation [1] and noticed that it's
actually
> installing a version of Katello? What is the relationship
between Katello
> and the standalone SAM product offering? Is SAM going away (am I
wasting
> my time)?
>
> Thanks,
>
> Josh
>
> [1]
>
SAM-1.4, which was released a year or so ago, is supported on RHEL6.
It is based on the katello upstream project but before the merge
with foreman.
When SAM-6 is released, it will still be based on katello but this
time after the merge with foreman. The features of SAM are strictly
limited to subscription management and basic content consumption.
(There are no content views, no remote package installation, etc.)
The release date of SAM-6 has not been published yet.
In terms of where to invest time, SAM-1.4 is a supported product.
That said, if it were me I would try to get a copy of Sat-6.1 to use
until SAM-6 is released since there will not be an in-place
migration of SAM-1.4 to SAM-6. (Note that I am an engineer so do not
have insights into how likely it is you could convince biz dev for a
license. :)
Please let us know how you end up proceeding.
--
You received this message because you are subscribed to the Google
Groups "Foreman users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-users+unsubscribe@googlegroups.com
<mailto:foreman-users%2Bunsubscribe@googlegroups.com>.
To post to this group, send email to foreman-users@googlegroups.com
<mailto:foreman-users@googlegroups.com>.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
