111–120 of 126 posts
Earlier quoted context omitted.
everything works great on gitlab, until the moment you had to migrate. Landmine experience in issue lists
Hi, Community Advocate from GitLab here. Could you please reference what issues you are experiencing? We'd love to follow up on it. Also, if you want to write the details, it would be great to open an issue https://gitlab.com/gitlab-org/gitlab-ce/issues . Thanks in advance.
https://gitlab.com/gitlab-org/gitlab-ce/issues/27217
Something like this. When I fixed the VERSION manually, there are other errors, as expected.
However the peculiar thing is the errors are not idempotent. Somethings there's some postgres wrong column error, other times it says you can't import the project because you can't have hyphens in project names. (which I don't)
Migration is hard, considering everything can be linked in Gitlab.
Earlier quoted context omitted.
>> Our main path business path gets about 60,000 reqs min. For that, sure AWS Lambda would never compete. I'm curious about this statement because I'm currently working on a project where the intent is to port a legacy app to AWS Lambda. The legacy app is currently distributed across 96 VMs and handles ~ 50K reqs/min during normal times but can run into ~ 3M reqs/min during high demand. Are you saying AWS Lambda can…
I think he/she meant that Lambda wouldn't compete on pricing (as opposed to on performance).
I didn't read the article but something tells me that "serverless" involves a server of some kind ...
Serverless functions are a terrible idea. Way too restrictive and proprietary. Kubernetes is the future. Amazon throwing money behind the Serverless trend is only delaying the inevitable universal success of a standardized, open source container orchestration platform.
Your argument against serverless functions holds for AWS Lambda, but this Gitlab feature is based on Knative. That's an open source serverless platform based on Kubernetes. I think all money Amazon is throwing at serverless is to build a foundation to ultimately transform all their "managed" services into a serverless form. They already released serverless RDS ( https://aws.amazon.com/rds/aurora/serverless/ ).
I know what they mean with serverless, so that's not it.
- is this tied to CI in any way so stuff can get tested via knative?
- is this CI for functions to be deployed (via OpenFaaS or Lambda)?
- is this just a frontend for serverless backends?
I'm totally lost, I use GitLab as a hosted amount of git repos, with inclusion of CI runners, so maybe that's the wrong angle of approach? Which _problem_ does it solve? Is it to make using serverless easier? If I wanted to use 'functions' would I first have to install GitLab? Why would I use a code hosting platform for that?
Earlier quoted context omitted.
Seriously, VPS hosts are so far ahead of the cloud when it comes to cost/resource ratio. I can get a 4-core 4GB 120GB SHDD instance for ~$2/month. https://lowendbox.com/blog/hostedsimply-4gb-ram-ssd-cached-v... EDIT: cheaper even, $1.58/month: https://lowendbox.com/blog/n3servers-vps-hosting-and-hybrid-...
Low-cost VPSs are great, but their uptime is usually garbage. I myself run almost everything on a 9€/mo Contabo box (6c, 16GB) and while it's nice and powerful, it gets randomly rebooted way more often than acceptable (and I've heard similar about other hosts). For the "I'll get an angry phone call if the app is down for half an hour at 4 am" category of projects, the cost of a reliable enough VPS comes very close to…
I've read the announcement now twice but I can't make out what this is actually good for. I know what they mean with serverless, so that's not it. - is this tied to CI in any way so stuff can get tested via knative? - is this CI for functions to be deployed (via OpenFaaS or Lambda)? - is this just a frontend for serverless backends? I'm totally lost, I use GitLab as a hosted amount of git repos, with inclusion of CI…
I've read the announcement now twice but I can't make out what this is actually good for. I know what they mean with serverless, so that's not it. - is this tied to CI in any way so stuff can get tested via knative? - is this CI for functions to be deployed (via OpenFaaS or Lambda)? - is this just a frontend for serverless backends? I'm totally lost, I use GitLab as a hosted amount of git repos, with inclusion of CI…
Overall, this is trying to give more support for pushing functions to Kubernetes using Knative as the method. I believe that there will be some support built in to GitLab for supporting Knative functions. I also know that this already works with OpenFaaS and OpenFaaS cloud, whereas Lambda normally is not deployed directly to Kubernetes, although you can use GitLab CI to do this.
Earlier quoted context omitted.
let me guess, you don't have any experience in ops? 1) Scaling doesn't really require more work. It needs a bigger investment because a hardware hypervisor costs significantly more than a vm... after all, that hard metal can host tens of VMs 2) you still need to manage your linux system and OS if you're buying a VM... the only thing you don't need to worry about is hardware. So, a faulty hard drive, hypervisor failov…
I would dissent from #3 in that containers also have the inherent advantage of being able to scale and start quickly. A full VM takes time to boot and run through whatever setup/initialization needs to happen at the OS level, where a container just needs to copy/deploy and start. In many cases it's an additional abstraction, but there are advantages beyond just better hardware utilization.