[ 
https://issues.apache.org/jira/browse/JCLOUDS-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795768#comment-16795768
 ] 

Nhat Quang Nguyen commented on JCLOUDS-693:
-------------------------------------------

Hi,

Is there anyone who can support to implement the "existing" request parameter 
in stack update API

 
|existing (Optional)|body|boolean|A boolean specifying whether the service is 
about to reuse the existing stack template, parameters and environment. If 
{{template}} parameter is not provided, the existing template is used. If 
{{template_files}} is not provided, the existing environment is used. 
Parameters specified in the {{parameters}} key will patch over the existing 
values in the current stack. Parameters omitted will keep the existing values.|

 

/Nhat

> Support OpenStack Orchestration (Heat) API
> ------------------------------------------
>
>                 Key: JCLOUDS-693
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-693
>             Project: jclouds
>          Issue Type: New Feature
>          Components: jclouds-labs-openstack
>            Reporter: Jeremy Daggett
>            Priority: Major
>              Labels: openstack, orchestration
>
> Heat is the main project in the OpenStack Orchestration program. It 
> implements an orchestration engine to launch multiple composite cloud 
> applications based on templates in the form of text files that can be treated 
> like code. A native Heat template format is evolving, but Heat also 
> endeavours to provide compatibility with the AWS CloudFormation template 
> format, so that many existing CloudFormation templates can be launched on 
> OpenStack. Heat provides both an OpenStack-native ReST API and a 
> CloudFormation-compatible Query API.
> API Docs: http://developer.openstack.org/api-ref-orchestration-v1.html
> OpenStack Heat Wiki: https://wiki.openstack.org/wiki/Heat



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to