On 8/3/2016 11:47 AM, Jonathan D. Proulx wrote:
Hi All,
As a private cloud operatior who doesn't charge internal users, I'd
really like a way to force users to set an exiration time on their
instances so if they forget about them they go away.
I'd though Blazar was the thing to look at and
On Thu, Aug 04, 2016 at 09:59:15AM +0200, Álvaro López García wrote:
:For the record, we proposed a spec [1] on this long ago (actually, 1
:year ago).
:
:[1] https://review.openstack.org/#/c/104883/
:
:Your input is much welcome!
Thanks for the pointer, actually looks like you put in patch set
Take a look on manageiq.
Em 03/08/2016 17:50, "Jonathan D. Proulx" escreveu:
> Hi All,
>
> As a private cloud operatior who doesn't charge internal users, I'd
> really like a way to force users to set an exiration time on their
> instances so if they forget about them they
On 03 Aug 2016 (17:23), Tim Bell wrote:
>
> When I last looked, Blazar allows you to reserve instances for a given time.
> An example would be
>
> - We are organizing a user training session for 100 physicists from Monday to
> Friday
> - We need that each user is able to create 2 VMs within a
See inline.
Sent from my iPad
> On Aug 3, 2016, at 8:49 PM, Sam Morrison wrote:
>
>
>> On 4 Aug 2016, at 3:12 AM, Kris G. Lindgren wrote:
>>
>> We do something similar. We give everyone in the company an account on the
>> internal cloud. By
Yes, at Overstock our users don't provision instances directly out of horizon
or nova. They use an orchestration tool we wrote in Django which among other
things tracks a lease time, warns users about expiration, allows them to extend
etc. Works great for us, but the same approach may not
We discussed Blazar fairly extensively in a couple of recent
scientific-wg meetings. I'm having trouble searching out right the irc
log to support this but IIRC the problem with Blazar as is for the
typical virtualised cloud (non-Ironic) use-case is that it uses an
old/deprecated Nova API
On 4 August 2016 at 12:48, Sam Morrison wrote:
>
>> On 4 Aug 2016, at 3:12 AM, Kris G. Lindgren wrote:
>>
>> We do something similar. We give everyone in the company an account on the
>> internal cloud. By default they have a user- project. We have
> On 4 Aug 2016, at 3:12 AM, Kris G. Lindgren wrote:
>
> We do something similar. We give everyone in the company an account on the
> internal cloud. By default they have a user- project. We have a
> Jenkins job that adds metadata to all vm’s that are in user-
quirements at individual service level.
Regards~Hrushi
-Original Message-
From: Jonathan D. Proulx [mailto:j...@csail.mit.edu]
Sent: Wednesday, August 03, 2016 12:22 PM
To: Tim Bell <tim.b...@cern.ch>
Cc: openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] Blaza
On Wed, Aug 03, 2016 at 05:23:23PM +, Tim Bell wrote:
:
:When I last looked, Blazar allows you to reserve instances for a given time.
An example would be
:
:- We are organizing a user training session for 100 physicists from Monday to
Friday
:- We need that each user is able to create 2 VMs
When I last looked, Blazar allows you to reserve instances for a given time. An
example would be
- We are organizing a user training session for 100 physicists from Monday to
Friday
- We need that each user is able to create 2 VMs within a single shared project
(as the images etc. are set up
We do something similar. We give everyone in the company an account on the
internal cloud. By default they have a user- project. We have a
Jenkins job that adds metadata to all vm’s that are in user- projects. We then
have additional jobs that read that metadata and determine when the VM
Hi All,
As a private cloud operatior who doesn't charge internal users, I'd
really like a way to force users to set an exiration time on their
instances so if they forget about them they go away.
I'd though Blazar was the thing to look at and Chameleoncloud.org
seems to be using it (any of you
14 matches
Mail list logo