The Bitnami Application Library for VMware is a collection of popular open source applications that are prepackaged as application blueprints and ready to use with VMware vFabric™ Application Director. The library includes wikis, content and document management systems, portals, development tools, customer relationship management (CRM) systems and many other types of applications. You can learn more about them at http://bitnami.com/vmware
Bitnami’s library for VMware consists of Bitnami’s application components within reusable blueprints using industry’s leading Cloud-enabled application provisioning solution, VMware vFabric™ Application Director. The product takes a model-driven open approach to drastically simplify and automate application deployment topologies of portable multi-tier applications in private, public and hybrid clouds. These application topologies are called application blueprints. With the joint integration of Bitnami application packages with VMware vFabric™ Application Director, users can rapidly deploy and customize applications across clouds per their enterprise IT policies.
The Bitnami Application Library hooks up to existing services like Apache and MySQL, making it easy to deploy and manage your favorite applications.
The Bitnami Application Library currently supports the following OS platforms:
CentOS 5.6: Both local and remote MySQL deployments
Support for RHEL and Ubuntu is planned.
concrete5 CMS is a content management system that allows you to deploy web applications, websites, stores and forums and easily manage their content and site structure. concrete5 powers hundreds of thousands of sites and has been designed with the needs of developers, designers and site owners in mind. For example, it offers a flexible framework written in Object Oriented PHP 5, which follows a very extensible Model View Controller approach.
You can learn more about concrete5 CMS at (http://concrete5.org/)
The following sections will explain how to launch and manage concrete5 CMS with VMware vFabric™ Application Director.
Go to "Administration" in the Catalog section. Then in "Tags" create a new tag for Bitnami. This will make easier to identify the Bitnami services later when creating new Blueprints.
Description: Deployment of web applications
Use an Application Director wizard to create a new service.
image::images/concrete5 cms_service_details.png["concrete5 CMS Service Details",title="concrete5 CMS Service Details",align="center",caption="Figure 2: "]
image::images/concrete5 cms_service_properties.png["concrete5 CMS Service Properties",title="concrete5 CMS Service Properties",align="center",caption="Figure 3: "]
image::images/concrete5 cms_service_scripts.png["concrete5 CMS Service Scripts",title="concrete5 CMS Service Scripts",align="center",caption="Figure 4: "]
Once you have created the Bitnami concrete5 CMS service in your catalog, you can use it as a building block when you create your own Blueprints. To use Bitnami concrete5 CMS in your own BluePrints, complete the following steps:
Add an OS Template supported by the service.
Add the Apache 2.2.0 Web Server service.
Add the MySQL 5.0.0 Database server service.
Add the Bitnami concrete5 CMS service. Set the base_password property for the Bitnami concrete5 CMS service to match the MySQL service password - self:MySQL:db_root_password. For remote database installations you can also set the mysql_hostname and the mysql_port properties.
image::images/concrete5 cms_blueprint.png["concrete5 CMS Blueprint",title="concrete5 CMS Blueprint",align="center",caption="Figure 5: "]
The Bitnami concrete5 CMS Blueprint provides a server specification that includes:
A ready to run version of concrete5 CMS.
Blueprints make it easy to launch servers that share a well-defined, repeatable configuration. To launch a server based on a Blueprint, go to the Applications section in the vFabric UI and select one of the Bitnami concrete5 CMS Blueprints available in the system.
You need to specify a value for the concrete5 cms_password property for the Bitnami concrete5 CMS service. This is the password that will be used to log into the application.
Optionally, you can specify the following parameters:
concrete5 cms_user: The username that will be used to log in into the application. The default value is user.
concrete5 cms_user_name: Full name for the concrete5 CMS administrator user. The default value is User Name.
concrete5 cms_mail: concrete5 CMS administrator email address. The default value is firstname.lastname@example.org.
Once you have launched Bitnami concrete5 CMS, you can view the details for the running machines in your deployment, including the IP of the server where concrete5 CMS is running. Pointing your browser to http://<ip>/concrete5 cms will take you to the main screen of your application. You will be presented with a login screen:
image::images/concrete5 cms-login.png["Login Screen",title="Login Screen",align="center",caption="Figure 6: "]
You can now enter the username and password provided at launch time to access the application.
The installation of all Bitnami applications is standardized. This section provides an overview of where each component is located in the event that you need to log in to your server, which you can do using the VMware console.
The standard location for the Bitnami Library Application files is under /opt/bitnami. The following top-level folders are available:
mysql/: Contains configuration files related to MySQL. No MySQL binaries or libraries are bundled with Bitnami for VMware deployments. Instead, the apps deployed integrate with the existing MySQL server provided by the distribution (either local or remote) and that has been configured using the VMware vFabric™ Application Director service template.
apache2/: Contains configuration files related to Apache. No Apache binaries or libraries are bundled with Bitnami for VMware deployments. Instead, the apps deployed integrate with the existing Apache server provided by the distribution and that has been configured using the VMware vFabric™ Application Director service template.
scripts/: Control scripts internal to Bitnami.
apps/: The directory containing the Bitnami applications that have been installed.
And, inside apps/concrete5 cms folder:
You will find the application files for Bitnami concrete5 CMS under apps/concrete5 cms/htdocs/.
Apache configuration files for Bitnami concrete5 CMS, under apps/concrete5 cms/conf/ as well as optional configuration scripts under scripts/.
At the top level of the installation you will find the following additional files:
properties.ini: This file is readable only for the user that the installation was performed as. It includes information related to installation paths and configuration settings for the installed applications and associated services.
ctlscript.sh: Management script that allows you to start / stop different services. It provides a consistent interface across operating systems and services. You can find more information by typing /opt/bitnami/ctlscript.sh restart
The reason that all configuration and application files are located inside /opt/bitnami is to remain consistent with other Bitnami application packages such as native installers and VMs that can be downloaded from (http://bitnami.com). Maintaining a common filesystem layout across operating systems and delivery mechanisms helps in many scenarios, such as moving from local laptop development environment to a vCloud production environment.
You can find additional information about Bitnami Applications for VMware at http://bitnami.com/vmware