Nền tảng AppViewX là một ứng dụng phần mềm mô-
đun, mã thấp (low-code) cho phép tự động hóa và
điều phối cơ sở hạ tầng mạng bằng cách sử dụng
quy trình làm việc trực quan, nhận biết ngữ cảnh, trực
quan.
Tận dụng một thư viện khổng lồ gồm các nhiệm vụ và
quy trình làm việc được xây dựng trước, nền tảng
này cho phép các nhóm Ops nhanh chóng và dễ dàng
chuyển các yêu cầu kinh doanh thành quy trình công
việc tự động hóa để cải thiện tính nhanh nhẹn, thực
thi tuân thủ, loại bỏ lỗi và giảm chi phí.
Nền tảng của chúng tôi hoạt động khép kín và có
nhận thức về trạng thái, có khả năng xác minh rằng
mục đích đã đạt được và cung cấp thông tin chi tiết
hữu ích và khắc phục tự động.
catalog Tổng đài LG-Ericsson IPECS eMG 803c telecom
catalog cho dòng Tổng đài LG Ericsson IPECS eMG80 sử dụng nền tảng tiên tiếp có khả năng kết nối cả tín hiệu analog và IP áp dụng cho mọi doanh nghiệp. iPECS eMG80 mang lại trải nghiệm người dùng cực đơn giản nhưng hiệu quả với các tính năng linh hoạt
Nền tảng AppViewX là một ứng dụng phần mềm mô-
đun, mã thấp (low-code) cho phép tự động hóa và
điều phối cơ sở hạ tầng mạng bằng cách sử dụng
quy trình làm việc trực quan, nhận biết ngữ cảnh, trực
quan.
Tận dụng một thư viện khổng lồ gồm các nhiệm vụ và
quy trình làm việc được xây dựng trước, nền tảng
này cho phép các nhóm Ops nhanh chóng và dễ dàng
chuyển các yêu cầu kinh doanh thành quy trình công
việc tự động hóa để cải thiện tính nhanh nhẹn, thực
thi tuân thủ, loại bỏ lỗi và giảm chi phí.
Nền tảng của chúng tôi hoạt động khép kín và có
nhận thức về trạng thái, có khả năng xác minh rằng
mục đích đã đạt được và cung cấp thông tin chi tiết
hữu ích và khắc phục tự động.
catalog Tổng đài LG-Ericsson IPECS eMG 803c telecom
catalog cho dòng Tổng đài LG Ericsson IPECS eMG80 sử dụng nền tảng tiên tiếp có khả năng kết nối cả tín hiệu analog và IP áp dụng cho mọi doanh nghiệp. iPECS eMG80 mang lại trải nghiệm người dùng cực đơn giản nhưng hiệu quả với các tính năng linh hoạt
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.
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.
2. AGENDA
1. Docker&Rancher information 2019 (K3S,Rancher2.23)
2. Rancher use case in Japan Market 2018,2019
3. Future Standard(AI IoT vender)
4. Local ISP :sakura internet,nifty cloud(MSP)
5. Rancher/Docker Training
6. information Openinfradays and Cloudnative days 2019 in JAPAN
7. Mediabridge Service
9. 5. Rancher/Docker Training
Rancher/Docker Training
Course information
2 days course
Learn fundamentals of Rancher/Docker
Learn Docker Engine installation, Rancher
server construction
Learn OSS tools and Rancher functions
Learn Kubernetes settings and operations
11. ベトナムの優秀な人材を日本へ
Đưa các kỹ sư Việt Nam đang ở Nhật Bản và Việt Nam vào
làm việc tại các công ty Nhật Bản
メディアブリッジの人材開発事業
人材開発アカデミーのご紹介
Học viện phát triển
nguồn nhân lực Mediabridge
7. Mediabridge Service
12. 『メディアブリッジ人材開発アカデミー』は、日本に住んで働きたいとい
う夢を持った若者に対して、日本の最先端の技術を身につけ働けるチャン
スを与えることが私たちの活動の目的です。
Học viện phát triển nguồn nhân lực có mục đích giúp các ứng viên có cơ
hội học tiếng Nhật và chuyên môn miễn phí.
Học viện nhân lực Mediabridge
メディアブリッジ人材開発アカデミー
メディアブリッジは、一人でも多くのエンジニアの夢をかなえるために、様々な
企業とのパートナーシップを広げ日本国内外での教育プログラムを充実させてい
ます。
Mediabridge đã phát triển chương trình giáo dục cả ở Việt Nam, Nhật Bản và đào
tạo có lương ở môi trường doanh nghiệp.