Re: Steering Target Geo-Ordering

[Jeremy Mitchell]

So, back to the Seattle, Denver, Boston example...

To accomplish the geo ordering and redundant origin use case, you'd create
3 HTTP_LIVE delivery services? One with an origin in seattle. One with an
origin in denver. One with an origin in boston. (or would you create 6 ds's
so you have 2 in each location?)

Then you'd create a steering delivery service with 3 targets (the HTTP_LIVE
ds's you just created.) Each target would have type = GEO_ORDER and value =
?

I'm getting confused with that above scenario. How many targets would you
have? What would the type of each target be and what would the value of
each target be?

Jeremy


On Fri, Feb 23, 2018 at 3:40 PM, Rawlin Peters 
wrote:

> Hey folks,
>
> At Comcast we have a need to augment CLIENT_STEERING (also regular
> STEERING while we're at it) to allow targets to be ordered/sorted
> based upon the client's proximity to the origin of the target delivery
> services. I'd like to get your feedback on my proposed design and
> address any of your concerns.
>
> For HTTP_LIVE targets for instance, we'd like edge caches to ideally
> retrieve/serve data from an Origin that is close to the client and
> fall back to Origins that are farther and farther away. This allows
> for increased redundancy while ordering optimal Origins (Delivery
> Services) for a client to choose from.
>
> For example, I have 3 Origins in different locations: Seattle, Denver,
> and Boston. I would create an HTTP_LIVE delivery service for each
> origin and a CLIENT_STEERING delivery service with those delivery
> services as targets. I would then like to have those targets ordered
> based upon proximity to the client. So a client in Seattle would get
> the list [Seattle, Denver, Boston], while a client in Boston would get
> the list [Boston, Denver, Seattle].
>
> To make things more complicated, I want to add a redundant origin in
> each location and split traffic between them (like STEERING_WEIGHT
> today) while taking into account the geo-ordering. I also want to be
> able to force an ordering (like STEERING_ORDER today) among co-located
> targets.
>
> In order to accomplish this I propose to:
> 1. add two new steering types: GEO_ORDER and GEO_WEIGHT (by adding a
> target of type GEO_*, a steering DS would then enable geo-ordering)
> 2. associate a Delivery Service Origin with a latitude/longitude,
> thereby associating a lat/long to a GEO_* target
>
> Item 1 is pretty straightforward and will also play nicely with the
> current steering types (STEERING_ORDER and STEERING_WEIGHT). I've
> completed a POC within Traffic Router that basically provides the
> following ordering when mixing all 4 types in a single steering
> delivery service:
> - Negative STEERING_ORDER targets
> - GEO_WEIGHT and GEO_ORDER targets, grouped by proximity to the
> client, ordered by geo-order and the consistent-hashing from the
> weightings
> - STEERING_WEIGHT targets (consistent-hashed)
> - Positive STEERING_ORDER targets
>
> Item 2 is not as straightforward because the simple thing would be to
> just add an Origin Lat/Long field to the Delivery Service and call it
> a day. However I don't think we should do that, and I'll dive more
> into that in a separate thread (coming soon).
>
> Does anyone have questions/concerns about adding these new GEO_ORDER
> and GEO_STEERING target types and geo-sorting them based upon
> proximity to the client? Are you okay with the proposed ordering when
> all the steering types are mixed together?
>
> - Rawlin
>

Re: Google Summer of Code 2018 Mentor Registration

[Dave Neuman]

I think any of the perl -> go API stuff would be great.

On Mon, Feb 26, 2018 at 10:19 AM, Eric Friedrich (efriedri) <
efrie...@cisco.com> wrote:

> I agree, this would be a great way to grow the community.
>
> Do we have a list of marked issues in Github that would be good candidates?
>
> Or perhaps we can brainstorm some issues here on the mailer?
>
> —Eric
>
> > On Feb 24, 2018, at 5:18 PM, Phil Sorber  wrote:
> >
> > I think we should do this.
> >
> > -- Forwarded message -
> > From: Ulrich Stärk 
> > Date: Sat, Feb 24, 2018 at 2:19 PM
> > Subject: Google Summer of Code 2018 Mentor Registration
> > To: 
> > Cc: d...@community.apache.org 
> >
> >
> > Dear PMCs,
> >
> > I'm happy to announce that the ASF has made it onto the list of accepted
> > organizations for
> > Google Summer of Code 2018! [1,2]
> >
> > It is now time for mentors to sign up, so please pass this email on to
> your
> > community and
> > podlings. If you aren’t already subscribed to
> ment...@community.apache.org
> > you should do so now else
> > you might miss important information.
> >
> > Mentor signup requires two steps: mentor signup in Google's system [3]
> and
> > PMC acknowledgement.
> >
> > If you want to mentor a project in this year's SoC you will have to
> >
> > 1. Be an Apache committer.
> > 2. Request an acknowledgement from the PMC for which you want to mentor
> > projects. Use the below
> > template and *do not forget to copy ment...@community.apache.org*. We
> will
> > use the email adress you
> > indicate to send the invite to be a mentor for Apache.
> >
> > PMCs, read carefully please.
> >
> > We request that each mentor is acknowledged by a PMC member. This is to
> > ensure the mentor is in good
> > standing with the community. When you receive a request for
> > acknowledgement, please ACK it and cc
> > ment...@community.apache.org
> >
> > Lastly, it is not yet too late to record your ideas in Jira (see my
> > previous emails for details).
> > Students will now begin to explore ideas so if you haven’t already done
> so,
> > record your ideas
> > immediately!
> >
> > Cheers,
> >
> > Uli
> >
> > mentor request email template:
> > 
> > to: private@.apache.org
> > cc: ment...@community.apache.org
> > subject: GSoC 2018 mentor request for 
> >
> >  PMC,
> >
> > please acknowledge my request to become a mentor for Google Summer of
> Code
> > 2018 projects for Apache
> > .
> >
> > I would like to receive the mentor invite to 
> >
> > 
> >
> > 
> >
> > [1] https://summerofcode.withgoogle.com/organizations/
> > [2] https://summerofcode.withgoogle.com/organizations/5718432427802624/
> > [3] https://summerofcode.withgoogle.com/
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
>
>