<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I'm going to agree on that strategy.<br>
<br>
---- Nick<br>
<br>
<div class="moz-cite-prefix">On 3/12/2015 7:33 PM, Matt Kassawara
wrote:<br>
</div>
<blockquote
cite="mid:CABA+jQrYYG+8+DQ_Kck6SrqUQk64T_YFi84=JK41M0xWT4QcqQ@mail.gmail.com"
type="cite">
<div dir="ltr">Ceph definitely has a following, but I don't recall
specific conversation around redundant storage. Similar to
physical network redundancy, I wonder if we should simply
mention storage redundancy options rather than attempt to
support a particular variant... especially if all of them lean
toward a vendor.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Mar 12, 2015 at 4:58 PM, Meg
McRoberts <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:dreidellhasa@yahoo.com" target="_blank">dreidellhasa@yahoo.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div
style="color:#000;background-color:#fff;font-family:HelveticaNeue,Helvetica
Neue,Helvetica,Arial,Lucida
Grande,sans-serif;font-size:12px">
<div>Thanks, Matt -- this is very helpful.</div>
<div><br>
</div>
<div dir="ltr">What about storage? It seems like Ceph
as the storage back-end provides much better data
protection</div>
<div dir="ltr">than the alternatives. Did you sense a
movement towards adapting Ceph or are people clinging
to LVM,</div>
<div dir="ltr">etc? <br>
</div>
<div><span></span></div>
<br>
<blockquote style="border-left:2px solid
rgb(16,16,255);margin-left:5px;margin-top:5px;padding-left:5px">
<div style="font-family:HelveticaNeue,Helvetica
Neue,Helvetica,Arial,Lucida
Grande,sans-serif;font-size:12px">
<div style="font-family:HelveticaNeue,Helvetica
Neue,Helvetica,Arial,Lucida
Grande,sans-serif;font-size:16px">
<div dir="ltr">
<hr size="1"> <font face="Arial"> <b><span
style="font-weight:bold">From:</span></b>
Matt Kassawara <<a moz-do-not-send="true"
href="mailto:mkassawara@gmail.com"
target="_blank">mkassawara@gmail.com</a>><br>
<b><span style="font-weight:bold">To:</span></b>
"<a moz-do-not-send="true"
href="mailto:openstack-docs@lists.openstack.org"
target="_blank">openstack-docs@lists.openstack.org</a>"
<<a moz-do-not-send="true"
href="mailto:openstack-docs@lists.openstack.org"
target="_blank">openstack-docs@lists.openstack.org</a>>
<br>
<b><span style="font-weight:bold">Sent:</span></b>
Thursday, March 12, 2015 1:44 PM<br>
<b><span style="font-weight:bold">Subject:</span></b>
[OpenStack-docs] [ha-guide] Observations from
mid-cycle ops meetup<br>
</font> </div>
<div><span class=""><br>
<div>
<div dir="ltr">I went to the mid-cycle ops
meeting for a better idea of the HA
methods implemented by operators. Most
seem to agree on Galera with
MariaDB/MySQL, RabbitMQ
active-passive/active-active (some using a
load balancer and others configuring
services to use each node directly),
Memcached active/active (via Oslo hash
synchronization), and OpenStack APIs via
hardware or HAProxy load balancer. On the
other hand, networking drifted all over
the place. Some people live and die by
nova-net and won't move to neutron until
it 100% mirrors the multi-host
functionality with fixed/floating IP
addresses, others use neutron but only
with provider networks, most don't quite
trust DVR/L3HA yet, and a few implement
custom code with nova-net or neutron. For
networking in the HA guide, I mostly
suggest referencing the networking guide
scenarios rather than suggesting a
particular architecture. However, we
should also mention them in the
introduction somewhere because different
architectures may impact the minimum
number and type of nodes.</div>
</div>
<br>
</span>_______________________________________________<br>
OpenStack-docs mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-docs@lists.openstack.org"
target="_blank">OpenStack-docs@lists.openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
<br>
<br>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-docs mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a>
</pre>
</blockquote>
<br>
</body>
</html>