[GitHub] cloudstack issue #1615: CLOUDSTACK-9438: Fix for CLOUDSTACK-9252 - Make NFS ...

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1615
  
@jburwell I understand these comments: "help", "hello", "thanks", 
"package", "test"
Authorized contributors for kicking Trillian Jenkins test jobs are: 
['rhtyd', 'jburwell', 'murali-reddy', 'abhinandanprateek', 'PaulAngus', 
'borisstoyanov', 'karuturi']


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

[GitHub] cloudstack issue #1615: CLOUDSTACK-9438: Fix for CLOUDSTACK-9252 - Make NFS ...

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1615
  
@jburwell a Trillian-Jenkins test job (centos7 mgmt + vmware-55u3) has been 
kicked to run smoke tests against packages at 
http://packages.shapeblue.com/cloudstack/pr/1615


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

[GitHub] cloudstack issue #1615: CLOUDSTACK-9438: Fix for CLOUDSTACK-9252 - Make NFS ...

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1615
  
@blueorangutan help


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

[GitHub] cloudstack issue #1615: CLOUDSTACK-9438: Fix for CLOUDSTACK-9252 - Make NFS ...

[nvazquez]

Github user nvazquez commented on the issue:

https://github.com/apache/cloudstack/pull/1615
  
Sure, done


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

[GitHub] cloudstack issue #1615: CLOUDSTACK-9438: Fix for CLOUDSTACK-9252 - Make NFS ...

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1615
  
@nvazquez thanks for updates.  The Jenkins build failed.  It appears to be 
due a timeout.  Could you please force a rebuild by executing ``git commit 
--amend --no-edit && git push -f``?


---
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 #1545: CLOUDSTACK-8715: Add channel to Instances for Qemu G...

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1545
  
@wido thanks
@jburwell
With 4.9/lts we've reproduced many issues around patchviasocket timing out. 
If this is a better and more robust approach, should we have this fix in 
4.9/lts as well? This may require a new systemvmtemplate though. Given our 4.6 
based systemvm template is quite old (at least 8-9 months) and there have been 
security/openssl related updates, does it make sense to generate/publish a new 
systemvmtemplte for 4.9.1/lts? @wido is there a way we can avoid 
installation/generation of a new systemvm template 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 pull request #1632: Honor the forced parameter for stopVirtualMac...

[nathanejohnson]

GitHub user nathanejohnson opened a pull request:

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

Honor the forced parameter for stopVirtualMachine api call

CLOUDSTACK-9451

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

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

$ git pull https://github.com/myENA/cloudstack feature/honor_force_stop_vm

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

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


commit 8e8b511388df62eef9a5488677a57417c32d67db
Author: Nathan Johnson 
Date:   2016-08-09T19:16:00Z

Honor the forced parameter for stopVirtualMachine api call

CLOUDSTACK-9451




---
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: stopVirtualMachine command ignores the forced parameter

[Nathan Johnson]

Jeff Hair  wrote:

> Hi,
>
> I'm looking at the documentation and then the code for stopVirtualMachine.
> The forced parameter is passed down into the VM manager, where it seems to
> be ignored. This means that cleanupEvenIfFailed during VM stop will always
> be false, despite what the API command says. Going back to commit a4f4c986
> in 2013, we can see that the forced parameter was used. During subsequent
> refactoring, this seems to have vanished.



Jeff, after digging in I agree with you, this does look to be ignored.  So
I guess the question is: does cleanupEvenIfFailed mean the same thing as
the “forced" parameter?  If so, we could create a new overloaded
VMEntityManager / VMEntityManagerImpl stopvirtualmachine method with a bool
parameter, and then have that pass off to a new UserVMManagerImpl stop
method with a bool tacked on, and then it could pass this bool into
advanceStop.  Kind of messy, but overall wouldn’t be that much code to
change.

Thoughts?

Re: stopVirtualMachine command ignores the forced parameter

[Simon Weller]

Well, that's not good!


We were just about to implement this feature, so we'll go digging on this as 
well.


- Si


From: Jeff Hair 
Sent: Tuesday, August 9, 2016 12:21 PM
To: dev@cloudstack.apache.org
Subject: stopVirtualMachine command ignores the forced parameter

Hi,

I'm looking at the documentation and then the code for stopVirtualMachine.
The forced parameter is passed down into the VM manager, where it seems to
be ignored. This means that cleanupEvenIfFailed during VM stop will always
be false, despite what the API command says. Going back to commit a4f4c986
in 2013, we can see that the forced parameter was used. During subsequent
refactoring, this seems to have vanished.

[GitHub] cloudstack issue #1615: CLOUDSTACK-9438: Fix for CLOUDSTACK-9252 - Make NFS ...

[nvazquez]

Github user nvazquez commented on the issue:

https://github.com/apache/cloudstack/pull/1615
  
Done, thanks @jburwell for your 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.
---

stopVirtualMachine command ignores the forced parameter

[Jeff Hair]

Hi,

I'm looking at the documentation and then the code for stopVirtualMachine.
The forced parameter is passed down into the VM manager, where it seems to
be ignored. This means that cleanupEvenIfFailed during VM stop will always
be false, despite what the API command says. Going back to commit a4f4c986
in 2013, we can see that the forced parameter was used. During subsequent
refactoring, this seems to have vanished.

[GitHub] cloudstack issue #1615: CLOUDSTACK-9438: Fix for CLOUDSTACK-9252 - Make NFS ...

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1615
  
@nvazquez looking good.  One small item on the ``checkstate`` comment.  
Also, could you please squash your commits?


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

[jburwell]

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

https://github.com/apache/cloudstack/pull/1615#discussion_r74079012
  
--- Diff: server/src/com/cloud/storage/ImageStoreDetailsUtil.java ---
@@ -20,48 +20,68 @@
 
 import javax.inject.Inject;
 
+import org.apache.cloudstack.framework.config.dao.ConfigurationDao;
+import org.apache.cloudstack.framework.config.impl.ConfigurationVO;
 import org.apache.cloudstack.storage.datastore.db.ImageStoreDao;
 import org.apache.cloudstack.storage.datastore.db.ImageStoreDetailsDao;
 import org.apache.cloudstack.storage.datastore.db.ImageStoreVO;
 
+import com.cloud.capacity.CapacityManager;
+
 public class ImageStoreDetailsUtil {
 
 @Inject
 protected ImageStoreDao imageStoreDao;
 @Inject
 protected ImageStoreDetailsDao imageStoreDetailsDao;
+@Inject
+protected ConfigurationDao configurationDao;
 
 /**
- * Obtain NFS protocol version (if provided) for a store id.
- * It can be set by adding an entry in {@code image_store_details} 
table, providing {@code name=nfs.version} and {@code value=X} (e.g. 3)
+ * Retrieve global secondary storage NFS version default value
+ * @return global default value
+ */
+protected Integer getGlobalDefaultNfsVersion(){
+ConfigurationVO globalNfsVersion = 
configurationDao.findByName(CapacityManager.ImageStoreNFSVersion.key());
+String value = globalNfsVersion.getValue();
--- End diff --

@nvazquez that seems like a good solution.  Also, please use 
``Preconditions.checkState(globalNfsVersion !=null, "Unable to find global NFS 
version for version key" + CapacityManager.ImageStoreNFSVersion.key())`` to 
help someone understand why it happened in the unlikely event it occurs.


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

[nvazquez]

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

https://github.com/apache/cloudstack/pull/1615#discussion_r74068727
  
--- Diff: server/src/com/cloud/storage/ImageStoreDetailsUtil.java ---
@@ -20,48 +20,68 @@
 
 import javax.inject.Inject;
 
+import org.apache.cloudstack.framework.config.dao.ConfigurationDao;
+import org.apache.cloudstack.framework.config.impl.ConfigurationVO;
 import org.apache.cloudstack.storage.datastore.db.ImageStoreDao;
 import org.apache.cloudstack.storage.datastore.db.ImageStoreDetailsDao;
 import org.apache.cloudstack.storage.datastore.db.ImageStoreVO;
 
+import com.cloud.capacity.CapacityManager;
+
 public class ImageStoreDetailsUtil {
 
 @Inject
 protected ImageStoreDao imageStoreDao;
 @Inject
 protected ImageStoreDetailsDao imageStoreDetailsDao;
+@Inject
+protected ConfigurationDao configurationDao;
 
 /**
- * Obtain NFS protocol version (if provided) for a store id.
- * It can be set by adding an entry in {@code image_store_details} 
table, providing {@code name=nfs.version} and {@code value=X} (e.g. 3)
+ * Retrieve global secondary storage NFS version default value
+ * @return global default value
+ */
+protected Integer getGlobalDefaultNfsVersion(){
+ConfigurationVO globalNfsVersion = 
configurationDao.findByName(CapacityManager.ImageStoreNFSVersion.key());
+String value = globalNfsVersion.getValue();
--- End diff --

@jburwell I didn't consider it because configuration will be added and it 
will be present unless it is explicitly deleted from db. Anyways, I can add 
`Preconditions.checkState(globalNfsVersion != null)` do you agree?


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

[nvazquez]

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

https://github.com/apache/cloudstack/pull/1615#discussion_r74067494
  
--- Diff: server/src/com/cloud/storage/ImageStoreDetailsUtil.java ---
@@ -20,48 +20,68 @@
 
 import javax.inject.Inject;
 
+import org.apache.cloudstack.framework.config.dao.ConfigurationDao;
+import org.apache.cloudstack.framework.config.impl.ConfigurationVO;
 import org.apache.cloudstack.storage.datastore.db.ImageStoreDao;
 import org.apache.cloudstack.storage.datastore.db.ImageStoreDetailsDao;
 import org.apache.cloudstack.storage.datastore.db.ImageStoreVO;
 
+import com.cloud.capacity.CapacityManager;
+
 public class ImageStoreDetailsUtil {
 
 @Inject
 protected ImageStoreDao imageStoreDao;
 @Inject
 protected ImageStoreDetailsDao imageStoreDetailsDao;
+@Inject
+protected ConfigurationDao configurationDao;
 
 /**
- * Obtain NFS protocol version (if provided) for a store id.
- * It can be set by adding an entry in {@code image_store_details} 
table, providing {@code name=nfs.version} and {@code value=X} (e.g. 3)
+ * Retrieve global secondary storage NFS version default value
+ * @return global default value
+ */
+protected Integer getGlobalDefaultNfsVersion(){
+ConfigurationVO globalNfsVersion = 
configurationDao.findByName(CapacityManager.ImageStoreNFSVersion.key());
+String value = globalNfsVersion.getValue();
+return (value != null ? Integer.valueOf(value) : null);
+}
+/**
+ * Obtain NFS protocol version (if provided) for a store id, if not 
use default config value
  * @param storeId image store id
- * @return {@code null} if {@code nfs.version} is not found for 
storeId 
- * {@code X} if {@code nfs.version} is found found for storeId
+ * @return {@code null} if {@code secstorage.nfs.version} is not found 
for storeId 
+ * {@code X} if {@code secstorage.nfs.version} is found found for 
storeId
  */
 public Integer getNfsVersion(long storeId) throws 
NumberFormatException {
-String nfsVersion = null;
+Integer nfsVersion;
 if (imageStoreDetailsDao.getDetails(storeId) != null){
 Map storeDetails = 
imageStoreDetailsDao.getDetails(storeId);
--- End diff --

Done


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

[nvazquez]

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

https://github.com/apache/cloudstack/pull/1615#discussion_r74067440
  
--- Diff: server/src/com/cloud/configuration/ConfigurationManagerImpl.java 
---
@@ -520,6 +528,16 @@ public String updateConfiguration(final long userId, 
final String name, final St
 _accountDetailsDao.update(accountDetailVO.getId(), 
accountDetailVO);
 }
 break;
+
+case ImageStore:
+final ImageStoreVO imgStore = 
_imageStoreDao.findById(resourceId);
+if (imgStore == null) {
+throw new InvalidParameterValueException("unable to 
find image store by id " + resourceId);
--- End diff --

Thanks, I'll take it into account for next time


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

[GitHub] cloudstack issue #1602: CLOUDSTACK-9422: Granular 'vmware.create.full.clone'...

[nvazquez]

Github user nvazquez commented on the issue:

https://github.com/apache/cloudstack/pull/1602
  
Thanks @jburwell for your review! I refactored based on your comments.


---
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 #1545: CLOUDSTACK-8715: Add channel to Instances for Qemu G...

[wido]

Github user wido commented on the issue:

https://github.com/apache/cloudstack/pull/1545
  
@rhtyd: Yes, it does. It installs the Qemu Guest Agent into the SSVM.


---
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 #1545: CLOUDSTACK-8715: Add channel to Instances for Qemu G...

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1545
  
LGTM, @wido looks like this will require a new systemvm template?


---
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: SSLv3 on Apache Cloudstack 4.9.0 RC2

[Rohit Yadav]

Hi Ilya,


The error is not specifically produced by cloudmonkey but from requests [1] 
which uses urllib/python. If you're on OSX, you may need to rebuild python with 
openssl supporting the specific cipher suite.


Can you share what is your host os (osx vs linux?) and the output of:


1. python -c 'import requests; print 
requests.packages.urllib3.util.ssl_.DEFAULT_CIPHERS;'


2. python -V


3. python -c "import ssl; print ssl.OPENSSL_VERSION"


If you're on OSX, you can try the following:


brew install OpenSSL

env ARCHFLAGS="-arch x86_64" LDFLAGS="-L/usr/local/opt/openssl/lib" 
CFLAGS="-I/usr/local/opt/openssl/include" pip install cryptography

pip install requests[security]


Otherwise, you can try this:

You can try to install the latest openssl/crypto pkgs:

sudo pip install --upgrade pyopenssl cryptography



[1] https://github.com/kennethreitz/requests/issues/2022


Regards.


From: ilya 
Sent: 09 August 2016 05:16:17
To: dev@cloudstack.apache.org
Subject: Re: SSLv3 on Apache Cloudstack 4.9.0 RC2

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 

Re: [4.9.0] new mysql connector

[Wido den Hollander]

> Op 9 augustus 2016 om 12:57 schreef Pierre-Luc Dion :
> 
> 
> Wido, after dist-upgrade you were running at Ubuntu 16.04, correct?
> 

No, that is what the name seems to suggest. The sources.list still contained 
the 14.04 sources.

dist-upgrade however installs additional dependencies when they are required by 
the new version of the package.

'upgrade' will tell you it held a package back due to a new dependency.

Wido

> On Aug 9, 2016 06:33, "Wido den Hollander"  wrote:
> 
> >
> > > Op 9 augustus 2016 om 12:30 schreef Rajani Karuturi :
> > >
> > >
> > > on a fresh install dist-upgrade didnt work for me.
> > > Doing apt-get install python-mysql.connector worked.
> > >
> >
> > Did you install the .deb packages using 'dpkg'? If so, that indeed doesn't
> > install dependencies.
> >
> > When installing using 'apt-get install' it will resolve dependencies.
> >
> > This is not a CloudStack packaging issue, that's how dpkg and apt work.
> >
> > Wido
> >
> > > ~ Rajani
> > > http://cloudplatform.accelerite.com/
> > >
> > > On August 9, 2016 at 1:07 PM, Wido den Hollander (w...@widodh.nl)
> > > wrote:
> > > Op 8 augustus 2016 om 22:29 schreef 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 ?
> > > For the vote I upgraded a 4.8.0 mgmt server to 4.9.0 under Ubuntu
> > > 14.04.
> > >
> > > I had to run apt-get dist-upgrade (not upgrade) so that it would
> > > install the new mysql connector. After that it worked just fine.
> > >
> > > Wido
> > >
> > > [1]
> > > https://github.com/cloudops/cloudstack-docs-rn/blob/
> > 15624a834e1d6e5c4dfb89e0f0bab3218d8b4eea/source/upgrade/_
> > mysql_connector.rst
> > > ( 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 (
> > https://github.com/apache/cloudstack-docs-rn/pull/29 )
> > >
> > > Thanks,
> > >
> > > PL
> >

Re: [4.9.0] new mysql connector

[Pierre-Luc Dion]

Wido, after dist-upgrade you were running at Ubuntu 16.04, correct?

On Aug 9, 2016 06:33, "Wido den Hollander"  wrote:

>
> > Op 9 augustus 2016 om 12:30 schreef Rajani Karuturi :
> >
> >
> > on a fresh install dist-upgrade didnt work for me.
> > Doing apt-get install python-mysql.connector worked.
> >
>
> Did you install the .deb packages using 'dpkg'? If so, that indeed doesn't
> install dependencies.
>
> When installing using 'apt-get install' it will resolve dependencies.
>
> This is not a CloudStack packaging issue, that's how dpkg and apt work.
>
> Wido
>
> > ~ Rajani
> > http://cloudplatform.accelerite.com/
> >
> > On August 9, 2016 at 1:07 PM, Wido den Hollander (w...@widodh.nl)
> > wrote:
> > Op 8 augustus 2016 om 22:29 schreef 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 ?
> > For the vote I upgraded a 4.8.0 mgmt server to 4.9.0 under Ubuntu
> > 14.04.
> >
> > I had to run apt-get dist-upgrade (not upgrade) so that it would
> > install the new mysql connector. After that it worked just fine.
> >
> > Wido
> >
> > [1]
> > https://github.com/cloudops/cloudstack-docs-rn/blob/
> 15624a834e1d6e5c4dfb89e0f0bab3218d8b4eea/source/upgrade/_
> mysql_connector.rst
> > ( 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 (
> https://github.com/apache/cloudstack-docs-rn/pull/29 )
> >
> > Thanks,
> >
> > PL
>

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


---
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.9.0] new mysql connector

[Wido den Hollander]

> Op 9 augustus 2016 om 12:30 schreef Rajani Karuturi :
> 
> 
> on a fresh install dist-upgrade didnt work for me.
> Doing apt-get install python-mysql.connector worked.
> 

Did you install the .deb packages using 'dpkg'? If so, that indeed doesn't 
install dependencies.

When installing using 'apt-get install' it will resolve dependencies.

This is not a CloudStack packaging issue, that's how dpkg and apt work.

Wido

> ~ Rajani
> http://cloudplatform.accelerite.com/
> 
> On August 9, 2016 at 1:07 PM, Wido den Hollander (w...@widodh.nl)
> wrote:
> Op 8 augustus 2016 om 22:29 schreef 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 ?
> For the vote I upgraded a 4.8.0 mgmt server to 4.9.0 under Ubuntu
> 14.04.
> 
> I had to run apt-get dist-upgrade (not upgrade) so that it would
> install the new mysql connector. After that it worked just fine.
> 
> Wido
> 
> [1]
> https://github.com/cloudops/cloudstack-docs-rn/blob/15624a834e1d6e5c4dfb89e0f0bab3218d8b4eea/source/upgrade/_mysql_connector.rst
> ( 
> 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 ( 
> https://github.com/apache/cloudstack-docs-rn/pull/29 )
> 
> Thanks,
> 
> PL

Re: [4.9.0] new mysql connector

[Rajani Karuturi]

on a fresh install dist-upgrade didnt work for me.
Doing apt-get install python-mysql.connector worked.

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

On August 9, 2016 at 1:07 PM, Wido den Hollander (w...@widodh.nl)
wrote:
Op 8 augustus 2016 om 22:29 schreef 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 ?
For the vote I upgraded a 4.8.0 mgmt server to 4.9.0 under Ubuntu
14.04.

I had to run apt-get dist-upgrade (not upgrade) so that it would
install the new mysql connector. After that it worked just fine.

Wido

[1]
https://github.com/cloudops/cloudstack-docs-rn/blob/15624a834e1d6e5c4dfb89e0f0bab3218d8b4eea/source/upgrade/_mysql_connector.rst
( 
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 ( 
https://github.com/apache/cloudstack-docs-rn/pull/29 )

Thanks,

PL

Re: Please add me to Jira Contributors List

[Rajani Karuturi]

Done.

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

On August 8, 2016 at 7:18 PM, Frank Maximus
(frank.maxi...@nuagenetworks.net) 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

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

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1626
  
Thanks @karuturi 


---
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 #1626: [blocker] Fix systemvm template build

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 that is fine, we're not doing systemvmtemplate for 4.9 or maybe 
4.10. This fixes the systemvm template build issue, so please merge on 4.9 
branch and fwd merge it. It's because, we may want to build newer 
systemvmtemplate that is still 4.6 compatible, newer systemvm template may 
bring updates to openssl and other security related updates only.


---
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
  
can you rebase this PR to master? we wont be doing a new systemvm for 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 #1626: [blocker] Fix systemvm template build

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1626
  
ok. merging this 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.
---

Re: [4.9.0] new mysql connector

[Wido den Hollander]

> Op 8 augustus 2016 om 22:29 schreef 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 ?
> 

For the vote I upgraded a 4.8.0 mgmt server to 4.9.0 under Ubuntu 14.04.

I had to run apt-get dist-upgrade (not upgrade) so that it would install the 
new mysql connector. After that it worked just fine.

Wido

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

[GitHub] cloudstack-docs-rn pull request #29: 4.9

[karuturi]

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

https://github.com/apache/cloudstack-docs-rn/pull/29#discussion_r74007970
  
--- Diff: source/upgrade/_mysql_connector.rst ---
@@ -0,0 +1,33 @@
+Install new MySQL connector
+^^^
+
+Apache CloudStack |version| require an upgrade of the MySQL connector on 
CentOS.
--- End diff --

for debian, we should document to install 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.
---