azure deployment for matlab production server (payg) -凯发k8网页登录

main content

azure deployment for matlab production server (payg)

to deploy your matlab® production server™ (payg) environment on azure®, launch the matlab production server solution template from the azure marketplace. after the deployment to azure is complete, configure and manage matlab production server by logging in to the matlab production server (payg) dashboard.

for information about deploying matlab production server on azure with a license, see .

note

you must have an azure account to deploy resources on azure and configure your server environment.

you are responsible for the cost of the azure services and resources that the deployment uses.

follow these steps to deploy your server environment on azure.

  1. in the azure marketplace, on the offering page, click get it now. doing so launches the solution template where you provide values to configure your server environment.

  2. provision cloud resources. creating resources on azure can take up to 30 minutes.

  3. connect and log in to dashboard.

to run an application on matlab production server, you need to create the application using matlab compiler sdk™. for more information, see .

provision cloud resources

you must have an azure subscription before you can start deploying cloud resources for matlab production server on azure. launch the matlab production server solution template to configure and deploy cloud resources. the deployment process goes through the following steps. click ok at the end of each step to proceed to the next step.

basics

first, you must choose an azure subscription, specify a resource group to hold the resources you provision, and specify a location to start your resources in.

parameter namevalue
subscriptionchoose an azure subscription to use for purchasing resources.
resource group

choose a name for the resource group to hold the resources.

creating a new resource group for each deployment is recommended. doing so enables you to delete all the resources for each deployment easily.

region

choose the region to start resources in.

select a region that supports your requested virtual machine (vm) instance types. for a list of resources that are supported by region, see .

server

next, you configure the server vm and data persistence. each matlab production server instance runs on a vm and each instance runs multiple matlab production server workers. to deploy a server instance, you must specify parameters for the vm, such as the size, number of vms, and operating system.

parameter namevalue
server vm size

specify the size of the vm to use for the server.

it is recommended that you select a vm size where the number of vcpus on your vm matches the number of matlab production server workers per vm that you plan on using. for example, if you select a d8s v3 vm which has 8 vcpus, use 8 matlab production server workers. you can change the number of workers by updating the number of workers in the settings tab in the matlab production server dashboard. for more information about the property, see .

the template defaults to standard_d4s_v3. this configuration has 4 vcpus and 16 gb of memory. for more information on azure vms, see .

number of server vms

specify the number of vms to run matlab production server instances.

the deployment template sets the default to 2 vms for load balancing.

you can change the number of vms after the initial deployment. for more information, see .

server vm operating system

choose the server vm operating system.

windows® (windows server®) and linux® (ubuntu®) are the only available options.

in most cases, choosing an operating system depends on your personal preference. unless you add operating system-specific dependencies or content such as mex files to your applications, the applications you deploy to the server do not depend on a specific operating system.

create redis™ cache

choose whether you want to create an azure cache for redis.

creating this service allows you to use the persistence functionality of the server. persistence provides a mechanism to cache data between calls to matlab code running on a server instance. for more information, see data caching basics.

you can provision an azure cache for redis after the initial deployment. for setup instructions, see .

dashboard login

after you deploy the server vms, you can manage the server using the matlab production server dashboard, which provides a web-based interface to configure and manage matlab production server in the cloud. specify the login credentials for the dashboard.

parameter namevalue
admin username

specify the administrator user name to log in to the matlab production server dashboard.

admin password

specify the administrator password to log in to the matlab production server dashboard.

network

you can specify which ip addresses can access the dashboard, whether your solution should use a public ip address, and configure a virtual network (vnet).

parameter namevalue
allow connections from ip address

specify the ip address or a range of ip addresses that is permitted to connect to the dashboard that manages the server.

if you specify a range of ip addresses, use cidr notation, which provides the ip address before the slash and mask after the slash. the mask determines the number of ip addresses to include. for example, 10.0.0.1/24.

you can use a cidr calculator to determine the cidr notation for a range of ip addresses.

make solution available over internet

make your solution available over the internet by setting this parameter to yes. this will use public ip addresses.

if you set this parameter to no, the arm template does not assign a public ip address for the vm that hosts the dashboard. to access the dashboard, you can use a different vm located in the same virtual network as the vm that hosts the dashboard.

virtual network

create a new vnet or choose an existing one.

the template defaults to a creating a new vnet with predefined values. these are the values that azure defaults to while creating a new vnet. you can use the default values or enter new values based on your network setup.

the deployment opens the following ports when deploying in a new vnet. if you are using an existing vnet, you need to open the following ports.

  • 443 – required for communicating with the dashboard and the matlab execution endpoint.

  • 8000, 8004, 880, 9090, and 9910 – required for communication between the dashboard, matlab production server workers, and various microservices within the virtual network. these ports do not need to be accessible over the internet.

  • 6520065535 – required for the azure application gateway health check to work. these ports need to be accessible over the internet. for more information, see .

  • 22, 3389 – required for remote desktop functionality for windows or ssh for linux respectively. you can use remote login functionality for troubleshooting and debugging. you can close these ports after deployment is complete.

first subnet

second subnet

specify the subnet name and subnet address prefix for a new or existing subnet.

the first subnet hosts the dashboard. the second subnet hosts the application gateway.

the template defaults to creating new subnets with predefined values. you can use the default values or enter new values based on your network setup.

ssl certificate

in this section, you specify an ssl certificate for the azure application gateway to use. the application gateway provides an https endpoint that you use to connect to server instances and the matlab production server dashboard.

parameter namevalue
pfx certificateupload a pfx-formatted ssl certificate.
pfx certificate passwordif the certificate requires a password, enter it here. otherwise, leave the field blank.

connect and log in to dashboard

the matlab production server dashboard is a web-based interface to configure and manage matlab production server in the cloud.

note

the internet explorer® web browser is not supported for interacting with the dashboard.

complete these steps only after you successfully create your resource group. if your solution uses private ip addresses, you can connect to the dashboard from a vm located in the same virtual network as the vm that hosts the dashboard.

  1. in the azure portal, click resource groups.

  2. select the resource group that you created for this deployment.

  3. select deployments from the left pane. in the pane that opens, click microsoft.template.

  4. select outputs from the left pane.

  5. copy the parameter value for dashboardurl and paste it in a browser.

  6. use the administrator user name and password that you specified in the dashboard login step of the deployment process to log in.

configuring role-based access control for the dashboard is recommended. matlab production server integrates with oauth 2.0 providers such as microsoft® azure active directory, google® identity, and pingfederate® for providing role-based access control. role-based access control lets you grant users the privileges to perform tasks on the dashboard and server, based on their role. for more information on how to configure role-based access control, see .

related topics

    网站地图