[jira] [Updated] (CLOUDSTACK-5028) Instance is failing to start after releasing the primary storage from maintenance mode
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-5028:
-
Fix Version/s: 4.2.1
Instance is failing to start after releasing the primary storage from
maintenance mode
---
Key: CLOUDSTACK-5028
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5028
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller, VMware
Affects Versions: 4.2.1
Reporter: Sailaja Mada
Priority: Critical
Fix For: 4.2.1
Steps:
1. Configure two Adv zones using VMWARE hypervisor
2. Configuration with Zone wide primary storages
3. Deploy VM using a user account
4. Move the Primary storage into maintenance
5. With this VM got into stopped state
6. Release the Storage into maintenance
7. Now start the VM.
Observation:
Instance is failing to start after releasing the primary storage from
maintenance mode
2013-11-03 19:14:30,652 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-330:null) Seq 9-894186938: Executing request
2013-11-03 19:14:30,665 INFO [vmware.resource.VmwareResource]
(DirectAgent-330:10.102.192.18) Executing resource StartCommand:
{vm:{id:24,name:i-5-24-VM,bootloader:HVM,type:User,cpus:1,minSpeed:200,maxSpeed:200,minRam:536870912,maxRam:536870912,hostName:sailajaVM1,arch:x86_64,os:CentOS
5.3
(64-bit),bootArgs:,rebootOnCrash:false,enableHA:true,limitCpuUse:false,enableDynamicallyScaleVm:false,vncPassword:e5e3f536d1a3d5cc,params:{nicAdapter:E1000,vmware.reserve.cpu:false,nestedVirtualizationFlag:false,Message.ReservedCapacityFreed.Flag:false,rootDiskController:ide,vmware.reserve.mem:false},uuid:1ec83c40-e0dc-48ad-90d8-f4000c0dfe91,disks:[{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:1ffa6e41-00cc-47d5-958c-f8305ac06af4,volumeType:DATADISK,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:b33e996a-444e-3685-9070-0865067454c4,id:6,poolType:NetworkFilesystem,host:10.102.192.100,path:/cpg_vol/sailaja/sailajaps2,port:2049}},name:DATA-24,size:5368709120,path:a933eb3fa28a473ab5e28b99f5f2607e,volumeId:37,vmName:i-5-24-VM,accountId:5,chainInfo:{\diskDeviceBusName\:\scsi0:0\,\diskChain\:[\[7f18caf5397a340a934ed37c558aee2b]
i-5-24-VM/8d463fcfe15c43dea0cef4474864552e-04.vmdk\,\[7f18caf5397a340a934ed37c558aee2b]
i-5-24-VM/8d463fcfe15c43dea0cef4474864552e-03.vmdk\,\[7f18caf5397a340a934ed37c5,format:OVA,id:37,hypervisorType:VMware}},diskSeq:1,type:DATADISK},{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:91d3fff2-cc90-4122-b076-06588fa33401,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:7f18caf5-397a-340a-934e-d37c558aee2b,id:5,poolType:NetworkFilesystem,host:10.102.192.100,path:/cpg_vol/sailaja/sailajaps1,port:2049}},name:ROOT-24,size:2147483648,path:ROOT-24,volumeId:38,vmName:i-5-24-VM,accountId:5,format:OVA,id:38,hypervisorType:VMware}},diskSeq:0,type:ROOT},{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{uuid:257add99-2031-4ad8-b633-979f3812b1cd,id:200,format:ISO,accountId:1,hvm:true,displayText:VMware
Tools Installer ISO,name:vmware-tools.iso,guestOsType:CentOS 4.5
(32-bit),hypervisorType:VMware}},diskSeq:3,type:ISO}],nics:[{deviceId:0,networkRateMbps:200,defaultNic:true,uuid:f3987dbb-7e7e-4a50-8dc1-761b6bdd2f41,ip:10.1.1.79,netmask:255.255.255.0,gateway:10.1.1.1,mac:02:00:3a:5d:00:01,dns1:10.103.128.15,broadcastType:Vlan,type:Guest,broadcastUri:vlan://777,isolationUri:vlan://777,isSecurityGroupEnabled:false}]},hostIp:10.102.192.18,executeInSequence:true,wait:0}
2013-11-03 19:14:30,747 DEBUG [vmware.mo.HostMO]
(DirectAgent-330:10.102.192.18) find VM i-5-24-VM on host
2013-11-03 19:14:30,747 INFO [vmware.mo.HostMO]
(DirectAgent-330:10.102.192.18) VM i-5-24-VM not found in host cache
2013-11-03 19:14:30,747 DEBUG [vmware.mo.HostMO]
(DirectAgent-330:10.102.192.18) load VM cache on host
2013-11-03 19:14:30,769 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===START=== 10.104.255.45 -- GET
command=queryAsyncJobResultjobId=fc31a268-ae48-49c7-8908-35c52ee1b922response=jsonsessionkey=ktQfh1aD0%2Ffcgyias7vCxMP6WIs%3D_=1383486601934
2013-11-03 19:14:30,774 INFO [vmware.resource.VmwareResource]
(DirectAgent-330:10.102.192.18) VM i-5-24-VM already exists, tear down
devices for reconfiguration
2013-11-03 19:14:30,806 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===END=== 10.104.255.45 -- GET
command=queryAsyncJobResultjobId=fc31a268-ae48-49c7-8908-35c52ee1b922response=jsonsessionkey=ktQfh1aD0%2Ffcgyias7vCxMP6WIs%3D_=1383486601934
2013-11-03 19:14:31,194 DEBUG [vmware.resource.VmwareResource]
[jira] [Updated] (CLOUDSTACK-5028) Instance is failing to start after releasing the primary storage from maintenance mode
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-5028:
-
Attachment: startvmlogs.rar
Instance is failing to start after releasing the primary storage from
maintenance mode
---
Key: CLOUDSTACK-5028
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5028
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller, VMware
Affects Versions: 4.2.1
Reporter: Sailaja Mada
Priority: Critical
Fix For: 4.2.1
Attachments: startvmlogs.rar
Steps:
1. Configure two Adv zones using VMWARE hypervisor
2. Configuration with Zone wide primary storages
3. Deploy VM using a user account
4. Move the Primary storage into maintenance
5. With this VM got into stopped state
6. Release the Storage into maintenance
7. Now start the VM.
Observation:
Instance is failing to start after releasing the primary storage from
maintenance mode
2013-11-03 19:14:30,652 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-330:null) Seq 9-894186938: Executing request
2013-11-03 19:14:30,665 INFO [vmware.resource.VmwareResource]
(DirectAgent-330:10.102.192.18) Executing resource StartCommand:
{vm:{id:24,name:i-5-24-VM,bootloader:HVM,type:User,cpus:1,minSpeed:200,maxSpeed:200,minRam:536870912,maxRam:536870912,hostName:sailajaVM1,arch:x86_64,os:CentOS
5.3
(64-bit),bootArgs:,rebootOnCrash:false,enableHA:true,limitCpuUse:false,enableDynamicallyScaleVm:false,vncPassword:e5e3f536d1a3d5cc,params:{nicAdapter:E1000,vmware.reserve.cpu:false,nestedVirtualizationFlag:false,Message.ReservedCapacityFreed.Flag:false,rootDiskController:ide,vmware.reserve.mem:false},uuid:1ec83c40-e0dc-48ad-90d8-f4000c0dfe91,disks:[{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:1ffa6e41-00cc-47d5-958c-f8305ac06af4,volumeType:DATADISK,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:b33e996a-444e-3685-9070-0865067454c4,id:6,poolType:NetworkFilesystem,host:10.102.192.100,path:/cpg_vol/sailaja/sailajaps2,port:2049}},name:DATA-24,size:5368709120,path:a933eb3fa28a473ab5e28b99f5f2607e,volumeId:37,vmName:i-5-24-VM,accountId:5,chainInfo:{\diskDeviceBusName\:\scsi0:0\,\diskChain\:[\[7f18caf5397a340a934ed37c558aee2b]
i-5-24-VM/8d463fcfe15c43dea0cef4474864552e-04.vmdk\,\[7f18caf5397a340a934ed37c558aee2b]
i-5-24-VM/8d463fcfe15c43dea0cef4474864552e-03.vmdk\,\[7f18caf5397a340a934ed37c5,format:OVA,id:37,hypervisorType:VMware}},diskSeq:1,type:DATADISK},{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:91d3fff2-cc90-4122-b076-06588fa33401,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:7f18caf5-397a-340a-934e-d37c558aee2b,id:5,poolType:NetworkFilesystem,host:10.102.192.100,path:/cpg_vol/sailaja/sailajaps1,port:2049}},name:ROOT-24,size:2147483648,path:ROOT-24,volumeId:38,vmName:i-5-24-VM,accountId:5,format:OVA,id:38,hypervisorType:VMware}},diskSeq:0,type:ROOT},{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{uuid:257add99-2031-4ad8-b633-979f3812b1cd,id:200,format:ISO,accountId:1,hvm:true,displayText:VMware
Tools Installer ISO,name:vmware-tools.iso,guestOsType:CentOS 4.5
(32-bit),hypervisorType:VMware}},diskSeq:3,type:ISO}],nics:[{deviceId:0,networkRateMbps:200,defaultNic:true,uuid:f3987dbb-7e7e-4a50-8dc1-761b6bdd2f41,ip:10.1.1.79,netmask:255.255.255.0,gateway:10.1.1.1,mac:02:00:3a:5d:00:01,dns1:10.103.128.15,broadcastType:Vlan,type:Guest,broadcastUri:vlan://777,isolationUri:vlan://777,isSecurityGroupEnabled:false}]},hostIp:10.102.192.18,executeInSequence:true,wait:0}
2013-11-03 19:14:30,747 DEBUG [vmware.mo.HostMO]
(DirectAgent-330:10.102.192.18) find VM i-5-24-VM on host
2013-11-03 19:14:30,747 INFO [vmware.mo.HostMO]
(DirectAgent-330:10.102.192.18) VM i-5-24-VM not found in host cache
2013-11-03 19:14:30,747 DEBUG [vmware.mo.HostMO]
(DirectAgent-330:10.102.192.18) load VM cache on host
2013-11-03 19:14:30,769 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===START=== 10.104.255.45 -- GET
command=queryAsyncJobResultjobId=fc31a268-ae48-49c7-8908-35c52ee1b922response=jsonsessionkey=ktQfh1aD0%2Ffcgyias7vCxMP6WIs%3D_=1383486601934
2013-11-03 19:14:30,774 INFO [vmware.resource.VmwareResource]
(DirectAgent-330:10.102.192.18) VM i-5-24-VM already exists, tear down
devices for reconfiguration
2013-11-03 19:14:30,806 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===END=== 10.104.255.45 -- GET
command=queryAsyncJobResultjobId=fc31a268-ae48-49c7-8908-35c52ee1b922response=jsonsessionkey=ktQfh1aD0%2Ffcgyias7vCxMP6WIs%3D_=1383486601934
2013-11-03 19:14:31,194 DEBUG
[jira] [Commented] (CLOUDSTACK-5023) Deleting Port Forwarding Rule fails when generating usage events are enabled
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13812462#comment-13812462
]
ASF subversion and git services commented on CLOUDSTACK-5023:
-
Commit d6420cd91ebb493e8b9d4220e95b7a3250272db3 in branch refs/heads/4.2 from
[~dgrizzanti]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d6420cd ]
CLOUDSTACK-5023: Deleting Port Forwarding Rule fails when generating usage
events are enabled
Deleting Port Forwarding Rule fails when generating usage events are enabled
Key: CLOUDSTACK-5023
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5023
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.2.0
Reporter: David Grizzanti
Assignee: David Grizzanti
When generating usage events are enabled (using RabbitMQEventBus bean
configuration), deleting a port forwarding rule fails to delete the rule.
What you see as a response from the API call is:
{ queryasyncjobresultresponse :
{accountid:3f91b297-26e4-11e3-96f6-9e300504069a,userid:3f91e743-26e4-11e3-96f6-9e300504069a,cmd:org.apache.cloudstack.api.command.user.firewall.DeletePortForwardingRuleCmd,jobstatus:2,jobprocstatus:0,jobresultcode:530,jobresulttype:object,jobresult:{errorcode:530,errortext:Command
failed due to Internal Server
Error},created:2013-11-01T11:31:02-0400,jobid:a82a2ecb-2bcd-4f86-9d40-c4c9f0d85f6f}
}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CLOUDSTACK-5023) Deleting Port Forwarding Rule fails when generating usage events are enabled
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daan Hoogland updated CLOUDSTACK-5023:
--
Fix Version/s: Future
4.1.1
Deleting Port Forwarding Rule fails when generating usage events are enabled
Key: CLOUDSTACK-5023
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5023
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.2.0
Reporter: David Grizzanti
Assignee: David Grizzanti
Fix For: 4.1.1, Future
When generating usage events are enabled (using RabbitMQEventBus bean
configuration), deleting a port forwarding rule fails to delete the rule.
What you see as a response from the API call is:
{ queryasyncjobresultresponse :
{accountid:3f91b297-26e4-11e3-96f6-9e300504069a,userid:3f91e743-26e4-11e3-96f6-9e300504069a,cmd:org.apache.cloudstack.api.command.user.firewall.DeletePortForwardingRuleCmd,jobstatus:2,jobprocstatus:0,jobresultcode:530,jobresulttype:object,jobresult:{errorcode:530,errortext:Command
failed due to Internal Server
Error},created:2013-11-01T11:31:02-0400,jobid:a82a2ecb-2bcd-4f86-9d40-c4c9f0d85f6f}
}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (CLOUDSTACK-5029) cloud-bugtool isn't in release package like release notes say
gavin lee created CLOUDSTACK-5029: - Summary: cloud-bugtool isn't in release package like release notes say Key: CLOUDSTACK-5029 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5029 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0 Environment: CentOS 6.3 x64 CloudStack 4.2.0 Reporter: gavin lee Fix For: 4.3.0 Unlike the CS4.2 release notes say, I could not find cloud-bugtool in source tree or installed/upgrade CS4.2 platform. Further research shows it is in Citrix CloudPlatform 4.2. Since CS4.2 now was released, and CS4.2.1 won't add any new features. I guess it would be included in CS4.3. Currently the only change is remove the related info in CS4.2 release notes. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-2692) [MIPN][Enhancement] Add load balancing support for MIPN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy updated CLOUDSTACK-2692: -- Fix Version/s: (was: 4.3.0) Future [MIPN][Enhancement] Add load balancing support for MIPN --- Key: CLOUDSTACK-2692 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2692 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.1.0, 4.2.0 Reporter: Jayapal Reddy Assignee: Jayapal Reddy Fix For: Future Add support of Load balancing for MIPN feature -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4864) Create VMWare 64 bit system VM template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13812613#comment-13812613 ] Radhika Nair commented on CLOUDSTACK-4864: -- What is the documentation impact of this defect ? Is that a new template is available ? Create VMWare 64 bit system VM template --- Key: CLOUDSTACK-4864 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4864 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.2.0 Reporter: Abhinandan Prateek Assignee: Sateesh Chodapuneedi Priority: Blocker Fix For: 4.2.1 Attachments: systemvmtemplate64.ovf VMWare 64 bit template requires some custom work. Default template that is generated by jenkins has wrong cdrom setup and vmware tools, that needs to be fixed manually. Harddisk type is also incompatible. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-2031) [mipn] support for number of ips per nic limit needs to be added for the multiple ip address per nic
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy updated CLOUDSTACK-2031: -- Fix Version/s: (was: 4.3.0) Future [mipn] support for number of ips per nic limit needs to be added for the multiple ip address per nic - Key: CLOUDSTACK-2031 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2031 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Jayapal Reddy Assignee: Jayapal Reddy Priority: Minor Fix For: Future -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Closed] (CLOUDSTACK-4717) associate IP does not work on shared networks with out source NAT service
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-4717. This is fixed now. Hence closing the bug. associate IP does not work on shared networks with out source NAT service - Key: CLOUDSTACK-4717 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4717 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.0 Reporter: Murali Reddy Assignee: Murali Reddy Priority: Critical Fix For: 4.2.1 'shared network' with only DNS, DHCP and LB service provided by CloudStack is a valid service combination. in this case gateway is defined externally and cloudstack does not provide any nat service. But currently there is restriction that in order to acquire an IP to a network source nat service should have been enabled on the network. So effectively IP can not be acquired and no LB rules can be created. Currenrly acquiring IP on to a network with no source NAT service will throw error: In zone of type Advanced ip address can be associated only to the network of guest type Isolated with the SourceNat enabled Fix should be relax the restriction the source nat ip to enabled on the network on which ip is being acquired. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-5030) [Doc] Document the Procedure to create custom role in vCenter for CloudPlatform
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5030: - Fix Version/s: 4.2.1 [Doc] Document the Procedure to create custom role in vCenter for CloudPlatform --- Key: CLOUDSTACK-5030 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5030 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Sailaja Mada Fix For: 4.2.1 Steps: Procedure to create custom role in vCenter for CloudPlatform is described below: Requirement Elaborate minimal permissions required for a user account to be used by CloudPlatform. Back ground To manage VMware deployments, CloudPlatform need permissions for the role to manage infrastructure resources as the minimal i.e, Manage cluster/host Manage datastore/disks/files Manage port groups Manage dvPort groups Manage templates Import appliance Export a template Manage VM Manage snapshot of VM Manage custom field Solution Hence the idea is to create a role with above required minimal permissions and assign this custom role to the user designated to be used by CloudPlatform. For more robust implementation of this, the permissions could be divided into 2 roles where as each role (mapped with a user) is added to relevant object in vCenter infrastructure. Global role This is for custom attribute management - User with this role would be added to vCenter object WITHOUT propagation to child objects. Datacenter role This is for datacenter management - User with this role would be added to each of Datacenter object, WITH propagation to child objects, to be managed by this user. Detailed list of granualar permissions to be added to the global role to be used for CloudPlatform is below. Global.Manage custom attributes Global.set custom attributes Detailed list of granualar permissions to be added to the datacentre role to be used for CloudPlatform is below. Datastore.AllocateSpace Datastore.Browse Datastore.Configure Datastore.Remove file Datastore.FileManagement (Low level file operations and Update virtual machine files) dvPort group.Create dvPort group.Modify dvPort group.Policy dvPort group.Delete Folder.Create folder Folder.Delete folder Network.Assign Network.Configure Network.Remove Resource.HotMigrate (Migrate powered on vm) Resource.ColdMigrate (Migrate powered off vm) Resource.Assign virtualmachine to resource pool Resource.Assign vApp to resource pool Sessions.Validatesession Host.Configuration.Connection Host.Configuration.Security profile and firewall Host.Configuration.Maintenance Host.Configuration.Storage partition configuration Host.Configuration.SystemManagement Host.LocalOperations.Create Virtual Machine Host.LocalOperations.Delete Virtual Machine Host.LocalOperations.Reconfigure Virtual Machine Host.LocalOperations.Relayout Snapshots vApp.Export vApp.Import VirtualMachine.Config.AddExistingDisk VirtualMachine.Config.AddNewDisk VirtualMachine.Config.AdvancedConfig Virtualmachine.Configuration.Add or remove device Virtualmachine.Configuration.Change CPU Count Virtualmachine.Configuration.Change Resource Virtualmachine.Configuration.Extend Disk Virtualmachine.Configuration.Memory Virtualmachine.Configuration.Modify Device Setting Virtualmachine.Configuration.Reload from path Virtualmachine.Configuration.Rename Virtualmachine.Configuration.Remove disk Virtualmachine.Configuration.Set annotation Virtualmachine.Configuration.Settings Virtualmachine.Interaction.Answer question Virtualmachine.Interaction.Power Off Virtualmachine.Interaction.Power On VirtualMachine.Interaction.Reset Virtualmachine.Interaction.VMware Tools install VirtualMachine.Inventory.Create (New and from existing) VirtualMachine.Inventory.Register VirtualMachine.Inventory.Unregister VirtualMachine.Inventory.Remove VirtualMachine.Inventory.Move Virtualmachine.Provisioning.Allow file access Virtualmachine.Provisioning.Allow file upload Virtualmachine.Provisioning.Allow file download Virtualmachine.Provisioning.Mark as template Virtualmachine.Provisioning.Clone template Virtualmachine.Provisioning.Clone virtualmachine Virtualmachine.Provisioning.Deploy template Virtualmachine.Provisioning.Create template from virtual machine
[jira] [Created] (CLOUDSTACK-5030) [Doc] Document the Procedure to create custom role in vCenter for CloudPlatform
Sailaja Mada created CLOUDSTACK-5030: Summary: [Doc] Document the Procedure to create custom role in vCenter for CloudPlatform Key: CLOUDSTACK-5030 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5030 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Sailaja Mada Steps: Procedure to create custom role in vCenter for CloudPlatform is described below: Requirement Elaborate minimal permissions required for a user account to be used by CloudPlatform. Back ground To manage VMware deployments, CloudPlatform need permissions for the role to manage infrastructure resources as the minimal i.e, Manage cluster/host Manage datastore/disks/files Manage port groups Manage dvPort groups Manage templates Import appliance Export a template Manage VM Manage snapshot of VM Manage custom field Solution Hence the idea is to create a role with above required minimal permissions and assign this custom role to the user designated to be used by CloudPlatform. For more robust implementation of this, the permissions could be divided into 2 roles where as each role (mapped with a user) is added to relevant object in vCenter infrastructure. Global role This is for custom attribute management - User with this role would be added to vCenter object WITHOUT propagation to child objects. Datacenter role This is for datacenter management - User with this role would be added to each of Datacenter object, WITH propagation to child objects, to be managed by this user. Detailed list of granualar permissions to be added to the global role to be used for CloudPlatform is below. Global.Manage custom attributes Global.set custom attributes Detailed list of granualar permissions to be added to the datacentre role to be used for CloudPlatform is below. Datastore.AllocateSpace Datastore.Browse Datastore.Configure Datastore.Remove file Datastore.FileManagement (Low level file operations and Update virtual machine files) dvPort group.Create dvPort group.Modify dvPort group.Policy dvPort group.Delete Folder.Create folder Folder.Delete folder Network.Assign Network.Configure Network.Remove Resource.HotMigrate (Migrate powered on vm) Resource.ColdMigrate (Migrate powered off vm) Resource.Assign virtualmachine to resource pool Resource.Assign vApp to resource pool Sessions.Validatesession Host.Configuration.Connection Host.Configuration.Security profile and firewall Host.Configuration.Maintenance Host.Configuration.Storage partition configuration Host.Configuration.SystemManagement Host.LocalOperations.Create Virtual Machine Host.LocalOperations.Delete Virtual Machine Host.LocalOperations.Reconfigure Virtual Machine Host.LocalOperations.Relayout Snapshots vApp.Export vApp.Import VirtualMachine.Config.AddExistingDisk VirtualMachine.Config.AddNewDisk VirtualMachine.Config.AdvancedConfig Virtualmachine.Configuration.Add or remove device Virtualmachine.Configuration.Change CPU Count Virtualmachine.Configuration.Change Resource Virtualmachine.Configuration.Extend Disk Virtualmachine.Configuration.Memory Virtualmachine.Configuration.Modify Device Setting Virtualmachine.Configuration.Reload from path Virtualmachine.Configuration.Rename Virtualmachine.Configuration.Remove disk Virtualmachine.Configuration.Set annotation Virtualmachine.Configuration.Settings Virtualmachine.Interaction.Answer question Virtualmachine.Interaction.Power Off Virtualmachine.Interaction.Power On VirtualMachine.Interaction.Reset Virtualmachine.Interaction.VMware Tools install VirtualMachine.Inventory.Create (New and from existing) VirtualMachine.Inventory.Register VirtualMachine.Inventory.Unregister VirtualMachine.Inventory.Remove VirtualMachine.Inventory.Move Virtualmachine.Provisioning.Allow file access Virtualmachine.Provisioning.Allow file upload Virtualmachine.Provisioning.Allow file download Virtualmachine.Provisioning.Mark as template Virtualmachine.Provisioning.Clone template Virtualmachine.Provisioning.Clone virtualmachine Virtualmachine.Provisioning.Deploy template Virtualmachine.Provisioning.Create template from virtual machine Virtualmachine.Provisioning.Mark as template Virtualmachine.State.Create snapshot Virtualmachine.State.Remove Snapshot Virtualmachine.State.Revert to snapshot vSphereDistributedSwitch.Policy operation vSphereDistributedSwitch.Port configuration operation vSphereDistributedSwitch.Port setting
[jira] [Updated] (CLOUDSTACK-5030) [Doc] Document the Procedure to create custom role in vCenter for CloudPlatform
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-5030: - Labels: doc (was: ) [Doc] Document the Procedure to create custom role in vCenter for CloudPlatform --- Key: CLOUDSTACK-5030 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5030 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.1 Reporter: Sailaja Mada Labels: doc Fix For: 4.2.1 Steps: Procedure to create custom role in vCenter for CloudPlatform is described below: Requirement Elaborate minimal permissions required for a user account to be used by CloudPlatform. Back ground To manage VMware deployments, CloudPlatform need permissions for the role to manage infrastructure resources as the minimal i.e, Manage cluster/host Manage datastore/disks/files Manage port groups Manage dvPort groups Manage templates Import appliance Export a template Manage VM Manage snapshot of VM Manage custom field Solution Hence the idea is to create a role with above required minimal permissions and assign this custom role to the user designated to be used by CloudPlatform. For more robust implementation of this, the permissions could be divided into 2 roles where as each role (mapped with a user) is added to relevant object in vCenter infrastructure. Global role This is for custom attribute management - User with this role would be added to vCenter object WITHOUT propagation to child objects. Datacenter role This is for datacenter management - User with this role would be added to each of Datacenter object, WITH propagation to child objects, to be managed by this user. Detailed list of granualar permissions to be added to the global role to be used for CloudPlatform is below. Global.Manage custom attributes Global.set custom attributes Detailed list of granualar permissions to be added to the datacentre role to be used for CloudPlatform is below. Datastore.AllocateSpace Datastore.Browse Datastore.Configure Datastore.Remove file Datastore.FileManagement (Low level file operations and Update virtual machine files) dvPort group.Create dvPort group.Modify dvPort group.Policy dvPort group.Delete Folder.Create folder Folder.Delete folder Network.Assign Network.Configure Network.Remove Resource.HotMigrate (Migrate powered on vm) Resource.ColdMigrate (Migrate powered off vm) Resource.Assign virtualmachine to resource pool Resource.Assign vApp to resource pool Sessions.Validatesession Host.Configuration.Connection Host.Configuration.Security profile and firewall Host.Configuration.Maintenance Host.Configuration.Storage partition configuration Host.Configuration.SystemManagement Host.LocalOperations.Create Virtual Machine Host.LocalOperations.Delete Virtual Machine Host.LocalOperations.Reconfigure Virtual Machine Host.LocalOperations.Relayout Snapshots vApp.Export vApp.Import VirtualMachine.Config.AddExistingDisk VirtualMachine.Config.AddNewDisk VirtualMachine.Config.AdvancedConfig Virtualmachine.Configuration.Add or remove device Virtualmachine.Configuration.Change CPU Count Virtualmachine.Configuration.Change Resource Virtualmachine.Configuration.Extend Disk Virtualmachine.Configuration.Memory Virtualmachine.Configuration.Modify Device Setting Virtualmachine.Configuration.Reload from path Virtualmachine.Configuration.Rename Virtualmachine.Configuration.Remove disk Virtualmachine.Configuration.Set annotation Virtualmachine.Configuration.Settings Virtualmachine.Interaction.Answer question Virtualmachine.Interaction.Power Off Virtualmachine.Interaction.Power On VirtualMachine.Interaction.Reset Virtualmachine.Interaction.VMware Tools install VirtualMachine.Inventory.Create (New and from existing) VirtualMachine.Inventory.Register VirtualMachine.Inventory.Unregister VirtualMachine.Inventory.Remove VirtualMachine.Inventory.Move Virtualmachine.Provisioning.Allow file access Virtualmachine.Provisioning.Allow file upload Virtualmachine.Provisioning.Allow file download Virtualmachine.Provisioning.Mark as template Virtualmachine.Provisioning.Clone template Virtualmachine.Provisioning.Clone virtualmachine Virtualmachine.Provisioning.Deploy template Virtualmachine.Provisioning.Create template from
[jira] [Commented] (CLOUDSTACK-5029) cloud-bugtool isn't in release package like release notes say
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13812655#comment-13812655 ] Chip Childers commented on CLOUDSTACK-5029: --- This should be removed from the documentation, since the tool was not accepted by the project [1]. -chip [1] http://markmail.org/message/kregi5hsapvxdxdg cloud-bugtool isn't in release package like release notes say - Key: CLOUDSTACK-5029 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5029 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0 Environment: CentOS 6.3 x64 CloudStack 4.2.0 Reporter: gavin lee Fix For: 4.3.0 Unlike the CS4.2 release notes say, I could not find cloud-bugtool in source tree or installed/upgrade CS4.2 platform. Further research shows it is in Citrix CloudPlatform 4.2. Since CS4.2 now was released, and CS4.2.1 won't add any new features. I guess it would be included in CS4.3. Currently the only change is remove the related info in CS4.2 release notes. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CLOUDSTACK-5029) cloud-bugtool isn't in release package like release notes say
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen reassigned CLOUDSTACK-5029: -- Assignee: sebastien goasguen Removed mention of cloud-bugtool in docs as the tool as was not accepted in the code base. cloud-bugtool isn't in release package like release notes say - Key: CLOUDSTACK-5029 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5029 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0 Environment: CentOS 6.3 x64 CloudStack 4.2.0 Reporter: gavin lee Assignee: sebastien goasguen Fix For: 4.3.0 Unlike the CS4.2 release notes say, I could not find cloud-bugtool in source tree or installed/upgrade CS4.2 platform. Further research shows it is in Citrix CloudPlatform 4.2. Since CS4.2 now was released, and CS4.2.1 won't add any new features. I guess it would be included in CS4.3. Currently the only change is remove the related info in CS4.2 release notes. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CLOUDSTACK-5028) Instance is failing to start after releasing the primary storage from maintenance mode
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Likitha Shetty reassigned CLOUDSTACK-5028:
--
Assignee: Likitha Shetty
Instance is failing to start after releasing the primary storage from
maintenance mode
---
Key: CLOUDSTACK-5028
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5028
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller, VMware
Affects Versions: 4.2.1
Reporter: Sailaja Mada
Assignee: Likitha Shetty
Priority: Critical
Fix For: 4.2.1
Attachments: startvmlogs.rar
Steps:
1. Configure two Adv zones using VMWARE hypervisor
2. Configuration with Zone wide primary storages
3. Deploy VM using a user account
4. Move the Primary storage into maintenance
5. With this VM got into stopped state
6. Release the Storage into maintenance
7. Now start the VM.
Observation:
Instance is failing to start after releasing the primary storage from
maintenance mode
2013-11-03 19:14:30,652 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-330:null) Seq 9-894186938: Executing request
2013-11-03 19:14:30,665 INFO [vmware.resource.VmwareResource]
(DirectAgent-330:10.102.192.18) Executing resource StartCommand:
{vm:{id:24,name:i-5-24-VM,bootloader:HVM,type:User,cpus:1,minSpeed:200,maxSpeed:200,minRam:536870912,maxRam:536870912,hostName:sailajaVM1,arch:x86_64,os:CentOS
5.3
(64-bit),bootArgs:,rebootOnCrash:false,enableHA:true,limitCpuUse:false,enableDynamicallyScaleVm:false,vncPassword:e5e3f536d1a3d5cc,params:{nicAdapter:E1000,vmware.reserve.cpu:false,nestedVirtualizationFlag:false,Message.ReservedCapacityFreed.Flag:false,rootDiskController:ide,vmware.reserve.mem:false},uuid:1ec83c40-e0dc-48ad-90d8-f4000c0dfe91,disks:[{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:1ffa6e41-00cc-47d5-958c-f8305ac06af4,volumeType:DATADISK,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:b33e996a-444e-3685-9070-0865067454c4,id:6,poolType:NetworkFilesystem,host:10.102.192.100,path:/cpg_vol/sailaja/sailajaps2,port:2049}},name:DATA-24,size:5368709120,path:a933eb3fa28a473ab5e28b99f5f2607e,volumeId:37,vmName:i-5-24-VM,accountId:5,chainInfo:{\diskDeviceBusName\:\scsi0:0\,\diskChain\:[\[7f18caf5397a340a934ed37c558aee2b]
i-5-24-VM/8d463fcfe15c43dea0cef4474864552e-04.vmdk\,\[7f18caf5397a340a934ed37c558aee2b]
i-5-24-VM/8d463fcfe15c43dea0cef4474864552e-03.vmdk\,\[7f18caf5397a340a934ed37c5,format:OVA,id:37,hypervisorType:VMware}},diskSeq:1,type:DATADISK},{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:91d3fff2-cc90-4122-b076-06588fa33401,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:7f18caf5-397a-340a-934e-d37c558aee2b,id:5,poolType:NetworkFilesystem,host:10.102.192.100,path:/cpg_vol/sailaja/sailajaps1,port:2049}},name:ROOT-24,size:2147483648,path:ROOT-24,volumeId:38,vmName:i-5-24-VM,accountId:5,format:OVA,id:38,hypervisorType:VMware}},diskSeq:0,type:ROOT},{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{uuid:257add99-2031-4ad8-b633-979f3812b1cd,id:200,format:ISO,accountId:1,hvm:true,displayText:VMware
Tools Installer ISO,name:vmware-tools.iso,guestOsType:CentOS 4.5
(32-bit),hypervisorType:VMware}},diskSeq:3,type:ISO}],nics:[{deviceId:0,networkRateMbps:200,defaultNic:true,uuid:f3987dbb-7e7e-4a50-8dc1-761b6bdd2f41,ip:10.1.1.79,netmask:255.255.255.0,gateway:10.1.1.1,mac:02:00:3a:5d:00:01,dns1:10.103.128.15,broadcastType:Vlan,type:Guest,broadcastUri:vlan://777,isolationUri:vlan://777,isSecurityGroupEnabled:false}]},hostIp:10.102.192.18,executeInSequence:true,wait:0}
2013-11-03 19:14:30,747 DEBUG [vmware.mo.HostMO]
(DirectAgent-330:10.102.192.18) find VM i-5-24-VM on host
2013-11-03 19:14:30,747 INFO [vmware.mo.HostMO]
(DirectAgent-330:10.102.192.18) VM i-5-24-VM not found in host cache
2013-11-03 19:14:30,747 DEBUG [vmware.mo.HostMO]
(DirectAgent-330:10.102.192.18) load VM cache on host
2013-11-03 19:14:30,769 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===START=== 10.104.255.45 -- GET
command=queryAsyncJobResultjobId=fc31a268-ae48-49c7-8908-35c52ee1b922response=jsonsessionkey=ktQfh1aD0%2Ffcgyias7vCxMP6WIs%3D_=1383486601934
2013-11-03 19:14:30,774 INFO [vmware.resource.VmwareResource]
(DirectAgent-330:10.102.192.18) VM i-5-24-VM already exists, tear down
devices for reconfiguration
2013-11-03 19:14:30,806 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===END=== 10.104.255.45 -- GET
command=queryAsyncJobResultjobId=fc31a268-ae48-49c7-8908-35c52ee1b922response=jsonsessionkey=ktQfh1aD0%2Ffcgyias7vCxMP6WIs%3D_=1383486601934
