Date: Sun, 12 Jun 2016 20:06:50 +0100 From: Peter M Souter <p.morsou@gmail.com> To: Kurt Jaeger <lists@opsec.eu> Cc: ports@freebsd.org Subject: Re: Facter 3.X questions Message-ID: <CAD7dwGp__jN%2BMg7jZSZoAuu4GG9v2ezdou7M84N%2BqGQObFwmjw@mail.gmail.com> In-Reply-To: <20160604193607.GK41922@home.opsec.eu> References: <CAD7dwGq4aav7-398c6EPeSQOi%2B2QfqrBMq=OE1FVyED%2BjA5Wiw@mail.gmail.com> <20160604193607.GK41922@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Kurt, > Can you explain the state of factor for us ? We have 3.1.3 in the ports, and upstream is @3.1.8. <http://3.1.0.8/>; Have you tried to provide a patch to the ports to get the port up2date ? Not sure it would need a patch, I think just pulling down the latest tag from git should be enough. > Then: What are those 'facts' ? Are they modules for facter to collect specific info on a system etc ? Are they part of facter itself or do you want to provide seperate ports for this ? What kind of facts are generally available ? Facter is a tool to get information from a system, such as amount of RAM, CPUs, mounts, size of partitions etc. Usually for usage with Puppet. The missing facts are part of facter itself, they just got missed when the upgrade happened because we dont have internal infra for testing Facter, it's mainly in the hands of FreeBSD puppet users to log issues when stuff breaks. > The WWW in pkg-descr is https://puppetlabs.com/facter, which no longer works -- what would be the correct link ? Yeah, there was a site re-design recently. I guess the new link would probably be the main docs page: https://docs.puppet.com/facter/ Would that be something that needs a patch? I can see if I can figure out how to submit for that :) > How/when should facter replace rubygem-facter in the ports tree ? Right now puppet depends on rubygem-facter, which is only at 2.4.4 ? Upstream is at 2.4.6 I guess the best time to replace would be when all the missing facts are restored. I'm making ok progress on it right now, we have a hackathon soon so I might be able to get it completely across the line then. What's the policy of when ports get removed? Some people prefer to use the older Facter as it's Ruby based, or they're not reading to make the major version jump, so it might be best to keep both? > For this, we probably need more understanding of facter 8-} Any links that you can share that bring us up to speed ? Hah, it's not super clear how to get started in it. I'd recommend reading the Facter README to get up to speed with how to build: https://github.com/puppetlabs/facter/blob/master/README.md Then looking at a PR with an example of how a fact is written. If you can get your head around the Facter internals, it's basically just making sure each result key can match with some C/C++ code to get the information from the system. For example, to get processor count of the machine with a sysctl call: // Get the logical count of processors len = sizeof(result.logical_count); mib[1] = HW_NCPU; if (sysctl(mib, 2, &result.logical_count, &len, nullptr, 0) == -1) { LOG_DEBUG("sysctl hw.ncpu failed: %1% (%2%): logical processor count is unavailable.", strerror(errno), errno); } https://github.com/puppetlabs/facter/pull/1348/files If you're interested there's normally people in #puppet-dev on Freenode who know way more than I do about internals that can answer questions > Submit PRs requesting maintainer, and if they come with patches that bring the ports up2date, you're maintainer if the previous maintainer agrees. Just to make sure, I actually work at Puppet, it's not a conflict of interest or anything to become a Facter maintainer right? if not I'll give that a go! :) > PS. Sorry if this is the wrong way to do this, first time emailing to a > port maintainer list. I asked in the FreeBSD freenode room and people said > this was the way to do it and to CC the Ports mailing list also :) > Both lists are fine. As this is more a general ports question, -ports is probably fine for further discussion. There's not much discussion on -ruby. Great, removed ruby- from CC. On Sat, Jun 4, 2016 at 8:36 PM, Kurt Jaeger <lists@opsec.eu> wrote: > Hi! > > > Since Facter's move to a C/C++ codebase, a lot of facts have gone missing > > on FreeBSD machines. As a dabbler in FreeBSD I want to help fix this! :) > > Very nice! I'm no puppet or facter user, but I can probably help > with the ports part. > > Can you explain the state of factor for us ? We have 3.1.3 in > the ports, and upstream is @3.1.8. Have you tried to provide > a patch to the ports to get the port up2date ? > > Then: What are those 'facts' ? Are they modules for facter to > collect specific info on a system etc ? Are they part of facter itself > or do you want to provide seperate ports for this ? > > What kind of facts are generally available ? > > The WWW in pkg-descr is https://puppetlabs.com/facter, which > no longer works -- what would be the correct link ? > > How/when should facter replace rubygem-facter in the ports tree ? > Right now puppet depends on rubygem-facter, which is only at 2.4.4 ? > Upstream is at 2.4.6. > > > more difficult missing areas such as determining swap space, networks and > > such, that would be greatly appreciated. Getting kenv and sysctl settings > > has been fairly simple, these ones have been a little bit more complex... > > For this, we probably need more understanding of facter 8-} > Any links that you can share that bring us up to speed ? > > > 3) How difficult is it to become a maintainer? > > Submit PRs for sysutils/facter and sysutils/rubygem-facter. > robak@ is the maintainer for rubygem-facter, so maybe he's willing > to step down ? > > > I notice that facter is > > currently under the ruby maintainer email namespace, but right now it's > not > > released to Rubygems since 2.4 and the code is 85% C++ now. I wouldn't > mind > > throwing my hat in and becoming a maintainer if that would help? :) > > Submit PRs requesting maintainer, and if they come with > patches that bring the ports up2date, you're maintainer > if the previous maintainer agrees. > > > PS. Sorry if this is the wrong way to do this, first time emailing to a > > port maintainer list. I asked in the FreeBSD freenode room and people > said > > this was the way to do it and to CC the Ports mailing list also :) > > Both lists are fine. As this is more a general ports question, > -ports is probably fine for further discussion. There's not much > discussion on -ruby. > > -- > pi@opsec.eu +49 171 3101372 4 years to > go ! >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAD7dwGp__jN%2BMg7jZSZoAuu4GG9v2ezdou7M84N%2BqGQObFwmjw>