DOCSLIB.ORG

Install a Microk8s Single Node Cluster Locally on Windows 10

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Install a Microk8s Single Node Cluster Locally on Windows 10 Install a MicroK8s single node cluster locally on Windows 10 By Philippe Beraud, Microsoft France This walkthrough guides you through all the steps required to create and configure a MicroK8s cluster on Windows 10. Kubernetes1 runs on Linux. As such, MicroK8s2 provides a single command installation of the latest Kubernetes release on a Linux machine for development and testing. MicroK8s is easy to install and use on Ubuntu or any other Linux distro which supports snaps, i.e. pre-packaged applications (similar to Docker containers). Although Windows 10 now has some very useful features, such as the ability to install Ubuntu as an app, the integration of Windows Subsystem for Linux 2 (WSL2) doesn’t provide (yet) all the Ubuntu functionalities required to make MicroK8s run smoothly right out-of-the-box (OOB) and thus use the snap daemon. If you wish to experiment with running MicroK8s semi-natively, see: • Discourse post Using snapd in WSL2 • Post Running Snaps on WSL2 (Insiders only for now) along with the short YouTube video Use this ONE trick to run Linux Snap packages in Windows Subsystem for Linux 2 (WSL2) For now, and for the sake of simplicity for anyone looking to try out Kubernetes on Windows 10, let’s run MicroK8s on Windows 10 with virtualization. MicroK8s will install without problems on Ubuntu on a virtual machine (VM). The Canonical way to get a Linux VM on Windows 10 and to run MicroK8s in it is with multipass. Multipass gives you an easy to use interface to manage VMs on Windows 10 – Same is true on MacOS and Linux -. On Windows platforms, multipass defaults to using Microsoft Hyper-V as it’s virtualization provider. So, Microsoft Hyper-V is a prerequisite. (You can also take advantage of a local installation of VirtualBox if you want to.) Note For more information, see Instant Ubuntu VMs. Enabling Hyper-V The Windows 10 Hyper-V System requires: • Windows 10 Enterprise, Pro, or Education • 64-bit Processor with Second Level Address Translation (SLAT). • CPU support for VM Monitor Mode Extension (VT-c on Intel CPUs). • Minimum of 4 GB memory. Note For more information and troubleshooting, see Windows 10 Hyper-V System Requirements. Perform the following steps: 1. Open a PowerShell console as an Administrator. 1 https://kubernetes.io/ 2 https://github.com/ubuntu/microk8s 2. Check if virtualization is supported: PS C:> systeminfo If you see the following output, virtualization is supported. You can proceed with the next steps. Hyper-V Requirements: VM Monitor Mode Extensions: Yes Virtualization Enabled In Firmware: Yes Second Level Address Translation: Yes Data Execution Prevention Available: Yes If you see the following output, your system already has a Hypervisor installed and you can skip the next steps below. Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed. Otherwise, virtualization is unfortunately not supported on your machine, and you can not continue with this walkthrough. 3. Run the following command: PS C:> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All Note If the command couldn't be found, make sure you're running PowerShell as Administrator. 4. Once the installation has completed, reboot your Windows 10 machine. Creating the Ubuntu 18.04 LTS VM Perform the following steps: 1. Download and install multipass. The latest Windows 10 installer is available for download here on the multipass GitHub releases page. 2. Once multipass is installed, you can now create a VM to run MicroK8s. At least 4 Gb of RAM and 40 Gb of storage is recommended – you can pass these requirements when you launch the VM – a. Open a PowerShell console. b. Creates a new Ubuntu VM instance using the default, at this point in time, image: PS C:> multipass launch --name microk8s-vm --mem 4G --disk 40G It’s most likely going to be the latest cloud image of the newest Ubuntu LTS (Long Term Support) release, at the time of this writing a 18.04 LTS release. Note You can also choose another image, you can use the find command to see what’s available. Note For a complete listing of the available commands and their options in multipass, see the Command-line reference. When the command completes, a new VM named microk8s-vm is running. You can see it from the Hyper-V Manager. One should note that multipass uses the “Default Switch” network interface on Hyper-V, that, in turn, uses the “Internet Sharing” functionality, providing DHCP (IP addresses) and DNS (domain name resolution) to the instances. 3. Find the IP address which has been allocated to the VM: PS C:> multipass list Name State IPv4 Image microk8s-vm Running 172.22.82.139 Ubuntu 18.04 LTS Take a note of this IP as services will become available there when accessed from the Windows 10 host machine, see below. For example ,172.22.82.139 in our configuration. 4. To work within the VM environment more easily, get a shell inside the VM: C:\> multipass shell microk8s-vm This opens up a new Shell window: From within the VM shell, you can now follow along the rest of the quick start instructions for installing MicroK8s on multipass. Installing the MicroK8s cluster Perform the following steps: 1. Install the latest version of the MicroK8s snap: $ sudo snap install microk8s --classic Note Microk8s is a snap deploying Kubernetes. The MicroK8s snap closely follows upstream Kubernetes, so understanding a bit about the Kubernetes release cycle is helpful for more insight into MicroK8s releases. Upstream Kubernetes ships a new release series (e.g. 1.16.x) approximately every three months. For more information, see Snap channel overview. That’s all it takes for the installation, which is quick and painless! ;-) 2. MicroK8s has a built-in command to display its status (see hereafter). During installation you can use the --wait-ready flag to wait for the Kubernetes services to initialize. Check the status: $ sudo microk8s.status --wait-ready The microk8s-vm VM now runs a MicroK8s cluster on to of Ubuntu 18.04 LTS. MicroK8s comes with a set of tools: microk8s.start, microk8s.stop, microk8s.inspect, microk8s.status, microk8s.enable, microk8s.disable, microk8s.kubectl, microk8s.istioctl, and microk8s.config: • microk8s.start and microk8s.stop do what you would expect: start or stop your Kubernetes cluster. • microk8s.inspect gives you see the actual Kubernetes cluster status. • microk8s.status is a little less intuitive, as it shows the status of the add-ons and not the Kubernetes cluster status. You will use it alongside microk8s.enable and microk8s.disable to control add-ons. • microk8s.kubectl is a wrapper around kubectl, i.e. the cluster manager tool for Kubernetes. • microk8s.istioctl is used to control Istio, which can be enabled as an add-on via microk8s.enable istio. • microk8s.config, shows the client configuration that can be used to connect to your Kubernetes cluster, should you decide not to use microk8s.kubectl to do that. This command will result in output like the following: apiVersion: v1 clusters: - cluster: server: https://172.17.18.79:16443 name: microk8s-cluster contexts: - context: cluster: microk8s-cluster user: admin name: microk8s current-context: microk8s kind: Config preferences: {} users: - name: admin user: username: admin password: UFpWSGlHZDJuSkxpcCtJZ0JTU1dDK2d0eWk3NTdhZEg0TjVQcWVDc3Ywdz0K To feed this client config to microk8s.kubectl, you can for example write it to ~/.kube/config, i.e. the default configuration location. $ sudo microk8s.config > $HOME/.kube/config 3. Configure the network: $ sudo iptables -P FORWARD ACCEPT 4. MicroK8s creates a group to enable seamless usage of commands which require admin privilege. Add your current user to the group: $ sudo usermod -a -G microk8s ubuntu You will also need to re-enter the session for the group update to take place. 5. As mentioned above, MicroK8s bundles its own version of kubectl for accessing Kubernetes. Use it to run commands to monitor and control your Kubernetes. For example, view your node: $ microk8s.kubectl get nodes NAME STATUS ROLES AGE VERSION microk8s-vm Ready <none> 5m27s v1.17.0 6. Or alternatively see the running services: $ microk8s.kubectl get services NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes ClusterIP 10.152.183.1 <none> 443/TCP 6m17s 7. MicroK8s uses a namespaced kubectl command to prevent conflicts with any existing installs of the Kubernetes command-line tool, kubectl. kubectl allows you to run commands against Kubernetes clusters. You can use kubectl to deploy applications, inspect and manage cluster resources, and view logs. See Overview of kubectl. If you don't have an existing install, it is easier to add an alias (append to ~/.bash_aliases) like this: $ sudo snap alias microk8s.kubectl kubectl Added: - microk8s.kubectl as kubectl Otherwise, from the Bash terminal console, to install the latest version of kubectl, run the following command: $ snap install kubectl –classic $ kubectl version See Install kubectl on Linux. At this stage, you have a fully functional Kubernetes cluster. Creating a test deployment on the MicroK8s cluster Kubernetes is meant for deploying apps and services. You now can use the kubectl (alias) command (or the microk8s.kubectl command) to do that as with any Kubernetes. To install a first app, perform the following steps: 1. From the VM Shell, deploy NGINX with 3 replicas (instances) available: $ kubectl run nginx --image nginx:alpine --replicas 3 2. It may take a minute or two to install, but you can check the status. Once NGINX has been deployed, expose the application: $ kubectl expose deployment nginx --port 80 --target-port 80 --type ClusterIP -- selector=run=nginx --name nginx 3. See the new Service and ClusterIP address assigned: $ kubectl get svc You now have a deployed an application to a fully functional Kubernetes cluster using Microk8s Further configuring the MicroK8s cluster MicroK8s uses the minimum of components for a pure, lightweight Kubernetes.
Load more

Recommended publications
  • The Seeds of Rural Resilience
    NEWS & VIEWS FROM THE SUSTAINABLE SOUTHWEST Growing a Regional Food System THE SEEDS OF RURAL RESILIENCE October 2017 NORTHERN NEW MEXICO’S LARGEST DISTRIBUTION NEWSPAPER Vol. 9 No. 10 2 Green Fire Times • October 2017 www.GreenFireTimes.com Is Your Roof Winter Ready? Whether your roof is currently leaking or you’d like to restore your roof before it fails, Fix My Roof is the right choice. Call today for a free roof assessment! www.GreenFireTimes.com Green Fire Times • October 2017 3 YOU’LL LOVE WHAT YOU SEE! PROGRAM PARTNERS: FRIDAY SATURDAY OCT 27 NOV 14 7:30 PM 7:30 PM Sponsored by The L.A. Grow the Growers Browns Dance Farm Training 5 Project Business Incubation A CULTIVATING BERNALILLO COUNTY INITIATIVE bernalillo Applications for the 2018 Opencounty Space internships now available Lensic.org 505-988-1234 For more information NONPROFIT • COMMUNITY FUNDED SERVICE CHARGES APPLY AT ALL POINTS OF PURCHASE A special thanks to our www.bernco.gov/growthegrowers 2017/2018 sponsor: Find Your Future in ENGINEERING @Northern New Mexico College NORTHERN The most affordable 4-year now offering college in the Southwest classes at Santa Fe HEC! Northern Engineering programs include: n ABET-accredited Bachelor in INFORMATION ENGINEERING Tech (IET) n Ask about our new CYBERSECURITY concentration in IET Schedule your campus visit today! n Bachelor in ELECTROMECHANICAL Engineering/Solar Energy Concentration CALL 505.747.2111 or visit nnmc.edu n Associate of Applied Science degrees in RENEWABLE ENERGY and ELECTRICAL TECH 4 Green Fire Times Oc tober 2017 www.GreenFireTimes.com Vol. 9, No. 10 October 2017 Issue No.
    [Show full text]
  • AD Bridge User Guide
    AD Bridge User Guide May 2019 Legal Notice © Copyright 2019 Micro Focus or one of its affiliates. The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. For additional information, such as certification-related notices and trademarks, see http://www.microfocus.com/about/legal/. Contents About This Guide 5 1 Getting Started 7 2 Installing AD Bridge 9 Linux Requirements and Supported Platforms . 9 Linux Requirements . 9 Supported Linux Platforms. 10 Installing the AD Bridge Linux Agent. 11 Licensing the Linux Agent . 12 Joining Active Directory - Post Installation . 13 Installing the AD Bridge GPEdit Extension . 13 3 Managing Linux GPO Settings 15 Accessing or Creating Group Policy Objects . 15 Configuring Linux GPO Settings . 16 Managing Linux Agent Services with GPOs . 17 Importing Custom Configuration File Settings. 18 Managing Linux Applications with GPOs . 18 Managing User Logins with GPOs . 19 Viewing Policy Injection on a Linux Agent. 20 A Appendix 21 Linux Agent GPO Settings . 21 Linux Agent Commands and Lookups . 22 GPO Best Practices . 23 Contents 3 4 About This Guide The AD Bridge User Guide provides information to help you understand, install, configure, and employ the Micro Focus AD Bridge product to help manage your enterprise environment. Audience This guide is written for administrators and users who will use Micro Focus AD Bridge to more effectively manage Active Directory and group policies in a cross-platform environment.
    [Show full text]
  • List of New Applications Added in ARL #2517
    List of New Applications Added in ARL #2517 Application Name Publisher ActiveEfficiency 1.10 1E ACL Add-In 14.0 ACL Services ACL for Windows 14.2 ACL Services ACL for Windows 14.1 ACL Services Direct Link 7.5 ACL Services ACL Add-In 1.1 ACL Services Creative Cloud Connection 5 Adobe Experience Manager forms 6.5 Adobe Elements Auto Analyzer 12.0 Adobe Token Resolver 3.4 Adobe Token Resolver 3.6 Adobe LogTransport 1.6 Adobe LogTransport 2.4 Adobe IPC Broker 5.6 Adobe Data Workbench Adobe Token Resolver 3.5 Adobe Token Resolver 3.7 Adobe Dimension 3.2 Adobe Photo Downloader 8.0 Adobe LogTransport 2.2 Adobe GC Invoker Utility 4.5 Adobe GC Client 5.0 Adobe Crash Reporter 2.0 Adobe Crash Reporter 2.1 Adobe GC Invoker Utility 6.4 Adobe Dynamic Link Media Server 12.1 Adobe Token Resolver 3.3 Adobe Token Resolver 4.7 Adobe GC Client 4.4 Adobe Genuine Software Integrity Service 6.4 Adobe Creative Cloud Libraries 3 Adobe Token Resolver 3.9 Adobe Token Resolver 5.0 Adobe Genuine Software Integrity Service 6.5 Adobe Create PDF 17.1 Adobe Crash Reporter 1.5 Adobe Notification Client 4.9 Adobe GC Client 6.4 Adobe GC Client 6.5 Adobe Crash Reporter 1.6 Adobe Crash Reporter 2.2 Adobe Crash Reporter 2.4 Adobe GPU Sniffer 19.0 Adobe Token Generator 7.0 Adobe Token Resolver 3.8 Adobe LogTransport 1.5 Adobe InDesign Server CC (2020) Adobe GC Invoker Utility 5.0 Adobe GC Invoker Utility 6.5 Adobe RED Importer Plugin Unspecified Adobe Token Generator 8.0 Adobe GC Client 1.2 Adobe GC Client 4.5 Adobe EmailNotificationPlugin 11.0 Apple BatteryUIKit 1.0 Apple
    [Show full text]
  • Snap Vs Flatpak Vs Appimage: Know the Differences | Which Is Better
    Published on Tux Machines (http://www.tuxmachines.org) Home > content > Snap vs Flatpak vs AppImage: Know The Differences | Which is Better Snap vs Flatpak vs AppImage: Know The Differences | Which is Better By Rianne Schestowitz Created 08/12/2020 - 8:29pm Submitted by Rianne Schestowitz on Tuesday 8th of December 2020 08:29:48 PM Filed under Software [1] Every Linux distribution has its own package manager tool or command-line based repository system to update, install, remove, and manage packages on the system. Despite having a native package manager, sometimes you may need to use a third-party package manager on your Linux system to get the latest version of a package to avoid repository errors and server errors. In the entire post, we have seen the comparison between Snap, AppImage, and Flatpak. Snap, Flatpak, and AppImage; all have their pros and cons. In my opinion, I will always prefer the Flatpak package manager in the first place. If I can?t find any packages on Flatpak, then I?ll go for the AppImage. And finally, Snap is an excellent store of applications, but it still requires some development. I would go to the Snap store for proprietary or semi-proprietary applications than main applications. Please share it with your friends and the Linux community if you find this post useful and informative. Let us know which package manager do you prefer to use on your Linux system. You can write also write down your opinions regarding this post in the comment section. [2] Software Source URL: http://www.tuxmachines.org/node/145224 Links: [1] http://www.tuxmachines.org/taxonomy/term/38 [2] https://www.ubuntupit.com/snap-vs-flatpak-vs-appimage-know-the-difference/.
    [Show full text]
  • Ubuntu Server Guide Basic Installation Preparing to Install
    Ubuntu Server Guide Welcome to the Ubuntu Server Guide! This site includes information on using Ubuntu Server for the latest LTS release, Ubuntu 20.04 LTS (Focal Fossa). For an offline version as well as versions for previous releases see below. Improving the Documentation If you find any errors or have suggestions for improvements to pages, please use the link at thebottomof each topic titled: “Help improve this document in the forum.” This link will take you to the Server Discourse forum for the specific page you are viewing. There you can share your comments or let us know aboutbugs with any page. PDFs and Previous Releases Below are links to the previous Ubuntu Server release server guides as well as an offline copy of the current version of this site: Ubuntu 20.04 LTS (Focal Fossa): PDF Ubuntu 18.04 LTS (Bionic Beaver): Web and PDF Ubuntu 16.04 LTS (Xenial Xerus): Web and PDF Support There are a couple of different ways that the Ubuntu Server edition is supported: commercial support and community support. The main commercial support (and development funding) is available from Canonical, Ltd. They supply reasonably- priced support contracts on a per desktop or per-server basis. For more information see the Ubuntu Advantage page. Community support is also provided by dedicated individuals and companies that wish to make Ubuntu the best distribution possible. Support is provided through multiple mailing lists, IRC channels, forums, blogs, wikis, etc. The large amount of information available can be overwhelming, but a good search engine query can usually provide an answer to your questions.
    [Show full text]
  • Edgex Foundry Snap Package.Pdf
    CanSnap Package Tech Talks - Session 11 November 2018 edgexfoundry.org | @edgexfoundry Agenda ● Introduction to snaps ● Overview of the edgexfoundry snap ● How to install ● How to configure/manage/update ● How to use with additional device services ● Further references ● Upcoming tech talks ● Q&A edgexfoundry.org | @edgexfoundry Ian Johnson <[email protected]> ● Canonical / Software Engineer Field Engineering - Devices & IoT ● Primary snap developer for Dehli release ● Contributed CI work for snap build ● Contributed code to security to decouple Docker-isms ● Involved in testing most services for Dehli ● Contributed bug fixes to SMA ● Member of the DevOps working group edgexfoundry.org | @edgexfoundry Tony Espy <[email protected]> ● Canonical / Technical Architect Field Engineering - Devices & IoT ● Technical Steering Committee member ● Former Device Services WG chair ● Author of Device Services SDK Requirements ● Original developer of device-sdk-go ● Active member of Core, Device Services & Security working groups ● Created first EdgeX snap prototype edgexfoundry.org | @edgexfoundry Introduction What's a snap? Snaps are containerised software packages that work on all major Linux distributions without modification. Simple to create and publish, they automatically update safely. edgexfoundry.org | @edgexfoundry Introduction Snaps are... ● Self-contained squashfs-based software packages ● Containing one or more applications or services ● Cryptographically-signed by publisher and tamper-proof ● Published to risk-based update channels
    [Show full text]
  • Snappy Ubuntu Core Enabling Secure Devices with App Stores We Are the Company
    Snappy Ubuntu Core Enabling secure devices with app stores We are the company behind Ubuntu. Canonical and Ubuntu | Best of both worlds CANONICAL Ubuntu Commercial backing #1 Linux Desktop for the #1 general purpose Linux OS: #1 Cloud OS Ubuntu Now also for Global Services, phones, tablets & Support, IoT devices Certification! It has never been easier to make a custom hardware appliance... Building an IoT Appliance Beaglebone Black Raspberry Pi 2 Snickerdoodle Intel NUC Qualcomm DragonBoard Samsung Artik But why? Old-School Modern Embedded Embedded RTOS/Embedded General Linux cross-compilation normal toolchain single-purpose multi-purpose constrained 256M RAM 2G SD rare updates constant updates offline connected expensive & custom cheap & easy software devel software devel Linux Server Linux Device Ops Ops centralised distributed supported field-serviced expensive cheap elastic spof cheap to service expensive to fix Autopilot App Business App Lite (free, included) Farmers ($500) Pro ($100) Avalanches ($2500) Elite ($250) Miners ($9950) $600 drone (hardware) Apps, Services and SaaS Infrastructure Certification. Support. Assurance. Security. Maintenance. Compatibility. Transactional updates Application confinement Familiar Ubuntu app development classic snappy app writable app writable any package can area area write to any file app snap app snap os writable files writable spaces os snap per snap read-only snaps kernel config filesystem kernel snap Snappy system architecture Software Innovator(s) Snap Snap Snap ● Automatic updates Library
    [Show full text]
  • How Containers Work Sasha Goldshtein @Goldshtn CTO, Sela Group Github.Com/Goldshtn
    Linux How Containers Work Sasha Goldshtein @goldshtn CTO, Sela Group github.com/goldshtn Agenda • Why containers? • Container building blocks • Security profiles • Namespaces • Control groups • Building tiny containers Hardware Virtualization vs. OS Virtualization VM Container ASP.NET Express ASP.NET Express RavenDB Nginx RavenDB Nginx App App App App .NET Core .NET Core V8 libC .NET Core .NET Core V8 libC Ubuntu Ubuntu Ubuntu RHEL Ubuntu Ubuntu Ubuntu RHEL Linux Linux Linux Linux Linux Kernel Kernel Kernel Kernel Kernel Hypervisor Hypervisor DupliCated Shared (image layer) Key Container Usage Scenarios • Simplifying configuration: infrastructure as code • Consistent environment from development to production • Application isolation without an extra copy of the OS • Server consolidation, thinner deployments • Rapid deployment and scaling Linux Container Building Blocks User Namespaces node:6 ms/aspnetcore:2 openjdk:8 Copy-on- /app/server.js /app/server.dll /app/server.jar write layered /usr/bin/node /usr/bin/dotnet /usr/bin/javaControl groups filesystems /lib64/libc.so /lib64/libc.so /lib64/libc.so 1 CPU 2 CPU 1 CPU 1 GB 4 GB 2 GB syscall Kernel Security profile Security Profiles • Docker supports additional security modules that restrict what containerized processes can do • AppArmor: text-based configuration that restricts access to certain files, network operations, etc. • Docker uses seccomp to restrict system calls performed by the containerized process • The default seccomp profile blocks syscalls like reboot, stime, umount, specific types of socket protocols, and others • See also: Docker seccomp profile, AppArmor for Docker Experiment: Using a Custom Profile (1/4) host% docker run -d --rm microsoft/dotnet:runtime …app host% docker exec -it $CID bash cont# apt update && apt install linux-perf cont# /usr/bin/perf_4.9 record -F 97 -a ..
    [Show full text]
  • Conflict Resolution Via Containerless Filesystem Virtualization
    Dependency Heaven: Conflict Resolution via Containerless Filesystem Virtualization Anonymous Author(s) Abstract previous installation, effectively preventing concurrent ver- Resolving dependency versioning conflicts in applications sions of that library from coexisting. The same is true for is a long-standing problem in software development and packages whose executable names does not change across deployment. Containers have become a popular way to ad- releases; unless the user renames the existing executable dress this problem, allowing programs to be distributed in a files prior to the installation of a new version it is notpos- portable fashion and to run them under strict security con- sible to keep both installations around. The problem with straints. Due to the popularity of this approach, its use has that approach is that it breaks package managers, as the re- started to extend beyond its original aim, with users often named files will not be featured in the package manager’s creating containers bundling entire Linux distributions to database and, consequently, will not be tracked anymore. run mundane executables, incurring hidden performance Further, unless executables depending on the renamed files and maintenance costs. This paper presents an alternative are modified to reflect their new path, users need todefine approach to the problem of versioning resolution applied to which executable to activate at a given time, usually through locally-installed applications, through a virtualization tool tricky management of symbolic
    [Show full text]
  • Snap Creator Framework 4.1.1 Installation Guide
    Snap Creator® Framework 4.1.1 Installation Guide NetApp, Inc. Telephone: +1 (408) 822-6000 Part number: 215-09552_A0 495 East Java Drive Fax: +1 (408) 822-4501 November 2014 Sunnyvale, CA 94089 Support telephone: +1 (888) 463-8277 U.S. Web: www.netapp.com Feedback: [email protected] Table of Contents | 3 Contents What the Snap Creator Framework does .................................................. 5 Snap Creator architecture ............................................................................................ 6 Snap Creator Server ........................................................................................ 6 Snap Creator Agent ......................................................................................... 7 Plug-ins for application integration ................................................................. 7 Preinstallation requirements ....................................................................... 9 Snap Creator installation and configuration requirements .......................................... 9 Downloading the Snap Creator software .................................................................. 11 Creating a Snap Creator user for Data ONTAP ........................................................ 12 Data ONTAP operating in 7-mode ................................................................ 12 Clustered Data ONTAP ................................................................................. 13 Installing Java on Snap Creator hosts ......................................................................
    [Show full text]
  • WAM Tmarm User’S Guide
    WAM TMArm User’s Guide Barrett Technology® Inc. Document: D1001 Version: AA.00 Table of Contents Getting Started ........................................................................................................................................................ 2 Unpacking.............................................................................................................................................................................................2 System Setup.........................................................................................................................................................................................3 System Startup ......................................................................................................................................................................................7 Hardware................................................................................................................................................................. 8 WAM Arm............................................................................................................................................................................................8 WAM Wrist: .......................................................................................................................................................................................11 PC & Control Software........................................................................................................................................
    [Show full text]
  • Package Management and Distribution in a Cloud World
    Package Management and Distribution in a Cloud World Jose Miguel Parrella About me • Jose Miguel Parrella – GitHub: @bureado • Principal Program Manager, Office of the CTO, Microsoft Azure • Linux and open source enthusiast for 15+ years • Debian Developer, career distro-builder Package management in open source: always changing • 15 years ago: APT and RPM • Programming languages: from CPAN and PyPI to NPM and Golang packages Ecosystem Debian Upstream As a % Ruby 1100 9300 11.83% • Next-generation package Perl 3700 31000 11.94% management: Flatpak, Snaps, Nix, Python 3700 118000 3.14% etc. Node.js 1300 350000 0.37% • Container image specification & All-up libs 30K 2.8M 1.07% hub/store workflow Source: libraries.io and APT lists • Use cases where provenance is controlled by final distributor (e.g., embedded) It’s getting busy out there… Why is this challenging now? • Most IT Professionals working with Linux and open source technologies are not using modern package managers (or containers!) – A significant portion of the Enterprise IT budget depends on a historical decision: APT or RPM • The general community sentiment (sysadmin, DevOps, SRE, etc.) on this evolving technical story is skeptical Why do these technologies exist? We don’t know • Push the packaging responsibility upstream? • Be able to distribute non-free software more effectively and/or monetize? • Provide additional container and application security capabilities? • Reduce the size of a Linux distribution? • Make it easier to package for Linux by removing dependency tracking?
    [Show full text]