#4394 [easyfix] migrate fas server from puppet to ansible
Closed: Fixed None Opened 9 years ago by kevin.

The fas server application is in puppet. Migrate it over to ansible.

See:

puppet/modules/fas
puppet/manifests/nodes/fas*

Note that we have a fas_client ansible role already, this is for the fas_server instances and role.

and previous ansible migration tickets for more information.


Kevin could you have a look at the attachment and leave some comments. First I would like to create right ansible roles and then I will port the rest of puppet module. What did I miss, what do I add, are there any roles that are not needed, do I merge together some roles?

Looks pretty good overall. A few nitpicks:

Instead of making 'nobalance' a seperate role, how about using a variable like we do for the existing sundries nodes ( master_sundries_node: True on the machine doing the nobalance items) then you can just have it say "when: master_fas_node == True" and those steps will be skipped on other nodes.

I think we can just drop the devenv... thats fakefas01 and we will be dropping it someday soon.

Can you adjust and add info for fas01.stg also, and we can try it out by recreating fas01.stg. ;)

I added some new stuff and merged nobalance role with app. Would it be possible to join app with baseapp and have just one role?

Yes, sorry for the delay.

I think we can just merge add/baseapp into one thing. Would you like to do so? Or I can try...

I will do it. You will correct mistakes when this gets applied.

Kevin I merged app and baseapp. There are still some variables from puppet that are undefined in the patch at the moment. But I will leave that to you, because I don't know what to do. Otherwise I think this can be applied.

Sorry, I didn't get to this before beta freeze...

but I can apply soon in stg and get ready to roll out to production. ;) Thanks!

Login to comment on this ticket.

Metadata