Deployment Models
These deployment models, as defined by NIST , are not defined by operator, location or physically but by the service offered and type of community. Similar to cloud service models, the deployment models are not mutually exclusive. Redmine is an open source web-based project management tool which utilizes all of the cloud computing deployment models in a variety of ways. Examples of its use with each model are provided after each of the deployment models’ descriptions.
Private cloud: This cloud infrastructure is managed by the organization or a third party and is operated solely for the needs of the organization. This may exist on or off premise. An example of this is Redmine, which uses its own VMware vCloud installation to deploy its system.
Public cloud: This cloud infrastructure is available to a large industry group or the general public and is owned by a vendor selling cloud services. Redmine subscribes to Amazon Web Services for cloud services.
Source: Marwin Britto
Community cloud: This cloud infrastructure is shared by more than one organization and support a specific community that has common considerations. This may be managed by the organizations or a third party. This may exist on or off premise. Redmine is a member of an academic consortium (open source), which entitles Redmine to use the academic consortium’s cloud.
Hybrid cloud: This cloud infrastructure is composed of two or more types of clouds listed above that remain unique entities but are connected via standardized technology that affords portability of data and applications. Redmine uses Amazon Web Services to maintain the interface and VMware vCloud for the MySQL database system.
It is essential to understand that the service models, deployment models and the five characteristics of cloud computing as described by NIST do not run independently but are necessarily interrelated and connected to each other. A visual that displays these inter-relationships and necessary connections of the NIST cloud computing characteristics and models . This visual demonstrates that a cloud-based strategy can take on different configurations depending on the institution’s needs. It is not uncommon for institutions to begin with one service model, such as SaaS and a Public Cloud deployment model as a pilot, and then slowly scale if the pilot proves successful. It is also possibly to use several deployment models to support one or more service models
0 Comments:
Post a Comment