Commit Graph

33 Commits

Author SHA1 Message Date
Mohan Boddu
90d8dbec76 Rawhide being F30
Signed-off-by: Mohan Boddu <mboddu@bhujji.com>
2018-08-13 13:39:07 -04:00
Dusty Mabe
9fdd766e5d
atomic: move to unified repo structure
We move to /compose/atomic/repo for the compose time repo and to
/atomic/repo for the production/user repo. See [1].

[1] https://lists.fedoraproject.org/archives/list/rel-eng@lists.fedoraproject.org/thread/KLN5L33BIR3ZEHC5RIG4NXGO7LT6HBXJ/

Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
2018-03-03 12:33:47 -05:00
Dusty Mabe
8445c1def0
atomic: use f29 gpgkey for rawhide
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
2018-03-03 12:29:17 -05:00
Dusty Mabe
2779df193d
remove all mentions of *productimg*
They were moved into the anaconda installclasses so those packages
no longer exist.

Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
2018-02-27 10:58:04 -05:00
Dusty Mabe
bb3b98d505
atomic: add comment on why we disable firewall
In cloud Images we do this becaue it's generally accepted that
in a cloud environment there are higher level firewall constructs
(i.e. security groups).
2018-01-12 14:57:47 -05:00
Colin Walters
c66511d4f9 atomic-host: Stop overriding /etc/udev/rules.d/80-net-setup-link.rules
This bit was cargo culted from the old school Fedora Cloud image, but we have
also been using `net.ifnames=0` on the kernel command line, which ensures that
we get `eth0` as "the" NIC name.  (There's a huge amount of history behind
this and I'm not trying to change that behavior here)

The problem is that those udev rules do *other* things that we do want, such as
ensure that `veth` devices get `NM_CONTROLLED=no`. Without that e.g.
NetworkManager might try to do DHCP on those devices, which is at best slow
since they appear and disappear frequently, and at worst risks the host network
configuration.

For more information, see [RH bz#1503347](https://bugzilla.redhat.com/show_bug.cgi?id=1503347)

Signed-off-by: Colin Walters <walters@verbum.org>
2017-10-24 14:48:29 -04:00
Colin Walters
dda92b4f95 atomic-host: Update and clarify comment at the top
For obvious reasons, just trying to keep this updated.

Signed-off-by: Colin Walters <walters@verbum.org>
2017-10-24 14:40:46 -04:00
Colin Walters
8241be7492 atomic-host: Drop writing /etc/sysconfig/firstboot
We don't include firstboot in AH, we use cloud-init, so nothing
is ever going to parse this.  Drop it, since it shows up as a delta
in `ostree admin config-diff`, and further we want to reduce the
amount of stuff in this ks.

Signed-off-by: Colin Walters <walters@verbum.org>
2017-10-24 14:40:46 -04:00
Colin Walters
38dc52cb45 atomic-host: Stop writing /etc/hosts, use setup defaults
The `setup` package has this same content, let's not duplicate it. The only
difference between them today is trailing whitespace in our version.

Just trying to reduce the amount of stuff we do here to avoid deltas with bare
metal installs, containers, etc.

Signed-off-by: Colin Walters <walters@verbum.org>
2017-10-24 14:40:24 -04:00
Sinny Kumari
c656ae6f78 Include console=ttyAMA0 and console=hvc0 in Atomic kickstart
While booting Atomic cloudImage, we want to see kernel messages
on both VGA and serial console. It works fine with
tty1(vga console) and ttyS0(serial console) on x86_64 arch.
But, aarch64 and ppc64le doesn't use ttyS0 as serial console.
Instead, they use ttyAMA0(aarch64) and hvc0 (ppc64le).

Also, good point is that if a serial console specified in kernel
boot parameter is not supported on a given hardware platform, it
gets ignored. For example: console=ttyAMA0 and console=hvc0 will
get ignored on x86_64

Fixes: https://pagure.io/atomic-wg/issue/347

Signed-off-by: Sinny Kumari <sinny@redhat.com>
2017-10-12 12:14:16 +05:30
Dusty Mabe
97b0af5d00
atomic: extend the root filesystem to fill VG
With the change to using overlay in the root filesystem [1]. We
need to configure the cloud images to extend the root filesystem
by default [2]. Fixes [2]

[1] https://pagure.io/atomic-wg/issue/281
[2] https://pagure.io/atomic-wg/issue/343
2017-10-05 16:01:41 -04:00
Dusty Mabe
c3095c82ba
atomic: use basearch in ostreesetup line
This will help enable us to use the same kickstart file for multiple
architectures. Enabling work was in the pull requests listed below:

https://github.com/projectatomic/rpm-ostree/pull/877
https://github.com/rhinstaller/anaconda/pull/1186
2017-09-19 11:47:21 -04:00
Dusty Mabe
09243c1a40
atomic: verify ostree commits by using f28 key 2017-09-19 11:46:26 -04:00
Sinny Kumari
7d2e4519d8 Use reqpart in Fedora Atomic kickstart
Building Fedora Atomic CloudImage on architectures like
aarch64 and ppc64le needs platform specific partitions as well.

Issue - https://pagure.io/atomic-wg/issue/299#comment-449243

Signed-off-by: Sinny Kumari <sinny@redhat.com>
2017-09-14 21:22:49 +05:30
Colin Walters
ca4d6f43e1 atomichost: Update partitioning for new model
See https://pagure.io/atomic-wg/issue/281

This causes us to match the productimg setup. At some point hopefully we can use
`autopart` and not duplicate it.
2017-09-13 13:40:06 -04:00
Dusty Mabe
6b530c0957
atomic: remove temporary workaround for anaconda bug
This reverts commit 295519948b.

Now that the upstream fix [1] has been merged and a new version of
anaconda is in rawhide, we can revert this workaround.

[1] https://github.com/rhinstaller/anaconda/pull/1126
2017-08-10 11:53:23 -04:00
Dusty Mabe
295519948b
atomic: temporary workaround for anaconda bug
see https://pagure.io/atomic-wg/issue/301
2017-07-14 09:44:54 -04:00
Dusty Mabe
467f7dcb3c
atomic: enable gpg verification after install
Taking the first step towards enabling gpg verification for our
users we'll make it so that the media they download will verify
gpg signatures of commits by default.

The next step is to enable gpg verification during install as well
but there is a race condition where the commit that was just created
might not yet be signed. See [1] for more details.

[1] https://pagure.io/pungi/issue/650
2017-06-23 08:46:35 -04:00
Dusty Mabe
d85921a078
atomic: add some comments about url locations 2017-05-25 11:27:21 -04:00
Dusty Mabe
a5b8d6075e
atomic: use the same url scheme that is used in f2{5,6} 2017-05-25 11:21:19 -04:00
Dusty Mabe
df48af3278
atomic: move to new ref
Since we recently switched to fedora/rawhide/${basearch}/atomic-host
we should start pulling from there.

[1] https://pagure.io/fedora-atomic/c/ffada30
2017-05-25 11:19:39 -04:00
Dusty Mabe
68804358d8
atomic, cloud: remove rhgb by removing plymouth
a59dfe5 caused us a few problems:
  - sed was breaking the symlink on atomic systems
  - /boot/grub2/grub.cfg is not the right file on a UEFI system
  - etc..

We'll solve this problem a different way by just not installing
plymouth in our systems, which is another way [1] to make sure
rhgb/quiet don't appear on your kernel command line.

[1] ee91db6fa3/pyanaconda/payload/__init__.py (L722-L726)
2017-05-24 01:41:20 -04:00
Dusty Mabe
8f142150ba
atomic: don't use cmdline for install mode
similar change was done for docker/cloud in f6ecdc3

cmdline makes it so that %post --erroronfail won't actually stop the
installation in a way that imagefactory will detect the problem and
fail the build. See [1] for more details.

[1] https://github.com/rhinstaller/anaconda/issues/931
2017-05-08 11:36:00 -04:00
Dusty Mabe
a59dfe5f40
atomic, cloud: disable rhgb/quiet on boot
We want more verbose output on boot.

See https://bugzilla.redhat.com/show_bug.cgi?id=510523
2017-05-08 11:35:19 -04:00
Dusty Mabe
4948e8c002
atomic, cloud: don't create none user
Anaconda doesn't seem to require it anymore so no need to create it
and then delete it.
2017-05-08 11:35:16 -04:00
Dusty Mabe
c49c95145d
atomic: update link and revert some of the cherry-pick
Update the trac link to point to the pagure issue. Also
we don't actually want to enable legacy network service.
This was also reverted for f25 in 6f3661e.
2017-04-19 16:29:22 -04:00
Jason Brooks
38c2313eef
networking fixes for f25
* removes the extra ens3 ifcfg that seems to be added
by dracut at some point (cloud base did this in their
ks a year ago in c509863)
* adds net.ifnames=0 to the bootloader line, because
that seems to be necessary to actually disable consistent
device naming
* enables the network service

see https://pagure.io/atomic-wg/issue/174

(cherry picked from commit 5d987e82b3)
2017-04-19 15:59:00 -04:00
Dusty Mabe
fc0a635bc4
zero out resolv.conf during install
Anaconda is writing an /etc/resolv.conf from the install environment.
The system should start out with an empty file, otherwise cloud-init
will try to use this information and may error:
https://bugs.launchpad.net/cloud-init/+bug/1670052
2017-03-28 16:20:25 -04:00
Colin Walters
954957e609 atomic: Append GROWPART to d-s-s config
Rather than truncating.  This allows us to preserve any existing
configuration (e.g. overlayfs by default).
2017-03-21 10:54:59 -04:00
Colin Walters
9912269d88 all: Correct path to /var/lib/systemd/random-seed
At least for Atomic Host, AFAICS it isn't actually in the final
image; not entirely sure why.  But we should be using the right
path here anyways.

https://bugzilla.redhat.com/show_bug.cgi?id=1424404
2017-02-17 15:05:13 -05:00
Colin Walters
740a9b4969 atomic: Add workaround for bash 2016-09-01 16:54:58 -04:00
Adam Williamson
4af7364074 manipulate network service in %post (#1369794)
Due to #1369794 , anaconda cannot currently manipulate sysv
services in F25+. So to work around this, take 'network' out of
the services lines in all kickstarts and instead manipulate
it in the %post section, with chkconfig.

Also remove rsyslog from the Atomic image services line because
it doesn't appear to be included in the OStree tree at present
and so attempting to enable the service breaks Atomic image
compose, see e.g.:

https://kojipkgs.fedoraproject.org//work/tasks/9022/15349022/oz-x86_64.log

also correct the name of the ssh service in fedora-arm-base.ks;
it's sshd not ssh.
2016-08-24 11:27:40 -06:00
Dennis Gilmore
27a0af11dd remove cloud from atomic kickstarts and point at new repo location
Signed-off-by: Dennis Gilmore <dennis@ausil.us>
2016-04-11 14:09:19 -05:00