Integration with Microsoft Windows Azure Pack

From ISPWiki
Revision as of 20:13, 13 October 2016 by Ksenya (talk | contribs) (Tariff configuration)
Jump to: navigation, search

Installing the module

Before you start, you need to purchase a license for the module in your Client area, and assign it to your BILLmanager license. Please note: integration is supported only in BILLmanager Corporate.

Installation will be made automatically in Processing modules -> Created-> Virtual data-center -> Windows Azure Pack


You will need two servers for integration:

  1. The first server with BILLmanager 5 Corporate;
  2. The second one in "private" network Windows Azure Pack for Windows Server 2012.

Proxy server configuration

  1. Download the installer of proxy server to the second server;
  2. Extract data from the archive;
  3. Run the WapHttpServer.msi file and follow the steps of the Setup wizard;
  4. On the 4th step fill out the following form:
Module configuration

Service configuration

  1. Admin authentication site - URL of the authentication site (usually on port 30071);
  2. Administrator API - URL to Administrator API (usually on port 30004 );
  3. API Host - address of the host that will listen to the service;
  4. API Port - port that will listen to the service;
  5. SQL connection string - SQL Server connection string.
The following operations will be performed during setup:
- The system will add a new Firewall rule to allow access to the service on the port specified during setup;
- After all files are copied, the service will be restarted, and a self-signed certificate will be created if HTTPS protocol will be used. See configuration details for API host;

Manual configuration

In order to change parameters of the already configured service, complete the following steps:

  1. Navigate to Start -> Control Panel -> View Local Service in the window that will open find ISPsystem Service, press it with t нажимаем на него правой кнопкой мыши and select Stop;
  2. Go to the directory with installed application and find HTTPServer.exe.conf:
<?xml version="1.0" encoding="utf-8" ?>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5.2" />
    <add key="windowsAuthEndpoint" value="" />
    <add key="adminApiEndpoint" value=""/>
    <add key="apiCertificate" value="ISPsystem REST API Certificate"/>
    <add key="apiPort" value="8080"/>
    <add key="apiHost" value="https://localhost"/>
    <add key="startUser" value="Administrator"/>
    <add name="WapMembershipDatabase" connectionString="Data;User Id=SA;Password=password; Initial Catalog=Microsoft.MgmtSvc.PortalConfigStore;" />
    <membership defaultProvider="SqlProvider" hashAlgorithmType="HMACSHA256">
      <clear />
      <add name="SqlProvider" 
passwordFormat="Hashed" />

Configuration file parameters:

  1. windowsAuthEndpoint - URL of the authentication site;
  2. adminApiEndpoint - URL to Administrator API;
  3. apiCertificate - name of the certification for connection through HTTPS;
  4. apiPort - address of the host that the service will use;
  5. apiHost - port that the service will use;
  6. WapMembershipDatabase - SQL Server connection string.
Once completed, in the View Local Service window select  ISPsystem Service and right click Start.

Processing module configuration

In order to integrate BILLmanager 5 with Windows Azure Pack, navigate to Processing module -> Create -> Virtual data-center -> Microsoft Windows Azure Pack

Processing module parameters (see vCloud configuration):

  • URL ISPsystem API - URL to ISPsystem Service see above;
  • Username - username to access Administrator API;
  • User password - password to accessAdministrator API;
  • Windows domain name - name of the Windows domain, where the above user is located;
  • User management portal - link to the Windows Azure Pack user portal.

Tariff configuration

In order to create and configure a tariff plan for Azure Pack, you will need to complete the same steps as for configuring other tariff plans in the billing system. Please note:

  1. A virtual data-center template should contain the plan's name as it specified in Windows Azure Pack
  2. Add-ons can refer to one of general add-ons or set limits on a specific resource
  3. Add-ons that specify subscription on general add-ons looks like the following: дополнений задающих подписку на общие дополнения выглядит следующим образом:
    • Целочисленные дополнения определяют подписку на общее дополнение, в случае, если у дополнения задано служебное наименование совпадающее с именем общего дополнения и заказано не нулевое значение ресурса
    • Логические дополнения определяют подписку на общее дополнение, в случае, если у дополнения задано служебное наименование совпадающее с именем общего дополнения и дополнение заказано
    • Add-on, which is specified as enumeration, will define subscription for general add-on, if the internal name of the element matches the name of the general enumeration заданное перечислением определяет подписку на общее дополнение, в случае если внутреннее наименование заказанного элемента перечисления совпадает с именем общего дополнения
  4. Other tariff add-ons enable you to manage resources allocated to the virtual data-center and will be combined into a personal add-on for subscription. Currently, the following add-ons with internal names can be processed: дополнения к тарифному плану позволяют регулировать ресурсы выделяемые на виртуальный дата-центр и консолидируются в персональное дополнение к подписке. На данный момент обрабатываются дополнения заданные типами со следующими внутренними именами:
    • ncpu - number of virtual processors per data-center
    • flat - общая полоса пропускания на дата-центр
    • mem - amount of RAM per data-center
    • disc - amount of disk space in data-center
    • privatenet - number of private networks per data-center
    • extip - maximum number of public IP addresses per data-center
    • vmlimit - maximum number of virtual servers per data-center
    • vpntunnel - maximum number of VPN tunnels

For more flexible configuration of the tariff plan, you can use add-ons which allows clients to choose add-ons, based on ordered values of other add-ons, and policies, which allow to upgrade/downgrade ordered resources тарифного плана можно использовать дополнения с учетом по выбору клиента, с расчетов на основе заказанных значений других дополнений, а так же политики понижения и повышения объема заказанных ресурсов