Brian Dant briandant

➜ ficus vagrant up Ignoring ffi-1.9.10 because its extensions are not built. Try: gem pristine ffi --version 1.9.10 Ignoring nokogiri-1.6.3.1 because its extensions are not built. Try: gem pristine nokogiri --version 1.6.3.1 Ignoring unf_ext-0.0.7.1 because its extensions are not built. Try: gem pristine unf_ext --version 0.0.7.1 Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'ficus-devstack-2017-02-07'... ==> default: Matching MAC address for NAT networking... ==> default: Setting the name of the VM: ficus_default_1507581667207_79795 ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration...

La Vitoria

La Victoria 1: https://app.sparkmailapp.com/web-share/K02DAA_3Nzru2-F1q13t3S6hq-TBQEOsdDKPL0LS
La Victoria 2: https://app.sparkmailapp.com/web-share/tYYp2e-TfdxH6czwD7p779DS52Nl4GHTWpbxOis3
La Victoria 3: https://app.sparkmailapp.com/web-share/PygBtjAFD0OisfAveecBGj5q99yERN4QUXsYxXSV
La Vitoria 4: https://app.sparkmailapp.com/web-share/NNcevzSdfd1cSZyajmbV7HdmOWb4Q-T95ORCShti

Coveralls

Jul 2019: https://app.sparkmailapp.com/web-share/k6Cky-3TsRqyGG3-Fwy1NkMTjxkQlheMk2bOHxaa

Overview

This document explains how to best manage Theia at ISC, in conjunction with Appsembler.

Repo structure

One repo for Theia: appsembler/theia
One repo for all the ISC Docker Images
Several repos for Theia extensions

user___97983658

What does the consul kv store show now, as the container is stopped?

The container is indeed stopped:

$ swarm ps -a | grep user___97983658
a8c520d42a7f        idev_110_2019.1:v4                   "supervisord -c /etc…"    27 hours ago        Exited (0) 2 hours ago                                                                                                                                                    prod-itential-wharfhouse-4/user___97983658

The key question is "What attributes are you checking on the container's metadata?" We ask because it looks like the only thing modified by passing in --cpu is NanoCpus, not Cpus. We can successfully modify NanoCpus via the AVL application, but your application still complains that the cores count is too high.

A container started from the AVL dashboard:

root@prod-iscgseu1-wharfhouse-0:/home/briandant# swarm inspect learner___138ab157___0 | grep -i cpu

	FROM debian:jessie

	MAINTAINER Stuart Peters <[email protected]>

	# Arguments passed in
	ARG FTP_FILE=ftp://kitserver/kits/unreleased_ftp/IPDTool/2018.1.0/2018.1.0.245.0/IPDTool-2018.1.0.245.0-unix.tar.gz
	ARG KIT_DIR=IPDTool-2018.1.0.245.0-unix
	ENV TERRAFORM_VER="0.9.4"
	ENV DOCKER_VERSION="17.03.1-ce"
	ENV INT_F_NAME IPDTool-2018.1.0.245.0-unix.tar.gz

	Vagrant.require_version ">= 1.8.7"
	unless Vagrant.has_plugin?("vagrant-vbguest")
	raise "Please install the vagrant-vbguest plugin by running `vagrant plugin install vagrant-vbguest`"
	end

	VAGRANTFILE_API_VERSION = "2"

	MEMORY = 4096
	CPU_COUNT = 2