Re: CI/CD Pipeline & DSL

2016-09-16 Thread Ben Parees 
In the meantime, you can certainly install the fabric8 plugin into our
jenkins image and use those additional pipeline steps. The openshift
pipeline feature works with any valid jenkinsfile.  We just happen to
include the openshift specific plugin/dsl support in the image we ship.

Ben Parees | OpenShift

On Sep 16, 2016 19:08, "Clayton Coleman"  wrote:

> It's been discussed.  The primary concern would that would become a
> versionable API once we ship it, so we have to have a release and
> versioning process that maintains backwards compatibility for users for the
> life of the product.  That part is what we haven't sorted out yet.
>
> On Fri, Sep 16, 2016 at 9:23 AM, Charles Moulliard 
> wrote:
>
>> Hi,
>>
>> As far as I know Openshift and Fabric8 projects have developed DSL to
>> define Jenkins Pipelines running top of OpenShift/Kubernetes
>>
>> - OpenShift :  https://github.com/openshift/
>> jenkins-plugin#jenkins-pipeline-formerly-workflow-plugin
>> - Fabric8 : https://github.com/fabric8io/jenkins-pipeline-library
>>
>> Is it planned that (some) Fabric8 DSL tasks will be integrated in a
>> future version of OpenShift ?
>>
>> Regards,
>>
>> Charles
>>
>> ___
>> 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: CI/CD Pipeline & DSL

2016-09-16 Thread Charles Moulliard 
Hi Clayton,

Is there a jira ticket, email, ... where it has been discussed ?

Regards,

Charles

On Fri, Sep 16, 2016 at 7:07 PM, Clayton Coleman 
wrote:

> It's been discussed.  The primary concern would that would become a
> versionable API once we ship it, so we have to have a release and
> versioning process that maintains backwards compatibility for users for the
> life of the product.  That part is what we haven't sorted out yet.
>
> On Fri, Sep 16, 2016 at 9:23 AM, Charles Moulliard 
> wrote:
>
>> Hi,
>>
>> As far as I know Openshift and Fabric8 projects have developed DSL to
>> define Jenkins Pipelines running top of OpenShift/Kubernetes
>>
>> - OpenShift :  https://github.com/openshift/
>> jenkins-plugin#jenkins-pipeline-formerly-workflow-plugin
>> - Fabric8 : https://github.com/fabric8io/jenkins-pipeline-library
>>
>> Is it planned that (some) Fabric8 DSL tasks will be integrated in a
>> future version of OpenShift ?
>>
>> Regards,
>>
>> Charles
>>
>> ___
>> 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

openshift-ansible branches renamed

2016-09-16 Thread Scott Dodson 
Previously openshift-ansible had enterprise-3.x branches which was
confusing to community members. We have renamed those branches to
release-1.x in order to more closely align with Origin.

More info on branches and tags within openshift-ansible here
https://github.com/openshift/openshift-ansible/blob/master/README.md#branches-and-tags

--
Scott

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

Re: CI/CD Pipeline & DSL

2016-09-16 Thread Clayton Coleman 
It's been discussed.  The primary concern would that would become a
versionable API once we ship it, so we have to have a release and
versioning process that maintains backwards compatibility for users for the
life of the product.  That part is what we haven't sorted out yet.

On Fri, Sep 16, 2016 at 9:23 AM, Charles Moulliard 
wrote:

> Hi,
>
> As far as I know Openshift and Fabric8 projects have developed DSL to
> define Jenkins Pipelines running top of OpenShift/Kubernetes
>
> - OpenShift :  https://github.com/openshift/jenkins-plugin#jenkins-pipelin
> e-formerly-workflow-plugin
> - Fabric8 : https://github.com/fabric8io/jenkins-pipeline-library
>
> Is it planned that (some) Fabric8 DSL tasks will be integrated in a future
> version of OpenShift ?
>
> Regards,
>
> Charles
>
> ___
> 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

CI/CD Pipeline & DSL

2016-09-16 Thread Charles Moulliard 
Hi,

As far as I know Openshift and Fabric8 projects have developed DSL to
define Jenkins Pipelines running top of OpenShift/Kubernetes

- OpenShift :  https://github.com/openshift/jenkins-plugin#jenkins-
pipeline-formerly-workflow-plugin
- Fabric8 : https://github.com/fabric8io/jenkins-pipeline-library

Is it planned that (some) Fabric8 DSL tasks will be integrated in a future
version of OpenShift ?

Regards,

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

Re: Origin v1.3.0 released

2016-09-16 Thread Michal Fojtik 
It works even without public-hostname, in that case it will just give you
the IP that is resolvable from host (thanks Cesar! :-)

On Fri, Sep 16, 2016 at 11:53 AM, Marek Jelen  wrote:

> @mfojtik I can confirm that on my OSX with "Docker for Mac" on beta
> channel `oc cluster up --public-hostname="127.0.0.1"` works just fine.
>
> --
> mj
>
> On Fri, Sep 16, 2016 at 11:45 AM, Michal Fojtik 
> wrote:
>
>> I think the `--create-machine` is not longer needed if you are using the
>> "native" Docker (iow. the xhyve one) on OSX.
>>
>> On Fri, Sep 16, 2016 at 10:46 AM, Matthias Luebken 
>> wrote:
>>
>>> Congrats to everyone!
>>>
>>> > And of course I almost forget - the *fastest* way to get v1.3.0 is:
>>> >   $ oc cluster up --version=v1.3.0
>>>
>>> For Mac and Windows user I might add the infamous `--create-machine`
>>> flag:
>>>
>>> $ oc cluster up --version=v1.3.0 --create-machine
>>>
>>> Configures and spins up everything you need. Read more at:
>>> https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md
>>>
>>>
>>>
>>> On Fri, Sep 16, 2016 at 7:15 AM, Clayton Coleman 
>>> wrote:
>>>
 And of course I almost forget - the *fastest* way to get v1.3.0 is:

 $ oc cluster up --version=v1.3.0

 Enjoy!

 On Fri, Sep 16, 2016 at 12:51 AM, Clayton Coleman 
 wrote:

> Images have been pushed to the hub and release binaries are up on
> GitHub under release v1.3.0
> .  RPMs will
> take a few days to show up in the existing channels.
>
> v1.3.0 was a huge release - thanks to everyone who contributed to make
> it possible.  You can see a list of delivered changes on the 1.3 roadmap
> https://ci.openshift.redhat.com/releases_overview.html#3.3 as well as
> on the individual GitHub release pages for alpha.1 -> rc1.  Please give
> feedback or report any issues you see.
>
> Origin 1.4 will pick up Kube 1.4 and contain a number of more targeted
> features as you can see on the release roadmap
> https://ci.openshift.redhat.com/releases_overview.html#3.4.  The
> rebase has landed in master and we will reopen the queue for changes in 
> the
> morning.  We're also hard at work on Kubernetes 1.5 in the upstream
> community - don't hesitate to get involved there as well.
>
> Thanks!
>


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


>>>
>>>
>>> --
>>> Matthias Luebken
>>> Technical Product Owner
>>> Systems Design & Engineering
>>> 
>>> Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
>>> Commercial register: Amtsgericht Muenchen, HRB 153243,
>>> Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham,
>>> Michael O'Neill
>>>
>>> ___
>>> dev mailing list
>>> d...@lists.openshift.redhat.com
>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>>
>>>
>>
>> ___
>> dev mailing list
>> d...@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>
>>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Origin v1.3.0 released

2016-09-16 Thread Michal Fojtik 
I think the `--create-machine` is not longer needed if you are using the
"native" Docker (iow. the xhyve one) on OSX.

On Fri, Sep 16, 2016 at 10:46 AM, Matthias Luebken 
wrote:

> Congrats to everyone!
>
> > And of course I almost forget - the *fastest* way to get v1.3.0 is:
> >   $ oc cluster up --version=v1.3.0
>
> For Mac and Windows user I might add the infamous `--create-machine` flag:
>
> $ oc cluster up --version=v1.3.0 --create-machine
>
> Configures and spins up everything you need. Read more at:
> https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md
>
>
>
> On Fri, Sep 16, 2016 at 7:15 AM, Clayton Coleman 
> wrote:
>
>> And of course I almost forget - the *fastest* way to get v1.3.0 is:
>>
>> $ oc cluster up --version=v1.3.0
>>
>> Enjoy!
>>
>> On Fri, Sep 16, 2016 at 12:51 AM, Clayton Coleman 
>> wrote:
>>
>>> Images have been pushed to the hub and release binaries are up on GitHub
>>> under release v1.3.0
>>> .  RPMs will
>>> take a few days to show up in the existing channels.
>>>
>>> v1.3.0 was a huge release - thanks to everyone who contributed to make
>>> it possible.  You can see a list of delivered changes on the 1.3 roadmap
>>> https://ci.openshift.redhat.com/releases_overview.html#3.3 as well as
>>> on the individual GitHub release pages for alpha.1 -> rc1.  Please give
>>> feedback or report any issues you see.
>>>
>>> Origin 1.4 will pick up Kube 1.4 and contain a number of more targeted
>>> features as you can see on the release roadmap
>>> https://ci.openshift.redhat.com/releases_overview.html#3.4.  The rebase
>>> has landed in master and we will reopen the queue for changes in the
>>> morning.  We're also hard at work on Kubernetes 1.5 in the upstream
>>> community - don't hesitate to get involved there as well.
>>>
>>> Thanks!
>>>
>>
>>
>> ___
>> dev mailing list
>> d...@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>
>>
>
>
> --
> Matthias Luebken
> Technical Product Owner
> Systems Design & Engineering
> 
> Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
> Commercial register: Amtsgericht Muenchen, HRB 153243,
> Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham,
> Michael O'Neill
>
> ___
> dev mailing list
> d...@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Trouble following the Getting Started guide

2016-09-16 Thread Martin Goldstone 
I think there might be a little confusion here. I'm not using a proxy
between the master and the pods, the proxy is only for getting access to
the Internet. My understanding is that nodes running the pods would need
access to the Internet to download images from the docker hub, and to
install updates (I could run a local mirror for that if needed), so they
need to be configured with the proxy. I know I can put hostnames and
stable/known IP addresses (such as for the master) in the NO_PROXY list,
but in this case to get the http liveness and readiness probes working I
had to put the IP address of the pod in the NO_PROXY list. This works
initially as it's the first pod I've launched and docker seems to give out
IP addresses sequentially, so when starting the origin docker container I
could guess the IP address for the registry pod to put into the NO_PROXY
list, but I'd have thought that when using auto scaling for example this
would be next to impossible, as I won't have advance knowledge of the pods'
IP addresses, so I won't be able to add them to NO_PROXY.

On 15 Sep 2016 19:57, "Clayton Coleman"  wrote:

> *Generally*, a proxy shouldn't be between the router or master servers and
> the pods themselves.  So in production I would expect you to not have that
> issue because you should be able to identify your masters via hostname or
> long term IP (and thus be able to put them in NO_PROXY).  Running in a
> container does have some limitations like that for sure.
>
> The uber-doc for it here: https://docs.openshift.o
> rg/latest/install_config/http_proxies.html - we can add a suggestion that
> helps clarify the question if you think it's not clear enough.
>
> On Thu, Sep 15, 2016 at 11:43 AM, Martin Goldstone <
> m.j.goldst...@keele.ac.uk> wrote:
>
>> Thanks for that info.
>>
>> Your suggestion for #2 worked perfectly, I'll open a bug as you suggest.
>>
>> As for #3, it turns out it's all down to being behind a web proxy. I was
>> only setting the upper case versions of the HTTP_PROXY, HTTPS_PROXY and
>> NO_PROXY env vars, which curl was not picking up. The routing that does the
>> health check was however picking them up and as the IP address of that pod
>> wasn't included in the NO_PROXY env var, it was consulting the proxy. As
>> this was the first pod I started it was reliably getting an IP address of
>> 172.17.0.3. Putting this in the NO_PROXY list allows the container to start
>> successfully, which is great. Unfortunately it's not possible to wildcard
>> IP addresses in NO_PROXY, so I'm not quite sure how I'll manage this in a
>> production environment, as presumably if that pod goes away for whatever
>> reason, a new pod will get started and will have a new IP address. Any
>> suggestions? I'd prefer to keep it behind a proxy server, but I could just
>> give it a NATd Internet connection instead.
>>
>> Thanks.
>>
>> On 15 September 2016 at 16:06, Clayton Coleman 
>> wrote:
>>
>>> The first problem is probably because the request hadn't completely
>>> finished to import the image.  We should report a better error / wait for
>>> the import to happen.  Please open a bug describing what you did and we'll
>>> try to give you a better experience.
>>>
>>> For #2 - clean up what you did before, and run just "oadm registry".
>>> Everything should work correctly.  I think the docs are wrong - if my
>>> simpler suggestion works please open a bug on
>>> github.com/openshift/openshift-docs and we'll fix that.
>>>
>>> For #3 - I'll try to take a look at it and see whether I can recreate.
>>> We might have a bug in the example, since when you input the tags work
>>> correctly.
>>>
>>>
>>>
>>> On Thu, Sep 15, 2016 at 10:32 AM, Martin Goldstone <
>>> m.j.goldstone+opensh...@keele.ac.uk> wrote:
>>>
 Hi,

 I've just started looking at OpenShift Origin. I'm attempting to get it
 going on a CentOS Atomic Host box, and I've been following the Getting
 Started guide at https://docs.openshift.org/
 latest/getting_started/administrators.html#getting-started-a
 dministrators, using the method to run origin as a docker container.
 I've launched origin, and I can create the indicated test project and the
 deployment example app. I've also been able to login to the web console.

 The first of my problems is when the guide suggests running "oc tag
 deployment-example:v2 deployment-example:latest". This command fails with
  "error: "deployment-example:v2" is not currently pointing to an
 image, cannot use it as the source of a tag".

 Leaving this aside, I moved on to trying to deploy the integrated
 registry. Running the command listed, I receive a warning that I should be
 using the --service-account option as --credentials is deprecated. "oc get
 all" shows that the deploy pod is running for the registry, but the
 registry pod never starts. A combination of oc get, oc logs and oc describe
 led me to the conclusion that a service account under the

Can't run containers after advanced installation

2016-09-16 Thread Lionel Orellana 
Hi All

I installed Origin v1.3.0-rc1 (unaware of the imminent 1.3 release) using
the ansible method.
Everything seemed to have installed Ok. But whenever I try to build or run
anything I get this type of error:

Error syncing pod, skipping: failed to "StartContainer" for "POD" with
RunContainerError: "runContainer: Error response from daemon: failed to
create endpoint
k8s_POD.4a82dc9f_nodejs-example-2-build_bimorl_7194e4a4-7bcd-11e6-ab95-005056915814_cd78594e
on network bridge: adding interface veth7932aba to bridge docker0 failed:
could not find bridge docker0: route ip+net: no such network interface"

On the host running a simple docker image fails too.

bash-4.2$ sudo docker run hello-world
docker: Error response from daemon: failed to create endpoint
ecstatic_ramanujan on network bridge: adding interface veth59decae to
bridge docker0 failed: could not find bridge docker0: route ip+net: no such
network interface.

I have restarted the docker service several times with no effect. docker0
appears briefly when i do netstat -nr but then disappears again.

docker version 1.10.3
RHEL 7.2.

Thanks

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

Re: Origin v1.3.0 released

2016-09-16 Thread Lionel Orellana 
Thanks Clayton. Congrats to all on the new release!

Just a few hours earlier I was installing 1.3.0rc1 using ansible. Good
chance now for me to learn how upgrades work.

I'm trying to upgrade to 1.3
using 
openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_3/upgrade.yml.
I set the openshift_release to v1.3.0 in the inventory file. But it's not
happy:

"openshift_release is 1.3.0 which is not a valid release for a 1.3 upgrade"

Do I need to wait for the ansible upgrade playbooks to be updated?


Thanks.


Lionel



On 16 September 2016 at 15:15, Clayton Coleman  wrote:

> And of course I almost forget - the *fastest* way to get v1.3.0 is:
>
> $ oc cluster up --version=v1.3.0
>
> Enjoy!
>
> On Fri, Sep 16, 2016 at 12:51 AM, Clayton Coleman 
> wrote:
>
>> Images have been pushed to the hub and release binaries are up on GitHub
>> under release v1.3.0
>> .  RPMs will
>> take a few days to show up in the existing channels.
>>
>> v1.3.0 was a huge release - thanks to everyone who contributed to make it
>> possible.  You can see a list of delivered changes on the 1.3 roadmap
>> https://ci.openshift.redhat.com/releases_overview.html#3.3 as well as on
>> the individual GitHub release pages for alpha.1 -> rc1.  Please give
>> feedback or report any issues you see.
>>
>> Origin 1.4 will pick up Kube 1.4 and contain a number of more targeted
>> features as you can see on the release roadmap
>> https://ci.openshift.redhat.com/releases_overview.html#3.4.  The rebase
>> has landed in master and we will reopen the queue for changes in the
>> morning.  We're also hard at work on Kubernetes 1.5 in the upstream
>> community - don't hesitate to get involved there as well.
>>
>> Thanks!
>>
>
>
> ___
> 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