Storage is consistent--UTC. Display to user should go through an optional layer
to convert it to an end user-specified local timezone. This is part of
"localization" (l10n) which is the complement to "internationalization" (i18n).
Other examples of localization include number and date formatting.
- Gabriel
> -----Original Message-----
> From: [email protected]
> [mailto:openstack-
> [email protected]] On Behalf Of
> Johannes Erdfelt
> Sent: Wednesday, June 06, 2012 1:51 PM
> To: [email protected]
> Subject: Re: [Openstack] How to let nova use localtime rather than UTC
> time?
>
> On Wed, Jun 06, 2012, Gabriel Hurley <[email protected]> wrote:
> > Stored timestamps should always be in UTC, however efforts should be
> > made to support local timezones as a user-configurable option. Horizon
> > will be working towards this goal since Django has good timezone
> > support, I'd encourage other projects to keep this on their radar as
> > well.
>
> I'm a little confused by your reply. You said it should always be stored in
> UTC,
> but then it should be user-configurable to use local timezones?
>
> JE
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : [email protected]
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
