| *** tosky has quit IRC | 00:02 | |
| *** edmondsw has joined #openstack-tc | 00:38 | |
| *** edmondsw has quit IRC | 00:42 | |
| *** zaneb has joined #openstack-tc | 01:15 | |
| zaneb | it was highly inconvenient that a power cut occurred right in the middle of that conversation :( | 01:15 |
|---|---|---|
| *** diablo_rojo has quit IRC | 01:22 | |
| *** edmondsw has joined #openstack-tc | 02:26 | |
| *** edmondsw has quit IRC | 02:30 | |
| scas | 'openstack' and 'nova' are often synonymous, because most use cases are going to call for nova in some form. when i started working with openstack-the-product as but a consumer/deployer in folsom days, nova was just kind of expected, and largely what attracted my fleet of saved-from-ewaste servers | 03:55 |
| scas | one could argue that openstack-the-product has changed in its mission, but nova is still pretty much along for the ride | 03:55 |
| scas | i'd argue that most people don't think about the different subprojects when they want 'openstack'. they want some guide that doesn't take them through byzantine rabbit holes. that's where installers come in, but they're openstack-but-not-quite-openstack so we're in this grey area where the deployment is left to those with $$$$ or have the stomach for hacking out something from the open source bits | 04:01 |
| scas | the tire swing analogy is pretty apt here | 04:02 |
| scas | regardless of who is downstream making money from repackaging, the users shouldn't have to go to a VAR to get the tire swing xl double deluxe supreme edition | 04:05 |
| *** edmondsw has joined #openstack-tc | 04:14 | |
| *** edmondsw has quit IRC | 04:18 | |
| *** e0ne has joined #openstack-tc | 09:39 | |
| *** e0ne has quit IRC | 09:58 | |
| *** e0ne_ has joined #openstack-tc | 09:58 | |
| *** e0ne_ has quit IRC | 10:09 | |
| *** jaypipes has quit IRC | 10:59 | |
| *** e0ne has joined #openstack-tc | 11:38 | |
| *** e0ne has quit IRC | 11:56 | |
| *** tosky has joined #openstack-tc | 12:29 | |
| *** e0ne has joined #openstack-tc | 12:29 | |
| *** e0ne has quit IRC | 12:33 | |
| *** e0ne has joined #openstack-tc | 12:39 | |
| *** e0ne has quit IRC | 12:40 | |
| fungi | well, i think part of it is that there quite a few scenarios where you can have a functional combination of some subset of openstack services which doesn't include nova (originally stand-alone swift but now the likes of keystone, ironic, cinder and neutron too, maybe more, have stand-alone-ish deployment options) | 13:13 |
| fungi | but conveying that as a concept while calling any and all combinations "openstack" is a challenge to explain | 13:15 |
| *** dklyle has joined #openstack-tc | 13:17 | |
| *** e0ne has joined #openstack-tc | 13:18 | |
| fungi | it's enough of a challenge to explain what openstack is when you consider it all one bundle | 13:31 |
| fungi | much less when deconstructed and reassembled in a variety of partial combinations | 13:32 |
| *** e0ne has quit IRC | 13:35 | |
| *** e0ne has joined #openstack-tc | 13:41 | |
| *** e0ne has quit IRC | 13:45 | |
| fungi | constellations, i guess | 14:10 |
| *** ricolin has joined #openstack-tc | 15:07 | |
| *** tosky has quit IRC | 15:50 | |
| *** edmondsw has joined #openstack-tc | 16:51 | |
| *** edmondsw has quit IRC | 16:56 | |
| *** ricolin has quit IRC | 17:22 | |
| *** tosky has joined #openstack-tc | 17:56 | |
| *** edmondsw has joined #openstack-tc | 18:39 | |
| *** edmondsw has quit IRC | 18:44 | |
| *** e0ne has joined #openstack-tc | 19:57 | |
| *** e0ne has quit IRC | 20:13 | |
| *** e0ne has joined #openstack-tc | 20:21 | |
| *** edmondsw has joined #openstack-tc | 20:27 | |
| *** edmondsw has quit IRC | 20:32 | |
| *** e0ne has quit IRC | 20:56 | |
| *** edmondsw has joined #openstack-tc | 22:15 | |
| *** edmondsw has quit IRC | 22:20 | |
| *** diablo_rojo has joined #openstack-tc | 23:07 | |
| *** dklyle has quit IRC | 23:17 | |
| *** tosky has quit IRC | 23:20 | |
| *** diablo_rojo has quit IRC | 23:26 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!