Jump to: navigation, search

Difference between revisions of "Meetings/MuranoAgenda"

Line 15: Line 15:
  
 
* Kilo-2 status
 
* Kilo-2 status
* Destiny of the following blueprints
+
* Destiny of the following blueprints (do we need this features? If yes, need to set estimates)
 +
 
 
  * [https://blueprints.launchpad.net/murano/+spec/ability-to-specify-url-for-services-definitions Add the ability to specify url to tar.gz file with user-defined service]
 
  * [https://blueprints.launchpad.net/murano/+spec/ability-to-specify-url-for-services-definitions Add the ability to specify url to tar.gz file with user-defined service]
 
  * [https://blueprints.launchpad.net/murano/+spec/docker-registry-in-murano Support docker registry and expose Docker apps in Murano Catalog]
 
  * [https://blueprints.launchpad.net/murano/+spec/docker-registry-in-murano Support docker registry and expose Docker apps in Murano Catalog]
 
  * [https://blueprints.launchpad.net/murano/+spec/admin-rights-restriction Need to restrict admin rights on actions with non-pubic packages belongs to other tenants]
 
  * [https://blueprints.launchpad.net/murano/+spec/admin-rights-restriction Need to restrict admin rights on actions with non-pubic packages belongs to other tenants]
 +
* [https://blueprints.launchpad.net/murano/+spec/stop-deploy-during-the-deployment User should have possibility to stop environment deploy]
  
 
* Open Discussion
 
* Open Discussion

Revision as of 14:52, 3 February 2015

We have meetings in #openstack-meeting-alt weekly on Tuesdays at 17:00 UTC.

Next meetings

  • February 3, 2015, 17:00 UTC

Agenda

'templates' is too common word, especially in Openstack

 - environment-templates
 - environment-snapshots
 - environment blueprints
  • Kilo-2 status
  • Destiny of the following blueprints (do we need this features? If yes, need to set estimates)
* Add the ability to specify url to tar.gz file with user-defined service
* Support docker registry and expose Docker apps in Murano Catalog
* Need to restrict admin rights on actions with non-pubic packages belongs to other tenants
* User should have possibility to stop environment deploy
  • Open Discussion

Checklist for the meeting organizer

  • Publish the agenda 24h in advance.
  • Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action.
  • Use http://meetbot.debian.net/Manual.html to get an automatic summary.
  • Prepare an outline for the meeting to speed things up.
  • Record decisions and commitments; review in the next meeting.

Previous meetings

http://eavesdrop.openstack.org/meetings/murano/