https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • v
    er
  • v
  • v
    my problem is figuring out which pubkey i export there
  • v
    curie in this case
  • v
    so
  • v
    make a pql query to get all nodes with your wireguard profile (if all of them should mesh)
  • v
    iterate on that list. for each node get their wireguard_keys and networking.ip6 or whatever is the public ip, and come up with a naming scheme for the in-tunnel ips.
  • v
    e.g. an internal subnet and the last octett is from their networking.ip6
  • v
    and in their wireguard_keys list, you look for an entry named with the local hostname
  • v
    that will require a few puppet runs on each box, but it should be fully automated to mesh itself
  • v
    on top glue some BGP with bird, done
  • v
    ah yes, i need pql for this, that would work
  • v
    now i just need a puppetdb backend :p
  • v
    i'm using some bespoke redis thing because puppetdb is hosed in debian
  • v
    I feel sorry for you
  • v
    shrugs
  • v
    get a puppetdb :D
  • l
    use the aio?
  • v
    puppetdb 7 actually made it to experimental, it might be backportable
  • v
    what's aio?
  • l
    all in one/puppetlabs repos
  • v
    i did want to avoid puppetdb, in general, it seems like quite a monster, just to get exported resources
  • l
    and 7 is in testing
  • v
    there is a well working puppetdb module "include puppetdb" tadaaaa puppetdb working :D
  • v
    but of course, i often need more than exported resources
  • v
    Spritzgebaeck: hilarious :p
  • v
    i am aware of the existence of upstream packages, thanks
  • v
    it's really a small software
  • v
    puppetdb?!
  • v
    yes
1...178179180...648Latest