Re: Proposal for an open standard for memcached auto-discovery
Thanks Dormando. I will update the doc and add another section for meta protocol. On Sun, Mar 8, 2020 at 9:33 PM dormando wrote: > Hey, > > So first part: https://github.com/memcached/memcached/wiki/ReleaseNotes160 > > We won't be adding further features to the binary protocol, instead > extending off of the new text based meta protocol. I'll be looking at > your proposal more closely in a week or so now that 1.6.0 is out. > > -Dormando > > On Thu, 27 Feb 2020, dormando wrote: > > > Thanks for getting this started! > > > > It may take a while for me to review/think it over. I've been planning on > > tackling this but have a lot of research to do. > > > > On Thu, 27 Feb 2020, 'Iqram Mahmud' via memcached wrote: > > > > > Hi Dormando and memcached community, > > > > > > I work in Google Cloud Platform and we want to propose an open > standard for memcached node auto-discovery protocol that's independent of > Cloud providers > > > and can work with on-premise infrastructure as well. Auto-discovery > protocol will allow engineering teams to scale up or down the node count of > a > > > memcached cluster without doing any client-side deployment. The design > doc is here. > > > If we don't have an open standard on this, we might end up with the > situation where every Cloud provider will have their own protocol, causing > a lot of > > > migration pain to everyone else. > > > > > > We look forward to your comments. Once the design is final and > approved by you, we'll start sending patches for memcached server and > clients. > > > > > > Thanks, > > > Iqram > > > > > > -- > > > > > > --- > > > You received this message because you are subscribed to the Google > Groups "memcached" group. > > > To unsubscribe from this group and stop receiving emails from it, send > an email to memcached+unsubscr...@googlegroups.com. > > > To view this discussion on the web visit > > > > https://groups.google.com/d/msgid/memcached/CA%2Bd7wM6HZ-kQa-wySB4m9aiqckBbnAUfUQVCKOVTktyuGHN92g%40mail.gmail.com > . > > > > > > > > > > -- > > > > --- > > You received this message because you are subscribed to the Google > Groups "memcached" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to memcached+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/memcached/alpine.DEB.2.21.2002271445440.25120%40dskull > . > > > > -- > > --- > You received this message because you are subscribed to the Google Groups > "memcached" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to memcached+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/memcached/alpine.DEB.2.21.2003082131570.807%40dskull > . > -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/memcached/CA%2Bd7wM7zq5A97kVgBqYp5xJgogBAQYjOs5DX5v_Rnnj%3DX4ueeA%40mail.gmail.com.
Re: Proposal for an open standard for memcached auto-discovery
Hey, So first part: https://github.com/memcached/memcached/wiki/ReleaseNotes160 We won't be adding further features to the binary protocol, instead extending off of the new text based meta protocol. I'll be looking at your proposal more closely in a week or so now that 1.6.0 is out. -Dormando On Thu, 27 Feb 2020, dormando wrote: > Thanks for getting this started! > > It may take a while for me to review/think it over. I've been planning on > tackling this but have a lot of research to do. > > On Thu, 27 Feb 2020, 'Iqram Mahmud' via memcached wrote: > > > Hi Dormando and memcached community, > > > > I work in Google Cloud Platform and we want to propose an open standard for > > memcached node auto-discovery protocol that's independent of Cloud providers > > and can work with on-premise infrastructure as well. Auto-discovery > > protocol will allow engineering teams to scale up or down the node count of > > a > > memcached cluster without doing any client-side deployment. The design doc > > is here. > > If we don't have an open standard on this, we might end up with the > > situation where every Cloud provider will have their own protocol, causing > > a lot of > > migration pain to everyone else. > > > > We look forward to your comments. Once the design is final and approved by > > you, we'll start sending patches for memcached server and clients. > > > > Thanks, > > Iqram > > > > -- > > > > --- > > You received this message because you are subscribed to the Google Groups > > "memcached" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to memcached+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/memcached/CA%2Bd7wM6HZ-kQa-wySB4m9aiqckBbnAUfUQVCKOVTktyuGHN92g%40mail.gmail.com. > > > > > > -- > > --- > You received this message because you are subscribed to the Google Groups > "memcached" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to memcached+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/memcached/alpine.DEB.2.21.2002271445440.25120%40dskull. > -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/memcached/alpine.DEB.2.21.2003082131570.807%40dskull.
Re: Proposal for an open standard for memcached auto-discovery
Thanks for getting this started! It may take a while for me to review/think it over. I've been planning on tackling this but have a lot of research to do. On Thu, 27 Feb 2020, 'Iqram Mahmud' via memcached wrote: > Hi Dormando and memcached community, > > I work in Google Cloud Platform and we want to propose an open standard for > memcached node auto-discovery protocol that's independent of Cloud providers > and can work with on-premise infrastructure as well. Auto-discovery protocol > will allow engineering teams to scale up or down the node count of a > memcached cluster without doing any client-side deployment. The design doc is > here. > If we don't have an open standard on this, we might end up with the situation > where every Cloud provider will have their own protocol, causing a lot of > migration pain to everyone else. > > We look forward to your comments. Once the design is final and approved by > you, we'll start sending patches for memcached server and clients. > > Thanks, > Iqram > > -- > > --- > You received this message because you are subscribed to the Google Groups > "memcached" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to memcached+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/memcached/CA%2Bd7wM6HZ-kQa-wySB4m9aiqckBbnAUfUQVCKOVTktyuGHN92g%40mail.gmail.com. > > -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/memcached/alpine.DEB.2.21.2002271445440.25120%40dskull.
