openstack
/
murano
Code Issues Proposed changes
murano/meta
History
Paul Bourke 103f67815a Allow users to assign a security group to an app 
This patch allows users to supply a list* of their own security groups to
an instance, rather than using the application defined one (built via
the SecurityGroupManager).

* Note, while we can support multiple security groups, murano-dashboard
currently has no UI element to select multiple items. This means that
currently users are restricted to selecting one group. If/when the
UI is improved this change can easily support multiple groups.

Example
=======

Application authors can make this available in their apps as follows:

UI.yaml
-------
Forms:
  - instanceConfiguration:
      fields:
          ...
        - name: securityGroups
          type: securitygroup
          label: Security Group
          required: false

Class.yaml:
----------
  Application:
    ?:
       type: com.paul.HelloWorld
    instance:
      ?:
        type: io.murano.resources.LinuxMuranoInstance
      name: $.instanceConfiguration.hostname
      securityGroups: $.instanceConfiguration.securityGroups
      ...

DocImpact
Change-Id: I60d37cfe034c467e894ee93cf3718e463bf49337
Partially-Implements: blueprint app-use-existing-security-group
 		2017-04-27 17:37:20 +01:00
..
io.murano Allow users to assign a security group to an app 2017-04-27 17:37:20 +01:00
io.murano.applications Configuration is now properly applied to new nodes 2016-11-17 00:48:11 +00:00
README.rst Update meta folder readme 2015-05-21 15:10:44 +03:00

README.rst

Murano Core Classes

This folder contains common Murano classes combined to Core Library.

The content of this folder needs to be zipped and imported into Murano. After that Murano applications can be deployed.

To find murano-applications and explore how the common classes are used in Murano Applications, please refer to Murano Application Repository