+1 Binding,
Done upgrades from 4.9, 4.11, 4,13 and 4.15 with different hypervisors. Also
tested basic lifecycle operations on VMs, networks, volumes and others. No
issues were found.
Regards,
Bobby.
From: Suresh Anaparti
Date: Friday, 25 February 2022, 17:09
To: d...@cloudstack.apache.org ,
Yes. Thank you! I appreciate the help.
-jeremy
> On Monday, Feb 28, 2022 at 4:15 AM, Wei ZHOU (mailto:ustcweiz...@gmail.com)> wrote:
> Hi Jeremy,
>
> When you create a zone, in the pod setting, you need to input the system Ip
> ranges. The private IPs of system vms are picked up from the range.
Hi Jeremy,
When you create a zone, in the pod setting, you need to input the system Ip
ranges. The private IPs of system vms are picked up from the range.
Reserved system gateway
Reserved system netmask
Start Reserved system IP
End Reserved system IP
Please make sure you have input correct value
Thanks. After some digging around, I figured it out and it’s basically exactly
what you said. I found what I was looking for under the Traffic Types in the
Physical Network config. This is where the ranges are defined for
Management/Guest/Public/Storage. I had some really strange ranges defined
Hi Jeremy,
Public : Accessible / reachable from outside of the CS environment; are not
controlled and managed by CS. Has nothing to do with the usal terminology
regarding "IP-Adresses".
Private: Internal networks within the cloudstack environment - management /
storage / guesttraffic (if not usin
For example, my secondary storage vm has this assigned:
IP Address
192.168.30.62
Private IP Address
192.168.30.55
The public IP is predictable because I see this in the config for public IP
addresses under Network, but the private IP changes each time the vm reboots.
Where is the 192.168.30.55
Hi Jeremy,
Each system vm must have a public IP and a private IP.
public IP of console proxy VM: access vm console from client
private IP of console proxy VM: establish vnc or websocket connection to
hypervisor for VM console.
public IP of secondary storage VM: download template or volume from c
I can cut out IPs to use for the system vm’s, but why do they need two
interfaces? Is there a way to turn off the private interface?
Thanks
-jeremy
> On Monday, Feb 28, 2022 at 2:50 AM, Wei ZHOU (mailto:ustcweiz...@gmail.com)> wrote:
> Hi Jeremy,
>
> CloudStack must know the static IP of system
Hi Jeremy,
CloudStack must know the static IP of system vms so that they can be
configured by CloudStack. You should have a better network plan. It is easy
to avoid IP conflicts.
-Wei
On Mon, 28 Feb 2022 at 10:59, Jeremy Hansen
wrote:
> I’m not talking about public as in externally routable IP
I’m not talking about public as in externally routable IPs. The system vms use
the terminology of public and private IPs which in my case is just two IPs on
the same internal subnet so it seems redundant for no real reason. In my case
public and private is the same network so why have two interf
Morning all,
Firstly - thanks Bobby for volunteering and organising the GSoC2022.
I am writing just to support and share my opinion. This initiative is quite
important as it attracts new users to our community. We need to grow the
CloudStack family and get more developers engaged, who can help u
What do you mean by "static IPs"?
The system vms will continue to need the usual networks in Cloudstack.
You will need to look at the "management" and "public" (and "secondary
storage" if you specified that expressly) networks in Cloudstack, see if
there are any changes you can do to integra
12 matches
Mail list logo
