Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Cloud Platform’s new interactive CLI

cloudplatform.googleblog.com

Post reply on HN
Print view View original

71–79 of 79 posts

Re: Google Cloud Platform’s new interactive CLI

#71

Post by manigandham »

wetha wrote: post #58
manigandham wrote: post #55

Earlier quoted context omitted.

That is an understandably automatic control feature to keep the DB instance running well since PostgreSQL doesn't handle connection scaling well. The recommendation is to use pgbouncer, which you can also combine with the GCP cloudsql proxy into a separate container and use that way. We deploy that onto GKE as a service and have our apps use that. Some setup required but cleaner overall.

I assume CloudSQL is google’s alternative to AWS RDS. Less of an excuse to not make the setting user configurable when the competition (AWS) does.

There's no excuse, it's about a different philosophy.

AWS gives you lots of tuning controls and complexity while GCP tends to hide most of it with easier scaling and performance. It'll vary with individual products themselves but it looks like Cloud SQL is designed with that general outlook.

None of the clouds are perfect, the only viable strategy is to use the best parts of them all that fit your needs.

Re: Google Cloud Platform’s new interactive CLI

#72

Post by rifung »

optimusclimb wrote: post #28

I wish they would spend more time finishing the halfway done projects they've started (and fully documenting them), rather than continue to launch new ones. For instance...Google CloudSQL - Great! Postgres - Beta...Postgres from AppEngine python...err, we'll get around to it, maybe. Just giving one example, but my point is - finish what you've started before making new. I think recent articles I've read about launchi…

> I wish they would spend more time finishing the halfway done projects they've started (and fully documenting them), rather than continue to launch new ones.

Perhaps I am reading too much into your comment but you make it seem as though releasing other products slows down the development of those projects that you consider halfway done.

This is definitely not the case; it's not as though the engineers who were working on CloudSQL or AppEngine decided to start working on a CLI instead.

> I think recent articles I've read about launching being the track to promotion explain some of the state of things within GCP.

There are certainly issues with promotion but if anything I'd imagine getting a highly requested customer feature like Postgres out of beta would be awesome for promotion so I don't think that's the underlying issue here.

Re: Google Cloud Platform’s new interactive CLI

#73

Post by shankun »

bradhe wrote: post #53

This is awesome, interactive CLIs are great for simple use cases. I hope they continue to have support for non-interactive scenarios so that automation can continue to work (apologies if I missed that in the article).

Thanks. Yes, this is completely additive to the existing SDK.

Re: Google Cloud Platform’s new interactive CLI

#74

Post by kirubakaran »

shankun wrote: post #70
psychometry wrote: post #22

Still requires Python 2.7, right? What year is it again?

Thanks for the feedback. We are actively working on Python 3 support. Stay tuned!

Are you sure? App Engine Standard Environment has had that on the "roadmap" forever. Almost 10 years in fact.

https://issuetracker.google.com/issues/35876441

http://www.googblogs.com/enhancing-the-python-experience-on-...

Re: Google Cloud Platform’s new interactive CLI

#75

Post by e12e »

colemickens wrote: post #45
algorithmsRcool wrote: post #19

Earlier quoted context omitted.

Azure has one too https://docs.microsoft.com/en-us/azure/cloud-shell/overview

An interactive CLI (this) is not the really at all the same thing as a JavaScript TTY connected to a container (Cloud Shell). (Though, Google does also have a Cloud Console that is comparable to Azure's Cloud Shell.)

  python3 -m venv az.env
  source ./az.env/bin/activate
  pip install azure-cli
  az --help
Although ms has a strange fetish for complicated installation, one might prefer running it from docker:

https://docs.microsoft.com/en-us/cli/azure/install-azure-cli...

https://pypi.python.org/pypi/azure-cli

Re: Google Cloud Platform’s new interactive CLI

#77

Post by sandGorgon »

manigandham wrote: post #55
sandGorgon wrote: post #43

Earlier quoted context omitted.

+100 - i was waiting for them to launch Postgres prod. It just doesnt go live. Even worse, they have had trouble in exposing max_connections as configurable PostgreSQL flag ( https://issuetracker.google.com/issues/37271935 )

That is an understandably automatic control feature to keep the DB instance running well since PostgreSQL doesn't handle connection scaling well. The recommendation is to use pgbouncer, which you can also combine with the GCP cloudsql proxy into a separate container and use that way. We deploy that onto GKE as a service and have our apps use that. Some setup required but cleaner overall.

I'm afraid all of you are getting it wrong. The setting is hardcoded to 100.

Check this out - https://issuetracker.google.com/issues/37271935#comment39 and then the update https://issuetracker.google.com/issues/37271935#comment49

This is not a feature. It is a bug. It needs to be at par with RDS.

Re: Google Cloud Platform’s new interactive CLI

#78

Post by manigandham »

sandGorgon wrote: post #77
manigandham wrote: post #55

Earlier quoted context omitted.

That is an understandably automatic control feature to keep the DB instance running well since PostgreSQL doesn't handle connection scaling well. The recommendation is to use pgbouncer, which you can also combine with the GCP cloudsql proxy into a separate container and use that way. We deploy that onto GKE as a service and have our apps use that. Some setup required but cleaner overall.

I'm afraid all of you are getting it wrong. The setting is hardcoded to 100. Check this out - https://issuetracker.google.com/issues/37271935#comment39 and then the update https://issuetracker.google.com/issues/37271935#comment49 This is not a feature. It is a bug. It needs to be at par with RDS.

As actually stated in the comment you linked to, it is not hardcoded but scales with the instance size to protect against an out-of-memory condition. The lack of it being user configurable is a separate issue, and not a bug but rather a design detail of their managed service.

Re: Google Cloud Platform’s new interactive CLI

#79

Post by colemickens »

bjd145 wrote: post #63
colemickens wrote: post #45

Earlier quoted context omitted.

An interactive CLI (this) is not the really at all the same thing as a JavaScript TTY connected to a container (Cloud Shell). (Though, Google does also have a Cloud Console that is comparable to Azure's Cloud Shell.)

Cloud Shell has an interactive mode - https://docs.microsoft.com/en-us/cli/azure/interactive-azure...

That's the CLI (it's right there in the title of the article)... which yes, can be run from the Cloud Shell, as the Cloud Shell is just a bash docker container that has the CLI pre-installed, etc.
Post reply on HN