Re: IPV6 in Isolated/VPC networks

2021-07-15 Thread Hean Seng
Hi Wido, My initial thought is not like this, it is the /48 at ISP router, and /64 subnet assign to AdvanceZoneVR, AdvanceZoneVR responsible is distribule IPv6 ip (from the assigned /64 sunet) to VM, and not routing the traffic, in the VM that get the IPv6 IP will default route to ISP

Re: Can't select network offerings in new shared networks

2021-07-15 Thread Joshua Schaeffer
On 7/15/21 2:54 AM, Slavka Peleva wrote: > Hi Joshua, > > Can you check if the `VirtualRouter` provider is disabled and try to enable > it? Probably you're getting this error because it's disabled. You can check > the state with cloudmonkey/cmk ("list virtualrouterelements") or through DB >

Re: Failure to start Virtual Router after upgrade to 4.15.1

2021-07-15 Thread Slavka Peleva
That's great! :) On Thu, Jul 15, 2021 at 11:16 PM Edward St Pierre wrote: > Hi Slavka, > > You are a lifesaver, I had two versions of the api in the directory: > cloud-api-4.13.0.0.jar > cloud-api-4.15.1.0.jar > > Removed the old version from the previous update and all is good. Thanks > for

Re: Failure to start Virtual Router after upgrade to 4.15.1

2021-07-15 Thread Edward St Pierre
Hi Slavka, You are a lifesaver, I had two versions of the api in the directory: cloud-api-4.13.0.0.jar cloud-api-4.15.1.0.jar Removed the old version from the previous update and all is good. Thanks for your help. Ed On Thu, 15 Jul 2021 at 20:55, Slavka Peleva wrote: > Hi Eduard, > > Did

Re: Failure to start Virtual Router after upgrade to 4.15.1

2021-07-15 Thread Slavka Peleva
Hi Eduard, Did you upgrade and cloudstack agents? I guess that `cloud-api` jar in `/usr/share/cloudstack-agent/lib` is with an older version that does not have the method `isPrivateGateway` Best regards, Slavka On Thu, Jul 15, 2021 at 10:02 PM Edward St Pierre wrote: > Hello, > > Any help or

Failure to start Virtual Router after upgrade to 4.15.1

2021-07-15 Thread Edward St Pierre
Hello, Any help or pointers would be greatly appreciated. After upgrading CS Virtual routers to 4.15.1 The VM does actually get built and powers on (visible via console proxy), and then is suddenly powered off. and this error is displayed in the interface '(r-340-VM) Resource [Host:10] is

Re: New System Template for virtual routers

2021-07-15 Thread Edward St Pierre
Hi Wei, Yes same issue and removed the lock before asking the question. managed to update one of my VRs but unfortunately the others seem to be booting then shutting down. Will look into it a bit more later as I may have other problems too since updating from 4.15.0 to 4.15.1. Which might be

Re: [PROPOSE] RM for CloudStack Kubernetes Provider v1.0

2021-07-15 Thread Suresh Anaparti
+1 Good luck David! Regards, Suresh On 15/07/21, 12:02 PM, "David Jumani" wrote: Hi, I'd like to put myself forward as the release manager for CloudStack Kubernetes Provider v1.0. This will be the first release of

Re: New System Template for virtual routers

2021-07-15 Thread Wei ZHOU
Hi Edward, Is that same as what I reported at https://github.com/apache/cloudstack/issues/5138 ? removing /var/lock/conntrackd.lock solves the problem. -Wei On Thu, 15 Jul 2021 at 16:29, Edward St Pierre wrote: > Hi Guys, > > Is there a problem with the new system template? it appears that

Re: IPV6 in Isolated/VPC networks

2021-07-15 Thread Wido den Hollander
But you still need routing. See the attached PNG (and draw.io XML). You need to route the /48 subnet TO the VR which can then route it to the Virtual Networks behind the VR. There is no other way then routing with either BGP or a Static route. Wido Op 15-07-2021 om 12:39 schreef Hean Seng:

New System Template for virtual routers

2021-07-15 Thread Edward St Pierre
Hi Guys, Is there a problem with the new system template? it appears that there is a stale lock file for conntrackd, this is from a newly deployed virtual router that was not coming up properly: systemvm-kvm-4.15.1 Checksum:

Re: [PROPOSE] RM for CloudStack Kubernetes Provider v1.0

2021-07-15 Thread Simon Weller
+1 From: David Jumani Sent: Thursday, July 15, 2021 1:31 AM To: users ; d...@cloudstack.apache.org Subject: [PROPOSE] RM for CloudStack Kubernetes Provider v1.0 Hi, I'd like to put myself forward as the release manager for CloudStack Kubernetes

Security groups support in advanced zone

2021-07-15 Thread Wei ZHOU
Hi all, We are investigating security groups support in Advanced zones. it would be nice to get your feedback. Some background knowledge: (1) there are 3 types of zones in cloudstack: Basic, Advanced, Advanced with Security groups (support KVM and Xenserver. vmware is not supported) (2) Admins

Re: MySQL Version Clarity

2021-07-15 Thread Michael Kesper
Hi Andrija, Am 09.06.20 um 17:47 schrieb Andrija Panic: > Don't abuse MariaDB, as there is known incompatibilities (i.e. 5.5 would be > fine, but versions 10.x are known to not really work) > Community MySQL versions are fine, we usually use those. Did anyone investigate into the reasons for

VxLAN and XenServer/XCP-NG

2021-07-15 Thread Matthew Ritchie
Hello, I am in need of a quick confirmation. I am reading in the latest documentation for the VXLAN Plugin that "In CloudStack 4.X.0, this plugin only supports the KVM hypervisor with the standard linux bridge." Is this correct?...that I cannot use VxLAN with XenServer/XCP-NG ? thanks in

Re: IPV6 in Isolated/VPC networks

2021-07-15 Thread Hean Seng
Or explain like this : 1) Cloudstack generate list of /64 subnet from /48 that Network admin assigned to Cloudstack 2) Cloudsack allocated the subnet (that generated from step1) to Virtual Router, one Virtual Router have one subniet /64 3) Virtual Router allocate single IPv6 (within the range of

Re: IPV6 in Isolated/VPC networks

2021-07-15 Thread Hean Seng
Hi Wido, I think the /48 is at physical router as gateway , and subnet of /64 at VR of Cloudstack. Cloudstack only keep which /48 prefix and vlan information of this /48 to be later split the /64. to VR. And the instances is getting singe IPv6 of /64 IP. The VR is getting /64. The default

Re: IPV6 in Isolated/VPC networks

2021-07-15 Thread Wido den Hollander
Op 14-07-2021 om 16:44 schreef Hean Seng: Hi I replied in another thread, i think do not need implement BGP or OSPF, that would be complicated . We only need assign  IPv6 's /64 prefix to Virtual Router (VR) in NAT zone, and the VR responsible to deliver single IPv6 to VM via DHCP6. In

Re: Can't select network offerings in new shared networks

2021-07-15 Thread Slavka Peleva
Hi Joshua, Can you check if the `VirtualRouter` provider is disabled and try to enable it? Probably you're getting this error because it's disabled. You can check the state with cloudmonkey/cmk ("list virtualrouterelements") or through DB ("SELECT * FROM cloud.virtual_router_providers where

[PROPOSE] RM for CloudStack Kubernetes Provider v1.0

2021-07-15 Thread David Jumani
Hi, I'd like to put myself forward as the release manager for CloudStack Kubernetes Provider v1.0. This will be the first release of CloudStack Kubernetes Provider which facilitates Kubernetes deployments on Cloudstack. It allows