[fedora-atomic] PR #87: add back in gluster/ceph

[Jonathan Lebon]

jlebon merged a pull-request against the project: `fedora-atomic` that you are 
following.

Merged pull-request:

``
add back in gluster/ceph
``

https://pagure.io/fedora-atomic/pull-request/87
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Persistent URLs for images (again :)

[Jonathan Lebon]

> FWIW, in the Cockpit project CI/CD bots end up manually scraping layers
> index.html URL(s) to find the latest images.
> 
> https://github.com/cockpit-project/cockpit/blob/master/bots/images/scripts/fedora-atomic.bootstrap

For Fedora Atomic Host specifically, there are symbolic links you
can pull at least:

https://fedoraproject.org/wiki/Cloud#Fedora_Cloud_Atomic_Image_Download_Links
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[fedora-atomic] PR #79: post: Re-instate systemd ProtectHome/ProtectSystem and PrivateTmp

[Jonathan Lebon]

jlebon merged a pull-request against the project: `fedora-atomic` that you are 
following.

Merged pull-request:

``
post: Re-instate systemd ProtectHome/ProtectSystem and PrivateTmp
``

https://pagure.io/fedora-atomic/pull-request/79
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[fedora-atomic] PR #79: post: Re-instate systemd ProtectHome/ProtectSystem and PrivateTmp

[Jonathan Lebon]

jlebon commented on the pull-request: `post: Re-instate systemd 
ProtectHome/ProtectSystem and PrivateTmp` that you are following:
``
Huh, weird. It's on the cloud list at least: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/ABP32B6H3Z25R77A4PZIT56TKV2DC2IU/.
 Merging!
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/79
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[fedora-atomic] PR #79: post: Re-instate systemd ProtectHome/ProtectSystem and PrivateTmp

[Jonathan Lebon]

jlebon commented on the pull-request: `post: Re-instate systemd 
ProtectHome/ProtectSystem and PrivateTmp` that you are following:
``
Just to be sure, you meant the release that already went out today or in the 
next one in two weeks? Seems like it should be safe to merge now.
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/79
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[fedora-atomic] PR #78: post: Re-instate systemd ProtectHome/ProtectSystem and PrivateTmp

[Jonathan Lebon]

jlebon commented on the pull-request: `post: Re-instate systemd 
ProtectHome/ProtectSystem and PrivateTmp` that you are following:
``
It seems like the fix made it in systemd v232, which is in F26 as well. We 
should consider getting this in f26/f27 too, but let's prove it out in rawhide.
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/78
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[fedora-atomic] PR #78: post: Re-instate systemd ProtectHome/ProtectSystem and PrivateTmp

[Jonathan Lebon]

jlebon merged a pull-request against the project: `fedora-atomic` that you are 
following.

Merged pull-request:

``
post: Re-instate systemd ProtectHome/ProtectSystem and PrivateTmp
``

https://pagure.io/fedora-atomic/pull-request/78
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[fedora-atomic] PR #77: manifest: Add microcode_ctl

[Jonathan Lebon]

jlebon merged a pull-request against the project: `fedora-atomic` that you are 
following.

Merged pull-request:

``
manifest: Add microcode_ctl
``

https://pagure.io/fedora-atomic/pull-request/77
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[fedora-atomic] PR #76: manifest: Add microcode_ctl

[Jonathan Lebon]

jlebon merged a pull-request against the project: `fedora-atomic` that you are 
following.

Merged pull-request:

``
manifest: Add microcode_ctl
``

https://pagure.io/fedora-atomic/pull-request/76
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[fedora-atomic] PR #27: post: Work around LVM archival conflicting with ostree

[Jonathan Lebon]

jlebon commented on the pull-request: `post: Work around LVM archival 
conflicting with ostree` that you are following:
``
Would be nice to see this happen still. I'm sorely reminded of it every time I 
run `ostree admin config-diff` and have to swim through the output.
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/27
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[fedora-atomic] PR #68: f26: remove json file symlink

[Jonathan Lebon]

jlebon merged a pull-request against the project: `fedora-atomic` that you are 
following.

Merged pull-request:

``
f26: remove json file symlink
``

https://pagure.io/fedora-atomic/pull-request/68
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[fedora-atomic] PR #68: f26: remove json file symlink

[Jonathan Lebon]

jlebon commented on the pull-request: `f26: remove json file symlink` that you 
are following:
``
LGTM.
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/68
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[fedora-atomic] PR #67: rawhide: remove json file symlink

[Jonathan Lebon]

jlebon commented on the pull-request: `rawhide: remove json file symlink` that 
you are following:
``
LGTM, promise kept.
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/67
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[fedora-atomic] PR #67: rawhide: remove json file symlink

[Jonathan Lebon]

jlebon merged a pull-request against the project: `fedora-atomic` that you are 
following.

Merged pull-request:

``
rawhide: remove json file symlink
``

https://pagure.io/fedora-atomic/pull-request/67
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #295: Start using new mailing list/IRC channel around f26 release time

[Jonathan Lebon]

jlebon added a new comment to an issue you are following:
``
> discussions and troubleshooting Fedora build pipeline/releng (bodhi, punji, 
> etc.) for Atomic will be on the new channel #fedora-atomic. Content 
> discussions which start there will get re-directed to #atomic.

Sorry if I'm missing context from the IRC #fedora-cloud convo, but isn't the 
proper place for those discussions in #fedora-releng? Is it worth having a 
separate channel just for FAH releng? If that's really the case, then maybe the 
channel should be called #fah-releng instead. Calling it "fedora-atomic" 
invites discussions that should probably happen in #atomic by the proposal.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/295
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #282: Atomic Host images omit many common locales that all other flavors include

[Jonathan Lebon]

jlebon added a new comment to an issue you are following:
``
https://github.com/rhinstaller/anaconda/pull/1122
https://github.com/rhinstaller/lorax/pull/227
https://bugzilla.redhat.com/show_bug.cgi?id=1468619

I take it GA is far too close to have these in on time, but I hope we can get 
them in during a follow-up TWR.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/282
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[fedora-atomic] PR #63: Rename treefile to match ref

[Jonathan Lebon]

jlebon merged a pull-request against the project: `fedora-atomic` that you are 
following.

Merged pull-request:

``
Rename treefile to match ref
``

https://pagure.io/fedora-atomic/pull-request/63
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[fedora-atomic] PR #63: Rename treefile to match ref

[Jonathan Lebon]

jlebon commented on the pull-request: `Rename treefile to match ref` that you 
are following:
``
Yup, that makes sense.
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/63
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #282: Atomic Host images omit many common locales that all other flavors include

[Jonathan Lebon]

jlebon added a new comment to an issue you are following:
``
So just ballparking here, but 137 MB on disk will probably translate to ~35 MB 
additional space of the qcow2 (based on the same compression ratios I found in 
https://bugzilla.redhat.com/show_bug.cgi?id=1186757). I think if we're 
comfortable with that (I am :)), I'd vote for just shipping all the locales.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/282
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Requesting freeze exception for atomic in F26 to drop rpm-build deps

[Jonathan Lebon]

Hi,

If I understand correctly, in its current state, F26 AH will
be shipping with the atomic package which added the
rpm-build deps. The update that removes it again is blocked
in testing:

https://bodhi.fedoraproject.org/updates/FEDORA-2017-ac1919a04b

Double-checking the current state:

$ ostree remote add fedora-26 --no-gpg-verify 
https://kojipkgs.fedoraproject.org/atomic/26/
$ ostree pull fedora-26 --subpath=/usr/share/rpm --depth=0 
fedora/26/x86_64/atomic-host
  
$ ostree checkout -U --subpath=/usr/share/rpm 
fedora-26:fedora/26/x86_64/atomic-host tmp/rpmdb-26 
   
$ rpm -qa --dbpath $PWD/tmp/rpmdb-26 | grep -E '(rpm-build|gdb)'
gdb-headless-7.12.50.20170226-4.fc26.x86_64
rpm-build-libs-4.13.0.1-4.fc26.x86_64
rpm-build-4.13.0.1-4.fc26.x86_64
gdbm-1.13-1.fc26.x86_64

If this is what the F26 AH deliverables will be based on,
then would it be possible to justify a freeze exception out
of this? It's a pretty big wart on a new AH release, esp.
since the motto is that we're a streamlined OS, though it's
obviously not a critical release blocker.
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[fedora-atomic] PR #59: f26: add back in kube/storage clients for now

[Jonathan Lebon]

jlebon commented on the pull-request: `f26: add back in kube/storage clients 
for now` that you are following:
``
> Basically:
> ```
> rpm-ostree rebase fedora/27/x86_64/atomic-host
> rpm-ostree install kubernetes
> ```

Just in case this ticket yields documentation/blog posts or gets referred to by 
users, one can do this even more efficiently in the latest rpm-ostree:

```
rpm-ostree rebase fedora/27/x86_64/atomic-host --install kubernetes
```

For more information, see 
http://www.projectatomic.io/blog/2017/04/rpm-ostree-v2017.4-released/.
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/59
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[fedora-atomic] PR #54 `manifest: Change the ref/branch name to be fedora/.../atomic-host`

[Jonathan Lebon]

jlebon commented on the pull-request: `manifest: Change the ref/branch name to 
be fedora/.../atomic-host` that you are following:
``
That looks nice to me. I'll let @dustymabe take a look and do the merge.
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/54
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [atomic-devel] Fedora 26 change: using overlayfs as default

[Jonathan Lebon]

The Docker docs also has a breakdown of incompatibilities:

https://docs.docker.com/engine/userguide/storagedriver/overlayfs-driver/#/overlayfs-compatibility

Notably, there's the open(2) issue that has already been
mentioned. The second issue is that rename(2) can fail if
trying to move a dir across the lower and upper dirs:

$ mkdir lower upper work merged
$ mkdir lower/dir
$ sudo mount -t overlay overlay \
-olowerdir=$PWD/lower,upperdir=$PWD/upper,workdir=$PWD/work \
merged
$ python -c 'import os; os.rename("merged/dir", "merged/dir2")'
Traceback (most recent call last):
File "", line 1, in 
OSError: [Errno 18] Invalid cross-device link

So you have to watch for EXDEV and fall back on copying.
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Current Fedora 25 Atomic images are failing to boot

[Jonathan Lebon]

Just an update on this. We're passed the kernel panic issue
now that dracut-fips was backed out, but we're now getting
a reboot loop due to:

https://bugzilla.redhat.com/show_bug.cgi?id=1290659

- Original Message -
> 
> 
> On 10/03/2016 02:47 AM, Trishna Guha wrote:
> > On Wed, Sep 28, 2016 at 9:26 PM, Kushal Das  wrote:
> >> Hi all,
> >>
> >> The current F25 Atomic images are failing to boot[1], I never managed to
> >> reach
> >> dracut emergency shell in my local box.
> >>
> >> Can anyone else also please have a look?
> >>
> >> [1] https://apps.fedoraproject.org/autocloud/jobs/704/output
> > 
> > All the Fedora 25 Atomic images: qcow2, vagrant-libvirt,
> > vagrant-virtualbox are failing to boot.
> 
> 
> There is a kernel panic happening early in boot. Here is the serial
> console log from one of those boots:
> 
> https://paste.fedoraproject.org/442720/14755209/
> 
> Dusty
> ___
> cloud mailing list -- cloud@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
> 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Fedora 24 Atomic: Issue with /etc/os-release VARIANT_ID not being updated on Fedora 23 upgrade.

[Jonathan Lebon]

This is probably related:
https://pagure.io/fedora-atomic/issue/6

- Original Message -
> Hi all,
> 
> I just upgraded to the latest Fedora Atomic 24 Host with today's release and
> it seems that the recent commit still hasn't updated /etc/os-release:
> 
> [fedora@atomic ~]$ sudo atomic host upgrade
> Updating from: fedora-atomic:fedora-atomic/24/x86_64/docker-host
> No upgrade available.
> [fedora@atomic ~]$ sudo^C
> [fedora@atomic ~]$ cat /etc/os-release
> NAME=Fedora
> VERSION="24 (Twenty Four)"
> ID=fedora
> VERSION_ID=24
> PRETTY_NAME="Fedora 24 (Twenty Four)"
> ANSI_COLOR="0;34"
> CPE_NAME="cpe:/o:fedoraproject:fedora:24"
> HOME_URL=" https://fedoraproject.org/ "
> BUG_REPORT_URL=" https://bugzilla.redhat.com/ "
> REDHAT_BUGZILLA_PRODUCT="Fedora"
> REDHAT_BUGZILLA_PRODUCT_VERSION=24
> REDHAT_SUPPORT_PRODUCT="Fedora"
> REDHAT_SUPPORT_PRODUCT_VERSION=24
> PRIVACY_POLICY_URL= https://fedoraproject.org/wiki/Legal:PrivacyPolicy
> [fedora@atomic ~]$
> 
> 
> Charlie Drage
> PGP - 4096R/C037D617
> http://pgp.mit.edu/pks/lookup?op=get=0xDA227403C037D617
> 
> On Tue, Jul 12, 2016 at 4:56 PM, Colin Walters < walt...@verbum.org > wrote:
> 
> 
> 
> On Tue, Jul 12, 2016, at 03:17 PM, Charlie Drage wrote:
> 
> 
> 
> Issue:
> VARIANT_ID isn't updated within /etc/os-release from this commit:
> https://pagure.io/fork/sgallagh/fedora-release/c/56267336c738f80e3e7a344c740b5d02730c76c6
> to Fedora 24 Atomic host.
> Fixed:
> https://pagure.io/fedora-atomic/c/736d9dae7576c0382178719082068810d8c73bbf
> 
> ___
> cloud mailing list
> cloud@lists.fedoraproject.org
> https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
> 
> 
> 
> ___
> cloud mailing list
> cloud@lists.fedoraproject.org
> https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
> 
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: No RPM DB in latest Fedora 23 atomic images

[Jonathan Lebon]

- Original Message -
> The tests are failing for the latest Fedora 23 atomic images:
> 
> https://pagure.io/atomic-images/issue/36
> 
> There seems to be no rpm db inside the image:
> 
> -bash-4.3# rpm -qa
> -bash-4.3# echo $?
> 0

Seems like /usr/share/rpm does indeed have the rpmdb:

# mv /var/lib/rpm{,.bak}
# ln -s /usr/share/rpm /var/lib
# rpm -qa | wc -l
358

For some reason, the compose didn't clean up /var/lib/rpm and thus we didn't 
create the compat symlink on boot. The journal says this:

Jun 13 20:13:16 localhost.localdomain systemd-tmpfiles[753]: 
[/usr/lib/tmpfiles.d/tmpfiles-ostree-integration.conf:18] Duplicate line for 
path "/var/lib/rpm", ignoring.

(Not sure if that's tmpfiles' way of saying EEXIST).
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Fedora Atomic Host Two Week Release Announcement

[Jonathan Lebon]

- Original Message -
> Can we get a blog post of this which explains what's in it, especially
> Developer Mode?

I had a blog post PR ready to go for the website, but I see
now that it needs a rebase. Will ping you once I do that.
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Fedora Atomic Host Two Week Release Announcement

[Jonathan Lebon]

- Original Message -
> A new update of Fedora Cloud Atomic Host has been released and can be
> downloaded at:

Does anyone know which kickstart files are used when
creating these images? I thought they came from the
spin-kickstarts repo, but e.g. the kickstart edit from
commit 6641de0 doesn't appear in /root/anaconda-ks.cfg. And
so the Developer Mode boot entry didn't get added.

Or is it because that commit is from 5 days ago, and the
kickstart file somehow got picked up earlier than that?

[1] 
https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?h=f23=6641de0
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Fedora 23 Cloud Atomic Developer Mode Preview

[Jonathan Lebon]

Just uploaded a newer image (available at [1]) which
addresses some of the feedback received:
- The generated passwords should now be easier to type,
  with no easily misidentified letters.
- Helper message to explicitly say how to log into
  Cockpit.
- New tmux terminals and easy shortcuts for switching
  between them.

Cheers!

Jonathan

[1] https://jlebon.fedorapeople.org/atomic-devmode/latest/
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Fedora 23 Cloud Atomic Developer Mode Preview

[Jonathan Lebon]

I looked into this a bit more. Cloud-init provides an easy way to
give a fallback datasource when all other sources fail. It tries
multiple networked datasources before that.

For each of them, there is a 'timeout' and a 'max_wait' field. The
former is the timeout per connection attempt, and the latter is the
total amount of time before completely giving up retrying.

These are the URLs it tries to connect to:
- http://169.254.169.254/openstack (OpenStack, 10s timeout, no wait)
- http://169.254.169.254/2009-04-04/meta-data/instance-id (EC2, 50s timeout, 
120s max_wait)
- http://192.168.122.1/latest/meta-data/instance-id (CloudStack, 50s timeout, 
120s max_wait)

So, with the default behaviour, it takes 10+120+120 = 250s before
cloud-init finally decides to use the fallback source. I'm not sure
what the rationale is for making the EC2 and CloudStack values so
high (esp. in contrast to OpenStack).

If do go this way, I think we'd have to lower them to more
reasonable values so that the total time is at least under a
minute.
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Fedora 23 Cloud Atomic Developer Mode Preview

[Jonathan Lebon]

- Original Message -
> One other idea:
> 
> We simply do this by default for all cloud images, without a timeout - if no
> cloud-init metadata is provided, you can log in to the hypervisor console
> and see an autogenerated root password.

I like that. So just to make sure I understand what you mean here:
  - No new boot menu item
  - Whenever cloud-init fails to find a source, we generate an
expired root pw, disable ssh pwauth, and autologin
  - Atomic Developer Mode is started by a user command (e.g.
a /usr/bin/atomic-devmode)

Is that correct?

One issue here is that cloud-init takes some time before realizing
that it has no source. It tries to connect to the default metadata
server address. It uses a 50s timeout it seems. We would probably
have to reduce this to something more sensible (5s? 10s?).
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Fedora 23 Cloud Atomic Developer Mode Preview

[Jonathan Lebon]

- Original Message -
> I tried devmode this afternoon and it worked very well.  I discussed a few
> nits with jlebon on #atomic, but thought I would mention them here.
> 
> - The generated root password can include similar characters l (letter L), 1
> (number 1), O (upper-case letter O), 0 (number zero), etc.  I got bit by
> this when I tried to login to the cockpit interface.  Perhaps we could
> eventually use something like a series of dictionary words separated by a
> certain character?  (I found a discussion on StackOverflow [1] about this
> potential problem.)

I'm thinking of just rerunning pwmake until it satisfies our criteria,
rather than either crafting passwords ourselves, or messing with the string
it outputs and reducing the entropy.

> - I think we should include a string under the cockpit URL that says
> something like "Login to the cockpit console with the username "root" and
> the generated password above".  If an intended audience is people who have
> never used Linux, we should be fairly explicit with instructions right out
> of the box.

Agreed, good idea.
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Fedora 23 Cloud Atomic Developer Mode Preview

[Jonathan Lebon]

Hi all,

As some of you may already know, I've been working on adding
a new feature to the Fedora 23 Cloud Atomic image called
"Developer Mode" (I'm not sure yet if this is the correct
name for it). The Trello card is available at [1].

The high-level goal is to make Atomic more accessible by
providing a new GRUB 2 menu item labeled e.g. "Fedora 23
(Twenty Three) Developer Mode". This mode is an attempt to
provide a painless experience for folks who want to try out
Atomic, but (1) do not want to bother setting up a cloud-
init datasource, or (2) do not know anything about cloud-
init, or even (3) do not have much experience with
Linux overall.

Since the functionality is completely integrated into the
image, there are no requirements on the host system, other
than its ability to boot VMs.

When booted in Developer Mode, the following happens:
- cloud-init uses a local built-in datasource
- a new root password is generated
- the root user is automatically logged in on tty1
- the cockpit/ws image is downloaded and started
- a tmux session is started on tty1 to provide all the
  relevant information (root password, IP address,
  Cockpit console address)

The first Developer Mode image is available at [2]. I invite
you all to try it out and let me know what you think! I've
enabled the plymouth splash screen, which for now uses the
Fedora theme, but might later be switched over to an Atomic
theme.

I'd still like to give users a more helpful welcome message
after login. Maybe we could link to a new page on
projectatomic.io which describes Developer Mode in more
details.

As Matthew Miller pointed out, one of the drawbacks of this
approach is that the GRUB 2 menu timeout will probably have
to be slightly increased to give users more time to make
their selection (at the expense of also increasing boot
times in contexts that don't care about Developer Mode).

In my experience, increasing it by only 1s (for a total of
2s) was enough, but we should probably discuss it more. We
can also minimize this by shipping with a grub.cfg that uses
a 2s timeout, but with the default of 1s, so that at the
next grub2-mkconfig (e.g. on an upgrade/rebase), it will go
back to 1s.

Code is available at [3]. Some modifications to the
kickstart file were also necessary.

Cheers,

Jonathan

---

TL;DR: I added a new boot menu item to the Atomic image so
that you don't have to set up cloud-init. You can download
it from [2].

[1] https://trello.com/c/eK54YRTp
[2] https://jlebon.fedorapeople.org/atomic-devmode/latest/
[3] https://github.com/jlebon/atomic-devmode
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Fedora cloud image feedback

[Jonathan Lebon]

Hi all,

> https://fedoraproject.org/wiki/Changes/Local_Test_Cloud

Interesting tool. Hadn't seen it before.

I've also been working on a similar feature for the Atomic
image (although it should work just fine for the Base images
as well if we want). Basically, it adds a new boot menu item
labeled "Developer Mode" (working title ;) ).

It's meant for users with little experience (e.g. don't know
anything about cloud-init or how to use Vagrant, or even
Linux in general) or for those who want to "kick the tire",
so to speak.

When booted in Dev Mode:
   - cloud-init is configured to set a password for the
 cloud-user and root accounts
   - tty1 is automatically logged in as root with a tmux
 shell set up
   - cockpit is automatically downloaded and started and
 a URL is printed out for users to open in their
 browsers.

There is a card on the platinfra Trello board for this work:
https://trello.com/c/eK54YRTp

One advantage of this approach is that everything necessary
is encapsulated in the image, so there are no pkg (or even
OS) requirements on the user env (other than being able to
boot the image). But it does require a small kickstart
tweak as well as a new package added.

Cheers,

Jonathan
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org