Project

General

Profile

Feature #2377

.deb: package osmo-bts-virtual separately

Added by msuraev over 1 year ago. Updated 7 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
07/19/2017
Due date:
% Done:

100%

Spec Reference:

Description

Right now osmo-bts-virtual is packages into the same .deb as osmo-bts-trx. Those 2 are unrelated so we should have 2 (non-conflicting) .deb packages produced instead.

History

#1 Updated by msuraev over 1 year ago

Note: we should also make and install .service for it to make sure that it's functional out of the box.

#2 Updated by laforge about 1 year ago

On Fri, Jul 21, 2017 at 03:22:11PM +0000, msuraev [REDMINE] wrote:

Note: we should also make and install .service for it to make sure that it's functional out of the box.

I'm not entirely sure this is what you want for osmo-bts-virtual.

For a physical BTS, of course it is likely that you will want to start
a single instance of the program at system boot time. But for a virtual BTS,
I think the use case is almost always some kind of testing, and you don't
know when the user wants to do that, and how many instances with which configuration
to start.

So if at all, you would probably want to have something similar to the openvpn@
integration, so you could have an entire series of configuration files in some
directory, causing a series of osmo-bts-virtual instances to be started, each with their
own config file - and of course not enable them by default but wait for the user
to decide when he wants to start his BTSs.

#3 Updated by laforge 8 months ago

  • Assignee set to lynxis

#4 Updated by laforge 7 months ago

  • Status changed from New to Resolved
  • Assignee changed from lynxis to laforge
  • % Done changed from 0 to 100

Fixed on March 17 in
Change-Id: I1c88ed2f7111a6c061ac5721af8f09d9aca4a156

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)