Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1599
The initiative to split marvin into its own repository has been dropped for
now. Meanwhile, this PR can still be accepted as it fixed the code-generator to
work against the api discovery. I&#x
GitHub user rhtyd opened a pull request:
https://github.com/apache/cloudstack/pull/1612
packaging: Marvin and integration-tests packages
This introduces two new cloudstack packages: marvin and integration-tests.
The two packages will make it easier for CI systems to install
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1612
@PaulAngus sorry I did not get the question. Put what repo in that org?
Based on the response received on the dev-ML thread on splitting marvin,
this PR implements the alternative to
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1612
Packages repository built for this PR:
http://packages.shapeblue.com/cloudstack/custom/marvin-integration-tests/
---
If your project is set up for it, you can reply to this email and have your
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1612
@rohit if that keeps bothering you, I don't mind switching gh handle with
you :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user rhtyd opened a pull request:
https://github.com/apache/cloudstack/pull/1614
CLOUDSTACK-9437: Fix egress chain and cleanup for allow all traffic
- Fixes use of rules.v4/rules instead of router_rules.v4 file, this makes
sure
that FW_EGRESS_RULE chain gets created on
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1519
We should get this tested and merged for 4.9 /cc @swill
@abhinandanprateek @murali-reddy @JayapalUradi can you help review this and
advise any further changes, thanks.
---
If your project
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1614
Alright Will, closing 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 not have this feature
enabled and
Github user rhtyd closed the pull request at:
https://github.com/apache/cloudstack/pull/1614
---
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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1612
@swill @wido @PaulAngus @jburwell review and lgtm please, thanks :)
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1610
@milamberspace I tested upgrade scenario using debian packages, so at least
this works for debian mgmt server hosts. I think you hit the issue with CentOS
based mgmt server host?
---
If your
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1612
@wido thanks, the Juniper fix is not a separate PR as without that fix
packaging/build failure were happening (some times, and every time on a centos7
machine).
---
If your project is set up
GitHub user rhtyd opened a pull request:
https://github.com/apache/cloudstack/pull/1620
oobm: simply change password transactional logic
- Simplifies change password transactional logic without using pessmistic
locks
- Adds a re-enter password field in the UI to valid ipmi/oobm
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1621
LGTM thanks @milamberspace
---
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
Github user rhtyd closed the pull request at:
https://github.com/apache/cloudstack/pull/1620
---
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
GitHub user rhtyd reopened a pull request:
https://github.com/apache/cloudstack/pull/1620
oobm: simply change password transactional logic
- Simplifies change password transactional logic without using pessmistic
locks
- Adds a re-enter password field in the UI to valid ipmi
GitHub user rhtyd reopened a pull request:
https://github.com/apache/cloudstack/pull/1611
marvin: deploy clusters in separate threads
This speeds up cluster deployment by Marvin, each cluster deployment can be
executed in separate threads. This for example, allows for setting up
Github user rhtyd closed the pull request at:
https://github.com/apache/cloudstack/pull/1611
---
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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1612
Pinging for review -- @karuturi @koushik-das @abhinandanprateek @jburwell
If we can get this merged soon, all new PRs etc can be tested easily with
CI systems as we'll get the marvi
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1611
Pinging for review - @wido @karuturi @koushik-das @abhinandanprateek
@murali-reddy @jburwell
This is marvin specific change, Travis validation is enough to show that
deployDatacenter
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1599
Pinging for review - @wido @koushik-das @karuturi @abhinandanprateek
@jburwell
This enables `cloudstackAPI` api cmd/resp classes generation against a live
running mgmt server.
---
If your
Github user rhtyd closed the pull request at:
https://github.com/apache/cloudstack/pull/1531
---
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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1531
@karuturi @jburwell this PR has enough review, can we merge this?
The changes are necessary without them the systemvm template appliance
building fails, tested and built these templates
GitHub user rhtyd reopened a pull request:
https://github.com/apache/cloudstack/pull/1531
systemvmtemplate: fix build and upgrade to debian 7.11 iso
- Bumps base debian iso to version 7.11
- Upgrade ruby version to 2.3.0 (latest/stable)
- Fix Gemfile
- Update README
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1511
Let's have another attempt at this? /cc @karuturi @jburwell @DaanHoogland
@wido @swill @koushik-das @abhinandanprateek and others
---
If your project is set up for it, you can reply to
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1622
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, or if the
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1619
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, or if the
GitHub user rhtyd opened a pull request:
https://github.com/apache/cloudstack/pull/1625
[blocker] cloudstack: fix upgrade paths to 4.10.0
This adds an upgrade to master since the recent 4.9 cut, adds an upgrade
path to the new code version 4.10. Without this PR all PRs to master
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1625
@karuturi thanks, I'll have a look why it failed
---
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 rhtyd closed the pull request at:
https://github.com/apache/cloudstack/pull/1625
---
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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1625
Looks like this unit test failed: Tests run: 2, Failures: 0, Errors: 1,
Skipped: 0, Time elapsed: 4.773 sec <<< FAILURE! - in
org.apache.cloudstack.network.lb.ApplicationLoadBal
GitHub user rhtyd reopened a pull request:
https://github.com/apache/cloudstack/pull/1625
[blocker] cloudstack: fix upgrade paths to 4.10.0
This adds an upgrade to master since the recent 4.9 cut, adds an upgrade
path to the new code version 4.10. Without this PR all PRs to master
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1625
@karuturi that's a bot account that will do packaging and testing for us
soon, I was testing it :)
---
If your project is set up for it, you can reply to this email and have your
reply appe
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1625
Looks like this unit test is known to consume a lot of memory: Tests run:
1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.918 sec - in
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1625
@karuturi on the machine which was building the rpm packages
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1625
The unit test again failed with Travis:
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.821 sec
<<< FAILURE! - in org.apache.cloudstack.network.lb.ApplicationLoadBal
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1625
I'm able to consistently reproduce the unit test failure on a machine with
similar memory as Travis (~8GB RAM):
searchForExistingLoadBal
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1626
Ping for review and merge -- @karuturi @jburwell @agneya2001 @swill @wido
@DaanHoogland and others
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user rhtyd opened a pull request:
https://github.com/apache/cloudstack/pull/1626
[blocker] Fix systemvm template build
Previous PR: https://github.com/apache/cloudstack/pull/1531
Fixes failing systemvmtemplate build.
You can merge this pull request into a Git
Github user rhtyd closed the pull request at:
https://github.com/apache/cloudstack/pull/1531
---
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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1625
@karuturi all green now, can we merge this? /cc @jburwell
---
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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1625
@karuturi our Trillian job has hit an internal bug so the job died,
nevertheless a single run could take hours against real hypervisors (we've xen,
kvm and vmware). I'll keep you p
Github user rhtyd closed the pull request at:
https://github.com/apache/cloudstack/pull/1620
---
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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1625
Thanks @karuturi
---
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 rhtyd reopened a pull request:
https://github.com/apache/cloudstack/pull/1620
oobm: simply change password transactional logic
- Simplifies change password transactional logic without using pessmistic
locks
- Adds a re-enter password field in the UI to valid ipmi
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1612
@karuturi can we also test/merge this. This is a packaging change that only
introduces 'cloudstack-marvin' and 'cloudstack-integration-tests' packages. The
above package bu
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1492
@ProjectMoon can you close/open the PR to re-kick Travis
---
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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1607
@ProjectMoon can you close/open the PR to re-kick Travis
---
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
GitHub user rhtyd reopened a pull request:
https://github.com/apache/cloudstack/pull/1626
[blocker] Fix systemvm template build
Previous PR: https://github.com/apache/cloudstack/pull/1531
Fixes failing systemvmtemplate build.
You can merge this pull request into a Git
Github user rhtyd closed the pull request at:
https://github.com/apache/cloudstack/pull/1626
---
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
Github user rhtyd commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1626#discussion_r73648560
--- Diff: tools/appliance/definitions/systemvmtemplate/definition.rb ---
@@ -27,15 +27,15 @@
architectures = {
:i386
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1626
@karuturi why do we need an explicit JIRA ID, I would copy the same things
as on this PR. It duplicates effort on my end with no benefits. When you a
merge a PR, it contains the history and ID of
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1612
@karuturi done.
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/540
@jburwell Likitha has moved on, unlikely we'll hear from her or see further
development activity
---
If your project is set up for it, you can reply to this email and have your
reply appe
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1622
@ProjectMoon can you push -f or close+open this PR to re-kick Travis?
@jburwell Travis was failing on master due to a missing db path, a fix was
merged yesterday. All PRs with failing Travis
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/351
@anshul1886 can you rebase against latest master and push -f ?
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1612
@karuturi I don't understand your comment, centos7 packages have been
supported since 4.6 (actually 4.5 too ships a centos7 repository). The PR is
for 4.7 as it would fix and improve testin
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1626
@karuturi it would be difficult to create and send PRs for every bug. I
understand that it makes things easier, and I'll update the JIRA ID. That said,
please understand that while I try
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1626
@karuturi done.
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1612
@karuturi thanks, I understand now. You're right, I sent for 4.7 as we
support fwd-merging since 4.7 and we might need to test a 4.7 based security
release in future.
---
If your project i
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1612
Thank you @karuturi
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1612
Thanks @karuturi
I'm not sure why the PR did not close, closing it manually now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user rhtyd closed the pull request at:
https://github.com/apache/cloudstack/pull/1612
---
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
GitHub user rhtyd reopened a pull request:
https://github.com/apache/cloudstack/pull/1620
oobm: simply change password transactional logic
- Simplifies change password transactional logic without using pessmistic
locks
- Adds a re-enter password field in the UI to valid ipmi
Github user rhtyd closed the pull request at:
https://github.com/apache/cloudstack/pull/1620
---
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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1626
@karuturi can we merge this as well, this is the last of build blockers.
I'm currently increasing Jenkins slave capacity so @blueorangutan can kick
packaging and eventually start testing ag
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1621
The changes won't be tested by Trillian as it does not support upgrade
tests yet. Based on the packaging result, we can accept it if anyone has
performed an upgrade test manually. /cc @kar
Github user rhtyd closed the pull request at:
https://github.com/apache/cloudstack/pull/1599
---
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
GitHub user rhtyd reopened a pull request:
https://github.com/apache/cloudstack/pull/1599
Marvin: Fix codegenerator to work with API discovery
This fixes Marvin cloudstackAPI generator to work with a live running mgmt
server's api discovery.
You can merge this pull request i
Github user rhtyd closed the pull request at:
https://github.com/apache/cloudstack/pull/1611
---
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
GitHub user rhtyd reopened a pull request:
https://github.com/apache/cloudstack/pull/1611
marvin: deploy clusters in separate threads
This speeds up cluster deployment by Marvin, each cluster deployment can be
executed in separate threads. This for example, allows for setting up
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1619
Nevermind @blueorangutan centos7 packaging worked, debian builder had an
issue so it failed. I've fixed them.
---
If your project is set up for it, you can reply to this email and have
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1606
LGTM (did not test it, kicked a packaging build)
---
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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1607
Nevermind @blueorangutan the jenkins job died due to git/github related
errors:
error: index-pack died of signal 15
fatal: index-pack failed
I'll kick it again
---
If
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1626
@blueorangutan kickpkgs
---
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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1626
@blueorangutan showprogress
---
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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1626
testing - ignore me
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1626
@blueorangutan echo
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1626
@blueorangutan hello
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1626
@blueorangutan help
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1626
@blueorangutan thanks
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1626
@blueorangutan kick
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1624
@blueorangutan kick
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1620
@blueorangutan kick
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1622
@blueorangutan kick
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1619
@blueorangutan kick
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1623
@blueorangutan kick
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1623
@blueorangutan kick
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1619
@blueorangutan kick
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1615
@blueorangutan kick
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1622
@blueorangutan kick
---
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 rhtyd commented on the pull request:
https://github.com/apache/cloudstack/commit/4347776ac6ef9ae86fb016862f4a6b2376f8319a#commitcomment-18547661
In setup/db/db/schema-481to490.sql:
In setup/db/db/schema-481to490.sql on line 473:
@pdion891 you're right, thank
Github user rhtyd commented on the pull request:
https://github.com/apache/cloudstack/commit/4347776ac6ef9ae86fb016862f4a6b2376f8319a#commitcomment-18547724
In engine/schema/src/com/cloud/upgrade/dao/Upgrade481to490.java:
In engine/schema/src/com/cloud/upgrade/dao/Upgrade481to490
GitHub user rhtyd opened a pull request:
https://github.com/apache/cloudstack/pull/1629
CLOUDSTACK-9449: Fix typo in user role description
Fixes description in default user role entry.
You can merge this pull request into a Git repository by running:
$ git pull https
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1629
@blueorangutan kick
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1618
@blueorangutan package
@ProjectMoon can you push -f to rekick Travis?
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1617
@blueorangutan package
@ProjectMoon can you push -f to rekick Travis?
---
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 rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1606
@blueorangutan package
---
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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1611
@blueorangutan package
---
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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1605
@blueorangutan package
---
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
401 - 500 of 2445 matches
Mail list logo
