This week has seen me building bespoke LiveCD images for a client to allow
specific firmware bundles to be installed on hardware. To do this I was
using the older method:
livecd-creator --config=centos.ks -f LiveCD
to create my LiveCD.iso. The Foreman/Katello/Pulp side of my questions
comes from the kickstart file I was using. I tried to use the Pulp repos
that I had created in my Katello system. They're perfectly viewable in a
browser and look just like what a repo is supposed to look like. But when
I ran the livecd-creator command, I got complaints that the core group
couldn't be found. When I change the kickstart to point at internet CentOS
repos, or even the copy of the CentOS DVD which I also serve via http,
things worked fine.
I didn't have time to figure out why the Katello repos were failing. But
is there any obvious reason that I couldn't be using my Katello repos in
this way?
The kickstart file was using the URL shown in "Published At" in hammer repository info --id=1. It's an on-demand repo, but I've installed many
systems with much larger %packages sections than this LiveCD.
I think that Pulp does not support creating packagegroups, you will
only find these on original DVDs or kickstart repositories on CDN.
Better to ask at pulp-users tho.
LZ
···
On Wed, Apr 26, 2017 at 10:29 AM, Duncan Innes wrote:
> Hi,
>
> This week has seen me building bespoke LiveCD images for a client to allow
> specific firmware bundles to be installed on hardware. To do this I was
> using the older method:
>
> livecd-creator --config=centos.ks -f LiveCD
>
> to create my LiveCD.iso. The Foreman/Katello/Pulp side of my questions
> comes from the kickstart file I was using. I tried to use the Pulp repos
> that I had created in my Katello system. They're perfectly viewable in a
> browser and look just like what a repo is supposed to look like. But when I
> ran the livecd-creator command, I got complaints that the core group
> couldn't be found. When I change the kickstart to point at internet CentOS
> repos, or even the copy of the CentOS DVD which I also serve via http,
> things worked fine.
>
> I didn't have time to figure out why the Katello repos were failing. But is
> there any obvious reason that I couldn't be using my Katello repos in this
> way?
>
> The kickstart file was using the URL shown in "Published At" in `hammer
> repository info --id=1`. It's an on-demand repo, but I've installed many
> systems with much larger %packages sections than this LiveCD.
>
> It's a Foreman 1.14.3 & Katello 3.3.1 system.
>
> Cheers
>
> Duncan
>
> --
> 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.
In Katello 3.4 (to be released) there's an API:
POST API at /katello/api/package_groups for creation and a DELETE API at
/katello/api/package_groups for deletion.
In Katello3.3 you can:
Step 1:
pulp-admin rpm repo uploads group
–user-visible=true
–repo-id=rhel-ebi-package-groups
–group-id=package-group-gpfs-client-4.1.0-8
–name="Package Group for GPFS 4.1.0-8 clients"
–description="Package Group for GPFS 4.1.0-8 clients"
–mand-name=gpfs.docs
–mand-name=gpfs.gpl
–mand-name=gpfs.msg.en_US
–mand-name=gpfs.base
–mand-name=gpfs.gskit
–mand-name=gpfs.ext
···
On Wed, May 3, 2017 at 12:45 PM, Lukas Zapletal wrote:
I think that Pulp does not support creating packagegroups, you will
only find these on original DVDs or kickstart repositories on CDN.
Better to ask at pulp-users tho.
LZ
On Wed, Apr 26, 2017 at 10:29 AM, Duncan Innes duncan@innes.net wrote:
Hi,
This week has seen me building bespoke LiveCD images for a client to
allow
specific firmware bundles to be installed on hardware. To do this I was
using the older method:
livecd-creator --config=centos.ks -f LiveCD
to create my LiveCD.iso. The Foreman/Katello/Pulp side of my questions
comes from the kickstart file I was using. I tried to use the Pulp repos
that I had created in my Katello system. They’re perfectly viewable in a
browser and look just like what a repo is supposed to look like. But
when I
ran the livecd-creator command, I got complaints that the core group
couldn’t be found. When I change the kickstart to point at internet
CentOS
repos, or even the copy of the CentOS DVD which I also serve via http,
things worked fine.
I didn’t have time to figure out why the Katello repos were failing.
But is
there any obvious reason that I couldn’t be using my Katello repos in
this
way?
The kickstart file was using the URL shown in “Published At” in hammer repository info --id=1. It’s an on-demand repo, but I’ve installed many
systems with much larger %packages sections than this LiveCD.
So will the package groups be created automatically for each repo in 3.4?
Or is it just that the API is available for use?
I'll be rebuilding from scratch on 3.4 soon, so am not worried about the
state of my 3.3 system.
···
On Monday, 8 May 2017 09:06:14 UTC+1, Sean O'Keeffe wrote:
>
> Pulp does support package groups creation..
>
> In Katello 3.4 (to be released) there's an API:
> POST API at /katello/api/package_groups for creation and a DELETE API at
> /katello/api/package_groups for deletion.
>
> In Katello3.3 you can:
> Step 1:
> pulp-admin rpm repo uploads group \
> --user-visible=true \
> --repo-id=rhel-ebi-package-groups \
> --group-id=package-group-gpfs-client-4.1.0-8 \
> --name="Package Group for GPFS 4.1.0-8 clients" \
> --description="Package Group for GPFS 4.1.0-8 clients" \
> --mand-name=gpfs.docs \
> --mand-name=gpfs.gpl \
> --mand-name=gpfs.msg.en_US \
> --mand-name=gpfs.base \
> --mand-name=gpfs.gskit \
> --mand-name=gpfs.ext
>
> Step 2:
> foreman-rake console
> > Katello::PackageGroup.import_all
>
> Step 3:
> Force regenerate repo metadata
>
>
> On Wed, May 3, 2017 at 12:45 PM, Lukas Zapletal > wrote:
>
>> I think that Pulp does not support creating packagegroups, you will
>> only find these on original DVDs or kickstart repositories on CDN.
>> Better to ask at pulp-users tho.
>>
>> LZ
>>
>> On Wed, Apr 26, 2017 at 10:29 AM, Duncan Innes > > wrote:
>> > Hi,
>> >
>> > This week has seen me building bespoke LiveCD images for a client to
>> allow
>> > specific firmware bundles to be installed on hardware. To do this I was
>> > using the older method:
>> >
>> > livecd-creator --config=centos.ks -f LiveCD
>> >
>> > to create my LiveCD.iso. The Foreman/Katello/Pulp side of my questions
>> > comes from the kickstart file I was using. I tried to use the Pulp
>> repos
>> > that I had created in my Katello system. They're perfectly viewable in
>> a
>> > browser and look just like what a repo is supposed to look like. But
>> when I
>> > ran the livecd-creator command, I got complaints that the core group
>> > couldn't be found. When I change the kickstart to point at internet
>> CentOS
>> > repos, or even the copy of the CentOS DVD which I also serve via http,
>> > things worked fine.
>> >
>> > I didn't have time to figure out why the Katello repos were failing.
>> But is
>> > there any obvious reason that I couldn't be using my Katello repos in
>> this
>> > way?
>> >
>> > The kickstart file was using the URL shown in "Published At" in `hammer
>> > repository info --id=1`. It's an on-demand repo, but I've installed
>> many
>> > systems with much larger %packages sections than this LiveCD.
>> >
>> > It's a Foreman 1.14.3 & Katello 3.3.1 system.
>> >
>> > Cheers
>> >
>> > Duncan
>> >
>> > --
>> > 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 https://groups.google.com/group/foreman-users.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> Later,
>> Lukas @lzap Zapletal
>>
>> --
>> 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 https://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
That's just an API for adding additional groups. For a long time any yum
repo Pulp syncs it should also copy the package groups defined, I guess
your problem might be the source you are syncing from doesn't have any
package group defined in the metadata?
···
On Mon, May 8, 2017 at 10:34 AM, Duncan Innes wrote:
So will the package groups be created automatically for each repo in 3.4?
Or is it just that the API is available for use?
I’ll be rebuilding from scratch on 3.4 soon, so am not worried about the
state of my 3.3 system.
On Monday, 8 May 2017 09:06:14 UTC+1, Sean O’Keeffe wrote:
Pulp does support package groups creation…
In Katello 3.4 (to be released) there’s an API:
POST API at /katello/api/package_groups for creation and a DELETE API at
/katello/api/package_groups for deletion.
In Katello3.3 you can:
Step 1:
pulp-admin rpm repo uploads group
–user-visible=true
–repo-id=rhel-ebi-package-groups
–group-id=package-group-gpfs-client-4.1.0-8
–name=“Package Group for GPFS 4.1.0-8 clients”
–description=“Package Group for GPFS 4.1.0-8 clients”
–mand-name=gpfs.docs
–mand-name=gpfs.gpl
–mand-name=gpfs.msg.en_US
–mand-name=gpfs.base
–mand-name=gpfs.gskit
–mand-name=gpfs.ext
Step 2:
foreman-rake console
Katello::PackageGroup.import_all
Step 3:
Force regenerate repo metadata
On Wed, May 3, 2017 at 12:45 PM, Lukas Zapletal lz...@redhat.com wrote:
I think that Pulp does not support creating packagegroups, you will
only find these on original DVDs or kickstart repositories on CDN.
Better to ask at pulp-users tho.
LZ
On Wed, Apr 26, 2017 at 10:29 AM, Duncan Innes dun...@innes.net wrote:
Hi,
This week has seen me building bespoke LiveCD images for a client to
allow
specific firmware bundles to be installed on hardware. To do this I
was
using the older method:
livecd-creator --config=centos.ks -f LiveCD
to create my LiveCD.iso. The Foreman/Katello/Pulp side of my questions
comes from the kickstart file I was using. I tried to use the Pulp
repos
that I had created in my Katello system. They’re perfectly viewable
in a
browser and look just like what a repo is supposed to look like. But
when I
ran the livecd-creator command, I got complaints that the core group
couldn’t be found. When I change the kickstart to point at internet
CentOS
repos, or even the copy of the CentOS DVD which I also serve via http,
things worked fine.
I didn’t have time to figure out why the Katello repos were failing.
But is
there any obvious reason that I couldn’t be using my Katello repos in
this
way?
The kickstart file was using the URL shown in “Published At” in hammer repository info --id=1. It’s an on-demand repo, but I’ve installed
many
systems with much larger %packages sections than this LiveCD.
···
On Monday, 8 May 2017 11:22:55 UTC+1, Sean O'Keeffe wrote:
>
> That's just an API for adding additional groups. For a long time any yum
> repo Pulp syncs it should also copy the package groups defined, I guess
> your problem might be the source you are syncing from doesn't have any
> package group defined in the metadata?
>
> On Mon, May 8, 2017 at 10:34 AM, Duncan Innes > wrote:
>
>> So will the package groups be created automatically for each repo in
>> 3.4? Or is it just that the API is available for use?
>>
>> I'll be rebuilding from scratch on 3.4 soon, so am not worried about the
>> state of my 3.3 system.
>>
>> On Monday, 8 May 2017 09:06:14 UTC+1, Sean O'Keeffe wrote:
>>>
>>> Pulp does support package groups creation..
>>>
>>> In Katello 3.4 (to be released) there's an API:
>>> POST API at /katello/api/package_groups for creation and a DELETE API
>>> at /katello/api/package_groups for deletion.
>>>
>>> In Katello3.3 you can:
>>> Step 1:
>>> pulp-admin rpm repo uploads group \
>>> --user-visible=true \
>>> --repo-id=rhel-ebi-package-groups \
>>> --group-id=package-group-gpfs-client-4.1.0-8 \
>>> --name="Package Group for GPFS 4.1.0-8 clients" \
>>> --description="Package Group for GPFS 4.1.0-8 clients" \
>>> --mand-name=gpfs.docs \
>>> --mand-name=gpfs.gpl \
>>> --mand-name=gpfs.msg.en_US \
>>> --mand-name=gpfs.base \
>>> --mand-name=gpfs.gskit \
>>> --mand-name=gpfs.ext
>>>
>>> Step 2:
>>> foreman-rake console
>>> > Katello::PackageGroup.import_all
>>>
>>> Step 3:
>>> Force regenerate repo metadata
>>>
>>>
>>> On Wed, May 3, 2017 at 12:45 PM, Lukas Zapletal >>> wrote:
>>>
>>>> I think that Pulp does not support creating packagegroups, you will
>>>> only find these on original DVDs or kickstart repositories on CDN.
>>>> Better to ask at pulp-users tho.
>>>>
>>>> LZ
>>>>
>>>> On Wed, Apr 26, 2017 at 10:29 AM, Duncan Innes >>>> wrote:
>>>> > Hi,
>>>> >
>>>> > This week has seen me building bespoke LiveCD images for a client to
>>>> allow
>>>> > specific firmware bundles to be installed on hardware. To do this I
>>>> was
>>>> > using the older method:
>>>> >
>>>> > livecd-creator --config=centos.ks -f LiveCD
>>>> >
>>>> > to create my LiveCD.iso. The Foreman/Katello/Pulp side of my
>>>> questions
>>>> > comes from the kickstart file I was using. I tried to use the Pulp
>>>> repos
>>>> > that I had created in my Katello system. They're perfectly viewable
>>>> in a
>>>> > browser and look just like what a repo is supposed to look like. But
>>>> when I
>>>> > ran the livecd-creator command, I got complaints that the core group
>>>> > couldn't be found. When I change the kickstart to point at internet
>>>> CentOS
>>>> > repos, or even the copy of the CentOS DVD which I also serve via http,
>>>> > things worked fine.
>>>> >
>>>> > I didn't have time to figure out why the Katello repos were failing.
>>>> But is
>>>> > there any obvious reason that I couldn't be using my Katello repos in
>>>> this
>>>> > way?
>>>> >
>>>> > The kickstart file was using the URL shown in "Published At" in
>>>> `hammer
>>>> > repository info --id=1`. It's an on-demand repo, but I've installed
>>>> many
>>>> > systems with much larger %packages sections than this LiveCD.
>>>> >
>>>> > It's a Foreman 1.14.3 & Katello 3.3.1 system.
>>>> >
>>>> > Cheers
>>>> >
>>>> > Duncan
>>>> >
>>>> > --
>>>> > 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 https://groups.google.com/group/foreman-users.
>>>> > For more options, visit https://groups.google.com/d/optout.
>>>>
>>>>
>>>>
>>>> --
>>>> Later,
>>>> Lukas @lzap Zapletal
>>>>
>>>> --
>>>> 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 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-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> Visit this group at https://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
