[MB-7398] [2.0.2 RN + Manual?]Host name and IP address management in Couchbase Created: 12/Dec/12 Updated: 17/Jun/13 Resolved: 10/Apr/13
|Component/s:||documentation, ns_server, tools|
|Affects Version/s:||2.0, 2.0.1|
|Labels:||2.0.2-release-notes, PM-PRIORITIZED, customer|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
- Need ability to use host names that don't revert to IPs
- Need ability to non-disruptively change the IP address of nodes
- When setting up hostname based cluster(using etc/hosts), nodes revert back to ip when a new node is added by Hostname.
Decided to change address to "<IP>"
1.) Install 2.0 GA
2.) Stop couchbase-server
3.) Add ns_name to couchbase-server
4.) remove files per:http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-bestpractice-cloud-ip.html
5.) add hostname to /opt/couchbase/var/lib/couchbase/ip
6.) Start server and configure with beer-sample
7.) Hostname shows up correctly
8.) Add new node by hostname(no need to rebalance)
|Comment by Dipti Borkar [ 05/Feb/13 ]|
|Comment by Dipti Borkar [ 06/Feb/13 ]|
see also MB-4974|
|Comment by Maria McDuff [ 27/Mar/13 ]|
|upgrading to blocker for 2.0.2 release.|
|Comment by Simon Pai [ 30/Mar/13 ]|
|I really hope we can have this fixed sooner. It's blocking so many local dev environments. The best practice guide never worked for me.|
|Comment by Maria McDuff [ 02/Apr/13 ]|
|per bug scrub. alk to merge pretty soon.|
|Comment by Perry Krug [ 02/Apr/13 ]|
|Can we make sure there is a plan for the proper tooling and documentation around this as well? The couchbase-cli will have to be updated to support this option and documentation for the couchbase-cli, the UI and the REST API should be added to the manual for 2.0.2|
|Comment by Aleksey Kondratenko [ 05/Apr/13 ]|
|Comment by Perry Krug [ 08/Apr/13 ]|
Reopening as we need to either use this bug or create new ones for:
-Documentation updates: UI, CLI, REST API and also the deprecation of our "in the cloud" documentation along with a specific section on what this new capability is for.
-Tooling as the CLI will need to provide away of performing this as well
|Comment by Anil Kumar [ 10/Apr/13 ]|
Closing this bug since we've separate bug |
|Comment by Maria McDuff [ 10/Apr/13 ]|
|Deep, pls verify in 2.0.2. it is already merged.|
|Comment by Maria McDuff [ 10/Apr/13 ]|
|Need to be verified by QE. Deep is assigned.|
|Comment by kzeller [ 12/Apr/13 ]|
Input via email:|
Fwding you information from Aliaksey on the recent changes.
Will add notes on the ticket, once tested and verified.
Begin forwarded message:
From: Aliaksey <firstname.lastname@example.org>
Subject: Re: Ref: Need more information -
Date: April 11, 2013 10:11:51 AM PDT
To: Ketaki Gangal <Ketaki@couchbase.com>
Cc: Deepkaran Salooja <email@example.com>
2.0.0 way is _forbidden_ since 2.0.1. I don't know if that's documented or not but it must be.
2.0.1 instructions are actually compatible with new code. But manual change of address is not recommended anymore.
On Wed, Apr 10, 2013 at 7:28 PM, Ketaki Gangal <Ketaki@couchbase.com> wrote:
For testing changes from
Does this also mean, the older way http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-bestpractice-cloud-ip.html is/not valid anymore?
Could you confirm?
On Apr 10, 2013, at 6:50 PM, Deepkaran Salooja wrote:
For the changes done related to
And also need to find out if our earlier mechanism of hostname configuration is still valid:
|Comment by Deepkaran Salooja [ 16/Apr/13 ]|
Following CBQE tasks have been created to verify this change:|
|Comment by Maria McDuff [ 18/Apr/13 ]|
Deep -- |
Scenarios to confirm:
AWS: After upgrade, verify that the host is reachable by hostname (DNS resolution) even if private IP in amazon changed
AWS: After restart of instance, verify same as above.
|Comment by Dipti Borkar [ 22/Apr/13 ]|
Needs to go into the new behavior section of the release notes. |
|Comment by Maria McDuff [ 10/Jun/13 ]|
Shashank has tested this feature. The test cases for EC2 were executed and the status for those are updated in the test plan:|
A couple of points to note here are:
- The private IP of EC2 instances don't get changed on reboot. So that particular case couldn't be verified. However, after reboot couchbase works fine in EC2(with hostnames). [Test 22,23]
- On stopping/starting an instance, both hostname/ip change and the already installed couchbase server stops working. This looks ok to me. [Test 46,47]
Shashank was talking to Ketaki on this. If we want to test changing the IP while hostname remains the same or vice-versa, we'll need ITs help to setup something special internally for this.