[jira] [Commented] (CLOUDSTACK-9142) Migrate VM changes xmlDesc in an unsafe way

2016-01-21 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110351#comment-15110351
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9142:


Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1348#issuecomment-173519263
  
@remibergsma I reproduced the error. I had not copied the newlines from the 
problematic system into my unit test. will push a fix without hurry.


> Migrate VM changes xmlDesc in an unsafe way
> ---
>
> Key: CLOUDSTACK-9142
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9142
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server
>Affects Versions: 4.6.0, 4.7.0
>Reporter: David Amorim Faria
>Assignee: Daan Hoogland
>Priority: Critical
>
> This issue appears with commit 
> https://github.com/apache/cloudstack/commit/a709f34ff93579981afbd4df0f4334b61ada29a8
> where xmlDesc has some content replaced: {code}
> xmlDesc = 
> dm.getXMLDesc(xmlFlag).replace(libvirtComputingResource.getPrivateIp(), 
> command.getDestinationIp());
> {code}
> This line from LibvirtComputingResource.java was refactored into 
> LibvirtMigrateCommandWrapper.java in commit 
> https://github.com/apache/cloudstack/commit/28e55462f15bdd8699e97b668c4ffc01735a533d
> Example, node1 is 10.0.0.1, node2 is 10.0.0.2, rbd mon_host is 10.0.0.13.
> VM is running on kvm node1 and this happened when migrating a VM from node1 
> to node2, where the kvm nodes and the RBD mon nodes (mon_host) use IP 
> addresses in the same range, and the mon_host has an ip address that 
> partially matches the ip address (string) of the first kvm node.
> In the process list one can see that the mon_host changes from 10.0.0.13 to 
> 10.0.0.23 in the destination host, blocking the migration after a timeout due 
> to primary storage not being available.
> {code}
> root 25206  1.8  0.0 440184 17188 ?Sl   13:33   0:00 
> /usr/libexec/qemu-kvm -name r-74-VM -S -machine 
> pc-i440fx-rhel7.0.0,accel=kvm,usb=off -cpu 
> host,+rdtscp,+pdpe1gb,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pclmuldq,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme
>  -m 256 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 
> 1a32b655-0acf-424b-8722-9e7f507a3070 -smbios type=1,manufacturer=Apache 
> Software Foundation,product=CloudStack KVM 
> Hypervisor,uuid=1a32b655-0acf-424b-8722-9e7f507a3070 -no-user-config 
> -nodefaults -chardev 
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-r-74-VM/monitor.sock,server,nowait
>  -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
> -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device 
> virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive 
> file=rbd:rbd/15ea00f9-e52e-43cf-9e5e-62188e9da5d2:id=cloudstack:key===:auth_supported=cephx\;none:mon_host=10.0.0.23\:6789,if=none,id=drive-virtio-disk0,format=raw,serial=15ea00f9e52e43cf9e5e,cache=none
>  -device 
> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2
>  -drive 
> file=/usr/share/cloudstack-common/vms/systemvm.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw,cache=none
>  -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 
> -netdev tap,fd=32,id=hostnet0,vhost=on,vhostfd=33 -device 
> virtio-net-pci,netdev=hostnet0,id=net0,mac=11:11:11:11:11:11,bus=pci.0,addr=0x3,rombar=0,romfile=
>  -netdev tap,fd=34,id=hostnet1,vhost=on,vhostfd=35 -device 
> virtio-net-pci,netdev=hostnet1,id=net1,mac=22:22:22:22:22:22,bus=pci.0,addr=0x4,rombar=0,romfile=
>  -netdev tap,fd=36,id=hostnet2,vhost=on,vhostfd=37 -device 
> virtio-net-pci,netdev=hostnet2,id=net2,mac=33:33:33:33:33:33,bus=pci.0,addr=0x5,rombar=0,romfile=
>  -chardev pty,id=charserial0 -device 
> isa-serial,chardev=charserial0,id=serial0 -chardev 
> socket,id=charchannel0,path=/var/lib/libvirt/qemu/r-74-VM.agent,server,nowait 
> -device 
> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=r-74-VM.vport
>  -device usb-tablet,id=input0 -vnc 10.0.0.2:4,password -vga cirrus -incoming 
> tcp:[::]:49152 -msg timestamp=on
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CLOUDSTACK-9247) Templates go into "Not Ready" state after restarting manangement server with Swift as a Secondary Storage

2016-01-21 Thread Syed Ahmed (JIRA)
Syed Ahmed created CLOUDSTACK-9247:
--

 Summary: Templates go into "Not Ready" state after restarting 
manangement server with Swift as a Secondary Storage
 Key: CLOUDSTACK-9247
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9247
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Secondary Storage
Affects Versions: Future, 4.7.0, 4.8.0
Reporter: Syed Ahmed


When using Swift as a secondary storage, we create a template.properties file 
which stores the metadata about the template. Currently the data which is 
present in the file is incorrect which leads to templates becoming unavailable 
after they are downloaded.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CLOUDSTACK-9248) Ability to download templates when using Swift as a Secondary Storage

2016-01-21 Thread Syed Ahmed (JIRA)
Syed Ahmed created CLOUDSTACK-9248:
--

 Summary: Ability to download templates when using Swift as a 
Secondary Storage
 Key: CLOUDSTACK-9248
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9248
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Secondary Storage
Affects Versions: Future, 4.7.0, 4.8.0
Reporter: Syed Ahmed
Priority: Minor


Currently, when using Swift as a Secondary Storage, we cannot download the 
templates that get uploaded. I am opening this bug to track the addition of 
that functionality.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-9247) Templates go into "Not Ready" state after restarting manangement server with Swift as a Secondary Storage

2016-01-21 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1527#comment-1527
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9247:


Github user syed commented on the pull request:

https://github.com/apache/cloudstack/pull/1331#issuecomment-173678575
  
Jira ticket : 
[CLOUDSTACK-9247](https://issues.apache.org/jira/browse/CLOUDSTACK-9247)

I've tested this on our local setup and it works as expected. 


> Templates go into "Not Ready" state after restarting manangement server with 
> Swift as a Secondary Storage
> -
>
> Key: CLOUDSTACK-9247
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9247
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Secondary Storage
>Affects Versions: Future, 4.7.0, 4.8.0
>Reporter: Syed Ahmed
>
> When using Swift as a secondary storage, we create a template.properties file 
> which stores the metadata about the template. Currently the data which is 
> present in the file is incorrect which leads to templates becoming 
> unavailable after they are downloaded.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-9248) Ability to download templates when using Swift as a Secondary Storage

2016-01-21 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1584#comment-1584
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9248:


Github user syed commented on the pull request:

https://github.com/apache/cloudstack/pull/1332#issuecomment-173688390
  
JIRA: 
[CLOUDSTACK-9248](https://issues.apache.org/jira/browse/CLOUDSTACK-9248)

Tested this on our local setup. Created a template and generated the 
download link. Verified the download and it is the same as the template. 


> Ability to download templates when using Swift as a Secondary Storage
> -
>
> Key: CLOUDSTACK-9248
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9248
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Secondary Storage
>Affects Versions: Future, 4.7.0, 4.8.0
>Reporter: Syed Ahmed
>Priority: Minor
>
> Currently, when using Swift as a Secondary Storage, we cannot download the 
> templates that get uploaded. I am opening this bug to track the addition of 
> that functionality.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CLOUDSTACK-9249) Broken link on website & missing documentation

2016-01-21 Thread Sam McLeod (JIRA)
Sam McLeod created CLOUDSTACK-9249:
--

 Summary: Broken link on website & missing documentation
 Key: CLOUDSTACK-9249
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9249
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Doc
Reporter: Sam McLeod


It looks like there is no documentation / install guide for 4.7?

1. Click "Installation Guide" on https://cloudstack.apache.org/downloads.html
2. You are redirected to 
http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.7/
3. This documentation / page does not exist



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CLOUDSTACK-9250) Storage automation results in java memory leaks.

2016-01-21 Thread Balaji Mani (JIRA)
Balaji Mani created CLOUDSTACK-9250:
---

 Summary: Storage automation results in java memory leaks.
 Key: CLOUDSTACK-9250
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9250
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation
Affects Versions: 4.6.0
Reporter: Balaji Mani
Priority: Critical


While automating the storage creation and deletion in selenium, after 1000 
storage creation and deletion, the CloudStack management server getting freezes 
due to JAVA Heap.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-8958) add dedicated ips to domain

2016-01-21 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15112028#comment-15112028
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8958:


GitHub user ustcweizhou opened a pull request:

https://github.com/apache/cloudstack/pull/1357

CLOUDSTACK-8958: release dedicated ip range in domain removal

We are able to assign didacated vlan ip ranges after the merge of 
CLOUDSTACK-8958.
These ip ranges need to be released automatically when we delete a domain.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ustcweizhou/cloudstack 
release-ip-ranges-for-domain

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1357.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1357


commit 252ebb56f23cdffa243f8c71116688f19f6f9f0c
Author: Wei Zhou 
Date:   2016-01-20T16:21:06Z

CLOUDSTACK-8958: release dedicated ip range in domain removal




> add dedicated ips to domain
> ---
>
> Key: CLOUDSTACK-8958
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8958
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Wei Zhou
>Assignee: Wei Zhou
>
> add dedicated ips to domain 
> ips are dedicated to Account for now, so other customers and projects in the 
> same domain will use the system ip. this is not what we need.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)