Re: Agent dies every night/morning.... memory violation

[Andrija Panic]

Thanks guys,

I already disabled all cron jobs and everythgin (did not disable logrotate
though...) - will share my findings.

Thanks a lot for hint.

On 23 February 2015 at 17:30, Simon Weller  wrote:

> I agree with Marcus. I suggest you start monitoring everything that's
> going on around this time frame.
> Maybe dump available memory, and IO (both disk and network) to a file
> every minute or so, and see if you can correlate it to something in
> particular that might be happening on the underlying server, or the network
> connectivity to that server. Maybe slowly move  VMs one at a time to a
> different host and see if the issue follows a particular VM.
>
> In the mean time in order to reduce the affect of this problem, you could
> use a process monitoring like Monit to watch the PID and restart
> cloudstack-agent if a failure is detected.
>
> - Si
>
> 
> From: Marcus 
> Sent: Monday, February 23, 2015 10:21 AM
> To: dev@cloudstack.apache.org
> Cc: us...@cloudstack.apache.org
> Subject: Re: Agent dies every night/morning memory violation
>
> It doesn't really sound like an agent problem, but some other root
> problem that is causing issues for the agent. Perhaps it is specific
> to the host simply because there is a particular VM that always runs
> on that host and the VM itself is triggering the issue. Perhaps a
> heavy logrotate or cron job on the vm causes issues for librados. Just
> grasping at straws here. From the output provided it does seem that
> the libvirt bindings that include ceph code are terminating the agent
> execution.  My guess is that if you focus on "why this host" as
> opposed to "what's going on", you'll find the answer to both. Sorry, I
> know that's not much help.
>
> On Mon, Feb 23, 2015 at 7:29 AM, Andrija Panic 
> wrote:
> > Anybody?, before I start to cry :(
> >
> > On 21 February 2015 at 21:18, Andrija Panic 
> wrote:
> >
> >> HI Simon,
> >>
> >> selinux is disabled, I have just double checked.
> >>
> >> BTW, this is what I can see in the cloudstack-agent.err log - seems like
> >> some CEPH related issues, but not sure why would agent die...
> >> If I recall correclty, this might be happening since the CEPH update
> from
> >> 0.80.3? to 0.87 - and this seesm like some crash in librados
> >>
> >>
> >> libust[1907/2046]: Warning: HOME environment variable not set. Disabling
> >> LTTng-UST per-user tracing. (in setup_local_apps() at
> lttng-ust-comm.c:305)
> >> libvirt:  error : name in virDomainLookupByName must not be NULL
> >> libvirt:  error : name in virDomainLookupByName must not be NULL
> >> libvirt:  error : name in virDomainLookupByName must not be NULL
> >> libvirt:  error : name in virDomainLookupByName must not be NULL
> >> libvirt: Storage Driver error : failed to remove volume
> >> 'cloudstack/bd751250-de35-4d2e-a4e3-3ee4b636c2a7': Device or resource
> busy
> >> ./log/SubsystemMap.h: In function 'bool
> >> ceph::log::SubsystemMap::should_gather(unsigned int, int)' thread
> >> 7f04427fc700 time 2015-02-21 06:39:38.839210
> >> ./log/SubsystemMap.h: 62: FAILED assert(sub < m_subsys.size())
> >>  ceph version 0.87 (c51c8f9d80fa4e0168aa52685b8de40e42758578)
> >>  1: (()+0x1fe223) [0x7f060c932223]
> >>  2: (ObjectCacher::flusher_entry()+0x155) [0x7f060c9866e5]
> >>  3: (ObjectCacher::FlusherThread::entry()+0xd) [0x7f060c9976cd]
> >>  4: (()+0x79d1) [0x7f06605ee9d1]
> >>  5: (clone()+0x6d) [0x7f066033bb5d]
> >>  NOTE: a copy of the executable, or `objdump -rdS ` is
> needed
> >> to interpret this.
> >> terminate called after throwing an instance of 'ceph::FailedAssertion'
> >> 21/02/2015 06:39:38 1905 jsvc.exec error: Service did not exit cleanly
> >>
> >> On 20 February 2015 at 21:56, Simon Weller  wrote:
> >>
> >>> Andrija,
> >>>
> >>> What is SELinux set to on this host?
> >>>
> >>>
> >>> - SI
> >>>
> >>>
> >>> 
> >>> From: Andrija Panic 
> >>> Sent: Friday, February 20, 2015 6:06 AM
> >>> To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
> >>> Subject: Agent dies every night/morning memory violation
> >>>
> >>> Hi,
> >>>
> >>> I have crazy agent on one of the hosts, that is being killed each
> morning
> >>> and I found this in /var/log/audit.log:
> >>>
> >>> type=ANOM_ABEND msg=audit(1424321463.930:430678): auid=0 uid=0 gid=0
> >>> ses=68891 pid=10831 comm="jsvc" reason="memory violation" sig=6
> >>>
> >>> I dont remember changing anything on the system, but this keeps
> happening
> >>> each morning arrond same time 5.20am-5.40am.
> >>>
> >>> I'm wondering what the hack is happening, any suggestions where to
> >>> troubleshoot ?
> >>> Will check logs in details anyway...
> >>>
> >>> --
> >>>
> >>> Andrija Panić
> >>>
> >>
> >>
> >>
> >> --
> >>
> >> Andrija Panić
> >>
> >
> >
> >
> > --
> >
> > Andrija Panić
>



-- 

Andrija Panić

discuss [ release process checklist]

[Giles Sirett]

All

Cross posting to  marketing & dev

I had the displeasure of reading this article this morning
http://www.datacenterknowledge.com/archives/2015/02/23/openstack-vs-cloudstack-the-platforms-and-the-cloud-apis/

Initially I thought it was an old article that had been re-hashed, but then   I 
saw his reference to our downloads page:
http://cloudstack.apache.org/downloads.html

which clearly says “Apache CloudStack's most current release is 4.4.2”. Hence 
this article citing it as our current release (yes, theres other badly 
researched “facts” in the article also)

Obviously, this had  just an oversight during the 4.3,4.4 releases and I 
understand when everybody is trying to get a release out of the door, updating 
the website isn’t always going to be the top priotiy

This leads me to ask: have we, as a community, got some form of checklist for a 
release ? I’m thinking about all of the tasks (such as updating the website) 
“around” the code release, however I could ask the same question for the actual 
release itself



Kind Regards
Giles

Giles Sirett
CEO



D: +44 20 3603 0541 | S: +44 20 3603 0540 | M: +44 796 111 2055

giles.sir...@shapeblue.com | www.shapeblue.com | Twitter:@shapeBlue


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: discuss [ release process checklist]

[Erik Weber]

On Tue, Feb 24, 2015 at 10:07 AM, Giles Sirett 
wrote:

> All
>
> Cross posting to  marketing & dev
>
> I had the displeasure of reading this article this morning
>
> http://www.datacenterknowledge.com/archives/2015/02/23/openstack-vs-cloudstack-the-platforms-and-the-cloud-apis/
>
> Initially I thought it was an old article that had been re-hashed, but
> then   I saw his reference to our downloads page:
> http://cloudstack.apache.org/downloads.html
>
> which clearly says “Apache CloudStack's most current release is 4.4.2”.
> Hence this article citing it as our current release (yes, theres other
> badly researched “facts” in the article also)
>
>
Isn't 4.4.2 the newest release in terms of features?
Yes, 4.3.2 might have been released later, but that's a bugfix release and
for comparisons it would be better to compare the highest version number?

Or I might be misunderstanding the problem entirely

-- 
Erik

RE: Disable primary storage, not delete...

[Devdeep Singh]

If a storage pool is put in disabled state then it will not be picked up as a 
possible destination when a volume is being migrated or when a virtual machine 
is being migrated along with its volumes.

Regards,
Devdeep

> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Monday, February 23, 2015 7:44 PM
> To: dev@cloudstack.apache.org
> Cc: us...@cloudstack.apache.org
> Subject: Re: Disable primary storage, not delete...
> 
> Yeah, probably option 2 is better.
> 
> I would think you couldn't use this primary storage as the target of a
> migration or for HA.
> 
> On Monday, February 23, 2015, Harikrishna Patnala <
> harikrishna.patn...@citrix.com> wrote:
> 
> > Hi,
> >
> > I think it is better to go with option 2, as it makes sense to be part
> > of one of the states.
> >
> > I believe that VMs using that storage continue to work, but what are
> > the plans for the operations related to the storage on those VMs like
> > migration/HA/... ?
> >
> > Thanks,
> > Harikrishna
> >
> > On 23-Feb-2015, at 3:01 pm, Devdeep Singh  > > wrote:
> >
> > > Hi,
> > >
> > > I was looking into implementing the ability to disable a storage
> > > pool
> > for provisioning. I could think of two ways to do it
> > >
> > > 1. CloudStack admin could add a 'disabled' tag on the storage pool.
> > > The
> > storage pool allocators would skip the pools for allocating volumes
> > with the 'disabled' tag.
> > > 2. Other option would be to add 'Disabled' as one of the states of
> > storage pool. This could be a state in addition to "Up", "Maintenance" etc.
> > A storage pool in "Disabled" state will not be picked up for
> > provisioning volumes. This would require new apis for disabling/enabling
> storage pool.
> > >
> > > Thoughts, comments?
> > >
> > > Regards,
> > > Devdeep
> > >
> > >> -Original Message-
> > >> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com
> > ]
> > >> Sent: Monday, February 23, 2015 3:48 AM
> > >> To: dev@cloudstack.apache.org 
> > >> Cc: us...@cloudstack.apache.org 
> > >> Subject: Re: Disable primary storage, not delete...
> > >>
> > >> For my suggestion to work, though, your compute and disk offerings
> > >> have
> > to
> > >> be set up currently to make use of one or more storage tags.
> > >>
> > >> The idea is then that these offerings would require your primary
> > storage to
> > >> have a given tag or tags and it never will (effectively disabling
> > >> that
> > primary
> > >> storage from being used with your offerings).
> > >>
> > >> On Sunday, February 22, 2015, Mike Tutkowski
> > >> >
> > >> wrote:
> > >>
> > >>> What about changing the storage tags field of your primary storage
> > >>> so it doesn't serve as a match for any compute or disk offering?
> > >>>
> > >>> On Sunday, February 22, 2015, Andrija Panic
> > >>>  > 
> > >>>  > >>> ');>>
> > wrote:
> > >>>
> >  Hi folks,
> > 
> >  I was wondering is it safe to change the Cluster Wide primary
> >  storage to a Zone Wide primary storage (change the database,
> >  cloud.storage_pool). This is ACS 4.3.0
> > 
> > 
> >  Or actually better question - since I have some old NFS servers
> >  exist as Primary Storage - is there any way to exclude this NFS
> >  (Cluster
> >  Wide)  - or disable it, so the new Volume Uploads will not use
> >  that NFS storage...
> > 
> >  This is some trail from the history, that I can't really delete,
> >  but would like to completely disable further usage of this NFS 
> >  server...
> >  if possible at all...
> > 
> >  THanks,
> > 
> > 
> >  --
> > 
> >  Andrija Panić
> > 
> > >>>
> > >>>
> > >>> --
> > >>> *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
> *™*

RE: Network QoS (not bandwidth limiting)

[Paul Angus]

Hi Adrian,

Obviously I have to pick you up on not including the  tag, so I can't 
tell where it started :)
Otherwise I'm pretty much in complete agreement.

The community is probably too developer focused and for the project to stay 
relevant we probably need to redress that balance. What we really need are 
user-community driven features and far more user-input into the feature 
development process, and I agree that means making it more friendly to 
non-developers.  I'm not anti-developer, some of my best friends are developers 
:) but due to the job description, they don't tend to spend a lot of time 
consuming the product that they build especially not in the multitude of ways 
and users could be using them (SBP excepted).

I won't go into a lengthy discussion about all your individual points, I'll 
just say that I largely agree, and point people to the site to site VPN feature 
as an example. It's implemented in openswan which I have no problem with, 
except the documentation on openswan.org around how to connect it to various 
vendor's endpoints is sparse to non-existent.  Also the only place to see 
errors relating to the VPN are in a log file on the VPC virtual router which 
the user has no access to. VPNs are tricky enough to set up at the best of 
times, doing it without any feedback is a nightmare.  This would never pass any 
decent user acceptance testing.

To throw an idea in the ring, *maybe* for a feature to be accepted, its design 
document and functional specification have to have been 'signed off' by x 
independent 'users'.  Controversial I know, but I think it makes a good 
starting point for us to think about how the people on the user mailing list 
can get involved. A Section in the CloudStack wiki maintained by users showing 
the features that they may put input into might help.  Or a 'features & 
improvements ' mailing list might serve as neutral territory for users and 
developers to have conversations...

 Just some thoughts..


Regards,

Paul Angus
Cloud Architect
D: +44 20 3468 5163 |S: +44 20 3603 0540 | M: +44 7711 418 784 | T: @CloudyAngus
paul.an...@shapeblue.com

-Original Message-
From: Adrian Lewis [mailto:adr...@alsiconsulting.co.uk]
Sent: 24 February 2015 02:57
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: RE: Network QoS (not bandwidth limiting)

Hi Marcus, Somesh, Paul

Thanks for responding and yes, I think in some aspects I may be asking too much 
but this isn't just me asking for extra/additional/new features per se.
I think it's easier if I split up the issues that I perceive to be problems 
into four distinct areas. There's overlap between them but it might help me 
explain better:

1. New features
2. Features that are already there but that can’t be used 3. Features that are 
turned on that can't be turned off 4. Features that work but which could do 
with a more granular implementation

In more detail:

1. New features:
Yes this is a contentious one (QoS, Dynamic Routing, OpenVPN etc). I think that 
this is the greedy ask and it's not feasible or even fair to ask for stuff for 
free. Believe it or not, I'm not asking "for CloudStack to provide and maintain 
a fully fledged and featured router distribution in its provided virtual 
router". If customer demand pays for something new and cool to be developed and 
it's contributed back then great but this sort of thing can't be an expectation 
by default. For those that do want more, the solution here though might be, 
IMHO the ability to either:

a) Provide a relatively simple way for users (not devs) to customise the VR 
themselves, adding/swapping/deleting packages, orchestration agents (puppet 
ansible salt etc) and giving people access to the VR for configuration without 
the risk of deletion on recreation; making the VR a 'first-class citizen' vm 
instead of a disposable commodity.

b) Allow the use of third party router/firewall VMs to be used instead of the 
default VR. Obviously, this would be at the sacrifice of functions that a 3rd 
party might not provide such as userdata and most other functions would have to 
be managed manually on the VR without the orchestration functionality that ACS 
provides with the official system VMs. There appears to already be a way to do 
this but I can’t find much information on this so I might be very wrong. The 
router.template. setting lets me create my own VR template but 
things went very wrong when I tried using it so I gave up. This setting also 
applies to every single vr in the entire zone which is not going to fit for 
many, especially if the replacement is a commercially licensed product. This is 
what I gather Somesh alluded to in his reply. It would be great if we could 
offer a choice of built-in VR, a Vyatta VR or a Cisco VR depending on the 
customer requirements without having to code a separate network provider for 
each, get it committed and wait for a new release.

2. Features that are already there but that can’t be used

[GitHub] cloudstack pull request: CLOUDSTACK-8280: UI does not display sour...

[rags22489664]

GitHub user rags22489664 opened a pull request:

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

CLOUDSTACK-8280: UI does not display source CIDR in VPC ACL

Since https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6b0c34f, 
the source cidr for acl rules are not dislpayed in the UI. Since the entity was 
split into two tables network_acl_item and network_acl_item_cidrs, populating 
cidrs before returning the response, 

A view could have been created but only one column from the 
network_acl_item_cidrs table is needed.

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

$ git pull https://github.com/rags22489664/cloudstack master

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

https://github.com/apache/cloudstack/pull/87.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 #87


commit 9f07a55f391f4928a6d16f930f142ad63884074d
Author: ramamurtis 
Date:   2015-02-24T10:12:12Z

CLOUDSTACK-8280: UI does not display source CIDR in VPC ACL




---
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: Disable primary storage, not delete...

[Andrija Panic]

Deevdap, thx for info, but this is Primary Storage (ACS 4.3.0) there is
only options to put it in Maintance mode, which I can not really do because
of VMs that might be using this storage.

I did not see option to set it to Disabled state ?

thx

On 24 February 2015 at 10:26, Devdeep Singh 
wrote:

> If a storage pool is put in disabled state then it will not be picked up
> as a possible destination when a volume is being migrated or when a virtual
> machine is being migrated along with its volumes.
>
> Regards,
> Devdeep
>
> > -Original Message-
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > Sent: Monday, February 23, 2015 7:44 PM
> > To: dev@cloudstack.apache.org
> > Cc: us...@cloudstack.apache.org
> > Subject: Re: Disable primary storage, not delete...
> >
> > Yeah, probably option 2 is better.
> >
> > I would think you couldn't use this primary storage as the target of a
> > migration or for HA.
> >
> > On Monday, February 23, 2015, Harikrishna Patnala <
> > harikrishna.patn...@citrix.com> wrote:
> >
> > > Hi,
> > >
> > > I think it is better to go with option 2, as it makes sense to be part
> > > of one of the states.
> > >
> > > I believe that VMs using that storage continue to work, but what are
> > > the plans for the operations related to the storage on those VMs like
> > > migration/HA/... ?
> > >
> > > Thanks,
> > > Harikrishna
> > >
> > > On 23-Feb-2015, at 3:01 pm, Devdeep Singh  > > > wrote:
> > >
> > > > Hi,
> > > >
> > > > I was looking into implementing the ability to disable a storage
> > > > pool
> > > for provisioning. I could think of two ways to do it
> > > >
> > > > 1. CloudStack admin could add a 'disabled' tag on the storage pool.
> > > > The
> > > storage pool allocators would skip the pools for allocating volumes
> > > with the 'disabled' tag.
> > > > 2. Other option would be to add 'Disabled' as one of the states of
> > > storage pool. This could be a state in addition to "Up", "Maintenance"
> etc.
> > > A storage pool in "Disabled" state will not be picked up for
> > > provisioning volumes. This would require new apis for
> disabling/enabling
> > storage pool.
> > > >
> > > > Thoughts, comments?
> > > >
> > > > Regards,
> > > > Devdeep
> > > >
> > > >> -Original Message-
> > > >> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com
> > > ]
> > > >> Sent: Monday, February 23, 2015 3:48 AM
> > > >> To: dev@cloudstack.apache.org 
> > > >> Cc: us...@cloudstack.apache.org 
> > > >> Subject: Re: Disable primary storage, not delete...
> > > >>
> > > >> For my suggestion to work, though, your compute and disk offerings
> > > >> have
> > > to
> > > >> be set up currently to make use of one or more storage tags.
> > > >>
> > > >> The idea is then that these offerings would require your primary
> > > storage to
> > > >> have a given tag or tags and it never will (effectively disabling
> > > >> that
> > > primary
> > > >> storage from being used with your offerings).
> > > >>
> > > >> On Sunday, February 22, 2015, Mike Tutkowski
> > > >> >
> > > >> wrote:
> > > >>
> > > >>> What about changing the storage tags field of your primary storage
> > > >>> so it doesn't serve as a match for any compute or disk offering?
> > > >>>
> > > >>> On Sunday, February 22, 2015, Andrija Panic
> > > >>>  > > 
> > > >>>  > > >>> ');>>
> > > wrote:
> > > >>>
> > >  Hi folks,
> > > 
> > >  I was wondering is it safe to change the Cluster Wide primary
> > >  storage to a Zone Wide primary storage (change the database,
> > >  cloud.storage_pool). This is ACS 4.3.0
> > > 
> > > 
> > >  Or actually better question - since I have some old NFS servers
> > >  exist as Primary Storage - is there any way to exclude this NFS
> > >  (Cluster
> > >  Wide)  - or disable it, so the new Volume Uploads will not use
> > >  that NFS storage...
> > > 
> > >  This is some trail from the history, that I can't really delete,
> > >  but would like to completely disable further usage of this NFS
> server...
> > >  if possible at all...
> > > 
> > >  THanks,
> > > 
> > > 
> > >  --
> > > 
> > >  Andrija Panić
> > > 
> > > >>>
> > > >>>
> > > >>> --
> > > >>> *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 w

Build failed in Jenkins: build-master-noredist #4099

[jenkins]

See 

Changes:

[abhinandan.prateek] CLOUDSTACK-8265: added os mappings for Ubuntu 14.04

--
[...truncated 2557 lines...]
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.788 sec - in 
com.cloud.network.ExternalLoadBalancerDeviceManagerImplTest
Running com.cloud.network.element.VirtualRouterElementTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 0.006 sec - in 
com.cloud.network.element.VirtualRouterElementTest
Running com.cloud.network.UpdatePhysicalNetworkTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.276 sec - in 
com.cloud.network.UpdatePhysicalNetworkTest
Running com.cloud.network.CreatePrivateNetworkTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.051 sec - in 
com.cloud.network.CreatePrivateNetworkTest
Running com.cloud.network.NetworkModelTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec - in 
com.cloud.network.NetworkModelTest
Running com.cloud.network.router.NetworkHelperImplTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.048 sec - in 
com.cloud.network.router.NetworkHelperImplTest
Running com.cloud.network.router.RouterControlHelperTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.053 sec - in 
com.cloud.network.router.RouterControlHelperTest
Running com.cloud.network.router.VirtualNetworkApplianceManagerImplTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.228 sec - in 
com.cloud.network.router.VirtualNetworkApplianceManagerImplTest
Running com.cloud.network.security.SecurityGroupManagerImplTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.172 sec - in 
com.cloud.network.security.SecurityGroupManagerImplTest
Running com.cloud.network.security.SecurityGroupQueueTest
Total jobs dequeued = 10, num queued=1002 queue current size=992
Num Vms= 50 Queue size = 50
Num Vms= 2 Queue size = 2 time=139 ms
Num Vms= 5000 Queue size = 5000 time=2392 ms
Num Vms= 1 Queue size = 1 time=0 ms
Num Vms= 100 Queue size = 100 time=232 ms
Total jobs dequeued = 10, num queued=1010 queue current size=1000
Total jobs dequeued = 1, num queued=1001 queue current size=1000
Total jobs dequeued = 10, num queued=1000 queue current size=990
Total jobs dequeued = 10, num queued=10 queue current size=0
Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.362 sec <<< 
FAILURE! - in com.cloud.network.security.SecurityGroupQueueTest
testNumJobsEqToNumVms3(com.cloud.network.security.SecurityGroupQueueTest)  Time 
elapsed: 3.138 sec  <<< ERROR!
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:693)
at 
com.cloud.network.security.SecurityGroupQueueTest.testNumJobsEqToNumVms2(SecurityGroupQueueTest.java:124)
at 
com.cloud.network.security.SecurityGroupQueueTest.testNumJobsEqToNumVms3(SecurityGroupQueueTest.java:143)

Running com.cloud.network.vpc.VpcManagerImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec - in 
com.cloud.network.vpc.VpcManagerImplTest
Running com.cloud.network.DedicateGuestVlanRangesTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.026 sec - in 
com.cloud.network.DedicateGuestVlanRangesTest
Running com.cloud.network.lb.AssignLoadBalancerTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.07 sec - in 
com.cloud.network.lb.AssignLoadBalancerTest
Running com.cloud.network.lb.UpdateLoadBalancerTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.055 sec - in 
com.cloud.network.lb.UpdateLoadBalancerTest
Running com.cloud.network.dao.NetworkDaoTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in 
com.cloud.network.dao.NetworkDaoTest
Running com.cloud.vm.FirstFitPlannerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.433 sec - in 
com.cloud.vm.FirstFitPlannerTest
Running com.cloud.vm.DeploymentPlanningManagerImplTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.525 sec - in 
com.cloud.vm.DeploymentPlanningManagerImplTest
Running com.cloud.vm.snapshot.VMSnapshotManagerTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.16 sec - in 
com.cloud.vm.snapshot.VMSnapshotManagerTest
Running com.cloud.vm.UserVmManagerTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.281 sec - in 
com.cloud.vm.UserVmManagerTest
Running com.cloud.configuration.ValidateIpRangeTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec - in 
com.cloud.configuration.ValidateIpRangeTest
Running com.cloud.configuration.ConfigurationManagerTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.054 sec - in 
com.cloud.configuration.ConfigurationManagerTest
Running com.cloud

RE: discuss [ release process checklist]

[Giles Sirett]

Erik

Somehow you seem to have uncovered my numeric dyslexia  - you are 100% right.

Thread cancelled :-)




Kind Regards
Giles

D: +44 20 3603 0541 | M: +44 796 111 2055
giles.sir...@shapeblue.com




> -Original Message-
> From: Erik Weber [mailto:terbol...@gmail.com]
> Sent: 24 February 2015 09:16
> To: dev
> Cc: market...@cloudstack.apache.org
> Subject: Re: discuss [ release process checklist]
>
> On Tue, Feb 24, 2015 at 10:07 AM, Giles Sirett 
> wrote:
>
> > All
> >
> > Cross posting to  marketing & dev
> >
> > I had the displeasure of reading this article this morning
> >
> > http://www.datacenterknowledge.com/archives/2015/02/23/openstack-vs-
> cl
> > oudstack-the-platforms-and-the-cloud-apis/
> >
> > Initially I thought it was an old article that had been re-hashed, but
> > then   I saw his reference to our downloads page:
> > http://cloudstack.apache.org/downloads.html
> >
> > which clearly says “Apache CloudStack's most current release is 4.4.2”.
> > Hence this article citing it as our current release (yes, theres other
> > badly researched “facts” in the article also)
> >
> >
> Isn't 4.4.2 the newest release in terms of features?
> Yes, 4.3.2 might have been released later, but that's a bugfix release and for
> comparisons it would be better to compare the highest version number?
>
> Or I might be misunderstanding the problem entirely
>
> --
> Erik
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:

[ghxandsky]

Github user ghxandsky commented on the pull request:


https://github.com/apache/cloudstack/commit/0c0c7dd070c146e2f55bfe6a3cebf3ced115690f#commitcomment-9892420
  
No code change?


---
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 #165

[jenkins]

See 

[GitHub] cloudstack pull request: CLOUDSTACK-8280: UI does not display sour...

[DaanHoogland]

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/87#issuecomment-75833513
  
I recognize the problem and did some code to implement it in the response 
generation. might be this didn't make it to any release yet. Have a look at 
ListNetworkACLsCmd.execute and the call to 
_responseGenerator.createNetworkACLItemResponse(acl) in there. It caught me by 
surprise.


---
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:

[terbolous]

Github user terbolous commented on the pull request:


https://github.com/apache/cloudstack/commit/0c0c7dd070c146e2f55bfe6a3cebf3ced115690f#commitcomment-9901732
  
Looks like a bad backport of

https://github.com/apache/cloudstack/commit/c368d3b6eeb41efe508bb0d3e0abe3a4ca5bb8e2
?

On Tue, Feb 24, 2015 at 2:10 PM, Star Guo  wrote:

> No code change?
>
> —
> 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.
---

java 1.8?

[Laszlo Hornyak]

Hi,

Oracle published a warning on java 1.7 EOL a few months ago and just
recently I noticed that there is no java 1.7 in Fedora 21 at all.
At the same time I have some problems building CS on Fedora 21 + OpenJDK
1.8 (CLOUDSTACK-8279)

What are the plans from the JDK-compatibility perspective?
Anyone having the same problems with the tests in java 1.8?

Regards,
Laszlo

-- 

EOF

Re: java 1.8?

[Daan Hoogland]

Laszlo, I didn't try recently but unit tests failed when I first
tried. we should be rather fine, though. unless I missed a
deprecation.

On Tue, Feb 24, 2015 at 9:37 PM, Laszlo Hornyak
 wrote:
> Hi,
>
> Oracle published a warning on java 1.7 EOL a few months ago and just
> recently I noticed that there is no java 1.7 in Fedora 21 at all.
> At the same time I have some problems building CS on Fedora 21 + OpenJDK
> 1.8 (CLOUDSTACK-8279)
>
> What are the plans from the JDK-compatibility perspective?
> Anyone having the same problems with the tests in java 1.8?
>
> Regards,
> Laszlo
>
> --
>
> EOF



-- 
Daan