Shulou(Shulou.com)06/02 Report--

System environment VMware workstation

System CentOS-7-x86_64-DVD-1810

The following should be noted: this article is composed of several blogs. The author recorded some mistakes along the way in order to avoid forgetting, such as 10.10.10.0.0and24, which should be changed to 10.1.1.0mm24. In order to save time, part of the figure depends on https://www.linuxprobe.com/chapter-22.html.

The / etc/hosts file needs to be modified before installation to add 127.0.0.1 op.sealin.top (op.sealin.top is the current machine name)

# yum install-y http://rdo.fedorapeople.org/rdo-release.rpm

# yum install-y openstack-packstack

# packstack-- allinone / / an error is reported here in the execution. One is about NetworkManager. You can close it, but execute it to control.pp and then close the demo module. The command is as follows:

# packstack-allinone-provision-demo=n

Welcome to Installer setup utility

Installing:

Clean Up [DONE]

Setting up ssh keys [DONE]

Discovering hosts' details [DONE]

Adding pre install manifest entries [DONE]

Preparing servers [DONE]

Adding AMQP manifest entries [DONE]

Adding MySQL manifest entries [DONE]

Adding Keystone manifest entries [DONE]

Adding Glance Keystone manifest entries [DONE]

Adding Glance manifest entries [DONE]

Adding Cinder Keystone manifest entries [DONE]

Adding Cinder manifest entries [DONE]

Checking if the Cinder server has a cinder-volumes vg [DONE]

Adding Nova API manifest entries [DONE]

Adding Nova Keystone manifest entries [DONE]

Adding Nova Cert manifest entries [DONE]

Adding Nova Conductor manifest entries [DONE]

Creating ssh keys for Nova migration [DONE]

Gathering ssh host keys for Nova migration [DONE]

Adding Nova Compute manifest entries [DONE]

Adding Nova Scheduler manifest entries [DONE]

Adding Nova VNC Proxy manifest entries [DONE]

Adding Openstack Network-related Nova manifest entries [DONE]

Adding Nova Common manifest entries [DONE]

Adding Neutron API manifest entries [DONE]

Adding Neutron Keystone manifest entries [DONE]

Adding Neutron L3 manifest entries [DONE]

Adding Neutron L2 Agent manifest entries [DONE]

Adding Neutron DHCP Agent manifest entries [DONE]

Adding Neutron LBaaS Agent manifest entries [DONE]

Adding Neutron Metering Agent manifest entries [DONE]

Adding Neutron Metadata Agent manifest entries [DONE]

Checking if NetworkManager is enabled and running [DONE]

Adding OpenStack Client manifest entries [DONE]

Adding Horizon manifest entries [DONE]

Adding Swift Keystone manifest entries [DONE]

Adding Swift builder manifest entries [DONE]

Adding Swift proxy manifest entries [DONE]

Adding Swift storage manifest entries [DONE]

Adding Swift common manifest entries [DONE]

Adding Provisioning Demo manifest entries [DONE]

Adding MongoDB manifest entries [DONE]

Adding Ceilometer manifest entries [DONE]

Adding Ceilometer Keystone manifest entries [DONE]

Adding Nagios server manifest entries [DONE]

Adding Nagios host manifest entries [DONE]

Adding post install manifest entries [DONE]

Installing Dependencies [DONE]

Copying Puppet modules and manifests [DONE]

Applying 192.168.1.105_prescript.pp

192.168.1.105_prescript.pp: [DONE]

Applying 192.168.1.105_amqp.pp

Applying 192.168.1.105_mysql.pp

192.168.1.105_amqp.pp: [DONE]

192.168.1.105_mysql.pp: [DONE]

Applying 192.168.1.105_keystone.pp

Applying 192.168.1.105_glance.pp

Applying 192.168.1.105_cinder.pp

192.168.1.105_keystone.pp: [DONE]

192.168.1.105_glance.pp: [DONE]

192.168.1.105_cinder.pp: [DONE]

Applying 192.168.1.105_api_nova.pp

192.168.1.105_api_nova.pp: [DONE]

Applying 192.168.1.105_nova.pp

192.168.1.105_nova.pp: [DONE]

Applying 192.168.1.105_neutron.pp

192.168.1.105_neutron.pp: [DONE]

Applying 192.168.1.105_neutron_fwaas.pp

Applying 192.168.1.105_osclient.pp

Applying 192.168.1.105_horizon.pp

192.168.1.105_neutron_fwaas.pp: [DONE]

192.168.1.105_osclient.pp: [DONE]

192.168.1.105_horizon.pp: [DONE]

Applying 192.168.1.105_ring_swift.pp

192.168.1.105_ring_swift.pp: [DONE]

Applying 192.168.1.105_swift.pp

Applying 192.168.1.105_provision_demo.pp

192.168.1.105_swift.pp: [DONE]

192.168.1.105_provision_demo.pp: [DONE]

Applying 192.168.1.105_mongodb.pp

192.168.1.105_mongodb.pp: [DONE]

Applying 192.168.1.105_ceilometer.pp

Applying 192.168.1.105_nagios.pp

Applying 192.168.1.105_nagios_nrpe.pp

192.168.1.105_ceilometer.pp: [DONE]

192.168.1.105_nagios.pp: [DONE]

192.168.1.105_nagios_nrpe.pp: [DONE]

Applying 192.168.1.105_postscript.pp

192.168.1.105_postscript.pp: [DONE]

Applying Puppet manifests [DONE]

Finalizing [DONE]

* Installation completed successfully*

Additional information:

Irectory.

.

Create the configuration file of the network card for the cloud platform: [root@op ~] # DEVICE=br-ex IPADDR=192.168.3.91 NETMASK=255.255.255.0 BOOTPROTO=static DNS1=192.168.3.1 GATEWAY=192.168.3.1 BROADCAST=192.168.3.254 NM_CONTROLLED=no DEFROUTE=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no ONBOOT=yes DEVICETYPE=ovs TYPE= "OVSIntPort" OVS_BRIDGE=br-ex modify the parameter information of the network card as follows: [root@openstack ~] # DEVICE= "ens33" ONBOOT=yes TYPE=OVSPort DEVICETYPE=ovs OVS_BRIDGE=br-ex NM_CONTROLLED=no IPV6INIT=no Add card devices to OVS network: [root@openstack ~] # [root@openstack ~] # 55501ff1-856c-46f1-8a00-5c61e48bb64d Bridge br-ex Port br-ex Interface br-ex type: internal Bridge br-int fail_mode: secure Port br-int Interface br-int type: internal Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Bridge br-tun Port patch-int Interface patch-int type: patch options: {peer=patch-tun} Port br-tun Interface br-tun type: internal Ovs_version: "2.1.3" restart the system to synchronize network devices: [root@op ~] # reboot

/ / Landing platform http://192.168.3.91/dashboard

View password

# cat / root/keystonerc_admin

Export OS_USERNAME=admin

Export OS_TENANT_NAME=admin

Export OS_PASSWORD=3b63bde2721349d0

Export OS_AUTH_URL= http://192.168.1.105:5000/v2.0/

Openstack creates a network:

Click to create a subnet:

Subnet details:

Create a VPC

Add routing information

Fill in the route name:

Set the gateway information for the route:

Set up the gateway:

Add interfaces to the network topology:

Add interface information:

Openstack installs windown system

In principle, it is installed through kvm and then uploaded to openstack. Most of them are installed in this way on the Internet, but you have to download the virtio driver first and search the Internet for it.

Virt-install-connect qemu:///system-name win7-ram 4080-vcpus 2-network=default,model=virtio-disk path=/tmp/win7.qcow2,format=qcow2,device=disk,bus=virtio-cdrom / tmp/win7.iso-disk path=/tmp/virtio-win-0.1.160.iso,device=cdrom-graphics spice,listen=0.0.0.0-boot cdrom

There are two problems here. One is that the cdrom cannot be read because the device names of win7.iso and win-0.1.160.iso are upside down. Just set win7.iso to hda,win-0.1.160.iso and hdb. The other is stuck in start windows. At first, it was said on the Internet that the value of-- video was changed to cirrus, but it had no effect. Later, it was found that it was the problem of the simulator. Because my environment was vmware, the simulator had to be changed.

Virsh destroy win7 stop win7

Vi / etc/libvirt/qemu/win7.xml

Dev options can be exchanged. They have already been exchanged on the way.

Virsh define / etc/libvirt/qemu/win7.xml

Virsh destroy win7 & & virsh start win7

Enter the viostor driver corresponding to the normal driver of the system, at first I thought it was vioscsi, but I thought the driver was not good, then it can be installed normally, and other drivers, such as network cards and graphics cards, will be installed after installation.

At this time, we are done, and we have successfully made a mirror image of qcow2. Next, deploy to glance.

Glance image-create-name "windows7"-file home/house/windows7.qcow2-disk-format qcow2-container-format bare-visibility public-progress

Error: you must provide a username via either-- os-username or Env [OS _ USERNAME]

Because I changed the password before.

The solution is to execute the following command under the root user

Source keystonerc_admin

Then execute the upload command

When you are finished, you can see the image on the openstack platform, and then you can start to create the virtual machine.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.