Hi,
As said in the error message, there are some networks associated with this
physical network.
SELECT * FROM networks WHERE physical_network_id= AND
removed IS NULL;
-Wei
On Fri, 12 Jan 2024 at 08:42, Bryan Tiang wrote:
> Hi Suresh,
>
> We tried that as well but still got the same result.
Hi All,
VLAN and many other things was managed by proxmox infra.
And I already follow confluence page for ssvm troubleshooting and found that
gateway is not pinged. I will again raise my issue as below,
1. When ISO has been adding then error encountered that “There is no secondary
storage VM fo
Hi Suresh,
We tried that as well but still got the same result.
This is really interesting… We are scratching our heads.
Regards,
Bryan
On 12 Jan 2024 at 1:30 PM +0800, Suresh Kumar Anaparti
, wrote:
> Hi Bryan,
>
> It's the integer id of the physical network, not uuid.
>
> with uuid, check w
Congratulations Alex
From: Nux
Date: Thursday, 11 January 2024 at 3:58 AM
To: Dev , Users
Subject: New committer: Alexandre Mattioli
All,
The Project Management Committee (PMC) for Apache CloudStack
has invited Alexandre Mattioli to become a committer and we are pleased
to announce that they ha
Hi Bryan,
It's the integer id of the physical network, not uuid.
with uuid, check with this.
SELECT * FROM cloud.op_dc_vnet_alloc WHERE physical_network_id = (SELECT id
FROM cloud.physical_network WHERE uuid = '') AND
taken IS NOT NULL
Regards,
Suresh
On Fri, Jan 12, 2024 at 10:55 AM Bryan Tian
Hi Bharat,
Can you check the VLAN configuration on the switch ports? Make sure the SSVM
vNICs are on the expected bridges?
-Jithin
From: Bharat Bhushan Saini
Date: Thursday, 11 January 2024 at 11:38 PM
To: ustcweiz...@gmail.com , ji...@linservers.com
Cc: users@cloudstack.apache.org
Subject:
Hi Suresh,
So sorry for this. But we ran the query and this was the result.
Could it be something else?
Regards,
Bryan
On 11 Jan 2024 at 8:39 PM +0800, Suresh Kumar Anaparti
, wrote:
> Hi Bryan,
>
> From the code, the error is due to some allocated vlans found through the
> below query. If the
Hi All,
We are running Cs 4.15.0.0 with 2 KVM hosts having security groups enabled
zone. We have a VM which a GRE tunnel has been setup between it and a
server outside our network. Both hosts had been rebooted a few days ago due
to power interruption. Before the reboot happens, the GRE tunnel was
Hi Fariborz,
Sorry if misunderstanding but I think you may want to create a new Shared
network on the Networks section (not entering through the Zone and Physical
network), and define the IP range on the network creation. Once created you can
navigate to Networks -> Shared network -> IP ranges
Hi.
I have now successfully managed to add the new IP range using the old UI at
Infrastructure -> Zone -> Physical Network -> Guest -> Network -> View IP
ranges. However, in the new UI, there is nowhere to manage shared guest
network IP ranges. I don't have public traffic type setup. All VMs are
a
Hi Wei and Jimmy,
I already deployed cloudstack version 4.18 with 1 management server included
mysql and nfs in it and 1 kvm with libvirt, also both system was running on the
ubuntu 22.04 LTS.
After adding a zone, facts are below,
1. Zone is enabled.
2. Host server is up and running.
3.
Hi,
Can you go to Zone -> Physical Network -> Traffic Types -> Public and check if
the IP ranges added are visible there.
Thanks,
Pearl
From: Wei ZHOU
Sent: January 11, 2024 10:53 AM
To: users@cloudstack.apache.org
Subject: Re: Urgent - Cannot manage shared IP
Do you use old or new UI ?
Do you use an advanced zone with or without security groups ?
On Thu, 11 Jan 2024 at 16:40, Fariborz Navidan
wrote:
> Hello Friends,
>
> I have a very urgent problem with adding new shared IP address range (CIDR)
> in a advanced zone. We are running 4.15.0.0 and I had
Hello Friends,
I have a very urgent problem with adding new shared IP address range (CIDR)
in a advanced zone. We are running 4.15.0.0 and I had configured multiple
shared IP address CIDRs in previous version 4.14. In 4.14, we could manage
IP ranges by going to Zone -> Physical Network -> Guest ->
If you want to play or test cloudstack on a single server, you can try with
https://github.com/shapeblue/mbx
-Wei
On Thu, 11 Jan 2024 at 13:36, Bharat Bhushan Saini
wrote:
> Hi Jimmy,
>
>
>
> It is ok with the nested virtualization but I want to try it.
>
> May in future I will move it to the
Hi Bryan,
>From the code, the error is due to some allocated vlans found through the
below query. If the result is empty, that error doesn't appear.
SELECT * FROM cloud.op_dc_vnet_alloc WHERE physical_network_id = AND taken IS NOT NULL
Regards,
Suresh
On Thu, Jan 11, 2024 at 3:57 PM Bryan Tian
Hi Jimmy,
It is ok with the nested virtualization but I want to try it.
May in future I will move it to the dedicated infra.
Thanks and Regards,
Bharat Saini
[signature_3857218017]
From: Jimmy Huybrechts
Date: Thursday, 11 January 2024 at 5:43 PM
To: users@cloudstack.apache.org
Subject: Re: A
Hi,
I believe combining proxmox and cloudstack is not supported at all since
proxmox does things with KVM in their own way.
If you want to run Cloudstack on top of proxmox you would get nested
virtualization.
--
Jimmy
Van: Bharat Bhushan Saini
Datum: donderdag, 11 januari 2024 om 13:08
Aan: u
Hi All,
May anyone help me for the deployment of the apache cloudstack on the proxmox
infra.
If anyone will help me I will be grateful to him.
Kindly reply on that mail to make two way communication.
Thanks and Regards,
Bharat Saini
[signature_1984116516]
--- Disclaimer
Congrats Alex!
From: Slavka Peleva
Sent: Thursday, January 11, 2024 12:22 PM
To: users@cloudstack.apache.org
Cc: d...@cloudstack.apache.org
Subject: Re: New committer: Alexandre Mattioli
Congrats Alex!
On Thu, Jan 11, 2024 at 8:51 AM Abhishek Kumar wrote:
> C
Hi Suresh,
Sorry, its Version 4.18.1
Yes its the same error message as before:
Delete physical network: (Physical Network 1) The Physical Network is not
deletable because there are allocated vnets for this physical network
Version: 4.18.1
Hypervisor: Linux Ubuntu
Storage: Linbit
Regards,
Brya
Hi Suresh,
Yes its the same error message as before:
Delete physical network: (Physical Network 1) The Physical Network is not
deletable because there are allocated vnets for this physical network
Version: 4.18
Hypervisor: Linux Ubuntu
Storage: Linbit
Regards,
Bryan
On 11 Jan 2024 at 5:46 PM +
Hi Bryan,
If 'taken' / other columns are NULL, you should see different error. Can
you confirm if it is still the same error for that physical network? What's
the cloudstack version you are using?
Regards,
Suresh
On Thu, Jan 11, 2024 at 2:13 PM Bryan Tiang
wrote:
> Hi Suresh,
>
> We set it Nul
Hi Suresh,
We set it Null and got the same error:
i. Updated 'taken' to NULL - same error
ii. Updated the other columns to NULL - same error
iii. Restarted management service and retry - same error
Did we do something wrong?
Regards,
Bryan
On 11 Jan 2024 at 4:24 PM +0800, Suresh Kumar Anaparti
Hi Bryan,
If there are no network / nics for the vlan, you can update 'taken' to NULL
for that vlan in the op_dc_vnet_alloc table.
Check network / nics usage with the below queries before update.
SELECT * FROM cloud.networks WHERE broadcast_uri LIKE '%%';
SELECT * FROM cloud.nics where broadcast_
25 matches
Mail list logo
