Bugzilla is a vigorous, featureful, and mature bug-tracking system or defect-tracking system that allows teams of developers to maintain track of unsettled bugs, issues, problems, enhancement, and other change requests in their products with effectiveness. Organizations are now turning to Bugzilla as it offers appropriate workflow management, custom fields, and bug visibility control.
Features:
Advanced Search Proficiencies: Bugzilla provides two types of search in which the first includes a basic Google-like bug search that is very simple for new users and searches the full text of a bug. The next is a very advanced search where you can create any search that you want, including time-based searches.
Controlled e-mail notifications by user preferences: You can get an e-mail about any change made in Bugzilla, and the type of notifications that you get on bugs is completely controlled by your personal user preferences.
Bug Lists in Multiple Formats (Atom, iCal and so on): While searching for the bugs, you can get the results in many formats rather than just the basic HTML layout. Bug lists are available in Atom and they are also available in iCalender format. If you are utilizing the time-tracking features of Bugzilla, then you can see where your bugs fit into your calendar. In addition, there are even more formats available, like long, printable report format, CSV format, and other XML formats as well.
Automatic Duplicate Bug Detection: Bugzilla has the calibre to automatically look for similar bugs in the system and enable the user to add themselves to the CC list of one of those bugs rather than filing a new one.
It will take a few minutes for your VM to be deployed. When the deployment is finished, move on to the next section.
Connect to virtual machine
Create an SSH connection with the VM.
bashCopy
ssh azureuser@10.111.12.123
Usage / Deployment Instructions
Step 1: Access the Bugzilla in Azure Marketplace and click on Get it now button.
Click on Continue and then click on Create.
Step 2: In the create a virtual machine window, enter or select appropriate values for zone, machine type, and so on.
Click on create.
Step 3: The below window confirms that VM was deployed.
Step 3: Check perl –v
Step 4: Add the database configuration as below:
Database User: root
Database Password: Niles@123
Database name: bugzilla
Host: localhost
Step 5: cd /var/www/html/bugzilla-5.0.6
./checksetup.pl
/usr/bin/perl install-module.pl –all
nano /var/www/html/bugzilla/localconfig
Again check
./checksetup.pl
nano /etc/apache2/sites-available/bugzilla.conf
Testing the Installation:
/var/www/html/bugzilla-5.0.6/testserver.pl http://<ip of running ec2 instance>
Accessing Bugzilla at Web Interface:
Enjoy your Application.
Until now, small developers did not have the capital to acquire massive compute resources and ensure they had the capacity they needed to handle unexpected spikes in load. Amazon EC2 enables any developer to leverage Amazon’s own benefits of massive scale with no up-front investment or performance compromises. Developers are now free to innovate knowing that no matter how successful their businesses become, it will be inexpensive and simple to ensure they have the compute capacity they need to meet their business requirements.
The “Elastic” nature of the service allows developers to instantly scale to meet spikes in traffic or demand. When computing requirements unexpectedly change (up or down), Amazon EC2 can instantly respond, meaning that developers have the ability to control how many resources are in use at any given point in time. In contrast, traditional hosting services generally provide a fixed number of resources for a fixed amount of time, meaning that users have a limited ability to easily respond when their usage is rapidly changing, unpredictable, or is known to experience large peaks at various intervals.
Traditional hosting services generally provide a pre-configured resource for a fixed amount of time and at a predetermined cost. Amazon EC2 differs fundamentally in the flexibility, control and significant cost savings it offers developers, allowing them to treat Amazon EC2 as their own personal data center with the benefit of Amazon.com’s robust infrastructure.
When computing requirements unexpectedly change (up or down), Amazon EC2 can instantly respond, meaning that developers have the ability to control how many resources are in use at any given point in time. In contrast, traditional hosting services generally provide a fixed number of resources for a fixed amount of time, meaning that users have a limited ability to easily respond when their usage is rapidly changing, unpredictable, or is known to experience large peaks at various intervals.
Secondly, many hosting services don’t provide full control over the compute resources being provided. Using Amazon EC2, developers can choose not only to initiate or shut down instances at any time, they can completely customize the configuration of their instances to suit their needs – and change it at any time. Most hosting services cater more towards groups of users with similar system requirements, and so offer limited ability to change these.
Finally, with Amazon EC2 developers enjoy the benefit of paying only for their actual resource consumption – and at very low rates. Most hosting services require users to pay a fixed, up-front fee irrespective of their actual computing power used, and so users risk overbuying resources to compensate for the inability to quickly scale up resources within a short time frame.
No. You do not need an Elastic IP address for all your instances. By default, every instance comes with a private IP address and an internet routable public IP address. The private address is associated exclusively with the instance and is only returned to Amazon EC2 when the instance is stopped or terminated. The public address is associated exclusively with the instance until it is stopped, terminated or replaced with an Elastic IP address. These IP addresses should be adequate for many applications where you do not need a long lived internet routable end point. Compute clusters, web crawling, and backend services are all examples of applications that typically do not require Elastic IP addresses.
You have complete control over the visibility of your systems. The Amazon EC2 security systems allow you to place your running instances into arbitrary groups of your choice. Using the web services interface, you can then specify which groups may communicate with which other groups, and also which IP subnets on the Internet may talk to which groups. This allows you to control access to your instances in our highly dynamic environment. Of course, you should also secure your instance as you would any other server.