[
https://issues.apache.org/jira/browse/CLOUDSTACK-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14988021#comment-14988021
]
ASF GitHub Bot commented on CLOUDSTACK-8832:
--------------------------------------------
Github user jburwell commented on the pull request:
https://github.com/apache/cloudstack/pull/801#issuecomment-153473377
@ustcweizhou @remibergsma this is a massive technical debt that we are
carrying with other plugins, and I think we need to stop to expanding that
debt. In some cases, we (i.e. ASF) have been granted licenses for virtual
appliances to test plugin operation (a completely valid way to verify
operation). For others, we are shipping code that has not been verified for a
number of releases. In the past, plugins have been contributed and tested for
a release, but those contributors have not remained active to maintain the
plugin. Since the community lacks the equipment or test rigs, no one else can
pick up maintenance -- leaving us with bit rotting code. In summary, as a
community, we should not be accepting the responsibility to support and
maintain code whose operation we cannot verify -- plugin or core. The question
of what to do with existing plugins that don't meet this criteria is a
discussion for another thread.
> Update Nuage VSP plugin to work with Nuage VSP release 3.2
> ----------------------------------------------------------
>
> Key: CLOUDSTACK-8832
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8832
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.6.0
> Reporter: Nick Livens
> Assignee: Nick Livens
> Attachments: nuageVspMarvinLogs.tar.gz
>
>
> Nuage VSP 3.2 is being released, we want to bring the plugin up to date for
> this release
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
