21:21:25 hey guys. gotta ask, what does the pricing of 0.009$ /gb per month mean in SmartOS context? 21:21:46 transferred data of the public images? 22:21:58 zt3phan, I think you are referencing our Triton support pricing for Manta. 22:28:55 aha..i was on a site that stated that price i was like wtf :p 22:29:04 that explains it. 22:30:14 how long until EOL for your latest LTS release? could'nt find a specific date/year. 22:38:51 SmartOS, Triton, and Manta are all 100% open source an can be used without a fee. 22:39:32 bahamat, nwilkens; ty 22:40:15 Triton and Manta support contracts are available. Without a contract, we only have an SLA for the discuss mailing lists. You're welcome to ask questions in either IRC, Discord, or Matrix, but there's no assurance anyone will be listening at any particular time. 22:40:33 On the mailing lists we'll definitely get back to you, but there's no bounded time frame for it. 22:41:01 As far as LTS goes, there are several different components to consider. 22:41:31 First, you should read this: https://www.illumos.org/docs/contributing/qds/ 22:41:49 ty 22:42:27 SmartOS and Triton have fairly strong assurances on committed public interfaces. If there's a documented public interface, we will not break it. 22:42:46 If it does break, that's a regression bug that requires fixing ASAP. 22:43:34 So in that sense, SmartOS/Triton/Manta are perpetually rolling LTS (if that's not too much of a contradiction) 22:43:56 Images have different LTS statuses. 22:44:23 im talking straight SmartOS 22:45:13 Straight SmartOS has strong guarantees about backward compatibility. 22:45:30 noted on one site selling usb's, they offered smartos blabla 2023 LTS 22:45:55 Yeah, which doesn't really make sense. What website is this? 22:46:01 WE don't mark SmartOS releases as LTS per se. 22:46:10 Now OmniOS does, so perhaps the vendor Got Confused? 22:46:15 gotta check, gimme a sec 22:49:21 SmartOS itself, being a live image, we don't really do revisions of releases. We do have branches for them, so if you require it, you can build an old release branch with minor modifications. 22:49:55 But in general, a but in a platform image can get a fix in the next platform image release. 22:50:44 Updating to new versions should always be safe, and rollbacks are extremely easy, if the need arises. 22:50:57 Either upgrading or downgrading is just selecting the desired PI and rebooting. 22:51:41 i getcha. 22:52:23 dancmd: mightve been that case,yes. 22:52:37 can't find it atm. 22:52:57 Instance images where we are not the 1st party vendor (e.g., Linux images), we don't provide any support for the distro itself. 22:53:59 We do support where it interacts with SmartOS. So a bug in bhyve that causes ill behavior in Linux, that's on us. The SmartOS guest tools, or interacting with the metadata interface, that's all on us. 22:54:40 But like nginx, or postgres behavior that's a legit bug in the 3rd party software, you need to deal with the distro, or original authors. 22:56:12 Native zone images (e.g., base-64-lts, minimal-64-lts, etc) each Q4 yearly release is LTS for three years. That means that the software versions are relatively stable. Security fixes are made available where possible. 22:57:49 In some cases you might end up with like some software like foo-1.37, and they fix a security issue in v2.0. Backporting that may be extremely difficult so a new foo2-2.0 package might be added so that they don't conflict, and you can decide when you're ready to make the major version bump. 22:59:06 i understand ya.