I run FreeNAS (FreeBSD based) on HP Microservers. ECC RAM, 4 drive bays, ...
The older Gen8 boxes Just Work.
With FreeBSD, the newer Gen10 boxes would hang the first time you boot, you need to pause it and set the hw.pci.realloc_bars loader variable to 1. Haven't tried a new install recently.
Details here: https://www.virten.net/2017/10/fix-for-freenas-on-hpe-micros...
Sana Biotechnology | Engineered cells as medicines | sana.com | San Francisco, Seattle, Cambridge | Full-time | Computational Engineer
We believe we are entering a new era of medicine. The ability to modify genes and use cells as medicines provides new tools to meaningfully change the outcome of many human diseases. Three aspirations drive Sana: repair and control genes in any cell; replace any cell in the body; and tear down barriers to accessing out therapies.
The Computational Engineering team has several openings for engineers to help us build out our production infrastructure. Paraphrasing Russ Cox's definition of software engineering (https://research.swtch.com/vgo-eng), our team is what happens to computational biology, cloud infrastructure, and lab automation when you add time and other teams. Beyond being a polyglot coder (Python, R, Nextflow, Terraform), we're looking for people who can have productive discussions about version control strategies, test frameworks, deployment strategies, and documentation tools and then get behind the team's decisions and move things forward.
> Databases are made to execute queries, not to install them.
But being able to freely/quicly stand up database servers and quickly create/drop databases makes development and testing much simpler and more reliable.
Given the question: "How do you know that deploying this thing will work?"
- When it's quick/legal to stand up fresh servers and create databases, the answer can be "I tested it, just now, and it works."
- Otherwise you end up in "I read through it and it looks good" or perhaps "We tried most of it on the test instance last week before the other team started using it."
Actually, the whole "create database" is misleading when comparing the two.
For Oracle, a "database" is the a server instance; you create the database when you install the software (without creating a "database" you don't actually have anything running). For postgres, a database is just a level of data organization/segregation.
In an oracle instance you only have a single database. The equivalent of the postgres "database" would be "user/schema" in Oracle.
Not at all. Because Oracle does not have multiple databases per instance does not equal a PostgreSQL database to an user in Oracle. On the contrary, it means PostgreSQL is way more flexible, because there we have and databases, and users and schemas as ISO meant it.
[Spack](https://spack.io) uses patchelf and additional tooling to relocate it's binary packages to other paths. It generally works, although one has to special case things that burn their install directory into their builds (e.g. Perl).
> But most importantly, all builds are completely reproducible.
This is only true if the commands that the recipe executes are reproducible. If someone's pulling packages from PyPi or C[PR]AN or ... w/out locking the versions, all bets are off.
This is one of my biggest beefs with many containerization sales pitches...
Want to buy some pens?