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

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1593
  
Packaging result: ✔centos6 ✔centos7 ✔debian repo: 
http://packages.shapeblue.com/cloudstack/pr/1593
Job ID #65


---
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 #1541: Systemd packaging for Ubuntu 16.04

[vincentbernat]

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

https://github.com/apache/cloudstack/pull/1541#discussion_r73830499
  
--- Diff: debian/cloudstack-agent.install ---
@@ -18,12 +18,11 @@
 /etc/cloudstack/agent/agent.properties
 /etc/cloudstack/agent/environment.properties
 /etc/cloudstack/agent/log4j-cloud.xml
+/etc/default/cloudstack-agent
 /etc/profile.d/cloudstack-agent-profile.sh
 /etc/logrotate.d/cloudstack-agent
-/etc/init.d/cloudstack-agent
 /usr/bin/cloudstack-setup-agent
--- End diff --

You can keep the init.d file for everybody. If the the system is running 
systemd, a service with the same basename will override the init.d file.


---
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 #1541: Systemd packaging for Ubuntu 16.04

[vincentbernat]

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

https://github.com/apache/cloudstack/pull/1541#discussion_r73830557
  
--- Diff: debian/control ---
@@ -3,7 +3,7 @@ Section: libs
 Priority: extra
 Maintainer: Wido den Hollander 
 Build-Depends: debhelper (>= 9), openjdk-8-jdk | openjdk-7-jdk, 
genisoimage,
- python-mysql.connector, maven (>= 3) | maven3, python (>= 2.7)
+ python-mysql.connector, maven (>= 3) | maven3, python (>= 2.7), 
lsb-release
--- End diff --

For systemd integration, you need to Build-Depends on dh-systemd. 
Unfortunately, this will make the package unbuildable on Precise. See below.


---
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 #1541: Systemd packaging for Ubuntu 16.04

[vincentbernat]

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

https://github.com/apache/cloudstack/pull/1541#discussion_r73830730
  
--- Diff: debian/rules ---
@@ -5,9 +5,18 @@ PACKAGE = $(shell dh_listpackages|head -n 1|cut -d '-' -f 
1)
 SYSCONFDIR = "/etc"
 DESTDIR = "debian/tmp"
 
+ifeq ($(shell lsb_release -sr), 14.04)
+SUBSTVARS = -Vjre:Depends="openjdk-7-jre-headless" 
-Vjdk:Depends="openjdk-7-jdk" -Vinit:"Depends:jsvc"
+else
+SUBSTVARS = -Vjre:Depends="openjdk-8-jre-headless" 
-Vjdk:Depends="openjdk-8-jdk" -Vinit:"Depends:systemd"
+endif
+
 %:
dh $@ --with python2
--- End diff --

You need to do `--with python2,systemd`. Otherwise, systemd unit won't be 
enabled automatically and the integration won't happen (no restart of the 
service on upgrade for example).


---
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 #1541: Systemd packaging for Ubuntu 16.04

[rhtyd]

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

https://github.com/apache/cloudstack/pull/1541#discussion_r73830805
  
--- Diff: debian/control ---
@@ -3,7 +3,7 @@ Section: libs
 Priority: extra
 Maintainer: Wido den Hollander 
 Build-Depends: debhelper (>= 9), openjdk-8-jdk | openjdk-7-jdk, 
genisoimage,
- python-mysql.connector, maven (>= 3) | maven3, python (>= 2.7)
+ python-mysql.connector, maven (>= 3) | maven3, python (>= 2.7), 
lsb-release
--- End diff --

@vincentbernat that should be okay, we can use Xenial to build pkgs for 
both Xenial and Precise. At some point we'll need to stop building packages for 
Precise.


---
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 #1541: Systemd packaging for Ubuntu 16.04

[vincentbernat]

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

https://github.com/apache/cloudstack/pull/1541#discussion_r73830801
  
--- Diff: debian/rules ---
@@ -116,17 +132,24 @@ override_dh_auto_install:
 
# cloudstack-usage
mkdir $(DESTDIR)/$(SYSCONFDIR)/$(PACKAGE)/usage
-   mkdir $(DESTDIR)/var/log/$(PACKAGE)/usage
mkdir $(DESTDIR)/usr/share/$(PACKAGE)-usage
mkdir $(DESTDIR)/usr/share/$(PACKAGE)-usage/plugins
install -D usage/target/cloud-usage-$(VERSION).jar 
$(DESTDIR)/usr/share/$(PACKAGE)-usage/lib/$(PACKAGE)-usage.jar
install -D usage/target/dependencies/* 
$(DESTDIR)/usr/share/$(PACKAGE)-usage/lib/
cp usage/target/transformed/db.properties 
$(DESTDIR)/$(SYSCONFDIR)/$(PACKAGE)/usage/
cp usage/target/transformed/log4j-cloud_usage.xml 
$(DESTDIR)/$(SYSCONFDIR)/$(PACKAGE)/usage/log4j-cloud.xml
-   install -D packaging/debian/init/cloud-usage 
$(DESTDIR)/$(SYSCONFDIR)/init.d/$(PACKAGE)-usage
+
+   install -d -m0755 debian/$(PACKAGE)-usage/etc/init.d
+   install -D -m0755 packaging/debian/$(PACKAGE)-usage.init 
debian/$(PACKAGE)-usage/etc/init.d/$(PACKAGE)-usage
+   install -d -m0755 debian/$(PACKAGE)-usage/lib/systemd/system
+   install -m0644 packaging/debian/$(PACKAGE)-usage.service 
debian/$(PACKAGE)-usage/lib/systemd/system/$(PACKAGE)-usage.service
+   install -m0644 packaging/debian/$(PACKAGE)-usage.default 
$(DESTDIR)/$(SYSCONFDIR)/default/$(PACKAGE)-usage
 
 override_dh_installinit:
dh_installinit -pcloudstack-management -pcloudstack-agent 
-pcloudstack-usage --onlyscripts --no-start
 
+override_dh_systemd_enable:
+   dh_systemd_enable -pcloudstack-agent -pcloudstack-usage
+
--- End diff --

This bit needs the `--with systemd` bit mentioned above.


---
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 #1541: Systemd packaging for Ubuntu 16.04

[rhtyd]

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

https://github.com/apache/cloudstack/pull/1541#discussion_r73830916
  
--- Diff: debian/cloudstack-agent.install ---
@@ -18,12 +18,11 @@
 /etc/cloudstack/agent/agent.properties
 /etc/cloudstack/agent/environment.properties
 /etc/cloudstack/agent/log4j-cloud.xml
+/etc/default/cloudstack-agent
 /etc/profile.d/cloudstack-agent-profile.sh
 /etc/logrotate.d/cloudstack-agent
-/etc/init.d/cloudstack-agent
 /usr/bin/cloudstack-setup-agent
--- End diff --

@wido can we also move the debian directory to packaging folder? The deb 
files are build at `..` which is the parent folder of the cloudstack 
repo/source code, and causes issues when doing concurrent builds using Jenkins.


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

[GitHub] cloudstack issue #1541: Systemd packaging for Ubuntu 16.04

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1541
  
@blueorangutan package


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

[GitHub] cloudstack issue #1541: Systemd packaging for Ubuntu 16.04

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1541
  
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you 
posted as I make progress.


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

[GitHub] cloudstack issue #1541: Systemd packaging for Ubuntu 16.04

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1541
  
Packaging result: ✔centos6 ✔centos7 ✔debian repo: 
http://packages.shapeblue.com/cloudstack/pr/1541
Job ID #67


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

[GitHub] cloudstack issue #1630: Add projectid to project details page

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1630
  
LGTM, @pdion891 can we have a screenshot to confirm regression testing?


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

[GitHub] cloudstack pull request #1631: Fix debian build error due to commit 3315eb5

[karuturi]

GitHub user karuturi opened a pull request:

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

Fix debian build error due to commit 3315eb5

debian build is broken due to the changelog changes in commit 3315eb5. 
Fixed the same.
To test, do a debian following the instructions at 
http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.8/building_from_source.html#building-deb-packages

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

$ git pull https://github.com/karuturi/cloudstack 
merge-49-to-master-deb-build

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

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


commit d87828af2449907192dfd69a22fdb9cd5780d329
Author: Rajani Karuturi 
Date:   2016-08-08T09:32:03Z

Fix debian build error due to commit 
3315eb5420e1b2cedf906aeb709740efc2f08cfd




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

[karuturi]

Github user karuturi commented on the pull request:


https://github.com/apache/cloudstack/commit/3315eb5420e1b2cedf906aeb709740efc2f08cfd#commitcomment-18555999
  
@pdion891 Thanks for reporting this. created a PR #1631 

For the second part, version_number-string seems to be an accepted format 
by debian 
https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version
I dont have good knowledge in debian packaging. Will let others fix this if 
required.


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

[GitHub] cloudstack issue #1054: CLOUDSTACK-8818: Use MySQL native connector with Pyt...

[wido]

Github user wido commented on the issue:

https://github.com/apache/cloudstack/pull/1054
  
The package is called *python-mysql.connector* in Ubuntu and Debian: 
http://packages.ubuntu.com/xenial/python-mysql.connector

The mysql-connector-python package name is CentOS/RHEL.


---
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 #1617: Changed UsageEventUtils to UsageEventEmitter ...

[ProjectMoon]

Github user ProjectMoon closed the pull request at:

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


---
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: current list of blockers

[Rajani Karuturi]

Thanks Rohit. Will take a look at the PR.
~ Rajanihttp://cloudplatform.accelerite.com/
On August 5, 2016 at 5:01 PM, Rohit Yadav
(rohit.ya...@shapeblue.com) wrote:CLOUDSTACK-9437 has been fixed
and applied on 4.9+. This can be closed.

CLOUDSTACK-9420 needs a checking against latest 4.9.0 release or
master.

We also have a build blocker which is around systemvm template
building: (not exactly a road-block but would be great to get it
merged)
https://github.com/apache/cloudstack/pull/1626 ( 
https://github.com/apache/cloudstack/pull/1626 )

Regards.
From: Rajani Karuturi
Sent: 05 August 2016
15:38:14To: dev@cloudstack.apache.org ( dev@cloudstack.apache.org
)Subject: current list of blockers
We have the following list of blockers currently open.
CLOUDSTACK-9437: Outbound traffic fails to work after VR is
upgraded topost 4.6+ releaseCLOUDSTACK-9420: Process encryption
hangsCLOUDSTACK-9408: remove runtime references
to http://download.cloud.com ( http://download.cloud.com )
If you have some time, please take a look at them.
JIRA search query: project=cloudstack AND priority = Blocker AND
resolutionis EMPTY
Thanks,
~Rajanihttp://cloudplatform.accelerite.com/ ( 
http://cloudplatform.accelerite.com/ )
rohit.ya...@shapeblue.com ( rohit.ya...@shapeblue.com
) www.shapeblue.com ( http://www.shapeblue.com )53 Chandos Place,
Covent Garden, London WC2N 4HSUK@shapeblue

[GitHub] cloudstack pull request #1617: Changed UsageEventUtils to UsageEventEmitter ...

[ProjectMoon]

GitHub user ProjectMoon reopened a pull request:

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

Changed UsageEventUtils to UsageEventEmitter and made it injectable

An updated version of #1191, against the master branch. This also updates 
the HypervisorTemplateAdapter test slightly, making it less unwieldy.

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

$ git pull https://github.com/greenqloud/cloudstack 
pr-usage-event-emitter-master

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

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


commit 9dba2fc9b42bb91de1ec17dc01c2f9c64749fd3c
Author: nnesic 
Date:   2015-11-26T16:02:44Z

Changed UsageEventUtils to UsageEventEmitter and made it injectable




---
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 #1618: Now returning os info with the list snapshot ...

[ProjectMoon]

Github user ProjectMoon closed the pull request at:

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


---
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 #1618: Now returning os info with the list snapshot ...

[ProjectMoon]

GitHub user ProjectMoon reopened a pull request:

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

Now returning os info with the list snapshot response

This commit adds the ID and display name of the OS on the volume. 

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

$ git pull https://github.com/greenqloud/cloudstack 
pr-return-os-info-snapshots

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

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


commit 04bd2fe0d1ec85db6fe9237ae5fb66d533e59f01
Author: Pall Helgason 
Date:   2016-03-02T13:11:30Z

Now returning os info with the list snapshot 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: Meet BlueOrangutan

[Wido den Hollander]

> Op 6 augustus 2016 om 11:14 schreef Rohit Yadav :
> 
> 
> All,
> 
> 
> Meet blueorangutan [1], a Github bot account that will help us automate 
> CloudStack (PR) testing [2][3] among other things.
> 
> 
> It works by polling Github notifications for the apache/cloudstack repository 
> every minutes and then reacts to comments. We can post comments on a 
> apache/cloudstack PR and ask @blueorangutan to perform certain build jobs 
> such as building packages, then running Trillian [2] tests (across a set of 
> hypervisors) using those packages, and finally report us the results.
> 
> 
> Since, the task of building packages and testing them are expensive. A 
> typical packaging job may take up to 30 minutes, a typical Trillian [2][3] 
> environment can take about 30 minutes to build/deploy a zone, and a Trillian 
> (smoke) test run may take hours while an exhaustive Trillian 
> (component+smoke) test run may take 3-4 days. Due to these reasons, for now 
> the '@blueorangutan test' task is restricted to a selected Github users (my 
> colleagues at ShapeBlue). Running Trillian test for each PR may be expensive, 
> we may consider batching smaller thoroughly reviewed PRs, then create 
> packages for a set of PRs and test them all at once as well.
> 
> 

What do you need in additional resources? Building packages for example can be 
done very easily in Docker containers. I can provide resources for that if 
needed. No problem!

> The task to build (centos6, centos7, debian) packages is relatively less 
> expensive and anyone can request blueorangutan to build packages now by 
> commenting '@blueorangutan package' on a PR.
> 
> 
> The great blue ape aims to be a quite friendly and polite bot, go on any 
> apache/cloudstack PR and try:
> 
> '@blueorangutan hello'
> 
> 
> Or, build package for a PR:
> 
> '@blueorangutan package'
> 
> 
> Or, if it helps you build packages you may say:
> 
> '@blueorangutan thanks'
> 
> 
> This is an experiment and I hope to improve this over time, any feedback and 
> comments are welcome.
> 
> 
> [1] https://github.com/blueorangutan
> 
> [2] 
> http://www.shapeblue.com/trillian-flexible-on-demand-individual-cloud-environment-creation/
> 
> [3] 
> http://www.shapeblue.com/cloudstack-test-automation-with-trillian-and-jenkins/
> 
> Regards.
> 
> rohit.ya...@shapeblue.com 
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>   
>  
>

[GitHub] cloudstack issue #1622: Adding missing bits field to TemplateResponse

[ProjectMoon]

Github user ProjectMoon commented on the issue:

https://github.com/apache/cloudstack/pull/1622
  
Rebased to latest master, though I still haven't checked into the Jenkins 
issue.


---
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 #1541: Systemd packaging for Ubuntu 16.04

[wido]

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

https://github.com/apache/cloudstack/pull/1541#discussion_r73848786
  
--- Diff: debian/cloudstack-agent.install ---
@@ -18,12 +18,11 @@
 /etc/cloudstack/agent/agent.properties
 /etc/cloudstack/agent/environment.properties
 /etc/cloudstack/agent/log4j-cloud.xml
+/etc/default/cloudstack-agent
 /etc/profile.d/cloudstack-agent-profile.sh
 /etc/logrotate.d/cloudstack-agent
-/etc/init.d/cloudstack-agent
 /usr/bin/cloudstack-setup-agent
--- End diff --

Maybe, never tried that before. Might be possible. But shall we do that in 
a different PR? Merge this one and then fix 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.
---

[GitHub] cloudstack issue #1631: Fix debian build error due to commit 3315eb5

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
  @blueorangutan package


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

[GitHub] cloudstack issue #1631: Fix debian build error due to commit 3315eb5

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
@karuturi a Jenkins job has been kicked to build packages. I'll keep you 
posted as I make progress.


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

[GitHub] cloudstack issue #1631: Fix debian build error due to commit 3315eb5

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
@ blueorangutan 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 issue #1631: Fix debian build error due to commit 3315eb5

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
 @blueorangutan 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.
---

Re: Meet BlueOrangutan

[Rajani Karuturi]

This is great. Thanks for all the hardwork Rohit. Will start using it.

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

On Sat, Aug 6, 2016 at 2:44 PM, Rohit Yadav 
wrote:

> All,
>
>
> Meet blueorangutan [1], a Github bot account that will help us automate
> CloudStack (PR) testing [2][3] among other things.
>
>
> It works by polling Github notifications for the apache/cloudstack
> repository every minutes and then reacts to comments. We can post comments
> on a apache/cloudstack PR and ask @blueorangutan to perform certain build
> jobs such as building packages, then running Trillian [2] tests (across a
> set of hypervisors) using those packages, and finally report us the results.
>
>
> Since, the task of building packages and testing them are expensive. A
> typical packaging job may take up to 30 minutes, a typical Trillian [2][3]
> environment can take about 30 minutes to build/deploy a zone, and a
> Trillian (smoke) test run may take hours while an exhaustive Trillian
> (component+smoke) test run may take 3-4 days. Due to these reasons, for now
> the '@blueorangutan test' task is restricted to a selected Github users (my
> colleagues at ShapeBlue). Running Trillian test for each PR may be
> expensive, we may consider batching smaller thoroughly reviewed PRs, then
> create packages for a set of PRs and test them all at once as well.
>
>
> The task to build (centos6, centos7, debian) packages is relatively less
> expensive and anyone can request blueorangutan to build packages now by
> commenting '@blueorangutan package' on a PR.
>
>
> The great blue ape aims to be a quite friendly and polite bot, go on any
> apache/cloudstack PR and try:
>
> '@blueorangutan hello'
>
>
> Or, build package for a PR:
>
> '@blueorangutan package'
>
>
> Or, if it helps you build packages you may say:
>
> '@blueorangutan thanks'
>
>
> This is an experiment and I hope to improve this over time, any feedback
> and comments are welcome.
>
>
> [1] https://github.com/blueorangutan
>
> [2] http://www.shapeblue.com/trillian-flexible-on-demand-
> individual-cloud-environment-creation/
>
> [3] http://www.shapeblue.com/cloudstack-test-automation-
> with-trillian-and-jenkins/
>
> Regards.
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

[GitHub] cloudstack issue #1631: Fix debian build error due to commit 3315eb5

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
Packaging result: ✖centos6 ✖centos7 ✖debian repo: 
http://packages.shapeblue.com/cloudstack/pr/1631
Job ID-68


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

[GitHub] cloudstack issue #1631: Fix debian build error due to commit 3315eb5

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
@karuturi I checked there was an internal infra issue, I'll kick it again
@blueorangutan package


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

[GitHub] cloudstack issue #1631: Fix debian build error due to commit 3315eb5

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you 
posted as I make progress.


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

[GitHub] cloudstack issue #1631: Fix debian build error due to commit 3315eb5

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
@blueorangutan 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 issue #1631: Fix debian build error due to commit 3315eb5

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
you're welcome @rhtyd


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

[GitHub] cloudstack issue #1631: Fix debian build error due to commit 3315eb5

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
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 #1620: oobm: simply change password transactional lo...

[rhtyd]

GitHub user rhtyd reopened a pull request:

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

oobm: simply change password transactional logic

- Simplifies change password transactional logic without using pessmistic 
locks
- Adds a re-enter password field in the UI to valid ipmi/oobm password

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

$ git pull https://github.com/shapeblue/cloudstack 4.9-oobm-password-fix

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

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


commit 8ac3c883cd61fa0e18498aaae4e4f519743295c4
Author: Rohit Yadav 
Date:   2016-07-11T11:36:09Z

oobm: simply change password transactional logic

- Simplifies change password transactional logic without using pessmistic 
locks
- Adds a re-enter password field in the UI to valid ipmi/oobm password

Signed-off-by: Rohit Yadav 




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

[GitHub] cloudstack pull request #1620: oobm: simply change password transactional lo...

[rhtyd]

Github user rhtyd closed the pull request at:

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


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

[GitHub] cloudstack issue #1115: CLOUDSTACK-9064: The users should be able to create ...

[abhinandanprateek]

Github user abhinandanprateek commented on the issue:

https://github.com/apache/cloudstack/pull/1115
  
fixed in 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 #1115: CLOUDSTACK-9064: The users should be able to ...

[abhinandanprateek]

Github user abhinandanprateek closed the pull request at:

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


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

[GitHub] cloudstack issue #1631: Fix debian build error due to commit 3315eb5

[abhinandanprateek]

Github user abhinandanprateek commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
LGTM on review


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

[GitHub] cloudstack issue #1630: Add projectid to project details page

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1630
  
Packaging result: ✖centos6 ✔centos7 ✔debian repo: 
http://packages.shapeblue.com/cloudstack/pr/1630
Job ID-69


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

[GitHub] cloudstack issue #1631: Fix debian build error due to commit 3315eb5

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
Packaging result: ✖centos6 ✔centos7 ✔debian repo: 
http://packages.shapeblue.com/cloudstack/pr/1631
Job ID-70


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

[GitHub] cloudstack issue #1631: Fix debian build error due to commit 3315eb5

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
Thanks @abhinandanprateek and @rhtyd. I will merge once @blueorangutan is 
happy


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

[GitHub] cloudstack issue #1541: Systemd packaging for Ubuntu 16.04

[wido]

Github user wido commented on the issue:

https://github.com/apache/cloudstack/pull/1541
  
Thank you @vincentbernat, I applied your fixes. Can you take a look?


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

[GitHub] cloudstack issue #1541: Systemd packaging for Ubuntu 16.04

[vincentbernat]

Github user vincentbernat commented on the issue:

https://github.com/apache/cloudstack/pull/1541
  
The only change I have noticed is the change in postinst. This could bypass 
the local administrator policy. It would not restart the agent on upgrade 
either. I would suggest to :

 - Build-Depends on dh-systemd
 - Add --with systemd, python2 do dh invocation
 - Remove the postinst snippet

If you don't want to add a dependency to dh-systemd, the override in 
debian/rules is useless and the postinst snippet should be more complex. Check 
for example `/var/lib/dpkg/info/openssh-server.postinst` for the sections 
`dh_systemd_enable`. Note that there are other snippets in postrm.


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

[GitHub] cloudstack issue #1541: Systemd packaging for Ubuntu 16.04

[wido]

Github user wido commented on the issue:

https://github.com/apache/cloudstack/pull/1541
  
@vincentbernat Thanks! Good pointers. I will look into those.


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

[GitHub] cloudstack issue #1631: Fix debian build error due to commit 3315eb5

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
@rhtyd I see centos6 packages at 
http://packages.shapeblue.com/cloudstack/pr/1631/centos/4.10/ 
Can you share what failed?


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

[GitHub] cloudstack issue #1631: Fix debian build error due to commit 3315eb5

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
@karuturi yes debugging, hold on.


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

[GitHub] cloudstack issue #1054: CLOUDSTACK-8818: Use MySQL native connector with Pyt...

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1054
  
what @pdion891 says is correct. I just tried building deb packages on 
ubuntu 12:04 
Even after installing http://dev.mysql.com/downloads/connector/python/ its 
complaining about python mysql connector

> dpkg-buildpackage -uc -us
> dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): 
-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security
> dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor): 
-D_FORTIFY_SOURCE=2
> dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): 
-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security
> dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): 
-g -O2
> dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor): 
-Wl,-Bsymbolic-functions -Wl,-z,relro
> dpkg-buildpackage: source package cloudstack
> dpkg-buildpackage: source version 4.10.0-SNAPSHOT
> dpkg-buildpackage: source changed by the Apache CloudStack project 

> dpkg-buildpackage: host architecture amd64
>  dpkg-source --before-build cloudstack
> dpkg-checkbuilddeps: Unmet build dependencies: python-mysql.connector
> dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied; 
aborting.
> dpkg-buildpackage: warning: (Use -d flag to override.)

after editing debian/control using 
`:%s/python-mysql.connector/mysql-connector-python/g`, it worked fine


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

[GitHub] cloudstack issue #1626: [blocker] Fix systemvm template build

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1626
  
@rhtyd @blueorangutan where can I see the test results? What tests were 
executed, what succeeded, what failed if any, failure/success logs etc.


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

[GitHub] cloudstack issue #1631: Fix debian build error due to commit 3315eb5

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
@karuturi I've fixed the issue, it was env config related on one of the 
slaves. Since debian repo got built successfully. We can merge your PR.


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

[GitHub] cloudstack issue #1631: Fix debian build error due to commit 3315eb5

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
ok. thanks merging 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 #1631: Fix debian build error due to commit 3315eb5

[asfgit]

Github user asfgit closed the pull request at:

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


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

[Rohit Yadav]

Thanks Rene, Wido and Rajani for the feedback.

Once we can have the system working as we wanted, we will publish wiki/docs on 
how we can collaboratively setup our own test environments that can be used in 
some federated way to distribute build-test load. Trillian is already open and 
our current infra uses the same repo (i.e. there is no secrets or fork) as 
anyone else can: https://github.com/shapeblue/Trillian

For now, I've added a restriction to allow only our RMs to build packages etc. 
The build bot and its background infra is an experiment, and likely to change 
its vocabulary as well.

Regards.

From: Rajani Karuturi 
Sent: 08 August 2016 15:38:03
To: dev@cloudstack.apache.org
Cc: us...@cloudstack.apache.org
Subject: Re: Meet BlueOrangutan

This is great. Thanks for all the hardwork Rohit. Will start using it.

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

On Sat, Aug 6, 2016 at 2:44 PM, Rohit Yadav 
wrote:

> All,
>
>
> Meet blueorangutan [1], a Github bot account that will help us automate
> CloudStack (PR) testing [2][3] among other things.
>
>
> It works by polling Github notifications for the apache/cloudstack
> repository every minutes and then reacts to comments. We can post comments
> on a apache/cloudstack PR and ask @blueorangutan to perform certain build
> jobs such as building packages, then running Trillian [2] tests (across a
> set of hypervisors) using those packages, and finally report us the results.
>
>
> Since, the task of building packages and testing them are expensive. A
> typical packaging job may take up to 30 minutes, a typical Trillian [2][3]
> environment can take about 30 minutes to build/deploy a zone, and a
> Trillian (smoke) test run may take hours while an exhaustive Trillian
> (component+smoke) test run may take 3-4 days. Due to these reasons, for now
> the '@blueorangutan test' task is restricted to a selected Github users (my
> colleagues at ShapeBlue). Running Trillian test for each PR may be
> expensive, we may consider batching smaller thoroughly reviewed PRs, then
> create packages for a set of PRs and test them all at once as well.
>
>
> The task to build (centos6, centos7, debian) packages is relatively less
> expensive and anyone can request blueorangutan to build packages now by
> commenting '@blueorangutan package' on a PR.
>
>
> The great blue ape aims to be a quite friendly and polite bot, go on any
> apache/cloudstack PR and try:
>
> '@blueorangutan hello'
>
>
> Or, build package for a PR:
>
> '@blueorangutan package'
>
>
> Or, if it helps you build packages you may say:
>
> '@blueorangutan thanks'
>
>
> This is an experiment and I hope to improve this over time, any feedback
> and comments are welcome.
>
>
> [1] https://github.com/blueorangutan
>
> [2] http://www.shapeblue.com/trillian-flexible-on-demand-
> individual-cloud-environment-creation/
>
> [3] http://www.shapeblue.com/cloudstack-test-automation-
> with-trillian-and-jenkins/
>
> Regards.
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

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

[GitHub] cloudstack issue #1630: Add projectid to project details page

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1630
  
Packaging result: ✔centos6 ✔centos7 ✔debian repo: 
http://packages.shapeblue.com/cloudstack/pr/1630
Job ID-71


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

[GitHub] cloudstack issue #1631: Fix debian build error due to commit 3315eb5

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1631
  
Packaging result: ✔centos6 ✔centos7 ✔debian repo: 
http://packages.shapeblue.com/cloudstack/pr/1631
Job ID-72


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

[GitHub] cloudstack issue #1626: [blocker] Fix systemvm template build

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1626
  
@karuturi I'll work on it, get blueorangutan to upload them to the comments 
or someplace else. For now, you may see the build log attached in this comment;


[systemfix-job17.txt](https://github.com/apache/cloudstack/files/406707/systemfix-job17.txt)



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

[GitHub] cloudstack issue #1115: CLOUDSTACK-9064: The users should be able to create ...

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1115
  
@abhinandanprateek was this merged in 4.9 as well?


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

[GitHub] cloudstack issue #1115: CLOUDSTACK-9064: The users should be able to create ...

[abhinandanprateek]

Github user abhinandanprateek commented on the issue:

https://github.com/apache/cloudstack/pull/1115
  
@rhtyd yes it is merged in 4.9 as well.


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

[GitHub] cloudstack issue #1115: CLOUDSTACK-9064: The users should be able to create ...

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1115
  
@abhinandanprateek great 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 issue #1054: CLOUDSTACK-8818: Use MySQL native connector with Pyt...

[wido]

Github user wido commented on the issue:

https://github.com/apache/cloudstack/pull/1054
  
Why is t hat required? The package is also available for 12.04: 
http://packages.ubuntu.com/precise/python-mysql.connector


---
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-docs-rn pull request #29: 4.9

[pdion891]

GitHub user pdion891 opened a pull request:

https://github.com/apache/cloudstack-docs-rn/pull/29

4.9

Please confirm it make sense to add a new package repo for the MySQL driver.

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

$ git pull https://github.com/cloudops/cloudstack-docs-rn 4.9

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

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


commit 0cfe73b39ac84ea1b9ef764a2eddba7ba48e2bf5
Author: Will Stevens 
Date:   2016-08-01T20:20:49Z

initial commit of the 4.9 changes

commit c083230f81dc23a4e0fd8a947f08fe6f8519ec17
Author: Will Stevens 
Date:   2016-08-03T19:11:28Z

updated the 'about' section

commit 166cdbf2574f1a0417611f681c3d88e843d62b12
Author: Will Stevens 
Date:   2016-08-04T20:39:31Z

updated known issues

commit a13414718c182f5a935b99d8f95e5c89ec9bdca6
Author: Pierre-Luc Dion 
Date:   2016-08-06T18:09:20Z

complete upgrade paths to 4.9




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

[GitHub] cloudstack issue #1054: CLOUDSTACK-8818: Use MySQL native connector with Pyt...

[pdion891]

Github user pdion891 commented on the issue:

https://github.com/apache/cloudstack/pull/1054
  
Are you saying it's not like CentOS which require to install 
mysq-connector-python from mysql repo [1], on ubuntu the package would have not 
been renamed ?

[1] 
https://github.com/cloudops/cloudstack-docs-rn/blob/4.9/source/upgrade/_mysql_connector.rst



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

[GitHub] cloudstack issue #1054: CLOUDSTACK-8818: Use MySQL native connector with Pyt...

[wido]

Github user wido commented on the issue:

https://github.com/apache/cloudstack/pull/1054
  
No, it isn't indeed.

``apt-get dist-upgrade``

That will show you that new dependencies are required for install and it 
will download them. No manual need for downloading a .deb file and installing 
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-docs-rn issue #29: 4.9

[swill]

Github user swill commented on the issue:

https://github.com/apache/cloudstack-docs-rn/pull/29
  
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.
---

Please add me to Jira Contributors List

[Frank Maximus]

Hi,

I want to assign a jira issue I created to myself.
Can my account *fmaximus* be added to the contributors list.

Thanks in advance,



*Frank Maximus *

Senior Software Development Engineer

*nuage*networks.net

[GitHub] cloudstack issue #1054: CLOUDSTACK-8818: Use MySQL native connector with Pyt...

[pdion891]

Github user pdion891 commented on the issue:

https://github.com/apache/cloudstack/pull/1054
  
ok, thanks, I will make sure the doc reflect that. 

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

[VOTE] Apache Cloudstack 4.8.1 RC2

[Will Stevens]

Hi All,

Sorry for the version mix up with RC1.  This will be the 4.8.1 release, not
the 4.8.2 release.

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

Git Branch and Commit SH:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=
shortlog;h=refs/heads/4.8.1-RC20160808T1006
Commit: a63db21d16072821a1e27473813fddf36accfdd4

List of changes will be produced with the release notes once the RC passes.

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


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

Vote will be open for 72 hours.

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

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

Re: [VOTE] Apache Cloudstack 4.8.2 RC1

[Will Stevens]

I have pushed a new vote for RC2.  Sorry for the mix up.  The release
should have been 4.8.1 and I made a mistake and put it as 4.8.2 for RC1.

Sorry for the confusion...

On Fri, Aug 5, 2016 at 9:44 PM, Will Stevens 
wrote:

> Yes. I think I should stop the vote and fix this. Thx...
>
> On Aug 5, 2016 7:56 PM, "Milamber"  wrote:
>
>> if I change the version in ./tools/checkstyle/pom.xml to 4.8.2, I can
>> build the debian packages successfully.
>> Note I use the git tag 4.8.2RC1 to build, but the tar.bz2 archives have
>> the 4.8.1 version for checkstyle pom.xml file too.
>>
>> Perhaps, Will, you must stop the vote, fixes, and launch a RC2?
>>
>> One question: this issue exist with the CentOS build?
>>
>>
>>
>> On 05/08/2016 20:50, Milamber wrote:
>>
>>
>> On 05/08/2016 22:45, Will Stevens wrote:
>>
>>> I will look into this.  Thanks...
>>>
>>> *Will STEVENS*
>>> Lead Developer
>>>
>>> *CloudOps* *| *Cloud Solutions Experts
>>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>>> w cloudops.com *|* tw @CloudOps_
>>>
>>> On Fri, Aug 5, 2016 at 3:50 PM, Milamber  wrote:
>>>
>>> Hello,

 I have this error when I try to build the debian packages (on ubuntu
 14.04)

 [INFO] --- maven-remote-resources-plugin:1.3:process (default) @
 cloudstack-framework ---
 [INFO] Building jar: /root/CS/cloudstack-dev/tools/
 checkstyle/target/checkstyle-4.8.1.jar

 [...]

 [ERROR] Failed to execute goal org.apache.maven.plugins:maven
 -checkstyle-plugin:2.11:check
 (cloudstack-checkstyle) on project cloud-maven-standard: Execution
 cloudstack-checkstyle of goal org.apache.maven.plugins:maven
 -checkstyle-plugin:2.11:check
 failed: Plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.11 or
 one of its dependencies could not be resolved: Failure to find
 org.apache.cloudstack:checkstyle:jar:4.8.2 in
 http://repo.maven.apache.org/maven2 was cached in the local repository,
 resolution will not be reattempted until the update interval of central
 has
 elapsed or updates are forced -> [Help 1]


 The version number 4.8.1 still in ./tools/checkstyle/pom.xml

 Probably the same issue with :
 ./services/iam/server/pom.xml
 ./services/iam/plugin/pom.xml
 ./services/console-proxy/plugin/pom.xml


 Milamber



 On 05/08/2016 18:51, Will Stevens wrote:

 Bump...
>
> On Thu, Aug 4, 2016 at 11:38 AM, Will Stevens <
> williamstev...@gmail.com>
> wrote:
>
> Link didn't get auto-created correctly, so here it is again for
> everyone
>
>> who is using something like gmail as a client:
>>
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=s
>> hortlog;h=refs/heads/4.8.2-RC20160804T1130
>>
>> On Thu, Aug 4, 2016 at 11:37 AM, Will Stevens <
>> williamstev...@gmail.com>
>> wrote:
>>
>> Hi All,
>>
>>> I've created a 4.8.2 release, with the following artifacts up for a
>>> vote:
>>>
>>> Git Branch and Commit SH:
>>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=s
>>> hortlog;h=refs/heads/4.8.2-RC20160804T1130
>>> Commit: d6fdde04357625e4d2d8b5ef09aafd2a0741dc17
>>>
>>> List of changes will be produced with the release notes once the RC
>>> passes.
>>>
>>> Source release (checksums and signatures are available at the same
>>> location):
>>> https://dist.apache.org/repos/dist/dev/cloudstack/4.8.2/
>>>
>>> PGP release keys (signed using CB818F64):
>>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>>
>>> Vote will be open for 72 hours.
>>>
>>> For sanity in tallying the vote, can PMC members please be sure to
>>> indicate "(binding)" with their vote?
>>>
>>> [ ] +1  approve
>>> [ ] +0  no opinion
>>> [ ] -1  disapprove (and reason why)
>>>
>>>
>>>
>>

[GitHub] cloudstack-docs-rn issue #29: 4.9

[swill]

Github user swill commented on the issue:

https://github.com/apache/cloudstack-docs-rn/pull/29
  
Doesn't look like the `api_changes` made it into this PR for some reason...


---
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-docs-rn issue #29: 4.9

[swill]

Github user swill commented on the issue:

https://github.com/apache/cloudstack-docs-rn/pull/29
  
Nevermind.  I missed it because it was compressed `833 additions, 75 
deletions not shown because the diff is too large. Please use a local Git 
client to view these 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 issue #1622: Adding missing bits field to TemplateResponse

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1622
  
@ProjectMoon the URI exception is caused by a attempting to parse an 
unrecognized/unregistered scheme (lswitch).  It would be a problem at runtime 
for the management server, and need to be addressed.


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

[4.9.0] new mysql connector

[Pierre-Luc Dion]

Hi,

>From what I'm seeing we need to upgrade the MySQL connector for Python with
4.9.0 on CentOS.

Here is the suggested path, tested on CentOS6 [1]. This snipped will be
part of the upgrade and install instructions. Also, look like these steps
are not required on Ubuntu 14.04, did any one can confirmed we are good on
Ubuntu 14.04 ?


[1]
https://github.com/cloudops/cloudstack-docs-rn/blob/15624a834e1d6e5c4dfb89e0f0bab3218d8b4eea/source/upgrade/_mysql_connector.rst

Also, Please review the PR:
https://github.com/apache/cloudstack-docs-rn/pull/29

Thanks,

PL

Re: [VOTE] Apache Cloudstack 4.8.2 RC1

[Chiradeep Vittal]

With this release, is ACS still dependent on downloads.cloud.com in any way?

On Mon, Aug 8, 2016 at 7:31 AM, Will Stevens 
wrote:

> I have pushed a new vote for RC2.  Sorry for the mix up.  The release
> should have been 4.8.1 and I made a mistake and put it as 4.8.2 for RC1.
>
> Sorry for the confusion...
>
> On Fri, Aug 5, 2016 at 9:44 PM, Will Stevens 
> wrote:
>
> > Yes. I think I should stop the vote and fix this. Thx...
> >
> > On Aug 5, 2016 7:56 PM, "Milamber"  wrote:
> >
> >> if I change the version in ./tools/checkstyle/pom.xml to 4.8.2, I can
> >> build the debian packages successfully.
> >> Note I use the git tag 4.8.2RC1 to build, but the tar.bz2 archives have
> >> the 4.8.1 version for checkstyle pom.xml file too.
> >>
> >> Perhaps, Will, you must stop the vote, fixes, and launch a RC2?
> >>
> >> One question: this issue exist with the CentOS build?
> >>
> >>
> >>
> >> On 05/08/2016 20:50, Milamber wrote:
> >>
> >>
> >> On 05/08/2016 22:45, Will Stevens wrote:
> >>
> >>> I will look into this.  Thanks...
> >>>
> >>> *Will STEVENS*
> >>> Lead Developer
> >>>
> >>> *CloudOps* *| *Cloud Solutions Experts
> >>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> >>> w cloudops.com *|* tw @CloudOps_
> >>>
> >>> On Fri, Aug 5, 2016 at 3:50 PM, Milamber  wrote:
> >>>
> >>> Hello,
> 
>  I have this error when I try to build the debian packages (on ubuntu
>  14.04)
> 
>  [INFO] --- maven-remote-resources-plugin:1.3:process (default) @
>  cloudstack-framework ---
>  [INFO] Building jar: /root/CS/cloudstack-dev/tools/
>  checkstyle/target/checkstyle-4.8.1.jar
> 
>  [...]
> 
>  [ERROR] Failed to execute goal org.apache.maven.plugins:maven
>  -checkstyle-plugin:2.11:check
>  (cloudstack-checkstyle) on project cloud-maven-standard: Execution
>  cloudstack-checkstyle of goal org.apache.maven.plugins:maven
>  -checkstyle-plugin:2.11:check
>  failed: Plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.11
> or
>  one of its dependencies could not be resolved: Failure to find
>  org.apache.cloudstack:checkstyle:jar:4.8.2 in
>  http://repo.maven.apache.org/maven2 was cached in the local
> repository,
>  resolution will not be reattempted until the update interval of
> central
>  has
>  elapsed or updates are forced -> [Help 1]
> 
> 
>  The version number 4.8.1 still in ./tools/checkstyle/pom.xml
> 
>  Probably the same issue with :
>  ./services/iam/server/pom.xml
>  ./services/iam/plugin/pom.xml
>  ./services/console-proxy/plugin/pom.xml
> 
> 
>  Milamber
> 
> 
> 
>  On 05/08/2016 18:51, Will Stevens wrote:
> 
>  Bump...
> >
> > On Thu, Aug 4, 2016 at 11:38 AM, Will Stevens <
> > williamstev...@gmail.com>
> > wrote:
> >
> > Link didn't get auto-created correctly, so here it is again for
> > everyone
> >
> >> who is using something like gmail as a client:
> >>
> >> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=s
> >> hortlog;h=refs/heads/4.8.2-RC20160804T1130
> >>
> >> On Thu, Aug 4, 2016 at 11:37 AM, Will Stevens <
> >> williamstev...@gmail.com>
> >> wrote:
> >>
> >> Hi All,
> >>
> >>> I've created a 4.8.2 release, with the following artifacts up for a
> >>> vote:
> >>>
> >>> Git Branch and Commit SH:
> >>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=s
> >>> hortlog;h=refs/heads/4.8.2-RC20160804T1130
> >>> Commit: d6fdde04357625e4d2d8b5ef09aafd2a0741dc17
> >>>
> >>> List of changes will be produced with the release notes once the RC
> >>> passes.
> >>>
> >>> Source release (checksums and signatures are available at the same
> >>> location):
> >>> https://dist.apache.org/repos/dist/dev/cloudstack/4.8.2/
> >>>
> >>> PGP release keys (signed using CB818F64):
> >>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >>>
> >>> Vote will be open for 72 hours.
> >>>
> >>> For sanity in tallying the vote, can PMC members please be sure to
> >>> indicate "(binding)" with their vote?
> >>>
> >>> [ ] +1  approve
> >>> [ ] +0  no opinion
> >>> [ ] -1  disapprove (and reason why)
> >>>
> >>>
> >>>
> >>
>

Re: [VOTE] Apache Cloudstack 4.8.2 RC1

[Will Stevens]

Not sure.  I don't think there were any changes on that front yet.

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Mon, Aug 8, 2016 at 4:49 PM, Chiradeep Vittal 
wrote:

> With this release, is ACS still dependent on downloads.cloud.com in any
> way?
>
> On Mon, Aug 8, 2016 at 7:31 AM, Will Stevens 
> wrote:
>
> > I have pushed a new vote for RC2.  Sorry for the mix up.  The release
> > should have been 4.8.1 and I made a mistake and put it as 4.8.2 for RC1.
> >
> > Sorry for the confusion...
> >
> > On Fri, Aug 5, 2016 at 9:44 PM, Will Stevens 
> > wrote:
> >
> > > Yes. I think I should stop the vote and fix this. Thx...
> > >
> > > On Aug 5, 2016 7:56 PM, "Milamber"  wrote:
> > >
> > >> if I change the version in ./tools/checkstyle/pom.xml to 4.8.2, I can
> > >> build the debian packages successfully.
> > >> Note I use the git tag 4.8.2RC1 to build, but the tar.bz2 archives
> have
> > >> the 4.8.1 version for checkstyle pom.xml file too.
> > >>
> > >> Perhaps, Will, you must stop the vote, fixes, and launch a RC2?
> > >>
> > >> One question: this issue exist with the CentOS build?
> > >>
> > >>
> > >>
> > >> On 05/08/2016 20:50, Milamber wrote:
> > >>
> > >>
> > >> On 05/08/2016 22:45, Will Stevens wrote:
> > >>
> > >>> I will look into this.  Thanks...
> > >>>
> > >>> *Will STEVENS*
> > >>> Lead Developer
> > >>>
> > >>> *CloudOps* *| *Cloud Solutions Experts
> > >>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> > >>> w cloudops.com *|* tw @CloudOps_
> > >>>
> > >>> On Fri, Aug 5, 2016 at 3:50 PM, Milamber 
> wrote:
> > >>>
> > >>> Hello,
> > 
> >  I have this error when I try to build the debian packages (on ubuntu
> >  14.04)
> > 
> >  [INFO] --- maven-remote-resources-plugin:1.3:process (default) @
> >  cloudstack-framework ---
> >  [INFO] Building jar: /root/CS/cloudstack-dev/tools/
> >  checkstyle/target/checkstyle-4.8.1.jar
> > 
> >  [...]
> > 
> >  [ERROR] Failed to execute goal org.apache.maven.plugins:maven
> >  -checkstyle-plugin:2.11:check
> >  (cloudstack-checkstyle) on project cloud-maven-standard: Execution
> >  cloudstack-checkstyle of goal org.apache.maven.plugins:maven
> >  -checkstyle-plugin:2.11:check
> >  failed: Plugin org.apache.maven.plugins:
> maven-checkstyle-plugin:2.11
> > or
> >  one of its dependencies could not be resolved: Failure to find
> >  org.apache.cloudstack:checkstyle:jar:4.8.2 in
> >  http://repo.maven.apache.org/maven2 was cached in the local
> > repository,
> >  resolution will not be reattempted until the update interval of
> > central
> >  has
> >  elapsed or updates are forced -> [Help 1]
> > 
> > 
> >  The version number 4.8.1 still in ./tools/checkstyle/pom.xml
> > 
> >  Probably the same issue with :
> >  ./services/iam/server/pom.xml
> >  ./services/iam/plugin/pom.xml
> >  ./services/console-proxy/plugin/pom.xml
> > 
> > 
> >  Milamber
> > 
> > 
> > 
> >  On 05/08/2016 18:51, Will Stevens wrote:
> > 
> >  Bump...
> > >
> > > On Thu, Aug 4, 2016 at 11:38 AM, Will Stevens <
> > > williamstev...@gmail.com>
> > > wrote:
> > >
> > > Link didn't get auto-created correctly, so here it is again for
> > > everyone
> > >
> > >> who is using something like gmail as a client:
> > >>
> > >> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=s
> > >> hortlog;h=refs/heads/4.8.2-RC20160804T1130
> > >>
> > >> On Thu, Aug 4, 2016 at 11:37 AM, Will Stevens <
> > >> williamstev...@gmail.com>
> > >> wrote:
> > >>
> > >> Hi All,
> > >>
> > >>> I've created a 4.8.2 release, with the following artifacts up
> for a
> > >>> vote:
> > >>>
> > >>> Git Branch and Commit SH:
> > >>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=s
> > >>> hortlog;h=refs/heads/4.8.2-RC20160804T1130
> > >>> Commit: d6fdde04357625e4d2d8b5ef09aafd2a0741dc17
> > >>>
> > >>> List of changes will be produced with the release notes once the
> RC
> > >>> passes.
> > >>>
> > >>> Source release (checksums and signatures are available at the
> same
> > >>> location):
> > >>> https://dist.apache.org/repos/dist/dev/cloudstack/4.8.2/
> > >>>
> > >>> PGP release keys (signed using CB818F64):
> > >>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> > >>>
> > >>> Vote will be open for 72 hours.
> > >>>
> > >>> For sanity in tallying the vote, can PMC members please be sure
> to
> > >>> indicate "(binding)" with their vote?
> > >>>
> > >>> [ ] +1  approve
> > >>> [ ] +0  no opinion
> > >>> [ ] -1  disapprove (and reason why)
> > >>>
> > >>>
> > >>>
> > >>
> >
>

Re: Please add me to Jira Contributors List

[ilya]

Who has the karma?

++ David Nalley

On 8/8/16 6:47 AM, Frank Maximus wrote:
> Hi,
> 
> I want to assign a jira issue I created to myself.
> Can my account *fmaximus* be added to the contributors list.
> 
> Thanks in advance,
> 
> 
> 
> *Frank Maximus *
> 
> Senior Software Development Engineer
> 
> *nuage*networks.net
> 

Re: SSLv3 on Apache Cloudstack 4.9.0 RC2

[ilya]

Hi Rohit,

No luck. We do have custom internal CA.

Also, why is "SSLV3_ALERT_HANDSHAKE_FAILURE" causing issue? i thought
SSLV3 failure handshake is a good response...

Running steps you've outline - did not seem to make any difference for
this issue. Setting verifysslcert false also dont help.




imusayev:~$ sudo pip install --upgrade requests[security] requests
Double requirement given: requests (already in requests[security],
name='requests')
Storing debug log for failure in /Users/imusayev/Library/Logs/pip.log


imusayev:~$ sudo pip install --upgrade
git+https://github.com/apache/cloudstack-cloudmonkey.git
Downloading/unpacking
git+https://github.com/apache/cloudstack-cloudmonkey.git
  Cloning https://github.com/apache/cloudstack-cloudmonkey.git to
/tmp/pip-ayrDw8-build
  Running setup.py (path:/tmp/pip-ayrDw8-build/setup.py) egg_info for
package from git+https://github.com/apache/cloudstack-cloudmonkey.git
If you're upgrading, run the following to enable parameter completion:
  cloudmonkey sync
  cloudmonkey set paramcompletion true
Parameter completion may fail, if the above is not run!

Requirement already up-to-date: Pygments>=1.5 in
/Library/Python/2.7/site-packages (from cloudmonkey==5.3.3)
Requirement already up-to-date: argcomplete in
/Library/Python/2.7/site-packages (from cloudmonkey==5.3.3)
Requirement already up-to-date: dicttoxml in
/Library/Python/2.7/site-packages (from cloudmonkey==5.3.3)
Requirement already up-to-date: prettytable>=0.6 in
/Library/Python/2.7/site-packages/prettytable-0.7.2-py2.7.egg (from
cloudmonkey==5.3.3)
Downloading/unpacking requests from
https://pypi.python.org/packages/f8/90/42d5e0d9b5c4c3629a3d99823bbc3748fb85616f0f7a45e79ba7908d4642/requests-2.11.0-py2.py3-none-any.whl#md5=369b7333bf2f710143a1b6678f2f214c
(from cloudmonkey==5.3.3)
  Downloading requests-2.11.0-py2.py3-none-any.whl (514kB): 514kB downloaded
Requirement already up-to-date: requests-toolbelt in
/Library/Python/2.7/site-packages (from cloudmonkey==5.3.3)
Installing collected packages: requests, cloudmonkey
  Found existing installation: requests 2.10.0
Uninstalling requests:
  Successfully uninstalled requests
  Found existing installation: cloudmonkey 5.3.2
Uninstalling cloudmonkey:
  Successfully uninstalled cloudmonkey
  Running setup.py install for cloudmonkey
If you're upgrading, run the following to enable parameter completion:
  cloudmonkey sync
  cloudmonkey set paramcompletion true
Parameter completion may fail, if the above is not run!

Installing cloudmonkey script to /usr/local/bin
Successfully installed requests cloudmonkey
Cleaning up...


imusayev:~$ cloudmonkey
☁ Apache CloudStack 🐵 cloudmonkey 5.3.3. Type help or ? to list commands.

Using management server profile: lab1-ssl

(lab1-ssl) > list zones
Connection refused by server: [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3
alert handshake failure (_ssl.c:590)
Error Authentication failed


(lab1-ssl) > set verifysslcert false
(lab1-ssl) > list zones
Connection refused by server: [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3
alert handshake failure (_ssl.c:590)
Error Authentication failed




On 8/6/16 1:33 AM, Rohit Yadav wrote:
> Hi Ilya,
> 
> 
> Can you try this:
> 
> sudo pip install --upgrade requests[security] requests
> 
> sudo pip install --upgrade 
> git+https://github.com/apache/cloudstack-cloudmonkey.git
> 
> 
> Then try again?
> 
> 
> As a workaround (in case of custom CA etc.) if it fails we can ask 
> cloudmonkey to ignore ssl certificate verification (connection will be still 
> secure, but cloudmonkey/requests won't verify the certificate) by running: 
> set verifysslcert false.
> 
> 
> Regards.
> 
> 
> From: ilya 
> Sent: 06 August 2016 06:15:25
> To: dev@cloudstack.apache.org
> Subject: Re: SSLv3 on Apache Cloudstack 4.9.0 RC2
> 
> Looks more like cloudmonkey 5.3.2 issue - i guess..
> 
> I confirmed i'm not serving SSLv3 - which would be Tomcat configuration
> issue anyway.
> 
> (lab1-ssl) > list zones
> Connection refused by server: [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3
> alert handshake failure (_ssl.c:590)
> Error Authentication failed
> 
> regards
> ilya
> 
> 
> On 8/5/16 3:32 PM, ilya wrote:
>> Has anyone tested Cloudstack 4.9.0 RC2 with SSL?
>>
>> Somehow, in my case tomcat reverted back to SSL v3 on port 8443 - which
>> is a big no-no.
>>
>> Please kindly check, alternatively if i dont hear from anyone i will
>> raise a blocker.
>>
>> On 8/3/16 10:39 PM, ilya wrote:
>>> Hi Will and Team
>>>
>>> Can someone point me to upgrade instructions if such exist.
>>>
>>> Would like to avoid learning through trial and error if possible.
>>>
>>> I will be testing upgrade and functionality of KVM & VMware Advanced
>>> Shared Zones from ACS4.5.2 to latest.
>>>
>>> Thanks
>>> ilya
>>>
>>> On 7/29/16 11:06 AM, ilya wrote:
 Hi Will

 What Remi mentioned sounds reasonable..

 I'll be spending sometime today

[GitHub] cloudstack issue #1630: Add projectid to project details page

[pdion891]

Github user pdion891 commented on the issue:

https://github.com/apache/cloudstack/pull/1630
  
I've added some more information in the project detail page as on following 
screenshot:


![prj1](https://cloud.githubusercontent.com/assets/5923502/17500440/995a4420-5da3-11e6-947e-b1fe66dabbfe.png)

![prj2](https://cloud.githubusercontent.com/assets/5923502/17500444/9de96912-5da3-11e6-80b3-ca125017beae.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.
---

Re: 4.10.0 release

[ilya]

Hi Guys,

Gave this thread a read - sorry i'm a bit late on this topic.

I agree with what Will, John and Rohit proposed. I also understand
Rajani's hesitancy - we dont want master to become a zoo.

In summary, i think the proposed workflow should avoid the zoo case and
give us structure that will yield some stability.

* 1 PR
* 1 Test (at a minimum) - be it Blue Orangutan, Bubble, Marvin,
screenshot - when tests dont apply, etc..
* 2 LGTMs
-> then merge

This should be a decent gating framework to avoid not well tested commits.

We just need a a consistent way of determining which tests should be ran.

Regards
ilya

On 8/4/16 10:19 AM, Will Stevens wrote:
> Yes, I agree with this.
> 
> CVEs need to be handled in security@ and will be added to the branches
> manually once they have been agreed upon there, so no PRs are needed for
> them.
> 
> I also agree that exceptions can be made for version changes in POMs and
> such because those are scripted changes which are part of the release
> process.  We may want to update the Release Procedure documentation to
> include some details around the commits which Rohit made (which I
> highlighted earlier) as those probably fall into this type of situation as
> well.  Not sure those can be scripted as part of cutting a release, but
> they are related to the release process, so detailed instructions for
> making those changes would be helpful to include.
> 
> In general, yes, your statements are all correct.  We may want to send out
> a bit of a notice on the dev@ list to highlight this.  For the last little
> while we have been having the RMs handle all of the merging of code, so we
> may want to officially inform the dev community that if you have commit
> access you can commit, but you need to follow these guidelines [1].  I
> would even go so far as to give a summary of the process.
> 
> *Example:*
> Create a GH PR with the change and get 2 LGTM (including proof of tests
> passing).
> 
> Once a PR is ready, commit it with the following flow.  Let's assume the
> change is for 4.8 and needs to be forward merged.
> 
> $ git fetch origin
> $ git checkout 4.8
> $ git rebase origin 4.8
> $ git pr 
> $ git log -p
> $ git push origin 4.8
> $ git checkout 4.9
> $ git rebase origin 4.9
> $ git fwd-merge 4.8
> $ git log -p
> $ git push origin 4.9
> $ git checkout master
> $ git rebase origin master
> $ git fwd-merge 4.9
> $ git log -p
> $ git push origin master
> 
> You can decipher this workflow from the Release Principles [1] document,
> but it is not nearly this clear.  I suggest we make this process more
> obvious so everyone knows what they are doing if they mae commits...
> 
> [1]
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+principles+for+Apache+CloudStack+4.6+and+up
> 
> *Will STEVENS*
> Lead Developer
> 
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
> 
> On Thu, Aug 4, 2016 at 12:17 PM, John Burwell 
> wrote:
> 
>> Will,
>>
>> My understanding of the release principles is that all changes must have a
>> PR with the exception of CVE fixes.  Since we must accept CVE fixes in
>> private, the 2 LGTM rule is applied on the security@ mailing list and on
>> private JIRA security ticket.  I would also say that the release commits
>> (e.g. tags, change of Maven versions in the POMs, etc) could also be
>> granted an exception to the rule.  Otherwise, yes, my understanding is that
>> everything else requires a PR.  Do you agree with that interpretation?
>>
>> Thanks,
>> -John
>>
>> P.S. I plan to consolidate the release section of the wiki shortly as we
>> have a number of topics that ostensibly conflict with each other.
>>
>>>
>> john.burw...@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London VA WC2N 4HSUK
>> @shapeblue
>>
>>
>>
>> On Aug 4, 2016, at 12:02 PM, Will Stevens  wrote:
>>>
 john.burw...@shapeblue.com
>>
>>
>