We write, we don’t plagiarise! Every answer is different no matter how many orders we get for the same assignment. Your answer will be 100% plagiarism-free, custom written, unique and different from every other student.
I agree to receive phone calls from you at night in case of emergency
Please share your assignment brief and supporting material (if any) via email here at: [email protected] after completing this order process.
No Plagiarism Guarantee - 100% Custom Written
SCHYNDEL WORKS WEBSITE PROJECT
As the 2017 technology placements have been completed, SchyndelWorks now has a team of technology graduates that can help them setup their public facing website. These graduates will work with the cloud engineer to deliver a product that meets all the business requirements specified in sections 3 & 4 of this document.
The web development team has already created the necessary code (php) for the SchyndelWork’s public facing websites. This code must now be deployed to a public facing website hosted on the cloud.
The new system must be able to meet the following business requirements
Business Requirement (A): Creation of Web-Server-A
Note: The cloud engineer is adamant that apache installed via a package manager for Web-Server-A will NOT be accepted.
Web-Server-A will initially be used as staging server so it must serve http via port 8080. Ensure that the port firewall is open & visible.
Server should be installed at /etc/apache2/schyndel/server_root
All necessary user key/password/group files for auth to be placed at
As PHP web developers have been contracted to create site content, your website should have the capability of executing & serving php scripts
To allow ease of use, the server must be capable of dealing with misspelling/capitalization issues.
Hint: You can use the following commands to download the content:
mv -f schyndel-works-site-master/* .
The default document to be served is index.html then index.shtml then index.php
Your server must permit Server Side Includes (SSI) for files with the .shtml extension.
Your site must not permit .gif files from being served.
All content served by the web server must respond with the following Response Header
Business Requirement (B): Creation of Web-Server-B
Now that the staging server has been created, a production web server now needs to be setup. This production web server will be identical to "Web-Server-A" except the changes listed below:
VM to host Web-Server-B on a "t2.large" ec2 instance of AWS (or equivalent if using azure)
Port used to serve documents should be 8050
Ensure that the port firewall is open & visible.
For example, when setting the port, you will need to add the following comment in your configuration file
# BR (B).2: As per requirement, changed port from 80 to 8050
Business Requirement (C): Creation of Load-Balancer
then average out the results.
o /load/cpu.php has a concurrency of 10 & test 150 requests
o /load/io.php has a concurrency of 10 & test 200 requests.
o It has also been recommended that this particular vm (“Load-Testing” vm
only) be terminated once you have finished your load tests.
o On the vm you only need to install:
▪ apt-get install apache2-utils (this gives you access to ab)
▪ apt-get install httperf (this gives you access to httperf)
# BR (C).2: As per requirement, set loadfactor to X for node X
Business Requirement (D): Alternative load balancing algorithm
"Business Requirement C" and you need to create a new report.
A zip file containing the following assets needs to be submitted:
│ ├─── a-report.txt
│ ├─── httpd.conf (for Web-Server-A)
│ └─── (all auth files)
│ ├─── httpd.conf (for Web-Server-B)
│ └─── <>
│ ├─── c-report.docx
│ ├─── c-report.pdf
│ ├─── 000-default.conf (for Load-Balancer)
│ └─── (any other config files changed)
└─── / business-requirement-d
├─── 000-default.conf (for Load-Balancer)
└─── (any other config files changed)