Mobile Statistics using Grafana, Prometheus running on OpenShift
by Wojciech Trocki
Hi everyone
I have been working today on investigation for enabling mobile application
statistics on top of OpenShift.
The main target was to enable mobile clients (using our SDK) to send
statistics payload to server.
For this purpose we were sending back mobile.next() SDK version from
different mobile clients and visualizing that data Grafana.
*Demo: *
https://www.youtube.com/watch?v=zC95jJr1kcc
*Where is the value? *
Grafana, can be used to showcase various statistics that mobile developers
will need without extended development effort.
*How we can extend this:*
- Investigate different ways to store data in Prometheus (using labels etc.)
- Integrate with Keycloak to showcase SDK capabilities and permissions.
- Golang implementation for service
Regards
--
WOJCIECH TROCKI
Red Hat Mobile <https://www.redhat.com/>
IM: wtrocki
<https://red.ht/sig>
6 years, 3 months
Problem to run mobile-core
by Daniel Passos
Hi,
I’m trying to run mobile-core a my Mac and I running this problem:
{
"changed": false,
"cmd": "oc cluster up --service-catalog=true
--host-config-dir=/Users/passos/Development/Projects/AeroGear/mobile-core/ui
--host-data-dir=/Users/passos/Development/Projects/AeroGear/mobile-core/ui/openshift-data
--host-pv-dir=/Users/passos/Development/Projects/AeroGear/mobile-core/ui/openshift-pvs
--host-volumes-dir=/Users/passos/Development/Projects/AeroGear/mobile-core/ui/openshift-volumes
--routing-suffix=192.168.37.1.nip.io --public-hostname=192.168.37.1
--version=v3.7.0 --image=openshift/origin",
"delta": "0:00:03.655825",
"end": "2018-01-09 15:58:00.300861",
"failed": true,
"msg": "non-zero return code",
"rc": 1,
"start": "2018-01-09 15:57:56.645036",
"stderr": "",
"stderr_lines": [],
"stdout": "Starting OpenShift using openshift/origin:v3.7.0
...\n-- Checking OpenShift client ... OK\n-- Checking Docker client
... OK\n-- Checking Docker version ... OK\n-- Checking for existing
OpenShift container ... OK\n-- Checking for openshift/origin:v3.7.0
image ... OK\n-- Checking Docker daemon configuration ... OK\n--
Checking for available ports ... OK\n-- Checking type of volume mount
... \n Using Docker shared volumes for OpenShift volumes\n-- Creating
host directories ... OK\n-- Finding server IP ... \n Using public
hostname IP 192.168.37.1 as the host IP\n Using 192.168.37.1 as the
server IP\n-- Checking service catalog version requirements ... OK\n--
Starting OpenShift container ... \n Creating initial OpenShift
configuration\nFAIL\n Error: could not create OpenShift
configuration\n Caused By:\n Error: cannot start container
80344c3dfaeb8c3036360fef07ac411c0f516b2ef8faeba0003e3ccf205d2f42\n
Caused By:\n Error: Error response from daemon: {"message":"linux
mounts: path /Users/passos/Development/Projects/AeroGear/mobile-core/ui/openshift-volumes
is mounted on /Users but it is not a shared or slave mount"}",
"stdout_lines": [
"Starting OpenShift using openshift/origin:v3.7.0 ...",
"-- Checking OpenShift client ... OK",
"-- Checking Docker client ... OK",
"-- Checking Docker version ... OK",
"-- Checking for existing OpenShift container ... OK",
"-- Checking for openshift/origin:v3.7.0 image ... OK",
"-- Checking Docker daemon configuration ... OK",
"-- Checking for available ports ... OK",
"-- Checking type of volume mount ... ",
" Using Docker shared volumes for OpenShift volumes",
"-- Creating host directories ... OK",
"-- Finding server IP ... ",
" Using public hostname IP 192.168.37.1 as the host IP",
" Using 192.168.37.1 as the server IP",
"-- Checking service catalog version requirements ... OK",
"-- Starting OpenShift container ... ",
" Creating initial OpenShift configuration",
"FAIL",
" Error: could not create OpenShift configuration",
" Caused By:",
" Error: cannot start container
80344c3dfaeb8c3036360fef07ac411c0f516b2ef8faeba0003e3ccf205d2f42",
" Caused By:",
" Error: Error response from daemon: {
"message":"linux mounts: path
/Users/passos/Development/Projects/AeroGear/mobile-core/ui/openshift-volumes
is mounted on /Users but it is not a shared or slave mount"
}"
]
}
Here is my environment:
→ oc version
oc v3.7.0+7ed6862
kubernetes v1.7.6+a08f5eeb62
→ docker -v
Docker version 17.12.0-ce, build c97c6d6
--
-- Passos
6 years, 3 months
I have just enabled PR checking on mobile-cli!
by Adam Saleh
Hi all,
after a day or so of fiddling around, there is now a mandatory check on the
mobile-cli repository [1],
running on our trusted jenkins-wendy [2]. If there are any problems with
the check, please shout at me on IRC :-)
Check themselves are quite benign right now:
* installs dependencies through glide
* runs make build (after last Craigs PR this includes some tests as well)
* tries to run the 'mobile' binary to print out the help
I think this is a good start and as next steps I will probably try to do
* some proper documentation about i.e. updating the slave image if somebody
would need to
* adding proper test-result/coverage collecting
I am putting together a proper proposal for PR-testing in Aerogear, where
we could discuss how thorough do we want to have these tests.
Please let me know what you think about this :-)
Adam
[1] https://github.com/aerogear/mobile-cli/blob/master/Jenkinsfile
[2] https://jenkins-wendy.ci.feedhenry.org/job/aerogear/job/mobile-cli/
6 years, 3 months
5.x/Mobile Comms
by David Martin
Hi all,
This email is moreso a formality so everyone knows how we have been
communicating, but wanted to share so everyone is aware, particular with a
lot of new team members working on 5.x.
However, if you feel strongly against anything here, please lets discuss.
TLDR;
* Lets default to #aerogear for all chat, discussions etc..
* Lets use direct messages, email or #mobile-internal for private chat,
discussions etc...
Reasons
* #aerogear on freenode is already active with 5.x chat & discussions, and
has been for ~6 months (it's been active a lot longer than that for mobile
things)
* having a central place for chat increases the likelihood of getting help
or feedback, particularly if people across different teams hit the same
issues and have solved it already. It also increases visibility of work
other teams are doing, which can avoid duplication & encourage collaboration
* we are all part of 1 larger team working on the same goal. Lets not
exclude or silo ourselves
* #aerogear is public/open. 5.x development is all upstream/open. Removing
any barriers to building an open community, which we are all the foundation
of, makes sense
--
David Martin
Red Hat Mobile
Twitter: @irldavem
IRC: @irldavem (#aerogear)
6 years, 3 months
AeroGear Github projects
by Daniel Passos
Hi
I wanna create some Github projects to help us to organize repos on
AeroGear organization. Wdyt?
I was thinking about create 2 types of projects:
1. Platforms
2. Features
Some examples in my mind:
Platforms
Android
iOS
JS
Xamarin
Cordova
Feature
Website
Core
Http
Push
OAuth2
Database
Security
Sync
PS: A repo can be in more than one project.
--
-- Passos
6 years, 3 months
