kpantic

Consumer-grade GPUs in an OpenStack system (NVIDIA GPUs)

Assumptions

This assumes you have GTX980 cards in your system (PCI id 10de:13c0 & 10de:0fbb per card). Just add more IDs for other cards in order to make this more generic. This also assumes nova uses qemu-kvm as the virtualization hypervisor (qemu-system-x86_64). This seems to be the default on OpenStack Newton when installed using openstack-ansible.

We assume OpenStack Newton is pre-installed and that we are working on a Nova compute node. This has been tested on an Ubuntu 16.04 system where I installed OpenStack AIO version 14.0.0 (different from the git tag used in the instructions!): http://docs.openstack.org/developer/openstack-ansible/developer-docs/quickstart-aio.html

Prepare the system for GPU passthrough (set up IOMMU/vfio/...)

Note: This is heavily based on information from https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#Enabling_IOMMU adapted for Ubuntu 16.04

kpantic

Trello

First sync

When a project is initially linked to a Trello board, certain events need to be created to reflect the current status of the project. The following is a list of certain actions that need to be done to reflect the current status on varys.

• For each card on Trello create the following Events:
  • Event card_created with an event_object_type of card.
  • Event card_added_to_list with an event_object_type of card and its ID.
• For each list on Trello create the following Events:

kpantic

Decisions from 1st DevLeads Meeting regarding migration.

• All cards on Trello on Backlog or ToDo will be turned into Issues on GitLab. Checklists on Trello will be synced as checklists in Issue on GitLab.
• Assignment on a card or issue gets synced.
• Estimation will be handled in the name of an issue on GitLab. Synced from and to Trello.
• Automatic generation of Milestone triggered by assigning a label to the latest Agenda card.
• Doing is a label on GitLab that triggers a move to that list on Trello. The automatic assignment of this Label has to be discussed further.
• Client and design requirements blocking cards will be informed by Labels on GitLab and will generate changes to be defined on Trello.
• When an issue is ready to tested, it is closed on GitLab (moved to To Be Tested on Trello) and a related QA issue is created on GitLab.

kpantic

Trello

Todas estos datos haría falta verlos por Equipo, por miembro del equipo.

1. Total de Story Points completados semana a semana. (Tanto en este como en los puntos 2-4, no es importante que sea semana por semana pero como por día pudiese ser una agrupación muy poco útil, pusimos semanas. También pudiese ser una agrupación dinámica que dependa de que tanto tiempo se esté mostrando. Por ejemplo, si se mostrarán 5 días, se agrupa por días, si se mostrará un mes, se agrupa por semanas y si se mostrará un año, se agrupa por meses)
2. Total de Story Points asignados semana a semana.
3. Total de tarjetas finalizadas semana a semana cuyo esfuerzo fue menor a la estimación.
4. Total de tarjetas finalizadas semana a semana cuyo esfuerzo fue mayor a la estimación.
5. Promedios de los valores 1-4.
6. Calcular porcentaje de éxito de tarjetas que son movidas de To Be Tested a Approved a la primera. Explicación: Las tarjetas a ser probadas por QA (en To Be Tested) pueden ser rechazadas o aprobadas por el cliente o

kpantic

Scenarios that need to be handled in GitLab in order to fully migrate away from Trello for dev-dev communication.

1. Estimation and Effort for each User Story (card in Trello)
2. Differentiate between "Finished coding, deployed to Dev" and "Approved by client and deployed to production"
3. Mark a card as being blocked by a required client action.
4. Define weekly workload, full backlog for the current sprint and "wish list" for additional tasks.
5. Be able to, at a weekly meeting, assign tasks to each team member and have them report when they're working on a task via Trello during the week. This means separating "assigned", from "working on actively".
6. ...

kpantic

/* This can be copy-pasted into a Stylish (https://chrome.google.com/webstore/detail/stylish/fjnbnpbmkenffdnngjfgmeleoegfcffe?hl=en) */
/* style assigned to the right Inbox URL */

body{
	background: url(https://ssl.gstatic.com/ui/v1/icons/mail/images/2/5/ninja/footer_bg.gif);  
}

nav > div:first-child {
	background: rgb(0, 111, 138);
}

kpantic

from fabric.api import (task, local, lcd)


"""
The pep8 and jshint tasks return False if errors were found and True if found.
The show_errors parameter controls if the method prints out the errors returned by
the checker program.

Requirements: Install pep8 and jshint, so that they can be run from the command line
 - pip install pep8