MCP Deployment Guide Version Q4-18 Mirantis Cloud Platform Deployment Guide

Total Page:16

File Type:pdf, Size:1020Kb

MCP Deployment Guide Version Q4-18 Mirantis Cloud Platform Deployment Guide MCP Deployment Guide version q4-18 Mirantis Cloud Platform Deployment Guide Copyright notice 2021 Mirantis, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. No part of this publication may be reproduced in any written, electronic, recording, or photocopying form without written permission of Mirantis, Inc. Mirantis, Inc. reserves the right to modify the content of this document at any time without prior notice. Functionality described in the document may not be available at the moment. The document contains the latest information at the time of publication. Mirantis, Inc. and the Mirantis Logo are trademarks of Mirantis, Inc. and/or its affiliates in the United States an other countries. Third party trademarks, service marks, and names mentioned in this document are the properties of their respective owners. ©2021, Mirantis Inc. Page 2 Mirantis Cloud Platform Deployment Guide Preface This documentation provides information on how to use Mirantis products to deploy cloud environments. The information is for reference purposes and is subject to change. Intended audience This documentation is intended for deployment engineers, system administrators, and developers; it assumes that the reader is already familiar with network and cloud concepts. Documentation history The following table lists the released revisions of this documentation: Revision date Description February 8, 2019 Q4`18 GA ©2021, Mirantis Inc. Page 3 Mirantis Cloud Platform Deployment Guide Introduction MCP enables you to deploy and manage cloud platforms and their dependencies. These include OpenStack and Kubernetes based clusters. The deployment can be performed automatically through MCP DriveTrain or using the manual deployment procedures. The MCP DriveTrain deployment approach is based on the bootstrap automation of the Salt Master node that contains MAAS hardware nodes provisioner as well as on the automation of an MCP cluster deployment using the Jenkins pipelines. This approach significantly reduces your time and eliminates possible human errors. The manual deployment approach provides the ability to deploy all the components of the cloud solution in a very granular fashion. The guide also covers the deployment procedures for additional MCP components including OpenContrail, Ceph, StackLight, NFV features. Seealso Minimum hardware requirements ©2021, Mirantis Inc. Page 4 Mirantis Cloud Platform Deployment Guide Plan the deployment The configuration of your MCP installation depends on the individual requirements that should be met by the cloud environments. The detailed plan of any MCP deployment is determined on a per-cloud basis. For the MCP reference architecture and design overview, see: MCP Reference Architecture: Plan an OpenStack environment or MCP Reference Architecture: Plan a Kubernetes cluster depending on the type of your deployment. Caution! Kubernetes support termination notice Starting with the MCP 2019.2.5 update, the Kubernetes component is no longer supported as a part of the MCP product. This implies that Kubernetes is not tested and not shipped as an MCP component. Although the Kubernetes Salt formula is available in the community driven SaltStack formulas ecosystem, Mirantis takes no responsibility for its maintenance. Customers looking for a Kubernetes distribution and Kubernetes lifecycle management tools are encouraged to evaluate the Mirantis Kubernetes-as-a-Service (KaaS) and Docker Enterprise products. At the same time, MCP provides a flexible reduced prebuilt mirror image that you can customize depending on the needs of your MCP deployment after the initial bootstrap is performed. The usage of the prebuilt mirror image is essential in case of an offline MCP deployment scenario. The prebuilt mirror image contains the Debian package mirror (Aptly or flat deb repositories), Docker images mirror (Registry), Git repositories mirror, and mirror of the Mirantis Ubuntu VM cloud images (VCP). This guide includes the steps required for the case with the additional prebuilt VM deployment on the Foundation node. ©2021, Mirantis Inc. Page 5 Mirantis Cloud Platform Deployment Guide Prepare for the deployment Create a project repository An MCP cluster deployment configuration is stored in a Git repository created on a per-customer basis. This section instructs you on how to manually create and prepare your project repository for an MCP deployment. Before you start this procedure, create a Git repository in your version control system, such as GitHub. To create a project repository manually: 1. Log in to any computer. 2. Create an empty directory and change to that directory. In the example below, it is mcpdoc. 3. Initialize your project repository: git init Example of system response: Initialized empty Git repository in /Users/crh/Dev/mcpdoc/.git/ 4. Add your repository to the directory you have created: git remote add origin <YOUR-GIT-REPO-URL> 5. Verify that Git and your local repository are set up correctly by creating and pushing a test file to your project repository. Run the following example commands: Note The example commands below require the Git and GitHub credentials to be created and configured for your project repository. git remote add origin https://github.com/example_account/mcpdoc.git git config --local user.email "[email protected]" git config --local user.name "example_gituser" git config -l echo "#. mcpdoc" >> README.md git add README.md git commit -m "first commit" git push -u origin master ©2021, Mirantis Inc. Page 6 Mirantis Cloud Platform Deployment Guide 6. Create the following directories for your deployment metadata model: mkdir -p classes/cluster mkdir nodes 7. Add the Reclass variable to your bash profile by verifying your current directory using pwd and adding the string that exports the Reclass variable with the output value of the pwd command: pwd vim ~/.bash_profile export RECLASS_REPO=<PATH_TO_YOUR_DEV_DIRECTORY> Example of system response: /Users/crh/Dev/mcpdoc/ "~/.bash_profile" 13L, 450C export RECLASS_REPO="/Users/crh/Dev/mcpdoc/" 8. Log out and log back in. 9. Verify that your ~/.bash_profile is sourced: echo $RECLASS_REPO The command must show the value of your RECLASS_REPO variable. Example of system response: /Users/crh/Dev/mcpdoc/ 10 Add the Mirantis Reclass module to your repository as a submodule: . git submodule add https://github.com/Mirantis/reclass-system-salt-model ./classes/system/ Example of system response: Cloning into '<PATH_TO_YOUR_DEV_DIRECTORY>/classes/system'... remote: Counting objects: 8923, done. remote: Compressing objects: 100% (214/214), done. remote: Total 8923 (delta 126), reused 229 (delta 82), pack-reused 8613 Receiving objects: 100% (8923/8923), 1.15 MiB | 826.00 KiB/s, done. Resolving deltas: 100% (4482/4482), done. Checking connectivity... done. ©2021, Mirantis Inc. Page 7 Mirantis Cloud Platform Deployment Guide 11 Update the submodule: . git submodule sync git submodule update --init --recursive --remote 12 Add your changes to a new commit: . git add -A 13 Commit your changes: . git commit 14 Add your commit message. Example of system response: [master (root-commit) 9466ada] Initial Commit 2 files changed, 4 insertions(+) create mode 100644 .gitmodules create mode 160000 classes/system 15 Push your changes: . git push 16 Proceed to Create a deployment metadata model. ©2021, Mirantis Inc. Page 8 Mirantis Cloud Platform Deployment Guide Create a deployment metadata model In a Reclass metadata infrastructural model, the data is stored as a set of several layers of objects, where objects of a higher layer are combined with objects of a lower layer, that allows for as flexible configuration as required. The MCP metadata model has the following levels: • Service level includes metadata fragments for individual services that are stored in Salt formulas and can be reused in multiple contexts. • System level includes sets of services combined in a such way that the installation of these services results in a ready-to-use system. • Cluster level is a set of models that combine already created system objects into different solutions. The cluster module settings override any settings of service and system levels and are specific for each deployment. The model layers are firmly isolated from each other. They can be aggregated on a south-north direction using service interface agreements for objects on the same level. Such approach allows reusing of the already created objects both on service and system levels. This section describes how to generate the cluster level metadata model for your MCP cluster deployment using the Model Designer web UI. The tool used to generate the model is Cookiecutter, a command-line utility that creates projects from templates. While generating a metadata model, you can enable automated encryption of all secrets for the Salt Master node .iso file. Note The Model Designer web UI is only available within Mirantis. The Mirantis deployment engineers can access the Model Designer web UI using their Mirantis corporate username and password. The workflow of a model creation includes the following stages: 1. Defining the model through the Model Designer web UI. 2. Optional. Tracking the execution of the model creation pipeline in the Jenkins web UI. 3. Obtaining the generated model to your email address or getting it published to the project repository directly. Note If you prefer publishing to the project repository, verify that the dedicated repository is configured correctly and Jenkins
Recommended publications
  • Deliverable No. 5.3 Techniques to Build the Cloud Infrastructure Available to the Community
    Deliverable No. 5.3 Techniques to build the cloud infrastructure available to the community Grant Agreement No.: 600841 Deliverable No.: D5.3 Deliverable Name: Techniques to build the cloud infrastructure available to the community Contractual Submission Date: 31/03/2015 Actual Submission Date: 31/03/2015 Dissemination Level PU Public X PP Restricted to other programme participants (including the Commission Services) RE Restricted to a group specified by the consortium (including the Commission Services) CO Confidential, only for members of the consortium (including the Commission Services) Grant Agreement no. 600841 D5.3 – Techniques to build the cloud infrastructure available to the community COVER AND CONTROL PAGE OF DOCUMENT Project Acronym: CHIC Project Full Name: Computational Horizons In Cancer (CHIC): Developing Meta- and Hyper-Multiscale Models and Repositories for In Silico Oncology Deliverable No.: D5.3 Document name: Techniques to build the cloud infrastructure available to the community Nature (R, P, D, O)1 R Dissemination Level (PU, PP, PU RE, CO)2 Version: 1.0 Actual Submission Date: 31/03/2015 Editor: Manolis Tsiknakis Institution: FORTH E-Mail: [email protected] ABSTRACT: This deliverable reports on the technologies, techniques and configuration needed to install, configure, maintain and run a private cloud infrastructure for productive usage. KEYWORD LIST: Cloud infrastructure, OpenStack, Eucalyptus, CloudStack, VMware vSphere, virtualization, computation, storage, security, architecture. The research leading to these results has received funding from the European Community's Seventh Framework Programme (FP7/2007-2013) under grant agreement no 600841. The author is solely responsible for its content, it does not represent the opinion of the European Community and the Community is not responsible for any use that might be made of data appearing therein.
    [Show full text]
  • MCP Q4`18 Release Notes Version Q4-18 Mirantis Cloud Platform Release Notes Version Q4`18
    MCP Q4`18 Release Notes version q4-18 Mirantis Cloud Platform Release Notes version Q4`18 Copyright notice 2021 Mirantis, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. No part of this publication may be reproduced in any written, electronic, recording, or photocopying form without written permission of Mirantis, Inc. Mirantis, Inc. reserves the right to modify the content of this document at any time without prior notice. Functionality described in the document may not be available at the moment. The document contains the latest information at the time of publication. Mirantis, Inc. and the Mirantis Logo are trademarks of Mirantis, Inc. and/or its affiliates in the United States an other countries. Third party trademarks, service marks, and names mentioned in this document are the properties of their respective owners. ©2021, Mirantis Inc. Page 2 Mirantis Cloud Platform Release Notes version Q4`18 What’s new This section provides the details about the features and enhancements introduced with the latest MCP release version. Note The MCP integration of the community software projects, such as OpenStack, Kubernetes, OpenContrail, and Ceph, includes the integration of the features which the MCP consumers can benefit from. Refer to the MCP Q4`18 Deployment Guide for the software features that can be deployed and managed by MCP DriveTrain. MCP DriveTrain • Encryption of sensitive data in the Reclass model • Galera verification and restoration pipeline • Jenkins version upgrade • Partitioning table for the VCP images Encryption of sensitive data in the Reclass model SECURITY Implemented the GPG encryption to protect sensitive data in the Git repositories of the Reclass model as well as the key management mechanism for secrets encryption and decryption.
    [Show full text]
  • Google Cloud Platform (GCP): Возможности И Преимущества
    Google Cloud Platform (GCP): возможности и преимущества Дмитрий Новаковский, Олег Ивонин Январь 2017 Кто мы? Дмитрий Новаковский / [email protected] ● Customer Engineer @ Google Netherlands B.V. ● Поддержка продаж и разработка решений на основе GCE, GKE, GAE ● В прошлом: ○ IaaS/PaaS (OpenStack @ Mirantis) ○ SaaS (ETAdirect @ TOA Technologies/Oracle) Олег Ивонин / [email protected] ● Cloud Web Solutions Engineer @ Google Netherlands B.V. ● Разработка инструментов для анализа стоимости конфигураций и планирования архитектуры облачных решений на основе GCP ○ Google Cloud Platform Pricing Calculator и другие О чем мы расскажем? ● Часть 1: Google Cloud Platform 101 ○ Наборы облачных сервисов и их назначение ○ Преимущества на рынке ● Часть 2: Инфраструктурные сервисы GCP (IaaS/PaaS) ○ GCE - Виртуальные машины ○ GKE - Оркестрация Docker контейнеров ○ GAE - NoOps/PaaS окружения ● Часть 3: Big Data и Machine Learning инструменты GCP ● Часть 4: Примеры, итоги и вопросы/ответы Disclaimer Google Cloud Platform 4 Часть 1: Google Cloud Platform 101 Google Cloud Platform 5 Путь IT-инфраструктуры в “облако” Storage Processing Memory Network Storage Processing Memory Network Physical / Self-Service / Serverless / Colo / VPS Elastic / IaaS NoOps / PaaS Google Cloud Platform 6 Что такое Google Cloud Platform? GCP - это набор коммерческих облачных сервисов, основанных на разработках и опыте Google в для собственных продуктов: ● Google Search ● YouTube ● Google Maps ● и др. Google’s Data Research Flume MapReduce Dremel Millwheel TensorFlow GFS Megastore
    [Show full text]
  • Entrust Nshield Hsms and Mirantis Kubernetes Engine Enhance The
    Entrust nShield HSMs and Mirantis Kubernetes Engine Enhance the Security of Containerized Applications Integrated solution enables application developers to easily access high assurance cryptographic services HIGHLIGHTS THE PROBLEM • Support today’s fast-paced application Developers lack ability to access container deployment environments cryptographic functions for their • Provide secure access to Entrust applications nShield® hardware security modules Modern application development uses (HSMs) containers and Kubernetes to standardize • Allow critical cryptographic key software design and facilitate continuous management to run transparently integration and continuous delivery (CI/CD). • Establish a FIPS 140-2 and Common The process enables developers to deploy Criteria certified root of trust new applications with the assurance that they’ll run reliably in any user environment. • Help facilitate auditing and compliance A critical component of the software with data security regulations development process is the security of the CI/CD software supply chain. To date, adding an HSM root of trust for container deployments has been difficult. LEARN MORE AT ENTRUST.COM Enhancing the security of containerized applications THE CHALLENGE THE SOLUTION Enabling access to cryptographic Mirantis Kubernetes Engine services without impacting and Entrust nShield HSMs development process Mirantis Kubernetes Engine is a market- While the security of applications developed leading container platform for accelerating using containers and Kubernetes is
    [Show full text]
  • Forrester: Multicloud Container Development Platforms, Q3 2020
    LICENSED FOR INDIVIDUAL USE ONLY The Forrester Wave™: Multicloud Container Development Platforms, Q3 2020 The Eight Providers That Matter Most And How They Stack Up by Dave Bartoletti and Charlie Dai September 15, 2020 Why Read This Report Key Takeaways In our 29-criterion evaluation of multicloud Red Hat-IBM, Google, And Rancher Lead The container development platform providers, we Pack identified the eight most significant ones — Forrester’s research uncovered a market in which Canonical, D2iQ, Google, Mirantis, Platform9 Red Hat-IBM, Google, and Rancher are Leaders; Systems, Rancher, Red Hat-IBM, VMware — VMware, D2iQ, and Platform9 Systems are and researched, analyzed, and scored them. Strong Performers; and Mirantis and Canonical This report shows how each provider measures are Contenders. up and helps infrastructure and operations Dev Experience, Distributed Operations, And professionals select the right one for their needs. Ecosystem Integrations Are Key Differentiators As developers and technology teams race to meet the demand for cloud-native applications, developer experience and development services, distributed infrastructure operations, and rich ecosystem partnerships and integrations will dictate which platform providers will lead the pack. This PDF is only licensed for individual use when downloaded from forrester.com or reprints.forrester.com. All other distribution prohibited. FORRESTER.COM FOR INFRASTRUCTURE & OPERATIONS PROFESSIONALS The Forrester Wave™: Multicloud Container Development Platforms, Q3 2020 The Eight Providers
    [Show full text]
  • View Whitepaper
    INFRAREPORT Top M&A Trends in Infrastructure Software EXECUTIVE SUMMARY 4 1 EVOLUTION OF CLOUD INFRASTRUCTURE 7 1.1 Size of the Prize 7 1.2 The Evolution of the Infrastructure (Public) Cloud Market and Technology 7 1.2.1 Original 2006 Public Cloud - Hardware as a Service 8 1.2.2 2016 - 2010 - Platform as a Service 9 1.2.3 2016 - 2019 - Containers as a Service 10 1.2.4 Container Orchestration 11 1.2.5 Standardization of Container Orchestration 11 1.2.6 Hybrid Cloud & Multi-Cloud 12 1.2.7 Edge Computing and 5G 12 1.2.8 APIs, Cloud Components and AI 13 1.2.9 Service Mesh 14 1.2.10 Serverless 15 1.2.11 Zero Code 15 1.2.12 Cloud as a Service 16 2 STATE OF THE MARKET 18 2.1 Investment Trend Summary -Summary of Funding Activity in Cloud Infrastructure 18 3 MARKET FOCUS – TRENDS & COMPANIES 20 3.1 Cloud Providers Provide Enhanced Security, Including AI/ML and Zero Trust Security 20 3.2 Cloud Management and Cost Containment Becomes a Challenge for Customers 21 3.3 The Container Market is Just Starting to Heat Up 23 3.4 Kubernetes 24 3.5 APIs Have Become the Dominant Information Sharing Paradigm 27 3.6 DevOps is the Answer to Increasing Competition From Emerging Digital Disruptors. 30 3.7 Serverless 32 3.8 Zero Code 38 3.9 Hybrid, Multi and Edge Clouds 43 4 LARGE PUBLIC/PRIVATE ACQUIRERS 57 4.1 Amazon Web Services | Private Company Profile 57 4.2 Cloudera (NYS: CLDR) | Public Company Profile 59 4.3 Hortonworks | Private Company Profile 61 Infrastructure Software Report l Woodside Capital Partners l Confidential l October 2020 Page | 2 INFRAREPORT
    [Show full text]
  • Red Hat Hyperconverged Infrastructure for Cloud 13
    Red Hat Hyperconverged Infrastructure for Cloud 13 Release Notes Release notes for Red Hat Hyperconverged Infrastructure for Cloud Last Updated: 2018-07-13 Red Hat Hyperconverged Infrastructure for Cloud 13 Release Notes Release notes for Red Hat Hyperconverged Infrastructure for Cloud Legal Notice Copyright © 2018 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Openstack Cloud Learning
    Michael Mullins FILE:MULLINS.odp / / Page 1 Senior IT Specialist [email protected] OpenStack Cloud Learning 11th Swiss OpenStack User Group Meetup with Docker IBM Cloud Transformation Lab for Data Science Vulkanstrasse 106, 8010 Zurich, Switzerland Michael Mullins Mirantis OpenStack Certified Professional IBM Certified Solution Advisor Cloud Computing Architecture v4 Brocade Certified vRouter Engineer All opinions expressed in this presentation are my own Michael Mullins FILE:MULLINS.odp / / Page 2 Senior IT Specialist [email protected] Agenda Introduction Why we need to learn OpenStack? Why? OpenStack skills, supply & demand Sources of learning What? Learning roadmaps Hosted OpenStack trials & demos How? Building your own Summary Michael Mullins FILE:MULLINS.odp / / Page 3 Senior IT Specialist [email protected] Why we need to learn OpenStack? OpenStack Engineers make 36% more then an average cloud engineer – OpenStack foundation Mirantis Certified OpenStack Engineers make > $136K - Glassdoor 14 million Cloud jobs to be created by end of 2015 – BSA Software Alliance OpenStack is growing so fast that the talent pool is not deep enough to fill the positions available – Rackspace Last but not least, We like OpenStack Michael Mullins FILE:MULLINS.odp / / Page 4 Senior IT Specialist [email protected] OpenStack skills, supply & demand We are seeing shorter life cycles for Tech World Wide Web Smartphone Virtualisation Public Cloud lConsumer confidence Private Cloud lThe geek factor lOpEx versus CapEx Training
    [Show full text]
  • Brief: Openstack Is Now Ready for Business
    FOR CIOS Brief: OpenStack Is Now Ready For Business Robust Technology And A Strong Community Make This Open Source Cloud A Good Choice For Powering New Enterprise Applications by Paul Miller and Lauren E. Nelson September 9, 2015 | Updated: September 16, 2015 Why Read This Brief Key Takeaways The open source cloud computing project OpenStack Is Now A Technologically Credible OpenStack has come a long way since NASA Platform Upon Which To Grow and Rackspace launched it in 2010. Backed OpenStack’s latest release offers CIOs the right by leading technology infrastructure providers tools to build an agile BT estate in support of including Cisco, Dell, EMC, HP, IBM, Intel, and the applications for their organization’s rapidly VMware, OpenStack underpins significant expanding systems of engagement. Broad workloads at an increasingly diverse set of industry support for, and ongoing development of, organizations, including BMW, CERN, Comcast, the core open source components of OpenStack eBay, and Wal-Mart. For CIOs engaged in broader diminish the risk of vendor lock-in and expensive programs to win, serve, and retain customers — long-term licensing commitments. and refocus business technology (BT) spend — a Partners Make It Easier To Manage planned and pragmatic rollout of OpenStack OpenStack’s Remaining Rough Edges now demands serious consideration. This Some see strategic advantage in nurturing or brief highlights lessons learned by OpenStack hiring talent to build and manage all aspects of adopters, illustrating the technology’s role in their OpenStack deployment. But the dominant driving and sustaining change as CIOs move to model behind most successful OpenStack embrace the age of the customer.
    [Show full text]
  • Triliovault and Mirantis Cloud Platform the Smart Solution for Business Data Protection and Recovery
    SOLUTIONS SHEET TrilioVault and Mirantis Cloud Platform The Smart Solution for Business Data Protection and Recovery Introduction on OpenStack. More forward-looking DevOps groups are recognizing this and are building data protection Trilio, the creators of the first and only comprehensive solutions into their environments at the beginning of data protection platform native to OpenStack, is a their OpenStack journey. preferred provider of backup and recovery solutions for Mirantis Cloud Platform, offering enhanced data retention, protection, and integrity for workloads TrilioVault running on OpenStack. Organizations that rely on TrilioVault is the industry’s first native backup and Mirantis for their OpenStack deployments can have recovery solution for OpenStack. Developed out confidence knowing that tenants backed by the of Raksha – the first data-protection-as-a-service TrilioVault application and data recovery solution will specification for OpenStack – and authored by Trilio’s enjoy greater resiliency and operational efficiencies. founders, TrilioVault was designed and built from the ground up specifically for OpenStack. Adhering to OpenStack Benefits the characteristics required by cloud environments, TrilioVault’s flexible, fault-tolerant, forever scalable OpenStack transforms traditional data centers into solution provides seamless self-service, multi-tenant, software-defined infrastructure (networking, storage, policy-based comprehensive backup and rapid recovery essentially SD-everything). The widespread adoption of workloads running in OpenStack. Deployment can of OpenStack has made cloud infrastructure a source happen at any point in the journey and is completely of competitive advantage. non-disruptive. Overcoming Challenges Mirantis Once an OpenStack application goes into deployment, Mirantis Cloud Platform (MCP) is an agile, operations- backup and recovery—along with comprehensive data centric infrastructure platform that offers new protection—become a key business requirement.
    [Show full text]
  • MCP Salt Formulas Version Q4-18 Mirantis Cloud Platform Salt Formulas Documentation Version Latest
    MCP Salt Formulas version q4-18 Mirantis Cloud Platform Salt Formulas Documentation version latest Copyright notice 2021 Mirantis, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. No part of this publication may be reproduced in any written, electronic, recording, or photocopying form without written permission of Mirantis, Inc. Mirantis, Inc. reserves the right to modify the content of this document at any time without prior notice. Functionality described in the document may not be available at the moment. The document contains the latest information at the time of publication. Mirantis, Inc. and the Mirantis Logo are trademarks of Mirantis, Inc. and/or its affiliates in the United States an other countries. Third party trademarks, service marks, and names mentioned in this document are the properties of their respective owners. ©2021, Mirantis Inc. Page 2 Mirantis Cloud Platform Salt Formulas Documentation version latest Preface This documentation provides information on how to use Mirantis products to deploy cloud environments. The information is for reference purposes and is subject to change. Intended audience This documentation is intended for deployment engineers, system administrators, and developers; it assumes that the reader is already familiar with network and cloud concepts. Documentation history The following table lists the released revisions of this documentation: Revision date Description February 8, 2019 Q4`18 GA ©2021, Mirantis Inc. Page 3 Mirantis Cloud Platform Salt Formulas Documentation version latest List of Salt formulas supported in MCP Salt formulas are pre-written Salt states. They are open-ended and can be used for such tasks as package installation, service configuration and starting, users and permissions setup, and others.
    [Show full text]
  • Netscaler® 11.1 - Third Party Notices
    NetScaler® 11.1 - Third Party Notices NetScaler 11.1 may include third party software components licensed under the following terms. This list was generated using third party software as of the date listed. This list may change with specific versions of the product and may not be complete; it is provided “As-Is.” TO THE EXTENT PERMITTED BY APPLICABLE LAW, CITRIX AND ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, WITH REGARD TO THE LIST OR ITS ACCURACY OR COMPLETENESS, OR WITH RESPECT TO ANY RESULTS TO BE OBTAINED FROM USE OR DISTRIBUTION OF THE LIST. BY USING OR DISTRIBUTING THE LIST, YOU AGREE THAT IN NO EVENT SHALL CITRIX BE HELD LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY OTHER DAMAGES WHATSOEVER RESULTING FROM ANY USE OR DISTRIBUTION OF THIS LIST. 1 Table of Contents 7-Zip (win32) 9.20 ....................................................................................................................................... 12 Apache HTTP Server 2.2.14 ......................................................................................................................... 12 Apache Tomcat 7.0.69 ................................................................................................................................ 12 Apache Xalan-C 1.10.0 ................................................................................................................................ 12 Apache Xerces-C++ XML Parser 2.7.0 ........................................................................................................
    [Show full text]