Re: [Puppet Users] Stomp connector deprecated ?
On Monday, February 18, 2013 12:21:11 AM UTC-6, John Warburton wrote: Is this mcollective version 3.x or 2.3.x? Deprecation warning occurs in 2.3. Complete removal will occur in the 3.x production branch. So you should be good to continue using it for a few months to come, but when the next production series comes around it will really be gone. It's an early headsup. Hmm - I'm 3/4 way through my proof of concept and rolling out into lab over the coming 6-8 weeks. Production should be in 2-3 months. Should I continue with mcollective 2.2.x / stomp 1.2.2 / Active MQ 5.5 or wait a bit longer? You are absolutely fine to continue with your roll out. However, you should work the specific ActiveMQ or RabbitMQ connector into that rollout if you want to be fully forward-compatible. Ellison posted the link to the docs previously. Thanks John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Stomp connector deprecated ?
- Original Message - From: Drew Blessing drew.bless...@mac.com To: puppet-users@googlegroups.com Sent: Monday, February 18, 2013 11:47:53 AM Subject: Re: [Puppet Users] Stomp connector deprecated ? On Monday, February 18, 2013 12:21:11 AM UTC-6, John Warburton wrote: Is this mcollective version 3.x or 2.3.x? Deprecation warning occurs in 2.3. Complete removal will occur in the 3.x production branch. 2.2.x is the production branch that tends to stay around 6 months to a year 2.3.x is the early adopter/dev series deprecation log lines is in 2.2.3, removed in 2.3.1 and there will be several more 2.3.x releases before 2.2.x moves on. We do it this way so that we can identify any issues with the removal in the more risky branch. For example we now know that debian's package system and this removal will cause hassles, we know this cos the dev series feels that pain and it means by the time 3.0 or 2.4 comes around we can properly warn production users. No eta for when the 2.2.x branch will move forward, no eta for when this adapter will be removed from production code, no need to panic. But if you're starting out now you should look to using one of the new connectors I posted links to. The ActiveMQ and RabbitMQ connectors are just specialised versions of the Stomp ones, they were introduced to the production branches 2012/04/30 and 2012/09/13 so they've had a good bit of time to be tested before we are now finally warning that we will at some point in the future move to them as standard. I'll update the docs with this information hopefully this week So you should be good to continue using it for a few months to come, but when the next production series comes around it will really be gone. It's an early headsup. Hmm - I'm 3/4 way through my proof of concept and rolling out into lab over the coming 6-8 weeks. Production should be in 2-3 months. Should I continue with mcollective 2.2.x / stomp 1.2.2 / Active MQ 5.5 or wait a bit longer? You are absolutely fine to continue with your roll out. However, you should work the specific ActiveMQ or RabbitMQ connector into that rollout if you want to be fully forward-compatible. Ellison posted the link to the docs previously. Thanks John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Stomp connector deprecated ?
On 18 February 2013 23:19, R.I.Pienaar r...@devco.net wrote: No eta for when the 2.2.x branch will move forward, no eta for when this adapter will be removed from production code, no need to panic. But if you're starting out now you should look to using one of the new connectors I posted links to. The ActiveMQ and RabbitMQ connectors are just specialised versions of the Stomp ones, they were introduced to the production branches 2012/04/30 and 2012/09/13 so they've had a good bit of time to be tested before we are now finally warning that we will at some point in the future move to them as standard. I'll update the docs with this information hopefully this week Thanks for the detailed response RI - appreciated John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Stomp connector deprecated ?
I found almost by accident in the release nots for mcollective 2.2.3 : The STOMP adapter will not be maintained past this release series, we now issue deprecation warnigns ... 2012/02/12 Deprecate the stomp connector 19146 And the ticket is: (9 days old, so not from 2012) http://projects.puppetlabs.com/issues/19146 The release notes for the developpement branches are not better, they talk about the same ticket. So it was decided 9 days agos by a single guy to remove the stomp connector from the production branch of mcollective. But when I googled about 'http://projects.puppetlabs.com/issues/19146', I found nothing. No ticket about the rational for that, no warning for users. All the documentation talks about installing this connector. What a strange communication. The connector is not a small feature to change, I must recheck and re test a lot of things, talks to the security peoples about openning new holes in the firewall. What about peoples using a stomp only message broker ? You should have at least changed the documentation before, as the official requirement for Mcollective on (at least) Redhat are wrong : http://docs.puppetlabs.com/mcollective/reference/basic/gettingstarted_redhat.html Requirements We try to keep the requirements on external Gems to a minimum, you only need: • A Stomp server, tested against ActiveMQ • Ruby • Rubygems • Ruby Stomp Client -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Stomp connector deprecated ?
- Original Message - From: Fabrice Bacchella fbacche...@spamcop.net To: puppet-users@googlegroups.com Sent: Sunday, February 17, 2013 11:13:49 AM Subject: [Puppet Users] Stomp connector deprecated ? I found almost by accident in the release nots for mcollective 2.2.3 : The STOMP adapter will not be maintained past this release series, we now issue deprecation warnigns ... 2012/02/12Deprecate the stomp connector 19146 And the ticket is: (9 days old, so not from 2012) http://projects.puppetlabs.com/issues/19146 The release notes for the developpement branches are not better, they talk about the same ticket. So it was decided 9 days agos by a single guy to remove the stomp connector from the production branch of mcollective. But when I googled about 'http://projects.puppetlabs.com/issues/19146', I found nothing. No ticket about the rational for that, no warning for users. A deprecation is just a warning telling you that it will go away, we do not remove features from the middle of a production series So you should be good to continue using it for a few months to come, but when the next production series comes around it will really be gone. It's an early headsup. In the run up to the next production release the docs will be updated to reflect this deprecation You'd then use either: http://docs.puppetlabs.com/mcollective/reference/plugins/connector_activemq.html or http://docs.puppetlabs.com/mcollective/reference/plugins/connector_rabbitmq.html All the documentation talks about installing this connector. What a strange communication. The connector is not a small feature to change, I must recheck and re test a lot of things, talks to the security peoples about openning new holes in the firewall. What about peoples using a stomp only message broker ? You should have at least changed the documentation before, as the official requirement for Mcollective on (at least) Redhat are wrong : http://docs.puppetlabs.com/mcollective/reference/basic/gettingstarted_redhat.html So again, it's just a log message saying in future it will go away, nothing has changed in 2.2.x other than an additional log message. Requirements We try to keep the requirements on external Gems to a minimum, you only need: • A Stomp server, tested against ActiveMQ • Ruby • Rubygems • Ruby Stomp Client The requirements remain unchanged, even once the stomp connector is removed we still use the stomp technology but we have specialised versions of it for either ActiveMQ or RabbitMQ -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Stomp connector deprecated ?
On 17 February 2013 22:45, R.I.Pienaar r...@devco.net wrote: A deprecation is just a warning telling you that it will go away, we do not remove features from the middle of a production series Is this mcollective version 3.x or 2.3.x? So you should be good to continue using it for a few months to come, but when the next production series comes around it will really be gone. It's an early headsup. Hmm - I'm 3/4 way through my proof of concept and rolling out into lab over the coming 6-8 weeks. Production should be in 2-3 months. Should I continue with mcollective 2.2.x / stomp 1.2.2 / Active MQ 5.5 or wait a bit longer? Thanks John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Stomp connector deprecated ?
http://docs.puppetlabs.com/mcollective/reference/plugins/connector_activemq.html Specifically the Differences between ActiveMQ connector and Stomp Connector part. If you're using activemq, it's probably better in most ways to use the more specific connector, and thus not have to worry about using a deprecated component. On Sunday, February 17, 2013 10:21:11 PM UTC-8, John Warburton wrote: On 17 February 2013 22:45, R.I.Pienaar r...@devco.net javascript:wrote: A deprecation is just a warning telling you that it will go away, we do not remove features from the middle of a production series Is this mcollective version 3.x or 2.3.x? So you should be good to continue using it for a few months to come, but when the next production series comes around it will really be gone. It's an early headsup. Hmm - I'm 3/4 way through my proof of concept and rolling out into lab over the coming 6-8 weeks. Production should be in 2-3 months. Should I continue with mcollective 2.2.x / stomp 1.2.2 / Active MQ 5.5 or wait a bit longer? Thanks John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
