<div dir="ltr">For project meta-info like this, seems like a wiki page is a good location. Thanks for sending. <div><br></div><div>Anne</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Sep 18, 2013 at 3:59 AM, <a href="mailto:marios@redhat.com">marios@redhat.com</a> <span dir="ltr"><<a href="mailto:mandreou@redhat.com" target="_blank">mandreou@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I have an AI from the tuskar community meeting to come up with a<br>
description of how TripleO 'differs from' Tuskar. I have no idea where<br>
this will be used/placed and in fact I don't know where to send it:<br>
should we paste it into the naming etherpad, open a launchpad docs<br>
blueprint (seems a bit much, especially as I don't know which doc it's<br>
going into). Alternatively please feel free to change and use as you see<br>
fit wherever:<br>
<br>
<br>
"<br>
<br>
How does tuskar fit in with TripleO?<br>
<br>
<br>
TripleO [1] is a blanket term for a number of subprojects - but the<br>
basic jist of it is you start with a controller 'undercloud' machine,<br>
meaning it is an OpenStack setup where the nova-compute service is using<br>
the baremetal driver rather than any other hypervisor specific driver.<br>
The TripleO concept is to use this baremetal nova-compute service,<br>
together with HEAT (also on this 'undercloud' machine/available to it)<br>
and diskimage-builder/TOCI to deploy OpenStack, with OpenStack. In other<br>
words, with Triple-O you can use the OpenStack API itself to instuct<br>
your undercloud nova-compute service to deploy entire OpenStack<br>
service(s) (compute service, block storage etc) which become your<br>
end-user "overcloud(s)" ( ;) ). This is frickin' awesome.<br>
<br>
<br>
Tuskar [2] is actually a perfect fit for TripleO and entirely depends on<br>
the TripleO concept and services to do all of the heavy lifting.<br>
Actually, Tuskar may in part be defined as a *design* tool. With Tuskar,<br>
you get a UI and API with which you can tell the undercloud<br>
nova-baremetal service exactly which OpenStack services (i.e. baremetal<br>
images) to deploy onto which machines in the datacenter. The UI<br>
integrates into the default OpenStack Horizon dashboard and allows you<br>
to define your datacenter in terms of Racks (groups of physical machines<br>
registered by id/mac_address) and ResourceClasses (groups of Racks that<br>
all provide the same Overcloud service 'compute' vs 'block_storage').<br>
<br>
<br>
In the simplest terms, Tuskar translates your definition into the<br>
undercloud machine HEAT template, allowing you to then provision your<br>
datacenter at the push of a button. Beyond this planning/design, Tuskar<br>
also monitors the datacenter, allowing operators to make most efficient<br>
use of capacity. Ultimately, Tuskar aims to allow you to plan, define,<br>
deploy and monitor your datacenter in an accessible, scalable,<br>
repeatable, highly available and secure way.<br>
"<br>
<br>
<br>
<br>
thanks, marios<br>
<br>
<br>
[1]<br>
<a href="http://www.openstack.org/summit/portland-2013/session-videos/presentation/openstack-on-openstack-overview" target="_blank">http://www.openstack.org/summit/portland-2013/session-videos/presentation/openstack-on-openstack-overview</a><br>
[2] <a href="https://www.youtube.com/watch?feature=player_embedded&v=VEY035-Lyzo" target="_blank">https://www.youtube.com/watch?feature=player_embedded&v=VEY035-Lyzo</a><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Anne Gentle<br><a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>
</div>