rabbitmq-peer-discovery-aws classic config format question

180 views
Skip to first unread message

Rod

unread,
Jul 31, 2019, 5:30:20 PM7/31/19
to rabbitmq-users
Hi, 

I'm in the attempt of migrating from RabbitMQ 3.6.10 to a 3.7.x version

In the 3.6.10 we used rabbitmq-autocluster, and since I'm trying to jump to a newer RabbitMQ version, I will have to jump to rabbitmq-peer-discovery-aws  

When using rabbitmq-autocluster, we had in the rabbitmq.config file this, but I'm not sure how to migrate to the newer rabbitmq-peer-discovery-aws:

{autocluster, [
    {autocluster_log_level, debug},
    {backend, aws},
    {aws_autoscaling, false},
    {aws_ec2_tags, [
      {"rabbit-cluster-id", "poc_name"}
    ]},
    {aws_ec2_region, "us-east-1"}
  ]},


Some examples of different config for different features are here https://github.com/rabbitmq/rabbitmq-server/blob/master/docs/advanced.config.example but none of them for this feature that I am looking for.

Another question would be: knowing that following plugins are deprecated in 3.7.x, If I tried to use rabbitmq-autocluster (and therefore rabbitmq_aws) with 3.7.x would them work? or they wouldn´t even be took in account?

Michael Klishin

unread,
Jul 31, 2019, 5:38:01 PM7/31/19
to rabbitmq-users
What is the feature you are looking for?

All peer discovery mechanisms have pretty extensive documentation, including the AWS one [1].

I believe `autocluster.aws_autoscaling` simply indicates that tag-based discovery should be used.
New style config format does not have or need an alternative, unlees you opt in to use autoscaling group discovery
it will assume that instance tags must be used [2].

rabbitmq-autocluster is unsupported. I cannot recommend unsupported plugins over supported and well documented ones.


--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/fd46d684-91f0-43ba-af8d-4e83e8af54a0%40googlegroups.com.


--
MK

Staff Software Engineer, Pivotal/RabbitMQ

Rod

unread,
Jul 31, 2019, 5:51:40 PM7/31/19
to rabbitmq-users
Hi Michael,

Maybe I'm confused. 

What I'm trying to say is whenever we had to use rabbitmq-autocluster we used this config along with it:
{autocluster, [
    {autocluster_log_level, debug},
    {backend, aws},
    {aws_autoscaling, false},
    {aws_ec2_tags, [
      {"rabbit-cluster-id", "poc_name"}
    ]},
    {aws_ec2_region, "us-east-1"}
  ]},


Now that plugin is deprecated, I want to use the new rabbitmq-peer-discovery-aws  implementation included in RabbitMQ 3.7.x But In order to "migrate" above script to use it with rabbitmq-peer-discovery-aws I don't know how to proceed, and got confused.  I had already read the links you posted, but I'm not clear how to proceed, and I'm not sure what would be the configuration for rabbitmq-peer-discovery-aws  under classic config format.

Thanks!


El miércoles, 31 de julio de 2019, 17:38:01 (UTC-4), Michael Klishin escribió:
What is the feature you are looking for?

All peer discovery mechanisms have pretty extensive documentation, including the AWS one [1].

I believe `autocluster.aws_autoscaling` simply indicates that tag-based discovery should be used.
New style config format does not have or need an alternative, unlees you opt in to use autoscaling group discovery
it will assume that instance tags must be used [2].

rabbitmq-autocluster is unsupported. I cannot recommend unsupported plugins over supported and well documented ones.


On Thu, Aug 1, 2019 at 12:30 AM Rod <rodrigo...@gmail.com> wrote:
Hi, 

I'm in the attempt of migrating from RabbitMQ 3.6.10 to a 3.7.x version

In the 3.6.10 we used rabbitmq-autocluster, and since I'm trying to jump to a newer RabbitMQ version, I will have to jump to rabbitmq-peer-discovery-aws  

When using rabbitmq-autocluster, we had in the rabbitmq.config file this, but I'm not sure how to migrate to the newer rabbitmq-peer-discovery-aws:

{autocluster, [
    {autocluster_log_level, debug},
    {backend, aws},
    {aws_autoscaling, false},
    {aws_ec2_tags, [
      {"rabbit-cluster-id", "poc_name"}
    ]},
    {aws_ec2_region, "us-east-1"}
  ]},


Some examples of different config for different features are here https://github.com/rabbitmq/rabbitmq-server/blob/master/docs/advanced.config.example but none of them for this feature that I am looking for.

Another question would be: knowing that following plugins are deprecated in 3.7.x, If I tried to use rabbitmq-autocluster (and therefore rabbitmq_aws) with 3.7.x would them work? or they wouldn´t even be took in account?

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitm...@googlegroups.com.

Michael Klishin

unread,
Jul 31, 2019, 7:28:35 PM7/31/19
to rabbitmq-users
First step would be to understand what you are trying to accomplish. A config is a statement of intent. What is your intent?

There is no need to use classic config format with 3.7 peer discovery mechanisms. You would not gain anything.
The configuration keys are not always the same, you have to oblige by the Erlang syntax and so on.

`autocluster.autocluster_log_level` does not exist, all peer discovery logging uses the same log level as the rest of the system [1].
`autocluster.backend` is covered in [2].

`autocluster.aws_autoscaling` is not necessary unless you want to use ASGs.
`autocluster.aws_ec2_region` is covered in [3]
`autocluster.aws_ec2_tags` is covered in [4].

New style config file is covered in [5][6].


To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/d418a4e8-b828-4d22-b8fa-4b5eeca1ec99%40googlegroups.com.

Rod

unread,
Aug 1, 2019, 12:07:42 PM8/1/19
to rabbitmq-users
Ok thanks Michael. I think I have solved more of the question reading again some docs. 
But I'm still having one:  as you saw above, I have custom tags under aws_ec2_tags.

Using the new style I just see region service and environment availables. So, how to deal with my custom tags?


El miércoles, 31 de julio de 2019, 19:28:35 (UTC-4), Michael Klishin escribió:
First step would be to understand what you are trying to accomplish. A config is a statement of intent. What is your intent?

There is no need to use classic config format with 3.7 peer discovery mechanisms. You would not gain anything.
The configuration keys are not always the same, you have to oblige by the Erlang syntax and so on.

`autocluster.autocluster_log_level` does not exist, all peer discovery logging uses the same log level as the rest of the system [1].
`autocluster.backend` is covered in [2].

`autocluster.aws_autoscaling` is not necessary unless you want to use ASGs.
`autocluster.aws_ec2_region` is covered in [3]
`autocluster.aws_ec2_tags` is covered in [4].

New style config file is covered in [5][6].


Michael Klishin

unread,
Aug 2, 2019, 5:23:06 PM8/2/19
to rabbitmq-users
I've linked to [1] twice already in this thread. The section is entitled Using EC2 Instance Tags.
A quote from that section goes like this:

«Tags are configured using the cluster_formation.aws.instance_tags key. The example below uses three tags: region, service, and environment…»


To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/0ab1d289-cf2f-49e4-8a1f-d8d45f0db483%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages