All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Chris Austen <austenc@us.ibm.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: possible hackathon
Date: Thu, 23 Mar 2017 14:00:50 +1100	[thread overview]
Message-ID: <87y3vwu271.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <OF3D2CC421.3C763A88-ON862580EB.006DE8D6-862580EB.0078D20E@notes.na.collabserv.com>

Chris Austen <austenc@us.ibm.com> writes:
> I'm not saying there is, but if there was a possibility for a hackathon are
> there any ideas out there that would be of interest?  Some things off the
> top of my head would be...
>
> Updated simulation model
> remote python scripts to collect thermal data from the host
> Redfish dbus discovery
> bmc swarm... talk dbus over multiple BMCs
> System XML builder
> OpenStack Ironic pluggin

op-test-framework integration.

I have the most basic of basic bits of OpenBMC support:
https://github.com/open-power/op-test-framework/blob/master/common/OpTestOpenBMC.py

but it lacks support for literally everything except getting access to
host console.

The reality is, if we're going to ship OpenBMC based OpenPOWER machines,
we need to be able to test them with our automated tests, which means
either the current REST API has to be consumed, or something like
RedFish needs to happen (and be consumed).

It could be helpful to have the OPAL test teams work alongside OpenBMC
dev on this and a good view into the world of living with OpenBMC?

-- 
Stewart Smith
OPAL Architect, IBM.

  reply	other threads:[~2017-03-23  3:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22 21:59 possible hackathon Chris Austen
2017-03-23  3:00 ` Stewart Smith [this message]
2017-03-27 10:39 ` Benjamin Herrenschmidt
2017-03-28  3:46   ` Lei YU
2017-03-28  4:09   ` Joel Stanley

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=87y3vwu271.fsf@linux.vnet.ibm.com \
    --to=stewart@linux.vnet.ibm.com \
    --cc=austenc@us.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.