Recent blog posts

I haven’t done an update in a few weeks. Here are some of the blog posts from our community in the last few weeks.

Red Hat joins the DPDK Project by Marcos Garcia – Principal Technical Marketing Manager

Today, the DPDK community announced during the Open Networking Summit that they are moving the project to the Linux Foundation, and creating a new governance structure to enable companies to engage with the project, and pool resources to promote the DPDK community. As a long-time contributor to DPDK, Red Hat is proud to be a founding Gold member of the new DPDK Project initiative under the Linux Foundation.

Read more at http://redhatstackblog.redhat.com/2017/04/06/red-hat-joins-the-dpdk-project/

What’s new in OpenStack Ocata by rbowen

OpenStack Ocata has now been out for a little over a month – https://releases.openstack.org/ – and we’re about to see the first milestone of the Pike release. Past cycles show that now’s about the time when people start looking at the new release to see if they should consider moving to it. So here’s a quick overview of what’s new in this release.

Read more at http://drbacchus.com/whats-new-in-openstack-ocata/

Steve Hardy: OpenStack TripleO in Ocata, from the OpenStack PTG in Atlanta by Rich Bowen

Steve Hardy talks about TripleO in the Ocata release, at the Openstack PTG in Atlanta.

Read more at http://rdoproject.org/blog/2017/04/steve-hardy-openstack-tripido-in-ocata-from-the-openstack-ptg-in-atlanta/

Using a standalone Nodepool service to manage cloud instances by tristanC

Nodepool is a service used by the OpenStack CI team to deploy and manage a pool of devstack images on a cloud server for use in OpenStack project testing.

Read more at http://rdoproject.org/blog/2017/03/standalone-nodepool/

Red Hat Summit 2017 – Planning your OpenStack labs by Eric D. Schabell

This year in Boston, MA you can attend the Red Hat Summit 2017, the event to get your updates on open source technologies and meet with all the experts you follow throughout the year.

Read more at http://redhatstackblog.redhat.com/2017/04/04/red-hat-summit-2017-planning-your-openstack-labs/

Stephen Finucane – OpenStack Nova – What’s new in Ocata by Rich Bowen

At the OpenStack PTG in February, Stephen Finucane speaks about what’s new in Nova in the Ocata release of OpenStack.

Read more at http://rdoproject.org/blog/2017/03/stephen-finucane-openstack-nova-whats-new-in-ocata/

Zane Bitter – OpenStack Heat, OpenStack PTG, Atlanta by Rich Bowen

At the OpenStack PTG last month, Zane Bitter speaks about his work on OpenStack Heat in the Ocata cycle, and what comes next.

Read more at http://rdoproject.org/blog/2017/03/zane-bitter-openstack-heat-openstack-ptg-atlanta/

The journey of a new OpenStack service in RDO by amoralej

When new contributors join RDO, they ask for recommendations about how to add new services and help RDO users to adopt it. This post is not a official policy document nor a detailed description about how to carry out some activities, but provides some high level recommendations to newcomers based on what I have learned and observed in the last year working in RDO.

Read more at http://rdoproject.org/blog/2017/03/the-journey-of-a-service-in-rdo/

InfraRed: Deploying and Testing Openstack just made easier! by bregman

Deploying and testing OpenStack is very easy. If you read the headline and your eyebrows raised, you are at the right place. I believe that most of us, who experienced at least one deployment of OpenStack, will agree that deploying OpenStack can be a quite frustrating experience. It doesn’t matter if you are using it for […]

Read more at http://abregman.com/2017/03/20/infrared-deploying-and-testing-openstack-just-made-easier/
Quelle: RDO

Global customer access and additional services now available for Azure in India

Since the launch of the Microsoft Cloud in India, we have seen tremendous growth of our customers’ cloud usage. For example, we’re collaborating with Tata Motors, India’s leading auto manufacturer, to provide connected driving experiences powered by Azure. Flipkart has adopted Azure as its exclusive public cloud platform to enable its continued growth and expansion, and to scale quickly and stay resilient. Kotak Mahindra Bank partnered with Zing HR and turned to Azure for an integrated and flexible mobile HR solution.

Today, I’m excited to share that global companies can now benefit from access to the three Azure regions in India: West India (Mumbai), Central India (Pune) and South India (Chennai). These regions provide world-class reliability and performance combined with data residency in India to support the digital transformation of organizations. Customers gain the benefit of data replication across these locations, ensuring business continuity in both pure cloud and hybrid scenarios.

Selected noteworthy services deployed in India regions since my last update include Power BI and HDInsight, with full features across Windows and Linux. Power BI is a suite of business analytics tools to analyze data and share insights to monitor a business and get answers quickly with rich dashboards available on every device. With HDInsight, you can easily spin up enterprise-grade, open source cluster types, guaranteed with the industry’s best 99.9% SLA and 24/7 support.

I’m proud about these expansions, and to see Azure in India enabling our users to deploy dev, test and production workloads closest to their employees, partners and customers anywhere in the world.
Quelle: Azure

Paygilant prevents mobile wallet fraud with IBM Cloud technology

People around the world do almost everything with their mobile devices. Paying for purchases with them is just another use case that makes sense.
That’s why the issuers — banks, financial markets, communications service providers and mobile wallet providers — as well as merchants  want to be part of this trend. They’re developing and promoting their mobile wallets to the market and appealing to their channels and installed customer bases, which increases mobile wallet use. It’s just a matter of time before plastic cards will be replaced entirely by mobile wallets.
Authentication slowing things down
The promise of the mobile wallet is convenience, but what usually happens is customers are forced to authenticate almost every purchase regardless of the associated risk, so it really isn’t convenient after all.
Say someone in a coffee shop just wants to grab a coffee and go. Typically, that person is on the way to the office and it’s a hassle to be delayed with the need to authenticate using a pincode, fingerprint or some other type of authentication required by the mobile wallet provider.
In most cases, it’s not necessary and doesn’t make much sense. For example, if someone buys the same coffee at roughly the same time at the same location every day, then the likelihood of that transaction being fraudulent on any given day is close to zero. Authentication in this scenario just causes friction.
Need for increased security
Today, fraud is growing by flying under the radar because of a new trend. To avoid hassle, mobile wallet issuers now allow customers to buy up to a certain amount without any authentication. For amounts up to $100 in the US and Canada or up to €50 in Europe or up to £20 in the UK, for example, users don’t need to authenticate.
This situation poses an even bigger risk because the only thing a fraudster needs to do is steal someone’s phone, go to a merchant and buy things using that device. By the time the fraud is detected, the money is already gone. This is easily feasible, as more than half of mobile users don’t lock their phones and up to 40 percent of robberies in major cities involve cell phones.
Eliminating friction and fraud
This fraud trend is what triggered Paygilant Ltd. to develop a solution that would address how to eliminate both friction and fraud.
A portmanteau of “payment” and “vigilant,” the name Paygilant says in a word what the company does: detects fraud at the point of payment with an innovative mobile wallet solution. Paygilant was founded in 2014 to eliminate both the authentication friction that occurs when someone on the go uses a smartphone for a quick, routine purchase and the fraud that occurs when someone uses a stolen identity or device, especially with smaller purchases that are not authenticated.
Vision leading to innovation
Paygilant had a transformational vision for the mobile wallet space. To make it a reality, we needed to team with a provider that could help us design and build our solution architecture. We evaluated different options and decided to apply to the IBM Alpha Zone accelerator program, which is an intensive, 20-week program for startups to develop solutions with onsite support, mentoring and technical training. Paygilant engineers worked closely with the Alpha Zone team to create a highly scalable architecture comprising various IBM products and services.
Developing the mobile wallet solution
We developed a product based on an innovative technology which relocates the traditional fraud detection process from the back end to the mobile device. We now have a unique behavioral map of each customer, reflecting individual activities and spending habits, enabling the most accurate detection rate. The map is updated every two to three days, and it tracks customer activity from all channels, regardless of whether the transaction involves a plastic card or a mobile device.
In real time, before a transaction is even completed, we can detect on the device whether the transaction is made by the customer or whether it’s suspicious. In a majority of cases, we eliminate the need to authenticate because the detection rate is extremely high, three times higher than any traditional fraud-detection system. At a coffee shop, customers simply tap their phone, take their coffee and they’re on the way to the office. There’s no need for them to do anything else, without compromising on risk.
Only roughly 10 percent of transactions trigger authentication that requires the Paygilant solution to validate identity. If it’s the authorized user, that person will pass successfully. If it’s a fraudster, then the authentication will fail and fraud will be prevented. Paygilant’s role is to identify the suspicious activity or transaction and let the wallet provider know that there is something suspicious going on. What action to take next is up to the wallet provider.
Building on cognitive and cloud data services
Paygilant can work as a cloud-based or on-premises solution. The cloud option runs on IBM technology. The on-premises version is for financial institutions that aren’t comfortable sending data outside their own networks. The registration process includes IBM Watson Natural Language Classifier technology, which makes sure people registering are really who they say they are.
IBM Watson technology helps build a customer profile based on information from different public data sources, including social media information, and matches it against the registration details.
Delivering on the promise
Paygilant decreases both the need for authentication and the occurrence of fraud, which means savings for banks and mobile wallet providers. Typically, customers significantly reduce payment authentication with Paygilant than with other systems. Banks and mobile wallet providers can cut operating expenses for fraud detection by up to 60 percent because call center workload is reduced, as well as the cost of fraud itself.
Users don’t even realize that the Paygilant solution is backing up the mobile wallet app they’re using. It works in the background. The solution makes possible the frictionless shopping experience customers expect with mobile wallets.
Read the case study to learn more.
The post Paygilant prevents mobile wallet fraud with IBM Cloud technology appeared first on news.
Quelle: Thoughts on Cloud