Unset fields of API objects have None values instead of wsme.types.Unset

[Vladyslav Drok]

In API objects constructors, e.g. in Node, fields initialization is done this way:

for k in fields:
    # Skip fields we do not expose.
    if not hasattr(self, k):
        continue
    self.fields.append(k)
    setattr(self, k, kwargs.get(k))

So, the field is set to None if it is passed to __init__ as None and if it is not passed at all.
If it's not passed at all it's better to use wsme.types.Unset instead of None, as it is its purpose:

setattr(self, k, kwargs.get(k, wsme.types.Unset))

so that these two cases can be distinguished.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/131139

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/131139
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=645072bfa3da8c63b6e469021db334b8d7586416
Submitter: Jenkins
Branch: master

commit 645072bfa3da8c63b6e469021db334b8d7586416
Author: Vladyslav Drok <email address hidden>
Date: Mon Oct 27 15:09:45 2014 +0200

    Use wsme.Unset as default value for API objects

    wsme.Unset should be used instead of None as default value for API
    objects as None is valid value that could be passed to constructor.

    Closes-bug: #1385247
    Change-Id: I94f6dd14a7befe217552cf2c6998bb1c1d2d338d