Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/2044
@DaanHoogland Not for us since we still use link clones but I am sure tons
of other might be affected. Interestingly enough that with PR 1773 merged the
default behavior in API is not to allow
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/2044
@DaanHoogland Thanks. But for #1 the requirement for the code changes is
that the template is deleted from cloudstack. In this condition
restoreVirtualMachines when template ID is not specified
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/2044
@DaanHoogland Can you clarify few questions/concerns
1. This change will likely to break restoreVirtualMachine functions. At the
very least users should be able to turn off new behavior
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1762
@yvsubhash Please, take this up. So far this PR hasn't moved forward.
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/2043
LGTM on the code change.
@borisstoyanov @rhtyd @DaanHoogland Can we re-kick vmware test for this PR?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1836
@rhtyd @karuturi This is a new improvement introduced in PR1941 that
allows volume and VM snapshots to coexist. Now, test
test_01_test_vm_volume_snapshot in test_vm_snapshots.py needs
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@borisstoyanov Let's re-run vmware B.O test for this PR now
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/2002
LGTM on the code review. @borisstoyanov @rhtyd Can you kick off tests for
this PR?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@priyankparihar Fortunately those API are already written. As per PR1767
you can get VM details including rootdiskcontroller using listVirtualMachines
API and listTemplates.
So if we
Github user serg38 commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1813#discussion_r108580807
--- Diff: test/integration/smoke/test_deploy_vm_root_resize.py ---
@@ -114,36 +134,46 @@ def test_00_deploy_vm_root_resize(self):
# 2. root
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@borisstoyanov Can you also kick off vmware test in parallel?
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@cloudsadhu Thanks for the changes. LGTM on the code review. @borisstoyanov
@rhtyd @DaanHoogland Can you kick off another round of test for vmware and Xen
for this PR ?
---
If your project
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/2019
LGTM
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/2017
@SudharmaJain Isn't it duplicate to PR1613 that is already merged?
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1994
@nvazquez Looks like Travis cant SSH into management server during the test
.
2017-03-17 19:26:58,672 - DEBUG - mount -t nfs
nfs:/export/automation/1/testprimary
/mnt/marvin-1b4190cb
Github user serg38 commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1813#discussion_r105932339
--- Diff: test/integration/smoke/test_deploy_vm_root_resize.py ---
@@ -114,7 +114,13 @@ def test_00_deploy_vm_root_resize(self):
# 2. root
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/2002
@sudhansu7 Shouldn't we update POD id upon a successful migration? If
migration fails we will have wrong POD id in the DB.
---
If your project is set up for it, you can reply to this email
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1253
@sureshanaparti Why don't we just remove Config for this setting and leave
default to be 8?
Your logic to handle v4.1 will take care of old installations.
As of May 2016 Vsphere 4.X
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1257
@sureshanaparti I've been thinking if there is better way to re-sync all
portgroups and I couldn't come up with easy alternative. With that said if we
are copying portgroups for newly added host
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@sadhugit NFS supports root disk resize with full clones. I don't see any
restriction in the code and it actually works on Vmware no matter what kind of
underlying storage technology is used
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1994
@mike-tutkowski Can you test this fix in your environment?
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@priyankparihar I think we need to improve smoke test
test_deploy_vm_root_resize.py and introduce the logic you implemented in
component test test_rootvolume_resize.py.
We would want smoke
Github user serg38 commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1813#discussion_r105409367
--- Diff: test/integration/component/test_rootvolume_resize.py ---
@@ -0,0 +1,1140 @@
+# Licensed to the Apache Software Foundation (ASF) under one
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1994
@rhtyd @borisstoyanov Can you kick off new tests for this release blocker?
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@borisstoyanov @rhtyd Can you kick off new round of tests for this PR?
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1994
@nvazquez Is storage_tag_view still in use after this change that reference
old way of retrieving the tags? If not should we remove it? E.g. host tags
don't have a separate view.
---
If your
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1994
@nvazquez Should we simply replace storage_tag_view instead of switching
queries over to another view?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1994
@mike-tutkowski @karuturi @koushik-das @rafaelweingartner Please review
the fix for 4.10 blocker
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/793
@anshul1886 I am curious if there is a way to cancel stuck vmsnapshot jobs
without restarting management server. E.g. VM deployment go to error start upon
any failure in the process
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1774
LGTM
tag: mergeready
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1879
LGTM @nvazquez Can we test it with shared networking?
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1989
@abhinandanprateek I am curious if this PR will allow deploying VM with
Data disk attached?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1961
LGTM
tag:mergeready
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@borisstoyanov Thanks. Can you check in B.O. what is value of global
configuration 'vmware.create.full.clone', if the same configuration is set for
the primary storage pool and if so what
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1813
Still fails but error is different now
Exception: Job failed: {jobprocstatus : 0, created :
u'2017-03-03T09:20:53+', jobresult : {errorcode : 530, errortext : u'Unable
to start a VM due
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1961
@rhtyd @borisstoyanov did you have a chance to add nfs2 test data in B.O. ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@borisstoyanov Can you kick off B.O for Vmware again? Hopefully it will
pass.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1774
@borisstoyanov That would be awesome .
---
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
Github user serg38 commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1813#discussion_r103719599
--- Diff: server/src/com/cloud/vm/UserVmManagerImpl.java ---
@@ -3614,6 +3604,26 @@ public UserVmVO doInTransaction(TransactionStatus
status) throws
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@rhtyd @borisstoyanov @DaanHoogland Can we get B.O. management server log
to check why exception is generated?
---
If your project is set up for it, you can reply to this email and have your
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1773
Thanks @priyankparihar . We verified in our environment that all is working
fine including UI part.
LGTM
I think this one is
tag:mergeready
---
If your project is set up
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1935
@rhtyd @karuturi To fix errors in B.O in
test_02_list_snapshots_with_removed_data_store we need to merge PR1961 and then
adjust test_data on B.O side to have correct mapping for nfs2 label
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1935
@rafaelweingartner Can you review latest updates from @nvazquez . Since
tests are passing this PR will be ready for merging to 4.10
---
If your project is set up for it, you can reply
Github user serg38 commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1958#discussion_r102753237
--- Diff: server/src/com/cloud/configuration/ConfigurationManagerImpl.java
---
@@ -508,7 +507,7 @@ public String updateConfiguration(final long userId
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1941
@borisstoyanov @rhtyd Can we re-test this with B.O. ?
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1961
@karuturi I agree with @nvazquez . This PR can be safely merged and then
B.O. runtime environment needs to be adjusted to define nfs2 mountpoint in
test_data.py
---
If your project is set up
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1961
LGTM
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1847
@karuturi @anshul1886 Can we tweak line 278 of test_snaphsot.py from
self.services["nfs"],
to self.services["nfs2"],
and re-merge this PR so
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1773
@priyankparihar Well. API use cases can be recoded but not UI. Presently we
can delete templates in UI even with active VMs. With your changes there will
be no recourse. An easy option
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1773
@priyankparihar A part is still missing that will use forced option in UI
but give a user option to cancel deletion if active VMs exist
---
If your project is set up for it, you can reply
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1773
@jburwell That was default behavior for few years to allow deletion of the
template even if active VMs exist. Deletion of the template on secondary
doesn't remove the template copy on primary
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1768
@marcaurele I tend to agree with @rhtydthat it could break some of the
upgrades. If I get it right with your proposed changes, upgrade scripts become
obsolete since all the changes can be done
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1847
@nvazquez @rhtyd @anshul1886 We might need to tweak the test_data.py to add
additional nfs mount e.g. nfs1 and use it in this test. E.g adding
"nfs1": {
"u
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1773
@ustcweizhou @priyankparihar @borisstoyanov The default behavior was always
equivalent of force=true. We seem to agree that the UI behavior should remain
forced=true but with extra warning. We
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1773
@priyankparihar @ustcweizhou There seems to be just one case where it will
affect resetVM operations. If template is deleted and root disk is migrated to
another PS where there is no template
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1773
@priyankparihar I agree with @ustcweizhou . Default behavior should remain
forced. And in this case Web UI we should give a warning with "yes and no" if
template has deployed VM so
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@priyankparihar Resize test still fails on vmware. It is hard to see the
reason in blueorangutain output but you might want to make sure the test
provisioning uses full clones via setting
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1913
@karuturi This one is ready for merging. LGTM and test results are positive.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1913
LGTM
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@priyankparihar You need to adjust smoke test test_deploy_vm_root_resize.py
to support vmware root resize. Otherwise it will keep failing
2017-02-15 12:48:59,150 - CRITICAL - FAILED
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@borisstoyanov Looks like some environmental issues with backend NFS. Can
you kick it again for vmware ?
u'2017-02-15T20:21:38+', jobresult : {errorcode : 530, errortext :
u'Failed
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1727
@karuturi This one is ready for merging. Two LGTMs + tests passing on all 3
hypervisors
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/927
@karuturi
Smoke test test_internal_lb.py uses a value of
network.loadbalancer.haproxy.stats.auth which is encrypted for haproxy checks.
settings["username"]
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1727
@borisstoyanov @DaanHoogland @rhtyd KVM tests passed but key smoke test is
skipped
test_change_service_offering_for_vm_with_snapshots Skipped
To be on the safe side can we test
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1727
@DaanHoogland @borisstoyanov @rhtyd Guys can you kick off tests for this PR?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1747
@karuturi Test passed. Two LGTM received. Looks like it is ready for merging
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1747
LGTM
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1747
@rafaelweingartner Do we get you LGTM?
@DaanHoogland @rhtyd Can we kick off tests for this?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1747
@rafaelweingartner This PR is two fold.
1. This is something that was done a long ago for hosts and was never
implemented for storage. It transitions location of of storage tags over
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1767
LGTM
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1747
@rafaelweingartner Can you review this PR?
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1727
@koushik-das @rhtyd @rafaelweingartner Can you review changes @nvazquez
put in place? CI tests are good.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1727
LGTM
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1913
@rhtyd @karuturi Can we run vmware tests on this PR and merge on success ?
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1905
@rhtyd @karuturi Can we run tests on this PR and merge on success ?
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1767
@karuturi Can we merge this one ?
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1747
@rhtyd @karuturi Can we run tests on this PR and merge on success ?
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1727
@rhtyd @karuturi Can we run tests on this PR and merge on success ?
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1833
@pdumbre I confirm your observation. LGTM on code review.
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1711
Yes it is in 4.9.2.
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1727
@nvazquez Since 4.9.2 is already released and this is not a bugfix the DB
changes should go to schema-490to4910.sql
---
If your project is set up for it, you can reply to this email and have
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1888
We need to change one more setting for noredist build to work with updated
iControl version
in install-non-oss.sh
mvn install:install-file -Dfile=cloud-iControl.jar  Â
-DgroupId
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1901
Thanks @ustcweizhou LGTM for code review
---
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
Github user serg38 commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1901#discussion_r95828294
--- Diff:
api/src/org/apache/cloudstack/api/command/admin/domain/ListDomainsCmd.java ---
@@ -53,6 +59,12 @@
description = "I
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1735
@mike-tutkowski The only comments in this PR are about deletion of PS with
a snapshot copy. I am 100% agree with your statement. This PR excludes
destroyed snapshot copies including ones
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1747
@rhtyd Can you kick off tests fro this PR?
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1767
@rhtyd Can you kick off tests for this PR?
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1735
@mike-tutkowski @anshul1886 @rhtyd We had enough LGTM and successful test
results for this PR. Are there any concern before merging it?
---
If your project is set up for it, you can reply
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1727
@koushik-das @rhtyd This PR now supports custom service offerings. Can you
review and kick off tests?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1899
LGTM
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/977
@rhtyd @ustcweizhou We need to enable smoke tests for vmsnaphsots for KVM
in test_vm_snapshots.py
if cls.hypervisor.lower() in (KVM.lower(), "hyperv&q
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1847
@mike-tutkowski @anshul-gangwar @nvazquez I believe the same issue is
addressed in PR1735 but in a more consistent fashion
---
If your project is set up for it, you can reply to this email
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1876
LGTM
---
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
Github user serg38 closed the pull request at:
https://github.com/apache/cloudstack-www/pull/32
---
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
Github user serg38 closed the pull request at:
https://github.com/apache/cloudstack-www/pull/30
---
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
Github user serg38 closed the pull request at:
https://github.com/apache/cloudstack-www/pull/31
---
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
GitHub user serg38 opened a pull request:
https://github.com/apache/cloudstack-www/pull/32
Adding Sergey and Nicolas to commiters
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/serg38/cloudstack-www master
Alternatively you
GitHub user serg38 opened a pull request:
https://github.com/apache/cloudstack-www/pull/31
Addingn Sergey and Nicolas to committers
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/serg38/cloudstack-www patch-2
Alternatively you
GitHub user serg38 opened a pull request:
https://github.com/apache/cloudstack-www/pull/30
Added Sergey and Nicolas to committers
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/serg38/cloudstack-www patch-1
Alternatively you
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1846
LGTM
---
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
1 - 100 of 295 matches
Mail list logo
