Preparing the Azure Machine Learning Workspace (Part 2 of 2)

By Ashwin Venugopal -

 




To read part 1, please click here




Deploying the Workspace

We can easily set up our first Azure Machine Learning workspace with the help of CLI, as follows:
  • Log in to your Azure environment via the CLI- $ az login, that will open a website with an AAD login screen, and when you return to the console, you will have some information about your AAD tenant, your subscription, as well as your user.

  • However, if you want to check which subscription is active (for more that one subscription), you can use $ az account show --output table command. 

  • Now, after being done with all that, you have to check the situation with the installed extension via $ az extension list command.

  • You should also remove the old version carefully, so that you won't break a script still in use. To do this, you can use $ az extension remove -n azure-cli-ml; or $ az extension remove -n ml commands.

  • Now, you can install the ML extension via  $ az extension add -n ml command,

  • You can look at the help page for the extension  ($ az ml -h).

  • You can also check if anything is missing for the creation of the workspace via  $ az ml workspace create -h command.

  • Now, as a resource group is required which in turn also require a location, we have to look for an available data center location for the Azure cloud with the help of  $ az account list-locations -o table command, which can be used to create the resource group.

  • Finally, if you want to check the deployment at any point, then, you can run $ az ml workspace show -g mldemo -w ml demows command.   








To read part 1, please click here




















































































Comments

Post a Comment

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more