incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chip Childers (JIRA)" <>
Subject [jira] [Resolved] (CLOUDSTACK-514) Marvin and Cloudmonkey don't work when an API target uses https or an alternate path
Date Mon, 19 Nov 2012 19:27:59 GMT


Chip Childers resolved CLOUDSTACK-514.

    Resolution: Fixed

Resolved in master via the following two commits:

commit 311ef69a77e0f9b02b714786f04214ab9e0d0169
Author: Chip Childers <>
Date:   Mon Nov 19 14:24:10 2012 -0500

    CLOUDSTACK-514: Added protocol and path support to cloudmonkey.
    This is the second half of making cloudmonkey and marvin more
    flexible in environments that may have https enabled and / or
    a different path for the cloudstack API.
    Signed-off-by: Chip Childers <>

commit 2ee9253c78152d517f8448f66a779c6e3777b19c
Author: Chip Childers <>
Date:   Mon Nov 19 12:06:18 2012 -0500

    CLOUDSTACK-514: Adding https and api path support to Marvin.
    This is the first part of fixing CLOUDSTACK-514, and is hopefully
    backward compatible with previous use of Marvin.  I added two new
    parameters to the cloudstackConnection module, protocol and path.
    Both have been defaulted to the previously *assumed* values.
    Signed-off-by: Chip Childers <>
> Marvin and Cloudmonkey don't work when an API target uses https or an alternate path
> ------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-514
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>          Components: Cloudmonkey, Test Tools
>    Affects Versions: 4.0.0
>            Reporter: Chip Childers
>            Assignee: Chip Childers
>            Priority: Critical
>             Fix For: 4.1.0
> Cloudmonkey and Marvin assume that the target API URL is going to be http, when it's
much more likely that production environments will be via https.  They also make an assumption
about the API's path, which is invalid when (for example) Citrix Cloud Portal is sitting on
top of CloudStack.
> I think we need to fix both of these issues.

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:

View raw message