How to specify a static IP when creating a ZStack virtual machine?

When creating a private cloud host, Zstack needs to select the network, primary storage, image, resource specifications, and possibly physical machines and clusters.

When creating a public cloud host, zstack needs to select an image, security group, network, computing specifications, and possibly an availability zone. In contrast, it is impossible for a public cloud to see a physical machine, while a private cloud cannot see an Availability Zone, and the computing specifications and network models of the two may be completely different.

You can put them on the same page, but whether it's one page or two pages is a step for the user's operation path, so it doesn't make much sense.

What really makes ZStack so seamless is that it makes the operation feel completely seamless. That is, the creation process is exactly the same, and all resources do not need to go to the public cloud console for additional search, and all operations can be completed locally in a closed loop.

Do you first click on the configuration information page of the virtual machine details page, select a network under the network card, and click the operation next to the network card? >?Set the Specify IP button, set the specified IP for the virtual machine, and remember to turn off the virtual machine before the operation.

You can try to execute this command:

root@localhost ] zstack-ctl configure sets the IP address of the management node [root@localhost ] zstack-ctl restar node Restart the management node service.

I also picked it up from the official website, if it doesn't work, you can go to zstack and search it again.

Generally, when there are multiple network cards and IP addresses on the system (for example, one is an internal network and the other is an external network), Zstack will default to the IP address of the network card used by the default routing of the system.

root@ceph-host ~]# zstack-ctl configure

where $ is the IP address that the user wants to specify quietly.

If the original hostname in the image is localhost, DHCP changes the hostname to be related to the IP address. For example, if the IP address of the virtual machine is set, then the virtual host hostnme will become 192-168-12-3.

Broken green carp clucked 6 yes 6 directory x5

?Check whether the default gateway inside the virtual machine is configured and reachable.

Check whether the physical link is reachable. Make sure that the corresponding Layer 2 network is wired exactly the same on each physical machine.

I asked a friend of mine who has used zstack, you can use it as a reference. You can add a new IP range to the L3 network and delete the original one, and then restart the virtual machine to reassign the IP in the new IP range.

zstack allows you to add two primary storage to a cluster. But if the primary storage type is different, such as a localstorage and an NFS. If you create a virtual machine again, the root disk will be created in localstorage by default, and the data disk will be created in NFS by default.

This situation needs to be paid attention to.