brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Corbett <>
Subject JcloudsLocation behaviour
Date Thu, 11 Jun 2015 11:24:16 GMT
Hi all,

A couple of ideas for JcloudsLocation.

I'd like to make it possible to incorporate existing machines into Brooklyn
as Jclouds locations rather than bring-your-own-node locations. To do this
I'd like to add a new config key, named something like "provision mode".
Valid options are:
* obtain: The current behaviour. Always provisions a new machine.
* rebind: Attempt to rebind to an existing machine using the location
properties and entity's provisioning properties. Fail if no suitable
machine is found.
* rebind or obtain: As rebind but calling `obtain` rather than failing if
no existing machine is found.

Deployments would fail if an existing machine was found but Brooklyn cannot
connect to it.

To aid the rebind cases I would add a second config key that sets the
predicate used to determine whether an existing machine should be used. The
current predicate
cross-checks IDs and hostnames. An obvious extension would be to look at a
machine's tags.

I think this would be beneficial for users that want to bring existing
systems under Brooklyn's control.

Second, when stopping entities is there any way to distinguish between
stopping and destroying their locations? The stop effector currently
accepts "stopProcessMode" and "stopMachineMode" arguments. I'm wondering if
there's a case for a third argument named "destroyMachineMode" (with values
always/never/if-not-stopped) that allows the caller to distinguish between
suspending and destroying instances.

Any thoughts?



Cloudsoft Corporation Limited, Registered in Scotland No: SC349230. 
 Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
This e-mail message is confidential and for use by the addressee only. If 
the message is received by anyone other than the addressee, please return 
the message to the sender by replying to it and then delete the message 
from your computer. Internet e-mails are not necessarily secure. Cloudsoft 
Corporation Limited does not accept responsibility for changes made to this 
message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of 
viruses, it is the responsibility of the recipient to ensure that the 
onward transmission, opening or use of this message and any attachments 
will not adversely affect its systems or data. No responsibility is 
accepted by Cloudsoft Corporation Limited in this regard and the recipient 
should carry out such virus and other checks as it considers appropriate.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message