Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of runseb@gmail.com designates
 209.85.215.171 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [HOW-TO] Custom REST call on Destroy and Deploy
From: sebgoa <runseb@gmail.com>
In-Reply-To: 
 <D2EE6B3265AD864EB3EA4F5C670D256F27345F66@EXDFO01L-CRP-06.webmdhealth.net>
Date: Sat, 5 Oct 2013 09:30:27 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <93B6E7CA-9C47-47E8-B705-7C3E68B1448C@gmail.com>
References: 
 <D2EE6B3265AD864EB3EA4F5C670D256F27345F66@EXDFO01L-CRP-06.webmdhealth.net>
To: dev@cloudstack.apache.org


On Oct 4, 2013, at 9:21 PM, "Musayev, Ilya" <imusayev@webmd.net> wrote:

> We would like to add additional operations in ACS when we do deploy =
and destroy.
>=20
> For example, when VM is destroyed, we want to make create a JIRA =
ticket (rest call) to track the decomision process.
> When VM is deployed, we may need to do something else, but also rest =
based?
>=20
> I can see 2 ways of doing this,
>=20
>=20
> 1)      Extend the UI and initiate extra REST calls via java script  =
(low risk)
>=20
> 2)      Add more functionality to API Command (extra work and =
maintenance burden)
>=20
> 3)      Create a Custom front end (seems like a lot of work)
>=20
>=20
> How can this be done most efficiently and hopefully with least =
intrusion?

How do you make the destroy and deploy ?

Would be easy to do it with a wrapper that also creates those tickets :)=