Re: Review Request 11906: CLOUDSTACK-1047: tracking in logs using job id

[Prasanna Santhanam]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/11906/#review22580
---


LGTM but clutters the log up quite a bit.

- Prasanna Santhanam


On June 18, 2013, 7:07 a.m., Sanjay Tripathi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/11906/
> ---
> 
> (Updated June 18, 2013, 7:07 a.m.)
> 
> 
> Review request for cloudstack, Devdeep Singh, Nitin Mehta, and Sateesh 
> Chodapuneedi.
> 
> 
> Bugs: CLOUDSTACK-1047
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-1047: tracking in logs using job id
> 
> https://issues.apache.org/jira/browse/CLOUDSTACK-1047
> 
> 
> Diffs
> -
> 
>   server/src/com/cloud/async/AsyncJobManagerImpl.java 0101a8a 
>   server/src/com/cloud/storage/VolumeManagerImpl.java 4297efb 
> 
> Diff: https://reviews.apache.org/r/11906/diff/
> 
> 
> Testing
> ---
> 
> Tests:
> 1. Deploy an Instance.
> 2. In the Management server logs, check the async job description, it should 
> be somthing like: job-[ 22 ] = [ 1075d499-03a8-44c3-ac9e-348dc5b32ba1 ]
> 
> 
> Thanks,
> 
> Sanjay Tripathi
> 
>

Re: Testcase Failure

[Dharmesh Kakadia]

Realized the problem. I hadn't change the package structure in
surefire-plugin exclude configuration in pom.xml. That solved the problem.

Thanks,
Dharmesh


On Sat, Jun 29, 2013 at 7:36 PM, Dharmesh Kakadia wrote:

> Hi,
>
> I am trying to switch com.cloud.network package to org.apache.network.
> While doing so, I am encountering following failure in test case. I tried
> looking around for few hours, but no success. I don't understand
> spring-junit testing much. I looked at
> https://cwiki.apache.org/CLOUDSTACK/unit-testing-101.html but still not
> clear how dependencies are resolved in testing.
>
> Please tell me where to look for.
>
> Tests in error:
>   testSchedule(org.apache.network.security.SecurityGroupManagerImpl2Test):
> Error creating bean with name 'dataCenterDaoImpl': Injection of autowired
> dependencies failed; nested exception is
> org.springframework.beans.factory.BeanCreationException: Could not autowire
> field: protected org.apache.network.dao.AccountGuestVlanMapDao
> com.cloud.dc.dao.DataCenterDaoImpl._accountGuestVlanMapDao; nested
> exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No
> matching bean of type [org.apache.network.dao.AccountGuestVlanMapDao] found
> for dependency: expected at least 1 bean which qualifies as autowire
> candidate for this dependency. Dependency annotations:
> {@javax.inject.Inject()}
>
> Thanks,
> Dharmesh
>

Review Request 12200: Fixed issues while adding DC to zone in VM ware

[Rayees Namathponnan]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/12200/
---

Review request for cloudstack, Girish Shilamkar and Prasanna Santhanam.


Repository: cloudstack-git


Description
---

Fixed issues  while adding DC to zone in VM ware, 

Also script modified to skip adding host in vmware.


Diffs
-

  tools/marvin/marvin/deployDataCenter.py 961718a 

Diff: https://reviews.apache.org/r/12200/diff/


Testing
---

Tested 


Thanks,

Rayees Namathponnan

Re: Review Request 12200: Fixed issues while adding DC to zone in VM ware

[Sateesh Chodapuneedi]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/12200/#review22581
---



tools/marvin/marvin/deployDataCenter.py


Only 1 vmwareDC can be added to a zone, hence we don't need to iterate over 
vmwareDcs collection. Better if we have vmwareDc object rather than collection 
vmwareDcs.
The above check for None is good. 


- Sateesh Chodapuneedi


On June 30, 2013, 7:29 a.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12200/
> ---
> 
> (Updated June 30, 2013, 7:29 a.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar and Prasanna Santhanam.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fixed issues  while adding DC to zone in VM ware, 
> 
> Also script modified to skip adding host in vmware.
> 
> 
> Diffs
> -
> 
>   tools/marvin/marvin/deployDataCenter.py 961718a 
> 
> Diff: https://reviews.apache.org/r/12200/diff/
> 
> 
> Testing
> ---
> 
> Tested 
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

Re: Review Request 12200: Fixed issues while adding DC to zone in VM ware

[Prasanna Santhanam]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/12200/#review22582
---


I think you were working on an old HEAD which is why most of the pep8 and 
storage related changes were removed. Please resubmit after pulling in latest

Also, don't forget to run a pep8 check on the file
$ pip install pep8
$ pep8 deployDataCenter.py

You can check for tab issues using tabnanny
$ python -m tabnanny tools


tools/marvin/marvin/deployDataCenter.py


Retain this as the new style class inheriting from `object`.



tools/marvin/marvin/deployDataCenter.py


These are required for adding object store and cache storage. Were these 
removed intentionally?



tools/marvin/marvin/deployDataCenter.py


These are required for adding object store and cache storage. Were these 
removed intentionally?


- Prasanna Santhanam


On June 30, 2013, 7:29 a.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12200/
> ---
> 
> (Updated June 30, 2013, 7:29 a.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar and Prasanna Santhanam.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fixed issues  while adding DC to zone in VM ware, 
> 
> Also script modified to skip adding host in vmware.
> 
> 
> Diffs
> -
> 
>   tools/marvin/marvin/deployDataCenter.py 961718a 
> 
> Diff: https://reviews.apache.org/r/12200/diff/
> 
> 
> Testing
> ---
> 
> Tested 
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

Re: Jenkins and IRC

[Prasanna Santhanam]

On Fri, Jun 28, 2013 at 10:25:47AM -0700, Hugo Trippaers wrote:
> >> @David, remember that nginx proxy timeout setting we discussed ages
> >> ago? Would be nice to get that sorted so we can use some extra cloud
> >> power on jenkins.cloudstack.org. Any ideas on how we can get that
> >> done?
> > 
> > I plan on moving the current jenkins node on to a CloudStack setup
> > along with configuring jenkins purely via github/yaml config files.
> > still exploring. I think there should be some nginx puppet recipes
> > around for quick configuration.  
> 
> Nice! I still have some cloud power i can add to the jenkins pool in
> our cloud, so with all those clouds we should be able to speed
> things up.

Yup - that's where we should be headed.

> 
> I tried making the change to the nginx configuration a while back,
> but some it did not get propagated, maybe you can have a look?  This
> is my commit on the puppet module:
> https://github.com/CloudStack-extras/cso-infrastructure/commit/9d65207989e7cbc5231f3f5184bd4bf6bf0f84d5

I don't know if the instance has been pulling config changes from
puppet anymore. It might need reviving. @David, is puppetmaster still
running for the cso-infra?

-- 
Prasanna.,


Powered by BigRock.com

[CI] tabnanny and pep8

[Prasanna Santhanam]

It looks like the python scripts are getting mangled either by the
submitter or at reviewboard. I fixed a bunch of tests (c731597) that
failed in this weekend's test run because of tab issues.

Going forward all test scripts will be checked for tabs and
indentation issues by tabnanny
http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-tabnanny/

Also marvin will have python pep8 compliance check done by
http://jenkins.buildacloud.org/view/master/job/cloudstack-marvin/

Thanks,

-- 
Prasanna.,


Powered by BigRock.com

Re: [ACS42] Branch created

[Prasanna Santhanam]

On Sat, Jun 29, 2013 at 04:30:45PM +, Animesh Chaturvedi wrote:
> I have created 4.2 branch
> 

Reviewboard patches need to be looked at. Some of the bugs are
targeted for 4.2. I applied what I could and added reviewers for some.
Didn't get through it all, but will take a look again later today.

-- 
Prasanna.,


Powered by BigRock.com

Re: [ACS42] Branch created

[Prasanna Santhanam]

On Sun, Jun 30, 2013 at 02:11:17PM +0530, Prasanna Santhanam wrote:
> On Sat, Jun 29, 2013 at 04:30:45PM +, Animesh Chaturvedi wrote:
> > I have created 4.2 branch
> > 
> 
> Reviewboard patches need to be looked at. Some of the bugs are
> targeted for 4.2. I applied what I could and added reviewers for some.
> Didn't get through it all, but will take a look again later today.
> 

here's the latest list of pending reviews:

Found 55 pending review requests for cloudstack
 #ID | Submitter   | Branch  | Reviewer 
|Upd| 
-
7018 | bharatk | | nitin,   | Y 
| 
8294 | kawai   | master  |  |   
| 
9696 | weizhou | 4.0.1   | jayapal,nitin,   |   
| 
10366 | radhikap| master  | chip.childers,jtomechak,ke4qqq,p | 
Y | 
10411 | pborreli| 4.1 | jzb,sebgoa,  |  
 | 
10594 | serverchief | 4.1 | chiradeep,   |  
 | 
10614 | serverchief | 4.1 | chiradeep,   |  
 | 
10773 | nicolas.lamirau | 4.1 |  |  
 | 
10776 | swamy   | master  | gpshilamkar,talluri,tsp, |  
 | 
10828 | chiragj | | gpshilamkar,sailajam,tsp,|  
 | 
10882 | isaac.chiang| master  | pranavs, |  
 | 
10970 | dahn| | chiradeep,murali.reddy,Spark404, |  
 | 
11052 | fangw   | master  | edison,kelveny,  |  
 | 
11216 | harikrishna.pat | master  | nitin,   |  
 | 
11277 | edison  | master  |  |  
 | 
11327 | kawai   | 4.1, master | pranavs, |  
 | 
11462 | talluri | master  | Sateesh,tsp, |  
 | 
11479 | mtutkowski  | master  | edison,jburwell, | 
Y | 
11526 | talluri | Master  | tsp, |  
 | 
11626 | gauravaradhye   | | tsp, |  
 | 
11627 | Saksham | 4.1 | kishan,  | 
Y | 
11649 | sanjay.tripathi | master  | devdeep, |  
 | 
11670 | sanjay.tripathi | master  | devdeep, | 
Y | 
11858 | rajesh_battala  | master  | alena1108,murali.reddy,ramganesh | 
Y | 
11861 | dahn| |  |  
 | 
11900 | rayeesn | | gpshilamkar,tsp, |  
 | 
11904 | sanjeevneelarap | master  | talluri,tsp, |  
 | 
11906 | sanjay.tripathi | master  | devdeep,nitin,Sateesh,   | 
Y | 
11921 | rayeesn | master  | gpshilamkar,tsp, |  
 | 
11942 | kocka   | |  | 
Y | 
11953 | mebigfatguy | trunk   | alena1108,prachidamle,   | 
Y | 
11981 | asteer  | | Spark404,|  
 | 
11984 | vijayendrabvs   | master  | chip.childers,edison,minchen07,  |  
 | 
11992 | rajesh_battala  | master  | alexhu,edison,ramganesh,Sateesh  | 
Y | 
12025 | rajesh_battala  | master  | alexhu,edison,ramganesh,Sateesh  | 
Y | 
12063 | harikrishna.pat | master  | aprateek,kishan,nitin,   | 
Y | 
12079 | harikrishna.pat | master  | aprateek,| 
Y | 
12098 | pawitp  | master  |  |  
 | 
12106 | dlafferty   | master  | alexhu,chip.childers,edison, | 
Y | 
12109 | bharatk | master  | aprateek,|  
 | 
12126 | topcloud| vmsync  |  | 
Y | 
12131 | dlafferty   | master  | edison,minchen07,| 
Y | 
12134 | kocka   | |  | 
Y | 
12143 | fangw   | master  | edison,  | 
Y | 
12144 | fangw   | | edison,  | 
Y | 
12156 | sanjay.tripathi | master  | devdeep,Sateesh, | 
Y | 
12158 | rajesh_battala  | master  | edison,  | 
Y | 
12180 | vijayendrabvs   | master  | chip.childers,devdeep,kelveny,Sa | 
Y | 
12184 | rayeesn | master and  | prachidamle, | 
Y | 
12185 | mebigfatguy | trunk   |  | 
Y | 
12188 | kocka   | |  | 
Y | 
12190 | kocka 

Re: [CI] tabnanny and pep8

[Rohit Yadav]

+1.

*tabnanny* nice name by the way :P

Cheers.

On Sun, Jun 30, 2013 at 2:08 PM, Prasanna Santhanam  wrote:

> It looks like the python scripts are getting mangled either by the
> submitter or at reviewboard. I fixed a bunch of tests (c731597) that
> failed in this weekend's test run because of tab issues.
>
> Going forward all test scripts will be checked for tabs and
> indentation issues by tabnanny
> http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-tabnanny/
>
> Also marvin will have python pep8 compliance check done by
> http://jenkins.buildacloud.org/view/master/job/cloudstack-marvin/
>
> Thanks,
>
> --
> Prasanna.,
>
> 
> Powered by BigRock.com
>
>

Re: Review Request 11962: CLOUDSTACK-1758: SSVM tests failed due to ssh error

[ASF Subversion and Git Services]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/11962/#review22585
---


Commit 7d72966e45d3e2f122d5b3d44e9e300bf017a593 in branch 
refs/heads/master-6-17-stable from Girish Shilamkar
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7d72966 ]

CLOUDSTACK-1758: Update ssh key location for vmware

Signed-off-by: Prasanna Santhanam 
(cherry picked from commit 6e63bb78220a057bca329ee6a8779f0e4c476586)


- ASF Subversion and Git Services


On June 19, 2013, 2:50 p.m., Girish Shilamkar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/11962/
> ---
> 
> (Updated June 19, 2013, 2:50 p.m.)
> 
> 
> Review request for cloudstack and Prasanna Santhanam.
> 
> 
> Bugs: CLOUDSTACK-1758
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Additional fixes were needed which were found during further testing.
> 
> 
> Diffs
> -
> 
>   test/integration/smoke/test_ssvm.py d637f96 
> 
> Diff: https://reviews.apache.org/r/11962/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Girish Shilamkar
> 
>

RE: [ACS42] Branch created

[Animesh Chaturvedi]

> -Original Message-
> From: Sateesh Chodapuneedi [mailto:sateesh.chodapune...@citrix.com]
> Sent: Saturday, June 29, 2013 8:34 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [ACS42] Branch created
> 
> Hi Animesh,
> Can you please let me know if commits into this branch are controlled?
> 
> Regards,
> Sateesh
[Animesh>] No the commits are not controlled at this time but no new features 
can be added only bug fixes
> 
> > -Original Message-
> > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > Sent: 29 June 2013 22:01
> > To: dev@cloudstack.apache.org
> > Subject: [ACS42] Branch created
> >
> > I have created 4.2 branch
> >
> > Animesh

Re: [DISCUSS] If BVT breaks, revert the commits...

[Prasanna Santhanam]

On Sat, Jun 29, 2013 at 12:31:31PM -0400, David Nalley wrote:
> On Sat, Jun 29, 2013 at 12:45 AM, Prasanna Santhanam  wrote:
> > On Sat, Jun 29, 2013 at 12:18:17AM +, Alex Huang wrote:
> >>
> >> To avoid having a bunch of reverts and resubmits, the developers
> >> should be able to request that BVT run on their branch and don't
> >> merge until BVT on their branch is at 100%.  We will work on
> >> figuring out how to do that.
> >>
> >> Comments?
> >>
> > Quick questions:
> >
> > 1. How do we test contributor code (from github/reviewboard) because
> > we have no staging area/branch?
> >
> 
> Take a look at the pre-commit testing that hadoop does, that might be
> usable for us. Olamy did a blog post about it recently.
> 

Thanks for the pointers! I will check it out.

> >
> > 4. Who will fix the tests which are broken?
> >
> 
> Well if we treat master as frozen until the tests are fixed, then I'd
> suppose that folks wanting to get code in will be incentivized to at
> least help fix them so that master can start getting code again :)
> 

It's an imposition not an incentive then :)

The reason for the impossibly long fix cycles for automated tests is
mainly because there isn't any review of test plans and tests
automated from those plans. So the project coming to Apache to *me*
personally has been a boon in this way to fix this process failure. At
least now we have reviews and a few more eyes looking at the problems
... even more would help.

Once we get to fixing the existing tests I think everyone will begin
to see how bloated some of them can get and can be simplified from an
automated perspective.

So I'm in on Alex's plan, in fact I fix tests everyday so glad to have
others join the effort.

-- 
Prasanna.,


Powered by BigRock.com

Re: [ACS42] Branch created

[Prasanna Santhanam]

On Sun, Jun 30, 2013 at 04:29:31PM +, Animesh Chaturvedi wrote:
> 
> 
> > -Original Message-
> > From: Sateesh Chodapuneedi [mailto:sateesh.chodapune...@citrix.com]
> > Sent: Saturday, June 29, 2013 8:34 PM
> > To: dev@cloudstack.apache.org
> > Subject: RE: [ACS42] Branch created
> > 
> > Hi Animesh,
> > Can you please let me know if commits into this branch are controlled?
> > 
> > Regards,
> > Sateesh
> [Animesh>] No the commits are not controlled at this time but no new
> features can be added only bug fixes

Should be (the same as it was for 4.1), RM will cherry-pick from
master/ apply from reviewboard. Except for docs and test script fixes
which can be pushed in post freeze. Any reason why it should not be
this way?

-- 
Prasanna.,


Powered by BigRock.com

Re: [DISCUSS] Java 7, tomcat 7 and further upgrades

[Prasanna Santhanam]

On Thu, Jun 27, 2013 at 04:18:40PM -0400, John Burwell wrote:
> All,
> 
> I am +1 for Java7.  However, I would like to propose ridding
> ourselves of Tomcat entirely and embedding a network stack such as
> Netty (http://netty.io) with a servlet bridge.  We have one JSP in
> the system that generates JSON resources.  It could be easily
> eliminated with a simple servlet that generates JSON from a
> ResourceBundle.  Outside of this JSP. I don't see any other
> requirements for a JEE container besides hosting a servlet.  We
> would gain a far simpler, self-contained deployment model (a single
> jar).  Additionally, we would gain greater control of the startup
> and shutdown lifecycle, as well as, threading dynamics.  If there is
> interest in this approach, I have thoughts on how to achieve this
> embedding and create a lightweight daemon framework that could be
> used for all CloudStack daemons.
> 
> As an aside, I also think we should replace our hand-rolled NIO code
> with Netty as well.
> 

John - could you break this and other thoughts down a little more in
what's involved?  Perhaps into its own thread. I don't know Netty. And
my J2EE is shaky at best. 

It's been a previous wish on this list to have the packaging of
cloudstack into a single easily deployable war instead of all the
complicated packaging we do. So I'd like to hear more of that and
other issues you describe.

-- 
Prasanna.,


Powered by BigRock.com

Re: Master build problem

[Prasanna Santhanam]

On Sun, Jun 30, 2013 at 06:47:22AM +, Paul Angus wrote:
> Is this fix in the new 4.2 branch?  I'm getting the following error when 
> trying to log in to the management UI. (UI reports 'Invalid Username or 
> Password')
> 
> 2013-06-30 07:12:33,779 DEBUG [cloud.user.AccountManagerImpl] 
> (catalina-exec-5:null) Attempting to log in user: admin in domain 1
> 2013-06-30 07:12:33,779 DEBUG [server.auth.SHA256SaltedUserAuthenticator] 
> (catalina-exec-5:null) Retrieving user: admin
> 2013-06-30 07:12:33,782 WARN  [server.auth.SHA256SaltedUserAuthenticator] 
> (catalina-exec-5:null) The stored password for admin isn't in the right 
> format for this authenticator
> 

This sounds unrelated to the previous error described in this thread.

Did you redeploy the database? If not what are your passwords hashed
as (MD5/SHA256/PlainText) in the cloud.account table? And what's in
the componentContext.xml?  Specifically, the order of authenticators.

-- 
Prasanna.,


Powered by BigRock.com

Re: [DISCUSS][VOTE] Moving cloudmonkey to its own repository, have its own release process

[Rohit Yadav]

On Sat, Jun 29, 2013 at 9:47 PM, David Nalley  wrote:

> Rohit:
>
> Do you plan on generating a cloudmonkey release? (and acting as the
> RM?, should be comparatively simple, but we might need to document
> it.)
>

Sure, why not. I can be the initial RM. We can document the process on wiki
which should be fairly straight forward and put some (help) documentation
or links to it on the README file.


> Setup.py will need to be fixed, but I have no other concerns than
> that. I plan to make this writable momentarily.
>

Pl. go ahead and also fix setup.py, when I do diff -Naur with the latest it
shows no differences for me. I'm not sure how to fix in history because
when I do diff for all commits where setup.py was changed I see no
differences in those commits.

Regards.


>
> --David
>
> On Sat, Jun 29, 2013 at 9:27 AM, Rohit Yadav  wrote:
> > More than 72 hours now. Let's make it writable and publish latest
> > cloudmonkey on pypi.
> >
> > Cheers.
> >
> > On Wed, Jun 26, 2013 at 3:02 AM, David Nalley  wrote:
> >
> >> >
> >> > Not sure about setup.py related failures.
> >> >
> >>
> >> Me either - setup.py is pretty dramatically different between the two
> >> repos.
> >>
> >> --David
> >>
>

Re: [ACS42] Branch created

[Chip Childers]

On Jun 30, 2013, at 12:39 PM, Prasanna Santhanam  wrote:

> On Sun, Jun 30, 2013 at 04:29:31PM +, Animesh Chaturvedi wrote:
>>
>>
>>> -Original Message-
>>> From: Sateesh Chodapuneedi [mailto:sateesh.chodapune...@citrix.com]
>>> Sent: Saturday, June 29, 2013 8:34 PM
>>> To: dev@cloudstack.apache.org
>>> Subject: RE: [ACS42] Branch created
>>>
>>> Hi Animesh,
>>> Can you please let me know if commits into this branch are controlled?
>>>
>>> Regards,
>>> Sateesh
>> [Animesh>] No the commits are not controlled at this time but no new
>> features can be added only bug fixes
>
> Should be (the same as it was for 4.1), RM will cherry-pick from
> master/ apply from reviewboard. Except for docs and test script fixes
> which can be pushed in post freeze. Any reason why it should not be
> this way?

That isn't until later in the schedule. The RM shouldn't be a
bottleneck to bug fixing right now.

>
> --
> Prasanna.,
>
> 
> Powered by BigRock.com
>
>

RE: Master build problem

[Paul Angus]

Hi Prasanna,

Here is the section from the componentContext.xml file.  The username/password 
in the user table is admin / 0.724297075275608

The state was is "disabled" by default I changed it to enabled but it didn't 
make a difference.

 

  
  
  
  
  
  

  
  

  
  
  
  
  
  

  

-Original Message-
From: Prasanna Santhanam [mailto:t...@apache.org]
Sent: 30 June 2013 17:50
To: dev@cloudstack.apache.org
Subject: Re: Master build problem

On Sun, Jun 30, 2013 at 06:47:22AM +, Paul Angus wrote:
> Is this fix in the new 4.2 branch?  I'm getting the following error
> when trying to log in to the management UI. (UI reports 'Invalid
> Username or Password')
>
> 2013-06-30 07:12:33,779 DEBUG [cloud.user.AccountManagerImpl]
> (catalina-exec-5:null) Attempting to log in user: admin in domain 1
> 2013-06-30 07:12:33,779 DEBUG
> [server.auth.SHA256SaltedUserAuthenticator] (catalina-exec-5:null)
> Retrieving user: admin
> 2013-06-30 07:12:33,782 WARN
> [server.auth.SHA256SaltedUserAuthenticator] (catalina-exec-5:null) The
> stored password for admin isn't in the right format for this
> authenticator
>

This sounds unrelated to the previous error described in this thread.

Did you redeploy the database? If not what are your passwords hashed as 
(MD5/SHA256/PlainText) in the cloud.account table? And what's in the 
componentContext.xml?  Specifically, the order of authenticators.

--
Prasanna.,


Powered by BigRock.com


This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is operated under 
license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Jenkins and IRC

[David Nalley]

On Sun, Jun 30, 2013 at 4:11 AM, Prasanna Santhanam  wrote:
> On Fri, Jun 28, 2013 at 10:25:47AM -0700, Hugo Trippaers wrote:
>> >> @David, remember that nginx proxy timeout setting we discussed ages
>> >> ago? Would be nice to get that sorted so we can use some extra cloud
>> >> power on jenkins.cloudstack.org. Any ideas on how we can get that
>> >> done?
>> >
>> > I plan on moving the current jenkins node on to a CloudStack setup
>> > along with configuring jenkins purely via github/yaml config files.
>> > still exploring. I think there should be some nginx puppet recipes
>> > around for quick configuration.
>>
>> Nice! I still have some cloud power i can add to the jenkins pool in
>> our cloud, so with all those clouds we should be able to speed
>> things up.
>
> Yup - that's where we should be headed.
>
>>
>> I tried making the change to the nginx configuration a while back,
>> but some it did not get propagated, maybe you can have a look?  This
>> is my commit on the puppet module:
>> https://github.com/CloudStack-extras/cso-infrastructure/commit/9d65207989e7cbc5231f3f5184bd4bf6bf0f84d5
>
> I don't know if the instance has been pulling config changes from
> puppet anymore. It might need reviving. @David, is puppetmaster still
> running for the cso-infra?
>

I don't believe it is - and I am hoping we move to a CloudStack-hosted
Jenkins rather than the current one.

--David

Re: On git 4.1 (4.1.1-SNAPSHOT), jetty:run fails because of database version errors

[Ryan Lei]

Great. Both the OSS and non-OSS builds fine on the 4.1 branch now! Tested
on OS X 10.6.8 and CentOS 6.3.

But here's another flaw in DB upgrade:
The upgrade writes the timestamp in UTC+0 time zone in MySQL (in 4.1, 4.2,
master):

[4.1] mysql> select * from version;
++-+-+--+
| id | version | updated | step |
++-+-+--+
|  1 | 4.0.0   | 2013-07-01 10:05:24 | Complete |
|  2 | 4.1.0   | 2013-07-01 02:18:36 | Complete |
|  3 | 4.1.1   | 2013-07-01 02:18:36 | Complete |
++-+-+--+

[4.2] mysql> select * from version;
++-+-+--+
| id | version | updated | step |
++-+-+--+
|  1 | 4.0.0   | 2013-07-01 10:38:22 | Complete |
|  2 | 4.1.0   | 2013-07-01 02:41:17 | Complete |
|  3 | 4.2.0   | 2013-07-01 02:41:18 | Complete |
++-+-+--+

My time zone is CST (UTC+8). The correct time should be 2013-07-01 10:xx:xx.

mysql> SELECT NOW(); reports the correct time, so I guess the problem is on
the Java (JDBC?) side.


---
Yu-Heng (Ryan) Lei, Associate Reasearcher
Chunghwa Telecom Laboratories / Cloud Computing Laboratory
ryan...@cht.com.tw
or
ryanlei750...@gmail.com



On Sat, Jun 29, 2013 at 1:59 AM, Hugo Trippaers  wrote:

> Hello :-)
>
> Nice find!
>
> I've pushed this commit to the branch:
>
>  commit b330f2aa909d7ddc387863e0806f71964f6d5f80
> Author: Hugo Trippaers 
> Date:   Fri Jun 28 10:57:51 2013 -0700
>
> CLOUDSTACK-3278 Add the 410 to 411 upgrade to the
> PremiumDatabaseUpgradeChecker
>
> Can you verify if this fixes your problem?
>
>
> Cheers,
>
> Hugo
>
> On Jun 28, 2013, at 10:39 AM, Ryan Lei  wrote:
>
> > Actually, the errors happen only in non-OSS build with git 4.1
> > (4.1.1-SNAPSHOT).
> >
> > OSS build with git 4.1 and non-OSS build with 4.1.0 source code work
> fine.
> > They are able to run the Upgrade40to41 or Upgrade410to411.
> >
> > I have created a JIRA ticket for this issue:
> > https://issues.apache.org/jira/browse/CLOUDSTACK-3278
> >
> >
> ---
> > Yu-Heng (Ryan) Lei, Associate Reasearcher
> > Chunghwa Telecom Laboratories / Cloud Computing Laboratory
> > ryan...@cht.com.tw<
> https://email.cht.com.tw/owa/redir.aspx?C=-wE1FEC3G0SWYpVkiWo8SsDdf3ZqO9AIuAPTzRnFYCUi-z4YljtI_hyVKkNHfn9F1Bn-vUWJnQ4.&URL=mailto%3aryanlei%40cht.com.tw
> >
> > or
> > ryanlei750...@gmail.com
> >
> >
> >
> > On Fri, Jun 28, 2013 at 4:42 PM, Ryan Lei  wrote:
> >
> >> Hi all,
> >> I was trying to use the git 4.1 branch to run non-OSS CloudStack from
> >> source. My commands were:
> >>
> >> (1) Put the neccessary jars in deps
> >> (2) Run deps/install-non-oss.sh with success
> >> (3) $ mvn clean install -DskipTests=true -Dnonoss
> >> (4) $ mvn -P developer -pl developer -Ddeploydb
> >> (5) $ mvn -pl :cloud-client-ui jetty:run
> >>
> >> Then I got these DB version errors which made the jetty quit:
> >> INFO  [utils.component.ComponentContext] (Timer-2:) Running
> >> SystemIntegrityChecker encryptionSecretKeyChecker
> >> INFO  [utils.component.ComponentContext] (Timer-2:) Running
> >> SystemIntegrityChecker databaseIntegrityChecker
> >> INFO  [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Grabbing lock
> to
> >> check for database integrity.
> >> INFO  [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Performing
> >> database integrity check
> >> INFO  [utils.component.ComponentContext] (Timer-2:) Running
> >> SystemIntegrityChecker managementServerNode
> >> INFO  [utils.component.ComponentContext] (Timer-2:) Running
> >> SystemIntegrityChecker premiumDatabaseUpgradeChecker
> >> INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Grabbing lock to
> >> check for database upgrade.
> >> INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) DB version =
> 4.0.0
> >> Code Version = 4.1.1-SNAPSHOT
> >> INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Database upgrade
> >> must be performed from 4.0.0 to 4.1.1-SNAPSHOT
> >> ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) The end upgrade
> >> version is actually at 4.1.0 but our management server code version is
> at
> >> 4.1.1-SNAPSHOT
> >> ERROR [utils.component.ComponentContext] (Timer-2:) System integrity
> check
> >> failed. Refuse to startup
> >>
> >>
> >> In MySQL, I found the table in 'version' has only one entry whose value
> is
> >> 4.0.0.
> >> Manually modifying the value to 4.1.1 led to other exceptions. Looks
> like
> >> 4.1 git "forgets" to upgrade the database.
> >>
> >> Is this a bug in the current 4.1 branch?
> >>
> >>
> >>
> --

Re: Test Result for test-smoke-matrix #559

[Prasanna Santhanam]

Here's the latest run, there are only 7 failures left to have a fully 
successful run.

Test Run: #561

Total:94
Fail :7
Skip :2


name   passfailskip
test_vm_life_cycle/  10   0   0
test_global_settings/ 1   0   0
test_affinity_groups/ 0   1   0
test_deploy_vm/   1   0   0
test_network_acl/ 1   0   0
test_regions/ 1   0   0
test_resource_detail/ 1   0   0
test_pvlan/   1   0   0
test_iso/ 5   0   1
test_deploy_vm_with_userdata/ 2   0   0
test_routers/10   0   0
test_disk_offerings/  3   0   0
test_scale_vm/0   1   0
test_deploy_vms_with_varied_deploymentplanners/   2   1   0
test_templates/   6   1   1
test_internal_lb/ 1   0   0
test_nic/ 1   0   0
test_portable_publicip/   2   0   0
test_non_contigiousvlan/  1   0   0
test_ssvm/   10   0   0
test_network/ 7   3   0
test_public_ip_range/ 1   0   0
test_vm_snapshots/3   0   0
test_volumes/ 9   0   0
test_guest_vlan_range/1   0   0
test_privategw_acl/   1   0   0
test_service_offerings/   4   0   0



Regressions

name
   durationage
integration.smoke.test_templates.TestCreateTemplate.test_01_create_template 
 51.686  1
integration.smoke.test_network.TestLoadBalancingRule.test_01_create_lb_rule_src_nat
  66.749  1
integration.smoke.test_network.TestReleaseIP.test_releaseIP 
171.407  1

Failures

name
durationage
integration.smoke.test_affinity_groups.TestDeployVmWithAffinityGroup.test_DeployVmAntiAffinityGroup
0.584 28
integration.smoke.test_scale_vm.TestScaleVm.test_01_scale_vm
  40.644 36
integration.smoke.test_deploy_vms_with_varied_deploymentplanners.TestDeployVmWithVariedPlanners.test_deployvm_userdispersing
  87.437147
integration.smoke.test_network.TestLoadBalancingRule.test_02_create_lb_rule_non_nat
   15.347 36

Fixed

name
   durationage
integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso
 71.225  0
integration.smoke.test_templates.TestTemplates.test_03_delete_template  
  5.19   0
integration.smoke.test_templates.TestTemplates.test_04_extract_template 
  5.205  0
integration.smoke.test_network.TestAssignRemoveLB.test_assign_and_removal_lb
458.79   0
integration.smoke.test_network.TestPortForwarding.test_01_port_fwd_on_src_nat   
111.604  0
integration.smoke.test_network.TestPortForwarding.test_02_port_fwd_on_non_src_nat
30.584  0
integration.smoke.test_vm_snapshots.TestVmSnapshot.test_01_create_vm_snapshots  
 98.616  0
integration.smoke.test_vm_snapshots.TestVmSnapshot.test_02_revert_vm_snapshots  
171.544  0
integration.smoke.test_vm_snapshots.TestVmSnapshot.test_03_delete_vm_snapshots  
185.229  0
integration.smoke.test_service_offerings.TestServiceOfferings.test_04_change_offering_small
 107.035  0


-- 
Prasanna.,


Powered by BigRock.com

4.2 branch with devcloud not working properly.

[Thomas O'Dowd]

Hi all,

checked out 4.2 branch today. New build, deploydb and start management
server. then deploysvr... on the management server terminal logs, I can
see a new exception that wasn't on master last week.

ERROR [cloud.vm.VirtualMachineManagerImpl] (consoleproxy-1:) Failed to start 
instance VM[ConsolePr
oxy|v-2-VM]
com.cloud.utils.exception.CloudRuntimeException: Failed to create template 
storage pool entry
at 
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl.create(PrimaryDataStoreImp
l.java:237)
at 
org.apache.cloudstack.storage.volume.VolumeServiceImpl.createBaseImageAsync(VolumeServi
ceImpl.java:352)
at 
org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(Vo
lumeServiceImpl.java:490)
at 
com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2479)
at 
com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2536)
at 
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:851)
at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550)
at 
com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsoleProxyManagerImpl.java:
556)
at 
com.cloud.consoleproxy.ConsoleProxyManagerImpl.allocCapacity(ConsoleProxyManagerImpl.ja
va:927)
at 
com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:
1664)
at 
com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:
157)
at 
com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111)
at 
com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33)
at 
com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81)
at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at 
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Schedul
edThreadPoolExecutor.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
INFO  [xen.resource.CitrixResourceBase] (DirectAgent-6:) VM does not exist on 
XenServer9d4c9db8-32f7-25c3-0435-eab4bf3adcea
ERROR [network.element.SspElement] (consoleproxy-1:) ReservationContext was 
null for 
NicProfile[5-2-65d519e9-b735-4585-8a92-5dd2cb8d9f06-192.168.56.151-vlan://untagged
 Ntwk[204|Guest|6]
ERROR [network.element.SspElement] (consoleproxy-1:) ReservationContext was 
null for NicProfile[6-2-null-null-null Ntwk[202|Control|3]
ERROR [network.element.SspElement] (consoleproxy-1:) ReservationContext was 
null for NicProfile[7-2-null-null-null Ntwk[201|Management|2]
WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:) Exception 
while trying to start console proxy
com.cloud.exception.AgentUnavailableException: Resource [Host:1] is 
unreachable: Host 1: Unable to start instance due to Failed to create template 
storage pool entry
at 
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:944)
at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550)
at 
com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsoleProxyManagerImpl.java:556)
at 
com.cloud.consoleproxy.ConsoleProxyManagerImpl.allocCapacity(ConsoleProxyManagerImpl.java:927)
at 
com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:1664)
at 
com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:157)
at 
com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111)
at 
com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33)
at 
com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81)
at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at 
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecu

[DISCUSS] unanswered questions

[Daan Hoogland]

H,

This might be more appropriate on the marketing list but it concerns
contents here; Between Thursday and Saturday 6 questions where posed on
this list that have not been replied to. Starting to work on cloudstack
this happened to me as well a couple of times. Given that people take the
trouble to ask, they are either trying to contribute or evaluating
cloudstack for usage. In both cases it is missed chance if we let those
people pass by.

At a first glance it would seem there are two kind of questions that don't
get answered:
- boring ones
- difficult ones
- unclear ones

Do more people see this as an issue?

I would propose a chasing schedule, in which people are 'on duty' for a day
and try to find answers for all the questions that didn't get answered in
'their day'.

Yes I am volunteering if at least 8 people participate.

regards,
Daan

Re: 4.2 branch with devcloud not working properly.

[Prasanna Santhanam]

On Mon, Jul 01, 2013 at 02:26:26PM +0900, Thomas O'Dowd wrote:
> Hi all,
> 
> checked out 4.2 branch today. New build, deploydb and start management
> server. then deploysvr... on the management server terminal logs, I can
> see a new exception that wasn't on master last week.
> 
 
> The system vms do eventually get launched but when I stop them and
> restart the management server it never starts them again.
> 
> Any ideas? I've been testing with devcloud like this for a while now so
> I don't think it's something I'm doing.
> 
I reset the devcloud image to the base snapshot on virtualbox and
rebuilt on 4.2 and didn't find any exceptions. Then I stopped
management server,  and destroyed my systemVMs and they came back up
fine.

Edison mentioned the issue was with systemvm.iso last week
http://markmail.org/message/c4ihlzu7lxohhc5k

Can you retry by reseting devcloud?

-- 
Prasanna.,


Powered by BigRock.com

Re: [DISCUSS] unanswered questions

[Prasanna Santhanam]

On Mon, Jul 01, 2013 at 07:34:00AM +0200, Daan Hoogland wrote:
> H,
> 
> This might be more appropriate on the marketing list but it concerns
> contents here; Between Thursday and Saturday 6 questions where posed on
> this list that have not been replied to. Starting to work on cloudstack
> this happened to me as well a couple of times. Given that people take the
> trouble to ask, they are either trying to contribute or evaluating
> cloudstack for usage. In both cases it is missed chance if we let those
> people pass by.
> 
> At a first glance it would seem there are two kind of questions that don't
> get answered:
> - boring ones
> - difficult ones
> - unclear ones
> 
> Do more people see this as an issue?
> 

Sometimes yes. Do you mean dev@ and users@? OR just dev@?

> I would propose a chasing schedule, in which people are 'on duty' for a day
> and try to find answers for all the questions that didn't get answered in
> 'their day'.
> 

Don't know how strictly one can adhere to this since most of us have
$dayjob duties.

> Yes I am volunteering if at least 8 people participate.
> 

-- 
Prasanna.,


Powered by BigRock.com

Re: [DISCUSS] unanswered questions

[Daan Hoogland]

On Mon, Jul 1, 2013 at 7:43 AM, Prasanna Santhanam  wrote:

> On Mon, Jul 01, 2013 at 07:34:00AM +0200, Daan Hoogland wrote:
> > H,
> >
> > This might be more appropriate on the marketing list but it concerns
> > contents here; Between Thursday and Saturday 6 questions where posed on
> > this list that have not been replied to. Starting to work on cloudstack
> > this happened to me as well a couple of times. Given that people take the
> > trouble to ask, they are either trying to contribute or evaluating
> > cloudstack for usage. In both cases it is missed chance if we let those
> > people pass by.
> >
> > At a first glance it would seem there are two kind of questions that
> don't
> > get answered:
> > - boring ones
> > - difficult ones
> > - unclear ones
> >
> > Do more people see this as an issue?
> >
>
> Sometimes yes. Do you mean dev@ and users@? OR just dev@?
>
I must confess I am guilty of not answerring any questions on users@.. So I
mean dev@.. but I can imagine the problem being present there as well.


>
> > I would propose a chasing schedule, in which people are 'on duty' for a
> day
> > and try to find answers for all the questions that didn't get answered in
> > 'their day'.
> >
>
> Don't know how strictly one can adhere to this since most of us have
> $dayjob duties.
>
> > Yes I am volunteering if at least 8 people participate.
> >
>
> --
> Prasanna.,
>
> 
> Powered by BigRock.com
>
>

Re: Review Request 12184: Fix for defect CLOUDSTACK-2927

[Likitha Shetty]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/12184/#review22587
---

Ship it!


Ship It!

- Likitha Shetty


On June 29, 2013, 12:28 a.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12184/
> ---
> 
> (Updated June 29, 2013, 12:28 a.m.)
> 
> 
> Review request for cloudstack and Prachi Damle.
> 
> 
> Bugs: CLOUDSTACK-2927
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Updated cloud.spec to package from  awsapi/resource/Axis2/axis2.xml  
> cloudstack-bridge/webapps/awsapi/WEB-INF/conf
> 
> 
> Diffs
> -
> 
> 
> Diff: https://reviews.apache.org/r/12184/diff/
> 
> 
> Testing
> ---
> 
> tested 
> 
> 
> File Attachments
> 
> 
> File added
>   
> https://reviews.apache.org/media/uploaded/files/2013/06/29/0001-Adding-axis2.xml-to-cloudstack-bridge-webapps-awsapi.patch
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

Re: Suggestion needed for CLOUDSTACK-212

[Dharmesh Kakadia]

Hi David,

I have submitted a patch yesterday. It migrates com.cloud.network o
org.apache.network. Please let me know if this is fine so that I can go on
for the rest of the packages.

Thanks,
Dharmesh


On Sat, Jun 29, 2013 at 10:09 PM, David Nalley  wrote:

> On Fri, Jun 28, 2013 at 4:05 AM, Sebastien Goasguen 
> wrote:
> >
> > On Jun 27, 2013, at 1:23 PM, Dharmesh Kakadia 
> wrote:
> >
> >> Hi,
> >>
> >> I misunderstood the feature freeze. This has been assigned to fix in
> >> Version 4.2 on jira. As per this discussion, should I change it to 4.3 ?
> >
> > Dharmesh, can you give us the pointer to github where you put the latest
> changes on this ?
> >
> > Did you rebase against the latest master lately ?
> >
> > -sebastien
> >
>
> Dharmesh:
> 4.2 has branched, and I'd like to get this up for review - can you get
> us a patch and push it to ReviewBoard?
>
> --David
>

Re: Review Request 12184: Fix for defect CLOUDSTACK-2927

[ASF Subversion and Git Services]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/12184/#review22588
---


Commit b4f6b57ef5242a2faf9df386aaff6e00ad388e03 in branch refs/heads/master 
from Rayeesn
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b4f6b57 ]

Adding axis2.xml to cloudstack-bridge/webapps/awsapi/WEB-INF/conf as part of 
defect CLOUDSTACK-2927


- ASF Subversion and Git Services


On June 29, 2013, 12:28 a.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12184/
> ---
> 
> (Updated June 29, 2013, 12:28 a.m.)
> 
> 
> Review request for cloudstack and Prachi Damle.
> 
> 
> Bugs: CLOUDSTACK-2927
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Updated cloud.spec to package from  awsapi/resource/Axis2/axis2.xml  
> cloudstack-bridge/webapps/awsapi/WEB-INF/conf
> 
> 
> Diffs
> -
> 
> 
> Diff: https://reviews.apache.org/r/12184/diff/
> 
> 
> Testing
> ---
> 
> tested 
> 
> 
> File Attachments
> 
> 
> File added
>   
> https://reviews.apache.org/media/uploaded/files/2013/06/29/0001-Adding-axis2.xml-to-cloudstack-bridge-webapps-awsapi.patch
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

Re: [DISCUSS] unanswered questions

[Prasanna Santhanam]

On Mon, Jul 01, 2013 at 07:57:11AM +0200, Daan Hoogland wrote:
> On Mon, Jul 1, 2013 at 7:43 AM, Prasanna Santhanam  wrote:
> 
> > On Mon, Jul 01, 2013 at 07:34:00AM +0200, Daan Hoogland wrote:
> > > H,
> > >
> > > This might be more appropriate on the marketing list but it concerns
> > > contents here; Between Thursday and Saturday 6 questions where posed on
> > > this list that have not been replied to. Starting to work on cloudstack
> > > this happened to me as well a couple of times. Given that people take the
> > > trouble to ask, they are either trying to contribute or evaluating
> > > cloudstack for usage. In both cases it is missed chance if we let those
> > > people pass by.
> > >
> > > At a first glance it would seem there are two kind of questions that
> > don't
> > > get answered:
> > > - boring ones
> > > - difficult ones
> > > - unclear ones
> > >
> > > Do more people see this as an issue?
> > >
> >
> > Sometimes yes. Do you mean dev@ and users@? OR just dev@?
> >
> I must confess I am guilty of not answerring any questions on users@.. So I
> mean dev@.. but I can imagine the problem being present there as well.
> 

users@ needs more people because I see difficult questions there
often. dev@ just needs attention from folks working on the related
piece of code and that's easier to get by Cc-ing the person if they've
missed it. Given that the question has remained unanswered for a
while.

For boring and unclear questions what is reqd is a page that describes
"how to get your questions answered on the cloudstack mailing lists?".
Other communities I've noticed have this sort of a page. 


-- 
Prasanna.,


Powered by BigRock.com

Re: Review Request 12184: Fix for defect CLOUDSTACK-2927

[ASF Subversion and Git Services]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/12184/#review22589
---


Commit 9b722f4ccc0f6fb3ee4a34297593fe01fc23b4d7 in branch refs/heads/4.2 from 
Rayeesn
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9b722f4 ]

Adding axis2.xml to cloudstack-bridge/webapps/awsapi/WEB-INF/conf as part of 
defect CLOUDSTACK-2927


- ASF Subversion and Git Services


On June 29, 2013, 12:28 a.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12184/
> ---
> 
> (Updated June 29, 2013, 12:28 a.m.)
> 
> 
> Review request for cloudstack and Prachi Damle.
> 
> 
> Bugs: CLOUDSTACK-2927
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Updated cloud.spec to package from  awsapi/resource/Axis2/axis2.xml  
> cloudstack-bridge/webapps/awsapi/WEB-INF/conf
> 
> 
> Diffs
> -
> 
> 
> Diff: https://reviews.apache.org/r/12184/diff/
> 
> 
> Testing
> ---
> 
> tested 
> 
> 
> File Attachments
> 
> 
> File added
>   
> https://reviews.apache.org/media/uploaded/files/2013/06/29/0001-Adding-axis2.xml-to-cloudstack-bridge-webapps-awsapi.patch
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

changing bug severity

[Prasanna Santhanam]

I've noticed bugs change severity from Major->Critical->Blocker and
vice-versa without reason. Can the bug reporters please mention the
reason as to how something :

a) blocks movement on the feature/installation/cloudstack in general
b) affects deployment and does not have workarounds via the API
c) troubleshooting done with respect to a and b.

Here's some light reading on how to have bugs resolved faster:
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

Thanks,

-- 
Prasanna.,


Powered by BigRock.com

Re: Master build problem

[Prasanna Santhanam]

On Sun, Jun 30, 2013 at 07:14:38PM +, Paul Angus wrote:
> Hi Prasanna,
> 
> Here is the section from the componentContext.xml file.  The 
> username/password in the user table is admin / 0.724297075275608
> 
> The state was is "disabled" by default I changed it to enabled but it didn't 
> make a difference.

There is some kind of bug here. Can you tell us the steps to reproduce
this from a fresh build? You will need to begin by wiping out the DB,
doing the build, deploydb and a jetty:run.

What happens is that management server saves random values for
user/password on startup. In another separate class it sets the
password to default of admin/password based on the authenticator
enabled. It looks like we randomized the password but failed to set it
to defaults.
-- 
Prasanna.,


Powered by BigRock.com