Re: [4.6] Trouble with virtual router

[Marcus]

So it could be a systemvm template change, perhaps?

On Wed, Apr 29, 2015 at 11:13 PM, Mike Tutkowski
 wrote:
> I logged into the VR, noticed the IP addresses weren't showing up as
> expected when I ran ifconfig, then I restarted networking services, which
> set the IP addresses up properly.
>
> On Thu, Apr 30, 2015 at 12:08 AM, Marcus  wrote:
>
>> Logged into the router?
>>
>>
>> On Wed, Apr 29, 2015 at 10:58 PM, Mike Tutkowski
>>  wrote:
>> > Well, I seem to be able to reproduce this every time I start up the VR in
>> > my environment.
>> >
>> > I'm not sure, though, if this is only my environment or if other people
>> who
>> > are making brand new CS clouds with 4.6 also see this issue.
>> >
>> > On Wed, Apr 29, 2015 at 11:50 PM, Daan Hoogland > >
>> > wrote:
>> >
>> >> Op do 30 apr. 2015 om 07:26 schreef Mike Tutkowski <
>> >> mike.tutkow...@solidfire.com>:
>> >> ...
>> >>
>> >>
>> >> > Should I open a ticket for this?
>> >> >
>> >> if you can reproduce, please.
>> >>
>> >
>> >
>> >
>> > --
>> > *Mike Tutkowski*
>> > *Senior CloudStack Developer, SolidFire Inc.*
>> > e: mike.tutkow...@solidfire.com
>> > o: 303.746.7302
>> > Advancing the way the world uses the cloud
>> > *™*
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> *™*

Re: [4.6] Trouble with virtual router

[Mike Tutkowski]

That's what I'm thinking.

On Thu, Apr 30, 2015 at 1:04 AM, Marcus  wrote:

> So it could be a systemvm template change, perhaps?
>
> On Wed, Apr 29, 2015 at 11:13 PM, Mike Tutkowski
>  wrote:
> > I logged into the VR, noticed the IP addresses weren't showing up as
> > expected when I ran ifconfig, then I restarted networking services, which
> > set the IP addresses up properly.
> >
> > On Thu, Apr 30, 2015 at 12:08 AM, Marcus  wrote:
> >
> >> Logged into the router?
> >>
> >>
> >> On Wed, Apr 29, 2015 at 10:58 PM, Mike Tutkowski
> >>  wrote:
> >> > Well, I seem to be able to reproduce this every time I start up the
> VR in
> >> > my environment.
> >> >
> >> > I'm not sure, though, if this is only my environment or if other
> people
> >> who
> >> > are making brand new CS clouds with 4.6 also see this issue.
> >> >
> >> > On Wed, Apr 29, 2015 at 11:50 PM, Daan Hoogland <
> daan.hoogl...@gmail.com
> >> >
> >> > wrote:
> >> >
> >> >> Op do 30 apr. 2015 om 07:26 schreef Mike Tutkowski <
> >> >> mike.tutkow...@solidfire.com>:
> >> >> ...
> >> >>
> >> >>
> >> >> > Should I open a ticket for this?
> >> >> >
> >> >> if you can reproduce, please.
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > *Mike Tutkowski*
> >> > *Senior CloudStack Developer, SolidFire Inc.*
> >> > e: mike.tutkow...@solidfire.com
> >> > o: 303.746.7302
> >> > Advancing the way the world uses the cloud
> >> > *™*
> >>
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the cloud
> > *™*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
*™*

Jenkins build is still unstable: simulator-singlerun #1171

[jenkins]

See 

Re: marvin test cases + travis

[Sebastien Goasguen]

> On Apr 30, 2015, at 8:35 AM, Rajani Karuturi  wrote:
> 
> Hi Abhi,
> Can we also add findbugs check in travis?
> 

note that there are other SaaS services like Travis that we could use…like 
coveralls, tools to create packages etc…

literally any CI/CD can be outsourced...

> ~Rajani
> 
> On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
> 
>> 
>>There are more than 10 additional suites that can still be included to
>> the travis-CI.
>> Since the current set runs comfortably I will go ahead and add more. If
>> the system gets overloaded, then we can balance the kind of test suites and
>> amount of test suits that run comfortably on travis.
>> 
>> -abhi
>> 
>> 
>> 
>> 
>> Find out more about ShapeBlue and our range of CloudStack related services
>> 
>> IaaS Cloud Design & Build<
>> http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Software Engineering<
>> http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure Support<
>> http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses<
>> http://shapeblue.com/cloudstack-training/>
>> 
>> 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 a
>> company incorporated in India and is operated under license from Shape Blue
>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
>> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
>> a company registered by The Republic of South Africa and is traded under
>> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>> 

Re: [DISCUSS] 4.6 release management

[Sebastien Goasguen]

> On Apr 29, 2015, at 9:49 PM, Marcus  wrote:
> 
> After reviewing the history as mentioned by Daan, unless we propose
> and vote on a newer workflow model I think the best we can do is to
> simply be more strict about commits to master. They all need to be
> merges that have been tested against master before merge. This will in
> theory make master more stable, but doesn't really change the workflow
> we've already agreed upon and have been working under (although
> bugfixes sometimes were not coming in from branches, and cherry-picked
> bugfixes from branches will need to go into a branch first, tested
> against master, and merged to master). We can essentially set a date
> and do that any time, with some advance notice that direct commits
> will be reverted.

Yes +1.

-Set a date
-Tag master for reference
-Find a volunteer or two to RM master
-automatic revert on master if not from RM
-all commits to master come from PR, need clear review and green tests
-harden master (basic QA process), release 4.6 as a tag on master
-all features and fixes need to be made on branches or forks and onus is on 
devs to rebase to master
-brings everyone onto 4.6 (make sure we have upgrade paths from 4.3, 4.4, etc)
-from there forward only maintain a linear release through master

Feel free to add, tweak

PS: No need to vote if we have consensus. Taking a clue from ASF members, votes 
should be avoided at all cost, they mean that we do not have clear consensus.


> 
> On Sat, Apr 18, 2015 at 12:50 AM, Sebastien Goasguen  wrote:
>> 
>>> On Apr 18, 2015, at 8:36 AM, Marcus  wrote:
>>> 
>>> Have they diverged that much? Due to cherry-picking, I guess.
>>> Otherwise you should be able to do it cleanly.
>>> 
>>> There's a good opportunity to do this next release. Instead of
>>> creating a release branch, we freeze master and start creating dev
>>> branches.
>> 
>> +1
>> 
>> This just amounts to treating master now like a release branch. Getting back 
>> to PL suggestion, that means
>> that any commit to master would be through a PR or MERGE request on the ML. 
>> Anything else will be reverted by the RM.
>> 
>> Marcus, do you feel like writing down a little process for this and some 
>> dates that we can target.
>> It would be nice to do this for 4.6.
>> 
>>> 
>>> On Fri, Apr 17, 2015 at 10:46 PM, Daan Hoogland  
>>> wrote:
 We heavily invested in code now on master. Not looking forward to
 backporting that.
 
 mobile dev with bilingual spelling checker used (read at your own risk)
 Op 17 apr. 2015 21:02 schreef "Marcus" :
 
> Well, would we just swap the last release branch with master? Master
> is the dev branch, and the last release is really what we have as a
> stable branch.
> 
> On Fri, Apr 17, 2015 at 8:44 AM, Daan Hoogland 
> wrote:
>> On Fri, Apr 17, 2015 at 2:43 AM, Sebastien Goasguen 
> wrote:
>>> 
 On Apr 17, 2015, at 12:49 AM, Pierre-Luc Dion 
> wrote:
 
 Today during the CloudStackdays  we did a round table about Release
 management targeting the next 4.6 releases.
 
 
 Quick bullet point discussions:
 
 ideas to change release planning
 
 - Plugin contribution is complicated because often  a new plugin
> involve
 change on the core:
- ex: storage plugin involve changes on Hypervisor code
 - There is an idea of going on a 2 weeks release model which could
 introduce issue the database schema.
 - Database schema version should be different then the application
 version.
 - There is a will to enforce git workflow in 4.6  and trigger
> simulator
 job on  PullRequest.
 - Some people (I'm part of them) are concerned on our current way of
 supporting and back porting fixes to multiple release (4.3.x, 4.4.x,
 4.5.x). But the current level of confidence against latest release
> is low,
 so that need to be improved.
 
 
 So, the main messages is that w'd like to improve the release
> velocity, and
 release branch stability.  so we would like to propose few change in
> the
 way we would add code to the 4.6 branch as follow:
 
 - All new contribution to 4.6 would be thru Pull Request or merge
> request,
 which would trigger a simulator job, ideally only if that pass the PR
> would
 be accepted and automatically merged.  At this time, I think we pretty
> much
 have everything in place to do that. At a first step we would use
 simulator+marvin jobs then improve tests coverage from there.
>>> 
>>> +1
>>> 
>>> We do need to realize what this means and be all fine with it.
>>> 
>>> It means that if someone who is not RM directly commits to the release
> branch, the commit will be reverted.
>>> And that from the beginning of the bra

Re: marvin test cases + travis

[Abhinandan Prateek]

> On 30-Apr-2015, at 12:05 pm, Rajani Karuturi  wrote:
>
> Hi Abhi,
> Can we also add findbugs check in travis?
>

Let me check the status of findbug, if all the issues are resolved then we can 
make it part of CI.
If not we can make it part of build, and generate and publish the findbug 
reports so that people can fix the issues.

> ~Rajani
>
> On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
>>
>>There are more than 10 additional suites that can still be included to
>> the travis-CI.
>> Since the current set runs comfortably I will go ahead and add more. If
>> the system gets overloaded, then we can balance the kind of test suites and
>> amount of test suits that run comfortably on travis.
>>
>> -abhi
>>
>>
>>
>>
>> Find out more about ShapeBlue and our range of CloudStack related services
>>
>> IaaS Cloud Design & Build<
>> http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Software Engineering<
>> http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure Support<
>> http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses<
>> http://shapeblue.com/cloudstack-training/>
>>
>> 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 a
>> company incorporated in India and is operated under license from Shape Blue
>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
>> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
>> a company registered by The Republic of South Africa and is traded under
>> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>>

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

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 a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Ubuntu packages on http://cloudstack.apt-get.eu/ have typo (32bit repo)

[Ilia Shakitko]

Hi all,

There is a typo found in a repo: http://cloudstack.apt-get.eu/

http://cloudstack.apt-get.eu/ubuntu/dists/trusty/4.5/
http://cloudstack.apt-get.eu/ubuntu/dists/trusty/4.6/


Both folders contain a subfolder: “binary-i385” and that breaks repo is trying 
to get update for a 32bit version.

It should be: “binary-i-386”

Kind regards,

Ilia Shakitko
Innovation Engineer
LeaseWeb Technologies B.V.

T: +31 20 316 0235

E: i.shaki...@tech.leaseweb.com
W: www.leaseweb.com

Luttenbergweg 8,1101 EC Amsterdam,  Netherlands

Jenkins build is still unstable: simulator-singlerun #1172

[jenkins]

See 

[GitHub] cloudstack pull request: CLOUDSTACK-8413: Fixed resource tags on d...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/194


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-8414: [Hyper-V] Fixed template...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/195


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-8416: added support for FIPS c...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/196


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-8420: [Hyper-V] Fixed number f...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/201


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-8418: [Hyper-V] use systemvm.i...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/198


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-8419: [Hyper-V] corrected the ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/200


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-8417 : [Hyper-V] Added support...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/197


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-8422: Fixed unable to delete z...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/202


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-8423: [Xenserver] Improved the...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/204


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: minor issues seen in travis.yml

[Rohit Yadav]

Hi Raja,

Thanks for sharing. We’ll fix it.

> On 30-Apr-2015, at 6:12 am, Raja Pullela  wrote:
>
> Hi,
>
> I saw couple of issue in travis.yml -
>
> -  3rd line:  "smoke/smoke/test_reset_vm_on_reboot" - it should be 
> "smoke/test_reset_vm_on_reboot"
>
> -  7th line: component/test_acl_isolatednetwork - is listed twice
> will be creating a ticket but wanted to inform ahead.
>
> best,
> Raja

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab



Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

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 a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

[GitHub] cloudstack pull request: Skipping change service offering test for...

[sanju1010]

GitHub user sanju1010 opened a pull request:

https://github.com/apache/cloudstack/pull/213

Skipping change service offering test for LXC since this is not applicable 
to containers



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sanju1010/cloudstack lxc

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/213.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #213


commit b4fb221b56ef75e44be3f72d76894beba9bd65f8
Author: sanjeev 
Date:   2015-04-30T09:09:36Z

Skipping change service offering test for LXC since this is not applicable 
to containers




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: minor issues seen in travis.yml

[Rohit Yadav]

On a second look I did not find the issues you shared on 4.5 or master? Did not 
find the first issue, the second one has two tests: 
component/test_acl_isolatednetwork_delete component/test_acl_isolatednetwork  
(both are different with the same prefix).

> On 30-Apr-2015, at 6:12 am, Raja Pullela  wrote:
>
> Hi,
>
> I saw couple of issue in travis.yml -
>
> -  3rd line:  "smoke/smoke/test_reset_vm_on_reboot" - it should be 
> "smoke/test_reset_vm_on_reboot"
>
> -  7th line: component/test_acl_isolatednetwork - is listed twice
> will be creating a ticket but wanted to inform ahead.

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab



Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

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 a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

[GitHub] cloudstack pull request: Skipping change service offering test for...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/213


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-8431: [Hyper-V] Fixed VM deplo...

[anshul1886]

GitHub user anshul1886 opened a pull request:

https://github.com/apache/cloudstack/pull/214

CLOUDSTACK-8431: [Hyper-V] Fixed VM deployment failing when the stale vhd 
already exists

Now generating guid when the template copy from secondary to primary 
storage requested instead of using it same as secondary

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/anshul1886/cloudstack-1 CLOUDSTACK-8431

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/214.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #214


commit 6bcbf3a22d1a0e1fe20c7e01ca8b0e538d6cd198
Author: Anshul Gangwar 
Date:   2015-04-24T09:53:18Z

CLOUDSTACK-8431: [Hyper-V] Fixed VM deployment failing when the stale vhd 
already exists
Now generating guid when the template copy from secondary to primary 
storage requested instead of using it same as secondary




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: Fixed a few findbugs issues after the mer...

[karuturi]

GitHub user karuturi opened a pull request:

https://github.com/apache/cloudstack/pull/215

Fixed a few findbugs issues after the merge 0b83559

HttpUploadServerHandler.java:142, DM_BOXED_PRIMITIVE_FOR_PARSING
NfsSecondaryStorageResource.java:2630, DM_BOXED_PRIMITIVE_FOR_PARSING
NfsSecondaryStorageResource.java:2775, DM_DEFAULT_ENCODING
EncryptionUtil.java:59, DM_DEFAULT_ENCODING

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/karuturi/cloudstack upload-findbugs

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/215.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #215


commit d39b99351236aeb23c8d63ef0c57d24f5f445ebf
Author: Rajani Karuturi 
Date:   2015-04-30T06:30:42Z

Fixed a few findbugs issues after the merge 0b83559

HttpUploadServerHandler.java:142, DM_BOXED_PRIMITIVE_FOR_PARSING
NfsSecondaryStorageResource.java:2630, DM_BOXED_PRIMITIVE_FOR_PARSING
NfsSecondaryStorageResource.java:2775, DM_DEFAULT_ENCODING
EncryptionUtil.java:59, DM_DEFAULT_ENCODING




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Jenkins build is still unstable: simulator-4.5-singlerun #228

[jenkins]

See 

Disable treshold for Secondary Storage?

[Andrija Panic]

Hi guys,

just wodering, if the Global Config setting
"pool.storage.capacity.disablethreshold" also applies to Secondary Storage
- since I dont see any dedicated settings for this for Secondary Storage...


Thx

-- 

Andrija Panić

Re: minor issues seen in travis.yml

[Abhinandan Prateek]

> On 30-Apr-2015, at 2:46 pm, Rohit Yadav  wrote:
>
> On a second look I did not find the issues you shared on 4.5 or master? Did 
> not find the first issue, the second one has two tests: 
> component/test_acl_isolatednetwork_delete component/test_acl_isolatednetwork  
> (both are different with the same prefix).

I fixed it.

>
>> On 30-Apr-2015, at 6:12 am, Raja Pullela  wrote:
>>
>> Hi,
>>
>> I saw couple of issue in travis.yml -
>>
>> -  3rd line:  "smoke/smoke/test_reset_vm_on_reboot" - it should be 
>> "smoke/test_reset_vm_on_reboot"
>>
>> -  7th line: component/test_acl_isolatednetwork - is listed twice
>> will be creating a ticket but wanted to inform ahead.
>
> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
>
>
>
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software 
> Engineering
> CloudStack Infrastructure 
> Support
> CloudStack Bootcamp Training 
> Courses
>
> 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 a company 
> incorporated in India and is operated under license from Shape Blue Ltd. 
> Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
> operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
> registered by The Republic of South Africa and is traded under license from 
> Shape Blue Ltd. ShapeBlue is a registered trademark.

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

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 a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Ubuntu packages on http://cloudstack.apt-get.eu/ have typo (32bit repo)

[Wido den Hollander]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 04/30/2015 10:17 AM, Ilia Shakitko wrote:
> Hi all,
> 
> There is a typo found in a repo: http://cloudstack.apt-get.eu/
> 
> http://cloudstack.apt-get.eu/ubuntu/dists/trusty/4.5/ 
> http://cloudstack.apt-get.eu/ubuntu/dists/trusty/4.6/
> 
> 
> Both folders contain a subfolder: “binary-i385” and that breaks
> repo is trying to get update for a 32bit version.
> 
> It should be: “binary-i-386”
> 

Thanks! Stupid typo on my side. I created those directories yesterday
to prepare the mirror for any upcoming releases.

Wido

> Kind regards,
> 
> Ilia Shakitko Innovation Engineer LeaseWeb Technologies B.V.
> 
> T: +31 20 316 0235
> 
> E: i.shaki...@tech.leaseweb.com W:
> www.leaseweb.com
> 
> Luttenbergweg 8,1101 EC Amsterdam,  Netherlands
> 
> 
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJVQf/CAAoJEAGbWC3bPspCIBUQAKushtdDXmCF3SGL66F2+k5E
3zISs8tc9k6c4zw6eXIfhyRn5VOnLjrTpW4T6feqQLgejRI/Nk4CJbfW2J4vwPA9
fhu70UkIq1vsdXnUr/3/ycPYYpJqgpnmGNjoLil2G+rJ4RDYI5pn4UwjaDHBy0bM
gwqRr33xXwYuAX/Wj0xpFHz7y2kCR/CLRGkVNaBnjDobzV0bnWcJZ6aSVPs9Ytm1
E1eeABhRICf47jwVhm0EJlIE3jrRGnA2sOLz7rNcr4oIvrSSiV8CXdZ2LD34ddtY
7OD+hx+wkL3blhRwvhqa+e8JXZCP7RUHluzvvQxLULOIT8Rb+HfnSspsWD2rGhHd
98tQsOkR6MemygCK0piumr0O782exZQVEgf1bkNI9GQ0Qhjkeu3xkir58hkMrH/5
u7/L+RCMWJp8ld6RG1akilgOK2YIo1cHmv0rA1V2z4gUgrW5f11ahArEwy5gQoa1
BKeIncX6Y8s+3yvfyXtQ2PQZ7YHjFbVCbIjtm3dMB4j/f+ZP4jnMFfkbw5IrWExg
fFvbH4fcY6aECaMz+RZKlaR2M/DLl7rPvNcgN3n/rsRWFpMurDNHRMdh1BMnJymA
191A+B8LOWwhkjntWmPFL8x5h5YXSFS2681KfpQAQsXhxJdNE9R62RAl/UIqQuYk
rl3b9bNqqhSCxrQq6scr
=3AmK
-END PGP SIGNATURE-

Re: marvin test cases + travis

[Rajani Karuturi]

Hey Abhi,

In the recent travis runs, its not printing the test case in output (
https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)

It used to print the test case name and status (
https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)

Do you think it can be due to any recent changes?

~Rajani

On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
abhinandan.prat...@shapeblue.com> wrote:

>
> There are more than 10 additional suites that can still be included to
> the travis-CI.
> Since the current set runs comfortably I will go ahead and add more. If
> the system gets overloaded, then we can balance the kind of test suites and
> amount of test suits that run comfortably on travis.
>
> -abhi
>
>
>
>
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build<
> http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software Engineering<
> http://shapeblue.com/cloudstack-software-engineering/>
> CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses<
> http://shapeblue.com/cloudstack-training/>
>
> 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 a
> company incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
> a company registered by The Republic of South Africa and is traded under
> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>

[GitHub] cloudstack pull request: CLOUDSTACK-8431: [Hyper-V] Fixed VM deplo...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/214


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [4.6] Trouble with virtual router

[Wilder Rodrigues]

Hi Mike,

I’m actually using the same VHD as you and it is just working fine.

Have you checked the /var/log/SMlog on your xen host?

Also, if you can check the logs of the SSVM under /var/log/cloud.log and see 
what it says concerning the communication between the SSVM and the agent would 
be nice.

Cheers,
Wilder

On 30 Apr 2015, at 09:19, Mike Tutkowski  wrote:

> That's what I'm thinking.
> 
> On Thu, Apr 30, 2015 at 1:04 AM, Marcus  wrote:
> 
>> So it could be a systemvm template change, perhaps?
>> 
>> On Wed, Apr 29, 2015 at 11:13 PM, Mike Tutkowski
>>  wrote:
>>> I logged into the VR, noticed the IP addresses weren't showing up as
>>> expected when I ran ifconfig, then I restarted networking services, which
>>> set the IP addresses up properly.
>>> 
>>> On Thu, Apr 30, 2015 at 12:08 AM, Marcus  wrote:
>>> 
 Logged into the router?
 
 
 On Wed, Apr 29, 2015 at 10:58 PM, Mike Tutkowski
  wrote:
> Well, I seem to be able to reproduce this every time I start up the
>> VR in
> my environment.
> 
> I'm not sure, though, if this is only my environment or if other
>> people
 who
> are making brand new CS clouds with 4.6 also see this issue.
> 
> On Wed, Apr 29, 2015 at 11:50 PM, Daan Hoogland <
>> daan.hoogl...@gmail.com
> 
> wrote:
> 
>> Op do 30 apr. 2015 om 07:26 schreef Mike Tutkowski <
>> mike.tutkow...@solidfire.com>:
>> ...
>> 
>> 
>>> Should I open a ticket for this?
>>> 
>> if you can reproduce, please.
>> 
> 
> 
> 
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> *™*
 
>>> 
>>> 
>>> 
>>> --
>>> *Mike Tutkowski*
>>> *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkow...@solidfire.com
>>> o: 303.746.7302
>>> Advancing the way the world uses the cloud
>>> *™*
>> 
> 
> 
> 
> -- 
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> *™*

Jenkins build is still unstable: simulator-singlerun #1173

[jenkins]

See 

Re: marvin test cases + travis

[Abhinandan Prateek]

It is possible, I will check.

> On 30-Apr-2015, at 3:43 pm, Rajani Karuturi  wrote:
>
> Hey Abhi,
>
> In the recent travis runs, its not printing the test case in output (
> https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
>
> It used to print the test case name and status (
> https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
>
> Do you think it can be due to any recent changes?
>
> ~Rajani
>
> On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
>>
>>There are more than 10 additional suites that can still be included to
>> the travis-CI.
>> Since the current set runs comfortably I will go ahead and add more. If
>> the system gets overloaded, then we can balance the kind of test suites and
>> amount of test suits that run comfortably on travis.
>>
>> -abhi
>>
>>
>>
>>
>> Find out more about ShapeBlue and our range of CloudStack related services
>>
>> IaaS Cloud Design & Build<
>> http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Software Engineering<
>> http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure Support<
>> http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses<
>> http://shapeblue.com/cloudstack-training/>
>>
>> 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 a
>> company incorporated in India and is operated under license from Shape Blue
>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
>> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
>> a company registered by The Republic of South Africa and is traded under
>> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>>

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

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 a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

RE: minor issues seen in travis.yml

[Raja Pullela]

BTW, looks like Abhi updated the file about 6hrs ago.
This was the file - I looked at:  
https://github.com/apache/cloudstack/blob/7843a092f51569ba003132bc80f87350b66aa5bf/.travis.yml


-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com] 
Sent: Thursday, April 30, 2015 2:46 PM
To: dev@cloudstack.apache.org
Subject: Re: minor issues seen in travis.yml

On a second look I did not find the issues you shared on 4.5 or master? Did not 
find the first issue, the second one has two tests: 
component/test_acl_isolatednetwork_delete component/test_acl_isolatednetwork  
(both are different with the same prefix).

> On 30-Apr-2015, at 6:12 am, Raja Pullela  wrote:
>
> Hi,
>
> I saw couple of issue in travis.yml -
>
> -  3rd line:  "smoke/smoke/test_reset_vm_on_reboot" - it should be 
> "smoke/test_reset_vm_on_reboot"
>
> -  7th line: component/test_acl_isolatednetwork - is listed twice
> will be creating a ticket but wanted to inform ahead.

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab



Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & 
Build
CSForge – rapid IaaS deployment 
framework
CloudStack 
Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training 
Courses

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 a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: marvin test cases + travis

[Rajani Karuturi]

I think its due to this commit
https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77

Here, test file name is changed from testname to [smoke,component]/testname

But, while running each test file in the for loop, it prepends the name
with smoke and hence, it cant find the file and none of the tests in the
file are run



~Rajani

On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
abhinandan.prat...@shapeblue.com> wrote:

> It is possible, I will check.
>
> > On 30-Apr-2015, at 3:43 pm, Rajani Karuturi  wrote:
> >
> > Hey Abhi,
> >
> > In the recent travis runs, its not printing the test case in output (
> > https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
> >
> > It used to print the test case name and status (
> > https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
> >
> > Do you think it can be due to any recent changes?
> >
> > ~Rajani
> >
> > On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> > abhinandan.prat...@shapeblue.com> wrote:
> >
> >>
> >>There are more than 10 additional suites that can still be included
> to
> >> the travis-CI.
> >> Since the current set runs comfortably I will go ahead and add more. If
> >> the system gets overloaded, then we can balance the kind of test suites
> and
> >> amount of test suits that run comfortably on travis.
> >>
> >> -abhi
> >>
> >>
> >>
> >>
> >> Find out more about ShapeBlue and our range of CloudStack related
> services
> >>
> >> IaaS Cloud Design & Build<
> >> http://shapeblue.com/iaas-cloud-design-and-build//>
> >> CSForge – rapid IaaS deployment framework >
> >> CloudStack Consulting
> >> CloudStack Software Engineering<
> >> http://shapeblue.com/cloudstack-software-engineering/>
> >> CloudStack Infrastructure Support<
> >> http://shapeblue.com/cloudstack-infrastructure-support/>
> >> CloudStack Bootcamp Training Courses<
> >> http://shapeblue.com/cloudstack-training/>
> >>
> >> 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 a
> >> company incorporated in India and is operated under license from Shape
> Blue
> >> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
> Brasil
> >> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd
> is
> >> a company registered by The Republic of South Africa and is traded under
> >> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
> >>
>
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build<
> http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software Engineering<
> http://shapeblue.com/cloudstack-software-engineering/>
> CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses<
> http://shapeblue.com/cloudstack-training/>
>
> 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 a
> company incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
> a company registered by The Republic of South Africa and is traded under
> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>

Re: [DISCUSS] State of 4.5 and testing in local environments

[David Nalley]

Just as an FYI, we've dramatically increased Travis capacity.

https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci

On Thursday, April 30, 2015, Abhinandan Prateek <
abhinandan.prat...@shapeblue.com> wrote:

> Yes, lot of sanity testing can be accomplished by the automated test
> suites that we already have.
>
> There are still lot of tests that can be run using the travis-CI, (need to
> see how many more without loading the travis system). Some of the companies
> including Shapeblue are already running most or all of the test cases.
> This means that the latest branches  (4.5, 4.6) already have a level of
> sanity.
>
> At this stage we should define the amount of coverage that automation
> provides and also look at the areas where automation is failing, and work
> towards covering it.  We need this as we continue to find issues that are
> not covered by automation.
>
> I agree that while releasing if issues are found then we fix them and also
> write tests so that these do not reoccur.
>
> -abhi
>
> > On 30-Apr-2015, at 7:42 am, David Nalley >
> wrote:
> >
> > The problem is really two fold.
> > Cutting an RC isn't terribly time consuming, once you've done it a
> > dozen times or so, it goes by pretty quickly.
> >
> > The problem is the time it takes to do any material testing; and that
> > we don't have a way of telling what the status of a candidate is
> > without doing lots of manual testing. We've had multiple cases of
> > having enough binding votes for 4.5.x candidates only for someone to
> > find problems. This leads me (and this could just be my perspective)
> > to let an RC sit for a while - get folks to test it. My experience as
> > a person voting is that rapid churn of RCs leads me to not even
> > attempt to setup a testing environment, much less do any testing. I
> > found that by the time I could get around to testing an RC vote had
> > been cancelled and it had been rerolled, sometimes twice.
> >
> > I've said this before, and I'll toss it out again. I think we have to
> > start 'trusting' the automated tests. We find lots of problems
> > manually, but we don't improve the testing situation for those blocker
> > issues that stopped us from releasing. I'm of the opinion we should
> > release quickly, very quickly. But if we have to spend a week just
> > looking for bugs, that will never fly. So - let the standard be
> > automated tests - and if there's a problem, we create an automated
> > test for it, and solve in a week or two. That will force us to live
> > and die by automated tests.
> >
> > --David
> >
> > On Wed, Apr 29, 2015 at 9:45 AM, Rohit Yadav  > wrote:
> >> Hi Wilder - Thanks we’ll need all the ammo we have :) I’ve already done
> my testings wrt XS 6.2/6.5 and KVM qemu 2.0/2.1/2.2 so will test KVM 1.5
> and VMware 5.5.
> >>
> >> Hi Daan - makes sense, we’re “so" late with 4.5.1 that we need to focus
> on 4.6.0 to avoid delaying it. I’ve asked David regarding co-piloting the
> next 4.5.1 RC since he could be busy and I want to help with lifting some
> weights. I’m planning to do basic tests with VMware today, publish new
> systemvmtemplates tomorrow (I’m already done with KVM and Xen) and plan to
> cut a 4.5.1 RC on Monday and if we don’t hit any blocker or regressions ACS
> 4.5.1 should be released by the end of next week.
> >>
> >>> On 29-Apr-2015, at 2:49 pm, Wilder Rodrigues <
> wrodrig...@schubergphilis.com > wrote:
> >>>
> >>> Hi Rohit,
> >>>
> >>> I will join you in testing 4.5 form next week - just have to finish
> some stuff.
> >>>
> >>> My environments will be:
> >>>
> >>> * Xen 6.2/6.5
> >>> * KVM (qemu 1.5.3 and 2.1)
> >>>
> >>> Let’s rock!
> >>>
> >>> Cheers,
> >>> Wilder
> >>>
> >>> On 28 Apr 2015, at 18:33, Rohit Yadav  > wrote:
> >>>
>  Hi all,
> 
>  ### 4.5 Release Effort
> 
>  I’ve been exhaustively testing ACS 4.5 wrt Xen 6.2, Xen 6.5, KVM
> (qemu 2.0, 2.3) and I feel we’re pretty good but we need testing efforts
> and I want to help drive efforts to releasing ACS 4.5.1 -- if you’ve any
> issues that you would like to get fixed that are either regressions or
> blockers can you please share on this thread? If we don’t find any blockers
> or regressions let us invest in ACS 4.5 testing and release it soon. For
> other minor issues we can always fix them and release 4.5.2 etc if and when
> needed in future.
> 
>  Regarding my 4.5 testing - I’ve tested basic vm life cycle operations
> (deploy, start, stop, destroy/expunge, migrate to another host, migrate to
> another storage pool, deploy using iso) for all cases and found no issues;
> 
>  KVM with basic zone (with/without security groups, SG blockers were
> found and fixed)
>  KVM with Adv zone (with/without security groups, both isolated
> network and VPC worked, networking issues were found and fixed)
>  XenServer 6.2 with basic and adv zones (with/without security groups,
> no SG issues found)
>  XenServer 6.5 with basic and adv zones (with/with

KVM HA

[Budur Nagaraju]

 HI
  New to cloud stack struggled searching for configuring KVM HA unable to
find any document .
  Pls any help to configure KVM HA in cloud stack ,really helps a lot.

Thanks,
Nagaraju

[GitHub] cloudstack pull request: Fixed a few findbugs issues after the mer...

[DaanHoogland]

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/215#issuecomment-97749108
  
LGTM. I will have a pull and build at it.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Jenkins build is still unstable: simulator-singlerun #1174

[jenkins]

See 

Re: marvin test cases + travis

[Rajani Karuturi]

after correcting the test file path, its working fine

https://travis-ci.org/karuturi/cloudstack/jobs/60681263



~Rajani

On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi  wrote:

> I think its due to this commit
>
> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77
>
> Here, test file name is changed from testname to [smoke,component]/testname
>
> But, while running each test file in the for loop, it prepends the name
> with smoke and hence, it cant find the file and none of the tests in the
> file are run
>
>
>
> ~Rajani
>
> On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
>> It is possible, I will check.
>>
>> > On 30-Apr-2015, at 3:43 pm, Rajani Karuturi  wrote:
>> >
>> > Hey Abhi,
>> >
>> > In the recent travis runs, its not printing the test case in output (
>> > https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
>> >
>> > It used to print the test case name and status (
>> > https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
>> >
>> > Do you think it can be due to any recent changes?
>> >
>> > ~Rajani
>> >
>> > On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
>> > abhinandan.prat...@shapeblue.com> wrote:
>> >
>> >>
>> >>There are more than 10 additional suites that can still be included
>> to
>> >> the travis-CI.
>> >> Since the current set runs comfortably I will go ahead and add more. If
>> >> the system gets overloaded, then we can balance the kind of test
>> suites and
>> >> amount of test suits that run comfortably on travis.
>> >>
>> >> -abhi
>> >>
>> >>
>> >>
>> >>
>> >> Find out more about ShapeBlue and our range of CloudStack related
>> services
>> >>
>> >> IaaS Cloud Design & Build<
>> >> http://shapeblue.com/iaas-cloud-design-and-build//>
>> >> CSForge – rapid IaaS deployment framework<
>> http://shapeblue.com/csforge/>
>> >> CloudStack Consulting
>> >> CloudStack Software Engineering<
>> >> http://shapeblue.com/cloudstack-software-engineering/>
>> >> CloudStack Infrastructure Support<
>> >> http://shapeblue.com/cloudstack-infrastructure-support/>
>> >> CloudStack Bootcamp Training Courses<
>> >> http://shapeblue.com/cloudstack-training/>
>> >>
>> >> 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 a
>> >> company incorporated in India and is operated under license from Shape
>> Blue
>> >> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
>> Brasil
>> >> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty
>> Ltd is
>> >> a company registered by The Republic of South Africa and is traded
>> under
>> >> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>> >>
>>
>> Find out more about ShapeBlue and our range of CloudStack related services
>>
>> IaaS Cloud Design & Build<
>> http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Software Engineering<
>> http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure Support<
>> http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses<
>> http://shapeblue.com/cloudstack-training/>
>>
>> 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 a
>> company incorporated in India and is operated under license from Shape Blue
>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
>> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
>> a company registered by The Republic of South Africa and is traded under
>> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>>
>
>

[GitHub] cloudstack pull request: Fixed a few findbugs issues after the mer...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/215


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: marvin test cases + travis

[Abhinandan Prateek]

Yes, thanks for checking. I was worried that now some of them may start timing 
out.
I have another 10 suites tested, will add them once everything seems fine.

-abhi


> On 30-Apr-2015, at 5:32 pm, Rajani Karuturi  wrote:
>
> after correcting the test file path, its working fine
>
> https://travis-ci.org/karuturi/cloudstack/jobs/60681263
>
>
>
> ~Rajani
>
> On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi  wrote:
>
>> I think its due to this commit
>>
>> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77
>>
>> Here, test file name is changed from testname to [smoke,component]/testname
>>
>> But, while running each test file in the for loop, it prepends the name
>> with smoke and hence, it cant find the file and none of the tests in the
>> file are run
>>
>>
>>
>> ~Rajani
>>
>> On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
>> abhinandan.prat...@shapeblue.com> wrote:
>>
>>> It is possible, I will check.
>>>
 On 30-Apr-2015, at 3:43 pm, Rajani Karuturi  wrote:

 Hey Abhi,

 In the recent travis runs, its not printing the test case in output (
 https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)

 It used to print the test case name and status (
 https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)

 Do you think it can be due to any recent changes?

 ~Rajani

 On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
 abhinandan.prat...@shapeblue.com> wrote:

>
>   There are more than 10 additional suites that can still be included
>>> to
> the travis-CI.
> Since the current set runs comfortably I will go ahead and add more. If
> the system gets overloaded, then we can balance the kind of test
>>> suites and
> amount of test suits that run comfortably on travis.
>
> -abhi
>
>
>
>
> Find out more about ShapeBlue and our range of CloudStack related
>>> services
>
> IaaS Cloud Design & Build<
> http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework<
>>> http://shapeblue.com/csforge/>
> CloudStack Consulting
> CloudStack Software Engineering<
> http://shapeblue.com/cloudstack-software-engineering/>
> CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses<
> http://shapeblue.com/cloudstack-training/>
>
> 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 a
> company incorporated in India and is operated under license from Shape
>>> Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
>>> Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty
>>> Ltd is
> a company registered by The Republic of South Africa and is traded
>>> under
> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>
>>>
>>> Find out more about ShapeBlue and our range of CloudStack related services
>>>
>>> IaaS Cloud Design & Build<
>>> http://shapeblue.com/iaas-cloud-design-and-build//>
>>> CSForge – rapid IaaS deployment framework
>>> CloudStack Consulting
>>> CloudStack Software Engineering<
>>> http://shapeblue.com/cloudstack-software-engineering/>
>>> CloudStack Infrastructure Support<
>>> http://shapeblue.com/cloudstack-infrastructure-support/>
>>> CloudStack Bootcamp Training Courses<
>>> http://shapeblue.com/cloudstack-training/>
>>>
>>> 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 a
>>> company incorporated in India and is operated under license from Shape Blue
>>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorpor

[GitHub] cloudstack pull request: Fixed a few findbugs issues after the mer...

[karuturi]

Github user karuturi commented on the pull request:

https://github.com/apache/cloudstack/pull/215#issuecomment-97754239
  
Thanks Daan


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Jenkins build is still unstable: simulator-4.5-singlerun #229

[jenkins]

See 

Re: marvin test cases + travis

[Abhinandan Prateek]

One of the run did timeout. Will balance the runs.

> On 30-Apr-2015, at 5:59 pm, Abhinandan Prateek 
>  wrote:
>
> Yes, thanks for checking. I was worried that now some of them may start 
> timing out.
> I have another 10 suites tested, will add them once everything seems fine.
>
> -abhi
>
>
>> On 30-Apr-2015, at 5:32 pm, Rajani Karuturi  wrote:
>>
>> after correcting the test file path, its working fine
>>
>> https://travis-ci.org/karuturi/cloudstack/jobs/60681263
>>
>>
>>
>> ~Rajani
>>
>> On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi  wrote:
>>
>>> I think its due to this commit
>>>
>>> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77
>>>
>>> Here, test file name is changed from testname to [smoke,component]/testname
>>>
>>> But, while running each test file in the for loop, it prepends the name
>>> with smoke and hence, it cant find the file and none of the tests in the
>>> file are run
>>>
>>>
>>>
>>> ~Rajani
>>>
>>> On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
>>> abhinandan.prat...@shapeblue.com> wrote:
>>>
 It is possible, I will check.

> On 30-Apr-2015, at 3:43 pm, Rajani Karuturi  wrote:
>
> Hey Abhi,
>
> In the recent travis runs, its not printing the test case in output (
> https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
>
> It used to print the test case name and status (
> https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
>
> Do you think it can be due to any recent changes?
>
> ~Rajani
>
> On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
>>
>>  There are more than 10 additional suites that can still be included
 to
>> the travis-CI.
>> Since the current set runs comfortably I will go ahead and add more. If
>> the system gets overloaded, then we can balance the kind of test
 suites and
>> amount of test suits that run comfortably on travis.
>>
>> -abhi
>>
>>
>>
>>
>> Find out more about ShapeBlue and our range of CloudStack related
 services
>>
>> IaaS Cloud Design & Build<
>> http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework<
 http://shapeblue.com/csforge/>
>> CloudStack Consulting
>> CloudStack Software Engineering<
>> http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure Support<
>> http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses<
>> http://shapeblue.com/cloudstack-training/>
>>
>> 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 a
>> company incorporated in India and is operated under license from Shape
 Blue
>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
 Brasil
>> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty
 Ltd is
>> a company registered by The Republic of South Africa and is traded
 under
>> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>>

 Find out more about ShapeBlue and our range of CloudStack related services

 IaaS Cloud Design & Build<
 http://shapeblue.com/iaas-cloud-design-and-build//>
 CSForge – rapid IaaS deployment framework
 CloudStack Consulting
 CloudStack Software Engineering<
 http://shapeblue.com/cloudstack-software-engineering/>
 CloudStack Infrastructure Support<
 http://shapeblue.com/cloudstack-infrastructure-support/>
 CloudStack Bootcamp Training Courses<
 http://shapeblue.com/cloudstack-training/>

 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 err

Jenkins build is still unstable: simulator-singlerun #1175

[jenkins]

See 

[GitHub] cloudstack pull request: CLOUDSTACK-8433: Remove awsapi

[bhaisaab]

GitHub user bhaisaab opened a pull request:

https://github.com/apache/cloudstack/pull/216

CLOUDSTACK-8433: Remove awsapi

Following actions from discussions on dev ML regarding removing awsapi and 
preferring ec2stack. Reference from last PR: 
https://github.com/apache/cloudstack/pull/44 Opening a new one as master has 
changed since then and rebasing caused several conflicts so this PR consists of 
3 patches (to make rebasing easier).

- Removes awsapi and awsapi-setup
- Removes awsapi packaging rules for debian, centos63, centos7, fedora 
20/21
- Removes catalina port 7080 service configs
- Fixes build replace properties for AWSAPILOG
- Removes maven profile for building awsapi and deploying db in 
developer profile
- Removes awsapi db properties usage across codebase
- Removes references from spring xmls, test cases and TransactionLegacy
- Adds sql command to drop database cloudbridge in 
schema-451to460-cleanup.sql

CentOS 7, CentOS 6.3, Debian repository: 
http://packages.bhaisaab.org/cloudstack/nukeawsapi
TravisCI: https://travis-ci.org/apache/cloudstack/builds/60704658


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apache/cloudstack nuke-awsapi

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/216.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #216


commit e8d4ebf022a1838b079f7017b587ed8c1de37e32
Author: Rohit Yadav 
Date:   2015-04-30T14:05:39Z

CLOUDSTACK-8433: remove awsapi and awsapi-setup

Following actions from discussions on dev ML regarding removing awsapi and
prefering ec2stack. Reference from last PR:
https://github.com/apache/cloudstack/pull/44

Signed-off-by: Rohit Yadav 

commit e0eea01b4c718582e6c34d04e5f22b5d4a446d56
Author: Rohit Yadav 
Date:   2015-04-30T14:11:05Z

CLOUDSTACK-8433: remove awsapi rpm and debian packaging

- Removes awsapi packaging rules for debian, centos63, centos7, fedora 20/21
- Removes catalina port 7080 service configs
- Fixes build replace properties for AWSAPILOG
- Removes maven profile for building awsapi and deploying db in developer 
profile

Signed-off-by: Rohit Yadav 

commit 72831ecfecdf5cd437f28c600341dc9ade00b4b7
Author: Rohit Yadav 
Date:   2015-04-30T14:15:39Z

CLOUDSTACK-8433: remove awsapi db usage and add upgrade cleanup path

- Removes awsapi db properties usage across codebase
- Removes references from spring xmls, test cases and TransactionLegacy
- Adds sql command to drop database cloudbridge in 
schema-451to460-cleanup.sql

Signed-off-by: Rohit Yadav 

commit 4435ede72a437ec3adfedf46d429193f3ef039f5
Author: Rohit Yadav 
Date:   2015-04-30T15:43:51Z

CLOUDSTACK-8433: Fix rpm builds, avoid using commons-logging

- Removes commons-logging.properties file introduced with awsapi
- Fixed utils to use log4j instead of commons logging

Signed-off-by: Rohit Yadav 




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [GitHub] cloudstack pull request: CLOUDSTACK-8433: Remove awsapi

[sebgoa]

Rohit, give me couple days :

1-to get the ec2stack donation finished and the code imported.
2-we should merge this once we agree on a 4.6 release management method.



On Apr 30, 2015, at 5:49 PM, bhaisaab  wrote:

> GitHub user bhaisaab opened a pull request:
> 
>https://github.com/apache/cloudstack/pull/216
> 
>CLOUDSTACK-8433: Remove awsapi
> 
>Following actions from discussions on dev ML regarding removing awsapi and 
> preferring ec2stack. Reference from last PR: 
> https://github.com/apache/cloudstack/pull/44 Opening a new one as master has 
> changed since then and rebasing caused several conflicts so this PR consists 
> of 3 patches (to make rebasing easier).
> 
>- Removes awsapi and awsapi-setup
>- Removes awsapi packaging rules for debian, centos63, centos7, fedora 
> 20/21
>- Removes catalina port 7080 service configs
>- Fixes build replace properties for AWSAPILOG
>- Removes maven profile for building awsapi and deploying db in 
> developer profile
>- Removes awsapi db properties usage across codebase
>- Removes references from spring xmls, test cases and TransactionLegacy
>- Adds sql command to drop database cloudbridge in 
> schema-451to460-cleanup.sql
> 
>CentOS 7, CentOS 6.3, Debian repository: 
> http://packages.bhaisaab.org/cloudstack/nukeawsapi
>TravisCI: https://travis-ci.org/apache/cloudstack/builds/60704658
> 
> 
> You can merge this pull request into a Git repository by running:
> 
>$ git pull https://github.com/apache/cloudstack nuke-awsapi
> 
> Alternatively you can review and apply these changes as the patch at:
> 
>https://github.com/apache/cloudstack/pull/216.patch
> 
> To close this pull request, make a commit to your master/trunk branch
> with (at least) the following in the commit message:
> 
>This closes #216
> 
> 
> commit e8d4ebf022a1838b079f7017b587ed8c1de37e32
> Author: Rohit Yadav 
> Date:   2015-04-30T14:05:39Z
> 
>CLOUDSTACK-8433: remove awsapi and awsapi-setup
> 
>Following actions from discussions on dev ML regarding removing awsapi and
>prefering ec2stack. Reference from last PR:
>https://github.com/apache/cloudstack/pull/44
> 
>Signed-off-by: Rohit Yadav 
> 
> commit e0eea01b4c718582e6c34d04e5f22b5d4a446d56
> Author: Rohit Yadav 
> Date:   2015-04-30T14:11:05Z
> 
>CLOUDSTACK-8433: remove awsapi rpm and debian packaging
> 
>- Removes awsapi packaging rules for debian, centos63, centos7, fedora 
> 20/21
>- Removes catalina port 7080 service configs
>- Fixes build replace properties for AWSAPILOG
>- Removes maven profile for building awsapi and deploying db in developer 
> profile
> 
>Signed-off-by: Rohit Yadav 
> 
> commit 72831ecfecdf5cd437f28c600341dc9ade00b4b7
> Author: Rohit Yadav 
> Date:   2015-04-30T14:15:39Z
> 
>CLOUDSTACK-8433: remove awsapi db usage and add upgrade cleanup path
> 
>- Removes awsapi db properties usage across codebase
>- Removes references from spring xmls, test cases and TransactionLegacy
>- Adds sql command to drop database cloudbridge in 
> schema-451to460-cleanup.sql
> 
>Signed-off-by: Rohit Yadav 
> 
> commit 4435ede72a437ec3adfedf46d429193f3ef039f5
> Author: Rohit Yadav 
> Date:   2015-04-30T15:43:51Z
> 
>CLOUDSTACK-8433: Fix rpm builds, avoid using commons-logging
> 
>- Removes commons-logging.properties file introduced with awsapi
>- Fixed utils to use log4j instead of commons logging
> 
>Signed-off-by: Rohit Yadav 
> 
> 
> 
> 
> ---
> 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 enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---

[GitHub] cloudstack pull request: CLOUDSTACK-8433: Remove awsapi

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/216#issuecomment-97861338
  
@runseb -  Sure. I was testing 4.5 today and the awsapi service did not 
work for me, after wasting almost 2 hours to make it work, I tried ec2stack 
which worked out of the box. I thought it would be a good idea to get rid of it 
and promote ec2stack :)

I’ve split the changes in 3 commits to make it easier to rebase/merge. 
I’ll keep this open and hope to merge it next week but am interested in merge 
it now to avoid rebasing efforts again. If ec2stack will get its own git repo 
like docs repos or cloudmonkey - does it matter if we merge this now or next 
week and will this block 4.6 release management?


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Jenkins build is still unstable: simulator-4.5-singlerun #230

[jenkins]

See 

Re: marvin test cases + travis

[David Nalley]

Do we need to ask for an increase in run time?
50 minutes is the OSS default, but the ASF is a paying customer and we
can ask for longer timeouts.

--David

On Thu, Apr 30, 2015 at 10:06 AM, Abhinandan Prateek
 wrote:
> One of the run did timeout. Will balance the runs.
>
>> On 30-Apr-2015, at 5:59 pm, Abhinandan Prateek 
>>  wrote:
>>
>> Yes, thanks for checking. I was worried that now some of them may start 
>> timing out.
>> I have another 10 suites tested, will add them once everything seems fine.
>>
>> -abhi
>>
>>
>>> On 30-Apr-2015, at 5:32 pm, Rajani Karuturi  wrote:
>>>
>>> after correcting the test file path, its working fine
>>>
>>> https://travis-ci.org/karuturi/cloudstack/jobs/60681263
>>>
>>>
>>>
>>> ~Rajani
>>>
>>> On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi  wrote:
>>>
 I think its due to this commit

 https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77

 Here, test file name is changed from testname to [smoke,component]/testname

 But, while running each test file in the for loop, it prepends the name
 with smoke and hence, it cant find the file and none of the tests in the
 file are run



 ~Rajani

 On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
 abhinandan.prat...@shapeblue.com> wrote:

> It is possible, I will check.
>
>> On 30-Apr-2015, at 3:43 pm, Rajani Karuturi  wrote:
>>
>> Hey Abhi,
>>
>> In the recent travis runs, its not printing the test case in output (
>> https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
>>
>> It used to print the test case name and status (
>> https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
>>
>> Do you think it can be due to any recent changes?
>>
>> ~Rajani
>>
>> On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
>> abhinandan.prat...@shapeblue.com> wrote:
>>
>>>
>>>  There are more than 10 additional suites that can still be included
> to
>>> the travis-CI.
>>> Since the current set runs comfortably I will go ahead and add more. If
>>> the system gets overloaded, then we can balance the kind of test
> suites and
>>> amount of test suits that run comfortably on travis.
>>>
>>> -abhi
>>>
>>>
>>>
>>>
>>> Find out more about ShapeBlue and our range of CloudStack related
> services
>>>
>>> IaaS Cloud Design & Build<
>>> http://shapeblue.com/iaas-cloud-design-and-build//>
>>> CSForge – rapid IaaS deployment framework<
> http://shapeblue.com/csforge/>
>>> CloudStack Consulting
>>> CloudStack Software Engineering<
>>> http://shapeblue.com/cloudstack-software-engineering/>
>>> CloudStack Infrastructure Support<
>>> http://shapeblue.com/cloudstack-infrastructure-support/>
>>> CloudStack Bootcamp Training Courses<
>>> http://shapeblue.com/cloudstack-training/>
>>>
>>> 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 a
>>> company incorporated in India and is operated under license from Shape
> Blue
>>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
> Brasil
>>> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty
> Ltd is
>>> a company registered by The Republic of South Africa and is traded
> under
>>> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>>>
>
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build<
> http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software Engineering<
> http://shapeblue.com/cloudstack-software-engineering/>
> CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses<
> http://shapeblue.com/cloudstack-training/>
>
> 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 express

Re: marvin test cases + travis

[Ian Duffy]

> Do we need to ask for an increase in run time?

>From my experience I wouldn't say its required however *it would be very nice*.
At the moment what we do is create new parallel jobs and balance the
tests across them so each job is under 50mins.

Anywho, just my 2c, see what others say/think.

On 30 April 2015 at 17:34, David Nalley  wrote:
> Do we need to ask for an increase in run time?
> 50 minutes is the OSS default, but the ASF is a paying customer and we
> can ask for longer timeouts.
>
> --David
>
> On Thu, Apr 30, 2015 at 10:06 AM, Abhinandan Prateek
>  wrote:
>> One of the run did timeout. Will balance the runs.
>>
>>> On 30-Apr-2015, at 5:59 pm, Abhinandan Prateek 
>>>  wrote:
>>>
>>> Yes, thanks for checking. I was worried that now some of them may start 
>>> timing out.
>>> I have another 10 suites tested, will add them once everything seems fine.
>>>
>>> -abhi
>>>
>>>
 On 30-Apr-2015, at 5:32 pm, Rajani Karuturi  wrote:

 after correcting the test file path, its working fine

 https://travis-ci.org/karuturi/cloudstack/jobs/60681263



 ~Rajani

 On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi  wrote:

> I think its due to this commit
>
> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77
>
> Here, test file name is changed from testname to 
> [smoke,component]/testname
>
> But, while running each test file in the for loop, it prepends the name
> with smoke and hence, it cant find the file and none of the tests in the
> file are run
>
>
>
> ~Rajani
>
> On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
>> It is possible, I will check.
>>
>>> On 30-Apr-2015, at 3:43 pm, Rajani Karuturi  wrote:
>>>
>>> Hey Abhi,
>>>
>>> In the recent travis runs, its not printing the test case in output (
>>> https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
>>>
>>> It used to print the test case name and status (
>>> https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
>>>
>>> Do you think it can be due to any recent changes?
>>>
>>> ~Rajani
>>>
>>> On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
>>> abhinandan.prat...@shapeblue.com> wrote:
>>>

  There are more than 10 additional suites that can still be included
>> to
 the travis-CI.
 Since the current set runs comfortably I will go ahead and add more. If
 the system gets overloaded, then we can balance the kind of test
>> suites and
 amount of test suits that run comfortably on travis.

 -abhi




 Find out more about ShapeBlue and our range of CloudStack related
>> services

 IaaS Cloud Design & Build<
 http://shapeblue.com/iaas-cloud-design-and-build//>
 CSForge – rapid IaaS deployment framework<
>> http://shapeblue.com/csforge/>
 CloudStack Consulting
 CloudStack Software Engineering<
 http://shapeblue.com/cloudstack-software-engineering/>
 CloudStack Infrastructure Support<
 http://shapeblue.com/cloudstack-infrastructure-support/>
 CloudStack Bootcamp Training Courses<
 http://shapeblue.com/cloudstack-training/>

 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 a
 company incorporated in India and is operated under license from Shape
>> Blue
 Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
>> Brasil
 and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty
>> Ltd is
 a company registered by The Republic of South Africa and is traded
>> under
 license from Shape Blue Ltd. ShapeBlue is a registered trademark.

>>
>> Find out more about ShapeBlue and our range of CloudStack related 
>> services
>>
>> IaaS Cloud Design & Build<
>> http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting

Jenkins build is still unstable: simulator-singlerun #1176

[jenkins]

See 

RFC: Removing 1M lines of junk

[Rohit Yadav]

Hi all,

I was testing awsapi with 4.5 today and it just did not work for me, after few 
hours I gave up and used ec2stack which worked out of the box and certainly 
felt more friendly to work with. I remembered we discussed removing awsapi but 
then the momentum never precipitated into action, so I spent some time today to 
cleanly remove awsapi and making sure it has a cleanup upgrade path and does 
not break the builds or the packaging. (Also found and fixed a debian build 
issue that someone recently reported, noredist builds being broken)

Here is the PR: https://github.com/apache/cloudstack/pull/216
Here is a repo from the branch to prove that package works too: 
http://packages.bhaisaab.org/cloudstack/nukeawsapi

As Sebastien has asked me to hold on this for few days, I hope to merge this 
next week or later; but before that happends please feel free to share any 
comments, questions. Thanks.

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

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 a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

[GitHub] cloudstack pull request: CLOUDSTACK-8433: Remove awsapi

[runseb]

Github user runseb commented on the pull request:

https://github.com/apache/cloudstack/pull/216#issuecomment-97891196
  


-Sebastien

> On 30 Apr 2015, at 18:12, Rohit Yadav  wrote:
> 
> @runseb - Sure. I was testing 4.5 today and the awsapi service did not 
work for me, after wasting almost 2 hours to make it work, I tried ec2stack 
which worked out of the box. I thought it would be a good idea to get rid of it 
and promote ec2stack :)
> 
> I’ve split the changes in 3 commits to make it easier to rebase/merge. 
I’ll keep this open and hope to merge it next week but am interested in merge 
it now to avoid rebasing efforts again. If ec2stack will get its own git repo 
like docs repos or cloudmonkey - does it matter if we merge this now or next 
week and will this block 4.6 release management?
> 
Nothing technical, just a better process in my view. To be sure we dont 
have a period with no official ec2 interface.

Lets talk it over a bit and decide mud next week . That should not causr 
too much rebase headache.

Ok ?

> —
> Reply to this email directly or view it on GitHub.
> 



---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: RFC: Removing 1M lines of junk

[Sebastien Goasguen]

-Sebastien

> On 30 Apr 2015, at 19:23, Rohit Yadav  wrote:
> 
> Hi all,
> 
> I was testing awsapi with 4.5 today and it just did not work for me, after 
> few hours I gave up and used ec2stack which worked out of the box and 
> certainly felt more friendly to work with. I remembered we discussed removing 
> awsapi but then the momentum never precipitated into action, so I spent some 
> time today to cleanly remove awsapi and making sure it has a cleanup upgrade 
> path and does not break the builds or the packaging. (Also found and fixed a 
> debian build issue that someone recently reported, noredist builds being 
> broken)
> 
> Here is the PR: https://github.com/apache/cloudstack/pull/216
> Here is a repo from the branch to prove that package works too: 
> http://packages.bhaisaab.org/cloudstack/nukeawsapi
> 
> As Sebastien has asked me to hold on this for few days, I hope to merge this 
> next week or later; but before that happends please feel free to share any 
> comments, questions. Thanks.
> 

Thanks a lot for this Rohit.

+1 

And lets have a few days to allow people to chime in


> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
> 
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design & Build
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software 
> Engineering
> CloudStack Infrastructure 
> Support
> CloudStack Bootcamp Training 
> Courses
> 
> 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 a company 
> incorporated in India and is operated under license from Shape Blue Ltd. 
> Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
> operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
> registered by The Republic of South Africa and is traded under license from 
> Shape Blue Ltd. ShapeBlue is a registered trademark.

[GitHub] cloudstack pull request: CLOUDSTACK-8433: Remove awsapi

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/216#issuecomment-97891883
  
Copy that.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: RFC: Removing 1M lines of junk

[David Nalley]

On Thu, Apr 30, 2015 at 1:23 PM, Rohit Yadav  wrote:
> Hi all,
>
> I was testing awsapi with 4.5 today and it just did not work for me, after 
> few hours I gave up and used ec2stack which worked out of the box and 
> certainly felt more friendly to work with. I remembered we discussed removing 
> awsapi but then the momentum never precipitated into action, so I spent some 
> time today to cleanly remove awsapi and making sure it has a cleanup upgrade 
> path and does not break the builds or the packaging. (Also found and fixed a 
> debian build issue that someone recently reported, noredist builds being 
> broken)
>
> Here is the PR: https://github.com/apache/cloudstack/pull/216
> Here is a repo from the branch to prove that package works too: 
> http://packages.bhaisaab.org/cloudstack/nukeawsapi
>
> As Sebastien has asked me to hold on this for few days, I hope to merge this 
> next week or later; but before that happends please feel free to share any 
> comments, questions. Thanks.
>

I haven't looked at all at the changes or the resulting builds, but in
principle, I agree.
I don't think that anyone is actively maintaining the AWSAPI code .(We
did have a bug fix 6 months ago to address a security issue, but it
looks as if it has set idle for ~2 years otherwise).

Deprecate AWSAPI - make the python based stuff optional. It will
reduce the codebase size tremendously.

--David

Re: RFC: Removing 1M lines of junk

[Daan Hoogland]

We will have to provide a migration path if anybody is actually using it.

Biligual auto correct use.  Read at your own risico
On 30 Apr 2015 19:36, "David Nalley"  wrote:

> On Thu, Apr 30, 2015 at 1:23 PM, Rohit Yadav 
> wrote:
> > Hi all,
> >
> > I was testing awsapi with 4.5 today and it just did not work for me,
> after few hours I gave up and used ec2stack which worked out of the box and
> certainly felt more friendly to work with. I remembered we discussed
> removing awsapi but then the momentum never precipitated into action, so I
> spent some time today to cleanly remove awsapi and making sure it has a
> cleanup upgrade path and does not break the builds or the packaging. (Also
> found and fixed a debian build issue that someone recently reported,
> noredist builds being broken)
> >
> > Here is the PR: https://github.com/apache/cloudstack/pull/216
> > Here is a repo from the branch to prove that package works too:
> http://packages.bhaisaab.org/cloudstack/nukeawsapi
> >
> > As Sebastien has asked me to hold on this for few days, I hope to merge
> this next week or later; but before that happends please feel free to share
> any comments, questions. Thanks.
> >
>
> I haven't looked at all at the changes or the resulting builds, but in
> principle, I agree.
> I don't think that anyone is actively maintaining the AWSAPI code .(We
> did have a bug fix 6 months ago to address a security issue, but it
> looks as if it has set idle for ~2 years otherwise).
>
> Deprecate AWSAPI - make the python based stuff optional. It will
> reduce the codebase size tremendously.
>
> --David
>

Re: marvin test cases + travis

[Daan Hoogland]

Travis is starting to indue the, 'oh,  a timeout again' - blindness in me.
Let's put a safe time on it.  A result should mean something and those time
out are like the (decreasing) abundance of Jenkins failures.

So +1 for increasing the time

On Thu, 30 Apr 2015 18:46 Ian Duffy  wrote:

> > Do we need to ask for an increase in run time?
>
> From my experience I wouldn't say its required however *it would be very
> nice*.
> At the moment what we do is create new parallel jobs and balance the
> tests across them so each job is under 50mins.
>
> Anywho, just my 2c, see what others say/think.
>
> On 30 April 2015 at 17:34, David Nalley  wrote:
> > Do we need to ask for an increase in run time?
> > 50 minutes is the OSS default, but the ASF is a paying customer and we
> > can ask for longer timeouts.
> >
> > --David
> >
> > On Thu, Apr 30, 2015 at 10:06 AM, Abhinandan Prateek
> >  wrote:
> >> One of the run did timeout. Will balance the runs.
> >>
> >>> On 30-Apr-2015, at 5:59 pm, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
> >>>
> >>> Yes, thanks for checking. I was worried that now some of them may
> start timing out.
> >>> I have another 10 suites tested, will add them once everything seems
> fine.
> >>>
> >>> -abhi
> >>>
> >>>
>  On 30-Apr-2015, at 5:32 pm, Rajani Karuturi 
> wrote:
> 
>  after correcting the test file path, its working fine
> 
>  https://travis-ci.org/karuturi/cloudstack/jobs/60681263
> 
> 
> 
>  ~Rajani
> 
>  On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi 
> wrote:
> 
> > I think its due to this commit
> >
> >
> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77
> >
> > Here, test file name is changed from testname to
> [smoke,component]/testname
> >
> > But, while running each test file in the for loop, it prepends the
> name
> > with smoke and hence, it cant find the file and none of the tests in
> the
> > file are run
> >
> >
> >
> > ~Rajani
> >
> > On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
> > abhinandan.prat...@shapeblue.com> wrote:
> >
> >> It is possible, I will check.
> >>
> >>> On 30-Apr-2015, at 3:43 pm, Rajani Karuturi 
> wrote:
> >>>
> >>> Hey Abhi,
> >>>
> >>> In the recent travis runs, its not printing the test case in
> output (
> >>> https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
> >>>
> >>> It used to print the test case name and status (
> >>> https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
> >>>
> >>> Do you think it can be due to any recent changes?
> >>>
> >>> ~Rajani
> >>>
> >>> On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> >>> abhinandan.prat...@shapeblue.com> wrote:
> >>>
> 
>   There are more than 10 additional suites that can still be
> included
> >> to
>  the travis-CI.
>  Since the current set runs comfortably I will go ahead and add
> more. If
>  the system gets overloaded, then we can balance the kind of test
> >> suites and
>  amount of test suits that run comfortably on travis.
> 
>  -abhi
> 
> 
> 
> 
>  Find out more about ShapeBlue and our range of CloudStack related
> >> services
> 
>  IaaS Cloud Design & Build<
>  http://shapeblue.com/iaas-cloud-design-and-build//>
>  CSForge – rapid IaaS deployment framework<
> >> http://shapeblue.com/csforge/>
>  CloudStack Consulting<
> http://shapeblue.com/cloudstack-consultancy/>
>  CloudStack Software Engineering<
>  http://shapeblue.com/cloudstack-software-engineering/>
>  CloudStack Infrastructure Support<
>  http://shapeblue.com/cloudstack-infrastructure-support/>
>  CloudStack Bootcamp Training Courses<
>  http://shapeblue.com/cloudstack-training/>
> 
>  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 a
>  company incorporated in India and is operated under license from
> Shape
> >> Blue
>  Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated
> in
> >> Brasil
>  an

Jenkins build is still unstable: simulator-singlerun #1177

[jenkins]

See 

Jenkins build is still unstable: simulator-singlerun #1178

[jenkins]

See 

[GitHub] cloudstack pull request: CLOUDSTACK-8335: removed ceph repository

[K0zka]

GitHub user K0zka opened a pull request:

https://github.com/apache/cloudstack/pull/217

CLOUDSTACK-8335: removed ceph repository

artifact resolved from maven central
https://repo1.maven.org/maven2/com/ceph/rados/0.1.4/

Signed-off-by: Laszlo Hornyak 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/K0zka/cloudstack removecephrepo_1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/217.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #217


commit 6c5ab46a5af56995265ca653979fa6b7c9dfd39e
Author: Laszlo Hornyak 
Date:   2015-04-30T18:58:59Z

CLOUDSTACK-8335: removed ceph repository - artifact resolved from maven 
central

Signed-off-by: Laszlo Hornyak 




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS] Moving to Java 8

[Wilder Rodrigues]

Hi Marcus,

Apologies for taking so much time to reply to your email, but was, and still 
am, quite busy. :)

I would only use reflection if that was the only way to do it. The use of 
reflection usually makes the code more complex, which is not good when we have 
java developers in all different levels (from jr. do sr) working with 
cloudstack. It also makes us lose the type safety, which might also harm the 
exception handling if not done well. In addition, if we need to refactor 
something, the IDE is no longer going to do few things because the refection 
code cannot be found.

If someone will need to extend the LibvirtComputingResource that would be no 
problem with the approach I’m using. The CitrixResourceBase also has quite few 
sub-classes and it works just fine.

I will document on the wiki page how it should be done when sub-classing the 
LibvirtComputingResource class.

In a quick note/snippet, one would do:

public class EkhoComputingResource extends LibvirtComputingResource {

   @Override
public Answer executeRequest(final Command cmd) {

final LibvirtRequestWrapper wrapper = 
LibvirtRequestWrapper.getInstance();
try {
return wrapper.execute(cmd, this);
} catch (final Exception e) {
return Answer.createUnsupportedCommandAnswer(cmd);
}
}
}


In the flyweight where I keep the wrapper we could have ():

final Hashtable, CommandWrapper> 
linbvirtCommands = new Hashtable, CommandWrapper>();
linbvirtCommands.put(StopCommand.class, new 
LibvirtStopCommandWrapper());

final Hashtable, CommandWrapper> ekhoCommands 
= new Hashtable, CommandWrapper>();
linbvirtCommands.put(StopCommand.class, new EkhoStopCommandWrapper());

resources.put(LibvirtComputingResource.class, linbvirtCommands);
resources.put(EkhoComputingResource.class, ekhoCommands);

But that is needed only if the StopCommand has a different behaviour for the 
EkhoComputingResource.

Once a better version of the documentation is on the wiki, I will let you know.

On other matters, I’m also adding unit tests for all the changes. We already 
went from 4% to 13.6% coverage in the KVM hypervisor plugin. The code I already 
refactored has 56% of coverage.

You can see all the commits here: 
https://github.com/schubergphilis/cloudstack/tree/refactor/libvirt_resource

Cheers,
Wilder

On 23 Apr 2015, at 17:26, Marcus 
mailto:shadow...@gmail.com>> wrote:

Great to see someone working on it. What sorts of roadblocks came out
of reflection? How does the wrapper design solve the pluggability
issue? This is pretty important to me, since I've worked with several
companies now that end up subclassing LibvirtComputingResource in
order to handle their own Commands on the hypervisor from their
server-side plugins, and changing their 'resource' to that in
agent.properties. Since the main agent class needs to be set at agent
join, this is harder to manage than it should be.

I mentioned the reflection model because that's how I tend to handle
the commands when subclassing LibvirtComputingResource. I haven't had
any problems with it, but then again I haven't tried to refactor 5500
lines into that model, either.

On Thu, Apr 23, 2015 at 1:17 AM, Wilder Rodrigues
mailto:wrodrig...@schubergphilis.com>> wrote:
Hi Marcus,

I like the annotation idea, but reflection is trick because it hides some
information about the code.

Please, have a look at the CitrixResourceBase after the refactor I did. It
became quite smaller and test coverage was improved.

URL:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Refactoring+XenServer+Hypervisor+Plugin

The same patter is being about to Libvirt stuff. The coverage on the KVM
hypervisor plugin already went from 4 to 10.5% after refactoring 6 commands

Cheers,
Wilder

On 22 Apr 2015, at 23:06, Marcus  wrote:

Kind of a tangent, but I'd actually like to see some work done to
clean up LibvirtComputing resource. One model I've prototyped that
seems to work is to create an annotation, such as
'KVMCommandExecutor', with a 'handles' property. With this annotation,
you implement a class that handles, e.g. StartCommand, etc. Then in
LibvirtComputingResource, the 'configure' method fetches all of these
executors via reflection and stores them in an object. Then, instead
of having all of the 'instanceof' lines in LibvirtComputingResource,
the executeRequest method fetches the executor that handles the
incoming command and runs it.

I think this would break up LibvirtComputingResource into smaller,
more testable and manageable chunks, and force things like config and
utility methods to move to a more sane location, as well. As a bonus,
this model makes things pluggable. Someone could ship KVM plugin code
containing standalone command executors that are discovered at runtime
for things they need to run at the hypervisor level.

On Tue, Apr 21, 2015 at 6:27 AM, Wilder Rodrigues
 wrote:

Hi all,

Yesterday I started workin

Re: [DISCUSS] Moving to Java 8

[Marcus]

Ok. I wish I could share some code, because it isn't really as big of
a deal as it sounds from your reasoning. It is literally just 3 lines
on startup that fetch anything with the '@AgentExecutor' annotation
and stores it in a hash whose key is the value from @AgentExecutor's
'handles' property. Then when a *Command comes it it is passed to the
appropriate Executor class.

Looking at CitrixRequestWrapper, the 3 lines I mention are almost
identical in function to your init method, just that it uses the
annotation to find all of the commands, rather than hardcoding them.
We use the same annotation design for the api side of the code on the
management server, which allows the api commands to be easier to write
and self-contained (you don't have to update other code to add a new
api call). It makes things easier for novice developers.

This implementation is no less typesafe than the previous design (the
one with all of the instanceof). It didn't require any casting or
warning suppression, either, as the wrapper does.

Extending LibvirtComputingResource is not ideal, and doesn't work if
multiple third parties are involved. Granted, there hasn't been a lot
of demand for this, nevertheless it's particularly important for KVM,
where the Command classes are executed on the hypervisor it's not
really feasible to just dump the code in your management server-side
plugin like some plugins do.

In reviewing the code, the two implementations are really very close.
If you just updated init to fetch the wrappers based on either an
annotation or the class they extend, or something along those lines so
this method doesn't have to be edited every time a command is added,
that would be more or less the same thing. The the KVM agent would be
pluggable like the management server side is.

On Thu, Apr 30, 2015 at 12:55 PM, Wilder Rodrigues
 wrote:
> Hi Marcus,
>
> Apologies for taking so much time to reply to your email, but was, and still
> am, quite busy. :)
>
> I would only use reflection if that was the only way to do it. The use of
> reflection usually makes the code more complex, which is not good when we
> have java developers in all different levels (from jr. do sr) working with
> cloudstack. It also makes us lose the type safety, which might also harm the
> exception handling if not done well. In addition, if we need to refactor
> something, the IDE is no longer going to do few things because the refection
> code cannot be found.
>
> If someone will need to extend the LibvirtComputingResource that would be no
> problem with the approach I’m using. The CitrixResourceBase also has quite
> few sub-classes and it works just fine.
>
> I will document on the wiki page how it should be done when sub-classing the
> LibvirtComputingResource class.
>
> In a quick note/snippet, one would do:
>
> public class EkhoComputingResource extends LibvirtComputingResource {
>
>@Override
> public Answer executeRequest(final Command cmd) {
>
> final LibvirtRequestWrapper wrapper =
> LibvirtRequestWrapper.getInstance();
> try {
> return wrapper.execute(cmd, this);
> } catch (final Exception e) {
> return Answer.createUnsupportedCommandAnswer(cmd);
> }
> }
> }
>
>
> In the flyweight where I keep the wrapper we could have ():
>
> final Hashtable, CommandWrapper>
> linbvirtCommands = new Hashtable,
> CommandWrapper>();
> linbvirtCommands.put(StopCommand.class, new
> LibvirtStopCommandWrapper());
>
> final Hashtable, CommandWrapper>
> ekhoCommands = new Hashtable, CommandWrapper>();
> linbvirtCommands.put(StopCommand.class, new
> EkhoStopCommandWrapper());
>
> resources.put(LibvirtComputingResource.class, linbvirtCommands);
> resources.put(EkhoComputingResource.class, ekhoCommands);
>
> But that is needed only if the StopCommand has a different behaviour for the
> EkhoComputingResource.
>
> Once a better version of the documentation is on the wiki, I will let you
> know.
>
> On other matters, I’m also adding unit tests for all the changes. We already
> went from 4% to 13.6% coverage in the KVM hypervisor plugin. The code I
> already refactored has 56% of coverage.
>
> You can see all the commits here:
> https://github.com/schubergphilis/cloudstack/tree/refactor/libvirt_resource
>
> Cheers,
> Wilder
>
> On 23 Apr 2015, at 17:26, Marcus  wrote:
>
> Great to see someone working on it. What sorts of roadblocks came out
> of reflection? How does the wrapper design solve the pluggability
> issue? This is pretty important to me, since I've worked with several
> companies now that end up subclassing LibvirtComputingResource in
> order to handle their own Commands on the hypervisor from their
> server-side plugins, and changing their 'resource' to that in
> agent.properties. Since the main agent class needs to be set at agent
> join, this is harder to manage than it should be.
>
> I mentioned the reflection model because that's how I tend

Re: RFC: Removing 1M lines of junk

[Rohit Yadav]

Hi,

> On 30-Apr-2015, at 7:43 pm, Daan Hoogland  wrote:
>
> We will have to provide a migration path if anybody is actually using it.

The migration path would be documenting the change as part of the release notes 
to simply switch from using the consumer URL server_ip:7080/awsapi to setting 
up ec2stack and consuming from URL server_ip:5000 (or any other configured 
port). Normally service offerings are rather limited compared to other 
resources, when setting up ec2stack users can provide the mapping to it or 
migrate it to ec2stack using something custom like cloudmonkey+bash.

The important issue to note here is that a lot of real-world awsapi integration 
with a user's own subsystems may not follow any convention or be rather 
customised other than consumption of service URL and associated 
apikey/secretkey, so migration path from our end would mostly consist of 
documenting the changes. This upgrade path may also be implemented as a script 
or a ec2stack tool that can read cloudbridge database to get useful configs and 
service offering mappings. And, there may be some changes that may not be 
migrated or supported due to the different AWS API versions both the services 
support and one’s own custom usage/implementation.

Regards.

> Biligual auto correct use.  Read at your own risico
> On 30 Apr 2015 19:36, "David Nalley"  wrote:
>
>> On Thu, Apr 30, 2015 at 1:23 PM, Rohit Yadav 
>> wrote:
>>> Hi all,
>>>
>>> I was testing awsapi with 4.5 today and it just did not work for me,
>> after few hours I gave up and used ec2stack which worked out of the box and
>> certainly felt more friendly to work with. I remembered we discussed
>> removing awsapi but then the momentum never precipitated into action, so I
>> spent some time today to cleanly remove awsapi and making sure it has a
>> cleanup upgrade path and does not break the builds or the packaging. (Also
>> found and fixed a debian build issue that someone recently reported,
>> noredist builds being broken)
>>>
>>> Here is the PR: https://github.com/apache/cloudstack/pull/216
>>> Here is a repo from the branch to prove that package works too:
>> http://packages.bhaisaab.org/cloudstack/nukeawsapi
>>>
>>> As Sebastien has asked me to hold on this for few days, I hope to merge
>> this next week or later; but before that happends please feel free to share
>> any comments, questions. Thanks.
>>>
>>
>> I haven't looked at all at the changes or the resulting builds, but in
>> principle, I agree.
>> I don't think that anyone is actively maintaining the AWSAPI code .(We
>> did have a bug fix 6 months ago to address a security issue, but it
>> looks as if it has set idle for ~2 years otherwise).
>>
>> Deprecate AWSAPI - make the python based stuff optional. It will
>> reduce the codebase size tremendously.
>>
>> --David
>>

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab



Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

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 a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: ACS 4.5.1 fails

[Rafael Fonseca]

That won't fix it.. if the java-1.8.0-openjdk that will just install
java-1.7.0-openjdk next to it.. alternatives will probably still be
configured to run with 1.8.0.
If you actually want to be sure that it will run on java 7 you also need to
add a Conflicts: java-1.8.0-openjdk to the spec file so that the packet
manager will also uninstall that version ;)


On Wed, Apr 29, 2015 at 11:27 PM, Rohit Yadav 
wrote:

> Hi,
>
> Fixed on 4.5 now:
> https://github.com/apache/cloudstack/commit/031d7a9c43c5082913064a39829ecefb2239c5ab
>
> Latest 4.5 testing repo: http://packages.bhaisaab.org/cloudstack/testing
>
> > On 27-Apr-2015, at 6:09 pm, ilya  wrote:
> >
> > perhaps we need to patch and hard set java to = 1.7 (vs =>1.7) with arch
> type of x86_64  - until we are ready with 1.8..
> >
> > On 4/27/15 7:01 AM, Rafael Fonseca wrote:
> >> Hi there :)
> >>
> >> You didn't mention if you were running 32 or 64 bit OS... 32 bit JVM
> can't
> >> scale over 1.4/1.6Gb Heap size, no matter what you put in the -Xmx
> option ;)
> >>
> >> RF
> >>
> >> On Mon, Apr 27, 2015 at 3:44 PM, Timothy Lothering <
> >> tlother...@datacentrix.co.za> wrote:
> >>
> >>> Hi Keerthiraja,
> >>>
> >>> We are on 4.3.0.2 - So I am not sure it the tomcat6-nonssl.conf
> differs. I
> >>> looked at your JAVA_OPTS line and mine,
> >>>
> >>> Your Line:
> >>>
> >>> JAVA_OPTS="-Djava.awt.headless=true
> -Dcom.sun.management.jmxremote=false
> >>> -Xmx2g -XX:+HeapDumpOnOutOfMemoryError
> >>> -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M
> >>> -XX:MaxPermSize=800m
> >>>
> -Djava.security.properties=/etc/cloudstack/management/java.security.ciphers"
> >>>
> >>> Mine:
> >>>
> >>> JAVA_OPTS="-Djava.awt.headless=true
> >>> -Dcom.sun.management.jmxremote.port=45219
> >>> -Dcom.sun.management.jmxremote.authenticate=false
> >>> -Dcom.sun.management.jmxremote.ssl=false -Xmx4g -Xms2g
> >>> -XX:+HeapDumpOnOutOfMemoryError
> >>> -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M
> >>> -XX:MaxPermSize=800m"
> >>>
> >>> There are some options missing, but I also do not see a "-Xms" line in
> >>> yours. I will put 4.5.1 in Lab and see what happens.
> >>>
> >>> My ACS MS has 8GB RAM, that is why I have -Xmx4g
> >>>
> >>> Regards,
> >>> Timothy Lothering
> >>> Solutions Architect
> >>> Managed Services
> >>>
> >>> T: +27877415535
> >>> F: +27877415100
> >>> C: +27824904099
> >>> E: tlother...@datacentrix.co.za
> >>>
> >>>
> >>> DISCLAIMER NOTICE:
> >>>
> >>> Everything in this e-mail and any attachments relating to the official
> >>> business of Datacentrix Holdings Ltd. and its subsidiaries
> >>> ('Datacentrix') is proprietary to Datacentrix. It is confidential,
> legally
> >>> privileged and protected by law. Datacentrix does not
> >>> own and endorse any other content. Views and opinions are those of the
> >>> sender unless clearly stated as being that of Datacentrix.
> >>> The person addressed in the e-mail is the sole authorised recipient.
> >>> Please notify the sender immediately if it has unintentionally
> >>> reached you and do not read, disclose or use the content in any way.
> >>> Datacentrix cannot assure that the integrity of this communication
> >>> has been maintained nor that it is free of errors, virus, interception
> or
> >>> interference.
> >>> -Original Message-
> >>> From: Keerthiraja SJ [mailto:sjkeer...@gmail.com]
> >>> Sent: 27 April 2015 08:28 AM
> >>> To: dev@cloudstack.apache.org
> >>> Cc: us...@cloudstack.apache.org
> >>> Subject: Fwd: ACS 4.5.1 fails
> >>>
> >>> Hi All,
> >>>
> >>> I installed the ACS in my VirtualBox. After I install the CS with 4GB
> base
> >>> memory I could not able to start the server.
> >>>
> >>> I scale the memory upto 12GB still I could not able to start the ACS.
> >>> In /var/log/cloudstack/management/catalina.out I could see error as
> >>>
> >>> Can't start up: not enough memory
> >>> Can't start up: not enough memory
> >>> Can't start up: not enough memory
> >>> Can't start up: not enough memory
> >>> Can't start up: not enough memory
> >>> Can't start up: not enough memory
> >>> Can't start up: not enough memory
> >>> Can't start up: not enough memory
> >>> Can't start up: not enough memory
> >>> Can't start up: not enough memory
> >>>
> >>> Is I missing anything.
> >>>
> >>> In the default file of below I could see the java value as default.
> >>>
> >>> tomcat6.conf -> /etc/cloudstack/management/tomcat6-nonssl.conf
> >>>
> >>> JAVA_OPTS="-Djava.awt.headless=true
> -Dcom.sun.management.jmxremote=false
> >>> -Xmx2g -XX:+HeapDumpOnOutOfMemoryError
> >>> -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M
> >>> -XX:MaxPermSize=800m
> >>>
> -Djava.security.properties=/etc/cloudstack/management/java.security.ciphers"
> >>>
> >>>
> >>> Kindly let me know if any one found this issue. I even tried by
> increasing
> >>> the -Xmx2g into 4g still I don't see any improvement.
> >>>
> >>>
> >>>
> >>>
> >>> Thanks,
> >>> Keerthi
> >>>
> >
>
> Regards,
> Rohit Yadav
> Softw

Re: [DISCUSS] 4.6 release management

[Pierre-Luc Dion]

Hi,

In my mind it was kind of making more sense to start by keeping 4.6 into a
separate branch, enforce pull-requests and deploy the CI. smaller step but
faster result, and from there, once we get stable with the CI and git flow;
move into master, do fastest releases cycle. If we consider we can do all
that starting in 4.6, I'm all for it!

Marcus: are you preparing a proposal on this? wiki page? I can help

Seb: doesn't the vote would confirm the consensus?

Raja:  do we have any documentation somewhere on how to use, contribute to
the smoke test? that could be our start for the CI tests?


Cheers


On Thu, Apr 30, 2015 at 3:58 AM, Sebastien Goasguen 
wrote:

>
> > On Apr 29, 2015, at 9:49 PM, Marcus  wrote:
> >
> > After reviewing the history as mentioned by Daan, unless we propose
> > and vote on a newer workflow model I think the best we can do is to
> > simply be more strict about commits to master. They all need to be
> > merges that have been tested against master before merge. This will in
> > theory make master more stable, but doesn't really change the workflow
> > we've already agreed upon and have been working under (although
> > bugfixes sometimes were not coming in from branches, and cherry-picked
> > bugfixes from branches will need to go into a branch first, tested
> > against master, and merged to master). We can essentially set a date
> > and do that any time, with some advance notice that direct commits
> > will be reverted.
>
> Yes +1.
>
> -Set a date
> -Tag master for reference
> -Find a volunteer or two to RM master
> -automatic revert on master if not from RM
> -all commits to master come from PR, need clear review and green tests
> -harden master (basic QA process), release 4.6 as a tag on master
> -all features and fixes need to be made on branches or forks and onus is
> on devs to rebase to master
> -brings everyone onto 4.6 (make sure we have upgrade paths from 4.3, 4.4,
> etc)
> -from there forward only maintain a linear release through master
>
> Feel free to add, tweak
>
> PS: No need to vote if we have consensus. Taking a clue from ASF members,
> votes should be avoided at all cost, they mean that we do not have clear
> consensus.
>
>
> >
> > On Sat, Apr 18, 2015 at 12:50 AM, Sebastien Goasguen 
> wrote:
> >>
> >>> On Apr 18, 2015, at 8:36 AM, Marcus  wrote:
> >>>
> >>> Have they diverged that much? Due to cherry-picking, I guess.
> >>> Otherwise you should be able to do it cleanly.
> >>>
> >>> There's a good opportunity to do this next release. Instead of
> >>> creating a release branch, we freeze master and start creating dev
> >>> branches.
> >>
> >> +1
> >>
> >> This just amounts to treating master now like a release branch. Getting
> back to PL suggestion, that means
> >> that any commit to master would be through a PR or MERGE request on the
> ML. Anything else will be reverted by the RM.
> >>
> >> Marcus, do you feel like writing down a little process for this and
> some dates that we can target.
> >> It would be nice to do this for 4.6.
> >>
> >>>
> >>> On Fri, Apr 17, 2015 at 10:46 PM, Daan Hoogland <
> daan.hoogl...@gmail.com> wrote:
>  We heavily invested in code now on master. Not looking forward to
>  backporting that.
> 
>  mobile dev with bilingual spelling checker used (read at your own
> risk)
>  Op 17 apr. 2015 21:02 schreef "Marcus" :
> 
> > Well, would we just swap the last release branch with master? Master
> > is the dev branch, and the last release is really what we have as a
> > stable branch.
> >
> > On Fri, Apr 17, 2015 at 8:44 AM, Daan Hoogland <
> daan.hoogl...@gmail.com>
> > wrote:
> >> On Fri, Apr 17, 2015 at 2:43 AM, Sebastien Goasguen <
> run...@gmail.com>
> > wrote:
> >>>
>  On Apr 17, 2015, at 12:49 AM, Pierre-Luc Dion  >
> > wrote:
> 
>  Today during the CloudStackdays  we did a round table about
> Release
>  management targeting the next 4.6 releases.
> 
> 
>  Quick bullet point discussions:
> 
>  ideas to change release planning
> 
>  - Plugin contribution is complicated because often  a new plugin
> > involve
>  change on the core:
> - ex: storage plugin involve changes on Hypervisor code
>  - There is an idea of going on a 2 weeks release model which could
>  introduce issue the database schema.
>  - Database schema version should be different then the application
>  version.
>  - There is a will to enforce git workflow in 4.6  and trigger
> > simulator
>  job on  PullRequest.
>  - Some people (I'm part of them) are concerned on our current way
> of
>  supporting and back porting fixes to multiple release (4.3.x,
> 4.4.x,
>  4.5.x). But the current level of confidence against latest release
> > is low,
>  so that need to be improved.
> 
> 
>  So, the mai

Re: [DISCUSS] 4.6 release management

[David Nalley]

On Thu, Apr 30, 2015 at 3:58 AM, Sebastien Goasguen  wrote:
>
>> On Apr 29, 2015, at 9:49 PM, Marcus  wrote:
>>
>> After reviewing the history as mentioned by Daan, unless we propose
>> and vote on a newer workflow model I think the best we can do is to
>> simply be more strict about commits to master. They all need to be
>> merges that have been tested against master before merge. This will in
>> theory make master more stable, but doesn't really change the workflow
>> we've already agreed upon and have been working under (although
>> bugfixes sometimes were not coming in from branches, and cherry-picked
>> bugfixes from branches will need to go into a branch first, tested
>> against master, and merged to master). We can essentially set a date
>> and do that any time, with some advance notice that direct commits
>> will be reverted.
>
> Yes +1.
>
> -Set a date
> -Tag master for reference
> -Find a volunteer or two to RM master
> -automatic revert on master if not from RM
> -all commits to master come from PR, need clear review and green tests
> -harden master (basic QA process), release 4.6 as a tag on master
> -all features and fixes need to be made on branches or forks and onus is on 
> devs to rebase to master
> -brings everyone onto 4.6 (make sure we have upgrade paths from 4.3, 4.4, etc)
> -from there forward only maintain a linear release through master
>
> Feel free to add, tweak


I'm +0 on the above - what would push me to +1 would be stripping the
RM as gatekeeper and letting CI be the gatekeeper (e.g. - all commits
go in via PR that tests successfully.) I don't think that an RM is
capable of understanding all of the pieces enough to judge any given
patch, especially a more complicated patch, and its a SPOF - it's also
incredibly difficult for a single person to keep up with all of the
pending patches.
I'd also be okay with must be reviewed by another committer so that
two committers have to agree.
Now, that said, if velocity is high, it will make kicking a release
out somewhat difficult as the amount of churn is going to be high.

>
> PS: No need to vote if we have consensus. Taking a clue from ASF members, 
> votes should be avoided at all cost, they mean that we do not have clear 
> consensus.
>
>

YES - this!!

Re: [DISCUSS] 4.6 release management

[Abhinandan Prateek]

Guys,

  Do I see a QACloud in works, something in line with devcloud but with a 
bigger collection of Hypervisors + marvin ?
If we can bundle these Hypervisors and QA automation then effectively we can 
have many more people join our QA effort.

> On 29-Apr-2015, at 9:24 pm, Rohit Yadav  wrote:
>
> Hi Remi,
>
> Thanks. Sure we can work together on this, I guess you would be running 
> KVM/XenServer on KVM. Ping me if you need help on running ESX 5.x on KVM as 
> it requires a patched qemu system binary (prebuilt debs here 
> http://people.apache.org/~bhaisaab/qemu). If these nested hosts are managed 
> by CloudStack itself instead of virsh or virt-viewer, then use ACS 4.5 or 
> master.
>
>> On 29-Apr-2015, at 5:21 pm, Remi Bergsma  wrote:
>>
>> Hi Rohit,
>>
>> Nice work!
>>
>> I agree we need an environment that does run on something else than the 
>> local machine, as we need more horse power. We worked on something similar, 
>> where we have a cluster of KVM controlled by CloudStack in our Employee 
>> Cloud and spin large VMs running CentOS 7.1 (we use 32 or 64GB ram). In this 
>> big VM we run KVM again and spin up all infrastructure, ranging from 
>> hypervisors, SDN controllers, database hosts, storage appliances, etc. The 
>> big benefit is that networking is easy, as it is all in one box. Also, 
>> everybody uses the same prefixes. Using a L2 VPN we connect the workstations 
>> to the dev/test environment. All VMs can be controlled using virt-manager 
>> (like you also showed) and it is actually CloudStack running inside 
>> CloudStack. Deploying this VM has been automated and we’re now working on 
>> automating different scenario’s. They can also be used as Jenkins build 
>> slaves, for example. It is work in progress.
>>
>> Long story short: Let's work together on this :-)
>>
>> Regards,
>> Remi
>>
>>
>>> On 28 Apr 2015, at 21:07, Rohit Yadav  wrote:
>>>
>>> Hi Ilya,
>>>
>>> In short - to run ESX and other hypervisors (Xen, KVM, OVM3, HyperV etc) on 
>>> KVM you need to;
>>>
>>> - use patched qemu (tested to work on both Ubuntu 14.04 and 15.04 x64, I’m 
>>> waiting for Fedora 22 to test it on F22 as well), you may install the 
>>> pre-built debs or build/install qemu from source using the patch from here: 
>>> people.apache.org/~bhaisaab/qemu
>>> - use ACS using latest 4.5 branch and deploy a basic zone (without SG) to 
>>> provision hypervisor hosts as user vms
>>> - in agent.properties (on your kvm host), enable guest.cpu.features=vmx and 
>>> guest.cpu.mode=host-passthrough
>>> - when deploying ESX 5.x on vm (or installing using an ISO) deploy 
>>> virtualmachine with details nicAdapter=vmxnet3, for other hypervisors 
>>> (including ESX 6.0) E1000, the default nic adapter, works
>>>
>>> IMO this is a better approach as it does not depend on ESX or VMWare fusion 
>>> that requires special hardware (vCenter/Windows etc or OSX/Apple machine) 
>>> and are difficult to automate. Working with KVM host, since is a Linux 
>>> machine, would be more familiar to sysadmins and certainly a pleasure to 
>>> scale and work with because one can avoid management tools (such as 
>>> XenCenter or vCenter).
>>>
>>> (I’m still working on the "CloudStack Developer Kit” {CDK} so it’s not in a 
>>> state to be released yet, will avoid publishing a faulty tool now. Instead 
>>> of the DevCloud approach which promotes everything on one machine, the CDK 
>>> I’m trying to build focuses on developer productivity, reproducibility and 
>>> scalability of a QA lab, it recommends at least one companion hardware with 
>>> a developer’s workstation/laptop which can be a small-form-factor server 
>>> like a mini PC or NUC with at least 16GB RAM and 4 cores i7 with Intel VT. 
>>> Hope to share it soon.)
>>>
 On 28-Apr-2015, at 7:17 pm, ilya  wrote:

 Rohit

 Any headway on ESX 5.5? I've done this many times before using cloudstack 
 and esx, but i was using esx as parent hypervisor.

 The challenge for me was being able to automatically deploy and configure 
 the vSphere + ESXi env. I managed to get the whole flow working with bash 
 script, puppet, VMA and while it works its not pretty. The challenge was 
 the networking bit.

 Last but not least, consider using cloudstack to test cloudstack. i.e. 
 master env, would use cloudstack projects and spinup smaller envs with 
 KVM, Xen and VmWare bound to each project.

 Regards
 ilya

 On 4/24/15 7:53 AM, Rohit Yadav wrote:
> Daan,
>
>> On 24-Apr-2015, at 3:53 pm, Daan Hoogland  
>> wrote:
>>
>> Rohit, the issues you mention are not as painful if we release in a
>> two week schedule as the period of creating a fix to seeing it in a
>> release will be shorter. Some releases will be broken for some people,
>> I don't think we can prevent this. The target we are aiming for is to
>> big to cover it completely.
> I agree with you, but I think there are pros and co

Re: marvin test cases + travis

[Abhinandan Prateek]

+1 for increased timeouts.

At the moment we get less than 24 commits per day on master. Only a couple on 
other branches per day.
We can increase the timeout to upto 70 minutes or more. Will try to ensure that 
in general a single run does not take more than an hour.

A timeout window slightly higher will ensure that we do not see timeout 
failures.

> On 30-Apr-2015, at 11:25 pm, Daan Hoogland  wrote:
>
> Travis is starting to indue the, 'oh,  a timeout again' - blindness in me.
> Let's put a safe time on it.  A result should mean something and those time
> out are like the (decreasing) abundance of Jenkins failures.
>
> So +1 for increasing the time
>
> On Thu, 30 Apr 2015 18:46 Ian Duffy  wrote:
>
>>> Do we need to ask for an increase in run time?
>>
>> From my experience I wouldn't say its required however *it would be very
>> nice*.
>> At the moment what we do is create new parallel jobs and balance the
>> tests across them so each job is under 50mins.
>>
>> Anywho, just my 2c, see what others say/think.
>>
>> On 30 April 2015 at 17:34, David Nalley  wrote:
>>> Do we need to ask for an increase in run time?
>>> 50 minutes is the OSS default, but the ASF is a paying customer and we
>>> can ask for longer timeouts.
>>>
>>> --David
>>>
>>> On Thu, Apr 30, 2015 at 10:06 AM, Abhinandan Prateek
>>>  wrote:
 One of the run did timeout. Will balance the runs.

> On 30-Apr-2015, at 5:59 pm, Abhinandan Prateek <
>> abhinandan.prat...@shapeblue.com> wrote:
>
> Yes, thanks for checking. I was worried that now some of them may
>> start timing out.
> I have another 10 suites tested, will add them once everything seems
>> fine.
>
> -abhi
>
>
>> On 30-Apr-2015, at 5:32 pm, Rajani Karuturi 
>> wrote:
>>
>> after correcting the test file path, its working fine
>>
>> https://travis-ci.org/karuturi/cloudstack/jobs/60681263
>>
>>
>>
>> ~Rajani
>>
>> On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi 
>> wrote:
>>
>>> I think its due to this commit
>>>
>>>
>> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77
>>>
>>> Here, test file name is changed from testname to
>> [smoke,component]/testname
>>>
>>> But, while running each test file in the for loop, it prepends the
>> name
>>> with smoke and hence, it cant find the file and none of the tests in
>> the
>>> file are run
>>>
>>>
>>>
>>> ~Rajani
>>>
>>> On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
>>> abhinandan.prat...@shapeblue.com> wrote:
>>>
 It is possible, I will check.

> On 30-Apr-2015, at 3:43 pm, Rajani Karuturi 
>> wrote:
>
> Hey Abhi,
>
> In the recent travis runs, its not printing the test case in
>> output (
> https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
>
> It used to print the test case name and status (
> https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
>
> Do you think it can be due to any recent changes?
>
> ~Rajani
>
> On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
>>
>> There are more than 10 additional suites that can still be
>> included
 to
>> the travis-CI.
>> Since the current set runs comfortably I will go ahead and add
>> more. If
>> the system gets overloaded, then we can balance the kind of test
 suites and
>> amount of test suits that run comfortably on travis.
>>
>> -abhi
>>
>>
>>
>>
>> Find out more about ShapeBlue and our range of CloudStack related
 services
>>
>> IaaS Cloud Design & Build<
>> http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework<
 http://shapeblue.com/csforge/>
>> CloudStack Consulting<
>> http://shapeblue.com/cloudstack-consultancy/>
>> CloudStack Software Engineering<
>> http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure Support<
>> http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses<
>> http://shapeblue.com/cloudstack-training/>
>>
>> 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 an

Jenkins build is still unstable: simulator-singlerun #1179

[jenkins]

See 

Re: marvin test cases + travis

[Rajani Karuturi]

At the moment we are creating 10 parallel jobs and in each job we do
1. mvn clean install
2. deploydb, deploy datacenter
3. run tests

if we change step 1 to mvn clean install -DskipTests=true and run junit
tests only in one job, that would save time.

Also, with earlier 5 jobs setup, it used to run fine on my private fork.
Now, it takes double the time(as it runs only 5 parallel jobs) and usually
timesout




~Rajani

On Fri, May 1, 2015 at 8:25 AM, Abhinandan Prateek <
abhinandan.prat...@shapeblue.com> wrote:

> +1 for increased timeouts.
>
> At the moment we get less than 24 commits per day on master. Only a couple
> on other branches per day.
> We can increase the timeout to upto 70 minutes or more. Will try to ensure
> that in general a single run does not take more than an hour.
>
> A timeout window slightly higher will ensure that we do not see timeout
> failures.
>
> > On 30-Apr-2015, at 11:25 pm, Daan Hoogland 
> wrote:
> >
> > Travis is starting to indue the, 'oh,  a timeout again' - blindness in
> me.
> > Let's put a safe time on it.  A result should mean something and those
> time
> > out are like the (decreasing) abundance of Jenkins failures.
> >
> > So +1 for increasing the time
> >
> > On Thu, 30 Apr 2015 18:46 Ian Duffy  wrote:
> >
> >>> Do we need to ask for an increase in run time?
> >>
> >> From my experience I wouldn't say its required however *it would be very
> >> nice*.
> >> At the moment what we do is create new parallel jobs and balance the
> >> tests across them so each job is under 50mins.
> >>
> >> Anywho, just my 2c, see what others say/think.
> >>
> >> On 30 April 2015 at 17:34, David Nalley  wrote:
> >>> Do we need to ask for an increase in run time?
> >>> 50 minutes is the OSS default, but the ASF is a paying customer and we
> >>> can ask for longer timeouts.
> >>>
> >>> --David
> >>>
> >>> On Thu, Apr 30, 2015 at 10:06 AM, Abhinandan Prateek
> >>>  wrote:
>  One of the run did timeout. Will balance the runs.
> 
> > On 30-Apr-2015, at 5:59 pm, Abhinandan Prateek <
> >> abhinandan.prat...@shapeblue.com> wrote:
> >
> > Yes, thanks for checking. I was worried that now some of them may
> >> start timing out.
> > I have another 10 suites tested, will add them once everything seems
> >> fine.
> >
> > -abhi
> >
> >
> >> On 30-Apr-2015, at 5:32 pm, Rajani Karuturi 
> >> wrote:
> >>
> >> after correcting the test file path, its working fine
> >>
> >> https://travis-ci.org/karuturi/cloudstack/jobs/60681263
> >>
> >>
> >>
> >> ~Rajani
> >>
> >> On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi  >
> >> wrote:
> >>
> >>> I think its due to this commit
> >>>
> >>>
> >>
> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77
> >>>
> >>> Here, test file name is changed from testname to
> >> [smoke,component]/testname
> >>>
> >>> But, while running each test file in the for loop, it prepends the
> >> name
> >>> with smoke and hence, it cant find the file and none of the tests
> in
> >> the
> >>> file are run
> >>>
> >>>
> >>>
> >>> ~Rajani
> >>>
> >>> On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
> >>> abhinandan.prat...@shapeblue.com> wrote:
> >>>
>  It is possible, I will check.
> 
> > On 30-Apr-2015, at 3:43 pm, Rajani Karuturi 
> >> wrote:
> >
> > Hey Abhi,
> >
> > In the recent travis runs, its not printing the test case in
> >> output (
> > https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
> >
> > It used to print the test case name and status (
> > https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
> >
> > Do you think it can be due to any recent changes?
> >
> > ~Rajani
> >
> > On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> > abhinandan.prat...@shapeblue.com> wrote:
> >
> >>
> >> There are more than 10 additional suites that can still be
> >> included
>  to
> >> the travis-CI.
> >> Since the current set runs comfortably I will go ahead and add
> >> more. If
> >> the system gets overloaded, then we can balance the kind of test
>  suites and
> >> amount of test suits that run comfortably on travis.
> >>
> >> -abhi
> >>
> >>
> >>
> >>
> >> Find out more about ShapeBlue and our range of CloudStack
> related
>  services
> >>
> >> IaaS Cloud Design & Build<
> >> http://shapeblue.com/iaas-cloud-design-and-build//>
> >> CSForge – rapid IaaS deployment framework<
>  http://shapeblue.com/csforge/>
> >> CloudStack Consulting<
> >> http://shapeblue.com/cloudstack-consultancy/>
> >> CloudStack Software Engineering<
> >> http://shapeblue.

[GitHub] cloudstack pull request: CLOUDSTACK-8335: removed ceph repository

[karuturi]

Github user karuturi commented on the pull request:

https://github.com/apache/cloudstack/pull/217#issuecomment-98048948
  
some of the travis jobs timedout. changes look good to me. merging.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS] Moving to Java 8

[Wilder Rodrigues]

Hi Marcus,

Thanks for the email… I’m always in for improvements. But why can’t you share 
the code?

Few points below:

1. I added an subclassing example of LibvirtComputingResource because you 
mentioned it in a previous email:

On 23 Apr 2015, at 17:26, Marcus 
mailto:shadow...@gmail.com>> wrote:

I mentioned the reflection model because that's how I tend to handle
the commands when subclassing LibvirtComputingResource.

2. Current situation with LibvirtComputingResource on Master is:

a. 67 IFs
b. 67 private/protected methods that are used only there
c. If a new Command is added it means we will have a new IF and a new private 
method
e. Maintenance is hell, test is close to zero and code quality is below 
expectations

That being said, the main idea with the refactor is to change structure only, 
not behaviour. So what I’m doing is to simply move the code out the 
LibvirtCompRes and write tests for it, keeping the behaviour the same - to be 
done in a next phase.
If you look at the changes you will see that some wrappers are already 100% 
covered. However, some others have 4% or 8% (not that much though). I would 
like to refactor that as well, but that could change behaviour (mentioned 
above) which I don’t want to touch now.

3. With the new situation:

a. No IFs
b. All methods wrapped by other classes (command wrappers) - loosely coupled, 
easier to test and maintain
c. If a new Command is added we would have to add a command wrapper and 1 line 
in the request wrapper implementation ( I know, it hurts you a bit) - but 
please bear with me for the good news.

4. the warnings are due to that:
Hashtable, CommandWrapper>()

No big deal.

As I understood from  your first paragraph we would have to annotated the 
commands classes, right? I mean, all of them.

That’s something I wouldn’t do in this phase, to be honest. It might seem 
harmless to do, but I like to break things down a bit and have more isolation 
in my changes.

What’s next: I will finish the refactor with the request wrapper as it is. For 
me it is no problem do add the lines now and remove them in 1 week. Most of the 
work is concentrated in the tests, which I’m trying as hard as I can to get 
them in the best way possible. Once it’s done and pushed to master, I will 
analyse what we would need to apply the annotation.

But before I go to bring the kids to school, just one question:

a. The “handle” value, in the annotation, would have the wrapper class that 
would be used for that command, right?  Now let’s get 1 command as example: 
CheckHealthCommand. Its wrapper implementation differs per hypervisor (just 
like all the other wrapper commands do). I’m not taking the time to really 
think about it now, but how would we annotated the different wrappers per 
command?

Thanks again for your time.

Cheers,
Wilder


On 30 Apr 2015, at 22:52, Marcus 
mailto:shadow...@gmail.com>> wrote:

Ok. I wish I could share some code, because it isn't really as big of
a deal as it sounds from your reasoning. It is literally just 3 lines
on startup that fetch anything with the '@AgentExecutor' annotation
and stores it in a hash whose key is the value from @AgentExecutor's
'handles' property. Then when a *Command comes it it is passed to the
appropriate Executor class.

Looking at CitrixRequestWrapper, the 3 lines I mention are almost
identical in function to your init method, just that it uses the
annotation to find all of the commands, rather than hardcoding them.
We use the same annotation design for the api side of the code on the
management server, which allows the api commands to be easier to write
and self-contained (you don't have to update other code to add a new
api call). It makes things easier for novice developers.

This implementation is no less typesafe than the previous design (the
one with all of the instanceof). It didn't require any casting or
warning suppression, either, as the wrapper does.

Extending LibvirtComputingResource is not ideal, and doesn't work if
multiple third parties are involved. Granted, there hasn't been a lot
of demand for this, nevertheless it's particularly important for KVM,
where the Command classes are executed on the hypervisor it's not
really feasible to just dump the code in your management server-side
plugin like some plugins do.

In reviewing the code, the two implementations are really very close.
If you just updated init to fetch the wrappers based on either an
annotation or the class they extend, or something along those lines so
this method doesn't have to be edited every time a command is added,
that would be more or less the same thing. The the KVM agent would be
pluggable like the management server side is.

On Thu, Apr 30, 2015 at 12:55 PM, Wilder Rodrigues
mailto:wrodrig...@schubergphilis.com>> wrote:
Hi Marcus,

Apologies for taking so much time to reply to your email, but was, and still
am, quite busy. :)

I would only use reflection if that was the only way to do it. The use of
reflection

[GitHub] cloudstack pull request: CLOUDSTACK-8335: removed ceph repository

[karuturi]

Github user karuturi commented on the pull request:

https://github.com/apache/cloudstack/pull/217#issuecomment-98052415
  
merged. forgot to add closes tag


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---