SAP has transitioned from a purely centralized approach to user and project management in Perforce to a more decentralized model. They implemented a central user database synchronized to over 100 Perforce server instances. Initially, all administration was done centrally but they introduced "admin groups" allowing project managers to self-manage user access for their projects. They also allow any user to request access to projects and are piloting self-service project creation for mobile development projects to reduce wait times. Future plans include full self-service project creation across all projects and depots.
An overview of Teraproc cluster-as-a-service offerings for high-performance distributed analytics. This overview presentation includes a step-by-step demonstration of the process of deploying a ready-to-run R Studio cluster environment on Amazon Web Services. More information available at http://teraproc.com
Comparing the TCO of HP NonStop with Oracle RACThomas Burg
HP NonStop is often (wrongly!) perceived as "expensive", specifically compared with the combination of "vanilla X86 hardware" and the Oracle RAC DB offering.
This presentation talks about an in-depth analysis HP did to compare the two offerings fair and square. You might be surprised at the results ...
SharePoint Backup And Disaster Recovery with Joel OlesonJoel Oleson
This walks through the various options around backup and restore with SharePoint. This deck was presented at Tech Ed South East Asia 2008 by Joel Oleson
As opposed to databases for which established benchmarks have been driving the advancement of the field since a long time, workflow engines still lack a well-accepted benchmark that allows to give a fair comparison of their performance. In this talk we discuss the reasons and propose how to address the main challenges related to benchmarking these complex middleware systems at the core of business process automation and service composition solutions. In particular, we look at how to generate a representative workload and how to define suitable performance metrics. You will learn how to use our framework to measure the performance and resource consumption of your BPMN engine and compare different configurations to tune its performance in your concrete real-life project. The talk will also present preliminary experimental results obtained while benchmarking popular open source engines.
An overview of Teraproc cluster-as-a-service offerings for high-performance distributed analytics. This overview presentation includes a step-by-step demonstration of the process of deploying a ready-to-run R Studio cluster environment on Amazon Web Services. More information available at http://teraproc.com
Comparing the TCO of HP NonStop with Oracle RACThomas Burg
HP NonStop is often (wrongly!) perceived as "expensive", specifically compared with the combination of "vanilla X86 hardware" and the Oracle RAC DB offering.
This presentation talks about an in-depth analysis HP did to compare the two offerings fair and square. You might be surprised at the results ...
SharePoint Backup And Disaster Recovery with Joel OlesonJoel Oleson
This walks through the various options around backup and restore with SharePoint. This deck was presented at Tech Ed South East Asia 2008 by Joel Oleson
As opposed to databases for which established benchmarks have been driving the advancement of the field since a long time, workflow engines still lack a well-accepted benchmark that allows to give a fair comparison of their performance. In this talk we discuss the reasons and propose how to address the main challenges related to benchmarking these complex middleware systems at the core of business process automation and service composition solutions. In particular, we look at how to generate a representative workload and how to define suitable performance metrics. You will learn how to use our framework to measure the performance and resource consumption of your BPMN engine and compare different configurations to tune its performance in your concrete real-life project. The talk will also present preliminary experimental results obtained while benchmarking popular open source engines.
How Continuous Delivery Helped McKesson Create Award Winning ApplicationsPerforce
Healthcare has always had unique challenges, and as we move through the Affordable Care Act era, it requires new and stronger applications. Choosing the right tool to create and deploy these applications is critical. Hear how CI and CD (before we even knew the terms) contributed to the production of an award-winning electronic health record application, iKnowMed, and how those lessons learned continue to shape McKesson’s ongoing application development and deployment.
Could you release off your mainline today? In our fast paced world well scheduled releases have become a thing of the past. Now more then ever you must maintain clean well tested code lines that can be shipped at any moment. At the last Merge we talked about how these increased demands pushed Xilinx to develop automation that validates every change before submission. In this talk we will continue that discussion covering the evolution of our tools over the past two years as we have battled with more developers, more products, and a faster code churn the ever before.
Granular Protections Management with TriggersPerforce
Managing the Perforce Helix protections table can be unwieldy at best. Learn how we implemented a trigger-based system that removes the need for an administrator to manually edit the protections table. By granting ownership of individual projects or codelines in the protections table, we can allow project managers to control permissions to a path without worrying about mistakes that could affect the entire company.
Microservices allow for extensible app architecture and a vendor-agnostic, scalable infrastructure. While microservices simplify app deployments, they come at a price: because they’re so fragmented, it is more difficult to track and manage all the independent, yet interconnected components of an app. All this information (requirements, code, test cases and results, build artifacts, and deployment blueprints) needs to live somewhere and most importantly be versioned. Using a real example and a live demonstration of Perforce Helix, Docker and Selenium, get best practices and tips for enabling a robust, scalable and extensible pipeline to support today’s modern app delivery.
From ClearCase to Perforce Helix: Breakthroughs in Scalability at IntelPerforce
See how the Intel Security and Sensors Firmware team transitioned from IBM ClearCase to Perforce Helix with Microsoft TFS to enable robust and scalable ALM and CI with full traceability. Discover how Intel consolidated and converged 15 different development methodologies used to drive firmware projects to three single paths for all Intel platforms.
[Webinar] The Changing Role of Release Engineering in a DevOps World with J. ...Perforce
The rise of DevOps is revitalizing age-old topics in release engineering and application lifecycle management, and aspects of software delivery that DevOps doesn’t magically solve. If you're responsible for the release engineering function in your organization, see what the new world looks like and which aspects of the industry it’s leaving behind.
How Continuous Delivery Helped McKesson Create Award Winning ApplicationsPerforce
Healthcare has always had unique challenges, and as we move through the Affordable Care Act era, it requires new and stronger applications. Choosing the right tool to create and deploy these applications is critical. Hear how CI and CD (before we even knew the terms) contributed to the production of an award-winning electronic health record application, iKnowMed, and how those lessons learned continue to shape McKesson’s ongoing application development and deployment.
Could you release off your mainline today? In our fast paced world well scheduled releases have become a thing of the past. Now more then ever you must maintain clean well tested code lines that can be shipped at any moment. At the last Merge we talked about how these increased demands pushed Xilinx to develop automation that validates every change before submission. In this talk we will continue that discussion covering the evolution of our tools over the past two years as we have battled with more developers, more products, and a faster code churn the ever before.
Granular Protections Management with TriggersPerforce
Managing the Perforce Helix protections table can be unwieldy at best. Learn how we implemented a trigger-based system that removes the need for an administrator to manually edit the protections table. By granting ownership of individual projects or codelines in the protections table, we can allow project managers to control permissions to a path without worrying about mistakes that could affect the entire company.
Microservices allow for extensible app architecture and a vendor-agnostic, scalable infrastructure. While microservices simplify app deployments, they come at a price: because they’re so fragmented, it is more difficult to track and manage all the independent, yet interconnected components of an app. All this information (requirements, code, test cases and results, build artifacts, and deployment blueprints) needs to live somewhere and most importantly be versioned. Using a real example and a live demonstration of Perforce Helix, Docker and Selenium, get best practices and tips for enabling a robust, scalable and extensible pipeline to support today’s modern app delivery.
From ClearCase to Perforce Helix: Breakthroughs in Scalability at IntelPerforce
See how the Intel Security and Sensors Firmware team transitioned from IBM ClearCase to Perforce Helix with Microsoft TFS to enable robust and scalable ALM and CI with full traceability. Discover how Intel consolidated and converged 15 different development methodologies used to drive firmware projects to three single paths for all Intel platforms.
[Webinar] The Changing Role of Release Engineering in a DevOps World with J. ...Perforce
The rise of DevOps is revitalizing age-old topics in release engineering and application lifecycle management, and aspects of software delivery that DevOps doesn’t magically solve. If you're responsible for the release engineering function in your organization, see what the new world looks like and which aspects of the industry it’s leaving behind.
The presentation describes the functionality as well as the advantages of a project undertaken by us in the Cloud Computing course whereby we build a PaaS using Docker.
The link to the project is :
https://github.com/kanika2107/Paas_with_Docker_CloudProject
Demo video : https://www.youtube.com/watch?v=2h-hodrzTu8&feature=youtu.be
#IIITHyderabad #CloudComputing #CSE565 #Monsoon15 #SIEL #Docker #PaaS #Apache #Containers #PHP #SQL #HTML #Web2Py
Comparison of Several PaaS Cloud Computing Platformsijsrd.com
Today, the question is less about whether or not to use Platform as a Services (PaaS), but rather which providers to use. PaaS is a computing platform that abstracts the infrastructure, OS, and middleware to drive developer productivity. PaaS offerings are "polyglot" and "polyhost". Selection of Platform as a Service provider is an important process because an ideal vendor will be able to continue to partner with company as company grows. There are many components to be consider while selecting PaaS vendor like Scalability, Availability, Manageability, Performance, Security, Accessibility, Billing At a high-level a PaaS helps organizations, specifically by providing a fast and scalable way to host applications in the cloud.
Using Platform-As-A-Service (Paas) for Better Resource Utilization and Better...AM Publications
Popularity of cloud computing has increased many times in the last few years. One major driving force
behind this rapid increase in adoption of cloud is the economic benefits that the cloud provides. The benefits imply the
economies of scale that go with the pool of configurable computing resources which together constitute the cloud.
Cloud frees the user from the job of setting up and maintaining the computational infrastructure and helps him to
focus on developing and perfecting his application. Also the cloud provides the benefit of scaling (manual/real-time)
so that the application continues to work even under heavy load. However moving onto cloud is not an easy process
and requires planning. In this paper we review some techniques that have been used or proposed by research scholars
and cloud experts to create customized cloud platforms. These techniques can be used to design our own cloud
infrastructure to enable us to reap the benefits that cloud computing has to provide.
How to Organize Game Developers With Different Planning NeedsPerforce
Different skills have different needs when it comes to planning. For a coder it may make perfect sense to plan work in two-week sprints, but for an artist, an asset may take longer than two weeks to complete.
How do you allow different skills to plan the way that works best for them? Some studios may choose to open up for flexibility – do whatever you like! But that tends to cause issues with alignment and siloes of data, resulting in loss of vision. Lost vision in the sense that it is difficult to understand, but also — and maybe more importantly — the risk of losing the vision of what the game will be.
With the right approach, however, you can avoid these obstacles. Join backlog expert Johan Karlsson to learn:
-The balance of team autonomy and alignment.
-How to use the product backlog to align the project vision.
-How to use tools to support the flexibility you need.
Looking for a planning and backlog tool? You can try Hansoft for free.
Regulatory Traceability: How to Maintain Compliance, Quality, and Cost Effic...Perforce
How do regulations impact your product requirements? How do you ensure that you identify all the needed requirements changes to meet these regulations?
Ideally, your regulations should live alongside your product requirements, so you can trace among each related item. Getting to that point can be quite an undertaking, however. Ultimately you want a process that:
-Saves money
-Ensures quality
-Avoids fines
If you want help achieving these goals, this webinar is for you. Watch Tom Totenberg, Senior Solutions Engineer for Helix ALM, show you:
-How to import a regulation document into Helix ALM.
-How to link to requirements.
-How to automate impact analysis from regulatory updates.
Efficient Security Development and Testing Using Dynamic and Static Code Anal...Perforce
Be sure to register for a demo, if you would like to see how Klocwork can help ensure that your code is secure, reliable, and compliant.
https://www.perforce.com/products/klocwork/live-demo
If it’s not documented, it didn’t happen.
When it comes to compliance, if you’re doing the work, you need to prove it. That means having well-documented SOPs (standard operating procedures) in place for all your regulated workflows.
It also means logging your efforts to enforce these SOPs. They show that you took appropriate action in any number of scenarios, which can be related to regulations, change requests, firing of an employee, logging an HR compliant, or anything else that needs a structured workflow.
But when do you need to do this, and how do you go about it?
In this webinar, Tom Totenberg, our Helix ALM senior solutions engineer, clarifies workflow enforcement SOPs, along with a walkthrough of how Perforce manages GDPR (General Data Protection Regulation) requests. He’ll cover:
-What are SOPs?
-Why is it important to have this documentation?
-Example: walking through our internal Perforce GDPR process.
-What to beware of.
-Building the workflow in ALM.
Branching Out: How To Automate Your Development ProcessPerforce
If you could ship 20% faster, what would it mean for your business? What could you build? Better question, what’s slowing your teams down?
Teams struggle to manage branching and merging. For bigger teams and projects, it gets even more complex. Tracking development using a flowchart, team wiki, or a white board is ineffective. And attempts to automate with complex scripting are costly to maintain.
Remove the bottlenecks and automate your development your way with Perforce Streams –– the flexible branching model in Helix Core.
Join Brad Hart, Chief Technology Officer and Brent Schiestl, Senior Product Manager for Perforce version control to learn how Streams can:
-Automate and customize development and release processes.
-Easily track and propagate changes across teams.
-Boost end user efficiency while reducing errors and conflicts.
-Support multiple teams, parallel releases, component-based development, and more.
How to Do Code Reviews at Massive Scale For DevOpsPerforce
Code review is a critical part of your build process. And when you do code review right, you can streamline your build process and achieve DevOps.
Most code review tools work great when you have a team of 10 developers. But what happens when you need to scale code review to 1,000s of developers? Many will struggle. But you don’t need to.
Join our experts Johan Karlsson and Robert Cowham for a 30-minute webinar. You’ll learn:
-The problems with scaling code review from 10s to 100s to 1,000s of developers along with other dimensions of scale (files, reviews, size).
-The solutions for dealing with all dimensions of scale.
-How to utilize Helix Swarm at massive scale.
Ready to scale code review and streamline your build process? Get started with Helix Swarm, a code review tool for Helix Core.
By now many of us have had plenty of time to clean and tidy up our homes. But have you given your product backlog and task tracking software as much attention?
To keep your digital tools organized, it is important to avoid hoarding on to inefficient processes. By removing the clutter in your product backlog, you can keep your teams focused.
It’s time to spark joy by cleaning up your planning tools!
Join Johan Karlsson — our Agile and backlog expert — to learn how to:
-Apply digital minimalism to your tracking and planning.
-Organize your work by category.
-Motivate teams by transitioning to a cleaner way of working.
TRY HANSOFT FREE
Going Remote: Build Up Your Game Dev Team Perforce
Everyone’s working remote as a result of the coronavirus (COVID-19). And while game development has always been done with remote teams, there’s a new challenge facing the industry.
Your audience has always been mostly at home – now they may be stuck there. And they want more games to stay happy and entertained.
So, how can you enable your developers to get files and feedback faster to meet this rapidly growing demand?
In this webinar, you’ll learn:
-How to meet the increasing demand.
-Ways to empower your remote teams to build faster.
-Why Helix Core is the best way to maximize productivity.
Plus, we’ll share our favorite games keeping us happy in the midst of a pandemic.
Shift to Remote: How to Manage Your New WorkflowPerforce
The spread of coronavirus has fundamentally changed the way people work. Companies around the globe are making an abrupt shift in how they manage projects and teams to support their newly remote workers.
Organizing suddenly distributed teams means restructuring more than a standup. To facilitate this transition, teams need to update how they collaborate, manage workloads, and maintain projects.
At Perforce, we are here to help you maintain productivity. Join Johan Karlsson — our Agile expert — to learn how to:
Keep communication predictable and consistent.
-Increase visibility across teams.
-Organize projects, sprints, Kanban boards and more.
-Empower and support your remote workforce.
Hybrid Development Methodology in a Regulated WorldPerforce
In a regulated industry, collaboration can be vital to building quality products that meet compliance. But when an Agile team and a Waterfall team need to work together, it can feel like mixing oil with water.
If you're used to Agile methods, Waterfall can feel slow and unresponsive. From a Waterfall perspective, pure Agile may lack accountability and direction. Misaligned teams can slow progress, and expose your development to mistakes that undermine compliance.
It's possible to create the best of both worlds so your teams can operate together harmoniously. This is how to develop products quickly, and still make regulators happy.
Join ALM Solutions Engineer Tom Totenberg in this webinar to learn how teams can:
- Operate efficiently with differing methodologies.
- Glean best practices for their tailored hybrid.
- Work together in a single environment.
Watch the webinar, and when you're ready for a tool to help you with the hybrid, know that you can try Helix ALM for free.
Better, Faster, Easier: How to Make Git Really Work in the EnterprisePerforce
There's a lot of reasons to love Git. (Git is awesome at what it does.) Let’s look at the 3 major use cases for Git in the enterprise:
1. You work with third party or outsourced development teams.
2. You use open source in your products.
3. You have different workflow needs for different teams.
Making the best of Git can be difficult in an enterprise environment. Trying to manage all the moving parts is like herding cats.
So, how do you optimize your teams’ use of Git — and make it all fit into your vision of the enterprise SDLC?
You’ll learn about:
-The challenges that accompany each use case — third parties, open source code, different workflows.
-Ways to solve these problems.
-How to make Git better, faster, and easier — with Perforce
Easier Requirements Management Using Diagrams In Helix ALMPerforce
Sometimes requirements need visuals. Whether it’s a diagram that clarifies an idea or a screenshot to capture information, images can help you manage requirements more efficiently. And that means better quality products shipped faster.
In this webinar, Helix ALM Professional Services Consultant Gerhard Krüger will demonstrate how to use visuals in ALM to improve requirements. Learn how to:
-Share information faster than ever.
-Drag and drop your way to better teamwork.
-Integrate various types of visuals into your requirements.
-Utilize diagram and flowchart software for every need.
-And more!
Immediately apply the information in this webinar for even better requirements management using Helix ALM.
It’s common practice to keep a product backlog as small as possible, probably just 10-20 items. This works for single teams with one Product Owner and perhaps a Scrum Master.
But what if you have 100 Scrum teams managing a complex system of hardware and software components? What do you need to change to manage at such a massive scale?
Join backlog expert Johan Karlsson to learn how to:
-Adapt Agile product backlog practices to manage many backlogs.
-Enhance collaboration across disciplines.
-Leverage backlogs to align teams while giving them flexibility.
Achieving Software Safety, Security, and Reliability Part 3: What Does the Fu...Perforce
In Part 3, we will look at what the future might hold for embedded programming languages and development tools. And, we will look at the future for software safety and security standards.
How to Scale With Helix Core and Microsoft Azure Perforce
Microsoft Azure helps teams increase their speed, gain flexibility, and save time. Using Helix Core with Azure you maximizes cloud benefits. You can scale to meet both current and future deployment demands. And this powerful combination helps secure your most valuable IP assets.
So, where do you start? What do you need to set up your teams for success? How can you expedite your pipelines to deliver ahead of your competitors?
Join Chuck Gehman from Perforce to learn more about:
-Compute, storage, and security options from Azure.
-Strategies that boost your cloud investment.
-Tips to secure your data.
-Best practices for global deployments.
Achieving Software Safety, Security, and Reliability Part 2Perforce
In Part 2, we will focus on the automotive industry, as it leads the way in enforcing safety, security, and reliability standards as well as best practices for software development. We will then examine how other industries could adopt similar practices.
Modernizing an application’s architecture is often a necessary multi-year project in the making. The goal –– to stabilize code, detangle dependencies, and adopt a toolset that ignites innovation.
Moving your monolith repository to a microservices/component based development model might be on trend. But is it right for you?
Before you break up with anything, it is vital to assess your needs and existing environment to construct the right plan. This can minimize business risks and maximize your development potential.
Join Tom Tyler and Chuck Gehman to learn more about:
-Why you need to plan your move with the right approach.
-How to reduce risk when refactoring your monolithic repository.
-What you need to consider before migrating code.
Achieving Software Safety, Security, and Reliability Part 1: Common Industry ...Perforce
In part one of our three-part webinar series, we examine common software development challenges, review the safety and security standards adopted by different industries, and examine the best practices that can be applied to any software development team.
The features you’ve been waiting for! Helix ALM’s latest update expands usability and functionality to bring solid improvements to your processes.
Watch Helix ALM Senior Product Manager Paula Rome demonstrate how new features:
-Simplify workflows.
-Expand report analysis.
-Boost productivity in the Helix ALM web client.
All this and MORE packed into an exciting 30 minutes! Get inspired. Be extraordinary with the new Helix ALM.
Companies that track requirements, create traceability matrices, and complete audits - especially for compliance - run into many problems using only Word and Excel to accomplish these tasks.
Most notably, manual processes leave employees vulnerable to making costly mistakes and wasting valuable time.
These outdated tracking procedures rob organizations of benefiting from four keys to productivity and efficiency:
-Automation
-Collaboration
-Visibility
-Traceability
However, modern application lifecycle management (ALM) tools solve all of these problems, linking and organizing information into a single source of truth that is instantly auditable.
Gerhard Krüger, senior consultant for Helix ALM, explains how the right software supports these fundamentals, generating improvements that save time and money.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
GridMate - End to end testing is a critical piece to ensure quality and avoid...ThomasParaiso2
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
GridMate - End to end testing is a critical piece to ensure quality and avoid...
[SAP] Perforce Administrative Self Services at SAP
1.
MERGE 2013 THE PERFORCE CONFERENCE SAN FRANCISCO • APRIL 24−26
Perforce Administrative
Self- Services at SAP
Wolfram Kramer, SAP AG
Perforce White Paper
SAP changed the processes for user and group
administration and for project management step by
step from a purely centralistic approach to a much
leaner one.
2. 2 Perforce Administrative Self-Services at SAP
Background
SAP AG has used Perforce as its version control system for almost 15 years. The use of
Perforce has grown over time; currently, SAP hosts one of the largest Perforce server
installations in the world in terms of the number of licensed users: 10,000. In terms of the
number of productively used Perforce server instances, it is the largest one, with approximately
100. Many of the developers accessing Perforce use it to work with more than one instance.
Perforce implements a per-server user and group management for which instance-specific
protection tables are defined. It is evident that on the one hand, a synchronization of users,
groups, and also protection tables is necessary to ensure that any user gets access to all the
servers where he or she expects it. On the other hand, it is also clear that such a
synchronization of user and group data cannot be done manually on all the servers.
For this reason, early in the 21st century SAP implemented a central user and group storage
based on a relational database. The user and group data for each Perforce server instance are
synchronized from there. Manual user and group administration directly on a Perforce instance
(via p4 user or p4 group) was not done any more. The leading paradigm for the
implementation of the central user and group storage was a centralistic approach of user
management and any user and group management activities were done by a central team.
Tightly coupled with the scheme of permission groups and protections is the centralized
governed depot structure on any Perforce server at SAP. Versioned files are organized in so-
called projects as folders on the second level on the Perforce server directly below the depots.
The creation of projects and their code lines (organized in the third level below) is strictly
standardized and can only be done through a central infrastructure. Perforce triggers prohibit
adding new files outside an already existing project and/or code line. The design of the project
and code line creation process followed the paradigm of central administration by a central
team.
Although central teams are good at providing services in a workflow-like manner for
implementing and empowerment of governance, they are a hindrance in the context of lean
and agile principles because they are bottlenecks for the flow. They produce waiting time for
the requestors (project managers or developers) because the workflow still needs human
interaction by the central team. This white paper describes how SAP changed the processes
for user and group administration and for project management step by step from a purely
centralistic approach to a much leaner one with—in the ideal case—no more waiting time for
consumers.
Perforce Server Landscape and Centralized User Storage
The Perforce server landscape at SAP consists of:
• Approximately 100 Perforce server instances
• A relational database named “P4SAP” containing central metadata such as user, group,
and project data
• The P4 Management System P4MS as a framework of tools and services for data
manipulation on the P4SAP database
3. 3 Perforce
Administrative
Self-‐Services
at
SAP
• Tools and services for data synchronization from the P4SAP database to Perforce
servers, also integrated into P4MS
• Self-services and web services around P4MS to enable user interaction
Figure 1 illustrates the architecture:
Figure 1: Perforce server and user storage at SAP
Users and groups as parts of the metadata are stored and maintained on the P4SAP database
via the P4 Management System (P4MS). Each group that is stored in the database has a
specific validity scope of Perforce servers to which it is synchronized. This is because the
sources of certain larger products are distributed over more than one Perforce server. The
definitions of groups affecting accesses to the code base therefore have to be the same on
each Perforce server. This is ensured by the synchronization of the group from the P4SAP
database to all Perforce servers within the validity scope of the group.
Synchronization of user data to Perforce servers happens together with group synchronization.
The protection scheme at SAP assumes that any user gets permission through a group in
which the user is a member. As soon as the first group that contains the user as a member is
synchronized to a dedicated server, the user data is synchronized as well. This
synchronization ensures that any member of a group that exists on one Perforce server is also
a valid user defined on the Perforce server. From a technical point of view, P4MS uses p4 user
–i to create a user on the relevant Perforce servers.
Permission groups control the access to files within Perforce depots. At SAP, a standard
Perforce depot is structured along projects. A project is a location in the Perforce depot tree
that hosts the code for a subsystem of an SAP application. Because subsystems can have
their own release cycles, the code line level is below the project level, which ends up in a
Perforce depot structure (see Error! Reference source not found.).
Ruby
Dele
4. 4 Perforce Administrative Self-Services at SAP
Perforce creates folders as pure representations of the full path of versioned files, appearing
whenever a file having a new path is submitted. To prohibit wild creation of folder structures at
SAP’s Perforce servers, pre-submit triggers prevent the creation of new project and code line
folders. Creation of new projects is therefore also a task for the central Perforce team that
operates on request by the development teams. It has permission to circumvent the pre-submit
trigger for the creation of a first, empty file in the path of the new project. The purpose of this
first “createdir.txt” file is to make the path visible in the Perforce navigation tree. By this
operation, the pre-submit trigger is deactivated for future submits on the project path.
Currently, there are more than 9,000 projects; each has a lot of code lines. New code lines of a
project are usually needed for release branching. A service offered in the P4MS framework
automatically creates the needed code line as a folder in Perforce. Nevertheless, the creation
of new projects is still a manual, central activity.
Figure 2: At SAP, a standard Perforce depot is structured along projects
Design of Perforce Access Groups and Permissions
In the past, development teams followed a lot of different processes that slightly differed in
requirements concerning code line patterns, their naming, and their permission groups. But
one pattern applied to almost all variants contained two basic groups:
• A dev group that has permissions for writing to the dev code line where all new changes
are created; developers are typically members of this group.
• A patcher group that has permissions for writing on the qual code line that contains the
qualified, stable code; permissions to this code line usually have build operators and
quality managers.
5. 5 Perforce
Administrative
Self-‐Services
at
SAP
//product_X
project_A
dev
qual
dev
group
project_A-‐dev
patcher
group
project_A-‐patcher
write
read
write
write
Figure 3: Permissions are simplified for project admins at SAP
Although it is possible to apply this pattern on a per-project level, in most cases, this approach
is too finely granular. In general, a product consists of several projects that are contained in
one depot. The same people are working on any of the projects within the depot. Therefore,
the group pattern is often applied on a depot level: instead of groups like project_A-dev and
project B-dev, product_X-dev is used. This simplification means the project admin has to
maintain dev and patcher groups only once and not for each project separately (see Figure 3.)
Also the central Perforce team that creates new projects does not have to create new groups
or make new entries into the protection table. The latter are covered by entries using wildcards
such as:
write group product_X-dev * //product_X/*/dev/...
read group product_X-dev * //product_X/*/qual/...
write group product_X-patcher * //product_X/*/dev/...
write group product_X-patcher * //product_X/*/qual/...
Centralized User Management
Shortly after the introduction of Perforce in 2001, SAP began to distribute projects to more than
one Perforce server instance. After first developing intermediate solutions using script-based
copy of users from one server to another one, the central user and group storage described
above was introduced (see Figure 4). After that, it was possible for the central Perforce
operating team to use a web front end to maintain users and groups in the central database.
Groups were assigned to one or more Perforce instances. Publishing users and groups to the
Perforce server was done instantaneously by pressing the save button.
Ruby
Dele
6. 6 Perforce Administrative Self-Services at SAP
Figure 4: A web front end is used to maintain users and groups in the central database
It was a great step forward because per-instance maintenance of groups was no longer
needed. But still all requirements from developer teams were handled by processes based on
workflows. Typical scenarios handled by the central operating team were:
• Adding a user to a permission group to grant read or write access to a project; keep in
mind that the admin groups already mentioned did not yet exist.
• Creation of a new project including its permission groups.
There were of course tools that made the creation of a project as comfortable as possible for
the operation team; creation of the project and the groups was possible in one step. But the
strict centralization of any activity concerning user and project management turned out to be a
bottleneck: it was not scalable with the increasing number of projects. Instead, it created
waiting time for the developer teams and it ate up the time of the central Perforce operating
team, preventing it from investing in improvements to the infrastructure.
Group Member Self-Administration
The consequence was the insight that user management had to be decentralized. In fact, the
decision whether permissions on a project shall be granted to a specific user was not done by
the central team but by the responsible development manager of the project. This was when
the admin group for a project was introduced (see Figure 5).
The admin group has the purpose to modify the dev group and patcher group for a project and
for itself. It exists only inside P4MS and is in general not synchronized to Perforce servers at
all. Project managers are usually members of this group since they decide who should join as
developer or build operator of the project.
7. 7 Perforce
Administrative
Self-‐Services
at
SAP
//product_X
project_A
dev
qual
dev
group
project_A-‐dev
patcher
group
project_A-‐patcher
admin
group
project_a-‐admin
change
change
changewrite
read
write
write
Figure 5 An admin group was established to decentralize user management
P4MS has an own authorization concept that is able to assign P4MS-application specific
permissions to groups. Members of the admin groups of a project can modify the dev and
patcher groups in P4MS and thus in the P4SAP database. The synchronization mechanism
described above does the job to make these groups productive on the dedicated Perforce
servers.
By what has been described, the use case “I as a project manager would like to define the
group members who have access to my project” is covered. For the use case “I as a developer
would like to get access for a dedicated project,” the mechanism is not sufficient. The
assumption is unfortunately wrong that the developer could just write an email to his or her
project manager to add him or her into the project dev group. Often the developer does not
know who the project manager is.
Figure 6: Any employee is able to request access to a project in Perforce at SAP
To cover the second use case, P4MS offers a service by which any employee is able to
request access to a project in Perforce. This can be done in two ways: either the user knows
the name of the access group of the project he/she wants to be join or—and this happens in
8. 8 Perforce Administrative Self-Services at SAP
most cases because most people are not familiar with the group names—the user provides the
Perforce path of the project he or she want to get access to. In the latter case, the system finds
out by itself which project the path points to and what the name of the dev group is (see Figure
6).
Then the system determines the admin group that is able to maintain the dev group, and an
email is sent to members of the admin group. Via the link that is included in this email, any of
the addressed administrators is able to open the maintenance dialog for the dev group the
requesting user wants to join. After having pressed the button for approval, the user is added
to the group within the P4SAP database. The synchronization of the group to the affected
Perforce servers is scheduled and takes place within a few minutes asynchronously.
What makes this dialog so powerful is that a new Perforce user is created automatically on any
affected Perforce server where the user did not exist before. In this case, a strong random
password is created, and the user receives a generated email to set a password of his or her
choice. Hence the outlined workflow applies to already existing Perforce users who get access
to an additional project as well as for people who did not have a Perforce user before.
At this point, it is worthwhile to outline the procedure of setting passwords on SAP’s Perforce
servers. As already mentioned, many of the users have to connect to more than one Perforce
server. Letting them maintain and synchronize their passwords by themselves by applying the
p4 passwd command on each server would create much frustration. Therefore, the password
setting and distribution occur via a central service in P4MS that sets the password
automatically on each Perforce server on which the user is synchronized. For security reasons,
the passwords are not stored (not even encrypted) in the P4SAP database. Hence whenever
users get access to an additional server, they have to go through this service once again (but
with the advantage that, afterward, the password is the same on all Perforce servers).
Limited Local Perforce Project Control
Group administration has been successfully decentralized, but the creation of new projects and
code lines until recently was completely a central responsibility. But agility for the development
teams also means being able to create very quickly the prerequisites to start a new prototype
without any unnecessary loss of time. A project on a Perforce server belongs to the most basic
infrastructural pieces that enable developers to do their work. A central workflow to create a
project with all its waiting time and involvement of central people that does not directly add
value to the product does not fit any more. Therefore, SAP introduced a self-service for project
creation in a dedicated area where speed is crucial: projects hosting code for mobile
applications.
Ruby
Dele
9. 9 Perforce
Administrative
Self-‐Services
at
SAP
Figure 7: Self-service project creation at SAP
The solution enables project managers to create a project by themselves without having to
request project creation from a central team. The self-service asks the project manager for a
project name; provided that the name is not yet in use, the project is created (i.e., the
corresponding path on the Perforce server is created) (see Figure 7).
So far, this self-service is only able to create the project in one single depot on one single
server hosting all SAP mobile applications. Also the permission concept is so far rather
pragmatically solved: for all the projects within this depot, there is only one dev group, one
patcher group, and one admin group. As long as no special, more granular permissions on a
per-project level are needed, this is sufficient. Otherwise, in rare cases, interaction by the
central operating team is still required.
The Future: Full Local Perforce Project Control
For the future, SAP plans to extend this offering to any kind of projects in any depot and on
any Perforce server such that any project manager at SAP could get rid of lengthy workflows
for project creation.
But this will not be possible without solving a structural problem: the right choice of the hosting
depot and Perforce instance for a completely new project still needs some central governance.
Often the creation of a completely new depot is required; in the future, this will be a task of
central administration. But luckily, that only happens when completely new products are
invented. The much more frequent use case for a project manager is: “I need a new project in
the same depot where all my other projects are already located.” Specifying an already
existing project in a dialog or choosing it from a drop-down box is then an easy task for the
project manager and a feasible approach of a generic self-service for project creation.
10. 1
0
Perforce Administrative Self-Services at SAP
Another challenge comes with the creation of protections on the Perforce server.
Unfortunately, there is no common pattern for code lines and groups that have read or write
access to them that fits for all development teams. Much worse, development teams need the
ability to create new code lines (e.g., for prototyping that does not follow any name pattern). To
avoid involving central manual interaction again, the protections on the Perforce servers have
to be adapted as well: the self-service must be able to add lines into the protection table to
grant permissions on a code line defined by the project administrator.