Is it possible to get the micro images for AWS

[Blair]

I live on the West Coast and very often the East Coast Cloud has
extremely high latency. i would love to just make the existing micro
level CloudBioLinux images available to everyone here is it possible
to get ahold of the latest one? Or if not what is the process to
create a micro instance?

Thanks,

Blair

[Enis Afgan]

Hi Blair, 

Amazon does not support a way for machine images to span or be transfered from one region to another. So, you would have to build a new image using cloudbiolinux scripts in the US-West region. Once the image is built for the given region, you can use it with any type of instance.

The instructions on how to build an image are available here (see section: Building an image from scratch using CloudBioLinux): https://github.com/chapmanb/cloudbiolinux

cheers,

Enis

--
You received this message because you are subscribed to the Google Groups "cloudbiolinux" group.
To post to this group, send email to cloudb...@googlegroups.com.
To unsubscribe from this group, send email to cloudbiolinu...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/cloudbiolinux?hl=en.

[Blair]

Hi Enis

 

Well I tried to use the instructions and well they keep wanting to create a full Cloud Instance with GUI and everything else I've made a BioNode using Unbuntu 12.04 (the lastest and will make it

available to everyone in the  next day or two at least for the west coast of the USA). But CloudBioLinux is not quite what I want. I want a compute group that can do all of the heavy work and leave the

real work to me and my local machine (an i7).

 

Thanks,

 

Blair 

[Pjotr Prins]

Hi Blair,

On Sun, May 6, 2012 at 3:26 AM, Blair <blair.j...@gmail.com> wrote:

Hi Enis

 

Well I tried to use the instructions and well they keep wanting to create a full Cloud Instance with GUI and everything else I've made a BioNode using Unbuntu 12.04 (the lastest and will make it

available to everyone in the  next day or two at least for the west coast of the USA). But CloudBioLinux is not quite what I want. I want a compute group that can do all of the heavy work and leave the

real work to me and my local machine (an i7)

that is intriguing.  I am one of the creators of BioNode, and, in fact, we merged with CBL last summer. You can create a BioNode using CBL flavors, as described here (for a minimal flavor):

  https://github.com/pjotrp/cloudbiolinux/blob/master/doc/hacking.md

and

  https://github.com/pjotrp/cloudbiolinux/tree/master/contrib/bionode

The default CBL builds all packages (indeed). Flavors have been developed so you can do a subset, by selection packages in a YAML file, i.e.

  https://github.com/pjotrp/cloudbiolinux/blob/master/contrib/bionode/main.yaml

and configuration defined with

  https://github.com/pjotrp/cloudbiolinux/blob/master/contrib/bionode/fabricrc_bionode.txt

It is all really straightforward (kudos to Brad for that). And because it is Python and YAML it is quite hackable. The reason we have merged with BioNode is to be able to share development resources. Once you define your own flavor, you benefit from the work that is being done on CBL.

The only thing I don't like about CBL is that Cloudman, a separate target, has a high integration with CBL code - I think that is unnecessary. Cloudman should be designed as a CBL flavor.

With time I am building more installations using CBL flavors. I plan to add support for Chef or Cfruby (the latter I also created myself) as a post-install facility. These tools are being used, but are as yet not integrated as an option. But other than that, if you see CBL as a flexible VM builder, CBL delivers the goods on many platforms.

If you invest in CBL, it will pay off in time. That is my experience.

Pj.

[Enis Afgan]

Pjotr,

The only thing I don't like about CBL is that Cloudman, a separate target, has a high integration with CBL code - I think that is unnecessary. Cloudman should be designed as a CBL flavor.

I just issued a pull request to Brad which will make installation of CloudMan configurable via main.yaml config script, so that should make it easy enough to omit if you're not actually using this to build images on the cloud. The rationale for integrating CloudMan with CBL is that with CloudMan you're actually able to use the scalability of the cloud vs. being confined to a single machine. Therefore, CloudMan is really a service and not an end result and thus I do not think it would make sense to have it as a flavor. Anyhow - it should be easy enough to omit it from an install from now on.

Cheers,

Enis