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
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
provi
- Original Message -
> OK part of my confusion is that 'grub2-mkconfig' does not work when
> called directly. Doing that results in a malformed grub.cfg.
>
> What is the correct way, on atomic builds, to recreate the grub.cfg?
> How does rpm-ostree do this?
Yeah, I've been confused by tha
- 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
- Original Message -
> On Mon, Jan 4, 2016 at 11:35 AM, Colin Walters wrote:
> > On Wed, Dec 23, 2015, at 11:50 AM, Jonathan Lebon wrote:
> >> Hi all,
> >>
> >> As some of you may already know, I've been working on adding
> >> a new
- 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
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 la
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 ea
Hi Joe,
Just wrote the change proposal for this[1]. I haven't yet tagged it
in the relevant categories. Since it's my first change proposal, I
wanted to run it by you (and others) to see if it's all in order.
Thanks,
Jonathan
[1] https://fedoraproject.org/wiki/Changes/Atomic_Developer_Mode
- 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
- 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 mailin
- Original Message -
> We do have F24 Atomic images, autocloud just fails to notice them.
> fedora_nightlies finds them just fine:
>
> https://www.happyassassin.net/nightlies.html
When I boot the latest F24 Atomic qcow2 image there (right
now "Fedora-Atomic-24-20160422.n.0.x86_64.qcow2"),
- 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
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 hos
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, 201
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 acro
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-ato
> - pre-loading containers on system startup
> * there is a need for being able to load containers on system
> startup into the container runtime. I think jlebon already
> worked on something like this maybe. Either way the idea is that
> we have a service that looks in a cert
> cool. seems like we got most of the way there but never integrated it
> into atomic host? Is it in any shipped version of atomic host that we
> produce?
It was more of a POC. If we want to get this into Fedora, it
might be worth integrating into the projectatomic/atomic
codebase, rather than a s
I traced it down to:
http://pkgs.fedoraproject.org/cgit/rpms/atomic.git/commit/?h=f25&id=7d15e4a0be2db29deda4b92a039a041d81bbe205
http://pkgs.fedoraproject.org/cgit/rpms/atomic.git/commit/?h=f25&id=cb845639e7388bb9aa3b5aef7dabffa3434b1ae1
I.e. atomic needs to build RPMs for the system container
w
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
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
Thanks Adam for the quick resolution. Would it be easy to
have an automated workflow to gate these updates on some
quick sanity tests? E.g. push to `:next` first, run some
tests, and then push to `:latest`?
We're starting to rely more and more on this image in
upstream tests, which means that any
And of course I didn't finish my sentence :), which is:
If yes, then let's log an issue in the atomic-wg perhaps?
- Original Message -
> Thanks Adam for the quick resolution. Would it be easy to
> have an automated workflow to gate these updates on some
> quick sanity tests? E.g. push to
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
comfo
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
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
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 d
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
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
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 lis
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.f
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
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 lin
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
T
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
T
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 r
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 l
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
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/.
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 l
> 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 pul
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 u
43 matches
Mail list logo
