52-technologies-in-2016 icon indicating copy to clipboard operation
52-technologies-in-2016 copied to clipboard

Published 20 hours ago • verified publisher icon shekhargulati

Feedback: Week 8 CoreOS

Open shekhargulati opened this issue 8 years ago • 3 comments

Please provide your feedback by posting a comment against this issue.

shekhargulati avatar Feb 22 '16 17:02 shekhargulati

CoreOS isn't built on ChromeOS. They both use the same SDK, but technically Gentoo is the upstream. CoreOS maintains their own eBuilds and keeps a portage mirror on GitHub.

brianredbeard avatar Feb 22 '16 21:02 brianredbeard

thanks @brianredbeard I will make the changes.

shekhargulati avatar Feb 23 '16 16:02 shekhargulati

That journalctl command you write in the end only happens to work by lucky accident. Had fleet scheduled the unit onto another machine, you would not be able to access it via journalctl, which only works on the local host.

fleetctl journal -f hello.service would work, regardless of where the unit has been scheduled.

The divide between what is operating locally (systemd and journalctl), and what fleet does to unify them into a cluster-wide system is probably one of the more conceptually difficult topics in CoreOS.

You might also need to mention that SSH agent forwarding (with your key added) is really useful, since that is required for many of the fleetctl commands that need to access other hosts (such as pulling info from the journal, or actually logging in to them for you via SSH, to go to where the unit is running).

llarsson avatar Mar 11 '16 07:03 llarsson