cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rene Moser <>
Subject Re: [VOTE] Split Marvin to its own repository
Date Mon, 18 Jul 2016 12:02:57 GMT

I used to use marvin for setup simulator environments for using it as
integration test environments (4.5-latest) for the Ansible CloudStack

It's been a while and I can not really remember exactly what it was
caused it to fail but since a few weeks I was not able to setup such an
environment. I think it was related to some "cypto" dependencies which
didn't fit anymore.

Would splitting marvin out help to make the setup more reliable for
older cloudstack versions (e.g. 4.5 >=) as well?

Thanks for clarification.


On 07/18/2016 11:44 AM, Rohit Yadav wrote:
> All,
> Based on a recent discussion thread [1], I want to start a voting thread to
> gather consensus around splitting Marvin from the CloudStack repository.
> On successful voting, we would extract and maintain Marvin as a separate
> library in a separate repository (example repository [2]) and various
> build/test systems such as Travis [3] can install it directly for usage
> with pip+git etc.
> Background: During the build process, a commands.xml generated to build
> apidocs is also used to generate CloudStack Cmd and Request classes are
> auto-generated, which is the only dependency why we needed Marvin and
> CloudStack together. The auto-generated cloudstackAPI module can be also
> generated against a live running CloudStack mgmt server which has api
> discovery (listApis) enabled. The integration tests will still be tied to a
> branch and will remain withing the repository. A PR [3] was sent to show
> that we can still execute tests using this approach, and this would finally
> allow us to build, release and use Marvin as an independent library.
> Vote will be open for 72 hours.
> For sanity in tallying the vote, can PMC members please be sure to indicate
> "(binding)" with their vote?
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> [1]
> [2]
> [3]
> Regards,
> Rohit Yadav

View raw message