[Openstack-operators] What would you like in Pike?

Mohammed Naser mnaser at vexxhost.com
Mon Jan 16 13:06:19 UTC 2017


> On Jan 16, 2017, at 7:57 AM, Yaguang Tang <heut2008 at gmail.com> wrote:
> 
> I'd like to see this feature  "Attach a single volume to multiple instances" https://blueprints.launchpad.net/nova/+spec/multi-attach-volume <https://blueprints.launchpad.net/nova/+spec/multi-attach-volume> to be implmented in Nova side. 
> 
> This feature has been working for more than two years, but hasn't been accepted by upstream…

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.

> 
> On Sun, Jan 15, 2017 at 2:53 PM, Joshua Harlow <harlowja at fastmail.com <mailto:harlowja at fastmail.com>> wrote:
> I'll add a couple:
> 
> Cascading deletes,
> 
> 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).
> 
> Orphans (not the annie kind),
> 
> 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)?
> 
> $ find . | grep -i "orphan"
> ./libvirt/cleanup-orphaned-vms.sh
> ./libvirt/remove-deleted-orphans.sh
> ./neutron/delete_orphan_floatingips.py
> ./neutron/listorphans.py
> ./nova/orphaned_vms.sh
> ./ansible/playbooks/orphaned-vm-clenaup.yaml
> ./ansible/tasks/orphaned-vms.yaml
> ./cinder/orphaned_volumes.sh
> 
> Same with https://github.com/openstack/ospurge <https://github.com/openstack/ospurge> (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).
> 
> Just search google for 'openstack orphan cleanup' and you'll find more scripts and code that people have been writing...
> 
> -Josh
> 
> Melvin Hillsman wrote:
> Hey everyone,
> 
> I am hoping to get a dialogue started to gain some insight around things
> Operators, Application Developers, and End Users would like to see
> happen in Pike. If you had a dedicated environment, dedicated team, and
> freedom to choose how you deployed, new features, older features,
> enhancements, etc, and were not required to deal with customer/client
> tickets, calls, and maintenances, could keep a good feedback loop
> between your team and the upstream community of any project, what would
> like to make happen or work on hoping the next release of OpenStack
> had/included/changed/enhanced/removed…?
> 
> Kind regards,
> 
> --
> 
> *Melvin Hillsman*
> 
> Ops Technical Lead
> 
> OpenStack Innovation Center
> 
> _mrhillsman at gmail.com <mailto:mrhillsman at gmail.com> <mailto:mrhillsman at gmail.com <mailto:mrhillsman at gmail.com>>_
> 
> phone: (210) 312-1267 <tel:%28210%29%20312-1267>
> 
> mobile: (210) 413-1659 <tel:%28210%29%20413-1659>
> 
> Learner | Ideation | Belief | Responsibility | Command
> 
> _http://osic.org_ <http://osic.org_/>
> 
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org <mailto:OpenStack-operators at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators>
> 
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org <mailto:OpenStack-operators at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators>
> 
> 
> 
> -- 
> Tang Yaguang
> 
> 
>  
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20170116/05222c49/attachment.html>


More information about the OpenStack-operators mailing list