Added example for scheduler hints

source/guide/3.2/installation.md

@@ -180,7 +180,6 @@ Now let's say you want to install the 3.2a4 release specifically. You should run
 python get-cloudify.py --version 3.2a4
 {% endhighlight %}
 
-
 # Installing From PyPI
 
 Cloudify's CLI is also distributed to PyPI. You can install Cloudify from PyPI though we recommend using the script as installing from PyPI does not handle prerequisites and does not provide some other comforts the script is designed to provide.
@@ -197,6 +196,29 @@ source virtual-env-name/bin/activate
 
 {%endtip%}
 
+## Prerequisites for Compilation when installing from PyPI
+Cloudify's CLI has dependencies that require compilation on your machine:
+
+### Windows
+For Windows it's suggested to use [Unofficial Windows Binaries for Python](http://www.lfd.uci.edu/~gohlke/pythonlibs)
+and install the following packages:
+
+1. PyCrypto
+2. PyYAML (by default, if no compiler is found, PyYAML's installation will fall-through to a non-compiled version.)
+
+### Linux
+
+* Under Ubuntu/Debian, you'll need to install the `python-dev` package.
+* Under CentOS/RHEL, you'll need to install the `python-devel` package.
+
+### OS X
+You will need Apple's developers tools that are installed with Xcode.
+
+{% tip title=Tip%}
+By default, cloudify will place the CLI log file under this path: '{tmp_folder}/cloudify-{username}/cloudify-cli.log'
+You can change this by editing the 'config.yaml' file found at '{cli_installation_folder}/.cloudify'
+{% endtip %}
+
 ## Installing the latest Stable Release
 To install the CLI run the following command:
 
@@ -218,8 +240,7 @@ Now let's say you want to install the 3.1rc2 release specifically. You should ru
 pip install cloudify==3.1rc2
 {% endhighlight %}
 
-
-## installing from Github
+# installing from Github
 To install the CLI from Github you must install several modules in the correct order.
 
 Let's say you want to install from the `master` branch. run:
@@ -232,30 +253,6 @@ pip install https://github.com/cloudify-cosmo/cloudify-script-plugin/archive/mas
 pip install https://github.com/cloudify-cosmo/cloudify-cli/archive/master.zip
 {% endhighlight %}
 
-## Prerequisites for Compilation when installing from PyPI
-Cloudify's CLI has dependencies that require compilation on your machine:
-
-### Windows
-For Windows it's suggested to use [Unofficial Windows Binaries for Python](http://www.lfd.uci.edu/~gohlke/pythonlibs)
-and install the following packages:
-
-1. PyCrypto
-2. PyYAML (by default, if no compiler is found, PyYAML's installation will fall-through to a non-compiled version.)
-
-### Linux
-
-* Under Ubuntu/Debian, you'll need to install the `python-dev` package.
-* Under CentOS/RHEL, you'll need to install the `python-devel` package.
-
-### OS X
-You will need Apple's developers tools that are installed with Xcode.
-
-{% tip title=Tip%}
-By default, cloudify will place the CLI log file under this path: '{tmp_folder}/cloudify-{username}/cloudify-cli.log'
-You can change this by editing the 'config.yaml' file found at '{cli_installation_folder}/.cloudify'
-{% endtip %}
-
-
 # What's Next?
 Now that you know the requirements and have the CLI installed, you can [bootstrap your own manager](getting-started-bootstrapping.html)
 

source/guide/3.2/plugin-openstack.md

@@ -588,7 +588,7 @@ Some relationships take effect in non-relationship operations, e.g. a subnet whi
 
 **Mapped Operations:**
 
-  * `cloudify.interfaces.relationship_lifecycle.unlink`: detaches the volume from the server.
+  * `cloudify.interfaces.relationship_lifecycle.unlink`: detaches the server from the port.
     * **Inputs:**
       * `openstack_config` see the [Openstack Configuration](#openstack-configuration).
 
@@ -1137,6 +1137,45 @@ Node by node explanation:
 {% endgcloak %}
 
 
+## Example V
+
+This example shows how to pass scheduler hints to Nova, in order to achieve affinity or anti-affinity effect.
+
+{% togglecloak id=5 %}
+Example V
+{% endtogglecloak %}
+
+{% gcloak 5 %}
+At this stage, the OpenStack plugin does not provide the functionality of managing server groups
+(creation, deletion) through blueprints. Therefore, it is assumed that a server group has already been created
+by other means, for example:
+
+{% highlight bash %}
+nova server-group-create --policy anti-affinity my-anti-affinity-group
+{% endhighlight %}
+
+Given that, you can define a node template as follows (this example receives the server group's name from an
+input):
+
+{% highlight yaml %}
+inputs:
+  server_group:
+    type: string
+
+node_templates:
+  my_server:
+    type: cloudify.openstack.nodes.Server
+    interfaces:
+      cloudify.interfaces.lifecycle:
+        create:
+          inputs:
+            args:
+              scheduler_hints:
+                group: [ get_input: server_group ]
+{% endhighlight %}
+{% endgcloak %}
+
+
 # Tips
 
 * It is highly recommended to **ensure that Openstack names are unique** (for a given type): While Openstack allows for same name objects, having identical names for objects of the same type might lead to ambiguities and errors.