RE: Re:RE: Re:RE: Re:RE: Where are the snapshots generated by schedules?

[Rajesh Battala]

Hi Enric,
This issue is resolved in the 4.1 build with this commit. 
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=913e2b38bfe5b29c0c172171e83d4fb7f8a8e6d6
Please use the latest build to resolve the snapshot issue.

Thanks
Rajesh Battala

> -Original Message-
> From: Enric Muñoz [mailto:emu...@intecom.ad]
> Sent: Friday, July 5, 2013 12:32 PM
> To: us...@cloudstack.apache.org
> Subject: RE: Re:RE: Re:RE: Re:RE: Where are the snapshots generated by
> schedules?
> 
> It happens to me the same using XCP 1.6. I set up recurring snapshots but
> they are not created and no error appears. However, there's  a warning in
> the logs every 5 minutes:
> 
> 2013-07-05 08:56:43,599 DEBUG [storage.snapshot.SnapshotSchedulerImpl]
> (SnapshotPollTask:null) Snapshot scheduler.poll is being called at 2013-07-05
> 06:56:43 GMT
> 2013-07-05 08:56:43,601 DEBUG [storage.snapshot.SnapshotSchedulerImpl]
> (SnapshotPollTask:null) Got 1 snapshots to be executed at 2013-07-05
> 06:56:43 GMT
> 2013-07-05 08:56:43,604 DEBUG [storage.snapshot.SnapshotSchedulerImpl]
> (SnapshotPollTask:null) Scheduling 1 snapshot for volume 20 for schedule id:
> 4 at 2013-07-02 12$
> 2013-07-05 08:56:43,613 WARN  [storage.snapshot.SnapshotSchedulerImpl]
> (SnapshotPollTask:null) Scheduling snapshot failed due to
> java.lang.NullPointerException
> 
> Anyone knows how this can be solved?
> 
> Thanks
> 
> -Mensaje original-
> De: WXR [mailto:1485739...@qq.com]
> Enviado el: martes, 02 de julio de 2013 17:38
> Para: users
> Asunto: Re:RE: Re:RE: Re:RE: Where are the snapshots generated by
> schedules?
> 
> I think the schedule job is created successfully.I can see the text like this:
> 
> 
> 
> 
> Scheduled Snapshots
>Time: 
> 1 min past the hr
>  Timezone:
> [UTC-12:00] GMT-12:00 Keep: 3
> 
> 
> 
> 
> -- Original --
> From:  "Rajesh Battala";
> Date:  Tue, Jul 2, 2013 11:15 PM
> To:  "us...@cloudstack.apache.org";
> 
> Subject:  RE: Re:RE: Re:RE: Where are the snapshots generated by schedules?
> 
> 
> 
> NPE issue for recurring snapshot is fixed long back. This should not occur.
> Schedule snapshots works the same way we take manually snapshots.
> For schedule snapshot, CS will create the createsnapshot async job while the
> schedule occurs to take the snapshot for the volume.
> Is the schedule snapshot job is created successfully?
> 
> 
> > -Original Message-
> > From: WXR [mailto:1485739...@qq.com]
> > Sent: Tuesday, July 2, 2013 8:34 PM
> > To: users
> > Subject: Re:RE: Re:RE: Where are the snapshots generated by schedules?
> >
> > Yes I'm using kvm,but I'm using basic network,not advanced network.
> > The jira link give a solution but I don't know how to do it,I'm not
> > familiar with java and git.
> > What can I do to fix the bug,should I rebuild the project?
> >
> >
> > -- Original --
> > From:  "Geoff Higginbottom";
> > Date:  Tue, Jul 2, 2013 10:38 PM
> > To:  "us...@cloudstack.apache.org";
> >
> > Subject:  RE: Re:RE: Where are the snapshots generated by schedules?
> >
> >
> >
> > Are you using KVM by any chance, there is currently a ticket logged in
> > relation to Scheduled Snapshots failing on KVM.
> >
> > If so take a look at
> > https://issues.apache.org/jira/browse/CLOUDSTACK-1353
> > and see if it mirrors your symptoms
> >
> > Regards
> >
> > Geoff Higginbottom
> >
> > D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
> >
> > geoff.higginbot...@shapeblue.com
> >
> >
> > -Original Message-
> > From: WXR [mailto:1485739...@qq.com]
> > Sent: 02 July 2013 15:36
> > To: users
> > Subject: Re:RE: Where are the snapshots generated by schedules?
> >
> > I'm sure I have added the schedule and I can see it at the bottom of
> > the schedule box.
> >
> >
> >
> >
> > -- Original --
> > From:  "Geoff Higginbottom";
> > Date:  Tue, Jul 2, 2013 10:27 PM
> > To:  "us...@cloudstack.apache.org";
> >
> > Subject:  RE: Where are the snapshots generated by schedules?
> >
> >
> >
> > When setting up the recurring snapshot, ensure that after entering the
> > times etc, you click the Add Button, then the Done Button.  Failing to
> > click the Add button will result in no Schedule being created
> >
> > Regards
> >
> > Geoff Higginbottom
> >
> > D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
> >
> > geoff.higginbot...@shapeblue.com
> >
> >
> > -Original Message-
> > From: WXR [mailto:1485739...@qq.com]
> > Sent: 02 July 2013 15:14
> > To: users
> > Subject: Where are the snapshots generated by schedules?
> >
> > If I create a snapshot of a volume , I can see it on the snapshot list.
> > But if I create a hourly schedule for a volume and wait enough
> > time(longer than 1 day),I can't see any snapshot associated with the
> > volume on the snapshot list.All snapshots listed are "manual".

Re: [Discuss][CLOUDSTACK-212] Namespace change for ASF

[Sebastien Goasguen]

On Jul 5, 2013, at 1:28 AM, Ryan Lei  wrote:

> Hi, the corresponding CLOUDSTACK-212 is marked as "Improvement," and
> planned to be fixed in 4.2.0.
> 
> But since we have passed the feature freeze date, will the namespace change
> be deferred to 4.3.0?
> 

Yes that's the plan, trying to have it reach master asap to be early in the 4.3 
development cycle.

we will update the bug fix version

> ---
> Yu-Heng (Ryan) Lei, Associate Reasearcher
> Chunghwa Telecom Laboratories / Cloud Computing Laboratory
> ryan...@cht.com.tw
> or
> ryanlei750...@gmail.com
> 
> 
> 
> On Fri, Jul 5, 2013 at 3:07 AM, Wido den Hollander  wrote:
> 
>> Hi,
>> 
>> 
>> On 07/04/2013 01:53 PM, Dharmesh Kakadia wrote:
>> 
>>> Hi,
>>> 
>>> Since the cloudstack project has moved to ASF, the suggestion is to move
>>> from com.cloud packages to org.apache java packages .(
>>> https://issues.apache.org/**jira/browse/CLOUDSTACK-212
>>> )
>>> 
>>> As you might be realize, this is pretty big change. And merging this
>>> changes with a continuously updating master is non-trivial. So, here is
>>> the
>>> planned strategy after discussion over IRC. I am starting this thread to
>>> inform and know everyone's opinions.
>>> 
>>> 1. I will be pushing code with new packages on branch "namespacechanges"
>>> and will notify on this thread as each refactored module is pushed.
>>> 
>>> 2. There will be a freeze on master branch commits for some time in which
>>> "namespacechanges" will be applied to master. I suggest the date to be
>>> 20th
>>> July.
>>> 
>>> 
>> +1 on doing this, since we have to do it at some point.
>> 
>> One question though, since this will break a lot of merges, can we also do
>> a whitespace fix?
>> 
>> We still have a lot of tabs instead of 4 spaces and with a simple find and
>> sed we can fix that.
>> 
>> Same goes for trailing spaces.
>> 
>> We could do one (or multiple) commits which address these issues at once?
>> 
>> Wido
>> 
>> 
>> 
>> 3. All the branch-owner updates their branch for reflect new packages. It
>>> was suggested that branch owners can look into the "namespacechanges"
>>> branch as it grows and start doing the package changes early, although it
>>> depends on branch-owners.
>>> 
>>> Thanks,
>>> Dharmesh
>>> 
>>> 

master not perfect:(

[Daan Hoogland]

H,

I get a repetition of the following sequence of logging when running master. 
Anybody knows what happened?

INFO  [agent.manager.AgentManagerImpl] (AgentManager-Handler-11:) Connection 
from /127.0.0.1 closed but no cleanup was done.
WARN  [utils.nio.Link] (AgentManager-Selector:) SSL: Fail to find the generated 
keystore. Loading fail-safe one to continue.
ERROR [agent.transport.Request] (AgentManager-Handler-13:) Caught problem with 
[{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicNetmask":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","privateIpAddress":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","privateNetmask":"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask":"255.255.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":"NfsSecondaryStorageResource","contextMap":{},"wait":0}}]
com.google.gson.JsonParseException: The JsonDeserializer 
com.cloud.agent.transport.ArrayTypeAdaptor@7db106d failed to deserialize json 
object 
[{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicNetmask":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","privateIpAddress":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","privateNetmask":"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask":"255.255.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":"NfsSecondaryStorageResource","contextMap":{},"wait":0}}]
 given the type class [Lcom.cloud.agent.api.Command;
   at 
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:64)
   at 
com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
   at 
com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(JsonDeserializationVisitor.java:80)
   at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:101)
   at 
com.google.gson.JsonDeserializationContextDefault.fromJsonArray(JsonDeserializationContextDefault.java:67)
   at 
com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:52)
   at com.google.gson.Gson.fromJson(Gson.java:551)
   at com.google.gson.Gson.fromJson(Gson.java:498)
   at com.cloud.agent.transport.Request.getCommands(Request.java:235)
   at 
com.cloud.agent.manager.AgentManagerImpl$AgentHandler.processRequest(AgentManagerImpl.java:1196)
   at 
com.cloud.agent.manager.AgentManagerImpl$AgentHandler.doTask(AgentManagerImpl.java:1349)
   at 
com.cloud.agent.manager.ClusteredAgentManagerImpl$ClusteredAgentHandler.doTask(ClusteredAgentManagerImpl.java:659)
   at com.cloud.utils.nio.Task.run(Task.java:83)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
Caused by: com.cloud.utils.exception.CloudRuntimeException: can't find 
StartupSecondaryStorageCommand
   at 
com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:77)
   at 
com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:37)
   at 
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:51)
   ... 15 more
WARN  [utils.nio.Task] (AgentManager-Handler-13:) Caught the following 
exception but pushing on
com.google.gson.JsonParseException: The JsonDeserializer 
com.cloud.agent.transport.ArrayTypeAdaptor@7db106d failed to deserialize json 
object 
[{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicNetmask":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","privateIpAddress":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","privateNetmask":"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask":"255.255.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":"NfsSecondaryStorageResource","contextMap":{},"wait":0}}]
 given the type class [Lcom.cloud.agent.api.Command;
   at 
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:64)
   at 
com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
   at 
com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(JsonDeserializationVisitor.java:80)
   at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:101)
   at 
com.google.gson.JsonDeserializationCon

RE: master not perfect:(

[Abhinav Roy]

I faced the same issue, then I logged on to the xenserver host and deleted the 
tags, restarted the MS but even after that i could see these errors. Finally I 
rebooted the Xen Host and after that the error was not seen. Filed a bug for 
the same, https://issues.apache.org/jira/browse/CLOUDSTACK-3377

Thanks and regards,
Abhinav
-Original Message-
From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com] 
Sent: Friday, July 05, 2013 2:56 PM
To: dev@cloudstack.apache.org
Subject: master not perfect:(

H,

I get a repetition of the following sequence of logging when running master. 
Anybody knows what happened?

INFO  [agent.manager.AgentManagerImpl] (AgentManager-Handler-11:) Connection 
from /127.0.0.1 closed but no cleanup was done.
WARN  [utils.nio.Link] (AgentManager-Selector:) SSL: Fail to find the generated 
keystore. Loading fail-safe one to continue.
ERROR [agent.transport.Request] (AgentManager-Handler-13:) Caught problem with 
[{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicNetmask":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","privateIpAddress":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","privateNetmask":"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask":"255.255.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":"NfsSecondaryStorageResource","contextMap":{},"wait":0}}]
com.google.gson.JsonParseException: The JsonDeserializer 
com.cloud.agent.transport.ArrayTypeAdaptor@7db106d failed to deserialize json 
object 
[{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicNetmask":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","privateIpAddress":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","privateNetmask":"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask":"255.255.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":"NfsSecondaryStorageResource","contextMap":{},"wait":0}}]
 given the type class [Lcom.cloud.agent.api.Command;
   at 
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:64)
   at 
com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
   at 
com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(JsonDeserializationVisitor.java:80)
   at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:101)
   at 
com.google.gson.JsonDeserializationContextDefault.fromJsonArray(JsonDeserializationContextDefault.java:67)
   at 
com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:52)
   at com.google.gson.Gson.fromJson(Gson.java:551)
   at com.google.gson.Gson.fromJson(Gson.java:498)
   at com.cloud.agent.transport.Request.getCommands(Request.java:235)
   at 
com.cloud.agent.manager.AgentManagerImpl$AgentHandler.processRequest(AgentManagerImpl.java:1196)
   at 
com.cloud.agent.manager.AgentManagerImpl$AgentHandler.doTask(AgentManagerImpl.java:1349)
   at 
com.cloud.agent.manager.ClusteredAgentManagerImpl$ClusteredAgentHandler.doTask(ClusteredAgentManagerImpl.java:659)
   at com.cloud.utils.nio.Task.run(Task.java:83)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source) Caused by: 
com.cloud.utils.exception.CloudRuntimeException: can't find 
StartupSecondaryStorageCommand
   at 
com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:77)
   at 
com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:37)
   at 
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:51)
   ... 15 more
WARN  [utils.nio.Task] (AgentManager-Handler-13:) Caught the following 
exception but pushing on
com.google.gson.JsonParseException: The JsonDeserializer 
com.cloud.agent.transport.ArrayTypeAdaptor@7db106d failed to deserialize json 
object 
[{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicNetmask":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","privateIpAddress":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","privateNetmask":"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask":"255.255.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":"NfsSecondaryStorageResource","contextMap":{},"wait":0}}]
 give

Re: master not perfect:(

[Prasanna Santhanam]

On Fri, Jul 05, 2013 at 09:26:11AM +, Daan Hoogland wrote:
> H,
> 
> I get a repetition of the following sequence of logging when running
> master. Anybody knows what happened?

Try the steps here: http://markmail.org/message/ranl2l3pzq5qnzd2
> 
-- 
Prasanna.,

RE: master not perfect:(

[Hugo Trippaers]

Hey guys,

Did you use the latest systemvm.iso on the systemvm? This error might occur 
when the classes on the secondary storage vm are out of sync with the classes 
on the management server. 

If you are running from a maven build make sure that the systemvm profile is 
enabled to generate the systemvm.iso and that the file is properly 
uploaded/copied.

Cheers,


Hugo

> -Original Message-
> From: Abhinav Roy [mailto:abhinav@citrix.com]
> Sent: Friday, July 05, 2013 11:44 AM
> To: dev@cloudstack.apache.org
> Subject: RE: master not perfect:(
> 
> I faced the same issue, then I logged on to the xenserver host and deleted
> the tags, restarted the MS but even after that i could see these errors. 
> Finally
> I rebooted the Xen Host and after that the error was not seen. Filed a bug for
> the same, https://issues.apache.org/jira/browse/CLOUDSTACK-3377
> 
> Thanks and regards,
> Abhinav
> -Original Message-
> From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com]
> Sent: Friday, July 05, 2013 2:56 PM
> To: dev@cloudstack.apache.org
> Subject: master not perfect:(
> 
> H,
> 
> I get a repetition of the following sequence of logging when running master.
> Anybody knows what happened?
> 
> INFO  [agent.manager.AgentManagerImpl] (AgentManager-Handler-11:)
> Connection from /127.0.0.1 closed but no cleanup was done.
> WARN  [utils.nio.Link] (AgentManager-Selector:) SSL: Fail to find the
> generated keystore. Loading fail-safe one to continue.
> ERROR [agent.transport.Request] (AgentManager-Handler-13:) Caught
> problem with
> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCe
> nter":"1","pod":"1","guid":"s-1-VM-
> NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-
> SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicNetmas
> k":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","privateIpAddr
> ess":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","privateNetma
> sk":"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask":"2
> 55.255.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":"N
> fsSecondaryStorageResource","contextMap":{},"wait":0}}]
> com.google.gson.JsonParseException: The JsonDeserializer
> com.cloud.agent.transport.ArrayTypeAdaptor@7db106d failed to deserialize
> json object
> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCe
> nter":"1","pod":"1","guid":"s-1-VM-
> NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-
> SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicNetmas
> k":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","privateIpAddr
> ess":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","privateNetma
> sk":"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask":"2
> 55.255.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":"N
> fsSecondaryStorageResource","contextMap":{},"wait":0}}] given the type
> class [Lcom.cloud.agent.api.Command;
>at
> com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserial
> izerExceptionWrapper.java:64)
>at
> com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonD
> eserializationVisitor.java:92)
>at
> com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(JsonDe
> serializationVisitor.java:80)
>at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:101)
>at
> com.google.gson.JsonDeserializationContextDefault.fromJsonArray(JsonDes
> erializationContextDefault.java:67)
>at
> com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserial
> izationContextDefault.java:52)
>at com.google.gson.Gson.fromJson(Gson.java:551)
>at com.google.gson.Gson.fromJson(Gson.java:498)
>at com.cloud.agent.transport.Request.getCommands(Request.java:235)
>at
> com.cloud.agent.manager.AgentManagerImpl$AgentHandler.processReque
> st(AgentManagerImpl.java:1196)
>at
> com.cloud.agent.manager.AgentManagerImpl$AgentHandler.doTask(Agent
> ManagerImpl.java:1349)
>at
> com.cloud.agent.manager.ClusteredAgentManagerImpl$ClusteredAgentHan
> dler.doTask(ClusteredAgentManagerImpl.java:659)
>at com.cloud.utils.nio.Task.run(Task.java:83)
>at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
> Source)
>at java.lang.Thread.run(Unknown Source) Caused by:
> com.cloud.utils.exception.CloudRuntimeException: can't find
> StartupSecondaryStorageCommand
>at
> com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor
> .java:77)
>at
> com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor
> .java:37)
>at
> com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserial
> izerExceptionWrapper.java:51)
>... 15 more
> WARN  [utils.nio.Task] (AgentManager-Handler-13:) Caught the following
> exc

RE: master not perfect:(

[Rajesh Battala]

Hi Daan,
Please build the systemvm.iso and remove the tags on xenserver host which will 
copy the new generated systemvm.iso. 
Newly built systemvm.iso will resolve this issue.

Thanks
Rajesh Battala


> -Original Message-
> From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com]
> Sent: Friday, July 5, 2013 2:56 PM
> To: dev@cloudstack.apache.org
> Subject: master not perfect:(
> 
> H,
> 
> I get a repetition of the following sequence of logging when running master.
> Anybody knows what happened?
> 
> INFO  [agent.manager.AgentManagerImpl] (AgentManager-Handler-11:)
> Connection from /127.0.0.1 closed but no cleanup was done.
> WARN  [utils.nio.Link] (AgentManager-Selector:) SSL: Fail to find the
> generated keystore. Loading fail-safe one to continue.
> ERROR [agent.transport.Request] (AgentManager-Handler-13:) Caught
> problem with
> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCen
> ter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-
> 1-VM","version":"4.2.0-
> SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicNetmask
> ":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","privateIpAddres
> s":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","privateNetmask"
> :"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask":"255.2
> 55.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":"NfsSec
> ondaryStorageResource","contextMap":{},"wait":0}}]
> com.google.gson.JsonParseException: The JsonDeserializer
> com.cloud.agent.transport.ArrayTypeAdaptor@7db106d failed to deserialize
> json object
> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCen
> ter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-
> 1-VM","version":"4.2.0-
> SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicNetmask
> ":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","privateIpAddres
> s":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","privateNetmask"
> :"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask":"255.2
> 55.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":"NfsSec
> ondaryStorageResource","contextMap":{},"wait":0}}] given the type class
> [Lcom.cloud.agent.api.Command;
>at
> com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeseriali
> zerExceptionWrapper.java:64)
>at
> com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDe
> serializationVisitor.java:92)
>at
> com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(JsonDes
> erializationVisitor.java:80)
>at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:101)
>at
> com.google.gson.JsonDeserializationContextDefault.fromJsonArray(JsonDeser
> ializationContextDefault.java:67)
>at
> com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeseriali
> zationContextDefault.java:52)
>at com.google.gson.Gson.fromJson(Gson.java:551)
>at com.google.gson.Gson.fromJson(Gson.java:498)
>at com.cloud.agent.transport.Request.getCommands(Request.java:235)
>at
> com.cloud.agent.manager.AgentManagerImpl$AgentHandler.processRequest
> (AgentManagerImpl.java:1196)
>at
> com.cloud.agent.manager.AgentManagerImpl$AgentHandler.doTask(AgentM
> anagerImpl.java:1349)
>at
> com.cloud.agent.manager.ClusteredAgentManagerImpl$ClusteredAgentHand
> ler.doTask(ClusteredAgentManagerImpl.java:659)
>at com.cloud.utils.nio.Task.run(Task.java:83)
>at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
> Source)
>at java.lang.Thread.run(Unknown Source) Caused by:
> com.cloud.utils.exception.CloudRuntimeException: can't find
> StartupSecondaryStorageCommand
>at
> com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.j
> ava:77)
>at
> com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.j
> ava:37)
>at
> com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeseriali
> zerExceptionWrapper.java:51)
>... 15 more
> WARN  [utils.nio.Task] (AgentManager-Handler-13:) Caught the following
> exception but pushing on
> com.google.gson.JsonParseException: The JsonDeserializer
> com.cloud.agent.transport.ArrayTypeAdaptor@7db106d failed to deserialize
> json object
> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCen
> ter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-
> 1-VM","version":"4.2.0-
> SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicNetmask
> ":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","privateIpAddres
> s":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","privateNetmask"
> :"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask":"255.2
> 55.255.0","storageMacAddress":"06:ad:58:00:00:08","resou

RE: master not perfect:(

[Likitha Shetty]

In my case the discussed steps didn't resolve the issue (removing all the tags 
from the host , cleaning up systemvm.iso from the codebase , ensuring the 
systemvm profile is enabled during maven build and also ensuring the host has 
the newly generated systemvm.iso).
Only once I rebooted the host was the issue resolved.

Thanks,
Likitha

>-Original Message-
>From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com]
>Sent: Friday, July 05, 2013 3:23 PM
>To: dev@cloudstack.apache.org
>Subject: RE: master not perfect:(
>
>Hey guys,
>
>Did you use the latest systemvm.iso on the systemvm? This error might occur
>when the classes on the secondary storage vm are out of sync with the classes
>on the management server.
>
>If you are running from a maven build make sure that the systemvm profile is
>enabled to generate the systemvm.iso and that the file is properly
>uploaded/copied.
>
>Cheers,
>
>
>Hugo
>
>> -Original Message-
>> From: Abhinav Roy [mailto:abhinav@citrix.com]
>> Sent: Friday, July 05, 2013 11:44 AM
>> To: dev@cloudstack.apache.org
>> Subject: RE: master not perfect:(
>>
>> I faced the same issue, then I logged on to the xenserver host and
>> deleted the tags, restarted the MS but even after that i could see
>> these errors. Finally I rebooted the Xen Host and after that the error
>> was not seen. Filed a bug for the same,
>> https://issues.apache.org/jira/browse/CLOUDSTACK-3377
>>
>> Thanks and regards,
>> Abhinav
>> -Original Message-
>> From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com]
>> Sent: Friday, July 05, 2013 2:56 PM
>> To: dev@cloudstack.apache.org
>> Subject: master not perfect:(
>>
>> H,
>>
>> I get a repetition of the following sequence of logging when running master.
>> Anybody knows what happened?
>>
>> INFO  [agent.manager.AgentManagerImpl] (AgentManager-Handler-11:)
>> Connection from /127.0.0.1 closed but no cleanup was done.
>> WARN  [utils.nio.Link] (AgentManager-Selector:) SSL: Fail to find the
>> generated keystore. Loading fail-safe one to continue.
>> ERROR [agent.transport.Request] (AgentManager-Handler-13:) Caught
>> problem with
>> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCe
>> nter":"1","pod":"1","guid":"s-1-VM-
>> NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-
>> SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicNetma
>> s
>> k":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","privateIp
>> Addr
>> ess":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","privateNe
>> tma
>> sk":"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask"
>> :"2
>> 55.255.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":"
>> N fsSecondaryStorageResource","contextMap":{},"wait":0}}]
>> com.google.gson.JsonParseException: The JsonDeserializer
>> com.cloud.agent.transport.ArrayTypeAdaptor@7db106d failed to
>> deserialize json object
>> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCe
>> nter":"1","pod":"1","guid":"s-1-VM-
>> NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-
>> SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicNetma
>> s
>> k":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","privateIp
>> Addr
>> ess":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","privateNe
>> tma
>> sk":"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask"
>> :"2
>> 55.255.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":"
>> N fsSecondaryStorageResource","contextMap":{},"wait":0}}] given the
>> type class [Lcom.cloud.agent.api.Command;
>>at
>> com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeser
>> ial
>> izerExceptionWrapper.java:64)
>>at
>> com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(Js
>> onD
>> eserializationVisitor.java:92)
>>at
>> com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(Jso
>> nDe
>> serializationVisitor.java:80)
>>at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:101)
>>at
>> com.google.gson.JsonDeserializationContextDefault.fromJsonArray(JsonDe
>> s
>> erializationContextDefault.java:67)
>>at
>> com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDese
>> rial
>> izationContextDefault.java:52)
>>at com.google.gson.Gson.fromJson(Gson.java:551)
>>at com.google.gson.Gson.fromJson(Gson.java:498)
>>at com.cloud.agent.transport.Request.getCommands(Request.java:235)
>>at
>> com.cloud.agent.manager.AgentManagerImpl$AgentHandler.processReque
>> st(AgentManagerImpl.java:1196)
>>at
>> com.cloud.agent.manager.AgentManagerImpl$AgentHandler.doTask(Agent
>> ManagerImpl.java:1349)
>>at
>> com.cloud.agent.manager.ClusteredAgentManagerImpl$ClusteredAgentHan
>> dler.doTask(ClusteredAgentManagerImpl.java:659)
>>at com.cloud.utils.nio.Task.run(Task.java:83)
>>at java.util.concurrent.ThreadPoolExecutor.r

RE: master not perfect:(

[Rajesh Battala]

After the new systemvm.iso is generated and tags/systemvm.iso are removed on 
xenserver host , when mgmt. server starts, it will copy the new systemvm.iso to 
the Host.
Then the issue will be resolved. 

> -Original Message-
> From: Likitha Shetty [mailto:likitha.she...@citrix.com]
> Sent: Friday, July 5, 2013 3:38 PM
> To: dev@cloudstack.apache.org
> Subject: RE: master not perfect:(
> 
> In my case the discussed steps didn't resolve the issue (removing all the tags
> from the host , cleaning up systemvm.iso from the codebase , ensuring the
> systemvm profile is enabled during maven build and also ensuring the host
> has the newly generated systemvm.iso).
> Only once I rebooted the host was the issue resolved.
> 
> Thanks,
> Likitha
> 
> >-Original Message-
> >From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com]
> >Sent: Friday, July 05, 2013 3:23 PM
> >To: dev@cloudstack.apache.org
> >Subject: RE: master not perfect:(
> >
> >Hey guys,
> >
> >Did you use the latest systemvm.iso on the systemvm? This error might
> >occur when the classes on the secondary storage vm are out of sync with
> >the classes on the management server.
> >
> >If you are running from a maven build make sure that the systemvm
> >profile is enabled to generate the systemvm.iso and that the file is
> >properly uploaded/copied.
> >
> >Cheers,
> >
> >
> >Hugo
> >
> >> -Original Message-
> >> From: Abhinav Roy [mailto:abhinav@citrix.com]
> >> Sent: Friday, July 05, 2013 11:44 AM
> >> To: dev@cloudstack.apache.org
> >> Subject: RE: master not perfect:(
> >>
> >> I faced the same issue, then I logged on to the xenserver host and
> >> deleted the tags, restarted the MS but even after that i could see
> >> these errors. Finally I rebooted the Xen Host and after that the
> >> error was not seen. Filed a bug for the same,
> >> https://issues.apache.org/jira/browse/CLOUDSTACK-3377
> >>
> >> Thanks and regards,
> >> Abhinav
> >> -Original Message-
> >> From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com]
> >> Sent: Friday, July 05, 2013 2:56 PM
> >> To: dev@cloudstack.apache.org
> >> Subject: master not perfect:(
> >>
> >> H,
> >>
> >> I get a repetition of the following sequence of logging when running
> master.
> >> Anybody knows what happened?
> >>
> >> INFO  [agent.manager.AgentManagerImpl] (AgentManager-Handler-11:)
> >> Connection from /127.0.0.1 closed but no cleanup was done.
> >> WARN  [utils.nio.Link] (AgentManager-Selector:) SSL: Fail to find the
> >> generated keystore. Loading fail-safe one to continue.
> >> ERROR [agent.transport.Request] (AgentManager-Handler-13:) Caught
> >> problem with
> >>
> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCe
> >> nter":"1","pod":"1","guid":"s-1-VM-
> >> NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-
> >> SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicNetm
> >> a
> >> s
> >> k":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","privateI
> >> p
> >> Addr
> >> ess":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","privateN
> >> e
> >> tma
> >> sk":"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask"
> >> :"2
> >> 55.255.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":"
> >> N fsSecondaryStorageResource","contextMap":{},"wait":0}}]
> >> com.google.gson.JsonParseException: The JsonDeserializer
> >> com.cloud.agent.transport.ArrayTypeAdaptor@7db106d failed to
> >> deserialize json object
> >>
> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCe
> >> nter":"1","pod":"1","guid":"s-1-VM-
> >> NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-
> >> SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicNetm
> >> a
> >> s
> >> k":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","privateI
> >> p
> >> Addr
> >> ess":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","privateN
> >> e
> >> tma
> >> sk":"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask"
> >> :"2
> >> 55.255.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":"
> >> N fsSecondaryStorageResource","contextMap":{},"wait":0}}] given the
> >> type class [Lcom.cloud.agent.api.Command;
> >>at
> >> com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDese
> >> r
> >> ial
> >> izerExceptionWrapper.java:64)
> >>at
> >> com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(J
> >> s
> >> onD
> >> eserializationVisitor.java:92)
> >>at
> >> com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(Js
> >> o
> >> nDe
> >> serializationVisitor.java:80)
> >>at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:101)
> >>at
> >> com.google.gson.JsonDeserializationContextDefault.fromJsonArray(JsonD
> >> e
> >> s
> >> erializationContextDefault.java:67)
> >>at
> >> com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDes
> >> e
> >> rial
> >> iza

Re: master not perfect:(

[Nitin Mehta]

Shouldn't we have a better mechanism of pushing systemvm.iso onto XS ? Why
does it have to be manually done by clearing the tags ?

Thanks,
-Nitin

On 05/07/13 3:43 PM, "Rajesh Battala"  wrote:

>After the new systemvm.iso is generated and tags/systemvm.iso are removed
>on xenserver host , when mgmt. server starts, it will copy the new
>systemvm.iso to the Host.
>Then the issue will be resolved.
>
>> -Original Message-
>> From: Likitha Shetty [mailto:likitha.she...@citrix.com]
>> Sent: Friday, July 5, 2013 3:38 PM
>> To: dev@cloudstack.apache.org
>> Subject: RE: master not perfect:(
>> 
>> In my case the discussed steps didn't resolve the issue (removing all
>>the tags
>> from the host , cleaning up systemvm.iso from the codebase , ensuring
>>the
>> systemvm profile is enabled during maven build and also ensuring the
>>host
>> has the newly generated systemvm.iso).
>> Only once I rebooted the host was the issue resolved.
>> 
>> Thanks,
>> Likitha
>> 
>> >-Original Message-
>> >From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com]
>> >Sent: Friday, July 05, 2013 3:23 PM
>> >To: dev@cloudstack.apache.org
>> >Subject: RE: master not perfect:(
>> >
>> >Hey guys,
>> >
>> >Did you use the latest systemvm.iso on the systemvm? This error might
>> >occur when the classes on the secondary storage vm are out of sync with
>> >the classes on the management server.
>> >
>> >If you are running from a maven build make sure that the systemvm
>> >profile is enabled to generate the systemvm.iso and that the file is
>> >properly uploaded/copied.
>> >
>> >Cheers,
>> >
>> >
>> >Hugo
>> >
>> >> -Original Message-
>> >> From: Abhinav Roy [mailto:abhinav@citrix.com]
>> >> Sent: Friday, July 05, 2013 11:44 AM
>> >> To: dev@cloudstack.apache.org
>> >> Subject: RE: master not perfect:(
>> >>
>> >> I faced the same issue, then I logged on to the xenserver host and
>> >> deleted the tags, restarted the MS but even after that i could see
>> >> these errors. Finally I rebooted the Xen Host and after that the
>> >> error was not seen. Filed a bug for the same,
>> >> https://issues.apache.org/jira/browse/CLOUDSTACK-3377
>> >>
>> >> Thanks and regards,
>> >> Abhinav
>> >> -Original Message-
>> >> From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com]
>> >> Sent: Friday, July 05, 2013 2:56 PM
>> >> To: dev@cloudstack.apache.org
>> >> Subject: master not perfect:(
>> >>
>> >> H,
>> >>
>> >> I get a repetition of the following sequence of logging when running
>> master.
>> >> Anybody knows what happened?
>> >>
>> >> INFO  [agent.manager.AgentManagerImpl] (AgentManager-Handler-11:)
>> >> Connection from /127.0.0.1 closed but no cleanup was done.
>> >> WARN  [utils.nio.Link] (AgentManager-Selector:) SSL: Fail to find the
>> >> generated keystore. Loading fail-safe one to continue.
>> >> ERROR [agent.transport.Request] (AgentManager-Handler-13:) Caught
>> >> problem with
>> >>
>> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCe
>> >> nter":"1","pod":"1","guid":"s-1-VM-
>> >> NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-
>> >> SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicNetm
>> >> a
>> >> s
>> >> k":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","privateI
>> >> p
>> >> Addr
>> >> ess":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","privateN
>> >> e
>> >> tma
>> >> 
>>sk":"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask"
>> >> :"2
>> >> 
>>55.255.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":"
>> >> N fsSecondaryStorageResource","contextMap":{},"wait":0}}]
>> >> com.google.gson.JsonParseException: The JsonDeserializer
>> >> com.cloud.agent.transport.ArrayTypeAdaptor@7db106d failed to
>> >> deserialize json object
>> >>
>> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCe
>> >> nter":"1","pod":"1","guid":"s-1-VM-
>> >> NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-
>> >> SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicNetm
>> >> a
>> >> s
>> >> k":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","privateI
>> >> p
>> >> Addr
>> >> ess":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","privateN
>> >> e
>> >> tma
>> >> 
>>sk":"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask"
>> >> :"2
>> >> 
>>55.255.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":"
>> >> N fsSecondaryStorageResource","contextMap":{},"wait":0}}] given the
>> >> type class [Lcom.cloud.agent.api.Command;
>> >>at
>> >> com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDese
>> >> r
>> >> ial
>> >> izerExceptionWrapper.java:64)
>> >>at
>> >> com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(J
>> >> s
>> >> onD
>> >> eserializationVisitor.java:92)
>> >>at
>> >> com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(Js
>> >> o
>> >> nDe
>> >> serializationVisitor.java:80)
>> >

Re: any feedback of upgrading cloudstack from 3.0.2 to 4.1 with xenserver 6.0.2 hosts

[France]

Hi,

i suggest, you send only to one mailing list at a time. :-)
I've sent a similar question before our upgrade, but didn't get a 
response, so I understand your position.


We have recently upgraded 3.0.2 to 4.1 and all hotfixes on XenServer to 
date for 6.0.2.
Install went with some problems, but mainly because lack of accurate 
documentation.

Here is a bug submitted for that:
https://issues.apache.org/jira/browse/CLOUDSTACK-3138

When upgrading XenServers, just be sure to unmanage cluster or stop 
Cloudstack, so it won't select another master.
Also backup Cloudstack server before upgrade, so there will be a 
downgrade path if it fails.

Upgrade cloudstack with it's VM's first, then XenServers.

Good luck. :-)

Regards,
F.

System works otherwise.

On 4/7/13 11:55 PM, William Jiang wrote:

Hi,
We have a plan to upgrade  cloudstack 3.0.2 to 4.1, we use xenserver 6.0.2 as 
host servers.
Did anyone have run the same upgrade path? Any  issues or comments will be 
great appreciated.

For xenserver 6.0.2(with XS602E001 and XS602E002 updates), can we keep this 
version or it's better  upgrade to xenserver 6.1.

Thanks,
William
This e-mail may be privileged and/or confidential, and the sender does not 
waive any related rights and obligations. Any distribution, use or copying of 
this e-mail or the information it contains by other than an intended recipient 
is unauthorized. If you received this e-mail in error, please advise me (by 
return e-mail or otherwise) immediately. Ce courrier électronique est 
confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations 
qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des 
renseignements qu'il contient par une personne autre que le (les) 
destinataire(s) désigné(s) est interdite. Si vous recevez ce courrier 
électronique par erreur, veuillez m'en aviser immédiatement, par retour de 
courrier électronique ou par un autre moyen.

Review Request 12277: Add VHDX image support

[Donal Lafferty]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/12277/
---

Review request for cloudstack and edison su.


Repository: cloudstack-git


Description
---

Add VHDX image support, which is missing from DiskFormat class, revised 
ImageFormat interface, StorageManager implementation, and the application 
component spec.

NB:  applicationContext.xml.in can only be checked at runtime.  A non-Hyper-V 
user should verify that it does not break anything.


Diffs
-

  client/tomcatconf/applicationContext.xml.in 
14255c1e7a50719757ffa4f3d6f27eaeacfde917 
  
engine/api/src/org/apache/cloudstack/engine/subsystem/api/storage/disktype/DiskFormat.java
 6be7a6bb49eb534b56cb9da9c88da5ffb7d00fa4 
  
engine/api/src/org/apache/cloudstack/engine/subsystem/api/storage/disktype/VHDX.java
 PRE-CREATION 
  engine/storage/src/org/apache/cloudstack/storage/image/format/VHDX.java 
PRE-CREATION 
  server/src/com/cloud/storage/StorageManagerImpl.java 
d9ef853a743c1bfbb1e8a3aa911f1f857985b15a 

Diff: https://reviews.apache.org/r/12277/diff/


Testing
---

Compiles and runs when using Hyper-V plugin.

Has not been run in non-Hyper-V scenarios.


Thanks,

Donal Lafferty

Re: [Discuss][CLOUDSTACK-212] Namespace change for ASF

[Dharmesh Kakadia]

Hi,

@Wido good suggestion. Tabs are easy to replace with regex. I am not sure
of trailing whitespace though. Should be able to complete that too by 20th.

@Ryan Thanks for pointing out. I tried to update the version, but version
4.3 doesn't exist yet ;)

Thanks,
Dharmesh


On Fri, Jul 5, 2013 at 1:29 PM, Sebastien Goasguen  wrote:

>
> On Jul 5, 2013, at 1:28 AM, Ryan Lei  wrote:
>
> > Hi, the corresponding CLOUDSTACK-212 is marked as "Improvement," and
> > planned to be fixed in 4.2.0.
> >
> > But since we have passed the feature freeze date, will the namespace
> change
> > be deferred to 4.3.0?
> >
>
> Yes that's the plan, trying to have it reach master asap to be early in
> the 4.3 development cycle.
>
> we will update the bug fix version
>
> >
> ---
> > Yu-Heng (Ryan) Lei, Associate Reasearcher
> > Chunghwa Telecom Laboratories / Cloud Computing Laboratory
> > ryan...@cht.com.tw<
> https://email.cht.com.tw/owa/redir.aspx?C=-wE1FEC3G0SWYpVkiWo8SsDdf3ZqO9AIuAPTzRnFYCUi-z4YljtI_hyVKkNHfn9F1Bn-vUWJnQ4.&URL=mailto%3aryanlei%40cht.com.tw
> >
> > or
> > ryanlei750...@gmail.com
> >
> >
> >
> > On Fri, Jul 5, 2013 at 3:07 AM, Wido den Hollander 
> wrote:
> >
> >> Hi,
> >>
> >>
> >> On 07/04/2013 01:53 PM, Dharmesh Kakadia wrote:
> >>
> >>> Hi,
> >>>
> >>> Since the cloudstack project has moved to ASF, the suggestion is to
> move
> >>> from com.cloud packages to org.apache java packages .(
> >>> https://issues.apache.org/**jira/browse/CLOUDSTACK-212<
> https://issues.apache.org/jira/browse/CLOUDSTACK-212>
> >>> )
> >>>
> >>> As you might be realize, this is pretty big change. And merging this
> >>> changes with a continuously updating master is non-trivial. So, here is
> >>> the
> >>> planned strategy after discussion over IRC. I am starting this thread
> to
> >>> inform and know everyone's opinions.
> >>>
> >>> 1. I will be pushing code with new packages on branch
> "namespacechanges"
> >>> and will notify on this thread as each refactored module is pushed.
> >>>
> >>> 2. There will be a freeze on master branch commits for some time in
> which
> >>> "namespacechanges" will be applied to master. I suggest the date to be
> >>> 20th
> >>> July.
> >>>
> >>>
> >> +1 on doing this, since we have to do it at some point.
> >>
> >> One question though, since this will break a lot of merges, can we also
> do
> >> a whitespace fix?
> >>
> >> We still have a lot of tabs instead of 4 spaces and with a simple find
> and
> >> sed we can fix that.
> >>
> >> Same goes for trailing spaces.
> >>
> >> We could do one (or multiple) commits which address these issues at
> once?
> >>
> >> Wido
> >>
> >>
> >>
> >> 3. All the branch-owner updates their branch for reflect new packages.
> It
> >>> was suggested that branch owners can look into the "namespacechanges"
> >>> branch as it grows and start doing the package changes early, although
> it
> >>> depends on branch-owners.
> >>>
> >>> Thanks,
> >>> Dharmesh
> >>>
> >>>
>
>

RE: master not perfect:(

[Hugo Trippaers]

Heya,

It will be done automagically once you upgrade the version number. The tag 
lists the version number and checks that against the current version you are 
running.

This is probably good for users who only want to update the systemvm once, when 
they upgrade to a new version. For developers who generally work on the same 
version its more troublesome, just like database upgrades. A developer 
typically recompiles regularly and needs the latest version of both database 
and systemvm.

A solution could be to ignore the tag when developer is set to true in the 
global config. Any better ideas?

Cheers,

Hugo

> -Original Message-
> From: Nitin Mehta [mailto:nitin.me...@citrix.com]
> Sent: Friday, July 05, 2013 12:48 PM
> To: dev@cloudstack.apache.org
> Subject: Re: master not perfect:(
> 
> Shouldn't we have a better mechanism of pushing systemvm.iso onto XS ?
> Why does it have to be manually done by clearing the tags ?
> 
> Thanks,
> -Nitin
> 
> On 05/07/13 3:43 PM, "Rajesh Battala"  wrote:
> 
> >After the new systemvm.iso is generated and tags/systemvm.iso are
> >removed on xenserver host , when mgmt. server starts, it will copy the
> >new systemvm.iso to the Host.
> >Then the issue will be resolved.
> >
> >> -Original Message-
> >> From: Likitha Shetty [mailto:likitha.she...@citrix.com]
> >> Sent: Friday, July 5, 2013 3:38 PM
> >> To: dev@cloudstack.apache.org
> >> Subject: RE: master not perfect:(
> >>
> >> In my case the discussed steps didn't resolve the issue (removing all
> >>the tags  from the host , cleaning up systemvm.iso from the codebase ,
> >>ensuring the  systemvm profile is enabled during maven build and also
> >>ensuring the host  has the newly generated systemvm.iso).
> >> Only once I rebooted the host was the issue resolved.
> >>
> >> Thanks,
> >> Likitha
> >>
> >> >-Original Message-
> >> >From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com]
> >> >Sent: Friday, July 05, 2013 3:23 PM
> >> >To: dev@cloudstack.apache.org
> >> >Subject: RE: master not perfect:(
> >> >
> >> >Hey guys,
> >> >
> >> >Did you use the latest systemvm.iso on the systemvm? This error
> >> >might occur when the classes on the secondary storage vm are out of
> >> >sync with the classes on the management server.
> >> >
> >> >If you are running from a maven build make sure that the systemvm
> >> >profile is enabled to generate the systemvm.iso and that the file is
> >> >properly uploaded/copied.
> >> >
> >> >Cheers,
> >> >
> >> >
> >> >Hugo
> >> >
> >> >> -Original Message-
> >> >> From: Abhinav Roy [mailto:abhinav@citrix.com]
> >> >> Sent: Friday, July 05, 2013 11:44 AM
> >> >> To: dev@cloudstack.apache.org
> >> >> Subject: RE: master not perfect:(
> >> >>
> >> >> I faced the same issue, then I logged on to the xenserver host and
> >> >> deleted the tags, restarted the MS but even after that i could see
> >> >> these errors. Finally I rebooted the Xen Host and after that the
> >> >> error was not seen. Filed a bug for the same,
> >> >> https://issues.apache.org/jira/browse/CLOUDSTACK-3377
> >> >>
> >> >> Thanks and regards,
> >> >> Abhinav
> >> >> -Original Message-
> >> >> From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com]
> >> >> Sent: Friday, July 05, 2013 2:56 PM
> >> >> To: dev@cloudstack.apache.org
> >> >> Subject: master not perfect:(
> >> >>
> >> >> H,
> >> >>
> >> >> I get a repetition of the following sequence of logging when
> >> >> running
> >> master.
> >> >> Anybody knows what happened?
> >> >>
> >> >> INFO  [agent.manager.AgentManagerImpl] (AgentManager-Handler-
> 11:)
> >> >> Connection from /127.0.0.1 closed but no cleanup was done.
> >> >> WARN  [utils.nio.Link] (AgentManager-Selector:) SSL: Fail to find
> >> >> the generated keystore. Loading fail-safe one to continue.
> >> >> ERROR [agent.transport.Request] (AgentManager-Handler-13:) Caught
> >> >> problem with
> >> >>
> >>
> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCe
> >> >> nter":"1","pod":"1","guid":"s-1-VM-
> >> >> NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-
> >> >> SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicN
> >> >> etm
> >> >> a
> >> >> s
> >> >> k":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","priva
> >> >> teI
> >> >> p
> >> >> Addr
> >> >> ess":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","priva
> >> >> teN
> >> >> e
> >> >> tma
> >> >>
> >>sk":"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask"
> >> >> :"2
> >> >>
> >>55.255.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":
> "
> >> >> N fsSecondaryStorageResource","contextMap":{},"wait":0}}]
> >> >> com.google.gson.JsonParseException: The JsonDeserializer
> >> >> com.cloud.agent.transport.ArrayTypeAdaptor@7db106d failed to
> >> >> deserialize json object
> >> >>
> >>
> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCe
> >> >> nter":"1","pod":"1","guid":"s-1-VM-
> >> >> NfsSecondaryStorageR

Re: master not perfect:(

[Nitin Mehta]

Good solution Hugo.
Can we also not embed md5sum in the tag ? In that case it would push the
iso if the md5sum doesn't match
Will it break more things than it will solve :) ?

Thanks,
-Nitin

On 05/07/13 5:45 PM, "Hugo Trippaers" 
wrote:

>Heya,
>
>It will be done automagically once you upgrade the version number. The
>tag lists the version number and checks that against the current version
>you are running.
>
>This is probably good for users who only want to update the systemvm
>once, when they upgrade to a new version. For developers who generally
>work on the same version its more troublesome, just like database
>upgrades. A developer typically recompiles regularly and needs the latest
>version of both database and systemvm.
>
>A solution could be to ignore the tag when developer is set to true in
>the global config. Any better ideas?
>
>Cheers,
>
>Hugo
>
>> -Original Message-
>> From: Nitin Mehta [mailto:nitin.me...@citrix.com]
>> Sent: Friday, July 05, 2013 12:48 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: master not perfect:(
>> 
>> Shouldn't we have a better mechanism of pushing systemvm.iso onto XS ?
>> Why does it have to be manually done by clearing the tags ?
>> 
>> Thanks,
>> -Nitin
>> 
>> On 05/07/13 3:43 PM, "Rajesh Battala"  wrote:
>> 
>> >After the new systemvm.iso is generated and tags/systemvm.iso are
>> >removed on xenserver host , when mgmt. server starts, it will copy the
>> >new systemvm.iso to the Host.
>> >Then the issue will be resolved.
>> >
>> >> -Original Message-
>> >> From: Likitha Shetty [mailto:likitha.she...@citrix.com]
>> >> Sent: Friday, July 5, 2013 3:38 PM
>> >> To: dev@cloudstack.apache.org
>> >> Subject: RE: master not perfect:(
>> >>
>> >> In my case the discussed steps didn't resolve the issue (removing all
>> >>the tags  from the host , cleaning up systemvm.iso from the codebase ,
>> >>ensuring the  systemvm profile is enabled during maven build and also
>> >>ensuring the host  has the newly generated systemvm.iso).
>> >> Only once I rebooted the host was the issue resolved.
>> >>
>> >> Thanks,
>> >> Likitha
>> >>
>> >> >-Original Message-
>> >> >From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com]
>> >> >Sent: Friday, July 05, 2013 3:23 PM
>> >> >To: dev@cloudstack.apache.org
>> >> >Subject: RE: master not perfect:(
>> >> >
>> >> >Hey guys,
>> >> >
>> >> >Did you use the latest systemvm.iso on the systemvm? This error
>> >> >might occur when the classes on the secondary storage vm are out of
>> >> >sync with the classes on the management server.
>> >> >
>> >> >If you are running from a maven build make sure that the systemvm
>> >> >profile is enabled to generate the systemvm.iso and that the file is
>> >> >properly uploaded/copied.
>> >> >
>> >> >Cheers,
>> >> >
>> >> >
>> >> >Hugo
>> >> >
>> >> >> -Original Message-
>> >> >> From: Abhinav Roy [mailto:abhinav@citrix.com]
>> >> >> Sent: Friday, July 05, 2013 11:44 AM
>> >> >> To: dev@cloudstack.apache.org
>> >> >> Subject: RE: master not perfect:(
>> >> >>
>> >> >> I faced the same issue, then I logged on to the xenserver host and
>> >> >> deleted the tags, restarted the MS but even after that i could see
>> >> >> these errors. Finally I rebooted the Xen Host and after that the
>> >> >> error was not seen. Filed a bug for the same,
>> >> >> https://issues.apache.org/jira/browse/CLOUDSTACK-3377
>> >> >>
>> >> >> Thanks and regards,
>> >> >> Abhinav
>> >> >> -Original Message-
>> >> >> From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com]
>> >> >> Sent: Friday, July 05, 2013 2:56 PM
>> >> >> To: dev@cloudstack.apache.org
>> >> >> Subject: master not perfect:(
>> >> >>
>> >> >> H,
>> >> >>
>> >> >> I get a repetition of the following sequence of logging when
>> >> >> running
>> >> master.
>> >> >> Anybody knows what happened?
>> >> >>
>> >> >> INFO  [agent.manager.AgentManagerImpl] (AgentManager-Handler-
>> 11:)
>> >> >> Connection from /127.0.0.1 closed but no cleanup was done.
>> >> >> WARN  [utils.nio.Link] (AgentManager-Selector:) SSL: Fail to find
>> >> >> the generated keystore. Loading fail-safe one to continue.
>> >> >> ERROR [agent.transport.Request] (AgentManager-Handler-13:) Caught
>> >> >> problem with
>> >> >>
>> >>
>> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCe
>> >> >> nter":"1","pod":"1","guid":"s-1-VM-
>> >> >> NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-
>> >> >> SNAPSHOT","iqn":"NoIqn","publicIpAddress":"195.66.90.212","publicN
>> >> >> etm
>> >> >> a
>> >> >> s
>> >> >> k":"255.255.255.224","publicMacAddress":"06:fb:ca:00:00:01","priva
>> >> >> teI
>> >> >> p
>> >> >> Addr
>> >> >> ess":"10.200.23.62","privateMacAddress":"06:ad:58:00:00:08","priva
>> >> >> teN
>> >> >> e
>> >> >> tma
>> >> >>
>> >>sk":"255.255.255.0","storageIpAddress":"10.200.23.62","storageNetmask"
>> >> >> :"2
>> >> >>
>> >>55.255.255.0","storageMacAddress":"06:ad:58:00:00:08","resourceName":
>> "
>> >> >> N fsSecondaryStor

Re: Review Request 12223: Async jobs actions now trigger event bus messages to be published

[Murali Reddy]

On 03/07/13 9:02 PM, "Ryan Dietrich"  wrote:

>
>
>> On July 3, 2013, 9:04 a.m., Murali Reddy wrote:
>> > server/src/com/cloud/async/AsyncJobManagerImpl.java, lines 147-156
>> > 
>>>>
>> >
>> > IMO this is not right. event type in asyn job are used for
>>'action events' which are basically user actions. Since we are just
>>dealing with 'asyn job' events its more appropriate events would be like
>>schedule of a new job, completion of job, status update of job etc.
>>Ofcourse you are adding details like instance/entity type and its UUID,
>>and command type etc which makes this event meaningful any way.
>
>It's the event type OF the command that the async job is performing.
>It's part of the abstract class that you're forced to implement when
>deriving from BaseAsyncCmd!  Not having it would be a mistake,

My concern was this event category becoming redundant of action events. I
would imagine use case for asyn job events, would be to fire an CloudStack
API which is asyn, and instead of polling management server for job status
be able to get the callback when job is done. Since you have already added
the job status (submit/complete/update) as event type for this async job
event category I am fine with the patch you submitted. Applied it on both
master and 4.2.

> I thought you'd comment on the fact that I'm substring-ing it out of
>JSON instead of just creating a new database column within AsyncJobVO.

I guess current approach Is fine. Event type is not primary attribute of
Async Job.

>
>
>> On July 3, 2013, 9:04 a.m., Murali Reddy wrote:
>> > server/src/com/cloud/async/AsyncJobManagerImpl.java, line 161
>> > 
>>>>
>> >
>> > Like mentioned in above comment, it would be appropriate we
>>capture schedule/complete/status update of async job here
>
>No problem.  I'll add an argument to the publish function.  It's called
>in three places.  Once for submit, once for update and once for complete.
> It'll be a simple string argument that will be captured and sent within
>the event description.
>
>
>> On July 3, 2013, 9:04 a.m., Murali Reddy wrote:
>> > server/src/com/cloud/async/AsyncJobManagerImpl.java, line 162
>> > 
>>>>
>> >
>> > any way we have instance id and instance UUID, please use them to
>>form routing key.
>
>But what if we don't?  Are you saying to make getInstanceId /
>getInstanceType abstract, forcing all async commands to implement those
>function?  Right now they have null returning definitions, which makes
>this line of code make sense.

Yeah, I noticed not all commands have implemented, probability need an
effort to clean it up and make the methods abstract. Can you please file a
bug for this?

>
>
>> On July 3, 2013, 9:04 a.m., Murali Reddy wrote:
>> > server/src/com/cloud/async/AsyncJobManagerImpl.java, line 173
>> > 
>>>>
>> >
>> > Internal id's are not exposed. Since UUID is populated in the
>>description that should be enough.
>
>Cool, I'll make that change.
>
>
>- Ryan
>
>
>---
>This is an automatically generated e-mail. To reply, visit:
>https://reviews.apache.org/r/12223/#review22704
>---
>
>
>On July 3, 2013, 2:17 p.m., Ryan Dietrich wrote:
>> 
>> ---
>> This is an automatically generated e-mail. To reply, visit:
>> https://reviews.apache.org/r/12223/
>> ---
>> 
>> (Updated July 3, 2013, 2:17 p.m.)
>> 
>> 
>> Review request for cloudstack, Marcus Sorensen and Murali Reddy.
>> 
>> 
>> Bugs: CLOUDSTACK-3190
>> 
>> 
>> Repository: cloudstack-git
>> 
>> 
>> Description
>> ---
>> 
>> Updated AsyncJobManagerImpl to publish async job events when async jobs
>>are created, updated and completed.
>> I am currently stashing the command event description in the
>>commandInfo structure, and then pulling it back out as needed.
>> I could switch this to make a database change, but that seemed like a
>>more invasive change.
>> 
>> I have further diffs to clean up ActionEvent and AlertEvent as well.
>> 
>> 
>> Diffs
>> -
>> 
>>   api/src/com/cloud/event/EventCategory.java cee6529
>>   server/src/com/cloud/api/ApiServer.java 0cd1d61
>>   server/src/com/cloud/async/AsyncJobManagerImpl.java 0101a8a
>> 
>> Diff: https://reviews.apache.org/r/12223/diff/
>> 
>> 
>> Testing
>> ---
>> 
>> Manual testing only at this point.  I am more than willing to write a
>>python test using marvin, but I'm unsure if marvin has rabbitmq library
>>support or not yet.  Please advise.
>> 
>> 
>> Thanks,
>> 
>> Ryan Dietrich
>> 
>>
>
>

AWS SDK version for object store

[Prasanna Santhanam]

There was another issue I found today with the SDK v1.3.21. It appears
I can't use periods in the name of a bucket. I see an SSL Exception
when this is done [1]. The bug is fixed in the v1.3.22. There are also
couple of other issues fixed related to s3 on the latest version of
the SDK.  Is there any reason not to use the latest stable SDK version
in CloudStack? IOW, why did we choose the v1.3.21?

[1] http://issues.apache.org/jira/browse/CLOUDSTACK-3374

-- 
Prasanna.,


Powered by BigRock.com

[GSOC] Update to document

[Sebastien Goasguen]

Hi guys,

I modified the format of our "report", I moved the proposals to a chapter and 
started a new chapter called "updates".
Each of you should use a section to write a small report/updates on your 
progress so far.

You can see the doc at:
http://jenkins.cloudstack.org/job/docs-4.3-gsoc-guide/lastSuccessfulBuild/artifact/Apache_CloudStack-4.2.0-CloudStack_GSoC_Guide-en-US.pdf

Your respective sections should be self-explanatory when you checkout the code.

We will use this for the mid-summer evaluation that Google wants/needs.

A good example of progress report is from Ian at:

http://imduffy15.blogspot.co.uk

You can include specific things about your project but also things related to 
CloudStack itself, what you are learning (jira, git etc..) and what you 
contributed so far outside your project (e.g Meng gave us the quick install 
guide for 4.1 and Dharmesh is looking at a significant update to the code with 
CLOUDSTACK-212)

Cheers,

-Sebastien

Re: [GSOC] Update to document

[Prasanna Santhanam]

On Fri, Jul 05, 2013 at 09:18:10AM -0400, Sebastien Goasguen wrote:
> Hi guys,
> 
> I modified the format of our "report", I moved the proposals to a
> chapter and started a new chapter called "updates".
> Each of you should use a section to write a small report/updates on
> your progress so far.
> 
> You can see the doc at:
> http://jenkins.cloudstack.org/job/docs-4.3-gsoc-guide/lastSuccessfulBuild/artifact/Apache_CloudStack-4.2.0-CloudStack_GSoC_Guide-en-US.pdf
> 
> Your respective sections should be self-explanatory when you
> checkout the code.
> 
> We will use this for the mid-summer evaluation that Google
> wants/needs.
> 
> A good example of progress report is from Ian at:
> 
> http://imduffy15.blogspot.co.uk
> 
> You can include specific things about your project but also things
> related to CloudStack itself, what you are learning (jira, git
> etc..) and what you contributed so far outside your project (e.g
> Meng gave us the quick install guide for 4.1 and Dharmesh is looking
> at a significant update to the code with CLOUDSTACK-212)
> 

Excellent work so far. Great work all!

-- 
Prasanna.,


Powered by BigRock.com

Re: CloudStack Documentation URL redirection

[Kimihiko Kitase]

Hello, David, Its still redirected to
http://cloudstack.apache.org/docs/ja-JP/index.html..
Non English speaker just wants to go
http://cloudstack.apache.org/docs/en-US/index.html at first.
And if need, they select their language from drop down list.
So can you please simply stop this redirection?

Thanks
Kimi

2013/7/4 Ryan Lei :
> +1 for Taiwan users using zh-TW browsers.
> I would be redirected to the file-not-found page at
> http://cloudstack.apache.org/docs/zh-TW/index.html
> So I would have to bookmark http://cloudstack.apache.org/docs/en-US/. I'm
> used to reading the English documentation, anyway.
>
> ---
> Yu-Heng (Ryan) Lei, Associate Reasearcher
> Chunghwa Telecom Laboratories / Cloud Computing Laboratory
> ryan...@cht.com.tw
> or
> ryanlei750...@gmail.com
>
>
>
> On Wed, Jul 3, 2013 at 5:25 PM, Kimihiko Kitase <
> kimihiko.kit...@citrix.co.jp> wrote:
>
>> Hello
>>
>> Can you please stop redirection of http://cloudstack.apache.org/docs?
>> If I access this site with JA browser, its redirected to
>> http://cloudstack.apache.org/docs/ja-JP/index.html. But its not found.
>> For JA user, http://cloudstack.apache.org/docs/en-US/index.html is OK. If
>> JA User wants to check Japanese doc, we select it from drop down list. I
>> believe other language users are same..
>>
>> Thanks
>> Kimi
>>
>>

Re: CloudStack Documentation URL redirection

[Sebastien Goasguen]

On Jul 5, 2013, at 10:02 AM, Kimihiko Kitase  wrote:

> Hello, David, Its still redirected to
> http://cloudstack.apache.org/docs/ja-JP/index.html..
> Non English speaker just wants to go
> http://cloudstack.apache.org/docs/en-US/index.html at first.
> And if need, they select their language from drop down list.
> So can you please simply stop this redirection?

Kimi, I don't think it's voluntary. 
It seems to be a mix of browser settings and the way the html doc is built. But 
I think David is looking into it. 
Of course it's July 4th week-end, so probably nothing will happen until Monday.


> 
> Thanks
> Kimi
> 
> 2013/7/4 Ryan Lei :
>> +1 for Taiwan users using zh-TW browsers.
>> I would be redirected to the file-not-found page at
>> http://cloudstack.apache.org/docs/zh-TW/index.html
>> So I would have to bookmark http://cloudstack.apache.org/docs/en-US/. I'm
>> used to reading the English documentation, anyway.
>> 
>> ---
>> Yu-Heng (Ryan) Lei, Associate Reasearcher
>> Chunghwa Telecom Laboratories / Cloud Computing Laboratory
>> ryan...@cht.com.tw
>> or
>> ryanlei750...@gmail.com
>> 
>> 
>> 
>> On Wed, Jul 3, 2013 at 5:25 PM, Kimihiko Kitase <
>> kimihiko.kit...@citrix.co.jp> wrote:
>> 
>>> Hello
>>> 
>>> Can you please stop redirection of http://cloudstack.apache.org/docs?
>>> If I access this site with JA browser, its redirected to
>>> http://cloudstack.apache.org/docs/ja-JP/index.html. But its not found.
>>> For JA user, http://cloudstack.apache.org/docs/en-US/index.html is OK. If
>>> JA User wants to check Japanese doc, we select it from drop down list. I
>>> believe other language users are same..
>>> 
>>> Thanks
>>> Kimi
>>> 
>>> 

Re: CloudStack Documentation URL redirection

[Kimihiko Kitase]

Thanks! Its not urgent:)

2013/7/5 Sebastien Goasguen :
>
> On Jul 5, 2013, at 10:02 AM, Kimihiko Kitase  wrote:
>
>> Hello, David, Its still redirected to
>> http://cloudstack.apache.org/docs/ja-JP/index.html..
>> Non English speaker just wants to go
>> http://cloudstack.apache.org/docs/en-US/index.html at first.
>> And if need, they select their language from drop down list.
>> So can you please simply stop this redirection?
>
> Kimi, I don't think it's voluntary.
> It seems to be a mix of browser settings and the way the html doc is built. 
> But I think David is looking into it.
> Of course it's July 4th week-end, so probably nothing will happen until 
> Monday.
>
>
>>
>> Thanks
>> Kimi
>>
>> 2013/7/4 Ryan Lei :
>>> +1 for Taiwan users using zh-TW browsers.
>>> I would be redirected to the file-not-found page at
>>> http://cloudstack.apache.org/docs/zh-TW/index.html
>>> So I would have to bookmark http://cloudstack.apache.org/docs/en-US/. I'm
>>> used to reading the English documentation, anyway.
>>>
>>> ---
>>> Yu-Heng (Ryan) Lei, Associate Reasearcher
>>> Chunghwa Telecom Laboratories / Cloud Computing Laboratory
>>> ryan...@cht.com.tw
>>> or
>>> ryanlei750...@gmail.com
>>>
>>>
>>>
>>> On Wed, Jul 3, 2013 at 5:25 PM, Kimihiko Kitase <
>>> kimihiko.kit...@citrix.co.jp> wrote:
>>>
 Hello

 Can you please stop redirection of http://cloudstack.apache.org/docs?
 If I access this site with JA browser, its redirected to
 http://cloudstack.apache.org/docs/ja-JP/index.html. But its not found.
 For JA user, http://cloudstack.apache.org/docs/en-US/index.html is OK. If
 JA User wants to check Japanese doc, we select it from drop down list. I
 believe other language users are same..

 Thanks
 Kimi


>

Re: [GSOC] Update to document

[Ian Duffy]

@Sebastien - Is it ok to just copy and paste over what I had in that
blog post? (Excluding the opening image and closing paragraph)

On 5 July 2013 14:25, Prasanna Santhanam  wrote:
> On Fri, Jul 05, 2013 at 09:18:10AM -0400, Sebastien Goasguen wrote:
>> Hi guys,
>>
>> I modified the format of our "report", I moved the proposals to a
>> chapter and started a new chapter called "updates".
>> Each of you should use a section to write a small report/updates on
>> your progress so far.
>>
>> You can see the doc at:
>> http://jenkins.cloudstack.org/job/docs-4.3-gsoc-guide/lastSuccessfulBuild/artifact/Apache_CloudStack-4.2.0-CloudStack_GSoC_Guide-en-US.pdf
>>
>> Your respective sections should be self-explanatory when you
>> checkout the code.
>>
>> We will use this for the mid-summer evaluation that Google
>> wants/needs.
>>
>> A good example of progress report is from Ian at:
>>
>> http://imduffy15.blogspot.co.uk
>>
>> You can include specific things about your project but also things
>> related to CloudStack itself, what you are learning (jira, git
>> etc..) and what you contributed so far outside your project (e.g
>> Meng gave us the quick install guide for 4.1 and Dharmesh is looking
>> at a significant update to the code with CLOUDSTACK-212)
>>
>
> Excellent work so far. Great work all!
>
> --
> Prasanna.,
>
> 
> Powered by BigRock.com
>

Re: [GSOC] Update to document

[Sebastien Goasguen]

On Jul 5, 2013, at 10:25 AM, Ian Duffy  wrote:

> @Sebastien - Is it ok to just copy and paste over what I had in that
> blog post? (Excluding the opening image and closing paragraph)
> 

yes no problem, I'd love to see some info on your jenkins setup though :)

and you can add the snapshots too...

> On 5 July 2013 14:25, Prasanna Santhanam  wrote:
>> On Fri, Jul 05, 2013 at 09:18:10AM -0400, Sebastien Goasguen wrote:
>>> Hi guys,
>>> 
>>> I modified the format of our "report", I moved the proposals to a
>>> chapter and started a new chapter called "updates".
>>> Each of you should use a section to write a small report/updates on
>>> your progress so far.
>>> 
>>> You can see the doc at:
>>> http://jenkins.cloudstack.org/job/docs-4.3-gsoc-guide/lastSuccessfulBuild/artifact/Apache_CloudStack-4.2.0-CloudStack_GSoC_Guide-en-US.pdf
>>> 
>>> Your respective sections should be self-explanatory when you
>>> checkout the code.
>>> 
>>> We will use this for the mid-summer evaluation that Google
>>> wants/needs.
>>> 
>>> A good example of progress report is from Ian at:
>>> 
>>> http://imduffy15.blogspot.co.uk
>>> 
>>> You can include specific things about your project but also things
>>> related to CloudStack itself, what you are learning (jira, git
>>> etc..) and what you contributed so far outside your project (e.g
>>> Meng gave us the quick install guide for 4.1 and Dharmesh is looking
>>> at a significant update to the code with CLOUDSTACK-212)
>>> 
>> 
>> Excellent work so far. Great work all!
>> 
>> --
>> Prasanna.,
>> 
>> 
>> Powered by BigRock.com
>> 

Re: [GSOC] Update to document

[Ian Duffy]

Sorry to create two emails in a row...

Just in terms of the Google wants/needs deadline on the 29th, is there
anything you guys, the cloudstack community specifically want to see?

I know Abhi mentioned the creation of a prototype for me in one of the
gtalk conversations we had awhile back. So I'm hoping to have the
plugin I detailed in the blog post completely cleaned up and ready for
review by you guys with full end to end testing by that date. This
would allow me to have the second half of the Google summer of code
term to work on creating a UI to allow admins to easily provision
users and extending the plugin where/if required. As mentioned to
Sebastien during the skype interviews I would *ideally* like to have
the project wrapped up by the end of August, based on the progress so
far this seems possible.

On 5 July 2013 15:25, Ian Duffy  wrote:
> @Sebastien - Is it ok to just copy and paste over what I had in that
> blog post? (Excluding the opening image and closing paragraph)
>
> On 5 July 2013 14:25, Prasanna Santhanam  wrote:
>> On Fri, Jul 05, 2013 at 09:18:10AM -0400, Sebastien Goasguen wrote:
>>> Hi guys,
>>>
>>> I modified the format of our "report", I moved the proposals to a
>>> chapter and started a new chapter called "updates".
>>> Each of you should use a section to write a small report/updates on
>>> your progress so far.
>>>
>>> You can see the doc at:
>>> http://jenkins.cloudstack.org/job/docs-4.3-gsoc-guide/lastSuccessfulBuild/artifact/Apache_CloudStack-4.2.0-CloudStack_GSoC_Guide-en-US.pdf
>>>
>>> Your respective sections should be self-explanatory when you
>>> checkout the code.
>>>
>>> We will use this for the mid-summer evaluation that Google
>>> wants/needs.
>>>
>>> A good example of progress report is from Ian at:
>>>
>>> http://imduffy15.blogspot.co.uk
>>>
>>> You can include specific things about your project but also things
>>> related to CloudStack itself, what you are learning (jira, git
>>> etc..) and what you contributed so far outside your project (e.g
>>> Meng gave us the quick install guide for 4.1 and Dharmesh is looking
>>> at a significant update to the code with CLOUDSTACK-212)
>>>
>>
>> Excellent work so far. Great work all!
>>
>> --
>> Prasanna.,
>>
>> 
>> Powered by BigRock.com
>>

Re: [GSOC] Update to document

[Sebastien Goasguen]

On Jul 5, 2013, at 10:35 AM, Ian Duffy  wrote:

> Sorry to create two emails in a row...
> 
> Just in terms of the Google wants/needs deadline on the 29th, is there
> anything you guys, the cloudstack community specifically want to see?
> 

I am going to check exactly what Google requires, the evaluation will be 
submitted by your mentor: Abhi :)

In general I think a prototype demo and seeing your code committed is really 
what we would like.

So don't be afraid to commit, if you don't want to break the existing setup we 
can created a feature branch for you. But we'd rather see lots of small commits 
than a large chunk at the end.



> I know Abhi mentioned the creation of a prototype for me in one of the
> gtalk conversations we had awhile back. So I'm hoping to have the
> plugin I detailed in the blog post completely cleaned up and ready for
> review by you guys with full end to end testing by that date. This
> would allow me to have the second half of the Google summer of code
> term to work on creating a UI to allow admins to easily provision
> users and extending the plugin where/if required. As mentioned to
> Sebastien during the skype interviews I would *ideally* like to have
> the project wrapped up by the end of August, based on the progress so
> far this seems possible.
> 
> On 5 July 2013 15:25, Ian Duffy  wrote:
>> @Sebastien - Is it ok to just copy and paste over what I had in that
>> blog post? (Excluding the opening image and closing paragraph)
>> 
>> On 5 July 2013 14:25, Prasanna Santhanam  wrote:
>>> On Fri, Jul 05, 2013 at 09:18:10AM -0400, Sebastien Goasguen wrote:
 Hi guys,
 
 I modified the format of our "report", I moved the proposals to a
 chapter and started a new chapter called "updates".
 Each of you should use a section to write a small report/updates on
 your progress so far.
 
 You can see the doc at:
 http://jenkins.cloudstack.org/job/docs-4.3-gsoc-guide/lastSuccessfulBuild/artifact/Apache_CloudStack-4.2.0-CloudStack_GSoC_Guide-en-US.pdf
 
 Your respective sections should be self-explanatory when you
 checkout the code.
 
 We will use this for the mid-summer evaluation that Google
 wants/needs.
 
 A good example of progress report is from Ian at:
 
 http://imduffy15.blogspot.co.uk
 
 You can include specific things about your project but also things
 related to CloudStack itself, what you are learning (jira, git
 etc..) and what you contributed so far outside your project (e.g
 Meng gave us the quick install guide for 4.1 and Dharmesh is looking
 at a significant update to the code with CLOUDSTACK-212)
 
>>> 
>>> Excellent work so far. Great work all!
>>> 
>>> --
>>> Prasanna.,
>>> 
>>> 
>>> Powered by BigRock.com
>>> 

Re: [GSOC] Update to document

[Ian Duffy]

> I'd love to see some info on your jenkins setup though :)

Planning a blog post on the configuration to follow up on the
screencast I did awhile back. I emailed Prasanna earlier in the week,
I'm going to work with him to get my jenkins setup along with some
static analysis with sonar source for the main build on the
buildacloud Jenkins.

On 5 July 2013 15:35, Ian Duffy  wrote:
> Sorry to create two emails in a row...
>
> Just in terms of the Google wants/needs deadline on the 29th, is there
> anything you guys, the cloudstack community specifically want to see?
>
> I know Abhi mentioned the creation of a prototype for me in one of the
> gtalk conversations we had awhile back. So I'm hoping to have the
> plugin I detailed in the blog post completely cleaned up and ready for
> review by you guys with full end to end testing by that date. This
> would allow me to have the second half of the Google summer of code
> term to work on creating a UI to allow admins to easily provision
> users and extending the plugin where/if required. As mentioned to
> Sebastien during the skype interviews I would *ideally* like to have
> the project wrapped up by the end of August, based on the progress so
> far this seems possible.
>
> On 5 July 2013 15:25, Ian Duffy  wrote:
>> @Sebastien - Is it ok to just copy and paste over what I had in that
>> blog post? (Excluding the opening image and closing paragraph)
>>
>> On 5 July 2013 14:25, Prasanna Santhanam  wrote:
>>> On Fri, Jul 05, 2013 at 09:18:10AM -0400, Sebastien Goasguen wrote:
 Hi guys,

 I modified the format of our "report", I moved the proposals to a
 chapter and started a new chapter called "updates".
 Each of you should use a section to write a small report/updates on
 your progress so far.

 You can see the doc at:
 http://jenkins.cloudstack.org/job/docs-4.3-gsoc-guide/lastSuccessfulBuild/artifact/Apache_CloudStack-4.2.0-CloudStack_GSoC_Guide-en-US.pdf

 Your respective sections should be self-explanatory when you
 checkout the code.

 We will use this for the mid-summer evaluation that Google
 wants/needs.

 A good example of progress report is from Ian at:

 http://imduffy15.blogspot.co.uk

 You can include specific things about your project but also things
 related to CloudStack itself, what you are learning (jira, git
 etc..) and what you contributed so far outside your project (e.g
 Meng gave us the quick install guide for 4.1 and Dharmesh is looking
 at a significant update to the code with CLOUDSTACK-212)

>>>
>>> Excellent work so far. Great work all!
>>>
>>> --
>>> Prasanna.,
>>>
>>> 
>>> Powered by BigRock.com
>>>

codestyle checker?

[Donal Lafferty]

I'd like to clean up my Java so that it matches codestyle 
(http://cloudstack.apache.org/develop/coding-conventions.html).

Is there a tool that will check / fix my code?

DL

Re: Review Request 12223: Async jobs actions now trigger event bus messages to be published

[Murali Reddy]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/12223/#review22785
---

Ship it!


70f33efa7250d1ac8022f4390cddcbcb62ba92f8 master
e7c8a35c3aca4722666c6f6ff6bc9caac46e17c3 4.2

- Murali Reddy


On July 3, 2013, 3:58 p.m., Ryan Dietrich wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12223/
> ---
> 
> (Updated July 3, 2013, 3:58 p.m.)
> 
> 
> Review request for cloudstack, Marcus Sorensen and Murali Reddy.
> 
> 
> Bugs: CLOUDSTACK-3190
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Updated AsyncJobManagerImpl to publish async job events when async jobs are 
> created, updated and completed.
> I am currently stashing the command event description in the commandInfo 
> structure, and then pulling it back out as needed.
> I could switch this to make a database change, but that seemed like a more 
> invasive change.
> 
> I have further diffs to clean up ActionEvent and AlertEvent as well.
> 
> 
> Diffs
> -
> 
>   api/src/com/cloud/event/EventCategory.java cee6529 
>   server/src/com/cloud/api/ApiServer.java 0cd1d61 
>   server/src/com/cloud/async/AsyncJobManagerImpl.java 0101a8a 
> 
> Diff: https://reviews.apache.org/r/12223/diff/
> 
> 
> Testing
> ---
> 
> Manual testing only at this point.  I am more than willing to write a python 
> test using marvin, but I'm unsure if marvin has rabbitmq library support or 
> not yet.  Please advise.
> 
> 
> Thanks,
> 
> Ryan Dietrich
> 
>

Generate single rpm quickly (cloudstack-agent)

[Abhishek Lahiri]

Hi,

I am attempting to make a simple change in the
cloudstack/dist/rpmbuild/SOURCES/cloudstack-4.2.0-SNAPSHOT/python/lib/cloudutils/utilities.py
script , so that the cloudstack-setup-agent script does not throw an error
and exit if it cannot fine /dev/kvm (usage scenario - running cloudstack
inside a running vm). Anyway the change is trivial , but after I make the
change I have to run cloudstack/packaging/centos63/package.sh which takes a
very long time to complete and generate the rpms under
cloudstack/dist/rpmbuild/RPMS/x86_64. Is there any way I can speed up this
process? I just need to generate the
cloudstack-agent-4.2.0-SNAPSHOT.el6.x86_64.rpm package everytime I make
some change to the utilities.py script.  This will save me a lot of time.

Thanks
AL

sonar

[Laszlo Hornyak]

Hi,

I have found CloudStack in the ASF sonar instance
https://analysis.apache.org/dashboard/index/100206?did=1

But looks like it was not executed for a good while. Is it possible to
re-enable it? In general it often helps to spot problems.

Thank you,
Laszlo
-- 

EOF

Review Request 12278: CLOUDSTACK-3384: CloudStack allow VLAN range between 0-4096. Should be 0-'4095'.

[Toshiaki Hatano]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/12278/
---

Review request for cloudstack, Alena Prokharchyk, Chiradeep Vittal, Murali 
Reddy, Hugo Trippaers, and Sheng Yang.


Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-3384


Repository: cloudstack-git


Description
---

CLOUDSTACK-3384: CloudStack allow VLAN range between 0-4096. Should be 0-'4095'.

There're VLAN range check code in com.cloud.network.NetworkServiceImpl. 
But it allows VLAN range between 0-4096. 

VLAN ID have 12 bit field and it's between 0-4095 (0x000 - 0xFFF) . 
CloudStack should return error when someone try to assign VLAN ID 4096 to 
network. 


Diffs
-

  server/src/com/cloud/network/NetworkServiceImpl.java 05df742 

Diff: https://reviews.apache.org/r/12278/diff/


Testing
---

Trying to create zone with Guest VLAN range 4090-4096 from WebUI.

updatePhysicalNetwork returns error correctly.


Thanks,

Toshiaki Hatano

RE: Review Request 12278: CLOUDSTACK-3384: CloudStack allow VLAN range between 0-4096. Should be 0-'4095'.

[Toshiaki Hatano]

My apology for sending review request in HTML format...

How can I change this behavior of Review Board? (Is there setting?)

--
Toshiaki

From: Toshiaki Hatano [mailto:nore...@reviews.apache.org] On Behalf Of Toshiaki 
Hatano
Sent: Friday, July 05, 2013 14:15
To: Hugo Trippaers; Sheng Yang; Chiradeep Vittal; Alena Prokharchyk; Murali 
Reddy
Cc: cloudstack; Toshiaki Hatano
Subject: Review Request 12278: CLOUDSTACK-3384: CloudStack allow VLAN range 
between 0-4096. Should be 0-'4095'.

This is an automatically generated e-mail. To reply, visit: 
https://reviews.apache.org/r/12278/ 

Review request for cloudstack, Alena Prokharchyk, Chiradeep Vittal, Murali 
Reddy, Hugo Trippaers, and Sheng Yang.
By Toshiaki Hatano.
Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-3384 
Repository: cloudstack-git 
Description 
CLOUDSTACK-3384: CloudStack allow VLAN range between 0-4096. Should be 0-'4095'.

There're VLAN range check code in com.cloud.network.NetworkServiceImpl. 
But it allows VLAN range between 0-4096. 

VLAN ID have 12 bit field and it's between 0-4095 (0x000 - 0xFFF) . 
CloudStack should return error when someone try to assign VLAN ID 4096 to 
network. 
Testing 
Trying to create zone with Guest VLAN range 4090-4096 from WebUI.

updatePhysicalNetwork returns error correctly.
Diffs 
• server/src/com/cloud/network/NetworkServiceImpl.java (05df742)
View Diff



This email message is intended for the use of the person to whom it has been 
sent, and may contain information that is confidential or legally protected. If 
you are not the intended recipient or have received this message in error, you 
are not authorized to copy, distribute, or otherwise use this message or its 
attachments. Please notify the sender immediately by return e-mail and 
permanently delete this message and any attachments. Verio Inc. makes no 
warranty that this email is error or virus free.  Thank you.

Re: Generate single rpm quickly (cloudstack-agent)

[Marcus Sorensen]

You only need to run package.sh when you've tested everything and made
sure it's ready. Then you package the final product. For testing, you
can just edit utilities.py in its installed location on the server.

You can run the agent in a VM if you're using vmware-fusion or KVM,
you just have to enable the support for vmx on the hypervisor so you
can modprobe the kvm modules, and then set the 'nested' flag on the
module configs. If you don't, I believe the agent will fail to start
anyway, as it does 'lsmod| grep kvm' on startup.

See devcloud-kvm as an example of running the agent in a vm:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/devcloud-kvm

On Fri, Jul 5, 2013 at 11:42 AM, Abhishek Lahiri  wrote:
> Hi,
>
> I am attempting to make a simple change in the
> cloudstack/dist/rpmbuild/SOURCES/cloudstack-4.2.0-SNAPSHOT/python/lib/cloudutils/utilities.py
> script , so that the cloudstack-setup-agent script does not throw an error
> and exit if it cannot fine /dev/kvm (usage scenario - running cloudstack
> inside a running vm). Anyway the change is trivial , but after I make the
> change I have to run cloudstack/packaging/centos63/package.sh which takes a
> very long time to complete and generate the rpms under
> cloudstack/dist/rpmbuild/RPMS/x86_64. Is there any way I can speed up this
> process? I just need to generate the
> cloudstack-agent-4.2.0-SNAPSHOT.el6.x86_64.rpm package everytime I make
> some change to the utilities.py script.  This will save me a lot of time.
>
> Thanks
> AL

Re: Generate single rpm quickly (cloudstack-agent)

[Marcus Sorensen]

On a side note, I've made the modifications required once to run qemu
without the kvm modules, as a test. You have do do several things, not
just disable the checks (that are there for a reason, to ensure that
everything will work). You'd have to disable several checks, and then
edit the XML definitions that cloudstack creates when defining virtual
machines. After all that, you end up with unbearably slow vms inside a
vm. Unless you don't have access to the hypervisor host (in which case
this is the only option), it's far better to just enable nested
virtualization on the host and use the kvm modules like you would with
a real hardware host.

On Fri, Jul 5, 2013 at 3:38 PM, Marcus Sorensen  wrote:
> You only need to run package.sh when you've tested everything and made
> sure it's ready. Then you package the final product. For testing, you
> can just edit utilities.py in its installed location on the server.
>
> You can run the agent in a VM if you're using vmware-fusion or KVM,
> you just have to enable the support for vmx on the hypervisor so you
> can modprobe the kvm modules, and then set the 'nested' flag on the
> module configs. If you don't, I believe the agent will fail to start
> anyway, as it does 'lsmod| grep kvm' on startup.
>
> See devcloud-kvm as an example of running the agent in a vm:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/devcloud-kvm
>
> On Fri, Jul 5, 2013 at 11:42 AM, Abhishek Lahiri  wrote:
>> Hi,
>>
>> I am attempting to make a simple change in the
>> cloudstack/dist/rpmbuild/SOURCES/cloudstack-4.2.0-SNAPSHOT/python/lib/cloudutils/utilities.py
>> script , so that the cloudstack-setup-agent script does not throw an error
>> and exit if it cannot fine /dev/kvm (usage scenario - running cloudstack
>> inside a running vm). Anyway the change is trivial , but after I make the
>> change I have to run cloudstack/packaging/centos63/package.sh which takes a
>> very long time to complete and generate the rpms under
>> cloudstack/dist/rpmbuild/RPMS/x86_64. Is there any way I can speed up this
>> process? I just need to generate the
>> cloudstack-agent-4.2.0-SNAPSHOT.el6.x86_64.rpm package everytime I make
>> some change to the utilities.py script.  This will save me a lot of time.
>>
>> Thanks
>> AL

Re: Generate single rpm quickly (cloudstack-agent)

[Abhishek Lahiri]

I agree it makes sense to have nested virtualization enabled on the host, but 
can you please share the exact changes that you made to allow qemu , just for 
testing?

On Jul 5, 2013, at 2:48 PM, Marcus Sorensen  wrote:

> On a side note, I've made the modifications required once to run qemu
> without the kvm modules, as a test. You have do do several things, not
> just disable the checks (that are there for a reason, to ensure that
> everything will work). You'd have to disable several checks, and then
> edit the XML definitions that cloudstack creates when defining virtual
> machines. After all that, you end up with unbearably slow vms inside a
> vm. Unless you don't have access to the hypervisor host (in which case
> this is the only option), it's far better to just enable nested
> virtualization on the host and use the kvm modules like you would with
> a real hardware host.
> 
> On Fri, Jul 5, 2013 at 3:38 PM, Marcus Sorensen  wrote:
>> You only need to run package.sh when you've tested everything and made
>> sure it's ready. Then you package the final product. For testing, you
>> can just edit utilities.py in its installed location on the server.
>> 
>> You can run the agent in a VM if you're using vmware-fusion or KVM,
>> you just have to enable the support for vmx on the hypervisor so you
>> can modprobe the kvm modules, and then set the 'nested' flag on the
>> module configs. If you don't, I believe the agent will fail to start
>> anyway, as it does 'lsmod| grep kvm' on startup.
>> 
>> See devcloud-kvm as an example of running the agent in a vm:
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/devcloud-kvm
>> 
>> On Fri, Jul 5, 2013 at 11:42 AM, Abhishek Lahiri  
>> wrote:
>>> Hi,
>>> 
>>> I am attempting to make a simple change in the
>>> cloudstack/dist/rpmbuild/SOURCES/cloudstack-4.2.0-SNAPSHOT/python/lib/cloudutils/utilities.py
>>> script , so that the cloudstack-setup-agent script does not throw an error
>>> and exit if it cannot fine /dev/kvm (usage scenario - running cloudstack
>>> inside a running vm). Anyway the change is trivial , but after I make the
>>> change I have to run cloudstack/packaging/centos63/package.sh which takes a
>>> very long time to complete and generate the rpms under
>>> cloudstack/dist/rpmbuild/RPMS/x86_64. Is there any way I can speed up this
>>> process? I just need to generate the
>>> cloudstack-agent-4.2.0-SNAPSHOT.el6.x86_64.rpm package everytime I make
>>> some change to the utilities.py script.  This will save me a lot of time.
>>> 
>>> Thanks
>>> AL

Re: Using the ACS simulator for jclouds "live" tests - some questions. =)

[Andrew Bayer]

Awesome! I'll try to play with Marvin and cloudmonkey to do prep for
jclouds tests with the simulator this weekend. Thanks!

A.

On Thu, Jul 4, 2013 at 8:19 AM, Prasanna Santhanam  wrote:

> Andrew - Firstly, apologize for the delayed response. You caught me at
> a bad time when I was attempting to fix the simulator which was broken
> when you sent this email. It took longer than expected to fix and get
> it back in shape.
>
> My comments are inline.
>
> On Mon, Jun 24, 2013 at 11:08:20AM -0700, Andrew Bayer wrote:
> > Hey all -
> >
> > So, at David Nalley's suggestion, I'm trying to run jclouds' live tests
> for
> > ACS against a simulator instance, so that I can actually run the full
> > battery of API tests (including global admin, advanced and basic
> > networking, etc) without having to set up a ton of CloudStack instances.
> In
> > a perfect world, it'd be great if there was a standalone war that used h2
> > for the DB and had different flags to pass to it for different starting
> > settings, but I'd be immensely happy to be able to get the following in
> > place on startup (or an easy script to run to do this on top of the base
> > setup):
> >
> Indeed, this is something David discussed with me and it's a great way
> to run the live tests of jclouds. Right now the simulator jar is
> packaged as a plugin. But there's a few spring related connections to
> be made to get it to work with CloudStack installs. I'll figure out
> how we can package (may be a simulator cloudstack rpm) so you can have
> this running.
>
> The simulator itself only provides the ability to mock hypervisor
> commands but the setup of the network model, zone type etc needs to be
> done from the outside. This can be done with the help of marvin's json
> configuration commands. It's just an API driver that can set things up
> for you. There are samples in our code base under
> setup/dev/advanced.cfg and setup/dev/basic.cfg. The tutorial on marvin
> also has this information on how to generate your own style of
> deployment. [1]
>
> [1] https://cwiki.apache.org/confluence/x/QQzMAQ
>
> > - A hardcoded API/secret key for admin, so that I don't have to go click
> > through to create/get it, and can instead just use the same thing every
> > time.
>
> The regular setup of the simulator can be followed by a couple of
> cloudmonkey (ACS CLI) commands to achieve this.
>
> >
> > - At least one available simulator template (best-case would be Ubuntu
> > 10.04 or 12.04) that can be "booted up" out of the box - for whatever
> > reason (I honestly can't tell, from the brief dive I did through the
> code),
> > all the builtin templates come up with isready=false in the listTemplates
> > output, which makes jclouds think there are no templates, etc, etc... I
> > thought this is because they're all in Allocated state, not Ready, but
> even
> > changing them to Ready in the DB didn't do the trick.
>
> The guest OS is something that doesn't matter to the simulator.
> Whatever you ask for will be deployed. One limitation of the simulator
> is that it keeps CloudStack 'happy' by telling it it's got whatever is
> requested. So any negative scenarios will be harder to test without a
> change in the simulator.
>
> The templates issue still exists but with cloudmonkey you can register
> your template and it will come to ready state:
>
> cloudmonkey>> register template format=RAW hypervisor=Simulator
> isfeatured=true ispublic=true name=tiny displaytext=tiny url=
> http://test.url.com/test.rawostypeid=bb62589e-e3cd-11e2-ad39-ea6434daa8ba
> zoneid=55318568-8d4b-412c-8c10-82f47651eb51
>
>
> >
> > - A fake host for starting fake instances on - this may already be there,
> > but I never got far enough to be sure.
>
> Which tutorial are you following to get through this?
> Here's the right link:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python#Marvin-TestingwithPython-
>
> >
> > The above would at least get me able to run the most recent set of live
> > tests I've been working on (testing the new CloudStack implementation of
> > jclouds' cross-compute abstraction for image creation/destruction), but
> in
> > the longer term, I'd absolutely love to be able to run our whole suite
> > against the simulator - obviously, it'd just be an approximation of the
> > real thing, and I'd still try to find real existing ACS setups to finagle
> > access to in order to run the tests against real, live setups, but
> anything
> > I can automate is a huge win for jclouds, and I imagine it'd be very
> useful
> > for libcloud, deltacloud, fog, etc as well!
> >
>
> thanks - indeed it will be. I hope to hear more from your tests.
>
> --
> Prasanna.,
>
> 
> Powered by BigRock.com
>
>

RE: Spring Framework Question

[Soheil Eizadi]

Hi Mike,
You typically have a public interface for your DAO:
public interface InfobloxDao extends GenericDao{

}

Then an implementation:
public class InfobloxDaoImpl extends GenericDaoBase
 implements InfobloxDao {
...
}

This is a good link for the details of Database Access:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Data+Access+Layer

The DataBase DAO is one of the Beans you register with Spring
componentContext.xml.in:  

Then at run time the call like the one you have below wires your application 
typically plugin to the plugin data base implementation:
@Inject
 InfobloxDao _infobloxDao;



From: Mike Tutkowski [mike.tutkow...@solidfire.com]
Sent: Sunday, April 21, 2013 11:53 AM
To: cloudstack-...@incubator.apache.org
Subject: Spring Framework Question

Hi,

I'm new to the Spring Framework.  I understand the basic concepts, but am
not familiar with the details regarding how to hook up dependencies.

For example, I see this in various classes:

@Inject DiskOfferingDao diskOfferingDao;


What did we have to do in Spring (ex. files to configure) so that the
proper runtime instance of DiskOfferingDao was instantiated and assigned to
diskOfferingDao?


Thanks!

--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*™*

Plugin/ Agent/ Host States

[Soheil Eizadi]

I am trying to understand how the Host object state transitions to Up state? I 
see it starts in Alert state.
There is not a setter for status and the comment for it in HostVO.java said:

   /**

 * Note: There is no setter for status because it has to be set in the dao 
code.

 */

@Column(name="status", nullable=false)

private Status status = null;


Thanks,
-Soheil

Re: Generate single rpm quickly (cloudstack-agent)

[Marcus Sorensen]

I don't have a current patch or anything, and I'm not near a PC, but look
in LibvirtComputingResource.java and elsewhere for references to lsmod or
KVM and comment any out. Then go into LibvirtVMDef.java and look at the
strings that build the XML. You will want to start some VMS on your host
manually for reference on what works, then look at that XML and make the
adjustments in that file. Immediately what comes to mind is changing
"domain type=kvm" to "domain type=qemu" and there is an os type somewhere
from hvm to whatever your host supports (type 'virsh capabilities' I think).
On Jul 5, 2013 4:32 PM, "Abhishek Lahiri"  wrote:

>
>
> I agree it makes sense to have nested virtualization enabled on the host,
> but can you please share the exact changes that you made to allow qemu ,
> just for testing?
>
> On Jul 5, 2013, at 2:48 PM, Marcus Sorensen  wrote:
>
> > On a side note, I've made the modifications required once to run qemu
> > without the kvm modules, as a test. You have do do several things, not
> > just disable the checks (that are there for a reason, to ensure that
> > everything will work). You'd have to disable several checks, and then
> > edit the XML definitions that cloudstack creates when defining virtual
> > machines. After all that, you end up with unbearably slow vms inside a
> > vm. Unless you don't have access to the hypervisor host (in which case
> > this is the only option), it's far better to just enable nested
> > virtualization on the host and use the kvm modules like you would with
> > a real hardware host.
> >
> > On Fri, Jul 5, 2013 at 3:38 PM, Marcus Sorensen 
> wrote:
> >> You only need to run package.sh when you've tested everything and made
> >> sure it's ready. Then you package the final product. For testing, you
> >> can just edit utilities.py in its installed location on the server.
> >>
> >> You can run the agent in a VM if you're using vmware-fusion or KVM,
> >> you just have to enable the support for vmx on the hypervisor so you
> >> can modprobe the kvm modules, and then set the 'nested' flag on the
> >> module configs. If you don't, I believe the agent will fail to start
> >> anyway, as it does 'lsmod| grep kvm' on startup.
> >>
> >> See devcloud-kvm as an example of running the agent in a vm:
> >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/devcloud-kvm
> >>
> >> On Fri, Jul 5, 2013 at 11:42 AM, Abhishek Lahiri 
> wrote:
> >>> Hi,
> >>>
> >>> I am attempting to make a simple change in the
> >>>
> cloudstack/dist/rpmbuild/SOURCES/cloudstack-4.2.0-SNAPSHOT/python/lib/cloudutils/utilities.py
> >>> script , so that the cloudstack-setup-agent script does not throw an
> error
> >>> and exit if it cannot fine /dev/kvm (usage scenario - running
> cloudstack
> >>> inside a running vm). Anyway the change is trivial , but after I make
> the
> >>> change I have to run cloudstack/packaging/centos63/package.sh which
> takes a
> >>> very long time to complete and generate the rpms under
> >>> cloudstack/dist/rpmbuild/RPMS/x86_64. Is there any way I can speed up
> this
> >>> process? I just need to generate the
> >>> cloudstack-agent-4.2.0-SNAPSHOT.el6.x86_64.rpm package everytime I make
> >>> some change to the utilities.py script.  This will save me a lot of
> time.
> >>>
> >>> Thanks
> >>> AL
>