Direct Link connection options for hybrid clouds

Companies are striving to implement more cost-effective IT environments using hybrid clouds that include both on-premises and off-premises resources. Direct Link on IBM SoftLayer, introduced in my previous blog post, helps IBM Cloud clients integrate their private, public and hybrid clouds with high performance, security-rich connections.
Here’s how Direct Link connects your IT resources.
Physical connectivity
Physical connectivity occurs through a dedicated fiber connection (one or 10 Gigabits per second) that links a customer’s service equipment and the network equipment in an IBM point of presence (PoP). The method of connection depends on the type of connection:

Direct Link NSP: Customers directly connecting their existing data centers to the IBM Cloud would terminate a telco-provided Ethernet, MPLS, DWDM or SONET connection into their service endpoint equipment within an IBM PoP, then run a fiber cross-connect from that equipment to the IBM patch panel. The panel connects to ports on the IBM cross-connect router (XCR) in the PoP, which routes traffic to an IBM data center and ultimately through IBM’s carrier-grade, private global IP network to its final destination. Customers are responsible for purchasing the physical fiber cross-connect.
Direct Link colocation: Customers with colocation facilities within the same building or campus as an existing IBM data center would terminate a redundant fiber connection into a cross-connect panel installed in the POD (server farm) where their compute resources are provisioned. Customers are responsible for purchasing the fiber cross connect from their colocated facility to the IBM data center patch panel, which can span different floors in the same building or different buildings.
Direct Link cloud exchange: Customers using an IBM-approved cloud exchange partner would terminate a telco WAN service into an IBM PoP (same as Direct Link NSP) and also into the cloud exchange partner’s software-defined network, creating secure point-to-multipoint virtual connections among their private networks, the cloud exchange and the IBM Cloud.

(See the Direct Link FAQ for more information.)

Network connectivity
Network connectivity is defined by routing policies for an organization’s IP address space. Public IP addresses are universally assigned and may be static (reserved for a particular network resource, such as a server) or dynamic (they change as resource demands change but come from an assigned public pool). Private IP addresses are used for internal traffic shielded from the public internet by network elements such as routers or firewalls. This makes it possible for the same IP address space to be used by multiple parties simultaneously without conflict.
IBM Direct Link has three network connectivity options:

Dual IP remote hosts: Customers add additional IP addresses (or reassign the IP addresses for existing on-premises, colocated or cloud exchange hosts) to include public IP address space assigned to the IBM Cloud. This allows IBM to securely route customer traffic between the customer’s private network and the IBM network.
Network address translation (NAT): Customers configure NAT on network elements acting as private network gateways (usually a router or firewall). This allows assigned public IP address space to be used on private networks without conflict, since public IPs are converted to private IPs (and vice versa) as they cross the NAT gateway. For customers with private IPs that conflict with IBM IPs, NAT can be provisioned in both directions (source and destination).
Bring-your-own IP (BYOIP): Customers bring their assigned public IP address space into the IBM private network. Customers must create generic routing encapsulation (GRE) or IP security (IPSec) tunnels between their on-premises or colocation network and the IBM network. They can then use any IP address space they choose on the private network, as long as there are no conflicts with IBM’s public or private address space, and then route traffic across the tunnel between networks.

These methods of connectivity contribute to providing the security and performance that hybrid clouds require in enterprise-scale IT environments.
To learn more about Direct Link and other features and technology available with IBM SoftLayer, check out our Cloud How-To webcast series.
The post Direct Link connection options for hybrid clouds appeared first on news.
Quelle: Thoughts on Cloud

Top 5 Docker Questions from Microsoft Ignite

Last week was busy for the team at Microsoft Ignite in Atlanta. With the exciting announcement about the next evolution of the Docker and Microsoft relationship, the availability of Docker for Windows Server 2016 workloads, the show floor, general session, keynotes, and breakout sessions were all abuzz about Docker for Windows. Whether you were attended or not we want to make sure you didn’t miss a thing, here are the key announcements at this year’s Microsoft Ignite:

Docker Doubles Container Market with Support for Windows Workloads
Availability of Docker For Windows Server 2016
Docker Commercially Supported Docker Engine available in Windows Server 2016

Cool @VisualStudio and @docker integration being demoed by @shanselman at auto creation of Dockerfiles & debug inside containers. pic.twitter.com/HVDHKmwRrL
— Marcus Robinson (@techdiction) September 26, 2016

Wow @Docker engine included with all Server 2016 deployments. MSIgnite
— Joe Kelly (@_JoeKelly_) September 26, 2016

 
Here our top 5 questions heard in the Docker booth:

What are containers?

While container technology had been around for more than a decade. However, as the leader in the containerization market, .Docker has made the technology usable and accessible to all developers and sysadmins. . Containers allow developers and IT Pros to package an application into a standardized unit for software development, making them highly portable and able to run across any operating system. Each container contains a complete filesystem with everything needed to run: code, runtime, system tools, system libraries –essentially,  anything that can be installed on a server. This guarantees that the software will always run the same, regardless of its environment, without having to make any changes to the underlying code. Docker containers were previously only available to the Linux community and with the announcement of Docker for Windows Server 2016, Docker containers are now available for Windows workloads addressing 98% of enterprise workloads.
 

How is this different than App-V Application Virtualization?

Those in the Windows OS world are familiar with Microsoft App-V or ThinApp and naturally there were questions about comparing them to Docker containers. Application virtualization is used to package a full application with the relevant OS libraries into a single executable. Docker is a set of tooling used to build server based applications.  A single application could be comprised of one or hundreds of containers connected together. App-V is used for desktop applications and are not designed for server based applications. The most common example is packaging browsers with extensions so they can access custom web apps.  Each App-V package can reside on a laptop with different extensions/plugins, etc. To learn more about Application Virtualization and Docker, read our blog: There’s Application Virtualization and There’s Docker
 

How do I get started with Docker for Windows Server?

Integrating Visual Studio Tools for Docker and Docker for Windows provides desktop development environments for building Dockerized Windows apps. Getting started is easy and we have the tools you need to get started in a few easy steps:

Pick your tool:

The latest Anniversary update for Windows 10 offers containerization support for the Windows 10 kernel.
To run Windows containers in production at scale, download a free evaluation version Windows Server 2016 and install it on bare metal or in a VM running on Hyper-V, VirtualBox or similar.

Install a Windows Docker Engine on your system with Docker for Windows public beta on your system.
Run your first Windows Container in just a few steps with the instructions listed on the “Getting Started with Docker for Windows” webpage.
Create your own Dockerfile with our Image2Docker tool, a Powershell module that points at a virtual hard disk image, scans for common Windows components and suggest a Dockerfile. Read the blog to learn more and get started.

For a complete list of instructions read our blog post &; Build And Run Your First Docker Windows Server Container & view Windows Server container base images and applications on Docker Hub from Microsoft.
 

How do I manage containers?

Docker Datacenter is the integrated container orchestration and management platform for IT Pros. Today Docker Datacenter is available on Azure to manage Linux application environments. With the availability of Windows Server 2016 and Docker Engine, we are planning for a beta in Q4 2016 of Docker Datacenter management for Windows Server based applications.  Sign up here to be notified of the beta.
 

Where can I learn more?

There are lots of great resources and sessions to help you learn more. Whether you attended the conference or watched online here’s a wrap up of the top five session from Microsoft Ignite:

General Session with Scott Guthrie, EVP Cloud and Enterprise at Microsoft and Daryll Fogal CTO at Tyco

 

Keynote: “Reinvent IT infrastructure for business agility” with Jason Zander, CVP Microsoft Azure and Ben Golub, CEO of Docker

 

Breakout sessions:

Walk the path to containerization – transforming workloads into containers
Accelerate application delivery with Docker Containers and Windows Server 2016
Dive into the new world of Windows Server and Hyper-V Containers

Top 5 Docker questions from MSIgnite &8211; Answers hereClick To Tweet

Resources

Learn more about Docker on Windows Server
Sign up to be notified of GA and the Docker Datacenter for Windows Beta
Register for a webinar: Docker for Windows Server
Learn more about the Docker and Microsoft partnership

The post Top 5 Docker Questions from Microsoft Ignite appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Fahrt im autonomen Bus: Im Rausch der Langsamkeit

Im Herzen der Niederlande pendeln seit über einem halben Jahr kleine Busse zwischen einer Universität und einer Bahnstation, ganz ohne Fahrer und voll autonom. Golem.de hat im Rahmen der GTC Europe eine Spritztour in einem Wepod-Bus gemacht – eine zukunftsträchtige, aber eher gemächliche Fahrt. Hinweis: Um sich diesen Artikel vorlesen zu lassen, klicken Sie auf den Player im Artikel. (Autonomes Fahren, Internet)
Quelle: Golem

3D-Elements: Kameras in der Umkleidekabine

Beim Anprobieren gleich die eigene Figur scannen: Das österreichische Unternehmen 3D-Elements hat einen 3D-Scanner für Menschen entwickelt. Das 3D-Modell soll unter anderem bei der Anprobe von online gekaufter Kleidung eingesetzt werden, die kommende Version des 3D-Scanners wird in die Umkleidekabine integriert. (Photokina 2016, Scanner)
Quelle: Golem