[GitHub] cloudstack pull request: [4.6] CLOUDSTACK-9083: Add disk serial to...

[wido]

Github user wido commented on the pull request:

https://github.com/apache/cloudstack/pull/1121#issuecomment-160559759
  
LGTM based on the code. I don't see any real issues.


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

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

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/1132#issuecomment-160561489
  
@sateesh-chodapuneedi this is a real bug for many users as they are not 
able to use Windows 2012 templates with vmware/CloudStack, which is why we need 
the fix in 4.5 for 4.5.3 besides this does not involve any db changes but 
simply add to a list of supported controller types other than ide or scsi.


---
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: What SDN are you using?

[Nux!]

Eric,

I think OVS is implied when we talk VXLAN on KVM.

Simon, thanks for your thoughts. It's what I was afraid of. Guess it's still 
early days for SDN. :-)

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "GoGoZoom PDX" 
> To: dev@cloudstack.apache.org
> Sent: Monday, 30 November, 2015 04:44:16
> Subject: Re: What SDN are you using?

> Hm - Not a single mention of OpenvSwitch? I wonder why?...
> 
> Eric Pretorious
> Portland, OR
> On Nov 29, 2015 11:20 AM, "Simon Weller"  wrote:
> 
>> Nux,
>>
>> The two most deployed SDN solutions are Vmware NSX-MH (Nicara) and Nuage
>> VSP (Alcatel-Lucent).  Neither are cheap!
>> We've been evaluating whether we're going to run a POC on Nuage, as it
>> does have some very cool features including service chaining.
>> Most of the other SDN plugins within CS are either very alpha, or haven't
>> received any updates in quite a while.
>> I polled the dev list list a few months back and it didn't appear anyone
>> on the lists were running (or willing to talk about) Big Switch, Midonet or
>> Stratosphere. I know someone built the start of a plugin for Open Daylight,
>> but it hasn't seen any development since then. We even reached out to
>> Midonet, offering to pay for support and they told us to install Openstack
>> ;-)
>>
>> We have the native KVM VXLAN implementation running in our lab and it
>> seems to work very well. We went 100% 10/40GB using open platform switches
>> and Cumulus linux.
>>
>> Our main interest in SDN is to provide more advanced traffic steering and
>> security features later.
>>
>> - Si
>>
>>
>>
>>
>>
>> 
>> From: Nux! 
>> Sent: Sunday, November 29, 2015 12:56 PM
>> To: Cloudstack Users List
>> Cc: dev
>> Subject: What SDN are you using?
>>
>> Hello,
>>
>> So besides the folks using Nicira, can anyone recommend any other SDN
>> thing or should I stay with v(x)lans?
>> I'm kind of removed from this side of things since my deployments tend to
>> be with Security Grups in a single or few VLANs, any suggestions welcome,
>> preferably free/foss.
>>
>> Lucian
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro

Re: What SDN are you using?

[sebgoa]

On Nov 29, 2015, at 8:19 PM, Simon Weller  wrote:

> Nux,
> 
> The two most deployed SDN solutions are Vmware NSX-MH (Nicara) and Nuage VSP 
> (Alcatel-Lucent).  Neither are cheap!
> We've been evaluating whether we're going to run a POC on Nuage, as it does 
> have some very cool features including service chaining.
> Most of the other SDN plugins within CS are either very alpha, or haven't 
> received any updates in quite a while. 
> I polled the dev list list a few months back and it didn't appear anyone on 
> the lists were running (or willing to talk about) Big Switch, Midonet or 
> Stratosphere.

Midonet and Stratosphere are pretty much abandoned.
So is the open contrail driver.

Big Switch should work as it was updated recently and should be in 4.6 (let me 
cc KC Wange who did the refactor recently).

The opendaylight and native GRE have always been beta, and you are correct that 
they have not received much attention.

> I know someone built the start of a plugin for Open Daylight, but it hasn't 
> seen any development since then. We even reached out to Midonet, offering to 
> pay for support and they told us to install Openstack ;-)
> 
> We have the native KVM VXLAN implementation running in our lab and it seems 
> to work very well. We went 100% 10/40GB using open platform switches and 
> Cumulus linux.

Good to know.

> 
> Our main interest in SDN is to provide more advanced traffic steering and 
> security features later.
> 
> - Si
> 
> 
> 
> 
> 
> 
> From: Nux! 
> Sent: Sunday, November 29, 2015 12:56 PM
> To: Cloudstack Users List
> Cc: dev
> Subject: What SDN are you using?
> 
> Hello,
> 
> So besides the folks using Nicira, can anyone recommend any other SDN thing 
> or should I stay with v(x)lans?
> I'm kind of removed from this side of things since my deployments tend to be 
> with Security Grups in a single or few VLANs, any suggestions welcome, 
> preferably free/foss.
> 
> Lucian
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro

Re: [NOTICE] people.apache.org web space is moving to home.apache.org

[sebgoa]

Talluri,

Can you answer Ian's comment below ?

-sebastien

On Nov 28, 2015, at 3:03 AM, Ian Duffy  wrote:

> What are the legal implications of any of hosting that
> licensed/copyrighted/paid-for material if any?
> 
> windows7.vhd
> RHEL6-64bit.ova
> RHEL764bitwithtools.vhd
> 79211594-1d4a-4dee-ae6c-c5c315ded2be.vhd which appears to be windows 8
> 
> On 25 November 2015 at 18:44, Srikanteswararao talluri <
> talluri.w...@gmail.com> wrote:
> 
>> Moved all the following references in the test code to
>> https://home.apache.org/~talluri/ .  github PR
>> https://github.com/apache/cloudstack/pull/1123
>> 
>> http://people.apache.org/~tsp/cloud-set-guest-password
>> 
>> http://people.apache.org/~tsp/dummy.iso
>> 
>> "http://people.apache.org/~sanjeev/centos63.ova";,
>> 
>> "http://people.apache.org/~sanjeev/windows7.vhd";,
>> 
>> "http://people.apache.org/~sanjeev/new-test-win.ova";,
>> 
>> "http://people.apache.org/~sanjeev/Rhel6-64bit.ova";,
>> 
>> "http://people.apache.org/~sanjeev/ttylinux_pv.vhd.bz2";,
>> 
>> "http://people.apache.org/~sanjeev/RHEL764bitwithtools.vhd";,
>> 
>> "
>> http://people.apache.org/~sanjeev/79211594-1d4a-4dee-ae6c-c5c315ded2be.vhd
>> ",
>> 
>> "http://people.apache.org/~sanjeev/rajani-thin-volume.vhd";,
>> 
>> "http://people.apache.org/~sanjeev/CentOS5.5(64bit)-vmware-autoscale.ova",
>> 
>> "http://people.apache.org/~sanjeev/rajani-thin-volume.qcow2";,
>> 
>> "http://people.apache.org/~sanjeev/centos56-x86_64.vhd.bz2";,
>> 
>> "http://people.apache.org/~sanjeev/CentOS5.3-x86_64.ova";
>> 
>> "
>> http://people.apache.org/~sanjeev/eec2209b-9875-3c8d-92be-c001bd8a0faf.qcow2.bz2
>> "
>> 
>> "url": "http://people.apache.org/~sanjeev/CentOS-6.3-x86_64-bin-DVD1.iso";
>> 
>> "
>> http://people.apache.org/~sanjeev/systemvm64template-2014-09-30-4.3-vmware.ova
>> ",
>> 
>> 
>> Thanks,
>> 
>> ~Talluri
>> 
>> 
>> On Wed, Nov 25, 2015 at 8:28 PM, Daan Hoogland 
>> wrote:
>> 
>>> You are right, Sebastien. @Rajani, do you have an idea on the volume of
>>> work, here?
>>> 
>>> On Wed, Nov 25, 2015 at 2:10 PM, sebgoa  wrote:
>>> 
 
 On Nov 25, 2015, at 2:07 PM, Daan Hoogland 
 wrote:
 
> are those refs expecting particular content returned? (it will be
> redirected)
> 
 
 the way I read the email, it will be redirected but would give a 404 if
 you don't move the data yourself :)
 
> On Wed, Nov 25, 2015 at 1:40 PM, Rajani Karuturi 
 wrote:
> 
>> We have references to people.apache.org in our testdata.
>> 
>> ~Rajani
>> 
>> On Wed, Nov 25, 2015 at 5:50 PM, Daniel Gruno >> 
>> wrote:
>> 
>>> Hi folks,
>>> as the subject says, people.apache.org is being decommissioned
>> soon,
 and
>>> personal web space is being moved to a new home, aptly named
>>> home.apache.org ( https://home.apache.org/ )
>>> 
>>> IMPORTANT:
>>> If you have things on people.apache.org that you would like to
>>> retain,
>>> please make a copy of it and move it to home.apache.org. (note,
>> you
 will
>>> have to make a folder called 'public_html' there, for items to show
>>> up
>>> under https://home.apache.org/~yourID/ ).
>>> 
>>> We will _NOT_ be moving your data for you. There is simply too much
>>> old
>>> junk data on minotaur (the current people.apache.org machine) for
>> it
 to
>>> make sense to rsync it across, so we have made the decision that
>>> moving
>>> data is up to each individual committer.
>>> 
>>> The new host, home.apache.org, will ONLY be for web space, you
>> will
 not
>>> have shell access to the machine (but you can copy data to it using
 SFTP
>>> and your SSH key). Access to modify LDAP records (for project
>> chairs)
>>> will be moved to a separate host when the time comes.
>>> 
>>> There will be a 3 month grace period to move your data across.
>> After
>>> this time span (March 1st, 2016), minotaur will no longer serve up
>>> personal web space, and visits to people.apache.org will be
>>> redirected
>>> to home.apache.org.
>>> 
>>> With regards,
>>> Daniel on behalf of the Apache Infrastructure Team.
>>> 
>>> PS: All replies to this should go to infrastruct...@apache.org
>>> 
>> 
> 
> 
> 
> --
> Daan
 
 
>>> 
>>> 
>>> --
>>> Daan
>>> 
>> 

Re: 4.7 status update

[sebgoa]

On Nov 27, 2015, at 7:23 PM, Remi Bergsma  wrote:

> Hi all,
> 
> The next version of Apache CloudStack will be built on top of 4.6 and 
> released from the stable master branch. In the past weeks we’ve added several 
> PRs on master with new features:
> 
>  *   Upgrade to latest AWS S3 SDK
>  *   List api’s preformance improvement
>  *   UI improvement and metrics views
>  *   Nicira plugin update
>  *   Nuage plugin update

+ quota ?

>  *   and a bunch of bug fixes and code quality improvements
> 
> Keep these dates in mind:
> 
> Mon Dec  7: 4.7.0 Feature freeze
> Mon Dec 14: 4.7.0 RC1
> 
> This means we’ve about 10 days until we freeze for 4.7. Please review PRs to 
> get them in on time. Maybe even send new PRs. But we do need reviewers ;-)
> 
> It will be a great release again!
> 
> Regards,
> Remi
> 

[GitHub] cloudstack pull request: CID-1338387: Deletion of method endPointS...

[runseb]

Github user runseb commented on the pull request:

https://github.com/apache/cloudstack/pull/1124#issuecomment-160568739
  
@rafaelweingartner there has been lots of discussion on the list about 
testing. The TravisCI setup is supposed to do part of it, and we can also 
trigger the tests as jenkins Jobs.There are problems with the TravisCI setup, 
it might be a good item to have your group tackle.


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

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

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/1131#issuecomment-160574800
  
@sateesh-chodapuneedi as mentioned on the other PR, the issue is that many 
users are not able to use Windows 2012 templates and we see this as a severe 
bug that needs to be fixed as Windows 2012 is a fairly common template to be 
deployed.


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

[GitHub] cloudstack pull request: [4.6] CLOUDSTACK-9083: Add disk serial to...

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/1121#issuecomment-160574861
  
Merging now that we're tests performed and 2LGTMs.


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

[GitHub] cloudstack pull request: [4.6] CLOUDSTACK-9083: Add disk serial to...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] cloudstack pull request: [4.5] CLOUDSTACK-9083: Add disk serial to...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] cloudstack pull request: [4.6] CLOUDSTACK-9083: Add disk serial to...

[DaanHoogland]

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1121#issuecomment-160576751
  
great @bhaisaab I'll create the merge forward


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

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/768#issuecomment-160578342
  
@remibergsma LGTM, I've rebased the branch against latest master 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: libvirt fix forward merge

[DaanHoogland]

GitHub user DaanHoogland opened a pull request:

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

libvirt fix forward merge

@remibergsma @karuturi can you check

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

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

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

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


commit 12c395b56052af36901ab3ed1a366ed8985740eb
Author: Rohit Yadav 
Date:   2015-11-25T09:07:40Z

CLOUDSTACK-9083: Add disk serial to kvm virt xml

Adds disk serial ids based on volume uuids to the virt xml. This may be 
useful
for appliances/software that needs some serial ids on the VM disks. This 
does not
impact existing/running VMs, the vm virt xmls will be updates for running 
VMs
the next time they are stopped/started.

For testing, disk serial (of debian based systemvm) in the virt xml matched 
that
in /sys/devices/pci:00::00:07.0/virtio4/block/vda/serial.

We currently don't support scsi-blcok devices for which serial is not 
supported,
for this we've added a DeviceType (LUN) which may be used in future and a 
check
to not add the serial to the xml if disk type is LUN.
Refer: https://libvirt.org/formatdomain.html#elementsDisks

Signed-off-by: Rohit Yadav 

commit 7dcc6540e76db06fe51e8f33803260762ffaa826
Author: Rohit Yadav 
Date:   2015-11-30T09:40:31Z

Merge pull request #1121 from shapeblue/4.6-cloudstack-9083

[4.6] CLOUDSTACK-9083: Add disk serial to kvm virt xmlAdds disk serial ids 
based on volume uuids to the virt xml. This may be useful
for appliances/software that needs some serial ids on the VM disks. This 
does not
impact existing/running VMs, the vm virt xmls will be updates for running 
VMs
the next time they are stopped/started.

For testing, disk serial (of debian based systemvm) in the virt xml matched 
that
in /sys/devices/pci:00::00:07.0/virtio4/block/vda/serial.

We currently don't support scsi-blcok devices for which serial is not 
supported,
for this we've added a DeviceType (LUN) which may be used in future and a 
check
to not add the serial to the xml if disk type is LUN.
Refer: https://libvirt.org/formatdomain.html#elementsDisks

* pr/1121:
  CLOUDSTACK-9083: Add disk serial to kvm virt xml

Signed-off-by: Rohit Yadav 

commit f29d8caac8fd1bdf28b4eeed50b804194daef17c
Author: Daan Hoogland 
Date:   2015-11-30T09:49:08Z

Merge release branch 4.6 to master

* 4.6:
  CLOUDSTACK-9083: Add disk serial to kvm virt xml




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

[bhaisaab]

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

https://github.com/apache/cloudstack/pull/768#discussion_r46123680
  
--- Diff: engine/schema/src/com/cloud/upgrade/dao/Upgrade452to460.java ---
@@ -66,10 +66,25 @@ public boolean supportsRollingUpgrade() {
 @Override
 public void performDataMigration(final Connection conn) {
 updateSystemVmTemplates(conn);
+alterAddColumnToCloudUsage(conn);
 updateVMInstanceUserId(conn);
 addIndexForVMInstance(conn);
 }
 
+public void alterAddColumnToCloudUsage(final Connection conn) {
--- End diff --

@abhinandanprateek the only fix needed now is to move this db migration 
from 452to460, to Upgrade460to471 class since we're going to merge on 
4.7/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.
---

[GitHub] cloudstack pull request: libvirt fix forward merge

[bhaisaab]

Github user bhaisaab commented on the pull request:

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

Build failed in Jenkins: simulator-4.5-singlerun #281

[jenkins]

See 

--
Started by upstream project "build-4.5-simulator" build number 335
originally caused by:
 Started by upstream project "build-4.5" build number 543
 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:763)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1012)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1043)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1276)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1738)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
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:1640)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1388)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:62)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:313)
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:120)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
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:1416)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)
at hudson.remoting.Channel.call(Channel.java:781)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor594.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.$Proxy55.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:761)
... 11 more
ERROR: null
[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 process

[GitHub] cloudstack pull request: Quota

[abhinandanprateek]

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

https://github.com/apache/cloudstack/pull/768#discussion_r46124731
  
--- Diff: engine/schema/src/com/cloud/upgrade/dao/Upgrade452to460.java ---
@@ -66,10 +66,25 @@ public boolean supportsRollingUpgrade() {
 @Override
 public void performDataMigration(final Connection conn) {
 updateSystemVmTemplates(conn);
+alterAddColumnToCloudUsage(conn);
 updateVMInstanceUserId(conn);
 addIndexForVMInstance(conn);
 }
 
+public void alterAddColumnToCloudUsage(final Connection conn) {
--- End diff --

Upgrade460to470 as 4.7/master will have the changes


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

[bhaisaab]

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

https://github.com/apache/cloudstack/pull/768#discussion_r46124926
  
--- Diff: engine/schema/src/com/cloud/upgrade/dao/Upgrade452to460.java ---
@@ -66,10 +66,25 @@ public boolean supportsRollingUpgrade() {
 @Override
 public void performDataMigration(final Connection conn) {
 updateSystemVmTemplates(conn);
+alterAddColumnToCloudUsage(conn);
 updateVMInstanceUserId(conn);
 addIndexForVMInstance(conn);
 }
 
+public void alterAddColumnToCloudUsage(final Connection conn) {
--- End diff --

My bad on naming the exact class, but you get the point :)


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

[sebgoa]

Hi folks, we need to resolve this.

1-But I have to start with one comment:
Apache open office releases binaries, users don't compile from source. So it is 
possible within ASF to officially release binaries.

2-We have several initiatives around repos, apt-get.eu (Wido), shapeblue repos, 
Nux mirrors and image templates.
Seems everyone agrees we need a tag team to coordinate all of it and offer a 
unified front.

3-This unified front is great, but it won't happen this week, it will take time 
and dedication.

4-The small issue we are facing is about 3 lines in an HTML file on our 
website. Pierre-Luc and I had a chat Friday, in one of his comments on the PR 
he suggested that we list 3 categories:

- source
- community repo
- 3-rd party repo

I am +1 with this, why ?

-source is a no brainer
- community repo (apt-get) because that's our defacto pkg repo even though we 
don't vote on packages. There was not vote to say these were our community repo 
but that's a fact. Several people have access to the machine and can make 
updates etc...
- 3rd party, allows us to list vendor pkg repo. The more vendors provide 
CloudStack the better. I see it a bit like the "books" discussions we had 
couple years ago. We do not endorse them, but we should promote them.

In our docs however, we should not be referencing 3rd party repos, and any URLs 
should be cloudstack project specific.

Can you please reply with your vote on these 3 categories. I think it's a 
compromise that helps us move forward.

-sebastien



On Nov 27, 2015, at 10:41 AM, Daan Hoogland  wrote:

> On Fri, Nov 27, 2015 at 10:38 AM, Paul Angus 
> wrote:
> 
>> Doesn't that meant that we'll have to vote on the source and the packaged
>> rpms/debs otherwise they we have no official community standing. ?
>> 
> ​I am not sure how we can give them official standing yet but we are the
> apache foundation​, so we vote on source. I would say we vote on the
> packaging software from a different repo then the core+plugins and
> automatically update a repo from that one. The repo will not be endorsed
> but the way it is filled will be.
> 
> my €0,02 of future dreams
> 
> 
> -Original Message-
>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> Sent: 27 November 2015 09:36
>> To: dev 
>> Subject: Re: Package Repositories
>> 
>> On Fri, Nov 27, 2015 at 9:58 AM, Paul Angus 
>> wrote:
>> 
>>> So. My understanding is that to make the packages in the repo 'official'
>>> they must be voted on.  -- would we make the packages what we vote on,
>>> rather that the source code (bearing in mind you can't separate the
>>> packaging in that case).   IMHO, it'll make testing a whole lot simpler
>> for
>>> folks if there is just no requirement to build from source.
>>> 
>> 
>> ​We will not stop voting on the source! Any vote on -, or otherwise
>> handling of packages is a separate thing.​
>> 
> 
> 
> -- 
> Daan

[GitHub] cloudstack pull request: CLOUDSTACK-9077 Fix injectkeys.sh to work...

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/1109#issuecomment-160585862
  
@wido @remibergsma do we want this on 4.5?


---
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-9010: adjust packaging for cen...

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/1008#issuecomment-160588176
  
@davidamorimfaria @remibergsma should we port this to 4.5?


---
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: What SDN are you using?

[Vadim Kimlaychuk]

I don't know if applicable, but I had very good impression from VyOS 
(http://vyos.net/wiki/Main_Page).


Vadim.

On 2015-11-29 20:56, Nux! wrote:


Hello,

So besides the folks using Nicira, can anyone recommend any other SDN 
thing or should I stay with v(x)lans?
I'm kind of removed from this side of things since my deployments tend 
to be with Security Grups in a single or few VLANs, any suggestions 
welcome, preferably free/foss.


Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro [1]




Links:
--
[1] http://www.nux.ro

Re: Package Repositories

[Nux!]

+1 your categories.

Also +1 for the unified thing under cloudstack.apache.org domain.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "sebgoa" 
> To: dev@cloudstack.apache.org
> Sent: Monday, 30 November, 2015 10:08:59
> Subject: Re: Package Repositories

> Hi folks, we need to resolve this.
> 
> 1-But I have to start with one comment:
> Apache open office releases binaries, users don't compile from source. So it 
> is
> possible within ASF to officially release binaries.
> 
> 2-We have several initiatives around repos, apt-get.eu (Wido), shapeblue 
> repos,
> Nux mirrors and image templates.
> Seems everyone agrees we need a tag team to coordinate all of it and offer a
> unified front.
> 
> 3-This unified front is great, but it won't happen this week, it will take 
> time
> and dedication.
> 
> 4-The small issue we are facing is about 3 lines in an HTML file on our 
> website.
> Pierre-Luc and I had a chat Friday, in one of his comments on the PR he
> suggested that we list 3 categories:
> 
> - source
> - community repo
> - 3-rd party repo
> 
> I am +1 with this, why ?
> 
> -source is a no brainer
> - community repo (apt-get) because that's our defacto pkg repo even though we
> don't vote on packages. There was not vote to say these were our community 
> repo
> but that's a fact. Several people have access to the machine and can make
> updates etc...
> - 3rd party, allows us to list vendor pkg repo. The more vendors provide
> CloudStack the better. I see it a bit like the "books" discussions we had
> couple years ago. We do not endorse them, but we should promote them.
> 
> In our docs however, we should not be referencing 3rd party repos, and any 
> URLs
> should be cloudstack project specific.
> 
> Can you please reply with your vote on these 3 categories. I think it's a
> compromise that helps us move forward.
> 
> -sebastien
> 
> 
> 
> On Nov 27, 2015, at 10:41 AM, Daan Hoogland  wrote:
> 
>> On Fri, Nov 27, 2015 at 10:38 AM, Paul Angus 
>> wrote:
>> 
>>> Doesn't that meant that we'll have to vote on the source and the packaged
>>> rpms/debs otherwise they we have no official community standing. ?
>>> 
>> ​I am not sure how we can give them official standing yet but we are the
>> apache foundation​, so we vote on source. I would say we vote on the
>> packaging software from a different repo then the core+plugins and
>> automatically update a repo from that one. The repo will not be endorsed
>> but the way it is filled will be.
>> 
>> my €0,02 of future dreams
>> 
>> 
>> -Original Message-
>>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>>> Sent: 27 November 2015 09:36
>>> To: dev 
>>> Subject: Re: Package Repositories
>>> 
>>> On Fri, Nov 27, 2015 at 9:58 AM, Paul Angus 
>>> wrote:
>>> 
 So. My understanding is that to make the packages in the repo 'official'
 they must be voted on.  -- would we make the packages what we vote on,
 rather that the source code (bearing in mind you can't separate the
 packaging in that case).   IMHO, it'll make testing a whole lot simpler
>>> for
 folks if there is just no requirement to build from source.
 
>>> 
>>> ​We will not stop voting on the source! Any vote on -, or otherwise
>>> handling of packages is a separate thing.​
>>> 
>> 
>> 
>> --
> > Daan

Re: Package Repositories

[Daan Hoogland]

+1 all the way, sebastien

On Mon, Nov 30, 2015 at 11:20 AM, Nux!  wrote:

> +1 your categories.
>
> Also +1 for the unified thing under cloudstack.apache.org domain.
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "sebgoa" 
> > To: dev@cloudstack.apache.org
> > Sent: Monday, 30 November, 2015 10:08:59
> > Subject: Re: Package Repositories
>
> > Hi folks, we need to resolve this.
> >
> > 1-But I have to start with one comment:
> > Apache open office releases binaries, users don't compile from source.
> So it is
> > possible within ASF to officially release binaries.
> >
> > 2-We have several initiatives around repos, apt-get.eu (Wido),
> shapeblue repos,
> > Nux mirrors and image templates.
> > Seems everyone agrees we need a tag team to coordinate all of it and
> offer a
> > unified front.
> >
> > 3-This unified front is great, but it won't happen this week, it will
> take time
> > and dedication.
> >
> > 4-The small issue we are facing is about 3 lines in an HTML file on our
> website.
> > Pierre-Luc and I had a chat Friday, in one of his comments on the PR he
> > suggested that we list 3 categories:
> >
> > - source
> > - community repo
> > - 3-rd party repo
> >
> > I am +1 with this, why ?
> >
> > -source is a no brainer
> > - community repo (apt-get) because that's our defacto pkg repo even
> though we
> > don't vote on packages. There was not vote to say these were our
> community repo
> > but that's a fact. Several people have access to the machine and can make
> > updates etc...
> > - 3rd party, allows us to list vendor pkg repo. The more vendors provide
> > CloudStack the better. I see it a bit like the "books" discussions we had
> > couple years ago. We do not endorse them, but we should promote them.
> >
> > In our docs however, we should not be referencing 3rd party repos, and
> any URLs
> > should be cloudstack project specific.
> >
> > Can you please reply with your vote on these 3 categories. I think it's a
> > compromise that helps us move forward.
> >
> > -sebastien
> >
> >
> >
> > On Nov 27, 2015, at 10:41 AM, Daan Hoogland 
> wrote:
> >
> >> On Fri, Nov 27, 2015 at 10:38 AM, Paul Angus 
> >> wrote:
> >>
> >>> Doesn't that meant that we'll have to vote on the source and the
> packaged
> >>> rpms/debs otherwise they we have no official community standing. ?
> >>>
> >> ​I am not sure how we can give them official standing yet but we are the
> >> apache foundation​, so we vote on source. I would say we vote on the
> >> packaging software from a different repo then the core+plugins and
> >> automatically update a repo from that one. The repo will not be endorsed
> >> but the way it is filled will be.
> >>
> >> my €0,02 of future dreams
> >>
> >>
> >> -Original Message-
> >>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> >>> Sent: 27 November 2015 09:36
> >>> To: dev 
> >>> Subject: Re: Package Repositories
> >>>
> >>> On Fri, Nov 27, 2015 at 9:58 AM, Paul Angus 
> >>> wrote:
> >>>
>  So. My understanding is that to make the packages in the repo
> 'official'
>  they must be voted on.  -- would we make the packages what we vote on,
>  rather that the source code (bearing in mind you can't separate the
>  packaging in that case).   IMHO, it'll make testing a whole lot
> simpler
> >>> for
>  folks if there is just no requirement to build from source.
> 
> >>>
> >>> ​We will not stop voting on the source! Any vote on -, or otherwise
> >>> handling of packages is a separate thing.​
> >>>
> >>
> >>
> >> --
> > > Daan
>



-- 
Daan

[GitHub] cloudstack pull request: CLOUDSTACK-9010: adjust packaging for cen...

[DaanHoogland]

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1008#issuecomment-160589376
  
@bhaisaab I think it is fine to do so, but centos7 support was still 
experimental. Not sure if we spring hopes there that are unjust.


---
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: What SDN are you using?

[Frank Louwers]

Hi Vadim,

Are you using VyOS in a Cloudstack environment?


> On 30 Nov 2015, at 11:20, Vadim Kimlaychuk  wrote:
> 
> I don't know if applicable, but I had very good impression from VyOS 
> (http://vyos.net/wiki/Main_Page).
> 
> Vadim.
> 
> On 2015-11-29 20:56, Nux! wrote:
> 
>> Hello,
>> So besides the folks using Nicira, can anyone recommend any other SDN thing 
>> or should I stay with v(x)lans?
>> I'm kind of removed from this side of things since my deployments tend to be 
>> with Security Grups in a single or few VLANs, any suggestions welcome, 
>> preferably free/foss.
>> Lucian
>> --
>> Sent from the Delta quadrant using Borg technology!
>> Nux!
>> www.nux.ro [1]
> 
> 
> 
> Links:
> --
> [1] http://www.nux.ro

RE: Package Repositories

[Paul Angus]

Sebastien,

Can you confirm that users can expect to find the noredist build of the rpms 
and debs at apt-get.eu ?



[ShapeBlue Ltd]
Paul Angus
VP Technology   ,   ShapeBlue Ltd


s:  02036170528 |  t:  
@cloudyangus   |  m:  +44 
7711418784

e:  paul.an...@shapeblue.com|  
w:  www.shapeblue.com

53 Chandos Place, Covent Garden, London WC2N 4HS. UK


[cid:image3afcee.png@994f8dc6.4db2b336]


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




-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: 30 November 2015 10:24
To: dev 
Subject: Re: Package Repositories

+1 all the way, sebastien

On Mon, Nov 30, 2015 at 11:20 AM, Nux!  wrote:

> +1 your categories.
>
> Also +1 for the unified thing under cloudstack.apache.org domain.
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "sebgoa" 
> > To: dev@cloudstack.apache.org
> > Sent: Monday, 30 November, 2015 10:08:59
> > Subject: Re: Package Repositories
>
> > Hi folks, we need to resolve this.
> >
> > 1-But I have to start with one comment:
> > Apache open office releases binaries, users don't compile from source.
> So it is
> > possible within ASF to officially release binaries.
> >
> > 2-We have several initiatives around repos, apt-get.eu (Wido),
> shapeblue repos,
> > Nux mirrors and image templates.
> > Seems everyone agrees we need a tag team to coordinate all of it and
> offer a
> > unified front.
> >
> > 3-This unified front is great, but it won't happen this week, it
> > will
> take time
> > and dedication.
> >
> > 4-The small issue we are facing is about 3 lines in an HTML file on
> > our
> website.
> > Pierre-Luc and I had a chat Friday, in one of his comments on the PR
> > he suggested that we list 3 categories:
> >
> > - source
> > - community repo
> > - 3-rd party repo
> >
> > I am +1 with this, why ?
> >
> > -source is a no brainer
> > - community repo (apt-get) because that's our defacto pkg repo even
> though we
> > don't vote on packages. There was not vote to say these were our
> community repo
> > but that's a fact. Several people have access to the machine and can
> > make updates etc...
> > - 3rd party, allows us to list vendor pkg repo. The more vendors
> > provide CloudStack the better. I see it a bit like the "books"
> > discussions we had couple years ago. We do not endorse them, but we should 
> > promote them.
> >
> > In our docs however, we should not be referencing 3rd party repos,
> > and
> any URLs
> > should be cloudstack project specific.
> >
> > Can you please reply with your vote on these 3 categories. I think
> > it's a compromise that helps us move forward.
> >
> > -sebastien
> >
> >
> >
> > On Nov 27, 2015, at 10:41 AM, Daan Hoogland
> > 
> wrote:
> >
> >> On Fri, Nov 27, 2015 at 10:38 AM, Paul Angus
> >> 
> >> wrote:
> >>
> >>> Doesn't that meant that we'll have to vote on the source and the
> packaged
> >>> rpms/debs otherwise they we have no official community standing. ?
> >>>
> >> ​I am not sure how we can give them official standing yet but we
> >> are the apache foundation​, so we vote on source. I would say we
> >> vote on the packaging software from a different repo then the
> >> core+plugins and automatically update a repo from that one. The
> >> repo will not be endorsed but the way it is filled will be.
> >>
> >> my €0,02 of future dreams
> >>
> >>
> >> -Original Message-
> >>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> >>> Sent: 27 November 2015 09:36
> >>> To: dev 
> >>> Subject: Re: Package Repositories
> >>>
> >>> On Fri, Nov 27, 2015 at 9:58 AM, Paul Angus
> >>> 
> >>> wrote:
> >>>
>  So. My understanding is that to make the packages in the repo
> 'official'
>  they must be voted on. -- would we make the packages what we
>  vote on, rather that the source code (bearing in mind you can't separate 
>  the
>  packaging

Re: Package Repositories

[Rohit Yadav]

On 30-Nov-2015, at 3:38 PM, sebgoa mailto:run...@gmail.com>> 
wrote:

- source
- community repo
- 3-rd party repo

I am +1 with this, why ?

-source is a no brainer
- community repo (apt-get) because that's our defacto pkg repo even though we 
don't vote on packages. There was not vote to say these were our community repo 
but that's a fact. Several people have access to the machine and can make 
updates etc...
- 3rd party, allows us to list vendor pkg repo. The more vendors provide 
CloudStack the better. I see it a bit like the "books" discussions we had 
couple years ago. We do not endorse them, but we should promote them.

+1 on possibly doing official packages and hosting in future.

-1 on the listings, community repo is 3rd party repo too. With my PMC hat on - 
just because several people from the community are maintaining it should not 
make it blessed unless they are officially voted. Even if half the community 
were to maintain an unofficial repository, it would still be a 3rd party repo.

We should write them like this:

- source
- 3rd party repo (not endorsed by Apache)

Rohit Yadav
Software Architect

[cid:image003.png@01D122E8.F6EFE910]



S: +44 20 3603 0540 | M: +91 88 262 30892

rohit.ya...@shapeblue.com | 
www.shapeblue.com | 
Twitter:@ShapeBlue

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS




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

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

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

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

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

[GitHub] cloudstack pull request: CLOUDSTACK-9010: adjust packaging for cen...

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/1008#issuecomment-160590038
  
@DaanHoogland I see, leaving it then. CentOS7 users should use 4.6/4.7 then.


---
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-4.5-singlerun #282

[jenkins]

See 

--
Started by upstream project "build-4.5-simulator" build number 336
originally caused by:
 Started by upstream project "build-4.5" build number 544
 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:763)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1012)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1043)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1276)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1738)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
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:1640)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1388)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:62)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:313)
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:120)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
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:1416)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)
at hudson.remoting.Channel.call(Channel.java:781)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor594.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.$Proxy55.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:761)
... 11 more
ERROR: null
[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 process

[GitHub] cloudstack pull request: CLOUDSTACK-9092: L10n fix in "Add LDAP Ac...

[milamberspace]

Github user milamberspace commented on the pull request:

https://github.com/apache/cloudstack/pull/1139#issuecomment-160591699
  
Not tested, but code is good.
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: CLOUDSTACK-9010: adjust packaging for cen...

[davidamorimfaria]

Github user davidamorimfaria commented on the pull request:

https://github.com/apache/cloudstack/pull/1008#issuecomment-160594088
  
@bhaisaab I see no harm in trying to package 4.5 with this spec. It should 
just work (read, services start) if all the files expected by the spec file are 
also included in 4.5.



---
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-9095 : Hypervisor changes to s...

[nlivens]

GitHub user nlivens opened a pull request:

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

CLOUDSTACK-9095 : Hypervisor changes to support UserData for Nuage VSP



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

$ git pull https://github.com/nlivens/cloudstack master_nuage

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

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


commit 35d5a2b042ebd8437411773e94da5858f7d3fb8c
Author: Nick Livens 
Date:   2015-11-30T10:32:38Z

CLOUDSTACK-9095 : Hypervisor changes to support UserData for Nuage VSP




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

[sebgoa]

On Nov 30, 2015, at 11:28 AM, Rohit Yadav  wrote:

> 
>> On 30-Nov-2015, at 3:38 PM, sebgoa  wrote:
>> 
>> - source
>> - community repo
>> - 3-rd party repo
>> 
>> I am +1 with this, why ?
>> 
>> -source is a no brainer
>> - community repo (apt-get) because that's our defacto pkg repo even though 
>> we don't vote on packages. There was not vote to say these were our 
>> community repo but that's a fact. Several people have access to the machine 
>> and can make updates etc...
>> - 3rd party, allows us to list vendor pkg repo. The more vendors provide 
>> CloudStack the better. I see it a bit like the "books" discussions we had 
>> couple years ago. We do not endorse them, but we should promote them.
> 
> +1 on possibly doing official packages and hosting in future.
> 
> -1 on the listings, community repo is 3rd party repo too. With my PMC hat on 
> - just because several people from the community are maintaining it should 
> not make it blessed unless they are officially voted. Even if half the 
> community were to maintain an unofficial repository, it would still be a 3rd 
> party repo.
> 
> We should write them like this:
> 
> - source
> - 3rd party repo (not endorsed by Apache)
> 

big -1 on this, that would be even more confusing.

The community repos stand out from any other repos because:

- there are part of the installation docs, and 
- because they have been maintained for several years now.
- they are non-affiliated

The fact that we don't vote on them is really a technicality that we never 
addressed (lacked of time, lack of clear policy etc).

if we can't resolve this then I will be in favor of just listing source 
downloads.


> Rohit Yadav
> Software Architect
> 
> 
> 
> 
> 
> S: +44 20 3603 0540 | M: +91 88 262 30892 
> 
> rohit.ya...@shapeblue.com | www.shapeblue.com | Twitter:@ShapeBlue
> 
> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
> 
> 
> 
> 
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design & Build
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software Engineering
> CloudStack Infrastructure Support
> CloudStack Bootcamp Training Courses
> 
> This email and any attachments to it may be confidential and are intended 
> solely for the use of the individual to whom it is addressed. Any views or 
> opinions expressed are solely those of the author and do not necessarily 
> represent those of Shape Blue Ltd or related companies. If you are not the 
> intended recipient of this email, you must neither take any action based upon 
> its contents, nor copy or show it to anyone. Please contact the sender if you 
> believe you have received this email in error. Shape Blue Ltd is a company 
> incorporated in England & Wales. ShapeBlue Services India LLP is a company 
> incorporated in India and is operated under license from Shape Blue Ltd. 
> Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
> operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
> registered by The Republic of South Africa and is traded under license from 
> Shape Blue Ltd. ShapeBlue is a registered trademark.
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design & Build
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software Engineering
> CloudStack Infrastructure Support
> CloudStack Bootcamp Training Courses
> 
> This email and any attachments to it may be confidential and are intended 
> solely for the use of the individual to whom it is addressed. Any views or 
> opinions expressed are solely those of the author and do not necessarily 
> represent those of Shape Blue Ltd or related companies. If you are not the 
> intended recipient of this email, you must neither take any action based upon 
> its contents, nor copy or show it to anyone. Please contact the sender if you 
> believe you have received this email in error. Shape Blue Ltd is a company 
> incorporated in England & Wales. ShapeBlue Services India LLP is a company 
> incorporated in India and is operated under license from Shape Blue Ltd. 
> Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
> operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
> registered by The Republic of South Africa and is traded under license from 
> Shape Blue Ltd. ShapeBlue is a registered trademark.

[GitHub] cloudstack pull request: CLOUDSTACK-9010: adjust packaging for cen...

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/1008#issuecomment-160599550
  
@davidamorimfaria thanks, I personally won't be able to fix/test this 
soonish so dropping this unless of course you or someone wants this in 4.5 and 
sends a 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.
---

Re: What SDN are you using?

[Vadim Kimlaychuk]

We have been using it at our DEV cloud around year ago. Now we are out 
or resources so dev- environment is destroyed.


Vadim.

On 2015-11-30 12:24, Frank Louwers wrote:


Hi Vadim,

Are you using VyOS in a Cloudstack environment?

On 30 Nov 2015, at 11:20, Vadim Kimlaychuk  wrote:

I don't know if applicable, but I had very good impression from VyOS 
(http://vyos.net/wiki/Main_Page [1]).


Vadim.

On 2015-11-29 20:56, Nux! wrote:

Hello,
So besides the folks using Nicira, can anyone recommend any other SDN 
thing or should I stay with v(x)lans?
I'm kind of removed from this side of things since my deployments tend 
to be with Security Grups in a single or few VLANs, any suggestions 
welcome, preferably free/foss.

Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro [2] [1 [2]]

Links:
--
[1] http://www.nux.ro [2]




Links:
--
[1] http://vyos.net/wiki/Main_Page
[2] http://www.nux.ro

[GitHub] cloudstack pull request: Removed the PlannerBase class because it ...

[wido]

Github user wido commented on the pull request:

https://github.com/apache/cloudstack/pull/1108#issuecomment-160599664
  
Code seems good, waiting for @borisroman to come up with test results


---
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-9080: Resource limits for Prim...

[wido]

Github user wido commented on the pull request:

https://github.com/apache/cloudstack/pull/1107#issuecomment-160600074
  
The fix seems good to me. I can't run the Marvin tests, but it looks good 
to me


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

[poll] cloudstack exam

[Giles Sirett]

Quick poll: has anybody here taken the ACCEL cloudstack certification exam ? 
what did you think ? Too hard, too easy ? – about right ?

Also, by way of reminder: if you use the code  ACCELpromocodeASF when 
registering for the exam, 1/3 of the fee goes to the ACS project

Kind Regards
Giles

Giles Sirett
CEO

[cid:image003.png@01D104EF.CE276C40]

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

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


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

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

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

[Nux!]

Hello Vadim,

How exactly are you integrating VyOS in Cloudstack? We're also using it 
internally, but not sure how it would help us, especially with regards to SDN.

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Vadim Kimlaychuk" 
> To: dev@cloudstack.apache.org
> Cc: us...@cloudstack.apache.org, "Nux!" 
> Sent: Monday, 30 November, 2015 11:09:18
> Subject: Re: What SDN are you using?

> We have been using it at our DEV cloud around year ago. Now we are out
> or resources so dev- environment is destroyed.
> 
> Vadim.
> 
> On 2015-11-30 12:24, Frank Louwers wrote:
> 
>> Hi Vadim,
>> 
>> Are you using VyOS in a Cloudstack environment?
>> 
>> On 30 Nov 2015, at 11:20, Vadim Kimlaychuk  wrote:
>> 
>> I don't know if applicable, but I had very good impression from VyOS
>> (http://vyos.net/wiki/Main_Page [1]).
>> 
>> Vadim.
>> 
>> On 2015-11-29 20:56, Nux! wrote:
>> 
>> Hello,
>> So besides the folks using Nicira, can anyone recommend any other SDN
>> thing or should I stay with v(x)lans?
>> I'm kind of removed from this side of things since my deployments tend
>> to be with Security Grups in a single or few VLANs, any suggestions
>> welcome, preferably free/foss.
>> Lucian
>> --
>> Sent from the Delta quadrant using Borg technology!
>> Nux!
>> www.nux.ro [2] [1 [2]]
>> 
>> Links:
>> --
>> [1] http://www.nux.ro [2]
> 
> 
> 
> Links:
> --
> [1] http://vyos.net/wiki/Main_Page
> [2] http://www.nux.ro

Re: What SDN are you using?

[Vadim Kimlaychuk]

We mostly use it as external (to Cloudstack) intelligent switch/router, 
but also installed it as guest VM within cloud to provide customized SDN 
functionality.


Vadim.

On 2015-11-30 13:10, Nux! wrote:


Hello Vadim,

How exactly are you integrating VyOS in Cloudstack? We're also using it 
internally, but not sure how it would help us, especially with regards 
to SDN.


Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro [1]

- Original Message -


From: "Vadim Kimlaychuk" 
To: dev@cloudstack.apache.org
Cc: us...@cloudstack.apache.org, "Nux!" 
Sent: Monday, 30 November, 2015 11:09:18
Subject: Re: What SDN are you using?


We have been using it at our DEV cloud around year ago. Now we are out
or resources so dev- environment is destroyed.

Vadim.

On 2015-11-30 12:24, Frank Louwers wrote:

Hi Vadim,

Are you using VyOS in a Cloudstack environment?

On 30 Nov 2015, at 11:20, Vadim Kimlaychuk  wrote:

I don't know if applicable, but I had very good impression from VyOS
(http://vyos.net/wiki/Main_Page [2] [1 [2]]).

Vadim.

On 2015-11-29 20:56, Nux! wrote:

Hello,
So besides the folks using Nicira, can anyone recommend any other SDN
thing or should I stay with v(x)lans?
I'm kind of removed from this side of things since my deployments tend
to be with Security Grups in a single or few VLANs, any suggestions
welcome, preferably free/foss.
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro [1] [2 [1]] [1 [2]]

Links:
--
[1] http://www.nux.ro [1] [2 [1]]

Links:
--
[1] http://vyos.net/wiki/Main_Page [2]
[2] http://www.nux.ro [1]




Links:
--
[1] http://www.nux.ro
[2] http://vyos.net/wiki/Main_Page

[GitHub] cloudstack pull request: CID-1338387: Deletion of method endPointS...

[rafaelweingartner]

Github user rafaelweingartner commented on the pull request:

https://github.com/apache/cloudstack/pull/1124#issuecomment-160603505
  
I was thinking about that. Starting in January we will have some extra 
time, then we might have a look at 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: Package Repositories

[Rajani Karuturi]

+1 on the categories.

~Rajani

On Mon, Nov 30, 2015 at 3:38 PM, sebgoa  wrote:

> Hi folks, we need to resolve this.
>
> 1-But I have to start with one comment:
> Apache open office releases binaries, users don't compile from source. So
> it is possible within ASF to officially release binaries.
>
> 2-We have several initiatives around repos, apt-get.eu (Wido), shapeblue
> repos, Nux mirrors and image templates.
> Seems everyone agrees we need a tag team to coordinate all of it and offer
> a unified front.
>
> 3-This unified front is great, but it won't happen this week, it will take
> time and dedication.
>
> 4-The small issue we are facing is about 3 lines in an HTML file on our
> website. Pierre-Luc and I had a chat Friday, in one of his comments on the
> PR he suggested that we list 3 categories:
>
> - source
> - community repo
> - 3-rd party repo
>
> I am +1 with this, why ?
>
> -source is a no brainer
> - community repo (apt-get) because that's our defacto pkg repo even though
> we don't vote on packages. There was not vote to say these were our
> community repo but that's a fact. Several people have access to the machine
> and can make updates etc...
> - 3rd party, allows us to list vendor pkg repo. The more vendors provide
> CloudStack the better. I see it a bit like the "books" discussions we had
> couple years ago. We do not endorse them, but we should promote them.
>
> In our docs however, we should not be referencing 3rd party repos, and any
> URLs should be cloudstack project specific.
>
> Can you please reply with your vote on these 3 categories. I think it's a
> compromise that helps us move forward.
>
> -sebastien
>
>
>
> On Nov 27, 2015, at 10:41 AM, Daan Hoogland 
> wrote:
>
> > On Fri, Nov 27, 2015 at 10:38 AM, Paul Angus 
> > wrote:
> >
> >> Doesn't that meant that we'll have to vote on the source and the
> packaged
> >> rpms/debs otherwise they we have no official community standing. ?
> >>
> > ​I am not sure how we can give them official standing yet but we are the
> > apache foundation​, so we vote on source. I would say we vote on the
> > packaging software from a different repo then the core+plugins and
> > automatically update a repo from that one. The repo will not be endorsed
> > but the way it is filled will be.
> >
> > my €0,02 of future dreams
> >
> >
> > -Original Message-
> >> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> >> Sent: 27 November 2015 09:36
> >> To: dev 
> >> Subject: Re: Package Repositories
> >>
> >> On Fri, Nov 27, 2015 at 9:58 AM, Paul Angus 
> >> wrote:
> >>
> >>> So. My understanding is that to make the packages in the repo
> 'official'
> >>> they must be voted on.  -- would we make the packages what we vote on,
> >>> rather that the source code (bearing in mind you can't separate the
> >>> packaging in that case).   IMHO, it'll make testing a whole lot simpler
> >> for
> >>> folks if there is just no requirement to build from source.
> >>>
> >>
> >> ​We will not stop voting on the source! Any vote on -, or otherwise
> >> handling of packages is a separate thing.​
> >>
> >
> >
> > --
> > Daan
>
>

[GitHub] cloudstack pull request: CLOUDSTACK-9074: Support shared networkin...

[nvazquez]

Github user nvazquez commented on the pull request:

https://github.com/apache/cloudstack/pull/1094#issuecomment-160636372
  
@miguelaferreira thanks for reviewing! Sure, would be great to discuss them


---
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-6276 Fixing affinity groups fo...

[pdube]

Github user pdube commented on the pull request:

https://github.com/apache/cloudstack/pull/1134#issuecomment-160638862
  
@DaanHoogland Ok, I understand what you mean. I do think that we need some 
clarifications on what the standards are (search vs list, service vs query vs 
dao, etc.) PS: I was not taking it that way :)


---
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-9074: Support shared networkin...

[nvazquez]

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

https://github.com/apache/cloudstack/pull/1094#discussion_r46148014
  
--- Diff: 
api/src/com/cloud/network/guru/NetworkGuruAdditionalFunctions.java ---
@@ -0,0 +1,12 @@
+package com.cloud.network.guru;
+
+import java.util.Map;
+
+public interface NetworkGuruAdditionalFunctions {
--- End diff --

I agree. This was the "best" solution I found, maybe for my lack CS 
architecture knowledge. This was the problem that I faced:
I needed to call this functions from NetworkOrchestrator. However, from 
NetworkOrchestrator I could access NetworkGuru interface, so I decided not to 
include this methods in NetworkGuru interface, implementing them blank in every 
guru except in NiciraNvpGuestNetworkGuru. I decided to create this interface, 
only implemented by NiciraNvpGuestNetworkGuru just to avoid doing that.

In NetworkOrchestrator, line 682 I made a call to one of this functions. 
How can I improve this solution?


---
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-9074: Support shared networkin...

[nvazquez]

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

https://github.com/apache/cloudstack/pull/1094#discussion_r46148337
  
--- Diff: setup/db/db/schema-460to470.sql ---
@@ -18,3 +18,5 @@
 --;
 -- Schema upgrade from 4.6.0 to 4.7.0;
 --;
+
+ALTER TABLE `cloud`.`nicira_nvp_router_map` DROP INDEX 
`logicalrouter_uuid` ;
--- End diff --

Right. As many networks can now connect to the same logical router


---
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-9074: Support shared networkin...

[nvazquez]

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

https://github.com/apache/cloudstack/pull/1094#discussion_r46148362
  
--- Diff: setup/db/db/schema-461to470.sql ---
@@ -18,3 +18,5 @@
 --;
 -- Schema upgrade from 4.6.1 to 4.7.0;
 --;
+
+ALTER TABLE `cloud`.`nicira_nvp_router_map` DROP INDEX 
`logicalrouter_uuid` ;
--- End diff --

Right. As many networks can now connect to the same logical router


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

[Pierre-Luc Dion]

Hi all,

So just to make this email smaller, it will be strait...

All discussions around repos is not a rant on Shapeblue where you guys are
doing a super job on maintaining the community and the project. This as to
do only with installation instructions of an opensource project where repos
from installation instruction keep changing from a generic (pub free
url)[1] to a url that look like a commercially supported product [2], it's
just that.

I don't see why we should have a separate vote on a binary version from the
voted source? and why not consider the repo on cloudstack.apt-get.eu as
different then 3rd party, because it is part of the installation
instruction (and we need instruction from binaries), it is also maintain by
the community.

It would definitely make more sense to use packages.apache.org or
cloudstack.apache.org/packages.

Paul, as far as releases I know, package on cloudstack.apt-get.eu include
noredis libraries.


[1]
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.6.0/upgrade/upgrade-4.4.html#cloudstack-rpm-repository
[2]
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.5.2/upgrade/upgrade-4.4.html#cloudstack-rpm-repository

Here is some other confusions examples from the mailing list:
- http://markmail.org/thread/xor6maadmwl2hnas
- http://markmail.org/thread/f4xidv6rq2anyv26

If we agree on categories I can submit a new PR for the download page.

Regards,


PL

On Mon, Nov 30, 2015 at 6:24 AM, Rajani Karuturi  wrote:

> +1 on the categories.
>
> ~Rajani
>
> On Mon, Nov 30, 2015 at 3:38 PM, sebgoa  wrote:
>
> > Hi folks, we need to resolve this.
> >
> > 1-But I have to start with one comment:
> > Apache open office releases binaries, users don't compile from source. So
> > it is possible within ASF to officially release binaries.
> >
> > 2-We have several initiatives around repos, apt-get.eu (Wido), shapeblue
> > repos, Nux mirrors and image templates.
> > Seems everyone agrees we need a tag team to coordinate all of it and
> offer
> > a unified front.
> >
> > 3-This unified front is great, but it won't happen this week, it will
> take
> > time and dedication.
> >
> > 4-The small issue we are facing is about 3 lines in an HTML file on our
> > website. Pierre-Luc and I had a chat Friday, in one of his comments on
> the
> > PR he suggested that we list 3 categories:
> >
> > - source
> > - community repo
> > - 3-rd party repo
> >
> > I am +1 with this, why ?
> >
> > -source is a no brainer
> > - community repo (apt-get) because that's our defacto pkg repo even
> though
> > we don't vote on packages. There was not vote to say these were our
> > community repo but that's a fact. Several people have access to the
> machine
> > and can make updates etc...
> > - 3rd party, allows us to list vendor pkg repo. The more vendors provide
> > CloudStack the better. I see it a bit like the "books" discussions we had
> > couple years ago. We do not endorse them, but we should promote them.
> >
> > In our docs however, we should not be referencing 3rd party repos, and
> any
> > URLs should be cloudstack project specific.
> >
> > Can you please reply with your vote on these 3 categories. I think it's a
> > compromise that helps us move forward.
> >
> > -sebastien
> >
> >
> >
> > On Nov 27, 2015, at 10:41 AM, Daan Hoogland 
> > wrote:
> >
> > > On Fri, Nov 27, 2015 at 10:38 AM, Paul Angus  >
> > > wrote:
> > >
> > >> Doesn't that meant that we'll have to vote on the source and the
> > packaged
> > >> rpms/debs otherwise they we have no official community standing. ?
> > >>
> > > ​I am not sure how we can give them official standing yet but we are
> the
> > > apache foundation​, so we vote on source. I would say we vote on the
> > > packaging software from a different repo then the core+plugins and
> > > automatically update a repo from that one. The repo will not be
> endorsed
> > > but the way it is filled will be.
> > >
> > > my €0,02 of future dreams
> > >
> > >
> > > -Original Message-
> > >> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> > >> Sent: 27 November 2015 09:36
> > >> To: dev 
> > >> Subject: Re: Package Repositories
> > >>
> > >> On Fri, Nov 27, 2015 at 9:58 AM, Paul Angus  >
> > >> wrote:
> > >>
> > >>> So. My understanding is that to make the packages in the repo
> > 'official'
> > >>> they must be voted on.  -- would we make the packages what we vote
> on,
> > >>> rather that the source code (bearing in mind you can't separate the
> > >>> packaging in that case).   IMHO, it'll make testing a whole lot
> simpler
> > >> for
> > >>> folks if there is just no requirement to build from source.
> > >>>
> > >>
> > >> ​We will not stop voting on the source! Any vote on -, or otherwise
> > >> handling of packages is a separate thing.​
> > >>
> > >
> > >
> > > --
> > > Daan
> >
> >
>

New Defects reported by Coverity Scan for cloudstack

[scan-admin]

Hi,

Please find the latest report on new defect(s) introduced to cloudstack found 
with Coverity Scan.

2 new defect(s) introduced to cloudstack found with Coverity Scan.
4 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent 
build analyzed by Coverity Scan.

New defect(s) Reported-by: Coverity Scan
Showing 2 of 2 defect(s)


** CID 1341073:  Null pointer dereferences  (FORWARD_NULL)
/server/src/com/cloud/api/ApiServer.java: 676 in 
com.cloud.api.ApiServer.queueCommand(org.apache.cloudstack.api.BaseCmd, 
java.util.Map, java.lang.StringBuilder)()



*** CID 1341073:  Null pointer dereferences  (FORWARD_NULL)
/server/src/com/cloud/api/ApiServer.java: 676 in 
com.cloud.api.ApiServer.queueCommand(org.apache.cloudstack.api.BaseCmd, 
java.util.Map, java.lang.StringBuilder)()
670 Long instanceId = (objectId == null) ? 
asyncCmd.getInstanceId() : objectId;
671 
672 // users can provide the job id they want to use, so log as 
it is a uuid and is unique
673 String injectedJobId = asyncCmd.getInjectedJobId();
674 _uuidMgr.checkUuidSimple(injectedJobId, AsyncJob.class);
675 
>>> CID 1341073:  Null pointer dereferences  (FORWARD_NULL)
>>> Calling a method on null object "caller".
676 AsyncJobVO job = new AsyncJobVO("", callerUserId, 
caller.getId(), cmdObj.getClass().getName(),
677 ApiGsonHelper.getBuilder().create().toJson(params), 
instanceId,
678 asyncCmd.getInstanceType() != null ? 
asyncCmd.getInstanceType().toString() : null,
679 injectedJobId);
680 job.setDispatcher(_asyncDispatcher.getName());
681 

** CID 1341076:  Control flow issues  (DEADCODE)
/server/src/com/cloud/api/ApiServer.java: 658 in 
com.cloud.api.ApiServer.queueCommand(org.apache.cloudstack.api.BaseCmd, 
java.util.Map, java.lang.StringBuilder)()



*** CID 1341076:  Control flow issues  (DEADCODE)
/server/src/com/cloud/api/ApiServer.java: 658 in 
com.cloud.api.ApiServer.queueCommand(org.apache.cloudstack.api.BaseCmd, 
java.util.Map, java.lang.StringBuilder)()
652 }
653 
654 long startEventId = ctx.getStartEventId();
655 asyncCmd.setStartEventId(startEventId);
656 
657 // save the scheduled event
>>> CID 1341076:  Control flow issues  (DEADCODE)
>>> Execution cannot reach this expression "1L" inside statement "eventId = 
>>> com.cloud.event.A...".
658 final Long eventId =
659 
ActionEventUtils.onScheduledActionEvent((callerUserId == null) ? 
(Long)User.UID_SYSTEM : callerUserId, asyncCmd.getEntityOwnerId(), 
asyncCmd.getEventType(),
660 asyncCmd.getEventDescription(), 
asyncCmd.isDisplay(), startEventId);
661 if (startEventId == 0) {
662 // There was no create event before, set current event 
id as start eventId
663 startEventId = eventId;



To view the defects in Coverity Scan visit, 
https://scan.coverity.com/projects/cloudstack?tab=overview

To manage Coverity Scan email notifications for "dev@cloudstack.apache.org", 
click 
https://scan.coverity.com/subscriptions/edit?email=dev%40cloudstack.apache.org&token=494aabd5ba647999fa41b6d766646231

Re: What SDN are you using?

[Simon Weller]

> We have the native KVM VXLAN implementation running in our lab and it seems 
> to work very well. We went 100% >10/40GB using open platform switches and 
> Cumulus linux.

>Good to know.

On the subject of VXLAN on KVM, note that is does not use Openvswitch. 
Openvswitch doesn't support multicast VXLAN, so it's not a complete 
implementation. Full native VXLAN support was added to the linux kernel, so the 
current support in CS is using the linux native implementation.

- Si

Re: What SDN are you using?

[Nux!]

Simon,

To clarify, we're talking about this implementation, right?
https://issues.apache.org/jira/browse/CLOUDSTACK-2328

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Simon Weller" 
> To: dev@cloudstack.apache.org, "Kuangching Wang" , 
> us...@cloudstack.apache.org
> Sent: Monday, 30 November, 2015 13:18:15
> Subject: Re: What SDN are you using?

> 
> 
>> We have the native KVM VXLAN implementation running in our lab and it seems 
>> to
>> work very well. We went 100% >10/40GB using open platform switches and 
>> Cumulus
>> linux.
> 
>>Good to know.
> 
> On the subject of VXLAN on KVM, note that is does not use Openvswitch.
> Openvswitch doesn't support multicast VXLAN, so it's not a complete
> implementation. Full native VXLAN support was added to the linux kernel, so 
> the
> current support in CS is using the linux native implementation.
> 
> - Si
> 
> 

[GitHub] cloudstack pull request: CLOUDSTACK-8818: Use MySQL native connect...

[wido]

Github user wido commented on the pull request:

https://github.com/apache/cloudstack/pull/1054#issuecomment-160648931
  
@borisroman @DaanHoogland Anybody else? :)


---
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-8715: Add VirtIO channel to al...

[wido]

Github user wido commented on the pull request:

https://github.com/apache/cloudstack/pull/985#issuecomment-160649027
  
Still working on this one. However, I need to get stuff into libvirt-java 
upstream. Working on that here: 
https://github.com/wido/libvirt-java/commits/qemu-guest-command


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

[Wido den Hollander]

On 30-11-15 15:29, Pierre-Luc Dion wrote:
> Hi all,
> 
> So just to make this email smaller, it will be strait...
> 
> All discussions around repos is not a rant on Shapeblue where you guys are
> doing a super job on maintaining the community and the project. This as to
> do only with installation instructions of an opensource project where repos
> from installation instruction keep changing from a generic (pub free
> url)[1] to a url that look like a commercially supported product [2], it's
> just that.
> 

I've been quit on this discussion because it's imho just that. I came up
with the repo a long time ago since there was none. For the end-user we
wanted repositories and we build them.

> I don't see why we should have a separate vote on a binary version from the
> voted source? and why not consider the repo on cloudstack.apt-get.eu as
> different then 3rd party, because it is part of the installation
> instruction (and we need instruction from binaries), it is also maintain by
> the community.
> 

True. It's that I host the machine, I don't own it. Multiple people have
access to the machine.

> It would definitely make more sense to use packages.apache.org or
> cloudstack.apache.org/packages.
> 

Yes, packages.cloudstack.org would be great! If we could have somebody
CNAME it to cloudstack.apt-get.eu it would be even more awesome.

> Paul, as far as releases I know, package on cloudstack.apt-get.eu include
> noredis libraries.
> 

The debs don't I think. I never checked the RPMs.

Wido

> 
> [1]
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.6.0/upgrade/upgrade-4.4.html#cloudstack-rpm-repository
> [2]
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.5.2/upgrade/upgrade-4.4.html#cloudstack-rpm-repository
> 
> Here is some other confusions examples from the mailing list:
> - http://markmail.org/thread/xor6maadmwl2hnas
> - http://markmail.org/thread/f4xidv6rq2anyv26
> 
> If we agree on categories I can submit a new PR for the download page.
> 
> Regards,
> 
> 
> PL
> 
> On Mon, Nov 30, 2015 at 6:24 AM, Rajani Karuturi  wrote:
> 
>> +1 on the categories.
>>
>> ~Rajani
>>
>> On Mon, Nov 30, 2015 at 3:38 PM, sebgoa  wrote:
>>
>>> Hi folks, we need to resolve this.
>>>
>>> 1-But I have to start with one comment:
>>> Apache open office releases binaries, users don't compile from source. So
>>> it is possible within ASF to officially release binaries.
>>>
>>> 2-We have several initiatives around repos, apt-get.eu (Wido), shapeblue
>>> repos, Nux mirrors and image templates.
>>> Seems everyone agrees we need a tag team to coordinate all of it and
>> offer
>>> a unified front.
>>>
>>> 3-This unified front is great, but it won't happen this week, it will
>> take
>>> time and dedication.
>>>
>>> 4-The small issue we are facing is about 3 lines in an HTML file on our
>>> website. Pierre-Luc and I had a chat Friday, in one of his comments on
>> the
>>> PR he suggested that we list 3 categories:
>>>
>>> - source
>>> - community repo
>>> - 3-rd party repo
>>>
>>> I am +1 with this, why ?
>>>
>>> -source is a no brainer
>>> - community repo (apt-get) because that's our defacto pkg repo even
>> though
>>> we don't vote on packages. There was not vote to say these were our
>>> community repo but that's a fact. Several people have access to the
>> machine
>>> and can make updates etc...
>>> - 3rd party, allows us to list vendor pkg repo. The more vendors provide
>>> CloudStack the better. I see it a bit like the "books" discussions we had
>>> couple years ago. We do not endorse them, but we should promote them.
>>>
>>> In our docs however, we should not be referencing 3rd party repos, and
>> any
>>> URLs should be cloudstack project specific.
>>>
>>> Can you please reply with your vote on these 3 categories. I think it's a
>>> compromise that helps us move forward.
>>>
>>> -sebastien
>>>
>>>
>>>
>>> On Nov 27, 2015, at 10:41 AM, Daan Hoogland 
>>> wrote:
>>>
 On Fri, Nov 27, 2015 at 10:38 AM, Paul Angus >>
 wrote:

> Doesn't that meant that we'll have to vote on the source and the
>>> packaged
> rpms/debs otherwise they we have no official community standing. ?
>
 ​I am not sure how we can give them official standing yet but we are
>> the
 apache foundation​, so we vote on source. I would say we vote on the
 packaging software from a different repo then the core+plugins and
 automatically update a repo from that one. The repo will not be
>> endorsed
 but the way it is filled will be.

 my €0,02 of future dreams


 -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: 27 November 2015 09:36
> To: dev 
> Subject: Re: Package Repositories
>
> On Fri, Nov 27, 2015 at 9:58 AM, Paul Angus >>
> wrote:
>
>> So. My understanding is that to make the packages in the repo
>>> 'official'
>> they must be voted on.  -- would we make the packages 

[GitHub] cloudstack pull request: CLOUDSTACK-8715: Add VirtIO channel to al...

[NuxRo]

Github user NuxRo commented on the pull request:

https://github.com/apache/cloudstack/pull/985#issuecomment-160654716
  
Ok, godspeed.
 With a bit of luck perhaps we'll see this somewhere in 4.7.x?


---
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: What SDN are you using?

[Simon Weller]

>
>From: Nux! 
>Sent: Monday, November 30, 2015 8:39 AM
>To: dev@cloudstack.apache.org
>Cc: Kuangching Wang; us...@cloudstack.apache.org
>Subject: Re: What SDN are you using?
>
>Simon,
>
>To clarify, we're talking about this implementation, right?
>https://issues.apache.org/jira/browse/CLOUDSTACK-2328

Yes, correct.

[GitHub] cloudstack pull request: Show Agent name in Ping response

[wido]

GitHub user wido opened a pull request:

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

Show Agent name in Ping response

Before:

DEBUG [c.c.a.m.AgentManagerImpl] (AgentManager-Handler-4:null) Ping 
from 66

After:

DEBUG [c.c.a.m.AgentManagerImpl] (AgentManager-Handler-4:null) Ping 
from 66 (n01)

Makes it easier to search for hosts in the logs. Most loglines contain both 
the hostId and hostName.

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

$ git pull https://github.com/wido/cloudstack agent-ping-name

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

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


commit da85e9861a876de2dd8b1be1dde86469bda8a33b
Author: Wido den Hollander 
Date:   2015-11-30T15:13:45Z

Show Agent name in Ping response




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

[Daan Hoogland]

On Mon, Nov 30, 2015 at 3:38 PM, Wido den Hollander  wrote:

> > Paul, as far as releases I know, package on cloudstack.apt-get.eu
> include
> > noredis libraries.
> >
>
> The debs don't I think. I never checked the RPMs.


​Any RPMs I uploaded do. Those are mostly the 4.4 ones (not sure but I
think the 4.3 ones as well).​



-- 
Daan

Re: Package Repositories

[Nux!]

BTW, if these bits are "no redistribute", why are we distributing them?

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Daan Hoogland" 
> To: "dev" 
> Sent: Monday, 30 November, 2015 15:28:24
> Subject: Re: Package Repositories

> On Mon, Nov 30, 2015 at 3:38 PM, Wido den Hollander  wrote:
> 
>> > Paul, as far as releases I know, package on cloudstack.apt-get.eu
>> include
>> > noredis libraries.
>> >
>>
>> The debs don't I think. I never checked the RPMs.
> 
> 
> ​Any RPMs I uploaded do. Those are mostly the 4.4 ones (not sure but I
> think the 4.3 ones as well).​
> 
> 
> 
> --
> Daan

[GitHub] cloudstack pull request: CLOUDSTACK-9074: Support shared networkin...

[nvazquez]

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

https://github.com/apache/cloudstack/pull/1094#discussion_r46159749
  
--- Diff: api/src/com/cloud/network/Networks.java ---
@@ -251,6 +252,10 @@ public static URI fromString(String candidate) {
 if 
(com.cloud.dc.Vlan.UNTAGGED.equalsIgnoreCase(candidate)) {
 return Native.toUri(candidate);
 }
+if (UuidUtils.validateUUID(candidate)){
+//Supporting lswitch uuid as vlan id: set 
broadcast_uri = null and add row on nicira_nvp_router_map with 
logicalrouter_uuid = candidate
+return null;
--- End diff --

The idea is to support creating Shared Networks over NSX Managed Network 
Offering, so there will be this two cases (for creation):
* Providing numerical VLAN_ID:
 * broadcastdomain_type = Lswitch
 * broadcast_uri = "vlan://VLAN_ID"
* Providing logical router UUID as VLAN_ID:
 * broadcastdomain_type = Lswitch
 * broadcast_uri = NULL
 * add entry on nicira_nvp_router_map with network id and logical router's 
UUID

For second case, I included the code in the catch block as I asumed that 
VLAN_ID provided is not numerical (as long parsing fail). 


---
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: Show Agent name in Ping response

[ustcweizhou]

Github user ustcweizhou commented on the pull request:

https://github.com/apache/cloudstack/pull/1143#issuecomment-160670527
  
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: Show Agent name in Ping response

[pdube]

Github user pdube commented on the pull request:

https://github.com/apache/cloudstack/pull/1143#issuecomment-160674157
  
LGTM, but consider using the default log4j formatter. ex:
`logger.debug("Ping from {} ({})", hostid, hostname);`
and extracting the message to a constant


---
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: Show Agent name in Ping response

[wido]

Github user wido commented on the pull request:

https://github.com/apache/cloudstack/pull/1143#issuecomment-160679884
  
@pdube Thanks! I didn't know that existed :)


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

[sebgoa]

On Nov 30, 2015, at 4:39 PM, Nux!  wrote:

> BTW, if these bits are "no redistribute", why are we distributing them?

This is really a case of evolution and expectation.

When Wido started this, these pkgs were not sanctioned by the *project*, hence 
non-official release pkgs and not voted on.

This is still the case.

We called this pkg repo the "community" repo because they are maintained by 
community members but not sanctioned by a vote by the project and hence to this 
point, not official ASF releases.

These are convenience pkgs.

It seems that it might be the time to work on figuring out how to offer 
official pkg, meaning sanctioned by a vote on dev@.

Until we establish this process and actually do a release, this repo remains a 
community repo (which does not imply that they are official pkg).

The only difference I make between apt-get.eu and shapeblue repo is that the 
apt-get has folks from different affiliation with access to the machine. Even 
though the shapeblue repo is also maintained by committers.

This discussion is all good for the project, so let's not try to create any 
type of conflict here.

Now that we have a second pkg repo to list on the download page this is forcing 
us to (re) think what deem a "community" repo and most possibly work towards 
official pkgs.

To re-iterate my take on this, we are going to have a period of time where we 
still have the community repo (called like this historically) + shapeblue repo 
until we potentially unify them of list them with a proper term.

This is why I proposed:

1-source release (official)
2-community repo (non-official)
3-third party (non-official, with single affiliation of people who have access).

** We just need a simple, acceptable naming for the download page for a 
transitory period **

Ps: certainly things could get a bit more complicated if people outside 
shapeblue had access to this repo.

> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> - Original Message -
>> From: "Daan Hoogland" 
>> To: "dev" 
>> Sent: Monday, 30 November, 2015 15:28:24
>> Subject: Re: Package Repositories
> 
>> On Mon, Nov 30, 2015 at 3:38 PM, Wido den Hollander  wrote:
>> 
 Paul, as far as releases I know, package on cloudstack.apt-get.eu
>>> include
 noredis libraries.
 
>>> 
>>> The debs don't I think. I never checked the RPMs.
>> 
>> 
>> ​Any RPMs I uploaded do. Those are mostly the 4.4 ones (not sure but I
>> think the 4.3 ones as well).​
>> 
>> 
>> 
>> --
>> Daan

Re: Package Repositories

[sebgoa]

On Nov 30, 2015, at 11:28 AM, Paul Angus  wrote:

> Sebastien,
> 
> Can you confirm that users can expect to find the noredist build of the rpms 
> and debs at apt-get.eu ?
> 

I don't know

What I understood from Rohit, is that the "shapeblue" repo also contains pkgs 
that are hot-fixed and have features back ported.
In that sense it is quite a different repo than apt-get which only has pkg for 
each release.


> 
> 
>   
> Paul Angus
> VP Technology  ,   ShapeBlue Ltd
> s:02036170528   |  t: @cloudyangus  |  m: +44 
> 7711418784
> e:paul.an...@shapeblue.com  |  w: www.shapeblue.com
>53 Chandos Place, Covent Garden, London WC2N 4HS. UK
> 
> Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue 
> Services India LLP is a company incorporated in India and is operated under 
> license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company 
> incorporated in Brasil and is operated under license from Shape Blue Ltd. 
> ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa 
> and is traded under license from Shape Blue Ltd. ShapeBlue is a registered 
> trademark.
> This email and any attachments to it may be confidential and are intended 
> solely for the use of the individual to whom it is addressed. Any views or 
> opinions expressed are solely those of the author and do not necessarily 
> represent those of Shape Blue Ltd or related companies. If you are not the 
> intended recipient of this email, you must neither take any action based upon 
> its contents, nor copy or show it to anyone. Please contact the sender if you 
> believe you have received this email in error.
> 
> 
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: 30 November 2015 10:24
> To: dev 
> Subject: Re: Package Repositories
> 
> +1 all the way, sebastien
> 
> On Mon, Nov 30, 2015 at 11:20 AM, Nux!  wrote:
> 
> > +1 your categories.
> >
> > Also +1 for the unified thing under cloudstack.apache.org domain.
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> >
> > - Original Message -
> > > From: "sebgoa" 
> > > To: dev@cloudstack.apache.org
> > > Sent: Monday, 30 November, 2015 10:08:59
> > > Subject: Re: Package Repositories
> >
> > > Hi folks, we need to resolve this.
> > >
> > > 1-But I have to start with one comment:
> > > Apache open office releases binaries, users don't compile from source.
> > So it is
> > > possible within ASF to officially release binaries.
> > >
> > > 2-We have several initiatives around repos, apt-get.eu (Wido),
> > shapeblue repos,
> > > Nux mirrors and image templates.
> > > Seems everyone agrees we need a tag team to coordinate all of it and
> > offer a
> > > unified front.
> > >
> > > 3-This unified front is great, but it won't happen this week, it
> > > will
> > take time
> > > and dedication.
> > >
> > > 4-The small issue we are facing is about 3 lines in an HTML file on
> > > our
> > website.
> > > Pierre-Luc and I had a chat Friday, in one of his comments on the PR
> > > he suggested that we list 3 categories:
> > >
> > > - source
> > > - community repo
> > > - 3-rd party repo
> > >
> > > I am +1 with this, why ?
> > >
> > > -source is a no brainer
> > > - community repo (apt-get) because that's our defacto pkg repo even
> > though we
> > > don't vote on packages. There was not vote to say these were our
> > community repo
> > > but that's a fact. Several people have access to the machine and can
> > > make updates etc...
> > > - 3rd party, allows us to list vendor pkg repo. The more vendors
> > > provide CloudStack the better. I see it a bit like the "books"
> > > discussions we had couple years ago. We do not endorse them, but we 
> > > should promote them.
> > >
> > > In our docs however, we should not be referencing 3rd party repos,
> > > and
> > any URLs
> > > should be cloudstack project specific.
> > >
> > > Can you please reply with your vote on these 3 categories. I think
> > > it's a compromise that helps us move forward.
> > >
> > > -sebastien
> > >
> > >
> > >
> > > On Nov 27, 2015, at 10:41 AM, Daan Hoogland
> > > 
> > wrote:
> > >
> > >> On Fri, Nov 27, 2015 at 10:38 AM, Paul Angus
> > >> 
> > >> wrote:
> > >>
> > >>> Doesn't that meant that we'll have to vote on the source and the
> > packaged
> > >>> rpms/debs otherwise they we have no official community standing. ?
> > >>>
> > >> ​I am not sure how we can give them official standing yet but we
> > >> are the apache foundation​, so we vote on source. I would say we
> > >> vote on the packaging software from a different repo then the
> > >> core+plugins and automatically update a repo from that one. The
> > >> repo will not be endorsed but the way it is filled will be.
> > >>
> > >> my €0,02 of future dreams
> > >>
> > >>
> > >> -Original Message-
> > >>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> > >>> Sent: 2

[GitHub] cloudstack pull request: Show Agent name in Ping response

[pdube]

Github user pdube commented on the pull request:

https://github.com/apache/cloudstack/pull/1143#issuecomment-160684591
  
@wido :)


---
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-8988: Removed unused adapters ...

[DaanHoogland]

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/943#issuecomment-160704405
  
there is a merge conflict @rodrigo93 . can you resolve it please?


---
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-8988: Removed unused adapters ...

[rafaelweingartner]

Github user rafaelweingartner commented on the pull request:

https://github.com/apache/cloudstack/pull/943#issuecomment-160705037
  
@DaanHoogland , where did you see the merge conflict Daan ? I did not find 
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: Add marvin test to verify if DomainAdmin ...

[remibergsma]

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1122#issuecomment-160711475
  
LGTM, the test runs fine here:

```
Testcreation, adding and removing tag on public IP address ... === 
TestName: test_24_public_IP_tag | Status : SUCCESS ===
ok
```


---
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-8988: Removed unused adapters ...

[rodrigo93]

Github user rodrigo93 commented on the pull request:

https://github.com/apache/cloudstack/pull/943#issuecomment-160714102
  
@DaanHoogland Can you tell us where the conflict is? It seems ok to me.


---
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: Fix secondary storage not working with sw...

[pdion891]

Github user pdion891 commented on the pull request:

https://github.com/apache/cloudstack/pull/1133#issuecomment-160715727
  
LGTM,  quickly tested, can create vm, templates and snapshots.


---
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: Fix secondary storage not working with sw...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Update L10N resource files with 4.6 strin...

[pdion891]

Github user pdion891 commented on the pull request:

https://github.com/apache/cloudstack/pull/1138#issuecomment-160719956
  
LGTM, seams to fix linguistic issues, at least solving few for French.



---
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: Update L10N resource files with 4.6 strin...

[pdube]

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

https://github.com/apache/cloudstack/pull/1138#discussion_r46184167
  
--- Diff: client/WEB-INF/classes/resources/messages_fr_FR.properties ---
@@ -1739,7 +1740,7 @@ message.action.enable.nexusVswitch=Confirmer 
l\\'activation de ce Nexus 1000v
 message.action.enable.physical.network=Confirmer l\\'activation de ce 
r\u00e9seau physique.
 message.action.enable.pod=Activer ce pod ?
 message.action.enable.zone=Activer cette zone ?
-message.action.expunge.instance=Confirmez que vous souhaitez oruger cette 
instance.
+message.action.expunge.instance=Confirmez que vous souhaitez effacer cette 
instance.
--- End diff --

purger?


---
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: Update L10N resource files with 4.6 strin...

[pdube]

Github user pdube commented on the pull request:

https://github.com/apache/cloudstack/pull/1138#issuecomment-160720589
  
Suggested a small french change, but still 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: Update L10N resource files with 4.6 strin...

[pdube]

Github user pdube commented on the pull request:

https://github.com/apache/cloudstack/pull/1138#issuecomment-160721861
  
@remibergsma Fine with me


---
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: Update L10N resource files with 4.6 strin...

[remibergsma]

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1138#issuecomment-160721455
  
Thanks for the reviews, I'll merge it to 4.6 like this. The improvement 
should go via Transiflex website and ends up in a new PR when @milamberspace 
submits the new translations.


---
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: Update L10N resource files with 4.6 strin...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] cloudstack pull request: [4.6.1] CLOUDSTACK-9022: keep Destroyed v...

[ustcweizhou]

GitHub user ustcweizhou opened a pull request:

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

[4.6.1] CLOUDSTACK-9022: keep Destroyed volumes for sometime

for now, the Destroyed volumes will be expunged in Storage cleanup thread, 
no matter when they are destroyed.
In Expunging vm thread, we expunge the Destroyed vms which have been 
destroyed at least 'expunge.delay' seconds. We add the similar configuration 
for volumes.
same to #1029 , this is for 4.6


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

$ git pull https://github.com/ustcweizhou/cloudstack 
storage-cleanup-delay-4.6

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

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


commit 12c395b56052af36901ab3ed1a366ed8985740eb
Author: Rohit Yadav 
Date:   2015-11-25T09:07:40Z

CLOUDSTACK-9083: Add disk serial to kvm virt xml

Adds disk serial ids based on volume uuids to the virt xml. This may be 
useful
for appliances/software that needs some serial ids on the VM disks. This 
does not
impact existing/running VMs, the vm virt xmls will be updates for running 
VMs
the next time they are stopped/started.

For testing, disk serial (of debian based systemvm) in the virt xml matched 
that
in /sys/devices/pci:00::00:07.0/virtio4/block/vda/serial.

We currently don't support scsi-blcok devices for which serial is not 
supported,
for this we've added a DeviceType (LUN) which may be used in future and a 
check
to not add the serial to the xml if disk type is LUN.
Refer: https://libvirt.org/formatdomain.html#elementsDisks

Signed-off-by: Rohit Yadav 

commit 1e67a5d2c89009daabdcded86e9844824ec7d1ed
Author: Syed 
Date:   2015-11-27T18:48:18Z

Fix secondary storage not working with swift

commit 6d4722953f859c537aadd2a0b4b5f3553f33dc69
Author: Milamber 
Date:   2015-11-29T19:01:56Z

Update L10N resource files with 4.6 strings from Transifex (20151129)

commit 7dcc6540e76db06fe51e8f33803260762ffaa826
Author: Rohit Yadav 
Date:   2015-11-30T09:40:31Z

Merge pull request #1121 from shapeblue/4.6-cloudstack-9083

[4.6] CLOUDSTACK-9083: Add disk serial to kvm virt xmlAdds disk serial ids 
based on volume uuids to the virt xml. This may be useful
for appliances/software that needs some serial ids on the VM disks. This 
does not
impact existing/running VMs, the vm virt xmls will be updates for running 
VMs
the next time they are stopped/started.

For testing, disk serial (of debian based systemvm) in the virt xml matched 
that
in /sys/devices/pci:00::00:07.0/virtio4/block/vda/serial.

We currently don't support scsi-blcok devices for which serial is not 
supported,
for this we've added a DeviceType (LUN) which may be used in future and a 
check
to not add the serial to the xml if disk type is LUN.
Refer: https://libvirt.org/formatdomain.html#elementsDisks

* pr/1121:
  CLOUDSTACK-9083: Add disk serial to kvm virt xml

Signed-off-by: Rohit Yadav 

commit df0797affd0bdec9f42a28fee6af5291d4528698
Author: Remi Bergsma 
Date:   2015-11-30T18:36:37Z

Merge pull request #1133 from syed/4.6

Fix secondary storage not working with swiftOriginal PR and discussion at 
#1112

* pr/1133:
  Fix secondary storage not working with swift

Signed-off-by: Remi Bergsma 

commit e675250f6068e76d422618f8a4467aea29c256a6
Author: Remi Bergsma 
Date:   2015-11-30T18:49:01Z

Merge pull request #1138 from milamberspace/L10N-update-4.6-20151129

Update L10N resource files with 4.6 strings from Transifex (20151129)Small 
update of L10N files before the 4.6.1 release candidate

cc @remibergsma

* pr/1138:
  Update L10N resource files with 4.6 strings from Transifex (20151129)

Signed-off-by: Remi Bergsma 

commit 9077c9a5b47224b2d00978ff67e9af6957ec589b
Author: Wei Zhou 
Date:   2015-11-03T16:04:55Z

CLOUDSTACK-9022: keep Destroyed volumes for sometime

commit 4ed1e0d5f809d1bb2845b6e076d55eeb1ce3f0f4
Author: Wei Zhou 
Date:   2015-11-04T08:27:32Z

CLOUDSTACK-9022: move storage.cleanup related global configurations to 
StorageManager




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

[GitHub] cloudstack pull request: [4.6.1] CLOUDSTACK-9022: keep Destroyed v...

[ustcweizhou]

GitHub user ustcweizhou opened a pull request:

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

[4.6.1] CLOUDSTACK-9022: keep Destroyed volumes for sometime

for now, the Destroyed volumes will be expunged in Storage cleanup thread, 
no matter when they are destroyed.
In Expunging vm thread, we expunge the Destroyed vms which have been 
destroyed at least 'expunge.delay' seconds. We add the similar configuration 
for volumes.

same to #1029 , for 4.6


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

$ git pull https://github.com/ustcweizhou/cloudstack 
storage-cleanup-delay-4.6

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

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


commit 9077c9a5b47224b2d00978ff67e9af6957ec589b
Author: Wei Zhou 
Date:   2015-11-03T16:04:55Z

CLOUDSTACK-9022: keep Destroyed volumes for sometime

commit 4ed1e0d5f809d1bb2845b6e076d55eeb1ce3f0f4
Author: Wei Zhou 
Date:   2015-11-04T08:27:32Z

CLOUDSTACK-9022: move storage.cleanup related global configurations to 
StorageManager




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

[GitHub] cloudstack pull request: [4.6.1] CLOUDSTACK-9022: keep Destroyed v...

[pdube]

Github user pdube commented on the pull request:

https://github.com/apache/cloudstack/pull/1144#issuecomment-160739865
  
Hey @ustcweizhou, could you create the PR towards 4.6 please, it is hard to 
determine exactly what you changed. Thanks


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

[GitHub] cloudstack pull request: make sure all files are updates with new ...

[remibergsma]

GitHub user remibergsma opened a pull request:

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

make sure all files are updates with new version

During the previous release I had to edit these manually. This will fix 
that so all versions get updated.

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

$ git pull https://github.com/remibergsma/cloudstack build_script_fixes

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

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


commit df3ce171e834c4fa6ec9c3e98bd8f50959753418
Author: Remi Bergsma 
Date:   2015-11-30T20:39:02Z

make sure all files are updates with new version




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

[GitHub] cloudstack pull request: [4.6.1] CLOUDSTACK-9022: keep Destroyed v...

[remibergsma]

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1144#issuecomment-160756847
  
@ustcweizhou This is a mistake I guess, PR against the wrong branch?


---
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: make sure all files are updates with new ...

[DaanHoogland]

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

https://github.com/apache/cloudstack/pull/1146#discussion_r46201120
  
--- Diff: tools/build/build_asf.sh ---
@@ -101,6 +101,11 @@ perl -pi -e "s/-SNAPSHOT//" build/replace.properties
 perl -pi -e "s/-SNAPSHOT//" services/console-proxy/plugin/pom.xml
 perl -pi -e "s/-SNAPSHOT//" tools/marvin/setup.py
 perl -pi -e "s/-SNAPSHOT//" tools/marvin/marvin/deployAndRun.py
+perl -pi -e "s/-SNAPSHOT//" debian/changelog
+perl -pi -e "s/-SNAPSHOT//" services/iam/plugin/pom.xml
--- End diff --

to bad the poms don't get changed by the mvn versions:set task :(


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

[GitHub] cloudstack pull request: [4.6.1] CLOUDSTACK-9022: keep Destroyed v...

[ustcweizhou]

Github user ustcweizhou closed the pull request at:

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


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

[GitHub] cloudstack pull request: [4.6.1] CLOUDSTACK-9022: keep Destroyed v...

[ustcweizhou]

Github user ustcweizhou commented on the pull request:

https://github.com/apache/cloudstack/pull/1144#issuecomment-160758013
  
@pdube @remibergsma I will recreate a new 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: make sure all files are updates with new ...

[DaanHoogland]

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1146#issuecomment-160761783
  
Looks good to me. The version-branch should have gone in like this from the 
get go.


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

[John Burwell]

Sebastian,

As I mentioned in my initial message, the public ShapeBlue repositories [1] are 
noredist builds of release baselines with no additional patches or changes.  My 
understanding is that the project cannot officially distribute the noredist 
plugins due to inability of the community to distribute libraries required by 
these components.  If my understanding is correct, I don’t think a community 
managed package repos could contain packages with this components.

I am +1 to the categories.  I am +1 to the making packages official project 
deliverables that are voted out.  Users clear prefer to install via packages.  
It seems like applying the full attention of the community to test them would 
certainly a good thing for users.

Thanks,
-John

[1]: http://packages.shapeblue.com/cloudstack/upstream

—
John Burwell
VP Software Engineering


USA: (571) 403-2411 | UK: +44 20 3603 0542
john.burw...@shapeblue.com | www.shapeblue.com | Twitter: @ShapeBlue
ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS

> On Nov 30, 2015, at 11:44 AM, sebgoa  wrote:
>
>
> On Nov 30, 2015, at 11:28 AM, Paul Angus  wrote:
>
>> Sebastien,
>>
>> Can you confirm that users can expect to find the noredist build of the rpms 
>> and debs at apt-get.eu ?
>>
>
> I don't know
>
> What I understood from Rohit, is that the "shapeblue" repo also contains pkgs 
> that are hot-fixed and have features back ported.
> In that sense it is quite a different repo than apt-get which only has pkg 
> for each release.
>
>
>>
>>
>>
>> Paul Angus
>> VP Technology ,   ShapeBlue Ltd
>> s:   02036170528   |  t: @cloudyangus  |  m: +44 
>> 7711418784
>> e:   paul.an...@shapeblue.com  |  w: www.shapeblue.com
>>   53 Chandos Place, Covent Garden, London WC2N 4HS. UK
>>
>> Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue 
>> Services India LLP is a company incorporated in India and is operated under 
>> license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company 
>> incorporated in Brasil and is operated under license from Shape Blue Ltd. 
>> ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa 
>> and is traded under license from Shape Blue Ltd. ShapeBlue is a registered 
>> trademark.
>> This email and any attachments to it may be confidential and are intended 
>> solely for the use of the individual to whom it is addressed. Any views or 
>> opinions expressed are solely those of the author and do not necessarily 
>> represent those of Shape Blue Ltd or related companies. If you are not the 
>> intended recipient of this email, you must neither take any action based 
>> upon its contents, nor copy or show it to anyone. Please contact the sender 
>> if you believe you have received this email in error.
>>
>>
>> -Original Message-
>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> Sent: 30 November 2015 10:24
>> To: dev 
>> Subject: Re: Package Repositories
>>
>> +1 all the way, sebastien
>>
>> On Mon, Nov 30, 2015 at 11:20 AM, Nux!  wrote:
>>
>>> +1 your categories.
>>>
>>> Also +1 for the unified thing under cloudstack.apache.org domain.
>>>
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>>
>>> Nux!
>>> www.nux.ro
>>>
>>> - Original Message -
 From: "sebgoa" 
 To: dev@cloudstack.apache.org
 Sent: Monday, 30 November, 2015 10:08:59
 Subject: Re: Package Repositories
>>>
 Hi folks, we need to resolve this.

 1-But I have to start with one comment:
 Apache open office releases binaries, users don't compile from source.
>>> So it is
 possible within ASF to officially release binaries.

 2-We have several initiatives around repos, apt-get.eu (Wido),
>>> shapeblue repos,
 Nux mirrors and image templates.
 Seems everyone agrees we need a tag team to coordinate all of it and
>>> offer a
 unified front.

 3-This unified front is great, but it won't happen this week, it
 will
>>> take time
 and dedication.

 4-The small issue we are facing is about 3 lines in an HTML file on
 our
>>> website.
 Pierre-Luc and I had a chat Friday, in one of his comments on the PR
 he suggested that we list 3 categories:

 - source
 - community repo
 - 3-rd party repo

 I am +1 with this, why ?

 -source is a no brainer
 - community repo (apt-get) because that's our defacto pkg repo even
>>> though we
 don't vote on packages. There was not vote to say these were our
>>> community repo
 but that's a fact. Several people have access to the machine and can
 make updates etc...
 - 3rd party, allows us to list vendor pkg repo. The more vendors
 provide CloudStack the better. I see it a bit like the "books"
 discussions we had couple years ago. We do not endorse them, but we should 
 promote them.

 In our docs however, we should not be referencing 3rd p

[GitHub] cloudstack pull request: make sure all files are updates with new ...

[pdube]

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

https://github.com/apache/cloudstack/pull/1146#discussion_r46204918
  
--- Diff: tools/build/build_asf.sh ---
@@ -101,6 +101,11 @@ perl -pi -e "s/-SNAPSHOT//" build/replace.properties
 perl -pi -e "s/-SNAPSHOT//" services/console-proxy/plugin/pom.xml
 perl -pi -e "s/-SNAPSHOT//" tools/marvin/setup.py
 perl -pi -e "s/-SNAPSHOT//" tools/marvin/marvin/deployAndRun.py
+perl -pi -e "s/-SNAPSHOT//" debian/changelog
+perl -pi -e "s/-SNAPSHOT//" services/iam/plugin/pom.xml
+perl -pi -e "s/-SNAPSHOT//" services/iam/pom.xm
+perl -pi -e "s/-SNAPSHOT//" services/iam/server/pom.xml
--- End diff --

Why do you have to add these manually? What about the other folders in 
/services?


---
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: make sure all files are updates with new ...

[pdube]

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

https://github.com/apache/cloudstack/pull/1146#discussion_r46204974
  
--- Diff: tools/build/build_asf.sh ---
@@ -123,11 +128,7 @@ git clean -f
 
 #create a RC branch
 RELEASE_BRANCH="RC"`date +%Y%m%dT%H%M`
--- End diff --

Might be clearer to name this variable RC_BRANCH_SUFFIX


---
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: make sure all files are updates with new ...

[remibergsma]

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1146#issuecomment-160764367
  
The build script now makes a branch that makes sense: 
`4.6.1-RC20151130T2206` instead of `4.6-RC20151130T2206`. Also the versions are 
updated properly.

Output example:
https://cloud.githubusercontent.com/assets/1630096/11484755/2a4d6922-97b0-11e5-901c-15bde6b49771.png";>



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

[GitHub] cloudstack pull request: make sure all files are updates with new ...

[remibergsma]

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

https://github.com/apache/cloudstack/pull/1146#discussion_r46205215
  
--- Diff: tools/build/build_asf.sh ---
@@ -101,6 +101,11 @@ perl -pi -e "s/-SNAPSHOT//" build/replace.properties
 perl -pi -e "s/-SNAPSHOT//" services/console-proxy/plugin/pom.xml
 perl -pi -e "s/-SNAPSHOT//" tools/marvin/setup.py
 perl -pi -e "s/-SNAPSHOT//" tools/marvin/marvin/deployAndRun.py
+perl -pi -e "s/-SNAPSHOT//" debian/changelog
+perl -pi -e "s/-SNAPSHOT//" services/iam/plugin/pom.xml
+perl -pi -e "s/-SNAPSHOT//" services/iam/pom.xm
+perl -pi -e "s/-SNAPSHOT//" services/iam/server/pom.xml
--- End diff --

It is supposed to go automatically, but it doesn't pick these ones up. It 
should be investigated why that is and if these are still used.


---
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: make sure all files are updates with new ...

[remibergsma]

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

https://github.com/apache/cloudstack/pull/1146#discussion_r46205478
  
--- Diff: tools/build/build_asf.sh ---
@@ -123,11 +128,7 @@ git clean -f
 
 #create a RC branch
 RELEASE_BRANCH="RC"`date +%Y%m%dT%H%M`
--- End diff --

Yep, changed 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:

[pdube]

Github user pdube commented on the pull request:


https://github.com/apache/cloudstack/commit/7d7420fd1e5908e1bc4ee04a314241212f7a6481#commitcomment-14693674
  
+1


---
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: make sure all files are updates with new ...

[pdube]

Github user pdube commented on the pull request:

https://github.com/apache/cloudstack/pull/1146#issuecomment-160765582
  
Ok then, 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: make sure all files are updates with new ...

[rafaelweingartner]

Github user rafaelweingartner commented on the pull request:

https://github.com/apache/cloudstack/pull/1146#issuecomment-160765816
  
It LGTM, 
I would just recommend using “sed” in combination with “find” to 
look up for every file that we want to change the version number, instead of 
perl, but that is more a matter of taste.



---
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: make sure all files are updates with new ...

[remibergsma]

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1146#issuecomment-160766514
  
@rafaelweingartner I agree and I think this needs some TLC indeed. 
Investigate why it doesn't work with mvn and then do one global search/replace 
for the remaining. I'll merge this now and proceed with 4.6.1RC, then make the 
improvement later.


---
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: make sure all files are updates with new ...

[pdion891]

Github user pdion891 commented on the pull request:

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