#40 support setting ostree urls in kickstarts for image builds
Closed: Dropped 2 years ago by tkopecek. Opened 8 years ago by ausil.

Just like we have to set the url line in a kickstart for image building, if doing a ostree image we need to also set the ostreesetup line also

https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-cloud-atomic.ks#n36 is an example of what the line needs to look like, afaik pykickstart should be able to set the options, if it can't then we will need to file RFE's so it can.


The linked file has been renamed to fedora-atomic.ks.

Pykickstart can modify the ostreesetup line, so there should be no need for any RFEs.

Metadata Update from @mikem:
- Issue tagged with: discussion

5 years ago

Seems like you could just place the ostreesetup line directly in the kickstart that you pass in. I guess the point here is that these urls are changing much faster than the rest of the kickstart, so you want to separate them out. Correct?

Is it just the url part of the line, or are the other parts that need to be separated out to?

@mikem you can only modify the url if you pass in a kickstart, ideally the buildier will clone the kickstart repo from git, update the ostreesetup line and pass it in to the image build. exactly the same as we do for other image builds as part of a compose.

Seems like you could just place the ostreesetup line directly in the kickstart that you pass in. I guess the point here is that these urls are changing much faster than the rest of the kickstart, so you want to separate them out. Correct?

Right. The main reason we want this is that we have several "branches" within an ostree repository and we'd like to be able to switch which branch we embed in the media by just hanging pungi config (which passes the arg to koji). Another reason is that we just started building updates-testing and updates media. We'd like to use the same kickstarts for both and just have the pungi config specify the branch to use.

Is it just the url part of the line, or are the other parts that need to be separated out to?

I think if we do this I'd prefer to be able to specify the entire line so we can have control over it and don't have to come back with subsequent requests. I mentioned in IRC but I don't know if you saw it. We might be able to achieve this goal by having a 'ksappend' argument that just appends a line to a kickstart file. so we could:

ksappend "ostreesetup blah blah"

and that would override the earlier ostreesetup directive in the kickstart file. Not sure if this is an ugly solution or not.

Metadata Update from @yulwang:
- Issue priority set to: Normal
- Issue tagged with: backlog, groomed

4 years ago

Going to drop this one. If you think it is still relevant, please reopen.

Metadata Update from @tkopecek:
- Custom field Size adjusted to None
- Issue close_status updated to: Dropped
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata