Created 11-01-2017 10:43 AM
Hi Team,
We are exploring Cloudbreak in Azure. We want to use our custom image for HDP installation as some libraries needs to be present in the cluster nodes.
As suggested in the article http://sequenceiq.com/cloudbreak-docs/master/images/, i have created "arm-images.yml" in etc directory in cloudbreak-deployment directory. The whole path is "/root/cloudbreak-deployment/etc".
below is the content in arm-images.yml file.
azure_rm:
East Asia: https://sequenceiqeastasia2.blob.core.windows.net/images/cb-2016-06-14-03-27.vhd
East US: https://mystoredisks1558.blob.core.windows.net/vhds/Hdptestimage120171031154408.vhd
Central US: https://sequenceiqcentralus2.blob.core.windows.net/images/cb-2016-06-14-03-27.vhd
North Europe: https://sequenceiqnortheurope2.blob.core.windows.net/images/cb-2016-06-14-03-27.vhd
South Central US: https://sequenceiqouthcentralus2.blob.core.windows.net/images/cb-2016-06-14-03-27.vhd
North Central US: https://sequenceiqorthcentralus2.blob.core.windows.net/images/cb-2016-06-14-03-27.vhd
East US 2: https://mystoredisks1558.blob.core.windows.net/vhds/Hdptestimage120171031154408.vhd
Japan East: https://sequenceiqjapaneast2.blob.core.windows.net/images/cb-2016-06-14-03-27.vhd
Japan West: https://sequenceiqjapanwest2.blob.core.windows.net/images/cb-2016-06-14-03-27.vhd
Southeast Asia: https://sequenceiqsoutheastasia2.blob.core.windows.net/images/cb-2016-06-14-03-27.vhd
West US: https://sequenceiqwestus2.blob.core.windows.net/images/cb-2016-06-14-03-27.vhd
West Europe: https://sequenceiqwesteurope2.blob.core.windows.net/images/cb-2016-06-14-03-27.vhd
Brazil South: https://sequenceiqbrazilsouth2.blob.core.windows.net/images/cb-2016-06-14-03-27.vhd
I have put my custom image path for East US and East US 2.
When i start deploying cluster it is taking the default image "https://sequenceiqeastus12.blob.core.windows.net/images/hdc-hdp--1706211640.vhd" came up with Cloudbreak.
i have checked the log, but did not get any related info.
Does any one have any idea.
Thanks in Advance....
Created 11-27-2017 12:38 PM
Hi @Paramesh malla,
it seems to me that there is a documentation error. Please modify your file and replace "azure_rm:" with "azure:"
You can check the current file here.
Created 11-27-2017 12:38 PM
Hi @Paramesh malla,
it seems to me that there is a documentation error. Please modify your file and replace "azure_rm:" with "azure:"
You can check the current file here.
Created 01-18-2018 10:36 AM
Hi @mmolnar,
Thanks, that worked.
But i am getting an error, as that image is not having public access. Any tip to resolve it other than giving publicly available image?
Created 01-19-2018 02:43 PM
You can use an Azure Shared Access Signature to restrict the access to your VHD based on time or access policy. You can generate the URL with Azure Storage Explorer like documented here and replace the original in arm-images.yml.
Created 02-21-2018 02:13 PM
Hi,
Can i update and use new image, Once i launched the cluster with my custom image?
if so, can you tell me how?
Thanks in Advance.
Created 02-21-2018 02:18 PM
New images can only be applied to new clusters so it is not possible to replace an image of a running cluster.
Hope this helps!
Created 02-21-2018 02:22 PM
@pdarvasi
Hi, thanks for your quick reply.
What if i want to update some configuration/package in image? is there any way? like can i run some command (through cloud break) after creating new VM from image?
Thanks Again.
Created 02-21-2018 02:25 PM
Yes, you can utilize the recipe functionality of Cloudbreak like documented here.