Why is it called automation?
-
@Pete-S said in Why is it called automation?:
@DustinB3403 said in Why is it called automation?:
@scottalanmiller said in Why is it called automation?:
@DustinB3403 said in Why is it called automation?:
I already made that argument with him when he said a car will automatically shift up or down. Which sure, if it has an automatic transmission and the driver of the vehicle accelerates or slows down.
But only in response to the driver giving input via the accelerator. If the human stops, the gears shift out and wait. It's not "fully automated" outside of a super limited scope that needs constant human interaction to keep automating. It's dramatically less automated than something like Salt that keeps being automated even after the human has left.
Absolutely, he provided the example, I was explaining how it requires human interaction to keep the car in 3rd.
No, the transmission is fully automated when it goes intro neutral if you break. It's not human interaction as it would do exactly the same if a robot pressed the break pedal. Or if a self-driving car would brake.
Salt is fully automated when it stops when state is achieved. But unlike the transmission, the human doesn't have to change the accelerator to put Salt into neutral, it detects the need for neutral on its own. Automated fully versus partially.
-
@Pete-S are you just trolling us right now?
This seems to be far to repetitive to not be you messing with us.
-
As already stated, no system in the world is 100% automated with out any input from the outside world.
If it were 100% automated, it would be sentient.
Sentience is completely different than being automated. You are sentient, a dog is sentient.
Most computer programs aren't even remotely sentient although that is changing with AI. And the sentience there is extremely limited.
-
@Pete-S
Salt, Bash, Python, PowerShell, Ansible, cron, task scheduler, etc... are all tools used to automate all the things.
I don't understand the confusion here.
-
Like with a car that's being driven down the road.
A brake can be applied, due to some outside factor. The driver wanting to slam on the brake and cause an accident or an AI sensing something that is obstructing the flow of traffic.
But in 1, the sentient HUMAN is saying, Screw this, and slams on the brake. In the other a program say STOP THE CAR.
The human understands that stopping the car on the road may cause a wreck, the AI may have an idea of how to avoid damage, but not that it would cause an wreck when it slams on the brake at 65 MPH.
-
-
I'm not messing with you guys, but I think I have to give up on you. :grinning_face_with_smiling_eyes:
I think you answered my question though. I just have to face the fact that automation means something else to you and that is why Ansible, Salt etc are considered to be automation tools.
In my world automation is something more but I realize I'm the odd one out.
-
@Pete-S said in Why is it called automation?:
I'm not messing with you guys, but I think I have to give up on you. :grinning_face_with_smiling_eyes:
I think you answered my question though. I just have to face the fact that automation means something else to you and that is why Ansible, Salt etc are considered to be automation tools.
In my world automation is something more but I realize I'm the odd one out.
In what world? In your world the first robots built them selves, the cars have always known how to drive and that the scripts are created from literally nothing.
You have to be messing with us.
-
@Pete-S said in Why is it called automation?:
I'm not messing with you guys, but I think I have to give up on you. :grinning_face_with_smiling_eyes:
I think you answered my question though. I just have to face the fact that automation means something else to you and that is why Ansible, Salt etc are considered to be automation tools.
In my world automation is something more but I realize I'm the odd one out.
No, everything you are describing as automation Salt does. It's not a difference in definition of automation. It's a difference in understanding of these tools. In every example you have given, Salt and Ansible automate MORE than you expect, not less. They are beyond your scope of automation, not falling short. You are just not realizing how much they automate and how totally automatic they are.
Your automation definitions aren't wrong, just your understanding of the automation completeness of the products.
-
@Obsolesce said in Why is it called automation?:
@Pete-S
Salt, Bash, Python, PowerShell, Ansible, cron, task scheduler, etc... are all tools used to automate all the things.
I don't understand the confusion here.
Exactly... automate all the things. Unlike the transmission or factory examples which just automate some of the things. Maybe they automate so much that it gets confusing?
-
There are awesome amount of information on YouTube from SaltStack
https://www.youtube.com/user/SaltStack/
