Greetings, Mistral team!
As you may be aware, I've been working with other folks in the community
on documenting a vision for OpenStack clouds (formerly known as the
'Technical Vision') - essentially to interpret the mission statement in
long-form, in a way that we can use to actually help guide decisions.
You can read the latest draft here: https://review.openstack.org/592205
We're trying to get feedback from as many people as possible - in many
ways the value is in the process of coming together to figure out what
we're trying to achieve as a community with OpenStack and how we can
work together to build it. The document is there to help us remember
what we decided so we don't have to do it all again over and over.
The vision is structured with two sections that apply broadly to every
project in OpenStack - describing the principles that we believe are
essential to every cloud, and the ones that make OpenStack different
from some other clouds. The third section is a list of design goals that
we want OpenStack as a whole to be able to meet - ideally each project
would be contributing toward one or more of these design goals.
I see Mistral contributing to two of the design goals. First, it helps
with Customisable Integration by enabling application developers to
incorporate glue logic between cloud services or between the application
and cloud services, and host it in the cloud without the need to
pre-allocate a VM for it. Secondly, it also contributes to the Built-in
Reliability and Durability goal by providing applications with a
highly-reliable way of maintaining workflow state without the need for
the application itself to do it.
The sections on Bidirectional Compatibility and Interoperability will
probably be relevant to design decisions in Mistral, since workbooks are
one of the artifact types that I'd expect to help with interoperability
across clouds. The Cross-Project Dependencies section may also be of
special interest to review, since Mistral is a service that many other
OpenStack services could potentially rely on.
If you would like me or another TC member to join one of your team IRC
meetings to discuss further what the vision means for your team, please
reply to this thread to set it up. You are also welcome to bring up any
questions in the TC IRC channel, #openstack-tc - there's more of us
around during Office Hours
(https://governance.openstack.org/tc/#office-hours), but you can talk to
us at any time.
Feedback can also happen either in this thread or on the review
https://review.openstack.org/592205
If the team is generally happy with the vision as it is and doesn't have
any specific feedback, that's cool but I'd like to request that at least
the PTL leave a vote on the review. It's important to know whether we
are actually developing a consensus in the community or just talking to
ourselves :)
many thanks,
Zane.
__________________________________________________________________________
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
