Ask Your Question

codylab's profile - activity

2019-10-29 05:58:04 -0600 received badge  Famous Question (source)
2019-01-22 17:06:58 -0600 commented answer Openstack queen instance creation error - No valid host was found.

Bernd: Thank you for letting me know about the Placement CLI. As for the error, I haven't got it fixed and will probably just go back to start afresh. Luckily, it was just a POC...

2019-01-22 09:45:26 -0600 commented answer Openstack queen instance creation error - No valid host was found.

I followed the above procedure and the two versions of UUIDs were in sync afterward. But then I started getting errors from nova-conductor during instance launch. That was the only trace and I haven't figured out a solution yet.

2019-01-22 09:37:55 -0600 commented answer Openstack queen instance creation error - No valid host was found.

@Bernd: what a great post! I run into the same issue due to a similar cause today. In my case, I redeployed my stack using openstack-ansible and ended up with the same "conflict of resource provider" error. I don't know how it could happen given ansible is supposed to be idempotent, but it happened.

2019-01-21 20:19:22 -0600 commented answer how to use br-vlan veth pair ? what is the benefit of veth?

.... In my case, I was unable to launch any instances because the neutron-linuxbridge-agent on network and compute nodes got terminated because it was unable to bind to "eth12" - which was non-existent on the hosts.

2019-01-21 20:16:23 -0600 commented answer how to use br-vlan veth pair ? what is the benefit of veth?

If you have extra nics to separate flat and vlan, there is no need to create a veth pair as per the example. If you followed the example without creating a veth pair, you may have a successful deployment, but would run into errors when creating flat or vlan networks....

2019-01-19 19:38:07 -0600 answered a question how to use br-vlan veth pair ? what is the benefit of veth?

I had the same question and below is what I understand after chatting on IRC. Please correct me if I am wrong.

It just so happens that in the example it used br-vlan for both flat and vlan traffics. Since you would need to map flat and vlan to two different interfaces in the physical_interface_mappings, the workaround was to create a veth pair (br-vlan-veth <--> eth12) for the flat network in this case. It then plugged one end (br-vlan-veth) to br-vlan and the other (eth12) to the neutron agent.

I think the proper br-vlan configuration for the /etc/network/interfaces should look like this:

auto br-vlan
iface br-vlan inet manual
    bridge_stp off
    bridge_waitport 0
    bridge_fd 0
    pre-up ip link add br-vlan-veth type veth peer name eth12 || true
    pre-up ip link set br-vlan-veth up
    pre-up ip link set eth12 up
    post-down ip link del br-vlan-veth || true
    bridge_ports bond1 br-vlan-veth    #here br-vlan-veth is plugged into br-vlan

A side node: if you are into OSA, you should consider joining the project's IRC channel at #openstack-ansible on Freenode. Many cool folks are out there to help.

2019-01-17 09:25:44 -0600 commented question How can I clear this nova installation problem ? please help me

Bernd: that was a great catch! :-) Hope it solved the problem.

2018-12-11 03:31:30 -0600 received badge  Famous Question (source)
2018-10-04 08:20:59 -0600 answered a question tripleo single-nic-vlans ip not assigned based on subnet in network_environment file
...
    - type: ovs_bridge
      name: bridge_name
    # use_dhcp: false # remove this line from controller and compute nic-config files
      dns_servers:
      get_param: DnsServers 
...
2018-10-04 08:13:29 -0600 commented question tripleo single-nic-vlans ip not assigned based on subnet in network_environment file

Remove the line use_dhcp: false from the ovs_bridge used by vlans for both controller and compute nic-config files. I think that should solve your problem.

2018-09-30 11:56:09 -0600 commented answer Queens OpenStack: Unable to Launch Instance Virtual Machine DHCP issue

As @Bernd suggested, could you verify if any AMQP errors occur at the time you launch an instance?

2018-09-30 07:47:24 -0600 commented answer Queens OpenStack: Unable to Launch Instance Virtual Machine DHCP issue

And if the compute node seemingly has enough RAM, please also check the reserved_host_memory_mb in /etc/nova/nova.conf on the compute node and make sure you still have enough RAM after deducting that value.

2018-09-30 07:39:25 -0600 commented answer Queens OpenStack: Unable to Launch Instance Virtual Machine DHCP issue

Hi @nag and @bernd. I faced similar issues before with virtual environment. How many RAM and vCPUs does your compute node have? It could simply because you did not have enough RAM left available for the flavor you choosed for CentOS.

2018-09-19 08:28:14 -0600 commented question issue with tripleo installation

No need to change undercloud in your case. The network for nic2 must be routable for external traffic, as noted in the configuration.

2018-09-19 07:33:54 -0600 commented question issue with tripleo installation

In that case, you can attach nic3 to a bridge for external traffic and modify the nic-configs/controller.yaml accordingly. The example in /usr/share/openstack-tripleo-heat-templates/network/config/multiple-nics/controller.yaml should be your friend :-)

2018-09-19 06:52:58 -0600 commented answer issue with tripleo on pre-deployed nodes

As replied in another post, it's impossible in this case. You have to keep a constant ssh connection during pre-provisioned deployment. External traffic requires to create a bridge (ovs or linuxbridge) and it will disconnect your existing ssh connection on that nic.

2018-09-19 06:45:03 -0600 commented question issue with tripleo installation

1) You can't. You need to keep a constant ssh connection during pre-provisioned deployment. If you attach nic1 to a bridge for the external traffic, your ssh would drop, and the deployment would hang. 2) That's the tag for the current Queens repo. 3) Default controller role includes storage services

2018-09-18 10:02:03 -0600 commented question issue with tripleo installation

To put external traffic on another network in this case, you either need to add another NIC or use vlan and network separation during deployment. To enable SSL on external endpoint, follow this guide

2018-09-18 09:48:58 -0600 commented answer issue with tripleo on pre-deployed nodes

The parameters section in nic-config templates uses a default format. You normally don't need to change anything there unless you add custom networks. The actual NIC configuration happens in the resources section.

2018-09-18 09:44:10 -0600 commented answer How to create an instance with a specific ip?

That also works for assigning a fixed IP to VM. The only caveat for this approach is to remember to delete the port after removing the instance, to avoid from leaving an orphaned port with a binded IP behind.

2018-09-17 11:11:39 -0600 commented answer issue with tripleo on pre-deployed nodes

How long did the "stuck" last? It could take a little while at certain stages depending on your system specs. Try to monitor the cpu utilization on undercloud and overcloud nodes during the progress.

2018-09-17 09:51:45 -0600 commented answer issue with tripleo on pre-deployed nodes

By "fresh booted up servers" you meant freshly installed OS not just a reboot, right? If you get an error you should be able to find some traces from the undercloud or the controller in overcloud. The last resort is to grep haproxy and error from the /var/log and see if you can find something there.

2018-09-17 09:19:16 -0600 received badge  Notable Question (source)
2018-09-17 08:44:24 -0600 commented answer issue with tripleo on pre-deployed nodes

You would need to delete previous stacks from the undercloud with openstack overcloud delete overcloud before redeploy anew. Otherwise, the new templates will not be applied properly. Also, your pre-provisioned nodes should be in "brand-new" state to avoid conflicts from previous configurations.

2018-09-17 04:10:08 -0600 received badge  Teacher (source)
2018-09-15 18:24:38 -0600 answered a question How to create an instance with a specific ip?

openstack server create --nic net-id=<net-uuid>,v4-fixed-ip=10.10.10.100 with other arguments.

2018-09-13 21:26:40 -0600 answered a question issue with tripleo on pre-deployed nodes

@akari I have made a pre-provisioned deployment according to your specs (i.e. 2 NICs per server, no network isolation or VLAN). Since this method requires an uninterrupted SSH connection between undercloud and overcloud servers during deployment, l used NIC1 for SSH and NIC2 for provisioning and overcloud traffics.

My local environment:

Networks
Network 1: 192.168.100.0/24 (isolated for SSH connection only)
Network 2: 192.168.24.0/24 (must be routable for external traffic) 

Undercloud
NIC1: 192.168.100.2
NIC2: 192.168.24.2

Controller
NIC1: 192.168.100.3
NIC2: 192.168.24.3

Compute
NIC1: 192.168.100.4
NIC2: 192.168.24.4

You would need to pass the following environment files along with others to the CLI (See bottom). All files and folders are placed under the /home/stack directory.

ctlplane-assignments.yaml (change IPs to your local settings)

resource_registry:
  OS::TripleO::DeployedServer::ControlPlanePort: /usr/share/openstack-tripleo-heat-templates/deployed-server/deployed-neutron-port.yaml

parameter_defaults:
  DeployedServerPortMap:
    controller-ctlplane:
      fixed_ips:
        - ip_address: 192.168.24.3 # nic2 address of pre-configured controller node
      subnets:
        - cidr: 24
    compute-ctlplane:
      fixed_ips:
        - ip_address: 192.168.24.4 # nic 2 address of pre-configured compute node
      subnets:
        - cidr: 24

network-environment.yaml (change IPs to your local settings)

resource_registry:
  OS::TripleO::ControllerDeployedServer::Net::SoftwareConfig: /home/stack/nic-configs/controller.yaml
  OS::TripleO::ComputeDeployedServer::Net::SoftwareConfig: /home/stack/nic-configs/compute.yaml

parameter_defaults:
  ControlPlaneSubnetCidr: '24'
  ControlPlaneDefaultRoute: 192.168.24.2  # undercloud local_ip
  ExternalInterfaceDefaultRoute: 192.168.24.1  # Network 2 gateway
  EC2MetadataIp: 192.168.24.2  # undercloud local_ip
  NeutronExternalNetworkBridge: "''"
  NeutronNetworkType: 'vxlan'
  NeutronTunnelTypes: 'vxlan'

nic-configs/controller.yaml

heat_template_version: queens
description: >
  Software Config to drive os-net-config to configure ovs bridge on NIC2 for the Controller role.
parameters:
  ControlPlaneIp:
    default: ''
    description: IP address/subnet on the ctlplane network
    type: string
  StorageIpSubnet:
    default: ''
    description: IP address/subnet on the storage network
    type: string
  StorageMgmtIpSubnet:
    default: ''
    description: IP address/subnet on the storage_mgmt network
    type: string
  InternalApiIpSubnet:
    default: ''
    description: IP address/subnet on the internal_api network
    type: string
  TenantIpSubnet:
    default: ''
    description: IP address/subnet on the tenant network
    type: string
  ExternalIpSubnet:
    default: ''
    description: IP address/subnet on the external network
    type: string
  ManagementIpSubnet:
    default: ''
    description: IP address/subnet on the management network
    type: string
  StorageNetworkVlanID:
    default: 30
    description: Vlan ID for the storage network traffic.
    type: number
  StorageMgmtNetworkVlanID:
    default: 40
    description: Vlan ID for the storage_mgmt network traffic.
    type: number
  InternalApiNetworkVlanID:
    default: 20
    description: Vlan ID for the internal_api network traffic.
    type: number
  TenantNetworkVlanID:
    default: 50
    description: Vlan ID for the tenant network traffic.
    type: number
  ExternalNetworkVlanID:
    default: 10
    description: Vlan ID for the external network traffic.
    type: number
  ManagementNetworkVlanID:
    default: 60
    description: Vlan ID for the management network traffic.
    type: number
  ControlPlaneSubnetCidr: 
    default: '24'
    description: The subnet CIDR of the control plane network.
    type: string
  ControlPlaneDefaultRoute: 
    description: The default route of the control plane network.
    type: string
  ExternalInterfaceDefaultRoute:
    default: '10.0.0.1'
    description: default route for the external network
    type: string
  DnsServers:
    default: []
    description: A list of DNS servers (2 max for some implementations) that will be added to resolv.conf.
    type: comma_delimited_list
  EC2MetadataIp ...
(more)
2018-09-12 18:54:13 -0600 commented question issue with tripleo on pre-deployed nodes

Hi akarki, bear with me as I am going to make a pre-provisioned deployment test on my gears at work. Will get back to you later.

2018-09-11 10:17:02 -0600 commented question issue with tripleo on pre-deployed nodes

In my case, I used NIC1 on a native vlan for undercloud control plane traffic and NIC2 for all VLANs traffics (including the external/floating IP network) on my overcloud nodes. Without knowing your network setup, the config files may not work.

2018-09-11 10:05:40 -0600 commented question issue with tripleo on pre-deployed nodes

Bear in mind that some "not-so-smart" switches require you to manually setup each VLAN ID for trunk ports. You may check with your switch manual for that.

2018-09-11 10:04:05 -0600 commented question issue with tripleo on pre-deployed nodes

Before we go further, first I want to make sure if you have configured the switch properly. If you have two NICs for each overcloud node, you need to set trunk ports for the NICs that carry VLAN traffics, if you choose to use network isolation.

2018-09-10 19:08:29 -0600 commented question issue with tripleo on pre-deployed nodes

Step 2 is for cluster configuration, including for Pacemaker, HAProxy , Galera/MySQL, etc. How many controller node(s) did you have? Did you use any custom roles or composable services? If using the default controller role (i.e. monolithic), It has to be either 1 or 3 controller nodes with Tripleo.

2018-09-06 10:29:41 -0600 commented question Issue with tripleo

the pre-provisioned approach does not use ironic to introspect overcloud nodes, hence no instackenv.json or ipmi stuff involved. In this case, the undercloud either uses DHCP to assign IPs to overcloud nodes, or use static IPs provided by..... remember your test-net.yaml file? :-)

2018-09-06 09:09:15 -0600 commented question enable external network endpoint in tripleo

Seems alright to me.

2018-09-06 07:44:48 -0600 commented question enable external network endpoint in tripleo

In short, the floating IP provides a 1-to-1 NAT on neutron router for the applied VM, so that external connections (e.g. from Internet) can reach the VM via a floating IP (which is a publicly routable one). It is the same as the "Elastic IP" in AWS.

2018-09-06 07:30:25 -0600 commented question enable external network endpoint in tripleo

You need to have SSL/TLS configured in order to use public endpoint on the undercloud. Change generate_service_certificate = True and then do openstack undercloud upgrade. If unable to upgrade, re-install the undercloud.

2018-09-06 07:23:53 -0600 commented answer issue with tripleo

Did you change anything under the default template directory? And did you pass any customized roles/services files to openstack overcloud deploy ?

2018-09-06 07:20:23 -0600 commented answer issue with tripleo

At this stage, I'd check heat*, mistral, neutron, and nova folders in /var/log/ for clues. A misconfigured network could trigger seemingly irrelevant errors, as it happened to me before.

2018-09-06 07:09:42 -0600 commented answer issue with tripleo

If you use fixed IPs on overcloud nodes, then yes, you need to include your test-net.yaml file. Just make sure you've changed the template path to an absolute one, as mentioned in the "answer" section.

2018-09-05 17:19:02 -0600 commented answer issue with tripleo

I cannot get the format worked properly here. Please have a look at: http://paste.openstack.org/show/729571/.