Priority & Ordering of some stories for upcoming sprint
by David Martin
Hi all,
Sharing some thoughts on priority and ordering to help with the focus of
the upcoming sprint.
Before we can do this:
As a DevOps Engineer I want to be able to visualise data provided by the
other services on an overview / dashboard screen [met]
https://trello.com/c/SQsfFS34/4-as-a-devops-engineer-i-want-to-be-able-to...
I think we need to do this:
As a developer I want to be able to expose metrics data about Identity
Management in prometheus format from an endpoint of the service [idm]
https://trello.com/c/NgXh76Oi/6-as-a-developer-i-want-to-be-able-to-expos...
It would help a lot to have an example to focus on and build out first,
which would also give us a great reference for future visualization
integrations.
There is a working example already with keycloak and grafana, but they were
for the proof of concept. Doing these stories should be focusing on
something more complete, documented, well tested and maintainable.
Thoughts anyone?
--
David Martin
Red Hat Mobile
Twitter: @irldavem
IRC: @irldavem (#aerogear)
7 years, 12 months
Mitigating ML problems
by John Frizelle
Hi All,
Until such time as we get confirmation that the problems with delivery to
the arergrear-dev ML have been fixed (or we migrate from mailman to a
public google group for the ML), can I ask that ALL mail sent to the
aerogear-dev ML is also sent to the other 2 MLs on this thread -
feedhenry-dev and mobile-dev.
I know this is a bit of a pain, but it's even more painful to not have
mails delivered in a timely fashion.
I know there has been suggestions made to move from mailman to Google
Groups already, but not sure where these discussions are at... Is there
anything preventing us making this jump - the mailman ML problem has been
ongoing for quite some time now with no resolution in sight that I am aware
of, so perhaps it's time to look at moving to Google Groups?
Cheers,
John.
--
John Frizelle
Chief Architect, Red Hat Mobile
Consulting Engineer
mobile: *+353 87 290 1644 <//+353872901644>*
twitter:* @johnfriz*
skype: *john_frizelle*
mail: *jfrizell(a)redhat.com <jfrizell(a)redhat.com>*
7 years, 12 months
Proposal for addition of --mobile flag to oc cluster up
by Phil Brookes
Hey Everyone,
I have opened a proposal with the OpenShift team, hoping to start a
discussion around the addition of a --mobile=true flag to the oc cluster up
command. Running oc cluster up --mobile=true will start a local OpenShift
cluster with all of the MCP features enabled.
This would be a great way for us to gain some exposure for the Mobile Core
and get it into the hands of developers more quickly and easily, so I’d
love to see you share your thoughts on this idea. You can review / comment
/ support it here:
https://github.com/openshift/origin/issues/18089
Thanks,
Phil.
8 years
Re: [aerogear-dev] [feedhenry-dev] Naming Convention for Mobile Services ?
by Paul Wright
Hi Chris,
thanks for starting this discussion, can I object to one item:
> Security & Identity Management = keycloak
because this is likely to end up in downstream documentation, we should
avoid names of upstream projects. In this case I hope we can use
something like 'identity' instead?
Paul
On 01/10/2018 11:44 AM, Chris Foley wrote:
> Hi All,
>
> I had a brief discussion with John around Naming Conventions and what
> may be worth putting in place which could be beneficial but not
> restrictive. I wanted to kick start discussion on this around what may
> be worthwhile.
>
> An important aspect of 5.x is the value add services and getting these
> in place and discoverable from Mobile Core. Should we be applying some
> naming convention or mandatory attributes to these services?
>
> Attributes / Properties of a Service, e.g. ;
> ----------------------------------------------
> *Display Name*: Push Notifications
> *id / serviceName*: push
> *APB Label/Tag*: mobile-service
> Would it be any benefit if the APB tag (mobile-service) carried over
> and became a label on the OCP service (e.g. for the Core SDK to read
> what Mobile Services are available in a namespace)?
> *APB Integrations*: <list of service ids of the services this service
> integrates with>
>
> Some of the above may be agreed already!
>
> We should agree on the actual serviceNames (interested to hear the
> Mobile Service Teams view on what the names should be):
> Metrics = metrics
> Push Notifications = push
> Data Synchronisation = sync
> Security & Identity Management = keycloak
> Mobile Build Automation = build
> API Gateway = gateway
>
> Are there other naming aspects which could be worthwhile getting
> agreement on? Around the SDKs, as they are being designed now, it is
> probably worth considering also.
>
> All opinions welcome.
>
> Best Regards,
> Chris.
> --
>
> CHRISTOPHER FOLEY
>
> BUSINESS SYSTEMS ANALYST, MOBILE
>
> Red Hat Ireland <https://www.redhat.com/>
>
> Communications House, Cork Road,
>
> Waterford City, Ireland X91NY33
>
> chfoley(a)redhat.com <mailto:chfoley@redhat.com>
>
> <https://red.ht/sig>
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>
>
>
> _______________________________________________
> feedhenry-dev mailing list
> feedhenry-dev(a)redhat.com
> https://www.redhat.com/mailman/listinfo/feedhenry-dev
--
Paul Wright
Mobile Docs (github: finp)
8 years
Re: [aerogear-dev] Mobile Statistics using Grafana, Prometheus running on OpenShift
by David Martin
Very nice Wojciech.
I'd love to see/hear more about how it works from the Mobile App, if that
piece is working.
Did you populate stats using the App, or by just curling an endpoint?
(Maybe you said and I missed that)
On 10 January 2018 at 12:22, Wojciech Trocki <wtrocki(a)redhat.com> wrote:
> Forwarding to internal list as AeroGear list seems to be having problems
> with mail delivery.
>
> ---------- Forwarded message ----------
> From: Wojciech Trocki <wtrocki(a)redhat.com>
> Date: Tue, Jan 9, 2018 at 7:55 PM
> Subject: Mobile Statistics using Grafana, Prometheus running on OpenShift
> To: AeroGear Developer Mailing List <aerogear-dev(a)lists.jboss.org>
>
>
> 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>
>
>
--
David Martin
Red Hat Mobile
Twitter: @irldavem
IRC: @irldavem (#aerogear)
8 years
