<div dir="ltr">Another +1 for mult-attach please. </div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 16, 2017 at 6:09 AM, Amrith Kumar <span dir="ltr"><<a href="mailto:amrith.kumar@gmail.com" target="_blank">amrith.kumar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div class="m_8080429508592480410WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I echo this sentiment; attaching a single Cinder volume or a group of volumes in a consistency group to multiple instances would be something I’d like to see in Pike.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">-amrith<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><u></u> <u></u></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><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Yaguang Tang [mailto:<a href="mailto:heut2008@gmail.com" target="_blank">heut2008@gmail.com</a>] <br><b>Sent:</b> Monday, January 16, 2017 7:57 AM<br><b>To:</b> Joshua Harlow <<a href="mailto:harlowja@fastmail.com" target="_blank">harlowja@fastmail.com</a>><br><b>Cc:</b> OpenStack Operators <<a href="mailto:openstack-operators@lists.openstack.org" target="_blank">openstack-operators@lists.<wbr>openstack.org</a>><br><b>Subject:</b> Re: [Openstack-operators] What would you like in Pike?<u></u><u></u></span></p></div></div><div><div class="h5"><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">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" target="_blank">https://blueprints.launchpad.<wbr>net/nova/+spec/multi-attach-<wbr>volume</a> to be implmented in Nova side. <u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">This feature has been working for more than two years, but hasn't been accepted by upstream...<u></u><u></u></p></div></div><div><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">On Sun, Jan 15, 2017 at 2:53 PM, Joshua Harlow <<a href="mailto:harlowja@fastmail.com" target="_blank">harlowja@fastmail.com</a>> wrote:<u></u><u></u></p><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><p class="MsoNormal">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-<wbr>vms.sh<br>./libvirt/remove-deleted-<wbr>orphans.sh<br>./neutron/delete_orphan_<wbr>floatingips.py<br>./neutron/listorphans.py<br>./nova/orphaned_vms.sh<br>./ansible/playbooks/orphaned-<wbr>vm-clenaup.yaml<br>./ansible/tasks/orphaned-vms.<wbr>yaml<br>./cinder/orphaned_volumes.sh<br><br>Same with <a href="https://github.com/openstack/ospurge" target="_blank">https://github.com/openstack/<wbr>ospurge</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:<u></u><u></u></p><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><p class="MsoNormal">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>*Melvin Hillsman*<br><br>Ops Technical Lead<br><br>OpenStack Innovation Center<br><br>_<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>>_<br><br>phone: <a href="tel:%28210%29%20312-1267" target="_blank">(210) 312-1267</a><br><br>mobile: <a href="tel:%28210%29%20413-1659" target="_blank">(210) 413-1659</a><br><br>Learner | Ideation | Belief | Responsibility | Command<br><br>_<a href="http://osic.org_" 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.<wbr>openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-operators</a><u></u><u></u></p></blockquote><p class="MsoNormal"><br>______________________________<wbr>_________________<br>OpenStack-operators mailing list<br><a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.<wbr>openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-operators</a><u></u><u></u></p></blockquote></div><p class="MsoNormal"><br><br clear="all"><u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p></div><p class="MsoNormal">-- <u></u><u></u></p><div><div><div><p class="MsoNormal">Tang Yaguang<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal"> <u></u><u></u></p></div></div></div></div></div></div></div></div></div><br>______________________________<wbr>_________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.<wbr>openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-operators</a><br>
<br></blockquote></div><br></div>