<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Randy,</p>
<p><br>
</p>
<p>Yes, we're using Beezim's zimbra-ceph connector. I suggest you
contact them directly to get more information about their
connector.<br>
</p>
<p><br>
</p>
<p>Regards,</p>
<p><br>
</p>
<p>Frédéric.<br>
</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">Le 29/01/2018 à 19:09, Randy Leiker a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:2140143102.608.1517249368872.JavaMail.%22Randy%20Leiker%22@RandysPC">
<style type="text/css">p { margin: 0; }</style>
<div style="font-family: arial,helvetica,sans-serif; font-size:
10pt; color: #000000">
<div>Hi Frederic,</div>
<div><br>
</div>
<div>Thanks for your suggestions. I've begun looking into
incorporating Ceph into the Zimbra mailbox HA project. I
think this approach makes a lot of sense as it makes the
message blobs & indexes for each end user mailbox highly
available, in addition to avoiding the problem of needing to
reliably move large quantities of mailbox data from one Zimbra
mailbox node to another in a short period of time. Did you by
chance work with BeeZim on this implementation?</div>
<br>
<br>
<div><span name="x"></span>
<div>
<div>
<div><span style="color: rgb(255, 102, 0); font-weight:
bold;"><br>
Randy Leiker (</span><span style="font-weight: bold;">
<span style="color: rgb(51, 51, 255);
background-color: rgb(255, 255, 255);"><a class="moz-txt-link-abbreviated" href="mailto:randy@skywaynetworks.com">randy@skywaynetworks.com</a></span>
<span style="color: rgb(255, 102, 0);">)</span></span><br>
<span style="color: rgb(0, 0, 153);">Skyway Networks,
LLC</span><br>
<span style="color: rgb(0, 0, 153);">1.800.538.5334</span>
<span style="color: rgb(255, 102, 0);">/</span> <span
style="color: rgb(0, 0, 153);">913.663.3900 Ext. 100</span><br>
<span style="color: rgb(0, 0, 153);"></span><a
href="http://www.skywaynetworks.com"
moz-do-not-send="true">https://www.skywaynetworks.com</a><br>
</div>
</div>
</div>
<span name="x"></span><br>
</div>
<hr id="zwchr">
<div
style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From:
</b>"Frédéric Nass" <a class="moz-txt-link-rfc2396E" href="mailto:frederic.nass@univ-lorraine.fr"><frederic.nass@univ-lorraine.fr></a><br>
<b>To: </b>"Jonathan Labbé" <a class="moz-txt-link-rfc2396E" href="mailto:jlabbe@neonova.net"><jlabbe@neonova.net></a>,
"Randy Leiker" <a class="moz-txt-link-rfc2396E" href="mailto:randy@skywaynetworks.com"><randy@skywaynetworks.com></a><br>
<b>Cc: </b><a class="moz-txt-link-abbreviated" href="mailto:users@lists.zetalliance.org">users@lists.zetalliance.org</a><br>
<b>Sent: </b>Friday, January 19, 2018 10:52:32 AM<br>
<b>Subject: </b>Re: [Users] Zimbra mailbox project<br>
<br>
<p>Hi,</p>
<p>Moving from SAN storage to Ceph object storage
(zimbra_class_store) really helped us to keep our Zimbra's
infrastructure up all time.<br>
</p>
<p>We're now able to empty a store from all its 1500+
mailboxes in about half an hour, only moving mysql metadatas
as all stores can access all blobs from the object storage
(zimbraMailboxMoveSkipBlobs: TRUE,
zimbraMailboxMoveSkipHsmBlobs: TRUE). This allows us to
patch or upgrade a zimbra store with no downtime.</p>
<p><span id="result_box" class="" lang="en"><span class="">Future
"always-on" mode will probably only come true when all
stores will share unique, yet highly available, storage
and metadata services.</span></span></p>
<p>Frederic.<br>
</p>
<div class="moz-cite-prefix">Le 17/01/2018 à 17:31, Jonathan
Labbé a écrit :<br>
</div>
<blockquote
cite="mid:CA+ymp7+BCQvn31NnWz0Ueu8W8bgNYtrAFoah8ePQ5ewa3ux-rQ@mail.gmail.com">
<div dir="ltr">Wish, I did not have to leave in the middle
of the meeting. So we take huge advantage of this
already. We are currently running 4x LDAP (2 MMR servers
and 2 Replica only servers), 8 x MTAs, 8x Proxies, and
~50x Mailbox stores, spread across two virtual data
centers. We have F5's in the mix to help with proper load
balancing and handling our SSL termination, and our own
mailproxy system in front of Zimbra handling our client
authentication.
<div><br>
</div>
<div>We have been looking at ways to try and maintain
balanced numbers on our mailbox stores, with size of
mailbox, imap usage (which hopefully the new IMAP
servers will be good), etc. The feasibility of just
evacuating a mail store for us, as you put it, just
doesn't seem feasible. For example, we have a good
chunk of our mail stores with 16TB of mail on them.
That's a lot to just suddenly move, especially if you're
trying to ensure as little or no loss of mail while this
happens.
<div><br>
</div>
<div>A few questions I have;</div>
<div><br>
</div>
<div>How are you evacuating mailboxes off of a "bad"
mailstore? How does that user data and their mail get
transferred to the other mail stores? I am not aware
of any zmmailbox command that just does this, except
for zmboxmove, this can be a slow process.</div>
<div>Have you ran a dockerized mailbox store before?
How does it perform? How many users were you able to
run concurrently on this mail store? </div>
<div>Is this process also taking advantage of Zimbra's
backup processes to ensure fast mailstore recovery?<br>
<div><br>
</div>
<div> <br>
<div class="gmail_extra"><br clear="all">
<div>
<div
class="m_5597709289716434337gmail_signature"><br>
<table
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);width:389.6px"
width="100%" cellspacing="0" cellpadding="0"
border="0">
<tbody>
<tr>
<td
style="font-family:arial,sans-serif;margin:0px">
<table style="max-width:100%"
width="100%" cellspacing="0"
cellpadding="0" border="0">
<tbody>
<tr>
<td
style="font-family:arial,sans-serif;margin:0px;vertical-align:top;padding-right:15px;padding-top:5px;max-width:75px"
rowspan="3" valign="top"><img
style="vertical-align:initial;border-radius:4px;max-width:75px"
alt="photo"
src="http://neonova.net/wp-content/uploads/2016/12/N_Logo_NeoNova.png"
moz-do-not-send="true"
width="50" height="37"></td>
<td
style="font-family:arial,sans-serif;margin:0px;vertical-align:top"
valign="top">
<table cellspacing="0"
cellpadding="0" border="0">
<tbody>
<tr>
<td
style="font-family:arial,sans-serif;margin:0px;padding-bottom:5px">
<table
style="line-height:1.6;font-family:Verdana,Arial,sans-serif;font-size:11px;color:rgb(78,75,76);padding-left:2px;width:322.8px"
width="100%"
cellspacing="0"
cellpadding="0"
border="0">
<tbody>
<tr>
<td
style="font-family:arial,sans-serif;margin:0px"><span
style="margin:0px;padding:0px;color:rgb(23,80,131);font-size:15px">Jonathan
Labbé</span><br>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td
style="font-family:arial,sans-serif;margin:0px;padding:5px
0px 8px;border-top:1px
solid gray">
<table
style="line-height:1.6;font-family:Verdana,Arial,sans-serif;font-size:11px;color:rgb(78,75,76);padding-left:2px;width:325px"
width="100%"
cellspacing="0"
cellpadding="0"
border="0">
<tbody>
<tr>
<td
style="font-family:arial,sans-serif;margin:0px;line-height:18px"><span
style="display:inline-block;white-space:nowrap;color:rgb(78,75,76);text-decoration:none">
<a
href="tel:%28919%29%20460-3330"
target="_blank" moz-do-not-send="true">919-460-3330</a> • <a
href="http://jlabbe@neonova.net"
style="color:rgb(78,75,76);text-decoration:none" target="_blank"
moz-do-not-send="true"><font
color="red"><b>MailScanner
has detected a
possible fraud
attempt from
"jlabbe@neonova.net"
claiming to be</b></font>
jlabbe@neonova.net</a></span><br>
<span
style="display:inline-block;white-space:nowrap"><a
style="color:rgb(78,75,76);text-decoration:none"
href="https://neonova.net"
target="_blank" moz-do-not-send="true">www.neonova.net</a></span> <a
href="https://www.facebook.com/NeoNovaNNS/"
target="_blank" moz-do-not-send="true"><img
src="http://neonova.net/wp-content/uploads/2016/12/facebookIcon.png"
moz-do-not-send="true" width="10" height="10"></a> <a
href="https://twitter.com/NeoNova_NNS"
target="_blank" moz-do-not-send="true"><img
src="http://neonova.net/wp-content/uploads/2016/12/twitterIcon.png"
moz-do-not-send="true" width="10" height="10"></a> <a
href="http://www.linkedin.com/company/neonova-network-services"
target="_blank" moz-do-not-send="true"><img
src="http://neonova.net/wp-content/uploads/2016/12/linkedinIcon.png"
moz-do-not-send="true" width="10" height="10"></a></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<br>
</div>
</div>
<br>
<div class="gmail_quote">On Tue, Jan 16, 2018 at
6:54 PM, Randy Leiker <span dir="ltr"><<a
href="mailto:randy@skywaynetworks.com"
target="_blank" moz-do-not-send="true">randy@skywaynetworks.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="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000">
<div style="color:rgb(0,0,0)"><font
size="2" face="arial, helvetica,
sans-serif">Hi Everyone,</font></div>
<div style="color:rgb(0,0,0)"><font
size="2" face="arial, helvetica,
sans-serif"><br>
</font></div>
<div style="color:rgb(0,0,0)"><font
size="2" face="arial, helvetica,
sans-serif">Earlier, on today's weekly
Zeta Alliance call, I proposed a
project to introduce new resiliency
capabilities to Zimbra mailbox
servers. Here's an outline of what
was discussed & a further
expansion on that topic:</font></div>
<div style="color:rgb(0,0,0)"><font
size="2" face="arial, helvetica,
sans-serif"><br>
</font></div>
<div style="color:rgb(0,0,0)"><b><font
size="2" face="arial, helvetica,
sans-serif">Project Background</font></b></div>
<div style="color:rgb(0,0,0)"><font
size="2" face="arial, helvetica,
sans-serif">Dating back to early
Zimbra versions, it's always been
possible to create a cluster of Zimbra
server nodes where individual
components of Zimbra can be broken out
into separate nodes for both load
balancing & reliability benefits.
As an example, consider a minimal
Zimbra cluster with:</font></div>
<div style="color:rgb(0,0,0)">
<ul>
<li><font size="2" face="arial,
helvetica, sans-serif">2 x LDAP
nodes</font></li>
<li><font size="2" face="arial,
helvetica, sans-serif">2 x Proxy
nodes</font></li>
<li><font size="2" face="arial,
helvetica, sans-serif">2 x MTA
nodes</font></li>
<li><font size="2" face="arial,
helvetica, sans-serif">2 x Mailbox
nodes</font></li>
</ul>
<font size="2" face="arial, helvetica,
sans-serif">Within this example
cluster, you could afford to lose 1 of
each type of node (either due to
maintenance, human error, or a
disaster event), and the Zimbra
cluster would remain mostly
operational. The exception, is the
mailbox nodes, in that, if you lose a
mailbox node, any user mailboxes on
that node become immediately
unavailable. This limitation exists
because, by design, a user's mailbox
storage is tightly bound to a given
mailbox node.</font></div>
<div style="color:rgb(0,0,0)"><font
size="2" face="arial, helvetica,
sans-serif"><br>
</font></div>
<div style="color:rgb(0,0,0)"><font
size="2" face="arial, helvetica,
sans-serif">Shortly after Zimbra was
acquired from Yahoo by VMware, there
were mentions in various webinars
& presentations regarding
expanding on Zimbra's high
availability (HA) capabilities. Most
of those discussions seemed to focus
on leveraging HA capabilities that
were part of VMware products, but not
necessarily in adding native HA
capabilities to the Zimbra Suite
itself. The VMware approach to HA for
Zimbra works, as long as the VM
hosting a Zimbra node remains bootable
and all of the Zimbra services can
start successfully following recovery
by VMware's HA feature. However, it's
of no help when you need to take a
Zimbra mailbox node down for
maintenance, perform a mailbox node
upgrade, troubleshoot a fault on a
mailbox node, or just deprecate a
mailbox node for migration to newer
hardware, since the end result is down
time for mailbox end users.</font></div>
<div style="color:rgb(0,0,0)"><font
size="2" face="arial, helvetica,
sans-serif"><br>
</font></div>
<div style="color:rgb(0,0,0)"><font
size="2" face="arial, helvetica,
sans-serif">In more recent years,
Zimbra mailbox node HA was on the road
map for Telligent, and most recently
is on the road map for Synacor, with
some suggestions indicating that it
might make an appearance in a Zimbra
9.0 release. I think many Zimbra
partners understand the significant
undertaking that will be needed to
decouple the storage of end user
mailboxes from the mailbox nodes, and
given that effort, the arrival of a
true mailbox node HA feature is
probably some ways off yet into the
future.</font></div>
<div style="color:rgb(0,0,0)"><font
size="2" face="arial, helvetica,
sans-serif"><br>
</font></div>
<div style="color:rgb(0,0,0)"><b><font
size="2" face="arial, helvetica,
sans-serif">Project Proposal</font></b></div>
<div style="color:rgb(0,0,0)"><font
size="2" face="arial, helvetica,
sans-serif">I propose building new
flexibility around Zimbra mailbox
nodes, while leaving the standard
Zimbra distribution as-is. This would
allow for addressing the current
shortcomings outlined above. Above
all, the intent of the project is to
avoid changing the standard Zimbra
distribution, so as not to create
future support or upgrade problems,
and rather to leverage a combination
of freely available, open source tools
& built-in Zimbra admin utilities
to make it easy enough that Zimbra
admins (of all skill levels) have the
ability to take Zimbra mailbox nodes
on & offline at-will with no
disruption to mailbox end users. This
doesn't eliminate the need for best
practices, such as regular backups of
your Zimbra infrastructure, but rather
seeks to solve issues that backups
don't address.</font></div>
<div style="color:rgb(0,0,0)"><font
size="2" face="arial, helvetica,
sans-serif"><br>
</font></div>
<div style="color:rgb(0,0,0)"><font
size="2" face="arial, helvetica,
sans-serif">The project involves
placing all Zimbra mailbox nodes
within Docker containers, so it's the
same mailbox node install you're used
to doing, but just within a container
instead. Other components of Zimbra
(LDAP, MTAs, Proxies, etc.) could
continue to run as VMs, physical
machines, or perhaps within containers
as well. With at least several
containers, each running a Zimbra
mailbox node, user mailboxes would
presumably be evenly distributed over
those mailbox nodes. This
distribution could be done arbitrarily
by a Zimbra admin, or through the
course of normal day-to-day
provisioning of mailboxes, by allowing
Zimbra to choose which mailbox node to
provision mailboxes on, from the pool
of available mailbox nodes, which is
functionality that exists today within
Zimbra. With the introduction of the
Zextras tools in Zimbra 8.8, using the
Zextras backup/restore functionality
would be yet another means to migrate
customer mailboxes into mailbox nodes,
housed within containers.</font></div>
<div style="color:rgb(0,0,0)"><font
size="2" face="arial, helvetica,
sans-serif"><br>
</font></div>
<div style="color:rgb(0,0,0)"><font
size="2" face="arial, helvetica,
sans-serif">A script would then be
created to allow for a given mailbox
node (container) to have all of its
mailboxes evacuated automatically.
There are many cases where you may
need to place a mailbox node into
maintenance mode. To name a few:</font></div>
<div>
<ul>
<li><font size="2" face="arial,
helvetica, sans-serif">A service
impacting configuration change is
needed. For example, a Zimbra
service restart for a new Let's
Encrypt SSL certificate, or a
zmprov local configuration value
change that you want to test.</font></li>
<li><font size="2" face="arial,
helvetica, sans-serif">A hardware
or software (operating
system/Zimbra package) fault
exists.</font></li>
<li><font size="2" face="arial,
helvetica, sans-serif">The mailbox
node has insufficient hardware
resources & is being
deprecated for a newer mailbox
node with more resources.</font></li>
<li><font size="2" face="arial,
helvetica, sans-serif">The mailbox
node has developed an unknown,
difficult to troubleshoot problem,
so rather than troubleshoot it,
the node is simply replaced.</font></li>
<li><font size="2" face="arial,
helvetica, sans-serif">A prior
configuration error (aka human
error) has led to an unstable
mailbox node, so rather than
fixing it, the node is replaced.</font></li>
</ul>
<div><font size="2" face="arial,
helvetica, sans-serif">The script
would take a few simple inputs, such
as the target mailbox node, and the
desired action. Available actions
might include:</font></div>
<div>
<ul>
<li><font size="2" face="arial,
helvetica, sans-serif">Evacuating
all mailboxes from a node</font></li>
<li><font size="2" face="arial,
helvetica, sans-serif">Restoring
mailboxes to a node</font></li>
<li><font size="2" face="arial,
helvetica, sans-serif">Evacuating
all mailboxes & removing the
node from the cluster</font></li>
<li><font size="2" face="arial,
helvetica, sans-serif">Adding a
node to the Zimbra cluster &
re-distributing mailboxes to the
newly added node</font></li>
</ul>
<font size="2" face="arial, helvetica,
sans-serif">For options requiring
evacuation of mailboxes, the script
would query Zimbra LDAP to determine
which mailboxes are on that server,
then using Zimbra's built-in
zmmailbox utility, evacuate those
mailboxes evenly across the
remaining mailbox nodes
(containers). For options requiring
adding/removal of mailbox nodes,
this would have a tie-in with both
Docker & perhaps Kubernetes to
allow for automating the
provisioning & de-provisioning
of containers for hosting the
mailbox nodes. I think there's room
to greatly expand on the available
actions for this script, but this
could be the first few steps. Care
would be needed to ensure that the
script handles error conditions
well, most likely by alerting a
human to a problem encountered
carrying out a given action, with a
recommendation of what's needed next
to resolve it.</font></div>
</div>
<div><font size="2" face="arial,
helvetica, sans-serif"><br>
</font></div>
<div><font size="2" face="arial,
helvetica, sans-serif">I know that's a
long email, but wanted to offer some
explanation to give you a scope of the
project. The project would be free
& open source for all in the
Zimbra community to use. Several
people expressed interest in this
project on the weekly call earlier
today. I'm curious to hear if others
in the Zeta Alliance feel that this
would be a worthwhile project that
your organization could use and/or
contribute to in the form of ideas,
development, or testing. Your
thoughts & feedback please?</font></div>
<div
style="color:rgb(0,0,0);font-family:arial,helvetica,sans-serif;font-size:10pt"><br>
</div>
<br>
<div
style="color:rgb(0,0,0);font-family:arial,helvetica,sans-serif;font-size:10pt"><span></span>
<div>
<div>
<div><span
style="color:rgb(255,102,0);font-weight:bold"><br>
Randy Leiker (</span><span
style="font-weight:bold"> <span
style="color:rgb(51,51,255);background-color:rgb(255,255,255)"><a
href="mailto:randy@skywaynetworks.com"
target="_blank"
moz-do-not-send="true">randy@skywaynetworks.com</a></span>
<span
style="color:rgb(255,102,0)">)</span></span><br>
<span style="color:rgb(0,0,153)">Skyway
Networks, LLC</span><br>
<span style="color:rgb(0,0,153)"><a
href="tel:%28800%29%20538-5334" target="_blank" moz-do-not-send="true">1.800.538.5334</a></span>
<span style="color:rgb(255,102,0)">/</span>
<span style="color:rgb(0,0,153)"><a
href="tel:%28913%29%20663-3900" target="_blank" moz-do-not-send="true">913.663.3900
Ext. 100</a></span><br>
<span style="color:rgb(0,0,153)"></span><a
href="http://www.skywaynetworks.com" target="_blank"
moz-do-not-send="true">https://www.skywaynetworks.com</a><br>
</div>
</div>
</div>
<span></span><br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>