<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:"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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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.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:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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 lang=EN-US link=blue vlink=purple><div class=WordSection1><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.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>-amrith<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><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><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:heut2008@gmail.com] <br><b>Sent:</b> Monday, January 16, 2017 7:57 AM<br><b>To:</b> Joshua Harlow <harlowja@fastmail.com><br><b>Cc:</b> OpenStack Operators <openstack-operators@lists.openstack.org><br><b>Subject:</b> Re: [Openstack-operators] What would you like in Pike?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></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">https://blueprints.launchpad.net/nova/+spec/multi-attach-volume</a> to be implmented in Nova side. <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>This feature has been working for more than two years, but hasn't been accepted by upstream...<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></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:<o:p></o:p></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-vms.sh<br>./libvirt/remove-deleted-orphans.sh<br>./neutron/delete_orphan_floatingips.py<br>./neutron/listorphans.py<br>./nova/orphaned_vms.sh<br>./ansible/playbooks/orphaned-vm-clenaup.yaml<br>./ansible/tasks/orphaned-vms.yaml<br>./cinder/orphaned_volumes.sh<br><br>Same with <a href="https://github.com/openstack/ospurge" target="_blank">https://github.com/openstack/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:<o:p></o:p></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/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>_______________________________________________<br>OpenStack-operators mailing list<br><a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><o:p></o:p></p></blockquote><p class=MsoNormal><br>_______________________________________________<br>OpenStack-operators mailing list<br><a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><o:p></o:p></p></blockquote></div><p class=MsoNormal><br><br clear=all><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>-- <o:p></o:p></p><div><div><div><p class=MsoNormal>Tang Yaguang<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal> <o:p></o:p></p></div></div></div></div></div></div></body></html>