After a fair amount of experimenting, I don't seem able to get Katello to
do what I hoped it might do. I suspect this is just me, but I would be
grateful if someone could confirm.
More broadly, I want to be able to compare the new content to what is
already installed across my server estate (i.e. show the delta) and then
apply the updates en masse (or perhaps in batches / with caveats / for
certain packages). I can only see the 'update all' button. The promotion
of views between environments is a clever concept, but I'm missing the more
basic functionality at present (because of my understanding I suspect).
If I understand what you are looking for, this is generally handled via
errata. However, we do realize that not everything comes with errata and
have an outstanding issue to be able to see what packages have updates
available from the content hosts current content ( Feature #8571: As an UI user i like to see upgradable packages for a system in Content Host => Packages - Katello - Foreman). A cruder method would be to
use the API to query the content view version for the packages associated
to it, query the content host for the list of packages and then compare the
two. You could then issue installs for specific packages based on the
outcome. If the issue I mentioned doesn't meet your use case or meet all of
its needs, please do file an issue describing what you'd like to see in as
much detail and we will see what we can do.
Eric
···
On Thu, Apr 2, 2015 at 11:19 AM, JC wrote:
Hi all,
After a fair amount of experimenting, I don’t seem able to get Katello to
do what I hoped it might do. I suspect this is just me, but I would be
grateful if someone could confirm.
More broadly, I want to be able to compare the new content to what is
already installed across my server estate (i.e. show the delta) and then
apply the updates en masse (or perhaps in batches / with caveats / for
certain packages). I can only see the ‘update all’ button. The promotion
of views between environments is a clever concept, but I’m missing the more
basic functionality at present (because of my understanding I suspect).
Thanks for the quick response Eric. Yes, you have captured (understood)
what I'm after, and like Stefan Meyer, I'm thinking particularly of
CentOS. I am evaluating Katello for a customer, who has c. 600,
predominantly CentOS, servers and they need to be able to see (with pretty
reports ideally) how far from 'current' their estate is and then update it
(ideally in [automated] phases). It sounds like I need to track feature
8571, but stop what I'm doing for now.
···
On 2 April 2015 at 16:29, Eric D Helms wrote:
If I understand what you are looking for, this is generally handled via
errata. However, we do realize that not everything comes with errata and
have an outstanding issue to be able to see what packages have updates
available from the content hosts current content ( Feature #8571: As an UI user i like to see upgradable packages for a system in Content Host => Packages - Katello - Foreman). A cruder method would be to
use the API to query the content view version for the packages associated
to it, query the content host for the list of packages and then compare the
two. You could then issue installs for specific packages based on the
outcome. If the issue I mentioned doesn’t meet your use case or meet all of
its needs, please do file an issue describing what you’d like to see in as
much detail and we will see what we can do.
After a fair amount of experimenting, I don’t seem able to get Katello to
do what I hoped it might do. I suspect this is just me, but I would be
grateful if someone could confirm.
More broadly, I want to be able to compare the new content to what is
already installed across my server estate (i.e. show the delta) and then
apply the updates en masse (or perhaps in batches / with caveats / for
certain packages). I can only see the ‘update all’ button. The promotion
of views between environments is a clever concept, but I’m missing the more
basic functionality at present (because of my understanding I suspect).
There is also an open issue around supporting external errata ( Feature #8656: Ability to import errata data from an external source. - Katello - Foreman) for things like CentOS errata.
We have a lot on our plate that we are working on currently and afaik both
the issues I have mentioned do not have any active work on them. If you
don't mind up-voting and even adding your use-cases/scenarios where
appropriate, it would go a long way to helping us prioritize and implement
them. Thanks for the feedback!
Eric
···
On Thu, Apr 2, 2015 at 11:42 AM, Jamie Caldwell wrote:
Thanks for the quick response Eric. Yes, you have captured (understood)
what I’m after, and like Stefan Meyer, I’m thinking particularly of
CentOS. I am evaluating Katello for a customer, who has c. 600,
predominantly CentOS, servers and they need to be able to see (with pretty
reports ideally) how far from ‘current’ their estate is and then update it
(ideally in [automated] phases). It sounds like I need to track feature
8571, but stop what I’m doing for now.
If I understand what you are looking for, this is generally handled via
errata. However, we do realize that not everything comes with errata and
have an outstanding issue to be able to see what packages have updates
available from the content hosts current content ( Feature #8571: As an UI user i like to see upgradable packages for a system in Content Host => Packages - Katello - Foreman). A cruder method would be to
use the API to query the content view version for the packages associated
to it, query the content host for the list of packages and then compare the
two. You could then issue installs for specific packages based on the
outcome. If the issue I mentioned doesn’t meet your use case or meet all of
its needs, please do file an issue describing what you’d like to see in as
much detail and we will see what we can do.
After a fair amount of experimenting, I don’t seem able to get Katello
to do what I hoped it might do. I suspect this is just me, but I would be
grateful if someone could confirm.
More broadly, I want to be able to compare the new content to what is
already installed across my server estate (i.e. show the delta) and then
apply the updates en masse (or perhaps in batches / with caveats / for
certain packages). I can only see the ‘update all’ button. The promotion
of views between environments is a clever concept, but I’m missing the more
basic functionality at present (because of my understanding I suspect).
Thanks Eric. Yes, I think the two issues are interwoven. I do, very much,
appreciate everyone's hard work. I've voted up and updated both tickets.
···
On 2 April 2015 at 16:52, Eric D Helms wrote:
There is also an open issue around supporting external errata ( Feature #8656: Ability to import errata data from an external source. - Katello - Foreman) for things like CentOS
errata. We have a lot on our plate that we are working on currently and
afaik both the issues I have mentioned do not have any active work on them.
If you don’t mind up-voting and even adding your use-cases/scenarios where
appropriate, it would go a long way to helping us prioritize and implement
them. Thanks for the feedback!
Thanks for the quick response Eric. Yes, you have captured (understood)
what I’m after, and like Stefan Meyer, I’m thinking particularly of
CentOS. I am evaluating Katello for a customer, who has c. 600,
predominantly CentOS, servers and they need to be able to see (with pretty
reports ideally) how far from ‘current’ their estate is and then update it
(ideally in [automated] phases). It sounds like I need to track feature
8571, but stop what I’m doing for now.
If I understand what you are looking for, this is generally handled via
errata. However, we do realize that not everything comes with errata and
have an outstanding issue to be able to see what packages have updates
available from the content hosts current content ( Feature #8571: As an UI user i like to see upgradable packages for a system in Content Host => Packages - Katello - Foreman). A cruder method would be
to use the API to query the content view version for the packages
associated to it, query the content host for the list of packages and then
compare the two. You could then issue installs for specific packages based
on the outcome. If the issue I mentioned doesn’t meet your use case or meet
all of its needs, please do file an issue describing what you’d like to see
in as much detail and we will see what we can do.
After a fair amount of experimenting, I don’t seem able to get Katello
to do what I hoped it might do. I suspect this is just me, but I would be
grateful if someone could confirm.
More broadly, I want to be able to compare the new content to what is
already installed across my server estate (i.e. show the delta) and then
apply the updates en masse (or perhaps in batches / with caveats / for
certain packages). I can only see the ‘update all’ button. The promotion
of views between environments is a clever concept, but I’m missing the more
basic functionality at present (because of my understanding I suspect).
I think it doesn't help to create just an import tool for CentOS. We are
mirroring some external repositories and most of them are without erratas.
We would need to create errata manually for every updated package in our
repos.
Some of our own rpm packages are created by other groups within the company
and at the moment they can upload them to a Satellite channel.
···
On Thursday, April 2, 2015 at 5:52:38 PM UTC+2, Eric Helms wrote:
>
> There is also an open issue around supporting external errata (
> http://projects.theforeman.org/issues/8656) for things like CentOS
> errata. We have a lot on our plate that we are working on currently and
> afaik both the issues I have mentioned do not have any active work on them.
> If you don't mind up-voting and even adding your use-cases/scenarios where
> appropriate, it would go a long way to helping us prioritize and implement
> them. Thanks for the feedback!
>
> Eric
>
> On Thu, Apr 2, 2015 at 11:42 AM, Jamie Caldwell > wrote:
>
>> Thanks for the quick response Eric. Yes, you have captured (understood)
>> what I'm after, and like Stefan Meyer, I'm thinking particularly of
>> CentOS. I am evaluating Katello for a customer, who has c. 600,
>> predominantly CentOS, servers and they need to be able to see (with pretty
>> reports ideally) how far from 'current' their estate is and then update it
>> (ideally in [automated] phases). It sounds like I need to track feature
>> 8571, but stop what I'm doing for now.
>>
>> On 2 April 2015 at 16:29, Eric D Helms <ericd...@gmail.com > >> wrote:
>>
>>> If I understand what you are looking for, this is generally handled via
>>> errata. However, we do realize that not everything comes with errata and
>>> have an outstanding issue to be able to see what packages have updates
>>> available from the content hosts current content (
>>> http://projects.theforeman.org/issues/8571). A cruder method would be
>>> to use the API to query the content view version for the packages
>>> associated to it, query the content host for the list of packages and then
>>> compare the two. You could then issue installs for specific packages based
>>> on the outcome. If the issue I mentioned doesn't meet your use case or meet
>>> all of its needs, please do file an issue describing what you'd like to see
>>> in as much detail and we will see what we can do.
>>>
>>> Eric
>>>
>>> On Thu, Apr 2, 2015 at 11:19 AM, JC <mr.jamie...@gmail.com >>> > wrote:
>>>
>>>> Hi all,
>>>>
>>>> After a fair amount of experimenting, I don't seem able to get Katello
>>>> to do what I hoped it might do. I suspect this is just me, but I would be
>>>> grateful if someone could confirm.
>>>>
>>>> I have followed the 'General Workflow
>>>> ',
>>>> and have a published content view and attached content hosts. But what I
>>>> don't get is how to 'apply' that view (taken of the CentOS 6 updates repo)
>>>> to the host(s)?
>>>>
>>>> More broadly, I want to be able to compare the new content to what is
>>>> already installed across my server estate (i.e. show the delta) and then
>>>> apply the updates en masse (or perhaps in batches / with caveats / for
>>>> certain packages). I can only see the 'update all' button. The promotion
>>>> of views between environments is a clever concept, but I'm missing the more
>>>> basic functionality at present (because of my understanding I suspect).
>>>>
>>>> Help much appreciated. Thanks.
>>>>
>>>> --
>>>> 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-user...@googlegroups.com .
>>>> To post to this group, send email to forema...@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 a topic in the
>>> Google Groups "Foreman users" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/foreman-users/tVtmQihqPuQ/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> foreman-user...@googlegroups.com .
>>> To post to this group, send email to forema...@googlegroups.com
>>> .
>>> Visit this group at http://groups.google.com/group/foreman-users.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Jamie.
>>
>> --
>> 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-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
