In this first task you need to configure web-02
to be identical to web-01
. Fortunately, you built a Bash script during your web server project, and they’ll now come in handy to easily configure web-02
. Remember, always try to automate your work!
Since we’re placing our web servers behind a load balancer for this project, we want to add a custom Nginx response header. The goal here is to be able to track which web server is answering our HTTP requests, to understand and track the way a load balancer works. More in the coming tasks.
Requirements:
- Configure Nginx so that its HTTP response contains a custom header (on
web-01
andweb-02
)- The name of the custom HTTP header must be
X-Served-By
- The value of the custom HTTP header must be the hostname of the server Nginx is running on
- The name of the custom HTTP header must be
- Write
0-custom_http_response_header
so that it configures a brand new Ubuntu machine to the requirements asked in this task - Ignore
SC2154
forshellcheck
Install and configure HAproxy on your lb-01
server.
Requirements:
- Configure HAproxy so that it send traffic to
web-01
andweb-02
- Distribute requests using a roundrobin algorithm
- Make sure that HAproxy can be managed via an init script
- Make sure that your servers are configured with the right hostnames:
[STUDENT_ID]-web-01
and[STUDENT_ID]-web-02
. If not, follow this tutorial. - For your answer file, write a Bash script that configures a new Ubuntu machine to respect above requirements
Just as in task #0, we’d like you to automate the task of creating a custom HTTP header response, but with Puppet.
- The name of the custom HTTP header must be
X-Served-By
- The value of the custom HTTP header must be the hostname of the server Nginx is running on
- Write
2-puppet_custom_http_response_header.pp
so that it configures a brand new Ubuntu machine to the requirements asked in this task