Run clients using a development environment

Registered by Leo Arias on 2013-06-14

We need to run all the clients agaist a test environment, so they should be easily configurable to run against staging and development servers.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Steps:

  1. Kill syncdaemon if it is running.
  2. Open seahorse and delete the Ubuntu One credentials, if present.
  3. Log in with Staging Ubuntu SSO:
   $ U1_DEBUG=True USSOC_SERVICE_URL=https://login.staging.ubuntu.com/api/1.0/ /usr/lib/ubuntu-sso-client/ubuntu-sso-login &
   $ export SSO_AUTH_BASE_URL=https://login.staging.ubuntu.com
   $ export SSO_UONE_BASE_URL=https://staging.one.ubuntu.com
   $ /usr/lib/ubuntu-sso-client/ubuntu-sso-login-qt
   Log in or sign up.

  4. Start syncdaemon with staging server:
   $ /usr/lib/ubuntuone-client/ubuntuone-syncdaemon --disable_ssl_verify --dns_srv=None --host=91.189.89.89 &
   $ u1sdtool --connect

  5. Start the unity musicstore daemon with staging server (this one is currently on the private PPA https://code.launchpad.net/~diegosarmentero/+archive/u1-dash-builds):
  $ pkill unity-music; G_MESSAGES_DEBUG=all U1_STAGING_WEBAPI=https://staging.one.ubuntu.com/ U1_STAGING_AUTHENTICATION=https://login.staging.ubuntu.com/ /usr/lib/x86_64-linux-gnu/unity-lens-music/unity-musicstore-daemon

  Information gathered from devs:

  instructions from verterok to use syncdaemon with staging servers:

  - echo -e "[__main__]\ndns_srv=None\n# staging\nhost=91.189.89.89\n" >
  ~/.config/ubuntuone/syncdaemon.conf

  instructions from rye to get the tokens need to connect to staging:

  - download ubuntuone-sso-login.py and run it with --u1-host=staging.one.ubuntu.com - this will give you the oauth tokens you will be able to stuff into syncdaemon via ~/.config/ubuntuone/syncdaemon.conf [__main__] section, oauth parameter
  and downloads are at people.canonical.com/~roman.yepishev/us/ubuntuone-sso-login.py
  (Leo: This address doesn't seem to work)

  after that you will be able to do u1sdtool --connect, that does not use
  anything SSO/ubuntuone-control-panel related etc.

  instructions from nessita to connect the control panel to staging
  servers:

  You can change the definition of WEBSERVICE_BASE_URL in
  ubuntuone/controlpanel/__init__.py so it points to staging. This will
  only affect REST api calls.

 instructions from facundobatista to use u1 folders not in the user home:

 HOME=/tmp/u1test/home/ /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
 --port 443 --host 91.189.89.89 --dns_srv=None --oauth
  poKxXrgdrwgsFQhLnktYInOMXcSCLBbtbgsQSwBNWdUcCpMOxB:rcYNrtsSFVQgZAvCdfLflaLiGhWWVZIuIOwvrDZBRVzohfKayB
  --data_dir /tmp/u1test/home/.local/share/ubuntuone/syncdaemon --root_dir
  /tmp/u1test/home/Ubuntu\ One --shares_dir
  /tmp/u1test/home/.local/share/ubuntuone/shares --logging-backup_c

  NOTE: these days you will probably need to add --disable_ssl_verify when
  connecting to the staging servers. (alecu)

  Instructions from alecu to sign in with SSO staging:
  1) make sure that Syncdaemon is not running, and that there are no U1
  credentials using seahorse. Delete them if there are any.

  2) $ U1_DEBUG=True USSOC_SERVICE_URL=https://login.staging.ubuntu.com/api/1.0/
  /usr/lib/ubuntu-sso-client/ubuntu-sso-login

  3)
   $ export SSO_AUTH_BASE_URL=https://login.staging.ubuntu.com
   $ export SSO_UONE_BASE_URL=https://staging.one.ubuntu.com
/usr/lib/ubuntu-sso-client/ubuntu-sso-login-qt

  4) Log into u1 with an existing account

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.