If I created a VM Azure machine and setup/installed all required nodejs, npm modules, IIS, mongoDb. on basis on my usages I shut down the VM machine. After start the VM machine, Will I get the entire machine with all installation.
Yes, you will. VMs are stateful. The only thing that might change (depending on the setup) is the internal\external IP addresses.
Azure even provides auto shutdown feature, to save you some clicking.
Related
I install supervisord and mysql via azure ssh.
But after a few days, all my installed packages are disappeared, and all my tables in mysql are also gone.
It seems that the server is updated regularly, but my files are fine.
Do i need to set somethings?
You are using a PaaS service, not a virtual machine and you can't install applications like MySQL on it. Well, Azure let you do it but as you experienced, when Azure does its maintenance, your app will/can be moved to another host. This is normal behavior.
One solution on App Service is to use containers and a Docker Compose file.
I have VM scale set for my Azure ServiceFabric Application deployed in Azure. I need to run RabbitMQ server on each virtual machine in my VM scale set when it starts (especially actual when I am going to scale up my cluster and new VM is going to be created). In other words I want make queue run automatically. Are there any possibilities to do the next steps after VM has been launched:
Check if RabbitMQ is already installed.
Download and install if not from specified URL.
If it has been installed just run it.
I guess this issue can be solved with virtual machine scale set Automation Script, but I am not sure. Any ideas and suggestions?
You could do this using a VM custom script extension. An extension runs on every new VM when a scale set is deployed or when it scales out.
Your extension could do the checks, install and run, and perhaps create a service so RabbitMQ runs if the VM is rebooted etc.
The following articles provide more details on deploying apps with scale sets:
Deploy your application on virtual machine scale sets
How are Applications deployed on VM Scale Sets?
I created a virtual machine using an Ubuntu image with Discourse preloaded from the Azure gallery. After the automatic setup completed, I can see that the VM is running but I can't connect to it in order to view the machine remotely. I don't see any setting that can resolve this for me. Does anyone know what is happening?
You should use a client like Bitvise SSH Client, which is recommended by Microsoft, to perform tasks on your ubuntu VM.
I have a RavenDb installed as a service in my Azure Virtual Machine. It currently works fine but I've seen some post telling it is risky to do (e. g. there are some problems with locks when your machine is shut down by Azure). Are those problems still actual (or may be they were already resolved by RavenDb team) or should I look at RavenHQ?
On Azure, you want to use RavenHQ.
In Azure, you need to run multiple machines in a replicated scenario. You cannot run on a single machine, since it is quite frequent that Azure will shut down your machine.
You also need to deal with backups, recovery and many other things.
Does anyone know if one can host a website using the VMRole in Windows Azure?
If I have IIS running on the VM can I access that from the outside?
Also, if I scale to multiple instances of the same VM, will that endpoint be automatically load balanced, just like a WebRole?
Note: There are some requirements that I have that cannot be accomplished with the WebRole, so that is why I am not using it. (if you were wondering)
Thanks in advance!
Yes, you can host a web site in an VM Role. The VM Role must be Windows 2008 R2, which has IIS, so you should have everything you need to support your website. You'll just need to work with HyperV locally to construct the VHD, then prep it with Windows Azure tools, etc.
Just curious: What specific requirements do you have that cannot be accomplished with a Web Role? There are three core use cases for VM Role:
The setup process cannot be automated
The setup process is not 100% reliable (e.g. installers periodically fail)
The setup process takes too long (maybe more than 5 minutes or so)
With startup tasks, you shouldn't have any restrictions on installing software, registering COM controls, modifying the registry, etc.