Hi Shadeed,
A good question!
On Tue, Feb 10, 2015 at 11:45 PM, Shaheedur Haque (shahhaqu) <
shahh...@cisco.com> wrote:
> Hi,
>
> This is surely backwards. Why do deployment policies name the
> application? Why can’t a single deployment policy be referenced by multiple
> applications (just like before)?
>
> In the current release it is not possible to re-use an application
definion with multiple deploymet policies. To be more specific there is no
application template support. This is something we discussed during past
months in the Dev mailing list and decided to include it in a later release
due to the complexity of the application composite model and its deployment
process.
At the moment an application can only be deployed with a given deployment
policy. If we need to deploy the same application with a different
deployment policy we will need to use a different application id.
> Also, what is confusing is that the samples are themselves inconsistent.
> For example, the first one I looked at [3] seems to be missing *any*
> binding between the application .json and the deployment .json; are these
> samples actually supposed to work, or are they perhaps a work in progress
> only?
>
We have removed application id from the deployment policy because it is
there in the API URL which is used for deploying the application:
curl -X POST -H "Content-Type: application/json" -d
"@${iaas_artifacts_path}/deployment-policy.json"
-k -v -u admin:admin https://${host_ip}:${host_port}/api/applications/
single-cartridge-app/deploy
It seems like it has been not reflected in the deployment policy in [2].
Thanks
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
