Murano Weekly Meeting 2015.07.28

 

Meeting time：　　 2015.July.28th 1:00~2:00

Chairperson：　　　Kirill Zaitsev, core from Mirantis

Meeting summary：

 

1.Migrating to yaql 1.0 status.

   PIC:      Stan Lagun

   Status:  This quest is almost completed and most of our unit tests are green already with small minor issues left to fix so the final version is going to be really soon.

   Action:  As soon as yaql and muranopl is ready, Kirill Zaitsev will write an email to encourage murano team and murano users to test new yaql.

 

2.Cloud Foundry Service Broker status

   PIC:      Nikolay Starodubtsev

   Status:  The Cloud Foundry integration code is ready for review, and waiting for the new Cloud Foundry stackato image to test the new ServiceBroker API v2.5.

   What is Cloud Foundry?

 Cloud foundry is the first open source PAAS cloud platform which is launched by VMware.

 It supports a variety of framework, language, runtime environment, cloud platform and application services,

 allowing developers to application deployment and expansion within a few seconds,

 no need to worry about the problem of any infrastructure. 

 About this point, it is similar to Murano.

 Link: http://baike.baidu.com/view/8193015.htm

   Blue Print Description:

　　　　  CloudFoundry allows an integration with 3rd party services via ServiceBroker API.

　　　　  The current version of API is v2.5. The API is provided by Pivotal Company which is established by EMC and VMWare.

　　　　  If Murano implements this API, it will be possible to expose all Murano applications as a services in CloudFoundry PaaS.

　　　　  This will significantly improve PaaS user experience as it will have an ability to integrate his app with existing apps in Murano

　　　　  and deploy really complex configurations on top of OpenStack.

　　　　  Link: https://blueprints.launchpad.net/murano/+spec/cloudfoundry-api-support

 

3.Support for heat environments and files status

   PIC:      mgershen

   Status:  

　　　　  (1) The heat environments feature implementation has not set in yet.

 　　　　 (2) The heat files feature implementation is going well and waiting for review.

　　　　  (3) In order to make the connection between the stack in heat to the Murano environments, the Murano environment ID will be a part of the stack name.

　　　　  (4) Heat has already allowed showing and hiding stack tagging, and tagging paramters should be passed when Murano calls heat API.

   Blue Print Description:

 　　　　 (1) Allowing Heat environments to be saved and deployed as part of a Murano Heat package.

　　　　  Heat environment is used to map resource names to templates, and optionally can be used to define common stack parameters.

 

　　　　  Heat environment files should be placed in the package under '/Heat/Environments'.

　　　　  When a user request to add a Heat-generated package to a Murano environment, 

　　　　  he should have an option to specify one of the heat-environment-files located at '/Heat/Environments' in the package, 

　　　　  and this heat-environment-file should be sent to Heat with the template during Murano environment deployment. 

　　　　  If no heat-environment-file was specified, the template will be deployed without a Heat environment.

 

　　　　  (2) Allowing Heat additional files to be saved and deployed as part of a Murano Heat applications.

　　　　  Adding additional files to a package should be optional. Such files should be placed in the package under '/HeatFiles'. 

　　　　  When a Heat-generated package is being deployed,

　　　　  if the package contains additional files, they should be sent to Heat together with the template and params.

　　　　  If there are any Heat additional files located in the package under '/HeatFiles', 

　　　　  they should all be sent with the template during stack creation in Heat.

 

　　　　  Link: https://blueprints.launchpad.net/murano/+spec/cloudfoundry-api-support

 

4.My Weekly Work

　　　　 With Kirill Zaitsev's help, I have made an implementation for "Add js linting jobs to murano-dashboard".

　　　　 Almost I have submit 6 partially implements for this blue print, and 3 partially implements have been merged in this week.

   Blue Print Description:

　　　　 To ensure good quality of js files murano-dashboard should have js-linter jobs.

　　　　 Horizon is currently adopting JP style guide and eslint, we could adopt the same tools for the purpose.

　　　　 Blue Print Link: https://blueprints.launchpad.net/murano/+spec/add-js-lint-jobs

　　　　 Blue Print Query Link: https://review.openstack.org/#/q/project:openstack/murano-dashboard+branch:master+topic:bp/add-js-lint-jobs,n,z