f a network or vnet of a record
> op_dc_vnet_alloc is null or unsupported.
>
> can you share the following ?
>
> select id,vnet from op_dc_vnet_alloc;
> select id,broadcast_uri from networks where data_center_id is not null
> and broadcast_uri is not null;
>
>
> -W
@Wei ZHOU any thoughts ?
On Thu, Jun 13, 2024 at 9:29 PM Curious Pandora wrote:
> There are indeed 4 networks with NULL broadcast_uri that are causing the
> problem. I think those are systemic for cloudstack.
> +-+-+---+
>
Hello,
I think there is no way to make this work from cloudstack.
However, in case you are using openvswitch on your hosts you could try to
create a mirror there for egress, ingress or both
Let's say the vm machine port is vnet10.
Something like this could work for you:
# Add an internal port
;
> On Thu, Jun 13, 2024 at 11:35 AM Curious Pandora
> wrote:
> >
> > Hello, for vnet null there seems to be none:
> >
> > select * from op_dc_vnet_alloc where vnet IS NULL;
> > Empty set (0.001 sec)
> >
> > For API CALL:
> > GET
> listall
_vnet_alloc" table if there is a record with empty
> "vnet" ?
>
> select * from op_dc_vnet_alloc where vnet IS NULL;
>
>
> -Wei
>
> On Thu, Jun 13, 2024 at 10:02 AM Curious Pandora
> wrote:
> >
> > Hello,
> >
> > we get a 503 error
Hello,
we get a 503 error when trying to list guest vlans (both from web and api
call).
The relevant error log in the management server is:
ERROR [c.c.a.ApiServer] (qtp1278254413-1728:ctx-d3eec0e8 ctx-7b04643e)
(logid:6a2d2a44) unhandled exception executing api command:
[Ljava.lang.String;@1a84b
ore about the topology? Because by default you
> should not be creating vni/vxlan devices, cloudstack (modifyvxlan.sh)
> should be doing this for you.
>
> How are you using VXLAN in your environment? With BGP and EVPN up until
> the host?
>
> Wido
>
> >
> >
> &
*,
Maybe it's a good idea to add vni* in the list of accepted interfaces and
update the documentation to reflect that.
On Tue, Aug 1, 2023 at 9:45 AM Wido den Hollander wrote:
>
>
> Op 31-07-2023 om 11:57 schreef Curious Pandora:
> > Thanks for the reply. For some strange rea
nder wrote:
>
>
> Op 31/07/2023 om 10:03 schreef Curious Pandora:
> > Hello,
> >
> > just a quick confirmation if the VXLAN plugin can apply to
> > management/storage/public networks as well or is only implemented for
> guest
> > networks.
> >
regards,
> Sina
>
>
>
> --- Original Message ---
> On Monday, March 28th, 2022 at 19:07, Curious Pandora
> wrote:
>
>
> >
>
> >
>
> > Hello,
> >
>
> > We are in the process of migrating some of our VMs to a new zone wide NFS
>
Hello,
We are in the process of migrating some of our VMs to a new zone wide NFS
primary storage.
Some of the live and offline migrations went smoothly. However, no more
migrations can take place at the moment.
For an offline migration the host selected to do it by the scheduler
reports in cloud
com> wrote:
> Are you using overprovisioning?
>
> Em sáb., 26 de mar. de 2022 21:30, Curious Pandora
> escreveu:
>
> > After some further looking round and testing i am providing my findings.
> >
> > After monitoring all the database queries it is confirmed
normally but only 357MB
are actually allocated
That probably indicates some problem with the code.
On Thu, Mar 24, 2022 at 10:50 PM Curious Pandora wrote:
> Yes. I already confirmed that.
>
> +-+
> | service_offering_id |
> +-+
> |
check the database to see if the service offering is correct ?
>
> select service_offering_id from vm_instance where id=1410;
> select * from service_offering where id=;
>
> -Wei
>
>
>
> On Thu, 24 Mar 2022 at 09:23, Curious Pandora wrote:
>
> > Hello all,
> &g
Hello all,
After dedicating a pod for system vms (might have nothing to do with the
problem )
the virtual routers stopped working.
The routers cannot launch since they are created with 174080kb of memory.
174080
174080
According to the logs from the management server indeed the creation
param
Hello all,
After dedicating a pod for system vms (might have nothing to do with the
problem )
the virtual routers stopped working.
The routers cannot launch since they are created with 174080kb of memory.
174080
174080
According to the logs from the management server indeed the creation
param
16 matches
Mail list logo
