[openstack-dev] [TripleO] Summit session wrapup

Jordan OMara jomara at redhat.com
Mon Dec 2 19:17:29 UTC 2013

On 01/12/13 00:27 -0500, Tzu-Mainn Chen wrote:
>I think we may all be approaching the planning of this project in the wrong way, because of confusions such as: 
>> Well, I think there is one small misunderstanding. I've never said that
>> manual way should be primary workflow for us. I agree that we should lean
>> toward as much automation and smartness as possible. But in the same time, I
>> am adding that we need manual fallback for user to change that smart
>> decision.
>> Primary way would be to let TripleO decide, where the stuff go. I think we
>> agree here.
>That's a pretty fundamental requirement that both sides seem to agree upon - but that agreement got lost in the discussions of what feature should come in which release, etc. That seems backwards to me. 
>I think it's far more important that we list out requirements and create a design document that people agree upon first. Otherwise, we run the risk of focusing on feature X for release 1 without ensuring that our architecture supports feature Y for release 2. 
>To make this example more specific: it seems clear that everyone agrees that the current Tuskar design (where nodes must be assigned to racks, which are then used as the primary means of manipulation) is not quite correct. Instead, we'd like to introduce a philosophy where we assume that users don't want to deal with homogeneous nodes individually, instead letting TripleO make decisions for them. 

I agree; getting buy-in on a design document up front is going to
save us future anguish

>Regarding this - I think we may want to clarify what the purpose of our releases are at the moment. Personally, I don't think our current planning is about several individual product releases that we expect to be production-ready and usable by the world; I think it's about milestone releases which build towards a more complete product. 
>From that perspective, if I were a prospective user, I would be less concerned with each release containing exactly what I need. Instead, what I would want most out of the project is: 
>a) frequent stable releases (so I can be comfortable with the pace of development and the quality of code) 
>b) design documentation and wireframes (so I can be comfortable that the architecture will support features I need) 
>c) a roadmap (so I have an idea when my requirements will be met) 

Jordan O'Mara <jomara at redhat.com>
Red Hat Engineering, Raleigh 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131202/cea534e7/attachment.pgp>

More information about the OpenStack-dev mailing list