On 04/13/2016 11:16 AM, Thierry Carrez wrote: > Fox, Kevin M wrote: >> I think my head just exploded. :) >> >> That idea's similar to neutron sfc stuff, where you just say what >> needs to connect to what, and it figures out the plumbing. >> >> Ideally, it would map somehow to heat & docker COE & neutron sfc to >> produce a final set of deployment scripts and then just runs it >> through the meat grinder. :) >> >> It would be awesome to use. It may be very difficult to implement. >> >> If you ignore the non container use case, I think it might be fairly >> easily mappable to all three COE's though. > > This feels like Heat with a more readable descriptive language. I > don't really like this approach, because you end up with the lowest > common denominator between COE's functionality. They are all > different. And they are at the peak of the differentiation phase.
Are we able to define that lowest common denominator at this stage? Maybe that subset of features is still valuable? __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
