13:00:52 nikolam : have you tried setting up with an internal dns domain (which doesn't exist)? 13:06:14 neuroserve, hi, yes, I changed config for everything to be .internal domain 13:06:32 But I didn't reinstall form scratch per se using those settings. I might try that. 14:06:23 Hello, is there a bhyve orchestration engine? I found one called pot, but was wondering if anyone here had any experience/recommendation regarding this. 14:16:47 pot you say 15:02:35 Guest32 (LIBERA-IRC): TritonDataCenter? 15:30:12 that looks promising, thank you 15:31:34 Guest32: SmartOS has bhyve built in. You use the vmadm command to manage all types of virtual instances, including bhyve, zones, containers, docker, and kvm. 15:31:48 Triton is for managing multiple SmartOS compute nodes. 15:32:19 and for having a usable VM management interface, for me 15:32:21 You can go anywhere from two to several thousand. 15:33:29 last time I played with smartos, vmadm usage boiled down to writing JSON files which defined the VMs 15:33:33 For a single compute node, it's probably better to just use SmartOS by itself. But there are benefits with Triton starting at 2+. And the more you have, the more it makes sense to use Triton instead. 15:33:52 zizzy: That's true, but most people keep templates around. 15:34:22 zizzy: e.g.,: here are mine https://github.com/bahamat/smartos-flair/tree/master/templates 15:34:32 or if even smartos is not a hard requirement, then freebsd and https://bhyve.npulse.net/ might come handy. 15:34:54 bahamat: oh, nice, thank you 15:39:53 right, thank you all! ideally, I was looking to kubernetes-like "deployments" for SmartOS VMs, automatic failover, global monitoring, etc 15:41:47 Triton has HA/redundancy and monitoring features built in. 15:43:17 There's also a mature API and CLI tool. 15:53:39 nice! I saw zizzy talking about VM management interface, is this built in or an external package? 15:54:39 probably built-in 15:55:11 smartdatacenter is a rather large appliance which uses smartos as base, but it's hassle-free to setup 15:56:43 you can test it inside a virtual machine using CoaL image (cloud on a laptop) 15:58:33 iirc it's pretty much standard sdc image, but with absurd overprovisioning config values to make it schedule zones on a mem/cpu-limited environment, like a virtual machine 15:59:30 zones = "instances" in triton lingo, basically 15:59:59 (the term "zone" is actually derived from solaris zones, but that's just trivia) 16:07:35 I think I'll try out CoaL. thanks again!