<div dir="ltr"><div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 25, 2014 at 10:43 AM, James Slagle <span dir="ltr"><<a href="mailto:james.slagle@gmail.com" target="_blank">james.slagle@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="">On Fri, Jul 25, 2014 at 9:59 AM, John Griffith<br>
<<a href="mailto:john.griffith@solidfire.com">john.griffith@solidfire.com</a>> wrote:<br>
<br>
</div><div class="">> The LIO versus Tgt thing however is a bit troubling. Is there a reason that<br>
> TripleO decided to do the exact opposite of what the defaults are in the<br>
> rest of OpenStack here? Also any reason why if there was a valid<br>
> justification for this it didn't seem like it might be worthwhile to work<br>
> with the rest of the OpenStack community and share what they considered to<br>
> be the better solution here?<br>
<br>
</div>Not really following what you find troubling. Cinder allows you to<br>
configure it to use Tgt or LIO. Are you objecting to the fact that<br>
TripleO allows people to *choose* to use LIO?<br></blockquote><div class="gmail_default" style="font-family:'courier new',monospace">Nope, that's fine... what I'm uneasy about is there appears to be a suggestion to have different defaults for things based on distribution. If this turns out to be the only way to make things work, then sure... we do what we have to do.</div>
<div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace">Maybe I'm missing some points in the thread, if it's strictly "do we allow options" then sure, I'm not saying that's a bad thing particularly if those options are the same as we already do in other projects.</div>
<div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace"><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">>> LIO is used on RHEL, because RHEL doesn't offer TGT. So what is "the LIO</span><br style="font-family:arial,sans-serif;font-size:12.727272033691406px">
<span style="font-family:arial,sans-serif;font-size:12.727272033691406px">>> versus Tgt thing?</span><br></div><div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace">
What version of RHEL don't offer tgtadm? It's in 6.5; also I responded to a post on this subject a while back about having consistent defaults whether you're dealing with an over-cloud or an under-cloud; IMO uniqueness between the two in terms of defaults is something that should be carefully weighed. My suggestion was and is, that if for example LIO was the only option, then we should work together to make that a consistent default across the board. Sounds like maybe I misunderstood what was being done here so perhaps it's not an issue. </div>
<div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace"><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">>> "TripleO is a program aimed at installing, upgrading and operating</span><br style="font-family:arial,sans-serif;font-size:12.727272033691406px">
<span style="font-family:arial,sans-serif;font-size:12.727272033691406px">>> OpenStack clouds using OpenStack's own cloud facilities as the foundations</span><br style="font-family:arial,sans-serif;font-size:12.727272033691406px">
<span style="font-family:arial,sans-serif;font-size:12.727272033691406px">>> - building on nova, neutron and heat to automate fleet management at</span><br style="font-family:arial,sans-serif;font-size:12.727272033691406px">
<span style="font-family:arial,sans-serif;font-size:12.727272033691406px">>> datacentre scale (and scaling down to as few as 2 machines)."</span><br style="font-family:arial,sans-serif;font-size:12.727272033691406px">
<br>Sure, but for some crazy reason I had always assumed that there would be some 'value add' here, whether that be efficiency, ease of deployment or whatever. Not just "I can use OpenStack to deploy OpenStack and throw away the large number of tools designed to do this sort of thing and reinvent them because it's neat".</div>
<div class="gmail_default"><font face="courier new, monospace"><br></font></div><div class="gmail_default"><font face="courier new, monospace">I'm not saying that's how I see it, but I am saying maybe the stated purpose could use a bit of detail.</font></div>
<div class="gmail_default"><font face="courier new, monospace"><br></font><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">>> Nobody expects datacenter scale to be easy. We do, however, have a</span><br style="font-family:arial,sans-serif;font-size:12.727272033691406px">
<span style="font-family:arial,sans-serif;font-size:12.727272033691406px">>> reasonable expectation that OpenStack can be used to deploy large,</span><br style="font-family:arial,sans-serif;font-size:12.727272033691406px">
<span style="font-family:arial,sans-serif;font-size:12.727272033691406px">>> complex applications. If it cannot, OpenStack is in trouble.</span><br></div><div class="gmail_default"><span style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br>
</span></div><div class="gmail_default"><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">Sure... but I think by adding (more to the point exposing) as much complexity as possible and reinventing tools OpenStack will be in trouble as well (likely more trouble). </span></div>
<div class="gmail_default"><span style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></span></div><div class="gmail_default"><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">Granted Heat is great for the deployment of applications in an OpenStack Cloud, so you're saying that since TripleO uses Heat it falls into the same category? OpenStack on OpenStack is just another application we're deploying? Then maybe all of this should be folded in to Heat in perhaps a different design, or maybe it already is for the most part. Can't really tell for sure as I've never really been able to do get anything really working with TripleO as of yet, which goes back to my earlier comment about complexity and what the actual goal is.</span></div>
<div class="gmail_default"><span style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></span></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
As was explained in the review[1], Tgt is the default for TripleO. If<br>
you want to use LIO, TripleO offers that choice, just like Cinder<br>
does.<br></blockquote><div><br></div><div class="gmail_default" style="font-family:'courier new',monospace">Cool... you can disregard any comments I made on that subject then.</div><div class="gmail_default" style="font-family:'courier new',monospace">
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
[1] <a href="https://review.openstack.org/#/c/78463/" target="_blank">https://review.openstack.org/#/c/78463/</a><br>
<div class="im"><br>
<br>
--<br>
-- James Slagle<br>
--<br>
<br>
</div><div class=""><div class="h5">_______________________________________________<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>
</div></div></blockquote></div><br></div></div>