[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Pulp-list] Date and Time Feedback Requested!



On 04/15/2011 11:36 AM, Jason L Connor wrote:
> Hi Everyone,
> 
> I'm personally struggling with date and time formats and timezone data
> in pulp.
> 
> We're currently using 2 different formats, 1 for specifying date and
> time information and 1 for reporting date and time information. I'd like
> to see us unify this, and I'm looking for feedback on what is
> easiest/most desired.
> 
> For reporting, we're generally using a timestamp as seconds since the
> epoch as a float in the utc timezone.
> 
> For specifying date time data, we're accepting objects with the
> following integer fields: (year, month, day, hour, minute) in the local
> timezone of the pulp server.
> 
> 
> This is obviously confusing... (especially because some of the reporting
> is using the second format, like for repo schedules)
> 
> 
> Here's what I'd like to propose:
> 
> The date/time format is always an object, with the fields(year, month,
> day, hour, minute, second)
> Please note that pulp will not honor the 'second' field when specify
> times, it's only use is in reporting.
> 
> The times are always specified in the timezone local to the pulp server.
> 
> This keeps the logic on pulp as simple as possible. As well as providing
> both a machine parsable and human readable format for date/time data.
> 
> Ok, fire away...
> 

Personally that sounds much nicer, but obviously for those of us making
use of this we'll have to make some changes on our side.  Will the
object contain time zone data or are we basing this off UTC as well?

-- 
Jason E. Rist
Senior Software Engineer
Systems Management and Cloud Enablement
Red Hat, Inc.
+1.919.754.4048
Freenode: jrist


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]