Aurelio  Yost

Aurelio Yost

1639141200

How to Add A Jenkins Controller & Jenkins Agent Node in Azure Part VII

Learn how to add a Jenkins agent controller and Jenkins agent node on azure.
This video is a part of our Jenkins Tutorial series. In this video, Moss(@tech_with_moss), explains how you can set up and add a Jenkins agent controller and an additional azure agent node with a Jenkins controller node example.

By the end of this video, you will learn 🎫 -: 
🔸 What is the purpose of an agent in Jenkins?
🔸 What is Jenkins controller?
🔸 How does Jenkins agent work?
🔸 How to launch agent via ssh in Jenkins?
🔸 How to add Jenkins agent node controller?
🔸 How to add additional agent node in azure?

Vɪᴅᴇᴏ Cʜᴀᴘᴛᴇʀꜱ
➤  00:00 Introduction
➤  00:41 What is the purpose of an agent in Jenkins?
➤  01:10 How Jenkins agent controller can help?
➤  02:01 The environment
➤  02:55 Set up Jenkins controller and Jenkins agent node
➤  06:20 Add additional azure agent node
➤  07:55 Create a directory
➤ 14:58 Create a test azure agent
➤ 17:05 Verify echo command

Kick Start Testing -: https://accounts.lambdatest.com/register?utm_source=YouTube&utm_medium=YouTubeChannel&utm_campaign=Videos&utm_term=-NUQhwmhTCw
Try Jenkins Testing with LambdaTest -: https://www.lambdatest.com/continuous-testing-with-jenkins-pipeline?utm_source=YouTube&utm_medium=YouTubeChannel&utm_campaign=Videos&utm_term=-NUQhwmhTCw

#jenkins  #tutorial  #node  #azure 

What is GEEK

Buddha Community

How to Add A Jenkins Controller & Jenkins Agent Node in Azure Part VII
Aurelio  Yost

Aurelio Yost

1639141200

How to Add A Jenkins Controller & Jenkins Agent Node in Azure Part VII

Learn how to add a Jenkins agent controller and Jenkins agent node on azure.
This video is a part of our Jenkins Tutorial series. In this video, Moss(@tech_with_moss), explains how you can set up and add a Jenkins agent controller and an additional azure agent node with a Jenkins controller node example.

By the end of this video, you will learn 🎫 -: 
🔸 What is the purpose of an agent in Jenkins?
🔸 What is Jenkins controller?
🔸 How does Jenkins agent work?
🔸 How to launch agent via ssh in Jenkins?
🔸 How to add Jenkins agent node controller?
🔸 How to add additional agent node in azure?

Vɪᴅᴇᴏ Cʜᴀᴘᴛᴇʀꜱ
➤  00:00 Introduction
➤  00:41 What is the purpose of an agent in Jenkins?
➤  01:10 How Jenkins agent controller can help?
➤  02:01 The environment
➤  02:55 Set up Jenkins controller and Jenkins agent node
➤  06:20 Add additional azure agent node
➤  07:55 Create a directory
➤ 14:58 Create a test azure agent
➤ 17:05 Verify echo command

Kick Start Testing -: https://accounts.lambdatest.com/register?utm_source=YouTube&utm_medium=YouTubeChannel&utm_campaign=Videos&utm_term=-NUQhwmhTCw
Try Jenkins Testing with LambdaTest -: https://www.lambdatest.com/continuous-testing-with-jenkins-pipeline?utm_source=YouTube&utm_medium=YouTubeChannel&utm_campaign=Videos&utm_term=-NUQhwmhTCw

#jenkins  #tutorial  #node  #azure 

Aurelio  Yost

Aurelio Yost

1636898700

Add Jenkins Controller & Agent Node for Windows: Part VI

In this video, learn how to add Jenkins controller & Jenkins agent node for Windows. 
This is Part VI of the Jenkins LambdaTest Tutorial series wherein Moss (@tech_with_moss), a DevOps engineer, explains about configuring Jenkins controller and Jenkins agent nodes to overcome the limitation of a single Jenkins instance. The growing organization needs to scale Jenkins on multiple platforms like Windows, Mac OS, Ubuntu, and Linux.

Jenkins agents are machines to whom Jenkins controllers can delegate the task of building projects distributed across different platforms that support Java. It allows multi-platform build and testing using the same Jenkins Server.

An agent node might be a windows machine, a Linux machine, or some other platform that supports Java; this allows multi-platform build and testing using the same Jenkins server.  

You will also learn about -:
🔸 How does Jenkins connect to Windows agent?
🔸 Where does Jenkins agent run?
🔸 How does Jenkins agents work?
🔸 How do you deploy Jenkins agent and connect it to Jenkins master?

Vɪᴅᴇᴏ Cʜᴀᴘᴛᴇʀꜱ 
➤ 00:00 Introduction to Jenkins Tutorial for Beginners
➤ 00:40 Problems with single Jenkins Server and Need for Jenkins Controller-Agent setup
➤ 01:10 Jenkins Controller/Agent (Master/Slave) Architecture
➤ 02:03 How to add a Jenkins Controller Node
➤ 05:25 How to add a Jenkins Windows Agent Node for Local system setup
➤ 07:38 Configuring the global security to activate the local Windows Jenkins Agent Node
➤ 10:00 Testing the Jenkins Controller/Agent setup for Windows
➤ 11:48 Conclusion

#jenkins #tutorial  #node  #testing 

Eric  Bukenya

Eric Bukenya

1624713540

Learn NoSQL in Azure: Diving Deeper into Azure Cosmos DB

This article is a part of the series – Learn NoSQL in Azure where we explore Azure Cosmos DB as a part of the non-relational database system used widely for a variety of applications. Azure Cosmos DB is a part of Microsoft’s serverless databases on Azure which is highly scalable and distributed across all locations that run on Azure. It is offered as a platform as a service (PAAS) from Azure and you can develop databases that have a very high throughput and very low latency. Using Azure Cosmos DB, customers can replicate their data across multiple locations across the globe and also across multiple locations within the same region. This makes Cosmos DB a highly available database service with almost 99.999% availability for reads and writes for multi-region modes and almost 99.99% availability for single-region modes.

In this article, we will focus more on how Azure Cosmos DB works behind the scenes and how can you get started with it using the Azure Portal. We will also explore how Cosmos DB is priced and understand the pricing model in detail.

How Azure Cosmos DB works

As already mentioned, Azure Cosmos DB is a multi-modal NoSQL database service that is geographically distributed across multiple Azure locations. This helps customers to deploy the databases across multiple locations around the globe. This is beneficial as it helps to reduce the read latency when the users use the application.

As you can see in the figure above, Azure Cosmos DB is distributed across the globe. Let’s suppose you have a web application that is hosted in India. In that case, the NoSQL database in India will be considered as the master database for writes and all the other databases can be considered as a read replicas. Whenever new data is generated, it is written to the database in India first and then it is synchronized with the other databases.

Consistency Levels

While maintaining data over multiple regions, the most common challenge is the latency as when the data is made available to the other databases. For example, when data is written to the database in India, users from India will be able to see that data sooner than users from the US. This is due to the latency in synchronization between the two regions. In order to overcome this, there are a few modes that customers can choose from and define how often or how soon they want their data to be made available in the other regions. Azure Cosmos DB offers five levels of consistency which are as follows:

  • Strong
  • Bounded staleness
  • Session
  • Consistent prefix
  • Eventual

In most common NoSQL databases, there are only two levels – Strong and EventualStrong being the most consistent level while Eventual is the least. However, as we move from Strong to Eventual, consistency decreases but availability and throughput increase. This is a trade-off that customers need to decide based on the criticality of their applications. If you want to read in more detail about the consistency levels, the official guide from Microsoft is the easiest to understand. You can refer to it here.

Azure Cosmos DB Pricing Model

Now that we have some idea about working with the NoSQL database – Azure Cosmos DB on Azure, let us try to understand how the database is priced. In order to work with any cloud-based services, it is essential that you have a sound knowledge of how the services are charged, otherwise, you might end up paying something much higher than your expectations.

If you browse to the pricing page of Azure Cosmos DB, you can see that there are two modes in which the database services are billed.

  • Database Operations – Whenever you execute or run queries against your NoSQL database, there are some resources being used. Azure terms these usages in terms of Request Units or RU. The amount of RU consumed per second is aggregated and billed
  • Consumed Storage – As you start storing data in your database, it will take up some space in order to store that data. This storage is billed per the standard SSD-based storage across any Azure locations globally

Let’s learn about this in more detail.

#azure #azure cosmos db #nosql #azure #nosql in azure #azure cosmos db

Ruthie  Bugala

Ruthie Bugala

1620435660

How to set up Azure Data Sync between Azure SQL databases and on-premises SQL Server

In this article, you learn how to set up Azure Data Sync services. In addition, you will also learn how to create and set up a data sync group between Azure SQL database and on-premises SQL Server.

In this article, you will see:

  • Overview of Azure SQL Data Sync feature
  • Discuss key components
  • Comparison between Azure SQL Data sync with the other Azure Data option
  • Setup Azure SQL Data Sync
  • More…

Azure Data Sync

Azure Data Sync —a synchronization service set up on an Azure SQL Database. This service synchronizes the data across multiple SQL databases. You can set up bi-directional data synchronization where data ingest and egest process happens between the SQL databases—It can be between Azure SQL database and on-premises and/or within the cloud Azure SQL database. At this moment, the only limitation is that it will not support Azure SQL Managed Instance.

#azure #sql azure #azure sql #azure data sync #azure sql #sql server

Eric  Bukenya

Eric Bukenya

1624106940

Azure Series: Multi-part series on Azure Cloud and related guidelines

In this multi-part Azure Cloud series, I intend to cover the general aspects of Azure in simple terms, the business case for cloud, some deep dives where required, migration strategy, AllOps, security by design framework, reference architectures, and/or demo, and more. I am putting up a Lego bricks approach with multiple layers (in conjunction with the OSI / TCP/IP Layer) and will be adding several Reference architectures (for Web, Batch, Mobile, Data Lake, Big Data, Machine Learning, etc) after assorting and categorizing these Lego pieces. Along the way, I will also discuss the adoption of cloud for different sizes of organizations and building a cloud for scale and how best can make it built to last and at the same time extend it to handshake with other cloud providers to enable Poly Cloud / Multi-Cloud based adoption for the organization.

#azure #azure-data-lake #azure-devops #azure-interview