Merge branch 'main' into lzf_24.05-01

Author: jpalmeiro

CONTRIBUTING.md

@@ -0,0 +1,55 @@
+# Contributing to this repository
+
+We welcome your contributions! There are multiple ways to contribute.
+
+## Opening issues
+
+For bugs or enhancement requests, please file a GitHub issue unless it's
+security related. When filing a bug remember that the better written the bug is,
+the more likely it is to be fixed. If you think you've found a security
+vulnerability, do not raise a GitHub issue and follow the instructions in our
+[security policy](./SECURITY.md).
+
+## Contributing code
+
+We welcome your code contributions. Before submitting code via a pull request,
+you will need to have signed the [Oracle Contributor Agreement][OCA] (OCA) and
+your commits need to include the following line using the name and e-mail
+address you used to sign the OCA:
+
+```text
+Signed-off-by: Your Name <[email protected]>
+```
+
+This can be automatically added to pull requests by committing with `--sign-off`
+or `-s`, e.g.
+
+```text
+git commit --signoff
+```
+
+Only pull requests from committers that can be verified as having signed the OCA
+can be accepted.
+
+## Pull request process
+
+1. Ensure there is an issue created to track and discuss the fix or enhancement
+   you intend to submit.
+1. Fork this repository.
+1. Create a branch in your fork to implement the changes. We recommend using
+   the issue number as part of your branch name, e.g. `1234-fixes`.
+1. Ensure that any documentation is updated with the changes that are required
+   by your change.
+1. Ensure that any samples are updated if the base image has been changed.
+1. Submit the pull request. *Do not leave the pull request blank*. Explain exactly
+   what your changes are meant to do and provide simple steps on how to validate.
+   your changes. Ensure that you reference the issue you created as well.
+1. We will assign the pull request to 2-3 people for review before it is merged.
+
+## Code of conduct
+
+Follow the [Golden Rule](https://en.wikipedia.org/wiki/Golden_Rule). If you'd
+like more specific guidelines, see the [Contributor Covenant Code of Conduct][COC].
+
+[OCA]: https://oca.opensource.oracle.com
+[COC]: https://www.contributor-covenant.org/version/1/4/code-of-conduct/

SECURITY.md

@@ -0,0 +1,38 @@
+# Reporting security vulnerabilities
+
+Oracle values the independent security research community and believes that
+responsible disclosure of security vulnerabilities helps us ensure the security
+and privacy of all our users.
+
+Please do NOT raise a GitHub Issue to report a security vulnerability. If you
+believe you have found a security vulnerability, please submit a report to
+[[email protected]][1] preferably with a proof of concept. Please review
+some additional information on [how to report security vulnerabilities to Oracle][2].
+We encourage people who contact Oracle Security to use email encryption using
+[our encryption key][3].
+
+We ask that you do not use other channels or contact the project maintainers
+directly.
+
+Non-vulnerability related security issues including ideas for new or improved
+security features are welcome on GitHub Issues.
+
+## Security updates, alerts and bulletins
+
+Security updates will be released on a regular cadence. Many of our projects
+will typically release security fixes in conjunction with the
+Oracle Critical Patch Update program. Additional
+information, including past advisories, is available on our [security alerts][4]
+page.
+
+## Security-related information
+
+We will provide security related information such as a threat model, considerations
+for secure use, or any known security issues in our documentation. Please note
+that labs and sample code are intended to demonstrate a concept and may not be
+sufficiently hardened for production use.
+
+[1]: mailto:[email protected]
+[2]: https://www.oracle.com/corporate/security-practices/assurance/vulnerability/reporting.html
+[3]: https://www.oracle.com/security-alerts/encryptionkey.html
+[4]: https://www.oracle.com/security-alerts/

app-dev/devops-and-containers/oke/README.md

@@ -37,6 +37,10 @@ Reviewed: 20.12.2023
 - [How to deploy Ingress Nginx using Helm in OCI](https://medium.com/@ivan-delic/deploy-ingress-nginx-using-helm-in-oci-c3ff4d9d5450)
 - [Version Control Your Database in a Microservices Architecture](https://www.youtube.com/watch?v=qh9jppe_yNI)
 - [Kubernetes Service Operator for OCI Streaming — First steps](https://blogs.oracle.com/developers/post/using-oci-with-k8s)
+- [Disaster Recovery — Notes on Velero and OKE, Part 1: Stateless Pods](https://medium.com/oracledevs/disaster-recovery-notes-on-velero-and-oke-part-1-stateless-pods-b4ba3e737386)
+- [Disaster Recovery — Notes on Velero and OKE, Part 2: Stateful Pods with Persistent Volumes and Block Volume](https://medium.com/oracledevs/disaster-recovery-notes-on-velero-and-oke-part-2-stateful-pods-with-persistent-volumes-and-80204b3ac6d7)
+- [Disaster Recovery: Notes on Velero and OKE — part 3: Stateful Pods with Persistent Volumes and File Storage](https://medium.com/oracledevs/oke-disaster-recovery-notes-on-velero-and-oke-part-3-stateful-pods-with-persistent-volumes-and-a6eacef7600b)
+- [Test S3 Compatibility - Preparing Backups and DR for OKE and Velero](https://github.com/fharris/oci-s3-compatibility)
 
 
 # Useful Links

cloud-architecture/oracle-apps-erp/jde-migration/jde-migration-template-v1.pdf

@@ -1,9 +1,10 @@
 # DISCLAIMER
-This code is provided as a starting point for your own benchmarks or for adaptation to your specific needs. It is not production-ready, and may lack a testing strategy, requiring modifications to function properly.
 
+This code is provided as a starting point for your own benchmarks or for adaptation to your specific needs. It is not production-ready, and may lack a testing strategy, requiring modifications to function properly.
 
 # gds-benchmakrs
-```
+
+```bash
 [root@machine gds_benchmarks]# tree -L 2
 .
 ├── backups
@@ -34,12 +35,12 @@ The **'scripts'** directory contains all the bash scripts used for initializing
 
 During operation, **'launch.sh'** will conduct multiple tests using a variety of block and file sizes, which are predefined (Block sizes include: 4k, 8k, 16k, 32k, 64k, 128k, 256k, 512k, 1M, 2M, 4M, 8M, 16M). Each test iteration is performed four times. The file size varies depending on the number of threads, and to maintain efficiency, file sizes are kept relatively small. The GDSIO benchmark scales the file size with the number of threads, which can lead to extensive data processing. For example, running eight threads with a 128G file size would result in a total of 1024 TB of data being written, reflecting the scale of operations handled by this setup.
 
-
 Each test will be logged under the corresponding directory. The naming of the log files has the following format: ``gdsio_s<block size>_m<mode number>_w<threads / workers>_r<repetition number>_d<timestamp>.log``  
 gdsio_s1M_m2_w1_r1_d1671836744.log  
 For example, this log refers to a test that used 1M as block size, Mode 2 (CPU_GPU), 1 thread, and its timestamp.  
 Each log also contains the full command that was issued to run:  
-```
+
+```bash
 /usr/local/cuda/gds/tools/gdsio -D /mnt/nvme0/ -d 0 -w 1 -s 8G -x 2 -i 1M -I 1 -V >> /home/ubuntu/gds_benchmarks/scripts/../logs/CPU_GPU//gdsio_s1M_m2_w1_r1_d1671836744.log  
 IoType: WRITE XferType: CPU_GPU Threads: 1 DataSetSize: 8388608/8388608(KiB) IOSize: 1024(KiB) Throughput: 4.179353 GiB/sec, Avg_Latency: 233.618286 usecs ops: 8192 total_time 1.914172 secs  
 Verifying data  

cloud-architecture/oracle-apps-erp/jde-migration/jde-migration-template-v2.5.docx

@@ -1,28 +1,31 @@
 # AI infrastructure and GPU
 
-We are a team of technical specialists for AI infrastructure, graphics, and HPC on NVIDIA GPUs at OCI for
-- AI infrastructure for large-scale AI (Generative AI Large language model training, NLP) and small-scale AI (predictive AI, recommender systems, speech recognition, computer vision)
-- Computational Fluid Dynamics, Finite Element Analysis, Molecular Dynamics, Monte Carlo Simulations
-- Parallel File Systems (Weka, GlusterFS, BeeGFS, Lustre, IBM Spectrum Scale/GPFS)
-- Graphics (streaming, gaming, VDI)
-who support customers across various industries and geographies in EMEA (local support in 10 languages incl. German, French, Dutch, Italian & Spanish) with
-- Presentations
-- Demonstrations
-- PoCs/benchmarks
-- Architecture designs & sizing
-
-# Useful Links 
+We are a team of technical specialists for AI infrastructure, graphics, and HPC on NVIDIA GPUs at OCI for:
+
+    - AI infrastructure for large-scale AI (Generative AI Large language model training, NLP) and small-scale AI (predictive AI, recommender systems, speech recognition, computer vision)
+    - Computational Fluid Dynamics, Finite Element Analysis, Molecular Dynamics, Monte Carlo Simulations
+    - Parallel File Systems (Weka, GlusterFS, BeeGFS, Lustre, IBM Spectrum Scale/GPFS)
+    - Graphics (streaming, gaming, VDI)
+
+Who support customers across various industries and geographies in EMEA (local support in 10 languages incl. German, French, Dutch, Italian & Spanish) with:
+
+    - Presentations
+    - Demonstrations
+    - PoCs/benchmarks
+    - Architecture designs & sizing
+
+## Useful Links
 
 - [Oracle Cloud GPU Instances](https://www.oracle.com/uk/cloud/compute/gpu/)
     - High-level description of Oracle Cloud GPU offering
 - [Oracle Cloud AI Infrastructure](https://www.oracle.com/uk/ai-infrastructure/)
-    - High-level description of Oracle Cloud Artificial Intelligence infrastructure offering   
+    - High-level description of Oracle Cloud Artificial Intelligence infrastructure offering
 - [GPU instances details](https://docs.oracle.com/en-us/iaas/Content/Compute/References/computeshapes.htm#bm-gpu)
     - Oracle Cloud Bare-Metal GPU specifications
 - [AI infrastructure - Best practices on OCI](https://www.oracle.com/cloud/oci-best-practices-guide/#ai-infra-on-oci)
     - Guides, architectures, videos, and automation scripts to plan, design, and deploy AI workloads on our GPU compute and OCI services.
 
-# License
+## License
 
 Copyright (c) 2024 Oracle and/or its affiliates.
 

cloud-infrastructure/ai-infra-gpu/Benchmarks/gds-benchmarks/README.md

@@ -1,18 +1,18 @@
 # GPU Compute Instances
- 
+
 This repository contains detailed information related to Oracle Cloud Infrastructure GPU compute instances.
- 
-Reviewed: 26.02.20224
- 
+
+Reviewed: 26.02.2024
+
 # Table of Contents
- 
+
 1. [Team Publications](#team-publications)
 2. [Useful Links](#useful-links)
- 
+
 # Team Publications
- 
+
 ## Blog Posts
- 
+
 - [Oracle and UbiOps make your AI workloads land on OCI with NVIDIA GPUs](https://blogs.oracle.com/cloud-infrastructure/post/ubiops-ai-workloads-on-oci)
     - Deploy UbiOps on Oracle Cloud using Oracle Kubernetes Engines (OKE) and GPU instances
 - [A Deep Fake Example on Oracle Cloud Infrastructure](https://blogs.oracle.com/cloud-infrastructure/post/a-deepfake-example-on-oracle-cloud-infrastructure)
@@ -34,7 +34,7 @@ Reviewed: 26.02.20224
 
 - [Deploying NVIDIA NIM on OKE with model repository stored on Object Storage](https://docs.oracle.com/en/learn/deploy-nvidia-nim-on-oke/)
     - Step-by-step tutorial to run inference at scale using NVIDIA NIM.
- 
+
 ## LiveLabs
 
 - [Running Faceswap on OCI](https://apexapps.oracle.com/pls/apex/r/dbpm/livelabs/view-workshop?wid=798&session=4731494759204)
@@ -51,26 +51,25 @@ Reviewed: 26.02.20224
 
 - [Running AI on NVIDIA A10 GPUs in Oracle Cloud](https://www.youtube.com/watch?v=auvNHWoblIA)
     - How to run AI on NVIDIA A10 GPUs in Oracle Cloud
- 
- ## Re-useable Assets
+
+## Re-useable Assets
 
 - [Navigating the AI Revolution: Opportunities and Challenges - German - efcom Symposium 2023](https://www.youtube.com/watch?v=r_ZG2sUzhqo)
     - For all German speakers interested in hearing high-level about the foundations of GPU, what AI is (and how it is connected to Machine Learning, Data Science, LLM, GenAI), and how Oracle is approaching it.
 
 # Useful Links
- 
+
 - [NVIDIA H100 GPUs on Oracle Cloud](https://blogs.oracle.com/cloud-infrastructure/post/general-availability-oci-compute-nvidia-h100)
     - Announcing general availability for OCI Compute bare metal instances powered by NVIDIA H100 GPUs
 - [NVIDIA L40S GPUs on Oracle Cloud](https://blogs.oracle.com/cloud-infrastructure/post/announcing-oci-compute-nvidia-l40s-gpus)
-    - Announcing OCI Compute with NVIDIA L40S GPUs   
+    - Announcing OCI Compute with NVIDIA L40S GPUs
 - [Superclusters with RDMA](https://blogs.oracle.com/cloud-infrastructure/post/superclusters-rdma-high-performance)
-    - Deep dive explanation about Oracle Cloud-specific network for GPU workload at scale      
+    - Deep dive explanation about Oracle Cloud-specific network for GPU workload at scale
 
- 
 # License
- 
+
 Copyright (c) 2024 Oracle and/or its affiliates.
- 
+
 Licensed under the Universal Permissive License (UPL), Version 1.0.
- 
+
 See [LICENSE](https://github.com/oracle-devrel/technology-engineering/blob/main/LICENSE) for more details.