<div dir="ltr"><div class="gmail_default" style="font-family:courier new,monospace">Tim,<br><br></div><div class="gmail_default" style="font-family:courier new,monospace">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.<br><br></div><div class="gmail_default" style="font-family:courier new,monospace">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></div><div class="gmail_default" style="font-family:courier new,monospace"><br></div><div class="gmail_default" style="font-family:courier new,monospace">Thanks!<br></div><div class="gmail_extra"><div><div class="gmail_signature" data-smartmail="gmail_signature"><span style="font-family:courier new,monospace"></span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">-amrith</span><br><br><br></div></div>
<br><div class="gmail_quote">On Tue, Aug 15, 2017 at 12:43 PM, Tim Bell <span dir="ltr"><<a href="mailto:Tim.Bell@cern.ch" target="_blank">Tim.Bell@cern.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" link="blue" vlink="purple" lang="EN-GB">
<div class="m_4327822111919757063WordSection1">
<p class="MsoNormal"><span>One idea I found interesting from the past discussion was the approach that the user need is a database with a connection string.<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>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?<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>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.<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>Tim<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span 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.<wbr>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.<wbr>openstack.org</a>><br>
<b>Subject: </b>[openstack-dev] [trove][tc][all] Trove restart - next steps<u></u><u></u></span></p>
</div><div><div class="h5">
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><u></u> <u></u></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt">
<span style="font-size:10.0pt;font-family:"Courier",serif">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><u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt">
<span style="font-size:10.0pt;font-family:"Courier",serif">-amrith<br>
<br>
<br>
<br>
[1] <a href="http://openstack.markmail.org/thread/wokk73ecv44ipfjz" target="_blank">http://openstack.markmail.org/<wbr>thread/wokk73ecv44ipfjz</a><br>
[2] <a href="http://markmail.org/message/gfqext34xh5y37ir" target="_blank">http://markmail.org/message/<wbr>gfqext34xh5y37ir</a><br>
<br>
</span><u></u><u></u></p>
</div>
</div>
</div>
</div></div></div>
</div>
<br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br></div></div>