date:20151216

CS 4.7.0 RC1: bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory

2015-12-16 Thread Milamber


Hello,

On my 4.7.0 RC1 test environment, I've this warning message:
2015-12-15 23:57:35,165 WARN 
[c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(RouterStatusMonitor-1:ctx-f1556e81) (logid:db80c3d4) Unable to get 
alerts from router r-11-VM bash: /opt/cloud/bin/getRouterAlerts.sh: No 
such file or directory


I don't find this bash script anywhere (on management node, host node 
and inside the VR)


I find theses references to this script inside:

public static final String ROUTER_ALERTS = "getRouterAlerts.sh";
./core/src/com/cloud/agent/resource/virtualnetwork/VRScripts.java

ExecutionResult result = _vrDeployer.executeInVR(routerIp, 
VRScripts.ROUTER_ALERTS, args);

./core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java


I use the system vm template from jenkins [1] dated from 02-Dec-2015.

I my understand, the CS 4.7.0 can use the systemvm 4.6?

This is a bug or just I use the wrong systemvm?


[1] 
http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-4.6.0-kvm.qcow2.bz2

[GitHub] cloudstack pull request: [4.7.0/master] DB Paths fixes: 4.5.3->4.7...

2015-12-16 Thread bhaisaab

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/1247#issuecomment-165039772
  
cc @remibergsma @DaanHoogland 


---
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: [4.7.0/master] DB Paths fixes: 4.5.3->4.7...

2015-12-16 Thread bhaisaab

GitHub user bhaisaab opened a pull request:

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

[4.7.0/master] DB Paths fixes: 4.5.3->4.7.0, 4.6.2->4.7.0

- Adds missing upgrade path objects from 4.5.3 to 4.7.0
- Adds an explicit upgrade path class from 4.6.2 to 4.7.0, that extends over
  the upgrade path from 4.6.1 to 4.7.0

Notes:
- The getUpgradableVersionRange() is not used to validate from/to versions 
which is why upgrading from 4.6.2 to 4.7.0 works without any errors when using 
the Upgrade461to470 for 4.6.2 version.

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

$ git pull https://github.com/shapeblue/cloudstack 47-dbpathsfix

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

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


commit 1ce3746d50db3f3e05857854b596e749760075fd
Author: Rohit Yadav 
Date:   2015-12-16T09:01:00Z

engine/schema: Fix upgrade paths 4.5.3->4.7.0, 4.6.2->4.7.0

- Adds missing upgrade path objects from 4.5.3 to 4.7.0
- Adds an explicit upgrade path class from 4.6.2 to 4.7.0, that extends over
  the upgrade path from 4.6.1 to 4.7.0

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: [VOTE] Apache CloudStack 4.7.0

2015-12-16 Thread Stephan Seitz

Hi devs,

could someone please test VR in advanced networking? In detail: adding
>=10 public IPs and adding >=5 firewall and portforwarding rules to
each of the IPs.
I've noticed that each single call into the VR updates and verifies the
whole set of rules. I don't know if this was introduced around 4.5 or
if I just hit an edgecase recently. Using more than a few IPs/rules is
not only really time consuming, in case of a network/VR restart it also
leads to a VR shutdown (maybe some watchdog kicks in after a timeout).

Thanks, and sorry that I don't have enough ressources this year to
check this on my own.

Stephan


Am Mittwoch, den 16.12.2015, 08:34 +0100 schrieb Boris Schrijver:
> Hi all,
> 
> Hereby my vote for the ACS 4.7.0 RC 1
> 
> Details:
> 
> Vote: +1
> 
> Besides the integration tests (which all ran fine) I've also tested
> the
> following:
> 
>  - S3 Integration (Secondary Storage) with NFS Staging store
>  - Ceph RBD storage (Primary Storage)
>  - Basic networking with security groups 
> 
> -- 
> 
> Met vriendelijke groet / Kind regards,
> 
> Boris Schrijver
> 
> PCextreme B.V.
> 
> http://www.pcextreme.nl/contact
> Tel direct: +31 (0) 118 700 215
> 
> > On December 16, 2015 at 12:34 AM Remi Bergsma <
> > rberg...@schubergphilis.com>
> > wrote:
> > 
> > 
> > +1 (binding)
> > 
> > This vote is based on testing on a real cloud.
> > 
> > At Schuberg Philis we built a new cloud based on ACS 4.7.0RC1
> > (upgraded from
> > 4.6). It runs XenServer 6.5 clusters, a CentOS 7 management
> > cluster, Galera DB
> > (also on CentOS 7), HA proxies (CentOS 7), NFS storage and
> > Nicira/NSX for
> > networking/SDN. Capacity to start with is about 12TB ram and 500+
> > cores.
> > Secondary storage is an S3 compatible solution (Cloudian) with NFS
> > staging
> > store. Configured LDAP for authentication.
> > 
> > Before a go-live we always do thorough testing and try to break the
> > setup
> > emulating crashes and problems.
> > 
> > We successful executed these CloudStack related tests:
> > 
> >   *   crashed a hypervisor which was poolmaster and saw recovery in
> > about 5
> > min (tested with/without returning of the hypervisor)
> >   *   crashed a hypervisor which was NOT poolmaster and saw
> > recovery in about
> > 5 min (tested with/without returning of the hypervisor)
> >   *   crashed overbooked hypervisor in a cluster with too many VMs
> > to run on
> > the remaining hypervisors. Saw it recovered fully when crashed
> > hypervisor
> > returned. (this you don’t want to happen, but at least the recovery
> > was
> > automatic)
> >   *   crashed one of the app servers; the other one continued and
> > took over.
> > No user impact.
> >   *   crashed the main Galera DB node, the two remaining nodes
> > survived and
> > kept working. No CloudStack impact.
> >   *   did performance tests and walked into the default 200mbps
> > limit on
> > tiers. When we removed it (aka configured it properly) we could use
> > full
> > 10gbps.
> >   *   crashed the NFS staging store, could not deploy VM from
> > template that
> > was not already on primary storage. Recovered automatically when
> > NFS returned
> > and VM was started.
> >   *   many functional tests, also covered In the integration tests
> > (spin many
> > VMs, migrate, make port forwardings etc).
> >   *   executed patch round (live migrating vms around), rebooting
> > all
> > hypervisors without user impact.
> > 
> > Conclusion:
> > It’s pretty solid, even with one management server and a degraded
> > database we
> > could still continue and operate existing VMs and start new ones.
> > When the
> > nodes returned recovery was automatic.
> > We feel confident running production with Apache CloudStack 4.7 and
> > will start
> > doing so later today!
> > 
> > Regards,
> > Remi
> > 
> > PS:
> > The integration tests we run in the dev/test environments were also
> > successful
> > (the same I executed on the PRs that were merged).
> > 
> > 
> > 
> > From: Remi Bergsma
> > mailto:rberg...@schubergphilis.com>>
> > Date: Sunday 13 December 2015 21:27
> > To: "dev@cloudstack.apache.org"
> > mailto:dev@cloudstack.apache.org>>
> > Subject: [VOTE] Apache CloudStack 4.7.0
> > 
> > Hi all,
> > 
> > Since our 4.6.0 release (on Nov 13th, exactly 1 month ago), we have
> > merged
> > 100+ pull requests [1] with lots of bug fixes, refactoring and of
> > course new
> > features. Time for a new release!
> > 
> > 
> > I've created a 4.7.0 release candidate, with the following
> > artifacts up for a
> > vote:
> > 
> > Git Branch and Commit SH:
> > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog
> > ;h=4.7.0-RC20151213T2109
> > 
> > Commit: 2f26a859a971a9852ed9f6f34fe35e52fe6028a9
> > 
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.7.0/
> > 
> > PGP release keys (signed using A47DDC4F):
> > https://dist.apache.org/repos/dist/release/clouds

[GitHub] cloudstack pull request: CLOUDSTACK-9146: Refactor Hypervisor KVM ...

2015-12-16 Thread DaanHoogland

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1224#issuecomment-165057616
  
@wilderrodrigues ok, I see how you meant 'should' now, please convince 
Rohit, not me. I you want to convince me you have to argue why we should keep 
maven n favour of make;)


---
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: Bug-ID: CLOUDSTACK-8654: Added guest_os m...

2015-12-16 Thread DaanHoogland

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1244#issuecomment-165059827
  
LGTM, not tested


---
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-9175: [VMware DRS] Adding new ...

2015-12-16 Thread sureshanaparti

GitHub user sureshanaparti opened a pull request:

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

CLOUDSTACK-9175: [VMware DRS] Adding new host to DRS cluster does not 
participate in load balancing.

Summary: When a new host is added to a cluster, Cloudstack doesn't create 
all the port groups (created by cloudstack earlier in other hosts) present in 
the cluster. Since the new host doesn't have all the necessary networking port 
groups of cloudstack, it is not eligible to participate in DRS load balancing 
or HA.

Solution: When adding a host to the cluster in Cloudstack, use VMware API 
to find the list of unique port groups on a previously added host (older host 
in the cluster) if exists and then create them on the new host.

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

$ git pull https://github.com/sureshanaparti/cloudstack 
CLOUDSTACK-9175_VMwareDRSIssue

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

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


commit c22ce365936ac08e28527d9192277d8768ecabfa
Author: Suresh Kumar Anaparti 
Date:   2015-09-21T14:27:03Z

CLOUDSTACK-7151: Support multiple physical networks at cluster level for 
guest traffic over VMware deployments.

commit 0d51865f0f7d679d068dd510e00e431ba02c36d8
Author: Suresh Kumar Anaparti 
Date:   2015-12-15T11:48:31Z

Revert "CLOUDSTACK-7151: Support multiple physical networks at cluster 
level for guest traffic over VMware deployments."

This reverts commit c22ce365936ac08e28527d9192277d8768ecabfa.

commit 2bdb194783284cdf9bdd067f8e757e913151029f
Author: Suresh Kumar Anaparti 
Date:   2015-12-15T12:13:53Z

Merge branch 'master' of https://github.com/sureshanaparti/cloudstack

commit d3c3f498d19ae623e6b658627087cfc2ec734e67
Author: Suresh Kumar Anaparti 
Date:   2015-12-16T10:29:14Z

CLOUDSTACK-9175: [VMware DRS] Adding new host to DRS cluster does not 
participate in load balancing.

Summary: When a new host is added to a cluster, Cloudstack doesn't create 
all the port groups (created by cloudstack earlier in other hosts) present in 
the cluster. Since the new host doesn't have all the necessary networking port 
groups of cloudstack, it is not eligible to participate in DRS load balancing 
or HA.
Solution: When adding a host to the cluster in Cloudstack, use VMware API 
to find the list of unique port groups on a previously added host (older host 
in the cluster) if exists and then create them on the new host.




---
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-9181 Prevent syntax error in c...

2015-12-16 Thread remibergsma

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1249#issuecomment-165060510
  
Ping @sspans @wilderrodrigues to review.


---
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-9181 Prevent syntax error in c...

2015-12-16 Thread remibergsma

GitHub user remibergsma opened a pull request:

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

CLOUDSTACK-9181 Prevent syntax error in checkrouter.sh

Added quotes to prevent syntax errors in weird situations.

Error seen in mgt server:
```
2015-12-15 14:30:32,371 DEBUG [c.c.a.m.AgentManagerImpl] 
(RedundantRouterStatusMonitor-7:ctx-0dd8ef3e) Details from executing class 
com.cloud.agent.api.CheckRouterCommand: Status: UNKNOWN
/opt/cloud/bin/checkrouter.sh: line 28: [: =: unary operator expected
/opt/cloud/bin/checkrouter.sh: line 31: [: =: unary operator expected
```
Cause:
```
root@r-1191-VM:/opt/cloud/bin# ./checkrouter.sh
./checkrouter.sh: line 28: [: =: unary operator expected
./checkrouter.sh: line 31: [: =: unary operator expected
Status: UNKNOWN
```

Somehow a nic was missing.

After fix the script can handle this:

```
root@r-1191-VM:/opt/cloud/bin# ./checkrouter.sh
Status: UNKNOWN
```

The other states are also reported fine:
```
root@r-1191-VM:/opt/cloud/bin# ./checkrouter.sh
Status: MASTER
```

```
root@r-1192-VM:/opt/cloud/bin# ./checkrouter.sh
Status: BACKUP
```


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

$ git pull https://github.com/remibergsma/cloudstack fix-checkrouter-script

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

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


commit b7785fc70e95d8da5936fcad34de026d1d04982a
Author: Remi Bergsma 
Date:   2015-12-16T10:27:26Z

CLOUDSTACK-9181 Prevent syntax error in checkrouter.sh




---
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: [VOTE] Apache CloudStack 4.7.0

2015-12-16 Thread Rohit Yadav

Hi all,

I’ve tested 4.6.2 to 4.7.0 database upgrades and it works because there are no 
checks in the code wrt from/to versions declared in an upgrade classes. The 
other issue is the upgrade path for 4.5.3 is broken and would not upgrade it to 
4.7.0, but leave it in between. I’ve sent a PR for review that fixes these 
issues: https://github.com/apache/cloudstack/pull/1247

It’s debatable whether we need to care about 4.5.3 as it’s not released yet, in 
which case we can aim to fix the db issue for 4.7.1+. Though, in my opinion the 
issue is a blocker as it would leave future users of 4.5.3 in a bad state if 
they decide to upgrade to 4.7.0 (assuming 4.5.3 should be out soon after 
4.6.2/4.7.0) so I’m casting the following for now:

-1 (binding)


Meanwhile, I’m testing 4.7.0-rc1 and following works for me:

- Life cycle tests with KVM (CentOS6 and Ubuntu 14.04 based)
- Regression testing: SAML single-sign on, several minor KVM enhancements
- Metrics UI views
- Upgrade tests from 4.5.2 and from 4.6.2 (note: if pre 4.5 users with multiple 
zones/secondary storages try to upgrade to 4.7.0, they would likely hit 
systemvm template not synced across all secondary storages issue; fix is to 
rsync or cp all systemvm template folder across all zones/secondary storages 
and mark that template as Active in DB)

(yet to test with XenServer and VMware, and using CentOS7 as KVM host and mgmt 
server host)

Repos used:
http://packages.shapeblue.com/cloudstack/testing/centos/4.7
http://packages.shapeblue.com/cloudstack/testing/centos7/4.7 
http://packages.shapeblue.com/cloudstack/testing/debian/4.7

SystemVM template used:
http://packages.shapeblue.com/systemvmtemplate/4.6

Regards.


[ShapeBlue]
Rohit Yadav
Software Architect  ,   ShapeBlue


d:  +44 203 603 0540 | s:   |  
m:  +91 8826230892

e:  rohit.ya...@shapeblue.com | t: 
   |  w:  
www.shapeblue.com

a:  53 Chandos Place, Covent Garden London WC2N 4HS UK


[cid:image58f498.png@dc0d96a2.40b5e854]


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




On 16-Dec-2015, at 12:20 AM, Rohit Yadav 
mailto:rohit.ya...@shapeblue.com>> wrote:

On 15-Dec-2015, at 10:34 PM, Wilder Rodrigues 
mailto:wrodrig...@schubergphilis.com>> wrote:

Rohit voted -1, but I did not have any problem upgrading from 4.6.2 to 4.7.0. 
Concerning the issue with 4.5.3, I would not consider it a blocker since 4.5.3 
was not even released. So, you have time to get it working or first go to 4.6.0.

I’ll test again upgrading from 4.6.2 to 4.7.0 tomorrow and keep you posted, 
based on the code the from/to versions in the upgrade path classes are 
incorrect but if it’s still passing then likely the database upgrader/checker 
may not be enforcing.

I did not start with 4.5.3 release efforts in order to not dilute other release 
efforts, I plan to work on it post 4.7.0. There is an upgrade path from 4.5.3 
which is incorrect - either it should not be there in the first place or it 
must be correctly fixed. We should be releasing CloudStack which can cause DB 
upgrade issues for previous/older release's users. While it may not be a 
blocker, this need to be fixed either in 4.7.0 or in 4.7.1 (future minor 
release then :) ).

Regards.
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

[GitHub] cloudstack pull request: [4.7.0/master] DB Paths fixes: 4.5.3->4.7...

2015-12-16 Thread remibergsma

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1247#issuecomment-165061200
  
@bhaisaab Thanks for fixing / improving this. Will have a look and test it. 
Are you OK with handling this in 4.7.1 (due in say 2 weeks)? By that time 4.5.3 
is also there.


---
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-9161: fix the quota marvin tes...

2015-12-16 Thread DaanHoogland

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1240#issuecomment-165062191
  
@agneya2001 your solution LGTM

@remibergsma will you put it in your regression suite anyway? It does run 
in the bubble (limitation of warranty; I tested that before the move to 
test/integration/plugin)


---
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: [4.7.0/master] DB Paths fixes: 4.5.3->4.7...

2015-12-16 Thread bhaisaab

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/1247#issuecomment-165062188
  
@remibergsma yes, I've already shared this on dev@ that we need to fix this 
either in 4.7.0 or 4.7.1 :)
Since, it's not a blocker for 4.7.0 per se we don't need to stop the voting 
but it would be ideal if we could fix the issue in 4.7.0


---
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: automated CLOUDSTACK 9177 9178 9179

2015-12-16 Thread shwetaag

GitHub user shwetaag opened a pull request:

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

automated CLOUDSTACK 9177 9178 9179

Automated three test cases for Cloud stack 
First is  Atomation of Usage events for "uploadedVolume" 
Second  is Verify correct Guest OS (RHEL 7) Mapping for vmware  
Third is  Verify register ssh key pair can not be used to register same ssh 
keys with different name

More details on the given  bugs 

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

$ git pull https://github.com/shwetaag/cloudstack bug_fixes

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

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


commit 3efd5d60871510984c47a78113f704019e37bb73
Author: shweta agarwal 
Date:   2015-12-16T10:35:33Z

automated CLOUDSTACK 9177 9178 9179




---
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: [VOTE] Apache CloudStack 4.7.0

2015-12-16 Thread Abhinandan Prateek

+0

Created a cluster with 2 Xen 6.5.
Manually tested vm-lifecycle, live migration, snapshots, iso download, VPC s, 
firewall, PF rules, console proxy.

Ran several integration tests.
On quota found one issue, due to parallely running integration tests that were 
adding and removing accounts: 
https://issues.apache.org/jira/browse/CLOUDSTACK-9174

Voting +0 as the release is solid, but wish that the above quota fix and 
CLOUDSTACK-9161 are also included.

Regards,

-abhi

[ShapeBlue]
Abhinandan Prateek
Software Architect  ,   ShapeBlue

d:  +44 203 603 0540 | s:   |  
m:  +91 970 11 99011

e:  abhinandan.prat...@shapeblue.com | t: 
 |  w:  
www.shapeblue.com

a:  53 Chandos Place, Covent Garden London WC2N 4HS UK

[cid:image80c48b.png@7456ca94.4782da63]

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

On 14/12/15, 1:57 AM, "Remi Bergsma"  wrote:

>Hi all,
>
>Since our 4.6.0 release (on Nov 13th, exactly 1 month ago), we have merged 
>100+ pull requests [1] with lots of bug fixes, refactoring and of course new 
>features. Time for a new release!
>
>
>I've created a 4.7.0 release candidate, with the following artifacts up for a 
>vote:
>
>Git Branch and Commit SH:
>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=4.7.0-RC20151213T2109
>
>Commit: 2f26a859a971a9852ed9f6f34fe35e52fe6028a9
>
>Source release (checksums and signatures are available at the same location):
>https://dist.apache.org/repos/dist/dev/cloudstack/4.7.0/
>
>PGP release keys (signed using A47DDC4F):
>https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
>Vote will be open for at least 72 hours.
>
>For sanity in tallying the vote, can PMC members please be sure to indicate 
>"(binding)" with their vote?
>
>[ ] +1 approve
>[ ] +0 no opinion
>[ ] -1 disapprove (and reason why)
>
>
>[1] git log --pretty=oneline --abbrev-commit origin/4.6..4.7.0-RC20151213T2109 
>| grep "Merge pull request"
>
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

Re: CS 4.7.0 RC1: bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory

2015-12-16 Thread Remi Bergsma

Hi Milamber,

Nice find! Yes, the 4.6 systemvm template is fine. The 4.7 systemvm.iso 
contains all changed files that we need.

I see getRouterAlerts.sh in 4.6 but not in 4.7/master. Since I upgraded it 
still works for me somehow. Will need to investigate why that is.

It looks like regression from 6477bd8ff7f982e10d0d20a97857262897dc05ed, PR 1084.

Did you create an issue for it? It’s not a big issue I’d say.

Regards,
Remi





On 16/12/15 09:15, "Milamber"  wrote:

>Hello,
>
>On my 4.7.0 RC1 test environment, I've this warning message:
>2015-12-15 23:57:35,165 WARN 
>[c.c.n.r.VirtualNetworkApplianceManagerImpl] 
>(RouterStatusMonitor-1:ctx-f1556e81) (logid:db80c3d4) Unable to get 
>alerts from router r-11-VM bash: /opt/cloud/bin/getRouterAlerts.sh: No 
>such file or directory
>
>I don't find this bash script anywhere (on management node, host node 
>and inside the VR)
>
>I find theses references to this script inside:
>
> public static final String ROUTER_ALERTS = "getRouterAlerts.sh";
>./core/src/com/cloud/agent/resource/virtualnetwork/VRScripts.java
>
> ExecutionResult result = _vrDeployer.executeInVR(routerIp, 
>VRScripts.ROUTER_ALERTS, args);
>./core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java
>
>
>I use the system vm template from jenkins [1] dated from 02-Dec-2015.
>
>I my understand, the CS 4.7.0 can use the systemvm 4.6?
>
>This is a bug or just I use the wrong systemvm?
>
>
>[1] 
>http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-4.6.0-kvm.qcow2.bz2
>
>

[VOTE] Apache CloudStack 4.7.0

2015-12-16 Thread Keerthiraja SJ

Hi All,

I could not able to perform the PVLAN as per below wiki on 4.7.0.
Is any one tested it.

https://cwiki.apache.org/confluence/display/CLOUDSTACK/PVLAN+for+isolation+within+a+VLAN

Thanks,
Keerthi

Re: [VOTE] Apache CloudStack 4.7.0

2015-12-16 Thread Remi Bergsma

Hi Rohit,

Thanks for the PR. I think we will do 4.7.1 in about 2 weeks time, so that’s 
around the time 4.5.3 will also be there. Wouldn’t that just be fine? For now, 
4.5.3 is not there yet so blocking a release based on that doesn’t seem fair to 
me.

Let’s get the new stuff to our users (we will get even more feedback) and then 
improve it. We will release 4.7.1 soon, like we did with 4.6.1. In other words, 
I think releasing fast is better than trying to be perfect and causing delays.

Agree?

Regards,
Remi


From: Rohit Yadav mailto:rohit.ya...@shapeblue.com>>
Reply-To: "dev@cloudstack.apache.org" 
mailto:dev@cloudstack.apache.org>>
Date: Wednesday 16 December 2015 11:36
To: "dev@cloudstack.apache.org" 
mailto:dev@cloudstack.apache.org>>
Subject: Re: [VOTE] Apache CloudStack 4.7.0

Hi all,

I’ve tested 4.6.2 to 4.7.0 database upgrades and it works because there are no 
checks in the code wrt from/to versions declared in an upgrade classes. The 
other issue is the upgrade path for 4.5.3 is broken and would not upgrade it to 
4.7.0, but leave it in between. I’ve sent a PR for review that fixes these 
issues: https://github.com/apache/cloudstack/pull/1247

It’s debatable whether we need to care about 4.5.3 as it’s not released yet, in 
which case we can aim to fix the db issue for 4.7.1+. Though, in my opinion the 
issue is a blocker as it would leave future users of 4.5.3 in a bad state if 
they decide to upgrade to 4.7.0 (assuming 4.5.3 should be out soon after 
4.6.2/4.7.0) so I’m casting the following for now:

-1 (binding)


Meanwhile, I’m testing 4.7.0-rc1 and following works for me:

- Life cycle tests with KVM (CentOS6 and Ubuntu 14.04 based)
- Regression testing: SAML single-sign on, several minor KVM enhancements
- Metrics UI views
- Upgrade tests from 4.5.2 and from 4.6.2 (note: if pre 4.5 users with multiple 
zones/secondary storages try to upgrade to 4.7.0, they would likely hit 
systemvm template not synced across all secondary storages issue; fix is to 
rsync or cp all systemvm template folder across all zones/secondary storages 
and mark that template as Active in DB)

(yet to test with XenServer and VMware, and using CentOS7 as KVM host and mgmt 
server host)

Repos used:
http://packages.shapeblue.com/cloudstack/testing/centos/4.7
http://packages.shapeblue.com/cloudstack/testing/centos7/4.7 
http://packages.shapeblue.com/cloudstack/testing/debian/4.7

SystemVM template used:
http://packages.shapeblue.com/systemvmtemplate/4.6

Regards.


[ShapeBlue]
Rohit Yadav
Software Architect  ,   ShapeBlue


d:  +44 203 603 0540 | s:   |  
m:  +91 8826230892

e:  rohit.ya...@shapeblue.com | t: 
   |  w:  
www.shapeblue.com

a:  53 Chandos Place, Covent Garden London WC2N 4HS UK


[cid:image58f498.png@dc0d96a2.40b5e854]


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




On 16-Dec-2015, at 12:20 AM, Rohit Yadav 
mailto:rohit.ya...@shapeblue.com>> wrote:

On 15-Dec-2015, at 10:34 PM, Wilder Rodrigues 
mailto:wrodrig...@schubergphilis.com>> wrote:

Rohit voted -1, but I did not have any problem upgrading from 4.6.2 to 4.7.0. 
Concerning the issue with 4.5.3, I would not consider it a blocker since 4.5.3 
was not even released. So, you have time to get it working or first go to 4.6.0.

I’ll test again upgrading from 4.6.2 to 4.7.0 tomorrow and keep you posted, 
based on the code the from/to versions in the upgrade path classes are 
incorrect but if it’s still passing then likely the database upgrader/checker 
may not be enforcing.

I did not start with 4.5.3 release efforts in order to not dilute other release 
efforts, I plan to work on it post 4.7.0. There is an upgrade path from 4.5.3 
which is incorrect - either it should not be there in the first place or it 
must be correctly fixed. We should be releasing CloudStack which can

[GitHub] cloudstack pull request: CLOUDSTACK-9181 Prevent syntax error in c...

2015-12-16 Thread sspans

Github user sspans commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1249#discussion_r47763613
  
--- Diff: systemvm/patches/debian/config/opt/cloud/bin/checkrouter.sh ---
@@ -17,21 +17,20 @@
 # under the License.
 
 STATUS=UNKNOWN
-INTERFACE=eth1
 ROUTER_TYPE=$(cat /etc/cloudstack/cmdline.json | grep type | awk '{print 
$2;}' | sed -e 's/[,\"]//g')
-if [ $ROUTER_TYPE = "router" ]
+if [ "$ROUTER_TYPE" = "router" ]
 then
ROUTER_STATE=$(ip addr | grep eth0 | grep inet | wc -l | xargs bash -c  
'if [ $0 == 2 ]; then echo "MASTER"; else echo "BACKUP"; fi')
STATUS=$ROUTER_STATE
 else
-   ROUTER_STATE=$(ip addr | grep $INTERFACE | grep state | awk '{print 
$9;}')
-   if [ $ROUTER_STATE = "UP" ]
+   ROUTER_STATE=$(ip addr | grep eth1 | grep state | awk '{print $9;}')
--- End diff --

You didn't mention the INTERFACE -> eth1 change in your commit description, 
can you leave that part out?


---
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: [VOTE] Apache CloudStack 4.7.0

2015-12-16 Thread Rohit Yadav

Hi Remi,


[ShapeBlue]
Rohit Yadav
Software Architect  ,   ShapeBlue


d:  +44 203 603 0540 | s:   |  
m:  +91 8826230892

e:  rohit.ya...@shapeblue.com | t: 
   |  w:  
www.shapeblue.com

a:  53 Chandos Place, Covent Garden London WC2N 4HS UK


[cid:imagefac66c.png@91490132.44b2ccf0]


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




On 16-Dec-2015, at 4:40 PM, Remi Bergsma 
mailto:rberg...@schubergphilis.com>> wrote:

Let’s get the new stuff to our users (we will get even more feedback) and then 
improve it. We will release 4.7.1 soon, like we did with 4.6.1. In other words, 
I think releasing fast is better than trying to be perfect and causing delays.

Agree?

Alright, agree.

Replacing my -1 vote with a +0 (binding) vote for now (as I’m still not done 
with my testings).

Regards.
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

[GitHub] cloudstack pull request: CLOUDSTACK-8847: ListServiceOfferings is ...

2015-12-16 Thread nitin-maharana

Github user nitin-maharana commented on the pull request:

https://github.com/apache/cloudstack/pull/823#issuecomment-165074680
  
@agneya2001 : If the new service offering wants in change of deployment 
then it should be fine. But the change affects after reboot only. Thanks.


---
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-9132: API createVolume takes e...

2015-12-16 Thread nitin-maharana

Github user nitin-maharana commented on the pull request:

https://github.com/apache/cloudstack/pull/1206#issuecomment-165076449
  
@rafaelweingartner : Thanks for the suggestion. I will follow the same to 
write test cases for this.
@DaanHoogland : Should we make the Name field as optional in UI as well as 
API?

Thanks.


---
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-9132: API createVolume takes e...

2015-12-16 Thread DaanHoogland

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1206#issuecomment-165081512
  
@nitin-maharana that would be my preference. In the UI a pop-up could 
explain the consequence of not entering a name.


---
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-9175: [VMware DRS] Adding new ...

2015-12-16 Thread resmo

Github user resmo commented on the pull request:

https://github.com/apache/cloudstack/pull/1248#issuecomment-165088002
  
`older` is a bit misleading, what about `existent` e.g. 
findExistentHypervisorHostInCluster?


---
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-9180: Optimize concurrent VM d...

2015-12-16 Thread koushik-das

GitHub user koushik-das opened a pull request:

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

CLOUDSTACK-9180: Optimize concurrent VM deployment operation on same â¦

â¦network

Check if VR needs to be allocated for a given network and only acquire lock 
if required

Refer to the bug for details.

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

$ git pull https://github.com/koushik-das/cloudstack CLOUDSTACK-9180

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

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


commit de8942644df26fdd97010f8eec1fddf7d97fc8ae
Author: Koushik Das 
Date:   2015-12-16T12:23:03Z

CLOUDSTACK-9180: Optimize concurrent VM deployment operation on same network
Check if VR needs to be allocated for a given network and only acquire lock 
if required




---
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-9180: Optimize concurrent VM d...

2015-12-16 Thread koushik-das

Github user koushik-das commented on the pull request:

https://github.com/apache/cloudstack/pull/1251#issuecomment-165092578
  
Simulator test results for basic zone. Failure is for NiciraNvp which can 
be ignored.

-

test DeployVM in anti-affinity groups ... === TestName: 
test_DeployVmAntiAffinityGroup | Status : SUCCESS ===
ok
Test to deploy vm with a first fit offering ... === TestName: 
test_deployvm_firstfit | Status : SUCCESS ===
ok
Test deploy VMs using user concentrated planner ... === TestName: 
test_deployvm_userconcentrated | Status : SUCCESS ===
ok
Test deploy VMs using user dispersion planner ... === TestName: 
test_deployvm_userdispersing | Status : SUCCESS ===
ok
Test to create disk offering ... === TestName: test_01_create_disk_offering 
| Status : SUCCESS ===
ok
Test to create  a sparse type disk offering ... === TestName: 
test_02_create_sparse_type_disk_offering | Status : SUCCESS ===
ok
Test to create  a sparse type disk offering ... === TestName: 
test_04_create_fat_type_disk_offering | Status : SUCCESS ===
ok
Test to update existing disk offering ... === TestName: 
test_02_edit_disk_offering | Status : SUCCESS ===
ok
Test to delete disk offering ... === TestName: test_03_delete_disk_offering 
| Status : SUCCESS ===
ok
test update configuration setting at zone level scope ... === TestName: 
test_UpdateConfigParamWithScope | Status : SUCCESS ===
ok
test_nic_secondaryip_add_remove 
(integration.smoke.test_multipleips_per_nic.TestDeployVM) ... === TestName: 
test_nic_secondaryip_add_remove | Status : SUCCESS ===
ok
Failure: ImportError (cannot import name NiciraNvp) ... === TestName: 
Failure: | Status : EXCEPTION ===
ERROR
Test to create a portable public ip range ... === TestName: 
test_createPortablePublicIPRange | Status : SUCCESS ===
ok
Test primary storage pools - XEN, KVM, VMWare. Not Supported for hyperv ... 
=== TestName: test_01_primary_storage_nfs | Status : SUCCESS ===
ok
Test reset virtual machine on reboot ... === TestName: 
test_01_reset_vm_on_reboot | Status : SUCCESS ===
ok
Test system VM start ... === TestName: test_01_sys_vm_start | Status : 
SUCCESS ===
ok
Test system templates are ready ... === TestName: 
test_02_sys_template_ready | Status : SUCCESS ===
ok
Test to create service offering ... === TestName: 
test_01_create_service_offering | Status : SUCCESS ===
ok
Test to update existing service offering ... === TestName: 
test_02_edit_service_offering | Status : SUCCESS ===
ok
Test to delete service offering ... === TestName: 
test_03_delete_service_offering | Status : SUCCESS ===
ok
Test Edit template ... === TestName: test_02_edit_template | Status : 
SUCCESS ===
ok
Test delete template ... === TestName: test_03_delete_template | Status : 
SUCCESS ===
ok
Update & Test for template permissions ... === TestName: 
test_05_template_permissions | Status : SUCCESS ===
ok
Test only public templates are visible to normal user ... === TestName: 
test_07_list_public_templates | Status : SUCCESS ===
ok
Test System templates are not visible to normal user ... === TestName: 
test_08_list_system_templates | Status : SUCCESS ===
ok
Download a Volume attached to a VM ... === TestName: 
test_03_download_attached_volume | Status : SUCCESS ===
ok
Delete a Volume attached to a VM ... === TestName: 
test_04_delete_attached_volume | Status : SUCCESS ===
ok
Detach a Volume attached to a VM ... === TestName: test_05_detach_volume | 
Status : SUCCESS ===
ok
Delete a Volume unattached to an VM ... === TestName: 
test_09_delete_detached_volume | Status : SUCCESS ===
ok

Ran 29 tests in 462.825s

FAILED (errors=1)

---


Selective advanced zone tests on simulator
---

test_vm_life_cycle.py

Test advanced zone virtual router ... === TestName: 
test_advZoneVirtualRouter | Status : SUCCESS ===
ok
Test Deploy Virtual Machine ... === TestName: test_deploy_vm | Status : 
SUCCESS ===
ok
Test Multiple Deploy Virtual Machine ... === TestName: 
test_deploy_vm_multiple | Status : SUCCESS ===
ok
Test Stop Virtual Machine ... === TestName: test_01_stop_vm | Status : 
SUCCESS ===
ok
Test Start Virtual Machine ... === TestName: test_02_start_vm | Status : 
SUCCESS ===
ok
Test Reboot Virtual Machine ... === TestName: test_03_reboot_vm | Status : 
SUCCESS ===
ok
Test destroy Virtual Machine ... === TestName: test_06_destroy_vm | Status 
: SUCCESS ===
ok
Test recover Virtual Machine ... === TestName

[GitHub] cloudstack pull request: CLOUDSTACK-9182: Some running VMs turned ...

2015-12-16 Thread sureshanaparti

GitHub user sureshanaparti opened a pull request:

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

CLOUDSTACK-9182: Some running VMs turned off on manual migration when auto 
migration failed while host preparing for maintenance.

CLOUDSTACK-9182: Some running VMs turned off on manual migration when auto 
migration failed while host preparing for maintenance.

Fix: Block VMOperations if Host in PrepareForMaintenance mode. VM 
operations (Stop, Reboot, Destroy, Migrate to host) are not allowed when Host 
in PrepareForMaintenance mode.

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

$ git pull https://github.com/sureshanaparti/cloudstack CLOUDSTACK-9182

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

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


commit 98186f9e6a3f659ac294a30b2243070961c167fe
Author: Suresh Kumar Anaparti 
Date:   2015-12-16T12:31:30Z

CLOUDSTACK-9182: Some running VMs turned off on manual migration when auto 
migration failed while host preparing for maintenance.

Fix: Block VMOperations if Host in PrepareForMaintenance mode. VM 
operations (Stop, Reboot, Destroy, Migrate to host) are not allowed when Host 
in PrepareForMaintenance mode.




---
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: CS 4.7.0 RC1: bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory

2015-12-16 Thread Wilder Rodrigues

Hi there… 

What kind of hypervisor do you have?

Cheers,
Wilder


> On 16 Dec 2015, at 09:15, Milamber  wrote:
> 
> Hello,
> 
> On my 4.7.0 RC1 test environment, I've this warning message:
> 2015-12-15 23:57:35,165 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (RouterStatusMonitor-1:ctx-f1556e81) (logid:db80c3d4) Unable to get alerts 
> from router r-11-VM bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or 
> directory
> 
> I don't find this bash script anywhere (on management node, host node and 
> inside the VR)
> 
> I find theses references to this script inside:
> 
>public static final String ROUTER_ALERTS = "getRouterAlerts.sh";
> ./core/src/com/cloud/agent/resource/virtualnetwork/VRScripts.java
> 
>ExecutionResult result = _vrDeployer.executeInVR(routerIp, 
> VRScripts.ROUTER_ALERTS, args);
> ./core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java
> 
> 
> I use the system vm template from jenkins [1] dated from 02-Dec-2015.
> 
> I my understand, the CS 4.7.0 can use the systemvm 4.6?
> 
> This is a bug or just I use the wrong systemvm?
> 
> 
> [1] 
> http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-4.6.0-kvm.qcow2.bz2
> 
>

Re: [VOTE] Apache CloudStack 4.7.0

2015-12-16 Thread Sebastien Goasguen

Just a quick note here,

We are getting in the holidays season, and we have not yet discussed all 
implications of our new workflow and ability to release much faster.

- Upgrade is a big thing for us, so let’s make sure we keep getting it right.
- We need to have a discussion about which branch to keep maintaining and what 
upgrade paths to maintain...
- We need to sort out some automation around release notes and publishing on 
the website (4.6.1 is not yet publicized on the website…).

So while I love the speed, I would also welcome a step back to see what other 
things we need to sort out before we start releasing like “maniacs” (in a good 
way) :)

-sebastien

> On Dec 16, 2015, at 12:25 PM, Rohit Yadav  wrote:
> 
> Hi Remi,
> 
> 
>   
> Rohit Yadav
> Software Architect,   ShapeBlue
> d:+44 203 603 0540 | s:|  m:  +91 8826230892
> e:rohit.ya...@shapeblue.com | t:   |  w:  www.shapeblue.com
> a:53 Chandos Place, Covent Garden London WC2N 4HS UK
> 
> 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.
> 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.
> 
> 
>> On 16-Dec-2015, at 4:40 PM, Remi Bergsma  wrote:
>> 
>> Let’s get the new stuff to our users (we will get even more feedback) and 
>> then improve it. We will release 4.7.1 soon, like we did with 4.6.1. In 
>> other words, I think releasing fast is better than trying to be perfect and 
>> causing delays.
>> 
>> Agree?
> 
> Alright, agree.
> 
> Replacing my -1 vote with a +0 (binding) vote for now (as I’m still not done 
> with my testings).
> 
> Regards.
> 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

[GitHub] cloudstack pull request: CLOUDSTACK-8847: ListServiceOfferings is ...

2015-12-16 Thread agneya2001

Github user agneya2001 commented on the pull request:

https://github.com/apache/cloudstack/pull/823#issuecomment-165102057
  
@nitin-maharana i am wondering why should change in service offering have 
any restrictions on tags ?  @kishankavala any usage implications.


---
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: [VOTE] Apache CloudStack 4.6.2

2015-12-16 Thread Wido den Hollander

Vote: +1 (binding)

I've verified the test results from Boris and they look good.

These tests were done at our office and also tested against our local
Ceph cluster.

Wido

On 15-12-15 09:26, Boris Schrijver wrote:
> Hi!
> 
> Tested this RC over the past two days. Looking good!
> 
> Details:
> 
> Version: ACS 4.6.2 RC1
> 
> Vote: +1
> 
> Besides the integration tests underneath I have also tested manually against 
> S3
> and Ceph.
> 
> **Environment**
>  - 2 KVM host on CentOS 7.1
>  - 1 Management Server on CentOS 7.1
>  - Agent + Common RPMs built from source
> 
> **Integration test suite 1**
> ```
> nosetests --with-marvin --marvin-config=${marvinCfg} -s -a
> tags=advanced,required_hardware=true \
> component/test_password_server.py \
> smoke/test_vpc_redundant.py \
> smoke/test_routers_iptables_default_policy.py \
> smoke/test_routers_network_ops.py \
> smoke/test_vpc_router_nics.py \
> smoke/test_router_dhcphosts.py \
> smoke/test_loadbalance.py \
> smoke/test_internal_lb.py \
> smoke/test_ssvm.py \
> smoke/test_vpc_vpn.py \
> smoke/test_privategw_acl.py \
> smoke/test_network.py
> ```
> 
> **Result test suite 1**
> ```
> Check the password file in the Router VM ... === TestName:
> test_isolate_network_password_server | Status : SUCCESS ===
> ok
> Create a redundant VPC with two networks with two VMs in each network ... ===
> TestName: test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Status :
> SUCCESS ===
> ok
> Create a redundant VPC with two networks with two VMs in each network and 
> check
> default routes ... === TestName: test_02_redundant_VPC_default_routes | 
> Status :
> SUCCESS ===
> ok
> Create a redundant VPC with two networks with two VMs in each network ... ===
> TestName: test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers 
> |
> Status : SUCCESS ===
> ok
> Test iptables default INPUT/FORWARD policy on RouterVM ... === TestName:
> test_02_routervm_iptables_policies | Status : SUCCESS ===
> ok
> Test iptables default INPUT/FORWARD policies on VPC router ... === TestName:
> test_01_single_VPC_iptables_policies | Status : SUCCESS ===
> ok
> Test redundant router internals ... === TestName:
> test_01_isolate_network_FW_PF_default_routes_egress_true | Status : SUCCESS 
> ===
> ok
> Test redundant router internals ... === TestName:
> test_02_isolate_network_FW_PF_default_routes_egress_false | Status : SUCCESS 
> ===
> ok
> Test redundant router internals ... === TestName:
> test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true | Status : SUCCESS 
> ===
> ok
> Test redundant router internals ... === TestName:
> test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false | Status : SUCCESS 
> ===
> ok
> Test redundant router internals ... === TestName:
> test_03_RVR_Network_check_router_state | Status : SUCCESS ===
> ok
> Create a VPC with two networks with one VM in each network and test nics after
> destroy ... === TestName: test_01_VPC_nics_after_destroy | Status : SUCCESS 
> ===
> ok
> Create a VPC with two networks with one VM in each network and test default
> routes ... === TestName: test_02_VPC_default_routes | Status : SUCCESS ===
> ok
> Check that the /etc/dhcphosts.txt doesn't contain duplicate IPs ... ===
> TestName: test_router_dhcphosts | Status : SUCCESS ===
> ok
> Test to create Load balancing rule with source NAT ... === TestName:
> test_01_create_lb_rule_src_nat | Status : SUCCESS ===
> ok
> Test to create Load balancing rule with non source NAT ... === TestName:
> test_02_create_lb_rule_non_nat | Status : SUCCESS ===
> ok
> Test for assign & removing load balancing rule ... === TestName:
> test_assign_and_removal_lb | Status : SUCCESS ===
> ok
> Test to verify access to loadbalancer haproxy admin stats page ... === 
> TestName:
> test02_internallb_haproxy_stats_on_all_interfaces | Status : SUCCESS ===
> ok
> Test create, assign, remove of an Internal LB with roundrobin http traffic to 
> 3
> vm's ... === TestName: test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80 |
> Status : SUCCESS ===
> ok
> Test SSVM Internals ... === TestName: test_03_ssvm_internals | Status : 
> SUCCESS
> ===
> ok
> Test CPVM Internals ... === TestName: test_04_cpvm_internals | Status : 
> SUCCESS
> ===
> ok
> Test stop SSVM ... === TestName: test_05_stop_ssvm | Status : SUCCESS ===
> ok
> Test stop CPVM ... === TestName: test_06_stop_cpvm | Status : SUCCESS ===
> ok
> Test reboot SSVM ... === TestName: test_07_reboot_ssvm | Status : SUCCESS ===
> ok
> Test reboot CPVM ... === TestName: test_08_reboot_cpvm | Status : SUCCESS ===
> ok
> Test destroy SSVM ... === TestName: test_09_destroy_ssvm | Status : SUCCESS 
> ===
> ok
> Test destroy CPVM ... === TestName: test_10_destroy_cpvm | Status : SUCCESS 
> ===
> ok
> Test Remote Access VPN in VPC ... === TestName: test_vpc_remote_access_vpn |
> Status : SUCCESS ===
> ok
> Test VPN in VPC ... === TestName: test_vpc_site2site_vpn | Status : SUCCESS 
> ===
> ok
> test_01_vpc_privategw_ac

Re: [VOTE] Apache CloudStack 4.7.0

2015-12-16 Thread Wido den Hollander

Vote: +1

See more below

On 16-12-15 08:34, Boris Schrijver wrote:
> Hi all,
> 
> Hereby my vote for the ACS 4.7.0 RC 1
> 
> Details:
> 
> Vote: +1
> 
> Besides the integration tests (which all ran fine) I've also tested the
> following:
> 
>  - S3 Integration (Secondary Storage) with NFS Staging store
>  - Ceph RBD storage (Primary Storage)

There is a known issue with 4.7.0:
https://issues.apache.org/jira/browse/CLOUDSTACK-8302

This issue however also exists in ALL previous versions and there is a
outstanding PR for this: https://github.com/apache/cloudstack/pull/1230

Since this issue has been there for a long time I don't consider it as a
blocker.

Wido

>  - Basic networking with security groups 
> 
> -- 
> 
> Met vriendelijke groet / Kind regards,
> 
> Boris Schrijver
> 
> PCextreme B.V.
> 
> http://www.pcextreme.nl/contact
> Tel direct: +31 (0) 118 700 215
> 
>> On December 16, 2015 at 12:34 AM Remi Bergsma 
>> wrote:
>>
>>
>> +1 (binding)
>>
>> This vote is based on testing on a real cloud.
>>
>> At Schuberg Philis we built a new cloud based on ACS 4.7.0RC1 (upgraded from
>> 4.6). It runs XenServer 6.5 clusters, a CentOS 7 management cluster, Galera 
>> DB
>> (also on CentOS 7), HA proxies (CentOS 7), NFS storage and Nicira/NSX for
>> networking/SDN. Capacity to start with is about 12TB ram and 500+ cores.
>> Secondary storage is an S3 compatible solution (Cloudian) with NFS staging
>> store. Configured LDAP for authentication.
>>
>> Before a go-live we always do thorough testing and try to break the setup
>> emulating crashes and problems.
>>
>> We successful executed these CloudStack related tests:
>>
>>   *   crashed a hypervisor which was poolmaster and saw recovery in about 5
>> min (tested with/without returning of the hypervisor)
>>   *   crashed a hypervisor which was NOT poolmaster and saw recovery in about
>> 5 min (tested with/without returning of the hypervisor)
>>   *   crashed overbooked hypervisor in a cluster with too many VMs to run on
>> the remaining hypervisors. Saw it recovered fully when crashed hypervisor
>> returned. (this you don’t want to happen, but at least the recovery was
>> automatic)
>>   *   crashed one of the app servers; the other one continued and took over.
>> No user impact.
>>   *   crashed the main Galera DB node, the two remaining nodes survived and
>> kept working. No CloudStack impact.
>>   *   did performance tests and walked into the default 200mbps limit on
>> tiers. When we removed it (aka configured it properly) we could use full
>> 10gbps.
>>   *   crashed the NFS staging store, could not deploy VM from template that
>> was not already on primary storage. Recovered automatically when NFS returned
>> and VM was started.
>>   *   many functional tests, also covered In the integration tests (spin many
>> VMs, migrate, make port forwardings etc).
>>   *   executed patch round (live migrating vms around), rebooting all
>> hypervisors without user impact.
>>
>> Conclusion:
>> It’s pretty solid, even with one management server and a degraded database we
>> could still continue and operate existing VMs and start new ones. When the
>> nodes returned recovery was automatic.
>> We feel confident running production with Apache CloudStack 4.7 and will 
>> start
>> doing so later today!
>>
>> Regards,
>> Remi
>>
>> PS:
>> The integration tests we run in the dev/test environments were also 
>> successful
>> (the same I executed on the PRs that were merged).
>>
>>
>>
>> From: Remi Bergsma
>> mailto:rberg...@schubergphilis.com>>
>> Date: Sunday 13 December 2015 21:27
>> To: "dev@cloudstack.apache.org"
>> mailto:dev@cloudstack.apache.org>>
>> Subject: [VOTE] Apache CloudStack 4.7.0
>>
>> Hi all,
>>
>> Since our 4.6.0 release (on Nov 13th, exactly 1 month ago), we have merged
>> 100+ pull requests [1] with lots of bug fixes, refactoring and of course new
>> features. Time for a new release!
>>
>>
>> I've created a 4.7.0 release candidate, with the following artifacts up for a
>> vote:
>>
>> Git Branch and Commit SH:
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=4.7.0-RC20151213T2109
>>
>> Commit: 2f26a859a971a9852ed9f6f34fe35e52fe6028a9
>>
>> Source release (checksums and signatures are available at the same location):
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.7.0/
>>
>> PGP release keys (signed using A47DDC4F):
>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>
>> Vote will be open for at least 72 hours.
>>
>> For sanity in tallying the vote, can PMC members please be sure to indicate
>> "(binding)" with their vote?
>>
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>>
>> [1] git log --pretty=oneline --abbrev-commit 
>> origin/4.6..4.7.0-RC20151213T2109
>> | grep "Merge pull request"
>>

[GitHub] cloudstack pull request: CLOUDSTACK-9181 Prevent syntax error in c...

2015-12-16 Thread remibergsma

Github user remibergsma commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1249#discussion_r47776850
  
--- Diff: systemvm/patches/debian/config/opt/cloud/bin/checkrouter.sh ---
@@ -17,21 +17,20 @@
 # under the License.
 
 STATUS=UNKNOWN
-INTERFACE=eth1
 ROUTER_TYPE=$(cat /etc/cloudstack/cmdline.json | grep type | awk '{print 
$2;}' | sed -e 's/[,\"]//g')
-if [ $ROUTER_TYPE = "router" ]
+if [ "$ROUTER_TYPE" = "router" ]
 then
ROUTER_STATE=$(ip addr | grep eth0 | grep inet | wc -l | xargs bash -c  
'if [ $0 == 2 ]; then echo "MASTER"; else echo "BACKUP"; fi')
STATUS=$ROUTER_STATE
 else
-   ROUTER_STATE=$(ip addr | grep $INTERFACE | grep state | awk '{print 
$9;}')
-   if [ $ROUTER_STATE = "UP" ]
+   ROUTER_STATE=$(ip addr | grep eth1 | grep state | awk '{print $9;}')
--- End diff --

Split the commits and added a note.


---
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: CS 4.7.0 RC1: bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory

2015-12-16 Thread Milamber




On 16/12/2015 11:02, Remi Bergsma wrote:

Hi Milamber,

Nice find! Yes, the 4.6 systemvm template is fine. The 4.7 systemvm.iso 
contains all changed files that we need.

I see getRouterAlerts.sh in 4.6 but not in 4.7/master. Since I upgraded it 
still works for me somehow. Will need to investigate why that is.

It looks like regression from 6477bd8ff7f982e10d0d20a97857262897dc05ed, PR 1084.


Reference : CLOUDSTACK-9067




Did you create an issue for it?



Done : https://issues.apache.org/jira/browse/CLOUDSTACK-9183




  It’s not a big issue I’d say.


I suppose, that could be fix in 4.7.1.



Regards,
Remi





On 16/12/15 09:15, "Milamber"  wrote:


Hello,

On my 4.7.0 RC1 test environment, I've this warning message:
2015-12-15 23:57:35,165 WARN
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:ctx-f1556e81) (logid:db80c3d4) Unable to get
alerts from router r-11-VM bash: /opt/cloud/bin/getRouterAlerts.sh: No
such file or directory

I don't find this bash script anywhere (on management node, host node
and inside the VR)

I find theses references to this script inside:

 public static final String ROUTER_ALERTS = "getRouterAlerts.sh";
./core/src/com/cloud/agent/resource/virtualnetwork/VRScripts.java

 ExecutionResult result = _vrDeployer.executeInVR(routerIp,
VRScripts.ROUTER_ALERTS, args);
./core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java


I use the system vm template from jenkins [1] dated from 02-Dec-2015.

I my understand, the CS 4.7.0 can use the systemvm 4.6?

This is a bug or just I use the wrong systemvm?


[1]
http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-4.6.0-kvm.qcow2.bz2

Re: CS 4.7.0 RC1: bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory

2015-12-16 Thread Milamber




On 16/12/2015 12:54, Wilder Rodrigues wrote:

Hi there…

What kind of hypervisor do you have?


KVM on Ubuntu 14.04.3

Jira: https://issues.apache.org/jira/browse/CLOUDSTACK-9183



Cheers,
Wilder



On 16 Dec 2015, at 09:15, Milamber  wrote:

Hello,

On my 4.7.0 RC1 test environment, I've this warning message:
2015-12-15 23:57:35,165 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(RouterStatusMonitor-1:ctx-f1556e81) (logid:db80c3d4) Unable to get alerts from 
router r-11-VM bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or 
directory

I don't find this bash script anywhere (on management node, host node and 
inside the VR)

I find theses references to this script inside:

public static final String ROUTER_ALERTS = "getRouterAlerts.sh";
./core/src/com/cloud/agent/resource/virtualnetwork/VRScripts.java

ExecutionResult result = _vrDeployer.executeInVR(routerIp, 
VRScripts.ROUTER_ALERTS, args);
./core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java


I use the system vm template from jenkins [1] dated from 02-Dec-2015.

I my understand, the CS 4.7.0 can use the systemvm 4.6?

This is a bug or just I use the wrong systemvm?


[1] 
http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-4.6.0-kvm.qcow2.bz2

Re: [VOTE] Apache CloudStack 4.7.0

2015-12-16 Thread Dag Sonstebo

+0

Tested:
- vSphere 5.5 / NFS backed zone.
- Overall performance and functionality OK.

Specifically tested selectable VMware SCSI controller with W2012R2 guests:
- Controller model can only be specified on template *upload* from GUI - not 
deployment, which has to be one from API on command line. It would be nice to 
have this as an option on GUI deploy and on template create.
- Changing the root disk controller for existing VMs doesn’t get applied in 
vSphere.
- Overriding adapter model on API deploy from template works (i.e. is applied 
in vSphere and in cloud.user_vm_details) in certain cases:
- LSI logic SAS (lsisas1068) override works.
- LSI logic parallel (lsilogic) override works.
- pvscsi (pvscsi) override works.
- ide (ide) override does not work, falls back to LSI Logic SAS.
- scsi (scsi) does not work, seems to fall back to LSI Logic Parallel.
- buslogic (buslogic) does not work (invalid controller for 64-bit guest OSes).
- Above comments do not take into account guest OS behaviour, which is mixed 
depending on what tools / drivers are installed in the W2012R2 guest. Without 
further surgery only LSI Logic SAS has proven consistent.

Regards,
Dag Sonstebo
ShapeBlue






[ShapeBlue]
Dag Sonstebo
ShapeBlue

d:  +44 203 603 0540 | s: 

e:  dag.sonst...@shapeblue.com | t: 
 |  w:  
www.shapeblue.com

a:  53 Chandos Place, Covent Garden London WC2N 4HS UK


[cid:image207fb6.png@f6950409.46a58bb6]


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




On 13/12/2015, 20:27, "Remi Bergsma"  wrote:

>Hi all,
>
>Since our 4.6.0 release (on Nov 13th, exactly 1 month ago), we have merged 
>100+ pull requests [1] with lots of bug fixes, refactoring and of course new 
>features. Time for a new release!
>
>
>I've created a 4.7.0 release candidate, with the following artifacts up for a 
>vote:
>
>Git Branch and Commit SH:
>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=4.7.0-RC20151213T2109
>
>Commit: 2f26a859a971a9852ed9f6f34fe35e52fe6028a9
>
>Source release (checksums and signatures are available at the same location):
>https://dist.apache.org/repos/dist/dev/cloudstack/4.7.0/
>
>PGP release keys (signed using A47DDC4F):
>https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
>Vote will be open for at least 72 hours.
>
>For sanity in tallying the vote, can PMC members please be sure to indicate 
>"(binding)" with their vote?
>
>[ ] +1 approve
>[ ] +0 no opinion
>[ ] -1 disapprove (and reason why)
>
>
>[1] git log --pretty=oneline --abbrev-commit origin/4.6..4.7.0-RC20151213T2109 
>| grep "Merge pull request"
>
Dag Sonstebo


dag.sonst...@shapeblue.com | www.shapeblue.com
Dag Sonstebo


dag.sonst...@shapeblue.com | www.shapeblue.com
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

RE: [VOTE] Apache CloudStack 4.7.0

2015-12-16 Thread Glenn Wagner

Hi,

+0

Test Lab
- CentOS 6.7 Management Server / NFS Primary and Secondary Storage / MYSQL 5.1
- Xenserver 6.2 SP1

Advanced Zone setup

UI enhancements tested metics view
VM Testing - Deploy , start , stop , restart , destroy)
Volume tests ( Create , attach/detach , destroy, download
Template and ISO (register , download)






Regards
Glenn Wagner
ShapeBlue South Africa


[ShapeBlue]
Glenn Wagner
Senior Consultant   ,   ShapeBlue


d:  +27 21 527 0091 | s: |  
m:  +27 73 917 4111

e:  glenn.wag...@shapeblue.com | t: 
 |  w:  
www.shapeblue.com

a:  2nd Floor, Oudehuis Centre, 122 Main Rd, Somerset West Cape Town 7130 
South Africa


[cid:image261fa4.png@cf8ffd01.4684af9b]


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




-Original Message-
From: Remi Bergsma [mailto:rberg...@schubergphilis.com]
Sent: Sunday, 13 December 2015 10:28 PM
To: dev@cloudstack.apache.org
Subject: [VOTE] Apache CloudStack 4.7.0

Hi all,

Since our 4.6.0 release (on Nov 13th, exactly 1 month ago), we have merged 100+ 
pull requests [1] with lots of bug fixes, refactoring and of course new 
features. Time for a new release!


I've created a 4.7.0 release candidate, with the following artifacts up for a 
vote:

Git Branch and Commit SH:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=4.7.0-RC20151213T2109

Commit: 2f26a859a971a9852ed9f6f34fe35e52fe6028a9

Source release (checksums and signatures are available at the same location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.7.0/

PGP release keys (signed using A47DDC4F):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

Vote will be open for at least 72 hours.

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)


[1] git log --pretty=oneline --abbrev-commit origin/4.6..4.7.0-RC20151213T2109 
| grep "Merge pull request"

Glenn Wagner
Senior Consultant

glenn.wag...@shapeblue.com | www.shapeblue.com
Glenn Wagner
Senior Consultant

glenn.wag...@shapeblue.com | www.shapeblue.com
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

[GitHub] cloudstack pull request: [4.5] CLOUDSTACK-4787 - vmware diskcontro...

2015-12-16 Thread bhaisaab

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/1131#issuecomment-165228795
  
Merging based on #1132


---
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: [4.5] CLOUDSTACK-4787 - vmware diskcontro...

2015-12-16 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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: [VOTE] Apache CloudStack 4.6.2

2015-12-16 Thread Milamber


Hello,

My vote +1 (binding)


My tests (all tests are passed on a CloudStack (1mgr+2nodes+1nfs) inside 
CloudStack topology) :


1/ Fresh install of 4.6.2 (adv net) on Ubuntu 14.04.3 + KVM + NFS : OK
Some standard tests (create vm, migration, HA, create network, create 
user, create ssh key, destroy vm, register template, create snapshot, 
restore snapshot, create template, ip association, ip release, static 
nat, firewall rule)
Some tests with cloudstack ansible module (create network, register 
templates, create vm, ip, firewall rule)


2/ Fresh install of 4.5.2 (adv net) on Ubuntu 14.04.3 + KVM + NFS and 
after migration to CS 4.6.2 : OK
Some standard tests (create vm, migration, HA (crash host), create 
network, create user, create ssh key, destroy vm, register template, 
create snapshot, restore snapshot, create template, resize volume)
Some tests with cloudstack ansible module (create network, register 
templates, create vm, ip, firewall rule)


3/ Tests all localizations of Web UI (with a complete installation of 
CS) : local strings works wells except Spanish and Arabic (expected, 
some strings needs to be fixes on Transifex)


Thanks to RM team.

Milamber

On 13/12/2015 18:36, Remi Bergsma wrote:

Hi all,

In the past two weeks (since 4.6.1), 23 pull [1] requests have been merged to 
4.6 branch and then to master/4.7.0. Therefore it makes sense to wrap-up the 
4.6 release cycle with a final release and bring all the improvements to our 
users. Vote e-mail below. Later today we will send another RC for 4.7.0.


I've created a 4.6.2 release candidate, with the following artifacts up for a 
vote:

Git Branch and Commit SH:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=4.6.2-RC20151213T1914

Commit: 10e0130dd6e0c06deae4f5ccfd43d5bcecea57b6

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.6.2/

PGP release keys (signed using A47DDC4F):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

Vote will be open for at least 72 hours.

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)


[1] git log --pretty=oneline --abbrev-commit 4.6.1..4.6.2-RC20151213T1914 | grep 
"Merge pull request"

Re: [VOTE] Apache CloudStack 4.7.0

2015-12-16 Thread Milamber


Hello,

My vote +1 (binding)


My tests (all tests are passed on a CloudStack (1mgr+2nodes+1nfs) inside 
CloudStack topology) :


1/ Fresh install of 4.7.0 (adv net) on Ubuntu 14.04.3 + KVM + NFS : OK
Some standard tests (create vm, migration, HA, create network, create 
user, create ssh key, destroy vm, register template, create snapshot, 
restore snapshot, create template, ip association, ip release, static 
nat, firewall rule)
Some tests with cloudstack ansible module (create network, register 
templates, create vm, ip, firewall rule)


2/ Fresh install of 4.5.2 (adv net) on Ubuntu 14.04.3 + KVM + NFS, and 
after migration to 4.7.0 : OK
Some standard tests (create vm, migration, HA (crash host), create 
network, create user, create ssh key, destroy vm, register template, 
create snapshot, restore snapshot, create template, resize volume)
Some tests with cloudstack ansible module (create network, register 
templates, create vm, ip, firewall rule)
Special tests with Redondant Virtual Router (RVR) VR master destroy 
(only 8 icmp packets lost after the 'virtual crash')


3/ Tests all localizations of Web UI (with a complete installation of 
CS) : local strings works wells except Spanish and Arabic (expected, 
some strings needs to be fixes on Transifex)



Known minor issue: https://issues.apache.org/jira/browse/CLOUDSTACK-9183

Thanks to RM team. Double sprints with 4.6.2/4.7.0!

Milamber

On 13/12/2015 20:27, Remi Bergsma wrote:

Hi all,

Since our 4.6.0 release (on Nov 13th, exactly 1 month ago), we have merged 100+ 
pull requests [1] with lots of bug fixes, refactoring and of course new 
features. Time for a new release!


I've created a 4.7.0 release candidate, with the following artifacts up for a 
vote:

Git Branch and Commit SH:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=4.7.0-RC20151213T2109

Commit: 2f26a859a971a9852ed9f6f34fe35e52fe6028a9

Source release (checksums and signatures are available at the same location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.7.0/

PGP release keys (signed using A47DDC4F):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

Vote will be open for at least 72 hours.

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)


[1] git log --pretty=oneline --abbrev-commit origin/4.6..4.7.0-RC20151213T2109 | grep 
"Merge pull request"

[GitHub] cloudstack pull request: CLOUDSTACK-8847: ListServiceOfferings is ...

2015-12-16 Thread agneya2001

Github user agneya2001 commented on the pull request:

https://github.com/apache/cloudstack/pull/823#issuecomment-165325933
  
@nitin-maharana @koushik-das @kishankavala @bhaisaab @jburwell 
@DaanHoogland @remibergsma Can we have a discussion on: Why do we need any kind 
of restriction on tags while looking for compatible service offering ? Is there 
any downside ? My opinion is we should just allow change of service offering 
irrespective of tags.


---
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-9184: [VMware] vmware.ports.pe...

2015-12-16 Thread sureshanaparti

GitHub user sureshanaparti opened a pull request:

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

CLOUDSTACK-9184: [VMware] vmware.ports.per.dvportgroup global setting is 
not useful from vCenter 5.0 onwards

Modify the default value of this setting, which is currently 256, by 
decreasing it to 8 because even a dvportgroup with autoexpand feature enabled 
there exists an initial number of ports as starting point, which can be again 
configured through this configuration setting. But keeping this value 256 
doesn't make sense when auto expand feature is available. Keeping the starting 
number of dvports per dvportgroup to reasonably minimum would ensure optimal 
distribution across dvportgroups in dvSwitch.

The vSphere Auto Expand feature (introduced in vSphere 5.0) will take care 
of dynamically increasing/decreasing the dvPorts when running out of 
distributed ports . But in case of vSphere 4.1/4.0 (If used), as this feature 
is not there, the new default value (=> 8) have an impact in the existing 
deployments. Action item for vSphere 4.1/4.0: Admin should modify the global 
configuration setting "vmware.ports.per.dvportgroup" from 8 to any number based 
on their environment because the proposal default value of 8 would be very less 
without auto expand feature in general. The current default value of 256 may 
not need immediate modification after deployment, but 8 would be very less 
which means admin need to update immediately after upgrade.

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

$ git pull https://github.com/sureshanaparti/cloudstack CLOUDSTACK-9184

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

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


commit 4e0cd09226ed1819f51ad018ec0020358d5c3e85
Author: Suresh Kumar Anaparti 
Date:   2015-12-17T04:34:53Z

CLOUDSTACK-9184: [VMware] vmware.ports.per.dvportgroup global setting is 
not useful from vCenter 5.0 onwards

Fix: Modify the default value of this setting, which is currently 256, by 
decreasing it to 8 because even a dvportgroup with autoexpand feature enabled 
there exists an initial number of ports as starting point, which can be again 
configured through this configuration setting.




---
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-9175: [VMware DRS] Adding new ...

2015-12-16 Thread sureshanaparti

Github user sureshanaparti commented on the pull request:

https://github.com/apache/cloudstack/pull/1248#issuecomment-165339578
  
@resmo, Out of all the running hosts present in the cluster, the port 
groups are fetched from the host which was first added to the cloudstack, 
assuming that it has all the cloudstack created port groups. So existent may 
not be the right word. Any other?


---
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-9174: A deleted account result...

2015-12-16 Thread agneya2001

GitHub user agneya2001 opened a pull request:

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

CLOUDSTACK-9174: A deleted account results in NPE

When an account is deleted from cloudstack for which quota is still
being calculated and if the quota reaches minimum threshold then
quota service will try to alert the user. This results in NPE and is
fixed by excluding such accounts from alerting and other quota related
mechanisms.

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

$ git pull https://github.com/shapeblue/cloudstack master-9174

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

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


commit c07720b73cb16cb55dc83047373e22885d47dbc5
Author: Abhinandan Prateek 
Date:   2015-12-17T05:02:33Z

CLOUDSTACK-9174: A deleted account results in NPE

When an account is deleted from cloudstack for which quota is still
being calculated and if the quota reaches minimum threshold then
quota service will try to alert the user. This results in NPE and is
fixed by excluding such accounts from alerting and other quota related
mechanisms.




---
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-8961: Changes related to the U...

2015-12-16 Thread kansal

Github user kansal closed the pull request at:

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


---
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-8961: Changes related to the U...

2015-12-16 Thread kansal

Github user kansal commented on the pull request:

https://github.com/apache/cloudstack/pull/941#issuecomment-165340109
  
Closing this PR, will create a new one against 4.6


---
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-8961: Changes related to the U...

2015-12-16 Thread kansal

GitHub user kansal opened a pull request:

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

Cloudstack-8961: Changes related to the UI of VPN Users management.

The current VPN uses are added in the VPN tab inside the public IP after 
the VPN is enabled. For each network(for which VPN is supported and enabled), 
the VPN users are shared. As the Cloudstack doc says â The account owner can 
create and manage users for their VPN. CloudStack does not use its account 
database for this purpose but uses a separate table. The VPN user database is 
shared across all the VPNs created by the account owner. All VPN users get 
access to all VPNs created by the account owner.â

The current implementation of going inside each network and adding VPN 
users give a first feel as if the users are network based. To fix this, Shifted 
the VPN users to networks tab views.


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

$ git pull https://github.com/kansal/cloudstack CLOUDSTACK-8961

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

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


commit 8cecc255b4d3d12ac004743d2f8a0f1b6f148527
Author: Kshitij Kansal 
Date:   2015-10-13T07:26:24Z

CLOUDSTACK-8961: Changes related to the UI of VPN Users management.

commit 01690e3ac60a36c772bb965ff1c5135fc66d67e0
Author: Kshitij Kansal 
Date:   2015-12-15T09:37:24Z

CLOUDSTACK-8961: Added an option for admins to add VPN users in the domains 
they have access to




---
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-9185: [VMware DRS] VM sync fai...

2015-12-16 Thread sureshanaparti

GitHub user sureshanaparti opened a pull request:

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

CLOUDSTACK-9185: [VMware DRS] VM sync failed with exception due to 
out-of-band changes

Summary: The target 
"ClusteredVirtualMachineManagerImpl.HandlePowerStateReport" invoked during the 
VM power state sync is not found as HandlePowerStateReport was not implemented 
in ClusteredVirtualMachineManagerImpl and was private in 
VirtualMachineManagerImpl, which was resulting in InvocationTargetException. 
Changed HandlePowerStateReport() in VirtualMachineManagerImpl to protected.

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

$ git pull https://github.com/sureshanaparti/cloudstack CLOUDSTACK-9185

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

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


commit 2d5f6a7911585a8075996e106f97b7f3b89067f8
Author: Suresh Kumar Anaparti 
Date:   2015-12-17T05:29:31Z

CLOUDSTACK-9185: [VMware DRS] VM sync failed with exception due to 
out-of-band changes

Summary: The target 
"ClusteredVirtualMachineManagerImpl.HandlePowerStateReport" invoked during the 
VM power state sync is not found as HandlePowerStateReport was not implemented 
in ClusteredVirtualMachineManagerImpl and was private in 
VirtualMachineManagerImpl, which was resulting in InvocationTargetException. 
Changed HandlePowerStateReport() in VirtualMachineManagerImpl to protected.




---
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-8961: Changes related to the U...

2015-12-16 Thread kansal

Github user kansal commented on the pull request:

https://github.com/apache/cloudstack/pull/1255#issuecomment-165342311
  
cc @milamberspace @karuturi Have reopened this PR against the current 
master. This is in continuation with #941. 
![screen shot 2015-12-17 at 11 02 13 
am](https://cloud.githubusercontent.com/assets/4276209/11862175/e1800faa-a4ad-11e5-90e2-34a39699eb82.png)
![screen shot 2015-12-17 at 11 02 49 
am](https://cloud.githubusercontent.com/assets/4276209/11862177/eb01d46e-a4ad-11e5-9340-7f39652b0374.png)
![screen shot 2015-12-17 at 11 03 07 
am](https://cloud.githubusercontent.com/assets/4276209/11862178/f058f370-a4ad-11e5-88a0-3e25c925f1de.png)
![screen shot 2015-12-17 at 11 03 27 
am](https://cloud.githubusercontent.com/assets/4276209/11862180/f511e836-a4ad-11e5-9732-e292ca831e9f.png)



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

50 matches

Mail list logo