<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Courier;
panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:Consolas;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:595.0pt 842.0pt;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:2081560288;
mso-list-type:hybrid;
mso-list-template-ids:-655745648 872735620 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Consolas;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:10.0pt;font-family:Consolas;color:#1F497D'>Tim,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Consolas;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Consolas;color:#1F497D'>Sorry for the delay getting back to you.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Consolas;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Consolas;color:#1F497D'>Different database vendors give you different levels of isolation within your database itself, and making a database truly multi-tenant was something that we did not want to get into. The discussion centered around the benefits of such a use-case and thing that drove the decision to not go down the path of multi-tenancy was that if Trove provided a VM per database instance, implementing multi-tenancy is something that a trove user can in fact do for themselves.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Consolas;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Consolas;color:#1F497D'>At the time when we thought about this, the critical things on the horizon were to implement replication and clustering, and add support for more capabilities and databases. Therefore multi-tenancy did not rise very far on the list. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Consolas;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Consolas;color:#1F497D'>Looking at it again, I like the idea but again think there are higher priority things I’d like to focus on first. In digging us out of the current ditch that we are in, multi-tenancy may not be the thing that would materially benefit the project.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Consolas;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Consolas;color:#1F497D'>But, we shall discuss in a week or so at PTG.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Consolas;color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:Consolas;color:#1F497D'>--<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Consolas;color:#1F497D'>Amrith Kumar<br><a href="mailto:amrith.kumar@gmail.com">amrith.kumar@gmail.com</a><br><br><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:Consolas;color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> Tim Bell [mailto:Tim.Bell@cern.ch] <br><b>Sent:</b> Wednesday, August 16, 2017 1:45 PM<br><b>To:</b> OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org><br><b>Subject:</b> Re: [openstack-dev] [trove][tc][all] Trove restart - next steps<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Thanks for the info.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Can you give a summary for reasons for why this was not a viable approach?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Tim<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin-left:.5in'><b><span lang=EN-GB style='font-size:12.0pt;color:black'>From: </span></b><span lang=EN-GB style='font-size:12.0pt;color:black'>Amrith Kumar <<a href="mailto:amrith.kumar@gmail.com">amrith.kumar@gmail.com</a>><br><b>Reply-To: </b>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br><b>Date: </b>Tuesday, 15 August 2017 at 23:09<br><b>To: </b>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br><b>Subject: </b>Re: [openstack-dev] [trove][tc][all] Trove restart - next steps<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB><o:p> </o:p></span></p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><span lang=EN-GB style='font-family:"Courier New"'>Tim,<o:p></o:p></span></p></div><div><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><span lang=EN-GB style='font-family:"Courier New"'>This is an idea that was discussed at a trove midcycle a long time back (Juno midcycle, 2014). It came up briefly in the Kilo midcycle as well but was quickly rejected again.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB style='font-family:"Courier New"'>I've added it to the list of topics for discussion at the PTG. If others want to add topics to that list, the etherpad is at <a href="https://etherpad.openstack.org/p/trove-queens-ptg">https://etherpad.openstack.org/p/trove-queens-ptg</a></span><span lang=EN-GB style='font-family:"Cambria Math",serif'></span><span lang=EN-GB style='font-family:"Courier New"'><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB style='font-family:"Courier New"'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB style='font-family:"Courier New"'>Thanks!<o:p></o:p></span></p></div><div><div><div><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><span lang=EN-GB style='font-family:"Courier New"'><br>-amrith</span><span lang=EN-GB><o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB><o:p> </o:p></span></p><div><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB>On Tue, Aug 15, 2017 at 12:43 PM, Tim Bell <<a href="mailto:Tim.Bell@cern.ch" target="_blank">Tim.Bell@cern.ch</a>> wrote:<o:p></o:p></span></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'><span lang=EN-GB>One idea I found interesting from the past discussion was the approach that the user need is a database with a connection string.<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'><span lang=EN-GB> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'><span lang=EN-GB>How feasible is the approach where we are provisioning access to a multi-tenant database infrastructure rather than deploying a VM with storage and installing a database?<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'><span lang=EN-GB> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'><span lang=EN-GB>This would make the service delivery (monitoring, backup, upgrades) in the responsibility of the cloud provider rather than the end user. Some quota/telemetry would be needed to allocate costs to the project.<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'><span lang=EN-GB> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'><span lang=EN-GB>Tim<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'><span lang=EN-GB> <o:p></o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.0in'><b><span lang=EN-GB style='font-size:12.0pt;color:black'>From: </span></b><span lang=EN-GB style='font-size:12.0pt;color:black'>Amrith Kumar <<a href="mailto:amrith.kumar@gmail.com" target="_blank">amrith.kumar@gmail.com</a>><br><b>Reply-To: </b>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br><b>Date: </b>Tuesday, 15 August 2017 at 17:44<br><b>To: </b>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br><b>Subject: </b>[openstack-dev] [trove][tc][all] Trove restart - next steps</span><span lang=EN-GB><o:p></o:p></span></p></div><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.0in'><span lang=EN-GB> <o:p></o:p></span></p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt;margin-left:1.0in'><span lang=EN-GB style='font-size:10.0pt;font-family:Courier'>Now that we have successfully navigated the Pike release and branched<br>the tree, I would like to restart the conversation about how to revive<br>and restart the Trove project.<br><br>Feedback from the last go around on this subject[1] resulted in a<br>lively discussion which I summarized in [2]. The very quick summary is<br>this, there is interest in Trove, there is a strong desire to maintain<br>a migration path, there is much that remains to be done to get there.<br><br>What didn't come out of the email discussion was any concrete and<br>tangible uptick in the participation in the project, promises<br>notwithstanding.<br><br>There have however been some new contributors who have been submitting<br>patches and to help channel their efforts, and any additional<br>assistance that we may receive, I have created the (below) list of<br>priorities for the project. These will also be the subject of<br>discussion at the PTG in Denver.<br><br> - Fix the gate<br><br> - Update currently failing jobs, create xenial based images<br> - Fix gate jobs that have gone stale (non-voting, no one paying<br> attention)<br><br> - Bug triage<br><br> - Bugs in launchpad are really out of date, assignments to<br> people who are no longer active, bugs that are really support<br> requests, etc.,<br> - Prioritize fixes for Queens and beyond<br><br> - Get more active reviewers<br><br> - There seems to still be a belief that 'contributing' means<br> 'fixing bugs'. There is much more value in actually doing<br> reviews.<br> - Get at least a three member active core review team by the<br> end of the year.<br><br> - Complete Python 3 support<br><br> - Currently not complete; especially on the guest side<br><br> - Community Goal, migrate to oslo.policy<br><br> - Anything related to new features<br><br>This is clearly an opinionated list, and is open to change but I'd<br>like to do that based on the Agile 'stand up' meeting rules. You know, the chicken and pigs thing :)<br><br>So, if you'd like to get on board, offer suggestions to change this<br>list, and then go on to actually implement those changes, c'mon over.</span><span lang=EN-GB><o:p></o:p></span></p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt;margin-left:1.0in'><span lang=EN-GB style='font-size:10.0pt;font-family:Courier'>-amrith<br><br><br><br>[1] <a href="http://openstack.markmail.org/thread/wokk73ecv44ipfjz" target="_blank">http://openstack.markmail.org/thread/wokk73ecv44ipfjz</a><br>[2] <a href="http://markmail.org/message/gfqext34xh5y37ir" target="_blank">http://markmail.org/message/gfqext34xh5y37ir</a></span><span lang=EN-GB><o:p></o:p></span></p></div></div></div></div></div></div></div><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><span lang=EN-GB><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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><o:p></o:p></span></p></blockquote></div><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB><o:p> </o:p></span></p></div></div></div></div></body></html>