yahoo-eng-team team mailing list archive

[OpenStack Infra <1561200@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/368682
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=424a633fd985ad517a06dee1aeec805702d2e576
Submitter: Jenkins
Branch:    master

commit 424a633fd985ad517a06dee1aeec805702d2e576
Author: Kevin Benton <kevin@xxxxxxxxxx>
Date:   Fri Sep 9 06:20:40 2016 -0700

    Include timezone in timestamp fields
    
    The Neutron 'created_at'/'updated_at' fields on API resources
    were inconsistent with other OpenStack projects because we did
    not include timezone information. This patch addressed that
    problem by adding the zulu time indicator onto the end of the
    fields.
    
    Because this could break clients expecting no timezone, this patch
    also eliminates the 'timestamp_core' and 'timestamp_ext' extensions
    and consolidates them into a new 'timestamp' extension. This makes
    the change discoverable via the API.
    
    This is assuming the current API development paradigm where
    extensions can come and go depending on the deployment and the client
    is expected to handle this by checking the loaded extensions.
    Once we decide extensions are permanent, this type of change will
    no longer be possible.
    
    Even though this is being proposed late in the cycle, it is better
    to get this change in before the release where we expose even more
    resources with incorrectly formatted timestamps.
    
    APIImpact
    Closes-Bug: #1561200
    Change-Id: I2ee2ed4c713d88345adc55b022feb95653eec663


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1561200

Title:
  created_at and updated_at times don't include timezone

Status in neutron:
  Fix Released

Bug description:
  created_at and updated_at were recently added to the API calls and
  notifications for many neutron resources (networks, subnets, ports,
  possibly more), which is awesome! I've noticed that the times don't
  include a timezone (compare to nova servers and glance images, for
  instance).

  Even if there's an assumption a user can make, this can create
  problems with some display tools (I noticed this because a javascript
  date formatting filter does local timezone conversions when a timezone
  is created, which meant times for resources created seconds apart
  looked as though they were several hours adrift.

  Tested on neutron mitaka RC1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1561200/+subscriptions