10:45 p.m.
Has anyone been able to use "oc cluster up --metrics" in order to run OpenShift
Origin *and* Origin Metrics but running a local build (i.e. I need to pick up changes in
master branch of Origin/Origin Metrics that aren't released yet).
The docs make it look very complicated, and nothing I found seems to help a dev get this
up and running quickly without having to look at tons of docs and run lots of commands
with bunches of yaml :).
I'm hoping it is easy, but not documented.
This link doesn't even mention "cluster up" let alone running with Origin
Metrics:
https://github.com/openshift/origin/blob/master/CONTRIBUTING.adoc#develop...
If I run "openshift start" - how do I get my own build of Origin Metrics to
deploy, like "oc cluster up --metrics" does?
It seems no matter what I do, using "cluster up" pulls down images from docker
hub. I have no idea how to run Origin+Metrics using a local build.
I'm hoping someone knows how to do this and can give me the steps.
3:58 a.m.
Mazz,
On 02/19/2017 05:45 AM, John Mazzitelli wrote:
Has anyone been able to use "oc cluster up --metrics" in
order to run OpenShift Origin *and* Origin Metrics but running a local build (i.e. I need
to pick up changes in master branch of Origin/Origin Metrics that aren't released
yet).
As long as you have the desired artifacts in a Docker registry (local or
remote), you should be able to specify it vi the --image and --version
flags:
oc cluster up --image='openshift/origin' --version=latest
In case that's not enough: on a recent task, I built OpenShift locally
and started it with "sudo ./openshift start", and then, from the
origin-metrics clone:
$ ./hack/build-images.sh \
--prefix="jpkroehling/origin-" \
--version="dev"
$ oc process -f metrics.yaml \
-v IMAGE_PREFIX="jpkroehling/origin-" \
-v IMAGE_VERSION="dev" \
-v HAWKULAR_METRICS_HOSTNAME=hawkular-metrics.example.com \
-v USE_PERSISTENT_STORAGE=false \
-v CASSANDRA_NODES=2 | oc create -n openshift-infra -f -
- Juca.
6:27 a.m.
On 02/19/2017 05:45 AM, John Mazzitelli wrote:
> Has anyone been able to use "oc cluster up --metrics" in order to run
> OpenShift Origin *and* Origin Metrics but running a local build (i.e. I
> need to pick up changes in master branch of Origin/Origin Metrics that
> aren't released yet).
As long as you have the desired artifacts in a Docker registry (local or
remote), you should be able to specify it vi the --image and --version
flags:
oc cluster up --image='openshift/origin' --version=latest
How do you build the images from source so they are put in your local Docker registry? I
couldn't see anything in their Makefiles of origin and origin-metrics that do this.
7:16 a.m.
On 02/20/2017 01:27 PM, John Mazzitelli wrote:
How do you build the images from source so they are put in your local
Docker registry? I couldn't see anything in their Makefiles of origin and
origin-metrics that do this.
Take a look at `hack/build-images.sh`. For the record: as I had all the
tools set already from a previous build, I just re-built and ran with
"sudo ./openshift start" from `_output/local/bin/linux/amd64`
- Juca.
1:28 p.m.
Also, just a note that deploying metrics via the deployer pod is deprecated after
OpenShift 3.4
The current way to deploy metrics to OpenShift is it use Ansible.
The docs for how to use this should be available here
https://docs.openshift.org/latest/install_config/cluster_metrics.html but it looks like
the docs have not been updated yet (the PR has been merged:
https://github.com/openshift/openshift-docs/pull/3529)
For the time being the deployer still needs to stay around for backwards compatibility
reasons and to support 'oc cluster up', but you should be moving away from this
for development purposes.
----- Original Message -----
From: "Juraci Paixão Kröhling"
<jpkroehling(a)redhat.com>
To: hawkular-dev(a)lists.jboss.org
Sent: Monday, 20 February, 2017 8:16:00 AM
Subject: Re: [Hawkular-dev] openshift - using cluster up but building from source
On 02/20/2017 01:27 PM, John Mazzitelli wrote:
> How do you build the images from source so they are put in your local
> Docker registry? I couldn't see anything in their Makefiles of origin and
> origin-metrics that do this.
Take a look at `hack/build-images.sh`. For the record: as I had all the
tools set already from a previous build, I just re-built and ran with
"sudo ./openshift start" from `_output/local/bin/linux/amd64`
- Juca.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
11:16 p.m.
$ oc process -f metrics.yaml \
-v IMAGE_PREFIX="jpkroehling/origin-" \
-v IMAGE_VERSION="dev" \
-v HAWKULAR_METRICS_HOSTNAME=hawkular-metrics.example.com \
-v USE_PERSISTENT_STORAGE=false \
-v CASSANDRA_NODES=2 | oc create -n openshift-infra -f -
OK, has anyone tried this on the latest code? (that is, 1.5 alpha 3 OR master).
I have a feeling in the latest code this "metrics.yaml" isn't all that you
need now. There is more that is needed. Because if you only create the entities within
metrics.yaml, you get errors from this oc create:
"Error from server (Forbidden): pods "metrics-deployer-" is forbidden:
service account openshift-infra/metrics-deployer was not found, retry after the service
account is created"
OK, so I then try the following: before this "oc process -f metrics.yaml" I run
this extra command:
$ oc create -n openshift-infra -f metrics-deployer-setup.yaml
Which all results in:
serviceaccount "metrics-deployer" created
pod "metrics-deployer-3k89r" created
Sounds good right? Well, go to the UI Console and see that metrics deployer has an error:
MountVolume.SetUp failed for volume
"kubernetes.io/secret/2a843217-f8bd-11e6-95ab-54ee7549ae45-secret" (spec.Name:
"secret") pod "2a843217-f8bd-11e6-95ab-54ee7549ae45" (UID:
"2a843217-f8bd-11e6-95ab-54ee7549ae45") with: secrets
"metrics-deployer" not found
11:30 p.m.
OK, I got it. In case anyone cares (yes, I found these in the docs - go figure.)
oc create -n openshift-infra -f metrics-deployer-setup.yaml
oc adm policy add-role-to-user edit system:serviceaccount:openshift-infra:metrics-deployer
-n openshift-infra
oc secrets new metrics-deployer nothing=/dev/null -n openshift-infra
oc adm policy add-role-to-user view system:serviceaccount:openshift-infra:hawkular -n
openshift-infra
oc adm policy add-cluster-role-to-user cluster-reader
system:serviceaccount:openshift-infra:heapster -n openshift-infra
NOW you can oc create metrics.yaml :)
At least now I see all my "latest" containers starting up. I'll see what
else is broke after it all starts :)
----- Original Message -----
> $ oc process -f metrics.yaml \
> -v IMAGE_PREFIX="jpkroehling/origin-" \
> -v IMAGE_VERSION="dev" \
> -v HAWKULAR_METRICS_HOSTNAME=hawkular-metrics.example.com \
> -v USE_PERSISTENT_STORAGE=false \
> -v CASSANDRA_NODES=2 | oc create -n openshift-infra -f -
OK, has anyone tried this on the latest code? (that is, 1.5 alpha 3 OR
master).
I have a feeling in the latest code this "metrics.yaml" isn't all that you
need now. There is more that is needed. Because if you only create the
entities within metrics.yaml, you get errors from this oc create:
"Error from server (Forbidden): pods "metrics-deployer-" is forbidden:
service account openshift-infra/metrics-deployer was not found, retry
after the service account is created"
OK, so I then try the following: before this "oc process -f metrics.yaml" I
run this extra command:
$ oc create -n openshift-infra -f metrics-deployer-setup.yaml
Which all results in:
serviceaccount "metrics-deployer" created
pod "metrics-deployer-3k89r" created
Sounds good right? Well, go to the UI Console and see that metrics deployer
has an error:
MountVolume.SetUp failed for volume
"kubernetes.io/secret/2a843217-f8bd-11e6-95ab-54ee7549ae45-secret"
(spec.Name: "secret") pod "2a843217-f8bd-11e6-95ab-54ee7549ae45"
(UID:
"2a843217-f8bd-11e6-95ab-54ee7549ae45") with: secrets
"metrics-deployer"
not found
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
7:58 a.m.
----- Original Message -----
From: "John Mazzitelli" <mazz(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Wednesday, 22 February, 2017 12:30:00 AM
Subject: Re: [Hawkular-dev] openshift - using cluster up but building from source
OK, I got it. In case anyone cares (yes, I found these in the docs - go
figure.)
oc create -n openshift-infra -f metrics-deployer-setup.yaml
oc adm policy add-role-to-user edit
system:serviceaccount:openshift-infra:metrics-deployer -n openshift-infra
oc secrets new metrics-deployer nothing=/dev/null -n openshift-infra
oc adm policy add-role-to-user view
system:serviceaccount:openshift-infra:hawkular -n openshift-infra
oc adm policy add-cluster-role-to-user cluster-reader
system:serviceaccount:openshift-infra:heapster -n openshift-infra
NOW you can oc create metrics.yaml :)
At least now I see all my "latest" containers starting up. I'll see what
else
is broke after it all starts :)
Just a reminder, this is using the deployer which is deprecated. Please start using
openshift-ansible to deploy metrics.
----- Original Message -----
> > $ oc process -f metrics.yaml \
> > -v IMAGE_PREFIX="jpkroehling/origin-" \
> > -v IMAGE_VERSION="dev" \
> > -v HAWKULAR_METRICS_HOSTNAME=hawkular-metrics.example.com \
> > -v USE_PERSISTENT_STORAGE=false \
> > -v CASSANDRA_NODES=2 | oc create -n openshift-infra -f -
>
> OK, has anyone tried this on the latest code? (that is, 1.5 alpha 3 OR
> master).
>
> I have a feeling in the latest code this "metrics.yaml" isn't all that
you
> need now. There is more that is needed. Because if you only create the
> entities within metrics.yaml, you get errors from this oc create:
>
> "Error from server (Forbidden): pods "metrics-deployer-" is
forbidden:
> service account openshift-infra/metrics-deployer was not found, retry
> after the service account is created"
>
> OK, so I then try the following: before this "oc process -f metrics.yaml"
I
> run this extra command:
>
> $ oc create -n openshift-infra -f metrics-deployer-setup.yaml
>
> Which all results in:
>
> serviceaccount "metrics-deployer" created
> pod "metrics-deployer-3k89r" created
>
> Sounds good right? Well, go to the UI Console and see that metrics deployer
> has an error:
>
> MountVolume.SetUp failed for volume
> "kubernetes.io/secret/2a843217-f8bd-11e6-95ab-54ee7549ae45-secret"
> (spec.Name: "secret") pod
"2a843217-f8bd-11e6-95ab-54ee7549ae45" (UID:
> "2a843217-f8bd-11e6-95ab-54ee7549ae45") with: secrets
"metrics-deployer"
> not found
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
6:45 a.m.
Hi,
The way I tested these was to modify the openshift/origin-metrics and
deploy the metrics that way (copy new ear from metrics build etc).
There's a Dockerfile to deploy to your local instance also.
But I didn't of course use --use-metrics or oc cluster up but did those
steps manually also.
- Micke
On 02/19/2017 06:45 AM, John Mazzitelli wrote:
Has anyone been able to use "oc cluster up --metrics" in
order to run OpenShift Origin *and* Origin Metrics but running a local build (i.e. I need
to pick up changes in master branch of Origin/Origin Metrics that aren't released
yet).
The docs make it look very complicated, and nothing I found seems to help a dev get this
up and running quickly without having to look at tons of docs and run lots of commands
with bunches of yaml :).
I'm hoping it is easy, but not documented.
This link doesn't even mention "cluster up" let alone running with Origin
Metrics:
https://github.com/openshift/origin/blob/master/CONTRIBUTING.adoc#develop...
If I run "openshift start" - how do I get my own build of Origin Metrics to
deploy, like "oc cluster up --metrics" does?
It seems no matter what I do, using "cluster up" pulls down images from docker
hub. I have no idea how to run Origin+Metrics using a local build.
I'm hoping someone knows how to do this and can give me the steps.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
2617
days inactive
2620
days old
8 comments
4 participants
participants (4)
-
John Mazzitelli -
Juraci Paixão Kröhling -
Matt Wringe -
Michael Burman