[openstack-dev] [oslo] question about oslo_utils and oslo_versonedobjects

2017-03-06 Thread zengchen
Hi, guys: I find a non-coincidence definition in Oslo, oslo_utils.timeutils.utcnow is defined like this: def utcnow(with_timezone=False): oslo_versonedobjects.fields.DateTimeField is defined like this class DateTimeField(AutoTypedField): def __init__(self, tzinfo_aware=T

Re: [openstack-dev] [oslo] question about oslo_utils and oslo_versonedobjects

2017-03-08 Thread zengchen
Hi, jayThanks for your reply. Do you means it is no need to do that optimization?In my opinion, It is better if do some change. Thanks again. Best Wishes zeng chen At 2017-03-08 00:57:51, "Jay Pipes" wrote: >On 03/07/2017 01:34 AM, zengchen wrote: >> Hi, guys: &

Re: [openstack-dev] [oslo] question about oslo_utils and oslo_versonedobjects

2017-03-08 Thread zengchen
of easy of use. Certainly, I can change the codes as you described. Really appreciate your reply. Best Wishes! zeng chen At 2017-03-09 10:43:23, "Jay Pipes" wrote: >On 03/08/2017 09:07 PM, zengchen wrote: >> Hi, jay >> Thanks for your reply. Do you means it is no nee

Re: [openstack-dev] [oslo] question about oslo_utils and oslo_versonedobjects

2017-03-09 Thread zengchen
Hi jay: Understand you. It is a good method! I will try to update my codes. Really appreciate your reply. Thanks! Best Wishes! zeng chen At 2017-03-10 02:52:55, "Jay Pipes" wrote: >On 03/09/2017 01:37 AM, zengchen wrote: >> I'm contr

Re: [openstack-dev] [fuxi][stackube][kuryr] IRC meeting

2017-05-23 Thread zengchen
? best wishes! zengchen At 2017-05-22 23:37:29, "Hongbin Lu" wrote: Hi all, We will have an IRC meeting at UTC 1400-1500 Tuesday (2017-05-23). At the meeting, we will discuss the k8s storage integration with OpenStack. This effort might cross more than one teams (i.e. kuryr an

[openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang

2017-05-25 Thread zengchen
Hi guys: hongbin had committed a bp of rewriting Fuxi with go language[1]. My question is where to commit codes for it. We have two choice, 1. create a new repository, 2. create a new branch. IMO, the first one is much better. Because there are many differences in the layer of infrastructure

Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang

2017-05-25 Thread zengchen
Very sorry to foget attaching the link for bp of rewriting Fuxi with go language. https://blueprints.launchpad.net/fuxi/+spec/convert-to-golang At 2017-05-25 19:46:54, "zengchen" wrote: Hi guys: hongbin had committed a bp of rewriting Fuxi with go language[1]. My question i

Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang

2017-05-25 Thread zengchen
codes in the new Fuxi-golang? Besides, IMO, It is better to create a repository for Fuxi-golang, because Fuxi is the project of Openstack, Thanks very much! Best Wishes! zengchen At 2017-05-25 22:47:29, "John Griffith" wrote: On Thu, May 25, 2017 at 5:50 AM, zengchen wr

Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang

2017-05-27 Thread zengchen
Hi John & Ben: I have committed a patch[1] to add a new repository to Openstack. Please take a look at it. Thanks very much! [1]: https://review.openstack.org/#/c/468635 Best Wishes! zengchen 在 2017-05-26 21:30:48,"John Griffith" 写道: On Thu, May 25, 2017 at 10:0

Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang

2017-05-31 Thread zengchen
ut your work on integrating Manila? Thanks very much! Best Wishes! zengchen . [1] http://git.openstack.org/cgit/openstack/magnum/tree/magnum/drivers/common/templates/swarm/fragments/volume-service.sh?h=stable/ocata At 2017-05-30 19:47:26, "Spyros Trigazis" wrote: FYI, there is alrea

Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang

2017-06-05 Thread zengchen
://review.openstack.org/#/c/470111/ Best Wishes zengchen At 2017-05-31 23:55:15, "Hongbin Lu" wrote: Please find my replies inline. Best regards, Hongbin From: Spyros Trigazis [mailto:strig...@gmail.com] Sent: May-30-17 9:56 AM To: OpenStack Development Mailing List (not

[openstack-dev] [heat] A question on creating Manila Share

2016-12-08 Thread zengchen
['ip', 'domain'])], required=True ), However, I see manila has defined different allowed value for 'ACCESS_TYPE', which includes 'ip', 'user', 'cert', 'cephx'. So, my que

Re: [openstack-dev] [heat] A question on creating Manila Share

2016-12-12 Thread zengchen
Rabi Mishra & Rico Lin: Thanks very much for your reply! I have submitted a bug report at https://bugs.launchpad.net/heat/+bug/1649217, and will submit a patch to fix it later. cheers zengchen 在 2016-12-09 12:45:01,"Rabi Mishra" 写道: Hi zengchen, Yeah, the co

[openstack-dev] [heat] A question on the endpoint of Heat

2016-12-19 Thread zengchen
Hi, Heat stackers: May I ask a question about the endpoint of Heat. I see the endpoints of Heat registered to Keystone look like this. 'http://10.229.45.150:8004/v1/$(project_id)s' . My question is that why use '$' instead of '%' as the replacement symbol. Is there some kind of rule? cheer

Re: [openstack-dev] [heat] A question on the endpoint of Heat

2016-12-20 Thread zengchen
/keystone/catalog/backends/templated.py#L68 cheers zengchen At 2016-12-20 22:22:17, "Zane Bitter" wrote: >On 20/12/16 02:29, zengchen wrote: >> Hi, Heat stackers: >> May I ask a question about the endpoint of Heat. I see the endpoints >> of Heat regist

[openstack-dev] [Karbor] Questions about algorithm of building resource graph

2016-10-10 Thread zengchen
Hi karbor guys: I have some questions about algorithm of building resource graph. I have described them in the attached file. Any thoughts will be welcomed. Thanks very much! zengchen Questions about algorithm of building resource graph.pptx Description: MS-Powerpoint 2007 presentation

Re: [openstack-dev] [Karbor] Questions about algorithm of building resource graph

2016-10-12 Thread zengchen
from you. Please, take a look at it. Thanks very much! zengchen At 2016-10-11 09:06:33, "zengchen" wrote: Hi karbor guys: I have some questions about algorithm of building resource graph. I have described them in the attached file. Any thoughts will be welcomed. Thanks