Project

General

Profile

Actions

action #20910

closed

migration support for Leap

Added by lnussel almost 7 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Development
Target version:
-
Start date:
2017-07-31
Due date:
2017-08-31
% Done:

0%

Estimated time:

Description

For easier upgrade between minor Leap versions and also for a potential migration to SLE, Leap should get support for using the same migration mechanism as SLE. So for that we need to be able to optionally connect with SCC to get the repos from there.

  1. figure out how getting repos from SCC works (SUSEConnect puts something in /etc/zypp/services.d AFAIK)
  2. find a way to handle our standard repos is a way compatible with 1). IIRC SCC expects a specific layout of URLs that may not match ours.
  3. check how updating from 42.3 would work, ie removing repos and adding them the way 2) would do.
  4. how to handle installation without registration? we need our default repos there too.
Actions #1

Updated by lnussel almost 7 years ago

  • Description updated (diff)
Actions #2

Updated by lnussel almost 7 years ago

  • Description updated (diff)
Actions #4

Updated by favogt almost 7 years ago

  1. SUSEConnect adds a RIS service with a URL with credentials pointing to SCC. SCC responds with a list of repos to add.
  2. Arbitrary URLs are possible, so anything is fine except for possible restrictions internal to SCC.
  3. Needs to be done by YaST or a openSUSE-release package that removes all Leap repo files within /etc/zypp/repos.d
  4. I'd suggest to always register, just with anonymous data by default. Then zypper will get the repos during the next refresh. Otherwise it's possible to have a package install a local-only service files that points directly to the repos, but that's IMO more complicated than needed.
Actions #5

Updated by favogt almost 7 years ago

For Leap -> SLE migration, which is only officially supported by offline installation currently, only the removal of old repos is required.

Actions #6

Updated by okurz almost 5 years ago

@favogt I think this has actually progressed further if not being actually completed?

Actions #7

Updated by favogt almost 5 years ago

There is a migration to SLE, but I don't know whether migration to different Leap version is possible.

Actions #9

Updated by okurz almost 5 years ago

yes, I have seen the project. Nice idea. However I would suggest to focus this ticket on "Leap should get support for using the same migration mechanism as SLE" as mentioned in the description.

Actions #10

Updated by favogt almost 5 years ago

  • Assignee changed from favogt to lnussel

Reassigning, I don't think there's anything left for me to do

Actions #11

Updated by lnussel over 4 years ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF