nilebox

# 1. Current Nail's PR implementation
# + single union type with uniform way of passing parameters
# - breaking backward compatibility with current "parameters" field
# - extra "inline" nesting level for inline parameters (concern expressed by Doug)
spec:
  serviceClassName: user-provided-service
  planName: default
  parameters:
    inline:
      username: root

nilebox

package queue;

import com.google.common.collect.ImmutableMap;
import org.joda.time.Duration;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.jdbc.core.JdbcTemplate;
import org.springframework.jdbc.core.RowCallbackHandler;
import org.springframework.jdbc.core.RowMapper;
import org.springframework.jdbc.core.namedparam.MapSqlParameterSource;

nilebox

• Backward compatible API:
  • API resource names finalized (#1080)
    • implemented by @duglin and merged (#1054), but then reverted
    • proposal: pending for API review? Who's taking action? @pmorie?
  • Kube names of ServiceClass and Plan determined (#802)
    • proposal: @pmorie started a discussion in sig-architecture, no consensus yet
  • Use Generation instead of checksum (#1095)
    • proposal: written by @pmorie, there are questions, no consensus yet
  • Create new resource for plan (#454)
• proposal: @MHBauer, had a consensus today with reverse reference from plan to class

nilebox

Goals

• Being able to provision and consume resources that live outside Kubernetes cluster, with a standard API
• Kubernetes native UX from the Service Catalog API and kubectl perspective
• Seamless integration of credentials into Pods
• Integration with brokers according to OSB spec and REST API

Non-goals

• Making OSB dictate the implementation details of the platform
• Consistency with CloudFoundry behavior (which works as a stateless direct RPC proxy, sends only partial updates with diff etc) is not a concern, as long as we meet the OSB requirements

nilebox

/*
 You are given:
- a set of tiles, each tile represents a letter and a score associated with it; there might be many tiles of the same letter, each having the same score
- a dictionary of valid words

Find a set of words combined from the tiles that will give you a max sum score. Each tile can be used at most once.
You have to subtract the total sum of remaining (unused) tiles from the result.
*/

class Tile {

nilebox

syntax = "proto3";

// NOTE: Groups with big hex numbers is just an illustration for easier visibility

// Option 1: Combined enum

enum Severity
{
  DEBUG          = 0x000;
  DEBUG_TRACE    = 0x001;

nilebox

{
  user(login: "nilebox") {
    id
    login
    organizations(first: 10) {
      nodes {
        id
        name
      }
    }