All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Truschnigg <johannes@truschnigg.info>
To: openbmc@lists.ozlabs.org
Subject: Re: Settings backup and restore tool prototype using Ansible -- RFC on a published project
Date: Thu, 5 Jun 2025 11:28:28 +0200	[thread overview]
Message-ID: <aEFjPIgHlz4i5VG0@vault.lan> (raw)
In-Reply-To: <Z+MP02Uckh6jt/3O@home.paul.comp>

[-- Attachment #1: Type: text/plain, Size: 798 bytes --]

On Tue, Mar 25, 2025 at 11:19:31PM +0300, Paul Fertser wrote:
> [...]
> 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. [...]

I just wanted to let the list know that `ansible_redfish_settings` helped me a
great deal in getting a small fleet of ten new servers deployed the other
week, even though their BMCs are not equipped with firmware based on OpenBMC
at all. I highly recommend taking a close look at Paul's approach if you have
to wrangle many BMC configs at once.

-- 
with best regards:
- Johannes Truschnigg ( johannes@truschnigg.info )

www:   https://johannes.truschnigg.info/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2025-06-05  9:37 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
2025-06-05  9:28     ` Johannes Truschnigg [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=aEFjPIgHlz4i5VG0@vault.lan \
    --to=johannes@truschnigg.info \
    --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.