Configuring LDAP on ReviewBaord

If you are looking at this post, you would have already installed reviewboard and are facing issues configuring LDAP on it.

For others who landed here by chance:

Review Board is a powerful web-based code review tool that offers developers an easy way to handle code reviews. It scales well from small projects to large companies and offers a variety of tools to take much of the stress and time out of the code review process.

You can checkout reviewboard @ http://www.reviewboard.org/

Now comming to the topic, reviewboard asks for the following LDAP settings:

LDAP Server : ldap://<your server ip>:389 (By convention this can be : ldap://ldap.<your company name>.<com|net|org>:389)

LDAP Base DN (Used to perform LDAP searches) : Should generally be composed of OU & DC. For ex:- OU=users,OU=<US|Canada|AsiaPac|Japan>,OU=<(Engineering|Eng)|(Finance|Fin)),DC=<yourcompanydomain>,DC=<com|net|org>
example1: OU=users,OU=AsiaPac,OU=Eng,DC=GooG,DC=com
example2: OU=users,DC=CSCO,DC=com

User Mask: (sAMAccountName=%s) (This should generally do the trick if not try CN=%s or UID=%S. You can also refer to http://msdn.microsoft.com/en-us/library/windows/desktop/aa746475%28v=vs.85%29.aspx for more information)

If your LDAP server allows anonymous users to query then you can leave
Anonymous User Mask : <blank>
Anonymous User Passwrod: <blank>

if not then you may need to ask your network admin to create a team/group id which can browse LDAP server. But if you want to check if everything is configured well you can use your login credentials here.
Anonymous User Mask : <domain>\<your user name>
Anonymous User Passwrod: <your password>

Acronyms
DN : Distinguished Name
CN : Common Name
DC : Domain Component
SN : Surname
mail : mail

Comments

Openstack : Fixing Failed to create network. No tenant network is available for allocation issue.

Assumptions : You are using ML2 plugin configured to use Vlans If you try to create a network for a tenant and it fails with the following error: Error: Failed to create network "Test": 503-{u'NeutronError': {u'message': u'Unable to create the network. No tenant network is available for allocation.', u'type': u'NoNetworkAvailable', u'detail': u''}} The problem can be due to missing configuration in the below files: In /etc/neutron/plugins/ml2/ml2_conf.ini network_vlan_ranges =physnet1:1000:2999 (1000:2999 is the Vlan range allocation) In /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini bridge_mappings = physnet1:br-eth1 (in OVS we map the physical network to the OVS bridge) Note You should have created a bridge br-eth1 manually and mapped it to a port ovs-vsctl add-br br-eth1 ovs-vsctl add-port br-eth1 eth1 Once configuration is done, restart the neutron ovs agent on the compute node(s):

Solved: Fix for Git clone failure due to GnuTLS recv error (-9)

My devstack installation was failing with an error reported by the GnuTLS module as shown below: $ git clone https://github.com/openstack/horizon.git /opt/stack/horizon --branch master Cloning into '/opt/stack/horizon'... remote: Counting objects: 154213, done. remote: Compressing objects: 100% (11/11), done. error: RPC failed; curl 56 GnuTLS recv error (-9): A TLS packet with unexpected length was received. fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed The following Git config changes fixed the issue for me. Am hoping it will be useful for someone out there: $ git config http.sslVerify false $ git config --global http.postBuffer 1048576000

QuickBite: Tap Vs Veth

Linux supports virtual networking via various artifacts such as: Soft Switches (Linux Bridge, OpenVSwitch) Virtual Network Adapters (tun, tap, veth and a few more) In this blog, we will look at the virtual network adapters tap and veth. From a practical view point, both seem to be having the same functionality and its a bit confusing as to where to use what. A quick definition of tap/veth is as follows: TAP A TAP is a simulated interface which exists only in the kernel and has no physical component associated with it. It can be viewed as a simple Point-to-Point or Ethernet device, which instead of receiving packets from a physical media, receives them from user space program and instead of sending packets via physical media writes them to the user space program. When a user space program (in our case the VM) gets attached to the tap interface it gets hold of a file descriptor, reading from which gives it the data being sent on the tap interface. Writing to the file descri

Clouds, Networking and Technology

Search This Blog