From: "Czarnowski, Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@linux.intel.com>
To: Ed Tanous <ed@tanous.net>,
"Hawrylewicz Czarnowski,
Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@intel.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Virtual Media repository request
Date: Mon, 13 Dec 2021 20:17:27 +0100 [thread overview]
Message-ID: <71f145ed-47bb-44b0-eb9f-35a56bc353b9@linux.intel.com> (raw)
In-Reply-To: <CACWQX81Q0w=oK_Sv9OHKrMo5pj2-HaPEW8Dh1MEuRDjNSQKKaA@mail.gmail.com>
On 11.12.2021 22:13, Ed Tanous wrote:
> On Tue, Dec 7, 2021 at 7:52 AM Hawrylewicz Czarnowski, Przemyslaw
> <przemyslaw.hawrylewicz.czarnowski@intel.com> wrote:
>>
>> Hi.
>>
>> I would like to request for new Virtual Media service repository (based on the design document located here: https://github.com/openbmc/docs/blob/master/designs/virtual-media.md).
>
> Considering that the virtual media already uses pieces of
> functionality from the old virtual media, why wouldn't this just go in
> https://github.com/openbmc/jsnbd
>
> Ideally we shouldn't need two different virtual media implementations,
> and my understanding is that the "new" one is a complete replacement
> for jsnbd, while still using the javascript portions of it; Moving
> the implementation there will simplify when people look for virtual
> media, and will promote the reuse of code, so I think that's what we
> should do.
I think it depends. From my perspective, mixing javascript and service
code is not a good thing. They come from different origins and does
quite different job (even if they are connected together)
Moreover virtual media service if far more than the current
implementation. Old functionality is just at least 1/4 of the
possibilities of new service.
This is, of course, my personal insight. There are more competent people
with wider background in OpenBMC to make the final decision.
Przemek
>
>>
>> The service itself is a reworked Virtual Media which early stage is available here: https://github.com/Intel-BMC/provingground.
>>
>> And additional question: is there anything to do in order to enable CI for this repo?
>
> I believe CI is already enabled for jsnbd, so I think we're already
> good to go there.
>
>>
>> --
>> Best regards,
>> Przemyslaw Czarnowski
>>
--
Best regards,
Przemyslaw Czarnowski
prev parent reply other threads:[~2021-12-13 19:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 15:50 Virtual Media repository request Hawrylewicz Czarnowski, Przemyslaw
2021-12-08 16:56 ` Patrick Williams
2021-12-09 8:56 ` Czarnowski, Przemyslaw
2021-12-09 10:41 ` i.kononenko
2021-12-13 16:10 ` Patrick Williams
2021-12-13 19:44 ` Czarnowski, Przemyslaw
2021-12-14 2:11 ` Jeremy Kerr
2021-12-15 19:26 ` Ed Tanous
2021-12-17 9:28 ` Czarnowski, Przemyslaw
2021-12-17 9:45 ` Jeremy Kerr
2021-12-20 12:54 ` Czarnowski, Przemyslaw
2021-12-23 1:01 ` Czarnowski, Przemyslaw
2022-12-19 14:01 ` Czarnowski, Przemyslaw
2022-12-19 17:43 ` Ed Tanous
2023-01-03 5:36 ` Jeremy Kerr
2021-12-11 21:13 ` Ed Tanous
2021-12-13 19:17 ` Czarnowski, Przemyslaw [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=71f145ed-47bb-44b0-eb9f-35a56bc353b9@linux.intel.com \
--to=przemyslaw.hawrylewicz.czarnowski@linux.intel.com \
--cc=ed@tanous.net \
--cc=openbmc@lists.ozlabs.org \
--cc=przemyslaw.hawrylewicz.czarnowski@intel.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.