https://www.puppet.com/community logo
Join Slack
Powered by
# freebsd
  • b
    yes
  • b
    choose any arm server size you like, just be sure to delete it after you're done
    👍 1
  • b
    we've ~ 150€/month free there and currently we spend 50-70 per month I think
  • b
    \o/
  • s
    Copy code
    2023-11-22T18:44:12.392Z INFO  [async-dispatch-2] [p.s.m.master-service] Puppet Server has successfully started and is now ready to handle requests
  • s
    loooks good 🙂
  • s
    Let's compile a catalog now
  • b
    \o/
  • s
    Copy code
    root@amnesia:~ # puppet agent -t
Info: Using environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Caching catalog for <http://amnesia.example.com|amnesia.example.com>
Info: Applying configuration version '1700679006'
Notice: /Stage[main]/Main/File[/tmp/test]/ensure: defined content as '{sha256}2fc87389015ae0691fbc1afd7d2ff3e0d0410ce4288c5fa0c942c5e5b45fc91c'
Notice: Applied catalog in 0.01 seconds
root@amnesia:~ # cat /tmp/test
it works!
  • s
    100% success \o/
  • s
    Awesome, I will commit the change so that we build packages for aarch64.
  • s
    @bastelfreak so if I want to use FreeBSD for my account, I have to fill-in a technical support request and they handle this on a per-user basis?
  • b
    per project, but yes. raise an issue and mention the links to the iso, they will add it
  • s
    👍 Thanks!
  • b
    if you just need stuff for testing you can always use the vox pupuli account if you like
    👍 1
  • b
    and if someone has really too much free time, they could work on an automated freebsd setup and then we use that for beaker
    😍 1
  • b
    we can take a snapshot from a running instance and use that to spin up new servers via the API. I think that's a good way to go. But if someone has a better idea just tell me
  • s
    Hello! No update for the Puppet ports for a long time, I guess you know why 😒. I just realize that Puppet 7 has reached EOL, so I will deprecate 
    sysutils/puppet7
    accordingly. Puppet 7 could optionally use cfacter (facter 3, 
    sysutils/facter
    ) which was recently marked broken because it does not build with recent versions of boost. It will be scheduled for deletion too (no port depend on it). Same apply for 
    devel/leatherman
    and 
    devel/cpp-hocon
    (since no other port depend on them). 
    net/cpp-pcp-client
    and 
    sysutils/pxp-agent
    have already been deprecated yesterday because the former is broken (also boost) and is only used to build the latter which is only useful for users of choria who want to un bolt tasks.
    👍 1
  • s
    (this also include 
    sysutils/puppetserver7
    , 
    databases/puppetdb7
    and 
    databases/puppetdb-terminus7
    indeed)
  • s
    I am still waiting to have some visibility regarding facter before pushing openvox ports to the FreeBSD ports tree. Perforce promised a resolution in a few weeks (https://github.com/voxpupuli/community-triage/issues/28#issuecomment-2881122958 "Facter* (Perforce and Community will come together in a few week's time to continue the discussion on facter)"), so maybe after 6+ month of no-info we will be able to move on?
  • s
    I am starting to work on these ports locally to ensure they work as expected and be able to move quickly when we finally know what will happen to facter.
  • s
    Next, I plan to deprecate the puppet ports because they will not receive updates and the openvox ones are a drop-in replacement, add an entry to UPDATING to tell people about this move, and write an entry for the next quarterly report.
  • s
    I quite struggle at writing non-technical things, so if you feel like you can help for these last tasks, I would be very happy to hear from you 😉
  • s
    FYI, I created ports for the openvox components in a branch in my fork of the repo: https://github.com/smortex/freebsd-ports/tree/openvox. When we know about facter future, I will update them accordingly and push them to the official ports tree. I tested them with the project I use as integration test when updating the legacy puppet ports and experienced no issue.
  • s
    Good news everyone: the FreeBSD ports for OpenVox have been released to the FreeBSD ports tree. Packages should be available in a few days.
    🙌 1
  • s
    In the meantime a word of caution: the multi_json gem 1.17.0 is backwards incompatible with the previous minor version. A 1.18.0 version has been committed yesterday, but until this package is available, updating to 1.17.0 will break the puppetserver package. You can avoid this by locking multi_json until the fixed package is available.
  • s
    Because Puppet Core is now closed source, the Puppet packages will not be updated anymore unless Perfoce decide to do updates to their legacy repo (something they told us they would do on major CVE). I do not think it is worth keeping them in the FreeBSD ports tree, so I plan to deprecate them soon. If you have concerns, please tell me.
  • s
    Heads up: the openvoxdb packages will be delayed while we handle some unexpected breakage… See https://github.com/OpenVoxProject/openvoxdb/issues/31 for details.
  • s
    Root cause of the openvoxdb packages resolved. Packages should be available in a few days
  • s
    In the meantime, you can upgrade your agents as packages are now available. For now, there is no replacement for pdk/bolt, so 
    pkg install openvox-agent8
    will want to remove them too if they are installed. Stay with puppet for now if this is a concern: work is being done to bring community packages for bolt and the development tools.