[openstack-dev] 回复：[goals][python3][karbor] Please process thepython3-first patches
Thanks for pushing these patches, we will review and merge them ASAP. 原始邮件 发件人:Nguyễn Trí Hảinguyentriha...@gmail.com 收件人:OpenStack Development Mailing List (not for usage questions)openstack-dev@lists.openstack.org 抄送:jiaopengjujiaopen...@cmss.chinamobile.com 发送时间:2018年9月21日(周五) 20:36 主题:[openstack-dev][goals][python3][karbor] Please process thepython3-first patches HiKarbor team and Karbor PTL, As part of the "Run under Python 3 by default" community goal [1] for OpenStack in the Stein cycle, I proposed the patches related to python3-first goal very long time ago. However, there is no activity for those patches. Please receive those patches and review them. Those patches belong to: - openstack/karbor - openstack/karbor-dashboard - openstack/python-karborclient Here they are:https://review.openstack.org/#/q/project:%255E.*karbor.*+topic:python3-first+status:open [1]https://governance.openstack.org/tc/goals/stein/python3-first.html -- Nguyen Tri Hai/ Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 回复： [manila] Nominating Zhong Jun (zhongjun) for Manilacore
+1 for zhongjun! 原始邮件 发件人:Goutham" goutham.pachar...@netapp.com 收件人:OpenStack Development Mailing List (not for usage questions)openstack-dev@lists.openstack.org 发送时间:2017年11月20日(周一) 07:29 主题:[openstack-dev] [manila] Nominating Zhong Jun (zhongjun) for Manilacore Hello Manila developers, I would like to nominate Zhong Jun (zhongjun on irc, zhongjun2 on gerrit) to be part of the Manila core team. Zhongjun has been an important member of our community since the Kilo release, and has, in the past few releases made significant contributions to the constellation of projects related to openstack/manila [1]. She is also our ambassador in the APAC region/timezones. Her opinion is valued amongst the core team and I think, as a core reviewer and maintainer, she would continue to help grow and maintain our project. Please respond with a +1/-1. We will not be having an IRC meeting this Thursday (23rd November 2017), so if we have sufficient quorum, PTL extraordinaire, Ben Swartzlander will confirm her nomination here. [1] http://stackalytics.com/?user_id=jun-zhongjunrelease=allmetric=person-day Thanks, Goutham__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [requirements][ec2-api] How about using boto3instead of boto in requirements
Hi, Thanks! I will try to use botocore instead of boto3 to find out whether the code running or not. jiaopengju mail: jiaopen...@cmss.chinamobile.com 原始邮件 发件人:Andrey pavlovandrey...@gmail.com 收件人:OpenStack Development Mailing List (not for usage questions)openstack-dev@lists.openstack.org; andrey.mpandrey...@gmail.com; Alexandre levinealexandrelev...@gmail.com 发送时间:2017年6月20日(周二) 18:25 主题:Re: [openstack-dev] [requirements][ec2-api] How about using boto3instead of boto in requirements Hi, We (ec2-api team) now in the middle of some investigations that should lead us to either to remove boto from the code or to change it to botocore as we decided previously. We'll done with it to the middle of July. Regards, Andrey Pavlov. On Tue, Jun 20, 2017 at 10:15 AM, Tony Breeds t...@bakeyournoodle.com wrote: On Mon, Jun 19, 2017 at 09:33:02PM +0800, jiaopengju wrote: Hi Dims, I got response from core member of ec2-api. What do you think about it? -- Hi, I don't treat adding new library as a problem. - I see that you don't remove boto - so your change doesn't affect ec2-api code. Part of the role of the requirements team is to ensure that we don't end up with several libraries that have significant overlap in functionality. Clearly boto and boto3 fall squarely in that camp. What the requirements team needs is some assurance that switching to boto3 is something that the ec2-api team would be able to do. Running on boto which has been deprecated in favor of boto3 make sense from a lot of levels. We're far enough into the Queens cycle that I doubt it'd happen this cycle :( Yours Tony.__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [requirements] [ec2-api]How about using boto3instead ofboto in requirements
Hi Dims, I got response from core member of ec2-api. What do you think about it? -- Hi, I don't treat adding new library as a problem. - I see that you don't remove boto - so your change doesn't affect ec2-api code. - boto doesn't require botocore and jmespath - right now ec2-api itself doesn't use botocore. botocore is needed only for functional tests of ec2-api. P.S. and I prefer to use botocore cause I know how to use it. I had such change -https://review.openstack.org/#/c/198571/ Regards, Andrey Pavlov. -- 原始邮件 发件人:jiaopengjujiaopen...@cmss.chinamobile.com 收件人:OpenStack Development Mailing List (not for usage questions)openstack-dev@lists.openstack.org 抄送:mthodemth...@mthode.org; seans...@dague.net; alexandrelev...@gmail.com; andrey...@gmail.com; fter...@hotmail.com 发送时间:2017年6月19日(周一) 20:39 主题:Re: [openstack-dev] [requirements] [ec2-api]How about using boto3instead ofboto in requirements Add core members of ec2-api to cc list. Pengju Jiao mail: jiaopen...@cmss.chinamobile.com 原始邮件 发件人:jiaopengjujiaopen...@cmss.chinamobile.com 收件人:OpenStack Development Mailing List (not for usage questions)openstack-dev@lists.openstack.org 抄送:mthodemth...@mthode.org; seans...@dague.net 发送时间:2017年6月19日(周一) 20:33 主题:Re: [openstack-dev] [requirements] [ec2-api]How about using boto3instead ofboto in requirements Thanks, I will try to reach out them in ec2-api channel. Pengju Jiao mail: jiaopen...@cmss.chinamobile.com Hi Pengju Jiao, The main consume i believe is EC2-API : http://codesearch.openstack.org/?q=%5Ebotoi=nopefiles=.*req.*%5C.txtrepos= http://codesearch.openstack.org/?q=%5E(from%7Cimport).*botoi=nopefiles=repos= Can you please reach out to them? Thanks, Dims On Mon, Jun 19, 2017 at 3:11 AM, jiaopengju jiaopen...@cmss.chinamobile.com wrote: Hi, everyone: I have a blueprint of freezer to support s3 storage driver [1], so I need to add boto3 to the requirements [2]. Why use boto3 but not boto? Boto3 [3] is the next version of Boto, is now stable and recommended for general use. It can be used side-by-side with Boto in the same project, so it is easy to start using Boto3 in your existing projects as well as new projects. Going forward, API updates and all new feature work will be focused on Boto3.Problem Boto3 requires botocore, jmespath and s3transfer. botocore and jmespath are already used by boto, this is because boto is used by ec2-api (and heat-cfntools, rally and swift3). After adding Boto3 to requirements, we will have old and new libraries ATM.My suggenstion How about using boto3 instead of boto? This will require us to do some migration about boto to boto3.Anyone has ideas or suggesstions? Thank you very much![1] https://review.openstack.org/#/c/471295 [2]https://review.openstack.org/#/c/473067 [3]https://github.com/boto/boto3 Pengju Jiao mail: jiaopen...@cmss.chinamobile.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Davanum Srinivas :: https://twitter.com/dims __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [requirements] [ec2-api]How about using boto3instead ofboto in requirements
Add core members of ec2-api to cc list. Pengju Jiao mail: jiaopen...@cmss.chinamobile.com 原始邮件 发件人:jiaopengjujiaopen...@cmss.chinamobile.com 收件人:OpenStack Development Mailing List (not for usage questions)openstack-dev@lists.openstack.org 抄送:mthodemth...@mthode.org; seans...@dague.net 发送时间:2017年6月19日(周一) 20:33 主题:Re: [openstack-dev] [requirements] [ec2-api]How about using boto3instead ofboto in requirements Thanks, I will try to reach out them in ec2-api channel. Pengju Jiao mail: jiaopen...@cmss.chinamobile.com Hi Pengju Jiao, The main consume i believe is EC2-API : http://codesearch.openstack.org/?q=%5Ebotoi=nopefiles=.*req.*%5C.txtrepos= http://codesearch.openstack.org/?q=%5E(from%7Cimport).*botoi=nopefiles=repos= Can you please reach out to them? Thanks, Dims On Mon, Jun 19, 2017 at 3:11 AM, jiaopengju jiaopen...@cmss.chinamobile.com wrote: Hi, everyone: I have a blueprint of freezer to support s3 storage driver [1], so I need to add boto3 to the requirements [2]. Why use boto3 but not boto? Boto3 [3] is the next version of Boto, is now stable and recommended for general use. It can be used side-by-side with Boto in the same project, so it is easy to start using Boto3 in your existing projects as well as new projects. Going forward, API updates and all new feature work will be focused on Boto3.Problem Boto3 requires botocore, jmespath and s3transfer. botocore and jmespath are already used by boto, this is because boto is used by ec2-api (and heat-cfntools, rally and swift3). After adding Boto3 to requirements, we will have old and new libraries ATM.My suggenstion How about using boto3 instead of boto? This will require us to do some migration about boto to boto3.Anyone has ideas or suggesstions? Thank you very much![1] https://review.openstack.org/#/c/471295 [2]https://review.openstack.org/#/c/473067 [3]https://github.com/boto/boto3 Pengju Jiao mail: jiaopen...@cmss.chinamobile.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Davanum Srinivas :: https://twitter.com/dims __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [requirements] [ec2-api]How about using boto3 instead ofboto in requirements
Thanks, I will try to reach out them in ec2-api channel. Pengju Jiao mail: jiaopen...@cmss.chinamobile.com Hi Pengju Jiao, The main consume i believe is EC2-API : http://codesearch.openstack.org/?q=%5Ebotoi=nopefiles=.*req.*%5C.txtrepos= http://codesearch.openstack.org/?q=%5E(from%7Cimport).*botoi=nopefiles=repos= Can you please reach out to them? Thanks, Dims On Mon, Jun 19, 2017 at 3:11 AM, jiaopengju jiaopen...@cmss.chinamobile.com wrote: Hi, everyone: I have a blueprint of freezer to support s3 storage driver [1], so I need to add boto3 to the requirements [2]. Why use boto3 but not boto? Boto3 [3] is the next version of Boto, is now stable and recommended for general use. It can be used side-by-side with Boto in the same project, so it is easy to start using Boto3 in your existing projects as well as new projects. Going forward, API updates and all new feature work will be focused on Boto3.Problem Boto3 requires botocore, jmespath and s3transfer. botocore and jmespath are already used by boto, this is because boto is used by ec2-api (and heat-cfntools, rally and swift3). After adding Boto3 to requirements, we will have old and new libraries ATM.My suggenstion How about using boto3 instead of boto? This will require us to do some migration about boto to boto3.Anyone has ideas or suggesstions? Thank you very much![1] https://review.openstack.org/#/c/471295 [2]https://review.openstack.org/#/c/473067 [3]https://github.com/boto/boto3 Pengju Jiao mail: jiaopen...@cmss.chinamobile.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Davanum Srinivas :: https://twitter.com/dims __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [requirements] How about using boto3 instead of boto in requirements
Hi, everyone: I have a blueprint of freezer to support s3 storage driver [1], so I need to add boto3 to the requirements [2]. Why use boto3 but not boto? Boto3 [3] isthe next version of Boto, is now stable and recommended for general use. It can be used side-by-side with Boto in the same project, so it is easy to start using Boto3 in your existing projects as well as new projects. Going forward, API updates and all new feature work will be focused on Boto3. Problem Boto3 requires botocore, jmespath and s3transfer. botocore and jmespath are already used by boto, this is because boto is used by ec2-api (and heat-cfntools, rally and swift3). After adding Boto3 to requirements, we will have old and new libraries ATM. My suggenstion How about using boto3 instead of boto? This will require us to do some migration about boto to boto3. Anyone has ideas or suggesstions? Thank you very much! [1]https://review.openstack.org/#/c/471295 [2]https://review.openstack.org/#/c/473067 [3]https://github.com/boto/boto3 Pengju Jiao mail:jiaopen...@cmss.chinamobile.com__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] How about using boto3 instead of boto in requirements
Hi, everyone: I have a blueprint of freezer to support s3 storage driver [1], so I need to add boto3 to the requirements [2]. Why use boto3 but not boto? Boto3 [3] isthe next version of Boto, is now stable and recommended for general use. It can be used side-by-side with Boto in the same project, so it is easy to start using Boto3 in your existing projects as well as new projects. Going forward, API updates and all new feature work will be focused on Boto3. Problem Boto3 requires botocore, jmespath and s3transfer. botocore and jmespath are already used by boto, this is because boto is used by ec2-api (and heat-cfntools, rally and swift3). After adding Boto3 to requirements, we will have old and new libraries ATM. My suggenstion How about using boto3 instead of boto? This will require us to do some migration about boto to boto3. Anyone has ideas or suggesstions? Thank you very much! [1]https://review.openstack.org/#/c/471295 [2]https://review.openstack.org/#/c/473067 [3]https://github.com/boto/boto3 Pengju Jiao mail: jiaopen...@cmss.chinamobile.com__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
