This document discusses horizontal and vertical auto scaling concepts. It defines auto scaling as having three main components: monitoring systems that collect metrics, a decision support machine that applies rules to determine scaling actions, and a scaling engine that executes those actions. It provides examples of monitoring different resources, describes challenges in resolving conflicting rules, and lists some open source tools that can enable auto scaling functionality.
This document summarizes discussions from the PTG-Denver meeting. It outlines the agenda which included an introduction to PTG, highlighting discussion topics, recapping accomplishments in the Pike release, and plans for ongoing work in the Queens release. Key topics discussed were skip-release upgrades, API-SIG, and accomplishments across various OpenStack projects including Neutron, Cinder, Nova, Ironic, Glance, and Kolla from Pike and planned work for Queens.
This document discusses deploying IPv6 on OpenStack. It provides an overview of IPv6, including that IPv6 addresses the shortage of IPv4 addresses by providing a vastly larger 128-bit address space. It describes IPv6 address types and allocation methods. It also discusses IPv6 configuration modes in OpenStack, including stateless address autoconfiguration (SLAAC) and DHCPv6 stateless and stateful modes. Additionally, it covers deployment options for IPv6 on OpenStack like dual stack, NAT64/DNS64, and network tunnels. It provides details on IPv6 address and router advertisement configuration in OpenStack.
This document summarizes background information on OpenStack and discusses plans to promote OpenStack in Vietnam. Specifically, it defines cloud computing, outlines the key characteristics of cloud platforms, and lists some major OpenStack foundations and releases. It also provides examples of 8 successful OpenStack stories and discusses Vietnam's cloud computing market and challenges in adopting OpenStack locally. Finally, it outlines some initial experiments with OpenStack in Vietnam and plans to develop a roadmap with goals and ideas to further promote OpenStack adoption in the country through collaboration between companies, government, and universities.
Horizon now has a separate page for key pairs and API access in the Compute panel. The Floating IPs page is now located in the Network panel. Nova cells v2 is now required for OpenStack deployments in the Ocata release, requiring at least one new cell v2 configuration. Glance now supports a community image sharing feature allowing public access to shared images. Cinder now supports active-active high availability configurations for volume services.
The document recaps the 2017 OpenStack BOS Summit/Forum, noting that it had over 5,000 attendees, 750 sessions, and focused on containers, SDN/NFV, edge computing, and collaboration between communities. A keynote talk by Edward Snowden emphasized that closed source software and lack of user control over cloud infrastructure are issues.
This document discusses portgroups support in Ironic to provide link aggregation and fault tolerance capabilities. It describes the need for bonded interfaces to achieve high bandwidth and reliability. Key topics covered include Linux bonding driver modes, switch-side LAG configuration, creating port groups in Ironic, and associating ports. A demo shows static portgroups working in flat and multi-tenant network scenarios. Future work may allow dynamic portgroup configuration and additional bonding modes.
This document provides an overview of OpenStack Nova's architecture and code structure. It begins with an introduction to Nova's mission to provide scalable on-demand access to compute resources. It then covers Nova's core components, data flows, and code organization. Key aspects summarized include Nova's use of Cells to partition compute nodes, its facade design pattern for APIs, and its reliance on common OpenStack libraries like Oslo and Stevedore for configuration, logging, and extensibility.
The document discusses Ceph, an open source distributed storage platform that provides unified object, block, and file storage. It describes how the speaker's company Hostvn deployed Ceph in production, including using it with OpenStack. They started with a small proof-of-concept cluster using all SSD drives before expanding to a larger cluster with more nodes. Key lessons learned included keeping the design simple, monitoring performance closely during rebalancing, and realizing there is no one-size-fits-all model for Ceph deployment. Future plans include upgrading networking and replacing current storage with Ceph.
The document discusses the OpenStack Kilo release from the OpenStack Foundation. Some key points:
- Kilo aimed to create a stable core platform for interoperability and integrating new technologies.
- It focused on defining stable core services and saw key growth in integrated projects like Ironic for bare-metal provisioning.
- Major components like Nova, Keystone, Glance, Cinder, Neutron, Ceilometer, and Horizon received new features, improvements, and bug fixes related to areas like performance, security, manageability and advanced networking services.
- The discussion section raises questions about factors that would motivate upgrading to Kilo like improved stability, performance and flexibility, and challenges that may come with
The document discusses applying OpenStack at iNET, an IT company in Vietnam. It introduces the author who is leading OpenStack deployment and operations. It then outlines iNET's architecture which uses Mitaka OpenStack with bonded network and Ceph storage. Their plans are to migrate more servers and all customer VPS to OpenStack. Key challenges discussed are selecting an OpenStack version, covering all components, and testing performance with limited lab devices.
This document describes a simulation game to demonstrate contributing to open source software. The game uses kirigami, the Japanese art of paper cutting and folding, to simulate open source development roles and processes. Players will be divided into teams representing different open source groups like upstream developers, a company, and free software contributors. They will collaborate to plan and build different parts of a campus landscape with the goal of demonstrating open source best practices like communication, diplomacy, planning and review.
This document discusses booting virtual machines from volumes in OpenStack. It provides an overview of the Cinder block storage system and describes the booting process. It then details three booting methods - booting an instance from an image and attaching a non-bootable volume, booting from a bootable volume, and attaching swap or ephemeral disks. Steps are provided for creating and attaching both bootable and non-bootable volumes.
The document provides a recap of the OpenStack Austin Summit that took place from April 25-29, 2016 at the Austin Convention Center. It includes statistics about the summit such as over 7,500 attendees from 62 countries, 400+ sessions, and 1,200+ companies represented. It also summarizes some of the keynotes that discussed OpenStack adoption trends, the latest Mitaka release, and case studies from companies like SAP, Volkswagen Group, and AT&T that are using OpenStack in production.
Cloud computing involves computation done over the internet as a service. By 2020, cloud services are projected to be the primary IT consumption source for most individuals and enterprises, with the cloud computing market worth $241 billion. As computing moves to this new paradigm, IT jobs require new skills like virtualization, automation, security, and understanding IT as a service through models like SaaS, PaaS and IaaS. Cloud certifications and integrating cloud technologies into curricula can help develop these skills.
The document discusses making OpenStack controller core services highly available. It describes using Pacemaker and Corosync to manage virtual IP addresses and services across multiple nodes. HAProxy is used as a load balancer between the virtual IPs and service instances. The database uses Galera cluster for multi-master replication. RabbitMQ and Memcached are made highly available through clustering as well. Failure scenarios are tested by stopping nodes and services.
This document discusses horizontal and vertical auto scaling concepts. It defines auto scaling as having three main components: monitoring systems that collect metrics, a decision support machine that applies rules to determine scaling actions, and a scaling engine that executes those actions. It provides examples of monitoring different resources, describes challenges in resolving conflicting rules, and lists some open source tools that can enable auto scaling functionality.
This document summarizes discussions from the PTG-Denver meeting. It outlines the agenda which included an introduction to PTG, highlighting discussion topics, recapping accomplishments in the Pike release, and plans for ongoing work in the Queens release. Key topics discussed were skip-release upgrades, API-SIG, and accomplishments across various OpenStack projects including Neutron, Cinder, Nova, Ironic, Glance, and Kolla from Pike and planned work for Queens.
This document discusses deploying IPv6 on OpenStack. It provides an overview of IPv6, including that IPv6 addresses the shortage of IPv4 addresses by providing a vastly larger 128-bit address space. It describes IPv6 address types and allocation methods. It also discusses IPv6 configuration modes in OpenStack, including stateless address autoconfiguration (SLAAC) and DHCPv6 stateless and stateful modes. Additionally, it covers deployment options for IPv6 on OpenStack like dual stack, NAT64/DNS64, and network tunnels. It provides details on IPv6 address and router advertisement configuration in OpenStack.
This document summarizes background information on OpenStack and discusses plans to promote OpenStack in Vietnam. Specifically, it defines cloud computing, outlines the key characteristics of cloud platforms, and lists some major OpenStack foundations and releases. It also provides examples of 8 successful OpenStack stories and discusses Vietnam's cloud computing market and challenges in adopting OpenStack locally. Finally, it outlines some initial experiments with OpenStack in Vietnam and plans to develop a roadmap with goals and ideas to further promote OpenStack adoption in the country through collaboration between companies, government, and universities.
Horizon now has a separate page for key pairs and API access in the Compute panel. The Floating IPs page is now located in the Network panel. Nova cells v2 is now required for OpenStack deployments in the Ocata release, requiring at least one new cell v2 configuration. Glance now supports a community image sharing feature allowing public access to shared images. Cinder now supports active-active high availability configurations for volume services.
The document recaps the 2017 OpenStack BOS Summit/Forum, noting that it had over 5,000 attendees, 750 sessions, and focused on containers, SDN/NFV, edge computing, and collaboration between communities. A keynote talk by Edward Snowden emphasized that closed source software and lack of user control over cloud infrastructure are issues.
This document discusses portgroups support in Ironic to provide link aggregation and fault tolerance capabilities. It describes the need for bonded interfaces to achieve high bandwidth and reliability. Key topics covered include Linux bonding driver modes, switch-side LAG configuration, creating port groups in Ironic, and associating ports. A demo shows static portgroups working in flat and multi-tenant network scenarios. Future work may allow dynamic portgroup configuration and additional bonding modes.
This document provides an overview of OpenStack Nova's architecture and code structure. It begins with an introduction to Nova's mission to provide scalable on-demand access to compute resources. It then covers Nova's core components, data flows, and code organization. Key aspects summarized include Nova's use of Cells to partition compute nodes, its facade design pattern for APIs, and its reliance on common OpenStack libraries like Oslo and Stevedore for configuration, logging, and extensibility.
The document discusses Ceph, an open source distributed storage platform that provides unified object, block, and file storage. It describes how the speaker's company Hostvn deployed Ceph in production, including using it with OpenStack. They started with a small proof-of-concept cluster using all SSD drives before expanding to a larger cluster with more nodes. Key lessons learned included keeping the design simple, monitoring performance closely during rebalancing, and realizing there is no one-size-fits-all model for Ceph deployment. Future plans include upgrading networking and replacing current storage with Ceph.
The document discusses the OpenStack Kilo release from the OpenStack Foundation. Some key points:
- Kilo aimed to create a stable core platform for interoperability and integrating new technologies.
- It focused on defining stable core services and saw key growth in integrated projects like Ironic for bare-metal provisioning.
- Major components like Nova, Keystone, Glance, Cinder, Neutron, Ceilometer, and Horizon received new features, improvements, and bug fixes related to areas like performance, security, manageability and advanced networking services.
- The discussion section raises questions about factors that would motivate upgrading to Kilo like improved stability, performance and flexibility, and challenges that may come with
The document discusses applying OpenStack at iNET, an IT company in Vietnam. It introduces the author who is leading OpenStack deployment and operations. It then outlines iNET's architecture which uses Mitaka OpenStack with bonded network and Ceph storage. Their plans are to migrate more servers and all customer VPS to OpenStack. Key challenges discussed are selecting an OpenStack version, covering all components, and testing performance with limited lab devices.
This document describes a simulation game to demonstrate contributing to open source software. The game uses kirigami, the Japanese art of paper cutting and folding, to simulate open source development roles and processes. Players will be divided into teams representing different open source groups like upstream developers, a company, and free software contributors. They will collaborate to plan and build different parts of a campus landscape with the goal of demonstrating open source best practices like communication, diplomacy, planning and review.
This document discusses booting virtual machines from volumes in OpenStack. It provides an overview of the Cinder block storage system and describes the booting process. It then details three booting methods - booting an instance from an image and attaching a non-bootable volume, booting from a bootable volume, and attaching swap or ephemeral disks. Steps are provided for creating and attaching both bootable and non-bootable volumes.
The document provides a recap of the OpenStack Austin Summit that took place from April 25-29, 2016 at the Austin Convention Center. It includes statistics about the summit such as over 7,500 attendees from 62 countries, 400+ sessions, and 1,200+ companies represented. It also summarizes some of the keynotes that discussed OpenStack adoption trends, the latest Mitaka release, and case studies from companies like SAP, Volkswagen Group, and AT&T that are using OpenStack in production.
Cloud computing involves computation done over the internet as a service. By 2020, cloud services are projected to be the primary IT consumption source for most individuals and enterprises, with the cloud computing market worth $241 billion. As computing moves to this new paradigm, IT jobs require new skills like virtualization, automation, security, and understanding IT as a service through models like SaaS, PaaS and IaaS. Cloud certifications and integrating cloud technologies into curricula can help develop these skills.
The document discusses making OpenStack controller core services highly available. It describes using Pacemaker and Corosync to manage virtual IP addresses and services across multiple nodes. HAProxy is used as a load balancer between the virtual IPs and service instances. The database uses Galera cluster for multi-master replication. RabbitMQ and Memcached are made highly available through clustering as well. Failure scenarios are tested by stopping nodes and services.
Cấu hình Ubuntu server và cài đặt các bảo mật cần thiết:
1. Cài đặt tường lửa
2. Cài đặt antivirus
3. Cài đặt LAMP (Linux Apache, MySQL, PHP)
4. Cài đặt quản trị
Link server mẫu: http://megaurl.in/IZb9
This document compares Terraform and Pulumi infrastructure as code tools. It provides overviews of each tool, including what they are, how they work, and why to use them. For Terraform, it describes it as an IaC tool that defines cloud and on-premise resources in configuration files. For Pulumi, it notes it uses familiar programming languages for IaC. The document also compares key differences like syntax, testing, structuring large projects, and state file troubleshooting. It ends with best practices for both tools.
This document provides tips for becoming a "cool dad" through home automation. It discusses the author's experience transforming his home into a smart home using various devices that communicate over different protocols. Some challenges discussed are the separate apps required for each device, latency issues, security concerns, reliability, and ensuring a good user experience. The author advocates for a home automation system that is event-driven, runs locally at the edge rather than in the cloud, and focuses on simplicity rather than requiring users to adapt to the technology.
Vitastor is a fast and simple Ceph-like block storage solution that aims to maximize performance for SSDs and NVMEs. It focuses on block storage with fixed-size blocks rather than Ceph's object storage model. Vitastor uses a monitor, Etcd, and OSDs like Ceph but without a separate CRUSH layer and with monitors that do not store data. It supports technologies like RDMA for low latency and high throughput. The presenter's experiments showed Vitastor had improved performance over Ceph in some tests but also experienced some integration and operational issues.
This document discusses Zero touch on-premise storage infrastructure with OpenStack Cinder. It describes Viettel's IT infrastructure with mixed storage resources and the challenges of managing it. The solution presented uses OpenStack Cinder and additional tools to automate the management and provisioning of block storage for bare metal servers and OpenStack instances. This removes manual configuration steps and improves performance by pre-zoning storage connections. The goal is to make volume management simpler and allow adding new storage resources without additional configuration through the unified management solution.
This document discusses running MySQL on Kubernetes with Percona Kubernetes Operators. It provides an introduction to cloud native applications and Kubernetes. It then discusses the benefits and challenges of running MySQL on Kubernetes compared to database-as-a-service options. It introduces Percona Kubernetes Operators for MySQL, which help manage and configure MySQL deployments on Kubernetes. Finally, it discusses how to deploy MySQL with the Percona Kubernetes Operators, including prerequisites, connectivity, architecture, high availability, and monitoring.
Agile and DevOps are a great combination for software development. When combined, Agile adds structure to planned development work while DevOps incorporates unplanned work from operations teams. This allows for iterative development in small batches with test and delivery automation. It also improves team workflow by giving all members knowledge of the full development and operations lifecycle. Key practices include involving operations in sprint planning, automating workflows, implementing service backlogs under DevOps principles, using infrastructure as code tools, and including quality assurance at each phase. Measurement of outcomes helps ensure continuous improvement when applying Agile and DevOps together.
The document discusses establishing a true DevOps culture and environment. It begins by describing the traditional battle between developers and operations staff. DevOps aims to resolve this conflict by having developers and operations work together across the entire application lifecycle. The document then outlines some of the challenges in implementing DevOps and presents steps for establishing a true DevOps environment, including having a common language, planning infrastructure and processes together, coding to DevOps best practices, coordinating deployments, and centralizing monitoring and logs. Key aspects are involving all teams early, sharing information transparently, and avoiding prioritizing specific tools over collaboration.
This document describes the OpenStack Korea User Group's efforts to establish an upstream contribution mentoring program. It details how they struggled at first due to a lack of experience, but were eventually able to contribute by starting small, such as adding columns to the OpenStack client output and fixing test cases. Over two years, they developed a contribution academy program where mentees analyzed the OpenStack client code, mapped out unimplemented commands, and implemented some themselves. As a result of this ongoing mentoring effort, they have contributed several bug fixes, issues, new commands, and documentation improvements to the OpenStack upstream project.
The document discusses using Senlin, an OpenStack clustering service, to provide autoscaling capabilities for multicloud platforms. Senlin allows for managing clusters of nodes across different cloud providers and includes features like load balancing, auto-healing, and scaling policies. It describes how Senlin was implemented at a company to provide a centralized autoscaling solution across OpenStack and VMware cloud environments. Some drawbacks of Senlin are also outlined, along with potential future work like multi-region clusters and global load balancing.
This document discusses solutions for generating unique identifiers at high speeds. It compares auto-increment, UUID, hash, and Snowflake approaches. Snowflake is highlighted as able to generate up to 4 billion IDs per second while maintaining order, supporting distribution and sharding, and providing security benefits. The document outlines how Snowflake works by combining a timestamp, node ID determined via file, random number, IP address or ZooKeeper, and an increasing sequence number stored in Redis to generate the IDs at high speeds with strong ordering properties.
This document discusses upgrading an Openstack network to SDN with Tungsten Fabric. It evaluates three solutions: 1) using the same database across regions, 2) hot-swapping Open vSwitch and virtual routers, and 3) using an ML2 plugin. The recommended solution is #3 as it provides minimum downtime. Key steps include installing the OpenContrail driver, synchronizing network resources between Openstack and Tungsten, and live migrating VMs. Topology 2 is also recommended as it requires minimum changes. The upgrade migrated 80 VMs and 16 compute nodes to the SDN network without downtime. Issues discussed include synchronizing resources and migrating VMs between Open vSwitch and virtual routers.
Xuan-Thuy Dang gave a presentation about load balancing Kubernetes services on bare metal servers using Cilium. The presentation covered Industrial IoT, cloud computing, SDN and Cilium. It demonstrated how to use Cilium to provide load balancing for Kubernetes services running on bare metal servers and provided resources for further information.
Cluster API is a Kubernetes sub-project that provides declarative APIs and tooling to simplify provisioning, upgrading, and operating multiple Kubernetes clusters on any infrastructure. It works by having core Cluster API components along with plugins for different bootstrap, control-plane and infrastructure providers like Openstack, AWS, GCP etc. The presentation discusses Cluster API integration with Openstack, considerations for using it in production including separate internal and public connections and reusing Openstack networking, and proposes a time-saving deployment model leveraging various Cluster API and Gardener projects.
This document provides an overview of the Apache James email server project. It discusses James' support for common email protocols like SMTP, IMAP, and the newer JMAP standard. It also describes James' architecture, including its use of mailets and processors to customize email processing. The document recommends James for its flexibility, extensibility, and support for observability through structured logs and metrics.
More from Vietnam Open Infrastructure User Group (20)
4. 014
1.Up/Down
2.Băng thông
Các
thiết bị
mạng
1.Up/Down
2.API Response
time
3.Thống kê
OpenStack
Services
1.RAM,CPU
2.Storage
Giám sát
máy ảo
1.Trực quan
2. Tùy chỉnh
Hiển thị
1.Qua email
2.Qua SMS
Phương
thức cảnh
báo
1.RAM, DISK,
CPU
2.Net, File
System
Server
vật lý
Linh hoạt
mở rộng
1. Linh hoạt
2.Phân tán
1. Tại sao chọn Zabbix
Các bài toán
5. 015
Đánh giá
Bài toán
Cảnh báo
Linh hoạt mở rộng
Máy chủ vật lý
Các thiết bị mạng
Hiển thị
OpenStack Services
Máy ảo
Zabbix Nagios
Không có thông tin
Hạn chế
Shinken
Không có thông tin
Hạn chế
1. Tại sao chọn Zabbix
6. 016
Yêu cầu
hệ thống
Tìm hiểu
giải pháp
Thử nghiệm
LAB
So sánh
Đánh giáLựa chọnĐề xuất
1. Tại sao chọn Zabbix
20. 3. Triển khai Zabbix như thế nào 0115
Tìm hiểu giải pháp
Thử nghiệm
tính năng
Thiết kế
Triển khai
Tài liệu
Theo dõi hoạt động
Update, bổ sung
tính năng
Trao đổi, đánh giá,
báo cáo