Re: CLOUDSTACK-7982 - KVM live migration

[Rajani Karuturi]

You are now on the Jira contributors list. You should be able to
assign issues.

Thanks,
~ Rajani
http://cloudplatform.accelerite.com/

On August 12, 2016 at 5:57 PM, ma...@exoscale.ch
(ma...@exoscale.ch) wrote:
Need some Jira love... Can someone give me the rights to assign
myself to this JIRA issue, or to assign myself directly. Thanks

https://issues.apache.org/jira/browse/CLOUDSTACK-7982

There are new configuration items and some explainations to be
documented. I thought to write it in the documentation project.
Is it required to write something in the wiki too?

Marc-Aurèle

--
Exoscale
Av de Provence 4
1007 Lausanne
+41 78 622 42 31
www.exoscale.ch ( http://www.exoscale.ch )

[GitHub] cloudstack pull request #1628: updated contributing.md

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1641: CLOUDSTACK-9459: the try's catch blick was sh...

[abhinandanprateek]

GitHub user abhinandanprateek opened a pull request:

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

CLOUDSTACK-9459: the try's catch blick was shortening the preparedstatement 
life

the try's catch blick was shortening the preparedstatement's life resulting 
in bad resultset when used outside of try catch.

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

$ git pull https://github.com/shapeblue/cloudstack upgrade_fix

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

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


commit a2fcc65d9050b9cd6915e36e5274379aa3298957
Author: Abhinandan Prateek 
Date:   2016-08-16T08:34:43Z

CLOUDSTACK-9459: the try's catch block was shortening the preparedstatement 
life
resulting in bad resultset when used outside of try catch.




---
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 issue #1641: CLOUDSTACK-9459: the try's catch block was shortenin...

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1641
  
LGTM, the only change is to move the catch block to the end so the 
ResultSet is not closed once the code comes out of the try-catch block.


---
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 issue #1638: CLOUDSTACK-9456: Use Spring 4 and Java 8

[pdion891]

Github user pdion891 commented on the issue:

https://github.com/apache/cloudstack/pull/1638
  
Shouldn't we consider doing a 5.0.0 release that would support Java 8 or we 
want to go  Java8 at 4.10.0 ?

Otherwise I can't review, but I should be able to help on testing.


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

cloudstack-usage no longer working / error saving account to cloud_usage db

[Stephan Seitz]

Hi!

We've recently noticed cloudstack-usage is no longer able to write
usage data into mysql. I assume this happened after updateing to
4.8.0.1 or 4.9 - we missed that error in our testsetup...

Here's the usage.log: http://pastebin.com/Zpvnw4xX

Finally it fails with following message:

ERROR [usage.dao.UsageDaoImpl] (Usage-Job-1:null) (logid:) error saving
account to cloud_usage db


I've checked the changes between 4.8 and 4.9

https://fossies.org/diffs/apache-cloudstack/4.8.0.1-src_vs_4.9.0-src/en
gine/schema/src/com/cloud/usage/dao/UsageDaoImpl.java-diff.html

cloud_usage.account now shows role_id, but that table looks good to me:

mysql> show create table account \G
*** 1. row ***
   Table: account
Create Table: CREATE TABLE `account` (
  `id` bigint(20) unsigned NOT NULL,
  `account_name` varchar(100) DEFAULT NULL COMMENT 'an account name set
by the creator of the account, defaults to username for single
accounts',
  `uuid` varchar(40) DEFAULT NULL,
  `type` int(1) unsigned NOT NULL,
  `role_id` bigint(20) unsigned DEFAULT NULL,
  `domain_id` bigint(20) unsigned DEFAULT NULL,
  `state` varchar(10) NOT NULL DEFAULT 'enabled',
  `removed` datetime DEFAULT NULL COMMENT 'date removed',
  `cleanup_needed` tinyint(1) NOT NULL DEFAULT '0',
  `network_domain` varchar(100) DEFAULT NULL COMMENT 'Network domain
name of the Vms of the account',
  `default_zone_id` bigint(20) unsigned DEFAULT NULL,
  `default` int(1) unsigned NOT NULL DEFAULT '0' COMMENT '1 if account
is default',
  PRIMARY KEY (`id`),
  UNIQUE KEY `uc_account__uuid` (`uuid`),
  KEY `i_account__removed` (`removed`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
1 row in set (0.00 sec)

Having a look at that data, I'm a bit confused since uuid,
network_domain and default_zone_id are NULL for every account.

As an example:

mysql> select * from account limit 1 \G
*** 1. row ***
 id: 1
   account_name: system
   uuid: NULL
   type: 1
role_id: NULL
  domain_id: 1
  state: enabled
removed: NULL
 cleanup_needed: 0
 network_domain: NULL
default_zone_id: NULL
default: 0
1 row in set (0.00 sec)


I've already looked at plain SQL statements logged by the mysqld, but
that's really messy and grepping for INSERT/UPDATE queries defined in
UsageDaoImpl didn't show anything. Finally grepping for 'statistics' in
the raw sql-log doesn't result a line. 

Could someone please shed some light how I could get the usage service
collecting and reporting data again?

Thanks in advance!

cheers,

- Stephan

Re: [PROPOSAL] Early LTS Initial Release

[Pierre-Luc Dion]

To me, if we would like to offer LTS, we need to fix following core issues:
-  how database version is handle, right now database structure is mixed
with upgrade*.sql files and some java code
-  better test upgrade path, I'm not sure we test them properly :-S


I have to admit I'm not fan of LTS release and would probably be -1, on
this for the following reasons:

Over the last year of so we start bumping old branch sub-release to back
port bugfixes, the idea is not bad, but we are now facing issues that
Upgrade paths are broken because older branch minor releases can be more
recent than latest main release as result as database consistency.  last
example:  4.8.1 will be release after 4.9.0

A problematic issue that we are experiencing is the database structure, we
currently have a scenario in our infra where a fresh installation of 4.7.2
does not have the same `configuration` table content as an older system
that have that path: 4.4.0 -> 4.4.4 -> 4.7.0 -> 4.7.2
I blame our database versioning method, and the fact that we are changing
upgrade_*.sql files between releases. The reality is that once  release
package are voted,
we should never change update*.sql files except for the next coming version
that as not been released yet. Rohit discussed about solution about this in
the past, we should review that.

Another issue we are seeing, that our personal experience at keep using an
old branch, is the complexity of submitting bug fixes that require 2 code
fixes if the main code diverge too much, back porting bug fixes or new
features is not trivial sometime because the code base change too much
between versions. This is not really inviting to submit bug fixes.

So now regression tests are event more complicated because a bug can be
fixed in  an older branch but not in master due to code refactor, or
missing PR or merge.

Also, keeping users in previous branch prevent them to use latest
hypervisors releases (XenServer 7.0) and latest Guest OSes (ex: Ubuntu
16.04).
After running CloudStack for few years now, I found that remaining on an
old branch/release is a medium term dead end, because you end up with
inability to upgrade or use latest hypervisors and new guest OSes, upgrade
path is much more complex and involve much more efforts than upgrading
often as Shubberg proposed in the past. We have the capability to upgrade
our software as oppose to similar projects, so we should leverage this.

Last thing, I found the propose versioning is too complicated, why adding
5th and 6th digit, shouldn't we start bumping up 4.x.x to 5.x.x instead?


I don't want to  block any initiative going that path, LTS, but I'm a bit
concerned in our current state and upgrade paths.


Regards,

Pierre-Luc


On Wed, Aug 3, 2016 at 2:33 AM, Rajani Karuturi  wrote:

> The idea of maintaing the release branch longer can be discussed.
> But, I am -1 for separate branches and separate release trains.
> Maintaing the upgrade paths would be a big overhead.
> We are not doing regular releases on the main release branches.
> Rohit did a great job for 4.5(though it was backporting and not
> forward merging at that time). Beyond that, we are not doing
> regular releases. If we do regular updates on the release
> branches, users who wish to take a release once in 6 months can
> do so even now. It will just be current+6 release (assuming we do
> regular minor releases every month)
> ~ Rajanihttp://cloudplatform.accelerite.com/
> On August 3, 2016 at 4:07 AM, John Burwell
> (john.burw...@shapeblue.com) wrote:Rajani,
> As I mentioned in my previous email, the original motivation for
> a completely separate branch was based on objections by some
> community members that the longer, more conservative LTS release
> cycle would place a drag on the velocity of regular
> releases. Additionally, users interested in LTS releases voiced
> their desire to have fewer releases a year. Therefore, where the
> regular release cycle is scheduled to make major releases every 2
> months and maintenance releases every month, the LTS cycle makes
> major releases every 6 months and maintenance releases less
> frequently (e.g. every 3 months). These longer cycles allow
> users with longer acceptance test/verification cycles to more
> easily keep up with upgrades. Completely separate branches and
> release cycles were proposed to serve both use cases (rapid,
> leading upgrades and more traditional maintenance cycles).
> I am open to collapsing LTS into the regular maintenance releases
> (e.g. 4.9 simply becomes supported for 20 months instead of 4
> months). Ultimately, I would like that decision to be based on
> user feedback since separate release branches/cycles have been
> previously discussed with no objections [1]. I have CC’ed users@
> to solicit thoughts from our users on which approach would be
> preferred.
> Thanks,-John
> [1]: http://markmail.org/thread/zh43rc6ahs4te46l (
> http://markmail.org/thread/zh43rc6ahs4te46l ) john.burw...@shapeblue.com
> ( john.burw..

[GitHub] cloudstack pull request #1593: CLOUDSTACK-9417: Usage module refactoring

[rafaelweingartner]

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

https://github.com/apache/cloudstack/pull/1593#discussion_r74957023
  
--- Diff: usage/src/com/cloud/usage/UsageSanityChecker.java ---
@@ -72,7 +72,9 @@ protected boolean checkItemCountByPstmt(CheckCase 
checkCase) throws SQLException
 try (PreparedStatement pstmt = 
conn.prepareStatement(checkCase.sqlTemplate)) {
 if(checkCase.checkId) {
 pstmt.setInt(1, lastId);
-pstmt.setInt(2, maxId);
+if (maxId > 0) {
+pstmt.setInt(2, maxId);
--- End diff --

@nvazquez thanks for the explanation. Now I understood it a little bit 
more. These SLQs that are built using if(s)/else(s) and use few methods are a 
bit hard to follow sometimes without debugging it in runtime.

This was my only doubt. So, LGTM here.



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

CCC Brasil

[Marco Sinhoreli]

All,

I am very sorry to have to say that we have had to postpone the upcoming CCC 
conference in Sao Paluo.

Over the past few months we have been working very hard with an events 
organiser to try and get the conference off the ground. Conferences are very 
expensive to stage here in Brasil so we were relying on a number of large 
sponsors. Unfortunately , we are unable to get enough sponsors for the proposed 
September dates due to multiple schedule conflicts.

I appreciate that this is very late notice. Up until this week we were hoping 
to have enough sponsorship to run the event but we were also conscious that 
this would have left only a little time for CFP and people to make travel 
arrangements. We have therefore decided to cancel the September conference. 
We’re working with local sponsors and our venue hosts to try and find some 
dates either later in 2016 or in 2017.

Best regards,


[cid:D163DEC9-811D-4BA2-9505-94F51109CA0B]

Marco Sinhoreli
Managing Consultant
marco.sinhor...@shapeblue.com
mobile: +55 21 98276 3636


Praia de Botafogo 501, bloco 1 - sala 101 – Botafogo
Rio de Janeiro, RJ - Brazil - CEP 22250-040
office: + 55 21 2586 6390 | fax: +55 21 2586 6002
http://www.shapeblue.com/ | twitter: @shapeblue

[GitHub] cloudstack pull request #1593: CLOUDSTACK-9417: Usage module refactoring

[nvazquez]

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

https://github.com/apache/cloudstack/pull/1593#discussion_r74966728
  
--- Diff: usage/src/com/cloud/usage/UsageSanityChecker.java ---
@@ -72,7 +72,9 @@ protected boolean checkItemCountByPstmt(CheckCase 
checkCase) throws SQLException
 try (PreparedStatement pstmt = 
conn.prepareStatement(checkCase.sqlTemplate)) {
 if(checkCase.checkId) {
 pstmt.setInt(1, lastId);
-pstmt.setInt(2, maxId);
+if (maxId > 0) {
+pstmt.setInt(2, maxId);
--- End diff --

Thanks @rafaelweingartner! 
Absolutely, now I notice there was also a similar 
[comment](https://github.com/apache/cloudstack/pull/1593/files#r67563826) by 
@jburwell about this, I should have explained it a little further on this PR 
description as it can be confusing.


---
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 issue #1615: CLOUDSTACK-9438: Fix for CLOUDSTACK-9252 - Make NFS ...

[serg38]

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1615
  
@jburwell Are there any outstanding issues with this PR? It is waiting for 
second LGTM.


---
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 issue #1605: CLOUDSTACK-9428: Fix for CLOUDSTACK-9211 - Improve p...

[serg38]

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1605
  
@rafaelweingartner @swill  Will you be able to review this one? 


---
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 issue #1602: CLOUDSTACK-9422: Granular 'vmware.create.full.clone'...

[serg38]

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1602
  
@jburwell Are there any outstanding issues with this PR? It is waiting for 
second LGTM.


---
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 issue #1593: CLOUDSTACK-9417: Usage module refactoring

[serg38]

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1593
  
@karuturi @jburwell There are 2 LGTM in this PR.  Packaging, Travis and 
Jenkins all passed. Can this be merged? 


---
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 issue #1560: CLOUDSTACK-9386: DS template copies don’t get dele...

[serg38]

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1560
  
 @rafaelweingartner @jburwell @rhtyd @koushik-das Can you review this PR?


---
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 issue #1542: CLOUDSTACK-9379: Support nested virtualization at VM...

[serg38]

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1542
  
@jburwell @rhtyd @koushik-das Can you review this PR?


---
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 issue #1542: CLOUDSTACK-9379: Support nested virtualization at VM...

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1542
  
@nvazquez @serg38 how about we remove vmware.nested.virtualization.perVM 
and instead if the user vm detail exists and is true, it overrides the global 
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 issue #1638: CLOUDSTACK-9456: Use Spring 4 and Java 8

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1638
  
@pdion891 we're neither breaking any backward compatibility wrt APIs, or 
schema, nor we've made any core change (mgmt server core, cmd-answer patterns, 
rpcs/serialization, or the plugin-system). So, I think there is no need to do a 
5.0.0 for this (yet).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [GitHub] cloudstack issue #1542: CLOUDSTACK-9379: Support nested virtualization at VM...

[Sergey Levitskiy]

@rhtyd The rationale to have vmware.nested.virtualization.perVM was that 
advanced vm_details and template details are user controlled. With 
https://issues.apache.org/jira/browse/CLOUDSTACK-9457 
‘Allow retrieval and modification of VM and template details via API and UI’ 
users will be able to change any advanced details in UI and API.
If admin wants to preserve that nested virtualization is controlled in 
centralized fashion they can do so by setting 
vmware.nested.virtualization.perVM to ‘false’. Idea was to allow organizations 
that currently have nested virtualization disabled to have it so after upgrade.

On 8/16/16, 10:21 AM, "rhtyd"  wrote:

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1542
  
@nvazquez @serg38 how about we remove 
vmware.nested.virtualization.perVM and instead if the user vm detail exists and 
is true, it overrides the global 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.
---

Re: Request for comments: Moving to Spring 4 and Java 8

[Rohit Yadav]

All,


We now have a PR where we're able to build, run and test CloudStack master with 
JDK 1.8 and Spring 4.3. Special thanks to Marc-Aurèle Brothier for fixing the 
unit test issues.


The only outstanding issue is getting the F5 plugin to build, which I could not 
figure out how to fix even with their latest jdk1.8 iControl library. I 
therefore request any F5 maintainers to have a look and advise changes 
necessary to get this plugin to work with ACS master with the PR: 
https://github.com/apache/cloudstack/pull/1638


Otherwise, we would have to disable it moving forward if we've no one to 
maintain it or no user(s) who may be using it.


Please provide your review, feedback and comments on the PR. Thanks.


Regards.


From: Rohit Yadav 
Sent: 12 August 2016 17:44:53
To: dev@cloudstack.apache.org
Subject: Request for comments: Moving to Spring 4 and Java 8

All,


It's about time to migrate master to Java 8 JDK and Spring 4. Please help 
review the following PRs:

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


There are three outstanding issues that I need help and feedback on:


1. F5 plugin fails to build due to issue likely in the axis dependency library, 
I've disabled it from the build now. Do we have a F5 developer/maintainer who 
can look at it.


2. Two unit tests failures due to Spring 4 migration:

com/cloud/vm/DeploymentPlanningManagerImplTest.java

com/globo/globodns/cloudstack/resource/GloboDnsResourceTest.java


Do we have anyone who can help fix the above tests? Deployment planner 
developers, or globo-dns plugin maintainers?


3. In general, the end-to-end testing of plugins. There may be plugins which 
are not maintained or used anymore, we need discuss how to deal with them 
moving forward. As a first step we may want to start disable them from the 
build, especially those failing builds.


Comments, feedback? Thanks.


Regards.

rohit.ya...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue




rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

[GitHub] cloudstack issue #1593: CLOUDSTACK-9417: Usage module refactoring

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1593
  
@serg38 I only see code review LGTMs.  We need at least one test LGTM 
before this PR. In this case, those tests must be run against real hardware and 
hypervisors.  Also, we need an LGTM from all reviewers that raised an issue.  I 
haven't had a chance tore-review as I am on leave this week.  (All PRs require 
at least one code review and at least test LGTM to be merged).


---
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 issue #1638: CLOUDSTACK-9456: Use Spring 4 and Java 8

[pdion891]

Github user pdion891 commented on the issue:

https://github.com/apache/cloudstack/pull/1638
  
Make sense,  thanks, I hope it will get thru then to add support for Ubuntu 
16.04 for the management server host and KVM.



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

[Nicolás Vázquez]

C
​an you please let us know dates for rescheduled event as soon as possible?

Thanks​

2016-08-16 12:32 GMT-03:00 Marco Sinhoreli :

> All,
>
>
>
> I am very sorry to have to say that we have had to postpone the upcoming
> CCC conference in Sao Paluo.
>
>
>
> Over the past few months we have been working very hard with an events
> organiser to try and get the conference off the ground. Conferences are
> very expensive to stage here in Brasil so we were relying on a number of
> large sponsors. Unfortunately , we are unable to get enough sponsors for
> the proposed September dates due to multiple schedule conflicts.
>
>
>
> I appreciate that this is very late notice. Up until this week we were
> hoping to have enough sponsorship to run the event but we were also
> conscious that this would have left only a little time for CFP and people
> to make travel arrangements. We have therefore decided to cancel the
> September conference. We’re working with local sponsors and our venue hosts
> to try and find some dates either later in 2016 or in 2017.
>
>
> Best regards,
>
>
>
> *Marco Sinhoreli*
>
> Managing Consultant
>
> marco.sinhor...@shapeblue.com
>
> mobile: +55 21 98276 3636
>
>
>
> Praia de Botafogo 501, bloco 1 - sala 101 – Botafogo
>
> Rio de Janeiro, RJ - Brazil - CEP 22250-040
>
> office: + 55 21 2586 6390 | fax: +55 21 2586 6002
>
> http://www.shapeblue.com/ | twitter: @shapeblue
>

[DISCUSS] Using Github's squash merge to close pull request?

[Rohit Yadav]

All,


I found that Github also allows to merge a PR with the changes squashed [1], 
our git-pr script uses a normal branch-merge pattern. Should we evaluate using 
the approach of squash-merging a PR [1] to reduce git-history clutter?


Github also (finally) allows to edit a PR and change base branch, so several 
old PRs can be edited to change base branch to 4.9 (wherever applicable)[2]. 
So, if you've a old PR that is still pending please consider editing the base 
branch to 4.7-4.9 wherever applicable.



[1] https://help.github.com/articles/about-pull-request-merge-squashing/

[2] https://github.com/blog/2224-change-the-base-branch-of-a-pull-request

Regards.

rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

[GitHub] cloudstack issue #1638: CLOUDSTACK-9456: Use Spring 4 and Java 8

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1638
  
@rhtyd @pdion891 I apologize for my delayed reply as I am on vacation ATM.  
We had previously agreed not to require Java8 until 5.0.0 which is scheduled 
for the end of 2016.  4.x should be able to run on Java7 and Java8.  
Furthermore, Spring4 does not require Java8 so I don't see why such a Java 
upgrade would conflated with a Spring upgrade.

@rhytd I think it makes sense to reduce scope of this PR to Soring only.  
In a separate PR, we can address running tests for 4.x on both Java7 and Java8 
which needs to be done for LTS as well.  Does that make sense?


---
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 issue #1638: CLOUDSTACK-9456: Use Spring 4 and Java 8

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1638
  
@jburwell Running tests against JRE 1.7, 1.8 is do-able. But I really want 
our master to use JDK 1.8. If we want to be able to run ACS mgmt server, agents 
etc against JRE 1.8 on both 4.9/lts and master branches why not use JDK 1.8 for 
at least master moving forward? Starting 4.10 why not make JRE 1.8 default for 
CloudStack mgmt server and agents?


---
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 #1642: System VMs on Managed Storage

[mike-tutkowski]

GitHub user mike-tutkowski opened a pull request:

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

System VMs on Managed Storage

This PR makes it easier to spin up system VMs on managed storage.

Managed storage is when you have a dedicated volume on a SAN for a 
particular virtual disk (making it easier to deliver QoS).

For example, with this PR, you'd likely have a single virtual disk for a 
system VM. On XenServer, that virtual disk resides by itself in a storage 
repository (no other virtual disks share this storage repository).

Same concept for vSphere. The virtual disk of the system VM would reside by 
itself in a datastore (no other virtual disks share this datastore).

It was possible in the past to spin up system VMs that used managed 
storage, but this PR facilitates the use case by making changes to the System 
Service Offering dialog (and by putting in some parameter checks in the 
management server).

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

$ git pull https://github.com/mike-tutkowski/cloudstack managed_system_vms

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

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


commit af8e76c8e993ac6298d643fbf1f588ab0e5265f9
Author: Mike Tutkowski 
Date:   2016-08-12T03:26:06Z

Updated the GUI to enable storage QoS for system VMs

commit 3b84b10f8e3b95e832a2ed2509f84552fe6f67a7
Author: Mike Tutkowski 
Date:   2016-08-12T04:53:52Z

Throw an exception if customized IOPS or hypervisor snapshot reserve are 
passed in for a system VM.




---
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 issue #1642: System VMs on Managed Storage

[mike-tutkowski]

Github user mike-tutkowski commented on the issue:

https://github.com/apache/cloudstack/pull/1642
  
Here is a screen capture on the changes to the System Service Offering 
dialog.

[](url)
https://cloud.githubusercontent.com/assets/3019295/17714367/ba238e5e-63bc-11e6-946c-ed6906739a58.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.
---

[GitHub] cloudstack issue #1593: CLOUDSTACK-9417: Usage module refactoring

[serg38]

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1593
  
@jburwell LGTM for the test part. This PR was extensively tested on
Environment: RHEL 6 management servers, Vmware ESX5.5 and 6.0 with advanced 
networking 


---
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 issue #1638: CLOUDSTACK-9456: Use Spring 4 and Java 8

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1638
  
@rhtyd there is a difference between supporting Java8 and using it as the 
default version.  By changing the POMs, Maven will require that Java8 in order 
to use CloudStack dependencies.  Furthermore, making Java8 ripples into 
supported Tomcat versions and Linux distributions.  Therefore, we agreed 
sometime ago that 4.x would support Java8, and 5.0.0 would require/default to 
it. Personally, I would like to adopt Java8 as soon as possible, but we have to 
recognize that many of our users can move so quickly.  I would also like to do 
it once we have Jetty embedded so that the upgrade is much simpler for users of 
Linux distributions because they will no longer be concerned with version 
matching Tomcat.


---
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 issue #1593: CLOUDSTACK-9417: Usage module refactoring

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1593
  
@serg38 we require Marvin test results and, as well as, the results of any 
manual tests to be posted into the PR.  This information is a pre-requisite for 
merging PRs.  Please see other closed PRs for examples of test result reporting.


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

Upgrade from 4.8.0.1 to 4.9 issue

[Marty Godsey]

I upgraded a very clean environment of 4.8.0.1 to 4.9 and I am receiving this 
error when trying to enable the dynamic.apichecker.enabled setting:

2016-08-17 00:20:03,148 DEBUG [c.c.a.ApiServlet] 
(catalina-exec-25:ctx-01fb5369) (logid:3a6b506e) ===START===  192.168.250.250 
-- GET  
command=updateConfiguration&response=json&name=dynamic.apichecker.enabled&value=true&_=1471407604828
2016-08-17 00:20:03,156 INFO  [c.c.a.ApiServer] (catalina-exec-25:ctx-01fb5369 
ctx-9c3c87d4) (logid:3a6b506e) Restricted configuration update not allowed
2016-08-17 00:20:03,157 DEBUG [c.c.a.ApiServlet] (catalina-exec-25:ctx-01fb5369 
ctx-9c3c87d4) (logid:3a6b506e) ===END===  192.168.250.250 -- GET  
command=updateConfiguration&response=json&name=dynamic.apichecker.enabled&value=true&_=1471407604828

When I say clean this is an environment that is all of two weeks old and has 2 
instances and about 5 accounts. These accounts are LDAP integrated and 
authenticate without issue after the update. All functions seems to work accept 
the role-based additions. The GUI doesn't even show the little icon in the tab. 
The management servers are Ubuntu 14.04.05 and the I am using community 
packages. There were no errors on the update.

Thank you for the help.

Regards,
Marty Godsey

Secondary VM https download certificate error

[Marty Godsey]

Hello,

I have updated my SSVMs to use SSL for traffic. I have uploaded my cert and 
almost everything works as intended. The console proxy works without issue. If 
I go to an instance and click view console, I am not prompted for an invalid 
certificate. However, if I go to templates and click download template, I get a 
properly formatted url:

https://ip.ip.ip.ip.mydomain.com/userdata/*

but the certificate is signed by systemvm which causes the browser to complain. 
I followed the documentation as written. I updated:

secstorage.encrypt.copy = true
secstorage.ssl.cert.domain = *.mydomain.com
consoleproxy.url.domain = *.mydomain.com

I also uploaded the cert and it was successful. I am confident everything is 
set from the cert side since the proxy works. I have rebooted the secondary 
storage vm numerous times and also destroyed it so it was recreated.

My ACS version is 4.9.


Regards,
Marty Godsey

[GitHub] cloudstack issue #1593: CLOUDSTACK-9417: Usage module refactoring

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1593
  
@blueorangutan test


---
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 issue #1619: Add the Transifex config for next version of CS (4.1...

[milamberspace]

Github user milamberspace commented on the issue:

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

Add the transifex config for new L10N resources files must be done after 
each new major release on master branch (for the N+1 release, and after the 
creation of the release branch)

After, we must update the translation on each branch (releases and master 
branch) regularly or just before make a minor release.

For the documentation, I've just update the wiki:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Update+L10N+files+from+Transifex+to+git+repo



---
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 #1611: marvin: deploy clusters in separate threads

[koushik-das]

Github user koushik-das commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1611#discussion_r75071072
  
--- Diff: tools/marvin/marvin/deployDataCenter.py ---
@@ -224,6 +225,15 @@ def createClusters(self, clusters, zoneId, podId, 
vmwareDc=None):
podId,
clusterId)
 
+threads = []
+for cluster in clusters:
+t = threading.Thread(target=createCluster, args=(cluster,))
+t.start()
+threads.append(t)
+
+for t in threads:
+t.join(1800)
--- End diff --

Instead of hardcoding, better to set it based on host count in the cluster. 
Also consider that waitForHost() can wait upto 60 secs.

If one t.join() throws what happens to the other threads. Also will 
__cleanAndExit() behave consistently if there are exceptions in multiple 
threads.


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