Getting Started With Google Cloud Marketplace
Circonus IRONdb is available on the Google Cloud Marketplace as a multi-VM (virtual machine) solution. The solution configures your chosen number of nodes into a cluster, suitable for either standalone use or as a private storage cluster connected to the Circonus SaaS platform.
Deploying the Circonus IRONdb GCP Solution
Access the Circonus IRONdb page in Google Marketplace and click the LAUNCH ON COMPUTE ENGINE button.
In the “New Circonus IRONdb deployment” window, select the desired Zone, Instance Count, and Machine Type. Circonus strongly recommends using SSD for the Metric data disk (the volume where your telementry data will be stored on each node). Choose the desired size of the Metric data disk.
If you wish to send Graphite metrics to the cluster from outside the Google Cloud, leave the “Allow TCP port 2003” firewall rule enabled.
If you wish to send OpenTSDB metrics to the cluster from outside the Google Cloud, leave the “Allow TCP port 4242” firewall rule enabled.
By default, Circonus IRONdb will report software malfunctions to Circonus. This requires internet access from each node of the cluster. If you do not wish to allow this outbound traffic, uncheck the “Automated crash reporting” option.
Click the Deploy button. The Deployment Manager page provides the status of the deployment.
Once the deployment succeeds, you can check the status of Circonus IRONdb on each cluster node by logging into the VM and running the following command:
# /usr/bin/systemctl status circonus-irondb
Your Circonus IRONdb deployment is now ready to accept metric data. For more information on how to send data in, see the Integrations page in the Circonus IRONdb documentation.
If you plan to connect this deployment to your Circonus SaaS account, see below for additional steps.
Connecting A Deployment to Circonus SaaS
Connecting a GCP Marketplace deployment as a swimlane for a Circonus SaaS
account requires static IP address assignments for the nodes, as well as
opening the IRONdb API port (8112/tcp) to the SaaS egress IPs, which can be
obtained by querying the DNS name
$ dig out.circonus.net +short 22.214.171.124 126.96.36.199
After deploying a Marketplace cluster, navigate to your project’s “VPC network” page:
Change To Static IPs
- Choose “External IP addresses” from the left menu.
- Locate the address resources associated with the IRONdb cluster (the In use by column).
- For each address identified, change the Type from “Ephemeral” to “Static”. This will pop a dialog where you must enter a Name and, optionally, a Description. Note: the values cannot be changed once set.
Gather Node UUIDs
Circonus will use the node UUIDs (assigned internally during deployment) to create DNS records that will be used to connect to the cluster from the Circonus SaaS environment.
Log into one of the cluster nodes and run the following command:
grep gcpmkt /etc/hosts
The output will be a list of IP addresses and hostnames that start with a UUID. Send this list, along with the external IP address that corresponds to each node, to Circonus.
Add Firewall Rule
Choose “Firewall rules” from the left menu, then click the
+ CREATE FIREWALL RULE option at the top of the page.
- Enter a descriptive name for the rule, such as
- (optional) Add a longer description.
- Select which Network the rule applies to. Often this is
defaultbut choose the one that matches where the cluster is deployed.
Prioritycan be left at its default.
Direction of trafficand
Action on matchat their defaults (Ingress and Allow, respectively)
Specified target tags
- In the
Target tagsfield, enter the same tag used for the port 2003/4242 rules, which is
- In the
Source IP rangesfield enter, one at a time,
188.8.131.52/32(or change the IPs if different from the DNS result above.)
Second source filteras
Protocols and ports, the default is
Specified protocols and port. Check the
tcpbox and enter
8112in the input field next to it.
- Click Create.
Open Source Licenses
License information for all open source software included in or distributed
with Circonus IRONdb may be found on any cluster node in the directory,