The Barcelona Supercomputing Center has launched the European Laboratory for Open Computer Architecture (LOCA), a five-year effort aimed at developing energy efficient, high performance computing chips based on open architectures. …
Europe Opens Second Front For Domestic HPC Processors was written by Michael Feldman at The Next Platform.
The variance in performance hasn't shaken Amazon's grip on the market. AWS remains the largest...
The increased interoperability testing will include Nokia’s virtual network functions and...
Service provider revenue dropped 13% year over year in Q1, while Cisco’s enterprise business...
The cloud giant is pitching the platform as a way to help customers find, subscribe to, and use...
A 5G SA core will allow operators to offer 5G-specific services, including network slicing, mobile...
By next year, five Internet of Things (IoT) devices are projected to be in use for every person on the planet.
IoT devices offer endless opportunities to improve productivity, economic growth, and quality of life. Think smart cities, self-driving cars, and the ways connected medical devices can monitor our health. The potential growth of IoT is virtually infinite.
But with opportunity comes a significant amount of risk. As much as we’d like to trust manufacturers to make sure burglars can’t watch our homes through data from an automated vacuum, many new devices lack even basic security features. And thousands of new devices are coming online each year without commitment to basic measures such as using unique passwords, encrypting our data, or updating software to address vulnerabilities.
To help people and businesses around the world prepare, a dedicated group is rising to the challenge of securing the Internet of Things though cooperation across borders and sectors.
They are government agencies, non-governmental organizations, and other organizations and experts working on IoT security joined together to form the IoT Security Policy Platform. We are proud to say the Internet Society is amongst them too. Together we’ve been discussing and sharing best practices and Continue reading
This week's IPv6 Buzz discusses getting IPv6 into enterprise wireless environments. We discuss what proper vendor support for v6 looks like, evaluate the impact of a lack of DHCPv6 support in Android, why running dual stack is more work than a clean cutover, and more. Our guest is Joe Neville, a technical consultant at HPE Aruba.
The post IPv6 Buzz 039: Bringing IPv6 Into Enterprise Wireless appeared first on Packet Pushers.

In the past, Ansible content such as roles, modules and plugins was usually consumed in two ways: the modules were part of the Ansible package, and roles could be found in Galaxy. However, as time went on the current method of content distribution had challenges with scale for both contributors and consumers of Ansible content. Dylan described this in a blog post worth reading.
Recent releases of Ansible started a journey towards better content management. In previous Ansible releases, each and every module was strictly tied to the release schedule of Ansible and community, customer, and partner feedback demonstrated that the release schedule of content needed to evolve. Ansible content collections allow our Ansible contributors to create specialized content without being tied to a specific release cycle of the Ansible product, making it easier to plan and deliver. For Ansible newcomers, the collections come “pre-packaged” with modules and playbooks around common use cases like networking and security, making it easier to get off the ground with Ansible. If you want to learn more about Ansible content collections, check out our series about collections!
The introduction of collections to the Ansible ecosystem solves a number of challenges for access to Continue reading

With the release of Red Hat Ansible Automation Platform, Ansible Content Collections are now fully supported. Ansible Content Collections, or collections, represent the new standard of distributing, maintaining and consuming automation. By combining multiple types of Ansible content (playbooks, roles, modules, and plugins), flexibility and scalability are greatly improved.
Everyone!
Traditionally, module creators have had to wait for their modules to be marked for inclusion in an upcoming Ansible release or had to add them to roles, which made consumption and management more difficult. By shipping modules within Ansible Content Collections along with pertinent roles and documentation, and removing the barrier to entry, creators are now able to move as fast as the demand for their creations. For a public cloud provider, this means new functionality of an existing service or a new service altogether, can be rolled out along with the ability to automate the new functionality.
For the automation consumer, this means that fresh content is continuously made available for consumption. Managing content in this manner also becomes easier as modules, plugins, roles, and docs are packaged and tagged with a collection version. Modules can be updated, renamed, improved upon; roles can be updated to Continue reading

In the past, Ansible content such as roles, modules and plugins was usually consumed in two ways: the modules were part of the Ansible package, and roles could be found in Galaxy. However, as time went on the current method of content distribution had challenges with scale for both contributors and consumers of Ansible content. Dylan described this in a blog post worth reading.
Recent releases of Ansible started a journey towards better content management. In previous Ansible releases, each and every module was strictly tied to the release schedule of Ansible and community, customer, and partner feedback demonstrated that the release schedule of content needed to evolve. Ansible content collections allow our Ansible contributors to create specialized content without being tied to a specific release cycle of the Ansible product, making it easier to plan and deliver. For Ansible newcomers, the collections come “pre-packaged” with modules and playbooks around common use cases like networking and security, making it easier to get off the ground with Ansible. If you want to learn more about Ansible content collections, check out our series about collections!
The introduction of collections to the Ansible ecosystem solves a number of challenges for access to Continue reading

With the upcoming release of the Red Hat Ansible Automation Platform there are now included Software as a Service (SaaS) offerings, one of which is Automation Analytics. This application provides a visual dashboard, health notifications and organization statistics for your Ansible Automation. Automation Analytics works across multiple Ansible Tower clusters allowing holistic analytics across your entire infrastructure.
When talking to the community and our customers, a question that often comes up is: “How do we measure success?”. Automation Analytics provides key data on Job Template usage, Ansible Module usage, organizational comparisons across your enterprise, and much more. This data can be used to assess usage, success criteria, and even charge backs between different groups. This blog post will outline how to get started with Automation Analytics and start collecting data right away.
There are some terms used in this blog post that may be unfamiliar Continue reading
DMVPN spokes can use either point-to-point GRE tunnels or multipoint GRE tunnel interface. Recently, I received a question regarding DMVPN.
In fact, the Reader asked me two questions: When is GRE used in network design? When is mGRE used in network design?
Answering the aforementioned questions are the basics that you must know if you are planning to design DMVPN network.
As you might have known, DMVPN is a hub, spoke type of topology. And the most useful, important functionality of DMVPN is that it provides excellent scalability by reducing the number of tunnel interfaces configured on the hub and spokes.
I mentioned the DMVPN phases in one of my articles. Because of that, I will not explain them here again. However, if you don’t understand the meaning of DMVPN phases, I would recommend that you peruse the article on DMVPN basics before reading this article.
Point-to-Point GRE interface is used, only in Phase 1, on the spokes.
In all the Phases, mGRE interface type is always used on the hubs.
In Phase 2 and Phase 3 of DMVPN implementation, spokes also use mGRE (not multicast GRE, but multipoint GRE) interface types.
Compared to the point-to-point GRE interface, mGRE provides Continue reading