The Australian Oracle User Group, AUSOUG, have a focus on bringing together our Oracle community and servicing their core technical, development and applications needs. A balanced program is aimed at all levels of skill and experience within a forum of User led independent knowledge sharing.
The best Oracle blogs from thousands of blogs on the web ranked by traffic, social media followers, domain authority & freshness.
Happy to share that my blog has been choosen for another year as the Top 100 Blogs around the world, the list contains talened, experience and professional people 🎉🎉🎉
All-at-once deployments instantly shift traffic from the original (old) Lambda function to the updated (new) Lambda function, all at one time. All-at-once deployments can be beneficial when the speed of your deployments matters. In this strategy, the new version of your code is released quickly, and all your users get to access it immediately.
Canary
A linear deployment is similar to canary deployment. In this strategy, you direct a small amount of traffic to
In a canary deployment, you deploy your new version of your application code and shift a small percentage of production traffic to point to that new version. After you have validated that this version is safe and not causing errors, you direct all traffic to the new version of your code.
Linear
A linear deployment is similar to canary deployment. In this strategy, you direct a small amount of traffic to your new version of code at first. After a specified period of time, you automatically increment the amount of traffic that you send to the new version until you’re sending 100% of production traffic.
Comparing deployment strategies
To help you decide which deployment strategy to use for your application, you’ll need to consider each option’s consumer impact, rollback, event model factors, and deployment speed. The comparison table below illustrates these points.
Deployment
Consumer Impact
Rollback
Event Model Factors
Deployment Speed
All-at-once
All at once
Redeploy older version
Any event model at low concurrency rate
Immediate
Canary/ Linear
1-10% typical initial traffic shift, then phased
Revert 100% of traffic to previous deployment
Better for high-concurrency workloads
Minutes to hours
Deployment preferences with AWS SAM
Traffic shifting with aliases is directly integrated into AWS SAM. If you’d like to use all-at-once, canary, or linear deployments with your Lambda functions, you can embed that directly into your AWS SAM templates. You can do this in the deployment preferences section of the template. AWS CodeDeploy uses the deployment preferences section to manage the function rollout as part of the AWS CloudFormation stack update. SAM has several pre-built deployment preferences you can use to deploy your code. See the table below for examples.
Deployment Preferences Type
Description
Canary10Percent30Minutes
Shifts 10 percent of traffic in the first increment. The remaining 90 percent is deployed 30 minutes later.
Canary10Percent5Minutes
Shifts 10 percent of traffic in the first increment. The remaining 90 percent is deployed 5 minutes later.
Canary10Percent10Minutes
Shifts 10 percent of traffic in the first increment. The remaining 90 percent is deployed 10 minutes later.
Canary10Percent15Minutes
Shifts 10 percent of traffic in the first increment. The remaining 90 percent is deployed 15 minutes later.
Linear10PercentEvery10Minutes
Shifts 10 percent of traffic every 10 minutes until all traffic is shifted.
Linear10PercentEvery1Minute
Shifts 10 percent of traffic every minute until all traffic is shifted.
Linear10PercentEvery2Minutes
Shifts 10 percent of traffic every 2 minutes until all traffic is shifted.
Linear10PercentEvery3Minutes
Shifts 10 percent of traffic every 3 minutes until all traffic is shifted.
AllAtOnce
Shifts all traffic to the updated Lambda functions at once.
Creating a deployment pipeline
When you check a piece of code into source control, you don’t want to wait for a human to manually approve it or have each piece of code run through different quality checks. Using a CI/CD pipeline can help automate the steps required to release your software deployment and standardize on a core set of quality checks.
You need to develop and deploy a python app that writes a new file to S3 on every execution. These files need to be maintained only for 24h.
The content of the file is not important, but add the date and time as prefix for you files name.
The name of the buckets should be the following ones for QA and Staging respectively:
qa-FIRSTNAME-LASTNAME-platform-challenge
staging-FIRSTNAME-LASTNAME-platform-challenge
The app will be running as a docker container in a Kubernetes cluster every 5 minutes. There is a Namespace for QA and a different Namespace for Staging in the cluster. You don’t need to provide tests but you need to be sure the app will work.
Quest Oracle Community is home to 25,000+ users of JD Edwards, PeopleSoft, Oracle Cloud apps and Oracle Database products. We connect Oracle users to technology leaders and Oracle experts from companies who are driving innovation and leading through their use of Oracle products.
The Quest Oracle Community is dedicated to helping Oracle users develop skills and expand knowledge by connecting with other Oracle users and experts for education and networking.
Today some customer contact me complaining that they are trying to sync the development with UAT, when i check the issue everything was normal for the first time, but the alert logs indicate that database could complete the checkpoint.
so this what i did to make the import faster ( which i completed it as well ) :-
Change database to no archive mode.
increase sga_target temporary.
use parallel command depend on cpu core.
Use commit=N with import parameters.
you can exclude indexes by exclude=indexes but i don’t prefer this at all.
increase db_cache_size.
This simple steps that could help someone to make import little faster or solve hang issue.
I discussed before how to create package repository on Linux here, the same could be happened on Solaris 11.2 when you install Database any version mandatory packages should be installed to make it easy repository helps you a lot and will be available any time you need, and Image packaging system(IPS) repository is one of the important things in Solaris 11 onwards.
You need to download the following files & upload them to the server :-
Once the file is ready upload them to the server under one file called Repo for example. it should looks like the below :-
#ls -lrt total 14373947 -rwx—— 1 root root 1771800121 Aug 9 08:24 sol-11_2-repo-1of4.zip -rwx—— 1 root root 1889867782 Aug 9 11:20 sol-11_2-repo-2of4.zip -rwx—— 1 root root 1902167161 Aug 9 22:34 sol-11_2-repo-3of4.zip -rwx—— 1 root root 1790358735 Aug 10 00:16 sol-11_2-repo-4of4.zip -rwx—— 1 root root 5594 Aug 10 20:16 install-repo.ksh -rwx—— 1 root root 228 Aug 10 20:17 sol-11_2-repo-md5sums.txt drwxr-xr-x 2 root root 2 Aug 10 20:40 repo
as you see from the above output package publisher still working under oracle Link. Let’s Start Working, Set the executable bit for install-repo.ksh and execute like below.
#./install-repo.ksh -d /export/oracle/repo/ -v -c Comparing checksums of downloaded files…done. Checksums match. Uncompressing sol-11_2-repo-1of4.zip…done. Uncompressing sol-11_2-repo-2of4.zip…done. Uncompressing sol-11_2-repo-3of4.zip…done. Uncompressing sol-11_2-repo-4of4.zip…done. Repository can be found in /export/oracle/repo/. Initiating repository verification.