Why OpenBMC not ready for production?

[Patrick Williams]

On Tue, Dec 20, 2016 at 11:30:29PM +0300, Илья Кузнецов wrote:
> Hello,
> Could you please advice if there are any architectural problem in OpenBMC design or current implementation issues which do not allow use it in end-customer environment?
> What significant efforts should be applied to get it ready? It is
> rather rhetorical question, but still I would like to hear opinion of
> development team.

Ready for production can mean one of two things (or some combination of
both):

    - Has sufficient functionality to fit our needs.
    - Has sufficient stability to fit our needs.

There are two branches within our OpenBMC tree: v1.0 and master.  v1.0
was the branch that shipped / ships on the P8 Barreleye machine.  It has
relative stability but only functionality that was specifically
requested by that group.  In that sense it is "ready for production".  Master
is where we are doing our development for next-generation products (P9) and
as such it currently has less stability than the v1.0 branch.

There are architectural changes being done between v1.0 and master to
better support additional machines and features in the long-term.  In
some cases, the v1.0 code implementation was machine-specific and we are
working to make the master version more generic.  Master is not
currently in a shape where you would place it into production, from a
stability perspective, but we have a path to get there as we near the
end of this major development cycle.

As far as functionality, the master branch is not adding significant
functionality above what the original v1.0 Barreleye code had, but there
are some specific adds.  I can either point you to Github where we have
the "2.0" milestone identified or you can ask about specific features
you might be interested in and if we currently plan to have that
complete.

-- 
Patrick Williams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20161221/d89a478d/attachment.sig>