This should be the third last topic that I'd like to share related to my RHCE course, but my brain just hang there without any progress. So I proceed with SELinux and firewall first. I am still trying to understand the networking terms, teaming and bridge are 2 new words that I learned from RH Admin III course. Actually, I still don't quite understand what is the usage for these. When I setup VirtualBox for this series of sharings, I started to understand more for bridge... Anyway, let me stay focus on the topic (how-to). The Network Manager commands (nmcli) are rather easy to use, if you know what you are trying to do. Network teaming I did some hacks to make 2 available interfaces, enp0s8 and enp0s10. Next, create a team master. This team master will configured to activebackup setting, i.e. one port/link is used while other reserved as backup. Now create the team slaves (team ports). Use teamdctl to see the status of the teaming. This is provided in teamd pac
OMG! I can't believe that it's a year passed by, and I did not write up for the last 2 topics that I'd like to covered in RHCE! Those posts were prepared after I have finished and passed RHCE. Anyway, I am in preparation for another certification, CCSP. Thought of "document" my study notes in order to help me to organize my notes, and also help me to reinforce my understanding on the topics. I am going to start from Domain 2. D2 : Cloud Data Security M1 : Understand Cloud Data Life Cycle Process overview This table is to layout the possible access and allowed access by functions/actor/location. The access control requirement and design can be retrieved from this table. M2 : Understand Implication of Cloud to Enterprise Risk Risk management Risk framework Key roles associate with data management Data subject : individual who is the subject of personal data Data controller : person who determines the purpose and how to process personal data
I have always wanted to write about this for years. Like other old, stubborn developers, I hate process changes, and introduced to something I don't know or not familiar with. And these are not technical related to me, and I have no interest in it. Somehow, after we are forced to do this, and got familiarised with it, we started to enjoy it. We were proud of our team velocity acceleration too! I still can't differentiate or identify what scrum, agile, and bla bla bla is, but I think we did the estimation and planning right. It helps in our projects and sprints planning. You could visit Wiki's page on Planning Poker or continue to read this. I am no longer a developer, and the team dismissed long time ago. Anyway, for me to explain this easier, I will use present tense in the following. :) Our team consists of a Project Manager, a Product Owner, a Scrum Master, who is also the tech lead of the developers, 4 other developers and 2 QAs. It starts with the features o
Comments
Post a Comment