You can use http://pastebin.com/ to upload the logs and provide the link.
-Harikrishna
On 02-Sep-2014, at 10:06 am, Giri Prasad g_p...@yahoo.com.INVALID wrote:
Thanks.
The error occurs at line 20400th line in the management server log. Please
let me know, where I can upload these 20400
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23819/
---
(Updated Sept. 2, 2014, 6:26 a.m.)
Review request for cloudstack, sanjeev n
Hi all,
The latest build seems to have broken starting the management server - I've
raised https://issues.apache.org/jira/browse/CLOUDSTACK-7465
http://jenkins.buildacloud.org/job/simulator-singlerun/259/ has failed, and I'm
assuming it's the same cause, but I can't see a lot of information on
This is the erring commit
commit c730bc3491f8b684c5ae51e0bff54cf7577cc246
Author: Rohit Yadav rohit.ya...@shapeblue.com
Date: Mon Sep 1 21:14:13 2014 +0200
server: Add event bus bean as commented xml in META-INF core
This adds a spring bean xml to have EventBus for ACS, but the
I've resolved my ticket as a duplicate of
https://issues.apache.org/jira/browse/CLOUDSTACK-7464
Please note that this has nothing to do with RHEL7 - I saw it on RHEL6.3
John
From: Koushik Das [koushik@citrix.com]
Sent: 02 September 2014 08:02
To:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/25240/
---
Review request for cloudstack and Kishan Kavala.
Bugs:
Hi Hugo,
On Tue, Sep 2, 2014 at 10:09 AM, h...@apache.org wrote:
Revert server: Add event bus bean as commented xml in META-INF core
Breaks CloudStack startup. You're better off putting this on the wiki
Alright will do, but this is just a file in which the bean is commented so
it does not
Right it is a commented out file but I think spring does not like Empty Context
Files so it is failing to start.
On 02-Sep-2014, at 1:49 pm, Rohit Yadav rohityada...@gmail.com wrote:
Hi Hugo,
On Tue, Sep 2, 2014 at 10:09 AM, h...@apache.org wrote:
Revert server: Add event bus bean as
Hey Rohit,
It does break CS startup, otherwise i would not have reverted it. Spring does
not tolerate empty xml files.
Cheers,
Hugo
On 2 sep. 2014, at 10:19, Rohit Yadav rohityada...@gmail.com wrote:
Hi Hugo,
On Tue, Sep 2, 2014 at 10:09 AM, h...@apache.org wrote:
Revert server: Add
See http://jenkins.buildacloud.org/job/simulator-singlerun/261/changes
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/25243/
---
Review request for cloudstack, Brian Federle and Jessica Wang.
Bugs:
Github user imduffy15 closed the pull request at:
https://github.com/apache/cloudstack/pull/13
---
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 imduffy15 commented on the pull request:
https://github.com/apache/cloudstack/pull/13#issuecomment-54129007
Status successfully shown. Test completed. Closing.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/25228/#review52018
---
Ship it!
commit 51e0488e5c07595219142fb2f954726f72e0adf2
- Kishan
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
See http://jenkins.buildacloud.org/job/build-master-noredist/3438/changes
Changes:
[kishan] CLOUDSTACK-7316: Usage Server is not getting started when we install
it on management server. This is happening when encryption is enabled. For
usage server it is not able to get key file in the
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/25243/#review52020
---
Ship it!
Ship It!
- Rajani Karuturi
On Sept. 2, 2014, 9:37
On Sept. 2, 2014, 10:37 a.m., Rajani Karuturi wrote:
Ship It!
commit c200ada863dd4a7d5659538e4378c77a3e89d597
- Rajani
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/25243/#review52020
Hi,
When I connect to CloudStack's VPN on a network (L2TP over IPSEC), I’m assigned
an IP like 10.1.2.2 and the DNS assigned is 10.1.2.1, but the virtual router is
not listening on this IP (VPN) for DNS queries but on guest network so I cannot
access resources by using internal dns domain
See http://jenkins.buildacloud.org/job/build-master/1521/changes
Changes:
[rajanikaruturi] CLOUDSTACK-7463: UI: Domain Admin UI shows 'Add LDAP Users'
button (should not be shown)
--
[...truncated 3885 lines...]
[INFO] skip non existing resourceDirectory
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/25235/#review52023
---
1. It should be possible to refactor these tests to put code into
On Mon, Sep 1, 2014 at 10:20 AM, Daan Hoogland daan.hoogl...@gmail.com wrote:
SO May 1st and 1st manday in september are both due to may 4th...
Nice read Stephen.
Now back to 4.4.x
I would like to create a new release if people feel we have something to
release. How is the general
GitHub user wilderrodrigues opened a pull request:
https://github.com/apache/cloudstack/pull/14
Pull request of changes in the cloud-server module
In the last 10 weeks we have been working in the cloud-server, focusing our
time in the refactor of the
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
On 09/01/2014 04:30 PM, Wido den Hollander wrote:
On 09/01/2014 04:20 PM, Daan Hoogland wrote:
SO May 1st and 1st manday in september are both due to may 4th...
Nice read Stephen.
Now back to 4.4.x
I would like to create a new release if people feel we have something to
release. How is
Github user wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/pull/14#issuecomment-54147257
Okay, I'm already on that.
Cheers,
Wilder
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Hi,
I’m going through list of issues that affect 4.3.0 and 4.3.1 and cherry-picking
those which are already fixed elsewhere. This is the issue which would involve
some modifications to the schema:
https://issues.apache.org/jira/browse/CLOUDSTACK-6756
@Sebatien: can you please take a look at
Github user wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/pull/14#issuecomment-54150383
Hi Rohit,
Did as you suggested and got no conflicts detected.
[INFO]
On Sep 2, 2014, at 3:20 PM, Rohit Yadav rohit.ya...@shapeblue.com wrote:
Hi,
I’m going through list of issues that affect 4.3.0 and 4.3.1 and
cherry-picking those which are already fixed elsewhere. This is the issue
which would involve some modifications to the schema:
On 09/02/2014 03:30 PM, sebgoa wrote:
On Sep 2, 2014, at 3:20 PM, Rohit Yadav rohit.ya...@shapeblue.com wrote:
Hi,
I’m going through list of issues that affect 4.3.0 and 4.3.1 and cherry-picking
those which are already fixed elsewhere. This is the issue which would involve
some
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/24740/
---
(Updated Sept. 2, 2014, 1:38 p.m.)
Review request for cloudstack, Santhosh
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/24696/
---
(Updated Sept. 2, 2014, 1:38 p.m.)
Review request for cloudstack, Santhosh
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/25248/
---
Review request for cloudstack, Alena Prokharchyk, edison su, Darren Shepherd,
On Tue, Sep 2, 2014 at 9:34 AM, Wido den Hollander w...@widodh.nl wrote:
On 09/02/2014 03:30 PM, sebgoa wrote:
On Sep 2, 2014, at 3:20 PM, Rohit Yadav rohit.ya...@shapeblue.com wrote:
Hi,
I’m going through list of issues that affect 4.3.0 and 4.3.1 and
cherry-picking those which are
Do I read the ticket wrong or that fix is already in 4.4?
FG
On 2014-09-02, 10:48 AM, Rohit Yadav wrote:
On 02-Sep-2014, at 4:38 pm, David Nalley da...@gnsa.us wrote:
I agree - how will users upgrade from 4.3.1 to 4.4.x or later - schema
changes aren't necessarily going to screw up the
On 02-Sep-2014, at 4:54 pm, Francois Gaudreault fgaudrea...@cloudops.com
wrote:
Do I read the ticket wrong or that fix is already in 4.4?
FG
Yes, this already is in 4.4 but the issue is — do we want it for 4.3 branch as
it affects 4.3.0 release as well and it’s a major issue for people using
On 2014-09-02, 11:00 AM, Rohit Yadav wrote:
On 02-Sep-2014, at 4:54 pm, Francois Gaudreault fgaudrea...@cloudops.com
wrote:
Do I read the ticket wrong or that fix is already in 4.4?
FG
Yes, this already is in 4.4 but the issue is — do we want it for 4.3 branch as it affects
4.3.0 release
Github user lsimons commented on the pull request:
https://github.com/apache/cloudstack/pull/14#issuecomment-54167891
Thanks Travis! So cool that this is working...the failure is due to the
change here:
Github user bhaisaab commented on the pull request:
https://github.com/apache/cloudstack/pull/14#issuecomment-54169234
Thanks to @imduffy15 we have TravisCI fire up on every commit.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
The right way to do this is to do commit to commit migrations and use some
db versioning tools like liquibase or flywaydb which will execute the new
change sets. We discussed this before and IIRC, someone started working on
it.
On Tue, Sep 2, 2014 at 20:58 PM, Rohit Yadav
@Rohit
I think we are playing with fire here a bit. DB changes should be made on
major releases and we should try to avoid DB changes on minor releases
because of this type of problem. We have to keep the upgrade paths as
clean as possible because we don't want people running into issues when
On 02-Sep-2014, at 5:40 pm, Rajani Karuturi raj...@apache.org wrote:
The right way to do this is to do commit to commit migrations and use some
db versioning tools like liquibase or flywaydb which will execute the new
change sets. We discussed this before and IIRC, someone started working on
If you’re not going to read anything because the thread has gone too long
already, read this:
4.4.0 is already out there, if we release 4.3.1 there is no way people can
upgrade to 4.4.0 as the upgrade paths exist in the 4.4.0 release itself which
does not know about 4.3.1
On 02-Sep-2014, at
On Sep 2, 2014, at 11:56 AM, Rohit Yadav rohit.ya...@shapeblue.com wrote:
On 02-Sep-2014, at 5:40 pm, Rajani Karuturi raj...@apache.org wrote:
The right way to do this is to do commit to commit migrations and use some
db versioning tools like liquibase or flywaydb which will execute the new
I think we're discussing the matter of policy, rather than this case. Can
we make this one work, I'm confident you can, Rohit. But as a policy, do
we want to make changes to DB schemas in minor (bugfix) releases, and I
think the answer being given is no. Perhaps that means the concrete
solution
Hi, with simulator now running on travis we are seeing test failures a bit more
clearly.
test_04_extrat_Iso is failing on 4.3 branch
Could someone fix the test or investigate what's happening.
https://travis-ci.org/apache/cloudstack/jobs/34183172
thanks
-sebastien
As some of you may have noticed github PR has been turned on for our main repo
(it was already the case for the docs repo).
In addition, TravisCI config files have been added to master and 4.3 (not yet
for 4.4).
https://travis-ci.org/apache/cloudstack/builds
The Travis jobs, compile
I think this covers the main use case we have to be concerned about, so I
think this is fine. I don't think we should have to worry about upgrading
from 4.3.1 to 4.4.0. I agree that if we maintain an upgrade path from
4.3.1 to 4.4.1, we should be fine.
*Will STEVENS*
Lead Developer
*CloudOps*
On 02-Sep-2014, at 6:05 pm, Marcus shadow...@gmail.com wrote:
I think we're discussing the matter of policy, rather than this case. Can
we make this one work, I'm confident you can, Rohit. But as a policy, do
we want to make changes to DB schemas in minor (bugfix) releases, and I
think the
So just to be clear, Sebastien, does that mean it's acceptable for
non-committers to submit their code for review via a Github pull request,
instead of using ReviewBoard? (I hope so: I think that will make the process
easier and so encourage contributions).
--
Stephen Turner
-Original
While investigating an issue with secondary storage templates, I noticed all
the file handling I came across shelled and execute things like mkdir, rm, etc,
etc. With the migration to Java 7 is there still a reason to continue that
method of file handling or in the future could/should file
See http://jenkins.buildacloud.org/job/simulator-hotfix-trigger/28/
--
[...truncated 1125 lines...]
[INFO]
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @
cloud-framework-cluster ---
[INFO] Surefire report directory:
If we could keep code like that all in Java, that would be my personal
preference.
On Tue, Sep 2, 2014 at 10:42 AM, David Bierce david.bie...@appcore.com
wrote:
While investigating an issue with secondary storage templates, I noticed
all the file handling I came across shelled and execute
On 02-Sep-2014, at 6:19 pm, Will Stevens wstev...@cloudops.com wrote:
I think this covers the main use case we have to be concerned about, so I
think this is fine. I don't think we should have to worry about upgrading
from 4.3.1 to 4.4.0. I agree that if we maintain an upgrade path from
Github user wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/pull/14#issuecomment-54187941
Fixing it right now.
Sorry for the incovenience.
Cheers,
Wilder
---
If your project is set up for it, you can reply to this email and
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/25258/
---
Review request for cloudstack and Mike Tutkowski.
Bugs: CLOUDSTACK-7467
On 02-09-14 19:06, Mike Tutkowski wrote:
If we could keep code like that all in Java, that would be my personal
preference.
+1
Makes error handling (using Exception) a lot easier and cleaner.
Stay away from Shell if not required.
Wido
On Tue, Sep 2, 2014 at 10:42 AM, David Bierce
Me too, but I’m new to this code base and to Java so I didn’t know if there was
a rational behind it or not. :)
There were a few places in SSVM where it is handling symlinks, for which
support wasn’t added till Java 7 (according to the Docs), that was the only
reason I could think of.
On 02-09-14 20:11, David Bierce wrote:
Me too, but I’m new to this code base and to Java so I didn’t know if there was
a rational behind it or not. :)
There were a few places in SSVM where it is handling symlinks, for which
support wasn’t added till Java 7 (according to the Docs), that was
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/25248/#review52059
---
See http://jenkins.buildacloud.org/job/build-master/1522/changes
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/25266/
---
Review request for cloudstack, Frank Zhang and Hugo Trippaers.
Bugs:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/25258/#review52061
---
Ship it!
Committed with SHA
See http://jenkins.buildacloud.org/job/build-master-noredist/3439/changes
On Sept. 2, 2014, 7:01 p.m., Nitin Mehta wrote:
engine/orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java, line
814
https://reviews.apache.org/r/25248/diff/1/?file=673914#file673914line814
Checking for template==null masks the whole problem.
1. Such validations
Hi,
I was wondering what our current best practices are around storing
passwords in the DB?
For example, if you want to store the username and password of a resource
that CloudStack manages, how do we recommend storing the password?
Thanks!
--
*Mike Tutkowski*
*Senior CloudStack Developer,
On 02-09-14 21:22, Mike Tutkowski wrote:
Hi,
I was wondering what our current best practices are around storing
passwords in the DB?
For example, if you want to store the username and password of a resource
that CloudStack manages, how do we recommend storing the password?
Using the
On Tue, Sep 2, 2014 at 10:48 AM, Rohit Yadav rohit.ya...@shapeblue.com wrote:
On 02-Sep-2014, at 4:38 pm, David Nalley da...@gnsa.us wrote:
I agree - how will users upgrade from 4.3.1 to 4.4.x or later - schema
changes aren't necessarily going to screw up the upgrade process, but
certainly
Thanks, Wido
Do you happen to know a relevant class off the top of your head?
On Tue, Sep 2, 2014 at 1:25 PM, Wido den Hollander w...@widodh.nl wrote:
On 02-09-14 21:22, Mike Tutkowski wrote:
Hi,
I was wondering what our current best practices are around storing
passwords in the DB?
On 02-09-14 21:29, Mike Tutkowski wrote:
Thanks, Wido
Do you happen to know a relevant class off the top of your head?
No sorry, but if you search for where it fetches the VNC password for
KVM VMs you should find it.
It's probably the DB layer which does the encryption and decryption.
OK - thanks!
On Tue, Sep 2, 2014 at 1:33 PM, Wido den Hollander w...@widodh.nl wrote:
On 02-09-14 21:29, Mike Tutkowski wrote:
Thanks, Wido
Do you happen to know a relevant class off the top of your head?
No sorry, but if you search for where it fetches the VNC password for KVM
VMs
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
Hey All,
I am a committer and when I tried to push a hotfix branch to '
https://github.com/apache/cloudstack.git' today, I got a Permission
Denied error. Is this a problem with my account or is there an issue with
the github repo right now?
Thx,
*Will STEVENS*
Lead Developer
*CloudOps* *|
On Sep 2, 2014, at 3:57 PM, Will Stevens wstev...@cloudops.com wrote:
Hey All,
I am a committer and when I tried to push a hotfix branch to '
https://github.com/apache/cloudstack.git' today, I got a Permission
Denied error. Is this a problem with my account or is there an issue with
the
You can't push to github. It's a RO mirror.
You push commits to git-wip-us.a.o.
Very few people have write access to anything on github.com/apache
On Tue, Sep 2, 2014 at 3:57 PM, Will Stevens wstev...@cloudops.com wrote:
Hey All,
I am a committer and when I tried to push a hotfix branch to '
Oh. I thought for sure I had done that before, but maybe I am just losing
my mind (totally possible). :)
Thanks guys,
Will
*Will STEVENS*
Lead Developer
*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_
On Tue, Sep 2,
Hi,
You can add @Encrypt tag to the field and it would be stored in encrypted
form in the DB, and decrypted automatically when reading. It uses the key
file provided in db.properties for encryption.
You can check many of the VOs, for example UserVO, as a reference.
HTH
Amogh
On 9/2/14 12:38
On Sept. 2, 2014, 7:01 p.m., Nitin Mehta wrote:
engine/orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java, line
814
https://reviews.apache.org/r/25248/diff/1/?file=673914#file673914line814
Checking for template==null masks the whole problem.
1. Such validations
Thanks, Amogh
In my case, I'm storing the password in the storage_pool_details table's
value field. Not all cells in this column will need to be encrypted,
though. What do you suggest there?
On Tue, Sep 2, 2014 at 2:28 PM, Amogh Vasekar amogh.vase...@citrix.com
wrote:
Hi,
You can add
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
Hi,
You can check DBEncryptionUtil, it provides utility methods for encryption
/ decryption. May be add some custom logic for only your cell?
HostEntityDaoImpl might be useful reference.
Thanks,
Amogh
On 9/2/14 1:47 PM, Mike Tutkowski mike.tutkow...@solidfire.com wrote:
Thanks, Amogh
In my
Created another wiki [1] for troubleshooting and information on the
implementation details.
[1]
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Troubleshooting+-+up
loading+custom+domain+certificate+instead+of+using+realhostip.com
Thanks,
-Nitin
On 05/06/14 7:03 PM, Nitin Mehta
See http://jenkins.buildacloud.org/job/simulator-hotfix-trigger/29/
--
[...truncated 7107 lines...]
[INFO]
[INFO] Building Apache CloudStack Developer Mode 4.4.1-SNAPSHOT
[INFO]
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
Thanks, Amogh
It looks like I can simply call the static encrypt method before I store
the password in the DB, then pull out the encrypted value and call the
static decrypt method before I send the password to the resource in
question.
On Tue, Sep 2, 2014 at 3:05 PM, Amogh Vasekar
See http://jenkins.buildacloud.org/job/build-master-noredist/3442/changes
Changes:
[min.chen] CLOUDSTACK-7471:Regular user is allowed to
deleteNetwork/RestartNetwork
[min.chen] Fix incorrectly written unit tests.
--
[...truncated 5058 lines...]
[INFO]
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
On Tue, Sep 2, 2014 at 9:18 PM, Will Stevens wstev...@cloudops.com wrote:
@Rajani
I am not entirely sure which technology is being used for the db upgrade
paths, but I think it is probably something like liquibase already. I
would have to check on the technology, but this is already in
this was to your suggestion of a separate tool that does (rolling)
upgrades which i think is a new proposal. I should have made it clear in
my mail about it and should have started it with right way according to
me.
right way to do things is in no way against iterative development. May be
at a
CS on Ubuntu 12.04 LTS, 4.1 is working correctly on the same hardware
(partition1).
This problem is with CS 4.3 on Ubuntu 14.04 LTS (partition2):
2014-09-01 17:21:23,267 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-6:ctx-d1e72afb) Add job-27 into job monitoring
2014-09-01 17:21:23,267
Github user wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/pull/14#issuecomment-54255040
Hi Rohit,
I changed the db.properties last night and from the 3 builds 1 was
successful (job 30.1). Concerning the other 2, jobs 30.2 and 30.3, I saw
GitHub user wilderrodrigues reopened a pull request:
https://github.com/apache/cloudstack/pull/14
Pull request of changes in the cloud-server module
In the last 10 weeks we have been working in the cloud-server, focusing our
time in the refactor of the
Github user wilderrodrigues closed the pull request at:
https://github.com/apache/cloudstack/pull/14
---
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 wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/pull/14#issuecomment-54255074
Sorry mouse went over the wrong button my mistake and I closed the PR.
Cheers,
Wilder
---
If your project is set up for it, you can reply to
96 matches
Mail list logo
