We need to provide some opportunity to manage all leases belonging to one tenant

Registered by Dina Belova

I'm thinking about following use case here:

- there is need to manage some special kind of tenants and expire all VMs belonging to them after some amount of time. Or any other action.

Blueprint information

Dina Belova
Dina Belova
Series goal:
Accepted for 0.x.0
Not started
Milestone target:
milestone icon next
Completed by
Hiroaki Kobayashi

Related branches



As part of project/tenant creation we would like to mark the tenant in such a way that climate will automatically create a lease for the resources. All non-production tenants/projects will be granted a default quota and all resources should have associated leases. Blazar leases will trigger work-flows via notifications. The work-flows defined in mistral will provide automation to achieve some of our non-production capacity management needs. We expect Mistral work-flows to trigger emails, ability for customer to extend lease and finally for the resource to potentially be backed up and then deleted.

We have also considered implementing a non-blazar process to automatically create the leases for all non-production tenants.



I think the use case is OK. But we must also have a blueprint that allow the user to create "Tenant Types" with 'default' lease attributes. Then when creating a tenant, the user can specify lease dates and/or tenant type

Well, I think the placement decisions should rely on the Openstack projects themselves, As said per IRC, I'm thinking of some way of placement like that :
Service (ask for a lease) -> Blazar (check the capacity) -> Scheduling (select good candidates) -> Blazar (creates lease with good candidates, and act on candidates when lease start) -> Service

I got this feedback from Joel:
>> What resources will be considered in this case

Primarily vm/server resources however having object containers, floating IPs and the like also under a lease that expired and was given back to the pool of available resources would potentially be valuable. For us and our need managing just the VM resource is sufficient for the foreseeable future IMO.

>> default quota value that will be granted

This is configured at project/tenant create time and is currently 5 VMs, 5 floating IPs, 200 GB storage.


Work Items

This blueprint contains Public information 
Everyone can see this information.