In Kolla, during this PTG, we came up with idea of scenario based testing+documentation. Basically what we want to do is to provide set of kolla configurations, howtos and tempest configs to test out different "constellations" or use-cases. If, instead of in Kolla, do these in cross-community manner (and just host kolla-specific things in kolla), I think that would partially address what you're asking for here.
On 26 September 2017 at 13:01, Jonathan Proulx <j...@csail.mit.edu> wrote: > On Tue, Sep 26, 2017 at 12:16:30PM -0700, Clint Byrum wrote: > > :OpenStack is big. Big enough that a user will likely be fine with learning > :a new set of tools to manage it. > > New users in the startup sense of new, probably. > > People with entrenched environments, I doubt it. > > But OpenStack is big. Big enough I think all the major config systems > are fairly well represented, so whether I'm right or wrong this > doesn't seem like an issue to me :) > > Having common targets (constellations, reference architectures, > whatever) so all the config systems build the same things (or a subset > or superset of the same things) seems like it would have benefits all > around. > > -Jon > > __________________________________________________________________________ > 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 __________________________________________________________________________ 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
