cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Yadav (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-499) cloudmonkey CLI can't accept complex parameters
Date Fri, 16 Nov 2012 16:42:12 GMT


Rohit Yadav commented on CLOUDSTACK-499:

So, I've changed how requests are made and args are calculated; in the new format maps can
be passed as in http get requests for simplicity:

create networkoffering conservemode=true name=unique-name displaytext=description-text guestiptype=Isolated
traffictype=GUEST serviceofferingid=9f873a59-2c4a-4c4f-9e1d-c27d919be584 supportedservices=Dhcp,Dns,UserData
serviceproviderlist[0].service=Dhcp serviceproviderlist[0].provider=VirtualRouter serviceproviderlist[1].service=Dns
serviceproviderlist[1].provider=VirtualRouter serviceproviderlist[2].service=UserData serviceproviderlist[2].provider=VirtualRouter

This is still ugly and may be improved. Pl. share any improvement suggestions?
> cloudmonkey CLI can't accept complex parameters
> -----------------------------------------------
>                 Key: CLOUDSTACK-499
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>          Components: Usage
>    Affects Versions: 4.1.0
>         Environment: Ubuntu 12.04, KVM hypervisor
>            Reporter: Dave Cahill
>            Assignee: Rohit Yadav
>              Labels: cloudmonkey
>             Fix For: 4.1.0
> When setting up a networkoffering, there's a serviceProviderList parameter which is a
list of items, each of which has several key value pairs.
> According to Rohit (on dev list):
> "The way maps are handled in url are very different than how cloudmonkey parses and passing
> This actually needs to be fixed in Marvin, I've figured out a way but it may cause issues
with marvin, will discuss with Prasanna and fix it soon."

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