Re: [MirageOS-devel] Mirage, persistence, kv store, file system, what's the plan?

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

On 10 May 2017, at 20:21, Tom Ridge <tom.j.ridge+list@xxxxxxxxxxxxxx> wrote:

Looks interesting! 

Anyone else have anything?

Hi Tom,

You may also want to follow the dev reports I've started issuing weekly on

the Moby DataKit project, where we aggregate activities around Irmin, DataKit

and filesystem protocol libraries such as 9P.

https://github.com/moby/datakit/tree/master/reports

There's significant activity around the Git and 9P libraries at the moment

(see Thomas' mail from earlier today), and Gabriel's filesystem work will also

hopefully form the basis of a pure Irmin unikernel onto block storage. This should

be fairly complementary to your own filesystem as they have different performance

profiles, so I hope we can make all of those work together.

At a management level: Is anyone co-ordinating mirage? Anil? Hannes?

As Mindy pointed out, the set of active core team members are at:

https://mirage.io/community/#team

We also have bi-weekly IRC catchups where anyone can sync up; agenda

is at; https://github.com/mirage/mirage-www/wiki/Call-Agenda

(today's log is at https://irclog.whitequark.org/mirage/2017-05-10)

Aside from this list, that meeting is a good place to discuss things synchronously.

Did you have anything else in mind from a "management" perspective?

regards,

Anil

On 10 May 2017 at 16:56, G2P code <g2p.code@xxxxxxxxx> wrote:

Hello,
I have implemented most of a KV store specifically for MirageOS.
It's available at https://github.com/g2p/mirage-storage .
My plan is to add more filesystem-like features, such as a faster
integrity check, and an Irmin backend.

On Wed, May 10, 2017 at 7:42 PM, Tom Ridge
<tom.j.ridge+list@googlemail.com> wrote:
> Dear All,
>
> Regarding Mirage and the file system, what are the plans in this area? I was
> intending to develop a kv store on tjr_btree, and then a file system on top
> of that. But I thought I would check first to see what others would like,
> are already planning, or are already implementing.
>
> (NOTE I am not overly familiar with Mirage)
>
> Thanks!
>

> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel