Upgrade in Azure Cloud to v0.1.2-243

 


Upgrading Azure Cloud installation of OpenRose - Requirements Management - An Open Source and FREE Requirements Management Application / Tool.

This guide helps users to Upgrade all required software and components to run OpenRose in Azure Cloud environemtn. It guides users to upgrade 

  • OpenRose WebUI front-end 
  • OpenRose API back-end 

Direct Link to YouTube Video : 

https://www.youtube.com/watch?v=RAqYgCKiLQs

Video Transcript :

Hello once again, and welcome to OpenRose—a FREE and Open Source Requirements Management Application / Tool. You can find more information about OpenRose at 

https://github.com/openrose

Here, we can see that we have two releases available. The one currently installed in the cloud environment, which is Azure Cloud, is version 0.1.0.0. Now that a new version is available, we are ready to deploy it in our cloud environment.

To deploy the new version, we first need to connect to our cloud shell. This means we must open the cloud shell in Azure Cloud. Once inside, we can proceed with downloading the latest version and deploying it to the web. Let me show you the simple commands we will use.

First, log into the Azure portal, navigate to the cloud shell, and run a command that lists all the organizations or subscriptions you have access to. This command displays all accounts associated with your environment. Next, we will connect to a specific subscription using a subscription ID. By running "account set subscription" and providing the subscription ID, we ensure that we are connected to the correct subscription. Please make sure to connect to the subscription where you have deployed OpenRose.

After connecting to the subscription, verify that you are indeed connected to the correct one by running "account show output table". This command will display the relevant details in a table format. 

Next, we proceed with downloading the package. The package URL follows the format "win_x86_openrose_API_version_number". We are deploying the x86 architecture because we are using minimal resources in our Azure subscription. Since our app services environment does not support deploying the x64 version, we are opting for the x86 packages for both the API and the web UI, storing them in our home locations.

After downloading, we must stop both services—OpenRose API and OpenRose Web UI. These services are hosted in separate app services within Azure. You can see the web UI app service and the OpenRose API app service; these are two distinct deployments.

Now, let's proceed with the web deployment. It’s a simple command: "web app deploy source is a zip file". The config zip file belongs to the "OpenRose" resource group. The first deployment we will perform is for OpenRose API, retrieving the package stored in the home location. Once the API deployment is complete, we will deploy the web UI using a similar command, but here, we specify OpenRose Web UI as the app service within our resource group. The web UI zip file is then retrieved and deployed.

Once both deployments are complete, we do not need any additional configuration changes. Since we use environment variables to manage API connections and SQL server connections, our setup remains unchanged. If we check the environment variables in the web UI, we will find the API base URL, which points to our API instance. Similarly, in the API environment variables, we will see the connection string for our SQL Azure server. 

With all components already configured in the cloud, the only step remaining is to start the web application. First, we restart the API. This step is essential because, when upgrading from the previous version, the API may need to execute database schema changes on SQL Server. If any schema updates are required, they are applied at startup. Though this architecture might change in the future, for now, the API startup checks for schema modifications and applies them using Entity Framework Core.

After restarting the API, we also restart the web UI. It’s advisable to wait a minute or two for the API to complete any necessary database migrations before starting the web UI. While starting the web UI immediately is an option, waiting ensures a smooth transition.

Once the web UI is operational, access the web UI portal and click on the browse option. Here, I have already started my application. Switching back to OpenRose in the cloud, you can see that the version has successfully been upgraded from 0.1.0.0 to 0.1.2-243. In the future, we aim to ensure that version numbers match the actual release tags applied in our GitHub environment.

The upgrade process is quite simple, involving just a few steps:

  1. Connect to the correct subscription.
  2. Download the required deployment packages.
  3. Stop the app services for both the API and web UI.
  4. Deploy the web applications for OpenRose API and OpenRose Web UI.
  5. Restart the OpenRose API and OpenRose Web UI

Once these steps are completed, your upgrade to version 0.1.2-243 in the cloud will be fully finalized.

We hope you find this guide helpful and that you will use OpenRose in various environments, particularly in the cloud. Please share OpenRose with others who might benefit from this free and open-source application. Thank you for your time today. Have a great day!




Comments

Post a Comment

Popular posts from this blog

Introduction to OpenRose - Requirements Management

Image
Watch it on YouTube at : https://www.youtube.com/watch?v=P0x3ZaHg8sA OpenRose - Requirements Management Application VIDEO TRANSCRIPT Hello, and thanks for joining in for the launch of OpenRose, an open-source requirements management application. The main purpose is to help users and teams "do it right" and ultimately reduce waste. OpenRose is released on GitHub at [github.com/OpenRose](https://github.com/OpenRose). Users can look at the source code and documentation at the same location. Let me do a quick demo of the application. In this environment, I'm using Windows 11 on a desktop computer, not a server. I have installed IIS and deployed a web deployment package over IIS. When you connect to OpenRose, on the homepage, you will see a welcome message like this: "Welcome to OpenRose." One would start by creating a new project. For this demo, I've created two separate projects. The first project is a small example of how I converted a document published b...
Read more

What is Requirement?

Image
What is Requirement? OpenRose - Requirements Management An Open Source and FREE Requirements Management Application / Tool Direct Link to YouTube Video : https://www.youtube.com/watch?v=3qQzKbfvRPA Video Transcript :   Hi, welcome to OpenRose, an open-source and free requirements management application. Please visit https://github.com/openrose for more information. Let's go to the project dashboard, and this time, let's open a deep hierarchical level project. This is just a demo project, so when I open that project in the TreeView and start expanding the project, I can see some sample item types along with a Parking Lot, which is the system item type. Inside item type one, I have a top-level item, then item one and item two, which are broken down into further items. You can see I've given the names which indicate a kind of logical hierarchical structure in the name. Here, you can see L1, L2, L3, L4—that's the level. The project is considered as level one, and item ...
Read more

Details View - OpenRose - Requirements Management

Image
    Details View OpenRose - Requirements Management An Open Source and FREE Requirements Management Application / Tool Direct Link to YouTube Video : https://www.youtube.com/watch?v=FC67o7lUy3I Video Transcript : Hello. OpenRose is a requirements management application, which is freely available and published on GitHub. Simply go to github.com/openrose to find more. Today, we will discuss the Details View. When you go into the Projects section where you can see your list of projects, there are two main views: the Tree View and the Details View. When I click on Details View, I enter the project one level at a time, or I exit the project one level at a time. Inside the project, we know that there are item types. In this particular view, we can see that I have a parking lot, which is a system item type, and four other item types that I have created. This is a public document published by Barkley's Bank, which I have tried converting into some sort of specification or requirem...
Read more