Zurich IBM Cloud Private Bootcamp

I was lucky in these days to meet good people at IBM Zurich,  I enjoyed tech sales overview about the state of the market and what IBM is doing to be in the market.

Only one word, containerize, containerize, containerize,containerize.... Containerize as much as possible everything.

Without this process you can't enjoy some IBM product in a cloud native way.

Now let's talk about bootcamp by Philippe Thomas from IBM France, roadmap was straightforward :
  • Introduction to IBM Cloud Private
  • Demonstration
  • Technical Overview
  • Installing IBM Cloud Private Lab
  • Using the Console
  • Docker Overview and Lab
  • Kubernetes Overview and Lab
  • Helm and Lab
  • Cloud Foundry
  • Application Patterns for ICP
  • MircroserviceBuilder Labs
  • Continuous Integration/Delivery & Lab
  • Monitoring and Demo
  • Cloud Automation Manager & Demo
  • Conclusion
At a first look could be a long list but you have all the information to start from zero and with the same material / labs you can also do the same in your company with your colleague, isn't beautiful !?!?

And this one of my favorite point about  this course, at the end of these two days you can share knowledge with your colleague and earn your badge from your company during daily work!

Here the link https://www.onlinedigitallearning.com/course/view.php?id=2315

Another cool point was, ok if you fail the installation don't worry you have a ready virtual machine to use, in this bootcamp all the aspect and situation are covered!

What I really missed was no mention about IKS ( IBM Kubernetes Services ) new cloud service avaiable on IBM Cloud.

Below link about slides deck and gitub course, enjoy!

Here link of slides deck https://ibm.ent.box.com/v/ICP2018PREZ
Here link of github course https://github.com/phthom/IBMCloudPrivate


Comments

Post a Comment

Popular posts from this blog

IBM and Red Hat long story, long love, now married!

Most of the people thinking about opensource they think in my perspective mostly to Red Hat and other company rather than IBM. IBM is really active in opensource for a long time, helped Apache Foundation , Eclipse Foudation collaborate with the Linux Foundation and Red Hat as well. I think I can create a different long post to describe how is active and how helped opensource in different way. We can analyze  this acquisition from different perspective, from Financial to  Development. My personal point of view ( from a Cloud Architect ) most of the application around the world in banking, assurance and not only are java based, think about java in cloud in the past Year could be hard. Right now we can talk about java in the cloud with opensource project like OpenJ9 and OpenLiberty and the community behind. If you think about moving from on premise to cloud or from monolitch to microservice you can't say " well it's time to rework " because you are throwing years o
Read more

MY EXPERIENCE @ HYBRID CLOUD SUMMIT IN ZURICH

Image
I can simply say “it was a great experience” and based on the audience probably people can trust me, but let's go deeper into the event. My favorite part of the event was the panel session with cloud discussions and question answer about slides and example presented during the session. Based on discussion the most relevant general questions are: Adoption: best practices on adopting cloud technologies Development: how to develop cloud applications in the right way and how we can enable fresh people into this great world IBM and Forrester gave a lot of answers because there are different aspects and factors we need to cover when we talk about cloud development and adoption, let me share some of these: Security: 12 factor principle is the main manifesto to follow Digital Experience: in cloud you need to create applications user centric Performance: in cloud you need to give best experience to the end user in every part of the world Microservice: rework of the legacy
Read more

Kubernetes Persistent Volumes and Claims

In a distrubuted system, storage isn't simple to manage without a good abstraction, kubernetes offer an object called persistent volume to let pod to reclaim storage for persisting data. In the pod definition you can define your volume type with another object called persistentVolumeClaim where you can define type size and many other things. There are different phase in the persistent storage lifecycle: Provisioning : when an administrator create a Persistent Volume or a cloud resource dynamically request Binding : when a PVC is created  k8s control loop watch if there are Persisten Volume matching the PVC  and bind them together. Use : when the bound volume is mounted in to the pod Releasing : whene the POD is done and an API request is sent to delete the related bound PVC, the volume in this stage remains Reclaim : there are three options related to this state: - Retain:  keep data interact and allow an administrato to handle data from storage - Delete:  tells the volume
Read more