mech

mech automates Constellix DNS configuration (similar to octodns and terraform). The advantage of mech is that it supports advanced configuration with multiple GTD regions and GeoProximity locations.

The application manages DNS records, Sonar checks and GeoProximity locations. The functionality can easily be extended to support other Constellix resources.

Supported features

Sonar REST API

Sonar

• static configuration
  • http
  • tcp
  • icmp
  • dns
  • ssl cert
• runtime data
  • http
  • icmp
  • dns
  • tcp
  • ssl cert

DNS

• Domain records

  • A
  • AAAA
  • ANAME
  • CAA
  • CERT
  • CNAME
  • HINFO
  • HTTP
  • MX
  • NAPTR
  • NS
  • PTR
  • RP
  • SPF
  • SRV
  • TXT
  • pools?

• GeoProximity

  • Renaming

Configuration format

constellix:
  sonar:
    http_checks:
      - file1.yaml
      - file2.yaml
      - ...
    tcp_checks:
      - myfolder/*.yaml
  dns:
    surfly.gratis:
      - file4.yaml

Use mech sonar discover static -t http command to print existing configuration

Resource naming

Some resources (e.g. a Sonar check ID in failover configuration) can be specified in two different ways:

• ID of the resource, int
• dynamically discovered value (e.g. @sonar,http:test-online). When parsing the configuration mech will call Constellix Sonar REST API and retrieve all available http checks. If one of the http checks has name test-online, it's ID will be used as sonarCheckId. TCP checks work the same way with @sonar,tcp:<name>

Resources

• Constellix DNS REST API v4
• Constellix Sonar Rest API
• Constellix go client (just for reference)