Author: olamy Date: Mon Jul 9 10:08:36 2012 New Revision: 1359019 URL: http://svn.apache.org/viewvc?rev=1359019&view=rev Log: 2 spaces indenting in xml
Modified: incubator/kalumet/site/src/site/xdoc/index.xml Modified: incubator/kalumet/site/src/site/xdoc/index.xml URL: http://svn.apache.org/viewvc/incubator/kalumet/site/src/site/xdoc/index.xml?rev=1359019&r1=1359018&r2=1359019&view=diff ============================================================================== --- incubator/kalumet/site/src/site/xdoc/index.xml (original) +++ incubator/kalumet/site/src/site/xdoc/index.xml Mon Jul 9 10:08:36 2012 @@ -16,52 +16,59 @@ limitations under the License. --> <document> - <properties> - <title>What is Apache Kalumet?</title> - </properties> - <body> - <section name="What is Apache Kalumet?"> - <p> - Apache Kalumet is a complete deployment and provisioning platform. - It's a perfect complement of continuous integration tools (such as Jenkins, Continuum, etc), - by providing continuous deployment. - </p> - <p> - It supports custom provisioning plan (named kscripts), and provides native support - of differents technologies, including J2EE, OSGi, etc. - </p> - <p> - For instance, in the enterprise, the continuous integration tool provides an artifact. - This artifact could be in different format (jar, war, ear, zip, tar.gz, etc) and may contain: - <ul> - <li>others archives</li> - <li>configuration files which have to be updated to fit a target environment</li> - <li>eventually SQL scripts to update a database</li> - </ul> - More over, these artifacts may require some middlewares to run: - <ul> - <li>setup an operating system matching the middlewares requirements</li> - <li>an archive containing PHP, HTML, etc, require an Apache HTTPd server</li> - <li>a war file requires a JSP/Servlet engine such as Apache Tomcat or Jetty</li> - <li>an ear requires a J2EE application server such as Apache Geronimo, IBM WebSphere, Oracle WebLogic</li> - <li>etc ...</li> - </ul> - From an industrial perspective, it's the role of the administrators to: - <ul> - <li>install and setup the operating system</li> - <li>install the middlewares (for instance uncompress the middlewares archives, create response files, launch installation script, etc)</li> - <li>customize the middlewares (for instance setup the httpd.conf file, install additional modules, create and deploy data source in an application server, etc)</li> - <li>uncompress the application artifacts, and deploy into the middlewares</li> - </ul> - It requires different teams, a lot of scripts, mostly not managed in a central place, and a human error risk is high. - More the number of environments is high, with differents technologies, more the effort is important for the administrators. - </p> - <p> - Apache Kalumet provides a central platform (the Kalumet Console), interacting with agents, to handle all these tasks. - </p> - <p> - <b>NB: the Kalumet website is under construction, new resources will be available soon.</b> - </p> + <properties> + <title>What is Apache Kalumet?</title> + </properties> + <body> + <section name="What is Apache Kalumet?"> + <p> + Apache Kalumet is a complete deployment and provisioning platform. + It's a perfect complement of continuous integration tools (such as Jenkins, Continuum, etc), + by providing continuous deployment. + </p> + <p> + It supports custom provisioning plan (named kscripts), and provides native support + of differents technologies, including J2EE, OSGi, etc. + </p> + <p> + For instance, in the enterprise, the continuous integration tool provides an artifact. + This artifact could be in different format (jar, war, ear, zip, tar.gz, etc) and may contain: + <ul> + <li>others archives</li> + <li>configuration files which have to be updated to fit a target environment</li> + <li>eventually SQL scripts to update a database</li> + </ul> + More over, these artifacts may require some middlewares to run: + <ul> + <li>setup an operating system matching the middlewares requirements</li> + <li>an archive containing PHP, HTML, etc, require an Apache HTTPd server</li> + <li>a war file requires a JSP/Servlet engine such as Apache Tomcat or Jetty</li> + <li>an ear requires a J2EE application server such as Apache Geronimo, IBM WebSphere, Oracle WebLogic</li> + <li>etc ...</li> + </ul> + From an industrial perspective, it's the role of the administrators to: + <ul> + <li>install and setup the operating system</li> + <li>install the middlewares (for instance uncompress the middlewares archives, create response files, launch + installation script, etc) + </li> + <li>customize the middlewares (for instance setup the httpd.conf file, install additional modules, create and + deploy data source in an application server, etc) + </li> + <li>uncompress the application artifacts, and deploy into the middlewares</li> + </ul> + It requires different teams, a lot of scripts, mostly not managed in a central place, and a human error risk is + high. + More the number of environments is high, with differents technologies, more the effort is important for the + administrators. + </p> + <p> + Apache Kalumet provides a central platform (the Kalumet Console), interacting with agents, to handle all these + tasks. + </p> + <p> + <b>NB: the Kalumet website is under construction, new resources will be available soon.</b> + </p> </section> - </body> + </body> </document> \ No newline at end of file