[GitHub] [cloudstack-documentation] blueorangutan removed a comment on pull request #262: ipv6: support for isolated nw, vpc tiers

[GitBox]

blueorangutan removed a comment on pull request #262:
URL: 
https://github.com/apache/cloudstack-documentation/pull/262#issuecomment-1026491404


   @shwstppr a Jenkins job has been kicked to build the document. I'll keep you 
posted as I make progress.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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

[GitHub] [cloudstack-documentation] shwstppr removed a comment on pull request #262: ipv6: support for isolated nw, vpc tiers

[GitBox]

shwstppr removed a comment on pull request #262:
URL: 
https://github.com/apache/cloudstack-documentation/pull/262#issuecomment-1026490926


   @blueorangutan docbuild


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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

[GitHub] [cloudstack-documentation] shwstppr commented on pull request #262: ipv6: support for isolated nw, vpc tiers

[GitBox]

shwstppr commented on pull request #262:
URL: 
https://github.com/apache/cloudstack-documentation/pull/262#issuecomment-1026578546


   @blueorangutan docbuild


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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

[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #262: ipv6: support for isolated nw, vpc tiers

[GitBox]

blueorangutan commented on pull request #262:
URL: 
https://github.com/apache/cloudstack-documentation/pull/262#issuecomment-1026579175


   @shwstppr a Jenkins job has been kicked to build the document. I'll keep you 
posted as I make progress.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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

[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #262: ipv6: support for isolated nw, vpc tiers

[GitBox]

blueorangutan commented on pull request #262:
URL: 
https://github.com/apache/cloudstack-documentation/pull/262#issuecomment-1026579800


   Doc build preview: http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/262. 
(SL-JID 185)


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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

[GitHub] [cloudstack-documentation] blueorangutan removed a comment on pull request #262: ipv6: support for isolated nw, vpc tiers

[GitBox]

blueorangutan removed a comment on pull request #262:
URL: 
https://github.com/apache/cloudstack-documentation/pull/262#issuecomment-1026579175






-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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

[GitHub] [cloudstack-documentation] shwstppr removed a comment on pull request #262: ipv6: support for isolated nw, vpc tiers

[GitBox]

shwstppr removed a comment on pull request #262:
URL: 
https://github.com/apache/cloudstack-documentation/pull/262#issuecomment-1026578546


   @blueorangutan docbuild


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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

[GitHub] [cloudstack-documentation] shwstppr commented on pull request #262: ipv6: support for isolated nw, vpc tiers

[GitBox]

shwstppr commented on pull request #262:
URL: 
https://github.com/apache/cloudstack-documentation/pull/262#issuecomment-1026584044


   @blueorangutan docbuild


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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

[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #262: ipv6: support for isolated nw, vpc tiers

[GitBox]

blueorangutan commented on pull request #262:
URL: 
https://github.com/apache/cloudstack-documentation/pull/262#issuecomment-1026585443


   @shwstppr a Jenkins job has been kicked to build the document. I'll keep you 
posted as I make progress.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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

[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #262: ipv6: support for isolated nw, vpc tiers

[GitBox]

blueorangutan commented on pull request #262:
URL: 
https://github.com/apache/cloudstack-documentation/pull/262#issuecomment-1026586743


   Doc build preview: http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/262. 
(SL-JID 186)


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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

Testing 4.16.1

[Boris Stoyanov]

Hi guys,

I’ve created this view: 
https://github.com/orgs/apache/projects/24/views/20?groupedBy%5BcolumnId%5D=Assignees

It shows all the tickets marked with ‘needs-testing’ label, if you have 
bandwidth and willingness to join the testing efforts please pick an item and 
assign it to yourself.

When you’re done testing please share your results and either yay or nay the pr 
in the review section, especially if you need something merged in 4.16.1

Thanks,
Bobby.

 

Re: [DISCUSS] Log4j migration

[Daan Hoogland]

completely agree, Rohit.

On Mon, Jan 31, 2022 at 8:01 AM Rohit Yadav 
wrote:

> All,
>
> Given there are no objections or other thoughts discussed on the thread, I
> propose the following:
>
>   *   Short-term: switch to reload4j which is a drop-in replacement and
> has published a few releases since last two weeks (seems active), this will
> require less effort for the benefit of updates/fixes that we'll get
> immediately.
>
>   *   Long-term: refactor the logging usage across codebase with a utility
> wrapper (in cloud-utils) where the logging library can be replaced with
> something like logback (which seems more mature and maintained). The
> long-term option can be discussed after we move to the drop-in replacement
> and it turns out to be not maintained or has issues.
>
> I've started a WIP PR draft for the short-term solution
> https://github.com/apache/cloudstack/pull/5878
>
>
>
> Regards.
>
> 
> From: Daan Hoogland 
> Sent: Wednesday, January 19, 2022 18:23
> To: dev 
> Cc: us...@cloudstack.apache.org 
> Subject: Re: [DISCUSS] Log4j migration
>
> As I was involved it shouldn't come as a surprise to anyone that I agree
> with Rohit on all he says here.
> There was one consideration that we (both) abandoned quite early on; making
> a pluggable framework for logging in which one can add their own preferred
> library. We do not think it is worth the effort, but as a GSoC project or
> if someone is willing to sponsor that it can still be put back on the
> table.
> I have a slight preference for the wrapper solution but am open to any
> input from everyone.
>
> On Wed, Jan 19, 2022 at 1:17 PM Rohit Yadav 
> wrote:
>
> > All,
> >
> > Following log4jshell advisory [1], I want to start a discussion thread
> > around what next steps should we follow.
> >
> > Overview: The log4j 1.x has limited feature set and didn't have the same
> > attack surface as log4j 2.x, this saved the ACS community from log4jshell
> > [1]. In addition, our uber/fat jar build process since (last few years)
> > only bundles classes from dependency jars that CloudStack management
> server
> > codebase requires; this may benefit that certain classes which could be
> > exploit-able in 1.x weren't actually shadowed/bundled in the
> > cloudstack-management uber/fat jar[2]. This strategy reduces the
> CloudStack
> > management uber/far jar's attack surface greatly.
> >
> > What is used in CloudStack: (details investigated with my colleague Daan)
> >
> >   *   Basic logging feature (console/file/rsyslog appenders, log levels,
> > log4j config file)
> >   *   Context-aware logging (this includes full/abbreviated class/package
> > name, and sometimes specific context,
> >
> > LogContext and CallContext have some example use of MDC, NDC)
> >
> >   *   Stacktrace upon exception, a custom CglibThrowableRenderer class
> >   *   Jar dependencies used: log4j v1.2.17, and apache-log4j-extras
> v1.2.17
> >
> > As the next step, I think it would be better to refactor the logging
> usage
> > to a new loggging utility in cloud-utils which can be used throughout the
> > codebase, and this utility can in-turn wrap whatever logging library we
> use
> > and reduce our dependency on any logging library/version and swiftly
> change
> > logging library. The utility may also allow us to centrally add custom
> > cloudstack feature (such as context-aware logging, manage stacktrace
> output
> > etc).
> >
> > I did some research to look at possible options for the community:
> >
> >   1.  Status-Quo, stick with log4j 1.x: this is not ideal, as v1.2.17 was
> > the last release in 1.x which has reach EOL [3].
> >   2.  Migrate to 2.x: this is probably what is advised by the Apache
> > Logging PMC [4] since 1.x has EOL, however:
> >  *   1.x pretty much sufficed our requirements of a logging library
> > and 2.x has a large attack surface.
> >  *
> >  *   Other Apache projects (such as hadoop, hive etc) are facing
> while
> > migrating their large codebases to log4j 2.x; the migration will require
> > time, effort, and testing. The 2.x migration guide would require a lot of
> > manual effort, there is no tooling to do this at scale.
> >  *   On Twitter, some of the Logging PMC have advised that their v3
> > architecture will make log4j modular and lower attach surfaces.
> >  *   My opinion: Logging library shouldn't try to do anything beyond
> > logging, I'm less confident in migrating to 2.x after seeing how the CVE
> > was handled by the Logging PMC and I didn't have a good interaction with
> > them in a ML discussion thread. For an ASF TLP that is asked to adhere to
> > the 'community over code' spirit, the user community isn't listend to and
> > in a ML thread, it was deemed that any 1.x fork/maintenance would be
> > considered "hostile" - this has led to interested sponsors and PMCs of
> > other Apache projects joining forces with Ceki to continue log4j 1.x fork
> > outside of ASF (see below).
> >   3.  Migrate t

Announcement: CloudStack European User Group Virtual - April 7th, 2022

[Ivet Petrova]

Hello,

I am excited to announce that the CloudStack European User Group will be 
organising its first meet-up for the year as a virtual event.
The event will happen on April 7th and when we finalise the agenda, we will be 
able to share exact timings also.

At this stage, the Call for Speakers is now open! Deadline for all submissions 
- February 25th 2022, 23:59PM!
Be sure you support the community by submitting your idea for a conference talk.

Submit your talk here:
https://forms.gle/rX5q31KwiJiXdngQ9

Stay tuned for more details soon!



Kind regards,


 

[RESULT] [VOTE] Release Apache CloudStack Terraform Provider v0.4.0

[Harikrishna Patnala]

Hi all,

The vote for CloudStack Terraform Provider v0.4.0 *passes* with
3 PMC + 3 non-PMC votes.

+1 (PMC / binding)
3 persons (Rohit, Daan, Boris)

+1 (non binding)
3 persons (Pearl, Vladi, Suresh)

0
none

-1
none

Thanks to everyone participating.

I will now prepare the release announcement to go out after 24-48 hours to give 
the mirrors time to catch up.

Regards,
Harikrishna

 

Re: [PROPOSE] RM for 4.17

[Suresh Kumar Anaparti]

+1

Thanks for volunteering again, good luck Nicolas!

Regards,
Suresh

On Tue, Feb 1, 2022 at 2:02 AM Gabriel Beims Bräscher 
wrote:

> Sounds good.
> Thaks, Nicolas.
>
> On Mon, Jan 31, 2022, 19:42 Rohit Yadav  wrote:
>
> > Sounds good to me, thanks for volunteering Nicolas.
> >
> >
> > Regards.
> >
> > 
> > From: Boris Stoyanov 
> > Sent: Monday, January 31, 2022 13:58
> > To: dev@cloudstack.apache.org ;
> > us...@cloudstack.apache.org 
> > Cc: dev@cloudstack.apache.org 
> > Subject: Re: [PROPOSE] RM for 4.17
> >
> > +1, I can help with triage/testing and any other business Nicolas, let me
> > know if you need any additional hands.
> >
> > Bobby.
> >
> > From: Ivet Petrova 
> > Date: Friday, 28 January 2022, 16:11
> > To: us...@cloudstack.apache.org 
> > Cc: dev@cloudstack.apache.org 
> > Subject: Re: [PROPOSE] RM for 4.17
> > Nicolas,
> > Just to mention you did a great job last time!
> >
> > Kind regards,
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On 28 Jan 2022, at 16:05, Nicolas Vazquez  > > wrote:
> >
> > Dear All,
> >
> > I would like to put myself forward as the release manager for 4.17.0.0.
> >
> > I propose we have a window of at least 6 weeks to allow the community and
> > users to test and report issues, I will propose the timeline details
> soon.
> >
> > I hope to have your support. Please let me know if you have any thoughts
> /
> > comments.
> >
> > Regards,
> > Nicolas Vazquez
> >
> >
> >
> >
>

[GitHub] [cloudstack-documentation] weizhouapache commented on pull request #261: vmware: Add supported minor versions

[GitBox]

weizhouapache commented on pull request #261:
URL: 
https://github.com/apache/cloudstack-documentation/pull/261#issuecomment-1026732580


   @blueorangutan docbuild
   
   


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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

[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #261: vmware: Add supported minor versions

[GitBox]

blueorangutan commented on pull request #261:
URL: 
https://github.com/apache/cloudstack-documentation/pull/261#issuecomment-1026733407


   @weizhouapache a Jenkins job has been kicked to build the document. I'll 
keep you posted as I make progress.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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

[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #261: vmware: Add supported minor versions

[GitBox]

blueorangutan commented on pull request #261:
URL: 
https://github.com/apache/cloudstack-documentation/pull/261#issuecomment-1026734392


   Doc build preview: http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/261. 
(SL-JID 187)


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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

[GitHub] [cloudstack-terraform-provider] DaanHoogland commented on issue #31: Failure to add secondary IP to a NIC for a VM in a project

[GitBox]

DaanHoogland commented on issue #31:
URL: 
https://github.com/apache/cloudstack-terraform-provider/issues/31#issuecomment-1026876854


   I have run your config changing only the keys and ids at the top. I needed 
to munaually create the project called 'myProject' but then the environment 
deployed without errors. I checked if the network existed in the project and if 
the VM had a secondary ip. all good. also destroying went without error 
messages.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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

[GitHub] [cloudstack-terraform-provider] DaanHoogland commented on issue #31: Failure to add secondary IP to a NIC for a VM in a project

[GitBox]

DaanHoogland commented on issue #31:
URL: 
https://github.com/apache/cloudstack-terraform-provider/issues/31#issuecomment-1026878010


   not sure what your issue was but something else must have been in play, 
@Pearl1594 . Note however that I executed it in a simulated environment.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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

Re: [PROPOSE] RM for 4.17

[Nicolas Vazquez]

Thanks all for your support!

I propose the following timelines for the 4.17.0.0 release, which is targeted 
for Q1/Q2 2022.

- (7-8 weeks) Ongoing – Mid March 2022: Accept all bugs, issues, improvements 
allowed in LTS [1]
- (1 week) Stabilise the 4.17 branch, accept only critical/blocker issues (if 
any)
- End March 2022 and onwards: Cut 4.17.0.0 RC1 and further RCs if necessary, 
start/conclude vote, and finish release work

My colleague Boris will assist me during the process for 
reviewing/testing/merging the PRs. You can find the open issues and PRs at the 
4.17.0.0 Github milestone [2]. Ping me (@nvazquez) or Boris (@borisstoyanov) on 
your issues and PRs, that are to be included in 4.17.0.0.

Looking forward for your support on bug fixes, reviews, tests, etc. Thanks.

[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
[2] https://github.com/apache/cloudstack/milestone/21

Regards,
Nicolas Vazquez


From: Suresh Kumar Anaparti 
Date: Tuesday, 1 February 2022 at 08:07
To: dev 
Cc: us...@cloudstack.apache.org 
Subject: Re: [PROPOSE] RM for 4.17
+1

Thanks for volunteering again, good luck Nicolas!

Regards,
Suresh

On Tue, Feb 1, 2022 at 2:02 AM Gabriel Beims Bräscher 
wrote:

> Sounds good.
> Thaks, Nicolas.
>
> On Mon, Jan 31, 2022, 19:42 Rohit Yadav  wrote:
>
> > Sounds good to me, thanks for volunteering Nicolas.
> >
> >
> > Regards.
> >
> > 
> > From: Boris Stoyanov 
> > Sent: Monday, January 31, 2022 13:58
> > To: dev@cloudstack.apache.org ;
> > us...@cloudstack.apache.org 
> > Cc: dev@cloudstack.apache.org 
> > Subject: Re: [PROPOSE] RM for 4.17
> >
> > +1, I can help with triage/testing and any other business Nicolas, let me
> > know if you need any additional hands.
> >
> > Bobby.
> >
> > From: Ivet Petrova 
> > Date: Friday, 28 January 2022, 16:11
> > To: us...@cloudstack.apache.org 
> > Cc: dev@cloudstack.apache.org 
> > Subject: Re: [PROPOSE] RM for 4.17
> > Nicolas,
> > Just to mention you did a great job last time!
> >
> > Kind regards,
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On 28 Jan 2022, at 16:05, Nicolas Vazquez  > > wrote:
> >
> > Dear All,
> >
> > I would like to put myself forward as the release manager for 4.17.0.0.
> >
> > I propose we have a window of at least 6 weeks to allow the community and
> > users to test and report issues, I will propose the timeline details
> soon.
> >
> > I hope to have your support. Please let me know if you have any thoughts
> /
> > comments.
> >
> > Regards,
> > Nicolas Vazquez
> >
> >
> >
> >
>

 

Re: Not able to autoscale kubernetes cluster

[Ranjit Jadhav]

Hello folks,

Any insight on this? We are facing the same issue.

Regards,
Ranjit

On Mon, 31 Jan 2022 at 22:48, Rishabh Rapatwar 
wrote:

> Hi all,
>
> I am trying to autoscale kubernetes cluster, but it's not working.
> Following are the logs of cluster-autoscaler pod in kube-system:
>
> I0131 17:01:11.537869   1 client.go:175] NewAPIRequest response status
> code:200
> I0131 17:01:11.538288   1 cloudstack_manager.go:88] Got cluster :
> &{c6496415-daea-4051-993a-3b9f9c58242e voyager 1 3 2
>  1 [0xc000e889f0 0xc000e88a20 0xc000e88a50]}
> E0131 17:01:11.538366   1 static_autoscaler.go:271] Failed to get node
> infos for groups: Unable to find node voyager-c
> ontrol-17ea9f68878 in cluster
> I0131 17:01:21.538749   1 static_autoscaler.go:229] Starting main loop
>
> ACS version used is 4.16, and kubernetes version is 1.22.2
>
> Can anyone please help here?
>
>
> Thankyou,
> Rishabh
>

[GitHub] [cloudstack-documentation] Pearl1594 commented on pull request #259: Add CKS compatibility matrix details

[GitBox]

Pearl1594 commented on pull request #259:
URL: 
https://github.com/apache/cloudstack-documentation/pull/259#issuecomment-1027645909


   @blueorangutan docbuild


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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

[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #259: Add CKS compatibility matrix details

[GitBox]

blueorangutan commented on pull request #259:
URL: 
https://github.com/apache/cloudstack-documentation/pull/259#issuecomment-1027646387


   @Pearl1594 a Jenkins job has been kicked to build the document. I'll keep 
you posted as I make progress.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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

[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #259: Add CKS compatibility matrix details

[GitBox]

blueorangutan commented on pull request #259:
URL: 
https://github.com/apache/cloudstack-documentation/pull/259#issuecomment-1027647175


   Doc build preview: http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/259. 
(SL-JID 188)


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

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