Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Well when we talk about installation it is like installing a piece of software on one machine but you at the same time you can deploy this installation in the way described below.
Installation is usually targeted to a single machine whereas in deployment you target more than a machine.
For example: When I say I will install Linux on one of my machine this will be considered as installation. However if I will use this machine as a base and using ks.cfg (kick start) I create an automatic installation setup for installing linux on other machines with the same setting as that of on this machine then that it will be considered as deployment because you are deploying (pushing) the settings that are there on one machine to other machines.
Another example is of deployment is Automatic updates. If you want that only single machine should receive updates from RHN (Red Hat Network) and then you will create a repository on this machine to push updates to other machine then it will considered as deployment.
In simple words whenever there is a push it is deployment whether it is of applications, software or any kind of updates and whenever there is something ready to eat/installed :-) like any software on a CD ready to be used/installed on a machine it is installation.
They basically mean the same thing. Deployment, like roll-out is normally used to denote a large scale. i.e. you would install one router, you would deploy 25 routers and probably roll-out 500. So I guess installation is when you are talking specifically whereas a deployment or a roll-out is when you are talking generically.
I really think deployment is no where like a definition for installation;
Quote:
excerpt from Software deployment; Software deployment is all of the activities that make a software system available for use.
The general deployment process consists of several interrelated activities with possible transitions between them. These activities can occur at the producer site or at the consumer site or both. Because every software system is unique, the precise processes or procedures within each activity can hardly be defined. Therefore, "deployment" should be interpreted as a general process that has to be customized according to specific requirements or characteristics. A brief description of each activity will be presented later.
I know this is general definition: but deployment is the actual making available to parties the software that would be used for setting up a installation or multiples within the installation.
For me, deployment is more of a system-level term.
While it can imply more than one instance is installed, it can also include things that go beyond the installation(s) of the software; that might be user training, it might be workflow/procedures and documentation and it might be changes to the network infrastructure to allow this piece of software to be used effectively, depending on context (and obviosly, some of these things are only really common in an enterprise context, rather than with a single home user).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.