Presplay Cloud Tech*

Amazon to Acquire Health Care Company One Medical in $3.9 Billion Deal

Presplay — Sat, 30 Jul 2022 18:37:04 +0000

The acquisition signals Amazon’s continued foray into the healthcare market having bought PillPack in 2018 for $750 million, using the acquisition to launch its own online pharmacy years later. Amazon has also ramped up effort in its telehealth service Amazon Care, along with plans to develop at-home medical diagnostics.

The deal — one of its largest acquisitions ever — will give Amazon a physical network of health-care offices and providers, as well as access to technology the start-up has built to enable virtual doctor visits. It adds to the company’s existing health-care portfolio, which includes an online pharmacy and Amazon Care, a virtual and in-home urgent care service.

“There is an immense opportunity to make the health care experience more accessible, affordable and even enjoyable for patients, providers, and payers,” One Medical CEO Amir Dan Rubin said in a statement.

The deal is a sign of Amazon’s long-simmering health care ambitions. As the company has marched from one retail business to another — including books, CDs, electronics, dog food, diapers and clothes — it has had to look in less obvious spots to find opportunities that can provide meaningful expansion.

Machine Learning And Artificial Intelligence, Cloud Computing and 5G Will be the Most Important Technologies in 2022

Presplay — Thu, 18 Nov 2021 11:00:11 +0000

Artificial Intelligence and Machine Learning, Cloud Computing and 5G Will be the Most Important Technologies in 2022, Says New IEEE Study

Thu, November 18, 2021, 11:00 AM·7 min read

Chief information officers, chief technology officers and technology leaders globally surveyed on key technology trends, priorities and predictions for 2022 and beyond

PISCATAWAY, N.J., Nov. 18, 2021 /PRNewswire/ — IEEE, the world’s largest technical professional organization dedicated to advancing technology for humanity, today released the results of “The Impact of Technology in 2022 and Beyond: an IEEE Global Study,” a new survey of global technology leaders from the U.S., U.K., China, India and Brazil. The study, which included 350 chief technology officers, chief information officers and IT directors, covers the most important technologies in 2022, industries most impacted by technology in the year ahead, and technology trends through the next decade. To learn more about the study and the impact of technology in 2022 and beyond, visit https://transmitter.ieee.org/impact-of-technology-2022/.

The most important technologies, innovation, sustainability and the future

Which technologies will be the most important in 2022? Among total respondents, more than one in five (21%) say AI and machine learning, cloud computing (20%) and 5G (17%) will be the most important technologies next year. Because of the global pandemic, technology leaders surveyed said in 2021 they accelerated adoption of cloud computing (60%), AI and machine learning (51%), and 5G (46%), among others.

It’s not surprising, therefore, that 95% agree –– including 66% who strongly agree –– that AI will drive the majority of innovation across nearly every industry sector in the next 1-5 years.

When asked which of the following areas 5G will most benefit in the next year, technology leaders surveyed said:

telemedicine, including remote surgery and health record transmissions (24%)
remote learning and education (20%)
personal and professional day-to-day communications (15%)
entertainment, sports and live event streaming (14%)
manufacturing and assembly (13%)
transportation and traffic control (7%)
carbon footprint reduction and energy efficiency (5%)
farming and agriculture (2%)

As for industry sectors most impacted by technology in 2022, technology leaders surveyed cited manufacturing (25%), financial services (19%), healthcare (16%) and energy (13%). As compared to the beginning of 2021, 92% of respondents agree, including 60% who strongly agree, that implementing smart building technologies that benefit sustainability, decarbonization and energy savings has become a top priority for their organization.

Workplace technologies, Human Resources collaboration and COVID-19

As the impact of COVID-19 varies globally and hybrid work continues, technology leaders nearly universally agree (97% agree, including 69% who strongly agree) their team is working more closely than ever before with Human Resources leaders to implement workplace technologies and apps for office check-in, space usage data and analytics, COVID and health protocols, employee productivity, engagement and mental health.

Among challenges technology leaders see in 2022, maintaining strong cybersecurity for a hybrid workforce of remote and in-office workers is viewed by those surveyed as challenging by 83% of respondents (40% very, 43% somewhat) while managing return-to-office health and safety protocols, software, apps and data is seen as challenging by 73% of those surveyed (29% very, 44% somewhat). Determining what technologies are needed for their company in the post-pandemic future is anticipated to be challenging for 68% of technology leaders (29% very, 39% somewhat). Recruiting technologists and filling open tech positions in the year ahead is also seen as challenging by 73% of respondents.

Robots rise over the next decade

Looking ahead, 81% agree that in the next five years, one quarter of what they do will be enhanced by robots, and 77% agree that in the same time frame, robots will be deployed across their organization to enhance nearly every business function from sales and human resources to marketing and IT. A majority of respondents agree (78%) that in the next 10 years, half or more of what they do will be enhanced by robots. As for the deployments of robots that will most benefit humanity, according to the survey, those are manufacturing and assembly (33%), hospital and patient care (26%) and earth and space exploration (13%).

Connected devices continue to proliferate

As a result of the shift to hybrid work and the pandemic, more than half (51%) of technology leaders surveyed believe the number of devices connected to their businesses that they need to track and manage –– such as smartphones, tablets, sensors, robots, vehicles, drones, etc. –– increased as much as 1.5 times, while for 42% of those surveyed the number of devices increased in excess of 1.5 times.

However, the perspectives of technology leaders globally diverge when asked about managing even more connected devices in 2022. When asked if the number of devices connected to their company’s business will grow so significantly and rapidly in 2022 that it will be unmanageable, over half of technology leaders disagree (51%), but 49% agree. Those differences can also be seen across regions — 78% in India, 64% in Brazil and 63% in the U.S. agree device growth will be unmanageable, while a strong majority in China (87%) and just over half (52%) in the U.K disagree.

Cyber and physical security, preparedness and deployment of technologies

The cybersecurity concerns most likely to be in technology leaders’ top two are issues related to the mobile and hybrid workforce including employees using their own devices (39%) and cloud vulnerability (35%). Additional concerns include data center vulnerability (27%), a coordinated attack on their network (26%) and a ransomware attack (25%). Notably, 59% of all technology leaders surveyed currently use or in the next five years plan to use drones for security, surveillance or threat prevention as part of their business model. There are regional disparities though. Current drone use for security or plans to do so in the next five years are strongest in Brazil (78%), China (71%), India (60%) and the U.S. (52%) compared to only (32%) in the U.K. where 48% of respondents say they have no plans to use drones in their business.

An open-source distributed database that uses cryptography through a distributed ledger, blockchain enables trust among individuals and third parties. The four uses in the next year respondents were most likely to cite in their own top three most important uses for blockchain technology are:

Secure machine to machine interaction in the Internet of Things (IoT) (61%)
Shipment tracing and contactless digital transactions (51%)
Keeping health and medical records secure in the cloud (47%)
Securing connecting parties within a specified ecosystem (47%)

The vast majority of those surveyed (92%) believe that compared to a year ago, their company is better prepared to respond to a potentially catastrophic interruption such as a data breach or natural disaster. Of that majority, 65% strongly agree that COVID-19 accelerated their preparedness.

About the Survey

“The Impact of Technology in 2022 and Beyond: an IEEE Global Study” surveyed 350 CIOs, CTOs, IT directors and other technology leaders in the U.S., China, U.K., India and Brazil at organizations with more than 1,000 employees across multiple industry sectors including banking and financial services, consumer goods, education, electronics, engineering, energy, government, healthcare, insurance, retail, technology and telecommunications. The surveys were conducted October 8-20, 2021.

About IEEE

IEEE is the world’s largest technical professional organization dedicated to advancing technology for the benefit of humanity. Through its highly cited publications, conferences, technology standards, and professional and educational activities, IEEE is the trusted voice in a wide variety of areas ranging from aerospace systems, computers, and telecommunications to biomedical engineering, electric power, and consumer electronics. Learn more.

Best DevOps Monitoring Tools for 2021

Presplay — Tue, 10 Aug 2021 19:55:43 +0000

Development and operations (DevOps) is the merger of practices, tools and cultural philosophies that increases the ability of an enterprise to deliver applications and services more frequently while improving quality and being cost-effective. By evolving and enhancing products at a rapid pace, DevOps enables enterprises to compete proficiently in the market.

Enterprises that implement traditional infrastructure management and software development processes are likely to be left behind in today’s competitive market, as the modern software development lifecycle encompasses multiple, simultaneous stages of development and testing.

A unified team that performs development, testing, and operations functions is of the essence.

The benefits of DevOps include:

Faster innovation, market adoption and business efficiency.
Rapid delivery of releases.
Practices like continuous integration, continuous delivery and monitoring and logging ensure the reliability of deliverables.
Automation and consistency help you develop, operate and manage processes at scale.
A DevOps cultural model enables effective team building.
Retain control and preserve compliance by using configuration management techniques, fine-grained controls and automated compliance policies.

Table of Contents

What are Monitoring Tools in DevOps?

Given the high velocity of development, testing and operations in today’s application lifecycle, frequent code changes are commonplace.

DevOps monitoring tools provide a comprehensive view of a production environment in real-time, automation, and expanded management throughout the application lifecycle – from planning, development and testing to deployment and operations.

When it comes to application and service monitoring, visualizations, real-time streaming and historical replay are critical components. DevOps monitoring enables development teams to quickly and automatically respond to any ruination in the customer experience.

It enables teams to “shift left” to earlier development stages in order to curtail broken production changes. DevOps monitoring tools help teams manage complex development environments at scale while retaining control of the fast nature that is enabled by DevOps.

In this guide, we will dive into all you should know about the top DevOps monitoring tools.

Best DevOps Monitoring Tools

Here are the best DevOps monitoring tools:

SolarWinds AppOptics (Librato)
Sensu Go
Git (GitHub, GitLab and Bitbucket)
Red Hat Ansible Automation Platform
Microsoft Teams

SolarWinds AppOptics (Librato)

SolarWinds AppOptics is an application and infrastructure monitoring solution that offers a fully customizable metrics platform, distributed transaction tracing, host maps, and more than 150 cloud-ready integrations. With full-stack application performance monitoring (APM), you can visualize and troubleshoot application bottlenecks simply and quickly.

Key Differentiators

Infrastructure monitoring enables a 360-degree view of your enterprise infrastructure and provides advanced alerting in real time, host and container maps, and custom infrastructure dashboards.
The solution provides out-of-the-box support for a variety of frameworks and libraries, including Python, Java, Go, .NET, PHP, Scala and Node.js.
SolarWinds AppOptics automatically determines the root cause of application performance problems.
With distributed tracing, exception tracking and live code profiling, you can trace requests across processes, hosts and data centers.
You can introduce any metric into SolarWinds AppOptics and display them along with infrastructure and application metrics.
With multi-dimensional tags, you can filter and group data with ease.
With over 150+ turnkey, cloud-ready integrations, you can obtain data straight from the source. These include AWS and Azure services, Docker, Kubernetes, etc.
You can try SolarWinds AppOptics free of cost for 30 days. The infrastructure and application monitoring package costs $24.99 per host, per month.

Sensu Go

Sensu Go is a turnkey, end-to-end observability pipeline that enables you to collect, filter, and transform monitoring events and send them to a database of choice. The solution delivers monitoring as code on any cloud, helps eliminate data silos, automates service delivery, reduces alert fatigue and enables automation of diagnosis and self-healing, all from a single observability control plane.

Key Differentiators

Offers limitless integrations for monitoring. You can integrate the platforms and tools that your enterprise relies on, including AWS, Azure, Docker, OpenStack, Kubernetes, etc.
Using Sensu Go’s high-performance enterprise datastore, you can monitor thousands of nodes from a solitary cluster.
With Sensu Go’s federation capabilities, you can obtain visibility into globally distributed infrastructure.
Offers comprehensive health monitoring and enables you to collect basic system metrics, custom application metrics and logs. You can integrate with external databases for unified business intelligence (BI).
Offers incident management and real-time alerting via communication channels like email, SMS and Slack. You can customize alert policies with contact routing and event filters.
Provides native support for diagnosis and self-healing — execute custom scripts/trigger service restarts when problems are detected, automate repetitive operations and trigger remediation actions via third-party APIs.
You can automate service discovery
Sensu Go is available free of cost and is best suited to small-sized companies. Sensu Go Pro is available for $3 per node, per month and is perfectly suited to mid-sized environments. Sensu Go Enterprise is available for $5 per node, per month and is designed for large-sized enterprises.

Git (GitHub, GitLab and Bitbucket)

Git is an open source, distributed version control and source code management (SCM) system that is easy to learn, has a small footprint, and offers lightning-fast performance and efficiency.

With the help of the software, you can easily coordinate work among your DevOps team during source code development. The latest source release of Git is version 2.32.0. You can download the software for Windows, Linux/Unix and macOS.

Key Differentiators

Popular offerings of Git repositories as a service include GitHub, GitLab and Bitbucket.
Git’s branching model enables frictionless context switching, role-based codelines, feature-based workflow and disposable experimentation.
Since Git was built to work on the Linux kernel, is written in C and most operations are performed locally, it can effectively handle large repositories in double-quick time.
As a distributed SCM, there is no single point of failure, as you can create a copy of the entire repository.
Git provides data assurance, as checksums are used to verify data integrity.
With staging area, commits can be formatted and reviewed before completion.
GitHub (free) offers the distributed version control and SCM functionality of Git, along with wikis for every project, continuous integration, task management, feature requests and bug tracking.
GitLab (free) is a web-based DevOps lifecycle tool. Its applications include continuous integration (CI/CD), SCM, Auto DevOps, DevSecOps, agile development, value stream management and GitOps.
Bitbucket (now Bitbucket Cloud) is a one-stop destination for project planning and collaboration on code, testing, and deployment. It is available for free (limited users) and in the form of paid plans. Features include pull requests, Bitbucket Pipelines, IP whitelisting, merge checks, code search, issue tracking and Smart Mirroring.

Red Hat Ansible Automation Platform

Red Hat Ansible Automation Platform provides a framework for building and operating information technology (IT) automation at scale. With a visual dashboard, automation tools including certified, reusable content and analytics and role-based access control, you can centralize and control enterprise infrastructure.

The platform’s YAML automation language makes it possible to assess, manage, and share automation content across an organization. With searchable collections of pre-composed modules and roles, you can easily create automation.

Key Differentiators

With standardized and unified IT automation, Red Hat Ansible Automation Platform helps make network management more consistent. You can automate user onboarding, infrastructure provisioning and orchestration, system patching and updating and software installation.

Red Hat Insights provides unified visibility across platforms. With Red Hat Insights, you can detect, analyze and remediate potential software and configuration problems through automatic alerts.

Red Hat Insights provides a reporting provision on the status of automation deployments across multiple clusters.

You can easily access and distribute collections of supported, precomposed content for quick implementation.

The platform provides developers and business users access to automation resources and services.

You can automate security practices and collate the tools used in security activities.

Developers can set up automation to manage, provision and deploy compute infrastructure across environments. By automating processes, you can rapidly move software between testing and production environments.

The STANDARD package is ideal for enterprise IT operations. The premium package is ideal for mission-critical DevOps. Contact Red Hat Ansible for pricing information. You can try the platform free of cost for 60 days.

Microsoft Teams

When it comes to unifying distributed members of your DevOps team, there is no better solution than a Unified Communications as a Service (UCaaS) platform. Microsoft Teams is an UCaaS platform that allows organizations to virtually meet, chat, call, and collaborate.

Microsoft Teams is the free version of Microsoft’s UCaaS offerings and does not include additional Microsoft Office services and applications. That said, the solution is sufficient if all you need is real-time presence monitoring, individual and group chatting and secure online meetings with up to 100 members, for up to an hour at a time.

Key Differentiators

You can set up ChatOps with messaging extensions. You can integrate all the components in your DevOps toolchain. By integrating DevOps tools, these applications will publish content directly into team conversations/individual chats, which enables faster resolution of issues, ease of collaboration, quicker update sharing, and better knowledge dissemination.
Enterprises embedded in the Microsoft tool suite can benefit from Microsoft Teams. You can integrate over 700 applications from the app store to increase team productivity and manage complex projects. You can leverage custom-built applications to address industry-specific needs with the Microsoft Power Platform.
Microsoft Teams is available in 181 markets and 53 languages. Windows, macOS, Android and iOS users can download and implement the solution.
Microsoft Teams is free of cost. Microsoft 365 Business Standard is ideally suited to small- and mid-sized organizations and is available for $12.50 per month/per user (annual commitment). Microsoft Office 365 E3 is best suited to large-scale enterprises and is available for $20 per month/per user (annual commitment).
Microsoft 365 Business Standard and Microsoft Office 365 E3 offer additional perks when compared to Microsoft Teams, including larger meeting participant capacities, longer meeting durations, the ability to record meetings, personal file storage, business email, advanced auditing and reporting and secure cloud storage.

Choosing DevOps Monitoring Tools

SolarWinds AppOptics offers modern infrastructure monitoring, root cause determination of application performance issues, distributed transaction tracing, custom metrics and analytics and several turnkey, cloud-ready integrations. Overall, SolarWinds AppOptics is a handy DevOps monitoring tool.

The Sensu Go observability pipeline provides monitoring for mission-critical systems and is integrated, secure and scalable. The solution offers health checks, custom metrics and logs, alerts and incident management, endpoint management, auto-remediation and monitoring as code. Sensu Go is one of the best DevOps monitoring tools around.

Git is an essential component of DevOps. You can incorporate several services for hosting your Git repositories, including GitHub, GitLab and Bitbucket. If you are looking for a foundation for building and operating enterprise automation at scale, Red Hat Ansible Automation Platform is a fantastic tool.

Microsoft Teams is an excellent solution to connect distributed team members. You can avail of ChatOps, integrate over 700 applications to streamline workflow, build custom applications and host and participate in video conferences.

You can utilize one or more DevOps monitoring tools, so strictly assess each of the tools we detailed and add one or more of them to your DevOps toolchain.

Fully stacked Starship caps busy week at SpaceX’s Texas rocket yard

Presplay — Tue, 10 Aug 2021 00:59:31 +0000

Last week’s progress at SpaceX’s Starship development site culminated with the spectacular, but brief, sight of a fully-stacked launcher towering nearly 400 feet above the tidal flats of South Texas.

The first full stacking of SpaceX’s Starship launch vehicle, doubling as a fit check and photo opportunity, will be followed by more outfitting of the huge rocket ahead of its first orbital test launch. Later Friday, SpaceX detached the Starship upper stage and rolled it back to a nearby high bay for additional work to prep for its trip to space.

Elon Musk, SpaceX’s founder and CEO, tweeted Friday that engineers in South Texas will complete work on the heat shield tiles that cover the stainless steel skin of the rocket’s upper stage, known simply as Starship. SpaceX will also install thermal protection materials around the 29 high-power Raptor engines at the base of the rocket’s first stage, which SpaceX calls the Super Heavy.

Together, the rocket stands 394 feet (120 meters) tall. That’s enough to make the Starship the tallest rocket ever built.

Musk said Friday that SpaceX teams will also complete work on the ground storage tanks that will contain the methane and liquid oxygen propellants to be loaded into the gigantic rocket. Another task will be the mounting of a quick disconnect arm on the launch tower at the orbital launch pad at the Starship development site, which SpaceX calls Starbase.

The quick disconnect arm will feed propellants into the Starship upper stage during the countdown.

“Two weeks,” Musk tweeted.

The launch tower itself is a recent addition to the Starbase site. SpaceX constructed the structure earlier this summer.

Musk did not mention other work planned ahead of the first Starship orbital launch attempt. SpaceX is expected to perform cryogenic proof testing of the Super Heavy and Starship. SpaceX may also be planning multiple test-firings of their Raptor engines.

Last week’s accomplishments at Starbase, located on the Texas Gulf Coast east of Brownsville, included the first assembly of 29 Raptor engines at the bottom of a Super Heavy booster.

SpaceX mounted six Raptor engines to a Starship upper stage, including three engines designed for operation in Earth’s atmosphere and three with larger nozzles optimized for firing in space.

The 29 methane-fueled Raptor engines on the Super Heavy booster will combine to generate nearly 15 million pounds of thrust at full power, more than any other rocket in history.

Musk tweeted Friday that seeing the first full-scale Starship launch vehicle on its launch pad was a “dream come true.”

SpaceX has not identified a target date for the Starship’s first orbital test launch, but the company wrote in a filing with the Federal Communications Commission in May that it expected the demonstration mission to occur some time between June 20 and Dec. 20.

Crews at SpaceX’s Starbase test site in South Texas stack the company’s first full-scale Starship testing vehicle Friday. Credit: SpaceX

The orbital test launch will follow a series of ongoing atmospheric flights intended to validate the rocket’s performance at relatively low altitudes.

The five Starship prototypes, each using only the vehicle’s upper stage, launched since December have each used three Raptor engines to power the 16-story test rockets to altitudes of more than 30,000 feet (about 10 kilometers) over South Texas. Four test rockets exploded during or soon after landing, but the most recent Starship prototype — Serial No. 15 — nailed its vertical, propulsive touchdown back at the Starbase facility.

The Starship stage, like the Super Heavy booster and SpaceX’s partially reusable Falcon 9 rocket currently in operation, will use variable thrust from its main engines to slow down for landing.

The Super Heavy and Starship vehicles stacked Friday are designated Booster 4 and Ship 20.

Unlike the Starships flown on the recent atmospheric hops, Ship 20 is covered in thousands of heat-resistant tiles to protect the craft’s stainless steel structure from the scorching heat it will encounter during re-entry into Earth’s atmosphere.

Crews at SpaceX’s Starbase test site in South Texas stack the company’s first full-scale Starship launch vehicle Friday. Credit: SpaceX

SpaceX is developing the privately-owned Starship vehicle as a fully reusable launch and space transportation system capable of ferrying more than 100 metric tons of cargo into low Earth orbit, more than any other rocket in the world. SpaceX eventually aims to develop an in-space refueling capability to extend Starship’s heavy-duty cargo carrying range into the solar system.

During an orbital launch attempt, a reusable Super Heavy first stage booster will detach from the Starship and come back to Earth for a vertical landing. Eventually, SpaceX wants to use catcher arms on the launch tower to capture the descending first stage, making it easier to configure and refuel for another mission.

SpaceX is also modifying offshore oil drilling rigs to serve as floating Starship launch and landing platforms.

The Starship will continue into orbit and deploy its payloads or travel to its deep space destination, and finally return to Earth to be flown again. The Starship vehicle doubles as an upper stage and a refillable transporter to ferry people and cargo through space to destinations in Earth orbit, the moon, Mars, and other distant locations.

The reusable architecture, which builds upon SpaceX’s partially reusable Falcon 9 rocket, is designed to reduce the cost of each flight.

“There is a reason no fully reusable orbital rocket has been built — it’s an insanely hard problem,” Musk tweeted Friday. Moreover, it must be rapidly & completely reusable (like an airplane). This is the only way to make life multiplanetary. Efficiencies of scale is why Starship is so large.”

The Starship’s first orbital test flight, though audacious in scale, will aim to prove out the rocket’s basic launch and re-entry capabilities without fully testing out the complicated landing and recovery systems, according to SpaceX’s filing with the FCC.

After liftoff, the rocket’s Super Heavy booster will fire its cluster of up to 29 Raptor engines for around 2 minute, 49 seconds, on a track toward the east from the Starbase launch site.

About two seconds later, the 228-foot-tall (69.5-meter) Super Heavy booster will jettison to begin a descent to a landing in the Gulf of Mexico around 8 minutes, 15 seconds, after launch. The giant booster will aim to land about 12 miles, (20 kilometers) from shore, according to SpaceX.

Meanwhile, the Starship orbital stage will ignite its Raptor engines at T+plus 2 minutes, 56 seconds, and accelerate into orbit, heading east over the Gulf of Mexico and following a track passing between South Florida and Cuba. Cutoff of the Raptor engines is expected about 8 minutes, 41 seconds, into the mission, SpaceX said, once the rocket achieves the required orbital velocity of around 17,000 mph (more than 27,000 kilometers per hour).

“The Orbital Starship will continue on flying between the Florida Straits. It will achieve orbit until performing a powered, targeted landing approximately 100 kilometers (about 62 miles) off the northwest coast of Kauai in a soft ocean landing,” SpaceX said.

The entire flight — from liftoff in Texas to splashdown near Hawaii — will last around 90 minutes.

SpaceX’s Super Heavy booster with 29 Raptor engines. Credit: Elon Musk on Twitter

One of the first operational uses of the Starship vehicle will be as a lunar landing craft ferrying astronauts to and from the moon’s surface.

In April, NASA awarded SpaceX a $2.9 billion contract to design, build, and test a Starship variant to carry astronauts to the moon’s surface for the first human lunar landing in more than 50 years.

NASA says the first crew moon landing in the agency’s Artemis lunar program could still happen before the end of 2024, a date originally established under the Trump administration.

President Biden has kept the Artemis program largely on track, although NASA officials admit technical or budget delays could thwart prospects for a human lunar landing in 2024.

NASA is in the final stages of assembling its own government-managed heavy-lift rocket called the Space Launch System at the Kennedy Space Center in Florida.

The first version of the SLS, known as Block 1, will stand about 322 feet (98 meters) tall and generate 8.8 million pounds of thrust at liftoff.

NASA says the SLS Block 1 configuration can carry more than 95 metric tons of payload to low Earth orbit, but all of the rocket will be expended. The rocket will be powered by four hydrogen-fed engines and twin solid rocket boosters left over from the space shuttle program, during which the engines and booster segments were reused.

The space agency has spent more than $19 billion on the SLS program since 2011, and the rocket’s first launch has been delayed more than three years.

The first SLS test flight, named Artemis 1 and still officially scheduled late this year, will launch NASA’s Orion crew capsule on an unpiloted test flight around the moon, setting the stage for the Artemis 2 mission in 2023 to send astronauts on a round-trip flyby of the moon.

For the first Artemis lunar lander mission, astronauts will also launch aboard an Orion spacecraft on top of the Space Launch System, then rendezvous near the moon with SpaceX’s Starship landing vessel, which will launch separately — and without a crew — atop a Super Heavy booster.

The crew members will dock with the Starship and ride SpaceX’s 15-story lander to the lunar surface. The Starship will ferry the astronauts back to the Orion capsule for return to Earth.

OVERCOMING CLOUD MIGRATION COMMON ISSUES

Presplay — Sun, 30 May 2021 18:38:52 +0000

More than 85% of organizations use cloud platforms for at least one application today. That said, most organizations also face challenges when transitioning to a cloud environment. Find out what some of the most common cloud migration problems are, and how a managed service provider and an end-to-end cloud migration strategy can ensure successful data migration.

WHY BUSINESSES ARE WILLING TO FACE CLOUD DATA MIGRATION CHALLENGES

Few organizations are concerned about the costs of transitioning to the cloud. But the advantages of migrating data to the cloud are exponential.

Virtually every business is willing to bear the short-term pain of migrating to take advantage of the long-term benefits of cloud computing:

Mobility
Cost Savings
Flexibility
Disaster recovery
Scalability
Insight
Security
Autonomous software updates

Though every organization’s business objectives are different, and strategies for moving data to a cloud-based environment also unique, most still face very similar challenges.

In this article, we discuss the top challenges surrounding the cloud migration process, and how you can avoid them.

Monitor metrics on Azure Database for PostgreSQL – Flexible Server

Presplay — Sat, 22 May 2021 13:25:38 +0000

Monitoring data about your servers helps you troubleshoot and optimize for your workload. Azure Database for PostgreSQL provides various monitoring options to provide insight into the behavior of your server.

Metrics

Azure Database for PostgreSQL provides various metrics that give insight into the behavior of the resources supporting the PostgreSQL server. Each metric is emitted at a one-minute frequency, and has up to 93 days of history. You can configure alerts on the metrics. Other options include setting up automated actions, performing advanced analytics, and archiving history. For more information, see the Azure Metrics Overview.

List of metrics

The following metrics are available for PostgreSQL flexible server:

LIST OF METRICS
Metric	Metric Display Name	Unit	Description
active_connections	Active Connections	Count	The number of connections to your server.
backup_storage_used	Backup Storage Used	Bytes	Amount of backup storage used. This metric represents the sum of storage consumed by all the full database backups, differential backups, and log backups retained based on the backup retention period set for the server. The frequency of the backups is service managed. For geo-redundant storage, backup storage usage is twice that of the locally redundant storage.
connections_failed	Failed Connections	Count	Failed connections.
connections_succeeded	Succeeded Connections	Count	Succeeded connections.
cpu_credits_consumed	CPU Credits Consumed	Count	Number of credits used by the flexible server. Applicable to Burstable tier.
cpu_credits_remaining	CPU Credits Remaining	Count	Number of credits available to burst. Applicable to Burstable tier.
cpu_percent	CPU percent	Percent	Percentage of CPU in use.
disk_queue_depth	Disk Queue Depth	Count	Number of outstanding I/O operations to the data disk.
iops	IOPS	Count	Number of I/O operations to disk per second.
maximum_used_transactionIDs	Maximum Used Transaction IDs	Count	Maximum transaction ID in use.
memory_percent	Memory percent	Percent	Percentage of memory in use.
network_bytes_egress	Network Out	Bytes	Amount of outgoing network traffic.
network_bytes_ingress	Network In	Bytes	Amount of incoming network traffic.
read_iops	Read IOPS	Count	Number of data disk I/O read operations per second.
read_throughput	Read Throughput	Bytes	Bytes read per second from disk.
storage_free	Storage Free	Bytes	The amount of storage space available.
storage_percent	Storage percent	Percentage	Percent of storage space used. The storage used by the service may include the database files, transaction logs, and the server logs.
storage_used	Storage Used	Bytes	Percent of storage space used. The storage used by the service may include the database files, transaction logs, and the server logs.
txlogs_storage_used	Transaction Log Storage Used	Bytes	Amount of storage space used by the transaction logs.
write_throughput	Write Throughput	Bytes	Bytes written per second to disk.
write_iops	Write IOPS	Count	Number of data disk I/O write operations per second.

Server logs

Azure Database for PostgreSQL allows you to configure and access Postgres’ standard logs. To learn more about logs, visit the logging concepts doc.

Performance Recommendations in Azure Database for PostgreSQL – Single Server

Presplay — Sat, 22 May 2021 13:19:42 +0000

Applies to: Azure Database for PostgreSQL – Single Server versions 9.6, 10, 11

The Performance Recommendations feature analyses your databases to create customized suggestions for improved performance. To produce the recommendations, the analysis looks at various database characteristics including schema. Enable Query Store on your server to fully utilize the Performance Recommendations feature. After implementing any performance recommendation, you should test performance to evaluate the impact of those changes.

Permissions

Owner or Contributor permissions required to run analysis using the Performance Recommendations feature.

Performance recommendations

The Performance Recommendations feature analyzes workloads across your server to identify indexes with the potential to improve performance.

Open Performance Recommendations from the Intelligent Performance section of the menu bar on the Azure portal page for your PostgreSQL server.

Select Analyze and choose a database, which will begin the analysis. Depending on your workload, th analysis may take several minutes to complete. Once the analysis is done, there will be a notification in the portal. Analysis performs a deep examination of your database. We recommend you perform analysis during off-peak periods.

The Recommendations window will show a list of recommendations if any were found.

Recommendations are not automatically applied. To apply the recommendation, copy the query text and run it from your client of choice. Remember to test and monitor to evaluate the recommendation.

Recommendation types

Currently, two types of recommendations are supported: Create Index and Drop Index.

Create Index recommendations

Create Index recommendations suggest new indexes to speed up the most frequently run or time-consuming queries in the workload. This recommendation type requires Query Store to be enabled. Query Store collects query information and provides the detailed query runtime and frequency statistics that the analysis uses to make the recommendation.

Drop Index recommendations

Besides detecting missing indexes, Azure Database for PostgreSQL analyzes the performance of existing indexes. If an index is either rarely used or redundant, the analyzer recommends dropping it.

Considerations

Performance Recommendations is not available for read replicas.

Next steps

Learn more about monitoring and tuning in Azure Database for PostgreSQL.

Executing the right migration strategy for your IT transformation.

Presplay — Thu, 22 Apr 2021 17:41:43 +0000

While this may seem academic, we have seen organizations spend millions with no results—all because their project lacked focus.

In today’s market place, migrations are frequently referred to as relocations, consolidations, cloud migrations, or hybrid migration. The ability to differentiate between the various types of migrations is fundamental to communicating what you are trying to accomplish. It facilitates a more intelligent conversation within an organization, its stakeholders, executive sponsors, and vendors.

Migration is a general, overarching term describing the process of moving IT systems, workloads, applications, and their infrastructure from their present operating environment to one or more new target environments, e.g., private/public cloud, colocation facilities, edge location, and/or an owned and operated data center.

What type of migration should you execute?

Hybrid
Cloud
Consolidation
Colocation
Relocation

Hybrid

The lines have been blurred between the different types of migrations. Many organizations today require a hybrid enterprise environment where their infrastructure and systems operate across multiple IT landscapes. These landscapes can include owned, leased and operated data centers, various private and public clouds (IaaS, PaaS, SaaS, DRaaS), and colocation facilities. A hybrid enterprise can provision and move applications with great fluidity between various infrastructures to optimize performance, security, and cost. But, the most compelling reason for the hybrid enterprise is the speed with which an enterprise can respond to market opportunities and competitive threats. The IT department is no longer the bottleneck for rolling out new services, it’s the accelerator, dramatically transforming the IT landscape.

Cloud

Cloud migrations move applications, workloads, systems, and infrastructure from a physical and/or virtual environment (p2c, v2c) to a private or public cloud provider, or it moves these systems in between cloud environments.

While not necessarily less expensive than physical infrastructure, cloud infrastructure can transform the enterprise with greater agility and scalability through:

On-demand self service
Broader network access
Resource pooling
Rapid elasticity
Measured/metered services\

Consolidations

Data center consolidations reduce the number of physical data centers and/or the number of servers being used by either decommissioning legacy servers, repurposing servers, and/or the reducing servers via virtualization and/or hyper-converged technology. The goal is to achieve a higher level of density and decreased footprint. In many cases, the physical consolidation of facilities has similar attributes but also includes the sale of the facility, exit from a lease, and/or reuse of the space for other mission critical needs. Here are several of the top benefits:

Less hardware
Power savings
Smaller network
Lower facility costs
Reduced cooling loads
Fewer software licenses
Reduction in manpower

Consolidations are typically driven by server sprawl, mergers and acquisitions, a demand for higher density levels via virtualization, and cost savings from power and cooling consumption.

Colocation/ Relocation

Data center relocations move infrastructure from their current location to a new location. It involves only two data centers: the sending data center (source location) and the receiving data center (target location). These are accomplished in the following manner:

Physical-to- physical (p2p or forklifts)
Physical-to-virtual (p2v)
Virtual-to-virtual (v2v)
Physical-to-cloud (p2c)
Virtual-to-cloud (v2c)

Increasingly, enterprises are electing to collocate in lieu of building new data center facilities. The exceptions are organizations in highly regulated industries with compliance requirements such as banking, health-care, and public utilities.

The decision to build, buy, modernize or collocate a data center(s) is also influenced by an organization’s CapEx or OpEx posture. If the goal is to maximize OpEx, then collocation is smart. If not, CapEx compels a build, buy, or modernize approach depending on variables such as power consumption, cooling, footprint, cost, and timeline to operational readiness.

Relocation success starts with identifying the optimum target location; therefore, site selection is critical.

What Does an AWS Cloud Support Engineer Do?

Presplay — Thu, 25 Mar 2021 22:27:13 +0000

It seems that AWS is the underpinning of a lot of the technology we use today — websites, monitoring, data management, and more. What’s more, the prevalence of AWS cloud support engineers are more in-demand.

For the uninitiated, Amazon Web Services (AWS) Cloud is Amazon’s cloud platform that offers over 175 applications, ranging from infrastructure and storage to blockchain and IoT. Many developers use AWS Cloud applications when building out their products.

With so many AWS applications and over 1 million customers, it takes a fleet of talented AWS Cloud Support Engineers to keep things moving. So what does being an AWS cloud support engineer entail?

A Day in the Life of an AWS Cloud Support Engineer

A day in the life of an AWS Cloud Support engineer involves a combination of helping customers with their AWS applications, debugging reported problems, building and maintaining AWS test instances, and working with AWS Cloud Developers to better understand and support the product.

Recently, Amazon’s AWS blog shared a day in the life of one of their AWS Support engineers to try and attract more support engineers to apply for jobs with them. This AWS Support Engineer worked on a large variety of different issues with various customers, from talking a new customer through launching their Amazon EC2 instance to assisting an existing customer with their massive data migration.

Each day, there are new problems ready to be solved and sometimes there are even new products to learn and support. That’s where the testbed comes in. AWS Cloud Support Engineers generally own and maintain their own testbed.

This can be used to run automated tests, build out a new application in order to learn how to troubleshoot it better, and even try to simulate problems experienced by customers.

Since AWS Cloud supports applications on the web, they must be up and running all the time. If something goes wrong, there must be a support engineer available to help. This means that AWS Cloud Support Engineers typically work in shifts: a day shift and a night shift. The work is typically the same, if you’re a night owl, this could be a really great job opportunity for you!

The Skillset of an AWS Cloud Support Engineer

AWS Cloud Support Engineers should have a solid understanding of AWS applications, cloud computing, networking, system administration, scripting, automated testing, security, system architecture, and network administration.

Since this role centers on supporting customers, it’s important for AWS Cloud Support Engineers to be tireless troubleshooters who can see both the big picture and get down to details. Expert knowledge of AWS applications is a must. Plus, experience in customer and technical support is a huge plus.

AWS Cloud Support Engineer Expected Salary

According to Paysa, AWS Cloud Support Engineers make an average of $155,000 a year, with the top percentile of earners making close to $200,000.

Keep in mind that Paysa’s numbers are based on salaries at Amazon. You can also be hired as an AWS Cloud Support Engineer at other companies — like Digital Island, Borland, or Pinnacle Systems. Those salaries average closer to $134,000.

Your Journey to Being an AWS Cloud Support Engineer

If helping customers with their AWS Cloud products, maintaining and monitoring your own testbed, and making well over six figures a year sounds like your dream job, then it’s time to get started adding those skills to your resume!

Migrate with confidence using a proven data center and cloud migration strategy.

Presplay — Mon, 22 Mar 2021 17:46:41 +0000

The Migration Strategy Board helps organizations develop a data center or cloud migration plan. Designed like an interactive game board, it visualizes the five major phases of a data center and cloud migration project.

It includes objectives, deliverables, tools, and additional tips for migrating assets, infrastructure, and services. A methodology specific to migrations helps ensure operational stability, business continuity, and savings.

White Paper

The Cloud and Data Center Migration Methodology

Discover the cloud and data center migration methodology behind the Migration Strategy Board. It is a proven process that migrates physical assets and apps with zero operational disruption. Get insight for your hybrid IT transformation and reduce IT costs.

Migrate physical assets and applications with zero operational disruption.

David-Kenneth Group’s Cloud and Data Center Migration Methodology (DKGm) is a step-by-step, proven process for planning and executing successful migrations. It is intentionally designed to support hybrid IT operating environments. Organized into five phases, it includes a baseline of more than 80 deliverables and two migration-specific toolsets. Below is a summary of each phase.

Five Methodology Phases

Phase 1: Initiation
Phase 2: Discovery
Phase 3: Planning
Phase 4: Execution
Phase 5: Closeout

Phase 1: Initiation

The Initiation Phase launches the project and includes key objectives that lay the groundwork for success. It establishes the business case and project charter, organizes the project team, and is where a high-level migration strategy begins to take shape.

Your key objectives are:

Define enterprise strategy: Identify and document how the cloud and the data center can be a driver of key strategic business initiatives. Also, provide guidelines for cloud adoption, future modernization and optimization initiatives, and other agile technologies.

Develop business case: Identify the goals and objectives (business and technical) for cloud and data center migrations, key performance indicators, risks and benefits, and an ROI analysis for the project. A well-crafted case facilitates institutional buy-in.
Develop project charter: Document project objectives and constraints, what is in and out of scope, the resources involved, milestones, risks, dependencies, and high-level budget estimates. A well-executed charter helps to minimize internal politics.

Select migration approaches: Given your current data center, cloud, colocation, and edge environments, identify potential migration types, taking into consideration security and regulatory compliance. Also include in your evaluation the project teams’ skill sets, which can be a significant cost driver if skill gaps need to be addressed.

Create a plan and schedule: Establish a preliminary timeline, schedule, resource list, and communication plan for stakeholders. It should include the estimated resource costs, the number of sites to be moved, the number of move groups, and the major milestones.
Kick-off migration: Review the project timeline, high-level project goals, set expectations, review roles and responsibilities, articulate the communication plan, and kick off your data center migration project with actionable next steps.

Tips

Solid goals are key.
Set realistic expectations.
Enforce project priorities. They will be tested.
Communicate early and often with stakeholders.

The people in your organization and your customers are the most
critical component of your migration. Communicating a solid plan will build
confidence in the project and help address organizational concerns.

Phase 2: Discovery

The Discovery Phase identifies and documents your physical and virtual environment, inclusive of the application inventory and interdependencies. With a combination of auto and manual data collection methods, discovery identifies critical data at the business, application, and infrastructure layers.

The goal is to create a Master Asset Library (MAL), a repository for asset data and the authoritative source for the migration.

It includes the following objectives:

Collect documentation: Collect and consolidate all existing documentation from each business unit, via your databases (CMDB/CMS), diagrams, facility documentation, contracts, etc.
Deploy auto-discovery tool: Deploy an auto-discovery tool to capture data across your operating environment and into the cloud, from application workloads to data lurking at the edge.
Map dependencies: Identify interdependencies across the business, application, and infrastructure layers (network, cloud, compute, and storage). Also capture traffic flows between server, storage, and network assets daily, weekly, monthly, quarterly, and during other seasonal events.

Distribute questionnaires: Use questionnaires to collect otherwise “undiscoverable” information from server and application owners, resolve gaps from auto-discovery, and understand data points that machines cannot uncover, i.e., maintenance windows, application owners, hard-coded IP addresses, security concerns, etc.
Conduct interviews: Interview server and application owners to resolve gaps, address external partner and cloud connections, capture undocumented requirements, and address special situations brought to attention by the questionnaires.

Do manual inventory and site audit: Validate auto-discovered data and capture any assets that were not auto-discoverable. Gather information needed for the floor plan, rack elevation, and patch diagrams.
Consolidate asset data: Consolidate auto- and manual-discovery data into a single repository of truth, aka the MAL, and keep it current with regular scans, including the integration of operational activities with your change control board.

Tips

Don’t get stuck in discovery. If you document too much, you risk budget and schedule overruns.
Different situations require gathering different information. For example, some undocumented assets may only be known by select stakeholders.
Do not forget to gather business information, i.e., TCO, ROI, SLAs, service windows, refresh.

Organizations discover undocumented IT assets and dependencies 100%
of the time and typically experience a +20% variance between what is known and what is discovered.

Phase 3: Planning

The Planning Phase is where the team determines dispositions and performs move-group planning. The project plan and schedule evolve into the master plan for execution. During this phase a clear and consolidated picture of what will be necessary during the execution phase takes shape.

Here are the objectives:

Application workload placement: Use your discovery data to categorize and prioritize workloads to assess best-fit placements. Be certain to carefully weigh the implications of any application infrastructure modifications, i.e., rehost, re-platform, repurchase, refactor, retire, and retain. Evaluate and select a cloud service provider(s), ensuring organizational requirements, regulatory requirements, data controls, and compliance laws (GDPR, SOX, PII) are supported.

Determine dispositions: Use discovery data and business drivers to select the end-state disposition of physical assets and applications where it can optimally function and service the business. A hybrid mix of dispositions is typical as some systems are not cloud-ready or cloud-fit.

Create move groups: Analyze data in the MAL to understand interdependencies between transactions, services, IP, systems, applications, networks, compliance regulations, and hardware. Establish the move groups and move dates, and for a quick win, identify migration pilot group(s) to test and optimize, ensuring that at least one of every migration disposition planned is included.

Modernize and optimize infrastructure: Identify the current state of your infrastructure (as-is), the ideal future state (to-be), and the temporary transition state necessary between them. Align with business, budget, and timeline objectives to remediate necessary gaps and issues. Design (high-level and low-level designs), procure via a bill of materials (BOM), build, and configure your target state IT infrastructure environment.
Modernize and optimize cloud: Ensure you are fully leveraging the agility and elasticity of the cloud by updating operational processes and procedures.

Formulate test plans: Migration testing must validate that the new infrastructure and cloud services continue to deliver the same services and performance. Tabletop, infrastructure, application, user acceptance, and latency testing are optimal.

Develop move plans: Sequence all the move groups on a timeline for the migration. Review and verify the move plan schedule with the business stakeholders to ensure no negative impacts. Don’t forget logistical and backup planning.

Plan data management: Compartmentalize the data in the cloud environment to control access, ensure compliance requirements are in place/configured, and mitigate security risks.
Mitigate migration risks: Mitigate potential migration risks and issues with contingency dates, rollback plans, backup resources, a clear chain of command for quick decisions, enforced change control, and other elements that establish a robust fault-tolerant plan.

Prepare target data center locations: Upgrade and install in advance the power, circuits, cooling, and cabling infrastructure. Ready all the new equipment in the target location and validate it performs to specification via ready-for-use (RFU) testing before any migrations can begin.
Prepare target cloud provider: Configure the initial cloud setup for users, billing, resource hierarchy, access control, networking configuration, monitoring, security, compliance, and other basic set-up requirements before the first service is hosted to avoid future re-work and issues. Architect and design your target cloud environment much like you would your data center taking into account needs for high availability and redundancy. The cloud is not an excuse for poor design and is not a panacea with built-in redundancy. It must be designed.

Tips

Creative timing and groupings can simplify or reduce costs.
Procurement is often a critical path, especially for new circuits.
Have a fallback window and a plan B. Do not be afraid to use them.

Smart simplicity and creative problem solving can resolve
challenges—like unsupported assets, security gaps,
and more—without disrupting the timeline or the budget.

Phase 4: Execution

A data center or cloud migration is 75 percent planning and 25 percent execution. Thorough planning and preparation are your best protection against migration risks. Pre-migration testing, pilot migrations, contingency rollback planning, and detailed cutover run books support the final go or no-go decision as the gatekeeper for execution readiness. Post-testing, acceptance criteria, and solid issue tracking ensure you do not walk away from the scene with a hidden bomb still ticking.

Below are the crucial steps to the Execution Phase:

Complete pre-migration tests: Utilize pre-migration testing as a baseline for post-migration performance, and identify errors or performance issues already present in the system. Course-correct before initiating a migration.
Execute data center pilot migration(s): Use pilot migrations as an opportunity to build support and trust internally by migrating low-complexity, low-risk workloads. Utilize the same key steps for large groups, optimizing processes and procedures, and documenting lessons learned. Similarly, migrate non-production environments before their production equivalent to refine and monitor the success of the cutover process.
Execute cloud pilot migrations: Test migration tools for status tracking, performance evaluation, and cost-effectiveness against the metrics defined in the business case. Map out any solutions for bottlenecks before they become an issue with a production system
Run data center backups: Establish and execute a backup plan to ensure a full restore is possible in the event of total equipment failure or data loss during migration.
Run cloud backups: Confirm that business-critical data and applications in the cloud are recoverable and within the allowable timeframe.
Decide go/no-go: Make a go/no-go decision about whether to execute the migration. This decision is made jointly by a designated team of decision-makers comprised of core project team members.

Execute migration: Execute the migration based on the migration plan and run book. Enforce a clear chain of command and responsibilities, capturing and managing any issues as they emerge.

Complete post-migration testing: Run infrastructure test scripts on storage devices and servers to ensure a healthy connected environment, then hand off for business user acceptance testing of databases and applications. Finally, closely monitor applications in production for the next 24 hours for any necessary performance tuning.
Conclude support period: Keep the migration support desk open to ensure full stabilization of the system and to address issues that can surface a week or so post-migration.

Tips

Bigger moves can be easier than small ones.
Migrate from steady-state to steady-state.
Do not underestimate the test planning effort.

Triggering your contingencies and maintaining control can make
a critical difference when the plan does not go as planned.

Phase 5: Closeout

After completing the complex undertaking of migration, the Closeout Phase can catch organizations by surprise with hidden risks and expenses, and it can take longer than anyone expects.

Below are the objectives:

Decommission assets & space: Track the inventory of remaining assets and develop a strategy for decommissioning them. Assets may be liquidated, retired, or resold. Review your lease agreement and building and facility services contracts. Establish a termination plan for services at the previous facility, restore and clean the site, and protect or destroy any sensitive materials.
Establish operations: Ensure that regular operations’ staff are familiarized with the new environmental responsibilities and skill gaps are remediated, and fully return operational activities to them. Also, integrate DevOps and update the governance model including infrastructure and data standards for the cloud. Define the customer interface for cloud services. To ensure business continuity, review DR plans with the newly transformed environment. Establish strong governance for cloud capabilities and attributes with future cloud applications, services, and monitoring capabilities in mind.

Optimize infrastructure: Continuously monitor, measure, and improve procedures and procedures to ensure responsiveness to business dynamics and needs. Do not hesitate to terminate cloud instances that are not fully utilized or no longer serve their purposes(s). Remember to identify KPIs as a baseline for ongoing infrastructure optimization, modernization, and cost control comparison.
Optimize cloud: Monitor cloud utilization and costs across internal and external platforms and develop a capacity-planning process that keeps the cloud rightsized. For ongoing cleanup and containment, establish audit levels and a cloud adoption framework.

Update contracts and SLA agreements: Manage relationships with stakeholders as you update contracts and SLA agreements, and ensure all details are reflected in new agreements.
Conduct debrief & close project: Change inevitably brings about lessons learned. Review the project with stakeholders and capture, document, and mitigate any issues. Take this opportunity to also document new design considerations discovered during the migration project. Review key success metrics, document findings, show savings, and package these data points into a debriefing report. Invite the sponsors to review and accept the deliverables.

Tips

If the disaster recovery of primary critical systems is not working well, now is the time to correct it while the right team is assembled.
Absorb valuable information gained from the migration project into the organization and tools.
Publish lessons learned as a record for future migration projects.

Done right, significant value and expense can be saved in the closeout phase.

The Bottom Line about Cloud and Data Center Migrations

A data center and cloud migration can fundamentally transform how you deliver IT services and yield an attractive return on investment for IT and business operations. But, you need a rock-solid migration plan, tailored to your operating environment, to get you there.

A methodology specific to migrations will help you create the plan and achieve the transformative results you are looking for while ensuring operational stability in the process.

Presplay Cloud Tech*

Amazon to Acquire Health Care Company One Medical in $3.9 Billion Deal

Machine Learning And Artificial Intelligence, Cloud Computing and 5G Will be the Most Important Technologies in 2022

Artificial Intelligence and Machine Learning, Cloud Computing and 5G Will be the Most Important Technologies in 2022, Says New IEEE Study

Best DevOps Monitoring Tools for 2021

What are Monitoring Tools in DevOps?

Best DevOps Monitoring Tools

SolarWinds AppOptics (Librato)

Sensu Go

Git (GitHub, GitLab and Bitbucket)

Red Hat Ansible Automation Platform

Microsoft Teams

Choosing DevOps Monitoring Tools

Fully stacked Starship caps busy week at SpaceX’s Texas rocket yard

OVERCOMING CLOUD MIGRATION COMMON ISSUES

WHY BUSINESSES ARE WILLING TO FACE CLOUD DATA MIGRATION CHALLENGES

TOP 8 CLOUD MIGRATION CHALLENGES AND PROBLEMS

– SECURITY & PRIVACY

– DOWNTIME

– LACK OF STRATEGY

– INTEROPERABILITY

– COST

– ADAPTABILITY

– CAPABILITY

– BANDWIDTH

Monitor metrics on Azure Database for PostgreSQL – Flexible Server

Metrics

List of metrics

Server logs

Recommended content

Backup and restore in Azure Database for PostgreSQL – Flexible Server

Logical decoding – Azure Database for PostgreSQL – Single Server

Monitor and tune – Azure Database for PostgreSQL – Single Server

Logical replication and logical decoding – Azure Database for PostgreSQL – Flexible Server

Limits – Azure Database for PostgreSQL – Flexible Server

Extensions – Azure Database for PostgreSQL – Flexible Server

Query Performance Insight – Azure Database for PostgreSQL – Single Server

Compute and Storage Options – Azure Database for PostgreSQL – Flexible Server

Performance Recommendations in Azure Database for PostgreSQL – Single Server

Permissions

Performance recommendations

Recommendation types

Create Index recommendations

Drop Index recommendations

Considerations

Next steps

Recommended content

Logical replication and logical decoding – Azure Database for PostgreSQL – Flexible Server

Limits – Azure Database for PostgreSQL – Flexible Server

Planned maintenance notification – Azure Database for PostgreSQL – Single Server

Logical decoding – Azure Database for PostgreSQL – Single Server

Backup and restore in Azure Database for PostgreSQL – Flexible Server

Overview of business continuity with Azure Database for PostgreSQL – Flexible Server

Query Performance Insight – Azure Database for PostgreSQL – Single Server

Executing the right migration strategy for your IT transformation.

What type of migration should you execute?

Hybrid

Cloud

Consolidations

Colocation/ Relocation

What Does an AWS Cloud Support Engineer Do?

A Day in the Life of an AWS Cloud Support Engineer

The Skillset of an AWS Cloud Support Engineer

AWS Cloud Support Engineer Expected Salary

Your Journey to Being an AWS Cloud Support Engineer

Migrate with confidence using a proven data center and cloud migration strategy.

The Cloud and Data Center Migration Methodology

Migrate physical assets and applications with zero operational disruption.

Phase 1: Initiation

Tips

The people in your organization and your customers are the most critical component of your migration. Communicating a solid plan will build confidence in the project and help address organizational concerns.

Phase 2: Discovery

Tips

Organizations discover undocumented IT assets and dependencies 100% of the time and typically experience a +20% variance between what is known and what is discovered.

Phase 3: Planning

Tips

Phase 4: Execution

Tips

Triggering your contingencies and maintaining control can make a critical difference when the plan does not go as planned.

Phase 5: Closeout

The people in your organization and your customers are the most
critical component of your migration. Communicating a solid plan will build
confidence in the project and help address organizational concerns.

Organizations discover undocumented IT assets and dependencies 100%
of the time and typically experience a +20% variance between what is known and what is discovered.

Triggering your contingencies and maintaining control can make
a critical difference when the plan does not go as planned.