3 ms·

Do you still have to have a canonical sso account just to login to your own devices? EDIT: The answer appears to still be yes. I don't know who canonical is ma

Do you still have to have a canonical sso account just to login to your own devices? EDIT: The answer appears to still be yes. I don't know who canonical is making this for, but no company is going to want to deploy IoT devices that hand over the root of trust for authentication to a third party. And I have to believe that many individuals/hobbyists that would otherwise be excited to use this will choose another distro for the same reason. Canonical seems to be out of touch with what people actually want, and is happy to build things it likes that will ultimately be irrelevant.

yourstruly-br 4y ago
They have no clue what the market wants. Nobody is going to shell out $15k-20k to build a solution. We lost about 4 months betting on it and eventually moved away. We are glad we did.
- nix23 4y ago
  >Nobody is going to shell out $15k-20k to build a solution. Well that's not true, if the solution is a success 20k is not much....problem is it rarely is with canonical.
  - yourstruly-br 4y ago
    In our case we were building a solution from scratch. It is very hard to justify upfront costs like that, involving open-source and early in the project. IoT solution costs should move up according to scale. That's why AWS, Azure, and others have grown their IoT offerings. Nobody starts paying $20k upfront to use AWS IoT.
    - nix23 4y ago
      >Nobody starts paying $20k upfront to use AWS IoT. You have not written anything about upfront or IoT. AWS IoT? Is that even a thing? (pun intended)
tssva 4y ago
For individuals and hobbyists Ubuntu Server would likely make more sense than Ubuntu Core. I used to recommend it for use on headless Raspberry Pi's over Raspberry Pi OS. Use of cloud-init and netplan made it much easier for deployment of headless RPi's. Unfortunately for 22.04 they made some changes on the RPi which severely impacted my deployments causing me to move away from Ubuntu on the RPi and to no longer recommend it to others.
- waveform80 4y ago
  What were the changes in 22.04 on the Pi server images that severely impacted you? (disclosure: I'm probably the one that made those changes, so apologies for that, but I'd like to know what they were in case there's anything I can do about them)
  - tssva 4y ago
    Maybe severely was the wrong word to use. I use RPi's in my home lab so any impact no matter how significant is limited in real world impact. In this case it was limited to loss of access to several services in my home lab for a few hours due to a complete loss of network connectivity to the server and a few hours of my time troubleshooting the issue. The major issue was caused by moving some of the kernel modules to linux-modules-extra package. It caused an issue when I upgraded because the 8021q module needed for vlan support was moved to this package. I lost network connectivity to the first Pi I upgraded due to this. The Pi in question had an ip address assigned to the interface and to vlans configured for the interface. When networkd could not create the vlans on the interface it failed without assigning the ip address to the interface itself. I filed a ticket regarding this. I consider the ability to use vlans to be a fairly basic expectation of a server os especially when it previously worked out of the box. I would also think vlan support to be an expected feature for the IoT gateway role pushed as appropriate for Ubuntu Core. Luckily I was able to connect to the serial console, troubleshoot and eventually correct the issue. When the module which supports a commonly used part of the ethernet family of protocols is moved to an optional package, I would expect testing of the impact to connectivity to existing deployments to take place. This led me to lose some faith in the testing done of Ubuntu on the RPi and the stability of the platform going forward. Switching platforms was easy to do in my case and so I did. Hopefully the recommendations I made in my ticket of either moving the module back to linux-modules or adding an explicit warning to the release notes happens. The current warning regarding some modules having been moved to linux-modules-extra, without any detailing of them including the functionality they tie back to, is completely inadequate.

yourstruly-br 4y ago

They have no clue what the market wants. Nobody is going to shell out $15k-20k to build a solution. We lost about 4 months betting on it and eventually moved away. We are glad we did.

nix23 4y ago
>Nobody is going to shell out $15k-20k to build a solution. Well that's not true, if the solution is a success 20k is not much....problem is it rarely is with canonical.
- yourstruly-br 4y ago
  In our case we were building a solution from scratch. It is very hard to justify upfront costs like that, involving open-source and early in the project. IoT solution costs should move up according to scale. That's why AWS, Azure, and others have grown their IoT offerings. Nobody starts paying $20k upfront to use AWS IoT.
  - nix23 4y ago
    >Nobody starts paying $20k upfront to use AWS IoT. You have not written anything about upfront or IoT. AWS IoT? Is that even a thing? (pun intended)

tssva 4y ago

For individuals and hobbyists Ubuntu Server would likely make more sense than Ubuntu Core. I used to recommend it for use on headless Raspberry Pi's over Raspberry Pi OS. Use of cloud-init and netplan made it much easier for deployment of headless RPi's. Unfortunately for 22.04 they made some changes on the RPi which severely impacted my deployments causing me to move away from Ubuntu on the RPi and to no longer recommend it to others.

waveform80 4y ago
What were the changes in 22.04 on the Pi server images that severely impacted you? (disclosure: I'm probably the one that made those changes, so apologies for that, but I'd like to know what they were in case there's anything I can do about them)
- tssva 4y ago
  Maybe severely was the wrong word to use. I use RPi's in my home lab so any impact no matter how significant is limited in real world impact. In this case it was limited to loss of access to several services in my home lab for a few hours due to a complete loss of network connectivity to the server and a few hours of my time troubleshooting the issue. The major issue was caused by moving some of the kernel modules to linux-modules-extra package. It caused an issue when I upgraded because the 8021q module needed for vlan support was moved to this package. I lost network connectivity to the first Pi I upgraded due to this. The Pi in question had an ip address assigned to the interface and to vlans configured for the interface. When networkd could not create the vlans on the interface it failed without assigning the ip address to the interface itself. I filed a ticket regarding this. I consider the ability to use vlans to be a fairly basic expectation of a server os especially when it previously worked out of the box. I would also think vlan support to be an expected feature for the IoT gateway role pushed as appropriate for Ubuntu Core. Luckily I was able to connect to the serial console, troubleshoot and eventually correct the issue. When the module which supports a commonly used part of the ethernet family of protocols is moved to an optional package, I would expect testing of the impact to connectivity to existing deployments to take place. This led me to lose some faith in the testing done of Ubuntu on the RPi and the stability of the platform going forward. Switching platforms was easy to do in my case and so I did. Hopefully the recommendations I made in my ticket of either moving the module back to linux-modules or adding an explicit warning to the release notes happens. The current warning regarding some modules having been moved to linux-modules-extra, without any detailing of them including the functionality they tie back to, is completely inadequate.