Hi all, we would also like to see both of the features mentioned by Tim getting a clear path into Pike. We are daily struggling with the same problems CERN has (albeit at a much smaller scale), and getting these two things would greatly simplify our day-to-day life and ability to use OpenStack to do compute-on-demand.
Cheers, Dario Vianello Cloud Bioinformatics Application Architect European Bioinformatics Institute (EMBL-EBI) Wellcome Trust Genome Campus, Hinxton, Cambridge, CB10 1SD, UK Email: da...@ebi.ac.uk <mailto:da...@ebi.ac.uk> > On 14 Jan 2017, at 10:10, Tim Bell <tim.b...@cern.ch> 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 > > <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/) > <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 <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
