[jira] [Commented] (CLOUDSTACK-10246) VM HA issues

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10246:
-

blueorangutan commented on issue #2474: CLOUDSTACK-10246 Fix Host HA and VM HA 
issues
URL: https://github.com/apache/cloudstack/pull/2474#issuecomment-371019688
 
 
   Trillian test result (tid-2328)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 21963 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2474-t2328-kvm-centos7.zip
   Intermitten failure detected: /marvin/tests/smoke/test_iso.py
   Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
   Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
   Smoke tests completed. 52 look OK, 2 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   test_04_rvpc_privategw_static_routes | `Failure` | 329.18 | 
test_privategw_acl.py
   test_02_edit_iso | `Failure` | 0.04 | test_iso.py
   test_05_iso_permissions | `Failure` | 0.05 | test_iso.py
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> VM HA issues
> 
>
> Key: CLOUDSTACK-10246
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10246
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
> Environment: My setup is CentOS 7 Management server with 3 CentOS 7 
> KVM HVs, NFS as primary and secondary storages.
>Reporter: Nux
>Priority: Major
>
> VM HA fails to kick in when one of the hypervisors goes down.
> It even fails to restart the system VMs which remain down along with the 
> instances until the affected HV comes back online.
> When I crash or power off the HV the system marks it in the hosts list as 
> "Alert" or "Disconnected" respectively. It should get changed to "Down" after 
> that, but this never happens.
>  
> I have tried various combinations of setups (Adv, Basic), none succeeded.
>  
> My instances use HA enabled offerings.
> Management server DEBUG logs here:
> [http://tmp.nux.ro/CW4-vmhafail-411rc1.txt]
>  
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-8855) Improve Error Message for Host Alert State

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-8855:


blueorangutan commented on issue #2387: CLOUDSTACK-8855 Improve Error Message 
for Host Alert State and reconnect host API.
URL: https://github.com/apache/cloudstack/pull/2387#issuecomment-371014155
 
 
   Trillian test result (tid-2327)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 28075 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2387-t2327-kvm-centos7.zip
   Intermitten failure detected: /marvin/tests/smoke/test_certauthority_root.py
   Intermitten failure detected: /marvin/tests/smoke/test_public_ip_range.py
   Intermitten failure detected: /marvin/tests/smoke/test_templates.py
   Intermitten failure detected: /marvin/tests/smoke/test_usage.py
   Intermitten failure detected: /marvin/tests/smoke/test_volumes.py
   Intermitten failure detected: /marvin/tests/smoke/test_vpc_vpn.py
   Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py
   Smoke tests completed. 63 look OK, 4 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   test_04_extract_template | `Failure` | 128.29 | test_templates.py
   ContextSuite context=TestISOUsage>:setup | `Error` | 0.00 | test_usage.py
   test_06_download_detached_volume | `Failure` | 137.84 | test_volumes.py
   test_01_redundant_vpc_site2site_vpn | `Failure` | 324.51 | test_vpc_vpn.py
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improve Error Message for Host Alert State
> --
>
> Key: CLOUDSTACK-8855
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8855
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.6.0
>Reporter: Bharat Kumar
>Assignee: Bharat Kumar
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10314) Add Text-Field to each ACL Rule

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10314:
-

blueorangutan commented on issue #2475: [CLOUDSTACK-10314] Add Text-Field to 
each ACL Rule
URL: https://github.com/apache/cloudstack/pull/2475#issuecomment-370998663
 
 
   Trillian test result (tid-2326)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 22170 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2475-t2326-kvm-centos7.zip
   Smoke tests completed. 67 look OK, 0 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Add Text-Field to each ACL Rule 
> 
>
> Key: CLOUDSTACK-10314
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10314
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Minor
>
> It might be interesting to have a text field (e.g. CHAR-256) added to each 
> ACL rule, which allows to enter a "reason" for each FW Rule created. This is 
> valuable for customer documentation, as well as best practice for an evidence 
> towards auditing the system.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10317) In case of multiple-public ips, snat fails to work for addtional public nics/network for guest traffic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10317:
-

blueorangutan commented on issue #2476: CLOUDSTACK-10317: Fix SNAT rules for 
additional public nics
URL: https://github.com/apache/cloudstack/pull/2476#issuecomment-370973833
 
 
   Trillian test result (tid-2324)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 26230 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2476-t2324-kvm-centos7.zip
   Intermitten failure detected: /marvin/tests/smoke/test_templates.py
   Smoke tests completed. 67 look OK, 0 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> In case of multiple-public ips, snat fails to work for addtional public 
> nics/network for guest traffic
> --
>
> Key: CLOUDSTACK-10317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10317
> 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.12.0.0, 4.11.1.0
>
>
> If a VR has two+ public nics, traffic from guest VM fails to be NAT-ed 
> correctly for traffic towards additional public nics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10246) VM HA issues

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10246:
-

blueorangutan commented on issue #2474: CLOUDSTACK-10246 Fix Host HA and VM HA 
issues
URL: https://github.com/apache/cloudstack/pull/2474#issuecomment-370944019
 
 
   @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has 
been kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> VM HA issues
> 
>
> Key: CLOUDSTACK-10246
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10246
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
> Environment: My setup is CentOS 7 Management server with 3 CentOS 7 
> KVM HVs, NFS as primary and secondary storages.
>Reporter: Nux
>Priority: Major
>
> VM HA fails to kick in when one of the hypervisors goes down.
> It even fails to restart the system VMs which remain down along with the 
> instances until the affected HV comes back online.
> When I crash or power off the HV the system marks it in the hosts list as 
> "Alert" or "Disconnected" respectively. It should get changed to "Down" after 
> that, but this never happens.
>  
> I have tried various combinations of setups (Adv, Basic), none succeeded.
>  
> My instances use HA enabled offerings.
> Management server DEBUG logs here:
> [http://tmp.nux.ro/CW4-vmhafail-411rc1.txt]
>  
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10246) VM HA issues

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10246:
-

borisstoyanov commented on issue #2474: CLOUDSTACK-10246 Fix Host HA and VM HA 
issues
URL: https://github.com/apache/cloudstack/pull/2474#issuecomment-370943779
 
 
   @blueorangutan test


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> VM HA issues
> 
>
> Key: CLOUDSTACK-10246
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10246
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
> Environment: My setup is CentOS 7 Management server with 3 CentOS 7 
> KVM HVs, NFS as primary and secondary storages.
>Reporter: Nux
>Priority: Major
>
> VM HA fails to kick in when one of the hypervisors goes down.
> It even fails to restart the system VMs which remain down along with the 
> instances until the affected HV comes back online.
> When I crash or power off the HV the system marks it in the hosts list as 
> "Alert" or "Disconnected" respectively. It should get changed to "Down" after 
> that, but this never happens.
>  
> I have tried various combinations of setups (Adv, Basic), none succeeded.
>  
> My instances use HA enabled offerings.
> Management server DEBUG logs here:
> [http://tmp.nux.ro/CW4-vmhafail-411rc1.txt]
>  
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10232) SystemVMs and VR to run as HVM on XenServer

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10232:
-

blueorangutan commented on issue #2465: CLOUDSTACK-10232: SystemVMs and VR to 
run as HVM on XenServer
URL: https://github.com/apache/cloudstack/pull/2465#issuecomment-370917680
 
 
   Trillian test result (tid-2319)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 33265 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2465-t2319-kvm-centos7.zip
   Intermitten failure detected: /marvin/tests/smoke/test_public_ip_range.py
   Intermitten failure detected: /marvin/tests/smoke/test_ssvm.py
   Intermitten failure detected: /marvin/tests/smoke/test_templates.py
   Intermitten failure detected: /marvin/tests/smoke/test_usage.py
   Intermitten failure detected: /marvin/tests/smoke/test_volumes.py
   Intermitten failure detected: /marvin/tests/smoke/test_host_maintenance.py
   Smoke tests completed. 63 look OK, 4 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   test_04_extract_template | `Failure` | 128.39 | test_templates.py
   ContextSuite context=TestISOUsage>:setup | `Error` | 0.00 | test_usage.py
   test_06_download_detached_volume | `Failure` | 141.78 | test_volumes.py
   test_02_cancel_host_maintenace_with_migration_jobs | `Error` | 2.39 | 
test_host_maintenance.py
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> SystemVMs and VR to run as HVM on XenServer
> ---
>
> Key: CLOUDSTACK-10232
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10232
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM, Virtual Router, XenServer
>Affects Versions: 4.10.0.0, 4.9.3.0
>Reporter: Pierre-Luc Dion
>Priority: Major
>
> Following the recent Meltdown-Spectre security risk,one of the mitigation,as 
> of Jan 2018, for XenServer Hypervisor is to run Virtual-Machine in HVM mode.
> Currently SystemVMs and Virtual-Routers run as PV on XenServer and the eth0 
> is configured using {{/etc/init.d/cloud-early-config}} using grub params from 
> {{/proc/cmdline}}. When VM run as HVM, it is not possible to push initial 
> boot instruction via pygrub.
> Quick tests has been done using xenstore and it look like it would be 
> possible to send same initial boot instruction has pygrub but using xenstore 
> for HVM instances.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10246) VM HA issues

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10246:
-

blueorangutan commented on issue #2474: CLOUDSTACK-10246 Fix Host HA and VM HA 
issues
URL: https://github.com/apache/cloudstack/pull/2474#issuecomment-370913368
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1762


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> VM HA issues
> 
>
> Key: CLOUDSTACK-10246
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10246
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
> Environment: My setup is CentOS 7 Management server with 3 CentOS 7 
> KVM HVs, NFS as primary and secondary storages.
>Reporter: Nux
>Priority: Major
>
> VM HA fails to kick in when one of the hypervisors goes down.
> It even fails to restart the system VMs which remain down along with the 
> instances until the affected HV comes back online.
> When I crash or power off the HV the system marks it in the hosts list as 
> "Alert" or "Disconnected" respectively. It should get changed to "Down" after 
> that, but this never happens.
>  
> I have tried various combinations of setups (Adv, Basic), none succeeded.
>  
> My instances use HA enabled offerings.
> Management server DEBUG logs here:
> [http://tmp.nux.ro/CW4-vmhafail-411rc1.txt]
>  
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10246) VM HA issues

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10246:
-

blueorangutan commented on issue #2474: CLOUDSTACK-10246 Fix Host HA and VM HA 
issues
URL: https://github.com/apache/cloudstack/pull/2474#issuecomment-370900817
 
 
   @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep 
you posted as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> VM HA issues
> 
>
> Key: CLOUDSTACK-10246
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10246
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
> Environment: My setup is CentOS 7 Management server with 3 CentOS 7 
> KVM HVs, NFS as primary and secondary storages.
>Reporter: Nux
>Priority: Major
>
> VM HA fails to kick in when one of the hypervisors goes down.
> It even fails to restart the system VMs which remain down along with the 
> instances until the affected HV comes back online.
> When I crash or power off the HV the system marks it in the hosts list as 
> "Alert" or "Disconnected" respectively. It should get changed to "Down" after 
> that, but this never happens.
>  
> I have tried various combinations of setups (Adv, Basic), none succeeded.
>  
> My instances use HA enabled offerings.
> Management server DEBUG logs here:
> [http://tmp.nux.ro/CW4-vmhafail-411rc1.txt]
>  
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10246) VM HA issues

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10246:
-

borisstoyanov commented on issue #2474: CLOUDSTACK-10246 Fix Host HA and VM HA 
issues
URL: https://github.com/apache/cloudstack/pull/2474#issuecomment-370900571
 
 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> VM HA issues
> 
>
> Key: CLOUDSTACK-10246
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10246
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
> Environment: My setup is CentOS 7 Management server with 3 CentOS 7 
> KVM HVs, NFS as primary and secondary storages.
>Reporter: Nux
>Priority: Major
>
> VM HA fails to kick in when one of the hypervisors goes down.
> It even fails to restart the system VMs which remain down along with the 
> instances until the affected HV comes back online.
> When I crash or power off the HV the system marks it in the hosts list as 
> "Alert" or "Disconnected" respectively. It should get changed to "Down" after 
> that, but this never happens.
>  
> I have tried various combinations of setups (Adv, Basic), none succeeded.
>  
> My instances use HA enabled offerings.
> Management server DEBUG logs here:
> [http://tmp.nux.ro/CW4-vmhafail-411rc1.txt]
>  
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10314) Add Text-Field to each ACL Rule

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10314:
-

blueorangutan commented on issue #2475: [CLOUDSTACK-10314] Add Text-Field to 
each ACL Rule
URL: https://github.com/apache/cloudstack/pull/2475#issuecomment-370900482
 
 
   @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has 
been kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Add Text-Field to each ACL Rule 
> 
>
> Key: CLOUDSTACK-10314
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10314
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Minor
>
> It might be interesting to have a text field (e.g. CHAR-256) added to each 
> ACL rule, which allows to enter a "reason" for each FW Rule created. This is 
> valuable for customer documentation, as well as best practice for an evidence 
> towards auditing the system.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10314) Add Text-Field to each ACL Rule

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10314:
-

borisstoyanov commented on issue #2475: [CLOUDSTACK-10314] Add Text-Field to 
each ACL Rule
URL: https://github.com/apache/cloudstack/pull/2475#issuecomment-370900354
 
 
   @blueorangutan test


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Add Text-Field to each ACL Rule 
> 
>
> Key: CLOUDSTACK-10314
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10314
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Minor
>
> It might be interesting to have a text field (e.g. CHAR-256) added to each 
> ACL rule, which allows to enter a "reason" for each FW Rule created. This is 
> valuable for customer documentation, as well as best practice for an evidence 
> towards auditing the system.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-8855) Improve Error Message for Host Alert State

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-8855:


blueorangutan commented on issue #2387: CLOUDSTACK-8855 Improve Error Message 
for Host Alert State and reconnect host API.
URL: https://github.com/apache/cloudstack/pull/2387#issuecomment-370900489
 
 
   @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has 
been kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improve Error Message for Host Alert State
> --
>
> Key: CLOUDSTACK-8855
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8855
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.6.0
>Reporter: Bharat Kumar
>Assignee: Bharat Kumar
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-8855) Improve Error Message for Host Alert State

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-8855:


borisstoyanov commented on issue #2387: CLOUDSTACK-8855 Improve Error Message 
for Host Alert State and reconnect host API.
URL: https://github.com/apache/cloudstack/pull/2387#issuecomment-370900271
 
 
   @blueorangutan test


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improve Error Message for Host Alert State
> --
>
> Key: CLOUDSTACK-8855
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8855
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.6.0
>Reporter: Bharat Kumar
>Assignee: Bharat Kumar
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10317) In case of multiple-public ips, snat fails to work for addtional public nics/network for guest traffic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10317:
-

blueorangutan commented on issue #2476: CLOUDSTACK-10317: Fix SNAT rules for 
additional public nics
URL: https://github.com/apache/cloudstack/pull/2476#issuecomment-370881992
 
 
   Trillian test result (tid-2317)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 29943 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2476-t2317-kvm-centos7.zip
   Intermitten failure detected: /marvin/tests/smoke/test_outofbandmanagement.py
   Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
   Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py
   Smoke tests completed. 65 look OK, 2 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   test_02_vpc_privategw_static_routes | `Failure` | 186.17 | 
test_privategw_acl.py
   test_hostha_enable_ha_when_host_in_maintenance | `Error` | 1.75 | 
test_hostha_kvm.py
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> In case of multiple-public ips, snat fails to work for addtional public 
> nics/network for guest traffic
> --
>
> Key: CLOUDSTACK-10317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10317
> 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.12.0.0, 4.11.1.0
>
>
> If a VR has two+ public nics, traffic from guest VM fails to be NAT-ed 
> correctly for traffic towards additional public nics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10240) ACS cannot migrate a volume from local to shared storage (for XenServer)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10240:
-

rafaelweingartner commented on issue #2425: [CLOUDSTACK-10240] ACS cannot 
migrate a local volume to shared storage
URL: https://github.com/apache/cloudstack/pull/2425#issuecomment-370865982
 
 
   @khos2ow would you mind reviewing this PR?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> ACS cannot migrate a volume from local to shared storage (for XenServer)
> 
>
> Key: CLOUDSTACK-10240
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10240
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Major
>
> CloudStack is logically restricting the migration of local storages to shared 
> storage and vice versa. This restriction is a logical one and can be removed 
> for XenServer deployments. Therefore, we will enable migration of volumes 
> between local-shared storages in XenServers independently of their service 
> offering. This will work as an override mechanism to the disk offering used 
> by volumes. If administrators want to migrate local volumes to a shared 
> storage, they should be able to do so (the hypervisor already allows that). 
> The same the other way around.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10240) ACS cannot migrate a volume from local to shared storage (for XenServer)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10240:
-

rafaelweingartner commented on issue #2425: [CLOUDSTACK-10240] ACS cannot 
migrate a local volume to shared storage
URL: https://github.com/apache/cloudstack/pull/2425#issuecomment-370853345
 
 
   @DaanHoogland this test `test_hostha_enable_ha_when_host_in_maintenance` 
error seems to be persistent in other PRs as well. Can I consider that the 
tests finished successfully?
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> ACS cannot migrate a volume from local to shared storage (for XenServer)
> 
>
> Key: CLOUDSTACK-10240
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10240
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Major
>
> CloudStack is logically restricting the migration of local storages to shared 
> storage and vice versa. This restriction is a logical one and can be removed 
> for XenServer deployments. Therefore, we will enable migration of volumes 
> between local-shared storages in XenServers independently of their service 
> offering. This will work as an override mechanism to the disk offering used 
> by volumes. If administrators want to migrate local volumes to a shared 
> storage, they should be able to do so (the hypervisor already allows that). 
> The same the other way around.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10268) Fix and enhance package script

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10268:
-

khos2ow commented on issue #2433: CLOUDSTACK-10268: Fix and enhance package 
script
URL: https://github.com/apache/cloudstack/pull/2433#issuecomment-370843827
 
 
   @rafaelweingartner @DaanHoogland I did consider using 
`CloudstackVersion.java` but wanted to be less disruptive and keep 
`Version.java` alive, although it can easily be deleted in favor of 
CloudstackVersion because there are only a handful of places which use it.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Fix and enhance package script
> --
>
> Key: CLOUDSTACK-10268
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10268
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Reporter: Khosrow Moossavi
>Priority: Minor
> Fix For: 4.12.0.0
>
>
> * new flag `-T, --use-timestamp` to use `timestamp` when POM version contains 
> SNAPSHOT
>  ** in the final artifacts (jar) name
>  ** in the final package (rpm, deb) name
>  ** in `/etc/cloudstack-release` file of SystemVMs
>  ** in the Management Server > About dialog
>  * if there's a "branding" string in the POM version (e.g. 
> `x.y.z.a-NAME[-SNAPSHOT]`),  the branding name will be used in the final 
> generated pacakge name such as following:
>   ** `cloudstack-management-x.y.z.a-NAME.NUMBER.el7.centos.x86_64`
>  ** `cloudstack-management_x.y.z.a-NAME-NUMBER~xenial_all.deb`
>  * branding string can be overriden with newly added `-b, --brand` flag
>  * handle the new format version for VR version
>  * fix long opts (they were broken)
>  * tolerate and show a warning message for unrecognized flags
>  * usage help reformat



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10268) Fix and enhance package script

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10268:
-

rafaelweingartner commented on issue #2433: CLOUDSTACK-10268: Fix and enhance 
package script
URL: https://github.com/apache/cloudstack/pull/2433#issuecomment-370844139
 
 
   Please  do the honors and delete it :)


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Fix and enhance package script
> --
>
> Key: CLOUDSTACK-10268
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10268
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Reporter: Khosrow Moossavi
>Priority: Minor
> Fix For: 4.12.0.0
>
>
> * new flag `-T, --use-timestamp` to use `timestamp` when POM version contains 
> SNAPSHOT
>  ** in the final artifacts (jar) name
>  ** in the final package (rpm, deb) name
>  ** in `/etc/cloudstack-release` file of SystemVMs
>  ** in the Management Server > About dialog
>  * if there's a "branding" string in the POM version (e.g. 
> `x.y.z.a-NAME[-SNAPSHOT]`),  the branding name will be used in the final 
> generated pacakge name such as following:
>   ** `cloudstack-management-x.y.z.a-NAME.NUMBER.el7.centos.x86_64`
>  ** `cloudstack-management_x.y.z.a-NAME-NUMBER~xenial_all.deb`
>  * branding string can be overriden with newly added `-b, --brand` flag
>  * handle the new format version for VR version
>  * fix long opts (they were broken)
>  * tolerate and show a warning message for unrecognized flags
>  * usage help reformat



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10232) SystemVMs and VR to run as HVM on XenServer

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10232:
-

khos2ow commented on issue #2465: CLOUDSTACK-10232: SystemVMs and VR to run as 
HVM on XenServer
URL: https://github.com/apache/cloudstack/pull/2465#issuecomment-370840118
 
 
   @syed awesome, thanks!
   
   @pdion891 yes that's correct, it uses Debian 9 since 4.11. Would you say 
there will be a lot of difference - in terms of performance - between Debian 7 
and 9? In terms of functionality should be fine though.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> SystemVMs and VR to run as HVM on XenServer
> ---
>
> Key: CLOUDSTACK-10232
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10232
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM, Virtual Router, XenServer
>Affects Versions: 4.10.0.0, 4.9.3.0
>Reporter: Pierre-Luc Dion
>Priority: Major
>
> Following the recent Meltdown-Spectre security risk,one of the mitigation,as 
> of Jan 2018, for XenServer Hypervisor is to run Virtual-Machine in HVM mode.
> Currently SystemVMs and Virtual-Routers run as PV on XenServer and the eth0 
> is configured using {{/etc/init.d/cloud-early-config}} using grub params from 
> {{/proc/cmdline}}. When VM run as HVM, it is not possible to push initial 
> boot instruction via pygrub.
> Quick tests has been done using xenstore and it look like it would be 
> possible to send same initial boot instruction has pygrub but using xenstore 
> for HVM instances.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10317) In case of multiple-public ips, snat fails to work for addtional public nics/network for guest traffic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10317:
-

blueorangutan commented on issue #2476: CLOUDSTACK-10317: Fix SNAT rules for 
additional public nics
URL: https://github.com/apache/cloudstack/pull/2476#issuecomment-370836797
 
 
   @rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been 
kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> In case of multiple-public ips, snat fails to work for addtional public 
> nics/network for guest traffic
> --
>
> Key: CLOUDSTACK-10317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10317
> 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.12.0.0, 4.11.1.0
>
>
> If a VR has two+ public nics, traffic from guest VM fails to be NAT-ed 
> correctly for traffic towards additional public nics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10317) In case of multiple-public ips, snat fails to work for addtional public nics/network for guest traffic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10317:
-

rhtyd commented on issue #2476: CLOUDSTACK-10317: Fix SNAT rules for additional 
public nics
URL: https://github.com/apache/cloudstack/pull/2476#issuecomment-370836631
 
 
   @blueorangutan test 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> In case of multiple-public ips, snat fails to work for addtional public 
> nics/network for guest traffic
> --
>
> Key: CLOUDSTACK-10317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10317
> 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.12.0.0, 4.11.1.0
>
>
> If a VR has two+ public nics, traffic from guest VM fails to be NAT-ed 
> correctly for traffic towards additional public nics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10317) In case of multiple-public ips, snat fails to work for addtional public nics/network for guest traffic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10317:
-

blueorangutan commented on issue #2476: CLOUDSTACK-10317: Fix SNAT rules for 
additional public nics
URL: https://github.com/apache/cloudstack/pull/2476#issuecomment-370833080
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1761


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> In case of multiple-public ips, snat fails to work for addtional public 
> nics/network for guest traffic
> --
>
> Key: CLOUDSTACK-10317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10317
> 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.12.0.0, 4.11.1.0
>
>
> If a VR has two+ public nics, traffic from guest VM fails to be NAT-ed 
> correctly for traffic towards additional public nics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10311) Agent Log Rotate variable replace bug

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10311:
-

blueorangutan commented on issue #2471: CLOUDSTACK-10311 Agent Log Rotate 
variable replace bug
URL: https://github.com/apache/cloudstack/pull/2471#issuecomment-370819910
 
 
   Packaging result: ✔centos6 ✔centos7 ✖debian. JID-1757


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Agent Log Rotate variable replace bug
> -
>
> Key: CLOUDSTACK-10311
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10311
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.10.0.0, 4.9.3.0
>Reporter: Sean Lair
>Priority: Major
>
> The cloudstack-agent was modified to use the @AGENTLOG@ variable entry, but 
> the pom.xml file was not correct to do the replacement of the @AGENTLOG@.
> {{@AGENTLOG@}}
> {{/var/log/cloudstack/agent/security_group.log}}
> {{{}}
> {{ copytruncate}}
> {{ daily}}
> {{ rotate 5}}
> {{ compress}}
> {{ missingok}}
> {{}}}
> PR coming



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-8855) Improve Error Message for Host Alert State

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-8855:


blueorangutan commented on issue #2387: CLOUDSTACK-8855 Improve Error Message 
for Host Alert State and reconnect host API.
URL: https://github.com/apache/cloudstack/pull/2387#issuecomment-370819925
 
 
   Packaging result: ✔centos6 ✔centos7 ✖debian. JID-1760


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improve Error Message for Host Alert State
> --
>
> Key: CLOUDSTACK-8855
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8855
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.6.0
>Reporter: Bharat Kumar
>Assignee: Bharat Kumar
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10314) Add Text-Field to each ACL Rule

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10314:
-

blueorangutan commented on issue #2475: [CLOUDSTACK-10314] Add Text-Field to 
each ACL Rule
URL: https://github.com/apache/cloudstack/pull/2475#issuecomment-370819912
 
 
   Packaging result: ✔centos6 ✔centos7 ✖debian. JID-1758


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Add Text-Field to each ACL Rule 
> 
>
> Key: CLOUDSTACK-10314
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10314
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Minor
>
> It might be interesting to have a text field (e.g. CHAR-256) added to each 
> ACL rule, which allows to enter a "reason" for each FW Rule created. This is 
> valuable for customer documentation, as well as best practice for an evidence 
> towards auditing the system.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10246) VM HA issues

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10246:
-

blueorangutan commented on issue #2474: CLOUDSTACK-10246 Fix Host HA and VM HA 
issues
URL: https://github.com/apache/cloudstack/pull/2474#issuecomment-370819917
 
 
   Packaging result: ✔centos6 ✖centos7 ✖debian. JID-1759


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> VM HA issues
> 
>
> Key: CLOUDSTACK-10246
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10246
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
> Environment: My setup is CentOS 7 Management server with 3 CentOS 7 
> KVM HVs, NFS as primary and secondary storages.
>Reporter: Nux
>Priority: Major
>
> VM HA fails to kick in when one of the hypervisors goes down.
> It even fails to restart the system VMs which remain down along with the 
> instances until the affected HV comes back online.
> When I crash or power off the HV the system marks it in the hosts list as 
> "Alert" or "Disconnected" respectively. It should get changed to "Down" after 
> that, but this never happens.
>  
> I have tried various combinations of setups (Adv, Basic), none succeeded.
>  
> My instances use HA enabled offerings.
> Management server DEBUG logs here:
> [http://tmp.nux.ro/CW4-vmhafail-411rc1.txt]
>  
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10317) In case of multiple-public ips, snat fails to work for addtional public nics/network for guest traffic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10317:
-

DagSonsteboSB commented on a change in pull request #2476: CLOUDSTACK-10317: 
Fix SNAT rules for additional public nics
URL: https://github.com/apache/cloudstack/pull/2476#discussion_r172553658
 
 

 ##
 File path: systemvm/debian/opt/cloud/bin/cs/CsAddress.py
 ##
 @@ -388,7 +388,7 @@ def fw_router(self):
 self.fw.append(["mangle", "",
 "-A VPN_%s -j RETURN" % self.address['public_ip']])
 self.fw.append(["nat", "",
-"-A POSTROUTING -o eth2 -j SNAT --to-source %s" % 
self.address['public_ip']])
+"-A POSTROUTING -o %s -j SNAT --to-source %s" % 
(self.dev, self.address['public_ip'])])
 
 Review comment:
   You are right @ustcweizhou - just tested this. Routing happens *after SNAT* 
hence translating all non-static NATed traffic to the source IP address on eth2 
works even if this means a SNAT rule against eth3, eth4, etc.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> In case of multiple-public ips, snat fails to work for addtional public 
> nics/network for guest traffic
> --
>
> Key: CLOUDSTACK-10317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10317
> 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.12.0.0, 4.11.1.0
>
>
> If a VR has two+ public nics, traffic from guest VM fails to be NAT-ed 
> correctly for traffic towards additional public nics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10317) In case of multiple-public ips, snat fails to work for addtional public nics/network for guest traffic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10317:
-

rhtyd commented on issue #2476: CLOUDSTACK-10317: Fix SNAT rules for additional 
public nics
URL: https://github.com/apache/cloudstack/pull/2476#issuecomment-370818736
 
 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> In case of multiple-public ips, snat fails to work for addtional public 
> nics/network for guest traffic
> --
>
> Key: CLOUDSTACK-10317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10317
> 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.12.0.0, 4.11.1.0
>
>
> If a VR has two+ public nics, traffic from guest VM fails to be NAT-ed 
> correctly for traffic towards additional public nics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10317) In case of multiple-public ips, snat fails to work for addtional public nics/network for guest traffic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10317:
-

rhtyd commented on a change in pull request #2476: CLOUDSTACK-10317: Fix SNAT 
rules for additional public nics
URL: https://github.com/apache/cloudstack/pull/2476#discussion_r172553142
 
 

 ##
 File path: systemvm/debian/opt/cloud/bin/cs/CsAddress.py
 ##
 @@ -388,7 +388,7 @@ def fw_router(self):
 self.fw.append(["mangle", "",
 "-A VPN_%s -j RETURN" % self.address['public_ip']])
 self.fw.append(["nat", "",
-"-A POSTROUTING -o eth2 -j SNAT --to-source %s" % 
self.address['public_ip']])
+"-A POSTROUTING -o %s -j SNAT --to-source %s" % 
(self.dev, self.address['public_ip'])])
 
 Review comment:
   Thanks all for your discussion and testing, I'll test @ustcweizhou 's fix 
now.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> In case of multiple-public ips, snat fails to work for addtional public 
> nics/network for guest traffic
> --
>
> Key: CLOUDSTACK-10317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10317
> 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.12.0.0, 4.11.1.0
>
>
> If a VR has two+ public nics, traffic from guest VM fails to be NAT-ed 
> correctly for traffic towards additional public nics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10317) In case of multiple-public ips, snat fails to work for addtional public nics/network for guest traffic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10317:
-

blueorangutan commented on issue #2476: CLOUDSTACK-10317: Fix SNAT rules for 
additional public nics
URL: https://github.com/apache/cloudstack/pull/2476#issuecomment-370818984
 
 
   @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted 
as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> In case of multiple-public ips, snat fails to work for addtional public 
> nics/network for guest traffic
> --
>
> Key: CLOUDSTACK-10317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10317
> 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.12.0.0, 4.11.1.0
>
>
> If a VR has two+ public nics, traffic from guest VM fails to be NAT-ed 
> correctly for traffic towards additional public nics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10232) SystemVMs and VR to run as HVM on XenServer

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10232:
-

pdion891 commented on issue #2465: CLOUDSTACK-10232: SystemVMs and VR to run as 
HVM on XenServer
URL: https://github.com/apache/cloudstack/pull/2465#issuecomment-370807868
 
 
   @rafaelweingartner  for the load test, I want to make sure that on a heavily 
loaded xenserver, will not affect data availability from xenstore at the 
creation of a VR. We are also running some benchmark on the VR between HVM and 
PV to see if moving to HVM will improve VR performance.
   
   @khos2ow,  in 4.11 systemvm is using Debian 9 correct ? if so, it's not what 
we are currently testing, we are currently focusing on the 4.10 template Debian 
7


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> SystemVMs and VR to run as HVM on XenServer
> ---
>
> Key: CLOUDSTACK-10232
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10232
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM, Virtual Router, XenServer
>Affects Versions: 4.10.0.0, 4.9.3.0
>Reporter: Pierre-Luc Dion
>Priority: Major
>
> Following the recent Meltdown-Spectre security risk,one of the mitigation,as 
> of Jan 2018, for XenServer Hypervisor is to run Virtual-Machine in HVM mode.
> Currently SystemVMs and Virtual-Routers run as PV on XenServer and the eth0 
> is configured using {{/etc/init.d/cloud-early-config}} using grub params from 
> {{/proc/cmdline}}. When VM run as HVM, it is not possible to push initial 
> boot instruction via pygrub.
> Quick tests has been done using xenstore and it look like it would be 
> possible to send same initial boot instruction has pygrub but using xenstore 
> for HVM instances.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10317) In case of multiple-public ips, snat fails to work for addtional public nics/network for guest traffic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10317:
-

ustcweizhou commented on a change in pull request #2476: CLOUDSTACK-10317: Fix 
SNAT rules for additional public nics
URL: https://github.com/apache/cloudstack/pull/2476#discussion_r172535132
 
 

 ##
 File path: systemvm/debian/opt/cloud/bin/cs/CsAddress.py
 ##
 @@ -388,7 +388,7 @@ def fw_router(self):
 self.fw.append(["mangle", "",
 "-A VPN_%s -j RETURN" % self.address['public_ip']])
 self.fw.append(["nat", "",
-"-A POSTROUTING -o eth2 -j SNAT --to-source %s" % 
self.address['public_ip']])
+"-A POSTROUTING -o %s -j SNAT --to-source %s" % 
(self.dev, self.address['public_ip'])])
 
 Review comment:
   @DagSonsteboSB yes, I think the outgoing IP for the vms without static nat 
should be the source nat IP, in your example 10.100.1.10
   
   In my point of view, the rules applied on ethernet other than eth2 (for 
example eth3) are not needed at all, however it is not harmful to have them. 
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> In case of multiple-public ips, snat fails to work for addtional public 
> nics/network for guest traffic
> --
>
> Key: CLOUDSTACK-10317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10317
> 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.12.0.0, 4.11.1.0
>
>
> If a VR has two+ public nics, traffic from guest VM fails to be NAT-ed 
> correctly for traffic towards additional public nics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10317) In case of multiple-public ips, snat fails to work for addtional public nics/network for guest traffic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10317:
-

DagSonsteboSB commented on a change in pull request #2476: CLOUDSTACK-10317: 
Fix SNAT rules for additional public nics
URL: https://github.com/apache/cloudstack/pull/2476#discussion_r172526560
 
 

 ##
 File path: systemvm/debian/opt/cloud/bin/cs/CsAddress.py
 ##
 @@ -388,7 +388,7 @@ def fw_router(self):
 self.fw.append(["mangle", "",
 "-A VPN_%s -j RETURN" % self.address['public_ip']])
 self.fw.append(["nat", "",
-"-A POSTROUTING -o eth2 -j SNAT --to-source %s" % 
self.address['public_ip']])
+"-A POSTROUTING -o %s -j SNAT --to-source %s" % 
(self.dev, self.address['public_ip'])])
 
 Review comment:
   Hi @ustcweizhou - in your scenario - does this not mean you end up SNATing 
on the wrong interface? So lets say you have eth2/VLAN10/10.100.1.10/24 and 
eth3/VLAN20/10.100.2.20/24. With your method that would SNAT to
   
   - A POSTROUTING -o eth3 -j SNAT --to-source 10.100.1.10
   
   So in other words the IP address would be right for the initial source NAT, 
but it would end up being translated on the wrong interface?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> In case of multiple-public ips, snat fails to work for addtional public 
> nics/network for guest traffic
> --
>
> Key: CLOUDSTACK-10317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10317
> 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.12.0.0, 4.11.1.0
>
>
> If a VR has two+ public nics, traffic from guest VM fails to be NAT-ed 
> correctly for traffic towards additional public nics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-8855) Improve Error Message for Host Alert State

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-8855:


blueorangutan commented on issue #2387: CLOUDSTACK-8855 Improve Error Message 
for Host Alert State and reconnect host API.
URL: https://github.com/apache/cloudstack/pull/2387#issuecomment-370791841
 
 
   @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep 
you posted as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improve Error Message for Host Alert State
> --
>
> Key: CLOUDSTACK-8855
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8855
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.6.0
>Reporter: Bharat Kumar
>Assignee: Bharat Kumar
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-8855) Improve Error Message for Host Alert State

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-8855:


borisstoyanov commented on issue #2387: CLOUDSTACK-8855 Improve Error Message 
for Host Alert State and reconnect host API.
URL: https://github.com/apache/cloudstack/pull/2387#issuecomment-370791497
 
 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improve Error Message for Host Alert State
> --
>
> Key: CLOUDSTACK-8855
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8855
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.6.0
>Reporter: Bharat Kumar
>Assignee: Bharat Kumar
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10246) VM HA issues

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10246:
-

borisstoyanov commented on issue #2474: CLOUDSTACK-10246 Fix Host HA and VM HA 
issues
URL: https://github.com/apache/cloudstack/pull/2474#issuecomment-370788754
 
 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> VM HA issues
> 
>
> Key: CLOUDSTACK-10246
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10246
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
> Environment: My setup is CentOS 7 Management server with 3 CentOS 7 
> KVM HVs, NFS as primary and secondary storages.
>Reporter: Nux
>Priority: Major
>
> VM HA fails to kick in when one of the hypervisors goes down.
> It even fails to restart the system VMs which remain down along with the 
> instances until the affected HV comes back online.
> When I crash or power off the HV the system marks it in the hosts list as 
> "Alert" or "Disconnected" respectively. It should get changed to "Down" after 
> that, but this never happens.
>  
> I have tried various combinations of setups (Adv, Basic), none succeeded.
>  
> My instances use HA enabled offerings.
> Management server DEBUG logs here:
> [http://tmp.nux.ro/CW4-vmhafail-411rc1.txt]
>  
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10246) VM HA issues

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10246:
-

borisstoyanov commented on issue #2474: CLOUDSTACK-10246 Fix Host HA and VM HA 
issues
URL: https://github.com/apache/cloudstack/pull/2474#issuecomment-370791081
 
 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> VM HA issues
> 
>
> Key: CLOUDSTACK-10246
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10246
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
> Environment: My setup is CentOS 7 Management server with 3 CentOS 7 
> KVM HVs, NFS as primary and secondary storages.
>Reporter: Nux
>Priority: Major
>
> VM HA fails to kick in when one of the hypervisors goes down.
> It even fails to restart the system VMs which remain down along with the 
> instances until the affected HV comes back online.
> When I crash or power off the HV the system marks it in the hosts list as 
> "Alert" or "Disconnected" respectively. It should get changed to "Down" after 
> that, but this never happens.
>  
> I have tried various combinations of setups (Adv, Basic), none succeeded.
>  
> My instances use HA enabled offerings.
> Management server DEBUG logs here:
> [http://tmp.nux.ro/CW4-vmhafail-411rc1.txt]
>  
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10246) VM HA issues

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10246:
-

blueorangutan commented on issue #2474: CLOUDSTACK-10246 Fix Host HA and VM HA 
issues
URL: https://github.com/apache/cloudstack/pull/2474#issuecomment-370791279
 
 
   @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep 
you posted as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> VM HA issues
> 
>
> Key: CLOUDSTACK-10246
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10246
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
> Environment: My setup is CentOS 7 Management server with 3 CentOS 7 
> KVM HVs, NFS as primary and secondary storages.
>Reporter: Nux
>Priority: Major
>
> VM HA fails to kick in when one of the hypervisors goes down.
> It even fails to restart the system VMs which remain down along with the 
> instances until the affected HV comes back online.
> When I crash or power off the HV the system marks it in the hosts list as 
> "Alert" or "Disconnected" respectively. It should get changed to "Down" after 
> that, but this never happens.
>  
> I have tried various combinations of setups (Adv, Basic), none succeeded.
>  
> My instances use HA enabled offerings.
> Management server DEBUG logs here:
> [http://tmp.nux.ro/CW4-vmhafail-411rc1.txt]
>  
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-8855) Improve Error Message for Host Alert State

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-8855:


rafaelweingartner commented on issue #2387: CLOUDSTACK-8855 Improve Error 
Message for Host Alert State and reconnect host API.
URL: https://github.com/apache/cloudstack/pull/2387#issuecomment-370789719
 
 
   @borisstoyanov could you run tests here?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Improve Error Message for Host Alert State
> --
>
> Key: CLOUDSTACK-8855
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8855
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.6.0
>Reporter: Bharat Kumar
>Assignee: Bharat Kumar
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10246) VM HA issues

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10246:
-

borisstoyanov commented on issue #2474: CLOUDSTACK-10246 Fix Host HA and VM HA 
issues
URL: https://github.com/apache/cloudstack/pull/2474#issuecomment-370789130
 
 
   @Slair1 what issues are fixed, do we have marvin tests for them? If not I 
think it'll be good to add them.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> VM HA issues
> 
>
> Key: CLOUDSTACK-10246
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10246
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
> Environment: My setup is CentOS 7 Management server with 3 CentOS 7 
> KVM HVs, NFS as primary and secondary storages.
>Reporter: Nux
>Priority: Major
>
> VM HA fails to kick in when one of the hypervisors goes down.
> It even fails to restart the system VMs which remain down along with the 
> instances until the affected HV comes back online.
> When I crash or power off the HV the system marks it in the hosts list as 
> "Alert" or "Disconnected" respectively. It should get changed to "Down" after 
> that, but this never happens.
>  
> I have tried various combinations of setups (Adv, Basic), none succeeded.
>  
> My instances use HA enabled offerings.
> Management server DEBUG logs here:
> [http://tmp.nux.ro/CW4-vmhafail-411rc1.txt]
>  
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10274) L2 network refused to be designed on VXLAN physical network

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10274:
-

rhtyd closed pull request #2448: CLOUDSTACK-10274: L2 network refused to be 
designed on VXLAN physical network
URL: https://github.com/apache/cloudstack/pull/2448
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/plugins/network-elements/vxlan/src/com/cloud/network/guru/VxlanGuestNetworkGuru.java
 
b/plugins/network-elements/vxlan/src/com/cloud/network/guru/VxlanGuestNetworkGuru.java
index c065bd191d0..35f588fd567 100644
--- 
a/plugins/network-elements/vxlan/src/com/cloud/network/guru/VxlanGuestNetworkGuru.java
+++ 
b/plugins/network-elements/vxlan/src/com/cloud/network/guru/VxlanGuestNetworkGuru.java
@@ -55,11 +55,12 @@ public VxlanGuestNetworkGuru() {
 @Override
 protected boolean canHandle(NetworkOffering offering, final NetworkType 
networkType, final PhysicalNetwork physicalNetwork) {
 // This guru handles only Guest Isolated network that supports Source 
nat service
-if (networkType == NetworkType.Advanced && 
isMyTrafficType(offering.getTrafficType()) && offering.getGuestType() == 
Network.GuestType.Isolated &&
-isMyIsolationMethod(physicalNetwork)) {
+if (networkType == NetworkType.Advanced && 
isMyTrafficType(offering.getTrafficType()) &&
+(offering.getGuestType() == Network.GuestType.Isolated || 
offering.getGuestType() == Network.GuestType.L2) &&
+isMyIsolationMethod(physicalNetwork)) {
 return true;
 } else {
-s_logger.trace("We only take care of Guest networks of type   " + 
GuestType.Isolated + " in zone of type " + NetworkType.Advanced);
+s_logger.trace("We only take care of Guest networks of type   " + 
GuestType.Isolated + " or " + GuestType.L2 + " in zone of type " + 
NetworkType.Advanced);
 return false;
 }
 }
@@ -72,6 +73,10 @@ public Network design(NetworkOffering offering, 
DeploymentPlan plan, Network use
 return null;
 }
 
+if (offering.getGuestType() == GuestType.L2 && 
network.getBroadcastUri() != null) {
+String vxlan = 
BroadcastDomainType.getValue(network.getBroadcastUri());
+network.setBroadcastUri(BroadcastDomainType.Vxlan.toUri(vxlan));
+}
 network.setBroadcastDomainType(BroadcastDomainType.Vxlan);
 
 return network;


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> L2 network refused to be designed on VXLAN physical network 
> 
>
> Key: CLOUDSTACK-10274
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10274
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Priority: Major
> Fix For: 4.11.1.1
>
>
> Issue reported by [~nuxro] while trying to add an L2 network on a VXLAN 
> physical network:
> 2018-02-06 11:20:27,748 DEBUG [c.c.n.NetworkServiceImpl] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found physical 
> network id=201 based on requested tags mellanoxvxlan
> 2018-02-06 11:20:27,749 DEBUG [c.c.n.NetworkServiceImpl] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found physical 
> network id=201 based on requested tags mellanoxvxlan
> 2018-02-06 11:20:27,766 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design this network, the physical isolation type is not BCF_SEGMENT
> 2018-02-06 11:20:27,766 DEBUG [o.a.c.n.c.m.ContrailGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design this network
> 2018-02-06 11:20:27,767 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design this network
> 2018-02-06 11:20:27,767 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design this network
> 2018-02-06 11:20:27,767 DEBUG [c.c.n.g.OvsGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 

[jira] [Commented] (CLOUDSTACK-10246) VM HA issues

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10246:
-

borisstoyanov commented on issue #2474: CLOUDSTACK-10246 Fix Host HA and VM HA 
issues
URL: https://github.com/apache/cloudstack/pull/2474#issuecomment-370788754
 
 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> VM HA issues
> 
>
> Key: CLOUDSTACK-10246
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10246
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
> Environment: My setup is CentOS 7 Management server with 3 CentOS 7 
> KVM HVs, NFS as primary and secondary storages.
>Reporter: Nux
>Priority: Major
>
> VM HA fails to kick in when one of the hypervisors goes down.
> It even fails to restart the system VMs which remain down along with the 
> instances until the affected HV comes back online.
> When I crash or power off the HV the system marks it in the hosts list as 
> "Alert" or "Disconnected" respectively. It should get changed to "Down" after 
> that, but this never happens.
>  
> I have tried various combinations of setups (Adv, Basic), none succeeded.
>  
> My instances use HA enabled offerings.
> Management server DEBUG logs here:
> [http://tmp.nux.ro/CW4-vmhafail-411rc1.txt]
>  
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10314) Add Text-Field to each ACL Rule

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10314:
-

blueorangutan commented on issue #2475: [CLOUDSTACK-10314] Add Text-Field to 
each ACL Rule
URL: https://github.com/apache/cloudstack/pull/2475#issuecomment-370788514
 
 
   @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep 
you posted as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Add Text-Field to each ACL Rule 
> 
>
> Key: CLOUDSTACK-10314
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10314
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Minor
>
> It might be interesting to have a text field (e.g. CHAR-256) added to each 
> ACL rule, which allows to enter a "reason" for each FW Rule created. This is 
> valuable for customer documentation, as well as best practice for an evidence 
> towards auditing the system.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10314) Add Text-Field to each ACL Rule

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10314:
-

borisstoyanov commented on issue #2475: [CLOUDSTACK-10314] Add Text-Field to 
each ACL Rule
URL: https://github.com/apache/cloudstack/pull/2475#issuecomment-370788388
 
 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Add Text-Field to each ACL Rule 
> 
>
> Key: CLOUDSTACK-10314
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10314
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Minor
>
> It might be interesting to have a text field (e.g. CHAR-256) added to each 
> ACL rule, which allows to enter a "reason" for each FW Rule created. This is 
> valuable for customer documentation, as well as best practice for an evidence 
> towards auditing the system.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10311) Agent Log Rotate variable replace bug

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10311:
-

blueorangutan commented on issue #2471: CLOUDSTACK-10311 Agent Log Rotate 
variable replace bug
URL: https://github.com/apache/cloudstack/pull/2471#issuecomment-370788209
 
 
   @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep 
you posted as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Agent Log Rotate variable replace bug
> -
>
> Key: CLOUDSTACK-10311
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10311
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.10.0.0, 4.9.3.0
>Reporter: Sean Lair
>Priority: Major
>
> The cloudstack-agent was modified to use the @AGENTLOG@ variable entry, but 
> the pom.xml file was not correct to do the replacement of the @AGENTLOG@.
> {{@AGENTLOG@}}
> {{/var/log/cloudstack/agent/security_group.log}}
> {{{}}
> {{ copytruncate}}
> {{ daily}}
> {{ rotate 5}}
> {{ compress}}
> {{ missingok}}
> {{}}}
> PR coming



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10311) Agent Log Rotate variable replace bug

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10311:
-

borisstoyanov commented on issue #2471: CLOUDSTACK-10311 Agent Log Rotate 
variable replace bug
URL: https://github.com/apache/cloudstack/pull/2471#issuecomment-370787915
 
 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Agent Log Rotate variable replace bug
> -
>
> Key: CLOUDSTACK-10311
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10311
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.10.0.0, 4.9.3.0
>Reporter: Sean Lair
>Priority: Major
>
> The cloudstack-agent was modified to use the @AGENTLOG@ variable entry, but 
> the pom.xml file was not correct to do the replacement of the @AGENTLOG@.
> {{@AGENTLOG@}}
> {{/var/log/cloudstack/agent/security_group.log}}
> {{{}}
> {{ copytruncate}}
> {{ daily}}
> {{ rotate 5}}
> {{ compress}}
> {{ missingok}}
> {{}}}
> PR coming



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10317) In case of multiple-public ips, snat fails to work for addtional public nics/network for guest traffic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10317:
-

rhtyd commented on a change in pull request #2476: CLOUDSTACK-10317: Fix SNAT 
rules for additional public nics
URL: https://github.com/apache/cloudstack/pull/2476#discussion_r172520624
 
 

 ##
 File path: systemvm/debian/opt/cloud/bin/cs/CsAddress.py
 ##
 @@ -388,7 +388,7 @@ def fw_router(self):
 self.fw.append(["mangle", "",
 "-A VPN_%s -j RETURN" % self.address['public_ip']])
 self.fw.append(["nat", "",
-"-A POSTROUTING -o eth2 -j SNAT --to-source %s" % 
self.address['public_ip']])
+"-A POSTROUTING -o %s -j SNAT --to-source %s" % 
(self.dev, self.address['public_ip'])])
 
 Review comment:
   Thanks for confirming that we indeed need to set the device/interface in the 
rule @ustcweizhou. I think it makes sense to have the default packets routed to 
the default public snat ip. I'll let others comment on it.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> In case of multiple-public ips, snat fails to work for addtional public 
> nics/network for guest traffic
> --
>
> Key: CLOUDSTACK-10317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10317
> 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.12.0.0, 4.11.1.0
>
>
> If a VR has two+ public nics, traffic from guest VM fails to be NAT-ed 
> correctly for traffic towards additional public nics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10317) In case of multiple-public ips, snat fails to work for addtional public nics/network for guest traffic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10317:
-

ustcweizhou commented on a change in pull request #2476: CLOUDSTACK-10317: Fix 
SNAT rules for additional public nics
URL: https://github.com/apache/cloudstack/pull/2476#discussion_r172464559
 
 

 ##
 File path: systemvm/debian/opt/cloud/bin/cs/CsAddress.py
 ##
 @@ -388,7 +388,7 @@ def fw_router(self):
 self.fw.append(["mangle", "",
 "-A VPN_%s -j RETURN" % self.address['public_ip']])
 self.fw.append(["nat", "",
-"-A POSTROUTING -o eth2 -j SNAT --to-source %s" % 
self.address['public_ip']])
+"-A POSTROUTING -o %s -j SNAT --to-source %s" % 
(self.dev, self.address['public_ip'])])
 
 Review comment:
   @rhtyd what we are using are
   ```
   diff --git a/systemvm/patches/debian/config/opt/cloud/bin/cs/CsAddress.py 
b/systemvm/patches/debian/config/opt/cloud/bin/cs/CsAddress.py
   index e6aea26..d336e0a 100755
   --- a/systemvm/patches/debian/config/opt/cloud/bin/cs/CsAddress.py
   +++ b/systemvm/patches/debian/config/opt/cloud/bin/cs/CsAddress.py
   @@ -400,7 +400,7 @@ class CsIP:
self.fw.append(["mangle", "",
"-A VPN_%s -j RETURN" % 
self.address['public_ip']])
self.fw.append(["nat", "",
   -"-A POSTROUTING -o eth2 -j SNAT --to-source %s" 
% self.address['public_ip']])
   +"-A POSTROUTING -o %s -j SNAT --to-source %s" % 
(self.dev, self.cl.get_eth2_ip())])
self.fw.append(["mangle", "",
"-A PREROUTING -i %s -m state --state NEW " % 
self.dev +
"-j CONNMARK --set-xmark %s/0x" % 
self.dnum])
   ```


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> In case of multiple-public ips, snat fails to work for addtional public 
> nics/network for guest traffic
> --
>
> Key: CLOUDSTACK-10317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10317
> 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.12.0.0, 4.11.1.0
>
>
> If a VR has two+ public nics, traffic from guest VM fails to be NAT-ed 
> correctly for traffic towards additional public nics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10318) Bug on sorting ACL rules list in chrome

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10318:
-

rafaelweingartner closed pull request #2478: [CLOUDSTACK-10318] Bug on sorting 
ACL rules list in chrome
URL: https://github.com/apache/cloudstack/pull/2478
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/ui/scripts/vpc.js b/ui/scripts/vpc.js
index 9dc8323e7cd..a77c4d7b585 100644
--- a/ui/scripts/vpc.js
+++ b/ui/scripts/vpc.js
@@ -1325,7 +1325,7 @@
 
 if(items){
 items.sort(function(a, 
b) {
-return a.number >= 
b.number;
+return a.number - 
b.number;
 }).map(function(acl) {
 if 
(parseInt(acl.protocol)) { // protocol number
 
acl.protocolnumber = acl.protocol;


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bug on sorting ACL rules list in chrome 
> 
>
> Key: CLOUDSTACK-10318
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10318
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Major
> Fix For: 4.12
>
>
> There is a bug on ACL rules list when a user creates more than 10 rules.
> #Steps to reproduce this issue
> - Create more than 10 ACL rules.
> - Access the ACL rules list page.
> - You will see that they are not sorted as they should by the ACL rule number



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (CLOUDSTACK-10318) Bug on sorting ACL rules list in chrome

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-10318.
-
Resolution: Fixed

> Bug on sorting ACL rules list in chrome 
> 
>
> Key: CLOUDSTACK-10318
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10318
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Major
> Fix For: 4.12
>
>
> There is a bug on ACL rules list when a user creates more than 10 rules.
> #Steps to reproduce this issue
> - Create more than 10 ACL rules.
> - Access the ACL rules list page.
> - You will see that they are not sorted as they should by the ACL rule number



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10318) Bug on sorting ACL rules list in chrome

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10318:
-

rafaelweingartner commented on issue #2478: [CLOUDSTACK-10318] Bug on sorting 
ACL rules list in chrome
URL: https://github.com/apache/cloudstack/pull/2478#issuecomment-370742768
 
 
   What happens there is that Google Chrome only sorts blocks of 10 elements 
when the sort function return Boolean values. To fix it, we need to return a 
numeric value indicating if the first object is smaller (-), equal (0), or (+) 
greater than the second one.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bug on sorting ACL rules list in chrome 
> 
>
> Key: CLOUDSTACK-10318
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10318
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Major
> Fix For: 4.12
>
>
> There is a bug on ACL rules list when a user creates more than 10 rules.
> #Steps to reproduce this issue
> - Create more than 10 ACL rules.
> - Access the ACL rules list page.
> - You will see that they are not sorted as they should by the ACL rule number



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10318) Bug on sorting ACL rules list in chrome

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10318:
-

rafaelweingartner commented on issue #2478: [CLOUDSTACK-10318] Bug on sorting 
ACL rules list in chrome
URL: https://github.com/apache/cloudstack/pull/2478#issuecomment-370742768
 
 
   What happens there is that Google Chrome only sorts blocks of 10 elements 
when the sort function returns Boolean values. To fix it, we need to return a 
numeric value indicating if the first object is smaller (-), equal (0), or (+) 
greater than the second one.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bug on sorting ACL rules list in chrome 
> 
>
> Key: CLOUDSTACK-10318
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10318
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Major
> Fix For: 4.12
>
>
> There is a bug on ACL rules list when a user creates more than 10 rules.
> #Steps to reproduce this issue
> - Create more than 10 ACL rules.
> - Access the ACL rules list page.
> - You will see that they are not sorted as they should by the ACL rule number



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10232) SystemVMs and VR to run as HVM on XenServer

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10232:
-

blueorangutan commented on issue #2465: CLOUDSTACK-10232: SystemVMs and VR to 
run as HVM on XenServer
URL: https://github.com/apache/cloudstack/pull/2465#issuecomment-370741679
 
 
   @DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has 
been kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> SystemVMs and VR to run as HVM on XenServer
> ---
>
> Key: CLOUDSTACK-10232
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10232
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM, Virtual Router, XenServer
>Affects Versions: 4.10.0.0, 4.9.3.0
>Reporter: Pierre-Luc Dion
>Priority: Major
>
> Following the recent Meltdown-Spectre security risk,one of the mitigation,as 
> of Jan 2018, for XenServer Hypervisor is to run Virtual-Machine in HVM mode.
> Currently SystemVMs and Virtual-Routers run as PV on XenServer and the eth0 
> is configured using {{/etc/init.d/cloud-early-config}} using grub params from 
> {{/proc/cmdline}}. When VM run as HVM, it is not possible to push initial 
> boot instruction via pygrub.
> Quick tests has been done using xenstore and it look like it would be 
> possible to send same initial boot instruction has pygrub but using xenstore 
> for HVM instances.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10232) SystemVMs and VR to run as HVM on XenServer

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10232:
-

DaanHoogland commented on issue #2465: CLOUDSTACK-10232: SystemVMs and VR to 
run as HVM on XenServer
URL: https://github.com/apache/cloudstack/pull/2465#issuecomment-370741614
 
 
   @blueorangutan test


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> SystemVMs and VR to run as HVM on XenServer
> ---
>
> Key: CLOUDSTACK-10232
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10232
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM, Virtual Router, XenServer
>Affects Versions: 4.10.0.0, 4.9.3.0
>Reporter: Pierre-Luc Dion
>Priority: Major
>
> Following the recent Meltdown-Spectre security risk,one of the mitigation,as 
> of Jan 2018, for XenServer Hypervisor is to run Virtual-Machine in HVM mode.
> Currently SystemVMs and Virtual-Routers run as PV on XenServer and the eth0 
> is configured using {{/etc/init.d/cloud-early-config}} using grub params from 
> {{/proc/cmdline}}. When VM run as HVM, it is not possible to push initial 
> boot instruction via pygrub.
> Quick tests has been done using xenstore and it look like it would be 
> possible to send same initial boot instruction has pygrub but using xenstore 
> for HVM instances.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10318) Bug on sorting ACL rules list in chrome

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10318:
-

rafaelweingartner commented on issue #2478: [CLOUDSTACK-10318] Bug on sorting 
ACL rules list in chrome
URL: https://github.com/apache/cloudstack/pull/2478#issuecomment-370741336
 
 
   Ok. there you go.
   Before:
   
![before](https://user-images.githubusercontent.com/4129005/37028279-9eb187ec-2112-11e8-8706-826678975dbe.png)
   
   After:
   
![after](https://user-images.githubusercontent.com/4129005/37028288-a343de4a-2112-11e8-848a-1223214b8d27.png)
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bug on sorting ACL rules list in chrome 
> 
>
> Key: CLOUDSTACK-10318
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10318
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Major
> Fix For: 4.12
>
>
> There is a bug on ACL rules list when a user creates more than 10 rules.
> #Steps to reproduce this issue
> - Create more than 10 ACL rules.
> - Access the ACL rules list page.
> - You will see that they are not sorted as they should by the ACL rule number



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10318) Bug on sorting ACL rules list in chrome

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10318:
-

borisstoyanov commented on issue #2478: [CLOUDSTACK-10318] Bug on sorting ACL 
rules list in chrome
URL: https://github.com/apache/cloudstack/pull/2478#issuecomment-370735062
 
 
   Thanks @rafaelweingartner, please show us what was the issue and how the fix 
looks. Since we don't require any test results on this, let us have some 
justification as screenshots please. 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bug on sorting ACL rules list in chrome 
> 
>
> Key: CLOUDSTACK-10318
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10318
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Major
> Fix For: 4.12
>
>
> There is a bug on ACL rules list when a user creates more than 10 rules.
> #Steps to reproduce this issue
> - Create more than 10 ACL rules.
> - Access the ACL rules list page.
> - You will see that they are not sorted as they should by the ACL rule number



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10268) Fix and enhance package script

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10268:
-

rafaelweingartner commented on issue #2433: CLOUDSTACK-10268: Fix and enhance 
package script
URL: https://github.com/apache/cloudstack/pull/2433#issuecomment-370733584
 
 
   Regarding the version thing
   @khos2ow what about deleting that `version.java` class and using only the 
"CloudStackVersion"? It is quite confusing having these two objects around.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Fix and enhance package script
> --
>
> Key: CLOUDSTACK-10268
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10268
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Reporter: Khosrow Moossavi
>Priority: Minor
> Fix For: 4.12.0.0
>
>
> * new flag `-T, --use-timestamp` to use `timestamp` when POM version contains 
> SNAPSHOT
>  ** in the final artifacts (jar) name
>  ** in the final package (rpm, deb) name
>  ** in `/etc/cloudstack-release` file of SystemVMs
>  ** in the Management Server > About dialog
>  * if there's a "branding" string in the POM version (e.g. 
> `x.y.z.a-NAME[-SNAPSHOT]`),  the branding name will be used in the final 
> generated pacakge name such as following:
>   ** `cloudstack-management-x.y.z.a-NAME.NUMBER.el7.centos.x86_64`
>  ** `cloudstack-management_x.y.z.a-NAME-NUMBER~xenial_all.deb`
>  * branding string can be overriden with newly added `-b, --brand` flag
>  * handle the new format version for VR version
>  * fix long opts (they were broken)
>  * tolerate and show a warning message for unrecognized flags
>  * usage help reformat



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10268) Fix and enhance package script

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10268:
-

rafaelweingartner commented on issue #2433: CLOUDSTACK-10268: Fix and enhance 
package script
URL: https://github.com/apache/cloudstack/pull/2433#issuecomment-370732885
 
 
   @khos2ow I will test the package generation in both centoOs7 and CentOs6. I 
see that @DaanHoogland already started some other tests, so this should cover 
if the changes in version check
   
   @DaanHoogland I do think unit-test cases are appreciated. If @khos2ow is 
willing to create them, it would be great.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Fix and enhance package script
> --
>
> Key: CLOUDSTACK-10268
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10268
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Reporter: Khosrow Moossavi
>Priority: Minor
> Fix For: 4.12.0.0
>
>
> * new flag `-T, --use-timestamp` to use `timestamp` when POM version contains 
> SNAPSHOT
>  ** in the final artifacts (jar) name
>  ** in the final package (rpm, deb) name
>  ** in `/etc/cloudstack-release` file of SystemVMs
>  ** in the Management Server > About dialog
>  * if there's a "branding" string in the POM version (e.g. 
> `x.y.z.a-NAME[-SNAPSHOT]`),  the branding name will be used in the final 
> generated pacakge name such as following:
>   ** `cloudstack-management-x.y.z.a-NAME.NUMBER.el7.centos.x86_64`
>  ** `cloudstack-management_x.y.z.a-NAME-NUMBER~xenial_all.deb`
>  * branding string can be overriden with newly added `-b, --brand` flag
>  * handle the new format version for VR version
>  * fix long opts (they were broken)
>  * tolerate and show a warning message for unrecognized flags
>  * usage help reformat



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10232) SystemVMs and VR to run as HVM on XenServer

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10232:
-

blueorangutan commented on issue #2465: CLOUDSTACK-10232: SystemVMs and VR to 
run as HVM on XenServer
URL: https://github.com/apache/cloudstack/pull/2465#issuecomment-370729272
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1755


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> SystemVMs and VR to run as HVM on XenServer
> ---
>
> Key: CLOUDSTACK-10232
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10232
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM, Virtual Router, XenServer
>Affects Versions: 4.10.0.0, 4.9.3.0
>Reporter: Pierre-Luc Dion
>Priority: Major
>
> Following the recent Meltdown-Spectre security risk,one of the mitigation,as 
> of Jan 2018, for XenServer Hypervisor is to run Virtual-Machine in HVM mode.
> Currently SystemVMs and Virtual-Routers run as PV on XenServer and the eth0 
> is configured using {{/etc/init.d/cloud-early-config}} using grub params from 
> {{/proc/cmdline}}. When VM run as HVM, it is not possible to push initial 
> boot instruction via pygrub.
> Quick tests has been done using xenstore and it look like it would be 
> possible to send same initial boot instruction has pygrub but using xenstore 
> for HVM instances.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10318) Bug on sorting ACL rules list in chrome

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10318:
-

rafaelweingartner commented on issue #2478: [CLOUDSTACK-10318] Bug on sorting 
ACL rules list in chrome
URL: https://github.com/apache/cloudstack/pull/2478#issuecomment-370728784
 
 
   I am not adding/removing anything in the UI. I am neither changing/replacing 
anything visible. I am only changing a sort function that was not following the 
standards, and that is why it was not working in chrome.
   
   I mean, the screenshot will not prove much. It is a static image. I can 
provide you with two images, one with the problem and other with the problem 
solved if you really think they are important.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bug on sorting ACL rules list in chrome 
> 
>
> Key: CLOUDSTACK-10318
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10318
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Major
> Fix For: 4.12
>
>
> There is a bug on ACL rules list when a user creates more than 10 rules.
> #Steps to reproduce this issue
> - Create more than 10 ACL rules.
> - Access the ACL rules list page.
> - You will see that they are not sorted as they should by the ACL rule number



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10317) In case of multiple-public ips, snat fails to work for addtional public nics/network for guest traffic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10317:
-

blueorangutan commented on issue #2476: CLOUDSTACK-10317: Fix SNAT rules for 
additional public nics
URL: https://github.com/apache/cloudstack/pull/2476#issuecomment-370723713
 
 
   @rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been 
kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> In case of multiple-public ips, snat fails to work for addtional public 
> nics/network for guest traffic
> --
>
> Key: CLOUDSTACK-10317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10317
> 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.12.0.0, 4.11.1.0
>
>
> If a VR has two+ public nics, traffic from guest VM fails to be NAT-ed 
> correctly for traffic towards additional public nics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10317) In case of multiple-public ips, snat fails to work for addtional public nics/network for guest traffic

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10317:
-

rhtyd commented on issue #2476: CLOUDSTACK-10317: Fix SNAT rules for additional 
public nics
URL: https://github.com/apache/cloudstack/pull/2476#issuecomment-370723519
 
 
   @blueorangutan test
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> In case of multiple-public ips, snat fails to work for addtional public 
> nics/network for guest traffic
> --
>
> Key: CLOUDSTACK-10317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10317
> 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.12.0.0, 4.11.1.0
>
>
> If a VR has two+ public nics, traffic from guest VM fails to be NAT-ed 
> correctly for traffic towards additional public nics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10232) SystemVMs and VR to run as HVM on XenServer

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10232:
-

blueorangutan commented on issue #2465: CLOUDSTACK-10232: SystemVMs and VR to 
run as HVM on XenServer
URL: https://github.com/apache/cloudstack/pull/2465#issuecomment-370718248
 
 
   @DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you 
posted as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> SystemVMs and VR to run as HVM on XenServer
> ---
>
> Key: CLOUDSTACK-10232
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10232
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM, Virtual Router, XenServer
>Affects Versions: 4.10.0.0, 4.9.3.0
>Reporter: Pierre-Luc Dion
>Priority: Major
>
> Following the recent Meltdown-Spectre security risk,one of the mitigation,as 
> of Jan 2018, for XenServer Hypervisor is to run Virtual-Machine in HVM mode.
> Currently SystemVMs and Virtual-Routers run as PV on XenServer and the eth0 
> is configured using {{/etc/init.d/cloud-early-config}} using grub params from 
> {{/proc/cmdline}}. When VM run as HVM, it is not possible to push initial 
> boot instruction via pygrub.
> Quick tests has been done using xenstore and it look like it would be 
> possible to send same initial boot instruction has pygrub but using xenstore 
> for HVM instances.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10232) SystemVMs and VR to run as HVM on XenServer

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10232:
-

DaanHoogland commented on issue #2465: CLOUDSTACK-10232: SystemVMs and VR to 
run as HVM on XenServer
URL: https://github.com/apache/cloudstack/pull/2465#issuecomment-370717962
 
 
   I see enough people have discussed this, so I am going to trust them and 
some tests ;)
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> SystemVMs and VR to run as HVM on XenServer
> ---
>
> Key: CLOUDSTACK-10232
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10232
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM, Virtual Router, XenServer
>Affects Versions: 4.10.0.0, 4.9.3.0
>Reporter: Pierre-Luc Dion
>Priority: Major
>
> Following the recent Meltdown-Spectre security risk,one of the mitigation,as 
> of Jan 2018, for XenServer Hypervisor is to run Virtual-Machine in HVM mode.
> Currently SystemVMs and Virtual-Routers run as PV on XenServer and the eth0 
> is configured using {{/etc/init.d/cloud-early-config}} using grub params from 
> {{/proc/cmdline}}. When VM run as HVM, it is not possible to push initial 
> boot instruction via pygrub.
> Quick tests has been done using xenstore and it look like it would be 
> possible to send same initial boot instruction has pygrub but using xenstore 
> for HVM instances.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10232) SystemVMs and VR to run as HVM on XenServer

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10232:
-

syed commented on issue #2465: CLOUDSTACK-10232: SystemVMs and VR to run as HVM 
on XenServer
URL: https://github.com/apache/cloudstack/pull/2465#issuecomment-370716576
 
 
   Yes I’m sure, unless that logic changed in the time since I last looked
   On Fri, Feb 23, 2018 at 11:10 AM Khosrow Moossavi 
   wrote:
   
   > @syed  are you sure? I don't think with only
   > systemvm.iso, cloud-early-config will be updated with new code.
   >
   > —
   > You are receiving this because you were mentioned.
   > Reply to this email directly, view it on GitHub
   > ,
   > or mute the thread
   > 

   > .
   >
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> SystemVMs and VR to run as HVM on XenServer
> ---
>
> Key: CLOUDSTACK-10232
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10232
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM, Virtual Router, XenServer
>Affects Versions: 4.10.0.0, 4.9.3.0
>Reporter: Pierre-Luc Dion
>Priority: Major
>
> Following the recent Meltdown-Spectre security risk,one of the mitigation,as 
> of Jan 2018, for XenServer Hypervisor is to run Virtual-Machine in HVM mode.
> Currently SystemVMs and Virtual-Routers run as PV on XenServer and the eth0 
> is configured using {{/etc/init.d/cloud-early-config}} using grub params from 
> {{/proc/cmdline}}. When VM run as HVM, it is not possible to push initial 
> boot instruction via pygrub.
> Quick tests has been done using xenstore and it look like it would be 
> possible to send same initial boot instruction has pygrub but using xenstore 
> for HVM instances.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10318) Bug on sorting ACL rules list in chrome

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10318:
-

borisstoyanov commented on issue #2478: [CLOUDSTACK-10318] Bug on sorting ACL 
rules list in chrome
URL: https://github.com/apache/cloudstack/pull/2478#issuecomment-370716105
 
 
   @rafaelweingartner can you upload some screenshots? Since it's a UI change I 
don't see point of running integration tests. 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Bug on sorting ACL rules list in chrome 
> 
>
> Key: CLOUDSTACK-10318
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10318
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Major
> Fix For: 4.12
>
>
> There is a bug on ACL rules list when a user creates more than 10 rules.
> #Steps to reproduce this issue
> - Create more than 10 ACL rules.
> - Access the ACL rules list page.
> - You will see that they are not sorted as they should by the ACL rule number



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10268) Fix and enhance package script

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10268:
-

blueorangutan commented on issue #2433: CLOUDSTACK-10268: Fix and enhance 
package script
URL: https://github.com/apache/cloudstack/pull/2433#issuecomment-370715381
 
 
   @DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has 
been kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Fix and enhance package script
> --
>
> Key: CLOUDSTACK-10268
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10268
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Reporter: Khosrow Moossavi
>Priority: Minor
> Fix For: 4.12.0.0
>
>
> * new flag `-T, --use-timestamp` to use `timestamp` when POM version contains 
> SNAPSHOT
>  ** in the final artifacts (jar) name
>  ** in the final package (rpm, deb) name
>  ** in `/etc/cloudstack-release` file of SystemVMs
>  ** in the Management Server > About dialog
>  * if there's a "branding" string in the POM version (e.g. 
> `x.y.z.a-NAME[-SNAPSHOT]`),  the branding name will be used in the final 
> generated pacakge name such as following:
>   ** `cloudstack-management-x.y.z.a-NAME.NUMBER.el7.centos.x86_64`
>  ** `cloudstack-management_x.y.z.a-NAME-NUMBER~xenial_all.deb`
>  * branding string can be overriden with newly added `-b, --brand` flag
>  * handle the new format version for VR version
>  * fix long opts (they were broken)
>  * tolerate and show a warning message for unrecognized flags
>  * usage help reformat



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10268) Fix and enhance package script

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10268:
-

DaanHoogland commented on issue #2433: CLOUDSTACK-10268: Fix and enhance 
package script
URL: https://github.com/apache/cloudstack/pull/2433#issuecomment-370715104
 
 
   good point @rafaelweingartner! @khos2ow can you add unit tests for the class.
   Please both note that there is a 'new' class called CloudStackVersion as 
well. Not sure if we should consider that in this work.
   @blueorangutan test


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Fix and enhance package script
> --
>
> Key: CLOUDSTACK-10268
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10268
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Reporter: Khosrow Moossavi
>Priority: Minor
> Fix For: 4.12.0.0
>
>
> * new flag `-T, --use-timestamp` to use `timestamp` when POM version contains 
> SNAPSHOT
>  ** in the final artifacts (jar) name
>  ** in the final package (rpm, deb) name
>  ** in `/etc/cloudstack-release` file of SystemVMs
>  ** in the Management Server > About dialog
>  * if there's a "branding" string in the POM version (e.g. 
> `x.y.z.a-NAME[-SNAPSHOT]`),  the branding name will be used in the final 
> generated pacakge name such as following:
>   ** `cloudstack-management-x.y.z.a-NAME.NUMBER.el7.centos.x86_64`
>  ** `cloudstack-management_x.y.z.a-NAME-NUMBER~xenial_all.deb`
>  * branding string can be overriden with newly added `-b, --brand` flag
>  * handle the new format version for VR version
>  * fix long opts (they were broken)
>  * tolerate and show a warning message for unrecognized flags
>  * usage help reformat



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10274) L2 network refused to be designed on VXLAN physical network

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10274:
-

NuxRo commented on issue #2448: CLOUDSTACK-10274: L2 network refused to be 
designed on VXLAN physical network
URL: https://github.com/apache/cloudstack/pull/2448#issuecomment-370699457
 
 
   @borisstoyanov Yes, I confirm this fixes my issues. Thanks


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> L2 network refused to be designed on VXLAN physical network 
> 
>
> Key: CLOUDSTACK-10274
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10274
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Priority: Major
> Fix For: 4.11.1.1
>
>
> Issue reported by [~nuxro] while trying to add an L2 network on a VXLAN 
> physical network:
> 2018-02-06 11:20:27,748 DEBUG [c.c.n.NetworkServiceImpl] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found physical 
> network id=201 based on requested tags mellanoxvxlan
> 2018-02-06 11:20:27,749 DEBUG [c.c.n.NetworkServiceImpl] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found physical 
> network id=201 based on requested tags mellanoxvxlan
> 2018-02-06 11:20:27,766 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design this network, the physical isolation type is not BCF_SEGMENT
> 2018-02-06 11:20:27,766 DEBUG [o.a.c.n.c.m.ContrailGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design this network
> 2018-02-06 11:20:27,767 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design this network
> 2018-02-06 11:20:27,767 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design this network
> 2018-02-06 11:20:27,767 DEBUG [c.c.n.g.OvsGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design this network
> 2018-02-06 11:20:27,769 DEBUG [o.a.c.n.g.SspGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) SSP not 
> configured to be active
> 2018-02-06 11:20:27,769 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design this network
> 2018-02-06 11:20:27,769 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design network using network offering 19 on physical network 201
> 2018-02-06 11:20:27,770 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Releasing lock 
> for Acct[6af2875b-04fc-11e8-923e-002590474525-admin]
> 2018-02-06 11:20:27,789 DEBUG [c.c.u.d.T.Transaction] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Rolling back 
> the transaction: Time = 38 Name =  qtp788117692-390; called by 
> -TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-TransactionLegacy.close:656-Transaction.execute:43-Transaction.execute:47-NetworkOrchestrator.createGuestNetwork:2315-NetworkServiceImpl$4.doInTransaction:1383-NetworkServiceImpl$4.doInTransaction:1331-Transaction.execute:40-NetworkServiceImpl.commitNetwork:1331-NetworkServiceImpl.createGuestNetwork:1294-NativeMethodAccessorImpl.invoke0:-2
> 2018-02-06 11:20:27,798 ERROR [c.c.a.ApiServer] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) unhandled 
> exception executing api command: [Ljava.lang.String;@43b9df02
> com.cloud.utils.exception.CloudRuntimeException: Unable to convert network 
> offering with specified id to network profile
>     at 
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.setupNetwork(NetworkOrchestrator.java:726)
>     at 
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransaction(NetworkOrchestrator.java:2364)
>     at 
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransaction(NetworkOrchestrator.java:2315)
>     at 
> com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:50)
>     at com.cloud.utils.db.Transaction.execute(Transaction.java:40)
>     at