Frictionless and intelligent deployment practices across any footprint are a vital part of Mirantis Container Cloud. This release contains a number of enhancements to Mirantis Container Cloud to make initial deployment and ongoing operations easier. In version 2.13 of Mirantis Container Cloud we introduce the following features: Enhancements in Bare Metal Provisioning – Bare metal … Continued
Quelle: Mirantis
We are proud to share that RAIN, a distributed computing solution supporting industries like manufacturing, utilities, telecom, and retail, has begun to use k0s – a lightweight Kubernetes distro. RAIN leverages multiple Kubernetes distros now, each of which have their own specific use case, and they needed a Kubernetes distro that was lightweight, secure, and … Continued
Quelle: Mirantis
The world’s resources are increasingly scarce and yet too often they are wasted. At Veolia, we use waste to produce new resources, helping to build a circular economy that redefines growth with a focus on sustainability.Our sustainability mission transcends borders, and nearly 179,000 employees work in dozens of profit centers worldwide to bring it to life. It’s a massive operation that requires an IT architecture to match, which is why we’ve streamlined critical IT work across our global operations with Google Cloud. As Technical Lead and Product Manager for Veolia’s Google Cloud, it’s my team’s responsibility to standardize processes around security, governance, and compliance, and make sure our employees have all the right tools to do their best work, securely. Google Cloud’s Security Command Center (SCC) Premium is the core product that we use to protect our technology environment. We use it across 39 business units, spanning 31 countries worldwide.Fueling autonomy and keeping secure with Security Command Center In line with our sustainability motto “create once, then copy and adapt to reuse many times,” we encourage local teams to work autonomously. That includes their use of Google Cloud solutions. We use many Google Cloud products including BigQuery, Compute Engine, GKE, Cloud Functions, and Cloud Storage. Across the board, we’re working with Google Cloud in an agile and collaborative way to deliver smart water, waste, and energy solutions to communities globally.But there’s no agility without security, and it’s my team’s responsibility to make sure our environment is secure at all times. Because our Google Cloud environment is extensive, and we give individual business units autonomy over their use of cloud solutions, we also set the parameters and policies for them to operate with all compliance and security controls in place in an organized way. SCC Premium is the common tool that all our business units use to keep their individual projects and assets secure. It helps us to gain visibility over our entire Google Cloud environment and identify threats, vulnerabilities, and misconfigurations with real-time insights. Gaining visibility to drive resultsHere’s that visibility in numbers: we use SCC Premium to monitor 2,800 projects with hundreds of thousands of assets. We continually observe our Google Cloud environment using SCC to quickly discover misconfigurations and respond to threats based on our latest findings. If an anomaly is revealed, we remediate incidents ourselves or alert respective business units. We’ve also started to consolidate our SCC findings in a global dashboard to give business units an overview of their security position, enabling them to take swift action.Streamlining remediation to curb threats and wasted resourcesAs our risk management platform for Google Cloud, SCC enables us to streamline the process of security management. It provides findings in near real-time and with all its insights, we can decide on the next steps and alert relevant parties to remediate misconfigurations. I really like the context and recommended actions that SCC provides for each of the findings. These recommendations help us to remediate incidents ourselves or alert project owners. This new visibility has already helped us remediate misconfigurations that could adversely affect our cloud services. SCC, for example, enabled us to identify firewall misconfigurations and it saved us around 500 hours when compared to pre-SCC times.Another benefit of the visibility we’ve gained with SCC is our ability to prioritize our security tasks and use our time more efficiently. As one of France’s biggest users of public cloud services, we have a lot of Google Cloud projects running, and a lot of ground to cover — from misconfigurations to imminent threats. Without SCC, it was difficult to identify patterns and adapt our priorities accordingly. Deleting unused service account keys, for example, used to be difficult, because we had to check service accounts for each project separately. With SCC, we identified unused keys and marked them for deletion. This has cut the time it takes us to delete unused service account keys by 1,000 hours. In addition, we use SCC to identify any misconfigurations like overly permissive roles associated with the service account and threats like service account self-investigation. Using SCC’s container threat detection, we can proactively identify threats like remote shell execution in our containers. For example, we were alerted to 1800 findings when a container with a remote shell inside had been duplicated. Thanks to SCC, we managed to identify the root cause and remediate these containers quickly. Stronger compliance, more easily achievedSCC also helps us to strengthen our compliance standards. Our Google Cloud environment needs to align with the CIS Google Cloud Computing Foundations Benchmark v1.1, which helps our organization to improve our overall security posture. Often, a lack of compliance simply means a lack of training. With our SCC findings, we don’t only evaluate where we stand, we are also able to educate our workforce to address issues proactively that help make us more compliant.Securing a sustainable future with Security Command CenterWe’ve already achieved a lot with SCC, and we are excited about the new capabilities we’re yet to explore. Currently, we’re working to implement auto-remediation to help us act on alerts immediately, whenever they occur. By connecting SCC with Pub/Sub, we’ll be able to trigger workflows that fix potential breaches automatically within minutes, by disabling accounts, for example. We also plan to use synergies with Google Workspace to send SCC findings directly to the project owners in real-time via Google Chat, ensuring that relevant employees are made aware of potential vulnerabilities right away.Like all our cloud solutions, we want to use SCC to empower our individual business units with the autonomy they need to pursue their own goals as part of our larger organization. It’s a great tool at their fingertips, helping us to reduce risk and cut down waste across our cloud environment as we work to resource the world more sustainably.
Quelle: Google Cloud Platform
Lung cancer is the leading cause of cancer death in the United States and like any cancer, early detection is crucial to survival. Screening at-risk populations is an important part of reducing mortality, and if concerning nodules are found on imaging, further testing may be required. Today, we’ll share how Northwell Health uses Google Cloud products such as Cloud Healthcare APIs and BigQuery to increase caregiver productivity and deliver better care for patients with findings that indicate potential development of lung cancer.Northwell is New York’s largest healthcare providerNorthwell Health is New York’s largest healthcare provider with 23 hospitals and nearly 800 outpatient facilities. Northwell’s nearly 4,000 doctors care for millions of patients each year, and at this scale, there is an immense amount of healthcare data to manage. To better manage and leverage this data, Northwell Health partnered with Google Cloud starting in 2018.Enabling caregivers to spend more time with patientsNic Lorenzen, the lead developer of Northwell Emerging Technology and Innovation team, has a mission to put together data for caregivers in a way that makes sense. It is no secret that inefficient electronic health records systems have a negative impact on a physician’s ability to deliver quality care. Traditional EHRs have information distributed across many tabs, which forces caregivers to spend considerable time at the computer trying to find information. Moreover, speed of care matters. If care is delayed, patients may have to spend more time in the hospital and may suffer worse health outcomes.To solve this problem, Nic’s team focused on giving caregivers the most relevant pieces of data at the right time by developing an intelligent clinician rounding app. The data needed to derive these insights can depend on the caregiver’s role–a nurse cares about different things than a cardiologist. This system aggregates multiple data sources, and provides patient-specific insights to caregivers.This system would not have been possible before with traditional EHRs and data warehouses that have proprietary data models and rarely sync data in real time. Now with data easily accessible through Google Cloud’s Healthcare solutions, Nic’s team can deliver the right clinical information to the right people instantly. These days, Nic says, “instead of spending 75% of our time dealing with architecting the underlying platforms, we spend 75% of our time focused on higher value use cases for clinicians and patients. Google Cloud’s Healthcare solutions have greatly improved our developer productivity and time to value.”Caregivers have found this new system to be a game changer.Before the implementation of this system, caregivers would spend, on average, seven to nine minutes finding the data needed to make medical decisions for one patient. Now, that aggregated information is delivered to a caregiver’s mobile device in less than a second.Ensuring patients get the right care with the power of AIThere are a number of reasons why patients might not get the care that they need. For example, patients today can go to multiple hospitals and clinics settings, and coordinating care across multiple facilities is complex. Regional hospitals and clinics have their own siloed view of their data, so pertinent information gathered by one clinic might not be seen by another. These gaps in clinical data lead to gaps in patient care.When a patient gets radiologic imaging, they may have findings unrelated to the reason they initially got the imaging. For example, a chest CT for a car accident might reveal an incidental lung nodule that could be cancerous. Unfortunately, research shows that a large portion of patients do not get follow up for these incidental findings because it isn’t the primary reason why the patient is seeing a doctor. Moreover, social determinants of health are a factor that affects which patients receive follow-up care. Identifying these patients and providing the necessary follow up care prevents adverse events related to delayed detection of cancer.Source: https://commons.wikimedia.org/wiki/File:LungMets2008.jpgWith Cloud Healthcare solutions, Northwell built an AI model to identify these patients so that oncologists can appropriately follow up with patients who have findings suspicious for lung cancer. The AI model detects incidental pulmonary nodules in radiology reports so that doctors can then contact the patients that need follow-up care. Nic says his team was able to build this system in a week: “Google Cloud did a lot of heavy-lifting for us and allowed us to get to the AI applications much faster. It allowed us to build a platform that just works.” Healthcare systems can now rapidly generate healthcare insights with one end-to-end solution, Google Cloud Healthcare Data Engine. It builds on and extends the core capabilities of the Google Cloud Healthcare APIto make healthcare data more immediately useful by enabling an interoperable, longitudinal record of patient data. Northwell Health uses Google Cloud as the core of their platform, enabling their developers to create solutions to the most pressing healthcare problems.Special thanks to Kalyan Pamarthy, Product Management Lead on Cloud Healthcare and Natural Language APIs for contributing to this blog post.Related ArticleRead Article
Quelle: Google Cloud Platform
We’re excited to share the news that leading global research and advisory firm Forrester Research has named Google AppSheet a Leader in the recently released report The Forrester Wave™: Low-code Platforms for Business Developers, Q4 2021. It’s our treasured community of business developers—those closest to the challenges that line-of-business apps can solve—who deserve credit for not only the millions of apps created with AppSheet, but also the collaborative approach to no-code development that has helped further our mission of empowering everyone to build custom solutions to reclaim their time and talent. AppSheet received the highest marks possible in the product vision and planned enhancements criteria, with Forrester noting in the report that “AppSheet’s vision for AI-infused-and-supported citizen development is unique and particularly well suited to Google. The tech giant’s deep pockets and ecosystem give AppSheet an advantage in its path to market, market visibility, and product roadmap.”“Features for process automation and AI are leading,” remarking that, “The platform provides a clean, intuitive modeling environment suitable for both long-running processes and triggered automations, as well as a useful range of pragmatic AI services such as document ingestion.”Many enterprise customers including Carrefour Property – Carmila, Globe Telecom, American Electric Power, and Singapore Press Holdings (SPH) choose AppSheet as their business developer partner, along with thousands of other organizations in every industry. We are honored to serve these customers and to be a Leader in the Forrester Wave™: Low-code Platforms for Business Developers. We look forward to continuing to innovate and to helping customers on their digital transformation journey. To download the full report, visit here and enter your email address. To learn more about AppSheet, visit our website.
Quelle: Google Cloud Platform
Docker’s Peter McKee sits down with Uffizzi Co-founders Grayson Adkins – who serves as Head of Product – and Josh Thurman – who serves as Head of Developer Relations – for a Q&A on the CP method.
Check out the live stream from August 26th for Docker Build: Enabling Full-Stack Continuous Previews with Uffizzi
(The below transcript has been edited for clarity and format)
Peter McKee: It’s great having you guys back on the Live Show. I love the idea of Continuous Previews, tell me what brought you guys to the concept?Grayson Adkins: The kernel of the idea – no pun intended – came from our own challenges in trying to develop our product faster. We continued to observe two problems that were hindering forward progress. On the development side we were too often merging broken features – and then we would have all this commingled code and finding where the bug was introduced and then fixing it was really hindering progress. The returned tickets were always holding us back – the classic two steps forward, one step back. On the product side I do all our design work and I kept finding that the design/requirements would need to be modified as I saw the product come to life. And when I would ask “Can I see it yet?” there was no easy solution to that. So for me to see a new feature and provide feedback I would have to wait until the branch was merged and deployed to our QA environment. Then the feedback process would start and, as tickets are returned, they’d go back through this big loop of “In Development”, then merge and deploy, then I can check it again. There was too big of a gap between Development and Product.At the time Uffizzi’s product direction was moving towards making it easy for Developers to deploy their apps to the cloud and once we realized we could fix the “dirty code in main” and “can I see it yet” problems with the same process I realized we could repurpose what we had built to be a Preview Engine for full-stack and microservices applications – something where you could “Continuously Preview” what’s in your feature pipeline.Josh Thurman: There’s two other big picture elements that brought this into focus for us. Everyone has seen the success of the Frontend Preview tools by static site platforms like Netlify and Vercel. Their success taught us that making it easy to Preview was extremely valuable for teams, but no one had really formalized the concept and the supporting technology for more complex applications. So we realized that the Preview concept shouldn’t just apply to frontends, it should apply to everything that we build.The other major factor was observing how the complexity of microservices architectures and remote work were making it harder to collaborate – particularly as teams and app ecosystems grow in size and complexity. So the Continuous Previews concept is really about removing barriers to collaborating early and often – it’s about taking away all the barriers between the developer coding the feature and the team member who is reviewing or approving it.
At a high level, Continuous Previews equals continuous collaboration – so you have a process and technology that is facilitating a collaborative culture and that’s really when you start to see major improvements in team velocity, cycle times, lead times, and code stability.Peter McKee: I’ve read the CP Manifesto ( www.cpmanifesto.org / https://github.com/UffizziCloud/Continuous_Previews_Manifesto ) that outlines the principles of CP, what inspired you to write and publish that?Josh Thurman: It was clear to us that CP is so much bigger than any tool or service, and we also recognize that it’s easy to confuse tools or products with concepts. So we took a cue from the Agile Manifesto and decided that the CP concept and its underlying principles need to be out there for everyone to benefit from and to understand the “Why?”.Grayson Adkins: The Agile Manifesto is the governing document for how to build software as a team, and we see CP as a best practice that’s nested within the Agile umbrella.
Peter McKee: Reading the CP manifesto and talking to you guys a few times about it I have a good sense of what CP is at a strategic level but tell me about the tactical level, how does it impact teams on a day-to-day basis?Grayson Adkins: Most teams follow similar Development workflows that align with the Agile Loop of Design, Develop, Integrate, Test, and Deliver. When you’re following this process a Developer picks up a ticket, checks out a branch and starts developing. Once they think they have met the requirements, they then indicate that their ticket is ready to be merged by opening a PR.
Take this process and multiply it by the number of developers working on different features and you end up with X amount of features that are ready to be merged. At some interval you execute CI (Continuous Integration) and now you have a batch of new features in your QA environment where for the first time in this process they are ready to be reviewed by someone other than the Developer who coded the feature.
The problem with this process is that you are bringing QA in way too late in the game. Once a feature has been merged and deployed it’s 10x harder to find and fix a bug as opposed to catching the issue(s) early and addressing it at the feature branch level where, again, it’s relatively easy to find and fix.
When a developer pushes new code using the CP method it can be QA’d without merging – and also without the Developer having to context switch out of their Git workflow. The Preview has eliminated the barrier to the collaboration, and your iterative process of Develop – Preview, Develop – Preview is happening faster, and it’s also happening earlier in the development process.
In a more literal sense you are bringing QA into the development process where traditionally it has served as an add-on function.Josh Thurman: I’m glad you said teams generically as opposed to saying Development Team or Product Team. Even though we see most organizations task-organize into Dev Team and Product Team, I think the construct can be a hindrance to collaboration. CP is a process for “The Team” meaning everyone who contributes to the success of a product. Peter McKee: You guys have mentioned barriers to collaboration – what exactly are those barriers that teams face now?Josh Thurman: Good question. The cleanest way to have your application readily accessible to everyone on your team for testing is to have it deployed to the cloud and reachable via a secure URL endpoint. I should emphasize here that the endpoint could be to test your full-stack application or any of its individual components like an API or a front end element as examples.
To deploy a version of your application you need a hosting environment – and setting that up – particularly for a complex or microservices-based application – is no easy task. Most teams have persistent environments like Test, QA, Staging, and Production that are maintained by your DevOps and Ops team members. To set up a new environment just to test one feature branch is a significant barrier. The CP method calls for on-demand hosting environments that have a purpose-driven lifecycle. They are stood up to Preview and Test a feature branch and then they are taken down after that feature is merged. This is where technology comes in and this is what Uffizzi does so well. Uffizzi provides teams with an off-the-shelf solution that completely automates on-demand hosting environments with policy-based triggers that facilitate the preview. You can have as many test environments as you need, when you need them, for the amount of time you need them. And I’ll just add that with this method you also remove your single point of failure when you have a persistent QA or Test environment go down and have to spend most of a day fixing that.
Grayson Adkins: The other barrier is DevOps expertise. Just as one example – it’s a significant jump in complexity to go from a 20+ line Docker Compose file to a 1000+ line YAML file. DevOps expertise is often it’s own bottleneck within an organization, and if you can reduce the demands on them with an automated solution that’s a big win. To follow best DevOps practices we’ve centered the product around infrastructure-as-code through a uffizzi-compose.yml that is syntactically the same as docker-compose.yml (based on version 3.9) but with some additional inputs.
But we also have a GUI and the concept of Templates that are meant to increase accessibility – the CP concept is something that can benefit teams of all sizes and skill levels, and we want to act as a DevOps force multiplier in those cases.Peter McKee: Speaking of barriers, what do you guys see as the biggest hurdle to teams adopting a CP methodology?Josh Thurman: For a method to take off it needs to be paired with a technology that is easy enough to use that it really starts to proliferate. Again to reference what Netlify and Vercel have done, they made it simple enough that Frontend Previews have really taken off in the last few years.
Of course this is what we are trying to do with Uffizzi in the context of full-stack and microservices applications. We are offering a very specific tool that makes it easy to implement CP by abstracting away the complexity of managing hosting environments and deployments. Grayson Adkins: I think the other issue is overcoming the inertia of “good enough”—everyone is getting the job done now, so why do they need a new way of doing business? This is the same hurdle with every new process and technology. Before Agile, Waterfall was good enough. Before container orchestration, VMs (virtual machines) were good enough. So I think we’ll go through an early adopter period, and you eventually get to a point where the competitive advantage is such that it requires organizations to implement CP or they risk getting left behind.
Peter: As we wrap up what we can look forward to from Uffizzi – what’s on the Road Map? Grayson Adkins: We’ve got some exciting new features rolling out. In the near term we are expanding our integrations both with image registries and collaboration software. We’re currently rolling out integrations with image registries at all the major cloud providers – AWS, Azure, and GCP. Then over the next few months we’ll add Gitlab and Bitbucket for repos and then Slack, Jira, Microsoft Teams, and Asana on the collaboration side.Peter McKee: Well this has been fantastic, I really appreciate your time and your thought leadership. I can see how this is a game-changer for how organizations build and test. I look forward to seeing how CP and Uffizzi continue to benefit the Dev Community.
If you have any Docker-related questions, please feel free to reach out on Twitter to @pmckee and join us in our community slack.If you have any Uffizzi-related questions, please feel free to reach out on Twitter to @uffizzi_ and join us in our uffizzi users community slack – Josh Thurman (@JoshThurman19) or Grayson Adkins (@GraysonAdkins).You can view the CP manifesto here- www.cpmanifesto.org
And the Open Source Repos here- UffizziCloud/Continuous_Previews_Manifesto: Source for: https://cpmanifesto.org
https://github.com/UffizziCloud/uffizzi_controller
https://github.com/UffizziCloud/uffizzi_app
The post Continuous Previews (CP): Don’t Merge Until You Preview appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/
Das AWS Serverless Application Model (SAM) kündigt eine öffentliche Vorversion von AWS SAM Accelerate an. Die AWS SAM CLI ist ein Entwicklertool, das das Entwickeln, lokale Testen, Verpacken und Bereitstellen von Serverless-Anwendungen vereinfacht. SAM Accelerate ist eine neue Funktion von SAM CLI, die es Entwicklern ermöglicht, Code-Änderungen, die lokal an ihren Serverless-Anwendungen vorgenommen wurden, in einer cloudbasierten Umgebung schneller und einfacher zu testen, wodurch die Zeit von der lokalen Iteration bis zur Produktionsbereitschaft verkürzt wird.
Quelle: aws.amazon.com
Mit dem Amazon Chime SDK können Entwickler ihren Web- oder mobilen Anwendungen Audio-, Video-, Bildschirmfreigabe- und Messaging-Funktionen in Echtzeit hinzufügen. Ab heute unterstützt das Amazon Chime SDK iOS- und Android-Push-Benachrichtigungen über Amazon Pinpoint für Nachrichten, die über SDK-Messaging-Kanäle von Amazon Chime gesendet werden. Mit Push-Benachrichtigungen kann ein Entwickler, der SDK-Messaging von Amazon Chime für den Chat verwendet, dazu beitragen, dass seine Benutzer über neue Nachrichten benachrichtigt werden, auch wenn sie ihre App nicht aktiv verwenden. Benutzer können zwischen Anwendungen wechseln oder ihr Mobilgerät sperren und erhalten eine Benachrichtigung, wenn eine neue Nachricht oder ein Anruf eingeht, sodass sie auf die Benachrichtigung tippen und zur ursprünglichen App zurückkehren können, um das Gespräch fortzusetzen oder dem Anruf beizutreten.
Quelle: aws.amazon.com
Apples iPhones sollen künftig erkennen, wenn sie in einem Auto liegen, das gerade einen Unfall hatte. Dann soll der Notruf gewählt werden. (Apple, iPhone)
Quelle: Golem
Was am 1. November 2021 neben den großen Meldungen sonst noch passiert ist, in aller Kürze. (Internet, Intel)
Quelle: Golem
