2. Kering overview
■ Who is Kering
‒ Kering is a world leader in luxury apparel and accessories with sport & lifestyle activities.
‒ Kering develop a well-balanced ensemble of 20 brands.
‒ Kering’s mission is to enable its customers to express their personality and to fulfil their dreams,
while making a positive contribution to people and the planet.
■ Brands:
■ But also a Service Provider for major retail partners:
‒ Used to belong to PPR (Pinault-Printemps-Redoute)
3. A piece of Kering’s history
■ Before 2009, La Redoute (belonging to group PPR) was hosted in the
US, and used the Akamai CDN
■ In 2009, PPR decided to move La Redoute infrastructure back to
France
‒ Creation of a new DataCenter in France
‒ POC to replace Akamai by Varnish community was held to accelerate La Redoute
Websites
■ Varnish POC was successful PPR then decided to extend web cache
acceleration based on Varnish to
‒ Fnac
‒ Conforama
‒ Kering.com and keringfoundation.org
4. A piece of Kering’s history (cont.)
■ In 2013, PPR becomes Kering, Fnac, La Redoute and Conforama do
not belong anymore to the group
■ Kering remains a Service Provider for Fnac, La Redoute and
Conforama and delivers
‒ Computing (physical and virtual servers)
‒ Network
‒ Internet access
‒ Web hosting and cache acceleration (Varnish)
■ In 2014, Kering outsources its IT service management from LinkByNet/
Telindus to Fujitsu Technology solutions
5. Varnish usage at Kering
■ Until 2014, and under LBN/Telindus IT service management
outsourcing, Varnish community edition v3.x was deployed on a cluster
of 2 x 8 physical servers with 64 GB of RAM each, ie for a total of 1 TB
of RAM available
■ In 2014, Kering designed 2 brand new datacenters, and was decided to
change the Varnish architecture too:
‒ New powerful servers: from 16 to 6 servers, from 64 to 512 GB of RAM, ie a total of 3
TB RAM
‒ New Varnish version: from v3.x community to Varnich Cache Plus 4.x
‒ New administration console: from homemade console to the Varnish Administration
Console (VAC) which is now fully multitenant since v3.1 of the VAC
9. Multitenant Varnish Administration Console
■ VAC is
‒ Multitenant (1 or several
cache groups per
customer)
‒ Failover
• Switch is performed by
change Varnish agent REST
connection URL
10. Additional tooling around Varnish at Kering
■ Google crawls isolation
‒ NCSA logging enabling
‒ Modify the ncsa logging script and isolate google
crawls
[root@zzsfr1varnish2 logrotate.d]# cat /etc/systemd/system/
varnishncsa@.service
[Unit]
Description=Varnish NCSA logging %i
After=network.target
[Service]
Type=forking
PIDFile=/run/varnishncsa-%i.pid
ExecStart=/usr/bin/varnishncsa -a -w /home/log/varnish/
varnishncsa-%i.log -D -P /run/varnishncsa-%i.pid -n %i -q
"ReqHeader ~ '(G|g)oogle'"
