Ask Your Question

bel var's profile - activity

2019-05-13 04:55:00 -0500 answered a question openstack-ansible Rocky heat ERROR: Internal Error

after some investigation i found that heat request the keystone via https :

I edit heat.conf from:

[clients_keystone] insecure = False

to : [clients_keystone] insecure = True

this is solve issue

2019-05-03 08:50:36 -0500 received badge  Student (source)
2019-04-17 02:04:17 -0500 received badge  Notable Question (source)
2019-04-15 13:58:50 -0500 received badge  Popular Question (source)
2019-04-15 08:54:06 -0500 commented answer Is ceilometer project is deprecated ?

Thank you,

2019-04-15 07:51:31 -0500 received badge  Scholar (source)
2019-04-15 05:48:49 -0500 commented answer Is ceilometer project is deprecated ?

@bernd-bausch So there is no endpoint for ceilomter as the above error message is normal, is it right?

2019-04-15 04:45:15 -0500 asked a question Is ceilometer project is deprecated ?

I have follow openstack ansible production example from below link :

https://docs.openstack.org/openstack-ansible/stein/user/prod/example.html (https://docs.openstack.org/openstack-...)

but when i try to test ceilometer commands it gave me below messages :

root@infra2-utility-container-d14558a5:~#ceilometer capabilities** /openstack/venvs/utility-18.1.5/local/lib/python2.7/site-packages/ceilometerclient/shell.py:177: UserWarning: ceilometerclient is now deprecated as the Ceilometer API has been deprecated. Please use either aodhclient, pankoclient or gnocchiclient. "ceilometerclient is now deprecated as the Ceilometer API has " internalURL endpoint for metering service in RegionOne region not found

so please any hint to recover this issue

2019-04-15 03:05:42 -0500 received badge  Editor (source)
2019-02-03 12:47:14 -0500 received badge  Famous Question (source)
2019-01-23 07:32:26 -0500 answered a question LinuxBridge vs. OVS

I have test the two methods and I found the ovs is more comfort if you need to make any further changes on your network after the installation as example in mapping physical networks with bridges or interfaces is more easier on OVS than linux-bridge cause you will map in neutron config with OVS bridge "virtual bridge" so that you can do any changes with this bridge and the physical interfaces without the neutron config takes any change

2019-01-21 05:45:56 -0500 commented answer how to use br-vlan veth pair ? what is the benefit of veth?

I am asking cause i try flat and vlan networks on different physnet with different physical interface without the veth pair and i haven't any problem. Also i try it with br-vlan without veth pair and there is no problem so is there any hint we can try to test this veth pair

2019-01-20 10:09:31 -0500 received badge  Notable Question (source)
2019-01-19 17:04:18 -0500 received badge  Popular Question (source)
2019-01-12 04:25:47 -0500 asked a question how to use br-vlan veth pair ? what is the benefit of veth?

Hello

I have installed openstack via ansible but i cannot find the benefit of veth pair which created in compute host interfaces' file as mentioned in official document : https://docs.openstack.org/openstack-ansible/rocky/user/prod/example.html (https://docs.openstack.org/openstack-...)

# For tenant vlan support, create a veth pair to be used when the neutron
# agent is not containerized on the compute hosts. 'eth12' is the value used on
# the host_bind_override parameter of the br-vlan network section of the
# openstack_user_config example file. The veth peer name must match the value
# specified on the host_bind_override parameter.
#
# When the neutron agent is containerized it will use the container_interface
# value of the br-vlan network, which is also the same 'eth12' value.
#
# Create veth pair, do not abort if already exists
#    pre-up ip link add br-vlan-veth type veth peer name eth12 || true
# Set both ends UP
#    pre-up ip link set br-vlan-veth up
#    pre-up ip link set eth12 up
# Delete veth pair on DOWN
#    post-down ip link del br-vlan-veth || true
#    bridge_ports bond1 br-vlan-veth

can anyone please explain more or give me some example cause in my first time i made my tests using that bridge "br-vlan" without creating the veth pair

2018-12-17 07:36:59 -0500 commented answer Singelnode - "No valid host was found"

yes there is a bug reported but still no answer https://bugs.launchpad.net/nova/+bug/1787846 (https://bugs.launchpad.net/nova/+bug/...)

2018-11-21 16:16:03 -0500 commented question instance take different dhcp IP and different gateway than allocation-pool and subnet gateway

thank you @bernd-bausch it seems there is another DHCP in system same my test range for bad chance

2018-11-19 08:07:08 -0500 asked a question instance take different dhcp IP and different gateway than allocation-pool and subnet gateway

I have problem in getting right dhcp ip from network to my instance as i think it is a bug :

I have deployed this version of openstack :

git clone -b 17.1.3 https://git.openstack.org/openstack/openstack-ansible (https://git.openstack.org/openstack/o...) /opt/openstack-ansible

then create this network :

root@r2s11:~# openstack network show c460fde9-fe0b-45b3-9b2f-3271fe98d3f3 +---------------------------+--------------------------------------+ | Field | Value | +---------------------------+--------------------------------------+ | admin_state_up | UP | | availability_zone_hints | | | availability_zones | nova | | created_at | 2018-11-19T07:40:19Z | | description | | | dns_domain | None | | id | c460fde9-fe0b-45b3-9b2f-3271fe98d3f3 | | ipv4_address_scope | None | | ipv6_address_scope | None | | is_default | False | | is_vlan_transparent | None | | mtu | 1500 | | name | provider1 | | port_security_enabled | True | | project_id | 86596157827a42ce8b6623f0be6a67ea | | provider:network_type | flat | | provider:physical_network | physnet1 | | provider:segmentation_id | None | | qos_policy_id | None | | revision_number | 6 | | router:external | External | | segments | None | | shared | True | | status | ACTIVE | | subnets | c87a9de4-1e2a-459c-a84f-9212615b04e6 | | tags | | | updated_at | 2018-11-19T07:41:21Z | +---------------------------+--------------------------------------+

root@r2s11:~# openstack subnet show c87a9de4-1e2a-459c-a84f-9212615b04e6 +-------------------+--------------------------------------+ | Field | Value | +-------------------+--------------------------------------+ | allocation_pools | 172.1.1.50-172.1.1.100 | | cidr | 172.1.1.0/24 | | created_at | 2018-11-19T07:41:21Z | | description | | | dns_nameservers | 8.8.4.4 | | enable_dhcp | True | | gateway_ip | 172.1.1.8 | | host_routes | | | id | c87a9de4-1e2a-459c-a84f-9212615b04e6 | | ip_version | 4 | | ipv6_address_mode | None | | ipv6_ra_mode | None | | name | provider1-v4 | | network_id | c460fde9-fe0b-45b3-9b2f-3271fe98d3f3 | | project_id | 86596157827a42ce8b6623f0be6a67ea | | revision_number | 0 | | segment_id | None | | service_types | | | subnetpool_id | None | | tags | | | updated_at | 2018-11-19T07:41:21Z | +-------------------+--------------------------------------+

root@r2s11:~# openstack server show 6cc0f830-6031-4a82-bda7-703a6b8e3a75 +-------------------------------------+----------------------------------------------------------+ | Field | Value | +-------------------------------------+----------------------------------------------------------+ | OS-DCF:diskConfig | MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | r2s11 | | OS-EXT-SRV-ATTR:hypervisor_hostname | r2s11 | | OS-EXT-SRV-ATTR:instance_name | instance-00000003 | | OS-EXT-STS:power_state | Running | | OS-EXT-STS:task_state | None | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2018-11-19T07:48:14.000000 | | OS-SRV-USG:terminated_at | None | | accessIPv4 | | | accessIPv6 | | | addresses | provider1=172.1.1.60 | | config_drive | | | created | 2018-11-19T07:48:03Z | | flavor | minif (91b149e7-d2e8-421a-9504-a65ff0fd4dfe) | | hostId | 87b51fccb0b3b94c2f6cd1eb52f0117252ba1a33531ba0a01c938361 | | id | 6cc0f830-6031-4a82-bda7-703a6b8e3a75 | | image | testimage (22b43685-4de5-4da4-86cb-137b723adab6) | | key_name | None | | name | myCirrosServer | | progress | 0 | | project_id | 86596157827a42ce8b6623f0be6a67ea | | properties | | | security_groups | name='default' | | status | ACTIVE | | updated | 2018-11-19T07:48:15Z | | user_id | 35d61eebe5a54b31b6c1f6c2d1242d16 | | volumes_attached | | +-------------------------------------+----------------------------------------------------------+

but the instance get ip 172.1.1.243 with gateway 172.1.1.1 while in horizon GUI its ip is 172.1.1.60

So please any help please.

Thank you

2018-11-19 08:07:08 -0500 asked a question instance take different dhcp IP and gateway than allocation-pool and subnet gateway

I have problem in getting right dhcp ip from network to my instance as i think it is a bug :

I have deployed this version of openstack :

git clone -b 17.1.3 https://git.openstack.org/openstack/openstack-ansible (https://git.openstack.org/openstack/o...) /opt/openstack-ansible

then create this network :

root@r2s11:~# openstack network show c460fde9-fe0b-45b3-9b2f-3271fe98d3f3 +---------------------------+--------------------------------------+ | Field | Value | +---------------------------+--------------------------------------+ | admin_state_up | UP | | availability_zone_hints | | | availability_zones | nova | | created_at | 2018-11-19T07:40:19Z | | description | | | dns_domain | None | | id | c460fde9-fe0b-45b3-9b2f-3271fe98d3f3 | | ipv4_address_scope | None | | ipv6_address_scope | None | | is_default | False | | is_vlan_transparent | None | | mtu | 1500 | | name | provider1 | | port_security_enabled | True | | project_id | 86596157827a42ce8b6623f0be6a67ea | | provider:network_type | flat | | provider:physical_network | physnet1 | | provider:segmentation_id | None | | qos_policy_id | None | | revision_number | 6 | | router:external | External | | segments | None | | shared | True | | status | ACTIVE | | subnets | c87a9de4-1e2a-459c-a84f-9212615b04e6 | | tags | | | updated_at | 2018-11-19T07:41:21Z | +---------------------------+--------------------------------------+

root@r2s11:~# openstack subnet show c87a9de4-1e2a-459c-a84f-9212615b04e6 +-------------------+--------------------------------------+ | Field | Value | +-------------------+--------------------------------------+ | allocation_pools | 172.1.1.50-172.1.1.100 | | cidr | 172.1.1.0/24 | | created_at | 2018-11-19T07:41:21Z | | description | | | dns_nameservers | 8.8.4.4 | | enable_dhcp | True | | gateway_ip | 172.1.1.8 | | host_routes | | | id | c87a9de4-1e2a-459c-a84f-9212615b04e6 | | ip_version | 4 | | ipv6_address_mode | None | | ipv6_ra_mode | None | | name | provider1-v4 | | network_id | c460fde9-fe0b-45b3-9b2f-3271fe98d3f3 | | project_id | 86596157827a42ce8b6623f0be6a67ea | | revision_number | 0 | | segment_id | None | | service_types | | | subnetpool_id | None | | tags | | | updated_at | 2018-11-19T07:41:21Z | +-------------------+--------------------------------------+

root@r2s11:~# openstack server show 6cc0f830-6031-4a82-bda7-703a6b8e3a75 +-------------------------------------+----------------------------------------------------------+ | Field | Value | +-------------------------------------+----------------------------------------------------------+ | OS-DCF:diskConfig | MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | r2s11 | | OS-EXT-SRV-ATTR:hypervisor_hostname | r2s11 | | OS-EXT-SRV-ATTR:instance_name | instance-00000003 | | OS-EXT-STS:power_state | Running | | OS-EXT-STS:task_state | None | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2018-11-19T07:48:14.000000 | | OS-SRV-USG:terminated_at | None | | accessIPv4 | | | accessIPv6 | | | addresses | provider1=172.1.1.60 | | config_drive | | | created | 2018-11-19T07:48:03Z | | flavor | minif (91b149e7-d2e8-421a-9504-a65ff0fd4dfe) | | hostId | 87b51fccb0b3b94c2f6cd1eb52f0117252ba1a33531ba0a01c938361 | | id | 6cc0f830-6031-4a82-bda7-703a6b8e3a75 | | image | testimage (22b43685-4de5-4da4-86cb-137b723adab6) | | key_name | None | | name | myCirrosServer | | progress | 0 | | project_id | 86596157827a42ce8b6623f0be6a67ea | | properties | | | security_groups | name='default' | | status | ACTIVE | | updated | 2018-11-19T07:48:15Z | | user_id | 35d61eebe5a54b31b6c1f6c2d1242d16 | | volumes_attached | | +-------------------------------------+----------------------------------------------------------+

but the instance get ip 172.1.1.243 with gateway 172.1.1.1

So please any help please.

Thank you