a third option would be to deploy the micro bosh stemcell on vCloud using a VCD micro bosh stemcell. The micro bosh instance can be configured to communitcate with AWS, so it can talk to wrapper service and you can use it to do a deployment.

Otherwise I'd pick #2 as it is faster to get up and running...

Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
"The question is not if you are paranoid, it is if you are paranoid enough."
On Nov 13, 2012, at 9:04, Shane Witbeck wrote:

I'm working on a service whose goal is to provide a REST/Query-based API for vCloud that is compatible with Amazon EC2 and S3 services. For example, you can use the EC2 cmd line tools to query and operate on vCloud Director.

I'm putting together a demo which will deploy a sample app to vCloud using BOSH.

The basic command flow would be something like:

bosh cli --> AWS micro bosh --> wrapper service --> vCloud Director

There are two approaches I'm considering for this:
deploy the AWS micro bosh and the wrapper service in the same vCD where the demo app will be deployed.
deploy the AWS micro bosh and the wrapper service in AWS and point the service to the target vCD.
#1 seems the more natural solution from the BOSH perspective.
#2 I'm not is possible but saves me from creating my own stemcell/OVF package to upload/install in the vCD.

Due to a very tight deadline, I'm keen to use the most simplistic/fastest approach even if it's somewhat contrived.

What are your opinions on the two approaches above? Is there a third approach which would work better?


Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 8 | next ›
Discussion Overview
groupbosh-users @
postedNov 13, '12 at 5:12p
activeNov 16, '12 at 1:42p



site design / logo © 2021 Grokbase