Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1601
Thanks @swill
---
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
All,
Based on a recent discussion thread [1], I want to start a voting thread to
gather consensus around splitting Marvin from the CloudStack repository.
On successful voting, we would extract and maintain Marvin as a separate
library in a separate repository (example repository [2]) and various
Would it make sense to have tests include cloudstack versions along with
'other' requirements in their meta-data, so that they don't *have* to be tied
to a branch.
Kind regards,
Paul Angus
paul.an...@shapeblue.comĀ
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeb
Hi
I used to use marvin for setup simulator environments for using it as
integration test environments (4.5-latest) for the Ansible CloudStack
modules.
It's been a while and I can not really remember exactly what it was
caused it to fail but since a few weeks I was not able to setup such an
envir
Github user swill commented on the issue:
https://github.com/apache/cloudstack/pull/1455
@sanju1010 can you close and reopen this PR to kick off travis again?
Thanks...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as w
Github user swill commented on the issue:
https://github.com/apache/cloudstack/pull/1455
### CI RESULTS
```
Tests Run: 85
Skipped: 0
Failed: 0
Errors: 0
Duration: 3h 55m 23s
```
**Associated Uploads**
**`/tm
Github user swill commented on the issue:
https://github.com/apache/cloudstack/pull/1594
### CI RESULTS
```
Tests Run: 85
Skipped: 0
Failed: 1
Errors: 0
Duration: 3h 52m 54s
```
**Summary of the problem(s):**
```
FAIL:
Github user swill commented on the issue:
https://github.com/apache/cloudstack/pull/1594
@nvazquez I have fun this on two different CI environments with the same
error coming up in both. Can you confirm this is not related to this change?
Thanks...
---
If your project is set up fo
Github user kiwiflyer commented on the issue:
https://github.com/apache/cloudstack/pull/1608
We have QA'd the patch and confirm that it prevents the agent from crashing
when an unexpected exception occurs from upstream RBD libs.
LGTM
---
If your project is set up for it, you
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1480
---
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 asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1595
---
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 asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1455
---
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 asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1608
---
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 asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1601
---
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 asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1610
---
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 asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1609
---
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
I have merged the following PRs in preparation for RC2:
https://github.com/apache/cloudstack/pull/1610
https://github.com/apache/cloudstack/pull/1609
https://github.com/apache/cloudstack/pull/1608
https://github.com/apache/cloudstack/pull/1601
https://github.com/apache/cloudstack/pull/1595
https://
Github user milamberspace commented on the issue:
https://github.com/apache/cloudstack/pull/1583
@swill I do not see why changes on the L10N resource files have an impact
on the VPC behavior ... This looks like a false positive ...
---
If your project is set up for it, you can reply
Github user swill commented on the issue:
https://github.com/apache/cloudstack/pull/1583
Thanks, I couldn't either, but wanted to get a second opinion. I am
running CI against it for the 3rd time to see if the same thing pops again.
---
If your project is set up for it, you can repl
Hi,
Is there a way to start Jetty on a port other than :8080? I've tried with
mvn -pl :cloud-client-ui jetty:run -Djetty.port=8081
and it did not work. I need this because the machine where I am doing my
dev is alreay
running a service on port 8080 and I can't change that.
-Syed
Probably a question that could be asked on the user mailing list.
On 18/07/2016 3:41 PM, Syed Mushtaq wrote:
Hi,
Is there a way to start Jetty on a port other than :8080? I've tried with
mvn -pl :cloud-client-ui jetty:run -Djetty.port=8081
and it did not work. I need this because the machine
Try changing in
client/pom.xmlhttps://github.com/apache/cloudstack/blob/master/client/pom.xml#L459
~ Rajanihttp://cloudplatform.accelerite.com/
On July 19, 2016 at 1:11 AM, Syed Mushtaq
(syed1.mush...@gmail.com) wrote:Hi,
Is there a way to start Jetty on a port other than :8080? I've
tried with
mvn
22 matches
Mail list logo