Home / user-531786

Geordie's questions

Martin Hope
Geordie
Asked: 2020-09-12 10:45:24 +0800 CST
  • 0

I'm setting up a simple hub-spoke configuration of VNets in Azure. Hub contains a VPN gateway then creating spokes for storage, compute etc. My main concern is latency so I'd rather not setup custom routing through the hub VNet.

Since the storage spoke will need to see the compute spoke, do I need to setup peering connections between the spokes or does Azure route through the hub VNet automatically?

azure virtual-network peering
Martin Hope
Geordie
Asked: 2019-09-04 17:19:22 +0800 CST
  • 1

I'm developing a docker image that requires access to shared data in a Azure file share. I want to test this locally before deploying to Azure and I'm not using swarms.

I'm using the Azure CloudStor Docker plugin

I've successfully installed the Cloudstor plugin locally:

docker plugin install --alias cloudstor:azure --grant-all-permissions docker4x/cloudstor:17.06.1-ce-azure1 CLOUD_PLATFORM=AZURE AZURE_STORAGE_ACCOUNT_KEY="..." AZURE_STORAGE_ACCOUNT="..."

And successfully compiled my container using a Docker file:

FROM nvidia/cuda:10.1-base-ubuntu18.04

# Update + Prerequisites
RUN apt-get update \    
    && apt-get -y install build-essential checkinstall \
    && apt-get -y install sudo \
    && apt-get -y install curl \
    && apt-get -y install zip \
    && apt-get -y install unzip \
    && apt-get -y install cifs-utils \    
    && apt-get -y install nfs-common nfs-kernel-server

# Install Azure CLI
RUN curl -sL https://aka.ms/InstallAzureCLIDeb | bash

# SMB ports
EXPOSE 137/udp 138/udp 139 445

RUN mkdir /mnt/myshare

If I run the container without --mount everything works fine.

If I however try this:

docker run -it myImage --mount type=volume,volume-driver=cloudstor:azure,source="myAzureShare",destination="/mnt/myShare" /bin/bash

I get this error:

docker.exe: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"--mount\": executable file not found in $PATH": unknown.

Do I need to install any CloudStor dependencies in the image? Are there any extra parameters I need to add when running the container?

Edit: this fixed the above error. But now it's as though Docker can't find the image when i use the --mount flag:

docker.exe: Error response from daemon: pull access denied for myImage, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.

If I don't use --mount the image loads fine

azure
Martin Hope
Geordie
Asked: 2019-08-23 07:18:32 +0800 CST
  • 1

I have a blob container in a storage account where each blob is an image. I've added "w" and "h" metadata fields to each blob containing the width and height of the image.

I've followed the instructions here to add a search service to the blob store except I added the metadata and not the blob content.

I can confirm the metadata is there and valid, if I browse the blobs in the Azure portal I can see the fields with valid data and if I execute "search=*" in the search explorer I get this back for each blob:

{
            "@search.score": 1,
            "w": 640,
            "h": 424,
            "metadata_storage_path": "......"
}

My problem is I want to search by image width(w) and height(h) and can't workout how.

Tried these example queries to search for w=640 with no luck, just returns all blobs or errors:

w=640
search=*&w=640
search=*&w eq 640
w eq 640

One thing I've noticed is that when writing the blob metadata (I used the Azure storage Python library) you can only write string data. But when you specifiy the fields in the data source can set them as int32.

How do I enable filterable searching over blob metadata fields?

Edit: As per SumanthMarigowda-MSFT's answer, I looked a this doc, and in my case here are some example queries:

Only 640x480:

search=*&$filter=(w eq 640 and h eq 480)

All with w betwen 640 and 700:

search=*&$filter=(w ge 640 and w lt 700)
azure