[OmniOS-discuss] Repos

[Eric Sproul]

On Tue, Jan 1, 2013 at 8:27 PM, Denis Cheong <denis at denisandyuki.net> wrote:

>
> On Wed, Jan 2, 2013 at 11:45 AM, Brian Hechinger <wonko at 4amlunch.net>wrote:
>
>> On 1/1/2013 5:09 PM, Denis Cheong wrote:
>>
>>> The ms is not really useful if you want stuff to 'just work' ... apache
>>> from ms takes a LOT of work to get running from the ms repository.
>>>
>>
>> Actually, I found apache in ms to not be terribly hard to set up. My main
>> issue with ms is the lack of SMF bits.
>>
>
> Apache from ms did not come with anything configured - the /www directory
> structure where it stores everything isn't created, the config file doesn't
> have any PHP in it, there are missing support programs (including ones that
> are not even available) ... no docs means that you have to figure out all
> this yourself.
>

As noted here: http://omnios.omniti.com/wiki.php/Packaging the
ms.omniti.compackages are what we use internally.  We have additional
internal setup
protocols when we use these packages.  They serve our needs, though we
don't mind letting others use them.  As for docs, everything you need to
know about Apache is at http://httpd.apache.org/docs/


> SMF bits are there from ms, they are just not installed by default ... you
> have to import them in (and of course there's no docs yet).  Not sure why
> these packages only half-install them like that ... other than that because
> they do not have a working configuration out of the box, installing them
> into SMF would be premature - you have to finish doing the install manually
> before there's any use installing the SMF entries.
>

The SMF manifest that ships with Apache is an example.  Each of our
internal projects keep their own customized manifests in our configuration
management systems.  The one in the package is there to serve as a guide
for our developers when setting up a new instance.

It's early days I guess ... while I understand and appreciate that OmniOS
> is 'minimalistic' in its base install, it would be nice to be able to say
> with a few simple commands:  Create me a web server zone, and install
> Apache with PHP and Zend, and have it be up and running with a working
> configuration without needing to edit a single config file.
>
> Likewise with "create me a MySQL server zone" ...
>
> Lack of the ability to get working configs up and running easily is going
> to hold back OmniOS from broader adoption IMHO...
>

It sounds like you want a configuration management tool.  An operating
system or package install cannot possibly account for all permutations of
user requirements.  The things you say you want are necessarily
site-specific, and these days there are numerous choices for
programmatically describing the setup you want.  See Chef, Puppet,
cfengine, etc.  The OS and packages are your raw materials, from which you
construct the kinds of systems you want, either hand-crafting them or using
additional tools as your "factory".

Another way to get what you want would be to roll your own packages that
put things where you want, install your SMF manifests, and contain
site-local configs.  Feel free to fork
https://github.com/omniti-labs/omnios-build.git and roll your own.  We're
happy to lend advice with getting a build environment set up.

Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://omniosce.org/ml-archive/attachments/20130102/a30dcbad/attachment.html>