none
Managing Microsoft R Server configuration RRS feed

  • Question

  • Hi,

    We are currently investigating the use of Microsoft R Server (Linux) to deploy and publish R scripts as a REST API. Coming from a Linux background however, I'm not too sure how administrators manage the configuration of their installation(s). I was wondering if anybody could share their preferred workflow for installing and configuring Microsoft R Server automatically. 

    Coming from a Linux background, I would expect everything to be configurable through config files. However, I can't find any documentation on the available files and their options. For example, how could I automate configuring the ports for the different services, or the users and their passwords without relying on the admin utility (Microsoft.DeployR.Utils.AdminUtil/Microsoft.DeployR.Utils.AdminUtil.dll)?

    We use Puppet for all our configuration management needs, but I can't seem to figure out if we could apply the same techniques to R Server?

    Thank you for any insights you could provide.

    Best regards,
    Steven


    Thursday, January 12, 2017 6:53 PM

Answers

  • Hi Steve!

    R server operationalization is based on dotnet core and stores it's configuration in a appsettings.json configuration file.

    see (https://msdn.microsoft.com/en-us/microsoft-r/operationalize/admin-get-started)

    User configuration is managed via either LDAP or Azure Active directory. You should be able to use Puppet to configure an LDAP server. See

    https://msdn.microsoft.com/en-us/microsoft-r/operationalize/security-authentication

    to describe how to configure R server operationalization to authenticate with LDAP.

    R server has systemd and upstart service configuration files to make it easy to run the Web and compute nodes.

    Hope this helps,

    Colin

    Thursday, January 12, 2017 10:53 PM

All replies

  • Hi Steve!

    R server operationalization is based on dotnet core and stores it's configuration in a appsettings.json configuration file.

    see (https://msdn.microsoft.com/en-us/microsoft-r/operationalize/admin-get-started)

    User configuration is managed via either LDAP or Azure Active directory. You should be able to use Puppet to configure an LDAP server. See

    https://msdn.microsoft.com/en-us/microsoft-r/operationalize/security-authentication

    to describe how to configure R server operationalization to authenticate with LDAP.

    R server has systemd and upstart service configuration files to make it easy to run the Web and compute nodes.

    Hope this helps,

    Colin

    Thursday, January 12, 2017 10:53 PM
  • Hi Colin,

    Thank you, the appsettings.json was exactly what I was looking for! That should make it all work together nicely.

    One final question, do you have any idea how the AdminPassword entry is generated in appsettings.json?

    Thanks for your help!

    Best regards,
    Steven

    <style type="text/css">p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Menlo; color: #f9f9f9; background-color: #272727} span.s1 {font-variant-ligatures: no-common-ligatures} </style>
    Friday, January 13, 2017 5:57 PM
  • The admin password is based on a salted password, hashed with Pbkdf2 and stored in base 64.

    If you're deploying with automation, you should configure an LDAP set up - the AdminPassword is ignored if LDAP is configured, and it will support using different usernames versus only `admin'. There is no functionality difference between different accounts.

    Tuesday, January 17, 2017 8:10 PM