incubator-libcloud mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrian Cole <>
Subject [libcloud] Fwd: [compute] profile design and reuse of libcloud names where appropriate
Date Fri, 18 Dec 2009 21:25:56 GMT
FYI: this is related to our IRC discussion earlier.


---------- Forwarded message ----------
From: Adrian Cole <>
Date: Fri, Dec 18, 2009 at 1:25 PM
Subject: [compute] profile design and reuse of libcloud names where


On our compute api, it would make discussions easier to use the same vocab
as what is deemed de-facto.  I'd suggest apache incubator status of libcloud
is sufficient grounds to accept their vocab where appropriate.  For this
reason, I recommend we use words like "Node" instead of "Server".  I've
updated our docs accordingly [1]


Ivan and I had a good chat on #libcloud about profiles and naming.  Through
discussion, the bottom line is that Profiles are a good way of resolving
customer asks, which may use cloud-specific lingo, to generic Image, Size,
and Options. They are also a nice way of encapsulating inputs to creation
such that they can be persisted for later use.

  Profile profile = nodeService.resolve(ami("ami-1fd73376"),
instanceType(M1_SMALL), nearRegion(US_EAST));
  for (int i=0;i<10;i++)
      CreateNodeMetadata node = nodeService.createNode(name+i,
profile.getImage(), profile.getSize(), profile.getOptions());

With profiles, we can allow sophisticated, provider-specific configuration
asks to be accessible to the user, while keeping existing interfaces simple.

Let us know your feedback!


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