Please use this identifier to cite or link to this item:
http://ir.juit.ac.in:8080/jspui/jspui/handle/123456789/6813
Full metadata record
DC Field | Value | Language |
---|---|---|
dc.contributor.author | Singla, Kanav | - |
dc.contributor.author | Sathyaraj, Pristley [Guided by] | - |
dc.date.accessioned | 2022-09-26T09:24:08Z | - |
dc.date.available | 2022-09-26T09:24:08Z | - |
dc.date.issued | 2019 | - |
dc.identifier.uri | http://ir.juit.ac.in:8080/jspui/jspui/handle/123456789/6813 | - |
dc.description.abstract | In todays IT world with increasing computing power and demands of the world the server power and so does the manpower need to be increased. With increase in server counts the failure chances increases and so does the responsibility of humans to maintain them and keep them running at all costs. This is too much work and solve this automation is the best way to keep in control the demands of today and our project running at all times. The problem is solved by automating the deployment process. The general sending process comprises of a few interrelated exercises with potential changes between them. These exercises can happen at the maker side or at the buyer side or both. Since each product framework is interesting, the exact procedures or methodology inside every action can barely be characterized. Along these lines, "sending" ought to be decrypted as a general procedure that must be redone as per explicit necessities or qualities. In this project, we will be using two very popular configuration tools for deploying namely, Ansible and Puppet. Puppet is master server architecture that has a master which has configuration info that can be sent to nodes for them to be in a required state. It uses Ruby language which is not easy to learn. Ansible is same as puppet but has an agentless arch that helps them to deploy on the host machine. It has playbooks which are maintained so that target machines can be configured. It has YAML language. (It is a comprehensible information serialization language and is usually utilized for setup of documents). | en_US |
dc.language.iso | en | en_US |
dc.publisher | Jaypee University of Information Technology, Solan, H.P. | en_US |
dc.subject | Orchestration performance tools | en_US |
dc.subject | Serverless web application | en_US |
dc.subject | DevOps | en_US |
dc.title | Comparison of Software Orchestration Performance Tools and Serverless Web Application | en_US |
dc.type | Project Report | en_US |
Appears in Collections: | B.Tech. Project Reports |
Files in This Item:
File | Description | Size | Format | |
---|---|---|---|---|
Comparison of Software Orchestration Performance Tools and Serverless Web Application.pdf | 2.41 MB | Adobe PDF | View/Open |
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.