Thread: Installing a kit on an existing installer node

Hi,

=20

I'm a Kusu newbie, so please forgive any silly questions.

=20

I want to install a custom kit that I built on an existing installer
node. I used kitops to add the kit, and I used repoman to add (and
rebuild) the kit to my repository. That seems to have worked. I can
see the kit listed in my repository using 'repoman -l'. However, it
doesn't seem like the kit actually installed on my installer node. I am
assuming there is another step required to initiate an update on my
installer node, but I'm not sure what that is. Any pointers or help
would be greatly appreciated!

=20

There's a strong chance my kit isn't built correctly, but I wanted to
make sure I was doing the correct steps to install it first.

=20

Thanks,

Brock Taylor

Hi Taylor,

On Wed, 19 Dec 2007 13:41:42 -0800
"Taylor, Brock A" <brock.a.taylor@intel.com> wrote:

> Hi,
>
>
>
> I'm a Kusu newbie, so please forgive any silly questions.

Welcome!

> I want to install a custom kit that I built on an existing installer
> node. I used kitops to add the kit, and I used repoman to add (and
> rebuild) the kit to my repository. That seems to have worked. I can
> see the kit listed in my repository using 'repoman -l'. However, it
> doesn't seem like the kit actually installed on my installer node. I
> am assuming there is another step required to initiate an update on my
> installer node, but I'm not sure what that is. Any pointers or help
> would be greatly appreciated!

Yes, you are still missing a couple steps.

First, you need to run ngedit and associate the kit's components you
want with the appropriate nodegroup.

ngedit will inform you that the nodes in this nodegroup need to be
synced; it will offer to do this for you immediately, or give you a
command to run later. In any case, running `cfmsync -p` after ngedit
will perform the installation.

Note that you might need to wait a little while until all the packages
are installed.

> There's a strong chance my kit isn't built correctly, but I wanted to
> make sure I was doing the correct steps to install it first.
>
>
>
> Thanks,
>
> Brock Taylor

Good luck!
Mike

>Date: Thu, 20 Dec 2007 08:48:49 +0900
>From: Mike Mazur <mmazur@osgdc.org>
>Subject: Re: [Kusu-users] Installing a kit on an existing installer
> node
>To: kusu-users@osgdc.org
>Message-ID: <20071220084849.5e63e694@kitt>
>Content-Type: text/plain; charset=3DUS-ASCII
>
>Hi Taylor,
>
>On Wed, 19 Dec 2007 13:41:42 -0800
>"Taylor, Brock A" <brock.a.taylor@intel.com> wrote:
>
>> Hi,
>>
>>
>>
>> I'm a Kusu newbie, so please forgive any silly questions.
>
>Welcome!
>
>> I want to install a custom kit that I built on an existing installer
>> node. I used kitops to add the kit, and I used repoman to add (and
>> rebuild) the kit to my repository. That seems to have worked. I can
>> see the kit listed in my repository using 'repoman -l'. However, it
>> doesn't seem like the kit actually installed on my installer node. I
>> am assuming there is another step required to initiate an update on
my
>> installer node, but I'm not sure what that is. Any pointers or help
>> would be greatly appreciated!
>
>Yes, you are still missing a couple steps.
>
>First, you need to run ngedit and associate the kit's components you
>want with the appropriate nodegroup.
>
>ngedit will inform you that the nodes in this nodegroup need to be
>synced; it will offer to do this for you immediately, or give you a
>command to run later. In any case, running `cfmsync -p` after ngedit
>will perform the installation.
>
>Note that you might need to wait a little while until all the packages
>are installed.
>
>> There's a strong chance my kit isn't built correctly, but I wanted to
>> make sure I was doing the correct steps to install it first.
>>
>>
>>
>> Thanks,
>>
>> Brock Taylor
>
>Good luck!
>Mike
>
That got me through. I was able to update the installer node and see
the kit was installed.

Thanks!!

-Brock