Manually get VMs for devs to learn OMS, so we can start implementing the back-end

[a-laughlin]

The instructions for downloading a VM are located at http://docs.openmustardseed.org/get_started/tab_dev_environment/

The VMs require an ID3-provided key to decrypt. Soon there will be a UI to automatically download the VM and get the key emailed to us. I'm getting one manually for @sDurgam and I so we can get started. It should be coming via email this evening or tomorrow.

@sDurgam The last line of the VM instructions says that phone interaction isn't yet supported. We'd have to do some DNS configuration and port forwarding to get it working on the VM.

@illumin-us-r3v0lution I pasted the updated sequence diagram in #9. Does that help for what we're trying to do?

[a-laughlin]

Placing this here so I can follow up on it tomorrow.

From #oms:

<alaughlin> So.  Imagine you're using Funf to collect GPS data.  You have android code that tells it to run at 8am.  You want to change it to collect data at 10am.  In the Web UI, you change a form field from 8am to 10pm.  Your android code gets the change, and updates when funf will collect data.
<oms> alaughlin: ok, that makes sense. what is the question I can help with?
<oms> alaughlin: somethign I am realizing.. while this is not yet 100% ready, the OMS architecture would take care of this need through the Global Settings Registry
<oms> the android app is an App in a TAB, and thus, it has access to the GSR as a config dictionarty
<oms> or dictionary of config keys
<oms> that detail (the time to check, or whatever) would be a config key for either the App (privately) or the TAB (shared by all Apps in the TAB, but no other TABs)

[a-laughlin]

@illumin-us-r3v0lution, we're talking through architecture in #9. That should help us better outline a scenario to choose which dev environment.

That said, how easy is it for someone with Linux admin experience to do the DNS work that would make phones locally usable? i.e., is it something that could be covered in a single stack overflow question? Maybe it would make more sense to spin up a couple of remote VMs like we had for hap3, hap4, etc? That seems like it may be the quickest way to get started.

[iluminite]

I missed the note on this ticket, I need a better place to see those flags.

DNS/Linux/etc for connecting phones.. here is the scenario: while you may be holding your phone and physically next to your computer running this development environment.. your phone and the computer, as two clients on a global network, are NOT really 'next two each other' - in general, these two devices are on completely separate networks.

Where does that put us? This VM you run on a local computer needs to be found and connected to, on the network, by the phone - the phone needs to be able to reach the VM from the network it is on.

If you create a DNS entry (like with a dyndns-type service) pointed at the network in which the VM runs, and if you route traffic from the outside to that VM, you will do fine. It'd be best to use HTTPS and port 443 (self-signed cert is fine).

[iluminite]

@a-laughlin - were you able to get your developers on the VMs they needed?

[a-laughlin]

@illumin-us-r3v0lution Not yet. That said, we may not need to address the DNS issue at this stage.

@sDurgam, from here it looks like the android emulator can access a local server, so the dev VM and the emulator should work okay together locally. We won't need a remote server.

[sDurgam]

@a-laughlin Cool.

[a-laughlin]

@sDurgam, I'm unsure if you got my message on the IRC channel about trying to import the VM image with VMware instead of VirtualBox. Any luck with that?

[sDurgam]

@a-laughlin I will check with them today.

[a-laughlin]

@sDurgam, I just looked around VMware's site. It looks like they don't have a free product. I'll discuss solutions tomorrow with the ID3 team. My guess is that we'll end up using a remote server for the backend.

[a-laughlin]

@sDurgam, do you have virtualization enabled in your pc's BIOS?

[sDurgam]

@a-laughlin I am bit occupied till tomorrow evening. I will work on VM tomorrow evening.

[a-laughlin]

Sounds good. Thanks for the update.

[sDurgam]

@a-laughlin Thanks. Enabling virtualization in BIOS worked.

[a-laughlin]

Woo hoo! I'll leave this ticket open for now until we can get on OMS v0.8.5.

Pasting in from #oms IRC channel.

so you can start with creating a CoreID and some personas, and interact with OIDC, and then start to understand what those Tokens and Personas are doing and build TABs at this point, that VM is 2 releases old. we'll have an updated VM for 0.8.5 before the end of next week (that's the current goal, which is so far rather doable) ... let us know how we can help and we will, else we'll ping you again as the v0.8.5 release comes out