zaletniy

Using Graph Analysis to Design Microservice Architectures in the Cloud

This interactive Neo4j graph tutorial covers how to use graph analysis to find software modules that are highly centralized, making good candidates to be decomposed into microservices.

---

zaletniy

openapi: 3.0.0
# Added by API Auto Mocking Plugin
servers:
  - description: SwaggerHub API Auto Mocking
    url: https://virtserver.swaggerhub.com/SVilgelm/IAM_API/1.0.0
  - description: keyckloak.k8ss
    url: https://keycloak.local:8443/auth/realms/k8s


info:

zaletniy

RSA key

File like

-----BEGIN RSA PRIVATE KEY-----
MIIEpAIBAAKCAQEAr7ivQ7D5lbF4Z3bB6xNJ+IJwkr+1J7MJpbSt8/Ge6ORbbpK3
...
ajwMAEogApmYwgWg57Ri6H8debGDkk5bEEYDbXJBXAuNb5835s5Ael+BZCe7u/NU
/RIOvToDuSemdCp27s1MqxMr3hrNg3agXKmSDCWhM27dj1eH2fDP7g==
-----END RSA PRIVATE KEY-----

zaletniy

#!/bin/bash
# Usage:
#  passe secret_alias recepient
#
# Example:
#  passe jira_admin_password Ian
#

# Waiting when it will be replaced with 
# age https://docs.google.com/document/d/11yHom20CrsuX8KQJXBBw04s80Unjv8zCg_A7sPAX_9Y/edit#

zaletniy

Keybase proof

I hereby claim:

• I am zaletniy on github.
• I am zaletniy (https://keybase.io/zaletniy) on keybase.
• I have a public key ASBAJZFVbq777Zy3IauW53NTx83z1mhWisv0OhTk3wQp_wo

To claim this, I am signing this object:

zaletniy

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>
  <parent>
    <groupId>org.opendaylight.controller</groupId>
    <artifactId>commons.parent</artifactId>
    <version>1.0.2-SNAPSHOT</version>
    <relativePath>opendaylight/commons/parent</relativePath>
  </parent>
  <artifactId>releasepom</artifactId>

zaletniy

Trove-Heat Integration Topics:

1. Hardening the heat integration: The instances are not turning ACTIVE on multiple occasions. Further investigation on with the pointer that during some of these cases the prepare method is not called.
2. Heat Events than poll: The polling mechanism to check the status of the heat-stack for completion/failure can be replaced with handling the events from heat and acting accordingly. In the wake of point 1 above, it also needs to be validated that stack- creation-complete status from heat syncs with the instance creation within the stack.
3. Configurable templating: Making the template content as configurable.
4. Trove instance-store updates for multiple instances (governed by the template): In case the template provisions more than one instances then we need a design on the instance state update in trove db.
5. Any further abstractions in trove (may be an instance-group concept) per point 4: Do we need an instance-group like concept in trove for aggregating the multiple instan