andrijapanicsb commented on pull request #809:
URL:
https://github.com/apache/cloudstack-primate/pull/809#issuecomment-710169692
Agree @nvazquez - my bad for not giving this input to @davidjumani , thx for
pointing out
This
davidjumani opened a new issue #23:
URL: https://github.com/apache/cloudstack-kubernetes-provider/issues/23
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
davidjumani commented on pull request #22:
URL:
https://github.com/apache/cloudstack-kubernetes-provider/pull/22#issuecomment-710111511
Tests pass. Good to go @onitake
```
go test -v ./...
=== RUN TestReadConfig
--- PASS: TestReadConfig (0.00s)
=== RUN TestNewCSCloud
rhtyd merged pull request #17:
URL: https://github.com/apache/cloudstack-kubernetes-provider/pull/17
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
UR
Hi Everyone,
I hope that you are all coping with the weird world that we are in at the
moment. And my best wishes to anyone and everyone and hope that we can all
get together at a collab again soon.
I emailed a few months ago to make sure that there were no problems with
having a code freeze in
No way automatically, manually is OK and the only way forward since you are
on the same version all the time.
Best,
On Fri, 16 Oct 2020, 10:00 Darrin Hüsselmann, <
darrin.husselm...@shapeblue.com> wrote:
> Hi Rakesh,
>
> db changes are applied automatically if the Cloudstack version changes and
nvazquez commented on pull request #809:
URL:
https://github.com/apache/cloudstack-primate/pull/809#issuecomment-710047611
@andrijapanicsb @DaanHoogland @davidjumani we should only hide if its Vmware
and deploy-as-is, for the older templates that should be still visible
-
andrijapanicsb commented on pull request #810:
URL:
https://github.com/apache/cloudstack-primate/pull/810#issuecomment-709917783
LGTM, displayed nicely, merging.
This is an automated message from the Apache Git Service.
To r
andrijapanicsb merged pull request #810:
URL: https://github.com/apache/cloudstack-primate/pull/810
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
blueorangutan commented on pull request #809:
URL:
https://github.com/apache/cloudstack-primate/pull/809#issuecomment-709916165
Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian
:heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/809 (JID-3
blueorangutan commented on pull request #809:
URL:
https://github.com/apache/cloudstack-primate/pull/809#issuecomment-709911781
@davidjumani a Jenkins job has been kicked to build primate packages. I'll
keep you posted as I make progress.
-
davidjumani commented on pull request #809:
URL:
https://github.com/apache/cloudstack-primate/pull/809#issuecomment-709911205
@blueorangutan package
This is an automated message from the Apache Git Service.
To respond to the
blueorangutan commented on pull request #810:
URL:
https://github.com/apache/cloudstack-primate/pull/810#issuecomment-709908305
Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian
:heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/810 (JID-3
blueorangutan commented on pull request #810:
URL:
https://github.com/apache/cloudstack-primate/pull/810#issuecomment-709903724
@davidjumani a Jenkins job has been kicked to build primate packages. I'll
keep you posted as I make progress.
-
davidjumani commented on pull request #810:
URL:
https://github.com/apache/cloudstack-primate/pull/810#issuecomment-709903479
@blueorangutan package
This is an automated message from the Apache Git Service.
To respond to the
DaanHoogland commented on pull request #809:
URL:
https://github.com/apache/cloudstack-primate/pull/809#issuecomment-709896894
ok, in view of `deploy-as-is` this makes sense, but I think it should
blocked/handled in the API as well.
---
Hi Rakesh,
db changes are applied automatically if the Cloudstack version changes and
there is an upgrade path in the code, I think you may have not changed version.
Cheers
Darrin
From: Rakesh Venkatesh
Sent: Friday, October 16, 2020 9:56 AM
To: users ; dev
Sub
Hello Users and Dev
Is there a way a new DB schema changes can be applied automatically
whenever I install new packages? My setup was running with two month old
changes of 4.15 and when I deployed new packages with latest changes, all
the recent db scheme changes are not applied and I need to run
davidjumani opened a new pull request #810:
URL: https://github.com/apache/cloudstack-primate/pull/810
### Before :
### After :
