Return-Path: 
 <dev-return-6719-apmail-deltacloud-dev-archive=deltacloud.apache.org@deltacloud.apache.org>
X-Original-To: apmail-deltacloud-dev-archive@www.apache.org
Delivered-To: apmail-deltacloud-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id D4691D990
	for <apmail-deltacloud-dev-archive@www.apache.org>;
 Wed, 21 Nov 2012 10:36:16 +0000 (UTC)
Received: (qmail 82562 invoked by uid 500); 21 Nov 2012 10:36:16 -0000
Delivered-To: apmail-deltacloud-dev-archive@deltacloud.apache.org
Received: (qmail 82462 invoked by uid 500); 21 Nov 2012 10:36:16 -0000
Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@deltacloud.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@deltacloud.apache.org>
List-Post: <mailto:dev@deltacloud.apache.org>
List-Id: <dev.deltacloud.apache.org>
Reply-To: dev@deltacloud.apache.org
Delivered-To: mailing list dev@deltacloud.apache.org
Received: (qmail 82439 invoked by uid 99); 21 Nov 2012 10:36:15 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Nov 2012 10:36:15 +0000
X-ASF-Spam-Status: No, hits=-5.0 required=5.0
	tests=RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of mfojtik@redhat.com designates
 209.132.183.28 as permitted sender)
Received: from [209.132.183.28] (HELO mx1.redhat.com) (209.132.183.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Nov 2012 10:36:11 +0000
Received: from int-mx11.intmail.prod.int.phx2.redhat.com
 (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24])
	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qALAZov7016660
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <dev@deltacloud.apache.org>; Wed, 21 Nov 2012 05:35:50 -0500
Received: from dhcp-29-121.brq.redhat.com (dhcp-29-121.brq.redhat.com
 [10.34.29.121])
	by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id
 qALAZm9e009195
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 21 Nov 2012 05:35:49 -0500
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: MAC address access in vsphere
From: Michal Fojtik <mfojtik@redhat.com>
In-Reply-To: <50ACA08F.1040303@ongame.com>
Date: Wed, 21 Nov 2012 11:36:41 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D65B24F4-2775-4438-8A21-5B57A3C99A78@redhat.com>
References: <50ACA08F.1040303@ongame.com>
To: dev@deltacloud.apache.org
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24
X-Virus-Checked: Checked by ClamAV on apache.org

On Nov 21, 2012, at 10:36 AM, Xavier Naveira <xavier.naveira@ongame.com> =
wrote:

Hi Xavier,

This is actually a very good catch. We do advertise the MAC address =
because in time between
instance guest tools report the IP address to VSPhere we don't know what =
the real IP address is.

How about this:

<public_addresses>
  <address type=3D"mac">3c:97:0e:1b:3b:82</address>
  <address type=3D"ipv4">10.0.0.1</address>
</public_addresses>

I mean we can just keep reporting the MAC address. Also I think we can =
do the same
for RHEV-M and for the OpenStack.

I can't see anything that we could possibly break with this, because it =
is just addition.
But might be I'm wrong :-)

 -- Michal

> Hi,
>=20
> I have a feature suggestion that I think shouldn't be that hard to add =
(assumption that's probably wrong :) )
>=20
> I'm using deltacloud with vsphere. regarding the network addresses it =
seems that only the public addresses field is used.
>=20
> This field is populated with the mac address of the machine when the =
machine is started but doesn't get an ip address from a dhcp server.
>=20
> As soon a dhcp server offers and ip address and the machine accepts it =
the mac address is replaced with the ip address in the public addresses =
field.
>=20
> This is a problem because the macaddress information disappears from =
deltacloud and there is no way to retrieve it once the machine has =
gotten an ip address from dhcp.
>=20
> Would it be possible to add a field/use the private addresses field to =
store the mac address permanently? How is this managed in the other =
drivers?
>=20
> Thank you!
>=20
> Xavier

Michal Fojtik
http://deltacloud.org
mfojtik@redhat.com