``` sudo dd if=/dev/zero of=/tmpswap bs=4096 count=1M && sudo chmod 0600 /tmpswap && sudo chown root:root /tmpswap && sudo mkswap /tmpswap && sudo swapon /tmpswap ```
HashiCorp IPO today
81–90 of 206 posts
Re: HashiCorp IPO today
#82Don’t understand why anyone would need their cloud products. Who needs Terraform or Nomad or Vault as a service?
They're like Docker for DevOps? > ...a common confusion is multi-cloud vs. multi-vendor services. The latter is way more common, especially at smaller companies. Tools like Terraform are often touted as "multi-cloud" and people ask questions like "Why would I use Terraform if I use only AWS?" And the easy answer to that is tools like Terraform allow you to manage anything with an API as code. For example: do you want…
Where i'm at it has been SQL Server for the last 12 years and now Azure for cloud services.
It's highly unlikely that will change for the next 10 years.
And almost equally unlikely that Terraform will be used instead of ARM templates and Bicep.
Re: HashiCorp IPO today
#83Earlier quoted context omitted.
I'll pick TFE because Nomad doesn't exist as a service. Audit trails, authorization, authentication, sentry rules (don't allow devs to open a public port for example), centralized automation (plans executed in order), dedicated build agents. That's a few reasons why we used TFE at Capital One.
Curious -- is “used” past-tense because you're no longer at Capital One, or because Capital One stopped using them?
Re: HashiCorp IPO today
#84Earlier quoted context omitted.
How does a bump help employees/founders? Don't they have some fixed number of shares?
The employees' shares are tax based on the IPO price, not the price at which shares beginning trading. So with a large bump (like 100% on Snowflake for example), you defer a lot of tax to the future. And if you hold out 1 year until selling, you change a lot of that gain from income into long term capital gains (which has a lower tax rate)
Re: HashiCorp IPO today
#85Their symbol is hcp instead of hash, what a shame.
I would have preferred HCL
You made life as a cloud infra beard better for a while, and I wish you all success going onwards.
Re: HashiCorp IPO today
#86Earlier quoted context omitted.
What makes you think they will enter monitoring next?
They have some many parts of spinning up/change the infrastructure (Terraform), connect the services (Consul), run the apps (Nomad) but not their own way to tell you how well they do. Also monitoring is quite sticky and high margin. I think it makes sense but have no special insight.
Re: HashiCorp IPO today
#87Re: HashiCorp IPO today
#88Re: HashiCorp IPO today
#89Earlier quoted context omitted.
They're like Docker for DevOps? > ...a common confusion is multi-cloud vs. multi-vendor services. The latter is way more common, especially at smaller companies. Tools like Terraform are often touted as "multi-cloud" and people ask questions like "Why would I use Terraform if I use only AWS?" And the easy answer to that is tools like Terraform allow you to manage anything with an API as code. For example: do you want…
Multi-cloud is a nice idea, but not for everyone. Where i'm at it has been SQL Server for the last 12 years and now Azure for cloud services. It's highly unlikely that will change for the next 10 years. And almost equally unlikely that Terraform will be used instead of ARM templates and Bicep.
k8s is a nice way to get there, if your k8s is running on gcp, aws, or azure it doesn't really impact your pipelines or process at all.
Things are harder at the bleeding edge, I'm working atm on a site that's all in on aws lambda with server less framework and aurora, kinesis and such, to the point where a migration would mean a rewrite tbh.. And that's alright for them, they're ok with their cloud partner.. And it's cheap too..
Re: HashiCorp IPO today
#90Don’t understand why anyone would need their cloud products. Who needs Terraform or Nomad or Vault as a service?
Terrraform is declarative and describes the end state of what you want your system to look like. Executing terraform on anything other than blank slate requires that the deployment needs to know state of the current system. You can store that state yourself, or you can have HCP store it for you as a service