High Availability for Bluemix Secure Gateway Docker Client - docker

Architecting a solution on Bluemix that will use the Secure Gateway service to connect to on-premise resources.
Trying to understand how to approach achieving a production high availability configuration for the Secure Gateway Client which runs inside a Docker contained provided by Bluemix.
How are others approaching HA for the SG Client?

Docker does support an auto-start functionality, but there is no built in support within Secure Gateway currently to take advantage of that. Our next release (1.3.0) will support native installers for Linux (Ubuntu, RHEL and SLES), which will be out last week this month. Once out, you could use the native installer, setup the auto-start facility and control your client using native upstart or systemD capabilities.

Related

Is it possible to do development of Dapr based applications without using Docker Desktop?

Based on the documentation for Dapr mentioned at :https://learn.microsoft.com/en-us/dotnet/architecture/dapr-for-net-developers/getting-started . It looks like Docker Desktop is mandatory perquisite as part of Dapr setup in local environment.
The Docker company recently announced that it would be making changes in its Docker Desktop subscription terms. With this update it is not possible to install Docker Desktop in the local development environment. Can anyone help me to know how to continue Dapr based application development without Docker Desktop in this case.
Can anyone help me here by providing their guidance?

What is the difference between Flask and Docker?

I am lost in these words. Watched a lot of videos and articles. But I am not able to understand the difference. Flask helps me to create web interface which can be used only on my local system. But what does docker do? Does it make the application visible to world with url? Requesting answer in very simple words..
Flask is a web framework in that it provides an API for the python language with which web applications can be built, such as a website or a backend service.
Docker is a containerization tool which deals with the deployment of applications and the environment in which they run. Docker provides a lightweight alternative to Virtual Machines - a lightweight software environment in which an application can run independently, with dependencies handled by Docker. Docker environments can vary in operating system, the programming language of the application being deployed, and more.
I may, for example, build a web application in python using libraries provided by the flask API, then deploy the application on a server in a docker environment running a Windows Operating system.

Which AMI to Select (Sever 2016 Base or Server 2016 Base with Containers)

I am creating a new EC2 instance in AWS. As I am new to this, i am confused with the AMI.
Current Usage:
General Purpose web server
Hosting Web API (.net 4.6.2)
Future Needs
Need to support .net core as I am planning to migrate the Web API to core
Planning to integrate CI/CD with AWS Code pipeline
Environment Selected
Instace Type : m5 large
When i check AMI t select i have 2 options:
Microsoft Windows Server 2016 Base (I think 2016 is enough)
Microsoft Windows Server 2016 Base with Containers
I am confused here. I understood that later have docker containers. But i didn't get the advantage on that in the server. I am planning to learn docker. But as of now, i need your quick help to continue. As i specified, the application may need docker for the build server while configure with Code pipeline.
Please suggest the best option and the needs of that added feature
If you are interested in Docker and plan to run Docker on ECS then you should choose ECS-Optimized Windows Server Amazon Machine Image.
As far you Future Needs it does not depend on AMI but you container do depend on AMI.
This week, we’re adding support for running production workloads
in Windows containers using Amazon Elastic Container Service (Amazon
ECS). Now, Amazon ECS provides an ECS-Optimized Windows Server Amazon
Machine Image (AMI). This AMI is based on the EC2 Windows Server 2016
AMI, and includes Docker 17.06 Enterprise Edition and the ECS Agent
1.16. This AMI provides improved instance and container launch time performance. It’s based on Windows Server 2016 Datacenter and includes
Docker 17.06.2-ee-5, along with a new version of the ECS agent that
now runs as a native Windows service.
This will help to maintain your ECS services in future also have some advantage over Microsoft Windows Server 2016 Base with out ECS optimized.
The ECS agent ran as a process that made it difficult to monitor and manage. As a service, the agent can be health-checked, managed, and restarted no differently than other Windows services.
The AMI also includes pre-cached images for Windows Server Core 2016 and Windows Server Nano Server 2016. By caching the images in the AMI, launching new Windows containers is significantly faster
The Windows-compatible ECS-optimized AMI also reports CPU and memory utilization and reservation metrics to Amazon CloudWatch.
You can explore more about here

Can I run any docker container in Microsoft Iot Edge?

IoT Edge from Microsoft uses docker for managing modules.
Is it possible to run any docker container on a IoT Edge device?
Yes, you can run any kind of docker-based container on IoT Edge as long as the image supports the architecture your Edge device uses (amd64, arm32, etc.) The container does not have to be aware of IoT Edge or even talk to the runtime. In this case the Edge runtime will simply make sure the container is up and running according to your settings.
Azure IoT Edge modules are implemented as containers, so IoT Edge needs a container engine to launch them. Microsoft provides a container engine, moby-engine, to fulfill this requirement. This container engine is based on the Moby open-source project. Docker CE and Docker EE are other popular container engines. They're also based on the Moby open-source project and are compatible with Azure IoT Edge. Microsoft provides best effort support for systems using those container engines; however, Microsoft can't ship fixes for issues in them. For this reason, Microsoft recommends using moby-engine on production systems.
Please refer Azure IoT Edge supported systems for more details.
Also see How to install IoT Edge on Kubernetes (Preview)
Hope this helps.

OpenCV deployment on windows azure

Is it possible to deploy an OpenCV application to windows azure?
Open CV is comes into client application category accessible through user interface and also can be used for backend processing. Windows Azure Cloud services is used for web application so Open CV does not fit in the application model. For backend processing you may think to use cloud service as worker but that need lots of work on your part and defeat the purpose.
For the sake of completeness and possibility, you sure can get a Windows Azure Virtual Machine, along with Windows OS and deploy OpenCV application there. Once ready you can Remote Desktop to the VM and use it. You may pay monthly cost to use the VM but you sure can do it. But I am sure that is not your objective either.
Yes, I'll say its possible to install OpenCV applications to Azure.
Check the following Deep Learning VM
It comes with pre-installed software. Most of the machine learning libraries along with the OpenCV project are pre-installed
You can also use APIs to host your models on the Windows Azure

Resources