incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chip Childers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-414) marvin cloudstackAPI is packaging each api call in its separate module, we should create a single module
Date Mon, 07 Jan 2013 21:52:13 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chip Childers updated CLOUDSTACK-414:
-------------------------------------

    Fix Version/s:     (was: 4.1.0)
    
> marvin cloudstackAPI is packaging each api call in its separate module, we should create
a single module
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-414
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-414
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API, Test Tools
>    Affects Versions: 4.1.0
>         Environment: Devcloud, OSX 10.8.1
>            Reporter: sebastien goasguen
>            Assignee: sebastien goasguen
>            Priority: Critical
>
> build-marvin uses codegenerator.py to create the cloudstackAPI/ in the marvin tree. The
way this is done each API is its own module. This makes it troublesome to use the cloudstackAPI
in python. We may want to create a single cloudstackapi file which contains all the skeleton
classes generated.
> That way something like inspect.getmembers(cloudstackAPI,inspect.isclass) will return
something.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message