Hi,
Currently, we are using two different cloudfront distributions to CDN content for /atomic/repo/objects/ and /atomic/repo/deltas/ . With the current setup we see an issue https://github.com/ostreedev/ostree/issues/1541 . To overcome this issue and provide faster delivery of ostree content, we have created a cloudfront distribution where we CDN /atomic/repo/ .
This patch (available in attachment) adds some redirect rules to use new cloudfront urls for testing purpose and see how much improvement we get in content delivery. This patch shouldn't impact existing infra setup.
Thanks, Sinny
On 1/3/19 10:40 AM, Sinny Kumari wrote:
Hi,
Currently, we are using two different cloudfront distributions to CDN content for /atomic/repo/objects/ and /atomic/repo/deltas/ . With the current setup we see an issue https://github.com/ostreedev/ostree/issues/1541 . To overcome this issue and provide faster delivery of ostree content, we have created a cloudfront distribution where we CDN /atomic/repo/ .
This patch (available in attachment) adds some redirect rules to use new cloudfront urls for testing purpose and see how much improvement we get in content delivery. This patch shouldn't impact existing infra setup.
I'd like to highlight this is for testing purposes only and should have a short life. We just wanted to make sure the "redirect penalty" that we experience with our prod redirects is also reflected in our testing so we can get more accurate results.
Sinny,
One thing we might want to do is use https for the cloudfron URLs like we are for the prod redirects. Otherwise LGTM.
Dusty
On Thu, Jan 3, 2019 at 9:16 PM Dusty Mabe dusty@dustymabe.com wrote:
On 1/3/19 10:40 AM, Sinny Kumari wrote:
Hi,
Currently, we are using two different cloudfront distributions to CDN
content for
/atomic/repo/objects/ and /atomic/repo/deltas/ . With the current setup
we see
an issue https://github.com/ostreedev/ostree/issues/1541 . To overcome
this
issue and provide faster delivery of ostree content, we have created a cloudfront distribution where we CDN /atomic/repo/ .
This patch (available in attachment) adds some redirect rules to use new cloudfront urls for testing purpose and see how much improvement we get
in
content delivery. This patch shouldn't impact existing infra setup.
I'd like to highlight this is for testing purposes only and should have a short life. We just wanted to make sure the "redirect penalty" that we experience with our prod redirects is also reflected in our testing so we can get more accurate results.
Sinny,
One thing we might want to do is use https for the cloudfron URLs like we are for the prod redirects. Otherwise LGTM.
Ah yes, nice catch. Updated patch is available in the attachment. This is the sad part part of doing copy paste :/
Dusty
I've applied the patch and deployed it in production.
On Thu, Jan 3, 2019 at 4:55 PM Sinny Kumari ksinny@gmail.com wrote:
On Thu, Jan 3, 2019 at 9:16 PM Dusty Mabe dusty@dustymabe.com wrote:
On 1/3/19 10:40 AM, Sinny Kumari wrote:
Hi,
Currently, we are using two different cloudfront distributions to CDN content for /atomic/repo/objects/ and /atomic/repo/deltas/ . With the current setup we see an issue https://github.com/ostreedev/ostree/issues/1541 . To overcome this issue and provide faster delivery of ostree content, we have created a cloudfront distribution where we CDN /atomic/repo/ .
This patch (available in attachment) adds some redirect rules to use new cloudfront urls for testing purpose and see how much improvement we get in content delivery. This patch shouldn't impact existing infra setup.
I'd like to highlight this is for testing purposes only and should have a short life. We just wanted to make sure the "redirect penalty" that we experience with our prod redirects is also reflected in our testing so we can get more accurate results.
Sinny,
One thing we might want to do is use https for the cloudfron URLs like we are for the prod redirects. Otherwise LGTM.
Ah yes, nice catch. Updated patch is available in the attachment. This is the sad part part of doing copy paste :/
Dusty
-- http://sinny.io/ _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
On Fri, Jan 4, 2019 at 9:16 PM Mikolaj Izdebski mizdebsk@redhat.com wrote:
I've applied the patch and deployed it in production.
Thanks a lot Mikolaj!
On Thu, Jan 3, 2019 at 4:55 PM Sinny Kumari ksinny@gmail.com wrote:
On Thu, Jan 3, 2019 at 9:16 PM Dusty Mabe dusty@dustymabe.com wrote:
On 1/3/19 10:40 AM, Sinny Kumari wrote:
Hi,
Currently, we are using two different cloudfront distributions to CDN
content for
/atomic/repo/objects/ and /atomic/repo/deltas/ . With the current
setup we see
an issue https://github.com/ostreedev/ostree/issues/1541 . To
overcome this
issue and provide faster delivery of ostree content, we have created a cloudfront distribution where we CDN /atomic/repo/ .
This patch (available in attachment) adds some redirect rules to use
new
cloudfront urls for testing purpose and see how much improvement we
get in
content delivery. This patch shouldn't impact existing infra setup.
I'd like to highlight this is for testing purposes only and should have
a short
life. We just wanted to make sure the "redirect penalty" that we
experience with
our prod redirects is also reflected in our testing so we can get more
accurate
results.
Sinny,
One thing we might want to do is use https for the cloudfron URLs like
we are for
the prod redirects. Otherwise LGTM.
Ah yes, nice catch. Updated patch is available in the attachment. This is the sad part part of doing copy paste :/
Dusty
-- http://sinny.io/ _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to
infrastructure-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
infrastructure@lists.fedoraproject.org
-
Dusty Mabe -
Mikolaj Izdebski -
Sinny Kumari