Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use some provisioning/automation software #42

Open
ForNeVeR opened this issue Feb 21, 2020 · 4 comments
Open

Use some provisioning/automation software #42

ForNeVeR opened this issue Feb 21, 2020 · 4 comments
Assignees

Comments

@ForNeVeR
Copy link
Member

Currently, most of our tasks are manual and error-prone. We should at least use some simple automation software. I think about Ansible, since it imposes no requirements for the host (I believe) and should work across all the platforms we use.

@Minoru, have you had a chance to try it somewhere?

@Minoru
Copy link
Member

Minoru commented Feb 21, 2020

Not in production. Still going through toy examples, running it against a local VM.

The best resources for learning so far are this page as a guide and the official docs as a reference.

@ForNeVeR ForNeVeR changed the title Use Ansible or some other automation software Use some other provisioning/automation software Feb 22, 2020
@ForNeVeR
Copy link
Member Author

ForNeVeR commented Feb 22, 2020

Ansible doesn't support Windows as control node, so it won't work.

I've aslo checked out Puppet and Salt, but they seem to enterprisey: both asked me to fill some crazy forms before I could download their clients.

Chef seems like the only remaining option, will investigate further.

@ForNeVeR
Copy link
Member Author

ForNeVeR commented May 6, 2020

Chef would work, it looks cross-platform enough. But, all out of a sudden, I don't like idea of managing a separate Ruby (or, for what matters, Python) environment specially for the purpose of module deployment.

My use case may be a bit unusual: I'll need this environment, probably, once or twice a year: a significant amount of time between invocations. It's likely that I'll significantly change my machines or environment between these periods, so pracically every time I'll run the client I'll need to tune my environment again (and for me managing renv/venv is rather unpleasant experience).

Also, the agent-less deployment for Chef requires some additional magic which couldn't be good.

@ForNeVeR
Copy link
Member Author

ForNeVeR commented May 6, 2020

So, I've decided I'll invent a bycicle, because why the hell not.

We'll have a good cross-platform deployment system that manages precisely the tasks we need in Codingteam and which is operable and environment-friendly for my machines and my use cases (since I'm currently the only operator for the stuff, it is important).

Stay tuned, ETA ~6 months.

@ForNeVeR ForNeVeR changed the title Use some other provisioning/automation software Use some provisioning/automation software May 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants