Ask Your Question

fattony666's profile - activity

2018-12-22 08:59:05 -0600 received badge  Famous Question (source)
2018-09-05 09:09:17 -0600 commented answer How to connect VMs to network with "real" DHCP?

@Viktor Schlaffer can this be achieved with a 2nd flat network on a dedicated network interface? I would like to use an external DHCP provider for my 2nd provider network

2018-09-05 09:09:17 -0600 received badge  Commentator
2018-09-05 08:58:46 -0600 commented question What are the steps to use an external dhcp server with vlan or flat provider?

would be interested as well. I have an OpenStack installation with a configured VLAN, and the DHCP IP address should be assigned by an external IP provider and from any OpenStack allocation pool configured for this particular network...

2018-09-05 08:56:23 -0600 received badge  Supporter (source)
2018-09-05 07:23:02 -0600 commented answer External network only works for routers

have the same issue here, would need to know how to access / ping the external hosted VMs from within. I would like to create a network that spans the outside as well as inside of openstack and is managed by an external DHCP provider (checkpoint).

2018-09-05 07:12:36 -0600 commented question Nova shows different IP than given by external DHCP server

hi, did you already had the chance to implement this? I'm currently stuck at the same issue, where I would need to configure and enable an external DHCP server to provide IP addresses to my 2nd provider network

2018-09-05 06:44:41 -0600 commented question provide ip to anopenstack vm via external dhcp

@Bernd Bausch: It basically looks like this: 1x provider network (flat) on eth1, 1x mgmt ntw on eth2 and 1x "vlan1" (the vlan network that we would like to use) on eth3. Disabling the DHCP provider within openstack for vlan1 and enabling it on the physical switch should do the trick?

2018-09-05 06:07:59 -0600 commented question network provider how to add dhcp options

Hi, where you able to change this? I'm looking as well to be able to use an external DHCP provider to distinguish between already assgined IP addresses and new ones...

2018-09-05 03:54:22 -0600 commented question How instance obtain ip from external dhcp server

Hi! Where you able to resolve this issue already? If yes, how did you do it?

2018-09-05 03:42:29 -0600 commented question provide ip to anopenstack vm via external dhcp

@Bernd Bausch: Does this apply to VLAN networks as well? we confiugred 1x Vlan network which is mapped to our OpenStack controller / compute nodes and we would like to manage the DHCP IP allocation from the external physical router. OpenStack creates an IP address pool too, which is not needed

2018-09-03 03:42:55 -0600 answered a question Cinder volume on SAN immediately removed

Hi Vinoth, please see below our cinder.conf:

[DEFAULT]
rootwrap_config = /etc/cinder/rootwrap.conf
api_paste_confg = /etc/cinder/api-paste.ini
#iscsi_helper = tgtadm
volume_name_template = volume-%s
#volume_group = cinder-volumes
verbose = True
auth_strategy = keystone
state_path = /var/lib/cinder
lock_path = /var/lock/cinder
volumes_dir = /var/lib/cinder/volumes
transport_url = rabbit://openstack:rabbitMQ@hrzgf01r01controller01
my_ip = 172.16.250.4
enabled_backends = hrzgf01svc01
glance_api_servers = http://hrzgf01r01controller01:9292
zoning_mode = fabric

[database]
connection = mysql+pymysql://cinder:rabbitMQ@hrzgf01r01controller01/cinder

[keystone_authtoken]
auth_uri = http://hrzgf01r01controller01:5000
auth_url = http://hrzgf01r01controller01:5000
memcached_servers = hrzgf01r01controller01:11211
auth_type = password
project_domain_id = default
user_domain_id = default
project_name = service
username = cinder
password = password

[oslo_concurrency]
lock_path = /var/lib/cinder/tmp

[hrzgf01svc01]
volume_driver = cinder.volume.drivers.ibm.storwize_svc.storwize_svc_fc.StorwizeSVCFCDriver
volume_backend_name = hrzgf01svc01
san_ip = 192.168.0.50
san_login = openstackadmin
san_password = password
storwize_svc_volpool_name = hrzgf01storagepool01
capabilities:storage_protocol='<in> FC'


[fc-zone-manager]

#
# From cinder
#

# South bound connector for zoning operation (string value)
brcd_sb_connector = HTTP

# Southbound connector for zoning operation (string value)
#cisco_sb_connector = cinder.zonemanager.drivers.cisco.cisco_fc_zone_client_cli.CiscoFCZoneClientCLI

# FC Zone Driver responsible for zone management (string value)
zone_driver = cinder.zonemanager.drivers.brocade.brcd_fc_zone_driver.BrcdFCZoneDriver

# Zoning policy configured by user; valid values include "initiator-target" or
# "initiator" (string value)
zoning_policy = initiator

# Comma separated list of Fibre Channel fabric names. This list of names is
# used to retrieve other SAN credentials for connecting to each SAN fabric
# (string value)
fc_fabric_names = fabric01,fabric02

# FC SAN Lookup Service (string value)
fc_san_lookup_service = cinder.zonemanager.drivers.brocade.brcd_fc_san_lookup_service.BrcdFCSanLookupService

# Set this to True when you want to allow an unsupported zone manager driver to
# start. Drivers that haven't maintained a working CI system and testing are
# marked as unsupported until CI is working again. This also marks a driver as
# deprecated and may be removed in the next release. (boolean value)
#enable_unsupported_driver = false


[fabric01]

# EMC switches

# From cinder
#

# South bound connector for the fabric. (string value)
# Possible values:
# SSH - <no description="" provided="">
# HTTP - <no description="" provided="">
# HTTPS - <no description="" provided="">
fc_southbound_protocol = HTTP

# Management IP of fabric. (string value)
fc_fabric_address = 192.168.0.30

# Fabric user ID. (string value)
fc_fabric_user = cinder

# Password for user. (string value)
fc_fabric_password = password

# Connecting port (port value)
# Minimum value: 0
# Maximum value: 65535
fc_fabric_port = 22

# Local SSH certificate Path. (string value)
#fc_fabric_ssh_cert_path =

# Overridden zoning policy. (string value)
zoning_policy = initiator-target

# Overridden zoning activation state. (boolean value)
zone_activate = true

# Overridden zone name prefix. (string value)
zone_name_prefix = openstack_

# Virtual Fabric ID. (string value)
#fc_virtual_fabric_id = <none>


[fabric02]

# Brocade switches

# From cinder
#

# South bound connector for the fabric. (string value)
# Possible values:
# SSH - <no description="" provided="">
# HTTP - <no description="" provided="">
# HTTPS - <no description="" provided="">
fc_southbound_protocol = HTTP

# Management IP of fabric. (string value)
fc_fabric_address = 192.168.0.28

# Fabric user ID. (string value)
fc_fabric_user = cinder

# Password for user. (string value)
fc_fabric_password = password

# Connecting port (port value)
# Minimum value: 0
# Maximum value: 65535
fc_fabric_port = 22

# Local SSH certificate Path. (string value)
#fc_fabric_ssh_cert_path =

# Overridden zoning policy. (string value)
zoning_policy = initiator-target

# Overridden zoning activation state. (boolean value)
zone_activate = true

# Overridden zone name prefix. (string value)
zone_name_prefix = openstack_

# Virtual Fabric ID. (string value)
#fc_virtual_fabric_id = <none>

// EDIT: As we are using a IBM storage system, it looks like the ... (more)

2018-09-03 03:08:47 -0600 received badge  Notable Question (source)
2018-09-01 01:32:54 -0600 received badge  Popular Question (source)
2018-08-31 07:57:08 -0600 received badge  Editor (source)
2018-08-31 07:56:39 -0600 asked a question Cinder volume on SAN immediately removed

Hi all,

We are running OpenStack Queens on Ubuntu 16.04 LTS and are using IBM DS4700 as external storage. To manage the storage, we have Brocade Network Advisor 14.3.1 and the Brocade Fibre Channel Zoning plugin setup and creating volumes on the external storage. That works.

However cinder-volume is not able to create the correct target-initiator zones, therefore the instances are not able to use created volumes.

The volume get created, the instances are getting created, but the zoning information is created and immediately removed by cinder again.

Please see below:

2018-08-31 14:39:23.620 4235 INFO cinder.zonemanager.drivers.brocade.brcd_fc_zone_driver [req-6d52f55c-006d-43c0-b32e-59b9a32f0d2f 8f6e2e71596f4e67bd02121a9f3ff3f5 3be8c468652748398997fd6b11188814 - default default] Zone map to create: {'openstack_21000024ff0466a4500507680c111a9a': ['21:00:00:24:ff:04:66:a4', '50:05:07:68:0c:11:1a:9a'], 'openstack_21000024ff0466a4500507680c111a92': ['21:00:00:24:ff:04:66:a4', '50:05:07:68:0c:11:1a:92']}
2018-08-31 14:39:23.620 4235 INFO cinder.zonemanager.drivers.brocade.brcd_fc_zone_driver [req-6d52f55c-006d-43c0-b32e-59b9a32f0d2f 8f6e2e71596f4e67bd02121a9f3ff3f5 3be8c468652748398997fd6b11188814 - default default] Zone map to update: {}
2018-08-31 14:39:29.776 4235 INFO cinder.zonemanager.fc_zone_manager [req-6d52f55c-006d-43c0-b32e-59b9a32f0d2f 8f6e2e71596f4e67bd02121a9f3ff3f5 3be8c468652748398997fd6b11188814 - default default] Add connection: finished iterating over all target list
2018-08-31 14:39:29.947 4235 INFO cinder.volume.manager [req-6d52f55c-006d-43c0-b32e-59b9a32f0d2f 8f6e2e71596f4e67bd02121a9f3ff3f5 3be8c468652748398997fd6b11188814 - default default] attachment_update completed successfully.
2018-08-31 14:39:41.092 4235 INFO cinder.volume.drivers.ibm.storwize_svc.storwize_svc_fc [req-73c6e79a-fbdf-4718-b421-d2b3fd491655 8f6e2e71596f4e67bd02121a9f3ff3f5 3be8c468652748398997fd6b11188814 - default default] Need to remove FC Zone, building initiator target map.
2018-08-31 14:39:41.337 4235 INFO cinder.zonemanager.utils [req-73c6e79a-fbdf-4718-b421-d2b3fd491655 8f6e2e71596f4e67bd02121a9f3ff3f5 3be8c468652748398997fd6b11188814 - default default] Using FC Zone Manager 1.0.2, Driver BrcdFCZoneDriver 1.5.
2018-08-31 14:39:41.338 4235 INFO cinder.zonemanager.fc_zone_manager [req-73c6e79a-fbdf-4718-b421-d2b3fd491655 8f6e2e71596f4e67bd02121a9f3ff3f5 3be8c468652748398997fd6b11188814 - default default] Delete connection target list: [u'500507680C211A92', u'50

Cinder creates the volume and the zoning information and then removes it immediately again with the message: "Need to remove FC Zone, building initiator target map."

We do not know why this message occures, any help appricated.

Thank you

2018-04-19 02:04:57 -0600 answered a question recover windows admin password

Hello,

To retrieve the password without access to the Horizon dashboard option or without access over the CLI seems quite impossible to me.

The following link provides details about how to retrieve the passwording using the dashboard and nova: https://cloudbase.it/openstack-windows-admin-password/ (Cloudbase.it)

2018-04-14 20:31:04 -0600 answered a question cinder-volume CappedVersionUnknown

Issue is still in place on OpenStack Queens version, running Ubuntu 16.04

I applied the same steps as mentioned above to remove the issues. Applied the steps on controller & storage node separately.

2018-04-14 20:30:58 -0600 commented answer VolumeNotCreated: Volume did not finish being created even after we waited 197 seconds or 61 attempts

Thanks, helped me further as well. Increased the same setting to allocate volumes faster on our attached SAN storage

2018-04-14 20:30:57 -0600 answered a question Problem attaching volume: Connector doesn't have required information: wwpns

Hi,

We have OpenStack Queens running on Ubuntu 16.04 LTS and run into the same issue. Fixied it by installing missing system libraries "sysfsutils".

See following Red Hat blog: https://access.redhat.com/solutions/969433 (OpenStack Cinder volume is unable to attach to a VM instance)

Hope this helps you further!

2018-04-14 20:30:53 -0600 commented answer Connecting Cinder node to EMC SAN

Hi Paul,

Can you please share your cinder.conf file if still possible?

I am trying to connect my Cinder / compute node to Brocade / IBM SAN, but OpenStack is somehow not able to create a volume on the FC storage.

Thank you.

2018-04-12 01:12:08 -0600 received badge  Enthusiast