Re: [VOTE] Release Apache CloudStack CloudMonkey 5.2.0 (take #3)

2014-08-23 Thread Nux! 
-1 for now (do I have binding "powers"?)

I've started with fresh config (ie. rm -rf ~/.cloudmonkey), but I keep getting 
this:

đŸ” > sync
Error processing json: No JSON object could be decoded
Failed to sync apis, please check your config?
Note: `sync` requires api discovery service enabled on the CloudStack 
management server

The log is extensive and with loads of sensitive information, will need 
clearing which I can't do right now.

All my settings are AFAIK correct.. Previous version was working fine with the 
same credentials.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro


- Original Message -
> From: "Sebastien Goasguen" 
> To: dev@cloudstack.apache.org
> Sent: Friday, 22 August, 2014 7:53:13 PM
> Subject: Re: [VOTE] Release Apache CloudStack CloudMonkey 5.2.0 (take #3)
> 
> 
> On Aug 22, 2014, at 5:16 AM, Rohit Yadav  wrote:
> 
> > Hi,
> > 
> > On 22-Aug-2014, at 10:22 am, Sebastien Goasguen  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
> > CSForge – rapid IaaS deployment framework
> > CloudStack Consulting
> > CloudStack Infrastructure
> > Support
> > CloudStack Bootcamp Training
> > Courses
> > 
> > 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.
> 
>

CoreOS

2014-08-23 Thread Mo 
Greetings Dev,

Has anyone successfully setup CoreOS on Cloudstack / KVM? If so, wanna
share your tips?

- Mo

Re: [VOTE] Release Apache CloudStack CloudMonkey 5.2.0 (take #3)

2014-08-23 Thread Rohit Yadav 
Hi,


On 23-Aug-2014, at 2:07 pm, Nux!  wrote:

> -1 for now (do I have binding "powers"?)
>
> I've started with fresh config (ie. rm -rf ~/.cloudmonkey), but I keep 
> getting this:
>
> đŸ” > sync
> Error processing json: No JSON object could be decoded
> Failed to sync apis, please check your config?
> Note: `sync` requires api discovery service enabled on the CloudStack 
> management server
>
> The log is extensive and with loads of sensitive information, will need 
> clearing which I can't do right now.
>
> All my settings are AFAIK correct.. Previous version was working fine with 
> the same credentials.

Can you recheck your config, url etc.? The order of preference is keys > 
password auth > integration (8096).

Can you check the url it is calling in ~/.cloudmonkey/log and share with me as 
well removing the session key etc?

Can you try by doing a clean remove, pip uninstall cloudmonkey and build using 
the source tarball and try again?

I’ve checked against exoscale's, local setup and few other setup and this works 
for me.

Regards.

>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
>
> - Original Message -
>> From: "Sebastien Goasguen" 
>> To: dev@cloudstack.apache.org
>> Sent: Friday, 22 August, 2014 7:53:13 PM
>> Subject: Re: [VOTE] Release Apache CloudStack CloudMonkey 5.2.0 (take #3)
>>
>>
>> On Aug 22, 2014, at 5:16 AM, Rohit Yadav  wrote:
>>
>>> Hi,
>>>
>>> On 22-Aug-2014, at 10:22 am, Sebastien Goasguen  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
>>> CSForge – rapid IaaS deployment framework
>>> CloudStack Consulting
>>> CloudStack Infrastructure
>>> Support
>>> CloudStack Bootcamp Training
>>> Courses
>>>
>>> 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 incor

Re: CoreOS

2014-08-23 Thread Nux! 
Hello,

Their openstack image will boot, but of course user data/passwd, stuff specific 
to Cloudstack will not.
I have looked into it a bit and found quite frustrating to work with it (it 
seemed limited and esoteric); they stripped it down quite a bit and the 
partitioning is weird. I want to look at it again, but when I have some more 
time.

Let me know if you have more success with it. :)



--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro


- Original Message -
> From: "Mo" 
> To: "dev" 
> Sent: Saturday, 23 August, 2014 1:54:18 PM
> Subject: CoreOS
> 
> Greetings Dev,
> 
> Has anyone successfully setup CoreOS on Cloudstack / KVM? If so, wanna
> share your tips?
> 
> - Mo
>

API doc build failure in 4.4 ARM

2014-08-23 Thread Ezaul Zillmer 
Hi all
I'm trying to compile in 4.4 cloustack cubieboard2 ARMv7
'm encontrondo a difficulty to compile apidocs FAILURE
post here the result of the compilation would like to know what to do to
solve
this problem?

INFO] Apache CloudStack Plugin - Palo Alto .. SUCCESS [1:
10.948s]
[INFO] Apache CloudStack Plugin - Network NetScaler .. SUCCESS [1:
13.317s]
[INFO] Apache CloudStack Plugin - Network Nicira NVP . SUCCESS [1:
20.384s]
[INFO] Apache CloudStack Plugin - BigSwitch Virtual Network Segment SUCCESS
[56.306s]
[INFO] Apache CloudStack Plugin - Midokura Midonet ... SUCCESS [2:
08.551s]
[INFO] Apache CloudStack Plugin - Stratosphere SSP ... SUCCESS
[56.283s]
[INFO] Apache CloudStack Plugin - Network Opendaylight ... SUCCESS
[56.978s]
[INFO] Apache CloudStack Plugin - Random Storage Allocator SUCCESS
[34.541s]
[INFO] Apache CloudStack Plugin - User Authenticator LDAP SUCCESS [1:
39.094s]
[INFO] Apache CloudStack Plugin - User Authenticator MD5. SUCCESS [35.514s]
[INFO] Apache CloudStack Plugin - User Authenticator Plain Text SUCCESS
[32.886s]
[INFO] Apache CloudStack Plugin - User Authenticator Salted SHA256 SUCCESS
[44.703s]
[INFO] Apache CloudStack Plugin - Dns Notifier Example ... SUCCESS
[32.130s]
[INFO] Apache CloudStack Plugin - Image S3 Storage ... SUCCESS
[38.533s]
[INFO] Apache CloudStack Plugin - Image Storage provider Swift SUCCESS
[35.296s]
[INFO] Apache CloudStack Plugin - Image Storage default provider SUCCESS
[35.825s]
[INFO] Apache CloudStack Plugin - Storage Image sample provider SUCCESS
[34.548s]
[INFO] Apache CloudStack Plugin - Volume Nexenta Storage Provider SUCCESS
[47.713s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider SUCCESS
[1: 11.799s]
[INFO] Apache CloudStack Plugin - Volume Storage default provider SUCCESS
[37.480s]
[INFO] Apache CloudStack Plugin - Storage Volume CloudByte Provider SUCCESS
[48.737s]
[INFO] Apache CloudStack Plugin - Storage Volume sample provider SUCCESS
[35.173s]
[INFO] Apache CloudStack Plugin - SNMP Alerts  SUCCESS
[48.381s]
[INFO] Apache CloudStack Plugin - Syslog Alerts .. SUCCESS
[41.366s]
[INFO] Apache CloudStack Plugin - VXLAN Network .. SUCCESS
[49.315s]
[INFO] Apache CloudStack Framework - Spring Module ... SUCCESS
[47.235s]
[INFO] Apache CloudStack Secondary Storage Controller  SUCCESS
[38.601s]
[INFO] Apache CloudStack Console Proxy - RDP Client .. SUCCESS [1:
42.416s]
[INFO] Apache CloudStack Console Proxy ... SUCCESS
[15.272s]
[INFO] Apache CloudStack Console Proxy - Server .. SUCCESS
[45.385s]
[INFO] Apache CloudStack System ... VM SUCCESS [1:
44.692s]
[INFO] Apache CloudStack UI Client ... SUCCESS [4:
02.765s]
[INFO] Apache CloudStack Framework - QuickCloud .. SUCCESS
[14.270s]
[INFO] Apache CloudStack Test  SUCCESS
[33.130s]
[INFO] Apache CloudStack Developer Mode .. SUCCESS
[31.887s]
[INFO] Apache CloudStack Developer Tools . SUCCESS [4.948s]
[INFO] Apache CloudStack apidocs . FAILURE [4:
55.573s]
[INFO] Apache CloudStack marvin .. SKIPPED
[INFO] Apache CloudStack DevCloud  SKIPPED
[INFO] Apache CloudStack DevCloud-KVM  SKIPPED
[INFO] ---
-
[INFO] BUILD FAILURE
[INFO] ---
-
[INFO] Total time: 1: 49: 29.237s
[INFO] Finished at: Sat Aug 23 16:27:15 EDT 2014
[INFO] Final Memory: 61M / 159M
[INFO] ---
-
[ERROR] Failed to execute goal org.codehaus.mojo: exec-maven-plugin: 1.2.1:
exec (compile) on project cloud-apidoc: Command execution failed. Process
exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the-and switch.
[ERROR] Re-run Maven using the-X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read The Following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn  rf: cloud-apidoc

Any Solution? for my problem?
Thank you I'm waiting

Re: CoreOS

2014-08-23 Thread Coetsier, Antoine 
Work has been done but not fully documented yet:

https://github.com/coreos/coreos-overlay/tree/master/coreos-base/oem-clouds
tack

-- 

Antoine 






Le 23.08.14 23:57, « Nux! »  a écrit :

>Hello,
>
>Their openstack image will boot, but of course user data/passwd, stuff
>specific to Cloudstack will not.
>I have looked into it a bit and found quite frustrating to work with it
>(it seemed limited and esoteric); they stripped it down quite a bit and
>the partitioning is weird. I want to look at it again, but when I have
>some more time.
>
>Let me know if you have more success with it. :)
>
>
>
>--
>Sent from the Delta quadrant using Borg technology!
>
>Nux!
>www.nux.ro
>
>
>- Original Message -
>> From: "Mo" 
>> To: "dev" 
>> Sent: Saturday, 23 August, 2014 1:54:18 PM
>> Subject: CoreOS
>> 
>> Greetings Dev,
>> 
>> Has anyone successfully setup CoreOS on Cloudstack / KVM? If so, wanna
>> share your tips?
>> 
>> - Mo
>>