More changes on yum.puppetlabs.com

[Michael Stahnke]

Greetings,

I'd like to remove the cruft (no longer maintained) areas of
yum.puppetlabs.com. I fear they only cause confusion and offer
less-than-desirable experience for our users.

I'd like to remove

/base
/prosvc
/porsvc.unsigned
/SRMS
/sources

I'd like to do this some time next week. The stuff mostly found in
base is available elsewhere and signed properly. The prosvc stuff has
been largely unmaintained. The /SRPMS folder is now broken out into
each distribution area, so this high-level directory isn't needed.
The /sources directory contains a very incomplete listing of source.
We have that available either via SRPMS or at downloads.puppetlabs.com

This will basically keep:

/el (stuff for RHEL, CentOS, Scientific, Oracle Linux etc)
/fedora

For specific feedback on this change, you can update
http://projects.puppetlabs.com/issues/8473 or you can reply to this
thread.

NOTE:
There's been some discussion about other package platforms,
Debian/Ubuntu, Solaris, etc. There are plans to begin working on
making those packages readily available (working with the community),
however it's time permitting still.

Mike

[Michael Stahnke]

On Thu, Oct 6, 2011 at 10:34 AM, Michael Stahnke <sta...@puppetlabs.com> wrote:
> Greetings,
>
> I'd like to remove the cruft (no longer maintained) areas of
> yum.puppetlabs.com.  I fear they only cause confusion and offer
> less-than-desirable experience for our users.
>
> I'd like to remove
>
> /base
> /prosvc
> /porsvc.unsigned
> /SRMS
> /sources
>
> I'd like to do this some time next week.

This has been completed.

Please let me know if you have issues.

[Alexandre]

ah so that's why i could not find it at first. Somewhere in the Cloud
provisioner or Dashboard or documentation, there were links
to ...prosvc...

On 6 oct, 19:34, Michael Stahnke <stah...@puppetlabs.com> wrote:
> Greetings,
>
> I'd like to remove the cruft (no longer maintained) areas of
> yum.puppetlabs.com.  I fear they only cause confusion and offer
> less-than-desirable experience for our users.
>
> I'd like to remove
>
> /base
> /prosvc
> /porsvc.unsigned
> /SRMS
> /sources
>
> I'd like to do this some time next week. The stuff mostly found in
> base is available elsewhere and signed properly.  The prosvc stuff has
> been largely unmaintained.  The /SRPMS folder is now broken out into
> each distribution area, so this high-level directory isn't needed.
> The /sources directory contains a very incomplete listing of source.
> We have that available either via SRPMS or at downloads.puppetlabs.com
>
> This will basically keep:
>
> /el (stuff for RHEL, CentOS, Scientific, Oracle Linux etc)
> /fedora
>

> For specific feedback on this change, you can updatehttp://projects.puppetlabs.com/issues/8473or you can reply to this

[praveen pekuda]

  can u please update 4.8 puppet verstion in this repos, we are not identified this version

[Melissa Stone]

Hello,

You can find Puppet 4.8 in the puppet-agent 1.8 packages. These are available via the PC1 repo.

You can find more information on what is provided in the puppet-agent packages at https://docs.puppet.com/puppet/latest/about_agent.html and more about the PC1 repo at https://puppet.com/blog/welcome-to-puppet-collections.

The puppet 4.8 installation instructions can be found at https://docs.puppet.com/puppet/4.8/install_pre.html

I hope this helps

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7c80b7d9-0818-4171-afa5-9ddf6350577a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Melissa Stone

release engineering

mel...@puppet.com | @melissaapiedra

[Arkadi Colson]

Hi

Somebody managed to implement Collectd - InfluxDB - Grafana monitoring
in an automated way? Collectd is not a problem but how to automate
graphs addition in Grafana for new hosts based on roles?

Thx!
Arkadi

[Klavs Klavsen]

We do that.. look at http://docs.grafana.org/reference/scripting/

You can simply write a scripted dashboard and have your javascript check f.ex. for the existence of a mysql counter on the relevant host.. and then draw the graphs for "mysql" if the counters are there - and so on for all other type of graphs you want.

We then link from our monitoring system to the scripted dashboard - with hostname as argument - that way we always have a direct link from an alert, to all relevant graphs for a host.