FANDOM


IPSaaS is a cloud computing service model and technology that combines Infrastructure (IaaS), Platform (PaaS) and Software as a Service (SaaS). [1]

IPSaaS technology was first founded and brought to market by Jared Rice, Stanley Ford and Michael Miller of EasyCloud[2]

IPSaaS Technology

IPSaaS is a combination of 3 major technologies. IaaS (Infrastructure as a Service),PaaS (Platform as a Service),SaaS (Software as a Service), when combined, creates IPSaaS. To run an IPSaaS environment through an IPSaaS provider, requires no expertise, if only running simple web software on the IPSaaS environment.

Providing IPSaaS

Currently, EasyCloud and Cloudways are the only IPSaaS providers with two different and totally separate platforms. One platform is controlled by the user and the other is controlled by server application. The downside in providing IPSaaS is you have to provide customer support for all three technologies. Normally users pay and receive support from three separate companies when trying to use IaaS, PaaS and SaaS collectively. An IPSaaS provider provides support and customer service for all three technologies to the customer. This is great for the customer and costly for the provider.

IPaSys

IPaSys stands for Infrastructure, Platform and Software Your Supporting. It is the same thing as IPSaaS without the management services of an IPSaaS provider. IPaSys refers to groups or companies who build or utilize infrastructure, platform and software and manage all three themselves. IPaSys can easily be created using a cloud backup service through a popular infrastructure provider such as Amazon Cloud or Rackspace Cloud. The IPaSys model was also created by the IPSaaS founders and includes the same advantages as IPSaaS other than the support and service perks from a provider.

Platform

A cloud platform is required in any IPSaaS setup. Generally a good platform will require two Hypervisors, one Data Storage Server, one Backup Storage Server and one Edge Server for CDN at minimum. This is enough to store hundreds of cloud images and enough ram to power at least 16 cloud nodes.

Infrastructure + Platform

OpenStack provides a great platform for IPSaaS environments that run web applications. OpenStack is known for its ability to operate Centos at high levels with the majority of users reporting excellent uptimes by major infrastructure providers such as Rackspace, Amazon and SingleHop. Every IPSaaS environment requires a cloud platform to operate on top of the cloud infrastructure. The cloud platform is important in how your infrastructure operates. Rackspace is the first company to offer OpenStack and Cloud infrastructure as a combined service. Heroku was the first company to offer infrastructure and platform as a service as a cohesive solution.

Cloud Images and IPSaaS

A IPSaaS environment can be created simply through cloud images. First a working version of the software is created on a cloud server. Once the server is completely functioning, a backup or image is created. The image of that server is now reachable through the infrastructure provider's API. There are several softwares such as WHMCS that work well with API from cloud infrastructure providers and can launch server images with one mouse click. The design and overall usability of WHMCS is poor and out-dated and is not a professional way to provide IPSaaS to your customer. A custom PHP application that communicates with API's from your infrastructure and platform would work better, in you plan on becoming a IPSaaS provider.

Application For Infrastructure API

An IPSaaS environment requires a front-end web application to launch IPSaaS or IPaSys environments. Once working images are configured at your infrastructure provider, the front-end used to deploy cloud nodes has to be built. An application can be built in several languages including PHP and Ruby On Rails, to work with the infrastructure and platform API. The perfect IPSaaS or IPaSys environments are created with load balancing, full cloud server management, image management and backup management all through an API application.

Controlling Infrastructure, Platform and Software

There has yet to be a provider that controls Infrastructure, Platform and Software collectively. Controlling refers to the provider controlling the data center where the provider operates their infrastructure, platform and software. Some infrastructure companies don't operate or support their platform and softwares in-house. EasyCloud and Cloudways are sub-vendors to several infrastructure and platform providers. Infrastructure providers have yet to dabble into the combination of all cloud computing service models.

MySQL Changes For IPSaaS

When launching server images that have working software, your backup image will contain the same MySQL root password. This has to be changed automatically by the application or the user. One option is to setup a .htaccess file in the root folder of your working cloud server that forwards the first access to the server, to a change password form. This form can easily be created using PHP. Another option is to track the build and activity of the cloud server with another application that can be placed on the server itself, to monitor these actions. Once the build is complete, your application can launch a background terminal session, to rewrite the password and then send it to your application's database.

Pre-Installed Plugins For IPSaaS

When working with bare-bone cloud nodes, its important to pre-install the correct plugins for a functioning server. Great plugins for Linux cloud servers include wget, ftp, openssl, zip and unzip. Most infrastructure providers have popular commands already pre-installed.

References

This article uses material from the Wikipedia article IPSaaS, that was deleted or is being discussed for deletion, which is released under the Creative Commons Attribution-ShareAlike 3.0 Unported License.
Author(s): DoriSmith Search for "IPSaaS" on Google
View Wikipedia's deletion log of "IPSaaS"
Wikipedia-logo-v2