(mcp-standalone)[https://github.com/feedhenry/mcp-standalone]
The mobile control panel aims to help mobile developers working with and integrating with mobile enabled services on OpenShift. It provides a mobile centric view and set of features designed to enable mobile developers to focus on building great mobile applications with deep server side integrations to powerful services such as server side data sync, push notification, authentication etc without necessarily worrying about how to provision and configure those services to work with their mobile clients.
This repo has 3 main parts:
1) ./server
The api server which serves as the server side logic for the mcp UI.
2) ./ui
The mcp ui. This is an extension to the OpenShift UI to give a mobile centric view and set of features.
3) ./docs
This holds design docs, architectural docs, use cases and development guides etc.
oc
cli >= 3.6.0-rc0 https://github.com/openshift/origin/releases (Known issue with service-catalog in 3.6.0)oc cluster down
.The installer/
directory contains a collection of Ansible roles to install
the Mobile Control Panel in OpenShift.
The installer will perform a number of tasks:
oc cluster up
with the Service Catalog enabledansible-galaxy install -r requirements.yml
in the current directory to
install dependencies.Running the installer against localhost:
ansible-playbook playbook.yml -e "dockerhub_username=myuser" -e "dockerhub_password=mypass" --ask-become-pass
Once Ansible finished run oc cluster status
to get the URL of the web console.
To create a mobile app using oc
:
oc create -f ./server/hack/install-apiserver/MobileApp.json
Variables can be provided as arguments to the ansible-playbook
command using
-e variable_name=variable_value
or by populating the
vars/mobile-control-panel.yml
file.
dockerhub_username
- DockerHub usernamedockerhub_password
- DockerHub passwordNote: If dockerhub_username
and dockerhub_password
are not specified the
Ansible Service broker will not be created.
templates
- A list of templates to create for the Template Service Broker.
The values can be local paths or URLs. Example: -e "templates=['/path/to/template.yaml']"
host_config_dir
- Where to create or use the existing host config during oc cluster up
.cluster_version
- The version of images to use during oc cluster up
.cluster_public_hostname
- The hostname to use with --public-ip
and --routing-suffix
options in oc cluster up
.dockerhub_org
- The org to point the ASB to, to look for APB images (defaults to ansibleplaybookbundle
)launch_apb_on_bind
- Set to true to have binds kick off a fresh APB to run the bind playbook (times out at 60 seconds, defaults to False
)If you want to just stop the cluster:
oc cluster down
To stop the cluster and remove any openshift config (Destructive):
./ui/clean.sh
If you get this error straight after installing locally, the mobile-apiserver may not be running yet. You can check that by doing:
oc get po -l 'app=apiserver' -n mobile
NAME READY STATUS RESTARTS AGE
apiserver-1747434594-pzdvv 2/2 Running 0 13m
You can debug the reason why its not running by using oc get events -n mobile
and looking for any errors or failure events.
If the apiserver is not showing, it may have failed to install. Check the install logs for any errors.