Thanks! This seems to have (mostly) worked...
Sadly, mostly is not enough - here's the attached message I get at the end of
the script...
Unfortunately it seems to have broken the master node in that it has become
unable to deploy anything now :(
GATHERING FACTS ***************************************************************
ok: [paas.intrinsic.world]
TASK: [Wait for master API to become available before proceeding] *************
skipping: [paas.intrinsic.world]
TASK: [openshift_manage_node | Wait for Node Registration] ********************
failed: [paas.intrinsic.world] => (item=apps.intrinsic.world) => {"attempts":
20, "changed": false, "cmd": ["oc", "get", "node", "apps.intrinsic.world"],
"delta": "0:00:00.080607", "end": "2016-02-22 15:27:34.288005", "failed": true,
"item": "apps.intrinsic.world", "rc": 1, "start": "2016-02-22 15:27:34.207398",
"stdout_lines": [], "warnings": []}
stderr: Error from server: the server has asked for the client to provide
credentials
msg: Task failed as maximum retries was encountered
failed: [paas.intrinsic.world] => (item=apps2.intrinsic.world) => {"attempts":
20, "changed": false, "cmd": ["oc", "get", "node", "apps2.intrinsic.world"],
"delta": "0:00:00.111236", "end": "2016-02-22 15:29:34.106358", "failed": true,
"item": "apps2.intrinsic.world", "rc": 1, "start": "2016-02-22
15:29:33.995122", "stdout_lines": [], "warnings": []}
stderr: Error from server: the server has asked for the client to provide
credentials
msg: Task failed as maximum retries was encountered
FATAL: all hosts have already failed -- aborting
PLAY RECAP ********************************************************************
to retry, use: --limit @/Users/candide/scaleup.retry
apps.intrinsic.world : ok=101 changed=9 unreachable=0 failed=0
apps2.intrinsic.world : ok=101 changed=15 unreachable=0 failed=0
localhost : ok=9 changed=0 unreachable=0 failed=0
paas.intrinsic.world : ok=12 changed=4 unreachable=0 failed=1
> On 20 Feb 2016, at 18:47, Brenton Leanhardt <[email protected]> wrote:
>
> On Sat, Feb 20, 2016 at 11:28 AM, Clayton Coleman <[email protected]
> <mailto:[email protected]>> wrote:
>> The ansible scripts should be reentrant (if you didn't change your
>> config files on disk after install), and adding a new node is just
>> adding the machine to the ansible inventory and rerunning.
>>
>
> There is a scaleup playbook specifically meant to handle this
> situation. We understand not everyone is managing all configuration
> in Ansible so the scaleup playbook manages to add the new node without
> modifying the configuration of any preexisting system.
>
> ./playbooks/byo/openshift-cluster/scaleup.yml
>
> If I remember correctly you create an inventory listing your masters
> and then the new nodes that you wish to install.
>
>> Pods today don't automatically reschedule once placed - there is a
>> feature planned in the future called the rebalancer that would do
>> that. However, if you trigger a rolling deployment all new pods are
>> created, so you should see your app be cleanly spread across the new
>> node and old node after deploying.
>>
>>> On Feb 20, 2016, at 10:55 AM, Candide Kemmler <[email protected]>
>>> wrote:
>>>
>>> I now have the 7 pods of my application running and easily deployable. Next
>>> is learning how to scale it. Being able to multiply pods is great but it
>>> doesn't help if you only have one low-performance machine to deploy them
>>> on. My provider (ovh) makes it super easy to add vps's with various cpu/ram
>>> characteristics.
>>>
>>> How can I turn them into nodes and make sure that pods are getting deployed
>>> to them?
>>>
>>> Is it possible to create a server, use ansible to turn it into a node and
>>> then decide exactly which pods will run on it?
>>>
>>>
>>> _______________________________________________
>>> users mailing list
>>> [email protected]
>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>> _______________________________________________
>> users mailing list
>> [email protected] <mailto:[email protected]>
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>> <http://lists.openshift.redhat.com/openshiftmm/listinfo/users>
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
