Return-Path: 
 <deltacloud-dev-return-1637-apmail-incubator-deltacloud-dev-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-deltacloud-dev-archive@minotaur.apache.org
Delivered-To: apmail-incubator-deltacloud-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 9BEC33EF8
	for <apmail-incubator-deltacloud-dev-archive@minotaur.apache.org>;
 Wed,  4 May 2011 19:35:44 +0000 (UTC)
Received: (qmail 83979 invoked by uid 500); 4 May 2011 19:35:44 -0000
Delivered-To: apmail-incubator-deltacloud-dev-archive@incubator.apache.org
Received: (qmail 83950 invoked by uid 500); 4 May 2011 19:35:44 -0000
Mailing-List: contact deltacloud-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:deltacloud-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:deltacloud-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:deltacloud-dev@incubator.apache.org>
List-Id: <deltacloud-dev.incubator.apache.org>
Reply-To: deltacloud-dev@incubator.apache.org
Delivered-To: mailing list deltacloud-dev@incubator.apache.org
Received: (qmail 83942 invoked by uid 99); 4 May 2011 19:35:44 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 May 2011 19:35:44 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 May 2011 19:35:42 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 2D9FBC1A56
	for <deltacloud-dev@incubator.apache.org>;
 Wed,  4 May 2011 19:35:03 +0000 (UTC)
Date: Wed, 4 May 2011 19:35:03 +0000 (UTC)
From: "Chris Lalancette (JIRA)" <jira@apache.org>
To: deltacloud-dev@incubator.apache.org
Message-ID: 
 <1828816447.22595.1304537703183.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (DTACLOUD-36) Load Balancers don't seem to be
 HATEOS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org

Load Balancers don't seem to be HATEOS
--------------------------------------

                 Key: DTACLOUD-36
                 URL: https://issues.apache.org/jira/browse/DTACLOUD-36
             Project: DeltaCloud
          Issue Type: Bug
          Components: Server
            Reporter: Chris Lalancette
            Assignee: David Lutterkort


When fetching the XML related to a load balancer, it looks like this:

<load_balancers>
  <load_balancer href="http://localhost:3001/api/load_balancers/my-load-balancer" id="my-load-balancer">
    <actions>
      <link href="http://localhost:3001/api/load_balancers/my-load-balancer" method="delete" rel="destroy"/>
    </actions>
    ...
  </load_balancer>
</load_balancers>

What you'll notice about the <actions> section is that it is missing a link to "register" a new instance with this load_balancer.  In order to be fully HATEOS, I would expect the XML above to have an action similar to:

<link href="http://localhost:3001/api/load_balancers/my-load-balancer/register" method="post" rel="register"/>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira