https://www.puppet.com/community logo
Join Slack
Powered by
# office-hours
  • n
    When did facts get moved from the 
    values
    key ? I thought it was puppet 7 in general, but i've got a linux host on 
    7.13.1
    where facts are returned in 
    values
    and a windows host on 7.18.0 where they aren't
  • j
    Hi folks, Have a question about open source puppet, ask away!
  • j
    @nickgw If you run 
    puppet facts find
    then you're going to get a 
    Puppet::Node::Facts
    object serialization including 
    values
  • j
    But if you do 
    puppet facts show
    then it will just print the fact values (which is probably what you really want)
  • n
    makes sense, but i ran 
    puppet facts find
    on each system and 7.13.1 returned in the values key, 7.18.0 did not
  • n
    i lied,
  • n
    you're right
  • s
    This message was deleted.
    j
    b
    • 3
    • 2
  • b
    for a normal user it's not obvious that multiple teams maintain different module groups with different guidelines/configuration
    nodding 1
  • b
    other question. https://github.com/puppetlabs/puppet-runtime/ is the basically the vanagon config/data to build the different puppet/puppetserver debian/rpm packages?
  • j
    That repo builds all of the ruby, openssl, curl, etc components that we vendor in 
    puppet-agent
    , 
    pdk
    , 
    bolt
    , etc packages
  • j
    Then https://github.com/puppetlabs/puppet-agent takes the prebuilt runtime, puppet, facter, etc and builds rpm, deb, msi, etc
  • j
    We split it because building the runtime is "expensive" and rarely changes.
  • b
    Is there a chance/who do I need to send chocolate to make the build pipelines public so people can contribute to it?
    🤣 1
  • j
    I would love it if the community could contribute, but there are a few difficulties. We support a number of platforms that aren't the typical Linux/macOS/Windows, like AIX & Solaris.
  • b
    no problem, just put the debian/ubuntu pipelines public, so we don't have to wait more than 1.5 years for packages 🙂
  • b
    that would still be a huge improvement compared to no public pipeline at all
  • j
    As one of the people working on adding new OS platforms for the last year+, I would love nothing more than to make it easier for the community to contribute to "Please support platform X with architecture Y"
    👍 1
  • j
    But getting to that point isn't so easy. For example, take Debian 11 ARM. The work for adding agent support is in: https://tickets.puppetlabs.com/browse/PA-4604 But a prerequisite is creating the VM image to work in our environment.
  • j
    And updating 
    beaker
    , et al to recognize/handle the new OS/arch combination
  • d
    meeting Next up is 🧑‍🏫 Bolt in 4 hours
  • b
    do you run some builds in containers or does it have to be a VM?
  • j
    It has to be VM at the moment, because that's just how things work currently. But with some effort it could be made to work with containers, at least for the "easy" linux platforms.
  • b
    yeah sounds good
  • b
    is there any way for the community to help at the moment?
  • c
    https://github.com/sharpie/puppet-build-experiment runs 
    puppet-agent
    and 
    puppet-runtime
    builds inside containers. It's been a while since I've worked on it, so likely some cobwebs there.
  • b
    ah neat
  • j
    In order to run builds in a way that's consumable by our CI system, we'd need a webservice to implement VMPooler-like REST API methods and then have it proxy those requests to some container backend.
  • c
    The approach taken above is nested: it's a Vanagon project with platform configuration designed to work with 
    -e docker
    and then the project configurations for 
    puppet-runtime
    and 
    puppet-agent
    clone and build those projects inside the container with 
    -e local
    .
  • b
    nice
1...565758...78Latest