Re: cluster up - reuse registry address

[Lionel Orellana]

I guess what I need is a way to configure the proxy as per
https://docs.openshift.org/latest/install_config/http_proxies.html#configuring-hosts-for-proxies

On Tue, 9 Aug 2016 at 10:05 AM, Lionel Orellana  wrote:

> It's been difficult to get a functional poc going with oc cluster up
> behind a proxy.
>
> I need to maintain the registry's address so I can add it to the no_proxy
> variable of the docker deamon. Clayton's procedure works for reusing the
> address . I will try --use-existing-config.
>
> But I also need to add the registry's internal address (which always seems
> to be initially set to 172.17.0.4) to the no_proxy variable of the cluster
> up command itself. Otherwise the health checks try to go through the proxy
> and fail.
>
> When I recreate the registry (in order to set a known service ip) the pod
> ip changes and the health checks start to fail again.
>
> Obviously I am making this harder than it should be. But I just can't get
> the right combination to run a cluster behind a proxy where I can login to
> the registry (docker login). Maybe I should have said that's what I'm
> trying to do from the beginning.
>
> Cheers
>
>
> Lionel.
>
> On Tue, 9 Aug 2016 at 1:16 AM, Clayton Coleman 
> wrote:
>
>> Generally deep configuration is not the goal of oc cluster up - that's
>> more the Ansible installs responsibility.  oc cluster up is about getting a
>> running cluster up for test / dev as quickly as possible, but we don't want
>> to add fine grained tuning to it.
>>
>> On Mon, Aug 8, 2016 at 10:49 AM, Cesar Wong  wrote:
>>
>>> Hi Lionel,
>>>
>>> You can always reuse the same data/config dirs and keep your service ips:
>>>
>>> oc cluster up --host-data-dir=blah --host-config-dir=blah
>>> --use-existing-config
>>>
>>> On Aug 7, 2016, at 9:17 PM, Lionel Orellana  wrote:
>>>
>>> Thanks Clayton.
>>>
>>> Would be nice to have a way of setting the address when using cluster up
>>> though.
>>> On Mon, 8 Aug 2016 at 11:03 AM, Clayton Coleman 
>>> wrote:
>>>
 When you create the registry you can specify the service IP that is
 assigned (as long as another service hasn't claimed it).

 $ oadm registry -o yaml > registry.yaml
 $ vi registry.yaml
 # Set the registry service `spec.clusterIP` field to a valid
 service IP (must be within the service CIDR, typically 172.30.0.0/16)
 $ oc create -f registry.yaml


 On Sun, Aug 7, 2016 at 8:55 PM, Lionel Orellana 
 wrote:

> Hi
>
> I'm facing a similar problem to this:
> https://github.com/openshift/origin/issues/7879
>
> Basically I need to configure the NO_PROXY variable of the Docker
> deamon to include the registry address. Problem is with cluster up I can't
> control the ip address that will be assigned to the registry. Or at least 
> I
> can't find a way to do it. Is there an option that I'm not seeing?
>
> Thanks
>
> Lionel.
>
> ___
> 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
>>>
>>>
>>>
>>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: cluster up - reuse registry address

[Lionel Orellana]

It's been difficult to get a functional poc going with oc cluster up behind
a proxy.

I need to maintain the registry's address so I can add it to the no_proxy
variable of the docker deamon. Clayton's procedure works for reusing the
address . I will try --use-existing-config.

But I also need to add the registry's internal address (which always seems
to be initially set to 172.17.0.4) to the no_proxy variable of the cluster
up command itself. Otherwise the health checks try to go through the proxy
and fail.

When I recreate the registry (in order to set a known service ip) the pod
ip changes and the health checks start to fail again.

Obviously I am making this harder than it should be. But I just can't get
the right combination to run a cluster behind a proxy where I can login to
the registry (docker login). Maybe I should have said that's what I'm
trying to do from the beginning.

Cheers

Lionel.

On Tue, 9 Aug 2016 at 1:16 AM, Clayton Coleman  wrote:

> Generally deep configuration is not the goal of oc cluster up - that's
> more the Ansible installs responsibility.  oc cluster up is about getting a
> running cluster up for test / dev as quickly as possible, but we don't want
> to add fine grained tuning to it.
>
> On Mon, Aug 8, 2016 at 10:49 AM, Cesar Wong  wrote:
>
>> Hi Lionel,
>>
>> You can always reuse the same data/config dirs and keep your service ips:
>>
>> oc cluster up --host-data-dir=blah --host-config-dir=blah
>> --use-existing-config
>>
>> On Aug 7, 2016, at 9:17 PM, Lionel Orellana  wrote:
>>
>> Thanks Clayton.
>>
>> Would be nice to have a way of setting the address when using cluster up
>> though.
>> On Mon, 8 Aug 2016 at 11:03 AM, Clayton Coleman 
>> wrote:
>>
>>> When you create the registry you can specify the service IP that is
>>> assigned (as long as another service hasn't claimed it).
>>>
>>> $ oadm registry -o yaml > registry.yaml
>>> $ vi registry.yaml
>>> # Set the registry service `spec.clusterIP` field to a valid service
>>> IP (must be within the service CIDR, typically 172.30.0.0/16)
>>> $ oc create -f registry.yaml
>>>
>>>
>>> On Sun, Aug 7, 2016 at 8:55 PM, Lionel Orellana 
>>> wrote:
>>>
 Hi

 I'm facing a similar problem to this:
 https://github.com/openshift/origin/issues/7879

 Basically I need to configure the NO_PROXY variable of the Docker
 deamon to include the registry address. Problem is with cluster up I can't
 control the ip address that will be assigned to the registry. Or at least I
 can't find a way to do it. Is there an option that I'm not seeing?

 Thanks

 Lionel.

 ___
 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
>>
>>
>>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Recreate strategy optimization

[Clayton Coleman]

That's not possible today, although in the future I could imagine
support for that.  There would have to be some gating factor that
prevents pod startup which is not yet possible.

You *can* pre-seed a cluster with images by creating a daemon set in
your prestart deployment hook that contains the image, then wait until
enough pods have started to continue.  The scheduler would then prefer
those nodes because your image is already pulled.

> On Aug 8, 2016, at 4:52 PM, Philippe Lafoucrière 
>  wrote:
>
> Hi,
>
> I have noticed something that could be optimized in recreate strategy: During 
> a deploy, Openshift will set the current running replicas to zero, and then 
> pull the new image, and eventually starts it.
> The problem is, sometimes, the pull can very (very) long, and during that 
> period, the pods are unavailable. I would be more efficient to start pulling 
> the image, and IF the image is pulled successfully, start to touch replicas.
> What do you think?
>
> Thanks,
> Philippe
> ___
> 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

Recreate strategy optimization

[Philippe Lafoucrière]

Hi,

I have noticed something that could be optimized in recreate strategy:
During a deploy, Openshift will set the current running replicas to zero,
and then pull the new image, and eventually starts it.
The problem is, sometimes, the pull can very (very) long, and during that
period, the pods are unavailable. I would be more efficient to start
pulling the image, and IF the image is pulled successfully, start to touch
replicas.
What do you think?

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

Re: Using a Jenkins Slave in openshift

[Ben Parees]

The sample defines a buildconfig which ultimately uses this directory as
the context for a docker build:
https://github.com/siamaksade/jenkins-s2i-example/tree/master/slave

it does that by pointing the buildconfig to this repo:
https://github.com/siamaksade/jenkins-s2i-example

and the context directory named "slave" within that repo:
https://github.com/siamaksade/jenkins-s2i-example/tree/master/slave

which you can see defined here:
https://github.com/siamaksade/jenkins-s2i-example/blob/master/jenkins-slave-builder-template.yaml#L36-L40

https://github.com/siamaksade/jenkins-s2i-example/blob/master/jenkins-slave-builder-template.yaml#L61-L68

If you are trying to build your own slave image, you need to point to a
repo (and optionally a contextdir within that repo) that contains an
appropriate Dockerfile, as the example does.



On Mon, Aug 8, 2016 at 2:43 PM, Akshaya Khare 
wrote:

> Hi Ben,
>
> So after making changes to the imagestream, I wasn't able to get the build
> running initially.
> But that was because already there were failed builds and buildconfigs
> which were preventing the build to run successfully.
>
> Once I deleted the old failed builds, I was able to get the new build
> running, but it failed once I tried running my Jenkins job.
> I gave my github repository as the repository url for the build, and this
> is the log i get for the failed pod:
>
>
>
>
>
>
>
>
>
>
>
>
> *I0808 14:06:51.779594   1 source.go:96] git ls-remote
> https://github.com/akshayakhare/ims/ 
> --headsI0808 14:06:51.779659   1 repository.go:275] Executing git
> ls-remote https://github.com/akshayakhare/ims/
>  --headsI0808 14:07:06.989568   1
> source.go:189] Cloning source from https://github.com/akshayakhare/ims/
> I0808 14:07:06.989649   1
> repository.go:275] Executing git clone --recursive
> https://github.com/akshayakhare/ims/ 
> /tmp/docker-build543901321...I0808 14:07:35.174676   1
> repository.go:300] Out: Merge pull request #28 from
> chemistry-sourabh/LoggingI0808 14:07:35.174708   1 common.go:78]
> Setting build revision to
> &api.GitSourceRevision{Commit:"79ed71a8470c973c6f6cad380657c2df93948345",
> Author:api.SourceControlUser{Name:"Akshaya Khare",
> Email:"akshayakh...@gmail.com "},
> Committer:api.SourceControlUser{Name:"GitHub", Email:"nore...@github.com
> "}, Message:"Merge pull request #28 from
> chemistry-sourabh/Logging"}F0808 14:07:35.200435   1 builder.go:185]
> Error: build error: open /tmp/docker-build543901321/Dockerfile: no such
> file or directory*
> Do i need to create a docker file in my repository to run successfully?
> You mentioned that the sample git given in the blog uses a "slave" sub
> directory, will I have to create a similar structure in my repository?
>
> Looking at the sample Docker file given in the blog below, makes me
> believe that it copies the workspace from the current image to its own
> container and then runs it:
> https://github.com/siamaksade/jenkins-s2i-example/blob/
> master/slave/Dockerfile
>
> Is my understanding correct?
>
>
> On Fri, Aug 5, 2016 at 4:39 PM, Ben Parees  wrote:
>
>> You'll need to define the imagestream you've got the build pushing to,
>> the sample does that here:
>> https://github.com/siamaksade/jenkins-s2i-example/blob/maste
>> r/jenkins-slave-builder-template.yaml#L12-L21
>>
>> you'll need to name the imagestream "jdk8-jenkins-slave" in your case.
>>
>>
>> On Fri, Aug 5, 2016 at 4:06 PM, Akshaya Khare 
>> wrote:
>>
>>> I've attached the buildconfig, and the project name is "jenkinstin2"...
>>>
>>> On Fri, Aug 5, 2016 at 2:38 PM, Ben Parees  wrote:
>>>


 On Fri, Aug 5, 2016 at 2:28 PM, Akshaya Khare 
 wrote:

> Hi,
>
> I have a project configured in jenkins container(thanks to Ben Parees
> for suggesting s2i, it works like a charm) running on openshiift which I
> need to test every time there is a pull request from github.
>
> And we are planning to run those test cases on a separate node, since
> the environment is ideal for testing.
> I was following this blog by Siamak Sadeghianfar which seems to do
> exactly the thing which I'm expecting it to do.
>
> https://blog.openshift.com/openshift-3-2-jenkins-s2i-slave-pods/
>
> Now whenever I try creating the slave image from the UI, I get an
> error saying:
>
>
>
>
> *"build failed 44 hours ago - 29d91a3: added metadata to Dockerfile
> (Siamak Sadeghianfar  >)""bc/jenkins is pushing to
> imagestreamtag/jenkins:latest that is using is/jenkins, but that image
> stream does not exist"*
>

 ​can you share your buildconfig definition (json or yaml) and the name
 of the project you've defined it in?

 ​


>
> I can see the docker image :->* :5000/jenkinstin2/jenkins 
>>>

Re: Using a Jenkins Slave in openshift

[Akshaya Khare]

Hi Ben,

So after making changes to the imagestream, I wasn't able to get the build
running initially.
But that was because already there were failed builds and buildconfigs
which were preventing the build to run successfully.

Once I deleted the old failed builds, I was able to get the new build
running, but it failed once I tried running my Jenkins job.
I gave my github repository as the repository url for the build, and this
is the log i get for the failed pod:












*I0808 14:06:51.779594   1 source.go:96] git ls-remote
https://github.com/akshayakhare/ims/ 
--headsI0808 14:06:51.779659   1 repository.go:275] Executing git
ls-remote https://github.com/akshayakhare/ims/
 --headsI0808 14:07:06.989568   1
source.go:189] Cloning source from https://github.com/akshayakhare/ims/
I0808 14:07:06.989649   1
repository.go:275] Executing git clone --recursive
https://github.com/akshayakhare/ims/ 
/tmp/docker-build543901321...I0808 14:07:35.174676   1
repository.go:300] Out: Merge pull request #28 from
chemistry-sourabh/LoggingI0808 14:07:35.174708   1 common.go:78]
Setting build revision to
&api.GitSourceRevision{Commit:"79ed71a8470c973c6f6cad380657c2df93948345",
Author:api.SourceControlUser{Name:"Akshaya Khare",
Email:"akshayakh...@gmail.com "},
Committer:api.SourceControlUser{Name:"GitHub", Email:"nore...@github.com
"}, Message:"Merge pull request #28 from
chemistry-sourabh/Logging"}F0808 14:07:35.200435   1 builder.go:185]
Error: build error: open /tmp/docker-build543901321/Dockerfile: no such
file or directory*
Do i need to create a docker file in my repository to run successfully?
You mentioned that the sample git given in the blog uses a "slave" sub
directory, will I have to create a similar structure in my repository?

Looking at the sample Docker file given in the blog below, makes me believe
that it copies the workspace from the current image to its own container
and then runs it:
https://github.com/siamaksade/jenkins-s2i-example/blob/master/slave/Dockerfile

Is my understanding correct?


On Fri, Aug 5, 2016 at 4:39 PM, Ben Parees  wrote:

> You'll need to define the imagestream you've got the build pushing to, the
> sample does that here:
> https://github.com/siamaksade/jenkins-s2i-example/blob/
> master/jenkins-slave-builder-template.yaml#L12-L21
>
> you'll need to name the imagestream "jdk8-jenkins-slave" in your case.
>
>
> On Fri, Aug 5, 2016 at 4:06 PM, Akshaya Khare 
> wrote:
>
>> I've attached the buildconfig, and the project name is "jenkinstin2"...
>>
>> On Fri, Aug 5, 2016 at 2:38 PM, Ben Parees  wrote:
>>
>>>
>>>
>>> On Fri, Aug 5, 2016 at 2:28 PM, Akshaya Khare 
>>> wrote:
>>>
 Hi,

 I have a project configured in jenkins container(thanks to Ben Parees
 for suggesting s2i, it works like a charm) running on openshiift which I
 need to test every time there is a pull request from github.

 And we are planning to run those test cases on a separate node, since
 the environment is ideal for testing.
 I was following this blog by Siamak Sadeghianfar which seems to do
 exactly the thing which I'm expecting it to do.

 https://blog.openshift.com/openshift-3-2-jenkins-s2i-slave-pods/

 Now whenever I try creating the slave image from the UI, I get an error
 saying:




 *"build failed 44 hours ago - 29d91a3: added metadata to Dockerfile
 (Siamak Sadeghianfar >>> >)""bc/jenkins is pushing to
 imagestreamtag/jenkins:latest that is using is/jenkins, but that image
 stream does not exist"*

>>>
>>> ​can you share your buildconfig definition (json or yaml) and the name
>>> of the project you've defined it in?
>>>
>>> ​
>>>
>>>

 I can see the docker image :->* :5000/jenkinstin2/jenkins 
 *without
 any tags.

 What have I messed up here?

 And what should be the repository URL for this jenkins-slave-builder, I
 tried giving my github project url and also the sample
 jenkins-s2i-example.git url, both end up giving the same error.

>>>
>>> ​the repository the buildconfig references?  depends what you want to
>>> build, but it doesn't sound like that is your current issue.​
>>>
>>> the example i think you're following uses this repository as the source
>>> repo input for the slave image build:
>>>
>>> https://github.com/siamaksade/jenkins-s2i-example.git
>>>
>>> but it uses a context subdirectory of "slave".
>>>
>>> you can see the build config definition (and relevant parameters) here:
>>> https://raw.githubusercontent.com/siamaksade/jenkins-s2i-example/master/jenkins-slave-builder-template.yaml
>>>
>>>
>>>
>>>
>>>

 Also I got the master image running, but apparently the configuration
 *doesn't* have the one field it certainly needs to have...

 *Restrict where this p

Re: API client / library / javascript

[Clayton Coleman]

That's a bug then - because -n namespace should override the file on disk.

On Mon, Aug 8, 2016 at 1:59 PM, Tobias Florek  wrote:

> Hi!
>
> > > Can "oc" client be called that when we implement shell call to oc
> > Yes, `-o yaml` and `-o json` from most calls.
>
> With one major drawback!
>
> In a container on openshift/kubernetes, oc will always assume the
> namespace the container is running in, with no way of overriding. This
> is due to /run/secrets/kubernetes.io/serviceaccount/namespace.
>
> Cheers,
>  Tobias Florek
>
> ___
> 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: API client / library / javascript

[Tobias Florek]

Hi!

> > Can "oc" client be called that when we implement shell call to oc
> Yes, `-o yaml` and `-o json` from most calls.

With one major drawback!

In a container on openshift/kubernetes, oc will always assume the
namespace the container is running in, with no way of overriding. This
is due to /run/secrets/kubernetes.io/serviceaccount/namespace.

Cheers,
 Tobias Florek

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

Re: cluster up - reuse registry address

[Clayton Coleman]

Generally deep configuration is not the goal of oc cluster up - that's more
the Ansible installs responsibility.  oc cluster up is about getting a
running cluster up for test / dev as quickly as possible, but we don't want
to add fine grained tuning to it.

On Mon, Aug 8, 2016 at 10:49 AM, Cesar Wong  wrote:

> Hi Lionel,
>
> You can always reuse the same data/config dirs and keep your service ips:
>
> oc cluster up --host-data-dir=blah --host-config-dir=blah
> --use-existing-config
>
> On Aug 7, 2016, at 9:17 PM, Lionel Orellana  wrote:
>
> Thanks Clayton.
>
> Would be nice to have a way of setting the address when using cluster up
> though.
> On Mon, 8 Aug 2016 at 11:03 AM, Clayton Coleman 
> wrote:
>
>> When you create the registry you can specify the service IP that is
>> assigned (as long as another service hasn't claimed it).
>>
>> $ oadm registry -o yaml > registry.yaml
>> $ vi registry.yaml
>> # Set the registry service `spec.clusterIP` field to a valid service
>> IP (must be within the service CIDR, typically 172.30.0.0/16)
>> $ oc create -f registry.yaml
>>
>>
>> On Sun, Aug 7, 2016 at 8:55 PM, Lionel Orellana 
>> wrote:
>>
>>> Hi
>>>
>>> I'm facing a similar problem to this: https://github.com/openshift/
>>> origin/issues/7879
>>>
>>> Basically I need to configure the NO_PROXY variable of the Docker deamon
>>> to include the registry address. Problem is with cluster up I can't control
>>> the ip address that will be assigned to the registry. Or at least I can't
>>> find a way to do it. Is there an option that I'm not seeing?
>>>
>>> Thanks
>>>
>>> Lionel.
>>>
>>> ___
>>> 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
>
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: cluster up - reuse registry address

[Cesar Wong]

Hi Lionel,

You can always reuse the same data/config dirs and keep your service ips:

oc cluster up --host-data-dir=blah --host-config-dir=blah --use-existing-config

> On Aug 7, 2016, at 9:17 PM, Lionel Orellana  wrote:
> 
> Thanks Clayton. 
> 
> Would be nice to have a way of setting the address when using cluster up 
> though.
> On Mon, 8 Aug 2016 at 11:03 AM, Clayton Coleman  > wrote:
> When you create the registry you can specify the service IP that is assigned 
> (as long as another service hasn't claimed it).
> 
> $ oadm registry -o yaml > registry.yaml
> $ vi registry.yaml
> # Set the registry service `spec.clusterIP` field to a valid service IP 
> (must be within the service CIDR, typically 172.30.0.0/16 
> )
> $ oc create -f registry.yaml
> 
> 
> On Sun, Aug 7, 2016 at 8:55 PM, Lionel Orellana  > wrote:
> Hi
> 
> I'm facing a similar problem to this: 
> https://github.com/openshift/origin/issues/7879 
> 
> 
> Basically I need to configure the  NO_PROXY variable of the Docker deamon to 
> include the registry address. Problem is with cluster up I can't control the 
> ip address that will be assigned to the registry. Or at least I can't find a 
> way to do it. Is there an option that I'm not seeing?
> 
> Thanks
> 
> Lionel.
> 
> ___
> 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

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

Re: API client / library / javascript

[Clayton Coleman]

Yes, `-o yaml` and `-o json` from most calls.

On Mon, Aug 8, 2016 at 10:32 AM, David Strejc 
wrote:

> Can "oc" client be called that when we implement shell call to oc it
> is returining YAMLs or JSONs?
> David Strejc
> https://octopussystems.cz
> t: +420734270131
> e: david.str...@gmail.com
>
>
> On Mon, Aug 8, 2016 at 4:28 PM, Clayton Coleman 
> wrote:
> > I don't know how well split out the OpenShift console client is but
> > I'm sure there would be interest in that.  The Kubernetes dashboard
> > also probably has a JavaScript client that could be extended to
> > Openshift resources
> >
> >> On Aug 8, 2016, at 10:14 AM, David Strejc 
> wrote:
> >>
> >> Is there any API client (other than oc) or library ideally for
> >> javascript or we must implement whole REST API calls ourselves?
> >>
> >> Many thanks for any direction.
> >>
> >> David Strejc
> >> https://octopussystems.cz
> >> t: +420734270131
> >> e: david.str...@gmail.com
> >>
> >> ___
> >> 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: API client / library / javascript

[David Strejc]

Can "oc" client be called that when we implement shell call to oc it
is returining YAMLs or JSONs?
David Strejc
https://octopussystems.cz
t: +420734270131
e: david.str...@gmail.com


On Mon, Aug 8, 2016 at 4:28 PM, Clayton Coleman  wrote:
> I don't know how well split out the OpenShift console client is but
> I'm sure there would be interest in that.  The Kubernetes dashboard
> also probably has a JavaScript client that could be extended to
> Openshift resources
>
>> On Aug 8, 2016, at 10:14 AM, David Strejc  wrote:
>>
>> Is there any API client (other than oc) or library ideally for
>> javascript or we must implement whole REST API calls ourselves?
>>
>> Many thanks for any direction.
>>
>> David Strejc
>> https://octopussystems.cz
>> t: +420734270131
>> e: david.str...@gmail.com
>>
>> ___
>> 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: API client / library / javascript

[Clayton Coleman]

I don't know how well split out the OpenShift console client is but
I'm sure there would be interest in that.  The Kubernetes dashboard
also probably has a JavaScript client that could be extended to
Openshift resources

> On Aug 8, 2016, at 10:14 AM, David Strejc  wrote:
>
> Is there any API client (other than oc) or library ideally for
> javascript or we must implement whole REST API calls ourselves?
>
> Many thanks for any direction.
>
> David Strejc
> https://octopussystems.cz
> t: +420734270131
> e: david.str...@gmail.com
>
> ___
> 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: API client / library / javascript

[Jason DeTiberus]

On Aug 8, 2016 10:14 AM, "David Strejc"  wrote:
>
> Is there any API client (other than oc) or library ideally for
> javascript or we must implement whole REST API calls ourselves?

Nothing official currently. There is work being done in upstream Kubernetes
for this, but timeline for supported clients other than golang will be 1.4
at the earliest.

That said, the swagger api spec is exposed at /swaggerapi on the api
server, so a client can be generated using that. There are some potential
pain points there (not unworkable, though) and that is the main reason for
the delays in providing officially supported clients.

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

API client / library / javascript

[David Strejc]

Is there any API client (other than oc) or library ideally for
javascript or we must implement whole REST API calls ourselves?

Many thanks for any direction.

David Strejc
https://octopussystems.cz
t: +420734270131
e: david.str...@gmail.com

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