basho-labs / puppet-riak

A puppet module to deploy Riak clusters
Apache License 2.0
33 stars 37 forks source link

Upgrading from 1.3.0 to 1.3.1 #18

Closed Iristyle closed 11 years ago

Iristyle commented 11 years ago

So in the Puppet script that Vagrant runs, I have

Notice that I already have 1.3.0 installed.

class { 'riak':
  version => '1.3.0',
  cfg => {
    riak_api => {
       pb_backlog => 64
    },
    riak_kv => {
      storage_backend => '__atom_riak_kv_eleveldb_backend',
      map_js_vm_count => 24,
      reduce_js_vm_count => 24
    },
    riak_control => {
      enabled => true,
      auth => '__atom_none',
      admin => true
    }
  }
}

Now I want to upgrade to 1.3.1 -- and presumably I just need to change the version

class { 'riak':
  version => '1.3.1',
  cfg => {
    riak_api => {
       pb_backlog => 64
    },
    riak_kv => {
      storage_backend => '__atom_riak_kv_eleveldb_backend',
      map_js_vm_count => 24,
      reduce_js_vm_count => 24
    },
    riak_control => {
      enabled => true,
      auth => '__atom_none',
      admin => true
    }
  }
}

But nothing happens... just the normal config runs.

Note also that I get this warning from Hiera, as this is a Vagrant box, etc. -- with no centralized Hiera store. Not sure if that's a problem?

Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
haf commented 11 years ago

Hi,

Have a look at https://github.com/basho/puppet-riak/pull/15

You'll see I started a discussion in the contents of the pull request text body. Please have this discussion there.

Iristyle commented 11 years ago

Sorry -- didn't see there was already a discussion open on this -- thanks!