[GitHub] cloudstack pull request: Cleanup stale files in /tmp which is fill...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: [PROPOSAL] Commit to master through PR only

[Wilder Rodrigues]

Nice!

I spent couple of hours this morning to review a few PRs.

But we still have too many of them and not many people reviewing/testing, which 
makes the process a bit slow.

>From the guys who usually review PRs, who is currently on holidays?

Cheers,
Wilder


> On 29 Jun 2015, at 11:27, sebgoa  wrote:
> 
> Ok we are on,
> 
> Starting today, commit to master through PR only.
> 2 LGTM needed for merge.
> If Travis fails, we can still merge given a good explanation of why (since 
> travis has issues once in a while).
> 
> I will keep an eye on commit, at least once a day, and ping the list if I see 
> a commit that went in without a PR.
> 
> thanks, let's give this a shot, goal being of course to stabilize master for 
> 4.6.
> 
> Everyone should start testing master as if it were a release branch now.
> 
> -sebastien
> 
> 
> On Jun 28, 2015, at 9:17 AM, Remi Bergsma  wrote:
> 
>> Let’s do it!
>> 
>> Starting tomorrow we’ll commit to master through PR only (as described 
>> below), and we’ll evaluate this at Sept 30, 2015. 
>> 
>> I’ll put a reminder in my schedule to start the thread.
>> 
>> Regards,
>> Remi
>> 
>>> On 26 jun. 2015, at 23:10, Daan Hoogland  wrote:
>>> 
>>> date := 2015-09-30 ???
>>> 
>>> On Fri, Jun 26, 2015 at 9:54 PM, David Nalley  wrote:
 On Thu, Jun 25, 2015 at 10:38 AM, Sebastien Goasguen  
 wrote:
> Folks,
> 
> A few of us are in Amsterdam at DevOps days. We are chatting about 
> release management procedure.
> Remi is working on a set of principles that he will put on the wiki to 
> start a [DISCUSS].
> 
> However to get started on the right track. I would like to propose the 
> following easy step:
> 
> Starting Monday June 29th (next monday):
> 
> - Only commit through PR will land on master (after a minimum of 2 LGTM 
> and green Travis results)
> - Direct commit will be reverted
> - Any committer can merge the PR.
> 
> Goal being to start having a new practice -everything through PR for 
> everyone- which is an easy way to gate our own commits building up to a 
> PR.
> 
> There is no tooling involved, just human agreement.
> 
> cheers,
> 
> -Sebastien
 
 In general, +1
 I think we should set a time, say a month or two out, to review how
 well it has worked, and what we need to tweak to make things better. I
 think we should be explicit with this so that we can say 'On $date'
 we'll start a thread to talk about what has and hasn't worked and how
 we can improve this.
 
 --David
>>> 
>>> 
>>> 
>>> -- 
>>> Daan
>> 
> 

Re: [PROPOSAL] Commit to master through PR only

[sebgoa]

On Jul 1, 2015, at 9:35 AM, Wilder Rodrigues  
wrote:

> Nice!
> 
> I spent couple of hours this morning to review a few PRs.
> 
> But we still have too many of them and not many people reviewing/testing, 
> which makes the process a bit slow.
> 

I expect this week to get slow. It's July 4th week end in the US.

And it's a new process.

IMHO there is no problem in being a little slow and having a back log of PRs as 
long as it make releasing faster.

And it will motivate everyone to review.

> From the guys who usually review PRs, who is currently on holidays?
> 
> Cheers,
> Wilder
> 
> 
>> On 29 Jun 2015, at 11:27, sebgoa  wrote:
>> 
>> Ok we are on,
>> 
>> Starting today, commit to master through PR only.
>> 2 LGTM needed for merge.
>> If Travis fails, we can still merge given a good explanation of why (since 
>> travis has issues once in a while).
>> 
>> I will keep an eye on commit, at least once a day, and ping the list if I 
>> see a commit that went in without a PR.
>> 
>> thanks, let's give this a shot, goal being of course to stabilize master for 
>> 4.6.
>> 
>> Everyone should start testing master as if it were a release branch now.
>> 
>> -sebastien
>> 
>> 
>> On Jun 28, 2015, at 9:17 AM, Remi Bergsma  wrote:
>> 
>>> Let’s do it!
>>> 
>>> Starting tomorrow we’ll commit to master through PR only (as described 
>>> below), and we’ll evaluate this at Sept 30, 2015. 
>>> 
>>> I’ll put a reminder in my schedule to start the thread.
>>> 
>>> Regards,
>>> Remi
>>> 
 On 26 jun. 2015, at 23:10, Daan Hoogland  wrote:
 
 date := 2015-09-30 ???
 
 On Fri, Jun 26, 2015 at 9:54 PM, David Nalley  wrote:
> On Thu, Jun 25, 2015 at 10:38 AM, Sebastien Goasguen  
> wrote:
>> Folks,
>> 
>> A few of us are in Amsterdam at DevOps days. We are chatting about 
>> release management procedure.
>> Remi is working on a set of principles that he will put on the wiki to 
>> start a [DISCUSS].
>> 
>> However to get started on the right track. I would like to propose the 
>> following easy step:
>> 
>> Starting Monday June 29th (next monday):
>> 
>> - Only commit through PR will land on master (after a minimum of 2 LGTM 
>> and green Travis results)
>> - Direct commit will be reverted
>> - Any committer can merge the PR.
>> 
>> Goal being to start having a new practice -everything through PR for 
>> everyone- which is an easy way to gate our own commits building up to a 
>> PR.
>> 
>> There is no tooling involved, just human agreement.
>> 
>> cheers,
>> 
>> -Sebastien
> 
> In general, +1
> I think we should set a time, say a month or two out, to review how
> well it has worked, and what we need to tweak to make things better. I
> think we should be explicit with this so that we can say 'On $date'
> we'll start a thread to talk about what has and hasn't worked and how
> we can improve this.
> 
> --David
 
 
 
 -- 
 Daan
>>> 
>> 
> 

[GitHub] cloudstack pull request: CLOUDSTACK-8597. Failed to migrate volume...

[likitha]

Github user likitha commented on the pull request:

https://github.com/apache/cloudstack/pull/541#issuecomment-117515627
  
@wilderrodrigues , 
Background -
1. When CS tries to live migrate a volume, it chooses a host endpoint to 
perform the migration by selecting any host that has the storage containing the 
volume mounted on it. Now when we attempt to migrate a volume that is on a zone 
wide storage, the endpoint could be any host in the zone because in case of 
zone wide storage, every host in the zone has the storage mounted on it. 
2. During migration, vCenter expects the target datastore/storage pool to 
be mounted on the source host because the VM obviously needs to be able to 
access the target datastore.

Now in the mentioned issue, say a host that doesn't contain the VM is 
chosen as the endpoint. As mentioned above, it could happen because today CS 
chooses any host that has the source storage mounted on it. In that case 
migration will fail because this host cant see the target datastore. 

By picking the host containing the volume's VM as endpoint we ensure that 
both the source and target storage pools are visible to the VM irrespective of 
the scope of the storage pool.

Previously, similar fixes have been made for other operations like volume 
deletion, snapshot creation because in these cases as well the underlying 
resource needs the VM of the volume to be visible to the host endpoint.


---
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-8597. Failed to migrate volume...

[wilderrodrigues]

Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/541#issuecomment-117517309
  
Hi @likitha 

I understood what the issue says, but what I really meant concerns what the 
code does.

The only practical change in the code was this:

if (volume.getHypervisorType() == Hypervisor.HypervisorType.Hyperv || 
volume.getHypervisorType() == Hypervisor.HypervisorType.VMware) {
...
}

Which means that now it will also get in the IF when the Hypervisor is of 
HypervisorType.VMware type.

So, what you really want is: support volume migration from zone-wide to 
cluster-wide storage when hypervisor is VMware.

Is that correct?

If you look further at the code, when CS will do DELETEVOLUME, it would 
take into account only VMware. So, HyperV wouldn't be supported.


![image](https://cloud.githubusercontent.com/assets/5129209/8450115/dc04f71c-1fd7-11e5-8cbc-127d4030ce73.png)

Cheers,
Wilder


---
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: Cleanup stale files in /tmp which is fill...

[DaanHoogland]

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/531#issuecomment-117517228
  
@wilderrodrigues let's stick to that for now (I kind of did the last few 
findbugs thing to see what happened with them:)

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 pull request: Cleanup stale files in /tmp which is fill...

[wilderrodrigues]

Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/531#issuecomment-117517482
  
@DaanHoogland 

I already merged :)

Got a LGTM from @karuturi 

Thanks, guys!


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

Build failed in Jenkins: simulator-singlerun #1327

[jenkins]

See 

--
Started by upstream project "build-master-simulator" build number 2144
originally caused by:
 Started by an SCM change
 Started by upstream project "build-master" build number 2439
 originally caused by:
  Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on simulator in workspace 

 > /usr/bin/git rev-parse --is-inside-work-tree # timeout=400
Fetching changes from the remote Git repository
 > /usr/bin/git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git # timeout=400
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
 > /usr/bin/git --version # timeout=400
 > /usr/bin/git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git 
 > +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:735)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:983)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1016)
at hudson.scm.SCM.checkout(SCM.java:484)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1258)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
at hudson.model.Run.execute(Run.java:1759)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags 
--progress https://git-wip-us.apache.org/repos/asf/cloudstack.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: error:  while accessing 
https://git-wip-us.apache.org/repos/asf/cloudstack.git/info/refs

fatal: HTTP request failed

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1591)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1379)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:86)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:324)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:121)
at hudson.remoting.UserRequest.perform(UserRequest.java:49)
at hudson.remoting.Request$2.run(Request.java:324)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
at ..remote call to simulator(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
at hudson.remoting.Channel.call(Channel.java:752)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor375.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at sun.proxy.$Proxy46.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:733)
... 11 more
ERROR: Error fetching remote repo 'origin'
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JUnit
[xUnit] [INFO] - [JUnit] - No test report file(s) were found with the pattern 
'xunit.xml' relative to 
' for the testing 
framework 'JUnit'.  Did you enter a pattern relative to the correct directory?  
Did you generate the result report(s) for 'JUnit'?
[xUnit] [ERROR] - No test reports found for the metric 'JUnit' with the 

[GitHub] cloudstack pull request: CLOUDSTACK-8597. Failed to migrate volume...

[likitha]

Github user likitha commented on the pull request:

https://github.com/apache/cloudstack/pull/541#issuecomment-117526563
  
Yes, now in addition to HyperV, even in case of VMware we want CS to chose 
the host containing the VM as the endpoint when the storage actions is 
'MIGRATEVOLUME'. 
Since the code to do that already exists because of HyperV, I simply added 
a check for VMware 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.
---

Custom dictionary implementation

[Ramzi Youssefi]

Hello everyone,

I'm implementing a UI Plugin and I would like to have a custom dictionary
for the labels.
Could you guys please provide an example on how to do this?
I need three different languages and I would like to have the labels in the
dictionary within the plugin.

Any help would be greatly appreciated.
Regards,
-- 
Ramzi Youssefi
Görlitzer Str. 49
01099 Dresden, Germany.
Cell: +49 173 1965465
Email: ryouss...@gmail.com

[GitHub] cloudstack pull request: CLOUDSTACK-8597. Failed to migrate volume...

[sateesh-chodapuneedi]

Github user sateesh-chodapuneedi commented on the pull request:

https://github.com/apache/cloudstack/pull/541#issuecomment-117537697
  
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-cloudmonkey pull request: Dockerfile

[runseb]

Github user runseb commented on the pull request:


https://github.com/apache/cloudstack-cloudmonkey/pull/7#issuecomment-117538042
  
LGTM, feel free to merge


---
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-8597. Failed to migrate volume...

[wilderrodrigues]

Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/541#issuecomment-117541379
  
Hi @likitha 

And what about DeleteVolume? It now supports only VMware, but the 
MigrateVolume supports both VMware and HyperV. It would be nice to keep it 
consistent.

I have 2 suggestions:

1. Edit the issue title to make sure that it complies with your fix. 
Something like this: Failed to migrate a volume from zone-wide to cluster-wide 
storage when using VMware.

2. If you don't mind, create another issue to deal with the 
StorageAction.DELETEVOLUME and change it in a separate PR. I think it should be 
consistent.

You got my LGTM based on the explanations you gave.

Cheers,
Wilder




---
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: [PROPOSAL] Quota management service for cloudstack

[sebgoa]

On Jun 26, 2015, at 1:32 PM, Abhinandan Prateek 
 wrote:

> Team,
> 
>   Would like to enhance usage server to provide quota management service to 
> cloudstack.
> This will provide better control on resource usage; and a common denomination 
> to measure resource usage.
> This will be an optional service that can be enabled or disabled as required 
> by the operator.
> 
> The detailed discussion is in functional specs here [2]. The corresponding 
> jira ticket is [1].
> 
> Please vote so that a decision to include it or not can be taken.
> 
> [1] https://issues.apache.org/jira/browse/CLOUDSTACK-8592
> [2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Quota+Service+-+FS
> 

Can you add this to the roadmap wiki page…

thanks

> 
> Regards,
> -abhi
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design & Build
> CSForge - rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software 
> Engineering
> CloudStack Infrastructure 
> Support
> CloudStack Bootcamp Training 
> Courses
> 
> This email and any attachments to it may be confidential and are intended 
> solely for the use of the individual to whom it is addressed. Any views or 
> opinions expressed are solely those of the author and do not necessarily 
> represent those of Shape Blue Ltd or related companies. If you are not the 
> intended recipient of this email, you must neither take any action based upon 
> its contents, nor copy or show it to anyone. Please contact the sender if you 
> believe you have received this email in error. Shape Blue Ltd is a company 
> incorporated in England & Wales. ShapeBlue Services India LLP is a company 
> incorporated in India and is operated under license from Shape Blue Ltd. 
> Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
> operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
> registered by The Republic of South Africa and is traded under license from 
> Shape Blue Ltd. ShapeBlue is a registered trademark.

RE: [PROPOSAL] Quota management service for cloudstack

[Rajesh Battala]

+1 
Nice feature to have 

-Original Message-
From: Abhinandan Prateek [mailto:abhinandan.prat...@shapeblue.com] 
Sent: Friday, June 26, 2015 5:03 PM
To: CloudStack Dev
Subject: [PROPOSAL] Quota management service for cloudstack

Team,

   Would like to enhance usage server to provide quota management service to 
cloudstack.
This will provide better control on resource usage; and a common denomination 
to measure resource usage.
This will be an optional service that can be enabled or disabled as required by 
the operator.

The detailed discussion is in functional specs here [2]. The corresponding jira 
ticket is [1].

Please vote so that a decision to include it or not can be taken.

[1] https://issues.apache.org/jira/browse/CLOUDSTACK-8592
[2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Quota+Service+-+FS


Regards,
-abhi
Find out more about ShapeBlue and our range of CloudStack related services

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

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

Re: [PROPOSAL] Quota management service for cloudstack

[Erik Weber]

On Fri, Jun 26, 2015 at 1:32 PM, Abhinandan Prateek <
abhinandan.prat...@shapeblue.com> wrote:

> Team,
>
>Would like to enhance usage server to provide quota management service
> to cloudstack.
> This will provide better control on resource usage; and a common
> denomination to measure resource usage.
> This will be an optional service that can be enabled or disabled as
> required by the operator.
>
> The detailed discussion is in functional specs here [2]. The corresponding
> jira ticket is [1].
>
> Please vote so that a decision to include it or not can be taken.
>
> [1] https://issues.apache.org/jira/browse/CLOUDSTACK-8592
> [2]
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Quota+Service+-+FS
>
>

I am a bit slow nowadays (vacation_mode = True), would you mind describing
how this differs from the current account/global limits?

-- 
Erik

Re: [PROPOSAL] Quota management service for cloudstack

[Rohit Yadav]

> On 01-Jul-2015, at 10:58 am, Erik Weber  wrote:
>
> I am a bit slow nowadays (vacation_mode = True), would you mind describing
> how this differs from the current account/global limits?

I think the global limits and quota are quite different,

Account/Global limits are per resource are to limit a user/account to 
run/deploy/use maximum amount of a resource, for example number of VMs a user 
can deploy.

Quota is to block new demands from a user/account once they exhaust their 
quota/credit.

For example, we can give some quota to a user which is giving them 1000 cloud 
coins (credit), each cloud resource such as ip address and VMs have a flat 
quota rate (for example, 10 points per IP); the user deploys bunch of VMs and 
consumes some public IPs etc, and finally the user exhausts the quota and the 
quota system blocks the user to demand any new resource.

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



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

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

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

[GitHub] cloudstack pull request: CLOUDSTACK-8597. Failed to migrate volume...

[likitha]

Github user likitha commented on the pull request:

https://github.com/apache/cloudstack/pull/541#issuecomment-117559997
  
Thanks for taking the time to review @wilderrodrigues.
I have updated the issue description.
As far as 'StorageAction.DELETEVOLUME' is concerned I am not entirely sure 
if the same logic applies to HyperV, In case of VMware since we can't access 
volume managed object, we reconfigure the VM managed object to detach the 
volume and further delete it. And that is why we choose the endpoint based on 
the VM. I am not sure if we have the same problem in HyperV. In any case I will 
open a ticket to track it, that way we a HyperV expert can comment on it. 


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

[GitHub] cloudstack pull request: CLOUDSTACK-8602. MigrateVirtualMachineWit...

[likitha]

GitHub user likitha opened a pull request:

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

CLOUDSTACK-8602. MigrateVirtualMachineWithVolume leaves old chain dat…

…a for volume.

Update chain info of a volume after  migration.

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

$ git pull https://github.com/likitha/cloudstack CLOUDSTACK-8602

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

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


commit fc33dc35645d52caf5cdbed112101df83104feab
Author: Likitha Shetty 
Date:   2015-04-17T18:33:26Z

CLOUDSTACK-8602. MigrateVirtualMachineWithVolume leaves old chain data for 
volume.
Update chain info of a volume after  migration.




---
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-8180 - RouterVM does no longer...

[wilderrodrigues]

GitHub user wilderrodrigues opened a pull request:

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

CLOUDSTACK-8180 - RouterVM does no longer provide X-ForwardedFor header 
with Loadbalancer

Hi @remibergsma and @DaanHoogland 

The "option forwardfor" in the haproxy has been fixed.

- Make sure the "option forwardfor" is always available by not removing it
- If keepalived is enabled, then set "no option forceclose"

Could you please have a look at this PR?

The first commit is about formatting the code, can be ignored. The second 
commit is the actual change.

Cheers,
Wilder

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

$ git pull https://github.com/schubergphilis/cloudstack fix/CLOUDSTACK-8180

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

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


commit 4dd000b850d3afa98b66b623aaec6f6e8bdcab01
Author: wilderrodrigues 
Date:   2015-07-01T09:51:06Z

CLOUDSTACK-8180 - RouterVM does no longer provide X-ForwardedFor header 
with Loadbalancer

   - Formatting code

commit 932f8aee261411da75c549f4e4ddaca77a4714d9
Author: wilderrodrigues 
Date:   2015-07-01T09:52:11Z

CLOUDSTACK-8180 - RouterVM does no longer provide X-ForwardedFor header 
with Loadbalancer

   - Make sure the "option forwardfor" is always available by not removing 
it
   - If keepalived is enabled, then set "no option forceclose"




---
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-8180 - RouterVM does no longer...

[remibergsma]

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/549#issuecomment-117576939
  
Thanks for fixing it, LGTM.
Small comment: I see two commits with the same first line. Personally I'd 
prefer to see from the first line what a commit implements.


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

Timezone for snapshot policy ACS 4.3.2 - wrong interpretation or not

[Andrija Panic]

Hi,

can anyone shed some light on the problem I see with time zones while
creating scheduled snapshot policies...

Im creating scheduled snapshot for 1 volume, I keep 1 last snapshot, I set
timezone to i.e. Europe/Zurich, scheduled to run at 1AM after midnight.

After I check DB, in cloud.snapshot_policy table I see policy created fine
But in cloud.snasphot_schedule - I see time set to TODAY 23H, instead of
tomorow 1AM as per the policy.

Time now (as I'm typing this) :) is 13h/1PM - so normally I expect next
daily snapshot to happen tomorow after midnight 1AM.

Am I doing something wrong here, or is my understanding of zones wrong for
some reason ?

Timezone on the management server/OS is CEST as we speak, reflecting reall
time on our timezone...

Thanks,

-- 

Andrija Panić

[GitHub] cloudstack pull request: CLOUDSTACK-8180 - RouterVM does no longer...

[wilderrodrigues]

Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/549#issuecomment-117583894
  
@remibergsma 

I also think it's a bit annoying the commits with the same message, but we 
have to inform the jira issue.

Next time I will add the jira issue number but not the whole description. 
Instead of the description I will add the commit message... It will clarify 
things.

Thanks for the review.

Cheers,
Wilder


---
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: [PROPOSAL] Quota management service for cloudstack

[Koushik Das]

I like the concept of quota. But I am thinking whether this should be a core 
part of CS or developed as a plugin. Cloud coins example given below may be a 
plugin, based on which decision to allow/disallow operation is made. Another 
plugin could be to allow/disallow operations based on VM count or say the 
current storage used in bytes. There should be flexibility to put in a 
condition of choice by the developer/user. If there are multiple such plugins, 
an option should be provided to decide the ordering of the plugins (similar to 
the various host investigators that are available).

-Koushik

-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com] 
Sent: Wednesday, 1 July 2015 14:48
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] Quota management service for cloudstack


> On 01-Jul-2015, at 10:58 am, Erik Weber  wrote:
>
> I am a bit slow nowadays (vacation_mode = True), would you mind 
> describing how this differs from the current account/global limits?

I think the global limits and quota are quite different,

Account/Global limits are per resource are to limit a user/account to 
run/deploy/use maximum amount of a resource, for example number of VMs a user 
can deploy.

Quota is to block new demands from a user/account once they exhaust their 
quota/credit.

For example, we can give some quota to a user which is giving them 1000 cloud 
coins (credit), each cloud resource such as ip address and VMs have a flat 
quota rate (for example, 10 points per IP); the user deploys bunch of VMs and 
consumes some public IPs etc, and finally the user exhausts the quota and the 
quota system blocks the user to demand any new resource.

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



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

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

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

[GitHub] cloudstack pull request: CLOUDSTACK-8597. Failed to migrate volume...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-8566: Filter sensitive details...

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/536#issuecomment-117600568
  
I guess a better fix needs to be worked on, closing now.


---
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-8566: Filter sensitive details...

[bhaisaab]

Github user bhaisaab closed the pull request at:

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


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

Build failed in Jenkins: simulator-singlerun #1328

[jenkins]

See 

--
Started by upstream project "build-master-simulator" build number 2145
originally caused by:
 Started by an SCM change
 Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on simulator in workspace 

 > /usr/bin/git rev-parse --is-inside-work-tree # timeout=400
Fetching changes from the remote Git repository
 > /usr/bin/git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git # timeout=400
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
 > /usr/bin/git --version # timeout=400
 > /usr/bin/git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git 
 > +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:735)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:983)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1016)
at hudson.scm.SCM.checkout(SCM.java:484)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1258)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
at hudson.model.Run.execute(Run.java:1759)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags 
--progress https://git-wip-us.apache.org/repos/asf/cloudstack.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: error:  while accessing 
https://git-wip-us.apache.org/repos/asf/cloudstack.git/info/refs

fatal: HTTP request failed

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1591)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1379)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:86)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:324)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:121)
at hudson.remoting.UserRequest.perform(UserRequest.java:49)
at hudson.remoting.Request$2.run(Request.java:324)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
at ..remote call to simulator(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
at hudson.remoting.Channel.call(Channel.java:752)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor375.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at sun.proxy.$Proxy46.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:733)
... 11 more
ERROR: Error fetching remote repo 'origin'
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JUnit
[xUnit] [INFO] - [JUnit] - No test report file(s) were found with the pattern 
'xunit.xml' relative to 
' for the testing 
framework 'JUnit'.  Did you enter a pattern relative to the correct directory?  
Did you generate the result report(s) for 'JUnit'?
[xUnit] [ERROR] - No test reports found for the metric 'JUnit' with the 
resolved pattern 'xunit.xml'. Configuration error?.
[xUnit] [INFO] - Failing BUILD.
[xUnit] [INFO] - There are errors when processing test results.
[xUnit] [INFO] 

Build failed in Jenkins: build-4.5 #493

[jenkins]

See 

Changes:

[Rohit Yadav] appliance: bump systemvm template version to 4.5.2

--
[...truncated 2970 lines...]
 T E S T S
---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-plugin-network-netscaler ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-plugin-network-palo-alto ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
cloud-plugin-network-palo-alto ---
[INFO] Compiling 2 source files to 

[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-plugin-network-netscaler ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
cloud-plugin-network-netscaler ---
[INFO] Compiling 12 source files to 

Running com.cloud.network.lb.LoadBalanceRuleHandlerTest
[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-plugin-network-internallb ---
[INFO] Surefire report directory: 


---
 T E S T S
---
log4j:WARN No appenders could be found for logger 
(com.cloud.network.lb.LoadBalanceRuleHandler).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.964 sec
Running com.cloud.network.lb.ElasticLoadBalancerManagerImplTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.811 sec

Results :

Tests run: 15, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Plugin - Network Nicira NVP 4.5.2-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
cloud-plugin-network-nvp ---
[INFO] Deleting 

 (includes = [**/*], excludes = [])
[INFO] Deleting 

 (includes = [target, dist], excludes = [])
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-plugin-network-nvp ---
Running org.apache.cloudstack.internallbelement.InternalLbElementTest
log4j:WARN No appenders could be found for logger 
(org.springframework.test.context.junit4.SpringJUnit4ClassRunner).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-plugin-network-nvp ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-plugin-network-nvp ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
cloud-plugin-network-nvp ---
[INFO] Compiling 71 source files to 

[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-plugin-network-palo-alto ---
[INFO] Surefire report directory: 


---
 T E S T S
---
Running com.cloud.network.resource.PaloAltoResourceTest
log4j:WARN No appenders could be found for logger 
(com.cloud.network.resource.PaloAltoResource).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
[INFO] 
[INFO] --- maven-r

Re: [PROPOSAL] Quota management service for cloudstack

[Rohit Yadav]

> On 01-Jul-2015, at 12:31 pm, Koushik Das  wrote:
>
> I like the concept of quota. But I am thinking whether this should be a core 
> part of CS or developed as a plugin.

It will be a separate plugin, not part of the core CS though we may need to 
refactor the core to allow configurability of features in the plugin.

> Cloud coins example given below may be a plugin, based on which decision to 
> allow/disallow operation is made. Another plugin could be to allow/disallow 
> operations based on VM count or say the current storage used in bytes. There 
> should be flexibility to put in a condition of choice by the developer/user. 
> If there are multiple such plugins, an option should be provided to decide 
> the ordering of the plugins (similar to the various host investigators that 
> are available).

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



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

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

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

Re: [PROPOSAL] Quota management service for cloudstack

[Abhinandan Prateek]

> On 01-Jul-2015, at 2:20 pm, sebgoa  wrote:
>
>
> On Jun 26, 2015, at 1:32 PM, Abhinandan Prateek 
>  wrote:
>
>> Team,
>>
>>  Would like to enhance usage server to provide quota management service to 
>> cloudstack.
>> This will provide better control on resource usage; and a common 
>> denomination to measure resource usage.
>> This will be an optional service that can be enabled or disabled as required 
>> by the operator.
>>
>> The detailed discussion is in functional specs here [2]. The corresponding 
>> jira ticket is [1].
>>
>> Please vote so that a decision to include it or not can be taken.
>>
>> [1] https://issues.apache.org/jira/browse/CLOUDSTACK-8592
>> [2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Quota+Service+-+FS
>>
>
> Can you add this to the roadmap wiki page…
>

Yes, added in the roadmap.

-abhi


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

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

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

[GitHub] cloudstack pull request: CLOUDSTACK-8180 - RouterVM does no longer...

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/549#issuecomment-117646467
  
@wilderrodrigues LGTM, meld the commits to one maybe?


---
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: Allow custom command role ACL files on cl...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-8180 - RouterVM does no longer...

[asfgit]

Github user asfgit closed the pull request at:

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


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

Build failed in Jenkins: simulator-singlerun #1329

[jenkins]

See 

--
Started by upstream project "build-master-simulator" build number 2146
originally caused by:
 Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on simulator in workspace 

 > /usr/bin/git rev-parse --is-inside-work-tree # timeout=400
Fetching changes from the remote Git repository
 > /usr/bin/git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git # timeout=400
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
 > /usr/bin/git --version # timeout=400
 > /usr/bin/git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git 
 > +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:735)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:983)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1016)
at hudson.scm.SCM.checkout(SCM.java:484)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1258)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
at hudson.model.Run.execute(Run.java:1759)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags 
--progress https://git-wip-us.apache.org/repos/asf/cloudstack.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: error:  while accessing 
https://git-wip-us.apache.org/repos/asf/cloudstack.git/info/refs

fatal: HTTP request failed

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1591)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1379)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:86)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:324)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:121)
at hudson.remoting.UserRequest.perform(UserRequest.java:49)
at hudson.remoting.Request$2.run(Request.java:324)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
at ..remote call to simulator(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
at hudson.remoting.Channel.call(Channel.java:752)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor375.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at sun.proxy.$Proxy46.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:733)
... 11 more
ERROR: Error fetching remote repo 'origin'
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JUnit
[xUnit] [INFO] - [JUnit] - No test report file(s) were found with the pattern 
'xunit.xml' relative to 
' for the testing 
framework 'JUnit'.  Did you enter a pattern relative to the correct directory?  
Did you generate the result report(s) for 'JUnit'?
[xUnit] [ERROR] - No test reports found for the metric 'JUnit' with the 
resolved pattern 'xunit.xml'. Configuration error?.
[xUnit] [INFO] - Failing BUILD.
[xUnit] [INFO] - There are errors when processing test results.
[xUnit] [INFO] - Skipping tests recording

[GitHub] cloudstack pull request: CLOUDSTACK-8600. Upon detaching a disk, d...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-8590 Refactoring NiciraNVP res...

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/546#issuecomment-117653714
  
@wilderrodrigues LGTM, and Travis is green though there is no way for me to 
test it against the real h/w. Please go ahead with the merge.


---
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-8590 Refactoring NiciraNVP res...

[asfgit]

Github user asfgit closed the pull request at:

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


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

Build failed in Jenkins: simulator-singlerun #1330

[jenkins]

See 

--
Started by upstream project "build-master-simulator" build number 2147
originally caused by:
 Started by upstream project "build-master" build number 2441
 originally caused by:
  Started by an SCM change
 Started by an SCM change
 Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on simulator in workspace 

 > /usr/bin/git rev-parse --is-inside-work-tree # timeout=400
Fetching changes from the remote Git repository
 > /usr/bin/git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git # timeout=400
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
 > /usr/bin/git --version # timeout=400
 > /usr/bin/git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git 
 > +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:735)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:983)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1016)
at hudson.scm.SCM.checkout(SCM.java:484)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1258)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
at hudson.model.Run.execute(Run.java:1759)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags 
--progress https://git-wip-us.apache.org/repos/asf/cloudstack.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: error:  while accessing 
https://git-wip-us.apache.org/repos/asf/cloudstack.git/info/refs

fatal: HTTP request failed

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1591)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1379)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:86)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:324)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:121)
at hudson.remoting.UserRequest.perform(UserRequest.java:49)
at hudson.remoting.Request$2.run(Request.java:324)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
at ..remote call to simulator(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
at hudson.remoting.Channel.call(Channel.java:752)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor375.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at sun.proxy.$Proxy46.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:733)
... 11 more
ERROR: Error fetching remote repo 'origin'
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JUnit
[xUnit] [INFO] - [JUnit] - No test report file(s) were found with the pattern 
'xunit.xml' relative to 
' for the testing 
framework 'JUnit'.  Did you enter a pattern relative to the correct directory?  
Did you generate the result report(s) for 'JUnit'?
[xUnit] [ERROR] - No test reports found for the metric 'JUnit' with the 
resolved pattern 'xunit.xml'. Configuration error?.

[GitHub] cloudstack pull request: GitHub master

[koushik-das]

GitHub user koushik-das opened a pull request:

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

GitHub master

Patch for CLOUDSTACK-8603. 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 github_master

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

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


commit 215f795f1d8d33de0092e1ed39a0994355df1fd9
Author: Koushik Das 
Date:   2015-07-01T12:12:02Z

CLOUDSTACK-8603: Random list VM failures at scale (more than 1000 VMs) when 
VM has resource tags
There is no 'removed' field on the resource_tags table. So 'id' based 
search may return a record or null in case record is deleted.
Added a check for null or empty in search resource tags based on 'id'.

commit 2650adc3ad5db3ae5841955ef33fe6902f1920f1
Author: Koushik Das 
Date:   2015-07-01T13:52:33Z

Merge remote-tracking branch 'origin/master' into github_master




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

Build failed in Jenkins: simulator-singlerun #1331

[jenkins]

See 

--
Started by upstream project "build-master-simulator" build number 2148
originally caused by:
 Started by upstream project "build-master" build number 2442
 originally caused by:
  Started by an SCM change
  Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on simulator in workspace 

 > /usr/bin/git rev-parse --is-inside-work-tree # timeout=400
Fetching changes from the remote Git repository
 > /usr/bin/git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git # timeout=400
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
 > /usr/bin/git --version # timeout=400
 > /usr/bin/git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git 
 > +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:735)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:983)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1016)
at hudson.scm.SCM.checkout(SCM.java:484)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1258)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
at hudson.model.Run.execute(Run.java:1759)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags 
--progress https://git-wip-us.apache.org/repos/asf/cloudstack.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: error:  while accessing 
https://git-wip-us.apache.org/repos/asf/cloudstack.git/info/refs

fatal: HTTP request failed

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1591)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1379)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:86)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:324)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:121)
at hudson.remoting.UserRequest.perform(UserRequest.java:49)
at hudson.remoting.Request$2.run(Request.java:324)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
at ..remote call to simulator(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
at hudson.remoting.Channel.call(Channel.java:752)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor375.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at sun.proxy.$Proxy46.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:733)
... 11 more
ERROR: Error fetching remote repo 'origin'
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JUnit
[xUnit] [INFO] - [JUnit] - No test report file(s) were found with the pattern 
'xunit.xml' relative to 
' for the testing 
framework 'JUnit'.  Did you enter a pattern relative to the correct directory?  
Did you generate the result report(s) for 'JUnit'?
[xUnit] [ERROR] - No test reports found for the metric 'JUnit' with the 
resolved pattern 'xunit.xml'. Configuration error?.
[xUnit] [INFO] - Failing

[ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

[Rohit Yadav]

The Project Management Committee (PMC) for Apache CloudStack are pleased to 
announce that Wilder  Rodrigues (ekho) has accepted our invitation to join the 
PMC.

Please join me in congratulating him.

On behalf of the Apache CloudStack PMC,
Rohit Yadav

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

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

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

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

Re: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

[Remi Bergsma]

Awesome news Wilder! :-)

Sent from my iPhone

> On 01 Jul 2015, at 19:12, Rohit Yadav  wrote:
> 
> The Project Management Committee (PMC) for Apache CloudStack are pleased to 
> announce that Wilder  Rodrigues (ekho) has accepted our invitation to join 
> the PMC.
> 
> Please join me in congratulating him.
> 
> On behalf of the Apache CloudStack PMC,
> Rohit Yadav
> 
> ---
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
> 
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design & Build
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software 
> Engineering
> CloudStack Infrastructure 
> Support
> CloudStack Bootcamp Training 
> Courses
> 
> This email and any attachments to it may be confidential and are intended 
> solely for the use of the individual to whom it is addressed. Any views or 
> opinions expressed are solely those of the author and do not necessarily 
> represent those of Shape Blue Ltd or related companies. If you are not the 
> intended recipient of this email, you must neither take any action based upon 
> its contents, nor copy or show it to anyone. Please contact the sender if you 
> believe you have received this email in error. Shape Blue Ltd is a company 
> incorporated in England & Wales. ShapeBlue Services India LLP is a company 
> incorporated in India and is operated under license from Shape Blue Ltd. 
> Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
> operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
> registered by The Republic of South Africa and is traded under license from 
> Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

[Mike Tutkowski]

Congratulations! :)

On Wed, Jul 1, 2015 at 11:12 AM, Rohit Yadav 
wrote:

> The Project Management Committee (PMC) for Apache CloudStack are pleased
> to announce that Wilder  Rodrigues (ekho) has accepted our invitation to
> join the PMC.
>
> Please join me in congratulating him.
>
> On behalf of the Apache CloudStack PMC,
> Rohit Yadav
>
> ---
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
>
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build<
> http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software Engineering<
> http://shapeblue.com/cloudstack-software-engineering/>
> CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses<
> http://shapeblue.com/cloudstack-training/>
>
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is a
> company incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
> a company registered by The Republic of South Africa and is traded under
> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>



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

Re: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

[Ahmad Emneina]

Sweet! Well deserved Wilder.

On Wed, Jul 1, 2015 at 10:19 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Congratulations! :)
>
> On Wed, Jul 1, 2015 at 11:12 AM, Rohit Yadav 
> wrote:
>
> > The Project Management Committee (PMC) for Apache CloudStack are pleased
> > to announce that Wilder  Rodrigues (ekho) has accepted our invitation to
> > join the PMC.
> >
> > Please join me in congratulating him.
> >
> > On behalf of the Apache CloudStack PMC,
> > Rohit Yadav
> >
> > ---
> > Rohit Yadav
> > Software Architect, ShapeBlue
> > M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> > Blog: bhaisaab.org | Twitter: @_bhaisaab
> >
> > Find out more about ShapeBlue and our range of CloudStack related
> services
> >
> > IaaS Cloud Design & Build<
> > http://shapeblue.com/iaas-cloud-design-and-build//>
> > CSForge – rapid IaaS deployment framework
> > CloudStack Consulting
> > CloudStack Software Engineering<
> > http://shapeblue.com/cloudstack-software-engineering/>
> > CloudStack Infrastructure Support<
> > http://shapeblue.com/cloudstack-infrastructure-support/>
> > CloudStack Bootcamp Training Courses<
> > http://shapeblue.com/cloudstack-training/>
> >
> > This email and any attachments to it may be confidential and are intended
> > solely for the use of the individual to whom it is addressed. Any views
> or
> > opinions expressed are solely those of the author and do not necessarily
> > represent those of Shape Blue Ltd or related companies. If you are not
> the
> > intended recipient of this email, you must neither take any action based
> > upon its contents, nor copy or show it to anyone. Please contact the
> sender
> > if you believe you have received this email in error. Shape Blue Ltd is a
> > company incorporated in England & Wales. ShapeBlue Services India LLP is
> a
> > company incorporated in India and is operated under license from Shape
> Blue
> > Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
> Brasil
> > and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd
> is
> > a company registered by The Republic of South Africa and is traded under
> > license from Shape Blue Ltd. ShapeBlue is a registered trademark.
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> *™*
>

Re: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

[Nux!]

Parabéns! :)

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Rohit Yadav" 
> To: "dev" 
> Sent: Wednesday, 1 July, 2015 18:12:36
> Subject: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

> The Project Management Committee (PMC) for Apache CloudStack are pleased to
> announce that Wilder  Rodrigues (ekho) has accepted our invitation to join the
> PMC.
> 
> Please join me in congratulating him.
> 
> On behalf of the Apache CloudStack PMC,
> Rohit Yadav
> 
> ---
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
> 
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design & Build
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software
> Engineering
> CloudStack Infrastructure
> Support
> CloudStack Bootcamp Training 
> Courses
> 
> This email and any attachments to it may be confidential and are intended 
> solely
> for the use of the individual to whom it is addressed. Any views or opinions
> expressed are solely those of the author and do not necessarily represent 
> those
> of Shape Blue Ltd or related companies. If you are not the intended recipient
> of this email, you must neither take any action based upon its contents, nor
> copy or show it to anyone. Please contact the sender if you believe you have
> received this email in error. Shape Blue Ltd is a company incorporated in
> England & Wales. ShapeBlue Services India LLP is a company incorporated in
> India and is operated under license from Shape Blue Ltd. Shape Blue Brasil
> Consultoria Ltda is a company incorporated in Brasil and is operated under
> license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by
> The Republic of South Africa and is traded under license from Shape Blue Ltd.
> ShapeBlue is a registered trademark.

Re: [PROPOSAL] Commit to master through PR only

[David Nalley]

On Wed, Jul 1, 2015 at 3:39 AM, sebgoa  wrote:
>
> On Jul 1, 2015, at 9:35 AM, Wilder Rodrigues  
> wrote:
>
>> Nice!
>>
>> I spent couple of hours this morning to review a few PRs.
>>
>> But we still have too many of them and not many people reviewing/testing, 
>> which makes the process a bit slow.
>>
>
> I expect this week to get slow. It's July 4th week end in the US.
>
> And it's a new process.
>
> IMHO there is no problem in being a little slow and having a back log of PRs 
> as long as it make releasing faster.
>
> And it will motivate everyone to review.
>

Having seen this work in a few other communities, it will create a
currency out of reviews. (and that's a good thing)
You'll review someones PR in exchange for their review. People will
come to the list asking for their review to get some attention.
We'll end up having a weekly(?) PR-athon, etc.

--David

Re: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

[Rafael Fonseca]

Well deserved indeed. Parabéns Wilder!

Sent from my iThing
On Jul 1, 2015 7:13 PM, "Rohit Yadav"  wrote:

> The Project Management Committee (PMC) for Apache CloudStack are pleased
> to announce that Wilder  Rodrigues (ekho) has accepted our invitation to
> join the PMC.
>
> Please join me in congratulating him.
>
> On behalf of the Apache CloudStack PMC,
> Rohit Yadav
>
> ---
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
>
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build<
> http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software Engineering<
> http://shapeblue.com/cloudstack-software-engineering/>
> CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses<
> http://shapeblue.com/cloudstack-training/>
>
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is a
> company incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
> a company registered by The Republic of South Africa and is traded under
> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>

RE: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

[Somesh Naidu]

Congratulations Wilder!

Regards,
Somesh

-Original Message-
From: Rafael Fonseca [mailto:rsafons...@gmail.com] 
Sent: Wednesday, July 01, 2015 1:43 PM
To: dev
Subject: Re: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

Well deserved indeed. Parabéns Wilder!

Sent from my iThing
On Jul 1, 2015 7:13 PM, "Rohit Yadav"  wrote:

> The Project Management Committee (PMC) for Apache CloudStack are pleased
> to announce that Wilder  Rodrigues (ekho) has accepted our invitation to
> join the PMC.
>
> Please join me in congratulating him.
>
> On behalf of the Apache CloudStack PMC,
> Rohit Yadav
>
> ---
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
>
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build<
> http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software Engineering<
> http://shapeblue.com/cloudstack-software-engineering/>
> CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses<
> http://shapeblue.com/cloudstack-training/>
>
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is a
> company incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
> a company registered by The Republic of South Africa and is traded under
> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>

Re: [PROPOSAL] Commit to master through PR only

[Rohit Yadav]

Hi,

> On 25-Jun-2015, at 4:38 pm, Sebastien Goasguen  wrote:
>
> A few of us are in Amsterdam at DevOps days. We are chatting about release 
> management procedure.
> Remi is working on a set of principles that he will put on the wiki to start 
> a [DISCUSS].
>
> However to get started on the right track. I would like to propose the 
> following easy step:
>
> Starting Monday June 29th (next monday):
>
> - Only commit through PR will land on master (after a minimum of 2 LGTM and 
> green Travis results)
> - Direct commit will be reverted
> - Any committer can merge the PR.

+1

I’ve been trying to help close PRs, it was difficult at first but then I found 
some tooling to help me do that. I think it’s certainly do-able without 
investing a lot of effort to do it, perhaps can done everyday or every few days 
in a week.

Some suggestions and comments to improve PR reviewing/merging:

- Let's merge the PR commits in a fast forward way instead of doing a branch 
merge that introduces frivolous merge commits. This is one approach to do 
quickly and painlessly:

http://blog.remibergsma.com/2015/05/24/accepting-pull-requests-the-easy-way/

- Let’s try to send PR around on one issue or one broad issue, or against a 
JIRA ticket; but avoid unrelated sub-systems etc

- If there are not many changes (say less than 100-200 lines were changed), 
let's have the changes melded into one commit. This can be done either by the 
PR author or by the committer. The immediate benefit is that all the changes 
will be much easy to port across other branches, easy to view and follow 
git-log, and easy to revert-able.

- Certain PRs that are typographical fixes, doc fixes and tooling related fixes 
- so let’s review and merge them if we’ve at least one green review (“LGTM”), 
though changes to CloudStack mgmt server, agent and plugins codebase IMO should 
have at least 2 green reviews (“LGTM”).

> Goal being to start having a new practice -everything through PR for 
> everyone- which is an easy way to gate our own commits building up to a PR.
>
> There is no tooling involved, just human agreement.
>
> cheers,

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



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

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

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

[GitHub] cloudstack pull request: CLOUDSTACK-8603: Random list VM failures ...

[koushik-das]

GitHub user koushik-das opened a pull request:

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

CLOUDSTACK-8603: Random list VM failures at scale (more than 1000 VMs…

…) when VM has resource tags

There is no 'removed' field on the resource_tags table. So 'id' based 
search may return a record or null in case record is deleted.
Added a check for null or empty in search resource tags based on 'id'.

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

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

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

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


commit 9f8ba5fcc8dc7d96774190bf44f848336dc06d9b
Author: Koushik Das 
Date:   2015-07-01T17:47:46Z

CLOUDSTACK-8603: Random list VM failures at scale (more than 1000 VMs) when 
VM has resource tags
There is no 'removed' field on the resource_tags table. So 'id' based 
search may return a record or null in case record is deleted.
Added a check for null or empty in search resource tags based on 'id'.




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

[koushik-das]

Github user koushik-das commented on the pull request:

https://github.com/apache/cloudstack/pull/550#issuecomment-117765057
  
Discarding 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 pull request: GitHub master

[koushik-das]

Github user koushik-das closed the pull request at:

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


---
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: [PROPOSAL] Commit to master through PR only

[John Burwell]

All,

I think we should stick to 2 votes per PR.  Defining types of PRs becomes 
difficult bordering on the arbitrary — adding a process complexity and the 
potential to start debating if a particular PR is one type or another.

I agree regarding the fast forward, and feel that all PRs should squashed down 
to one commit.  Ultimately, intermediate commits that seem informative in a 
feature branch become noise in a history as large as CloudStack’s.

To enforce the policy and ensure that PRs are merged in an orderly and correct 
manner (i.e. one at time), I think we should consider adopting a tool such as 
bors [1] to verify that the merge passes all tests and then performs the merge. 
It would some minor modification to require two votes, but I doubt that would 
take much effort to implement.  If there is interest, I would happy to make 
those changes for the project.

Thanks,
-John

[1]: https://github.com/graydon/bors

---
John Burwell (@john_burwell)
VP of Software Engineering, ShapeBlue
(571) 403-2411 | +44 20 3603 0542
http://www.shapeblue.com



> On Jul 1, 2015, at 1:48 PM, Rohit Yadav  wrote:
>
> Hi,
>
>> On 25-Jun-2015, at 4:38 pm, Sebastien Goasguen  wrote:
>>
>> A few of us are in Amsterdam at DevOps days. We are chatting about release 
>> management procedure.
>> Remi is working on a set of principles that he will put on the wiki to start 
>> a [DISCUSS].
>>
>> However to get started on the right track. I would like to propose the 
>> following easy step:
>>
>> Starting Monday June 29th (next monday):
>>
>> - Only commit through PR will land on master (after a minimum of 2 LGTM and 
>> green Travis results)
>> - Direct commit will be reverted
>> - Any committer can merge the PR.
>
> +1
>
> I’ve been trying to help close PRs, it was difficult at first but then I 
> found some tooling to help me do that. I think it’s certainly do-able without 
> investing a lot of effort to do it, perhaps can done everyday or every few 
> days in a week.
>
> Some suggestions and comments to improve PR reviewing/merging:
>
> - Let's merge the PR commits in a fast forward way instead of doing a branch 
> merge that introduces frivolous merge commits. This is one approach to do 
> quickly and painlessly:
>
> http://blog.remibergsma.com/2015/05/24/accepting-pull-requests-the-easy-way/
>
> - Let’s try to send PR around on one issue or one broad issue, or against a 
> JIRA ticket; but avoid unrelated sub-systems etc
>
> - If there are not many changes (say less than 100-200 lines were changed), 
> let's have the changes melded into one commit. This can be done either by the 
> PR author or by the committer. The immediate benefit is that all the changes 
> will be much easy to port across other branches, easy to view and follow 
> git-log, and easy to revert-able.
>
> - Certain PRs that are typographical fixes, doc fixes and tooling related 
> fixes - so let’s review and merge them if we’ve at least one green review 
> (“LGTM”), though changes to CloudStack mgmt server, agent and plugins 
> codebase IMO should have at least 2 green reviews (“LGTM”).
>
>> Goal being to start having a new practice -everything through PR for 
>> everyone- which is an easy way to gate our own commits building up to a PR.
>>
>> There is no tooling involved, just human agreement.
>>
>> cheers,
>
> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
>
>
>
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software 
> Engineering
> CloudStack Infrastructure 
> Support
> CloudStack Bootcamp Training 
> Courses
>
> This email and any attachments to it may be confidential and are intended 
> solely for the use of the individual to whom it is addressed. Any views or 
> opinions expressed are solely those of the author and do not necessarily 
> represent those of Shape Blue Ltd or related companies. If you are not the 
> intended recipient of this email, you must neither take any action based upon 
> its contents, nor copy or show it to anyone. Please contact the sender if you 
> believe you have received this email in error. Shape Blue Ltd is a company 
> incorporated in England & Wales. ShapeBlue Services India LLP is a company 
> incorporated in India and is operated under license from Shape Blue Ltd. 
> Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
> operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
> registered by The Republic of South Africa and is traded under license from 

Re: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

[John Burwell]

Congratulations and welcome Wilder.

---
John Burwell (@john_burwell)
VP of Software Engineering, ShapeBlue
(571) 403-2411 | +44 20 3603 0542
http://www.shapeblue.com



> On Jul 1, 2015, at 1:45 PM, Somesh Naidu  wrote:
>
> Congratulations Wilder!
>
> Regards,
> Somesh
>
> -Original Message-
> From: Rafael Fonseca [mailto:rsafons...@gmail.com]
> Sent: Wednesday, July 01, 2015 1:43 PM
> To: dev
> Subject: Re: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack
>
> Well deserved indeed. Parabéns Wilder!
>
> Sent from my iThing
> On Jul 1, 2015 7:13 PM, "Rohit Yadav"  wrote:
>
>> The Project Management Committee (PMC) for Apache CloudStack are pleased
>> to announce that Wilder  Rodrigues (ekho) has accepted our invitation to
>> join the PMC.
>>
>> Please join me in congratulating him.
>>
>> On behalf of the Apache CloudStack PMC,
>> Rohit Yadav
>>
>> ---
>> Rohit Yadav
>> Software Architect, ShapeBlue
>> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
>> Blog: bhaisaab.org | Twitter: @_bhaisaab
>>
>> Find out more about ShapeBlue and our range of CloudStack related services
>>
>> IaaS Cloud Design & Build<
>> http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Software Engineering<
>> http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure Support<
>> http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses<
>> http://shapeblue.com/cloudstack-training/>
>>
>> This email and any attachments to it may be confidential and are intended
>> solely for the use of the individual to whom it is addressed. Any views or
>> opinions expressed are solely those of the author and do not necessarily
>> represent those of Shape Blue Ltd or related companies. If you are not the
>> intended recipient of this email, you must neither take any action based
>> upon its contents, nor copy or show it to anyone. Please contact the sender
>> if you believe you have received this email in error. Shape Blue Ltd is a
>> company incorporated in England & Wales. ShapeBlue Services India LLP is a
>> company incorporated in India and is operated under license from Shape Blue
>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
>> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
>> a company registered by The Republic of South Africa and is traded under
>> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>>

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

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

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

Re: [GitHub] cloudstack pull request: As an operator I want to be able to chang...

[John Burwell]

Daan,

I disagree regarding the squash.  As I read through the list of commits, they 
read as a series of small commits that do not explain the overall change.  When 
this batch of small of commits is merged into the large history of master, the 
intent of this work will be lost.  In my opinion, squashing them into one 
commit with a descriptive commit message will be much more helpful to people 
trying to comprehend the work at some point in the future.

Thanks,
-John

---
John Burwell (@john_burwell)
VP of Software Engineering, ShapeBlue
(571) 403-2411 | +44 20 3603 0542
http://www.shapeblue.com



> On Jun 29, 2015, at 5:30 AM, Daan Hoogland  wrote:
>
> Do not squash commits and hide history unless it makes reading it much
> and obviously clearer. It is only good in my not so humble opinion in
> case of to and fro commits where a thing has been reverted and
> reapplied and reverted again and so on.
>
> Also do not rebase commits but make merge commits, this make seeing
> what happened when much easier and also make reverting of big chunks
> of work easier: if it seems to work merge, if it turns out it doesn't
> revert the merge fix and merge again.
>
> €0,02
>
>
> On Mon, Jun 29, 2015 at 11:07 AM, wilderrodrigues  wrote:
>> Github user wilderrodrigues commented on the pull request:
>>
>>https://github.com/apache/cloudstack/pull/527#issuecomment-116545842
>>
>>I created the issue and added to the last commit. Did it last week:
>>
>>https://issues.apache.org/jira/browse/CLOUDSTACK-8589
>>
>>Perhaps you missed that.
>>
>>Concerning squashed commits, ew should really have discussed about it 
>> when you were here. I'm 100% if I squash my atomic commits next time you 
>> guys will complain. It seems I haven't been clear enough about that yet.
>>
>>@remibergsma @miguelaferreira Would you guys give your input on these 
>> "squash commits" matter? I'm a bit tired of this discussion. For me, 
>> squashed commits won't make a review easier, unless there is no review at 
>> all or if the committer has changes a couple of lines in a bash script.
>>
>>What I would like to see is people testing changes the way I do.
>>
>>Cheers,
>>Wilder
>>
>>
>> ---
>> 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.
>> ---
>
>
>
> --
> Daan

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

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

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

Running VMs stopped upon CloudStack agent disconnected and re-connecting to management server

[Indra Pramana]

Dear all,

I am using CloudStack version 4.2.0 with KVM hypervisor. I notice a strange
behaviour when an agent got disconnected from the management server and I
restarted the cloudstack-agent service to reconnect, it takes very long
time to reconnect. And most of the time, it will stop most -- if not all --
of the running VMs on the host before finally manage to re-connect.

I checked the management server logs, and it seems these are the entries
which caused  the VMs to be stopped:


2015-07-02 02:12:13,556 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) Executing:
/usr/share/cloudstack-common/scripts/vm/network/security_group.py
destroy_network_rules_for_vm --vmname i-648-2613-VM --vif vnet9
2015-07-02 02:12:13,711 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) Execution is successful.
2015-07-02 02:12:13,712 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) Try to stop the vm at first
2015-07-02 02:12:15,716 DEBUG [utils.script.Script]
(agentRequest-Handler-3:null) Executing: /bin/bash -c ls
/sys/class/net/breth1-8/brif | grep vnet
2015-07-02 02:12:15,741 DEBUG [utils.script.Script]
(agentRequest-Handler-3:null) Execution is successful.
2015-07-02 02:12:15,742 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-3:null) Processing command:
com.cloud.agent.api.StopCommand
2015-07-02 02:12:16,253 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) Executing:
/usr/share/cloudstack-common/scripts/vm/network/security_group.py
destroy_network_rules_for_vm --vmname i-2-1779-VM
2015-07-02 02:12:16,423 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) Execution is successful.
2015-07-02 02:12:16,424 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) Try to stop the vm at first
2015-07-02 02:12:16,426 DEBUG [utils.script.Script]
(agentRequest-Handler-3:null) Executing: /bin/bash -c ls
/sys/class/net/breth1-8/brif | grep vnet
2015-07-02 02:12:16,456 DEBUG [utils.script.Script]
(agentRequest-Handler-3:null) Execution is successful.
2015-07-02 02:12:16,457 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-3:null) Processing command:
com.cloud.agent.api.StopCommand


Any reason why the network rules need to be destroyed? How can I prevent
VMs to be stopped upon agent re-connecting to the management server? Anyone
seeing similar behaviour?

Looking forward to your reply, thank you.

Cheers.

Re: [PROPOSAL] Commit to master through PR only

[Daan Hoogland]

I'm afraid I don't agree on some of points here, Rohit.

On Wed, Jul 1, 2015 at 7:48 PM, Rohit Yadav  wrote:
...

> Some suggestions and comments to improve PR reviewing/merging:
>
> - Let's merge the PR commits in a fast forward way instead of doing a branch 
> merge that introduces frivolous merge commits. This is one approach to do 
> quickly and painlessly:
>
> http://blog.remibergsma.com/2015/05/24/accepting-pull-requests-the-easy-way/


Most specifically I am a great proponent of merge commits. The make
very clear that a bunch of work belongs together and was merged at a
certain point in time.

>
> - Let’s try to send PR around on one issue or one broad issue, or against a 
> JIRA ticket; but avoid unrelated sub-systems etc

Now this I strongly agree on with you.

>
> - If there are not many changes (say less than 100-200 lines were changed), 
> let's have the changes melded into one commit. This can be done either by the 
> PR author or by the committer. The immediate benefit is that all the changes 
> will be much easy to port across other branches, easy to view and follow 
> git-log, and easy to revert-able.

Only if the change is rally doing only one thing. It is the merge
commit that should make it easily revertible.

>
> - Certain PRs that are typographical fixes, doc fixes and tooling related 
> fixes - so let’s review and merge them if we’ve at least one green review 
> (“LGTM”), though changes to CloudStack mgmt server, agent and plugins 
> codebase IMO should have at least 2 green reviews (“LGTM”).

this is one I agree on again :) (score for those keeping: 2-2)


-- 
Daan

Re: [PROPOSAL] Commit to master through PR only

[Daan Hoogland]

On Wed, Jul 1, 2015 at 8:44 PM, John Burwell  wrote:
> All,
>
> I think we should stick to 2 votes per PR.  Defining types of PRs becomes 
> difficult bordering on the arbitrary — adding a process complexity and the 
> potential to start debating if a particular PR is one type or another.

agree

>
> I agree regarding the fast forward, and feel that all PRs should squashed 
> down to one commit.  Ultimately, intermediate commits that seem informative 
> in a feature branch become noise in a history as large as CloudStack’s.

bad practice in my not so humble opinion.

>
> To enforce the policy and ensure that PRs are merged in an orderly and 
> correct manner (i.e. one at time), I think we should consider adopting a tool 
> such as bors [1] to verify that the merge passes all tests and then performs 
> the merge. It would some minor modification to require two votes, but I doubt 
> that would take much effort to implement.  If there is interest, I would 
> happy to make those changes for the project.

Tooling is great but let us first find a practice to agree on and then
fit tooling on it.

>
> Thanks,
> -John
>
> [1]: https://github.com/graydon/bors
>
> ---
> John Burwell (@john_burwell)
> VP of Software Engineering, ShapeBlue
> (571) 403-2411 | +44 20 3603 0542
> http://www.shapeblue.com
>
>
>
>> On Jul 1, 2015, at 1:48 PM, Rohit Yadav  wrote:
>>
>> Hi,
>>
>>> On 25-Jun-2015, at 4:38 pm, Sebastien Goasguen  wrote:
>>>
>>> A few of us are in Amsterdam at DevOps days. We are chatting about release 
>>> management procedure.
>>> Remi is working on a set of principles that he will put on the wiki to 
>>> start a [DISCUSS].
>>>
>>> However to get started on the right track. I would like to propose the 
>>> following easy step:
>>>
>>> Starting Monday June 29th (next monday):
>>>
>>> - Only commit through PR will land on master (after a minimum of 2 LGTM and 
>>> green Travis results)
>>> - Direct commit will be reverted
>>> - Any committer can merge the PR.
>>
>> +1
>>
>> I’ve been trying to help close PRs, it was difficult at first but then I 
>> found some tooling to help me do that. I think it’s certainly do-able 
>> without investing a lot of effort to do it, perhaps can done everyday or 
>> every few days in a week.
>>
>> Some suggestions and comments to improve PR reviewing/merging:
>>
>> - Let's merge the PR commits in a fast forward way instead of doing a branch 
>> merge that introduces frivolous merge commits. This is one approach to do 
>> quickly and painlessly:
>>
>> http://blog.remibergsma.com/2015/05/24/accepting-pull-requests-the-easy-way/
>>
>> - Let’s try to send PR around on one issue or one broad issue, or against a 
>> JIRA ticket; but avoid unrelated sub-systems etc
>>
>> - If there are not many changes (say less than 100-200 lines were changed), 
>> let's have the changes melded into one commit. This can be done either by 
>> the PR author or by the committer. The immediate benefit is that all the 
>> changes will be much easy to port across other branches, easy to view and 
>> follow git-log, and easy to revert-able.
>>
>> - Certain PRs that are typographical fixes, doc fixes and tooling related 
>> fixes - so let’s review and merge them if we’ve at least one green review 
>> (“LGTM”), though changes to CloudStack mgmt server, agent and plugins 
>> codebase IMO should have at least 2 green reviews (“LGTM”).
>>
>>> Goal being to start having a new practice -everything through PR for 
>>> everyone- which is an easy way to gate our own commits building up to a PR.
>>>
>>> There is no tooling involved, just human agreement.
>>>
>>> cheers,
>>
>> Regards,
>> Rohit Yadav
>> Software Architect, ShapeBlue
>> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
>> Blog: bhaisaab.org | Twitter: @_bhaisaab
>>
>>
>>
>> Find out more about ShapeBlue and our range of CloudStack related services
>>
>> IaaS Cloud Design & Build
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Software 
>> Engineering
>> CloudStack Infrastructure 
>> Support
>> CloudStack Bootcamp Training 
>> Courses
>>
>> This email and any attachments to it may be confidential and are intended 
>> solely for the use of the individual to whom it is addressed. Any views or 
>> opinions expressed are solely those of the author and do not necessarily 
>> represent those of Shape Blue Ltd or related companies. If you are not the 
>> intended recipient of this email, you must neither take any action based 
>> upon its contents, nor copy or show it to anyone. Please contact the sender 
>> if you believe you have received this email in error. Shape Blue Ltd is a 
>> company incorporated in England & Wales. ShapeBlue Services India LL

[GitHub] cloudstack pull request: CLOUDSTACK-8180 - RouterVM does no longer...

[miguelaferreira]

Github user miguelaferreira commented on the pull request:

https://github.com/apache/cloudstack/pull/549#issuecomment-117802350
  
@wilderrodrigues @remibergsma @bhaisaab why not just put the the ticket ID 
in the commit message?
something like: 
*   CLOUDSTACK-8180: adding this
*   CLOUDSTACK-8180: changing that


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

Re: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

[Erik Weber]

On Wed, Jul 1, 2015 at 7:12 PM, Rohit Yadav 
wrote:

> The Project Management Committee (PMC) for Apache CloudStack are pleased
> to announce that Wilder  Rodrigues (ekho) has accepted our invitation to
> join the PMC.
>

Please join me in congratulating him.
>
>

Congratulations Wilder :-)

-- 
Erik

Re: [PROPOSAL] Commit to master through PR only

[Erik Weber]

On Wed, Jul 1, 2015 at 7:48 PM, Rohit Yadav 
wrote:

> Hi,
>
> > On 25-Jun-2015, at 4:38 pm, Sebastien Goasguen  wrote:
> >
> > A few of us are in Amsterdam at DevOps days. We are chatting about
> release management procedure.
> > Remi is working on a set of principles that he will put on the wiki to
> start a [DISCUSS].
> >
> > However to get started on the right track. I would like to propose the
> following easy step:
> >
> > Starting Monday June 29th (next monday):
> >
> > - Only commit through PR will land on master (after a minimum of 2 LGTM
> and green Travis results)
> > - Direct commit will be reverted
> > - Any committer can merge the PR.
>
> +1
>
> I’ve been trying to help close PRs, it was difficult at first but then I
> found some tooling to help me do that. I think it’s certainly do-able
> without investing a lot of effort to do it, perhaps can done everyday or
> every few days in a week.
>
> Some suggestions and comments to improve PR reviewing/merging:
>
> - Let's merge the PR commits in a fast forward way instead of doing a
> branch merge that introduces frivolous merge commits. This is one approach
> to do quickly and painlessly:
>
>
> http://blog.remibergsma.com/2015/05/24/accepting-pull-requests-the-easy-way/
>
>

I'm no git expert, so I don't know if the downloading of patches and
applying them has any benefits over branch merging, but what I usually do
is this:

(github is my remote name for the github repo)

$ git fetch github pull//head:

$ git checkout master (or whatever branch you're merging to)
$ git merge 

-- 
Erik

[GitHub] cloudstack pull request: CLOUDSTACK-8180 - RouterVM does no longer...

[remibergsma]

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/549#issuecomment-117813307
  
I agree, ticket id is enough. 

Sent from my iPhone

> On 01 Jul 2015, at 21:35, Miguel Ferreira  
wrote:
> 
> @wilderrodrigues @remibergsma @bhaisaab why not just put the the ticket 
ID in the commit message?
> something like:
> 
> CLOUDSTACK-8180: adding this
> CLOUDSTACK-8180: changing that
> —
> Reply to this email directly or view it on GitHub.
> 



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

[GitHub] cloudstack pull request: CLOUDSTACK-8180 - RouterVM does no longer...

[wilderrodrigues]

Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/549#issuecomment-117815608
  
Yep... Agree.

That's what I also suggested in my reply.

We are getting better... Next one will be perfect. :)

Thanks, guys!

Cheers,
Wilder

Sent from my iPhone

On 01 Jul 2015, at 22:17, Remi Bergsma 
mailto:notificati...@github.com>> wrote:

I agree, ticket id is enough.

Sent from my iPhone

> On 01 Jul 2015, at 21:35, Miguel Ferreira 
mailto:notificati...@github.com>> wrote:
>
> @wilderrodrigues @remibergsma @bhaisaab why not just put the the ticket 
ID in the commit message?
> something like:
>
> CLOUDSTACK-8180: adding this
> CLOUDSTACK-8180: changing that
> —
> Reply to this email directly or view it on GitHub.
>

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



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

Re: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

[Milamber]

Congratulations Wilder!



On 01/07/2015 17:12, Rohit Yadav wrote:

The Project Management Committee (PMC) for Apache CloudStack are pleased to 
announce that Wilder  Rodrigues (ekho) has accepted our invitation to join the 
PMC.

Please join me in congratulating him.

On behalf of the Apache CloudStack PMC,
Rohit Yadav

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

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

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

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

RE: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

[Rajesh Battala]

Hearty Congratulations  Wilder  Rodrigues

-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com] 
Sent: Wednesday, July 1, 2015 10:43 PM
To: dev
Subject: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

The Project Management Committee (PMC) for Apache CloudStack are pleased to 
announce that Wilder  Rodrigues (ekho) has accepted our invitation to join the 
PMC.

Please join me in congratulating him.

On behalf of the Apache CloudStack PMC,
Rohit Yadav

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

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

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

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

Re: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

[Rajani Karuturi]

Congratulations Wilder..

~Rajani

On Thu, Jul 2, 2015 at 7:48 AM, Rajesh Battala 
wrote:

> Hearty Congratulations  Wilder  Rodrigues
>
> -Original Message-
> From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
> Sent: Wednesday, July 1, 2015 10:43 PM
> To: dev
> Subject: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack
>
> The Project Management Committee (PMC) for Apache CloudStack are pleased
> to announce that Wilder  Rodrigues (ekho) has accepted our invitation to
> join the PMC.
>
> Please join me in congratulating him.
>
> On behalf of the Apache CloudStack PMC,
> Rohit Yadav
>
> ---
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
>
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build<
> http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software Engineering<
> http://shapeblue.com/cloudstack-software-engineering/>
> CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses<
> http://shapeblue.com/cloudstack-training/>
>
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is a
> company incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
> a company registered by The Republic of South Africa and is traded under
> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>

[GitHub] cloudstack pull request: CLOUDSTACK-8590 Refactoring NiciraNVP res...

[karuturi]

Github user karuturi commented on the pull request:

https://github.com/apache/cloudstack/pull/546#issuecomment-117896507
  
shouldnt we wait for another 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.
---

Re: [PROPOSAL] Commit to master through PR only

[Rajani Karuturi]

I do the same Erik. Sometimes I merge the changes from the authors branch
directly without creating a local copy (using the command mentioned in the
pull request mail).

+1 on 2 manual reviews per PR irrespective of how trivial it is.

-1 on squashed commits. If the author thinks that the change deserves more
than one commit, it should be that way. Fast forwarding >1 commits and
merging doesnt make any sense. The PR information is lost on all the
previous commits except for the one where the PR is mentioned.

~Rajani

On Thu, Jul 2, 2015 at 1:13 AM, Erik Weber  wrote:

> On Wed, Jul 1, 2015 at 7:48 PM, Rohit Yadav 
> wrote:
>
> > Hi,
> >
> > > On 25-Jun-2015, at 4:38 pm, Sebastien Goasguen 
> wrote:
> > >
> > > A few of us are in Amsterdam at DevOps days. We are chatting about
> > release management procedure.
> > > Remi is working on a set of principles that he will put on the wiki to
> > start a [DISCUSS].
> > >
> > > However to get started on the right track. I would like to propose the
> > following easy step:
> > >
> > > Starting Monday June 29th (next monday):
> > >
> > > - Only commit through PR will land on master (after a minimum of 2 LGTM
> > and green Travis results)
> > > - Direct commit will be reverted
> > > - Any committer can merge the PR.
> >
> > +1
> >
> > I’ve been trying to help close PRs, it was difficult at first but then I
> > found some tooling to help me do that. I think it’s certainly do-able
> > without investing a lot of effort to do it, perhaps can done everyday or
> > every few days in a week.
> >
> > Some suggestions and comments to improve PR reviewing/merging:
> >
> > - Let's merge the PR commits in a fast forward way instead of doing a
> > branch merge that introduces frivolous merge commits. This is one
> approach
> > to do quickly and painlessly:
> >
> >
> >
> http://blog.remibergsma.com/2015/05/24/accepting-pull-requests-the-easy-way/
> >
> >
>
> I'm no git expert, so I don't know if the downloading of patches and
> applying them has any benefits over branch merging, but what I usually do
> is this:
>
> (github is my remote name for the github repo)
>
> $ git fetch github pull//head:
> 
> $ git checkout master (or whatever branch you're merging to)
> $ git merge 
>
> --
> Erik
>

RE: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

[Koushik Das]

Congrats Wilder!

-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com] 
Sent: Wednesday, 1 July 2015 22:43
To: dev
Subject: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

The Project Management Committee (PMC) for Apache CloudStack are pleased to 
announce that Wilder  Rodrigues (ekho) has accepted our invitation to join the 
PMC.

Please join me in congratulating him.

On behalf of the Apache CloudStack PMC,
Rohit Yadav

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

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

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

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

Re: [PROPOSAL] Quota management service for cloudstack

[Koushik Das]

On 01-Jul-2015, at 4:44 PM, Rohit Yadav  wrote:

> 
>> On 01-Jul-2015, at 12:31 pm, Koushik Das  wrote:
>> 
>> I like the concept of quota. But I am thinking whether this should be a core 
>> part of CS or developed as a plugin.
> 
> It will be a separate plugin, not part of the core CS though we may need to 
> refactor the core to allow configurability of features in the plugin.

Please update the FS with the plugin interface and its interaction with the 
other components once it is finalized.

> 
>> Cloud coins example given below may be a plugin, based on which decision to 
>> allow/disallow operation is made. Another plugin could be to allow/disallow 
>> operations based on VM count or say the current storage used in bytes. There 
>> should be flexibility to put in a condition of choice by the developer/user. 
>> If there are multiple such plugins, an option should be provided to decide 
>> the ordering of the plugins (similar to the various host investigators that 
>> are available).
> 
> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
> 
> 
> 
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design & Build
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software 
> Engineering
> CloudStack Infrastructure 
> Support
> CloudStack Bootcamp Training 
> Courses
> 
> This email and any attachments to it may be confidential and are intended 
> solely for the use of the individual to whom it is addressed. Any views or 
> opinions expressed are solely those of the author and do not necessarily 
> represent those of Shape Blue Ltd or related companies. If you are not the 
> intended recipient of this email, you must neither take any action based upon 
> its contents, nor copy or show it to anyone. Please contact the sender if you 
> believe you have received this email in error. Shape Blue Ltd is a company 
> incorporated in England & Wales. ShapeBlue Services India LLP is a company 
> incorporated in India and is operated under license from Shape Blue Ltd. 
> Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
> operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
> registered by The Republic of South Africa and is traded under license from 
> Shape Blue Ltd. ShapeBlue is a registered trademark.

RE: [PROPOSAL] Commit to master through PR only

[Sateesh Chodapuneedi]

> -Original Message-
> From: John Burwell [mailto:john.burw...@shapeblue.com]
> Sent: Thursday, July 2, 2015 12:14 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] Commit to master through PR only
> 
> All,
> 
> I think we should stick to 2 votes per PR.  Defining types of PRs becomes 
> difficult
> bordering on the arbitrary — adding a process complexity and the potential to
> start debating if a particular PR is one type or another.
> 
> I agree regarding the fast forward, and feel that all PRs should squashed down
> to one commit.  Ultimately, intermediate commits that seem informative in a
> feature branch become noise in a history as large as CloudStack’s.

+1 for squashing to 1 commit

Regards,
Sateesh

> 
> To enforce the policy and ensure that PRs are merged in an orderly and correct
> manner (i.e. one at time), I think we should consider adopting a tool such as 
> bors
> [1] to verify that the merge passes all tests and then performs the merge. It
> would some minor modification to require two votes, but I doubt that would
> take much effort to implement.  If there is interest, I would happy to make 
> those
> changes for the project.
> 
> Thanks,
> -John
> 
> [1]: https://github.com/graydon/bors
> 
> ---
> John Burwell (@john_burwell)
> VP of Software Engineering, ShapeBlue
> (571) 403-2411 | +44 20 3603 0542
> http://www.shapeblue.com
> 
> 
> 
> > On Jul 1, 2015, at 1:48 PM, Rohit Yadav  wrote:
> >
> > Hi,
> >
> >> On 25-Jun-2015, at 4:38 pm, Sebastien Goasguen 
> wrote:
> >>
> >> A few of us are in Amsterdam at DevOps days. We are chatting about release
> management procedure.
> >> Remi is working on a set of principles that he will put on the wiki to 
> >> start a
> [DISCUSS].
> >>
> >> However to get started on the right track. I would like to propose the
> following easy step:
> >>
> >> Starting Monday June 29th (next monday):
> >>
> >> - Only commit through PR will land on master (after a minimum of 2 LGTM
> and green Travis results)
> >> - Direct commit will be reverted
> >> - Any committer can merge the PR.
> >
> > +1
> >
> > I’ve been trying to help close PRs, it was difficult at first but then I 
> > found some
> tooling to help me do that. I think it’s certainly do-able without investing 
> a lot of
> effort to do it, perhaps can done everyday or every few days in a week.
> >
> > Some suggestions and comments to improve PR reviewing/merging:
> >
> > - Let's merge the PR commits in a fast forward way instead of doing a branch
> merge that introduces frivolous merge commits. This is one approach to do
> quickly and painlessly:
> >
> > http://blog.remibergsma.com/2015/05/24/accepting-pull-requests-the-easy-
> way/
> >
> > - Let’s try to send PR around on one issue or one broad issue, or against a 
> > JIRA
> ticket; but avoid unrelated sub-systems etc
> >
> > - If there are not many changes (say less than 100-200 lines were changed),
> let's have the changes melded into one commit. This can be done either by the
> PR author or by the committer. The immediate benefit is that all the changes 
> will
> be much easy to port across other branches, easy to view and follow git-log,
> and easy to revert-able.
> >
> > - Certain PRs that are typographical fixes, doc fixes and tooling related 
> > fixes -
> so let’s review and merge them if we’ve at least one green review (“LGTM”),
> though changes to CloudStack mgmt server, agent and plugins codebase IMO
> should have at least 2 green reviews (“LGTM”).
> >
> >> Goal being to start having a new practice -everything through PR for
> everyone- which is an easy way to gate our own commits building up to a PR.
> >>
> >> There is no tooling involved, just human agreement.
> >>
> >> cheers,
> >
> > Regards,
> > Rohit Yadav
> > Software Architect, ShapeBlue
> > M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> > Blog: bhaisaab.org | Twitter: @_bhaisaab
> >
> >
> >
> > Find out more about ShapeBlue and our range of CloudStack related services
> >
> > IaaS Cloud Design & Build build//>
> > CSForge – rapid IaaS deployment framework
> > CloudStack Consulting
> > CloudStack Software Engineering engineering/>
> > CloudStack Infrastructure Support infrastructure-support/>
> > CloudStack Bootcamp Training Courses training/>
> >
> > This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based upon 
> its
> contents, nor copy or show it to anyone. Please contact the sender if you
> believe you have rece

RE: [PROPOSAL] Commit to master through PR only

[Rajesh Battala]

+1 for squashing commit

-Original Message-
From: John Burwell [mailto:john.burw...@shapeblue.com] 
Sent: Thursday, July 2, 2015 12:14 AM
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] Commit to master through PR only

All,

I think we should stick to 2 votes per PR.  Defining types of PRs becomes 
difficult bordering on the arbitrary — adding a process complexity and the 
potential to start debating if a particular PR is one type or another.

I agree regarding the fast forward, and feel that all PRs should squashed down 
to one commit.  Ultimately, intermediate commits that seem informative in a 
feature branch become noise in a history as large as CloudStack’s.

To enforce the policy and ensure that PRs are merged in an orderly and correct 
manner (i.e. one at time), I think we should consider adopting a tool such as 
bors [1] to verify that the merge passes all tests and then performs the merge. 
It would some minor modification to require two votes, but I doubt that would 
take much effort to implement.  If there is interest, I would happy to make 
those changes for the project.

Thanks,
-John

[1]: https://github.com/graydon/bors

---
John Burwell (@john_burwell)
VP of Software Engineering, ShapeBlue
(571) 403-2411 | +44 20 3603 0542
http://www.shapeblue.com



> On Jul 1, 2015, at 1:48 PM, Rohit Yadav  wrote:
>
> Hi,
>
>> On 25-Jun-2015, at 4:38 pm, Sebastien Goasguen  wrote:
>>
>> A few of us are in Amsterdam at DevOps days. We are chatting about release 
>> management procedure.
>> Remi is working on a set of principles that he will put on the wiki to start 
>> a [DISCUSS].
>>
>> However to get started on the right track. I would like to propose the 
>> following easy step:
>>
>> Starting Monday June 29th (next monday):
>>
>> - Only commit through PR will land on master (after a minimum of 2 LGTM and 
>> green Travis results)
>> - Direct commit will be reverted
>> - Any committer can merge the PR.
>
> +1
>
> I’ve been trying to help close PRs, it was difficult at first but then I 
> found some tooling to help me do that. I think it’s certainly do-able without 
> investing a lot of effort to do it, perhaps can done everyday or every few 
> days in a week.
>
> Some suggestions and comments to improve PR reviewing/merging:
>
> - Let's merge the PR commits in a fast forward way instead of doing a branch 
> merge that introduces frivolous merge commits. This is one approach to do 
> quickly and painlessly:
>
> http://blog.remibergsma.com/2015/05/24/accepting-pull-requests-the-easy-way/
>
> - Let’s try to send PR around on one issue or one broad issue, or against a 
> JIRA ticket; but avoid unrelated sub-systems etc
>
> - If there are not many changes (say less than 100-200 lines were changed), 
> let's have the changes melded into one commit. This can be done either by the 
> PR author or by the committer. The immediate benefit is that all the changes 
> will be much easy to port across other branches, easy to view and follow 
> git-log, and easy to revert-able.
>
> - Certain PRs that are typographical fixes, doc fixes and tooling related 
> fixes - so let’s review and merge them if we’ve at least one green review 
> (“LGTM”), though changes to CloudStack mgmt server, agent and plugins 
> codebase IMO should have at least 2 green reviews (“LGTM”).
>
>> Goal being to start having a new practice -everything through PR for 
>> everyone- which is an easy way to gate our own commits building up to a PR.
>>
>> There is no tooling involved, just human agreement.
>>
>> cheers,
>
> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
>
>
>
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software 
> Engineering
> CloudStack Infrastructure 
> Support
> CloudStack Bootcamp Training 
> Courses
>
> This email and any attachments to it may be confidential and are intended 
> solely for the use of the individual to whom it is addressed. Any views or 
> opinions expressed are solely those of the author and do not necessarily 
> represent those of Shape Blue Ltd or related companies. If you are not the 
> intended recipient of this email, you must neither take any action based upon 
> its contents, nor copy or show it to anyone. Please contact the sender if you 
> believe you have received this email in error. Shape Blue Ltd is a company 
> incorporated in England & Wales. ShapeBlue Services India LLP is a company 
> incorporated in India and is operated under license from Shape Blue Ltd. 
> Shape

RE: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

[Sateesh Chodapuneedi]

Hearty Congratulations Wilder :-)

Regards,
Sateesh

> -Original Message-
> From: Erik Weber [mailto:terbol...@gmail.com]
> Sent: Thursday, July 2, 2015 1:08 AM
> To: dev
> Subject: Re: [ANNOUNCE] Wilder Rodrigues as a new PMC member of
> CloudStack
> > The Project Management Committee (PMC) for Apache CloudStack are
> > pleased to announce that Wilder  Rodrigues (ekho) has accepted our
> > invitation to join the PMC.
> >
> 
> Please join me in congratulating him.
> 
> Congratulations Wilder :-)
> 
> --
> Erik

[GitHub] cloudstack pull request: Config drive changes for vm migration

[jayapalu]

GitHub user jayapalu opened a pull request:

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

Config drive changes for vm migration

On vm migration attaching it in destination host is taken care in this 
patch.
In this patch only xenserver resource changes are added.

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

$ git pull https://github.com/apache/cloudstack dhcpoffload

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

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


commit b641231ab01f13685b8a237abceebf446a532169
Author: Jayapal 
Date:   2015-06-17T09:46:54Z

Fixed issue in adding vm SG rules on vm reboot for xenserver 6.5

commit c3304c5d38759a4f0f304c378886c274662c4815
Author: Jayapal 
Date:   2015-06-09T10:43:21Z

CLOUDSTACK-8324: Added migration changes for config drive

commit b8c112e35bcc98e1ee142cfb8901a0d9af28320d
Author: Jayapal 
Date:   2015-06-09T10:43:21Z

CLOUDSTACK-8324: Added migration changes for config drive

commit 45721aed527dea84581a9a3bf1fe83ed909e30d1
Author: Jayapal 
Date:   2015-06-29T06:59:51Z

Merge branch 'dhcpoffload' of 
https://git-wip-us.apache.org/repos/asf/cloudstack into dhcpoffload

commit 197f0cb99e9e24684d644ae39ce62690b859b25f
Author: Jayapal 
Date:   2015-07-01T08:49:20Z

Removed using config drive label from the uservmservice

commit faa531de9dd3c1187a60d0ca62ed8a3eefba4f47
Author: Jayapal 
Date:   2015-07-02T04:26:58Z

Fixed config key in multiple places




---
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: [PROPOSAL] Commit to master through PR only

[Wilder Rodrigues]

Sateesh and Rajesh,

It seems you were the only guys who +1 the squash idea. Could you please share 
with us what benefits you think squashing commits will bring? 

I wil give you the simplest example that could come to my mind to encourage no 
squash:

* I open a Java class with 5 thousand lines. The first thing I do is format the 
code and commit the change.
* I go back to the class and apply the fix, let’s say, a 3 lines change, then I 
commit the change again.

Now, think about the PR. It will contain 2 commits: 1 with the formatting 
changes only; and a second commit with 3 lines change.

Would you like to see it quashed and all messed up? It would be very difficult 
to review.

That’s just a simple example.

Cheers,
Wilder 

> On 02 Jul 2015, at 07:22, Rajesh Battala  wrote:
> 
> +1 for squashing commit
> 
> -Original Message-
> From: John Burwell [mailto:john.burw...@shapeblue.com] 
> Sent: Thursday, July 2, 2015 12:14 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] Commit to master through PR only
> 
> All,
> 
> I think we should stick to 2 votes per PR.  Defining types of PRs becomes 
> difficult bordering on the arbitrary — adding a process complexity and the 
> potential to start debating if a particular PR is one type or another.
> 
> I agree regarding the fast forward, and feel that all PRs should squashed 
> down to one commit.  Ultimately, intermediate commits that seem informative 
> in a feature branch become noise in a history as large as CloudStack’s.
> 
> To enforce the policy and ensure that PRs are merged in an orderly and 
> correct manner (i.e. one at time), I think we should consider adopting a tool 
> such as bors [1] to verify that the merge passes all tests and then performs 
> the merge. It would some minor modification to require two votes, but I doubt 
> that would take much effort to implement.  If there is interest, I would 
> happy to make those changes for the project.
> 
> Thanks,
> -John
> 
> [1]: https://github.com/graydon/bors
> 
> ---
> John Burwell (@john_burwell)
> VP of Software Engineering, ShapeBlue
> (571) 403-2411 | +44 20 3603 0542
> http://www.shapeblue.com
> 
> 
> 
>> On Jul 1, 2015, at 1:48 PM, Rohit Yadav  wrote:
>> 
>> Hi,
>> 
>>> On 25-Jun-2015, at 4:38 pm, Sebastien Goasguen  wrote:
>>> 
>>> A few of us are in Amsterdam at DevOps days. We are chatting about release 
>>> management procedure.
>>> Remi is working on a set of principles that he will put on the wiki to 
>>> start a [DISCUSS].
>>> 
>>> However to get started on the right track. I would like to propose the 
>>> following easy step:
>>> 
>>> Starting Monday June 29th (next monday):
>>> 
>>> - Only commit through PR will land on master (after a minimum of 2 LGTM and 
>>> green Travis results)
>>> - Direct commit will be reverted
>>> - Any committer can merge the PR.
>> 
>> +1
>> 
>> I’ve been trying to help close PRs, it was difficult at first but then I 
>> found some tooling to help me do that. I think it’s certainly do-able 
>> without investing a lot of effort to do it, perhaps can done everyday or 
>> every few days in a week.
>> 
>> Some suggestions and comments to improve PR reviewing/merging:
>> 
>> - Let's merge the PR commits in a fast forward way instead of doing a branch 
>> merge that introduces frivolous merge commits. This is one approach to do 
>> quickly and painlessly:
>> 
>> http://blog.remibergsma.com/2015/05/24/accepting-pull-requests-the-easy-way/
>> 
>> - Let’s try to send PR around on one issue or one broad issue, or against a 
>> JIRA ticket; but avoid unrelated sub-systems etc
>> 
>> - If there are not many changes (say less than 100-200 lines were changed), 
>> let's have the changes melded into one commit. This can be done either by 
>> the PR author or by the committer. The immediate benefit is that all the 
>> changes will be much easy to port across other branches, easy to view and 
>> follow git-log, and easy to revert-able.
>> 
>> - Certain PRs that are typographical fixes, doc fixes and tooling related 
>> fixes - so let’s review and merge them if we’ve at least one green review 
>> (“LGTM”), though changes to CloudStack mgmt server, agent and plugins 
>> codebase IMO should have at least 2 green reviews (“LGTM”).
>> 
>>> Goal being to start having a new practice -everything through PR for 
>>> everyone- which is an easy way to gate our own commits building up to a PR.
>>> 
>>> There is no tooling involved, just human agreement.
>>> 
>>> cheers,
>> 
>> Regards,
>> Rohit Yadav
>> Software Architect, ShapeBlue
>> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
>> Blog: bhaisaab.org | Twitter: @_bhaisaab
>> 
>> 
>> 
>> Find out more about ShapeBlue and our range of CloudStack related services
>> 
>> IaaS Cloud Design & Build
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Software

[GitHub] cloudstack pull request: CLOUDSTACK-8606: DB performance impacted ...

[koushik-das]

GitHub user koushik-das opened a pull request:

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

CLOUDSTACK-8606: DB performance impacted due to VM sync.

VM sync. generates a lot of queries on vm_instance table with 
'instance_name' as filter. Since the field is not
indexed, these kind of queries will impact DB performance. Added an index 
for instance_name field.

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

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

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

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


commit 47e005db533cbd9b2e40efc0adb276b677e228e2
Author: Koushik Das 
Date:   2015-07-02T06:41:53Z

CLOUDSTACK-8606: DB performance impacted due to VM sync.
VM sync. generates a lot of queries on vm_instance table with 
'instance_name' as filter. Since the field is not
indexed, these kind of queries will impact DB performance. Added an index 
for instance_name field.




---
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: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

[Wilder Rodrigues]

Thanks a lot, guys!

As I told Rohit yesterday:

=
We have a common goal: make Apache CloudStack the most robust and rock solid 
cloud platform there is. I will take this opportunity to contribute even more 
and to lead people towards the same goal.
=

Thanks again for the trust!

Cheers,
Wilder


> On 02 Jul 2015, at 05:38, Rajani Karuturi  wrote:
> 
> Congratulations Wilder..
> 
> ~Rajani
> 
> On Thu, Jul 2, 2015 at 7:48 AM, Rajesh Battala 
> wrote:
> 
>> Hearty Congratulations  Wilder  Rodrigues
>> 
>> -Original Message-
>> From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
>> Sent: Wednesday, July 1, 2015 10:43 PM
>> To: dev
>> Subject: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack
>> 
>> The Project Management Committee (PMC) for Apache CloudStack are pleased
>> to announce that Wilder  Rodrigues (ekho) has accepted our invitation to
>> join the PMC.
>> 
>> Please join me in congratulating him.
>> 
>> On behalf of the Apache CloudStack PMC,
>> Rohit Yadav
>> 
>> ---
>> Rohit Yadav
>> Software Architect, ShapeBlue
>> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
>> Blog: bhaisaab.org | Twitter: @_bhaisaab
>> 
>> Find out more about ShapeBlue and our range of CloudStack related services
>> 
>> IaaS Cloud Design & Build<
>> http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Software Engineering<
>> http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure Support<
>> http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses<
>> http://shapeblue.com/cloudstack-training/>
>> 
>> This email and any attachments to it may be confidential and are intended
>> solely for the use of the individual to whom it is addressed. Any views or
>> opinions expressed are solely those of the author and do not necessarily
>> represent those of Shape Blue Ltd or related companies. If you are not the
>> intended recipient of this email, you must neither take any action based
>> upon its contents, nor copy or show it to anyone. Please contact the sender
>> if you believe you have received this email in error. Shape Blue Ltd is a
>> company incorporated in England & Wales. ShapeBlue Services India LLP is a
>> company incorporated in India and is operated under license from Shape Blue
>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
>> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
>> a company registered by The Republic of South Africa and is traded under
>> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>>