David Brenner Jr's Random Things

Let's assume you've read all of VMware's recommended reference books on how to design a vSAN platform. You've designed the fabric of your vSAN for traffic management. You've calculated your vSAN's storage requirements for its Capacity Layer and its Cache Layer. What's next?  You can follow this simplified guide with only seven steps to get your vSAN working! Step #1 Assemble your servers with the correct ratios of disk drives to flash drives. Step #2 Configure the BIOS settings of your servers. Step #3 Install the ESXi software on your servers. ESXi will automatically configure itself based on the BIOS settings. Step #4 Check that the vSAN objects were setup correctly on your servers.   Step #5 Install the vCSA software on a server outside of your storage cluster, then configure your Organization, Primary Adapter, and Primary Virtual Switch. Step #6 Connect to your vCSA using your vSphere client to configure

For example components can be optimized for better performance through a compiler, inside an interpreter, or from the outside via the environment. Whereas services can only be optimized via the environment. Rarely does a service have a very low-level interface for tuning internals. Functions Threads Objects Components Services  Locality  Same Same Different Same Different Different Different  Environment  Same Same Same Same Different Different  Overhead  Max Min Min Min Max Distributed Max Distributed  Speed   Very Fast IPC   Very Fast IPC   Fast IPC   Slow IPC   Very Slow IPC   Optimization  Compiler Compiler Interpreter  Environment  Compiler Interpreter  Environment  Environment  Debugging  Min Long-term Short-term Long-term Long-term Long-term Do you have a suggestion about how to improve this blog? Let's talk about it. Contact me at David.Brenner.Jr@Gmail.com or 720-584-5229.

DevOps changes the traditional models of Software Development and IT Operations in a business. DevOps brings together Software Development and IT Operations as programmable infrastructure or infrastructure as code . DevOps is about managing the configuration of infrastructure using automation and programming via Agile, Continuous Integration and Continuous Delivery. Continuous Integration automates the building and testing of code in a test environment (that's an exact clone of the production environment) as changes are made to a version control system. Continuous Delivery controls the phases of Continuous Integration, and deploys new changes to the production environment. The CI/CD services of the infrastructure follow the client-server models of microservices architecture . Microservices require orchestration software to build and deploy distributed services hosted on virtualization platforms. Those distributed services use a centralized MQ/API for inter-service communica

Continuous Integration (CI) automates the building and testing of software in a test environment whenever a change is committed to a revision control system. CI performs QA testing of a change before adding it to the current working version. CI makes sure all development can be integrated into a build. CI Best Practices 1. Maintain a test environment that's a clone of the production environment. 2. Maintain a revision control system such as CVS, SVN or Git. 3. Automate the building of software and the documenting of code in the test environment. 4. Automate QA testing of a change then report that change to developers. 5. Commit changes regularly to avoid integration conflicts. 6. Monitor the revision control system for a commit then build the software before replacing the current working version. Do you have a suggestion about how to improve this blog? Let's talk about it. Contact me at David.Brenner.Jr@Gmail.com or 720-584-5229.

AppArmor learns the behaviors of applications through established access controls (for monitoring and reporting) and enforces application security policies. Security-Enhanced Linux (SELinux) uses rule-based policy enforcement to restrict the functionality of users and services. Grsecurity uses Linux Security Modules to enhance security of the Linux kernel. Features AppArmor SELinux Grsecurity Allow/Deny Policy Yes Yes Yes Hierarchical Domains Yes Yes Yes Object Types Yes Yes Yes Data Types No No No Account Management No Yes Yes Service Management No Yes Yes Network Management No* Yes Yes Access Control Lists Yes Yes Yes Role-Based Access Control Yes Yes Yes Security Context No Yes No Linux Kernel Module Yes Yes Yes Language No Yes Yes Unified Configuration Yes No No Doesn't Prohibit Other Applications & Tools Yes No No No Installation No No No Few Dependencies Yes No Yes