hannes changed the topic of #mirage to: bug cleaning day every first friday in month (14:00 UTC - late, next: 2nd Feb); MirageOS 3 is released, happy hacking!
_whitelogger has joined #mirage
dtornabene has joined #mirage
dtornabene has quit [Remote host closed the connection]
dtornabene has joined #mirage
dtornabene has quit [Quit: Leaving]
reynir has quit [Quit: WeeChat 1.7.1]
reynir has joined #mirage
argent_smith has joined #mirage
kensan has quit [Quit: leaving]
mort___ has joined #mirage
demonimin has quit [Remote host closed the connection]
demonimin has joined #mirage
demonimin has quit [Changing host]
demonimin has joined #mirage
mort___ has quit [Quit: Leaving.]
argent_smith has quit [Quit: Leaving.]
kensan has joined #mirage
mort___ has joined #mirage
mort___ has quit [Client Quit]
mort___ has joined #mirage
mort___ has quit [Client Quit]
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
<mato>
I won't be around for the catchup today, have some errands to run exactly at 5pm.
<mato>
(I may be able to pop in for 15mins at some point)
<yomimono>
it's not too late to add things if there's something you'd like to discuss!
<yomimono>
first up, we have a reminder that GSoC/Outreachy/Pioneer Projects could use some attention
<yomimono>
hannes updated the Canopy data, but there's still some out-of-date information on the mirage-www wiki
<yomimono>
the xen project wiki points (correctly) to canopy now (thanks lars_kurth)! but perhaps we should remove the mirage-www content
<yomimono>
if you have new information about anything listed at http://canopy.mirage.io/tags/help%20needed , or are interested in mentoring a project not listed there, please send updates :)
<lars_kurth>
yomimono: I raised this as GSoC is coming up. Usually Google does look for the quality of Project lists. The only potential issue I can see is that on http://canopy.mirage.io/tags/help%20needed there is no easy way to find out whom to approach when interested in a project
<lars_kurth>
Related to it, was whether someone from Mirage OS is willing to be a GSoC co-admin as in the past to act as a bridge between Mirage OS and me
<hannes>
lars_kurth: agreed, while each project has an "author", we should embed the information to contact mirageos-devel@lists.xenproject.org.
<yomimono>
probably it needs to be more specific than just "contact the mailing list"
<lars_kurth>
Agreed: Normally the convention is, contact list and CC mentor.
<lars_kurth>
Anyway, think about it and let me know what you want to do. Then I can update the Xen Wiki pages accordingly
<yomimono>
lars_kurth: I'm willing to co-admin again.
<lars_kurth>
Thanks
<yomimono>
(I'm also quite happy to hand it off to someone else who is interested, fwiw.)
<yomimono>
(if that's you, please contact me or lars today, otherwise we'll proceed assuming I'll do it.)
<yomimono>
sound good to you, lars?
<lars_kurth>
Yes.
<yomimono>
great, thank you very much :) gsoc and outreachy have been great for mirageos and we really appreciate the work you do to make that possible for us.
<lars_kurth>
It's not an awful lot of work, but you will get a bit of extra e-mail and may have to chase the one or other person occasionally
djwillia has joined #mirage
<lars_kurth>
That is the co-admin job
mort___ has joined #mirage
<yomimono>
if nothing else on this topic --
<yomimono>
next up, we have a note about the next bug cleaning day, which will be friday 2nd february
<lars_kurth>
Could I ask you to do FOSDEM next? As I have some info
<yomimono>
sure lars_kurth, lay it on us :)
<lars_kurth>
Alright: The Xen Project has a booth again. As a subproject, you are welcome to hand out flyers, show demos, ...
<hannes>
lars_kurth: thanks. I'll for sure drop by (mato will come as well). I'm not sure whether anyone else will be in Brussels.
<hannes>
but we have no flyers or anything exhibition-y planned so far.
<lars_kurth>
hannes: Can you pm me with mail addresses (I am pretty bad mapping IRC handles to mail) and I can CC you on our planning thread
<yomimono>
if anyone is planning on attending and keen to plan something for the booth, perhaps mirageos-devel would be the place to arrange that
<lars_kurth>
It's up to you: it's an offer. Do you guys have any talks you give? If so, I can add to the website and our "What's going on at FOSDEM flyer
<lars_kurth>
Or I can CC mirageos-devel, but that seems a bit spammy
<hannes>
lars_kurth: no, we don't have any talks.
<lars_kurth>
OK
<hannes>
lars_kurth: I PMed you both mail addresses.
<lars_kurth>
Thanks
<hannes>
lars_kurth: and thanks for the offer! :)
<lars_kurth>
Thats all from me
<yomimono>
cool, thanks lars_kurth :)
<yomimono>
also in meatspace, the next hack retreat in marrakech is coming up: http://retreat.mirage.io/
<lars_kurth>
Just another quick FYI QubesOS will also have a booth and will have 2-3 people there
<yomimono>
7th through 18th of March, "pls sign up" - anything else we should note, hannes?
<hannes>
yomimono: no, apart from please sign up soon :)
<hannes>
djwillia: are you guys planning another trip to marrakesh? :)
<djwillia>
hannes: not in march, unfortunately, but maybe at the end of the year if it happens again
<hannes>
djwillia: ok, good to know. it's likely to happen again..
<djwillia>
cool!
<yomimono>
if that's all -
<hannes>
but taking one step back, we had a bug cleaning day on jan 5th, and ~50 issues were closed over the mirage organisation. I think these are very effective -- more participants are welcome! :)
<yomimono>
+1 !
<hannes>
(I liked the one in november more, where we shifted ~35 repositories away from the mirage organisation ;)
<reynir>
o/ from the airport
<yomimono>
I think there may be more opportunity there :P
<yomimono>
the next one will be right before FOSDEM (2nd feb to FOSDEM's 3rd and 4th feb), so if you're attending that you can brag about what you got done the day before :P
<yomimono>
(of course we are all welcome to fix and close issues outside of bug cleaning day as well ;)
<yomimono>
if nothing else -
<yomimono>
niks3089, there's an item "thoughts on providing support for DPDK and/or SR-IOV"
<yomimono>
not sure whether this is "niks3089 has thoughts" or "niks3089 wants your thoughts", maybe both?
<niks3089>
Yes, both!
<niks3089>
Hi all, I am researching on NFV/network performance for Unikernels. Since mirageOS now has netmap support thanks to solo5/ukvm, I wanted to look at providing support for dpdk . I would like to investigate and determine the network performance and do a comparison and show my findings. Does this sound like a good idea? Would like to know your thoughts on this
<niks3089>
I reached out to Timada regarding netmap support in solo5, I want to try out his changes and run some performance tests
<djwillia>
i have not tried out the netmap support
<niks3089>
I wanted to know if there is a process in order to start these kind of projects, regarding whom to contact, if anyone is willing to mentor and help with answering a bunch of questions i had
<yomimono>
niks3089: we don't have anything super formal. it's generally a good idea to drop a mail to the mirageos-devel list saying what you want to do first of all
<djwillia>
ricarkol and I would be happy to answer questions
<yomimono>
probably the right people to mentor this project would be those who know a lot about solo5 :)
<yomimono>
jinx! thanks, djwillia.
<hannes>
I agree, mirageos-devel sounds like a good starting point (I'm also interested in your design including DPDK, and your findings) :)
<niks3089>
right, I have discussed this briefly with rickarkol
<yomimono>
we've had a few people interested in dpdk over last year or so (iirc chris fegan who attended the second hack retreat was also interested in this space), but afaik not much beyond ideas so far
<djwillia>
where have you guys been discussing?
<hannes>
niks3089: you can also create a project page on our canopy (https://canopy.mirage.io/Projects) by extending the mirage/canopy-data repository
<niks3089>
great, i'll create on right away
<niks3089>
djwilla: We've been talking over email. I had worked on a feature for solo5 with his helpp
<niks3089>
thanks. I'll also send an email in mirage-os asking for feedback. Essentially I would like to know how the netmap based conduct experiments, hardware and tools required. Benchmarking etc
<djwillia>
have you successfully run Timada's netmap code?
<mk270>
sort of: any tips on what things need to be documented first, other than fixing the contributors page ... also if there's someone who can point me at a good example of persistent storage
<yomimono>
thomasga (looks like not present, but he reads logs) is currently doing lots of work around persistent storage
<mk270>
i stuck this on the agenda for the previous fortnightly irc meet, and then ended up with no internet access when it took place
<mk270>
my understanding is that there's not a lot to talk about *yet* on the persistent storage front - is that correct?
<yomimono>
I'm not sure about *good* but there is an example in mirage-skeleton. mirage-www also reads from persistent storage although it makes no use of writing
<mk270>
yes, i'm looking for examples of writing. i shall check again in mirage-skeleton
<yomimono>
mk270: less true than it used to be. the combination of irmin + wodan + existing block support should make it quite possible but it seems there are details to be worked out there
<yomimono>
mk270: yeah, my advice for writing to persistent storage with the existing filesystem support is "don't"
<mk270>
fair enough. it's sometimes hard to distinguish between "works ok today" and "will work soon" / "used to work before vX.Y of some dependency"
<yomimono>
if you don't care about filesystems, it works great!
<mk270>
i'm agnostic about filesystems; writing to raw block device counts
<yomimono>
in that case, it works great!
<yomimono>
it's definitely not "works ok today" unless you want to just write to a raw block device
<mk270>
it used to be my job not to care about filesystems; a hard mentality to fix
<reynir>
heh
<yomimono>
I need to set up some more thorough tests for this anyway because of some work in mirage/mirage , so I can cc you on that
<mk270>
yomimono: :)
<yomimono>
the mirage-skeleton example does write some stuff to a block device, then read it back
<mk270>
it looks to me like "you don't get a filesystem, but can i interest you in this raw device that you write to via Irmin?" might be viable in a few months ... is that a sensible reading?
<yomimono>
where "raw device" is slightly more complicated, yes
<mk270>
ok - i had not spotted the mirage-skeleton app that did that, and as i said i'll look again - the plumbing for "how do i tell mirage about /dev/vg0/my-raw-lv" is important even if the unikernel that uses it is trivial
<yomimono>
yeah, it's in (iirc) device-usage/block
<mk270>
no worries - v little progress so far, but one must simply keep plugging away at it
<yomimono>
the human condition
<mk270>
it also kicks a different subset of tyres from the other routine activities that the community engages in
<yomimono>
sounds like as good a place to end as any :)
<yomimono>
thanks for attending, everyone!
<hannes>
thx for running the meeting, yomimono!
niks3089 has quit [Quit: Page closed]
<yomimono>
thanks for sending the reminder email, hannes :)
<djwillia>
thank you
<yomimono>
my computer and I are off to buy the biggest bag of rock salt they sell at the little neighborhood hardware store
<yomimono>
stay warm and/or cool, all!
yomimono has quit [Quit: Leaving]
<lars_kurth>
yomimono, hannes: I have another question which has been bothering me for a while. Have you agreed on an official list of repos for MirageOS yet? I am still using TROVE for https://xen.biterg.io/goto/fbac70861be5f69f07d68753a5ddb120
<lars_kurth>
If not, could you add that to one of the future meeting agenda items
ricarkol has quit [Quit: Leaving.]
<hannes>
lars_kurth: I'm adding it to the agenda in 2 weeks!