History

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-1333: JCLOUDS-1334: JCLOUDS-1470: Require Java 8 and Guava 22	2020-06-25 08:11:30 +09:00
README.md	Update maven coordinates for promoted Azure ARM	2018-01-08 15:11:22 +01: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.md

Azure Compute ARM Provider

Build status for azurecompute-arm module:

Setting Up Test Credentials

Create a Service Principal

Install and configure Azure CLI following these steps.

Using the Azure CLI, run the following commands to create a service principal

# Enter your Microsoft account credentials when prompted
az login

# Set current subscription to create a service principal
az account set --subscription <Subscription-id>

# Create an AD application with your information.
az ad app create --display-name <name> --password <password> --homepage <home-page> --identifier-uris <identifier-uris>

# For example: az ad app create --display-name "jcloudsarm" --password abcd --homepage "https://jcloudsarm" --identifier-uris "https://jcloudsarm"

# Output will include a value for `Application Id`, which will be used for the live tests

# Create a Service Principal
az ad sp create --id <Application-id>

# Output will include a value for `Object Id`, to be used in the next step

Run the following commands to assign roles to the service principal

# Assign roles for this service principal
az role assignment create --role Contributor --assignee <ObjectId>

Look up the the tenant Id

az account show

# output will be a JSON which will include the `Tenant id`

Verify service principal

az login -u <Application-id> -p <password> --service-principal --tenant <Tenant-id>

Run Live Tests

Use the following to run one live test:

mvn -Dtest=<name of the live test> \
    -Dtest.azurecompute-arm.identity="<Application-id>" \
    -Dtest.azurecompute-arm.credential="<password>" \
    -Dtest.azurecompute-arm.endpoint="https://management.azure.com/subscriptions/<Subscription-id>" \
    -Dtest.oauth.endpoint="https://login.microsoftonline.com/<Tenant-id>/oauth2/token"
    integration-test -Plive

Use the following to run all the live tests:


mvn clean verify -Plive \
    -Dtest.azurecompute-arm.identity="<Application-id>"" \
    -Dtest.azurecompute-arm.credential="<password>"" \
    -Dtest.azurecompute-arm.endpoint="https://management.azure.com/subscriptions/<Subscription-id>"" \
    -Dtest.oauth.endpoint=https://login.microsoftonline.com/<Tenant-id>/oauth2/token

How to use it

Azure Compute ARM provider works exactly as any other jclouds provider. Notice that as Azure supports dozens of locations, operations like listImages can be really time-consuming. To limit the scope of such operations there are some additional properties you may want to use:

jclouds.azurecompute.arm.publishers

which is by default Canonical,RedHat

and

jclouds.regions

which is by default null. If you want to target only the north europe region, you can use

jclouds.regions="northeurope"