julienstroheker/acs-engine-client

acs-engine-client's Issues

CI

Package as Electron APP

We have to package the application by following the ACS-Engine releases.

Ex : acs-engine-client v.0.14 will package acs-engine v0.14

We have to package for all the OS (Darwin, Linux and Windows)

Make the _output folder generated from acs-engine available in the client

From #4 we will allow the user to get browse the _output folder to get all the authentication files and see the ARM templates

Deploy the ARM templates generated to Azure

From #4 and using #5 we will deploy to Azure

Generate the ARM template using acs-engine binary

From #3 we will call the acs-engine binary to generate the ARM template by using :

./acs-engine generate config.json

Manage the authentication to an Azure Subscription

Create UI

The MVP should be using only the minimum prerequisites :

• orchestratorType - String - This, will be and support only Kubernetes per default in the MVP
• masterCount - Int - Number of master
• dnsPrefix - String - Prefix
• masterVmSize - Array/String
• agentPool - Array
  • name - Name
  • count - Int
  • vmSize - Array/String
  • availabilityProfile - Array with one value for now : AvailabilitySet (and VMSS in the future)
• adminUsername - String
• sshkeyData - String
• ClientId - String
• PasswordClientId - String

Example for acs-engine :

{
  "apiVersion": "vlabs",
  "properties": {
    "orchestratorProfile": {
      "orchestratorType": "Kubernetes"
    },
    "masterProfile": {
      "count": 1,
      "dnsPrefix": "",
      "vmSize": "Standard_D2_v2"
    },
    "agentPoolProfiles": [
      {
        "name": "agentpool1",
        "count": 3,
        "vmSize": "Standard_D2_v2",
        "availabilityProfile": "AvailabilitySet"
      }
    ],
    "linuxProfile": {
      "adminUsername": "azureuser",
      "ssh": {
        "publicKeys": [
          {
            "keyData": ""
          }
        ]
      }
    },
    "servicePrincipalProfile": {
      "clientId": "",
      "secret": ""
    }
  }
}

Feat : Add Download button for the acs-engine bin

Allow the user to download automatically the acs-engine bin in the ./lib folder

Generate the acs engine JSON file from the UI

From #1 we will generate the acs-engine .json file such as :

{
  "apiVersion": "vlabs",
  "properties": {
    "orchestratorProfile": {
      "orchestratorType": "Kubernetes"
    },
    "masterProfile": {
      "count": 1,
      "dnsPrefix": "",
      "vmSize": "Standard_D2_v2"
    },
    "agentPoolProfiles": [
      {
        "name": "agentpool1",
        "count": 3,
        "vmSize": "Standard_D2_v2",
        "availabilityProfile": "AvailabilitySet"
      }
    ],
    "linuxProfile": {
      "adminUsername": "azureuser",
      "ssh": {
        "publicKeys": [
          {
            "keyData": ""
          }
        ]
      }
    },
    "servicePrincipalProfile": {
      "clientId": "",
      "secret": ""
    }
  }
}