select a particular instance type through Brooklyn blueprint

[Gowri LN <go...@gmail.com>]

Hi,

I am trying to launch a simple VM on AWS using Brooklyn . I used the
following blueprints:
 Blueprint1:

name: simple-vm
> location:
>   jclouds:aws-ec2:us-west-1
> services:
> - type: brooklyn.entity.basic.EmptySoftwareProcess
>   name: VM
>   provisioning.properties:
>     minRam: 1024mb
>     minCores: 4
>     minDisk: 1gb


Blueprint 2:

name: simple-vm
> location:
>   jclouds:aws-ec2:us-west-1
> services:
>  - type: brooklyn.entity.basic.EmptySoftwareProcess
>    name: VM
>    provisioning.properties:
>      minRam: 1024mb
>      minCores: 4
>      minDisk: 0



Brooklyn  launched  ubuntu instance  for both the blueprints but it
selected m1.small flavour of instance.

How does the image selection logic work? why did it not select other
instance types ( say t2.micro) for blueprint 2 ?

 or in other words

 How can I specify the instance flavours through blueprints ? ( By flavour
I mean AWS Instance types)

Can someone please provide link to the documentation which has details of
this ?

Thanks,

Re: select a particular instance type through Brooklyn blueprint

[Andrea Turli <an...@cloudsoftcorp.com>]

Hi Gowri,

Apache Brooklyn uses Apache jclouds to provision VMs in the cloud. You need
to take into account the following two concepts:
- image
- hardwareSpec

In Brooklyn using YAML blueprint you can specify a particular image
using `imageId: eu-west-1/ami-3bbaa54f` (to target CentOS 6.4 x64 HVM) and
you can specify a particular hardwareSpec using `hardwareId: m3.medium`
Of course, using hardwareId or imageId are specific to the cloud provider
you are targeting.

You may want to have a more portable blueprint (cloud-independent) by
specifying something like

provisioning.properties:
  minRam: 1024mb
  minCores: 4
  osFamily: centos
  # or something like
  imageNameRegex=CentOS_66_x64

to be able to provision a centos VM with at least 4 CPU cores and 1 GB RAM
in whatever location supported.
For more information you can have a look at all the properties supported at
[1]

HTH,
Andrea

[1]:
https://github.com/apache/incubator-brooklyn/blob/9595ddc943fa9cb00f86a20e030cffd07bded69b/locations/jclouds/src/main/java/brooklyn/location/jclouds/JcloudsLocationConfig.java





On 2 June 2015 at 14:32, Gowri LN <go...@gmail.com> wrote:

> Hi,
>
> I am trying to launch a simple VM on AWS using Brooklyn . I used the
> following blueprints:
>  Blueprint1:
>
> name: simple-vm
> > location:
> >   jclouds:aws-ec2:us-west-1
> > services:
> > - type: brooklyn.entity.basic.EmptySoftwareProcess
> >   name: VM
> >   provisioning.properties:
> >     minRam: 1024mb
> >     minCores: 4
> >     minDisk: 1gb
>
>
> Blueprint 2:
>
> name: simple-vm
> > location:
> >   jclouds:aws-ec2:us-west-1
> > services:
> >  - type: brooklyn.entity.basic.EmptySoftwareProcess
> >    name: VM
> >    provisioning.properties:
> >      minRam: 1024mb
> >      minCores: 4
> >      minDisk: 0
>
>
>
> Brooklyn  launched  ubuntu instance  for both the blueprints but it
> selected m1.small flavour of instance.
>
> How does the image selection logic work? why did it not select other
> instance types ( say t2.micro) for blueprint 2 ?
>
>  or in other words
>
>  How can I specify the instance flavours through blueprints ? ( By flavour
> I mean AWS Instance types)
>
> Can someone please provide link to the documentation which has details of
> this ?
>
> Thanks,
>