LCE or CV/CCV package differentials

Hola,

Is there an easy way to get a comprehensive list of package changes between
two CV versions or two Lifecycle Environment versions?

I'm looking into the hammer help now, and have found

which suggests that a per CV package list is available. I could wrap up a
couple of those in a bash script I guess?

I presumed this would be a solved problem - being able to report on what
packages will change should the LCE be promoted to the new CV version.
That's the actual problem I'm trying to solve - am I doing it wrong again?

Cheers
L.

··· ------ "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics is the insistence that we cannot ignore the truth, nor should we panic about it. It is a shared consciousness that our institutions have failed and our ecosystem is collapsing, yet we are still here — and we are creative agents who can shape our destinies. Apocalyptic civics is the conviction that the only way out is through, and the only way through is together. "

Greg Bloom @greggish

After some banging away, I found this:

hammer package list --organization-id 1 --content-view-id 25
–content-view-version 25 --repository-id 2

returned a list, but only after I'd tried

hammer package list --organization-id 1 --content-view-id 25

then

hammer package list --organization-id 1 --content-view-id 25
–content-view-version 25

It would be great to be able to iterate over the included repo versions
without necessarily needing to know what they were - so that

hammer package list --organization-id 1 --content-view-id 25
–content-view-version 25

returned a list of packages of all the repos in it? Am I missing something
simple?

L.

··· On 1 August 2017 at 14:14, Lachlan Musicman wrote:

Hola,

Is there an easy way to get a comprehensive list of package changes
between two CV versions or two Lifecycle Environment versions?

I’m looking into the hammer help now, and have found
Bug #20046: hammer package list no longer supports --content-view or --content-view-id - Katello - Foreman
which suggests that a per CV package list is available. I could wrap up a
couple of those in a bash script I guess?

I presumed this would be a solved problem - being able to report on what
packages will change should the LCE be promoted to the new CV version.
That’s the actual problem I’m trying to solve - am I doing it wrong again?


"The antidote to apocalypticism is apocalyptic civics. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

Greg Bloom @greggish

There is no easy way to do this. We have the same issue and I'd think its a
pretty basic use case!

From memory, there is a compare API endpoint but that will only report on
errata differences between two content view versions.

We do this by grabbing all packages / puppet modules (as that's the two
bits we're interested in) in the two content view versions and diff'ing.
Its slow. Really slow - like 15 minutes or so slow.

··· On Tuesday, August 1, 2017 at 12:59:02 AM UTC-4, Lachlan Musicman wrote: > > On 1 August 2017 at 14:14, Lachlan Musicman > wrote: > >> Hola, >> >> Is there an easy way to get a comprehensive list of package changes >> between two CV versions or two Lifecycle Environment versions? >> >> I'm looking into the hammer help now, and have found >> http://projects.theforeman.org/issues/20046 >> >> which suggests that a per CV package list is available. I could wrap up a >> couple of those in a bash script I guess? >> >> I presumed this would be a solved problem - being able to report on what >> packages will change should the LCE be promoted to the new CV version. >> That's the actual problem I'm trying to solve - am I doing it wrong again? >> > > > After some banging away, I found this: > > hammer package list --organization-id 1 --content-view-id 25 > --content-view-version 25 --repository-id 2 > > returned a list, but only after I'd tried > > hammer package list --organization-id 1 --content-view-id 25 > > then > > hammer package list --organization-id 1 --content-view-id 25 > --content-view-version 25 > > It would be great to be able to iterate over the included repo versions > without necessarily needing to know what they were - so that > > hammer package list --organization-id 1 --content-view-id 25 > --content-view-version 25 > > returned a list of packages of all the repos in it? Am I missing something > simple? > > L. > > > ------ > "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic > civics is the insistence that we cannot ignore the truth, nor should we > panic about it. It is a shared consciousness that our institutions have > failed and our ecosystem is collapsing, yet we are still here — and we are > creative agents who can shape our destinies. Apocalyptic civics is the > conviction that the only way out is through, and the only way through is > together. " > > *Greg Bloom* @greggish > https://twitter.com/greggish/status/873177525903609857 > >

Yeah - even just that command I found took a long time to process, and that
CV has 4 Products in it, so it might be quite long.

I woke up at 3am wondering if I should teach myself ruby and build a module
that interrogates the database directly, but then I remembered my todo list.

On the "I wish" pile.

Thanks for the feedback.

cheers
L.

··· ------ "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics is the insistence that we cannot ignore the truth, nor should we panic about it. It is a shared consciousness that our institutions have failed and our ecosystem is collapsing, yet we are still here — and we are creative agents who can shape our destinies. Apocalyptic civics is the conviction that the only way out is through, and the only way through is together. "

Greg Bloom @greggish

On 2 August 2017 at 12:49, Andrew Schofield aas@ourhavens.co.uk wrote:

There is no easy way to do this. We have the same issue and I’d think its
a pretty basic use case!

From memory, there is a compare API endpoint but that will only report on
errata differences between two content view versions.

We do this by grabbing all packages / puppet modules (as that’s the two
bits we’re interested in) in the two content view versions and diff’ing.
Its slow. Really slow - like 15 minutes or so slow.

On Tuesday, August 1, 2017 at 12:59:02 AM UTC-4, Lachlan Musicman wrote:

On 1 August 2017 at 14:14, Lachlan Musicman dat...@gmail.com wrote:

Hola,

Is there an easy way to get a comprehensive list of package changes
between two CV versions or two Lifecycle Environment versions?

I’m looking into the hammer help now, and have found
Bug #20046: hammer package list no longer supports --content-view or --content-view-id - Katello - Foreman
http://www.google.com/url?q=http%3A%2F%2Fprojects.theforeman.org%2Fissues%2F20046&sa=D&sntz=1&usg=AFQjCNH_wK1hwk8FkYio5FsGU7oQLi2VxQ
which suggests that a per CV package list is available. I could wrap up
a couple of those in a bash script I guess?

I presumed this would be a solved problem - being able to report on what
packages will change should the LCE be promoted to the new CV version.
That’s the actual problem I’m trying to solve - am I doing it wrong again?

After some banging away, I found this:

hammer package list --organization-id 1 --content-view-id 25
–content-view-version 25 --repository-id 2

returned a list, but only after I’d tried

hammer package list --organization-id 1 --content-view-id 25

then

hammer package list --organization-id 1 --content-view-id 25
–content-view-version 25

It would be great to be able to iterate over the included repo versions
without necessarily needing to know what they were - so that

hammer package list --organization-id 1 --content-view-id 25
–content-view-version 25

returned a list of packages of all the repos in it? Am I missing
something simple?

L.


"The antidote to apocalypticism is apocalyptic civics. Apocalyptic
civics is the insistence that we cannot ignore the truth, nor should we
panic about it. It is a shared consciousness that our institutions have
failed and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

Greg Bloom @greggish https://twitter.com/greggish/s
tatus/873177525903609857


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.

Maybe also add it to our "I wish" pile too? :slight_smile:

http://projects.theforeman.org/projects/katello/issues/new

Greg

··· On Wed, 2017-08-02 at 13:02 +1000, Lachlan Musicman wrote: > On the "I wish" pile.
··· On 3 August 2017 at 22:42, Greg Sutcliffe wrote:

On Wed, 2017-08-02 at 13:02 +1000, Lachlan Musicman wrote:

On the “I wish” pile.

Maybe also add it to our “I wish” pile too? :slight_smile:

Foreman


"The antidote to apocalypticism is apocalyptic civics. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

Greg Bloom @greggish

There are existing issues around this large feature and an RFC if you'd
like to contribute via review:

https://github.com/theforeman/rfcs/pull/17

I've written a script using both hammer and apipie to do comparisons I
could share.

··· On Aug 3, 2017 7:35 PM, "Lachlan Musicman" wrote:

On 3 August 2017 at 22:42, Greg Sutcliffe greg.sutcliffe@gmail.com > wrote:

On Wed, 2017-08-02 at 13:02 +1000, Lachlan Musicman wrote:

On the “I wish” pile.

Maybe also add it to our “I wish” pile too? :slight_smile:

http://projects.theforeman.org/projects/katello/issues/new

http://projects.theforeman.org/issues/20501


"The antidote to apocalypticism is apocalyptic civics. Apocalyptic
civics is the insistence that we cannot ignore the truth, nor should we
panic about it. It is a shared consciousness that our institutions have
failed and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

Greg Bloom @greggish https://twitter.com/greggish/
status/873177525903609857


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.

I'd be interested in this?

I have a basic script which calls the api and drags down all packages from
version a and version b and does a comparison. Its simplistic at best.

··· On 3 August 2017 at 20:49, Eric D Helms wrote:

There are existing issues around this large feature and an RFC if you’d
like to contribute via review:

https://github.com/theforeman/rfcs/pull/17

I’ve written a script using both hammer and apipie to do comparisons I
could share.

Thanks Eric,

I'll take a look at the RFC/etc - but if you have some scripts I could look
at that would be appreciated too.

cheers
L.

··· ------ "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics is the insistence that we cannot ignore the truth, nor should we panic about it. It is a shared consciousness that our institutions have failed and our ecosystem is collapsing, yet we are still here — and we are creative agents who can shape our destinies. Apocalyptic civics is the conviction that the only way out is through, and the only way through is together. "

Greg Bloom @greggish

On 4 August 2017 at 10:49, Eric D Helms eric.d.helms@gmail.com wrote:

There are existing issues around this large feature and an RFC if you’d
like to contribute via review:

Content View Version Compare by johnpmitsch · Pull Request #17 · theforeman/rfcs · GitHub

I’ve written a script using both hammer and apipie to do comparisons I
could share.

On Aug 3, 2017 7:35 PM, “Lachlan Musicman” datakid@gmail.com wrote:

On 3 August 2017 at 22:42, Greg Sutcliffe greg.sutcliffe@gmail.com >> wrote:

On Wed, 2017-08-02 at 13:02 +1000, Lachlan Musicman wrote:

On the “I wish” pile.

Maybe also add it to our “I wish” pile too? :slight_smile:

Foreman

Feature #20501: Content View version differentials - a list of software that will be updated - Katello - Foreman


"The antidote to apocalypticism is apocalyptic civics. Apocalyptic
civics is the insistence that we cannot ignore the truth, nor should we
panic about it. It is a shared consciousness that our institutions have
failed and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

Greg Bloom @greggish https://twitter.com/greggish/s
tatus/873177525903609857


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.


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.