Creating workflow that automates testing and deployment. Key components are Docker, Git, Travis-CI and Elastic Beanstalk on AWS.
Purpose of creating workflows such as this is to make repetitive testing and deployments easy as possible, minimize use of time and possibility to human error. What could go wrong if software tests and go-live deployments are done by computers?
I wanted to create a better naming scheme than only serial number or generic “Mati’s Mac”. More convenient is to rename computers with their owner’s and computer model’s name. Why? Because when you’re looking reports from your deployments or what ever, you can tell straight away what you are dealing with.
I wanted to create a local admin user during our zerotouch macOS deployment in our Jamf environment. Problem was that i wanted to avoid admin user with generic password that employees might not change. So how to randomise password during zerotouch deployment?
Osana Tietoturvan hallinta-kurssia kuului suunnitella ja toteuttaa projekti, jonka aiheeksi valitsimme suojatut yhteydet ja varmenteet. Projekti tehtiin Ciscon Packet Tracer simulaattori ohjelmassa.Continue reading →
I thought that it would be important first step to plan the addressing scheme. I segmented every department in their own VLAN and every VLAN has it’s own host range. For getting known a little better with subnetting math, I didn’t assign easiest /24 bit masks for every subnet. For sake of complexity and training, subnets has /25, /26 or /30 bit long masks. Continue reading →