Thats cool a controlled and independent stack with all the dependencies.
Independent of the OS is great. Scl works only on rhel 6 and 7.

Please don't forget rhel 5 packages also. I know it is outdated but it is
still widely used .

And bundled software will need to receive security updates, ex ruby
openssl, etc .

Best
Lmello

Best
Em 19/11/2014 13:00, "Matthaus Owens" <matth...@puppetlabs.com> escreveu:

> Erik,
> The plan is to deliver the AIO package to not just platforms with
> older rubies, but to all of the deb/rpm platforms we package for
> currently.
>
> On Wed, Nov 19, 2014 at 6:02 AM, Erik Dalén <erik.gustav.da...@gmail.com>
> wrote:
> >
> >
> > On Tue Nov 18 2014 at 8:04:13 PM Eric Sorenson
> > <eric.soren...@puppetlabs.com> wrote:
> >>
> >> Hi all, as some of you have noticed, our target date in JIRA for Puppet
> 4
> >> is not too far off now. (We just moved it out from early December to
> early
> >> January based on the remaining must-have workflow). While you can poke
> >> through tickets to see exactly what's going in, it might be helpful to
> have
> >> a little higher level overview of what is happening. Let me try to
> provide
> >> that as well as ask some questions of things we're not sure about.
> >>
> >> 1. Ruby 1.8.7 support is going away.
> >>
> >> 2. To enable #1 but still support OSes that ship with 1.8.7, we're going
> >> to be packaging and delivering Puppet 4 an an 'all-in-one' (AIO) package
> >> bundled together with
> >>  - openssl
> >>  - ruby
> >>  - augeas
> >>  - ruby-augeas
> >>  - ruby-stomp
> >>  - ruby-shadow
> >>  - puppet
> >>  - mcollective
> >>  - facter
> >>  - hiera
> >> - + misc supporting gems/libs (deep merge, yaml, etc)
> >> (Question: are there other *agent side* components you feel are
> essential
> >> to the functioning of the puppet stack?)
> >
> >
> > puppetdb-terminus - required for masterless setups.
> >
> > Btw, is there anything stopping you from delivering this AIO package to
> > newer systems as well? For example Ubuntu Trusty has ruby 1.9.3 by
> default
> > but also has ruby 2.0.0. But an AIO package with ruby 2.1.x would be a
> big
> > speed increase compared to both those other ruby versions.
> >
> >>
> >>
> >> 3. The AIO packages will have a filesystem layout that installs the
> >> programs into /opt/puppetlabs/agent and the configs into
> >> /etc/puppetlabs/agent ; the packages will be a different basename than
> >> puppet ('puppet-agent') so won't install automatically on an upgrade,
> but
> >> *will* obsolete the puppet packages if you decide to install them. AIO
> >> packages will be available from the Nightly repos Real Soon Now[tm] and
> I
> >> expect Melissa or Haus will update when they're up so everyone can poke
> at
> >> 'em.
> >>
> >> 4. We are planning to break cross-major-version compatibility over the
> >> network. The amount of change we need to support in order to keep moving
> >> components to the Puppet Server and out of Ruby is the main driver for
> this,
> >> but generally, if you can't break compatibility on a major version
> >> boundary... when CAN you? See PUP-3641 for the overview of that work.
> >>
> >> 5. The upgrade process would be as Chris described above, where you'd
> set
> >> up a new server running puppet 4 (hey it's an opportunity to move your
> >> puppetmasters to EL 7!) and point the new agents at it, leave the old
> ones
> >> running until their agents are drained.
> >> Question: What can/should we do to make that kind of transition go more
> >> smoothly? (One idea that just struck me is to have the puppet4 agent
> have a
> >> different default value for $server than 'puppet', so it wouldn't need
> >> post-install configuration to point at the new server)
> >>
> >> 6. We're going to stop providing the puppetmaster/puppet-server
> >> (passenger) packaging in favour of the puppetserver packages. There will
> >> still be rack/passenger support in Puppet 4, but not in Puppet 5.
> >>
> >> 7. Umm.. I think that's all.
> >>
> >>
> >> Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
> >> puppet platform // coffee // techno // bicycles
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups
> >> "Puppet Developers" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an
> >> email to puppet-dev+unsubscr...@googlegroups.com.
> >> To view this discussion on the web visit
> >>
> https://groups.google.com/d/msgid/puppet-dev/FF17DBFD-7DB1-4241-AC3C-EE9520A2E1C9%40puppetlabs.com
> .
> >> For more options, visit https://groups.google.com/d/optout.
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Puppet Developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to puppet-dev+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/puppet-dev/CAAAzDLcqbDwMZEWZrjyZRYkDLwk6cUn%3DYjFE1YyduQuHzLucRA%40mail.gmail.com
> .
> >
> > For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Matthaus Owens
> Puppet Labs
>
> Join us at PuppetConf 2015, October 5-9 in Portland, OR -
> http://2015.puppetconf.com.
> Register early to save 40%!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-dev/CACD%3DwAeOeHxhtTUBY1FDeoiOQWRzGJuhF6xWYaJp_i5As0UvYA%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/CAM%3D8oNKrTp7peG3iaQuEwQb014B4L0ASmmv4FGDzqi2ecLsfPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to