I have created a Neo4j VM Enterprise 4.0 on Azure.
On this VM I called call dbms.procedures. I saw that Graph Data Science (GDS) is not installed on this VM when this VM was created on Azure. Usually I work with Neo4j Desktop and I just had to click on install button.
With a Neo4j VM in Azure I don't know how to install GDS.
What can I do ?
The instructions for installing APOC are here.
Related
I have a requirement of Windows version 1809/build 17763 VM on azure for some task. I choked and was not able to find the VM on azure. How can I setup windows VM with above version/build
You can create a VHD with Windows OS version you need locally then upload this VHD to Azure and use this VHD to create a managed image so that you can create VMs by this managed image.
For detailed steps see this official doc.
Btw, I noticed that there is a VM image based on windows server 1809, you can find it while creating VMs => see all images:
I have implemented a .Net console application which pulls the data from databricks Applications .
I have installed SIMBA ODBC drivers in my local and was able to connect to databricks cluster from my local .net application.
Now I want to host my .net application in AZURE PAAS .So how do I install SIMBA ODBC drivers in AZURE PAAS ?
Please let me know . Thanks in advance !
As that resembles you are connecting to Hive using .Net Application.
You can use data bricks REST API.
https://docs.databricks.com/dev-tools/api/latest/index.html
(OR)
You can use the docker Image Container by adding Docker to your application and run the docker file. so that the dependency drivers & Application gets installed & form an image container. The Image needs to be registered in the Azure container instance & link the container instance to Azure App Service.
I am trying to migrate Linux VM running on AWS to Azure but it has Kernel version (4.4.0-1088-AWS) which is not supported with Azure.
I tried to use Azure Site Recovery to replicate the Virtual machine directly to Azure but the mobility service agent is not installing there due to Kernel version not being supported.
Is there any way to migrate those VMs or Is there any way to clone the same VMs to Azure by creating a new instance and moving data and configuration.
Current OS Version is Ubuntu 14.04
You can create new instance as per requirement Ubuntu version and then copy manually data
You can treat the Linux VM as physical and migrate to Azure using Azure migrate or Azure Site Recovery.
For more details, see a similar discussion on the MSDN forum - https://social.msdn.microsoft.com/Forums/en-US/e542831d-a506-495f-8d4b-61e093c5345a/migrate-from-aws-to-azure?forum=hypervrecovmgr
We have a requirement to Migrate EC2 instance of AWS to Azure as VM, have been trying to implement the same from this source,
unable to complete the process. Tried and stuck on Protection Group.
I'm looking in these other links
Migrating a VM from EC2 to Azure at 300 Mbps For this I'm able to create VM in Classis portal but unable connect to it only port 80 is active all other ports are not working
Migrate virtual machines in Amazon Web Services (AWS) to Azure with Azure Site Recovery
https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-vmware-to-azure
https://aws.amazon.com/ec2/vm-import/ on trying this I'm getting this unresolved EC2 API export to S3 ACL issue
Can anyone suggest me a workflow on how to implement this?
I achieved this by downloading AWS EC2 VHD to an Hyper-V enabled machine on-premises.
Following are the steps.
Create VM from VHD and Remove AWS related software.
Open Hyper-V manager and create VM from the downloaded VHD.
Log in to the VM and uninstalled AWS related services from control panel (AWS Drivers, EC2configService, AWS Tools for Windows, AWS SSM Agent)
All these changes were affected on the VHD.
Upload the converted VHD to Azure Storage (using the Azure PowerShell cmdlets)
Create av Azure VM-Image from that VHD in Classic Azure Portal
Create an Azure VM using the new Image.
Created a classic VM in Azure portal.
For creating a VM under Resource manager, created VHD of newly migrated VM and using that created a new VM in azure portal.
Mention any workflow other than this.
There are multiple ways to migrate machines.
Azure Migrate: Server Migration is one tool that lets you do that and is the recommended way to rehost x86 machines to Azure. You can treat the EC2 instance (AWS VM) as though it were a Physical machine and migrate it to Azure as long as the Operating System on the machine is supported by the Physical Server Migration flow (also check the kernel version to ensure it is supported) https://learn.microsoft.com/en-us/azure/migrate/tutorial-migrate-physical-virtual-machines
That being said, EC2 VMs may have some changes that you’ll need to make before migrating them, or it may cause issues once in Azure. For example if they are using cloudinit for VM provisioning, you may want to disable cloudinit on the VM before replicating it because the provisioning steps performed by cloudinit on the VM maybe AWS specific and wont be valid after the migration to Azure.
The other thing to note is if the VM is a PV VM (para-virtualized) and not a HVM VM you may not be able to run it as is because paravirtualized VMs use a custom boot sequence in AWS (you may be able to get over this challenge by installing GRUB 2 on the VM and building grub)
The recommendation, if you are using this approach, is to always perform a test migration first to test the process.
I am setting up Windows HPC cluster according to the guide and sample code provided:
http://msdn.microsoft.com/en-us/library/hh560241(v=vs.85).aspx
The sample code has a Windows application to generate the cspkg and cscfg files. I can use these files to make the deployment on Azure successfully. But the problem is that the OS installed on the instance is Windows Server 2008 R2 rather than Windows Server 2008 R2 HPC Pack, which is defined in the csdef file in the following code. In addition, the config.EnableL2H() and config.EnableSOA() have also been invoked.
Is there something I did wrong when configuring the configuration files? Any suggestions will be appreciated.
Thanks,
Hui
I've found the problem and fixed it. The problem is the fire wall issue between SQL Azure server and Azure instance deploying service. Windows HPC cluster reply on the SQL database to store the jobs history within HPC job scheduler. Without connecting to SQL server database, the process of staging the HPC pack module to Azure Blob fails.
The solution is to adjust the SQL Azure server fire wall filter management rules and check the box "enable communication between SQL server and the other Azure services".
Thank you,
Hui