Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

1. Request core and storage quota from Azure

...

For information on requesting core and storage quotas, see the Azure solutions documentation, or contact Azure Support.

2.

...

Install the Azure

...

CLI 

After completing step 1, you will need to install the CLI module for Azure , using command line instructions with a tool such as Terminal. For more informationdetails, see the npm Azure page Install the Azure CLI on Linux.

To download and install

...

the Azure CLI, do the following:
  1. If you don’t have Node.js or npm installed on On your Ubuntu system, open a Terminal window and use the following command. For Mac and Windows systems, go to the npm Azure package tutorialfollow the instructions found here: How to install the Azure CLI.

Code Block
$  curl -sL https://debaka.nodesource.comms/setupInstallAzureCLIDeb | sudo -E bash -

2. Use the following command to get the latest nodejs package.

Code Block
$  sudo apt-get install -y nodejs

3. Now you can download the Azure CLI NPM module and navigate to the node_modules/azure-cli/bin directory.

Code Block
$  npm install azure-cli
$  cd node_modules/azure-cli/bin

3. Log in to

...

Azure and (optionally) set your subscription

After installing the Azure CLI, log into your Azure subscription to complete the remaining steps.

To log in to

...

Azure

...

, do the following:
  1. In the Terminal window, use the following command to initiate logging into your Azure subscription.

Code Block
node_modules/azure-cli/bin$ ./azure login
info:    Executing command$  az login

2. Use a web browser to open the page https://akamicrosoft.mscom/devicelogin.

3. Enter the displayed code to authenticate. In the following example, the subscription code is hidden.

Code Block
EnterTo sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code ######### to authenticate.

4. The following response is shown. In the following example, the subscription code is hidden.

Code Block
-info:   Added subscription ----------------
info:    Added subscription -----------------
+
info:    login command OK

5. Set the the configuration to use ARM.

Code Block
node_modules/azure-cli/bin$ ./azure config mode arm
info:    New mode is arm
OPTIONAL: If your account manages multiple Azure subscriptions, do the following:

4. After you have logged in, list all Azure subscriptions you have access to. Make a note of the SubscriptionId for the subscription you will be using to set up Scuba.

Code Block
$  az account list

5. With the SubscriptionId from above, use the following command to set which subscription you will be using for the remainder of this guide.

Code Block
$  az account set -s <SubscriptionId>

4. Create an application and service principle

In this task Next, you will create an application ( for Scuba ) with a client secret (password), and then use the AppID to create a service principle.

...

  1. To create an application (for Scuba), use the following command. Make a note of the AppID the password you input, and the AppID ("id") that is displayed, for use in the next step.

Code Block
breakoutModewide
node_modules/azure-cli/bin$ ./azure$  az ad app create --display-name "Scuba" --home-page "https://www.scuba.io" -i "http://www.scuba.io/" --password "<replace_with_random_password>"
+ Creating application Scuba                                               
data:    AppId:                   [A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]
data:    ObjectId:                ecf07ff3-8058-45ed-9947-a21479eb2d03
data:    DisplayName:             Scuba
data:    IdentifierUris:          0=http://www.scuba.io/TENANT_NAME
data:    ReplyUrls:             
data:    AvailableToOtherTenants:  False
data:    AppPermissions:      
data:                             claimValue:  user_impersonation
data:                             description:  Allow the application to access Scuba on behalf of the signed-in user.
data:                             directAccessGrantTypes:
data:                             displayName:  Access Scuba
data:                             impersonationAccessGrantTypes:  impersonated=User, impersonator=Application
data:                             isDisabled:
data:                             origin:  Application
data:                             permissionId:  aed80878-75f0-43db-acd5-57a9d2ffe046
data:                             resourceScopeType:  Personal
data:                             userConsentDescription:  Allow the application to access Scuba on your behalf.
data:                             userConsentDisplayName:  Access Scuba
data:                             lang:
info:    ad app create command OK

2. Create a Service Principle using the AppId from the previous step. Make a note of the Object Id ObjectId that is displayed, for when you create a role in the next section.

Code Block
node_modules/azure-cli/bin$ ./azure ad sp create [A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]
info:    Executing command$  az ad sp create + Creating service principal for application [A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]
data:    Object Id:               39b17ad6-ce3d-unique-ObjectId-558c54dcdc42
data:    Display Name:            Scuba
data:    Service Principal Names:
data:                             0892eb09-2dc0-4010-8620-0eeb9a8db7cf
data:                             http://www.scuba.io/TENANT_NAME
info:    ad sp create command OK-id <AppId>

5. Create a role and show the account

In this task Finally, you will create a role using the Object ID ObjectId generated in the previous section, then show the account information.

To create a role and show the account, do the following:

1. To create a role, enter the following

...

command using the ObjectId generated when you created a Service Principle in the previous section.

Code Block
node_modules/azure-cli/bin$ ./azure$  az role assignment create --objectId 39b17ad6-ce3d-unique-ObjectId-558c54dcdc42 -o Owner -c /subscriptions/[A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]
 
info:    Executing command role assignment create
+ Finding role with specified name                                            
-data:   RoleAssignmentId    : /subscriptions/[A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]/providers/Microsoft.Authorization/roleAssignments/f4ee00a7-a147-49a3-bad3-41d9cc838a25
data:    RoleDefinitionName   : Owner
data:    RoleDefinitionId     : 8e3af657-a8ff-443c-a75c-2fe8c4bcb635
data:    Scope                : /subscriptions/[A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]-[A-Z+a-z+0-9]
data:    Display Name         : Scuba
data:    SignInName           :
data:    ObjectId             : 39b17ad6-ce3d-unique-ObjectId-558c54dcdc42
data:    ObjectType           : ServicePrincipalrole "Owner" --assignee-object-id <ObjectId> --scope /subscriptions/<SubscriptionId>

2. To show the details of the your Azure account, log in to the VM and enter the following command. Make a note of the TenantId in the Tenant IDoutput.

Code Block
(bastion)youuser@ubuntu14-vm:~/scuba/node_modules/azure-cli/bin$ ./azure account show
info:    Executing command account show
data:    Name                        : Microsoft Azure Internal Consumption
data:    ID                          : d725682b-your-unique-id-19a9cedeb659
data:    State                       : Enabled
data:    Tenant ID                   : 72f988bf-unique-tenant-id-2d7cd011db47
data:    Is Default                  : true
data:    Environment                 : AzureCloud
data:    Has Certificate             : No
data:    Has Access Token            : Yes
data:    User name                   : v-youuser@microsoft.com
data:   
info:    account show command OK$  az account show

6. Submit information to provision a Scuba cluster

This task outlines Now that you have set up and configured your Azure subscription, you have all of the information you need gather and submit need submit to Scuba to provision a new cluster in Azure. 

...

  1. The App Id that you generated when you created an application (in step 4).

  2. The Application Secret that you specified when you created an application (in step 4).

  3. The Tenant ID Id that you generated when showing the account (in step 5).

  4. The Region in which the cluster is to be deployed.

  5. The Subscription IDId, from your Azure Portal.

  6. Cluster sizing defined with your Scuba implementation team, while Planning your Scuba deployment.

  7. Core and Storage quota you requested from Azure, such as:

    1. Quantity of VM Types with respective region:
      [Example: 500 cores,  D3s, East US 2]
      [Example: 100 cores, A7s, Central US]

...

  • Date of core fulfillment:

  • Request is temporary (Yes/No)? If yes, include the details.

  • Bursting usage pattern (Yes/No)? If yes, include the details.

  • With which team and service do you belong:

  • Business Justification: 

  • Amount of Premium Storage in GB or TB: 

What's Next

The Scuba team will deploy and configure your new cluster once we have the above information. After the cluster is deployed, you are ready to add data.