Announcing the winners & finalists of the Dataiku Frontrunner Awards 2021! Read their inspiring stories

Usage of existing VNET in Azure by Fleet Manager

0 Kudos

As part of recent Fleet Manager installation, it transpired that it can only make use new VNET and subnet subsequently. How about if we are to leverage existing VNET that the organisation has already?

Also, IP address of Fleet Manager is chosen as first IP of that subnet provided in ARM template. Per my understanding, the following points need to be looked into and they are as follows.

  •  More flexibility on choosing IP address for Fleet Manager in ARM template. For example, an administrator should have the option to specify the IP of Fleet Manager. 
  • Once Fleet Manager installation is done, IP address of each DSS instances such as Designer Node, Deployer, Automation Node can also be specified by an administrator in Fleet Manager console. 

Benefits:

  • As prerequisite, an architect will be able to fix IP addresses to each nodes.
  • In Azure, network routing can also be taken care of before installation.
  • DNS entries will be done well before.
  • Firewall rules  need to be there. 

If we set up network before Fleet Manager installation, it would be more friendly to an Azure architect.