[GitHub] [cloudstack-kubernetes-provider] onitake commented on issue #19: Fix License headers to files

[GitBox]

onitake commented on issue #19:
URL: 
https://github.com/apache/cloudstack-kubernetes-provider/issues/19#issuecomment-702593380


   I'll take care of it.
   
   A few question with respect to [the 
policy](https://www.apache.org/legal/src-headers.html):
   - Should I add a license header to Makefile and Dockerfile?
   - go.mod is at least partially autogenerated by Go. Does it need a license 
header?
   - go.sum is fully autogenerated, I don't think a license header is required 
(or makes even sense) there
   - What about the example manifests deployment.yaml and 
nginx-ingress-controller-patch.yml?
   
   Anything else I forgot?



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-kubernetes-provider] onitake commented on issue #16: [DISCUSS] Work on next release

[GitBox]

onitake commented on issue #16:
URL: 
https://github.com/apache/cloudstack-kubernetes-provider/issues/16#issuecomment-702596507


   @rhtyd I think we are ready to cut a release when CI is set up and the 
outstanding issues are fixed (i.e. #19 , #18 , #17 )
   
   The version we're running in production is equivalent to what's in the 
source tree right now, and it's working very well.
   
   Should I prepare a changelog with respect to the initial source drop? Or a 
full "initial release" note?



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-kubernetes-provider] onitake opened a new issue #20: Update the Kubernetes frameworks

[GitBox]

onitake opened a new issue #20:
URL: https://github.com/apache/cloudstack-kubernetes-provider/issues/20


   We're currently building against a very old Kubernetes framework version: 
1.15.2
   The project is already at 1.19, with 1.20 in alpha.
   
   Update all frameworks to the latest stable version and keep them up to date.
   This may require fixing incompatibilities and should be thoroughly tested on 
different cluster versions.
   
   Automated testing may be very useful, see also #4 .



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-kubernetes-provider] onitake commented on issue #16: [DISCUSS] Work on next release

[GitBox]

onitake commented on issue #16:
URL: 
https://github.com/apache/cloudstack-kubernetes-provider/issues/16#issuecomment-702603951


   Going through all the issues, there is another thing we might want to 
consider, but I'm not sure if it should be done for 1.0:
   
   We're building against an older version of the k8s framework (1.15.2), and 
Kubernetes is already at 1.19. The Kubernetes project guarantees compatibility 
+/- two version steps, so we may already have issues with 1.19. But I currently 
don't have a way to test this.
   
   If you're ok with it, I think we should release 1.0 built against the old 
framework, as that's what we tested with.
   Post-1.0 we should fix #20 and #13. The k8s project recommends to always 
build against the latest framework code, so we may want to regularly update 
frameworks and test against different cluster versions.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-www] DaanHoogland merged pull request #77: Update security page

[GitBox]

DaanHoogland merged pull request #77:
URL: https://github.com/apache/cloudstack-www/pull/77


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-www] DaanHoogland commented on pull request #77: Update security page

[GitBox]

DaanHoogland commented on pull request #77:
URL: https://github.com/apache/cloudstack-www/pull/77#issuecomment-702613653


   @svenvogel (cc @PaulAngus ) is a publication action in order now?



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

RE: Dev Environment

[Klahre, Dirk]

Hi Gregor,

thanks for your answer.
You're right, solved my problem too. :)

Thanks for your help
Regards
Dirk


Dirk Klahre
Cloud Stack Developer - Cloud Management Platform
GMS Cloud Infrastructure Services



We Transform. Trust into Value

itelligence Global Managed Services GmbH ▪ Breitscheidstrasse 48 ▪ 01237 Dresden
phone: +49 3591 5253-1562 ▪
e-mail: dirk.kla...@itelligence.de

www.itelligencegroup.com



Wir halten Sie immer auf dem Laufenden!
Folgen Sie uns auf unseren Social Media Kanälen:
Xing LinkedIn Facebook Twitter

Profitieren Sie vom Know-how unserer Experten – mit dem itelligence 
Infoservice! Jetzt kostenlos registrieren!



itelligence Global Managed Services GmbH ▪ Sitz: Bautzen ▪ Handelsregister: 
Amtsgericht Dresden, HRB 21356
Geschäftsführer: Mirko Kruse ▪ André Walter
-Original Message-
From: Riepl, Gregor (SWISS TXT) 
Sent: Donnerstag, 1. Oktober 2020 14:16
To: dev@cloudstack.apache.org
Subject: Re: Dev Environment

EXTERNAL MAIL:


Hi Dirk,


My second problem is with git branches. My problem here is that I wanted to use 
the cloudstack version 4.13.1 as base, for this reason I checkout the 4.13.1 
branch, but the build process goes wrong with a couple of errors, after this I 
checkout the master and revert it to the commit 
b2ffa3e.

But the build process still didn’t work. Then I thought  that I have  problems 
with my dev environment and test the build process with the official release, 
but this works fine. So now I’m a little bit confused. What should I do, when I 
want to use a specific code base version?


I had similar problems when I tried to build tags, but I can't quite remember 
how I solved them.
Note that there is no 4.13.1 branch, only 4.13. There is a tag for 4.13.1.0 
though. Perhaps you should try again with the HEAD of 4.13?

Your best option will probably be to clean out any build leftovers and maybe 
even your Maven cache, then try again. There may also be subtle differences in 
building with IntelliJ and from the command line.

Regards,
Gregor

[GitHub] [cloudstack-kubernetes-provider] onitake opened a new pull request #21: Add missing license headers

[GitBox]

onitake opened a new pull request #21:
URL: https://github.com/apache/cloudstack-kubernetes-provider/pull/21


   Fixes: #19 



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] DaanHoogland opened a new issue #785: [BUG] boot into setup dissapeared

[GitBox]

DaanHoogland opened a new issue #785:
URL: https://github.com/apache/cloudstack-primate/issues/785


   **Describe the bug**
   A boot into setup check is expected in the instance action start and reboot 
as are shown in the vm wizard:
   
   https://user-images.githubusercontent.com/2486961/94930482-c16b4300-04c6-11eb-897f-795a7a5c596f.png";>
   
   https://user-images.githubusercontent.com/2486961/94930488-c4feca00-04c6-11eb-8296-f4da52192405.png";>
   
   https://user-images.githubusercontent.com/2486961/94930499-c7f9ba80-04c6-11eb-8aee-d5639fcff6b7.png";>
   
   **To Reproduce**
   Steps to reproduce the behavior:
   
   1. Log in as a User or an Admin
   2. Go to '...'
   3. Click on ''
   4. Scroll down to ''
   5. See error
   
   **Expected behavior**
   A clear and concise description of what you expected to happen.
   
   **Screenshots**
   If applicable, add screenshots to help explain your problem.
   
   **Desktop (please complete the following information):**
- OS: [e.g. Windows, Mac, iOS, Android with device/screen details if 
applicable]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
   
   **Additional context**
   Add any other context about the problem here.
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] DaanHoogland commented on issue #785: [BUG] boot into setup dissapeared

[GitBox]

DaanHoogland commented on issue #785:
URL: 
https://github.com/apache/cloudstack-primate/issues/785#issuecomment-702746207


   @davidjumani @shwstppr looks like a regression since the initial merge. I 
noticed during taking screenshots for an intro doc. do you have a quick 
assesment? cc @rhtyd 



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-cloudmonkey] soreana opened a new pull request #70: Added new option to change default cmk config file.

[GitBox]

soreana opened a new pull request #70:
URL: https://github.com/apache/cloudstack-cloudmonkey/pull/70


   Cloudmonkey command lets us use a different config file rather than the 
default one. This pull request added the same functionality to the `cmk` 
command.
   
   ```
   cmk -c ./my-config
   ```



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org