[jira] [Created] (CLOUDSTACK-9083) Add disk serial to vm/libvirt xml in case of KVM
Rohit Yadav created CLOUDSTACK-9083: --- Summary: Add disk serial to vm/libvirt xml in case of KVM Key: CLOUDSTACK-9083 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9083 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Rohit Yadav Assignee: Rohit Yadav Priority: Minor Fix For: 4.5.3, 4.7.0, 4.6.1 Certain appliances/software fail on KVM as they require disk serials (inside of the VM). The fix would be to add a disk serial (from volume uuid) in the generated libvirt xml for all disks except for lun/scsi block type disks (which we don't support yet, so we can add in a deviceType for now and leave some comment). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9064) Can't create multiple "Guest Networks" with same VLAN ID in the same zone on different "Physical Networks"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026264#comment-15026264 ] ASF GitHub Bot commented on CLOUDSTACK-9064: Github user bhaisaab commented on the pull request: https://github.com/apache/cloudstack/pull/1116#issuecomment-159501130 LGTM > Can't create multiple "Guest Networks" with same VLAN ID in the same zone on > different "Physical Networks" > --- > > Key: CLOUDSTACK-9064 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9064 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.2 >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Critical > > We can't create multiple "Guest Networks" with same VLAN ID in the same zone > on different "Physical Networks". > I get this message then I try: > There is a isolated/shared network with vlan id: already exists in > zone > We had added that feature and it was working in 4.1+, but > apparently there is a regression. There's no reason the same VLAN ids can't > be reused on different physical networks > http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201505.mbox/%3CCALFpzo5X169uj-3e4Jb-BsJ%2BXabSUyFJfMULKFNoBP0pP_geLg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9064) Can't create multiple "Guest Networks" with same VLAN ID in the same zone on different "Physical Networks"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026265#comment-15026265 ] ASF GitHub Bot commented on CLOUDSTACK-9064: Github user bhaisaab commented on the pull request: https://github.com/apache/cloudstack/pull/1115#issuecomment-159501138 LGTM > Can't create multiple "Guest Networks" with same VLAN ID in the same zone on > different "Physical Networks" > --- > > Key: CLOUDSTACK-9064 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9064 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.2 >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Critical > > We can't create multiple "Guest Networks" with same VLAN ID in the same zone > on different "Physical Networks". > I get this message then I try: > There is a isolated/shared network with vlan id: already exists in > zone > We had added that feature and it was working in 4.1+, but > apparently there is a regression. There's no reason the same VLAN ids can't > be reused on different physical networks > http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201505.mbox/%3CCALFpzo5X169uj-3e4Jb-BsJ%2BXabSUyFJfMULKFNoBP0pP_geLg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9064) Can't create multiple "Guest Networks" with same VLAN ID in the same zone on different "Physical Networks"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026263#comment-15026263 ] ASF GitHub Bot commented on CLOUDSTACK-9064: Github user bhaisaab commented on the pull request: https://github.com/apache/cloudstack/pull/1117#issuecomment-159501118 LGTM > Can't create multiple "Guest Networks" with same VLAN ID in the same zone on > different "Physical Networks" > --- > > Key: CLOUDSTACK-9064 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9064 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.2 >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Critical > > We can't create multiple "Guest Networks" with same VLAN ID in the same zone > on different "Physical Networks". > I get this message then I try: > There is a isolated/shared network with vlan id: already exists in > zone > We had added that feature and it was working in 4.1+, but > apparently there is a regression. There's no reason the same VLAN ids can't > be reused on different physical networks > http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201505.mbox/%3CCALFpzo5X169uj-3e4Jb-BsJ%2BXabSUyFJfMULKFNoBP0pP_geLg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9081) Unable to convert to json in Storage XenMotion
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026248#comment-15026248
]
ASF GitHub Bot commented on CLOUDSTACK-9081:
GitHub user karuturi opened a pull request:
https://github.com/apache/cloudstack/pull/1118
CLOUDSTACK-9081 Migration of vm across clusters fails in clustered MS setup
Storage motion of vm across clusters/xenserver-pools fails in a
clustered management server setup. In xen storage motion we have to send
a migrate_receive command to the destination host, followed by
migrate_send command to the source host. The sr and network detials of
the destination host have to be passed in migrate_send command on the
source. While migrating across clusters the source and destination
resources are seperate objects. To pass this information across
resources we have to send seperate migrate with storage receive and send
commands to the resource. In a clustered ms setup these commands may
have to be forwarded to another ms as the resource may be owned by it.
The serilization of the command and answer objects fails in such case as
it doesn't understand the xapi sr and network objects. Made a change to
serialize these objects in the resource layer and pass the around as
strings in the command and answer objects.
Reviewed-By: @likitha
Author: @devdeep
Tested-By: @sailajamada
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/karuturi/cloudstack CLOUDSTACK-9081
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1118.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 #1118
commit d6e15aa530ac99652975f688e9aebe6e4ab5a00e
Author: Devdeep Singh
Date: 2015-11-25T04:01:11Z
CLOUDSTACK-9081 Migration of vm across clusters fails in clustered MS setup
Storage motion of vm across clusters/xenserver-pools fails in a
clustered management server setup. In xen storage motion we have to send
a migrate_receive command to the destination host, followed by
migrate_send command to the source host. The sr and network detials of
the destination host have to be passed in migrate_send command on the
source. While migrating across clusters the source and destination
resources are seperate objects. To pass this information across
resources we have to send seperate migrate with storage receive and send
commands to the resource. In a clustered ms setup these commands may
have to be forwarded to another ms as the resource may be owned by it.
The serilization of the command and answer objects fails in such case as
it doesn't understand the xapi sr and network objects. Made a change to
serialize these objects in the resource layer and pass the around as
strings in the command and answer objects. Reviewed-By: Likitha
> Unable to convert to json in Storage XenMotion
> --
>
> Key: CLOUDSTACK-9081
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9081
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Reporter: Rajani Karuturi
>
> Storage motion of vm across clusters/xenserver-pools fails
> in a clustered management server setup. In xen storage motion we have to send
> a migrate_receive command to the destination host, followed by migrate_send
> command to the source host. The sr and network detials of the destination
> host have to be passed in migrate_send command on the source. While migrating
> across clusters the source and destination resources are seperate objects. To
> pass this information across resources we have to send seperate migrate with
> storage receive and send commands to the resource. In a clustered ms setup
> these commands may have to be forwarded to another ms as the resource may be
> owned by it. The serilization of the command and answer objects fails in such
> case as it doesn't understand the xapi sr and network objects.
> The following JSON conversion error was recorded in management-server2.log.
> {noformat}
> 2015-06-19 10:36:48,507 ERROR [c.c.a.t.Request] (AgentManager-Handler-7:null)
> (logid:) Unable to convert to json:
> [{"com.cloud.agent.api.MigrateWithStorageReceiveAnswer":{"volumeToSr":[{"t":{"id":51828,"name":"Data4","path":"abce3250-8c25-4634-89e3-cef7af6e16b8","size":5368709120,"type":"DATADISK","storagePoolType":"IscsiLUN","storagePoolUuid":"3ae7d68f-8981-34ac-95f0-c67ef3354748","deviceId":4},"u":{"ref":"OpaqueRef:63e4185a-835a-c7e2-4dc3-fbcb95e97872"}},{"t":{"id":51729,"name":"RO
[jira] [Commented] (CLOUDSTACK-9064) Can't create multiple "Guest Networks" with same VLAN ID in the same zone on different "Physical Networks"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026203#comment-15026203 ] ASF GitHub Bot commented on CLOUDSTACK-9064: GitHub user abhinandanprateek opened a pull request: https://github.com/apache/cloudstack/pull/1117 CLOUDSTACK-9064: The users should be able to create multiple Guest Sh… https://issues.apache.org/jira/browse/CLOUDSTACK-9064 CLOUDSTACK-9064: The users should be able to create multiple Guest Shared Networks in same Vlan ID, same Physical Network and same network, just with a different IP ranges. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shapeblue/cloudstack 4.5-9064 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1117.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 #1117 commit 2e6c7ce4c8bc98c51d153a595d757bbcc886a2a6 Author: Abhinandan Prateek Date: 2015-11-24T07:59:59Z CLOUDSTACK-9064: The users should be able to create multiple Guest Shared Networks in same Vlan ID, same Physical Network and same network, just with a different IP ranges. > Can't create multiple "Guest Networks" with same VLAN ID in the same zone on > different "Physical Networks" > --- > > Key: CLOUDSTACK-9064 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9064 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.2 >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Critical > > We can't create multiple "Guest Networks" with same VLAN ID in the same zone > on different "Physical Networks". > I get this message then I try: > There is a isolated/shared network with vlan id: already exists in > zone > We had added that feature and it was working in 4.1+, but > apparently there is a regression. There's no reason the same VLAN ids can't > be reused on different physical networks > http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201505.mbox/%3CCALFpzo5X169uj-3e4Jb-BsJ%2BXabSUyFJfMULKFNoBP0pP_geLg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9064) Can't create multiple "Guest Networks" with same VLAN ID in the same zone on different "Physical Networks"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026190#comment-15026190 ] ASF GitHub Bot commented on CLOUDSTACK-9064: GitHub user abhinandanprateek opened a pull request: https://github.com/apache/cloudstack/pull/1116 CLOUDSTACK-9064: The users should be able to create multiple Guest Sh… https://issues.apache.org/jira/browse/CLOUDSTACK-9064 CLOUDSTACK-9064: The users should be able to create multiple Guest Shared Networks in same Vlan ID, same Physical Network and same network, just with a different IP ranges. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shapeblue/cloudstack 4.6-9064 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1116.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 #1116 commit d09898553e8a7722f82866367923bc8cedc62829 Author: Abhinandan Prateek Date: 2015-11-24T07:59:59Z CLOUDSTACK-9064: The users should be able to create multiple Guest Shared Networks in same Vlan ID, same Physical Network and same network, just with a different IP ranges. > Can't create multiple "Guest Networks" with same VLAN ID in the same zone on > different "Physical Networks" > --- > > Key: CLOUDSTACK-9064 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9064 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.2 >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Critical > > We can't create multiple "Guest Networks" with same VLAN ID in the same zone > on different "Physical Networks". > I get this message then I try: > There is a isolated/shared network with vlan id: already exists in > zone > We had added that feature and it was working in 4.1+, but > apparently there is a regression. There's no reason the same VLAN ids can't > be reused on different physical networks > http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201505.mbox/%3CCALFpzo5X169uj-3e4Jb-BsJ%2BXabSUyFJfMULKFNoBP0pP_geLg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9064) Can't create multiple "Guest Networks" with same VLAN ID in the same zone on different "Physical Networks"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026177#comment-15026177 ] ASF GitHub Bot commented on CLOUDSTACK-9064: GitHub user abhinandanprateek opened a pull request: https://github.com/apache/cloudstack/pull/1115 CLOUDSTACK-9064: The users should be able to create multiple Guest Sh… …ared Networks in same Vlan ID, same Physical Network and same network, just with a different IP ranges. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shapeblue/cloudstack master-9064 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1115.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 #1115 commit 0d2f1ed81cc3e3b28274772c5baa41c55bae58b7 Author: Abhinandan Prateek Date: 2015-11-24T07:59:59Z CLOUDSTACK-9064: The users should be able to create multiple Guest Shared Networks in same Vlan ID, same Physical Network and same network, just with a different IP ranges. > Can't create multiple "Guest Networks" with same VLAN ID in the same zone on > different "Physical Networks" > --- > > Key: CLOUDSTACK-9064 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9064 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.2 >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Critical > > We can't create multiple "Guest Networks" with same VLAN ID in the same zone > on different "Physical Networks". > I get this message then I try: > There is a isolated/shared network with vlan id: already exists in > zone > We had added that feature and it was working in 4.1+, but > apparently there is a regression. There's no reason the same VLAN ids can't > be reused on different physical networks > http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201505.mbox/%3CCALFpzo5X169uj-3e4Jb-BsJ%2BXabSUyFJfMULKFNoBP0pP_geLg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9064) Can't create multiple "Guest Networks" with same VLAN ID in the same zone on different "Physical Networks"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026149#comment-15026149 ] ASF GitHub Bot commented on CLOUDSTACK-9064: Github user abhinandanprateek closed the pull request at: https://github.com/apache/cloudstack/pull/1113 > Can't create multiple "Guest Networks" with same VLAN ID in the same zone on > different "Physical Networks" > --- > > Key: CLOUDSTACK-9064 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9064 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.2 >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Critical > > We can't create multiple "Guest Networks" with same VLAN ID in the same zone > on different "Physical Networks". > I get this message then I try: > There is a isolated/shared network with vlan id: already exists in > zone > We had added that feature and it was working in 4.1+, but > apparently there is a regression. There's no reason the same VLAN ids can't > be reused on different physical networks > http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201505.mbox/%3CCALFpzo5X169uj-3e4Jb-BsJ%2BXabSUyFJfMULKFNoBP0pP_geLg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9064) Can't create multiple "Guest Networks" with same VLAN ID in the same zone on different "Physical Networks"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026146#comment-15026146 ] ASF GitHub Bot commented on CLOUDSTACK-9064: GitHub user abhinandanprateek reopened a pull request: https://github.com/apache/cloudstack/pull/1113 CLOUDSTACK-9064: The users should be able to create multiple Guest Sh… Fix for https://issues.apache.org/jira/browse/CLOUDSTACK-9064 The users should be able to create multiple Guest Shared Networks in same Vlan ID, same Physical Network and same network, just with a different IP ranges. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shapeblue/cloudstack 4.5.2-vlan Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1113.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 #1113 commit d631e989ec80d6e6a7ed1156169605859bc64608 Author: Abhinandan Prateek Date: 2015-11-24T07:59:59Z CLOUDSTACK-9064: The users should be able to create multiple Guest Shared Networks in same Vlan ID, same Physical Network and same network, just with a different IP ranges. commit 452a5d9e01fb9f0e26d3f4ec59ec904737767b97 Author: Abhinandan Prateek Date: 2015-11-25T04:02:30Z CLOUDSTACK-9064: The users should be able to create multiple Guest Shared Networks in same Vlan ID, same Physical Network and same network, just with a different IP ranges. > Can't create multiple "Guest Networks" with same VLAN ID in the same zone on > different "Physical Networks" > --- > > Key: CLOUDSTACK-9064 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9064 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.2 >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Critical > > We can't create multiple "Guest Networks" with same VLAN ID in the same zone > on different "Physical Networks". > I get this message then I try: > There is a isolated/shared network with vlan id: already exists in > zone > We had added that feature and it was working in 4.1+, but > apparently there is a regression. There's no reason the same VLAN ids can't > be reused on different physical networks > http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201505.mbox/%3CCALFpzo5X169uj-3e4Jb-BsJ%2BXabSUyFJfMULKFNoBP0pP_geLg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9065) Packaging RPM: Add option for package release version, cleanup and lint
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15025860#comment-15025860 ] ASF GitHub Bot commented on CLOUDSTACK-9065: GitHub user davidamorimfaria opened a pull request: https://github.com/apache/cloudstack/pull/1114 CLOUDSTACK-9065: fix bug when creating packaging with noredist flag You can merge this pull request into a Git repository by running: $ git pull https://github.com/davidamorimfaria/cloudstack 4.6 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1114.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 #1114 commit adb0d3bb744f3c4ed86201a8f811f16a0b9f87de Author: David Amorim Faria Date: 2015-11-25T00:41:22Z CLOUDSTACK-9065: fix bug when creating packaging with noredist flag > Packaging RPM: Add option for package release version, cleanup and lint > --- > > Key: CLOUDSTACK-9065 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9065 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Packaging >Affects Versions: 4.6.0 >Reporter: David Amorim Faria >Assignee: David Amorim Faria >Priority: Trivial > > In RPM Packaging, add option for package release version. > Also, code cleanup and some linting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9064) Can't create multiple "Guest Networks" with same VLAN ID in the same zone on different "Physical Networks"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15025463#comment-15025463 ] ASF GitHub Bot commented on CLOUDSTACK-9064: Github user remibergsma commented on the pull request: https://github.com/apache/cloudstack/pull/1113#issuecomment-159411260 What about 4.6? > Can't create multiple "Guest Networks" with same VLAN ID in the same zone on > different "Physical Networks" > --- > > Key: CLOUDSTACK-9064 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9064 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.2 >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Critical > > We can't create multiple "Guest Networks" with same VLAN ID in the same zone > on different "Physical Networks". > I get this message then I try: > There is a isolated/shared network with vlan id: already exists in > zone > We had added that feature and it was working in 4.1+, but > apparently there is a regression. There's no reason the same VLAN ids can't > be reused on different physical networks > http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201505.mbox/%3CCALFpzo5X169uj-3e4Jb-BsJ%2BXabSUyFJfMULKFNoBP0pP_geLg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9051) Update Ip address of NIC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15025259#comment-15025259 ] ASF GitHub Bot commented on CLOUDSTACK-9051: Github user DaanHoogland commented on the pull request: https://github.com/apache/cloudstack/pull/1086#issuecomment-159391187 tests performed [1086.network.results.txt](https://github.com/apache/cloudstack/files/43165/1086.network.results.txt) [1086.vpc.results.txt](https://github.com/apache/cloudstack/files/43166/1086.vpc.results.txt) > Update Ip address of NIC > > > Key: CLOUDSTACK-9051 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9051 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Wei Zhou > > Sometimes we want to change the ipaddress of a NIC to a specified ip. > we need to add an API to replace the manual database change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9061) cannot deploy Instance when using Swift as Secondary Storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15025092#comment-15025092 ] ASF GitHub Bot commented on CLOUDSTACK-9061: Github user pdion891 commented on the pull request: https://github.com/apache/cloudstack/pull/1112#issuecomment-159370086 @remibergsma, yep, let me test this, we would also like to have this into 4.6.1 if we can test it on time. Thanks. > cannot deploy Instance when using Swift as Secondary Storage > > > Key: CLOUDSTACK-9061 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9061 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Secondary Storage >Affects Versions: 4.5.2, 4.6.0 >Reporter: Pierre-Luc Dion > > When using Swift as Secondary Storage, new Instance cannot be created. > Uploading new template work and end up correctly into swift. but creating > VM's from this new template fail. > Seams that the SSVM fail do create the cache template into the Primary > storage. Observer on XenServer 6.2 with CloudStack 4.5.2 and 4.6.0rc1 > This feature work well in 4.4.x. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9069) Newly added project is not showing in the drop down until the browser is refreshed.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024887#comment-15024887 ] ASF GitHub Bot commented on CLOUDSTACK-9069: Github user nitin-maharana commented on the pull request: https://github.com/apache/cloudstack/pull/1082#issuecomment-159346524 I tested in chrome and firefox. > Newly added project is not showing in the drop down until the browser is > refreshed. > --- > > Key: CLOUDSTACK-9069 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9069 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitin Kumar Maharana > > Steps to reproduce: > 1.Login as admin and navigate to Projects page. > 2.Add one project and navigate to Dashboard. > 3.Check for newly added project in Project drop down. > Actual behaviour: > New project is showing in drop down only after refreshing the browser. > Expected behaviour: > New project should be shown in drop down without refreshing the browser also. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9069) Newly added project is not showing in the drop down until the browser is refreshed.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024851#comment-15024851 ] ASF GitHub Bot commented on CLOUDSTACK-9069: Github user rafaelweingartner commented on the pull request: https://github.com/apache/cloudstack/pull/1082#issuecomment-159338806 @nitin-maharana , I do not have CS 4.6 or 4.5.1 here to test. However, I have compared those files from CS 4.3.2 with files from 4.5.1 and 4.6.0. I could not see a change that would make that stop working (since it is working in 4.3.2). I might have overlooked them, but can someone else also test it? Additionally, in what browser did you test? > Newly added project is not showing in the drop down until the browser is > refreshed. > --- > > Key: CLOUDSTACK-9069 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9069 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitin Kumar Maharana > > Steps to reproduce: > 1.Login as admin and navigate to Projects page. > 2.Add one project and navigate to Dashboard. > 3.Check for newly added project in Project drop down. > Actual behaviour: > New project is showing in drop down only after refreshing the browser. > Expected behaviour: > New project should be shown in drop down without refreshing the browser also. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9064) Can't create multiple "Guest Networks" with same VLAN ID in the same zone on different "Physical Networks"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024292#comment-15024292 ] ASF GitHub Bot commented on CLOUDSTACK-9064: Github user bhaisaab commented on the pull request: https://github.com/apache/cloudstack/pull/1113#issuecomment-159234061 LGTM (yet to test it) > Can't create multiple "Guest Networks" with same VLAN ID in the same zone on > different "Physical Networks" > --- > > Key: CLOUDSTACK-9064 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9064 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.2 >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Critical > > We can't create multiple "Guest Networks" with same VLAN ID in the same zone > on different "Physical Networks". > I get this message then I try: > There is a isolated/shared network with vlan id: already exists in > zone > We had added that feature and it was working in 4.1+, but > apparently there is a regression. There's no reason the same VLAN ids can't > be reused on different physical networks > http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201505.mbox/%3CCALFpzo5X169uj-3e4Jb-BsJ%2BXabSUyFJfMULKFNoBP0pP_geLg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9082) Improvements with list public ip addresses
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024195#comment-15024195 ] Wei Zhou commented on CLOUDSTACK-9082: -- (5) add optional IP address parameter to command associateIpAddress > Improvements with list public ip addresses > -- > > Key: CLOUDSTACK-9082 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9082 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Wei Zhou > > it will include the following changes: > (1) list ALL/Allocated/Free Ips in shared network > (2) list all available ips when acqure a new public ip address (for isolated > network) > (3) list available ips when acquire secondary ips (for shared network) > (4) list available ips (on shared network) when update vm nic ip. (related to > CLOUDSTACK-9051) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9079) ipsec service is not running after restarting virtual router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024144#comment-15024144 ] Erik Weber commented on CLOUDSTACK-9079: testing fix now :-) > ipsec service is not running after restarting virtual router > > > Key: CLOUDSTACK-9079 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9079 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: SystemVM, Virtual Router >Affects Versions: 4.6.0 > Environment: ACS 4.5.1 upgraded to 4.6.0 >Reporter: Erik Weber >Priority: Critical > Labels: systemvm, virtualrouter, vpn > > after upgrading to 4.6.0 the ipsec service does no longer automatically start > and as an effect vpn does not work. > manually starting the ipsec service, or doing any vpn related configuration > (adding/deleting users) remedies the problem. > Steps to reproduce: > 1) Install ACS 4.6.0 > 2) Configure a VPC (I haven't tested with normal isolated networks) > 3) Enable remote access VPN, configure a user > 4) Confirm that VPN works > 5) Restart the VR > 6) Confirm that VPN does NOT work, either by trying to connect or by issuing > 'service ipsec status' on the VR -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9051) Update Ip address of NIC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024115#comment-15024115 ] ASF GitHub Bot commented on CLOUDSTACK-9051: Github user ustcweizhou commented on the pull request: https://github.com/apache/cloudstack/pull/1086#issuecomment-159211074 Just added a new commit in this PR. CLOUDSTACK-9051: reprogram network as a part of vm nic ip update Review and testing are welcome! > Update Ip address of NIC > > > Key: CLOUDSTACK-9051 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9051 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Wei Zhou > > Sometimes we want to change the ipaddress of a NIC to a specified ip. > we need to add an API to replace the manual database change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9082) Improvements with list public ip addresses
Wei Zhou created CLOUDSTACK-9082: Summary: Improvements with list public ip addresses Key: CLOUDSTACK-9082 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9082 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Wei Zhou Assignee: Wei Zhou it will include the following changes: (1) list ALL/Allocated/Free Ips in shared network (2) list all available ips when acqure a new public ip address (for isolated network) (3) list available ips when acquire secondary ips (for shared network) (4) list available ips (on shared network) when update vm nic ip. (related to CLOUDSTACK-9051) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9081) Unable to convert to json in Storage XenMotion
Rajani Karuturi created CLOUDSTACK-9081:
---
Summary: Unable to convert to json in Storage XenMotion
Key: CLOUDSTACK-9081
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9081
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Rajani Karuturi
Storage motion of vm across clusters/xenserver-pools fails
in a clustered management server setup. In xen storage motion we have to send a
migrate_receive command to the destination host, followed by migrate_send
command to the source host. The sr and network detials of the destination host
have to be passed in migrate_send command on the source. While migrating across
clusters the source and destination resources are seperate objects. To pass
this information across resources we have to send seperate migrate with storage
receive and send commands to the resource. In a clustered ms setup these
commands may have to be forwarded to another ms as the resource may be owned by
it. The serilization of the command and answer objects fails in such case as it
doesn't understand the xapi sr and network objects.
The following JSON conversion error was recorded in management-server2.log.
{noformat}
2015-06-19 10:36:48,507 ERROR [c.c.a.t.Request] (AgentManager-Handler-7:null)
(logid:) Unable to convert to json:
[{"com.cloud.agent.api.MigrateWithStorageReceiveAnswer":{"volumeToSr":[{"t":{"id":51828,"name":"Data4","path":"abce3250-8c25-4634-89e3-cef7af6e16b8","size":5368709120,"type":"DATADISK","storagePoolType":"IscsiLUN","storagePoolUuid":"3ae7d68f-8981-34ac-95f0-c67ef3354748","deviceId":4},"u":{"ref":"OpaqueRef:63e4185a-835a-c7e2-4dc3-fbcb95e97872"}},{"t":{"id":51729,"name":"ROOT-61290","path":"19a7495d-fb3b-45ef-92e6-e86c017ed1f2","size":53687091200,"type":"ROOT","storagePoolType":"IscsiLUN","storagePoolUuid":"cb398aad-77cc-3916-9e3f-3debec31ff71","deviceId":0},"u":{"ref":"OpaqueRef:63e4185a-835a-c7e2-4dc3-fbcb95e97872"}},{"t":{"id":51826,"name":"Data2","path":"13982b0d-e427-45df-9c7f-b258406bdcd7","size":5368709120,"type":"DATADISK","storagePoolType":"IscsiLUN","storagePoolUuid":"3ae7d68f-8981-34ac-95f0-c67ef3354748","deviceId":2},"u":{"ref":"OpaqueRef:63e4185a-835a-c7e2-4dc3-fbcb95e97872"}},{"t":{"id":51825,"name":"Data1","path":"064685fc-1abf-4086-8f81-98dfea2090ce","size":5368709120,"type":"DATADISK","storagePoolType":"IscsiLUN","storagePoolUuid":"3ae7d68f-8981-34ac-95f0-c67ef3354748","deviceId":1},"u":{"ref":"OpaqueRef:63e4185a-835a-c7e2-4dc3-fbcb95e97872"}},{"t":{"id":51829,"name":"Data5","path":"85d8ab52-7c79-4338-9433-11a50cb0bbc1","size":5368709120,"type":"DATADISK","storagePoolType":"IscsiLUN","storagePoolUuid":"3ae7d68f-8981-34ac-95f0-c67ef3354748","deviceId":5},"u":{"ref":"OpaqueRef:63e4185a-835a-c7e2-4dc3-fbcb95e97872"}},{"t":{"id":51827,"name":"Data3","path":"7fc80df1-5065-4286-a1c8-87574e798251","size":5368709120,"type":"DATADISK","storagePoolType":"IscsiLUN","storagePoolUuid":"3ae7d68f-8981-34ac-95f0-c67ef3354748","deviceId":12},"u":{"ref":"OpaqueRef:63e4185a-835a-c7e2-4dc3-fbcb95e97872"}}],"nicToNetwork":[{"t":{"deviceId":0,"networkRateMbps":2000,"defaultNic":true,"pxeDisable":false,"nicUuid":"45cd68fb-fe60-454c-9a08-f73fd902cef0","uuid":"38a40e2d-0f12-4015-9753-8c08d76d52dc","ip":"172.27.0.113","netmask":"255.255.0.0","gateway":"172.27.0.1","mac":"02:00:59:6b:00:08","dns1":"8.8.8.8","dns2":"8.8.4.4","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://1109","isolationUri":"vlan://1109","isSecurityGroupEnabled":false,"name":"cloud-public"},"u":{"ref":"OpaqueRef:c9087c77-81f9-03eb-9cf8-df7868354563"}},{"t":{"deviceId":1,"networkRateMbps":-1,"defaultNic":false,"pxeDisable":false,"nicUuid":"1504aed4-4871-48d5-abed-581889cea7c7","uuid":"28f3a4f4-dd3d-42d2-b4a4-5243a50232c8","ip":"10.10.10.2","netmask":"255.255.255.0","gateway":"10.10.10.1","mac":"06:a8:b8:00:10:83","dns1":"8.8.8.8","dns2":"8.8.4.4","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://3339","isolationUri":"vlan://3339","isSecurityGroupEnabled":false,"name":"cloud-public"},"u":{"ref":"OpaqueRef:0110ebab-607d-f02f-134a-383e77324677"}}],"token":{"session_id":"OpaqueRef:c5929d08-fc30-939b-fd01-0921799fb98a","host":"OpaqueRef:0d842514-468d-4dd9-5dfe-015ce3898a66","SM":"http://10.32.1.4/services/SM?session_id\u003dOpaqueRef:c5929d08-fc30-939b-fd01-0921799fb98a","master":"http://10.13.4.1/","xenops":"http://10.32.1.4/services/xenops?session_id\u003dOpaqueRef:c5929d08-fc30-939b-fd01-0921799fb98a"},"result":true,"contextMap":{},"wait":0}}]
2015-06-19 10:36:48,507 WARN [c.c.u.n.Task] (AgentManager-Handler-7:null)
(logid:) Caught the following exception but pushing on
com.google.gson.JsonParseException: Type information is unavailable, and the
target object is not a primitive:
{"ref":"OpaqueRef:63e4185a-835a-c7e2-4dc3-fbcb95e97872"}
at
com.google.gson.JsonObjectDeseria
[jira] [Commented] (CLOUDSTACK-4787) Allow selection of scsi controller type in vSphere
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15023990#comment-15023990 ] Rohit Yadav commented on CLOUDSTACK-4787: - [~sateeshc] is the feature branch merged on master, do we have this feature working and available yet in 4.6 or 4.7/master? > Allow selection of scsi controller type in vSphere > -- > > Key: CLOUDSTACK-4787 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4787 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, UI, VMware >Affects Versions: 4.2.0, 4.3.0 > Environment: vSphere 5.1 >Reporter: Chris Sciarrino >Assignee: Sateesh Chodapuneedi >Priority: Critical > > When adding an OVA template for a vSphere environment allow the selection of > the scsi controller type. > Currently the instances are deployed with the the LSI Parallel controller > type. This results in a blue screen on boot when attempting to deploy > templates that use the LSI SAS controller. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9064) Can't create multiple "Guest Networks" with same VLAN ID in the same zone on different "Physical Networks"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15023958#comment-15023958 ] ASF GitHub Bot commented on CLOUDSTACK-9064: GitHub user abhinandanprateek opened a pull request: https://github.com/apache/cloudstack/pull/1113 CLOUDSTACK-9064: The users should be able to create multiple Guest Sh… Fix for https://issues.apache.org/jira/browse/CLOUDSTACK-9064 The users should be able to create multiple Guest Shared Networks in same Vlan ID, same Physical Network and same network, just with a different IP ranges. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shapeblue/cloudstack 4.5.2-vlan Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1113.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 #1113 commit d631e989ec80d6e6a7ed1156169605859bc64608 Author: Abhinandan Prateek Date: 2015-11-24T07:59:59Z CLOUDSTACK-9064: The users should be able to create multiple Guest Shared Networks in same Vlan ID, same Physical Network and same network, just with a different IP ranges. > Can't create multiple "Guest Networks" with same VLAN ID in the same zone on > different "Physical Networks" > --- > > Key: CLOUDSTACK-9064 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9064 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.2 >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Critical > > We can't create multiple "Guest Networks" with same VLAN ID in the same zone > on different "Physical Networks". > I get this message then I try: > There is a isolated/shared network with vlan id: already exists in > zone > We had added that feature and it was working in 4.1+, but > apparently there is a regression. There's no reason the same VLAN ids can't > be reused on different physical networks > http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201505.mbox/%3CCALFpzo5X169uj-3e4Jb-BsJ%2BXabSUyFJfMULKFNoBP0pP_geLg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
