Difference between revisions of "Meetings/MuranoAgenda"
< Meetings
Timur Sufiev (talk | contribs) (→Agenda) |
(List of articles the HP team are interested in discussing) |
||
| Line 11: | Line 11: | ||
* Voting for the proper term 'Application being deployed/configured in an Environment' (Currently we have an 'Application' as entity in AppCatalog. Using an OOP analogy it is like a Class, while instances of that class are being added to an Environment - for later deployment. 'Class instance' entity is now called 'Service' - but that is a legacy of times when Murano aimed to deploy Windows services only. So that term should be remade.) | * Voting for the proper term 'Application being deployed/configured in an Environment' (Currently we have an 'Application' as entity in AppCatalog. Using an OOP analogy it is like a Class, while instances of that class are being added to an Environment - for later deployment. 'Class instance' entity is now called 'Service' - but that is a legacy of times when Murano aimed to deploy Windows services only. So that term should be remade.) | ||
* Drafting plan for the next release cycle: | * Drafting plan for the next release cycle: | ||
| − | ** Discuss the feedback about App Catalog description (https://wiki.openstack.org/wiki/Murano/ApplicationCatalog) from HP team | + | ** Discuss the feedback about App Catalog description (https://wiki.openstack.org/wiki/Murano/ApplicationCatalog) from HP team. List of additions we've thought about so far: |
| + | *** Support for packages without installation components (e.g. 3rd party services) (https://blueprints.launchpad.net/murano/+spec/packages-without-classes) | ||
| + | *** Credential storage for those services (probably need to wait until Barbican is further along) | ||
| + | *** Additional author/supplier information (https://blueprints.launchpad.net/murano/+spec/additional-author-information) | ||
| + | *** Support for contacting APIs (both in-stack, like Trove, and external) in packages (this is an existing blueprint https://blueprints.launchpad.net/murano/+spec/call-api-from-workflows) | ||
| + | *** Better unit test coverage | ||
| + | *** Permission policies in line with other openstack services (https://blueprints.launchpad.net/murano/+spec/policy-checks-in-api) | ||
| + | *** Some UI changes from our user experience team (these are cosmetic, can discuss them separately with whoever's interested) | ||
| + | *** User documentation (particularly creating packages) | ||
| + | *** Ceilometer integration (I think this is already on the roadmap) | ||
** Compose the list of missing features, prioritize | ** Compose the list of missing features, prioritize | ||
* Open discussion | * Open discussion | ||
Revision as of 16:49, 21 April 2014
We have meetings in #openstack-meeting-alt weekly on Tuesdays at 17:00 UTC.
Next meetings
- Apr 24, 2014, 17:00 UTC
Agenda
- Roll call
- Action Items Review
- Release status
- Voting for the proper term 'Application being deployed/configured in an Environment' (Currently we have an 'Application' as entity in AppCatalog. Using an OOP analogy it is like a Class, while instances of that class are being added to an Environment - for later deployment. 'Class instance' entity is now called 'Service' - but that is a legacy of times when Murano aimed to deploy Windows services only. So that term should be remade.)
- Drafting plan for the next release cycle:
- Discuss the feedback about App Catalog description (https://wiki.openstack.org/wiki/Murano/ApplicationCatalog) from HP team. List of additions we've thought about so far:
- Support for packages without installation components (e.g. 3rd party services) (https://blueprints.launchpad.net/murano/+spec/packages-without-classes)
- Credential storage for those services (probably need to wait until Barbican is further along)
- Additional author/supplier information (https://blueprints.launchpad.net/murano/+spec/additional-author-information)
- Support for contacting APIs (both in-stack, like Trove, and external) in packages (this is an existing blueprint https://blueprints.launchpad.net/murano/+spec/call-api-from-workflows)
- Better unit test coverage
- Permission policies in line with other openstack services (https://blueprints.launchpad.net/murano/+spec/policy-checks-in-api)
- Some UI changes from our user experience team (these are cosmetic, can discuss them separately with whoever's interested)
- User documentation (particularly creating packages)
- Ceilometer integration (I think this is already on the roadmap)
- Compose the list of missing features, prioritize
- Discuss the feedback about App Catalog description (https://wiki.openstack.org/wiki/Murano/ApplicationCatalog) from HP team. List of additions we've thought about so far:
- 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.
