I have just no more idea were to look after… If your plugin uses it, make sure to call ! in some initializer When I now schedule a job on a Linunx machine, I get the following error: (stacktrace below) ops, we're sorry but something went wrong The Dynflow world was not initialized yet. With this i noticed that redis and dynflow-sidekiq was missing, so I installed it, added systemd services for and and edited the configuration. Then i just wanted to get the remote-execution-ssh part going first. I can provision ubuntu machines with an ansible user and a SSH-key. I have the Ansible-plugin installed in foreman and have a smart-proxy with the proxy-plugins, I am able to import roles. The next Important step for us is to get the ansible-plugin running. We are able to provision Linux and Windows machines on VMware and are quite happy with foreman so far. We have come quite far yet, we are able to install foreman, tftp, dhcp-server with smart proxy, control bind from smart proxy, and configure Foreman completly from ansible. We have quite good knowledge on ansible but not on puppet yet. We evaluate Foreman in our department since a few weeks ago, to better understand what is happening and how foreman works we decided to install Foreman from packages with ansible on our own. My Name is Fabian and I am relatively new to foreman, also I am an Ops-Guy and do not have very much experience with programming, especially not with ruby.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |