I tried to fix errors happening with puppet 3.2.3, mostly it's in the way
templates access variables, i.e. variables references should be prefixed
with '@' for puppet 3.x. Seems to be working fine with both 3.2.3 and 2.7
now. Does it make sense to do this kind of quick fix in the upstream, while
the bigger refactoring (BIGTOP-840) is in progress? And if it does, is it
possible to bring the changes into branch-0.6, or it's not working this way
with big top?
On Thu, Aug 8, 2013 at 11:51 AM, Konstantin Boudnik <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 08, 2013 at 11:29AM, Roman Shaposhnik wrote:
> > Hi Andrey!
> > On Thu, Aug 8, 2013 at 11:14 AM, Andrey Klochkov
> > <[EMAIL PROTECTED]> wrote:
> > > Hello,
> > > What puppet versions are supported by big top currently? I'm using big
> > > 0.6, and previously I noticed that it didn't work with puppet 3.x but
> > > puppet 2.7 worked fine.
> > Your observation is absolutely correct -- we're stuck with Puppet 2..
> > Personally I prefer Puppet 2.7 in my daily deploys of Bigtop, but 2.6
> > should be fine as well.
> > Puppet 3.x is known to be incompatible.
> I am running our recipes with Puppet 3.1.x; however 3.2.x doesn't work for
> > > Unfortunately, now I have to switch to 3.x because
> > > of our IT using it to manage the infrastructure. Should it actually
> > > with 0.6, trunk? Any Jiras tracking that?
> > We do have a JIRA tracking refactoring of our Puppet code:
> > https://issues.apache.org/jira/browse/BIGTOP-840
> > My original idea was to do a pretty significant overhaul, but
> > perhaps I've bitten way more that I was able to chew :-(
> > We would *love* if you could help us tackle it!
> > Thanks,
> > Roman.