Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix memcached instance #47

Merged
merged 9 commits into from
Aug 11, 2015
Merged

Conversation

someara
Copy link

@someara someara commented Jul 21, 2015

No description provided.

Current .kitchen.yml, Berksfile, and serverspec files require updates
to allow "kitchen test" to complete.

- moved current .kitchen.yml file to .kitchen.cloud.yml to avoid cloud
  provider missing key errors
- created a new .kitchen.yml file using vagrant driver, chef_zero
  provisioner, updated centos platforms, and added ubuntu-14.04
- updated Berksfile to use source location as site location has been
  deprecated in Berkshelf 3
- updated instance_spec.rb for Serverspec V2 and added a few more
  simple tests
- split `default.rb` recipe into `install.rb` and `configure.rb` to
  allow memcached_instance definition to proceed without default init
   configuration
- install `libmemcached-dev` instead of `libmemcache-dev` if debian
  family
- modify memcached_instance to only include `install.rb` recipe, disable
  and stop service, set instance name to `memcached` if specified as
  `memcached` and add missing options `udp_port`, `threads`,
   `max_object_size`, and `experimental_options`
- add missing `max_object_size` option to `sv-memcached-run` template
  as well as `experimental_options` and `threads` if specified
- add serverspec test to `default` test suite
- update `instance` serverspec test to check that memcached is running
  under runit
Add guard to memcached_instance definition to avoid service stop
When a large `maxconn` parameter are specified, the ulimit needs to
be increased. Currently only used with runit.
Debian family distributions automatically start services on install
which can cause weird states, especially when switching to runit.

- added logic to check whether memcached package is installed:
  if no, disable autostart, install, re-enable autostart
  if yes, execute package provider as normal (to allow upgrades)
@lock
Copy link

lock bot commented Oct 21, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants