change the repo stackforge to openstack and github to cgit

change the repo stackforge to openstack
and change github to cgit

Change-Id: I1bf3b1ed517e1f70b0b2cedee0c01681eda544f8
This commit is contained in:
zhurong 2015-12-20 21:16:34 +08:00
parent 5da4c5f22a
commit 4b158f921a
2 changed files with 11 additions and 11 deletions

View File

@ -7,7 +7,7 @@ Some objects and actions can be used in several application deployments.
All common parts are grouped into MuranoPL libraries.
Murano core library is a set of classes needed in each deployment.
Class names from core library can be used in the application definitions.
This library is located under the `meta <https://github.com/stackforge/murano/tree/master/meta/io.murano>`_
This library is located under the `meta <https://git.openstack.org/cgit/openstack/murano/tree/meta/io.murano>`_
directory.
Classes included in the Murano core library are as follows:
@ -41,7 +41,7 @@ All MuranoPL classes are implicitly inherited from this class.
.. seealso::
Source `Object.yaml
<https://github.com/openstack/murano/blob/master/meta/io.murano/Classes/Object.yaml>`_
<https://git.openstack.org/cgit/openstack/murano/tree/meta/io.murano/Classes/Object.yaml>`_
file.
@ -57,7 +57,7 @@ this class.
.. seealso::
Source `Application.yaml
<https://github.com/openstack/murano/blob/master/meta/io.murano/Classes/Application.yaml>`_
<https://git.openstack.org/cgit/openstack/murano/tree/meta/io.murano/Classes/Application.yaml>`_
file.
@ -71,7 +71,7 @@ Manages security groups during an application deployment.
.. seealso::
Source `SecurityGroupManager.yaml
<https://github.com/openstack/murano/blob/46d993702fa952bcc25acf97ebbb24d0ac108a65/meta/io.murano/Classes/system/SecurityGroupManager.yaml>`_
<https://git.openstack.org/cgit/openstack/murano/tree/meta/io.murano/Classes/system/SecurityGroupManager.yaml>`_
file.
@ -124,7 +124,7 @@ Environments is intent to group applications to manage them easily.
.. seealso::
Source `Environment.yaml
<https://github.com/openstack/murano/blob/master/meta/io.murano/Classes/Environment.yaml>`_
<https://git.openstack.org/cgit/openstack/murano/tree/meta/io.murano/Classes/Environment.yaml>`_
file.
@ -183,7 +183,7 @@ deploying, joining to the network, applying security group, and deleting.
.. seealso::
Source `Instance.yaml
<https://github.com/openstack/murano/blob/master/meta/io.murano/Classes/resources/Instance.yaml>`_
<https://git.openstack.org/cgit/openstack/murano/tree/meta/io.murano/Classes/resources/Instance.yaml>`_
file.
@ -223,7 +223,7 @@ The basic abstract class for all MuranoPL classes representing networks.
.. seealso::
Source `Network.yaml
<https://github.com/openstack/murano/blob/master/meta/io.murano/Classes/resources/Network.yaml>`_
<https://git.openstack.org/cgit/openstack/murano/tree/meta/io.murano/Classes/resources/Network.yaml>`_
file.
.. _logger:
@ -304,8 +304,8 @@ This method uses the ERROR level:
.. seealso::
* Source `Logger.yaml
<https://github.com/openstack/murano/blob/master/meta/io.murano/Classes/system/Logger.yaml>`_
<https://git.openstack.org/cgit/openstack/murano/tree/meta/io.murano/Classes/system/Logger.yaml>`_
file.
* `OpenStack networking logging
configuration <http://docs.openstack.org/liberty/config-reference/content/networking-options-logging.html>`_.
configuration <http://docs.openstack.org/liberty/config-reference/content/networking-options-logging.html>`_.

View File

@ -63,7 +63,7 @@ of the model goes. So murano understands that instead of simple value
MuranoPL object is used. You can pick parameters you got from a user
(they should be described in the Forms section) and pick the right place
where they should be set. To do this `YAQL
<https://github.com/ativelkov/yaql/blob/master/README.md>`_ is
<https://git.openstack.org/cgit/openstack/yaql/tree/README.rst>`_ is
used. Two yaql functions are used for object model generation:
* **generateHostname** is used for machine hostname generation; it accepts 2 arguments: name pattern (string) and index (integer). If '#' symbol is present in name pattern, it will be replaced with the index provided. If pattern is not given, a random name will be generated.
@ -160,7 +160,7 @@ attributes are the following:
Note that hidden field's description will still be visible in the descriptions area (if given).
Hidden fields are used storing some data to be used by other, visible fields.
* **minLength**, **maxLength** (for string fields) and **minValue**, **maxValue** (for integer fields) are transparently translated into django validation properties.
* **validators** is a list of dictionaries, each dictionary should at least have *expr* key, under that key either some `YAQL <https://github.com/stackforge/yaql/blob/master/README.rst>`_ expression is stored, either one-element dictionary with *regexpValidator* key (and some regexp string as value). Another possible key of a validator dictionary is *message*, and although it is not required, it is highly desirable to specify it - otherwise, when validator fails (i.e. regexp doesn't match or YAQL expression evaluates to false) no message will be shown. Note that field-level validators use YAQL context different from all other attributes and section: here *$* root object is set to the value of field being validated (to make expressions shorter).
* **validators** is a list of dictionaries, each dictionary should at least have *expr* key, under that key either some `YAQL <https://git.openstack.org/cgit/openstack/yaql/tree/README.rst>`_ expression is stored, either one-element dictionary with *regexpValidator* key (and some regexp string as value). Another possible key of a validator dictionary is *message*, and although it is not required, it is highly desirable to specify it - otherwise, when validator fails (i.e. regexp doesn't match or YAQL expression evaluates to false) no message will be shown. Note that field-level validators use YAQL context different from all other attributes and section: here *$* root object is set to the value of field being validated (to make expressions shorter).
* **widgetMedia** sets some custom *CSS* and *JavaScript* used for the field's widget rendering. Note, that files should be placed to Django static folder in advance.
Mostly they are used to do some client-side field enabling/disabling, hiding/unhiding etc.
This is a temporary field which will be dropped once Version 3 of Dynamic UI is implemented (since it will transparently translate YAQL expressions into the appropriate *JavaScript*).