DOCSLIB.ORG

Functional Programming and Nix for Reproducible, Immutable Infrastructure

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Functional Programming and Nix for Reproducible, Immutable Infrastructure Functional programming and Nix for reproducible, immutable infrastructure Nix Functions and packaging Agenda Functions and operating systems Development shells Docker without Dockerfiles Nix Functional programming for infrastructure Nix History Functions: same input, same output 12th century “Nix: A Safe and Policy-Free System for Software History Deployment” Eelco Dolstra 2004 “NixOS: A Purely Functional Linux Support Distribution” Eelco Dolstra 2008 Alternatives I started using it 2014 Use cases Nix Support Nix, programming language Nix, package manager History ● Linux ● macOS ● WSL & WSL2 Support NixOS, Linux operating system Alternatives NixOps, deployment tool Use cases Nix Alternatives Divergent Manual configuration Shell scripts History apt, yum, pacman Convergent Support Puppet, Chef, Ansible Alternatives Congruent Docker Guix Use cases Divergent State Time Convergent State Time Congruent State Time Nix Use cases ● Cross-compiling ● Virtual machines (Linux, Windows) ● Automated GUI/service tests History ● chroot environments ● AppImage packages ● RPM and Deb packages Support ● Continuous integration ● Development shells Alternatives ● Docker images Use cases Package management As functions Package management Package Build inputs Dependencies Sources Packages Configuration Build outputs Expressions Artifacts Derivations Build definitions Steps to create artifact from inputs Outputs ● Dependencies ● Build steps ● Artifact Package B Package A Package C Package D Package management Expressions Nix programming language only has expressions Build inputs are values Packages Use functions to define the steps Expressions Derivations Outputs Package management mkDerivation { Packages name = "hello-file"; buildCommand = " Expressions echo 'Hello world' > $out "; Derivations } Outputs Package management mkDerivation { name = "hello-file"; Packages buildInputs = [ hello ]; buildCommand = " Expressions hello > $out "; Derivations } Outputs Package management Packages runCommand "hello-file" { buildInputs = [ hello ]; Expressions } "hello > $out" Derivations Outputs Package management Derivations A tree representing the build to run No more functions, only serialised values Packages nix-instantiate Expressions Derivations Outputs Package management Packages $ nix-instantiate hello-file.nix Expressions /nix/store/sn8i-hello-file.drv Derivations Outputs Package management "outputs": { "out": { "path": "/nix/store/jr4s-hello-file" Packages } } Expressions "inputSrcs": [ Derivations "/nix/store/9krl-default-builder.sh" ] Outputs Package management "inputDrvs": { "/nix/store/5gpb-stdenv-linux.drv": [ "out" ], Packages "/nix/store/ccna-bash-4.4-p23.drv": [ "out" Expressions ], "/nix/store/sddw-hello-2.10.drv": [ Derivations "out" ] Outputs } Package management "platform": "x86_64-linux" "builder": Packages "/nix/store/b9p7-bash-4.4-p23/bin/bash" Expressions "args": [ "-e", Derivations "/nix/store/9krl-default-builder.sh" ] Outputs Package "env": { management "buildCommand": "hello > $out", "buildInputs": "/nix/store/gdh8-hello-2.10", "builder": Packages "/nix/store/b9p7-bash-4.4-p23/bin/bash", "name": "hello-file", Expressions "out": "/nix/store/jr4s-hello-file", "outputs": "out", Derivations "passAsFile": "buildCommand", "stdenv": "/nix/store/r23m-stdenv-linux", "system": "x86_64-linux" Outputs } Package management Outputs Files stored at hash of the derivation Purity is same derivation should give same output Packages Can be checked for purity by building many times Expressions Or we can use a chroot Derivations Caching builds becomes trivial nix-store --realise Outputs Package management Packages $ nix-store --realise /nix/store/sn8i-hello-file.drv /nix/store/jr4s-hello-file Expressions $ cat /nix/store/jr4s-hello-file Hello, world! Derivations Outputs Operating systems As functions Operating systems { services.openssh.enable = true; virtualisation.docker.enable = true; Configuration users.extraUsers.brian = { Generations uid = 1000; extraGroups = [ "wheel" "docker" ]; }; } Operation systems Generations If we change configuration we build a new profile A profile contains kernel, systemd configuration, Configuration /etc files and a directory to be placed on $PATH Profiles are registered as generations Generations Old generations can be collected Generations are shown at boot Image; MichaelLindman (level1techs.com) Development shells Using functions Development shells $ nix-shell -p python $$ which python /nix/store/8818-python-2.7.11/bin/python Usage $ cd myproject Configuration $ nix-shell ## install direnv $ cd myproject Development mkDerivation { shells name = "amkt-env"; buildInputs = [ nodejs-8_x Usage yarn jdk Configuration which curl git flow ] ++ optionals isLinux [ firefox ]; } Docker as functions No Dockerfiles Docker as functions FROM alpine Dockerfile RUN apk add --update cowsay Nix CMD ["/bin/cowsay", "hello"] EXPOSE 8080 Docker as functions Dockerfile What’s the version of Cowsay? What’s the version of Perl? Dockerfile What’s the version of libc? Nix What’s the version of Alpine? Docker as functions dockerTools.buildImage { name = "cowsay-hello"; contents = [ cowsay ]; fromImage = alpine; Dockerfile config = { Cmd = [ "/bin/cowsay" "hello" ]; Nix ExposedPorts = { "8080/tcp" = {}; }; }; } Functional infra One tool for CI, dev and prod. Known versions of everything. All reproducible. Thank you! Functions Simplicity Same inputs always give same output Can always inline and extract expressions Simplicity Evaluation is substitution Reuse Functions Reuse If we see same code, we can always extract it out Using code is just using functions Simplicity Reuse Agenda item 1 Agenda item 2 Agenda Agenda item 3 Agenda item 4 Agenda item 5 Agenda item 6 Highlight sections As you introduce them Agenda Hold *shift* and drag the bar Use *Distribute* tools Found under *Arrange* In the menu above Talk Title Subtitle Talk Title Subtitle Alternate agenda option Alternate agenda option Chapter Titles Chapter subtitles should be two lines or less super awesome things This is a big statement slide. Use dark background for bolder points. This is a big statement slide. Use dark background for bolder points. This is a big statement slide. Use light background for lighter points. This is a big statement slide. Use dark background for bolder points. This is a reference point slide. Likely will be from a site, book, talk, etc. Source Book, Source Author, Other Relevant Info This is a reference point slide. Likely will be from a site, book, talk, etc. Source Book, Source Author, Other Relevant Info This is a quote slide. Keep it tweetable. AUTHOR If you can’t explain it simply, you don’t understand it well enough. ALBERT EINSTEIN Use when Can be used explaining as pro/con, two sides of hypothesis/ a point finding, etc. List out List out The qualities The qualities of the two of the two Different sides Different sides Use another Use another Slide type Slide type If you want to point out If you want to point out The similarities The similarities Talking point Big statement Supporting info for talking point. with support Use no more than two lines. Talking point Manage audience focus by placing bar beneath talking point. Talking point Stay consistent with using the light or dark throughout the related big statement. Spacing Big statement Hold down *Shift* to drag when moving the bar to make sure it with support stays properly aligned. Please remember Using a lot of text on slides is like reading your notes to your audience. Not presenting. Less is more If you don’t need any of the points, don’t use them. We don’t believe in filler, baby! Deeper info slide title Talking point This is arguably the most text that should ever be on one of your presentation slides. Bold text Are they here to read or be engaged? Normal text Don’t ask your audience to read/listen to your notes and call it a presentation. Can send them a document. Move marker Don’t need a third point? Change text style Go ahead and delete! Code sample "contentBylineItems": [ with headers { "context": "addon", "target": { "type": "inlinedialog" }, "tooltip": { "value": "Approvals" }, Bold text "icon": { "url": "/images/approval.png" }, Normal text "name": { "value": "Page Approvals" }, "key": "byline-item", Move marker "url": "/approvals?contentId={content.id}" Change text style } ] Use illustrations from the Graphic Assets Deck to support point. Use illustrations from the Graphic Assets Deck to support point. Keep your big points short & sweet Talking point Supporting text should be brief and no longer than 4 lines. Limit one talking point and image per slide. Talking point Illustrations Separators Utilize spot illustrations Use minimal grey bar to from our design site. separate points/illustrations. Talking point Usage Remember Don’t Obsess These slides have proven Keep the text light and focus The illustrations need only to be versatile in use. on presenting your points. to hint at your point. Talking point Headline 3 Rehearse Focus No worries Subtext type size is Rely on rehearsing Use 4 points It’s OK if the subtext optimized at 14 pt. your voiceover maximum to keep lengths differ. rather than writing. focus. Before After Use to discuss points about how Celebrate how fantastic things are now something worked before. that you’ve implemented changes. Short title, 2 lines max Talking point Supporting text should be brief and no longer than 4 lines. Limit one talking point and image per slide. Point 1 Point 2 Point 3 Point 4 Illustrations > text Use illustrations to represent ideas rather than always relying on
Load more

Recommended publications
  • Github: a Case Study of Linux/BSD Perceptions from Microsoft's
    1 FLOSS != GitHub: A Case Study of Linux/BSD Perceptions from Microsoft’s Acquisition of GitHub Raula Gaikovina Kula∗, Hideki Hata∗, Kenichi Matsumoto∗ ∗Nara Institute of Science and Technology, Japan {raula-k, hata, matumoto}@is.naist.jp Abstract—In 2018, the software industry giants Microsoft made has had its share of disagreements with Microsoft [6], [7], a move into the Open Source world by completing the acquisition [8], [9], the only reported negative opinion of free software of mega Open Source platform, GitHub. This acquisition was not community has different attitudes towards GitHub is the idea without controversy, as it is well-known that the free software communities includes not only the ability to use software freely, of ‘forking’ so far, as it it is considered as a danger to FLOSS but also the libre nature in Open Source Software. In this study, development [10]. our aim is to explore these perceptions in FLOSS developers. We In this paper, we report on how external events such as conducted a survey that covered traditional FLOSS source Linux, acquisition of the open source platform by a closed source and BSD communities and received 246 developer responses. organization triggers a FLOSS developers such the Linux/ The results of the survey confirm that the free community did trigger some communities to move away from GitHub and raised BSD Free Software communities. discussions into free and open software on the GitHub platform. The study reminds us that although GitHub is influential and II. TARGET SUBJECTS AND SURVEY DESIGN trendy, it does not representative all FLOSS communities.
    [Show full text]
  • Debian \ Amber \ Arco-Debian \ Arc-Live \ Aslinux \ Beatrix
    Debian \ Amber \ Arco-Debian \ Arc-Live \ ASLinux \ BeatriX \ BlackRhino \ BlankON \ Bluewall \ BOSS \ Canaima \ Clonezilla Live \ Conducit \ Corel \ Xandros \ DeadCD \ Olive \ DeMuDi \ \ 64Studio (64 Studio) \ DoudouLinux \ DRBL \ Elive \ Epidemic \ Estrella Roja \ Euronode \ GALPon MiniNo \ Gibraltar \ GNUGuitarINUX \ gnuLiNex \ \ Lihuen \ grml \ Guadalinex \ Impi \ Inquisitor \ Linux Mint Debian \ LliureX \ K-DEMar \ kademar \ Knoppix \ \ B2D \ \ Bioknoppix \ \ Damn Small Linux \ \ \ Hikarunix \ \ \ DSL-N \ \ \ Damn Vulnerable Linux \ \ Danix \ \ Feather \ \ INSERT \ \ Joatha \ \ Kaella \ \ Kanotix \ \ \ Auditor Security Linux \ \ \ Backtrack \ \ \ Parsix \ \ Kurumin \ \ \ Dizinha \ \ \ \ NeoDizinha \ \ \ \ Patinho Faminto \ \ \ Kalango \ \ \ Poseidon \ \ MAX \ \ Medialinux \ \ Mediainlinux \ \ ArtistX \ \ Morphix \ \ \ Aquamorph \ \ \ Dreamlinux \ \ \ Hiwix \ \ \ Hiweed \ \ \ \ Deepin \ \ \ ZoneCD \ \ Musix \ \ ParallelKnoppix \ \ Quantian \ \ Shabdix \ \ Symphony OS \ \ Whoppix \ \ WHAX \ LEAF \ Libranet \ Librassoc \ Lindows \ Linspire \ \ Freespire \ Liquid Lemur \ Matriux \ MEPIS \ SimplyMEPIS \ \ antiX \ \ \ Swift \ Metamorphose \ miniwoody \ Bonzai \ MoLinux \ \ Tirwal \ NepaLinux \ Nova \ Omoikane (Arma) \ OpenMediaVault \ OS2005 \ Maemo \ Meego Harmattan \ PelicanHPC \ Progeny \ Progress \ Proxmox \ PureOS \ Red Ribbon \ Resulinux \ Rxart \ SalineOS \ Semplice \ sidux \ aptosid \ \ siduction \ Skolelinux \ Snowlinux \ srvRX live \ Storm \ Tails \ ThinClientOS \ Trisquel \ Tuquito \ Ubuntu \ \ A/V \ \ AV \ \ Airinux \ \ Arabian
    [Show full text]
  • Free Gnu Linux Distributions
    Free gnu linux distributions The Free Software Foundation is not responsible for other web sites, or how up-to-date their information is. This page lists the GNU/Linux distributions that are ​Linux and GNU · ​Why we don't endorse some · ​GNU Guix. We recommend that you use a free GNU/Linux system distribution, one that does not include proprietary software at all. That way you can be sure that you are. Canaima GNU/Linux is a distribution made by Venezuela's government to distribute Debian's Social Contract states the goal of making Debian entirely free. The FSF is proud to announce the newest addition to our list of fully free GNU/Linux distributions, adding its first ever small system distribution. Trisquel, Kongoni, and the other GNU/Linux system distributions on the FSF's list only include and only propose free software. They reject. The FSF's list consists of ready-to-use full GNU/Linux systems whose developers have made a commitment to follow the Guidelines for Free. GNU Linux-libre is a project to maintain and publish % Free distributions of Linux, suitable for use in Free System Distributions, removing. A "live" distribution is a Linux distribution that can be booted The portability of installation-free distributions makes them Puppy Linux, Devil-Linux, SuperGamer, SliTaz GNU/Linux. They only list GNU/Linux distributions that follow the GNU FSDG (Free System Distribution Guidelines). That the software (as well as the. Trisquel GNU/Linux is a fully free operating system for home users, small making the distro more reliable through quicker and more traceable updates.
    [Show full text]
  • A Deep Dive Into Nixos: from Configuration to Boot CS5250: Advanced Operating Systems
    A Deep Dive into NixOS: From Configuration To Boot CS5250: Advanced Operating Systems Chen Jingwen A0111764L National University of Singapore Abstract Mature operating systems (e.g. Windows, Fedora) are inherently stateful and imperative, adding layers of complexity by installing or upgrading software. This causes side-effects such as breaking existing software while upgrading shared libraries without maintaining backwards compatibility. NixOS is a Linux distribution designed to be purely functional, where building everything from the kernel to the web browser has no side- effects. System configuration files are written in the Nix language, a lazy functional domain specific language with a declarative syntax, and software packages are managed by the Nix package manager. A distinct feature of NixOS is the ability to declare the configuration of an entire system in one file, which is then used to build a bootable system deterministically. This report gives an overview and the motivations of NixOS, and a deep dive into how the configuration of an operating system can be derived from a single file. 1 Contents 1 Introduction 4 2 Motivation 5 2.1 Multiple versions . 5 2.2 Destructive updates . 5 2.3 Rollback difficulties . 6 2.4 Non-atomic upgrades . 6 2.5 Inability to reproduce builds . 6 3 NixOS Architecture 7 3.1 Package specifications and the Nix expression language . 7 3.1.1 Nix expression language . 8 3.1.2 Derivations . 9 3.2 Nix store . 9 3.2.1 Cryptographic hash . 9 3.2.2 Source to binary deployment . 10 3.2.3 Nix database . 10 3.3 Nix package manager .
    [Show full text]
  • Nix(OS) - Revolutionizing Packaging and Configuration Management!
    Nix(OS) - Revolutionizing packaging and configuration management! The Purely Functional Linux Distribution 1 Before we begin (FYI) Ask questions at any time Please ask lots of questions :) The slides contain some redundancy There are a few optional slides at the end Please give me feedback Louder Faster/slower More/less details Etc. 2 About me Michael Weiss aka. primeos Computer science student at the University of Tübingen I love free soware, etc. First nixpkgs commit: 2016-10-05 I maintain ~41 packages and ~3 modules (2018-06-08) I also love privacy (i.e. no more details :P) Email: [email protected] (#privacy) 3 Main components Nix (package manager) Nixpkgs (Nix packages collection) NixOS (operating system) NixOps (DevOps / cloud deployment tool) 4 Nix* ISO/OSI model NixOps NixOS Nixpkgs Nix 5 Other tools Hydra (Nix based continuous build system) Disnix (distributed services deployment) PatchELF (change dynamic linker and RPATH) {cabal,go,node,pip,python,pypi,composer,hex,bower,vim,...}2 6 History Started as a research project (with funding) First paper in 2004 (many will follow) Nix package manager developed by Eelco Dolstra as part of his PhD research (~2003) First NixOS prototype developed by Armijn Hemel as his master's thesis project Hydra developed as part of the LaQuSo Buildfarm project 7 Timeline 2003: init (research begins) 2007: NixOS becomes usable + x86_64 support 2008: Website moved to nixos.org 2009: Nix logo + Nix(OS) build on Hydra 2011: Migration from Subversion to Git(Hub) 2013: Switch from Upstart to systemd +
    [Show full text]
  • Porteus Kali 1.0.6
    DISTROHOPPER DISTROHOPPER We’ve tapped GCHQ’s communications to find out what’s going on in distro land. Porteus Lightning-fast live Linux. orteus is a distribution designed for running directly off a USB stick. Big Pdeal – almost every distribution can do that these days, so you may wonder if there’s still room for a distro like Porteus. However, there’s plenty that’s unusual about it. Porteus doesn’t have a download link like you may expect, but a build service where you can customise your own version of Porteus. You can select things like the desktop environment, the web browser and word processor, and in the Advanced options you can set things like the system passwords and boot behaviour. The second unusual thing about Porteus is how quickly it boots. On our test system, Porteus Mate got from Grub to the desktop in under 10 seconds, and this was in a Porteus Kiosk has a bounty scheme where you can donate money towards certain features. virtual machine. The VM was allocated two cores of the i7 processor, but to put it into distro, it took just 15 seconds. On the down targeted very firmly at people who want context, OpenSuse took just over a minute. side there is quite a limited choice for the a minimal live distro. Of course, this isn’t This speed is incredible for a live distro. We applications you can install, and there’s really a problem, because there are loads of ran the test again with the KDE version of little else other than those you select in the alternative options for people who want a Porteus, and even with the heavyweight build system.
    [Show full text]
  • Nixos: Järjestelmäkonfiguraation Hallintaan Erikoistunut Linux-Jakelu
    Kalle Kumpulainen NIXOS: JÄRJESTELMÄKONFIGURAATION HALLINTAAN ERIKOISTUNUT LINUX-JAKELU Informaatioteknologian ja viestinnän tiedekunta Kandidaatintyö Toukokuu 2019 i TIIVISTELMÄ Kalle Kumpulainen: NixOS: Järjestelmäkonfiguraation Hallintaan Erikoistunut Linux-jakelu English title: NixOS: A Linux Distribution Specialized in System Configuration Management Kandidaatintyö Tampereen yliopisto Tieto- ja sähkötekniikka Toukokuu 2019 Työn analyysin kohteena oli hollantilaisen Eelco Dolstran tutkimusprojektina alkanut ja sittem- min väitöskirjaksi asti päätynyt projekti NixOS, joka on järjestelmäkonfiguroinnin hallintaan ja oh- jelmistojen jakeluun liittyvien ongelmakohtien ratkaisemiseen erikoistunut Linux-pohjainen käyt- töjärjestelmä. Tämän työn tarkoituksena oli selvittää tarkemmin mitä nämä ongelmakohdat tosia- siassa ovat, millaisilla ratkaisuilla niitä on NixOS:ssä ratkaistu ja millaisia eroavaisuuksia NixOS si- sältää verrattuna muihin suosittuihin Linux-käyttöjärjestelmiin. Tämän lisäksi tavoitteena oli myös selvittää millaisiin käyttökohteisiin NixOS sopii. Työssä perehdyttiin aluksi tavallisten Linux-jakeluiden rakenteeseen, josta erityisesti pakettien- hallintaan, koska se on NixOS:n poikkeuksellisin ja tärkein komponentti. Näillä tiedoilla siirryttiin NixOS:n esittelyyn, josta käytiin läpi sen historiaa, rakennetta ja erityisiä ominaisuuksia. Tämän jälkeen keskityttiin NixOS:n tärkeimpään ominaisuuteen, eli sen pakettienhallintajärjestelmään. Siitä käytiin läpi sen toimintaperiaate ja erot muihin pakettienhallintajärjestelmiin.
    [Show full text]
  • Journal of Functional Programming Nixos: a Purely Functional Linux
    Journal of Functional Programming http://journals.cambridge.org/JFP Additional services for Journal of Functional Programming: Email alerts: Click here Subscriptions: Click here Commercial reprints: Click here Terms of use : Click here NixOS: A purely functional Linux distribution EELCO DOLSTRA, ANDRES LÖH and NICOLAS PIERRON Journal of Functional Programming / Volume 20 / Special Issue 5­6 / November 2010, pp 577 ­ 615 DOI: 10.1017/S0956796810000195, Published online: 15 October 2010 Link to this article: http://journals.cambridge.org/abstract_S0956796810000195 How to cite this article: EELCO DOLSTRA, ANDRES LÖH and NICOLAS PIERRON (2010). NixOS: A purely functional Linux distribution. Journal of Functional Programming,20, pp 577­615 doi:10.1017/ S0956796810000195 Request Permissions : Click here Downloaded from http://journals.cambridge.org/JFP, by Username: nrnr, IP address: 108.20.67.9 on 31 Aug 2012 JFP 20 (5 & 6): 577–615, 2011. c Cambridge University Press 2010 577 doi:10.1017/S0956796810000195 First published online 15 October 2010 NixOS: A purely functional Linux distribution EELCO DOLSTRA Department of Software Technology, Delft University of Technology, Postbus 5031, 2600 GA Delft, The Netherlands (e-mail: [email protected]) ANDRES LOH¨ Department of Information and Computing Sciences, Utrecht University, Postbus 80 . 089, 3508 TB Utrecht, The Netherlands (e-mail: [email protected]) NICOLAS PIERRON EPITA Research and Development Laboratory, 14-16 rue Voltaire, 94276 Le Kremlin-Bicetreˆ cedex, France (e-mail: [email protected]) Abstract Existing package and system configuration management tools suffer from an imperative model, where system administration actions such as package upgrades or changes to system configuration files are stateful: they destructively update the state of the system.
    [Show full text]
  • Reproducible Builds Summit IV December 11 – 13, 2019
    Reproducible Builds Summit IV December 11 – 13, 2019. Paris, France Event Documentation Aspiration, 2973 16th Street, Suite 300, San Francisco, CA 94103 Phone: (415) 839-6456 • [email protected] • aspirationtech.org Table of Contents Agenda..........................................................................................................................................4 Session notes..............................................................................................................................10 Day 1.......................................................................................................................................10 Project updates...................................................................................................................10 Agenda brainstorming........................................................................................................13 Strategic working sessions I...............................................................................................21 Tooling............................................................................................................................21 Compilers.......................................................................................................................23 User verification..............................................................................................................24 Terminology....................................................................................................................28
    [Show full text]
  • Sage Installation Guide Release 9.4
    Sage Installation Guide Release 9.4 The Sage Development Team Aug 24, 2021 CONTENTS 1 Linux package managers 3 2 Install from Pre-built Binaries5 2.1 Download Guide.............................................5 2.2 Linux...................................................5 2.3 macOS..................................................6 2.4 Microsoft Windows (Cygwin)......................................6 3 Install from conda-forge 7 4 Install from Source Code 9 4.1 Supported platforms...........................................9 4.2 Prerequisites............................................... 10 4.3 Additional software........................................... 18 4.4 Step-by-step installation procedure.................................... 20 4.5 Make targets............................................... 25 4.6 Environment variables.......................................... 25 4.7 Installation in a Multiuser Environment................................. 30 5 Launching SageMath 33 5.1 Using a Jupyter Notebook remotely................................... 33 5.2 WSL Post-installation steps....................................... 34 5.3 Setting up SageMath as a Jupyter kernel in an existing Jupyter notebook or JupyterLab installation.. 35 6 Troubleshooting 37 Index 39 i ii Sage Installation Guide, Release 9.4 You can install SageMath either from a package manager, a pre-built binary tarball or from its sources. Installing SageMath from your distribution package manager is the preferred and fastest solution (dependencies will be automatically taken care of and SageMath will be using your system Python). It is the case at least for the following GNU/Linux distributions: Debian version >= 9, Ubuntu version >= 18.04, Arch Linux, and NixOS. If you are in this situation, see Linux package managers. If your operating system does not provide SageMath, you can also use a pre-built binary. See the section Install from Pre-built Binaries. Or you could install the sage package from the conda-forge project.
    [Show full text]
  • Nixos: the Purely Functional Linux Distribution
    NixOS: The Purely Functional Linux Distribution Eelco Dolstra LogicBlox 21 November 2013 Upgrading is risky business I No way to roll back I Not atomic / transactional Not declarative I Configuration is result of automated/manual changes over time I Therefore hard to reproduce Package management limitations I Hard to have multiple versions of a package I Need to be root to install packages I Upgrading one package may break others (“DLL hell”) So what was wrong with the previous 298 distributions? Not declarative I Configuration is result of automated/manual changes over time I Therefore hard to reproduce Package management limitations I Hard to have multiple versions of a package I Need to be root to install packages I Upgrading one package may break others (“DLL hell”) So what was wrong with the previous 298 distributions? Upgrading is risky business I No way to roll back I Not atomic / transactional Package management limitations I Hard to have multiple versions of a package I Need to be root to install packages I Upgrading one package may break others (“DLL hell”) So what was wrong with the previous 298 distributions? Upgrading is risky business I No way to roll back I Not atomic / transactional Not declarative I Configuration is result of automated/manual changes over time I Therefore hard to reproduce So what was wrong with the previous 298 distributions? Upgrading is risky business I No way to roll back I Not atomic / transactional Not declarative I Configuration is result of automated/manual changes over time I Therefore hard to reproduce Package management limitations I Hard to have multiple versions of a package I Need to be root to install packages I Upgrading one package may break others (“DLL hell”) Analysis Conventional Linux distributions have an imperative (stateful) approach to configuration / package management.
    [Show full text]
  • Self-Scaling Clusters and Reproducible Containers to Enable Scientific Computing
    Self-Scaling Clusters and Reproducible Containers to Enable Scientific Computing Peter Z. Vaillancourt∗, J. Eric Coultery, Richard Knepperz, Brandon Barkerx ∗Center for Advanced Computing Cornell University, Ithaca, New York, USA Email: [email protected] yCyberinfrastructure Integration Research Center Indiana University, Bloomington, IN, USA Email: [email protected] zCenter for Advanced Computing Cornell University, Ithaca, New York, USA Email: [email protected] xCenter for Advanced Computing Cornell University, Ithaca, New York, USA Email: [email protected] Abstract—Container technologies such as Docker have become cyberinfrastructure at a number of campuses, enabling them a crucial component of many software industry practices espe- to provide computational resources to their faculty members cially those pertaining to reproducibility and portability. The con- [2]. As more organizations utilize cloud resources in order tainerization philosophy has influenced the scientific computing community, which has begun to adopt – and even develop – con- to provide flexible infrastructure for research purposes, CRI tainer technologies (such as Singularity). Leveraging containers has begun providing tools to harness the scalability and utility for scientific software often poses challenges distinct from those of cloud infrastructure, working together with the members encountered in industry, and requires different methodologies. of the Aristotle Cloud Federation Project [3]. Red Cloud, the This is especially true for HPC. With an increasing number Cornell component of the Aristotle Cloud Federation, provides of options for HPC in the cloud (including NSF-funded cloud projects), there is strong motivation to seek solutions that provide an OpenStack cloud services much like the Jetstream resource, flexibility to develop and deploy scientific software on a variety that is available both to Cornell faculty as well as to Aristotle of computational infrastructures in a portable and reproducible members.
    [Show full text]