Home

Table of Contents

QPackages: the Easy Way to Install, Maintain and Configure Applications

Searching Racktivity Strategy

With the Q-Package (virtual applications), Q-layer introduces an application packaging system, that has the advantages of a conventional packaging system but not the complexity. Q-Package takes away all the packaging difficulties and is targeted specifically at system administrators, who are not considered developers.

A number of existing open-source applications has been packaged as a Q-Package. These packaged open-source applications are called "QPackages".

About

The Qpackages library is an initiative of Q-layer. The target audience includes system administrators, developers and anyone involved in installation, configuration and maintenance of software packages on servers and desktop computers. Q-Packages framework is like RPM or Apt-get, but more advanced and not tied to a single distribution or operating system.

A Q-Package is an application that has been packaged for easy installation using the application packaging framework of Q-Shell. Q-Shell is a powerful and easy-to-use cross platform shell.
Q-Shell can be installed on Linux, OpenSolaris and Windows, it provides powerful features for system administration and it is the primary user interface to download, install and handle all Q-Packages.
Q-Shell can be downloaded from http://www.pylabs.org.

Benefits

For end-users

  • Cross-platform uniform installation of applications: Linux/Unix, Windows and OpenSolaris (Mac OSX coming soon)

  • Integrated configuration management: configure each application from Q-Shell using a standard set of commands

  • Automatic updates

  • Dependency management

  • Fully sandboxed installation on Linux and OpenSolaris (no conflicts between applications and libraries)

  • Partially sandboxed installation on Windows

For developers

  • Packaging your application as a Q-Package gives users seamless access to your application, you don't have to worry about pre-installation requirements

  • You can assign quality levels to each application and maintain different branches in the field (testing, production etc.)

  • Very easy dependency management: e.g. if your application requires Apache, just create a dependency on Apache

  • Uniform configuration and control of all applications in Q-Shell: e.g. manage Apache by using commands such as q.manage.apache.start()
 
Recently Updated
by Kristof De Spiegeleer (22 Aug)
My qpackage seems to have no files, how to troubleshoot
by Kristof De Spiegeleer (22 Aug)
Glossary
Domains configuration file
by Ayman Taher (09 Aug)
Confluence
by Abdelrahman Hegazy (08 Aug)
ConfluenceTest
by Kristof De Spiegeleer (08 Aug)
networkinventorymanager
by Kristof De Spiegeleer (08 Aug)
QPackages3 (to be deprecated)
by Kristof De Spiegeleer (08 Aug)
Document Archiver
by Kristof De Spiegeleer (08 Aug)
ServerApps
by Kristof De Spiegeleer (05 Aug)
ExampleSourcesCfgFromMercurial
by Kristof De Spiegeleer (05 Aug)
Home
by Kristof De Spiegeleer (05 Aug)
Contributors
by Kristof De Spiegeleer (05 Aug)
Attachments
by Kristof De Spiegeleer (05 Aug)
Internal
by Luk Macken (29 Apr)
How to update a Qpackage4
by Luk Macken (29 Apr)
Administrating QPackages4
by Luk Macken (29 Apr)
How To Create a basic Q-Package4
by Luk Macken (29 Apr)
QPackages 4 - HowTo's
by Nancy Sami (Gone) (29 Mar)
KeySpace
by Sanjay Vaid (04 Mar)
Getting started with qpackages4

bugs & source code

  • see [contribute]

License

The license of each individual OpenVApp is the same as the license of the original application which is packaged inside the Q-Package.
In order to install and use Q-Packages, Q-Shell needs to be installed. Visit Pymonkey.org for more information on the license of Q-Shell.

Dependencies and related projects

  • Pymonkey.org: PyMonkey is an open-source scripting language, tailored to system administrators (Q-Shell uses PyMonkey scripts, e.g. to automate manual tasks)
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.