[jira] [Commented] (CLOUDSTACK-2701) Enable storage migration for VMware resources
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13672814#comment-13672814 ] ASF subversion and git services commented on CLOUDSTACK-2701: - Commit 984b59d1eecf677ad2d824d37175976f9b6e2eec in branch refs/heads/master from Sateesh Chodapuneedi sate...@apache.org [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=984b59d ] CLOUDSTACK-2701 Moved bean VmwareStorageMotionStrategy to nonossComponentContext.xml.in Enable storage migration for VMware resources - Key: CLOUDSTACK-2701 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Storage vMotion allows VMs to be moved from one host to another, along with storage across datastores in datacenter. It provides the option to live migrate a VM’s disks along with the VM itself. It is now possible to migrate a VM from one datastore to another, or even to migrate a VM’s disks from one datastore to another with VM running on same host, all while the VM is running. This issue is to track the support of storage vMotion for VMware resources in cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done to branch vmware-storage-motion. Just now created this ticket to deal with specific areas in implementation that is well contained and limited to VMware resource only. Commits related to VmwareStorageMotionStrategy class and it's implementation along with commands MigrateWithStorageCommand and MigrateVolumeCommand are done under CLOUDSTACK-659 ticket. Release Planning: Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer (section VMware resource) Feature branch: vmware-storage-motion -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2701) Enable storage migration for VMware resources
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13671725#comment-13671725 ] ASF subversion and git services commented on CLOUDSTACK-2701: - Commit 51996094ff2cb7d275507779bc8ed108dd8057e4 in branch refs/heads/master from Sateesh Chodapuneedi sate...@apache.org [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5199609 ] CLOUDSTACK-2701 - Enable storage migration for VMware resources Whitespace cleanup Signed-off-by: Sateesh Chodapuneedi sate...@apache.org CLOUDSTACK-2701 - Enable storage migration for VMware resources Removing injections which are not required in Vmware Manager Enable storage migration for VMware resources - Key: CLOUDSTACK-2701 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Storage vMotion allows VMs to be moved from one host to another, along with storage across datastores in datacenter. It provides the option to live migrate a VM’s disks along with the VM itself. It is now possible to migrate a VM from one datastore to another, or even to migrate a VM’s disks from one datastore to another with VM running on same host, all while the VM is running. This issue is to track the support of storage vMotion for VMware resources in cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done to branch vmware-storage-motion. Just now created this ticket to deal with specific areas in implementation that is well contained and limited to VMware resource only. Commits related to VmwareStorageMotionStrategy class and it's implementation along with commands MigrateWithStorageCommand and MigrateVolumeCommand are done under CLOUDSTACK-659 ticket. Release Planning: Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer (section VMware resource) Feature branch: vmware-storage-motion -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2701) Enable storage migration for VMware resources
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13671747#comment-13671747 ] Sateesh Chodapuneedi commented on CLOUDSTACK-2701: -- Merged feature branch vmware-storage-motion into Master. Enable storage migration for VMware resources - Key: CLOUDSTACK-2701 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Storage vMotion allows VMs to be moved from one host to another, along with storage across datastores in datacenter. It provides the option to live migrate a VM’s disks along with the VM itself. It is now possible to migrate a VM from one datastore to another, or even to migrate a VM’s disks from one datastore to another with VM running on same host, all while the VM is running. This issue is to track the support of storage vMotion for VMware resources in cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done to branch vmware-storage-motion. Just now created this ticket to deal with specific areas in implementation that is well contained and limited to VMware resource only. Commits related to VmwareStorageMotionStrategy class and it's implementation along with commands MigrateWithStorageCommand and MigrateVolumeCommand are done under CLOUDSTACK-659 ticket. Release Planning: Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer (section VMware resource) Feature branch: vmware-storage-motion -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2701) Enable storage migration for VMware resources
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670222#comment-13670222 ] ASF subversion and git services commented on CLOUDSTACK-2701: - Commit a96c9c5ae4138a4e22d0ee73b985ea4efbe77c9a in branch refs/heads/vmware-storage-motion from Sateesh Chodapuneedi sate...@apache.org [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a96c9c5 ] CLOUDSTACK-2701 - Enable storage migration for VMware resources Injecting component VolumeManager into VmwareResource. Enable storage migration for VMware resources - Key: CLOUDSTACK-2701 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Storage vMotion allows VMs to be moved from one host to another, along with storage across datastores in datacenter. It provides the option to live migrate a VM’s disks along with the VM itself. It is now possible to migrate a VM from one datastore to another, or even to migrate a VM’s disks from one datastore to another with VM running on same host, all while the VM is running. This issue is to track the support of storage vMotion for VMware resources in cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done to branch vmware-storage-motion. Just now created this ticket to deal with specific areas in implementation that is well contained and limited to VMware resource only. Commits related to VmwareStorageMotionStrategy class and it's implementation along with commands MigrateWithStorageCommand and MigrateVolumeCommand are done under CLOUDSTACK-659 ticket. Release Planning: Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer (section VMware resource) Feature branch: vmware-storage-motion -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2701) Enable storage migration for VMware resources
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670253#comment-13670253 ] ASF subversion and git services commented on CLOUDSTACK-2701: - Commit 406785b4aec457ea24dde13b23529fd8df9c1645 in branch refs/heads/vmware-storage-motion from Sateesh Chodapuneedi sate...@apache.org [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=406785b ] CLOUDSTACK-2701 - Enable storage migration for VMware resources Whitespace cleanup Signed-off-by: Sateesh Chodapuneedi sate...@apache.org Enable storage migration for VMware resources - Key: CLOUDSTACK-2701 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Storage vMotion allows VMs to be moved from one host to another, along with storage across datastores in datacenter. It provides the option to live migrate a VM’s disks along with the VM itself. It is now possible to migrate a VM from one datastore to another, or even to migrate a VM’s disks from one datastore to another with VM running on same host, all while the VM is running. This issue is to track the support of storage vMotion for VMware resources in cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done to branch vmware-storage-motion. Just now created this ticket to deal with specific areas in implementation that is well contained and limited to VMware resource only. Commits related to VmwareStorageMotionStrategy class and it's implementation along with commands MigrateWithStorageCommand and MigrateVolumeCommand are done under CLOUDSTACK-659 ticket. Release Planning: Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer (section VMware resource) Feature branch: vmware-storage-motion -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2701) Enable storage migration for VMware resources
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13669126#comment-13669126 ] ASF subversion and git services commented on CLOUDSTACK-2701: - Commit f3e3aaac1c43bdbcaf40e62b34a87cfff788de90 in branch refs/heads/vmware-storage-motion from Sateesh Chodapuneedi sate...@apache.org [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f3e3aaa ] CLOUDSTACK-2701 - Enable storage migration for VMware resources Sending command MigrateWithStorageCommand to source host instead of target host for the case of migration of VM within cluster. Enable storage migration for VMware resources - Key: CLOUDSTACK-2701 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Storage vMotion allows VMs to be moved from one host to another, along with storage across datastores in datacenter. It provides the option to live migrate a VM’s disks along with the VM itself. It is now possible to migrate a VM from one datastore to another, or even to migrate a VM’s disks from one datastore to another with VM running on same host, all while the VM is running. This issue is to track the support of storage vMotion for VMware resources in cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done to branch vmware-storage-motion. Just now created this ticket to deal with specific areas in implementation that is well contained and limited to VMware resource only. Commits related to VmwareStorageMotionStrategy class and it's implementation along with commands MigrateWithStorageCommand and MigrateVolumeCommand are done under CLOUDSTACK-659 ticket. Release Planning: Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer (section VMware resource) Feature branch: vmware-storage-motion -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2701) Enable storage migration for VMware resources
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13669127#comment-13669127 ] ASF subversion and git services commented on CLOUDSTACK-2701: - Commit eac87e8bfead2ee30b1fb7c348cb5276c0213d70 in branch refs/heads/vmware-storage-motion from Sateesh Chodapuneedi sate...@apache.org [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=eac87e8 ] CLOUDSTACK-2701 - Enable storage migration for VMware resources Fixing attach volume and delete volume cases for volumes that are moved off original path in datastore when created. If volume is not found in root directory or datastore, do search in sub folders. Enable storage migration for VMware resources - Key: CLOUDSTACK-2701 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Storage vMotion allows VMs to be moved from one host to another, along with storage across datastores in datacenter. It provides the option to live migrate a VM’s disks along with the VM itself. It is now possible to migrate a VM from one datastore to another, or even to migrate a VM’s disks from one datastore to another with VM running on same host, all while the VM is running. This issue is to track the support of storage vMotion for VMware resources in cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done to branch vmware-storage-motion. Just now created this ticket to deal with specific areas in implementation that is well contained and limited to VMware resource only. Commits related to VmwareStorageMotionStrategy class and it's implementation along with commands MigrateWithStorageCommand and MigrateVolumeCommand are done under CLOUDSTACK-659 ticket. Release Planning: Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer (section VMware resource) Feature branch: vmware-storage-motion -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2701) Enable storage migration for VMware resources
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13669125#comment-13669125 ] ASF subversion and git services commented on CLOUDSTACK-2701: - Commit 1b66e96d9c6476b6ee18f293a282612bf73645f0 in branch refs/heads/vmware-storage-motion from Sateesh Chodapuneedi sate...@apache.org [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1b66e96 ] CLOUDSTACK-2701 - Enable storage migration for VMware resources Searching for virtual disk during device tear down. Enable storage migration for VMware resources - Key: CLOUDSTACK-2701 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Storage vMotion allows VMs to be moved from one host to another, along with storage across datastores in datacenter. It provides the option to live migrate a VM’s disks along with the VM itself. It is now possible to migrate a VM from one datastore to another, or even to migrate a VM’s disks from one datastore to another with VM running on same host, all while the VM is running. This issue is to track the support of storage vMotion for VMware resources in cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done to branch vmware-storage-motion. Just now created this ticket to deal with specific areas in implementation that is well contained and limited to VMware resource only. Commits related to VmwareStorageMotionStrategy class and it's implementation along with commands MigrateWithStorageCommand and MigrateVolumeCommand are done under CLOUDSTACK-659 ticket. Release Planning: Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer (section VMware resource) Feature branch: vmware-storage-motion -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2701) Enable storage migration for VMware resources
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13669259#comment-13669259 ] ASF subversion and git services commented on CLOUDSTACK-2701: - Commit 83f731049f00741628697f266afeb1edc50995eb in branch refs/heads/vmware-storage-motion from Sateesh Chodapuneedi sate...@apache.org [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=83f7310 ] CLOUDSTACK-2701 - Enable storage migration for VMware resources Moved 2 methods that are not specific to VMware but Volume are moved to VolumeManager from VmwareManager. Moved datastore volume path constructing code to separate method. Added check for source and target host, if they are from different DCs/vCenter instances. Enable storage migration for VMware resources - Key: CLOUDSTACK-2701 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Storage vMotion allows VMs to be moved from one host to another, along with storage across datastores in datacenter. It provides the option to live migrate a VM’s disks along with the VM itself. It is now possible to migrate a VM from one datastore to another, or even to migrate a VM’s disks from one datastore to another with VM running on same host, all while the VM is running. This issue is to track the support of storage vMotion for VMware resources in cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done to branch vmware-storage-motion. Just now created this ticket to deal with specific areas in implementation that is well contained and limited to VMware resource only. Commits related to VmwareStorageMotionStrategy class and it's implementation along with commands MigrateWithStorageCommand and MigrateVolumeCommand are done under CLOUDSTACK-659 ticket. Release Planning: Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer (section VMware resource) Feature branch: vmware-storage-motion -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2701) Enable storage migration for VMware resources
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13667779#comment-13667779 ] ASF subversion and git services commented on CLOUDSTACK-2701: - Commit c6d7a751b51582560cd0483c7ebbdcd7b43b6b1e in branch refs/heads/vmware-storage-motion from Sateesh Chodapuneedi sate...@apache.org [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c6d7a75 ] CLOUDSTACK-2701 - Enable storage migration for VMware resources Fixing attach volume and delete volume cases for volumes that are moved off original path in datastore when created. If volume is not found in root directory or datastore, do search in sub folders. Enable storage migration for VMware resources - Key: CLOUDSTACK-2701 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Storage vMotion allows VMs to be moved from one host to another, along with storage across datastores in datacenter. It provides the option to live migrate a VM’s disks along with the VM itself. It is now possible to migrate a VM from one datastore to another, or even to migrate a VM’s disks from one datastore to another with VM running on same host, all while the VM is running. This issue is to track the support of storage vMotion for VMware resources in cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done to branch vmware-storage-motion. Just now created this ticket to deal with specific areas in implementation that is well contained and limited to VMware resource only. Commits related to VmwareStorageMotionStrategy class and it's implementation along with commands MigrateWithStorageCommand and MigrateVolumeCommand are done under CLOUDSTACK-659 ticket. Release Planning: Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer (section VMware resource) Feature branch: vmware-storage-motion -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2701) Enable storage migration for VMware resources
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13667873#comment-13667873 ] ASF subversion and git services commented on CLOUDSTACK-2701: - Commit 07d5271d041f288debbe8c9e391aa64d1c894b9b in branch refs/heads/vmware-storage-motion from Sateesh Chodapuneedi sate...@apache.org [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=07d5271 ] CLOUDSTACK-2701 - Enable storage migration for VMware resources Sending command MigrateWithStorageCommand to source host instead of target host for the case of migration of VM within cluster. Enable storage migration for VMware resources - Key: CLOUDSTACK-2701 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Storage vMotion allows VMs to be moved from one host to another, along with storage across datastores in datacenter. It provides the option to live migrate a VM’s disks along with the VM itself. It is now possible to migrate a VM from one datastore to another, or even to migrate a VM’s disks from one datastore to another with VM running on same host, all while the VM is running. This issue is to track the support of storage vMotion for VMware resources in cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done to branch vmware-storage-motion. Just now created this ticket to deal with specific areas in implementation that is well contained and limited to VMware resource only. Commits related to VmwareStorageMotionStrategy class and it's implementation along with commands MigrateWithStorageCommand and MigrateVolumeCommand are done under CLOUDSTACK-659 ticket. Release Planning: Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer (section VMware resource) Feature branch: vmware-storage-motion -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
