From: Paul Fertser <fercerpav@gmail.com>
To: Adriana Kobylak <anoo@linux.ibm.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: Settings backup and restore tool prototype using Ansible -- RFC on a published project
Date: Tue, 25 Mar 2025 23:19:31 +0300 [thread overview]
Message-ID: <Z+MP02Uckh6jt/3O@home.paul.comp> (raw)
In-Reply-To: <F4A34EF4-9572-4863-97BB-8ACA4B7FF1A5@linux.ibm.com>
Hello Adriana,
On Tue, Mar 25, 2025 at 02:31:33PM -0500, Adriana Kobylak wrote:
> Some previous discussion on Backup and Restore for
> reference: [1]https://lore.kernel.org/all/YiEbhAQEdJzf706i@heinlein/T/#m50f639da25e073f973e18b5728c15cc1bf61d168
> In summary, the DMTF is open to having a schema proposal submitted, they're just
> looking for someone from the OpenBMC community to help drive it.
That's interesting, thank you. Guess I have seen it before but since
the link to the issue was (and still is) 404 it wasn't that
informative.
What do you think about my approach though? I would think it can work
right away with many different existing Redfish backends
implementations without going through standartisation process and
covers a wide range of actual usecases. In my first mail I outlined
the core ideas which are trivially expandable to proper user stories
if needed, so it's not just a "feature" but one can clearly describe
why, who, when and where could be using that "what".
Do you have other related and relevant usecases in mind that can not
be nicely covered by that prototype I've shown?
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com
next prev parent reply other threads:[~2025-03-25 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 9:36 Settings backup and restore tool prototype using Ansible -- RFC on a published project Paul Fertser
2025-03-25 19:31 ` Adriana Kobylak
2025-03-25 20:19 ` Paul Fertser [this message]
2025-06-05 9:28 ` Johannes Truschnigg
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=Z+MP02Uckh6jt/3O@home.paul.comp \
--to=fercerpav@gmail.com \
--cc=anoo@linux.ibm.com \
--cc=openbmc@lists.ozlabs.org \
/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.