hannes changed the topic of #mirage to: https://mirage.io - bug cleaning day every first friday in month (14:00 UTC - late, next: Feb 1st) - next call Jan 9th 16:00 GMT https://github.com/mirage/mirage-www/wiki/Call-Agenda - this channel is logged at http://irclog.whitequark.org/mirage/ - MirageOS 3.3.1 is released - happy hacking!
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
Haudegen has quit [Read error: Connection reset by peer]
iovec has joined #mirage
_whitelogger has joined #mirage
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
djs55 has joined #mirage
jnavila has joined #mirage
Haudegen has joined #mirage
_whitelogger has joined #mirage
jnavila has quit [Ping timeout: 246 seconds]
mort___ has joined #mirage
jnavila has joined #mirage
djs55 has quit [Quit: Leaving.]
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
djs55 has joined #mirage
mort___ has quit [Quit: Leaving.]
superherointj has joined #mirage
<superherointj> How do you deploy MirageOS to production? Which cloud companies/service is used for hosting?
<superherointj> Would it make sense to make a docker image and deploy using docker instead of Xen/Kvm?
<h01ger> superherointj: depending on your use case, yes
Haudegen has quit [Remote host closed the connection]
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
<superherointj> h01ger, for production, is it good idea? Xen/Kvm would cause a situation of "nested virtualization" and I'm not sure how it plays out. But docker could be nested VT as well. Humm...
<h01ger> 'for production' can mean a zillion things, and there are cases where i would not touch docker with a 10m stick, and there are some, where i might even consider docker. sometimes...
<superherointj> I see docker isnt needed if I had direct access to Xen/KVM hosts. My question is, how people using MirageOS usually approach this situation of having to host on cloud?
Haudegen has joined #mirage
djs55 has quit [Quit: Leaving.]
djs55 has joined #mirage
djs55 has quit [Quit: Leaving.]
superherointj has quit [Ping timeout: 246 seconds]
<hannes> hmm, superherojointj left now... but to add to his question -- solo5 just got a new backend using seccomp, so it is now easily possible to deploy MirageOS unikernels as processes (see nabla-containers for some description thereof, although the seccomp-solo5 patch was a major rework of nabla-containers).
<h01ger> nice
<hannes> and FWIW, the current solo5-hvt deployment story is being worked on actively... :)
<hannes> it is a bit tricky since the tender (host system process) is tailored for each unikernel (depending on which modules are required there) -- but this is going to be revised in the near future
superherointj has joined #mirage
<hannes> superherointj: pls see above (or http://irclog.whitequark.org/mirage/)
<hannes> I personally deploy atm MirageOS solo5 hvt virtual machines on my own hardware which I have in some data center (yes, I know this is not too common anymore)
djs55 has joined #mirage
<apache2> you can just compile for the unix target and run them inside linux
djs55 has quit [Quit: Leaving.]
djs55 has joined #mirage
djs55 has quit [Client Quit]
djs55 has joined #mirage
djs55 has quit [Client Quit]
<superherointj> hannes, thanks for answering. I'll have a look.
<hannes> superherointj: I think for Xen servers, there is somewhere a shell script, and there is also somewhere a script to deploy to GCE using the virtio target of mirageos (which btw also emits a libvirt xml deployment file) -- so it really depends on your scenario / hosting provider -- and as remarked above there's quite some work in progress to streamline the deployment step
mort___ has joined #mirage
mort___1 has joined #mirage
mort___1 has quit [Client Quit]
mort___ has quit [Ping timeout: 240 seconds]
Haudegen has quit [Remote host closed the connection]
djs55 has joined #mirage
djs55 has quit [Ping timeout: 244 seconds]
superherointj has quit [Ping timeout: 268 seconds]
Haudegen has joined #mirage
superherointj has joined #mirage
mort___ has joined #mirage
superherointj has quit [Ping timeout: 240 seconds]
mort___ has left #mirage [#mirage]
mort___ has joined #mirage
jnavila has quit [Ping timeout: 252 seconds]
superherointj has joined #mirage
superherointj has quit [Ping timeout: 246 seconds]
superherointj has joined #mirage
superherointj has quit [Ping timeout: 250 seconds]
mort___ has quit [Quit: Leaving.]
Haudegen has quit [Remote host closed the connection]