This document provides guidance on obtaining and modifying container images for use with Red Hat OpenStack Platform 13. It describes several methods for configuring a registry for container images, including using the local undercloud registry, the Red Hat registry, or a Satellite server. It also provides details on using the openstack overcloud container image prepare command to generate configuration files and lists of images, customize image tags and namespaces, and include additional services like Ceph storage that require special container images. The goal is to help users understand how to access and manage the container images needed for deploying and updating an OpenStack overcloud.
This document provides a summary of the Red Hat Enterprise Linux 7 System Administrator's Guide. It covers deployment, configuration, and administration of RHEL 7. The guide contains chapters on basic system configuration including networking, firewalls, SELinux, users/groups. Other chapters cover time/date configuration, subscriptions/software management, log files, and accessing Red Hat support. It is intended for system administrators with basic Linux knowledge.
003 red hat-enterprise_linux-6-dm_multipath-en-usGanesh Bagde
This document provides information about configuring and administering Device Mapper Multipathing (DM-Multipath) in Red Hat Enterprise Linux 6. It describes DM-Multipath components and setup, how to configure multipath devices, and troubleshooting multipath issues. The document contains chapters on multipath devices, setting up DM-Multipath, the DM-Multipath configuration file, and DM-Multipath administration and troubleshooting. It is intended to help system administrators manage systems using DM-Multipath for storage multipathing.
This document is the OpenStack Beginner's Guide for Ubuntu Precise edition. It provides an introduction to OpenStack components including Nova, Glance, Swift, Keystone and Horizon. It then describes how to install and configure these components on an Ubuntu server, including installing databases, configuring Keystone, Glance, Nova, Swift and Horizon.
- Configuration is stored as LDAP entries under cn=config within the directory
- Server plug-ins have their own configuration entries under cn=plugins,cn=config
- Configuration data is output to LDIF files located in /var/lib/dirsrv/instance/ldif
- Schema configuration files are located in /etc/dirsrv/instance/schema
- Core configuration attributes are referenced in an alphabetical listing
This document provides tuning guidelines for optimizing Oracle 9i and 10g database performance on Red Hat Enterprise Linux systems. It covers topics such as kernel tuning, memory configuration, I/O optimization, and use of large pages. The guidelines are applicable to Red Hat Enterprise Linux versions 2.1 through 5 for both 32-bit and 64-bit systems.
Red hat enterprise_linux-7-load_balancer_administration-en-uschakrikolla
This document provides an overview of load balancing technologies in Red Hat Enterprise Linux 7. It discusses the key components of a load balancer including Keepalived and HAProxy. Keepalived performs failover at the transport layer and load balancing using Linux Virtual Server, while HAProxy provides load balancing for HTTP and TCP services at the application layer. The document describes common load balancer configurations including basic and three-tier setups. It also covers load balancing scheduling methods and how Keepalived and HAProxy can work together for high availability.
This document provides an installation guide for OpenStack on Ubuntu 14.04. It describes installing and configuring the core OpenStack services including Identity, Compute, Image, Block Storage, Object Storage, Networking, Dashboard, Orchestration, and Telemetry. The guide walks through setting up the basic environment, installing each service on controller and compute nodes, and verifying their operation. It also discusses legacy networking and provides next steps after the initial installation.
Red hat open_stack_platform-10-manual_installation_procedures-en-usCesar Aguirre
This document provides instructions for manually installing Red Hat OpenStack Platform 10. It includes chapters on installing and configuring the various OpenStack services and components like the identity, object storage, block storage, compute, networking, dashboard, telemetry, and others. The document contains detailed steps for prerequisites, package installation, configuration, database setup, service validation and more. It is intended to be a reference for deploying OpenStack from scratch.
This document provides a summary of the Red Hat Enterprise Linux 7 System Administrator's Guide. It covers deployment, configuration, and administration of RHEL 7. The guide contains chapters on basic system configuration including networking, firewalls, SELinux, users/groups. Other chapters cover time/date configuration, subscriptions/software management, log files, and accessing Red Hat support. It is intended for system administrators with basic Linux knowledge.
003 red hat-enterprise_linux-6-dm_multipath-en-usGanesh Bagde
This document provides information about configuring and administering Device Mapper Multipathing (DM-Multipath) in Red Hat Enterprise Linux 6. It describes DM-Multipath components and setup, how to configure multipath devices, and troubleshooting multipath issues. The document contains chapters on multipath devices, setting up DM-Multipath, the DM-Multipath configuration file, and DM-Multipath administration and troubleshooting. It is intended to help system administrators manage systems using DM-Multipath for storage multipathing.
This document is the OpenStack Beginner's Guide for Ubuntu Precise edition. It provides an introduction to OpenStack components including Nova, Glance, Swift, Keystone and Horizon. It then describes how to install and configure these components on an Ubuntu server, including installing databases, configuring Keystone, Glance, Nova, Swift and Horizon.
- Configuration is stored as LDAP entries under cn=config within the directory
- Server plug-ins have their own configuration entries under cn=plugins,cn=config
- Configuration data is output to LDIF files located in /var/lib/dirsrv/instance/ldif
- Schema configuration files are located in /etc/dirsrv/instance/schema
- Core configuration attributes are referenced in an alphabetical listing
This document provides tuning guidelines for optimizing Oracle 9i and 10g database performance on Red Hat Enterprise Linux systems. It covers topics such as kernel tuning, memory configuration, I/O optimization, and use of large pages. The guidelines are applicable to Red Hat Enterprise Linux versions 2.1 through 5 for both 32-bit and 64-bit systems.
Red hat enterprise_linux-7-load_balancer_administration-en-uschakrikolla
This document provides an overview of load balancing technologies in Red Hat Enterprise Linux 7. It discusses the key components of a load balancer including Keepalived and HAProxy. Keepalived performs failover at the transport layer and load balancing using Linux Virtual Server, while HAProxy provides load balancing for HTTP and TCP services at the application layer. The document describes common load balancer configurations including basic and three-tier setups. It also covers load balancing scheduling methods and how Keepalived and HAProxy can work together for high availability.
This document provides an installation guide for OpenStack on Ubuntu 14.04. It describes installing and configuring the core OpenStack services including Identity, Compute, Image, Block Storage, Object Storage, Networking, Dashboard, Orchestration, and Telemetry. The guide walks through setting up the basic environment, installing each service on controller and compute nodes, and verifying their operation. It also discusses legacy networking and provides next steps after the initial installation.
Red hat open_stack_platform-10-manual_installation_procedures-en-usCesar Aguirre
This document provides instructions for manually installing Red Hat OpenStack Platform 10. It includes chapters on installing and configuring the various OpenStack services and components like the identity, object storage, block storage, compute, networking, dashboard, telemetry, and others. The document contains detailed steps for prerequisites, package installation, configuration, database setup, service validation and more. It is intended to be a reference for deploying OpenStack from scratch.
This document provides instructions for deploying a private Infrastructure as a Service (IaaS) cloud using Red Hat Cloud Foundations components. It describes setting up the necessary infrastructure services including the Red Hat Enterprise Linux, Red Hat Enterprise Virtualization, Red Hat Satellite, and JBoss middleware components. It then outlines the steps to deploy virtualization hosts, provision tenant virtual machines, and configure high availability clustering.
This document provides instructions for installing and configuring Cloudian object storage software and CloudBerry Lab products to enable cloud backup services. Key steps include installing Linux, Cloudian, third party software, and configuring Cloudian. Credentials from Cloudian can then be used to configure CloudBerry Managed Backup for offering backup services to customers using the private cloud storage. Standalone CloudBerry products like Backup, Explorer and Drive can also access the storage.
A- LES CONCEPTS
Comprehension du bim.
Travailler dans différentes vues.
Classement et hierarchie des éléments dans Revit.
B-L'ENVIRONNEMENT DE TRAVAIL
Page des fichiers rescents et grand R.
Le ruban.
Fenêtre des propriétés.
Explorateur du projet.
Navigation dans un modèle.(zoom, rotation et panoramique).
Selection des objets, et verouillage.
C-DEMARRAGE D'UN PROJET.
Les gabarits.
Travail collaboratif.
Configuration d'un nouveau projet.
Manipulation des niveaux.
Manipulation des files de projet.
Utilisation des cotes temporaires.
C- MODELISATION PAR OBJETS:
Ajout des murs.
Propriété et type de murs.
Utilisation des accroches.
Ajouts de poteaux et poutres.
Ajout de portes et fenêtres.
Ajout d'élements de plomberie et d'électricité.
Utilisation de la jonction entre murs.
Utilisation des contraintes.
D- LIENS, IMPORTS ET GROUPES:
Lier fichiers DWG/DXF/SKP
Création de topogrpahie d'un site à partir d'un fichier.
Création et gestion des groupes.
Création et gestion des liens Revit.
Utilisation du partage d'emplacement.
E- MODELISATION PAR ESQUISSE:
Sols., toits et plafonds.
Toit par extrusion.
Ouvertures.
F-ESCALIERS.
Edition avancée d'escalier.
Edition avancée de gardes corps.
G- EDITION AVANCEE DES MURS:
Création d'un nouveau type de murs..
Création et gestion des murs empilés.
Création et gestion des murs rideaux.
.
H- GESTION DES GRAPHISMES:
Gestion du style des objets.
Gestion du remplacement de la visibilité et du graphisme des éléments.
Création et application des gabarits de vue.
Cacher et isoler les éléments.
Cadrage de la vue.
Plage de vue et entendues.
Vue isométrique d'une selection.
Option d'affichage des graphismes.
I- PIECES:
Création et gestion des pièces.
J- NOMENCLATURE ET ETIQUETTES:
Gestion des étiquettes.
Création et gestion des nomenclatures.
Modification des nomenclatures.
Enrichissement des VCCTP par les nomenclatures.
K-ANNOTATIONS.
Textes.
Dimensions
Symboles.
Légendes.
Détails.
Définir ses annotations.
L- PARAMETRIQUE ET FAMILLES
Utilisation des paramètres en mode projet.
Concept de famille.
Création d'une famille.
Utilisation des contraintes.
Utilisation des formes solides.
M- FEUILLE, IMPRESSION, PUBLICATION:
Création d'une feuille d'impression.
Export CAO.
Publication.
Impression PDF.
N- TRUCS ET ASTUCES.
A découvrir en formation.
This document provides instructions for installing and configuring Cloudian object storage software and CloudBerry backup products to enable an individual or company to become a cloud backup provider using their own hardware. It outlines the requirements, installation steps, and configuration of Cloudian, Linux server, third party software, and CloudBerry Managed Backup. Following these steps allows one to offer cloud backup services to customers using a private cloud storage built on their own resources.
Red hat enterprise_linux-7-beta-installation_guide-en-usmuhammad adeel
This document provides an installation guide for Red Hat Enterprise Linux 7. It describes how to install RHEL 7 on AMD64, Intel 64, IBM Power Systems, and IBM System z architectures. The guide covers preparing installation media, planning hardware requirements, performing the installation, and troubleshooting installation issues. It also discusses advanced installation methods like Kickstart, PXE, and VNC installations.
This document provides a developer's guide for using the Oracle Service Bus (OSB) integrated development environment (IDE) to create and configure proxy services, business services, message flows, transformations, transports, and other OSB resources. It describes tasks like creating projects and folders, generating services from WSDLs, designing split-join message flows, debugging message flows, and more.
Deploying oracle rac 10g with asm on rhel and sles with svcwikiwei
This document provides guidance on configuring Oracle RAC 10g with ASM on Red Hat Linux and SUSE Linux using the IBM SAN Volume Controller (SVC). The SVC simplifies storage management by pooling storage from various systems into a single resource and enables nondisruptive data migration. It also improves availability through replication services. The document outlines configuring the SVC, device mapper multipath, and identifying storage on cluster nodes for ASM. It aims to demonstrate an easy configuration using these guidelines.
How to become cloud backup provider with Cloudian HyperStore and CloudBerry L...Cloudian
This document provides instructions for installing and configuring Cloudian object storage software and CloudBerry backup products to enable a company to become a cloud backup provider using their own hardware. It outlines requirements, installation steps for Linux, Cloudian, and CloudBerry software, and configuration of Cloudian and CloudBerry Managed Backup. Following these steps allows a company, especially a managed service provider, to offer cloud backup services to customers using their own private cloud storage infrastructure.
This document provides an overview and guide for implementing and tuning open source applications on IBM PowerLinux systems using virtualization. It introduces common open source applications for web, mail, file, print and network serving. It then describes considerations for installing the Virtual I/O Server (VIOS), creating virtual servers, installing Linux and applications. The guide also covers monitoring with Ganglia and performance tuning. It is intended to help professionals plan and deploy open source solutions on IBM PowerLinux infrastructure.
This document provides an overview and instructions for setting up an Oracle Database for use as a data warehouse, including preparing the hardware environment, configuring initialization parameters, and accessing Oracle Warehouse Builder. It also covers identifying data sources by importing metadata from various sources like flat files into Oracle Warehouse Builder. The document contains information to help users build and populate their Oracle Database data warehouse.
Software Defined Everything infrastructure that virtualizes compute, network, and storage resources and delivers it as a service. Rather than by the hardware components of the infrastructure, the management and control of the compute, network, and storage infrastructure are automated by intelligent software that is running on the Lenovo x86 platform.
This document introduces Subversion (SVN) as a version control system that improves upon CVS. It discusses downloading and using SVN clients like TortoiseSVN, describes how to set up a SVN repository for a project with multiple developers, and provides examples of common SVN commands like checking out files, committing changes, and updating a working copy.
Red Hat Enterprise Linux 5.2 Virtualization GuideRishi Sharma
This document is the Red Hat Enterprise Linux Virtualization Guide which contains information on installing, configuring, managing and troubleshooting virtualization technologies in Red Hat Enterprise Linux. It discusses system requirements, installation of virtualization packages and guests, configuration of virtualized devices, networks and security, administration of virtual machines, and includes a reference guide. It aims to provide all the information needed to work with virtualization in Red Hat Enterprise Linux.
Red hat enterprise_linux-6-logical_volume_manager_administration-en-usMohanKumar Palanichamy
This document provides a guide to administering the Logical Volume Manager (LVM) in Red Hat Enterprise Linux 6. It describes LVM components such as physical volumes, volume groups, and logical volumes. It also provides details on using LVM command line tools to perform tasks like creating and managing physical volumes, volume groups, linear, mirrored and striped logical volumes. The document includes examples and details managing LVM in a clustered environment.
The document is the Oracle Coherence Developer's Guide, Release 3.7. It provides contextual information, instructions, and examples to teach developers and architects how to use Oracle Coherence and develop Coherence-based applications. Coherence allows for clustered data management, uses a single API for logical operations and XML configuration for physical settings, and supports caching, various data storage and serialization options, and extensibility.
V mware service-def-private-cloud-11q1-white-paperChiến Nguyễn
This document defines a private cloud service using VMware technologies. It outlines a phased approach including initial goals of delivering a fully operational private cloud with 400 VMs and later enhancing it to support 1000 VMs and federation with public clouds. It describes common workload categories and use cases, defines service tiers with different resource models, roles and access rights, and chargeback/metering. It also provides suggestions for an initial vApp catalog.
This document describes the OpenACC API, which allows programmers to offload compute intensive regions of CPU code to attached accelerators like GPUs. It defines OpenACC directives, runtime routines, and environment variables. Directives are used to specify regions for offloading and augment compiler information. Runtime routines control device behavior and query properties. Environment variables also control device behavior.
This document provides instructions for installing and configuring a two-node Oracle RAC cluster using virtual machines on a single laptop or desktop computer. It details the necessary hardware requirements, including a minimum of 8GB RAM and 40GB free disk space. The software components needed are Windows 7 64-bit as the host operating system, along with VirtualBox for virtualization, Putty and VNC Viewer for remote access, and Oracle Grid Infrastructure and database software. The document provides a step-by-step guide to setting up the virtualized environment, installing Linux on the virtual machines, configuring the Grid Infrastructure and database software, and testing the overall cluster configuration.
- Oracle Data Integrator is a tool for integrating data between heterogeneous systems and applications. It has components for modeling data, designing interfaces, executing integration processes, and monitoring results.
- The core components include repositories to store metadata, a design studio to create interfaces and mappings, and run-time agents that execute integration processes.
- This guide will help users get started with Oracle Data Integrator by walking through installing the software, exploring an example ETL project, and learning how to design and run integrations.
A review of the growth of the Israel Genealogy Research Association Database Collection for the last 12 months. Our collection is now passed the 3 million mark and still growing. See which archives have contributed the most. See the different types of records we have, and which years have had records added. You can also see what we have for the future.
How to Manage Your Lost Opportunities in Odoo 17 CRMCeline George
Odoo 17 CRM allows us to track why we lose sales opportunities with "Lost Reasons." This helps analyze our sales process and identify areas for improvement. Here's how to configure lost reasons in Odoo 17 CRM
This document provides instructions for deploying a private Infrastructure as a Service (IaaS) cloud using Red Hat Cloud Foundations components. It describes setting up the necessary infrastructure services including the Red Hat Enterprise Linux, Red Hat Enterprise Virtualization, Red Hat Satellite, and JBoss middleware components. It then outlines the steps to deploy virtualization hosts, provision tenant virtual machines, and configure high availability clustering.
This document provides instructions for installing and configuring Cloudian object storage software and CloudBerry Lab products to enable cloud backup services. Key steps include installing Linux, Cloudian, third party software, and configuring Cloudian. Credentials from Cloudian can then be used to configure CloudBerry Managed Backup for offering backup services to customers using the private cloud storage. Standalone CloudBerry products like Backup, Explorer and Drive can also access the storage.
A- LES CONCEPTS
Comprehension du bim.
Travailler dans différentes vues.
Classement et hierarchie des éléments dans Revit.
B-L'ENVIRONNEMENT DE TRAVAIL
Page des fichiers rescents et grand R.
Le ruban.
Fenêtre des propriétés.
Explorateur du projet.
Navigation dans un modèle.(zoom, rotation et panoramique).
Selection des objets, et verouillage.
C-DEMARRAGE D'UN PROJET.
Les gabarits.
Travail collaboratif.
Configuration d'un nouveau projet.
Manipulation des niveaux.
Manipulation des files de projet.
Utilisation des cotes temporaires.
C- MODELISATION PAR OBJETS:
Ajout des murs.
Propriété et type de murs.
Utilisation des accroches.
Ajouts de poteaux et poutres.
Ajout de portes et fenêtres.
Ajout d'élements de plomberie et d'électricité.
Utilisation de la jonction entre murs.
Utilisation des contraintes.
D- LIENS, IMPORTS ET GROUPES:
Lier fichiers DWG/DXF/SKP
Création de topogrpahie d'un site à partir d'un fichier.
Création et gestion des groupes.
Création et gestion des liens Revit.
Utilisation du partage d'emplacement.
E- MODELISATION PAR ESQUISSE:
Sols., toits et plafonds.
Toit par extrusion.
Ouvertures.
F-ESCALIERS.
Edition avancée d'escalier.
Edition avancée de gardes corps.
G- EDITION AVANCEE DES MURS:
Création d'un nouveau type de murs..
Création et gestion des murs empilés.
Création et gestion des murs rideaux.
.
H- GESTION DES GRAPHISMES:
Gestion du style des objets.
Gestion du remplacement de la visibilité et du graphisme des éléments.
Création et application des gabarits de vue.
Cacher et isoler les éléments.
Cadrage de la vue.
Plage de vue et entendues.
Vue isométrique d'une selection.
Option d'affichage des graphismes.
I- PIECES:
Création et gestion des pièces.
J- NOMENCLATURE ET ETIQUETTES:
Gestion des étiquettes.
Création et gestion des nomenclatures.
Modification des nomenclatures.
Enrichissement des VCCTP par les nomenclatures.
K-ANNOTATIONS.
Textes.
Dimensions
Symboles.
Légendes.
Détails.
Définir ses annotations.
L- PARAMETRIQUE ET FAMILLES
Utilisation des paramètres en mode projet.
Concept de famille.
Création d'une famille.
Utilisation des contraintes.
Utilisation des formes solides.
M- FEUILLE, IMPRESSION, PUBLICATION:
Création d'une feuille d'impression.
Export CAO.
Publication.
Impression PDF.
N- TRUCS ET ASTUCES.
A découvrir en formation.
This document provides instructions for installing and configuring Cloudian object storage software and CloudBerry backup products to enable an individual or company to become a cloud backup provider using their own hardware. It outlines the requirements, installation steps, and configuration of Cloudian, Linux server, third party software, and CloudBerry Managed Backup. Following these steps allows one to offer cloud backup services to customers using a private cloud storage built on their own resources.
Red hat enterprise_linux-7-beta-installation_guide-en-usmuhammad adeel
This document provides an installation guide for Red Hat Enterprise Linux 7. It describes how to install RHEL 7 on AMD64, Intel 64, IBM Power Systems, and IBM System z architectures. The guide covers preparing installation media, planning hardware requirements, performing the installation, and troubleshooting installation issues. It also discusses advanced installation methods like Kickstart, PXE, and VNC installations.
This document provides a developer's guide for using the Oracle Service Bus (OSB) integrated development environment (IDE) to create and configure proxy services, business services, message flows, transformations, transports, and other OSB resources. It describes tasks like creating projects and folders, generating services from WSDLs, designing split-join message flows, debugging message flows, and more.
Deploying oracle rac 10g with asm on rhel and sles with svcwikiwei
This document provides guidance on configuring Oracle RAC 10g with ASM on Red Hat Linux and SUSE Linux using the IBM SAN Volume Controller (SVC). The SVC simplifies storage management by pooling storage from various systems into a single resource and enables nondisruptive data migration. It also improves availability through replication services. The document outlines configuring the SVC, device mapper multipath, and identifying storage on cluster nodes for ASM. It aims to demonstrate an easy configuration using these guidelines.
How to become cloud backup provider with Cloudian HyperStore and CloudBerry L...Cloudian
This document provides instructions for installing and configuring Cloudian object storage software and CloudBerry backup products to enable a company to become a cloud backup provider using their own hardware. It outlines requirements, installation steps for Linux, Cloudian, and CloudBerry software, and configuration of Cloudian and CloudBerry Managed Backup. Following these steps allows a company, especially a managed service provider, to offer cloud backup services to customers using their own private cloud storage infrastructure.
This document provides an overview and guide for implementing and tuning open source applications on IBM PowerLinux systems using virtualization. It introduces common open source applications for web, mail, file, print and network serving. It then describes considerations for installing the Virtual I/O Server (VIOS), creating virtual servers, installing Linux and applications. The guide also covers monitoring with Ganglia and performance tuning. It is intended to help professionals plan and deploy open source solutions on IBM PowerLinux infrastructure.
This document provides an overview and instructions for setting up an Oracle Database for use as a data warehouse, including preparing the hardware environment, configuring initialization parameters, and accessing Oracle Warehouse Builder. It also covers identifying data sources by importing metadata from various sources like flat files into Oracle Warehouse Builder. The document contains information to help users build and populate their Oracle Database data warehouse.
Software Defined Everything infrastructure that virtualizes compute, network, and storage resources and delivers it as a service. Rather than by the hardware components of the infrastructure, the management and control of the compute, network, and storage infrastructure are automated by intelligent software that is running on the Lenovo x86 platform.
This document introduces Subversion (SVN) as a version control system that improves upon CVS. It discusses downloading and using SVN clients like TortoiseSVN, describes how to set up a SVN repository for a project with multiple developers, and provides examples of common SVN commands like checking out files, committing changes, and updating a working copy.
Red Hat Enterprise Linux 5.2 Virtualization GuideRishi Sharma
This document is the Red Hat Enterprise Linux Virtualization Guide which contains information on installing, configuring, managing and troubleshooting virtualization technologies in Red Hat Enterprise Linux. It discusses system requirements, installation of virtualization packages and guests, configuration of virtualized devices, networks and security, administration of virtual machines, and includes a reference guide. It aims to provide all the information needed to work with virtualization in Red Hat Enterprise Linux.
Red hat enterprise_linux-6-logical_volume_manager_administration-en-usMohanKumar Palanichamy
This document provides a guide to administering the Logical Volume Manager (LVM) in Red Hat Enterprise Linux 6. It describes LVM components such as physical volumes, volume groups, and logical volumes. It also provides details on using LVM command line tools to perform tasks like creating and managing physical volumes, volume groups, linear, mirrored and striped logical volumes. The document includes examples and details managing LVM in a clustered environment.
The document is the Oracle Coherence Developer's Guide, Release 3.7. It provides contextual information, instructions, and examples to teach developers and architects how to use Oracle Coherence and develop Coherence-based applications. Coherence allows for clustered data management, uses a single API for logical operations and XML configuration for physical settings, and supports caching, various data storage and serialization options, and extensibility.
V mware service-def-private-cloud-11q1-white-paperChiến Nguyễn
This document defines a private cloud service using VMware technologies. It outlines a phased approach including initial goals of delivering a fully operational private cloud with 400 VMs and later enhancing it to support 1000 VMs and federation with public clouds. It describes common workload categories and use cases, defines service tiers with different resource models, roles and access rights, and chargeback/metering. It also provides suggestions for an initial vApp catalog.
This document describes the OpenACC API, which allows programmers to offload compute intensive regions of CPU code to attached accelerators like GPUs. It defines OpenACC directives, runtime routines, and environment variables. Directives are used to specify regions for offloading and augment compiler information. Runtime routines control device behavior and query properties. Environment variables also control device behavior.
This document provides instructions for installing and configuring a two-node Oracle RAC cluster using virtual machines on a single laptop or desktop computer. It details the necessary hardware requirements, including a minimum of 8GB RAM and 40GB free disk space. The software components needed are Windows 7 64-bit as the host operating system, along with VirtualBox for virtualization, Putty and VNC Viewer for remote access, and Oracle Grid Infrastructure and database software. The document provides a step-by-step guide to setting up the virtualized environment, installing Linux on the virtual machines, configuring the Grid Infrastructure and database software, and testing the overall cluster configuration.
- Oracle Data Integrator is a tool for integrating data between heterogeneous systems and applications. It has components for modeling data, designing interfaces, executing integration processes, and monitoring results.
- The core components include repositories to store metadata, a design studio to create interfaces and mappings, and run-time agents that execute integration processes.
- This guide will help users get started with Oracle Data Integrator by walking through installing the software, exploring an example ETL project, and learning how to design and run integrations.
A review of the growth of the Israel Genealogy Research Association Database Collection for the last 12 months. Our collection is now passed the 3 million mark and still growing. See which archives have contributed the most. See the different types of records we have, and which years have had records added. You can also see what we have for the future.
How to Manage Your Lost Opportunities in Odoo 17 CRMCeline George
Odoo 17 CRM allows us to track why we lose sales opportunities with "Lost Reasons." This helps analyze our sales process and identify areas for improvement. Here's how to configure lost reasons in Odoo 17 CRM
ISO/IEC 27001, ISO/IEC 42001, and GDPR: Best Practices for Implementation and...PECB
Denis is a dynamic and results-driven Chief Information Officer (CIO) with a distinguished career spanning information systems analysis and technical project management. With a proven track record of spearheading the design and delivery of cutting-edge Information Management solutions, he has consistently elevated business operations, streamlined reporting functions, and maximized process efficiency.
Certified as an ISO/IEC 27001: Information Security Management Systems (ISMS) Lead Implementer, Data Protection Officer, and Cyber Risks Analyst, Denis brings a heightened focus on data security, privacy, and cyber resilience to every endeavor.
His expertise extends across a diverse spectrum of reporting, database, and web development applications, underpinned by an exceptional grasp of data storage and virtualization technologies. His proficiency in application testing, database administration, and data cleansing ensures seamless execution of complex projects.
What sets Denis apart is his comprehensive understanding of Business and Systems Analysis technologies, honed through involvement in all phases of the Software Development Lifecycle (SDLC). From meticulous requirements gathering to precise analysis, innovative design, rigorous development, thorough testing, and successful implementation, he has consistently delivered exceptional results.
Throughout his career, he has taken on multifaceted roles, from leading technical project management teams to owning solutions that drive operational excellence. His conscientious and proactive approach is unwavering, whether he is working independently or collaboratively within a team. His ability to connect with colleagues on a personal level underscores his commitment to fostering a harmonious and productive workplace environment.
Date: May 29, 2024
Tags: Information Security, ISO/IEC 27001, ISO/IEC 42001, Artificial Intelligence, GDPR
-------------------------------------------------------------------------------
Find out more about ISO training and certification services
Training: ISO/IEC 27001 Information Security Management System - EN | PECB
ISO/IEC 42001 Artificial Intelligence Management System - EN | PECB
General Data Protection Regulation (GDPR) - Training Courses - EN | PECB
Webinars: https://pecb.com/webinars
Article: https://pecb.com/article
-------------------------------------------------------------------------------
For more information about PECB:
Website: https://pecb.com/
LinkedIn: https://www.linkedin.com/company/pecb/
Facebook: https://www.facebook.com/PECBInternational/
Slideshare: http://www.slideshare.net/PECBCERTIFICATION
हिंदी वर्णमाला पीपीटी, hindi alphabet PPT presentation, hindi varnamala PPT, Hindi Varnamala pdf, हिंदी स्वर, हिंदी व्यंजन, sikhiye hindi varnmala, dr. mulla adam ali, hindi language and literature, hindi alphabet with drawing, hindi alphabet pdf, hindi varnamala for childrens, hindi language, hindi varnamala practice for kids, https://www.drmullaadamali.com
This slide is special for master students (MIBS & MIFB) in UUM. Also useful for readers who are interested in the topic of contemporary Islamic banking.
The simplified electron and muon model, Oscillating Spacetime: The Foundation...RitikBhardwaj56
Discover the Simplified Electron and Muon Model: A New Wave-Based Approach to Understanding Particles delves into a groundbreaking theory that presents electrons and muons as rotating soliton waves within oscillating spacetime. Geared towards students, researchers, and science buffs, this book breaks down complex ideas into simple explanations. It covers topics such as electron waves, temporal dynamics, and the implications of this model on particle physics. With clear illustrations and easy-to-follow explanations, readers will gain a new outlook on the universe's fundamental nature.
it describes the bony anatomy including the femoral head , acetabulum, labrum . also discusses the capsule , ligaments . muscle that act on the hip joint and the range of motion are outlined. factors affecting hip joint stability and weight transmission through the joint are summarized.
How to Add Chatter in the odoo 17 ERP ModuleCeline George
In Odoo, the chatter is like a chat tool that helps you work together on records. You can leave notes and track things, making it easier to talk with your team and partners. Inside chatter, all communication history, activity, and changes will be displayed.
Digital Artefact 1 - Tiny Home Environmental Design
Trans.pdf
1. Red Hat OpenStack Platform 13
Transitioning to Containerized Services
A basic guide to working with OpenStack Platform containerized services
Last Updated: 2021-10-01
2.
3. Red Hat OpenStack Platform 13 Transitioning to Containerized Services
A basic guide to working with OpenStack Platform containerized services
OpenStack Team
rhos-docs@redhat.com
6. Red Hat OpenStack Platform 13 Transitioning to Containerized Services
2
7. CHAPTER 1. INTRODUCTION
Past versions of Red Hat OpenStack Platform used services managed with Systemd. However, more
recent version of OpenStack Platform now use containers to run services. Some administrators might
not have a good understanding of how containerized OpenStack Platform services operate, and so this
guide aims to help you understand OpenStack Platform container images and containerized services.
This includes:
How to obtain and modify container images
How to manage containerized services in the overcloud
Understanding how containers differ from Systemd services
The main goal is to help you gain enough knowledge of containerized OpenStack Platform services to
transition from a Systemd-based environment to a container-based environment.
1.1. CONTAINERIZED SERVICES AND KOLLA
Each of the main Red Hat OpenStack Platform (RHOSP) services run in containers. This provides a
method to keep each service within its own isolated namespace separated from the host. This has the
following effects:
During deployment, RHOSP pulls and runs container images from the Red Hat Customer Portal.
The podman command operates management functions, like starting and stopping services.
To upgrade containers, you must pull new container images and replace the existing containers
with newer versions.
Red Hat OpenStack Platform uses a set of containers built and managed with the Kolla toolset.
CHAPTER 1. INTRODUCTION
3
8. CHAPTER 2. OBTAINING AND MODIFYING CONTAINER
IMAGES
A containerized overcloud requires access to a registry with the required container images. This chapter
provides information on how to prepare the registry and your overcloud configuration to use container
images for Red Hat OpenStack Platform.
This guide provides several use cases to configure your overcloud to use a registry. Before attempting
one of these use cases, it is recommended to familiarize yourself with how to use the image preparation
command. See Section 2.2, “Container image preparation command usage” for more information.
2.1. REGISTRY METHODS
Red Hat OpenStack Platform supports the following registry types:
Remote Registry
The overcloud pulls container images directly from registry.redhat.io. This method is the easiest for
generating the initial configuration. However, each overcloud node pulls each image directly from the
Red Hat Container Catalog, which can cause network congestion and slower deployment. In addition,
all overcloud nodes require internet access to the Red Hat Container Catalog.
Local Registry
The undercloud uses the docker-distribution service to act as a registry. This allows the director to
synchronize the images from registry.redhat.io and push them to the docker-distribution registry.
When creating the overcloud, the overcloud pulls the container images from the undercloud’s
docker-distribution registry. This method allows you to store a registry internally, which can speed
up the deployment and decrease network congestion. However, the undercloud only acts as a basic
registry and provides limited life cycle management for container images.
NOTE
The docker-distribution service acts separately from docker. docker is used to pull and
push images to the docker-distribution registry and does not serve the images to the
overcloud. The overcloud pulls the images from the docker-distribution registry.
Satellite Server
Manage the complete application life cycle of your container images and publish them through a Red
Hat Satellite 6 server. The overcloud pulls the images from the Satellite server. This method provides
an enterprise grade solution to store, manage, and deploy Red Hat OpenStack Platform containers.
Select a method from the list and continue configuring your registry details.
NOTE
When building for a multi-architecture cloud, the local registry option is not supported.
2.2. CONTAINER IMAGE PREPARATION COMMAND USAGE
This section provides an overview on how to use the openstack overcloud container image prepare
command, including conceptual information on the command’s various options.
Generating a Container Image Environment File for the Overcloud
Red Hat OpenStack Platform 13 Transitioning to Containerized Services
4
9. One of the main uses of the openstack overcloud container image prepare command is to create an
environment file that contains a list of images the overcloud uses. You include this file with your
overcloud deployment commands, such as openstack overcloud deploy. The openstack overcloud
container image prepare command uses the following options for this function:
--output-env-file
Defines the resulting environment file name.
The following snippet is an example of this file’s contents:
parameter_defaults:
DockerAodhApiImage: registry.redhat.io/rhosp13/openstack-aodh-api:13.0-34
DockerAodhConfigImage: registry.redhat.io/rhosp13/openstack-aodh-api:13.0-34
...
The environment file also contains the DockerInsecureRegistryAddress parameter set to the IP
address and port of the undercloud registry. This parameter configures overcloud nodes to access
images from the undercloud registry without SSL/TLS certification.
Generating a Container Image List for Import Methods
If you aim to import the OpenStack Platform container images to a different registry source, you can
generate a list of images. The syntax of list is primarily used to import container images to the container
registry on the undercloud, but you can modify the format of this list to suit other import methods, such
as Red Hat Satellite 6.
The openstack overcloud container image prepare command uses the following options for this
function:
--output-images-file
Defines the resulting file name for the import list.
The following is an example of this file’s contents:
container_images:
- imagename: registry.redhat.io/rhosp13/openstack-aodh-api:13.0-34
- imagename: registry.redhat.io/rhosp13/openstack-aodh-evaluator:13.0-34
...
Setting the Namespace for Container Images
Both the --output-env-file and --output-images-file options require a namespace to generate the
resulting image locations. The openstack overcloud container image prepare command uses the
following options to set the source location of the container images to pull:
--namespace
Defines the namespace for the container images. This is usually a hostname or IP address with a
directory.
--prefix
Defines the prefix to add before the image names.
As a result, the director generates the image names using the following format:
[NAMESPACE]/[PREFIX][IMAGE NAME]
CHAPTER 2. OBTAINING AND MODIFYING CONTAINER IMAGES
5
10. Setting Container Image Tags
Use the --tag and --tag-from-label options together to set the tag for each container images.
--tag
Sets the specific tag for all images from the source. If you only use this option, director pulls all
container images using this tag. However, if you use this option in combination with --tag-from-label,
director uses the --tag as a source image to identify a specific version tag based on labels. The --tag
option is set to latest by default.
--tag-from-label
Use the value of specified container image labels to discover and pull the versioned tag for every
image. Director inspects each container image tagged with the value that you set for --tag, then uses
the container image labels to construct a new tag, which director pulls from the registry. For example,
if you set --tag-from-label {version}-{release}, director uses the version and release labels to
construct a new tag. For one container, version might be set to 13.0 and release might be set to 34,
which results in the tag 13.0-34.
IMPORTANT
The Red Hat Container Registry uses a specific version format to tag all Red Hat
OpenStack Platform container images. This version format is {version}-{release}, which
each container image stores as labels in the container metadata. This version format
helps facilitate updates from one {release} to the next. For this reason, you must always
use the --tag-from-label {version}-{release} when running the openstack overcloud
container image prepare command. Do not only use --tag on its own to to pull container
images. For example, using --tag latest by itself causes problems when performing
updates because director requires a change in tag to update a container image.
2.3. CONTAINER IMAGES FOR ADDITIONAL SERVICES
The director only prepares container images for core OpenStack Platform Services. Some additional
features use services that require additional container images. You enable these services with
environment files. The openstack overcloud container image prepare command uses the following
option to include environment files and their respective container images:
-e
Include environment files to enable additional container images.
The following table provides a sample list of additional services that use container images and their
respective environment file locations within the /usr/share/openstack-tripleo-heat-templates
directory.
Service Environment File
Ceph Storage environments/ceph-ansible/ceph-ansible.yaml
Collectd environments/services-docker/collectd.yaml
Congress environments/services-docker/congress.yaml
Fluentd environments/services-docker/fluentd.yaml
Red Hat OpenStack Platform 13 Transitioning to Containerized Services
6
11. OpenStack Bare Metal (ironic) environments/services-docker/ironic.yaml
OpenStack Data Processing
(sahara)
environments/services-docker/sahara.yaml
OpenStack EC2-API environments/services-docker/ec2-api.yaml
OpenStack Key Manager
(barbican)
environments/services-docker/barbican.yaml
OpenStack Load Balancing-as-a-
Service (octavia)
environments/services-docker/octavia.yaml
OpenStack Shared File System
Storage (manila)
environments/manila-{backend-name}-config.yaml
NOTE: See OpenStack Shared File System (manila)for more
information.
Open Virtual Network (OVN) environments/services-docker/neutron-ovn-dvr-ha.yaml
Sensu environments/services-docker/sensu-client.yaml
Service Environment File
The next few sections provide examples of including additional services.
Ceph Storage
If deploying a Red Hat Ceph Storage cluster with your overcloud, you need to include the
/usr/share/openstack-tripleo-heat-templates/environments/ceph-ansible/ceph-ansible.yaml
environment file. This file enables the composable containerized services in your overcloud and the
director needs to know these services are enabled to prepare their images.
In addition to this environment file, you also need to define the Ceph Storage container location, which is
different from the OpenStack Platform services. Use the --set option to set the following parameters
specific to Ceph Storage:
--set ceph_namespace
Defines the namespace for the Ceph Storage container image. This functions similar to the --
namespace option.
--set ceph_image
Defines the name of the Ceph Storage container image. Usually,this is rhceph-3-rhel7.
--set ceph_tag
Defines the tag to use for the Ceph Storage container image. This functions similar to the --tag
option. When --tag-from-label is specified, the versioned tag is discovered starting from this tag.
The following snippet is an example that includes Ceph Storage in your container image files:
$ openstack overcloud container image prepare
...
CHAPTER 2. OBTAINING AND MODIFYING CONTAINER IMAGES
7
12. -e /usr/share/openstack-tripleo-heat-templates/environments/ceph-ansible/ceph-ansible.yaml
--set ceph_namespace=registry.redhat.io/rhceph
--set ceph_image=rhceph-3-rhel7
--tag-from-label {version}-{release}
...
OpenStack Bare Metal (ironic)
If deploying OpenStack Bare Metal (ironic) in your overcloud, you need to include the
/usr/share/openstack-tripleo-heat-templates/environments/services-docker/ironic.yaml
environment file so the director can prepare the images. The following snippet is an example on how to
include this environment file:
$ openstack overcloud container image prepare
...
-e /usr/share/openstack-tripleo-heat-templates/environments/services-docker/ironic.yaml
...
OpenStack Data Processing (sahara)
If deploying OpenStack Data Processing (sahara) in your overcloud, you need to include the
/usr/share/openstack-tripleo-heat-templates/environments/services-docker/sahara.yaml
environment file so the director can prepare the images. The following snippet is an example on how to
include this environment file:
$ openstack overcloud container image prepare
...
-e /usr/share/openstack-tripleo-heat-templates/environments/services-docker/sahara.yaml
...
OpenStack Neutron SR-IOV
If deploying OpenStack Neutron SR-IOV in your overcloud, include the /usr/share/openstack-tripleo-
heat-templates/environments/services-docker/neutron-sriov.yaml environment file so the director
can prepare the images. The default Controller and Compute roles do not support the SR-IOV service,
so you must also use the -r option to include a custom roles file that contains SR-IOV services. The
following snippet is an example on how to include this environment file:
$ openstack overcloud container image prepare
...
-r ~/custom_roles_data.yaml
-e /usr/share/openstack-tripleo-heat-templates/environments/services-docker/neutron-sriov.yaml
...
OpenStack Load Balancing-as-a-Service (octavia)
If deploying OpenStack Load Balancing-as-a-Service in your overcloud, include the
/usr/share/openstack-tripleo-heat-templates/environments/services-docker/octavia.yaml
environment file so the director can prepare the images. The following snippet is an example on how to
include this environment file:
$ openstack overcloud container image prepare
...
-e /usr/share/openstack-tripleo-heat-templates/environments/services-docker/octavia.yaml
Red Hat OpenStack Platform 13 Transitioning to Containerized Services
8
13. ...
OpenStack Shared File System (manila)
Using the format manila-{backend-name}-config.yaml, you can choose a supported back end to
deploy the Shared File System with that back end. Shared File System service containers can be
prepared by including any of the following environment files:
environments/manila-isilon-config.yaml
environments/manila-netapp-config.yaml
environments/manila-vmax-config.yaml
environments/manila-cephfsnative-config.yaml
environments/manila-cephfsganesha-config.yaml
environments/manila-unity-config.yaml
environments/manila-vnx-config.yaml
For more information about customizing and deploying environment files, see the following resources:
Deploying the updated environment in CephFS via NFS Back End Guide for the Shared File
System Service
Deploy the Shared File System Service with NetApp Back Ends in NetApp Back End Guide for
the Shared File System Service
Deploy the Shared File System Service with a CephFS Back End in CephFS Back End Guide for
the Shared File System Service
2.4. USING THE RED HAT REGISTRY AS A REMOTE REGISTRY
SOURCE
Red Hat hosts the overcloud container images on registry.redhat.io. Pulling the images from a remote
registry is the simplest method because the registry is already configured and all you require is the URL
and namespace of the image that you want to pull. However, during overcloud creation, the overcloud
nodes all pull images from the remote repository, which can congest your external connection. As a
result, this method is not recommended for production environments. For production environments, use
one of the following methods instead:
Setup a local registry
Host the images on Red Hat Satellite 6
Procedure
1. To pull the images directly from registry.redhat.io in your overcloud deployment, an
environment file is required to specify the image parameters. Run the following command to
generate the container image environment file:
(undercloud) $ sudo openstack overcloud container image prepare
--namespace=registry.redhat.io/rhosp13
--prefix=openstack-
--tag-from-label {version}-{release}
--output-env-file=/home/stack/templates/overcloud_images.yaml
Use the -e option to include any environment files for optional services.
CHAPTER 2. OBTAINING AND MODIFYING CONTAINER IMAGES
9
14. Use the -r option to include a custom roles file.
If using Ceph Storage, include the additional parameters to define the Ceph Storage
container image location: --set ceph_namespace, --set ceph_image, --set ceph_tag.
2. Modify the overcloud_images.yaml file and include the following parameters to authenticate
with registry.redhat.io during deployment:
ContainerImageRegistryLogin: true
ContainerImageRegistryCredentials:
registry.redhat.io:
<USERNAME>: <PASSWORD>
Replace <USERNAME> and <PASSWORD> with your credentials for registry.redhat.io.
The overcloud_images.yaml file contains the image locations on the undercloud. Include
this file with your deployment.
NOTE
Before you run the openstack overcloud deploy command, you must log in
to the remote registry:
(undercloud) $ sudo docker login registry.redhat.io
The registry configuration is ready.
2.5. USING THE UNDERCLOUD AS A LOCAL REGISTRY
You can configure a local registry on the undercloud to store overcloud container images.
You can use director to pull each image from the registry.redhat.io and push each image to the
docker-distribution registry that runs on the undercloud. When you use director to create the
overcloud, during the overcloud creation process, the nodes pull the relevant images from the
undercloud docker-distribution registry.
This keeps network traffic for container images within your internal network, which does not congest
your external network connection and can speed the deployment process.
Procedure
1. Find the address of the local undercloud registry. The address uses the following pattern:
<REGISTRY_IP_ADDRESS>:8787
Use the IP address of your undercloud, which you previously set with the local_ip parameter in
your undercloud.conf file. For the commands below, the address is assumed to be
192.168.24.1:8787.
2. Log in to registry.redhat.io:
(undercloud) $ docker login registry.redhat.io --username $RH_USER --password
$RH_PASSWD
Red Hat OpenStack Platform 13 Transitioning to Containerized Services
10
15. 3. Create a template to upload the the images to the local registry, and the environment file to
refer to those images:
(undercloud) $ openstack overcloud container image prepare
--namespace=registry.redhat.io/rhosp13
--push-destination=192.168.24.1:8787
--prefix=openstack-
--tag-from-label {version}-{release}
--output-env-file=/home/stack/templates/overcloud_images.yaml
--output-images-file /home/stack/local_registry_images.yaml
Use the -e option to include any environment files for optional services.
Use the -r option to include a custom roles file.
If using Ceph Storage, include the additional parameters to define the Ceph Storage
container image location: --set ceph_namespace, --set ceph_image, --set ceph_tag.
4. Verify that the following two files have been created:
local_registry_images.yaml, which contains container image information from the remote
source. Use this file to pull the images from the Red Hat Container Registry
(registry.redhat.io) to the undercloud.
overcloud_images.yaml, which contains the eventual image locations on the undercloud.
You include this file with your deployment.
5. Pull the container images from the remote registry and push them to the undercloud registry:
(undercloud) $ openstack overcloud container image upload
--config-file /home/stack/local_registry_images.yaml
--verbose
Pulling the required images might take some time depending on the speed of your network and
your undercloud disk.
NOTE
The container images consume approximately 10 GB of disk space.
6. The images are now stored on the undercloud’s docker-distribution registry. To view the list of
images on the undercloud’s docker-distribution registry, run the following command:
(undercloud) $ curl http://192.168.24.1:8787/v2/_catalog | jq .repositories[]
NOTE
The _catalog resource by itself displays only 100 images. To display more
images, use the ?n=<interger> query string with the _catalog resource to
display a larger number of images:
(undercloud) $ curl http://192.168.24.1:8787/v2/_catalog?n=150 | jq
.repositories[]
CHAPTER 2. OBTAINING AND MODIFYING CONTAINER IMAGES
11
16. To view a list of tags for a specific image, use the skopeo command:
(undercloud) $ curl -s http://192.168.24.1:8787/v2/rhosp13/openstack-keystone/tags/list | jq
.tags
To verify a tagged image, use the skopeo command:
(undercloud) $ skopeo inspect --tls-verify=false
docker://192.168.24.1:8787/rhosp13/openstack-keystone:13.0-44
The registry configuration is ready.
2.6. USING A SATELLITE SERVER AS A REGISTRY
Red Hat Satellite 6 offers registry synchronization capabilities. This provides a method to pull multiple
images into a Satellite server and manage them as part of an application life cycle. The Satellite also acts
as a registry for other container-enabled systems to use. For more details information on managing
container images, see "Managing Container Images" in the Red Hat Satellite 6 Content Management
Guide.
The examples in this procedure use the hammer command line tool for Red Hat Satellite 6 and an
example organization called ACME. Substitute this organization for your own Satellite 6 organization.
Procedure
1. Create a template to pull images to the local registry:
$ source ~/stackrc
(undercloud) $ openstack overcloud container image prepare
--namespace=rhosp13
--prefix=openstack-
--output-images-file /home/stack/satellite_images
Use the -e option to include any environment files for optional services.
Use the -r option to include a custom roles file.
If using Ceph Storage, include the additional parameters to define the Ceph Storage
container image location: --set ceph_namespace, --set ceph_image, --set ceph_tag.
NOTE
This version of the openstack overcloud container image prepare command
targets the registry on the registry.redhat.io to generate an image list. It uses
different values than the openstack overcloud container image prepare
command used in a later step.
2. This creates a file called satellite_images with your container image information. You will use
this file to synchronize container images to your Satellite 6 server.
3. Remove the YAML-specific information from the satellite_images file and convert it into a flat
file containing only the list of images. The following sed commands accomplish this:
Red Hat OpenStack Platform 13 Transitioning to Containerized Services
12
17. (undercloud) $ awk -F ':' '{if (NR!=1) {gsub("[[:space:]]", ""); print $2}}' ~/satellite_images >
~/satellite_images_names
This provides a list of images that you pull into the Satellite server.
4. Copy the satellite_images_names file to a system that contains the Satellite 6 hammer tool.
Alternatively, use the instructions in the Hammer CLI Guide to install the hammer tool to the
undercloud.
5. Run the following hammer command to create a new product ( OSP13 Containers) to your
Satellite organization:
$ hammer product create
--organization "ACME"
--name "OSP13 Containers"
This custom product will contain our images.
6. Add the base container image to the product:
$ hammer repository create
--organization "ACME"
--product "OSP13 Containers"
--content-type docker
--url https://registry.redhat.io
--docker-upstream-name rhosp13/openstack-base
--name base
7. Add the overcloud container images from the satellite_images file.
$ while read IMAGE; do
IMAGENAME=$(echo $IMAGE | cut -d"/" -f2 | sed "s/openstack-//g" | sed "s/:.*//g") ;
hammer repository create
--organization "ACME"
--product "OSP13 Containers"
--content-type docker
--url https://registry.redhat.io
--docker-upstream-name $IMAGE
--name $IMAGENAME ; done < satellite_images_names
8. Synchronize the container images:
$ hammer product synchronize
--organization "ACME"
--name "OSP13 Containers"
Wait for the Satellite server to complete synchronization.
NOTE
Depending on your configuration, hammer might ask for your Satellite server
username and password. You can configure hammer to automatically login using
a configuration file. See the "Authentication" section in the Hammer CLI Guide.
CHAPTER 2. OBTAINING AND MODIFYING CONTAINER IMAGES
13
18. 9. If your Satellite 6 server uses content views, create a new content view version to incorporate
the images.
10. Check the tags available for the base image:
$ hammer docker tag list --repository "base"
--organization "ACME"
--product "OSP13 Containers"
This displays tags for the OpenStack Platform container images.
11. Return to the undercloud and generate an environment file for the images on your Satellite
server. The following is an example command for generating the environment file:
(undercloud) $ openstack overcloud container image prepare
--namespace=satellite6.example.com:5000
--prefix=acme-osp13_containers-
--tag-from-label {version}-{release}
--output-env-file=/home/stack/templates/overcloud_images.yaml
NOTE
This version of the openstack overcloud container image prepare command
targets the Satellite server. It uses different values than the openstack
overcloud container image prepare command used in a previous step.
When running this command, include the following data:
--namespace - The URL and port of the registry on the Satellite server. The default
registry port on Red Hat Satellite is 5000. For example, --
namespace=satellite6.example.com:5000.
--prefix= - The prefix is based on a Satellite 6 convention for labels, which uses lower case
characters and substitutes spaces for underscores. The prefix differs depending on whether
you use content views:
If you use content views, the structure is [org]-[environment]-[content view]-
[product]-. For example: acme-production-myosp13-osp13_containers-.
If you do not use content views, the structure is [org]-[product]-. For example: acme-
osp13_containers-.
--tag-from-label {version}-{release} - Identifies the latest tag for each image.
-e - Include any environment files for optional services.
-r - Include a custom roles file.
--set ceph_namespace, --set ceph_image, --set ceph_tag - If using Ceph Storage,
include the additional parameters to define the Ceph Storage container image location.
Note that ceph_image now includes a Satellite-specific prefix. This prefix is the same value
as the --prefix option. For example:
--set ceph_image=acme-osp13_containers-rhceph-3-rhel7
Red Hat OpenStack Platform 13 Transitioning to Containerized Services
14
19. This ensures the overcloud uses the Ceph container image using the Satellite naming
convention.
12. The overcloud_images.yaml file contains the image locations on the Satellite server. Include
this file with your deployment.
The registry configuration is ready.
2.7. MODIFYING CONTAINERS IMAGES
Red Hat provides a set of pre-built container images through the Red Hat Container Catalog
(registry.redhat.io). It is possible to modify these images and add additional layers to them. This is
useful for adding RPMs for certified 3rd party drivers to the containers.
NOTE
To ensure continued support for modified OpenStack Platform container images, ensure
that the resulting images comply with the "Red Hat Container Support Policy" .
This example shows how to customize the latest openstack-keystone image. However, these
instructions can also apply to other images:
Procedure
1. Pull the image you aim to modify. For example, for the openstack-keystone image:
$ sudo docker pull registry.redhat.io/rhosp13/openstack-keystone:latest
2. Check the default user on the original image. For example, for the openstack-keystone image:
$ sudo docker run -it registry.redhat.io/rhosp13/openstack-keystone:latest whoami
root
NOTE
The openstack-keystone image uses root as the default user. Other images use
specific users. For example, openstack-glance-api uses glance for the default
user.
3. Create a Dockerfile to build an additional layer on an existing container image. The following is
an example that pulls the latest OpenStack Identity (keystone) image from the Container
Catalog and installs a custom RPM file to the image:
FROM registry.redhat.io/rhosp13/openstack-keystone
MAINTAINER Acme
LABEL name="rhosp13/openstack-keystone-acme" vendor="Acme" version="2.1"
release="1"
# switch to root and install a custom RPM, etc.
USER root
COPY custom.rpm /tmp
RUN rpm -ivh /tmp/custom.rpm
CHAPTER 2. OBTAINING AND MODIFYING CONTAINER IMAGES
15
20. # switch the container back to the default user
USER root
4. Build and tag the new image. For example, to build with a local Dockerfile stored in the
/home/stack/keystone directory and tag it to your undercloud’s local registry:
$ docker build /home/stack/keystone -t "192.168.24.1:8787/rhosp13/openstack-keystone-
acme:rev1"
5. Push the resulting image to the undercloud’s local registry:
$ docker push 192.168.24.1:8787/rhosp13/openstack-keystone-acme:rev1
6. Edit your overcloud container images environment file (usually overcloud_images.yaml) and
change the appropriate parameter to use the custom container image.
WARNING
The Container Catalog publishes container images with a complete software stack
built into it. When the Container Catalog releases a container image with updates
and security fixes, your existing custom container will not include these updates and
will require rebuilding using the new image version from the Catalog.
Red Hat OpenStack Platform 13 Transitioning to Containerized Services
16
21. CHAPTER 3. DEPLOYING AND UPDATING AN OVERCLOUD
WITH CONTAINERS
This chapter provides info on how to create a container-based overcloud and keep it updated.
3.1. DEPLOYING AN OVERCLOUD
This procedure demonstrates how to deploy an overcloud with minimum configuration. The result will be
a basic two-node overcloud (1 Controller node, 1 Compute node).
Procedure
1. Source the stackrc file:
$ source ~/stackrc
2. Run the deploy command and include the file containing your overcloud image locations
(usually overcloud_images.yaml):
(undercloud) $ openstack overcloud deploy --templates
-e /home/stack/templates/overcloud_images.yaml
--ntp-server pool.ntp.org
3. Wait until the overcloud completes deployment.
3.2. UPDATING AN OVERCLOUD
For information on updating a containerized overcloud, see the Keeping Red Hat OpenStack Platform
Updated guide.
CHAPTER 3. DEPLOYING AND UPDATING AN OVERCLOUD WITH CONTAINERS
17
22. CHAPTER 4. WORKING WITH CONTAINERIZED SERVICES
This chapter provides some examples of commands to manage containers and how to troubleshoot your
OpenStack Platform containers
4.1. MANAGING CONTAINERIZED SERVICES
The overcloud runs most OpenStack Platform services in containers. In certain situations, you might
need to control the individual services on a host. This section provides some common docker
commands you can run on an overcloud node to manage containerized services. For more
comprehensive information on using docker to manage containers, see Working with Docker formatted
containers in the Getting Started with Containers guide.
NOTE
Before running these commands, check that you are logged into an overcloud node and
not running these commands on the undercloud.
Listing containers and images
To list running containers:
$ sudo docker ps
To also list stopped or failed containers, add the --all option:
$ sudo docker ps --all
To list container images:
$ sudo docker images
Inspecting container properties
To view the properties of a container or container images, use the docker inspect command. For
example, to inspect the keystone container:
$ sudo docker inspect keystone
Managing basic container operations
To restart a containerized service, use the docker restart command. For example, to restart the
keystone container:
$ sudo docker restart keystone
To stop a containerized service, use the docker stop command. For example, to stop the keystone
container:
$ sudo docker stop keystone
To start a stopped containerized service, use the docker start command. For example, to start the
keystone container:
Red Hat OpenStack Platform 13 Transitioning to Containerized Services
18
23. $ sudo docker start keystone
NOTE
Any changes to the service configuration files within the container revert after restarting
the container. This is because the container regenerates the service configuration based
upon files on the node’s local file system in /var/lib/config-data/puppet-generated/. For
example, if you edit /etc/keystone/keystone.conf within the keystone container and
restart the container, the container regenerates the configuration using /var/lib/config-
data/puppet-generated/keystone/etc/keystone/keystone.conf on the node’s local file
system, which overwrites any the changes made within the container before the restart.
Monitoring containers
To check the logs for a containerized service, use the docker logs command. For example, to view the
logs for the keystone container:
$ sudo docker logs keystone
Accessing containers
To enter the shell for a containerized service, use the docker exec command to launch /bin/bash. For
example, to enter the shell for the keystone container:
$ sudo docker exec -it keystone /bin/bash
To enter the shell for the keystone container as the root user:
$ sudo docker exec --user 0 -it <NAME OR ID> /bin/bash
To exit from the container:
# exit
4.2. TROUBLESHOOTING CONTAINERIZED SERVICES
If a containerized service fails during or after overcloud deployment, use the following recommendations
to determine the root cause for the failure:
NOTE
Before running these commands, check that you are logged into an overcloud node and
not running these commands on the undercloud.
Checking the container logs
Each container retains standard output from its main process. This output acts as a log to help
determine what actually occurs during a container run. For example, to view the log for the keystone
container, use the following command:
$ sudo docker logs keystone
CHAPTER 4. WORKING WITH CONTAINERIZED SERVICES
19
24. In most cases, this log provides the cause of a container’s failure.
Inspecting the container
In some situations, you might need to verify information about a container. For example, use the
following command to view keystone container data:
$ sudo docker inspect keystone
This provides a JSON object containing low-level configuration data. You can pipe the output to the jq
command to parse specific data. For example, to view the container mounts for the keystone container,
run the following command:
$ sudo docker inspect keystone | jq .[0].Mounts
You can also use the --format option to parse data to a single line, which is useful for running commands
against sets of container data. For example, to recreate the options used to run the keystone container,
use the following inspect command with the --format option:
$ sudo docker inspect --format='{{range .Config.Env}} -e "{{.}}" {{end}} {{range .Mounts}} -v
{{.Source}}:{{.Destination}}{{if .Mode}}:{{.Mode}}{{end}}{{end}} -ti {{.Config.Image}}' keystone
NOTE
The --format option uses Go syntax to create queries.
Use these options in conjunction with the docker run command to recreate the container for
troubleshooting purposes:
$ OPTIONS=$( sudo docker inspect --format='{{range .Config.Env}} -e "{{.}}" {{end}} {{range
.Mounts}} -v {{.Source}}:{{.Destination}}{{if .Mode}}:{{.Mode}}{{end}}{{end}} -ti {{.Config.Image}}'
keystone )
$ sudo docker run --rm $OPTIONS /bin/bash
Running commands in the container
In some cases, you might need to obtain information from within a container through a specific Bash
command. In this situation, use the following docker command to execute commands within a running
container. For example, to run a command in the keystone container:
$ sudo docker exec -ti keystone <COMMAND>
NOTE
The -ti options run the command through an interactive pseudoterminal.
Replace <COMMAND> with your desired command. For example, each container has a health check
script to verify the service connection. You can run the health check script for keystone with the
following command:
$ sudo docker exec -ti keystone /openstack/healthcheck
Red Hat OpenStack Platform 13 Transitioning to Containerized Services
20
25. To access the container’s shell, run docker exec using /bin/bash as the command:
$ sudo docker exec -ti keystone /bin/bash
Exporting a container
When a container fails, you might need to investigate the full contents of the file. In this case, you can
export the full file system of a container as a tar archive. For example, to export the keystone
container’s file system, run the following command:
$ sudo docker export keystone -o keystone.tar
This command create the keystone.tar archive, which you can extract and explore.
CHAPTER 4. WORKING WITH CONTAINERIZED SERVICES
21
26. CHAPTER 5. COMPARING SYSTEMD SERVICES TO
CONTAINERIZED SERVICES
This chapter provides some reference material to show how containerized services differ from Systemd
services.
5.1. SYSTEMD SERVICE COMMANDS VS CONTAINERIZED SERVICE
COMMANDS
The following table shows some similarities between Systemd-based commands and their Docker
equivalents. This helps identify the type of service operation you aim to perform.
Function Systemd-based Docker-based
List all services systemctl list-units -t service docker ps --all
List active services systemctl list-units -t service
--state active
docker ps
Check status of service systemctl status openstack-
nova-api
docker ps --filter
"name=nova_api$" --all
Stop service systemctl stop openstack-
nova-api
docker stop nova_api
Start service systemctl start openstack-
nova-api
docker start nova_api
Restart service systemctl restart openstack-
nova-api
docker restart nova_api
Show service configuration systemctl show openstack-
nova-api
systemctl cat openstack-
nova-api
docker inspect nova_api
Show service logs journalctl -u openstack-
nova-api
docker logs nova_api
5.2. SYSTEMD SERVICES VS CONTAINERIZED SERVICES
The following table shows Systemd-based OpenStack services and their container-based equivalents.
OpenStack service Systemd services Docker containers
Red Hat OpenStack Platform 13 Transitioning to Containerized Services
22
31. nova /var/log/nova/ /var/log/containers/nova/
/var/log/containers/httpd/nov
a-api/
/var/log/containers/httpd/nov
a-placement/
panko /var/log/containers/panko/
/var/log/containers/httpd/pan
ko-api/
rabbitmq /var/log/rabbitmq/ /var/log/containers/rabbitmq/
redis /var/log/redis/ /var/log/containers/redis/
swift /var/log/swift/ /var/log/containers/swift/
OpenStack service Systemd service logs Docker container logs
5.4. SYSTEMD CONFIGURATION VS CONTAINERIZED
CONFIGURATION
The following table shows Systemd-based OpenStack configuration and their equivalents for
containers. All container-based configuration locations are available on the physical host, are mounted
to the container, and are merged (via kolla) into the configuration within each respective container.
OpenStack service Systemd service configuration Docker container configuration
aodh /etc/aodh/ /var/lib/config-data/puppet-
generated/aodh/
ceilometer /etc/ceilometer/ /var/lib/config-data/puppet-
generated/ceilometer/etc/ceil
ometer/
cinder /etc/cinder/ /var/lib/config-data/puppet-
generated/cinder/etc/cinder/
glance /etc/glance/ /var/lib/config-data/puppet-
generated/glance_api/etc/gla
nce/
gnocchi /etc/gnocchi/ /var/lib/config-data/puppet-
generated/gnocchi/etc/gnocc
hi/
CHAPTER 5. COMPARING SYSTEMD SERVICES TO CONTAINERIZED SERVICES
27