From: Adriana Kobylak <anoo@linux.ibm.com>
To: ed.tanous@intel.com
Cc: openbmc@lists.ozlabs.org, Jeremy Kerr <jk@ozlabs.org>
Subject: Re: Virtual Media
Date: Mon, 10 Dec 2018 11:43:59 -0600 [thread overview]
Message-ID: <0d755df3a97b91ceebcdb7b50d403741@linux.vnet.ibm.com> (raw)
In-Reply-To: <eb74222a-737f-92cb-66a3-8d023b5962dc@ozlabs.org>
Hi Ed,
> - the nbd infrastructure allows us to use a unix domain socket (rather
> than a network socket) for that interface.
> - Using a websocket proxy, we can connect that process' stdio to a
> websocket.
As you pointed out, the Redfish schema for Virtual Media may not fit
with this design, so wanted to get your thoughts on how/if we could
somehow implement having the client request to mount the device via a
websocket, like by calling the VirtualMedia/<device_id> api, or could we
leverage some other schemas, or what would be your suggestion? Thanks!
Reference:
https://gerrit.openbmc-project.xyz/#/c/openbmc/bmcweb/+/16481/
https://gerrit.openbmc-project.xyz/#/c/openbmc/phosphor-rest-server/+/14752/
next prev parent reply other threads:[~2018-12-10 17:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 21:55 Virtual Media Matt Spinler
2018-07-26 16:29 ` Matt Spinler
2018-07-27 9:06 ` Jeremy Kerr
2018-07-31 18:02 ` Vernon Mauery
2018-08-01 0:56 ` Jeremy Kerr
2018-08-01 4:12 ` Stewart Smith
2018-08-01 4:18 ` Jeremy Kerr
2018-08-01 5:07 ` Stewart Smith
2018-12-10 17:43 ` Adriana Kobylak [this message]
2018-12-10 19:13 ` Ed Tanous
-- strict thread matches above, loose matches on Subject: below --
2019-10-09 21:11 Rapkiewicz, Pawel
2019-10-10 19:30 ` Adriana Kobylak
2019-10-10 22:21 ` Ed Tanous
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=0d755df3a97b91ceebcdb7b50d403741@linux.vnet.ibm.com \
--to=anoo@linux.ibm.com \
--cc=ed.tanous@intel.com \
--cc=jk@ozlabs.org \
--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.