51 Matching Annotations
  1. Nov 2019
    1. Create hybrid cloud consistency

      TODO: quick dive -- has hybrid identity management/sync + (these are not in AWS):

      • Integrated management and security across your hybrid cloud: This component provides you with a cohesive way to monitor, manage, and secure the environment, which enables increased visibility and control.
      • A consistent data platform for the datacenter and the cloud: This component creates data portability, combined with seamless access to on-premises and cloud data services for deep insight into all data sources.
      • Unified development and DevOps across the cloud and on-premises datacenters: This component allows you to move applications between the two environments as needed. Developer productivity improves because both locations now have the same development environment.
    2. Policy decisions.

      In AWS, security baseline - detective guardrails and logging.

    3. Using role-based access control.

      IAM in AWS

    4. Monitoring decisions.

      NOT IN AWS

    5. Cost requirements

      In AWS, consolidated billing and cost allocation tags

    6. organizing resources

      resource organization is the generic term for multi-account, multi-OU, multi-project approaches

    7. Database decisions.

      TODO: quick dive with decision tree - db options to be decided early on

    8. Networking decisions.

      TODO: quick dive with decision tree

    9. Storage decisions

      Only in Azure: storage is planned early on

    10. landing zone blueprints

      LZ CFs + Account Factory in AWS Service Catalog

    11. Azure Policy initiatives

      this is AWS Organizations with SCPs

    12. will be reflected in the blueprint or other automation scripts that create your landing zone

      At least IaC for LZ

  2. Jun 2019
    1. For Kraken and GDAX you may wish to use --order_type="taker", this uses market orders instead of limit orders. You usually pay a higher fee, but you can be sure that your order is filled instantly. This means that the sim will more closely match your live trading. Please note that GDAX does not charge maker fees (limit orders), so you will need to choose between not paying fees and running the risk orders do not get filled on time, or paying somewhat high % of fees and making sure your orders are always filled on time.
    1. RSI dropped below 30, signaling that there might be no more sellers left in the market and that the move could be over.

      RSI < 30 = oversold = price about to go up

      RSI > 70 = overbought = price about to go down

  3. May 2019
    1. Installing runtime

      apt-get install -y docker.io

    2. apt-get update && apt-get install -y apt-transport-https curl curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add - cat <<EOF >/etc/apt/sources.list.d/kubernetes.list deb https://apt.kubernetes.io/ kubernetes-xenial main EOF apt-get update apt-get install -y kubelet kubeadm kubectl apt-mark hold kubelet kubeadm kubectl

      Install Docker container runtime first.

      apt-get install -y docker.io

    1. Joining your nodes

      Install runtime.

      sudo -i
      apt-get update && apt-get upgrade -y
      apt-get install -y docker.io
      

      Install kubeadm, kubelet and kubectl.

      https://kubernetes.io/docs/setup/independent/install-kubeadm/#installing-kubeadm-kubelet-and-kubectl

      apt-get update && apt-get install -y apt-transport-https curl
      curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -
      cat <<EOF >/etc/apt/sources.list.d/kubernetes.list
      deb https://apt.kubernetes.io/ kubernetes-xenial main
      EOF
      apt-get update
      apt-get install -y kubelet kubeadm kubectl
      apt-mark hold kubelet kubeadm kubectl
      
    1. When designing the addressing plan for an application, the primary consideration is to keep the CIDR blocks used for creating subnets within a single zone as contiguous as possible
    1. The CIDR block must not be the same or larger than the CIDR range of a route in any of the VPC route tables.
    2. You have a limit on the number of CIDR blocks you can associate with a VPC and the number of routes you can add to a route table. You cannot associate a CIDR block if this results in you exceeding your limits.
      • IPv4 CIDR blocks per VPC 5 This limit is made up of your primary CIDR block plus 4 secondary CIDR blocks.

      • Route tables per VPC

      200

      This limit includes the main route table.

      • Routes per route table (non-propagated routes)

      50

      You can increase this limit up to a maximum of 1000; however, network performance might be impacted. This limit is enforced separately for IPv4 routes and IPv6 routes.

      If you have more than 125 routes, we recommend that you paginate calls to describe your route tables for better performance.

    3. You cannot increase or decrease the size of an existing CIDR block.
    4. The allowed block size is between a /28 netmask and /16 netmask.
    5. Adding IPv4 CIDR Blocks to a VPC

      Expanding a VPC IPv4 CIDR block

    1. The permissible size of the block ranges between /16 netmask and a /28 netmask.

      Permissible AWS CIDR block range for AWS VPC

    1. When creating VPCs and VSwitches, you have to specify the private IP address range for the VPC in the form of a Classless Inter-Domain Routing (CIDR) block. Private IP address range of VPC Use 192.168.0.0/16, 172.16.0.0/12, and 10.0.0.0/8 or their subsets as the private IP address range for your VPC. Note the following when planning the private IP address range of VPC: If you have only one VPC and it does not have to communicate with a local data center, you are free to use any of the preceding IP address ranges or their subnets. If you have multiple VPCs, or you want to build a hybrid cloud composed of one or more VPCs and local data centers, we recommend that you use a subset of these standard IP address ranges as the IP address range for your VPC and make sure that the netmask is no larger than /16. You also need to consider whether the classic network is used when selecting a VPC CIDR block. If you plan to connect ECS instances in a classic network with a VPC, we recommend that you do not use the IP address range 10.0.0.0/8, which is also used by the classic network.

      VPC CIDR / IP Addressing plan

    1. def trigger_state_machines(self):

      Get the state machines arn mapping ( {what the state machine is for} : {state machineARN} ) in the environment variables of LandingZoneStateMachineTriggerLambda function

    1. Diapers Are Not Forever
    2. Potty Training Tip #9: Read Potty-Themed Books
    3. I love Potette
    4. Potty Training Tip #7: Take It on the Road
    5. Cons:Avoid going overboard, says Christophersen. “Then, when your child has an accident, they may be deflated by the lack of support.” Tell them that accidents happen!
    6. Potty Training Tip #4: Give Praise and Affirmation
    7. Potty Training Tip #3: Give a Reward (and Get Creative!)
    8. When they do put it in the potty, make sure you both have a look (yuck, I know, but the visual is important.)
    9. Make flushing a huge deal by pointing at the swirling water and acknowledging the cool whooshing sound.
    10. Potty Training Tip #2: Try Naked Time
    11. If you leave the house, have a spare potty in the car or visit places you’re sure have public restrooms.
    12. On the third day, go for an all-day session.
    13. Let them eat, drink and play as normal, but every 15 minutes put them on the potty. At the end of a session, revert back to a diaper or pull-up and go on with your day.
    14. This means that you’ll want to train your child in the morning and afternoon for a few hours at home.
  4. Apr 2019