24/10/18 Open Session Summary
[Note: These are AI generated notes. They can be wildly inaccurate, sometimes in hilarious ways. I keep in the way AI generated it just to keep it interesting. Plus, I'm lazy]
Quick recap
The team discussed the evolution of application development, the benefits and challenges of using containers, and the differences between running containers on AWS using ECS and EKS. They also explored the concept of abstraction in computing, the importance of understanding the underlying layers of abstraction, and the role of code for resource orchestration. The conversation ended with a light-hearted discussion about Microsoft's logging issues and introductions from new attendees.
Summary
Water Polo Dedication, Workout Routines, and Dogs
Evolution of Application Development and Containers
Don to prepare a presentation on containers for next week's meeting, if schedule permits.
Kyle to reach out to community members for additional resume feedback.
Cloud Security Office Hours team to promote Discord channel to increase membership beyond 250 people.
Attendees to add their LinkedIn profiles in the chat for networking purposes.
Cloud Security Office Hours team to consider organizing more resume review sessions due to their high value.
Shawn compared the dedication of water polo players to other sports like basketball.
Patrick shared his daily workout routine and expressed interest in water polo.
Chris and Patrick discussed their dogs, Ripley and Ragnar, with Chris mentioning a setback with Ragnar's license and a potential appeal. They also discussed the possibility of using a friend's address if the appeal fails.
Bradley, a new attendee, introduced himself and shared how he found the meeting.
Shawn emphasized the meeting's open and interactive nature, inviting everyone to ask questions and share their experiences.
Shawn discussed the evolution of application development, highlighting the challenges faced in the past due to dependencies on the operating system and the difficulty in coordinating among multiple developers. He explained how virtualization and containers emerged as solutions, enabling portability and compatibility.
Containers allowed for the creation of micro-architectures, where each function could be its own package or container, with all containers working together to form a deployment.
Shawn also mentioned that David would have more insights on this topic.
Shawn discussed the benefits of using containers for application deployment, emphasizing their role in facilitating portability and accelerating development.
He highlighted how containers reduce dependency on specific environments and allow for deployment on-premises or in the cloud.
David added that containers help resolve issues with application compatibility across different platforms and hardware, and also accelerate deployment. He suggested that developers should aim for cloud-native solutions where possible to avoid relying on containers, which still require management.
Container Benefits, Challenges, and Deployment Strategies
Container Orchestration, Digital Twins, and Auto Scaling
Container and Virtual Machine Differences
Exploring Abstraction, CI/CD, and Cloud Roles
The team discussed the benefits and challenges of using containers in their operations.
David highlighted the difficulty of tracking and locating containers, especially when they are not well-documented.
Jay added that containers offer security benefits, such as isolating processes and restricting access to the file system, but emphasized the importance of proper configuration.
Shawn and Jay also discussed the importance of testing and approving versions before deployment, and the potential risks of using the latest version.
Don brought up the example of Crowdstrike's recent update, suggesting that inadequate testing and communication could have contributed to the issue.
The team agreed to continue the discussion on deployment methods and automation.
The team discussed the challenges of testing under load and the potential solution of digital twins.
Shawn shared his experience with the red and blue system from Novell and explained the role of containers in the ecosystem, emphasizing the need for an orchestrator like Kubernetes.
The team also discussed the benefits of auto scaling and self-healing in container orchestration, with a focus on cost efficiency and resilience.
The conversation concluded with an agreement to further explore the topic of ECS and EKS, with Ed expressing interest in understanding the difference between Amazon ECS and EKS.
The team discussed the differences between running containers on AWS using ECS and EKS, with a focus on the complexity of the topic.
They also explored the distinctions between containers and virtual machines, with Shawn explaining that containers are lighter weight and share the same OS kernel, while virtual machines have their own root user.
The team also touched on the concept of serverless, with Shawn explaining that it means not having control over the host, but being able to define what to run and where it runs.
The team discussed the concept of abstraction in computing, with Shawn and Jay emphasizing the importance of understanding the underlying layers of abstraction to effectively debug problems.
They also touched on the topic of continuous integration and continuous delivery (CI/CD), with Shawn explaining that it involves the automated processing and deployment of software.
D expressed interest in moving into cloud security and devops roles, and Shawn clarified that CI/CD is not exclusive to cloud or on-prem environments, but rather a development process that can be applied to both.
The team also briefly discussed the role of cloud specialists in managing the deployment of software.
Code Orchestration, CI/CD, and Agile Practices
Meeting sumary generated by AI. AI-generated content may be inaccurate or misleading. Always check for accuracy. Tryhackme series on container security Microsoft said it lost weeks of security logs for its customers' cloud products | TechCrunch CI/CD explained | Github
new
Jay discussed the benefits of using code for resource orchestration, including accuracy and error prevention, but mentioned potential configuration drift and the need for version control.
Aaron McKenzie compared CI/CD to car manufacturing, emphasizing quality control and distribution.
Brad noted that CI promotes code stability through post-commit testing.
isaac said a failed CI indicates the process is working properly.
The team agreed on the importance of agile practices and frequent, small changes.
Don was thanked for initiating the container discussion, and potentially leading the next session.
Shawn introduced Discord for networking conversations.
Chris encouraged new attendee introductions, and Bradley introduced himself, sharing his Silicon Valley startup and security background.
Michael offered to help others after collaborating with Kyle on his resume.
The team discussed a recent Azure logging issue, with Jay noting potential missing log entries.
The conversation ended with a light-hearted discussion about Microsoft's logging issues.
https://tryhackme.com/r/room/introtocontainerisation
https://tryhackme.com/module/container-security
https://github.com/resources/articles/devops/ci-cd
Here is todays summary of CSOH which was an interesting session about containers! Feel free to expand on any of the topics discussed here, or add anything that might have been missed. Also we now have a suggestions channel if you have any ideas for the group drop them in there.
Here is the great CI/CD infographic shared by David during the call
