On 12/19/2013 01:44 PM, Michael Mraka wrote:
> So do we need entitle such system at all? Nowadays there can be
> unetitled system in spacewalk. Does bootstrap entitlement brings us
> something more than current unetitled system?
Short answer: yes. Among other things, a bootstrap-entitled system can
be powered back on and provisioned.
Long answer: we use the bootstrap entitlement to distinguish bare-metal
systems from others in the Web UI: they get a different icon, some forms
are disabled where they do not make sense, we added a bare-metal
specific search page, etc.
Basically we want the sysadmin to have an "inventory" of bare-metal
systems where the only possible operations are:
- display some hardware details;
- kickstart;
- do power management;
- move between organizations.
Also, we could not find out how to create an activation key without any
entitlement. It seems like both an entitlement and a base channel are
needed in the Web UI, and even with hand-written SQL you need an
entitlement to insert a line in rhnRegTokenEntitlement, otherwise you
get an invalid token.
Server-side error:
rhnServer/server_token.fetch_token('ERROR', "Invalid token '1-<KEY_NAME>'")"
Client-side error:
Could not find token '1-nokey'
Error Class Code: 60
Error Class Info:
The activation token specified could not be found on the server.
Please retry with a valid key.
> [automatic shutdown...] That's a feature of the boot image, right?
Yes.
> So I could achieve the same with 'poweroff' in post install kickstart script.
I guess so, even though I do not understand why you would want to do that.
Idea is that the boot image is used by default before any kickstart. We
want any new bare-metal system to automatically appear in Spacewalk as
soon as it is connected to the network and powered on, to have it
"inventoried" and ease a subsequent kickstart.
Because it might take a long time (even months) between inventory and
kickstart, we automatically shut the system down in between.
> Yes, we can't create such boot image in satellite right now. So I'd have
> to create external distribution with memory only image and import it to
> satellite. Then I'd have to create an activation key which asigns no base
> channel and no entitlements to systems. And I'd also have to manage
> kickstart based on this distribution + activation key to be the default
> pxe image. Is it all I need?
I am not sure to understand who "I" refers to in the above sentences -
is it you as a Spacewalk developer or user?
With this contribution we propose to add a pre-built bootstrap image to
the files installed by Spacewalk, users should not edit it in any way.
This image gets automatically configured as default in Cobbler as soon
as the feature is enabled in the Web UI. Enabling will also create a
user-invisible activation key used by the bootstrap image on bare-metal
systems. That special key will only assign a user-invisible bootstrap
entitlement that, in turn, will be used later used to distinguish such
bare-metal systems visually.
> Just trying to figure out whether we can't achieve the same goal
> somehow easier with the current code...
We obviously also thought hard about this, but could not find out a
simpler alternative. Suggestions are welcome, as always.
Regards,
--
Silvio Moioli
SUSE LINUX Products GmbH
Maxfeldstraße 5, 90409 Nürnberg Germany
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
