Hullo
I'm trying to port some .debs from Raspbian to Fedora IoT. Annoyingly, from the point of view of this exercise, the only Fedora image that I can get to work on my Pis is the IoT one (the others don't seem to work with my monitors/hdmi cables).
So, I'm installing dependencies via rpm-ostree, which is a good exercise in any case. However, one of the repos seems to be offline (fedora.roving-it.com: svcs-01.roving-it.com), which is where the wifi/bluetooth firmware were downloaded from. This name resolves to a Digital Ocean droplet, but I don't seem to be able to get to it at all for the past few hours, either by ipv4 or ipv6. Traceroute(6) stops somewhere inside DO.
Is this a normal intermittent failure, and, if so, how long do these normally persist/is there an expected service level?
Tim
On Tue, Sep 25, 2018 at 2:12 PM Tim Coote tim+fedoraproject.org@coote.org wrote:
Hullo
I'm trying to port some .debs from Raspbian to Fedora IoT. Annoyingly, from the point of view of this exercise, the only Fedora image that I can get to work on my Pis is the IoT one (the others don't seem to work with my monitors/hdmi cables).
So, I'm installing dependencies via rpm-ostree, which is a good exercise in any case. However, one of the repos seems to be offline (fedora.roving-it.com: svcs-01.roving-it.com), which is where the wifi/bluetooth firmware were downloaded from. This name resolves to a Digital Ocean droplet, but I don't seem to be able to get to it at all for the past few hours, either by ipv4 or ipv6. Traceroute(6) stops somewhere inside DO.
Is this a normal intermittent failure, and, if so, how long do these normally persist/is there an expected service level?
Seems it didn't come back from a reboot, let me poke it.
Ah. Excellent anecdote for my contention that IoT introduces a big change: moving from an observed to an unobserved system, and spotting and fixing the unhappy paths that result is the bulk of the work.
It's bad enough with connection oriented protocols in low latency environments. It's much harder with sleepy devices that are battery powered.
:-)
tc
up and running now. Thanks, Peter.
I also learned that telnet supports happy eyeballs, which is a win.
It's back!
On Tue, Sep 25, 2018 at 2:14 PM Peter Robinson pbrobinson@gmail.com wrote:
On Tue, Sep 25, 2018 at 2:12 PM Tim Coote tim+fedoraproject.org@coote.org wrote:
Hullo
I'm trying to port some .debs from Raspbian to Fedora IoT. Annoyingly, from the point of view of this exercise, the only Fedora image that I can get to work on my Pis is the IoT one (the others don't seem to work with my monitors/hdmi cables).
So, I'm installing dependencies via rpm-ostree, which is a good exercise in any case. However, one of the repos seems to be offline (fedora.roving-it.com: svcs-01.roving-it.com), which is where the wifi/bluetooth firmware were downloaded from. This name resolves to a Digital Ocean droplet, but I don't seem to be able to get to it at all for the past few hours, either by ipv4 or ipv6. Traceroute(6) stops somewhere inside DO.
Is this a normal intermittent failure, and, if so, how long do these normally persist/is there an expected service level?
Seems it didn't come back from a reboot, let me poke it.
-
Peter Robinson -
Tim Coote