[GitHub] cloudstack issue #1837: [4.9] Smoketest Health

2017-01-01 Thread rhtyd
Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1837
  
Component tests results:

https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1837-t732-kvm-centos7.zip

https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1837-t733-vmware-55u3.zip

https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1837-t734-xenserver-65sp1.zip


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] cloudstack pull request #1883: CLOUDSTACK-9723: Enable unique mac address ac...

2017-01-01 Thread jayapalu
GitHub user jayapalu opened a pull request:

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

CLOUDSTACK-9723: Enable unique mac address across the zones

Enable unique mac address across different deployments and networks.
If there two networks in two different deployment zones then this feature 
will avoid mac address collision.

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

$ git pull https://github.com/Accelerite/cloudstack uniqueMac

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

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

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

This closes #1883


commit c3f1ff9533fe8d433580dc13209b7bcf4020bc3a
Author: Jayapal 
Date:   2016-12-30T07:10:25Z

CLOUDSTACK-9723: Enable unique mac address across the zones




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---