What Tim said :) my ordering:
1) Preemptable Instances -- this would be huge and life changing I'd give up any other improvements to get this. 2) Deeper utilization of nested projects -- mostly we find ways to mange with out this but it would be great to have. A) to allow research groups (our internal fiscal/administrative divisions) to sub divide quota allocations accordinf to their own priorities on a self serve basis (provided proper RBAC configs) B) to answer show back questions more easily. Currently with flat projects individual research groups have multiple openstack projects, by convention we mange to usually be able to aggregaet them in reporting, but deing able to show susage by a parent and all it 's childeren woudl be very useful 3) Quota improvements -- this is important but we've learned to deal with it -Jon On Sat, Jan 14, 2017 at 10:10:40AM +0000, Tim Bell wrote: :There are a couple of items which have not been able to make it to the top priority for recent releases which would greatly simplify our day to day work with the users and make the cloud more flexible. The background use cases are described in https://openstack-in-production.blogspot.fr/2016/04/resource-management-at-cern.html : : :- Quota management improvements : :o Manual interventions are often required to sync the current usage with the OpenStack view : :o Nested projects are now in Keystone but is limited support in other projects for the end user benefit, such as delegation of quota for sub-projects : :- Nova pre-emptible instances (https://review.openstack.org/#/c/104883/) to give spot market functionality : :o We want to run our cloud at near 100% utilisation but this requires rapid ejection of lower priority VMs : :That having been said, I also fully support key priorities currently being worked on such as cells v2 and placement. : :Tim : :From: Melvin Hillsman <mrhills...@gmail.com> :Date: Friday, 13 January 2017 at 02:30 :To: openstack-operators <openstack-operators@lists.openstack.org> :Subject: [Openstack-operators] What would you like in Pike? : :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
