You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by Bryan Call <bc...@apache.org> on 2016/08/19 18:08:53 UTC
[PROPOSAL] Removing clustering support in 7.0.0
There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
The proposal is to remove the configurations options for clustering and remove the code for it.
-Bryan
Re: [PROPOSAL] Removing clustering support in 7.0.0
Posted by Phil Sorber <so...@apache.org>.
+1 on removing it.
On Fri, Aug 19, 2016, 12:09 Bryan Call <bc...@apache.org> wrote:
> There are a few features we are looking to remove in the ATS 7.0.0
> release. If you are using these features and require them, please respond
> to this email. We also need to have people that are willing to invest time
> and fix some of the bugs for these features. Your feedback is very
> important!
>
> There are a number of bugs filed against clustering. There are
> alternatives to using clustering, such as parent selection and the CARP
> plugin that Yahoo is open sourcing. If we are going to keep clustering
> supporting we would need someone that is willing to work on the bugs.
>
> The proposal is to remove the configurations options for clustering and
> remove the code for it.
>
> -Bryan
>
>
>
>
>
Re: [PROPOSAL] Removing clustering support in 7.0.0
Posted by "Steven R. Feltner" <sf...@godaddy.com>.
We are considering using cluster management-only for shared configuration for our next project. Currently, we have 12 ATS nodes all acting independently. The next project will have double that number of nodes, and I was trying to get away from having to deploy configuration changes per node.
I was also considering adding in functionality such that I could send a PURGE command to one node, and have that command be replicated across all of the nodes in the cluster, as opposed to having to send a PURGE command to each of the nodes individually.
Based on Bryan’s proposal, we are revisiting the idea of clustered ATS. I am just giving feedback that we are considering using it.
If anyone has ideas on how to manage configs across this many nodes, or about how to trigger PURGE and similar cache commands to all nodes, please let me know.
Thanks,
Steven
On 8/19/16, 2:08 PM, "Bryan Call" <bc...@apache.org> wrote:
There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
The proposal is to remove the configurations options for clustering and remove the code for it.
-Bryan
Re: [PROPOSAL] Removing clustering support in 7.0.0
Posted by Phil Sorber <so...@apache.org>.
+1 on removing it.
On Fri, Aug 19, 2016, 12:09 Bryan Call <bc...@apache.org> wrote:
> There are a few features we are looking to remove in the ATS 7.0.0
> release. If you are using these features and require them, please respond
> to this email. We also need to have people that are willing to invest time
> and fix some of the bugs for these features. Your feedback is very
> important!
>
> There are a number of bugs filed against clustering. There are
> alternatives to using clustering, such as parent selection and the CARP
> plugin that Yahoo is open sourcing. If we are going to keep clustering
> supporting we would need someone that is willing to work on the bugs.
>
> The proposal is to remove the configurations options for clustering and
> remove the code for it.
>
> -Bryan
>
>
>
>
>
Re: [PROPOSAL] Removing clustering support in7.0.0
Posted by Reindl Harald <h....@thelounge.net>.
Am 30.08.2016 um 01:07 schrieb Nguyen, Hai:
> We are using clustering to share configuration settings in environments
> that do load balancing across multiple proxies. Administrators that
> have large deployments would need to configure every proxy manually
no
they just would use a config management or just write some scripts to
pull changes over SSH or https from a common source and genearte the
local configs on the target machine as they do for every other software
Re: Re: Re: [PROPOSAL] Removing clustering support in7.0.0
Posted by Igor Galić <i....@brainsware.org>.
why would anyone configure anything manually in the age of puppet, chef,
ansible, and a million other config management tools?
--
Igor Galić
Tel: +43 (0) 664 886 22 883
Mail: i.galic@brainsware.org
URL: https://brainsware.org/
GPG: 8716 7A9F 989B ABD5 100F 4008 F266 55D6 2998 1641
On Tue, 30 Aug 2016, at 01:07, Nguyen, Hai wrote:
> We are using clustering to share configuration settings in
> environments that do load balancing across multiple proxies.
> Administrators that have large deployments would need to configure
> every proxy manually.
>
> -Hai
> *From:* Bryan Call [mailto:bcall@apache.org] *Sent:* Monday, August
> 29, 2016 3:52 PM *To:* Nguyen, Hai *Cc:* dev@trafficserver.apache.org;
> users@trafficserver.apache.org *Subject:* EXTERNAL: Re: Re: [PROPOSAL]
> Removing clustering support in 7.0.0
>
> Can you talk about how you are using the clustering feature? Would
> parent proxying also work for your use case?
>
> -Bryan
>
>
>
>> On Aug 29, 2016, at 3:30 PM, Nguyen, Hai
>> <hn...@forcepoint.com> wrote:
>>
>> I’m sorry for sending the feedback on this proposal late. Can we
>> please keep the clustering feature? We’ve been using it
>> extensively here.
>>
>> Thanks,
>> -Hai
>>
>> *From:* Bryan Call [mailto:bcall@apache.org] *Sent:* Monday, August
>> 29, 2016 3:20 PM *To:* dev@trafficserver.apache.org *Cc:*
>> users@trafficserver.apache.org *Subject:* EXTERNAL: Re: [PROPOSAL]
>> Removing clustering support in 7.0.0
>>
>> Thank you for all the feedback on this proposal. Removing clustering
>> support will be done in 7.0.0.
>>
>> -Bryan
>>
>>
>>
>>> On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zw...@apache.org> wrote:
>>>
>>>>
>>>> On Aug 19, 2016, at 3:18 PM, James Peach <jp...@apache.org> wrote:
>>>>
>>>>
>>>>
>>>> On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org> wrote:
>>>>
>>>> There are a few features we are looking to remove in the ATS 7.0.0
>>>> release. If you are using these features and require them, please
>>>> respond to this email. We also need to have people that are
>>>> willing to invest time and fix some of the bugs for these
>>>> features. Your feedback is very important!
>>>>
>>>> There are a number of bugs filed against clustering. There are
>>>> alternatives to using clustering, such as parent selection and the
>>>> CARP plugin that Yahoo is open sourcing. If we are going to keep
>>>> clustering supporting we would need someone that is willing to
>>>> work on the bugs.
>>>>
>>>> The proposal is to remove the configurations options for
>>>> clustering and remove the code for it.
>>>>
>>>> I've seen a few people asking about clustering recently, so it
>>>> seems like there is interest. But it *really* needs a code owner to
>>>> make it live. Count me as a +0.
>>>
>>>
>>> A serious issue with the lack of developer support is that other
>>> areas of the code suffers. Meaning, we have a hard time making
>>> progress with other areas (like metrics, or configurations), because
>>> we don’t have anyone who’s testing and maintaining the clustering
>>> feature.
>>>
>>> This is a tough one though, the general feature is useful, but
>>> we’re seriously crippling ourselves with an unsupported legacy
>>> system.
>>>
>>> +0 from me as well.
>>>
>>> — Leif
>>
>>
>>
>> Scanned by Forcepoint Email Security Gateway Click here[1] to report
>> this email as spam
>
>
>
> Scanned by Forcepoint Email Security Gateway Click here[2] to report
> this email as spam
>
>
>
>
Links:
1. https://esgpem.websense.com/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5e05ab970ae3ca9cc1d4d703e3a16bba58faf015599e14c7422c0fe0e50f83ec29c6a066df750951d586cbd4b9c445f9f7ede47b5ff2432e6db5d9ab138ccf9f92096d50fce4041f5c685b71e990171ff43cba7313b924b534e998c2f8842e648735033d6e98ce3c50b6ef6e38032c0f11163d221beb5819204db1eb665a0f03fd0ef0444d79aef489
2. https://esgpem.websense.com:443/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5eac36c03d0e7ff0b57b7e3ed898c04d3b57443d4dd6633da2a02f7e00cad8ee51e76369bb7724613990fab7f6a77e81c146894a278e2586fe25ecf0e847b3e8c92d9fea959c461e1b4b8eadc7dda39f476525df499317859b67ad36e597e46f717050f777046e98b211aa34ec38cc86034854bfa41cee96304774a1766865ea10
Re: [PROPOSAL] Removing clustering support in 7.0.0
Posted by Thomas Jackson <ja...@gmail.com>.
Also late response... sorry about that.
I'm +1 on removing this, "clustering" as a concept is an okay thing-- but
clustering in ATS today requires L2 connectivity-- which in practice most
people can't really use.
Even if that was a viable option, the clustering doesn't give enough
controls for operability (canaries, etc.) so it ends up being more of a
problem.
On Sun, Sep 11, 2016 at 4:09 PM, McClimont, Aaron (SACE) <
Aaron.McClimont@sa.gov.au> wrote:
> Bryan,
>
> Some (more) late feedback for the proposal to remove clustering
> support... We are also using clustering for the management of configuration
> between multiple load balancing nodes using cluster.type = 1 (full),
> although we could get by with cluster.type = 2 (management only). We would
> certainly appreciate at least the configuration management being supported
> in 7.0.0+, we don't specifically need the clustered cache feature.
>
> Regards,
>
> Aaron McClimont
>
> -----Original Message-----
> From: Bryan Call [mailto:bcall@apache.org]
> Sent: Friday, 9 September 2016 4:29 AM
> To: users@trafficserver.apache.org
> Cc: dev@trafficserver.apache.org
> Subject: [PROPOSAL] Removing clustering support in 7.0.0
>
> After discussing with the other committers on the project we have decided
> to remove the clustering feature in ATS 7.0.0.
>
> There are people in the community that are using configuration management
> (Puppet, Chef, Salt, etc.) for large installations. If you need help on
> syncing configuration outside of ATS, there is a very good chance other
> people in the community would be willing to help. This might be a great
> opportunity to add some tools or examples to ATS to help out other people
> in the community with configuration management.
>
> Thank you,
>
> -Bryan
>
>
>
> > On Aug 29, 2016, at 4:39 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
> >
> > We are running Management-Only clustering (cluster.type = 2)
> >
> > From: Bryan Call [mailto:bcall@apache.org]
> > Sent: Monday, August 29, 2016 4:33 PM
> > To: Nguyen, Hai
> > Cc: dev@trafficserver.apache.org; users@trafficserver.apache.org
> > Subject: EXTERNAL: Re: Re: Re: [PROPOSAL] Removing clustering support
> > in7.0.0
> >
> > What cluster mode are you running (proxy.local.cluster.type)?
> >
> > -Bryan
> >
> >
> >
> >
> > On Aug 29, 2016, at 4:07 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
> >
> > We are using clustering to share configuration settings in environments
> that do load balancing across multiple proxies. Administrators that have
> large deployments would need to configure every proxy manually.
> >
> > -Hai
> > From: Bryan Call [mailto:bcall@apache.org]
> > Sent: Monday, August 29, 2016 3:52 PM
> > To: Nguyen, Hai
> > Cc: dev@trafficserver.apache.org; users@trafficserver.apache.org
> > Subject: EXTERNAL: Re: Re: [PROPOSAL] Removing clustering support in
> > 7.0.0
> >
> > Can you talk about how you are using the clustering feature? Would
> parent proxying also work for your use case?
> >
> > -Bryan
> >
> >
> >
> >
> > On Aug 29, 2016, at 3:30 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
> >
> > I’m sorry for sending the feedback on this proposal late. Can we please
> keep the clustering feature? We’ve been using it extensively here.
> >
> > Thanks,
> > -Hai
> >
> > From: Bryan Call [mailto:bcall@apache.org]
> > Sent: Monday, August 29, 2016 3:20 PM
> > To: dev@trafficserver.apache.org
> > Cc: users@trafficserver.apache.org
> > Subject: EXTERNAL: Re: [PROPOSAL] Removing clustering support in 7.0.0
> >
> > Thank you for all the feedback on this proposal. Removing clustering
> support will be done in 7.0.0.
> >
> > -Bryan
> >
> >
> >
> >
> > On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zw...@apache.org> wrote:
> >
> >
> > On Aug 19, 2016, at 3:18 PM, James Peach <jp...@apache.org> wrote:
> >
> >
> >
> >
> >
> > On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org> wrote:
> >
> > There are a few features we are looking to remove in the ATS 7.0.0
> release. If you are using these features and require them, please respond
> to this email. We also need to have people that are willing to invest time
> and fix some of the bugs for these features. Your feedback is very
> important!
> >
> > There are a number of bugs filed against clustering. There are
> alternatives to using clustering, such as parent selection and the CARP
> plugin that Yahoo is open sourcing. If we are going to keep clustering
> supporting we would need someone that is willing to work on the bugs.
> >
> > The proposal is to remove the configurations options for clustering and
> remove the code for it.
> >
> > I've seen a few people asking about clustering recently, so it seems
> like there is interest. But it *really* needs a code owner to make it live.
> Count me as a +0.
> >
> >
> > A serious issue with the lack of developer support is that other areas
> of the code suffers. Meaning, we have a hard time making progress with
> other areas (like metrics, or configurations), because we don’t have anyone
> who’s testing and maintaining the clustering feature.
> >
> > This is a tough one though, the general feature is useful, but we’re
> seriously crippling ourselves with an unsupported legacy system.
> >
> > +0 from me as well.
> >
> > — Leif
> >
> >
> >
> > Scanned by Forcepoint Email Security Gateway Click here to report this
> > email as spam
> >
> >
> >
> > Scanned by Forcepoint Email Security Gateway Click here to report this
> > email as spam
> >
> >
> >
> > Scanned by Forcepoint Email Security Gateway Click here to report this
> > email as spam
>
>
RE: [PROPOSAL] Removing clustering support in 7.0.0
Posted by "McClimont, Aaron (SACE)" <Aa...@sa.gov.au>.
Bryan,
Some (more) late feedback for the proposal to remove clustering support... We are also using clustering for the management of configuration between multiple load balancing nodes using cluster.type = 1 (full), although we could get by with cluster.type = 2 (management only). We would certainly appreciate at least the configuration management being supported in 7.0.0+, we don't specifically need the clustered cache feature.
Regards,
Aaron McClimont
-----Original Message-----
From: Bryan Call [mailto:bcall@apache.org]
Sent: Friday, 9 September 2016 4:29 AM
To: users@trafficserver.apache.org
Cc: dev@trafficserver.apache.org
Subject: [PROPOSAL] Removing clustering support in 7.0.0
After discussing with the other committers on the project we have decided to remove the clustering feature in ATS 7.0.0.
There are people in the community that are using configuration management (Puppet, Chef, Salt, etc.) for large installations. If you need help on syncing configuration outside of ATS, there is a very good chance other people in the community would be willing to help. This might be a great opportunity to add some tools or examples to ATS to help out other people in the community with configuration management.
Thank you,
-Bryan
> On Aug 29, 2016, at 4:39 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
>
> We are running Management-Only clustering (cluster.type = 2)
>
> From: Bryan Call [mailto:bcall@apache.org]
> Sent: Monday, August 29, 2016 4:33 PM
> To: Nguyen, Hai
> Cc: dev@trafficserver.apache.org; users@trafficserver.apache.org
> Subject: EXTERNAL: Re: Re: Re: [PROPOSAL] Removing clustering support
> in7.0.0
>
> What cluster mode are you running (proxy.local.cluster.type)?
>
> -Bryan
>
>
>
>
> On Aug 29, 2016, at 4:07 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
>
> We are using clustering to share configuration settings in environments that do load balancing across multiple proxies. Administrators that have large deployments would need to configure every proxy manually.
>
> -Hai
> From: Bryan Call [mailto:bcall@apache.org]
> Sent: Monday, August 29, 2016 3:52 PM
> To: Nguyen, Hai
> Cc: dev@trafficserver.apache.org; users@trafficserver.apache.org
> Subject: EXTERNAL: Re: Re: [PROPOSAL] Removing clustering support in
> 7.0.0
>
> Can you talk about how you are using the clustering feature? Would parent proxying also work for your use case?
>
> -Bryan
>
>
>
>
> On Aug 29, 2016, at 3:30 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
>
> I’m sorry for sending the feedback on this proposal late. Can we please keep the clustering feature? We’ve been using it extensively here.
>
> Thanks,
> -Hai
>
> From: Bryan Call [mailto:bcall@apache.org]
> Sent: Monday, August 29, 2016 3:20 PM
> To: dev@trafficserver.apache.org
> Cc: users@trafficserver.apache.org
> Subject: EXTERNAL: Re: [PROPOSAL] Removing clustering support in 7.0.0
>
> Thank you for all the feedback on this proposal. Removing clustering support will be done in 7.0.0.
>
> -Bryan
>
>
>
>
> On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zw...@apache.org> wrote:
>
>
> On Aug 19, 2016, at 3:18 PM, James Peach <jp...@apache.org> wrote:
>
>
>
>
>
> On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org> wrote:
>
> There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
>
> There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
>
> The proposal is to remove the configurations options for clustering and remove the code for it.
>
> I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
>
>
> A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
>
> This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
>
> +0 from me as well.
>
> — Leif
>
>
>
> Scanned by Forcepoint Email Security Gateway Click here to report this
> email as spam
>
>
>
> Scanned by Forcepoint Email Security Gateway Click here to report this
> email as spam
>
>
>
> Scanned by Forcepoint Email Security Gateway Click here to report this
> email as spam
RE: [PROPOSAL] Removing clustering support in 7.0.0
Posted by "McClimont, Aaron (SACE)" <Aa...@sa.gov.au>.
Bryan,
Some (more) late feedback for the proposal to remove clustering support... We are also using clustering for the management of configuration between multiple load balancing nodes using cluster.type = 1 (full), although we could get by with cluster.type = 2 (management only). We would certainly appreciate at least the configuration management being supported in 7.0.0+, we don't specifically need the clustered cache feature.
Regards,
Aaron McClimont
-----Original Message-----
From: Bryan Call [mailto:bcall@apache.org]
Sent: Friday, 9 September 2016 4:29 AM
To: users@trafficserver.apache.org
Cc: dev@trafficserver.apache.org
Subject: [PROPOSAL] Removing clustering support in 7.0.0
After discussing with the other committers on the project we have decided to remove the clustering feature in ATS 7.0.0.
There are people in the community that are using configuration management (Puppet, Chef, Salt, etc.) for large installations. If you need help on syncing configuration outside of ATS, there is a very good chance other people in the community would be willing to help. This might be a great opportunity to add some tools or examples to ATS to help out other people in the community with configuration management.
Thank you,
-Bryan
> On Aug 29, 2016, at 4:39 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
>
> We are running Management-Only clustering (cluster.type = 2)
>
> From: Bryan Call [mailto:bcall@apache.org]
> Sent: Monday, August 29, 2016 4:33 PM
> To: Nguyen, Hai
> Cc: dev@trafficserver.apache.org; users@trafficserver.apache.org
> Subject: EXTERNAL: Re: Re: Re: [PROPOSAL] Removing clustering support
> in7.0.0
>
> What cluster mode are you running (proxy.local.cluster.type)?
>
> -Bryan
>
>
>
>
> On Aug 29, 2016, at 4:07 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
>
> We are using clustering to share configuration settings in environments that do load balancing across multiple proxies. Administrators that have large deployments would need to configure every proxy manually.
>
> -Hai
> From: Bryan Call [mailto:bcall@apache.org]
> Sent: Monday, August 29, 2016 3:52 PM
> To: Nguyen, Hai
> Cc: dev@trafficserver.apache.org; users@trafficserver.apache.org
> Subject: EXTERNAL: Re: Re: [PROPOSAL] Removing clustering support in
> 7.0.0
>
> Can you talk about how you are using the clustering feature? Would parent proxying also work for your use case?
>
> -Bryan
>
>
>
>
> On Aug 29, 2016, at 3:30 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
>
> I’m sorry for sending the feedback on this proposal late. Can we please keep the clustering feature? We’ve been using it extensively here.
>
> Thanks,
> -Hai
>
> From: Bryan Call [mailto:bcall@apache.org]
> Sent: Monday, August 29, 2016 3:20 PM
> To: dev@trafficserver.apache.org
> Cc: users@trafficserver.apache.org
> Subject: EXTERNAL: Re: [PROPOSAL] Removing clustering support in 7.0.0
>
> Thank you for all the feedback on this proposal. Removing clustering support will be done in 7.0.0.
>
> -Bryan
>
>
>
>
> On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zw...@apache.org> wrote:
>
>
> On Aug 19, 2016, at 3:18 PM, James Peach <jp...@apache.org> wrote:
>
>
>
>
>
> On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org> wrote:
>
> There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
>
> There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
>
> The proposal is to remove the configurations options for clustering and remove the code for it.
>
> I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
>
>
> A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
>
> This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
>
> +0 from me as well.
>
> — Leif
>
>
>
> Scanned by Forcepoint Email Security Gateway Click here to report this
> email as spam
>
>
>
> Scanned by Forcepoint Email Security Gateway Click here to report this
> email as spam
>
>
>
> Scanned by Forcepoint Email Security Gateway Click here to report this
> email as spam
[PROPOSAL] Removing clustering support in 7.0.0
Posted by Bryan Call <bc...@apache.org>.
After discussing with the other committers on the project we have decided to remove the clustering feature in ATS 7.0.0.
There are people in the community that are using configuration management (Puppet, Chef, Salt, etc.) for large installations. If you need help on syncing configuration outside of ATS, there is a very good chance other people in the community would be willing to help. This might be a great opportunity to add some tools or examples to ATS to help out other people in the community with configuration management.
Thank you,
-Bryan
> On Aug 29, 2016, at 4:39 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
>
> We are running Management-Only clustering (cluster.type = 2)
>
> From: Bryan Call [mailto:bcall@apache.org]
> Sent: Monday, August 29, 2016 4:33 PM
> To: Nguyen, Hai
> Cc: dev@trafficserver.apache.org; users@trafficserver.apache.org
> Subject: EXTERNAL: Re: Re: Re: [PROPOSAL] Removing clustering support in7.0.0
>
> What cluster mode are you running (proxy.local.cluster.type)?
>
> -Bryan
>
>
>
>
> On Aug 29, 2016, at 4:07 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
>
> We are using clustering to share configuration settings in environments that do load balancing across multiple proxies. Administrators that have large deployments would need to configure every proxy manually.
>
> -Hai
> From: Bryan Call [mailto:bcall@apache.org]
> Sent: Monday, August 29, 2016 3:52 PM
> To: Nguyen, Hai
> Cc: dev@trafficserver.apache.org; users@trafficserver.apache.org
> Subject: EXTERNAL: Re: Re: [PROPOSAL] Removing clustering support in 7.0.0
>
> Can you talk about how you are using the clustering feature? Would parent proxying also work for your use case?
>
> -Bryan
>
>
>
>
> On Aug 29, 2016, at 3:30 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
>
> I’m sorry for sending the feedback on this proposal late. Can we please keep the clustering feature? We’ve been using it extensively here.
>
> Thanks,
> -Hai
>
> From: Bryan Call [mailto:bcall@apache.org]
> Sent: Monday, August 29, 2016 3:20 PM
> To: dev@trafficserver.apache.org
> Cc: users@trafficserver.apache.org
> Subject: EXTERNAL: Re: [PROPOSAL] Removing clustering support in 7.0.0
>
> Thank you for all the feedback on this proposal. Removing clustering support will be done in 7.0.0.
>
> -Bryan
>
>
>
>
> On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zw...@apache.org> wrote:
>
>
> On Aug 19, 2016, at 3:18 PM, James Peach <jp...@apache.org> wrote:
>
>
>
>
>
> On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org> wrote:
>
> There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
>
> There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
>
> The proposal is to remove the configurations options for clustering and remove the code for it.
>
> I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
>
>
> A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
>
> This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
>
> +0 from me as well.
>
> — Leif
>
>
>
> Scanned by Forcepoint Email Security Gateway
> Click here to report this email as spam
>
>
>
> Scanned by Forcepoint Email Security Gateway
> Click here to report this email as spam
>
>
>
> Scanned by Forcepoint Email Security Gateway
> Click here to report this email as spam
[PROPOSAL] Removing clustering support in 7.0.0
Posted by Bryan Call <bc...@apache.org>.
After discussing with the other committers on the project we have decided to remove the clustering feature in ATS 7.0.0.
There are people in the community that are using configuration management (Puppet, Chef, Salt, etc.) for large installations. If you need help on syncing configuration outside of ATS, there is a very good chance other people in the community would be willing to help. This might be a great opportunity to add some tools or examples to ATS to help out other people in the community with configuration management.
Thank you,
-Bryan
> On Aug 29, 2016, at 4:39 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
>
> We are running Management-Only clustering (cluster.type = 2)
>
> From: Bryan Call [mailto:bcall@apache.org]
> Sent: Monday, August 29, 2016 4:33 PM
> To: Nguyen, Hai
> Cc: dev@trafficserver.apache.org; users@trafficserver.apache.org
> Subject: EXTERNAL: Re: Re: Re: [PROPOSAL] Removing clustering support in7.0.0
>
> What cluster mode are you running (proxy.local.cluster.type)?
>
> -Bryan
>
>
>
>
> On Aug 29, 2016, at 4:07 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
>
> We are using clustering to share configuration settings in environments that do load balancing across multiple proxies. Administrators that have large deployments would need to configure every proxy manually.
>
> -Hai
> From: Bryan Call [mailto:bcall@apache.org]
> Sent: Monday, August 29, 2016 3:52 PM
> To: Nguyen, Hai
> Cc: dev@trafficserver.apache.org; users@trafficserver.apache.org
> Subject: EXTERNAL: Re: Re: [PROPOSAL] Removing clustering support in 7.0.0
>
> Can you talk about how you are using the clustering feature? Would parent proxying also work for your use case?
>
> -Bryan
>
>
>
>
> On Aug 29, 2016, at 3:30 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
>
> I’m sorry for sending the feedback on this proposal late. Can we please keep the clustering feature? We’ve been using it extensively here.
>
> Thanks,
> -Hai
>
> From: Bryan Call [mailto:bcall@apache.org]
> Sent: Monday, August 29, 2016 3:20 PM
> To: dev@trafficserver.apache.org
> Cc: users@trafficserver.apache.org
> Subject: EXTERNAL: Re: [PROPOSAL] Removing clustering support in 7.0.0
>
> Thank you for all the feedback on this proposal. Removing clustering support will be done in 7.0.0.
>
> -Bryan
>
>
>
>
> On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zw...@apache.org> wrote:
>
>
> On Aug 19, 2016, at 3:18 PM, James Peach <jp...@apache.org> wrote:
>
>
>
>
>
> On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org> wrote:
>
> There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
>
> There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
>
> The proposal is to remove the configurations options for clustering and remove the code for it.
>
> I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
>
>
> A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
>
> This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
>
> +0 from me as well.
>
> — Leif
>
>
>
> Scanned by Forcepoint Email Security Gateway
> Click here to report this email as spam
>
>
>
> Scanned by Forcepoint Email Security Gateway
> Click here to report this email as spam
>
>
>
> Scanned by Forcepoint Email Security Gateway
> Click here to report this email as spam
RE: Re: Re: Re: [PROPOSAL] Removing clustering supportin7.0.0
Posted by "Nguyen, Hai" <hn...@forcepoint.com>.
We are running Management-Only clustering (cluster.type = 2)
From: Bryan Call [mailto:bcall@apache.org]
Sent: Monday, August 29, 2016 4:33 PM
To: Nguyen, Hai
Cc: dev@trafficserver.apache.org; users@trafficserver.apache.org
Subject: EXTERNAL: Re: Re: Re: [PROPOSAL] Removing clustering support in7.0.0
What cluster mode are you running (proxy.local.cluster.type)?
-Bryan
On Aug 29, 2016, at 4:07 PM, Nguyen, Hai <hn...@forcepoint.com>> wrote:
We are using clustering to share configuration settings in environments that do load balancing across multiple proxies. Administrators that have large deployments would need to configure every proxy manually.
-Hai
From: Bryan Call [mailto:bcall@apache.org]
Sent: Monday, August 29, 2016 3:52 PM
To: Nguyen, Hai
Cc: dev@trafficserver.apache.org<ma...@trafficserver.apache.org>; users@trafficserver.apache.org<ma...@trafficserver.apache.org>
Subject: EXTERNAL: Re: Re: [PROPOSAL] Removing clustering support in 7.0.0
Can you talk about how you are using the clustering feature? Would parent proxying also work for your use case?
-Bryan
On Aug 29, 2016, at 3:30 PM, Nguyen, Hai <hn...@forcepoint.com>> wrote:
I’m sorry for sending the feedback on this proposal late. Can we please keep the clustering feature? We’ve been using it extensively here.
Thanks,
-Hai
From: Bryan Call [mailto:bcall@apache.org]
Sent: Monday, August 29, 2016 3:20 PM
To: dev@trafficserver.apache.org<ma...@trafficserver.apache.org>
Cc: users@trafficserver.apache.org<ma...@trafficserver.apache.org>
Subject: EXTERNAL: Re: [PROPOSAL] Removing clustering support in 7.0.0
Thank you for all the feedback on this proposal. Removing clustering support will be done in 7.0.0.
-Bryan
On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zw...@apache.org>> wrote:
On Aug 19, 2016, at 3:18 PM, James Peach <jp...@apache.org>> wrote:
On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org>> wrote:
There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
The proposal is to remove the configurations options for clustering and remove the code for it.
I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
+0 from me as well.
— Leif
Scanned by Forcepoint Email Security Gateway
Click here<https://esgpem.websense.com/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5e05ab970ae3ca9cc1d4d703e3a16bba58faf015599e14c7422c0fe0e50f83ec29c6a066df750951d586cbd4b9c445f9f7ede47b5ff2432e6db5d9ab138ccf9f92096d50fce4041f5c685b71e990171ff43cba7313b924b534e998c2f8842e648735033d6e98ce3c50b6ef6e38032c0f11163d221beb5819204db1eb665a0f03fd0ef0444d79aef489> to report this email as spam
Scanned by Forcepoint Email Security Gateway
Click here<https://esgpem.websense.com/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5eac36c03d0e7ff0b57b7e3ed898c04d3b57443d4dd6633da2a02f7e00cad8ee51e76369bb7724613990fab7f6a77e81c146894a278e2586fe25ecf0e847b3e8c92d9fea959c461e1b4b8eadc7dda39f476525df499317859b67ad36e597e46f717050f777046e98b211aa34ec38cc86034854bfa41cee96304774a1766865ea10> to report this email as spam
Scanned by Forcepoint Email Security Gateway
Click here<https://esgpem.websense.com:443/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5ec25e4a1f55784b0df5ba82ae80362d547e15c0fc90303b382c0fe0e50f83ec29c6a066df750951d586cbd4b9c445f9f7ede47b5ff2432e6db5d9ab138ccf9f92096d50fce4041f5c685b71e990171ff43cba7313b924b534e998c2f8842e648735033d6e98ce3c50b6ef6e38032c0f11163d221beb5819204db1eb665a0f03fd0ef0444d79aef489> to report this email as spam
RE: Re: Re: Re: [PROPOSAL] Removing clustering supportin7.0.0
Posted by "Nguyen, Hai" <hn...@forcepoint.com>.
We are running Management-Only clustering (cluster.type = 2)
From: Bryan Call [mailto:bcall@apache.org]
Sent: Monday, August 29, 2016 4:33 PM
To: Nguyen, Hai
Cc: dev@trafficserver.apache.org; users@trafficserver.apache.org
Subject: EXTERNAL: Re: Re: Re: [PROPOSAL] Removing clustering support in7.0.0
What cluster mode are you running (proxy.local.cluster.type)?
-Bryan
On Aug 29, 2016, at 4:07 PM, Nguyen, Hai <hn...@forcepoint.com>> wrote:
We are using clustering to share configuration settings in environments that do load balancing across multiple proxies. Administrators that have large deployments would need to configure every proxy manually.
-Hai
From: Bryan Call [mailto:bcall@apache.org]
Sent: Monday, August 29, 2016 3:52 PM
To: Nguyen, Hai
Cc: dev@trafficserver.apache.org<ma...@trafficserver.apache.org>; users@trafficserver.apache.org<ma...@trafficserver.apache.org>
Subject: EXTERNAL: Re: Re: [PROPOSAL] Removing clustering support in 7.0.0
Can you talk about how you are using the clustering feature? Would parent proxying also work for your use case?
-Bryan
On Aug 29, 2016, at 3:30 PM, Nguyen, Hai <hn...@forcepoint.com>> wrote:
I’m sorry for sending the feedback on this proposal late. Can we please keep the clustering feature? We’ve been using it extensively here.
Thanks,
-Hai
From: Bryan Call [mailto:bcall@apache.org]
Sent: Monday, August 29, 2016 3:20 PM
To: dev@trafficserver.apache.org<ma...@trafficserver.apache.org>
Cc: users@trafficserver.apache.org<ma...@trafficserver.apache.org>
Subject: EXTERNAL: Re: [PROPOSAL] Removing clustering support in 7.0.0
Thank you for all the feedback on this proposal. Removing clustering support will be done in 7.0.0.
-Bryan
On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zw...@apache.org>> wrote:
On Aug 19, 2016, at 3:18 PM, James Peach <jp...@apache.org>> wrote:
On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org>> wrote:
There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
The proposal is to remove the configurations options for clustering and remove the code for it.
I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
+0 from me as well.
— Leif
Scanned by Forcepoint Email Security Gateway
Click here<https://esgpem.websense.com/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5e05ab970ae3ca9cc1d4d703e3a16bba58faf015599e14c7422c0fe0e50f83ec29c6a066df750951d586cbd4b9c445f9f7ede47b5ff2432e6db5d9ab138ccf9f92096d50fce4041f5c685b71e990171ff43cba7313b924b534e998c2f8842e648735033d6e98ce3c50b6ef6e38032c0f11163d221beb5819204db1eb665a0f03fd0ef0444d79aef489> to report this email as spam
Scanned by Forcepoint Email Security Gateway
Click here<https://esgpem.websense.com/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5eac36c03d0e7ff0b57b7e3ed898c04d3b57443d4dd6633da2a02f7e00cad8ee51e76369bb7724613990fab7f6a77e81c146894a278e2586fe25ecf0e847b3e8c92d9fea959c461e1b4b8eadc7dda39f476525df499317859b67ad36e597e46f717050f777046e98b211aa34ec38cc86034854bfa41cee96304774a1766865ea10> to report this email as spam
Scanned by Forcepoint Email Security Gateway
Click here<https://esgpem.websense.com:443/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5ec25e4a1f55784b0df5ba82ae80362d547e15c0fc90303b382c0fe0e50f83ec29c6a066df750951d586cbd4b9c445f9f7ede47b5ff2432e6db5d9ab138ccf9f92096d50fce4041f5c685b71e990171ff43cba7313b924b534e998c2f8842e648735033d6e98ce3c50b6ef6e38032c0f11163d221beb5819204db1eb665a0f03fd0ef0444d79aef489> to report this email as spam
Re: Re: Re: [PROPOSAL] Removing clustering support in7.0.0
Posted by Bryan Call <bc...@apache.org>.
What cluster mode are you running (proxy.local.cluster.type)?
-Bryan
> On Aug 29, 2016, at 4:07 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
>
> We are using clustering to share configuration settings in environments that do load balancing across multiple proxies. Administrators that have large deployments would need to configure every proxy manually.
>
> -Hai
> From: Bryan Call [mailto:bcall@apache.org]
> Sent: Monday, August 29, 2016 3:52 PM
> To: Nguyen, Hai
> Cc: dev@trafficserver.apache.org; users@trafficserver.apache.org
> Subject: EXTERNAL: Re: Re: [PROPOSAL] Removing clustering support in 7.0.0
>
> Can you talk about how you are using the clustering feature? Would parent proxying also work for your use case?
>
> -Bryan
>
>
>
>
> On Aug 29, 2016, at 3:30 PM, Nguyen, Hai <hnguyen@forcepoint.com <ma...@forcepoint.com>> wrote:
>
> I’m sorry for sending the feedback on this proposal late. Can we please keep the clustering feature? We’ve been using it extensively here.
>
> Thanks,
> -Hai
>
> From: Bryan Call [mailto:bcall@apache.org <ma...@apache.org>]
> Sent: Monday, August 29, 2016 3:20 PM
> To: dev@trafficserver.apache.org <ma...@trafficserver.apache.org>
> Cc: users@trafficserver.apache.org <ma...@trafficserver.apache.org>
> Subject: EXTERNAL: Re: [PROPOSAL] Removing clustering support in 7.0.0
>
> Thank you for all the feedback on this proposal. Removing clustering support will be done in 7.0.0.
>
> -Bryan
>
>
>
>
> On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zwoop@apache.org <ma...@apache.org>> wrote:
>
>
> On Aug 19, 2016, at 3:18 PM, James Peach <jpeach@apache.org <ma...@apache.org>> wrote:
>
>
>
>
> On Aug 19, 2016, at 11:08 AM, Bryan Call <bcall@apache.org <ma...@apache.org>> wrote:
>
> There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
>
> There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
>
> The proposal is to remove the configurations options for clustering and remove the code for it.
>
> I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
>
>
> A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
>
> This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
>
> +0 from me as well.
>
> — Leif
>
>
>
> Scanned by Forcepoint Email Security Gateway
> Click here <https://esgpem.websense.com/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5e05ab970ae3ca9cc1d4d703e3a16bba58faf015599e14c7422c0fe0e50f83ec29c6a066df750951d586cbd4b9c445f9f7ede47b5ff2432e6db5d9ab138ccf9f92096d50fce4041f5c685b71e990171ff43cba7313b924b534e998c2f8842e648735033d6e98ce3c50b6ef6e38032c0f11163d221beb5819204db1eb665a0f03fd0ef0444d79aef489> to report this email as spam
>
>
>
> Scanned by Forcepoint Email Security Gateway
> Click here <https://esgpem.websense.com/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5eac36c03d0e7ff0b57b7e3ed898c04d3b57443d4dd6633da2a02f7e00cad8ee51e76369bb7724613990fab7f6a77e81c146894a278e2586fe25ecf0e847b3e8c92d9fea959c461e1b4b8eadc7dda39f476525df499317859b67ad36e597e46f717050f777046e98b211aa34ec38cc86034854bfa41cee96304774a1766865ea10> to report this email as spam
Re: Re: Re: [PROPOSAL] Removing clustering support in7.0.0
Posted by Bryan Call <bc...@apache.org>.
What cluster mode are you running (proxy.local.cluster.type)?
-Bryan
> On Aug 29, 2016, at 4:07 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
>
> We are using clustering to share configuration settings in environments that do load balancing across multiple proxies. Administrators that have large deployments would need to configure every proxy manually.
>
> -Hai
> From: Bryan Call [mailto:bcall@apache.org]
> Sent: Monday, August 29, 2016 3:52 PM
> To: Nguyen, Hai
> Cc: dev@trafficserver.apache.org; users@trafficserver.apache.org
> Subject: EXTERNAL: Re: Re: [PROPOSAL] Removing clustering support in 7.0.0
>
> Can you talk about how you are using the clustering feature? Would parent proxying also work for your use case?
>
> -Bryan
>
>
>
>
> On Aug 29, 2016, at 3:30 PM, Nguyen, Hai <hnguyen@forcepoint.com <ma...@forcepoint.com>> wrote:
>
> I’m sorry for sending the feedback on this proposal late. Can we please keep the clustering feature? We’ve been using it extensively here.
>
> Thanks,
> -Hai
>
> From: Bryan Call [mailto:bcall@apache.org <ma...@apache.org>]
> Sent: Monday, August 29, 2016 3:20 PM
> To: dev@trafficserver.apache.org <ma...@trafficserver.apache.org>
> Cc: users@trafficserver.apache.org <ma...@trafficserver.apache.org>
> Subject: EXTERNAL: Re: [PROPOSAL] Removing clustering support in 7.0.0
>
> Thank you for all the feedback on this proposal. Removing clustering support will be done in 7.0.0.
>
> -Bryan
>
>
>
>
> On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zwoop@apache.org <ma...@apache.org>> wrote:
>
>
> On Aug 19, 2016, at 3:18 PM, James Peach <jpeach@apache.org <ma...@apache.org>> wrote:
>
>
>
>
> On Aug 19, 2016, at 11:08 AM, Bryan Call <bcall@apache.org <ma...@apache.org>> wrote:
>
> There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
>
> There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
>
> The proposal is to remove the configurations options for clustering and remove the code for it.
>
> I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
>
>
> A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
>
> This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
>
> +0 from me as well.
>
> — Leif
>
>
>
> Scanned by Forcepoint Email Security Gateway
> Click here <https://esgpem.websense.com/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5e05ab970ae3ca9cc1d4d703e3a16bba58faf015599e14c7422c0fe0e50f83ec29c6a066df750951d586cbd4b9c445f9f7ede47b5ff2432e6db5d9ab138ccf9f92096d50fce4041f5c685b71e990171ff43cba7313b924b534e998c2f8842e648735033d6e98ce3c50b6ef6e38032c0f11163d221beb5819204db1eb665a0f03fd0ef0444d79aef489> to report this email as spam
>
>
>
> Scanned by Forcepoint Email Security Gateway
> Click here <https://esgpem.websense.com/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5eac36c03d0e7ff0b57b7e3ed898c04d3b57443d4dd6633da2a02f7e00cad8ee51e76369bb7724613990fab7f6a77e81c146894a278e2586fe25ecf0e847b3e8c92d9fea959c461e1b4b8eadc7dda39f476525df499317859b67ad36e597e46f717050f777046e98b211aa34ec38cc86034854bfa41cee96304774a1766865ea10> to report this email as spam
RE: Re: Re: [PROPOSAL] Removing clustering support in7.0.0
Posted by "Nguyen, Hai" <hn...@forcepoint.com>.
We are using clustering to share configuration settings in environments that do load balancing across multiple proxies. Administrators that have large deployments would need to configure every proxy manually.
-Hai
From: Bryan Call [mailto:bcall@apache.org]
Sent: Monday, August 29, 2016 3:52 PM
To: Nguyen, Hai
Cc: dev@trafficserver.apache.org; users@trafficserver.apache.org
Subject: EXTERNAL: Re: Re: [PROPOSAL] Removing clustering support in 7.0.0
Can you talk about how you are using the clustering feature? Would parent proxying also work for your use case?
-Bryan
On Aug 29, 2016, at 3:30 PM, Nguyen, Hai <hn...@forcepoint.com>> wrote:
I’m sorry for sending the feedback on this proposal late. Can we please keep the clustering feature? We’ve been using it extensively here.
Thanks,
-Hai
From: Bryan Call [mailto:bcall@apache.org]
Sent: Monday, August 29, 2016 3:20 PM
To: dev@trafficserver.apache.org<ma...@trafficserver.apache.org>
Cc: users@trafficserver.apache.org<ma...@trafficserver.apache.org>
Subject: EXTERNAL: Re: [PROPOSAL] Removing clustering support in 7.0.0
Thank you for all the feedback on this proposal. Removing clustering support will be done in 7.0.0.
-Bryan
On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zw...@apache.org>> wrote:
On Aug 19, 2016, at 3:18 PM, James Peach <jp...@apache.org>> wrote:
On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org>> wrote:
There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
The proposal is to remove the configurations options for clustering and remove the code for it.
I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
+0 from me as well.
— Leif
Scanned by Forcepoint Email Security Gateway
Click here<https://esgpem.websense.com/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5e05ab970ae3ca9cc1d4d703e3a16bba58faf015599e14c7422c0fe0e50f83ec29c6a066df750951d586cbd4b9c445f9f7ede47b5ff2432e6db5d9ab138ccf9f92096d50fce4041f5c685b71e990171ff43cba7313b924b534e998c2f8842e648735033d6e98ce3c50b6ef6e38032c0f11163d221beb5819204db1eb665a0f03fd0ef0444d79aef489> to report this email as spam
Scanned by Forcepoint Email Security Gateway
Click here<https://esgpem.websense.com:443/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5eac36c03d0e7ff0b57b7e3ed898c04d3b57443d4dd6633da2a02f7e00cad8ee51e76369bb7724613990fab7f6a77e81c146894a278e2586fe25ecf0e847b3e8c92d9fea959c461e1b4b8eadc7dda39f476525df499317859b67ad36e597e46f717050f777046e98b211aa34ec38cc86034854bfa41cee96304774a1766865ea10> to report this email as spam
RE: Re: Re: [PROPOSAL] Removing clustering support in7.0.0
Posted by "Nguyen, Hai" <hn...@forcepoint.com>.
We are using clustering to share configuration settings in environments that do load balancing across multiple proxies. Administrators that have large deployments would need to configure every proxy manually.
-Hai
From: Bryan Call [mailto:bcall@apache.org]
Sent: Monday, August 29, 2016 3:52 PM
To: Nguyen, Hai
Cc: dev@trafficserver.apache.org; users@trafficserver.apache.org
Subject: EXTERNAL: Re: Re: [PROPOSAL] Removing clustering support in 7.0.0
Can you talk about how you are using the clustering feature? Would parent proxying also work for your use case?
-Bryan
On Aug 29, 2016, at 3:30 PM, Nguyen, Hai <hn...@forcepoint.com>> wrote:
I’m sorry for sending the feedback on this proposal late. Can we please keep the clustering feature? We’ve been using it extensively here.
Thanks,
-Hai
From: Bryan Call [mailto:bcall@apache.org]
Sent: Monday, August 29, 2016 3:20 PM
To: dev@trafficserver.apache.org<ma...@trafficserver.apache.org>
Cc: users@trafficserver.apache.org<ma...@trafficserver.apache.org>
Subject: EXTERNAL: Re: [PROPOSAL] Removing clustering support in 7.0.0
Thank you for all the feedback on this proposal. Removing clustering support will be done in 7.0.0.
-Bryan
On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zw...@apache.org>> wrote:
On Aug 19, 2016, at 3:18 PM, James Peach <jp...@apache.org>> wrote:
On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org>> wrote:
There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
The proposal is to remove the configurations options for clustering and remove the code for it.
I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
+0 from me as well.
— Leif
Scanned by Forcepoint Email Security Gateway
Click here<https://esgpem.websense.com/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5e05ab970ae3ca9cc1d4d703e3a16bba58faf015599e14c7422c0fe0e50f83ec29c6a066df750951d586cbd4b9c445f9f7ede47b5ff2432e6db5d9ab138ccf9f92096d50fce4041f5c685b71e990171ff43cba7313b924b534e998c2f8842e648735033d6e98ce3c50b6ef6e38032c0f11163d221beb5819204db1eb665a0f03fd0ef0444d79aef489> to report this email as spam
Scanned by Forcepoint Email Security Gateway
Click here<https://esgpem.websense.com:443/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5eac36c03d0e7ff0b57b7e3ed898c04d3b57443d4dd6633da2a02f7e00cad8ee51e76369bb7724613990fab7f6a77e81c146894a278e2586fe25ecf0e847b3e8c92d9fea959c461e1b4b8eadc7dda39f476525df499317859b67ad36e597e46f717050f777046e98b211aa34ec38cc86034854bfa41cee96304774a1766865ea10> to report this email as spam
Re: Re: [PROPOSAL] Removing clustering support in 7.0.0
Posted by Bryan Call <bc...@apache.org>.
Can you talk about how you are using the clustering feature? Would parent proxying also work for your use case?
-Bryan
> On Aug 29, 2016, at 3:30 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
>
> I’m sorry for sending the feedback on this proposal late. Can we please keep the clustering feature? We’ve been using it extensively here.
>
> Thanks,
> -Hai
>
> From: Bryan Call [mailto:bcall@apache.org]
> Sent: Monday, August 29, 2016 3:20 PM
> To: dev@trafficserver.apache.org
> Cc: users@trafficserver.apache.org
> Subject: EXTERNAL: Re: [PROPOSAL] Removing clustering support in 7.0.0
>
> Thank you for all the feedback on this proposal. Removing clustering support will be done in 7.0.0.
>
> -Bryan
>
>
>
>
> On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zwoop@apache.org <ma...@apache.org>> wrote:
>
>
> On Aug 19, 2016, at 3:18 PM, James Peach <jpeach@apache.org <ma...@apache.org>> wrote:
>
>
>
> On Aug 19, 2016, at 11:08 AM, Bryan Call <bcall@apache.org <ma...@apache.org>> wrote:
>
> There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
>
> There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
>
> The proposal is to remove the configurations options for clustering and remove the code for it.
>
> I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
>
>
> A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
>
> This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
>
> +0 from me as well.
>
> — Leif
>
>
>
> Scanned by Forcepoint Email Security Gateway
> Click here <https://esgpem.websense.com/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5e05ab970ae3ca9cc1d4d703e3a16bba58faf015599e14c7422c0fe0e50f83ec29c6a066df750951d586cbd4b9c445f9f7ede47b5ff2432e6db5d9ab138ccf9f92096d50fce4041f5c685b71e990171ff43cba7313b924b534e998c2f8842e648735033d6e98ce3c50b6ef6e38032c0f11163d221beb5819204db1eb665a0f03fd0ef0444d79aef489> to report this email as spam
Re: Re: [PROPOSAL] Removing clustering support in 7.0.0
Posted by Bryan Call <bc...@apache.org>.
Can you talk about how you are using the clustering feature? Would parent proxying also work for your use case?
-Bryan
> On Aug 29, 2016, at 3:30 PM, Nguyen, Hai <hn...@forcepoint.com> wrote:
>
> I’m sorry for sending the feedback on this proposal late. Can we please keep the clustering feature? We’ve been using it extensively here.
>
> Thanks,
> -Hai
>
> From: Bryan Call [mailto:bcall@apache.org]
> Sent: Monday, August 29, 2016 3:20 PM
> To: dev@trafficserver.apache.org
> Cc: users@trafficserver.apache.org
> Subject: EXTERNAL: Re: [PROPOSAL] Removing clustering support in 7.0.0
>
> Thank you for all the feedback on this proposal. Removing clustering support will be done in 7.0.0.
>
> -Bryan
>
>
>
>
> On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zwoop@apache.org <ma...@apache.org>> wrote:
>
>
> On Aug 19, 2016, at 3:18 PM, James Peach <jpeach@apache.org <ma...@apache.org>> wrote:
>
>
>
> On Aug 19, 2016, at 11:08 AM, Bryan Call <bcall@apache.org <ma...@apache.org>> wrote:
>
> There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
>
> There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
>
> The proposal is to remove the configurations options for clustering and remove the code for it.
>
> I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
>
>
> A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
>
> This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
>
> +0 from me as well.
>
> — Leif
>
>
>
> Scanned by Forcepoint Email Security Gateway
> Click here <https://esgpem.websense.com/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5e05ab970ae3ca9cc1d4d703e3a16bba58faf015599e14c7422c0fe0e50f83ec29c6a066df750951d586cbd4b9c445f9f7ede47b5ff2432e6db5d9ab138ccf9f92096d50fce4041f5c685b71e990171ff43cba7313b924b534e998c2f8842e648735033d6e98ce3c50b6ef6e38032c0f11163d221beb5819204db1eb665a0f03fd0ef0444d79aef489> to report this email as spam
RE: Re: [PROPOSAL] Removing clustering support in 7.0.0
Posted by "Nguyen, Hai" <hn...@forcepoint.com>.
I’m sorry for sending the feedback on this proposal late. Can we please keep the clustering feature? We’ve been using it extensively here.
Thanks,
-Hai
From: Bryan Call [mailto:bcall@apache.org]
Sent: Monday, August 29, 2016 3:20 PM
To: dev@trafficserver.apache.org
Cc: users@trafficserver.apache.org
Subject: EXTERNAL: Re: [PROPOSAL] Removing clustering support in 7.0.0
Thank you for all the feedback on this proposal. Removing clustering support will be done in 7.0.0.
-Bryan
On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zw...@apache.org>> wrote:
On Aug 19, 2016, at 3:18 PM, James Peach <jp...@apache.org>> wrote:
On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org>> wrote:
There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
The proposal is to remove the configurations options for clustering and remove the code for it.
I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
+0 from me as well.
— Leif
Scanned by Forcepoint Email Security Gateway
Click here<https://esgpem.websense.com:443/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5e05ab970ae3ca9cc1d4d703e3a16bba58faf015599e14c7422c0fe0e50f83ec29c6a066df750951d586cbd4b9c445f9f7ede47b5ff2432e6db5d9ab138ccf9f92096d50fce4041f5c685b71e990171ff43cba7313b924b534e998c2f8842e648735033d6e98ce3c50b6ef6e38032c0f11163d221beb5819204db1eb665a0f03fd0ef0444d79aef489> to report this email as spam
RE: Re: [PROPOSAL] Removing clustering support in 7.0.0
Posted by "Nguyen, Hai" <hn...@forcepoint.com>.
I’m sorry for sending the feedback on this proposal late. Can we please keep the clustering feature? We’ve been using it extensively here.
Thanks,
-Hai
From: Bryan Call [mailto:bcall@apache.org]
Sent: Monday, August 29, 2016 3:20 PM
To: dev@trafficserver.apache.org
Cc: users@trafficserver.apache.org
Subject: EXTERNAL: Re: [PROPOSAL] Removing clustering support in 7.0.0
Thank you for all the feedback on this proposal. Removing clustering support will be done in 7.0.0.
-Bryan
On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zw...@apache.org>> wrote:
On Aug 19, 2016, at 3:18 PM, James Peach <jp...@apache.org>> wrote:
On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org>> wrote:
There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
The proposal is to remove the configurations options for clustering and remove the code for it.
I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
+0 from me as well.
— Leif
Scanned by Forcepoint Email Security Gateway
Click here<https://esgpem.websense.com:443/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5e05ab970ae3ca9cc1d4d703e3a16bba58faf015599e14c7422c0fe0e50f83ec29c6a066df750951d586cbd4b9c445f9f7ede47b5ff2432e6db5d9ab138ccf9f92096d50fce4041f5c685b71e990171ff43cba7313b924b534e998c2f8842e648735033d6e98ce3c50b6ef6e38032c0f11163d221beb5819204db1eb665a0f03fd0ef0444d79aef489> to report this email as spam
Re: [PROPOSAL] Removing clustering support in 7.0.0
Posted by Bryan Call <bc...@apache.org>.
Thank you for all the feedback on this proposal. Removing clustering support will be done in 7.0.0.
-Bryan
> On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zw...@apache.org> wrote:
>
>>
>> On Aug 19, 2016, at 3:18 PM, James Peach <jp...@apache.org> wrote:
>>
>>
>>> On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org> wrote:
>>>
>>> There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
>>>
>>> There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
>>>
>>> The proposal is to remove the configurations options for clustering and remove the code for it.
>>
>> I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
>
>
> A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
>
> This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
>
> +0 from me as well.
>
> — Leif
Re: [PROPOSAL] Removing clustering support in 7.0.0
Posted by Bryan Call <bc...@apache.org>.
Thank you for all the feedback on this proposal. Removing clustering support will be done in 7.0.0.
-Bryan
> On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zw...@apache.org> wrote:
>
>>
>> On Aug 19, 2016, at 3:18 PM, James Peach <jp...@apache.org> wrote:
>>
>>
>>> On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org> wrote:
>>>
>>> There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
>>>
>>> There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
>>>
>>> The proposal is to remove the configurations options for clustering and remove the code for it.
>>
>> I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
>
>
> A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
>
> This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
>
> +0 from me as well.
>
> — Leif
Re: [PROPOSAL] Removing clustering support in 7.0.0
Posted by Leif Hedstrom <zw...@apache.org>.
> On Aug 19, 2016, at 3:18 PM, James Peach <jp...@apache.org> wrote:
>
>
>> On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org> wrote:
>>
>> There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
>>
>> There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
>>
>> The proposal is to remove the configurations options for clustering and remove the code for it.
>
> I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
+0 from me as well.
— Leif
Re: [PROPOSAL] Removing clustering support in 7.0.0
Posted by Leif Hedstrom <zw...@apache.org>.
> On Aug 19, 2016, at 3:18 PM, James Peach <jp...@apache.org> wrote:
>
>
>> On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org> wrote:
>>
>> There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
>>
>> There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
>>
>> The proposal is to remove the configurations options for clustering and remove the code for it.
>
> I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature.
This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system.
+0 from me as well.
— Leif
Re: [PROPOSAL] Removing clustering support in 7.0.0
Posted by James Peach <jp...@apache.org>.
> On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org> wrote:
>
> There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
>
> There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
>
> The proposal is to remove the configurations options for clustering and remove the code for it.
I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
J
Re: [PROPOSAL] Removing clustering support in 7.0.0
Posted by James Peach <jp...@apache.org>.
> On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org> wrote:
>
> There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
>
> There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
>
> The proposal is to remove the configurations options for clustering and remove the code for it.
I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0.
J
Re: [PROPOSAL] Removing clustering support in 7.0.0
Posted by "Steven R. Feltner" <sf...@godaddy.com>.
We are considering using cluster management-only for shared configuration for our next project. Currently, we have 12 ATS nodes all acting independently. The next project will have double that number of nodes, and I was trying to get away from having to deploy configuration changes per node.
I was also considering adding in functionality such that I could send a PURGE command to one node, and have that command be replicated across all of the nodes in the cluster, as opposed to having to send a PURGE command to each of the nodes individually.
Based on Bryan’s proposal, we are revisiting the idea of clustered ATS. I am just giving feedback that we are considering using it.
If anyone has ideas on how to manage configs across this many nodes, or about how to trigger PURGE and similar cache commands to all nodes, please let me know.
Thanks,
Steven
On 8/19/16, 2:08 PM, "Bryan Call" <bc...@apache.org> wrote:
There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important!
There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs.
The proposal is to remove the configurations options for clustering and remove the code for it.
-Bryan