Re: [openstack-dev] [tacker] Tacker PTL Non-candidacy
Hi Sridhar, Thanks for your leadership in Tacker for last two years!! Great years for the project. I am glad that you will be continuing contributing to the project. I look forward to work with you for further collaboration between Tacker and TOSCA translator projects. Regards, Sahdev Zala From: Sridhar Ramaswamy To: "OpenStack Development Mailing List (not for usage questions)" Date: 01/18/2017 06:11 PM Subject:[openstack-dev] [tacker] Tacker PTL Non-candidacy As I announced in the last Tacker weekly meeting, I'm not planning to run for Pike PTL position. Having served in this role for the last three cycles (including for the periods before it was a big-tent project), I think it is time for someone else to step in and take this forward. I'll continue to contribute as a core-team member. I'll be available to help the new PTL in any ways needed. Personally, it has been a such a rewarding experience. I would like to thank all the contributors - cores and non-core members - who supported this project and me. We had an incredible amount of cross-project collaboration in tacker, with the likes of tosca-parser / heat-translator, neutron networking-sfc, senlin, and mistral - my sincere thanks to all the PTLs and the members of those projects. Now going forward, we have tons to do in Tacker - towards making it a leading, community built TOSCA Orchestrator service. And that, not just for the current focus area of NFV but also expand into Enterprise and Container use-cases. Fun times! thanks, Sridhar irc: sridhar_ram __ 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] [tosca-parser] [heat-translator] [heat] [tacker] [opnfv] heat-translator and tosca-parser 0.7.0
Hello Everyone, On behalf of the Heat Translator and TOSCA Parser team, I am pleased to announce the 0.7.0 PyPI release of heat-translator and tosca-parser which can be downloaded fromhttps://pypi.python.org/pypi/heat-translator and https://pypi.python.org/pypi/tosca-parser respectively. This release includes following enhancements, heat-translator: - new APIs to produce and access multiple translated templates - translation support for Heat SoftwareDeploymentGroup resource - new test templates - bug fixes - doc updates tosca-parser: - support for parsing TOSCA qualified names - TOSCA substitution_mappings parsing and validation - support for get_operation_output function - support for custom interfaces - enhanced template validation - bug fixes - doc updates Thanks!! Regards, Sahdev Zala __ 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] [heat-translator][tosca-parser] No Weekly IRC meeting this week on Nov 24 - US holiday
Hello Team, A gentle reminder, as we discussed in the meeting last week, there will be no weekly meeting this week on Thursday Nov 24th due to Thanksgiving holiday in USA. Regards, Sahdev Zala __ 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] [tosca-parser] [heat-translator] cross-project design session with [Tacker] at summit
Qiming, hi, I meant to say Friday Oct 28th (October for Ocata :)) Thanks for noticing it. Absolutely, I have added it to the agenda and I will cover it. Totally understand the overlapping of various sessions. In the Heat Translator we have recently added support for translation to Senlin resources and we had some discussion on scaling with Tacker team couple weeks back, something which is already part of discussion at the summit. Thanks! Regards, Sahdev Zala From: Qiming Teng To: "OpenStack Development Mailing List (not for usage questions)" Date: 10/18/2016 02:44 AM Subject:Re: [openstack-dev] [tosca-parser] [heat-translator] cross-project design session with [Tacker] at summit You meant Nov 28th, right? Also, I'd like to join the discussion because Senlin can help offload the clustering, auto-scaling and auto-healing work from Tacker so Tacker can be more focused on the NFV support. However, the schedule for design summit was ... very packed. There are many sessions I'll have to miss. For this one, could you please help bring up this topic? TOSCA-parser was a blocking factor for Tacker to use Senlin directly. We will need some helps from your team. Thanks. Regards, Qiming On Mon, Oct 17, 2016 at 11:58:42AM -0400, Sahdev P Zala wrote: > Hi team, > > The TOSCA-Parser/Heat-Translator and Tacker will be having a cross-project > design session at the Barcelona summit. Sripriya has started etherpad doc > to collect discussion items. If you have any, please add it there. > > Friday, Nov 18th, 11:00am - 11:40am - Workroom Session > Location: CCIB - Centre de Convencions Internacional de Barcelona - P1 - > Room 128 > > https://etherpad.openstack.org/p/tacker-ocata-summit > > > Safe travels. See you there! > > Regards, > Sahdev Zala > __ 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] [tosca-parser] [heat-translator] cross-project design session with [Tacker] at summit
Hi team, The TOSCA-Parser/Heat-Translator and Tacker will be having a cross-project design session at the Barcelona summit. Sripriya has started etherpad doc to collect discussion items. If you have any, please add it there. Friday, Nov 18th, 11:00am - 11:40am - Workroom Session Location: CCIB - Centre de Convencions Internacional de Barcelona - P1 - Room 128 https://etherpad.openstack.org/p/tacker-ocata-summit Safe travels. See you there! Regards, Sahdev Zala __ 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] [tosca-parser] [heat-translator] [heat] [tacker] [opnfv] Heat-Translator 0.6.0 release
Hello Everyone, On behalf of the Heat Translator team, I am pleased to announce the 0.6.0 PyPI release of heat-translator which can be downloaded from https://pypi.python.org/pypi/heat-translator This release includes several enhancements: Python 3.5 support Auto deployment of translated templates with proper authentication with Keystone and using Heat client to create stack. Also Nova and Glance clients, instead of direct REST calls, are now used to query available flavors and images in the user environment. This was a needed update on initial deployment support where OS_* environment variables were used to determine deployment instead of Keystone auth. Translation support for Senlin cluster and auto scaling policy resources Translation support for AutoScalingGroup, ScalingPolicy and Aodh resources Support for TOSCA get_operation_output and concat function translation New CLI option to provide a desired stack name when auto deploy translated template Handling of Ansible roles used with TOSCA artifacts Refactoring of shell program to use argparse Requirement updates Documentation update and bug fixes etc. Thanks! Regards, Sahdev Zala __ 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] [heat-translator] [tosca-parser] Reminder = no IRC meeting this week
Hello team, FYI, as we discussed in our last meeting, there will be no meeting today Thursday August 25th as I am travelling. Please take any discussion on IRC or via emails. Thanks! Regards, Sahdev Zala __ 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] [tosca-parser] [heat-translator] [heat] [tacker] [opnfv] TOSCA-Parser 0.6.0 release
Hello Everyone, On behalf of the TOSCA-Parser team, I am pleased to announce the 0.6.0 PyPI release of tosca-parser which can be downloaded from https://pypi.python.org/pypi/tosca-parser This release includes following enhancements: Python 3.5 support Support for TOSCA Repository which is an external repository in TOSCA service template containing deployment and implementation artifacts Implementation of triggers in policies Support for Credential data type Support for Token function get_attribute function support for optional requirement or capability Refactoring of TOSCA definition file for easy reuse Added new exception UnsupportedType to handle TOSCA types that are not supported in parser at any given time New test template for Container node type NFV definition updates for NFV.CP and NFV.VNFFG Moved to use urllib2 from urllib to use with input templates specified via URL Requirements updates Small bug fixes Thanks! Regards, Sahdev Zala __ 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] [heat-translator] [tosca-parser] No weekly IRC meeting this week - July 28th
Hello team, As we talked in our last meeting, there will be no meeting this Thursday July 28th due to no strong agenda and my unavailability this week. Please take any discussion on IRC or via emails. Thanks! Regards, Sahdev Zala __ 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] New core reviewers nomination for TOSCA-Parser and or Heat-Translator project [tosca-parser][heat-translator][heat]
Thanks core team for your +1 vote. Welcome new core - Bob, Miguel, Bharath and Mathiue. Thanks again for your great contribution!! Regards, Sahdev Zala From: Sahdev P Zala/Durham/IBM@IBMUS To: "OpenStack Development Mailing List \(not for usage questions\)" Date: 05/31/2016 09:30 AM Subject:[openstack-dev] New core reviewers nomination for TOSCA-Parser and or Heat-Translator project [tosca-parser][heat-translator][heat] Hello TOSCA-Parser and Heat-Translator core team, I would like to nominate following current active contributors to the tosca-parser and or heat-translator project as core reviewers to speed up the development. They are contributing for more than six months and has remained one of the top five contributors for a mentioned project(s). Please reply to this thread or email me with your vote (+1 or -1) by EOD June 4th. [1] Bob Haddleton: Bob is a lead developer for the TOSCA NFV specific parsing and translation in the tosca-parser and heat-translator projects respectively. Bob actively participates in IRC meetings and other discussion via emails or IRC. He is a also a core reviewer in OpenStack Tacker project. I would like to nominate him for core reviewer position for both tosca-parser and heat-translator. [2] Miguel Caballar: Miguel is familiar with TOSCA for long time. He is an asset for the tosca-parser project and has been bringing lot of new use cases to the project. He is a second lead developer overall for the project at present. I would like to nominate him for core reviewer position in tosca-parser. [3] Bharath Thiruveedula: Bharath is actively contributing to the heat-translator project. He knows project well and has implemented important blueprints during the Mitaka cycle including enhancement to the OSC plugin, automatic deployment of translated templates and dynamic querying of flavors and images. Bharath actively participates in IRC meetings and other discussion via emails or IRC. I would like to nominate him for the core reviewer position in heat-translator. [4] Mathieu Velten: Mathieu is familiar with TOSCA for long time as well. He is brining new use cases regularly and actively working on enhancing the heat-translator project with needed implementation. He also uses the translated templates with real time deployment with Heat for his work on project Indigo DataCloud [5]. He knows project well and was the second lead developer for the project during the Mitaka cycle. I would like to nominate him for the core reviewer position in heat-translator. [1] http://stackalytics.com/?release=all&module=tosca-parser&metric=commits&user_id=bob-haddleton and http://stackalytics.com/?release=all&module=heat-translator&metric=commits&user_id=bob-haddleton [2] http://stackalytics.com/?release=all&module=tosca-parser&metric=commits&user_id=micafer1 [3] http://stackalytics.com/?release=all&module=heat-translator&metric=commits&user_id=bharath-ves [4] http://stackalytics.com/?release=all&metric=commits&module=heat-translator&user_id=matmaul [5] https://www.indigo-datacloud.eu/ Thanks! Regards, Sahdev Zala RTP, NC __ 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] New core reviewers nomination for TOSCA-Parser and or Heat-Translator project [tosca-parser][heat-translator][heat]
Hello TOSCA-Parser and Heat-Translator core team, I would like to nominate following current active contributors to the tosca-parser and or heat-translator project as core reviewers to speed up the development. They are contributing for more than six months and has remained one of the top five contributors for a mentioned project(s). Please reply to this thread or email me with your vote (+1 or -1) by EOD June 4th. [1] Bob Haddleton: Bob is a lead developer for the TOSCA NFV specific parsing and translation in the tosca-parser and heat-translator projects respectively. Bob actively participates in IRC meetings and other discussion via emails or IRC. He is a also a core reviewer in OpenStack Tacker project. I would like to nominate him for core reviewer position for both tosca-parser and heat-translator. [2] Miguel Caballar: Miguel is familiar with TOSCA for long time. He is an asset for the tosca-parser project and has been bringing lot of new use cases to the project. He is a second lead developer overall for the project at present. I would like to nominate him for core reviewer position in tosca-parser. [3] Bharath Thiruveedula: Bharath is actively contributing to the heat-translator project. He knows project well and has implemented important blueprints during the Mitaka cycle including enhancement to the OSC plugin, automatic deployment of translated templates and dynamic querying of flavors and images. Bharath actively participates in IRC meetings and other discussion via emails or IRC. I would like to nominate him for the core reviewer position in heat-translator. [4] Mathieu Velten: Mathieu is familiar with TOSCA for long time as well. He is brining new use cases regularly and actively working on enhancing the heat-translator project with needed implementation. He also uses the translated templates with real time deployment with Heat for his work on project Indigo DataCloud [5]. He knows project well and was the second lead developer for the project during the Mitaka cycle. I would like to nominate him for the core reviewer position in heat-translator. [1] http://stackalytics.com/?release=all&module=tosca-parser&metric=commits&user_id=bob-haddleton and http://stackalytics.com/?release=all&module=heat-translator&metric=commits&user_id=bob-haddleton [2] http://stackalytics.com/?release=all&module=tosca-parser&metric=commits&user_id=micafer1 [3] http://stackalytics.com/?release=all&module=heat-translator&metric=commits&user_id=bharath-ves [4] http://stackalytics.com/?release=all&metric=commits&module=heat-translator&user_id=matmaul [5] https://www.indigo-datacloud.eu/ Thanks! Regards, Sahdev Zala RTP, NC __ 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] [tosca-parser] [heat-translator] [heat] [tacker] [opnfv] TOSCA-Parser and Heat-Translator 0.5.0 release
Hello Everyone, On behalf of the TOSCA-Parser and Heat-Translator team, I am pleased to announce the 0.5.0 PyPI release of tosca-parser and heat-translator which can be downloaded from https://pypi.python.org/pypi/tosca-parser and https://pypi.python.org/pypi/heat-translator respectively. These releases includes following enhancements: TOSCA-Parser 0.5.0: • Support for LoadBalancer node parsing • Support of parsing triggers in policies • Implementation of PortSpec datatype • Support for range data type • Support for concat function • Support for SOURCE and TARGET in get_property and get_attribute function • Bug fixes • Doc update Heat-Translator 0.5.0: • Dynamic image querying with Glance for TOSCA operating system constraints • New CLI option to automatically deploy translated template with Heat • Translation support for Ansible and Puppet scripts • Update to use latest tosca-parser release 0.5.0 • Bug fixes • Doc update Please let me know if you have any questions or comments. Thanks! Regards, Sahdev Zala __ 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] [tosca-parser] [heat-translator] Collaboration with [Tacker] project at the Austin Summit
Hi Howard, Yes, absolutely. See you in few days! Regards, Sahdev Zala From: Zhipeng Huang To: "OpenStack Development Mailing List (not for usage questions)" Date: 04/19/2016 07:51 PM Subject:Re: [openstack-dev] [tosca-parser] [heat-translator] Collaboration with [Tacker] project at the Austin Summit Hi Sahdev, Could parser team also be part of the joint session ? On Tue, Apr 19, 2016 at 9:55 PM, Sahdev P Zala wrote: Hi Team, We will be having a collaborative session with Tacker project at the summit. The following Tacker working session will be focused on it, Tacker Developer Track: April 28, 2016 : 3:10 - 3:50pm / MR 415A: Working Session If you are at the summit, please join. Safe travels. See you in Austin! Regards, Sahdev Zala __ 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 -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Prooduct Line Huawei Technologies Co,. Ltd Email: huangzhip...@huawei.com Office: Huawei Industrial Base, Longgang, Shenzhen (Previous) Research Assistant Mobile Ad-Hoc Network Lab, Calit2 University of California, Irvine Email: zhipe...@uci.edu Office: Calit2 Building Room 2402 OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado __ 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] [tosca-parser] [heat-translator] Collaboration with [Tacker] project at the Austin Summit
Hi Team, We will be having a collaborative session with Tacker project at the summit. The following Tacker working session will be focused on it, Tacker Developer Track: April 28, 2016 : 3:10 - 3:50pm / MR 415A: Working Session If you are at the summit, please join. Safe travels. See you in Austin! Regards, Sahdev Zala __ 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] [tosca-parser] [heat-translator] No weekly meeting on April 21 and 28
Hello Team, Considering OpenStack Austin Summit and preparation, there will be no IRC weekly meetings for next two weeks for the tosca-parser and heat-translator projects. Safe travels. See you in Austin! Thanks! Regards, Sahdev Zala __ 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] [tosca-parser] [heat-translator] [heat] [tacker] Heat-Translator 0.4.0 PyPI release
Hello Everyone, On behalf of the Heat-Translator team, I am pleased to announce the 0.4.0 PyPI release of heat-translator which can be downloaded from https://pypi.python.org/pypi/heat-translator This release includes following enhancements: ▪ Uses latest tosca-parser 0.4.0 release ▪ Introduced support for TOSCA Policy translation ▪ Introduced support for TOSCA NFV translation ▪ New test suite for OpenStackClient (OSC) plug-in ▪ Allows user to provide parameters at the deployment time by using Heat get_param function ▪ Dynamic handling of Nova server specific key_name property which is not part of TOSCA template, and TOSCA Compute specific capabilities properties for constraints based selection of flavor and image ▪ Enhanced interfaces translation with support for get_artifact function ▪ Bug fixes ▪ Doc updates Thanks! Regards, Sahdev Zala PTL, Heat-Translator __ 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] [tacker][tacker] TOSCA-Parser 0.4.0 PyPI release
:) Hi Sridhar, You are welcome and absolutely. Looking forward for a continuous collaboration and enhanced NFV support in parser as we go forward. Thanks! Regards, Sahdev Zala From: Sridhar Ramaswamy To: "OpenStack Development Mailing List (not for usage questions)" Date: 02/04/2016 03:04 PM Subject:Re: [openstack-dev] [tacker][tacker] TOSCA-Parser 0.4.0 PyPI release Thanks for the note Sahdev. Appreciate your support in getting in TOSCA NFV Profile quickly in time for our Mitaka plans. This is awesome collaboration between tacker and heat-translator projects. Lets keep this going! - Sridhar PS: fixed the subject :) On Wed, Feb 3, 2016 at 6:08 PM, Sahdev P Zala wrote: Hello Tacker team, Sorry I forgot to include the project name in the subject of the following original email, so FYI. Thanks! Regards, Sahdev Zala - Forwarded by Sahdev P Zala/Durham/IBM on 02/03/2016 09:03 PM - From: Sahdev P Zala/Durham/IBM@IBMUS To:"OpenStack Development Mailing List (not for usage questions)" Date:02/03/2016 08:16 PM Subject:[openstack-dev] [tosca-parser] [heat-translator] [heat] TOSCA-Parser 0.4.0 PyPI release Hello Everyone, On behalf of the TOSCA-Parser team, I am pleased to announce the 0.4.0 PyPI release of tosca-parser which can be downloaded from https://pypi.python.org/pypi/tosca-parser This release includes following enhancements: 1) Initial support for TOSCA Simple Profile for Network Functions Virtualization (NFV) v1.0 2) Support for TOSCA Groups and Group Type 3) Initial support for TOSCA Policy and Policy Types 4) Support for TOSCA Namespaces 5) Many bug fixes and minor enhancements including: -Fix for proper inheritance among types and custom relationships based on it -Updated min and max length with map -New get_property function for HOST properties similar to get_attribute function -Updated datatype_definition -Support for nested properties -Fix for incorrect inheritance in properties of capabilities -High level validation of imported template types -Six compatibility for urllib -Test updates -Documentation updates Please let me know if you have any questions or comments. Thanks! Regards, Sahdev Zala PTL, Tosca-Parser __ 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 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] [tacker] TOSCA-Parser 0.4.0 PyPI release
Hello Tacker team, Sorry I forgot to include the project name in the subject of the following original email, so FYI. Thanks! Regards, Sahdev Zala - Forwarded by Sahdev P Zala/Durham/IBM on 02/03/2016 09:03 PM - From: Sahdev P Zala/Durham/IBM@IBMUS To: "OpenStack Development Mailing List (not for usage questions)" Date: 02/03/2016 08:16 PM Subject:[openstack-dev] [tosca-parser] [heat-translator] [heat] TOSCA-Parser 0.4.0 PyPI release Hello Everyone, On behalf of the TOSCA-Parser team, I am pleased to announce the 0.4.0 PyPI release of tosca-parser which can be downloaded from https://pypi.python.org/pypi/tosca-parser This release includes following enhancements: 1) Initial support for TOSCA Simple Profile for Network Functions Virtualization (NFV) v1.0 2) Support for TOSCA Groups and Group Type 3) Initial support for TOSCA Policy and Policy Types 4) Support for TOSCA Namespaces 5) Many bug fixes and minor enhancements including: -Fix for proper inheritance among types and custom relationships based on it -Updated min and max length with map -New get_property function for HOST properties similar to get_attribute function -Updated datatype_definition -Support for nested properties -Fix for incorrect inheritance in properties of capabilities -High level validation of imported template types -Six compatibility for urllib -Test updates -Documentation updates Please let me know if you have any questions or comments. Thanks! Regards, Sahdev Zala PTL, Tosca-Parser __ 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] [tosca-parser] [heat-translator] [heat] TOSCA-Parser 0.4.0 PyPI release
Hello Everyone, On behalf of the TOSCA-Parser team, I am pleased to announce the 0.4.0 PyPI release of tosca-parser which can be downloaded from https://pypi.python.org/pypi/tosca-parser This release includes following enhancements: 1) Initial support for TOSCA Simple Profile for Network Functions Virtualization (NFV) v1.0 2) Support for TOSCA Groups and Group Type 3) Initial support for TOSCA Policy and Policy Types 4) Support for TOSCA Namespaces 5) Many bug fixes and minor enhancements including: -Fix for proper inheritance among types and custom relationships based on it -Updated min and max length with map -New get_property function for HOST properties similar to get_attribute function -Updated datatype_definition -Support for nested properties -Fix for incorrect inheritance in properties of capabilities -High level validation of imported template types -Six compatibility for urllib -Test updates -Documentation updates Please let me know if you have any questions or comments. Thanks! Regards, Sahdev Zala PTL, Tosca-Parser __ 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] [heat-translator][tacker] Openstack Artifact Repository
Hi Bruce, This is interesting and I would like to join the discussion at the summit. Regards, Sahdev Zala From: "Bruce Thompson (brucet)" To: "openstack-dev@lists.openstack.org" Date: 02/01/2016 10:53 AM Subject:[openstack-dev] [heat-translator][tacker] Openstack Artifact Repository During the mid cycle meeting there was a discussion on the Tacker repository and a potential replacement using the OpenStack artifact repository. Here is a link to a description of the OpenStack Artifact Repository: https://specs.openstack.org/openstack/glance-specs/specs/kilo/artifact-repository.html It may be worthwhile to have a discussion with the team working on this project at the next Summit in Austin. Bruce T __ 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] [app-catalog] Add TOSCA assets to the catalog
Great. Thank you so much Kevin and Steve!! I will try defining schema for TOSCA and update it for the review. Regards, Sahdev Zala From: "Fox, Kevin M" To: "OpenStack Development Mailing List (not for usage questions)" Date: 01/27/2016 05:26 PM Subject:Re: [openstack-dev] Add TOSCA assets to the catalog Our schema file is located here: http://git.openstack.org/cgit/openstack/app-catalog/tree/openstack_catalog/web/static/assets.schema.yaml We don't have a schema type defined for TOSCA assets yet. We should discuss the sorts of things that need to be listed so that the asset can be loaded into an OpenStack instance. For example, glance needs architecture, minimum requirements, container type information, etc in addition to the file. When the horizon plugin installs/runs it, we need to pass all the information along. Also, it would be helpful to discuss the mechanism for launching the assets if there is such a thing. Thanks, Kevin From: Steve Gordon [sgor...@redhat.com] Sent: Wednesday, January 27, 2016 1:07 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [app-catalog] Add TOSCA assets to the catalog - Original Message ----- > From: "Sahdev P Zala" > To: "OpenStack Development Mailing List (not for usage questions)" > > Hello, > > I am looking at this blueprint > https://blueprints.launchpad.net/app-catalog/+spec/add-tosca-assets and > confused about the first task, "define metadata for TOSCA assets"? Can > someone please provide example of metadata for previous work on Heat and > Murano? I tried to find some old patch for reference but couldn't get one. > > > The TOSCA will provide YAML template file and package in a CSAR form > (.csar and .zip) to host on catalog. > > > Thanks! > > Regards, > Sahdev Zala I *believe* it's referring to the metadata for the asset type, if you look in the schema here: http://git.openstack.org/cgit/openstack/app-catalog/tree/openstack_catalog/web/static/assets.schema.yaml ...you will find definitions for heat, glance, and murano assets indicating required properties etc. -Steve __ 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 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] [app-catalog] Add TOSCA assets to the catalog
Hello, I am looking at this blueprint https://blueprints.launchpad.net/app-catalog/+spec/add-tosca-assets and confused about the first task, "define metadata for TOSCA assets"? Can someone please provide example of metadata for previous work on Heat and Murano? I tried to find some old patch for reference but couldn't get one. The TOSCA will provide YAML template file and package in a CSAR form (.csar and .zip) to host on catalog. Thanks! Regards, Sahdev Zala __ 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] [heat-translator] [tosca-parser] [heat] Heat-Translator 0.3.0 PyPI release
Hello Everyone, On behalf of the Heat-Translator team, I am pleased to announce the 0.3.0 PyPI release of heat-translator which can be downloaded from https://pypi.python.org/pypi/heat-translator This release includes following enhancements, Per project development plan, we will be having a point release every four to six weeks interval with new features. Thanks! Regards, Sahdev Zala __ 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] [tosca-parser] [heat-translator] [heat] TOSCA-Parser 0.3.0 PyPI release
Hello Everyone, On behalf of the TOSCA-Parser team, I am pleased to announce the 0.3.0 PyPI release of tosca-parser which can be downloaded from https://pypi.python.org/pypi/tosca-parser This release includes following enhancements, · Support for nested imports – allows use of importing type definition within a type definition. · Full validation of TOSCA template – until now we were throwing error as we hit but with full validation all errors are compiled and displayed together. This will be used in heat-translator to allow user to provide an option to validate TOSCA template without actual translation. · A new test shell entry point – a new shell command, tosca-parser, is created for testing and validating TOSCA templates. · Support for .csar file extension – now both .zip and .csar extensions are supported for a CSAR file. · Many small fixes – o Remove decompressed temporary directory after processing CSAR file in in unit tests in Jenkin’s environment. o Updated trove classifier for the project. o The tosca-parser project is added to OpenStack global requirements to automatically update requirements. o TOSCA definition update for admin and public endpoint, and PortSpec type per the latest spec. o New missing validation and i18n fixes. o Updated error messages for uniform formatting across the project. o Documentation update etc. Per project development plan, we will be having a point release every five to six weeks interval with new features. Thanks! Regards, Sahdev Zala __ 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] [Murano] py26 support in python-muranoclient
> From: Clark Boylan > To: openstack-dev@lists.openstack.org > Date: 10/09/2015 02:00 PM > Subject: Re: [openstack-dev] [Murano] py26 support in python-muranoclient > > > > On Fri, Oct 9, 2015, at 10:32 AM, Vahid S Hashemian wrote: > > Serg, Jeremy, > > > > Thank you for your response, so the issue I ran into with my patch is the > > gate job failing on python26. > > You can see it here: https://review.openstack.org/#/c/232271/ > > > > Serg suggested that we add 2.6 support to tosca-parser, which is fine > > with > > us. > > But I got a bit confused after reading Jeremy's response. > > It seems to me that the support will be going away, but there is no > > timeline (and therefore no near-term plan?) > > So, I'm hoping Jeremy can advise whether he also recommends the same > > thing, or not. > There is a timeline (though admittedly hard to find) at > https://etherpad.openstack.org/p/YVR-relmgt-stable-branch which says > Juno support would run through the end of November. Since Juno is the > last release to support python2.6 we will remove python2.6 support from > the test infrastructure at that time as well. > > I personally probably wouldn't bother with extra work to support > python2.6, but that all depends on how much work it is and whether or > not you find value in it. Ultimately it is up to you, just know that the > Infrastructure team will stop hosting testing for python2.6 when Juno is > EOLed. > > Hope this helps, > Clark Thanks Clark and Jeremy! This is very helpful. Serg, now knowing that CI testing is not going to continue in few weeks and many other projects has dropped python 2.6 support or getting there, if Murano decides the same that would be great. If Murano team decide to continue the 2.6 support, we will need to enable support in tosca-parser as well. As you mentioned it may not be a lot of work for us and we are totally fine in making changes, but without automated tests it can be challenging in future. Thanks! Sahdev Zala > __ > 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] [heat-translator] Nominating new core reviewers
Thanks all for your vote to this email thread or via email to me. I have added Vahid Hashemian and Srinivas Tadepalli as core reviewers for the heat-translator project. Congratulations both! Regards, Sahdev Zala From: Idan Moyal To: openstack-dev@lists.openstack.org Date: 08/19/2015 06:52 AM Subject:Re: [openstack-dev] Fw: [heat-translator] Nominating new corereviewers +1 Hello, I am glad to nominate Vahid Hashemian [1] and Srinivas Tadepalli [2] for the Heat-Translator core reviewers team. Both of them have been providing significant contribution, development and review, since the beginning of this year and knows code base well. Existing cores, please reply this email by end of this week with your vote +1/-1 for their addition to the team. Review stats: http://stackalytics.com/report/contribution/heat-translator/90 [1] https://review.openstack.org/#/q/reviewer:%22Vahid+Hashemian+%253Cvahidhashemian%2540us.ibm.com%253E%22,n,z [2] https://review.openstack.org/#/q/reviewer:%22srinivas_tadepalli+%253Csrinivas.tadepalli%2540tcs.com%253E%22,n,z Regards, Sahdev Zala PTL, Heat-Translator __ 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] [heat-translator] Nominating new core reviewers
Hello, I am glad to nominate Vahid Hashemian [1] and Srinivas Tadepalli [2] for the Heat-Translator core reviewers team. Both of them have been providing significant contribution, development and review, since the beginning of this year and knows code base well. Existing cores, please reply this email by end of this week with your vote +1/-1 for their addition to the team. Review stats: http://stackalytics.com/report/contribution/heat-translator/90 [1] https://review.openstack.org/#/q/reviewer:%22Vahid+Hashemian+%253Cvahidhashemian%2540us.ibm.com%253E%22,n,z [2] https://review.openstack.org/#/q/reviewer:%22srinivas_tadepalli+%253Csrinivas.tadepalli%2540tcs.com%253E%22,n,z Regards, Sahdev Zala PTL, Heat-Translator __ 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] [heat-translator] [heat] IRC Channel for heat-translator
Hi everyone, I just wanted to let you know that the heat-translator project now has IRC Channel in place - #openstack-heat-translator Thanks! Regards, Sahdev Zala __ 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] [Heat] Request for python-heatclient project to adopt heat-translator
Thanks all for a good discussion. I would like to call for an agreement on this subject in Wednesday's (Oct 8th) Heat IRC meeting. It has been added in the agenda. Thanks! Regards, Sahdev Zala IBM SWG Standards Strategy Durham, NC (919)486-2915 T/L: 526-2915 From: Steven Hardy To: "OpenStack Development Mailing List (not for usage questions)" Date: 09/23/2014 05:46 AM Subject:Re: [openstack-dev] [Heat] Request for python-heatclient project to adopt heat-translator On Fri, Sep 19, 2014 at 06:54:27PM -0400, Zane Bitter wrote: > On 09/09/14 05:52, Steven Hardy wrote: > >Hi Sahdev, > > > >On Tue, Sep 02, 2014 at 11:52:30AM -0400, Sahdev P Zala wrote: > >>Hello guys, > >> > >>As you know, the heat-translator project was started early this year with > >>an aim to create a tool to translate non-Heat templates to HOT. It is a > >>StackForge project licensed under Apache 2. We have made good progress > >>with its development and a demo was given at the OpenStack 2014 Atlanta > >>summit during a half-a-day session that was dedicated to heat-translator > >>project and related TOSCA discussion. Currently the development and > >>testing is done with the TOSCA template format but the tool is designed to > >>be generic enough to work with templates other than TOSCA. There are five > >>developers actively contributing to the development. In addition, all > >>current Heat core members are already core members of the heat-translator > >>project. > >> > >>Recently, I attended Heat Mid Cycle Meet Up for Juno in Raleigh and > >>updated the attendees on heat-translator project and ongoing progress. I > >>also requested everyone for a formal adoption of the project in the > >>python-heatclient and the consensus was that it is the right thing to do. > >>Also when the project was started, the initial plan was to make it > >>available in python-heatclient. Hereby, the heat-translator team would > >>like to make a request to have the heat-translator project to be adopted > >>by the python-heatclient/Heat program. > > > >Obviously I wasn't at the meetup, so I may be missing some context here, > >but can you answer some questions please? > > > >- Is the scope for heat-translator only tosca simple-profile, or also the > > original more heavyweight tosca too? > > > >- If it's only tosca simple-profile, has any thought been given to moving > > towards implementing support via a template parser plugin, rather than > > baking the translation into the client? > > One idea we discussed at the meetup was to use the template-building code > that we now have in Heat for building the HOT output from the translator - > e.g. the translator would produce ResourceDefinition objects and add them to > a HOTemplate object. > > That would actually get us a long way toward an implementation of a template > format plugin (which basically just has to spit out ResourceDefinition > objects). So maybe that approach would allow us to start in > python-heatclient and easily move it later into being a full-fledged > template format plugin in Heat itself. > > >While I see this effort as valuable, integrating the translator into the > >client seems the worst of all worlds to me: > > > >- Any users/services not intefacing to heat via python-heatclient can't use it > > Yep, this is a big downside (although presumably we'd want to build in a way > to just spit out the generated template that can be used by other clients). > > On the other hand, there is a big downside to having it (only) in Heat also > - you're dependent on the operator deciding to provide it. > > >- You prempt the decision about integration with any higher level services, > > e.g Mistral, Murano, Solum, if you bake in the translator at the > > heat level. > > Not sure I understand this one. I meant if non-simple TOSCA was in scope, would it make sense to bake the translation in at the heat level, when there are aspects of the DSL which we will never support (but some higher layer might). Given Sahdev's response saying simple-profile is all that is currently in scope, it's probably a non-issue, I just wanted to clarify if heat was the right place for this translation. Steve ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Heat] Request for python-heatclient project to adopt heat-translator
Hi Steve, sure. Please see my reply in-line. Thanks! Regards, Sahdev From: Steven Hardy To: "OpenStack Development Mailing List (not for usage questions)" Date: 09/09/2014 05:55 AM Subject:Re: [openstack-dev] [Heat] Request for python-heatclient project to adopt heat-translator Hi Sahdev, On Tue, Sep 02, 2014 at 11:52:30AM -0400, Sahdev P Zala wrote: >Hello guys, > >As you know, the heat-translator project was started early this year with >an aim to create a tool to translate non-Heat templates to HOT. It is a >StackForge project licensed under Apache 2. We have made good progress >with its development and a demo was given at the OpenStack 2014 Atlanta >summit during a half-a-day session that was dedicated to heat-translator >project and related TOSCA discussion. Currently the development and >testing is done with the TOSCA template format but the tool is designed to >be generic enough to work with templates other than TOSCA. There are five >developers actively contributing to the development. In addition, all >current Heat core members are already core members of the heat-translator >project. > >Recently, I attended Heat Mid Cycle Meet Up for Juno in Raleigh and >updated the attendees on heat-translator project and ongoing progress. I >also requested everyone for a formal adoption of the project in the >python-heatclient and the consensus was that it is the right thing to do. >Also when the project was started, the initial plan was to make it >available in python-heatclient. Hereby, the heat-translator team would >like to make a request to have the heat-translator project to be adopted >by the python-heatclient/Heat program. Obviously I wasn't at the meetup, so I may be missing some context here, but can you answer some questions please? - Is the scope for heat-translator only tosca simple-profile, or also the original more heavyweight tosca too? Heat-translator is designed to be used to translate any non-Heat templates to HOT. However, current development is done for the TOSCA simple-profile only and there is no plan to use it for heavyweight TOSCA. - If it's only tosca simple-profile, has any thought been given to moving towards implementing support via a template parser plugin, rather than baking the translation into the client? At the meetup, Randall and Zane also mentioned that we should dig into the plugin and see if that can also be used for TOSCA. However, we all agreed that translation is still good to have and if plugin can be used that will be another option for TOSCA users. While I see this effort as valuable, integrating the translator into the client seems the worst of all worlds to me: - Any users/services not intefacing to heat via python-heatclient can't use it With python-heatclient, translator will just add a command line option i.e. something like ‘heat-translator ' which will provide an output as HOT. The user needs to take the translated template and run it with Heat. - You prempt the decision about integration with any higher level services, e.g Mistral, Murano, Solum, if you bake in the translator at the heat level. Hopefully that won't happen. The translator can be a simple integration at the client level and provided just as a command line option without any added complexity. The scope question is probably key here - if you think the translator can do (or will be able to do) a 100% non-lossy conversion to HOT using only Heat, maybe it's time we considered discussing integration into Heat the service rather than the client. When the project was started, there was a discussion with Steve Baker and others on IRC that initially it is a good idea to provide the translator tool to users via python-heatclient and eventually, as the tool gets more mature, we can discuss to make it available in Heat engine to provide a seamless deployment of translated template. Conversely, if you're going to need other services to fully implement the spec, it probably makes sense for the translator to remain layered over heat (or integrated with another project which is layered over heat). The translator project has no dependency on other services and hoping for the same in future. I hope my answers make sense. Please let me know if you have further questions. Thanks! Steve ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Heat] Request for python-heatclient project to adopt heat-translator
Hi Angus, please see my reply in-line. Thanks! Regards, Sahdev From: Angus Salkeld To: "OpenStack Development Mailing List (not for usage questions)" Date: 09/09/2014 12:25 AM Subject:Re: [openstack-dev] [Heat] Request for python-heatclient project to adopt heat-translator Hi Would the translator ever need to talk to something like Mistral for workflow? I do not think so. There is no current plan that needs the heat-translator to talk to Mistral or other services. If so does it make sense to hook the translator into heat client. (this might not be an issue, just asking). -Angus On Wed, Sep 3, 2014 at 1:52 AM, Sahdev P Zala wrote: Hello guys, As you know, the heat-translator project was started early this year with an aim to create a tool to translate non-Heat templates to HOT. It is a StackForge project licensed under Apache 2. We have made good progress with its development and a demo was given at the OpenStack 2014 Atlanta summit during a half-a-day session that was dedicated to heat-translator project and related TOSCA discussion. Currently the development and testing is done with the TOSCA template format but the tool is designed to be generic enough to work with templates other than TOSCA. There are five developers actively contributing to the development. In addition, all current Heat core members are already core members of the heat-translator project. Recently, I attended Heat Mid Cycle Meet Up for Juno in Raleigh and updated the attendees on heat-translator project and ongoing progress. I also requested everyone for a formal adoption of the project in the python-heatclient and the consensus was that it is the right thing to do. Also when the project was started, the initial plan was to make it available in python-heatclient. Hereby, the heat-translator team would like to make a request to have the heat-translator project to be adopted by the python-heatclient/Heat program. Below are some of links related to the project, https://github.com/stackforge/heat-translator https://launchpad.net/heat-translator https://blueprints.launchpad.net/heat-translator https://bugs.launchpad.net/heat-translator http://heat-translator.readthedocs.org/ (in progress) Thanks! Regards, Sahdev Zala IBM SWG Standards Strategy Durham, NC (919)486-2915 T/L: 526-2915 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Heat] Request for python-heatclient project to adopt heat-translator
Hello guys, As you know, the heat-translator project was started early this year with an aim to create a tool to translate non-Heat templates to HOT. It is a StackForge project licensed under Apache 2. We have made good progress with its development and a demo was given at the OpenStack 2014 Atlanta summit during a half-a-day session that was dedicated to heat-translator project and related TOSCA discussion. Currently the development and testing is done with the TOSCA template format but the tool is designed to be generic enough to work with templates other than TOSCA. There are five developers actively contributing to the development. In addition, all current Heat core members are already core members of the heat-translator project. Recently, I attended Heat Mid Cycle Meet Up for Juno in Raleigh and updated the attendees on heat-translator project and ongoing progress. I also requested everyone for a formal adoption of the project in the python-heatclient and the consensus was that it is the right thing to do. Also when the project was started, the initial plan was to make it available in python-heatclient. Hereby, the heat-translator team would like to make a request to have the heat-translator project to be adopted by the python-heatclient/Heat program. Below are some of links related to the project, https://github.com/stackforge/heat-translator https://launchpad.net/heat-translator https://blueprints.launchpad.net/heat-translator https://bugs.launchpad.net/heat-translator http://heat-translator.readthedocs.org/ (in progress) Thanks! Regards, Sahdev Zala IBM SWG Standards Strategy Durham, NC (919)486-2915 T/L: 526-2915 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
