Retailer concerns, opportunities for Black Friday/Cyber Monday: New research

The shelves are stocked, the ads are running, and retail executives everywhere are readying their stores and systems for the long-awaited start of holiday shopping–Black Friday and Cyber Monday, the busiest time in retail.  As the former CMO and chief digital officer at Neiman Marcus Group, and now Google Cloud’s head of retail, I know firsthand how these two single days can affect revenue, growth, and brand loyalty. For retailers that perform well, Black Friday and Cyber Monday can bring in millions of dollars and thousands of new customers. But for those who don’t, let’s just say that consumers (and shareholders) have long memories. Black Friday and Cyber Monday are truly the Super Bowl or World Cup of retail. Retailers spend 10 months conditioning their teams and systems to handle the pressures of the big event, because that’s when the stakes are highest, and all eyes are on them. These two iconic shopping days have expanded far beyond their original 24-hour period, with many retailers pushing out promotions the entire week of Thanksgiving—and some the entire month of November. With longer campaigns comes even more uncertainty around when shopping “peaks” are expected to hit. Retailers must be ready to scale at any moment, since product popularity and viral success could happen at any time.At Google Cloud, we recently commissioned The Harris Poll to survey more than 200 U.S. retail executives, gauging their expectations for this year’s holiday shopping season and what they’re doing to prepare. Here are the top trends we discovered.1. Retailers are predicting even more digital sales Retailers have been seeing sales move from in-store to online for many years, and this year the trend continues. Survey respondents expect digital sales to account for about half of their overall sales this holiday weekend, with 26% coming from their websites and 22% coming from their apps. This is higher than the regular season store vs. online mix for most retailers, proving that consumers like to do their last-minute holiday shopping online. Nearly half (46%) of the retail executives in our survey anticipate that online traffic this Black Friday and Cyber Monday will be significantly higher this year compared to last. In particular, shoppers are taking to mobile even more for product discovery, especially as they shop in-store. In the past two years, mobile searches for “best deals” have grown more than 90% and searches around “rewards apps” and “Black Friday deals” are up 200%, according to recent Google data. This rise in online traffic also echoes data from the National Retail Federation, which predicts holiday retail sales this year are set to increase between 3.8 and 4.2%, and online sales to increase between 11 and 14%, as compared to 2018. As digital sales become a bigger part of overall sales, retailers will increasingly use traffic growth and website performance as a gauge of success. In fact, when survey respondents were asked how they’ll measure Black Friday and Cyber Monday outcomes, 55% pointed to traffic growth–just below the traditional sales volume metric (60%) and just above customer satisfaction (54%).2. Retailers are working to minimize the impact of website downtimeWith the stakes so high, it’s not surprising that retailers are spending time preparing their staff, stores, and infrastructure for peak demand. More than 4 in 5 (81%) of survey respondents say they take special measures to prepare for Black Friday and/or Cyber Monday, and a big part of these preparations is making sure their tech infrastructure is ready to display, process, and fulfill customer orders.There are many different touch points in a customer’s experience with a retailer, but it often starts or ends with a company’s website. Whether that customer is using the site to view a promotion, shop for ideas, place an order, or check the status of an order, this experience is a make-or-break moment. A June Retail Systems Research report, sponsored by Google, illuminated the impact that a slow or unavailable website can have on customer loyalty. When asked “Have you ever left a website because it’s too slow?” 91% of respondents said they had—and 30% of shoppers said they would think twice before using that retailer again. A website that crashes or stalls is a problem anytime of year, but it’s particularly challenging during Black Friday and Cyber Monday, when traffic surges and competition for consumer dollars is at an all-time high. From the Harris Poll survey, one in ten retail executives (10%) reported that their company’s website experienced an outage during Black Friday/Cyber Monday last year, and 40% said they experienced an outage within the past three years. That’s a lot of lost revenue—and potential negative impact to brand perception. This year, retailers expect even higher volumes of traffic. Survey respondents expect to see a 38% surge, on average, during Black Friday and Cyber Monday compared to their company’s normal online traffic.3. Retailers are prepared, but not fully confidentRetailers understand the stakes and have been preparing for Black Friday and Cyber Monday in many ways, from increasing their cloud capacity (66% of respondents), offering additional fulfillment options (61%), or spacing out offers and promotions to balance traffic (53%). Nearly nine in ten respondents (86%) said their company has a clear system that maps each process or system with its potential to degrade website performance.All this preparation has given respondents a certain level of confidence in their ability to perform during the holidays. However, many are still not fully confident and express areas of concern:Only half (52%) of respondents said they were very confident in their company’s overall peak readiness.Less than half said they were very confident in their website speed (42%) and scalability (45%) going into Black Friday and Cyber Monday. More than 80% said they were at least somewhat concerned about the efficacy of their supply chain during Black Friday and Cyber Monday, with two in five (44%) saying they were very concerned.These responses aren’t particularly surprising. With so many different channels to cover, and so many different failure points to consider, it would be surprising if anyone was completely confident. But what is surprising is that nearly a quarter of respondents (24%) do not have a plan in place should their website go down during this time. Being fully prepared means having a game plan for when things go wrong.At Google Cloud, we’ve worked with some of the biggest retailers in the business to make sure they’re ready to perform during the big event. For many, that means early capacity planning, identifying potential reliability issues early on, and working side-by-side with their IT and engineering teams in a war room during game day, just in case something does go wrong. We’ve seen a big increase in cloud consumption with our top retailers year-over-year, as well as significant growth in the number of retailers utilizing our white-glove services offering. This kind of partnership and prep work can be the difference between stellar sales numbers or creating an event that damages a retailer’s brand for years to come. Find more information on Google Cloud for retail.Research Method The survey was conducted online within the United States by The Harris Poll on behalf of Google from October 14-29, 2019, among 203 retail executives aged 21 years or older, employed full-time, part-time, or self-employed full-time, who work in the retail industry with a title of director level or higher, specifically with a role in IT, operations and production, strategy and business development, inventory management, supply chain, or ecommerce at companies with at least $5 million in annual revenue. The data are not weighted, and therefore are only representative of the individuals surveyed.
Quelle: Google Cloud Platform

It’s a wrap: Key announcements from Next ‘19 UK

Next UK brought together more than 7,000 attendees to take part in discussions, breakout sessions, hands-on training and networking with industry leaders. And along the way there were a wide range of Google Cloud announcements and updates. Although a trip to London might not have been on everyone’s agenda, a trip through the week’s announcements is no further than this post. Read on for some of the highlights. Migrating, modernizing and managing infrastructureInfrastructure is the foundation of your IT environment—and Google Cloud. Earlier this year, we announced new general purpose and workload-optimized virtual machine families, which means you can migrate and run even more applications including AAA gaming, HPC and even SAP HANA. Building on our compute momentum, we recently made a number of announcements to help you take advantage of our robust network infrastructure, faster and more efficiently.  In the weeks leading up to Next UK, we announced major new networking functionality. Support for Bring Your Own IP (BYOIP) allows you to accelerate your cloud migration by carrying over your existing IP addresses to Google’s network infrastructure across all our 20 regions—we are the first cloud provider to make this feature globally available. Then, the new Network Intelligence Center provides comprehensive visibility into your global Google Cloud deployment, and lets you proactively manage your network operations, cutting down troubleshooting time and helping prevent network outages.We also want to make sure that both operators and developers are able to easily monitor their infrastructure and services and identify incidents as quickly as possible. At Next UK, we announced that Stackdriver Monitoring is moving into the Google Cloud Console (beta), allowing users to access all operations management tools in one place for a faster, easier, and more integrated experience. And with Stackdriver Logging’s new Log Router, also in beta, we provide operators with the flexibility and reliability they need to manage and route their logs; Logs Router also supports customer managed encryption keys (CMEK) for your security needs. Finally, with the launch of SLO Service API in beta, we are empowering operators on Google Cloud or on-prem to focus on a set of service health signals that reflects the end-customer experience. SLOs can be set on container or VMs environments, giving developers and operators end-to-end visibility of the health of their entire fleet of microservices, in a single place.And for specialized workloads that you aren’t ready to move to the cloud yet, we now offer via partners Bare Metal Solution, dedicated infrastructure on which you can run applications like Oracle Database that’s connected via a low-latency and highly resilient interconnect to Google Cloud.Accelerating app modernizationYou don’t just want to move your applications to the cloud; you want to modernize them too, much the way that new customers such as Kaeser Kompressoren SE and DenizBank are doing with Anthos.  To help you get there, Migrate for Anthos is now generally available, allowing you to convert physical servers or virtual machines from a variety of sources (on-prem, Amazon AWS, Microsoft Azure, or Google Compute Engine) directly into containers running in Anthos or Google Kubernetes Engine (GKE). Or perhaps you want to connect applications via APIs. Apigee hybrid is now generally available, letting you deploy your API runtimes in a hybrid environment—both on-prem or in Google Cloud, including Anthos.We’re also helping you modernize your software development processes. We announced the general availability of both Cloud Run and Cloud Run for Anthos last week, bringing the benefits of serverless to container-based applications. And building Kubernetes applications is now easier than ever, with the general availability of Cloud Code, which integrates directly into your IDE, so you can create cloud-native apps from the comfort of your favorite development environment.   Unlocking data insightsCapturing and managing the data you need is essential to build an analytics foundation. We’ve made it easier with a few new tools.This week we announced the general availability of Cloud Data Fusion, a managed, cloud-native data ingestion and integration service. It equips developers, data engineers and business analysts to easily build and manage ETL and ELT pipelines to cleanse, transform and blend data from a broad range of sources. Data Fusion shifts an organization’s focus away from code and integration to insights and action. Built on the open source project CDAP, the product’s open core ensures portability for users across hybrid and multi-cloud environments. CDAP’s broad integration with on-prem and public cloud platforms gives Data Fusion users the ability to break down silos and deliver more value than ever through Google’s industry-leading big data tools.To make streaming analytics simpler and more cost-effective, we announced new features in Cloud Dataflow SQL, available in the public preview, as well as the general availability of Cloud Dataflow Flexible Resource Scheduling (FlexRS) for cost-effective batch event processing. Streaming analytics is an important part of modern data analytics, letting businesses better understand their customers in real time and make decisions accordingly. These new features make streaming analytics easier and more accessible to data engineers, particularly those with database experience. Cloud Dataflow SQL lets you use SQL queries to develop and run Cloud Dataflow jobs from the BigQuery web UI, and new features include Cloud Storage file support and a visual schema editor. The new Cloud Dataflow FlexRS feature reduces batch processing costs by up to 40% using advanced resourcescheduling techniques and a mix of different virtual machine (VM) types (including thepreemptible VM instances) to decrease processing costs while providing the same job completion guarantees as regular Cloud Dataflow jobs.Increasing interpretability with Explainable AIAI and machine learning are among the most transformative technologies of our era, and our aim is to put these tools in reach of more businesses, and do it in a way that’s fairer and more responsible. Our announcements at Next UK continue to further those goals.We announced Explainable AI to increase interpretability of AI and help developers understand how their machine learning models reached certain outcomes. Explainable AI consists of tools and frameworks to deploy interpretable and inclusive machine learning models. AI Explanations for AutoML Tables and Cloud AI Platform are available now and to start making your own AI deployments more understandable with Explainable AI, visit cloud.google.com/explainable-ai. You can also learn more by reading our AI blog post.Bringing more assistive features to the workplaceSpeaking of AI, we’re introducing new ways to help people create high-quality, error-free documents. We’re bringing the Smart Compose feature to Google Docs(beta), which uses AI to suggest complete sentences as you type. And now with the help of neural machine translation, Docs can help prevent even more spelling or grammatical errors in your work. Beyond helping folks create top-notch Docs, we announced that we’re expanding the power of the Google Assistant for G Suite users (beta). When people are logged into their G Suite account, they’ll soon be able to accomplish more on the go, like using voice commands to manage their calendar, send quick messages, or dial into meetings.Read more about how you can start using assistive features in Docs or expanded functionality of the Google Assistant in this post.Advancing control and visibility in the cloudCloud security depends on a strong foundation. In the weeks leading up to Next UK, we, along with our partners, announced OpenTitan—the first open source silicon root of trust (RoT) project that provides RoT design and integration guidelines for use in data center servers, storage, peripherals, and more. Open sourcing silicon design makes it more transparent, trustworthy, and ultimately, secure.Building on a secure-by-design foundation, we announced multiple capabilities to help customers increase control and visibility over their data and secure their cloud environments: External Key Manager, Key Access Justifications, Cloud Armor WAF, Packet Mirroring,andAdvanced Protection Program for G Suite users. In addition, we announced technical capabilities in Google Cloud that our European customers can use to meet their preferences for additional data residency, operational control, and access control.Looking aheadWe’re grateful for the chance to spend two full days learning from our customers, collaborators and partners in EMEA this week, and hearing so many amazing stories. And while all good things must come to an end, we have Next ’20 to look forward to—April 6-8 in San Francisco. We hope to see you there.To learn more, visit g.co/cloudnext.
Quelle: Google Cloud Platform

Is it too late to integrate GitOps?

Author: Ryan Cook (rcook@redhat.com)
Is it too late to integrate GitOps?
By: Ryan Cook
The idiom “missed the boat” can be used to describe the loss of an opportunity or a chance to do something. With OpenShift, the excitement to use this new and cool product immediately may create your own “missed the boat” moment in regards to managing and maintaining deployments, routes, and other OpenShift objects but what if the opportunity isn’t completely gone?
Continuing with our series on GitOps (LINK), the following article will walk through the process of migrating an application and its resources that were created manually to a process in which a GitOps tool manages the assets. To help us understand the process we will manually deploy a httpd application. Using the steps below we will create a namespace, deployment, and service and expose the service which will create a route.
oc create -f https://raw.githubusercontent.com/openshift/federation-dev/master/labs/lab-4-assets/namespace.yaml
oc create -f https://raw.githubusercontent.com/openshift/federation-dev/master/labs/lab-4-assets/deployment.yaml
oc create -f https://raw.githubusercontent.com/openshift/federation-dev/master/labs/lab-4-assets/service.yaml
oc expose svc/httpd -n simple-app

We start with our sample application managed manually, then bring it under GitOps control in a way which ensures the application remains available.

Define a repository for the code
Export our current objects and load into git
Select and deploy a GitOps tool
Add the repository to our GitOps tool
Define the application in our GitOps tool
Perform a dry run of the object using the GitOps tool
Perform sync of the objects using the GitOps tool
Enable pruning and auto-syncing of the objects

As we have stated in the previous articles(LINK), when using GitOps the git repository is the source of truth for all of your objects within your Kubernetes cluster(s). We will assume that a git repository service is currently being used within your organization. This git repository can be public or private but the repository must be accessible by the Kubernetes clusters. The repository can be the same one as where the application code exists or a separate repository can be used specifically for deployments. It is suggested that the repository has strict permissions as secrets, routes, and other objects need to be stored.
For this exercise a new public repository can be created on GitHub. The repository can be named whatever you like but for this example we will use the name blogpost for our repository.
If the YAML files for the objects have not previously been stored in git or locally then oc or kubectl binary can help us out. Below we will request the YAML for our namespace, deployment, service, and route. Clone the newly created repository and cd into the directory.
oc get namespace simple-app -o yaml –export > namespace.yaml
oc get deployment httpd -o yaml -n simple-app –export > deployment.yaml
oc get service httpd -o yaml -n simple-app –export > service.yaml
oc get route httpd -o yaml -n simple-app –export > route.yaml

Make the following modification to the deployment.yaml to remove a field in which Argo CD cannot sync properly.
sed -i ‘/sgeneration: .*/d’ deployment.yaml

We also must modify the route. We will first set a multiline variable and then we will replace ingress: null with the contents of the variable.
export ROUTE=” ingress:
– conditions:
– status: ‘True’
type: Admitted”

sed -i “s/ ingress: null/$ROUTE/g” route.yaml

Once we have these files it is time to save them into the git repository. From this point forward, the repository should be the source of truth for anything and manual changes to any of the objects should be prohibited.
git commit -am ‘initial commit of objects’
git push origin master

We will assume that ArgoCD has already been deployed based on this blog post (LINK). So we will add the newly created repository to Argo CD that contains the simple-app code. Ensure that the repository below matches the one that was created in previous steps.
argocd repo add https://github.com/cooktheryan/blogpost

Next, create the app. The app defines the values for the GitOps tool to know the repository and path to use, the OpenShift cluster to manage the objects, the specific branch of the repository, and whether to sync assets automatically or not.
argocd app create –project default
–name simple-app –repo https://github.com/cooktheryan/blogpost.git
–path . –dest-server https://kubernetes.default.svc
–dest-namespace simple-app –revision master –sync-policy none

Once the application has been defined in Argo CD the tool will begin to verify the current objects deployed objects versus those defined in the repository. We have the sync policy currently disabled and pruning is not enabled so no items should be changed at this point. One thing that you will notice is that the application within Argo CD UI will be stated as “Out of Sync” this is due to a missing label that ArgoCD supplies. This label will not cause any assets to be redeployed when we run the sync.
Now let’s run a dry run to ensure no errors exist within our files.
argocd app sync simple-app –dry-run

If no errors show up during the dry run we can move forward with the sync.
argocd app sync simple-app

When running the command argocd get on our simple-app application we should see that the application is “Healthy” and “Synced”. This means that all of the resources in our git repository now match those that are deployed.
argocd app get simple-app
Name: simple-app
Project: default
Server: https://kubernetes.default.svc
Namespace: simple-app
URL: https://argocd-server-route-argocd.apps.example.com/applications/simple-app
Repo: https://github.com/cooktheryan/blogpost.git
Target: master
Path: .
Sync Policy: <none>
Sync Status: Synced to master (60e1678)
Health Status: Healthy
…

At this point we can enable “auto-sync” and “pruning” to ensure that nothing in manually created and that any time an object is updated and pushed to the repository it will be deployed.
argocd app set simple-app –sync-policy automated –auto-prune

Now you have successfully migrated an application that did not initially use GitOps to a GitOps managed application.
The post Is it too late to integrate GitOps? appeared first on Red Hat OpenShift Blog.
Quelle: OpenShift