Feature #12533

Ability to point vagrant-libvirt to a custom storage pool

Added by vk 2017-05-10 16:11:58 . Updated 2020-01-01 09:12:29 .

Status:
Confirmed
Priority:
Low
Assignee:
Category:
Build system
Target version:
Start date:
2017-05-10
Due date:
% Done:

10%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
1
Affected tool:
Deliverable for:

Description

As discussed in Bug #12507, ability to use non-default Libvirt storage domain could be useful.
It’s as easy as adding something like below to vagrant/Vagrantfile in the config.vm.provider :libvirt section:

domain.storage_pool_name = ENV['TAILS_BUILD_LIBVIRT_POOL'] ? ENV['TAILS_BUILD_LIBVIRT_POOL'] : 'default'

Subtasks

Related issues

Related to Tails - Bug #12507: Vagrant: too little memory allocated for non-RAM builds Rejected 2017-05-04

History

#1 Updated by intrigeri 2017-05-10 16:14:51

  • Target version set to Tails_3.0
  • QA Check set to Ready for QA

I’m the RM for 3.0 so feel free to reassign to me. But the build system is your area so I figured you might want to handle this one :)

#2 Updated by intrigeri 2017-05-25 05:56:40

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

#3 Updated by intrigeri 2017-05-25 05:56:51

  • Subject changed from Ability to point vagrant-libvirt to a custom storage domain to Ability to point vagrant-libvirt to a custom storage pool

#4 Updated by intrigeri 2017-05-25 05:57:10

  • Type of work changed from Sysadmin to Code

#5 Updated by anonym 2017-05-25 12:33:25

  • Assignee changed from anonym to vk
  • QA Check changed from Ready for QA to Dev Needed

Now that the big rework of the build system is merged, there’s a few more instances of “default” that has to be taken care of. Please fix, test and report back when it work both when and without the option set!

And, yeah, an actual .patch (or Git pull request) would be preferred. :)

#6 Updated by intrigeri 2017-06-02 15:56:15

Timing-wise, we’re now very close to the 3.0 release: I’d be happy to review (and possibly merge) a branch submitted by June 6; if this is not plausible, please postpone to next release :)

#7 Updated by intrigeri 2017-06-09 20:20:25

  • Target version changed from Tails_3.0 to Tails_3.2

#8 Updated by anonym 2017-09-28 18:29:37

  • Target version changed from Tails_3.2 to Tails_3.3

#9 Updated by intrigeri 2017-09-29 08:59:42

  • Target version deleted (Tails_3.3)

vk, do you (still) plan to work on this? If so, please set whatever Target version you want. I doubt this will be suitable for a bugfix release so the next candidate would be 3.4.

#10 Updated by Anonymous 2018-01-15 16:36:29

Ping?

#11 Updated by Anonymous 2018-08-17 09:03:49

  • related to Bug #12507: Vagrant: too little memory allocated for non-RAM builds added

#12 Updated by Anonymous 2018-08-17 09:05:05

Are you still interested in working on this? If not, please deassign yourself from this ticket. It will make ticket tracking/triaging easier for us. Thanks.

#13 Updated by intrigeri 2020-01-01 09:12:29

  • Status changed from In Progress to Confirmed
  • Assignee deleted (vk)
  • Priority changed from Normal to Low