Activity log for bug #1519050

Date Who What changed Old value New value Message
2015-11-23 17:59:15 Bulat Gaifullin bug added bug
2015-11-23 17:59:23 Bulat Gaifullin fuel: importance Undecided High
2015-11-23 17:59:26 Bulat Gaifullin fuel: assignee Bulat Gaifullin (bgaifullin)
2015-11-23 17:59:29 Bulat Gaifullin fuel: milestone 8.0
2015-11-23 17:59:36 Bulat Gaifullin fuel: status New Confirmed
2015-11-23 17:59:40 Bulat Gaifullin fuel: status Confirmed In Progress
2015-11-23 20:21:08 Ilya Kutukov bug added subscriber Ilya Kutukov
2015-11-25 00:16:59 Mike Scherbakov tags feature
2015-11-25 07:59:30 OpenStack Infra fuel: assignee Bulat Gaifullin (bgaifullin) Ivan Kliuk (ivankliuk)
2015-11-25 08:11:20 Mike Scherbakov description User story: As a user who is experimenting in my OpenStack environment, I want to install application level plugins (non-core functionality) on top of my environment after it has been deployed so that I am not constrained only to plugins that were available (and I decided on) at the time of the deployment. Description: Some features (like VIP creation by a plugin) need to be reviewed to ensure they can be used by plugins post-deployment - if these features cannot be used, we need to backlog JIRA items as dependencies of this story to address changes We need to support a limited class of plugins that can be installed and/or modified after deployment. For example, a customer would like to add monitoring or log analytics. For some plugin types, such as SDN, post-deployment installation will not be possible. "Ex.1: During deployment customer decided add Zabbix - have to redeploy instead of add Ex.2: Cisco ACI plugin was late, entire deployment had to wait since no way to add plugin after deployment is started" Acceptance criteria: Any application level plugin can provide the same functionality if added after the environment is deployed as before Current application level plugins - Zabbix, others? User story: As a user who is experimenting in my OpenStack environment, I want to install application level plugins (non-core functionality) on top of my environment after it has been deployed so that I am not constrained only to plugins that were available (and I decided on) at the time of the deployment. Description: Some features (like VIP creation by a plugin) need to be reviewed to ensure they can be used by plugins post-deployment - if these features cannot be used, we need to backlog Launchpad items as dependencies of this story to address changes We need to support a limited class of plugins that can be installed and/or modified after deployment. For example, a customer would like to add monitoring or log analytics. For some plugin types, such as SDN, post-deployment installation will not be possible. "Ex.1: During deployment customer decided add Zabbix - have to redeploy instead of add Ex.2: Cisco ACI plugin was late, entire deployment had to wait since no way to add plugin after deployment is started" Acceptance criteria: Any application level plugin can provide the same functionality if added after the environment is deployed as before Current application level plugins - Zabbix, others?
2015-11-25 08:24:53 Maciej Relewicz tags feature area-python feature
2015-11-25 09:00:39 Bulat Gaifullin fuel: assignee Ivan Kliuk (ivankliuk) Bulat Gaifullin (bgaifullin)
2015-12-01 13:47:18 OpenStack Infra fuel: assignee Bulat Gaifullin (bgaifullin) Alexander Kislitsky (akislitsky)
2015-12-01 13:50:26 OpenStack Infra fuel: assignee Alexander Kislitsky (akislitsky) Bulat Gaifullin (bgaifullin)
2015-12-01 15:34:51 OpenStack Infra fuel: status In Progress Fix Committed
2015-12-02 16:44:45 Aleksei Stepanov tags area-python feature area-python feature on-verification
2016-02-03 10:50:44 ElenaRossokhina fuel: status Fix Committed Fix Released
2016-02-15 14:20:29 Nastya Urlapova tags area-python feature on-verification area-python feature