April 7, 2017 
< | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | >
April 7, 2017 [03:53:23] *** shyu <shyu!~shyu@106.38.122.3> has joined #project-FiFo[09:55:27] *** _ADN_ <_ADN_!~username@host86-173-158-83.range86-173.btcentralplus.com> has quit IRC (Ping timeout: 240 seconds)[10:11:15] *** _ADN_ <_ADN_!~username@5.148.34.186> has joined #project-FiFo[10:18:01] *** _ADN_ <_ADN_!~username@5.148.34.186> has quit IRC (Ping timeout: 268 seconds)[10:25:55] *** dexta <dexta!~D3XTA@host86-185-205-100.range86-185.btcentralplus.com> has quit IRC (Ping timeout: 240 seconds)[10:28:20] *** dexta <dexta!~D3XTA@host86-185-205-100.range86-185.btcentralplus.com> has joined #project-FiFo[10:30:51] *** _ADN_ <_ADN_!~username@5.148.34.186> has joined #project-FiFo[13:20:51] *** shyu <shyu!~shyu@106.38.122.3> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)[19:24:47] *** wiedi <wiedi!~wiedi@ip5b41bdb7.dynamic.kabel-deutschland.de> has quit IRC (Read error: Connection reset by peer)[19:25:23] *** wiedi <wiedi!~wiedi@ip5b41bdb7.dynamic.kabel-deutschland.de> has joined #project-FiFo[19:43:24] *** wiedi <wiedi!~wiedi@ip5b41bdb7.dynamic.kabel-deutschland.de> has quit IRC (Read error: Connection reset by peer)[19:46:56] *** wiedi <wiedi!~wiedi@ip5b41bdb7.dynamic.kabel-deutschland.de> has joined #project-FiFo[19:58:48] *** _ADN_ <_ADN_!~username@5.148.34.186> has quit IRC (Ping timeout: 260 seconds)[21:19:30] *** _ADN_ <_ADN_!~username@host86-173-158-83.range86-173.btcentralplus.com> has joined #project-FiFo[21:40:29] *** abates <abates!~abates@fw1a-wan.eecs.wsu.edu> has joined #project-FiFo[21:41:02] <abates> real talk[21:42:35] <abates> I've run SmartOS Joyent Triton Private Cloud (I think I got that all in there) in a development environment (2 head nodes w/ 128 GB ram, 4 compute nodes each 8 cores & 16 GB RAM)[21:43:10] <abates> I ended up not going that route due to the apparent instability of 'community releases'[21:43:58] <abates> Could someone here explain the difference of Triton / FiFo? Use-Case, stability, et cetera?[21:45:45] *** ipalreadytaken <ipalreadytaken!~ipalready@12.87.13.10> has joined #project-FiFo[21:46:36] *** ipalreadytaken <ipalreadytaken!~ipalready@12.87.13.10> has quit IRC (Client Quit)[21:46:43] *** ipalreadytaken <ipalreadytaken!~ipalready@12.87.13.10> has joined #project-FiFo[21:46:43] *** ChanServ sets mode: +o ipalreadytaken[21:47:38] <ipalreadytaken> hello abates[21:48:17] <abates> hellp[21:48:23] <abates> s/p/o/[21:49:04] <ipalreadytaken> fifo is similar to triton in several regards. it uses smartos as its os, and can deploy zones and kvm[21:49:08] <ipalreadytaken> of course lx too[21:49:50] <ipalreadytaken> we have limited support for docker, but mostly because most of our users are zones only types, so if we got better feed back on docker usage we could quickly implement some cahgnes[21:51:30] <ipalreadytaken> the biggest difference is the architecture. fifo is built as a distributed platform, so if you can multiple nodes and deal with failure of nodes without impacting uptime[21:51:51] <ipalreadytaken> triton uses a (quick) replication approach[21:53:49] <abates> so, in the fifo, could a zone/slice span multiple nodes (since it's distributed)?[21:54:21] <abates> if I remember correctly, triton couldn't handle creating a zone larger than your largest compute node.[21:54:26] <ipalreadytaken> no just fifo is distributed it is your job to distribute the apps you run in zones.[21:55:08] <ipalreadytaken> fifo has the same feature. over provisioning is not supported as it would be cheating your user out of a guaranteed resource[21:58:58] <abates> So, I guess that's here docker swarming style of provisioning resources on multiple nodes would come in place.[22:00:37] <abates> https://circleci.com/blog/its-the-future/[22:02:54] <ipalreadytaken> i dont understand your question[22:07:27] *** io_bora <io_bora!~io_bora@35.128.10.175> has joined #project-FiFo[22:08:28] <abates> Question turned to ramble.. Thanks ipalreadytaken, you've thoroughly answered my question.[22:09:02] <ipalreadytaken> no worries. if you have questions about specific architectures or applications feel free to ask[22:12:04] *** io_bora <io_bora!~io_bora@35.128.10.175> has quit IRC (Remote host closed the connection)[22:12:42] *** io_bora <io_bora!~io_bora@35.128.10.175> has joined #project-FiFo[22:17:10] *** io_bora <io_bora!~io_bora@35.128.10.175> has quit IRC (Ping timeout: 264 seconds)[23:05:51] *** ipalreadytaken <ipalreadytaken!~ipalready@12.87.13.10> has quit IRC (Remote host closed the connection)[23:29:43] *** ipalreadytaken <ipalreadytaken!~ipalready@12.87.13.10> has joined #project-FiFo[23:29:43] *** ChanServ sets mode: +o ipalreadytaken