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
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 th
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
ht
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 we
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
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 you
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 han
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
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
propos
Github user swill commented on the issue:
https://github.com/apache/cloudstack-www/pull/34
We may want to actually call out the user flow and commands to make the
process easier for people. This would be in addition to what you have already
written. Correct this if I am wrong about
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
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
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 pr
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/blueoranguta
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 bran
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
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 ha
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" ] ||
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
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 6749785caba78a9379e94bf3aaf
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/classp
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.
>
> ___
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 w
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.WebappClassLoade
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/t
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
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 loade
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
cata
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 t
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
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/blueoranguta
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
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
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/blueoranguta
34 matches
Mail list logo
