On Aug 22, 2014, at 5:16 AM, Rohit Yadav <rohit.ya...@shapeblue.com> wrote:

> Hi,
> 
> On 22-Aug-2014, at 10:22 am, Sebastien Goasguen <run...@gmail.com> wrote:
> 
>> Rohit, I am not sure what you tried to do with the url setting.
>> 
>> This is not entirely backward compatible because I need to create a profile 
>> anyway (add profile under core then move the user section under the profile 
>> name..etc).
>> If I keep host, path etc…it dos create a url key automatically but it seems 
>> to be hard coded to http://localhost:8080/client/api
> 
> When cloudmonkey starts, it assumes the defaults in case any key is missing 
> in the config. This issue you’re seeing is because cloudmonkey does not know 
> which config to pick the new one of old one and what to do if both old and 
> new ones exist.
> 
>> I was under the impression that it would read existing 
>> host/path/port/protocol keys and form a a new url value…
> 
> If we had host, port, path, protocol in the config file and the server 
> profile section as well there won’t be any way to know which one to pick. To 
> fix that, we don’t write or read these values from config file, but we still 
> support the set command on them which internally sets the url parameter.
> 
> This was also done so that any of your automation/script that are still using 
> set commands on these options won’t fail. And now cloudmonkey will not fail 
> and exit if there are any missing keys but it would add them in the config 
> and let you know.
> 
>> It does work with a properly set config file…so still +1 though in a perfect 
>> world this new version would re-format my config file properly including 
>> forming the profile section out of the user and server sections.
> 
> I think backward compatibility is best maintained at interface level so we 
> are not taking away any (set) options which was the fix.
> 
> If you’ve any solution on how to handle the case where both old config and 
> new config are present in the config, let’s fix that? There were couple of 
> other minor corner cases, supporting them would have added some technical 
> debt to the code so I avoided that and I think the impact to users would be 
> minimum. Please advise?

Since I don't have time to help with this, I am +1 as is.



> 
> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +41 779015219 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
> 
> 
> 
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
> CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
> CloudStack Infrastructure 
> Support<http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training 
> Courses<http://shapeblue.com/cloudstack-training/>
> 
> This email and any attachments to it may be confidential and are intended 
> solely for the use of the individual to whom it is addressed. Any views or 
> opinions expressed are solely those of the author and do not necessarily 
> represent those of Shape Blue Ltd or related companies. If you are not the 
> intended recipient of this email, you must neither take any action based upon 
> its contents, nor copy or show it to anyone. Please contact the sender if you 
> believe you have received this email in error. Shape Blue Ltd is a company 
> incorporated in England & Wales. ShapeBlue Services India LLP is a company 
> incorporated in India and is operated under license from Shape Blue Ltd. 
> Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
> operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
> registered by The Republic of South Africa and is traded under license from 
> Shape Blue Ltd. ShapeBlue is a registered trademark.

Reply via email to