-
Notifications
You must be signed in to change notification settings - Fork 1
The Cloudify Player powered by a server side application which is implemented using the Play framework and uses Cloudify as a foundation. What happens under the hood is that the player communicates with a Play Framework application on the server side. This app manages a pool of VMs deployed on the cloud (by default HPCloud) and “bootstrapped” with a running Cloudify manager. Whenever a user “plays” a recipe, the server borrows a VM from the free trial pool, connects to the manager running on it over REST, and issues the recipe installation command. After 30 – 60 seconds, you have a running app or framework, available for you to try out for limited time period. For users using their own cloud credentials, this mechanism is a bit different – they are allocated their own Cloudify management server, which then installs the recipes in production mode, with as many hosts and resources as needed (and obviously with no time limit).
No, you can use the trial mode in which you just click the play button and get a time-limited trial instance on the cloud with the framework of your choice.
Certainly, this will mean your not using the trial mode and are no longer limited with capacity or time.
The widget supports both full blown apps and specific frameworks. There are examples for both at the Cloudify Player page in the Cloudify community website.
Yes. When using the trial mode, there's only one VM allocated for each user, so most of the setups are non-clustered. When using your own cloud credentials, you can launch any Cloudify recipe, and in particular ones that start clustered setup of the framework of your choice.
Yes, each widget has a unique embed code that can be placed in any web page. Read the Embedding the widget page for more details.
Yes. You can setup and deploy the widget server on your own, and host the application and framework catalog of your choice. Read the installing page for more details.
Yes, check this page for directions.