<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#333333">
<br>
<div class="moz-cite-prefix">On 2013/19/09 04:08, Tomas Sedovic
wrote:<br>
</div>
<blockquote cite="mid:523AB0FC.6070901@redhat.com" type="cite">Hi
everyone,
<br>
<br>
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.
<br>
<br>
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.
<br>
<br>
And to provide a good user interface and API to let the operators
control and script this easily.
<br>
<br>
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.
<br>
<br>
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.
<br>
<br>
We've come to a conclusion that it would be a great opportunity
for both teams to join forces and build this thing together.
<br>
<br>
The benefits for Tuskar would be huge:
<br>
<br>
* being a part of an incubated project
<br>
* more eyballs (see Linus' Law (the ESR one))
<br>
* better information flow between the current Tuskar and TripleO
teams
<br>
* better chance at attracting early users and feedback
<br>
* chance to integrate earlier into an OpenStack release (we could
make it into the *I* one)
<br>
<br>
TripleO would get a UI and more developers trying it out and
helping with setup and integration.
<br>
<br>
This shouldn't even need to derail us much from the rough roadmap
we planned to follow in the upcoming months:
<br>
<br>
1. get things stable and robust enough to demo in Hong Kong on
real hardware
<br>
2. include metrics and monitoring
<br>
3. security
<br>
<br>
What do you think?
<br>
</blockquote>
Sounds like a good idea to me.<br>
<br>
-- Jarda<br>
<blockquote cite="mid:523AB0FC.6070901@redhat.com" type="cite">
<br>
Tomas
<br>
<br>
_______________________________________________
<br>
OpenStack-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
<br>
</blockquote>
<br>
</body>
</html>