stack.org>>
Date: miércoles, 26 de febrero de 2014 01:06
To:
"openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Keystone] Tenant expiration dates
On 02/24/2014 08:41 AM, D
On 02/24/2014 08:41 AM, Dina Belova wrote:
Cristian, hello
I believe that should not be done in such direct way, really.
Why not using project.extra field in DB to store this info? Is that
not appropriate for your ideas or there will be problems with there
implementing using extras?
It wou
Cristian, hello
I believe that should not be done in such direct way, really.
Why not using project.extra field in DB to store this info? Is that not
appropriate for your ideas or there will be problems with there
implementing using extras?
Thanks,
Dina
On Mon, Feb 24, 2014 at 5:25 PM, Sanchez,
Hi,
I’m thinking about creating a blueprint to allow the creating of tenants
defining start-date and end-date of that tenant. These dates will define a time
window in which the tenant is considered ‘enabled’ and auth tokens will be
given only when current time is between those dates.
This can be
