We have participated in a cloud hackfest together with Microsoft, U-Btech and Puppet to create a portal for automatic deployment of an Azure environment for R&D/QA purposes.
Details of the hackfest can be found in the link below:
https://microsoft.github.io/techcasestudies/devops/2017/03/14/risco.html
Monday, March 27, 2017
Sunday, January 1, 2017
Duplicating an Azure ARM VM
On Azure classic deployments, duplicating an Azure VM due to QA/R&D needs was easily done via the portal using the capture image option and later creating a VM from that image.
Unfortunately on ARM deployments this option is not available, so the course of action to create such a duplicate, is to use Powershell scripts.
In the below example, I deploy to an existing resource group and virtual network, but the scripts can be easily altered to create those as well if needed.
For the first step, I shutdown the VM I wanted to duplicate and copied its OS disk to a new storage/blob container (same blob container can be used, just need to rename the disk). To copy the disk I used Azure storage explorer.
And now for the Powershell scripts.
Unfortunately on ARM deployments this option is not available, so the course of action to create such a duplicate, is to use Powershell scripts.
In the below example, I deploy to an existing resource group and virtual network, but the scripts can be easily altered to create those as well if needed.
For the first step, I shutdown the VM I wanted to duplicate and copied its OS disk to a new storage/blob container (same blob container can be used, just need to rename the disk). To copy the disk I used Azure storage explorer.
And now for the Powershell scripts.
Tuesday, December 27, 2016
Enable logging on Fortigate-VM for Azure
Fortinet Fortigate-VM for Azure marketplace image, comes without a disk for logging by default, so in order to have the logging ability, an additional disk needs to be added.
Note: This procedure requires a couple of reboots to the firewall, so best done prior to the Fortigate being in production environment.
Step 1: Add logical disk to the Fortigate VM via the Azure portal (Powershell can also be used):
Open the Fortigate VM blade -> Disks ->Attach new
Step 2: Reboot the Fortigate (without reboot the Fortigate will not detect the newly added disk) - reboot can be done from the Fortigate System dashboard:
Step 3: Once the Fortigate reloaded, go into the CLI console which is in the System dashboard and run the following command: execute formatlogdisk, a long reboot will occur (around 15 min).
Step 4: Once reboot is completed and the Fortigate is up and running again, go to the Log & Report -> Log Config -> Log settings and check the "Disk" and "Enable Local Reports" settings.
Step 5: Go to the Traffic Logs, generate traffic towards to Fortigate and check that the logs are shown.
Note: This procedure requires a couple of reboots to the firewall, so best done prior to the Fortigate being in production environment.
Step 1: Add logical disk to the Fortigate VM via the Azure portal (Powershell can also be used):
Open the Fortigate VM blade -> Disks ->Attach new
Step 3: Once the Fortigate reloaded, go into the CLI console which is in the System dashboard and run the following command: execute formatlogdisk, a long reboot will occur (around 15 min).
Step 4: Once reboot is completed and the Fortigate is up and running again, go to the Log & Report -> Log Config -> Log settings and check the "Disk" and "Enable Local Reports" settings.
Step 5: Go to the Traffic Logs, generate traffic towards to Fortigate and check that the logs are shown.
Subscribe to:
Comments (Atom)