Open Stack

On 09/19/2013 04:00 PM, Adam Young wrote:
> On 09/19/2013 05:19 AM, Imre Farkas wrote:
>> On 09/19/2013 10:08 AM, Tomas Sedovic wrote:
>>> Hi everyone,
>>>
>>> Some of us Tuskar developers have had the chance to meet the TripleO
>>> developers face to face and discuss the visions and goals of our
>>> projects.
>>>
>>> Tuskar's ultimate goal is to have to a full OpenStack management
>>> solution: letting the cloud operators try OpenStack, install it, keep it
>>> running throughout the entire lifecycle (including bringing in new
>>> hardware, burning it in, decommissioning), help to scale it, secure the
>>> setup, monitor for failures, project the need for growth and so on.
>>>
>>> And to provide a good user interface and API to let the operators
>>> control and script this easily.
>>>
>>> Now, the scope of the OpenStack Deployment program (TripleO) includes
>>> not just installation, but the entire lifecycle management (from racking
>>> it up to decommissioning). Among other things they're thinking of are
>>> issue tracker integration and inventory management, but these could
>>> potentially be split into a separate program.
>>>
>>> That means we do have a lot of goals in common and we've just been going
>>> at them from different angles: TripleO building the fundamental
>>> infrastructure while Tuskar focusing more on the end user experience.
>>>
>>> We've come to a conclusion that it would be a great opportunity for both
>>> teams to join forces and build this thing together.
>>>
>>> The benefits for Tuskar would be huge:
>>>
>>> * being a part of an incubated project
>>> * more eyballs (see Linus' Law (the ESR one))
>>> * better information flow between the current Tuskar and TripleO teams
>>> * better chance at attracting early users and feedback
>>> * chance to integrate earlier into an OpenStack release (we could make
>>> it into the *I* one)
>>>
>>> TripleO would get a UI and more developers trying it out and helping
>>> with setup and integration.
>>>
>>> This shouldn't even need to derail us much from the rough roadmap we
>>> planned to follow in the upcoming months:
>>>
>>> 1. get things stable and robust enough to demo in Hong Kong on real
>>> hardware
>>> 2. include metrics and monitoring
>>> 3. security
>>>
>>> What do you think?
>>
>> That is an excellent idea!
>>
>> Does it mean from the practical point of view that the Tuskar code
>> will be merged into the TripleO repos and the project will be deleted
>> from StackForge and Launchpad?
>
> I would recommend against that, and instead have the unified team merge,
> but maintain both repos.  Think of how Keystone manages both
> python-keystoneclient and keystone server.
>
> And let me be the first to suggest that the unified team be called
> Tuskarooo!

My understanding is: we'd mostly keep our repos (tuskar, tukar-ui, 
python-tuskarclient) for now but probably move them from stackforge to 
openstack (since that's where all the TripleO repos live).

The Tuskar code would probably be integrated a bit later than the 
current TripleO stuff (API in I) and we'll need to meet some integration 
requirements, but I believe that eventually tuskar-ui would merge with 
Horizon just like all the other UIs do. (provided that ends up making sense)

There is some code we currently have in Tuskar that will make more sense 
to move to another project or whatever but that's details.

And yeah, Tuskarooo's great but I wouldn't say no to Tripletusk 
(Triceratops!) or say Gablerstaplerfahrer.

>
>>
>> Imre
>>
>>>
>>> Tomas
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>