elek

#!/usr/bin/env bash

: ${BYTEMAN_HOME=/tmp/byteman}
: ${BYTEMAN_DOWNLOAD_FILE=/tmp/byteman.zip}

if [ ! -d "$BYTEMAN_HOME" ]; then
   if [ ! -f "$BYTEMAN_DOWNLOAD_FILE" ]; then
      wget https://downloads.jboss.org/byteman/4.0.10/byteman-download-4.0.10-bin.zip -O "$BYTEMAN_DOWNLOAD_FILE"
   fi
   unzip "$BYTEMAN_DOWNLOAD_FILE" -d /tmp/

elek

elek

diff --git a/hadoop-ozone/dev-support/checks/integration.sh b/hadoop-ozone/dev-support/checks/integration.sh
index f522224f..d7883de3 100755
--- a/hadoop-ozone/dev-support/checks/integration.sh
+++ b/hadoop-ozone/dev-support/checks/integration.sh
@@ -18,8 +18,7 @@ cd "$DIR/../../.." || exit 1
 
 export MAVEN_OPTS="-Xmx4096m"
 mvn -B install -DskipTests
-mvn -B -fn test -pl :hadoop-ozone-integration-test,:hadoop-ozone-filesystem,:hadoop-ozone-tools \
-  -Dtest=\!TestMiniChaosOzoneCluster "$@"

elek

COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.0

COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.0

1. Definitions.

1.1. "Contributor" means each individual or entity that creates or contributes to the creation of Modifications.

1.2. "Contributor Version" means the combination of the Original Software, prior Modifications used by a Contributor (if any), and the Modifications made by that particular Contributor.

elek

  The MIT License
 
  Copyright (c) 2009 codehaus.org.
 
  Permission is hereby granted, free of charge, to any person obtaining a copy
  of this software and associated documentation files (the "Software"), to deal
  in the Software without restriction, including without limitation the rights
  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
  copies of the Software, and to permit persons to whom the Software is
  furnished to do so, subject to the following conditions:

elek

#!/usr/bin/env bash

sudo apk add --update --no-cache python py-pip 
sudo pip install --upgrade pip
sudo pip install robotframework requests robotframework-requests
git clone https://github.com/flokkr/robot.git /robot

elek

#!/usr/bin/env bash
set -x
export LOG_DIR=${LOG_DIR:-/tmp/log}
BASE_DIR=${BASE_DIR:-/opt/src}
mkdir -p $BASE_DIR
if [[ "$BASE_DIR" ]]; then
    cd $BASE_DIR
fi

elek

(Context: One of my college asked me about the Helm charts vs. Operators. And this was my answer)

Good question and I am very opinionated about this. I am not sure if I am right, but this is my personal view:

1. Kubernetes itself is hihghliy flexible (and this is the biggest power of it). The API can handle any resource types, everything is generic inside.

2. But it's not solved how the k8s yaml files should be effectively managed to release/deploy/operate applications.

3. One approach is Helm chart: using templates to generate the k8s resources files and install them with a server side component.

elek

We couldn’t find that file to show.

elek

/**
 * Licensed to the Apache Software Foundation (ASF) under one
 * or more contributor license agreements.  See the NOTICE file
 * distributed with this work for additional information
 * regarding copyright ownership.  The ASF licenses this file
 * to you under the Apache License, Version 2.0 (the
 * "License"); you may not use this file except in compliance
 * with the License.  You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/toLICENSE-2.0