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 (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
_mrhills...@gmail.com <mailto:mrhills...@gmail.com>_
phone: (210) 312-1267
mobile: (210) 413-1659
Learner | Ideation | Belief | Responsibility | Command
_http://osic.org_
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
