influxdata / azure-resource-manager-influxdb-enterprise Goto Github PK

Azure Marketplace

Need to update the configuration to reflect the known best practices for a influxDB cluster
(TSi, Flux, etc)

In our current Azure marketplace template, we create a new subnet with specific private ipAddress prefixes. We need to update the deployment to allow customers to select/reuse their own subnets.

Currently creating a new Telegaf config for the enterprise nodes, however there is a pre-created config file included in the image default. Better approach to use this config.

Perform basic level load testing on cluster Azure template deployment

• using inch

Refactor the cluster configuration script to use DNS

We want to create a new VM offer in the partner portal and enable the free trial option across several regions

Hi,

Need help on error below:

Thanks!

Document links on the Azure marketplace are using the latest breadcrumb anchor tag. This will make the link always point to the latest docs but the images are still fairly static. v1.7.10 is the current marketplace image.

Need to update the PlatformFaultDomainCount value in the datanodes VM template. Default incorrectly set to 3.

List of TODO items for the ARM templates:

• Review networking and resource templates are correct. @chobbs
• Add secondary volumes InfluxDB on data and meta nodes. @chobbs
• Add in hostnames. @chobbs
• Add in Azure extension scripts for setup. @chobbs
• Template testing and infrastructure review. @gunnaraasen
• Template & conf scripting updates and modification. @gunnaraasen/ @chobbs
• Review high-level architecture. @gunnaraasen

Need to included support for multiple Azure Availability Zones for the InfluxEnterprise template

The partner center in Azure has an option to enable a "test-drive" of the application deployment. Need to investigate how to enable and what it means

Marketplace enterprise templates current on allow deployment in the following locations:

            "westus",
            "eastus",
            "eastus2",
            "centralus",
            "southcentralus",
            "northcentralus",
            "eastasia",
            "southeastasia",
            "westeurope",
            "northeurope"

Need to add deployment resources to support https, for Azure only Application Gateway is available.

Suggest setting the default access points of loadbanacer and chronograf enabled to the most secure options.

Need a architectural description on how InfluxDB Enterprise is set up describing what the data nodes are, what are the meta nodes, what is placed behind the load balancer.

Now that we changed the vm naming convention, we will need to change these names in the cluster-configure.sh script so that the script can properly join() the newly named meta/data nodes.

License type needs to be properly set in the configuration file:

[enterprise]
license-key = ""
marketplace-env = ""

Need to enable Flux as part of the default settings for the marketplace listing

Need to add an additional option for customers to deploy monitoring node for cluster

Set up continuous integration via CircleCI or Jenkins

On each commit to master, CI should:

Validate Packer templates.
Validate solution templates.

Updating Chronograf to latest release version v1.8.4

Developing new mythology for partner-eng engagements

• 1. make it work
• 2. make it correct
• 3. make it perform

README should explain that when enabling the Chronograf option, it will act as a jumpbox to all other VM's

The chrono instance will be used as our bastion node (monitoring, chrono, templates)

The ARM templates do not currently provide output values. An obvious one would be the URL of the InfluxDB load balancer and a link to Chronograf.