<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Sorry for arriving late on this, the last Scientific WG discussion on Blazar was here:</div><div class=""><br class=""></div><a href="http://eavesdrop.openstack.org/meetings/scientific_wg/2016/scientific_wg.2016-07-06-09.00.log.html#l-115" class="">http://eavesdrop.openstack.org/meetings/scientific_wg/2016/scientific_wg.2016-07-06-09.00.log.html#l-115</a><div class=""><br class=""></div><div class="">Although there was more substance on OPIE in previous meetings.</div><div class=""><br class=""></div><div class="">Best wishes,</div><div class="">Stig</div><div class=""><br class=""><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 4 Aug 2016, at 04:51, Blair Bethwaite <<a href="mailto:blair.bethwaite@gmail.com" class="">blair.bethwaite@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">We discussed Blazar fairly extensively in a couple of recent<br class="">scientific-wg meetings. I'm having trouble searching out right the irc<br class="">log to support this but IIRC the problem with Blazar as is for the<br class="">typical virtualised cloud (non-Ironic) use-case is that it uses an<br class="">old/deprecated Nova API extension in order to reserve capacity for a<br class="">lease (I think it was something to do with shelve-offload, but I could<br class="">have my wires crossed). Whereas with Ironic it manipulates<br class="">host-aggregates.<br class=""><br class="">I like the idea of the positive, "yes I'm still using this",<br class="">confirmation, but it needs a tie into the dashboard. For those of us<br class="">using identity federations to bootstrap users this would also help<br class="">with account cleanup, as users who no longer have access (e.g., left<br class="">the sector) to the dashboard would not be able to extend resource<br class="">usage (without talking to support etc).<br class=""><br class="">Cheers,<br class=""><br class="">On 4 August 2016 at 03:23, Tim Bell <<a href="mailto:Tim.Bell@cern.ch" class="">Tim.Bell@cern.ch</a>> wrote:<br class=""><blockquote type="cite" class=""><br class="">When I last looked, Blazar allows you to reserve instances for a given time. An example would be<br class=""><br class="">- We are organizing a user training session for 100 physicists from Monday to Friday<br class="">- We need that each user is able to create 2 VMs within a single shared project (as the images etc. are set up before)<br class="">- OpenStack should ensure that these resources would be available (or reject the request) and schedule other Blazar requests around it<br class=""><br class="">This does need other functionality though which is currently not there<br class=""><br class="">- Spot instances, i.e. give me the resources if they are available but kill when you have a reservation. Alvaro is proposing a talk for some work done in Indigo Datacloud project for this at the summit (votes welcome).<br class="">- Impending shutdown notification .. save what you want quickly because you’re going to be deleted<br class=""><br class="">We have a use case where we offer each user a quota of 2 VMs for ‘Personal’ use. This gives a good onboarding experience but the problem is that our users forget they asked for resources. Something where we can define a default lifetime for a VM (ideally, a project) and users need to positively confirm they want to extend the lifetime would help identify these forgotten VMs.<br class=""><br class="">I think a good first step would be<br class=""><br class="">- An agreed metadata structure for a VM with an expiry date<br class="">- An agreed project metadata giving the default length of the VM<br class="">- An OSops script which finds those VMs exceeding the agreed period and goes through a ‘suspend’ for N days followed by a delete M days afterwards (to catch the accidents)<br class=""><br class="">I think this can be done in Nova as is if this is not felt to be a ‘standard’ function but we should agree on the names/concepts.<br class=""><br class="">Some of the needs are covered in <a href="https://openstack-in-production.blogspot.fr/2016/04/resource-management-at-cern.html" class="">https://openstack-in-production.blogspot.fr/2016/04/resource-management-at-cern.html</a><br class=""><br class="">Tim<br class=""><br class=""><br class="">On 03/08/16 18:47, "Jonathan D. Proulx" <<a href="mailto:jon@csail.mit.edu" class="">jon@csail.mit.edu</a>> wrote:<br class=""><br class=""> Hi All,<br class=""><br class=""> As a private cloud operatior who doesn't charge internal users, I'd<br class=""> really like a way to force users to set an exiration time on their<br class=""> instances so if they forget about them they go away.<br class=""><br class=""> I'd though Blazar was the thing to look at and <a href="http://chameleoncloud.org" class="">Chameleoncloud.org</a><br class=""> seems to be using it (any of you around here?) but it also doesn't<br class=""> look like it's seen substantive work in a long time.<br class=""><br class=""> Anyone have operational exprience with blazar to share or other<br class=""> solutions?<br class=""><br class=""> -Jon<br class=""><br class=""> _______________________________________________<br class=""> OpenStack-operators mailing list<br class=""> <a href="mailto:OpenStack-operators@lists.openstack.org" class="">OpenStack-operators@lists.openstack.org</a><br class=""> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br class=""><br class=""><br class="">_______________________________________________<br class="">OpenStack-operators mailing list<br class=""><a href="mailto:OpenStack-operators@lists.openstack.org" class="">OpenStack-operators@lists.openstack.org</a><br class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators<br class=""></blockquote><br class=""><br class=""><br class="">-- <br class="">Cheers,<br class="">~Blairo<br class=""><br class="">_______________________________________________<br class="">OpenStack-operators mailing list<br class=""><a href="mailto:OpenStack-operators@lists.openstack.org" class="">OpenStack-operators@lists.openstack.org</a><br class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators<br class=""></div></div></blockquote></div><br class=""></div></div></body></html>