<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p dir="auto" style=" text-align: left; margin-top: 25px; margin-bottom: 25px; font-family: sans-serif; font-size: 11pt; color: black; background-color: white ">
This is a feature that would help a lot when building mssql-server cluster with shared disk instead of setting up iscsi inside the machines.</p>
<p dir="auto" style=" text-align: left; margin-top: 25px; margin-bottom: 25px; font-family: sans-serif; font-size: 11pt; color: black; background-color: white ">
Skaffa Outlook för Android<br>
</p>
<br>
<br>
<br>
<div class="gmail_quote">On Mon, Jan 16, 2017 at 2:02 PM +0100, "Yaguang Tang" <span dir="ltr">
<<a href="mailto:heut2008@gmail.com" target="_blank">heut2008@gmail.com</a>></span> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="3D"ltr"">
<div dir="ltr">I'd like to see this feature "<b>Attach a single volume to multiple instances</b>"
<a href="https://blueprints.launchpad.net/nova/+spec/multi-attach-volume">https://blueprints.launchpad.net/nova/+spec/multi-attach-volume</a> to be implmented in Nova side.
<div><br>
</div>
<div>This feature has been working for more than two years, but hasn't been accepted by upstream...</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sun, Jan 15, 2017 at 2:53 PM, Joshua Harlow <span dir="ltr">
<<a href="mailto:harlowja@fastmail.com" target="_blank">harlowja@fastmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'll add a couple:<br>
<br>
Cascading deletes,<br>
<br>
Ie when a tenant/project/user is removed from keystone there should be someway to say deny that request if that tenant/project/user has active resources or there should be a away to cascade that delete through the rest of those resources (so they are deleted
also).<br>
<br>
Orphans (not the annie kind),<br>
<br>
Pretty sure the osops-tools-generic repo contains a bunch of scripts around orphaned items cleanup; this seems *similar* to the above and it feels these should be like umm fixed (or those scripts should be deleted if its not an issue anymore)?<br>
<br>
$ find . | grep -i "orphan"<br>
./libvirt/cleanup-orphaned-vms<wbr>.sh<br>
./libvirt/remove-deleted-orpha<wbr>ns.sh<br>
./neutron/delete_orphan_floati<wbr>ngips.py<br>
./neutron/listorphans.py<br>
./nova/orphaned_vms.sh<br>
./ansible/playbooks/orphaned-v<wbr>m-clenaup.yaml<br>
./ansible/tasks/orphaned-vms.y<wbr>aml<br>
./cinder/orphaned_volumes.sh<br>
<br>
Same with <a href="https://github.com/openstack/ospurge" rel="noreferrer" target="_blank">
https://github.com/openstack/o<wbr>spurge</a> (which seems like a specific project to try to clean this mess up, sorta funny/sad? that it has to exist in the first place).<br>
<br>
Just search google for 'openstack orphan cleanup' and you'll find more scripts and code that people have been writing...<br>
<br>
-Josh<br>
<br>
Melvin Hillsman wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="">Hey everyone,<br>
<br>
I am hoping to get a dialogue started to gain some insight around things<br>
Operators, Application Developers, and End Users would like to see<br>
happen in Pike. If you had a dedicated environment, dedicated team, and<br>
freedom to choose how you deployed, new features, older features,<br>
enhancements, etc, and were not required to deal with customer/client<br>
tickets, calls, and maintenances, could keep a good feedback loop<br>
between your team and the upstream community of any project, what would<br>
like to make happen or work on hoping the next release of OpenStack<br>
had/included/changed/enhanced/<wbr>removed…?<br>
<br>
Kind regards,<br>
<br>
--<br>
<br>
</span>*Melvin Hillsman*<span class=""><br>
<br>
Ops Technical Lead<br>
<br>
OpenStack Innovation Center<br>
<br>
</span>_<a href="mailto:mrhillsman@gmail.com" target="_blank">mrhillsman@gmail.com</a> <mailto:<a href="mailto:mrhillsman@gmail.com" target="_blank">mrhillsman@gmail.com</a>>_<span class=""><br>
<br>
phone: <a href="tel:%28210%29%20312-1267" value="+12103121267" target="_blank">(210) 312-1267</a><br>
<br>
mobile: <a href="tel:%28210%29%20413-1659" value="+12104131659" target="_blank">(210) 413-1659</a><br>
<br>
Learner | Ideation | Belief | Responsibility | Command<br>
<br>
</span>_<a href="http://osic.org_" rel="noreferrer" target="_blank">http://osic.org_</a><br>
<br>
______________________________<wbr>_________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.open<wbr>stack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-operators</a><br>
</blockquote>
<br>
______________________________<wbr>_________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.open<wbr>stack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-operators</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div>Tang Yaguang</div>
<div><br>
</div>
<br>
<div> </div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</body>
</html>