Skip to content

Instantly share code, notes, and snippets.

View busterswt's full-sized avatar

James Denton busterswt

  • ArcaneByte
  • San Antonio, TX
View GitHub Profile
Stock:
root@aio1-utility-container-3b5f2e9b:~# neutron --os-project-name TenantA --os-username UserA --os-password secrete port-create --name TestPortManual1 --fixed-ip ip_address=192.168.99.100 MySemiSharedNetwork
(rule:create_port and rule:create_port:fixed_ips) on {'binding:host_id': <neutron_lib.constants.Sentinel object at 0x7faf49f8ec50>, u'name': u'TestPortManual1', 'allowed_address_pairs': <neutron_lib.constants.Sentinel object at 0x7faf49f8ec50>, u'admin_state_up': True, u'network_id': u'4254cb38-41d3-438f-b5e6-cd1a096c3678', 'tenant_id': u'9e650b27cfce4833bbe61c650d5f59cb', 'extra_dhcp_opts': None, 'mac_address': <neutron_lib.constants.Sentinel object at 0x7faf49f8ec50>, 'binding:vnic_type': 'normal', 'device_owner': '', 'device_id': '', 'binding:profile': <neutron_lib.constants.Sentinel object at 0x7faf49f8ec50>, 'port_security_enabled': <neutron_lib.constants.Sentinel object at 0x7faf49f8ec50>, 'project_id': u'9e650b27cfce4833bbe61c650d5f59cb', u'fixed_ips': [{u'ip_address': u'192.168.99.100'}],
@busterswt
busterswt / port
Last active October 30, 2017 19:08
This ticket was created to document an escalation via Slack
The customer requested a new subnet be created to expand an existing network. While testing, they found that the new instance was not getting its IP from DHCP. Further testing found the DHCP ports for the new subnet were all in BUILD state, and DHCP requests were being ignored.
Further inspection showed that tracebacks were observed on a regular basis (every 10-12 seconds) in the neutron-openvswitch-agent.log files on all three controller nodes. Below is a snippet:
2017-10-26 16:24:28.458 4403 INFO neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [req-00e34b5f-346a-4c33-a71b-822fde6e6f46 - - - - -] Port e9c11103-9d10-4b27-b739-e428773d8fac updated. Details: {u'profile': {}, u'network_qos_policy_id': None, u'qos_policy_id': None, u'allowed_address_pairs': [], u'admin_state_up': True, u'network_id': u'e57257d9-f915-4c60-ac30-76b0e2d36378', u'segmentation_id': 2123, u'device_owner': u'network:dhcp', u'physical_network': u'physnet1', u'
network:
version: 2
ethernets:
ens160:
addresses: [10.50.0.9/24]
gateway4: 10.50.0.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
vlans:
ens160.100:
root@controller-01:/home/vagrant# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
[contrail-analyticsdb]
10.50.0.230
10.50.0.229
10.50.0.232
[contrail-controllers]
10.50.0.230
10.50.0.229
10.50.0.232
{
"server": [
{
"id": "cluster1-hp03",
"cluster_id": "cluster1",
"host_name": "cluster1-hp03",
"domain": "contrail.jimmdenton.com",
"mac_address": "2c:59:e5:3b:22:6c",
"ip_address": "10.50.0.230",
"password": "juniper",
root@hp-03:/tmp/contrail# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.2 LTS
Release: 16.04
Codename: xenial
--------
1. Set hostname and update /etc/hosts
{
"server": [
{
"cluster_id": "cluster1",
"domain": "contrail.jimmdenton.com",
"id": "server1",
"parameters" : {
"partition": "/dev/sda",
"provision": {
"contrail_4": {
{
"cluster" : [
{
"id": "cluster1",
"parameters" : {
"domain": "contrail.jimmdenton.com",
"subnet_mask": "255.255.255.0",
"gateway": "10.50.0.1",
"provision": {
"contrail_4": {
{
"image": [
{
"category": "package",
"id": "contrail_4_0_0_0_20",
"path": "/opt/contrail/contrail-cloud-docker_4.0.0.0-20-newton_xenial.tgz",
"type": "contrail-ubuntu-package",
"version": "4.0.0.0-20"
}
]