from:"Punith S"

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

engine/orchestration/src/org/apache/cloudstack/engine/orchestration/CloudOrchestrator.java
https://reviews.apache.org/r/25647/#comment93132

yes mike, when you create a compute offering with a specified min and max
iops on contrary to the custom iops, iops was setting null for the root disk,
since a new rootdiskoffering object is being created, predefined iops were not
being set.

and yes, this issue is not related to this S3 bug, but i thought it to be a
minor one, so i clubbed it with this review.

- punith s

On Sept. 15, 2014, 7:41 p.m., punith s wrote:

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

(Updated Sept. 15, 2014, 7:41 p.m.)

Review request for cloudstack, amit kumar das and Mike Tutkowski.

Bugs: 7406
https://issues.apache.org/jira/browse/7406

Repository: cloudstack-git

Description
---

this patch also fixes the iops null issue.

for more ref
https://issues.apache.org/jira/browse/CLOUDSTACK-7406

Diffs
-

engine/orchestration/src/org/apache/cloudstack/engine/orchestration/CloudOrchestrator.java
2b49954
server/src/com/cloud/vm/UserVmManagerImpl.java 0ea2a89

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

Testing
---

dry run only.

Thanks,

punith s

Re: Review Request 25647: enabling the rootdisksize variable for vm creation wrt managed storage

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

server/src/com/cloud/vm/UserVmManagerImpl.java
https://reviews.apache.org/r/25647/#comment93133

yeah, as i observed a new rootdisksize variable has been indroduced in
deployVM api for 4.4 onwards, which enables the user to give his own root disk
size greater than the current template size.
which in turn will override the template size by the given rootdisksize,
hence our SAN volume will be created based on the inputted rootdisksize by the
admin.

no, the user must be having a prior knowledge of whether the templates is
in S3/Swift or nfs,
if the user is using the normal nfs store, he need not specify the size
since the template is already contains the processed virtual size.

yes, this is the challenge i'm facing right now, since user has no prior
knowledge of the infrastructure nor that we are able to list the infrastructure
in the user mode.
hence i'm assuming that the admin will inform the user about this awareness
and the sizes to be given for the corrensponding templates.

- punith s

On Sept. 15, 2014, 7:41 p.m., punith s wrote:

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

(Updated Sept. 15, 2014, 7:41 p.m.)

Review request for cloudstack, amit kumar das and Mike Tutkowski.

Bugs: 7406
https://issues.apache.org/jira/browse/7406

Repository: cloudstack-git

Description
---

this patch also fixes the iops null issue.

for more ref
https://issues.apache.org/jira/browse/CLOUDSTACK-7406

Diffs
-

engine/orchestration/src/org/apache/cloudstack/engine/orchestration/CloudOrchestrator.java
2b49954
server/src/com/cloud/vm/UserVmManagerImpl.java 0ea2a89

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

Testing
---

dry run only.

Thanks,

punith s

Re: Review Request 25647: enabling the rootdisksize variable for vm creation wrt managed storage


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

(Updated Sept. 16, 2014, 5:15 p.m.)


Review request for cloudstack, amit kumar das and Mike Tutkowski.


Bugs: 7406
https://issues.apache.org/jira/browse/7406


Repository: cloudstack-git


Description
---

since cloudstack is not able to process the S3 or Switf templates for its 
virtual size(root disk size), admin is facing issues while creating a vm using 
third party storage plugins like cloudbyte and solidfire etc.
this patch enables the resize of root disk, on passing a  variable 
ismanagedstorage = true in deployVmCmd as a detail.
hence template root disksize is overriden by the given rootdisk size by the 
admin

this patch also fixes the iops null issue.

for more ref
https://issues.apache.org/jira/browse/CLOUDSTACK-7406


Diffs (updated)
-

  
engine/orchestration/src/org/apache/cloudstack/engine/orchestration/CloudOrchestrator.java
 2b49954 
  server/src/com/cloud/vm/UserVmManagerImpl.java 0ea2a89 

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


Testing
---

dry run only.


Thanks,

punith s

Re: Review Request 25647: enabling the rootdisksize variable for vm creation wrt managed storage


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

(Updated Sept. 16, 2014, 5:16 p.m.)


Review request for cloudstack and Mike Tutkowski.


Bugs: 7406
https://issues.apache.org/jira/browse/7406


Repository: cloudstack-git


Description
---

since cloudstack is not able to process the S3 or Switf templates for its 
virtual size(root disk size), admin is facing issues while creating a vm using 
third party storage plugins like cloudbyte and solidfire etc.
this patch enables the resize of root disk, on passing a  variable 
ismanagedstorage = true in deployVmCmd as a detail.
hence template root disksize is overriden by the given rootdisk size by the 
admin

this patch also fixes the iops null issue.

for more ref
https://issues.apache.org/jira/browse/CLOUDSTACK-7406


Diffs
-

  
engine/orchestration/src/org/apache/cloudstack/engine/orchestration/CloudOrchestrator.java
 2b49954 
  server/src/com/cloud/vm/UserVmManagerImpl.java 0ea2a89 

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


Testing
---

dry run only.


Thanks,

punith s

Review Request 25647: enabling the rootdisksize variable for vm creation wrt managed storage

2014-09-15 Thread punith s


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

Review request for cloudstack, amit kumar das and Mike Tutkowski.


Bugs: 7406
https://issues.apache.org/jira/browse/7406


Repository: cloudstack-git


Description
---

since cloudstack is not able to process the S3 or Switf templates for its 
virtual size(root disk size), admin is facing issues while creating a vm using 
third party storage plugins like cloudbyte and solidfire etc.
this patch enables the resize of root disk, on passing a  variable 
ismanagedstorage = true in deployVmCmd as a detail.
hence template root disksize is overriden by the given rootdisk size by the 
admin

this patch also fixes the iops null issue.

for more ref
https://issues.apache.org/jira/browse/CLOUDSTACK-7406


Diffs
-

  
engine/orchestration/src/org/apache/cloudstack/engine/orchestration/CloudOrchestrator.java
 2b49954 
  server/src/com/cloud/vm/UserVmManagerImpl.java 0ea2a89 

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


Testing
---

dry run only.


Thanks,

punith s

Re: S3/Swift Problem around Virtual Size

2014-09-11 Thread Punith S

sure mike :)

and it seems in context of managed storage we are creating the SAN volume
before downloading the template from S3 to staging store; means the SAN
volume of false size will be already created before fetching the actual
virtual size of the template !

hence i'm hitting the same issue again, saying not enough space !

so in case of S3 and Swift, shall we reserve minimum size of the SAN volume
for allowing the copy and later shall the admin resize the SAN volume to
his needs?

any thoughts ?

thanks

On Wed, Sep 10, 2014 at 10:18 PM, Mike Tutkowski 
mike.tutkow...@solidfire.com wrote:

 Also, of course feel free to put me down as a reviewer when you are ready
 and I can review the code shortly after.

 Thanks!

 On Wed, Sep 10, 2014 at 10:47 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 I have not heard recently on when code freeze for 4.5 is, per se.

 Regardless, I'd say this is an important-enough issue that we should wait
 for your patch.

 We're still in the process of getting 4.3.1 and 4.4.1 out the door, so I
 think it'll be a bit before 4.5 goes out.

 Thanks for your time and effort on this, Punith!

 On Wed, Sep 10, 2014 at 10:32 AM, Punith S punit...@cloudbyte.com
 wrote:

 yes mike,

 i'm fixing the issue w.r.t option 2.

 testing the patch is consuming much time, since i have to register the
 templates via S3, and it has to download via S3 to staging store.

 can i know when is the code freez for 4.5 ?

 thanks!

 On Tue, Sep 9, 2014 at 9:30 PM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 Yeah, either solution will fix this issue for managed storage in
 general (ex. SolidFire, CloudByte).

 On Tue, Sep 9, 2014 at 9:58 AM, Francois Gaudreault 
 fgaudrea...@cloudops.com wrote:

 That's great Punith :)

 Thanks for handling this one. I am not too worried about the option,
 as long as it fixes SF integration for 4.5 :)

 FG

 On Tue, Sep 9, 2014 at 11:55 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 Thanks for the info, Punith!

 Does that mean you are fixing the issue via Option2?

 On Tue, Sep 9, 2014 at 7:52 AM, Punith S punit...@cloudbyte.com
 wrote:

 yes mike,

 w.r.t to option 1:
 it will be like creating a VM w.r.t ISO, where admin will have to
 specify the os disk(ROOT) disk size.

 for option 2:
 i have figured out the issue, post downloading the template to S3,
 cloudstack will again download the template from S3 to staging nfs 
 store.
 here we need to access the file and process it with VHD processor in
 order to calculate the virtualsize but we are skipping this process,
 hence the virtual size is not being calculated while using the S3 or
 swift.

 the templates already present in the staging nfs storage cannot be
 applied to this process.

 for option 3:
 it's convenient to calculate the template virtual size while it is
 being copied from s3 to staged nfs store instead of staged nfs to 
 primary,
 since admin might be using more than one primary stores.

 i'm fixing the issue, will post the patch ASAP for 4.5.snapshot.

 thanks!

 On Tue, Sep 9, 2014 at 11:13 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 By the way, for anyone new to this issue, this is what we're
 referring to here:

 https://issues.apache.org/jira/browse/CLOUDSTACK-7406

 On Mon, Sep 8, 2014 at 11:41 PM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 Great :) Then a question might be, Is it too late in the game to
 interrogate the template to discover its virtual size if we're just 
 about
 to copy the template to primary storage?

 If it's not, this might be the place to run the logic to figure
 out the virtual size.

 Really, there are three big possibilities:

 1) Just ask the end user to provide the virtual size (not
 commenting here on what happens for already-uploaded templates)

 or

 2) Figure out the virtual size when the template is copied from
 object storage to secondary storage and update the DB with this info 
 (not
 sure what happens if the template has already been copied to
 (secondary-storage) NFS because it was used before)

 or

 3) Figure out the virtual size when the template is about to be
 copied from secondary storage to primary storage

 On Mon, Sep 8, 2014 at 11:35 PM, Sanjeev Neelarapu 
 sanjeev.neelar...@citrix.com wrote:

 Mike,

 You are right. Template gets copied to (secondary-storage) NFS
 before being copied to primary storage

 -Sanjeev

 -Original Message-
 From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
 Sent: Tuesday, September 09, 2014 10:55 AM
 To: dev@cloudstack.apache.org
 Cc: Punith S; Francois Gaudreault
 Subject: Re: S3/Swift Problem around Virtual Size

 Hi Will,

 Thanks for the input!

 I like the idea of storing the virtual size as metadata in S3 or
 Swift although this could require that the end user provide this 
 value when
 uploading the template.

 However, if we have the ability to determine the virtual size of
 the template after it gets downloaded to (secondary-storage

Re: S3/Swift Problem around Virtual Size

2014-09-10 Thread Punith S

yes mike,

i'm fixing the issue w.r.t option 2.

testing the patch is consuming much time, since i have to register the
templates via S3, and it has to download via S3 to staging store.

can i know when is the code freez for 4.5 ?

thanks!

On Tue, Sep 9, 2014 at 9:30 PM, Mike Tutkowski mike.tutkow...@solidfire.com
 wrote:

 Yeah, either solution will fix this issue for managed storage in general
 (ex. SolidFire, CloudByte).

 On Tue, Sep 9, 2014 at 9:58 AM, Francois Gaudreault 
 fgaudrea...@cloudops.com wrote:

 That's great Punith :)

 Thanks for handling this one. I am not too worried about the option, as
 long as it fixes SF integration for 4.5 :)

 FG

 On Tue, Sep 9, 2014 at 11:55 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 Thanks for the info, Punith!

 Does that mean you are fixing the issue via Option2?

 On Tue, Sep 9, 2014 at 7:52 AM, Punith S punit...@cloudbyte.com wrote:

 yes mike,

 w.r.t to option 1:
 it will be like creating a VM w.r.t ISO, where admin will have to
 specify the os disk(ROOT) disk size.

 for option 2:
 i have figured out the issue, post downloading the template to S3,
 cloudstack will again download the template from S3 to staging nfs store.
 here we need to access the file and process it with VHD processor in
 order to calculate the virtualsize but we are skipping this process,
 hence the virtual size is not being calculated while using the S3 or
 swift.

 the templates already present in the staging nfs storage cannot be
 applied to this process.

 for option 3:
 it's convenient to calculate the template virtual size while it is
 being copied from s3 to staged nfs store instead of staged nfs to primary,
 since admin might be using more than one primary stores.

 i'm fixing the issue, will post the patch ASAP for 4.5.snapshot.

 thanks!

 On Tue, Sep 9, 2014 at 11:13 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 By the way, for anyone new to this issue, this is what we're referring
 to here:

 https://issues.apache.org/jira/browse/CLOUDSTACK-7406

 On Mon, Sep 8, 2014 at 11:41 PM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 Great :) Then a question might be, Is it too late in the game to
 interrogate the template to discover its virtual size if we're just about
 to copy the template to primary storage?

 If it's not, this might be the place to run the logic to figure out
 the virtual size.

 Really, there are three big possibilities:

 1) Just ask the end user to provide the virtual size (not commenting
 here on what happens for already-uploaded templates)

 or

 2) Figure out the virtual size when the template is copied from
 object storage to secondary storage and update the DB with this info (not
 sure what happens if the template has already been copied to
 (secondary-storage) NFS because it was used before)

 or

 3) Figure out the virtual size when the template is about to be
 copied from secondary storage to primary storage

 On Mon, Sep 8, 2014 at 11:35 PM, Sanjeev Neelarapu 
 sanjeev.neelar...@citrix.com wrote:

 Mike,

 You are right. Template gets copied to (secondary-storage) NFS
 before being copied to primary storage

 -Sanjeev

 -Original Message-
 From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
 Sent: Tuesday, September 09, 2014 10:55 AM
 To: dev@cloudstack.apache.org
 Cc: Punith S; Francois Gaudreault
 Subject: Re: S3/Swift Problem around Virtual Size

 Hi Will,

 Thanks for the input!

 I like the idea of storing the virtual size as metadata in S3 or
 Swift although this could require that the end user provide this value 
 when
 uploading the template.

 However, if we have the ability to determine the virtual size of the
 template after it gets downloaded to (secondary-storage) NFS and we're 
 able
 to update the database with this info, then it would seem we would never
 need to ask the user for this value.

 Either way, the tricky part might be if the template in object
 storage has already been downloaded to (secondary-storage) NFS (say it 
 was
 used before). In this case, we won't need to download it to
 (secondary-storage) NFS again (at least not in the same zone), so we 
 won't
 have an easy opportunity to figure out the virtual size upon download 
 from
 object storage.

 I wonder if it's too late in this process if we figured out the
 virtual size before the copied template (now on (secondary-storage) NFS)
 gets copied to primary storage. If we could do it at this point, then we
 wouldn't have to worry about fixing the legacy situation because it 
 would
 just work out naturally. We would look in the DB to see if the virtual 
 size
 for this template is known and, if not, we could figure out the virtual
 size before downloading from (secondary-storage) NFS to primary storage
 each time. (Although I'm thinking this would come too late in the 
 process
 because we may have already asked the primary-storage plug-in to create 
 the
 necessary volume.)

 By the way, I'm assuming

Re: S3/Swift Problem around Virtual Size

2014-09-09 Thread Punith S

yes mike,

w.r.t to option 1:
it will be like creating a VM w.r.t ISO, where admin will have to specify
the os disk(ROOT) disk size.

for option 2:
i have figured out the issue, post downloading the template to S3,
cloudstack will again download the template from S3 to staging nfs store.
here we need to access the file and process it with VHD processor in order
to calculate the virtualsize but we are skipping this process,
hence the virtual size is not being calculated while using the S3 or swift.

the templates already present in the staging nfs storage cannot be applied
to this process.

for option 3:
it's convenient to calculate the template virtual size while it is being
copied from s3 to staged nfs store instead of staged nfs to primary,
since admin might be using more than one primary stores.

i'm fixing the issue, will post the patch ASAP for 4.5.snapshot.

thanks!

On Tue, Sep 9, 2014 at 11:13 AM, Mike Tutkowski 
mike.tutkow...@solidfire.com wrote:

 By the way, for anyone new to this issue, this is what we're referring to
 here:

 https://issues.apache.org/jira/browse/CLOUDSTACK-7406

 On Mon, Sep 8, 2014 at 11:41 PM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 Great :) Then a question might be, Is it too late in the game to
 interrogate the template to discover its virtual size if we're just about
 to copy the template to primary storage?

 If it's not, this might be the place to run the logic to figure out the
 virtual size.

 Really, there are three big possibilities:

 1) Just ask the end user to provide the virtual size (not commenting here
 on what happens for already-uploaded templates)

 or

 2) Figure out the virtual size when the template is copied from object
 storage to secondary storage and update the DB with this info (not sure
 what happens if the template has already been copied to (secondary-storage)
 NFS because it was used before)

 or

 3) Figure out the virtual size when the template is about to be copied
 from secondary storage to primary storage

 On Mon, Sep 8, 2014 at 11:35 PM, Sanjeev Neelarapu 
 sanjeev.neelar...@citrix.com wrote:

 Mike,

 You are right. Template gets copied to (secondary-storage) NFS before
 being copied to primary storage

 -Sanjeev

 -Original Message-
 From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
 Sent: Tuesday, September 09, 2014 10:55 AM
 To: dev@cloudstack.apache.org
 Cc: Punith S; Francois Gaudreault
 Subject: Re: S3/Swift Problem around Virtual Size

 Hi Will,

 Thanks for the input!

 I like the idea of storing the virtual size as metadata in S3 or Swift
 although this could require that the end user provide this value when
 uploading the template.

 However, if we have the ability to determine the virtual size of the
 template after it gets downloaded to (secondary-storage) NFS and we're able
 to update the database with this info, then it would seem we would never
 need to ask the user for this value.

 Either way, the tricky part might be if the template in object storage
 has already been downloaded to (secondary-storage) NFS (say it was used
 before). In this case, we won't need to download it to (secondary-storage)
 NFS again (at least not in the same zone), so we won't have an easy
 opportunity to figure out the virtual size upon download from object
 storage.

 I wonder if it's too late in this process if we figured out the virtual
 size before the copied template (now on (secondary-storage) NFS) gets
 copied to primary storage. If we could do it at this point, then we
 wouldn't have to worry about fixing the legacy situation because it would
 just work out naturally. We would look in the DB to see if the virtual size
 for this template is known and, if not, we could figure out the virtual
 size before downloading from (secondary-storage) NFS to primary storage
 each time. (Although I'm thinking this would come too late in the process
 because we may have already asked the primary-storage plug-in to create the
 necessary volume.)

 By the way, I'm assuming that a template gets copied to
 (secondary-storage) NFS before being copied to primary storage. I'm not
 super familiar with how this process works.

 Talk to you later,
 Mike

 On Mon, Sep 8, 2014 at 10:59 PM, Will Stevens wstev...@cloudops.com
 wrote:

  My two cents on the topic.
 
  Ideally we would save the size in the object store metadata and
  retrieve it from the metadata if it is set.  If it is not set in the
  object store metadata, then when it is fetched, we have to put it on
  NFS and determine the size (then ideally save the metadata back to the
  object store) and remove the NFS copy.
 
  This way the NFS copy approach is only ever done once and then the
  data is populated (for backwards compatibility).  For all templates
  created after the patch, the metadata would be stored and retrieved
  without the need for the NFS copy.
 
  Is this feasible?
 
  Will
 
 
  *Will STEVENS*
  Lead Developer
 
  *CloudOps* *| *Cloud Solutions

SSVM JAVA PROCESS NOT RUNNING, systemvm didn't get patched with the agent specific code

2014-09-04 Thread Punith S

hi,

i have been working on building noredist of master for vmware,

since i'm using mvn commands and jetty for deploying cloudstack

i'm building the cloudstack using
 $ mvn clean
$ mvn install -Dnoredist

deploying using $ mvn -pl :cloud-client-ui jetty:run -Dnoredist

also i'm seeding the SSVM template by using
as the link suggests
https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack

# mkdir -p /etc/cloudstack/management/
# cp 
./client/target/cloud-client-ui-4.5.0-SNAPSHOT/WEB-INF/classes/db.properties
/etc/cloudstack/management/
#
./client/target/generated-webapp/WEB-INF/classes/scripts/storage/secondary/cloud-install-sys-tmplt
-m /mnt/secondary -u http://
jenkins.buildacloud.org/view/master/job/build-systemvm-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvmtemplate-master-vmware.ova
-h vmware -F

when i deploy a vmware zone,everything come up fine but the systemvm's
agent is not running!

when i log into the ssvm,* i see 4.4.SNAPSHOT jars being patched in the
/use/local/cloud/ssvm*

hence the java process is not running
logs show
2014-09-04 09:20:24,760 INFO  [cloud.agent.AgentShell] (main:null) Agent
started
2014-09-04 09:20:24,764 INFO  [cloud.agent.AgentShell] (main:null)
Implementation Version is 4.4.0-SNAPSHOT
2014-09-04 09:20:24,765 INFO  [cloud.agent.AgentShell] (main:null)
agent.properties found at /usr/local/cloud/systemvm/conf/agent.properties
2014-09-04 09:20:24,772 DEBUG [cloud.agent.AgentShell] (main:null) Found
property: instance
2014-09-04 09:20:24,774 DEBUG [cloud.agent.AgentShell] (main:null) Found
property: resource
2014-09-04 09:20:24,774 INFO  [cloud.agent.AgentShell] (main:null)
Defaulting to using properties file for storage
2014-09-04 09:20:24,781 INFO  [cloud.agent.AgentShell] (main:null)
Defaulting to the constant time backoff algorithm
2014-09-04 09:20:24,801 INFO  [cloud.utils.LogUtils] (main:null) log4j
configuration found at /usr/local/cloud/systemvm/conf/log4j-cloud.xml
2014-09-04 09:20:24,825 DEBUG [cloud.agent.AgentShell] (main:null) Checking
to see if agent.SecStorage.pid exists.
2014-09-04 09:20:24,828 DEBUG [cloud.utils.ProcessUtil] (main:null)
environment.properties could not be opened
2014-09-04 09:20:24,836 DEBUG [cloud.utils.ProcessUtil] (main:null)
Executing: bash -c echo $PPID
2014-09-04 09:20:24,844 DEBUG [cloud.utils.ProcessUtil] (main:null)
Execution is successful.
*2014-09-04 09:20:24,853 ERROR [cloud.agent.AgentShell] (main:null) Unable
to start agent: Resource class not found:
com.cloud.storage.resource.PremiumSecondaryStorageResource due to:
java.lang.ClassNotFoundException:
com.cloud.storage.resource.PremiumSecondaryStorageResource*

i'm guessing there was no patch up between agent specific code !
am i missing out something here ?

thanks!
-- 
regards,

punith s
cloudbyte.com

Re: SSVM JAVA PROCESS NOT RUNNING, systemvm didn't get patched with the agent specific code

2014-09-04 Thread Punith S

thanks Hugo, it's working now :)

cheers!


On Thu, Sep 4, 2014 at 3:32 PM, Hugo Trippaers h...@trippaers.nl wrote:

 Punith,

 You need to enable the systemvm flag in cloudstack to make sure a new
 systemvm.iso is build.

 mvn -Dnoredist -Psystemvm clean install


 Cheers,

 Hugo

 On 4 sep. 2014, at 11:27, Punith S punit...@cloudbyte.com wrote:

  hi,
 
  i have been working on building noredist of master for vmware,
 
  since i'm using mvn commands and jetty for deploying cloudstack
 
  i'm building the cloudstack using
  $ mvn clean
  $ mvn install -Dnoredist
 
  deploying using $ mvn -pl :cloud-client-ui jetty:run -Dnoredist
 
  also i'm seeding the SSVM template by using
  as the link suggests
 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack
 
  # mkdir -p /etc/cloudstack/management/
  # cp
 ./client/target/cloud-client-ui-4.5.0-SNAPSHOT/WEB-INF/classes/db.properties
  /etc/cloudstack/management/
  #
 
 ./client/target/generated-webapp/WEB-INF/classes/scripts/storage/secondary/cloud-install-sys-tmplt
  -m /mnt/secondary -u http://
 
 jenkins.buildacloud.org/view/master/job/build-systemvm-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvmtemplate-master-vmware.ova
  -h vmware -F
 
  when i deploy a vmware zone,everything come up fine but the systemvm's
  agent is not running!
 
  when i log into the ssvm,* i see 4.4.SNAPSHOT jars being patched in the
  /use/local/cloud/ssvm*
 
  hence the java process is not running
  logs show
  2014-09-04 09:20:24,760 INFO  [cloud.agent.AgentShell] (main:null) Agent
  started
  2014-09-04 09:20:24,764 INFO  [cloud.agent.AgentShell] (main:null)
  Implementation Version is 4.4.0-SNAPSHOT
  2014-09-04 09:20:24,765 INFO  [cloud.agent.AgentShell] (main:null)
  agent.properties found at /usr/local/cloud/systemvm/conf/agent.properties
  2014-09-04 09:20:24,772 DEBUG [cloud.agent.AgentShell] (main:null) Found
  property: instance
  2014-09-04 09:20:24,774 DEBUG [cloud.agent.AgentShell] (main:null) Found
  property: resource
  2014-09-04 09:20:24,774 INFO  [cloud.agent.AgentShell] (main:null)
  Defaulting to using properties file for storage
  2014-09-04 09:20:24,781 INFO  [cloud.agent.AgentShell] (main:null)
  Defaulting to the constant time backoff algorithm
  2014-09-04 09:20:24,801 INFO  [cloud.utils.LogUtils] (main:null) log4j
  configuration found at /usr/local/cloud/systemvm/conf/log4j-cloud.xml
  2014-09-04 09:20:24,825 DEBUG [cloud.agent.AgentShell] (main:null)
 Checking
  to see if agent.SecStorage.pid exists.
  2014-09-04 09:20:24,828 DEBUG [cloud.utils.ProcessUtil] (main:null)
  environment.properties could not be opened
  2014-09-04 09:20:24,836 DEBUG [cloud.utils.ProcessUtil] (main:null)
  Executing: bash -c echo $PPID
  2014-09-04 09:20:24,844 DEBUG [cloud.utils.ProcessUtil] (main:null)
  Execution is successful.
  *2014-09-04 09:20:24,853 ERROR [cloud.agent.AgentShell] (main:null)
 Unable
  to start agent: Resource class not found:
  com.cloud.storage.resource.PremiumSecondaryStorageResource due to:
  java.lang.ClassNotFoundException:
  com.cloud.storage.resource.PremiumSecondaryStorageResource*
 
  i'm guessing there was no patch up between agent specific code !
  am i missing out something here ?
 
  thanks!
  --
  regards,
 
  punith s
  cloudbyte.com




-- 
regards,

punith s
cloudbyte.com

Re: S3/Swift Problem around Virtual Size

2014-08-27 Thread Punith S

hi

think i had a timeout problem!
on the second try the template has been downloaded to the S3 bucket and the
management server shows the status as download complete with template size
as 1.6G instead of its virtual size 20G.

and i see the template's status as Download Complete but it seems it is not
getting installed ! refer the attachment

can anyone explain the installing template after the download completes ?

On Wed, Aug 27, 2014 at 9:18 AM, Marcus shadow...@gmail.com wrote:

 Per Edisons comments about not knowing the image size, can't we just set
 some headers and store metadata with the template in S3 to save the virtual
 size when the template is registered? I'm assuming here that the SSVM does
 the work of pulling the template in and uploading to S3. Or it could be
 stored in the template table?
 On Aug 26, 2014 9:11 PM, Francois Gaudreault fgaudrea...@cloudops.com
 wrote:

  Looks like your SSVM cannot reach Internet properly?
 
  FG
 
  On 2014-08-26, 11:14 AM, Punith S wrote:
 
  hi francois,
 
  since i'm not having a swift setup, i'm using the s3 bucket.
 
  and as you recommended i got the SSVM up with seeded nfs storage,
 
  post that i removed the nfs secondary storage and added the S3 with
  staging nfs store as the new sec storage, since you cannot have any nfs
  secondary storage while using the S3.
 
  on registering the a new template, i'm getting template status as*Unable
  to execute HTTP request: No route to host*
  in managementserver.log
 
  2014-08-26 20:41:07,502 DEBUG [o.a.c.s.RemoteHostEndPoint]
  (Timer-24:ctx-b68380cd) Sending command org.apache.cloudstack.storage.
  command.DownloadProgressCommand to host: 10
  2014-08-26 20:41:07,507 DEBUG [c.c.a.t.Request] (Timer-24:ctx-b68380cd)
  Seq 10-5684105679694996125: Sending  { Cmd , MgmtId: 52242179434, via:
  10(s-142-VM), Ver: v1, Flags: 100011, [{org.apache.cloudstack.
  storage.command.DownloadProgressCommand:{jobId:d43a17c9-3b03-4ff9-
  8906-e1d155981e86,request:GET_STATUS,hvm:true,
  description:centext,maxDownloadSizeInBytes:53687091200,id:209,
  resourceType:TEMPLATE,installPath:template/tmpl/2/
  209/209-2-b624436c-5f37-30d4-8eaf-81582eb0d39d,_store:{
  com.cloud.agent.api.to.S3TO:{id:14,uuid:e4afd7bb-39ea-
  4128-ab93-f8a09b1d5e03,bucketName:test-cloudstack,
  httpsFlag:false,created:Aug 26, 2014 8:16:24
 PM,enableRRS:false,
  maxSingleUploadSizeInBytes:5368709120}},url:http://
  download.cloud.com/templates/builtin/centos56-x86_64.vhd.bz2
 
 ,format:VHD,accountId:2,name:209-2-b624436c-5f37-30d4-8eaf-81582eb0d39d,wait:0}}]
  }
  2014-08-26 20:41:07,556 DEBUG [c.c.a.t.Request]
  (AgentManager-Handler-10:null) Seq 10-5684105679694996125: Processing:
 {
  Ans: , MgmtId: 52242179434, via: 10, Ver: v1, Flags: 10,
  [{com.cloud.agent.api.storage.DownloadAnswer:{
  jobId:d43a17c9-3b03-4ff9-8906-e1d155981e86,
  downloadPct:0,errorString:No route to host,downloadStatus:
  DOWNLOAD_ERROR,installPath:template/tmpl/2/209/209-2-
  b624436c-5f37-30d4-8eaf-81582eb0d39d,templateSize:
  0,templatePhySicalSize:0,result:true,details:No route to
  host,wait:0}}] }
 
  but i don't see any logging happening in secondary storage vm's
 cloud.log
 
  not sure this error is happening due to S3!
 
 
  thanks!
 
 
 
  --
  Francois Gaudreault
  Gestionnaire de Produit | Product Manager - Cloud Platform  Services
  t:514-629-6775
 
  CloudOps Votre partenaire infonuagique | Cloud Solutions Experts
  420 rue Guy | Montreal | Quebec | H3J 1S6
  w: cloudops.com | tw: @CloudOps_
 
 




-- 
regards,

punith s
cloudbyte.com

Re: S3/Swift Problem around Virtual Size

2014-08-26 Thread Punith S

sure mike,

since i don't have a S3 account, i'm getting one today.

francois, can you brief me how you seeded your templates into S3.

thanks!


On Mon, Aug 25, 2014 at 11:16 PM, Mike Tutkowski 
mike.tutkow...@solidfire.com wrote:

 Yes, I expect we'll see the same issue with S3, as well.

 Punith - Is this something you might have time to investigate? Perhaps
 Edison can point us in the right direction here.


 On Mon, Aug 25, 2014 at 5:17 AM, Francois Gaudreault 
 fgaudrea...@cloudops.com wrote:

  Punith,
 
  I highly anticipate the same issue with S3... it shares a lot of code
 with
  swift.
 
  My focus would be swift, but we should fix for both :)
 
  FG
  On Aug 25, 2014 6:33 AM, Punith S punit...@cloudbyte.com wrote:
 
   thanks for opening this thread mike,
  
   since i only use nfs as my secondary storage provider, i didn't see
 this
   issue till date.
  
   is this issue occurring even using a S3 secondary storage with staging
  nfs
   store ?
  
   if so like edison pointed we need to fetch the virtual size from the
 nfs
   store instead of S3 in the deploymentmanager.
  
   thanks
  
  
   On Sat, Aug 23, 2014 at 3:45 AM, Mike Tutkowski 
   mike.tutkow...@solidfire.com wrote:
  
Hey Edison,
   
Do you know how difficult/easy of a fix this is, who might be
 available
   to
put this fix in, and for what release (hopefully 4.4.1) this fix
 could
   find
its way in?
   
Thanks!
Mike
   
   
On Fri, Aug 22, 2014 at 3:37 PM, Francois Gaudreault 
fgaudrea...@cloudops.com wrote:
   
 Min,

 Ok, but this is not the behavior I see. Even without requesting a
 VM
 create, the template is pushed to the staging NFS at least once. Is
  it
 downloaded there or pushed after download, that I am not sure. I
 was
 assuming the swift upload bash script was executed after the
 template
   is
on
 the staging.

 Anyway... the focus is on the virt size, and you all know the code
   better
 than I do :)

 FG
 On Aug 22, 2014 5:28 PM, Min Chen min.c...@citrix.com wrote:

 No. For S3/Swift, register template will directly upload templates
  to
   S3
 without going through staging NFS. It will only be copied to
 staging
   NFS
 when we first use that template to provision a VM.

 Thanks
 -min

 On 8/22/14 2:25 PM, Francois Gaudreault 
 fgaudrea...@cloudops.com
  
 wrote:

 Edison,
 
 Isnt the templates downloaded to the Staging NFS first?
 
 FG
 On Aug 22, 2014 5:20 PM, Edison Su edison...@citrix.com
 wrote:
 
  I know the reason why the size of template doesn¹t have correct
virtual
  size if it¹s registered in S3/Swift:
  In case of s3/swift, the template is directly stored into
  s3/swift
 through
  swift/s3 api, there is no place for cloudstack to look into
   template,
 to
  find out the virtual size during template registration.
  While, if secondary storage is NFS, the template is first
 stored
  on
  NFS(which has file system), cloudstack can unzip the
 template(if
it¹s a
  zipped file), and read virtual size from the file, then report
  back
to
 mgt
  server.
  In order to fix it, we can add some code as: all the templates
 registered
  on Swift/S3, need to be downloaded to a NFS intermediate
 storage
before
 it
  can be consumed by primary storage. After the download
 finished,
   then
 we
  check virtual size of template, and report back to mgt
   server/update
DB
 etc.
 
  From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
  Sent: Friday, August 22, 2014 1:38 PM
  To: dev@cloudstack.apache.org
  Cc: Edison Su
  Subject: S3/Swift Problem around Virtual Size
 
  Hi,
 
  This was brought up in a different e-mail thread, but I wanted
 to
make
 it
  more clear that it's related to CloudStack's download code
 around
 S3/Swift,
  so I'm opening up a new thread.
 
  Francois (from CloudOps) noticed today that when he downloaded
 a
 template
  (VHD format) to Swift (but it looks like the same applies for
 S3)
that
 the
  physical and virtual sizes are set to be the same.
 
  This appears to have the following consequence:
 
  You can download a template with a physical size of, say, 3 GB
  and
   a
 root
  disk that's supposed to be, say, 20 GB. Instead of the virtual
  size
 showing
  as 20 GB, it shows as 3 GB.
 
  This is not an issue with NFS. In that situation, the two sizes
  are
  correctly accounted for.
 
  What later can happen is the template is downloaded from Swift
  and
 takes
  up an unexpected amount of space on the XenServer storage
   repository
 (SR).
 
  If there is enough space on the SR, this isn't too big of a
 deal.
 However,
  for so-called managed storage plug

Re: S3/Swift Problem around Virtual Size

2014-08-26 Thread Punith S

hi francois,

since i'm not having a swift setup, i'm using the s3 bucket.

and as you recommended i got the SSVM up with seeded nfs storage,

post that i removed the nfs secondary storage and added the S3 with staging
nfs store as the new sec storage, since you cannot have any nfs secondary
storage while using the S3.

on registering the a new template, i'm getting template status as* Unable
to execute HTTP request: No route to host*

in managementserver.log

2014-08-26 20:41:07,502 DEBUG [o.a.c.s.RemoteHostEndPoint]
(Timer-24:ctx-b68380cd) Sending command
org.apache.cloudstack.storage.command.DownloadProgressCommand to host: 10
2014-08-26 20:41:07,507 DEBUG [c.c.a.t.Request] (Timer-24:ctx-b68380cd) Seq
10-5684105679694996125: Sending  { Cmd , MgmtId: 52242179434, via:
10(s-142-VM), Ver: v1, Flags: 100011,
[{org.apache.cloudstack.storage.command.DownloadProgressCommand:{jobId:d43a17c9-3b03-4ff9-8906-e1d155981e86,request:GET_STATUS,hvm:true,description:centext,maxDownloadSizeInBytes:53687091200,id:209,resourceType:TEMPLATE,installPath:template/tmpl/2/209/209-2-b624436c-5f37-30d4-8eaf-81582eb0d39d,_store:{com.cloud.agent.api.to.S3TO:{id:14,uuid:e4afd7bb-39ea-4128-ab93-f8a09b1d5e03,bucketName:test-cloudstack,httpsFlag:false,created:Aug
26, 2014 8:16:24
PM,enableRRS:false,maxSingleUploadSizeInBytes:5368709120}},url:
http://download.cloud.com/templates/builtin/centos56-x86_64.vhd.bz2,format:VHD,accountId:2,name:209-2-b624436c-5f37-30d4-8eaf-81582eb0d39d,wait:0}}]
}
2014-08-26 20:41:07,556 DEBUG [c.c.a.t.Request]
(AgentManager-Handler-10:null) Seq 10-5684105679694996125: Processing:  {
Ans: , MgmtId: 52242179434, via: 10, Ver: v1, Flags: 10,
[{com.cloud.agent.api.storage.DownloadAnswer:{jobId:d43a17c9-3b03-4ff9-8906-e1d155981e86,downloadPct:0,errorString:No
route to
host,downloadStatus:DOWNLOAD_ERROR,installPath:template/tmpl/2/209/209-2-b624436c-5f37-30d4-8eaf-81582eb0d39d,templateSize:0,templatePhySicalSize:0,result:true,details:No
route to host,wait:0}}] }

but i don't see any logging happening in secondary storage vm's cloud.log

not sure this error is happening due to S3!


thanks!

Re: S3/Swift Problem around Virtual Size

2014-08-25 Thread Punith S

thanks for opening this thread mike,

since i only use nfs as my secondary storage provider, i didn't see this
issue till date.

is this issue occurring even using a S3 secondary storage with staging nfs
store ?

if so like edison pointed we need to fetch the virtual size from the nfs
store instead of S3 in the deploymentmanager.

thanks


On Sat, Aug 23, 2014 at 3:45 AM, Mike Tutkowski 
mike.tutkow...@solidfire.com wrote:

 Hey Edison,

 Do you know how difficult/easy of a fix this is, who might be available to
 put this fix in, and for what release (hopefully 4.4.1) this fix could find
 its way in?

 Thanks!
 Mike


 On Fri, Aug 22, 2014 at 3:37 PM, Francois Gaudreault 
 fgaudrea...@cloudops.com wrote:

  Min,
 
  Ok, but this is not the behavior I see. Even without requesting a VM
  create, the template is pushed to the staging NFS at least once. Is it
  downloaded there or pushed after download, that I am not sure. I was
  assuming the swift upload bash script was executed after the template is
 on
  the staging.
 
  Anyway... the focus is on the virt size, and you all know the code better
  than I do :)
 
  FG
  On Aug 22, 2014 5:28 PM, Min Chen min.c...@citrix.com wrote:
 
  No. For S3/Swift, register template will directly upload templates to S3
  without going through staging NFS. It will only be copied to staging NFS
  when we first use that template to provision a VM.
 
  Thanks
  -min
 
  On 8/22/14 2:25 PM, Francois Gaudreault fgaudrea...@cloudops.com
  wrote:
 
  Edison,
  
  Isnt the templates downloaded to the Staging NFS first?
  
  FG
  On Aug 22, 2014 5:20 PM, Edison Su edison...@citrix.com wrote:
  
   I know the reason why the size of template doesn¹t have correct
 virtual
   size if it¹s registered in S3/Swift:
   In case of s3/swift, the template is directly stored into s3/swift
  through
   swift/s3 api, there is no place for cloudstack to look into template,
  to
   find out the virtual size during template registration.
   While, if secondary storage is NFS, the template is first stored on
   NFS(which has file system), cloudstack can unzip the template(if
 it¹s a
   zipped file), and read virtual size from the file, then report back
 to
  mgt
   server.
   In order to fix it, we can add some code as: all the templates
  registered
   on Swift/S3, need to be downloaded to a NFS intermediate storage
 before
  it
   can be consumed by primary storage. After the download finished, then
  we
   check virtual size of template, and report back to mgt server/update
 DB
  etc.
  
   From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
   Sent: Friday, August 22, 2014 1:38 PM
   To: dev@cloudstack.apache.org
   Cc: Edison Su
   Subject: S3/Swift Problem around Virtual Size
  
   Hi,
  
   This was brought up in a different e-mail thread, but I wanted to
 make
  it
   more clear that it's related to CloudStack's download code around
  S3/Swift,
   so I'm opening up a new thread.
  
   Francois (from CloudOps) noticed today that when he downloaded a
  template
   (VHD format) to Swift (but it looks like the same applies for S3)
 that
  the
   physical and virtual sizes are set to be the same.
  
   This appears to have the following consequence:
  
   You can download a template with a physical size of, say, 3 GB and a
  root
   disk that's supposed to be, say, 20 GB. Instead of the virtual size
  showing
   as 20 GB, it shows as 3 GB.
  
   This is not an issue with NFS. In that situation, the two sizes are
   correctly accounted for.
  
   What later can happen is the template is downloaded from Swift and
  takes
   up an unexpected amount of space on the XenServer storage repository
  (SR).
  
   If there is enough space on the SR, this isn't too big of a deal.
  However,
   for so-called managed storage plug-ins (examples are SolidFire and
   CloudByte), this will lead to them dynamically creating a SAN volume
 of
  the
   wrong size.
  
   Francois opened up the following ticket:
  
   https://issues.apache.org/jira/browse/CLOUDSTACK-7406
  
   Thanks!
  
   --
   Mike Tutkowski
   Senior CloudStack Developer, SolidFire Inc.
   e: mike.tutkow...@solidfire.commailto:mike.tutkow...@solidfire.com
   o: 303.746.7302
   Advancing the way the world uses the cloud
   http://solidfire.com/solution/overview/?video=play
  
 
 


 --
 *Mike Tutkowski*
 *Senior CloudStack Developer, SolidFire Inc.*
 e: mike.tutkow...@solidfire.com
 o: 303.746.7302
 Advancing the way the world uses the cloud
 http://solidfire.com/solution/overview/?video=play*™*




-- 
regards,

punith s
cloudbyte.com

Re: [GSOC] [CLOUDSTACK-6045] Final update

2014-08-20 Thread Punith S

nice work seif, thumbs up :)


On Wed, Aug 20, 2014 at 2:00 PM, ilya musayev ilya.mailing.li...@gmail.com
wrote:

 Wanted to add to Sebastian's comment your work is very much appreciated.
 We hope you stay with us in the future.


 On 8/20/14, 12:54 AM, Sebastien Goasguen wrote:

 Great work Seif, thanks for the slides.

 I hope you stay involved with the community.

 -sebastien

 On Aug 19, 2014, at 10:26 PM, Seif Eddine Jemli 
 seifeddineje...@gmail.com wrote:

  Hi everyone,

 As you probably know, I have worked on this project whose goal is making
 the GUI support adding primary storage to CS that is based on storage
 plug-ins.

 https://cwiki.apache.org/confluence/display/CLOUDSTACK/
 Create+GUI+to+add+primary+storage+based+on+plug-ins

 The pencils down firm deadline was Monday the 18th. I spent yesterday
 preparing a presentation that summarizes my GSoC tasks from this summer.

 Here is the link to the presentation:

 http://fr.slideshare.net/seif_100/seif-mike-gsoc2014cloudstack
 http://www.facebook.com/l.php?u=http%3A%2F%2Ffr.
 slideshare.net%2Fseif_100%2Fseif-mike-gsoc2014cloudstackh=QAQEcJBPc



 I have worked mainly on two tasks:

 * The first task I worked on was adding support into CloudStack's GUI to
 enable admins to add Primary Storage that is based on a custom plug-in.
 Prior to this, admins needed to perform this task either via CloudStack's
 CLI, its API, or some other tool that leveraged CloudStack's CLI or its
 API.

 * The other task was adding the following GUI control to CloudStack:

 http://loopj.com/jquery-tokeninput/

 This control replaces the need for admins to type in a comma-separated
 list
 of what CloudStack calls storage tags (we were also able to apply this
 control to what CloudStack calls host tags).

 As part of this process, I needed to create two new API calls to
 CloudStack
 and invoke them from the GUI. These API calls retrieve the current list
 of
 storage tags or host tags and populate them into the GUI control. The
 admin
 can then either select one or more existing tags and/or add new ones.
 Overall, this feature will make it much easier for admins to avoid input
 errors.

 GUI forms that make use of this new control include the following:

 -Add Primary Storage

 -Add Host

 -Add Compute Offering

 -Add Disk Offering

 Two detail views make use of this new control for editing tags:

 -Edit mode for a primary storage

 -Edit mode for a host

 These two tasks were completely fulfilled, and I hope that they will be
 useful for the CloudStack admins.

 I would like to thank my mentor, Mike Tutkowski, for his help and
 guidance
 during the project. I would also like to thank the Apache Cloudstack
 Community members for their helpful answers.

 The GSoC experience was very good overall, with especially a lot of
 learning. That being the case, I'll probably apply next year for another
 project.

 Beyond GSoC, I am thinking of modifying the URL input on the Add Primary
 Storage form to make it more user friendly by accepting key-value
 inputs.

 Thanks everyone,

 Seif





-- 
regards,

punith s
cloudbyte.com

Re: Fast way to rebuild the GUI?

2014-08-09 Thread Punith S

hi mike,

you can just replace the js file in
cloudstack-management/webapps/client/scripts/ folder and reload the
browser, js file will be reloaded in the cloudstack ui.

thanks.


On Sat, Aug 9, 2014 at 11:32 AM, Mike Tutkowski 
mike.tutkow...@solidfire.com wrote:

 Hi,

 When you change a JavaScript file for the GUI, is there a fast way to
 update the management server with this file short of having to rebuild the
 entire codebase?

 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
 http://solidfire.com/solution/overview/?video=play*™*




-- 
regards,

punith s
cloudbyte.com

Re: Fast way to rebuild the GUI?

2014-08-09 Thread Punith S

hi mike,

mvn -P developer -*pl* :cloud-client-ui -DskipTests=true

i guess running this command only builds  the cloud-client-ui package,
ie client/target/cloud-client-ui-4.4.0-SNAPSHOT.war
but it won't be extracted to client/target/cloud-client-ui-4.4.0-SNAPSHOT

hence the new changes will not be reflected.

for an easy workaround you can scp the changed js file form your workspace
to the script folder in the running cloudstack and on refreshing the
browser will reflect the changes.

thanks.


On Sat, Aug 9, 2014 at 11:58 AM, Mike Tutkowski 
mike.tutkow...@solidfire.com wrote:

 I should clarify that that command runs successfully, but the GUI does not
 incorporate the new changes from running that command anymore.


 On Sat, Aug 9, 2014 at 12:12 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

  I could be wrong, but I thought we compressed JS files now.
 
  This used to work:
 
  mvn -P developer -pl :cloud-client-ui -DskipTests=true
 
  Unfortunately it no longer does.
 
 
  On Sat, Aug 9, 2014 at 12:08 AM, Punith S punit...@cloudbyte.com
 wrote:
 
  hi mike,
 
  you can just replace the js file in
  cloudstack-management/webapps/client/scripts/ folder and reload the
  browser, js file will be reloaded in the cloudstack ui.
 
  thanks.
 
 
  On Sat, Aug 9, 2014 at 11:32 AM, Mike Tutkowski 
  mike.tutkow...@solidfire.com wrote:
 
   Hi,
  
   When you change a JavaScript file for the GUI, is there a fast way to
   update the management server with this file short of having to rebuild
  the
   entire codebase?
  
   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
   http://solidfire.com/solution/overview/?video=play*™*
  
 
 
 
  --
  regards,
 
  punith s
  cloudbyte.com
 
 
 
 
  --
  *Mike Tutkowski*
  *Senior CloudStack Developer, SolidFire Inc.*
  e: mike.tutkow...@solidfire.com
  o: 303.746.7302
  Advancing the way the world uses the cloud
  http://solidfire.com/solution/overview/?video=play*™*
 



 --
 *Mike Tutkowski*
 *Senior CloudStack Developer, SolidFire Inc.*
 e: mike.tutkow...@solidfire.com
 o: 303.746.7302
 Advancing the way the world uses the cloud
 http://solidfire.com/solution/overview/?video=play*™*




-- 
regards,

punith s
cloudbyte.com

Re: Import Template: qcow2

2014-08-08 Thread Punith S

hi mo,

you can put your centos qcow2 template in webapps/client directory and give
the registration url as http://xx.xx.xx.243:8080/client/
a22ed0a2-9285-42da-bc34-fc4e71d48910.qcow2 while registering the template
or you can create a simple python web server in centos and upload the
template.
be sure to give the exact os conf of the template.

thanks


On Sat, Aug 9, 2014 at 12:51 AM, mo m...@daoenix.com wrote:

 Hello,

 Question, I previously saved a CentOS 6.5 template (e.g. downloaded) and I
 got the file: a22ed0a2-9285-42da-bc34-fc4e71d48910.qcow2 on my local
 machine. I then uploaded it to my new install of CloudStack 4.4, but it
 won’t boot, it hangs at ‘Booting from Hard drive’, when I registered the
 template it “uploaded” rapidly, when it is in fact 2.2 gigs in size.

 How do you import templates? Because obviously this is not accurate how I
 proceeded.

 - Mo




-- 
regards,

punith s
cloudbyte.com

Re: [ANNOUNCE] Rajani Karuturi as committer

2014-07-22 Thread Punith S

Congrats Rajani :)

cheers!


On Tue, Jul 22, 2014 at 12:04 PM, Suresh Sadhu suresh.sa...@citrix.com
wrote:

 Congrats Rajani.

 -Original Message-
 From: Shweta Agarwal [mailto:shweta.agar...@citrix.com]
 Sent: 22 July 2014 11:57
 To: dev@cloudstack.apache.org
 Subject: RE: [ANNOUNCE] Rajani Karuturi as committer

 Congrats Rajani .. well Deserved ..

 -Original Message-
 From: Prasanna Santhanam [mailto:t...@apache.org]
 Sent: Tuesday, July 22, 2014 11:53 AM
 To: CloudStack Dev
 Subject: [ANNOUNCE] Rajani Karuturi as committer

 The Project Management Committee (PMC) for Apache CloudStack has asked
 Rajani Karuturi to become a committer and we are pleased to announce that
 she has accepted. Being a committer allows many contributors to contribute
 more autonomously. For developers, it makes it easier to submit changes and
 eliminates the need to have contributions reviewed via the patch submission
 process. Whether contributions are development-related or otherwise, it is
 a recognition of a contributor's participation in the project and
 commitment to the project and the Apache Way.

 Please join me in congratulating Rajani

 --
 Prasanna., on behalf of the CloudStack PMC

 
 Powered by BigRock.com




-- 
regards,

punith s
cloudbyte.com

Re: Review Request 23410: Improvised CloudByte Storage Plugin for 4.5 and above. jira id : CLOUDSTACK-7098

2014-07-18 Thread punith s



 On July 18, 2014, 9:36 a.m., Mike Tutkowski wrote:
  Ship It!
 
 Mike Tutkowski wrote:
 Changes were put into ACS repo with this commit:
 
 f3cbb699955243007ffb53b335d9508b2e422a06

sure thanks mike :)


- punith


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


On July 15, 2014, 7:48 p.m., punith s wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/23410/
 ---
 
 (Updated July 15, 2014, 7:48 p.m.)
 
 
 Review request for cloudstack, amit kumar das, edison su, and Mike Tutkowski.
 
 
 Repository: cloudstack-git
 
 
 Description
 ---
 
 The new improvised cloudbyte plugin for cloudstack supports the following 
 features
 
 * support for managed storage, where each vm disk has the guaranteed QoS.
 
 * supports resize of the volume.
 
 * supports both iscsi and nfs protocols in XEN server, and iscsi protocol for 
 KVM and vmware ESX with respect to managed storage.
 
 * supports storage level snapshot capabilites as well as hypervisor level 
 snapshot feature.
 
 * also exposing the custom api's for better ui integration.
 
 * support for unlimited storage nodes across the sites.
 
 * account integration in cloudbyte with respect to domains in cloudstack.
 
 
 Diffs
 -
 
   
 plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
  87c5f51 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java
  99d1e2a 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
  33004e3 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorHostListener.java
  de4711a 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorPrimaryDataStoreProvider.java
  e591082 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorUtil.java
  b75d12a 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiService.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiServiceImpl.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceCmd.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceResponse.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolCmd.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolResponse.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeCmd.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeResponse.java
  PRE-CREATION 
 
 Diff: https://reviews.apache.org/r/23410/diff/
 
 
 Testing
 ---
 
 system testing done.
 
 
 Thanks,
 
 punith s

Re: Review Request 23410: Improvised CloudByte Storage Plugin for 4.5 and above. jira id : CLOUDSTACK-7098

2014-07-16 Thread punith s



 On July 16, 2014, 10:25 a.m., Mike Tutkowski wrote:
  server/src/com/cloud/configuration/Config.java, line 1942
  https://reviews.apache.org/r/23410/diff/2/?file=628420#file628420line1942
 
  Perhaps I'm having trouble with Review Board, but it appears there are 
  still CloudByte-specific values in 
  server/src/com/cloud/configuration/Config.java.
  
  I see that they get inserted from 
  ElastistorPrimaryDataStoreProvider.java, as well.
  
  Isn't ElastistorPrimaryDataStoreProvider.java the only place we want to 
  insert them from?
  
  Thanks for clarifying

hi mike,

i guess you might be referring to an older diff revision or some problem with 
the review board!
you can verify revision 3 in this link where i see config.java has been 
removed, https://reviews.apache.org/r/23410/diff/
also you can get the raw diff from https://reviews.apache.org/r/23410/diff/raw/

thanks
 


- punith


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


On July 15, 2014, 7:48 p.m., punith s wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/23410/
 ---
 
 (Updated July 15, 2014, 7:48 p.m.)
 
 
 Review request for cloudstack, amit kumar das, edison su, and Mike Tutkowski.
 
 
 Repository: cloudstack-git
 
 
 Description
 ---
 
 The new improvised cloudbyte plugin for cloudstack supports the following 
 features
 
 * support for managed storage, where each vm disk has the guaranteed QoS.
 
 * supports resize of the volume.
 
 * supports both iscsi and nfs protocols in XEN server, and iscsi protocol for 
 KVM and vmware ESX with respect to managed storage.
 
 * supports storage level snapshot capabilites as well as hypervisor level 
 snapshot feature.
 
 * also exposing the custom api's for better ui integration.
 
 * support for unlimited storage nodes across the sites.
 
 * account integration in cloudbyte with respect to domains in cloudstack.
 
 
 Diffs
 -
 
   
 plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
  87c5f51 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java
  99d1e2a 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
  33004e3 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorHostListener.java
  de4711a 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorPrimaryDataStoreProvider.java
  e591082 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorUtil.java
  b75d12a 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiService.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiServiceImpl.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceCmd.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceResponse.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolCmd.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolResponse.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeCmd.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeResponse.java
  PRE-CREATION 
 
 Diff: https://reviews.apache.org/r/23410/diff/
 
 
 Testing
 ---
 
 system testing done.
 
 
 Thanks,
 
 punith s

Question regarding Quiesce VM feature in ACS 4.3 wrt XEN hypervisor

2014-07-16 Thread Punith S

hi,

while i was referring the ACS 4.3 doc for VM snapshot,
i see a feature Quiesce VM supported only by vmware hypervisor if the
cloudstack default primary storage is used,
but it also mentions that Quiesce VM can be supported if you are using a
third party primary storage plugin, the quiesce operation is provided by
plugin implementation!

is Quiesce VM is a limitation of  XEN hypervisor or is it not implemented
by xen agent in cloudstack ?

how is third party primary storage plugin related to hypervisor feature ?

-- 
regards,

punith s
cloudbyte.com

Re: Volume provisioning type in createDiskOffering API

2014-07-16 Thread Punith S

hi gaurav,

noji has written a document on this.
refer this link -
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Volume+provisioning+type+option

thanks


On Wed, Jul 16, 2014 at 2:06 PM, Gaurav Aradhye gaurav.arad...@clogeny.com
wrote:

 Hi,

 I believe this feature is in master branch, but I don't see the
 provisioningtype parameter in createDiskOffering API. Any idea why? I can
 see it defined in CreateDiskOfferingCmd.java file.


 Regards,
 Gaurav




-- 
regards,

punith s
cloudbyte.com

Re: Review Request 23410: Improvised CloudByte Storage Plugin for 4.5 and above. jira id : CLOUDSTACK-7098

2014-07-15 Thread punith s



 On July 14, 2014, 11:16 p.m., Mike Tutkowski wrote:
  From an e-mail I sent to dev@ about vendor-specific config values:
  
  
  Alena Prokharchyk via cloudstack.apache.org 
  10:42 AM (1 hour ago)
  
  to dev 
  Mike, may be you already know this info, putting it here in case someone
  is not aware of that. When global config variables are plugin specific,
  they have to inserted by the manager from your plugin; they should never
  be put to Config.java class.
  
  To implement it, make your manager implement Configurable.java. Here is
  the FS explaining it in more details:
  https://cwiki.apache.org/confluence/display/CLOUDSTACK/Configuration

hi mike,

thanks for the update, considering that the plugin specific configurations to 
be inserted from the plugin manager, i'm now inserting the cloudbyte global 
config from the provider while the plugin is been configured or installed.

thanks.  


- punith


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


On July 11, 2014, 6:12 p.m., punith s wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/23410/
 ---
 
 (Updated July 11, 2014, 6:12 p.m.)
 
 
 Review request for cloudstack, amit kumar das, edison su, and Mike Tutkowski.
 
 
 Repository: cloudstack-git
 
 
 Description
 ---
 
 The new improvised cloudbyte plugin for cloudstack supports the following 
 features
 
 * support for managed storage, where each vm disk has the guaranteed QoS.
 
 * supports resize of the volume.
 
 * supports both iscsi and nfs protocols in XEN server, and iscsi protocol for 
 KVM and vmware ESX with respect to managed storage.
 
 * supports storage level snapshot capabilites as well as hypervisor level 
 snapshot feature.
 
 * also exposing the custom api's for better ui integration.
 
 * support for unlimited storage nodes across the sites.
 
 * account integration in cloudbyte with respect to domains in cloudstack.
 
 
 Diffs
 -
 
   
 plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
  87c5f51 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java
  99d1e2a 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
  33004e3 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorHostListener.java
  de4711a 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorPrimaryDataStoreProvider.java
  e591082 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorUtil.java
  b75d12a 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiService.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiServiceImpl.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceCmd.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceResponse.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolCmd.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolResponse.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeCmd.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeResponse.java
  PRE-CREATION 
   server/src/com/cloud/configuration/Config.java fbcb1f4 
 
 Diff: https://reviews.apache.org/r/23410/diff/
 
 
 Testing
 ---
 
 system testing done.
 
 
 Thanks,
 
 punith s

Re: Review Request 23410: Improvised CloudByte Storage Plugin for 4.5 and above. jira id : CLOUDSTACK-7098

2014-07-15 Thread punith s


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

(Updated July 15, 2014, 7:48 p.m.)


Review request for cloudstack, amit kumar das, edison su, and Mike Tutkowski.


Changes
---

inserting the cloudbyte global configurations from the plugin provider instead 
of config.java, also supporting the update api for storage pool.


Repository: cloudstack-git


Description
---

The new improvised cloudbyte plugin for cloudstack supports the following 
features

* support for managed storage, where each vm disk has the guaranteed QoS.

* supports resize of the volume.

* supports both iscsi and nfs protocols in XEN server, and iscsi protocol for 
KVM and vmware ESX with respect to managed storage.

* supports storage level snapshot capabilites as well as hypervisor level 
snapshot feature.

* also exposing the custom api's for better ui integration.

* support for unlimited storage nodes across the sites.

* account integration in cloudbyte with respect to domains in cloudstack.


Diffs (updated)
-

  
plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
 87c5f51 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java
 99d1e2a 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
 33004e3 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorHostListener.java
 de4711a 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorPrimaryDataStoreProvider.java
 e591082 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorUtil.java
 b75d12a 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiService.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiServiceImpl.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceResponse.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolResponse.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeResponse.java
 PRE-CREATION 

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


Testing
---

system testing done.


Thanks,

punith s

Re: feature : changing volume properties dynamically in 4.5

2014-07-14 Thread Punith S

sure mike.
thanks :)


On Fri, Jul 11, 2014 at 9:18 PM, Mike Tutkowski 
mike.tutkow...@solidfire.com wrote:

 Just an FYI that I was busy the past week working on building integration
 tests for SolidFire-related functionality that's executed in CloudStack,
 but I plan to get back to this resizeVolume API work today.


 On Wed, Jun 25, 2014 at 10:27 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 Hi Punith,

 Yes, that is exactly the approach I was planning on taking: enhance the
 resizeVolume API to allow for IOPS control and to extend what it can do
 with volume sizes.

 Talk to you later!
 Mike


 On Wed, Jun 25, 2014 at 7:44 AM, Punith S punit...@cloudbyte.com wrote:

 hi mike,

 now this updateStoragePool API would be really helpful to update the
 backend storagepool and other third party features.

 question on individual CloudStack volumes
  is it feasible to associate resize volume and changing IOPS into one
 API ?

 if so we might need to add more intelligence in the design to make sure
 disk is not detached if only IOPS is being modified in the select new disk
 offering
 else disk shall be detached if both size and IOPS vary in the selected
 new disk offering.

 thanks.


 On Wed, Jun 25, 2014 at 2:25 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 OK, I've completed work on enabling a storage plug-in to be notified
 when the size and/or IOPS of the primary storage that it represents is
 changed:


 https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=c344693e48d80313270d1a972b0a3badf315567d

 This is related to the updateStoragePool API.

 I plan to switch my focus now to the resizeVolume API so that
 individual CloudStack volumes (as opposed to the entire storage pool they
 are from) can have not only their size, but their IOPS updated.


 On Fri, Jun 20, 2014 at 12:31 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 I'll define constants for the keys in PrimaryDataStoreLifeCycle.


 On Friday, June 20, 2014, Mike Tutkowski mike.tutkow...@solidfire.com
 wrote:

 In fact, we do use a hash-map approach for some KVM storage code, too.

 Let's do that here, as well.

 I'll make that change.

 Thanks

 On Friday, June 20, 2014, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 We do - in some places in the code - use a hash map...like what you
 describe.

 I guess the trade off there would be that the values that contain
 our numbers would end up being high-level objects instead of numbers
 (because we don't really know what future values might be).

 I'm OK with either approach.

 On Friday, June 20, 2014, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 Unfortunately, at the time being, the updateStoragePool API (from
 the public-facing API) only takes in bytes, IOPS, and storage 
 tags...not
 details (createStoragePool takes in a lot more parameters...including
 details).

 So - for now at least - we're a little limited in what the new
 interface method can tell storage providers about (unless we wanted to
 spend time adding to the parameter list of updateStoragePool).

 On Friday, June 20, 2014, Amit Das amit@cloudbyte.com wrote:

 Hi Mike,

 Is there any use case to have a more generic signature for
 updateStoragePool API ?

 e.g
 void updateStoragePool(StoragePool storagePool, MapE,V
 updateDetails);
 // not too sure of what should be E  V as of now. To start with E
  V can be String types or Enums for better static checks.

 instead of below
 void updateCapacity(StoragePool storagePool, Long capacityBytes, L
 ong capacityIops);

 

 Regards,
 Amit
 *CloudByte Inc.* http://www.cloudbyte.com/


 On Fri, Jun 20, 2014 at 10:37 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 I just wanted to update those who are interested in this thread
 about work I've done on this over the past couple days.

 This gist is that I've added a new method to the
 PrimaryDataStoreLifeCycle interface that has the following signature 
 (this
 code is not yet checked in):

 void updateCapacity(StoragePool storagePool, Long capacityBytes,
 Long capacityIops);

 This method can be invoked from StorageManagerImpl when the
 updateStoragePool API is called.

 This gives the storage plug-in that backs the primary storage in
 question an opportunity to update the backend storage it represents, 
 if
 that makes sense to do in your particular case (for example, 
 changing the
 size and/or IOPS of a volume).

 There is a related enhancement to the resizeVolume API that I
 plan to tackle next week. That one will be particularly useful for 
 managed
 storage plug-ins.

 Also, I have been collecting input on the generic key/value
 proposal here:


 https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=42566111

 That may turn into a considerable amount of work. I was initially
 thinking it could be fit into 4.5, but it might be 4.6.

 Thanks for any feedback!


 On Thu, Jun 12, 2014 at 11:09 PM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote

Re: Cannot release reservation

2014-07-11 Thread Punith S

hi,

try restarting the MS and see whether agent and MS are in sync.
also check the ssvm by running the health script by logging into to the
ssvm.
for more troubleshooting refer this link
https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM%2C+templates%2C+Secondary+storage+troubleshooting

thanks


On Fri, Jul 11, 2014 at 11:50 AM, Tejas Gadaria refond.g...@gmail.com
wrote:

 Hi,

 Due to power blackout i have to recreate ssvm  cpvm, i am able to deploy
 new vms also create new template but on System Capacity,  General  Alerts
 area, latest alerts are not populating.

 Also ssvm  cpvm status is 'running' but Agent state is not displayed in
 Cloudstack UI.

 I have production VMs running on ACS. how can i recreate ssvm  cpvm. ?

 I am using ACS 4.3  Xenserver 6.2 SP1

 Regards,
 Tejas


 On Thu, Jul 10, 2014 at 6:30 PM, Tejas Gadaria refond.g...@gmail.com
 wrote:

  Hi,
 
  I am getting below logs on CS 4.3 on Xenserver 6.2 SP1
  i m getting huge amount of of memory allocated to vms, where it is not
  actully..
 
  2014-07-10 16:43:16,643 DEBUG [c.c.a.AlertManagerImpl]
  (CapacityChecker:ctx-d205d3de) Done executing storage capacity update
  2014-07-10 16:43:16,643 DEBUG [c.c.a.AlertManagerImpl]
  (CapacityChecker:ctx-d205d3de) Executing capacity updates for public ip
 and
  Vlans
  2014-07-10 16:43:16,686 DEBUG [c.c.a.AlertManagerImpl]
  (CapacityChecker:ctx-d205d3de) Done capacity updates for public ip and
 Vlans
  2014-07-10 16:43:16,686 DEBUG [c.c.a.AlertManagerImpl]
  (CapacityChecker:ctx-d205d3de) Executing capacity updates for private ip
  2014-07-10 16:43:16,701 DEBUG [c.c.a.AlertManagerImpl]
  (CapacityChecker:ctx-d205d3de) Done executing capacity updates for
 private
  ip
  2014-07-10 16:43:16,701 DEBUG [c.c.a.AlertManagerImpl]
  (CapacityChecker:ctx-d205d3de) Done recalculating system capacity
  2014-07-10 16:43:16,705 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
  (HostReservationReleaseChecker:ctx-0828f975) Checking if any host
  reservation can be released ...
  2014-07-10 16:43:16,720 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
  (HostReservationReleaseChecker:ctx-0828f975) Cannot release reservation,
  Found 4 VMs Running on
 
  host 1
  2014-07-10 16:43:16,727 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
  (HostReservationReleaseChecker:ctx-0828f975) Cannot release reservation,
  Found 4 VMs Running on
 
  host 5
  2014-07-10 16:43:16,732 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
  (HostReservationReleaseChecker:ctx-0828f975) Cannot release reservation,
  Found 1 VMs Running on
 
  host 6
  2014-07-10 16:43:16,732 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
  (HostReservationReleaseChecker:ctx-0828f975) Done running
  HostReservationReleaseChecker ...
 




-- 
regards,

punith s
cloudbyte.com

Review Request 23410: Improvised CloudByte Storage Plugin for 4.5 and above. jira id : CLOUDSTACK-7098

2014-07-11 Thread punith s


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

Review request for cloudstack, amit kumar das, edison su, and Mike Tutkowski.


Repository: cloudstack-git


Description
---

The new improvised cloudbyte plugin for cloudstack supports the following 
features

* support for managed storage, where each vm disk has the guaranteed QoS.

* supports resize of the volume.

* supports both iscsi and nfs protocols in XEN server, and iscsi protocol for 
KVM and vmware ESX with respect to managed storage.

* supports storage level snapshot capabilites as well as hypervisor level 
snapshot feature.

* also exposing the custom api's for better ui integration.

* support for unlimited storage nodes across the sites.

* account integration in cloudbyte with respect to domains in cloudstack.


Diffs
-

  
plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
 87c5f51 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java
 99d1e2a 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
 33004e3 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorHostListener.java
 de4711a 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorPrimaryDataStoreProvider.java
 e591082 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorUtil.java
 b75d12a 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiService.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiServiceImpl.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceResponse.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolResponse.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeResponse.java
 PRE-CREATION 
  server/src/com/cloud/configuration/Config.java fbcb1f4 

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


Testing
---

system testing done.


Thanks,

punith s

Re: Review Request 23410: Improvised CloudByte Storage Plugin for 4.5 and above. jira id : CLOUDSTACK-7098

2014-07-11 Thread punith s


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

(Updated July 11, 2014, 6:12 p.m.)


Review request for cloudstack, amit kumar das, edison su, and Mike Tutkowski.


Changes
---

fixed a glitch in updating the used bytes.


Repository: cloudstack-git


Description
---

The new improvised cloudbyte plugin for cloudstack supports the following 
features

* support for managed storage, where each vm disk has the guaranteed QoS.

* supports resize of the volume.

* supports both iscsi and nfs protocols in XEN server, and iscsi protocol for 
KVM and vmware ESX with respect to managed storage.

* supports storage level snapshot capabilites as well as hypervisor level 
snapshot feature.

* also exposing the custom api's for better ui integration.

* support for unlimited storage nodes across the sites.

* account integration in cloudbyte with respect to domains in cloudstack.


Diffs (updated)
-

  
plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
 87c5f51 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java
 99d1e2a 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
 33004e3 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorHostListener.java
 de4711a 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorPrimaryDataStoreProvider.java
 e591082 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorUtil.java
 b75d12a 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiService.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorVolumeApiServiceImpl.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorInterfaceResponse.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorPoolResponse.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeCmd.java
 PRE-CREATION 
  
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ListElastistorVolumeResponse.java
 PRE-CREATION 
  server/src/com/cloud/configuration/Config.java fbcb1f4 

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


Testing
---

system testing done.


Thanks,

punith s

Re: How to change primary storage

2014-07-06 Thread Punith S

hi,

can you try updating the ip address(host_address) of your primary storage
in storage_pool table and check the logs for the storage status whether
things are working fine.

thanks.


On Mon, Jul 7, 2014 at 10:37 AM, Giri Prasad g_p...@yahoo.com.invalid
wrote:

 Thanks.

 I want to change the primary storage IP address from http://XXX.XXX.1.5
 to http://XXX.XXX.1.20. Also, I need to change the primary storage
 directory, from /export/aa to /export/dd.  What is the procedure?



 
  From: Prashant Kumar Mishra prashantkumar.mis...@citrix.com
 To: Giri Prasad g_p...@yahoo.com; dev@cloudstack.apache.org 
 dev@cloudstack.apache.org; us...@cloudstack.apache.org 
 us...@cloudstack.apache.org
 Sent: Monday, 7 July 2014 10:30 AM
 Subject: RE: How to change primary storage


 For error like The storage pool will not be used but cleanup is needed
 you should check global settings global.clenup.interaval  ,For quick
 cleanup you can set it to 300ms and check  parameter related to cleanup
 like storage.template.cleanup.enable  , storage cleanup enabled etc. If
 global settings are properly tuned I don't think  any database
 modifications required

 -cloud.volume  stores volumes information , if you are not able to delete
 storage becausevolume still exist on the storage change the volume state
 and delete.

 - storage_pool, storage_pool_view  for primary storage

 Thanks
 Prashant


 -Original Message-
 From: Giri Prasad [mailto:g_p...@yahoo.com]
 Sent: Monday, July 07, 2014 10:00 AM
 To: Prashant Kumar Mishra; dev@cloudstack.apache.org;
 us...@cloudstack.apache.org
 Subject: Re: How to change primary storage

 Hello,

 Thanks for suggestion, which I will try.

 Btw, I saw a lead as:
 http://comments.gmane.org/gmane.comp.apache.cloudstack.user/7000
 Which says :

 when I've had issues deleting primary storages in the past, I've ended up
 having to delete volumes that were still associated with the datastore from
 the cloud.volumes table.

 Is cloud.volumes the mysql table, where all the primary/secondary storage
 setups are stored? Or what is the exact db.tablename which stores the
 primary/secondary storage setups?


 Regards,
 D.Giriprasad



 - Original Message -
 From: Prashant Kumar Mishra prashantkumar.mis...@citrix.com
 To: dev@cloudstack.apache.org dev@cloudstack.apache.org; Giri Prasad 
 g_p...@yahoo.com; us...@cloudstack.apache.org 
 us...@cloudstack.apache.org
 Cc:
 Sent: Sunday, 6 July 2014 9:42 AM
 Subject: RE: How to change primary storage


 I would suggest add you new  primary storage ,migrate volumes  from old
 storage to new storage and  then remove ur old primary storage after
 enabling  maintenance mode.

 Thanks
 Prashant



 -Original Message-
 From: Giri Prasad [mailto:g_p...@yahoo.com.INVALID]
 Sent: Saturday, July 05, 2014 10:16 AM
 To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
 Subject: How to change primary storage

 Hello All,

  I installed CS 4.1 on ubuntu, with primary storage in /export/aa and
 secondary storage in /export/bb, both in the same hard disk as the
 management server of CS 4.1. The Ip of the server is  http://XXX.XXX.1.5.


  Recently, I configured the My Book Live Device, to the IP of
 http://XXX.XXX.1.20. I am able to mount this device to linux dir and view
 files on it.

  The CS 4.1 was installed before mounting this external My Book Live
 Device.

 Now I want to change the primary storage of the IP address from
 http://XXX.XXX.1.5 to http://XXX.XXX.1.20. Also, I need to change the
 primary storage directory.

  Can, anybody provide insights, on which Mysql table, should I update for
 CS 4.1 setup. Or is there a procedure, to change the primary storage
 settings via the CS 4.1 web interface gui?

 Thanks in advance.

 Regards,
 D.Giriprasad




-- 
regards,

punith s
cloudbyte.com

Re: [ANNOUNCE] Will Stevens as committer

2014-07-04 Thread Punith S

Congrats Will :)


On Fri, Jul 4, 2014 at 4:13 PM, Pierre-Luc Dion pd...@cloudops.com wrote:

 Congratulations Will ! 



 PL




-- 
regards,

punith s
cloudbyte.com

Fwd: [jira] [Created] (CLOUDSTACK-7003) Arithmetic exception while creating a vdi on nfs volume in managed storage.

2014-06-27 Thread Punith S

hi mike,

can you take a look at this logic, today i met an arithmetic exception(/ by
0) while creating a nfs volume.
any suggestions to calculate the maxNumberOfTries if the unavailableSrSpace
is equal to zero.

thanks


-- Forwarded message --
From: punith (JIRA) j...@apache.org
Date: Fri, Jun 27, 2014 at 11:57 AM
Subject: [jira] [Created] (CLOUDSTACK-7003) Arithmetic exception while
creating a vdi on nfs volume in managed storage.
To: cloudstack-iss...@incubator.apache.org


punith created CLOUDSTACK-7003:
--

 Summary: Arithmetic exception while creating a vdi on nfs
volume in managed storage.
 Key: CLOUDSTACK-7003
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7003
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the
default.)
  Components: Management Server
Affects Versions: 4.5.0
Reporter: punith


it seems we have a bug while creating a nfs disk on managed storage,

file - CitrixResourceBase.java
api - createVdi

long unavailableSrSpace = sr.getPhysicalUtilisation(conn);

6216long maxNumberOfTries = (totalSrSpace / unavailableSrSpace = 1) ?
(totalSrSpace / unavailableSrSpace) : 1;

since while creation nfs disk does not have a meta data written on it like
in iscsi , unavailableSrSpace might turn out to be 0(zero), hence throwing
an divide bt zero exception.
sometimes the unavailable



--
This message was sent by Atlassian JIRA
(v6.2#6252)



-- 
regards,

punith s
cloudbyte.com

Re: feature : changing volume properties dynamically in 4.5

2014-06-25 Thread Punith S

 Offering (i.e. neither size nor IOPS can be marked as custom) and when 
 the
 resize method of the storage plug-in is invoked, it will have a chance 
 to
 change the size and/or IOPS.

 I would say we should perform a bit of analysis in the CloudStack
 volume logic to NOT stop resize from being invoked on the storage 
 plug-in
 IF the volume size is the same, but the IOPS are different. This way 
 the
 volume can be online as long as the user is only changing the IOPS of 
 the
 volume.

 I also think it's only a problem for XenServer for the VDI to have
 its size changed dynamically.

 I plan to draw a flowchart for this soon. Once I do that I think it
 will be easier to talk in detail.

 Thanks!


 On Thu, Jun 12, 2014 at 12:59 PM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 From what I understand about the resizeVolume API, to change the
 size of a given volume, you must either:

 1) pass in a new Disk Offering (if the current Disk Offering the
 volume uses does not allow for a custom size)

 or

 2) pass in the ID of the volume and a new size (if the current
 Disk Offering the volume uses does allow for a custom size)

 Either way, if you are shrinking the volume's size, you then have
 to pass in 'true' for the 'shrinkok' parameter.

 One thing we should do is support this same concept with IOPS. At
 the time being, both Min and Max IOPS can be custom (set by user) or 
 non
 custom (set by admin). This is a direct parallel to custom size or
 non-custom size. If the user is using a non-custom IOPS setting and 
 wants
 to switch to a custom IOPS setting, he should be able to do so by 
 switching
 to a Disk Offering with custom IOPS. Of course we should support 
 doing this
 while the volume is attached.

 If arbitrary key/value pairs can be associated with Disk
 Offerings, then you should be able to get the new key/value pairs by
 switching to a new Disk Offering. We'd want to allow this to work 
 with the
 volume in the attached state, as well.

 Perhaps we should allow this all to happen online (volume
 attached) UNLESS doing what we're about to do will change the size of 
 the
 volume. Then we can fail the OP and tell them to detach the volume and
 re-run the OP.

 What are you thoughts on that?

 Also, I think volumeResize only works for data disks at the time
 being.

 In my mind, volumeResize is a bit of a misnomer now. We are really
 allowing the user to resize their Disk Offering now in terms of not 
 only
 size, but IOPS, and even arbitrary key/value pairs. This is still all 
 done
 by selecting a new Disk Offering (or - if you have a custom size or 
 custom
 IOPS disk offering already - by passing in the ID of the volume and 
 the new
 size and/or IOPS).

 Let's brainstorm on this a bit and see which way makes sense to go.

 Thanks!


 On Thu, Jun 12, 2014 at 9:48 AM, Punith S punit...@cloudbyte.com
 wrote:

 sure mike.

 and i have one question,

 which existing volume api are we gonna use for changing disk
 offerings(properties) dynamically ?
 since resize api will not allow unless the disk is detached !

 thanks.


 On Thu, Jun 12, 2014 at 11:37 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 Sounds good - let me give some thought as to how we should break
 up the work.

 My GSoC student from Tunisia will be helping us, as well.


 On Wed, Jun 11, 2014 at 8:34 AM, Punith S 
 punit...@cloudbyte.com wrote:

 yes it sounds good, thanks for the proposal mike,

 yeah right now i have implemented prototype of my proposal,
 since its not generic we shall implement your proposal for 4.5.
 on the other hand, for 4.5 i'm supporting nfs protocol and
 resize feature for managed storage in xenserver, now trying to 
 implement
 snapshot and support root disk for vm's.
 and yes if we can club together, i can start working on this
 proposal for data disk and get the prototype ready.
 what do you think ?

 thanks.


 On Wed, Jun 11, 2014 at 3:53 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 I'll send out a [PROPOSAL] e-mail so others who may not be
 following this e-mail thread have a better chance to comment on 
 the feature.


 On Tue, Jun 10, 2014 at 2:58 PM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 Here is that design document I was referring to, Punith:


 https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=42566111

 I've been working with a student in Tunisia who is
 participating in Google Summer of Code (GSoC) (I'm his mentor).

 He'll be working on part of this as will I. (He is also
 working on another related task not listed here.)

 Feel free to join us, if you have time available, as we can
 divide out coding and testing among the three of us.

 Talk to you later!
 Mike


 On Tue, Jun 10, 2014 at 10:18 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 I plan to draw up a design document surrounding generic
 key/value pairs today.

 Perhaps you can take a look at it when you have time, Punith?


 On Tue, Jun 10, 2014 at 10:06 AM

Re: CS 4.3 - Registering network-element plugin

hi pradeep,

the spring framework has been modularized in 4.3 onwards,
this link might help you in registering the new plugin.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Plug-ins%2C+Modules%2C+and+Extensions

thanks,


On Tue, Jun 24, 2014 at 11:57 AM, Pradeep Cloudstack 
pradeepcloudst...@yahoo.com.invalid wrote:

 Hi team,
 I need some help in registering network-element plugin in a 4.3
 installation.

 In 4.2 release, we used to make entries in componentContext.xml.

 However in 4.3, looks like there is a NetworkGuru Registry.
 How do we register our plugin here?

 -Pradeep




-- 
regards,

punith s
cloudbyte.com

Custom popup forms w.r.t Plugin Provider

hi,

I am in process of adding a new Add Primary Storage (specific to my Storage
plugin) form  whose labels  certain values will be different than the
current Default Provider's Add Primary Storage form.
also looping the GSoC'14
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Create+GUI+to+add+primary+storage+based+on+plug-ins

it seems adding more checks and if-else clauses in system.js will make it
more fragile and unmanageable.

use case:
since each vendor requires to use ui with their own specific params,

for example with add primary storage:
referring the attachment, popup form will be dynamically changed to have
different params wrt the selected storage providers.

hence instead of writing the vendor specific code inside system.js(common
file)
is it acceptable to modularize the code to different vendor specific js
files like in writing a third party UI plugin ?
ref -
https://cwiki.apache.org/confluence/display/CLOUDSTACK/UI+Plugin+Tutorial

thanks
-- 
regards,

punith s
cloudbyte.com

Re: CS 4.3 - Registering network-element plugin

hi pradeep,

can you make sure your jar is present in the cloud war.
to make this happen you have to register the dependency in the client
pom.xml file.

also you need to register your plugin in the plugin pom.xml file and make
sure the provider name matches.

thanks.

On Tue, Jun 24, 2014 at 12:38 PM, Pradeep Cloudstack
pradeepcloudst...@yahoo.com.invalid wrote:

Thanks Punith.
We had tried this.
However the jar file that is built didnot include the spring-*-context.xml
and module.properties
as a result of which our plugin didnot get registered.

We followed the approach that was taken for vxlan and created artifacts on
similar lines.

Can you pls help on what we are missing ?

-Pradeep

From: Punith S punit...@cloudbyte.com
To: cloudstack dev@cloudstack.apache.org; Pradeep Cloudstack
pradeepcloudst...@yahoo.com
Sent: Tuesday, June 24, 2014 12:11 PM
Subject: Re: CS 4.3 - Registering network-element plugin

hi pradeep,

the spring framework has been modularized in 4.3 onwards,
this link might help you in registering the new plugin.

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Plug-ins%2C+Modules%2C+and+Extensions

thanks,

On Tue, Jun 24, 2014 at 11:57 AM, Pradeep Cloudstack
pradeepcloudst...@yahoo.com.invalid wrote:

Hi team,
I need some help in registering network-element plugin in a 4.3
installation.

In 4.2 release, we used to make entries in componentContext.xml.

However in 4.3, looks like there is a NetworkGuru Registry.
How do we register our plugin here?

-Pradeep

--
regards,

punith s
cloudbyte.com

--
regards,

punith s
cloudbyte.com

Re: CS 4.3 - Registering network-element plugin

hi pradeep,

does the JuniperNetworkGuru.properties file contain your custom key value
pairs to be used in the plugin ?

thanks.


On Tue, Jun 24, 2014 at 2:56 PM, Pradeep Cloudstack 
pradeepcloudst...@yahoo.com.invalid wrote:

 Hi Punith,
 the war contains the jar file. Also, the names are correct.

 In out network-element pom.xml file, we had made entries to ensure that a
 property file
 is bundled with the jar

 ***
   build
  resources
resource
  directorysrc/directory
  filteringfalse/filtering
  includes
  includeJuniperNetworkGuru.properties/include
  /includes
/resource
  /resources
/build
 ***

 This seems to be causing the issue. If I remove this entry, I see that the
 spring.xml and module.properties
 are bundled in the jar, but our JuniperNetworkGuru.properties will not get
 bundled

 -Pradeep



 
  From: Punith S punit...@cloudbyte.com
 To: cloudstack dev@cloudstack.apache.org; Pradeep Cloudstack 
 pradeepcloudst...@yahoo.com
 Sent: Tuesday, June 24, 2014 12:55 PM
 Subject: Re: CS 4.3 - Registering network-element plugin


 hi pradeep,

 can you make sure your jar is present in the cloud war.
 to make this happen you have to register the dependency in the client
 pom.xml file.

 also you need to register your plugin in the plugin pom.xml file and make
 sure the provider name matches.

 thanks.



 On Tue, Jun 24, 2014 at 12:38 PM, Pradeep Cloudstack 
 pradeepcloudst...@yahoo.com.invalid wrote:

  Thanks Punith.
  We had tried this.
  However the jar file that is built didnot include the
 spring-*-context.xml
  and module.properties
  as a result of which our plugin didnot get registered.
 
  We followed the approach that was taken for vxlan and created artifacts
 on
  similar lines.
 
  Can you pls help on what we are missing ?
 
 
  -Pradeep
 
 
 
  
   From: Punith S punit...@cloudbyte.com
  To: cloudstack dev@cloudstack.apache.org; Pradeep Cloudstack 
  pradeepcloudst...@yahoo.com
  Sent: Tuesday, June 24, 2014 12:11 PM
  Subject: Re: CS 4.3 - Registering network-element plugin
 
 
  hi pradeep,
 
  the spring framework has been modularized in 4.3 onwards,
  this link might help you in registering the new plugin.
 
 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Plug-ins%2C+Modules%2C+and+Extensions
 
  thanks,
 
 
 
 
 
  On Tue, Jun 24, 2014 at 11:57 AM, Pradeep Cloudstack 
  pradeepcloudst...@yahoo.com.invalid wrote:
 
   Hi team,
   I need some help in registering network-element plugin in a 4.3
   installation.
  
   In 4.2 release, we used to make entries in componentContext.xml.
  
   However in 4.3, looks like there is a NetworkGuru Registry.
   How do we register our plugin here?
  
   -Pradeep
  
 
 
 
  --
  regards,

 
  punith s
  cloudbyte.com
 



 --
 regards,

 punith s
 cloudbyte.com




-- 
regards,

punith s
cloudbyte.com

Re: CS 4.3 - Registering network-element plugin

hi pradeep,

you can put your custom key value pairs in your *-context.xml inside your
bean

for example
bean id=elastistorDataStoreProvider

class=org.apache.cloudstack.storage.datastore.provider.ElastistorPrimaryDataStoreProvider
property name=esmanagementip value=10.10.171.180/
property name=esapikey
value=PubSInZaCji8hrRfOsCxgbug2I2k_sRJ0i2a9qmAzZIiCTcFPmZelzx6uNK9TYgqkdohCmq1L2J9eYmUe9YO6A/
property name=esaccountid
value=9e9f67d5-e06f-4d63-a0b8-e7255cba84b8/
property name=espoolid
value=d2d15d11-0f06-3426-a097-3e6e8b36f85c/
property name=esdefaultgateway value=10.10.1.1/
property name=essubnet value=8/
property name=estntinterface value=em0/
  /bean

also i'm curious to know how to move these properties out of the jar ?, can
you please elaborate.

thanks.



On Tue, Jun 24, 2014 at 4:02 PM, Pradeep Cloudstack 
pradeepcloudst...@yahoo.com.invalid wrote:

 Hi Punith,
 yes; the properties file contains custom key value pairs

 We have decided move this file out of our jar. So, no issues now

 -Pradeep



 
  From: Punith S punit...@cloudbyte.com
 To: cloudstack dev@cloudstack.apache.org; Pradeep Cloudstack 
 pradeepcloudst...@yahoo.com
 Sent: Tuesday, June 24, 2014 3:52 PM
 Subject: Re: CS 4.3 - Registering network-element plugin


 hi pradeep,

 does the JuniperNetworkGuru.properties file contain your custom key value
 pairs to be used in the plugin ?

 thanks.


 On Tue, Jun 24, 2014 at 2:56 PM, Pradeep Cloudstack 
 pradeepcloudst...@yahoo.com.invalid wrote:

  Hi Punith,
  the war contains the jar file. Also, the names are correct.
 
  In out network-element pom.xml file, we had made entries to ensure that a
  property file
  is bundled with the jar
 
  ***
build
   resources
 resource
   directorysrc/directory
   filteringfalse/filtering
   includes
   includeJuniperNetworkGuru.properties/include
   /includes
 /resource
   /resources
 /build
  ***
 
  This seems to be causing the issue. If I remove this entry, I see that
 the
  spring.xml and module.properties
  are bundled in the jar, but our JuniperNetworkGuru.properties will not
 get
  bundled
 
  -Pradeep
 
 
 
  
   From: Punith S punit...@cloudbyte.com
  To: cloudstack dev@cloudstack.apache.org; Pradeep Cloudstack 
  pradeepcloudst...@yahoo.com
  Sent: Tuesday, June 24, 2014 12:55 PM
  Subject: Re: CS 4.3 - Registering network-element plugin
 
 
  hi pradeep,
 
  can you make sure your jar is present in the cloud war.
  to make this happen you have to register the dependency in the client
  pom.xml file.
 
  also you need to register your plugin in the plugin pom.xml file and make
  sure the provider name matches.
 
  thanks.
 
 
 
  On Tue, Jun 24, 2014 at 12:38 PM, Pradeep Cloudstack 
  pradeepcloudst...@yahoo.com.invalid wrote:
 
   Thanks Punith.
   We had tried this.
   However the jar file that is built didnot include the
  spring-*-context.xml
   and module.properties
   as a result of which our plugin didnot get registered.
  
   We followed the approach that was taken for vxlan and created artifacts
  on
   similar lines.
  
   Can you pls help on what we are missing ?
  
  
   -Pradeep
  
  
  
   
From: Punith S punit...@cloudbyte.com
   To: cloudstack dev@cloudstack.apache.org; Pradeep Cloudstack 
   pradeepcloudst...@yahoo.com
   Sent: Tuesday, June 24, 2014 12:11 PM
   Subject: Re: CS 4.3 - Registering network-element plugin
  
  
   hi pradeep,
  
   the spring framework has been modularized in 4.3 onwards,
   this link might help you in registering the new plugin.
  
  
 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Plug-ins%2C+Modules%2C+and+Extensions
  
   thanks,
  
  
  
  
  
   On Tue, Jun 24, 2014 at 11:57 AM, Pradeep Cloudstack 
   pradeepcloudst...@yahoo.com.invalid wrote:
  
Hi team,
I need some help in registering network-element plugin in a 4.3
installation.
   
In 4.2 release, we used to make entries in componentContext.xml.
   
However in 4.3, looks like there is a NetworkGuru Registry.
How do we register our plugin here?
   
-Pradeep
   
  
  
  
   --
   regards,



 
  
   punith s
   cloudbyte.com
  
 
 
 
  --
  regards,
 
  punith s
  cloudbyte.com
 



 --
 regards,

 punith s
 cloudbyte.com




-- 
regards,

punith s
cloudbyte.com

Re: Review Request 22631: supporting nfs protocol and resize feature for managed storage in xenserver.

2014-06-23 Thread Punith S

sure mike :)

thanks.


On Tue, Jun 24, 2014 at 2:48 AM, Mike Tutkowski 
mike.tutkow...@solidfire.com wrote:

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

 Hi Punith,

 Just wanted to let you know that I have not forgotten about this review.

 I plan to check the code in once I finish up something else I'm working on 
 over the next day or so.

 Thanks!
 Mike


 - Mike Tutkowski

 On June 17th, 2014, 9:28 a.m. UTC, punith s wrote:
   Review request for cloudstack, amit kumar das, edison su, and Mike
 Tutkowski.
 By punith s.

 *Updated June 17, 2014, 9:28 a.m.*
  *Repository: * cloudstack-git
 Description

 currently managed storage only supports iscsi protocol.

 hence now adding support for nfs protocol and also resizing the vdi to the SR 
 size, hence fully utilizing the SR space in managed storage.

 to support nfs, the getNfsSR method's signature has to changed similar to 
 existing getIscsiSR method.

 SR will be created based on the volume's protocoltype.

 jira id - CLOUDSTACK-6916

   Testing

 system testing done.

   Diffs

- api/src/com/cloud/agent/api/to/DiskTO.java (5901367)
- 
 engine/orchestration/src/org/apache/cloudstack/engine/orchestration/VolumeOrchestrator.java
(eea931e)
- 
 plugins/hypervisors/xenserver/src/com/cloud/hypervisor/xenserver/resource/CitrixResourceBase.java
(9979802)
- server/src/com/cloud/storage/VolumeApiServiceImpl.java (9b034e9)

 View Diff https://reviews.apache.org/r/22631/diff/




-- 
regards,

punith s
cloudbyte.com

Re: [GSOC 2014]Create GUI to add primary storage based on plug-ins

2014-06-18 Thread Punith S

hi seif,

may i know the status of the GSoC primary storage UI project you are
currently working on.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Create+GUI+to+add+primary+storage+based+on+plug-ins
if you can loop me, i will be able to contribute.

thank you.

On Fri, Mar 21, 2014 at 7:47 PM, Mike Tutkowski
mike.tutkow...@solidfire.com wrote:

Thanks for the code, Punith!

Seif is someone I met about a year ago. I plan to mentor his work for
GSoC, but we'd definitely be happy for any input you or others have.

On Fri, Mar 21, 2014 at 4:10 AM, Seif Eddine Jemli
seifeddineje...@gmail.com wrote:

Thanks Punith!

2014-03-21 10:38 GMT+01:00 Punith S punit...@cloudbyte.com:

hi seif,

its cool you took this up, this would make admins to create primary
storage pool with respect to different storage vendors plugin using
cloudstack UI.

you can start off by looking at the createStoragepool api's parameters
in
4.4 and above,

all you have to do is when user ticks the managed storage , list the
storage providers and display the additional input for params of
createStoragePool api , ie. capacityIops, capacityBytes and Details map.

i have already tweaked the system.js script file in 4.2 for myself, i
have
attached it so you can refer it.

thanks.

On Fri, Mar 21, 2014 at 2:23 PM, Seif Eddine Jemli
seifeddineje...@gmail.com wrote:

Hi everyone,

I am Seif Eddine Jemli, a Tunisian student in a french computer science
engineergin college (the ENSEIRB-MATMECA grande ecole).

For GSOC 2014, I'm interested in looking at the JIRA Ticket
CLOUDSTACK-6045
:CreateGUI to add primary storage based on plug-in.
https://issues.apache.org/jira/browse/CLOUDSTACK-6045

My full proposal can be found on Google Melange at:
*

http://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/sjemli/5629499534213120

http://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/sjemli/5629499534213120
*

I am relying on your advices and suggestions!

Thanks,
Seif

--
regards,

punith s
cloudbyte.com

--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
http://solidfire.com/solution/overview/?video=play*™*

--
regards,

punith s
cloudbyte.com

Re: Review Request 22631: supporting nfs protocol and resize feature for managed storage in xenserver.


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

(Updated June 17, 2014, 1:35 p.m.)


Review request for cloudstack, amit kumar das, edison su, and Mike Tutkowski.


Changes
---

since we are using hypervisor reserve for snapshot, now i'm resizing the vdi to 
the size of cloudstack volume size instead of size of the attached SR.


Repository: cloudstack-git


Description
---

currently managed storage only supports iscsi protocol.

hence now adding support for nfs protocol and also resizing the vdi to the SR 
size, hence fully utilizing the SR space in managed storage.

to support nfs, the getNfsSR method's signature has to changed similar to 
existing getIscsiSR method.

SR will be created based on the volume's protocoltype.

jira id - CLOUDSTACK-6916


Diffs (updated)
-

  
plugins/hypervisors/xenserver/src/com/cloud/hypervisor/xenserver/resource/CitrixResourceBase.java
 9979802 

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


Testing
---

system testing done.


Thanks,

punith s

Re: Review Request 22631: supporting nfs protocol and resize feature for managed storage in xenserver.


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

(Updated June 17, 2014, 2:58 p.m.)


Review request for cloudstack, amit kumar das, edison su, and Mike Tutkowski.


Changes
---

had some problem with updating the second patch.


Repository: cloudstack-git


Description
---

currently managed storage only supports iscsi protocol.

hence now adding support for nfs protocol and also resizing the vdi to the SR 
size, hence fully utilizing the SR space in managed storage.

to support nfs, the getNfsSR method's signature has to changed similar to 
existing getIscsiSR method.

SR will be created based on the volume's protocoltype.

jira id - CLOUDSTACK-6916


Diffs (updated)
-

  api/src/com/cloud/agent/api/to/DiskTO.java 5901367 
  
engine/orchestration/src/org/apache/cloudstack/engine/orchestration/VolumeOrchestrator.java
 eea931e 
  
plugins/hypervisors/xenserver/src/com/cloud/hypervisor/xenserver/resource/CitrixResourceBase.java
 9979802 
  server/src/com/cloud/storage/VolumeApiServiceImpl.java 9b034e9 

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


Testing
---

system testing done.


Thanks,

punith s

Re: Review Request 22631: supporting nfs protocol and resize feature for managed storage in xenserver.

On June 16, 2014, 9 p.m., Mike Tutkowski wrote:
I was curious about the resizing of the VDI to take up all of the space of
the SR.

This is actually what I initially did in 4.2; however, it later dawned on
me that - if you want to take hypervisor snapshots - then you need to have
extra space left over in the SR. In other words, the VDI should be less
than the size of the SR.

To support this, I added a new field in 4.3: hypervisor_ss_reserve. This
field is a percentage of the size of the CloudStack volume (the VDI).

For example, if the user wants a 20 GB CloudStack volume (VDI) and the
hypervisor snapshot reserve field is set at 200%, the SR will be 60 GB (20
GB for the VDI + (20 GB * 2)).

Please let me know if you'd like more clarification on this. You can also
examine the SolidFire plug-in to get a feel for how this new field is
utilized.

thanks mike, since i'm still implementing snapshot i forgot to take a look at
this field.

following your logic, now i'm resizing the vdi only to the cloudstack volume
size instead of SR size, hence not using the entire SR size which contains the
hypervisor snapshot reserve.

when a user resizes the volume, let the storage plugin resize the backend
provider volume using the given snapshot reserve.

eg: from your industry standard logic,
if the current offering is at 10G and 25% reserve, this equates to 12.5 G
volume in cloudbyte. but the cloudstack volume remains at 10G in the DB.
when the user resizes the volume to a different offering say 20G and 50%
reserve, this equates to 30G volume in cloudbyte and the cloudstack volume is
resized to 20G in the DB.

hence now i'm mapping the vdi size to cloudstack volume size.

thanks.

- punith

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

On June 17, 2014, 2:58 p.m., punith s wrote:

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

(Updated June 17, 2014, 2:58 p.m.)

Review request for cloudstack, amit kumar das, edison su, and Mike Tutkowski.

Repository: cloudstack-git

Description
---

currently managed storage only supports iscsi protocol.

hence now adding support for nfs protocol and also resizing the vdi to the SR
size, hence fully utilizing the SR space in managed storage.

to support nfs, the getNfsSR method's signature has to changed similar to
existing getIscsiSR method.

SR will be created based on the volume's protocoltype.

jira id - CLOUDSTACK-6916

Diffs
-

api/src/com/cloud/agent/api/to/DiskTO.java 5901367

engine/orchestration/src/org/apache/cloudstack/engine/orchestration/VolumeOrchestrator.java
eea931e

plugins/hypervisors/xenserver/src/com/cloud/hypervisor/xenserver/resource/CitrixResourceBase.java
9979802
server/src/com/cloud/storage/VolumeApiServiceImpl.java 9b034e9

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

Testing
---

system testing done.

Thanks,

punith s

Re: Review Request 22631: supporting nfs protocol and resize feature for managed storage in xenserver.



 On June 16, 2014, 9:28 p.m., Mike Tutkowski wrote:
  plugins/hypervisors/xenserver/src/com/cloud/hypervisor/xenserver/resource/CitrixResourceBase.java,
   line 1963
  https://reviews.apache.org/r/22631/diff/1/?file=610681#file610681line1963
 
  It looks like in VolumeOrchestrator that the protocol type can be 
  null.
  
  That being the case, I recommend you reverse the order of the if 
  statement here to be like this:
  
  if (StoragePoolType.NetworkFilesystem.toString().equals(protocoltype))
  
  This should avoid a NullPointerException if protocoltype is ever 'null'.

thank you.


- punith


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


On June 17, 2014, 2:58 p.m., punith s wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/22631/
 ---
 
 (Updated June 17, 2014, 2:58 p.m.)
 
 
 Review request for cloudstack, amit kumar das, edison su, and Mike Tutkowski.
 
 
 Repository: cloudstack-git
 
 
 Description
 ---
 
 currently managed storage only supports iscsi protocol.
 
 hence now adding support for nfs protocol and also resizing the vdi to the SR 
 size, hence fully utilizing the SR space in managed storage.
 
 to support nfs, the getNfsSR method's signature has to changed similar to 
 existing getIscsiSR method.
 
 SR will be created based on the volume's protocoltype.
 
 jira id - CLOUDSTACK-6916
 
 
 Diffs
 -
 
   api/src/com/cloud/agent/api/to/DiskTO.java 5901367 
   
 engine/orchestration/src/org/apache/cloudstack/engine/orchestration/VolumeOrchestrator.java
  eea931e 
   
 plugins/hypervisors/xenserver/src/com/cloud/hypervisor/xenserver/resource/CitrixResourceBase.java
  9979802 
   server/src/com/cloud/storage/VolumeApiServiceImpl.java 9b034e9 
 
 Diff: https://reviews.apache.org/r/22631/diff/
 
 
 Testing
 ---
 
 system testing done.
 
 
 Thanks,
 
 punith s

Review Request 22631: supporting nfs protocol and resize feature for managed storage in xenserver.

2014-06-16 Thread punith s


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

Review request for cloudstack, amit kumar das, edison su, and Mike Tutkowski.


Repository: cloudstack-git


Description
---

currently managed storage only supports iscsi protocol.

hence now adding support for nfs protocol and also resizing the vdi to the SR 
size, hence fully utilizing the SR space in managed storage.

to support nfs, the getNfsSR method's signature has to changed similar to 
existing getIscsiSR method.

SR will be created based on the volume's protocoltype.

jira id - CLOUDSTACK-6916


Diffs
-

  api/src/com/cloud/agent/api/to/DiskTO.java 5901367 
  
engine/orchestration/src/org/apache/cloudstack/engine/orchestration/VolumeOrchestrator.java
 eea931e 
  
plugins/hypervisors/xenserver/src/com/cloud/hypervisor/xenserver/resource/CitrixResourceBase.java
 9979802 
  server/src/com/cloud/storage/VolumeApiServiceImpl.java 9b034e9 

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


Testing
---

system testing done.


Thanks,

punith s

Re: [ANNOUNCE] Pierre-Luc Dion as a committer

2014-06-15 Thread Punith S

congrats. cheers!


On Sun, Jun 15, 2014 at 5:17 AM, Ahmad Emneina aemne...@gmail.com wrote:

 Awesome stuff. Congrats Pierre-Luc!


 On Sat, Jun 14, 2014 at 2:12 PM, Nux! n...@li.nux.ro wrote:

  Congratulations, Pierre-Luc :)
 
  --
  Sent from the Delta quadrant using Borg technology!
 
  Nux!
  www.nux.ro
 
 
  - Original Message -
  From: sebgoa run...@gmail.com
  To: dev@cloudstack.apache.org
  Sent: Tuesday, 10 June, 2014 12:45:36 PM
  Subject: [ANNOUNCE] Pierre-Luc Dion as a committer
 
  The Project Management Committee (PMC) for Apache CloudStack has
  asked Pierre-Luc Dion to become a committer and we are pleased to
 announce
  that he has accepted.
 
  Being a committer allows many contributors to contribute more
  autonomously. For
  developers, it makes it easier to submit changes and eliminates the need
 to
  have contributions reviewed via the patch submission process. Whether
  contributions are development-related or otherwise, it is a recognition
 of
  a
  contributor's participation in the project and commitment to the project
  and
  the Apache Way.
 
  Please join me in congratulating Pierre-Luc!
 
  PS: Nice work on the documentation
 
  -Sebastien, on behalf of the CloudStack PMC
 




-- 
regards,

punith s
cloudbyte.com

Re: feature : changing volume properties dynamically in 4.5

2014-06-12 Thread Punith S

sure mike.

and i have one question,

which existing volume api are we gonna use for changing disk
offerings(properties) dynamically ?
since resize api will not allow unless the disk is detached !

thanks.


On Thu, Jun 12, 2014 at 11:37 AM, Mike Tutkowski 
mike.tutkow...@solidfire.com wrote:

 Sounds good - let me give some thought as to how we should break up the
 work.

 My GSoC student from Tunisia will be helping us, as well.


 On Wed, Jun 11, 2014 at 8:34 AM, Punith S punit...@cloudbyte.com wrote:

 yes it sounds good, thanks for the proposal mike,

 yeah right now i have implemented prototype of my proposal, since its not
 generic we shall implement your proposal for 4.5.
 on the other hand, for 4.5 i'm supporting nfs protocol and resize feature
 for managed storage in xenserver, now trying to implement snapshot and
 support root disk for vm's.
 and yes if we can club together, i can start working on this proposal for
 data disk and get the prototype ready.
 what do you think ?

 thanks.


 On Wed, Jun 11, 2014 at 3:53 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 I'll send out a [PROPOSAL] e-mail so others who may not be following
 this e-mail thread have a better chance to comment on the feature.


 On Tue, Jun 10, 2014 at 2:58 PM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 Here is that design document I was referring to, Punith:


 https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=42566111

 I've been working with a student in Tunisia who is participating in
 Google Summer of Code (GSoC) (I'm his mentor).

 He'll be working on part of this as will I. (He is also working on
 another related task not listed here.)

 Feel free to join us, if you have time available, as we can divide out
 coding and testing among the three of us.

 Talk to you later!
 Mike


 On Tue, Jun 10, 2014 at 10:18 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 I plan to draw up a design document surrounding generic key/value
 pairs today.

 Perhaps you can take a look at it when you have time, Punith?


 On Tue, Jun 10, 2014 at 10:06 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 Hi Punith,

 Yeah, I hear you about the number of permutations involved.

 Traditionally Compute and Disk Offerings have been immutable. It
 makes it easier from an accounting point of view for chargeback and 
 billing.

 You should definitely feel free to extend the CloudStack API. I think
 NetApp did this for one of their storage features in the recent past. 
 This
 way vendor-specific capabilities can be more easily offered without 
 making
 it look like all vendors support those particular features.

 I do not yet have any code in master related to generic keys/values.
 I'm still designing this.

 How does your schedule look for the 4.5 release? Do you think you
 might have available cycles to help out with this generic key/value
 implementation?

 Talk to you later!
 Mike


 On Tue, Jun 10, 2014 at 7:09 AM, Punith S punit...@cloudbyte.com
 wrote:

 hi mike,

 thanks for the reply, i like your approach which is a very generic
 way and also we only need to do a few changes to the current cloudstack,

 but on the other hand we are tying every property of the vendor to a
 disk offering through key/value pairs, since we offer lot of properties
 like i mentioned, this can create a lot of permutation combinations of 
 disk
 offerings, for say if i need to turn deduplication On for a specific 
 volume
 , should i have to create a new disk offering having current properties
 with deduplication On?

 is this approach already implemented in the current master ?

 and also like you mentioned about exposing a new api, is it okay if
 i expose our own api in my util by extending the PlugableService like in
 network plugins ?

 thanks.


 On Tue, Jun 10, 2014 at 1:17 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 Allow me to follow this up with more detail (with regards to what
 Chris and I talked about):

 As you are aware, today the way you associate a Compute Offering
 (CO) or a Disk Offering (DO) with a Primary Storage (PS) is via storage
 tagging.

 This has some benefits and drawbacks.

 One benefit is being able to have some level of vendor independence
 from the point of view of the CO or DO. For example, if the storage 
 tag of
 a DO is Fast, then this can be satisfied by PS that describes itself 
 as
 Fast, regardless of vendor.

 A major drawback with the storage-tagging approach, however, is
 that you are not easily able to leverage vendor-specific features, 
 which is
 often why you bought storage from the vendor in question to begin with.

 Ideally we do not want to add each vendor's features into the
 system as properties that can be seen by the admin regardless of 
 whether or
 not the underlying storage he's actually using supports the feature in
 question.

 This coarse approach, however, was sort of business as usual when I
 started in with CloudStack 1.5 years ago

Re: feature : changing volume properties dynamically in 4.5

2014-06-11 Thread Punith S

yes it sounds good, thanks for the proposal mike,

yeah right now i have implemented prototype of my proposal, since its not
generic we shall implement your proposal for 4.5.
on the other hand, for 4.5 i'm supporting nfs protocol and resize feature
for managed storage in xenserver, now trying to implement snapshot and
support root disk for vm's.
and yes if we can club together, i can start working on this proposal for
data disk and get the prototype ready.
what do you think ?

thanks.


On Wed, Jun 11, 2014 at 3:53 AM, Mike Tutkowski 
mike.tutkow...@solidfire.com wrote:

 I'll send out a [PROPOSAL] e-mail so others who may not be following this
 e-mail thread have a better chance to comment on the feature.


 On Tue, Jun 10, 2014 at 2:58 PM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 Here is that design document I was referring to, Punith:

 https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=42566111

 I've been working with a student in Tunisia who is participating in
 Google Summer of Code (GSoC) (I'm his mentor).

 He'll be working on part of this as will I. (He is also working on
 another related task not listed here.)

 Feel free to join us, if you have time available, as we can divide out
 coding and testing among the three of us.

 Talk to you later!
 Mike


 On Tue, Jun 10, 2014 at 10:18 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 I plan to draw up a design document surrounding generic key/value pairs
 today.

 Perhaps you can take a look at it when you have time, Punith?


 On Tue, Jun 10, 2014 at 10:06 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 Hi Punith,

 Yeah, I hear you about the number of permutations involved.

 Traditionally Compute and Disk Offerings have been immutable. It makes
 it easier from an accounting point of view for chargeback and billing.

 You should definitely feel free to extend the CloudStack API. I think
 NetApp did this for one of their storage features in the recent past. This
 way vendor-specific capabilities can be more easily offered without making
 it look like all vendors support those particular features.

 I do not yet have any code in master related to generic keys/values.
 I'm still designing this.

 How does your schedule look for the 4.5 release? Do you think you might
 have available cycles to help out with this generic key/value
 implementation?

 Talk to you later!
 Mike


 On Tue, Jun 10, 2014 at 7:09 AM, Punith S punit...@cloudbyte.com
 wrote:

 hi mike,

 thanks for the reply, i like your approach which is a very generic way
 and also we only need to do a few changes to the current cloudstack,

 but on the other hand we are tying every property of the vendor to a
 disk offering through key/value pairs, since we offer lot of properties
 like i mentioned, this can create a lot of permutation combinations of 
 disk
 offerings, for say if i need to turn deduplication On for a specific 
 volume
 , should i have to create a new disk offering having current properties
 with deduplication On?

 is this approach already implemented in the current master ?

 and also like you mentioned about exposing a new api, is it okay if i
 expose our own api in my util by extending the PlugableService like in
 network plugins ?

 thanks.


 On Tue, Jun 10, 2014 at 1:17 AM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 Allow me to follow this up with more detail (with regards to what
 Chris and I talked about):

 As you are aware, today the way you associate a Compute Offering (CO)
 or a Disk Offering (DO) with a Primary Storage (PS) is via storage 
 tagging.

 This has some benefits and drawbacks.

 One benefit is being able to have some level of vendor independence
 from the point of view of the CO or DO. For example, if the storage tag 
 of
 a DO is Fast, then this can be satisfied by PS that describes itself as
 Fast, regardless of vendor.

 A major drawback with the storage-tagging approach, however, is that
 you are not easily able to leverage vendor-specific features, which is
 often why you bought storage from the vendor in question to begin with.

 Ideally we do not want to add each vendor's features into the system
 as properties that can be seen by the admin regardless of whether or not
 the underlying storage he's actually using supports the feature in 
 question.

 This coarse approach, however, was sort of business as usual when I
 started in with CloudStack 1.5 years ago.

 That being the case, when I added QoS options to CS, I did so in a
 way where the admin would see Min IOPS and Max IOPS options regardless of
 whether or not his storage actually supported those controls (to mitigate
 this a bit in the GUI, the admin has to explicitly select Storage QoS
 from a combobox).

 We leverage the same use model with Hypervisor QoS: The admin sees
 these options regardless of whether or not they actually apply on the
 hypervisor where the VM gets deployed.

 Going forward, we want to implement a more

Re: feature : changing volume properties dynamically in 4.5

2014-06-10 Thread Punith S

hi mike,

thanks for the reply, i like your approach which is a very generic way and
also we only need to do a few changes to the current cloudstack,

but on the other hand we are tying every property of the vendor to a disk
offering through key/value pairs, since we offer lot of properties like i
mentioned, this can create a lot of permutation combinations of disk
offerings, for say if i need to turn deduplication On for a specific volume
, should i have to create a new disk offering having current properties
with deduplication On?

is this approach already implemented in the current master ?

and also like you mentioned about exposing a new api, is it okay if i
expose our own api in my util by extending the PlugableService like in
network plugins ?

thanks.


On Tue, Jun 10, 2014 at 1:17 AM, Mike Tutkowski 
mike.tutkow...@solidfire.com wrote:

 Allow me to follow this up with more detail (with regards to what Chris
 and I talked about):

 As you are aware, today the way you associate a Compute Offering (CO) or a
 Disk Offering (DO) with a Primary Storage (PS) is via storage tagging.

 This has some benefits and drawbacks.

 One benefit is being able to have some level of vendor independence from
 the point of view of the CO or DO. For example, if the storage tag of a DO
 is Fast, then this can be satisfied by PS that describes itself as
 Fast, regardless of vendor.

 A major drawback with the storage-tagging approach, however, is that you
 are not easily able to leverage vendor-specific features, which is often
 why you bought storage from the vendor in question to begin with.

 Ideally we do not want to add each vendor's features into the system as
 properties that can be seen by the admin regardless of whether or not the
 underlying storage he's actually using supports the feature in question.

 This coarse approach, however, was sort of business as usual when I
 started in with CloudStack 1.5 years ago.

 That being the case, when I added QoS options to CS, I did so in a way
 where the admin would see Min IOPS and Max IOPS options regardless of
 whether or not his storage actually supported those controls (to mitigate
 this a bit in the GUI, the admin has to explicitly select Storage QoS
 from a combobox).

 We leverage the same use model with Hypervisor QoS: The admin sees these
 options regardless of whether or not they actually apply on the hypervisor
 where the VM gets deployed.

 Going forward, we want to implement a more fine-grain and generic approach.

 We would like to have a storage provider field for the CO and DO windows
 (this equates to the name of one and only one storage provider). If the
 admin inputs a specific storage provider and does not use the storage tags
 field, he can enter in an arbitrary number of key/value pairs in another
 text field (perhaps we would provide a nice entry dialog to make this
 easier in the GUI). These key value pairs can be passed into the storage
 driver when it's asked to create (or update) a volume and the storage
 driver can decide what each and every key/value pair means.

 What do you think about this approach?

 Thanks


 On Mon, Jun 9, 2014 at 1:14 PM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

 Hi Punith,

 This kind of a feature is something Chris Suich and I discussed a while
 back.

 We talked about leveraging arbitrary key/value pairs to make this happen
 (OpenStack does something similar). The key/value pairs would be vendor
 specific.

 If we take a key/value approach, we might be able to make this all work
 the way things work today when the user wants to change an existing Compute
 Offering and/or Disk Offering.

 For example, the user would pick a new Compute Offering (with presumably
 has different key/value pairs) and CloudStack could inform the applicable
 storage provider, who could update the volume in question.

 This way we don't need to introduce a new API command and the use model
 for the user doesn't really change.

 What are you thoughts on this?

 Thanks,
 Mike


 On Mon, Jun 9, 2014 at 8:08 AM, Punith S punit...@cloudbyte.com wrote:

 hi guys,

 since most of the third party storage providers have been implementing
 1:1 mapping(managed storage) between a volume(dataset) and a vm
 disk(vdi/vmdk) for guaranteeing the Qos, i would like to propose a new
 feature to dynamically change the volume properties supported by storage
 vendors such as IOPS, Deduplication, Compression, Grace, Syncronization,
 Latency etc, depending on properties and features supported by respective
 storage vendors. hence providing more flexibility for users.

 in case of using default cloudstack storage provider, we can change the
 properties of the vdi/vmdk files apart from resizing the volume(vdi/vmdk).

 changes in management server include,

 new async web api ChangeVolumePropertiesCmd,
 new method in VolumeApiService for vo and dao validation implementations.
 new method in VolumeServiceManager for supporting callback and calling

feature : changing volume properties dynamically in 4.5

2014-06-09 Thread Punith S

hi guys,

since most of the third party storage providers have been implementing 1:1
mapping(managed storage) between a volume(dataset) and a vm disk(vdi/vmdk)
for guaranteeing the Qos, i would like to propose a new feature to
dynamically change the volume properties supported by storage vendors such
as IOPS, Deduplication, Compression, Grace, Syncronization, Latency
etc, depending on properties and features supported by respective storage
vendors. hence providing more flexibility for users.

in case of using default cloudstack storage provider, we can change the
properties of the vdi/vmdk files apart from resizing the volume(vdi/vmdk).

changes in management server include,

new async web api ChangeVolumePropertiesCmd,
new method in VolumeApiService for vo and dao validation implementations.
new method in VolumeServiceManager for supporting callback and calling the
respective storage provider driver's implementation.
new method in PrimaryDataStoreDriver interface for implementing respective
features according to their storage product.

changes in UI include,
new changing volume properties widget in volume section, showing different
properties depending upon listed storage providers.

any suggestions and feedbacks ?

thanks

-- 
regards,

punith s
cloudbyte.com

Re: [DISCUSS] Increasing VM IOPS by separating golden image in high IOPS partition in Xen Server ?

2014-06-05 Thread Punith S

 store as much golden image as I need.
 
  I have also tested it with 256 GB SSD mounted on Xen Server
 6.2.0
   with
 2TB
  local storage 1RPM, 6TB NFS share storage with 1GB network.
 The
IOPS
 of
  VMs which have golden image (master image) in SSD and child
 image
  in
NFS
  increate more than 30-40% compare with VMs which have both
 golden
   image
 and
  child image in NFS. The boot time of each VM is also decrease.
   ('cause
  golden image in SSD only reduced READ IOPS).
 
  Do you think this approach OK ?
 
 
  On Mon, Jun 2, 2014 at 12:50 PM, Mike Tutkowski 
  mike.tutkow...@solidfire.com wrote:
 
   Thanks, Punith - this is similar to what I was going to say.
  
   Any time a set of CloudStack volumes share IOPS from a common
  pool,
you
   cannot guarantee IOPS to a given CloudStack volume at a given
  time.
  
   Your choices at present are:
  
   1) Use managed storage (where you can create a 1:1 mapping
  between
   a
   CloudStack volume and a volume on a storage system that has
 QoS).
   As
  Punith
   mentioned, this requires that you purchase storage from a
 vendor
   who
   provides guaranteed QoS on a volume-by-volume bases AND has
 this
  integrated
   into CloudStack.
  
   2) Create primary storage in CloudStack that is not managed,
 but
   has
a
  high
   number of IOPS (ex. using SSDs). You can then storage tag this
primary
   storage and create Compute and Disk Offerings that use this
  storage
tag
  to
   make sure their volumes end up on this storage pool (primary
storage).
  This
   will still not guarantee IOPS on a CloudStack volume-by-volume
   basis,
 but
   it will at least place the CloudStack volumes that need a
 better
chance
  of
   getting higher IOPS on a storage pool that could provide the
necessary
   IOPS. A big downside here is that you want to watch how many
CloudStack
   volumes get deployed on this primary storage because you'll
 need
  to
   essentially over-provision IOPS in this primary storage to
  increase
the
   probability that each and every CloudStack volume that uses
 this
 primary
   storage gets the necessary IOPS (and isn't as likely to suffer
  from
the
   Noisy Neighbor Effect). You should be able to tell CloudStack
 to
   only
  use,
   say, 80% (or whatever) of the storage you're providing to it
 (so
  as
to
   increase your effective IOPS per GB ratio). This
  over-provisioning
   of
  IOPS
   to control Noisy Neighbors is avoided in option 1. In that
   situation,
 you
   only provision the IOPS and capacity you actually need. It is
 a
   much
 more
   sophisticated approach.
  
   Thanks,
   Mike
  
  
   On Sun, Jun 1, 2014 at 11:36 PM, Punith S 
  punit...@cloudbyte.com
  wrote:
  
hi hieu,
   
your problem is the bottle neck we see as a storage vendors
 in
   the
  cloud,
meaning all the vms in the cloud have not been guaranteed
 iops
   from
 the
primary storage, because in your case i'm assuming you are
   running
   1000vms
on a xen cluster whose all vm's disks are lying on a same
  primary
nfs
storage mounted to the cluster,
hence you won't get the dedicated iops for each vm since
 every
  vm
is
sharing the same storage. to solve this issue in cloudstack
 we
   the
  third
party vendors have implemented the plugin(namely cloudbyte ,
 solidfire
   etc)
to support managed storage(dedicated volumes with guaranteed
  qos
for
  each
vms) , where we are mapping each root disk(vdi) or data disk
  of a
vm
  with
one nfs or iscsi share coming out of a pool, also we are
   proposing
 the
   new
feature to change volume iops on fly in 4.5, where you can
   increase
 or
decrease your root disk iops while booting or at peak times.
  but
   to
 use
this plugin you have to buy our storage solution.
   
if not , you can try creating a nfs share out of ssd pool
  storage
and
create a primary storage in cloudstack out of it named as
  golden
  primary
storage with specific tag like gold, and create a compute
   offering
 for
   your
template with the storage tag as gold, hence all the vm's
 you
create
  will
sit on this gold primary storage with high iops. and other
 data
disks
  on
other primary storage but still here you cannot guarantee
 the
  qos
at
 vm
level.
   
thanks
   
   
On Mon, Jun 2, 2014 at 10:12 AM, Hieu LE 
 hieul...@gmail.com
wrote:
   
Hi all,
   
There are some problems

Re: [DISCUSS] Increasing VM IOPS by separating golden image in high IOPS partition in Xen Server ?

2014-06-01 Thread Punith S

hi hieu,

your problem is the bottle neck we see as a storage vendors in the cloud,
meaning all the vms in the cloud have not been guaranteed iops from the
primary storage, because in your case i'm assuming you are running 1000vms
on a xen cluster whose all vm's disks are lying on a same primary nfs
storage mounted to the cluster,
hence you won't get the dedicated iops for each vm since every vm is
sharing the same storage. to solve this issue in cloudstack we the third
party vendors have implemented the plugin(namely cloudbyte , solidfire etc)
to support managed storage(dedicated volumes with guaranteed qos for each
vms) , where we are mapping each root disk(vdi) or data disk of a vm with
one nfs or iscsi share coming out of a pool, also we are proposing the new
feature to change volume iops on fly in 4.5, where you can increase or
decrease your root disk iops while booting or at peak times. but to use
this plugin you have to buy our storage solution.

if not , you can try creating a nfs share out of ssd pool storage and
create a primary storage in cloudstack out of it named as golden primary
storage with specific tag like gold, and create a compute offering for your
template with the storage tag as gold, hence all the vm's you create will
sit on this gold primary storage with high iops. and other data disks on
other primary storage but still here you cannot guarantee the qos at vm
level.

thanks


On Mon, Jun 2, 2014 at 10:12 AM, Hieu LE hieul...@gmail.com wrote:

 Hi all,

 There are some problems while deploying a large amount of VMs in my company
 with CloudStack. All VMs are deployed from same template (e.g: Windows 7)
 and the quantity is approximately ~1000VMs. The problems here is low IOPS,
 low performance of VM (about ~10-11 IOPS, boot time is very high). The
 storage of my company is SAN/NAS with NFS and Xen Server 6.2.0. All Xen
 Server nodes have standard server HDD disk raid.

 I have found some solutions for this such as:

- Enable Xen Server Intellicache and some tweaks in CloudStack codes to
deploy and start VM in Intellicache mode. But this solution will
 transfer
all IOPS from shared storage to all local storage, hence affect and
 limit
some CloudStack features.
- Buying some expensive storage solutions and network to increase IOPS.
Nah..

 So, I am thinking about a new feature that (may be) increasing IOPS and
 performance of VMs:

1. Separate golden image in high IOPS partition: buying new SSD, plug in
Xen Server and deployed a new VM in NFS storage WITH golden image in
 this
new SSD partition. This can reduce READ IOPS in shared storage and
 decrease
boot time of VM. (Currenty, VM deployed in Xen Server always have a
 master
image (golden image - in VMWare) always in the same storage repository
 with
different image (child image)). We can do this trick by tweaking in VHD
header file with new Xen Server plug-in.
2. Create golden primary storage and VM template that enable this
feature.
3. So, all VMs deployed from template that had enabled this feature will
have a golden image stored in golden primary storage (SSD or some high
 IOPS
partition), and different image (child image) stored in other normal
primary storage.

 This new feature will not transfer all IOPS from shared storage to local
 storage (because high IOPS partition can be another high IOPS shared
 storage) and require less money than buying new storage solution.

 What do you think ? If possible, may I write a proposal in CloudStack wiki
 ?

 BRs.

 Hieu Lee

 --
 -BEGIN GEEK CODE BLOCK-
 Version: 3.1
 GCS/CM/IT/M/MU d-@? s+(++):+(++) !a C()$ ULC(++)$ P L++(+++)$
 E
 !W N* o+ K w O- M V- PS+ PE++ Y+ PGP+ t 5 X R tv+ b+(++)+++ DI- D+ G
 e++(+++) h-- r(++)+++ y-
 --END GEEK CODE BLOCK--




-- 
regards,

punith s
cloudbyte.com

Re: SSVM's are NOT RUNNING !

2014-04-29 Thread Punith S

 problem, hence updated my vhd util. where his SMlog has
the exception unlike in mine.*

*i can't find weather something is wrong in my xen or my secondary storage
!!*
*help!!*

*thanks.*


On Mon, Apr 28, 2014 at 10:50 AM, Punith S punit...@cloudbyte.com wrote:

 hi sanjay,

 it seems vhd-util is present in the xenserver

 [root@XenMaddy bin]# which vhd-util
 /opt/xensource/bin/vhd-util

 -rwxr-xr-x 1 root root  312K Jan 10 00:03 vhd-util

 i also copied the .vhd file from secondary storage manually
 to /opt/xensource/bin/ , its still not working out,
 pinging my storage server from hypervisor is working fine.

 is this vhd-util obsolete ?

 --
 regards,

 punith s
 cloudbyte.com




-- 
regards,

punith s
cloudbyte.com

Re: SSVM's are NOT RUNNING !

2014-04-29 Thread Punith S

hi guys,

finally this issue got cleared :)

it was the problem with my xen server which had a *Stale NFS file handle.*

*found that **copy_vhd_from_secondarystorage.sh was an old file which was
used for 4.2, hence the size was going null so had to replace it.*

had to modify the *copy_vhd_from_secondarystorage.sh *to throw the
exception in *SMlog.*

Apr 29 16:31:06 XenMaddy SM: [5729] ['bash',
'/opt/cloud/bin/copy_vhd_from_secondarystorage.sh',
'10.10.171.121:/kimisecondary/template/tmpl/1/1/',
'82f01cc2-3b35-d523-7c15-027ea933fada',
'cloud-44fc42e8-15e7-4634-8bfd-bd3a4ad7c366']
Apr 29 16:31:06 XenMaddy SM: [5756] ['uuidgen', '-r']
Apr 29 16:31:06 XenMaddy SM: [5756]   pread SUCCESS
*Apr 29 16:31:07 XenMaddy SM: [5756] lock: acquired
/var/lock/sm/82f01cc2-3b35-d523-7c15-027ea933fada/sr*
*Apr 29 16:31:07 XenMaddy SM: [5756] Raising exception [47, The SR is not
available]*
*Apr 29 16:31:07 XenMaddy SM: [5756] lock: released
/var/lock/sm/82f01cc2-3b35-d523-7c15-027ea933fada/sr*
*Apr 29 16:31:07 XenMaddy SM: [5756] * generic exception: vdi_create:
EXCEPTION SR.SROSError, The SR is not available*
Apr 29 16:31:07 XenMaddy SM: [5756]   File
/opt/xensource/sm/SRCommand.py, line 106, in run
Apr 29 16:31:07 XenMaddy SM: [5756] return self._run_locked(sr)
Apr 29 16:31:07 XenMaddy SM: [5756]   File
/opt/xensource/sm/SRCommand.py, line 147, in _run_locked
Apr 29 16:31:07 XenMaddy SM: [5756] target = sr.vdi(self.vdi_uuid)
Apr 29 16:31:07 XenMaddy SM: [5756]   File /opt/xensource/sm/NFSSR, line
223, in vdi
Apr 29 16:31:07 XenMaddy SM: [5756] return NFSFileVDI(self, uuid)
Apr 29 16:31:07 XenMaddy SM: [5756]   File /opt/xensource/sm/VDI.py, line
102, in __init__
Apr 29 16:31:07 XenMaddy SM: [5756] self.load(uuid)
Apr 29 16:31:07 XenMaddy SM: [5756]   File /opt/xensource/sm/FileSR.py,
line 401, in load
Apr 29 16:31:07 XenMaddy SM: [5756] raise
xs_errors.XenError('SRUnavailable')
Apr 29 16:31:07 XenMaddy SM: [5756]   File
/opt/xensource/sm/xs_errors.py, line 49, in __init__
Apr 29 16:31:07 XenMaddy SM: [5756] raise SR.SROSError(errorcode,
errormessage)
Apr 29 16:31:07 XenMaddy SM: [5756]
Apr 29 16:31:07 XenMaddy SM: [5756] lock: closed
/var/lock/sm/82f01cc2-3b35-d523-7c15-027ea933fada/sr

*[root@XenMaddy sr-mount]# df -h*
FilesystemSize  Used Avail Use% Mounted on
/dev/sda1 4.0G  3.4G  361M  91% /
none  373M   20K  373M   1% /dev/shm
/opt/xensource/packages/iso/XenCenter.iso
   52M   52M 0 100% /var/xen/xc-install
//10.11.1.251/qa  366G  340G   27G  93%
/var/run/sr-mount/f17836d0-2a7b-ae2b-7f4c-c9ecb851eebe
*df: `/var/run/sr-mount/82f01cc2-3b35-d523-7c15-027ea933fada': Stale NFS
file handle --- culprit.*
/dev/mapper/XSLocalEXT--0e2f9ac5--2075--8e1e--bd46--709c230d94ea-0e2f9ac5--2075--8e1e--bd46--709c230d94ea
  268G  2.4G  252G   1%
/var/run/sr-mount/0e2f9ac5-2075-8e1e-bd46-709c230d94ea
*10.10.171.121:/kimivolnfs*
*   47G  2.5G   45G   6%
/var/run/sr-mount/7bd9654c-18f3-f8af-de23-ebfc68709e89  -- my mounted
nfs primary storage.*

*bottom line was , all i needed to restart my xenserver(host).*
cheers!
thanks.


On Tue, Apr 29, 2014 at 1:37 PM, Punith S punit...@cloudbyte.com wrote:

 hi guys,

 i'm still going through the same problem,
 WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-43:ctx-12763945)
 destoryVDIbyNameLabel failed due to there are 0 VDIs with name
 cloud-fc59061b-d652-4210-920e-0e2fd587ba49
 *WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-43:ctx-12763945)
 can not create vdi in sr 58dd7e27-32c7-caab-e2b3-cdca45eefa7d*
 *WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-43:ctx-12763945)
 Catch Exception com.cloud.utils.exception.CloudRuntimeException for
 template +  due to com.cloud.utils.exception.CloudRuntimeException: can not
 create vdi in sr 58dd7e27-32c7-caab-e2b3-cdca45eefa7d*
 *com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
 58dd7e27-32c7-caab-e2b3-cdca45eefa7d*
 * at
 com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copy_vhd_from_secondarystorage(XenServerStorageProcessor.java:848*
 )
  at
 com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:918)
 at
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:75)
  at
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:50)
 at
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:609)
  at
 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:59)
 at
 com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:106)
  at
 com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216

Re: SSVM's are NOT RUNNING !

2014-04-27 Thread Punith S

hi sanjay,

it seems vhd-util is present in the xenserver

[root@XenMaddy bin]# which vhd-util
/opt/xensource/bin/vhd-util

-rwxr-xr-x 1 root root  312K Jan 10 00:03 vhd-util

i also copied the .vhd file from secondary storage manually
to /opt/xensource/bin/ , its still not working out,
pinging my storage server from hypervisor is working fine.

is this vhd-util obsolete ?

-- 
regards,

punith s
cloudbyte.com

Re: [ACS4.4, XenServer] Problem starting system VMs

2014-04-27 Thread Punith S

hi mike,

it seems you may be running out of management ip addresses but i'm not sure
of this error !

try these global settings ,

router.extra.public.nics = 5

router.version.check = false.

thanks.


On Mon, Apr 28, 2014 at 10:23 AM, Mike Tutkowski 
mike.tutkow...@solidfire.com wrote:

 I didn't mention this, but I'm using a Basic Zone.

 The problem is in the VirtualRouterElement, but I'm having a little trouble
 with my debugger at the moment, so haven't traced it any deeper than
 VirtualRouterElement.deployVirtualRouterInGuestNetwork.


 On Sun, Apr 27, 2014 at 10:10 PM, Mike Tutkowski 
 mike.tutkow...@solidfire.com wrote:

  It is actually a networking problem (although the exception is vague):
 
  Unable to create a deployment for VM[DomainRouter|r-10-VM]
 
  Inside of NetworkOrchestrator.prepareNic, prepareElement fails for the
  Virtual Router.
 
  Is there some network setting I might be missing for this patched version
  of 6.2?
 
  Thanks!
 
  ListProvider providersToImplement =
  getNetworkProviders(network.getId());
 
  for (NetworkElement element : networkElements) {
 
  if (providersToImplement.contains(element.getProvider())) {
 
  if (!_networkModel.isProviderEnabledInPhysicalNetwork(
  _networkModel.getPhysicalNetworkId(network),
  element.getProvider().getName())) {
 
  throw new CloudRuntimeException(Service provider  +
  element.getProvider().getName() +  either doesn't exist or is not
  enabled in physical network id: 
 
  + network.getPhysicalNetworkId());
 
  }
 
  if (s_logger.isDebugEnabled()) {
 
  s_logger.debug(Asking  + element.getName() +  to
  prepare for  + nic);
 
  }
 
  if (!prepareElement(element, network, profile, vmProfile,
  dest, context)) {
 
  throw new
 InsufficientAddressCapacityException(unable
  to configure the dhcp service, due to insufficiant address capacity,
  Network.class, network.getId());
 
  }
 
  }
 
  }
 
 
  On Sun, Apr 27, 2014 at 9:44 PM, Mike Tutkowski 
  mike.tutkow...@solidfire.com wrote:
 
  Hi,
 
  I recently installed 6.2 with XS62ESP1 and XS62ESP1004 (so that
  Xenserver625StorageProcessor would be utilized).
 
  When I create a cloud from scratch, my SSVM starts up fine, but CPVM
 ends
  up in the Paused state. I have to force a shutdown of that VM and then
  CloudStack restarts it and it works. This consistently happens. The
 system
  VMs are being deployed to the local storage of the one XS host I have
 in my
  one and only cluster.
 
  Any thoughts on that?
 
  Also, if I try to kick off a user VM to local storage, I get the
  general-purpose InsufficientCapacityException and the virtual router
 does
  not even start up.
 
  Can anyone create a similar cloud to what I've described here with XS
  6.2, XS62ESP1, and XS62ESP1004? I re-ran this test using a XS 6.1 host
 and
  it works just fine.
 
  At the moment, this is blocking a test case I'm trying to execute to
  verify code I had to write in Xenserver625StorageProcessor.
 
  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
 http://solidfire.com/solution/overview/?video=play
  *(tm)*
 
 
 
 
  --
  *Mike Tutkowski*
  *Senior CloudStack Developer, SolidFire Inc.*
  e: mike.tutkow...@solidfire.com
  o: 303.746.7302
  Advancing the way the world uses the cloud
 http://solidfire.com/solution/overview/?video=play
  *(tm)*
 



 --
 *Mike Tutkowski*
 *Senior CloudStack Developer, SolidFire Inc.*
 e: mike.tutkow...@solidfire.com
 o: 303.746.7302
 Advancing the way the world uses the
 cloudhttp://solidfire.com/solution/overview/?video=play
 *(tm)*




-- 
regards,

punith s
cloudbyte.com

SSVM's are NOT RUNNING !

hi guys,

i have fresh installed the cloudstack 4.3 ,
on adding a basic zone with xenserver 6.2
after seeding the secondary nfs storage mentioned in docs by

*/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
-m /mnt/secondary -u
http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2
http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2
-h xenserver  -F*

also tried seeding the secondary nfs storage by new link of ssvm templates

*/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
-m /mnt/secondary -u
http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-xen.vhd.bz2
http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-xen.vhd.bz2
-h xenserver -F*

*i'm getting the following errors.*

WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-1:ctx-99b42320)
destoryVDIbyNameLabel failed due to there are 0 VDIs with name
cloud-eedde44e-93ca-4fa1-bc9f-1fa06ddc1279
WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-1:ctx-99b42320)
can not create vdi in sr 2d85eb6a-d5a2-94ae-ed41-4051eafe882a
*WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-1:ctx-99b42320)
Catch Exception com.cloud.utils.exception.CloudRuntimeException for
template +  due to com.cloud.utils.exception.CloudRuntimeException: can not
create vdi in sr 2d85eb6a-d5a2-94ae-ed41-4051eafe882a*
*com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
2d85eb6a-d5a2-94ae-ed41-4051eafe882a*
*at *
com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copy_vhd_from_secondarystorage(XenServerStorageProcessor.java:848)
at
com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:918)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:75)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:50)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:609)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:59)
at


INFO  [o.a.c.s.v.VolumeServiceImpl] (secstorage-1:ctx-9eeb38cf) releasing
lock for VMTemplateStoragePool 1
WARN  [c.c.u.d.Merovingian2] (secstorage-1:ctx-9eeb38cf) Was unable to find
lock for the key template_spool_ref1 and thread id 1185113504
INFO  [c.c.v.VirtualMachineManagerImpl] (secstorage-1:ctx-9eeb38cf) Unable
to contact resource.
*com.cloud.exception.StorageUnavailableException: Resource [StoragePool:2]
is unreachable: Unable to create Vol[1|vm=1|ROOT]:Catch Exception
com.cloud.utils.exception.CloudRuntimeException for template +  due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
2d85eb6a-d5a2-94ae-ed41-4051eafe882a*
*at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1202)*
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1254)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:962)

...

INFO  [c.c.h.x.r.CitrixResourceBase] (DirectAgent-9:ctx-f8ea88cc) VM does
not exist on XenServer68659813-bd58-47cf-a759-986e54613a81
WARN  [c.c.s.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-9eeb38cf)
Exception while trying to start secondary storage vm
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[SecondaryStorageVm|s-1-VM]Scope=interface
com.cloud.dc.DataCenter; id=1
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:921)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:745)


my primary storage is seen mounted successfully on the hypervisor(host)

is the ssvm template got corrupted ?

thanks.

-- 
regards,

punith s
cloudbyte.com

Re: SSVM's are NOT RUNNING !

hi rajesh,

ran these commands on my xen host

[root@XenMaddy /]# vhd-util check -n
3fdfe519-a8e0-4a0b-9fc7-cd59465e53ab.vhd
cannot stat 3fdfe519-a8e0-4a0b-9fc7-cd59465e53ab.vhd: 2

[root@XenMaddy /]# vhd-util scan 3fdfe519-a8e0-4a0b-9fc7-cd59465e53ab.vhd
vhd=3fdfe519-a8e0-4a0b-9fc7-cd59465e53ab.vhd scan-error=-2
error-message='failure scanning target'
scan failed: -2

its showing failure.

referring -
https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM%2C+templates%2C+Secondary+storage+troubleshooting

thanks.


On Fri, Apr 25, 2014 at 5:09 PM, Rajesh Battala
rajesh.batt...@citrix.comwrote:

 Do you have vhd-util binary present in your xenserver?

 -Original Message-
 From: Punith S [mailto:punit...@cloudbyte.com]
 Sent: Friday, April 25, 2014 5:07 PM
 To: cloudstack
 Subject: SSVM's are NOT RUNNING !

 hi guys,

 i have fresh installed the cloudstack 4.3 , on adding a basic zone with
 xenserver 6.2 after seeding the secondary nfs storage mentioned in docs by


 */usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
 -m /mnt/secondary -u

 http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2
 
 http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2
 
 -h xenserver  -F*

 also tried seeding the secondary nfs storage by new link of ssvm templates


 */usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
 -m /mnt/secondary -u

 http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-xen.vhd.bz2
 
 http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-xen.vhd.bz2
 
 -h xenserver -F*

 *i'm getting the following errors.*

 WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-1:ctx-99b42320)
 destoryVDIbyNameLabel failed due to there are 0 VDIs with name
 cloud-eedde44e-93ca-4fa1-bc9f-1fa06ddc1279
 WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-1:ctx-99b42320)
 can not create vdi in sr 2d85eb6a-d5a2-94ae-ed41-4051eafe882a
 *WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-1:ctx-99b42320)
 Catch Exception com.cloud.utils.exception.CloudRuntimeException for
 template +  due to com.cloud.utils.exception.CloudRuntimeException: can not
 create vdi in sr 2d85eb6a-d5a2-94ae-ed41-4051eafe882a*
 *com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
 2d85eb6a-d5a2-94ae-ed41-4051eafe882a*
 *at *

 com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copy_vhd_from_secondarystorage(XenServerStorageProcessor.java:848)
 at

 com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:918)
 at

 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:75)
 at

 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:50)
 at

 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:609)
 at

 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:59)
 at

 
 INFO  [o.a.c.s.v.VolumeServiceImpl] (secstorage-1:ctx-9eeb38cf) releasing
 lock for VMTemplateStoragePool 1 WARN  [c.c.u.d.Merovingian2]
 (secstorage-1:ctx-9eeb38cf) Was unable to find lock for the key
 template_spool_ref1 and thread id 1185113504 INFO
  [c.c.v.VirtualMachineManagerImpl] (secstorage-1:ctx-9eeb38cf) Unable to
 contact resource.
 *com.cloud.exception.StorageUnavailableException: Resource [StoragePool:2]
 is unreachable: Unable to create Vol[1|vm=1|ROOT]:Catch Exception
 com.cloud.utils.exception.CloudRuntimeException for template +  due to
 com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
 2d85eb6a-d5a2-94ae-ed41-4051eafe882a*
 *at

 org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1202)*
 at

 org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1254)
 at

 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:962)

 ...

 INFO  [c.c.h.x.r.CitrixResourceBase] (DirectAgent-9:ctx-f8ea88cc) VM does
 not exist on XenServer68659813-bd58-47cf-a759-986e54613a81
 WARN  [c.c.s.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-9eeb38cf)
 Exception while trying to start secondary storage vm
 com.cloud.exception.InsufficientServerCapacityException: Unable to create
 a deployment for VM[SecondaryStorageVm|s-1-VM]Scope=interface
 com.cloud.dc.DataCenter; id=1
 at

 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:921

Re: SSVM's are NOT RUNNING !

hi,

i manually copied the seeded vhd file from secondary storage to my xen host
and ran the following commands.

[root@XenMaddy /]# vhd-util check -n
3fdfe519-a8e0-4a0b-9fc7-cd59465e53ab.vhd
primary footer invalid: invalid cookie
*3fdfe519-a8e0-4a0b-9fc7-cd59465e53ab.vhd appears invalid; dumping metadata*
VHD Footer Summary:
---
Cookie  : conectix
Features: (0x0002) RESV
File format version : Major: 1, Minor: 0
Data offset : 512
Timestamp   : Fri Jan  1 00:00:00 2010
Creator Application : 'tap'
Creator version : Major: 1, Minor: 3
Creator OS  : Unknown!
Original disk size  : 2500 MB (262144 Bytes)
Current disk size   : 2500 MB (262144 Bytes)
Geometry: Cyl: 5079, Hds: 16, Sctrs: 63
: = 2499 MB (2621251584 Bytes)
Disk type   : Dynamic hard disk
Checksum: 0xeda0|0xeda0 (Good!)
UUID: b19acba1-2978-4cb3-941f-b2559cf8843f
Saved state : No
Hidden  : 0

VHD Header Summary:
---
Cookie  : cxsparse
Data offset (unusd) : 18446744073709
Table offset: 1536
Header version  : 0x0001
Max BAT size: 1250
Block size  : 2097152 (2 MB)
Parent name :
Parent UUID : ----
Parent timestamp: Sat Jan  1 00:00:00 2000
Checksum: 0xf391|0xf391 (Good!)

VHD Batmap Summary:
---
Batmap offset   : 7168
Batmap size (secs)  : 1
Batmap version  : 0x00010002
Checksum: 0x63db|0x63db (Good!)



[root@XenMaddy /]# vhd-util scan 3fdfe519-a8e0-4a0b-9fc7-cd59465e53ab.vhd
vhd=3fdfe519-a8e0-4a0b-9fc7-cd59465e53ab.vhd capacity=262144
size=1078304768 hidden=0 parent=none


*the vdh fle appears to be invalid ,*

i seeded this vdh from the following link
*/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
-m /mnt/secondary
-u 
http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-xen.vhd.bz2
http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-xen.vhd.bz2
-h
xenserver -F*

*is there any alternative link ?*



On Fri, Apr 25, 2014 at 5:16 PM, Punith S punit...@cloudbyte.com wrote:

 hi rajesh,

 ran these commands on my xen host

 [root@XenMaddy /]# vhd-util check -n
 3fdfe519-a8e0-4a0b-9fc7-cd59465e53ab.vhd
 cannot stat 3fdfe519-a8e0-4a0b-9fc7-cd59465e53ab.vhd: 2

 [root@XenMaddy /]# vhd-util scan 3fdfe519-a8e0-4a0b-9fc7-cd59465e53ab.vhd
 vhd=3fdfe519-a8e0-4a0b-9fc7-cd59465e53ab.vhd scan-error=-2
 error-message='failure scanning target'
 scan failed: -2

 its showing failure.

 referring -
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM%2C+templates%2C+Secondary+storage+troubleshooting

 thanks.


 On Fri, Apr 25, 2014 at 5:09 PM, Rajesh Battala rajesh.batt...@citrix.com
  wrote:

 Do you have vhd-util binary present in your xenserver?

 -Original Message-
 From: Punith S [mailto:punit...@cloudbyte.com]
 Sent: Friday, April 25, 2014 5:07 PM
 To: cloudstack
 Subject: SSVM's are NOT RUNNING !

 hi guys,

 i have fresh installed the cloudstack 4.3 , on adding a basic zone with
 xenserver 6.2 after seeding the secondary nfs storage mentioned in docs by


 */usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
 -m /mnt/secondary -u

 http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2
 
 http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2
 
 -h xenserver  -F*

 also tried seeding the secondary nfs storage by new link of ssvm templates


 */usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
 -m /mnt/secondary -u

 http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-xen.vhd.bz2
 
 http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-xen.vhd.bz2
 
 -h xenserver -F*

 *i'm getting the following errors.*

 WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-1:ctx-99b42320)
 destoryVDIbyNameLabel failed due to there are 0 VDIs with name
 cloud-eedde44e-93ca-4fa1-bc9f-1fa06ddc1279
 WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-1:ctx-99b42320)
 can not create vdi in sr 2d85eb6a-d5a2-94ae-ed41-4051eafe882a
 *WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-1:ctx-99b42320)
 Catch Exception com.cloud.utils.exception.CloudRuntimeException for
 template +  due to com.cloud.utils.exception.CloudRuntimeException: can not
 create vdi in sr 2d85eb6a-d5a2-94ae-ed41-4051eafe882a*
 *com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
 2d85eb6a-d5a2-94ae-ed41-4051eafe882a

Re: SSVM's are NOT RUNNING !

hi ,

seeded the new valid template

[root@cs /]#
/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
-m /mnt/secondary -u
http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2-h
xenserver -F
--2014-04-25 18:11:39--
http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2
Resolving download.cloud.com... 207.171.189.81
Connecting to download.cloud.com|207.171.189.81|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 236599855 (226M) [application/octet-stream]
Saving to:
/usr/share/cloudstack-common/scripts/storage/secondary/65b3ab61-fa76-4ba1-9742-bd0060d889c1.vhd

100%[===]
236,599,855  675K/s   in 5m 53s

2014-04-25 18:17:38 (655 KB/s) -
/usr/share/cloudstack-common/scripts/storage/secondary/65b3ab61-fa76-4ba1-9742-bd0060d889c1.vhd
saved [236599855/236599855]

Uncompressing to
/usr/share/cloudstack-common/scripts/storage/secondary/65b3ab61-fa76-4ba1-9742-bd0060d889c1.vhd.tmp
(type bz2)...could take a long time
Moving to
/mnt/secondary/template/tmpl/1/1///65b3ab61-fa76-4ba1-9742-bd0060d889c1.vhd...could
take a while
Successfully installed system VM template  to
/mnt/secondary/template/tmpl/1/1/


validated in host,

[root@XenMaddy 1]# vhd-util check -n
65b3ab61-fa76-4ba1-9742-bd0060d889c1.vhd
65b3ab61-fa76-4ba1-9742-bd0060d889c1.vhd is valid


in management server it shows that the SystemVm template(xenserver)

ReadyYesStatusDownload Complete
but still it this giving me that same exception,

 WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-65:ctx-f336fc42)
destoryVDIbyNameLabel failed due to there are 0 VDIs with name
cloud-652438c0-d61d-4582-b8ab-c117576df1ce
WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-65:ctx-f336fc42)*
can not create vdi in sr 069d1983-b2a2-2a6b-f16b-5fb44cdd2f6a*
WARN  [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-65:ctx-f336fc42)
Catch Exception com.cloud.utils.exception.CloudRuntimeException for
template +  due to com.cloud.utils.exception.CloudRuntimeException: can not
create vdi in sr 069d1983-b2a2-2a6b-f16b-5fb44cdd2f6a
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
069d1983-b2a2-2a6b-f16b-5fb44cdd2f6a
at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.
*copy_vhd_from_secondarystorage(XenServerStorageProcessor.java:848)*
.
INFO  [c.c.v.VirtualMachineManagerImpl] (secstorage-1:ctx-a4b72c2a) Unable
to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:2]
is unreachable: Unable to create Vol[14|vm=14|ROOT]:Catch Exception
com.cloud.utils.exception.CloudRuntimeException for template +  due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
069d1983-b2a2-2a6b-f16b-5fb44cdd2f6a
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1202)
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1254)
...
WARN  [c.c.c.ConsoleProxyManagerImpl] (consoleproxy-1:ctx-0305a500)
Exception while trying to start console proxy
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[ConsoleProxy|v-6-VM]Scope=interface
com.cloud.dc.DataCenter; id=1
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:921)


i can see my primary storage mounted successfully in host as SR
*069d1983-b2a2-2a6b-f16b-5fb44cdd2f6a,*
can ping the nfs server from host.
but there seems to be while creating a vdi in sr, not sure why ?

thanks.


On Fri, Apr 25, 2014 at 5:47 PM, Punith S punit...@cloudbyte.com wrote:

 hi,

 i manually copied the seeded vhd file from secondary storage to my xen
 host and ran the following commands.

 [root@XenMaddy /]# vhd-util check -n
 3fdfe519-a8e0-4a0b-9fc7-cd59465e53ab.vhd
 primary footer invalid: invalid cookie
 *3fdfe519-a8e0-4a0b-9fc7-cd59465e53ab.vhd appears invalid; dumping
 metadata*
 VHD Footer Summary:
 ---
 Cookie  : conectix
 Features: (0x0002) RESV
 File format version : Major: 1, Minor: 0
 Data offset : 512
 Timestamp   : Fri Jan  1 00:00:00 2010
 Creator Application : 'tap'
 Creator version : Major: 1, Minor: 3
 Creator OS  : Unknown!
 Original disk size  : 2500 MB (262144 Bytes)
 Current disk size   : 2500 MB (262144 Bytes)
 Geometry: Cyl: 5079, Hds: 16, Sctrs: 63
 : = 2499 MB (2621251584 Bytes)
 Disk type   : Dynamic hard disk
 Checksum: 0xeda0|0xeda0 (Good!)
 UUID: b19acba1-2978-4cb3-941f-b2559cf8843f
 Saved state : No
 Hidden  : 0

 VHD Header Summary:
 ---
 Cookie

Re: CloudStack 4.3+ Plugins

2014-04-23 Thread Punith S

hi,

its good to have privately modularized context for plugins, but how do we
inject the required variables from the component context after building the
jars in 4.3 ?
in 4.2 i used to inject the required params for my plugin from the
componentcontext.xml after building the jars. so that params values can be
changed at any point of time.
all you need to do was to just restart the management server.
ref - bean id=elastistorDataStoreProvider
 
class=org.apache.cloudstack.storage.datastore.provider.ElastistorPrimaryDataStoreProvider
property name=esmanagementip value=10.10.171.180/
property name=esapikey
value=PubSInZaCji8hrRfOsCxgbug2I2k_sRJ0i2a9qmAzZIiCTcFPmZelzx6uNK9TYgqkdohCmq1L2J9eYmUe9YO6A/
property name=esaccountid
value=9e9f67d5-e06f-4d63-a0b8-e7255cba84b8/
property name=espoolid
value=d2d15d11-0f06-3426-a097-3e6e8b36f85c/
property name=esdefaultgateway value=10.10.1.1/
property name=essubnet value=8/
property name=estntinterface value=em0/
  /bean

but in 4.3 i'm not able to access my context.xml for injecting param values
once i build my jars. !!
any workaround available to do this ?

thanks.


On Thu, Apr 24, 2014 at 12:34 AM, Chris Suich csui...@gmail.com wrote:

 Hey Matt,

 Your correct in seeing that some improvements were made in 4.3 to
 support more modularized plugins. This wiki page and its two child
 pages should help you get started:
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Modularize+Spring

 You no longer NEED to put your commands in the commands.properties.in
 file as they can be specified in the API annotation now (they can be
 put in the file to allow users to white/blacklist the file per use
 role if they desire). Each module can also specify its own application
 context so that everything is privately modularized.

 Take a look at the SolidFire storage plugin. That module is using the
 new form of Spring extensions.

 -Chris

 On Wed, Apr 23, 2014 at 10:00 AM, Matt Spurlin matt.spur...@appcore.com
 wrote:
  In version 4.2 and below to get a plugin to work, I was adding a
 dependency in the pom.xml of the Client project and modifying
 applicationContext.xml.inand commands.properties.in. 4.3 appears to have
 introduces discoverable plugins. What needs to be done differently in order
 to take advantage of this?
  Thank you for your time,
  Matt



 --
 Chris Suich
 919-334-8193
 csui...@gmail.com




-- 
regards,

punith s
cloudbyte.com

unable to create a instance in 4.3 using new devcloud and solution

2014-04-15 Thread Punith S

hi,

i'm using new devcloud for 4.3, and configured the basic zone using
devcloud python scripts.
when we launch a the downloaded tiny linux template, it throws the
following exception :

Router requires upgrade. Unable to send command to router
Unable to send command. Upgrade in progress. Please contact administrator.
and finally insufficient server capacity exception.

and then found that the virtual router needed an upgrade from current 4.2
to 4.3 version,
so initiated the upgrade for virtual router, *the UI shows the upgrade was
completed successfully but the version still remains the same(4.2)*, hence
it fails again to create a instance again. and i also checked the
/opt/storage/secondary template in devcloud, it remains the new vdh file.

my workaround solution :
 just make *false* for router.check.version in global settings and restart
the MS.

any workaround for the upgrade for router from 4.2 to 4.3 in devcloud , is
there any new template we need to seed in secondary storage ??

-- 
regards,

punith s
cloudbyte.com

Re: Devcloud2 errors on 4.4

2014-04-15 Thread Punith S

(ReflectiveMethodInvocation.java:172)
 at
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at com.sun.proxy.$Proxy147.createHostAndAgent(Unknown Source)
 at
 com.cloud.agent.manager.AgentManagerImpl$SimulateStartTask.runInContext(AgentManagerImpl.java:1070)
 at
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:724)

 Any help would be appreciated.  Thanks!

 --
 David Grizzanti
 Software Engineer
 Sungard Availability Services
 e: david.grizza...@sungard.com
 w: 215-446-1431
 c: 570-575-0315




-- 
regards,

punith s
cloudbyte.com

Re: unable to create a instance in 4.3 using new devcloud and solution

2014-04-15 Thread Punith S

thanks for the link rajesh.


On Tue, Apr 15, 2014 at 11:19 PM, Rajesh Battala
rajesh.batt...@citrix.comwrote:

 Punit,
 There is a change in the template.
 Download it from
 http://jenkins.buildacloud.org/job/build-systemvm64-master/
 You can replace the base system vm template in devcloud and use it.

 Thanks
 Rajesh Battala

 -Original Message-
 From: Punith S [mailto:punit...@cloudbyte.com]
 Sent: Tuesday, April 15, 2014 11:59 AM
 To: cloudstack
 Subject: unable to create a instance in 4.3 using new devcloud and solution

 hi,

 i'm using new devcloud for 4.3, and configured the basic zone using
 devcloud python scripts.
 when we launch a the downloaded tiny linux template, it throws the
 following exception :

 Router requires upgrade. Unable to send command to router Unable to send
 command. Upgrade in progress. Please contact administrator.
 and finally insufficient server capacity exception.

 and then found that the virtual router needed an upgrade from current 4.2
 to 4.3 version, so initiated the upgrade for virtual router, *the UI shows
 the upgrade was completed successfully but the version still remains the
 same(4.2)*, hence it fails again to create a instance again. and i also
 checked the /opt/storage/secondary template in devcloud, it remains the new
 vdh file.

 my workaround solution :
  just make *false* for router.check.version in global settings and restart
 the MS.

 any workaround for the upgrade for router from 4.2 to 4.3 in devcloud , is
 there any new template we need to seed in secondary storage ??

 --
 regards,

 punith s
 cloudbyte.com




-- 
regards,

punith s
cloudbyte.com

Re: [ANNOUNCE] Paul Angus as a committer

2014-04-12 Thread Punith S

congrats Paul! :)


On Sat, Apr 12, 2014 at 9:03 AM, Ahmad Emneina aemne...@gmail.com wrote:

 Excellent news, congrats Paul!


 On Fri, Apr 11, 2014 at 8:04 PM, Nguyen Anh Tu t...@apache.org wrote:

  Congrats, Paul!
 
  --Tuna
 
 
  On Sat, Apr 12, 2014 at 9:59 AM, Chip Childers chip.child...@gmail.com
  wrote:
 
   Congrats!
  
On Apr 11, 2014, at 8:48 PM, Sebastien Goasguen run...@gmail.com
   wrote:
   
We are pleased to announce that Paul Angus was invited to be a
  committer
   on the Apache Cloudstack project and that he accepted,
   
Join us in welcoming and congratulating Paul Angus,
   
-Sebastien on behalf of the CloudStack PMC
  
 




-- 
regards,

punith s
cloudbyte.com

Re: [QUESTION] Debugging CS VMware logic in Eclipse

2014-04-06 Thread Punith S

hi,

try deleting the existing remote debug config and try to add new one , i
guess vmware project is not imported in the existing debug config.

thanks.


On Mon, Apr 7, 2014 at 7:55 AM, Mike Tutkowski mike.tutkow...@solidfire.com
 wrote:

 Also, both codebases were compiled the following way:

 mvn -P developer,systemvm clean install -D noredist

 I ran the CS MS this way:

 mvn -pl client jetty:run -D noredist


 On Sun, Apr 6, 2014 at 8:19 PM, Mike Tutkowski 
 mike.tutkow...@solidfire.com
  wrote:

  Hi,
 
  I have a weird debug problem that perhaps someone might be able to shed
  some light on.
 
  I am trying to hit a breakpoint in VmwareStorageProcessor
  (copyTemplateToPrimaryStorage(CopyCommand)).
 
  This has worked fine in the past, but - for whatever reason - today I can
  hit breakpoints in CS core code, but not in VmwareStorageProcessor.
 
  The code executes just fine...the template is copied down from secondary
  storage and all of that. I can set and hit a breakpoint in CS code that
  sends the message; however, breakpoints in the VMware-related code get
  ignored.
 
  The code on my management server and the code on my client machine where
 I
  am debugging are at the same SHA value.
 
  Any ideas what might be going on here? I can hit an equivalent breakpoint
  in XenServer code (where the template is being copied down).
 
  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
 http://solidfire.com/solution/overview/?video=play
  *(tm)*
 



 --
 *Mike Tutkowski*
 *Senior CloudStack Developer, SolidFire Inc.*
 e: mike.tutkow...@solidfire.com
 o: 303.746.7302
 Advancing the way the world uses the
 cloudhttp://solidfire.com/solution/overview/?video=play
 *(tm)*




-- 
regards,

punith s
cloudbyte.com

Re: Unable to deploy systemvms

2014-04-02 Thread Punith S

,
 Flags: 10, { CopyCmdAnswer } }
 2014-04-02 15:18:30,915 INFO  [o.a.c.s.v.VolumeServiceImpl]
 (secstorage-1:ctx-4d6c3938) releasing lock for VMTemplateStoragePool 4
 2014-04-02 15:18:30,915 WARN  [c.c.u.d.Merovingian2]
 (secstorage-1:ctx-4d6c3938) Was unable to find lock for the key
 template_spool_ref4 and thread id 404723302
 2014-04-02 15:18:30,915 DEBUG [o.a.c.e.o.VolumeOrchestrator]
 (secstorage-1:ctx-4d6c3938) Unable to create Vol[5|vm=5|ROOT]:Catch
 Exception com.cloud.utils.exception.CloudRuntimeException for template +
 due to com.cloud.utils.exception.CloudRuntimeException: can not create vdi
 in sr d2bf95cc-8761-c31d-37a5-173304cc621e
 2014-04-02 15:18:30,915 INFO  [c.c.v.VirtualMachineManagerImpl]
 (secstorage-1:ctx-4d6c3938) Unable to contact resource.
 com.cloud.exception.StorageUnavailableException: Resource [StoragePool:1]
 is unreachable: Unable to create Vol[5|vm=5|ROOT]:Catch Exception
 com.cloud.utils.exception.CloudRuntimeException for template +  due to
 com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
 d2bf95cc-8761-c31d-37a5-173304cc621e
 at

 org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.recreateVolume(VolumeOrchestrator.java:1202)
 at

 org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.prepare(VolumeOrchestrator.java:1254)
 at

 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:962)
 at

 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761)
 at

 com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:745)
 at

 com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:261)
 at

 com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:694)
 at

 com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1278)
 at

 com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123)
 at

 com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50)
 at
 com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111)
 at
 com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:35)
 at
 com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:88)
 at

 com.cloud.vm.SystemVmLoadScanner$1.runInContext(SystemVmLoadScanner.java:79)
 at

 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at

 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at

 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at

 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at

 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at
 java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
 at

 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
 at

 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
 at

 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at

 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2014-04-02 15:18:30,920 DEBUG [c.c.v.VirtualMachineManagerImpl]
 (secstorage-1:ctx-4d6c3938) Cleaning up resources for the vm
 VM[SecondaryStorageVm|s-5-VM] in Starting state



 Regards,
 Tejas




-- 
regards,

punith s
cloudbyte.com

Re: applying patch - manually change jar file

2014-03-24 Thread Punith S

hi,

if you are using maven build,

do mvn -P developer,systemvm clean install -pl cloud-plugin-hypervisor-xen

get the newly built jar from .m2 repo in localhost and replace the old jar
in /usr/share/cloudtsack-management/webapps/client/WEB-INF/lib.

your changes will be applied.

thanks.



On Mon, Mar 24, 2014 at 2:57 PM, Tomasz Zięba t.a.zi...@gmail.com wrote:

 Hello,

 after running:   jar -uvf .

 I have information:
 adding:

 apache-cloudstack-4.2.1-src/plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.class(in
 = 238178) (out= 104028)(deflated 56%)

 New file size increases:

 ls -la

 /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-xen-4.2.1*
 -rw-r--r-- 1 root root 366550 Mar 24 09:55

 /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-xen-4.2.1-SNAPSHOT.jar

 Original file looks as follows:

 ls -la

 /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/__cloud-plugin-hypervisor-xen-4.2.1-SNAPSHOT.jar__
 -rw-r--r-- 1 root root 261682 Mar 20 14:02

 /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/__cloud-plugin-hypervisor-xen-4.2.1-SNAPSHOT.jar__

 I'm using ACS from (cloudstack-*-SNAPSHOT.el6.x86_64.rpm) rpms na centos.


 PS: I'm not java master :-)


 Best Regards,


 2014-03-24 10:15 GMT+01:00 Wido den Hollander w...@widodh.nl:

  On 03/24/2014 10:12 AM, Tomasz Zięba wrote:
 
  Hello,
 
  How do I apply a patch to the ACS 4.2.1 ?
 
  I have fixed file:
  apache-cloudstack-4.2.1-src/plugins/hypervisors/xen/src/
  com/cloud/hypervisor/xen/resource/CitrixResourceBase.java
 
  and would like to make apply this changes to cloudstack-management
 
  After performing the following commands:
 
  /usr/bin/javac -cp
  /usr/share/java/commons-collections.jar:/usr/share/
  java/commons-dbcp.jar:/usr/share/java/commons-logging.
  jar:/usr/share/java/commons-logging-api.jar:/usr/share/
  java/commons-pool.jar:/usr/share/java/commons-httpclient.
  jar:/usr/share/java/ws-commons-util.jar:/usr/share/
  java/jnetpcap.jar:/usr/share/cloudstack-agent/lib/*:/usr/
  share/cloudstack-management/lib/*:/usr/share/cloudstack-
  common/lib/*:/usr/share/cloudstack-management/webapps/
  client/WEB-INF/lib/*
  apache-cloudstack-4.2.1-src/plugins/hypervisors/xen/src/
  com/cloud/hypervisor/xen/resource/CitrixResourceBase.java
 
  #find /usr/ -name *.jar -exec grep -Hls xen.resource {} \;
 
  /usr/bin/jar -uvf
 
 /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-plugin-
  hypervisor-xen-4.2.1-SNAPSHOT.jar
  apache-cloudstack-4.2.1-src/plugins/hypervisors/xen/src/
  com/cloud/hypervisor/xen/resource/CitrixResourceBase.class
  apache-cloudstack-4.2.1-src/plugins/hypervisors/xen/src/
  com/cloud/hypervisor/xen/resource/CitrixResourceBase$SRType.class
  apache-cloudstack-4.2.1-src/plugins/hypervisors/xen/src/
  com/cloud/hypervisor/xen/resource/CitrixResourceBase$XsHost.class
  apache-cloudstack-4.2.1-src/plugins/hypervisors/xen/src/
 
 com/cloud/hypervisor/xen/resource/CitrixResourceBase$XsLocalNetwork.class
 
 
  and restart cloudstack-management, unfortunately, still uses the old
  classes.
 
 
  You should remove the same file without the -SNAPSHOT in the name. It's
  probably reading that file on boot.
 
  Wido
 
   Thank you.
 
 
 


 --
 Regards,
 Tomasz Zięba
 Twitter: @TZieba
 LinkedIn: 
 pl.linkedin.com/pub/tomasz-zięba-ph-d/3b/7a8/ab6/http://pl.linkedin.com/pub/tomasz-zi%C4%99ba-ph-d/3b/7a8/ab6/
 http://pl.linkedin.com/pub/tomasz-zi%C4%99ba-ph-d/3b/7a8/ab6/




-- 
regards,

punith s
cloudbyte.com

Re: [NFS] Adding NFS primary storage fails

2014-03-20 Thread Punith S

there must be an another exception stacktrace thrown above this hostconnect
exception from XenApi with certain ERROR code(number) , which you can find
it out in xen docs.
is the storage pool getting attached in the xen hypervisor after this ?
try executing  mount in xen and see.

thanks.


On Wed, Mar 19, 2014 at 3:50 PM, Wilder Rodrigues 
wrodrig...@schubergphilis.com wrote:

 Hi all,

 I'm trying to tests some changes I did for CLOUDSTACK-6139.

 Currently I have 3 XenServer 6.2 instances and my management server is
 running in a different machine (debian 7). I have successfully created 2
 zones, which use Local Storage. Now I'm trying to create a 3rd zone, which
 will not use local storage.

 Everything goes fine until when it tries to add the primary storage. I'm
 facing a problem related to the heartbeat file, which does not exist.

 I already tried googling, found this:
 http://markmail.org/message/gbsqsvhzp7sq37tn#query:+page:1+mid:5x6zzhtjk5dscfgy+state:results

 I checked the source of the script (
 https://github.com/apache/cloudstack/blob/master/scripts/vm/hypervisor/xenserver/setup_heartbeat_file.sh),
 but it only makes clear that the file is expected.

 tween Host[-7-Routing] and
 org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@1eca16d9
 com.cloud.utils.exception.CloudRuntimeException: Unable establish
 connection from storage head to storage pool 10 due to
 ModifyStoragePoolCommand add XenAPIException:Unable to
 setup heartbeat file entry on SR fac6c87d-d8af-102f-f89a-d58429d986a3 due
 to #6# heartbeat file
 /var/run/sr-mount/fac6c87d-d8af-102f-f89a-d58429d986a3/hb-05e6d247-7cc8-43f4-969
 c-5ba97341539a doesn't exist host:05e6d247-7cc8-43f4-969c-5ba97341539a
 pool: 10.1.1.65/opt/storage/primary10
 at
 org.apache.cloudstack.storage.datastore.provider.DefaultHostListener.hostConnect(DefaultHostListener.java:67)
 at
 com.cloud.storage.StorageManagerImpl.connectHostToSharedPool(StorageManagerImpl.java:853)
 at
 org.apache.cloudstack.storage.datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl.attachCluster(CloudStackPrimaryDataStoreLifeCycleImpl.java:418)
 at
 com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:656)
 at
 com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:176)
 at
 org.apache.cloudstack.api.command.admin.storage.CreateStoragePoolCmd.execute(CreateStoragePoolCmd.java:163)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:156)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:593)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:416)
 at
 com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:330)
 at com.cloud.api.ApiServlet.access$000(ApiServlet.java:54)
 at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)

 Any idea how to get it working?

 Cheers,
 Wilder




-- 
regards,

punith s
cloudbyte.com

Re: Anyone else see these errors in Eclipse?

2014-03-17 Thread Punith S

you can get the vmware jars from this link,


   - vmware-vim.jar
   http://zooi.widodh.nl/cloudstack/build-dep/vmware-vim.jar
   - vmware-vim25.jar
   http://zooi.widodh.nl/cloudstack/build-dep/vmware-vim25.jar


place the jars in the dependency jar locations, the errors will be gone.


On Sat, Mar 15, 2014 at 8:47 PM, Laszlo Hornyak laszlo.horn...@gmail.comwrote:

 The commiter may not have realized that this profile must be activated to
 compile the module, also there are no jenkins builds configured to compile
 this module and this is broken for about a month. No one noticed until Mike
 told about it. Maybe the build-master-noredist could be a good candidate...


 On Sat, Mar 15, 2014 at 3:51 PM, Daan Hoogland daan.hoogl...@gmail.com
 wrote:

  someone hastily checked in some code without running unit tests!
  Unforgivable, especially if it was a refactoring. I am kind of lenient
  on quick bug fixes so i say this with some restraint. (excuse my
  Dutch)
 
  Do we have a merge conflict between two features or refactorings here?
 
  On Sat, Mar 15, 2014 at 3:37 PM, Laszlo Hornyak
  laszlo.horn...@gmail.com wrote:
   No, it is really broken, 'display' should be replaced with a boolean
   expression. I believe it was something left behind after a refactoring.
  
  
   On Sat, Mar 15, 2014 at 3:17 PM, Daan Hoogland 
 daan.hoogl...@gmail.com
  wrote:
  
   so, is eclipse wrong?
  
   On Sat, Mar 15, 2014 at 11:02 AM, Laszlo Hornyak
   laszlo.horn...@gmail.com wrote:
you are not alone :)
   
   
On Sat, Mar 15, 2014 at 7:38 AM, Mike Tutkowski 
mike.tutkow...@solidfire.com wrote:
   
display cannot be resolved to a variable
   
http://i.imgur.com/Jz2swFS.png
   
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloudhttp://solidfire.com/solution/overview/?video=play
*(tm)*
   
   
   
   
--
   
EOF
  
  
  
   --
   Daan
  
  
  
  
   --
  
   EOF
 
 
 
  --
  Daan
 



 --

 EOF




-- 
regards,

punith s
cloudbyte.com

Re: Secondary storage shows agent disconncted

2014-03-17 Thread Punith S

 [agent.manager.AgentManagerImpl]
 (catalina-exec-1:null) Sending Disconnect to listener:

 com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer$$EnhancerByCGLIB$$b39613a8
 2014-03-18 09:15:44,173 DEBUG [agent.manager.AgentManagerImpl]
 (catalina-exec-1:null) Sending Disconnect to listener:

 com.cloud.hypervisor.vmware.manager.VmwareManagerImpl$$EnhancerByCGLIB$$e5731093
 2014-03-18 09:15:44,173 DEBUG [agent.manager.AgentManagerImpl]
 (catalina-exec-1:null) Sending Disconnect to listener:
 com.cloud.vm.ClusteredVirtualMachineManagerImpl$$EnhancerByCGLIB$$b05e9e4d
 2014-03-18 09:15:44,173 DEBUG [agent.manager.AgentManagerImpl]
 (catalina-exec-1:null) Sending Disconnect to listener:
 com.cloud.network.security.SecurityGroupListener
 2014-03-18 09:15:44,174 DEBUG [agent.manager.AgentManagerImpl]
 (catalina-exec-1:null) Sending Disconnect to listener:
 com.cloud.storage.listener.StoragePoolMonitor
 2014-03-18 09:15:44,174 DEBUG [agent.manager.AgentManagerImpl]
 (catalina-exec-1:null) Sending Disconnect to listener:
 com.cloud.storage.secondary.SecondaryStorageListener
 2014-03-18 09:15:44,174 DEBUG [agent.manager.AgentManagerImpl]
 (catalina-exec-1:null) Sending Disconnect to listener:
 com.cloud.network.NetworkManagerImpl$$EnhancerByCGLIB$$5a1e7d69
 2014-03-18 09:15:44,174 DEBUG [agent.manager.AgentManagerImpl]
 (catalina-exec-1:null) Sending Disconnect to listener:
 com.cloud.agent.manager.AgentMonitor$$EnhancerByCGLIB$$cabeffc9
 2014-03-18 09:15:44,174 DEBUG [agent.manager.AgentManagerImpl]
 (catalina-exec-1:null) Sending Disconnect to listener:
 com.cloud.storage.download.DownloadListener
 2014-03-18 09:15:44,175 DEBUG [agent.manager.AgentManagerImpl]
 (catalina-exec-1:null) Sending Disconnect to listener:
 com.cloud.storage.upload.UploadListener
 2014-03-18 09:15:44,175 DEBUG [agent.manager.AgentManagerImpl]
 (catalina-exec-1:null) Sending Disconnect to listener:
 com.cloud.storage.LocalStoragePoolListener$$EnhancerByCGLIB$$5aad25fd
 2014-03-18 09:15:44,175 DEBUG [agent.manager.AgentManagerImpl]
 (catalina-exec-1:null) Sending Disconnect to listener:
 com.cloud.capacity.StorageCapacityListener
 2014-03-18 09:15:44,175 DEBUG [agent.manager.AgentManagerImpl]
 (catalina-exec-1:null) Sending Disconnect to listener:
 com.cloud.capacity.ComputeCapacityListener
 2014-03-18 09:15:44,175 DEBUG [agent.manager.AgentManagerImpl]
 (catalina-exec-1:null) Sending Disconnect to listener:
 com.cloud.consoleproxy.ConsoleProxyListener
 2014-03-18 09:15:44,176 DEBUG [agent.manager.AgentManagerImpl]
 (catalina-exec-1:null) Sending Disconnect to listener:
 com.cloud.network.SshKeysDistriMonitor
 2014-03-18 09:15:44,176 DEBUG [agent.manager.AgentManagerImpl]
 (catalina-exec-1:null) Sending Disconnect to listener:

 com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl$$EnhancerByCGLIB$$5d17a4f1
 2014-03-18 09:15:44,176 DEBUG [agent.manager.AgentManagerImpl]
 (catalina-exec-1:null) Sending Disconnect to listener:
 com.cloud.network.NetworkUsageManagerImpl$DirectNetworkStatsListener
 2014-03-18 09:15:44,176 DEBUG [cloud.network.NetworkUsageManagerImpl]
 (catalina-exec-1:null) Disconnected called on 2 with status Alert
 2014-03-18 09:15:44,177 DEBUG [cloud.host.Status] (catalina-exec-1:null)
 Transition:[Resource state = Enabled, Agent *event = AgentDisconnected*,
 Host id = 2, name = nfs://10.129.151.51/vol/secondary]
 2014-03-18 09:15:44,208 DEBUG [cloud.host.Status] (catalina-exec-1:null)
 Agent status update: [id = 2; name = nfs://10.129.151.51/vol/secondary;
 old
 status = Connecting; *event = AgentDisconnected;* new status = Alert; old
 update count = 1; new update count = 2]
 2014-03-18 09:15:44,208 DEBUG [agent.manager.ClusteredAgentManagerImpl]
 (catalina-exec-1:null) Notifying other nodes of to disconnect
 2014-03-18 09:15:44,210 DEBUG [cloud.host.Status] (catalina-exec-1:null)
 Transition:[Resource state = Enabled, Agent event = Ready, Host id = 2,
 name = nfs://10.129.151.51/vol/secondary]
 2014-03-18 09:15:44,212 DEBUG [cloud.host.Status] (catalina-exec-1:null)
 Unable to update host for event:Ready. Name=nfs://
 10.129.151.51/vol/secondary;
 New=[status=Up:msid=null:lastpinged=1362416351];
 Old=[status=Connecting:msid=null:lastpinged=1362416351];
 DB=[status=Connecting:msid=345049271977:lastpinged=1362416351:old update
 count=2]
 2014-03-18 09:15:44,213 DEBUG [cloud.host.Status] (catalina-exec-1:null)
 Transition:[Resource state = Enabled, *Agent event = AgentDisconnected*,
 Host id = 2, name = nfs://10.129.151.51/vol/secondary]
 2014-03-18 09:15:44,245 DEBUG [cloud.host.Status] (catalina-exec-1:null)
 Agent status update: [id = 2; name = nfs://10.129.151.51/vol/secondary;
 old
 status = Alert; *event = AgentDisconnected; new status = Alert;* old update
 count = 2; new update count = 3]
 2014-03-18 09:15:44,494 INFO  [cloud.resource.ResourceManagerImpl]
 (catalina-exec-1:null) server resources successfully discovered by
 SecondaryStorage


 Regards,
 Tejas




-- 
regards,

punith s
cloudbyte.com

Re: Review Request 19021: Cloudbyte Elastistor storage plug-in

2014-03-14 Thread Punith S

hi guys,

i have resolved all issues with fixes and refactoring of plugin code, its
good to go now ,
i'll submit once i get the ship it message. thanks for the review.


On Fri, Mar 14, 2014 at 11:19 AM, punith s punit...@cloudbyte.com wrote:

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

 On March 14th, 2014, 3:54 a.m. IST, *Mike Tutkowski* wrote:


 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.javahttps://reviews.apache.org/r/19021/diff/5/?file=518383#file518383line99
  (Diff
 revision 5)

 99

 if(details.get(esaccountid) != null)

   Does this plug-in support multiple CloudByte SANs at the same time?

 It looks like whatever values you set most recently for ElastistorUtil will 
 be utilized if you don't provide them in the details. Is this OK if you don't 
 provide all of the details for your second or more SAN?

  yes it will.

 yes, we are expecting admin to use cloudmonkey to create storage pool if the 
 elastistor params are not set for the first time.
 once the details are set he can use cloudstack UI to add or deleted storage 
 pools on the same SAN but if he wants to use different SAN
 we are expecting him to use cloudmonkey again to change elastistor params 
 through details map.

 thanks.




 - punith

 On March 13th, 2014, 2:46 p.m. IST, punith s wrote:
   Review request for cloudstack, edison su and Mike Tutkowski.
 By punith s.

 *Updated March 13, 2014, 2:46 p.m.*
  *Repository: * cloudstack-git
 Description

 This patch implements a basic storage plug-in for cloudbyte elastistor 
 v1.3.0, The plug-in is a new feature for cloudstack 4.4 and above.

 this does not implement managed storage yet, it is been integrated only with 
 CreateStoragePool and DeleteStoragePool api's.

 the desired behavior of the plugin are:

 * Allow an Admin to create a primary storage at cluster level, hence creates 
 a volume in elastistor and gets attached to the host with the given 
 capacityiops and capacitybytes through CreateStoragePool api with provider 
 being elastistor.

 *Allow an admin to delete a primary storage at cluster level, hence it 
 deletes the volume from host in cloudstack and deletes the respective volume 
 in elastistor.

 * volume and datadisks fuctions performs the default storage fuctions, ie. 
 the driver extends the CloudStackPrimaryDataStoreDriverImpl.

 * support for both nfs and icsci primary storage.

   Testing

 Build test using,

 mvn -P developer,systemvm clean install, which is successful.

 Manual testing has been performed using cloudmonkey.

 * Creating a primary storage based on cloudbyte storage plugin.

 cloudmonkey# create storagepool scope=cluster 
 zoneid=dac7223c-6d09-4dcb-82fb-bdecf7c657f5 
 podid=20a613c4-eccf-4fdc-b8ca-c51df483326f 
 clusterid=9a89bc12-bf00-496b-b1d8-8e92cdf1795f name=cloudbytevolume 
 provider=elastistor url=nfs://10.10.171.137/cloudbytetest capacityiops=500 
 capacitybytes=214748364800 tags=cloudbytetest
 storagepool:
 name = cloudbytevolume
 id = 57f70aa4-659b-3b53-b8ab-2f712474f107
 capacityiops = 500
 clusterid = 9a89bc12-bf00-496b-b1d8-8e92cdf1795f
 clustername = test000
 created = 2014-03-11T12:42:38+0530
 disksizeallocated = 0
 disksizetotal = 214748364800
 hypervisor = Any
 ipaddress = 10.10.171.137
 path = /cloudbytetest
 podid = 20a613c4-eccf-4fdc-b8ca-c51df483326f
 podname = test00
 scope = CLUSTER
 state = Up
 tags = cloudbytetest
 type = NetworkFilesystem
 zoneid = dac7223c-6d09-4dcb-82fb-bdecf7c657f5
 zonename = DevCloud0

 * Deleting the primary storage based on cloudbyte storage plugin.

 cloudmonkey# delete storagepool id=57f70aa4-659b-3b53-b8ab-2f712474f107
 success = true

 * creation of primary storage with negative capacityiops throws an exception.

 * creation of primary storage with already available name and ip throws an 
 exception.

 * if the elastistor params which are required for plugin configuration are 
 not injected through spring-storage-volume-cloudbyte-context.xml, it can be 
 set from details map.

 cloudmonkey# create storagepool scope=cluster 
 zoneid=afacc706-3f4d-4f50-82e6-bf0f82959ba8 
 podid=821ad540-6c98-43f3-935d-72a47a319b20 
 clusterid=e0ced156-532e-4941-99c0-f34ff1727544 name=nfsvol 
 provider=elastistor url=nfs://10.10.171.143/volnfs 
 details[0].esaccountid=9e9f67d5-e06f-4d63-a0b8-e7255cba84b8 
 details[1].espoolid=d2d15d11-0f06-3426-a097-3e6e8b36f85c 
 details[2].esdefaultgateway=10.10.1.1 details[3].essubnet=8  
 details[4].estntinterface=em0 details[5].esmanagementip=10.10.171.180
 details[6].esapikey=PubSInZaCji8hrRfOsCxgbug2I2k_sRJ0i2a9qmAzZIiCTcFPmZelzx6uNK9TYgqkdohCmq1L2J9eYmUe9YO6A
  capacityiops=100 capacitybytes=214748364800

 storagepool:
 name = nfsvol
 id = 7ea08bf6-777a-3553-8f1e-c3a9f9b626cb
 capacityiops = 100
 clusterid = e0ced156-532e-4941-99c0-f34ff1727544
 clustername = test000
 created = 2014-03-12T17:45:10+0530
 disksizeallocated = 0

Re: Review Request 19021: Cloudbyte Elastistor storage plug-in



 On March 12, 2014, 10:19 p.m., Mike Tutkowski wrote:
  plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorUtil.java,
   line 495
  https://reviews.apache.org/r/19021/diff/2/?file=517486#file517486line495
 
  I like how you removed the standalone files for each command and 
  integrated the commands into this one file.
  
  Quick question: It looks like your testing includes creating and 
  deleting a storage pool, which would lead to the creation and deletion of a 
  SAN volume. Have you had a chance to create a root disk and/or a data disk 
  on such a storage pool and then delete it?

thanks mike.

yea of course, i have tested all volume related api's such as createVolume, 
attachVolume, detachVolume and deleteVolume through my plugin.
even we can make volumes to sit on specific storage pool by mapping with unique 
tags with respect to your concept.
for more details i have added the cloudmonkey responses for volume api's.
 


- punith


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


On March 12, 2014, 9:39 p.m., punith s wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/19021/
 ---
 
 (Updated March 12, 2014, 9:39 p.m.)
 
 
 Review request for cloudstack, edison su and Mike Tutkowski.
 
 
 Repository: cloudstack-git
 
 
 Description
 ---
 
 This patch implements a basic storage plug-in for cloudbyte elastistor 
 v1.3.0, The plug-in is a new feature for cloudstack 4.4 and above.
 
 this does not implement managed storage yet, it is been integrated only with 
 CreateStoragePool and DeleteStoragePool api's.
 
 the desired behavior of the plugin are:
 
 * Allow an Admin to create a primary storage at cluster level, hence creates 
 a volume in elastistor and gets attached to the host with the given 
 capacityiops and capacitybytes through CreateStoragePool api with provider 
 being elastistor.
 
 *Allow an admin to delete a primary storage at cluster level, hence it 
 deletes the volume from host in cloudstack and deletes the respective volume 
 in elastistor.
 
 * volume and datadisks fuctions performs the default storage fuctions, ie. 
 the driver extends the CloudStackPrimaryDataStoreDriverImpl.
 
 * support for both nfs and icsci primary storage.
 
 
 Diffs
 -
 
   plugins/storage/volume/cloudbyte/pom.xml PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/BaseCommand.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/ElastiCenterClient.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/client/ElastiCenterCommand.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/AddQosGroupCmd.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/CreateTsmCmd.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/CreateVolumeCmd.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/DeleteTsmCmd.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/DeleteVolumeCmd.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/ListCapabilitiesCmd.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/ListTsmCmd.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/command/QueryAsyncJobResultCmd.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/Async.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/Capabilities.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/FileSystem.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/model/FileSystemWrapper.java
  PRE-CREATION

Re: Review Request 19021: Cloudbyte Elastistor storage plug-in

 = 10.10.171.143
path = /volnfs
podid = 821ad540-6c98-43f3-935d-72a47a319b20
podname = test00
scope = CLUSTER
state = Up
type = NetworkFilesystem
zoneid = afacc706-3f4d-4f50-82e6-bf0f82959ba8
zonename = DevCloud0

* creation of volume on created storage pool.
cloudmonkey# create volume zoneid=afacc706-3f4d-4f50-82e6-bf0f82959ba8 
diskofferingid=f20e3b76-82e3-43d1-91e3-3ff337d7181d name=testvolume

accountid = 819b1dfe-a9d3-11e3-a500-f46d04ee0527
cmd = org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd
created = 2014-03-13T11:51:27+0530
jobid = 596294b8-2b49-4b49-8526-9117cf56c95d
jobprocstatus = 0
jobresult:
volume:
name = testvolume
id = e079281e-d822-4b90-9e85-9648350a0369
account = admin
created = 2014-03-13T11:51:27+0530
destroyed = False
diskofferingdisplaytext = Small Disk, 5 GB
diskofferingid = f20e3b76-82e3-43d1-91e3-3ff337d7181d
diskofferingname = Small
displayvolume = True
domain = ROOT
domainid = 819ae3b6-a9d3-11e3-a500-f46d04ee0527
isextractable = True
jobid = 596294b8-2b49-4b49-8526-9117cf56c95d
jobstatus = 0
size = 5368709120
state = Allocated
storagetype = shared
tags:
type = DATADISK
zoneid = afacc706-3f4d-4f50-82e6-bf0f82959ba8
zonename = DevCloud0
jobresultcode = 0
jobresulttype = object
jobstatus = 1
userid = 819b856e-a9d3-11e3-a500-f46d04ee0527

* attaching a specific volume.
cloudmonkey# attach volume id=e079281e-d822-4b90-9e85-9648350a0369 
virtualmachineid=3e6eeab1-e624-461e-94e0-230215a8dbc3

accountid = 819b1dfe-a9d3-11e3-a500-f46d04ee0527
cmd = org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
created = 2014-03-13T11:55:09+0530
jobid = 364d7636-72ad-410c-891c-c38ac34b6d42
jobprocstatus = 0
jobresult:
volume:
id = e079281e-d822-4b90-9e85-9648350a0369
name = testvolume
account = admin
attached = 2014-03-13T11:55:11+0530
created = 2014-03-13T11:51:27+0530
destroyed = False
deviceid = 2
diskofferingdisplaytext = Small Disk, 5 GB
diskofferingid = f20e3b76-82e3-43d1-91e3-3ff337d7181d
diskofferingname = Small
displayvolume = True
domain = ROOT
domainid = 819ae3b6-a9d3-11e3-a500-f46d04ee0527
hypervisor = XenServer
isextractable = True
jobid = 364d7636-72ad-410c-891c-c38ac34b6d42
jobstatus = 0
size = 5368709120
state = Ready
storage = okay
storagetype = shared
tags:
type = DATADISK
virtualmachineid = 3e6eeab1-e624-461e-94e0-230215a8dbc3
vmdisplayname = tiny
vmname = tiny
vmstate = Running
zoneid = afacc706-3f4d-4f50-82e6-bf0f82959ba8
zonename = DevCloud0
jobresultcode = 0
jobresulttype = object
jobstatus = 1
userid = 819b856e-a9d3-11e3-a500-f46d04ee0527

*detaching a specific volume.
cloudmonkey# detach volume id=e079281e-d822-4b90-9e85-9648350a0369

accountid = 819b1dfe-a9d3-11e3-a500-f46d04ee0527
cmd = org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd
created = 2014-03-13T11:57:40+0530
jobid = 38fb6463-7d95-4d4c-8a50-1ec8a1c9ba98
jobprocstatus = 0
jobresult:
volume:
id = e079281e-d822-4b90-9e85-9648350a0369
name = testvolume
account = admin
created = 2014-03-13T11:51:27+0530
destroyed = False
diskofferingdisplaytext = Small Disk, 5 GB
diskofferingid = f20e3b76-82e3-43d1-91e3-3ff337d7181d
diskofferingname = Small
displayvolume = True
domain = ROOT
domainid = 819ae3b6-a9d3-11e3-a500-f46d04ee0527
hypervisor = XenServer
isextractable = True
jobid = 38fb6463-7d95-4d4c-8a50-1ec8a1c9ba98
jobstatus = 0
size = 5368709120
state = Ready
storage = okay
storagetype = shared
tags:
type = DATADISK
zoneid = afacc706-3f4d-4f50-82e6-bf0f82959ba8
zonename = DevCloud0
jobresultcode = 0
jobresulttype = object
jobstatus = 1
userid = 819b856e-a9d3-11e3-a500-f46d04ee0527

*deleting a volume
cloudmonkey# delete volume id=e079281e-d822-4b90-9e85-9648350a0369
success = true


Thanks,

punith s

Re: Review Request 19021: Cloudbyte Elastistor storage plug-in



 On March 13, 2014, 3:37 a.m., edison su wrote:
  Could you upload a new patch? I can't apply it on master branch, git 
  complains that some files are not indexed.

hi edison, 
i have added a fresh new patch like as if it's a new patch.

thanks.


- punith


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


On March 13, 2014, 12:21 p.m., punith s wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/19021/
 ---
 
 (Updated March 13, 2014, 12:21 p.m.)
 
 
 Review request for cloudstack, edison su and Mike Tutkowski.
 
 
 Repository: cloudstack-git
 
 
 Description
 ---
 
 This patch implements a basic storage plug-in for cloudbyte elastistor 
 v1.3.0, The plug-in is a new feature for cloudstack 4.4 and above.
 
 this does not implement managed storage yet, it is been integrated only with 
 CreateStoragePool and DeleteStoragePool api's.
 
 the desired behavior of the plugin are:
 
 * Allow an Admin to create a primary storage at cluster level, hence creates 
 a volume in elastistor and gets attached to the host with the given 
 capacityiops and capacitybytes through CreateStoragePool api with provider 
 being elastistor.
 
 *Allow an admin to delete a primary storage at cluster level, hence it 
 deletes the volume from host in cloudstack and deletes the respective volume 
 in elastistor.
 
 * volume and datadisks fuctions performs the default storage fuctions, ie. 
 the driver extends the CloudStackPrimaryDataStoreDriverImpl.
 
 * support for both nfs and icsci primary storage.
 
 
 Diffs
 -
 
   client/pom.xml af724b1 
   plugins/pom.xml 097f224 
   plugins/storage/volume/cloudbyte/pom.xml PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/module.properties
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorHostListener.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorPrimaryDataStoreProvider.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorUtil.java
  PRE-CREATION 
 
 Diff: https://reviews.apache.org/r/19021/diff/
 
 
 Testing
 ---
 
 Build test using, 
 
 mvn -P developer,systemvm clean install, which is successful.
 
 Manual testing has been performed using cloudmonkey.
 
 * Creating a primary storage based on cloudbyte storage plugin.
 
 cloudmonkey# create storagepool scope=cluster 
 zoneid=dac7223c-6d09-4dcb-82fb-bdecf7c657f5 
 podid=20a613c4-eccf-4fdc-b8ca-c51df483326f 
 clusterid=9a89bc12-bf00-496b-b1d8-8e92cdf1795f name=cloudbytevolume 
 provider=elastistor url=nfs://10.10.171.137/cloudbytetest capacityiops=500 
 capacitybytes=214748364800 tags=cloudbytetest
 storagepool:
 name = cloudbytevolume
 id = 57f70aa4-659b-3b53-b8ab-2f712474f107
 capacityiops = 500
 clusterid = 9a89bc12-bf00-496b-b1d8-8e92cdf1795f
 clustername = test000
 created = 2014-03-11T12:42:38+0530
 disksizeallocated = 0
 disksizetotal = 214748364800
 hypervisor = Any
 ipaddress = 10.10.171.137
 path = /cloudbytetest
 podid = 20a613c4-eccf-4fdc-b8ca-c51df483326f
 podname = test00
 scope = CLUSTER
 state = Up
 tags = cloudbytetest
 type = NetworkFilesystem
 zoneid = dac7223c-6d09-4dcb-82fb-bdecf7c657f5
 zonename = DevCloud0
 
 * Deleting the primary storage based on cloudbyte storage plugin.
 
 cloudmonkey# delete storagepool id=57f70aa4-659b-3b53-b8ab-2f712474f107
 success = true
 
 * creation of primary storage with negative capacityiops throws an exception.
 
 * creation of primary storage with already available name and ip throws an 
 exception.
 
 * if the elastistor params which are required for plugin configuration are 
 not injected through spring-storage-volume-cloudbyte-context.xml, it can be 
 set from details map.
 
 cloudmonkey# create storagepool scope=cluster 
 zoneid=afacc706-3f4d-4f50-82e6-bf0f82959ba8 
 podid=821ad540-6c98-43f3-935d-72a47a319b20 
 clusterid=e0ced156-532e-4941-99c0-f34ff1727544 name=nfsvol 
 provider=elastistor url=nfs://10.10.171.143/volnfs 
 details[0].esaccountid=9e9f67d5-e06f-4d63-a0b8-e7255cba84b8 
 details[1].espoolid=d2d15d11-0f06-3426-a097

Re: Review Request 19021: Cloudbyte Elastistor storage plug-in

jobstatus = 0
size = 5368709120
state = Allocated
storagetype = shared
tags:
type = DATADISK
zoneid = afacc706-3f4d-4f50-82e6-bf0f82959ba8
zonename = DevCloud0
jobresultcode = 0
jobresulttype = object
jobstatus = 1
userid = 819b856e-a9d3-11e3-a500-f46d04ee0527

* attaching a specific volume.
cloudmonkey# attach volume id=e079281e-d822-4b90-9e85-9648350a0369 
virtualmachineid=3e6eeab1-e624-461e-94e0-230215a8dbc3

accountid = 819b1dfe-a9d3-11e3-a500-f46d04ee0527
cmd = org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
created = 2014-03-13T11:55:09+0530
jobid = 364d7636-72ad-410c-891c-c38ac34b6d42
jobprocstatus = 0
jobresult:
volume:
id = e079281e-d822-4b90-9e85-9648350a0369
name = testvolume
account = admin
attached = 2014-03-13T11:55:11+0530
created = 2014-03-13T11:51:27+0530
destroyed = False
deviceid = 2
diskofferingdisplaytext = Small Disk, 5 GB
diskofferingid = f20e3b76-82e3-43d1-91e3-3ff337d7181d
diskofferingname = Small
displayvolume = True
domain = ROOT
domainid = 819ae3b6-a9d3-11e3-a500-f46d04ee0527
hypervisor = XenServer
isextractable = True
jobid = 364d7636-72ad-410c-891c-c38ac34b6d42
jobstatus = 0
size = 5368709120
state = Ready
storage = okay
storagetype = shared
tags:
type = DATADISK
virtualmachineid = 3e6eeab1-e624-461e-94e0-230215a8dbc3
vmdisplayname = tiny
vmname = tiny
vmstate = Running
zoneid = afacc706-3f4d-4f50-82e6-bf0f82959ba8
zonename = DevCloud0
jobresultcode = 0
jobresulttype = object
jobstatus = 1
userid = 819b856e-a9d3-11e3-a500-f46d04ee0527

*detaching a specific volume.
cloudmonkey# detach volume id=e079281e-d822-4b90-9e85-9648350a0369

accountid = 819b1dfe-a9d3-11e3-a500-f46d04ee0527
cmd = org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd
created = 2014-03-13T11:57:40+0530
jobid = 38fb6463-7d95-4d4c-8a50-1ec8a1c9ba98
jobprocstatus = 0
jobresult:
volume:
id = e079281e-d822-4b90-9e85-9648350a0369
name = testvolume
account = admin
created = 2014-03-13T11:51:27+0530
destroyed = False
diskofferingdisplaytext = Small Disk, 5 GB
diskofferingid = f20e3b76-82e3-43d1-91e3-3ff337d7181d
diskofferingname = Small
displayvolume = True
domain = ROOT
domainid = 819ae3b6-a9d3-11e3-a500-f46d04ee0527
hypervisor = XenServer
isextractable = True
jobid = 38fb6463-7d95-4d4c-8a50-1ec8a1c9ba98
jobstatus = 0
size = 5368709120
state = Ready
storage = okay
storagetype = shared
tags:
type = DATADISK
zoneid = afacc706-3f4d-4f50-82e6-bf0f82959ba8
zonename = DevCloud0
jobresultcode = 0
jobresulttype = object
jobstatus = 1
userid = 819b856e-a9d3-11e3-a500-f46d04ee0527

*deleting a volume
cloudmonkey# delete volume id=e079281e-d822-4b90-9e85-9648350a0369
success = true


Thanks,

punith s

Re: Review Request 19021: Cloudbyte Elastistor storage plug-in

podid = 821ad540-6c98-43f3-935d-72a47a319b20
podname = test00
scope = CLUSTER
state = Up
type = NetworkFilesystem
zoneid = afacc706-3f4d-4f50-82e6-bf0f82959ba8
zonename = DevCloud0

* creation of volume on created storage pool.
cloudmonkey# create volume zoneid=afacc706-3f4d-4f50-82e6-bf0f82959ba8 
diskofferingid=f20e3b76-82e3-43d1-91e3-3ff337d7181d name=testvolume

accountid = 819b1dfe-a9d3-11e3-a500-f46d04ee0527
cmd = org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd
created = 2014-03-13T11:51:27+0530
jobid = 596294b8-2b49-4b49-8526-9117cf56c95d
jobprocstatus = 0
jobresult:
volume:
name = testvolume
id = e079281e-d822-4b90-9e85-9648350a0369
account = admin
created = 2014-03-13T11:51:27+0530
destroyed = False
diskofferingdisplaytext = Small Disk, 5 GB
diskofferingid = f20e3b76-82e3-43d1-91e3-3ff337d7181d
diskofferingname = Small
displayvolume = True
domain = ROOT
domainid = 819ae3b6-a9d3-11e3-a500-f46d04ee0527
isextractable = True
jobid = 596294b8-2b49-4b49-8526-9117cf56c95d
jobstatus = 0
size = 5368709120
state = Allocated
storagetype = shared
tags:
type = DATADISK
zoneid = afacc706-3f4d-4f50-82e6-bf0f82959ba8
zonename = DevCloud0
jobresultcode = 0
jobresulttype = object
jobstatus = 1
userid = 819b856e-a9d3-11e3-a500-f46d04ee0527

* attaching a specific volume.
cloudmonkey# attach volume id=e079281e-d822-4b90-9e85-9648350a0369 
virtualmachineid=3e6eeab1-e624-461e-94e0-230215a8dbc3

accountid = 819b1dfe-a9d3-11e3-a500-f46d04ee0527
cmd = org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
created = 2014-03-13T11:55:09+0530
jobid = 364d7636-72ad-410c-891c-c38ac34b6d42
jobprocstatus = 0
jobresult:
volume:
id = e079281e-d822-4b90-9e85-9648350a0369
name = testvolume
account = admin
attached = 2014-03-13T11:55:11+0530
created = 2014-03-13T11:51:27+0530
destroyed = False
deviceid = 2
diskofferingdisplaytext = Small Disk, 5 GB
diskofferingid = f20e3b76-82e3-43d1-91e3-3ff337d7181d
diskofferingname = Small
displayvolume = True
domain = ROOT
domainid = 819ae3b6-a9d3-11e3-a500-f46d04ee0527
hypervisor = XenServer
isextractable = True
jobid = 364d7636-72ad-410c-891c-c38ac34b6d42
jobstatus = 0
size = 5368709120
state = Ready
storage = okay
storagetype = shared
tags:
type = DATADISK
virtualmachineid = 3e6eeab1-e624-461e-94e0-230215a8dbc3
vmdisplayname = tiny
vmname = tiny
vmstate = Running
zoneid = afacc706-3f4d-4f50-82e6-bf0f82959ba8
zonename = DevCloud0
jobresultcode = 0
jobresulttype = object
jobstatus = 1
userid = 819b856e-a9d3-11e3-a500-f46d04ee0527

*detaching a specific volume.
cloudmonkey# detach volume id=e079281e-d822-4b90-9e85-9648350a0369

accountid = 819b1dfe-a9d3-11e3-a500-f46d04ee0527
cmd = org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd
created = 2014-03-13T11:57:40+0530
jobid = 38fb6463-7d95-4d4c-8a50-1ec8a1c9ba98
jobprocstatus = 0
jobresult:
volume:
id = e079281e-d822-4b90-9e85-9648350a0369
name = testvolume
account = admin
created = 2014-03-13T11:51:27+0530
destroyed = False
diskofferingdisplaytext = Small Disk, 5 GB
diskofferingid = f20e3b76-82e3-43d1-91e3-3ff337d7181d
diskofferingname = Small
displayvolume = True
domain = ROOT
domainid = 819ae3b6-a9d3-11e3-a500-f46d04ee0527
hypervisor = XenServer
isextractable = True
jobid = 38fb6463-7d95-4d4c-8a50-1ec8a1c9ba98
jobstatus = 0
size = 5368709120
state = Ready
storage = okay
storagetype = shared
tags:
type = DATADISK
zoneid = afacc706-3f4d-4f50-82e6-bf0f82959ba8
zonename = DevCloud0
jobresultcode = 0
jobresulttype = object
jobstatus = 1
userid = 819b856e-a9d3-11e3-a500-f46d04ee0527

*deleting a volume
cloudmonkey# delete volume id=e079281e-d822-4b90-9e85-9648350a0369
success = true


Thanks,

punith s

Re: Review Request 19021: Cloudbyte Elastistor storage plug-in



 On March 12, 2014, 10:19 p.m., Mike Tutkowski wrote:
  plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorUtil.java,
   line 495
  https://reviews.apache.org/r/19021/diff/2/?file=517486#file517486line495
 
  I like how you removed the standalone files for each command and 
  integrated the commands into this one file.
  
  Quick question: It looks like your testing includes creating and 
  deleting a storage pool, which would lead to the creation and deletion of a 
  SAN volume. Have you had a chance to create a root disk and/or a data disk 
  on such a storage pool and then delete it?
 
 punith s wrote:
 thanks mike.
 
 yea of course, i have tested all volume related api's such as 
 createVolume, attachVolume, detachVolume and deleteVolume through my plugin.
 even we can make volumes to sit on specific storage pool by mapping with 
 unique tags with respect to your concept.
 for more details i have added the cloudmonkey responses for volume api's.


and yes while creating a instance root disk will be mapped to the required 
storage pool by creating a new compute offering with the storage tag of the 
corresponding storage pool.


- punith


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


On March 13, 2014, 2:46 p.m., punith s wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/19021/
 ---
 
 (Updated March 13, 2014, 2:46 p.m.)
 
 
 Review request for cloudstack, edison su and Mike Tutkowski.
 
 
 Repository: cloudstack-git
 
 
 Description
 ---
 
 This patch implements a basic storage plug-in for cloudbyte elastistor 
 v1.3.0, The plug-in is a new feature for cloudstack 4.4 and above.
 
 this does not implement managed storage yet, it is been integrated only with 
 CreateStoragePool and DeleteStoragePool api's.
 
 the desired behavior of the plugin are:
 
 * Allow an Admin to create a primary storage at cluster level, hence creates 
 a volume in elastistor and gets attached to the host with the given 
 capacityiops and capacitybytes through CreateStoragePool api with provider 
 being elastistor.
 
 *Allow an admin to delete a primary storage at cluster level, hence it 
 deletes the volume from host in cloudstack and deletes the respective volume 
 in elastistor.
 
 * volume and datadisks fuctions performs the default storage fuctions, ie. 
 the driver extends the CloudStackPrimaryDataStoreDriverImpl.
 
 * support for both nfs and icsci primary storage.
 
 
 Diffs
 -
 
   client/pom.xml af724b1 
   plugins/pom.xml 097f224 
   plugins/storage/volume/cloudbyte/pom.xml PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/module.properties
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorHostListener.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorPrimaryDataStoreProvider.java
  PRE-CREATION 
   
 plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorUtil.java
  PRE-CREATION 
 
 Diff: https://reviews.apache.org/r/19021/diff/
 
 
 Testing
 ---
 
 Build test using, 
 
 mvn -P developer,systemvm clean install, which is successful.
 
 Manual testing has been performed using cloudmonkey.
 
 * Creating a primary storage based on cloudbyte storage plugin.
 
 cloudmonkey# create storagepool scope=cluster 
 zoneid=dac7223c-6d09-4dcb-82fb-bdecf7c657f5 
 podid=20a613c4-eccf-4fdc-b8ca-c51df483326f 
 clusterid=9a89bc12-bf00-496b-b1d8-8e92cdf1795f name=cloudbytevolume 
 provider=elastistor url=nfs://10.10.171.137/cloudbytetest capacityiops=500 
 capacitybytes=214748364800 tags=cloudbytetest
 storagepool:
 name = cloudbytevolume
 id = 57f70aa4-659b-3b53-b8ab-2f712474f107
 capacityiops = 500
 clusterid = 9a89bc12-bf00-496b-b1d8-8e92cdf1795f
 clustername = test000
 created = 2014-03-11T12:42:38+0530
 disksizeallocated = 0
 disksizetotal = 214748364800
 hypervisor = Any
 ipaddress = 10.10.171.137
 path = /cloudbytetest
 podid = 20a613c4-eccf-4fdc-b8ca-c51df483326f
 podname = test00
 scope = CLUSTER
 state = Up
 tags = cloudbytetest

Re: Review Request 19021: Cloudbyte Elastistor storage plug-in