Image Management Using the Virtuozzo Application Catalog

Transcription

1 Image Management Using the Virtuozzo Application Catalog INTRODUCTION The cloud and hosting markets are developing rapidly. These days, one of the most common customer demands is for a service that allows the rapid deployment of preconfigured, ready-to-use applications. For service providers, however, building and maintaining dozens of such applications can be a major and expensive technical challenge, particularly with respect to the serious risks posed by security vulnerabilities found in many outdated applications. To address this need, Odin has partnered with Bitnami to jointly offer the Virtuozzo Application Catalog. Available as a new subscription for Virtuozzo, this new service provides the latest versions of your favorite applications and development stacks, all tested, optimized and ready for deployment in the environment of your choice. The catalog offers Wordpress, Redmine, SugarCRM, Alfresco, Drupal, MediaWiki, GitLab, and dozens of other popular applications designed for a wide variety of users and businesses. Each application is precompiled and preconfigured with everything necessary to work out-of-the-box in a container or in a virtual machine. You no longer need to waste enormous amounts of time fixing and updating your own application catalog. BUSINESS MODEL AND INTEGRATION WITH YOUR OWN PROVISIONING SYSTEM The Virtuozzo Application Catalog subscription licenses the service provider to deploy offered application images on any host running Virtuozzo 6 or newer, and launch such instances as virtual machines or as containers. The service provider is free to choose the most suitable monetization strategy. The most common models are: Target specific verticals that utilize particular applications. Promote the discover and consumption of additional IaaS-based hosting products by integrating the image catalog into the service provider s existing provisioning system, providing a seamless, one-click application deployment experience. Each application is accompanied by a standard computer-readable description (metadata) that can be used to build a catalog in the service provider s own control panels and online stores. For example, Ametys CMS has the following description: name = Ametys categories = CMS Parallels IP Holdings GmbH Vordergasse Schaffhausen Switzerland Tel: Fax: Parallels IP Holdings GmbH and its affiliates. All rights reserved. This product is protected by United States and international copyright laws. The product s underlying technology, patents, and trademarks are listed at Microsoft, Windows, Windows Server, Windows NT, Windows Vista, and MS-DOS are registered trademarks of Microsoft Corporation. Apple, Mac, the Mac logo, Mac OS, ipad, iphone, ipod touch, FaceTime HD camera and isight are trademarks of Apple Inc., registered in the US and other countries. Linux is a registered trademark of Linus Torvalds. All other marks and names mentioned herein may be trademarks of their respective owners. description = Ametys CMS is a multi-purpose Web factory and can run corporate websites, blogs, portals, and corporate wikis on the same server. Its features include roll-out enterprise portals, websites, blogs through a website factory and share contents. version = ports = 80, 443 logo.png

2 The catalog item descriptions of all supported applications are download as a single package. Depending on your needs, you can then create your own customized list of selected applications, or expose the entire catalog to your customers. When applications in the catalog are updated, or a new application added, the catalog s description package is updated as well. If you publish a customized list of catalog applications, you will need to maintain that list; review any ongoing updates to the catalog s description package and edit your customized list as desired. If you decide to expose all available applications to end users, you can simply convert the updated catalog listing into an end-user application catalog. INSTALLATION OPTIONS Each application is delivered as a: Container image Virtual machine image Standalone self-installer. With container or virtual machine images, you can quickly create a new instance, and only need to specify an image name as what Virtuozzo calls an OS template. The self-installer, on the other hand, allows you to install an application into an existing instance; any required application parameters can be provided in either attended or unattended mode. PASSWORD MANAGEMENT A password for a Virtuozzo Application Catalog image can be set in one of two ways: Automatically generated during instance creation Specified manually before starting the created instance. The password will be set during its initial configuration The resulting end user access credentials are saved to a file in the instance s root directory. You will need to retrieve and provide them to the application user. Note: Certain application images have specific password requirements, so make sure that the password is at least 8 characters long, is alphanumeric and has at least one digit. ABOUT THIS RELEASE The Virtuozzo Application Catalog is currently available only as a technical preview. While fully functional, delivery mechanisms are still being polished and it is therefore not yet intended for production. You should use this release to begin evaluating the catalog and how to integrate it into your own business operation systems. At the moment, the catalog preview is available to all Virtuozzo customers through the latest version of Virtuozzo 6. Using it requires no trial license simply follow the instructions below to set it up. If you have questions, please consult Bitnami s documentation ( the Virtuozzo forum ( or contact the Virtuozzo support team. The Virtuozzo Application Catalog service is slated for a production-ready launch in mid-q Please note that post-launch: Anonymous access to the catalog will be disabled. Access to the catalog will be through subscription and access keys. Free trial and evaluation access will be available. KNOWN RESTRICTIONS Virtuozzo Application Catalog images and self-installers use custom installation paths and configurations. Consequently, you should not install the same application using a standard procedure within the same running instance, nor should you use Virtuozzo EZ application templates. When installing multiple Web applications, ensure there are no conflicts for ports 80 and 443. The best way to avoid such conflicts is to create a new instance. Once an application is running, you may need to update it as required by said application. For details on updating certain applications, refer to Bitnami for help at

3 CONFIGURATION AND GETTING STARTED Obtaining Catalog Metadata 1 Make sure that the latest Virtuozzo version is installed: # yum update 2 Install the image catalog repository on the Virtuozzo node: # yum install catalog-repo If you want to download the complete catalog description metadata, run #yum install catalog-metadata All information is unpacked and stored in /vz/catalog/ organized according to application categories. The catalog is ready to use, and you can create instances. Creating Container Instances # yum groupinfo ez-catalog As an example, we shall create a Wordpress container instance named wordpress-ct. 1 Search for the Wordpress image. # yum search bitnami-wordpress 2 Create a container, specifying the image name as an OS template: # prlctl create wordpress-ct --vmtype ct --ostemplate ubuntu x86_64-bitnami_wordpress --config vswap.2048mb Virtuozzo will automatically download the image and spawn a container. Once the container is up, it may take a few seconds to configure the chosen application. 3 Connect the container to the external network and access Wordpress via browser. # prlctl set wordpress-ct --device-add net --dhcp yes --network Bridged 4 Start the container. To wait until the configuration is complete, use the --wait parameter: # prlctl start wordpress-ct --wait The instance is up and running.

4 5 Access end user credentials for the created application: # prlctl exec wordpress-ct cat bitnami_credentials.txt The password is generated automatically inside the VM or containers during its provisioning (for details, see Password Management on page 2). Provide the credentials from the file to the application user. Virtuozzo Application Catalog images are nearly identical to OS templates, and you do not need to learn any additional commands to work with them. For example, to speed up container creation, you can 1 use yum to download the image to the node: # yum install ubuntu x86_64-bitnami_wordpress-ez 2 and then cache it: # yum install ubuntu x86_64-bitnami_wordpress or: # vzpkg create cache ubuntu x86_64-bitnami_wordpress Creating a container will be significantly faster now. For example: 1 Create a container from a cached template: # prlctl create wordpress-ct-cached --vmtype ct --ostemplate ubuntu x86_64-bitnami_wordpress --config vswap.2048mb 2 Configure network in the container: # prlctl set wordpress-ct-cached --device-add net --dhcp yes --network Bridged 3 Set a Wordpress password. To do this: 3.1 mount container file system to the host: # prlctl mount wordpress-ct-cached 3.2 Copy the EnvID value from the output: # prlctl list -i wordpress-ct-cached

5 3.3 Create a file with a new Wordpress password: # echo vz6catalog > /vz/root/<env_id>/opt/bitnami/var/data/metadata_applications_password 4 Start the container: # prlctl start wordpress-ct-cached --wait 5 Obtain container s IP address: # prlctl exec wordpress-ct-cached ifconfig 6 Access Wordpress in a browser at the obtained IP address and verify that you can login with the following credentials: username user, password vz6catalog. Creating Virtual Machine Instances # yum groupinfo vm-catalog As an example, we shall create an AbanteCart VM instance named abantecart-vm. 1 Download the image to the host. For example: # yum install bitnami-abantecart 2 If required, register it as a template: # register_precached_vm bitnami-abantecart 3 Create a new instance based on the template: # prlctl create abantecart-vm --ostemplate bitnami-abantecart 4 Start the virtual machine. To wait until the configuration is complete, use the --wait parameter: # prlctl start abantecart-vm --wait The instance is up and running.

6 5 Access end user credentials for the created application: # prlctl exec abantecart-vm cat bitnami_credentials.txt The password is generated automatically inside the VM or containers during its provisioning, see Password Management on page 2). Provide the credentials from the file to the application user. Using Self-Installers # yum groupinfo selfinst-catalog As an example, we shall create a container instance named codiad-installer-ct and install Codiad into it. 1 Download the self-installer to the host: # yum install bitnami-codiad-selfinst 2 Create and start an Ubuntu container first: # prlctl create codiad-installer-ct --vmtype ct --ostemplate ubuntu x86_64 # prlctl start codiad-installer-ct 3 Configure the network adapter: # prlctl set codiad-installer-ct --device-add net --dhcp yes --network Bridged 4 Copy the downloaded self-installer into the container. In this example, the self-installer was downloaded to /vz/self-installers/ bitnami-codiad linux-x64-installer.run. 5 Launch headless installation inside the container: # vzctl exec codiad-installer-ct <path_to_installer_inside_container> The instance is up and running. Receiving Updates Updated images can be installed with a standard package manager. For example:using Self-Installers # yum update