date:20170203

[GitHub] cloudstack pull request #:

2017-02-03 Thread pdion891

Github user pdion891 commented on the pull request:


https://github.com/apache/cloudstack/commit/eabf862ba9751bcdbe18a6cc9b91f2ae48472cab#commitcomment-20741478
  
In setup/db/db/schema-4910to4920.sql:
In setup/db/db/schema-4910to4920.sql on line 217:
could it be possible there is a missing `;` at the last line ?


---
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 #1929: CLOUDSTACK-9770: fix missing ip routes in VR

2017-02-03 Thread milamberspace

Github user milamberspace commented on the issue:

https://github.com/apache/cloudstack/pull/1929
  
LGTM tested in real conditions with success


---
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 #1929: CLOUDSTACK-9770: fix missing ip routes in VR

2017-02-03 Thread milamberspace

Github user milamberspace commented on the issue:

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

@DaanHoogland Yes I've already tested with success the patch. Please see 
Jira

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

The PR by @ustcweizhou  is 
https://github.com/apache/cloudstack/pull/1929


---
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 #1929: CLOUDSTACK-9770: fix missing ip routes in VR

2017-02-03 Thread milamberspace

Github user milamberspace commented on the issue:

https://github.com/apache/cloudstack/pull/1929
  
@DaanHoogland Yes I've already tested with success the patch. Please see 
Jira



---
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 #1644: Honors the snapshot.backup.rightafter configuration ...

2017-02-03 Thread nathanejohnson

Github user nathanejohnson commented on the issue:

https://github.com/apache/cloudstack/pull/1644
  
@karuturi Just checking in on this, at one point it looked like we were 
going to possibly roll this out as a maintenance release of 4.8, and there is 
another PR open with the same changes against 4.8.  What would you like to do 
with this moving forward?

Here is a link to the other PR in question:

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


---
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 #1929: CLOUDSTACK-9770: fix missing ip routes in VR

2017-02-03 Thread DaanHoogland

Github user DaanHoogland commented on the issue:

https://github.com/apache/cloudstack/pull/1929
  
@milamberspace could you try with this patch? I think @ustcweizhou solved 
your problem with the default route


---
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-www issue #34: Remove link to “planet.apache.org” and update ...

2017-02-03 Thread rafaelweingartner

Github user rafaelweingartner commented on the issue:

https://github.com/apache/cloudstack-www/pull/34
  
I agree with you. The friendlier the better.

Sometimes we might think that those details are not important only because 
we have been around for so long here. On the other hand, a newcomer may feel 
lost without these details. I will add a more detailed step by step tonight.



---
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-www issue #34: Remove link to “planet.apache.org” and update ...

2017-02-03 Thread swill

Github user swill commented on the issue:

https://github.com/apache/cloudstack-www/pull/34
  
Unless you know how everything works behind the scene (which is like nobody 
pretty much), then it can be hard to understand initially.  I think this makes 
it easier for more people to contribute to the documentation and the website.

It is only a committer who has to publish the change.  It may be a random 
person who is not a committer who creates the PR though.  That would be 
awesome.  :)


---
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-www issue #34: Remove link to “planet.apache.org” and update ...

2017-02-03 Thread rafaelweingartner

Github user rafaelweingartner commented on the issue:

https://github.com/apache/cloudstack-www/pull/34
  
yeas, it makes.

I was assuming that any commiter that gets to here should be used to these 
steps; but, I will add a more detailed set of instructions like the one you 
proposed.


---
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-www issue #34: Remove link to “planet.apache.org” and update ...

2017-02-03 Thread rafaelweingartner

Github user rafaelweingartner commented on the issue:

https://github.com/apache/cloudstack-www/pull/34
  
Sure I do not mind.
I was assuming that the repo was going to be at 
https://git-wip-us.apache.org, but I added information in the README regarding 
this one.

Do you guys think we need to add/remove something?


---
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-www issue #34: Remove link to “planet.apache.org” and update ...

2017-02-03 Thread swill

Github user swill commented on the issue:

https://github.com/apache/cloudstack-www/pull/34

If you wouldn't mind, we might as well.  We also need to document that the
upstream ASF repo is at `
https://git-wip-us.apache.org/repos/asf/cloudstack-www.git`.  I don't think
that is documented anywhere, so committers won't know where to setup their
remotes as in order to push changes.  Thanks Rafael...  :)

On Fri, Feb 3, 2017 at 2:17 PM, Rafael WeingÃ¤rtner 
 wrote:

> I agree with @swill .
>
> If you want, I could add these details in the README about the integration
> between the web server at ASF and this "cloudstack-www" repo.
>
> â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> ,
> or mute the thread
> 

> .
>

---
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-www issue #34: Remove link to “planet.apache.org” and update ...

2017-02-03 Thread rafaelweingartner

Github user rafaelweingartner commented on the issue:

https://github.com/apache/cloudstack-www/pull/34
  
I agree with @swill.

If you want, I could add these details in the README about the integration 
between the web server at ASF and this "cloudstack-www" repo.


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

[GitHub] cloudstack issue #1913: CLOUDSTACK-9752: [Vmware] Optimization of volume att...

2017-02-03 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1913
  
Trillian test result (tid-801)
Environment: vmware-60u2 (x2), Advanced Networking with Mgmt server 7
Total time taken: 41486 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1913-t801-vmware-60u2.zip
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: 
/marvin/tests/smoke/test_routers_network_ops.py
Intermitten failure detected: /marvin/tests/smoke/test_routers.py
Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Test completed. 48 look ok, 1 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_04_rvpc_privategw_static_routes | `Failure` | 801.37 | 
test_privategw_acl.py
test_01_vpc_site2site_vpn | Success | 330.63 | test_vpc_vpn.py
test_01_vpc_remote_access_vpn | Success | 146.22 | test_vpc_vpn.py
test_01_redundant_vpc_site2site_vpn | Success | 516.19 | test_vpc_vpn.py
test_02_VPC_default_routes | Success | 316.12 | test_vpc_router_nics.py
test_01_VPC_nics_after_destroy | Success | 675.68 | test_vpc_router_nics.py
test_05_rvpc_multi_tiers | Success | 578.48 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | Success | 1466.72 | 
test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 682.28 | test_vpc_redundant.py
test_02_redundant_VPC_default_routes | Success | 614.37 | 
test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1265.89 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 20.66 | test_volumes.py
test_06_download_detached_volume | Success | 50.39 | test_volumes.py
test_05_detach_volume | Success | 100.24 | test_volumes.py
test_04_delete_attached_volume | Success | 10.15 | test_volumes.py
test_03_download_attached_volume | Success | 15.22 | test_volumes.py
test_02_attach_volume | Success | 54.95 | test_volumes.py
test_01_create_volume | Success | 434.99 | test_volumes.py
test_03_delete_vm_snapshots | Success | 275.17 | test_vm_snapshots.py
test_02_revert_vm_snapshots | Success | 188.95 | test_vm_snapshots.py
test_01_test_vm_volume_snapshot | Success | 145.97 | test_vm_snapshots.py
test_01_create_vm_snapshots | Success | 161.65 | test_vm_snapshots.py
test_deploy_vm_multiple | Success | 206.75 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.02 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.61 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 125.21 | test_vm_life_cycle.py
test_08_migrate_vm | Success | 55.72 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.07 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 5.09 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 5.11 | test_vm_life_cycle.py
test_02_start_vm | Success | 15.15 | test_vm_life_cycle.py
test_01_stop_vm | Success | 5.09 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 191.28 | test_templates.py
test_08_list_system_templates | Success | 0.03 | test_templates.py
test_07_list_public_templates | Success | 0.03 | test_templates.py
test_05_template_permissions | Success | 0.16 | test_templates.py
test_04_extract_template | Success | 15.27 | test_templates.py
test_03_delete_template | Success | 5.08 | test_templates.py
test_02_edit_template | Success | 90.16 | test_templates.py
test_01_create_template | Success | 100.60 | test_templates.py
test_10_destroy_cpvm | Success | 226.34 | test_ssvm.py
test_09_destroy_ssvm | Success | 238.15 | test_ssvm.py
test_08_reboot_cpvm | Success | 156.34 | test_ssvm.py
test_07_reboot_ssvm | Success | 158.08 | test_ssvm.py
test_06_stop_cpvm | Success | 176.54 | test_ssvm.py
test_05_stop_ssvm | Success | 173.23 | test_ssvm.py
test_04_cpvm_internals | Success | 1.01 | test_ssvm.py
test_03_ssvm_internals | Success | 3.13 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.09 | test_ssvm.py
test_01_list_sec_storage_vm | Success | 0.14 | test_ssvm.py
test_01_snapshot_root_disk | Success | 21.01 | test_snapshots.py
test_04_change_offering_small | Success | 122.72 | test_service_offerings.py
test_03_delete_service_offering | Success | 0.03 | test_service_offerings.py
test_02_edit_service_offering | Success | 0.06 | test_service_offerings.py
test_01_create_service_offering | Success | 0.08 | test_service_offerings.py
test_02_sys_template_ready | Success | 0.09 | test_secondary_storage.py
test_01_sys_vm_start | Success | 0.12 | test_secondary_storage.py
test_09_reboot_router | Success | 120.69 | test_routers.py
test_08_start_router | Success |

[GitHub] cloudstack-www issue #34: Remove link to “planet.apache.org” and update ...

2017-02-03 Thread swill

Github user swill commented on the issue:

https://github.com/apache/cloudstack-www/pull/34
  
Ya, thats basically where I think we have netted out to.  The `site-asf` 
branch which tracks the compiled content is served by the ASF (from somewhere). 
 If we push compiled content to that branch, it goes live right away.

Now that we have gone through all these details, I don't think we should 
try to introduce an external dependency into this and just use it the way it 
currently is being done.  I think it really is the simplest solution and there 
doesn't seem to be major downsides.

I think one thing that could help all this is proper documentation of the 
process in the README, but that is a totally different thread and should not 
block this PR.


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

[GitHub] cloudstack-www issue #34: Remove link to “planet.apache.org” and update ...

2017-02-03 Thread rafaelweingartner

Github user rafaelweingartner commented on the issue:

https://github.com/apache/cloudstack-www/pull/34
  
After all that has been posted here, I am inclined to say that nothing 
would change.
The Jenkins would build/"compile" the HTML files, and then it has to commit 
to a repo that is synchronized with a web server, right?

Is the repo that provides the HTML   the cloudstack-www on ASF? Then 
nothing seems to change. We still keep versioning "compiled" HTML files and not 
just the source code. 

I might be missing some other details, though.


---
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 #1888: CLOUDSTACK-9710: Switch to JRE1.8

2017-02-03 Thread swill

Github user swill commented on the issue:

https://github.com/apache/cloudstack/pull/1888
  
Maybe we should be defaulting this file to Java 8 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 issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

2017-02-03 Thread swill

Github user swill commented on the issue:

https://github.com/apache/cloudstack/pull/1888
  
I found the issue.  `jenv` was not setting the `JAVA_HOME` correctly, so 
the following logic in `/etc/cloudstack/management/classpath.conf` was getting 
hit.
```
if ([ -z "$JAVA_HOME" ] || [ ! -d "$JAVA_HOME" ]) && [ -d 
/usr/lib/jvm/jre-1.7.0 ]; then
 export JAVA_HOME=/usr/lib/jvm/jre-1.7.0
fi
```

I modified this section to be the following and everything is working now.
```
if ([ -z "$JAVA_HOME" ] || [ ! -d "$JAVA_HOME" ]) && [ -d 
/usr/lib/jvm/jre-1.8.0 ]; then
 export JAVA_HOME=/usr/lib/jvm/jre-1.8.0
fi
```


---
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: Upgrade fails on Master

2017-02-03 Thread Will Stevens

Thanks for the tip Nicolas.

It turns out that 'jenv' was not setting the JAVA_HOME even though it had
Java8 configured as the active Java version.

Because of this, the file '/etc/cloudstack/management/classpath.conf' was
defaulting to Java7.

I commented that section and made it default to Java8 and everything works
again.

---
export CLASSPATH
#if ([ -z "$JAVA_HOME" ] || [ ! -d "$JAVA_HOME" ]) && [ -d
/usr/lib/jvm/jre-1.7.0 ]; then
# export JAVA_HOME=/usr/lib/jvm/jre-1.7.0
#fi
if ([ -z "$JAVA_HOME" ] || [ ! -d "$JAVA_HOME" ]) && [ -d
/usr/lib/jvm/jre-1.8.0 ]; then
 export JAVA_HOME=/usr/lib/jvm/jre-1.8.0
fi
PATH=$JAVA_HOME/bin:/sbin:/usr/sbin:$PATH
export PATH
---

Thanks for the help everyone...



*Will STEVENS*
Lead Developer



On Fri, Feb 3, 2017 at 11:57 AM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> The others already answered this one:
> "Unsupported major.minor version 52.0"
>
> I am assuming you are compiling with 1.8, and it seems you are using 1.7 or
> lower version.
>
>
> On Fri, Feb 3, 2017 at 11:48 AM, Nicolas Vazquez 
> wrote:
>
> > Hi Will,
> >
> > Did you try modifying /etc/cloudstack/management/classpath.conf file for
> > Tomcat to run using java 8?
> >
> > 2017-02-03 13:43 GMT-03:00 Daan Hoogland :
> >
> > > that's what wat cought my eye as well, and this is important for users
> to
> > > consider, So to must first upgrade java and then ACS.
> > >
> > > 
> > > From: Milamber 
> > > Sent: 03 February 2017 17:40:37
> > > To: dev@cloudstack.apache.org
> > > Subject: Re: Upgrade fails on Master
> > >
> > >
> > > Probably an issue with your java version on your Centos machine? now CS
> > > 4.10 need Java 8 to run.
> > >
> > >
> > > On 03/02/2017 15:12, Will Stevens wrote:
> > > > That was the 'management-server.log'...
> > > >
> > > > Here is the 'catalina.out' log.
> > > >
> > > > --- snip ---
> > > > Feb 03, 2017 2:22:56 PM org.apache.catalina.loader.WebappClassLoader
> > > > validateJarFile
> > > > INFO:
> > > > validateJarFile(/usr/share/cloudstack-management/webapps/
> > > client/WEB-INF/lib/tomcat-embed-core-8.0.30.jar)
> > > > - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending
> class:
> > > > javax/servlet/Servlet.class
> > > > Feb 03, 2017 2:22:56 PM org.apache.tomcat.util.modeler.Registry
> > > > registerComponent
> > > > SEVERE: Null component
> > > > Catalina:type=JspMonitor,name=jsp,WebModule=//localhost/
> > > client,J2EEApplication=none,J2EEServer=none
> > > > Feb 03, 2017 2:22:56 PM org.apache.catalina.startup.HostConfig
> > > > deployDirectory
> > > > SEVERE: Error deploying web application directory client
> > > > java.lang.UnsupportedClassVersionError:
> > > > org/apache/cloudstack/spring/module/web/
> CloudStackContextLoaderListene
> > r
> > > :
> > > > Unsupported major.minor version 52.0 (unable to load class
> > > > org.apache.cloudstack.spring.module.web.
> CloudStackContextLoaderListene
> > r)
> > > > at
> > > > org.apache.catalina.loader.WebappClassLoader.findClassInternal(
> > > WebappClassLoader.java:2334)
> > > > at
> > > > org.apache.catalina.loader.WebappClassLoader.findClass(
> > > WebappClassLoader.java:976)
> > > > at
> > > > org.apache.catalina.loader.WebappClassLoader.loadClass(
> > > WebappClassLoader.java:1450)
> > > > at
> > > > org.apache.catalina.loader.WebappClassLoader.loadClass(
> > > WebappClassLoader.java:1329)
> > > > at
> > > > org.apache.catalina.startup.WebAnnotationSet.loadClassAnnotation(
> > > WebAnnotationSet.java:145)
> > > > at
> > > > org.apache.catalina.startup.WebAnnotationSet.
> > > loadApplicationListenerAnnotations(WebAnnotationSet.java:73)
> > > > at
> > > > org.apache.catalina.startup.WebAnnotationSet.
> > loadApplicationAnnotations(
> > > WebAnnotationSet.java:56)
> > > > at
> > > > org.apache.catalina.startup.ContextConfig.
> > applicationAnnotationsConfig(
> > > ContextConfig.java:294)
> > > > at org.apache.catalina.startup.ContextConfig.start(
> > > ContextConfig.java:1046)
> > > > at
> > > > org.apache.catalina.startup.ContextConfig.lifecycleEvent(
> > > ContextConfig.java:265)
> > > > at
> > > > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(
> > > LifecycleSupport.java:142)
> > > > at org.apache.catalina.core.StandardContext.start(
> > > StandardContext.java:4650)
> > > > at
> > > > org.apache.catalina.core.ContainerBase.addChildInternal(
> > > ContainerBase.java:791)
> > > > at org.apache.catalina.core.ContainerBase.addChild(
> > > ContainerBase.java:771)
> > > > at org.apache.catalina.core.StandardHost.addChild(
> > StandardHost.java:526)
> > > > at
> > > > org.apache.catalina.startup.HostConfig.deployDirectory(
> > > HostConfig.java:1041)
> > > > at
> > > > org.apache.catalina.startup.HostConfig.deployDirectories(
> > > HostConfig.java:964)
> > > > at org.apache.catalina.startup.HostConfig.deployApps(
> > > HostConfig.java:502)
> > > >

[GitHub] cloudstack pull request #1929: CLOUDSTACK-9770: fix missing ip routes in VR

2017-02-03 Thread ustcweizhou

GitHub user ustcweizhou opened a pull request:

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

CLOUDSTACK-9770: fix missing ip routes in VR

In network VR, the routes to current subnets are missing in corresponding 
ip route Table.
It is a typo in commit 6749785caba78a9379e94bf3aaf0c1fbc44c5445
In VPC VR, it works fine.

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

$ git pull https://github.com/ustcweizhou/cloudstack VR-missing-route

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

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


commit 8c69cb1c1fd7ba93e021dca7d6e08dbaa831ccfa
Author: Wei Zhou 
Date:   2017-02-03T09:04:10Z

CLOUDSTACK-9770: fix missing ip routes in VR




---
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: Upgrade fails on Master

2017-02-03 Thread Rafael Weingärtner

The others already answered this one:
"Unsupported major.minor version 52.0"

I am assuming you are compiling with 1.8, and it seems you are using 1.7 or
lower version.


On Fri, Feb 3, 2017 at 11:48 AM, Nicolas Vazquez 
wrote:

> Hi Will,
>
> Did you try modifying /etc/cloudstack/management/classpath.conf file for
> Tomcat to run using java 8?
>
> 2017-02-03 13:43 GMT-03:00 Daan Hoogland :
>
> > that's what wat cought my eye as well, and this is important for users to
> > consider, So to must first upgrade java and then ACS.
> >
> > 
> > From: Milamber 
> > Sent: 03 February 2017 17:40:37
> > To: dev@cloudstack.apache.org
> > Subject: Re: Upgrade fails on Master
> >
> >
> > Probably an issue with your java version on your Centos machine? now CS
> > 4.10 need Java 8 to run.
> >
> >
> > On 03/02/2017 15:12, Will Stevens wrote:
> > > That was the 'management-server.log'...
> > >
> > > Here is the 'catalina.out' log.
> > >
> > > --- snip ---
> > > Feb 03, 2017 2:22:56 PM org.apache.catalina.loader.WebappClassLoader
> > > validateJarFile
> > > INFO:
> > > validateJarFile(/usr/share/cloudstack-management/webapps/
> > client/WEB-INF/lib/tomcat-embed-core-8.0.30.jar)
> > > - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class:
> > > javax/servlet/Servlet.class
> > > Feb 03, 2017 2:22:56 PM org.apache.tomcat.util.modeler.Registry
> > > registerComponent
> > > SEVERE: Null component
> > > Catalina:type=JspMonitor,name=jsp,WebModule=//localhost/
> > client,J2EEApplication=none,J2EEServer=none
> > > Feb 03, 2017 2:22:56 PM org.apache.catalina.startup.HostConfig
> > > deployDirectory
> > > SEVERE: Error deploying web application directory client
> > > java.lang.UnsupportedClassVersionError:
> > > org/apache/cloudstack/spring/module/web/CloudStackContextLoaderListene
> r
> > :
> > > Unsupported major.minor version 52.0 (unable to load class
> > > org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListene
> r)
> > > at
> > > org.apache.catalina.loader.WebappClassLoader.findClassInternal(
> > WebappClassLoader.java:2334)
> > > at
> > > org.apache.catalina.loader.WebappClassLoader.findClass(
> > WebappClassLoader.java:976)
> > > at
> > > org.apache.catalina.loader.WebappClassLoader.loadClass(
> > WebappClassLoader.java:1450)
> > > at
> > > org.apache.catalina.loader.WebappClassLoader.loadClass(
> > WebappClassLoader.java:1329)
> > > at
> > > org.apache.catalina.startup.WebAnnotationSet.loadClassAnnotation(
> > WebAnnotationSet.java:145)
> > > at
> > > org.apache.catalina.startup.WebAnnotationSet.
> > loadApplicationListenerAnnotations(WebAnnotationSet.java:73)
> > > at
> > > org.apache.catalina.startup.WebAnnotationSet.
> loadApplicationAnnotations(
> > WebAnnotationSet.java:56)
> > > at
> > > org.apache.catalina.startup.ContextConfig.
> applicationAnnotationsConfig(
> > ContextConfig.java:294)
> > > at org.apache.catalina.startup.ContextConfig.start(
> > ContextConfig.java:1046)
> > > at
> > > org.apache.catalina.startup.ContextConfig.lifecycleEvent(
> > ContextConfig.java:265)
> > > at
> > > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(
> > LifecycleSupport.java:142)
> > > at org.apache.catalina.core.StandardContext.start(
> > StandardContext.java:4650)
> > > at
> > > org.apache.catalina.core.ContainerBase.addChildInternal(
> > ContainerBase.java:791)
> > > at org.apache.catalina.core.ContainerBase.addChild(
> > ContainerBase.java:771)
> > > at org.apache.catalina.core.StandardHost.addChild(
> StandardHost.java:526)
> > > at
> > > org.apache.catalina.startup.HostConfig.deployDirectory(
> > HostConfig.java:1041)
> > > at
> > > org.apache.catalina.startup.HostConfig.deployDirectories(
> > HostConfig.java:964)
> > > at org.apache.catalina.startup.HostConfig.deployApps(
> > HostConfig.java:502)
> > > at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
> > > at
> > > org.apache.catalina.startup.HostConfig.lifecycleEvent(
> > HostConfig.java:321)
> > > at
> > > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(
> > LifecycleSupport.java:142)
> > > at org.apache.catalina.core.ContainerBase.start(
> ContainerBase.java:1053)
> > > at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
> > > at org.apache.catalina.core.ContainerBase.start(
> ContainerBase.java:1045)
> > > at org.apache.catalina.core.StandardEngine.start(
> > StandardEngine.java:443)
> > > at org.apache.catalina.core.StandardService.start(
> > StandardService.java:516)
> > > at org.apache.catalina.core.StandardServer.start(
> > StandardServer.java:710)
> > > at org.apache.catalina.startup.Catalina.start(Catalina.java:593)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > at
> > > sun.reflect.NativeMethodAccessorImpl.invoke(
> > NativeMethodAccessorImpl.java:57)
> > > at
> > > sun.reflect.DelegatingMethodAccessorImpl.invoke(
> >

Re: Upgrade fails on Master

2017-02-03 Thread Nicolas Vazquez

Hi Will,

Did you try modifying /etc/cloudstack/management/classpath.conf file for
Tomcat to run using java 8?

2017-02-03 13:43 GMT-03:00 Daan Hoogland :

> that's what wat cought my eye as well, and this is important for users to
> consider, So to must first upgrade java and then ACS.
>
> 
> From: Milamber 
> Sent: 03 February 2017 17:40:37
> To: dev@cloudstack.apache.org
> Subject: Re: Upgrade fails on Master
>
>
> Probably an issue with your java version on your Centos machine? now CS
> 4.10 need Java 8 to run.
>
>
> On 03/02/2017 15:12, Will Stevens wrote:
> > That was the 'management-server.log'...
> >
> > Here is the 'catalina.out' log.
> >
> > --- snip ---
> > Feb 03, 2017 2:22:56 PM org.apache.catalina.loader.WebappClassLoader
> > validateJarFile
> > INFO:
> > validateJarFile(/usr/share/cloudstack-management/webapps/
> client/WEB-INF/lib/tomcat-embed-core-8.0.30.jar)
> > - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class:
> > javax/servlet/Servlet.class
> > Feb 03, 2017 2:22:56 PM org.apache.tomcat.util.modeler.Registry
> > registerComponent
> > SEVERE: Null component
> > Catalina:type=JspMonitor,name=jsp,WebModule=//localhost/
> client,J2EEApplication=none,J2EEServer=none
> > Feb 03, 2017 2:22:56 PM org.apache.catalina.startup.HostConfig
> > deployDirectory
> > SEVERE: Error deploying web application directory client
> > java.lang.UnsupportedClassVersionError:
> > org/apache/cloudstack/spring/module/web/CloudStackContextLoaderListener
> :
> > Unsupported major.minor version 52.0 (unable to load class
> > org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener)
> > at
> > org.apache.catalina.loader.WebappClassLoader.findClassInternal(
> WebappClassLoader.java:2334)
> > at
> > org.apache.catalina.loader.WebappClassLoader.findClass(
> WebappClassLoader.java:976)
> > at
> > org.apache.catalina.loader.WebappClassLoader.loadClass(
> WebappClassLoader.java:1450)
> > at
> > org.apache.catalina.loader.WebappClassLoader.loadClass(
> WebappClassLoader.java:1329)
> > at
> > org.apache.catalina.startup.WebAnnotationSet.loadClassAnnotation(
> WebAnnotationSet.java:145)
> > at
> > org.apache.catalina.startup.WebAnnotationSet.
> loadApplicationListenerAnnotations(WebAnnotationSet.java:73)
> > at
> > org.apache.catalina.startup.WebAnnotationSet.loadApplicationAnnotations(
> WebAnnotationSet.java:56)
> > at
> > org.apache.catalina.startup.ContextConfig.applicationAnnotationsConfig(
> ContextConfig.java:294)
> > at org.apache.catalina.startup.ContextConfig.start(
> ContextConfig.java:1046)
> > at
> > org.apache.catalina.startup.ContextConfig.lifecycleEvent(
> ContextConfig.java:265)
> > at
> > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(
> LifecycleSupport.java:142)
> > at org.apache.catalina.core.StandardContext.start(
> StandardContext.java:4650)
> > at
> > org.apache.catalina.core.ContainerBase.addChildInternal(
> ContainerBase.java:791)
> > at org.apache.catalina.core.ContainerBase.addChild(
> ContainerBase.java:771)
> > at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
> > at
> > org.apache.catalina.startup.HostConfig.deployDirectory(
> HostConfig.java:1041)
> > at
> > org.apache.catalina.startup.HostConfig.deployDirectories(
> HostConfig.java:964)
> > at org.apache.catalina.startup.HostConfig.deployApps(
> HostConfig.java:502)
> > at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
> > at
> > org.apache.catalina.startup.HostConfig.lifecycleEvent(
> HostConfig.java:321)
> > at
> > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(
> LifecycleSupport.java:142)
> > at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
> > at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
> > at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
> > at org.apache.catalina.core.StandardEngine.start(
> StandardEngine.java:443)
> > at org.apache.catalina.core.StandardService.start(
> StandardService.java:516)
> > at org.apache.catalina.core.StandardServer.start(
> StandardServer.java:710)
> > at org.apache.catalina.startup.Catalina.start(Catalina.java:593)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:57)
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:606)
> > at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
> > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
> >
> > Feb 03, 2017 2:22:56 PM org.apache.coyote.http11.Http11NioProtocol start
> > INFO: Starting Coyote HTTP/1.1 on http-8080
> > Feb 03, 2017 2:22:56 PM org.apache.jk.common.ChannelSocket init
> > INFO: JK: ajp13 listening on /0.0.0.0:20400
> > Feb 03, 2017 2:22:56 PM

Re: Upgrade fails on Master

2017-02-03 Thread Daan Hoogland

that's what wat cought my eye as well, and this is important for users to 
consider, So to must first upgrade java and then ACS.


From: Milamber 
Sent: 03 February 2017 17:40:37
To: dev@cloudstack.apache.org
Subject: Re: Upgrade fails on Master


Probably an issue with your java version on your Centos machine? now CS
4.10 need Java 8 to run.


On 03/02/2017 15:12, Will Stevens wrote:
> That was the 'management-server.log'...
>
> Here is the 'catalina.out' log.
>
> --- snip ---
> Feb 03, 2017 2:22:56 PM org.apache.catalina.loader.WebappClassLoader
> validateJarFile
> INFO:
> validateJarFile(/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/tomcat-embed-core-8.0.30.jar)
> - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class:
> javax/servlet/Servlet.class
> Feb 03, 2017 2:22:56 PM org.apache.tomcat.util.modeler.Registry
> registerComponent
> SEVERE: Null component
> Catalina:type=JspMonitor,name=jsp,WebModule=//localhost/client,J2EEApplication=none,J2EEServer=none
> Feb 03, 2017 2:22:56 PM org.apache.catalina.startup.HostConfig
> deployDirectory
> SEVERE: Error deploying web application directory client
> java.lang.UnsupportedClassVersionError:
> org/apache/cloudstack/spring/module/web/CloudStackContextLoaderListener :
> Unsupported major.minor version 52.0 (unable to load class
> org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener)
> at
> org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:2334)
> at
> org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:976)
> at
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1450)
> at
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1329)
> at
> org.apache.catalina.startup.WebAnnotationSet.loadClassAnnotation(WebAnnotationSet.java:145)
> at
> org.apache.catalina.startup.WebAnnotationSet.loadApplicationListenerAnnotations(WebAnnotationSet.java:73)
> at
> org.apache.catalina.startup.WebAnnotationSet.loadApplicationAnnotations(WebAnnotationSet.java:56)
> at
> org.apache.catalina.startup.ContextConfig.applicationAnnotationsConfig(ContextConfig.java:294)
> at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1046)
> at
> org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:265)
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4650)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
> at
> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1041)
> at
> org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:964)
> at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
> at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
> at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321)
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
> at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
> at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
> at org.apache.catalina.core.StandardService.start(StandardService.java:516)
> at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:593)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
>
> Feb 03, 2017 2:22:56 PM org.apache.coyote.http11.Http11NioProtocol start
> INFO: Starting Coyote HTTP/1.1 on http-8080
> Feb 03, 2017 2:22:56 PM org.apache.jk.common.ChannelSocket init
> INFO: JK: ajp13 listening on /0.0.0.0:20400
> Feb 03, 2017 2:22:56 PM org.apache.jk.server.JkMain start
> INFO: Jk running ID=0 time=0/37  config=null
> Feb 03, 2017 2:22:56 PM org.apache.catalina.startup.Catalina start
> INFO: Server startup in 1203 ms
> --- snip ---
>
> The packages were built on a CentOS6 Jenkins slave and are being run on a
> CentOS 6.8 VM.
>
> Any ideas???
>
> *Will STEVENS*
> Lead Developer
>
> 
>
> On Fri, Feb 3, 2017 at 9:45 AM, Rafael Weingärtner <
> rafaelweingart...@gmail.com>

Re: Upgrade fails on Master

2017-02-03 Thread Milamber



Probably an issue with your java version on your Centos machine? now CS 
4.10 need Java 8 to run.



On 03/02/2017 15:12, Will Stevens wrote:

That was the 'management-server.log'...

Here is the 'catalina.out' log.

--- snip ---
Feb 03, 2017 2:22:56 PM org.apache.catalina.loader.WebappClassLoader
validateJarFile
INFO:
validateJarFile(/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/tomcat-embed-core-8.0.30.jar)
- jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class:
javax/servlet/Servlet.class
Feb 03, 2017 2:22:56 PM org.apache.tomcat.util.modeler.Registry
registerComponent
SEVERE: Null component
Catalina:type=JspMonitor,name=jsp,WebModule=//localhost/client,J2EEApplication=none,J2EEServer=none
Feb 03, 2017 2:22:56 PM org.apache.catalina.startup.HostConfig
deployDirectory
SEVERE: Error deploying web application directory client
java.lang.UnsupportedClassVersionError:
org/apache/cloudstack/spring/module/web/CloudStackContextLoaderListener :
Unsupported major.minor version 52.0 (unable to load class
org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener)
at
org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:2334)
at
org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:976)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1450)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1329)
at
org.apache.catalina.startup.WebAnnotationSet.loadClassAnnotation(WebAnnotationSet.java:145)
at
org.apache.catalina.startup.WebAnnotationSet.loadApplicationListenerAnnotations(WebAnnotationSet.java:73)
at
org.apache.catalina.startup.WebAnnotationSet.loadApplicationAnnotations(WebAnnotationSet.java:56)
at
org.apache.catalina.startup.ContextConfig.applicationAnnotationsConfig(ContextConfig.java:294)
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1046)
at
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:265)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4650)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
at
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1041)
at
org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:964)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:593)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

Feb 03, 2017 2:22:56 PM org.apache.coyote.http11.Http11NioProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Feb 03, 2017 2:22:56 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:20400
Feb 03, 2017 2:22:56 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/37  config=null
Feb 03, 2017 2:22:56 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 1203 ms
--- snip ---

The packages were built on a CentOS6 Jenkins slave and are being run on a
CentOS 6.8 VM.

Any ideas???

*Will STEVENS*
Lead Developer



On Fri, Feb 3, 2017 at 9:45 AM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:


Is the log you posted a piece of catalina.out or the management-server.log?

Normally when the container (in this case Tomcat) does not go up, I try to
check the container log files, which may contain log entries that are not
logged in the application log file. For tomcat, I normally check the
catalina.out.

On Fri, Feb 3, 2017 at 9:40 AM, Will Stevens 
wrote:


Hey All,
I have been doing the same upgrade path for months.  It basically goes

[GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

2017-02-03 Thread swill

Github user swill commented on the issue:

https://github.com/apache/cloudstack/pull/1888
  
@rhtyd I built the Java 8 version on a CentOS6 slave and I am trying to 
install it on a CentOS 6.8 host and I am getting a similar issue.

The details are here:  
https://lists.apache.org/thread.html/d771df6a4ff07638362ab1343af69d6ab5d35a6cb4a9925b3077aa55@%3Cdev.cloudstack.apache.org%3E

This seems to be related to this PR.  I have not been able to get a Java 8 
version of ACS to work yet.


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

RE: Bug #8544

2017-02-03 Thread Marty Godsey

Sure. Let me get some information and post it. I am not a developer, I am the 
other side of the fence (network, systems, etc) so me debugging code would not 
be pretty. :) But I will post what I have proficiency in. Thank you Daan.

Regards,
Marty Godsey
Principal Engineer
nSource Solutions, LLC

-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] 
Sent: Thursday, February 2, 2017 3:50 PM
To: dev 
Subject: Re: Bug #8544

Marty, probably no active developers are hitting the issue, hence no one is 
working on it. Can you add information so someone that doesn't feel hindered by 
this can do diagnosis, or if at all possible can you point at what code is 
broken?

On Tue, Jan 31, 2017 at 11:07 PM, Marty Godsey  wrote:
> I ran into this bug today and I don't see any movement on it.
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-8544
>
> It was opened back in June of 2015 and is listed as still open for 4.9.2.0.
>
> Regards,
> Marty Godsey
> Principal Engineer
> nSource Solutions, LLC
>

--
Daan

Re: Upgrade fails on Master

2017-02-03 Thread Will Stevens

That was the 'management-server.log'...

Here is the 'catalina.out' log.

--- snip ---
Feb 03, 2017 2:22:56 PM org.apache.catalina.loader.WebappClassLoader
validateJarFile
INFO:
validateJarFile(/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/tomcat-embed-core-8.0.30.jar)
- jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class:
javax/servlet/Servlet.class
Feb 03, 2017 2:22:56 PM org.apache.tomcat.util.modeler.Registry
registerComponent
SEVERE: Null component
Catalina:type=JspMonitor,name=jsp,WebModule=//localhost/client,J2EEApplication=none,J2EEServer=none
Feb 03, 2017 2:22:56 PM org.apache.catalina.startup.HostConfig
deployDirectory
SEVERE: Error deploying web application directory client
java.lang.UnsupportedClassVersionError:
org/apache/cloudstack/spring/module/web/CloudStackContextLoaderListener :
Unsupported major.minor version 52.0 (unable to load class
org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener)
at
org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:2334)
at
org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:976)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1450)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1329)
at
org.apache.catalina.startup.WebAnnotationSet.loadClassAnnotation(WebAnnotationSet.java:145)
at
org.apache.catalina.startup.WebAnnotationSet.loadApplicationListenerAnnotations(WebAnnotationSet.java:73)
at
org.apache.catalina.startup.WebAnnotationSet.loadApplicationAnnotations(WebAnnotationSet.java:56)
at
org.apache.catalina.startup.ContextConfig.applicationAnnotationsConfig(ContextConfig.java:294)
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1046)
at
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:265)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4650)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
at
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1041)
at
org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:964)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:593)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

Feb 03, 2017 2:22:56 PM org.apache.coyote.http11.Http11NioProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Feb 03, 2017 2:22:56 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:20400
Feb 03, 2017 2:22:56 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/37  config=null
Feb 03, 2017 2:22:56 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 1203 ms
--- snip ---

The packages were built on a CentOS6 Jenkins slave and are being run on a
CentOS 6.8 VM.

Any ideas???

*Will STEVENS*
Lead Developer



On Fri, Feb 3, 2017 at 9:45 AM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> Is the log you posted a piece of catalina.out or the management-server.log?
>
> Normally when the container (in this case Tomcat) does not go up, I try to
> check the container log files, which may contain log entries that are not
> logged in the application log file. For tomcat, I normally check the
> catalina.out.
>
> On Fri, Feb 3, 2017 at 9:40 AM, Will Stevens 
> wrote:
>
> > Hey All,
> > I have been doing the same upgrade path for months.  It basically goes
> like
> > this.  I am running CentOS6.8.
> >
> > - Build code with jenkins and publish to a repo
> > - Backup

Re: Upgrade fails on Master

2017-02-03 Thread Rafael Weingärtner

Is the log you posted a piece of catalina.out or the management-server.log?

Normally when the container (in this case Tomcat) does not go up, I try to
check the container log files, which may contain log entries that are not
logged in the application log file. For tomcat, I normally check the
catalina.out.

On Fri, Feb 3, 2017 at 9:40 AM, Will Stevens 
wrote:

> Hey All,
> I have been doing the same upgrade path for months.  It basically goes like
> this.  I am running CentOS6.8.
>
> - Build code with jenkins and publish to a repo
> - Backup /etc/cloudstack/management/db.properties -> db.properties.bck
> - Update my /etc/yum.repos.d/cloudstack.repo file to point to the new
> build
> - Since it is the same version as the last time (4.10), I have to remove
> the old packages
> -- sudo yum -y remove cloudstack-management cloudstack-common
> cloudstack-usage
> - Install the new packages
> -- sudo yum -y install cloudstack-management cloudstack-usage
> - Copy the db.properties.bck to db.properties
> - Restart the service
>
> I recently pulled in the latest code from master and now I get different
> behavior.
>
> When I install the packages, I get this:
> --- snip ---
> Running Transaction
>   Installing : cloudstack-common-4.10.0.0-SNAPSHOT.el6.x86_64  1/3
>   Installing : cloudstack-management-4.10.0.0-SNAPSHOT.el6.x86_64  2/3
> Unable to determine ssl settings for server.xml, please run
> cloudstack-setup-management manually
> Unable to determine ssl settings for tomcat.conf, please run
> cloudstack-setup-management manually
>   Installing : cloudstack-usage-4.10.0.0-SNAPSHOT.el6.x86_64   3/3
> Replacing db.properties with management server db.properties
> Replacing key with management server key
>   Verifying  : cloudstack-common-4.10.0.0-SNAPSHOT.el6.x86_64  1/3
>   Verifying  : cloudstack-usage-4.10.0.0-SNAPSHOT.el6.x86_64   2/3
>   Verifying  : cloudstack-management-4.10.0.0-SNAPSHOT.el6.x86_64  3/3
>
> Installed:
>   cloudstack-management.x86_64 0:4.10.0.0-SNAPSHOT.el6
> cloudstack-usage.x86_64 0:4.10.0.0-SNAPSHOT.el6
>
>
> Dependency Installed:
>   cloudstack-common.x86_64 0:4.10.0.0-SNAPSHOT.el6
>
> Complete!
> --- snip --
>
> I check what files are in the '/etc/cloudstack/management' folder.
>
> --- snip relevant ---
> server-nonssl.xml
> server-ssl.xml
> server.xml -> /etc/cloudstack/management/server-nonssl.xml
> tomcat6.conf -> /etc/cloudstack/management/tomcat6-nonssl.conf
> tomcat6-nonssl.conf
> tomcat6-ssl.conf
> tomcat-users.xml
> --- snip relevant ---
>
> I notice that 'server.xml' is there, but 'tomcat.conf' is not.
>
> I run 'cloudstack-setup-management' as it says in the instructions.
>
> ---
> $ sudo cloudstack-setup-management
> Starting to configure CloudStack Management Server:
> Configure Firewall ...[OK]
> Configure CloudStack Management Server ...[OK]
> CloudStack Management Server setup is Done!
> ---
>
> It does not seem to have changed anything in '/etc/cloudstack/management'
> folder.
>
> I try to start the CloudStack Management service and then tail the log and
> I get this in the logs and the service does not start.
>
> --- snip ---
> 2017-01-18 20:01:19,134 INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle]
> (Thread-90:null) (logid:) stopping bean ClusterServiceServletAdapter
> 2017-01-18 20:01:19,135 ERROR [c.c.c.ClusterServiceServletContainer]
> (Thread-10:null) (logid:) Unexpected exception
> java.net.SocketException: Socket closed
> at java.net.PlainSocketImpl.socketAccept(Native Method)
> at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:
> 398)
> at java.net.ServerSocket.implAccept(ServerSocket.java:530)
> at java.net.ServerSocket.accept(ServerSocket.java:498)
> at
> com.cloud.cluster.ClusterServiceServletContainer$ListenerThread.run(
> ClusterServiceServletContainer.java:131)
> 2017-01-18 20:01:19,135 INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle]
> (Thread-90:null) (logid:) stopping bean ClusterManagerImpl
> 2017-01-18 20:01:19,135 INFO  [c.c.c.ClusterManagerImpl] (Thread-90:null)
> (logid:) Stopping Cluster manager, msid : 7617392934992
> --- snip ---
>
> I am not sure what changed on master that would have caused this, but
> apparently something is unhappy.
>
> Any ideas for how to resolve this and make sure upgrades still work for
> ACS?
>
> Thanks,
>
> Will
>



-- 
Rafael Weingärtner

Upgrade fails on Master

2017-02-03 Thread Will Stevens

Hey All,
I have been doing the same upgrade path for months.  It basically goes like
this.  I am running CentOS6.8.

- Build code with jenkins and publish to a repo
- Backup /etc/cloudstack/management/db.properties -> db.properties.bck
- Update my /etc/yum.repos.d/cloudstack.repo file to point to the new build
- Since it is the same version as the last time (4.10), I have to remove
the old packages
-- sudo yum -y remove cloudstack-management cloudstack-common
cloudstack-usage
- Install the new packages
-- sudo yum -y install cloudstack-management cloudstack-usage
- Copy the db.properties.bck to db.properties
- Restart the service

I recently pulled in the latest code from master and now I get different
behavior.

When I install the packages, I get this:
--- snip ---
Running Transaction
  Installing : cloudstack-common-4.10.0.0-SNAPSHOT.el6.x86_64  1/3
  Installing : cloudstack-management-4.10.0.0-SNAPSHOT.el6.x86_64  2/3
Unable to determine ssl settings for server.xml, please run
cloudstack-setup-management manually
Unable to determine ssl settings for tomcat.conf, please run
cloudstack-setup-management manually
  Installing : cloudstack-usage-4.10.0.0-SNAPSHOT.el6.x86_64   3/3
Replacing db.properties with management server db.properties
Replacing key with management server key
  Verifying  : cloudstack-common-4.10.0.0-SNAPSHOT.el6.x86_64  1/3
  Verifying  : cloudstack-usage-4.10.0.0-SNAPSHOT.el6.x86_64   2/3
  Verifying  : cloudstack-management-4.10.0.0-SNAPSHOT.el6.x86_64  3/3

Installed:
  cloudstack-management.x86_64 0:4.10.0.0-SNAPSHOT.el6
cloudstack-usage.x86_64 0:4.10.0.0-SNAPSHOT.el6


Dependency Installed:
  cloudstack-common.x86_64 0:4.10.0.0-SNAPSHOT.el6

Complete!
--- snip --

I check what files are in the '/etc/cloudstack/management' folder.

--- snip relevant ---
server-nonssl.xml
server-ssl.xml
server.xml -> /etc/cloudstack/management/server-nonssl.xml
tomcat6.conf -> /etc/cloudstack/management/tomcat6-nonssl.conf
tomcat6-nonssl.conf
tomcat6-ssl.conf
tomcat-users.xml
--- snip relevant ---

I notice that 'server.xml' is there, but 'tomcat.conf' is not.

I run 'cloudstack-setup-management' as it says in the instructions.

---
$ sudo cloudstack-setup-management
Starting to configure CloudStack Management Server:
Configure Firewall ...[OK]
Configure CloudStack Management Server ...[OK]
CloudStack Management Server setup is Done!
---

It does not seem to have changed anything in '/etc/cloudstack/management'
folder.

I try to start the CloudStack Management service and then tail the log and
I get this in the logs and the service does not start.

--- snip ---
2017-01-18 20:01:19,134 INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle]
(Thread-90:null) (logid:) stopping bean ClusterServiceServletAdapter
2017-01-18 20:01:19,135 ERROR [c.c.c.ClusterServiceServletContainer]
(Thread-10:null) (logid:) Unexpected exception
java.net.SocketException: Socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398)
at java.net.ServerSocket.implAccept(ServerSocket.java:530)
at java.net.ServerSocket.accept(ServerSocket.java:498)
at
com.cloud.cluster.ClusterServiceServletContainer$ListenerThread.run(ClusterServiceServletContainer.java:131)
2017-01-18 20:01:19,135 INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle]
(Thread-90:null) (logid:) stopping bean ClusterManagerImpl
2017-01-18 20:01:19,135 INFO  [c.c.c.ClusterManagerImpl] (Thread-90:null)
(logid:) Stopping Cluster manager, msid : 7617392934992
--- snip ---

I am not sure what changed on master that would have caused this, but
apparently something is unhappy.

Any ideas for how to resolve this and make sure upgrades still work for ACS?

Thanks,

Will

RE: [PROPOSAL] add native container orchestration service

2017-02-03 Thread Kishan Kavala

Murali,
 APIs are similar, but the name is generic - createServiceCluster instead of 
createContainerCluster
Same with DB tables names - service_cluster instead of container_cluster
API params or the DB columns in the spec you published don't have anything 
specific to container_clusters and can be used for any service.

-Original Message-
From: Murali Reddy [mailto:muralimmre...@gmail.com] 
Sent: 02 February 2017 02:34 PM
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service


Thanks for the feedback. There have been some concerns here with this proposal. 
I think we had sufficient valid arguments why we need this functionality in 
CloudStack. While this proposal is to use k8s as container orchestrator design 
should be able to adopt other container orchestrator.


Unless anybody has any specific technical points on this, I'd like to go on 
with its implementation and open up a PR.


Kishan, when do you think you can share further details (northbound API 
semantics etc) on the work you are doing? I am planning to get this feature the 
for 4.11. 



On 31/01/17, 5:54 PM, "Will Stevens"  wrote:

>I think that is covered in this proposal. There is nothing k8s specific 
>in this integration (from what I understand), all the k8s details are 
>passed in via the cloud-init configuration after the cluster has been 
>provisioned.
>
>On Jan 31, 2017 3:06 AM, "Lianghwa Jou"  wrote:
>
>
>There are many container orchestrators. Those container orchestrators 
>are happy to run on any VMs or bare metal machines. K8s is just one of 
>them and there will be more in the future. It may not be a good idea to 
>make CloudStack to be k8s aware. IMO, the relationship between k8s and 
>cloudstack should be similar to application and os. It probably not a 
>good idea to make your OS to be aware of any specific applications so 
>IMHO I don’t think k8s should be native to CloudStack. It makes more 
>sense to provide some generic services that many applications can take 
>advantages of. Some generic resource grouping service makes sense so a 
>group of VMs, baremetal machines or network can be treated as a single 
>entity. Some life cycle management will be necessary for these entities 
>too. We can deploy k8s, swarm, dcos or even non-container specific 
>services on top of CloudStack. The k8s is changing fast. One single 
>tenant installation may need more than one VM group and may actually 
>requires more (k8s federation). It will be a struggle to be in sync if 
>we try to bring k8s specific knowledge into cloudstack.
>
>Regards,
>
>
>--
>Lianghwa Jou
>VP Engineering, Accelerite
>email: lianghwa@accelerite.com
>
>
>
>
>
>On 1/29/17, 11:54 PM, "Murali Reddy"  wrote:
>
>
>I agree with some good views Will has shared and I also agree to 
>the concerns raised by Wido and Eric. IMO we need balance of staying 
>relevant/add new features vs stability of CloudStack and take 
>corrective action if needed. We have two good examples for both. When 
>SDN was hot technology CloudStack ended up with bunch of SDN controller 
>integrations.
>Few years later, now CloudStack is carrying baggage with no maintainers 
>for those plugins, with probably not many of CloudStack users needing overlays.
>On the other hand, other than attempt to liaison with ETSI for NFV no 
>effort was done. OpenStack has become de-facto for NFV. Now for 
>OpenStack, arguably NFV has become larger use case than cloud it self. 
>I concur with Will’s point that with minimal viable solution that does 
>not change the core of CloudStack, and can keep CloudStack relevant is 
>worth to be taken in.
>
>Will,
>
>To your question of how different is from ShapeBlue’s container 
>service, its design, implementation and API semantics etc remain same.
>ShapeBlue’s container service was true drop in plug-in to CloudStack, 
>with this proposal I am trying to re-work to make it a core CloudStack 
>pluggable service which is part of CloudStack.
>
>Key concepts that this proposal is trying to add
>
>- add notion of ‘container cluster’ as a first class entity in 
>CloudStack. Which is bacially collection of other CloudStack resources 
>(like VM’s, networks, public ip, network rules etc)
>- life cycle operation to manage ‘container cluster’ like 
>create, delete, start, stop, scale-up, scale-down, heal etc
>- orchestrate container orchestrator control plane on top of 
>provisioned resources
>
>At-least for k8s (which is what this proposal is targeting), 
>integration with k8s is bare minimum. There are cloud-config scripts 
>that automatically setup k8s cluster master and node VM’s. All 
>CloudStack is doing in passing the cloud-config to the core OS VM’s as user 
>data.
>
>Regards
>Murali Reddy
>
>
>
>
>
>
>
>On 29/01/17, 8:54 AM, "Will Stevens" behalf of

[GitHub] cloudstack issue #1905: CLOUDSTACK-9738: Optimize vm expunge process for ins...

2017-02-03 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1905
  
Trillian test result (tid-800)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 32817 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1905-t800-kvm-centos7.zip
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Test completed. 47 look ok, 2 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_02_redundant_VPC_default_routes | `Failure` | 864.15 | 
test_vpc_redundant.py
test_04_rvpc_privategw_static_routes | `Failure` | 366.16 | 
test_privategw_acl.py
test_01_vpc_site2site_vpn | Success | 160.30 | test_vpc_vpn.py
test_01_vpc_remote_access_vpn | Success | 66.11 | test_vpc_vpn.py
test_01_redundant_vpc_site2site_vpn | Success | 240.86 | test_vpc_vpn.py
test_02_VPC_default_routes | Success | 262.05 | test_vpc_router_nics.py
test_01_VPC_nics_after_destroy | Success | 504.83 | test_vpc_router_nics.py
test_05_rvpc_multi_tiers | Success | 506.66 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | Success | 1416.61 | 
test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 553.45 | test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1281.45 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 151.54 | test_volumes.py
test_08_resize_volume | Success | 156.48 | test_volumes.py
test_07_resize_fail | Success | 161.54 | test_volumes.py
test_06_download_detached_volume | Success | 156.85 | test_volumes.py
test_05_detach_volume | Success | 155.81 | test_volumes.py
test_04_delete_attached_volume | Success | 151.26 | test_volumes.py
test_03_download_attached_volume | Success | 156.31 | test_volumes.py
test_02_attach_volume | Success | 90.52 | test_volumes.py
test_01_create_volume | Success | 711.41 | test_volumes.py
test_03_delete_vm_snapshots | Success | 275.23 | test_vm_snapshots.py
test_02_revert_vm_snapshots | Success | 95.78 | test_vm_snapshots.py
test_01_create_vm_snapshots | Success | 158.73 | test_vm_snapshots.py
test_deploy_vm_multiple | Success | 277.87 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.03 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.71 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 125.26 | test_vm_life_cycle.py
test_08_migrate_vm | Success | 40.91 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.13 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 125.87 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 126.01 | test_vm_life_cycle.py
test_02_start_vm | Success | 10.19 | test_vm_life_cycle.py
test_01_stop_vm | Success | 45.35 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 45.51 | test_templates.py
test_08_list_system_templates | Success | 0.03 | test_templates.py
test_07_list_public_templates | Success | 0.04 | test_templates.py
test_05_template_permissions | Success | 0.08 | test_templates.py
test_04_extract_template | Success | 5.25 | test_templates.py
test_03_delete_template | Success | 5.11 | test_templates.py
test_02_edit_template | Success | 90.19 | test_templates.py
test_01_create_template | Success | 45.45 | test_templates.py
test_10_destroy_cpvm | Success | 131.70 | test_ssvm.py
test_09_destroy_ssvm | Success | 163.66 | test_ssvm.py
test_08_reboot_cpvm | Success | 101.78 | test_ssvm.py
test_07_reboot_ssvm | Success | 133.61 | test_ssvm.py
test_06_stop_cpvm | Success | 131.78 | test_ssvm.py
test_05_stop_ssvm | Success | 139.48 | test_ssvm.py
test_04_cpvm_internals | Success | 1.17 | test_ssvm.py
test_03_ssvm_internals | Success | 4.06 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.12 | test_ssvm.py
test_01_list_sec_storage_vm | Success | 0.14 | test_ssvm.py
test_01_snapshot_root_disk | Success | 11.23 | test_snapshots.py
test_04_change_offering_small | Success | 239.59 | test_service_offerings.py
test_03_delete_service_offering | Success | 0.04 | test_service_offerings.py
test_02_edit_service_offering | Success | 0.05 | test_service_offerings.py
test_01_create_service_offering | Success | 0.11 | test_service_offerings.py
test_02_sys_template_ready | Success | 0.13 | test_secondary_storage.py
test_01_sys_vm_start | Success | 0.18 | test_secondary_storage.py
test_09_reboot_router | Success | 35.33 | test_routers.py
test_08_start_router | Success | 30.35 | test_routers.py
test_07_stop_router | Success | 10.18 | test_routers.py

[GitHub] cloudstack issue #1928: Update hypervisor capabilities for xenserver 7

2017-02-03 Thread pdion891

Github user pdion891 commented on the issue:

https://github.com/apache/cloudstack/pull/1928
  
Please merge it into master as well, it also mean we need to make sure 
master does have the same file `setup/db/db/schema-4920to4930.sql` too.

We will do some testing around xenserver7 soon also  :-)


---
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-www issue #34: Remove link to “planet.apache.org” and update ...

2017-02-03 Thread swill

Github user swill commented on the issue:

https://github.com/apache/cloudstack-www/pull/34
  
OK. What would it be solving for?  Just trying to understand because we 
have to build the site locally anyway to check the changes and then we have to 
push the changes (which currently publishes the site).  Maybe I am missing 
something. 


---
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 #1924: CLOUDSTACK-9766 : Executing deleteSnapshot api with ...

2017-02-03 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1924
  
Trillian test result (tid-798)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 37116 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1924-t798-kvm-centos7.zip
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: 
/marvin/tests/smoke/test_routers_network_ops.py
Intermitten failure detected: /marvin/tests/smoke/test_volumes.py
Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Test completed. 48 look ok, 1 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_04_rvpc_privategw_static_routes | `Failure` | 361.03 | 
test_privategw_acl.py
test_01_vpc_site2site_vpn | Success | 165.15 | test_vpc_vpn.py
test_01_vpc_remote_access_vpn | Success | 66.08 | test_vpc_vpn.py
test_01_redundant_vpc_site2site_vpn | Success | 261.26 | test_vpc_vpn.py
test_02_VPC_default_routes | Success | 299.05 | test_vpc_router_nics.py
test_01_VPC_nics_after_destroy | Success | 532.79 | test_vpc_router_nics.py
test_05_rvpc_multi_tiers | Success | 524.85 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | Success | 1419.13 | 
test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 572.62 | test_vpc_redundant.py
test_02_redundant_VPC_default_routes | Success | 755.61 | 
test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1300.05 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 156.43 | test_volumes.py
test_08_resize_volume | Success | 156.30 | test_volumes.py
test_07_resize_fail | Success | 161.35 | test_volumes.py
test_06_download_detached_volume | Success | 156.21 | test_volumes.py
test_05_detach_volume | Success | 155.68 | test_volumes.py
test_04_delete_attached_volume | Success | 146.11 | test_volumes.py
test_03_download_attached_volume | Success | 156.18 | test_volumes.py
test_02_attach_volume | Success | 95.64 | test_volumes.py
test_01_create_volume | Success | 712.33 | test_volumes.py
test_03_delete_vm_snapshots | Success | 275.18 | test_vm_snapshots.py
test_02_revert_vm_snapshots | Success | 95.69 | test_vm_snapshots.py
test_01_create_vm_snapshots | Success | 158.71 | test_vm_snapshots.py
test_deploy_vm_multiple | Success | 247.51 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.03 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.69 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 125.23 | test_vm_life_cycle.py
test_08_migrate_vm | Success | 40.92 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.13 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 130.79 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 125.80 | test_vm_life_cycle.py
test_02_start_vm | Success | 10.16 | test_vm_life_cycle.py
test_01_stop_vm | Success | 40.30 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 55.52 | test_templates.py
test_08_list_system_templates | Success | 0.03 | test_templates.py
test_07_list_public_templates | Success | 0.04 | test_templates.py
test_05_template_permissions | Success | 0.06 | test_templates.py
test_04_extract_template | Success | 5.17 | test_templates.py
test_03_delete_template | Success | 5.10 | test_templates.py
test_02_edit_template | Success | 90.18 | test_templates.py
test_01_create_template | Success | 25.30 | test_templates.py
test_10_destroy_cpvm | Success | 161.68 | test_ssvm.py
test_09_destroy_ssvm | Success | 163.64 | test_ssvm.py
test_08_reboot_cpvm | Success | 101.47 | test_ssvm.py
test_07_reboot_ssvm | Success | 133.64 | test_ssvm.py
test_06_stop_cpvm | Success | 131.61 | test_ssvm.py
test_05_stop_ssvm | Success | 138.77 | test_ssvm.py
test_04_cpvm_internals | Success | 1.13 | test_ssvm.py
test_03_ssvm_internals | Success | 3.48 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.11 | test_ssvm.py
test_01_list_sec_storage_vm | Success | 0.12 | test_ssvm.py
test_01_snapshot_root_disk | Success | 11.20 | test_snapshots.py
test_04_change_offering_small | Success | 239.53 | test_service_offerings.py
test_03_delete_service_offering | Success | 0.03 | test_service_offerings.py
test_02_edit_service_offering | Success | 0.07 | test_service_offerings.py
test_01_create_service_offering | Success | 0.10 | test_service_offerings.py
test_02_sys_template_ready | Success | 0.13 | test_secondary_storage.py
test_01_sys_vm_start | Success | 0.16 | test_secondary_storage.py
test_09_reboot_router | Success | 35.31 |

[GitHub] cloudstack pull request #:

[GitHub] cloudstack issue #1929: CLOUDSTACK-9770: fix missing ip routes in VR

[GitHub] cloudstack issue #1929: CLOUDSTACK-9770: fix missing ip routes in VR

[GitHub] cloudstack issue #1929: CLOUDSTACK-9770: fix missing ip routes in VR

[GitHub] cloudstack issue #1644: Honors the snapshot.backup.rightafter configuration ...

[GitHub] cloudstack issue #1929: CLOUDSTACK-9770: fix missing ip routes in VR

[GitHub] cloudstack-www issue #34: Remove link to “planet.apache.org” and update ...

[GitHub] cloudstack-www issue #34: Remove link to “planet.apache.org” and update ...

[GitHub] cloudstack-www issue #34: Remove link to “planet.apache.org” and update ...

[GitHub] cloudstack-www issue #34: Remove link to “planet.apache.org” and update ...

[GitHub] cloudstack-www issue #34: Remove link to “planet.apache.org” and update ...

[GitHub] cloudstack-www issue #34: Remove link to “planet.apache.org” and update ...

[GitHub] cloudstack issue #1913: CLOUDSTACK-9752: [Vmware] Optimization of volume att...

[GitHub] cloudstack-www issue #34: Remove link to “planet.apache.org” and update ...

[GitHub] cloudstack-www issue #34: Remove link to “planet.apache.org” and update ...

[GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

[GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

Re: Upgrade fails on Master

[GitHub] cloudstack pull request #1929: CLOUDSTACK-9770: fix missing ip routes in VR

Re: Upgrade fails on Master

Re: Upgrade fails on Master

Re: Upgrade fails on Master

Re: Upgrade fails on Master

[GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

RE: Bug #8544

Re: Upgrade fails on Master

Re: Upgrade fails on Master

Upgrade fails on Master

RE: [PROPOSAL] add native container orchestration service

[GitHub] cloudstack issue #1905: CLOUDSTACK-9738: Optimize vm expunge process for ins...

[GitHub] cloudstack issue #1928: Update hypervisor capabilities for xenserver 7

[GitHub] cloudstack-www issue #34: Remove link to “planet.apache.org” and update ...

[GitHub] cloudstack issue #1924: CLOUDSTACK-9766 : Executing deleteSnapshot api with ...

33 matches

Site Navigation

Mail list logo

Footer information