Author: smohanty Date: Mon Sep 15 20:56:16 2014 New Revision: 1625161 URL: http://svn.apache.org/r1625161 Log: Fixing image links
Modified: incubator/slider/site/trunk/content/docs/slider_specs/application_configuration.md incubator/slider/site/trunk/content/docs/slider_specs/application_package.md incubator/slider/site/trunk/content/docs/slider_specs/creating_app_definitions.md Modified: incubator/slider/site/trunk/content/docs/slider_specs/application_configuration.md URL: http://svn.apache.org/viewvc/incubator/slider/site/trunk/content/docs/slider_specs/application_configuration.md?rev=1625161&r1=1625160&r2=1625161&view=diff ============================================================================== --- incubator/slider/site/trunk/content/docs/slider_specs/application_configuration.md (original) +++ incubator/slider/site/trunk/content/docs/slider_specs/application_configuration.md Mon Sep 15 20:56:16 2014 @@ -23,7 +23,7 @@ App Configuration is a folder containing In addition, application may have configuration parameters that do not necessarily go into a config files. Such configurations may be used during template expansion (parameters in env.sh files), as environment variables (e.g. JAVA_HOME), customize user names (for runas). These configurations can be provided as user inputs or are automatically inferred from the environment. Such configurations are stored in a file named "app_config.xml". -![Image](../../resources/images/app_config_folders_01.png?raw=true) +![Image](../../images/app_config_folders_01.png?raw=true) A config file is of the form: Modified: incubator/slider/site/trunk/content/docs/slider_specs/application_package.md URL: http://svn.apache.org/viewvc/incubator/slider/site/trunk/content/docs/slider_specs/application_package.md?rev=1625161&r1=1625160&r2=1625161&view=diff ============================================================================== --- incubator/slider/site/trunk/content/docs/slider_specs/application_package.md (original) +++ incubator/slider/site/trunk/content/docs/slider_specs/application_package.md Mon Sep 15 20:56:16 2014 @@ -42,7 +42,7 @@ various templates used by the applicatio other scripts, txt files, tarballs, etc. -![Image](../../resources/images/app_package_sample_04.png) +![Image](../../images/app_package_sample_04.png?raw=true) The example above shows a semi-expanded view of an application "HBASE-YARN-APP" and the package structure for OOZIE command scripts. Modified: incubator/slider/site/trunk/content/docs/slider_specs/creating_app_definitions.md URL: http://svn.apache.org/viewvc/incubator/slider/site/trunk/content/docs/slider_specs/creating_app_definitions.md?rev=1625161&r1=1625160&r2=1625161&view=diff ============================================================================== --- incubator/slider/site/trunk/content/docs/slider_specs/creating_app_definitions.md (original) +++ incubator/slider/site/trunk/content/docs/slider_specs/creating_app_definitions.md Mon Sep 15 20:56:16 2014 @@ -21,7 +21,7 @@ Slider AppPackages are a declarative def An application instance consists of several active component such as one or more masters and several slaves. There may be a number of accompanying processes in addition to the basic master/slave processes - lets refer to all processes as app component instances. When run in the context of Yarn, the application specific processes are activated within individual Yarn Container. If you pry into an Yarn container (created through Slider) it will be apparent as to what is the role of Slider-Agent and the actual application components. The following image provides an high-level view. Within a container there are at least two processes - and instance of a slider agent and an instance of an application component. The application can itself spawn more procsses if needed. -![Image](../../resources/images/slider-container.png?raw=true) +![Image](../../images/slider-container.png?raw=true) Figure 1 - High-level view of a container