Since we have a large number of Azure VMs, it is very time-consuming to connect to each machine and manually update software.
Is there a way to do this either automatically or at least centrally for multiple VMs?
For Windows Server 2019 updates, we use our Automation Account for update management.
Thanks for your support.
Nick
As suggested by #joelforysh we can not update automatically.
you can use Mange engine desktop central or SCCM to Schedule the software updates.
Reference
Related
I am in the process of evaluating vendors for upgrading our existing VMware environment. In a conversation with a provider, he told me that vMotion was not possible without a separate SAN appliance or vSAN (the latter requiring 6+ hosts and expensive licensing).
Under the impression that our 3-host cluster already had vMotion licensing and capability, I tried to "vMotion" a running Windows VM using the vSphere client. I was able to "migrate" both the VM and its disk to a new host and datastore respectively, but nowhere did I see the term "vMotion" in the Recent Tasks log at the bottom of the UI. What I did see there was "Migrating Virtual Machine - Active State" and I was able to maintain an RDC connection and interact with the VM all through the migration process.
My question: Am I misunderstanding the term vMotion? Is it different than migration in an "active state"?
Also, assuming vMotion is an unattended convenience and seeing as we already have an image-level backup solution for our VMs and my company is okay with manually restoring those VMs from a backup (as opposed to the convenience of an "instant," unattended, back-end restoration), is vMotion worth the investment in a dedicated SAN server if we're already capable of "live migration" on demand?
And don't worry about selling me on all the benefits of a SAN. Believe me, I'm already with you on that. The people over here who sign the checks just have different priorities is all.
TWIMC: We're in a 3-host cluster, ESXi 6.0 on all. Enterprise Plus licensing.
vMotion is VMware's branding for being able to migrate powered-on / running Virtual Machines from one ESX/ESXi host to another. vSphere UI does not refer to the actual operation in the UI as vMotion except for a number of places where the branding matters i.e. when configuring a feature called Enhanced vMotion Compatibility (EVC) or when enabling vMotion traffic through specific VMkernel virtual network adapter.
On the point about vSAN / physical SAN being mandatory - you already confirmed that you can migrate the VMDKs of a live VM so it's not a complete necessity. The official docs have a section about the limitations of simultaneous comput + storage migration: https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.vcenterhost.doc/GUID-9F1D4A3B-3392-46A3-8720-73CBFA000A3C.html.
I'd bet that migration should be faster if only the memory image of a powered-on VM is migrated - this is especially true in automated DRS setups where VMs are migrated automatically based on a pre-configured policy. Users on reddit seem to have tested this - https://www.reddit.com/r/vmware/comments/matict/vmware_drs_cluster_without_shared_storage_das/gru579m/?utm_source=reddit&utm_medium=web2x&context=3.
Note that I am a VMware employee (albeit not in sales), and you'd probably want a different, unbiased opinion about the product's merits ;)
I am new to cloud and still learning GCP, I exhausted almost all my free credit for GCP within 2 months while learning different modules.
GCP is great and provides a lot of things to ease the development and maintenance process.
But I realized using different modules cost me a lot.
So I was wondering if I could have a big VM box, install MySQL, Docker, and Java and React required components by myself, I can achieve pretty much what I want without using extra modules.
Am I right?
Can I use the same VM to host multiple sites by changing ports of API, or do I need to have different boxes for that?
Your question is out of GCP domain but about IT architecture. You can create a big VM with all installed on it. But you have to manage it by yourselves and the scalability is hard.
You can also have 1 VM per website, but the management cost is higher (patching and updgrade)! However you can scale with a better granularity (per website).
The standard pattern today is to explode your monolith server into dedicated services. The database on a specific server, the docker and Java in another one, and the react in a static component (like Google Cloud Platform).
If you want to use VM, you can use GKE and you containerize your application. It's far more easier to maintain your VM with an automatic tool like K8S.
The ultimate step, is to use serverless and/or full managed solution. Cloud SQL for your database, GCS for your static content, and App Engine or Cloud Run for your backend. Like this, you pay as you use and if you website is not very used, you won't be charged on it (except for the database).
What are the main difference between vsphere 5.5 and vsphere 6? Are there any feature additions? Are they backwards compatible?
Please check this table for a comparison
Vsphere 6/6.5 are a major departure from 5.5. There are a number of small changes but the 2 biggest you will likely notice is that in 6+ they deprecated the c# vCenter client and are moving vCenter to an in house linux based appliance system instead of hosting it on windows.
vSphere 6.5 used the HTML5 to access the vCenter data center management. access from any system in google chrome. completly deprecated the windows based Thin client.
Lot of feature added like HCI - Hyper converged infrastructure.
In this all your compute storage and Network will be integrated with single device.
You can reduce the manual task for management task. creating switch and deploying the configuration in multiple data center with same configuration. replication job will easy.
You can find more info
I want to deploy 10-15 VMWare hosts to cloudstack. This is my first time working with any type of cloud. I was doing research on installation and architecture, I was stuck on a point that for using VMWare hosts i have to install VCenter server, but i can't do that as it's paid. So, please guide me that is there a way of deploying these VMWare hosts on cloudstack without buying any licensed software.
Unfortunately, CloudStack does not support vSphere/ESXi without vCenter. There were several requests to support vSphere/ESXi without vCenter - however, keep in mind that many features vCenter provides must be implemented in CloudStack and it not an easy task.
If you want to remain open source and or/free, consider using Xen with XenCenter or just go pure KVM. I use to use VMware for most of my career and recently transitions to KVM - it was an easy switch and with no regrets.
CloudStack mailing lists are best to answering any setup questions you might have.
All best
-ilya
By design, vCenter is must for CloudStack to manage & build cloud over VMware ESXi hosts. It would be huge exercise to extend the support to ESXi host management without vCenter, which could be limited in features like live migration, VMware distributed virtual switches, DRS etc.
You might consider switching to XenServer which is free and very well supported seamlessly by CloudStack. Feel free discuss your deployment configuration and planning at users#cloudstack.apache.org or dev#cloudstack.apache.org.
Why would anyone use WSO2 Application Server instead of other application servers?
I rather encountered only problems with it, mainly due to class loading issues, so I would appreciate if someone could point out what are the advantages or the use cases when using WSO2-AS really makes a difference.
I can see the benefits of other standalone WSO2 products, but as far as the AS is concerned, I would rather rely on more lightweight servers and just package the libraries I need.
There are number of advantages on WSO2 Application Server.
1.) It provides in-built support for multi-tenancy, in case if you have isolated departments like organization there is no real need to have number of server instances you could simply create a new tenant.
2.) Automatic lazy loading support for tenants, web applications and web services. In a production system a particular tenant/web application/web service can be ideal for sometime it's a waste to allocate hardware resources continuously to such ideal applications specially if you use IaaS. WSO2 application server can detect such ideal tenant/web application/web service and release their resources and tenant/web application/web service will load again when a new request dispatch to the particular tenant/web application/web service.
3.) Wide range of deployment options, support to deploy on-premise, public or private IaaS , public or private PassS such as Apache Stratos. An an example one can deploy his application into WSO2 App Cloud (http://wso2.com/cloud/app-cloud/) instantly without downloading anything, later he can get same experience one of above platforms.
4.) Deployment synchronization feature, a clustered environment you may have very large number of nodes and upgrading application version and configuration changes across the cluster can be headache. Using Deployment synchronization feature you can modify only one node labeled as manger node and Deployment synchronization will take care about synchronize changes across the cluster automatically and consistently.
5.) When developing applications on WSO2 Application Server you can leverage carbon platform level features such as identity, registry, logging, distributed caching, multi-tenancy etc. As an example one can use identity features provided by the platform to mange users, roles permissions also for authentication and authorization without write something own.
6.) Inbuilt support for security standards such SSO among other WSO2 products.
7.) In-build monitoring capability for web services and web application through WSO2 BAM.
8.) Enhanced and rich dashboard for applications and services which facilitate to basic statistics, application management, security wizards, code generations, Try -It tools, run time logging configurations etc.
9.) Enhanced classloading mechanism (starting from AS 5.1.0), within one Application server instance you can have number of virtual server environments per application level. As an example one can specify an application run on minimal Tomcat mode or can assign to run Carbon mode which is ( Tomcat + Carbon platform).
When it come to your specific issue if you can specify your Application Server version and elaborate more on your classloading issue I can provide you more specific answer.
Having said above I want to mention that I'm from WSO2.