re: capstan hosting infrastructure: my knowledge is a bit rusty, but I believe that Casptan has the ability to create a repository, so it would be a matter of "renting" space on a public cloud and providing a method of access for posting, plus a way to browse the repository to find images of interest.
that way we could build up a supply of community images and get things rolling... as it is now (or used to be), only the base osv images are posted, and you have to build everything starting from those. As an example, I built a osv+perl image. Then I added cado (my codegen/templating language). so now we have three images that need posting: osv_base, osv_base+perl, osv_base+perl+cado. if I wanted to build a cado service, then I could then start with the third image. similar for any other language env... or web-services platform. think of what it would take to build a complex web-service api composed of many unikernels, for example. then of course you need an orchestration tool to manage your growing stable of unikernel services... like a rewrite of kubernetes designed to run unikernels instead of (or in addition to) docker images. I think there is a demand for unikernels in the microservices space, but I'm no market expert.. cheers. /r P.S. many apologies for hijacking your thread! we had a thread about this a couple of years back which didn't go anywhere - search for "Casptan" in the list. P.P.S: there is an interesting research project funded by VMware that provides the ability to manage vm's like containers: https://github.com/vmware/vic At 6:57 AM -0700 8/10/18, adamrgil...@gmail.com wrote: >Russ - I'd be interested in something like that. What kind of infrastructure >is needed to do the hosting like you suggest? > >nzois - Yes, I only plan to cluster for high availability of a mem cache >layer. I don't need replication as the app would just fetch updated database >data for the cache layer if it was missing. My concern is more about just only >having 1 active redis instance (currently) and not some sort of active backup >in case that server goes down. When I was reading about the clustering on >redis.io I was more interested in the Redis Sentinel. > >Are you saying I can change my Redis OSv ESXi deployment to support the >Sentinel HA cluster without rebuilding the OSv image? I was under the >impression from Waldek that any config change to OSv requires rebuilding the >image. > >-- >You received this message because you are subscribed to the Google Groups "OSv >Development" group. >To unsubscribe from this group and stop receiving emails from it, send an >email to osv-dev+unsubscr...@googlegroups.com. >For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to osv-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.