Project

General

Profile

Feature #6840

publish a foreman live-cd

Added by Ohad Levy about 8 years ago. Updated about 4 years ago.

Status:
Ready For Testing
Priority:
Normal
Category:
Packaging
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

as a user, I would like to quickly deploy foreman using a live cd


Related issues

Related to Installer - Feature #7464: add network awarenessNew

History

#1 Updated by Dominic Cleal about 8 years ago

  • Category set to Packaging

#2 Updated by Ohad Levy about 8 years ago

  • Legacy Backlogs Release (now unused) set to 10

#3 Updated by Ohad Levy about 8 years ago

  • Target version set to 1.7.5

#4 Updated by Dominic Cleal about 8 years ago

  • Legacy Backlogs Release (now unused) deleted (10)

#5 Updated by Dmitri Dolguikh almost 8 years ago

  • Target version changed from 1.7.5 to 1.7.4

#6 Updated by Ohad Levy almost 8 years ago

  • Target version changed from 1.7.4 to 1.7.3

#7 Updated by Ohad Levy almost 8 years ago

#8 Updated by Dominic Cleal almost 8 years ago

  • Target version changed from 1.7.3 to 1.7.2

#9 Updated by Lukas Zapletal almost 8 years ago

  • Assignee set to Lukas Zapletal

#10 Updated by Lukas Zapletal almost 8 years ago

So we discussed this with Marek and it looks like LiveCD without staypuft bits is not much useful today. So I will go ahead, test the build and create a jenkins job to create the ISO on our infrastructure. This would be first step.

We need staypuft bits because otherwise LiveCD would be without any post-configuration which would only lead to some kind of libvirt-only environment with all the network preconfigured.

What we could do would be to remove OpenStack bits from the kickstart, preferably making the ks file an ERB template so we can preprocess it before evaluation. This way we could have a nice Foreman + Staypuft installer iso with Staypuft on-live network post-setup but without OpenStack things.

Ohad what you think?

#11 Updated by Marek Hulán almost 8 years ago

I agree that just creating jenkins job that builds foreman+staypuft is a good start. After we finish #7464 we can create pure foreman variant.

#12 Updated by Lukas Zapletal almost 8 years ago

  • Status changed from New to Assigned

Ok running one test run and will move this to Jenkins once it works. As a next step, we could modularize the KS file a bit, maybe using a ERB templating:

- centos 6 vs 7 support (vs upstream RHEL support)
- xwindow vs non-xwindow version

#13 Updated by Lukas Zapletal almost 8 years ago

  • Status changed from Assigned to Ready For Testing

https://github.com/theforeman/foreman-live/pull/13

http://ci.theforeman.org/job/packaging_foreman_livecd/

There are some bugs in the image, I will work with Marek to resolve them. Currently its unmodified Staypuft.

#14 Updated by Tomer Brisker about 4 years ago

  • Target version deleted (1.7.2)

Also available in: Atom PDF