Demonstration: End-User Perspective
Christmas Cards Scenario
Marketplace: Mr. Quimm wants to send Christmas Greetings to his Customers
MOTIVATION: Mr. Quimm wants to distribute to all customers a christmas card this year. As a founder, he is keen to have good customer relations to his early adopters and network, at the same time he is very busy to organize this activity. At an event, he learns about CloudSocket and the BPaaS idea. Interested in the topic, he logs into the CloudSocket marketplace:
After login, he searches for appropriate bundles and identifies a fitting one. As he wants to save money but still have anyone in his network messaged, he decides to go for the medium sized one, that will send greetings right away and fits to his needs. Mr. Quimm has the chance to view relates details of the bundle as a textual description and graphically. The respective marketplace information is provided as descriptions, tags, the bundle price and categories.
Mr. Quimm performs a checkout to his chart and buys the bundle. A notification window provides information on the deployment run that has been triggered, deploying the bundle and all related assets in the cloud. Mr. Quimm will be notified by email as soon as the deployment has completed.
Now we have a detailed look at the execution environment to see what has been triggered by Mr. Quimm's actions.
ResourcesBPaaS Demonstration Marketplace
Execution Environment: Daniel the Cloud Provider Engineer provides a deep-dive into the infrastructure
MOTIVIATION: The deployment has been triggered by the interaction of Mr. Quimm with the marketplace. The deployment of the bundle is performed transparent for him, nevertheless we take a deep dive into the execution environment to understand the different steps of the setup happening on the backend. The cloud provider engine manages the deployment of the bundles and is responsible to return to the customer a running instance of the bundle.
The BPaaS Execution Environment will deploy the Software components over a infrastructure automatically (in our case OpenStack) and also setup related services in the infrastructure.
In the OpenStack monitor we can see that initially the instance is not yet ready. The deployment is performed by making services available in the instance, deploying the Workflow into the engine and integrating services with the workflow. Additionally the monitoring sensors are put into place.