jclouds/skeletons/standalone-compute
gurkerl83 32f6c4d50f Remove the OSGi configuration from each module. The approach of defining OSGi configuration through common properties and serving them to the bundle plugin gets no longer used; instead, OSGi configuration gets defined in each module's dedicated bnd file. 2020-10-26 19:58:41 +09:00
..
src JCLOUDS-1225: Address Guava 18 Objects changes 2017-08-22 17:12:53 -07:00
README.txt JCLOUDS-31. remove malformed, duplicate, or unnecessary headers 2013-05-16 21:30:32 -07:00
bnd.bnd Onboard bnd-configuration files, one per module 2020-10-26 19:58:41 +09:00
pom.xml Remove the OSGi configuration from each module. The approach of defining OSGi configuration through common properties and serving them to the bundle plugin gets no longer used; instead, OSGi configuration gets defined in each module's dedicated bnd file. 2020-10-26 19:58:41 +09:00

README.txt

this is a skeleton for a standalone compute provider.

Essentially, a standalone provider is one that doesn't use jclouds http services.  Examples could be native drivers like libvirt or shell-driven ones like virtualbox.