From: Adriana Kobylak <anoo@linux.ibm.com>
To: Nancy Yuen <yuenn@google.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
openbmc <openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org>
Subject: Re: What do you want in a package manager?
Date: Thu, 23 Jul 2020 14:57:42 -0500 [thread overview]
Message-ID: <a7949f916cf122cbc4ef1a3fb1d354ca@linux.vnet.ibm.com> (raw)
In-Reply-To: <CADfYTpGaahSo5oJ5n-Y2TZ=NoF0uh=BcPHkxuDqY4zuek7qrjQ@mail.gmail.com>
On 2020-07-21 02:57, Nancy Yuen wrote:
> I'm looking into package management for BMCs in our fleet. I'm
> wondering who else is interested in this, does it make sense for
> OpenBMC. What kind of features are important? What kind of package
> format (rpm, deb, something else)?
>
> We have a distributed system dictating versions of software (BIOS, OS,
> userspace packages, other firmware) which should be on a particular
> machine (based a machine's characteristics like type, owner, etc). So
> our use case has the BMC take a list of packages to be installed,
> natively installing the packages on the BMC.
Something around that area is this new recipe[1] to add a host fw image
to the BMC image at build time[2]. It'd be useful to have a manager that
would use different recipes to build a final image based on different
pieces.
> Packages must be signed
> and verified during installation.
To support the new image file provided by the host fw recipe, the
bmc-code-mgmt-repo added the concept of 'optional images'[3] that would
allow additional files to be included in the code update tarball and
enforce signature verification on them. Maybe that can be used/expanded
as we add support for additional packages.
> There is also the concept of
> deviation checking. If the files for a package or some parts of the
> file system deviates from what's expected, it triggers some kind of
> repair flow.
>
> ----------
> Nancy
1.
https://github.com/openbmc/meta-phosphor/commit/39b1ff0dcd12f15dc651aa20cb85cdec903cb5de
2. https://gerrit.openbmc-project.xyz/c/openbmc/meta-aspeed/+/34618
3.
https://github.com/openbmc/phosphor-bmc-code-mgmt/commit/73609bb51c8c43d471ba373317455d3cbe5c5c32
prev parent reply other threads:[~2020-07-23 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 7:57 What do you want in a package manager? Nancy Yuen
2020-07-21 15:17 ` Patrick Williams
2020-07-21 21:10 ` Nancy Yuen
2020-07-22 13:19 ` Vijay Khemka
2020-07-23 19:57 ` Adriana Kobylak [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a7949f916cf122cbc4ef1a3fb1d354ca@linux.vnet.ibm.com \
--to=anoo@linux.ibm.com \
--cc=openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org \
--cc=openbmc@lists.ozlabs.org \
--cc=yuenn@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.