[DCOS_OSS-1402] Upgrade from navstar to dcos-net properly Created: 10/Jul/17  Updated: 09/Nov/18  Resolved: 31/Aug/17

Status: Resolved
Project: DC/OS
Component/s: networking
Affects Version/s: None
Fix Version/s: DC/OS 1.11.0

Type: Task Priority: Medium
Reporter: Sergey Urbanovich (Inactive) Assignee: Sergey Urbanovich (Inactive)
Resolution: Won't Do  
Labels: 1.11
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relates to DCOS_OSS-691 DNS Failover Tests consistently fail ... Resolved
Epic Link: dcos-net
Sprint: Networking Team 1.11 Sprint 3
Story Points: 3


At this moment dcos-net nodes couldn't connect to old navstar nodes and don't have migrations of mnesia databases. It could be a problem for big clusters (100+ servers).

Comment by Deepak Goel [ 13/Jul/17 ]

There are two approaches to fix this issue - 1. Simple but not ideal, 2. Complex but ideal

1. Simple approach - Even though the system unit would be called dcos-net, keep the erlang node name as "navstar"
Pros: 1. smooth upgrade as old and new node would still operate on "navstar"
2. less code less risky
Cons: 1. May cause confusion because system unit name would be different from erlang node name
2. Not ideal due to above reason

2. Complex approach - Change the erlang node name to "dcos-net"
Pros: 1. Clean solution as systemd unit name corresponds to erlang node name
2. less confusion by having just one name across the board
Cons: 1. Need to add code to handle upgrade which involve re-writting mnesia meta data
2. Need to make changes in old code to be able to talk to new node "dcos-net"
3. More code more chances of error

Comment by Deepak Goel [ 13/Jul/17 ]

Sergey Urbanovich Avinash Sridharan Deepak Goel met and decided to go with simple approach and take the complex one in future

Comment by Sergey Urbanovich (Inactive) [ 31/Aug/17 ]

We decided to keep navstar as node name. It's the simplest solution. And almost no one will see this node name.

Generated at Wed May 18 07:07:21 CDT 2022 using JIRA 7.8.4#78004-sha1:5704c55c9196a87d91490cbb295eb482fa3e65cf.