Linode vs other cloud

Hello Ruchika,

We're excited to hear that you're interesting in Linode! I'm a Linode user, but as I work for them I'm a bit biased. Lets see if we can get you some answers without bias, though.

1. Linode features availability for above

Linode will allow you to do everything you've listed, though, IAM is an Amazon proprietary service. As Amazon offers many different kinds of services that supplement their services, IAM helps businesses manage their users accordingly to all of them. Linode is a more simpler hosting provider, providing the most powerful server possible with fewer, but essential, extras - such as backups. To manage these services on Linode, you can create users and edit their permissions:

https://www.linode.com/docs/platform/ac … -passwords">https://www.linode.com/docs/platform/accounts-and-passwords

You can add two factor authentication for extra security as well:

~~[https://www.linode.com/docs/security/linode-manager-security-controls" target="_blank">](https://www.linode.com/docs/security/li … y-controls">https://www.linode.com/docs/security/linode-manager-security-controls](

2. Linode Pricing/reliability compared to AWS

Linode is quite affordable, and in many cases much less taxing on the wallet compared to other hosting companies. I don't want to knock on any competitor so I'll leave this question for others, but Linode charges a flat rate for a block of resources as opposed to dynamically changing. You can see the prices here:

https://www.linode.com/pricing

3. Migration issues if any that people faced

This one really depends on the process taken to bring the content over, but it's relatively seamless from every person I've spoken to. If you're pressed on your existing duties, our Professional Services team can take care of the migration for you:

https://www.linode.com/professional-services

Good luck!

P.S. You can use the code 'linode10' for some extra starting credit.

I've been a linode customer for a very long time… since $20 got you 32mb ram and 6gb of disk space :)

I use my nodes to host my own domains and a few for friends (mail, dns,and web), some LAMP projects, and as a teaching resource (LAMP development and Linux admin)

I've never had an issue with my nodes that I didn't cause :) The times I've contacted support they've bent over backwards to say "yes" and help me out, although these were all related to weird billing stuff (I think where I work was one of the first to want to pay with a PO process).

Cost wise? I used AWS for a school thing since it was free for a year, and I figured that the micro amazon instance could cost me $15/mo and only provide 1/3 to 1/2 the cpu/ram/disk resources and only 1/4 the transfer that linode provided for the then-minimum $20/mo machine.

Now that linode has a $5/mo plan, I'm going to not allow my students to use AWS this term…

The biggest drawback of Linode imho is their use of limited custom kernels. For example on CentOS 7 it's not possible to enable SELinux and you can have issue with Docker as CONFIGNETFILTERXTMATCHIPVS is missing…

And yes it is possible to use the default os kernel by following this guide: ~~[https://www.linode.com/docs/tools-reference/custom-kernels-distros/run-a-distribution-supplied-kernel-with-kvm" target="_blank">](https://www.linode.com/docs/tools-refer … l-with-kvm">https://www.linode.com/docs/tools-reference/custom-kernels-distros/run-a-distribution-supplied-kernel-with-kvm](

But it's just not user-friendly and should be an easy choice when rebuilding or deploying a new Linode.

Disabling SElinux by default is such a bad design choice.

Apart from that it's a good value for price.

Interesting…

@willemdh:

The biggest drawback of Linode imho is their use of limited custom kernels. For example on CentOS 7 it's not possible to enable SELinux and you can have issue with Docker as CONFIGNETFILTERXTMATCHIPVS is missing…

And yes it is possible to use the default os kernel by following this guide: ~~[https://www.linode.com/docs/tools-reference/custom-kernels-distros/run-a-distribution-supplied-kernel-with-kvm" target="_blank">](https://www.linode.com/docs/tools-refer … l-with-kvm">https://www.linode.com/docs/tools-reference/custom-kernels-distros/run-a-distribution-supplied-kernel-with-kvm](

But it's just not user-friendly and should be an easy choice when rebuilding or deploying a new Linode.

Disabling SElinux by default is such a bad design choice.

Apart from that it's a good value for price.

I've run Docker but not for anything serious yet. What does CONFIGNETFILTERXTMATCHIPVS do that I might one day need?

I ran RedHat back in the day before the split as my own Desktop then later Ubuntu. I never saw either my own or any place I worked that I can recall, never saw SELinux work right and it or most packages needed to have configuration (which I can't recall now) to disable SELinux so they would work.

Comparing Linode to Digital Ocean: Some of my client's clients are lawyers and they find Digital Ocean's terms of service give the company too much freedom to plunder and abuse content that the user puts there. DO was approached to negotiate on the terms and they refused.

Comparing server firms headquartered in the US (e. g. Linode) to those in maybe some other countries: If you are publishing or storing anything politically sensitive, you might want to choose a server as out of reach of US officials as possible and in a country that is unlikely to be acting in cahoots with US officials as you can afford. I'm not going to hazard a guess here as to which countries those might be.

Jack Waugh

@willemdh:

The biggest drawback of Linode imho is their use of limited custom kernels. For example on CentOS 7 it's not possible to enable SELinux and you can have issue with Docker as CONFIGNETFILTERXTMATCHIPVS is missing…
Most, if not all of our distro templates, can be booted with the distribution's kernel, straight out of the box. Here's how:

Deploy CentOS, click on your Linode's configuration profile, set the kernel to GRUB, save, and boot. Done. You now have SELinux and all of the other patches distros apply to their kernels.

-Chris

@caker:

@willemdh:

The biggest drawback of Linode imho is their use of limited custom kernels. For example on CentOS 7 it's not possible to enable SELinux and you can have issue with Docker as CONFIGNETFILTERXTMATCHIPVS is missing…
Most, if not all of our distro templates, can be booted with the distribution's kernel, straight out of the box. Here's how:

Deploy CentOS, click on your Linode's configuration profile, set the kernel to GRUB, save, and boot. Done. You now have SELinux and all of the other patches distros apply to their kernels.

-Chris

Other way is to build them as modules and upload only the modules and run modprobe. its far easiest than the grub. On Centos in Linode these 2 modules are not enabled.

CONFIG_NETFILTER_XT_MATCH_IPVS=m
CONFIG_VXLAN=m

Download the kernel version of your linode from kernel.org and get the linode kernel config file and enable the above said as modules "vlan.ko & xt_ipvs.ko" build and move them to the

/usr/lib/modules/KERNEL_VERSION
depmod -a

/etc/modules-load.d/docker.conf
vxlan
xt_ipvs

I hope Linode will enable them in future to avoid this complexity. Those two modules are needed for Docker Swarm

@gleez:

@caker:

@willemdh:

The biggest drawback of Linode imho is their use of limited custom kernels. For example on CentOS 7 it's not possible to enable SELinux and you can have issue with Docker as CONFIGNETFILTERXTMATCHIPVS is missing…
Most, if not all of our distro templates, can be booted with the distribution's kernel, straight out of the box. Here's how:

Deploy CentOS, click on your Linode's configuration profile, set the kernel to GRUB, save, and boot. Done. You now have SELinux and all of the other patches distros apply to their kernels.

-Chris

Other way is to build them as modules and upload only the modules and run modprobe. its far easiest than the grub. On Centos in Linode these 2 modules are not enabled.

CONFIG_NETFILTER_XT_MATCH_IPVS=m
CONFIG_VXLAN=m

Download the kernel version of your linode from kernel.org and get the linode kernel config file and enable the above said as modules "vlan.ko & xt_ipvs.ko" build and move them to the

/usr/lib/modules/KERNEL_VERSION
depmod -a

/etc/modules-load.d/docker.conf
vxlan
xt_ipvs

I hope Linode will enable them in future to avoid this complexity. Those two modules are needed for Docker Swarm

Other way is to build them as modules and upload only the modules and run modprobe.

LOL Oh, you're serious? I haven't done stuff like that in Linux since the early to mid 1990's.

Why not? It's as simple as ever.

I was having issues with Docker Swarm in Linode.

Changing the kernel resulted to be quite easy in the Dashboard interface. And it solved my issues.

The full steps with screenshots are in this comment: https://github.com/docker/machine/issue … -341850111">https://github.com/docker/machine/issues/2753#issuecomment-341850111