| Virgo in the cloud (AWS) - provisioning suggestions? [message #913019] |
Fri, 14 September 2012 11:56  |
Eclipse User |
|
|
|
Hi,
I'm designing an OSGI-based application and I'd like to ask opinions on the best way to automatically provision artifacts to several (identical) instances of Virgo running on Amazon EC2.
Ideally, I'd like to create an AMI (Amazon Machine Image) which is a 'bare bones' Virgo install which automatically provisions bundles from a shared repository at startup, perhaps passing the repo info to the instance as a parameter. There will be a number of EC2 instances which need to be identically provisioned. If bundles/plans could be stored in S3 buckets, so much the better.
What's the best approach? Has anyone done something similar before?
I'm currently using VTS but could switch to Virgo Nano Full (I need WAB support) if the P2 provisioning could solve my problem. I intend to build my bundles using Maven/Tycho so deploying to a P2 repo should be ok.
Thanks,
Simon.
|
|
|
| Re: Virgo in the cloud (AWS) - provisioning suggestions? [message #916854 is a reply to message #913019] |
Wed, 19 September 2012 10:56  |
| Eclipse User |
|
|
|
|
You could probably use either a shared Virgo artefact repository and deploy common artefacts, such as plans, on the Virgo servers. Or you could use VNF (which supports WABs) and push the WABs using p2. VNF does not support regions, plans, or PARs, so I guess it depends how much isolation you are looking for.
|
|
|
Powered by
FUDForum. Page generated in 0.02638 seconds
Home