similar to: Anyone using coreos?

So I'm not running it on each individual container. Instead I'm running with a guarantee of at least one tinc container on each coreos host and then connect to other containers(currently have about 20 hosts running across the world with this setup) I find on the whole setup to work well, I'm not noticing any unusual overhead, but there is a lot of extra provisioning work I'm doing

Look for /lib/os-release in the /usr partition and try to use it, if present, before using lsb-release later on. This should not change the final result of the inspection, while using the os-release detection method also for CoreOS. --- Nikos, since you added the support for CoreOS in libguestfs, can you please check whether this change works for you as well? Thanks in advance.

Hello, It looks good to me and it makes the code more robust. Removing /usr/lib/os-release in future releases of CoreOS is less probable than removing /usr/share/coreos/lsb-release. After such a change I would also update `test-data/phony-guests/make-coreos-img.sh' to also inject an os-release file in the dummy image it creates. Find attached the `/usr/lib/os-release' and

I've read man ssh and man ssh-keygen and some howtos and still am not getting what I expect. I can do ssh john at 192.168.15.3 and login with a password OK. I want to be able to do that with keys in preparation for running rsync with keys, so I created a key on router1, the machine I want to ssh from. routem at router1:~/.ssh$ lla total 20 drwx------ 2 routem routem 4096 2009-03-08 09:55 .

* Implement coreos distro * Detect CoreOS images Signed-off-by: Nikos Skalkotos <skalkoto@grnet.gr> --- generator/actions.ml | 4 +++ src/guestfs-internal.h | 3 +++ src/inspect-fs-unix.c | 69 +++++++++++++++++++++++++++++++++++++++++++++++--- src/inspect-fs.c | 21 +++++++++++++++ src/inspect-icon.c | 1 + src/inspect.c | 59

Hello, is CoreOS supported by libguestfs? I was trying to run several commands some were successful others ended up with an error: for example virt-df was OK but when I tried to do virt-resize I got the following error message: root@ny2proxd03:/var/lib/vz/images/100# virt-resize --expand /dev/sda3 vm-100-disk-1.qcow2 vm-100-disk-1.qcow2.resized Examining vm-100-disk-1.qcow2 ... 100%

I've not really dug into testing tinc yet, but if you all will humor me in an uneducated blast of questions, I'd appreciate it. What can you do to keep tinc going if your high availability comes from cluster nodes being dispensable? Can tinc run on the cluster nodes? That seems like chicken/egg problem though to get tinc server installed and cluster nodes brought up... If tinc needs to be

Signed-off-by: Nikos Skalkotos <skalkoto@grnet.gr> --- .gitignore | 1 + inspector/Makefile.am | 1 + inspector/expected-coreos.img.xml | 30 +++++++++++ tests/guests/Makefile.am | 6 +++ tests/guests/guest-aux/make-coreos-img.sh | 83 +++++++++++++++++++++++++++++++ tests/guests/guests.xml.in | 16

Hello I'm sure someone has already tried this: I use a couple of electric heaters to heat my office. I'd like to somehow connect them to Asterisk so that I could switch them on remotely by either calling the IVR or sending an e-mail to the Asterisk host, so that the room is warm when I get to the office :-) Any information appreciated. Thank you.

> On Oct 1, 2018, at 3:25 PM, David Blaikie <dblaikie at gmail.com> wrote: > > > On Mon, Oct 1, 2018 at 3:24 PM JF Bastien <jfbastien at apple.com <mailto:jfbastien at apple.com>> wrote: >> On Oct 1, 2018, at 3:16 PM, David Blaikie <dblaikie at gmail.com <mailto:dblaikie at gmail.com>> wrote: >> >> (my vote, somewhat biased - is that

I am searching for the cheapeat *nix SOC device with ethernet and wifi that can run Python 2.7. Ethernet should be 100mbit and hopefully supporting PXE. OT because im doubting you can squeeze our bloaty friend onto such a device.... :)

> On Oct 1, 2018, at 3:16 PM, David Blaikie <dblaikie at gmail.com> wrote: > > (my vote, somewhat biased - is that I'd love to see more investment in Bloaty (to keep all these sort of size analysis tools and tricks in one place), but sort of accept folks are probably going to keep building more infrastructure for this sort of thing in LLVM directly) I get where that comes

Hello, I worked on a code size analysis tool for a 'week of code' project and think that it might be useful enough to upstream. The tool is inspired by bloaty (https://github.com/google/bloaty), but tries to do more to attribute code size in actionable ways. For example, it can calculate how many bytes inlined instances of a function added to a binary. In its diff mode, it can show how

This patch set adds support for inspecting CoreOS installations. In CoreOS the files that need to be inspected under /etc are links to files under /usr which is hosted on a different partition and mounted read only. Hence, inspecting the root fs is not enough to gather all needed information. This patch set adds code for recognizing the root and the /usr partitions of CoreOS and a new internal

On Wed, Mar 30, 2016 at 04:38:31PM +0200, Pino Toscano wrote: > Look for /lib/os-release in the /usr partition and try to use it, if > present, before using lsb-release later on. This should not change the > final result of the inspection, while using the os-release detection > method also for CoreOS. > --- > Nikos, since you added the support for CoreOS in libguestfs, can you

Signed-off-by: Nikos Skalkotos <skalkoto@grnet.gr> --- .gitignore | 1 + inspector/Makefile.am | 1 + inspector/expected-coreos.img.xml | 30 +++++++++++ inspector/test-virt-inspector.sh | 2 +- tests/guests/Makefile.am | 6 +++ tests/guests/guest-aux/make-coreos-img.sh | 83

This should make CentOS even better!: https://www.geekwire.com/2018/red-hat-snaps-coreos-250m-adding-big-piece-container-strategy/ - Ryan https://prefetch.net

On Fri, May 29, 2015 at 12:24:58PM +0300, Nikos Skalkotos wrote: > + if (collect_coreos_inspection_info (g)) { > + guestfs_int_free_inspect_info (g); > + return NULL; > + } Although this is stylistic, I think it's easier to understand if you change the if condition to: if (collect_coreos_inspection_info (g) == -1) { ... Rich. -- Richard Jones, Virtualization

On 02/06/15 17:10, Richard W.M. Jones wrote: Hello, > On Fri, May 29, 2015 at 12:24:58PM +0300, Nikos Skalkotos wrote: >> + if (collect_coreos_inspection_info (g)) { >> + guestfs_int_free_inspect_info (g); >> + return NULL; >> + } > Although this is stylistic, I think it's easier to understand if > you change the if condition to: > > if

On Tue, Jun 02, 2015 at 06:18:38PM +0300, Nikos Skalkotos wrote: > On 02/06/15 17:10, Richard W.M. Jones wrote: > Hello, > > > On Fri, May 29, 2015 at 12:24:58PM +0300, Nikos Skalkotos wrote: > >> + if (collect_coreos_inspection_info (g)) { > >> + guestfs_int_free_inspect_info (g); > >> + return NULL; > >> + } > > Although this is