History

Vijay Panghal 79ad45d6b9 Make user agent header configurable Jclouds sends default user agent string with each request to cloud services. But some of the application would like to overide this and send custom user agent instead. This commit define a string property to overide this default user agent string. This property will be applied to all outgoing http request to cloud services JCLOUDS-819		2016-12-20 11:12:53 +01:00
..
src	Make user agent header configurable	2016-12-20 11:12:53 +01:00
README.md	Update profitbricks readme to reflect previous refactoring changes	2016-02-20 01:33:26 +08:00
pom.xml	Next development version 2.0.1-SNAPSHOT	2016-11-15 01:17:08 +01:00

README.md

jclouds ProfitBricks

Terms

Like any cloud provider, ProfitBricks has its own set of terms in cloud computing. To abstract this into jclouds' Compute interface, these terms were associated:

Node - composite instance of Server and Storage
Image - both user-uploaded and provided Images; and Snapshots
Location - DataCenters and Region (Las Vegas, Frankfurt, etc.)
Hardware - number of cores, RAM size and storage size

Getting Started

ComputeService compute = ContextBuilder.newBuilder( "profitbricks" )
					.credentials( "profitbricks email", "password" )
					.buildView( ComputeServiceContext.class )
					.getComputeService();

This works well; however, we won't be able to use jclouds' ability to execute scripts on a remote node. This is because, ProfitBricks' default images require users to change passwords upon first log in.

To enable jclouds to execute script, we need to use a custom image. The easiest way to do this is via ProfitBricks snapshot:

Go to your DCD.
Provision a server + storage, and connect it to the internet. Upon success, you will receive an email containing the credentials needed to login to your server.
Login to your server, and change the password, as requested.

~ ssh root@<remote-ip>
...
Changing password for root.
(current) UNIX password: 
Enter new UNIX password: 
Retype new UNIX password: 
~ root@ubuntu:~# exit

Go back to the DCD, and make a snapshot of the storage. Put a descriptive name.
Configure jclouds to use this snapshot.

Template template = compute.templateBuilder()
	.imageNameMatches( "<ideally-unique-snapshot-name>" )
	.options( compute.templateOptions()
				.overrideLoginUser( "root" ) // unless you changed the user
				.overrideLoginPassword( "<changed-password>" ))
	// more options, as you need
	.build();
	
compute.createNodesInGroup( "cluster1", 1, template );

Limitations

There's no direct way of specifying arbitrary number of cores, RAM size, and storage size via the compute interface, at least until after JCLOUDS-482 is resolved. The adapter uses a predefined list hardware profiles instead.

Take note that these features are still accessible by unwraping the ProfitBricks API, but this'll reduce portability of your code. See Concepts.