GitHub user remibergsma opened a pull request:
https://github.com/apache/cloudstack/pull/1067
implemented upgrade path from 4.6.0 to 4.6.1
The 4.6 branch needs an upgrade path to 4.6.1. I looked at how this was
done before and think this will do. Can you give it a second pair of eye
Github user DaanHoogland commented on the pull request:
https://github.com/apache/cloudstack/pull/1067#issuecomment-156810107
looks good, let's run a test anyway. the jenkins should run it but it it's
running on a INFRA-10703 host so it will most likely fail.
---
If your project is s
Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/1067#issuecomment-156812719
@DaanHoogland I rebased it, as it needs the `checkstyle` fix in 4.6.
---
If your project is set up for it, you can reply to this email and have your
reply appea
Github user DaanHoogland commented on the pull request:
https://github.com/apache/cloudstack/pull/1067#issuecomment-156813885
merged with 4.6 branch and:
```
INFO [c.c.s.ManagementServerImpl] (main:ctx-1c73e37e) Startup CloudStack
management server...
INFO [c.c.c.ClusterM
Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/1067#issuecomment-156820839
This is an upgrade from 4.6.0 to 4.6.1:
```
INFO [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Running system
integrity checker com.cloud.upg
Github user DaanHoogland commented on the pull request:
https://github.com/apache/cloudstack/pull/1067#issuecomment-156821756
so, you have my lgtm, need a second 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 yo
Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/1067#issuecomment-156821894
Yes, let's stick to the rules :-)
---
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 projec
Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/1064#issuecomment-156827648
@wilderrodrigues Can you please make this PR against 4.6 instead of master?
It will then be included in 4.6.1 and also be merged forward to master.
---
If your
GitHub user remibergsma opened a pull request:
https://github.com/apache/cloudstack/pull/1068
Make master 4.7.0-SNAPSHOT and implement upgrade paths towards it
This bumps all pom.xml versions to 4.7.0-SNAPSHOT. It also implements
upgrade paths from 4.6.0 and the upcoming 4.6.1 (bran
Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/1068#issuecomment-156842157
This is an upgrade from `4.6.1` to `4.7.0`:
```
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) DB version = 4.6.1 Code
Version = 4.7.0-SNAPSHOT
Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/1068#issuecomment-156845271
This is an `4.6.0` to `4.7.0` upgrade:
```
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) DB version = 4.6.0 Code
Version = 4.7.0-SNAPSHOT
INF
Github user milamberspace commented on the pull request:
https://github.com/apache/cloudstack/pull/1067#issuecomment-156846865
LGTM
Works on my test deployment.
2015-11-15 19:52:41,711 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null)
Cleanup script
/usr/share/cloudstack-m
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1067
---
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
Hi all,
Congratulations on the release of Apache CloudStack 4.6.0. A new release is
always great, but this time it is even better that we released it off a stable
master!
Thanks for everyone's understanding when we had to freeze master for quite some
weeks. It helped, as we were able to make m
Github user milamberspace commented on the pull request:
https://github.com/apache/cloudstack/pull/1068#issuecomment-156859431
LGTM
Tested on a 4.6.1 to 4.70 with success
2015-11-15 22:00:04,726 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null)
Cleanup script
/usr/sha
Github user DaanHoogland commented on the pull request:
https://github.com/apache/cloudstack/pull/1068#issuecomment-156860838
compiled and started with no errors. tests are running but irrelevant for
this PR: LGTM
---
If your project is set up for it, you can reply to this email and
GitHub user pdion891 opened a pull request:
https://github.com/apache/cloudstack-docs-rn/pull/25
4.6
once LGTM, this will be merged into master and 4.6 branch will be created.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pdion8
Github user abhinandanprateek commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/768#discussion_r44887112
--- Diff:
framework/quota/src/org/apache/cloudstack/quota/constant/QuotaConfig.java ---
@@ -0,0 +1,53 @@
+//Licensed to the Apache Software
Github user abhinandanprateek commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/768#discussion_r44887207
--- Diff: framework/db/src/com/cloud/utils/db/Transaction.java ---
@@ -59,4 +59,30 @@ public T doInTransaction(TransactionStatus status)
throws
Github user karuturi commented on the pull request:
https://github.com/apache/cloudstack/pull/1068#issuecomment-156911523
4.6 has 4.6 to 4.6.1 upgrade path
and master has 4.6 to 4.7 upgrade path
once 4.6 is merged to master, wont there be a problem with upgrade path on
mas
I find it easier to use devcloud4[1]. It the easiest way for xen6.2
devcloud setup.
The documentation is also good. Just install the required tools/IP configs
mentioned in README [2]. Then, go to the advanced and follow the readme[3]
there for a advanced zone setup.
[1] https://github.com/apache/c
Github user karuturi commented on the pull request:
https://github.com/apache/cloudstack-docs-rn/pull/25#issuecomment-156922033
Thanks for taking this up @pdion891
Thanks for fixing all the package urls to one consistent source :+1:
Reviewed through the preview in github LGTM
Github user karuturi commented on the pull request:
https://github.com/apache/cloudstack/pull/1068#issuecomment-156939746
remi mentioned on slack that master already has 461to470. so, the merge
wont be a problem.
In future, during the first merge after any release, we should take c
Yes, ovm3 support is in 4.6.
Sent from my iPhone
> On 16 Nov 2015, at 02:52, Pierre-Luc Dion (JIRA) wrote:
>
>
>[
> https://issues.apache.org/jira/browse/CLOUDSTACK-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006139#comment-15006139
> ]
Github user karuturi commented on the pull request:
https://github.com/apache/cloudstack-docs-install/pull/24#issuecomment-156943469
There is no 4.6 yet. I am merging this to master
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack-docs-install/pull/24
---
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
Github user karuturi commented on the pull request:
https://github.com/apache/cloudstack-docs/pull/11#issuecomment-156944043
@rajsekharkpally how did you verify that its rendering properly?
I think this should be .rst for sphinx to understand and render it
properly.
This shou
Github user karuturi commented on the pull request:
https://github.com/apache/cloudstack-docs/pull/12#issuecomment-156944122
:+1: merging
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack-docs/pull/12
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1068
---
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
30 matches
Mail list logo
