Understanding the CloudStack Release Process
•Download as PPTX, PDF•
0 likes•569 views
The document discusses the CloudStack release process. It describes the current process which involves feature development, feature freeze, code freeze, and multiple release candidates that cause frustration. The process aims for a 4 month release cycle but has never maintained the schedule. The document proposes moving to reliance on automated testing, more rigid acceptance standards, gated commits based on passing tests, and releasing more frequently with smaller changes to improve quality and reduce delays.
Report
Share
Report
Share
Recommended
7 Apache Process Cloudstack Developer Day
This document discusses Apache CloudStack, an open source cloud computing platform that is currently in incubation at the Apache Software Foundation (ASF). It provides information on how the ASF works, CloudStack's status and participation, the development process, and how to contribute to the project. Key points include that CloudStack 4.0 has been released, the code has moved to Apache repositories, and contributors are working on improvements for the 4.1 release including packaging, dev tools, storage architecture, and testing. The document encourages participation through discussions, documentation, code reviews, and issue tracking on CloudStack's Jira and Review Board systems.
Agile North East Agile + DevOps by Craig Pearson of CAP Project Services
Slides from Agile North East community session - Agile + DevOps = Continuous Delivery on Steroids!!! Given by Craig Pearson of CAP Project Services
Micro Services - Small is Beautiful
The document discusses microservices and their advantages over monolithic architectures. Microservices break applications into small, independent components that can be developed, deployed and scaled independently. This allows for faster development and easier continuous delivery. The document recommends using Spring Boot to implement microservices and Docker to deploy and manage the microservices as independent components. It provides an example of implementing an ELK stack as Dockerized microservices.
Jenkins Pipeline on your Local Box to Reduce Cycle Time
A case study on how to reduce continuous delivery cycle time by using your local resources as the starting point for the continuous delivery Jenkins Pipeline. Your local box has spare CPU, memory and a Git repo to be used with a local Jenkins Pipeline. You get fast feedback and create lots of precious artifacts.
Validating latest changes with XCI
Open Platform for Network Functions Virtualization (OPNFV) is collaborative open source platform which facilitates the development and evolution of various open source ecosystems through system level integration, deployment and testing. Cross Community Continuous Integration (XCI) is an OPNFV project that regularly integrates the latest from each supported branch of select upstream projects. In this session, I’m going to give an overview of the XCI project, how this project meet DevOps principles, explain its general workflow and share some challenges of consuming rapidly evolving open source projects.
How to keep Jenkins logs forever without performance issues
Jenkins is a golden source of information: it contains logs, artifacts and feedback and x-refs from multiple sources. To keep our master healthy and responsive, often we need to remove precious data. The members of the Gerrit Code Review project wanted to keep everything and this is how we did it.
Micro Service – The New Architecture Paradigm
The document discusses microservices as a new software architecture paradigm. It defines microservices as small, independent processes that work together to form an application. The key benefits of microservices are that they allow for easier, faster deployment of features since each service is its own deployment unit and teams can deploy independently without integration. However, the document also notes challenges of microservices such as increased communication overhead, difficulty of code reuse across services, and managing dependencies between many different services. It concludes that microservices are best for projects where time to market is important and continuous delivery is a priority.
Heroku
Heroku is a platform as a service that originally started as a Ruby PaaS but now supports Node.js, Clojure, Grails, Scala, and Python. It uses the Git version control system for deployment and a dyno process model for scaling applications. While flexible in allowing custom buildpacks and configuration via environment variables, there are also restrictions like maximum source code size and memory limits for dyno processes.
Recommended
7 Apache Process Cloudstack Developer Day
This document discusses Apache CloudStack, an open source cloud computing platform that is currently in incubation at the Apache Software Foundation (ASF). It provides information on how the ASF works, CloudStack's status and participation, the development process, and how to contribute to the project. Key points include that CloudStack 4.0 has been released, the code has moved to Apache repositories, and contributors are working on improvements for the 4.1 release including packaging, dev tools, storage architecture, and testing. The document encourages participation through discussions, documentation, code reviews, and issue tracking on CloudStack's Jira and Review Board systems.
Agile North East Agile + DevOps by Craig Pearson of CAP Project Services
Slides from Agile North East community session - Agile + DevOps = Continuous Delivery on Steroids!!! Given by Craig Pearson of CAP Project Services
Micro Services - Small is Beautiful
The document discusses microservices and their advantages over monolithic architectures. Microservices break applications into small, independent components that can be developed, deployed and scaled independently. This allows for faster development and easier continuous delivery. The document recommends using Spring Boot to implement microservices and Docker to deploy and manage the microservices as independent components. It provides an example of implementing an ELK stack as Dockerized microservices.
Jenkins Pipeline on your Local Box to Reduce Cycle Time
A case study on how to reduce continuous delivery cycle time by using your local resources as the starting point for the continuous delivery Jenkins Pipeline. Your local box has spare CPU, memory and a Git repo to be used with a local Jenkins Pipeline. You get fast feedback and create lots of precious artifacts.
Validating latest changes with XCI
Open Platform for Network Functions Virtualization (OPNFV) is collaborative open source platform which facilitates the development and evolution of various open source ecosystems through system level integration, deployment and testing. Cross Community Continuous Integration (XCI) is an OPNFV project that regularly integrates the latest from each supported branch of select upstream projects. In this session, I’m going to give an overview of the XCI project, how this project meet DevOps principles, explain its general workflow and share some challenges of consuming rapidly evolving open source projects.
How to keep Jenkins logs forever without performance issues
Jenkins is a golden source of information: it contains logs, artifacts and feedback and x-refs from multiple sources. To keep our master healthy and responsive, often we need to remove precious data. The members of the Gerrit Code Review project wanted to keep everything and this is how we did it.
Micro Service – The New Architecture Paradigm
The document discusses microservices as a new software architecture paradigm. It defines microservices as small, independent processes that work together to form an application. The key benefits of microservices are that they allow for easier, faster deployment of features since each service is its own deployment unit and teams can deploy independently without integration. However, the document also notes challenges of microservices such as increased communication overhead, difficulty of code reuse across services, and managing dependencies between many different services. It concludes that microservices are best for projects where time to market is important and continuous delivery is a priority.
Heroku
Heroku is a platform as a service that originally started as a Ruby PaaS but now supports Node.js, Clojure, Grails, Scala, and Python. It uses the Git version control system for deployment and a dyno process model for scaling applications. While flexible in allowing custom buildpacks and configuration via environment variables, there are also restrictions like maximum source code size and memory limits for dyno processes.
Continuous Delivery and Micro Services - A Symbiosis
Continuous Delivery profits from Micro Services - and the other way round. This presentation shows how the two technologies work together - and how Micro Services can be used to simplify the transition to Continuous Delivery.
Micro Services - Smaller is Better?
This presentation shows some advice how to be successful with micro services: Which size is right? How shall a project start? What about refactoring?
Micro Services - Neither Micro Nor Service
Micro Services are a new approach to software architecture. This presentation discusses how small they should be - and wether they are really service - in the SOA sense.
20161103 Serverless Italy Meetup
This document summarizes a meetup about serverless technologies. It introduces the organizer and details that the meetup group was started as an experiment and has grown to 140 members who meet monthly. The key aspects of serverless technologies highlighted are that they are fast evolving and poorly documented. The most important things about the meetup are to join online discussions, present topics, provide contributions and ideas, and help spread awareness of serverless technologies.
Setting Up CircleCI Workflows for Your Salesforce Apps
This document discusses setting up CircleCI workflows for Salesforce apps. It covers prerequisites for CircleCI and Salesforce DX, why continuous integration (CI) is useful, basics of CI concepts and workflows, designing a sample CI workflow using CircleCI and SFDX that includes testing, code quality checks, and deployment. It demonstrates configuring and running the workflow in CircleCI and adding a quality gate using static code analysis with Apex PMD. Next steps discussed include breaking projects into smaller packages and parallelizing tests.
Jenkins world 2017 - Data-Driven CI Pipeline with Gerrit Code Review
There is hidden value in the data produced by your Continous Delivery Pipeline that could help
you achieve more efficient processing. The main objective of this workshop is to show you how to
extract that value and benefit from it.
We will introduce you to how to configure and improve your Continuous Delivery Pipeline using
data. After an overview of a Continuous Delivery Pipeline setup using Gerrit Code Review,
Jenkins, and Docker, we will go through the steps on how to extract and analyze data across all
the pipeline stages of the delivery chain.
Flink Community Update April 2015
Monthly Apache Flink Update, featuring the latest highlights from the community.
Presented at the Apache Flink Meetup in Berlin
Dev ops in the cloud use case and best practices meetup
The document discusses lessons learned from implementing agile team development in the cloud. It describes how Oracle uses agile methodology with two-week sprints and DevOps practices like continuous integration and delivery. Developers commit code to Git repositories which trigger automated builds and tests. They submit code for review through merge requests. Operations manages scheduled builds, deployments to staging, and production releases. The cloud-based environment simplifies collaboration and provides full traceability between issues, code changes, and deployments.
Software Architecture for DevOps and Continuous Delivery
Talks from Continuous Lifecycle 2013 in Germany about the influence of DevOps and Continuous Delivery on Software Architecture,
Louisville Software Engineering Meet Up: Continuous Integration Using Jenkins
This talk was given at the January 2016 Meetup of the Louisville Software Engineers. In it we discuss how to implement continuous integration in a development environment utilizing Jenkins CI.
Git and Github
Git is a version control system that allows users to track changes to files over time. It works by taking snapshots of files that are committed, with each commit having a unique hash ID. GitHub is a hosting service for git repositories that provides additional collaboration features on top of git. It allows users to host projects online and collaborate with others through features like pull requests.
Spring Boot
This document discusses Spring Boot, a framework for building Java applications. It makes building Java web applications easier by providing sensible defaults and automatic configuration. Spring Boot allows building applications that are easy to test, debug and deploy. It supports adding additional libraries and frameworks like Spring Data JPA with minimal configuration. The document demonstrates how to create a basic application with Spring Boot and Spring Data JPA with auto-configured infrastructure and shows how Spring Boot helps with development, operations and deployment of Java applications.
Alm with tfs 2013
The document provides an overview of how to effectively use ALM with TFS 2013. It discusses how to set up iterations and areas, move work items between iterations, add work item types to the backlog, and create useful queries. It also offers tips on creating release notes, branching code, and things to automate in builds. Key points covered include using tags instead of iterations to track work, branching code to isolate releases or unfinished work, and creating a new workspace per branch.
Build software like a bag of marbles, not a castle of LEGO®
If you have ever played with LEGO®, you will know that adding, removing or changing features of a completed castle isn’t as easy as it seems. You will have to deconstruct large parts to get to where you want to be, to build it all up again afterwards. Unfortunately, our software is often built the same way. Wouldn’t it be better if our software behaved like a bag of marbles? So you can just add, remove or replace them at will?
Most of us have taken different approaches to building software: a big monolith, a collection of services, a bus architecture, etc. But whatever your large scale architecture is, at the granular level (a single service or host), you will probably still end up with tightly couple code. Adding functionality means making changes to every layer, service or component involved. It gets even harder if you want to enable or disable features for certain deployments: you’ll need to wrap code in feature flags, write custom DB migration scripts, etc. There has to be a better way!
So what if you think of functionality as loose feature assemblies? We can construct our code in such a way that adding a feature is as simple as adding the assembly to your deployment, and removing it is done by just deleting the file. We would open the door for so many scenarios!
In this talk, I will explain how to tackle the following parts of your application to achieve this goal: WebAPI, Entity Framework, Onion Architecture, IoC and database migrations. And most of all, when you would want to do this. Because… ‘it depends’.
Rails tools
Reuven Lerner's presentation from Open Ruby Day in Herzliya, Israel on June 27th, 2010. I covered a few tools that are not part of Rails, but which help you with deployment,
Git branching strategies
The document discusses various Git branching strategies, including:
- Common concepts like branches, merges, and pull requests
- Popular workflows like GitHub Flow and branching per platform/release
- A case study of Telenet's workflow of using long-running release branches merged from master for testing before production deployment
- Best practices like using pull requests for code reviews, keeping long-running branches stable, and ensuring features are fully tested before being merged.
ELK Stack
Short presentation about the ELK stack (Elasticsearch, Logstash, Kibana) running on top of Docker / Vagrant.
CloudFest 2018 Hackathon Project Results Presentation - CFHack18
Our third annual hackathon at CloudFest (formerly WHDglobal) was a great success. Developers from all over Europe came to participate - including noted experts from the WordPress and Joomla communities. Six technology projects were completed with two building on last year's success. Topics included IoT, secure FPTD, Domain Connect, WordPress updates, and more. And a special thanks to our sponsors who made it all possible. Cheers!
Developer day - AWS: Fast Environments = Fast Deployments
The document discusses how AWS enables fast and flexible deployments through automation. It outlines problems with manual and unique server deployments like breakages and lack of change management. The solution presented is to automate the entire process through continuous integration and deployment tools like Jenkins, GitHub, Grunt, and AWS CloudFormation. This treats servers as identical and deployable resources, ensures all code is tested and production-ready, and allows for boring but successful automated deployments on demand.
Collaborating on GitHub for Open Source Documentation
At the Austin Write the Docs Meetup January 2016, Anne Gentle talks about her experiences collaborating on open source documentation.
Building a Dev/Test Cloud with Apache CloudStack
Presentation I gave at LinuxCon/CloudOpen Japan 2013 on building a dev/test cloud with Apache CloudStack
Successfully deploy build manage your cloud with cloud stack2
This document discusses CloudStack, an open source cloud management platform. It provides an overview of CloudStack's capabilities including deploying and managing virtual servers on demand, networking services, high availability, multi-tenancy, and support for multiple hypervisors. The document also discusses CloudStack's architecture, resources, availability zones, APIs, and acquisition by Citrix to build on their footprint in cloud computing. It concludes with inviting questions and providing contact information.
More Related Content
What's hot
Continuous Delivery and Micro Services - A Symbiosis
Continuous Delivery profits from Micro Services - and the other way round. This presentation shows how the two technologies work together - and how Micro Services can be used to simplify the transition to Continuous Delivery.
Micro Services - Smaller is Better?
This presentation shows some advice how to be successful with micro services: Which size is right? How shall a project start? What about refactoring?
Micro Services - Neither Micro Nor Service
Micro Services are a new approach to software architecture. This presentation discusses how small they should be - and wether they are really service - in the SOA sense.
20161103 Serverless Italy Meetup
This document summarizes a meetup about serverless technologies. It introduces the organizer and details that the meetup group was started as an experiment and has grown to 140 members who meet monthly. The key aspects of serverless technologies highlighted are that they are fast evolving and poorly documented. The most important things about the meetup are to join online discussions, present topics, provide contributions and ideas, and help spread awareness of serverless technologies.
Setting Up CircleCI Workflows for Your Salesforce Apps
This document discusses setting up CircleCI workflows for Salesforce apps. It covers prerequisites for CircleCI and Salesforce DX, why continuous integration (CI) is useful, basics of CI concepts and workflows, designing a sample CI workflow using CircleCI and SFDX that includes testing, code quality checks, and deployment. It demonstrates configuring and running the workflow in CircleCI and adding a quality gate using static code analysis with Apex PMD. Next steps discussed include breaking projects into smaller packages and parallelizing tests.
Jenkins world 2017 - Data-Driven CI Pipeline with Gerrit Code Review
There is hidden value in the data produced by your Continous Delivery Pipeline that could help
you achieve more efficient processing. The main objective of this workshop is to show you how to
extract that value and benefit from it.
We will introduce you to how to configure and improve your Continuous Delivery Pipeline using
data. After an overview of a Continuous Delivery Pipeline setup using Gerrit Code Review,
Jenkins, and Docker, we will go through the steps on how to extract and analyze data across all
the pipeline stages of the delivery chain.
Flink Community Update April 2015
Monthly Apache Flink Update, featuring the latest highlights from the community.
Presented at the Apache Flink Meetup in Berlin
Dev ops in the cloud use case and best practices meetup
The document discusses lessons learned from implementing agile team development in the cloud. It describes how Oracle uses agile methodology with two-week sprints and DevOps practices like continuous integration and delivery. Developers commit code to Git repositories which trigger automated builds and tests. They submit code for review through merge requests. Operations manages scheduled builds, deployments to staging, and production releases. The cloud-based environment simplifies collaboration and provides full traceability between issues, code changes, and deployments.
Software Architecture for DevOps and Continuous Delivery
Talks from Continuous Lifecycle 2013 in Germany about the influence of DevOps and Continuous Delivery on Software Architecture,
Louisville Software Engineering Meet Up: Continuous Integration Using Jenkins
This talk was given at the January 2016 Meetup of the Louisville Software Engineers. In it we discuss how to implement continuous integration in a development environment utilizing Jenkins CI.
Git and Github
Git is a version control system that allows users to track changes to files over time. It works by taking snapshots of files that are committed, with each commit having a unique hash ID. GitHub is a hosting service for git repositories that provides additional collaboration features on top of git. It allows users to host projects online and collaborate with others through features like pull requests.
Spring Boot
This document discusses Spring Boot, a framework for building Java applications. It makes building Java web applications easier by providing sensible defaults and automatic configuration. Spring Boot allows building applications that are easy to test, debug and deploy. It supports adding additional libraries and frameworks like Spring Data JPA with minimal configuration. The document demonstrates how to create a basic application with Spring Boot and Spring Data JPA with auto-configured infrastructure and shows how Spring Boot helps with development, operations and deployment of Java applications.
Alm with tfs 2013
The document provides an overview of how to effectively use ALM with TFS 2013. It discusses how to set up iterations and areas, move work items between iterations, add work item types to the backlog, and create useful queries. It also offers tips on creating release notes, branching code, and things to automate in builds. Key points covered include using tags instead of iterations to track work, branching code to isolate releases or unfinished work, and creating a new workspace per branch.
Build software like a bag of marbles, not a castle of LEGO®
If you have ever played with LEGO®, you will know that adding, removing or changing features of a completed castle isn’t as easy as it seems. You will have to deconstruct large parts to get to where you want to be, to build it all up again afterwards. Unfortunately, our software is often built the same way. Wouldn’t it be better if our software behaved like a bag of marbles? So you can just add, remove or replace them at will?
Most of us have taken different approaches to building software: a big monolith, a collection of services, a bus architecture, etc. But whatever your large scale architecture is, at the granular level (a single service or host), you will probably still end up with tightly couple code. Adding functionality means making changes to every layer, service or component involved. It gets even harder if you want to enable or disable features for certain deployments: you’ll need to wrap code in feature flags, write custom DB migration scripts, etc. There has to be a better way!
So what if you think of functionality as loose feature assemblies? We can construct our code in such a way that adding a feature is as simple as adding the assembly to your deployment, and removing it is done by just deleting the file. We would open the door for so many scenarios!
In this talk, I will explain how to tackle the following parts of your application to achieve this goal: WebAPI, Entity Framework, Onion Architecture, IoC and database migrations. And most of all, when you would want to do this. Because… ‘it depends’.
Rails tools
Reuven Lerner's presentation from Open Ruby Day in Herzliya, Israel on June 27th, 2010. I covered a few tools that are not part of Rails, but which help you with deployment,
Git branching strategies
The document discusses various Git branching strategies, including:
- Common concepts like branches, merges, and pull requests
- Popular workflows like GitHub Flow and branching per platform/release
- A case study of Telenet's workflow of using long-running release branches merged from master for testing before production deployment
- Best practices like using pull requests for code reviews, keeping long-running branches stable, and ensuring features are fully tested before being merged.
ELK Stack
Short presentation about the ELK stack (Elasticsearch, Logstash, Kibana) running on top of Docker / Vagrant.
CloudFest 2018 Hackathon Project Results Presentation - CFHack18
Our third annual hackathon at CloudFest (formerly WHDglobal) was a great success. Developers from all over Europe came to participate - including noted experts from the WordPress and Joomla communities. Six technology projects were completed with two building on last year's success. Topics included IoT, secure FPTD, Domain Connect, WordPress updates, and more. And a special thanks to our sponsors who made it all possible. Cheers!
Developer day - AWS: Fast Environments = Fast Deployments
The document discusses how AWS enables fast and flexible deployments through automation. It outlines problems with manual and unique server deployments like breakages and lack of change management. The solution presented is to automate the entire process through continuous integration and deployment tools like Jenkins, GitHub, Grunt, and AWS CloudFormation. This treats servers as identical and deployable resources, ensures all code is tested and production-ready, and allows for boring but successful automated deployments on demand.
Collaborating on GitHub for Open Source Documentation
At the Austin Write the Docs Meetup January 2016, Anne Gentle talks about her experiences collaborating on open source documentation.
What's hot (20)
Continuous Delivery and Micro Services - A Symbiosis
Continuous Delivery and Micro Services - A Symbiosis
Setting Up CircleCI Workflows for Your Salesforce Apps
Setting Up CircleCI Workflows for Your Salesforce Apps
Jenkins world 2017 - Data-Driven CI Pipeline with Gerrit Code Review
Jenkins world 2017 - Data-Driven CI Pipeline with Gerrit Code Review
Dev ops in the cloud use case and best practices meetup
Dev ops in the cloud use case and best practices meetup
Software Architecture for DevOps and Continuous Delivery
Software Architecture for DevOps and Continuous Delivery
Louisville Software Engineering Meet Up: Continuous Integration Using Jenkins
Louisville Software Engineering Meet Up: Continuous Integration Using Jenkins
Build software like a bag of marbles, not a castle of LEGO®
Build software like a bag of marbles, not a castle of LEGO®
CloudFest 2018 Hackathon Project Results Presentation - CFHack18
CloudFest 2018 Hackathon Project Results Presentation - CFHack18
Developer day - AWS: Fast Environments = Fast Deployments
Developer day - AWS: Fast Environments = Fast Deployments
Collaborating on GitHub for Open Source Documentation
Collaborating on GitHub for Open Source Documentation
Viewers also liked
Building a Dev/Test Cloud with Apache CloudStack
Presentation I gave at LinuxCon/CloudOpen Japan 2013 on building a dev/test cloud with Apache CloudStack
Successfully deploy build manage your cloud with cloud stack2
This document discusses CloudStack, an open source cloud management platform. It provides an overview of CloudStack's capabilities including deploying and managing virtual servers on demand, networking services, high availability, multi-tenancy, and support for multiple hypervisors. The document also discusses CloudStack's architecture, resources, availability zones, APIs, and acquisition by Citrix to build on their footprint in cloud computing. It concludes with inviting questions and providing contact information.
Build a Cloud Day - CloudStack
CloudStack is an open source cloud computing platform that provides infrastructure as a service. It was originally formed in 2008 as VMOps and was later acquired by Citrix in 2011. CloudStack allows for on-demand provisioning of computing resources in a multi-tenant environment with high availability and supports various hypervisors including KVM, XenServer, and VMware. It provides APIs to manage and automate the provisioning of virtual servers, load balancing, firewalls, storage, and networking.
Puppetpreso
This document discusses using Puppet to manage infrastructure as code with Apache CloudStack. It describes how Puppet types and providers were developed to allow defining CloudStack instances and entire application stacks in Puppet manifests. This enables automated deployment and configuration of infrastructure along with software configuration. Examples are given of using Puppet to define CloudStack instances, groups of instances that make up an application stack, and setting defaults for attributes. Resources mentioned include the CloudStack and Puppet GitHub pages.
10 Minute Overview of Apache CloudStack
CloudStack is an open source cloud computing platform that allows users to build and manage virtualized cloud environments. It provides tools for provisioning virtual machines, managing networks and storage, and monitoring resource usage. CloudStack's architecture includes components like hypervisors, primary storage, secondary storage, clusters, zones, and a management server. It offers both an administrative web interface and APIs for management and integration.
Bacd zenoss
The document discusses several monitoring tools like Nagios, collectd, and Ganglia and notes their lack of automation plugins and APIs. It then introduces Zenoss as a holistic monitoring solution with powerful plugins and APIs that can monitor various cloud platforms, hypervisors, and provide dashboards. Finally, it lists some resources for getting started with Zenoss including documentation, community forums, and code repositories.
On-demand Continuous Integration with Jenkins, jclouds, and CloudStack
This document discusses using Jenkins, jclouds, and CloudStack together to provide scalable continuous integration testing. It describes how the author transitioned from using dedicated Jenkins masters and VMs to dynamically provisioning build slaves from CloudStack on demand using jclouds. The key steps were building standard images with Packer, configuring the jclouds plugin in Jenkins to integrate with CloudStack as the cloud provider, and configuring jobs to spin up slaves when needed and terminate them after 30 minutes of idle time. This approach provides scalable testing resources that match the varying demand of their many projects.
ApacheConEU Keynote: What is the value of the Apache Software Foundation
The document discusses the value of the Apache Software Foundation and its mission to provide software for the public good through various projects. The Apache Software Foundation supports numerous open source projects that create widely-used software such as web servers, data processing tools, and databases.
Viewers also liked (8)
Successfully deploy build manage your cloud with cloud stack2
Successfully deploy build manage your cloud with cloud stack2
On-demand Continuous Integration with Jenkins, jclouds, and CloudStack
On-demand Continuous Integration with Jenkins, jclouds, and CloudStack
ApacheConEU Keynote: What is the value of the Apache Software Foundation
ApacheConEU Keynote: What is the value of the Apache Software Foundation
Similar to Understanding the CloudStack Release Process
Hacking on WildFly 9
Join us for this interactive event and get your hands dirty with some WildFly 9 hacking!
Our host Kabir Khan will explain how you can contribute to the WildFly project at many different levels, from properly reporting bugs in the forums and issue tracker, to actually being able to submit a pull request.
During this interactive event you will have a chance to play with WildFly 9 and try some of the following:
• Find a JIRA you want to work on.
• See how to check-out the code and setup your IDE.
• Build WildFly
• Code walkthrough - code organisation, jboss-modules etc.
• Debug something from a stack trace in a JIRA issue to nail down the problem.
• Try the testsuite
• And more!
TYPO3 Camp Stuttgart 2015 - Continuous Delivery with Open Source Tools
In diesem Talk beschreibe ich die Continuous Integartion Pipeline von punkt.de und deren Entstehen. Es wird motiviert, warum es sich lohnt, eine solche Pipeline zu implementieren und welche Tools wir dafür verwendet haben. Neben der Beschreibung von Git, Jenkins, Chef, Vagrant, Behat und Surf geht es auch um Integration der einzelnen Tools in eine Deployment Kette.
2016 09-dev opsjourney-devopsdaysoslo
A DevOps Journey - An experience report after 6 years of implementing DevOps and Continuous Delivery in Frende Forsikring, a small insurance company in Norway.
How to avoid microservice pitfalls
There are many resources out there that walk you through the process of setting up distributed systems, queuing and asynchronous processes — with and without NServiceBus.
Despite all the online education, teams continue to make the same common mistakes when designing and implementing microservices architecture. While the mistakes can have devastating consequences, they are easy to avoid when approached intentionally.
Jeffrey Palermo and Justin Self share their experiences in overcoming common microservices pitfalls and show how NServiceBus naturally encourages better architecture, such as easy adherence to SOLID principles.
Learn:
* What a microservice really is (and is not)
* What mistakes teams commonly make
* How to avoid the pitfalls and design more robust and scalable architecture
* How to equip your team for a microservices architecture
NDC London 2020 - Challenges of Managing CoreFx Repo -- Karel Zikmund
NDC London 2020 conference in London, UK - 2020/1/29
Talk: Challenges of Managing CoreFx Repo by Karel Zikmund
https://sessionize.com/s/karel-zikmund/archived-challenges-of-managing-corefx-repo/24173
https://www.youtube.com/watch?v=zLB2_h-3ZS4
Deployment automation framework with selenium
In my slides, I presented my experience in setting up a deployment automation framework with selenium.
The deployment automation framework dramatically dramatically reduced my deployment workload.
I hope my deployment automation setup experience help you in your own/customized automation framework setup with selenium and other open source tools.
Experiences Bringing CD to a DoD Project
Not every continuous delivery initiative starts with someone saying "drop everything. Let's do DevOps." Sometimes you have grow your practice incrementally. And sometimes, you don’t set out to grow a practice at all-- you are just fixing problems with your process, trying to make things better.
I'll walk through a case study of how our team worked on an exemplar project for the Department of Defense to show that agile could work in a decidedly waterfall culture. I’ll also discuss techniques and tools we used to bring a DevOps mindset and continuous delivery practices into an environment that wasn't already Agile.
I'll talk about how we were able to start in development, where we had the most control, with a "let's starting being Agile" initiative and working on "why is continuous integration important?" From there, we tackled one problem after another, each time making the release a little easier and a little less risky. We incrementally brought our practices through other environments until the project was confidently delivering working, QA-tested, security-tested releases that were ready for production every two weeks. I’ll discuss the journey we took and the tools we used to get to build quality into our product, our releases, and our release process.
This session is aimed at people that are trying to adopt agile and continuous delivery, but might be worried that it can’t work in their particular environment due to the enterprise, the culture, or the regulations that surround them.
Webinar - Continuous Integration with GitLab
The document is a presentation about continuous integration with GitLab. It discusses what continuous integration is, why it is important, and how to set up continuous integration builds using GitLab. Specifically, it defines continuous integration as integrating code regularly to prevent problems and identify issues early. It recommends gradually adopting continuous integration practices like writing test cases whenever bugs are fixed. The presentation also provides instructions on setting up a GitLab runner to enable continuous integration builds and adding a .gitlab-ci.yml file to configure builds.
Why It’s Important to Contribute to Open-Source Projects | Keysight Connect #10
*️⃣*️⃣*️⃣ About the presentation
Open-Source software is widely used by technology companies due to the range of advantages it brings to the table, like the potential to accelerate time-to-market. There are often times when we find ourselves having to adapt Open-Source code to meet our business needs. When numerous such code changes accumulate, we could have a difficult time migrating to a newer version of the Open-Source component. Upstreaming (the process of contributing in-house developed code to an Open-Source project, with the goal of having them accepted and distributed in future project releases) could be a useful tool in managing this complexity. Join us in this presentation, where we will discuss Open-Source and our current experience with contributing some of our in-house source code modifications back to an Open-Source project.
*️⃣*️⃣*️⃣ About the speaker
Tudor Cornea has been employed by Keysight Technologies Romania (formerly known as Ixia Romania) for about ten years. In all of this time, he has worked with a wide range of technologies from the Virtualization and Computer Networking areas. He has learned to appreciate the industry’s dynamicity and the related challenges along the way. His main areas of interest are Linux, Computer Networking, as well as Computer Security.
*️⃣*️⃣*️⃣ About Keysight Connect
Keysight Connect is a series of tech meetups where Keysight’s software engineers showcase their findings and side projects related to computer networks, testing tools, and cybersecurity. 🎫
Aiming for automatic updates - Drupal Dev Days Lisbon 2018
Drupal recents security updates resulted in many hours of work for different professionals involved in maintenance of Drupal websites from developers to operations teams.
New Drupal 8 release cycle is also requiring organisations to spend more time guaranteeing that their websites are following last minor core release so their sites are updated and ready to receive new features and security updates.
Nevertheless, even with the increasing required effort, we still don’t have an easy way to support automatic updates in Drupal core but options start to appear.
In this session I will talk about different possible alternatives that can minimize the effort to automatically update Drupal while still maintaining best practices in all the required phases.
Continuous Delivery Agiles 2014 Medellin
Conference about the Continuous Delivery Project on OLX. Tools we used, tools we created and opensourced like Octopush and lessons learned.
Experience in teaching devops
This document discusses Len Bass's experience teaching a DevOps course. It begins with an overview of DevOps and what it aims to accomplish. It then describes the structure and content of the course, which combines lectures, readings, discussions, and hands-on assignments using open source DevOps tools. The document notes that students often lack fundamental knowledge in areas like networking, security, and operations. It proposes establishing an "infrastructure minor" to address gaps in students' undergraduate education.
Atagg2015 Continuous delivery by building environment using docker
The document discusses how PayUMoney uses Docker containers to enable continuous delivery. It outlines challenges with limited testing environments and long setup times. PayUMoney developed a standardized Docker setup to allow anyone on the team to quickly spin up production-like environments on their own laptops. This enabled automated testing of all code branches, fast merging to mainline, and continuous deployment to production with zero downtime releases. Speakers Nitin Mukhija and Tarun Lalwani from PayUMoney presented on how Docker simplified their environment management and improved their delivery process.
Webinar: OpenStack Accelerates Software Development
The document discusses how OpenStack can accelerate software development. It outlines 7 ways that OpenStack provides benefits: 1) self-service provisioning, 2) shared image libraries, 3) CLIs, libraries and configuration management tools for automation, 4) REST APIs for automation, 5) using OpenStack to turbocharge continuous integration and continuous delivery (CI/CD) pipelines, 6) orchestrating application stacks using Heat, and 7) using OpenStack as a platform for technologies like Cloud Foundry, Mesos and Docker. The presentation provides examples and references for each way that OpenStack supports faster development.
Ci & proServer
This document discusses how continuous integration (CI) and continuous delivery (CD) can help software teams automatically merge code changes, deploy updates, and reduce errors. It recommends a simple stack using Gitlab for version control and CI, TYPO3 Surf for automated deployments and testing, and Ansible for infrastructure automation. The document argues that the proServer is well-suited for CI/CD with these tools and that the company punkt.de can help organizations set up and improve their CI/CD processes.
Continuous Delivery for the Rest of Us
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1vfO62b.
Lisa Van Gelder provides simple tips and tricks for improving delivery without investing lots of time up front creating complex deployment frameworks. Filmed at qconsf.com.
Lisa Van Gelder is a Senior Consultant at Cyrus Innovation where she works with companies to build and deliver software solutions, improve their software development process, and speed up delivery.
DevOps, Managing Development + Operations & Release in Large Scale
Due to the requirements faced by software developers today (which can be summed up as releasing working software early and often), various practices have emerged: continuous development, continuous testing/integration, and continuous deployment are all buzzwords in the industry. In such a fast-paced environment, collaboration is key to ensure software quality. Consequently, the functions of Development and Operations have started converging, giving birth to the notion of DevOps.
DevOps means the integration of the operations approach in entire development lifecycle, in order to incorporate post-deployment aspects and to maintain customer (quality) focus throughout the process.
This webinar will let you learn about managing Development, Operations and Release at scale via an integrated approach. We will also show you how some of our clients (large global enterprises) are using codeBeamer to release iterations as many as 9 times a day.
Picnic Software - Developing a flexible and scalable application
The team at Picnic Software giving a detailed walkthrough of their application architecture and development processes for a large Angular and .NET Event Sourcing application.
Make It Cooler: Using Decentralized Version Control
A commonly used version control system in the ColdFusion community is Subversion -- a centralized system that relies on being connected to a central server. The next generation version control systems are “decentralized”, in that version control tasks do not rely on a central server.
Decentralized version control systems are more efficient and offer a more practical way of software development.
In this session, Indy takes you through the considerations in moving from Subversion to Git, a decentralized version control system. You also get to understand the pros and cons of each and hear of the practical experience of migrating projects to decentralized version control.
Version control is often used in conjunction with a testing framework and continuous integration. To complete the picture, Indy walks you through how to integrate Git with a testing framework, MXUnit, and a continuous integration server, Hudson.
Selenium at Mozilla: An Essential Element to our Success
This document summarizes the history and current state of Selenium testing at Mozilla. It discusses how Selenium testing started in 2007 and has grown significantly since 2010. Currently there are 13 projects using WebDriver across various environments and platforms. Custom plugins and configurations have been created to help scale and manage the infrastructure. Lessons from previous releases helped improve practices around page object models and non-destructive testing. Continuous deployment also prompted assessing the role of Selenium in their testing strategy. The team collaborates openly with the community and welcomes contributions.
Similar to Understanding the CloudStack Release Process (20)
TYPO3 Camp Stuttgart 2015 - Continuous Delivery with Open Source Tools
TYPO3 Camp Stuttgart 2015 - Continuous Delivery with Open Source Tools
NDC London 2020 - Challenges of Managing CoreFx Repo -- Karel Zikmund
NDC London 2020 - Challenges of Managing CoreFx Repo -- Karel Zikmund
Why It’s Important to Contribute to Open-Source Projects | Keysight Connect #10
Why It’s Important to Contribute to Open-Source Projects | Keysight Connect #10
Aiming for automatic updates - Drupal Dev Days Lisbon 2018
Aiming for automatic updates - Drupal Dev Days Lisbon 2018
Atagg2015 Continuous delivery by building environment using docker
Atagg2015 Continuous delivery by building environment using docker
Webinar: OpenStack Accelerates Software Development
Webinar: OpenStack Accelerates Software Development
DevOps, Managing Development + Operations & Release in Large Scale
DevOps, Managing Development + Operations & Release in Large Scale
Picnic Software - Developing a flexible and scalable application
Picnic Software - Developing a flexible and scalable application
Make It Cooler: Using Decentralized Version Control
Make It Cooler: Using Decentralized Version Control
Selenium at Mozilla: An Essential Element to our Success
Selenium at Mozilla: An Essential Element to our Success
More from ke4qqq
The Tragedy of Open Source
The document discusses the "Tragedy of the Commons" concept in relation to open source software. It notes that while open source is now the default model for cloud, big data and new technologies, many critical open source projects face underfunding and lack of developer contributions, similar to an overgrazed common field. The document suggests organizations should invest in open source either by paying vendors or contributing code upstream to support core infrastructure projects.
Cloud Innovation and Risks
This document discusses innovations and risks related to cloud computing and containers. It notes that while public cloud infrastructure services continue growing, the private cloud market has narrowed. It also notes that while infrastructure as a service (IaaS) remains niche for some, operating an internal cloud can erode advantages over public cloud. The document also discusses consolidation in the platform as a service (PaaS) market and risks around building developer communities for open source PaaS projects. It acknowledges security issues with containers and how people consume untrusted container images. Finally, it suggests people are increasingly deploying services using schedulers like Mesos and Kubernetes rather than directly managing virtual machines.
Ceph and Apache CloudStack
This document discusses using Ceph block storage (RBD) with Apache CloudStack for distributed storage. Ceph provides block-level storage that scales for performance and capacity like SAN storage, addressing the need for EBS-like storage across availability zones. CloudStack currently uses local disk or requires separate storage resources per hypervisor, but using Ceph's distributed RBD allows datacenter-wide storage and removes constraints. Upcoming support in CloudStack includes format 2 RBD, snapshots, datacenter-wide storage resources, and removal of legacy storage dependencies.
It's not tools, Stupid
DevOps is primarily about culture, not tools. It aims to break down barriers between development and operations teams through continuous improvement. While tools are important, they don't define DevOps or ensure its goals are met. True DevOps requires cultural changes like empowering workers, eliminating fear, and prioritizing quality over metrics. It draws from philosophies like eliminating silos, constant learning, and taking responsibility for organizational change.
Infrastructure as code with Puppet and Apache CloudStack
This document discusses using Puppet to define infrastructure as code with Apache CloudStack. It describes how Puppet can be used to provision and configure virtual machines on CloudStack as well as define entire application stacks. The author provides examples of using Puppet types and providers to define CloudStack instances and groups of instances that can be deployed with a single Puppet manifest. Links are included to learn more about using Puppet to manage CloudStack infrastructure.
DevOps, Cloud, and the Death of Backup Tape Changers
- DevOps aims to break down barriers between development and operations teams through automation, measurement, and culture change. This enables faster delivery of applications and services.
- Traditional IT operations has focused too much on control and constraint rather than enabling teams. As a result, developers often work around or avoid IT.
- If IT does not adapt by becoming more agile and self-service oriented like cloud computing, it risks becoming irrelevant like backup tape changers - a outdated technology that people work to avoid. IT must partner with teams rather than control them to remain relevant in the future.
Building a Dev/Test Cloud with Apache CloudStack
Slides from my talk at the South East Linux Fest about building an IaaS dev/test cloud with Apache CloudStack
CloudStack Intro NYC
Quick 10 minute introduction to Apache CloudStack - presentation originally given at NYC CloudStack Users Group.
Infrastructure as code with Puppet and Apache CloudStack
Puppet can now be used to define not only the configuration of machines, but also the machines themselves and entire collections of machines when using CloudStack. New Puppet types and providers allow defining CloudStack instances, groups of instances, and entire application stacks that can then be deployed on CloudStack. This brings infrastructure as code to a new level by allowing Puppet to define and manage the entire CloudStack infrastructure.
Puppet and CloudStack
This document discusses using Puppet and infrastructure as code to manage Apache CloudStack infrastructure. It introduces the cloudstack_resources Puppet module which allows defining CloudStack instances and entire application stacks in Puppet manifests. This enables treating infrastructure like code where Puppet can deploy and configure entire environments on CloudStack. Examples are given of classifying servers and deploying a Hadoop cluster with a single Puppet resource definition. Links are provided to resources for using Puppet with CloudStack and videos that further explain the concepts.
CloudStack - LinuxFest NorthWest
This presentation provides an overview of Apache CloudStack, an open source cloud computing platform. It discusses CloudStack's history and licensing, its ability to provide infrastructure as a service across multiple hypervisors, and how it enables multi-tenancy, high availability, scalability, and resource allocation. Key CloudStack components and concepts are also summarized, such as networking models, security groups, primary and secondary storage, usage tracking, and its management architecture.
Build a Cloud Day - CloudStack
CloudStack is an open source cloud computing platform that provides infrastructure as a service. It was originally formed in 2008 as VMOps and was later acquired by Citrix in 2011. CloudStack allows for on-demand provisioning of computing resources in a multi-tenant environment with high availability and supports various hypervisors including KVM, XenServer, and VMware. It provides APIs to manage and automate the provisioning of virtual computing resources.
More from ke4qqq (12)
Infrastructure as code with Puppet and Apache CloudStack
Infrastructure as code with Puppet and Apache CloudStack
DevOps, Cloud, and the Death of Backup Tape Changers
DevOps, Cloud, and the Death of Backup Tape Changers
Infrastructure as code with Puppet and Apache CloudStack
Infrastructure as code with Puppet and Apache CloudStack
Recently uploaded
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
Finale of the Year: Apply for Next One!
Presentation for the event called "Finale of the Year: Apply for Next One!" organized by GDSC PJATK
June Patch Tuesday
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Azure API Management to expose backend services securely
How to use Azure API Management to expose backend service securely
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Taking AI to the Next Level in Manufacturing.pdf
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
System Design Case Study: Building a Scalable E-Commerce Platform - Hiike
This case study explores designing a scalable e-commerce platform, covering key requirements, system components, and best practices.
Best 20 SEO Techniques To Improve Website Visibility In SERP
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
dbms calicut university B. sc Cs 4th sem.pdf
Its a seminar ppt on database management system using sql
Recently uploaded (20)
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
Azure API Management to expose backend services securely
Azure API Management to expose backend services securely
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
System Design Case Study: Building a Scalable E-Commerce Platform - Hiike
System Design Case Study: Building a Scalable E-Commerce Platform - Hiike
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Understanding the CloudStack Release Process
- 1. Understanding the CloudStack Release Process David Nalley @ke4qqq ke4qqq@apache.org
- 2. #whoami • Director, The Apache Software Foundation • VP Infra, The Apache Software Foundation • PMC Member, Apache CloudStack • Employed by Citrix – Work in the Open Source Business Office – Originally at Cloud.com
- 3. Releases • Releases provide end users with usable software • Releases are official actions of the Foundation • Aside from a vote, the release process is left up to the project.
- 4. Releases – what we’ve done • We ‘strive’ for a 4 months release cycle. – We’ve never maintained schedule • We have multiple ‘phases’ for the release cycle.
- 5. Phase 1: Feature Development • Features developed on branches and merged when ready in this phase.
- 6. Phase 2: Feature Freeze • No new functionality • Only bugfixes committed
- 7. Phase 3: Code freeze • When all testing is supposed to occur • Stabilize the code base in preparation for release
- 8. Phase 4: Release candidates • This is when most testing seems to occur • We end up with many release candidates – The churn causes much frustration
- 9. The result • We ‘generally’ have acceptable releases, but sometimes they are delayed many months. • We exhaust our community with repeated test cycles.
- 10. Where we want to move (Disclaimer: I am only one person – my views may not be what we end up with. I do not have fiat authority)
- 11. Where we want to move • Reliance on automated testing. • Much more rigid acceptance standards for code – Require automated test coverage for new features – Require that problems be fixed and have tests
- 12. Where we want to move • Gated commits – based on automated testing. (passing tests as a requirement for each commit)
- 13. Faster • We want to release more frequently • Smaller changesets – minimize the effect of change on quality
- 14. Questions?
- 15. Join us • dev@cloudstack.apache.org • @cloudstack on Twitter • #cloudstack on irc.freenode.net