We need to decide on how to guide users migrating from v1 -> v2.

[cjdcordeiro]

We need to decide on how to guide users migrating from v1 -> v2.

Options include:

1. Migrate the nuvlabox resource (and related resources)
2. Put a warning saying that the migration can only be done by hand and not from the UI.

Other options?

Originally posted by @mebster in #48 (comment)

[cjdcordeiro]

Current process

1. update the NB as usual (through the UI, v1 to v2)
   1. it will work, but the agent will start complaining about schemas, and the NB will lose its hearbeat
2. manually change the NB status schema to remove obsolete attributes, i.e.

   curl -XPUT https://nuvla.io/api/nuvlabox-status/<uuid>?select=swarm-node-id,comment,docker-plugins ...
   

3. as an admin, update the nuvlabox-status and change version from 1 to 2
4. to be consistent, even though it doesn't seem to cause any errors, do the same on the nb resource

How to automate?

1 [x] seems to be working fine
2 [ ] only admin or the NB can change the nb-status. We could either: 1) backport the old schema attributes into the new schema, just to keep it compatible, or 2) add boilerplate code to the NB agent to remove those obsolete attributes
3 [ ] maybe the NB could also update?
4 [ ] this is a problem, because the version can not be updated by neither the user nor the NB, only admin...how to do it?

[cjdcordeiro]

automation work started in nuvla/api-server#507