I upgraded a very clean environment of 4.8.0.1 to 4.9 and I am receiving this
error when trying to enable the dynamic.apichecker.enabled setting:
2016-08-17 00:20:03,148 DEBUG [c.c.a.ApiServlet]
(catalina-exec-25:ctx-01fb5369) (logid:3a6b506e) ===START=== 192.168.250.250
-- GET
Github user jburwell commented on the issue:
https://github.com/apache/cloudstack/pull/1593
@serg38 we require Marvin test results and, as well as, the results of any
manual tests to be posted into the PR. This information is a pre-requisite for
merging PRs. Please see other closed
Github user jburwell commented on the issue:
https://github.com/apache/cloudstack/pull/1638
@rhtyd there is a difference between supporting Java8 and using it as the
default version. By changing the POMs, Maven will require that Java8 in order
to use CloudStack dependencies.
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1593
@jburwell LGTM for the test part. This PR was extensively tested on
Environment: RHEL 6 management servers, Vmware ESX5.5 and 6.0 with advanced
networking
---
If your project is set up for
Github user mike-tutkowski commented on the issue:
https://github.com/apache/cloudstack/pull/1642
Here is a screen capture on the changes to the System Service Offering
dialog.
[](url)
GitHub user mike-tutkowski opened a pull request:
https://github.com/apache/cloudstack/pull/1642
System VMs on Managed Storage
This PR makes it easier to spin up system VMs on managed storage.
Managed storage is when you have a dedicated volume on a SAN for a
particular
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1638
@jburwell Running tests against JRE 1.7, 1.8 is do-able. But I really want
our master to use JDK 1.8. If we want to be able to run ACS mgmt server, agents
etc against JRE 1.8 on both 4.9/lts and
Github user jburwell commented on the issue:
https://github.com/apache/cloudstack/pull/1638
@rhtyd @pdion891 I apologize for my delayed reply as I am on vacation ATM.
We had previously agreed not to require Java8 until 5.0.0 which is scheduled
for the end of 2016. 4.x should be
All,
I found that Github also allows to merge a PR with the changes squashed [1],
our git-pr script uses a normal branch-merge pattern. Should we evaluate using
the approach of squash-merging a PR [1] to reduce git-history clutter?
Github also (finally) allows to edit a PR and change base
C
an you please let us know dates for rescheduled event as soon as possible?
Thanks
2016-08-16 12:32 GMT-03:00 Marco Sinhoreli :
> All,
>
>
>
> I am very sorry to have to say that we have had to postpone the upcoming
> CCC conference in Sao Paluo.
>
>
>
> Over
Github user pdion891 commented on the issue:
https://github.com/apache/cloudstack/pull/1638
Make sense, thanks, I hope it will get thru then to add support for Ubuntu
16.04 for the management server host and KVM.
---
If your project is set up for it, you can reply to this email
Github user jburwell commented on the issue:
https://github.com/apache/cloudstack/pull/1593
@serg38 I only see code review LGTMs. We need at least one test LGTM
before this PR. In this case, those tests must be run against real hardware and
hypervisors. Also, we need an LGTM from
All,
We now have a PR where we're able to build, run and test CloudStack master with
JDK 1.8 and Spring 4.3. Special thanks to Marc-Aurèle Brothier for fixing the
unit test issues.
The only outstanding issue is getting the F5 plugin to build, which I could not
figure out how to fix even
@rhtyd The rationale to have vmware.nested.virtualization.perVM was that
advanced vm_details and template details are user controlled. With
https://issues.apache.org/jira/browse/CLOUDSTACK-9457
‘Allow retrieval and modification of VM and template details via API and UI’
users will be able to
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1638
@pdion891 we're neither breaking any backward compatibility wrt APIs, or
schema, nor we've made any core change (mgmt server core, cmd-answer patterns,
rpcs/serialization, or the plugin-system).
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1542
@nvazquez @serg38 how about we remove vmware.nested.virtualization.perVM
and instead if the user vm detail exists and is true, it overrides the global
setting?
---
If your project is set up for
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1542
@jburwell @rhtyd @koushik-das Can you review 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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1560
@rafaelweingartner @jburwell @rhtyd @koushik-das Can you review 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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1593
@karuturi @jburwell There are 2 LGTM in this PR. Packaging, Travis and
Jenkins all passed. Can this be merged?
---
If your project is set up for it, you can reply to this email and have your
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1602
@jburwell Are there any outstanding issues with this PR? It is waiting for
second LGTM.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1605
@rafaelweingartner @swill Will you be able to review this one?
---
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
Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1615
@jburwell Are there any outstanding issues with this PR? It is waiting for
second LGTM.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user nvazquez commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1593#discussion_r74966728
--- Diff: usage/src/com/cloud/usage/UsageSanityChecker.java ---
@@ -72,7 +72,9 @@ protected boolean checkItemCountByPstmt(CheckCase
checkCase) throws
All,
I am very sorry to have to say that we have had to postpone the upcoming CCC
conference in Sao Paluo.
Over the past few months we have been working very hard with an events
organiser to try and get the conference off the ground. Conferences are very
expensive to stage here in Brasil so
Github user rafaelweingartner commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1593#discussion_r74957023
--- Diff: usage/src/com/cloud/usage/UsageSanityChecker.java ---
@@ -72,7 +72,9 @@ protected boolean checkItemCountByPstmt(CheckCase
checkCase)
To me, if we would like to offer LTS, we need to fix following core issues:
- how database version is handle, right now database structure is mixed
with upgrade*.sql files and some java code
- better test upgrade path, I'm not sure we test them properly :-S
I have to admit I'm not fan of LTS
Hi!
We've recently noticed cloudstack-usage is no longer able to write
usage data into mysql. I assume this happened after updateing to
4.8.0.1 or 4.9 - we missed that error in our testsetup...
Here's the usage.log: http://pastebin.com/Zpvnw4xX
Finally it fails with following message:
ERROR
Github user pdion891 commented on the issue:
https://github.com/apache/cloudstack/pull/1638
Shouldn't we consider doing a 5.0.0 release that would support Java 8 or we
want to go Java8 at 4.10.0 ?
Otherwise I can't review, but I should be able to help on testing.
---
If
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1641
LGTM, the only change is to move the catch block to the end so the
ResultSet is not closed once the code comes out of the try-catch block.
---
If your project is set up for it, you can reply to
GitHub user abhinandanprateek opened a pull request:
https://github.com/apache/cloudstack/pull/1641
CLOUDSTACK-9459: the try's catch blick was shortening the preparedstatement
life
the try's catch blick was shortening the preparedstatement's life resulting
in bad resultset when
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1628
---
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
You are now on the Jira contributors list. You should be able to
assign issues.
Thanks,
~ Rajani
http://cloudplatform.accelerite.com/
On August 12, 2016 at 5:57 PM, ma...@exoscale.ch
(ma...@exoscale.ch) wrote:
Need some Jira love... Can someone give me the rights to assign
myself to this JIRA
Hi Jonas,
We've not yet updated the docs as we've not performed tests on/with
vCenter/ESXi 6 exhaustively. In practice, it does seem to work. We've an
automated Trillian [1] based environment where we're able to deploy an advanced
(CloudStack 4.9) zone with vCenter/ESXi 6 and get basic vm
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1638
Packaging result: âcentos6 âcentos7 âdebian repo:
http://packages.shapeblue.com/cloudstack/pr/1638
Job ID-86
---
If your project is set up for it, you can reply to this email
GitHub user marcaurele opened a pull request:
https://github.com/apache/cloudstack/pull/1640
CLOUDSTACK-9458: Fix HA bug when VMs are stopped on agent disconnect
VM are being restarted even if they don't have HA enabled. If the agent
gets back online before the command expires
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1638
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you
posted as I make progress.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1638
Thanks @marcaurele for your fix, it has been included in the 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
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1638
@blueorangutan package
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
38 matches
Mail list logo