<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 16, 2017, at 7:57 AM, Yaguang Tang <<a href="mailto:heut2008@gmail.com" class="">heut2008@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I'd like to see this feature "<b class="">Attach a single volume to multiple instances</b>" <a href="https://blueprints.launchpad.net/nova/+spec/multi-attach-volume" class="">https://blueprints.launchpad.net/nova/+spec/multi-attach-volume</a> to be implmented in Nova side. <div class=""><br class=""></div><div class="">This feature has been working for more than two years, but hasn't been accepted by upstream…</div></div></div></blockquote><div><br class=""></div><div>I would second this, we have users which have asked for this for quite sometime. 99% of the work is there (at least on the Cinder side) so it’s just a matter of integrating it within the Nova side of things.</div><br class=""><blockquote type="cite" class=""><div class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Sun, Jan 15, 2017 at 2:53 PM, Joshua Harlow <span dir="ltr" class=""><<a href="mailto:harlowja@fastmail.com" target="_blank" class="">harlowja@fastmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'll add a couple:<br class="">
<br class="">
Cascading deletes,<br class="">
<br class="">
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 class="">
<br class="">
Orphans (not the annie kind),<br class="">
<br class="">
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 class="">
<br class="">
$ find . | grep -i "orphan"<br class="">
./libvirt/cleanup-orphaned-vms<wbr class="">.sh<br class="">
./libvirt/remove-deleted-orpha<wbr class="">ns.sh<br class="">
./neutron/delete_orphan_floati<wbr class="">ngips.py<br class="">
./neutron/listorphans.py<br class="">
./nova/orphaned_vms.sh<br class="">
./ansible/playbooks/orphaned-v<wbr class="">m-clenaup.yaml<br class="">
./ansible/tasks/orphaned-vms.y<wbr class="">aml<br class="">
./cinder/orphaned_volumes.sh<br class="">
<br class="">
Same with <a href="https://github.com/openstack/ospurge" rel="noreferrer" target="_blank" class="">https://github.com/openstack/o<wbr class="">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 class="">
<br class="">
Just search google for 'openstack orphan cleanup' and you'll find more scripts and code that people have been writing...<br class="">
<br class="">
-Josh<br class="">
<br class="">
Melvin Hillsman wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
Hey everyone,<br class="">
<br class="">
I am hoping to get a dialogue started to gain some insight around things<br class="">
Operators, Application Developers, and End Users would like to see<br class="">
happen in Pike. If you had a dedicated environment, dedicated team, and<br class="">
freedom to choose how you deployed, new features, older features,<br class="">
enhancements, etc, and were not required to deal with customer/client<br class="">
tickets, calls, and maintenances, could keep a good feedback loop<br class="">
between your team and the upstream community of any project, what would<br class="">
like to make happen or work on hoping the next release of OpenStack<br class="">
had/included/changed/enhanced/<wbr class="">removed…?<br class="">
<br class="">
Kind regards,<br class="">
<br class="">
--<br class="">
<br class=""></span>
*Melvin Hillsman*<span class=""><br class="">
<br class="">
Ops Technical Lead<br class="">
<br class="">
OpenStack Innovation Center<br class="">
<br class=""></span>
_<a href="mailto:mrhillsman@gmail.com" target="_blank" class="">mrhillsman@gmail.com</a> <mailto:<a href="mailto:mrhillsman@gmail.com" target="_blank" class="">mrhillsman@gmail.com</a>>_<span class=""><br class="">
<br class="">
phone: <a href="tel:%28210%29%20312-1267" value="+12103121267" target="_blank" class="">(210) 312-1267</a><br class="">
<br class="">
mobile: <a href="tel:%28210%29%20413-1659" value="+12104131659" target="_blank" class="">(210) 413-1659</a><br class="">
<br class="">
Learner | Ideation | Belief | Responsibility | Command<br class="">
<br class=""></span>
_<a href="http://osic.org_/" rel="noreferrer" target="_blank" class="">http://osic.org_</a><br class="">
<br class="">
______________________________<wbr class="">_________________<br class="">
OpenStack-operators mailing list<br class="">
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank" class="">OpenStack-operators@lists.open<wbr class="">stack.org</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi<wbr class="">-bin/mailman/listinfo/openstac<wbr class="">k-operators</a><br class="">
</blockquote>
<br class="">
______________________________<wbr class="">_________________<br class="">
OpenStack-operators mailing list<br class="">
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank" class="">OpenStack-operators@lists.open<wbr class="">stack.org</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi<wbr class="">-bin/mailman/listinfo/openstac<wbr class="">k-operators</a><br class="">
</blockquote></div><br class=""><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class="">Tang Yaguang</div><div class=""><br class=""></div><br class=""><div class=""> </div></div></div>
</div>
_______________________________________________<br class="">OpenStack-operators mailing list<br class=""><a href="mailto:OpenStack-operators@lists.openstack.org" class="">OpenStack-operators@lists.openstack.org</a><br class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators<br class=""></div></blockquote></div><br class=""></body></html>