devranipankaj163 – Best DevOps

Confluence Assignment & Lab – Pankaj Devrani

devranipankaj163 — Wed, 21 Sep 2022 06:12:39 +0000

What are top 5 use cases of Confluence?

Writing product requirement
Documenting organisation processes
Create Technical and onboarding docs
Create Knowledge Base
Create sprint retrospective and demo pages

What is Space Vs Blogs Vs Pages

Space is used to organise content into a meaningful category. For e.g. Marketing, Development, Products
Blogs are used to share announcements, journal entries, status reports any other timely information
Pages are used to store information like technical knowledge, processes or meeting notes

List out Top 20 Macros of Confluence with one short intro

Macros are used to change the format and layout of the page or display media or perform actions from page.

Anchor macro – used to link specific part of the page
Attachment – display list of files attached
Code block macro – display code example
Children display macro – used to display a list of pages from a specific part of the page hierarchy
Content Report Table Macro – Content Report Table to a page to display a table of pages and blog posts with a specific label along with the creator and modified date
Favorite Pages Macro – display a list of all the pages you’ve saved for later
Jira Chart Macro – build visual graphs and charts from information in Jira
Jira Issues macro – display information from jira
HTML macro – embed content from an external website
Navigation Map Macro – display pages tagged with a specific label in a grid layout.
Network Macro – displays a list of Network activity on a Confluence page or blog post
Page Index Macro – Add the Page Index macro to a page to create an alphabetical index of all pages in the current space
Page Tree Macro – display all or part of the hierarchy of pages in a space
Office Excel Macro – display the contents of an Excel spreadsheet.

PDF Macro – display the content of a PDF document
Office PowerPoint Macro – display the content of a PowerPoint presentation
Status Macro – Add the Status macro to a page to highlight the status of a project, task, or item with a colored lozenge (rounded box)
Table of Contents Macro – Add the Table of Contents macro to a page to help your readers skip directly to the information they’re looking for
View File Macro – allow you to embed an Office or PDF document on a page.
Widget Connector Macro – embed online videos, slideshows, photostreams and more.

Jira Assignment – Pankaj Devrani

devranipankaj163 — Wed, 21 Sep 2022 06:11:59 +0000

What are top 10 use cases of Jira and give short explanations of each use cases
1. Test case management – you can integrate jira – Jira integrates with a variety of add-ons so the QA’s testing slides seamlessly into the software development cycle. Teams can test effectively and iteratively. QA teams use Jira issues, customized screens, fields, and workflows to manage manual and automated tests.
2. Jira for agile teams – Jira Software provides scrum and kanban boards out-of-the-box. Boards are task management hubs, where tasks are mapped to customizable workflows. Boards provide transparency across teamwork and visibility into the status of every work item
3. Project management – Teams can start with a project template or create their own custom workflow. Jira issues, also known as tasks, track each piece of work that needs to pass through the workflow steps to completion.
4. Software development teams – Jira Software provides planning and roadmap tools so teams can manage stakeholders, budgets, and feature requirements from day one. Jira integrates with a variety of CI/CD tools to facilitate transparency throughout the software development life cycle.
5. DevOps teams – Jira Software integrates with first- and third-party tools throughout the DevOps lifecycle, including code and version control tools like Bitbucket, GitHub, and Gitlab, documentation and knowledge management tools like Confluence, and monitoring and operating tools like Opsgenie
6. Product management teams – In Jira Software, teams can build a roadmap that’s associated with each project. The roadmap enables teams to sketch out the longer-term view of their work as well as track and share progress for their roadmap
7. Task Management – Create tasks for yourself and members of your team to work on, complete with its details, due dates, and reminders. Utilize subtasks to breakdown larger items of work. Allow others to watch the task to track its progress and be notified when it’s completed.
8. Bug tracking – Jira ensures that bugs are automatically assigned and prioritized once they are captured. Teams can then track a bug through to completion
9. Planning – With Jira software you can effectively plan the road maps for different projects and organisations.
10. Jira for requirements gathering – you can use Jira and confluence combined for requirement gathering and adding details into the tickets for the purpose of giving context to the people working on it.
Write down step by step process of adding custom fields in Jira issue with screenshot attached of each step
- Open the proejct and go to project settings from the left menu
- Now click on Issue types
- Choose issue. For e.g. Task
- From the right side choose type of custom field from Create a Field Section and add details to the field
Write down step by step process of adding New workflow in Jira with screenshot attached of each step
1. Go to Settings () > Issues
2. Choose Workflows and click Add workflow.
3. Add name and click on add
4. Click Add status to add a new step to the workflow (you can add existing statuses or create new ones)
5. Click Add transition or drag from a node on one status to another to add a transition
6. Add more status and transition based on requirement
List of Top 10 tasks to be done by Jira Administrator
1. Setting up Jira
2. Configuring User Permissions
3. Optimizing Workflows
4. Prioritize Security
5. Remove Unnecessary Workflows
6. Add extensions
7. Managing users
8. Adding users
9. Creating projects
10. Integrating third party vendors
List of Top 10 tasks to be done by Jira Project Owner
1. Configuring project details
2. Create issues
3. Customizing issues
4. Integrating Confluence and other thrid pary vendors
5. Managing project workflow
6. Managing project roles and members access
7. Customizing workflow for the project
8. Creating releases
9. Configuring Automation
10. Configuring notifications

Git Assingment -Pankaj Devrani

devranipankaj163 — Sat, 17 Sep 2022 08:22:47 +0000

Q1. What are differences between the git distributed model and svn server-client model?
1. Git is open source distributed vice control system whereas Apache Subversion is an open source software version and revision control system under Apache license
2. Git has a Distributed Model. But SVN has a Centralized Model.
3. In git every user has their own copy of code on their local like their own branch but In SVN there is central repository has working copy that also make changes and committed in central repository.
4. In git we do not required any Network to perform git operation but in SVN we required Network for runs the SVN operation.
5. In git we create only .git directory but in SVN we create .svn directory in each folder.
6. Git is slower with large number of binary files compared to SVN
Q2. Explain the use of Git Workspace – Staging – Repository area in detail with few use case
Q3. Write down the Types of git branch and use cases of it
1. Master – Used for production deployment
2. Feature branch – Used by developers for developing new features
3. Release branch – Used to deploy production ready features to production
4. Hotfix branch – Used to quickly deploy fix to production
5. Develop branch (aka Integration branch) – Used by developers to validate features in develop environment
Q4. Explain the Types of Merging and use cases of it.
1. Fast Forward Merge: When you create a branch, make some commits in that branch, the time you’re ready to merge, there is no new merge on the master. That way master’s pointer is just moved straight forward and history is one straight line. Command git rebase
2. Recursive Merge: In recursive merge, after you branch and make some commits, there are some new original commits on the ‘master‘. So, when it’s time to merge, git recurses over the branch and creates a new merge commit. Command: $ git merge–no-ff
3. Octopus Merge: Octopus Merge strategy resolves cases with more than two heads but refuses to do a complex merge that needs manual resolution. It is primarily meant to be used for bundling feature branch heads together. This is the default merge strategy when pulling or merging more than one branch. Command $ git merge -s octopus
4. Resolve Merge: This strategy can only resolve two heads (i.e. the current branch and another branch you pulled from) using a 3-way merge algorithm. It tries to carefully detect criss-cross merge ambiguities and is considered generally safe and fast. Command git merge -s resolve
5. Subtree Merge: This is a modified recursive strategy. When merging trees A and B, if B corresponds to a subtree of A, B is first adjusted to match the tree structure of A, instead of reading the trees at the same level. This adjustment is also done to the common ancestor tree. Command git merge -s subtree
Q5. Create a Table with Top 20 Git commands along with one line explanations like self cheat sheet.
- git config – sets the author name and email address respectively to be used with your commit. For e.g. git config -global user.name “[name]”
- git init – used to start a new repository. For e,g, git init [repository name]
- git clone – used to obtain a repository from an existing URL. For e.g. git clone [url]
- git add – adds one or more files to the staging area. For e.g. git add *
- git commit – records or snapshots the file permanently in the version history. For e.g. git commit -m “[ Type in the commit message]”
- git diff – shows the file differences which are not yet staged. For e.g – git diff –staged
- git reset – unstages the file, but it preserves the file contents. git reset [commit]
- git status – lists all the files that have to be committed.For e.g. git status
- git rm – deletes the file from your working directory and stages the deletion.
- git log – used to list the version history for the current branch.
- git show – hows the metadata and content changes of the specified commit.. For e.g. git show [commit]
- git tag – used to give tags to the specified commit. For e.g. git tag [commitID]
- git branch – lists all the local branches in the current repository. Also git branch [branchName] creates a new brnach
- git checkout – used to switch from one branch to another. For e.g. git checkout -b [branch name]
- git merge – merges the specified branch’s history into the current branch. For e.g. git merge [branch name]
- git remote – used to connect your local repository to the remote server. For e.g. git remote add [variable name] [Remote Server Link]
- git push – sends the committed changes of master branch to your remote repository. For e.g. git push [variable name] master – pushes Also pushes all branches to your remote repository with this command git push -all [variable name]
- git pull – fetches and merges changes on the remote server to your working directory.
- git stash – temporarily stores all the modified tracked files.

Docker Assignment – Pankaj Devrani

devranipankaj163 — Sat, 17 Sep 2022 06:20:18 +0000

Components of Docker and its Brief Summary
- Docker has below components.
  - dockerd – is a docker daemon which listens for docker API requests using three different types of sockets(unix, tcp and fd)
  - Containerd – is responsible for managing container lifecycle. It takes care of image push/pull, managing storage, invoking execution of containers, managing network primitives
  - RunC – is command-line client for running applications packed according to OCI format and is a compliant implementation of the OCI
What is the differenece between docker pause and unpause?
- pause – suspends al processes in the specified containers.
- unpause- un-suspends all the processes in the specified containers.
What is the differenet between docker stop and kill?
- docker stop command the container will stop gracefully using SIGTERM and SIGKILL where as docker kill command terminates the entrypoint process abruptly using SIGKILL signal(which can incurr of data or damage to file system)
What is the difference between docker exec and attach?
- docker attach – is used to attach your terminal inside running container.
- docker exec – is used to run a new command in the running container
List of dockerfile instructions and its Brief Summary?
- FROM – pulls base images from the registry
- ADD – copies image from host to container
- ENV – Sets an environment variable in the new container
- RUN – executes commands in a new layer on top of the current image and commit the results and committed image will be used for next step in the Dockerfile. RUN [“executable”, “param1”, “param2”] (exec form) or RUN (shell form)
- COPY – copies new files or directories from and adds them to the filesystem of the container at the path .
- EXPOSE – exposes the port of the container to the host using tcp(default) or udp
- ENRTYPOINT allows you to configure a container that will run as an executable
- CMD – to pass on defaults for a container. The parameters for entry point can be passed using CMD.
- VOLUME – Creates a shared volume that can be shared among containers opr by the host machine

6. What is the differenet between CMD vs Entrypoint
- ENRTYPOINT – It starts the process you want to run after staring the container
- CMD – is used to either pass on defaults for a container or . The parameters for entry point can be passed using CMD.