On Sep 1, 2006, at 3:53 PM, Matt Williamson wrote:
> Gregory Shaw wrote:
>>>>
>>> This is something we are thinking about and working on. The flow
>>> of control in our existing GUI, specifically the sysid questions
>>> for installation is clearly broken. We don't need to ask so many
>>> questions for Solaris installation. A lot of it can be gleaned
>>> from the existing system or from the network.
>> I'd like to see this go one step farther: Load the sysid and
>> configuration information into a centrally available repository
>> that could be queried instead of asking questions.
>
> Isn't this possible, to some degree, today?
>
> http://docs.sun.com/app/docs/doc/817-5504/6mkv4nh2i?a=view
>
> Chapter 6 Preconfiguring System Configuration Information (Tasks)
>
> This chapter describes how to preconfigure system information.
> Preconfiguration can help you to avoid being prompted for this
> information when you install the Solaris OS.
>
It's possible, but anything beyond the simple requires a lot of
knowledge, and a lot of time and effort.
For instance, I'd like to be able to configure client machines with
the following:
- a minimal set of services running
- certificates for the LDAP name services
- a software set that represents the exact set of packages necessary
- I want it to be the same across multiple architectures
- Syslog should be configured properly
- and lots of other options that require questions or scripts to run
after install
Much of the above could be done with a flar. However, creating a
flar is a time-consuming business that must be repeated with every
architecture and OS change.
If I could specify the configuration for a particular machine in a
web page, that could be saved as the system config. Future upgrades
or clones could use that same information.
It's only one step further to turn the above into an asset management
tool.
>> The current jumpstart can be automated with start and end scripts,
>> but that's a very complex solution. If a central repository for
>> information were available, it would be possible to boot a CD (or
>> across the net), type in a URL for the configuration information,
>> and stand back as the system installs itself.
>
> Some things, such as JET <http://www.sun.com/bigadmin/content/jet/
> index.html>, ease the complexity. While it is not for everyone,
> some do find JET quite useful.
>
> And you can specify a sysidcfg file via url at boot time although
> it is not documented very well, or at least I can't find it.
>
> SPARC <http://docs.sun.com/app/docs/doc/817-5506/6mkv6ki9g?a=view>
> X86 <http://docs.sun.com/app/docs/doc/817-5506/6mkv6ki9q?a=view>
>
> Matt
>
>
I don't disagree on JET. However, it's a big leap from a solaris CD
to JET. I'd like to make it so that configuring an excellent
jumpstart and boot configuration system can be done without a senior
sysadmin. The use of a configuration server for an entire
corporation would drive down the cost of using solaris within the
environment significantly.
As it stands today, most groups have their own jumpstart server and
processes for jumping machines. It works, but it doesn't need to be
that complicated.
-----
Gregory Shaw Programmer, SysAdmin
fmSoft, Inc. Network Planner
shaw at fmsoft.com And homebrewer...
Prayer belongs in schools like facts belong in organized religion.
Superintendant Chalmers - "The
Simpsons"
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/install-discuss/attachments/20060901/7f37d1a7/attachment.html>
