@michaelklishin michaelklishin released this Oct 19, 2017 · 101 commits to master since this release

Assets 4

0.10.0 is minor feature release. It targets RabbitMQ 3.6.x. For 3.7.0 (including preview releases), see individual cluster formation plugins.

Consul Backend

  • Consul 1.x support. This also means dropping support for Consul versions prior to 0.6.0.

    GitHub issues: #52, #53

Contributed by Andrew Colin Kissa.

@michaelklishin michaelklishin released this Oct 8, 2017 · 109 commits to master since this release

Assets 4

0.9.0 is minor feature release. It targets RabbitMQ 3.6.x. For 3.7.0 (including preview releases), see individual cluster formation plugins.

General Changes

  • HTTP[S] proxy support.

    Contributed by Matteo Cafasso.

    GitHub issue: #46.

  • Documentation and Docker example improvements.

Consul Backend

  • Corrected service deregistration key.

    Git commit: b8d27c8.

  • Session creation operation now will be retried up to 10 times should Consul
    respond with a 500.

    GitHub issue: #44.

  • Arbitrary tags now can be used when registering with Consul.

    Contributed by Andrew Colin Kissa.

    GitHub issue: #50

@michaelklishin michaelklishin released this May 31, 2017 · 159 commits to master since this release

Assets 4

0.8.0 is minor feature release. It targets RabbitMQ 3.6.x. For 3.7.0 (including preview releases), see individual cluster formation plugins.

General Changes

  • Locking support in discovery backends. This is an alternative solution to randomized startup delay.
    Both strive to address the natural race condition during initial cluster formation. Backends
    are not required to implement locking support, just like they are not required to support node registration.

    Contributed by Alexey Lebedeff (Mirantis).

    GitHub issue: rabbitmq-autocluster#6

Kubernetes Backend

AWS Backend

  • The AWS library used by this backend no longer tries to fetch instance metadata
    when it is first loaded. Previously it was happening even if a backend different from AWS was used.

    GitHub issue: rabbitmq-autocluster#27

Consul Backend

  • Locking support in the Consul backend (see above).

    Contributed by Valentin Fadeev.

    GitHub issue: rabbitmq-autocluster#22

etcd2 Backend

  • Locking support in the etcd2 backend (see above).

    Contributed by Alexey Lebedeff (Mirantis).

    GitHub issue: rabbitmq-autocluster#6

May 30, 2017
Merge branch 'ValFadeev-rabbitmq-autocluster_startup-locking-consul' …
…into stable
May 20, 2017
Merge pull request #6 from rabbitmq/rabbitmq-autocluster_startup-lock…
…ing-support

Add startup lock support (general framework + tested etcd implementation)
Pre-release
Pre-release

@michaelklishin michaelklishin released this May 20, 2017 · 185 commits to master since this release

Assets 5

0.8.0 Milestone 2 is a preview release of 0.8.0 which focuses on improving the Kubernetes and etcd2 backends.

General Changes

  • Locking support in discovery backends. This is an alternative solution to randomized startup delay.
    Both strive to address the natural race condition during initial cluster formation. Backends
    are not required to implement locking support, just like they are not required to support node registration.

    Contributed by Alexey Lebedeff (Mirantis).

    GitHub issue: rabbitmq-autocluster#6

etcd2 Backend

  • Locking support in etcd2 backend (see above).

    Contributed by Alexey Lebedeff (Mirantis).

    GitHub issue: rabbitmq-autocluster#6

Kubernetes Backend

AWS Backend

  • The AWS library used by this backend no longer tries to fetch instance metadata
    when it is first loaded. Previously it was happening even if a backend different from AWS was used.

    GitHub issue: rabbitmq-autocluster#27

@michaelklishin michaelklishin released this Apr 11, 2017 · 236 commits to master since this release

Assets 5

0.7.0

This is the first release produced from the team RabbitMQ fork of the plugin.

These release notes do not include a lot of bug fixes and small improvements that happened in the AWeber fork since 0.6.1 before team RabbitMQ decided to fork the project.

General Changes

  • Documentation guide is now embedded into README to simplify maintenance
    with multiple concurrently developed branches.

    GitHub issue: #12.

AWS Backend

  • Support the AWS_EC2_TAGS environment variable, its value is supposed to be JSON now

    GitHub issue: #7

  • Make it possible to use private instance IP addresses with AWS autoscaling groups

    GitHub issue: #14

  • Improve error handling when parsing tags.

    GitHub issue: #11.

  • Improve debug logging for AWS API requests

    GitHub issue: #15

  • Depend on the team RabbitMQ fork of rabbitmq-aws

    GitHub issue: #8

Consul Backend

  • Re-register with Consul if Consul reports that our node is not known for any reason.

    GitHub issue: #2

  • Support deregister_critical_service_after

    GitHub issue: #3

  • Support for custom hostnames (e.g. for environments that use DHCP but not dynamic DNS records)

    GitHub issue: #4

  • New Consul, Docker Compose and HAproxy example

    GitHub issue: #5

  • Support arbitrary strings as Consul node names. Contributed by @ValFadeev.

    GitHub issue: #9

  • Allow for clustering with nodes in the warning state if the user opts in. Contributed by @ValFadeev.

    GitHub issue: #10

Kubernetes Backend

  • Make it possible to connect to Kubernetes using a hostname and not just IP address. Contributed by @pavel987.

    GitHub issue: #13.

Apr 11, 2017
Use Make variables to populate application descriptor
Similarly to how all tier 1 and tier 2 RabbitMQ plugins currently do.
Jun 15, 2016
Use the instance metadata IP instead of FQDN (#67)
Jun 3, 2016
Another attempt to get deploy working