Bernd Bausch's profile - activity

If you want to run more than one VM, you need to:

• attach all VMs to the private network
• create a router between external and private network (done)
• associate the public IP as floating IP to one of the VMs

Is this address, 106.51.76.7, your public address? If so, you are done for that one VM. If not, add your public address to the external subnet.

Have a look at the external subnet. The allocation pools parameter gives you exactly one address. This means you can only run one VM on that network, then the address space is exhausted. I suppose no router can be attached for the same reason.

Did you connect the VM to the external network? If so, you can’t associate floating IPs with it. You don’t need to, either, since the VM’s address is already an external one.

Is there no other network connected to the router?

I have one public IP which I need to use to connect to a VM in OpenStack. I have created a network (external), subnet (with gateway and floating IP range) and a router too, which is connected with this subnet. But then when I try to associate this floating IP to an instance, it shows me no ports available. And when I go to interfaces in the router, this is shown:

(34bc8864-11ef) 106.51.xx.x Down External Gateway UP

Not sure how to resolve. Can someone please help me at the earliest please.

Edit 1:

openstack network show ext_net

+---------------------------+--------------------------------------+
| Field                     | Value                                |
+---------------------------+--------------------------------------+
| admin_state_up            | UP                                   |
| availability_zone_hints   |                                      |
| availability_zones        |                                      |
| created_at                | 2019-02-16T14:07:51Z                 |
| description               |                                      |
| dns_domain                | None                                 |
| id                        | ac9965f8-03f6-44ee-afde-c96a0834302d |
| ipv4_address_scope        | None                                 |
| ipv6_address_scope        | None                                 |
| is_default                | False                                |
| is_vlan_transparent       | None                                 |
| mtu                       | 1500                                 |
| name                      | ext_net                              |
| port_security_enabled     | True                                 |
| project_id                | ca908ee1456f4bd99ea6ed0f0f38b469     |
| provider:network_type     | flat                                 |
| provider:physical_network | default                              |
| provider:segmentation_id  | None                                 |
| qos_policy_id             | None                                 |
| revision_number           | 5                                    |
| router:external           | External                             |
| segments                  | None                                 |
| shared                    | False                                |
| status                    | ACTIVE                               |
| subnets                   | 7826a1dc-d22e-4c00-af78-865501bf96cf |
| tags                      |                                      |
| updated_at                | 2019-02-16T14:39:32Z                 |
+---------------------------+--------------------------------------+

openstack router show ext_router

+-------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Field                   | Value                                                                                                                                                                                   |
+-------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| admin_state_up          | UP                                                                                                                                                                                      |
| availability_zone_hints |                                                                                                                                                                                         |
| availability_zones      | nova                                                                                                                                                                                    |
| created_at              | 2019-02-16T14:18:44Z                                                                                                                                                                    |
| description             |                                                                                                                                                                                         |
| distributed             | False                                                                                                                                                                                   |
| external_gateway_info   | {"network_id": "ac9965f8-03f6-44ee-afde-c96a0834302d", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "7826a1dc-d22e-4c00-af78-865501bf96cf", "ip_address": "106.51.76.7"}]} |
| flavor_id               | None                                                                                                                                                                                    |
| ha                      | False                                                                                                                                                                                   |
| id                      | a1f8a7d4-5ead-437a-8b6c-ae71783510f5                                                                                                                                                    |
| interfaces_info         | []                                                                                                                                                                                      |
| name                    | ext_router                                                                                                                                                                              |
| project_id              | ca908ee1456f4bd99ea6ed0f0f38b469                                                                                                                                                        |
| revision_number         | 14                                                                                                                                                                                      |
| routes                  |                                                                                                                                                                                         |
| status                  | ACTIVE                                                                                                                                                                                  |
| tags                    |                                                                                                                                                                                         |
| updated_at              | 2019-02-16T14:39:51Z                                                                                                                                                                    |
+-------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

openstack subnet show ext_subnet

+-------------------+--------------------------------------+
| Field             | Value                                |
+-------------------+--------------------------------------+
| allocation_pools  | 106.51.76.7-106.51.76.7              |
| cidr              | 106.51.0.0/16                        |
| created_at        | 2019-02-16T14:39:32Z                 |
| description       |                                      |
| dns_nameservers   | 202.83.21.12, 202.83.21.2            |
| enable_dhcp       | True                                 |
| gateway_ip        | 106.51.64.1                          |
| host_routes       |                                      |
| id                | 7826a1dc-d22e-4c00-af78-865501bf96cf |
| ip_version        | 4                                    |
| ipv6_address_mode | None                                 |
| ipv6_ra_mode      | None                                 |
| name              | ext_subnet                           |
| network_id        | ac9965f8-03f6-44ee-afde-c96a0834302d |
| project_id        | ca908ee1456f4bd99ea6ed0f0f38b469     |
| revision_number   | 0                                    |
| segment_id        | None                                 |
| service_types     |                                      |
| subnetpool_id     | None                                 |
| tags              |                                      |
| updated_at        | 2019-02-16T14:39:32Z                 |
+-------------------+--------------------------------------+

I urge you to learn the fundamentals of Linux first. LVM is part of that.

As to your problem, I would like to know the details of your Cinder backend. Also, the output of the lsblk command on the server where you tried pvs and vgs.

If the router interface has the same IP as the VM, this can’t work.

By “details” I meant the output of openstack network show, router show and subnet show. You can edit it into your question.

If you don’t know what is LVM, you should not manage an OpenStack cloud. LVM is the logical volume manager; the vgs and pvs commands belong to it.

Of course cinder-volume adds some load, so in principle it does affect the controllers' performance. Probably not in a measurable way though.

You don't need to run cinder-volume on separate servers or VMs when your only Cinder backend is Ceph.

The only setting that is relevant to networking is the last one. Packstack won't set up any tenant router or network. You have to do that manually. Can you share your network and router details? You can edit them into the question.

Did you create this cloud? If so, how?

Can you show the details of your networks, subnets and routers?

What precise command or GUI options do you use to associate the floating IP, and what is the precise error message?

All I know is https://www.rdoproject.org/install/pa....

How about sharing the answerfile variables that you modified?

The nova api log helps you to find the request ID of the snapshot API. It starts with req- and is followed by a hex string.

Find the request ID in Nova logs to get more info.

could it be that you misconfigured the network?

No need for setting up bridges or anything else, just run the packstack command and you should be able to reach the instances via their floating IPs. If not, the setup was not correct. Did you create a default Packstack cloud or did you specify parameters or an answer file?

Devstack runs well in a 8GB VM, too. Packstack as well. Both are automatic methods for setting up a functioning cloud that you can then experiment with. Probably not bad advice at all, although you get a deeper understanding from the installation tutorials.

I was in a similar situation 5 years ago, although I had more time. Learning this in two months is a challenge. On the other hand, OpenStack was my first exposure to cloud computing.

You need to have a good grasp of Linux system administration. The usual platforms for installing OpenStack are RHEL/Centos, Ubuntu or SLES/OpenSuse. Pick one.

A good basis of Networking and Virtualization is strongly recommended.

Reading Python programs and knowing how to print log messages will help but is not mandatory in my opinion.

Everybody learns in a different way. I started reading the documentation, but every sentence contained at least two terms that I had not heard of before. So I went practical and followed the installation tutorial. It took me three days or so until my toy cloud was functional. This was hard work but forced me to learn.

I suggest you find a Linux box (e.g. a laptop with 16GB main memory, if possible an SSD), use KVM to create two virtual machines that you will install with one of the above operating systems, then follow the tutorial.

I did. See the blue text in my answer.

If you mean the Packstack host by "host OS", no particular setup is required. By default, Packstack creates a fake "external" network with an address of 172.24.4.0/28 (not sure about the 28) to which a route from the host exists.

Or if you need to install the software after the instance has booted for the first time, you could do something like

ssh INSTANCE_IP_ADDRESS apt-get install SOFTWARE

cloud-init runs when the instance boots for the first time. The user's mouse click could generate a YAML file which describes cloud-init's actions, and which you then use when launching the instance. Would this work for you?

That depends on your scripts. You could copy the scripts to the instance, log on to the instance and run the scripts.

Alternatively, you can use cloud-init to install software when the instance starts. To do this, write a cloud-init file and submit it to the instance using the --user-data option of the openstack server create command. See also the cloud-init documentation.

Of course, you can also use tools like Ansible or Puppet, but in my opinion the cloud-init option is the best for your requirement.

All I know is the page that lists the API calls. I have never used the OpenStack SDK. Perhaps in this case the principle is "the code is the documentation".

How about create_server_image?

I have the feeling that you are thoroughly confused though. Or I am confused by you. What do you want to achieve?

To log on, use ssh -i keyfile ubuntu@ip-address. If that doesn't work, perhaps you did not provide the key-name parameter when launching the instance.

you can give an instance any hostname you like. Log on to the instance and use the hostname command. To make the change permanent, most Linux distros keep the hostname in /etc/hostname, which you will have to edit.

ubuntuis the default account configured on ubuntu cloud images. See https://docs.openstack.org/image-guid....

ssh ubuntu@ip-address accesses the instance that has this IP address.

instance_name should be the name of an account configured on this instance. It should not be the name of an instance.

I wanted to know which parameters you used to launch the instance. Did you launch it with the correct keypair?

How did you create the instance?

As Deepa says. openstack server image create, then launch an instance from the image.

What do you mean by "no response" - do you get a prompt back, or does the command hang?

If the volume is in error status, check the Cinder log files for detailed information.

If you use LVM as a Cinder backend, and the vgs and pvs commands don't respond, it is not surprising that the volume can't be created. You should start by troubleshooting LVM.

The first one implements resource limits for VMs running on ESX, the second one changes the parameters used to configure the RAM, CPU and disk overbooking of compute hosts. They don’t look like they help with your requirement.

One thing looks wrong. Your answer file sets up the ML2 and the OVN plugins. Only one core plugin is possible. Try removing the OVN settings.

To summarize: You can ping the instance via its floating IP, but you can’t ping out from it. The instance is connected to a tenant network which a router connects to the external network. It can ping the router at 172.24.4.1. Correct?

This setting associates Neutron's external network to br-ex. However, I don't understand how you can access the instance via its floating ip under these circumstances.

Perhaps you missed os-neutron-ovs-bridge-mappings=extnet:br-ex. See https://www.rdoproject.org/networking....

Does it really say

AMQP server on 1172.xx.xx.xx:5672 is unreachable

i.e. 1172, not 172?

By the way, you may want to review the formatting of your question.

A remark: Your first link is about the current software release, whereas the second is about Mitaka, three years prior to Rocky.

Also, documentation pages feature a bug symbol. Click on it to report errors on the page.

Glad you found the error!