Well, after pocking around it looks that the problem is in the
cloudstack-agent.
When calling for com.cloud.agent.api.CheckNetworkCommand it is expected to
find interfaces such as eth*, bond*, team*, vlan*, em*, p*p*, ens*, eno*,
enp*, or enx*
In our case the interface is starting from vni*,
Ma
Op 04/08/2023 om 09:05 schreef Curious Pandora:
Well, after pocking around it looks that the problem is in the
cloudstack-agent.
When calling for com.cloud.agent.api.CheckNetworkCommand it is expected to
find interfaces such as eth*, bond*, team*, vlan*, em*, p*p*, ens*, eno*,
enp*, or enx*
Hello,
yes we utilize BGP and EVPN until the host. Then the vxlans are configured
for public/management/guest networks and the corresponding bridges are
created on top of those vnis.
The script will create the VNIs for the guest network on the guest bridge
and in the defined range and works as exp
Hi all,
Reminder that we will be having a user group meetup on August 18th in
Bangalore, India. You can register for the event here:
https://www.meetup.com/india-cloudstack-user-group/events/294738405/
Also we have an open CFP which will be active until next Friday, If you would
like to join wi
Hi Cristian,
I'm not sure, but could you try user data (cloud-init data) when you deploy a
VM. In there, you'll have flexibility to set the hostname of the VM to whatever
you'd like.
Regards.
From: [email protected]
Sent: Thursday, August 3, 2023 20:28
Hi Cristian,
In addition, in 4.18 a new feature - managed User data was introduced. This can
be used to register userdata with custom parameters - here, the hostname. And
when deploying the VM, the custom parameters could be set to the desired
values. You could refer to
https://www.shapeblue.c
Op 04/08/2023 om 13:07 schreef Curious Pandora:
Hello,
yes we utilize BGP and EVPN until the host. Then the vxlans are configured
for public/management/guest networks and the corresponding bridges are
created on top of those vnis.
But why do you create VXLAN devices for the public/guest net
Hi Rohit,
I didn't saw the display name in the metadata, this is why I ask:
{"vm_ip_address":"51.89.xx.xx","vm_metadata":[["userdata","user-data",null],
["metadata","service-offering","S-2"],["metadata","availability-zone","DE-00
1"],["metadata","local-ipv4","51.89.xx.xx"],["metadata","local-h
Hi Pearl,
I will test this when I upgrade to 4.18.x I'm waiting for 4.18.1.
Thank you,
Cristian
-Original Message-
From: Pearl d'Silva
Sent: Friday, August 4, 2023 4:24 PM
To: [email protected]
Subject: Re: set display_name as hostname to instances
Hi Cristian,
In additi
If you are using the UI to create the VM, set the name of the VM - this field
sets the hostname and the display name. So you should see this value in the
local-hostname file in the VR metadata folder.
If you are using the API, explicitly set the name field.
Let us know if you see the desired nam
The metadata does not show the display name for local-hostname, for both
parameters I see the name value of the VM, the deploy was made via API and I
provided only the display_name, where the display name is "displayname01".
As you see here, public and local have the same value, from vm name.
{"
11 matches
Mail list logo
