cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-8832) Update Nuage VSP plugin to work with Nuage VSP release 3.2
Date Tue, 03 Nov 2015 23:10:28 GMT


ASF GitHub Bot commented on CLOUDSTACK-8832:

Github user mike-tutkowski commented on the pull request:
    I liked Edison's approach to reviewing storage plug-in code: Since our storage plug-ins
don't really run in "sandboxes," his approach was to mainly examine the code to try to make
sure it wasn't inadvertently doing something bad to the data in the DB. For example, storage
plug-ins have direct access to the DB via DAO objects and can accidentally delete data that
doesn't belong to them.
    Aside from those kinds of actions, Edison didn't encourage spending too much time trying
to verify the correctness of storage plug-in code (that was an exercise left to the vendor).
    Personally, though, I'd like to get to the point where I can bring my Marvin integration
tests to the CloudStack repo and have them execute against virtual hardware. At the time being,
however, this is not an option.
    I also like having the ability to run these integration tests against different hypervisor
types and versions, but am not yet confident I know how to do this within CloudStack's integration-test
environment (so I just do this in house at SolidFire).

> Update Nuage VSP plugin to work with Nuage VSP release 3.2
> ----------------------------------------------------------
>                 Key: CLOUDSTACK-8832
>                 URL:
>             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

View raw message