On 07/20/2018 02:06 PM, Emilien Macchi wrote:
On Fri, Jul 20, 2018 at 2:55 PM Ben Nemec <openst...@nemebean.com
<mailto:openst...@nemebean.com>> wrote:
Okay, based on a private conversation this is coming off as way more
troll-ish than I intended. I don't understand where this work is
going,
but I don't really need to so I'll step back from the discussion.
Apologies for any offense.
No offense here, Ben. In fact I hope we can still continue to have a
productive discussion here.
I'm speaking on my own view now, and I'm happy to be wrong and learn but
I wanted to explore how far we can bring the work around standalone
architecture. If it was worth exploring making it "multi-node" somehow,
what would be our technical challenges and more than anything else: what
use-case we would enable.
I'm actually quite happy to see that people already looked at some of
these challenges before (see what Giulio / James / Steve H. already
worked on), so I guess it makes sense to continue the investigation.
We are not making any decision right now in what API we plan to use. The
current production architecture is still undercloud + overcloud, and our
day 2 operations are done by Mistral/Heat for now but as we transition
more to Ansible I think we wanted to explore more options.
I hope this little background helped.
Yeah, I realize now that I invented some requirements that you didn't
actually state in your original email. Slap on the wrist to me for poor
reading comprehension. :-)
__________________________________________________________________________
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
