This document discusses installing PHP7 on CentOS7 using Ansible. It provides commands to install the EPEL and Remi repositories, install PHP7 and related packages, and enable PHP7. It then shows how this process can be automated using Ansible roles and playbooks, including links to the example role and playbook on GitHub.
This document discusses the release of Symfony 3.0.0 and what is new compared to Symfony 2.x. Symfony 3.0 does not contain any new features, but rather focuses on compatibility layers and removing deprecated code and methods from Symfony 2.8. It provides a simple migration path for updating from Symfony 2.x to 3.0 using Composer. The key changes are removing deprecated functionality, standardizing the directory structure, and increasing the required PHP version to 5.5.9+.
This document discusses installing PHP7 on CentOS7 using Ansible. It provides commands to install the EPEL and Remi repositories, install PHP7 and related packages, and enable PHP7. It then shows how this process can be automated using Ansible roles and playbooks, including links to the example role and playbook on GitHub.
This document discusses the release of Symfony 3.0.0 and what is new compared to Symfony 2.x. Symfony 3.0 does not contain any new features, but rather focuses on compatibility layers and removing deprecated code and methods from Symfony 2.8. It provides a simple migration path for updating from Symfony 2.x to 3.0 using Composer. The key changes are removing deprecated functionality, standardizing the directory structure, and increasing the required PHP version to 5.5.9+.
This document discusses a FinTech company called Blue Payments that is moving its infrastructure to AWS. Blue Payments will deploy its applications across multiple Availability Zones using Amazon EC2, Amazon Aurora, Elastic Load Balancing, Amazon CloudFront, and Amazon Route 53. The infrastructure will be set up within a VPC with public subnets to provide high availability and scalability.
1) The document discusses compliance standards for financial services companies using AWS, including the Financial Services Information Sharing and Analysis Center (FISC), PCI DSS, NIST SP800, ISO/IEC 27001, and SOC2.
2) It provides an overview of the AWS shared responsibility model and lists AWS services and features that can help financial companies meet various compliance standards.
3) Resources are referenced for learning more about using AWS to meet FISC requirements, the Well-Architected Framework FSI Lens, baseline environments for financial institutions, and whitepapers on PCI DSS and NIST compliance on AWS.
Simple steps and tips to improve IT infrastructure operations #yapcasia #yapc...Yuichiro Saito
YAPC::Asia Tokyo 2015 (Day 2)
Follow-ups: http://www.koemu.com/blog/2015/08/24/yapcasia-tokyo-2015/
--- ABSTRACT ---
"Take away the pain !"
This is the keyword we defined to IT infrastructure operations two years ago.
I work for MSP company HEARTBEATS (MSP: IT Infrastructure Managed Service Provider Company).
At that time, IT infrastructure business was reached a turning point when IaaS(Infrastructure as a Service) was main currents of server system.
Then, we need to change our business strategy from the traditional approach.
This session, I'll talk about three themes as the person in charge of IT infrastructure operations, specially "Infrastructure as Code" that is only possible by MSP.
1: People WANT to talk about their problems
2: Involve closest person
3: Evaluating performance and beyond
First, I did two dimensional analysis: "Pain" and "Feasibility Solution".
There is no need of complex analysis !
Second, At HEARTBEATS, employee are all engineer except for general affairs.
I'll talk about conclusive factor of choice of pilot project, and a way of corporate pilot project member each other, that include some failed.
Third, we need to analyze of improvement operation.
Because, wrong approach doesn't lead profit increase.
【第54回 プログラミング・シンポジウム 発表資料 7-2】
Many new software development methods such as agile and iterative development require closer communication among developers compared to traditional ones. However today, many IT engineers are not good at communicating with others. Therefore, we are developing software engineer education curriculum with enhancement of communication skills (more specifically, consensus-building skills) in mind. We are adopting case-centered methods, in which both software development process and importance of consensus can be understood through actual experiences. For evaluation, we have applied our educational case method to six computer science undergraduates, composed in two groups of three persons each. As the result, consensus-building workshop in our curriculum was effective in achieving closer communication.
近年、アジャイルや反復開発など緊密なコミュニケーションを前提とする開発手法が普及してきている。しかし、他者とのコミュニケーションを拒むソフトウェア技術者の存在をはじめ、現在 のソフトウェア業界ではコミュニケーションスキルの向上は必ずしも実現されていない。そこで筆者らは、新人に対しコミュニケーションスキル、特に合意形成スキルを重視した技術者教育を行うことが重要だと考え、教育手法を設計・試行している。具体的には、開発プロセスをこなす中で合意形成の重要性を体験できるような、ケース中心の教育手法を採用している。その検証のため、大学4年生6名に集まってもらい、それぞれ3名のグループに分かれ、ケースを基に開発を進める実験を行った。その結果、コンセンサスを体感するワークショップを行う事で、コミュニケーションをより密にする開発を行う事が出来ることを確認した。