*** toddjohn has joined #openstack-app-catalog | 00:56 | |
*** toddjohn has quit IRC | 01:01 | |
*** toddjohn has joined #openstack-app-catalog | 01:16 | |
*** toddjohn has quit IRC | 01:18 | |
*** toddjohn has joined #openstack-app-catalog | 01:18 | |
*** toddjohn has quit IRC | 01:23 | |
*** rmoe_ has quit IRC | 02:14 | |
*** kzaitsev_mb has quit IRC | 02:14 | |
*** rmoe has joined #openstack-app-catalog | 02:14 | |
docaedo | blueprint regarding Mistral work as promised: https://blueprints.launchpad.net/app-catalog/+spec/add-mistral-assets | 03:07 |
---|---|---|
*** kzaitsev_mb has joined #openstack-app-catalog | 03:40 | |
*** kzaitsev_mb has quit IRC | 03:46 | |
*** kzaitsev_mb has joined #openstack-app-catalog | 04:43 | |
*** kzaitsev_mb has quit IRC | 05:36 | |
*** kebray has quit IRC | 05:49 | |
*** kebray has joined #openstack-app-catalog | 05:50 | |
*** kzaitsev_mb has joined #openstack-app-catalog | 06:32 | |
*** kzaitsev_mb has quit IRC | 06:37 | |
*** kebray has quit IRC | 07:25 | |
*** kzaitsev_mb has joined #openstack-app-catalog | 07:33 | |
*** kzaitsev_mb has quit IRC | 07:38 | |
*** kzaitsev_mb has joined #openstack-app-catalog | 08:34 | |
*** kzaitsev_mb has quit IRC | 08:38 | |
*** kzaitsev_mb has joined #openstack-app-catalog | 09:35 | |
*** kzaitsev_mb has quit IRC | 09:43 | |
*** kzaitsev_mb has joined #openstack-app-catalog | 11:29 | |
*** openstackgerrit has quit IRC | 12:50 | |
*** openstackgerrit has joined #openstack-app-catalog | 12:51 | |
*** toddjohn has joined #openstack-app-catalog | 13:31 | |
*** kebray has joined #openstack-app-catalog | 15:28 | |
openstackgerrit | Kevin Fox proposed openstack/app-catalog: Derive asset last modified date/time from git logs https://review.openstack.org/267087 | 17:11 |
*** dmowrer has joined #openstack-app-catalog | 18:03 | |
*** kzaitsev_mb has quit IRC | 18:12 | |
*** dmowrer_ has joined #openstack-app-catalog | 18:13 | |
kfox1111 | docaedo: btw, https://review.openstack.org/266072 | 18:55 |
docaedo | kfox1111: yep thanks, been reviewing and am happy to see this coming together | 18:56 |
kfox1111 | cool. yeah. I'm really hoping that will get openstack as a whole integrating with each other better. | 18:57 |
kfox1111 | there are soo many rough edges at that level. :/ | 18:57 |
docaedo | yeah I think a LOT about how disconnected OpenStack is. Made sense from the development perspective, but it's our biggest weakness | 19:04 |
docaedo | so many things that should just work together DON'T because different dev teams can do what they want, and everything is just loosely coupled | 19:05 |
kfox1111 | yeah. its kind of a good idea from a scalability standpoint, but it requires good cross team communication and understanding, and at least at the moment the projects are very strongly silo'ed. :/ | 19:05 |
kfox1111 | yeah. but the biggest problem is each team expecting the other to do all the work. | 19:05 |
kfox1111 | they agree something should be done, but can't on how. :/ | 19:06 |
kfox1111 | I | 19:06 |
docaedo | yes - like the problem of cleaning up resources after a tenant delete :) 8 summits I've been in conversations about who is responsible, and NOBODY wants to own it | 19:06 |
kfox1111 | I'm really surprised nova+cinder and nova+neutron work at all under these conditions. | 19:06 |
docaedo | haha yeah no kidding | 19:06 |
kfox1111 | yup. a very hard problem. :/ | 19:06 |
docaedo | one of the mistral workflows they are working on is to clean up after a deleted tenant - and it seems like the best idea I've heard yet since no one project feels like they should "own" that task | 19:07 |
kfox1111 | hmm... yeah. mistral would be a pretty good place to handle parts of it... | 19:08 |
kfox1111 | it has clients to all the rest. | 19:08 |
kfox1111 | there's been very interesting conversation on the tripleo team reguarding tripleo-api vs just using mistral | 19:08 |
docaedo | yeah I have followed that closely too, it's an interesting thread | 19:09 |
docaedo | For the most part, using mistral there does make sense | 19:09 |
kfox1111 | I think it will delay tripleo further, probably.... but it follows the great idea of making the underlying technologies of openstack work for useful use cases. | 19:09 |
kfox1111 | so I think it would be a great long term thing. | 19:09 |
kfox1111 | heat is way better these days because the heat team actually listens to the tripleo team. | 19:10 |
docaedo | I still see tripleO as a nice academic exercise without any real long term benefit - every operator I talk to even at moderate scale would rather use a smaller well-defined tool-set to deploy their cloud | 19:11 |
kfox1111 | with my op hat on, I'd love to use tripleo once stable. | 19:12 |
kfox1111 | its too opinionated at the moment, and without an upgrade path, unusable. | 19:12 |
kfox1111 | but tripleo admits those are issues, and are working on them. | 19:12 |
docaedo | indeed | 19:12 |
kfox1111 | with redhat actually starting to ship products based on it though, there's a good chance those will get resolved quickly. | 19:13 |
docaedo | quite possible | 19:16 |
*** kebray has quit IRC | 19:43 | |
*** toddjohn_ has joined #openstack-app-catalog | 23:06 | |
*** toddjohn has quit IRC | 23:09 | |
*** rmoe_ has joined #openstack-app-catalog | 23:52 | |
*** rmoe has quit IRC | 23:52 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!