Re: Hawkular Delete tenant

[John Sanda]

> On Jul 18, 2016, at 10:23 AM, Matt Wringe  wrote:
> 
> - Original Message -
>> From: "Diego Castro" 
>> To: "users" 
>> Sent: Monday, 18 July, 2016 9:27:33 AM
>> Subject: Hawkular Delete tenant
>> 
>> Hello, is there any way to delete a tenant and it's metrics programmatically?
> 
> Metrics have an expiry date and that is when they are removed from the system.
> 
> It is not currently possible to remove metrics programmatically.

Data expiration is the mechanism for purging metric data. I do recognize the 
need for tenant deletion. I have created 
https://issues.jboss.org/browse/HWKMETRICS-446 
 to track this.___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Atomic Centos, can't upgrade

[Philippe Lafoucrière]

We're using postgres 9.5.
It was working fine before the upgrade. Unfortunately, we upgraded atomic
AND Openshift at the same time, so I can't tell if it's a problem with
docker 1.10 or openshift 1.2.1.
I'd tend to say Docker 1.10, but we need to isolate this first.

Thanks,
Philippe
​
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Pending state

[Miloslav Vlach]

Hi,

what this mean ? I install the master + 2 nodes and I got this error
message ?

Jul 18 13:33:24 master origin-master: E0718 13:33:24.092596   17896
factory.go:355] Error scheduling default docker-registry-1-deploy: pod
(docker-registry-1-deploy) failed to fit in any node

Jul 18 13:33:24 master origin-master: fit failure on node (node2): Region

Jul 18 13:33:24 master origin-master: fit failure on node (node1):
MatchNodeSelector

Jul 18 13:33:24 master origin-master: ; retrying



what can I do ? It is something with bad label ?


Thanks Mila
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: OpenShift origin: internal routing with services

[aleks]

Am 14-07-2016 09:27, schrieb Den Cowboy:


Hi,

At the moment we have a setup like this:
project A
project B

project A contains a pod A which needs an API which is running in pod B 
in project B.

Pod A has an environment variable: "api-route.xxx.dev/api"
So when I'm going to that route in my browser I'm able to see the API 
and this works fine (okay we're able to configure https route etc)


But we'd like to keep everything internally. So without using routes. 
So thanks to the ovs-multitenant-pluging we're able to "join" the 
networks of our projects (namespaces). And I'm able to ping to from 
inside pod A to the service of my pod B in project B.

ping api-service.project-b
api-service.project-b.svc.cluster.local (172.30.xx.xx) 56(84) bytes of 
data.


So we're able to access the pod from its service without using an 
external route.
But like I told in the beginning. Our API is on api-route.xxx.dev/api 
so I have to go to something like 172.30.xx.xx:8080/api.


Is there a way to obtain this goal? So we try to connect to a 'subpath' 
of our service without using routes.

Is this possible?


I think  you can go another way and use a internal router with 
router-sharding


https://docs.openshift.org/latest/architecture/core_concepts/routes.html#router-sharding

and deploy the internal api on the internal router.

Best regards
Aleks

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Atomic Centos, can't upgrade

[Scott Dodson]

Sorry, wrong thread, disregard my reply.

On Mon, Jul 18, 2016 at 12:59 PM, Scott Dodson  wrote:
> We've worked around this change by checking for those booleans and
> setting each if they exist.
> https://github.com/openshift/openshift-ansible/pull/2166
>
> On Mon, Jul 18, 2016 at 12:56 PM, Josh Berkus  wrote:
>> On 07/15/2016 08:59 AM, Philippe Lafoucrière wrote:
>>> We're having a potential issue. One postgresql service is not starting
>>> on the beta cluster:
>>>
>>> FATAL:  could not open shared memory segment "/PostgreSQL.1804289383":
>>> Permission denied
>>>
>>> We need to investigate that, but it could be related to docker mounts
>>> (especially /dev/shm)
>>
>> This is due to a change in Docker, lemme see if I can find docs on it.
>> I know that Docker added constraints on dynamic shared memory at some point.
>>
>>
>> --
>> --
>> Josh Berkus
>> Project Atomic
>> Red Hat OSAS

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Atomic Centos, can't upgrade

[Josh Berkus]

On 07/18/2016 09:59 AM, Scott Dodson wrote:
> We've worked around this change by checking for those booleans and
> setting each if they exist.
> https://github.com/openshift/openshift-ansible/pull/2166

What version of Postgres is in this container?

-- 
--
Josh Berkus
Project Atomic
Red Hat OSAS

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Atomic Centos, can't upgrade

[Scott Dodson]

We've worked around this change by checking for those booleans and
setting each if they exist.
https://github.com/openshift/openshift-ansible/pull/2166

On Mon, Jul 18, 2016 at 12:56 PM, Josh Berkus  wrote:
> On 07/15/2016 08:59 AM, Philippe Lafoucrière wrote:
>> We're having a potential issue. One postgresql service is not starting
>> on the beta cluster:
>>
>> FATAL:  could not open shared memory segment "/PostgreSQL.1804289383":
>> Permission denied
>>
>> We need to investigate that, but it could be related to docker mounts
>> (especially /dev/shm)
>
> This is due to a change in Docker, lemme see if I can find docs on it.
> I know that Docker added constraints on dynamic shared memory at some point.
>
>
> --
> --
> Josh Berkus
> Project Atomic
> Red Hat OSAS

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: origin byo via ansible - etcd wrong IP

[Andrew Butcher]

What to the etcd urls look like in the master config created by ansible?
And to confirm, editing the etcd urls in the master config to contain "
https://10.2.2.10:2379; was the only change needed?

On Mon, Jul 18, 2016 at 12:30 PM, Miloslav Vlach 
wrote:

> [root@master origin]# hostname -f
>
> master
>
> [root@master origin]# ping master
>
> PING master (10.2.2.10) 56(84) bytes of data.
>
> 64 bytes from master (10.2.2.10): icmp_seq=1 ttl=64 time=0.028 ms
>
>
> Dne 18. července 2016 v 17:13:01, Jason DeTiberus (jdeti...@redhat.com)
> napsal/a:
>
>
>
> On Mon, Jul 18, 2016 at 11:10 AM, Andrew Butcher 
> wrote:
>
>>
>>
>> On Mon, Jul 18, 2016 at 11:02 AM, Jason DeTiberus 
>> wrote:
>>
>>>
>>>
>>> On Mon, Jul 18, 2016 at 10:51 AM, Miloslav Vlach <
>>> miloslav.vl...@rohlik.cz> wrote:
>>>
 Hi, I tried what you suggest but with no success. Maybe I don’t
 correctly write what I want.

 I can connect to master, node1, node2 - the installation process works
 good. The problem is that the IP address in master-config.yuml points to
 the wrong interface. Wrong IP address in config is 10.0.2.15 (NAT interface
 not accessible from other hosts) and the correct IP address is 10.2.2.10.

>>>
>>> Ah, my apologies. I misunderstood the issue originally. 'etcd_ip' should
>>> be the variable that you want to override to fix the issue.
>>>
>>
>> Setting openshift_ip is the correct way override it. I think the problem
>> may be that openshift_hostname should also be set in order to override the
>> etcd url in the master config.
>>
>
> Ah, thanks! I thought that was the case, but it's been a while since I
> looked through the etcd config code that I missed the translation.
>
>
>>
>> On the 10.2.2.10 host, what is the output of `hostname -f`?
>>
>>
>>> I don’t know how to specify the IP 10.2.2.10 for the etcd…

 Thanks Mila



 Dne 18. července 2016 v 16:33:41, Jason DeTiberus (jdeti...@redhat.com)
 napsal/a:

 If you are using ansible > 2.0, then you would set 'ansible_host' for
 each host. If using ansible < 2.0, then the variable is 'ansible_ssh_host'

 --
 Jason DeTiberus

 On Mon, Jul 18, 2016 at 10:12 AM, Miloslav Vlach <
 miloslav.vl...@rohlik.cz> wrote:

> Hi all,
>
> I would like to install one master and two nodes to my virtual box. I
> have problem with setting the primary IP address.
>
> All my VM have two interfaces: 10.0.2.15 (master NAT) and 10.2.2.10
> (host only).
>
> When I run the ansible-playbook I got error with etcd, which tries to
> connect to the 10.0.2.15. There is nothing. How can I setup the IP 
> address ?
>
> My inventory looks like this
>
> [masters]
>
> master openshift_ip=10.2.2.10 openshift_public_ip=10.2.2.10
>
>
> [etcd]
>
> master openshift_ip=10.2.2.10 openshift_public_ip=10.2.2.10
>
>
> [nodes]
>
> master openshift_node_labels="{'region': 'infra', 'zone': 'default'}" 
> openshift_ip=10.2.2.10
> openshift_public_ip=10.2.2.10
>
> node1 openshift_node_labels="{'region': 'primary', 'zone': 'default'}"
>  openshift_ip=10.2.2.11  openshift_public_ip=10.2.2.11
>
> node2 openshift_node_labels="{'region': 'primary', 'zone': 'default'}"
>  openshift_ip=10.2.2.12  openshift_public_ip=10.2.2.12
>
>
> When I manually change the master-config.yaml, the etched starts
> working. But I can’t do this by the ansible.
>
> etcdClientInfo:
>
>   ca: master.etcd-ca.crt
>
>   certFile: master.etcd-client.crt
>
>   keyFile: master.etcd-client.key
>
>   urls:
>
> - https://10.2.2.10:2379
>
>
>
> Thanks Mila
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>



>>>
>>>
>>> --
>>> Jason DeTiberus
>>>
>>> ___
>>> users mailing list
>>> users@lists.openshift.redhat.com
>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>>
>>>
>>
>
>
> --
> Jason DeTiberus
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: origin byo via ansible - etcd wrong IP

[Miloslav Vlach]

[root@master origin]# hostname -f

master

[root@master origin]# ping master

PING master (10.2.2.10) 56(84) bytes of data.

64 bytes from master (10.2.2.10): icmp_seq=1 ttl=64 time=0.028 ms


Dne 18. července 2016 v 17:13:01, Jason DeTiberus (jdeti...@redhat.com)
napsal/a:



On Mon, Jul 18, 2016 at 11:10 AM, Andrew Butcher 
wrote:

>
>
> On Mon, Jul 18, 2016 at 11:02 AM, Jason DeTiberus 
> wrote:
>
>>
>>
>> On Mon, Jul 18, 2016 at 10:51 AM, Miloslav Vlach <
>> miloslav.vl...@rohlik.cz> wrote:
>>
>>> Hi, I tried what you suggest but with no success. Maybe I don’t
>>> correctly write what I want.
>>>
>>> I can connect to master, node1, node2 - the installation process works
>>> good. The problem is that the IP address in master-config.yuml points to
>>> the wrong interface. Wrong IP address in config is 10.0.2.15 (NAT interface
>>> not accessible from other hosts) and the correct IP address is 10.2.2.10.
>>>
>>
>> Ah, my apologies. I misunderstood the issue originally. 'etcd_ip' should
>> be the variable that you want to override to fix the issue.
>>
>
> Setting openshift_ip is the correct way override it. I think the problem
> may be that openshift_hostname should also be set in order to override the
> etcd url in the master config.
>

Ah, thanks! I thought that was the case, but it's been a while since I
looked through the etcd config code that I missed the translation.


>
> On the 10.2.2.10 host, what is the output of `hostname -f`?
>
>
>> I don’t know how to specify the IP 10.2.2.10 for the etcd…
>>>
>>> Thanks Mila
>>>
>>>
>>>
>>> Dne 18. července 2016 v 16:33:41, Jason DeTiberus (jdeti...@redhat.com)
>>> napsal/a:
>>>
>>> If you are using ansible > 2.0, then you would set 'ansible_host' for
>>> each host. If using ansible < 2.0, then the variable is 'ansible_ssh_host'
>>>
>>> --
>>> Jason DeTiberus
>>>
>>> On Mon, Jul 18, 2016 at 10:12 AM, Miloslav Vlach <
>>> miloslav.vl...@rohlik.cz> wrote:
>>>
 Hi all,

 I would like to install one master and two nodes to my virtual box. I
 have problem with setting the primary IP address.

 All my VM have two interfaces: 10.0.2.15 (master NAT) and 10.2.2.10
 (host only).

 When I run the ansible-playbook I got error with etcd, which tries to
 connect to the 10.0.2.15. There is nothing. How can I setup the IP address 
 ?

 My inventory looks like this

 [masters]

 master openshift_ip=10.2.2.10 openshift_public_ip=10.2.2.10


 [etcd]

 master openshift_ip=10.2.2.10 openshift_public_ip=10.2.2.10


 [nodes]

 master openshift_node_labels="{'region': 'infra', 'zone': 'default'}" 
 openshift_ip=10.2.2.10
 openshift_public_ip=10.2.2.10

 node1 openshift_node_labels="{'region': 'primary', 'zone': 'default'}" 
 openshift_ip=10.2.2.11
 openshift_public_ip=10.2.2.11

 node2 openshift_node_labels="{'region': 'primary', 'zone': 'default'}" 
 openshift_ip=10.2.2.12
 openshift_public_ip=10.2.2.12


 When I manually change the master-config.yaml, the etched starts
 working. But I can’t do this by the ansible.

 etcdClientInfo:

   ca: master.etcd-ca.crt

   certFile: master.etcd-client.crt

   keyFile: master.etcd-client.key

   urls:

 - https://10.2.2.10:2379



 Thanks Mila


 ___
 users mailing list
 users@lists.openshift.redhat.com
 http://lists.openshift.redhat.com/openshiftmm/listinfo/users


>>>
>>>
>>>
>>
>>
>> --
>> Jason DeTiberus
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>>
>


--
Jason DeTiberus
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: origin byo via ansible - etcd wrong IP

[Jason DeTiberus]

On Mon, Jul 18, 2016 at 11:10 AM, Andrew Butcher 
wrote:

>
>
> On Mon, Jul 18, 2016 at 11:02 AM, Jason DeTiberus 
> wrote:
>
>>
>>
>> On Mon, Jul 18, 2016 at 10:51 AM, Miloslav Vlach <
>> miloslav.vl...@rohlik.cz> wrote:
>>
>>> Hi, I tried what you suggest but with no success. Maybe I don’t
>>> correctly write what I want.
>>>
>>> I can connect to master, node1, node2 - the installation process works
>>> good. The problem is that the IP address in master-config.yuml points to
>>> the wrong interface. Wrong IP address in config is 10.0.2.15 (NAT interface
>>> not accessible from other hosts) and the correct IP address is 10.2.2.10.
>>>
>>
>> Ah, my apologies. I misunderstood the issue originally. 'etcd_ip' should
>> be the variable that you want to override to fix the issue.
>>
>
> Setting openshift_ip is the correct way override it. I think the problem
> may be that openshift_hostname should also be set in order to override the
> etcd url in the master config.
>

Ah, thanks! I thought that was the case, but it's been a while since I
looked through the etcd config code that I missed the translation.


>
> On the 10.2.2.10 host, what is the output of `hostname -f`?
>
>
>> I don’t know how to specify the IP 10.2.2.10 for the etcd…
>>>
>>> Thanks Mila
>>>
>>>
>>>
>>> Dne 18. července 2016 v 16:33:41, Jason DeTiberus (jdeti...@redhat.com)
>>> napsal/a:
>>>
>>> If you are using ansible > 2.0, then you would set 'ansible_host' for
>>> each host. If using ansible < 2.0, then the variable is 'ansible_ssh_host'
>>>
>>> --
>>> Jason DeTiberus
>>>
>>> On Mon, Jul 18, 2016 at 10:12 AM, Miloslav Vlach <
>>> miloslav.vl...@rohlik.cz> wrote:
>>>
 Hi all,

 I would like to install one master and two nodes to my virtual box. I
 have problem with setting the primary IP address.

 All my VM have two interfaces: 10.0.2.15 (master NAT) and 10.2.2.10
 (host only).

 When I run the ansible-playbook I got error with etcd, which tries to
 connect to the 10.0.2.15. There is nothing. How can I setup the IP address 
 ?

 My inventory looks like this

 [masters]

 master openshift_ip=10.2.2.10 openshift_public_ip=10.2.2.10


 [etcd]

 master openshift_ip=10.2.2.10 openshift_public_ip=10.2.2.10


 [nodes]

 master openshift_node_labels="{'region': 'infra', 'zone': 'default'}" 
 openshift_ip=10.2.2.10
 openshift_public_ip=10.2.2.10

 node1 openshift_node_labels="{'region': 'primary', 'zone': 'default'}" 
 openshift_ip=10.2.2.11
 openshift_public_ip=10.2.2.11

 node2 openshift_node_labels="{'region': 'primary', 'zone': 'default'}" 
 openshift_ip=10.2.2.12
 openshift_public_ip=10.2.2.12


 When I manually change the master-config.yaml, the etched starts
 working. But I can’t do this by the ansible.

 etcdClientInfo:

   ca: master.etcd-ca.crt

   certFile: master.etcd-client.crt

   keyFile: master.etcd-client.key

   urls:

 - https://10.2.2.10:2379



 Thanks Mila


 ___
 users mailing list
 users@lists.openshift.redhat.com
 http://lists.openshift.redhat.com/openshiftmm/listinfo/users


>>>
>>>
>>>
>>
>>
>> --
>> Jason DeTiberus
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>>
>


-- 
Jason DeTiberus
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: origin byo via ansible - etcd wrong IP

[Jason DeTiberus]

On Mon, Jul 18, 2016 at 10:51 AM, Miloslav Vlach 
wrote:

> Hi, I tried what you suggest but with no success. Maybe I don’t correctly
> write what I want.
>
> I can connect to master, node1, node2 - the installation process works
> good. The problem is that the IP address in master-config.yuml points to
> the wrong interface. Wrong IP address in config is 10.0.2.15 (NAT interface
> not accessible from other hosts) and the correct IP address is 10.2.2.10.
>

Ah, my apologies. I misunderstood the issue originally. 'etcd_ip' should be
the variable that you want to override to fix the issue.


>
> I don’t know how to specify the IP 10.2.2.10 for the etcd…
>
> Thanks Mila
>
>
>
> Dne 18. července 2016 v 16:33:41, Jason DeTiberus (jdeti...@redhat.com)
> napsal/a:
>
> If you are using ansible > 2.0, then you would set 'ansible_host' for each
> host. If using ansible < 2.0, then the variable is 'ansible_ssh_host'
>
> --
> Jason DeTiberus
>
> On Mon, Jul 18, 2016 at 10:12 AM, Miloslav Vlach  > wrote:
>
>> Hi all,
>>
>> I would like to install one master and two nodes to my virtual box. I
>> have problem with setting the primary IP address.
>>
>> All my VM have two interfaces: 10.0.2.15 (master NAT) and 10.2.2.10 (host
>> only).
>>
>> When I run the ansible-playbook I got error with etcd, which tries to
>> connect to the 10.0.2.15. There is nothing. How can I setup the IP address ?
>>
>> My inventory looks like this
>>
>> [masters]
>>
>> master openshift_ip=10.2.2.10 openshift_public_ip=10.2.2.10
>>
>>
>> [etcd]
>>
>> master openshift_ip=10.2.2.10 openshift_public_ip=10.2.2.10
>>
>>
>> [nodes]
>>
>> master openshift_node_labels="{'region': 'infra', 'zone': 'default'}" 
>> openshift_ip=10.2.2.10
>> openshift_public_ip=10.2.2.10
>>
>> node1 openshift_node_labels="{'region': 'primary', 'zone': 'default'}" 
>> openshift_ip=10.2.2.11
>> openshift_public_ip=10.2.2.11
>>
>> node2 openshift_node_labels="{'region': 'primary', 'zone': 'default'}" 
>> openshift_ip=10.2.2.12
>> openshift_public_ip=10.2.2.12
>>
>>
>> When I manually change the master-config.yaml, the etched starts working.
>> But I can’t do this by the ansible.
>>
>> etcdClientInfo:
>>
>>   ca: master.etcd-ca.crt
>>
>>   certFile: master.etcd-client.crt
>>
>>   keyFile: master.etcd-client.key
>>
>>   urls:
>>
>> - https://10.2.2.10:2379
>>
>>
>>
>> Thanks Mila
>>
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>>
>
>
>


-- 
Jason DeTiberus
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: origin byo via ansible - etcd wrong IP

[Miloslav Vlach]

Hi, I tried what you suggest but with no success. Maybe I don’t correctly
write what I want.

I can connect to master, node1, node2 - the installation process works
good. The problem is that the IP address in master-config.yuml points to
the wrong interface. Wrong IP address in config is 10.0.2.15 (NAT interface
not accessible from other hosts) and the correct IP address is 10.2.2.10.

I don’t know how to specify the IP 10.2.2.10 for the etcd…

Thanks Mila



Dne 18. července 2016 v 16:33:41, Jason DeTiberus (jdeti...@redhat.com)
napsal/a:

If you are using ansible > 2.0, then you would set 'ansible_host' for each
host. If using ansible < 2.0, then the variable is 'ansible_ssh_host'

--
Jason DeTiberus

On Mon, Jul 18, 2016 at 10:12 AM, Miloslav Vlach 
wrote:

> Hi all,
>
> I would like to install one master and two nodes to my virtual box. I have
> problem with setting the primary IP address.
>
> All my VM have two interfaces: 10.0.2.15 (master NAT) and 10.2.2.10 (host
> only).
>
> When I run the ansible-playbook I got error with etcd, which tries to
> connect to the 10.0.2.15. There is nothing. How can I setup the IP address ?
>
> My inventory looks like this
>
> [masters]
>
> master openshift_ip=10.2.2.10 openshift_public_ip=10.2.2.10
>
>
> [etcd]
>
> master openshift_ip=10.2.2.10 openshift_public_ip=10.2.2.10
>
>
> [nodes]
>
> master openshift_node_labels="{'region': 'infra', 'zone': 'default'}" 
> openshift_ip=10.2.2.10
> openshift_public_ip=10.2.2.10
>
> node1 openshift_node_labels="{'region': 'primary', 'zone': 'default'}" 
> openshift_ip=10.2.2.11
> openshift_public_ip=10.2.2.11
>
> node2 openshift_node_labels="{'region': 'primary', 'zone': 'default'}" 
> openshift_ip=10.2.2.12
> openshift_public_ip=10.2.2.12
>
>
> When I manually change the master-config.yaml, the etched starts working.
> But I can’t do this by the ansible.
>
> etcdClientInfo:
>
>   ca: master.etcd-ca.crt
>
>   certFile: master.etcd-client.crt
>
>   keyFile: master.etcd-client.key
>
>   urls:
>
> - https://10.2.2.10:2379
>
>
>
> Thanks Mila
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: origin byo via ansible - etcd wrong IP

[Jason DeTiberus]

If you are using ansible > 2.0, then you would set 'ansible_host' for each
host. If using ansible < 2.0, then the variable is 'ansible_ssh_host'

--
Jason DeTiberus

On Mon, Jul 18, 2016 at 10:12 AM, Miloslav Vlach 
wrote:

> Hi all,
>
> I would like to install one master and two nodes to my virtual box. I have
> problem with setting the primary IP address.
>
> All my VM have two interfaces: 10.0.2.15 (master NAT) and 10.2.2.10 (host
> only).
>
> When I run the ansible-playbook I got error with etcd, which tries to
> connect to the 10.0.2.15. There is nothing. How can I setup the IP address ?
>
> My inventory looks like this
>
> [masters]
>
> master openshift_ip=10.2.2.10 openshift_public_ip=10.2.2.10
>
>
> [etcd]
>
> master openshift_ip=10.2.2.10 openshift_public_ip=10.2.2.10
>
>
> [nodes]
>
> master openshift_node_labels="{'region': 'infra', 'zone': 'default'}" 
> openshift_ip=10.2.2.10
> openshift_public_ip=10.2.2.10
>
> node1 openshift_node_labels="{'region': 'primary', 'zone': 'default'}" 
> openshift_ip=10.2.2.11
> openshift_public_ip=10.2.2.11
>
> node2 openshift_node_labels="{'region': 'primary', 'zone': 'default'}" 
> openshift_ip=10.2.2.12
> openshift_public_ip=10.2.2.12
>
>
> When I manually change the master-config.yaml, the etched starts working.
> But I can’t do this by the ansible.
>
> etcdClientInfo:
>
>   ca: master.etcd-ca.crt
>
>   certFile: master.etcd-client.crt
>
>   keyFile: master.etcd-client.key
>
>   urls:
>
> - https://10.2.2.10:2379
>
>
>
> Thanks Mila
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Hawkular Delete tenant

[Matt Wringe]

- Original Message -
> From: "Diego Castro" 
> To: "users" 
> Sent: Monday, 18 July, 2016 9:27:33 AM
> Subject: Hawkular Delete tenant
> 
> Hello, is there any way to delete a tenant and it's metrics programmatically?

Metrics have an expiry date and that is when they are removed from the system.

It is not currently possible to remove metrics programmatically.

> 
> ---
> Diego Castro / The CloudFather
> GetupCloud.com - Eliminamos a Gravidade
> 
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
> 

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

origin byo via ansible - etcd wrong IP

[Miloslav Vlach]

Hi all,

I would like to install one master and two nodes to my virtual box. I have
problem with setting the primary IP address.

All my VM have two interfaces: 10.0.2.15 (master NAT) and 10.2.2.10 (host
only).

When I run the ansible-playbook I got error with etcd, which tries to
connect to the 10.0.2.15. There is nothing. How can I setup the IP address ?

My inventory looks like this

[masters]

master openshift_ip=10.2.2.10 openshift_public_ip=10.2.2.10


[etcd]

master openshift_ip=10.2.2.10 openshift_public_ip=10.2.2.10


[nodes]

master openshift_node_labels="{'region': 'infra', 'zone': 'default'}"
openshift_ip=10.2.2.10
openshift_public_ip=10.2.2.10

node1 openshift_node_labels="{'region': 'primary', 'zone': 'default'}"
openshift_ip=10.2.2.11
openshift_public_ip=10.2.2.11

node2 openshift_node_labels="{'region': 'primary', 'zone': 'default'}"
openshift_ip=10.2.2.12
openshift_public_ip=10.2.2.12


When I manually change the master-config.yaml, the etched starts working.
But I can’t do this by the ansible.

etcdClientInfo:

  ca: master.etcd-ca.crt

  certFile: master.etcd-client.crt

  keyFile: master.etcd-client.key

  urls:

- https://10.2.2.10:2379



Thanks Mila
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Hawkular Delete tenant

[Diego Castro]

Hello, is there any way to delete a tenant and it's metrics
programmatically?

---
Diego Castro / The CloudFather
GetupCloud.com - Eliminamos a Gravidade
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

?????? help,how can be a user has the role "cluster admin"

[??????]

Jordan Liggitt,
So nice,Thank you!:) 
After run the command,it seems that the user "test" has got the role 
"cluster-admin ".Then I can go on.




--  --
??: "Jordan Liggitt";;
: 2016??7??18??(??) 10:57
??: "??"<459673...@qq.com>; 
: "Openshift Origin"; 
: Re: help,how can be a user has the role "cluster admin"



Did you already log in as user test? Only a cluster admin can give that role to 
another user, so you need to run that command as the bootstrap cluster admin 
user. The credentials for that user are in the admin.kubeconfig file on the API 
server.


oadm policy add-cluster-role-to-user cluster-admin test 
--config=/path/to/admin.kubeconfig







On Sun, Jul 17, 2016 at 9:41 PM, ?? <459673...@qq.com> wrote:
Hi,

Backgroud:
1.I install the Openshift Origin via the second method,"Method 2: Downloading 
the Binary"
2.Then I found that there is no Default Template in the cluster 
3.So I decide to install-config-imagestreams-templates[1].
4.But I found that I need to be the role "cluster-admin"
Question:
1.How to set a user to be the role "cluster admin"
2.What is command?
3.I have try the command "oadm policy add-cluster-role-to-user  
",but there is error in the CLI "Error from server: User "test" 
cannot get clusterpolicybindings at the cluster scope"[2]




[1]https://docs.openshift.org/latest/install_config/imagestreams_templates.html#install-config-imagestreams-templates
[2]

___
 users mailing list
 users@lists.openshift.redhat.com
 http://lists.openshift.redhat.com/openshiftmm/listinfo/users

6C455BF3@BC34CC51.FBA08C57
Description: Binary data
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users