Sultan

An Open edX Remote Devstack by Appsembler

This toolkit helps your run devstack on cloud (currently GCP). It will also provide you with the necessary tools to help you using your local machine for development, and your cloud instance for showing and testing.

The ultimate goal of this toolkit is to help you running projects under development on the cloud while having the luxury to run the engineering side on your machine. No dependencies headaches anymore.

Some available and ready-to-use devstack images are going to help you running the project in a couple of minutes. You can write, delete, and start from scratch anytime with no regrets.

Documentation

An extensive documentation on the architecture and the toolkit commands can be found in the repo's wiki page here.

1. Before you start

Make sure you have your SSH key added into our GCP Appsembler Devstack (appsembler-devstack-30) project. You can check that at GCP Compute Metadata. Make sure you have GCloud command-line tools installed.

2. Quick Start

2.1. Clone and configure

Follow the next steps to set up your Sultan devstack

$ git clone git@github.com:appsembler/sultan.git
$ cd sultan
$ sultan config init
## configs/.configs.username is created

2.2. Required configurations

The following configurations must be overridden in your recently-created config file:

SSH_KEY: The private key that has access to the GCP project where we will create your instance
PROJECT_ID: The GCloud project ID.
SERVICE_ACCOUNT_EMAIL: A string that we will use to create a service account.
SERVICE_KEY_PATH: Path to the service account key created in the steps above.

More about this later in Working with configurations section.

2.3. Create your first devstack

Create an instance from a pre-packaged image

$ sultan instance setup --image devstack-juniper

3. Working with configurations

3.1. Local environment set up

To setup the configurations on your local machine, we need to make sure that your local environment is correctly set up.

You'll need to create a service account in the GCloud project that will host your devstack instance (official docs here).
Grant the service account permission to create an instance (official docs here).
Grant the service account roles/compute.instanceAdmin role (See also the list of roles).
Download the service account on your machine.

3.2. Getting sultan configurations ready

After downloading the service account, edit the value of SERVICE_KEY_PATH to match its location. (Follow the official docs (here) to generate a key for your service account).
Edit (uncomment, set) the following values in your configs file

## File configs/.configs.$USER
SSH_KEY="$(HOME)/.ssh/id_rsa"
PROJECT_ID="appsembler-devstack-30"
SERVICE_ACCOUNT_EMAIL=devstack@appsembler-devstack-30.iam.gserviceaccount.com
SERVICE_KEY_PATH=/Users/matej/Work/Appsembler/appsembler-devstack-30-104c123267bf.json

NOTE

This example has my values

You should change the value SERVICE_KEY_PATH if you decided to copy and paste the configurations above.

3.3. Optional configurations

Accessing `sultan` from any directory on your machine

If you want to access sultan command line from any directory, add this repo dir to your PATH

$ export PATH=$PATH:$(pwd)  # pwd should translate to /path/to/projects/sultan

Enabling auto completion

To enable auto completion

$ source extras/sultan-completion.bash  # For bash shell
$ source extras/sultan-completion.zsh   # For zsh shell

NOTE

You can add the command above to your ~/.bashrc or ~/.zshrc

Check the best zone for your machine

This is in order to have as small latency to your machine and mounted dirs as possible. You can check it here: http://www.gcping.com/ Following example will be how I’ve set it up (the ZONE value) in Europe.

For minimum latency. You can set ZONE value to match the nearest GCP zone to you.

## File configs/.configs.$USER
ZONE=europe-west3-c

Debugging

If this is your first time creating your instance, we recommend enabling DEBUG mode to be able to to see a verbose output in case something fails:

## File configs/.configs.$USER
DEBUG=false

Devstack run command

We created a custom env variable for the devstack run command. EdX uses dev.up to get the devstack services running. However, in Appsembler we use some other services that requires extra environment variables such as HOST. So simply what we can do here is

## File configs/.configs.$USER
DEVSTACK_RUN_COMMAND="HOST=tahoe dev.up"

NOTE

You need to configure GCloud on your machine before setting the variables above.

4. Creating your first edX devstack instance

4.1. Setting up the devstack

Simple as running

$ IMAGE_NAME=devstack-juniper  # Or any other devstack image name
$ sultan instance setup --image $IMAGE_NAME

The previous command will spin an instance for you from an already created image. However, if you prefer to run the full setup from scratch just don't supply an image argument.

$ sultan instance setup

Make yourself some coffee. Go for a jog. Recreate the Sistine Chapel painting. Actually, go and built the chapel first. Then do the painting. You’ll have time. A full setup takes quite long. But, once it’s finished…

4.2. Bring up devstack up

To run the devstack

$ sultan devstack up

It works. Noice!!

Verify everything is reachable

To verify that your instance has been created:

$ sultan instance status  ## Prints your GCP instance status.
$ sultan instance ip  ## Shows you the instance IP.
$ sultan instance ping  ## Verifies that Ansible is able to reach your instance.

To verify that your devstack is running:

$ curl -I edx.devstack.lms:18010  ## Curls your LMS site.

NOTE

LMS and Studio might take up to 3 minutes to fully spin. You can check their logs by running sultan devstack make lms-logs.

Accessing the default created site, AMC, Studio, edx admin, AMC admin

Our Devstack automatically creates your initial site:

Property	Value
LMS URL	red.localhost:18000
Username	red
Email	red@example.com
Password	red

Hey, I cannot access red.localhost:18000!

Are you using Chrome? I was too. For some godforsaken reason it doesn’t work for me there (other URLs that are not localhost do). But in Firefox it does!

Other information:

Property	Value
AMC URL (Django-served)	http://tahoe.devstack.amc:29000
AMC Signup Wizard URL (Django-served)	http://tahoe.devstack.amc:29000/signup-wizard
LMS admin username	edx
LMS admin password	edx
AMC admin username	amc
AMC admin password	amc
Studio URL	http://amc.devstack.cms:18010

4.3. Optionally create your own site

During the config we have added a test.localhost entry. So if you create a new site just set the site name to test and you’ll automatically be good to go.

To skip the wizard and to create your site from command line (Good as it doesn't require email)

$ sultan devstack make lms-shell
$ ./manage.py lms create_devstack_site test
$ exit
$ sultan devstack make amc-shell
$ ./manage.py create_devstack_site test 
$ exit

If the signup wizard doesn’t progress from step 1 for you, go and check the AMC logs (method above). If you see an error logged referring to Terms and Conditions, it’s a lingering issue where the pip package was updated to a new version that doesn’t work. We have reverted that in the meantime, but in case it occurs to you, exit the logs and do a make amc-shell, then pip install django-termsandconditions==1.1.9

4.5. Everything works, you’re happy? SAVE IT.

Once you’ve got everything set up the way you like it and it’s working super-duper, you’ll want to save this sweet sweet and highly unlikely state of our glorious Devstack. To do that you want to create an image of your VM so you can redeploy it quickly whenever you (inevitably) break your Devstack.

In order to do so, simply run:

$ sultan image create

You can also specify a name for your image using

$ sultan image create --name my-lovely-image

NOTE

Just don't forget to supply the image name later to the setup command when you wanna retrieve it: sultan instance setup --image my-lovely-image.

4.6. Starting/stopping your Devstack

To start your Devstack once it’s set up:

$ sultan instance start
## beep-boop the machine does some machine stuff
$ sultan devstack up

Stopping? No problem

$ sultan instance stop  ## Will stop your devstack firts, then the instance.

Want to get rid of it?

$ sultan instance delete

OMG IT FAILS I CANNOT ACCESS MY INSTANCE. BAD DEVSTACK BAD!

It’s most likely a firewall issue. The instance is secured behind a firewall that only identifies your IP. Probably your IP happened to change (after a network disconnection for example). Here’s the remedy:

If you didn’t already, do the sultan instance start
Try reaching it with sultan instnace ping
if it cannot reach it, do the sultan instance restrict to adjust the firewall rule.

I’m just gonna assume it worked and you self-high-fived.

YOU LIED! IT STILL DOESN’T WORK!

Huh, could be something’s properly broken. But remember when we created the image of your instance?

$ sultan instance setup --image

NOTE

If you don't supply an image name to this command, sultan will default back to the IMAGE_NAME value set in your configs file. So all is good.

Woah it’s so fast I cannot believe it! Yup, really works fast and resets it to that glorious state you saved. Nice.

NOTE

The instance is secured behind a firewall by default. To override this behavior, change RESTRICT_INSTANCE value in your configs to false.

5. Development

To change or update edx-platform code from your machine and reflect on the server immediately, there are so many ways you can choose from. However, we recommend two common methods to ensure security, real-time transfer, and immediate reflection on the remote instance:

5.1. SSHFS

To use it all you have to do is to run sultan devstack mount and then open your favorite text editor and start editing files on the server from your machine.

5.2. Preferred IDEs

Some IDEs gives you the power to edit code on remote machines. Visual Studio Code for example, recently added Code Remote Extensions. With this extension, you'll be able to open any folder on your remote machine and take advantage of VS Code's full feature set.

NOTE

If you are using MacOS, make sure to install osxfuse and giving it the right permissions before running sultan devstack mount.

If you at a later point restart or whatever without unmounting first and it doesn’t work, just do sultan devstack unmount and then again sultan devstack mount. Works like a charm.

DISCLAIMER

Manually mounting your devstack locally is slow and laggy. Barely usable. But what I’ve found is that it works way way better with Visual Studio Code and its Code Remote Extensions.

6. To conclude

Please add more stuff to this doc as you discover helpful information. Let’s all strive for a bright future where an engineer can follow a couple easy steps here and BOOM it’s done.

7. Environment variables

We create a specific ignored .configs file for you when you ran sultan config init, to debug the final environment variables values you can run

$ sultan config debug

8. Tool help

To check the commands documentation run

$ sultan -h
$ sultan --help

9. Errors

Errors are possible all the time. If an error's fired while executing commands from this toolkit it is recommended to do a little bit more debugging. While this might be an issue with the tool, we just want you to make sure that you have everything correct set up in place:

Run sultan config debug and check if all of your environment variables hold the correct values.
Enable out debugging through the DEBUG setting in your env file.
Check our Wiki page for a detailed documentation on the configuration process.

If you couldn't identify the cause of the problem, please submit an issue on https://github.com/appsembler/sultan/issues.

LMS pages show TypeError exception

Problem

The exception below shows up on every (or most) lms pages a full example log is available in this gist.

TypeError: _clone() takes exactly 1 argument (3 given)

Instructions

Omar: While I don’t know why this happening, I know how to fix it.

Aparently devstack installs an incorrect django-model-utils package and it breaks the LMS. Install a specific version of jazzband/django-model-utils so the platform works:

$ ssh devstack
$ cd workspace/src
$ mkdir -p edxapp-pip
$ cd edxapp-pip
$ git clone https://github.com/jazzband/django-model-utils.git
$ cd django-model-utils
$ git checkout 3.0.0
$ exit
$ sultan devstack up

That should fix the problem.

rediris / sultan

Sultan

An Open edX Remote Devstack by Appsembler

Documentation

1. Before you start

2. Quick Start

2.1. Clone and configure

2.2. Required configurations

2.3. Create your first devstack

3. Working with configurations

3.1. Local environment set up

3.2. Getting sultan configurations ready

3.3. Optional configurations

Accessing `sultan` from any directory on your machine

Enabling auto completion

Check the best zone for your machine

Debugging

Devstack run command

4. Creating your first edX devstack instance

4.1. Setting up the devstack

4.2. Bring up devstack up

Verify everything is reachable

Accessing the default created site, AMC, Studio, edx admin, AMC admin

4.3. Optionally create your own site

4.5. Everything works, you’re happy? SAVE IT.

4.6. Starting/stopping your Devstack

OMG IT FAILS I CANNOT ACCESS MY INSTANCE. BAD DEVSTACK BAD!

YOU LIED! IT STILL DOESN’T WORK!

5. Development

5.1. SSHFS

5.2. Preferred IDEs

6. To conclude

7. Environment variables

8. Tool help

9. Errors

LMS pages show TypeError exception

Problem

Instructions

About

Languages

Sultan

An Open edX Remote Devstack by Appsembler

Documentation

1. Before you start

2. Quick Start

2.1. Clone and configure

2.2. Required configurations

2.3. Create your first devstack

3. Working with configurations

3.1. Local environment set up

3.2. Getting sultan configurations ready

3.3. Optional configurations

Accessing sultan from any directory on your machine

Enabling auto completion

Check the best zone for your machine

Debugging

Devstack run command

4. Creating your first edX devstack instance

4.1. Setting up the devstack

4.2. Bring up devstack up

Verify everything is reachable

Accessing the default created site, AMC, Studio, edx admin, AMC admin

4.3. Optionally create your own site

4.5. Everything works, you’re happy? SAVE IT.

4.6. Starting/stopping your Devstack

OMG IT FAILS I CANNOT ACCESS MY INSTANCE. BAD DEVSTACK BAD!

YOU LIED! IT STILL DOESN’T WORK!

5. Development

5.1. SSHFS

5.2. Preferred IDEs

6. To conclude

7. Environment variables

8. Tool help

9. Errors

LMS pages show TypeError exception

Problem

Instructions

About

Languages

Accessing `sultan` from any directory on your machine